Re: Successfully built packages said to be "out of date on m68k"

2003-12-23 Thread Florent Rougon
Mark Brown <[EMAIL PROTECTED]> wrote: > Check the archive to see if the package has actually been uploaded for > m68k - the buildd web page reports the build when it happens but the > changes file still needs to be signed before the package is uploaded. You guessed right, it seems: I looked in th

Re: Successfully built packages said to be "out of date on m68k"

2003-12-23 Thread Florent Rougon
Mark Brown <[EMAIL PROTECTED]> wrote: > Check the archive to see if the package has actually been uploaded for > m68k - the buildd web page reports the build when it happens but the > changes file still needs to be signed before the package is uploaded. You guessed right, it seems: I looked in th

Re: Successfully built packages said to be "out of date on m68k"

2003-12-23 Thread Mark Brown
On Tue, Dec 23, 2003 at 05:59:53PM +0100, Florent Rougon wrote: > which I don't understand since the m68k build log (as well as those for > all other architectures) looks OK : Check the archive to see if the package has actually been uploaded for m68k - the buildd web page reports the build when

Successfully built packages said to be "out of date on m68k"

2003-12-23 Thread Florent Rougon
Hi, My packages python2.{1,2,3}-xmms are not entering testing although they have met (as far as I can see) all the required conditions for four days now. The reason invoked on http://packages.qa.debian.org/p/pyxmms.html is : out of date on m68k: python2.1-xmms, python2.2-xmms, python2.3-xmms

Re: Successfully built packages said to be "out of date on m68k"

2003-12-23 Thread Mark Brown
On Tue, Dec 23, 2003 at 05:59:53PM +0100, Florent Rougon wrote: > which I don't understand since the m68k build log (as well as those for > all other architectures) looks OK : Check the archive to see if the package has actually been uploaded for m68k - the buildd web page reports the build when

Successfully built packages said to be "out of date on m68k"

2003-12-23 Thread Florent Rougon
Hi, My packages python2.{1,2,3}-xmms are not entering testing although they have met (as far as I can see) all the required conditions for four days now. The reason invoked on http://packages.qa.debian.org/p/pyxmms.html is : out of date on m68k: python2.1-xmms, python2.2-xmms, python2.3-xmms