On Fri, Oct 18, 2002 at 09:23:19AM +0200, Sven Luther wrote:
Also notice that the s390 is not a released port, so it will not stop
your package from entering testing, so i would not worry too much about
this, just wait it out a bit.
Thes arches you have to wait for are :
alpha, arm, hppa,
On Thu, Oct 17, 2002 at 11:32:40PM +1000, Drew Parsons wrote:
On Thu, Oct 17, 2002 at 11:44:14AM +0200, Marco Kuhlmann wrote:
How do I force a rebuild on buildd?
And more to the point [ ;) ], how do I force the autobuilder maintainers to
actually upload my package once it has been
On Thu, Oct 17, 2002 at 11:05:59PM +0200, Stefan Schwandter wrote:
Drew Parsons wrote:
And more to the point [ ;) ], how do I force the autobuilder maintainers to
actually upload my package once it has been autobuilt?
The s390 version of xprint-xprintorg has been built for a whole week
On Thu, Oct 17, 2002 at 11:32:40PM +1000, Drew Parsons wrote:
On Thu, Oct 17, 2002 at 11:44:14AM +0200, Marco Kuhlmann wrote:
How do I force a rebuild on buildd?
And more to the point [ ;) ], how do I force the autobuilder maintainers to
actually upload my package once it has been
On Fri, Oct 18, 2002 at 09:23:19AM +0200, Sven Luther wrote:
Also notice that the s390 is not a released port, so it will not stop
your package from entering testing, so i would not worry too much about
this, just wait it out a bit.
Thes arches you have to wait for are :
alpha, arm, hppa,
On Fri, Oct 18, 2002 at 09:23:19AM +0200, Sven Luther wrote:
Also notice that the s390 is not a released port, so it will not stop
your package from entering testing, so i would not worry too much about
this, just wait it out a bit.
You might want to take a look at
On Fri, Oct 18, 2002 at 08:21:05AM +0100, Jonathan McDowell wrote:
On Fri, Oct 18, 2002 at 09:23:19AM +0200, Sven Luther wrote:
Also notice that the s390 is not a released port, so it will not stop
your package from entering testing, so i would not worry too much about
this, just wait it
On Thu, Oct 17, 2002 at 11:05:59PM +0200, Stefan Schwandter wrote:
Drew Parsons wrote:
And more to the point [ ;) ], how do I force the autobuilder maintainers to
actually upload my package once it has been autobuilt?
The s390 version of xprint-xprintorg has been built for a whole week
Dear mentors:
How do I force a rebuild on buildd? One of my package could not
be built due to a bug in debhelper which is now solved. Two of
the architectures have already built the package successfully now
that the new version is available; can I trigger the other
architectures to try a
Hi Marco!
You wrote:
How do I force a rebuild on buildd? One of my package could not
be built due to a bug in debhelper which is now solved. Two of
the architectures have already built the package successfully now
that the new version is available; can I trigger the other
architectures to
* Bas Zoetekouw [EMAIL PROTECTED] (2002-10-17 12:17:56 +0200):
If you uploaded a new package, the buildds will automagically
build it. I could take some time, though.
Sorry, I did not make myself clear: I did not upload a new
package -- I want to trigger a new build attempt for an old
package
On Thu, Oct 17, 2002 at 11:44:14AM +0200, Marco Kuhlmann wrote:
How do I force a rebuild on buildd?
And more to the point [ ;) ], how do I force the autobuilder maintainers to
actually upload my package once it has been autobuilt?
The s390 version of xprint-xprintorg has been built for a
On Thu, Oct 17, 2002 at 03:15:35PM +0200, Bas Zoetekouw wrote:
Hi Sven!
You wrote:
Sorry, I did not make myself clear: I did not upload a new
package -- I want to trigger a new build attempt for an old
package of mine now that debhelper has been fixed.
The autobuilder retry old
Drew Parsons wrote:
And more to the point [ ;) ], how do I force the autobuilder maintainers to
actually upload my package once it has been autobuilt?
The s390 version of xprint-xprintorg has been built for a whole week now[1],
but it still hasn't been uploaded to the archive[2]. All other
Dear mentors:
How do I force a rebuild on buildd? One of my package could not
be built due to a bug in debhelper which is now solved. Two of
the architectures have already built the package successfully now
that the new version is available; can I trigger the other
architectures to try a
Hi Marco!
You wrote:
How do I force a rebuild on buildd? One of my package could not
be built due to a bug in debhelper which is now solved. Two of
the architectures have already built the package successfully now
that the new version is available; can I trigger the other
architectures to
* Bas Zoetekouw [EMAIL PROTECTED] (2002-10-17 12:17:56 +0200):
If you uploaded a new package, the buildds will automagically
build it. I could take some time, though.
Sorry, I did not make myself clear: I did not upload a new
package -- I want to trigger a new build attempt for an old
package
On Thu, Oct 17, 2002 at 01:16:43PM +0200, Marco Kuhlmann wrote:
* Bas Zoetekouw [EMAIL PROTECTED] (2002-10-17 12:17:56 +0200):
If you uploaded a new package, the buildds will automagically
build it. I could take some time, though.
Sorry, I did not make myself clear: I did not upload a
On Don, 2002-10-17 at 13:40, Sven Luther wrote:
On Thu, Oct 17, 2002 at 01:16:43PM +0200, Marco Kuhlmann wrote:
* Bas Zoetekouw [EMAIL PROTECTED] (2002-10-17 12:17:56 +0200):
If you uploaded a new package, the buildds will automagically
build it. I could take some time, though.
Hi Sven!
You wrote:
Sorry, I did not make myself clear: I did not upload a new
package -- I want to trigger a new build attempt for an old
package of mine now that debhelper has been fixed.
The autobuilder retry old packages that failed on a regular basis, just
wait some time for them
On Thu, Oct 17, 2002 at 11:44:14AM +0200, Marco Kuhlmann wrote:
How do I force a rebuild on buildd?
And more to the point [ ;) ], how do I force the autobuilder maintainers to
actually upload my package once it has been autobuilt?
The s390 version of xprint-xprintorg has been built for a
On Thu, Oct 17, 2002 at 03:15:35PM +0200, Bas Zoetekouw wrote:
Hi Sven!
You wrote:
Sorry, I did not make myself clear: I did not upload a new
package -- I want to trigger a new build attempt for an old
package of mine now that debhelper has been fixed.
The autobuilder retry old
Drew Parsons wrote:
And more to the point [ ;) ], how do I force the autobuilder maintainers to
actually upload my package once it has been autobuilt?
The s390 version of xprint-xprintorg has been built for a whole week now[1],
but it still hasn't been uploaded to the archive[2]. All other
23 matches
Mail list logo
