Your message dated Sat, 30 Mar 2013 02:47:50 +
with message-id
and subject line Bug#702102: fixed in pbuilder 0.215
has caused the Debian Bug report #702102,
regarding fails to upgrade (cowbuilder) chroot
to be marked as done.
This means that you claim that the problem has been dealt with
I've read the full thread now, sorry for the quick response, I was working down
the list.
At Tue, 26 Mar 2013 13:46:08 +0100,
Michael Biebl wrote:
>
> [1 ]
> Am 26.03.2013 09:48, schrieb Junichi Uekawa:
> > not enough information in the bug, 702811 seems to be a better bug.
>
> Say what? Have
I think that patch is completely borken too.
/dev/shm seems to be a symlink to /run/shm and /run/shm doesn't seem to exist
(in older debootstrap ? how did they get generated?)
anyway, I've committed a change to only look at /run/shm.
At Tue, 26 Mar 2013 18:48:40 + (UTC),
Thorsten Glaser wro
Chris Knadle dixit:
>+if [ "$DEB_BUILD_ARCH_OS" = "linux" ] && [ "$USEDEVSHM" = "yes" ]; then
>+ SHM_PATH="run/shm"
>
>+ [ ! -d "/$SHM_PATH" ] && SHM_PATH="dev/shm"
This
not enough information in the bug, 702811 seems to be a better bug.
At Sat, 02 Mar 2013 20:05:43 +0100,
Michael Biebl wrote:
>
> Package: pbuilder
> Version: 0.214
> Severity: serious
>
> Using cowbuilder in combination with pbuilder.
> The latest update broke cowbuilder --update
> Getting hundr
On Tuesday, March 26, 2013 08:46:08, Michael Biebl wrote:
> Am 26.03.2013 09:48, schrieb Junichi Uekawa:
> > not enough information in the bug, 702811 seems to be a better bug.
>
> Say what? Have you read the full bug report, including the analysis that
> it is because of /run/shm vs /dev/shm?
Re
Am 26.03.2013 09:48, schrieb Junichi Uekawa:
> not enough information in the bug, 702811 seems to be a better bug.
Say what? Have you read the full bug report, including the analysis that
it is because of /run/shm vs /dev/shm?
It's trivial to reproduce the bug this way. So I don't understand whic
For those who like me are (were) testing systemd, reverting to the default
init (SysV) in testing/unstable would also work around this problem.
signature.asc
Description: signature
On Wednesday, March 20, 2013 15:25:26, Michael Biebl wrote:
> from IRC:
>
> i ran into that one today, i think. had to set a variable in
> pbuilderrc to tell it to not bother mounting shm
> iirc it tries to check whether /run/shm exists on the host to
> decide whether to use /dev/shm or /run/sh
Am 20.03.2013 20:25, schrieb Michael Biebl:
> from IRC:
>
> i ran into that one today, i think. had to set a variable in
> pbuilderrc to tell it to not bother mounting shm
> iirc it tries to check whether /run/shm exists on the host to
> decide whether to use /dev/shm or /run/shm in the chroot
from IRC:
i ran into that one today, i think. had to set a variable in
pbuilderrc to tell it to not bother mounting shm
iirc it tries to check whether /run/shm exists on the host to
decide whether to use /dev/shm or /run/shm in the chroot
which makes no sense at all
That's the problem indeed
Package: pbuilder
Version: 0.214
--- Please enter the report below this line. ---
I saw this bug report via apt-listbugs and decided to do the upgrade anyway
to try to help debug the problem; however after upgrading for some reason I
don't seem to be hitting the bug. I have 6 cowbuidler chroots
Package: pbuilder
Version: 0.214
Severity: serious
Using cowbuilder in combination with pbuilder.
The latest update broke cowbuilder --update
Getting hundreds of:
rm: cannot remove
'/var/cache/pbuilder/build//cow.18262/proc/273/net/sockstat6': Operation
not permitted
-- System Information:
Deb
13 matches
Mail list logo
