Dear all,

since openjdk-6 version 6b18-1.8-0ubuntu1, uploaded in Debian as 6b18-1.8-1,
configuration of openjdk-6-jre-headless and ca-certificates-java fail if /proc
is not mounted.

On my default sbuild installation, proc is indeed not mounted and I can not use
it anymore to prepare my uploads that build-depend on openjdk-6-jre-headless.
Since no bug has been reported against sbuild, I wonder how other people are
working around this problem. Have I missed something obvious?

Have a nice day,

--
Charles Plessy
Debian Med packaging team


--
To UNSUBSCRIBE, email to debian-java-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 20100528045005.GA21874@kunpuu.plessy.org">http://lists.debian.org/20100528045005.GA21874@kunpuu.plessy.org

On Fri, May 28, 2010 at 01:50:05PM +0900, Charles Plessy wrote:
> Dear all,
>
> since openjdk-6 version 6b18-1.8-0ubuntu1, uploaded in Debian as 6b18-1.8-1,
> configuration of openjdk-6-jre-headless and ca-certificates-java fail if /proc
> is not mounted.
>
> On my default sbuild installation, proc is indeed not mounted and I can not use
> it anymore to prepare my uploads that build-depend on openjdk-6-jre-headless.
> Since no bug has been reported against sbuild, I wonder how other people are
> working around this problem. Have I missed something obvious?

Hi,

Are you using sbuild with sudo or schroot ($chroot_mode in
sbuild.conf)?

If you're using sudo, the chroot setup is entirely down to you, and
you need to make sure /proc, /sys etc. are mounted e.g. in your
fstab. sudo isn't recommended nowadays, though; schroot is much
more flexible.

If you're using schroot, /proc will be automatically mounted for all
chroot types except "plain", which is exactly like sudo: you need to
set it up yourself. For all other chroot types, e.g. directory,
lvm-snapshot etc., /proc will be automatically mounted (unless you
deliberately remove it from the mount-defaults file).

Hope this helped; if not, do let me know. If you're using schroot,
the output of 'schroot --config <chroot>' and/or 'schroot --info'
will be useful to let us know about your setup.


Regards,
Roger

--
.'`. Roger Leigh
: :' : Debian GNU/Linux http://people.debian.org/~rleigh/
`. `' Printing on GNU/Linux? http://gutenprint.sourceforge.net/
`- GPG Public Key: 0x25BFB848 Please GPG sign your mail.

Le Sun, May 30, 2010 at 11:37:34PM +0100, Roger Leigh a écrit :
>
> Are you using sbuild with sudo or schroot ($chroot_mode in
> sbuild.conf)?
>
> If you're using sudo, the chroot setup is entirely down to you, and
> you need to make sure /proc, /sys etc. are mounted e.g. in your
> fstab. sudo isn't recommended nowadays, though; schroot is much
> more flexible.
>
> If you're using schroot, /proc will be automatically mounted for all
> chroot types except "plain", which is exactly like sudo: you need to
> set it up yourself. For all other chroot types, e.g. directory,
> lvm-snapshot etc., /proc will be automatically mounted (unless you
> deliberately remove it from the mount-defaults file).

Dear Roger,

thank you very much, this was exactly the source of the problem.

In the computer where /proc was not mounted, /etc/schroot/schroot.conf did
not provide a type for the sid schroot, which then defautled to plain.
Indicating type=directory solved my problem. It is my mistake that I have
misconfigured this system and that it did not use the configuration files in
/etc/schroot/chroot.d.

When I was trying to solve my problem by myself, I looked for “/proc� as a
keyword in the documentation and did not find a hint that not having it mounted
was a symptom of not using the type I intended. If you think that others may
make a similar error, how about the following patch to the schroot
documentation?

diff --git a/man/schroot.conf.5.in b/man/schroot.conf.5.in
index 40cec0d..92e08b9 100644
--- a/man/schroot.conf.5.in
+++ b/man/schroot.conf.5.in
@@ -133,7 +133,8 @@ Plain and directory chroots
.PP
Chroots of type [oq]plain[cq] or [oq]directory[cq] are directories
accessible in the filesystem. The two types are equivalent except for the fact
-that directory chroots run setup scripts, whereas plain chroots do not.
+that directory chroots run setup scripts, whereas plain chroots do not. As a
+consequence, virtual filesystems like f[BI]/procfP are not mounted in plain chroots.
Additionally, directory chroots implement the fBfilesystem union chrootfP
options (see [lq]fIFilesystem Union chroot optionsfP[rq], below).
.PP


Have a nice day,

--
Charles


--
To UNSUBSCRIBE, email to debian-java-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 20100604085408.GE9028@kunpuu.plessy.org">http://lists.debian.org/20100604085408.GE9028@kunpuu.plessy.org