From: Jeremy H. <fi...@hi...> - 2004-02-29 12:08:17
|
It's not hard! I was firstly curious why the packages weren't compliant with the python policy, and then I found out that the package I had put into 10.3/unstable had been removed and replaced with an obsolete and uncompliant version!!! In the meantime, I'll just move the packages from 10.2-gcc3.3 to 10.3... On 29 Feb 2004, at 16:42, Ben Hines wrote: > Um.. this all started with me asking you to move everything to > 10.3/stable. I don't see why its so hard. I'll just do it. > > -Ben > > On Feb 28, 2004, at 7:14 PM, Jeremy Higgs wrote: > >> >> Hmmm... well that is a bit of a kludge, but it's an old version. >> 10.2-gcc3.3 has newer (compliant, I hope) versions. Who knows why I >> didn't transfer them across.. >> >> Looking back in the CVS commits, gnome-python-1.4.2-1.info was >> removed in late October last year (27/10, my time)... >> gnome-python-py23 was also added on the 3rd November to the 10.3 tree >> by Ben Hines, and I've edited it a couple of times since then. >> gnome-python-py23 was removed from 10.3/unstable by Keith Konger on >> the 10/1/04 with the GNOME 2.4.2 commit... I don't know why, though, >> you'd have to ask him. >> >> Anyway, should I move gnome-python-py2* back to 10.3/unstable, and >> remove the obsolete package? > |