[buildd-tools-devel] Bug#676386: schroot: Permit session-specific settings

[Daniel Dehennin]

Package: schroot
Version: 1.5.4-1
Severity: wishlist

Dear Maintainer,

It could be great to be able to use eatmydata only for non source
snapshot schroots.

This will avoid trashing the source when doing a upgrade.

Thanks.

IRC Log:
--------

<nebuchadnezzar> rleigh: hi, using eatmydata in snapshoted schroot by
adding "command-prefix=eatmydata" in /etc/schroot/chroot.d/$chroot.conf,
but is there a way to avoid using it for source chroot <nebuchadnezzar>
for example, I don't want to trash my source schroot when upgrading it
[...]
<rleigh> We should probably add the facility to have session-specific
settings. e.g. session.command-prefix and/or source.command-prefix, for
example, which are only used for that specific situation.


-- System Information:
Debian Release: wheezy/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (90, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 3.4.0+hati.2 (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
ii  libboost-iostreams1.49.0        1.49.0-3
ii  libboost-program-options1.49.0  1.49.0-3
ii  libboost-regex1.49.0            1.49.0-3
ii  libboost-system1.49.0           1.49.0-3
ii  libc6                           2.13-32
ii  libgcc1                         1:4.7.0-11
ii  liblockdev1                     1.0.3-1.4+b2
ii  libpam0g                        1.1.3-7.1
ii  libstdc++6                      4.7.0-11
ii  libuuid1                        2.20.1-5
ii  schroot-common                  1.5.4-1

schroot recommends no packages.

Versions of packages schroot suggests:
pn  aufs-modules | unionfs-modules  <none>
pn  btrfs-tools                     0.19+20120328-2
pn  debootstrap                     1.0.40
pn  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
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 229 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/buildd-tools-devel/attachments/20120606/57a0cd11/attachment-0001.pgp>