Why does upgrade not work without problems anymore?

Trac3R · 2008-12-05 13:17:56

It's not the first time in the last two months:

# pacman -Syu

...

Proceed with installation? [Y/n] 
checking package integrity...
(43/43) checking for file conflicts                 [#####################] 100%
error: could not prepare transaction
error: failed to commit transaction (conflicting files)
poppler: /usr/bin/pdffonts exists in filesystem
poppler: /usr/bin/pdfimages exists in filesystem
poppler: /usr/bin/pdfinfo exists in filesystem
poppler: /usr/bin/pdftoabw exists in filesystem
poppler: /usr/bin/pdftohtml exists in filesystem
poppler: /usr/bin/pdftoppm exists in filesystem
poppler: /usr/bin/pdftops exists in filesystem
poppler: /usr/bin/pdftotext exists in filesystem
poppler: /usr/include/poppler/Annot.h exists in filesystem
poppler: /usr/include/poppler/Array.h exists in filesystem
poppler: /usr/include/poppler/BaseFile.h exists in filesystem

...

poppler: /usr/lib/libpoppler.so exists in filesystem
poppler: /usr/lib/libpoppler.so.4 exists in filesystem
poppler: /usr/lib/libpoppler.so.4.0.0 exists in filesystem
poppler: /usr/lib/pkgconfig/poppler-cairo.pc exists in filesystem
poppler: /usr/lib/pkgconfig/poppler-splash.pc exists in filesystem
poppler: /usr/lib/pkgconfig/poppler.pc exists in filesystem
poppler: /usr/share/licenses/poppler/COPYING exists in filesystem
poppler: /usr/share/man/man1/pdffonts.1.gz exists in filesystem
poppler: /usr/share/man/man1/pdfimages.1.gz exists in filesystem
poppler: /usr/share/man/man1/pdfinfo.1.gz exists in filesystem
poppler: /usr/share/man/man1/pdftohtml.1.gz exists in filesystem
poppler: /usr/share/man/man1/pdftoppm.1.gz exists in filesystem
poppler: /usr/share/man/man1/pdftops.1.gz exists in filesystem
poppler: /usr/share/man/man1/pdftotext.1.gz exists in filesystem
poppler: /usr/share/poppler/cMap/Adobe-CNS1/Adobe-CNS1-0 exists in filesystem
poppler: /usr/share/poppler/cMap/Adobe-CNS1/Adobe-CNS1-1 exists in filesystem

...

jre: /etc/profile.d/jre.sh exists in filesystem
jre: /opt/java/jre/COPYRIGHT exists in filesystem
jre: /opt/java/jre/LICENSE exists in filesystem
jre: /opt/java/jre/README exists in filesystem
jre: /opt/java/jre/THIRDPARTYLICENSEREADME.txt exists in filesystem
jre: /opt/java/jre/Welcome.html exists in filesystem
jre: /opt/java/jre/bin/ControlPanel exists in filesystem
jre: /opt/java/jre/bin/java exists in filesystem
jre: /opt/java/jre/bin/java_vm exists in filesystem
jre: /opt/java/jre/bin/javaws exists in filesystem
jre: /opt/java/jre/bin/jcontrol exists in filesystem
jre: /opt/java/jre/bin/keytool exists in filesystem
jre: /opt/java/jre/bin/orbd exists in filesystem
jre: /opt/java/jre/bin/pack200 exists in filesystem
jre: /opt/java/jre/bin/policytool exists in filesystem
jre: /opt/java/jre/bin/rmid exists in filesystem
jre: /opt/java/jre/bin/rmiregistry exists in filesystem
jre: /opt/java/jre/bin/servertool exists in filesystem
jre: /opt/java/jre/bin/tnameserv exists in filesystem
jre: /opt/java/jre/bin/unpack200 exists in filesystem
jre: /opt/java/jre/javaws/javaws exists in filesystem
jre: /opt/java/jre/lib/audio/soundbank.gm exists in filesystem
jre: /opt/java/jre/lib/calendars.properties exists in filesystem

...

jre: /opt/java/jre/man/ja exists in filesystem
jre: /opt/java/jre/man/ja_JP.eucJP/man1/java.1 exists in filesystem
jre: /opt/java/jre/man/ja_JP.eucJP/man1/javaws.1 exists in filesystem

...

jre: /usr/lib/mozilla/plugins/libjavaplugin_oji.so exists in filesystem
Errors occurred, no packages were upgraded.

Of course, I could use --force or deinstall poppler, jre & co. with dependencies and reinstall it after other packages were upgraded. I will do so, anyway. But seriously, with upgrades this files do exist in filesystem, of course the do. And this can't be the standard way with virtually every upgrade. Is there a pacman issue I haven't found here? Is there another workaround?

Regards

Zariel · 2008-12-05 13:25:57

what did you upgrade?

Allan · 2008-12-05 13:26:22

For some reason it appears poppler and jre package details are lost from from your pacman database. When you had this previously, was it complete packages also?

Trac3R · 2008-12-05 13:34:11

The upgrade packages:

Targets (43): automake-1.10.2-1  xcb-util-0.3.1-1  cairo-1.8.4-1  dbus-core-1.2.4-1  dbus-1.2.4-1  libspectre-0.2.2-1  
              glib2-2.18.3-1  pango-1.22.3-1  gtk2-2.14.5-1  poppler-0.10.1-1  poppler-glib-0.10.1-1  evince-2.24.2-1  
              fftw-3.2-1  gpgme-1.1.7-2  imlib2-1.4.2-2  intltool-0.40.5-1  jre-6u11-1  kernel26-2.6.27.7-1  
              latex2html-2008-1  libdrm-2.3.1-2  libsoup-2.24.2.1-1  libv4l-0.5.7-1  libwnck-2.24.2-1  man-pages-3.14-1  
              xkeyboard-config-1.4-1  libpciaccess-0.10.5-1  xf86-input-evdev-2.0.7-1  xorg-server-1.5.3-2  
              nvidia-96xx-utils-96.43.09-1  mesa-7.2-1  nvidia-96xx-96.43.09-1  p7zip-4.61-1  pciutils-3.0.3-1  
              policykit-0.9-7  poppler-qt-0.10.1-1  tdb-3.2.5-1  smbclient-3.2.5-1  vlc-0.9.8-1  wavpack-4.50.1-1  
              xf86-video-nv-2.1.12-1  xf86-video-vesa-2.0.0-2  xproto-7.0.14-1  xvidcore-1.2.0-1

The last time it was also poppler. I haven't installed jre for so long time (2 or 3 weeks?), so it's the first time it has happened with it. Do you mean this with complete packages?

Last edited by Trac3R (2008-12-05 13:34:44)

Allan · 2008-12-05 13:52:57

No, I meant it seems to be every file in poppler and jre that has been lost by pacman. I.e the complete package is lost, not just a single file. This is quite unusual...

Trac3R · 2008-12-05 14:00:52

Yes, with poppler it were also so many files of the package.
BTW: -Sc has no infuence on pacmans database?

Last edited by Trac3R (2008-12-05 14:05:30)

Allan · 2008-12-05 14:08:10

-Sc does not touch the installed files database.

I would use "pacman -Sf" for just poppler and jre to fix this. Hopefully, it will not happen with the same packages again and you will eventually fill in any other missing entries in your database.

Trac3R · 2008-12-05 14:15:31

I have done so, already. I just wonder why this happens so often. How can I find out what For some reason could be? How can I test it, is there an open bug report?

Last edited by Trac3R (2008-12-05 14:15:44)

Arch Linux

#1 2008-12-05 13:17:56

Why does upgrade not work without problems anymore?

#2 2008-12-05 13:25:57

Re: Why does upgrade not work without problems anymore?

#3 2008-12-05 13:26:22

Re: Why does upgrade not work without problems anymore?

#4 2008-12-05 13:34:11

Re: Why does upgrade not work without problems anymore?

#5 2008-12-05 13:52:57

Re: Why does upgrade not work without problems anymore?

#6 2008-12-05 14:00:52

Re: Why does upgrade not work without problems anymore?

#7 2008-12-05 14:08:10

Re: Why does upgrade not work without problems anymore?

#8 2008-12-05 14:15:31

Re: Why does upgrade not work without problems anymore?

Board footer