Package: schroot; Maintainer for schroot is Christoph Biedl <debian.axhn@manchmal.in-ulm.de>; Source for schroot is src:schroot (PTS, buildd, popcon).
Reported by: Julien Viard de Galbert <julien@vdg.blogsite.org>
Date: Tue, 8 May 2012 14:54:05 UTC
Severity: normal
Tags: patch
Found in version schroot/1.4.25-1
Fixed in version schroot/1.5.2-1
Done: Roger Leigh <rleigh@debian.org>
Bug is archived. No further changes may be made.
View this report as an mbox folder, status mbox, maintainer mbox
Report forwarded
to debian-bugs-dist@lists.debian.org, julien@silicone.homelinux.org, Debian buildd-tools Developers <buildd-tools-devel@lists.alioth.debian.org>:
Bug#672113; Package schroot.
(Tue, 08 May 2012 14:54:09 GMT) (full text, mbox, link).
Acknowledgement sent
to Julien Viard de Galbert <julien@vdg.blogsite.org>:
New Bug report received and forwarded. Copy sent to julien@silicone.homelinux.org, Debian buildd-tools Developers <buildd-tools-devel@lists.alioth.debian.org>.
(Tue, 08 May 2012 14:54:09 GMT) (full text, mbox, link).
Message #5 received at submit@bugs.debian.org (full text, mbox, reply):
Package: schroot Version: 1.4.25-1+b1 Severity: normal Tags: patch Dear Maintainer, While using sbuild with a file schroot configuration I noticed that sometimes the session would not close. It appeared that some daemon was still running and keeping the filesystem busy. I'm using a tar with a toplevel directory containing the actual chroot content. My configuration looks like that: .... type=file file=/path/to/file.tar location=/squeeze Adding some debugging to 15killprocs I noticed that it misses the location part. So I tried the following change and it seams to fix it for me. diff --git a/etc/setup.d/15killprocs b/etc/setup.d/15killprocs index 3b679f5..7927ee7 100755 --- a/etc/setup.d/15killprocs +++ b/etc/setup.d/15killprocs @@ -84,5 +84,5 @@ do_kill_all() } if [ $STAGE = "setup-recover" ] || [ $STAGE = "setup-stop" ]; then - do_kill_all "$CHROOT_MOUNT_LOCATION" + do_kill_all "$CHROOT_PATH" fi Please double check that the change is correct and consider including it in a later release. Best Regards, Julien VdG -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'oldstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.38-2-amd64 (SMP w/2 CPU cores) Locale: LANG=C, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages schroot depends on: ii libboost-filesystem1.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-7 ii liblockdev1 1.0.3-1.4+b2 ii libpam0g 1.1.3-7.1 ii libstdc++6 4.7.0-7 ii libuuid1 2.20.1-4 ii schroot-common 1.4.25-1 schroot recommends no packages. Versions of packages schroot suggests: pn aufs-modules | unionfs-modules <none> pn btrfs-tools <none> pn debootstrap 1.0.40 pn lvm2 <none> -- no debconf information
Information forwarded
to debian-bugs-dist@lists.debian.org, Debian buildd-tools Developers <buildd-tools-devel@lists.alioth.debian.org>:
Bug#672113; Package schroot.
(Mon, 14 May 2012 20:33:08 GMT) (full text, mbox, link).
Acknowledgement sent
to Roger Leigh <rleigh@codelibre.net>:
Extra info received and forwarded to list. Copy sent to Debian buildd-tools Developers <buildd-tools-devel@lists.alioth.debian.org>.
(Mon, 14 May 2012 20:33:08 GMT) (full text, mbox, link).
Message #10 received at 672113@bugs.debian.org (full text, mbox, reply):
On Tue, May 08, 2012 at 04:52:32PM +0200, Julien Viard de Galbert wrote: > While using sbuild with a file schroot configuration I noticed that > sometimes the session would not close. It appeared that some daemon > was still running and keeping the filesystem busy. > > I'm using a tar with a toplevel directory containing the actual chroot > content. My configuration looks like that: > .... > type=file > file=/path/to/file.tar > location=/squeeze > > Adding some debugging to 15killprocs I noticed that it misses the > location part. So I tried the following change and it seams to fix it > for me. > > diff --git a/etc/setup.d/15killprocs b/etc/setup.d/15killprocs > index 3b679f5..7927ee7 100755 > --- a/etc/setup.d/15killprocs > +++ b/etc/setup.d/15killprocs > @@ -84,5 +84,5 @@ do_kill_all() > } > > if [ $STAGE = "setup-recover" ] || [ $STAGE = "setup-stop" ]; then > - do_kill_all "$CHROOT_MOUNT_LOCATION" > + do_kill_all "$CHROOT_PATH" > fi > > > Please double check that the change is correct and consider including it > in a later release. I'm not yet totally sure this is correct. For one of the chroots which fails, please could you run "schroot -v" and report what the values of CHROOT_MOUNT_LOCATION and CHROOT_PATH are when the setup scripts run on ending the session. For me, they are always identical, with LOCATION added to CHROOT_PATH if you have location=xxx in your configuration: I: 99check: CHROOT_MOUNT_LOCATION=/var/lib/schroot/mount/sid-file-ca2422b1-ce8b-4b91-9141-efc50cce55a9 I: 99check: CHROOT_PATH=/var/lib/schroot/mount/sid-file-ca2422b1-ce8b-4b91-9141-efc50cce55a9/sid In this case CHROOT_MOUNT_LOCATION is actually better, since it not only /includes/ CHROOT_PATH in the checks, it also will kill processes which are outside the chroot but which would cause the umount to fail (not for file, but certainly for lvm-snapshot and other related types). So in summary, I'm confused why the existing logic is not working for you given that it's actually encompassing (or should be encompassing) CHROOT_PATH. If it turns out this assumption is incorrect (and the above check will be invaluable in determining that), we can change it to maybe use either CHROOT_PATH or check both to be extra careful. Regards, Roger -- .''`. Roger Leigh : :' : Debian GNU/Linux http://people.debian.org/~rleigh/ `. `' schroot and sbuild http://alioth.debian.org/projects/buildd-tools `- GPG Public Key F33D 281D 470A B443 6756 147C 07B3 C8BC 4083 E800
Information forwarded
to debian-bugs-dist@lists.debian.org, Debian buildd-tools Developers <buildd-tools-devel@lists.alioth.debian.org>:
Bug#672113; Package schroot.
(Mon, 14 May 2012 23:18:03 GMT) (full text, mbox, link).
Acknowledgement sent
to Julien Viard de Galbert <julien@vdg.blogsite.org>:
Extra info received and forwarded to list. Copy sent to Debian buildd-tools Developers <buildd-tools-devel@lists.alioth.debian.org>.
(Mon, 14 May 2012 23:18:03 GMT) (full text, mbox, link).
Message #15 received at 672113@bugs.debian.org (full text, mbox, reply):
[Message part 1 (text/plain, inline)]
On Mon, May 14, 2012 at 09:30:34PM +0100, Roger Leigh wrote: > On Tue, May 08, 2012 at 04:52:32PM +0200, Julien Viard de Galbert wrote: > > While using sbuild with a file schroot configuration I noticed that > > sometimes the session would not close. It appeared that some daemon > > was still running and keeping the filesystem busy. > > > > I'm using a tar with a toplevel directory containing the actual chroot > > content. My configuration looks like that: > > .... > > type=file > > file=/path/to/file.tar > > location=/squeeze > > > > Adding some debugging to 15killprocs I noticed that it misses the > > location part. So I tried the following change and it seams to fix it > > for me. > > > > diff --git a/etc/setup.d/15killprocs b/etc/setup.d/15killprocs > > index 3b679f5..7927ee7 100755 > > --- a/etc/setup.d/15killprocs > > +++ b/etc/setup.d/15killprocs > > @@ -84,5 +84,5 @@ do_kill_all() > > } > > > > if [ $STAGE = "setup-recover" ] || [ $STAGE = "setup-stop" ]; then > > - do_kill_all "$CHROOT_MOUNT_LOCATION" > > + do_kill_all "$CHROOT_PATH" > > fi > > > > > > Please double check that the change is correct and consider including it > > in a later release. > First thanks for your quick answer. > I'm not yet totally sure this is correct. For one of the chroots > which fails, please could you run "schroot -v" and report what the > values of CHROOT_MOUNT_LOCATION and CHROOT_PATH are when the > setup scripts run on ending the session. > I'm not currently using the computer on which I saw the problem and was planning to actually setup the test before answering you, but I don't think this is needed because I totally agree with your next sentence: > For me, they are always identical, with LOCATION added to CHROOT_PATH > if you have location=xxx in your configuration: > > I: 99check: CHROOT_MOUNT_LOCATION=/var/lib/schroot/mount/sid-file-ca2422b1-ce8b-4b91-9141-efc50cce55a9 > I: 99check: CHROOT_PATH=/var/lib/schroot/mount/sid-file-ca2422b1-ce8b-4b91-9141-efc50cce55a9/sid > From what I've seen it's exactly that, CHROOT_PATH is CHROOT_MOUNT_LOCATION concatenated with "location". > In this case CHROOT_MOUNT_LOCATION is actually better, since it not > only /includes/ CHROOT_PATH in the checks, it also will kill processes > which are outside the chroot but which would cause the umount to > fail (not for file, but certainly for lvm-snapshot and other related > types). > This is where I disagree :) I would agree if the "do_kill_all" function was doing some call to "lsof" as I had to do to find out the offending process, but this function is not doing that. Instead it compares the entry in "/proc/PID/root/" with its parameter to find process that are run from within the chroot. So that's why I think the parameter should be the actual chroot path so CHROOT_PATH. > > So in summary, I'm confused why the existing logic is not working for > you given that it's actually encompassing (or should be encompassing) > CHROOT_PATH. If it turns out this assumption is incorrect (and the > above check will be invaluable in determining that), we can change it > to maybe use either CHROOT_PATH or check both to be extra careful. > When I first had the issue and was chasing it, I came across #391319 I know it's about 6 years old, it's when the script 15killprocs was created, and it pointed my investigation to its direction. But today, I just looked at it again and it seams to me that not killing process outside the chroot was considered a feature back then: May I quote message #15: | [...] If there are open files, we don't | want to kill anything /outside/ the chroot, which may also be using | the filesystem. I guess I should have written more of my analysis of the problem in my initial bugreport... But well I hope I made my point of view clearer now :) > > Regards, > Roger > Best Regards, Julien VdG -- Julien Viard de Galbert <julien@vdg.blogsite.org> http://silicone.homelinux.org/ <julien@silicone.homelinux.org> GPG Key ID: D00E52B6 Published on: hkp://keys.gnupg.net Key Fingerprint: E312 A31D BEC3 74CC C49E 6D69 8B30 6538 D00E 52B6
[signature.asc (application/pgp-signature, inline)]
Information forwarded
to debian-bugs-dist@lists.debian.org, Debian buildd-tools Developers <buildd-tools-devel@lists.alioth.debian.org>:
Bug#672113; Package schroot.
(Mon, 14 May 2012 23:36:03 GMT) (full text, mbox, link).
Acknowledgement sent
to Roger Leigh <rleigh@codelibre.net>:
Extra info received and forwarded to list. Copy sent to Debian buildd-tools Developers <buildd-tools-devel@lists.alioth.debian.org>.
(Mon, 14 May 2012 23:36:03 GMT) (full text, mbox, link).
Message #20 received at 672113@bugs.debian.org (full text, mbox, reply):
tags 672113 + pending thanks On Tue, May 15, 2012 at 01:15:49AM +0200, Julien Viard de Galbert wrote: > > In this case CHROOT_MOUNT_LOCATION is actually better, since it not > > only /includes/ CHROOT_PATH in the checks, it also will kill processes > > which are outside the chroot but which would cause the umount to > > fail (not for file, but certainly for lvm-snapshot and other related > > types). > > > This is where I disagree :) > > I would agree if the "do_kill_all" function was doing some call to > "lsof" as I had to do to find out the offending process, but this > function is not doing that. Instead it compares the entry in > "/proc/PID/root/" with its parameter to find process that are run > from within the chroot. So that's why I think the parameter should be > the actual chroot path so CHROOT_PATH. Ah, in this case your assessment is entirely correct. Committed into git and will be in the next upload. This should hopefully be tomorrow, to experimental, pending fixing one last build issue. Thanks, Roger -- .''`. Roger Leigh : :' : Debian GNU/Linux http://people.debian.org/~rleigh/ `. `' schroot and sbuild http://alioth.debian.org/projects/buildd-tools `- GPG Public Key F33D 281D 470A B443 6756 147C 07B3 C8BC 4083 E800
Added tag(s) pending.
Request was from Roger Leigh <rleigh@codelibre.net>
to control@bugs.debian.org.
(Mon, 14 May 2012 23:36:04 GMT) (full text, mbox, link).
Reply sent
to Roger Leigh <rleigh@debian.org>:
You have taken responsibility.
(Tue, 15 May 2012 22:39:39 GMT) (full text, mbox, link).
Notification sent
to Julien Viard de Galbert <julien@vdg.blogsite.org>:
Bug acknowledged by developer.
(Tue, 15 May 2012 22:39:39 GMT) (full text, mbox, link).
Message #27 received at 672113-close@bugs.debian.org (full text, mbox, reply):
Source: schroot
Source-Version: 1.5.2-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:
dchroot-dsa_1.5.2-1_amd64.deb
to main/s/schroot/dchroot-dsa_1.5.2-1_amd64.deb
dchroot_1.5.2-1_amd64.deb
to main/s/schroot/dchroot_1.5.2-1_amd64.deb
libsbuild-dev_1.5.2-1_amd64.deb
to main/s/schroot/libsbuild-dev_1.5.2-1_amd64.deb
libsbuild-doc_1.5.2-1_all.deb
to main/s/schroot/libsbuild-doc_1.5.2-1_all.deb
schroot-common_1.5.2-1_all.deb
to main/s/schroot/schroot-common_1.5.2-1_all.deb
schroot-dbg_1.5.2-1_amd64.deb
to main/s/schroot/schroot-dbg_1.5.2-1_amd64.deb
schroot_1.5.2-1.debian.tar.gz
to main/s/schroot/schroot_1.5.2-1.debian.tar.gz
schroot_1.5.2-1.dsc
to main/s/schroot/schroot_1.5.2-1.dsc
schroot_1.5.2-1_amd64.deb
to main/s/schroot/schroot_1.5.2-1_amd64.deb
schroot_1.5.2.orig.tar.xz
to main/s/schroot/schroot_1.5.2.orig.tar.xz
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 672113@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Roger Leigh <rleigh@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 ftpmaster@debian.org)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Format: 1.8
Date: Mon, 14 May 2012 23:29:22 +0100
Source: schroot
Binary: schroot-common libsbuild-dev schroot-dbg libsbuild-doc schroot dchroot dchroot-dsa
Architecture: source all amd64
Version: 1.5.2-1
Distribution: experimental
Urgency: low
Maintainer: Debian buildd-tools Developers <buildd-tools-devel@lists.alioth.debian.org>
Changed-By: Roger Leigh <rleigh@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: 477937 588962 625202 625205 648450 653732 658544 659524 659967 660040 661514 666274 666497 670881 672113
Changes:
schroot (1.5.2-1) experimental; urgency=low
.
* New upstream development release.
* Build with current Boost libraries (1.49).
* debian/control:
- Fix typo (debuggging, Closes: #653732). Thanks to Vincent Blut.
- Build-Depend on debhelper 9, and po4a 0.40.
- Upgrade to Standards-Version 3.9.3.
* schroot preinst: Remove default (script-config) conffiles on
upgrade. These are deprecated and support will be dropped in
the future.
* /etc/default/schroot supports ending sessions on stop
(Closes: #625202). The existing SESSIONS_RECOVER option has been
renamed to START_ACTION, and an additional STOP_ACTION option has
been added. Both of these may be set to "end" to cause all
sessions to be ended when run with a "start" or "stop" argument,
respectively.
* Support translation of the documentation with po4a
(Closes: #588962). A French translation of the manual pages has
been added, and translated manual pages are built, but is not yet
installed. Thanks to David Prévot.
* Support for overlayfs has been added in addition to aufs and
unionfs (Closes: #648450). Thanks to Evan Broder.
* Arbitrary options may now be set in a chroot definition in
schroot.conf. These options are also set in the environment when
running setup scripts, making this a simple means by which setup
scripts may be customised without writing code. As part of this
change, the error message for invalid keys has been reworded to
make it more helpful (Closes: #666274).
* The gshadow database is now copied into the chroot using the
nssdatabases setup script, rather than copyfiles.
* Services may be started and stopped inside the chroot on session
creation and session ending (Closes: #625205). These are specified
using the new setup.services key, and are started and stopped using
invoke-rc.d. See schroot.conf(5) for further details.
* 15killprocs kills processes under CHROOT_PATH rather than
CHROOT_MOUNT_LOCATION (Closes: #672113). Thanks to Julien Viard de
Galbert.
* The above options may be set (where permitted) on the schroot
command-line by using the new --option command-line option to set
the option to a user-defined value, which will permit users to
customise the behaviour of setup scripts. Note that only keys
specified in the new user-modifiable-keys or root-modifiable-keys
settings are permitted to be set, for security reasons.
* A new "custom" chroot type has been added (Closes: #477937). This
permits the testing and development of new specialised chroot
types without the need to write any C++ chroot modules. It just
requires a custom setup script, which can use arbitrary options
set in your schroot.conf for configuration. Options are provided
to set up the session cloning and purging behaviour for the custom
chroot. See schroot.conf(5) for further details.
* Exceptions thrown for command-line options validation errors no
longer use the Boost validation_error exception, which formatted
the exception reason text badly (Closes: #666497).
* schroot(1): Update overview text, including explaining the
restriction of the plain chroot type not running setup scripts
(Closes: #670881).
* PATH is now set when running setup scripts.
* Updated translations:
- da (Closes: #658544). Thanks to Joe Hansen.
- de (Closes: #659524). Thanks to Holger Wansing.
- fr (Closes: #661514). Thanks to Thomas Blein.
- pt (Closes: #660040). Thanks to Pedro Ribeiro.
- zh_CN (Closes: #659967). Thanks to Ji ZhengYu.
Checksums-Sha1:
46d95ae57ef81ae04d2bb942011a034791913c4e 2424 schroot_1.5.2-1.dsc
40377167864c508901882951a1c18ad65cbf744a 718344 schroot_1.5.2.orig.tar.xz
9eaf97eac6c0635ea18a37224b3e86255107b5c5 26764 schroot_1.5.2-1.debian.tar.gz
ea69f4484ca60bf980e71fc4fb4fc5c59f9610a6 252632 schroot-common_1.5.2-1_all.deb
b39961b61ce9d66f7263f622c882ed448b5e4dcc 2289162 libsbuild-dev_1.5.2-1_amd64.deb
b507d22255106284de74fcf04fd5eefc083180de 29677682 schroot-dbg_1.5.2-1_amd64.deb
0bbfcaa044a879c89a0f2a59e9914380c30b8eb6 7763476 libsbuild-doc_1.5.2-1_all.deb
4f055759337a3fd59358c1c03bfb50bcbaba028d 953368 schroot_1.5.2-1_amd64.deb
1ad84ef5033632d2ac6d3b6719bd6531811390db 370280 dchroot_1.5.2-1_amd64.deb
ebaace85d3790af293b5bad0f216099a02650a14 369528 dchroot-dsa_1.5.2-1_amd64.deb
Checksums-Sha256:
985e7a881b2a3e8b6060418c7b1a5601180986d1a7a0cab4dc2ac325622d8672 2424 schroot_1.5.2-1.dsc
14ea4c1fcd13fbccc4ac287d33e70ef26a804d85b803b60ee9d75a8f2c8eb9fc 718344 schroot_1.5.2.orig.tar.xz
70bc839e0671412f741d3cbf6a7553102464b0267e00bc744a4fcce24ce7f054 26764 schroot_1.5.2-1.debian.tar.gz
6d8610683e68a1df86c3b34cc563c832c8bae2c8cbaee3ab94c9032e61bc723f 252632 schroot-common_1.5.2-1_all.deb
ab4a95e673ee7a40b690d41cf78af152c2512a828fa5792acbb69b60876da779 2289162 libsbuild-dev_1.5.2-1_amd64.deb
5f9336e5b57b068be3c9402710dc4214dca940a547b0a860e66e38c43afa6a3a 29677682 schroot-dbg_1.5.2-1_amd64.deb
c01b9db96f89bf82ad216f24fad5bb006fa5069ad9bc983d6d14c35ae41125b8 7763476 libsbuild-doc_1.5.2-1_all.deb
06f8da78707c2296ee7c6e6df901f514155261d4747de74007faa8a5e351f9e5 953368 schroot_1.5.2-1_amd64.deb
cadf5c34c73eb39f834decc5f810bb7b4f82a929ffb9ca656a10019e46b291ca 370280 dchroot_1.5.2-1_amd64.deb
65edb882f2439af91bed0f558c8680ecc0160d1dacf0e3903c2b35a09f255897 369528 dchroot-dsa_1.5.2-1_amd64.deb
Files:
b6a925b56f5088359e2656a98cae4d0c 2424 admin optional schroot_1.5.2-1.dsc
7504d34970697b951896a4e36bb07bd3 718344 admin optional schroot_1.5.2.orig.tar.xz
92721f1e16d859c2373217a444d64f5d 26764 admin optional schroot_1.5.2-1.debian.tar.gz
4b568fe66dec35daca987dbaf8396e2a 252632 admin optional schroot-common_1.5.2-1_all.deb
1655225f16ac6632e0d04827b06c2173 2289162 libdevel optional libsbuild-dev_1.5.2-1_amd64.deb
48188da135046620adea7a2b6e88caee 29677682 debug extra schroot-dbg_1.5.2-1_amd64.deb
ff44d0b8eacc08ad16ec99b1f2e10f83 7763476 doc optional libsbuild-doc_1.5.2-1_all.deb
980c18a88ff2a6d2d0cbb29b2fea87f7 953368 admin optional schroot_1.5.2-1_amd64.deb
5d615c646ece726b00c420e72b9b1be4 370280 admin optional dchroot_1.5.2-1_amd64.deb
1fc394e3a7065f9661eefde1f0db6178 369528 admin optional dchroot-dsa_1.5.2-1_amd64.deb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
iQIcBAEBCgAGBQJPstEUAAoJEOJSSsUKn1xZwBIQALGJpz3JiKJK2xe2zAO9d5OT
PFdr3OzbjmFFVGnZHHde/0KohZ9OdAlMDUNr5CiDT73CcMkUOwSJJkSIhFsAUi5M
1awCYcsejTAUxSyKXimqDPdvI+e2jkWZ5xwaQX5fmCJ8fwN6pFyNizE83TepdiOU
jV0o6kJKKbXYtQCRGufxQPuxQAMWn8r4zdGLnLX8sucvznnFQoH33OhhJwhdaDj5
u3tJATFGvpcgoJ4G6OXHpeEc6t/S14Pm8XybFV03uFjQy/8WVSPLG5zYjvTnm2qx
5TZpUyIo9BMCzJgil1ZSa2Kw86nt/wwwmTa+ARDPokZIkHhh9hld9ma8P5EKkyqh
aNfPejbHm4xZ8s0zEWKjwK+Y+A5Dqdhf7oM7nMjewfgdrGSpPiVXuAbF2xImjt/T
iOzqoz+qRQ/PHLmPLfEZd1o3R84hN1kwPP9m0v8alUs8lAZahXHgpYIK0zrMMj2C
QjCcRLY3tU5Qbmh+XH5znSrdaRrnzOLggnT0Zl3/OXuZ0BYW/yEELvkb3fwC9dqO
6DrJu0kbcmU7QJudAQZs/nFXPrPGOmZLRHlo/nOl72k9Pvy/wvHVm4nQU2W3+YlE
BCiuc6M6u6CGChlmlIh9DSWCBLhyQsxnUxZ122ozROxgIEJiTzd1FbWKaFMwHDS5
ef8AeAx73TI91bVK4rpG
=r2bS
-----END PGP SIGNATURE-----
Bug archived.
Request was from Debbugs Internal Request <owner@bugs.debian.org>
to internal_control@bugs.debian.org.
(Thu, 28 Jun 2012 07:36:11 GMT) (full text, mbox, link).
Send a report that this bug log contains spam.
Debbugs is free software and licensed under the terms of the GNU Public License version 2. The current version can be obtained from https://bugs.debian.org/debbugs-source/.
Copyright © 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson, 2005-2017 Don Armstrong, and many other contributors.