Bug#964944: marked as done (language pack not selectable in libreoffice settings)
Your message dated Thu, 16 Jul 2020 05:05:56 +
with message-id
and subject line Bug#964944: fixed in libreoffice 1:7.0.0~rc2-1
has caused the Debian Bug report #964944,
regarding language pack not selectable in libreoffice settings
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.)
--
964944: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964944
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libreoffice-l10n-zh-cn
Version: 1:7.0.0~rc1-5
Severity: normal
Tags: l10n
Dear Maintainer,
zh-cn (and zh-tw) languages are not selectable in libreoffice settings
after upgrading to 7.0. By comparing with language packs of other
languages, I notice that some autogenerated commands are missing in
postinst script of libreoffice-l10n-zh-{cn,tw}. Manually running the
following commands fixes the problem:
ucf --three-way
"/usr/lib/libreoffice/share/.registry/Langpack-zh-CN.xcd"
"/etc/libreoffice/registry/Langpack-zh-CN.xcd"
ucfr --force libreoffice-l10n-zh-CN
"/etc/libreoffice/registry/Langpack-zh-CN.xcd"
ucf --three-way
"/usr/lib/libreoffice/share/.registry/res/fcfg_langpack_zh-CN.xcd"
"/etc/libreoffice/registry/res/fcfg_langpack_zh-CN.xcd"
ucfr --force libreoffice-l10n-zh-CN
"/etc/libreoffice/registry/res/fcfg_langpack_zh-CN.xcd"
ucf --three-way
"/usr/lib/libreoffice/share/.registry/res/registry_zh-CN.xcd"
"/etc/libreoffice/registry/res/registry_zh-CN.xcd"
ucfr --force libreoffice-l10n-zh-CN
"/etc/libreoffice/registry/res/registry_zh-CN.xcd"
ucf --three-way "/usr/lib/libreoffice/share/.registry/cjk_zh-CN.xcd"
"/etc/libreoffice/registry/cjk_zh-CN.xcd"
ucfr --force libreoffice-l10n-zh-CN "/etc/libreoffice/registry/cjk_zh-CN.xcd"
fi
-- System Information:
Debian Release: bullseye/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 5.7.0-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=zh_CN.UTF-8, LC_CTYPE=zh_CN.UTF-8 (charmap=UTF-8),
LANGUAGE=zh_CN:zh (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages libreoffice-l10n-zh-cn depends on:
ii libreoffice-common 1:7.0.0~rc1-5
ii locales 2.30-8
Versions of packages libreoffice-l10n-zh-cn recommends:
ii libreoffice-core 1:7.0.0~rc1-5
Versions of packages libreoffice-l10n-zh-cn suggests:
pn hunspell-dictionary-zh-cn | myspell-dictionary-zh-cn
pn hyphen-zh-cn
pn libreoffice-grammarcheck-zh-cn
ii libreoffice-help-zh-cn1:7.0.0~rc1-5
pn mythes-zh-cn
-- no debconf information
--- End Message ---
--- Begin Message ---
Source: libreoffice
Source-Version: 1:7.0.0~rc2-1
Done: Rene Engelhard
We believe that the bug you reported is fixed in the latest version of
libreoffice, 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 964...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Rene Engelhard (supplier of updated libreoffice 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, 15 Jul 2020 18:31:45 +
Source: libreoffice
Architecture: source
Version: 1:7.0.0~rc2-1
Distribution: unstable
Urgency: medium
Maintainer: Debian LibreOffice Maintainers
Changed-By: Rene Engelhard
Closes: 964944
Changes:
libreoffice (1:7.0.0~rc2-1) unstable; urgency=medium
.
* New upstream release candidate
.
* debian/control*.in:
- fix "compatibility" spelling and one s/package/library/ for consistency.
- add explicit depends on liblibreoffice-java for documentation purposes
* debian/rules:
- symlink oo-ldap.xcd.sample and oo-ad-ldap.xcd.sample to
in /etc/libreoffice/registry so that they are not hidden in
/usr/lib/libreoffice/share/.registry
- move /usr/lib/libreoffice/share/registry/README creation later it rules
so that it doesn't get hidden in /usr/lib/libreoffice/share/.registry
- fix adding the ucf snippets to zh-CN,zh-TW etc (closes: #964944)
- update jh_classpath calls for libreoffice.jar
Checksums-Sha1:
abc27149289c43
Bug#885195: [Pkg-electronics-devel] Bug#885195: Bug#885195: geda-gaf: please migrate to guile-2.2
Rob Browning writes: > Bdale Garbee writes: > >> I'm not interested in maintaining pcb any more. > > Does that mean geda-gaf etc? If so might it make sense for you (or > who?) to file a removal request, i.e. ROM or similar? Sorry, you make a good point, geda-gaf and pcb aren't the same thing. While I no longer use either (choosing to use the forks lepton-eda and pcb-rnd instead), there's no immediate need to shove pcb out of the archive. However, I see little chance of geda-gaf upstream working on the things needed to keep it viable in Debian any time soon, and with lepton-eda in my mind a complete replacement that still works with the same file formats, etc, I see no reason to go nuts trying to make geda-gaf better. I'll file a removal request for geda-gaf. Bdale signature.asc Description: PGP signature
Bug#964494: File system corruption with ext3 + kernel-4.19.0-9-amd64
On 7/7/20 8:13 PM, Ben Hutchings wrote: Control: reassign -1 src:linux Control: tag -1 moreinfo On Tue, 2020-07-07 at 17:30 -0700, Sarah Newman wrote: Package: linux-signed-amd64 Version: 4.19.0-9-amd64 We've had two separate reports now of debian buster users running 4.19.0-9-amd64 who experienced serious file system corruption. Which version? (I.e. what does "uname -v" or "dpkg -s linux-image-4.19.0-9-amd64" say?) - Both were using ext3 - Both are running Xen HVM, but I do not have reason to believe this to be related I doubt it matters, but the two observed failures were on hosts with Xeon v2's (we're currently working on fixing that.) New reports: * Buster 4.19.0-6-amd64, ext3, uptime ~36 weeks, Xeon v4, no failure * Buster 4.19.0-9-amd64, ext4, uptime ~6 days, Xeon v2, no failure (but it hasn't even been a week) * Arch Linux v5.6.11, ext3, uptime ~9 weeks, Xeon v2, no failure --Sarah
Bug#959947: marked as done (python-m2crypto-doc: missing Breaks+Replaces: m2crypto-doc (<< 0.35.2-2))
Your message dated Thu, 16 Jul 2020 03:48:40 +
with message-id
and subject line Bug#959947: fixed in m2crypto 0.36.0-1
has caused the Debian Bug report #959947,
regarding python-m2crypto-doc: missing Breaks+Replaces: m2crypto-doc (<<
0.35.2-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.)
--
959947: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=959947
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python-m2crypto-doc
Version: 0.35.2-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package fails to upgrade from
'testing'.
It installed fine in 'testing', then the upgrade to 'sid' 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 .../python-m2crypto-doc_0.35.2-2_all.deb ...
Unpacking python-m2crypto-doc (0.35.2-2) ...
dpkg: error processing archive
/var/cache/apt/archives/python-m2crypto-doc_0.35.2-2_all.deb (--unpack):
trying to overwrite '/usr/share/doc-base/m2crypto-documentation', which is
also in package m2crypto-doc 0.31.0-9
Errors were encountered while processing:
/var/cache/apt/archives/python-m2crypto-doc_0.35.2-2_all.deb
cheers,
Andreas
m2crypto-doc=0.31.0-9_python-m2crypto-doc=0.35.2-2.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: m2crypto
Source-Version: 0.36.0-1
Done: Sandro Tosi
We believe that the bug you reported is fixed in the latest version of
m2crypto, 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 959...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Sandro Tosi (supplier of updated m2crypto 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: Wed, 15 Jul 2020 23:27:35 -0400
Source: m2crypto
Architecture: source
Version: 0.36.0-1
Distribution: unstable
Urgency: medium
Maintainer: Sandro Tosi
Changed-By: Sandro Tosi
Closes: 959947 964299
Changes:
m2crypto (0.36.0-1) unstable; urgency=medium
.
* New upstream release
* debian/control
- add Breaks+Replaces: m2crypto-doc on -doc pkg; Closes: #959947, #964299
- wrap-and-sort
- bump compat level to 13
* debian/patches/{d3a43ffe1bfe4c128d6ab7c390419dee68f4ca5a.patch,
d67b8e3d2682eb70248d7070d860dabe5a003d52.patch}
- drop patches, merged upstream
Checksums-Sha1:
273951e3fa4ca1bb53adb102598fe6070b4618d9 2319 m2crypto_0.36.0-1.dsc
d35bb3322167b173c3aeb4854dc04ab969e495ae 447632 m2crypto_0.36.0.orig.tar.xz
417ab6425c02a96f1e724f1295fd574eae9b4ae6 58068 m2crypto_0.36.0-1.debian.tar.xz
2ae94320fc561e4e04979c10f8c491c9f92656c3 8032
m2crypto_0.36.0-1_source.buildinfo
Checksums-Sha256:
7130af610dedb0d899bb192373e62309600bd0139dced687d15b88023289d536 2319
m2crypto_0.36.0-1.dsc
f561a103742a5a8a99d9912f962921dea7a3529d2be66591401b4b7a95ae718f 447632
m2crypto_0.36.0.orig.tar.xz
075c9991254b7accb1c8b01a6835bd9516aa85b155b3ce29d6ce510b68c36eea 58068
m2crypto_0.36.0-1.debian.tar.xz
0d4238e30807e36172a20205465c6c78f8083eea798b027b2a914a3c1ca0da7d 8032
m2crypto_0.36.0-1_source.buildinfo
Files:
dbc90d6fef203a06c5edc8c301939c99 2319 python optional m2crypto_0.36.0-1.dsc
4c58d52993840e7656fcd35666e90f50 447632 python optional
m2crypto_0.36.0.orig.tar.xz
9396f5ef506b5a6a3dee2ba9a4fc3b95 58068 python optional
m2crypto_0.36.0-1.debian.tar.xz
f08543c887660f1fff32c803fa578a6b 8032 python optional
m2crypto_0.36.0-1_source.buildinfo
-BEGIN PGP SIGNATURE-
iQIzBAEBCAAdFiEEufrTGSrz5KUwnZ05h588mTgBqU8FAl8PyTkACgkQh588mTgB
qU9/8w/+JXi8edTB/RL0RQVSGhZHzLYCXYt26d3ELQVfdFUiK4WpTgTzk6EzN/Vx
hDoEQYMhWTtSlmTzq2jTgagiQIITfVesT46m3cXFGLRYgRe/WjODSdHyAG8h0Lu/
b2+9Ol81xLuUxaYVVcmoI8x6QA3m6iDSa8IH80WKivAka5PGx650gKTDyKJM4+3e
k3onkM2+Y1Qw0fv0MGqKI5rH2UGPdnpb0d/37wn2Rgx0wUEixoqcWRiHiLq8/s0G
IVX1BZwCONY0ZFLN30ujxTziPYJlHVUv15cWMCNlmjWxeV2HNCSwlyBZdL3rgKp/
wgn1AkTVTgEaCJ89LlPv78FCIXibj5Nm61YX5l
Bug#964299: marked as done (src:m2crypto: fails to migrate to testing for too long: unfixed RC bug and maintainer built arch:all binaries)
Your message dated Thu, 16 Jul 2020 03:48:40 +
with message-id
and subject line Bug#964299: fixed in m2crypto 0.36.0-1
has caused the Debian Bug report #964299,
regarding src:m2crypto: fails to migrate to testing for too long: unfixed RC
bug and maintainer built arch:all binaries
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.)
--
964299: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964299
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: m2crypto
Version: 0.31.0-9
Severity: serious
Control: close -1 0.35.2-2
Tags: sid bullseye
User: release.debian@packages.debian.org
Usertags: out-of-sync
Control: block -1 by 959947
Dear maintainer(s),
As recently announced [1], the Release Team now considers packages that
are out-of-sync between testing and unstable for more than 60 days as
having a Release Critical bug in testing. Your package src:m2crypto in
its current version in unstable has been trying to migrate for 60 days
[2]. Hence, I am filing this bug.
If a package is out of sync between unstable and testing for a longer
period, this usually means that bugs in the package in testing cannot be
fixed via unstable. Additionally, blocked packages can have impact on
other packages, which makes preparing for the release more difficult.
Finally, it often exposes issues with the package and/or
its (reverse-)dependencies. We expect maintainers to fix issues that
hamper the migration of their package in a timely manner.
This bug will trigger auto-removal when appropriate. As with all new
bugs, there will be at least 30 days before the package is auto-removed.
I have immediately closed this bug with the version in unstable, so if
that version or a later version migrates, this bug will no longer affect
testing. I have also tagged this bug to only affect sid and bullseye, so
it doesn't affect (old-)stable.
If you believe your package is unable to migrate to testing due to
issues beyond your control, don't hesitate to contact the Release Team.
Paul
[1] https://lists.debian.org/debian-devel-announce/2020/02/msg5.html
[2] https://qa.debian.org/excuses.php?package=m2crypto
signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: m2crypto
Source-Version: 0.36.0-1
Done: Sandro Tosi
We believe that the bug you reported is fixed in the latest version of
m2crypto, 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 964...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Sandro Tosi (supplier of updated m2crypto 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: Wed, 15 Jul 2020 23:27:35 -0400
Source: m2crypto
Architecture: source
Version: 0.36.0-1
Distribution: unstable
Urgency: medium
Maintainer: Sandro Tosi
Changed-By: Sandro Tosi
Closes: 959947 964299
Changes:
m2crypto (0.36.0-1) unstable; urgency=medium
.
* New upstream release
* debian/control
- add Breaks+Replaces: m2crypto-doc on -doc pkg; Closes: #959947, #964299
- wrap-and-sort
- bump compat level to 13
* debian/patches/{d3a43ffe1bfe4c128d6ab7c390419dee68f4ca5a.patch,
d67b8e3d2682eb70248d7070d860dabe5a003d52.patch}
- drop patches, merged upstream
Checksums-Sha1:
273951e3fa4ca1bb53adb102598fe6070b4618d9 2319 m2crypto_0.36.0-1.dsc
d35bb3322167b173c3aeb4854dc04ab969e495ae 447632 m2crypto_0.36.0.orig.tar.xz
417ab6425c02a96f1e724f1295fd574eae9b4ae6 58068 m2crypto_0.36.0-1.debian.tar.xz
2ae94320fc561e4e04979c10f8c491c9f92656c3 8032
m2crypto_0.36.0-1_source.buildinfo
Checksums-Sha256:
7130af610dedb0d899bb192373e62309600bd0139dced687d15b88023289d536 2319
m2crypto_0.36.0-1.dsc
f561a103742a5a8a99d9912f962921dea7a3529d2be66591401b4b7a95ae718f 447632
m2crypto_0.36.0.orig.tar.xz
075c9991254b7accb1c8b01a6835bd9516aa85b155b3ce29d6ce510b68c36eea 58068
m2crypto_0.36.0-1.debian.tar.xz
0d4238e30807e36172a20205465c6c78f8083eea798b027b2a914a3c1ca0da7d 8032
m2crypto_0.36.0-1_source.buildinfo
Files:
dbc90d6fef203a06c5edc8c301939c99 2319 python optional m2crypto_0.36.0-1.dsc
4c58d52993840e7656fcd35666e90f50 447632 python optional
m2crypto_0.
Bug#959947: marked as pending in m2crypto
Control: tag -1 pending Hello, Bug #959947 in m2crypto 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/modules/m2crypto/-/commit/57061b5a380fd51a7b753f9c1164511b9a9dfb1b add Breaks+Replaces: m2crypto-doc on -doc pkg; Closes: #959947, #964299 (this message was generated automatically) -- Greetings https://bugs.debian.org/959947
Processed: Bug#959947 marked as pending in m2crypto
Processing control commands: > tag -1 pending Bug #959947 [python-m2crypto-doc] python-m2crypto-doc: missing Breaks+Replaces: m2crypto-doc (<< 0.35.2-2) Added tag(s) pending. -- 959947: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=959947 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#965095: Searx 0.17.0 with uwsgi throws Internal Server Error
Package: searx Severity: grave Version: 0.17.0+dfsg1-1 There appears to be a missing Python dependency (werkzeug.contrib) in the new Searx 17.0 package uploaded to unstable. Tested in Debian unstable container. Error log from /var/log/uwsgi/app/searx.log --- Traceback (most recent call last): File "/usr/lib/python3/dist-packages/searx/webapp.py", line 50, in from werkzeug.contrib.fixers import ProxyFix ModuleNotFoundError: No module named 'werkzeug.contrib' Thu Jul 16 07:22:32 2020 - unable to load app 0 (mountpoint='') (callable not found or import error) Thu Jul 16 07:22:32 2020 - *** no app loaded. going in full dynamic mode *** Traceback (most recent call last): File "/usr/lib/python3/dist-packages/searx/webapp.py", line 50, in from werkzeug.contrib.fixers import ProxyFix ModuleNotFoundError: No module named 'werkzeug.contrib' -- Regards, Joseph Nuthalapati signature.asc Description: OpenPGP digital signature
Bug#961230: guile-2.2 FTBFS with make-dfsg/4.3-1: ERROR: alternatives priority expects min version < 1000.
Helmut Grohne writes: > It is surprising that this didn't fail with earlier versions of make. > The shell substitution is clearly wrong. It is unclear what it is > supposed to achieve. In any case, deleting these lines makes the build > proceed. > Hah, I just hit and fixed this last night when I was updating us to 3.0.4 (see 3.0.4-1). And yeah, that was wrong. Thanks -- Rob Browning rlb @defaultvalue.org and @debian.org GPG as of 2011-07-10 E6A9 DA3C C9FD 1FF8 C676 D2C4 C0F0 39E9 ED1B 597A GPG as of 2002-11-03 14DD 432F AE39 534D B592 F9A0 25C8 D377 8C7E 73A4
Bug#885195: [Pkg-electronics-devel] Bug#885195: Bug#885195: geda-gaf: please migrate to guile-2.2
Bdale Garbee writes: > I'm not interested in maintaining pcb any more. Does that mean geda-gaf etc? If so might it make sense for you (or who?) to file a removal request, i.e. ROM or similar? (I can of course, but I suspect it'll be more quickly accepted if one of the existing maintainers does.) Thanks -- Rob Browning rlb @defaultvalue.org and @debian.org GPG as of 2011-07-10 E6A9 DA3C C9FD 1FF8 C676 D2C4 C0F0 39E9 ED1B 597A GPG as of 2002-11-03 14DD 432F AE39 534D B592 F9A0 25C8 D377 8C7E 73A4
Bug#965054: guile-2.0 ftbfs on unstable (test failure)
Matthias Klose writes:
> After fixing the build with make 4.3, the build then fails with a test
> failure.
> Only seen on amd64, not on other architectures.
>
> [...]
> make check-TESTS
> make[4]: Entering directory '/<>/guile-2.0-2.0.13+1'
> Testing /<>/guile-2.0-2.0.13+1/meta/guile ...
> with GUILE_LOAD_PATH=/<>/guile-2.0-2.0.13+1/test-suite
> Running 00-initial-env.test
> Running 00-repl-server.test
> ERROR: 00-repl-server.test: repl-server: HTTP inter-protocol attack -
> arguments:
> ((system-error "fport_write" "~A" ("Broken pipe") (32)))
I'll try to remember to look in a bit, but that rings a vague bell -- we
may have added some patches (debian, and/or later upstream) for issues
there.
--
Rob Browning
rlb @defaultvalue.org and @debian.org
GPG as of 2011-07-10 E6A9 DA3C C9FD 1FF8 C676 D2C4 C0F0 39E9 ED1B 597A
GPG as of 2002-11-03 14DD 432F AE39 534D B592 F9A0 25C8 D377 8C7E 73A4
Bug#965091: glibc: setgroups: Bad address [2.31/x32, regression from 2.30]
On Wed, Jul 15, 2020 at 5:22 PM Jessica Clarke wrote: > > [H.J. Lu Cc'ed as author of what looks like the problematic commit] > > On Wed, 15 Jul 2020 23:47:27 +0200 (CEST) Thorsten Glaser > wrote: > > Some more analysis: > > > > We enter libc from openssh code with the correct values in rsi and rdi: > > > > > > (gdb) u > > => 0x56560e45 : call 0x5655d0b0 > > (gdb) info r > > rax0xfffe 65534 > > rbx0x5663a000 1449369600 > > rcx0x0 0 > > rdx0x0 0 > > rsi0xd2e0 4294955744 > > rdi0x1 1 > > rbp0x56641b50 1449401168 > > rsp0xd260 4294955616 > > r8 0x0 0 > > r9 0x0 0 > > r100xf7a8 4155017352 > > r110x246 582 > > r120x565d71d1 1448964561 > > r130x3 3 > > r140xe2cc 58060 > > r150x5663c730 1449379632 > > rip0x56560e45 1448480325 > > eflags 0x282 [ SF IF ] > > cs 0x3351 > > ss 0x2b43 > > ds 0x2b43 > > es 0x2b43 > > fs 0x0 0 > > gs 0x0 0 > > > > > > Inside glibc, there’s an indirect call: > > > > > > => 0xf79949f4 <__GI_setgroups+100>: call rax > > rax0xf7833500 4152571136 > > => 0xf7833500 <__nptl_setxid>: push r15 > > > > > > Some time in __nptl_setxid later, here’s the bug: > > > > > > 1162in allocatestack.c > > rax0xf77ca840 4152141888 > > rbx0xd230 4294955568 > > rcx0x0 0 > > rdx0x1 1 > > rsi0xd2e0 4294955744 > > rdi0xf77ca840 4152141888 > > rbp0xf77ca840 4152141888 > > rsp0xd1d0 4294955472 > > r8 0x0 0 > > r9 0x0 0 > > r100xf77caac0 4152142528 > > r110x246 582 > > r120xf784a360 4152664928 > > r130xf784a360 4152664928 > > Looks like df76ff3a446a787a95cf74cb15c285464d73a93d broke this upstream > (x32: Properly pass long to syscall [BZ #25810]). > > setgroups uses INLINE_SETXID_SYSCALL, which in turn passes its > arguments through the various id fields in xid_command. Unfortunately, > those are `long int`, and so, when the `const gid_t *list` argument > gets later passed through INTERNAL_SYSCALL_NCS, it's treated as an > integer argument and thus sign-extended, despite actually being a > pointer. I think xid_command's id fields need to become __kernel_ulong > or equivalent, with ARGIFY happening inside INLINE_SETXID_SYSCALL when > it still knows what the types are. > Please open a glibc bug with a small testcase. -- H.J.
Bug#965091: glibc: setgroups: Bad address [2.31/x32, regression from 2.30]
[H.J. Lu Cc'ed as author of what looks like the problematic commit] On Wed, 15 Jul 2020 23:47:27 +0200 (CEST) Thorsten Glaser wrote: > Some more analysis: > > We enter libc from openssh code with the correct values in rsi and rdi: > > > (gdb) u > => 0x56560e45 : call 0x5655d0b0 > (gdb) info r > rax0xfffe 65534 > rbx0x5663a000 1449369600 > rcx0x0 0 > rdx0x0 0 > rsi0xd2e0 4294955744 > rdi0x1 1 > rbp0x56641b50 1449401168 > rsp0xd260 4294955616 > r8 0x0 0 > r9 0x0 0 > r100xf7a8 4155017352 > r110x246 582 > r120x565d71d1 1448964561 > r130x3 3 > r140xe2cc 58060 > r150x5663c730 1449379632 > rip0x56560e45 1448480325 > eflags 0x282 [ SF IF ] > cs 0x3351 > ss 0x2b43 > ds 0x2b43 > es 0x2b43 > fs 0x0 0 > gs 0x0 0 > > > Inside glibc, there’s an indirect call: > > > => 0xf79949f4 <__GI_setgroups+100>: call rax > rax0xf7833500 4152571136 > => 0xf7833500 <__nptl_setxid>: push r15 > > > Some time in __nptl_setxid later, here’s the bug: > > > 1162in allocatestack.c > rax0xf77ca840 4152141888 > rbx0xd230 4294955568 > rcx0x0 0 > rdx0x1 1 > rsi0xd2e0 4294955744 > rdi0xf77ca840 4152141888 > rbp0xf77ca840 4152141888 > rsp0xd1d0 4294955472 > r8 0x0 0 > r9 0x0 0 > r100xf77caac0 4152142528 > r110x246 582 > r120xf784a360 4152664928 > r130xf784a360 4152664928 Looks like df76ff3a446a787a95cf74cb15c285464d73a93d broke this upstream (x32: Properly pass long to syscall [BZ #25810]). setgroups uses INLINE_SETXID_SYSCALL, which in turn passes its arguments through the various id fields in xid_command. Unfortunately, those are `long int`, and so, when the `const gid_t *list` argument gets later passed through INTERNAL_SYSCALL_NCS, it's treated as an integer argument and thus sign-extended, despite actually being a pointer. I think xid_command's id fields need to become __kernel_ulong or equivalent, with ARGIFY happening inside INLINE_SETXID_SYSCALL when it still knows what the types are. Jess
Bug#959828: systemctl: `Provides: systemd`, but doesn't provide what systemd does
Hello, My 2¢ on this: speech-dispatcher build-depends on systemd in order to get systemd.pc and read systemdsystemunitdir from it, but that fails on experimental buildds because they currently have systemctl installed instead of systemd: https://buildd.debian.org/status/package.php?p=speech-dispatcher&suite=experimental Of course, I could just hardcode the systemdsystemunitdir variable instead of letting ./configure read it from systemd.pc, and be done with the issue, but that seems very wrong to me. Adding a Build-conflicts also looks quite wrong to me: should we really make packages know what package provides-but-not-completely systemd? Samuel
Bug#965033: debdiff
I'm happy to NMU this since it's affecting some of my packages (zimlib,
libkiwix, zim-tools, etc.). debdiff is attached.
It's not clear to me why the dependency was commented out in the first
place, but it fixes the immediate issue. Let me know if that's OK and if
you'd like me to go ahead.
-- Kunal
diff -Nru meson-0.55.0/debian/changelog meson-0.55.0/debian/changelog
--- meson-0.55.0/debian/changelog 2020-07-12 07:29:15.0 -0700
+++ meson-0.55.0/debian/changelog 2020-07-15 15:48:39.0 -0700
@@ -1,3 +1,10 @@
+meson (0.55.0-1.1) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Add missing dependency on python3-pkg-resources Closes: #965033.
+
+ -- Kunal Mehta Wed, 15 Jul 2020 15:48:39 -0700
+
meson (0.55.0-1) unstable; urgency=medium
* New upstream release.
diff -Nru meson-0.55.0/debian/control meson-0.55.0/debian/control
--- meson-0.55.0/debian/control 2020-07-12 07:29:07.0 -0700
+++ meson-0.55.0/debian/control 2020-07-15 15:48:37.0 -0700
@@ -94,7 +94,7 @@
${misc:Depends},
${python3:Depends},
ninja-build(>=1.6),
-# python3-pkg-resources,
+ python3-pkg-resources,
Description: high-productivity build system
Meson is a build system designed to increase programmer
productivity. It does this by providing a fast, simple and easy to
Processed: your mail
Processing commands for cont...@bugs.debian.org: > affects 965091 openssh-server Bug #965091 [libc6] glibc: setgroups: Bad address [2.31/x32, regression from 2.30] Added indication that 965091 affects openssh-server > affects 965091 postfix Bug #965091 [libc6] glibc: setgroups: Bad address [2.31/x32, regression from 2.30] Added indication that 965091 affects postfix > thanks Stopping processing here. Please contact me if you need assistance. -- 965091: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965091 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#965087: marked as done (postfix/master[2632]: fatal: set_eugid: setgroups(137): Bad address)
Your message dated Wed, 15 Jul 2020 23:58:56 + (UTC) with message-id and subject line Re: Bug#965086: ssh: setgroups: Bad address [preauth] has caused the Debian Bug report #965087, regarding postfix/master[2632]: fatal: set_eugid: setgroups(137): Bad address 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.) -- 965087: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965087 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: postfix Version: 3.5.4-1 Severity: grave Justification: renders package unusable After a glibc upgrade today, I cannot start postfix any more. I first noticed that after reportbug syslog was strangely quiet, and sudo mailq does say: postqueue: warning: Mail system is down -- accessing queue directly Trying to start Postfix results in: Jul 15 22:40:24 tglase postfix/master[2632]: fatal: set_eugid: setgroups(137): Bad address This may be related to the setgroups fatal failure I’m reporting against OpenSSH :/ -- System Information: Debian Release: bullseye/sid APT prefers unreleased APT policy: (500, 'unreleased'), (500, 'buildd-unstable'), (500, 'unstable'), (100, 'experimental') Architecture: x32 (x86_64) Foreign Architectures: i386, amd64 Kernel: Linux 5.7.0-1-amd64 (SMP w/4 CPU threads) Kernel taint flags: TAINT_FIRMWARE_WORKAROUND Locale: LANG=C, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/lksh Init: sysvinit (via /sbin/init) Versions of packages postfix depends on: ii adduser3.118 ii cpio 2.13+dfsg-3 ii debconf [debconf-2.0] 1.5.74 ii dpkg 1.20.5 ii e2fsprogs 1.45.6-1 ii libc6 2.31-1 ii libdb5.3 5.3.28+dfsg1-0.6 ii libicu67 67.1-3 ii libsasl2-2 2.1.27+dfsg-2 ii libssl1.1 1.1.1g-1 ii lsb-base 11.1.0 ii netbase6.1 ii ssl-cert 1.0.39 Versions of packages postfix recommends: ii ca-bundle [ca-certificates] 20190604 ii python3 3.8.2-3 Versions of packages postfix suggests: ii bsd-mailx [mail-reader] 8.1.2-0.20180807cvs-1 ii libsasl2-modules 2.1.27+dfsg-2 pn postfix-cdb pn postfix-doc pn postfix-ldap pn postfix-lmdb pn postfix-mysql pn postfix-pcre pn postfix-pgsql pn postfix-sqlite pn procmail pn resolvconf pn ufw -- debconf information: postfix/procmail: false postfix/root_address: postfix/chattr: false postfix/destinations: tglase.lan.tarent.de, tglase.lan.tarent.de, localhost.lan.tarent.de, localhost postfix/main_cf_conversion_warning: true postfix/not_configured: postfix/compat_conversion_warning: true postfix/dynamicmaps_conversion_warning: postfix/protocols: all postfix/retry_upgrade_warning: * postfix/mailname: tglase.lan.tarent.de postfix/kernel_version_warning: postfix/rfc1035_violation: false postfix/mynetworks: 127.0.0.0/8 [:::127.0.0.0]/104 [::1]/128 postfix/tlsmgr_upgrade_warning: postfix/sqlite_warning: postfix/newaliases: false * postfix/main_mailer_type: Internet with smarthost postfix/bad_recipient_delimiter: * postfix/relayhost: mail.lixid.net postfix/mailbox_limit: 0 postfix/recipient_delim: + postfix/mydomain_warning: postfix/relay_restrictions_warning: postfix/lmtp_retired_warning: true --- End Message --- --- Begin Message --- Colin Watson dixit: >OK, thanks. I see you opened #965091, so it should be able to continue >there. Indeed. Same for the other bugreport, closing here. These were merely symptoms. bye, //mirabilos -- 18:47⎜ well channels… you see, I see everything in the same window anyway 18:48⎜ i know, you have some kind of telnet with automatic pong 18:48⎜ haha, yes :D 18:49⎜ though that's more tinyirc – sirc is more comfy--- End Message ---
Bug#965001: strange version 2.1.0 beta4 fails tests with mpfr4 4.1.0
On Tue, Jul 14, 2020, 3:15 AM Vincent Lefevre wrote:
> On 2020-07-14 09:48:18 +0200, Matthias Klose wrote:
> > There is no 2.1.0 beta4, just a beta1, so I don't know what was packaged
> in
> > February 2020. However the tests now fail with mpfr 4.1.0, seems to be
> > consistent across all architectures:
> >
> > **
> > File "test/test_gmpy2_format.txt", line 157, in test_gmpy2_format.txt
> > Failed example:
> > c.__format__('e')
> > Differences (ndiff with -expected +actual):
> > - '3.3331e-01+5e+00j'
> > + '3.3331e-01+5.e+00j'
> > ? +
>
> FYI, the old MPFR behavior was regarded as a bug:
>
>
> https://gforge.inria.fr/tracker/index.php?func=detail&aid=21816&group_id=136&atid=619
>
> There were 2 reasonable interpretations of the description in the
> MPFR manual that did not leave the output partly unspecified, and
> for each of them, some outputs were incorrect. The one that has
> been chosen is the one that is closer to ISO C's %e and it does
> not change the numerical output value (the only difference is
> trailing zeros).
>
> --
> Vincent Lefèvre - Web:
Bug#851771: php-gettext: CVE-2016-6175
I seem to have attached the wrong set of patches to this bug earlier.
Here are the correct ones. Upstream bug already has the correct set of
patches.
--
Sunil
From 0a325e7847daf150885911706926b7b8f5d7a66e Mon Sep 17 00:00:00 2001
From: Sunil Mohan Adapa
Date: Wed, 17 Jun 2020 14:07:30 -0700
Subject: [PATCH 1/2] Use custom parser for parsing plural expressions instead
of eval()
- A simple operator-precedence parser that prioritizes simplicity and
readability. Avoid using eval() for evaluating plural expressions.
- Fixes CVE-2016-6175.
- Fixes upstream bug https://bugs.launchpad.net/php-gettext/+bug/1606184
- Fixes Debian bug https://bugs.debian.org/851771
- Grammar for parsing code is same as the grammar for GNU gettext library:
http://git.savannah.gnu.org/cgit/gettext.git/tree/gettext-runtime/intl/plural.y
- Extensive tests for various locales with help from Unicode's plurals rules.
Tests for invalid syntax and expression parsing.
Signed-off-by: Sunil Mohan Adapa
---
Makefile | 4 +-
gettext.php | 53 +
plurals.php | 461 ++
tests/PluralsTest.php | 351
4 files changed, 823 insertions(+), 46 deletions(-)
create mode 100644 plurals.php
create mode 100644 tests/PluralsTest.php
diff --git a/Makefile b/Makefile
index b56394b..eda1408 100644
--- a/Makefile
+++ b/Makefile
@@ -5,6 +5,7 @@ DIST_FILES = \
gettext.php \
gettext.inc \
streams.php \
+ plurals.php \
AUTHORS \
README \
COPYING \
@@ -18,7 +19,8 @@ DIST_FILES = \
examples/locale/de_CH/LC_MESSAGES/messages.mo \
examples/update \
tests/LocalesTest.php \
- tests/ParsingTest.php
+ tests/ParsingTest.php \
+ tests/PluralsTest.php
check:
phpunit --verbose tests
diff --git a/gettext.php b/gettext.php
index 171d14e..0a121f7 100755
--- a/gettext.php
+++ b/gettext.php
@@ -21,6 +21,8 @@
*/
+require('plurals.php');
+
/**
* Provides a simple gettext replacement that works independently from
* the system's gettext abilities.
@@ -269,41 +271,6 @@ class gettext_reader {
}
}
- /**
- * Sanitize plural form expression for use in PHP eval call.
- *
- * @access private
- * @return string sanitized plural form expression
- */
- function sanitize_plural_expression($expr) {
-// Get rid of disallowed characters.
-$expr = preg_replace('@[^a-zA-Z0-9_:;\(\)\?\|\&=!<>+*/\%-]@', '', $expr);
-
-// Add parenthesis for tertiary '?' operator.
-$expr .= ';';
-$res = '';
-$p = 0;
-for ($i = 0; $i < strlen($expr); $i++) {
- $ch = $expr[$i];
- switch ($ch) {
- case '?':
-$res .= ' ? (';
-$p++;
-break;
- case ':':
-$res .= ') : (';
-break;
- case ';':
-$res .= str_repeat( ')', $p) . ';';
-$p = 0;
-break;
- default:
-$res .= $ch;
- }
-}
-return $res;
- }
-
/**
* Parse full PO header and extract only plural forms line.
*
@@ -330,14 +297,14 @@ class gettext_reader {
$this->load_tables();
// cache header field for plural forms
-if (! is_string($this->pluralheader)) {
+if ($this->pluralheader !== NULL) {
if ($this->enable_cache) {
$header = $this->cache_translations[""];
} else {
$header = $this->get_translation_string(0);
}
$expr = $this->extract_plural_forms_header_from_po_header($header);
- $this->pluralheader = $this->sanitize_plural_expression($expr);
+ $this->pluralheader = new PluralHeader($expr);
}
return $this->pluralheader;
}
@@ -354,16 +321,12 @@ class gettext_reader {
throw new InvalidArgumentException(
"Select_string only accepts integers: " . $n);
}
-$string = $this->get_plural_forms();
-$string = str_replace('nplurals',"\$total",$string);
-$string = str_replace("n",$n,$string);
-$string = str_replace('plural',"\$plural",$string);
+$plural_header = $this->get_plural_forms();
+$plural = $plural_header->expression->evaluate($n);
-$total = 0;
-$plural = 0;
+if ($plural < 0) $plural = 0;
+if ($plural >= $plural_header->total) $plural = $plural_header->total - 1;
-eval("$string");
-if ($plural >= $total) $plural = $total - 1;
return $plural;
}
diff --git a/plurals.php b/plurals.php
new file mode 100644
index 000..1c6ce12
--- /dev/null
+++ b/plurals.php
@@ -0,0 +1,461 @@
+
+
+ Drop in replacement for native gettext.
+
+ This file is part of PHP-gettext.
+
+ PHP-gettext is free software; you can redistribute it and/or modify
+ it under the terms of the GNU General Public License as published by
+ the Free Software Foundation; either version 2 of the License, or
+ (at your option) any later version.
+
+ PHP-gettext is distributed in the hope that it will be useful,
+ but WITHOUT ANY WARRANTY; without even the implied warranty of
+ MERCHANTABILITY or FIT
Bug#965086: marked as done (ssh: setgroups: Bad address [preauth])
Your message dated Wed, 15 Jul 2020 23:35:55 +0100 with message-id <20200715223555.gj2...@riva.ucam.org> and subject line Re: Bug#965086: ssh: setgroups: Bad address [preauth] has caused the Debian Bug report #965086, regarding ssh: setgroups: Bad address [preauth] 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.) -- 965086: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965086 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: openssh-server Version: 1:8.3p1-1 Severity: grave Justification: renders package unusable After an upgrade of libc6 today, I can no longer log into my system using ssh: tglase@tglase:~ $ ssh localhost Connection reset by 127.0.0.1 port 22 Jul 15 22:33:17 tglase sshd[27084]: fatal: setgroups: Bad address [preauth] More debugging: tglase@tglase:~ $ sudo cleanenv / /usr/sbin/sshd -p2000 -ddde debug2: load_server_config: filename /etc/ssh/sshd_config debug2: load_server_config: done config len = 329 debug2: parse_server_config_depth: config /etc/ssh/sshd_config len 329 debug2: /etc/ssh/sshd_config line 13: new include /etc/ssh/sshd_config.d/*.conf debug2: /etc/ssh/sshd_config line 13: no match for /etc/ssh/sshd_config.d/*.conf debug3: /etc/ssh/sshd_config:20 setting HostKey /etc/ssh/ssh_host_rsa_key debug3: /etc/ssh/sshd_config:63 setting ChallengeResponseAuthentication no debug3: /etc/ssh/sshd_config:86 setting UsePAM yes debug3: /etc/ssh/sshd_config:91 setting X11Forwarding yes debug3: /etc/ssh/sshd_config:95 setting PrintMotd no debug3: /etc/ssh/sshd_config:113 setting AcceptEnv LANG LC_* debug3: /etc/ssh/sshd_config:116 setting Subsystem sftp /usr/lib/openssh/sftp-server debug1: sshd version OpenSSH_8.3, OpenSSL 1.1.1g 21 Apr 2020 debug1: private host key #0: ssh-rsa SHA256:9ae2/1t8U30Savg3XisO1ZCDuaH8IXQm18FdLpW3g8M debug1: rexec_argv[0]='/usr/sbin/sshd' debug1: rexec_argv[1]='-p2000' debug1: rexec_argv[2]='-ddde' debug3: oom_adjust_setup debug1: Set /proc/self/oom_score_adj from 0 to -1000 debug2: fd 3 setting O_NONBLOCK debug1: Bind to port 2000 on 0.0.0.0. Server listening on 0.0.0.0 port 2000. debug2: fd 4 setting O_NONBLOCK debug3: sock_set_v6only: set socket 4 IPV6_V6ONLY debug1: Bind to port 2000 on ::. Server listening on :: port 2000. debug3: fd 5 is not O_NONBLOCK debug1: Server will not fork when running in debugging mode. debug3: send_rexec_state: entering fd = 8 config len 329 debug3: ssh_msg_send: type 0 debug3: send_rexec_state: done debug1: rexec start in 5 out 5 newsock 5 pipe -1 sock 8 debug3: recv_rexec_state: entering fd = 5 debug3: ssh_msg_recv entering debug3: recv_rexec_state: done debug2: parse_server_config_depth: config rexec len 329 debug2: parse_server_config_depth: config len 0 debug3: rexec:20 setting HostKey /etc/ssh/ssh_host_rsa_key debug3: rexec:63 setting ChallengeResponseAuthentication no debug3: rexec:86 setting UsePAM yes debug3: rexec:91 setting X11Forwarding yes debug3: rexec:95 setting PrintMotd no debug3: rexec:113 setting AcceptEnv LANG LC_* debug3: rexec:116 setting Subsystem sftp/usr/lib/openssh/sftp-server debug1: sshd version OpenSSH_8.3, OpenSSL 1.1.1g 21 Apr 2020 debug1: private host key #0: ssh-rsa SHA256:9ae2/1t8U30Savg3XisO1ZCDuaH8IXQm18FdLpW3g8M debug1: inetd sockets after dupping: 3, 3 Connection from 127.0.0.1 port 57626 on 127.0.0.1 port 2000 rdomain "" debug1: Local version string SSH-2.0-OpenSSH_8.3p1 Debian-1 debug1: Remote protocol version 2.0, remote software version OpenSSH_8.3p1 Debian-1 debug1: match: OpenSSH_8.3p1 Debian-1 pat OpenSSH* compat 0x0400 debug2: fd 3 setting O_NONBLOCK debug3: ssh_sandbox_init: preparing seccomp filter sandbox debug2: Network child is on pid 2057 debug3: preauth child monitor started debug3: privsep user:group 111:65534 [preauth] setgroups: Bad address [preauth] debug1: do_cleanup [preauth] debug3: PAM: sshpam_thread_cleanup entering [preauth] debug1: monitor_read_log: child log fd closed debug3: mm_request_receive entering debug1: do_cleanup debug3: PAM: sshpam_thread_cleanup entering debug1: Killing privsep child 2057 debug1: audit_event: unhandled event 12 -- System Information: Debian Release: bullseye/sid APT prefers unreleased APT policy: (500, 'unreleased'), (500, 'buildd-unstable'), (500, 'unstable'), (100, 'experimental') Architecture: x32 (x86_64) Foreign Architectures: i386, amd64 Kernel: Linux 5.7.0-1-amd64 (SMP w/4 CPU threads) Kernel taint flags: TAINT_FIRMWARE_WORKAROUND Locale: LANG=C, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/lksh Init: sysvinit (via /sbin/init) Versions of p
Bug#965086: ssh: setgroups: Bad address [preauth]
Hi Colin, >sshd.c:privsep_preauth_child. But its setgroups() call seems >straightforward, and I don't see how it could produce EFAULT: thanks for also looking at it, yes, I tracked it down in gdb, and the __nptl_setxid code is compiled differently, and I’m fresh out of ideas how to track it further down, but yes, this is most likely a bug in only glibc, so closing this one is probably right. Sorry for the noise, it’s where I first detected it, and I feared something with seccomp or so happened again. For now, I downgraded glibc, so the system is at all reachable. bye, //mirabilos -- tarent solutions GmbH Rochusstraße 2-4, D-53123 Bonn • http://www.tarent.de/ Tel: +49 228 54881-393 • Fax: +49 228 54881-235 HRB 5168 (AG Bonn) • USt-ID (VAT): DE122264941 Geschäftsführer: Dr. Stefan Barth, Kai Ebenrett, Boris Esser, Alexander Steeg
Bug#965091: glibc: setgroups: Bad address [2.31/x32, regression from 2.30]
> So something clearly changed…
Compiler output, most probably. I cannot reproduce it. I tried:
struct xid_command
{
int syscall_no;
long int id[3];
volatile int cntr;
volatile int error; /* -1: no call yet, 0: success seen, >0: error
seen. */
};
extern void a_barrier(int *);
# define REGISTERS_CLOBBERED_BY_SYSCALL "cc", "r11", "cx"
/* NB: This also works when X is an array. For an array X, type of
(X) - (X) is ptrdiff_t, which is signed, since size of ptrdiff_t
== size of pointer, cast is a NOP. */
#define TYPEFY1(X) __typeof__ ((X) - (X))
/* Explicit cast the argument. */
#define ARGIFY(X) ((TYPEFY1 (X)) (X))
/* Create a variable 'name' based on type of variable 'X' to avoid
explicit types. */
#define TYPEFY(X, name) __typeof__ (ARGIFY (X)) name
#undef INTERNAL_SYSCALL_NCS
#define INTERNAL_SYSCALL_NCS(number, err, nr, args...)
\
internal_syscall##nr (number, err, args)
#undef internal_syscall3
#define internal_syscall3(number, err, arg1, arg2, arg3)
\
({
\
unsigned long int resultvar;
\
TYPEFY (arg3, __arg3) = ARGIFY (arg3);
\
TYPEFY (arg2, __arg2) = ARGIFY (arg2);
\
TYPEFY (arg1, __arg1) = ARGIFY (arg1);
\
register TYPEFY (arg3, _a3) asm ("rdx") = __arg3;
\
register TYPEFY (arg2, _a2) asm ("rsi") = __arg2;
\
register TYPEFY (arg1, _a1) asm ("rdi") = __arg1;
\
asm volatile (
\
"syscall\n\t"
\
: "=a" (resultvar)
\
: "0" (number), "r" (_a1), "r" (_a2), "r" (_a3)
\
: "memory", REGISTERS_CLOBBERED_BY_SYSCALL);
\
(long int) resultvar;
\
})
int
foo(struct xid_command *cmdp)
{
int result;
asm volatile ("xor rsi,rsi\n\txor rdi,rdi" : : : "rsi", "rdi");
result = INTERNAL_SYSCALL_NCS (cmdp->syscall_no, err, 3,
cmdp->id[0], cmdp->id[1], cmdp->id[2]);
a_barrier(&result);
return result;
}
Save as x.c then:
x86_64-linux-gnux32-gcc-10 -c -std=gnu11 -fgnu89-inline -pipe -O2 -g -Wall
-Wwrite-strings -Wundef -Werror -fmerge-all-constants -frounding-math
-fstack-protector-strong -Wstrict-prototypes -Wold-style-definition
-fmath-errno -fpie -ftls-model=initial-exec -D_LIBC_REENTRANT -DPIC -S
-masm=intel x.c -Wno-error
This doesn’t yield any “movsxd” in the output, like in glibc, though:
b32: 67 48 63 73 08 movsxd rsi,DWORD PTR [ebx+0x8]
b37: 67 48 63 7b 04 movsxd rdi,DWORD PTR [ebx+0x4]
b3c: 67 48 63 53 0c movsxd rdx,DWORD PTR [ebx+0xc]
b41: 67 8b 03moveax,DWORD PTR [ebx]
b44: 0f 05 syscall
(disassembly of pthread_create.o from libpthread.a 2.31)
I’m unsure whether this is a glibc or gcc issue… without a reproducer
I’m stuck.
I’ll have to downgrade to 2.30 for now, to keep the system ssh-in-able…
bye,
//mirabilos
--
tarent solutions GmbH
Rochusstraße 2-4, D-53123 Bonn • http://www.tarent.de/
Tel: +49 228 54881-393 • Fax: +49 228 54881-235
HRB 5168 (AG Bonn) • USt-ID (VAT): DE122264941
Geschäftsführer: Dr. Stefan Barth, Kai Ebenrett, Boris Esser, Alexander Steeg
Bug#965073: marked as done (macs: shared library is not properly linked with libm)
Your message dated Wed, 15 Jul 2020 22:03:39 +
with message-id
and subject line Bug#965073: fixed in macs 2.2.7.1-3
has caused the Debian Bug report #965073,
regarding macs: shared library is not properly linked with libm
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.)
--
965073: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965073
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: macs
Version: 2.2.7.1-2
Severity: serious
Tags: patch
macs use the log() math function, but doesn't link link with libm.so.
This causes the non-versioned __log_finite symbol to be used, which in
turn causes issues when glibc version is upgraded:
https://ci.debian.net/data/autopkgtest/testing/amd64/m/macs/6261687/log.gz
The attached patch fixes that.
--- macs-2.2.7.1.orig/setup.py
+++ macs-2.2.7.1/setup.py
@@ -59,8 +59,8 @@ def main():
Extension("MACS2.IO.FixWidthTrack",
["MACS2/IO/FixWidthTrack.pyx"], include_dirs=numpy_include_dir,
extra_compile_args=extra_c_args),
Extension("MACS2.IO.PairedEndTrack",
["MACS2/IO/PairedEndTrack.pyx"], include_dirs=numpy_include_dir,
extra_compile_args=extra_c_args),
Extension("MACS2.IO.BedGraph", ["MACS2/IO/BedGraph.pyx"],
libraries=["m"], extra_compile_args=extra_c_args),
- Extension("MACS2.IO.ScoreTrack",
["MACS2/IO/ScoreTrack.pyx"], include_dirs=numpy_include_dir,
extra_compile_args=extra_c_args ),
- Extension("MACS2.IO.CallPeakUnit",
["MACS2/IO/CallPeakUnit.pyx"], include_dirs=numpy_include_dir,
extra_compile_args=extra_c_args),
+ Extension("MACS2.IO.ScoreTrack",
["MACS2/IO/ScoreTrack.pyx"], libraries=["m"], include_dirs=numpy_include_dir,
extra_compile_args=extra_c_args ),
+ Extension("MACS2.IO.CallPeakUnit",
["MACS2/IO/CallPeakUnit.pyx"], libraries=["m"], include_dirs=numpy_include_dir,
extra_compile_args=extra_c_args),
#Extension("MACS2.Statistics", ["MACS2/Statistics.pyx"],
libraries=["m"], include_dirs=["MACS2/",numpy_get_include()],
extra_compile_args=extra_c_args),
]
--- End Message ---
--- Begin Message ---
Source: macs
Source-Version: 2.2.7.1-3
Done: Andreas Tille
We believe that the bug you reported is fixed in the latest version of
macs, 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 965...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Andreas Tille (supplier of updated macs 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, 15 Jul 2020 23:27:39 +0200
Source: macs
Architecture: source
Version: 2.2.7.1-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team
Changed-By: Andreas Tille
Closes: 965073
Changes:
macs (2.2.7.1-3) unstable; urgency=medium
.
* Link properly with libm
Closes: #965073
* debhelper-compat 13 (routine-update)
Checksums-Sha1:
c8901732b20445ba74b95e2567c182c35a9fc2a6 2102 macs_2.2.7.1-3.dsc
68332c8e20356ed0356364a6d105054abe97f324 1267660 macs_2.2.7.1-3.debian.tar.xz
815a5862d34da3ddec8e8df674330d658c80a7c2 7252 macs_2.2.7.1-3_amd64.buildinfo
Checksums-Sha256:
1ad42909d66d5530a6db80a5f28897b2e8acb3b2436760bf1f1bd6e73ff8ce1b 2102
macs_2.2.7.1-3.dsc
ec8667e7d3c85f3de72a87238266236470dd8c04a5631ad0f75f31545f5ee6f5 1267660
macs_2.2.7.1-3.debian.tar.xz
07014944a3f38cc4b580eb0e32dc63ceb309c8c10969aa1430f34982f31b69d3 7252
macs_2.2.7.1-3_amd64.buildinfo
Files:
31b785b4272776fb74179acdc148afb6 2102 science optional macs_2.2.7.1-3.dsc
c1b0b0f58baae3f2d4cf1221dc19e46f 1267660 science optional
macs_2.2.7.1-3.debian.tar.xz
e45af06503361f208cfc0e584f9bba82 7252 science optional
macs_2.2.7.1-3_amd64.buildinfo
-BEGIN PGP SIGNATURE-
iQJFBAEBCgAvFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAl8PecARHHRpbGxlQGRl
Ymlhbi5vcmcACgkQV4oElNHGRtFvvQ//VCNVqsBVewQj2nh7kf99O2dg0/Cwx9BV
PJy0U2pGxxdbh3UGG6+T5lulUSlp2B/qVfY2013h4Q8OjkHnQYQ3wiiqsU62+mTa
hnHhtPDHyA1sMxQzK1Dpg+4LYWffccofN3BHdNoIhRkpcJypuPkgPWE3ZtTBSWCr
3F6KwdlTo4G9r64IF2uDeSSZlV+D3764ooI/MmLkVHvwoPP/4luZ8B/D9eqLeqe4
3Q1ye0byj4m/UFcObGkGMxX6h+qNsBJWFqIIjUGidAcHkKGEL6+epjM+TpCb
Bug#961852: marked as done (python-matrix-nio: autopkgtest failure: No module named 'matrix_nio')
Your message dated Wed, 15 Jul 2020 22:03:49 + with message-id and subject line Bug#961852: fixed in python-matrix-nio 0.12.0-2 has caused the Debian Bug report #961852, regarding python-matrix-nio: autopkgtest failure: No module named 'matrix_nio' 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.) -- 961852: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=961852 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: python-matrix-nio Version: 0.11.2-2 X-Debbugs-CC: debian...@lists.debian.org Severity: serious User: debian...@lists.debian.org Usertags: fails-always Dear maintainer(s), You recently added an autopkgtest to your package python-matrix-nio, great. However, it fails. Currently this failure is blocking the migration to testing [1]. Can you please investigate the situation and fix it? I copied some of the output at the bottom of this report. You're using autodep8 to trigger the test, but it seems your package naming and Python module name aren't aligned for autodep8. autodep8 recently acquired a new feature that enables you to tell autode8 what the real module name is that should be tested [2]. More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [1] https://qa.debian.org/excuses.php?package=python-matrix-nio [2] https://manpages.debian.org/unstable/autodep8/autodep8.1.en.html#PYTHON_PACKAGES https://ci.debian.net/data/autopkgtest/testing/amd64/p/python-matrix-nio/5580919/log.gz autopkgtest [15:19:47]: test autodep8-python3: set -e ; for py in $(py3versions -r 2>/dev/null) ; do cd "$AUTOPKGTEST_TMP" ; echo "Testing with $py:" ; $py -c "import matrix_nio; print(matrix_nio)" ; done autopkgtest [15:19:47]: test autodep8-python3: [--- Testing with python3.8: Traceback (most recent call last): File "", line 1, in ModuleNotFoundError: No module named 'matrix_nio' autopkgtest [15:19:48]: test autodep8-python3: ---] signature.asc Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Source: python-matrix-nio Source-Version: 0.12.0-2 Done: Johannes 'josch' Schauer We believe that the bug you reported is fixed in the latest version of python-matrix-nio, 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 961...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Johannes 'josch' Schauer (supplier of updated python-matrix-nio 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: Wed, 15 Jul 2020 23:43:14 +0200 Source: python-matrix-nio Architecture: source Version: 0.12.0-2 Distribution: unstable Urgency: medium Maintainer: Matrix Packaging Team Changed-By: Johannes 'josch' Schauer Closes: 961852 Changes: python-matrix-nio (0.12.0-2) unstable; urgency=medium . [ Johannes 'josch' Schauer ] * Team upload. . [ Henry-Nicolas Tourneur ] * autopkgtest-pkg-python: use correct module name (closes: #961852) Checksums-Sha1: 1949e10ee592e3ee5f3ca7371283cac7dc11dcfc 3114 python-matrix-nio_0.12.0-2.dsc 040228c67e3a8a8973f4dfe2fefa4cc6796d514a 7456 python-matrix-nio_0.12.0-2.debian.tar.xz Checksums-Sha256: a043b202f55e7646b5bd6954939038681595fca51907f854d56a6297e482ed7f 3114 python-matrix-nio_0.12.0-2.dsc 5e4f7923b1f2e04e3abd7d49b4c3305e37a3a2a0634bd495a2dc4fb1b27def7f 7456 python-matrix-nio_0.12.0-2.debian.tar.xz Files: de8fc752e854013e3f42880fea35cd28 3114 python optional python-matrix-nio_0.12.0-2.dsc 282449b61cbeaea61ae5317bda3af922 7456 python optional python-matrix-nio_0.12.0-2.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEElFhU6KL81LF4wVq58sulx4+9g+EFAl8PeXUACgkQ8sulx4+9 g+E9UA//fiyccrgm/P5zkjt0/mBMsdSHflo9kL5hKFzHndYv6stoFejabrzl8WDd 4H06ECOzrBIOKyax4j6aLnxBqtniLF7Hj+Cg0Wubyn/061ItTZADEaTcJ+I9Ah2l HgjbDpNAMMyPUkVdS+rHu94SoQ0ld4G7ILEwcF1PXKFExFYksvGfvDEshGluDnnG 8APGlC0NOHA1v3ZOmh43po+c3ewo2hWIOfLIpyV5Nu/YKHtiot/C2zgYcW6YnaAM PVe/gXXgfSdzixFa903BJRDA3HDwpH6xeA2nF9ARnMCu5lQGO/fVyq6fNHhqZbic 5n73pdINpSTiC6yX2/c0Lq7egGfs9s3daQ52vMN8oOSCJliCBxKsT+Rtz7hsGusp rW939BS7MilO4TESx+4TPUn1Fk/6CEimV
Bug#965091: glibc: setgroups: Bad address [2.31/x32, regression from 2.30]
Some more analysis: We enter libc from openssh code with the correct values in rsi and rdi: (gdb) u => 0x56560e45 : call 0x5655d0b0 (gdb) info r rax0xfffe 65534 rbx0x5663a000 1449369600 rcx0x0 0 rdx0x0 0 rsi0xd2e0 4294955744 rdi0x1 1 rbp0x56641b50 1449401168 rsp0xd260 4294955616 r8 0x0 0 r9 0x0 0 r100xf7a8 4155017352 r110x246 582 r120x565d71d1 1448964561 r130x3 3 r140xe2cc 58060 r150x5663c730 1449379632 rip0x56560e45 1448480325 eflags 0x282 [ SF IF ] cs 0x3351 ss 0x2b43 ds 0x2b43 es 0x2b43 fs 0x0 0 gs 0x0 0 Inside glibc, there’s an indirect call: => 0xf79949f4 <__GI_setgroups+100>: call rax rax0xf7833500 4152571136 => 0xf7833500 <__nptl_setxid>: push r15 Some time in __nptl_setxid later, here’s the bug: 1162in allocatestack.c rax0xf77ca840 4152141888 rbx0xd230 4294955568 rcx0x0 0 rdx0x1 1 rsi0xd2e0 4294955744 rdi0xf77ca840 4152141888 rbp0xf77ca840 4152141888 rsp0xd1d0 4294955472 r8 0x0 0 r9 0x0 0 r100xf77caac0 4152142528 r110x246 582 r120xf784a360 4152664928 r130xf784a360 4152664928 r140xf78482c8 4152656584 r150x40ca 1073742026 rip0xf7833752 4152571730 eflags 0x246 [ PF ZF IF ] cs 0x3351 ss 0x2b43 ds 0x2b43 es 0x2b43 fs 0x0 0 gs 0x0 0 => 0xf7833752 <__nptl_setxid+594>: movsxd rsi,DWORD PTR [ebx+0x8] 0xf7833757 <__nptl_setxid+599>: movsxd rdi,DWORD PTR [ebx+0x4] 0xf783375c <__nptl_setxid+604>: movsxd rdx,DWORD PTR [ebx+0xc] (gdb) t => 0xf7833752 <__nptl_setxid+594>: movsxd rsi,DWORD PTR [ebx+0x8] 1162in allocatestack.c rax0xf77ca840 4152141888 rbx0xd230 4294955568 rcx0x0 0 rdx0x1 1 rsi0xd2e0 -11552 rdi0xf77ca840 4152141888 rbp0xf77ca840 4152141888 rsp0xd1d0 4294955472 r8 0x0 0 r9 0x0 0 r100xf77caac0 4152142528 r110x246 582 r120xf784a360 4152664928 r130xf784a360 4152664928 r140xf78482c8 4152656584 r150x40ca 1073742026 rip0xf7833757 4152571735 eflags 0x246 [ PF ZF IF ] cs 0x3351 ss 0x2b43 ds 0x2b43 es 0x2b43 fs 0x0 0 gs 0x0 0 Looking at the next instructions… => 0xf7833757 <__nptl_setxid+599>: movsxd rdi,DWORD PTR [ebx+0x4] 0xf783375c <__nptl_setxid+604>: movsxd rdx,DWORD PTR [ebx+0xc] 0xf7833761 <__nptl_setxid+609>: moveax,DWORD PTR [ebx] 0xf7833764 <__nptl_setxid+612>: syscall … this most likely corresponds to this C source: 1162 result = INTERNAL_SYSCALL_NCS (cmdp->syscall_no, err, 3, 1163 cmdp->id[0], cmdp->id[1], cmdp->id[2]); Diffing glibc-2.30..glibc-2.31 shows no noticeable delta in nptl/allocatestack.c so going on. struct xid_command (nptl/descr.h) also did not change. Looking at pthread_create.o (whyever this is the file __nptl_setxid ends up being in) from 2.30-8, the code in question looks like this: c3d: 67 8b 75 08 movesi,DWORD PTR [ebp+0x8] c41: 67 8b 7d 04 movedi,DWORD PTR [ebp+0x4] c45: 67 8b 55 0c movedx,DWORD PTR [ebp+0xc] c49: 67 8b 45 00 moveax,DWORD PTR [ebp+0x0] c4d: 0f 05 syscall So something clearly changed… //mirabilos -- tarent solutions GmbH Rochusstraße 2-4, D-53123 Bonn • http://www.tarent.de/ Tel: +49 228
Bug#964631: diagnostics: FTBFS: FAIL: stacktrace
On Thu, Jul 09, 2020 at 01:08:43PM +0200, Lucas Nussbaum wrote: > Source: diagnostics > Version: 0.3.3-12 > Severity: serious > Justification: FTBFS on amd64 > Tags: bullseye sid ftbfs > Usertags: ftbfs-20200709 ftbfs-bullseye > > Hi, > > During a rebuild of all packages in sid, your package failed to build > on amd64. I was curious to see why it failed and did a bisect based on the snapshots. It built fine with the snapshot of 20200706T204334Z but failed with the snapshot of 20200707T024523Z. And the only change between these two snapshot was 'binutils' which moved to 2.34.90.20200706-1. Any idea what might have caused this? -- Regards Sudip
Bug#959981: marked as done (Trademark issues with Chef/Cinc package included in Debian)
Your message dated Wed, 15 Jul 2020 21:36:50 + with message-id and subject line Bug#963750: Removed package(s) from unstable has caused the Debian Bug report #959981, regarding Trademark issues with Chef/Cinc package included in Debian 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.) -- 959981: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=959981 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: chef Version: 15.8.25.3.gcf41df6a2-6 Severity: serious X-Debbugs-CC: la...@osuosl.org, maintain...@cinc.sh, be...@chef.io - Forwarded message from Lance Albertson - Date: Thu, 7 May 2020 11:40:38 -0700 From: Lance Albertson To: pkg-ruby-extras-maintain...@lists.alioth.debian.org, terce...@debian.org, ubuntu-m...@lists.ubuntu.com Cc: maintain...@cinc.sh, be...@chef.io Subject: Trademark concerns with Chef/Cinc package included in Debian and Ubuntu X-Spam-Level: X-Spam-Status: No, score=0.5 required=3.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,HTML_MESSAGE,SPF_SOFTFAIL,URIBL_BLOCKED,URIBL_SBL, URIBL_SBL_A autolearn=no autolearn_force=no version=3.4.2 Message-ID: All, I'm a member of the Cinc Project [1] which rebuilds and rebrands various Chef projects to comply with Chef Trademark Policy [2]. We have worked closely with Chef to ensure Cinc Client complies with this policy. A member of our community notified us today that it appears that Ubuntu [3] and Debian [4] are both including a package called "chef" which seems to pull in the Cinc source code but doesn't fully comply with the Chef Trademark Policy. We are concerned that this use of the Cinc Client in the manner it's currently presented will create an issue for us and you in the future unless this gets resolved quickly. Specifically, we are concerned with the following: 1. The package name should be cinc and not chef as Chef is trademarked and also causes users to think they are installing Chef when they are installing Cinc 2. The package should have proper attributions to include the Cinc Project including pointing any issues related to the package to our issue page, and not Chef 2. Running "chef-client" (or other similar commands) does not tell the user that it's actually using Cinc Client as our package does properly 3. All of the trademark renaming we did in our Cinc Client distribution seems to have been removed and retains all of the Chef related paths (i.e. /etc/chef when it should be /etc/cinc). This will cause confusion for users who are expecting Cinc. We would like to work with the Debian/Ubuntu maintainers to ensure you're following compliance and also ensuring our distribution works well on Debian/Ubuntu. However we also want to ensure you don't get into any legal trouble with Chef. I am sure most of these changes weren't done intentionally and was a mistake. Feel free to reach out to us via the #community-distros channel on the Chef Community Slack, or you can reach me directly via IRC on Freenode as "Ramereth". I've also cc'd Benny Vasquez who is a community manager at Chef who can answer any questions relating to this and provide any additional feedback. Thanks! [1] https://cinc.sh/ [2] https://www.chef.io/trademark-policy/ [3] https://packages.ubuntu.com/focal/chef [4] https://packages.debian.org/sid/chef -- Lance Albertson Director Oregon State University | Open Source Lab - End forwarded message - signature.asc Description: PGP signature --- End Message --- --- Begin Message --- Version: 15.8.25.3.gcf41df6a2-6+rm Dear submitter, as the package chef has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/963750 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Sean Whitton (the ftpmaster behind the curtain)--- End Message ---
Bug#964653: marked as done (freeimage: FTBFS: Source/FreeImage/PluginJPEG.cpp:506:1: error: ‘BOOL jpeg_read_icc_profile(j_decompress_ptr, JOCTET**, unsigned int*)’ was declared ‘extern’ and later ‘sta
Your message dated Wed, 15 Jul 2020 21:33:46 +
with message-id
and subject line Bug#964653: fixed in freeimage 3.18.0+ds2-4
has caused the Debian Bug report #964653,
regarding freeimage: FTBFS: Source/FreeImage/PluginJPEG.cpp:506:1: error: ‘BOOL
jpeg_read_icc_profile(j_decompress_ptr, JOCTET**, unsigned int*)’ was declared
‘extern’ and later ‘static’ [-fpermissive]
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.)
--
964653: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964653
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: freeimage
Version: 3.18.0+ds2-3
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200709 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> x86_64-linux-gnu-g++ -g -O2 -fdebug-prefix-map=/<>=.
> -specs=/usr/share/dpkg/no-pie-compile.specs -fstack-protector-strong -Wformat
> -Werror=format-security -Wall -pedantic -fPIC -fexceptions
> -fvisibility=hidden -Wno-ctor-dtor-privacy -D__ANSI__ -I. -ISource
> -ISource/Metadata -ISource/FreeImageToolkit -ISource/LibJPEG -ISource/LibPNG
> -ISource/LibTIFF4 -ISource/ZLib -ISource/LibOpenJPEG -ISource/OpenEXR
> -ISource/OpenEXR/Half -ISource/OpenEXR/Iex -ISource/OpenEXR/IlmImf
> -ISource/OpenEXR/IlmThread -ISource/OpenEXR/Imath -ISource/OpenEXR/IexMath
> -ISource/LibRawLite -ISource/LibRawLite/dcraw -ISource/LibRawLite/internal
> -ISource/LibRawLite/libraw -ISource/LibRawLite/src -ISource/LibWebP
> -ISource/LibJXR -ISource/LibJXR/common/include -ISource/LibJXR/image/sys
> -ISource/LibJXR/jxrgluelib -I/usr/include/jxrlib -I/usr/include/openjpeg-2.3
> -I/usr/include/libpng16 -I/usr/include/libraw -I/usr/include/x86_64-linux-gnu
> -I/usr/include/OpenEXR -Wdate-time -D_FORTIFY_SOURCE=2 -c
> Source/FreeImage/PluginJPEG.cpp -o Source/FreeImage/PluginJPEG.o
> Source/FreeImage/PluginJPEG.cpp:506:1: error: ‘BOOL
> jpeg_read_icc_profile(j_decompress_ptr, JOCTET**, unsigned int*)’ was
> declared ‘extern’ and later ‘static’ [-fpermissive]
> 506 | jpeg_read_icc_profile(j_decompress_ptr cinfo, JOCTET **icc_data_ptr,
> unsigned *icc_data_len) {
> | ^
> In file included from Source/FreeImage/PluginJPEG.cpp:39:
> /usr/include/jpeglib.h:1066:17: note: previous declaration of ‘boolean
> jpeg_read_icc_profile(j_decompress_ptr, JOCTET**, unsigned int*)’
> 1066 | EXTERN(boolean) jpeg_read_icc_profile(j_decompress_ptr cinfo,
> | ^
> Source/FreeImage/PluginJPEG.cpp: In function ‘BOOL
> jpeg_write_jfxx(j_compress_ptr, FIBITMAP*)’:
> Source/FreeImage/PluginJPEG.cpp:962:93: warning: suggest parentheses around
> ‘&&’ within ‘||’ [-Wparentheses]
> 962 | if((FreeImage_GetImageType(thumbnail) != FIT_BITMAP) ||
> (FreeImage_GetBPP(thumbnail) != 8) && (FreeImage_GetBPP(thumbnail) != 24)) {
> |
> ~~~^~
> In file included from Source/FreeImage/PluginJPEG.cpp:44:
> Source/Utilities.h: At global scope:
> Source/Utilities.h:533:20: warning: ‘FI_MSG_ERROR_UNSUPPORTED_COMPRESSION’
> defined but not used [-Wunused-variable]
> 533 | static const char *FI_MSG_ERROR_UNSUPPORTED_COMPRESSION =
> "Unsupported compression type";
> |^~~~
> Source/Utilities.h:532:20: warning: ‘FI_MSG_ERROR_UNSUPPORTED_FORMAT’ defined
> but not used [-Wunused-variable]
> 532 | static const char *FI_MSG_ERROR_UNSUPPORTED_FORMAT = "Unsupported
> format";
> |^~~
> Source/Utilities.h:531:20: warning: ‘FI_MSG_ERROR_MAGIC_NUMBER’ defined but
> not used [-Wunused-variable]
> 531 | static const char *FI_MSG_ERROR_MAGIC_NUMBER = "Invalid magic number";
> |^
> Source/Utilities.h:530:20: warning: ‘FI_MSG_ERROR_PARSING’ defined but not
> used [-Wunused-variable]
> 530 | static const char *FI_MSG_ERROR_PARSING = "Parsing error";
> |^~~~
> make[3]: *** [Makefile.gnu:66: Source/FreeImage/PluginJPEG.o] Error 1
The full build log is available from:
http://qa-logs.debian.net/2020/07/09/freeimage_3.18.0+ds2-3_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!
About the archive rebuild: The rebuild was done on EC2 VM instances from
Bug#965086: ssh: setgroups: Bad address [preauth]
On Wed, Jul 15, 2020 at 10:41:11PM +0200, Thorsten Glaser wrote:
> Package: openssh-server
> Version: 1:8.3p1-1
> Severity: grave
> Justification: renders package unusable
>
> After an upgrade of libc6 today, I can no longer log into my
> system using ssh:
Would it perhaps make sense to reassign this to libc6 first, unless and
until it seems to be a definite bug in OpenSSH? I'd have thought that
this sort of compatibility break would be a glibc bug in any event (if
nothing else it'd need a Breaks even if the fix is in OpenSSH), perhaps
unless OpenSSH is doing something clearly undefined.
Looking at your -ddd output, the failure must be within
sshd.c:privsep_preauth_child. But its setgroups() call seems
straightforward, and I don't see how it could produce EFAULT:
gid_t gidset[1];
[...]
gidset[0] = privsep_pw->pw_gid;
if (setgroups(1, gidset) == -1)
fatal("setgroups: %.100s", strerror(errno));
Is it possible that this is x32-specific in some way? I haven't been
able to reproduce it on amd64 so far. The implementation of setgroups()
also doesn't seem to have changed between the glibc-2.30 and glibc-2.31
tags upstream, though I haven't looked at the Debian patches.
--
Colin Watson (he/him) [cjwat...@debian.org]
Bug#965091: glibc: setgroups: Bad address [2.31/x32, regression from 2.30]
Package: libc6
Version: 2.31-1
Severity: grave
Justification: renders package unusable
This is related to #965086 and #965087 (and, in fact, possibly
causing them). After a glibc upgrade half the system services
(postfix, sshd, apt-get(!)) don’t work any more.
Downgrading with dpkg -i the following set of packages fixes it:
libc-bin_2.30-8_x32.deb
libc-dev-bin_2.30-8_x32.deb
libc-l10n_2.30-8_all.deb
libc6-dbg_2.30-8_x32.deb
libc6-dev_2.30-8_x32.deb
libc6_2.30-8_amd64.deb
libc6_2.30-8_i386.deb
libc6_2.30-8_x32.deb
locales-all_2.30-8_x32.deb
locales_2.30-8_all.deb
unscd_0.53-1+b3_x32.deb
Snippet from strace:
[…]
9839 getpid() = 9839
9839 chroot("/run/sshd") = 0
9839 chdir("/")= 0
9839 write(7, "\0\0\0$\0\0\0\7\0\0\0\34privsep user:group 1"..., 40) = 40
9839 setgroups(1, 0xff866750
9794 <... poll resumed>) = 1 ([{fd=6, revents=POLLIN}])
9839 <... setgroups resumed>) = -1 EFAULT (Bad address)
9794 read(6,
9839 write(7, "\0\0\0\36\0\0\0\1\0\0\0\26setgroups: Bad addre"..., 34
[…]
Noticeable: the sign-extended address.
I haven’t yet managed to reproduce this in a stand-alone program.
-- System Information:
Debian Release: bullseye/sid
APT prefers unreleased
APT policy: (500, 'unreleased'), (500, 'buildd-unstable'), (500, 'unstable'),
(100, 'experimental')
Architecture: x32 (x86_64)
Foreign Architectures: i386, amd64
Kernel: Linux 5.7.0-1-amd64 (SMP w/4 CPU threads)
Kernel taint flags: TAINT_FIRMWARE_WORKAROUND
Locale: LANG=C, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/lksh
Init: sysvinit (via /sbin/init)
Versions of packages libc6 depends on:
ii libcrypt1 1:4.4.16-1
ii libgcc-s1 10.1.0-6
Versions of packages libc6 recommends:
ii libidn2-0 2.3.0-1
Versions of packages libc6 suggests:
ii debconf [debconf-2.0] 1.5.74
ii glibc-doc 2.31-1
ii libc-l10n 2.31-1
ii locales2.31-1
-- debconf information:
glibc/disable-screensaver:
* libraries/restart-without-asking: true
glibc/restart-failed:
glibc/kernel-too-old:
* glibc/upgrade: true
* glibc/restart-services: postfix openbsd-inetd cups cron
glibc/kernel-not-supported:
Processed: gst-plugins-bad1.0: diff for NMU version 1.16.2-2.2
Processing control commands:
> tags 962720 + pending
Bug #962720 {Done: Adrian Bunk } [src:gst-plugins-bad1.0]
gst-plugins-bad1.0: FTBFS in sid
Added tag(s) pending.
--
962720: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962720
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#962720: gst-plugins-bad1.0: diff for NMU version 1.16.2-2.2
Control: tags 962720 + pending
Dear maintainer,
I've prepared an NMU for gst-plugins-bad1.0 (versioned as 1.16.2-2.2) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should delay it longer.
Cheers
--
Sebastian Ramacher
diff -Nru gst-plugins-bad1.0-1.16.2/debian/build-deps gst-plugins-bad1.0-1.16.2/debian/build-deps
--- gst-plugins-bad1.0-1.16.2/debian/build-deps 2019-12-04 14:34:03.0 +0100
+++ gst-plugins-bad1.0-1.16.2/debian/build-deps 2020-07-15 22:55:32.0 +0200
@@ -64,7 +64,7 @@
libsndfile1-dev (>= 1.0.16)
libsoundtouch-dev (>= 1.5.0)
libspandsp-dev
-libsrt-dev
+libsrt-gnutls-dev
libsrtp2-dev (>= 2.1)
libssl-dev
libtool (>= 2.2.6)
diff -Nru gst-plugins-bad1.0-1.16.2/debian/build-deps.in gst-plugins-bad1.0-1.16.2/debian/build-deps.in
--- gst-plugins-bad1.0-1.16.2/debian/build-deps.in 2019-12-04 14:34:01.0 +0100
+++ gst-plugins-bad1.0-1.16.2/debian/build-deps.in 2020-07-15 22:48:09.0 +0200
@@ -80,6 +80,6 @@
libopenmpt-dev
libnice-dev (>= 0.1.14)
libpango1.0-dev (>= 1.22)
-libsrt-dev
+libsrt-gnutls-dev
libaom-dev
libusrsctp-dev
diff -Nru gst-plugins-bad1.0-1.16.2/debian/changelog gst-plugins-bad1.0-1.16.2/debian/changelog
--- gst-plugins-bad1.0-1.16.2/debian/changelog 2020-02-05 22:46:23.0 +0100
+++ gst-plugins-bad1.0-1.16.2/debian/changelog 2020-07-15 22:56:22.0 +0200
@@ -1,3 +1,16 @@
+gst-plugins-bad1.0 (1.16.2-2.2) unstable; urgency=medium
+
+ * Non-maintainer upload.
+
+ [ Gianfranco Costamagna ]
+ * Replace libsrt-dev with libsrt-gnutls-dev
+ * Fix build with make 4.3 (Closes: #962720)
+
+ [ Sebastian Ramacher ]
+ * Apply upstream patch to build with new vulkan
+
+ -- Sebastian Ramacher Wed, 15 Jul 2020 22:56:22 +0200
+
gst-plugins-bad1.0 (1.16.2-2.1) unstable; urgency=medium
* Non-maintainer upload.
diff -Nru gst-plugins-bad1.0-1.16.2/debian/control gst-plugins-bad1.0-1.16.2/debian/control
--- gst-plugins-bad1.0-1.16.2/debian/control 2019-12-04 14:34:03.0 +0100
+++ gst-plugins-bad1.0-1.16.2/debian/control 2020-07-15 22:55:32.0 +0200
@@ -29,7 +29,6 @@
libdrm-dev (>= 2.4.55) [linux-any],
wayland-protocols (>= 1.4) [linux-any],
libvulkan-dev [linux-any],
- libsrt-dev [linux-any],
libgstreamer1.0-dev (>= 1.16.2),
gstreamer1.0-doc,
gstreamer1.0-plugins-base (>= 1.16.2),
@@ -81,7 +80,7 @@
libsndfile1-dev (>= 1.0.16),
libsoundtouch-dev (>= 1.5.0),
libspandsp-dev,
- libsrt-dev,
+ libsrt-gnutls-dev,
libsrtp2-dev (>= 2.1),
libssl-dev,
libtool (>= 2.2.6),
diff -Nru gst-plugins-bad1.0-1.16.2/debian/patches/29bf8d8528ec694f65c8fae310adac996322cc74.patch gst-plugins-bad1.0-1.16.2/debian/patches/29bf8d8528ec694f65c8fae310adac996322cc74.patch
--- gst-plugins-bad1.0-1.16.2/debian/patches/29bf8d8528ec694f65c8fae310adac996322cc74.patch 1970-01-01 01:00:00.0 +0100
+++ gst-plugins-bad1.0-1.16.2/debian/patches/29bf8d8528ec694f65c8fae310adac996322cc74.patch 2020-07-15 22:53:46.0 +0200
@@ -0,0 +1,46 @@
+From 29bf8d8528ec694f65c8fae310adac996322cc74 Mon Sep 17 00:00:00 2001
+From: "Jan Alexander Steffens (heftig)"
+Date: Sat, 9 May 2020 19:59:46 +0200
+Subject: [PATCH] vulkan: Drop use of VK_RESULT_BEGIN_RANGE
+
+This was removed in Vulkan 1.2.140.
+
+> Shortly after 2020-04-24, we will be removing the automatically
+> generated `VK_*_BEGIN_RANGE`, `VK_*_END_RANGE`, and `VK_*_RANGE_SIZE`
+> tokens from the Vulkan headers. These tokens are currently defined for
+> some enumerated types, but are explicitly not part of the Vulkan API.
+> They existed only to support some Vulkan implementation internals,
+> which no longer require them. We will be accepting comments on this
+> topic in [#1230], but we strongly suggest any external projects using
+> these tokens immediately migrate away from them.
+
+[#1230]: https://github.com/KhronosGroup/Vulkan-Docs/issues/1230
+---
+ ext/vulkan/vkerror.c | 4 +---
+ 1 file changed, 1 insertion(+), 3 deletions(-)
+
+diff --git a/ext/vulkan/vkerror.c b/ext/vulkan/vkerror.c
+index 3fec27e4d..c91589d9b 100644
+--- a/ext/vulkan/vkerror.c
b/ext/vulkan/vkerror.c
+@@ -27,7 +27,7 @@
+ #include "vkerror.h"
+
+ /* *INDENT-OFF* */
+-static const struct
++static const struct
+ {
+ VkResult result;
+ const char *str;
+@@ -63,8 +63,6 @@ _vk_result_to_string (VkResult result)
+
+ if (result >= 0)
+ return NULL;
+- if (result < VK_RESULT_BEGIN_RANGE)
+-return "Unknown Error";
+
+ for (i = 0; i < G_N_ELEMENTS (vk_result_string_map); i++) {
+ if (result == vk_result_string_map[i].result)
+--
+2.26.2
+
diff -Nru gst-plugins-bad1.0-1.16.2/debian/patches/fix-build-with-make-4.3.patch gst-plugins-bad1.0-1.16.2/debian/patches/fix-build-with-make-4.3.patch
--- gst-plugins-bad1.0-1.16.2/debian/patches/fix-build-with-make-4.3.patch 1970-
Bug#964041: marked as done (git-repair: FTBFS: duration parse error)
Your message dated Wed, 15 Jul 2020 21:09:49 + with message-id and subject line Bug#964041: fixed in git-repair 1.20200102-2 has caused the Debian Bug report #964041, regarding git-repair: FTBFS: duration parse error 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.) -- 964041: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964041 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: git-repair Version: 1.20200102-1 Severity: serious Tags: ftbfs This package fails to build on current sid. >From my build log: [21 of 69] Compiling Utility.HumanTime ( Utility/HumanTime.hs, dist/build/git-repair/git-repair-tmp/Utility/HumanTime.o ) Utility/HumanTime.hs:58:21: error: • Could not deduce (MonadFail m) arising from a use of ‘fail’ from the context: Monad m bound by the type signature for: parseDuration :: forall (m :: * -> *). Monad m => String -> m Duration at Utility/HumanTime.hs:47:1-48 Possible fix: add (MonadFail m) to the context of the inferred type of parsefail :: m a or the type signature for: parseDuration :: forall (m :: * -> *). Monad m => String -> m Duration • In the expression: fail "duration parse error; expected eg \"5m\" or \"1h5m\"" In an equation for ‘parsefail’: parsefail = fail "duration parse error; expected eg \"5m\" or \"1h5m\"" In an equation for ‘parseDuration’: parseDuration = maybe parsefail (return . Duration) . go 0 where go n [] = return n go n s = do num <- ... parsefail = fail "duration parse error; expected eg \"5m\" or \"1h5m\"" | 58 | parsefail = fail "duration parse error; expected eg \"5m\" or \"1h5m\"" | ^^^ make[1]: *** [Makefile:8: build] Error 1 make[1]: Leaving directory '/<>' dh_auto_build: error: make -j1 returned exit code 2 make: *** [debian/rules:10: binary] Error 25 -- Niko Tyni nt...@debian.org --- End Message --- --- Begin Message --- Source: git-repair Source-Version: 1.20200102-2 Done: Sean Whitton We believe that the bug you reported is fixed in the latest version of git-repair, 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 964...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Sean Whitton (supplier of updated git-repair 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, 15 Jul 2020 13:46:18 -0700 Source: git-repair Architecture: source Version: 1.20200102-2 Distribution: unstable Urgency: medium Maintainer: Sean Whitton Changed-By: Sean Whitton Closes: 964041 Changes: git-repair (1.20200102-2) unstable; urgency=medium . * Patch Utility/HumanTime.hs to update type constraint Monad -> MonadFail (Closes: #964041). * Source package configuration for dgit-maint-merge(7): - Add d/source/options - Add d/source/patch-header. Checksums-Sha1: 4763945ab17fb45f3b686174a63efe0c68df38eb 2401 git-repair_1.20200102-2.dsc 49cb9a015b76b37388b94dfd5afd8661e624a95e 15376 git-repair_1.20200102-2.debian.tar.xz Checksums-Sha256: 3c7304d7bdaabb5125bf9e5dc1fb2a59f13eac7c2f06cfb7ac23afc142712b45 2401 git-repair_1.20200102-2.dsc 6f60c4ab5f1013bb53cb1d2c02b5c9da3ea252fcaa0738405d302c8e258ea607 15376 git-repair_1.20200102-2.debian.tar.xz Files: 7accc3466431a943572185834891fdaf 2401 utils optional git-repair_1.20200102-2.dsc cc70666be96309cc1f95f9500ff3e085 15376 utils optional git-repair_1.20200102-2.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEm5FwB64DDjbk/CSLaVt65L8GYkAFAl8PazIACgkQaVt65L8G YkCnUQ//TGrftxA7w14B/hoSStT/CVrXBQTVH+7l1SCnLewIkXeszK6OKgMWd+wH SXee3ay5Z/AO+tvpdNEfCb1nd9NPk4ztRm7IwiKVaPUD/n
Bug#965086: ssh: setgroups: Bad address [preauth]
Package: openssh-server Version: 1:8.3p1-1 Severity: grave Justification: renders package unusable After an upgrade of libc6 today, I can no longer log into my system using ssh: tglase@tglase:~ $ ssh localhost Connection reset by 127.0.0.1 port 22 Jul 15 22:33:17 tglase sshd[27084]: fatal: setgroups: Bad address [preauth] More debugging: tglase@tglase:~ $ sudo cleanenv / /usr/sbin/sshd -p2000 -ddde debug2: load_server_config: filename /etc/ssh/sshd_config debug2: load_server_config: done config len = 329 debug2: parse_server_config_depth: config /etc/ssh/sshd_config len 329 debug2: /etc/ssh/sshd_config line 13: new include /etc/ssh/sshd_config.d/*.conf debug2: /etc/ssh/sshd_config line 13: no match for /etc/ssh/sshd_config.d/*.conf debug3: /etc/ssh/sshd_config:20 setting HostKey /etc/ssh/ssh_host_rsa_key debug3: /etc/ssh/sshd_config:63 setting ChallengeResponseAuthentication no debug3: /etc/ssh/sshd_config:86 setting UsePAM yes debug3: /etc/ssh/sshd_config:91 setting X11Forwarding yes debug3: /etc/ssh/sshd_config:95 setting PrintMotd no debug3: /etc/ssh/sshd_config:113 setting AcceptEnv LANG LC_* debug3: /etc/ssh/sshd_config:116 setting Subsystem sftp /usr/lib/openssh/sftp-server debug1: sshd version OpenSSH_8.3, OpenSSL 1.1.1g 21 Apr 2020 debug1: private host key #0: ssh-rsa SHA256:9ae2/1t8U30Savg3XisO1ZCDuaH8IXQm18FdLpW3g8M debug1: rexec_argv[0]='/usr/sbin/sshd' debug1: rexec_argv[1]='-p2000' debug1: rexec_argv[2]='-ddde' debug3: oom_adjust_setup debug1: Set /proc/self/oom_score_adj from 0 to -1000 debug2: fd 3 setting O_NONBLOCK debug1: Bind to port 2000 on 0.0.0.0. Server listening on 0.0.0.0 port 2000. debug2: fd 4 setting O_NONBLOCK debug3: sock_set_v6only: set socket 4 IPV6_V6ONLY debug1: Bind to port 2000 on ::. Server listening on :: port 2000. debug3: fd 5 is not O_NONBLOCK debug1: Server will not fork when running in debugging mode. debug3: send_rexec_state: entering fd = 8 config len 329 debug3: ssh_msg_send: type 0 debug3: send_rexec_state: done debug1: rexec start in 5 out 5 newsock 5 pipe -1 sock 8 debug3: recv_rexec_state: entering fd = 5 debug3: ssh_msg_recv entering debug3: recv_rexec_state: done debug2: parse_server_config_depth: config rexec len 329 debug2: parse_server_config_depth: config len 0 debug3: rexec:20 setting HostKey /etc/ssh/ssh_host_rsa_key debug3: rexec:63 setting ChallengeResponseAuthentication no debug3: rexec:86 setting UsePAM yes debug3: rexec:91 setting X11Forwarding yes debug3: rexec:95 setting PrintMotd no debug3: rexec:113 setting AcceptEnv LANG LC_* debug3: rexec:116 setting Subsystem sftp/usr/lib/openssh/sftp-server debug1: sshd version OpenSSH_8.3, OpenSSL 1.1.1g 21 Apr 2020 debug1: private host key #0: ssh-rsa SHA256:9ae2/1t8U30Savg3XisO1ZCDuaH8IXQm18FdLpW3g8M debug1: inetd sockets after dupping: 3, 3 Connection from 127.0.0.1 port 57626 on 127.0.0.1 port 2000 rdomain "" debug1: Local version string SSH-2.0-OpenSSH_8.3p1 Debian-1 debug1: Remote protocol version 2.0, remote software version OpenSSH_8.3p1 Debian-1 debug1: match: OpenSSH_8.3p1 Debian-1 pat OpenSSH* compat 0x0400 debug2: fd 3 setting O_NONBLOCK debug3: ssh_sandbox_init: preparing seccomp filter sandbox debug2: Network child is on pid 2057 debug3: preauth child monitor started debug3: privsep user:group 111:65534 [preauth] setgroups: Bad address [preauth] debug1: do_cleanup [preauth] debug3: PAM: sshpam_thread_cleanup entering [preauth] debug1: monitor_read_log: child log fd closed debug3: mm_request_receive entering debug1: do_cleanup debug3: PAM: sshpam_thread_cleanup entering debug1: Killing privsep child 2057 debug1: audit_event: unhandled event 12 -- System Information: Debian Release: bullseye/sid APT prefers unreleased APT policy: (500, 'unreleased'), (500, 'buildd-unstable'), (500, 'unstable'), (100, 'experimental') Architecture: x32 (x86_64) Foreign Architectures: i386, amd64 Kernel: Linux 5.7.0-1-amd64 (SMP w/4 CPU threads) Kernel taint flags: TAINT_FIRMWARE_WORKAROUND Locale: LANG=C, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/lksh Init: sysvinit (via /sbin/init) Versions of packages openssh-server depends on: ii adduser3.118 ii debconf [debconf-2.0] 1.5.74 ii dpkg 1.20.5 ii libaudit1 1:2.8.5-3+b1 ii libc6 2.31-1 ii libcom-err21.45.6-1 ii libcrypt1 1:4.4.16-1 ii libelogind0 [libsystemd0] 243.7-1+debian1 ii libgssapi-krb5-2 1.17-10 ii libkrb5-3 1.17-10 ii libpam-modules 1.3.1-5 ii libpam-runtime 1.3.1-5 ii libpam0g 1.3.1-5 ii libselinux13.1-1 ii libssl1.1 1.1.1g-1 ii libwrap0 7.6.q-30 ii lsb-base 11.1.0 ii openssh-client 1:8.3p1-1 ii openssh-sftp-server1:8.3p1-1 ii procps 2:3.3.16-5 ii runit-helper
Bug#965087: postfix/master[2632]: fatal: set_eugid: setgroups(137): Bad address
Package: postfix Version: 3.5.4-1 Severity: grave Justification: renders package unusable After a glibc upgrade today, I cannot start postfix any more. I first noticed that after reportbug syslog was strangely quiet, and sudo mailq does say: postqueue: warning: Mail system is down -- accessing queue directly Trying to start Postfix results in: Jul 15 22:40:24 tglase postfix/master[2632]: fatal: set_eugid: setgroups(137): Bad address This may be related to the setgroups fatal failure I’m reporting against OpenSSH :/ -- System Information: Debian Release: bullseye/sid APT prefers unreleased APT policy: (500, 'unreleased'), (500, 'buildd-unstable'), (500, 'unstable'), (100, 'experimental') Architecture: x32 (x86_64) Foreign Architectures: i386, amd64 Kernel: Linux 5.7.0-1-amd64 (SMP w/4 CPU threads) Kernel taint flags: TAINT_FIRMWARE_WORKAROUND Locale: LANG=C, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/lksh Init: sysvinit (via /sbin/init) Versions of packages postfix depends on: ii adduser3.118 ii cpio 2.13+dfsg-3 ii debconf [debconf-2.0] 1.5.74 ii dpkg 1.20.5 ii e2fsprogs 1.45.6-1 ii libc6 2.31-1 ii libdb5.3 5.3.28+dfsg1-0.6 ii libicu67 67.1-3 ii libsasl2-2 2.1.27+dfsg-2 ii libssl1.1 1.1.1g-1 ii lsb-base 11.1.0 ii netbase6.1 ii ssl-cert 1.0.39 Versions of packages postfix recommends: ii ca-bundle [ca-certificates] 20190604 ii python3 3.8.2-3 Versions of packages postfix suggests: ii bsd-mailx [mail-reader] 8.1.2-0.20180807cvs-1 ii libsasl2-modules 2.1.27+dfsg-2 pn postfix-cdb pn postfix-doc pn postfix-ldap pn postfix-lmdb pn postfix-mysql pn postfix-pcre pn postfix-pgsql pn postfix-sqlite pn procmail pn resolvconf pn ufw -- debconf information: postfix/procmail: false postfix/root_address: postfix/chattr: false postfix/destinations: tglase.lan.tarent.de, tglase.lan.tarent.de, localhost.lan.tarent.de, localhost postfix/main_cf_conversion_warning: true postfix/not_configured: postfix/compat_conversion_warning: true postfix/dynamicmaps_conversion_warning: postfix/protocols: all postfix/retry_upgrade_warning: * postfix/mailname: tglase.lan.tarent.de postfix/kernel_version_warning: postfix/rfc1035_violation: false postfix/mynetworks: 127.0.0.0/8 [:::127.0.0.0]/104 [::1]/128 postfix/tlsmgr_upgrade_warning: postfix/sqlite_warning: postfix/newaliases: false * postfix/main_mailer_type: Internet with smarthost postfix/bad_recipient_delimiter: * postfix/relayhost: mail.lixid.net postfix/mailbox_limit: 0 postfix/recipient_delim: + postfix/mydomain_warning: postfix/relay_restrictions_warning: postfix/lmtp_retired_warning: true
Bug#961811: baresip: diff for NMU version 0.6.1-1.1
Control: tags 961811 + patch Control: tags 961811 + pending Dear maintainer, I've prepared an NMU for baresip (versioned as 0.6.1-1.1) and uploaded it to DELAYED/2. Please feel free to tell me if I should delay it longer. Cheers -- Sebastian Ramacher diff -Nru baresip-0.6.1/debian/changelog baresip-0.6.1/debian/changelog --- baresip-0.6.1/debian/changelog 2019-02-18 13:30:38.0 +0100 +++ baresip-0.6.1/debian/changelog 2020-07-15 22:37:51.0 +0200 @@ -1,3 +1,12 @@ +baresip (0.6.1-1.1) unstable; urgency=medium + + * Non-maintainer upload. + * debian/patches: +- Unbreak patch 1002 with make 4.3 (Closes: #961811) +- Apply upstream patch to fix build of selftest + + -- Sebastian Ramacher Wed, 15 Jul 2020 22:37:51 +0200 + baresip (0.6.1-1) unstable; urgency=medium [ upstream ] diff -Nru baresip-0.6.1/debian/patches/1002_system_header_locations.patch baresip-0.6.1/debian/patches/1002_system_header_locations.patch --- baresip-0.6.1/debian/patches/1002_system_header_locations.patch 2019-02-11 20:42:25.0 +0100 +++ baresip-0.6.1/debian/patches/1002_system_header_locations.patch 2020-07-15 22:33:05.0 +0200 @@ -22,7 +22,7 @@ -USE_ALSA := $(shell [ -f $(SYSROOT)/include/alsa/asoundlib.h ] || \ - [ -f $(SYSROOT_ALT)/include/alsa/asoundlib.h ] && echo "yes") -+USE_ALSA := $(shell echo '\#include ' | \ ++USE_ALSA := $(shell echo '#include ' | \ + $(CC) -E - >/dev/null 2>&1 && echo yes) +USE_AMR := $(shell pkg-config --exists opencore-amrnb && echo "yes") +ifeq ($(USE_AMR),) @@ -39,9 +39,9 @@ - [ -f $(SYSROOT)/include/$(MACHINE)/libavformat/avformat.h ] || \ - [ -f $(SYSROOT_ALT)/include/libavformat/avformat.h ] && echo "yes") +endif -+USE_AVCODEC := $(shell echo '\#include ' | \ ++USE_AVCODEC := $(shell echo '#include ' | \ + $(CC) -E - >/dev/null 2>&1 && echo yes) -+USE_AVFORMAT := $(shell echo '\#include ' | \ ++USE_AVFORMAT := $(shell echo '#include ' | \ + $(CC) -E - >/dev/null 2>&1 && echo yes) USE_AVAHI := $(shell pkg-config --exists avahi-client && echo "yes") -USE_BV32 := $(shell [ -f $(SYSROOT)/include/bv32/bv32.h ] || \ @@ -69,21 +69,21 @@ - [ -f $(SYSROOT)/include/gsm/gsm.h ] || \ - [ -f $(SYSROOT)/local/include/gsm.h ] || \ - [ -f $(SYSROOT)/local/include/gsm/gsm.h ] && echo "yes") -+USE_BV32 := $(shell echo '\#include ' | \ + $(CC) -E - >/dev/null 2>&1 && echo yes) -+USE_CAIRO := $(shell echo '\#include ' |\ ++USE_CAIRO := $(shell echo '#include ' |\ + $(CC) -E - >/dev/null 2>&1 && echo yes) -+USE_DTLS := $(shell echo '\#include ' | \ ++USE_DTLS := $(shell echo '#include ' | \ + $(CC) -E - >/dev/null 2>&1 && echo yes) -+USE_DTLS_SRTP := $(shell echo '\#include ' | \ ++USE_DTLS_SRTP := $(shell echo '#include ' | \ + $(CC) -E - >/dev/null 2>&1 && echo yes) -+USE_G722 := $(shell echo '\#include ' | \ ++USE_G722 := $(shell echo '#include ' | \ + $(CC) -E - >/dev/null 2>&1 && echo yes) -+USE_G722_1 := $(shell echo '\#include ' | \ ++USE_G722_1 := $(shell echo '#include ' | \ + $(CC) -E - >/dev/null 2>&1 && echo yes) -+USE_G726 := $(shell echo '\#include ' | \ ++USE_G726 := $(shell echo '#include ' | \ + $(CC) -E - >/dev/null 2>&1 && echo yes) -+USE_GSM := $(shell echo '\#include ' | \ ++USE_GSM := $(shell echo '#include ' | \ + $(CC) -E - >/dev/null 2>&1 && echo yes) USE_GST := $(shell pkg-config --exists gstreamer-0.10 && echo "yes") USE_GST1 := $(shell pkg-config --exists gstreamer-1.0 && echo "yes") @@ -117,27 +117,27 @@ -USE_PORTAUDIO := $(shell [ -f $(SYSROOT)/local/include/portaudio.h ] || \ - [ -f $(SYSROOT)/include/portaudio.h ] || \ - [ -f $(SYSROOT_ALT)/include/portaudio.h ] && echo "yes") -+USE_H265 := $(shell echo '\#include ' | \ ++USE_H265 := $(shell echo '#include ' | \ + $(CC) -E - >/dev/null 2>&1 && echo yes) +endif -+USE_ILBC := $(shell echo '\#include ' | \ ++USE_ILBC := $(shell echo '#include ' | \ + $(CC) -E - >/dev/null 2>&1 && echo yes) -+USE_ISAC := $(shell echo '\#include ' | \ ++USE_ISAC := $(shell echo '#include ' | \ + $(CC) -E - >/dev/null 2>&1 && echo yes) -+USE_JACK := $(shell echo '\#include ' | \ ++USE_JACK := $(shell echo '#include ' | \ + $(CC) -E - >/dev/null 2>&1 && echo yes) -+USE_MPG123 := $(shell echo '\#include ' | \ ++USE_MPG123 := $(shell echo '#include ' | \ + $(CC) -E - >/dev/null 2>&1 && echo yes) -+USE_OPUS := $(shell echo '\#include ' | \ ++USE_OPUS := $(shell echo '#include ' | \ + $(CC) -E - >/dev/null 2>&1 && echo yes) -+USE_OSS := $(shell echo '\#include ' | \ ++USE_OSS := $(shell echo '#include ' | \ + $(CC) -E - >/dev/null 2>&1 || \ -+ echo '\#include ' | $(CC) -E - >/dev/null 2>&1 || \ -+ echo '\#include ' | $(CC) -E - >/dev/null 2>&1 && \ ++ echo '#include ' | $(CC) -E - >/dev/null 2>&1 || \ ++ echo '#include ' | $(CC) -E - >/dev/null 2>&1 && \ + echo yes) -+USE_PLC := $(shell echo '\#include ' | \ ++USE_PLC := $(shell echo '#include ' | \ + $(CC) -E - >/dev/null 2>&1 && echo yes) -+USE_PORTAUDIO := $(shell echo '\#include ' | \ ++USE_PORTAUDIO := $(s
Processed: baresip: diff for NMU version 0.6.1-1.1
Processing control commands: > tags 961811 + patch Bug #961811 [src:baresip] baresip FTBFS with make 4.3 Added tag(s) patch. > tags 961811 + pending Bug #961811 [src:baresip] baresip FTBFS with make 4.3 Added tag(s) pending. -- 961811: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=961811 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#963808: marked as done (ruby-sanitize: CVE-2020-4054: HTML sanitization bypass in Sanitize)
Your message dated Wed, 15 Jul 2020 20:40:50 + with message-id and subject line Bug#963808: fixed in ruby-sanitize 4.6.6-2.1 has caused the Debian Bug report #963808, regarding ruby-sanitize: CVE-2020-4054: HTML sanitization bypass in Sanitize 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.) -- 963808: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963808 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ruby-sanitize Version: 4.6.6-2 Severity: grave Tags: security upstream Justification: user security hole Hi, The following vulnerability was published for ruby-sanitize. CVE-2020-4054[0]: | In Sanitize (RubyGem sanitize) greater than or equal to 3.0.0 and less | than 5.2.1, there is a cross-site scripting vulnerability. When HTML | is sanitized using Sanitize's "relaxed" config, or a custom config | that allows certain elements, some content in a math or svg element | may not be sanitized correctly even if math and svg are not in the | allowlist. You are likely to be vulnerable to this issue if you use | Sanitize's relaxed config or a custom config that allows one or more | of the following HTML elements: iframe, math, noembed, noframes, | noscript, plaintext, script, style, svg, xmp. Using carefully crafted | input, an attacker may be able to sneak arbitrary HTML through | Sanitize, potentially resulting in XSS (cross-site scripting) or other | undesired behavior when that HTML is rendered in a browser. This has | been fixed in 5.2.1. 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-2020-4054 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-4054 [1] https://github.com/rgrove/sanitize/security/advisories/GHSA-p4x4-rw2p-8j8m [2] https://github.com/rgrove/sanitize/commit/a11498de9e283cd457b35ee252983662f7452aa9 Regards, Salvatore --- End Message --- --- Begin Message --- Source: ruby-sanitize Source-Version: 4.6.6-2.1 Done: Salvatore Bonaccorso We believe that the bug you reported is fixed in the latest version of ruby-sanitize, 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 963...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Salvatore Bonaccorso (supplier of updated ruby-sanitize 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: Sun, 12 Jul 2020 15:02:54 +0200 Source: ruby-sanitize Architecture: source Version: 4.6.6-2.1 Distribution: unstable Urgency: medium Maintainer: Debian Ruby Extras Maintainers Changed-By: Salvatore Bonaccorso Closes: 963808 Changes: ruby-sanitize (4.6.6-2.1) unstable; urgency=medium . * Non-maintainer upload. * fix: Don't treat :remove_contents as `true` when it's an Array * feat: Remove useless filtered element content by default * Fix sanitization bypass in HTML foreign content (CVE-2020-4054) (Closes: #963808) Checksums-Sha1: 8582b93426faf2d90f4160e06afae90d597bf448 2298 ruby-sanitize_4.6.6-2.1.dsc 9758396904eb64a50c00d95cdacb051926675d25 7484 ruby-sanitize_4.6.6-2.1.debian.tar.xz 7e3a5285a51d66a6fee96a94b3ccf89ce6ef5c7b 7239 ruby-sanitize_4.6.6-2.1_source.buildinfo Checksums-Sha256: f20d0a27b4d330eb5f38f333a20fa2bfee63c58a65c7574dd92133dda56d6567 2298 ruby-sanitize_4.6.6-2.1.dsc 6d3534b5629eece6ebd3ae73df46050d30dae7cf35bddc3c589cd902131239e3 7484 ruby-sanitize_4.6.6-2.1.debian.tar.xz d558ad725df7d42232aa1bb77409d2a260cfad3bc589e789a523661a163a09cf 7239 ruby-sanitize_4.6.6-2.1_source.buildinfo Files: 680cb8fbe6736f844b48f0af1f66543a 2298 ruby optional ruby-sanitize_4.6.6-2.1.dsc 196d9df60995ebcc04b50b99aa94c74b 7484 ruby optional ruby-sanitize_4.6.6-2.1.debian.tar.xz d4379c541e08a08915291f158fa10868 7239 ruby optional ruby-sanitize_4.6.6-2.1_source.buildinfo -BEGIN PGP SIGNATURE- iQKmBAEBCgCQFiEERkRAmAjBceBVMd3uBUy48xNDz0QFAl8MvrNfFIAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDQ2 NDQ0MDk4MDhDMTcxRTA1NTMxRERFRTA1NENCOEYzMTM0M0NGNDQSHGNhcm5pbEBk ZWJpYW4ub3JnAAoJEAVMuPMTQ89ERHMP/3AYP/aJOeg/iUtB
Bug#964666: marked as done (libopenshot: FTBFS: dh_missing: error: missing files, aborting)
Your message dated Wed, 15 Jul 2020 19:04:28 + with message-id and subject line Bug#964666: fixed in libopenshot 0.2.5+dfsg1-3 has caused the Debian Bug report #964666, regarding libopenshot: FTBFS: dh_missing: error: missing files, aborting 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.) -- 964666: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964666 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libopenshot Version: 0.2.5+dfsg1-2 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20200709 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_installdocs --indep > dh_doxygen --indep > make[1]: Leaving directory '/<>' >dh_installdocs > -O--builddirectory=/<>/libopenshot-0.2.5\+dfsg1/debian/build > -Nlibopenshot-doc >dh_installchangelogs > -O--builddirectory=/<>/libopenshot-0.2.5\+dfsg1/debian/build >dh_python3 > -O--builddirectory=/<>/libopenshot-0.2.5\+dfsg1/debian/build > I: dh_python3 fs:343: renaming _openshot.so to > _openshot.cpython-38-x86_64-linux-gnu.so >dh_installsystemduser > -O--builddirectory=/<>/libopenshot-0.2.5\+dfsg1/debian/build >dh_perl > -O--builddirectory=/<>/libopenshot-0.2.5\+dfsg1/debian/build >dh_link > -O--builddirectory=/<>/libopenshot-0.2.5\+dfsg1/debian/build >dh_strip_nondeterminism > -O--builddirectory=/<>/libopenshot-0.2.5\+dfsg1/debian/build >dh_compress > -O--builddirectory=/<>/libopenshot-0.2.5\+dfsg1/debian/build >dh_fixperms > -O--builddirectory=/<>/libopenshot-0.2.5\+dfsg1/debian/build >dh_missing > -O--builddirectory=/<>/libopenshot-0.2.5\+dfsg1/debian/build > dh_missing: warning: > usr/share/doc/libopenshot/API/AudioBufferSource_8cpp.html exists in > debian/tmp but is not installed to anywhere > dh_missing: warning: > usr/share/doc/libopenshot/API/classopenshot_1_1InvalidJSON.png exists in > debian/tmp but is not installed to anywhere > dh_missing: warning: > usr/share/doc/libopenshot/API/classopenshot_1_1ErrorEncodingAudio.html exists > in debian/tmp but is not installed to anywhere > dh_missing: warning: > usr/share/doc/libopenshot/API/classopenshot_1_1ChunkWriter-members.html > exists in debian/tmp but is not installed to anywhere > dh_missing: warning: > usr/share/doc/libopenshot/API/classopenshot_1_1BaseException.html exists in > debian/tmp but is not installed to anywhere > dh_missing: warning: > usr/share/doc/libopenshot/API/classopenshot_1_1Settings.html exists in > debian/tmp but is not installed to anywhere > dh_missing: warning: > usr/share/doc/libopenshot/API/structopenshot_1_1ProfileInfo-members.html > exists in debian/tmp but is not installed to anywhere > dh_missing: warning: > usr/share/doc/libopenshot/API/QtHtmlReader_8cpp_source.html exists in > debian/tmp but is not installed to anywhere > dh_missing: warning: usr/share/doc/libopenshot/API/Pixelate_8h.html exists in > debian/tmp but is not installed to anywhere > dh_missing: warning: > usr/share/doc/libopenshot/API/classopenshot_1_1AudioPlaybackThread.html > exists in debian/tmp but is not installed to anywhere > dh_missing: warning: > usr/share/doc/libopenshot/API/classopenshot_1_1ReaderBase-members.html exists > in debian/tmp but is not installed to anywhere > dh_missing: warning: usr/share/doc/libopenshot/API/globals_vars.html exists > in debian/tmp but is not installed to anywhere > dh_missing: warning: usr/share/doc/libopenshot/API/QtPlayer_8cpp.html exists > in debian/tmp but is not installed to anywhere > dh_missing: warning: > usr/share/doc/libopenshot/API/classopenshot_1_1InvalidJSONKey.html exists in > debian/tmp but is not installed to anywhere > dh_missing: warning: usr/share/doc/libopenshot/API/Pixelate_8h_source.html > exists in debian/tmp but is not installed to anywhere > dh_missing: warning: usr/share/doc/libopenshot/API/open.png exists in > debian/tmp but is not installed to anywhere > dh_missing: warning: > usr/share/doc/libopenshot/API/ReaderBase_8cpp_source.html exists in > debian/tmp but is not installed to anywhere > dh_missing: warning: > usr/share/doc/libopenshot/API/classopenshot_1_1Brightness-members.html exists > in debian/tmp but is not installed to anywhere > dh_missing: warning: usr/share/doc/libopenshot/API/functions_func_o.html > exists in debian/tmp but is not installed to anywhere > dh_missing: warning: usr/share/doc/libopenshot/API/classopenshot_1_1Blur.html > exists in debi
Processed: Bug#964666 marked as pending in libopenshot
Processing control commands: > tag -1 pending Bug #964666 [src:libopenshot] libopenshot: FTBFS: dh_missing: error: missing files, aborting Added tag(s) pending. -- 964666: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964666 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#964666: marked as pending in libopenshot
Control: tag -1 pending Hello, Bug #964666 in libopenshot 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/multimedia-team/libopenshot/-/commit/43689f7b3b058dfd0ee83dd7ff6a6bc863a02004 Add d/not-installed. (Closes: #964666) (this message was generated automatically) -- Greetings https://bugs.debian.org/964666
Bug#925789: marked as done (nsntrace: ftbfs with GCC-9)
Your message dated Wed, 15 Jul 2020 18:47:03 +0100 with message-id and subject line has caused the Debian Bug report #925789, regarding nsntrace: ftbfs with GCC-9 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.) -- 925789: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925789 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:nsntrace Version: 0~20160806-1 Severity: normal Tags: sid bullseye User: debian-...@lists.debian.org Usertags: ftbfs-gcc-9 Please keep this issue open in the bug tracker for the package it was filed for. If a fix in another package is required, please file a bug for the other package (or clone), and add a block in this package. Please keep the issue open until the package can be built in a follow-up test rebuild. The package fails to build in a test rebuild on at least amd64 with gcc-9/g++-9, but succeeds to build with gcc-8/g++-8. The severity of this report will be raised before the bullseye release, so nothing has to be done for the buster release. The full build log can be found at: http://people.debian.org/~doko/logs/gcc9-20190321/nsntrace_0~20160806-1_unstable_gcc9.log The last lines of the build log are at the end of this report. To build with GCC 9, either set CC=gcc-9 CXX=g++-9 explicitly, or install the gcc, g++, gfortran, ... packages from experimental. apt-get -t=experimental install g++ Common build failures are new warnings resulting in build failures with -Werror turned on, or new/dropped symbols in Debian symbols files. For other C/C++ related build failures see the porting guide at http://gcc.gnu.org/gcc-9/porting_to.html GCC 9 also passes the linker option --as-needed by default; typical build issues are passing libraries before object files to the linker, or underlinking of convenience libraries built from the same source. [...] config.status: creating config.h config.status: executing depfiles commands configure: WARNING: unrecognized options: --disable-maintainer-mode dh_auto_build -a -O--parallel make -j4 make[1]: Entering directory '/<>' make all-recursive make[2]: Entering directory '/<>' Making all in src make[3]: Entering directory '/<>/src' gcc -DHAVE_CONFIG_H -I. -I.. -I/usr/include/libnl3 -Wall -Wno-missing-braces -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -c -o nsntrace-nsntrace.o `test -f 'nsntrace.c' || echo './'`nsntrace.c gcc -DHAVE_CONFIG_H -I. -I.. -I/usr/include/libnl3 -Wall -Wno-missing-braces -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -c -o nsntrace-cmd.o `test -f 'cmd.c' || echo './'`cmd.c gcc -DHAVE_CONFIG_H -I. -I.. -I/usr/include/libnl3 -Wall -Wno-missing-braces -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -c -o nsntrace-net.o `test -f 'net.c' || echo './'`net.c gcc -DHAVE_CONFIG_H -I. -I.. -I/usr/include/libnl3 -Wall -Wno-missing-braces -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -c -o nsntrace-capture.o `test -f 'capture.c' || echo './'`capture.c gcc -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -lnl-route-3 -lnl-3 -pthread -Wl,-z,relro -o nsntrace nsntrace-nsntrace.o nsntrace-cmd.o nsntrace-net.o nsntrace-capture.o -lpcap /usr/bin/ld: nsntrace-net.o: in function `_nsntrace_net_get_nl_socket': ./src/net.c:66: undefined reference to `nl_socket_alloc' /usr/bin/ld: ./src/net.c:67: undefined reference to `nl_connect' /usr/bin/ld: nsntrace-net.o: in function `_nsntrace_net_iface_up': ./src/net.c:146: undefined reference to `rtnl_link_alloc_cache' /usr/bin/ld: ./src/net.c:150: undefined reference to `rtnl_link_get_by_name' /usr/bin/ld: ./src/net.c:154: undefined reference to `rtnl_addr_alloc' /usr/bin/ld: ./src/net.c:155: undefined reference to `rtnl_addr_set_link' /usr/bin/ld: ./src/net.c:156: undefined reference to `rtnl_link_put' /usr/bin/ld: ./src/net.c:158: undefined reference to `nl_addr_parse' /usr/bin/ld: ./src/net.c:162: undefined reference to `rtnl_addr_set_local' /usr/bin/ld: ./src/net.c:165: undefined reference to `nl_addr_put' /usr/bin/ld: ./src/net.c:167: undefined reference to `rtnl_addr_add' /usr/bin/ld: ./src/net.c:171: undefined reference to `rtnl_link_alloc' /usr/bin/ld: ./src/net.c:172: undefined reference to `rtnl_link_set_flags' /usr/bin/ld: ./src/net.c:174: undefined reference to `rtnl_link_
Processed: block 961195 with 965073
Processing commands for cont...@bugs.debian.org: > block 961195 with 965073 Bug #961195 [release.debian.org] transition: glibc 961195 was blocked by: 964227 964226 964220 964225 955368 964231 964223 964229 961195 was not blocking any bugs. Added blocking bug(s) of 961195: 965073 > thanks Stopping processing here. Please contact me if you need assistance. -- 961195: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=961195 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#964822: marked as done (pandoc: BD-Uninstallable)
Your message dated Wed, 15 Jul 2020 17:04:26 + with message-id and subject line Bug#964822: fixed in pandoc 2.9.1.1-1 has caused the Debian Bug report #964822, regarding pandoc: BD-Uninstallable 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.) -- 964822: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964822 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: pandoc Version: 2.5-3 Severity: serious Tags: ftbfs sid bullseye Justification: fails to build from source (but built successfully in the past) pandoc currenlty cannot be built because libghc-cmark-gfm-dev is newer than 0.2: pandoc build-depends on missing: - libghc-cmark-gfm-dev:amd64 (< 0.2) Cheers -- Sebastian Ramacher signature.asc Description: PGP signature --- End Message --- --- Begin Message --- Source: pandoc Source-Version: 2.9.1.1-1 Done: Jonas Smedegaard We believe that the bug you reported is fixed in the latest version of pandoc, 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 964...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jonas Smedegaard (supplier of updated pandoc 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, 14 Jul 2020 12:44:35 +0200 Source: pandoc Architecture: source Version: 2.9.1.1-1 Distribution: unstable Urgency: medium Maintainer: Debian Haskell Group Changed-By: Jonas Smedegaard Closes: 927689 959851 964822 Changes: pandoc (2.9.1.1-1) unstable; urgency=medium . [ upstream ] * new release(s) closes: bug#927689, #964822, #959851 . [ Jonas Smedegaard ] * fix provide virtual pandoc-abi-* * annotate binary package pandoc-dev as Multi-Arch: same * drop patch cherry-picked upstream since applied * copyright: update coverage * update long descriptions: + add new reader: Kira markup * fix provide virtual pandoc-abi Checksums-Sha1: 1b85b8981b9aeb0d6d1ddab4a83d51ab907b8ae1 8324 pandoc_2.9.1.1-1.dsc 235dbdc0e4ea730f6d96e54bec5c82109f3c80ca 12653173 pandoc_2.9.1.1.orig.tar.gz 257881f49cc504f81031dc3543c00d36d2a7e6ac 53288 pandoc_2.9.1.1-1.debian.tar.xz 2fa78c497f18ef29696c3101e6d6fb632d483531 20233 pandoc_2.9.1.1-1_amd64.buildinfo Checksums-Sha256: 04e2fdb1ae797ba983bfd895d3c1ebe43fa8c8360d210d2ff05a40eb16b42e73 8324 pandoc_2.9.1.1-1.dsc df776d5f27239fce9de6198b14c2bf3afce7bdc2ce77b0aace82431e3cedd08f 12653173 pandoc_2.9.1.1.orig.tar.gz da7c54ff3608658843eb21467f37060b753428be8b4c2a32fc8a01aa02e22a20 53288 pandoc_2.9.1.1-1.debian.tar.xz 0543e300499a8fdec74f5de0e5f7f280b0a81474dd672185ab6df4e89be7867d 20233 pandoc_2.9.1.1-1_amd64.buildinfo Files: b6586e2ad0bc42f974856ade91862206 8324 text optional pandoc_2.9.1.1-1.dsc faa1d73de9d9b439a16391b3c116635e 12653173 text optional pandoc_2.9.1.1.orig.tar.gz 0ffe8163baf69d2edcbff9da030c16b8 53288 text optional pandoc_2.9.1.1-1.debian.tar.xz ca95bae037278b9f15c247108ac05211 20233 text optional pandoc_2.9.1.1-1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAl8PMfcACgkQLHwxRsGg ASHB+A//dgEPMPiloOevyBp4tGAaR4orgPw05Jl37cYZ/e8WUxHCSn5IVU/F3Gxx aV+1TxsB+kb9gadaf5QaYMC/wtlpSp74VZcABxWWlwB8sMibP1CCXuk90rXdFH+g avwftFDWXTZbI5qFC1XArXmB6m76nf+ExlPIfWR52nzigov7/Oe3ZUW7NBzfgVhK DQHZIcVoszFEmCxWH+92xLKLcMN6oT+kh7i9PB4kAgm2zr077yM3L/YZzQ8PilH0 +gWC6VcDScCDgVyibEVl8HNHsXcVXTOPa3Ws0gCq90CcEU3qPUfASIx16bRTfhU6 6yX6exMJr4g78O/oboaGkFR/8jn7tupPoQjXF2mWtoEGiZNg3Zp79onkOIwbC2T1 1ihVrNHCdDsBe3ITt466O/6tJl1c5YZbTE2egHBuEqi733vf5t01ifHPAZps6+P8 EZSoi231peCn3qciysJwvxODKonv8wV1t+piIh/pdkGs4Xp7PMBEskRYFas/2jJU 8i6eDgF4KAUFEzCmz3HKsTN7wKaaKt3T6lQJqEfYVfE1krk+LYAVu3qhB3whJCXD Azzg8UJfIn6Izp6/ued0VJKcyNN53a/o4cEgY4TLTlhKmYRUu84ALCtr6VQUe9h5 JlI9KuPo5MNWTuzhW+qt6LRfk6TLPMh8tLkx01MuVNkZ+kkSEgU= =SnsU -END PGP SIGNATURE End Message ---
Bug#965073: macs: shared library is not properly linked with libm
Package: macs
Version: 2.2.7.1-2
Severity: serious
Tags: patch
macs use the log() math function, but doesn't link link with libm.so.
This causes the non-versioned __log_finite symbol to be used, which in
turn causes issues when glibc version is upgraded:
https://ci.debian.net/data/autopkgtest/testing/amd64/m/macs/6261687/log.gz
The attached patch fixes that.
--- macs-2.2.7.1.orig/setup.py
+++ macs-2.2.7.1/setup.py
@@ -59,8 +59,8 @@ def main():
Extension("MACS2.IO.FixWidthTrack",
["MACS2/IO/FixWidthTrack.pyx"], include_dirs=numpy_include_dir,
extra_compile_args=extra_c_args),
Extension("MACS2.IO.PairedEndTrack",
["MACS2/IO/PairedEndTrack.pyx"], include_dirs=numpy_include_dir,
extra_compile_args=extra_c_args),
Extension("MACS2.IO.BedGraph", ["MACS2/IO/BedGraph.pyx"],
libraries=["m"], extra_compile_args=extra_c_args),
- Extension("MACS2.IO.ScoreTrack",
["MACS2/IO/ScoreTrack.pyx"], include_dirs=numpy_include_dir,
extra_compile_args=extra_c_args ),
- Extension("MACS2.IO.CallPeakUnit",
["MACS2/IO/CallPeakUnit.pyx"], include_dirs=numpy_include_dir,
extra_compile_args=extra_c_args),
+ Extension("MACS2.IO.ScoreTrack",
["MACS2/IO/ScoreTrack.pyx"], libraries=["m"], include_dirs=numpy_include_dir,
extra_compile_args=extra_c_args ),
+ Extension("MACS2.IO.CallPeakUnit",
["MACS2/IO/CallPeakUnit.pyx"], libraries=["m"], include_dirs=numpy_include_dir,
extra_compile_args=extra_c_args),
#Extension("MACS2.Statistics", ["MACS2/Statistics.pyx"],
libraries=["m"], include_dirs=["MACS2/",numpy_get_include()],
extra_compile_args=extra_c_args),
]
Bug#964922: sudo: segmentation fault when include directive is active in /etc/sudoers
tags 964922 +pending thanks Thorsten Glaser writes: > On Sun, 12 Jul 2020, Bdale Garbee wrote: > >> However, since your but report caused *me* to go read that and realize @ >> is now preferred to # for that directive, I'm updating the default >> sudoers file for Debian to use @. Perhaps that will help reduce this >> particular form of confusion in the future. > > The file now reads: > > | # See sudoers(5) for more information on "#include" directives: > | > | @includedir /etc/sudoers.d > > Maybe you want to replace the other ‘#’ as well? Good point. In my repo for the next upload. Bdale signature.asc Description: PGP signature
Processed: Re: Bug#964922: sudo: segmentation fault when include directive is active in /etc/sudoers
Processing commands for cont...@bugs.debian.org:
> tags 964922 +pending
Bug #964922 {Done: Bdale Garbee } [sudo] sudo: segmentation
fault when include directive is active in /etc/sudoers
Added tag(s) pending.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
964922: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964922
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#921290: marked as done (gnunet-gtk: FTBFS with gnutls 3.6: 'GNUTLS_CRT_RAW' undeclared)
Your message dated Wed, 15 Jul 2020 17:36:20 +0200 with message-id and subject line gnunet-gtk: FTBFS with gnutls 3.6: 'GNUTLS_CRT_RAW' undeclared has caused the Debian Bug report #921290, regarding gnunet-gtk: FTBFS with gnutls 3.6: 'GNUTLS_CRT_RAW' undeclared 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.) -- 921290: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921290 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: gnunet-gtk Version: 0.11.0~pre66-1 Severity: serious Justification: fails to build from source (but built successfully in the past) Hi, gnunet-gtk/experimental recently started to FTBFS, this is probably related to the upload of gnutls28 3.6.x to unstable. The previous successful experimental builds happened with gnutls 3.5.19. libtool: compile: gcc -DHAVE_CONFIG_H -I. -I../.. -I../../ -I../../src/include -Wdate-time -D_FORTIFY_SOURCE=2 -pthread -I/usr/include/gtk-3.0 -I/usr/include/at-spi2-atk/2.0 -I/usr/include/at-spi-2.0 -I/usr/inclu de/dbus-1.0 -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include -I/usr/include/gtk-3.0 -I/usr/include/gio-unix-2.0 -I/usr/include/cairo -I/usr/include/libdrm -I/usr/include/pango-1.0 -I/usr/include/harfbuzz -I/usr/includ e/pango-1.0 -I/usr/include/fribidi -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng16 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libmount -I/usr/ include/blkid -I/usr/include/uuid -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -pthread -I/usr/include/gtk-3.0 -I/usr/include/at-spi2-atk/2.0 -I/usr/include/at-spi-2.0 -I/usr/include/dbus-1 .0 -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include -I/usr/include/gtk-3.0 -I/usr/include/gio-unix-2.0 -I/usr/include/cairo -I/usr/include/libdrm -I/usr/include/pango-1.0 -I/usr/include/harfbuzz -I/usr/include/pango-1 .0 -I/usr/include/fribidi -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng16 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libmount -I/usr/include/b lkid -I/usr/include/uuid -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -pthread -I/usr/include/libgladeui-2.0 -I/usr/include/gtk-3.0 -I/usr/include/at-spi2-atk/2.0 -I/usr/include/at-spi-2.0 -I/usr/include/dbus-1.0 -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include -I/usr/include/gtk-3.0 -I/usr/include/gio-unix-2.0 -I/usr/include/cairo -I/usr/include/libdrm -I/usr/include/pango-1.0 -I/usr/include/harfbuzz - I/usr/include/pango-1.0 -I/usr/include/fribidi -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng16 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libm ount -I/usr/include/blkid -I/usr/include/uuid -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/libxml2 -fno-strict-aliasing -Wall -g -O2 "-fdebug-prefix-map=/build/gnunet-gtk-0.1 1.0~pre66=." -fstack-protector-strong -Wformat -Werror=format-security -pthread -I/usr/include/gtk-3.0 -I/usr/include/at-spi2-atk/2.0 -I/usr/include/at-spi-2.0 -I/usr/include/dbus-1.0 -I/usr/lib/x86_64-linux-gnu/d bus-1.0/include -I/usr/include/gtk-3.0 -I/usr/include/gio-unix-2.0 -I/usr/include/cairo -I/usr/include/libdrm -I/usr/include/pango-1.0 -I/usr/include/harfbuzz -I/usr/include/pango-1.0 -I/usr/include/fribidi -I/usr /include/atk-1.0 -I/usr/include/cairo -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng16 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/uuid -I/usr/ include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -c plugin_gtk_namestore_box.c -fPIC -DPIC -o .libs/libgnunet_plugin_gtk_namestore_box_la-plugin_gtk_namestore_box.o In file included from plugin_gtk_namestore_box.c:62: plugin_gtk_namestore_tlsa.c: In function 'import_address_cb': plugin_gtk_namestore_tlsa.c:964:10: error: 'GNUTLS_CRT_RAW' undeclared (first use in this function); did you mean 'GNUTLS_CRT_MAX'? case GNUTLS_CRT_RAW: ^~ GNUTLS_CRT_MAX plugin_gtk_namestore_tlsa.c:964:10: note: each undeclared identifier is reported only once for each function it appears in plugin_gtk_namestore_tlsa.c:950:5: warning: enumeration value 'GNUTLS_CRT_RAWPK' not handled in switch [-Wswitch] switch (type) ^~ plugin_gtk_namestore_tlsa.c:950:5: warning: enumeration value 'GNUTLS_CRT_MAX' not handled in switch [-Wswitch] make[5]: *** [Makefile:1148: libgnunet_plugin_gtk_namestore_box_la-plugin_gtk_namestore_box.lo] Error 1 C
Processed: gnunet-gtk: FTBFS with gnutls 3.6: 'GNUTLS_CRT_RAW' undeclared
Processing commands for cont...@bugs.debian.org: > fixed 921290 gnunet-gtk/1.13.1-1 Bug #921290 [src:gnunet-gtk] gnunet-gtk: FTBFS with gnutls 3.6: 'GNUTLS_CRT_RAW' undeclared The source gnunet-gtk and version 1.13.1-1 do not appear to match any binary packages Marked as fixed in versions gnunet-gtk/1.13.1-1. > thanks Stopping processing here. Please contact me if you need assistance. -- 921290: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921290 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#964922: sudo: segmentation fault when include directive is active in /etc/sudoers
On Sun, 12 Jul 2020, Bdale Garbee wrote: > However, since your but report caused *me* to go read that and realize @ > is now preferred to # for that directive, I'm updating the default > sudoers file for Debian to use @. Perhaps that will help reduce this > particular form of confusion in the future. The file now reads: | # See sudoers(5) for more information on "#include" directives: | | @includedir /etc/sudoers.d Maybe you want to replace the other ‘#’ as well? bye, //mirabilos -- «MyISAM tables -will- get corrupted eventually. This is a fact of life. » “mysql is about as much database as ms access” – “MSSQL at least descends from a database” “it's a rebranded SyBase” “MySQL however was born from a flatfile and went downhill from there” – “at least jetDB doesn’t claim to be a database” ‣‣‣ Please, http://deb.li/mysql and MariaDB, finally die!
Bug#964774: marked as done (freetype: libfreetype6-udeb should not depend on non-udeb libbrotli1)
Your message dated Wed, 15 Jul 2020 15:05:03 + with message-id and subject line Bug#964774: fixed in freetype 2.10.2+dfsg-3 has caused the Debian Bug report #964774, regarding freetype: libfreetype6-udeb should not depend on non-udeb libbrotli1 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.) -- 964774: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964774 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: freetype Version: 2.10.2+dfsg-2 Severity: serious Tags: d-i Justification: breaks d-i User: de...@kali.org Usertags: origin-kali Builds of the debian-installer are failing lately due to changes in libfreetype6-udeb. They are failing with: The following packages have unmet dependencies: libfreetype6-udeb : Depends: libbrotli1 (>= 1.0.7) but it is not installable An udeb is not allowed to depend on non-udeb packages and there's no udeb package for libbrotli1. Please either disable the feature that requires brotli support in the udeb (meaning that you have to implement a double build like in some other packages providing udebs, see openssh or cairo) or work with the brotli maintainer to add the required udeb. If you go for the latter, it would be nice to disable the brotli dependency entirely until the udeb has been added and is gone through NEW. We don't think that support of WOFF fonts is important in the context of debian-installer so after a quick chat in #debian-boot, the consensus is leaning towards disabling that dependency in a separate udeb build. Cheers, -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (500, 'oldstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.19.0-6-amd64 (SMP w/4 CPU cores) Kernel taint flags: TAINT_UNSIGNED_MODULE Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled --- End Message --- --- Begin Message --- Source: freetype Source-Version: 2.10.2+dfsg-3 Done: Hugh McMaster We believe that the bug you reported is fixed in the latest version of freetype, 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 964...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Hugh McMaster (supplier of updated freetype 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, 15 Jul 2020 22:10:01 +1000 Source: freetype Architecture: source Version: 2.10.2+dfsg-3 Distribution: unstable Urgency: medium Maintainer: Hugh McMaster Changed-By: Hugh McMaster Closes: 964246 964774 Changes: freetype (2.10.2+dfsg-3) unstable; urgency=medium . [ Simon McVittie ] * d/tests: Add a superficial compile/link/run autopkgtest (Closes: #964246). . [ Hugh McMaster ] * debian/rules: - Update a comment. - Fix whitespace formatting. - Override dh_auto_clean to clean up ft2demos. - Override dh_auto_clean to remove objs/.libs/libfreetype.ver. - Run a separate build sequence for libfreetype6-udeb, which should not depend on libbrotli1 (Closes: #964774). * Minor stylistic changes to d/tests/libfreetype-dev. - Thanks to Simon McVittie for writing the autopkgtest. Checksums-Sha1: de5e052923f463396b0538c3e43c3a313615185f 3680 freetype_2.10.2+dfsg-3.dsc 85cccb2182a475fd2ccd08c99aa8767f9f72338f 116212 freetype_2.10.2+dfsg-3.debian.tar.xz 15c7bf6c35cc2827c8a5f2d5cc6053929e4cdace 8279 freetype_2.10.2+dfsg-3_amd64.buildinfo Checksums-Sha256: d91c8e350849462dc7fa93bf551c714653dfcbdb82ed7a45f1ecd414475c301b 3680 freetype_2.10.2+dfsg-3.dsc 7adcb9c757025deaa295f776787c8dc529d9ddfe30791862d476b73170782013 116212 freetype_2.10.2+dfsg-3.debian.tar.xz f43b2dabba5c5b8c8928ac68920745127f8b6cff2eefec4c7d247d2e21a9c2b8 8279 freetype_2.10.2+dfsg-3_amd64.buildinfo Files: 6711b2529ee08535903d5a61028b8c34 3680 libs optional freetype_2.10.2+dfsg-3.dsc 601a3ed39be1fa65410d41e1ab2a789e 116212 libs optional freetype_2.10.2+dfsg-3.debian.tar.xz e7d35a8046c12a3
Bug#964643: marked as done (sonic-visualiser: FTBFS: src/plugincandidates.cpp:235:13: error: ‘void QTime::start()’ is deprecated: Use QElapsedTimer instead [-Werror=deprecated-declarations])
Your message dated Wed, 15 Jul 2020 15:07:04 +
with message-id
and subject line Bug#964643: fixed in sonic-visualiser 4.1-1
has caused the Debian Bug report #964643,
regarding sonic-visualiser: FTBFS: src/plugincandidates.cpp:235:13: error:
‘void QTime::start()’ is deprecated: Use QElapsedTimer instead
[-Werror=deprecated-declarations]
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.)
--
964643: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964643
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: sonic-visualiser
Version: 4.0.1-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200709 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> g++ -c -pipe -Werror -O2 -fPIC -std=gnu++11 -Wall -Wextra -D_REENTRANT
> -DQT_NO_DEBUG -DQT_CORE_LIB -I. -Ichecker -isystem
> /usr/include/x86_64-linux-gnu/qt5 -isystem
> /usr/include/x86_64-linux-gnu/qt5/QtCore -Io
> -I/usr/lib/x86_64-linux-gnu/qt5/mkspecs/linux-g++ -o o/knownplugins.o
> src/knownplugins.cpp
> src/plugincandidates.cpp: In member function
> ‘std::vector >
> PluginCandidates::runHelper(std::vector >,
> std::string)’:
> src/plugincandidates.cpp:235:13: error: ‘void QTime::start()’ is deprecated:
> Use QElapsedTimer instead [-Werror=deprecated-declarations]
> 235 | t.start();
> | ^
> In file included from /usr/include/x86_64-linux-gnu/qt5/QtCore/QTime:1,
> from src/plugincandidates.cpp:40:
> /usr/include/x86_64-linux-gnu/qt5/QtCore/qdatetime.h:228:55: note: declared
> here
> 228 | QT_DEPRECATED_X("Use QElapsedTimer instead") void start();
> | ^
> src/plugincandidates.cpp:256:31: error: ‘int QTime::elapsed() const’ is
> deprecated: Use QElapsedTimer instead [-Werror=deprecated-declarations]
> 256 | if (t.elapsed() > timeout) {
> | ^
> In file included from /usr/include/x86_64-linux-gnu/qt5/QtCore/QTime:1,
> from src/plugincandidates.cpp:40:
> /usr/include/x86_64-linux-gnu/qt5/QtCore/qdatetime.h:230:54: note: declared
> here
> 230 | QT_DEPRECATED_X("Use QElapsedTimer instead") int elapsed() const;
> | ^~~
> cc1plus: all warnings being treated as errors
> make[4]: *** [Makefile.checker-lib:388: o/plugincandidates.o] Error 1
The full build log is available from:
http://qa-logs.debian.net/2020/07/09/sonic-visualiser_4.0.1-1_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!
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: sonic-visualiser
Source-Version: 4.1-1
Done: =?utf-8?q?IOhannes_m_zm=C3=B6lnig_=28Debian/GNU=29?=
We believe that the bug you reported is fixed in the latest version of
sonic-visualiser, 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 964...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
IOhannes m zmölnig (Debian/GNU) (supplier of updated
sonic-visualiser 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: Wed, 15 Jul 2020 14:58:01 +0200
Source: sonic-visualiser
Architecture: source
Version: 4.1-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Multimedia Maintainers
Changed-By: IOhannes m zmölnig (Debian/GNU)
Closes: 964643
Changes:
sonic-visualiser (4.1-1) unstable; urgency=medium
.
* New upstream version 4.1 (Closes: #964643)
.
* Adjust OSC-documentation path
* Let the build-system invoke 'capnp'
* Fix path to vamp-capnp in "clean" target
* Add CI-configuration
* Update dates in d/copyright
* Regenerate d/copyright_hints
* Bump dh-compat to 13
* Bump standards-version to 4.5.0
Ch
Processed: googler: "No results"
Processing control commands: > fixed -1 4.1-1 Bug #965067 [googler] googler: "No results" Marked as fixed in versions googler/4.1-1. -- 965067: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965067 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#965067: googler: "No results"
Package: googler Version: 3.7.1-1 Severity: grave Control: fixed -1 4.1-1 googler in buster seems completely broken. I get "No results" every time. -- Jakub Wilk
Bug#965064: pkg-haskell-tools: FTBFS in unstable
On Wed, Jul 15, 2020 at 02:40:39PM +0100, Dimitri John Ledkov wrote: > • No instance for (MonadFail Action) arising from a use of ‘fail’ AFAIK (slightly out of the loop), this is because fail is not a part of Monad any more https://downloads.haskell.org/~ghc/8.8.1/docs/html/users_guide/8.8.1-notes.html Upgrading shake will fix this, or it can be worked around in the meantime in pkg-haskell-tools by import Control.Monad.Fail as fail instance MonadFail Action where fail = Fail.fail Don't have time to upload it myself, but HTH. Cheers, -- Iain Lane [ i...@orangesquash.org.uk ] Debian Developer [ la...@debian.org ] Ubuntu Developer [ la...@ubuntu.com ] signature.asc Description: PGP signature
Processed: fix severity
Processing commands for cont...@bugs.debian.org: > severity 965001 serious Bug #965001 [src:python-gmpy2] strange version 2.1.0 beta4 fails tests with mpfr4 4.1.0 Severity set to 'serious' from 'normal' > thanks Stopping processing here. Please contact me if you need assistance. -- 965001: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965001 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#962596: ca-certificates: Removal of GeoTrust Global CA requires investigation
Hi, Thanks for maintaining ca-certificates. I just wanted to let you know that a number of customers of $work are affected by this, and we would very much welcome a return of the GeoTrust Global CA. It'd be nice if the uploaders of the ca-certificates could state what they intend to do, so we could take the appropriate measure locally. Cheers, Thomas Goirand (zigo)
Processed: Bug#964774 marked as pending in freetype
Processing control commands: > tag -1 pending Bug #964774 [src:freetype] freetype: libfreetype6-udeb should not depend on non-udeb libbrotli1 Ignoring request to alter tags of bug #964774 to the same tags previously set -- 964774: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964774 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#964774: marked as pending in freetype
Control: tag -1 pending Hello, Bug #964774 in freetype reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/debian/freetype/-/commit/59066db6afdd51052330ea906f89b9f4f483e173 debian/rules: Run a separate build sequence for libfreetype6-udeb libfreetype6-udeb should not depend on libbrotli1, so run the build sequence before building the main FreeType tree. Closes: #964774 (this message was generated automatically) -- Greetings https://bugs.debian.org/964774
Bug#964680: ibus-pinyin: FTBFS: lmyoslib.c:68:36: error: expected ‘)’ before ‘LUA_QS’
control: tags -1 patch pending
Hello, I uploaded in deferred/5 the following debdiff (and submitted upstream)
Feel free to cancel/reschedule as you wish.
diff -Nru ibus-pinyin-1.5.0/debian/changelog ibus-pinyin-1.5.0/debian/changelog
--- ibus-pinyin-1.5.0/debian/changelog 2019-12-07 21:11:35.0 +0100
+++ ibus-pinyin-1.5.0/debian/changelog 2020-07-15 11:26:32.0 +0200
@@ -1,3 +1,11 @@
+ibus-pinyin (1.5.0-6.1) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Fix lua compatibility issue due to deprecated LUA_QS macro.
+(Closes: #964680)
+
+ -- Gianfranco Costamagna Wed, 15 Jul 2020
11:26:32 +0200
+
ibus-pinyin (1.5.0-6) unstable; urgency=medium
* Team upload.
diff -Nru ibus-pinyin-1.5.0/debian/patches/lua-5.4.patch
ibus-pinyin-1.5.0/debian/patches/lua-5.4.patch
--- ibus-pinyin-1.5.0/debian/patches/lua-5.4.patch 1970-01-01
01:00:00.0 +0100
+++ ibus-pinyin-1.5.0/debian/patches/lua-5.4.patch 2020-07-15
11:26:30.0 +0200
@@ -0,0 +1,19 @@
+Description: Fix lua 5.4 compatibility, due to deprecated LUA_QS macro
+See:
https://polyrex.io/polyrex/dependencies/lua/-/commit/f97c64d7bf4c0f373711795d8faba0e8cd206761
+For reference.
+Author: Gianfranco Costamagna
+Bug-Debian: https://bugs.debian.org/964680
+Forwarded: https://github.com/phuang/ibus-pinyin/pull/18
+Last-Update: 2020-07-15
+
+--- ibus-pinyin-1.5.0.orig/lua/lmyoslib.c
ibus-pinyin-1.5.0/lua/lmyoslib.c
+@@ -65,7 +65,7 @@ static int getfield (lua_State *L, const
+ res = (int)lua_tointeger(L, -1);
+ else {
+ if (d < 0)
+- return luaL_error(L, "field " LUA_QS " missing in date table", key);
++ return luaL_error(L, "field '%s' missing in date table", key);
+ res = d;
+ }
+ lua_pop(L, 1);
diff -Nru ibus-pinyin-1.5.0/debian/patches/series
ibus-pinyin-1.5.0/debian/patches/series
--- ibus-pinyin-1.5.0/debian/patches/series 2019-12-07 21:11:35.0
+0100
+++ ibus-pinyin-1.5.0/debian/patches/series 2020-07-15 11:23:29.0
+0200
@@ -14,3 +14,4 @@
# python3 support
python3.patch
+lua-5.4.patch
Processed: Re: ibus-pinyin: FTBFS: lmyoslib.c:68:36: error: expected ‘)’ before ‘LUA_QS’
Processing control commands: > tags -1 patch pending Bug #964680 [src:ibus-pinyin] ibus-pinyin: FTBFS: lmyoslib.c:68:36: error: expected ‘)’ before ‘LUA_QS’ Added tag(s) patch and pending. -- 964680: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964680 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: libuser: Please stop using deprecated and headers
Processing commands for cont...@bugs.debian.org: > severity 956354 important Bug #956354 [libuser] libuser: Please stop using deprecated and headers Severity set to 'important' from 'serious' > thanks Stopping processing here. Please contact me if you need assistance. -- 956354: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=956354 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#956354: libuser: Please stop using deprecated and headers
severity 956354 important thanks Well actually, selinux support is not enabled in libuser, so this is not RC ATM
Bug#965054: guile-2.0 ftbfs on unstable (test failure)
Package: src:guile-2.0
Version: 2.0.13+1-5.4
Severity: serious
Tags: sid bullseye
After fixing the build with make 4.3, the build then fails with a test failure.
Only seen on amd64, not on other architectures.
[...]
make check-TESTS
make[4]: Entering directory '/<>/guile-2.0-2.0.13+1'
Testing /<>/guile-2.0-2.0.13+1/meta/guile ...
with GUILE_LOAD_PATH=/<>/guile-2.0-2.0.13+1/test-suite
Running 00-initial-env.test
Running 00-repl-server.test
ERROR: 00-repl-server.test: repl-server: HTTP inter-protocol attack - arguments:
((system-error "fport_write" "~A" ("Broken pipe") (32)))
Processed: severity of 950473 is serious
Processing commands for cont...@bugs.debian.org: > severity 950473 serious Bug #950473 [src:openssh-ssh1] Please remove usage of hardcoded SELinux security classes Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 950473: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=950473 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: severity of 956354 is serious
Processing commands for cont...@bugs.debian.org: > severity 956354 serious Bug #956354 [libuser] libuser: Please stop using deprecated and headers Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 956354: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=956354 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: severity of 956355 is serious
Processing commands for cont...@bugs.debian.org: > severity 956355 serious Bug #956355 [pam] pam: Please stop using deprecated and headers Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 956355: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=956355 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: severity of 964710 is serious
Processing commands for cont...@bugs.debian.org: > severity 964710 serious Bug #964710 [src:abinit] abinit: FTBFS: /usr/bin/env: ‘python’: No such file or directory Severity set to 'serious' from 'normal' > thanks Stopping processing here. Please contact me if you need assistance. -- 964710: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964710 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#964038: marked as pending in rabbitmq-server
Control: tag -1 pending Hello, Bug #964038 in rabbitmq-server 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/third-party/rabbitmq-server/-/commit/dfb68b1d2669e02884674a4917f72fb5a464e16d d/changelog: - Ships new version of the Prometheus plugin that works with Erlang version 23 (Closes: #964038). (this message was generated automatically) -- Greetings https://bugs.debian.org/964038
Processed: Bug#964038 marked as pending in rabbitmq-server
Processing control commands: > tag -1 pending Bug #964038 [rabbitmq-server] rabbitmq-server: Prometheus plugin doesn't support Erlang v23 Added tag(s) pending. -- 964038: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964038 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#965050: marked as done (python3-flask-babel: flask_babel broken after recent werkzeug update)
Your message dated Wed, 15 Jul 2020 07:48:29 +
with message-id
and subject line Bug#965050: fixed in flask-babel 0.12.2-1
has caused the Debian Bug report #965050,
regarding python3-flask-babel: flask_babel broken after recent werkzeug update
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.)
--
965050: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965050
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python3-flask-babel
Version: 0.11.2-3
Severity: normal
Tags: upstream
X-Debbugs-Cc: harin...@hurrynot.org
Dear Maintainer,
I use 'fava' which appears to use 'flask_babel'. Recently, 'fava' started
crashing with the following backtrace:
--8<--
Traceback (most recent call last):
File "/usr/bin/fava", line 11, in
load_entry_point('fava==1.14', 'console_scripts', 'fava')()
File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 490, in
load_entry_point
return get_distribution(dist).load_entry_point(group, name)
File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 2859,
in load_entry_point
return ep.load()
File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 2450,
in load
return self.resolve()
File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 2456,
in resolve
module = __import__(self.module_name, fromlist=['__name__'], level=0)
File "/usr/lib/python3/dist-packages/fava/cli.py", line 11, in
from fava.application import app
File "/usr/lib/python3/dist-packages/fava/application.py", line 35, in
from flask_babel import Babel
File "/usr/lib/python3/dist-packages/flask_babel/__init__.py", line 19, in
from werkzeug import ImmutableDict
ImportError: cannot import name 'ImmutableDict' from 'werkzeug'
(/usr/lib/python3/dist-packages/werkzeug/__init__.py)
--8<--
Turns out werkzeug was recently updated:
--8<--
python-werkzeug (1.0.1+dfsg1-2) unstable; urgency=medium
* Uploading to unstable.
-- Ondřej Nový Tue, 14 Jul 2020 09:40:21 +0200
--8<--
The origin of the bug seems to be the use of deprecated exports from werkzeug,
which were removed:
https://github.com/pallets/werkzeug/commit/d50618e3651ad5d4d3118e903a040b733c4d0233#diff-9ab9cda90dbf882c5f053820bffc3d15
The fix appears to be:
https://github.com/python-babel/flask-
babel/commit/fcc347b8e4c751f4cbe36d2a7652bc250f780c99
-- System Information:
Debian Release: bullseye/sid
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'unstable'), (500, 'testing'),
(500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 5.7.0-1-amd64 (SMP w/8 CPU threads)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages python3-flask-babel depends on:
ii python3 3.8.2-3
ii python3-babel 2.8.0+dfsg.1-3
ii python3-flask 1.1.2-1
ii python3-jinja2 2.11.2-1
python3-flask-babel recommends no packages.
Versions of packages python3-flask-babel suggests:
pn python-flask-babel-doc
-- no debconf information
--- End Message ---
--- Begin Message ---
Source: flask-babel
Source-Version: 0.12.2-1
Done: Johannes 'josch' Schauer
We believe that the bug you reported is fixed in the latest version of
flask-babel, 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 965...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Johannes 'josch' Schauer (supplier of updated flask-babel
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: Wed, 15 Jul 2020 09:24:58 +0200
Source: flask-babel
Architecture: source
Version: 0.12.2-1
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group
Changed-By: Johannes 'josch' Schauer
Closes: 965050
Changes:
flask-babel (0.12.2-1) unstable; urgency=medium
.
[ Håvard Flaget Aasen ]
* QA upload
* New upstream release
* Set upstream metadata fields: Bug-Database, Repository,
Repository-Browse.
* d/control
- Bump debhelper to 12
- Update Standards-Version to 4.5.0
-
Bug#965050: marked as pending in flask-babel
Control: tag -1 pending Hello, Bug #965050 in flask-babel 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/modules/flask-babel/-/commit/a4e9ce6a08b7322c92c6170b9782f748577828ee fix import of ImmutableDict from werkzeug (closes: #965050) (this message was generated automatically) -- Greetings https://bugs.debian.org/965050
Processed: Bug#965050 marked as pending in flask-babel
Processing control commands: > tag -1 pending Bug #965050 [python3-flask-babel] python3-flask-babel: flask_babel broken after recent werkzeug update Added tag(s) pending. -- 965050: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965050 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: severity of 965050 is serious, affects 965050
Processing commands for cont...@bugs.debian.org: > severity 965050 serious Bug #965050 [python3-flask-babel] python3-flask-babel: flask_babel broken after recent werkzeug update Severity set to 'serious' from 'normal' > affects 965050 searx Bug #965050 [python3-flask-babel] python3-flask-babel: flask_babel broken after recent werkzeug update Added indication that 965050 affects searx > thanks Stopping processing here. Please contact me if you need assistance. -- 965050: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965050 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#960762: marked as done (libvirt: random (?) test hangs)
Your message dated Wed, 15 Jul 2020 08:57:08 +0200 with message-id <20200715065708.ga3...@bogon.m.sigxcpu.org> and subject line Re: Bug#960762: [Pkg-libvirt-maintainers] Bug#960762: libvirt: random (?) test hangs has caused the Debian Bug report #960762, regarding libvirt: random (?) test hangs 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.) -- 960762: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960762 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libvirt Version: 6.0.0-7 Severity: serious Tags: ftbfs https://buildd.debian.org/status/fetch.php?pkg=libvirt&arch=all&ver=6.0.0-7&stamp=1589452859&raw=0 https://buildd.debian.org/status/fetch.php?pkg=libvirt&arch=i386&ver=6.0.0-7&stamp=1589494701&raw=0 ... make check-TESTS make[4]: Entering directory '/<>/debian/build/tests' make[5]: Entering directory '/<>/debian/build/tests' PASS: sockettest PASS: virbuftest PASS: virhostcputest PASS: seclabeltest PASS: virhashtest PASS: virconftest PASS: viratomictest PASS: utiltest PASS: shunloadtest PASS: viruritest PASS: virtimetest PASS: virkeyfiletest PASS: viralloctest PASS: virauthconfigtest PASS: virbitmaptest SKIP: vircgrouptest PASS: vircryptotest PASS: commandtest PASS: virendiantest PASS: virpcitest PASS: virfilecachetest PASS: virfirewalltest PASS: virkeycodetest PASS: viriscsitest PASS: virlockspacetest PASS: virlogtest PASS: virfiletest PASS: virrotatingfiletest PASS: virstringtest PASS: virportallocatortest PASS: sysinfotest PASS: virkmodtest PASS: vircapstest PASS: domainconftest PASS: virhostdevtest PASS: virnetdevtest PASS: virtypedparamtest SKIP: vshtabletest PASS: virerrortest PASS: virnetmessagetest PASS: domaincapstest PASS: virnetdaemontest PASS: virnetserverclienttest PASS: virschematest PASS: virnettlscontexttest PASS: fchosttest PASS: scsihosttest PASS: vircaps2xmltest PASS: virnettlssessiontest PASS: virresctrltest PASS: fdstreamtest PASS: virdbustest PASS: virsystemdtest PASS: virpolkittest PASS: xlconfigtest PASS: xmconfigtest PASS: libxlxml2domconfigtest PASS: virshtest PASS: qemudomaincheckpointxml2xmltest PASS: qemudomainsnapshotxml2xmltest PASS: qemumonitorjsontest PASS: qemuhotplugtest PASS: qemuxml2xmltest PASS: qemucapabilitiestest PASS: qemuxml2argvtest PASS: qemucaps2xmltest PASS: qemumemlocktest PASS: qemucommandutiltest PASS: qemumigparamstest PASS: qemublocktest PASS: qemufirmwaretest PASS: qemuvhostusertest PASS: lxcxml2xmltest PASS: lxcconf2xmltest PASS: openvzutilstest PASS: esxutilstest PASS: vboxsnapshotxmltest PASS: vmx2xmltest PASS: xml2vmxtest PASS: vmwarevertest PASS: virjsontest PASS: networkxml2xmlupdatetest PASS: virnetworkportxml2xmltest PASS: networkxml2xmltest PASS: networkxml2conftest PASS: networkxml2firewalltest PASS: nwfilterxml2xmltest PASS: virnwfilterbindingxml2xmltest PASS: nwfilterebiptablestest PASS: nwfilterxml2firewalltest PASS: storagevolxml2argvtest PASS: qemusecuritytest PASS: storagepoolxml2argvtest PASS: virstorageutiltest PASS: storagepoolcapstest PASS: storagepoolxml2xmltest PASS: virscsitest PASS: nsstest PASS: nssguesttest PASS: storagevolxml2xmltest PASS: nodedevxml2xmltest PASS: virstoragetest PASS: interfacexml2xmltest PASS: metadatatest PASS: secretxml2xmltest PASS: genericxml2xmltest PASS: virusbtest PASS: virnetdevbandwidthtest PASS: cputest PASS: virdrivermoduletest PASS: eventtest PASS: virdriverconnvalidatetest PASS: objecteventtest PASS: virnetdevopenvswitchtest PASS: virmacmaptest PASS: libvirtd-fail PASS: libvirtd-pool PASS: virsh-define-dev-segfault PASS: virsh-cpuset PASS: virsh-int-overflow PASS: virsh-read-bufsiz PASS: virsh-read-non-seekable PASS: virsh-schedinfo PASS: virsh-self-test PASS: virt-admin-self-test PASS: virsh-checkpoint PASS: virsh-snapshot PASS: virsh-start PASS: qemuagenttest PASS: virsh-undefine PASS: virsh-uriprecedence PASS: virsh-vcpupin PASS: virsh-optparse PASS: virt-aa-helper-test E: Build killed with signal TERM after 150 minutes of inactivity --- End Message --- --- Begin Message --- Version: libvirt/6.4.0-2 Hi, On Wed, Jul 15, 2020 at 12:19:46AM +0200, Andrea Bolognani wrote: > On Fri, Jul 03, 2020 at 12:04:16AM +0200, Andrea Bolognani wrote: > > On Wed, Jul 01, 2020 at 09:24:00AM +0200, Guido Günther wrote: > > > On Tue, Jun 30, 2020 at 09:28:34PM +0200, Andrea Bolognani wrote: > > > > Has anyone managed to reproduce this? I've built 6.0.0-7 from source > > > > in a tight loop 100 times, both in a sid:i386 chroot via cowbuilder > > > > and in a sid:i386 VM, without encountering a single failure. > > > > > > I tried to reproduce too when this came in and couldn't. > >
