Wouter Verhelst [EMAIL PROTECTED] writes:
On Mon, Jul 17, 2006 at 02:40:28PM -0400, Joe Smith wrote:
Wouter Verhelst [EMAIL PROTECTED] wrote in message
There is no such general solution. See
http://www.debian.org/devel/buildd/wanna-build-states#not-for-us
That says:
However, wanna-build
Wouter Verhelst [EMAIL PROTECTED] writes:
On Mon, Jul 17, 2006 at 05:53:25AM +0200, Goswin von Brederlow wrote:
The buildd package could just be a central hub where two or three
knowlegable people sift through the bug reports and then distribute it
to the affected/responsible person.
Who
On Tue, Jul 18, 2006 at 09:56:22AM +0200, Goswin von Brederlow wrote:
Two things:
- control files are part of the source. w-b would have to download and
unpack every source package to get that file.
Exactly.
- control files can be auto generated during build (e.g. glibc) and
might not
Wouter Verhelst [EMAIL PROTECTED] writes:
On Tue, Jul 18, 2006 at 09:56:22AM +0200, Goswin von Brederlow wrote:
Two things:
- control files are part of the source. w-b would have to download and
unpack every source package to get that file.
Exactly.
- control files can be auto generated
On Mon, Jul 17, 2006 at 05:53:25AM +0200, Goswin von Brederlow wrote:
The buildd package could just be a central hub where two or three
knowlegable people sift through the bug reports and then distribute it
to the affected/responsible person.
Who would you suggest would do that? I know it's
Wouter Verhelst [EMAIL PROTECTED] wrote in message
news:[EMAIL PROTECTED]
On Sat, Jul 15, 2006 at 10:55:32PM +0200, Ludovic Brenta wrote:
Where should I ask for help? Neither buildd.debian.org nor
www.debian.org/devel/buildd, mention where the buildd admins can be
reached; and
On Mon, Jul 17, 2006 at 02:40:28PM -0400, Joe Smith wrote:
Wouter Verhelst [EMAIL PROTECTED] wrote in message
There is no such general solution. See
http://www.debian.org/devel/buildd/wanna-build-states#not-for-us
That says:
However, wanna-build does not look at the control file of a
On Sat, Jul 15, 2006 at 10:55:32PM +0200, Ludovic Brenta wrote:
I will upload ~20 source packages in the next few weeks, adding
support for more architectures to each package. So I'm really looking
for a general solution and not one that only applies to asis.
Why aren't those packages
On Sat, Jul 15, 2006 at 10:55:32PM +0200, Ludovic Brenta wrote:
Where should I ask for help? Neither buildd.debian.org nor
www.debian.org/devel/buildd, mention where the buildd admins can be
reached; and lists.debian.org does not have a buildd@ list.
[EMAIL PROTECTED]. I just committed a
Wouter Verhelst [EMAIL PROTECTED] writes:
On Sat, Jul 15, 2006 at 10:55:32PM +0200, Ludovic Brenta wrote:
Where should I ask for help? Neither buildd.debian.org nor
www.debian.org/devel/buildd, mention where the buildd admins can be
reached; and lists.debian.org does not have a buildd@ list.
On Sun, Jul 16, 2006 at 06:31:56PM +0200, Ludovic Brenta wrote:
Wouter Verhelst [EMAIL PROTECTED] writes:
On Sat, Jul 15, 2006 at 10:55:32PM +0200, Ludovic Brenta wrote:
Where should I ask for help? Neither buildd.debian.org nor
www.debian.org/devel/buildd, mention where the buildd admins
Wouter Verhelst [EMAIL PROTECTED] writes:
On Sun, Jul 16, 2006 at 06:31:56PM +0200, Ludovic Brenta wrote:
Also, I would propose that a list, [EMAIL PROTECTED], or even better, a
pseudo-package, buildd, be created for such issues. buildd would
complement ftp.debian.org as a central place for
Hello,
Package asis (=3.15p-10) supports i386, kfreebsd-i386, sparc, and
powerpc.
I uploaded the next version (=2005-3) a couple of days ago. It adds
support for more architectures, namely: amd63, hppa, and ia64.
I notice that the buildds have successfully built the powerpc and
sparc packages,
Ludovic Brenta wrote:
Hello,
Hi Ludovic
Package asis (=3.15p-10) supports i386, kfreebsd-i386, sparc, and
powerpc.
I uploaded the next version (=2005-3) a couple of days ago. It adds
support for more architectures, namely: amd63, hppa, and ia64.
You should contact the buildd maintainers
14 matches
Mail list logo
