Your message dated Sat, 27 Oct 2012 23:47:35 +0000 with message-id <e1tsg6j-0000mf...@franck.debian.org> and subject line Bug#686148: fixed in schroot 1.6.4-1 has caused the Debian Bug report #686148, regarding schroot: Does not unmount /run/shm to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 686148: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=686148 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---Package: schroot Version: 1.6.3-1 Severity: minor Dear Maintainer, I noticed several “/run/shm” in my mount since a moment but did not figure out where they came from. I just create a new schroot and got one more, I umount all superfluous “/run/shm” and run “schroot -c sid-amd64-sbuild” and got: /dev/mapper/hati-sid--amd64--sbuild--a91d556e--4f12--4e9c--9c00--b7f4ee915b59 on /var/lib/schroot/mount/sid-amd64-sbuild-a91d556e-4f12-4e9c-9c00-b7f4ee915b59 type btrfs (rw,noatime,space_cache) proc on /var/lib/schroot/mount/sid-amd64-sbuild-a91d556e-4f12-4e9c-9c00-b7f4ee915b59/proc type proc (rw,nosuid,nodev,noexec,relatime) sysfs on /var/lib/schroot/mount/sid-amd64-sbuild-a91d556e-4f12-4e9c-9c00-b7f4ee915b59/sys type sysfs (rw,nosuid,nodev,noexec,relatime) devpts on /var/lib/schroot/mount/sid-amd64-sbuild-a91d556e-4f12-4e9c-9c00-b7f4ee915b59/dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000) tmpfs on /run/shm type tmpfs (rw,relatime) /dev/dm-13 on /var/lib/schroot/mount/sid-amd64-sbuild-a91d556e-4f12-4e9c-9c00-b7f4ee915b59/build type btrfs (rw,nodev,noatime,space_cache) /dev/mapper/hati-var+cache on /var/lib/schroot/mount/sid-amd64-sbuild-a91d556e-4f12-4e9c-9c00-b7f4ee915b59/var/cache/apt/archives type ext4 (rw,noatime,data=ordered) After quitting the schroot, the “/run/shm” is still here. Regards. -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (90, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.6.0-rc3+hati.1 (SMP w/2 CPU cores; PREEMPT) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages schroot depends on: ii libboost-filesystem1.49.0 1.49.0-3.1 ii libboost-iostreams1.49.0 1.49.0-3.1 ii libboost-program-options1.49.0 1.49.0-3.1 ii libboost-regex1.49.0 1.49.0-3.1 ii libboost-system1.49.0 1.49.0-3.1 ii libc6 2.13-35 ii libgcc1 1:4.7.1-7 ii liblockdev1 1.0.3-1.5 ii libpam0g 1.1.3-7.1 ii libstdc++6 4.7.1-7 ii libuuid1 2.20.1-5.1 ii schroot-common 1.6.3-1 schroot recommends no packages. Versions of packages schroot suggests: pn aufs-modules | unionfs-modules <none> ii btrfs-tools 0.19+20120328-8 ii debootstrap 1.0.42 ii lvm2 2.02.95-4 pn qemu-user-static <none> -- Configuration Files: /etc/schroot/sbuild/fstab changed: /proc /proc none rw,bind 0 0 /sys /sys none rw,bind 0 0 /dev/pts /dev/pts none rw,bind 0 0 tmpfs /dev/shm tmpfs defaults 0 0 /var/lib/sbuild/build /build none rw,bind 0 0 /var/cache/apt/archives /var/cache/apt/archives none rw,bind 0 0 /etc/schroot/setup.d/05lvm changed: set -e . "$SETUP_DATA_DIR/common-data" . "$SETUP_DATA_DIR/common-functions" . "$SETUP_DATA_DIR/common-config" if [ "$VERBOSE" = "verbose" ]; then LVM_VERBOSE="-v" fi if [ "$CHROOT_TYPE" = "lvm-snapshot" ]; then if [ $STAGE = "setup-start" ]; then if [ ! "$DEVTYPE" "$CHROOT_DEVICE" ]; then fatal "Device '$CHROOT_DEVICE' does not exist" fi if [ "$VERBOSE" = "verbose" ]; then lvcreate $LVM_VERBOSE --snapshot --name "$CHROOT_LVM_SNAPSHOT_NAME" \ "$CHROOT_DEVICE" $CHROOT_LVM_SNAPSHOT_OPTIONS else lvcreate $LVM_VERBOSE --snapshot --name "$CHROOT_LVM_SNAPSHOT_NAME" \ "$CHROOT_DEVICE" $CHROOT_LVM_SNAPSHOT_OPTIONS > /dev/null fi elif [ $STAGE = "setup-stop" ]; then if [ "$DEVTYPE" "$CHROOT_LVM_SNAPSHOT_DEVICE" ]; then # The lock needs to be dropped immediately before # destroying the device. There is a small race here, but # the lock can't be dropped once the device has been # removed. info "Removing device lock for $CHROOT_LVM_SNAPSHOT_DEVICE, owned by pid $PID" "$LIBEXEC_DIR/schroot-releaselock" \ --device="$CHROOT_LVM_SNAPSHOT_DEVICE" \ --pid=$PID || true MAPPER_DEVICE=`dmsetup info --noheadings -c -o name $CHROOT_LVM_SNAPSHOT_DEVICE` if [ "$VERBOSE" = "verbose" ]; then dmsetup remove -f "/dev/mapper/${MAPPER_DEVICE}" || true dmsetup remove -f "/dev/mapper/${MAPPER_DEVICE}-cow" || true lvremove $LVM_VERBOSE -f "$CHROOT_LVM_SNAPSHOT_DEVICE" || true else dmsetup remove -f "/dev/mapper/${MAPPER_DEVICE}" > /dev/null || true dmsetup remove -f "/dev/mapper/${MAPPER_DEVICE}-cow" > /dev/null || true lvremove $LVM_VERBOSE -f "$CHROOT_LVM_SNAPSHOT_DEVICE" > /dev/null || true fi else # The block device no longer exists, or was never created, # for example on lvcreate failure. warn "$CHROOT_LVM_SNAPSHOT_DEVICE does not exist (it may have been removed previously)" fi fi fi -- no debconf information -- Daniel Dehennin Récupérer ma clef GPG: gpg --keyserver pgp.mit.edu --recv-keys 0x7A6FE2DF
pgpDunYjkLbt6.pgp
Description: PGP signature
--- End Message ---
--- Begin Message ---Source: schroot Source-Version: 1.6.4-1 We believe that the bug you reported is fixed in the latest version of schroot, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 686...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Roger Leigh <rle...@debian.org> (supplier of updated schroot package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@debian.org) -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Format: 1.8 Date: Sat, 27 Oct 2012 23:30:38 +0100 Source: schroot Binary: schroot-common libsbuild-dev schroot-dbg libsbuild-doc schroot dchroot dchroot-dsa Architecture: source all amd64 Version: 1.6.4-1 Distribution: unstable Urgency: low Maintainer: Debian buildd-tools Developers <buildd-tools-de...@lists.alioth.debian.org> Changed-By: Roger Leigh <rle...@debian.org> Description: dchroot - Execute commands in a chroot environment dchroot-dsa - Execute commands in a chroot environment libsbuild-dev - development files for the Debian source builder libsbuild-doc - development documentation for the Debian source builder schroot - Execute commands in a chroot environment schroot-common - common files for schroot schroot-dbg - schroot, dchroot and dchroot-dsa debugging symbols Closes: 686148 688304 689078 691376 Changes: schroot (1.6.4-1) unstable; urgency=low . * New upstream stable release. * NEWS: Provide guidance for wheezy upgrades with regard to use of the profile key in a backward-compatible manner also using setup.config, to mimic the behaviour of the deprecated script-config key. * schroot.conf(5) additionally updated to document script-config deprecation and use of user keys such as setup.config. * schroot-mount: Canonicalise mountpoints with symlinks to avoid mounting absolute paths on the host rather than inside the chroot (Closes: #686148). Note the caveat regarding paths with multiple symlinks in schroot-script-config(5). This permits safe use of symlinks as mountpoints in some common circumstances, e.g. on /var/lock, which is a symlink to /run/lock, though this is not recommended practice. * 15binfmt no longer pollutes output, by redirecting stderr from "which update-binfmts" (Closes: #688304). * Ensure that CHROOT_ALIAS (setup scripts) and SCHROOT_ALIAS_NAME (user environment) always refer to the alias used to create the session (Closes: #689078). The alias is no longer canonicalised by sbuild::chroot_config::validate_chroots. The logic for chroot validation and information display in sbuild::chroot_config and schroot::main_base (and derived classes) required refactoring to allow the unresolved alias name to be passed through to the session clone operation in sbuild::session, so that it could be stored in the chroot's sbuild::chroot_facet_session facet. * On session recovery, mount the snapshot LV rather than the source LV for LVM snapshot chroots (Closes: #691376). The code which sets the mount device for all mountable chroots (with an sbuild::chroot_facet_mountable facet) is in sbuild::chroot_facet_session_clonable::clone_session_setup(). All chroot types refactored to set the mount device here. * 10mount uses a lock directory /var/lock/schroot to contain its lockfile, rather than directly using /var/lock, which is less secure. Checksums-Sha1: 47dbe8aace624516f731b2da360f218ca63d3775 2424 schroot_1.6.4-1.dsc b2b4b343a9f8a4151412019896400e247fff5e9e 736200 schroot_1.6.4.orig.tar.xz cb104208ad80052665212e828699788e23588300 30359 schroot_1.6.4-1.debian.tar.gz 5dce6f318da6ee6aadaddcabe8fe1ff1ebb8a5f7 267800 schroot-common_1.6.4-1_all.deb 121597525e3ed1ae5d46f6ecec4ef5a50101e9d1 2296982 libsbuild-dev_1.6.4-1_amd64.deb 2f4d364b23d2cc4200fcf068eae332a863701156 29133852 schroot-dbg_1.6.4-1_amd64.deb 9325b852af368ff61fcf3d131d1e3d831695811a 8188950 libsbuild-doc_1.6.4-1_all.deb 13c835eefafe83f113d728f32d4d9700693c4b46 966820 schroot_1.6.4-1_amd64.deb c5d00fa3370e76d24214938b266bb0de8e9639bf 370162 dchroot_1.6.4-1_amd64.deb d03a9626ba8d71ab4b213e9821b8316b829456fe 369404 dchroot-dsa_1.6.4-1_amd64.deb Checksums-Sha256: 561f06c639f76a7e45243739e84888b6dd30c1dbd2f782955230195515d73b84 2424 schroot_1.6.4-1.dsc a7d54a148353ed7e8d8db84c77a0f2e99681a4bb2c5b0d38c40ce2d99d8d6f87 736200 schroot_1.6.4.orig.tar.xz 03e3528d0c27f1cead324dba125623593356465e2e5af8b3299a74632e708e7a 30359 schroot_1.6.4-1.debian.tar.gz 36c08e25f16bcd18adf6cf5fb2ebdcf64bc4748318946e4dd5235f3450fffff3 267800 schroot-common_1.6.4-1_all.deb eab1e75d5cb3ac4ef7b1a8caccffb212feb1579220fdfec5fc0aeaf8f9196d18 2296982 libsbuild-dev_1.6.4-1_amd64.deb 3894554822a515e1a64eece573be0391a79f89b86796e6b15ffaed5b4d4aa0d9 29133852 schroot-dbg_1.6.4-1_amd64.deb 76a7f4029e928ba1b7ad492b6eeed39e83e51b26ed6f94a740b47a0a114cf1b4 8188950 libsbuild-doc_1.6.4-1_all.deb a2b8b1fdfa91bf24e5f62901388221d47f1511b89c4b146351f6d7f32deff3aa 966820 schroot_1.6.4-1_amd64.deb 26526dce97e415bc5b5165cf3747f38214aa362e3e1bbeb1c0a2f7f91d29df08 370162 dchroot_1.6.4-1_amd64.deb 0a9794ad52699325f8a47133a6c4a537ce785c3fbdd7fbfefabf16fdf437d53e 369404 dchroot-dsa_1.6.4-1_amd64.deb Files: 87383d70bf468b85f6819647b467711d 2424 admin optional schroot_1.6.4-1.dsc 2398bec3e8f6de01c298c3a706488826 736200 admin optional schroot_1.6.4.orig.tar.xz 64fb0e90bee2d171386be9ce9ebc1e6f 30359 admin optional schroot_1.6.4-1.debian.tar.gz 187ae6283cb6e8d54c88b5f08a8440d7 267800 admin optional schroot-common_1.6.4-1_all.deb 98b4bd43ee9b27ecc331e37b2baf9d7b 2296982 libdevel optional libsbuild-dev_1.6.4-1_amd64.deb 9085f9ad193de4c4f124d79e102026f5 29133852 debug extra schroot-dbg_1.6.4-1_amd64.deb 2249aae8b78e35f6ffc7ded524292da2 8188950 doc optional libsbuild-doc_1.6.4-1_all.deb ae70fd138660e79530a724a5d3881fcc 966820 admin optional schroot_1.6.4-1_amd64.deb d5061daac3513fb1f9e91b7a2243e4d7 370162 admin optional dchroot_1.6.4-1_amd64.deb 66929b2080ed3e0309029e2f11bd8861 369404 admin optional dchroot-dsa_1.6.4-1_amd64.deb -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (GNU/Linux) iQIcBAEBCgAGBQJQjGrBAAoJEOJSSsUKn1xZsf8QAKx7J93EKXunOaPgNB/5RwR/ I1KMROr1XKKpHeucu7g5/FGMRz+j5/DLrYj3LR6aLWdI+eD9aoK85ZxRqWHA+l9E 0SGYFuQgHp4A4ZCxo0qwZT+NhaUIRYLojWrZIwbYAZiYF1ICwJVJ1yK3oVvgtwD8 6uj1Qi9yLR+7o0Lp/UJH9czdLkmSRiHibkgAK9k3IyDbRlqxO0PFJ83msSZHwmIt 3eLm9hrvmOOZaY4yNkFm6K+LXAumMRNsDw9Om0itZu7mXed//OO3aT2ZASFjSYxx u4X+JERWEkxPQLo7R8H1luQtUWNfVYiVIb7tvCCzcG8NSs4PZcdw5wxkdsvieXWh pruWAoXg1WfvMsQSg3uyVkjJxELw9KbA9gWMSBxOfTqrc/UCc1++HVrgSs00z2G8 FMqAs8Zf7Vtx5KGqd2s5OXdItuad1qWbFLyYZQ02zEZGVI7+F7aJVDL0FdhrJBzN NGTPwhofpOrj2LBz5fUjrS2uz8qox8FgSyxf1yk3261Hagj+t5Iqg7nPc/me6/hD EKB2/5bfiuJdnSEFCcX7xwNkRqeUhYURbrW8DfiZ1CKGecKhVDjhkMETMxEuXCBg vPjyPO7wQcymSLcawQvG6+R+svL0436sZZCeB7s8RFst8p+lThW4phBf9wwaXoQT iSDyjx3vf4dxNPtynfeR =IvFG -----END PGP SIGNATURE-----
--- End Message ---