Mike Schacht wrote:
This list of debian machines: http://db.debian.org/machines.cgi, shows
that some of the machines allow access by all. There is no further
explanation of who qualifies as all, or how someone who is all can
get access.
The debian-admin list is given at the Admin contact
Mike Schacht wrote:
This list of debian machines: http://db.debian.org/machines.cgi, shows
that some of the machines allow access by all. There is no further
explanation of who qualifies as all, or how someone who is all can
get access.
The debian-admin list is given at the Admin contact
On Tue, May 27, 2003 at 07:09:56PM -0500, Mike Schacht wrote:
On Tue, May 27, 2003 at 09:24:28PM +0200, Adam Borowski wrote:
Another option is to use the compile farm at SourceForge. This is a bit
more tricky, as you would have to be registered as a participant of one of
project
On Tue, May 27, 2003 at 07:21:57PM -0500, Mike Schacht wrote:
On Tue, May 27, 2003 at 05:25:48PM -0300, Leo Costela Antunes wrote:
[...]
If so, the build logs[1] should give you more then enough help to track
your problems down before asking for another upload, and therefore
triggering another
On Tue, May 27, 2003 at 07:21:57PM -0500, Mike Schacht wrote:
On Tue, May 27, 2003 at 05:25:48PM -0300, Leo Costela Antunes wrote:
[...]
If so, the build logs[1] should give you more then enough help to track
your problems down before asking for another upload, and therefore
triggering another
On Tue, May 27, 2003 at 07:09:56PM -0500, Mike Schacht wrote:
On Tue, May 27, 2003 at 09:24:28PM +0200, Adam Borowski wrote:
Another option is to use the compile farm at SourceForge. This is a bit
more tricky, as you would have to be registered as a participant of one of
project
On Wed, May 28, 2003 at 08:39:08AM +0200, Andreas Metzler wrote:
Using ./configure -options ... || cat config.log in debian/rules was
suggested recently and could help a lot.
That's brilliant! And if configure works it doesn't even fill the build
logs with trash. Lovely. Done.
BTW what
The buildd-logs[1] don't provide enough debug information?
I know this doesn't answer your question, but I assume the portability
issues you mention are all build problems in one of Debian's supported
architectures, am I right?
If so, the build logs[1] should give you more then enough help to
Hi,
Leo Costela Antunes wrote:
The buildd-logs[1] don't provide enough debug information?
In this case not.
In many other cases also not...
Regards,
Rene
--
.''`. René Engelhard -- Debian GNU/Linux Developer
: :' : http://www.debian.org | http://people.debian.org/~rene/
`. `' [EMAIL
On Tue, May 27, 2003 at 12:25:37PM -0400, Joey Hess wrote:
Mike Schacht wrote:
I am not an official debian developer, but I maintain a couple of
packages. One of them, kdirstat, is already in the official
distribution. I intend to apply as a NM soon, but in the meantime,
since the last
On Tue, 27 May 2003, Sven Luther wrote:
On Tue, May 27, 2003 at 12:25:37PM -0400, Joey Hess wrote:
Mike Schacht wrote:
I am not an official debian developer, but I maintain a couple of
packages. One of them, kdirstat, is already in the official
distribution. I intend to apply as a NM
On Tue, May 27, 2003 at 12:25:37PM -0400, Joey Hess wrote:
This list of debian machines: http://db.debian.org/machines.cgi, shows
that some of the machines allow access by all. There is no further
explanation of who qualifies as all, or how someone who is all can
get access.
all =
On Tue, May 27, 2003 at 09:24:28PM +0200, Adam Borowski wrote:
Another option is to use the compile farm at SourceForge. This is a bit
more tricky, as you would have to be registered as a participant of one of
project hosted there, but that is not a big problem.
Ah, now I wonder about
On Tue, May 27, 2003 at 05:25:48PM -0300, Leo Costela Antunes wrote:
The buildd-logs[1] don't provide enough debug information?
I know this doesn't answer your question, but I assume the portability
issues you mention are all build problems in one of Debian's supported
architectures, am I
Hello,
I am not an official debian developer, but I maintain a couple of
packages. One of them, kdirstat, is already in the official
distribution. I intend to apply as a NM soon, but in the meantime,
since the last update of kdirstat, I am having portability problems. I
have no resources for
The buildd-logs[1] don't provide enough debug information?
I know this doesn't answer your question, but I assume the portability
issues you mention are all build problems in one of Debian's supported
architectures, am I right?
If so, the build logs[1] should give you more then enough help to
Mike Schacht wrote:
I am not an official debian developer, but I maintain a couple of
packages. One of them, kdirstat, is already in the official
distribution. I intend to apply as a NM soon, but in the meantime,
since the last update of kdirstat, I am having portability problems. I
have
Hi,
Leo Costela Antunes wrote:
The buildd-logs[1] don't provide enough debug information?
In this case not.
In many other cases also not...
Regards,
Rene
--
.''`. René Engelhard -- Debian GNU/Linux Developer
: :' : http://www.debian.org | http://people.debian.org/~rene/
`. `' [EMAIL
On Tue, May 27, 2003 at 12:25:37PM -0400, Joey Hess wrote:
Mike Schacht wrote:
I am not an official debian developer, but I maintain a couple of
packages. One of them, kdirstat, is already in the official
distribution. I intend to apply as a NM soon, but in the meantime,
since the last
On Tue, 27 May 2003, Sven Luther wrote:
On Tue, May 27, 2003 at 12:25:37PM -0400, Joey Hess wrote:
Mike Schacht wrote:
I am not an official debian developer, but I maintain a couple of
packages. One of them, kdirstat, is already in the official
distribution. I intend to apply as a NM
On Tue, May 27, 2003 at 12:25:37PM -0400, Joey Hess wrote:
This list of debian machines: http://db.debian.org/machines.cgi, shows
that some of the machines allow access by all. There is no further
explanation of who qualifies as all, or how someone who is all can
get access.
all =
On Tue, May 27, 2003 at 09:24:28PM +0200, Adam Borowski wrote:
Another option is to use the compile farm at SourceForge. This is a bit
more tricky, as you would have to be registered as a participant of one of
project hosted there, but that is not a big problem.
Ah, now I wonder about
On Tue, May 27, 2003 at 05:25:48PM -0300, Leo Costela Antunes wrote:
The buildd-logs[1] don't provide enough debug information?
I know this doesn't answer your question, but I assume the portability
issues you mention are all build problems in one of Debian's supported
architectures, am I
23 matches
Mail list logo
