[Solved] Updated filesystem and pacman info

new2arch · 2008-06-19 18:21:38

Pulled down the filesystem 2008.06-2 and after installation I get these warnings:

[2008-06-19 16:21] warning: /etc/issue installed as /etc/issue.pacnew
[2008-06-19 16:21] warning: /etc/passwd installed as /etc/passwd.pacnew
[2008-06-19 16:21] warning: /etc/shadow installed as /etc/shadow.pacnew
[2008-06-19 16:21] warning: /etc/fstab installed as /etc/fstab.pacnew
[2008-06-19 16:21] warning: /etc/gshadow installed as /etc/gshadow.pacnew
[2008-06-19 16:21] warning: /etc/hosts installed as /etc/hosts.pacnew
[2008-06-19 16:21] warning: /etc/group installed as /etc/group.pacnew
[2008-06-19 16:21] warning: /etc/resolv.conf installed as /etc/resolv.conf.pacn$
[2008-06-19 16:21] warning: /etc/ld.so.conf installed as /etc/ld.so.conf.pacnew
[2008-06-19 16:21] upgraded filesystem (2008.03-2 -> 2008.06-2)

Am I supposed to act? Why did the filesystem upgrade touch my passwd /shadow files?

The other PC that I upgraded didn't produce any of above messages.

Last edited by new2arch (2008-06-21 21:24:36)

kezar · 2008-06-19 18:36:09

It didn't do anything at all. Read http://wiki.archlinux.org/index.php/Pacnew_files

new2arch · 2008-06-19 18:56:32

kezar wrote:

It didn't do anything at all. Read http://wiki.archlinux.org/index.php/Pacnew_files

Thanks for the link.
But I'm still curious on why the filesystem upgrade would attempt to try replacing my passwd file?

phrakture · 2008-06-19 19:14:07

Because the initial passwd file is part of that package, and it was changed. pacnew files are generally a sign that you may need to merge something

bobdob · 2008-06-19 19:14:49

Does anyone else have a problem upgrading this package, because I get the following error:

error: could not prepare transaction
error: failed to commit transaction (conflicting files)
filesystem: /usr/local/share/man exists in filesystem
Errors occurred, no packages were upgraded.

Rulatir · 2008-06-19 19:26:49

Confirmed, same problem as bobdob in #5.

bobdob · 2008-06-19 19:45:44

I looked at /usr/local/share/man and it only contained two empty directories and a file named whatis which was 0 bytes???.
I moved it to man.old and the packaged installed with no errors.

new2arch · 2008-06-19 20:46:13

phrakture wrote:

Because the initial passwd file is part of that package, and it was changed. pacnew files are generally a sign that you may need to merge something

Ok, I didn't know the filesystem package contained multiple files. Thanks for clarifying that. I browsed the forum and found the tip about vim -> vimdiff [file] [file]. It's awesome.
I can conclude I don't want/need to merge any of my pacnew files with my old ones because I believe that will cause various problems... I assume it is okay to throw away the *.pacnew files since I don't intend to use them?

Last edited by new2arch (2008-06-19 20:46:41)

Stythys · 2008-06-19 21:33:54

guys, just run 'pacman -Suf' to get rid of the conflicting files error.

tigrmesh · 2008-06-20 02:56:23

new2arch wrote:

I can conclude I don't want/need to merge any of my pacnew files with my old ones because I believe that will cause various problems... I assume it is okay to throw away the *.pacnew files since I don't intend to use them?

Erm... That's not a good idea. Sometimes config syntax changes, and the program will expect the new syntax. I've had my system fail to boot due to unmerged changes (ignored pacnew files).

You actually want to replace the current config files with the new ones (adding in all of your changes).

toofishes · 2008-06-20 03:03:04

Stythys wrote:

guys, just run 'pacman -Suf' to get rid of the conflicting files error.

And get f*&%ed in the ass sometime when you overwrite something you really needed. This is the stupidest blanket advice you can give. I kind of hope you get screwed so you don't give bad advice again.

new2arch · 2008-06-20 09:09:24

tigrmesh wrote:

Erm... That's not a good idea. Sometimes config syntax changes, and the program will expect the new syntax. I've had my system fail to boot due to unmerged changes (ignored pacnew files).
You actually want to replace the current config files with the new ones (adding in all of your changes).

If you put it that way I will have to reconsider my statement and decision. However, after having studied the pacnew files and compared those with my current ones I simply cannot detect any differences except for the adjustments I've manually added to the stock config files such as 'group', 'passwd' and so forth.

Sorry for a noobish question but the syntax you're referring to, is it something hidden and thus I cannot see in the config files?

And if I wanted to merge pacnew and old config files, do I have to add my config changes to the pacnew files or can I do it other way around? I am not being lazy but replacing and merging the old config files with pacnew involves the proceedure of the renaming *.pacnew files.

Last edited by new2arch (2008-06-20 09:10:11)

dystoptic · 2008-06-20 12:53:16

For me the only things that changed were some directory names in fstab, e.g. /dev/cdrom -> /dev/cd

I would like to have only warnings, when the files really change. But in about 90 percent I do a diff and see nothing new. So I think if would be good, if there would be a check from the previous installed package to the actual. And if the diff of config files in those two packages shows nothing, than the file change warning could be omitted.

toofishes · 2008-06-20 13:47:53

There is- pacman doesn't make pacnew files *unless* something changed. Thus the appearance of a pacnew file is a pretty good sign you should do a merge and compare of the two files.

new2arch · 2008-06-20 14:05:06

toofishes wrote:

There is- pacman doesn't make pacnew files *unless* something changed. Thus the appearance of a pacnew file is a pretty good sign you should do a merge and compare of the two files.

I haven't paid any attention regarding this potential *.pacnew issue until now, guess I was lucky I didn't encounter any troubles.
A good 30 minutes were devoted to manually merge all pacnew files. I don't have the skills to merge the files using vim so my very unprofessional approach was this:

1. open up two root terminals
2. terminal 1: determine via vim what differences there are between pacnew and old file
3. terminal 2: using nano, manually add necessary lines into pacnew from the old config files
4. as root: example - 'mv /etc/rc.conf.pacnew /etc/rc.conf'
5. reboot and hope for the best.

And I guess I've learned my lesson today - don't wait weeks/months doing this because having to manually merge nearly 20 pacnew files is time consuming. Study the pacman output and merge when necessary after a pacman -Syu.

drag0nl0rd · 2008-06-20 15:03:42

new2arch wrote:

And I guess I've learned my lesson today - don't wait weeks/months doing this because having to manually merge nearly 20 pacnew files is time consuming. Study the pacman output and merge when necessary after a pacman -Syu.

If you have yaourt installed, try "yaourt -C" and if you know just the basic commands in vim, then the only new one for vimdiff (2 editing option under this yaourt command) is "ctrl+w w" for jump left/right in the compared documents. That's the way I get this deal done

new2arch · 2008-06-20 23:10:33

drag0nl0rd wrote:

new2arch wrote:
And I guess I've learned my lesson today - don't wait weeks/months doing this because having to manually merge nearly 20 pacnew files is time consuming. Study the pacman output and merge when necessary after a pacman -Syu.
If you have yaourt installed, try "yaourt -C" and if you know just the basic commands in vim, then the only new one for vimdiff (2 editing option under this yaourt command) is "ctrl+w w" for jump left/right in the compared documents. That's the way I get this deal done

Hm. I have to learn how to use vim properly. At the moment I only know ':quit!'. :-P
Thanks for the tip.

Arch Linux

#1 2008-06-19 18:21:38

[Solved] Updated filesystem and pacman info

#2 2008-06-19 18:36:09

Re: [Solved] Updated filesystem and pacman info

#3 2008-06-19 18:56:32

Re: [Solved] Updated filesystem and pacman info

#4 2008-06-19 19:14:07

Re: [Solved] Updated filesystem and pacman info

#5 2008-06-19 19:14:49

Re: [Solved] Updated filesystem and pacman info

#6 2008-06-19 19:26:49

Re: [Solved] Updated filesystem and pacman info

#7 2008-06-19 19:45:44

Re: [Solved] Updated filesystem and pacman info

#8 2008-06-19 20:46:13

Re: [Solved] Updated filesystem and pacman info

#9 2008-06-19 21:33:54

Re: [Solved] Updated filesystem and pacman info

#10 2008-06-20 02:56:23

Re: [Solved] Updated filesystem and pacman info

#11 2008-06-20 03:03:04

Re: [Solved] Updated filesystem and pacman info

#12 2008-06-20 09:09:24

Re: [Solved] Updated filesystem and pacman info

#13 2008-06-20 12:53:16

Re: [Solved] Updated filesystem and pacman info

#14 2008-06-20 13:47:53

Re: [Solved] Updated filesystem and pacman info

#15 2008-06-20 14:05:06

Re: [Solved] Updated filesystem and pacman info

#16 2008-06-20 15:03:42

Re: [Solved] Updated filesystem and pacman info

#17 2008-06-20 23:10:33

Re: [Solved] Updated filesystem and pacman info

Board footer