[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

cleanup of incorrect update-alternatives handling



Hi,

I've now cleaned up most of the incorrect alternatives handling in
wheezy and squeeze->wheezy updates, and most of these fixes have already
migrated to wheezy or are unblocked. Thanks for this!

There are a few packages left that cannot be fixed via unstable, a fix
would have to go via TPU - should I try this?

tucnak2 #668442
  (fixed in unstable, but unstable has a new upstream release,
   that does FTBFS on everything but the maintainers machine)
0m28.6s ERROR: WARN: Broken symlinks:
  /usr/bin/tucnak2 -> /etc/alternatives/tucnak
  /etc/alternatives/tucnak -> /usr/bin/tucnak
(does not remove the alternative on package removal)

fonts-vlgothic #699905
  (not fixed in unstable, patch available
   unstable has new upstream release)
0m54.7s INFO: Warning: Package purging left files on system:
  /etc/alternatives/ttf-japanese-gothic.ttf ->
/usr/share/fonts/truetype/vlgothic/VL-Gothic-Regular.ttf	 not owned
  /usr/share/fonts/	 owned by: fonts-vlgothic
  /usr/share/fonts/truetype/	 owned by: fonts-vlgothic
  /usr/share/fonts/truetype/ttf-japanese-gothic.ttf ->
/etc/alternatives/ttf-japanese-gothic.ttf	 not owned
(does not clean up obsolete alternatives on upgrades from squeeze)

and of course openjdk-6-jre #685185
1m37.1s INFO: Warning: Package purging left files on system:
  /etc/alternatives/javaws ->
/usr/lib/jvm/java-6-openjdk/jre/bin/javaws	 not owned
  /etc/alternatives/javaws.1.gz ->
/usr/lib/jvm/java-6-openjdk/jre/man/man1/javaws.1.gz	 not owned
  /etc/alternatives/pluginappletviewer ->
/usr/lib/jvm/java-6-openjdk/jre/bin/pluginappletviewer	 not owned
  /usr/bin/javaws -> /etc/alternatives/javaws	 not owned
  /usr/bin/pluginappletviewer -> /etc/alternatives/pluginappletviewer	
not owned
  /usr/share/man/man1/javaws.1.gz -> /etc/alternatives/javaws.1.gz	 not
owned
(does not clean up obsolete alternatives on upgrades from squeeze)
A patch is attached to the bug, I verified that this works properly, but
there is no way that I'd NMU/TPU this package :-)
That needs to be done by the maintainers.
More than 300 packages seem to be affected by this on squeeze->wheezy
updates, making it hard to spot packages that hav ebad alternatives
handling on their own.
But I'm afraid that still does not qualify to raise the severity to RC -
or is leaving broken symlinks in /usr/bin RC?


Andreas


Reply to: