Processed: It is not caffe that is broken
Processing control commands: > tags -1 moreinfo Bug #921299 [src:caffe] caffe: FTBFS with upcoming doxygen 1.8.15 Added tag(s) moreinfo. > reassign -1 doxygen Bug #921299 [src:caffe] caffe: FTBFS with upcoming doxygen 1.8.15 Bug reassigned from package 'src:caffe' to 'doxygen'. No longer marked as found in versions caffe/1.0.0+git20180821.99bd997-2. Ignoring request to alter fixed versions of bug #921299 to the same values previously set > retitle -1 "Doxygen breaks caffe" Bug #921299 [doxygen] caffe: FTBFS with upcoming doxygen 1.8.15 Changed Bug title to '"Doxygen breaks caffe"' from 'caffe: FTBFS with upcoming doxygen 1.8.15'. -- 921299: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921299 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#760423: marked as done (lighttpd: systemd service does not automatically create /var/run/lighttpd)
Your message dated Thu, 14 Feb 2019 12:03:02 +0100 with message-id <20190214110258.jpjjmsxu5v7qfq32@laureti-dev> and subject line Re: Bug#760423: lighttpd: systemd service does not automatically create /var/run/lighttpd has caused the Debian Bug report #760423, regarding lighttpd: systemd service does not automatically create /var/run/lighttpd 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.) -- 760423: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=760423 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: lighttpd Version: 1.4.35-3 Severity: important Dear Maintainer, When switching to systemd, the directory /var/run/lighttpd is not automatically created (and chown www-data), causing the resulting service to fail. A workaround is to manually create the directory with the right ownership, but I have not verified if this persists across restarts. Please automatically create the directory if it does not already exist. -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.14-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages lighttpd depends on: ii init-system-helpers 1.21 ii libattr11:2.4.47-1 ii libbz2-1.0 1.0.6-7 ii libc6 2.19-9 ii libfam0 2.7.0-17.1 ii libldap-2.4-2 2.4.39-1.1+b1 ii libpcre31:8.35-3 ii libssl1.0.0 1.0.1i-2 ii libterm-readline-perl-perl 1.0303-1 ii lsb-base4.1+Debian13 ii mime-support3.56 ii perl5.18.2-7 ii systemd 208-8 ii zlib1g 1:1.2.8.dfsg-1 Versions of packages lighttpd recommends: ii spawn-fcgi 1.6.4-1 Versions of packages lighttpd suggests: ii apache2-utils 2.4.10-1 ii openssl1.0.1i-2 pn rrdtool -- Configuration Files: /etc/lighttpd/lighttpd.conf changed [not included] /etc/logrotate.d/lighttpd changed [not included] -- no debconf information --- End Message --- --- Begin Message --- Hi, On Tue, Dec 04, 2018 at 09:14:12AM +0100, Helmut Grohne wrote: > Can you reproduce the issue at all? If no, please close the bug. I received a private reply that the bug likely no longer exists. It could have been connected to a switch from sysvinit to systemd. I also wondered whether possibly the tmpfile snippet wasn't run in postinst, because it wasn't debian/$pkg.tmpfile, but indeed debhelper does pick up manually installed tmpfiles and creates the relevant postinst snippet. My other theory thus proved wrong. I don't think there is anything actionable left on this bug and therefore close it. Helmut--- End Message ---
Nieuws - goud is een onmisbare bescherming voor schuldenberg van 250 miljard
Beste lezer, We leven in een gepolariseerde wereld vol onzekerheden en die onzekerheden werpen een steeds grotere schaduw af over de economie en over de financiële markten. Eigenlijk is onze wereld een surrealistisch plaatje geworden: iedereen blijft maar schulden maken, we leven er op los alsof er geen morgen bestaat. Zowel overheden, particulieren als bedrijven steken zichzelf steeds dieper in de schulden. Over het juiste bedrag van de uitstaande schulden verschillen de meningen, maar inmiddels zou het al gaan om een bedrag van meer dan 250.000 miljard dollar. Daarbij is rekening gehouden met alle openstaande verplichtingen van de overheden, inclusief sociale zekerheid, pensioenen enzovoort. Zelfs een klein kind zal beseffen dat de huidige situatie niet kan blijven duren, vroeg of laat zal er ergens een radertje vast lopen. En dan zal de (schulden)wagen aan het rollen gaan. GoldCore merkt op dat de globale debt-to-GDP ratio, zeg maar de verhouding schulden ten opzichte van het BBP, is opgelopen tot bijna 320%. Het hoeft geen betoog dat dergelijke verhouding astronomisch hoog is. Mathematisch gezien is het simpelweg onmogelijk geworden om de uitstaande schulden nog ooit terug te betalen. Het vervelende aan schulden is echter dat ze steeds op een bepaald moment in de toekomst terugbetaald moeten worden. De boodschap van GoldCore is dan ook duidelijk: de beleggers krijgen het advies om beschutting op de goudmarkt te zoeken tegen het uit de hand lopen van de schuldensituatie. Goud, zilver en in mindere mate de andere edelmetalen zullen hun waarde behouden wanneer de schuldenzeepbel implodeert, obligaties, aandelen, vastgoed, valuta’s enzovoort zullen dat in veel mindere mate doen. Een explosie van de goudprijs ligt dan ook in de lijn van de verwachtingen, zonder dat GoldCore zich waagt aan een voorspelling omtrent het toekomstig niveau van de goudprijs. Maar dat dit fors boven het huidige prijsniveau ligt, staat als een paal boven water [https://cdn.flxml.eu/lt-2161182922-bdd68f1b548e97dd159e723a4dd67de57dec5ef454e14522][1] ![2] [1]: https://cdn.flxml.eu/lt-2161182922-bdd68f1b548e97dd159e723a4dd67de57dec5ef454e14522 "https://cdn.flxml.eu/lt-2161182922-bdd68f1b548e97dd159e723a4dd67de57dec5ef454e14522"; [2]: https://cdn.flxml.eu//dyn/images/smartbuilder/transparent.png
Bug#921779: Bug#919413: cascade of FTBFS
On Tuesday, 12 February 2019 16:54:12 CET Andreas Tille wrote: > I'm > not sure how to deal with the jquery.js one since this is potentially an > issue with lots of dependencies - I remember discussions about this > which I did not followed. Fortunately, jquery is available as a Debian package. We had a similar issue with libmojolicious-perl. This package now: - removes jquery from source tarball [1] using debian/copyright Files-excluded parameter - depends on libjs-jquery - provides a symlink to Debian's query instead of the regular jquery file using debian/libmojolicious-perl.links file [2] HTH [1] https://salsa.debian.org/perl-team/modules/packages/libmojolicious-perl/blob/master/debian/copyright#L7 [2] https://salsa.debian.org/perl-team/modules/packages/libmojolicious-perl/blob/master/debian/libmojolicious-perl.links
Bug#921779: Bug#919413: cascade of FTBFS
Hi Dominique, see below Il 14/02/2019 15:16, Dominique Dumont ha scritto: On Tuesday, 12 February 2019 16:54:12 CET Andreas Tille wrote: I'm not sure how to deal with the jquery.js one since this is potentially an issue with lots of dependencies - I remember discussions about this which I did not followed. Fortunately, jquery is available as a Debian package. We had a similar issue with libmojolicious-perl. This package now: - removes jquery from source tarball [1] using debian/copyright Files-excluded parameter - depends on libjs-jquery - provides a symlink to Debian's query instead of the regular jquery file using debian/libmojolicious-perl.links file [2] HTH [1] https://salsa.debian.org/perl-team/modules/packages/libmojolicious-perl/blob/master/debian/copyright#L7 [2] https://salsa.debian.org/perl-team/modules/packages/libmojolicious-perl/blob/master/debian/libmojolicious-perl.links I 'm afraid we will not be able to avoid embedding jquery in doxygen, because it makes a weird use of it. The matter has been nicely put down by the former maintaners, see: https://salsa.debian.org/paolog-guest/doxygen/blob/master/debian/README.jquery Paolo
Bug#921779: Bug#919413: cascade of FTBFS
On Thu, Feb 14, 2019 at 03:16:22PM +0100, Dominique Dumont wrote: > On Tuesday, 12 February 2019 16:54:12 CET Andreas Tille wrote: > > I'm > > not sure how to deal with the jquery.js one since this is potentially an > > issue with lots of dependencies - I remember discussions about this > > which I did not followed. > > Fortunately, jquery is available as a Debian package. Sure it is. I simply remember some discussions about why doxygen needs its own jquery. I'd be really happy if this is not the case any more. Kind regards Andreas. -- http://fam-tille.de
Bug#907614: marked as done (vmdb2: please provide documentation)
Your message dated Thu, 14 Feb 2019 17:21:44 + with message-id and subject line Bug#907614: fixed in vmdb2 0.13.2+git20190214-1 has caused the Debian Bug report #907614, regarding vmdb2: please provide documentation 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.) -- 907614: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=907614 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: vmdb2 Version: 0.13.2-1 Severity: normal Hi, I am a user of autopkgtest and vmdebootstrap and stumbled across #904972. I would like to come up with a good replacement of vmdebootstrap using vmdb2. So I installed the package and wanted to read it's man page. But there is none. Looking into the package contents there doesn't seem to be any other kind of documentation either. I'm at a loss now as to how to make use of the vmdb2 package. The only thing I found was its --help output but that just seems to suggest that I need to create a config file of unknown format. Could you please provide documentation of vmdb2 in its binary package? Thanks! cheers, josch --- End Message --- --- Begin Message --- Source: vmdb2 Source-Version: 0.13.2+git20190214-1 We believe that the bug you reported is fixed in the latest version of vmdb2, 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 907...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Gunnar Wolf (supplier of updated vmdb2 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...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Tue, 12 Feb 2019 09:17:52 -0600 Source: vmdb2 Binary: vmdb2 Architecture: source all Version: 0.13.2+git20190214-1 Distribution: unstable Urgency: medium Maintainer: Gunnar Wolf Changed-By: Gunnar Wolf Description: vmdb2 - creator of disk images with Debian installed Closes: 907614 914027 Changes: vmdb2 (0.13.2+git20190214-1) unstable; urgency=medium . * New upstream version. * Add dependency and build-dependency on qemu-utils, for qemu-img. * Updated Homepage. * Build the manual and include it in the Debian package. (Closes: #907614) * Add build-dependcies for building docs. * Taking over maintainership, as upstream author retired from Debian, orphaning vmdb2 (Closes: #914027) * Bumping up standards-version 3.9.8 → 4.3.0, dh compat level 9 → 12 * Get the version information from debian/changelog instead of git, fixing potential (not reported) FTBFS Checksums-Sha1: 4474bfd5d90af77ad0b4c0fea23882f0bd3ceb2f 1956 vmdb2_0.13.2+git20190214-1.dsc 3dcad379d970d209f8d2e1973366e8771da8d74d 31911 vmdb2_0.13.2+git20190214.orig.tar.gz d3760b43414e4433fb257103f96754a8bb9a7b38 2568 vmdb2_0.13.2+git20190214-1.debian.tar.xz 5bc1e986ef71105475fd7f1f52102137ef2e17d3 69632 vmdb2_0.13.2+git20190214-1_all.deb df73b782c647131b7f713d1d6849abf6c84b2abe 11756 vmdb2_0.13.2+git20190214-1_amd64.buildinfo Checksums-Sha256: ec11a6f15eac577e5df20fd99d00c86e93c737677fd79d2f105a398eaf705a97 1956 vmdb2_0.13.2+git20190214-1.dsc 87eda3ab6a4137a57d4ce737d88bacc2a67303d96033f1535bdcba4210830ab9 31911 vmdb2_0.13.2+git20190214.orig.tar.gz 34581dc9ed8bdf4667e1b9e041fffdec7a13e163ae1f3eb8b6c2020d9e5c5c61 2568 vmdb2_0.13.2+git20190214-1.debian.tar.xz ef95d392827eace0b107845e79a4e8697294f0368946b801d6635946cf661297 69632 vmdb2_0.13.2+git20190214-1_all.deb e5f330c144d7c89bac54a982c727e786d807fa42af50f58e17d5152e1118012f 11756 vmdb2_0.13.2+git20190214-1_amd64.buildinfo Files: 292b54e5f09f96f6abb448464b39b952 1956 admin optional vmdb2_0.13.2+git20190214-1.dsc e84283c277c14b149562c2e703aa2d0f 31911 admin optional vmdb2_0.13.2+git20190214.orig.tar.gz ab36f2aafcc7d1d19747df98512ed4ab 2568 admin optional vmdb2_0.13.2+git20190214-1.debian.tar.xz d4885da916390c7935e26341838f5460 69632 admin optional vmdb2_0.13.2+git20190214-1_all.deb c4d4afa930d9637ec13744ef746e 11756 admin optional vmdb2_0.13.2+git20190214-1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEfHleU5lojd9m99YgSd0qTkl5YZwFAlxlnQ0ACgkQSd0qTkl5 YZz4bg//c8ty+6QoQw6GZr486/6WgMY/cDk63F+3sds2mHUF7BURXXeHeEeSahNo GWxbq76XMtp+Hyd0UOg0vZbWQKHCSR5ex4w8peEQLodRJJ7iXRUewNW/RrGTpiaJ GAikgYf+FFakMCtGbxGT7Zz
Processing of pepperflashplugin-nonfree_1.8.4_source.changes
pepperflashplugin-nonfree_1.8.4_source.changes uploaded successfully to localhost along with the files: pepperflashplugin-nonfree_1.8.4.dsc pepperflashplugin-nonfree_1.8.4.tar.xz pepperflashplugin-nonfree_1.8.4_amd64.buildinfo Greetings, Your Debian queue daemon (running on host usper.debian.org)
pepperflashplugin-nonfree_1.8.4_source.changes ACCEPTED into unstable
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Fri, 15 Feb 2019 01:29:52 +0800
Source: pepperflashplugin-nonfree
Architecture: source
Version: 1.8.4
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group
Changed-By: Shengjing Zhu
Closes: 858759 880710 886487 912673
Changes:
pepperflashplugin-nonfree (1.8.4) unstable; urgency=medium
.
* QA upload.
* Set Maintainer to Debian QA Group
* Remove unused pubkey-google.txt
* Update package description to reflect the current
implementation (Closes: #912673)
* Add i386 to package architecture (Closes: #886487)
* Convert package to git and set Vcs-{Browser,Git} field
* Use install command to copy files (Closes: #880710)
* Fix wget using verbose option all the time (Closes: #858759)
* Remove hal from Suggests, hal has been removed from archive
Checksums-Sha1:
a10ffad38d45d6490ea9923f7b41e6922276382f 1387
pepperflashplugin-nonfree_1.8.4.dsc
b48af8a0743ec77966c82183dfe54bb5790682c0 5108
pepperflashplugin-nonfree_1.8.4.tar.xz
1fc6918a95d7d8e6aad9bd41ec2110411d31e061 4821
pepperflashplugin-nonfree_1.8.4_amd64.buildinfo
Checksums-Sha256:
ac90947d09c3fd4a3977b5c85fde8a57ca71e5c4b052d3fa9520a47f0c40c0af 1387
pepperflashplugin-nonfree_1.8.4.dsc
223f6605db9e747deabe74741cc1c28e6c04f3acfef971dbaae7dac6434b10ad 5108
pepperflashplugin-nonfree_1.8.4.tar.xz
c3ad5ecef8578c046bb2c27759f651bfa32d19febd0174a25db6b1e1ce12ca4f 4821
pepperflashplugin-nonfree_1.8.4_amd64.buildinfo
Files:
4961fbaedad13b4a22437a2098533d92 1387 contrib/web optional
pepperflashplugin-nonfree_1.8.4.dsc
fe3acf49f6ec40d9d5db05db15b1a857 5108 contrib/web optional
pepperflashplugin-nonfree_1.8.4.tar.xz
640638d834c921c6fe35725d46d97ad0 4821 contrib/web optional
pepperflashplugin-nonfree_1.8.4_amd64.buildinfo
-BEGIN PGP SIGNATURE-
iQFEBAEBCgAuFiEE85F2DZP0aJKsSKyHONAPABi+PjUFAlxlppUQHHpoc2pAZGVi
aWFuLm9yZwAKCRA40A8AGL4+NbzqB/41p5dOJVSaxQm2fIgULz4tRv9rMpTP1LQX
x9vqHHsSxJ44t3xSEZY1040b8PYZBA3BcLQyrut4/R+vqVmgu8VgvZ5kyhQk8Zsq
PqEYuFKa2FbedmW75gvnseqBTtRxR0urxKrG/9bWKyphnVDwAFoROgK12CfkZWq1
HXAb5GLsz9FWZXjI75oU8YVt034GvevLotSkIKPp+WO9w7CJS7mE0EJbGDHEJT+S
5+l+ll8CAolc+wtGLZdd7R6CvjwMZeFwEmItP4Fwiju1t9F4c5+W3P5U+QqgImIC
zhQUsL61VOOa1cOEjBL5ZevVp/HkFkUsa1ndNDSLdWaIc//v6YbW
=IQEC
-END PGP SIGNATURE-
Thank you for your contribution to Debian.
Processing of zbar_0.21-1~exp1_source.changes
zbar_0.21-1~exp1_source.changes uploaded successfully to localhost along with the files: zbar_0.21-1~exp1.dsc zbar_0.21.orig.tar.gz zbar_0.21-1~exp1.debian.tar.xz zbar_0.21-1~exp1_amd64.buildinfo Greetings, Your Debian queue daemon (running on host usper.debian.org)
zbar_0.21-1~exp1_source.changes ACCEPTED into experimental
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 14 Feb 2019 15:51:03 -0500 Source: zbar Architecture: source Version: 0.21-1~exp1 Distribution: experimental Urgency: medium Maintainer: Debian QA Group Changed-By: Boyuan Yang Changes: zbar (0.21-1~exp1) experimental; urgency=medium . * QA upload. * New upstream release 0.21. * debian/watch: Monitor new upstream on GitHub. * debian/control: - Drop build-dependency on dh-exec, no longer necessary. * debian/gbp.conf: Disable gbp-import-orig postimport hook, it is useless now. * debian/rules: + Completely rewrite and use the dh sequencer. + use override_dh_strip to generate automatic debug packages. * debian/patches: - Drop all patches, merged or fixed upstream. + Cherry-pick upstream fixes on stable-0.21 branch till 20190214. + Add a patch to fix typos found by codespell. Checksums-Sha1: 6e53544faed09de5d246b1bdb8ca76d11deee9c3 2465 zbar_0.21-1~exp1.dsc c5e2e7db00c7d9669ecee1430d0a5ad3efaf8194 937718 zbar_0.21.orig.tar.gz 2374b1f676483f1002013a8ea331a242ed1a754e 15064 zbar_0.21-1~exp1.debian.tar.xz 5048f0af5abb8165dc48f079ecc7a7c6ce05f345 19898 zbar_0.21-1~exp1_amd64.buildinfo Checksums-Sha256: cc9a46ef5b3cd0c51e2d57dd7e34dee35480a03a19c7c55104fa42b94ae7d0ea 2465 zbar_0.21-1~exp1.dsc 98f8fa2a463743467c7ab331fa1f16c6c8a4c3e7cd11aef459f6566043d62cc2 937718 zbar_0.21.orig.tar.gz 06d402932094ef96c69ce34afd1e986519e215c2047404c9e05aa2b98afd009e 15064 zbar_0.21-1~exp1.debian.tar.xz 4ae0b9e337216bb4e603ef02c7b26a6330f7d8789090f9ad9b29db5be91b4a00 19898 zbar_0.21-1~exp1_amd64.buildinfo Files: 8e165bed0743206791df41c8b631364c 2465 libs optional zbar_0.21-1~exp1.dsc 42d7eaa228f77b4d759a070ccedf483f 937718 libs optional zbar_0.21.orig.tar.gz a2c020eb9082fb88bea1eab7a2811373 15064 libs optional zbar_0.21-1~exp1.debian.tar.xz 58b62ae68b431054dc8fa7338c29e408 19898 libs optional zbar_0.21-1~exp1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEfncpR22H1vEdkazLwpPntGGCWs4FAlxl3nYACgkQwpPntGGC Ws6T0w/+PkrdMbSv8BbKIZ0QZ51qN/9maRYP1MjfJxpbpvWyUyjDAzG/dS22QIHh pcTexGSoslov7EafAp1dMU8sGSN6Kj6DZ+ME39WB2vmgg+XrWtz/I4+pZRIepxEQ ngfnntFd1su47i6c2+LITGiMV2NCwXAasIYEs0laMp9KhwdAYD2uPq7yYuthaIAd K9rUnDa5jXcEyY98CxDOrFszig4ZqJw3ZqshTazkdeLYpYDH7gwC50ahGC3ZIYmY yS25uEtpG5ECMhk/SX1mP4/4YY1qGEJXwQBnU6BpWaLiI1aS6GZfcESB5VI01krM tva+c55yrDrgvW/UVLOwue4prLRXMbOQVfn1ijpxp9VuKxr2zAMgItlbcIL+VQgP wSfJNvHOh3n23TE+NjkojfHAykYcz7oP5IpB8igbLoX12/6z/rlg21QHk2vNr8Jt mBmy18IkD2X5/UQQDR167kRobo7uz9ebauqT6KVPDnoUzQ0/qK3QT/2IO2kHE01e lcCuURS7Tdk/gl3yD73qGnhoyrSWwYkeq4UADq0NC6eSS9f/IvwiH7NXznqzmr9B +zYawqUU54uct3CNvq30988InKnv0sRYyOYtGEJ16HtrlzNgwhX8Z0O7OkvlO226 yJnWHZivprMR/XlfsxzSd7lB/03ZhZIUAbMObfXAcrua84zGjAc= =ueTb -END PGP SIGNATURE- Thank you for your contribution to Debian.
Processed: Mark upstream marker for zbar python3 migration
Processing commands for cont...@bugs.debian.org: > forwarded 888303 https://github.com/mchehab/zbar/issues/27 Bug #888303 [src:zbar] zbar: Ship python3-zbar package Set Bug forwarded-to-address to 'https://github.com/mchehab/zbar/issues/27'. > thanks Stopping processing here. Please contact me if you need assistance. -- 888303: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=888303 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processing of zbar_0.21-1_source.changes
zbar_0.21-1_source.changes uploaded successfully to localhost along with the files: zbar_0.21-1.dsc zbar_0.21-1.debian.tar.xz zbar_0.21-1_amd64.buildinfo Greetings, Your Debian queue daemon (running on host usper.debian.org)
zbar_0.21-1_source.changes ACCEPTED into unstable
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 14 Feb 2019 18:32:38 -0500 Source: zbar Architecture: source Version: 0.21-1 Distribution: unstable Urgency: medium Maintainer: Debian QA Group Changed-By: Boyuan Yang Changes: zbar (0.21-1) unstable; urgency=medium . * QA upload. * Upload onto unstable. * debian/control: Update homepage with current GitHub project. Checksums-Sha1: 1be515688c6d6e43ab5d0727d288ef5d5e11d4ff 2448 zbar_0.21-1.dsc c3735c7e0c11939d1475f2ea67887fdc17629178 15236 zbar_0.21-1.debian.tar.xz f27af98b81c288d56ba7d3b8a4c561d3e763302b 19668 zbar_0.21-1_amd64.buildinfo Checksums-Sha256: 0222b2b4e208a82d29ce2ba2ed1ea26b15acf5336460b566427e557d74cb9fd7 2448 zbar_0.21-1.dsc 8a5e842020beacf41e95708110ebc09af63f70c0ea91d6ef49c83ce947c98b3c 15236 zbar_0.21-1.debian.tar.xz 6b80a885937463237c2168938287050b7dfebba3c689ffba8740efbe6851e476 19668 zbar_0.21-1_amd64.buildinfo Files: e3ccdf173cbfae4741d5fa5ee3c37f99 2448 libs optional zbar_0.21-1.dsc 1d359889c79a6eb678997b78b633a5ee 15236 libs optional zbar_0.21-1.debian.tar.xz 64b16467ca6d9c7c521def61e2d8620f 19668 libs optional zbar_0.21-1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEfncpR22H1vEdkazLwpPntGGCWs4FAlxl/VwACgkQwpPntGGC Ws4Qaw/+Pbphu2hp0nScE2nl7exxXfD9DSNDCvocnmJP6Wafzu/RkwwX70aBvm1V P27yDmz5Uqis7TnGK02q8qWwSsnAcgs5KmC456Qf64JQUcWIlYiEKEtvbifi9K5S puG5vCBwhYXVv/jdlBhKPUapMKYTFfJm/8RHqM7gJPtS7W9u+S1+/GeflAbDm0ar H5mMQT8RvLi3CZkZOjvQn0ACQCbaSc//RHe6Wxku661vSWsrc7rHC5lbb6ewL53W suKmosZ/a87ynkfLnkvtMnSCUASbM4CFuBv9Nt43F8ichhRWYeaunry7hZC036GH Kg6gj7VAGogTTcIzGNApfhTie+ba6eqqrBGuqDnIIxhQSmkS1Hk4BILwG7X5ZZ1I NAEfgEVFyU5rXYkPpZ26Dm2hbIfnVI4qUIgfWwWDMXP1vCVIx17+nNofx37lSqwC 54QaxDDMYoh26LL5eCu01/ZCzVWuMNLC2OymqF1lpCe+R+TtFKsQIzInl6a5wWAA XjJtoHnI5JiM6Gp2YiNWWhAqAQJi2L2Oe+4brP2P1TBHgGNHBOauotxIEYf6SnOu yWPzHBeE/mBQ7nTjfAbnpT2CH9/4E+mK21kcb3JGJR0jlTOVqvellqgtOUXiVb7F paCfHhU4tusxjiEAdl2z0Bpd8TTGvlMfTI6z4aUvPSnuyKELM/8= =CzY1 -END PGP SIGNATURE- Thank you for your contribution to Debian.
Processing of zbar_0.21-2_source.changes
zbar_0.21-2_source.changes uploaded successfully to localhost along with the files: zbar_0.21-2.dsc zbar_0.21-2.debian.tar.xz zbar_0.21-2_amd64.buildinfo Greetings, Your Debian queue daemon (running on host usper.debian.org)
zbar_0.21-2_source.changes ACCEPTED into unstable
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 14 Feb 2019 18:58:42 -0500 Source: zbar Architecture: source Version: 0.21-2 Distribution: unstable Urgency: medium Maintainer: Debian QA Group Changed-By: Boyuan Yang Changes: zbar (0.21-2) unstable; urgency=medium . * QA upload. * debian/zbar-tools.install: Use dh-exec again to selectively install zbarcam for linux-any only. Checksums-Sha1: 78c3a5514e2a87dfe34ab3e5ae011c6eef923323 2457 zbar_0.21-2.dsc e9df4413bec9c114f9fcf607344a1f72eda67851 15296 zbar_0.21-2.debian.tar.xz b38a8fa6525e7c5721bb9c2ac686a2628cff7cf6 19689 zbar_0.21-2_amd64.buildinfo Checksums-Sha256: 08074cb17d42f00cd401e4a2c049ecadd75341fd2845542afa40af00dd8dd173 2457 zbar_0.21-2.dsc a2fb277ac2df0b94dbc96c56ce408c22e7eeedcd5bd1646b4dd9736fd17bc2fc 15296 zbar_0.21-2.debian.tar.xz 0a1554cc93c388c8e1cf4846bdf4fac398df1657835318826a8074368f8ae9e7 19689 zbar_0.21-2_amd64.buildinfo Files: 1318723364b20d0b667876ab7b4807e5 2457 libs optional zbar_0.21-2.dsc 2463fe8b372e014301bf0e0414a7f95f 15296 libs optional zbar_0.21-2.debian.tar.xz d7f2b61275ba4171be48c193582d397d 19689 libs optional zbar_0.21-2_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEfncpR22H1vEdkazLwpPntGGCWs4FAlxmBFsACgkQwpPntGGC Ws5esQ/9EjTG3m6rcQxYX101xzlwYe8M5L829SiD7UhhEILaU4if/obAmDnbwHjN jZEHOOnEMsJCUJm//xZJSbgvILd6B4n/NgQNQg1It7IHIpM7WJWedbWNKkg3MlXJ D36jRowbr/A67HCI7PyiOXpYgIqMk73vYrNstxozGEg9b461cUhSiRBopr2s3BzT gD9NoWMGbEikRAs9H1pirPPK+f54wHSc/EhRKbevKuS0eXK/ueeMuf86mnm+BQG6 BdiwSCB8NI1GU2kZADh3b1Q7L3t9qs4jMYb/gqiTX6v3Od9eB8heRS6qIviFhgoE i1cBUAZujJ67cWwqmmun4wyKf7mY9aBPwEiwdqho+ag3iM7KHpMYZDHEY0D84tWI JXQeCw0iKgYY+QFxQBZA/Aee5kv0f/qoodMbNogfsnlQEkUYEjAsdkKQcHZRBSsD QU7ZIe2hDPt+L4MqEe5vFgsjh+UJhHch0bgtFaYOKRlOLE9DzgBDVvuBQeKwMJnM H3BTFSe0rafJb9oWz3YyhNWcQbMgDGSSp0ZBvUppu7ku1Dv0wLsNP/Kd8Ehzv17M 7aLm+dhg3mESoqUs/Y1Vkq5bE2lborsd4tWC9C+nCjP8kaUYxcvvOpFfDQbyZPwr QrZ3DxCklRJfKPn0HScz+MpXKv9cllJeSBtS62H0RDBc/TR+qnY= =2p8m -END PGP SIGNATURE- Thank you for your contribution to Debian.
lxctl is marked for autoremoval from testing
lxctl 0.3.1+debian-4 is marked for autoremoval from testing on 2019-03-23 It (build-)depends on packages with these RC bugs: 921667: lxc: lxc,apparmor: lxc fails to install in a chroot with apparmor installed
