|
Home > Archive > Debian Developers > September 2004 > daily pestering about s390 and sparc buildd failure
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
daily pestering about s390 and sparc buildd failure
|
|
| Thomas Bushnell BSG 2004-08-27, 6:25 pm |
|
I need someone to help with the buildd failure of the bbconf package
on s390 and sparc. To repeat, bbconf Build-Depends on xlibs-dev;
xlibs-dev depends on libx11-dev, and libx11-dev depends on libx11-6.
On s390, libx11-dev gets installed, but not its dependency libx11-6.
On sparc, xlibs-dev gets installed, but not its dependency libx11-dev.
In both cases, the failure to install libx11-6 causes the build
failure.
Blars Blarson suggested to me that the failure is pbuilder-specific,
but I used pbuilder on ppc and it works fine.
To debug this, I need access to an s390 or a sparc, or the buildd
maintainers of those architectures need to figure out why their build
daemons are not installing packages correctly.
I would look for a Debian project machine myself, but the table at
http://db.debian.org/machines.cgi is hopelessly out-of-date. The only
sparc machine working there is auric, and there are no s390s.. And
anyway, I don't know how to use pbuilder except as root, and I'm not
root on auric.
I need a volunteer. Please don't make me pester every day.
Thomas
--
To UNSUBSCRIBE, email to debian-devel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
| |
| Thomas Bushnell BSG 2004-08-27, 6:25 pm |
| Thomas Bushnell BSG <tb@becket.net> writes:
> Blars Blarson suggested to me that the failure is pbuilder-specific,
> but I used pbuilder on ppc and it works fine.
Oh, and according to the buildd logs, the failures are with sbuild
anyhow.
--
To UNSUBSCRIBE, email to debian-devel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
| |
| Thomas Bushnell BSG 2004-08-27, 6:25 pm |
| Thomas Bushnell BSG <tb@becket.net> writes:
> To debug this, I need access to an s390 or a sparc, or the buildd
> maintainers of those architectures need to figure out why their build
> daemons are not installing packages correctly.
Looks like I can log on vore, the sparc autobuilder which is failing.
So vore is running woody. Such commands as "apt-cache show xlibs-dev"
show the woody versions--which have way fewer dependencies, of
course. And "apt-cache show libx11-dev" reports that the package
doesn't exist (which it doesn't in woody).
Yet, the xlibs-dev that vore is downloading in the sbuild run is the
correct sid version--though this doesn't explain then why it doesn't
get the dependency (libx11-dev). Presumably sbuild is running in a
chroot.
But if apt-get is reading dependency information from woody, and then
installing sid packages, this might explain the problem. (My
recollection is that apt-get runs dpkg with --force-depends or
something like that, right?)
As yet, nobody has volunteered to help.
Thomas
--
To UNSUBSCRIBE, email to debian-devel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
| |
| Andrew Pollock 2004-08-27, 6:25 pm |
| On Fri, Aug 27, 2004 at 12:11:40AM -0700, Thomas Bushnell BSG wrote:
> Thomas Bushnell BSG <tb@becket.net> writes:
>
>
> Looks like I can log on vore, the sparc autobuilder which is failing.
>
> So vore is running woody. Such commands as "apt-cache show xlibs-dev"
> show the woody versions--which have way fewer dependencies, of
> course. And "apt-cache show libx11-dev" reports that the package
> doesn't exist (which it doesn't in woody).
>
> Yet, the xlibs-dev that vore is downloading in the sbuild run is the
> correct sid version--though this doesn't explain then why it doesn't
> get the dependency (libx11-dev). Presumably sbuild is running in a
> chroot.
>
> But if apt-get is reading dependency information from woody, and then
> installing sid packages, this might explain the problem. (My
> recollection is that apt-get runs dpkg with --force-depends or
> something like that, right?)
>
> As yet, nobody has volunteered to help.
Thomas, meet dchroot, dchroot, meet Thomas.
(base)apollock@vore:~$ dchroot -l
Available chroots: unstable testing stable oldstable sid sarge woody potato
regards
Andrew
--
To UNSUBSCRIBE, email to debian-devel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
| |
| Thomas Bushnell BSG 2004-08-27, 6:25 pm |
| Andrew Pollock <apollock@debian.org> writes:
> Thomas, meet dchroot, dchroot, meet Thomas.
>
> (base)apollock@vore:~$ dchroot -l
> Available chroots: unstable testing stable oldstable sid sarge woody potato
Curious.
tb@vore:~/foo$ man dchroot
No manual entry for dchroot
tb@vore:~/foo$ dchroot --help
Usage: dchroot <chroot>
Available chroots: unstable testing stable oldstable sid sarge woody potato
tb@vore:~/foo$ dchroot sid
Executing shell in chroot: /org/vore.debian.org/chroots/user/sid
(unstable)tb@vore:~$ apt-get install li xlibs-dev
E: Could not open lock file /var/lib/dpkg/lock - open (13 Permission denied)
E: Unable to lock the administration directory (/var/lib/dpkg/), are you root?
So that's splendid, but doesn't help me debug anything.
Perhaps this is obvious to y'all, but in the absence of someone who
says "I volunteer to figure out why this is failing", I have to try
myself, and the seemingly obvious tools are escaping me.
Thomas
--
To UNSUBSCRIBE, email to debian-devel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
| |
| Eduard Bloch 2004-08-27, 6:25 pm |
| #include <hallo.h>
* Thomas Bushnell BSG [Thu, Aug 26 2004, 11:52:07PM]:
> I would look for a Debian project machine myself, but the table at
> http://db.debian.org/machines.cgi is hopelessly out-of-date. The only
> sparc machine working there is auric, and there are no s390s.. And
raptor.debian.org works.
Eduard.
--
For any stupid thing chosen at random, you'll find at least 5 people on
the Internet who thinks it's a good idea. -- Steve Langasek in debian-devel
--
To UNSUBSCRIBE, email to debian-devel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
| |
| Blars Blarson 2004-08-28, 2:49 am |
| In article <87vff452jy.fsf@becket.becket.net> tb@becket.net writes:
>Do you have an alternative strategy for solving the problem, or are
>you just protesting that this strategy is inconvenient?
In this case, you should have asked me. You already knew I have a
sparc machine with pbuilder set up.
That offer goes for other DDs as well that need help debugging on
sparc. If the dual 300mhz machine gets overloaded, I've got other
machines that can be set up as well. (Vore is a single 300 Mhz
machine that has been doing almost all the building. Auric was set up
as a buildd when vore was down.)
--
Blars Blarson blarson@blars.org
http://www.blars.org/blars.html
With Microsoft, failure is not an option. It is a standard feature.
--
To UNSUBSCRIBE, email to debian-devel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
| |
| Frank Küster 2004-08-28, 3:19 pm |
| Blars Blarson <blarson@blars.org> schrieb:
> In article <87vff452jy.fsf@becket.becket.net> tb@becket.net writes:
>
> In this case, you should have asked me. You already knew I have a
> sparc machine with pbuilder set up.
Can you offer an sbuildm, too? It seems sometimes bugs hide themselves
with pbuilder...
Regards, Frank
--=20
Frank K=FCster, Biozentrum der Univ. Basel
Abt. Biophysikalische Chemie
| |
| Blars Blarson 2004-08-29, 2:49 am |
| In article <87wtzjrvt1.fsf@alhambra.bioz.unibas.ch> frank@debian.org writes:
>Blars Blarson <blarson@blars.org> schrieb:
>
>Can you offer an sbuildm, too? It seems sometimes bugs hide themselves
>with pbuilder...
Not at this time, but I might be able to set one up. (Pointing me to
directions might make this happen faster.) Pointers on how to set up
an autobuilder would be even better.
I've only seen a few packages that built on my pbuilder but failed the
autobuild for reaseons other than missing dependancies. (Where a
resceduled autobuild would work.) Most were obvious what the
autobuilders problem was. (/proc not mounted, missing /etc/services)
--
Blars Blarson blarson@blars.org
http://www.blars.org/blars.html
With Microsoft, failure is not an option. It is a standard feature.
--
To UNSUBSCRIBE, email to debian-devel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
| |
| Goswin von Brederlow 2004-09-02, 6:55 pm |
| Thomas Bushnell BSG <tb@becket.net> writes:
> Andrew Pollock <apollock@debian.org> writes:
>
>
> Curious.
> tb@vore:~/foo$ man dchroot
> No manual entry for dchroot
> tb@vore:~/foo$ dchroot --help
> Usage: dchroot <chroot>
> Available chroots: unstable testing stable oldstable sid sarge woody potato
> tb@vore:~/foo$ dchroot sid
> Executing shell in chroot: /org/vore.debian.org/chroots/user/sid
> (unstable)tb@vore:~$ apt-get install li xlibs-dev
> E: Could not open lock file /var/lib/dpkg/lock - open (13 Permission denied)
> E: Unable to lock the administration directory (/var/lib/dpkg/), are you root?
>
>
> So that's splendid, but doesn't help me debug anything.
You do know that apt has extensive documentation detailing how to
change pretty much everything. You can run apt without locking or
change the directory where apt puts the lock and downloads debs to
.....
You can run apt-get completly as user if you use -d or -s. If you need
a detailed example look at the get-packages in debian-installer.
Also apt-cache should work fine in the chroot.
> Perhaps this is obvious to y'all, but in the absence of someone who
> says "I volunteer to figure out why this is failing", I have to try
> myself, and the seemingly obvious tools are escaping me.
>
> Thomas
For s390 try the emulator.
MfG
Goswin
PS: One can also read Packages files manually and ude dpkg -I, -e and
-x to inspect packages on another arch.
--
To UNSUBSCRIBE, email to debian-devel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
| |
| Goswin von Brederlow 2004-09-02, 6:55 pm |
| Thomas Bushnell BSG <tb@becket.net> writes:
> Ingo Juergensmann <ij@2004.bluespice.org> writes:
>
>
> It's like you can't follow things for a moment. The bug would not and
> could not manifest itself on my arch.
>
>
> No, it doesn't. The new package hit the queues before the old one got
> built, and therefore the old one never got autobuilt (on the
> overloaded queues, that is).
But on the queues that just strugle to get along and have just build
or are still building your package.
Also note that the queue is not a FIFO. A new upload will cut in front
of other packages moving them back one position on archs where your
package has already been build. The further up in the queue sorting
your package is the more harmfull a new upload is (since more packages
below you are affected).
It is amazing how often Package builds get rejected or aborted due to
new uploads and for something like the mozilla clones with >50h build
time getting the build rejected realy sucks. Imagine someone uploading
mozilla again just to test if the s390 buildd has a bug.
MfG
Goswin
--
To UNSUBSCRIBE, email to debian-devel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
| |
| Goswin von Brederlow 2004-09-02, 6:55 pm |
| Thomas Bushnell BSG <tb@becket.net> writes:
> Ingo Juergensmann <ij@2004.bluespice.org> writes:
>
>
> I'm doing this on behalf of QA. Good grief, can't you please get the
> facts?
Then maybe QA should get access to more hardware?
>
> Perhaps you might get the facts before attacking me.
>
>
> Since the bug seems to me to be a bug in the buildd, what would you
> suggest I do?
Run sbuild using fakechroot in the dchroot.
> *MY* preference is to file a release-critical bug against the buildd
> pseudo-package... But there isn't one, and I doubt it would actually
> help. None of the buildd maintainers have said, "Oh, I'll look at
> this and make sure it gets fixed."
There is an sbuild package and the maintainer has recently reawakened.
He should also be aware of any differences between the buildd sbuild
and the sid version.
Did you try to talk to him about this?
> Thomas
MfG
Goswin
--
To UNSUBSCRIBE, email to debian-devel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
| |
| Martin Schulze 2004-09-02, 6:55 pm |
| Thomas Bushnell BSG wrote:
> Andrew Pollock <apollock@debian.org> writes:
>=20
tato[vbcol=seagreen]
>=20
> Curious.
> tb@vore:~/foo$ man dchroot
> No manual entry for dchroot
> tb@vore:~/foo$ dchroot --help
> Usage: dchroot <chroot>
> Available chroots: unstable testing stable oldstable sid sarge woody pota=
to
> tb@vore:~/foo$ dchroot sid
> Executing shell in chroot: /org/vore.debian.org/chroots/user/sid
> (unstable)tb@vore:~$ apt-get install li=08 =08=08 =08xlibs-dev
> E: Could not open lock file /var/lib/dpkg/lock - open (13 Permission deni=
ed)
> E: Unable to lock the administration directory (/var/lib/dpkg/), are you =
root?
Ever noticed that apt-get requires to run as root for locking
and dpkg requires root for installing packages? Dooh.
> So that's splendid, but doesn't help me debug anything.
>=20
> Perhaps this is obvious to y'all, but in the absence of someone who
> says "I volunteer to figure out why this is failing", I have to try
> myself, and the seemingly obvious tools are escaping me.
If you need some build dependencies installed, mail the admin,
which is debian-admin@lists.debian.org for our hosts. Dude, were
you taken over by an alien recently or something?
Regards,
Joey
--=20
Of course, I didn't mean that, which is why I didn't say it.
What I meant to say, I said. -- Thomas Bushnell
Please always Cc to me when replying to me on the lists.
| |
| Thomas Bushnell BSG 2004-09-02, 6:55 pm |
| Blars Blarson <blarson@blars.org> writes:
> I've only seen a few packages that built on my pbuilder but failed the
> autobuild for reaseons other than missing dependancies. (Where a
> resceduled autobuild would work.) Most were obvious what the
> autobuilders problem was. (/proc not mounted, missing /etc/services)
As it happens, the bbconf bug was triggered by having *more* packages
installed!
--
To UNSUBSCRIBE, email to debian-devel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
| |
| Thomas Bushnell BSG 2004-09-02, 6:55 pm |
| Goswin von Brederlow <brederlo@informatik.uni-tuebingen.de> writes:
> It is amazing how often Package builds get rejected or aborted due to
> new uploads and for something like the mozilla clones with >50h build
> time getting the build rejected realy sucks. Imagine someone uploading
> mozilla again just to test if the s390 buildd has a bug.
An excellent reason not to do that with mozilla. Of course, that you
shouldn't do something with a huge build doesn't imply that you
shouldn't ever do it.
--
To UNSUBSCRIBE, email to debian-devel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
| |
| Thomas Bushnell BSG 2004-09-02, 6:55 pm |
| Martin Schulze <joey@infodrom.org> writes:
>
> If you need some build dependencies installed, mail the admin,
> which is debian-admin@lists.debian.org for our hosts. Dude, were
> you taken over by an alien recently or something?
This wouldn't have helped, which I knew, which is why I didn't pursue
it as a strategy. If my crazy guess had been right, the problem was
that dependencies which were implied by debian/control weren't being
installed. Asking to have something in this or that root doesn't help
if getting them into the sbuild environment is failing for some
bizarre cause.
My crazy guess was wrong, but my probe found the bug, because it
generated exact package lists of the different sbuild environments,
which was crucial to finding the bug--and again, asking to have this
or that package installed wouldn't help.
I never had any problem compiling the package on s390 or sparc--which
people never seemed to pay attention to--the question was why the
package didn't build in sbuild *even though all the necessary
dependencies were installed*, and did build elsewhere.
--
To UNSUBSCRIBE, email to debian-devel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
| |
| Goswin von Brederlow 2004-09-02, 6:55 pm |
| Thomas Bushnell BSG <tb@becket.net> writes:
> Blars Blarson <blarson@blars.org> writes:
>
>
> As it happens, the bbconf bug was triggered by having *more* packages
> installed!
That is quite common. A lot of sources fail if automake / autoconf /
libtool is installed when they don't Build-Depend on it. During build
the package then suddenly runs those commands and messes up.
But that is a bug in the package.
MfG
Goswin
--
To UNSUBSCRIBE, email to debian-devel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
|
|
|
|
|