FAQ Search Today's Posts Mark Forums Read
» Video Reviews

» Linux Archive

Linux-archive is a website aiming to archive linux email lists and to make them easily accessible for linux users/developers.


» Sponsor

» Partners

» Sponsor

Go Back   Linux Archive > ArchLinux > ArchLinux General Discussion

 
 
LinkBack Thread Tools
 
Old 07-09-2012, 03:49 PM
"David C. Rankin"
 
Default util-linux pacman error, file conflicts (safe to force?)

Tom, All,

I ran into the following error regarding util-linux upgrade. I've looked in
the forum and the website, but nothing specific to it. The error is:


(72/72) checking for file conflicts
[###########################################] 100%

error: failed to commit transaction (conflicting files)
util-linux: /bin/login exists in filesystem
util-linux: /etc/pam.d/chfn exists in filesystem
util-linux: /etc/pam.d/chsh exists in filesystem
util-linux: /etc/pam.d/login exists in filesystem
util-linux: /usr/bin/chfn exists in filesystem
util-linux: /usr/bin/chsh exists in filesystem
util-linux: /usr/bin/newgrp exists in filesystem
util-linux: /usr/sbin/vigr exists in filesystem
util-linux: /usr/sbin/vipw exists in filesystem
util-linux: /usr/share/man/man1/chfn.1.gz exists in filesystem
util-linux: /usr/share/man/man1/chsh.1.gz exists in filesystem
util-linux: /usr/share/man/man1/login.1.gz exists in filesystem
util-linux: /usr/share/man/man1/newgrp.1.gz exists in filesystem
util-linux: /usr/share/man/man8/vigr.8.gz exists in filesystem
util-linux: /usr/share/man/man8/vipw.8.gz exists in filesystem
Errors occurred, no packages were upgraded.

Is this safe to force? I ask because I don't want to kill login by forcing
if there is a preferred way to do this.... What say the experts?


(this has happened on all my boxes..)


--
David C. Rankin, J.D.,P.E.
 
Old 07-09-2012, 03:52 PM
Mateusz Loskot
 
Default util-linux pacman error, file conflicts (safe to force?)

On 9 July 2012 16:49, David C. Rankin <drankinatty@suddenlinkmail.com> wrote:
> Tom, All,
>
> I ran into the following error regarding util-linux upgrade. I've looked
> in the forum and the website, but nothing specific to it. The error is:
>
> (72/72) checking for file conflicts
> [###########################################] 100%
> error: failed to commit transaction (conflicting files)
> util-linux: /bin/login exists in filesystem

> [...]

Check the ArchLinux ARM forum:

http://archlinuxarm.org/forum/viewtopic.php?t=3036&p=18467

where filesystem upgrade is suggested:

pacman -Syuf

But, I'd wait until someone confirms it is the right way to go.

Best regards,
--
Mateusz Loskot, http://mateusz.loskot.net
 
Old 07-09-2012, 04:10 PM
Denis A. Altoé Falqueto
 
Default util-linux pacman error, file conflicts (safe to force?)

On Mon, Jul 9, 2012 at 1:01 PM, David C. Rankin
<drankinatty@suddenlinkmail.com> wrote:
> On 07/09/2012 10:52 AM, Mateusz Loskot wrote:
>>
>> Check the ArchLinux ARM forum:
>>
>> http://archlinuxarm.org/forum/viewtopic.php?t=3036&p=18467
>>
>> where filesystem upgrade is suggested:
>>
>> pacman -Syuf
>>
>> But, I'd wait until someone confirms it is the right way to go.
>
>
>
> Thank you Mateusz!
>
> We will wait for the all clear from the devs before forcing. Arch Devs,
> when you can confirm a force is the proper way to handle this util-linux
> issue, please let us know. I'm just trying to avoid causing myself grief

One strange thing is that the files generating the conflict are owned
by the shadow package. I don't remember of any warning about forcing
updates for util-linux in arch-devel. It seems to me like a packaging
bug.

--
A: Because it obfuscates the reading.
Q: Why is top posting so bad?
For more information, please read: http://idallen.com/topposting.html

-------------------------------------------
Denis A. Altoe Falqueto
Linux user #524555
-------------------------------------------
 
Old 07-09-2012, 04:13 PM
Mateusz Loskot
 
Default util-linux pacman error, file conflicts (safe to force?)

On 9 July 2012 17:11, Daniel Wallace <daniel.wallace@gatech.edu> wrote:
> On Mon, Jul 09, 2012 at 04:52:08PM +0100, Mateusz Loskot wrote:
>> On 9 July 2012 16:49, David C. Rankin <drankinatty@suddenlinkmail.com> wrote:
>> > Tom, All,
>> >
>> > I ran into the following error regarding util-linux upgrade. I've looked
>> > in the forum and the website, but nothing specific to it. The error is:
>> >
>> > (72/72) checking for file conflicts
>> > [###########################################] 100%
>> > error: failed to commit transaction (conflicting files)
>> > util-linux: /bin/login exists in filesystem
>>
>> > [...]
>>
>> Check the ArchLinux ARM forum:
>>
>> http://archlinuxarm.org/forum/viewtopic.php?t=3036&p=18467
>>
>> where filesystem upgrade is suggested:
>>
>> pacman -Syuf
>>
>> But, I'd wait until someone confirms it is the right way to go.
>
> never -Syuf
> never -Suf
> never force an upgrade

In this particular case, what about:

pacman -Syu --ignore filesystem && pacman -S filesystem --force

what is advised on the ArchLinux ARM forum too.

(Disclaimer: I'm newbie here.)

Best regards,
--
Mateusz Loskot, http://mateusz.loskot.net
 
Old 07-09-2012, 04:26 PM
Mateusz Loskot
 
Default util-linux pacman error, file conflicts (safe to force?)

On 9 July 2012 17:17, Daniel Wallace <daniel.wallace@gatech.edu> wrote:
> On Mon, Jul 09, 2012 at 05:13:47PM +0100, Mateusz Loskot wrote:
>> On 9 July 2012 17:11, Daniel Wallace <daniel.wallace@gatech.edu> wrote:
>> > On Mon, Jul 09, 2012 at 04:52:08PM +0100, Mateusz Loskot wrote:
>> >> On 9 July 2012 16:49, David C. Rankin <drankinatty@suddenlinkmail.com> wrote:
>> >> > Tom, All,
>> >> >
>> >> > I ran into the following error regarding util-linux upgrade. I've looked
>> >> > in the forum and the website, but nothing specific to it. The error is:
>> >> >
>> >> > (72/72) checking for file conflicts
>> >> > [###########################################] 100%
>> >> > error: failed to commit transaction (conflicting files)
>> >> > util-linux: /bin/login exists in filesystem
>> >>
>> >> > [...]
>> >>
>> >> Check the ArchLinux ARM forum:
>> >>
>> >> http://archlinuxarm.org/forum/viewtopic.php?t=3036&p=18467
>> >>
>> >> where filesystem upgrade is suggested:
>> >>
>> >> pacman -Syuf
>> >>
>> >> But, I'd wait until someone confirms it is the right way to go.
>> >
>> > never -Syuf
>> > never -Suf
>> > never force an upgrade
>>
>> In this particular case, what about:
>>
>> pacman -Syu --ignore filesystem && pacman -S filesystem --force
>>
>> what is advised on the ArchLinux ARM forum too.
>>
>> (Disclaimer: I'm newbie here.)
>
>
> that is different. you aren't forcing the update.

Understood.

> I have not used archlinuxarm.

I have not used it either.

> You could always go ask in #archlinux-arm on freenode

No, because I'm asking about ArchLinux and its pacman.
I'm not interested in ArchLinux ARM.

Best regards.
--
Mateusz Loskot, http://mateusz.loskot.net
 
Old 07-09-2012, 04:28 PM
Ike Devolder
 
Default util-linux pacman error, file conflicts (safe to force?)

Op maandag 9 juli 2012 17:13:47 schreef Mateusz Loskot:
> On 9 July 2012 17:11, Daniel Wallace <daniel.wallace@gatech.edu> wrote:
> > On Mon, Jul 09, 2012 at 04:52:08PM +0100, Mateusz Loskot wrote:
> >> On 9 July 2012 16:49, David C. Rankin <drankinatty@suddenlinkmail.com>
wrote:
> >> > Tom, All,
> >> >
> >> > I ran into the following error regarding util-linux upgrade. I've
> >> > looked
> >> > in the forum and the website, but nothing specific to it. The error is:
> >> >
> >> > (72/72) checking for file conflicts
> >> > [###########################################] 100%
> >> > error: failed to commit transaction (conflicting files)
> >> > util-linux: /bin/login exists in filesystem
> >> >
> >> > [...]
> >>
> >> Check the ArchLinux ARM forum:
> >>
> >> http://archlinuxarm.org/forum/viewtopic.php?t=3036&p=18467
> >>
> >> where filesystem upgrade is suggested:
> >>
> >> pacman -Syuf
> >>
> >> But, I'd wait until someone confirms it is the right way to go.
> >
> > never -Syuf
> > never -Suf
> > never force an upgrade
>
> In this particular case, what about:
>
> pacman -Syu --ignore filesystem && pacman -S filesystem --force
>
> what is advised on the ArchLinux ARM forum too.
>
> (Disclaimer: I'm newbie here.)
>
> Best regards,

This is only valid concerning the update of the filesystem package from before
2012.6-2 to >= 2012.6-2 as noted in the newsitem [1].
Never use force if it was not advised like this in a newsitem.

[1]http://www.archlinux.org/news/filesystem-upgrade-manual-intervention-
required-1/

--Ike
 
Old 07-09-2012, 04:34 PM
Mateusz Loskot
 
Default util-linux pacman error, file conflicts (safe to force?)

On 9 July 2012 17:28, Ike Devolder <ike.devolder@gmail.com> wrote:
> Op maandag 9 juli 2012 17:13:47 schreef Mateusz Loskot:
>> On 9 July 2012 17:11, Daniel Wallace <daniel.wallace@gatech.edu> wrote:
>> > On Mon, Jul 09, 2012 at 04:52:08PM +0100, Mateusz Loskot wrote:
>> >> On 9 July 2012 16:49, David C. Rankin <drankinatty@suddenlinkmail.com> wrote:
>> >> >
>> >> > Tom, All,
>> >> >
>> >> > I ran into the following error regarding util-linux upgrade. I've
>> >> > looked
>> >> > in the forum and the website, but nothing specific to it. The error is:
>> >> >
>> >> > (72/72) checking for file conflicts
>> >> > [###########################################] 100%
>> >> > error: failed to commit transaction (conflicting files)
>> >> > util-linux: /bin/login exists in filesystem
>> >> >
>> >> > [...]
>> >>
>> >> Check the ArchLinux ARM forum:
>> >>
>> >> http://archlinuxarm.org/forum/viewtopic.php?t=3036&p=18467
>> >>
>> >> where filesystem upgrade is suggested:
>> >>
>> >> pacman -Syuf
>> >>
>> >> But, I'd wait until someone confirms it is the right way to go.
>> >
>> > never -Syuf
>> > never -Suf
>> > never force an upgrade
>>
>> In this particular case, what about:
>>
>> pacman -Syu --ignore filesystem && pacman -S filesystem --force
>>
>> what is advised on the ArchLinux ARM forum too.
>>
>> (Disclaimer: I'm newbie here.)
>
> This is only valid concerning the update of the filesystem package from before
> 2012.6-2 to >= 2012.6-2 as noted in the newsitem [1].
> Never use force if it was not advised like this in a newsitem.
>
> [1]http://www.archlinux.org/news/filesystem-upgrade-manual-intervention-
> required-1/

Thanks Ike, that's really helpful bit.

Best regards,
--
Mateusz Loskot, http://mateusz.loskot.net
 
Old 07-09-2012, 04:47 PM
Tom Gundersen
 
Default util-linux pacman error, file conflicts (safe to force?)

On Mon, Jul 9, 2012 at 5:13 PM, Mateusz Loskot <mateusz@loskot.net> wrote:
> On 9 July 2012 17:11, Daniel Wallace <daniel.wallace@gatech.edu> wrote:
>> On Mon, Jul 09, 2012 at 04:52:08PM +0100, Mateusz Loskot wrote:
>>> On 9 July 2012 16:49, David C. Rankin <drankinatty@suddenlinkmail.com> wrote:
>>> > Tom, All,
>>> >
>>> > I ran into the following error regarding util-linux upgrade. I've looked
>>> > in the forum and the website, but nothing specific to it. The error is:
>>> >
>>> > (72/72) checking for file conflicts
>>> > [###########################################] 100%
>>> > error: failed to commit transaction (conflicting files)
>>> > util-linux: /bin/login exists in filesystem
>>>
>>> > [...]
>>>
>>> Check the ArchLinux ARM forum:
>>>
>>> http://archlinuxarm.org/forum/viewtopic.php?t=3036&p=18467
>>>
>>> where filesystem upgrade is suggested:
>>>
>>> pacman -Syuf
>>>
>>> But, I'd wait until someone confirms it is the right way to go.
>>
>> never -Syuf
>> never -Suf
>> never force an upgrade
>
> In this particular case, what about:
>
> pacman -Syu --ignore filesystem && pacman -S filesystem --force

This is a separate issue, which there was a news item about. David's
question was not about filesystem, but about util-linux/shadow.

Cheers,

Tom
 
Old 07-09-2012, 04:49 PM
Tom Gundersen
 
Default util-linux pacman error, file conflicts (safe to force?)

On Mon, Jul 9, 2012 at 5:38 PM, Leonid Isaev <lisaev@umail.iu.edu> wrote:
> On Mon, 09 Jul 2012 10:49:46 -0500
> "David C. Rankin" <drankinatty@suddenlinkmail.com> wrote:
>
>> Tom, All,
>>
>> I ran into the following error regarding util-linux upgrade. I've looked
>> in the forum and the website, but nothing specific to it. The error is:
>>
>> (72/72) checking for file conflicts
>> [###########################################] 100%
>> error: failed to commit transaction (conflicting files)
>> util-linux: /bin/login exists in filesystem
>> util-linux: /etc/pam.d/chfn exists in filesystem
>> util-linux: /etc/pam.d/chsh exists in filesystem
>> util-linux: /etc/pam.d/login exists in filesystem
>> util-linux: /usr/bin/chfn exists in filesystem
>> util-linux: /usr/bin/chsh exists in filesystem
>> util-linux: /usr/bin/newgrp exists in filesystem
>> util-linux: /usr/sbin/vigr exists in filesystem
>> util-linux: /usr/sbin/vipw exists in filesystem
>> util-linux: /usr/share/man/man1/chfn.1.gz exists in filesystem
>> util-linux: /usr/share/man/man1/chsh.1.gz exists in filesystem
>> util-linux: /usr/share/man/man1/login.1.gz exists in filesystem
>> util-linux: /usr/share/man/man1/newgrp.1.gz exists in filesystem
>> util-linux: /usr/share/man/man8/vigr.8.gz exists in filesystem
>> util-linux: /usr/share/man/man8/vipw.8.gz exists in filesystem
>> Errors occurred, no packages were upgraded.
>>
>> Is this safe to force? I ask because I don't want to kill login by
>> forcing if there is a preferred way to do this.... What say the experts?
>
> Hmm.. pacman should have taken care of this automatically.
>
> Do: pacman -Sy && pacman -Su --ignore util-linux,shadow && pacman -S shadow
> util-linux. If the last call fails, use --force.

Never use force, not even as a last resort, unless you really know
that it is the right thing to do. It is very likely to end up deleting
your files.

-t
 
Old 07-09-2012, 04:51 PM
Tom Gundersen
 
Default util-linux pacman error, file conflicts (safe to force?)

On Mon, Jul 9, 2012 at 4:49 PM, David C. Rankin
<drankinatty@suddenlinkmail.com> wrote:
> Tom, All,
>
> I ran into the following error regarding util-linux upgrade. I've looked
> in the forum and the website, but nothing specific to it. The error is:
>
> (72/72) checking for file conflicts
> [###########################################] 100%
> error: failed to commit transaction (conflicting files)
> util-linux: /bin/login exists in filesystem
> util-linux: /etc/pam.d/chfn exists in filesystem
> util-linux: /etc/pam.d/chsh exists in filesystem
> util-linux: /etc/pam.d/login exists in filesystem
> util-linux: /usr/bin/chfn exists in filesystem
> util-linux: /usr/bin/chsh exists in filesystem
> util-linux: /usr/bin/newgrp exists in filesystem
> util-linux: /usr/sbin/vigr exists in filesystem
> util-linux: /usr/sbin/vipw exists in filesystem
> util-linux: /usr/share/man/man1/chfn.1.gz exists in filesystem
> util-linux: /usr/share/man/man1/chsh.1.gz exists in filesystem
> util-linux: /usr/share/man/man1/login.1.gz exists in filesystem
> util-linux: /usr/share/man/man1/newgrp.1.gz exists in filesystem
> util-linux: /usr/share/man/man8/vigr.8.gz exists in filesystem
> util-linux: /usr/share/man/man8/vipw.8.gz exists in filesystem
> Errors occurred, no packages were upgraded.

Upgrade shadow at the same time and it should solve the problem (or if
not, specify the upgrade order manually as Leonid suggested, though I
have not seen this beeing needed myself). Don't use --force.

Tom
 

Thread Tools




All times are GMT. The time now is 02:58 PM.

VBulletin, Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.
Copyright ©2007 - 2008, www.linux-archive.org