Lucas Nussbaum writes:
> Hi,
>
>
> I only built packages according to their Architecture: field. I didn't
> consider the Packages-arch-specific list.
>
I see you have failed build logs for mozart, but from the control file:
Package: mozart
Architecture: hppa i386 m68k mipsel mips po
On 18/10/06 at 08:49 -0500, Kevin Glynn wrote:
> Lucas Nussbaum writes:
> > Hi,
> >
>
> >
> > I only built packages according to their Architecture: field. I didn't
> > consider the Packages-arch-specific list.
> >
>
> I see you have failed build logs for mozart, but from the control fil
On Wed, Oct 18, 2006, Frans Pop wrote:
> python-xml: Depends: python-central (>= 0.4.15) but it is not going
> to be installed
> I expect this is either a transient error or a bug in the python
> packaging. I would probably be good if someone could check for this
> globally.
(Dropping d-release; please CC d-boot as I'm not subscribed to d-qa.)
On Wednesday 18 October 2006 11:16, Lucas Nussbaum wrote:
> I built packages from main which where supposed to build on AMD64
> according to their Architecture: field in a etch AMD64 chroot. Using
> sbuild improved the situation
On 18/10/06 at 11:52 +0200, Thijs Kinkhorst wrote:
> On Wed, 2006-10-18 at 11:41 +0200, Andreas Barth wrote:
> > Actually, in a test it *might* be ok. Usually, even if they're bugs,
> > they're not RC.
> >
> > Access to a debian-mirror is necessary for some packages, but rather
> > on a exception-
On Wed, Oct 18, 2006 at 09:36:26AM +0200, Lucas Nussbaum wrote:
> > Nice. How much time would a complete archive rebuild take?
>
> The build of the 9716 source packages which I was able to build on AMD64
> took a total time of 790936s (9 days, 4 hours). So it should
> theoritically be possible to
On Wed, Oct 18, 2006, Lucas Nussbaum wrote:
> I'm not going to process all the logs, so feel free to pick up some of
> them and work on them. Maybe we should find a way to work together on
> this ? (like a list of packages on wiki.d.o or in a svn repos ?)
> Are there some wiki-like table edition to
On Wed, 2006-10-18 at 11:41 +0200, Andreas Barth wrote:
> Actually, in a test it *might* be ok. Usually, even if they're bugs,
> they're not RC.
>
> Access to a debian-mirror is necessary for some packages, but rather
> on a exception-basis - almost all packages need to build with the
> packages t
* Thijs Kinkhorst ([EMAIL PROTECTED]) [061018 11:34]:
> On Wed, 2006-10-18 at 11:16 +0200, Lucas Nussbaum wrote:
> > Internet access was not available from the nodes. Are build scripts
> > allowed to download files from the Internet during build ? Some perl
> > modules do this in their tests.
>
>
On Wed, 2006-10-18 at 11:16 +0200, Lucas Nussbaum wrote:
> Internet access was not available from the nodes. Are build scripts
> allowed to download files from the Internet during build ? Some perl
> modules do this in their tests.
No, this is definately a bug. I've indeed encountered it a couple
On 18/10/06 at 11:13 +0200, Filippo Giunchedi wrote:
> On Wed, Oct 18, 2006 at 09:36:26AM +0200, Lucas Nussbaum wrote:
> > > Nice. How much time would a complete archive rebuild take?
> >
> > The build of the 9716 source packages which I was able to build on AMD64
> > took a total time of 790936s
Hi,
I built packages from main which where supposed to build on AMD64
according to their Architecture: field in a etch AMD64 chroot. Using
sbuild improved the situation a lot compared to my first attempt[1].
However, 548 packages still fail to build.
[1] http://lists.debian.org/debian-qa/2006/10/
On 12/10/06 at 18:34 +0200, Romain Francoise wrote:
> Lucas Nussbaum <[EMAIL PROTECTED]> writes:
>
> > I started to work on a rebuild of all packages in etch inside an etch
> > environment. I used about 100 AMD64 nodes from the Grid'5000 project.
>
> Nice. How much time would a complete archive
On Thu, Oct 12, 2006 at 04:48:14PM +0200, Lucas Nussbaum wrote:
> Hi,
[snip, thanks for taking care of this!]
>
> Packages that failed to build:
> bluez-hcidump 1.31-1 TODO
this is already fixed in bluez-hcidump 1.32-1 FYI
filippo
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject
On Thu, Oct 12, 2006 at 06:34:10PM +0200, Romain Francoise wrote:
> Lucas Nussbaum <[EMAIL PROTECTED]> writes:
>
> > I started to work on a rebuild of all packages in etch inside an etch
> > environment. I used about 100 AMD64 nodes from the Grid'5000 project.
>
> Nice. How much time would a com
On 12/10/06 at 18:34 +0200, Romain Francoise wrote:
> Lucas Nussbaum <[EMAIL PROTECTED]> writes:
>
> > I started to work on a rebuild of all packages in etch inside an etch
> > environment. I used about 100 AMD64 nodes from the Grid'5000 project.
>
> Nice. How much time would a complete archive
Lucas Nussbaum <[EMAIL PROTECTED]> writes:
> I started to work on a rebuild of all packages in etch inside an etch
> environment. I used about 100 AMD64 nodes from the Grid'5000 project.
Nice. How much time would a complete archive rebuild take?
> Packages that failed to build: [...]
> Romain F
* Lucas Nussbaum <[EMAIL PROTECTED]> [2006-10-12 17:45]:
> Why wouldn't it make sense to rebuild contrib and non-free as well ?
Because they made depend on software that is not even packaged at all.
And not all non-free software necessary allows recompilation anyway.
--
Martin Michlmayr
http://ww
On 12/10/06 at 16:42 +0100, Martin Michlmayr wrote:
> * Lucas Nussbaum <[EMAIL PROTECTED]> [2006-10-12 17:35]:
> > - no non-free entries in sources.list, so packages which build-dep on
> > non-free packages don't build.
>
> Packages in main are not allowed to do that anyway, and it only makes
>
* Lucas Nussbaum <[EMAIL PROTECTED]> [2006-10-12 17:35]:
> - no non-free entries in sources.list, so packages which build-dep on
> non-free packages don't build.
Packages in main are not allowed to do that anyway, and it only makes
sense to re-build main.
--
Martin Michlmayr
http://www.cyrius.c
On 12/10/06 at 16:17 +0100, Martin Michlmayr wrote:
> * Christoph Berg <[EMAIL PROTECTED]> [2006-10-12 17:08]:
> > here's the list sorted by Maintainer:
>
> I don't think this is useful because it includes architecture specific
> packages. It's no wonder that e.g. linux-kernel-di-mips fails to
>
On Thu, Oct 12, 2006 at 04:48:14PM +0200, Lucas Nussbaum wrote:
> [...]
> Packages that failed to build:
This is the same list, but dd-list'ified for your browsing convenience:
Laszlo Boszormenyi (GCS) <[EMAIL PROTECTED]>
gradm2
Loic Dachary (OuoU) <[EMAIL PROTECTED]>
poker-network
Masayu
* Christoph Berg <[EMAIL PROTECTED]> [2006-10-12 17:08]:
> here's the list sorted by Maintainer:
I don't think this is useful because it includes architecture specific
packages. It's no wonder that e.g. linux-kernel-di-mips fails to
build on amd64 or i386... you really need to exclude those. It'
Hi,
here's the list sorted by Maintainer:
Laszlo Boszormenyi (GCS) <[EMAIL PROTECTED]>
gradm2
Loic Dachary (OuoU) <[EMAIL PROTECTED]>
poker-network
Masayuki Hatta (mhatta) <[EMAIL PROTECTED]>
gtktrain
Peter De Schrijver (p2) <[EMAIL PROTECTED]>
quik
Peter De Schrijver (p2) <[EMAIL
Hi,
I started to work on a rebuild of all packages in etch inside an etch
environment. I used about 100 AMD64 nodes from the Grid'5000 project.
Since I was using AMD64 nodes, I first thought I would be building on this
arch. However, after a first run, I had about 700 FTBFSing packages
(including
25 matches
Mail list logo
