error: the following file conflicts were found:

dp · 2003-09-02 20:46:45

[root@Asteraceae damir]# uuuu
:: Synchronizing package databases...
 current.db.tar.gz        [####################################] 100% |     32K
 unofficial.db.tar.gz     [####################################] 100% |     61K
 unstable.db.tar.gz       [####################################] 100% |      2K
:: ed2k-gtk-gui-0.6.0-1: local version is newer
:: hotplug-2003_08_05-1: local version is newer
:: Above packages will be skipped.  To manually upgrade use 'pacman -S <pkg>'

Targets: pygtk-2.0.0-1 gnome-python-2.0.0-1 gtkhtml-3.0.8-1 libgpg-error-0.3-1
         libgcrypt-1.1.42-1

Proceed with upgrade? [Y/n]
loading package data... done.
checking for file conflicts...
error: the following file conflicts were found:
  usr: exists in "pygtk" (target) and "gnome-python" (target)
  usr/lib: exists in "pygtk" (target) and "gnome-python" (target)
  usr/lib/pkgconfig: exists in "pygtk" (target) and "gnome-python" (target)
  usr/lib/python2.3: exists in "pygtk" (target) and "gnome-python" (target)
  usr/lib/python2.3/site-packages: exists in "pygtk" (target) and "gnome-python" (target)
  usr/lib/python2.3/site-packages/gtk-2.0: exists in "pygtk" (target) and "gnome-python" (target)
  usr/share: exists in "pygtk" (target) and "gnome-python" (target)
  usr/share/pygtk: exists in "pygtk" (target) and "gnome-python" (target)
  usr/share/pygtk/2.0: exists in "pygtk" (target) and "gnome-python" (target)
  usr/share/pygtk/2.0/defs: exists in "pygtk" (target) and "gnome-python" (target)
  usr: exists in "pygtk" (target) and "libgpg-error" (target)
  usr/bin: exists in "pygtk" (target) and "libgpg-error" (target)
  usr/include: exists in "pygtk" (target) and "libgpg-error" (target)
  usr/lib: exists in "pygtk" (target) and "libgpg-error" (target)
  usr/share: exists in "pygtk" (target) and "libgpg-error" (target)
  usr: exists in "pygtk" (target) and "libgcrypt" (target)
  usr/bin: exists in "pygtk" (target) and "libgcrypt" (target)
  usr/include: exists in "pygtk" (target) and "libgcrypt" (target)
  usr/lib: exists in "pygtk" (target) and "libgcrypt" (target)
  usr/share: exists in "pygtk" (target) and "libgcrypt" (target)
  usr: exists in "gnome-python" (target) and "libgpg-error" (target)
  usr/lib: exists in "gnome-python" (target) and "libgpg-error" (target)
  usr/share: exists in "gnome-python" (target) and "libgpg-error" (target)
  usr: exists in "gnome-python" (target) and "libgcrypt" (target)
  usr/lib: exists in "gnome-python" (target) and "libgcrypt" (target)
  usr/share: exists in "gnome-python" (target) and "libgcrypt" (target)
  usr: exists in "libgpg-error" (target) and "libgcrypt" (target)
  usr/bin: exists in "libgpg-error" (target) and "libgcrypt" (target)
  usr/include: exists in "libgpg-error" (target) and "libgcrypt" (target)
  usr/lib: exists in "libgpg-error" (target) and "libgcrypt" (target)
  usr/share: exists in "libgpg-error" (target) and "libgcrypt" (target)
  usr/share/aclocal: exists in "libgpg-error" (target) and "libgcrypt" (target)

[root@Asteraceae damir]#

... are these the same files? what package should i first install? it's only me having this conflict? (use pacman2.6)

kritoke · 2003-09-02 21:00:45

I had a bit fewer conflicts than you, but today there definately were a bunch. I have nerves of steel, so I just did a pacman -Sfyu. I hope I didn't totally screw anything up by doing so, I really wonder how these conflicts came about. I had them before I upgraded to new pacman and afterwards. So I don't think thats the issue.

Kritoke

dp · 2003-09-02 21:03:10

it's for sure not pacman ... i had to upgrade another machine working on the old pacman, so i wanted to find out if ... but no, the same conflicts came

dp · 2003-09-02 21:06:44

why have pygtk and gnome-python the same files compiled with them?

maybe we should remove one copy from one of these packages --- if they are really the same ... so that no conflicts come up

someone who knows more about gnome-python should comment my post, please

orelien · 2003-09-02 21:15:31

If you look at the messages, you'll see pacman is only(!) complaining about directories, not files.
As a consequence, I don't think packages themselves are the root cause of these messages.
For now, a possible workaround would be to upgrade packages one by one...
We'll have a closer look at it ASAP.

Toth · 2003-09-02 21:46:54

Yeah, upgrading one by one worked fine for me. At first I thought it was because I have a custom gnome-python package for use with gdesklets. (Has to be built after installing pyorbit for gdesklets to work).

apeiro · 2003-09-03 02:23:39

I've found the bug in makepkg. It's from a recent change that produces the .FILELIST differently. The new method omits the necessary trailing slash on directory names.

This will be fixed in 2.6-3

sarah31 · 2003-09-03 02:49:29

and all the packages released with the new pacman are being rebuilt

dp · 2003-09-03 06:56:39

ok, the upgrade with the new pacman went smothly (i didnt force the upgrade when the conflicts came up ... just waited, and see: it is solved ... thank you)

Arch Linux

#1 2003-09-02 20:46:45

error: the following file conflicts were found:

#2 2003-09-02 21:00:45

Re: error: the following file conflicts were found:

#3 2003-09-02 21:03:10

Re: error: the following file conflicts were found:

#4 2003-09-02 21:06:44

Re: error: the following file conflicts were found:

#5 2003-09-02 21:15:31

Re: error: the following file conflicts were found:

#6 2003-09-02 21:46:54

Re: error: the following file conflicts were found:

#7 2003-09-03 02:23:39

Re: error: the following file conflicts were found:

#8 2003-09-03 02:49:29

Re: error: the following file conflicts were found:

#9 2003-09-03 06:56:39

Re: error: the following file conflicts were found:

Board footer