Bug#987280: CVE-2021-31254 CVE-2021-31255 CVE-2021-31256 CVE-2021-31257 CVE-2021-31258 CVE-2021-31259 CVE-2021-31260 CVE-2021-31261 CVE-2021-31262
Hi, On Tue, Apr 20, 2021 at 08:55:13PM +0200, Moritz Muehlenhoff wrote: > Package: gpac > Version: 1.0.1+dfsg1-3 > Severity: grave > Tags: security > X-Debbugs-Cc: Debian Security Team > > CVE-2021-31262 > https://github.com/gpac/gpac/commit/b2eab95e07cb5819375a50358d4806a8813b6e50 > https://github.com/gpac/gpac/issues/1738 > > CVE-2021-31261 > https://github.com/gpac/gpac/commit/cd3738dea038dbd12e603ad48cd7373ae0440f65 > https://github.com/gpac/gpac/issues/1737 > > CVE-2021-31260 > https://github.com/gpac/gpac/commit/df8fffd839fe5ae9acd82d26fd48280a397411d9 > https://github.com/gpac/gpac/issues/1736 > > CVE-2021-31259 > https://github.com/gpac/gpac/commit/3b84ffcbacf144ce35650df958432f472b6483f8 > https://github.com/gpac/gpac/issues/1735 > > CVE-2021-31258 > https://github.com/gpac/gpac/commit/ebfa346eff05049718f7b80041093b4c5581c24e > https://github.com/gpac/gpac/issues/1706 > > CVE-2021-31257 > https://github.com/gpac/gpac/commit/87afe070cd6866df7fe80f11b26ef75161de85e0 > https://github.com/gpac/gpac/issues/1734 > > CVE-2021-31256 > https://github.com/gpac/gpac/commit/2da2f68bffd51d89b1d272d22aa8cc023c1c066e > https://github.com/gpac/gpac/issues/1705 > > CVE-2021-31255 > https://github.com/gpac/gpac/commit/758135e91e623d7dfe7f6aaad7aeb3f791b7a4e5 > https://github.com/gpac/gpac/issues/1733 > > CVE-2021-31254 > https://github.com/gpac/gpac/commit/8986422c21fbd9a7bf6561cae65aae42077447e8 > https://github.com/gpac/gpac/issues/1703 There appeared some more gpac CVEs yesterday, should we fill those as a separate bug? See CVE-2021-29279, CVE-2021-30014, CVE-2021-30015, CVE-2021-30019, CVE-2021-30020, CVE-2021-30022, CVE-2021-30199 additionally. Regards, Salvatore
Processed: tagging 987275, found 987275 in 1.4.4-2
Processing commands for cont...@bugs.debian.org: > tags 987275 + upstream Bug #987275 [src:rust-diesel] CVE-2021-28305 Added tag(s) upstream. > found 987275 1.4.4-2 Bug #987275 [src:rust-diesel] CVE-2021-28305 Marked as found in versions rust-diesel/1.4.4-2. > thanks Stopping processing here. Please contact me if you need assistance. -- 987275: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=987275 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#987207: podman not running out-of-the-box as root
Processing control commands: > tag -1 moreinfo Bug #987207 [podman] podman not running out-of-the-box as root Added tag(s) moreinfo. -- 987207: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=987207 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#987207: podman not running out-of-the-box as root
Processing control commands: > tag -1 moreinfo Bug #987207 [podman] podman not running out-of-the-box as root Ignoring request to alter tags of bug #987207 to the same tags previously set -- 987207: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=987207 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#987207: podman not running out-of-the-box as root
Control: tag -1 moreinfo Hi Laurent, I've downloaded the Bullseye Alpha 3 debian installer and installed using kvm to have a super clean new system. Unfortunately, I was unable to reproduce the issue that you described below. (I did find some issues with rootless podman outside of a gnome-session, but that's a different story). The symptoms sound a lot like described in this upstream bug: https://github.com/containers/podman/issues/5721 Can you please compare your notes with that upstream bug? Can you confirm that the 'overlay' kernel module is loaded? (in my test, it was loaded automatically). If you still think this is an issue in the Debian package, please let me know. I may require your assistance with reproducing this issue. -rt On Mon, Apr 19, 2021 at 11:54 AM Laurent Bigonville wrote: > Package: podman > Version: 3.0.1+dfsg1-1 > Severity: serious > > Hello, > > After installing podman, I cannot run it as root out of the box as it > fails with: > > ERRO[] [graphdriver] prior storage driver overlay failed: kernel does > not support overlay fs: 'overlay' is not supported over extfs at > "/var/lib/containers/storage/overlay": backing file system is unsupported > for this graph driver > Error: kernel does not support overlay fs: 'overlay' is not supported over > extfs at "/var/lib/containers/storage/overlay": backing file system is > unsupported for this graph driver > > Looking at fedora it seems that they have a containers-common package > that ships a default storage.conf file: > > > https://src.fedoraproject.org/rpms/containers-common/blob/rawhide/f/storage.conf > > I see that the debian package is shipping a file in > /usr/share/containers/storage.conf (in the containers-storage package), > but that file is apparently not read (strace only shows that the file in > /etc/containers is read) and anyway unlike in fedora: > > 1) the driver is not set to overlay > 2) the file is installed only if the containers-storage package is > installed, which is not done by default. > 3) that file is not read anyway, strace only shows that > /etc/containers/storage.conf is read and not > /usr/share/containers/storage.conf, so the file is apparently useless > > Shouldn't debian do the same thing than fedora so everything works OOTB? > > As a side note, I can see they are shipping also other files as well, > like the seccomp.json file, using strace, it seems that podman tries to > read them: > > [pid 14835] newfstatat(AT_FDCWD, "/etc/containers/seccomp.json", > 0xcee6b8, 0) = -1 ENOENT (Aucun fichier ou dossier de ce type) > [pid 14835] newfstatat(AT_FDCWD, "/usr/share/containers/seccomp.json", > 0xcee788, 0) = -1 ENOENT (Aucun fichier ou dossier de ce type) > > Shouldn't that file be shipped by default too? > > Kind regards, > Laurent Bigonville > > -- System Information: > Debian Release: 11.0 > APT prefers unstable-debug > APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, > 'experimental-debug'), (1, 'experimental') > Architecture: amd64 (x86_64) > > Kernel: Linux 5.10.0-6-amd64 (SMP w/8 CPU threads) > Locale: LANG=fr_BE.UTF-8, LC_CTYPE=fr_BE.UTF-8 (charmap=UTF-8), > LANGUAGE=fr_BE:fr > Shell: /bin/sh linked to /usr/bin/dash > Init: systemd (via /run/systemd/system) > LSM: SELinux: enabled - Mode: Permissive - Policy name: refpolicy > > Versions of packages podman depends on: > ii conmon 2.0.25+ds1-1 > ii containernetworking-plugins 0.9.0-1+b3 > ii golang-github-containers-common 0.35.4+ds1-1 > ii init-system-helpers 1.60 > ii libc62.31-11 > ii libdevmapper1.02.1 2:1.02.175-2.1 > ii libgpgme11 1.14.0-1+b2 > ii libseccomp2 2.5.1-1 > ii runc 1.0.0~rc93+ds1-3 > > Versions of packages podman recommends: > ii buildah 1.20.0+ds1-1 > ii fuse-overlayfs1.4.0-1 > ii golang-github-containernetworking-plugin-dnsname 1.1.1+ds1-4+b4 > ii slirp4netns 1.0.1-2 > ii tini 0.19.0-1 > ii uidmap1:4.8.1-1 > > Versions of packages podman suggests: > ii containers-storage 1.24.8+dfsg1-1+b1 > ii docker-compose 1.25.0-1 > > -- no debconf information > > -- regards, Reinhard
Bug#987279: nim: amd64 binaries built by maintainer; needs source-ony upload
> I guess something went wrong with the upload, because the changes file has > both Indeed the upload of 1.4.6-1 was only meant for Experimental and I'm surprised it landed into Sid. Any way to revert Unstable? Thanks! -- Federico
Bug#984894: marked as done (python-azure: flaky autopkgtest: You need to call 'result' or 'wait' on all LROPoller you have created)
Your message dated Tue, 20 Apr 2021 21:51:53 +
with message-id
and subject line Bug#984894: fixed in python-azure 20201208+git-5
has caused the Debian Bug report #984894,
regarding python-azure: flaky autopkgtest: You need to call 'result' or 'wait'
on all LROPoller you have created
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.)
--
984894: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984894
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-azure
Version: 20201208+git-3
Severity: serious
Tags: sid bullseye
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: flaky
Dear maintainer(s),
Your package has an autopkgtest, great. However, I looked into
the history of your autopkgtest [1] (because it is blocking
sphinx) and I noticed it fails regularly, while a rerun passes. I
copied some of the output at the bottom of this report.
Because the unstable-to-testing migration software now blocks on
regressions in testing, flaky tests, i.e. tests that flip between
passing and failing without changes to the list of installed packages,
are causing people unrelated to your package to spend time on these
tests.
Paul
https://ci.debian.net/data/autopkgtest/testing/amd64/p/python-azure/10719743/log.gz
=== FAILURES
===
MgmtResourceLinksTest.test_application
pylib/devtools_testutils/mgmt_testcase.py:97: in tearDown
return super(AzureMgmtTestCase, self).tearDown()
pylib/devtools_testutils/azure_testcase.py:193: in tearDown
return super(AzureTestCase, self).tearDown()
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
_ _ _ _
self =
def tearDown(self):
os.environ = self.original_env
# Autorest.Python 2.x
assert not [t for t in threading.enumerate() if
t.name.startswith("AzureOperationPoller")], \
"You need to call 'result' or 'wait' on all
AzureOperationPoller you have created"
# Autorest.Python 3.x
> assert not [t for t in threading.enumerate() if
t.name.startswith("LROPoller")], \
"You need to call 'result' or 'wait' on all LROPoller you
have created"
E AssertionError: You need to call 'result' or 'wait' on all
LROPoller you have created
pylib/azure_devtools/scenario_tests/base.py:158: AssertionError
-- Captured log call
---
OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: python-azure
Source-Version: 20201208+git-5
Done: Luca Boccassi
We believe that the bug you reported is fixed in the latest version of
python-azure, 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 984...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Luca Boccassi (supplier of updated python-azure 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: SHA512
Format: 1.8
Date: Tue, 20 Apr 2021 20:56:52 +0100
Source: python-azure
Architecture: source
Version: 20201208+git-5
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team
Changed-By: Luca Boccassi
Closes: 984894
Changes:
python-azure (20201208+git-5) unstable; urgency=medium
.
* Skip test_mgmt_resource_managed_application.py::MgmtResourceLinksTest:
:test_application (Closes: #984894)
Checksums-Sha1:
35e0f8ffd5a28d99238052f617c478824c9e0c08 2978 python-azure_20201208+git-5.dsc
6006828e447756f70b180402c9b4ae954d0d381d 519328
python-azure_20201208+git-5.debian.tar.xz
308f9365264e57c7b4c179731164b65601150ccf 8736
python-azure_20201208+git-5_source.buildinfo
Checksums-Sha256:
c283c7fa0cb3f4cb7531dcee9f4621a53d8095a62c4397f4603fc48a824e5685 2978
python-azure_20201208+git-5.dsc
27c3e87ee3fc8fc81f9fd5391563f8df7fd5d724edeb2790c45b39ff92c24fa6 519328
python-azure_20201208+git-5.debian.tar.xz
f6ddeebebc90d3061aed2857d4af83f836e1af3572132da93e827fd4d891767a 8736
python-azure_20201208+git-5_source.buildinfo
Files:
070685151213f09000559a030863d347 2978 python optional
python-azure_20201208+git-5.dsc
Bug#981533: poetry-core: autopkgtest failure
Hello! Thanks for the report and sorry for the delay of my response. I've just push to salsa [0] a fix for this error. Now at least on salsa run autopkgtest successfully. I need sponsorship to upload it. I cc pollo that help me to upload to Debian. Thanks Cheers, Emmanuel [0] https://salsa.debian.org/python-team/packages/poetry-core
Processed: tagging 981533
Processing commands for cont...@bugs.debian.org: > tags 981533 + pending Bug #981533 [src:poetry-core] poetry-core: autopkgtest failure Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 981533: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=981533 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#982758: webext-browserpass: Failed to install on upgrade to bullseye
Hi,
Antoine Beaupré wrote:
> I have had the same, completely crashes the apt run too, neat. :)
>
> dpkg: error processing archive
> /var/cache/apt/archives/webext-browserpass_3.7.2-1+b1_amd64.deb (--unpack):
> unable to open
> '/usr/share/mozilla/extensions/{ec8030f7-c20a-464f-9b0e-13a3a9e97384}/browserp...@maximbaz.com/icon.png.dpkg-new':
> No such file or directory
> Reinstalling
> /etc/chromium/native-messaging-hosts/com.dannyvankooten.browserpass.json that
> was moved away
Ack. Ran into this, too, today.
> I bumped the severity because it completely fails to upgrade.
Thanks!
> Workaround: apt purge webext-browserpass && apt install webext-browserpass
Ah, nice!
I digged a bit deeper and found the culprit:
First that weird dpkg error message. It's well explained here:
https://raphaelhertzog.com/2011/07/18/deciphering-one-of-dpkg-weirdest-errors-unable-to-open-pathtofoo-dpkg-new/
This led me quickly looking into the preinst script and it indeed
fiddles with directories and symlinks. That's also why purging and
installing from scratch doesn't trigger the issue and helps as
workaround:
#!/bin/sh
set -e
# Automatically added by dh_installdeb/13.3.4
dpkg-maintscript-helper symlink_to_dir
/usr/share/chromium/extensions/browserpass /usr/share/webext/browserpass
3.0.0-1 -- "$@"
dpkg-maintscript-helper symlink_to_dir
/usr/share/mozilla/extensions/{ec8030f7-c20a-464f-9b0e-13a3a9e97384}/browserpass\@maximbaz.com
/usr/share/webext/browserpass 3.0.0-1 -- "$@"
dpkg-maintscript-helper rm_conffile
/etc/chromium/native-messaging-hosts/com.dannyvankooten.browserpass.json
3.4.1-3\~ -- "$@"
# End automatically added section
Combine that with the fact that the package ships both,
/usr/share/chromium/extensions/browserpass/icon.png and
/usr/share/mozilla/extensions/{ec8030f7-c20a-464f-9b0e-13a3a9e97384}/browserp...@maximbaz.com/icon.png
and you get that problem.
So now the question is, what exactly happens and how to fix it?
In general, symlink_to_dir seems to be the right thing, since those
directories are indeed symlinks in buster:
lrwxrwxrwx 1 root root 24 Feb 6 2019
/usr/share/chromium/extensions/browserpass -> ../../webext/browserpass/
lrwxrwxrwx 1 root root 27 Feb 6 2019
'/usr/share/mozilla/extensions/{ec8030f7-c20a-464f-9b0e-13a3a9e97384}/browserp...@maximbaz.com'
-> ../../../webext/browserpass/
And directory in sid/bullseye:
drwxr-xr-x 2 root root 4096 Apr 10 03:00
/usr/share/chromium/extensions/browserpass/
drwxr-xr-x 7 root root 4096 Apr 10 03:00
'/usr/share/mozilla/extensions/{ec8030f7-c20a-464f-9b0e-13a3a9e97384}/browserp...@maximbaz.com'/
The effect looks as if those symlinks weren't changed into
directories. But why? That 3.0.0-1 looks valid. And looking at my
upgrade logs (I always log dist-upgrades with "script"), the versions
seem the expected ones:
Preparing to unpack .../370-webext-browserpass_3.7.2-1+b1_amd64.deb ...
Unpacking webext-browserpass (3.7.2-1+b1) over (2.0.22-2) ...
dpkg: error processing archive
/tmp/apt-dpkg-install-VKYulC/370-webext-browserpass_3.7.2-1+b1_amd64.deb
(--unpack):
unable to open
'/usr/share/mozilla/extensions/{ec8030f7-c20a-464f-9b0e-13a3a9e97384}/browserp...@maximbaz.com/icon.png.dpkg-new':
No such file or directory
Reinstalling
/etc/chromium/native-messaging-hosts/com.dannyvankooten.browserpass.json that
was moved away
So I must admit, I'm currently not understanding what exactly goes
wrong. Wanted though to share how far I came with debugging this in
case someone else was stuck earlier in the process, but now has an
idea what goes wrong.
Will write again if I figure out more.
Regards, Axel
--
,''`. | Axel Beckert , https://people.debian.org/~abe/
: :' : | Debian Developer, ftp.ch.debian.org Admin
`. `' | 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5
`-| 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE
Bug#984894: marked as pending in python-azure
Control: tag -1 pending Hello, Bug #984894 in python-azure reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/python-team/packages/python-azure/-/commit/f100e90c2a0863a937367e3048e7ba1094b9a25a Skip test_mgmt_resource_managed_application.py::MgmtResourceLinksTest::test_application It appears to be flaky on autopkgtest VMs. See: https://ci.debian.net/data/autopkgtest/testing/amd64/p/python-azure/10719743/log.gz Closes: #984894 (this message was generated automatically) -- Greetings https://bugs.debian.org/984894
Processed: Bug#984894 marked as pending in python-azure
Processing control commands: > tag -1 pending Bug #984894 [src:python-azure] python-azure: flaky autopkgtest: You need to call 'result' or 'wait' on all LROPoller you have created Added tag(s) pending. -- 984894: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984894 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#984894: python-azure: flaky autopkgtest: You need to call 'result' or 'wait' on all LROPoller you have created
On Mon, 12 Apr 2021 21:18:02 +0200 Paul Gevers wrote: > Control: severity -1 serious > > Hi Luca, > > [Please CC submitters if you ask for their input, the BTS doesn't > forward messages automatically] > > On Wed, 24 Mar 2021 16:53:52 + Luca Boccassi wrote: > > I have ran the sdk/resources/azure-mgmt-resource tests locally for ~30 > > times and unfortunately I am not able to reproduce the issue. > > Did you by any chance run them in parallel? The failures on amd64 always > happen on ci-worker13, which is running 8 parallel debci workers. > Interestingly enough, armhf is *always* running on a host with 8 > parallel debci workers and there the issue isn't seen. All our arm64 > workers have two debci workers, as does ppc64el. The former is lightly > flaky, the latter hasn't showed a failure yet since -2. > > > Hence I'm > > downgrading + adding tags for help - if anyone is able to reproduce or > > spot the issue, a MR is more than welcome. > > This particular module was also updated in -4 to solve an unrelated > > issue, so it might very well be that this is solved too. > > -4 is as flaky as before. > > If there's something specific we can test for you on the ci.d.n infra > let us know. > > Paul > (Release Team hat on for the severity call, CI Team hat on for the offer > to help on the infra.) Hi, Thanks for the further information - I have now tried to run the same test in parallel multiple times, but still no luck. I'll just go ahead and blocklist it in the next upload. -- Kind regards, Luca Boccassi signature.asc Description: This is a digitally signed message part
Bug#983140: closed by Debian FTP Masters (reply to Lee Garrett ) (Bug#983140: fixed in ansible 2.10.7+merged+base+2.10.8+dfsg-1)
Hi Lee,
On 2021/04/19 11:06 PM, Debian Bug Tracking System wrote:
> #983140: ansible: Does not detect correct python interpreter on bullseye
> target
>
> It has been closed by Debian FTP Masters
> (reply to Lee Garrett ).
Glad to hear this will be fixed by this new version.
I was also working on a patch for 2.9.16 but I guess it's a bit late of
that :)
I'll attach it anyway for reference because I managed to have all unit
tests working by avoiding the user home directory. You might be
interested to have a look at that.
Thanks again for maintaining ansible!
Best,
--
Baptiste Beauplat - lyknode
diff -Nru ansible-2.9.16+dfsg/debian/changelog
ansible-2.9.16+dfsg/debian/changelog
--- ansible-2.9.16+dfsg/debian/changelog2021-01-06 11:56:22.0
+0100
+++ ansible-2.9.16+dfsg/debian/changelog2021-04-17 15:27:02.0
+0200
@@ -1,3 +1,11 @@
+ansible (2.9.16+dfsg-1.2) bullseye; urgency=medium
+
+ * Non-maintainer upload.
+ * Use python3.9 as default interpreter (Closes: #983140)
+ * Add autopkgtest to run a working subset of ansible test suite
+
+ -- Baptiste Beauplat Sat, 17 Apr 2021 15:27:02 +0200
+
ansible (2.9.16+dfsg-1.1) unstable; urgency=medium
* Non-maintainer upload.
diff -Nru
ansible-2.9.16+dfsg/debian/patches/0007-fix-interpreter-fallback.patch
ansible-2.9.16+dfsg/debian/patches/0007-fix-interpreter-fallback.patch
--- ansible-2.9.16+dfsg/debian/patches/0007-fix-interpreter-fallback.patch
1970-01-01 01:00:00.0 +0100
+++ ansible-2.9.16+dfsg/debian/patches/0007-fix-interpreter-fallback.patch
2021-04-17 15:27:02.0 +0200
@@ -0,0 +1,33 @@
+Description: Fix python interpreter discovery (Closes: #983140)
+ On machines upgrade from buster to bullseye, the wrong interpreter will be
+ discovered and used, causing the playbook run to fail. Update the fallback
list
+ so it correctly picks python3.9 on bullseye when both 3.9 and 3.7 are present,
+ which usually is the case on freshly upgrade machines.
+Origin: backport,
https://github.com/ansible/ansible/commit/c986cbb9961bfaedf1a6ae7f0c2e34be26d9ab12
+Forwarded: not-needed
+Applied-Upstream:
https://github.com/ansible/ansible/commit/c986cbb9961bfaedf1a6ae7f0c2e34be26d9ab12
+Reviewed-by: Lee Garrett
+Last-Update: 2021-03-23
+---
+This patch header follows DEP-3: http://dep.debian.net/deps/dep3/
+--- a/lib/ansible/config/base.yml
b/lib/ansible/config/base.yml
+@@ -1523,6 +1523,8 @@
+ name: Ordered list of Python interpreters to check for in discovery
+ default:
+ - /usr/bin/python
++ - python3.9
++ - python3.8
+ - python3.7
+ - python3.6
+ - python3.5
+--- a/test/lib/ansible_test/_internal/util.py
b/test/lib/ansible_test/_internal/util.py
+@@ -110,6 +110,7 @@
+ '3.6',
+ '3.7',
+ '3.8',
++'3.9',
+ )
+
+
diff -Nru ansible-2.9.16+dfsg/debian/patches/0008-fix-tests.patch
ansible-2.9.16+dfsg/debian/patches/0008-fix-tests.patch
--- ansible-2.9.16+dfsg/debian/patches/0008-fix-tests.patch 1970-01-01
01:00:00.0 +0100
+++ ansible-2.9.16+dfsg/debian/patches/0008-fix-tests.patch 2021-04-17
15:27:02.0 +0200
@@ -0,0 +1,44 @@
+From: Baptiste Beauplat
+Date: Mon, 19 Apr 2021 20:41:09 +0200
+Subject: Fix test suite
+
+* Mark two tests depending on pycrypto with the correct skipif
+* Inject remote_tmp configuration to point to /tmp to handle testbed without
+ HOME
+* Truncate output check on test_build_requirement_from_path_no_version due to
an
+ issue with text wrapping
+--- a/test/units/parsing/vault/test_vault.py
b/test/units/parsing/vault/test_vault.py
+@@ -528,6 +528,7 @@
+ b_key_pycrypto = self.vault_cipher._create_key_pycrypto(b_password,
b_salt, key_length=32, iv_length=16)
+ self.assertEqual(b_key_cryptography, b_key_pycrypto)
+
++@pytest.mark.skipif(not vault.HAS_PYCRYPTO, reason='Not testing
cryptography known key as pycrypto is not installed')
+ def test_create_key_known_cryptography(self):
+ b_password = b'hunter42'
+
+@@ -555,6 +556,7 @@
+ self.assertEqual(b_key_3, b_key_4)
+ self.assertEqual(b_key_1, b_key_4)
+
++@pytest.mark.skipif(not vault.HAS_PYCRYPTO, reason='Not testing pycrypto
known key as pycrypto is not installed')
+ def test_create_key_known_pycrypto(self):
+ b_password = b'hunter42'
+
+--- /dev/null
b/test/lib/ansible_test/_data/ansible.cfg
+@@ -0,0 +1,2 @@
++[defaults]
++remote_tmp = /tmp/ansible
+--- a/test/units/galaxy/test_collection_install.py
b/test/units/galaxy/test_collection_install.py
+@@ -242,8 +242,7 @@
+ assert mock_display.call_count == 1
+
+ actual_warn = ' '.join(mock_display.mock_calls[0][1][0].split('\n'))
+-expected_warn = "Collection at '%s' does not have a valid version set,
falling back to '*'. Found version: ''" \
+-% to_text(collection_artifact[0])
++expected_warn = "does not have a valid version set, falling back to '*'.
Found version: ''"
+ assert expected_warn in
Processed: Re: Bug#918984: fuse3 still not co-installable with fuse
Processing control commands: > tags -1 - bullseye + bookworm Bug #918984 [src:fuse3] fuse3: provide upgrade path fuse -> fuse3 for bullseye Removed tag(s) bullseye. Bug #918984 [src:fuse3] fuse3: provide upgrade path fuse -> fuse3 for bullseye Added tag(s) bookworm. > retitle -1 fuse3: provide upgrade path fuse -> fuse3 for bookworm Bug #918984 [src:fuse3] fuse3: provide upgrade path fuse -> fuse3 for bullseye Changed Bug title to 'fuse3: provide upgrade path fuse -> fuse3 for bookworm' from 'fuse3: provide upgrade path fuse -> fuse3 for bullseye'. -- 918984: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918984 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#918984: fuse3 still not co-installable with fuse
Control: tags -1 - bullseye + bookworm Control: retitle -1 fuse3: provide upgrade path fuse -> fuse3 for bookworm On 2021-04-06 21:30:37, Sebastian Ramacher wrote: > Control: severity -1 serious > Control: retitle -1 fuse3: provide upgrade path fuse -> fuse3 for bullseye > > The fuse/fuse3 situation turns out to be an issue for buster -> bullseye > upgrades. Take a minimal buster chroot with ntfs-3g and sshfs installed: > > $ apt-get -y install ntfs-3g sshfs > $ sed 's/buster/bullseye/' -i /etc/apt/sources.list > $ apt-get update > $ apt-get -y dist-upgrade > > After the upgrade, sshfs is still at the version from buster: > > $ apt-cache policy sshfs > sshfs: > Installed: 2.10+repack-2 > Candidate: 3.7.1+repack-1 > Version table: > 3.7.1+repack-1 500 > 500 http://localhost:3142/debian bullseye/main amd64 Packages > *** 2.10+repack-2 100 > 100 /var/lib/dpkg/status > > > Explicitely upgrading sshfs with apt-get install will cause fuse3 to be > installed and fuse to be removed. Thanks to Helmut Grohne for the > reproducer. > > With my release team hat on, I'm raising this issue to serious. We want > to provide working upgrade paths. One possible solution to the problem > would be for src:fuse3 to take over the fuse binary package as > transitional package depending on bin:fuse3. As far as I understand the > situation, all reverse dependencies of fuse should also work with fuse3. This is now being documented in the release notes at https://salsa.debian.org/ddp-team/release-notes/-/merge_requests/92 and should not occur in normal upgrades. Since fixing this issue also involves udeps, let's postponse this for bookworm. Cheers -- Sebastian Ramacher
Bug#987279: nim: amd64 binaries built by maintainer; needs source-ony upload
Hi, On Tue, Apr 20, 2021 at 08:58:05PM +0200, Ivo De Decker wrote: > Federico, > > On Tue, Apr 20, 2021 at 08:49:54PM +0200, Salvatore Bonaccorso wrote: > > The last nim upload seems to have included binary builds for amd64 > > which will prevent nim to potentially go to testing (even after > > unblocked), as it needs a source-only upload with builds done on > > buildds. > > > > Cf. https://tracker.debian.org/pkg/nim > > > > * Not built on buildd: arch amd64 binaries uploaded by > > federico.cera...@gmail.com > > * Not built on buildd: arch all binaries uploaded by > > federico.cera...@gmail.com, a new source-only upload is needed to allow > > migration > > I guess something went wrong with the upload, because the changes file has > both > > Distribution: sid > > and > > nim (1.4.6-1) experimental; urgency=medium > > > Please check what went wrong to avoid this in the future. > > In this case, I suspect the upload wasn't meant for bullseye, and it can just > stay in unstable (unfortunately). Unfortunately there is related the bug filled by Moritz, #987272, JFYI. Probably needs still a revert in unstable to the old version + patches? Regards, Salvatore
Bug#987279: nim: amd64 binaries built by maintainer; needs source-ony upload
Federico, On Tue, Apr 20, 2021 at 08:49:54PM +0200, Salvatore Bonaccorso wrote: > The last nim upload seems to have included binary builds for amd64 > which will prevent nim to potentially go to testing (even after > unblocked), as it needs a source-only upload with builds done on > buildds. > > Cf. https://tracker.debian.org/pkg/nim > > * Not built on buildd: arch amd64 binaries uploaded by > federico.cera...@gmail.com > * Not built on buildd: arch all binaries uploaded by > federico.cera...@gmail.com, a new source-only upload is needed to allow > migration I guess something went wrong with the upload, because the changes file has both Distribution: sid and nim (1.4.6-1) experimental; urgency=medium Please check what went wrong to avoid this in the future. In this case, I suspect the upload wasn't meant for bullseye, and it can just stay in unstable (unfortunately). Cheers, Ivo
Bug#987280: CVE-2021-31254 CVE-2021-31255 CVE-2021-31256 CVE-2021-31257 CVE-2021-31258 CVE-2021-31259 CVE-2021-31260 CVE-2021-31261 CVE-2021-31262
Package: gpac Version: 1.0.1+dfsg1-3 Severity: grave Tags: security X-Debbugs-Cc: Debian Security Team CVE-2021-31262 https://github.com/gpac/gpac/commit/b2eab95e07cb5819375a50358d4806a8813b6e50 https://github.com/gpac/gpac/issues/1738 CVE-2021-31261 https://github.com/gpac/gpac/commit/cd3738dea038dbd12e603ad48cd7373ae0440f65 https://github.com/gpac/gpac/issues/1737 CVE-2021-31260 https://github.com/gpac/gpac/commit/df8fffd839fe5ae9acd82d26fd48280a397411d9 https://github.com/gpac/gpac/issues/1736 CVE-2021-31259 https://github.com/gpac/gpac/commit/3b84ffcbacf144ce35650df958432f472b6483f8 https://github.com/gpac/gpac/issues/1735 CVE-2021-31258 https://github.com/gpac/gpac/commit/ebfa346eff05049718f7b80041093b4c5581c24e https://github.com/gpac/gpac/issues/1706 CVE-2021-31257 https://github.com/gpac/gpac/commit/87afe070cd6866df7fe80f11b26ef75161de85e0 https://github.com/gpac/gpac/issues/1734 CVE-2021-31256 https://github.com/gpac/gpac/commit/2da2f68bffd51d89b1d272d22aa8cc023c1c066e https://github.com/gpac/gpac/issues/1705 CVE-2021-31255 https://github.com/gpac/gpac/commit/758135e91e623d7dfe7f6aaad7aeb3f791b7a4e5 https://github.com/gpac/gpac/issues/1733 CVE-2021-31254 https://github.com/gpac/gpac/commit/8986422c21fbd9a7bf6561cae65aae42077447e8 https://github.com/gpac/gpac/issues/1703 Cheers, Moritz
Bug#987279: nim: amd64 binaries built by maintainer; needs source-ony upload
Source: nim Version: 1.4.6-1 Severity: serious Justification: not build on all release architectures by buildds; no source-only upload X-Debbugs-Cc: car...@debian.org Hi The last nim upload seems to have included binary builds for amd64 which will prevent nim to potentially go to testing (even after unblocked), as it needs a source-only upload with builds done on buildds. Cf. https://tracker.debian.org/pkg/nim * Not built on buildd: arch amd64 binaries uploaded by federico.cera...@gmail.com * Not built on buildd: arch all binaries uploaded by federico.cera...@gmail.com, a new source-only upload is needed to allow migration Regards, Salvatore
Bug#987275: CVE-2021-28305
Source: rust-diesel Severity: grave Tags: security X-Debbugs-Cc: Debian Security Team This was assigned CVE-2021-28305: https://rustsec.org/advisories/RUSTSEC-2021-0037.html Cheers, Moritz
Bug#987258: marked as done (epix: fails to install with xemacs21)
Your message dated Tue, 20 Apr 2021 17:48:25 + with message-id and subject line Bug#987258: fixed in epix 1.2.19-2 has caused the Debian Bug report #987258, regarding epix: fails to install with xemacs21 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.) -- 987258: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=987258 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: epix Version: 1.2.19-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package failed to install if xemacs21 is already installed. >From the attached log (scroll to the bottom...): Setting up epix (1.2.19-1) ... Install emacsen-common for xemacs21 emacsen-common: Handling install of emacsen flavor xemacs21 Loading /usr/share/emacsen-common/debian-startup... Loading 00debian... Compiling /usr/share/xemacs21/site-lisp/debian-startup.el... Wrote /usr/share/xemacs21/site-lisp/debian-startup.elc Done Install epix for xemacs21 install/epix: Handling install for emacsen flavor xemacs21 cp: cannot stat '*.el': No such file or directory ERROR: install script from epix package failed dpkg: error processing package epix (--configure): installed epix package post-installation script subprocess returned error exit status 1 Setting up imagemagick (8:6.9.11.60+dfsg-1) ... Processing triggers for libc-bin (2.31-11) ... Processing triggers for tex-common (6.16) ... Running updmap-sys. This may take some time... done. Running mktexlsr /var/lib/texmf ... done. Building format(s) --all. This may take some time... done. Errors were encountered while processing: epix cheers, Andreas epix=1.2.19-1_xemacs21.log.gz Description: application/gzip --- End Message --- --- Begin Message --- Source: epix Source-Version: 1.2.19-2 Done: Julian Gilbey We believe that the bug you reported is fixed in the latest version of epix, 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 987...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Julian Gilbey (supplier of updated epix 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, 20 Apr 2021 17:54:01 +0100 Source: epix Architecture: source Version: 1.2.19-2 Distribution: unstable Urgency: medium Maintainer: Julian Gilbey Changed-By: Julian Gilbey Closes: 987258 Changes: epix (1.2.19-2) unstable; urgency=medium . * Remove old debian/epix.emacsen-* files which prevented dh-elpa from working correctly (Closes: #987258) * Force configure to use /bin/bash for bash, otherwise building on systems with /bin being a symlink to /usr/bin leads to scripts with the incompatible /usr/bin/bash as their interpreter * Remove now-empty directory usr/share/emacs/site-lisp/epix from debian/epix.dirs Checksums-Sha1: c8071f6d45905c3edfb9131487dda38a5d02fabe 1798 epix_1.2.19-2.dsc 36d37f7d9d1b1b0a1a225e8565b638ea6c6841f7 5488 epix_1.2.19-2.debian.tar.xz c04d3c89d7939e89a7f1e3109e3aaf6ca2edb9bf 10430 epix_1.2.19-2_amd64.buildinfo Checksums-Sha256: d3f0f678b638c82eac72edad425c6d33b645c27ca1c30be3d9a648620ce8ca55 1798 epix_1.2.19-2.dsc 1ad2b3355d8276ef7c3a42e6e6f9a0631f07a8654f66b66f1a94af1334cd70cb 5488 epix_1.2.19-2.debian.tar.xz 46162fa83ad597a78cf0bb37c01a22df1a776c79169e3d2b4adfa0f66d549e3e 10430 epix_1.2.19-2_amd64.buildinfo Files: 562f31985e46aad90f12443e9be11f5d 1798 tex optional epix_1.2.19-2.dsc 2de92af5075af22be1e5550a7eac989d 5488 tex optional epix_1.2.19-2.debian.tar.xz 8e6b706b5a0ad06e211724263e36179e 10430 tex optional epix_1.2.19-2_amd64.buildinfo -BEGIN PGP SIGNATURE- iQJDBAEBCAAtFiEEfhrD+iemSShMMj72aVxCkxbAe/4FAmB/CasPHGpkZ0BkZWJp YW4ub3JnAAoJEGlcQpMWwHv+dQQQAKCFnadkKfJnycCydtLGn9tbrwrNacLpE97d f+i3p0GddIXyUgS0QETCii9PlIG3/E3d+4IVzcrVDZiVGk2pkk2LpWPqTwisv4Ag GPlv+YNLcfsJEkMbxZLKehyDiXl7yG4F4r0KHeiYQRMeh3sH42uuxxs9gQc42VV8 7Y/VFLtr9Eyy2QCdvqs3+LtRcmL2tUnNTMo2PQ2z109VK6HwhDaYOU8POaifAL+K E50500muPW1zCnzFYcX0zBs622ua005AoVhF6/Us+Vl1F9vkILz7z72GLZA/BlfZ caiSxUCKnUhzrnyMXuSMX6rnAM50Ex47EBWxdWVNqkmmrpXtIHZaHNLB6xN0T4xT
Bug#987219: marked as done (nvidia-graphics-drivers-tesla-418: CVE-2021-1076)
Your message dated Tue, 20 Apr 2021 15:43:35 + with message-id and subject line Bug#987219: fixed in nvidia-graphics-drivers-tesla-418 418.197.02-1 has caused the Debian Bug report #987219, regarding nvidia-graphics-drivers-tesla-418: CVE-2021-1076 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.) -- 987219: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=987219 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: nvidia-graphics-drivers Severity: serious Tags: security upstream Control: clone -1 -2 -3 -4 -5 -6 -7 Control: reassign -2 src:nvidia-graphics-drivers-legacy-340xx 340.76-6 Control: retitle -2 nvidia-graphics-drivers-legacy-340xx: CVE-2021-1076 Control: tag -2 + wontfix Control: reassign -3 src:nvidia-graphics-drivers-legacy-390xx 390.48-4 Control: retitle -3 nvidia-graphics-drivers-legacy-390xx: CVE-2021-1076 Control: reassign -4 src:nvidia-graphics-drivers-tesla-418 418.87.01-1 Control: retitle -4 nvidia-graphics-drivers-tesla-418: CVE-2021-1076 Control: reassign -5 src:nvidia-graphics-drivers-tesla-440 440.64.00-1 Control: retitle -5 nvidia-graphics-drivers-tesla-440: CVE-2021-1076 Control: tag -5 + wontfix Control: reassign -6 src:nvidia-graphics-drivers-tesla-450 450.51.05-1 Control: retitle -6 nvidia-graphics-drivers-tesla-450: CVE-2021-1076, CVE-2021-1077 Control: reassign -7 src:nvidia-graphics-drivers-tesla-460 460.32.03-1 Control: retitle -7 nvidia-graphics-drivers-tesla-460: CVE-2021-1076, CVE-2021-1077 Control: found -1 340.24-1 Control: found -1 343.22-1 Control: found -1 396.18-1 Control: found -1 430.14-1 Control: found -1 450.51-1 Control: found -1 455.23.04-1 https://nvidia.custhelp.com/app/answers/detail/a_id/5172 CVE‑2021‑1076 NVIDIA GPU Display Driver for Windows and Linux contains a vulnerability in the kernel mode layer (nvlddmkm.sys or nvidia.ko) where improper access control may lead to denial of service, information disclosure, or data corruption. CVE‑2021‑1077 NVIDIA GPU Display Driver for Windows and Linux contains a vulnerability where the software uses a reference count to manage a resource that is incorrectly updated, which may lead to denial of service. Driver Branch CVE IDs Addressed R465, R418, R390CVE‑2021‑1076 R460, R450 CVE‑2021‑1076, CVE‑2021‑1077 Andreas --- End Message --- --- Begin Message --- Source: nvidia-graphics-drivers-tesla-418 Source-Version: 418.197.02-1 Done: Andreas Beckmann We believe that the bug you reported is fixed in the latest version of nvidia-graphics-drivers-tesla-418, 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 987...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andreas Beckmann (supplier of updated nvidia-graphics-drivers-tesla-418 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, 20 Apr 2021 16:15:04 +0200 Source: nvidia-graphics-drivers-tesla-418 Architecture: source Version: 418.197.02-1 Distribution: unstable Urgency: medium Maintainer: Debian NVIDIA Maintainers Changed-By: Andreas Beckmann Closes: 987219 Changes: nvidia-graphics-drivers-tesla-418 (418.197.02-1) unstable; urgency=medium . * New upstream Tesla release 418.197.02 (2021-04-19). * Fixed CVE-2021-1076. (Closes: #987219) https://nvidia.custhelp.com/app/answers/detail/a_id/5172 Checksums-Sha1: 3c8b7f6fc838441708def9aa830cfcc186f7f968 7239 nvidia-graphics-drivers-tesla-418_418.197.02-1.dsc 039ff1b0ca36f2ec9b38d1f0cb5640d2871d9b3b 108992467 nvidia-graphics-drivers-tesla-418_418.197.02.orig-amd64.tar.gz c03e2bcd5077a34e1469bcfa654ec1713537c088 38380208 nvidia-graphics-drivers-tesla-418_418.197.02.orig-ppc64el.tar.gz 93ab54c8ca0ee4a1c500528c72416ca03123141f 141 nvidia-graphics-drivers-tesla-418_418.197.02.orig.tar.gz 5405e138eeeb9cbc99bfce9d5cc2f0808f72ad6c 191212 nvidia-graphics-drivers-tesla-418_418.197.02-1.debian.tar.xz ccdce3f2e060c403b117e2b2ce44ea5a8c2e4074 7925 nvidia-graphics-drivers-tesla-418_418.197.02-1_source.buildinfo Checksums-Sha256: 8c07a8b95a58fce41309c5baff9f92fa617135432482fc3c141d7a74e1cce93d 7239
Bug#987247: marked as done (imagemagick: failing autopkgtests after disabling of ghostscript handled formats)
Your message dated Tue, 20 Apr 2021 15:43:08 + with message-id and subject line Bug#987247: fixed in imagemagick 8:6.9.11.60+dfsg-1.3 has caused the Debian Bug report #987247, regarding imagemagick: failing autopkgtests after disabling of ghostscript handled formats 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.) -- 987247: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=987247 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: imagemagick Version: 8:6.9.11.60+dfsg-1.2 Severity: serious Justification: failing autopkgtests X-Debbugs-Cc: car...@debian.org,debian-rele...@lists.debian.org After disabling the ghostscript handled formats in policy.xml for imagemagick (following what was done in stable already with DSA 4712-1 / imagemagick 8:6.9.10.23+dfsg-2.1+deb10u1) the autopkgtests of imagemagick itself fail because they use 'convert rose: pdf:/dev/null' in part of the tests. Those need to be adjusted as well, and was a fallout of the previous done upload done as 8:6.9.11.60+dfsg-1.2. Regards, Salvatore --- End Message --- --- Begin Message --- Source: imagemagick Source-Version: 8:6.9.11.60+dfsg-1.3 Done: Salvatore Bonaccorso We believe that the bug you reported is fixed in the latest version of imagemagick, 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 987...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Salvatore Bonaccorso (supplier of updated imagemagick 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: SHA512 Format: 1.8 Date: Tue, 20 Apr 2021 16:37:59 +0200 Source: imagemagick Architecture: source Version: 8:6.9.11.60+dfsg-1.3 Distribution: unstable Urgency: medium Maintainer: ImageMagick Packaging Team Changed-By: Salvatore Bonaccorso Closes: 987247 Changes: imagemagick (8:6.9.11.60+dfsg-1.3) unstable; urgency=medium . * Non-maintainer upload. * autopkgtest: Drop PDF related tests which will fail after disabling ghostscript handled formats by default (Closes: #987247) Checksums-Sha1: 2886077832acc32aab621491c8d40dd32190a842 5229 imagemagick_6.9.11.60+dfsg-1.3.dsc acc9abcce20340a890340a25cd80af71b295e845 246928 imagemagick_6.9.11.60+dfsg-1.3.debian.tar.xz 4959ae5d96c9b6c2411ec1a89a457ccc938c86ce 6689 imagemagick_6.9.11.60+dfsg-1.3_source.buildinfo Checksums-Sha256: 5e09025a6861ace28ac9dc51db730172801e875842ba1faec5c9b736b2918269 5229 imagemagick_6.9.11.60+dfsg-1.3.dsc a85cb23dc8633a89349517378b4b973235a59fc4969b908be660c7bde0f2b36c 246928 imagemagick_6.9.11.60+dfsg-1.3.debian.tar.xz 1fc06e36756477054108af0a4a26ddfa8eb6a97f0b5b805d71b1158315449c8f 6689 imagemagick_6.9.11.60+dfsg-1.3_source.buildinfo Files: d5bb121bad5cf67c1349ae9c4166e8f3 5229 graphics optional imagemagick_6.9.11.60+dfsg-1.3.dsc 0fe7804dd8ea6f39e0739cf74bf04839 246928 graphics optional imagemagick_6.9.11.60+dfsg-1.3.debian.tar.xz 3f03c59511497346dd5b93eb794c0aaf 6689 graphics optional imagemagick_6.9.11.60+dfsg-1.3_source.buildinfo -BEGIN PGP SIGNATURE- iQKmBAEBCgCQFiEERkRAmAjBceBVMd3uBUy48xNDz0QFAmB+6DJfFIAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDQ2 NDQ0MDk4MDhDMTcxRTA1NTMxRERFRTA1NENCOEYzMTM0M0NGNDQSHGNhcm5pbEBk ZWJpYW4ub3JnAAoJEAVMuPMTQ89Etr4P/Rb2eq64yT1fBepZtRK90nOYgvfjNtMN 27ejC213Cg4Bvw6PtAlnT/17BakEu45AgMpVNyHpGhXEaaMjmtH6tGJkosDEAdDS eQ6HqvsVjpdaz4bnWPmz+4yWjcXMU2fofnM2Gb/tsE7XtS7nopvm/idoeSsUEL+g c+nQmdQzbesXYG79lUxxGoSIjQayUkZcmY5BVH7kAeQvdZQRPcdFvzAjAKeRtdHC BaLLEiTImXyMoMkde9TmSyhu8LsVaAxnmIg7fzahFmGSNmixy0kbkiU0k7l/4wkL JfdBvITvqCI5FCWSjzUvFluJgwy9sn75Sg8N73lGB69Y99nqovppyl7Yyio1uT88 tqbfXa8tN0GDIADuny16VtxG346XgIhTINk7/j7s7WvD72Hj6F5ck6Fdqi/1clAL z8jTbjcWpX2eQSYI0KtqY7VDkp3qhbT5La+DOuDx+6ixXrpwVHgqABs3p51mDgoE Nq35IHlHurn24630M1z5w32Js7qRAXxa7Ss+901CIZsFNPfq7dFG2zSPsEPyZNyx JuSiOyYOgMoFlC1sX7syZNg7+D0QLfqmBPhDWHPI0chAY1dSOfTXTQPRYXUPlnVV 47ZLPUR8sJdUg/+FIHbb3ZvoWRk3nYhtc/BkNfJiF+mf6bxn8ctbSQY1eMWhiN3h uLkcNZal0Mbg =blqL -END PGP SIGNATURE End Message ---
Bug#987264: git-el: fails to install with xemacs21
Package: git-el Version: 1:2.30.2-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package failed to install if xemacs21 is already installed. >From the attached log (scroll to the bottom...): Setting up git-el (1:2.31.0+next.20210315-1) ... Install git for emacs install/git: Handling install of emacsen flavor emacs mkdir: cannot create directory '/usr/share/emacs/site-lisp/git': No such file or directory /usr/lib/emacsen-common/packages/install/git emacs xemacs21 failed at /usr/lib/emacsen-common/lib.pl line 19, line 1. dpkg: error processing package git-el (--configure): installed git-el package post-installation script subprocess returned error exit status 2 Processing triggers for libc-bin (2.31-11) ... Errors were encountered while processing: git-el cheers, Andreas git-el=1:2.30.2-1_xemacs21.log.gz Description: application/gzip
Bug#987192: marked as done (ceph-base: purging deletes /etc/ceph/rbdmap owned by ceph-common)
Your message dated Tue, 20 Apr 2021 14:33:42 +
with message-id
and subject line Bug#987192: fixed in ceph 14.2.20-1
has caused the Debian Bug report #987192,
regarding ceph-base: purging deletes /etc/ceph/rbdmap owned by ceph-common
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.)
--
987192: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=987192
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ceph-base
Version: 14.2.18-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package removes files that
were installed by another package.
>From the attached log (scroll to the bottom...):
1m5.2s ERROR: FAIL: debsums reports modifications inside the chroot:
debsums: missing file /etc/ceph/rbdmap (from ceph-common package)
postrm has
if [ "${1}" = "purge" ] ; then
rm -rf /var/log/ceph
rm -rf /etc/ceph
fi
cheers,
Andreas
ceph-base_14.2.18-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: ceph
Source-Version: 14.2.20-1
Done: Thomas Goirand
We believe that the bug you reported is fixed in the latest version of
ceph, 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 987...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Thomas Goirand (supplier of updated ceph 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, 20 Apr 2021 13:00:13 +0200
Source: ceph
Architecture: source
Version: 14.2.20-1
Distribution: unstable
Urgency: medium
Maintainer: Ceph Packaging Team
Changed-By: Thomas Goirand
Closes: 986173 986974 987192
Changes:
ceph (14.2.20-1) unstable; urgency=medium
.
* New upstream point release (Closes: #986173):
- Fixes CVE-2021-20288: Unauthorized global_id reuse in cephx
(Closes: #986974)
* Remove "rm -rf /etc/ceph" in ceph-base.postinst (Closes: #987192).
Checksums-Sha1:
f7938952f01b07e007c54723e251cb0915566466 5896 ceph_14.2.20-1.dsc
59fffa0674e82770e54b7c411caf9749bb93aec1 129271968 ceph_14.2.20.orig.tar.gz
a49a3fc6b64f76f206d791b09f417d5f659cea05 111848 ceph_14.2.20-1.debian.tar.xz
4743457c8e33e71b1223bc14f6f92dab44cd933b 34310 ceph_14.2.20-1_amd64.buildinfo
Checksums-Sha256:
335d84ba78fb1edb07dcf237694e769396ae785c1a328de63fc4d1995a5ced13 5896
ceph_14.2.20-1.dsc
d3ebf4d8ca2a424927e22e5d8eb4af44b902d2d7f67d5f48688a77894d60e390 129271968
ceph_14.2.20.orig.tar.gz
cdb581cf3ef974f3479698c59c8f2a9927a2c8ab5960f214440a434fab956f08 111848
ceph_14.2.20-1.debian.tar.xz
f836949fb1130266f0ddd2bb34f6c8441a28e93b5577b10c79ea6efcf4b066ae 34310
ceph_14.2.20-1_amd64.buildinfo
Files:
0ee1ba12c5a86a90eadcdb4cd7a95e16 5896 admin optional ceph_14.2.20-1.dsc
a7c9095ba00b4a75b24cf27c3c1c1d61 129271968 admin optional
ceph_14.2.20.orig.tar.gz
84845ed0daec9e18ca6ed321a64fa213 111848 admin optional
ceph_14.2.20-1.debian.tar.xz
6bb248bb653ff15b6bb4d061094863a8 34310 admin optional
ceph_14.2.20-1_amd64.buildinfo
-BEGIN PGP SIGNATURE-
iQIzBAEBCAAdFiEEoLGp81CJVhMOekJc1BatFaxrQ/4FAmB+28sACgkQ1BatFaxr
Q/7GeQ//WnErc5KpisnonZ7d5U/wyH7CE3iU2JGpZVeCGED+/M1Tom/gq80Ttvse
BenC+qjlYNu5QyCZMEZcBreBiy4+Rw20V4YljygAyNjG9zzPns6L4lh1lF8oJOFJ
L3vraZZI91R0vkVlg6Q5cX71swF3LzzxH8S1ESIOssQfz6Y1A/A1nhHtYNH1uh7P
u81OnpF3c5aK5crZ3/eLTvxeDha4Pni26QawOvgyjxD9fCLPeTJcbuU98KRO4Ru0
/QiTc7WfpcY7eYuiO0qZWCu5X8dLZ/w6ykgHx1xfSZCiK9vI0C9caJviqRd5EHqE
B6QLFI9YzHJ68Y7jJQqbb36ubOOl1UK9lWFsGZu2RKsmqHhmBb++Qg529ZVtx9SB
7w8IixKVLe0DOTNAlvxQXh4dgc9sZWk5/l9mikk3zVmci7rlNsdmdf6AAXKWt/ib
vMdN6yr4ieeElraE8wJdg8LuGYd/DxHHoFnBkuCzdHhueb7jd+l11bH2IhwsExO3
HtmTPtZja5GkgfeYzgfeOIj1wrnrVFopqp7Lfi0d87IaoHKBMG1UmDEEYYSxuU9x
51GYadPjgZeDn1YCHdelY7uWXPdkLRl6FhXU6qXyDV2vAygr6oeNB11Ui2Q1F0Ds
7RDOspsgNZLMg7V5pHKYjQAnKLsXTcQiVei5G6dWjik8E+SOwLs=
=VgcA
-END PGP SIGNATURE End Message ---
Bug#986974: marked as done (ceph: CVE-2021-20288)
Your message dated Tue, 20 Apr 2021 14:33:42 + with message-id and subject line Bug#986974: fixed in ceph 14.2.20-1 has caused the Debian Bug report #986974, regarding ceph: CVE-2021-20288 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.) -- 986974: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=986974 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ceph Version: 14.2.18-1 Severity: grave Tags: security upstream Justification: user security hole X-Debbugs-Cc: car...@debian.org, Debian Security Team Hi, The following vulnerability was published for ceph. CVE-2021-20288[0]: | Unauthorized global_id reuse in cephx If you fix the vulnerability please also make sure to include the CVE (Common Vulnerabilities & Exposures) id in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2021-20288 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-20288 [1] https://bugzilla.redhat.com/show_bug.cgi?id=1938031 [2] https://www.openwall.com/lists/oss-security/2021/04/14/2 Please adjust the affected versions in the BTS as needed. Regards, Salvatore --- End Message --- --- Begin Message --- Source: ceph Source-Version: 14.2.20-1 Done: Thomas Goirand We believe that the bug you reported is fixed in the latest version of ceph, 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 986...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Thomas Goirand (supplier of updated ceph 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, 20 Apr 2021 13:00:13 +0200 Source: ceph Architecture: source Version: 14.2.20-1 Distribution: unstable Urgency: medium Maintainer: Ceph Packaging Team Changed-By: Thomas Goirand Closes: 986173 986974 987192 Changes: ceph (14.2.20-1) unstable; urgency=medium . * New upstream point release (Closes: #986173): - Fixes CVE-2021-20288: Unauthorized global_id reuse in cephx (Closes: #986974) * Remove "rm -rf /etc/ceph" in ceph-base.postinst (Closes: #987192). Checksums-Sha1: f7938952f01b07e007c54723e251cb0915566466 5896 ceph_14.2.20-1.dsc 59fffa0674e82770e54b7c411caf9749bb93aec1 129271968 ceph_14.2.20.orig.tar.gz a49a3fc6b64f76f206d791b09f417d5f659cea05 111848 ceph_14.2.20-1.debian.tar.xz 4743457c8e33e71b1223bc14f6f92dab44cd933b 34310 ceph_14.2.20-1_amd64.buildinfo Checksums-Sha256: 335d84ba78fb1edb07dcf237694e769396ae785c1a328de63fc4d1995a5ced13 5896 ceph_14.2.20-1.dsc d3ebf4d8ca2a424927e22e5d8eb4af44b902d2d7f67d5f48688a77894d60e390 129271968 ceph_14.2.20.orig.tar.gz cdb581cf3ef974f3479698c59c8f2a9927a2c8ab5960f214440a434fab956f08 111848 ceph_14.2.20-1.debian.tar.xz f836949fb1130266f0ddd2bb34f6c8441a28e93b5577b10c79ea6efcf4b066ae 34310 ceph_14.2.20-1_amd64.buildinfo Files: 0ee1ba12c5a86a90eadcdb4cd7a95e16 5896 admin optional ceph_14.2.20-1.dsc a7c9095ba00b4a75b24cf27c3c1c1d61 129271968 admin optional ceph_14.2.20.orig.tar.gz 84845ed0daec9e18ca6ed321a64fa213 111848 admin optional ceph_14.2.20-1.debian.tar.xz 6bb248bb653ff15b6bb4d061094863a8 34310 admin optional ceph_14.2.20-1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEoLGp81CJVhMOekJc1BatFaxrQ/4FAmB+28sACgkQ1BatFaxr Q/7GeQ//WnErc5KpisnonZ7d5U/wyH7CE3iU2JGpZVeCGED+/M1Tom/gq80Ttvse BenC+qjlYNu5QyCZMEZcBreBiy4+Rw20V4YljygAyNjG9zzPns6L4lh1lF8oJOFJ L3vraZZI91R0vkVlg6Q5cX71swF3LzzxH8S1ESIOssQfz6Y1A/A1nhHtYNH1uh7P u81OnpF3c5aK5crZ3/eLTvxeDha4Pni26QawOvgyjxD9fCLPeTJcbuU98KRO4Ru0 /QiTc7WfpcY7eYuiO0qZWCu5X8dLZ/w6ykgHx1xfSZCiK9vI0C9caJviqRd5EHqE B6QLFI9YzHJ68Y7jJQqbb36ubOOl1UK9lWFsGZu2RKsmqHhmBb++Qg529ZVtx9SB 7w8IixKVLe0DOTNAlvxQXh4dgc9sZWk5/l9mikk3zVmci7rlNsdmdf6AAXKWt/ib vMdN6yr4ieeElraE8wJdg8LuGYd/DxHHoFnBkuCzdHhueb7jd+l11bH2IhwsExO3 HtmTPtZja5GkgfeYzgfeOIj1wrnrVFopqp7Lfi0d87IaoHKBMG1UmDEEYYSxuU9x 51GYadPjgZeDn1YCHdelY7uWXPdkLRl6FhXU6qXyDV2vAygr6oeNB11Ui2Q1F0Ds 7RDOspsgNZLMg7V5pHKYjQAnKLsXTcQiVei5G6dWjik8E+SOwLs= =VgcA -END PGP SIGNATURE End Message ---
Processed: Re: Bug#987226: youtube-dl: ERROR: Unable to extract yt initial data
Processing control commands: > severity -1 important Bug #987226 [youtube-dl] youtube-dl: ERROR: Unable to extract yt initial data Severity set to 'important' from 'grave' -- 987226: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=987226 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#987226: youtube-dl: ERROR: Unable to extract yt initial data
control: severity -1 important thanks hi Mike, On Mon, Apr 19, 2021 at 09:39:55PM +, Mike Gabriel wrote: > Package: youtube-dl > Severity: grave you didn't really describe why you thought the severity should be grave, but anyway: $ youtube-dl https://twitter.com/zemodancingto/status/1381937205787172867#m [twitter] 1381937205787172867: Downloading guest token [twitter] 1381937205787172867: Downloading JSON metadata [twitter] 1381937205787172867: Downloading m3u8 information [download] Destination: zemo dancing to - Rick Astley - Never Gonna Give You Up-1381937205787172867.mp4 [download] 100% of 3.00MiB in 00:01 $ so this clearly shows the package isn't broken for everyone. -- cheers, Holger ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ holger@(debian|reproducible-builds|layer-acht).org ⢿⡄⠘⠷⠚⠋⠀ OpenPGP: B8BF54137B09D35CF026FE9D 091AB856069AAA1C ⠈⠳⣄ In Germany we don‘t say „Happy Valentine‘s Day, I love you“, we say „ich werde diesen vom Markt kreierten, konsumorientierten Trend des Kapitalismus nicht unterstützen,“ and I think that’s beautiful. (Hazel Brugger) signature.asc Description: PGP signature
Bug#987260: lyskom-elisp-client: fails to install with xemacs21
Package: lyskom-elisp-client
Version: 0.48+git.20200923.ec349ff4-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package failed to install if
xemacs21 is already installed.
>From the attached log (scroll to the bottom...):
Preparing to unpack
.../lyskom-elisp-client_0.48+git.20200923.ec349ff4-1_all.deb ...
Unpacking lyskom-elisp-client (0.48+git.20200923.ec349ff4-1) ...
Setting up lyskom-elisp-client (0.48+git.20200923.ec349ff4-1) ...
Install lyskom-elisp-client for emacs
install/lyskom-elisp-client: Handling install of emacsen flavor emacs
Install lyskom-elisp-client for xemacs21
install/lyskom-elisp-client: Handling install of emacsen flavor xemacs21
install/lyskom-elisp-client: byte-compiling for xemacs21
Please wait...
Compiling /usr/share/xemacs21/site-lisp/lyskom-elisp-client.el...
Ignoring `eval:' in file's local variables
While compiling lyskom-help-format-keymap in file
/usr/share/xemacs21/site-lisp/lyskom-elisp-client.el:
** variable this-command-keys bound but not referenced
While compiling toplevel forms:
!! Invalid read syntax (("#"))
>>Error occurred processing lyskom-elisp-client.el:
Invalid read syntax: "#"
Done
ERROR: install script from lyskom-elisp-client package failed
dpkg: error processing package lyskom-elisp-client (--configure):
installed lyskom-elisp-client package post-installation script subprocess
returned error exit status 1
Errors were encountered while processing:
lyskom-elisp-client
cheers,
Andreas
lyskom-elisp-client=0.48+git.20200923.ec349ff4-1_xemacs21.log.gz
Description: application/gzip
Processed: Re: maxima-emacs: maxima-emacs 5.44 does not work with XEmacs
Processing control commands: > severity -1 serious Bug #969410 [maxima-emacs] maxima-emacs: maxima-emacs 5.44 does not work with XEmacs Severity set to 'serious' from 'normal' -- 969410: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=969410 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#987259: utop: fails to install with xemacs21
Package: utop
Version: 2.7.0-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package failed to install if
xemacs21 is already installed.
>From the attached log (scroll to the bottom...):
Setting up utop (2.7.0-1) ...
Install emacsen-common for xemacs21
emacsen-common: Handling install of emacsen flavor xemacs21
Loading /usr/share/emacsen-common/debian-startup...
Loading 00debian...
Compiling /usr/share/xemacs21/site-lisp/debian-startup.el...
Wrote /usr/share/xemacs21/site-lisp/debian-startup.elc
Done
Install utop for xemacs21
install/utop: Handling install for emacsen flavor xemacs21
Loading /usr/share/emacsen-common/debian-startup...
Loading 00debian...
Compiling /usr/share/emacs/site-lisp/utop.el...
While compiling toplevel forms in file /usr/share/emacs/site-lisp/utop.el:
!! File error (("Cannot open load file" "pcase"))
>>Error occurred processing /usr/share/emacs/site-lisp/utop.el: Cannot open
load file: pcase
Done
ERROR: install script from utop package failed
dpkg: error processing package utop (--configure):
installed utop package post-installation script subprocess returned error
exit status 1
Processing triggers for libc-bin (2.31-11) ...
Errors were encountered while processing:
utop
cheers,
Andreas
utop=2.7.0-1_xemacs21.log.gz
Description: application/gzip
Bug#987258: epix: fails to install with xemacs21
Package: epix Version: 1.2.19-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package failed to install if xemacs21 is already installed. >From the attached log (scroll to the bottom...): Setting up epix (1.2.19-1) ... Install emacsen-common for xemacs21 emacsen-common: Handling install of emacsen flavor xemacs21 Loading /usr/share/emacsen-common/debian-startup... Loading 00debian... Compiling /usr/share/xemacs21/site-lisp/debian-startup.el... Wrote /usr/share/xemacs21/site-lisp/debian-startup.elc Done Install epix for xemacs21 install/epix: Handling install for emacsen flavor xemacs21 cp: cannot stat '*.el': No such file or directory ERROR: install script from epix package failed dpkg: error processing package epix (--configure): installed epix package post-installation script subprocess returned error exit status 1 Setting up imagemagick (8:6.9.11.60+dfsg-1) ... Processing triggers for libc-bin (2.31-11) ... Processing triggers for tex-common (6.16) ... Running updmap-sys. This may take some time... done. Running mktexlsr /var/lib/texmf ... done. Building format(s) --all. This may take some time... done. Errors were encountered while processing: epix cheers, Andreas epix=1.2.19-1_xemacs21.log.gz Description: application/gzip
Bug#987257: libcw{7,-dev}: removal of libcw{7,-dev} makes files disappear from libcw6{,-dev}
Package: libcw-dev,libcw7 Version: 3.6.0-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts replaces-without-breaks Hi, during a test with piuparts and DOSE tools I noticed your package causes removal of files that also belong to another package. This is caused by using Replaces without corresponding Breaks. The installation sequence to reproduce this problem is apt-get install libcw6-dev # (1) apt-get install libcw-dev apt-get remove libcw-dev # (2) The list of installed files at points (1) and (2) should be identical, but the following files have disappeared: /usr/include/libcw.h /usr/include/libcw_debug.h /usr/lib/x86_64-linux-gnu/libcw.a /usr/lib/x86_64-linux-gnu/libcw.so /usr/lib/x86_64-linux-gnu/pkgconfig/libcw.pc /usr/share/man/man3/libcw.3.gz /usr/share/man/man7/cw.7.gz This is a serious bug violating policy 7.6, see https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces and also see the footnote that describes this incorrect behavior: https://www.debian.org/doc/debian-policy/ch-relationships.html#id13 The libcw-dev package has the following relationships with libcw6-dev: Conflicts: n/a Replaces: libcw3-dev, libcw4-dev, libcw5-dev, libcw6-dev, unixcw-dev Breaks:libcw3-dev, unixcw-dev The libcw7 package has the following relationships with libcw6: Conflicts: n/a Replaces: libcw3, libcw4, libcw5, libcw6, unixcw Breaks:libcw3, unixcw >From the attached log (scroll to the bottom...): 0m25.1s ERROR: FAIL: After purging files have disappeared: /usr/include/libcw.h owned by: libcw-dev /usr/include/libcw_debug.h owned by: libcw-dev /usr/lib/x86_64-linux-gnu/libcw.a owned by: libcw-dev /usr/lib/x86_64-linux-gnu/libcw.so -> libcw.so.6.6.1 owned by: libcw-dev /usr/lib/x86_64-linux-gnu/pkgconfig/libcw.pc owned by: libcw-dev /usr/share/man/man3/libcw.3.gz owned by: libcw-dev /usr/share/man/man7/cw.7.gzowned by: libcw7:amd64 0m25.1s ERROR: FAIL: After purging files have been modified: /var/lib/dpkg/info/libcw6-dev.list not owned /var/lib/dpkg/info/libcw6:amd64.list not owned cheers, Andreas libcw6-dev=3.5.1-4_libcw-dev=3.6.0-1.log.gz Description: application/gzip
Processed: Bug#987192 marked as pending in ceph
Processing control commands: > tag -1 pending Bug #987192 [ceph-base] ceph-base: purging deletes /etc/ceph/rbdmap owned by ceph-common Added tag(s) pending. -- 987192: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=987192 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#987192: marked as pending in ceph
Control: tag -1 pending Hello, Bug #987192 in ceph reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/ceph-team/ceph/-/commit/4f04ea46b6fe23a24b43f04c49b7413cffdec8c8 Remove "rm -rf /etc/ceph" in ceph-base.postinst (Closes: #987192). (this message was generated automatically) -- Greetings https://bugs.debian.org/987192
Bug#986085: marked as done (wordpress-theme-twentytwentyone: broken symlink /var/lib/wordpress/wp-content/themes/twentytwentytwentyone -> /usr/share/wordpress/wp-content/themes/twentytwentytwentyone)
Your message dated Tue, 20 Apr 2021 12:48:25 + with message-id and subject line Bug#986085: fixed in wordpress 5.7.1+dfsg1-2 has caused the Debian Bug report #986085, regarding wordpress-theme-twentytwentyone: broken symlink /var/lib/wordpress/wp-content/themes/twentytwentytwentyone -> /usr/share/wordpress/wp-content/themes/twentytwentytwentyone 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.) -- 986085: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=986085 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: wordpress-theme-twentytwentyone Version: 5.7+dfsg1-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package ships (or creates) a broken symlink. >From the attached log (scroll to the bottom...): 0m22.5s ERROR: FAIL: Broken symlinks: /var/lib/wordpress/wp-content/themes/twentytwentytwentyone -> /usr/share/wordpress/wp-content/themes/twentytwentytwentyone (wordpress-theme-twentytwentyone) The target does not exist in any package. cheers, Andreas wordpress-theme-twentytwentyone_5.7+dfsg1-1.log.gz Description: application/gzip --- End Message --- --- Begin Message --- Source: wordpress Source-Version: 5.7.1+dfsg1-2 Done: Craig Small We believe that the bug you reported is fixed in the latest version of wordpress, 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 986...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Craig Small (supplier of updated wordpress 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: SHA512 Format: 1.8 Date: Tue, 20 Apr 2021 22:28:40 +1000 Source: wordpress Architecture: source Version: 5.7.1+dfsg1-2 Distribution: unstable Urgency: medium Maintainer: Craig Small Changed-By: Craig Small Closes: 986085 Changes: wordpress (5.7.1+dfsg1-2) unstable; urgency=medium . * Fix symlink for 2021 theme Closes: #986085 Checksums-Sha1: 8dbea665ba21e387260f6590ae2f0bb3bef7dc25 2392 wordpress_5.7.1+dfsg1-2.dsc 31d4045d2acb1acf72f12b23acf6007a01858016 6824396 wordpress_5.7.1+dfsg1-2.debian.tar.xz 235ea26792b7bf74bac633952e97036ac8ba0934 7494 wordpress_5.7.1+dfsg1-2_amd64.buildinfo Checksums-Sha256: bf44661e48cc390cc20c024729ad814b6f6f07344673ac1d84c1c8fa98898017 2392 wordpress_5.7.1+dfsg1-2.dsc 6b61f231fb1a89389d2cf76b3a6e196fc0117c0e657bc338633a81d982dda498 6824396 wordpress_5.7.1+dfsg1-2.debian.tar.xz 4b2022aaeb70087a0f5c049c5dd42f87fc34c44f93390e22e4f7a0dec8d7ab10 7494 wordpress_5.7.1+dfsg1-2_amd64.buildinfo Files: bc6798f0da4f68c932c712e8c82cb018 2392 web optional wordpress_5.7.1+dfsg1-2.dsc f12800e4bb38d7f212613fe3ad295a8d 6824396 web optional wordpress_5.7.1+dfsg1-2.debian.tar.xz f5e4d6ddf7f3914b814122aae51681e1 7494 web optional wordpress_5.7.1+dfsg1-2_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEXT3w9TizJ8CqeneiAiFmwP88hOMFAmB+yb4ACgkQAiFmwP88 hOOXow//Ud3xJNpMyYcbc/RppKzMq59MMx2UaOOJZEUH4DUx3lGwm/QAVfUIPpS/ Lag+Iv2rFHu1QEXhV27qX/2gI4AFxz9e9PNkmeLUYVQM/3Bai/dIM/mBWlcCLL32 TSuTVenMWknZheN4oJxDeNOPaBVQAYFgM1VjfChE9MI4WrMNUGvEbTb5eUqE87J7 6TpwU1Q8XBOwOO74OIeKnUu3Q5s7Uh5a7Odp2fuI5Zar3sVZiOUo/sTVOPNH8xZq /eI4ADKtIWbkjyytJLaQ4+6e6KA07ylMfyViPCJdx4RWyox/0a5rjdDL2Ivi0K38 uDcVmx0NpeBjgTCoOsgUPJ0pPjmxx8WQbe2wgd9Lz1GUhq1hjBvkmaiJVx8LNH5J zjrNcOBIjwMAkRHPLp4l3KSHtE2oeQ4T8bjEYvRHVzX0o/WB264yVeRc0QcGgfkb C18fqXXvqIFcRECLYqWxcsQsxqD9BRE6Il6VkJIHNPB+1gu87gTcZfqSKWpeWksD xIKLBr0aUrB0XQPfjHrLgStTl12ebKrBv4/Z+qOYNWHYu7cTkcGmAVBlJRMylGv3 4ji2guInXibnEnTJ4aChonUaF2GbwLREVjwr5VDH1IUk7xN8EdQodiu2wXxbYZMw PqGdRRuIRSzYLiyJwTV/wEc4ucvtb6sriqvNckHBa8r9iLnM3Z8= =xUtR -END PGP SIGNATURE End Message ---
Bug#986085: marked as pending in SOURCENAME
Control: tag -1 pending Hello, Bug #986085 in SOURCENAME reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/debian/wordpress/-/commit/9fb013e3ed28ef13529aba0a0f8690f5bac99b82 Fix symlink for 2021 theme Closes: #986085 (this message was generated automatically) -- Greetings https://bugs.debian.org/986085
Processed: Bug#986085 marked as pending in SOURCENAME
Processing control commands: > tag -1 pending Bug #986085 [wordpress-theme-twentytwentyone] wordpress-theme-twentytwentyone: broken symlink /var/lib/wordpress/wp-content/themes/twentytwentytwentyone -> /usr/share/wordpress/wp-content/themes/twentytwentytwentyone Added tag(s) pending. -- 986085: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=986085 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#987165: marked as done (offlineimap3: flaky autopkgtest: OfflineImapError("Failed to start ")
Your message dated Tue, 20 Apr 2021 12:18:26 +
with message-id
and subject line Bug#987165: fixed in offlineimap3
0.0~git20210225.1e7ef9e+dfsg-4
has caused the Debian Bug report #987165,
regarding offlineimap3: flaky autopkgtest: OfflineImapError("Failed to start "
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.)
--
987165: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=987165
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: offlineimap3
Version: 0.0~git20210225.1e7ef9e+dfsg-3
Severity: serious
Tags: sid bullseye
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: flaky
Dear maintainer(s),
Your package has an autopkgtest, great. However, I looked into the
history of your autopkgtest [1] and I noticed the it fails regularly,
while a rerun passes. I copied some of the output at the bottom
of this report.
Because the unstable-to-testing migration software now blocks on
regressions in testing, flaky tests, i.e. tests that flip between
passing and failing without changes to the list of installed packages,
are causing people unrelated to your package to spend time on these
tests.
Paul
[1] ...
https://ci.debian.net/packages/o/offlineimap3/testing/amd64/
https://ci.debian.net/packages/o/offlineimap3/testing/arm64/
https://ci.debian.net/packages/o/offlineimap3/testing/armhf/
https://ci.debian.net/packages/o/offlineimap3/testing/i386/
https://ci.debian.net/packages/o/offlineimap3/testing/ppc64el/
https://ci.debian.net/data/autopkgtest/testing/amd64/o/offlineimap3/11437720/log.gz
autopkgtest [04:27:00]: test testmail: [---
'/tmp/autopkgtest-lxc.7vdzo2pi/downtmp/build.iAb/src/debian/tests' ->
'/tmp/autopkgtest-lxc.7vdzo2pi/downtmp/autopkgtest_tmp/tests'
'/tmp/autopkgtest-lxc.7vdzo2pi/downtmp/build.iAb/src/debian/tests/control'
-> '/tmp/autopkgtest-lxc.7vdzo2pi/downtmp/autopkgtest_tmp/tests/control'
'/tmp/autopkgtest-lxc.7vdzo2pi/downtmp/build.iAb/src/debian/tests/offlinerc'
-> '/tmp/autopkgtest-lxc.7vdzo2pi/downtmp/autopkgtest_tmp/tests/offlinerc'
'/tmp/autopkgtest-lxc.7vdzo2pi/downtmp/build.iAb/src/debian/tests/testmail'
-> '/tmp/autopkgtest-lxc.7vdzo2pi/downtmp/autopkgtest_tmp/tests/testmail'
'/tmp/autopkgtest-lxc.7vdzo2pi/downtmp/build.iAb/src/debian/tests/user.py'
-> '/tmp/autopkgtest-lxc.7vdzo2pi/downtmp/autopkgtest_tmp/tests/user.py'
OfflineIMAP 7.3.0
Licensed under the GNU GPL v2 or any later version (with an OpenSSL
exception)
imaplib2 v3.05, Python v3.9.2, OpenSSL 1.1.1k 25 Mar 2021
imaplib2: 3.05
Remote repository 'Remote': type 'IMAP'
Host: localhost Port: None SSL: False
Establishing connection to localhost:143 (Remote)
Server supports ID extension.
Server welcome string: b'* OK [CAPABILITY IMAP4rev1 SASL-IR
LOGIN-REFERRALS ID ENABLE IDLE LITERAL+ STARTTLS AUTH=PLAIN] Dovecot
(Debian) ready.'
Server capabilities: ('IMAP4REV1', 'SASL-IR', 'LOGIN-REFERRALS', 'ID',
'ENABLE', 'IDLE', 'SORT', 'SORT=DISPLAY', 'THREAD=REFERENCES',
'THREAD=REFS', 'THREAD=ORDEREDSUBJECT', 'MULTIAPPEND', 'URL-PARTIAL',
'CATENATE', 'UNSELECT', 'CHILDREN', 'NAMESPACE', 'UIDPLUS',
'LIST-EXTENDED', 'I18NLEVEL=1', 'CONDSTORE', 'QRESYNC', 'ESEARCH',
'ESORT', 'SEARCHRES', 'WITHIN', 'CONTEXT=SEARCH', 'LIST-STATUS',
'BINARY', 'MOVE', 'SNIPPET=FUZZY', 'PREVIEW=FUZZY', 'STATUS=SIZE',
'SAVEDATE', 'LITERAL+', 'NOTIFY', 'SPECIAL-USE')
Folderlist:
INBOX
Local repository 'Local': type 'Maildir'
Folderlist:
OfflineIMAP 7.3.0
Licensed under the GNU GPL v2 or any later version (with an OpenSSL
exception)
imaplib2 v3.05, Python v3.9.2, OpenSSL 1.1.1k 25 Mar 2021
Account sync Test:
*** Processing account Test
Establishing connection to localhost:143 (Remote)
ERROR: Failed to start TLS connection: command: CAPABILITY =>
connection terminated
*** Finished account 'Test' in 3:00
ERROR: Exceptions occurred during the run!
ERROR: Failed to start TLS connection: command: CAPABILITY => connection
terminated
Traceback:
File "/usr/share/offlineimap3/offlineimap/accounts.py", line 298, in
syncrunner
self.__sync()
File "/usr/share/offlineimap3/offlineimap/accounts.py", line 374, in
__sync
remoterepos.getfolders()
File "/usr/share/offlineimap3/offlineimap/repository/IMAP.py", line
667, in getfolders
imapobj = self.imapserver.acquireconnection()
File "/usr/share/offlineimap3/offlineimap/imapserver.py", line 588, in
acquireconnection
self.__authn_helper(imapobj)
File "/usr/share/offlineimap3/offlineimap/imapserver.py", line 434, in
__authn_helper
self.__start_tls(imapobj)
File
Bug#987249: bookletimposer: Failing autopkgtests after imagemagick change to disable ghostscript handled formats
Source: bookletimposer Version: 0.3+ds-1 Severity: serious Justification: failing autopkgtests X-Debbugs-Cc: car...@debian.org Hi imagemagick / 8:6.9.11.60+dfsg-1.2 upload disabled ghostscript handled formats (which already was done earlier in DSA 4712-1 / imagemagick 8:6.9.10.23+dfsg-2.1+deb10u1) Unfortunately bookletimposer's autopkgtests (integration) uses convert xc:none -page A4 $i.pdf to first create 4 PDFs. But this is only preparational for the own tests for bookletimposer itself, so the failure is false in the sense it does not indicate a problem with bookletimposer. The autopkgtests should try to avoid first creating 4 PDFs with convert, as imagemagick disables now by default the ghostscript handled formats and so convert to PDF will be blocked. Regards, Salvatore
Bug#987247: imagemagick: failing autopkgtests after disabling of ghostscript handled formats
Source: imagemagick Version: 8:6.9.11.60+dfsg-1.2 Severity: serious Justification: failing autopkgtests X-Debbugs-Cc: car...@debian.org,debian-rele...@lists.debian.org After disabling the ghostscript handled formats in policy.xml for imagemagick (following what was done in stable already with DSA 4712-1 / imagemagick 8:6.9.10.23+dfsg-2.1+deb10u1) the autopkgtests of imagemagick itself fail because they use 'convert rose: pdf:/dev/null' in part of the tests. Those need to be adjusted as well, and was a fallout of the previous done upload done as 8:6.9.11.60+dfsg-1.2. Regards, Salvatore
Bug#987196: marked as done (neutron-common,neutron-metadata-agent: both manage /etc/neutron/metadata_agent.ini)
Your message dated Tue, 20 Apr 2021 11:48:26 +
with message-id
and subject line Bug#987196: fixed in neutron 2:17.1.1-1
has caused the Debian Bug report #987196,
regarding neutron-common,neutron-metadata-agent: both manage
/etc/neutron/metadata_agent.ini
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.)
--
987196: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=987196
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: neutron-common,neutron-metadata-agent
Version: 2:17.1.0-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed that removal of neutron-metadata-agent
removes files that were installed by another package.
The removed files were already present before the package was installed,
they may have been shipped or created by a dependency.
>From the attached log (scroll to the bottom...):
2m34.7s ERROR: FAIL: After purging files have disappeared:
/etc/neutron/metadata_agent.ininot owned
That file is managed by two packages:
/var/lib/dpkg/info/neutron-metadata-agent.postinst:CONF_FILE=/etc/neutron/metadata_agent.ini
/var/lib/dpkg/info/neutron-metadata-agent.postinst: install -D -m
0640 -o neutron -g neutron /usr/share/neutron-metadata-agent/metadata_agent.ini
${CONF_FILE}
/var/lib/dpkg/info/neutron-metadata-agent.postrm: rm -f
/etc/neutron/metadata_agent.ini
/var/lib/dpkg/info/neutron-common.postinst: pkgos_write_new_conf neutron
metadata_agent.ini
/var/lib/dpkg/info/neutron-common.postrm: rm -f
/etc/neutron/metadata_agent.ini
cheers,
Andreas
neutron-metadata-agent_2:17.1.0-2.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: neutron
Source-Version: 2:17.1.1-1
Done: Thomas Goirand
We believe that the bug you reported is fixed in the latest version of
neutron, 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 987...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Thomas Goirand (supplier of updated neutron 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, 20 Apr 2021 12:31:47 +0200
Source: neutron
Architecture: source
Version: 2:17.1.1-1
Distribution: unstable
Urgency: medium
Maintainer: Debian OpenStack
Changed-By: Thomas Goirand
Closes: 987196
Changes:
neutron (2:17.1.1-1) unstable; urgency=medium
.
* Tune neutron-api-uwsgi.ini for performance.
* New upstream release.
* neutron-common: do not manage metadata_agent.ini, and let the
neutron-metadata-agent package do it. Thanks to Andreas Beckmann for the
bug report. (Closes: #987196).
Checksums-Sha1:
6a80192d68d4d833e166e9e5699576a465a4a8d3 4945 neutron_17.1.1-1.dsc
f05d9b0dbc1fd20369abafce8d0db795ae5c57b3 10983432 neutron_17.1.1.orig.tar.xz
baf23f3c3fee273f730465ccb18af9103a4c26fc 49196 neutron_17.1.1-1.debian.tar.xz
e99d4efd10c8dad279768d257e1836c49ccebaf7 19826 neutron_17.1.1-1_amd64.buildinfo
Checksums-Sha256:
578a4a95b0ff5a2691f9281613dc047f24390a3290baf892b57ed162eac3f1ea 4945
neutron_17.1.1-1.dsc
ad71fa5bbb33fa0e468c94345b4d34913e19285a0bb685fae005c6d36352c755 10983432
neutron_17.1.1.orig.tar.xz
abc139db848e9f58db50dc8fb64562a771745ceb503af3a907bf4d620d8dab0c 49196
neutron_17.1.1-1.debian.tar.xz
022babbe68781a45778878b03ddd2fb2513184355dcf1513dbc99f32360e6ceb 19826
neutron_17.1.1-1_amd64.buildinfo
Files:
3490d27c68f908e093e3a3c552d1ed6c 4945 net optional neutron_17.1.1-1.dsc
0e1a63e3c7fc0b9972755ce730d173b8 10983432 net optional
neutron_17.1.1.orig.tar.xz
9f9024593abaf9678c18a5866c886df4 49196 net optional
neutron_17.1.1-1.debian.tar.xz
e2e30af0a28fca2e661bfccdef183ab8 19826 net optional
neutron_17.1.1-1_amd64.buildinfo
-BEGIN PGP SIGNATURE-
iQIzBAEBCAAdFiEEoLGp81CJVhMOekJc1BatFaxrQ/4FAmB+uSQACgkQ1BatFaxr
Q/7ulA//W5VtLYukagbD2aBjZstGpaf+KSLW+Hh1zNLfNLFD2cq6Qr2ADUSl/Aiu
bPTrEQaa6LzZQ2ccWXvLRv8bYVFhptQumF1Ws1bUKq3uvVG4Kn7vIKbkUCt9nH0g
GPr19zvrO9x7R7AxXYwsbOEnXK2bCKIDMFbosXM5ckChXwM5MokEJYOW1C8bx3TA
S23igLY5oa1wz4vQXMnFWBUnfYqrAuovzElkLIlcHylwQ5D5yIWn7Pi2cw60vBYw
Bug#987196: marked as done (neutron-common,neutron-metadata-agent: both manage /etc/neutron/metadata_agent.ini)
Your message dated Tue, 20 Apr 2021 11:18:29 +
with message-id
and subject line Bug#987196: fixed in neutron 2:18.0.0-2
has caused the Debian Bug report #987196,
regarding neutron-common,neutron-metadata-agent: both manage
/etc/neutron/metadata_agent.ini
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.)
--
987196: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=987196
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: neutron-common,neutron-metadata-agent
Version: 2:17.1.0-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed that removal of neutron-metadata-agent
removes files that were installed by another package.
The removed files were already present before the package was installed,
they may have been shipped or created by a dependency.
>From the attached log (scroll to the bottom...):
2m34.7s ERROR: FAIL: After purging files have disappeared:
/etc/neutron/metadata_agent.ininot owned
That file is managed by two packages:
/var/lib/dpkg/info/neutron-metadata-agent.postinst:CONF_FILE=/etc/neutron/metadata_agent.ini
/var/lib/dpkg/info/neutron-metadata-agent.postinst: install -D -m
0640 -o neutron -g neutron /usr/share/neutron-metadata-agent/metadata_agent.ini
${CONF_FILE}
/var/lib/dpkg/info/neutron-metadata-agent.postrm: rm -f
/etc/neutron/metadata_agent.ini
/var/lib/dpkg/info/neutron-common.postinst: pkgos_write_new_conf neutron
metadata_agent.ini
/var/lib/dpkg/info/neutron-common.postrm: rm -f
/etc/neutron/metadata_agent.ini
cheers,
Andreas
neutron-metadata-agent_2:17.1.0-2.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: neutron
Source-Version: 2:18.0.0-2
Done: Thomas Goirand
We believe that the bug you reported is fixed in the latest version of
neutron, 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 987...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Thomas Goirand (supplier of updated neutron 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, 20 Apr 2021 12:16:51 +0200
Source: neutron
Architecture: source
Version: 2:18.0.0-2
Distribution: experimental
Urgency: medium
Maintainer: Debian OpenStack
Changed-By: Thomas Goirand
Closes: 987196
Changes:
neutron (2:18.0.0-2) experimental; urgency=medium
.
* neutron-common: do not manage metadata_agent.ini, and let the
neutron-metadata-agent package do it. Thanks to Andreas Beckmann for the
bug report. (Closes: #987196).
Checksums-Sha1:
682a92ef7490a7f2f958b4022597a060770c28e7 4762 neutron_18.0.0-2.dsc
855f6d7a33507da4c82cc90aec415c3472b7ae2d 38352 neutron_18.0.0-2.debian.tar.xz
89f6c67147feeef6ac2fe05e0db73553556ff8fa 19836 neutron_18.0.0-2_amd64.buildinfo
Checksums-Sha256:
73774fd129bdfddd9b9dcdf85f55e14afe66a378ca455cbaebf082aba79fa3f1 4762
neutron_18.0.0-2.dsc
af0ca90db4a2aa320b1b2ea0e2afc2a0548cd095bd076e5f9db847e52b687a14 38352
neutron_18.0.0-2.debian.tar.xz
8887650cb922f77b0dea112b4d9501cf55d0c46adefb6878905f3790f4aa507f 19836
neutron_18.0.0-2_amd64.buildinfo
Files:
2c33cfa3a1421238bc00ac5cd6d55402 4762 net optional neutron_18.0.0-2.dsc
6236e87cfc05a818abdc09babd062413 38352 net optional
neutron_18.0.0-2.debian.tar.xz
5524a90bfe06473e94a77dc1b89ed0cb 19836 net optional
neutron_18.0.0-2_amd64.buildinfo
-BEGIN PGP SIGNATURE-
iQIzBAEBCAAdFiEEoLGp81CJVhMOekJc1BatFaxrQ/4FAmB+sj8ACgkQ1BatFaxr
Q/5jWQ/9Eij87VIu/27kmlVsuNJ0d6uIP1IXZlM9vxeeOF3oi769V29VC+XPTsY5
fP3ZFDiV2vsjQcMMOPwTaKA406jxnTSkW2t1/G6IUJ1GM3z4YIs/ZDQtjeHPp1UJ
4muUZEBIkJ4KrzmJyiV/6nMPQ+FQ8DYbPbxLwn6XezazzdNBDwLqChNuAMvrY3TS
YJ4ECxrRkTJsgAFAcb5TUPTHf2mmyYyF4t7o4g9SeJIAaac99LxlLDiobi7wzrFC
C8bzP0/9w8F2bnSaV4mAzJUzw5WucVpwLeSFaKXPDDt4Z8OFxItq22hPIUOXZC4s
pVo3wsgr3uGylCqBDipfgwJwwpplebRvH6QG9d3mqE8JEUoDI31LrpbOxN1zc6oW
gsLtjs9EaIWXlPHJ5t88B+aF1d/cYpZ8kCBsV4PLcDZcLcCsuOGrLIPpIzaqNNZy
DqY06/XL3J6slT1ES1Tmyj8oK//qxmoRRo+h2E6g0Ll5Sw0ZHYA5L1Gx1mGR7wBK
uBRnkDjRx9Q/tPwB7/1qIav5x2NIX+WICpnoK2SSGHc108nqXU6bdHStKdL2wgp/
TJd/goH7dUB6nysdKKrdR8kv0QG2lXQyWpgdkB7TZQbXUnTO2ejm3WikjqVkfokG
Processed: Re: Bug#982745: nginx-common: don't enable TLSv1 or TLSv1.1 in default configuration)
Processing control commands: > severity -1 grave Bug #982745 [nginx-common] nginx-common: don't enable TLSv1 or TLSv1.1 in default configuration Severity set to 'grave' from 'normal' > notforwarded -1 Bug #982745 [nginx-common] nginx-common: don't enable TLSv1 or TLSv1.1 in default configuration Unset Bug forwarded-to-address -- 982745: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=982745 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#987196: marked as pending in neutron
Control: tag -1 pending Hello, Bug #987196 in neutron reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/openstack-team/services/neutron/-/commit/ffab6d4dbc757543a2b3ddd2589984e729569a5d * neutron-common: do not manage metadata_agent.ini, and let the neutron-metadata-agent package do it. Thanks to Andreas Beckmann for the bug report. (Closes: #987196). (this message was generated automatically) -- Greetings https://bugs.debian.org/987196
Bug#987196: marked as pending in neutron
Control: tag -1 pending Hello, Bug #987196 in neutron reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/openstack-team/services/neutron/-/commit/d28eec6d9d5a5a086e5f0e68b70483e150020cad * neutron-common: do not manage metadata_agent.ini, and let the neutron-metadata-agent package do it. Thanks to Andreas Beckmann for the bug report. (Closes: #987196). (this message was generated automatically) -- Greetings https://bugs.debian.org/987196
Processed: Bug#987196 marked as pending in neutron
Processing control commands: > tag -1 pending Bug #987196 [neutron-common,neutron-metadata-agent] neutron-common,neutron-metadata-agent: both manage /etc/neutron/metadata_agent.ini Ignoring request to alter tags of bug #987196 to the same tags previously set -- 987196: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=987196 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Bug#987196 marked as pending in neutron
Processing control commands: > tag -1 pending Bug #987196 [neutron-common,neutron-metadata-agent] neutron-common,neutron-metadata-agent: both manage /etc/neutron/metadata_agent.ini Ignoring request to alter tags of bug #987196 to the same tags previously set -- 987196: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=987196 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#987196: marked as pending in neutron
Control: tag -1 pending Hello, Bug #987196 in neutron reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/openstack-team/services/neutron/-/commit/c4d0d780fc8773b71e78c0456e37b92c7cad63bb * neutron-common: do not manage metadata_agent.ini, and let the neutron-metadata-agent package do it. Thanks to Andreas Beckmann for the bug report. (Closes: #987196). (this message was generated automatically) -- Greetings https://bugs.debian.org/987196
Processed: Bug#987196 marked as pending in neutron
Processing control commands: > tag -1 pending Bug #987196 [neutron-common,neutron-metadata-agent] neutron-common,neutron-metadata-agent: both manage /etc/neutron/metadata_agent.ini Ignoring request to alter tags of bug #987196 to the same tags previously set -- 987196: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=987196 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Bug#987196 marked as pending in neutron
Processing control commands: > tag -1 pending Bug #987196 [neutron-common,neutron-metadata-agent] neutron-common,neutron-metadata-agent: both manage /etc/neutron/metadata_agent.ini Added tag(s) pending. -- 987196: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=987196 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#987196: marked as pending in neutron
Control: tag -1 pending Hello, Bug #987196 in neutron reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/openstack-team/services/neutron/-/commit/f95724455d3229c915006d63ca9481aed4e1b833 * neutron-common: do not manage metadata_agent.ini, and let the neutron-metadata-agent package do it. Thanks to Andreas Beckmann for the bug report. (Closes: #987196). (this message was generated automatically) -- Greetings https://bugs.debian.org/987196
Bug#987198: marked as done (barbican-api,barbican-common: both manage /etc/barbican/vassals/barbican-api.ini)
Your message dated Tue, 20 Apr 2021 10:33:28 + with message-id and subject line Bug#987198: fixed in barbican 1:12.0.0-2 has caused the Debian Bug report #987198, regarding barbican-api,barbican-common: both manage /etc/barbican/vassals/barbican-api.ini 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.) -- 987198: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=987198 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: barbican-api,barbican-common Version: 1:11.0.0-2 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed purging barbican-api removes files that were installed by another package. The removed files were already present before the package was installed, they may have been shipped or created by a dependency. >From the attached log (scroll to the bottom...): 1m21.4s ERROR: FAIL: After purging files have disappeared: /etc/barbican/vassals/ owned by: barbican-api /etc/barbican/vassals/barbican-api.ini owned by: barbican-api barbican-api ships it as a conffile, while barbican-common manages it with the maintainer scripts: /var/lib/dpkg/info/barbican-api.conffiles:/etc/barbican/vassals/barbican-api.ini /var/lib/dpkg/info/barbican-api.list:/etc/barbican/vassals/barbican-api.ini /var/lib/dpkg/info/barbican-common.md5sums:65c93e1360c99387fadbec36c7cba67c usr/share/barbican-common/vassals/barbican-api.ini /var/lib/dpkg/info/barbican-common.postinst:pkgos_write_new_conf barbican vassals/barbican-api.ini /var/lib/dpkg/info/barbican-common.postrm: for i in barbican.conf vassals/barbican-admin.ini vassals/barbican-api.ini barbican-admin-paste.ini barbican-api.conf barbican-api-paste.ini barbican-functional.conf policy.json api_audit_map.conf ; do /var/lib/dpkg/info/barbican-common.list:/usr/share/barbican-common/vassals/barbican-api.ini cheers, Andreas barbican-api_1:11.0.0-2.log.gz Description: application/gzip --- End Message --- --- Begin Message --- Source: barbican Source-Version: 1:12.0.0-2 Done: Thomas Goirand We believe that the bug you reported is fixed in the latest version of barbican, 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 987...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Thomas Goirand (supplier of updated barbican 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, 20 Apr 2021 11:53:16 +0200 Source: barbican Architecture: source Version: 1:12.0.0-2 Distribution: experimental Urgency: medium Maintainer: Debian OpenStack Changed-By: Thomas Goirand Closes: 987198 Changes: barbican (1:12.0.0-2) experimental; urgency=medium . * Do not manage stuff in /etc/barbican/vassals (Closes: #987198). Checksums-Sha1: 47caa34960c01f2eaf58145c578be4ca0810b5c9 3602 barbican_12.0.0-2.dsc acc02a532e0dbb4f04ee80f00bf05ca9839f0936 9672 barbican_12.0.0-2.debian.tar.xz 50b1bdb473f205c566351a6d876108d451a4f7a8 20577 barbican_12.0.0-2_amd64.buildinfo Checksums-Sha256: a7bdb88924cf32b560426f609f07592a8f827820eaa4577c190ef020eeb07693 3602 barbican_12.0.0-2.dsc 2553ad5aa81abbbc0e2da5e4af347c7c89fba3ffc980d29f958ba1b3292fd0b9 9672 barbican_12.0.0-2.debian.tar.xz e9262651d34be65adc0e44ec4971b79242b5ee8ea25e027fe4249ad313550df5 20577 barbican_12.0.0-2_amd64.buildinfo Files: 1771ea97bead2c9a8d17ae9f8c1a256a 3602 net optional barbican_12.0.0-2.dsc e1197c2c6633f3bde439ca5b368d5f88 9672 net optional barbican_12.0.0-2.debian.tar.xz 98953f68c9cde5ea108c00ef2a8b57c8 20577 net optional barbican_12.0.0-2_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEoLGp81CJVhMOekJc1BatFaxrQ/4FAmB+p6IACgkQ1BatFaxr Q/6JrA//SiuthptsA7stPg7vOzipabwQEijf5yZYn4haIlOzukRH9G22TeqH/SW/ Wd2bFjAPzdFsOBlZuWDWWF7OfRRqJzGbfl8gYdPxqfDhnp7LmtEFVCZgXXvHGyUE +Pm4kiNzuCqUhvRoQ1+NTk/3D1F1HlFLfj3Wa1MT+19J4gthBlYurslOCccORPbD Kzhl2AVpo/f6XH23aieR8KV0cqX2F0x5n6zlW/pB88YA2cygFTisrg0gB6DhlXrn N157+2i3GJAd+xBVKMdQ0AK1/T/P377aiPt2RM3CNgGrK/vLztGLHmVOe/si3ZOT i2CllESDYOgtB0VCM/BWYOl5OgquSCLWKVlALp4D4dmFEeW/WepUxOXFv16OW5m4 kJjLI8qTW28uqUJgTYxwx5NWFJJKjCzwG5RveY2GAawOLFD8TNYUkhD6g8icRMhi
Bug#987198: marked as done (barbican-api,barbican-common: both manage /etc/barbican/vassals/barbican-api.ini)
Your message dated Tue, 20 Apr 2021 10:18:23 + with message-id and subject line Bug#987198: fixed in barbican 1:11.0.0-3 has caused the Debian Bug report #987198, regarding barbican-api,barbican-common: both manage /etc/barbican/vassals/barbican-api.ini 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.) -- 987198: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=987198 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: barbican-api,barbican-common Version: 1:11.0.0-2 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed purging barbican-api removes files that were installed by another package. The removed files were already present before the package was installed, they may have been shipped or created by a dependency. >From the attached log (scroll to the bottom...): 1m21.4s ERROR: FAIL: After purging files have disappeared: /etc/barbican/vassals/ owned by: barbican-api /etc/barbican/vassals/barbican-api.ini owned by: barbican-api barbican-api ships it as a conffile, while barbican-common manages it with the maintainer scripts: /var/lib/dpkg/info/barbican-api.conffiles:/etc/barbican/vassals/barbican-api.ini /var/lib/dpkg/info/barbican-api.list:/etc/barbican/vassals/barbican-api.ini /var/lib/dpkg/info/barbican-common.md5sums:65c93e1360c99387fadbec36c7cba67c usr/share/barbican-common/vassals/barbican-api.ini /var/lib/dpkg/info/barbican-common.postinst:pkgos_write_new_conf barbican vassals/barbican-api.ini /var/lib/dpkg/info/barbican-common.postrm: for i in barbican.conf vassals/barbican-admin.ini vassals/barbican-api.ini barbican-admin-paste.ini barbican-api.conf barbican-api-paste.ini barbican-functional.conf policy.json api_audit_map.conf ; do /var/lib/dpkg/info/barbican-common.list:/usr/share/barbican-common/vassals/barbican-api.ini cheers, Andreas barbican-api_1:11.0.0-2.log.gz Description: application/gzip --- End Message --- --- Begin Message --- Source: barbican Source-Version: 1:11.0.0-3 Done: Thomas Goirand We believe that the bug you reported is fixed in the latest version of barbican, 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 987...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Thomas Goirand (supplier of updated barbican 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, 20 Apr 2021 11:59:15 +0200 Source: barbican Architecture: source Version: 1:11.0.0-3 Distribution: unstable Urgency: medium Maintainer: Debian OpenStack Changed-By: Thomas Goirand Closes: 987198 Changes: barbican (1:11.0.0-3) unstable; urgency=medium . * Tune barbican-api-uwsgi.ini for performance. * Do not manage stuff in /etc/barbican/vassals (Closes: #987198). Checksums-Sha1: afaedbe9c0a65260d3c477ced347984411bf5718 3638 barbican_11.0.0-3.dsc 6b76bb95c6a7a4bc5a2db5d8991e5e82e6a7bf55 10484 barbican_11.0.0-3.debian.tar.xz 6982e3734b74af8b6b00adbc283f4e1d8b986e65 20928 barbican_11.0.0-3_amd64.buildinfo Checksums-Sha256: c2e7d7d3bc63ad64bfcce12fb14fd77783742792e6d956a0e461f4e8491a1410 3638 barbican_11.0.0-3.dsc b71bf94534139b9f98d160b7057edf2ff6262eb2386e5569d487ae7c67bd9718 10484 barbican_11.0.0-3.debian.tar.xz 862c95ceb20b504225c49137dd8ed0aee29711f77e09a51ebd25a6238c117af2 20928 barbican_11.0.0-3_amd64.buildinfo Files: a965190fe42cc0e4b08167d2737a130f 3638 net optional barbican_11.0.0-3.dsc f4ece79588fe473686102f6bf419d836 10484 net optional barbican_11.0.0-3.debian.tar.xz 1bac8953c641e9ead835e98cdd2909f0 20928 net optional barbican_11.0.0-3_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEoLGp81CJVhMOekJc1BatFaxrQ/4FAmB+puQACgkQ1BatFaxr Q/71zA/7Bh1zKBsgL4gKNUxpuoYN6wtIAbkxRtneD5CwMgjW8WbjokQnArP4rSgI U2SmQ9oFHeWRDVuB9MS6/gGpB58WFCbSui9UKalLFll6hiLWUg3C1M1zTRGYhpfu OSMmdLSysrr148ciWRRUgfri8ecAJiKlIDSRV/knvwzCnpve2QgBuG4mWp4rjCzf 48ciLnaHXsE83VW4b3xe9VlWn3+IRol6sKoNkcJ3jgudjnbWCzhF8ezKbi0iNGjP WXEhRxFsA7XWbi5nqantrMnmRNoQDrKT5TRbSo1kb1goFyHDizcHQPVceQrsOwtp re30eWHimzYhJmBlzquMraOFmlXJLvePMBEJg7dy11hrC28voHKC6lpmYFsX7nhB
Processed: Bug#987198 marked as pending in barbican
Processing control commands: > tag -1 pending Bug #987198 [barbican-api,barbican-common] barbican-api,barbican-common: both manage /etc/barbican/vassals/barbican-api.ini Ignoring request to alter tags of bug #987198 to the same tags previously set -- 987198: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=987198 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#987198: marked as pending in barbican
Control: tag -1 pending Hello, Bug #987198 in barbican reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/openstack-team/services/barbican/-/commit/96ee288f3252df47237729e28da0df279f352e24 Do not manage stuff in /etc/barbican/vassals (Closes: #987198). (this message was generated automatically) -- Greetings https://bugs.debian.org/987198
Processed: Bug#987198 marked as pending in barbican
Processing control commands: > tag -1 pending Bug #987198 [barbican-api,barbican-common] barbican-api,barbican-common: both manage /etc/barbican/vassals/barbican-api.ini Ignoring request to alter tags of bug #987198 to the same tags previously set -- 987198: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=987198 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#987198: marked as pending in barbican
Control: tag -1 pending Hello, Bug #987198 in barbican reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/openstack-team/services/barbican/-/commit/57f430805c441e5e656339453c7286f477b2d7b9 Do not manage stuff in /etc/barbican/vassals (Closes: #987198). (this message was generated automatically) -- Greetings https://bugs.debian.org/987198
Bug#987198: marked as pending in barbican
Control: tag -1 pending Hello, Bug #987198 in barbican reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/openstack-team/services/barbican/-/commit/39ec418e0a1e89e015d20a5652a9bded7afdded1 Do not manage stuff in /etc/barbican/vassals (Closes: #987198). (this message was generated automatically) -- Greetings https://bugs.debian.org/987198
Processed: Bug#987198 marked as pending in barbican
Processing control commands: > tag -1 pending Bug #987198 [barbican-api,barbican-common] barbican-api,barbican-common: both manage /etc/barbican/vassals/barbican-api.ini Ignoring request to alter tags of bug #987198 to the same tags previously set -- 987198: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=987198 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#987198: marked as pending in barbican
Control: tag -1 pending Hello, Bug #987198 in barbican reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/openstack-team/services/barbican/-/commit/a8dd25fc4bb71479e76193c37e5baafd53bc98c3 Do not manage stuff in /etc/barbican/vassals (Closes: #987198). (this message was generated automatically) -- Greetings https://bugs.debian.org/987198
Processed: Bug#987198 marked as pending in barbican
Processing control commands: > tag -1 pending Bug #987198 [barbican-api,barbican-common] barbican-api,barbican-common: both manage /etc/barbican/vassals/barbican-api.ini Ignoring request to alter tags of bug #987198 to the same tags previously set -- 987198: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=987198 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#987198: marked as pending in barbican
Control: tag -1 pending Hello, Bug #987198 in barbican reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/openstack-team/services/barbican/-/commit/2fca6e35dbc92847ae526b2ce025ac7772411d0b Do not manage stuff in /etc/barbican/vassals (Closes: #987198). (this message was generated automatically) -- Greetings https://bugs.debian.org/987198
Processed: Bug#987198 marked as pending in barbican
Processing control commands: > tag -1 pending Bug #987198 [barbican-api,barbican-common] barbican-api,barbican-common: both manage /etc/barbican/vassals/barbican-api.ini Ignoring request to alter tags of bug #987198 to the same tags previously set -- 987198: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=987198 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#987194: marked as done (puppet-module-ceilometer: removes puppet-module-openstacklib alternative on package removal)
Your message dated Tue, 20 Apr 2021 10:03:44 +
with message-id
and subject line Bug#987194: fixed in puppet-module-ceilometer 18.4.0-2
has caused the Debian Bug report #987194,
regarding puppet-module-ceilometer: removes puppet-module-openstacklib
alternative on package removal
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.)
--
987194: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=987194
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: puppet-module-ceilometer
Version: 17.4.0-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package removes files that
were installed by another package.
The removed files were already present before the package was installed,
they may have been shipped or created by a dependency.
>From the attached log (scroll to the bottom...):
0m58.6s ERROR: FAIL: After purging files have disappeared:
/etc/alternatives/puppet-module-openstacklib ->
/usr/share/puppet/modules.available/openstacklib not owned
/usr/share/puppet/modules/openstacklib ->
/etc/alternatives/puppet-module-openstacklib not owned
prerm has
if [ "${1}" = "remove" ] || [ "${1}" = "upgrade" ] || [ "${1}" = "deconfigure"
] ; then
update-alternatives --remove puppet-module-openstacklib
/usr/share/puppet/modules.available/openstacklib
fi
while postinst/postrm only handle puppet-module-ceilometer
cheers,
Andreas
puppet-module-ceilometer_17.4.0-2.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: puppet-module-ceilometer
Source-Version: 18.4.0-2
Done: Thomas Goirand
We believe that the bug you reported is fixed in the latest version of
puppet-module-ceilometer, 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 987...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Thomas Goirand (supplier of updated puppet-module-ceilometer
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, 20 Apr 2021 11:39:43 +0200
Source: puppet-module-ceilometer
Architecture: source
Version: 18.4.0-2
Distribution: experimental
Urgency: medium
Maintainer: Debian OpenStack
Changed-By: Thomas Goirand
Closes: 987194
Changes:
puppet-module-ceilometer (18.4.0-2) experimental; urgency=medium
.
* Fix prerm to remove the correct ceilometer puppet module alternative,
and not the one of openstacklib. Thanks to Andreas Beckmann for the bug
report (Closes: #987194).
Checksums-Sha1:
6376e4f79e92a9a030b7a86ff6085927c6bd05fd 2176
puppet-module-ceilometer_18.4.0-2.dsc
f0b1ac64596c1920ace11485609f5627dd0c52d0 3196
puppet-module-ceilometer_18.4.0-2.debian.tar.xz
afffb5aac88047939ac4289fec63ce5af885dcf2 6811
puppet-module-ceilometer_18.4.0-2_amd64.buildinfo
Checksums-Sha256:
ba3130a189ddf30da8c7e0b4244ce916ed6df99aba3f10b94017ede8739b2cc8 2176
puppet-module-ceilometer_18.4.0-2.dsc
911873a2b17ecee83dcc6fb56169f007a951bdb4df70e8699682f15b22193bba 3196
puppet-module-ceilometer_18.4.0-2.debian.tar.xz
a885ea3bd661cdbb3c06bf4121cfccce3607f3da85b57e438abfd6fa1ea5ef2a 6811
puppet-module-ceilometer_18.4.0-2_amd64.buildinfo
Files:
e2fbe40ab8c13219d739551e60340a9a 2176 admin optional
puppet-module-ceilometer_18.4.0-2.dsc
28e209180fd8ea9ec4b46dad78214cb7 3196 admin optional
puppet-module-ceilometer_18.4.0-2.debian.tar.xz
7cf876145d95af23ac62335f2eeba1df 6811 admin optional
puppet-module-ceilometer_18.4.0-2_amd64.buildinfo
-BEGIN PGP SIGNATURE-
iQIzBAEBCAAdFiEEoLGp81CJVhMOekJc1BatFaxrQ/4FAmB+ogUACgkQ1BatFaxr
Q/65Eg//YegMjFODjY2WQeRQScIq9TNaPFLjboELI99r0ErGq0Dx01OEUxMabjKb
ggNbu86/7woUJfT6gdpkXff/dtFEVDgygA5n6e8sxwbEVwzHilQzpHic5uQLJVkr
mgc3sUXzUjQHvS1sci/kGZYgjKXJqWPrr+EOmt+czNoY6RpvMKuUXfbvigiu0jNa
xqwIuYzJWKyqw1vzcX3HHhFi9yl//W17QAnzlM1HcqidbewI//AGFsM783O9r9+k
AXAZyDGg3OuobRLtv6FMsIO7gCo6G3DmYMPt4Ytxq0OQgVoGYEb6FwgiRVwhgLRa
w2U23PkftyJT/FvkYbjObQz//SLmMxLs/JEejvFPPojOBAz7/G6H9YRrQQRMNEqH
ZxurkXmRHXPaDPyLfCHmuJzAt5wVl1AfZd0cZNxoRR1Cy5cOg+bRiKgUp3Uv4BjK
4D1QAINzsnijl9nGfUZzABxPRXow3Cb8jNC5PAgv9d7vUIXhUH4ZiaehrScy1YvS
Bug#987194: marked as done (puppet-module-ceilometer: removes puppet-module-openstacklib alternative on package removal)
Your message dated Tue, 20 Apr 2021 10:03:38 +
with message-id
and subject line Bug#987194: fixed in puppet-module-ceilometer 17.4.0-3
has caused the Debian Bug report #987194,
regarding puppet-module-ceilometer: removes puppet-module-openstacklib
alternative on package removal
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.)
--
987194: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=987194
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: puppet-module-ceilometer
Version: 17.4.0-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package removes files that
were installed by another package.
The removed files were already present before the package was installed,
they may have been shipped or created by a dependency.
>From the attached log (scroll to the bottom...):
0m58.6s ERROR: FAIL: After purging files have disappeared:
/etc/alternatives/puppet-module-openstacklib ->
/usr/share/puppet/modules.available/openstacklib not owned
/usr/share/puppet/modules/openstacklib ->
/etc/alternatives/puppet-module-openstacklib not owned
prerm has
if [ "${1}" = "remove" ] || [ "${1}" = "upgrade" ] || [ "${1}" = "deconfigure"
] ; then
update-alternatives --remove puppet-module-openstacklib
/usr/share/puppet/modules.available/openstacklib
fi
while postinst/postrm only handle puppet-module-ceilometer
cheers,
Andreas
puppet-module-ceilometer_17.4.0-2.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: puppet-module-ceilometer
Source-Version: 17.4.0-3
Done: Thomas Goirand
We believe that the bug you reported is fixed in the latest version of
puppet-module-ceilometer, 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 987...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Thomas Goirand (supplier of updated puppet-module-ceilometer
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, 20 Apr 2021 11:43:26 +0200
Source: puppet-module-ceilometer
Architecture: source
Version: 17.4.0-3
Distribution: unstable
Urgency: medium
Maintainer: Debian OpenStack
Changed-By: Thomas Goirand
Closes: 987194
Changes:
puppet-module-ceilometer (17.4.0-3) unstable; urgency=medium
.
* Fix prerm to remove the correct ceilometer puppet module alternative,
and not the one of openstacklib. Thanks to Andreas Beckmann for the bug
report (Closes: #987194).
Checksums-Sha1:
28c0aa38295e628f8553c07ad3e1db9bbf8bf5f3 2185
puppet-module-ceilometer_17.4.0-3.dsc
5afc91ad830695068a55576bad62221ad8554cc6 3168
puppet-module-ceilometer_17.4.0-3.debian.tar.xz
649c3d95f6de8293e13b53ea3d8c65ce81b553f9 6691
puppet-module-ceilometer_17.4.0-3_amd64.buildinfo
Checksums-Sha256:
1272f934b4968feb03a7902f4df6b210152fd6510501bc707cbd50bbd0a9fe13 2185
puppet-module-ceilometer_17.4.0-3.dsc
c260083d07a3dbb9e4e5d19bb55f623331276282e0942ccc1cd4cbec81f2c753 3168
puppet-module-ceilometer_17.4.0-3.debian.tar.xz
d11a66db59d99c2afe3d04c0001fe56d679fa81812579f13d6d4bf5b02ec6511 6691
puppet-module-ceilometer_17.4.0-3_amd64.buildinfo
Files:
8d320a9cfb1296f59b5ebb49eac93da8 2185 admin optional
puppet-module-ceilometer_17.4.0-3.dsc
c8a82f9338ab31f2e8226b29be658571 3168 admin optional
puppet-module-ceilometer_17.4.0-3.debian.tar.xz
ad15e2b292637e59f6288539a41836fb 6691 admin optional
puppet-module-ceilometer_17.4.0-3_amd64.buildinfo
-BEGIN PGP SIGNATURE-
iQIzBAEBCAAdFiEEoLGp81CJVhMOekJc1BatFaxrQ/4FAmB+oqwACgkQ1BatFaxr
Q/7s5g/+JasFb+asEjt2ich+NR2/69j+XXyXfQ8EaUt9IJ2qLF4C9B2xwbGGkTaA
TLXUPszA9rD+XNGWLX7SIv+kyT+CVEQyuW06fRHfyPV1qsfkSYffspJ6MNJlHCUn
RDXuMkOPVzUT65Eh8Rz17zVQQoXp2vPNXFzYK6yJRTGx+OUU8J2325IFjwJmbWMe
GGyEai47bhfYvO8icBNkGszSRtFWkVWnnlV38xmlTz5N8gS3nUjIfms1Mmlt2Ida
AP/hUB9gJixJiw98cXY1xTIx8kAXWElOGFoipl4yCnY9H9uvl+yCO2iAZ9AcMuvG
F/D55R/04yGQLPgj06EJ9kW1ZdS+KiAgl8EBB5aO/GZTzR/eUoiBm4BazsdGNP2D
wE9w3pEJkkbC9e5zAHqxt4NFOzjRbtTp8XrRK7gNycxLpgUKgXUgWgHsFN6LzUFn
7hQjHq4nNsYcOFwhqp2aGv58WBV812e7mGHM/A5f62+r8fIpA62NkNTbuybbKjcF
Bug#987198: marked as pending in barbican
Control: tag -1 pending Hello, Bug #987198 in barbican reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/openstack-team/services/barbican/-/commit/92dba330d257367abeec0985dfa2532a13afa182 Do not manage stuff in /etc/barbican/vassals (Closes: #987198). (this message was generated automatically) -- Greetings https://bugs.debian.org/987198
Processed: Bug#987198 marked as pending in barbican
Processing control commands: > tag -1 pending Bug #987198 [barbican-api,barbican-common] barbican-api,barbican-common: both manage /etc/barbican/vassals/barbican-api.ini Added tag(s) pending. -- 987198: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=987198 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#960867: From Dr Tracy from United States
-- Hello Dear, It is my great pleasure to contact you My name is Tracy William from the United States, Am an English and French nationalities. I will give you pictures and more details about my self as soon as i hear from you Tracy
Processed: Bug#987194 marked as pending in puppet-module-ceilometer
Processing control commands: > tag -1 pending Bug #987194 [puppet-module-ceilometer] puppet-module-ceilometer: removes puppet-module-openstacklib alternative on package removal Ignoring request to alter tags of bug #987194 to the same tags previously set -- 987194: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=987194 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#987194: marked as pending in puppet-module-ceilometer
Control: tag -1 pending Hello, Bug #987194 in puppet-module-ceilometer reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/openstack-team/puppet/puppet-module-ceilometer/-/commit/80d5e3806682beb223f1f017026c5de5e868ce0f * Fix prerm to remove the correct ceilometer puppet module alternative, and not the one of openstacklib. Thanks to Andreas Beckmann for the bug report (Closes: #987194). (this message was generated automatically) -- Greetings https://bugs.debian.org/987194
Bug#987193: marked as done (glance-common: purging deletes /etc/glance/rootwrap.conf owned by glance-store-common)
Your message dated Tue, 20 Apr 2021 09:48:41 +
with message-id
and subject line Bug#987193: fixed in glance 2:21.0.0-2
has caused the Debian Bug report #987193,
regarding glance-common: purging deletes /etc/glance/rootwrap.conf owned by
glance-store-common
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.)
--
987193: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=987193
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: glance-common
Version: 2:21.0.0-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package removes files that
were installed by another package.
>From the attached log (scroll to the bottom...):
2m9.3s ERROR: FAIL: debsums reports modifications inside the chroot:
debsums: missing file /etc/glance/rootwrap.conf (from glance-store-common
package)
postrm has
for i in [...] \
[...] rootwrap.conf [...] ; do
if [ -e "/etc/glance/${i}" ] ; then
rm /etc/glance/${i}
fi
done
cheers,
Andreas
glance-common_2:21.0.0-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: glance
Source-Version: 2:21.0.0-2
Done: Thomas Goirand
We believe that the bug you reported is fixed in the latest version of
glance, 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 987...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Thomas Goirand (supplier of updated glance 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, 15 Dec 2020 11:41:16 +0100
Source: glance
Architecture: source
Version: 2:21.0.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian OpenStack
Changed-By: Thomas Goirand
Closes: 987193
Changes:
glance (2:21.0.0-2) unstable; urgency=medium
.
* Add variables: DEB_BUILD_OPTIONS: nocheck DEB_BUILD_PROFILES: nocheck in
debian/salsa-ci.yml.
* Do not delete /etc/glance/rootwrap.conf, owned by python3-glance-store.
(Closes: #987193).
* mv /etc/glance/policy.json /etc/glance/disabled.policy.json.old instead of
deleting /etc/glance/policy.json.
* Tune glance-api-uwsgi.ini for performance.
Checksums-Sha1:
b134c2ff707b0f4ba541cba3353a1da2410b94a5 3736 glance_21.0.0-2.dsc
cd375c31d85e518ce146fddc457424c1ce119fd9 16500 glance_21.0.0-2.debian.tar.xz
e85254f3f02c285d713967b64315a48fabd5e44b 17286 glance_21.0.0-2_amd64.buildinfo
Checksums-Sha256:
2e148ec48e8edba33a9fe059ff02184251b3f1a5f65181d2f8a40ae80097d72e 3736
glance_21.0.0-2.dsc
2a47548bbc6879f8b1fa5dd78e884674fc2a4906309cf8d0098e5aad78629b69 16500
glance_21.0.0-2.debian.tar.xz
e035eb1a6359353b2ee98a5b999dc0fc33d36e169f4d108985ff5520b43d03ad 17286
glance_21.0.0-2_amd64.buildinfo
Files:
6015e3c08b13fe91ceeca5f58ff3d519 3736 net optional glance_21.0.0-2.dsc
a600daf02fc56d992185f430f22392fb 16500 net optional
glance_21.0.0-2.debian.tar.xz
492abf02e8c9cb951e533fa314b45993 17286 net optional
glance_21.0.0-2_amd64.buildinfo
-BEGIN PGP SIGNATURE-
iQIzBAEBCAAdFiEEoLGp81CJVhMOekJc1BatFaxrQ/4FAmB+n0UACgkQ1BatFaxr
Q/4vGg//RV8GOBOZcJWYqGzpMyfoQf/VlDhsbJUs/chPNYIyhRGS2u+vDXCTgKTY
KwHsHYwzCuyMsO+P6das2vRxh34fLnXyim7i4CKtN3UOu0xtr+uj2o4UrZhutfbJ
KvPkj3ilMgiLoOqHl5gzPv3POwlvEaflYSs8DK4/Pn4AakVIqrXME7Eh2JalBD+C
pHCm/MUZi0X3TLQBBPquT9rvNL/lam/VHsYXGQLB3/qVecGDzhgDXcDN6gfPDUD7
pC+FtH8M7Evi3TSHzGYoZ9F8pSRcv86qFcHBJB4unku9Mrz5s9HRvynzTxqO+xdL
uvv1md1E3vzWJ4F/NVfrYmZU7cwZUoPZcgmFjPliJLbuw00HEtrBHo5cW+Zd6j8v
OOoIUWyPqK04Yd/8CiH4+sRAdsi2tKeiZMTpYxQ/69pwudlasWxdijsUl7xgAUuK
gaYqOfxYzGi5O2ZghgmwtO8u2uLPfE2byjBgLT7K6r/J7m205e9BvAT7OaRm+eqJ
JSU+Ksq6catCf0P8rRpmaZ22k4uPCQkJWVlNflv8o/8G+cr99PMrN7lvjyLdvHis
7kcbh91qEyQx73aTo0ppbT9UfK6+QxCSrPqwEBhn8UkVOi8XGjfcGCcIG65ap2/d
R2SRs3qvx7ltzGx8CWjnGysIRB+PJBLTS7BZbHvP3n8CtdEbxHc=
=QHFw
-END PGP SIGNATURE End Message ---
Bug#987194: marked as pending in puppet-module-ceilometer
Control: tag -1 pending Hello, Bug #987194 in puppet-module-ceilometer reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/openstack-team/puppet/puppet-module-ceilometer/-/commit/48220e8405f2a3a2e45d32c4da717d78f2920808 * Fix prerm to remove the correct ceilometer puppet module alternative, and not the one of openstacklib. Thanks to Andreas Beckmann for the bug report (Closes: #987194). (this message was generated automatically) -- Greetings https://bugs.debian.org/987194
Bug#987194: marked as pending in puppet-module-ceilometer
Control: tag -1 pending Hello, Bug #987194 in puppet-module-ceilometer reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/openstack-team/puppet/puppet-module-ceilometer/-/commit/14d83517118c62c73d8054c3987d5b59d17c82e2 * Fix prerm to remove the correct ceilometer puppet module alternative, and not the one of openstacklib. Thanks to Andreas Beckmann for the bug report (Closes: #987194). (this message was generated automatically) -- Greetings https://bugs.debian.org/987194
Bug#987194: marked as pending in puppet-module-ceilometer
Control: tag -1 pending Hello, Bug #987194 in puppet-module-ceilometer reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/openstack-team/puppet/puppet-module-ceilometer/-/commit/5c8edf6625ca5a3b42b5f25d0092bc3a3bc701a3 * Fix prerm to remove the correct ceilometer puppet module alternative, and not the one of openstacklib. Thanks to Andreas Beckmann for the bug report (Closes: #987194). (this message was generated automatically) -- Greetings https://bugs.debian.org/987194
Processed: Bug#987194 marked as pending in puppet-module-ceilometer
Processing control commands: > tag -1 pending Bug #987194 [puppet-module-ceilometer] puppet-module-ceilometer: removes puppet-module-openstacklib alternative on package removal Ignoring request to alter tags of bug #987194 to the same tags previously set -- 987194: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=987194 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Bug#987194 marked as pending in puppet-module-ceilometer
Processing control commands: > tag -1 pending Bug #987194 [puppet-module-ceilometer] puppet-module-ceilometer: removes puppet-module-openstacklib alternative on package removal Ignoring request to alter tags of bug #987194 to the same tags previously set -- 987194: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=987194 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Bug#987194 marked as pending in puppet-module-ceilometer
Processing control commands: > tag -1 pending Bug #987194 [puppet-module-ceilometer] puppet-module-ceilometer: removes puppet-module-openstacklib alternative on package removal Ignoring request to alter tags of bug #987194 to the same tags previously set -- 987194: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=987194 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#987194: marked as pending in puppet-module-ceilometer
Control: tag -1 pending Hello, Bug #987194 in puppet-module-ceilometer reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/openstack-team/puppet/puppet-module-ceilometer/-/commit/d9186f2fbbfd15f96900b4eb946cde1ecfe04f93 * Fix prerm to remove the correct ceilometer puppet module alternative, and not the one of openstacklib. Thanks to Andreas Beckmann for the bug report (Closes: #987194). (this message was generated automatically) -- Greetings https://bugs.debian.org/987194
Processed: Bug#987194 marked as pending in puppet-module-ceilometer
Processing control commands: > tag -1 pending Bug #987194 [puppet-module-ceilometer] puppet-module-ceilometer: removes puppet-module-openstacklib alternative on package removal Ignoring request to alter tags of bug #987194 to the same tags previously set -- 987194: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=987194 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Bug#987194 marked as pending in puppet-module-ceilometer
Processing control commands: > tag -1 pending Bug #987194 [puppet-module-ceilometer] puppet-module-ceilometer: removes puppet-module-openstacklib alternative on package removal Added tag(s) pending. -- 987194: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=987194 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#987194: marked as pending in puppet-module-ceilometer
Control: tag -1 pending Hello, Bug #987194 in puppet-module-ceilometer reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/openstack-team/puppet/puppet-module-ceilometer/-/commit/74a544e40911ef1b11a1b1f18c4fa25bd4204a1d * Fix prerm to remove the correct ceilometer puppet module alternative, and not the one of openstacklib. Thanks to Andreas Beckmann for the bug report (Closes: #987194). (this message was generated automatically) -- Greetings https://bugs.debian.org/987194
