Gtkmm 2.6.x requires libatk 1.9.x/1.10.x, which is only in experimental at this time.
-Brad > -----Original Message----- > From: Philipp Kern [mailto:[EMAIL PROTECTED] > Sent: Friday, May 20, 2005 3:46 AM > To: Debian Bug Tracking System > Subject: Bug#309901: upload 2.6.x to unstable > > Package: gtkmm2.4 > Severity: wishlist > > Gtkmm 2.6.x should be uploaded to unstable. If it doesn't maintain > binary compatibility it should go in with an increased SONAME. Otherwise > I cannot see what Gtkmm 2.6 holds off from entering unstable as it is > backwards-compatible to 2.4, apart from the coming Sarge release. However > Sarge is now frozen and soon to be released, so one could upload to > unstable again. > > It was quite a long time in experimental, I successfully built my > 2.6-dependent package against it and I want it to enter Debian soon, but > first the newer version has to enter unstable. > > Kind regards, > Philipp Kern > Debian Developer -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
