On Wed, Oct 12, 2005 at 12:30:31AM -0700, Steve Langasek wrote: > On Wed, Oct 12, 2005 at 03:53:18PM +0930, Ron wrote: > > Package: gdk-imlib1 > > Version: 1.9.14-22 > > Severity: critical > > Justification: breaks unrelated software > > > Unless there is something big I am missing, > > Yes, there is. The old gdk-imlib1 depends on libpng2, and there are many > existing binaries, both in the archive and outside it, which depend directly > on both gdk-imlib1 and libpng2. The Conflicts is present to ensure that > users do not install combinations of packages on their systems that will > result in unusable, segfaulting applications, while allowing continued > installability of packages which depend on gdk-imlib1 without depending on > libpng2.
I'm aware of the trouble with mixing png versions (it's why wx2.4 reverted to libpng2/10 a couple of releases ago), but this still seems like a strange place to hammer this nail from to me. Why does png3/12 not declare this conflict now and let gdk-imlib dependency on it do the rest? > > gdk-imlib should certainly not take it upon itself to force the removal of > > libpng2 and all its dependencies... > > It doesn't. You're not forced to remove libpng2, you just don't get to keep > libpng2 *and* upgrade gdk-imlib1. Well... it makes me glad I have nothing that directly depends on gdk-imlib1, or my build machine would be losing tools I use while this shakes out -- a situation that could have made timely updates of my packages to suit a much more trying (and time consuming) proposition. > > Josselin: I see from #323354 that you are planning to kill > > off libpng2 soon in any case. > > libpng2 is already gone from unstable. Yes, I saw that was the case just after I fired this off. > Any packages still depending on > libpng2 need to be rebuilt with libpng3 (libpng12-0) to be released with > etch. Ack. I'll try to crank the handle for new wx2.4 packages tonight or tomorrow then. > > Where does this leave apps that still depend on gtk1? Will it be rebuilt > > to use png3, or something else? > > These packages are already being rebuilt to use png3. This is why > gdk-imlib1 has this conflict. I'm still not sure I see how the latter automatically follows from the former, but the song remains the same. I knew this was coming, but if there was a note about it coming _now_, I must have missed it. I can't say I'll be _unhappy_ to stop having to flip between the two png-dev packages, depending on what I'm building for upload, but I'm still missing something if this is the only/best way to make this transition. Done now though, so I guess I'll make the best of it... cheers, Ron -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
