You are not logged in.
- Topics: Active | Unanswered
#1 2008-09-27 21:04:21
- cookiecaper
- Member
- Registered: 2007-09-22
- Posts: 198
After upgrade to testing, schroot fails.
Get
[jeff@arch ~]$ schroot -c Arch32 -p opera
/usr/lib/schroot/schroot-mount: symbol lookup error: /usr/lib/schroot/schroot-mount: undefined symbol: _ZN5boost10filesystem6detail10status_apiERKSsRi
E: Arch32-110ee315-33b7-48ed-b56c-7280d07e8ad1: Chroot setup failed: stage=setup-startwith current testing. chroot is non-testing and I have upgraded klibc according to the mailing list. Using Arch x86_64 to login to Arch i686 chroot. Perhaps this is just because of different klibc versions? I don't know if it constitutes a bug or if it's supposed to be that way.
Offline
#2 2008-09-27 21:05:21
- fwojciec
- Member
- Registered: 2007-05-20
- Posts: 1,411
Re: After upgrade to testing, schroot fails.
You need to rebuild schroot package against the new boost from testing.
Offline
#3 2008-09-27 21:09:16
- cookiecaper
- Member
- Registered: 2007-09-22
- Posts: 198
Re: After upgrade to testing, schroot fails.
Oh, ahh. Thanks. The schroot maintainer needs to, too. ?
Last edited by cookiecaper (2008-09-27 21:09:28)
Offline
#4 2008-09-27 21:17:22
- fwojciec
- Member
- Registered: 2007-05-20
- Posts: 1,411
Re: After upgrade to testing, schroot fails.
Oh, ahh. Thanks. The schroot maintainer needs to, too. ?
Eventually, before boost is moved to extra, he'll need to, so yes.
Offline
#5 2008-10-06 12:19:26
- cookiecaper
- Member
- Registered: 2007-09-22
- Posts: 198
Re: After upgrade to testing, schroot fails.
I see. How does Arch deal with this? Is it policy not to update packages simultaneously in testing? iirc, testing is to ensure all is well before something goes to stable, just as an extra line of defense, and I understand if packages are sometimes missed (it is testing, after all), but should things not have to be rebuilt against new versions of dependencies when necessary? I'm also on the arch-dev-public list and see requests for signoff all the time but people usually ignore them. Do I just make sure nothing broke and then write in to say "nothing broke"? I want to be helpful dag nabbit. : )
Thanks again, man.
Last edited by cookiecaper (2008-10-06 12:23:54)
Offline
#6 2008-10-06 12:29:13
- Allan
- Pacman
- From: Brisbane, AU
- Registered: 2007-06-09
- Posts: 11,410
- Website
Re: After upgrade to testing, schroot fails.
The [testing] repo is only for packages in [core] and [extra]. Packages in the [community] do not get built against testing. Hopefully, once the [community] repo gets moved to using SVN, then we can get a [community-testing] repo. Until that point, you will need to rebuild packages using ABS when situations like this occur.
Package sign-offs are mainly for devs, although user help is appreciated with some packages that need specific hardware to test.
Offline