Bug#980935: pyzo: Crash at startup with python3.9
Hi. On Fri, 19 Feb 2021 16:35:29 +0100 Gianfranco Costamagna wrote: > Due to freeze, I can upload the patch on this bug right now, and maybe we can upload your changes in git to unstable once the current one goes in testing? > > I'm doing some git work to polish the packaging, I'll try to rebase your changes and push later today Excellent : thanks a lot. Alexis Bienvenüe.
Bug#973168: marked as done (pylint: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.9 3.8" returned exit code 13)
Your message dated Wed, 24 Feb 2021 05:33:28 +
with message-id
and subject line Bug#973168: fixed in pylint 2.7.1-1
has caused the Debian Bug report #973168,
regarding pylint: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i
python{version} -p "3.9 3.8" returned exit code 13
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.)
--
973168: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973168
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pylint
Version: 2.6.0-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201027 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[2]: Entering directory '/<>/doc'
> rm -f features.rst
> PYTHONPATH=/<> python3 ./exts/pylint_features.py
> rm -f extensions.rst
> PYTHONPATH=/<> python3 ./exts/pylint_extensions.py
> sphinx-build -b html -d _build/doctrees . _build/html
> Running Sphinx v3.2.1
> making output directory... done
> loading intersphinx inventory from
> https://astroid.readthedocs.io/en/latest/objects.inv...
> loading intersphinx inventory from https://docs.python.org/3/objects.inv...
> building [mo]: targets for 0 po files that are out of date
> building [html]: targets for 38 source files that are out of date
> updating environment: [new config] 38 added, 0 changed, 0 removed
> reading sources... [ 2%] backlinks
> reading sources... [ 5%] development_guide/contribute
> reading sources... [ 7%] development_guide/index
> reading sources... [ 10%] faq
> reading sources... [ 13%] how_tos/custom_checkers
> reading sources... [ 15%] how_tos/index
> reading sources... [ 18%] how_tos/plugins
> reading sources... [ 21%] how_tos/transform_plugins
> reading sources... [ 23%] index
> reading sources... [ 26%] intro
> reading sources... [ 28%] support
> reading sources... [ 31%] technical_reference/c_extensions
> reading sources... [ 34%] technical_reference/checkers
> reading sources... [ 36%] technical_reference/extensions
> reading sources... [ 39%] technical_reference/features
> reading sources... [ 42%] technical_reference/index
> reading sources... [ 44%] technical_reference/startup
> reading sources... [ 47%] tutorial
> reading sources... [ 50%] user_guide/ide-integration
> reading sources... [ 52%] user_guide/index
> reading sources... [ 55%] user_guide/installation
> reading sources... [ 57%] user_guide/message-control
> reading sources... [ 60%] user_guide/options
> reading sources... [ 63%] user_guide/output
> reading sources... [ 65%] user_guide/run
> reading sources... [ 68%] whatsnew/1.6
> reading sources... [ 71%] whatsnew/1.7
> reading sources... [ 73%] whatsnew/1.8
> reading sources... [ 76%] whatsnew/1.9
> reading sources... [ 78%] whatsnew/2.0
> reading sources... [ 81%] whatsnew/2.1
> reading sources... [ 84%] whatsnew/2.2
> reading sources... [ 86%] whatsnew/2.3
> reading sources... [ 89%] whatsnew/2.4
> reading sources... [ 92%] whatsnew/2.5
> reading sources... [ 94%] whatsnew/2.6
> reading sources... [ 97%] whatsnew/changelog
> reading sources... [100%] whatsnew/index
>
> looking for now-outdated files... none found
> pickling environment... done
> checking consistency... done
> preparing documents... done
> writing output... [ 2%] backlinks
> writing output... [ 5%] development_guide/contribute
> writing output... [ 7%] development_guide/index
> writing output... [ 10%] faq
> writing output... [ 13%] how_tos/custom_checkers
> writing output... [ 15%] how_tos/index
> writing output... [ 18%] how_tos/plugins
> writing output... [ 21%] how_tos/transform_plugins
> writing output... [ 23%] index
> writing output... [ 26%] intro
> writing output... [ 28%] support
> writing output... [ 31%] technical_reference/c_extensions
> writing output... [ 34%] technical_reference/checkers
> writing output... [ 36%] technical_reference/extensions
> writing output... [ 39%] technical_reference/features
> writing output... [ 42%] technical_reference/index
> writing output... [ 44%] technical_reference/startup
> writing output... [ 47%] tutorial
> writing output... [ 50%] user_guide/ide-integration
> writing output... [ 52%] user_guide/index
> writing output... [ 55%] user_guide/installation
> writing output... [ 57%] user_guide/message-control
> writing output... [ 60%] user_guide/options
> writing output... [ 63%] user_guide/output
> writing output... [ 65%] user_guide/run
> writing output... [ 68%] whatsnew/1.6
> writing output... [ 71%] whatsnew/1.7
> writing output... [ 73%] whatsnew/1.8
> writ
Bug#983091: xapian-core FTBFS on i386: test failure
On Tue, Feb 23, 2021 at 10:22:39PM +0200, Adrian Bunk wrote: > On Tue, Feb 23, 2021 at 07:52:42PM +, Olly Betts wrote: > >... > > As you note, on i386 the test was only run with the SSE build before > > the recent debian/rules modernisation, but that doesn't explain why > > m68k now fails. Looking at older m68k logs, it seems the testsuite > > wasn't being run, though I'm not seeing why not. > >... > > m68k and sh4 are building with nocheck. > > nocheck handling was lost in the debian/rules rewrite. I dropped that handling as I thought dh_auto_test now handled it by default, but checking the docs I see that is only on in compat level 13 and up (which I avoided to aid backporting.) Thanks for the pointer. Cheers, Olly
Processed: Bug#973168 marked as pending in pylint
Processing control commands:
> tag -1 pending
Bug #973168 [src:pylint] pylint: FTBFS: dh_auto_test: error: pybuild --test
--test-pytest -i python{version} -p "3.9 3.8" returned exit code 13
Added tag(s) pending.
--
973168: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973168
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#973168: marked as pending in pylint
Control: tag -1 pending Hello, Bug #973168 in pylint 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/pylint/-/commit/0db6ef95ac2d24298e8bd37e0386274c1795bf49 New upstream release; Closes: Closes: #973168 (this message was generated automatically) -- Greetings https://bugs.debian.org/973168
Processed: tagging 973168
Processing commands for cont...@bugs.debian.org:
> tags 973168 + fixed-upstream
Bug #973168 [src:pylint] pylint: FTBFS: dh_auto_test: error: pybuild --test
--test-pytest -i python{version} -p "3.9 3.8" returned exit code 13
Ignoring request to alter tags of bug #973168 to the same tags previously set
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
973168: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973168
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: tagging 973168
Processing commands for cont...@bugs.debian.org:
> tags 973168 - patch
Bug #973168 [src:pylint] pylint: FTBFS: dh_auto_test: error: pybuild --test
--test-pytest -i python{version} -p "3.9 3.8" returned exit code 13
Removed tag(s) patch.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
973168: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973168
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#983383: marked as done (qgis-server-common: missing Breaks+Replaces: qgis-server (<< 3.16))
Your message dated Wed, 24 Feb 2021 05:03:37 +
with message-id
and subject line Bug#983383: fixed in qgis 3.16.4+dfsg-1~exp2
has caused the Debian Bug report #983383,
regarding qgis-server-common: missing Breaks+Replaces: qgis-server (<< 3.16)
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.)
--
983383: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=983383
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: qgis-server-common
Version: 3.16.4+dfsg-1~exp1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package fails to upgrade from
'sid' to 'experimental'.
It installed fine in 'sid', then the upgrade to 'experimental' fails
because it tries to overwrite other packages files without declaring a
Breaks+Replaces relation.
See policy 7.6 at
https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces
>From the attached log (scroll to the bottom...):
Preparing to unpack .../qgis-server-common_3.16.4+dfsg-1~exp1_all.deb ...
Unpacking qgis-server-common (3.16.4+dfsg-1~exp1) ...
dpkg: error processing archive
/var/cache/apt/archives/qgis-server-common_3.16.4+dfsg-1~exp1_all.deb
(--unpack):
trying to overwrite '/usr/share/qgis/resources/server/api/ogc/schema.json',
which is also in package qgis-server 3.10.14+dfsg-1
dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
Errors were encountered while processing:
/var/cache/apt/archives/qgis-server-common_3.16.4+dfsg-1~exp1_all.deb
cheers,
Andreas
qgis-server=3.10.14+dfsg-1_qgis-server-common=3.16.4+dfsg-1~exp1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: qgis
Source-Version: 3.16.4+dfsg-1~exp2
Done: Bas Couwenberg
We believe that the bug you reported is fixed in the latest version of
qgis, 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 983...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Bas Couwenberg (supplier of updated qgis 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, 23 Feb 2021 21:09:34 +0100
Source: qgis
Architecture: source
Version: 3.16.4+dfsg-1~exp2
Distribution: experimental
Urgency: medium
Maintainer: Debian GIS Project
Changed-By: Bas Couwenberg
Closes: 983327 983383
Changes:
qgis (3.16.4+dfsg-1~exp2) experimental; urgency=medium
.
* Add Breaks/Replaces to qgis-server-{bin,common} for moved files.
(closes: #983383)
* Update symbols for other architectures.
* Add patch to fix FTBFS with PROJ 8.0.0.
(closes: #983327)
Checksums-Sha1:
7a8081cd75f07fc24bb84adf046d0299067a90fc 5361 qgis_3.16.4+dfsg-1~exp2.dsc
93028e2e8badcddd89bf313078d5831d4a9b829e 602004
qgis_3.16.4+dfsg-1~exp2.debian.tar.xz
6f5073d645a9f8d90da99dd68fd0fe5961195a8e 40828
qgis_3.16.4+dfsg-1~exp2_amd64.buildinfo
Checksums-Sha256:
06e543df84334d5cf60296a288954f6fd7eac9204873f052c5cf267a933d99f9 5361
qgis_3.16.4+dfsg-1~exp2.dsc
2eafab43a9955aba8df4a91837d616316a6bb629eba73768cc20e08706097c53 602004
qgis_3.16.4+dfsg-1~exp2.debian.tar.xz
846f386ca89d91a341c97a8f6be13a1c13394ef2b79497afeb586042f0910564 40828
qgis_3.16.4+dfsg-1~exp2_amd64.buildinfo
Files:
bc89f7c452e8bbea5fb060a4a3183b75 5361 science optional
qgis_3.16.4+dfsg-1~exp2.dsc
5c827ec61101735e7b51d6ac9e9ddd46 602004 science optional
qgis_3.16.4+dfsg-1~exp2.debian.tar.xz
d27fc9fd21662075770792e39e7c35d9 40828 science optional
qgis_3.16.4+dfsg-1~exp2_amd64.buildinfo
-BEGIN PGP SIGNATURE-
iQIzBAEBCgAdFiEEgYLeQXBWQI1hRlDRZ1DxCuiNSvEFAmA12QwACgkQZ1DxCuiN
SvE1GhAAwPyx83Her8NvBOJLr2rosezzc15jWsE1VedUAUoccai28DnY1fYcWW8u
M9C6vL+yHP/YXpUbjQ7YAznL2ptujw1u+NrbII82txaxpt0WKAj7L5sSs7Mh6LGf
uoPTnvO+Q6awknL/E45lbG8nk8pKZ377RTQix2+7RxNIWE0sByMyo3OMDJAziH7K
2N5LUYUOpxwtrByxTAWv1bFzjFnxlnddZkdjViMcSgri//sOKn/moC6mVng2nG+H
5GuSkdQ14a+YZWr9Senl+231seBagRvGQ/wajevB5OOVYOlOd8a1BMnC5S0fRkwe
DzpNGOXl04/hpRJJ8nQYyqnfcJNfupaGS3tuUwXyL24Ektl2vCtUSAyt5SdY4SA3
MZQOW2HjPvWxq8rb3fmtyWzp1gDVAAJz4rEbadQmZRR33DvjSOhWWH7wUbEO4bph
AsAfK1kowZbf4PZmuCLk1V+LvDz7o6WNGxzu9NgeN6NDOfHcdLajgkOh6oT
Bug#983433: libemail-outlook-message-perl: msgconvert: missing dependency on libemail-message-perl
Package: libemail-outlook-message-perl
Version: 0.920-1
Severity: serious
Control: found -1 0.919-4~bpo10+1
X-Debbugs-CC: Olly Betts
Due to a change in msgconvert, libemail-outlook-message-perl is missing
a dependency on libemail-message-perl in bullseye and buster-backports,
but not in Debian buster or stretch.
I wasn't sure whether this was deliberate or not, but the needed
dependency on libemail-message-perl does not appear in Recommends or
Suggests either so I figure it was just missed.
I note that all the upstream metadata files indicate that the Perl
Email::Address module is required so Depends seems correct.
Looking at the debdiff between buster & buster-backports it looks like
this was introduced in buster-backports by the fix for mbox separators
(#904664) and in bullseye by the upstream release adding that patch.
$ sudo chronic apt install -y libemail-outlook-message-perl
$ msgconvert
Can't locate Email/Address.pm in @INC (you may need to install the
Email::Address module) (@INC contains: /etc/perl
/usr/local/lib/x86_64-linux-gnu/perl/5.32.1 /usr/local/share/perl/5.32.1
/usr/lib/x86_64-linux-gnu/perl5/5.32 /usr/share/perl5
/usr/lib/x86_64-linux-gnu/perl-base /usr/lib/x86_64-linux-gnu/perl/5.32
/usr/share/perl/5.32 /usr/local/lib/site_perl) at /usr/bin/msgconvert line 8.
BEGIN failed--compilation aborted at /usr/bin/msgconvert line 8.
$ grep Email::Address `which msgconvert`
use Email::Address;
my @from_addr = Email::Address->parse($mail->header('From'));
$ chronic apt source -qq libemail-outlook-message-perl
$ (cd libemail-outlook-message-perl*/ ; grep -r Email::Address )
Checking for repositories in /home/pabs/tmp-context-arXYMcHaIE ...
META.json:"Email::Address" : "0",
Makefile.PL: 'Email::Address' => '0',
script/msgconvert:use Email::Address;
script/msgconvert:my @from_addr =
Email::Address->parse($mail->header('From'));
Build.PL:'Email::Address' => '0',
META.yml: Email::Address: '0'
-- System Information:
Debian Release: bullseye/sid
APT prefers testing-debug
APT policy: (900, 'testing-debug'), (900, 'testing'), (800,
'unstable-debug'), (800, 'unstable'), (790, 'buildd-unstable'), (700,
'experimental-debug'), (700, 'experimental'), (690, 'buildd-experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 5.10.0-3-amd64 (SMP w/4 CPU threads)
Kernel taint flags: TAINT_WARN, TAINT_FIRMWARE_WORKAROUND
Locale: LANG=en_AU.utf8, LC_CTYPE=en_AU.utf8 (charmap=UTF-8), LANGUAGE=en_AU:en
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages libemail-outlook-message-perl depends on:
ii libemail-mime-contenttype-perl 1.026-1
ii libemail-mime-perl 1.949-1
ii libemail-sender-perl1.300035-1
ii libemail-simple-perl2.216-1
ii libio-all-perl 0.87-1
ii libio-string-perl 1.08-3.1
ii libole-storage-lite-perl0.20-1
ii perl5.32.1-2
libemail-outlook-message-perl recommends no packages.
libemail-outlook-message-perl suggests no packages.
-- no debconf information
--
bye,
pabs
https://wiki.debian.org/PaulWise
signature.asc
Description: This is a digitally signed message part
Processed: libemail-outlook-message-perl: msgconvert: missing dependency on libemail-message-perl
Processing control commands: > found -1 0.919-4~bpo10+1 Bug #983433 [libemail-outlook-message-perl] libemail-outlook-message-perl: msgconvert: missing dependency on libemail-message-perl Marked as found in versions libemail-outlook-message-perl/0.919-4~bpo10+1. -- 983433: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=983433 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#983091: xapian-core FTBFS on i386: test failure
On Tue, Feb 23, 2021 at 07:52:42PM +, Olly Betts wrote: >... > As you note, on i386 the test was only run with the SSE build before > the recent debian/rules modernisation, but that doesn't explain why > m68k now fails. Looking at older m68k logs, it seems the testsuite > wasn't being run, though I'm not seeing why not. >... m68k and sh4 are building with nocheck. nocheck handling was lost in the debian/rules rewrite. > Cheers, > Olly cu Adrian
Bug#983091: xapian-core FTBFS on i386: test failure
On Sat, Feb 20, 2021 at 07:24:52PM +, Olly Betts wrote: > On Fri, Feb 19, 2021 at 11:36:46AM +0200, Adrian Bunk wrote: > > With the old debian/rules the test was only run with > > the SSE build. > > > > If exact results are required and the x87 excess precision is unwanted, > > test with the non-SSE build can be fixed with: > > > > --- debian/rules.old2021-02-18 15:12:59.097207579 + > > +++ debian/rules2021-02-18 15:13:51.537168694 + > > @@ -51,6 +51,10 @@ > > > > export DEB_HOST_ARCH ?= $(shell dpkg-architecture -qDEB_HOST_ARCH) > > > > +ifneq (,$(filter $(DEB_HOST_ARCH), i386 m68k)) > > +export DEB_CXXFLAGS_MAINT_APPEND += -ffloat-store > > +endif > > + > > # For i386 and *-i386. > > ifeq ($(patsubst %-i386,i386,$(DEB_HOST_ARCH)), i386) > > XAPIAN_BUILD_SSE := 1 > > Thanks for the report, and for tracking this down to excess precision. > > The upstream code is meant to address excess precision in the small > number of places where it matters but I guess there's a newer instance > that hasn't been caught before, or a newer testcase uncovers an existing > problem (or perhaps newer GCC optimises differently and that's uncovered > this.) > > The SSE2 build will get used by more i386 systems, so the overhead > from -ffloat-store won't affect many there at least, but it is a bit of > heavy hammer. I'll take a look and see if I can fix this in a more > targetted way. If not applying this for bullseye seems reasonable. > Or we could change the tests back to run just for the SSE2 build for > now - in real world use exact results are rarely a requirement, but > performance often is. Investigating on i386 I found that all the failures apart from ordecay1 appear to actually be from the effects of excess precision on testcase code itself (and looking at the m68k log, ordecay1 actually passes there.) As you note, on i386 the test was only run with the SSE build before the recent debian/rules modernisation, but that doesn't explain why m68k now fails. Looking at older m68k logs, it seems the testsuite wasn't being run, though I'm not seeing why not. I think given where we are in the bullseye freeze the least invasive change here makes sense, which is to not run the tests for the i386 non-SSE build (they are run for the SSE build, which is the build which gets used on SSE2-capable machines, which is most of them) or on m68k (which isn't ideal, but it isn't a release architecture currently.) This essentially restores the testing situation to what it was prior to my modernisation of debian/rules in the previous upload. Longer term, sorting out ordecay1 and the testsuite issues (perhaps building the testsuite with -ffloat-store on affected platforms.) Cheers, Olly
Bug#983365: linphone-desktop: chat messages
Control: tags -1 help Dear David, > 1- chat messages (history) are not displayed when I launch the app, > although I can see they are in the .local/share/linphone/linphone.db > file (using sqliteb or sqlitebrowser); > > 2- when someone sends me a message, it 'pops' a notification with the > message text (even if I am in front of the app) but the message is not > displayed by the application itself, nor the little numbered circle that > appears (on the appimage 4.2.5 version, to compare) i the left panel, > in(on top of) the user 'entry', nor in the user chat 'room'. > > I also verified that the message isn't added in the chat_message_content > of the linphone.db table, and i can see the following 'trace' in the > terminal i used to launchh the app: > > [22:11:12:653][0x1ff9eb0][Info]components/sip-addresses/SipAddressesModel.cpp:485: > "Update (`sip:sender.na...@sip.linphone.org`, > `sip:my.n...@sip.linphone.org`) from chat message." Thanks for your report. Unfortunately I'm extremely swamped for the next couple of weeks. I have also never used the Chat feature. For this reason I'm tagging this bug as "help". Two short questions: In Bug#983369 a few minutes later you wrote the date in the history is wrong, although in this bug it reads like you cannot display the history at all. Which one is correct? Did you start a fresh linphone profile or is the sqlite database upgraded from an older version? Could you (for a test) move it away to have it recreated? I fully understand choosing an RC severity, but I'm at a loss debugging this and I lack the time to dig into it, so this bug might make linphone-desktop miss the Bullseye release unless someone steps up to debug this. Bernhard
Processed: Re: Bug#983365: linphone-desktop: chat messages
Processing control commands: > tags -1 help Bug #983365 [linphone-desktop] linphone-desktop: chat messages Added tag(s) help. -- 983365: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=983365 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#980809: rmatrix: breaks autopkgtest of r-cran-glmmtmb on s390x
Graham, Martin, So I logged back onto the s390x box we can access. Matrix 1.13-2 does fail the factorization test when doing _R_CHECK_FORCE_SUGGESTS_=false R CMD check --no-manual \ --no-vignettes Matrix_1.3-2.tar.gz and Matrix 1.2-18 passes it. So Graham was right all-along that there was something in the 1.3-0 transition. Now, is that ultimately Matrix or the underlying QR code it uses? I don't know. But it reasonably easy for me to get access (and install the required packages) so once Martin has time to think through an approach or two I can likely test it. Best, Dirk -- https://dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org
Bug#983091: marked as done (xapian-core FTBFS on i386: test failure)
Your message dated Tue, 23 Feb 2021 19:33:39 + with message-id and subject line Bug#983091: fixed in xapian-core 1.4.18-3 has caused the Debian Bug report #983091, regarding xapian-core FTBFS on i386: test failure 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.) -- 983091: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=983091 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: xapian-core Version: 1.4.18-2 Severity: serious Tags: ftbfs patch https://buildd.debian.org/status/fetch.php?pkg=xapian-core&arch=i386&ver=1.4.18-2&stamp=1613459435&raw=0 ... 1 of 4 tests failed Please report to https://xapian.org/bugs make[6]: *** [Makefile:1070: check-TESTS] Error 1 With the old debian/rules the test was only run with the SSE build. If exact results are required and the x87 excess precision is unwanted, test with the non-SSE build can be fixed with: --- debian/rules.old2021-02-18 15:12:59.097207579 + +++ debian/rules2021-02-18 15:13:51.537168694 + @@ -51,6 +51,10 @@ export DEB_HOST_ARCH ?= $(shell dpkg-architecture -qDEB_HOST_ARCH) +ifneq (,$(filter $(DEB_HOST_ARCH), i386 m68k)) +export DEB_CXXFLAGS_MAINT_APPEND += -ffloat-store +endif + # For i386 and *-i386. ifeq ($(patsubst %-i386,i386,$(DEB_HOST_ARCH)), i386) XAPIAN_BUILD_SSE := 1 --- End Message --- --- Begin Message --- Source: xapian-core Source-Version: 1.4.18-3 Done: Olly Betts We believe that the bug you reported is fixed in the latest version of xapian-core, 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 983...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Olly Betts (supplier of updated xapian-core 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, 24 Feb 2021 07:33:41 +1300 Source: xapian-core Architecture: source Version: 1.4.18-3 Distribution: unstable Urgency: medium Maintainer: Olly Betts Changed-By: Olly Betts Closes: 983091 Changes: xapian-core (1.4.18-3) unstable; urgency=medium . * debian/rules: Workaround testcase sensitivity to excess precision by skipping the testsuite on m68k and in the non-SSE build on i386. (Closes: #983091) Checksums-Sha1: acabdb9a43dd5982229819dafdba74929468b2cd 2397 xapian-core_1.4.18-3.dsc 6ce59b01806f52a317346b4fe4d8245286ff8dfe 19276 xapian-core_1.4.18-3.debian.tar.xz 1256485d1f2cd0a37a099d14b4f5b3e5c1514730 7882 xapian-core_1.4.18-3_amd64.buildinfo Checksums-Sha256: 0a93cf2f5e8d43133ba2dcaa5934fda38ecfe03e1af0305a59bf89dc31c5a9ad 2397 xapian-core_1.4.18-3.dsc 3d6539cd04b2e2e15243f588befd59d7106eaf60b78a2b339091a07bdde6b2a4 19276 xapian-core_1.4.18-3.debian.tar.xz e4aacc16d7a66dc3dd0838733ebcf03455852c0cbb4db1b7996ca15ab2c2075c 7882 xapian-core_1.4.18-3_amd64.buildinfo Files: 3641b7322a51c796fc8052eb673646ea 2397 libs optional xapian-core_1.4.18-3.dsc 1292be43d35fc86a14899f30eba995b9 19276 libs optional xapian-core_1.4.18-3.debian.tar.xz e0c7e3f6f84d9eb8b913f3cf207d03bc 7882 libs optional xapian-core_1.4.18-3_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEECOJAD/f+j+3jrLUoGBR7BzutKwcFAmA1VGkACgkQGBR7Bzut Kwe4wxAAqayEMmX7KtdIHOxW7euZ/d+l5eMnFAlitE126EOb8lOKRhoewLv1RFDq vituzseLoxV/ZQJGNfBCpFzfWrB4l8c7hKoeE/DQ5jbNTLkxxAhBqJMlL73cQ66a QMguOQYffs/9GyCAo2qUAxoVkR77+sdfUiDspT9abjntRRZNd2yY0x6Iigrf+Gd3 cZbvdfZFM24wCC9DVNhp7UdjS7KUpy0WAo1KJ1iDIcNUdgX/WipKlYMFooDy8Z/G pqeuoWlFi7zF5h9kRsX3dEISDS0JfPldQliLHDR1/evWM5V0PEjBDhwQsdOrbTiG 7JpDo7lpTUlDfrhhR9kuIX/YFF3OQKo11/EEBDfyvvF4ZewvRNj08hmGeiu7z1TO cEDjHnSBxi03GlGNbffMUwwSeL62Hi5fREq97XapbXXx7r4KkcOCmklQWbVO+ofk F4VrxREyBz0+WWdlYxjRvhnm7bL1OM05Ncxd95CBC4c+2yEWXGdGPqe+/6JZT4bF rQNyD/y+Ej8ALL3WnS6f9mMAVS7MD2Art/thqIZehR6Gbv3qVhTG+XBdTIoCiQUH Zd2D3bKXlUhYNdjb772p/5FE6lLnhk2429NAtKFb2ogvMPGJLOvuFrYw07VH8SQl dDG1PdM00FdmXL7vH4aWJUjaFrxkCLx4EFO5adIPOTVhq2arE4g= =I5GA -END PGP SIGNATURE End Message ---
Processed: severity of 982530 is serious
Processing commands for cont...@bugs.debian.org: > severity 982530 serious Bug #982530 [libpam-modules] libpam-modules: unable to login when using pam_tally2 after upgrade to libpam-modules >1.4.0 Severity set to 'serious' from 'normal' > thanks Stopping processing here. Please contact me if you need assistance. -- 982530: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=982530 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#972339: armhf: hpcups crashes with free() invalid pointer for some printers
Processing control commands: > found -1 3.21.2+dfsg1-1 Bug #972339 [printer-driver-hpcups] armhf: hpcups crashes with free() invalid pointer for some printers Marked as found in versions hplip/3.21.2+dfsg1-1. -- 972339: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972339 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#972339: armhf: hpcups crashes with free() invalid pointer for some printers
Control: found -1 3.21.2+dfsg1-1 Hello there Bernhard, (CC'ing d-arm for help) Sadly, I could confirm on a local armhf QEMU instance that this serious bug is still present, in sid and bullseye; the steps in https://bugs.debian.org/972339#10 still apply and trigger the SIGABRT. Although I understand what you're saying in theoretical terms here, I'm completely at loss to propose a patch: I'm way over my head with my 10+years- old C and gdb competences. In the absence of any interest from upstream, I need help to fix hplip on armhf. (Note that amd64 is apparently also affected; see #974828) Whoever willing to help; if you need anything from me (as maintainer), please ask! I'm happy to explain my use of git-debrebase, or provide a different git history if it helps, I mostly don't want to be in the way of a fix! Humbly, OdyX Le samedi, 24 octobre 2020, 14.05:04 h CET Bernhard Übelacker a écrit : > I could reproduce this issue too. > > Attached is a valgrind run showing one invalid write > and a gdb session showing the issue. > > It looks like mallocs management data, which resides in the 8 bytes > before a returned pointer, gets overwritten and therefore > the free fails because "mchunk_size" is then 0. > > Kind regards, > Bernhard > > > Old value = 6057 > New value = 0 > __memcpy_neon () at ../sysdeps/arm/armv7/multiarch/memcpy_impl.S:295 > warning: Source file is more recent than executable. > 295 tst count, #4 > 1: compressBuf = named `this'> 2: /x *(int*)(0x7f5f43e8-4) = 0x0 > (gdb) bt > #0 __memcpy_neon () at ../sysdeps/arm/armv7/multiarch/memcpy_impl.S:295 > #1 0x7f55b8d2 in memcpy (__len=379, __src=, > __dest=) at > /usr/include/arm-linux-gnueabihf/bits/string_fortified.h:34 #2 > Mode9::Process (this=0x7f5e0e70, input=0x7f5e0e84) at > prnt/hpcups/Mode9.cpp:405 #3 0x7f562de0 in Pipeline::Process > (raster=, this=0x7f5d7340) at prnt/hpcups/Pipeline.cpp:79 #4 > Pipeline::Execute (this=0x7f5d7340, InputRaster=) at > prnt/hpcups/Pipeline.cpp:79 #5 0x7f562e02 in Pipeline::Execute > (this=0x7f5e6b88, InputRaster=) at > prnt/hpcups/Pipeline.cpp:83 #6 0x7f562e02 in Pipeline::Execute > (this=0x7f5e6b70, InputRaster=) at > prnt/hpcups/Pipeline.cpp:83 #7 0x7f55a20a in > HPCupsFilter::processRasterData (this=0x7f5b87c4 , > cups_raster=) at prnt/hpcups/HPCupsFilter.cpp:766 #8 > 0x7f55a6ee in HPCupsFilter::StartPrintJob (this=0x7f5b87c4 , > argc=6, argv=0xbefff7b4) at prnt/hpcups/HPCupsFilter.cpp:584 #9 0xb6bd9a20 > in __libc_start_main (main=0x7f5587d1 , argc=6, > argv=0xbefff7b4, init=, fini=0x7f56ed5d <__libc_csu_fini>, > rtld_fini=0xb6fe1075 <_dl_fini>, stack_end=0xbefff7b4) at libc-start.c:308 > #10 0x7f55889c in _start () at prnt/hpcups/HPCupsFilter.cpp:919 > > > https://sources.debian.org/src/hplip/3.21.2+dfsg1-1/prnt/hpcups/Mode9.cpp/#L > 405 -- OdyX signature.asc Description: This is a digitally signed message part.
Bug#978316: marked as done (libbio-db-embl-perl: FTBFS: dh_auto_test: error: make -j4 test TEST_VERBOSE=1 returned exit code 2)
Your message dated Tue, 23 Feb 2021 18:33:43 + with message-id and subject line Bug#978316: fixed in libbio-db-embl-perl 1.7.4-4 has caused the Debian Bug report #978316, regarding libbio-db-embl-perl: FTBFS: dh_auto_test: error: make -j4 test TEST_VERBOSE=1 returned exit code 2 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.) -- 978316: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=978316 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libbio-db-embl-perl Version: 1.7.4-2 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20201226 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > PERL_DL_NONLAZY=1 "/usr/bin/perl" "-MExtUtils::Command::MM" "-MTest::Harness" > "-e" "undef *Test::Harness::Switches; test_harness(1, 'blib/lib', > 'blib/arch')" t/*.t > t/00-compile.t ... > 1..1 > ok 1 - Bio/DB/EMBL.pm loaded ok > ok > t/author-mojibake.t .. skipped: these tests are for testing by the author > t/author-pod-coverage.t .. skipped: these tests are for testing by the author > t/author-pod-syntax.t skipped: these tests are for testing by the author > > - EXCEPTION - > MSG: EMBL stream with no ID. Not embl in my book > STACK Bio::SeqIO::embl::next_seq /usr/share/perl5/Bio/SeqIO/embl.pm:205 > STACK Bio::DB::WebDBSeqI::get_Seq_by_acc > /usr/share/perl5/Bio/DB/WebDBSeqI.pm:202 > STACK toplevel t/EMBL.t:27 > - > > # Looks like your test exited with 255 just after 2. > t/EMBL.t . > 1..16 > ok 1 - use Bio::DB::EMBL; > ok 2 > Dubious, test returned 255 (wstat 65280, 0xff00) > Failed 14/16 subtests > > Test Summary Report > --- > t/EMBL.t (Wstat: 65280 Tests: 2 Failed: 0) > Non-zero exit status: 255 > Parse errors: Bad plan. You planned 16 tests but ran 2. > Files=5, Tests=3, 1 wallclock secs ( 0.02 usr 0.00 sys + 0.29 cusr 0.02 > csys = 0.33 CPU) > Result: FAIL > Failed 1/5 test programs. 0/3 subtests failed. > make[1]: *** [Makefile:853: test_dynamic] Error 255 > make[1]: Leaving directory '/<>' > dh_auto_test: error: make -j4 test TEST_VERBOSE=1 returned exit code 2 The full build log is available from: http://qa-logs.debian.net/2020/12/26/libbio-db-embl-perl_1.7.4-2_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please marking it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with me so that we can identify if something relevant changed in the meantime. About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures. --- End Message --- --- Begin Message --- Source: libbio-db-embl-perl Source-Version: 1.7.4-4 Done: Étienne Mollier We believe that the bug you reported is fixed in the latest version of libbio-db-embl-perl, 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 978...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Étienne Mollier (supplier of updated libbio-db-embl-perl 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, 23 Feb 2021 18:22:06 +0100 Source: libbio-db-embl-perl Architecture: source Version: 1.7.4-4 Distribution: unstable Urgency: medium Maintainer: Debian Med Packaging Team Changed-By: Étienne Mollier Closes: 978316 Changes: libbio-db-embl-perl (1.7.4-4) unstable; urgency=medium . * Team upload. * d/rules: make sure tests remain offline Closes: #978316 * explicit offline autodep8 perl autopkgtest; this is required to mark the smoke test as "superficial", since there are no offline tests done by this autopkgtest. Checksums-Sha1: 43767ab9d
Bug#983379: linux uml segfault
On 23/02/2021 17:26, Ritesh Raj Sarraf wrote: Added the debian bug report in CC. On Tue, 2021-02-23 at 17:19 +, Anton Ivanov wrote: The current Debian user-mode-linux package in unstable is based on the 5.10.5 stable source which includes the mentioned patch, but is still causing an error for some users. After updating the tree to 5.10.5 and applying all Debian patches from the package, I cannot reproduce the bug. I am running it on 5.10, 5.2 and 4.19 hosts with the same parameters without issues. Hosts are all up to date Debian 10.8 and so is the UML userspace. Did you mean 5.10, 5.2 and 4.19 (UML) guests ? No. Hosts. I have several 6core/12thread Ryzens which are used for development testing. They all use identical userspace with the sole difference being the kernel. They all use a selection of 5.x because 4.19 does not support the hardware properly. The 4.19 testing is done on my old "test farm" which is all A8s and Athlon X760. We've seen this happen on Debian Testing and Unstable Host (of which the former would soon be the next stable i.e. Debian Bullseye). In our tests, when running the same linux uml binary (5.10) on a Debian Stable Host, it is working fine. OK. I will upgrade one of my systems to Debian testing to try to reproduce this. -- Anton R. Ivanov https://www.kot-begemot.co.uk/
Bug#980809: rmatrix: breaks autopkgtest of r-cran-glmmtmb on s390x
On Tue, Feb 23, 2021 at 3:17 PM Graham Inggs wrote: > > Hi Dirk > > On Tue, 23 Feb 2021 at 15:34, Dirk Eddelbuettel wrote: > > If it were me I would turn off the autopkgtest in r-cran-glmmtmb (maybe just > > on s390x) and move on. > > That would just be hiding the problem. > > If it is the kind of bug I described previously, it shows up more > often on big-endian systems, but it is still present on little-endian > systems, and will show up in the right (wrong) conditions. > You may be right on spot, Graham, or not.. Currently I don't have time to investigate ... also I *have* been a bit puzzled by therankMatrix(*, "qr") -- Matrix-only -- discrepancy that Dirk found. I agree it *would* be good to dig further, but that needs a chunk of dedicated time (and "free head") which I don't have for now. Apropos 'rabbit hole' : Isn't the origin -- long before the Matrix movie -- in Lewis Carrol's "Alice in Wonderland" (1865 !!): https://en.wikipedia.org/wiki/White_Rabbit ?? Best, Martin -- Martin Maechler, Seminar fuer Statistik, ETH Zurich
Bug#923500: snapd: non-classic snap not confined
Just a quick update - we looked at this and we think the apparmor support in Debian is sufficient to enable it in snaps by default. This is being worked on in https://github.com/snapcore/snapd/pull/9936 and once that lands I will upload to Debian. The goal is within this week. In addition to the spread tests we manually validated some key snaps and did not see regressions. With that upload we can close this bug because snaps are confined on Debian. Snaps will see the read only version of the "base" snap (e.g. core or core20) and only what access is granted via snap "interfaces". Cheers, Michael
Bug#982719: firehol: FTBFS: dh_auto_test: error: make -j1 check VERBOSE=1 returned exit code 2
I just noticed that firehol has no autopkgtests yet, but since ci.debian.net can run those under LXC/qemu instead of chroot this would allow for the test suite to run. It might however be a bit of a challenge to set that up at home if troubleshooting is needed. Copying the one for root-unittests from firewalld seems like a good starting point: https://salsa.debian.org/utopia-team/firewalld/-/blob/debian/master/debian/tests/control The maintainer apparently faced a similar problem and disabled the test suite for buildd builds: https://salsa.debian.org/utopia-team/firewalld/-/commit/d24a8b8b5b29708c811bcad4b9885d1665875aca Maybe he'll be willing to help with setting this up. The autopkgtest probably will have to specify "needs-root" to set unprivileged_userns_clone=1 (unless the VM image already has that set up), but the test suite itself needn't run as root. Regards, Dennis.
Bug#983379: linux uml segfault
Added the debian bug report in CC. On Tue, 2021-02-23 at 17:19 +, Anton Ivanov wrote: > > The current Debian user-mode-linux package in unstable is based on > > the 5.10.5 stable source which includes the mentioned patch, but is > > still causing an error for some users. > > After updating the tree to 5.10.5 and applying all Debian patches > from the package, I cannot reproduce the bug. > > I am running it on 5.10, 5.2 and 4.19 hosts with the same parameters > without issues. Hosts are all up to date Debian 10.8 and so is the > UML userspace. > Did you mean 5.10, 5.2 and 4.19 (UML) guests ? We've seen this happen on Debian Testing and Unstable Host (of which the former would soon be the next stable i.e. Debian Bullseye). In our tests, when running the same linux uml binary (5.10) on a Debian Stable Host, it is working fine. -- Ritesh Raj Sarraf | http://people.debian.org/~rrs Debian - The Universal Operating System signature.asc Description: This is a digitally signed message part
Bug#980684: marked as done (libfwupd-dev: missing dep causes rdeps to FTBFS)
Your message dated Tue, 23 Feb 2021 16:33:33 + with message-id and subject line Bug#980691: fixed in fwupd 1.5.7-1 has caused the Debian Bug report #980691, regarding libfwupd-dev: missing dep causes rdeps to FTBFS 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.) -- 980691: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=980691 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: gnome-firmware Version: 3.36.0-1 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20210120 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > dpkg-buildpackage > - > > Command: dpkg-buildpackage -us -uc -sa -rfakeroot > dpkg-buildpackage: info: source package gnome-firmware > dpkg-buildpackage: info: source version 3.36.0-1 > dpkg-buildpackage: info: source distribution unstable > dpkg-buildpackage: info: source changed by Laurent Bigonville > > dpkg-source --before-build . > dpkg-buildpackage: info: host architecture amd64 > debian/rules clean > dh clean --with gnome >dh_gnome_clean >dh_clean > dpkg-source -b . > dpkg-source: info: using source format '3.0 (quilt)' > dpkg-source: info: building gnome-firmware using existing > ./gnome-firmware_3.36.0.orig.tar.xz > dpkg-source: info: building gnome-firmware in > gnome-firmware_3.36.0-1.debian.tar.xz > dpkg-source: info: building gnome-firmware in gnome-firmware_3.36.0-1.dsc > debian/rules binary > dh binary --with gnome >dh_update_autotools_config >dh_autoreconf >dh_auto_configure > cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 meson .. > --wrap-mode=nodownload --buildtype=plain --prefix=/usr --sysconfdir=/etc > --localstatedir=/var --libdir=lib/x86_64-linux-gnu > The Meson build system > Version: 0.56.2 > Source dir: /<> > Build dir: /<>/obj-x86_64-linux-gnu > Build type: native build > Project name: gnome-firmware > Project version: 3.36.0 > Using 'CFLAGS' from environment with value: '-g -O2 > -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat > -Werror=format-security' > Using 'LDFLAGS' from environment with value: '-Wl,-z,relro' > Using 'CPPFLAGS' from environment with value: '-Wdate-time > -D_FORTIFY_SOURCE=2' > C compiler for the host machine: cc (gcc 10.2.1 "cc (Debian 10.2.1-6) 10.2.1 > 20210110") > C linker for the host machine: cc ld.bfd 2.35.1 > Using 'CFLAGS' from environment with value: '-g -O2 > -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat > -Werror=format-security' > Using 'LDFLAGS' from environment with value: '-Wl,-z,relro' > Using 'CPPFLAGS' from environment with value: '-Wdate-time > -D_FORTIFY_SOURCE=2' > Host machine cpu family: x86_64 > Host machine cpu: x86_64 > Compiler for C supports arguments -Waggregate-return: YES > Compiler for C supports arguments -Warray-bounds: YES > Compiler for C supports arguments -Wcast-align: YES > Compiler for C supports arguments -Wclobbered: YES > Compiler for C supports arguments -Wdeclaration-after-statement: YES > Compiler for C supports arguments -Wempty-body: YES > Compiler for C supports arguments -Wextra: YES > ../meson.build:60: WARNING: Consider using the built-in warning_level option > instead of using "-Wextra". > Compiler for C supports arguments -Wformat=2: YES > Compiler for C supports arguments -Wformat-security: YES > Compiler for C supports arguments -Wformat-signedness: YES > Compiler for C supports arguments -Wignored-qualifiers: YES > Compiler for C supports arguments -Wimplicit-function-declaration: YES > Compiler for C supports arguments -Winit-self: YES > Compiler for C supports arguments -Winline: YES > Compiler for C supports arguments -Wmissing-declarations: YES > Compiler for C supports arguments -Wmissing-format-attribute: YES > Compiler for C supports arguments -Wmissing-include-dirs: YES > Compiler for C supports arguments -Wmissing-noreturn: YES > Compiler for C supports arguments -Wmissing-parameter-type: YES > Compiler for C supports arguments -Wmissing-prototypes: YES > Compiler for C supports arguments -Wnested-externs: YES > Compiler for C supports arguments -Wno-discarded-qualifiers: YES > Compiler for C supports arguments -Wno-missing-field-initializers: YES > Compiler for C supports arguments -Wno-strict-aliasing: YES > Compiler for C supports arguments -Wno-suggest-attribute=format: YES > Compiler for C supports arguments -Wno-unused-parameter: YES > Compiler for C supports arguments -Wno-cast-function-type: YES > Compiler for C supports a
Bug#980691: marked as done (libfwupd-dev: missing dep causes rdeps to FTBFS)
Your message dated Tue, 23 Feb 2021 16:33:33 + with message-id and subject line Bug#980691: fixed in fwupd 1.5.7-1 has caused the Debian Bug report #980691, regarding libfwupd-dev: missing dep causes rdeps to FTBFS 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.) -- 980691: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=980691 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: gnome-software Version: 3.38.0-3 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20210120 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > dh_auto_configure -- -Dgnome_desktop=true -Dodrs=true -Dostree=false > -Dpackagekit=true -Dpackagekit_autoremove=true -Drpm_ostree=false > -Dubuntu_reviews=false -Dfwupd=false -Dflatpak=false -Dgudev=false > -Dmalcontent=false -Dvalgrind=false -Dflatpak=true -Dmalcontent=true > -Dgudev=true -Dfwupd=true -Dsnap=true -Dvalgrind=true > cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 meson .. > --wrap-mode=nodownload --buildtype=plain --prefix=/usr --sysconfdir=/etc > --localstatedir=/var --libdir=lib/x86_64-linux-gnu -Dgnome_desktop=true > -Dodrs=true -Dostree=false -Dpackagekit=true -Dpackagekit_autoremove=true > -Drpm_ostree=false -Dubuntu_reviews=false -Dfwupd=false -Dflatpak=false > -Dgudev=false -Dmalcontent=false -Dvalgrind=false -Dflatpak=true > -Dmalcontent=true -Dgudev=true -Dfwupd=true -Dsnap=true -Dvalgrind=true > The Meson build system > Version: 0.56.2 > Source dir: /<> > Build dir: /<>/obj-x86_64-linux-gnu > Build type: native build > WARNING: Unknown options: "ostree, ubuntu_reviews" > The value of new options can be set with: > meson setup --reconfigure -Dnew_option=new_value ... > Project name: gnome-software > Project version: 3.38.0 > Using 'CFLAGS' from environment with value: '-g -O2 > -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat > -Werror=format-security' > Using 'LDFLAGS' from environment with value: '-Wl,-z,relro -Wl,-z,now -Wl,-O1 > -Wl,--as-needed' > Using 'CPPFLAGS' from environment with value: '-Wdate-time > -D_FORTIFY_SOURCE=2' > C compiler for the host machine: cc (gcc 10.2.1 "cc (Debian 10.2.1-6) 10.2.1 > 20210110") > C linker for the host machine: cc ld.bfd 2.35.1 > Using 'CFLAGS' from environment with value: '-g -O2 > -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat > -Werror=format-security' > Using 'LDFLAGS' from environment with value: '-Wl,-z,relro -Wl,-z,now -Wl,-O1 > -Wl,--as-needed' > Using 'CPPFLAGS' from environment with value: '-Wdate-time > -D_FORTIFY_SOURCE=2' > Host machine cpu family: x86_64 > Host machine cpu: x86_64 > Compiler for C supports arguments -fstack-protector-strong: YES > Compiler for C supports arguments -Waggregate-return: YES > Compiler for C supports arguments -Warray-bounds: YES > Compiler for C supports arguments -Wcast-align: YES > Compiler for C supports arguments -Wclobbered: YES > Compiler for C supports arguments -Wdeclaration-after-statement: YES > Compiler for C supports arguments -Wempty-body: YES > Compiler for C supports arguments -Wextra: YES > ../meson.build:73: WARNING: Consider using the built-in warning_level option > instead of using "-Wextra". > Compiler for C supports arguments -Wformat=2: YES > Compiler for C supports arguments -Wformat-nonliteral: YES > Compiler for C supports arguments -Wformat-security: YES > Compiler for C supports arguments -Wformat-signedness: YES > Compiler for C supports arguments -Wignored-qualifiers: YES > Compiler for C supports arguments -Wimplicit-function-declaration: YES > Compiler for C supports arguments -Werror=implicit-function-declaration: YES > Compiler for C supports arguments -Winit-self: YES > Compiler for C supports arguments -Winline: YES > Compiler for C supports arguments -Wmissing-declarations: YES > Compiler for C supports arguments -Wmissing-format-attribute: YES > Compiler for C supports arguments -Wmissing-include-dirs: YES > Compiler for C supports arguments -Wmissing-noreturn: YES > Compiler for C supports arguments -Wmissing-parameter-type: YES > Compiler for C supports arguments -Wmissing-prototypes: YES > Compiler for C supports arguments -Wnested-externs: YES > Compiler for C supports arguments -Werror=nested-externs: YES > Compiler for C supports arguments -Wno-discarded-qualifiers: YES > Compiler for C supports arguments -Wno-missing-field-initializers: YES > Compiler for C supports arguments -Wno-strict-
Bug#980684: marked as done (libfwupd-dev: missing dep causes rdeps to FTBFS)
Your message dated Tue, 23 Feb 2021 16:33:33 + with message-id and subject line Bug#980684: fixed in fwupd 1.5.7-1 has caused the Debian Bug report #980684, regarding libfwupd-dev: missing dep causes rdeps to FTBFS 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.) -- 980684: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=980684 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: gnome-firmware Version: 3.36.0-1 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20210120 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > dpkg-buildpackage > - > > Command: dpkg-buildpackage -us -uc -sa -rfakeroot > dpkg-buildpackage: info: source package gnome-firmware > dpkg-buildpackage: info: source version 3.36.0-1 > dpkg-buildpackage: info: source distribution unstable > dpkg-buildpackage: info: source changed by Laurent Bigonville > > dpkg-source --before-build . > dpkg-buildpackage: info: host architecture amd64 > debian/rules clean > dh clean --with gnome >dh_gnome_clean >dh_clean > dpkg-source -b . > dpkg-source: info: using source format '3.0 (quilt)' > dpkg-source: info: building gnome-firmware using existing > ./gnome-firmware_3.36.0.orig.tar.xz > dpkg-source: info: building gnome-firmware in > gnome-firmware_3.36.0-1.debian.tar.xz > dpkg-source: info: building gnome-firmware in gnome-firmware_3.36.0-1.dsc > debian/rules binary > dh binary --with gnome >dh_update_autotools_config >dh_autoreconf >dh_auto_configure > cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 meson .. > --wrap-mode=nodownload --buildtype=plain --prefix=/usr --sysconfdir=/etc > --localstatedir=/var --libdir=lib/x86_64-linux-gnu > The Meson build system > Version: 0.56.2 > Source dir: /<> > Build dir: /<>/obj-x86_64-linux-gnu > Build type: native build > Project name: gnome-firmware > Project version: 3.36.0 > Using 'CFLAGS' from environment with value: '-g -O2 > -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat > -Werror=format-security' > Using 'LDFLAGS' from environment with value: '-Wl,-z,relro' > Using 'CPPFLAGS' from environment with value: '-Wdate-time > -D_FORTIFY_SOURCE=2' > C compiler for the host machine: cc (gcc 10.2.1 "cc (Debian 10.2.1-6) 10.2.1 > 20210110") > C linker for the host machine: cc ld.bfd 2.35.1 > Using 'CFLAGS' from environment with value: '-g -O2 > -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat > -Werror=format-security' > Using 'LDFLAGS' from environment with value: '-Wl,-z,relro' > Using 'CPPFLAGS' from environment with value: '-Wdate-time > -D_FORTIFY_SOURCE=2' > Host machine cpu family: x86_64 > Host machine cpu: x86_64 > Compiler for C supports arguments -Waggregate-return: YES > Compiler for C supports arguments -Warray-bounds: YES > Compiler for C supports arguments -Wcast-align: YES > Compiler for C supports arguments -Wclobbered: YES > Compiler for C supports arguments -Wdeclaration-after-statement: YES > Compiler for C supports arguments -Wempty-body: YES > Compiler for C supports arguments -Wextra: YES > ../meson.build:60: WARNING: Consider using the built-in warning_level option > instead of using "-Wextra". > Compiler for C supports arguments -Wformat=2: YES > Compiler for C supports arguments -Wformat-security: YES > Compiler for C supports arguments -Wformat-signedness: YES > Compiler for C supports arguments -Wignored-qualifiers: YES > Compiler for C supports arguments -Wimplicit-function-declaration: YES > Compiler for C supports arguments -Winit-self: YES > Compiler for C supports arguments -Winline: YES > Compiler for C supports arguments -Wmissing-declarations: YES > Compiler for C supports arguments -Wmissing-format-attribute: YES > Compiler for C supports arguments -Wmissing-include-dirs: YES > Compiler for C supports arguments -Wmissing-noreturn: YES > Compiler for C supports arguments -Wmissing-parameter-type: YES > Compiler for C supports arguments -Wmissing-prototypes: YES > Compiler for C supports arguments -Wnested-externs: YES > Compiler for C supports arguments -Wno-discarded-qualifiers: YES > Compiler for C supports arguments -Wno-missing-field-initializers: YES > Compiler for C supports arguments -Wno-strict-aliasing: YES > Compiler for C supports arguments -Wno-suggest-attribute=format: YES > Compiler for C supports arguments -Wno-unused-parameter: YES > Compiler for C supports arguments -Wno-cast-function-type: YES > Compiler for C supports a
Bug#980691: marked as done (libfwupd-dev: missing dep causes rdeps to FTBFS)
Your message dated Tue, 23 Feb 2021 16:33:33 + with message-id and subject line Bug#980684: fixed in fwupd 1.5.7-1 has caused the Debian Bug report #980684, regarding libfwupd-dev: missing dep causes rdeps to FTBFS 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.) -- 980684: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=980684 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: gnome-software Version: 3.38.0-3 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20210120 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > dh_auto_configure -- -Dgnome_desktop=true -Dodrs=true -Dostree=false > -Dpackagekit=true -Dpackagekit_autoremove=true -Drpm_ostree=false > -Dubuntu_reviews=false -Dfwupd=false -Dflatpak=false -Dgudev=false > -Dmalcontent=false -Dvalgrind=false -Dflatpak=true -Dmalcontent=true > -Dgudev=true -Dfwupd=true -Dsnap=true -Dvalgrind=true > cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 meson .. > --wrap-mode=nodownload --buildtype=plain --prefix=/usr --sysconfdir=/etc > --localstatedir=/var --libdir=lib/x86_64-linux-gnu -Dgnome_desktop=true > -Dodrs=true -Dostree=false -Dpackagekit=true -Dpackagekit_autoremove=true > -Drpm_ostree=false -Dubuntu_reviews=false -Dfwupd=false -Dflatpak=false > -Dgudev=false -Dmalcontent=false -Dvalgrind=false -Dflatpak=true > -Dmalcontent=true -Dgudev=true -Dfwupd=true -Dsnap=true -Dvalgrind=true > The Meson build system > Version: 0.56.2 > Source dir: /<> > Build dir: /<>/obj-x86_64-linux-gnu > Build type: native build > WARNING: Unknown options: "ostree, ubuntu_reviews" > The value of new options can be set with: > meson setup --reconfigure -Dnew_option=new_value ... > Project name: gnome-software > Project version: 3.38.0 > Using 'CFLAGS' from environment with value: '-g -O2 > -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat > -Werror=format-security' > Using 'LDFLAGS' from environment with value: '-Wl,-z,relro -Wl,-z,now -Wl,-O1 > -Wl,--as-needed' > Using 'CPPFLAGS' from environment with value: '-Wdate-time > -D_FORTIFY_SOURCE=2' > C compiler for the host machine: cc (gcc 10.2.1 "cc (Debian 10.2.1-6) 10.2.1 > 20210110") > C linker for the host machine: cc ld.bfd 2.35.1 > Using 'CFLAGS' from environment with value: '-g -O2 > -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat > -Werror=format-security' > Using 'LDFLAGS' from environment with value: '-Wl,-z,relro -Wl,-z,now -Wl,-O1 > -Wl,--as-needed' > Using 'CPPFLAGS' from environment with value: '-Wdate-time > -D_FORTIFY_SOURCE=2' > Host machine cpu family: x86_64 > Host machine cpu: x86_64 > Compiler for C supports arguments -fstack-protector-strong: YES > Compiler for C supports arguments -Waggregate-return: YES > Compiler for C supports arguments -Warray-bounds: YES > Compiler for C supports arguments -Wcast-align: YES > Compiler for C supports arguments -Wclobbered: YES > Compiler for C supports arguments -Wdeclaration-after-statement: YES > Compiler for C supports arguments -Wempty-body: YES > Compiler for C supports arguments -Wextra: YES > ../meson.build:73: WARNING: Consider using the built-in warning_level option > instead of using "-Wextra". > Compiler for C supports arguments -Wformat=2: YES > Compiler for C supports arguments -Wformat-nonliteral: YES > Compiler for C supports arguments -Wformat-security: YES > Compiler for C supports arguments -Wformat-signedness: YES > Compiler for C supports arguments -Wignored-qualifiers: YES > Compiler for C supports arguments -Wimplicit-function-declaration: YES > Compiler for C supports arguments -Werror=implicit-function-declaration: YES > Compiler for C supports arguments -Winit-self: YES > Compiler for C supports arguments -Winline: YES > Compiler for C supports arguments -Wmissing-declarations: YES > Compiler for C supports arguments -Wmissing-format-attribute: YES > Compiler for C supports arguments -Wmissing-include-dirs: YES > Compiler for C supports arguments -Wmissing-noreturn: YES > Compiler for C supports arguments -Wmissing-parameter-type: YES > Compiler for C supports arguments -Wmissing-prototypes: YES > Compiler for C supports arguments -Wnested-externs: YES > Compiler for C supports arguments -Werror=nested-externs: YES > Compiler for C supports arguments -Wno-discarded-qualifiers: YES > Compiler for C supports arguments -Wno-missing-field-initializers: YES > Compiler for C supports arguments -Wno-strict-
Processed: python3-scipy: scipy 1.6.1 changed API for sparse (COO) matrices
Processing control commands: > forwarded -1 https://github.com/scipy/scipy/issues/13585 Bug #983404 [python3-scipy] python3-scipy: scipy 1.6.1 changed API for sparse (COO) matrices Set Bug forwarded-to-address to 'https://github.com/scipy/scipy/issues/13585'. > affects -1 src:pandas src:qutip Bug #983404 [python3-scipy] python3-scipy: scipy 1.6.1 changed API for sparse (COO) matrices Added indication that 983404 affects src:pandas and src:qutip -- 983404: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=983404 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#983404: python3-scipy: scipy 1.6.1 changed API for sparse (COO) matrices
Package: python3-scipy Version: 1.6.1-1 Severity: serious Tags: upstream Justification: FTBFS Control: forwarded -1 https://github.com/scipy/scipy/issues/13585 Control: affects -1 src:pandas src:qutip scipy 1.6.1 marketed itself as "bug-fix only", but in fact introduced a change in the API handling sparse matrices with COO constructor. Reported upstream at https://github.com/scipy/scipy/issues/13585 with PR proposed at https://github.com/scipy/scipy/pull/13586 This causes pandas and qutip test to fail, so treating as FTBFS (severity serious). scipy 1.6.1 is not fit for bullseye. The signature of the problem is error messages concerning discrepancy dtyped of COO matrices e.g. * pandas (pandas.tests.arrays.sparse.test_array.TestAccessor.test_from_coo): index = pd.MultiIndex.from_arrays([[0, 0, 1, 3], [0, 2, 1, 3]]) expected = pd.Series([4, 9, 7, 5], index=index, dtype="Sparse[int]") > tm.assert_series_equal(result, expected) E AssertionError: Attributes of Series are different E E Attribute "dtype" are different E [left]: Sparse[float64, nan] E [right]: Sparse[int64, 0] /usr/lib/python3/dist-packages/pandas/tests/arrays/sparse/test_array.py:1196: AssertionError * qutip (tests.test_piqs.TestDicke.test_lindbladian): > self.data = np.array(obj, copy=copy, dtype=data_dtype) E TypeError: can't convert complex to float /usr/lib/python3/dist-packages/scipy/sparse/coo.py:161: TypeError
Processed: tagging 922981
Processing commands for cont...@bugs.debian.org: > tags 922981 + pending - moreinfo Bug #922981 [ca-certificates-java] ca-certificates-java: /etc/ca-certificates/update.d/jks-keystore doesn't update /etc/ssl/certs/java/cacerts Added tag(s) pending. Bug #922981 [ca-certificates-java] ca-certificates-java: /etc/ca-certificates/update.d/jks-keystore doesn't update /etc/ssl/certs/java/cacerts Removed tag(s) moreinfo. > thanks Stopping processing here. Please contact me if you need assistance. -- 922981: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=922981 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#912187: marked as done (Wrong jvm options for armhf)
Your message dated Tue, 23 Feb 2021 15:19:00 +0100 with message-id <4fb58909-b756-4d6c-d598-b0d6eca6e...@debian.org> and subject line Re: ca-certificates-java: Wrong jvm options for armhf has caused the Debian Bug report #912187, regarding Wrong jvm options for armhf 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.) -- 912187: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912187 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: ca-certificates-java Version: 20170531+nmu1 On armhf the server JVM is not available. But the postinst script assumes so and uses it to setup a temporary configuration in /etc/java-8-openjdk/jvm-armhf.cfg The installation of openjdk-8-jre-headless therefore fails! Running hooks in /etc/ca-certificates/update.d... Error: missing `server' JVM at `/usr/lib/jvm/java-8-openjdk-armhf/jre/lib/arm/server/libjvm.so'. Please install or use the JRE or JDK that contains these missing components. E: /etc/ca-certificates/update.d/jks-keystore exited with code 1. done. Errors were encountered while processing: ca-certificates-java openjdk-8-jre-headless:armhf openjdk-9-jre-headless:armhf E: Sub-process /usr/bin/dpkg returned an error code (1) Please use the client defaults instead (jvm.cfg-client_default from the openjdk sources): -client KNOWN -server ALIASED_TO -client Thanks! --- End Message --- --- Begin Message --- On Mon, 28 Jan 2019 20:22:13 +0100 Markus Koschany wrote: > This bug was apparently "fixed" in version 20170929 but then the change > was reverted in 20170930. Both versions were marked as fixed. The > severity is still "serious" and it is not clear from reading the > changelog whether version 20170930 addresses the problem The code dealing with creating temporary jvm config files is gone. Andreas--- End Message ---
Bug#980809: rmatrix: breaks autopkgtest of r-cran-glmmtmb on s390x
Hi Dirk On Tue, 23 Feb 2021 at 15:34, Dirk Eddelbuettel wrote: > If it were me I would turn off the autopkgtest in r-cran-glmmtmb (maybe just > on s390x) and move on. That would just be hiding the problem. If it is the kind of bug I described previously, it shows up more often on big-endian systems, but it is still present on little-endian systems, and will show up in the right (wrong) conditions. Regards Graham
Processed: Re: Bug#980809: rmatrix: breaks autopkgtest of r-cran-glmmtmb on s390x
Processing control commands: > affects -1 src:r-cran-glmmtmb Bug #980809 [src:rmatrix] rmatrix: breaks autopkgtest of r-cran-glmmtmb on s390x Added indication that 980809 affects src:r-cran-glmmtmb > affects -1 src:r-cran-tmb Bug #980809 [src:rmatrix] rmatrix: breaks autopkgtest of r-cran-glmmtmb on s390x Added indication that 980809 affects src:r-cran-tmb -- 980809: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=980809 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#980809: rmatrix: breaks autopkgtest of r-cran-glmmtmb on s390x
Control: affects -1 src:r-cran-glmmtmb Control: affects -1 src:r-cran-tmb Hi Andreas On Tue, 23 Feb 2021 at 10:30, Andreas Tille wrote: > If we do not find a timely solution what do you think about excluding > s390x temporarily from the list of architectures of this package and set > this bug to "important"? Since the autopkgtest failure in r-cran-glmmtmb is already in testing, and not blocking migration, and glmmTMB's upstream have shown that the bug is not in r-cran-glmmtmb, I don't think there's anything to do in r-cran-glmmtmb right now. I've marked this bug as no longer being in r-cran-glmmtmb, but rather that it affects r-cran-glmmtmb and r-cran-tmb. Regards Graham
Bug#982788: marked as done (swift: autopkgtest regression)
Your message dated Tue, 23 Feb 2021 13:50:30 +
with message-id
and subject line Bug#982788: fixed in swift 2.26.0-8
has caused the Debian Bug report #982788,
regarding swift: autopkgtest regression
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.)
--
982788: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=982788
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: swift
Version: 2.26.0-7
Severity: serious
https://ci.debian.net/data/autopkgtest/testing/amd64/s/swift/10443331/log.gz
...
autopkgtest [11:08:02]: test daemons: [---
# Create rings #
Device d0r1z1-127.0.0.1:6202R127.0.0.1:6202/sda1_"" with 1.0 weight got id 0
Device d0r1z1-127.0.0.1:6201R127.0.0.1:6201/sda1_"" with 1.0 weight got id 0
Device d0r1z1-127.0.0.1:6200R127.0.0.1:6200/sda1_"" with 1.0 weight got id 0
Reassigned 16 (100.00%) partitions. Balance is now 0.00. Dispersion is now 0.00
Reassigned 16 (100.00%) partitions. Balance is now 0.00. Dispersion is now 0.00
Reassigned 16 (100.00%) partitions. Balance is now 0.00. Dispersion is now 0.00
# Start all daemons #
# Waiting for start #
# HTTP GET #
Object: {"version": "2.26.0"}2021-02-13 11:08:17
URL:http://127.0.0.1:6200/recon/version [21/21] -> "-" [1]
Container: failed: Connection refused.
failed: Connection refused.
failed: Connection refused.
failed: Connection refused.
failed: Connection refused.
autopkgtest [11:08:27]: test daemons: ---]
autopkgtest [11:08:27]: test daemons: - - - - - - - - - - results - - - - - -
- - - -
daemons FAIL non-zero exit status 4
...
--- End Message ---
--- Begin Message ---
Source: swift
Source-Version: 2.26.0-8
Done: Thomas Goirand
We believe that the bug you reported is fixed in the latest version of
swift, 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 982...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Thomas Goirand (supplier of updated swift 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, 23 Feb 2021 14:11:16 +0100
Source: swift
Architecture: source
Version: 2.26.0-8
Distribution: unstable
Urgency: medium
Maintainer: Debian OpenStack
Changed-By: Thomas Goirand
Closes: 982788
Changes:
swift (2.26.0-8) unstable; urgency=medium
.
* Kill the autopkgtests. The team has other means of testing swift anyways.
(Closes: #982788).
Checksums-Sha1:
71139d64527e8393f98a88ca4d9e4d5b0651354a 3295 swift_2.26.0-8.dsc
2164cad96847790ab37a84fc1f150b8657e772f1 22660 swift_2.26.0-8.debian.tar.xz
2eded77f3cdd9d4177082368e00f547ae20e585e 14307 swift_2.26.0-8_amd64.buildinfo
Checksums-Sha256:
0f8ac7dd8d4eb1071357e6f6b621affb38f7d2253a044c6632d98818cad58401 3295
swift_2.26.0-8.dsc
a9e1e6648d901b82e9390d5cc7fc9bf34ce43da29ab5d37d872321ea8a2d1096 22660
swift_2.26.0-8.debian.tar.xz
c20110187c4b063eb6e9afc2846d49565c8d7d6528f59894848d90665230094c 14307
swift_2.26.0-8_amd64.buildinfo
Files:
b33fc6e14daec86acea09c2250037dc2 3295 net optional swift_2.26.0-8.dsc
eb543937de237d895c10dcc16bd585d8 22660 net optional
swift_2.26.0-8.debian.tar.xz
201d480ac07557dc636bee376c385190 14307 net optional
swift_2.26.0-8_amd64.buildinfo
-BEGIN PGP SIGNATURE-
iQIzBAEBCAAdFiEEoLGp81CJVhMOekJc1BatFaxrQ/4FAmA1AjAACgkQ1BatFaxr
Q/6H2g//bSt4I5/aYf5zAZz3XcCAUSF8sUXxmtSi/Qfis98VrEqexxHTuRjChnT4
zYqF/JQjaPs14wsLsmrnFR8EwAVaiVG/YrYXehgwtXwpCjovR8sozZgqGzL9MHyw
HALZCz0tTVMwzGUyHOX4nqU2gqSy3XmLnPqcrrtsZdPeORvAhGA7sidZ8kfrxBib
s99TL58AM5LJnTjYrm1YoCK+2KLvco6/Hsj7Uktr5vQd7kw/loKK0vYVkv+AFOxi
Omw+xpXdPH5k0HGkKasWdd3a2l1JRXoaxclQfvr8xdhJjFT/dhgnNjjCH4QcsCVW
MRBCBhXY6Z/Z9ycsq7Tpcn8TqC3R8uppdnHin135BZzSFMMrj7fD+1Ix4VYCBl25
ua6CnOUKlXQpkhtXSXAh7ueTnbrPYpSIGKyWvQpZsXTSpsJQDmpcZOwKxJWlt+DC
jkd8ktjXf6GyLR8pUGf4xavtIhkGlVSqp0yF8cLG1vfKmiCZfvWTLWD7aWIuvzMu
DlPEedEDNVvdSUo3Tc+rEYE6OyeCo3E7tc4k0N8/SYuXACYVV3Q6H7vpTFryaKoS
J4lyavPkeqvIzXGhtPlWhQe/7kSVgIjydVTsEBnJ92dQg52EFtq6AFDebv5sJnOU
fCrocXKwTYxnNdf3KSz24eARAX55wAeSwvk0wn2NyHjCFroIwsY=
=CQoT
-END PGP SIGNATURE End Message ---
Processed: tagging 795244, tagging 688415, tagging 908858, tagging 767272, tagging 929685, tagging 940297
Processing commands for cont...@bugs.debian.org: > tags 795244 + pending Bug #795244 [ca-certificates-java] ca-certificates-java.jar - String index out of range: -1 Added tag(s) pending. > tags 688415 + pending Bug #688415 [ca-certificates-java] creates possibly links in root directory Added tag(s) pending. > tags 908858 + pending Bug #908858 [ca-certificates-java] ca-certificates-java: error after package removal Added tag(s) pending. > tags 767272 + pending Bug #767272 [ca-certificates-java] ca-certificates-java: Removed certificates still in cacerts after activate update-ca-certificates-fresh trigger Added tag(s) pending. > tags 929685 + pending Bug #929685 [ca-certificates-java,default-jre-headless,openjdk-11-jre-headless] ca-certificates-java,default-jre-headless,openjdk-11-jre-headless: get rid of the circular dependency Added tag(s) pending. > tags 940297 + pending Bug #940297 [ca-certificates-java] ca-certificates-java: circular dependency hell Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 688415: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=688415 767272: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=767272 795244: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=795244 908858: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=908858 929685: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=929685 940297: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=940297 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#980809: rmatrix: breaks autopkgtest of r-cran-glmmtmb on s390x
If it were me I would turn off the autopkgtest in r-cran-glmmtmb (maybe just on s390x) and move on. I still have not been convinced by anyone that it is an issue in package Matrix causing this. Dirk -- https://dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org
Processed: Bug#982788 marked as pending in swift
Processing control commands: > tag -1 pending Bug #982788 [src:swift] swift: autopkgtest regression Added tag(s) pending. -- 982788: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=982788 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#982788: marked as pending in swift
Control: tag -1 pending Hello, Bug #982788 in swift 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/swift/-/commit/cc1ee6743f10673afb46f0c4e9c553d88c9fcb26 * Kill the autopkgtests. The team has other means of testing swift anyways. (Closes: #982788). (this message was generated automatically) -- Greetings https://bugs.debian.org/982788
Processed: Re: Bug#980809: rmatrix: breaks autopkgtest of r-cran-glmmtmb on s390x
Processing control commands: > reassign -1 src:rmatrix 1.3-0-1 Bug #980809 [src:rmatrix, src:r-cran-glmmtmb] rmatrix: breaks autopkgtest of r-cran-glmmtmb on s390x Bug reassigned from package 'src:rmatrix, src:r-cran-glmmtmb' to 'src:rmatrix'. No longer marked as found in versions rmatrix/1.3-0-1 and r-cran-glmmtmb/1.0.2.1-1. Ignoring request to alter fixed versions of bug #980809 to the same values previously set Bug #980809 [src:rmatrix] rmatrix: breaks autopkgtest of r-cran-glmmtmb on s390x Marked as found in versions rmatrix/1.3-0-1. > tags -1 - fixed-upstream Bug #980809 [src:rmatrix] rmatrix: breaks autopkgtest of r-cran-glmmtmb on s390x Removed tag(s) fixed-upstream. > forwarded -1 https://github.com/kaskr/adcomp/issues/340 Bug #980809 [src:rmatrix] rmatrix: breaks autopkgtest of r-cran-glmmtmb on s390x Changed Bug forwarded-to-address to 'https://github.com/kaskr/adcomp/issues/340' from 'https://github.com/glmmTMB/glmmTMB/issues/665'. -- 980809: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=980809 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#980809: rmatrix: breaks autopkgtest of r-cran-glmmtmb on s390x
Control: reassign -1 src:rmatrix 1.3-0-1 Control: tags -1 - fixed-upstream Control: forwarded -1 https://github.com/kaskr/adcomp/issues/340 Hi Dirk On Thu, 18 Feb 2021 at 19:58, Dirk Eddelbuettel wrote: > Thanks for the bug tracker follow-up which made me aware of the ongoing > discussion in #665 at glmmTMB. It's frustrating to have the run around but it > really looks like as I argued all along: not an issue in Matrix. I don't follow how you reach that conclusion. My understanding is all we have concluded is that it is not a bug in glmmTMB. > Now, TMB is > of course a complex package too.. Appreciate you chasing this so thoroughly. I've opened an issue with TMB upstream. "Let's see how deep the rabbit hole goes." :-) It's fitting that the quote is from The Matrix (1999). > PS What is bts-link? Is that a new service we have to tie our BTS to GH and > others? I've occasionally seen its handiwork before, but didn't know the origin. TIL: https://lists.debian.org/debian-devel-announce/2006/05/msg1.html Regards Graham
Bug#983393: gcc-10: Segmentation fault when building mkvtoolnix
Package: gcc-10 Version: 10.2.1-6 Severity: serious Dear Maintainer, Since the beginning of february gcc is unable to build mkvtoolnix. https://buildd.debian.org/status/fetch.php?pkg=mkvtoolnix&arch=amd64&ver=53.0.0-2&stamp=1612639953&raw=0 Christian -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.10.17 (SMP w/24 CPU threads) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages gcc-10 depends on: ii binutils 2.35.2-2 ii cpp-10 10.2.1-6 ii gcc-10-base10.2.1-6 ii libc6 2.31-9 ii libcc1-0 10.2.1-6 ii libgcc-10-dev 10.2.1-6 ii libgcc-s1 10.2.1-6 ii libgmp10 2:6.2.1+dfsg-1 ii libisl23 0.23-1 ii libmpc31.2.0-1 ii libmpfr6 4.1.0-3 ii libstdc++6 10.2.1-6 ii libzstd1 1.4.8+dfsg-2 ii zlib1g 1:1.2.11.dfsg-2 Versions of packages gcc-10 recommends: ii libc6-dev 2.31-9 Versions of packages gcc-10 suggests: pn gcc-10-doc pn gcc-10-locales pn gcc-10-multilib -- no debconf information
Bug#983010: mdocml breaks debiman autopkgtest: different output
Agreed, the test seems too brittle. Can we just turn the test off for now? https://github.com/Debian/debiman/issues/127 tracks updating mdocml on manpages.d.o, which I intend to do as time permits. I wonder whether it makes sense to have debiman packaged in Debian itself, though. Personally, I’m not maintaining that package, and I’m not sure if there are any users of the package. Anyway, any help welcome to sort this out on the package level. I don’t have time to help, sorry: https://michael.stapelberg.ch/posts/2019-03-10-debian-winding-down/ On Tue, Feb 23, 2021 at 12:45 PM Ivo De Decker wrote: > Control: reassign -1 debiman 0.0~git20200217.fc82521-1 > > Hi, > > On Thu, Feb 18, 2021 at 07:31:32AM +0100, Paul Gevers wrote: > > With a recent upload of mdocml the autopkgtest of debiman fails in > > testing when that autopkgtest is run with the binary packages of mdocml > > from unstable. It passes when run with only packages from testing. In > > tabular form: > > [...] > > > === CONT TestToHTML/i3lock > > convert_test.go:92: unexpected conversion result: (diff from want → > > got): > > --- /tmp/debiman-8492488252021-02-18 04:13:33.034473409 + > > +++ /tmp/debiman-3766921622021-02-18 04:13:33.034473409 + > > @@ -7,67 +7,76 @@ > > > > > > > > - > > - > > + > > + > > + > [...] > > Hard-coding the exact html output of a dependency that generates html, and > expecting that not to change doesn't seem like a robust way to test it > functionality, so I think it's clear that the bug is in the autopkgtest of > debiman. It's perfectly acceptable for mdocml to generate different html > output to represent the data (whether the upload of the new upstream > version > should have happened during the soft freeze is a different matter, but > that's > unrelated to this bug). > > Testing that the html is valid, and contains certain parts of the input > might > be a more useful test. > > Cheers, > > Ivo > -- Best regards, Michael
Bug#983383: qgis-server-common: missing Breaks+Replaces: qgis-server (<< 3.16)
Control: tags -1 pending Hi Andreas, Thanks for reporting this issue, it's fixed in git. Kind Regards, Bas -- GPG Key ID: 4096R/6750F10AE88D4AF1 Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
Processed: Re: Bug#983383: qgis-server-common: missing Breaks+Replaces: qgis-server (<< 3.16)
Processing control commands: > tags -1 pending Bug #983383 [qgis-server-common] qgis-server-common: missing Breaks+Replaces: qgis-server (<< 3.16) Added tag(s) pending. -- 983383: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=983383 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#983010: mdocml breaks debiman autopkgtest: different output
Control: reassign -1 debiman 0.0~git20200217.fc82521-1 Hi, On Thu, Feb 18, 2021 at 07:31:32AM +0100, Paul Gevers wrote: > With a recent upload of mdocml the autopkgtest of debiman fails in > testing when that autopkgtest is run with the binary packages of mdocml > from unstable. It passes when run with only packages from testing. In > tabular form: [...] > === CONT TestToHTML/i3lock > convert_test.go:92: unexpected conversion result: (diff from want → > got): > --- /tmp/debiman-8492488252021-02-18 04:13:33.034473409 + > +++ /tmp/debiman-3766921622021-02-18 04:13:33.034473409 + > @@ -7,67 +7,76 @@ > > > > - > - > + > + > + [...] Hard-coding the exact html output of a dependency that generates html, and expecting that not to change doesn't seem like a robust way to test it functionality, so I think it's clear that the bug is in the autopkgtest of debiman. It's perfectly acceptable for mdocml to generate different html output to represent the data (whether the upload of the new upstream version should have happened during the soft freeze is a different matter, but that's unrelated to this bug). Testing that the html is valid, and contains certain parts of the input might be a more useful test. Cheers, Ivo
Processed: Re: mdocml breaks debiman autopkgtest: different output
Processing control commands: > reassign -1 debiman 0.0~git20200217.fc82521-1 Bug #983010 [src:mdocml, src:debiman] mdocml breaks debiman autopkgtest: different output Bug reassigned from package 'src:mdocml, src:debiman' to 'debiman'. No longer marked as found in versions debiman/0.0~git20200217.fc82521-1 and mdocml/1.14.5-1. Ignoring request to alter fixed versions of bug #983010 to the same values previously set Bug #983010 [debiman] mdocml breaks debiman autopkgtest: different output Marked as found in versions debiman/0.0~git20200217.fc82521-1. -- 983010: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=983010 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#983376: binutils: Crash with building for i386 for amd64 host
Hi, On Tue, 23 Feb 2021 08:49:22 +0100 Christian Marillat wrote: > Package: binutils > Version: 2.35.2-2 > Severity: serious > > Dear Maintainer, > > Fell free to reassign this bug if needed. > > Since this binutils version I'm unable to build any package. > > I'm building i386 packages under pebuilder amd64. > > These crashes aren't related to hardware. I able to reproduce that under an > I7 2600K and AMD 3900 XT. > > Log are for mjpegtools_2.1.0+debian-6 and gst-plugins-bad1.0_1.18.3-1 > packages. > > Attached files are the build ouput from pebuilder *.build.gz files and GCC > Preprocessed source. From a quick look, it seems you are trying cross compilation in some unsupported way. For example, one of your logs shows: 8<8<8<- checking whether we are cross compiling... configure: error: in `/build/mjpegtools-2.1.0+debian': configure: error: cannot run C compiled programs. If you meant to cross compile, use `--host'. See `config.log' for more details tail -v -n \+0 config.log 8<8<8<-- I could cross compile mjpegtools to i386 locally with sbuild, using the following (check the logs attached) sbuild --dist unstable --host i386 mjpegtools Note that for cross compilation to work, dpkg-buildpackage needs to get an appropriate -a/--host-arch parameter. For example this is what the above sbuild invocation produces: Command: dpkg-buildpackage --sanitize-env -ai386 -Pcross,nocheck -us -uc -rfakeroot -j2 You log for mjpegtools, for example, shows: dpkg-buildpackage -us -uc -B -us -uc -j24 mjpegtools_i386-2021-02-23T11:05:53Z.build.gz Description: application/gzip signature.asc Description: PGP signature
Bug#980686: ldc: FTBFS: dh_auto_configure: error: cd bootstrap-stage2
Hi Matthias, On 2/23/21 1:36 AM, Matthias Klumpp wrote: [...] I'll have a look at fixing that. Thanks for the quick fix! Ivo
Processed: Re: Bug#983380: sane: HP ENVY 5536 doesn't scan anymore with simple-scan and xsane (hp-scan : error I/O=9)
Processing commands for cont...@bugs.debian.org: > reassign 983380 hplip 3.21.2+dfsg1-1 Bug #983380 [sane] sane: HP ENVY 5536 doesn't scan anymore with simple-scan and xsane (hp-scan : error I/O=9) Bug reassigned from package 'sane' to 'hplip'. No longer marked as found in versions sane-frontends/1.0.14-16. Ignoring request to alter fixed versions of bug #983380 to the same values previously set Bug #983380 [hplip] sane: HP ENVY 5536 doesn't scan anymore with simple-scan and xsane (hp-scan : error I/O=9) Marked as found in versions hplip/3.21.2+dfsg1-1. > severity 983380 normal Bug #983380 [hplip] sane: HP ENVY 5536 doesn't scan anymore with simple-scan and xsane (hp-scan : error I/O=9) Severity set to 'normal' from 'grave' > thanks Stopping processing here. Please contact me if you need assistance. -- 983380: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=983380 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#983380: sane: HP ENVY 5536 doesn't scan anymore with simple-scan and xsane (hp-scan : error I/O=9)
reassign 983380 hplip 3.21.2+dfsg1-1 severity 983380 normal thanks Hello alain, thank you for spending your time helping to make Debian better with this bug report. In the past, the error message "error: SANE: Error during device I/O (code=9)" always meant an error in the hplip package. In addition, the version hplip 3.21.2+dfsg1-1 is also heavily buggy. I therefore assign the error to the hplip package. CU Jörg Am Dienstag, dem 23.02.2021 um 09:53 +0100 schrieb alain: > Package: sane > Version: 1.0.14-16 > Severity: grave > Tags: upstream > Justification: renders package unusable > X-Debbugs-Cc: compte.perso.de-al...@bbox.fr > > last week-end tried to scan a very important document . > > no more xsane , simple-scan , hp-scan or vuescan works . > > alain@sid:~$ hp-scan > > HP Linux Imaging and Printing System (ver. 3.21.2) > Scan Utility ver. 2.2 > > Copyright (c) 2001-18 HP Development Company, LP > This software comes with ABSOLUTELY NO WARRANTY. > This is free software, and you are welcome to distribute it > under certain conditions. See COPYING file for more details. > > > - > > SELECT DEVICE | > - > > Num Scan device URI > - > 0 escl:http://127.0.0.1:6 > 1* hpaio:/usb/ENVY_5530_series?serial=CN595530XD06BX > > Enter number 0...1 for device (q=quit, =default: 1*) ? > warning: No destinations specified. Adding 'file' destination by > default. > Using device hpaio:/usb/ENVY_5530_series?serial=CN595530XD06BX > Opening connection to device... > error: SANE: Error during device I/O (code=9) > > > alain@sid:~$ hp-scan > > HP Linux Imaging and Printing System (ver. 3.21.2) > Scan Utility ver. 2.2 > > Copyright (c) 2001-18 HP Development Company, LP > This software comes with ABSOLUTELY NO WARRANTY. > This is free software, and you are welcome to distribute it > under certain conditions. See COPYING file for more details. > > > - > > SELECT DEVICE | > - > > Num Scan device URI > - > 0 escl:http://127.0.0.1:6 > 1* hpaio:/usb/ENVY_5530_series?serial=CN595530XD06BX > > Enter number 0...1 for device (q=quit, =default: 1*) ?0 > warning: No destinations specified. Adding 'file' destination by > default. > Using device escl:http://127.0.0.1:6 > Opening connection to device... > error: SANE: Out of memory (code=10) > > alain@sid:~$ systemctl list-units "ipp-usb*" | grep service > ipp-usb.service loaded active running Daemon for IPP over USB > printer support > > > alain@sid:~$ scanimage -L > device `escl:http://127.0.0.1:6' is a HP ENVY 5530 series > [FE04D6] (USB) > flatbed scanner > device `hpaio:/usb/ENVY_5530_series?serial=CN595530XD06BX' is a > Hewlett-Packard > ENVY_5530_series all-in-one > > your command : simple-scan escl:http://127.0.0.1:6 was nearly > ok . > > simple-scan started to connect and , quickly , closed itself : > "cannot connect" > > alain@sid:~$ lsusb -v | grep -A 3 bInterfaceClass.*7 > Couldn't open device, some information will be missing > Couldn't open device, some information will be missing > Couldn't open device, some information will be missing > bInterfaceClass 7 Printer > bInterfaceSubClass 1 Printer > bInterfaceProtocol 4 > iInterface 0 > -- > bInterfaceClass 7 Printer > bInterfaceSubClass 1 Printer > bInterfaceProtocol 2 Bidirectional > iInterface 0 > -- > bInterfaceClass 7 Printer > bInterfaceSubClass 1 Printer > bInterfaceProtocol 4 > iInterface 0 > can't get debug descriptor: Resource temporarily unavailable > Couldn't open device, some information will be missing > -- > bInterfaceClass 7 Printer > bInterfaceSubClass 1 Printer > bInterfaceProtocol 4 > iInterface 0 > Couldn't open device, some information will be missing > Couldn't open device, some information will be missing > Couldn't open device, some information will be missing > Couldn't open device, some information will be missing > Couldn't open device, some information will be missing > Couldn't open device, some information will be missing > > That is a possible upstream bug in SANE for this device. > > alain@sid:~$ sudo apt install --reinstall sane-airscan > [sudo] Mot de passe de alain : > Lecture des listes de paquets... Fait > Construction de l'arbre des dépendances... Fait > Lecture des informations d'état... Fait > 0 mis à jour, 0 nouvellement installés, 1 réinstallés, 0 à enlever et > 9 non mis > à jour. > Il est nécessaire de prendre 117 ko dans les archives. > Après cette opération, 0 o d'espace disque supplémentaires seront > utilisés. > Réception de :1 http://deb.debian.org/debian testing/main amd64 sane-
Bug#983383: qgis-server-common: missing Breaks+Replaces: qgis-server (<< 3.16)
Package: qgis-server-common Version: 3.16.4+dfsg-1~exp1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'sid' to 'experimental'. It installed fine in 'sid', then the upgrade to 'experimental' fails because it tries to overwrite other packages files without declaring a Breaks+Replaces relation. See policy 7.6 at https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces >From the attached log (scroll to the bottom...): Preparing to unpack .../qgis-server-common_3.16.4+dfsg-1~exp1_all.deb ... Unpacking qgis-server-common (3.16.4+dfsg-1~exp1) ... dpkg: error processing archive /var/cache/apt/archives/qgis-server-common_3.16.4+dfsg-1~exp1_all.deb (--unpack): trying to overwrite '/usr/share/qgis/resources/server/api/ogc/schema.json', which is also in package qgis-server 3.10.14+dfsg-1 dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) Errors were encountered while processing: /var/cache/apt/archives/qgis-server-common_3.16.4+dfsg-1~exp1_all.deb cheers, Andreas qgis-server=3.10.14+dfsg-1_qgis-server-common=3.16.4+dfsg-1~exp1.log.gz Description: application/gzip
Bug#983382: python-mitogen: uninstallable in sid
Source: python-mitogen Version: 0.2.9-2 Severity: serious Hello, the package is not installable anymore in sid due to ansible upload Depends: ansible (<< 2.10), ansible (>= 2.3), $ rmadison: ansible| 2.10.7-1 | unstable | source, all Can you please update the dependencies if the package is know to work with this version? G.
Bug#983381: openzwave-controlpanel: FTBFS in sid
control: tags -1 patch pending on deferred/15 diff -Nru openzwave-controlpanel-0.2a+git20161006.a390f35/debian/changelog openzwave-controlpanel-0.2a+git20161006.a390f35/debian/changelog --- openzwave-controlpanel-0.2a+git20161006.a390f35/debian/changelog 2020-11-19 22:01:52.0 +0100 +++ openzwave-controlpanel-0.2a+git20161006.a390f35/debian/changelog 2021-02-22 21:10:19.0 +0100 @@ -1,3 +1,10 @@ +openzwave-controlpanel (0.2a+git20161006.a390f35-2.2) unstable; urgency=medium + + * Non-maintainer upload. + * Build against new openzwave-versioned-dev package (Closes: #983381) + + -- Gianfranco Costamagna Mon, 22 Feb 2021 21:10:19 +0100 + openzwave-controlpanel (0.2a+git20161006.a390f35-2.1) unstable; urgency=medium * Non-maintainer upload. diff -Nru openzwave-controlpanel-0.2a+git20161006.a390f35/debian/control openzwave-controlpanel-0.2a+git20161006.a390f35/debian/control --- openzwave-controlpanel-0.2a+git20161006.a390f35/debian/control 2017-08-19 23:56:56.0 +0200 +++ openzwave-controlpanel-0.2a+git20161006.a390f35/debian/control 2021-02-22 21:10:18.0 +0100 @@ -3,7 +3,7 @@ Priority: optional Maintainer: Debian IoT Maintainers Uploaders: Dara Adib -Build-Depends: debhelper (>= 9), libmicrohttpd-dev, libopenzwave1.5-dev +Build-Depends: debhelper (>= 9), libmicrohttpd-dev, libopenzwave1.6-dev Standards-Version: 4.0.1 Homepage: https://github.com/OpenZWave/open-zwave-control-panel Vcs-Git: https://anonscm.debian.org/git/debian-iot/openzwave-controlpanel.git G.
Processed: Re: openzwave-controlpanel: FTBFS in sid
Processing control commands: > tags -1 patch pending Bug #983381 [src:openzwave-controlpanel] openzwave-controlpanel: FTBFS in sid Added tag(s) pending and patch. -- 983381: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=983381 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#983381: openzwave-controlpanel: FTBFS in sid
Source: openzwave-controlpanel Version: 0.2a+git20161006.a390f35-2.1 Severity: serious Hello, looks like the package can't build anymore because libopenzwave1.5-dev is now called libopenzwave1.6-dev Please update the dependency, or ask src:openzwave maintainers to switch to an unversioned -dev package Gianfranco
Bug#983380: sane: HP ENVY 5536 doesn't scan anymore with simple-scan and xsane (hp-scan : error I/O=9)
Package: sane
Version: 1.0.14-16
Severity: grave
Tags: upstream
Justification: renders package unusable
X-Debbugs-Cc: compte.perso.de-al...@bbox.fr
last week-end tried to scan a very important document .
no more xsane , simple-scan , hp-scan or vuescan works .
alain@sid:~$ hp-scan
HP Linux Imaging and Printing System (ver. 3.21.2)
Scan Utility ver. 2.2
Copyright (c) 2001-18 HP Development Company, LP
This software comes with ABSOLUTELY NO WARRANTY.
This is free software, and you are welcome to distribute it
under certain conditions. See COPYING file for more details.
-
| SELECT DEVICE |
-
Num Scan device URI
-
0 escl:http://127.0.0.1:6
1*hpaio:/usb/ENVY_5530_series?serial=CN595530XD06BX
Enter number 0...1 for device (q=quit, =default: 1*) ?
warning: No destinations specified. Adding 'file' destination by default.
Using device hpaio:/usb/ENVY_5530_series?serial=CN595530XD06BX
Opening connection to device...
error: SANE: Error during device I/O (code=9)
alain@sid:~$ hp-scan
HP Linux Imaging and Printing System (ver. 3.21.2)
Scan Utility ver. 2.2
Copyright (c) 2001-18 HP Development Company, LP
This software comes with ABSOLUTELY NO WARRANTY.
This is free software, and you are welcome to distribute it
under certain conditions. See COPYING file for more details.
-
| SELECT DEVICE |
-
Num Scan device URI
-
0 escl:http://127.0.0.1:6
1*hpaio:/usb/ENVY_5530_series?serial=CN595530XD06BX
Enter number 0...1 for device (q=quit, =default: 1*) ?0
warning: No destinations specified. Adding 'file' destination by default.
Using device escl:http://127.0.0.1:6
Opening connection to device...
error: SANE: Out of memory (code=10)
alain@sid:~$ systemctl list-units "ipp-usb*" | grep service
ipp-usb.service loaded active running Daemon for IPP over USB printer support
alain@sid:~$ scanimage -L
device `escl:http://127.0.0.1:6' is a HP ENVY 5530 series [FE04D6] (USB)
flatbed scanner
device `hpaio:/usb/ENVY_5530_series?serial=CN595530XD06BX' is a Hewlett-Packard
ENVY_5530_series all-in-one
your command : simple-scan escl:http://127.0.0.1:6 was nearly ok .
simple-scan started to connect and , quickly , closed itself : "cannot connect"
alain@sid:~$ lsusb -v | grep -A 3 bInterfaceClass.*7
Couldn't open device, some information will be missing
Couldn't open device, some information will be missing
Couldn't open device, some information will be missing
bInterfaceClass 7 Printer
bInterfaceSubClass 1 Printer
bInterfaceProtocol 4
iInterface 0
--
bInterfaceClass 7 Printer
bInterfaceSubClass 1 Printer
bInterfaceProtocol 2 Bidirectional
iInterface 0
--
bInterfaceClass 7 Printer
bInterfaceSubClass 1 Printer
bInterfaceProtocol 4
iInterface 0
can't get debug descriptor: Resource temporarily unavailable
Couldn't open device, some information will be missing
--
bInterfaceClass 7 Printer
bInterfaceSubClass 1 Printer
bInterfaceProtocol 4
iInterface 0
Couldn't open device, some information will be missing
Couldn't open device, some information will be missing
Couldn't open device, some information will be missing
Couldn't open device, some information will be missing
Couldn't open device, some information will be missing
Couldn't open device, some information will be missing
That is a possible upstream bug in SANE for this device.
alain@sid:~$ sudo apt install --reinstall sane-airscan
[sudo] Mot de passe de alain :
Lecture des listes de paquets... Fait
Construction de l'arbre des dépendances... Fait
Lecture des informations d'état... Fait
0 mis à jour, 0 nouvellement installés, 1 réinstallés, 0 à enlever et 9 non mis
à jour.
Il est nécessaire de prendre 117 ko dans les archives.
Après cette opération, 0 o d'espace disque supplémentaires seront utilisés.
Réception de :1 http://deb.debian.org/debian testing/main amd64 sane-airscan
amd64 0.99.24-1 [117 kB]
117 ko réceptionnés en 0s (1 268 ko/s)
(Lecture de la base de données... 283524 fichiers et répertoires déjà
installés.)
Préparation du dépaquetage de .../sane-airscan_0.99.24-1_amd64.deb ...
Dépaquetage de sane-airscan (0.99.24-1) sur (0.99.24-1) ...
Paramétrage de sane-airscan (0.99.24-1) ...
Traitement des actions différées (« triggers ») pour man-db (2.9.4-2) ...
alain@sid:~$ scanimage -L
device `escl:http://127.0.0.1:6' is a HP ENVY 5530 series [FE04D6] (USB)
flatbed scanner
device `airscan:e0:HP ENVY 5530 series [FE04D6] (USB)' is a eSCL HP ENVY 5530
series [FE04D6] (USB) ip=127.0.0.1
device `hpaio:/usb/ENVY_5530_series?serial=CN595530XD06BX' is a Hewlett-Packard
ENVY_5530_series all-in-one
Bug#983379: Panic on startup
Package: user-mode-linux Version: 5.10um1+b1 Severity: grave On startup of uml in e.g. fakemachine it panics straight away: ``` $ fakemachine -b uml "uname -a" kmsg_dump: <5>Linux version 5.10.5 (buildd@x86-conova-01) (gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.1) #1 Mon Jan 11 20:40:53 UTC 2021 <6>Zone ranges: <6> Normal [mem 0x-0xe164] <6>Movable zone start for each node <6>Early memory node ranges <6> node 0: [mem 0x-0x8164] <6>Initmem setup node 0 [mem 0x-0x8164] <7>On node 0 totalpages: 53 <7> Normal zone: 8282 pages used for memmap <7> Normal zone: 0 pages reserved <7> Normal zone: 53 pages, LIFO batch:63 <7>pcpu-alloc: s0 r0 d32768 u32768 alloc=1*32768 <7>pcpu-alloc: [0] 0 <6>Built 1 zonelists, mobility grouping on. Total pages: 521718 <5>Kernel command line: mem=2048M initrd=/tmp/fakemachine-981932232/initramfs.cpio panic=-1 nosplash systemd.unit=fakemachine.service console=tty0 vec0:transport=fd,fd=3,vec=0 quiet con1=fd:0,fd:1 con0=null con=none root=98:0 <6>Dentry cache hash table entries: 262144 (order: 9, 2097152 bytes, linear) <6>Inode-cache hash table entries: 131072 (order: 8, 1048576 bytes, linear) <6>mem auto-init: stack:off, heap alloc:off, heap free:off <6>Memory: 2044088K/212K available (5830K kernel code, 1535K rwdata, 1744K rodata, 191K init, 225K bss, 75912K reserved, 0K cma-reserved) <6>SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=1, Nodes=1 <6>NR_IRQS: 24 <6>clocksource: timer: mask: 0x max_cycles: 0x1cd42e205, max_idle_ns: 881590404426 ns <6>Calibrating delay loop... 4213.14 BogoMIPS (lpj=21065728) <6>pid_max: default: 32768 minimum: 301 <6>LSM: Security Framework initializing <6>Yama: disabled by default; enable with sysctl kernel.yama.* <6>SELinux: Initializing. <6>TOMOYO Linux initialized <6>Mount-cache hash table entries: 4096 (order: 3, 32768 bytes, linear) <6>Mountpoint-cache hash table entries: 4096 (order: 3, 32768 bytes, linear) <4> <4>Modules linked in: <6>Pid: 0, comm: swapper Not tainted 5.10.5 <6>RIP: 0033:[<604d4201>] <6>RSP: 7ffdc7521cb0 EFLAGS: 00010206 <6>RAX: RBX: 0059 RCX: 7ffdc752 <6>RDX: 0035 RSI: 60b69a71 RDI: 60d8ac3b <6>RBP: R08: 60b69a72 R09: 60d8abe2 <6>R10: 8000 R11: 3d74696e695f676e R12: 0002 <6>R13: 0005 R14: R15: 0001 <0>Kernel panic - not syncing: Segfault with no mm <4>CPU: 0 PID: 0 Comm: swapper Not tainted 5.10.5 #1 <4>Stack: <4> 623e3d20 8000 7fd9ee013908 7fd9ee013ae5 <4> 7fd9ee4629e8 7ffdc7521cf0 0400 <4> 7fd9ee409f20 7fd9ee4629e8 Call Trace: <4> [<604d4fa3>] ? __printk_safe_enter+0x0/0x35 <4> [<604d154a>] ? arch_local_irq_save+0x0/0x22 <4> [<604d46f5>] ? vprintk_emit+0x9d/0x185 <4> [<604d49d3>] ? vprintk_deferred+0x1d/0x32 <4> [<60a26ee2>] ? printk_deferred+0x93/0x9b <4> [<6088f79f>] ? bucket_table_alloc.isra.0+0x115/0x13d <4> [<60a26e4f>] ? printk_deferred+0x0/0x9b <4> [<6049cddb>] ? set_signals+0x0/0x38 <4> [<60589588>] ? arch_local_irq_save+0x0/0x22 <4> [<6055c928>] ? kvmalloc_node+0x56/0x96 <4> [<6058d3c0>] ? __kmalloc+0x1e2/0x1f9 <4> [<608e3d32>] ? ___ratelimit+0xd0/0xde <4> [<6088f79f>] ? bucket_table_alloc.isra.0+0x115/0x13d <4> [<60901485>] ? _warn_unseeded_randomness+0x60/0x8f <4> [<6090295b>] ? get_random_u32+0x29/0x98 <4> [<6088f79f>] ? bucket_table_alloc.isra.0+0x115/0x13d <4> [<6088f68a>] ? bucket_table_alloc.isra.0+0x0/0x13d <4> [<6088ff7a>] ? rhashtable_init+0x175/0x1ca <4> [<607ef317>] ? ipc_init_ids+0x4e/0x6f <4> [<600153bd>] ? sem_init+0x17/0x45 fakemachine: error starting uml backend: ``` -- System Information: Debian Release: bullseye/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'stable-debug'), (500, 'proposed-updates'), (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: armhf, arm64 Kernel: Linux 5.10.0-3-amd64 (SMP w/32 CPU threads) Kernel taint flags: TAINT_UNSIGNED_MODULE Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages user-mode-linux depends on: ii libc6 2.31-9 Versions of packages user-mode-linux recommends: ii uml-utilities 20070815.4-1 Versions of packages user-mode-linux suggests: ii gnome-terminal [x-terminal-emulator] 3.38.3-1 pn rootstrap ii rxvt-unicode [x-terminal-emulator]9.22-8+b1 ii slirp 1:1.0.17-11 pn user-mode-linux-doc pn vde2 ii xterm [x-terminal-emulator] 366-1 -- no debconf information
Bug#983159: marked as done (asterisk: CVE-2021-26906)
Your message dated Tue, 23 Feb 2021 08:33:33 + with message-id and subject line Bug#983159: fixed in asterisk 1:16.16.1~dfsg-1 has caused the Debian Bug report #983159, regarding asterisk: CVE-2021-26906 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.) -- 983159: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=983159 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: asterisk Version: 1:16.15.1~dfsg-1 Severity: grave Tags: security upstream X-Debbugs-Cc: car...@debian.org, Debian Security Team Hi, The following vulnerability was published for asterisk, filling as RC but this might not be warranted, if you feel otherwise please downgrade. I made it such because of the unauthenticated vector. CVE-2021-26906[0]: | An issue was discovered in res_pjsip_session.c in Digium Asterisk | through 13.38.1; 14.x, 15.x, and 16.x through 16.16.0; 17.x through | 17.9.1; and 18.x through 18.2.0, and Certified Asterisk through | 16.8-cert5. An SDP negotiation vulnerability in PJSIP allows a remote | server to potentially crash Asterisk by sending specific SIP responses | that cause an SDP negotiation failure. 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-26906 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-26906 [1] https://downloads.asterisk.org/pub/security/AST-2021-005.html Please adjust the affected versions in the BTS as needed. Regards, salvatore --- End Message --- --- Begin Message --- Source: asterisk Source-Version: 1:16.16.1~dfsg-1 Done: Bernhard Schmidt We believe that the bug you reported is fixed in the latest version of asterisk, 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 983...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Bernhard Schmidt (supplier of updated asterisk 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, 22 Feb 2021 21:45:24 +0100 Source: asterisk Architecture: source Version: 1:16.16.1~dfsg-1 Distribution: unstable Urgency: medium Maintainer: Debian VoIP Team Changed-By: Bernhard Schmidt Closes: 983157 983158 983159 Changes: asterisk (1:16.16.1~dfsg-1) unstable; urgency=medium . * New minor upstream version 16.16.1~dfsg - CVE-2020-35776 / AST-2021-001 (Closes: #983158) Remote crash in res_pjsip_diversion - CVE-2021-26717 / AST-2021-002 (Closes: #983157) Remote crash possible when negotiating T.38 - CVE-2021-26712 / AST-2021-003 Remote attacker could prematurely tear down SRTP calls - CVE-2021-26713 / AST-2021-004 An unsuspecting WebRTC user could crash Asterisk with multiple hold/unhold requests - CVE-2021-26906 / AST-2021-005 (Closes: #983159) Remote Crash Vulnerability in PJSIP channel driver Checksums-Sha1: 5c73481bd88fe4be6792a41fe2f23b3b5ffb49c6 4201 asterisk_16.16.1~dfsg-1.dsc f0b46a4eabe561df5c690f73862746fa01d67739 7055724 asterisk_16.16.1~dfsg.orig.tar.xz 6e31210b806d7027ef475eef0d6151773c0dad1a 5949036 asterisk_16.16.1~dfsg-1.debian.tar.xz 245f453160ced40a7c25b06ecde05eee12f35c3a 27221 asterisk_16.16.1~dfsg-1_amd64.buildinfo Checksums-Sha256: c967376bac906d3e82eea5435b372cdf858aa950488f3d82302dd5bac1ee864c 4201 asterisk_16.16.1~dfsg-1.dsc 42268f21025a0fab9288f616951609f8b10118fb63e35fae80e7d110eb5dda6e 7055724 asterisk_16.16.1~dfsg.orig.tar.xz 2c421974dbad0178b8af0ef3919b151c8317d1a841980a3ba4ec3be3c41d5a85 5949036 asterisk_16.16.1~dfsg-1.debian.tar.xz 5c3acfc60c27c44a0f5e4580f3ab9cb15822404a0f0958dc294a57179b6bca38 27221 asterisk_16.16.1~dfsg-1_amd64.buildinfo Files: cdd946324c7bfb50a0e2cb38fbc538f4 4201 comm optional asterisk_16.16.1~dfsg-1.dsc ad421903a111f0a43e25d64b7aadc2e9 7055724 comm optional asterisk_16.16.1~dfsg.orig.tar.xz 998121308e544f279b505428e4e41b48 5949036 comm optional asterisk_16.16.1~dfsg-1.debian.tar.xz 463b15a8fafdd15741f9864e9e4c847a 27221 comm optional asterisk_16.16.1~dfsg-1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQJFBAEBCgAvF
Bug#980809: rmatrix: breaks autopkgtest of r-cran-glmmtmb on s390x
Hi, any update to this bug? If we do not find a timely solution what do you think about excluding s390x temporarily from the list of architectures of this package and set this bug to "important"? I would not be happy about this but the issue creates some autoremoval warnings on other packages which is scary in times of freeze. Kind regards Andreas. -- http://fam-tille.de
