Bug#989776: marked as done (auto-apt-proxy: autopkgtest regression since June 2021)
Your message dated Sat, 19 Jun 2021 02:18:11 + with message-id and subject line Bug#989776: fixed in auto-apt-proxy 13.3 has caused the Debian Bug report #989776, regarding auto-apt-proxy: autopkgtest regression since June 2021 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.) -- 989776: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=989776 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: auto-apt-proxy Version: 13.2 Severity: serious Tags: bullseye-ignore User: debian...@lists.debian.org Usertags: regression X-Debbugs-CC: debian...@lists.debian.org Dear Antonio, Your package has an autopkgtest, great! However, since somewhere in May or June it started to fail [1]. Looking at the error, I have no clue why. Can you fix the situation? By the way, please mark tests that need internet access with the needs-internet restriction. Paul [Release team member hat on: as we are so late in the freeze, I don't want this bug to kick this package out of bullseye, although I still appreciate a fix or work around. Hence, the bullseye-ignore tag.] [1] https://ci.debian.net/packages/a/auto-apt-proxy/ https://ci.debian.net/data/autopkgtest/testing/amd64/a/auto-apt-proxy/12906396/log.gz utopkgtest [07:00:28]: test apt-integration: [--- Reading package lists... NOTICE: 'auto-apt-proxy' packaging is maintained in the 'Git' version control system at: https://salsa.debian.org/debian/auto-apt-proxy.git Please use: git clone https://salsa.debian.org/debian/auto-apt-proxy.git to retrieve the latest (possibly unreleased) updates to the package. Need to get 19.8 kB of source archives. Get:1 http://deb.debian.org/debian testing/main auto-apt-proxy 13.2 (dsc) [1751 B] Get:2 http://deb.debian.org/debian testing/main auto-apt-proxy 13.2 (tar) [18.1 kB] dpkg-source: info: extracting auto-apt-proxy in auto-apt-proxy-13.2 dpkg-source: info: unpacking auto-apt-proxy_13.2.tar.xz Fetched 19.8 kB in 0s (333 kB/s) autopkgtest [07:00:28]: test apt-integration: ---] autopkgtest [07:00:28]: test apt-integration: - - - - - - - - - - results - - - - - - - - - - apt-integration FAIL non-zero exit status 1 autopkgtest [07:00:31]: test apt-cacher-ng: [--- #1 auto-apt-proxy -- [FAILED #1, line 1] auto-apt-proxy @@ -1 +0,0 @@ -http://127.0.0.1:3142 -- FAIL: 1 of 1 test failed autopkgtest [07:00:32]: test apt-cacher-ng: ---] OpenPGP_signature Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Source: auto-apt-proxy Source-Version: 13.3 Done: Antonio Terceiro We believe that the bug you reported is fixed in the latest version of auto-apt-proxy, 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 989...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Antonio Terceiro (supplier of updated auto-apt-proxy 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: Fri, 18 Jun 2021 22:51:34 -0300 Source: auto-apt-proxy Architecture: source Version: 13.3 Distribution: unstable Urgency: medium Maintainer: Antonio Terceiro Changed-By: Antonio Terceiro Closes: 989776 Changes: auto-apt-proxy (13.3) unstable; urgency=medium . * autopkgtest: cope with auto-apt-proxy being pre-installed (Closes: #989776) Checksums-Sha1: 3b6c6b2253c03aef99b5ff1371e87ed908be9a60 1751 auto-apt-proxy_13.3.dsc dd8135c75a367475f6bceafa1824160dc0b1c5b0 18168 auto-apt-proxy_13.3.tar.xz adc2514c9f5887de8c863fa804668ea75142bae4 5805 auto-apt-proxy_13.3_amd64.buildinfo Checksums-Sha256: 0738bf92bf5ff08d51bf11d9d654e17871a2f577162b70cd3f9edc4b4c5ecdaf 1751 auto-apt-proxy_13.3.dsc ec4f4edd626648a4cdc4c0eec9395dcf642d4f545612e1628aaa43269d57555b 18168 auto-apt-proxy_13.3.tar.xz e207aed2d3d440b66eb6cc7a9d7be7c06b71518faf97f9619d6f9b9783f94b3b 5805 auto-apt-proxy_13.3_amd64.buildinfo Files: 20e0c7295ed4400f4491cffed83d33a4 1751 net optional auto-apt-proxy_13.3.dsc bee930ecb246a4dc3e41b291ee5d6280 18168 net optional auto-apt-proxy_13.3.tar.xz
Bug#989491: libxstream-java: CVE-2021-29505
On Sat, 05 Jun 2021 09:29:20 +0200 Salvatore Bonaccorso wrote: > Source: libxstream-java > Version: 1.4.15-2 Let's check it with buster version, then. Here's a patch for it, it lacks some blacklist items from current unstable version but it should be so if sticks to a minimum. Anyway, could you review it, please libstream-java.debdiff Description: Binary data
Bug#990058: libnss3: increase symbol version for SSL_GetChannelInfo when SSLChannelInfo size changes
Package: libnss3 Version: 2:3.67-1 Severity: serious Tags: patch Justification: Policy 8.6.3.3 X-Debbugs-Cc: Sebastian Ramacher , Carsten Schoenert Dear Maintainer, Thunderbird 1:78.11.0-1 in testing is unable to establish some (all?) TLS connections when run with libnss3 2:3.61-1, because it was built with libnss3-dev 2:3.66-1. The issue occurs because the size of SSLChannelInfo increased between NSS 3.61 and 3.66 (due to the addition of PRBool isFIPS). SSL_GetChannelInfo takes both a pointer to and size of SSLChannelInfo as arguments. If the size is greater than the size it expects, it returns SECFailure, causing the connection to fail. See https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=989839#48 for details. The issue is being discussed on debian-release, where Sebastian Ramacher pointed out that the libnss3 symbol file should bump the minimum version requirement for all symbols that works with SSLChannelInfo.[1] I agree. As far as I can tell, SSL_GetChannelInfo is the only such symbol. I believe it should be bumped to 2:3.66 for package 2:3.67 and bumped in future versions whenever the size of SSLChannelInfo changes. I've attached a patch to do so. Thanks for considering, Kevin [1]: https://lists.debian.org/debian-release/2021/06/msg00597.html -- System Information: Debian Release: 11.0 APT prefers testing-debug APT policy: (990, 'testing-debug'), (990, 'testing'), (500, 'unstable-debug'), (500, 'testing-security'), (500, 'stable-debug'), (500, 'unstable'), (500, 'oldstable'), (101, 'experimental'), (1, 'experimental-debug') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.13.0-rc6 (SMP w/4 CPU threads) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages libnss3 depends on: ii libc6 2.31-12 ii libnspr4 2:4.29-1 ii libsqlite3-0 3.34.1-3 libnss3 recommends no packages. libnss3 suggests no packages. -- no debconf information >From eaffc616b99dd2be285ade5df072cfa1e30924fe Mon Sep 17 00:00:00 2001 Message-Id: From: Kevin Locke Date: Fri, 18 Jun 2021 14:41:27 -0600 Subject: [PATCH] libnss3.symbols: bump SSL_GetChannelInfo to 2:3.66 PRBool isFIPS was added to SSLChannelInfo in NSS 3.66, causing its size to increase. Since SSL_GetChannelInfo is called with sizeof(SSLChannelInfo) and returns SECFailure when called with a larger size than it expects, it creates a version incompatibility where programs compiled with NSS >= 3.66 do not function correction when loaded with NSS < 3.66, as in #989839 for thunderbird. To avoid breakage, bump the version of SSL_GetChannelInfo, as suggested by Sebastian Ramacher in https://lists.debian.org/debian-release/2021/06/msg00597.html Signed-off-by: Kevin Locke --- debian/libnss3.symbols | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/debian/libnss3.symbols b/debian/libnss3.symbols index 5213379c..2bb7294a 100644 --- a/debian/libnss3.symbols +++ b/debian/libnss3.symbols @@ -154,5 +154,5 @@ libssl3.so libnss3 #MINVER# (symver)NSS_3.4 2:3.13.4-2~ (symver)NSS_3.7.4 2:3.13.4-2~ SSL_GetCipherSuiteInfo@NSS_3.4 2:3.44.0 - SSL_GetChannelInfo@NSS_3.4 2:3.34 + SSL_GetChannelInfo@NSS_3.4 2:3.66 SSL_GetPreliminaryChannelInfo@NSS_3.21 2:3.44.0 -- 2.30.2
Bug#990044: closed by Colin Watson (Re: Bug#990044: error: symbol 'grub_file_filters' not found)
Dear Colin, On 18.06.21 19:27, Debian Bug Tracking System wrote: This is an automatic notification regarding your Bug report which was filed against the grub2 package: #990044: error: symbol 'grub_file_filters' not found It has been closed by Colin Watson . Their explanation is attached below along with your original report. If this explanation is unsatisfactory and you have not received a better one in a separate message then please contact Colin Watson by replying to this email. Great! Thank you for you very fast response! That was it, I've only tried before grub-install /dev/sda best regards Stefan
Bug#989410: marked as done (nss breaks dogtag-pki autopkgtest on ppc64el: [SSL: LENGTH_MISMATCH] length mismatch (_ssl.c:1123))
Your message dated Fri, 18 Jun 2021 22:49:53 +0200
with message-id
and subject line Re: nss breaks dogtag-pki autopkgtest on ppc64el: [SSL:
LENGTH_MISMATCH] length mismatch (_ssl.c:1123)
has caused the Debian Bug report #989410,
regarding nss breaks dogtag-pki autopkgtest on ppc64el: [SSL: LENGTH_MISMATCH]
length mismatch (_ssl.c:1123)
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.)
--
989410: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=989410
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: nss, dogtag-pki
Control: found -1 nss/2:3.66-1
Control: found -1 dogtag-pki/10.10.2-3
Severity: serious
Tags: sid bullseye
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: breaks needs-update
Dear maintainer(s),
With a recent upload of nss the autopkgtest of dogtag-pki fails in
testing when that autopkgtest is run with the binary packages of nss
from unstable. It passes when run with only packages from testing. In
tabular form:
passfail
nssfrom testing2:3.66-1
dogtag-pki from testing10.10.2-3
all others from testingfrom testing
I copied some of the output at the bottom of this report.
Currently this regression is showing up in the migration report of nss
to testing [1]. Due to the nature of this issue, I filed this bug report
against both packages. Can you please investigate the situation and
reassign the bug to the right package?
More information about this bug and the reason for filing it can be found
on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation
Paul
[1] https://qa.debian.org/excuses.php?package=nss
https://ci.debian.net/data/autopkgtest/testing/ppc64el/d/dogtag-pki/12741349/log.gz
autopkgtest [18:46:23]: test pkispawn: [---
IP address is 192.168.122.76
Hostname was:
/etc/hosts now has:
127.0.0.1 localhost
::1 localhost ip6-localhost ip6-loopback
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters
192.168.122.76 autopkgtest.debci autopkgtest
Starting installation...
Completed installation for pki-tomcat
Notice: Trust flag u is set automatically if the private key is present.
ERROR: SSLError: HTTPSConnectionPool(host='autopkgtest.debci',
port=8443): Max retries exceeded with url: /ca/rest/installer/setupCert
(Caused by SSLError(SSLError(1, '[SSL: LENGTH_MISMATCH] length mismatch
(_ssl.c:1123)')))
File "/usr/lib/python3/dist-packages/pki/server/pkispawn.py", line
575, in main
scriptlet.spawn(deployer)
File
"/usr/lib/python3/dist-packages/pki/server/deployment/scriptlets/configuration.py",
line 995, in spawn
cert = deployer.setup_cert(client, tag)
File
"/usr/lib/python3/dist-packages/pki/server/deployment/__init__.py", line
355, in setup_cert
return client.setupCert(request)
File "/usr/lib/python3/dist-packages/pki/system.py", line 389, in
setupCert
response = self.connection.post(
File "/usr/lib/python3/dist-packages/pki/client.py", line 55, in wrapper
return func(self, *args, **kwargs)
File "/usr/lib/python3/dist-packages/pki/client.py", line 293, in post
r = self.session.post(
File "/usr/lib/python3/dist-packages/requests/sessions.py", line 590,
in post
return self.request('POST', url, data=data, json=json, **kwargs)
File "/usr/lib/python3/dist-packages/requests/sessions.py", line 542,
in request
resp = self.send(prep, **send_kwargs)
File "/usr/lib/python3/dist-packages/requests/sessions.py", line 655,
in send
r = adapter.send(request, **kwargs)
File "/usr/lib/python3/dist-packages/requests/adapters.py", line 514,
in send
raise SSLError(e, request=request)
Loading deployment configuration from debian/tests/deploy.cfg.
Installation log: /var/log/pki/pki-ca-spawn.20210602184645.log
Installing CA into /var/lib/pki/pki-tomcat.
Installation failed: HTTPSConnectionPool(host='autopkgtest.debci',
port=8443): Max retries exceeded with url: /ca/rest/installer/setupCert
(Caused by SSLError(SSLError(1, '[SSL: LENGTH_MISMATCH] length mismatch
(_ssl.c:1123)')))
CA spawn failed:
2021-06-02 18:47:26 ERROR: SSLError:
HTTPSConnectionPool(host='autopkgtest.debci', port=8443): Max retries
exceeded with url: /ca/rest/installer/setupCert (Caused by
SSLError(SSLError(1, '[SSL: LENGTH_MISMATCH] length mismatch
(_ssl.c:1123)')))
File "/usr/lib/python3/dist-packages/pki/server/pkispawn.py", line
575, in main
scriptlet.spawn(deployer)
File
Processed: Re: nss breaks dogtag-pki autopkgtest on ppc64el: [SSL: LENGTH_MISMATCH] length mismatch (_ssl.c:1123)
Processing commands for cont...@bugs.debian.org: > reassign 989410 src:nss 2:3.66-1 Bug #989410 [src:nss, src:dogtag-pki] nss breaks dogtag-pki autopkgtest on ppc64el: [SSL: LENGTH_MISMATCH] length mismatch (_ssl.c:1123) Bug reassigned from package 'src:nss, src:dogtag-pki' to 'src:nss'. No longer marked as found in versions dogtag-pki/10.10.2-3 and nss/2:3.66-1. Ignoring request to alter fixed versions of bug #989410 to the same values previously set Bug #989410 [src:nss] nss breaks dogtag-pki autopkgtest on ppc64el: [SSL: LENGTH_MISMATCH] length mismatch (_ssl.c:1123) Marked as found in versions nss/2:3.66-1. > affects 989410 dogtag-pki Bug #989410 [src:nss] nss breaks dogtag-pki autopkgtest on ppc64el: [SSL: LENGTH_MISMATCH] length mismatch (_ssl.c:1123) Added indication that 989410 affects dogtag-pki > fixed 989410 2:3.67-1 Bug #989410 [src:nss] nss breaks dogtag-pki autopkgtest on ppc64el: [SSL: LENGTH_MISMATCH] length mismatch (_ssl.c:1123) Marked as fixed in versions nss/2:3.67-1. > thanks Stopping processing here. Please contact me if you need assistance. -- 989410: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=989410 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#988214: Bug#989037: Bug#988214: fixed in rails 2:6.0.3.7+dfsg-1
Hi Utkarsh On 06-06-2021 06:14, Paul Gevers wrote: > I am hoping it's possible to just downgrade the *dependency* in rails > only, such that the upload can happen via unstable. There is no "direct > bullseye" route. Or do you expect you'll have to make (lots) of changes > to rails to match the right ruby-marcel package? If that's the case, > than ruby-marcel/unstable isn't a drop in replacement for > ruby-marcel/bullseye and I'd expect that ruby-marcel/unstable would need > a versioned Breaks for reverse dependent packages (ruby-activestorage), > but I'm not seeing that. Did your experimenting (as discussed on IRC last week) yield anything? Paul OpenPGP_signature Description: OpenPGP digital signature
Bug#966301: marked as done (guile oom test fails (but currently not on buildds))
Your message dated Fri, 18 Jun 2021 19:33:47 +
with message-id
and subject line Bug#966301: fixed in guile-2.2 2.2.7+1-6
has caused the Debian Bug report #966301,
regarding guile oom test fails (but currently not on buildds)
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.)
--
966301: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966301
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:guile-2.2
Version: 2.2.7+1-5.1
Severity: serious
Tags: sid bullseye
The guile testssuite fails one test on ppc64el:
[...]
wrote
`/<>/cache/guile/ccache/2.2-LE-8-3.A/<>/test-suite/standalone/test-stack-overflow.go'
allocate_stack failed: Cannot allocate memory
allocate_stack failed: Cannot allocate memory
allocate_stack failed: Cannot allocate memory
allocate_stack failed: Cannot allocate memory
allocate_stack failed: Cannot allocate memory
PASS: test-stack-overflow
wrote
`/<>/cache/guile/ccache/2.2-LE-8-3.A/<>/test-suite/standalone/test-out-of-memory.go'
GC Warning: Failed to expand heap by 134348800 bytes
GC Warning: Failed to expand heap by 134217728 bytes
GC Warning: Out of Memory! Heap size: 2 MiB. Returning NULL!
GC Warning: Failed to expand heap by 1000144896 bytes
GC Warning: Failed to expand heap by 113824 bytes
GC Warning: Out of Memory! Heap size: 2 MiB. Returning NULL!
mmap(PROT_NONE) failed
/bin/bash: line 5: 24840 Aborted top_srcdir="../.." srcdir="."
builddir="." CHARSETALIASDIR="/<>/lib" GUILE_AUTO_COMPILE=0
"../../meta/build-env" ${dir}$tst
FAIL: test-out-of-memory
==
1 of 39 tests failed
Please report to bug-gu...@gnu.org
https://buildd.debian.org/status/fetch.php?pkg=guile-2.2=ppc64el=2.2.7%2B1-5.1=1595497537=0
Apparently this is known, and already reported by Debian:
https://debbugs.gnu.org/cgi/bugreport.cgi?bug=+29464
but no update since 2017.
For some reason the test succeeds on the Ubuntu buildds.
--- End Message ---
--- Begin Message ---
Source: guile-2.2
Source-Version: 2.2.7+1-6
Done: Rob Browning
We believe that the bug you reported is fixed in the latest version of
guile-2.2, 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 966...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Rob Browning (supplier of updated guile-2.2 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: Fri, 18 Jun 2021 13:13:51 -0500
Source: guile-2.2
Architecture: source
Version: 2.2.7+1-6
Distribution: unstable
Urgency: medium
Maintainer: Rob Browning
Changed-By: Rob Browning
Closes: 966301
Changes:
guile-2.2 (2.2.7+1-6) unstable; urgency=medium
.
* Mark test-out-of-memory as an expected failure for now. Since this
test has been failing for a long time on various architectures, mark
it as expected to fail for now so that we'll still run it and can see
the results, but won't be blocked by it. There are known issues with
the test upstream, and at least in some past cases it's been possible
to reproduce the failure quickly by running
test-suite/standalone/test-out-of-memory in a loop.
.
Add 0005-Mark-test-out-of-memory-as-an-expected-failure-for-n.patch to
incorporate the change. (Closes: 966301)
Checksums-Sha1:
e90c497493913c9baa928fe2a4fc2947e14ed6b0 2151 guile-2.2_2.2.7+1-6.dsc
be9076ba3e8800d4964e502c5ae0f0310e754108 24116
guile-2.2_2.2.7+1-6.debian.tar.xz
db9609bbb370706f2fea64e488d355cdf382a4b8 7910
guile-2.2_2.2.7+1-6_amd64.buildinfo
Checksums-Sha256:
6decf132c8f3dd02731df676cccbecff4f461201c6f8bddfd6869955093de96d 2151
guile-2.2_2.2.7+1-6.dsc
4b9b36f8046a0626f532a18ef7d708ac2bbb2b6d9c71eb2948fb1d6469d94852 24116
guile-2.2_2.2.7+1-6.debian.tar.xz
1ec129aa741ae2688939b5980de6217558576e8eca2c654dfdae6aeb3be4af8e 7910
guile-2.2_2.2.7+1-6_amd64.buildinfo
Files:
b61b64e6ba77fce17b7a09ba62b44d53 2151 interpreters optional
guile-2.2_2.2.7+1-6.dsc
2a147bfd5039a261d0dfc879fba248fd 24116 interpreters optional
guile-2.2_2.2.7+1-6.debian.tar.xz
bbeb8deb28abe6d040451cfe2a88f697 7910 interpreters optional
guile-2.2_2.2.7+1-6_amd64.buildinfo
-BEGIN PGP SIGNATURE-
Processed: severity of 990000 is serious
Processing commands for cont...@bugs.debian.org:
> # make RC as DSA released
> severity 99 serious
Bug #99 {Done: Peter Palfrader } [src:tor] tor:
CVE-2021-34548 CVE-2021-34549 CVE-2021-34550
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
99: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=99
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#975270: rdiff-backup: Can't talk to the version from buster
Hello, Samuel Thibault, le dim. 16 mai 2021 19:03:11 +0200, a ecrit: > Gregor Zattler, le dim. 16 mai 2021 18:50:42 +0200, a ecrit: > > * Samuel Thibault [13. Mai. 2021]: > > > Kurt Roeckx, le jeu. 19 nov. 2020 20:40:05 +0100, a ecrit: > > >> I recently found out that my backup has broken for months. > > > > > > Not for month, but this does break my backups now that I try to upgrade > > > some machines, and I don't have another solution than to either > > > downgrade the package, or upgrade all my machines at the same time (!?) > > > to get my backups working again. > > > > the rdiff-backup project provides a helpful document > > regarding this: > > > > https://github.com/rdiff-backup/rdiff-backup/blob/master/docs/migration.md > > > > providing this document in the NEWS.Debian file might be > > enough in order to close this bug? > > Perhaps we could have a buster-backports package, so that before > upgrading machines to bullseye, we first just upgrade rdiff-backup on > all buster machines? I have uploaded it to buster-backports, it's now in so people can pre-upgrade. I'd however probably still be important to ship a NEWS.Debian entry to let people about about the incompatibility issue. Samuel
Bug#990044: marked as done (error: symbol 'grub_file_filters' not found)
Your message dated Fri, 18 Jun 2021 18:01:30 +0100
with message-id <20210618170130.gl13...@riva.ucam.org>
and subject line Re: Bug#990044: error: symbol 'grub_file_filters' not found
has caused the Debian Bug report #990044,
regarding error: symbol 'grub_file_filters' not found
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.)
--
990044: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=990044
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: grub2
Version: 2.02+dfsg1-20+deb10u3
Severity: critical
Justification: breaks the whole system
Dear Maintainer,
* What led up to the situation?
full upgrade to testing
* What exactly did you do (or not do) that was effective (or
ineffective)?
Install grub2/testing 2.04-18 amd64
* What was the outcome of this action?
Grub stop in rescue mode, message:
error: symbol 'grub_file_filters' not found
* What outcome did you expect instead?
loading the kernel
To start again, install 2.02+dfsg1-20+deb10u3, > u4 do not work
-- Package-specific info:
*** BEGIN /proc/mounts
/dev/sdb2 / ext4 rw,relatime,errors=remount-ro 0 0
/dev/sdb1 /boot ext4 rw,relatime,errors=remount-ro 0 0
/dev/mapper/_dev_dm_0 /home/nitz ext4 rw,relatime 0 0
*** END /proc/mounts
*** BEGIN /boot/grub/device.map
(hd0) /dev/disk/by-id/ata-SAMSUNG_HN-M101MBB_S2R8J1MBA04065
(hd1) /dev/disk/by-id/ata-WDC_WDS500G2B0A-00SM50_172843424862
#(hd2) /dev/disk/by-id/lvm-pv-uuid-Vty9C5-u24G-nx3B-Appj-UhSr-wQZj-LtfXc7
*** END /boot/grub/device.map
*** BEGIN /boot/grub/grub.cfg
#
# DO NOT EDIT THIS FILE
#
# It is automatically generated by grub-mkconfig using templates
# from /etc/grub.d and settings from /etc/default/grub
#
### BEGIN /etc/grub.d/00_header ###
if [ -s $prefix/grubenv ]; then
set have_grubenv=true
load_env
fi
if [ "${next_entry}" ] ; then
set default="${next_entry}"
set next_entry=
save_env next_entry
set boot_once=true
else
set default="Debian GNU/Linux, mit Xen-Hypervisor"
fi
if [ x"${feature_menuentry_id}" = xy ]; then
menuentry_id_option="--id"
else
menuentry_id_option=""
fi
export menuentry_id_option
if [ "${prev_saved_entry}" ]; then
set saved_entry="${prev_saved_entry}"
save_env saved_entry
set prev_saved_entry=
save_env prev_saved_entry
set boot_once=true
fi
function savedefault {
if [ -z "${boot_once}" ]; then
saved_entry="${chosen}"
save_env saved_entry
fi
}
function load_video {
if [ x$feature_all_video_module = xy ]; then
insmod all_video
else
insmod efi_gop
insmod efi_uga
insmod ieee1275_fb
insmod vbe
insmod vga
insmod video_bochs
insmod video_cirrus
fi
}
if [ x$feature_default_font_path = xy ] ; then
font=unicode
else
insmod part_msdos
insmod ext2
set root='hd1,msdos2'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd1,msdos2
--hint-efi=hd1,msdos2 --hint-baremetal=ahci1,msdos2
31010fdb-7e31-49df-bbce-b9fc3d11930d
else
search --no-floppy --fs-uuid --set=root 31010fdb-7e31-49df-bbce-b9fc3d11930d
fi
font="/usr/share/grub/unicode.pf2"
fi
if loadfont $font ; then
set gfxmode=auto
load_video
insmod gfxterm
set locale_dir=$prefix/locale
set lang=C
insmod gettext
fi
terminal_output gfxterm
if [ "${recordfail}" = 1 ] ; then
set timeout=30
else
if [ x$feature_timeout_style = xy ] ; then
set timeout_style=menu
set timeout=5
# Fallback normal timeout code in case the timeout_style feature is
# unavailable.
else
set timeout=5
fi
fi
### END /etc/grub.d/00_header ###
### BEGIN /etc/grub.d/05_debian_theme ###
insmod part_msdos
insmod ext2
set root='hd1,msdos2'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd1,msdos2
--hint-efi=hd1,msdos2 --hint-baremetal=ahci1,msdos2
31010fdb-7e31-49df-bbce-b9fc3d11930d
else
search --no-floppy --fs-uuid --set=root 31010fdb-7e31-49df-bbce-b9fc3d11930d
fi
insmod png
if background_image /usr/share/desktop-base/homeworld-theme/grub/grub-4x3.png;
then
set color_normal=white/black
set color_highlight=black/white
else
set menu_color_normal=cyan/blue
set menu_color_highlight=white/blue
fi
### END /etc/grub.d/05_debian_theme ###
### BEGIN /etc/grub.d/10_linux ###
function gfxmode {
set gfxpayload="${1}"
}
set linux_gfx_mode=
export linux_gfx_mode
menuentry 'Debian GNU/Linux' --class debian --class gnu-linux --class gnu
--class os $menuentry_id_option
Bug#990044: error: symbol 'grub_file_filters' not found
Package: grub2
Version: 2.02+dfsg1-20+deb10u3
Severity: critical
Justification: breaks the whole system
Dear Maintainer,
* What led up to the situation?
full upgrade to testing
* What exactly did you do (or not do) that was effective (or
ineffective)?
Install grub2/testing 2.04-18 amd64
* What was the outcome of this action?
Grub stop in rescue mode, message:
error: symbol 'grub_file_filters' not found
* What outcome did you expect instead?
loading the kernel
To start again, install 2.02+dfsg1-20+deb10u3, > u4 do not work
-- Package-specific info:
*** BEGIN /proc/mounts
/dev/sdb2 / ext4 rw,relatime,errors=remount-ro 0 0
/dev/sdb1 /boot ext4 rw,relatime,errors=remount-ro 0 0
/dev/mapper/_dev_dm_0 /home/nitz ext4 rw,relatime 0 0
*** END /proc/mounts
*** BEGIN /boot/grub/device.map
(hd0) /dev/disk/by-id/ata-SAMSUNG_HN-M101MBB_S2R8J1MBA04065
(hd1) /dev/disk/by-id/ata-WDC_WDS500G2B0A-00SM50_172843424862
#(hd2) /dev/disk/by-id/lvm-pv-uuid-Vty9C5-u24G-nx3B-Appj-UhSr-wQZj-LtfXc7
*** END /boot/grub/device.map
*** BEGIN /boot/grub/grub.cfg
#
# DO NOT EDIT THIS FILE
#
# It is automatically generated by grub-mkconfig using templates
# from /etc/grub.d and settings from /etc/default/grub
#
### BEGIN /etc/grub.d/00_header ###
if [ -s $prefix/grubenv ]; then
set have_grubenv=true
load_env
fi
if [ "${next_entry}" ] ; then
set default="${next_entry}"
set next_entry=
save_env next_entry
set boot_once=true
else
set default="Debian GNU/Linux, mit Xen-Hypervisor"
fi
if [ x"${feature_menuentry_id}" = xy ]; then
menuentry_id_option="--id"
else
menuentry_id_option=""
fi
export menuentry_id_option
if [ "${prev_saved_entry}" ]; then
set saved_entry="${prev_saved_entry}"
save_env saved_entry
set prev_saved_entry=
save_env prev_saved_entry
set boot_once=true
fi
function savedefault {
if [ -z "${boot_once}" ]; then
saved_entry="${chosen}"
save_env saved_entry
fi
}
function load_video {
if [ x$feature_all_video_module = xy ]; then
insmod all_video
else
insmod efi_gop
insmod efi_uga
insmod ieee1275_fb
insmod vbe
insmod vga
insmod video_bochs
insmod video_cirrus
fi
}
if [ x$feature_default_font_path = xy ] ; then
font=unicode
else
insmod part_msdos
insmod ext2
set root='hd1,msdos2'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd1,msdos2
--hint-efi=hd1,msdos2 --hint-baremetal=ahci1,msdos2
31010fdb-7e31-49df-bbce-b9fc3d11930d
else
search --no-floppy --fs-uuid --set=root 31010fdb-7e31-49df-bbce-b9fc3d11930d
fi
font="/usr/share/grub/unicode.pf2"
fi
if loadfont $font ; then
set gfxmode=auto
load_video
insmod gfxterm
set locale_dir=$prefix/locale
set lang=C
insmod gettext
fi
terminal_output gfxterm
if [ "${recordfail}" = 1 ] ; then
set timeout=30
else
if [ x$feature_timeout_style = xy ] ; then
set timeout_style=menu
set timeout=5
# Fallback normal timeout code in case the timeout_style feature is
# unavailable.
else
set timeout=5
fi
fi
### END /etc/grub.d/00_header ###
### BEGIN /etc/grub.d/05_debian_theme ###
insmod part_msdos
insmod ext2
set root='hd1,msdos2'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd1,msdos2
--hint-efi=hd1,msdos2 --hint-baremetal=ahci1,msdos2
31010fdb-7e31-49df-bbce-b9fc3d11930d
else
search --no-floppy --fs-uuid --set=root 31010fdb-7e31-49df-bbce-b9fc3d11930d
fi
insmod png
if background_image /usr/share/desktop-base/homeworld-theme/grub/grub-4x3.png;
then
set color_normal=white/black
set color_highlight=black/white
else
set menu_color_normal=cyan/blue
set menu_color_highlight=white/blue
fi
### END /etc/grub.d/05_debian_theme ###
### BEGIN /etc/grub.d/10_linux ###
function gfxmode {
set gfxpayload="${1}"
}
set linux_gfx_mode=
export linux_gfx_mode
menuentry 'Debian GNU/Linux' --class debian --class gnu-linux --class gnu
--class os $menuentry_id_option
'gnulinux-simple-31010fdb-7e31-49df-bbce-b9fc3d11930d' {
load_video
insmod gzio
if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio; fi
insmod part_msdos
insmod ext2
set root='hd1,msdos1'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd1,msdos1
--hint-efi=hd1,msdos1 --hint-baremetal=ahci1,msdos1
21ec0055-1c79-4010-a7b8-421818b40973
else
search --no-floppy --fs-uuid --set=root
21ec0055-1c79-4010-a7b8-421818b40973
fi
echo'Linux 5.10.0-7-amd64 wird geladen …'
linux /vmlinuz-5.10.0-7-amd64
root=UUID=31010fdb-7e31-49df-bbce-b9fc3d11930d ro quiet
echo'Initiale Ramdisk wird geladen …'
initrd /initrd.img-5.10.0-7-amd64
}
submenu 'Erweiterte Optionen für Debian
Processed: bug 990042 is forwarded to https://github.com/boumenot/p5-Net-Amazon/issues/9
Processing commands for cont...@bugs.debian.org: > forwarded 990042 https://github.com/boumenot/p5-Net-Amazon/issues/9 Bug #990042 [libnet-amazon-perl] libnet-amazon-perl: Net::Amazon broken with Amazon API changes? Set Bug forwarded-to-address to 'https://github.com/boumenot/p5-Net-Amazon/issues/9'. > thanks Stopping processing here. Please contact me if you need assistance. -- 990042: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=990042 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#990042: libnet-amazon-perl: Net::Amazon broken with Amazon API changes?
Package: libnet-amazon-perl Version: 0.62-1 Severity: grave Tags: upstream Justification: renders package unusable -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 I have a script which uses Net::Amazon, and which I run once every other year. The last attempt ended with no search results but just an error message of "Gone". The same can be seen when entering the URL from t/024signature.t in a browser: https://webservices.amazon.com/onca/xml?Service=AWSECommerceService=YOUR_AMZN_TOKEN=ItemSearch=Bubl%C3%A9=Music=ItemAttributes,Offers=2009-03-31=2009-06-02T16:31:39Z leads to a status of "410 Gone" and a content saying "Gone The requested resource /onca/xml is no longer available on this server and there is no forwarding address. Please remove all references to this resource." A very brief web search indicates that this API endpoint is retired. Which would make Net::Amazon disfunctional … Notes: - - tested with 0.62-2.1 but this most probably applies back to 0.62-1 - - I'll forward the bug upstream once I get a bug number Currently there's no issue yet at https://rt.cpan.org/Public/Dist/Display.html?Name=Net-Amazon or https://github.com/boumenot/p5-Net-Amazon/issues - - If Net::Amazon is indeed disfunctional we either need a fix quickly or it shouldn't be in the bullseye release - - libnet-amazon-perl has no reverse dependencies - - popcon: vote: 3 + old: 509 - - I think it was my first Debian package of a Perl module, back in 2006 :) - - I'll look into XML::Amazon soon Cheers, gregor - -- System Information: Debian Release: 11.0 APT prefers unstable APT policy: (990, 'unstable'), (500, 'unstable-debug'), (500, 'testing-security'), (500, 'experimental'), (500, 'testing'), (500, 'stable'), (500, 'oldstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.10.0-6-amd64 (SMP w/4 CPU threads) Kernel taint flags: TAINT_CPU_OUT_OF_SPEC, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=C, LC_CTYPE=de_AT.utf8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) LSM: AppArmor: enabled Versions of packages libnet-amazon-perl depends on: ii libhttp-message-perl 6.29-1 ii liblog-log4perl-perl 1.54-1 ii liburi-perl 5.08-1 ii libwww-perl 6.53-1 ii libxml-simple-perl2.25-1 ii perl 5.32.1-4 Versions of packages libnet-amazon-perl recommends: pn libcache-perl libnet-amazon-perl suggests no packages. - -- no debconf information -BEGIN PGP SIGNATURE- iQKTBAEBCgB9FiEE0eExbpOnYKgQTYX6uzpoAYZJqgYFAmDMxDhfFIAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEQx RTEzMTZFOTNBNzYwQTgxMDREODVGQUJCM0E2ODAxODY0OUFBMDYACgkQuzpoAYZJ qgZVFQ//V1NYgOfGVmEHdf2MCjgIW8wqKRk678iR5vGt2IOLAslR9lMxkR9A71AI 1LY0THUnA/dLQgq7DyNYjzvdppCikD5Lz+XGCeSySsdMgM5/JQLeqPXX8L7YmLGx Bl+rF1U5BKoixl6C11LVTWHzj45J1aj3pzoFQqq9Lqb2kx9bt1JtE6QQXFl9A+HR hTGTddsSMKcEAke14W0S2Fty3ULcCDLqB2C50OUKSLIOSN19vpMlPN/8CTgybMQL rQFI2qqlEnFY0UODuiDx0AxBP9wzszw5R4Jw3uK50GL7F/RTA1lAwJ/xy8FBoUSd HPGhw0+NKz4+NlOktlS2NICbFjhVhkaiYj+sIsmgumm1kXpqUlTO+Ydd/RaCJyMy c3bJ4p2pmKSZtDTpsZ7TcesX1uWILcv8IqAqkM27u4nd/zsH/zCQ3cyifbUGOlff zLk7touZPNxQBTUY+DN1dESxZtPnGPd+YUxzrjPySAhaOeIgwwnwiQ2Pt8fOWbWK oz5sH1DwS0TLJfgVd741JX37KeQc3jyCDptdjQ2rRHZkl1Lz7+YZFZE2CzsW/9zJ lG8V4YB7H5cgLgseW7xWxWj7vJDs/Hyo6qt9kXttIuilMkDGfZ4Ke1Wq6HiBUYNq jh/xH2gm1p8hCEmS4Qn/GAE51JoIgV6Is+tozZvvyqmNPWJVcsQ= =8Gia -END PGP SIGNATURE-
Bug#987441: Krita
Hi Lothar, Lothar Oelkers wrote (Fri, 18 Jun 2021 09:56:10 +0200): > Moin, > bin begeistert von bullseye. > Einzig Krita startet nicht nach korrekter Installation. > Nach apt remove qt5dxcd-plugin funktionieren alle Anwendungen. > Niemand vermisst das Paket. Please don't post such issues to this bug! This bug is only for problems regarding the debian-installer for Bullseye, not more. We don't want it to be flooded with diverse Bullseye issues. If you want to report an installation issue, please do so as documented here: https://d-i.debian.org/doc/installation-guide/de.amd64/apas04.html or post to debian-b...@lists.debian.org Holger -- Holger Wansing PGP-Fingerprint: 496A C6E8 1442 4B34 8508 3529 59F1 87CA 156E B076
Bug#987441: Krita
Ich bin so begeistert von Bullsey bis Debian 11 . Debian ist das beste Linux und es gibt nichts besseres. Ich Liebe mein Debian und das Sie nicht wie Cannonical und andere so vorangehen. Ich bin echt Dankbar und bin das ganze von Bullseye mitgegangebn. Das einzige Problem ist wenn ich die Workstation in den Standby geführt habe und möchte ihn wieder aufwecken. Das ist das einzige Problem. Bei mir läuft Gnome. Danke Liebe Debian Leute auf der ganzen Welt. He wir sind die echten und besten und das ist Debian. Gruß Andreas On 18.06.21 09:56, Lothar Oelkers wrote: Moin, bin begeistert von bullseye. Einzig Krita startet nicht nach korrekter Installation. Nach apt remove qt5dxcd-plugin funktionieren alle Anwendungen. Niemand vermisst das Paket. Gruß Lothar
Bug#988715: marked as done (atmel-firmware: triggers lintian autoreject tag 'file-in-etc-not-marked-as-conffile')
Your message dated Fri, 18 Jun 2021 13:34:02 + with message-id and subject line Bug#988715: fixed in atmel-firmware 1.3-4.1 has caused the Debian Bug report #988715, regarding atmel-firmware: triggers lintian autoreject tag 'file-in-etc-not-marked-as-conffile' 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.) -- 988715: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=988715 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: atmel-firmware Version: 1.3-4 Severity: serious Hi, your package triggers a non-overridable lintian autoreject tag, i.e. if the package would be reuploaded today without changes, it would be automatically rejected by ftp-master. https://lintian.debian.org/tags/file-in-etc-not-marked-as-conffile https://lintian.debian.org/sources/atmel-firmware E file-in-etc-not-marked-as-conffile etc/pcmcia/atmel.conf Andreas --- End Message --- --- Begin Message --- Source: atmel-firmware Source-Version: 1.3-4.1 Done: Adrian Bunk We believe that the bug you reported is fixed in the latest version of atmel-firmware, 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 988...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Adrian Bunk (supplier of updated atmel-firmware 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: Wed, 16 Jun 2021 15:17:00 +0300 Source: atmel-firmware Binary: atmel-firmware Architecture: source all Version: 1.3-4.1 Distribution: unstable Urgency: medium Maintainer: Simon Kelley Changed-By: Adrian Bunk Description: atmel-firmware - Firmware for Atmel at76c50x wireless networking chips. Closes: 988715 Changes: atmel-firmware (1.3-4.1) unstable; urgency=medium . * Non-maintainer upload. * Restore /etc/pcmcia/atmel.conf being a conffile. (Closes: #988715) Checksums-Sha1: dd973414a991b2b2130a8b57ca9ab6bc2971ea63 1666 atmel-firmware_1.3-4.1.dsc 2b1d26e1404b8bb8da592c4cb96a1bec837ce0fa 4483 atmel-firmware_1.3-4.1.diff.gz fdc4770a85f93db9fcca6cab499c2bdc036dc147 147328 atmel-firmware_1.3-4.1_all.deb c478827802868ff0ebb1f2f96765795751336aaa 4767 atmel-firmware_1.3-4.1_amd64.buildinfo Checksums-Sha256: f2a7f5267e3ab02b593c294dce189c514292216ca92f115386f34274b46a1278 1666 atmel-firmware_1.3-4.1.dsc b989f4cbafc2a1c6b17c7ae6d9e310532f7e24482b639aaeca14c899d7f8d93a 4483 atmel-firmware_1.3-4.1.diff.gz fed7f4ceb224d2420f44081ce6d4007edfef2133019dbf6e1f53e17bb9d92da6 147328 atmel-firmware_1.3-4.1_all.deb cb39f87d401f819669b812ec39242f37a2de06ab7c792f000139c61ab37dded9 4767 atmel-firmware_1.3-4.1_amd64.buildinfo Files: 2d32b48041a275cf2a8cc635c3c38727 1666 non-free/net optional atmel-firmware_1.3-4.1.dsc b77192a87080ace7f01a9843a9121727 4483 non-free/net optional atmel-firmware_1.3-4.1.diff.gz ece7e753fd1b1458ec2d6ec6a2165807 147328 non-free/net optional atmel-firmware_1.3-4.1_all.deb ad5acfbe6c78f103a6e855ba24cad940 4767 non-free/net optional atmel-firmware_1.3-4.1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAmDJ9nYACgkQiNJCh6LY mLEyWw/9GV1kT61oVFVZCBbVviHjzfsa0RP2PslylZ+PANvGFcg/jtzJ0K3B2gg/ dsa/Oy8ZDHyUcJy2076kMRURW8O/VLa88+sRe8WDDGBzQk1FYGgqNBxU9mdVQukM jOldR7SdIkypVvxWErwh9//7kMqBoN/rYLneXtoEG3vM7wf2kVE7Gr753Ed67z// e/XdofKB3dveEL3lEOOxzxamfPpk2N+hV3YxeTbnuhXiFZTJ4uUH0b6IYCgW0SQv CA00ERKKMiDWfyA2XLmLxHsJbCCpqR0KTd/+4Bhb2tpzNMcMFeczxtFCSKpPjr95 5CjgmyhRgU7f/sqgt4UOI+vNhY49Po8hvcnkm2iTJatZUPGShPVlHpwHSK1xllFK ZkWM8UrlXHxDct95A3LZOx80/9Qhq83bsZy/yrXmV0FlxZxCPQMTYFcQioCK8xYw r5b3c+XFbsL6IhvgCuoCcmn/oqcU6XjmcMSEt+MpvDHOEdLvH3E0xVBwMPuZvgiF wg+Lcxt2m0qhQUbaDw8/KAMwk/plcBiRs2rlrnQRdq/1ZtkxKS4M2w8enoKJpzFA IWrHUA/TD/6c1wmrFfiyw1e9v3ZGfIn+qIs/fkl6093h7CaAPJLW0fZKYnjOyTOC HkSTK+B3X7x8ZJRO87XHviGdKKd6QuUhP7hjk8ykASSIEInxEnU= =GyA1 -END PGP SIGNATURE End Message ---
Bug#988713: marked as done (pipemeter: triggers lintian autoreject tag 'FSSTND-dir-in-usr')
Your message dated Fri, 18 Jun 2021 12:34:17 + with message-id and subject line Bug#988713: fixed in pipemeter 1.1.5-1.1 has caused the Debian Bug report #988713, regarding pipemeter: triggers lintian autoreject tag 'FSSTND-dir-in-usr' 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.) -- 988713: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=988713 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: pipemeter Version: 1.1.5-1 Severity: serious Hi, your package triggers a non-overridable lintian autoreject tag, i.e. if the package would be reuploaded today without changes, it would be automatically rejected by ftp-master. https://lintian.debian.org/tags/FSSTND-dir-in-usr https://lintian.debian.org/sources/pipemeter E FSSTND-dir-in-usr usr/man/ Andreas --- End Message --- --- Begin Message --- Source: pipemeter Source-Version: 1.1.5-1.1 Done: Adrian Bunk We believe that the bug you reported is fixed in the latest version of pipemeter, 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 988...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Adrian Bunk (supplier of updated pipemeter 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: Wed, 16 Jun 2021 15:05:01 +0300 Source: pipemeter Architecture: source Version: 1.1.5-1.1 Distribution: unstable Urgency: medium Maintainer: Clint Byrum Changed-By: Adrian Bunk Closes: 988713 Changes: pipemeter (1.1.5-1.1) unstable; urgency=medium . * Non-maintainer upload. * Apply patch from Dennis Filder moving the man page to the correct location. (Closes: #988713) Checksums-Sha1: f2eb00f12d821cf596746782664a70fc28f89014 1788 pipemeter_1.1.5-1.1.dsc 0cd3964503be2656f1b14fb1c659796e5f80bfe0 2032 pipemeter_1.1.5-1.1.debian.tar.xz Checksums-Sha256: 8e1c8d4fb8984251d00b63af0e55c650378b325b0443406e9b16a6af6d5b63a1 1788 pipemeter_1.1.5-1.1.dsc 46353e86ca5f03dce83a7cac9b194eed7de8fcb9b7137598ce08ef25b71a8a23 2032 pipemeter_1.1.5-1.1.debian.tar.xz Files: 9a8e95839812f3a2b21ed0aac4712d4c 1788 admin extra pipemeter_1.1.5-1.1.dsc c0a109595187ba1898f9d9018e3c4869 2032 admin extra pipemeter_1.1.5-1.1.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAmDJ6eQACgkQiNJCh6LY mLHOyA/+I4kPU1jnpkHMDD0M2/qmcm1ZPApTqe308265EJg2G39p3W7to04GJ4lc pLrR9hZteThxg/8JHPdyngbUjGPJaBv3S9e6LabYPa6IukvzeE88I9ekajcW3Czy 4IFhw1dSJjJ93P7AGCWJ1DeOnzPYom8h7aKF1IQVUywO5fO1SPb2yViIR/JxdGln C5rvivDrfzI6p/dJg4s3iAMk5D6uqZIL6kpCWBb8mcS/qP2uads7SnXyTT7RW2uf D6Hiilqw3R6ndTcUUaPRwa7yjJhVB2jyMqWa7h2UnfvtwOaYX7K1capNnk0aNZGL f1ZN6QqeuGusZLtr9diyL7aS27C5eWYUhF9N1h0m58n4n5kaBS0/rT6UMXlFS2JH Tsm/Qc+GTDXNslAqdulrvC61rkWmsTy39SAOZD/vp1N0SClGdsqUji8yXilNOQ7+ cu0TyTCk1XnloaJssqyAo1oFe1GbMMX/EWHt52bv2NHNx9AcFbev3F0RyyGqzvfi FNt0LMb+Rc3toBOzwinMJRqp5p0UB3aFWioTPCXjeVWe0feMjdmpSi7Snxm6uq3Z mbNqh7Rwyck6lfMBjpo3q9MXQ/imF89Pa6A2Dg+FSc3B6R1iRsZvgvYPk5Y5ArEy Ypc5Xo4cSkgrfC9VqfGNo7F8OAVndzvy2XkaxAYsw18raM5BEek= =3x+9 -END PGP SIGNATURE End Message ---
Bug#932501: marked as done (squid-deb-proxy: daemon does not start due to the conf file not being allowed by apparmor)
Your message dated Fri, 18 Jun 2021 12:23:38 + with message-id and subject line Bug#932501: fixed in squid-deb-proxy 0.8.15+nmu1 has caused the Debian Bug report #932501, regarding squid-deb-proxy: daemon does not start due to the conf file not being allowed by apparmor 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.) -- 932501: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=932501 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: squid-deb-proxy Severity: important Tags: patch Dear Maintainer, squid-deb-proxy fails to start due due to the conf file not being allowed by apparmor: Jul 20 16:28:48 Tardis squid: FATAL: Unable to open configuration file: /etc/squid-deb-proxy/squid-deb-proxy.conf: (13) Permission denied Jul 20 16:28:48 Tardis squid-deb-proxy[10170]: failed! Jul 20 16:35:30 Tardis squid-deb-proxy[10276]: Stopping Squid Deb HTTP Proxy: squid-deb-proxy. Jul 20 16:35:30 Tardis systemd[1]: squid-deb-proxy.service: Succeeded. Jul 20 16:35:30 Tardis kernel: [4157921.317296] audit: type=1400 audit(1563597330.601:32): apparmor="DENIED" operation="open" profile="/usr/sbin/squid" name="/etc/squid-deb-proxy/squid-deb-proxy.conf" pid=10301 comm="squid" requested_mask="r" denied_mask="r" fsuid=0 ouid=0 Jul 20 16:35:30 Tardis squid-deb-proxy[10284]: Starting Squid Deb HTTP Proxy: squid-deb-proxy2019/07/20 16:35:30| FATAL: Unable to open configuration file: /etc/squid-deb-proxy/squid-deb-proxy.conf: (13) Permission denied The fix is to add /etc/squid-deb-proxy/** r, to /etc/apparmor.d/usr.sbin.squid Then apparmor_parser -r /etc/apparmor.d/usr.sbin.squid systemctl restart squid-deb-proxy #And test dig +nocmd +noall +answer @224.0.0.251 -p 5353 -t ptr _apt_proxy._tcp.local -- System Information: Debian Release: bullseye/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.19.0-5-amd64 (SMP w/4 CPU cores) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_NZ.UTF-8, LC_CTYPE=en_NZ.UTF-8 (charmap=UTF-8), LANGUAGE=en_NZ:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled --- End Message --- --- Begin Message --- Source: squid-deb-proxy Source-Version: 0.8.15+nmu1 Done: Hideki Yamane We believe that the bug you reported is fixed in the latest version of squid-deb-proxy, 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 932...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Hideki Yamane (supplier of updated squid-deb-proxy 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: Mon, 14 Jun 2021 23:41:11 +0900 Source: squid-deb-proxy Architecture: source Version: 0.8.15+nmu1 Distribution: unstable Urgency: medium Maintainer: Michael Vogt Changed-By: Hideki Yamane Closes: 932501 Changes: squid-deb-proxy (0.8.15+nmu1) unstable; urgency=medium . * Non-maintainer upload. * Add apparmor profiles to work (Closes: #932501) Checksums-Sha1: 83f33f13934c37a3673a78a5f788e8c5326bfff2 1803 squid-deb-proxy_0.8.15+nmu1.dsc b25e6f058b766b7523fd98a04892a1d5c4316090 22160 squid-deb-proxy_0.8.15+nmu1.tar.xz 9622b24d360ab475a939759fa419df106ec49f0d 7324 squid-deb-proxy_0.8.15+nmu1_amd64.buildinfo Checksums-Sha256: 6f5c145bd5a00d4427d0dbb40f5a3154f474fcb8de4c7db91e2d05f796911ed1 1803 squid-deb-proxy_0.8.15+nmu1.dsc 47891793545962e35a5230b756f347ac9d7a4ce13f44d4ce484a58c8f56dc427 22160 squid-deb-proxy_0.8.15+nmu1.tar.xz 2508f1b7567e2183edb2dd23257a754c2a50b7805027033e8274195711d32584 7324 squid-deb-proxy_0.8.15+nmu1_amd64.buildinfo Files: bf9bd8860cd031fc8cf66fca96d29fc5 1803 net optional squid-deb-proxy_0.8.15+nmu1.dsc eb984fc11fd0a287ee2d8db055a3b8b5 22160 net optional squid-deb-proxy_0.8.15+nmu1.tar.xz e497b165b8e4c04b88c71b3836f7317e 7324 net optional squid-deb-proxy_0.8.15+nmu1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEWOEiL5aWyIWjzRBMXTKNCCqqsUAFAmDIku8ACgkQXTKNCCqq sUDZJRAAj8BYoZZrTFJA/Nrmaz+mQpDofD4HivEpXJNWzZ0jhnINqLjvNXUvYg77
Bug#971897: marked as done (python3-gpiozero: Missing dependency/recommend on python3-pkg-resources)
Your message dated Fri, 18 Jun 2021 12:19:53 + with message-id and subject line Bug#971897: fixed in gpiozero 1.4.1-1.3 has caused the Debian Bug report #971897, regarding python3-gpiozero: Missing dependency/recommend on python3-pkg-resources 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.) -- 971897: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=971897 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: python3-gpiozero Version: 1.4.1-1.1 Dear maintainer, python3-gpiozero contains a "pinout" script, that crashes if python3-pkg-resources is not installed: $ pinout Traceback (most recent call last): File "/usr/bin/pinout", line 6, in from pkg_resources import load_entry_point ModuleNotFoundError: No module named 'pkg_resources' Best regards, Val --- End Message --- --- Begin Message --- Source: gpiozero Source-Version: 1.4.1-1.3 Done: Adrian Bunk We believe that the bug you reported is fixed in the latest version of gpiozero, 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 971...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Adrian Bunk (supplier of updated gpiozero 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: Wed, 16 Jun 2021 14:50:22 +0300 Source: gpiozero Architecture: source Version: 1.4.1-1.3 Distribution: unstable Urgency: medium Maintainer: Debian Raspberry Pi Maintainers Changed-By: Adrian Bunk Closes: 971897 Changes: gpiozero (1.4.1-1.3) unstable; urgency=medium . * Non-maintainer upload. * Add the missing dependency on python3-pkg-resources. (Closes: #971897) Checksums-Sha1: 45034cb5c0e3eb66cea8d6893f642f48ad8b4ba2 2035 gpiozero_1.4.1-1.3.dsc 83898811eac64a1719a83dd620236a029829743f 3044 gpiozero_1.4.1-1.3.debian.tar.xz Checksums-Sha256: a8d41ab4ae448ceb3bbdc3c49a93ba9b7af02548efa96fc7121a48b063a4e063 2035 gpiozero_1.4.1-1.3.dsc 874139b2a2ba9280696ba12366978bf0a5620530c89336d251d9c0890ee4530a 3044 gpiozero_1.4.1-1.3.debian.tar.xz Files: a6b5ee7a8abb187cc13a428157967e6f 2035 python optional gpiozero_1.4.1-1.3.dsc 900fc60bf8a05a9c4ab58226a6bde158 3044 python optional gpiozero_1.4.1-1.3.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAmDJ5psACgkQiNJCh6LY mLFTvhAAkHkJwdFeEzT9L1S8FefkLj6gqKEg8Goy2EV+LxWtor6UG/1rJjEoGMM+ D42xR6u1bCHK1R4yii1SbgxMZTc+6ysyeQglsLf1xZSAhv7i0ZNTI35h38u8WaQU wEhjjrvrofs0vUnor90/wvsqzojHlOGvdYKsgyWHxgfhbHJtXumwffjvcvRlx+ui a4a1fy1DwzKv5ska1/7fBRbg1WpnF3AYyQFeWK8T9YLt29ZYY+UDjIXhKjePQyYI d1l2SyZvtYmOWxORfWrqbgb74slvZWv3efbcAjdNTckIG54kMz1rwQM71XDBjDsI e1qfdB/byi/bmHz3+fWEe0zyfKfhbGfPMM2xStJSuTvko0LDycNGZhG7mVwBXwQM ChHjm48Nm/bkG5I3VfDvG7GxMLTaYHEDs1ZcZsm4nTawflm6rt7rtIAzPnWUKnrw 9O1CKrV9THRXgCR12EnBGmX9FPu9SwZ8LXlu5dZAce6mj27BX9U4INLDbv3a+lQO myTA9KzEl5k+UqWWvtVKxfei/EFCOkSRCSZLtENzQhWU4Qg5eqAJ9MO14nYOY9B6 fhBLL2L9n+sT/6slK3CS3NgU/lt9TNJ+SBNvGVOiAtxpbH+6Xv+gBkPTDw+hYgsD ESQm9Cnpyb/cP2L4yQbFvjg3Y+Nf4mdj0VedTN/PcIHFSWjhJBI= =y6LT -END PGP SIGNATURE End Message ---
Bug#982459: mdadm --examine in chroot without /proc,/dev,/sys mounted corrupts host's filesystem
Hi, On 25.04.21 00:36, Judit Foglszinger wrote: can you reproduce this bug on bullseye? (4.1-11) If so, what is your configuration (VM used, type of RAID)? Are all three conditions (/proc, /dev and /sys not mounted) required or does this also happen, if eg /dev and /sys are there but not /proc? If it still occurs until there would be a proper fix by upstream, a workaround like "are we in a chroot, if so, are the required things mounted, if not, fail", could be used to avoid the file system corruption. My own observations: Could not reproduce in virtualbox (both chroot and host system using recent bullseye), using RAID1, /dev/md0 on / type ext4 (rw,relatime,errors=remount-ro) # chroot chroot / # mdadm --examine --scan --config=partitions / # mdadm: cannot open /proc/partitions / # mdadm: No devices listed in partitions (in background on host running the mentioned find / command) No filesystem corruption after over 15 minutes, running the mdadm command in chroot several times didn't make a difference on that. I'm really sorry: Somehow I missed this mail when it came in my inbox 6 weeks ago. I only recognized the answer when I checked bugs.debian.org last week. I tried to reproduce the bug again and discovered, that my description contained a serious error: In fact /proc MUST be mounted in the chroot to observe the bug! I also could reproduce the bug with mdadm-4.1-11 (from bullseye) installed in the buster chroot (all other packages still from buster). I will try to reproduce the bug now with one of /dev or /sys mounted and check if it still occurs or not. I will send my report about this later as this will take some time again. Sorry for the delayed answer and the error in my initial bug report. Best Regards, -- Patrick Cernko Joint Administration: Information Services and Technology Max-Planck-Institute fuer Informatik & Softwaresysteme smime.p7s Description: S/MIME Cryptographic Signature
Processed: tagging 989603
Processing commands for cont...@bugs.debian.org: > tags 989603 + upstream confirmed Bug #989603 [ocsinventory-server] ocsinventory-server: Does not start after install Added tag(s) upstream and confirmed. > thanks Stopping processing here. Please contact me if you need assistance. -- 989603: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=989603 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tagging 983583
Processing commands for cont...@bugs.debian.org: > tags 983583 + pending Bug #983583 [src:golang-github-sylabs-sif] FTBFS on mips64el and mipsel Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 983583: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=983583 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#987441: Krita
Moin, bin begeistert von bullseye. Einzig Krita startet nicht nach korrekter Installation. Nach apt remove qt5dxcd-plugin funktionieren alle Anwendungen. Niemand vermisst das Paket. Gruß Lothar
Bug#989080: cifs-utils: Fix for CVE-2021-20208 breaks cifs.upcall
control: tags -1 +patch Here's MR https://salsa.debian.org/samba-team/cifs-utils/-/merge_requests/8
Processed: Re: cifs-utils: Fix for CVE-2021-20208 breaks cifs.upcall
Processing control commands: > tags -1 +patch Bug #989080 [cifs-utils] cifs-utils: Fix for CVE-2021-20208 breaks cifs.upcall Added tag(s) patch. -- 989080: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=989080 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#990026: cron: Reduced charset in MAILTO causes breakage
Package: cron Version: 3.0pl1-134 Severity: serious File: cron X-Debbugs-Cc: sm...@debian.org This change: https://salsa.debian.org/debian/cron/-/blob/master/debian/patches/features/Add-MAILFROM-environment-variable.patch added a MAILFROM envvar. It also adds a whitelist filter to both MAILFROM and MAILTO (which it fails to document in debian/cron.NEWS). Crucially, this now excludes the '=' character, among others. Since email localparts with embedded key=value assignments are frequently used to set variables like severity or category in ticketing / workflow systems, this is going to break existing installations. (It definitely will do so at my employer.) At minimum this needs to be documented. Ideally, the set of allowed characters should be expanded.
