Re: Buildds still not picking up new architectures, why?
On Sat, Aug 12, 2006 at 11:08:10AM +0200, Wouter Verhelst wrote:
On Wed, Aug 09, 2006 at 04:38:20PM -0400, Kevin Mark wrote:
So there is ONE w-b for {i386,ppc,...) and there is one buildd for each
arch that connects to that ONE w-b?
No. There is one system where wanna-build databases are stored. That
single one wanna-build system has, of course, multiple databases, but
there's only one version of wanna-build (the distinction is made with a
command-line parameter in the form of -b arch/build-db
There are a number of buildd machines for each arch that connect to that
one w-b machine and call it correctly, based on their local
configuration and other things. The number of buildd machines is not
limited, certainly not to just one (in fact, requirements for etch
include having more than one buildd).
Hi Wouter,
thanks for the clarification, I will add it to my diagram. Saw you on
opensource21.nl after downloading your video from democracyplayer.
cheers,
Kev
--
| .''`. == Debian GNU/Linux == | my web site: |
| : :' : The Universal | debian.home.pipeline.com |
| `. `' Operating System| go to counter.li.org and |
| `-http://www.debian.org/ |be counted! #238656 |
| my keysever: pgp.mit.edu | my NPO: cfsg.org |
signature.asc
Description: Digital signature
Re: Buildds still not picking up new architectures, why?
On Wed, Aug 09, 2006 at 04:38:20PM -0400, Kevin Mark wrote:
So there is ONE w-b for {i386,ppc,...) and there is one buildd for each
arch that connects to that ONE w-b?
No. There is one system where wanna-build databases are stored. That
single one wanna-build system has, of course, multiple databases, but
there's only one version of wanna-build (the distinction is made with a
command-line parameter in the form of -b arch/build-db
There are a number of buildd machines for each arch that connect to that
one w-b machine and call it correctly, based on their local
configuration and other things. The number of buildd machines is not
limited, certainly not to just one (in fact, requirements for etch
include having more than one buildd).
--
Fun will now commence
-- Seven Of Nine, Ashes to Ashes, stardate 53679.4
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Buildds still not picking up new architectures, why?
Hi Kevin,
On Wed, Aug 09, 2006 at 04:38:20PM -0400, Kevin Mark wrote:
Hi Aurélien G, (sorry for the bad conversion by mutt)
No problem, I am still not an UTF-8 guy, so my local ISO-8859-15
encoding is the culprit for you. ;)
So there is ONE w-b for {i386,ppc,...) and there is one buildd for each
arch that connects to that ONE w-b?
Exactly, but several buildds for each architecture which take the
packages with the status 'Needs-Build' from wanna-build.
Cheers,
--
.''`. Aurélien GÉRÔME
: :' :
`. `'` Free Software Developer
`- Unix Sys Net Admin
signature.asc
Description: Digital signature
Re: Buildds still not picking up new architectures, why?
Hi, On Mon, Aug 07, 2006 at 12:17:52PM -0400, Kevin Mark wrote: it is my understanding that each arch has its own wanna-build that uses its own copy of a p-a-s file. So, that would mean that there would have to be more than one copy updated. If this is not the case, then could some enlightened soul illuminate the facts. Is it also true that that there is a ftpmaster copy of p-a-s that overrides a porter copy? It is not the case, w-b is a centralised system which has only one copy of P-a-s for all architectures. Cheers, -- .''`. Aurélien GÉRÔME : :' : `. `'` Free Software Developer `- Unix Sys Net Admin signature.asc Description: Digital signature
Re: Buildds still not picking up new architectures, why?
Hi, On Mon, Aug 07, 2006 at 03:01:41PM +0200, Ludovic Brenta wrote: Someone else (lamont) did the changes I requested on p-a-s; now the only remaining problem is that the buildds are not taking the new version of p-a-s into account, because they can't talk to the CVS pserver. It seems it is not the case anymore. The following works from me now: cvs -z3 -d:pserver:[EMAIL PROTECTED]:/cvs/dak co dak Therefore, I assume w-b can do the same. Cheers, -- .''`. Aurélien GÉRÔME : :' : `. `'` Free Software Developer `- Unix Sys Net Admin signature.asc Description: Digital signature
Re: Buildds still not picking up new architectures, why?
On Wed, Aug 09, 2006 at 02:41:49PM +0200, Aurélien GÉRÔME wrote:
Hi,
On Mon, Aug 07, 2006 at 12:17:52PM -0400, Kevin Mark wrote:
it is my understanding that each arch has its own wanna-build that uses
its own copy of a p-a-s file. So, that would mean that there would have
to be more than one copy updated. If this is not the case, then could
some enlightened soul illuminate the facts. Is it also true that that
there is a ftpmaster copy of p-a-s that overrides a porter copy?
It is not the case, w-b is a centralised system which has only one
copy of P-a-s for all architectures.
Cheers,
Hi Aurélien G, (sorry for the bad conversion by mutt)
So there is ONE w-b for {i386,ppc,...) and there is one buildd for each
arch that connects to that ONE w-b?
TIA,
Kev
--
| .''`. == Debian GNU/Linux == | my web site: |
| : :' : The Universal | debian.home.pipeline.com |
| `. `' Operating System| go to counter.li.org and |
| `-http://www.debian.org/ |be counted! #238656 |
| my keysever: pgp.mit.edu | my NPO: cfsg.org |
signature.asc
Description: Digital signature
Re: Buildds still not picking up new architectures, why?
On Mon, Aug 07, 2006 at 12:17:52PM -0400, Kevin Mark wrote: Someone else (lamont) did the changes I requested on p-a-s; now the only remaining problem is that the buildds are not taking the new version of p-a-s into account, because they can't talk to the CVS pserver. it is my understanding that each arch has its own wanna-build that uses its own copy of a p-a-s file. No. -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. [EMAIL PROTECTED] http://www.debian.org/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Buildds still not picking up new architectures, why?
On Thu, 27 Jul 2006, Steve Langasek wrote: $ telnet cvs.debian.org cvspserver Trying 192.25.206.10... telnet: connect to address 192.25.206.10: Connection refused telnet: Unable to connect to remote host: Connection refused $ Without pserver running, wanna-build can't get its updates from CVS. Ryan Murray (w-b admin, DSA) is aware of the problem. I see that 1.5 week later, the pserver is still not responding. Is Ryan on vacation? If so, can anyone else fix the problem for him? This issue has been blocking the Ada transition (19 source packages, 11 RC bugs) for about 3 weeks now, and I'd really like to be able to proceed. If Ryan is the only person who can fix this, then Debian has a problem; it would be nice to put a w-b admin *team* in place, for redundancy and no single point of failure. -- Ludovic Brenta. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Buildds still not picking up new architectures, why?
Hi, On Mon, Aug 07, 2006 at 10:47:13AM +0200, Ludovic Brenta wrote: Ryan Murray (w-b admin, DSA) is aware of the problem. I see that 1.5 week later, the pserver is still not responding. Is Ryan on vacation? If so, can anyone else fix the problem for him? This issue has been blocking the Ada transition (19 source packages, 11 RC bugs) for about 3 weeks now, and I'd really like to be able to proceed. Couldn't you get the problematic outdated packages (I assume this is the case if you're talking about [testing?] transitions) removed temporarily? If Ryan is the only person who can fix this, then Debian has a problem; I assume the Debian administration team is responsible for this task, but as Ryan is also a w-b and p-a-s admin, it sounds reasonable to expect he will tend to it. it would be nice to put a w-b admin *team* in place, for redundancy and no single point of failure. I don't think we should talk of `failure' really, at most this is a hold-up. Michael -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Buildds still not picking up new architectures, why?
Michael Banck writes: Couldn't you get the problematic outdated packages (I assume this is the case if you're talking about [testing?] transitions) removed temporarily? No, that would not solve the problem. The problem, as the subject line says, is that the buildds are not building my packages on all architectures. I need to see the build logs on all archs before I'm satisfied that my packages are in good shape. The Ada transition does not require the removal of any package. If Ryan is the only person who can fix this, then Debian has a problem; I assume the Debian administration team is responsible for this task, but as Ryan is also a w-b and p-a-s admin, it sounds reasonable to expect he will tend to it. Someone else (lamont) did the changes I requested on p-a-s; now the only remaining problem is that the buildds are not taking the new version of p-a-s into account, because they can't talk to the CVS pserver. it would be nice to put a w-b admin *team* in place, for redundancy and no single point of failure. I don't think we should talk of `failure' really, at most this is a hold-up. Ah :) Well so far I have failed in executing my planned Ada transition, because of this hold-up :) But it is not too late to snatch victory from the jaws of defeat :) -- Ludovic Brenta. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Buildds still not picking up new architectures, why?
On Mon, Aug 07, 2006 at 03:01:41PM +0200, Ludovic Brenta wrote: Michael Banck writes: Couldn't you get the problematic outdated packages (I assume this is the case if you're talking about [testing?] transitions) removed temporarily? No, that would not solve the problem. The problem, as the subject line says, is that the buildds are not building my packages on all architectures. I need to see the build logs on all archs before I'm satisfied that my packages are in good shape. The Ada transition does not require the removal of any package. If Ryan is the only person who can fix this, then Debian has a problem; I assume the Debian administration team is responsible for this task, but as Ryan is also a w-b and p-a-s admin, it sounds reasonable to expect he will tend to it. Someone else (lamont) did the changes I requested on p-a-s; now the only remaining problem is that the buildds are not taking the new version of p-a-s into account, because they can't talk to the CVS pserver. Hi Ludovic Brenta. it is my understanding that each arch has its own wanna-build that uses its own copy of a p-a-s file. So, that would mean that there would have to be more than one copy updated. If this is not the case, then could some enlightened soul illuminate the facts. Is it also true that that there is a ftpmaster copy of p-a-s that overrides a porter copy? cheers, Kev -- | .''`. == Debian GNU/Linux == | my web site: | | : :' : The Universal | debian.home.pipeline.com | | `. `' Operating System| go to counter.li.org and | | `-http://www.debian.org/ |be counted! #238656 | | my keysever: pgp.mit.edu | my NPO: cfsg.org | signature.asc Description: Digital signature
Re: Buildds still not picking up new architectures, why?
On Mon, Aug 07, 2006 at 10:47:13AM +0200, Ludovic Brenta wrote: This issue has been blocking the Ada transition (19 source packages, 11 RC bugs) for about 3 weeks now, and I'd really like to be able to proceed. I don't see how this can be blocking a transition. Please just do it for the arches that are supported now. The buildd admins/porters can perfectly take care of it once P-a-s gets updated. Kurt -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Buildds still not picking up new architectures, why?
Kurt Roeckx writes: On Mon, Aug 07, 2006 at 10:47:13AM +0200, Ludovic Brenta wrote: This issue has been blocking the Ada transition (19 source packages, 11 RC bugs) for about 3 weeks now, and I'd really like to be able to proceed. I don't see how this can be blocking a transition. Please just do it for the arches that are supported now. The buildd admins/porters can perfectly take care of it once P-a-s gets updated. There are several reasons why this problem is blocking. One reason is that, as I explained in another post, I need to check the build logs on all architectures before I'm satisfied with my packages. Another is that many packages build-depend on each other, leading to a potential mess of build failures if a required package is missing when I try to build the next. A third reason is that the lack of builds on all archs will probably prevent the packages from migrating to testing. I really want all my packages to migrate to testing, so I am sure they will be in etch, before I consider re-uploading to fix minor problems or improve the packaging. But it's not you I need to convince, it is Ryan or whoever admins the CVS pserver where P-a-s is. I am also curious, like Kevin Mark, to understand the buildd infrastructure better. -- Ludovic Brenta. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Buildds still not picking up new architectures, why?
On Mon, Aug 07, 2006 at 09:18:06PM +0200, Ludovic Brenta wrote: Kurt Roeckx writes: But it's not you I need to convince, it is Ryan or whoever admins the CVS pserver where P-a-s is. I am also curious, like Kevin Mark, to understand the buildd infrastructure better. -- Hi Ludovic, my inquiries are to improve the acuracy of my mini-project at http://debian.home.pipeline.com/newdebian2.png or goto http://debian.home.pipeline.com/ for the full list. cheers, Kev -- | .''`. == Debian GNU/Linux == | my web site: | | : :' : The Universal | debian.home.pipeline.com | | `. `' Operating System| go to counter.li.org and | | `-http://www.debian.org/ |be counted! #238656 | | my keysever: pgp.mit.edu | my NPO: cfsg.org | signature.asc Description: Digital signature
Buildds still not picking up new architectures, why?
I have requested an update to Packages-arch-specific for asis and other packages, so that the buildds would try to build these packages on newly supported architectures. LaMont Jones made the requested changes on 2006-07-23 [1]. Yesterday (2006-07-26), I uploaded asis again (2005-4), hoping to have it built on all supported archs. But the buildds, again, only attempted builds on powerpc and sparc, ant not on the newly supported ones [2]. [1] http://lists.debian.org/debian-devel/2006/07/msg00856.html [2] http://buildd.debian.org/build.php?pkg=asis What is happening? This is blocking the transition of Ada packages. Please respond directly to me as well as on the list. -- Ludovic Brenta. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Buildds still not picking up new architectures, why?
Hi Ludovic, On Thu, Jul 27, 2006 at 12:45:11PM +0200, Ludovic Brenta wrote: I have requested an update to Packages-arch-specific for asis and other packages, so that the buildds would try to build these packages on newly supported architectures. LaMont Jones made the requested changes on 2006-07-23 [1]. Yesterday (2006-07-26), I uploaded asis again (2005-4), hoping to have it built on all supported archs. But the buildds, again, only attempted builds on powerpc and sparc, ant not on the newly supported ones [2]. So do I with iroffer. Hell, I was going to do another upload of it to finally get it on ia64 and s390. However, what you say prevents me to do so for now. Lamont told me wanna-build gets an updated P-a-s from the CVS in less than 24 hours, probably by a cron job. Unfortunately, it seems this is a false statement or simply an assumption from his part. Hence, it leads me to think the file fed to wanna-build needs a manual update from the CVS. Cheers, -- .''`. Aurélien GÉRÔME : :' : `. `'` Free Software Developer `- Unix Sys Net Admin signature.asc Description: Digital signature
Re: Buildds still not picking up new architectures, why?
On Thursday 27 July 2006 14:26, Aurélien GÉRÔME wrote: Hi Ludovic, On Thu, Jul 27, 2006 at 12:45:11PM +0200, Ludovic Brenta wrote: I have requested an update to Packages-arch-specific for asis and other packages, so that the buildds would try to build these packages on newly supported architectures. LaMont Jones made the requested changes on 2006-07-23 [1]. Yesterday (2006-07-26), I uploaded asis again (2005-4), hoping to have it built on all supported archs. But the buildds, again, only attempted builds on powerpc and sparc, ant not on the newly supported ones [2]. So do I with iroffer. Hell, I was going to do another upload of it to finally get it on ia64 and s390. However, what you say prevents me to do so for now. Lamont told me wanna-build gets an updated P-a-s from the CVS in less than 24 hours, probably by a cron job. Unfortunately, it seems this is a false statement or simply an assumption from his part. Hence, it leads me to think the file fed to wanna-build needs a manual update from the CVS. Hello, AFAICT Packages-arch-specific is a quinn-diff [1] conffile, so probably bugreports should be filed against that package, but I'm not sure if autobuilders actually use that package though. Also it seems like dak/wanna-build/trigger.daily [2] should call quinn-diff to pick up new entries from P-a-s, so not-picking new stuff should be filed against dak package or quinn-diff package ? I don't know how lene/christina is involved here. Hm, someone should really clarify these actually. [1] packages.debian.org/quinn-diff [2] http://cvs.debian.org/dak/wanna-build/trigger.daily?root=dakview=markup [3] http://cvs.debian.org/lene/christina?root=dakview=markup -- pub 4096R/0E4BD0AB 2003-03-18 people.fccf.net/danchev/key pgp.mit.edu fingerprint 1AE7 7C66 0A26 5BFF DF22 5D55 1C57 0C89 0E4B D0AB -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Buildds still not picking up new architectures, why?
Hi, On Thu, Jul 27, 2006 at 03:06:25PM +0300, George Danchev wrote: AFAICT Packages-arch-specific is a quinn-diff [1] conffile, so probably bugreports should be filed against that package, but I'm not sure if autobuilders actually use that package though. Also it seems like dak/wanna-build/trigger.daily [2] should call quinn-diff to pick up new entries from P-a-s, so not-picking new stuff should be filed against dak package or quinn-diff package ? I don't know how lene/christina is involved here. Hm, someone should really clarify these actually. Well, I do not think packages in the distribution are responsible for that situation. It is an infrastructure issue and the people holding the keys are always the same ones, with no time to do something about it and/or not willing to trust someone else to do the job. It is a dead end. [1] packages.debian.org/quinn-diff [2] http://cvs.debian.org/dak/wanna-build/trigger.daily?root=dakview=markup [3] http://cvs.debian.org/lene/christina?root=dakview=markup Cheers, -- .''`. Aurélien GÉRÔME : :' : `. `'` Free Software Developer `- Unix Sys Net Admin signature.asc Description: Digital signature
Re: Buildds still not picking up new architectures, why?
On Thursday 27 July 2006 15:55, Aurélien GÉRÔME wrote: Hi, On Thu, Jul 27, 2006 at 03:06:25PM +0300, George Danchev wrote: AFAICT Packages-arch-specific is a quinn-diff [1] conffile, so probably bugreports should be filed against that package, but I'm not sure if autobuilders actually use that package though. Also it seems like dak/wanna-build/trigger.daily [2] should call quinn-diff to pick up new entries from P-a-s, so not-picking new stuff should be filed against dak package or quinn-diff package ? I don't know how lene/christina is involved here. Hm, someone should really clarify these actually. Well, I do not think packages in the distribution are responsible for that situation. It is an infrastructure issue and the people holding the keys are always the same ones, with no time to do something about it and/or not willing to trust someone else to do the job. It is a dead end. In fact these are two separate issues: a) why the infrastructure doesn't use these packages; b) where to collect P-a-s calls for updates. I just read at #128280, that these calls for updates are not wanted as wishlist bugs against quinn-diff package, but I think that storing them in public media i.e. BTS is far most robust solution (reveals when wishlists have been filed, and how have been dealt with), than just posting them to someone's mailbox... but anyway I'd tend to comply with the maintainer choice as said in the buglog. -- pub 4096R/0E4BD0AB 2003-03-18 people.fccf.net/danchev/key pgp.mit.edu fingerprint 1AE7 7C66 0A26 5BFF DF22 5D55 1C57 0C89 0E4B D0AB -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Buildds still not picking up new architectures, why?
Ludovic Brenta [EMAIL PROTECTED] writes: I have requested an update to Packages-arch-specific for asis and other packages, so that the buildds would try to build these packages on newly supported architectures. LaMont Jones made the requested changes on 2006-07-23 [1]. Yesterday (2006-07-26), I uploaded asis again (2005-4), hoping to have it built on all supported archs. But the buildds, again, only attempted builds on powerpc and sparc, ant not on the newly supported ones [2]. [1] http://lists.debian.org/debian-devel/2006/07/msg00856.html [2] http://buildd.debian.org/build.php?pkg=asis What is happening? The cvs version of P-a-s is updated. Now wanna-build (quinn-diff) needs to be updated to the new file. You can check the w-b status on http://buildd.debian.org/stats/ (bottom) to see when it lists the package. I don't think LaMont has access to w-b so you might have to ask Ryan or Elmo to do this. This is blocking the transition of Ada packages. Please respond directly to me as well as on the list. MfG Goswin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Buildds still not picking up new architectures, why?
On Thu, Jul 27, 2006 at 12:45:11PM +0200, Ludovic Brenta wrote: I have requested an update to Packages-arch-specific for asis and other packages, so that the buildds would try to build these packages on newly supported architectures. LaMont Jones made the requested changes on 2006-07-23 [1]. Yesterday (2006-07-26), I uploaded asis again (2005-4), hoping to have it built on all supported archs. But the buildds, again, only attempted builds on powerpc and sparc, ant not on the newly supported ones [2]. [1] http://lists.debian.org/debian-devel/2006/07/msg00856.html [2] http://buildd.debian.org/build.php?pkg=asis What is happening? $ telnet cvs.debian.org cvspserver Trying 192.25.206.10... telnet: connect to address 192.25.206.10: Connection refused telnet: Unable to connect to remote host: Connection refused $ Without pserver running, wanna-build can't get its updates from CVS. Ryan Murray (w-b admin, DSA) is aware of the problem. Please respond directly to me as well as on the list. Please use Mail-Followup-To so my mailer can respect this request automatically. :) -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. [EMAIL PROTECTED] http://www.debian.org/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
