[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Needs-Build: 4833



Hi!

After doing or during the upgrade of Elgar I used the long waiting periods to have a look at buildd.net. It's amazing how much is breaking when you don't care about the code for 4 years.... ;-)

Anyway, we're up to 4833 packages in Needs-Build:

  wanna-build statistics - Mon Nov 12 06:51:13 CET 2012
  -----------------------------------------------------

Distribution unstable:
---------------------
Installed       :  1321
Needs-Build     :  4833
Building        :     0
Uploaded        :     0
Failed          :     0
Dep-Wait        :     0
Reupload-Wait   :     0
Install-Wait    :     0
Failed-Removed  :     0
Dep-Wait-Removed:     0
Not-For-Us      :     0
total           :  9906

 13.34% (1321) up-to-date,  13.34% (1321) including uploaded
 48.79% (4833) need building
  0.00% (  0) currently building
  0.00% (  0) failed/dep-wait
  0.00% (  0) old failed/dep-wait
  0.00% (  0) need porting or cause the buildd serious grief

That's a lot.

It's even as many packages in needs-build then the whole archive consists of in 2005:

1124103487 5439 191 105 10 123 52 0 0 4 0 25 5949

So, on Aug. 15 2008 we had 5949 packages in the archive, now we have to build 4833 out of 9906. It's obvious that m68k will be never again uptodate with unstable with 10.000 packages. So we have to reduce the number of packages, let's say, to 4000 packages maybe.

Anyway, I'm looking for a HowTo to setup a buildd. I found https://buildd.debian.org/docs/buildd-setup.txt and it differs a little bit from what we have used in the past. For example it seems that schroot is now preferred over (d)chroot and LVM snapshots are now supported. Can someone please comment if that URI is correct? Of course we need to adopt changes for debian-ports.org.

--
Ciao...          //    Fon: 0381-2744150
.     Ingo     \X/     http://blog.windfluechter.net

gpg pubkey: http://www.juergensmann.de/ij_public_key.


Reply to: