Le Mon, 1 Aug 2011 19:22:45 +0200, Helge Kreutzmann <deb...@helgefjell.de> a écrit :
> Hello Laurent, Hi, > On Sun, Jul 31, 2011 at 09:25:56PM +0200, Laurent Bigonville wrote: > > > Well that pretty annoying. Do you think you could create a patch to > > fix this in the unstable version? The API has minimal changes and > > that shouldn't be to complicated. Otherwise the release will remove > > it from testing to allow the transition of libnotify. > > I'd rather fix this in one step. Do you know any reason why 629566 > can't be resolved? Unfortunately they (you? see below) do not respond > to the bug report, and currently I cannot mail them directly (582765). > Well uploading brasero 3 requires other packages to be uploaded in unstable first (mainly nautilus) and would requires all packages using libbrasero-media to be updated to gtk3. So that's not that easy. > Of course I could see if I could do an upload "just" fixing your > transition, but it's not like I'm bored and do not have anything else > to do. And if I knew a reason/timeframe for the libbrasero-media3-dev > upload, then I could of course adjust. But I would not be very happy > to do the extra work for an upload fixing the libnotify transition > alone just to find out two days later that libbrasero-media3-dev was > uploaded. And especially given that both libnotify *and* > libbrasero-media3-dev have the same maintainer I find it somewhat > strange that the intermix (which I denoted by the proper blocks in the > BTS) cannot be resolved! (And not even a simple ack to my bug report > almost 2 month ago is possible). That's the game of the soname transition, the release team try to make a transition at a time, to avoid to much contention.. And as said, brasero 3 requires a lot of new libraries from GNOME3 and some of them also require transitions that's why the upload of GNOME 3 in unstable is slow. > And removing goobox from unstable would punish the wrong guy/would be > quite discouraging. I uploaded to experimental the same day you > reported the transition (btw. without a set timeframe), i.e. it's not > like I'm not responsive. I even talked with my previous sponsor about > this bug before I went on vacation some weeks ago, in case something > was happening with 629566. Well the the removal of a package from testing is in release team hands, so I cannot speak for them, but the best to ensure that the package stay in testing is to patch it to use the new API of libnotify. If you need help for the patch feel free to ask on the #debian-gnome on OTFC irc network, or I'll see if I can have a look at it. Regards Laurent Bigonville -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
