> I've also opened bugs against the following packages which depend on > xpm4.7 and should be recompiled against xpm4: > olvwm xconq lyx > asmail asmixer afterstep > xisp xmcpustate xpdf > xephem-motif xwave xboard > fvwm-common xtar-smotif maelstrom > jdk1.1-dev xlockmore xmysql > fvwm freeciv wine > fvwm2 fvwm95 xsok > xpat2 xsoldier ctwm > pixmap xmailbox ascd > tkstep42 gwm xbmbrowser > xtar-dmotif nedit-smotif xgalaga > jdk1.1-runtime xfaces ascdc > xbanner xtron wmaker > asmodem mctools-lite netscape3 > nedit-dmotif xscreensaver netscape4 I am wondering if it is really a bug for packages such as netscape3, netscape4, and jdk1.1-* to have a dependency against xpm4.7? They contain binary files (against libc5) that we can't recompile. I mean, dpkg should be able to resolve the dependencies with xpm4 (since it provides xpm4.7) - but it has a problem. Otherwise, anybody running 'stable' who wants the netscape or the jdk packages is going to try to grab them out of 'unstable', and screw up there system. I think a better approach might be to fix dpkg and xpm4 so that xpm4 can resolve the versioned dependencies. BTW, I'll edit the binaries in the jdk1.1-* packages so they'll work on a libc6 system. The binaries in the netscape4 package seem to be ok. > I've also opened bugs against these packages which are linked with -r. > (and break on a libc6 system). > emacs fvwm2 fvwm-common xdaliclock suffers from this too (I submitted a bug). Cheers, - Jim
Attachment:
pgp01yXTPsQT6.pgp
Description: PGP signature