Processed: Forwarded bug

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> forwarded 995290 https://github.com/emcconville/wand/issues/558
Bug #995290 [src:wand] wand: FTBFS with imagemagick 6.9.12.20
Set Bug forwarded-to-address to 
'https://github.com/emcconville/wand/issues/558'.
>
End of message, stopping processing here.

Please contact me if you need assistance.
-- 
995290: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995290
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#994969: jackd2: segfaults after today's upgrade of other Debian testing packages

[Ryan Thoryk]

I posted this to the upstream bug report:

---

After debugging glib for a while, I might've found the issue.  According 
to the documentation of g_quark_from_static_string(), that function 
shouldn't be used to initialize a global variable, but that's how it's 
being used in the crash location in glibmm.


As part of doing symbol checks, Jack loads and unloads the firewire 
module a number of times, that has the glibmm dependency.  Then it loads 
the module normally.  Glibmm initializes each load, it shows the glib 
functions being called each time.  Since the glibmm initialization uses 
the static_string function, glib stores the pointer to the static string 
inside it's hash table and creates a new gquark (the doc says a gquark 
object creation at this stage is too early).  What should be happening, 
is that due to the module unloads, previously stored string references 
become invalid in the hash table, causing a segfault when doing an 
strcmp, the function doc says to not use that function if you're going 
to unload the module.  The hash table's address itself remains the same 
during all of the loads and unloads, showing that it's not being 
unloaded.  The g_quark_from_string() function works, because it creates 
copies of the strings instead, so it's unload-safe.


Unlike what we thought of before, the string that glibmm passes to the 
glib function remains valid all the way to the crash, the culprit is 
that strcmp compares against a pointer to invalid memory that comes from 
the glib hash table.


--
Ryan Thoryk
r...@thoryk.com
r...@tliquest.net

Bug#995349: marked as done (ncbi-entrez-direct: FTBFS: no required module provides package github.com/fiam/gounidecode/unidecode)

[Debian Bug Tracking System]

Your message dated Mon, 04 Oct 2021 00:48:54 +
with message-id 
and subject line Bug#995349: fixed in ncbi-entrez-direct 14.6.20210224+dfsg-5
has caused the Debian Bug report #995349,
regarding ncbi-entrez-direct: FTBFS: no required module provides package 
github.com/fiam/gounidecode/unidecode
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.)


-- 
995349: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995349
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ncbi-entrez-direct
Version: 14.6.20210224+dfsg-4
Severity: serious
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu impish

Hi Aaron,

The ncbi-entrez-direct package currently fails to build in Debian unstable:

[...]
go build -v -gccgoflags '-g -O2 
-ffile-prefix-map=/tmp/ncbi-entrez-direct-14.6.20210224+dfsg=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wl,-z,relro 
-Wl,-z,now -Wl,--as-needed' -o bin/rchive rchive.go common.go
rchive.go:40:2: no required module provides package 
github.com/fiam/gounidecode/unidecode: go.mod file not found in current 
directory or any parent directory; see 'go help modules'
rchive.go:41:2: no required module provides package github.com/klauspost/cpuid: 
go.mod file not found in current directory or any parent directory; see 'go 
help modules'
rchive.go:42:2: no required module provides package github.com/pbnjay/memory: 
go.mod file not found in current directory or any parent directory; see 'go 
help modules'
rchive.go:43:2: no required module provides package 
github.com/surgebase/porter2: go.mod file not found in current directory or any 
parent directory; see 'go help modules'
common.go:71:2: no required module provides package golang.org/x/text/runes: 
go.mod file not found in current directory or any parent directory; see 'go 
help modules'
common.go:72:2: no required module provides package 
golang.org/x/text/transform: go.mod file not found in current directory or any 
parent directory; see 'go help modules'
common.go:73:2: no required module provides package 
golang.org/x/text/unicode/norm: go.mod file not found in current directory or 
any parent directory; see 'go help modules'
make[1]: *** [debian/rules:130: bin/rchive] Error 1
[...]

This failure is also reproducible in Ubuntu, where I first noticed it:

  
https://launchpad.net/ubuntu/+source/ncbi-entrez-direct/14.6.20210224+dfsg-4/+build/21767337

This failure prevents the newer version of the package from being included
in the upcoming Ubuntu release.

Thanks,
-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developer   https://www.debian.org/
slanga...@ubuntu.com vor...@debian.org


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: ncbi-entrez-direct
Source-Version: 14.6.20210224+dfsg-5
Done: Aaron M. Ucko 

We believe that the bug you reported is fixed in the latest version of
ncbi-entrez-direct, 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 995...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Aaron M. Ucko  (supplier of updated ncbi-entrez-direct 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, 03 Oct 2021 20:28:46 -0400
Source: ncbi-entrez-direct
Architecture: source
Version: 14.6.20210224+dfsg-5
Distribution: unstable
Urgency: high
Maintainer: Debian Med Packaging Team 

Changed-By: Aaron M. Ucko 
Closes: 995349
Changes:
 ncbi-entrez-direct (14.6.20210224+dfsg-5) unstable; urgency=high
 .
   * debian/rules:
 - Force traditional GOPATH mode (GO111MODULE=off) to avoid needing to
   produce proper offline go.mod and go.sum files, which turned out not
   to be nearly as straightforward as I'd hoped.  It's not clear how
   much longer this option will be available, but it works in 1.16 and
   from what I gather even 1.17 after all.  (Closes: #995349.)
 - Substitute .../klauspost/cpuid/v2 for .../klauspost/cpuid as needed.
 - Set CGO_{C,CPP,CXX,F,LD}FLAGS 

Bug#994969: jackd2: segfaults after today's upgrade of other Debian testing packages

[Ryan Thoryk]

I found that my edits were affecting the wrong file (I was working on a 
cached file instead, there were multiple copies of the code), and so my 
string modification doesn't actually work, it results in the same segfault.


Changing the function to q_quark_from_string() works.

--
Ryan Thoryk
r...@thoryk.com
r...@tliquest.net

Processed: Re: Bug#995392: ghostscript: ps2pdf trashes some characters

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> notforwarded 995678
Bug #995678 [texlive-base] texlive-base: pdflatex in TeX Live 2021 potentially 
generates invalid PDF, making ps2pdf silently trash some characters
Unset Bug forwarded-to-address
>
End of message, stopping processing here.

Please contact me if you need assistance.
-- 
995678: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995678
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: Re: Bug#995392: ghostscript: ps2pdf trashes some characters

[Debian Bug Tracking System]

Processing control commands:

> clone -1 -2
Bug #995392 [ghostscript] ghostscript: ps2pdf trashes some characters
Bug 995392 cloned as bug 995678
> reassign -2 texlive-base 2021.20210921-1
Bug #995678 [ghostscript] ghostscript: ps2pdf trashes some characters
Bug reassigned from package 'ghostscript' to 'texlive-base'.
No longer marked as found in versions ghostscript/9.54.0~dfsg-5 and 
ghostscript/9.53.3~dfsg-8.
Ignoring request to alter fixed versions of bug #995678 to the same values 
previously set
Bug #995678 [texlive-base] ghostscript: ps2pdf trashes some characters
Marked as found in versions texlive-base/2021.20210921-1.
> retitle -2 texlive-base: pdflatex in TeX Live 2021 potentially generates 
> invalid PDF, making ps2pdf silently trash some characters
Bug #995678 [texlive-base] ghostscript: ps2pdf trashes some characters
Changed Bug title to 'texlive-base: pdflatex in TeX Live 2021 potentially 
generates invalid PDF, making ps2pdf silently trash some characters' from 
'ghostscript: ps2pdf trashes some characters'.

-- 
995392: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995392
995678: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995678
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#995676: kmymoney FTBFS in bookworm.

[peter green]

Package: kmymoney
Version: 5.1.2-1
Severity: serious

While working on completing the kde transition in Raspbian bookworm I ran into 
a build
failure of kmymoney.

http://buildd.raspbian.org/status/fetch.php?pkg=kmymoney=armhf=5.1.2-1=1633154962


In file included from 
/<>/kmymoney/plugins/kbanking/dialogs/kbmapaccount.cpp:18:
/<>/kmymoney/plugins/kbanking/dialogs/../kbanking.h:161:49: error: 
expected ';' at end of member declaration
  161 | bool updateAccount(const MyMoneyAccount& acc) DEPRECATED;
  | ^
  |  ;
/<>/kmymoney/plugins/kbanking/dialogs/../kbanking.h:161:51: error: 
'DEPRECATED' does not name a type; did you mean 'QT_DEPRECATED'?
  161 | bool updateAccount(const MyMoneyAccount& acc) DEPRECATED;
  |   ^~
  |   QT_DEPRECATED


This is also happening on the reproducible builds tests for bookworm, on
all architectures tested by reproducible builds (amd64, i386, arm64 and armhf)
so it's not a raspbian specific issue.

I do not know if this also affects sid, the reproducible builds tests for sid 
are
showing a pass, but they were last run about a month ago, so something may have
changed in the meantime.

To get the package building in raspbian, I simply removed the DEPRECATED, I
don't know whether that is the best fix though.

Bug#995007: marked as done (gnustep-base ftbfs with updated autoconf/automake)

[Debian Bug Tracking System]

Your message dated Sun, 03 Oct 2021 23:34:08 +
with message-id 
and subject line Bug#995007: fixed in gnustep-base 1.27.0-4
has caused the Debian Bug report #995007,
regarding gnustep-base ftbfs with updated autoconf/automake
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.)


-- 
995007: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995007
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:gnustep-base
Version: 1.27.0-3
Severity: serious
Tags: sid bookworm

Seen while doing binNMUs for the libffi transition, blocking this transition:

[...]
dh_auto_configure -- \
ac_cv_lib_kvm_kvm_getenvv=no \
--disable-bfd  || (cat config.log; exit 1)
./configure --build=x86_64-linux-gnu --prefix=/usr
--includedir=\${prefix}/include --mandir=\${prefix}/share/man
--infodir=\${prefix}/share/info --sysconfdir=/etc --localstatedir=/var
--disable-option-checking --disable-silent-rules
--libdir=\${prefix}/lib/x86_64-linux-gnu --runstatedir=/run
--disable-maintainer-mode --disable-dependency-tracking
ac_cv_lib_kvm_kvm_getenvv=no --disable-bfd
configure: error: cannot find required auxiliary files:
tail -v -n \+0 config.log
==> config.log <==

[...]

## --- ##
## Core tests. ##
## --- ##

configure:2965: looking for aux files: config.guess config.sub
configure:3031: error: cannot find required auxiliary files:
--- End Message ---
--- Begin Message ---
Source: gnustep-base
Source-Version: 1.27.0-4
Done: Yavor Doganov 

We believe that the bug you reported is fixed in the latest version of
gnustep-base, 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 995...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Yavor Doganov  (supplier of updated gnustep-base 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, 29 Sep 2021 22:15:52 +0300
Source: gnustep-base
Architecture: source
Version: 1.27.0-4
Distribution: unstable
Urgency: medium
Maintainer: Debian GNUstep maintainers 

Changed-By: Yavor Doganov 
Closes: 995007
Changes:
 gnustep-base (1.27.0-4) unstable; urgency=medium
 .
   * debian/rules (override_dh_auto_configure): Fix FTBFS with
 Autoconf/2.71 (Closes: #995007).
Checksums-Sha1:
 38415a1f05370e3d94999a22d648b1cba6d11fe6 2965 gnustep-base_1.27.0-4.dsc
 386bd5e3f475c93156e622185db8e53592219f33 33208 
gnustep-base_1.27.0-4.debian.tar.xz
 0294ee195bdc9381da3cd59709eaf5a2861f79c9 7065 
gnustep-base_1.27.0-4_source.buildinfo
Checksums-Sha256:
 1475d4e106ead43e389d4dbe2ee94b73f6eff2a11bfd875b270c0590c1c16b46 2965 
gnustep-base_1.27.0-4.dsc
 3433524342ea6716428feb36efa002b8e5f3a1379cd45948c9aaa6b778f13948 33208 
gnustep-base_1.27.0-4.debian.tar.xz
 6bb26d238c65b921f37299884d483ab708b36493fe5f3ebcca8d0ddc59e5991a 7065 
gnustep-base_1.27.0-4_source.buildinfo
Files:
 e8d91b08b6dcb831da54c144e416fa91 2965 gnustep optional 
gnustep-base_1.27.0-4.dsc
 a2912f9e65a6fb6a88732d4cf314f6c6 33208 gnustep optional 
gnustep-base_1.27.0-4.debian.tar.xz
 708b104db98a3a1685abdd3383529b97 7065 gnustep optional 
gnustep-base_1.27.0-4_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJIBAEBCAAyFiEEU0DQATYMplbjSX63DEjqKnqP/XsFAmFaOeUUHHBsdWd3YXNo
QGRlYmlhbi5vcmcACgkQDEjqKnqP/XvCMQ/+L9oOkVwwmeHSkyNgUAGC1n5qgk1l
2TwflZblCht7D4Jliep7BmjmQoZFHt3lLMeYDfA5k14qDm5dHIxI0kQeyVEFQXWK
cu2q4BKNjUr33+EVIPSdhkxVFW5mdWhS5k+Nh9MdCJdXduMNpOvC2rwnw4f4KBhk
cfVLflMxerGRqAu+ElluuY88Zs1pjZYQACmoaVvwOeqt0fOLZ0DsnXumJnBLFTbL
HuskF0B/vYyffZdidvkYcZF1ZJRlnI+6dKdT1t8qdwitA0SwQ5+ENDEYhq1LFlfZ
kivxu81t8PqjlhV6xGNJ65XpqX0E3mjetabSJAugM26faowNSxe+07GYP8T5bQG1
xNsTq8/1OUIq7FscgsP4AQi4jntvcb85UNls/vuisScnVlIdkvui6FjUCZ2lic4N
wlbPO/uEhd4dqufC6OKi+4N0PfuRhy43QPntQv1zwLTQAGxEcLP8KLI8yFMwvz/l
MWph1tVvO+zM6cB1IN3CeBYCQBARVjUz+30fDheTElKomfnJhdLazUq2skDgqG/8
lueEX2p/Mzdl6+fKqUONdyd9Vqs5pDizBRLpOhOu3kfB2RQunU/WbXaqZazrEFLg
cbzMJiqQrBFd6sSAGok7SAY7EJmbjf2GNTTQI8OIWI8o9vbNEdfADFCjrniXYqSW
6XZM7UZRhY1jv8I=
=lhPj
-END PGP SIGNATURE End Message ---

Bug#931345: marked as done (nvchecker: autopkgtest regression in June 2019)

[Debian Bug Tracking System]

Your message dated Sun, 03 Oct 2021 23:19:49 +
with message-id 
and subject line Bug#931345: fixed in nvchecker 2.5-1
has caused the Debian Bug report #931345,
regarding nvchecker: autopkgtest regression in June 2019
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.)


-- 
931345: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=931345
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: nvchecker
Version: 1.3-2
Severity: important
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: regression

Dear maintainers,

Somewhere between 2019-05-28 and 2019-06-28, your package started to
fail in buster for version 1.3.2, and somewhere between 2019-06-10 and
2019-06-15 is started failing in unstable for version 1.4.3-1.

I copied some of the output at the bottom of this report.

Unfortunately, the regression isn't caught by the migration software, so
this is either caused by an indirect dependency of your package (maybe
hints can be found here [1]), or by an external factor. Please
investigate and fix your autopkgtest.

Paul

[1]
https://ci.debian.net/data/packages/unstable/amd64/n/nvchecker/2492039.log

https://ci.debian.net/data/autopkgtest/unstable/amd64/n/nvchecker/2492039/log.gz

=== FAILURES
===
_ test_anitya
__

get_version = .__call__ at 0x7f1f241d6e18>

async def test_anitya(get_version):
> assert await get_version("shutter", {"anitya": "fedora/shutter"})
== "0.94.2"
E AssertionError: assert '0.94.3' == '0.94.2'
E   - 0.94.3
E   ?  ^
E   + 0.94.2
E   ?  ^

tests/test_anitya.py:8: AssertionError
 test_debianpkg


get_version = .__call__ at 0x7f1f238a69d8>

@flaky(max_runs=10)
async def test_debianpkg(get_version):
>   assert await get_version("sigrok-firmware-fx2lafw",
{"debianpkg": None}) == "0.1.6-1"

tests/test_debianpkg.py:10:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
_ _ _ _
tests/conftest.py:50: in __call__
return await _get_version(name, config)
/usr/lib/python3/dist-packages/nvchecker/get_version.py:90: in get_version
version = await func(name, conf, **kwargs)
/usr/lib/python3/dist-packages/nvchecker/source/debianpkg.py:23: in
get_version
logger.error('Debian package not found', name=name)
/usr/lib/python3/dist-packages/structlog/_base.py:176: in _proxy_to_logger
args, kw = self._process_event(method_name, event, event_kw)
/usr/lib/python3/dist-packages/structlog/_base.py:136: in _process_event
event_dict = proc(self._logger, method_name, event_dict)
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
_ _ _ _

logger = )>
method_name = 'error'
event_dict = {'event': 'Debian package not found', 'logger_name':
'nvchecker.source.debianpkg', 'name': 'sigrok-firmware-fx2lafw'}

def proc(logger, method_name, event_dict):
  if method_name in ('warning', 'error'):
if 'exc_info' in event_dict:
  raise event_dict['exc_info']
>   raise RuntimeError(event_dict['event'])
E   RuntimeError: Debian package not found

tests/conftest.py:68: RuntimeError
_ test_debianpkg_strip_release
_

get_version = .__call__ at 0x7f1f238a69d8>

@flaky(max_runs=10)
async def test_debianpkg_strip_release(get_version):
>   assert await get_version("sigrok-firmware-fx2lafw",
{"debianpkg": None, "strip-release": 1}) == "0.1.6"

tests/test_debianpkg.py:14:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
_ _ _ _
tests/conftest.py:50: in __call__
return await _get_version(name, config)
/usr/lib/python3/dist-packages/nvchecker/get_version.py:90: in get_version
version = await func(name, conf, **kwargs)
/usr/lib/python3/dist-packages/nvchecker/source/debianpkg.py:23: in
get_version
logger.error('Debian package not found', name=name)
/usr/lib/python3/dist-packages/structlog/_base.py:176: in _proxy_to_logger
args, kw = self._process_event(method_name, event, event_kw)
/usr/lib/python3/dist-packages/structlog/_base.py:136: in _process_event
event_dict = proc(self._logger, method_name, event_dict)
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
_ _ _ _

logger = )>
method_name = 'error'
event_dict = {'event': 'Debian package not found', 'logger_name':
'nvchecker.source.debianpkg', 'name': 'sigrok-firmware-fx2lafw'}

def 

Processed: bug is RC

[Debian Bug Tracking System]

Processing control commands:

> severity -1 grave
Bug #995417 [src:python-requests-oauthlib] python-requests-oauthlib: please 
update to current upstream version 1.3.0
Severity set to 'grave' from 'wishlist'

-- 
995417: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995417
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#995625: httping FTBFS: error: format not a string literal and no format arguments [-Werror=format-security]

[Abhijith PA]

Thank you folkert. I will be very happy to take the patch, if you have 
committed in upstream repo. :)


--abhijith 


On 03/10/21 07:49 PM, folkert wrote:
> replace it by:
> 
> wprintw(w, "%s", what);
> 
> On Sun, Oct 03, 2021 at 07:48:19AM +0200, Helmut Grohne wrote:
> > Source: httping
> > Version: 2.5-5.1
> > Severity: serious
> > Tags: ftbfs
> > 
> > httping fails to build from source in unstable on amd64. A non-parallel
> > build ends as follows:
> > 
> > | x86_64-linux-gnu-gcc -g -O2 -ffile-prefix-map=/<>=. 
> > -fstack-protector-strong -Wformat -Werror=format-security -Wall -W -Wextra 
> > -pedantic -D_FORTIFY_SOURCE=2  -DVERSION=\"2.5\" 
> > -DLOCALEDIR=\"/usr/share/locale\" -DTCP_TFO -DNC -DFW -D_DEBUG -ggdb 
> > -Wdate-time -D_FORTIFY_SOURCE=2  -c -o nc.o nc.c
> > | nc.c: In function ???myprint???:
> > | nc.c:238:3: error: format not a string literal and no format arguments 
> > [-Werror=format-security]
> > |   238 |   wprintw(w, what);
> > |   |   ^~~
> > | nc.c: In function ???draw_graph???:
> > | nc.c:611:24: warning: unused parameter ???val??? [-Wunused-parameter]
> > |   611 | void draw_graph(double val)
> > |   | ~~~^~~
> > | nc.c: In function ???status_line???:
> > | nc.c:389:2: warning: ignoring return value of ???vasprintf??? declared 
> > with attribute ???warn_unused_result??? [-Wunused-result]
> > |   389 |  vasprintf(, fmt, ap);
> > |   |  ^
> > | cc1: some warnings being treated as errors
> > | make[1]: *** [: nc.o] Error 1
> > | make[1]: Leaving directory '/<>'
> > | dh_auto_build: error: make -j1 returned exit code 2
> > | make: *** [debian/rules:10: build] Error 25
> > | dpkg-buildpackage: error: debian/rules build subprocess returned exit 
> > status 2
> > 
> > This is likely caused by ncurses adding format string annotations.
> > 
> > Helmut
> 
> 
> Folkert van Heusden
> 
> -- 
> MultiTail ist eine flexible Applikation um Logfiles und Kommando
> Eingaben zu überprüfen. Inkl. Filter, Farben, Zusammenführen,
> Ansichten etc. http://www.vanheusden.com/multitail/
> --
> Phone: +31-6-41278122, PGP-key: 1F28D8AE, www.vanheusden.com

Bug#994285: marked as done (libseccomp: FTBFS on arm64, armhf, mips64el and mipsel)

[Debian Bug Tracking System]

Your message dated Sun, 03 Oct 2021 21:51:18 +
with message-id 
and subject line Bug#994285: fixed in libseccomp 2.5.2-2
has caused the Debian Bug report #994285,
regarding libseccomp: FTBFS on arm64, armhf, mips64el and mipsel
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.)


-- 
994285: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=994285
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libseccomp
Version: 2.5.1-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)

Hi,

libseccomp fails to build on arm64, armhf, mips64el and mipsel. This in
turn makes the tests of my package mmdebstrap fail because of the
resulting Multi-Arch:same version skew between amd64 and arm64.

Thanks!

cheers, josch
--- End Message ---
--- Begin Message ---
Source: libseccomp
Source-Version: 2.5.2-2
Done: Felix Geyer 

We believe that the bug you reported is fixed in the latest version of
libseccomp, 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 994...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Felix Geyer  (supplier of updated libseccomp 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, 03 Oct 2021 23:26:59 +0200
Source: libseccomp
Architecture: source
Version: 2.5.2-2
Distribution: unstable
Urgency: medium
Maintainer: Kees Cook 
Changed-By: Felix Geyer 
Closes: 994285
Changes:
 libseccomp (2.5.2-2) unstable; urgency=medium
 .
   * Revert mips and powerpc multiplexed syscall handling.
 - Fixes test suite failures. (Closes: #994285)
Checksums-Sha1:
 21c1e41767272f819b7c4104d75fafa018987bc6 2676 libseccomp_2.5.2-2.dsc
 49c7a7a27bf190333a0636adcdc45d70f962d376 27776 libseccomp_2.5.2-2.debian.tar.xz
Checksums-Sha256:
 fe35f84dea6f5b9e4e7c30481c45e96f4c6ce77d351d2bf242a47251ed1a6b0a 2676 
libseccomp_2.5.2-2.dsc
 70718c5e060d0b275a9e5dccdf109a8dc6720043392736cc474f61f74853c1ce 27776 
libseccomp_2.5.2-2.debian.tar.xz
Files:
 5aa39f755f5c86efef45189190302ca3 2676 libs optional libseccomp_2.5.2-2.dsc
 d2677ae59c76eaee78fcb89c8f9aceb6 27776 libs optional 
libseccomp_2.5.2-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEFkxwUS95KUdnZKtW/iLG/YMTXUUFAmFaIKgACgkQ/iLG/YMT
XUWk8A//bBIYqAw2JF1dbD6tjwYh9Y/AVIoB1+ryBgKBkMkHdFGuG55oSep2hpzm
LggWh7OSh7MMmHNL8+A/J5n6mgTEKaViZpntrkV+YvU4z9+L8gKHgDQ938QhY3FL
7NNlZvztjJk2woeef2YBI+AhsHdhhHWqyGG0LtHp7EbAlnW8qfQj84ReR+M62A4c
sZCMtpRqtYLipayD96fMMGdn1EmRWI+x95HigS0cIlHIpmf7w5eHp1q5mfyVp3Ju
alyuzgmp0L7uVZtpJB8vzvavu73+5TkT7qIE2Ih/UACX6An4tEODScHxdWUF6RHa
OtW1hYuJODX9AwF7gvFQwIHHut9TvP3Rj/gEzzxFinMlJnOT4/ilw424j54/pXOs
qJKQAb8Fkhjha3RSXrDnpOZL5qKT7idfqzf6gJG2j/Zh0WtSqRRPAkDGSNrumupl
hnYX6YEC4MH17uxVEUKOq6qBespm1SsD7/h+PEaMXCjAQagVn3BVI6WktCO7fO13
nFrUEnt1f7l51m2CoUVMg0lDGTkGbKxQ6V8mVUovgWG9x7mxQpxNhKFg60lP9g7c
AY4fehuO0h1llFRmHd4w3lpIbhamn3s/hgiRb9BvZEqYnupKbFNz/7XQB9zuymvQ
LnXr0nvRli1WLU1LqXjIQEe0Iv5qzrOFRPAqC96lA/DCD8MwBz0=
=nM/s
-END PGP SIGNATURE End Message ---

Bug#995672: cockpit-machines: 253-1 fails to build via apt-src

[Friedemann Schorer]

Package: cockpit-machines
Version: 253-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source

Dear Maintainer,

Got the latest source packages for cockpit-machines 253-1, unpacked them
locally via 'dpkg-source -x', made the source known to apt-src ('apt-src
import cockpit-machines --location cockpit-machines-253') and tried to
build it.
Here's the output:

 ~/build: apt-src list  
   
i   cockpit-machin 253-1  /home/frschorer/build/cockpit-machines-253   
 ~/build: apt-src build cockpit-machines
  
E: Not installed

When I import the sourcetree of cockpit 254-1 from unstable sources,
too,  and then try to build cockpit-machines apt-src builds the other cockpit 
packages instead.

I build a few packages through apt-src and never had this problem with any 
source package before, neither cockpit related packages nor others.

Pls let me know if you need additional info - I'd be happy to provide it
if possible.

-- System Information:
Debian Release: 10.10
  APT prefers oldstable-updates
  APT policy: (500, 'oldstable-updates'), (500, 'oldstable-proposed-updates'), 
(500, 'oldstable')
Architecture: amd64 (x86_64)

Kernel: Linux 5.10.0-0.bpo.8-amd64 (SMP w/12 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), 
LANGUAGE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages cockpit-machines depends on:
ii  cockpit-bridge 254-1
ii  libvirt-clients5.0.0-4+deb10u1
ii  libvirt-daemon-system  5.0.0-4+deb10u1
ii  libvirt-dbus   1.3.0-1

Versions of packages cockpit-machines recommends:
ii  gir1.2-libosinfo-1.0  1.2.0-1
ii  python3-gi3.30.4-1
pn  qemu-block-extra  
pn  virtinst  

cockpit-machines suggests no packages.

-- no debconf information

Bug#995608: marked as done (Black screen on AMD Ryzen based systems (AMDGPU related when AMD Secure Memory Encryption not disabled -- mem_encrypt=off))

[Debian Bug Tracking System]

Your message dated Sun, 03 Oct 2021 20:34:35 +
with message-id 
and subject line Bug#994453: fixed in linux 5.14.9-2
has caused the Debian Bug report #994453,
regarding Black screen on AMD Ryzen based systems (AMDGPU related when AMD 
Secure Memory Encryption not disabled -- mem_encrypt=off)
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.)


-- 
994453: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=994453
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:linux
Version: 5.14.6-3
Severity: grave
Justification: renders package unusable

Dear Maintainer,

using this kernel, my machine no longer boots.  Instead of showing a prompt to
enter the LUKS passphrase (as is done in version linux-image-5.10.0-7-amd64) a
non-blinking cursor is shown.  Nothing happens afterwards.

Version linux-image-5.10.0-7-amd64 still works, but newer versions
(linux-image-5.10.0-8-amd64 and the version this report is for) produce the
behaviour mentioned above.

I’m afraid that I don’t have a decent idea on what extra information to provide.



-- Package-specific info:
** Kernel log: boot messages should be attached

** Model information
sys_vendor: To Be Filled By O.E.M.
product_name: To Be Filled By O.E.M.
product_version: To Be Filled By O.E.M.
chassis_vendor: To Be Filled By O.E.M.
chassis_version: To Be Filled By O.E.M.
bios_vendor: American Megatrends Inc.
bios_version: P4.00
board_vendor: ASRock
board_name: B450 Steel Legend
board_version:

** Network interface configuration:
*** /etc/network/interfaces:

source /etc/network/interfaces.d/*

auto lo
iface lo inet loopback

allow-hotplug enp9s0
iface enp9s0 inet dhcp
iface enp9s0 inet6 auto

** PCI devices:
00:00.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse 
Root Complex [1022:1480]
Subsystem: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Root 
Complex [1022:1480]
Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: 
Kernel driver in use: pcieport

00:01.3 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse 
GPP Bridge [1022:1483] (prog-if 00 [Normal decode])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: 
Kernel driver in use: pcieport

00:02.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse 
PCIe Dummy Host Bridge [1022:1482]
Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: 
Kernel driver in use: pcieport

00:04.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse 
PCIe Dummy Host Bridge [1022:1482]
Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: 
Kernel driver in use: pcieport

00:08.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse 
PCIe Dummy Host Bridge [1022:1482]
Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- TAbort- Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: 
Kernel driver in use: pcieport

00:14.0 SMBus [0c05]: Advanced Micro Devices, Inc. [AMD] FCH SMBus Controller 
[1022:790b] (rev 61)
Subsystem: ASRock Incorporation FCH SMBus Controller [1849:]
Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap- 66MHz+ UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- 
SERR- TAbort- 
SERR- 

Bug#995495: marked as done (Black screen on AMD Ryzen based systems (AMDGPU related when AMD Secure Memory Encryption not disabled -- mem_encrypt=off))

[Debian Bug Tracking System]

Your message dated Sun, 03 Oct 2021 20:34:35 +
with message-id 
and subject line Bug#994453: fixed in linux 5.14.9-2
has caused the Debian Bug report #994453,
regarding Black screen on AMD Ryzen based systems (AMDGPU related when AMD 
Secure Memory Encryption not disabled -- mem_encrypt=off)
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.)


-- 
994453: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=994453
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:linux
Version: 5.14.6-3
Severity: important
X-Debbugs-Cc: deb...@s.muenzel.net

amdgpu fails to initialize at boot with linux-image-5.14.0.1-amd64, the
same system boots using 5.10.0-1-amd64.

Graphics card is a Radeon PRO WX 3200, CPU is a AMD Ryzen 9 3900X,
motherboard is ASRock X570 Taichi using latest BIOS.

-- Package-specific info:
** Version:
Linux version 5.14.0-1-amd64 (debian-ker...@lists.debian.org) (gcc-10 (Debian 
10.3.0-11) 10.3.0, GNU ld (GNU Binutils for Debian) 2.37) #1 SMP Debian 
5.14.6-3 (2021-09-28)

** Command line:
BOOT_IMAGE=/boot/vmlinuz-5.14.0-1-amd64 root=/dev/mapper/smallssd-sid--root ro 
quiet

** Tainted: D (128)
 * kernel died recently, i.e. there was an OOPS or BUG

** Kernel log:
[0.00] Linux version 5.14.0-1-amd64 (debian-ker...@lists.debian.org) 
(gcc-10 (Debian 10.3.0-11) 10.3.0, GNU ld (GNU Binutils for Debian) 2.37) #1 
SMP Debian 5.14.6-3 (2021-09-28)
[0.00] Command line: BOOT_IMAGE=/boot/vmlinuz-5.14.0-1-amd64 
root=/dev/mapper/smallssd-sid--root ro quiet
[0.00] x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point 
registers'
[0.00] x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers'
[0.00] x86/fpu: Supporting XSAVE feature 0x004: 'AVX registers'
[0.00] x86/fpu: xstate_offset[2]:  576, xstate_sizes[2]:  256
[0.00] x86/fpu: Enabled xstate features 0x7, context size is 832 bytes, 
using 'compacted' format.
[0.00] signal: max sigframe size: 1776
[0.00] BIOS-provided physical RAM map:
[0.00] BIOS-e820: [mem 0x-0x0009] usable
[0.00] BIOS-e820: [mem 0x000a-0x000f] reserved
[0.00] BIOS-e820: [mem 0x0010-0x09afefff] usable
[0.00] BIOS-e820: [mem 0x09aff000-0x09ff] reserved
[0.00] BIOS-e820: [mem 0x0a00-0x0a1f] usable
[0.00] BIOS-e820: [mem 0x0a20-0x0a213fff] ACPI NVS
[0.00] BIOS-e820: [mem 0x0a214000-0xbb6c] usable
[0.00] BIOS-e820: [mem 0xbb6d-0xbcd18fff] reserved
[0.00] BIOS-e820: [mem 0xbcd19000-0xbcd4afff] ACPI data
[0.00] BIOS-e820: [mem 0xbcd4b000-0xbd436fff] ACPI NVS
[0.00] BIOS-e820: [mem 0xbd437000-0xbdf77fff] reserved
[0.00] BIOS-e820: [mem 0xbdf78000-0xbdffefff] type 20
[0.00] BIOS-e820: [mem 0xbdfff000-0xbeff] usable
[0.00] BIOS-e820: [mem 0xbf00-0xbfff] reserved
[0.00] BIOS-e820: [mem 0xf000-0xf7ff] reserved
[0.00] BIOS-e820: [mem 0xfd20-0xfd2f] reserved
[0.00] BIOS-e820: [mem 0xfd40-0xfd5f] reserved
[0.00] BIOS-e820: [mem 0xfea0-0xfea0] reserved
[0.00] BIOS-e820: [mem 0xfeb8-0xfec01fff] reserved
[0.00] BIOS-e820: [mem 0xfec1-0xfec10fff] reserved
[0.00] BIOS-e820: [mem 0xfed0-0xfed00fff] reserved
[0.00] BIOS-e820: [mem 0xfed4-0xfed44fff] reserved
[0.00] BIOS-e820: [mem 0xfed8-0xfed8] reserved
[0.00] BIOS-e820: [mem 0xfedc2000-0xfedc] reserved
[0.00] BIOS-e820: [mem 0xfedd4000-0xfedd5fff] reserved
[0.00] BIOS-e820: [mem 0xff00-0x] reserved
[0.00] BIOS-e820: [mem 0x0001-0x00183f2f] usable
[0.00] BIOS-e820: [mem 0x00183f30-0x00183fff] reserved
[0.00] NX (Execute Disable) protection: active
[0.00] efi: EFI v2.70 by American Megatrends
[0.00] efi: ACPI=0xbd41e000 ACPI 2.0=0xbd41e014 TPMFinalLog=0xbd3e8000 
SMBIOS=0xbde24000 SMBIOS 3.0=0xbde23000 MEMATTR=0xb8074298 ESRT=0xb5871598 
[0.00] secureboot: Secure boot could not be determined (mode 0)
[0.00] SMBIOS 3.2.0 

Bug#995234: marked as done (Black screen on AMD Ryzen based systems (AMDGPU related when AMD Secure Memory Encryption not disabled -- mem_encrypt=off))

[Debian Bug Tracking System]

Your message dated Sun, 03 Oct 2021 20:34:35 +
with message-id 
and subject line Bug#994453: fixed in linux 5.14.9-2
has caused the Debian Bug report #994453,
regarding Black screen on AMD Ryzen based systems (AMDGPU related when AMD 
Secure Memory Encryption not disabled -- mem_encrypt=off)
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.)


-- 
994453: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=994453
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: linux-image-amd64
Version: 5.14.6-2
Severity: important

Dear Maintainer,

after today's kernel-upgrade in testing to linux-image-5.14.0-1-amd64 (version 
5.14.6-2)
X cannot be started on my machine neither by lightdm nor by hand with startx.
Booting with linux-image-5.10.0-8-amd64 (version 5.10.46-5) all works fine.

Hardware: AMD Ryzen3 3200G with Radeon Vega Graphics managed by amdgpu

I'll attach the relevant log-files for both kernels. But looking at Xorg.0.log 
it seems
as if the amdgpu-driver doesn't recognize the GPU any more and lists all 
supported
chipsets instead.
And than:

"[10.869] (II) modesetting: Driver for Modesetting Kernel Drivers: kms
[10.869] (II) FBDEV: driver for framebuffer: fbdev
[10.869] (II) VESA: driver for VESA chipsets: vesa
[10.870] (EE) open /dev/dri/card0: No such file or directory
[10.870] (WW) Falling back to old probe method for modesetting
[10.870] (EE) open /dev/dri/card0: No such file or directory
[10.870] (II) Loading sub module "fbdevhw"
[10.870] (II) LoadModule: "fbdevhw"
[10.870] (II) Loading /usr/lib/xorg/modules/libfbdevhw.so
[10.870] (II) Module fbdevhw: vendor="X.Org Foundation"
[10.870]compiled for 1.20.11, module version = 0.0.2
[10.870]ABI class: X.Org Video Driver, version 24.1
[10.871] (EE) Unable to find a valid framebuffer device
[10.871] (WW) Falling back to old probe method for fbdev
[10.871] (II) Loading sub module "fbdevhw"
[10.871] (II) LoadModule: "fbdevhw"
[10.871] (II) Loading /usr/lib/xorg/modules/libfbdevhw.so
[10.871] (II) Module fbdevhw: vendor="X.Org Foundation"
[10.871]compiled for 1.20.11, module version = 0.0.2
[10.871]ABI class: X.Org Video Driver, version 24.1
[10.871] (EE) open /dev/fb0: No such file or directory
[10.871] (EE) Screen 0 deleted because of no matching config section.
[10.871] (II) UnloadModule: "modesetting"
[10.871] (EE) Screen 0 deleted because of no matching config section.
[10.871] (II) UnloadModule: "fbdev"
[10.871] (II) UnloadSubModule: "fbdevhw"
[10.871] (II) Loading sub module "vbe"
[10.871] (II) LoadModule: "vbe"
[10.871] (II) Loading /usr/lib/xorg/modules/libvbe.so
[10.871] (II) Module vbe: vendor="X.Org Foundation"
[10.871]compiled for 1.20.11, module version = 1.1.0
[10.871]ABI class: X.Org Video Driver, version 24.1
[10.871] (II) Loading sub module "int10"
[10.871] (II) LoadModule: "int10"
[10.871] (II) Loading /usr/lib/xorg/modules/libint10.so
[10.871] (II) Module int10: vendor="X.Org Foundation"
[10.871]compiled for 1.20.11, module version = 1.0.0
[10.871]ABI class: X.Org Video Driver, version 24.1
[10.871] (II) VESA(0): initializing int10
[10.872] (EE) VESA(0): No V_BIOS found
[10.872] (II) UnloadModule: "vesa"
[10.872] (II) UnloadSubModule: "int10"
[10.872] (II) Unloading int10
[10.872] (II) UnloadSubModule: "vbe"
[10.872] (II) Unloading vbe
[10.872] (EE) Screen(s) found, but none have a usable configuration.
[10.872] (EE)
Fatal server error:
[10.872] (EE) no screens found(EE)
[10.872] (EE) "

Loaded kernel modules with 5.10.0-8:
lsmod | grep gpu
amdgpu   6606848  20
gpu_sched  40960  1 amdgpu
ttm   114688  1 amdgpu
drm_kms_helper274432  1 amdgpu
i2c_algo_bit   16384  1 amdgpu
drm   618496  7 gpu_sched,drm_kms_helper,amdgpu,ttm

Loaded kernel modules with 5.14.0-1:
lsmod | grep gpu
amdgpu   7778304  0
gpu_sched  45056  1 amdgpu
drm_ttm_helper 16384  1 amdgpu
ttm86016  2 amdgpu,drm_ttm_helper
drm_kms_helper307200  1 amdgpu
i2c_algo_bit   16384  1 amdgpu
drm   634880  5 
gpu_sched,drm_kms_helper,amdgpu,drm_ttm_helper,ttm

Whatever this causes, it only happens with the new kernel and makes it useless 
for me.
Would be nice if you had a look into it ;-)

Klaumi


-- System Information:
Debian Release: bookworm/sid
  APT prefers testing
  APT policy: 

Bug#995120: marked as done (Black screen on AMD Ryzen based systems (AMDGPU related when AMD Secure Memory Encryption not disabled -- mem_encrypt=off))

[Debian Bug Tracking System]

Your message dated Sun, 03 Oct 2021 20:34:35 +
with message-id 
and subject line Bug#994453: fixed in linux 5.14.9-2
has caused the Debian Bug report #994453,
regarding Black screen on AMD Ryzen based systems (AMDGPU related when AMD 
Secure Memory Encryption not disabled -- mem_encrypt=off)
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.)


-- 
994453: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=994453
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:linux
Version: 5.14.6-2
Severity: critical
Justification: breaks the whole system

Dear Maintainer,

* What led up to the situation?

Booting an AMD Raven Bridge computer with this kernel renders the system 
unusable because the amdgpu driver
cannot initialize. This happens because the kernel config enables secure memory 
encryption (SME) which
is not compatible with RAVEN [1]. In this case, the kernel will contain:

  amdgpu: SME is not compatible with RAVEN

* What exactly did you do (or not do) that was effective (or
 ineffective)?

Disabling SME is the only option, passing mem_encrypt=off to the kernel solves 
the problem

Since disabling SME on all systems is clearly overkill, I think the best option 
would be for the GRUB
scripts to probe for Raven Bridge and add "mem_encrypt=off". Based on [1], this 
should probably be done
by looking at the PCI devices.

[1] https://lore.kernel.org/linux-iommu/20200907104431.gh16...@8bytes.org/

-- Package-specific info:
** Version:
Linux version 5.14.0-1-amd64 (debian-ker...@lists.debian.org) (gcc-10 (Debian 
10.3.0-10) 10.3.0, GNU ld (GNU Binutils for Debian) 2.37) #1 SMP Debian 
5.14.6-2 (2021-09-19)

** Command line:
BOOT_IMAGE=/vmlinuz-5.14.0-1-amd64 root=/dev/mapper/debian--vg-root ro quiet 
iommu=pt amd_iommu_dump=1 acpi_osi=Linux mem_encrypt=off

** Tainted: OE (12288)
 * externally-built ("out-of-tree") module was loaded
 * unsigned module was loaded

** Kernel log:
[   10.586405] hid-multitouch 0018:044E:121F.0001: input,hidraw0: I2C HID v1.00 
Mouse [DELL0814:01 044E:121F] on i2c-DELL0814:01
[   10.594029] EXT4-fs (sda3): mounted filesystem without journal. Opts: 
(null). Quota mode: none.
[   10.594040] ext2 filesystem being mounted at /boot supports timestamps until 
2038 (0x7fff)
[   10.653242] input: HD-Audio Generic HDMI/DP,pcm=3 as 
/devices/pci:00/:00:08.1/:04:00.1/sound/card0/input17
[   10.653341] input: HD-Audio Generic HDMI/DP,pcm=7 as 
/devices/pci:00/:00:08.1/:04:00.1/sound/card0/input18
[   10.653426] input: HD-Audio Generic HDMI/DP,pcm=8 as 
/devices/pci:00/:00:08.1/:04:00.1/sound/card0/input19
[   10.663692] kvm: Nested Virtualization enabled
[   10.663696] SVM: kvm: Nested Paging enabled
[   10.663698] SEV supported: 16 ASIDs
[   10.663699] SEV-ES supported: 4294967295 ASIDs
[   10.663728] SVM: Virtual VMLOAD VMSAVE supported
[   10.663729] SVM: Virtual GIF supported
[   10.679112] dell_laptop: Using i8042 filter function for receiving events
[   10.685779] ath10k_pci :01:00.0: enabling device ( -> 0002)
[   10.686432] ath10k_pci :01:00.0: pci irq msi oper_irq_mode 2 irq_mode 0 
reset_mode 0
[   10.692311] MCE: In-kernel MCE decoding enabled.
[   10.721343] snd_hda_codec_realtek hdaudioC1D0: autoconfig for ALC3246: 
line_outs=1 (0x14/0x0/0x0/0x0/0x0) type:speaker
[   10.721355] snd_hda_codec_realtek hdaudioC1D0:speaker_outs=0 
(0x0/0x0/0x0/0x0/0x0)
[   10.721358] snd_hda_codec_realtek hdaudioC1D0:hp_outs=1 
(0x21/0x0/0x0/0x0/0x0)
[   10.721360] snd_hda_codec_realtek hdaudioC1D0:mono: mono_out=0x0
[   10.721362] snd_hda_codec_realtek hdaudioC1D0:inputs:
[   10.721363] snd_hda_codec_realtek hdaudioC1D0:  Headset Mic=0x19
[   10.721365] snd_hda_codec_realtek hdaudioC1D0:  Headphone Mic=0x1a
[   10.721367] snd_hda_codec_realtek hdaudioC1D0:  Internal Mic=0x12
[   10.768989] intel_rapl_common: Found RAPL domain package
[   10.768994] intel_rapl_common: Found RAPL domain core
[   10.780103] audit: type=1400 audit(1632665699.799:2): apparmor="STATUS" 
operation="profile_load" profile="unconfined" name="firejail-default" pid=740 
comm="apparmor_parser"
[   10.780768] audit: type=1400 audit(1632665699.803:3): apparmor="STATUS" 
operation="profile_load" profile="unconfined" name="lsb_release" pid=741 
comm="apparmor_parser"
[   10.781872] audit: type=1400 audit(1632665699.803:4): apparmor="STATUS" 
operation="profile_load" profile="unconfined" name="nvidia_modprobe" pid=744 
comm="apparmor_parser"
[   10.781878] audit: type=1400 audit(1632665699.803:5): apparmor="STATUS" 

Bug#994453: marked as done (Black screen on AMD Ryzen based systems (AMDGPU related when AMD Secure Memory Encryption not disabled -- mem_encrypt=off))

[Debian Bug Tracking System]

Your message dated Sun, 03 Oct 2021 20:34:35 +
with message-id 
and subject line Bug#994453: fixed in linux 5.14.9-2
has caused the Debian Bug report #994453,
regarding Black screen on AMD Ryzen based systems (AMDGPU related when AMD 
Secure Memory Encryption not disabled -- mem_encrypt=off)
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.)


-- 
994453: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=994453
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:linux
Version: 5.14.3-1~exp1
Severity: critical
Justification: breaks the whole system

Dear Maintainer,

booting the kernel on the computer as given in the description below
hangs at the message "loading initial ramdisk" (no change of display
mode, just the two initial boot message lines)

Turning off the boot "quiet" option, and/or adding "nomodeset" doesn't
change things.

regards,
Gert


-- Package-specific info:
** Kernel log: boot messages should be attached

** Model information
sys_vendor: ASUSTeK COMPUTER INC.
product_name: TUF Gaming FX505DY_FX505DY
product_version: 1.0   
chassis_vendor: ASUSTeK COMPUTER INC.
chassis_version: 1.0   
bios_vendor: American Megatrends Inc.
bios_version: FX505DY.308
board_vendor: ASUSTeK COMPUTER INC.
board_name: FX505DY
board_version: 1.0   

** PCI devices:
00:00.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD]
Raven/Raven2 Root Complex [1022:15d0]
Subsystem: ASUSTeK Computer Inc. Raven/Raven2 Root Complex
[1043:17c1]
Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop-
ParErr- Stepping- SERR- FastB2B- DisINTx-
Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort-
SERR- TAbort-
SERR- 

00:01.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family
17h (Models 00h-1fh) PCIe Dummy Host Bridge [1022:1452]
Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop-
ParErr- Stepping- SERR- FastB2B- DisINTx-
Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort-
SERR- TAbort-
SERR- TAbort-
Reset-
FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: 
Kernel driver in use: pcieport

00:01.2 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD]
Raven/Raven2 PCIe GPP Bridge [6:0] [1022:15d3] (prog-if 00 [Normal
decode])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
ParErr- Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort-
SERR- TAbort-
Reset-
FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: 
Kernel driver in use: pcieport

00:01.3 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD]
Raven/Raven2 PCIe GPP Bridge [6:0] [1022:15d3] (prog-if 00 [Normal
decode])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
ParErr- Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort+
SERR- TAbort-
Reset-
FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: 
Kernel driver in use: pcieport

00:01.4 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD]
Raven/Raven2 PCIe GPP Bridge [6:0] [1022:15d3] (prog-if 00 [Normal
decode])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
ParErr- Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort-
SERR- TAbort-
Reset-
FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: 
Kernel driver in use: pcieport

00:08.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family
17h (Models 00h-1fh) PCIe Dummy Host Bridge [1022:1452]
Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop-
ParErr- Stepping- SERR- FastB2B- DisINTx-
Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort-
SERR- TAbort-
SERR- TAbort-
Reset-
FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: 
Kernel driver in use: pcieport

00:08.2 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD]
Raven/Raven2 Internal PCIe GPP Bridge 0 to Bus B [1022:15dc] (prog-if
00 [Normal decode])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
ParErr- Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort-
SERR- TAbort-
Reset-
FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: 
Kernel driver in use: 

Processed: reassign 995655 to dnsmasq, found 995655 in 2.86-1

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> reassign 995655 dnsmasq
Bug #995655 [src:dnsmasq, src:systemd] dnsmasq breaks systemd autopkgtest: 
b'megasearch.net: 192.168.42.1' not found in b'megasearch.net: 207.148.248.143
Bug reassigned from package 'src:dnsmasq, src:systemd' to 'dnsmasq'.
No longer marked as found in versions systemd/247.9-1 and dnsmasq/2.86-1.
Ignoring request to alter fixed versions of bug #995655 to the same values 
previously set
> found 995655 2.86-1
Bug #995655 [dnsmasq] dnsmasq breaks systemd autopkgtest: b'megasearch.net: 
192.168.42.1' not found in b'megasearch.net: 207.148.248.143
Marked as found in versions dnsmasq/2.86-1.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
995655: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995655
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#995495: Description change

[Salvatore Bonaccorso]

Hi,

On Sun, Oct 03, 2021 at 10:33:10PM +0800, deb...@s.muenzel.net wrote:
> Looks like the bug title was changed to say "laptop" this is a desktop
> computer.
> 
> Also, the kernel does not hang -- it continues booting, and it is possible
> to log in via ssh.

Yes the subject could be better indeed, I wanted to higlight the
common set for all of 994453, 994949, 995120, 995234, 995608 and
995495.

We will in any case change in the next upload that AMD Secure Memory
Encryption is not activated by default, though enabled, as the
impacted users were defintively more than the benefit of haging it
activated by default.

Will be either in 5.14.9-2 or with a later further import of the
5.14.y series.

Salvatore

Bug#995608: linux-image-5.14.0-1-amd64: Boot immediately hangs.

[Salvatore Bonaccorso]

Hi Vincent!

On Sun, Oct 03, 2021 at 09:36:10PM +0200, Vincent Blut wrote:
> Le 2021-10-03 20:58, Salvatore Bonaccorso a écrit :
> > Hi Vincent,
> > 
> > On Sun, Oct 03, 2021 at 03:55:21PM +0200, Vincent Blut wrote:
> > > Hi,
> > > 
> > > Le 2021-10-03 11:40, Nathanael Schweers a écrit :
> > > > 
> > > > Salvatore Bonaccorso  writes:
> > > > 
> > > > > Control: tags -1 + moreinfo
> > > > >
> > > > > Hi Nathanael,
> > > > >
> > > > > On Sun, Oct 03, 2021 at 10:02:35AM +0200, Nathanael Schweers wrote:
> > > > >> Package: src:linux
> > > > >> Version: 5.14.6-3
> > > > >> Severity: grave
> > > > >> Justification: renders package unusable
> > > > >>
> > > > >> Dear Maintainer,
> > > > >>
> > > > >> using this kernel, my machine no longer boots.  Instead of showing a 
> > > > >> prompt to
> > > > >> enter the LUKS passphrase (as is done in version 
> > > > >> linux-image-5.10.0-7-amd64) a
> > > > >> non-blinking cursor is shown.  Nothing happens afterwards.
> > > > >>
> > > > >> Version linux-image-5.10.0-7-amd64 still works, but newer versions
> > > > >> (linux-image-5.10.0-8-amd64 and the version this report is for) 
> > > > >> produce the
> > > > >> behaviour mentioned above.
> > > > >>
> > > > >> I’m afraid that I don’t have a decent idea on what extra information 
> > > > >> to provide.
> > > > >
> > > > > Could you please confirm that booting with the 'mem_encrypt=off'
> > > > > kernel command line heps?
> > > > 
> > > > With this option the kernel does indeed boot.  Thanks for the tip!
> > > 
> > > Salvatore, given the increase in bug reports that this feature generates,
> > > I think it would be sensible to unset AMD_MEM_ENCRYPT_ACTIVE_BY_DEFAULT 
> > > until
> > > those incompatibilities are fixed, like I proposed in [1]. One would have 
> > > to
> > > use the "mem_encrypt=on" command line option to enable the AMD Secure 
> > > Memory
> > > Encryption. If it sounds reasonable to you and the rest of the kernel 
> > > team,
> > > I can send a merge request.
> > 
> > Yes I think at this point is reasonable, as people wanting the feature
> > still can enable it, but we do not break usual setups as it has hit
> > severral people arleady. Can you post the reference [1], it was not
> > included.  No need for a merge request, as I have the change already
> > in debian/config/kernelarch-x86/config .
> 
> Oops, sorry about that. [1] was supposed to point to 
> https://salsa.debian.org/kernel-team/linux/-/merge_requests/322/diffs

Ah thanks! We should have done that probably already at that time.

Pushed now the change to sid branch, so will be included in next
upload for unstable.

Regards,
Salvatore

Processed: severity of 994453 is serious

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> # lets raise severity to RC as the impact of the regression is worse as the 
> benefit of having AMD Secure Memory Encryption enabled by default
> severity 994453 serious
Bug #994453 [src:linux] Black screen on AMD Ryzen based systems (AMDGPU related 
when AMD Secure Memory Encryption not disabled -- mem_encrypt=off)
Bug #994949 [src:linux] Black screen on AMD Ryzen based systems (AMDGPU related 
when AMD Secure Memory Encryption not disabled -- mem_encrypt=off)
Bug #995120 [src:linux] Black screen on AMD Ryzen based systems (AMDGPU related 
when AMD Secure Memory Encryption not disabled -- mem_encrypt=off)
Bug #995234 [src:linux] Black screen on AMD Ryzen based systems (AMDGPU related 
when AMD Secure Memory Encryption not disabled -- mem_encrypt=off)
Bug #995495 [src:linux] Black screen on AMD Ryzen based systems (AMDGPU related 
when AMD Secure Memory Encryption not disabled -- mem_encrypt=off)
Bug #995608 [src:linux] Black screen on AMD Ryzen based systems (AMDGPU related 
when AMD Secure Memory Encryption not disabled -- mem_encrypt=off)
Severity set to 'serious' from 'important'
Severity set to 'serious' from 'important'
Severity set to 'serious' from 'important'
Severity set to 'serious' from 'important'
Severity set to 'serious' from 'important'
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
994453: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=994453
994949: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=994949
995120: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995120
995234: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995234
995495: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995495
995608: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995608
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#972570: [Pkg-javascript-devel] Bug#972570: node-lightgallery is built using minified files

[Joe Nahmias]

Hello,

Now that bullseye has been released, would it be possible to upload a fix
for this to unstable? That would allow node-lightgallery and rainloop to
migrate to testing (bookworm) and then be backported to bullseye.

If you are not able to do this at the moment, due to time constraints, I'm
happy to prepare the upload based on what's in Salsa, as long as it's okay
with the JS team.

Thanks,
--Joe

On Sat, Apr 24, 2021 at 04:12:06PM -0700, Daniel Ring wrote:
> It looks like this RC bug also caused the next version of Rainloop to be
> removed from bullseye before the freeze. That version contains an relatively
> important security fix (bug #962629), so both Rainloop and node-lightgallery
> will need to be uploaded to bullseye-backports (when available) as well as
> unstable.
> 
> Sincerely,
> Daniel Ring
> 
> On 4/23/2021 9:35 PM, Daniel Ring wrote:
> > The warnings are already overridden in the current version on Salsa,
> > since the Youtube/Vimeo/etc. embeds are only loaded when Lightgallery is
> > used to display a video from that source (e.g. by passing it a Youtube
> > link).
> > 
> > Sincerely,
> > Daniel Ring
> > 
> > On 4/23/2021 12:31 PM, Yadd wrote:
> > > Le 23/04/2021 à 19:03, Jonas Smedegaard a écrit :
> > > > Quoting Yadd (2021-04-23 17:47:23)
> > > > > Control: tags -1 + pending
> > > > > 
> > > > > Le 23/04/2021 à 09:44, Daniel Ring a écrit :
> > > > > > Hello Xavier,
> > > > > > 
> > > > > > It looks like the build process was minifying the source files to 
> > > > > > the
> > > > > > destination *.js files and copying the pre-minified
> > > > > > files to *.min.js. I
> > > > > > corrected it to copy the unminified files directly and minify them 
> > > > > > to
> > > > > > *.min.js.
> > > > > > 
> > > > > > I also updated the package on Salsa to exclude the minified
> > > > > > modules/*.min.js files via Files-Excluded in
> > > > > > d/copyright, so they're no
> > > > > > longer in the source package at all.
> > > > > > 
> > > > > > Sincerely,
> > > > > > Daniel Ring
> > > > > 
> > > > > Hi,
> > > > > 
> > > > > looks good to me, thanks! Could you also ignore these warnings in a
> > > > > debain/lintian-overrides? It looks like false positive
> > > > > 
> > > > > Cheers,
> > > > > Yadd
> > > > > 
> > > > >   W: node-lightgallery: privacy-breach-generic
> > > > > usr/share/nodejs/lightgallery/dist/js/lg-video.min.min.js [ > > > > class="lg-video-object lg-dailymotion '+o+'" '+l+' width="560"
> > > > > height="315"
> > > > [...]
> > > > Those warnings look real to me.
> > > > 
> > > > What makes you consider them false positives, Xavier?
> > > 
> > > Hi Jonas,
> > > 
> > > yes but the relevant lines are in if/then/else blocks:
> > > 
> > >    if (isVideo.youtube) {
> > >  ...  video = 

Bug#995655: dnsmasq breaks systemd autopkgtest: b'megasearch.net: 192.168.42.1' not found in b'megasearch.net: 207.148.248.143

[Michael Biebl]

Control: reassign -1 dnsmasq/2.86-1

It's a (known) regression in dnsmasq 2.86-1

CCing what I sent Simon privately a couple of days ago


Hi Simon,

as you probably know, the recent update of dnsmasq 2.86 to unstable broke the 
systemd autopkgtests, namely test-networkd.py, and more specifically

==
ERROR: test_resolved_domain_restricted_dns (__main__.DnsmasqClientTest)
resolved: domain-restricted DNS servers
--
Traceback (most recent call last):
  File 
"/tmp/autopkgtest-lxc.knebmh6r/downtmp/build.00t/src/test/networkd-test.py", 
line 659, in test_resolved_domain_restricted_dns
out = subprocess.check_output(['resolvectl', 'query', 'search.example.com'])
  File "/usr/lib/python3.9/subprocess.py", line 424, in check_output
return run(*popenargs, stdout=PIPE, timeout=timeout, check=True,
  File "/usr/lib/python3.9/subprocess.py", line 528, in run
raise CalledProcessError(retcode, process.args,
subprocess.CalledProcessError: Command '['resolvectl', 'query', 
'search.example.com']' returned non-zero exit status 1.

--
Ran 35 tests in 143.025s

FAILED (errors=1, skipped=2)


Afaics, this is a regression introduced by
https://thekelleys.org.uk/gitweb/?p=dnsmasq.git;a=commit;h=12a9aa7c628e2d7dcd34949603848a3fb53fce9c

and should be fixed by
https://thekelleys.org.uk/gitweb/?p=dnsmasq.git;a=commit;h=26bbf5a314d833beaf0f147d24409969f05f3dba




Am 03.10.21 um 19:23 schrieb Paul Gevers:

Source: dnsmasq, systemd
Control: found -1 dnsmasq/2.86-1
Control: found -1 systemd/247.9-1
Severity: serious
Tags: sid bookworm
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: breaks needs-update

Dear maintainer(s),

With a recent upload of dnsmasq the autopkgtest of systemd fails in
testing when that autopkgtest is run with the binary packages of dnsmasq
from unstable. It passes when run with only packages from testing. In
tabular form:

passfail
dnsmasqfrom testing2.86-1
systemdfrom testing247.9-1
all others from testingfrom testing

I copied some of the output at the bottom of this report.

Currently this regression is blocking the migration of dnsmasq to
testing [1]. Due to the nature of this issue, I filed this bug report
against both packages. Can you please investigate the situation and
reassign the bug to the right package?

More information about this bug and the reason for filing it can be found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation

Paul

[0] You can see what packages were added from the second line of the log
file quoted below. The migration software adds source package from
unstable to the list if they are needed to install packages from
dnsmasq/2.86-1. I.e. due to versioned dependencies or breaks/conflicts.
[1] https://qa.debian.org/excuses.php?package=dnsmasq

https://ci.debian.net/data/autopkgtest/testing/amd64/s/systemd/15711756/log.gz


==
FAIL: test_resolved_domain_restricted_dns (__main__.DnsmasqClientTest)
resolved: domain-restricted DNS servers
--
Traceback (most recent call last):
   File
"/tmp/autopkgtest-lxc.re_u3b37/downtmp/build.aCg/src/test/networkd-test.py",
line 660, in test_resolved_domain_restricted_dns
 self.assertIn(b'megasearch.net: 192.168.42.1', out)
AssertionError: b'megasearch.net: 192.168.42.1' not found in
b'megasearch.net: 207.148.248.143 -- link:
eth0\n\n-- Information acquired via protocol DNS in 123.2ms.\n-- Data is
authenticated: no\n'

--






OpenPGP_signature
Description: OpenPGP digital signature

Bug#995260: chrony: Mismatched filename for UNIX socket between client and daemon

[S Egbert]

There is still a Mismatched SOCK filespec implemented by chronyd and chronyc.

The saving grace was that loopback network interface hid this bug very well and 
saved the day for nearly everyone (who is not an expert Chronyd configurer)...

That is, until the directive 'cmddeny 127.0.0.1' is configured: then one finds 
out the hard way that there is no consistent way to open the UNIX socket.  


Workaround:

Don't use 'cmddeny 127.0.0.1' setting for now until the filenaming convention
for its socket file specification becomes synchronized between Chrony client 
and server.



STRACES
---
In all straces below, the config directive is:

  cmddeny 127.0.0.1


Client CLI Fallback method (default)

This following strace details the default operation of ordinary chronyc CLI 
client operation, specifically to send a 'sources' CLI command with hope to 
receive a list of NTP servers.

This shell invocation did NOT use an '-h' option, fallback mechanism to other 
communcation channel methods werre done:  
* Socket failed,  (this bug report)
* IPv4 loopback failed (due to 'cmddeny 127.0.0.1')
* IPv6 loopback failed (not sure how, but it shouldn't have happened)

#Shell Invocation
# strace -f chrony -d -d -d sources

socket(AF_INET, SOCK_DGRAM|SOCK_CLOEXEC, IPPROTO_IP) = 3
socket(AF_INET, SOCK_DGRAM|SOCK_NONBLOCK, IPPROTO_IP) = 3
write(2, "Resolved 127.0.0.1 to 127.0.0.1", 31Resolved 127.0.0.1 to 127.0.0.1) 
= 31
write(2, "\n", 1
write(2, "Resolved ::1 to ::1", 19Resolved ::1 to ::1) = 19
write(2, "\n", 1
socket(AF_UNIX, SOCK_DGRAM|SOCK_CLOEXEC|SOCK_NONBLOCK, 0) = 3
unlink("/var/run/chrony/chronyc.21014.sock") = -1 ENOENT (No such file or 
directory)
write(2, "Could not remove /var/run/chrony"..., 79Could not remove 
/var/run/chrony/chronyc.21014.sock : No such file or directory) = 79
write(2, "\n", 1
bind(3, {sa_family=AF_UNIX, sun_path="/var/run/chrony/chronyc.21014.sock"}, 
110) = -1 EACCES (Permission denied)
write(2, "Could not bind Unix socket to /v"..., 84Could not bind Unix socket to 
/var/run/chrony/chronyc.21014.sock : Permission denied) = 84
write(2, "\n", 1
getsockname(3, {sa_family=AF_UNIX}, [112->2]) = 0
socket(AF_INET, SOCK_DGRAM|SOCK_CLOEXEC|SOCK_NONBLOCK, IPPROTO_IP) = 3
write(2, "Opened UDPv4 socket fd=3 remote="..., 45Opened UDPv4 socket fd=3 
remote=127.0.0.1:323) = 45
write(2, "Could not receive message fd=3 :"..., 51Could not receive message 
fd=3 : Connection refused) = 51
write(2, "\n", 1
getsockname(3, {sa_family=AF_INET, sin_port=htons(34899), 
sin_addr=inet_addr("127.0.0.1")}, [112->16]) = 0
socket(AF_INET6, SOCK_DGRAM|SOCK_CLOEXEC|SOCK_NONBLOCK, IPPROTO_IP) = 3
read(4, "# /etc/nsswitch.conf\n#\n# Example"..., 4096) = 542
read(4, "", 4096)   = 0
read(4, "\177ELF\2\1\1\0\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0\0003\0\0\0\0\0\0"..., 
832) = 832
read(4, "# Internet (IP) protocols\n#\n# Up"..., 4096) = 2932
setsockopt(3, SOL_IPV6, IPV6_V6ONLY, [1], 4) = 0
write(2, "Opened UDPv6 socket fd=3 remote="..., 41Opened UDPv6 socket fd=3 
remote=[::1]:323) = 41
write(2, "\n", 1
write(2, "Sent data fd=3 len=32", 21Sent data fd=3 len=32)   = 21
write(2, "\n", 1
write(2, "Timeout 1.00 seconds", 24Timeout 1.00 seconds) = 24
write(2, "\n", 1
write(2, "Could not receive message fd=3 :"..., 51Could not receive message 
fd=3 : Connection refused) = 51
write(2, "\n", 1
write(2, "Sent data fd=3 len=32", 21Sent data fd=3 len=32)   = 21
write(2, "\n", 1
write(2, "Timeout 2.00 seconds", 24Timeout 2.00 seconds) = 24
write(2, "\n", 1
write(2, "Could not receive message fd=3 :"..., 51Could not receive message 
fd=3 : Connection refused) = 51
write(2, "\n", 1
write(2, "Sent data fd=3 len=32", 21Sent data fd=3 len=32)   = 21
write(2, "\n", 1
write(2, "Timeout 4.00 seconds", 24Timeout 4.00 seconds) = 24
write(2, "\n", 1
write(2, "Could not receive message fd=3 :"..., 51Could not receive message 
fd=3 : Connection refused) = 51
write(2, "\n", 1
getsockname(3, {sa_family=AF_INET6, sin6_port=htons(56416), 
sin6_flowinfo=htonl(0), inet_pton(AF_INET6, "::1", _addr), 
sin6_scope_id=0}, [112->28]) = 0


Client CLI Direct Loopback method
-
The following strace uses '-h' command line option to specify the desired 
sockets, network-based, but we know that daemon has already been directed by 
'cmddeny 127.0.0.1', so no go here.

Since the CLI command line explicitly asked for '-h 127.0.0.1' there were no 
fallback mechanism to try other channel methods (UNIX socket or a non-loopback 
remote network)  

That too failed (correctly) due to 'cmddeny 127.0.0.1' directive.

#Shell Invocation
# strace -f chronyc -h 127.0.0.1 sources

socket(AF_INET, SOCK_DGRAM|SOCK_CLOEXEC, IPPROTO_IP) = 3
socket(AF_INET, SOCK_DGRAM|SOCK_NONBLOCK, IPPROTO_IP) = 3
write(2, "Resolved 127.0.0.1 to 127.0.0.1", 31Resolved 127.0.0.1 to 127.0.0.1) 
= 31
write(2, "\n", 1
socket(AF_INET, SOCK_DGRAM|SOCK_CLOEXEC|SOCK_NONBLOCK, IPPROTO_IP) = 3
write(2, "Opened UDPv4 socket fd=3 

Processed: ruby-chef-utils: depends on the Internet during build

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #995346 [src:ruby-chef-utils] ruby-chef-utils: depends on the Internet 
during build
Severity set to 'serious' from 'important'

-- 
995346: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995346
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#995007: gnustep-base ftbfs with updated autoconf/automake

[Yavor Doganov]

On Sat, 02 Oct 2021 16:01:45 +0300,
Peter Green wrote:
> I see a fix for this issue has been uploaded to mentors, do you want
> me to sponsor it?

I'd be very grateful, thanks in advance!
My usual sponsor is not answering...

Processed: forcibly merging 994453 995608

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> forcemerge 994453 995608
Bug #994453 [src:linux] Kernel hangs on loading initramfs on AMD Ryzen based 
laptop (AMDGPU related when AMD Secure Memory Encryption not disabled -- 
mem_encrypt=off)
Bug #994949 [src:linux] Kernel hangs on loading initramfs on AMD Ryzen based 
laptop (AMDGPU related when AMD Secure Memory Encryption not disabled -- 
mem_encrypt=off)
Bug #995120 [src:linux] Kernel hangs on loading initramfs on AMD Ryzen based 
laptop (AMDGPU related when AMD Secure Memory Encryption not disabled -- 
mem_encrypt=off)
Bug #995234 [src:linux] Kernel hangs on loading initramfs on AMD Ryzen based 
laptop (AMDGPU related when AMD Secure Memory Encryption not disabled -- 
mem_encrypt=off)
Bug #995495 [src:linux] Kernel hangs on loading initramfs on AMD Ryzen based 
laptop (AMDGPU related when AMD Secure Memory Encryption not disabled -- 
mem_encrypt=off)
Bug #995495 [src:linux] Kernel hangs on loading initramfs on AMD Ryzen based 
laptop (AMDGPU related when AMD Secure Memory Encryption not disabled -- 
mem_encrypt=off)
Added tag(s) moreinfo.
Added tag(s) moreinfo.
Added tag(s) moreinfo.
Added tag(s) moreinfo.
Added tag(s) moreinfo.
Bug #995608 [src:linux] linux-image-5.14.0-1-amd64: Boot immediately hangs.
Severity set to 'important' from 'grave'
Marked as found in versions linux/5.14.6-2 and linux/5.14.3-1~exp1.
Added tag(s) upstream.
Bug #994949 [src:linux] Kernel hangs on loading initramfs on AMD Ryzen based 
laptop (AMDGPU related when AMD Secure Memory Encryption not disabled -- 
mem_encrypt=off)
Bug #995120 [src:linux] Kernel hangs on loading initramfs on AMD Ryzen based 
laptop (AMDGPU related when AMD Secure Memory Encryption not disabled -- 
mem_encrypt=off)
Bug #995234 [src:linux] Kernel hangs on loading initramfs on AMD Ryzen based 
laptop (AMDGPU related when AMD Secure Memory Encryption not disabled -- 
mem_encrypt=off)
Merged 994453 994949 995120 995234 995495 995608
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
994453: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=994453
994949: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=994949
995120: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995120
995234: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995234
995495: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995495
995608: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995608
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#993688: marked as done ('file' driver requires '/dev/mapper/' to be a regular file)

[Debian Bug Tracking System]

Your message dated Sun, 3 Oct 2021 21:33:17 +0300
with message-id <6cbd6152-7952-4336-0a87-416467d3a...@msgid.tls.msk.ru>
and subject line Re: Bug#993688: 'file' driver requires 
'/dev/mapper/' to be a regular file
has caused the Debian Bug report #993688,
regarding 'file' driver requires '/dev/mapper/' to be a regular 
file
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.)


-- 
993688: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=993688
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: qemu-system-x86
Version: 1:6.1+dfsg-4
Severity: normal

Hi,

this is a regression from qemu in bullseye to qemu in sid.

I am using a VM with a block device that is a crypted LV. It gets
unlocked by sudo cryptsetup --type=luks open /dev/mapper/drop-c_lv
cryptodevice, resulting in /dev/mapper/cryptodevice being a symlink to
/dev/dm-something with something being a different number every time.

The corresponding XML is

  
  
  
  
pn  vde2

-- no debconf information
--- End Message ---
--- Begin Message ---

Ok. After seeing what it is all about, I'm closing this bugreport.

libvirt has the necessary code for a long time now. When you want to
use a host device, please specify the corresponding setting in the
libvirt config for this. If you insist on using `file' driver, this
is exactly what you get.

One can argue (as I did) that in unix, everything's a file and we
should not distinguish between a regular file and a block device.
But there are multiple things which can be done with a block device
which can't be done with a regular file. For example, direct-access
async-io can be done only with a block device.  Yes, in theory qemu
can be a bit more user-friendly and try to enable those features
which are appropriate for the given "type" of file. But things will
quickly become complicated when you consider what to do with e.g.
migration.

Probably libvirt can be more user-friendly and at least give a warning
in a situation like this.  But this is a different story.

Either way, please specify the proper driver in libvirt configuration.

Thanks,

/mjt--- End Message ---

Bug#995625: httping FTBFS: error: format not a string literal and no format arguments [-Werror=format-security]

[folkert]

4ea9d5b78540c972e3fe1bf44db9f7b3f87c0ad0

On Sun, Oct 03, 2021 at 11:36:12PM +0530, Abhijith PA wrote:
> Thank you folkert. I will be very happy to take the patch, if you have 
> committed in upstream repo. :)
> 
> 
> --abhijith 
> 
> 
> On 03/10/21 07:49 PM, folkert wrote:
> > replace it by:
> > 
> > wprintw(w, "%s", what);
> > 
> > On Sun, Oct 03, 2021 at 07:48:19AM +0200, Helmut Grohne wrote:
> > > Source: httping
> > > Version: 2.5-5.1
> > > Severity: serious
> > > Tags: ftbfs
> > > 
> > > httping fails to build from source in unstable on amd64. A non-parallel
> > > build ends as follows:
> > > 
> > > | x86_64-linux-gnu-gcc -g -O2 -ffile-prefix-map=/<>=. 
> > > -fstack-protector-strong -Wformat -Werror=format-security -Wall -W 
> > > -Wextra -pedantic -D_FORTIFY_SOURCE=2  -DVERSION=\"2.5\" 
> > > -DLOCALEDIR=\"/usr/share/locale\" -DTCP_TFO -DNC -DFW -D_DEBUG -ggdb 
> > > -Wdate-time -D_FORTIFY_SOURCE=2  -c -o nc.o nc.c
> > > | nc.c: In function ???myprint???:
> > > | nc.c:238:3: error: format not a string literal and no format arguments 
> > > [-Werror=format-security]
> > > |   238 |   wprintw(w, what);
> > > |   |   ^~~
> > > | nc.c: In function ???draw_graph???:
> > > | nc.c:611:24: warning: unused parameter ???val??? [-Wunused-parameter]
> > > |   611 | void draw_graph(double val)
> > > |   | ~~~^~~
> > > | nc.c: In function ???status_line???:
> > > | nc.c:389:2: warning: ignoring return value of ???vasprintf??? declared 
> > > with attribute ???warn_unused_result??? [-Wunused-result]
> > > |   389 |  vasprintf(, fmt, ap);
> > > |   |  ^
> > > | cc1: some warnings being treated as errors
> > > | make[1]: *** [: nc.o] Error 1
> > > | make[1]: Leaving directory '/<>'
> > > | dh_auto_build: error: make -j1 returned exit code 2
> > > | make: *** [debian/rules:10: build] Error 25
> > > | dpkg-buildpackage: error: debian/rules build subprocess returned exit 
> > > status 2
> > > 
> > > This is likely caused by ncurses adding format string annotations.
> > > 
> > > Helmut
> > 
> > 
> > Folkert van Heusden
> > 
> > -- 
> > MultiTail ist eine flexible Applikation um Logfiles und Kommando
> > Eingaben zu überprüfen. Inkl. Filter, Farben, Zusammenführen,
> > Ansichten etc. http://www.vanheusden.com/multitail/
> > --
> > Phone: +31-6-41278122, PGP-key: 1F28D8AE, www.vanheusden.com


Folkert van Heusden

-- 
Nagios user? Check out CoffeeSaint - the versatile Nagios status
viewer! http://www.vanheusden.com/java/CoffeeSaint/
--
Phone: +31-6-41278122, PGP-key: 1F28D8AE, www.vanheusden.com

Bug#995658: assimp: autopkgtest regression since ci.d.n hosts run bullseye

[Paul Gevers]

Source: assimp
Version: 5.0.1~ds0-2
Severity: serious
User: debian...@lists.debian.org
Usertags: regression
X-Debbugs-CC: debian...@lists.debian.org

Dear maintainer(s),

Your package has an autopkgtest, great! However, since the release of
bullseye the autopkgtest fails on all architectures (most of the time).
It always failed on armhf and i386, but it now also fails on ppc64el,
arm64 and most of the time on amd64. The difference of course is that
the hosts on which the lxc based tests run are running bullseye instead
of buster (except ci-worker13, on which the test indeed still passes).
Can you please investigate?

Paul

https://ci.debian.net/packages/a/assimp/




OpenPGP_signature
Description: OpenPGP digital signature

Bug#995625: httping FTBFS: error: format not a string literal and no format arguments [-Werror=format-security]

[folkert]

replace it by:

wprintw(w, "%s", what);

On Sun, Oct 03, 2021 at 07:48:19AM +0200, Helmut Grohne wrote:
> Source: httping
> Version: 2.5-5.1
> Severity: serious
> Tags: ftbfs
> 
> httping fails to build from source in unstable on amd64. A non-parallel
> build ends as follows:
> 
> | x86_64-linux-gnu-gcc -g -O2 -ffile-prefix-map=/<>=. 
> -fstack-protector-strong -Wformat -Werror=format-security -Wall -W -Wextra 
> -pedantic -D_FORTIFY_SOURCE=2  -DVERSION=\"2.5\" 
> -DLOCALEDIR=\"/usr/share/locale\" -DTCP_TFO -DNC -DFW -D_DEBUG -ggdb 
> -Wdate-time -D_FORTIFY_SOURCE=2  -c -o nc.o nc.c
> | nc.c: In function ???myprint???:
> | nc.c:238:3: error: format not a string literal and no format arguments 
> [-Werror=format-security]
> |   238 |   wprintw(w, what);
> |   |   ^~~
> | nc.c: In function ???draw_graph???:
> | nc.c:611:24: warning: unused parameter ???val??? [-Wunused-parameter]
> |   611 | void draw_graph(double val)
> |   | ~~~^~~
> | nc.c: In function ???status_line???:
> | nc.c:389:2: warning: ignoring return value of ???vasprintf??? declared with 
> attribute ???warn_unused_result??? [-Wunused-result]
> |   389 |  vasprintf(, fmt, ap);
> |   |  ^
> | cc1: some warnings being treated as errors
> | make[1]: *** [: nc.o] Error 1
> | make[1]: Leaving directory '/<>'
> | dh_auto_build: error: make -j1 returned exit code 2
> | make: *** [debian/rules:10: build] Error 25
> | dpkg-buildpackage: error: debian/rules build subprocess returned exit 
> status 2
> 
> This is likely caused by ncurses adding format string annotations.
> 
> Helmut


Folkert van Heusden

-- 
MultiTail ist eine flexible Applikation um Logfiles und Kommando
Eingaben zu überprüfen. Inkl. Filter, Farben, Zusammenführen,
Ansichten etc. http://www.vanheusden.com/multitail/
--
Phone: +31-6-41278122, PGP-key: 1F28D8AE, www.vanheusden.com

Bug#995621: marked as done (openni-sensor-pointclouds does not trap errors during build)

[Debian Bug Tracking System]

Your message dated Sun, 03 Oct 2021 17:33:51 +
with message-id 
and subject line Bug#995621: fixed in openni-sensor-pointclouds 5.1.0.41.9-4
has caused the Debian Bug report #995621,
regarding openni-sensor-pointclouds does not trap errors during build
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.)


-- 
995621: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995621
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: openni-sensor-pointclouds
Version: 5.1.0.41.9-3
Severity: serious
Justification: policy 4.6

When a compilation step in openni-sensor-pointclouds fails, the
RedistMaker script that wraps the build, does not propagate the failure.
You can find a relevant invocation at:
https://sources.debian.org/src/openni-sensor-pointclouds/5.1.0.41.9-3/Platform/Linux/CreateRedist/RedistMaker/#L78

A very simple fix would be adding "set -e" to the top of the script.
Not propagating failure poses the risk of producing broken packages and
violates Debian policy section 4.6. This kind of bug therefore is
release-critical.

Helmut
--- End Message ---
--- Begin Message ---
Source: openni-sensor-pointclouds
Source-Version: 5.1.0.41.9-4
Done: Jochen Sprickerhof 

We believe that the bug you reported is fixed in the latest version of
openni-sensor-pointclouds, 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 995...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Jochen Sprickerhof  (supplier of updated 
openni-sensor-pointclouds 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, 03 Oct 2021 19:26:30 +0200
Source: openni-sensor-pointclouds
Architecture: source
Version: 5.1.0.41.9-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Multimedia Maintainers 
Changed-By: Jochen Sprickerhof 
Closes: 995621
Changes:
 openni-sensor-pointclouds (5.1.0.41.9-4) unstable; urgency=medium
 .
   [ Ondřej Nový ]
   * Bump Standards-Version to 4.4.1
 .
   [ Debian Janitor ]
   * Set upstream metadata fields: Repository, Repository-Browse.
   * Fix field name typo in debian/copyright (X-Comment => Comment).
   * Update standards version to 4.5.0, no changes needed.
 .
   [ Jochen Sprickerhof ]
   * Drop Homepage (redirects to apple.com)
   * Run RedistMaker with set -e (Closes: #995621)
   * bump policy and debhelper versions
   * drop gitlab-ci
   * Bump d/watch to 4
Checksums-Sha1:
 a5b7b92c4eccf8a46ba5c2a228eec7c9f6a02a27 2236 
openni-sensor-pointclouds_5.1.0.41.9-4.dsc
 dfa4f60248f0b6422ed8225a7fb189b58da12b42 5848 
openni-sensor-pointclouds_5.1.0.41.9-4.debian.tar.xz
 4717296255cd4869183c63c70eb0cd1490bd87ca 6386 
openni-sensor-pointclouds_5.1.0.41.9-4_source.buildinfo
Checksums-Sha256:
 488f729971062f0057242e1de9af3006e0f07aaf501143e4b6526e2596fe3b7a 2236 
openni-sensor-pointclouds_5.1.0.41.9-4.dsc
 fa61425ba15dc7b3dd458bebf040b130a78290cdd169db1e98def18e12e02581 5848 
openni-sensor-pointclouds_5.1.0.41.9-4.debian.tar.xz
 7232055987ea22004a6658382e29665f32d91574aa6cb80e24c7135f0664f1a3 6386 
openni-sensor-pointclouds_5.1.0.41.9-4_source.buildinfo
Files:
 4989d39c304beb6c07c881e810a0b8ce 2236 libs optional 
openni-sensor-pointclouds_5.1.0.41.9-4.dsc
 529c57d6acc8ca71043b94e81885a4d0 5848 libs optional 
openni-sensor-pointclouds_5.1.0.41.9-4.debian.tar.xz
 30553c7bec945377bbe656b6d9524a9e 6386 libs optional 
openni-sensor-pointclouds_5.1.0.41.9-4_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEc7KZy9TurdzAF+h6W//cwljmlDMFAmFZ5/cACgkQW//cwljm
lDPfiA//bkyBgdrVqN64ttmwdWs0HrmepbvBB287cjXV2aOB9RA2zd9wpcZaW/5m
JQ0A5Q6bGc1SsMdU9UILvCLRp3qScXbDI5fFtL4EqX6sO4PdpyoGyTZNWNWksF5y
nDjTJrmGC3uWyr9dRUe/JmGOP7kStqRBxQme/seUjCOgSd86aDxX7+7j3hLDVP2b
fquXtE7pRwSCIwlxYATzXSTIqfggOtjmN6UFFVD5S49axRpiXrsMoXeXS31q2xfO
Ozi9tM9GrqlmAR75JU/vJfuLKrZ0pX+HtugvwVr2gbvDbHqfo6DYbiQIBxlptFwN
YPHISBQH4AOCc1WKq1bz6tqFmqG6W3g1rEej5z95vZHyXXprjdnOwEe7zN0N/+qf
IS6/iaR3qeX0GccIxmlc/M6xH0at5gngfCwKHM6yPQ5JEaai/9YG5q8/g2C44gxB
3hyURZ6Kz/Uf5pTXaxZob7eCAvb5re8SHXFDvW42MSZSlrFwJHXf++2wpIzyGUur
7CPTrbxdumL8IVxv+uyvHyT2r1kNp9Ds32s6KpuaEG3MklrMcqJxCh/Qwk8TtgZZ
iXebF6mgOBocHoAh9OtfGbhCUWPmUnQWtA2E6NA56utonnk0viW7li6AFus0veRl

Bug#995621: marked as pending in openni-sensor-pointclouds

[Jochen Sprickerhof]

Control: tag -1 pending

Hello,

Bug #995621 in openni-sensor-pointclouds 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/openni-sensor-pointclouds/-/commit/704fc82328e534290dccea040b74a69dc68c1f32


Run RedistMaker with set -e

Closes: #995621


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/995621

Processed: Bug#995621 marked as pending in openni-sensor-pointclouds

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #995621 [src:openni-sensor-pointclouds] openni-sensor-pointclouds does not 
trap errors during build
Added tag(s) pending.

-- 
995621: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995621
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#995656: edk2: autopkgtest arm64 regression: test_aavmf_ms_secure_boot_signed: Access Denied

[Paul Gevers]

Source: edk2
Version: 2021.08-1
X-Debbugs-CC: debian...@lists.debian.org
Severity: serious
User: debian...@lists.debian.org
Usertags: regression

Dear maintainer(s),

With a recent upload of edk2 the autopkgtest of edk2 fails in testing on
arm64 when that autopkgtest is run with the binary packages of edk2 from
unstable. It passes when run with only packages from testing. In tabular
form:

   passfail
edk2   from testing2021.08-1
all others from testingfrom testing

I copied some of the output at the bottom of this report.

Currently this regression is blocking the migration to testing [1]. Can
you please investigate the situation and fix it?

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=edk2

https://ci.debian.net/data/autopkgtest/testing/arm64/e/edk2/15713990/log.gz

test_aavmf_ms_secure_boot_signed (__main__.BootToShellTest) ... mkfs.fat
4.2 (2021-01-31)
xorriso 1.5.4 : RockRidge filesystem manipulator, libburnia project.

Drive current: -outdev 'stdio:/tmp/tmprtuo53fa'
Media current: stdio file, overwriteable
Media status : is blank
Media summary: 0 sessions, 0 data blocks, 0 data, 16.2g free
Added to ISO image: directory '/'='/tmp/tmpvt36p18q'
xorriso : UPDATE :   2 files added in 1 seconds
xorriso : UPDATE :   2 files added in 1 seconds
xorriso : UPDATE :  48.36% done
ISO image produced: 65741 sectors
Written to medium : 65741 sectors at LBA 0
Writing to 'stdio:/tmp/tmprtuo53fa' completed successfully.

[=3hBdsDxe: failed to load Boot0001 "UEFI Misc
Device" from VenHw(93E34C7E-B50E-11DF-9223-2443DFD72085,00): Not Found

BdsDxe: loading Boot0002 "UEFI Misc Device 2" from PciRoot(0x0)/Pci(0x1,0x0)

BdsDxe: failed to load Boot0002 "UEFI Misc Device 2" from
PciRoot(0x0)/Pci(0x1,0x0): Access Denied

BdsDxe: loading Boot0003 "EFI Internal Shell" from
Fv(64074AFE-340A-4BE6-94BA-91B5B4D0F71E)/FvFile(7C04A583-9E3E-4F1C-AD65-E05268D0B4D1)

BdsDxe: starting Boot0003 "EFI Internal Shell" from
Fv(64074AFE-340A-4BE6-94BA-91B5B4D0F71E)/FvFile(7C04A583-9E3E-4F1C-AD65-E05268D0B4D1)

UEFI Interactive Shell v2.2

EDK II

UEFI v2.70 (EDK II, 0x0001)

Mapping table

  FS0:
Alias(s):CD0a:;BLK1:

  PciRoot(0x0)/Pci(0x1,0x0)/CDROM(0x0)

 BLK2: Alias(s):

  VenHw(93E34C7E-B50E-11DF-9223-2443DFD72085,00)

 BLK0: Alias(s):

  PciRoot(0x0)/Pci(0x1,0x0)

Press ESC in 5 seconds
to skip startup.nsh or any other key to
continue.


Shell> fs0:
fs0:

FS0:\> \efi\boot\bootaa64.efi
\efi\boot\bootaa64.efi

Command Error Status: Access Denied

FS0:\> reset -s
reset
-s

FAIL



OpenPGP_signature
Description: OpenPGP digital signature

Bug#995655: dnsmasq breaks systemd autopkgtest: b'megasearch.net: 192.168.42.1' not found in b'megasearch.net: 207.148.248.143

[Paul Gevers]

Source: dnsmasq, systemd
Control: found -1 dnsmasq/2.86-1
Control: found -1 systemd/247.9-1
Severity: serious
Tags: sid bookworm
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: breaks needs-update

Dear maintainer(s),

With a recent upload of dnsmasq the autopkgtest of systemd fails in
testing when that autopkgtest is run with the binary packages of dnsmasq
from unstable. It passes when run with only packages from testing. In
tabular form:

   passfail
dnsmasqfrom testing2.86-1
systemdfrom testing247.9-1
all others from testingfrom testing

I copied some of the output at the bottom of this report.

Currently this regression is blocking the migration of dnsmasq to
testing [1]. Due to the nature of this issue, I filed this bug report
against both packages. Can you please investigate the situation and
reassign the bug to the right package?

More information about this bug and the reason for filing it can be found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation

Paul

[0] You can see what packages were added from the second line of the log
file quoted below. The migration software adds source package from
unstable to the list if they are needed to install packages from
dnsmasq/2.86-1. I.e. due to versioned dependencies or breaks/conflicts.
[1] https://qa.debian.org/excuses.php?package=dnsmasq

https://ci.debian.net/data/autopkgtest/testing/amd64/s/systemd/15711756/log.gz


==
FAIL: test_resolved_domain_restricted_dns (__main__.DnsmasqClientTest)
resolved: domain-restricted DNS servers
--
Traceback (most recent call last):
  File
"/tmp/autopkgtest-lxc.re_u3b37/downtmp/build.aCg/src/test/networkd-test.py",
line 660, in test_resolved_domain_restricted_dns
self.assertIn(b'megasearch.net: 192.168.42.1', out)
AssertionError: b'megasearch.net: 192.168.42.1' not found in
b'megasearch.net: 207.148.248.143 -- link:
eth0\n\n-- Information acquired via protocol DNS in 123.2ms.\n-- Data is
authenticated: no\n'

--



OpenPGP_signature
Description: OpenPGP digital signature

Processed: dnsmasq breaks systemd autopkgtest: b'megasearch.net: 192.168.42.1' not found in b'megasearch.net: 207.148.248.143

[Debian Bug Tracking System]

Processing control commands:

> found -1 dnsmasq/2.86-1
Bug #995655 [src:dnsmasq, src:systemd] dnsmasq breaks systemd autopkgtest: 
b'megasearch.net: 192.168.42.1' not found in b'megasearch.net: 207.148.248.143
Marked as found in versions dnsmasq/2.86-1.
> found -1 systemd/247.9-1
Bug #995655 [src:dnsmasq, src:systemd] dnsmasq breaks systemd autopkgtest: 
b'megasearch.net: 192.168.42.1' not found in b'megasearch.net: 207.148.248.143
Marked as found in versions systemd/247.9-1.

-- 
995655: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995655
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#995653: django-mailman3 breaks hyperkitty autopkgtest: 'str' object has no attribute 'display_name'

[Paul Gevers]

Source: django-mailman3, hyperkitty
Control: found -1 django-mailman3/1.3.7-1
Control: found -1 hyperkitty/1.3.4-4
Severity: serious
Tags: sid bookworm
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: breaks needs-update

Dear maintainer(s),

With a recent upload of django-mailman3 the autopkgtest of hyperkitty
fails in testing when that autopkgtest is run with the binary packages
of django-mailman3 from unstable. It passes when run with only packages
from testing. In tabular form:

   passfail
django-mailman3from testing1.3.7-1
hyperkitty from testing1.3.4-4
all others from testingfrom testing

I copied some of the output at the bottom of this report.

Currently this regression is blocking the migration of django-mailman3
to testing [1]. Due to the nature of this issue, I filed this bug report
against both packages. Can you please investigate the situation and
reassign the bug to the right package?

More information about this bug and the reason for filing it can be found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation

Paul

[1] https://qa.debian.org/excuses.php?package=django-mailman3

https://ci.debian.net/data/autopkgtest/testing/amd64/h/hyperkitty/15711755/log.gz

==
ERROR: test_basic_reply (hyperkitty.tests.lib.test_posting.PostingTestCase)
--
Traceback (most recent call last):
  File
"/usr/lib/python3/dist-packages/hyperkitty/tests/lib/test_posting.py",
line 69, in test_basic_reply
self.user.save()
  File
"/usr/lib/python3/dist-packages/django/contrib/auth/base_user.py", line
66, in save
super().save(*args, **kwargs)
  File "/usr/lib/python3/dist-packages/django/db/models/base.py", line
743, in save
self.save_base(using=using, force_insert=force_insert,
  File "/usr/lib/python3/dist-packages/django/db/models/base.py", line
791, in save_base
post_save.send(
  File "/usr/lib/python3/dist-packages/django/dispatch/dispatcher.py",
line 173, in send
return [
  File "/usr/lib/python3/dist-packages/django/dispatch/dispatcher.py",
line 174, in 
(receiver, receiver(signal=self, sender=sender, **named))
  File "/usr/lib/python3/dist-packages/django_mailman3/signals.py", line
101, in create_profile
address.display_name = new_display_name
AttributeError: 'str' object has no attribute 'display_name'

==
ERROR: test_reply_different_sender
(hyperkitty.tests.lib.test_posting.PostingTestCase)
--
Traceback (most recent call last):
  File
"/usr/lib/python3/dist-packages/hyperkitty/tests/lib/test_posting.py",
line 102, in test_reply_different_sender
self.user.save()
  File
"/usr/lib/python3/dist-packages/django/contrib/auth/base_user.py", line
66, in save
super().save(*args, **kwargs)
  File "/usr/lib/python3/dist-packages/django/db/models/base.py", line
743, in save
self.save_base(using=using, force_insert=force_insert,
  File "/usr/lib/python3/dist-packages/django/db/models/base.py", line
791, in save_base
post_save.send(
  File "/usr/lib/python3/dist-packages/django/dispatch/dispatcher.py",
line 173, in send
return [
  File "/usr/lib/python3/dist-packages/django/dispatch/dispatcher.py",
line 174, in 
(receiver, receiver(signal=self, sender=sender, **named))
  File "/usr/lib/python3/dist-packages/django_mailman3/signals.py", line
101, in create_profile
address.display_name = new_display_name
AttributeError: 'str' object has no attribute 'display_name'

==
ERROR: test_smtp_error_raises_postingfailed
(hyperkitty.tests.lib.test_posting.PostingTestCase)
--
Traceback (most recent call last):
  File
"/usr/lib/python3/dist-packages/hyperkitty/tests/lib/test_posting.py",
line 89, in test_smtp_error_raises_postingfailed
self.user.save()
  File
"/usr/lib/python3/dist-packages/django/contrib/auth/base_user.py", line
66, in save
super().save(*args, **kwargs)
  File "/usr/lib/python3/dist-packages/django/db/models/base.py", line
743, in save
self.save_base(using=using, force_insert=force_insert,
  File "/usr/lib/python3/dist-packages/django/db/models/base.py", line
791, in save_base
post_save.send(
  File "/usr/lib/python3/dist-packages/django/dispatch/dispatcher.py",
line 173, in send
return [
  File "/usr/lib/python3/dist-packages/django/dispatch/dispatcher.py",
line 174, in 
(receiver, receiver(signal=self, sender=sender, **named))
  File "/usr/lib/python3/dist-packages/django_mailman3/signals.py", line
101, in create_profile
address.display_name = new_display_name
AttributeError: 'str' object has no 

Processed: django-mailman3 breaks hyperkitty autopkgtest: 'str' object has no attribute 'display_name'

[Debian Bug Tracking System]

Processing control commands:

> found -1 django-mailman3/1.3.7-1
Bug #995653 [src:django-mailman3, src:hyperkitty] django-mailman3 breaks 
hyperkitty autopkgtest: 'str' object has no attribute 'display_name'
Marked as found in versions django-mailman3/1.3.7-1.
> found -1 hyperkitty/1.3.4-4
Bug #995653 [src:django-mailman3, src:hyperkitty] django-mailman3 breaks 
hyperkitty autopkgtest: 'str' object has no attribute 'display_name'
Marked as found in versions hyperkitty/1.3.4-4.

-- 
995653: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995653
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#994266: pyjwt breaks azure-cli autopkgtest: Could not deserialize key data. The data may be in an incorrect format or it may be encrypted with an unsupported algorithm.

[Diego M. Rodriguez]

On Tue, 14 Sep 2021 22:30:24 +0200 Paul Gevers  wrote:
> Currently this regression is blocking the migration of pyjwt to testing
> [1]. Due to the nature of this issue, I filed this bug report against
> both packages. Can you please investigate the situation and reassign the
> bug to the right package?

As part of the "investigate" part - this might be related to a hotfix
introduced in azure-cli 2.26.1 [1], which includes a change on how the
"jwt.decode()" call related to the "verify" parameter [2]. pyjwt seems
to have deprecated it in its 2.0 release [3] (and a number of similar in
its upstream repo also point to that parameter).

[1]
https://github.com/MicrosoftDocs/azure-docs-cli/blob/master/docs-ref-conceptual/release-notes-azure-cli.md#storage-2
[2] https://github.com/Azure/azure-cli/pull/18811
[3]
https://github.com/jpadilla/pyjwt/blob/master/CHANGELOG.rst#dropped-deprecated-verify_expiration-param-in-jwtdecode
-- 
Diego M. Rodriguez

Bug#995649: therion: autopkgtest regression on at least arm64 and i386

[Paul Gevers]

Source: therion
Version: 6.0.2ds1-4
X-Debbugs-CC: debian...@lists.debian.org
Severity: serious
User: debian...@lists.debian.org
Usertags: regression
Control: affects -1 src:texlive-base src:texlive-lang

Dear maintainer(s),

With a recent upload of therion the autopkgtest of therion fails in
testing on at least arm64 and i386 when that autopkgtest is run with the
binary packages of therion from unstable. It passes when run with only
packages from testing. In tabular form:

   passfail
therionfrom testing6.0.2ds1-4
versioned deps [0] from testingfrom unstable
all others from testingfrom testing

I copied some of the output at the bottom of this report.

Currently this regression is blocking the migration to testing [1]. Can
you please investigate the situation and fix it?

More information about this bug and the reason for filing it can be found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation

Paul

[0] You can see what packages were added from the second line of the log
file quoted below. The migration software adds source package from
unstable to the list if they are needed to install packages from
therion/6.0.2ds1-4. I.e. due to versioned dependencies or breaks/conflicts.
[1] https://qa.debian.org/excuses.php?package=therion

https://ci.debian.net/data/autopkgtest/testing/arm64/t/therion/15744313/log.gz

writing samples/survex/cave1.pdf ...
This is MetaPost, version 2.01 (TeX Live 2022/dev/Debian) (kpathsea
version 6.3.4/dev)
(/usr/share/texlive/texmf-dist/metapost/base/mpost.mp
(/usr/share/texlive/texmf-dist/metapost/base/plain.mp
Preloading the plain mem file, version 1.005) ) (./data.mp [1] [2] [3] [4]
[5] [6] [7] [8] [9] [10] [11] [12] [13] [14]
[1] [2] [3] [4] [5] [6] [7] [8] [9] [10] [11] [12] [13] [14] [15] [16] [17]
(./mptextmp.mp) [18] (./mptextmp.mp) (./mptextmp.mp) (./mptextmp.mp)
(./mptextmp.mp) (./mptextmp.mp) (./mptextmp.mp) [19] )
33 output files written: data-patt.1 .. data.19
Transcript written on data.log.
converting scraps ... done
making map ... done
This is pdfTeX, Version 3.141592653-2.6-1.40.22 (TeX Live
2022/dev/Debian) (preloaded format=pdftex)
 restricted \write18 enabled.
entering extended mode
(./data.tex (./th_enc.tex) (./th_texts.tex) (./th_resources.tex
(/usr/share/texlive/texmf-dist/tex/generic/pdftex/glyphtounicode.tex))
(./th_fontdef.tex{/var/lib/texmf/fonts/map/pdftex/updmap/pdftex.map}<><><><>)
(./th_formdef.tex) (./th_pagedef.tex) (./th_pages.tex) [1]
)
Output written on data.pdf (1 page, 34360 bytes).
Transcript written on data.log.
done
checking CRC32 of all output files ...
samples/survex/cave1.pdf ... CRC32 error: was e974864e, expected a344ba1f
done.
therion: error -- CRC32 checks not passed.




OpenPGP_signature
Description: OpenPGP digital signature

Processed: therion: autopkgtest regression on at least arm64 and i386

[Debian Bug Tracking System]

Processing control commands:

> affects -1 src:texlive-base src:texlive-lang
Bug #995649 [src:therion] therion: autopkgtest regression on at least arm64 and 
i386
Added indication that 995649 affects src:texlive-base and src:texlive-lang

-- 
995649: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995649
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: reassign 995644 to lebiniou, found 995644 in 3.61.2-1

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> reassign 995644 lebiniou
Bug #995644 [lbeibiou] lebiniou: Fails to upgrade: trying to overwrite 
'/usr/share/lebiniou/etc/schemes.json'
Warning: Unknown package 'lbeibiou'
Bug reassigned from package 'lbeibiou' to 'lebiniou'.
No longer marked as found in versions 3.61.2-1.
Ignoring request to alter fixed versions of bug #995644 to the same values 
previously set
> found 995644 3.61.2-1
Bug #995644 [lebiniou] lebiniou: Fails to upgrade: trying to overwrite 
'/usr/share/lebiniou/etc/schemes.json'
Marked as found in versions lebiniou/3.61.2-1.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
995644: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995644
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#987938: librm: diff for NMU version 2.2.2+really2.1.4-0.1

[Adrian Bunk]

Control: tags 987938 + patch
Control: tags 987938 + pending

Dear maintainer,

I've prepared an NMU for librm (versioned as 2.2.2+really2.1.4-0.1) and 
uploaded it to DELAYED/2. Please feel free to tell me if I should cancel it.

Note that the attached debdiff is against the version 2.1.4-1 in 
bullseye/bookworm, not the version in unstable.

A proper fix can be done afterwards, and upgrading to the already 
released upstream version 2.2.3 would then also get rid of the +really
in the version.

cu
Adrian
diff -Nru librm-2.1.4/debian/changelog librm-2.2.2+really2.1.4/debian/changelog
--- librm-2.1.4/debian/changelog2021-01-25 11:39:25.0 +0200
+++ librm-2.2.2+really2.1.4/debian/changelog2021-10-03 18:30:23.0 
+0300
@@ -1,3 +1,17 @@
+librm (2.2.2+really2.1.4-0.1) unstable; urgency=high
+
+  * Non-maintainer upload.
+  * Revert back to 2.1.4 to avoid ABI breakage. (Closes: #987938)
+
+ -- Adrian Bunk   Sun, 03 Oct 2021 18:30:23 +0300
+
+librm (2.2.2-1) unstable; urgency=medium
+
+  * Update/fix debian/watch
+  * New upstream version 2.2.2
+
+ -- Hilko Bengen   Sat, 27 Mar 2021 12:44:31 +0100
+
 librm (2.1.4-1) unstable; urgency=medium
 
   * New upstream version 2.1.4
diff -Nru librm-2.1.4/debian/watch librm-2.2.2+really2.1.4/debian/watch
--- librm-2.1.4/debian/watch2021-01-25 10:30:48.0 +0200
+++ librm-2.2.2+really2.1.4/debian/watch2021-10-03 18:30:22.0 
+0300
@@ -1,4 +1,4 @@
 version=4
 
-https://gitlab.com/tabos/librm/-/tags \
-.*/archive/v(?:\d.*)/librm-v(\d.*).tar.bz2
+https://gitlab.com/tabos/librm/-/tags?sort=updated_desc \
+.*/archive/(?:\d.\S+)/librm-(\d\S+)\.tar\.bz2

Processed: librm: diff for NMU version 2.2.2+really2.1.4-0.1

[Debian Bug Tracking System]

Processing control commands:

> tags 987938 + patch
Bug #987938 [librm0] librm0: ABI breakage
Added tag(s) patch.
> tags 987938 + pending
Bug #987938 [librm0] librm0: ABI breakage
Added tag(s) pending.

-- 
987938: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=987938
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#992908: marked as done (awesome: autopkgtest regression between 20 and 23 August 2021: Could not resolve keysym)

[Debian Bug Tracking System]

Your message dated Sun, 3 Oct 2021 17:13:48 +0200
with message-id 
and subject line Re: awesome: autopkgtest regression between 20 and 23 August 
2021: Could not resolve keysym
has caused the Debian Bug report #992908,
regarding awesome: autopkgtest regression between 20 and 23 August 2021: Could 
not resolve keysym
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.)


-- 
992908: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=992908
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: awesome
Version: 4.3-5
Severity: serious
User: debian...@lists.debian.org
Usertags: regression
X-Debbugs-CC: debian...@lists.debian.org

Dear maintainer,

Your package has an autopkgtest, great! However, since this week
(somewhere between 20 August and 23 August 2021) it started to fail [1].
Can you look at it and fix the situation?

Paul

[1] https://ci.debian.net/packages/a/awesome/testing/amd64/

autopkgtest [13:23:59]: test integration.sh: [---
awesome_log: /tmp/tmp.Tu7TMRXwgL/_awesome_test.log
The XKEYBOARD keymap compiler (xkbcomp) reports:
> Internal error:   Could not resolve keysym XF86BrightnessAuto
> Internal error:   Could not resolve keysym XF86DisplayOff
> Internal error:   Could not resolve keysym XF86Info
> Internal error:   Could not resolve keysym XF86AspectRatio
> Internal error:   Could not resolve keysym XF86DVD
> Internal error:   Could not resolve keysym XF86Audio
> Internal error:   Could not resolve keysym XF86ChannelUp
> Internal error:   Could not resolve keysym XF86ChannelDown
> Internal error:   Could not resolve keysym XF86Break
> Internal error:   Could not resolve keysym XF86VideoPhone
> Internal error:   Could not resolve keysym XF86ZoomReset
> Internal error:   Could not resolve keysym XF86Editor
> Internal error:   Could not resolve keysym XF86GraphicsEditor
> Internal error:   Could not resolve keysym XF86Presentation
> Internal error:   Could not resolve keysym XF86Database
> Internal error:   Could not resolve keysym XF86Voicemail
> Internal error:   Could not resolve keysym XF86Addressbook
> Internal error:   Could not resolve keysym XF86DisplayToggle
> Internal error:   Could not resolve keysym XF86SpellCheck
> Internal error:   Could not resolve keysym XF86ContextMenu
> Internal error:   Could not resolve keysym XF86MediaRepeat
> Internal error:   Could not resolve keysym XF8610ChannelsUp
> Internal error:   Could not resolve keysym XF8610ChannelsDown
> Internal error:   Could not resolve keysym XF86Images
> Internal error:   Could not resolve keysym XF86NotificationCenter
> Internal error:   Could not resolve keysym XF86PickupPhone
> Internal error:   Could not resolve keysym XF86HangupPhone
> Internal error:   Could not resolve keysym XF86Fn
> Internal error:   Could not resolve keysym XF86Fn_Esc
> Internal error:   Could not resolve keysym XF86FnRightShift
> Internal error:   Could not resolve keysym XF86Numeric0
> Internal error:   Could not resolve keysym XF86Numeric1
> Internal error:   Could not resolve keysym XF86Numeric2
> Internal error:   Could not resolve keysym XF86Numeric3
> Internal error:   Could not resolve keysym XF86Numeric4
> Internal error:   Could not resolve keysym XF86Numeric5
> Internal error:   Could not resolve keysym XF86Numeric6
> Internal error:   Could not resolve keysym XF86Numeric7
> Internal error:   Could not resolve keysym XF86Numeric8
> Internal error:   Could not resolve keysym XF86Numeric9
> Internal error:   Could not resolve keysym XF86NumericStar
> Internal error:   Could not resolve keysym XF86NumericPound
> Internal error:   Could not resolve keysym XF86NumericA
> Internal error:   Could not resolve keysym XF86NumericB
> Internal error:   Could not resolve keysym XF86NumericC
> Internal error:   Could not resolve keysym XF86NumericD
> Internal error:   Could not resolve keysym XF86CameraFocus
> Internal error:   Could not resolve keysym XF86WPSButton
> Internal error:   Could not resolve keysym XF86CameraZoomIn
> Internal error:   Could not resolve keysym XF86CameraZoomOut
> Internal error:   Could not resolve keysym XF86CameraUp
> Internal error:   Could not resolve keysym XF86CameraDown
> Internal error:   Could not resolve keysym XF86CameraLeft
> Internal error:   Could not resolve keysym XF86CameraRight
> Internal error:   Could not resolve keysym XF86AttendantOn
> Internal error:   Could not resolve keysym XF86AttendantOff
> Internal error:   Could not resolve keysym XF86AttendantToggle
> Internal error:   Could not resolve keysym XF86LightsToggle
> Internal error:   Could not resolve keysym 

Bug#995644: lebiniou: Fails to upgrade: trying to overwrite '/usr/share/lebiniou/etc/schemes.json'

[Kurt Roeckx]

Package: lbeibiou
Version: 3.61.2-1
Severity: serious

Hi,

During an upgrade, I get the following:
dpkg: considering deconfiguration of lebiniou-data, which would be broken by 
installation of lebiniou ...
dpkg: yes, will deconfigure lebiniou-data (broken by lebiniou)
Preparing to unpack .../110-lebiniou_3.61.2-1+b1_amd64.deb ...
De-configuring lebiniou-data (3.54.1-1) ...
Unpacking lebiniou (3.61.2-1+b1) over (3.54.1-1) ...
dpkg: error processing archive 
/tmp/apt-dpkg-install-dU3HYR/110-lebiniou_3.61.2-1+b1_amd64.deb (--unpack):
 trying to overwrite '/usr/share/lebiniou/etc/schemes.json', which is also in 
package lebiniou-data 3.54.1-1
dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
dpkg: considering deconfiguration of lebiniou, which would be broken by 
installation of lebiniou-data ...
dpkg: yes, will deconfigure lebiniou (broken by lebiniou-data)
Preparing to unpack .../111-lebiniou-data_3.61.1-1_all.deb ...
De-configuring lebiniou (3.54.1-1) ...
Unpacking lebiniou-data (3.61.1-1) over (3.54.1-1) ...


This looks like it's missing a Replaces. A Breaks is not enough.

Trying again, it works because lebiniou-data got updated.

I'm not sure why the file moved from lebiniou-data to lebiniou.


Kurt

Bug#995608: linux-image-5.14.0-1-amd64: Boot immediately hangs.

[Vincent Blut]

Hi,

Le 2021-10-03 11:40, Nathanael Schweers a écrit :
> 
> Salvatore Bonaccorso  writes:
> 
> > Control: tags -1 + moreinfo
> >
> > Hi Nathanael,
> >
> > On Sun, Oct 03, 2021 at 10:02:35AM +0200, Nathanael Schweers wrote:
> >> Package: src:linux
> >> Version: 5.14.6-3
> >> Severity: grave
> >> Justification: renders package unusable
> >>
> >> Dear Maintainer,
> >>
> >> using this kernel, my machine no longer boots.  Instead of showing a 
> >> prompt to
> >> enter the LUKS passphrase (as is done in version 
> >> linux-image-5.10.0-7-amd64) a
> >> non-blinking cursor is shown.  Nothing happens afterwards.
> >>
> >> Version linux-image-5.10.0-7-amd64 still works, but newer versions
> >> (linux-image-5.10.0-8-amd64 and the version this report is for) produce the
> >> behaviour mentioned above.
> >>
> >> I’m afraid that I don’t have a decent idea on what extra information to 
> >> provide.
> >
> > Could you please confirm that booting with the 'mem_encrypt=off'
> > kernel command line heps?
> 
> With this option the kernel does indeed boot.  Thanks for the tip!

Salvatore, given the increase in bug reports that this feature generates,
I think it would be sensible to unset AMD_MEM_ENCRYPT_ACTIVE_BY_DEFAULT until
those incompatibilities are fixed, like I proposed in [1]. One would have to
use the "mem_encrypt=on" command line option to enable the AMD Secure Memory
Encryption. If it sounds reasonable to you and the rest of the kernel team,
I can send a merge request.

Cheers,
Vincent


signature.asc
Description: PGP signature

Bug#995594: marked as done (libhdf5[-openmpi]-dev: missing Depends: libcurl-dev)

[Debian Bug Tracking System]

Your message dated Sun, 03 Oct 2021 13:49:23 +
with message-id 
and subject line Bug#995594: fixed in hdf5 1.10.7+repack-3
has caused the Debian Bug report #995594,
regarding libhdf5[-openmpi]-dev: missing Depends: libcurl-dev
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.)


-- 
995594: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995594
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libhdf5-openmpi-dev
Version: 1.10.7+repack-2
Severity: serious
Justification: FTBFS
Control: affects -1 src:fenics-dolfinx

The hdf5 compiler wrappers declare -lcurl as a linked library
e.g. 
$ h5cc -showconfig | grep curl
Extra libraries: -lcrypto -lcurl -lpthread -lsz -lz -ldl -lm 
$ h5pcc -showconfig | grep curl
Extra libraries: -lcrypto -lcurl -lsz -lz -ldl -lm 


But libcurl-dev is not declared as a Dependency for libhdf5-openmpi-dev.
This means that compiling with h5pcc (or h5cc) fails unless [a]
libcurl-dev is installed.

This affects client packages using cmake that check HDF5
configuration using find_package(hdf5),
e.g. a trivial sample CMakeLists.txt

--
project(TEST_hdf5)

set(HDF5_PREFER_PARALLEL TRUE)
find_package(HDF5 REQUIRED COMPONENTS C)
--

gives the result,

  -- HDF5 C compiler wrapper is unable to compile a minimal HDF5 program.
  CMake Error at 
/usr/share/cmake-3.21/Modules/FindPackageHandleStandardArgs.cmake:230 (message):
Could NOT find HDF5 (missing: HDF5_LIBRARIES HDF5_INCLUDE_DIRS C) (found
version "")


A current example is the broken build of fenics-dolfinx on i386,
https://buildd.debian.org/status/fetch.php?pkg=fenics-dolfinx=i386=1%3A0.3.0-3=1633198410=0


cmake is desparately opaque, but with enough sweat and tears
(ultimately, by compiling the cmake hdf5 test file manually with
h5pcc) one can eventually discover that the problem is the -lcurl flag
in h5pcc,

  CMakeFiles/hdf5$ h5pcc cmake_hdf5_test.c
  /usr/bin/ld: cannot find -lcurl



I'm filing this bug against libhdf5-openmpi-dev, providing h5pcc, 
since I want to use hdf5-mpi, but the problem also affects libhdf5-dev
(providing h5cc).

Since h5pcc and h5cc invoke -lcurl, libhdf5-openmpi-dev, libhdf5-dev (and
probably libhdf5-mpich-dev also) should declare Depends: libcurl-dev

Finally, since libcurl-dev is virtual, the actual declaration should be
(following hdf5's Build-Depends)

  Depends: libcurl4-openssl-dev

or possibly Depends: libcurl4-openssl-dev | libcurl-dev
(the libcurl variants seem to be interchangeable)


Why h5cc needs -lcurl is a separate question! What is it trying to
download?


Drew


-- System Information:
Debian Release: bookworm/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.14.0-1-amd64 (SMP w/8 CPU threads)
Kernel taint flags: TAINT_OOT_MODULE
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_AU:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages libhdf5-openmpi-dev depends on:
ii  libaec-dev 1.0.6-1
ii  libhdf5-openmpi-103-1  1.10.7+repack-2
ii  libhdf5-openmpi-cpp-103-1  1.10.7+repack-2
ii  libhdf5-openmpi-fortran-1021.10.7+repack-2
ii  libhdf5-openmpi-hl-100 1.10.7+repack-2
ii  libhdf5-openmpi-hl-cpp-100 1.10.7+repack-2
ii  libhdf5-openmpi-hl-fortran-100 1.10.7+repack-2
ii  libjpeg-dev1:2.0.6-4
ii  libjpeg62-turbo-dev [libjpeg-dev]  1:2.0.6-4
ii  libopenmpi-dev 4.1.2~rc1-4
ii  zlib1g-dev 1:1.2.11.dfsg-2

libhdf5-openmpi-dev recommends no packages.

Versions of packages libhdf5-openmpi-dev suggests:
pn  libhdf5-doc  

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: hdf5
Source-Version: 1.10.7+repack-3
Done: Gilles Filippini 

We believe that the bug you reported is fixed in the latest version of
hdf5, 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 995...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Gilles Filippini  (supplier of updated hdf5 package)

(This message was generated automatically at their request; if you
believe that there is a problem with it 

Bug#995608: linux-image-5.14.0-1-amd64: Boot immediately hangs.

[Nathanael Schweers]

Salvatore Bonaccorso  writes:

> Control: tags -1 + moreinfo
>
> Hi Nathanael,
>
> On Sun, Oct 03, 2021 at 10:02:35AM +0200, Nathanael Schweers wrote:
>> Package: src:linux
>> Version: 5.14.6-3
>> Severity: grave
>> Justification: renders package unusable
>>
>> Dear Maintainer,
>>
>> using this kernel, my machine no longer boots.  Instead of showing a prompt 
>> to
>> enter the LUKS passphrase (as is done in version linux-image-5.10.0-7-amd64) 
>> a
>> non-blinking cursor is shown.  Nothing happens afterwards.
>>
>> Version linux-image-5.10.0-7-amd64 still works, but newer versions
>> (linux-image-5.10.0-8-amd64 and the version this report is for) produce the
>> behaviour mentioned above.
>>
>> I’m afraid that I don’t have a decent idea on what extra information to 
>> provide.
>
> Could you please confirm that booting with the 'mem_encrypt=off'
> kernel command line heps?

With this option the kernel does indeed boot.  Thanks for the tip!

Regards,
Nathanael

Bug#995036: marked as done (ghc ftbfs in unstable (autoconf / automake issues))

[Debian Bug Tracking System]

Your message dated Sun, 03 Oct 2021 12:33:37 +
with message-id 
and subject line Bug#995036: fixed in ghc 8.8.4-3
has caused the Debian Bug report #995036,
regarding ghc ftbfs in unstable (autoconf / automake issues)
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.)


-- 
995036: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995036
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:ghc
Version: 8.8.4-2
Severity: serious
Tags: sid bookworm

ghc ftbfs in unstable (autoconf / automake issues):

[...]
dh binary-arch
   dh_update_autotools_config -a
   debian/rules override_dh_autoreconf
make[1]: Entering directory '/<>'
dh_autoreconf perl -- boot
configure.ac:18: warning: The macro `AC_FOREACH' is obsolete.
configure.ac:18: You should run autoupdate.
./lib/autoconf/general.m4:191: AC_FOREACH is expanded from...
aclocal.m4:43: FP_CHECK_CONSTS is expanded from...
configure.ac:18: the top level
configure.ac:18: warning: The macro `_AC_COMPUTE_INT' is obsolete.
configure.ac:18: You should run autoupdate.
./lib/autoconf/general.m4:3376: _AC_COMPUTE_INT is expanded from...
aclocal.m4:10: FP_COMPUTE_INT is expanded from...
lib/m4sugar/m4sh.m4:692: _AS_IF_ELSE is expanded from...
lib/m4sugar/m4sh.m4:699: AS_IF is expanded from...
./lib/autoconf/general.m4:2249: AC_CACHE_VAL is expanded from...
./lib/autoconf/general.m4:2270: AC_CACHE_CHECK is expanded from...
aclocal.m4:19: FP_CHECK_CONST is expanded from...
aclocal.m4:43: FP_CHECK_CONSTS is expanded from...
configure.ac:18: the top level
configure.ac:18: warning: The macro `AC_HELP_STRING' is obsolete.
configure.ac:18: You should run autoupdate.
./lib/autoconf/general.m4:204: AC_HELP_STRING is expanded from...
./lib/autoconf/general.m4:1553: AC_ARG_WITH is expanded from...
configure.ac:18: the top level
configure.ac:24: warning: The macro `AC_HELP_STRING' is obsolete.
configure.ac:24: You should run autoupdate.
./lib/autoconf/general.m4:204: AC_HELP_STRING is expanded from...
./lib/autoconf/general.m4:1553: AC_ARG_WITH is expanded from...
configure.ac:24: the top level
configure.ac:30: warning: The macro `AC_HELP_STRING' is obsolete.
configure.ac:30: You should run autoupdate.
./lib/autoconf/general.m4:204: AC_HELP_STRING is expanded from...
./lib/autoconf/general.m4:1553: AC_ARG_WITH is expanded from...
configure.ac:30: the top level
configure.ac:36: warning: The macro `AC_HELP_STRING' is obsolete.
configure.ac:36: You should run autoupdate.
./lib/autoconf/general.m4:204: AC_HELP_STRING is expanded from...
./lib/autoconf/general.m4:1553: AC_ARG_WITH is expanded from...
configure.ac:36: the top level
configure.ac:24: warning: The macro `AC_HEADER_TIME' is obsolete.
configure.ac:24: You should run autoupdate.
./lib/autoconf/headers.m4:743: AC_HEADER_TIME is expanded from...
aclocal.m4:6: FP_DECL_ALTZONE is expanded from...
configure.ac:24: the top level
configure.ac:111: warning: The macro `AC_FOREACH' is obsolete.
configure.ac:111: You should run autoupdate.
./lib/autoconf/general.m4:191: AC_FOREACH is expanded from...
aclocal.m4:43: FP_CHECK_CONSTS is expanded from...
configure.ac:111: the top level
configure.ac:111: warning: The macro `_AC_COMPUTE_INT' is obsolete.
configure.ac:111: You should run autoupdate.
./lib/autoconf/general.m4:3376: _AC_COMPUTE_INT is expanded from...
aclocal.m4:10: FP_COMPUTE_INT is expanded from...
lib/m4sugar/m4sh.m4:692: _AS_IF_ELSE is expanded from...
lib/m4sugar/m4sh.m4:699: AS_IF is expanded from...
./lib/autoconf/general.m4:2249: AC_CACHE_VAL is expanded from...
./lib/autoconf/general.m4:2270: AC_CACHE_CHECK is expanded from...
aclocal.m4:19: FP_CHECK_CONST is expanded from...
aclocal.m4:43: FP_CHECK_CONSTS is expanded from...
configure.ac:111: the top level
configure.ac:30: warning: The macro `AC_HEADER_STDC' is obsolete.
configure.ac:30: You should run autoupdate.
./lib/autoconf/headers.m4:704: AC_HEADER_STDC is expanded from...
configure.ac:30: the top level
configure.ac:103: warning: The macro `AC_HELP_STRING' is obsolete.
configure.ac:103: You should run autoupdate.
./lib/autoconf/general.m4:204: AC_HELP_STRING is expanded from...
./lib/autoconf/general.m4:1553: AC_ARG_WITH is expanded from...
configure.ac:103: the top level
configure.ac:109: warning: The macro `AC_HELP_STRING' is obsolete.
configure.ac:109: You should run autoupdate.
./lib/autoconf/general.m4:204: AC_HELP_STRING is expanded from...
./lib/autoconf/general.m4:1553: AC_ARG_WITH is expanded from...
configure.ac:109: the top level
configure.ac:119: warning: The macro `_AC_COMPUTE_INT' is obsolete.
configure.ac:119: You should run 

Bug#995429: marked as done (ghc ftbfs in unstable (after fixing the autoconf issue))

[Debian Bug Tracking System]

Your message dated Sun, 03 Oct 2021 12:33:37 +
with message-id 
and subject line Bug#995429: fixed in ghc 8.8.4-3
has caused the Debian Bug report #995429,
regarding ghc ftbfs in unstable (after fixing the autoconf issue)
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.)


-- 
995429: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995429
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:ghc
Version: 8.8.4-2
Severity: serious
Tags: sid bookworm

after fixing the autoconf 2.7x issue, the ghc build still fails with:

[...]
rts/RetainerSet.c: In function ‘printRetainerSetShort’:

rts/RetainerSet.c:241:21: error:
 warning: writing 1 byte into a region of size 0 [-Wstringop-overflow=]
  241 | tmp[max_length] = '\0';
  | ^~
|
241 | tmp[max_length] = '\0';
| ^

rts/RetainerSet.c:235:10: error:
 note: at offset [-9223372036854775808, 9223372036854775807] to an object
with size at most 4294967295 declared here
  235 | char tmp[max_length + 1];
  |  ^~~
|
235 | char tmp[max_length + 1];
|  ^



and also:

[...]
rts/posix/Signals.c:680:5: error:
 warning: ‘siginterrupt’ is deprecated: Use sigaction with SA_RESTART
instead [-Wdeprecated-declarations]
  680 | siginterrupt(SIGINT, 1);// isn't this the default? --SDM
  | ^~~~
|
680 | siginterrupt(SIGINT, 1);// isn't this the default? --SDM
| ^
In file included from rts/posix/Signals.h:12,
 from rts/RtsSignals.h:13,

 from rts/posix/Signals.c:13:0: error:

/usr/include/signal.h:311:12: error:
 note: declared here
  311 | extern int siginterrupt (int __sig, int __interrupt) __THROW
  |^~~~
|
311 | extern int siginterrupt (int __sig, int __interrupt) __THROW
|^


[...]
rts/sm/Evac.c:255:1: error:
 warning: inlining failed in call to ‘evacuate_large’: --param
max-inline-insns-single limit reached [-Winline]
  255 | evacuate_large(StgPtr p)
  | ^~
|
255 | evacuate_large(StgPtr p)
| ^

rts/sm/Evac.c:596:11: error:
 note: called from here
  596 |   evacuate_large((P_)q);
  |   ^
|
596 |   evacuate_large((P_)q);
|   ^
rts/sm/Evac.c: In function ‘evacuate_BLACKHOLE1’:

rts/sm/Evac.c:255:1: error:
 warning: inlining failed in call to ‘evacuate_large’: --param
max-inline-insns-single limit reached [-Winline]
  255 | evacuate_large(StgPtr p)
  | ^~
|
255 | evacuate_large(StgPtr p)
| ^

rts/sm/Evac.c:901:9: error:
 note: called from here
  901 | evacuate_large((P_)q);
  | ^
|
901 | evacuate_large((P_)q);
| ^
--- End Message ---
--- Begin Message ---
Source: ghc
Source-Version: 8.8.4-3
Done: Ilias Tsitsimpis 

We believe that the bug you reported is fixed in the latest version of
ghc, 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 995...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Ilias Tsitsimpis  (supplier of updated ghc 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, 03 Oct 2021 14:27:00 +0300
Source: ghc
Architecture: source
Version: 8.8.4-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Haskell Group 

Changed-By: Ilias Tsitsimpis 
Closes: 944493 995036 995429
Changes:
 ghc (8.8.4-3) unstable; urgency=medium
 .
   * Disable parallel install to fix races with missing directories
 (Closes: #944493)
   * Fix FTBFS with autoconf 2.71. Thanks to Matthias Klose for the patch
 (Closes: #995036)
   * Fix FTBFS with Sphinx 4.2.0 (Closes: #995429)
Checksums-Sha1:
 45f2a66c553922f4263fc21e9d8354911299e92e 2637 ghc_8.8.4-3.dsc
 c8d303fed5dd5597e1e7d34ab804a64f7f73bd12 53968 ghc_8.8.4-3.debian.tar.xz
 f82db4aa010bf6c6c8d22edd6bd6e51f1b4d00ca 10512 ghc_8.8.4-3_source.buildinfo
Checksums-Sha256:
 036e95336cac46709a57c8e391751883d16eafce713c279a02660328e19cfd5f 

Bug#994969: jackd2: segfaults after today's upgrade of other Debian testing packages

[Ryan Thoryk]

On 10/3/21 6:33 AM, Simon McVittie wrote:

On Sat, 02 Oct 2021 at 20:48:55 +1000, ‍小太 wrote:
Perhaps jack_firewire.so and/or glibmm should be linked with -Wl,-z,nodelete
to prevent it from being removed from the address space even after
dlclose()? That would ensure that its static strings remain in memory.


I think my code only showed a dlopen() with a single call, but my 
backtrace shows that it attempts to load the library twice (with caught 
exceptions), followed by a possible success the third time, then the 
glibmm init and segfault.  I don't know why the library load is failing. 
 Since I did a stack allocation instead, I'd think that memory would 
become invalid if the library unloaded before the glibmm init.


I'd mainly have to play with it in gdb more to see what's happening. 
nos...@kota.moe might've done more debugging than I did.


--
Ryan Thoryk
r...@thoryk.com
r...@tliquest.net

Bug#995608: linux-image-5.14.0-1-amd64: Boot immediately hangs.

[Nathanael Schweers]

Package: src:linux
Version: 5.14.6-3
Severity: grave
Justification: renders package unusable

Dear Maintainer,

using this kernel, my machine no longer boots.  Instead of showing a prompt to
enter the LUKS passphrase (as is done in version linux-image-5.10.0-7-amd64) a
non-blinking cursor is shown.  Nothing happens afterwards.

Version linux-image-5.10.0-7-amd64 still works, but newer versions
(linux-image-5.10.0-8-amd64 and the version this report is for) produce the
behaviour mentioned above.

I’m afraid that I don’t have a decent idea on what extra information to provide.



-- Package-specific info:
** Kernel log: boot messages should be attached

** Model information
sys_vendor: To Be Filled By O.E.M.
product_name: To Be Filled By O.E.M.
product_version: To Be Filled By O.E.M.
chassis_vendor: To Be Filled By O.E.M.
chassis_version: To Be Filled By O.E.M.
bios_vendor: American Megatrends Inc.
bios_version: P4.00
board_vendor: ASRock
board_name: B450 Steel Legend
board_version:

** Network interface configuration:
*** /etc/network/interfaces:

source /etc/network/interfaces.d/*

auto lo
iface lo inet loopback

allow-hotplug enp9s0
iface enp9s0 inet dhcp
iface enp9s0 inet6 auto

** PCI devices:
00:00.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse 
Root Complex [1022:1480]
Subsystem: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Root 
Complex [1022:1480]
Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: 
Kernel driver in use: pcieport

00:01.3 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse 
GPP Bridge [1022:1483] (prog-if 00 [Normal decode])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: 
Kernel driver in use: pcieport

00:02.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse 
PCIe Dummy Host Bridge [1022:1482]
Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: 
Kernel driver in use: pcieport

00:04.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse 
PCIe Dummy Host Bridge [1022:1482]
Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: 
Kernel driver in use: pcieport

00:08.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse 
PCIe Dummy Host Bridge [1022:1482]
Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- TAbort- Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: 
Kernel driver in use: pcieport

00:14.0 SMBus [0c05]: Advanced Micro Devices, Inc. [AMD] FCH SMBus Controller 
[1022:790b] (rev 61)
Subsystem: ASRock Incorporation FCH SMBus Controller [1849:]
Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap- 66MHz+ UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- 
SERR- TAbort- 
SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- 
Kernel driver in use: nvme
Kernel modules: nvme

02:00.0 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD] 400 Series 
Chipset USB 3.1 XHCI Controller [1022:43d5] (rev 01) (prog-if 30 [XHCI])
Subsystem: ASMedia Technology Inc. 400 Series Chipset USB 3.1 XHCI 
Controller [1b21:1142]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: xhci_hcd
Kernel modules: xhci_pci

02:00.1 SATA controller [0106]: Advanced Micro Devices, Inc. [AMD] 400 Series 
Chipset SATA Controller [1022:43c8] (rev 01) (prog-if 01 [AHCI 1.0])
Subsystem: ASMedia Technology 

Bug#994969: jackd2: segfaults after today's upgrade of other Debian testing packages

[Simon McVittie]

On Sat, 02 Oct 2021 at 20:48:55 +1000, ‍小太 wrote:
> What I can add is from reading the documentation of 
> g_quark_from_static_string()
> (https://docs.gtk.org/glib/func.quark_from_static_string.html)
> is these particular lines seem to be of importance:
> 
> > It can be used with statically allocated strings in the main program,
> > but not with statically allocated memory in dynamically loaded
> > modules, if you expect to ever unload the module again
> 
> However, jackd will load jack_firewire.so three times (which means
> loading and unloading its glibmm dependency three times)

Perhaps jack_firewire.so and/or glibmm should be linked with -Wl,-z,nodelete
to prevent it from being removed from the address space even after
dlclose()? That would ensure that its static strings remain in memory.

smcv

Bug#994969: jackd2: segfaults after today's upgrade of other Debian testing packages

[Ryan Thoryk]

On 10/3/21 4:59 AM, 小太 wrote:

On Sun, 3 Oct 2021 at 20:47, Ryan Thoryk  wrote:
"Bad permissions for mapped region at address" can also mean it tried
to read from unreadable memory. The memory was mapped at some
point in the past, so it doesn't say unallocated memory

Also consider the segfault comes from strcmp(). Why would strcmp()
ever need to write to memory? You can verify with a disassember the
segfault comes from a read


The strcmp stumped me too.  I assumed it was trying to copy from a null 
pointer, but valgrind shows that the address wasn't null.  I forgot 
about the strcmp detail when writing my comment, strcmp is read-only.




I suspect this "worked" to fix the issue only due to a memory layout
change, and luck would have it that after your rebuild it now tries to
read from readable memory (albeit still not the expected memory)



After looking over the glib docs, the function does a const on the 
string, so it shouldn't be able to do a write.


I don't know enough about handling C-strings (I've mostly done C++ 
strings), but the only difference is the location of stored memory, 
maybe it's getting an access error when trying to access the literal 
(since it's being done from an external library), as opposed to a stack 
allocation.  That's the only thing I can think of.  Valgrind doesn't 
show any warning or error using this method, so it appears to be fine. 
I'll bring this up on the glibmm upstream and see what they say.  I 
think the proper way to to define it is "static const char[]" instead of 
"char[]", but it might not matter that much.


--
Ryan Thoryk
r...@thoryk.com
r...@tliquest.net

Bug#995429: ghc ftbfs in unstable (after fixing the autoconf issue)

[Ilias Tsitsimpis]

Hi Matthias,

On Fri, Oct 01, 2021 at 09:05AM, Matthias Klose wrote:
> after fixing the autoconf 2.7x issue, the ghc build still fails with:
> 
> [...]
> rts/RetainerSet.c: In function ‘printRetainerSetShort’:
> 
> rts/RetainerSet.c:241:21: error:
>  warning: writing 1 byte into a region of size 0 [-Wstringop-overflow=]
>   241 | tmp[max_length] = '\0';
>   | ^~
> |
> 241 | tmp[max_length] = '\0';
> | ^
> 
> rts/RetainerSet.c:235:10: error:
>  note: at offset [-9223372036854775808, 9223372036854775807] to an object
> with size at most 4294967295 declared here
>   235 | char tmp[max_length + 1];
>   |  ^~~
> |
> 235 | char tmp[max_length + 1];
> |  ^

I believe the above messages are not the reason why the build failed,
since these are warnings. When I tried building (after fixing the
autoconf 2.7x issue) it failed with:

  Running Sphinx v4.2.0

  Configuration error:
  There is a syntax error in your configuration file: (unicode error) 
'unicodeescape' codec can't decode bytes in position 1-2: truncated \u 
escape (conf.py, line 87)

GHC fails to build with the newer version of Sphinx available in
unstable. After fixing the Sphinx issue, I succeeded on building GHC on
unstable again. I will upload a new version now fixing these issues.

Thanks,

-- 
Ilias

Bug#995625: httping FTBFS: error: format not a string literal and no format arguments [-Werror=format-security]

[Helmut Grohne]

Source: httping
Version: 2.5-5.1
Severity: serious
Tags: ftbfs

httping fails to build from source in unstable on amd64. A non-parallel
build ends as follows:

| x86_64-linux-gnu-gcc -g -O2 -ffile-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wall -W -Wextra 
-pedantic -D_FORTIFY_SOURCE=2  -DVERSION=\"2.5\" 
-DLOCALEDIR=\"/usr/share/locale\" -DTCP_TFO -DNC -DFW -D_DEBUG -ggdb 
-Wdate-time -D_FORTIFY_SOURCE=2  -c -o nc.o nc.c
| nc.c: In function ‘myprint’:
| nc.c:238:3: error: format not a string literal and no format arguments 
[-Werror=format-security]
|   238 |   wprintw(w, what);
|   |   ^~~
| nc.c: In function ‘draw_graph’:
| nc.c:611:24: warning: unused parameter ‘val’ [-Wunused-parameter]
|   611 | void draw_graph(double val)
|   | ~~~^~~
| nc.c: In function ‘status_line’:
| nc.c:389:2: warning: ignoring return value of ‘vasprintf’ declared with 
attribute ‘warn_unused_result’ [-Wunused-result]
|   389 |  vasprintf(, fmt, ap);
|   |  ^
| cc1: some warnings being treated as errors
| make[1]: *** [: nc.o] Error 1
| make[1]: Leaving directory '/<>'
| dh_auto_build: error: make -j1 returned exit code 2
| make: *** [debian/rules:10: build] Error 25
| dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2

This is likely caused by ncurses adding format string annotations.

Helmut

Bug#995624: pktstat FTBFS: error: format not a string literal and no format arguments [-Werror=format-security]

[Helmut Grohne]

Source: pktstat
Version: 1.8.5-7
Severity: serious
Tags: ftbfs

pktstat fails to build from source in unstable on amd64. A non-parallel
build ends as follows:

| gcc -DHAVE_CONFIG_H -I.  -DPATH_PKTSTATRC=\"/etc/pktstatrc\" -Wdate-time 
-D_FORTIFY_SOURCE=2  -g -O2 -ffile-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wall -pedantic 
-D_BSD_SOURCE -c -o display.o display.c
| In file included from 
/usr/include/x86_64-linux-gnu/bits/libc-header-start.h:33,
|  from /usr/include/stdio.h:27,
|  from display.c:17:
| /usr/include/features.h:187:3: warning: #warning "_BSD_SOURCE and 
_SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" [-Wcpp]
|   187 | # warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use 
_DEFAULT_SOURCE"
|   |   ^~~
| display.c: In function ‘display_update’:
| display.c:499:33: warning: field width specifier ‘*’ expects argument of type 
‘int’, but argument 2 has type ‘long unsigned int’ [-Wformat=]
|   499 |  attron(A_UNDERLINE); printw("%-*s",
|   |   ~~^~
|   | |
|   | int
| display.c:552:13: warning: field precision specifier ‘.*’ expects argument of 
type ‘int’, but argument 2 has type ‘long unsigned int’ [-Wformat=]
|   552 |   printw("%.*s\n", MIN(maxx - LLEN, sizeof flows[i].tag - 1),
|   |   ~~^~
|   | |
|   | int
| display.c:566:15: warning: field precision specifier ‘.*’ expects argument of 
type ‘int’, but argument 2 has type ‘long unsigned int’ [-Wformat=]
|   566 |printw(" %.*s\n", MIN(maxx - LLEN - 2,
|   | ~~^~
|   |   |
|   |   int
| display.c:285:21: warning: variable ‘x’ set but not used 
[-Wunused-but-set-variable]
|   285 |  int maxx, maxy, y, x;
|   | ^
| display.c: In function ‘printhelp’:
| display.c:672:3: error: format not a string literal and no format arguments 
[-Werror=format-security]
|   672 |   printw((char *)h->name + 1);
|   |   ^~
| cc1: some warnings being treated as errors
| make[2]: *** [Makefile:483: display.o] Error 1
| make[2]: Leaving directory '/<>'
| make[1]: *** [Makefile:339: all] Error 2
| make[1]: Leaving directory '/<>'
| dh_auto_build: error: make -j1 returned exit code 2
| make: *** [debian/rules:11: build] Error 25
| dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2

This is likely due to ncurses including format string annotations.

Helmut

Bug#995623: refind FTBFS: error: conflicting types for ‘EFI_DEVICE_PATH_UTILITIES_PROTOCOL’

[Helmut Grohne]

Source: refind
Version: 0.12.0-1
Severity: serious
Tags: ftbfs

refind fails to build from source in unstable on amd64 and it also fails
to cross build for arm64 for the same reason. A build ends as follows:

| make[3]: Entering directory '/<>/EfiLib'
| /usr/bin/gcc -Os -fno-strict-aliasing -fno-tree-loop-distribute-patterns 
-fno-stack-protector -fshort-wchar -Wall -DEFIX64 -DEFI_FUNCTION_WRAPPER -m64 
-mno-red-zone  -fpic -I/usr/include/efi -I/usr/include/efi/x86_64 
-I/usr/include/efi/protocol -I../include -I../refind -I../libeg -I../mok -I. 
-I./../include \
|   -D__MAKEWITH_GNUEFI -c gnuefi-helper.c -o gnuefi-helper.o
| In file included from gnuefi-helper.c:19:
| DevicePathUtilities.h:229:3: error: conflicting types for 
‘EFI_DEVICE_PATH_UTILITIES_PROTOCOL’
|   229 | } EFI_DEVICE_PATH_UTILITIES_PROTOCOL;
|   |   ^~
| In file included from /usr/include/efi/efi.h:61,
|  from gnuefi-helper.h:24,
|  from gnuefi-helper.c:18:
| /usr/include/efi/efidevp.h:648:3: note: previous declaration of 
‘EFI_DEVICE_PATH_UTILITIES_PROTOCOL’ was here
|   648 | } EFI_DEVICE_PATH_UTILITIES_PROTOCOL;
|   |   ^~
| make[3]: *** [../Make.common:164: gnuefi-helper.o] Error 1
| make[3]: Leaving directory '/<>/EfiLib'
| make[2]: *** [Makefile:86: gnuefi] Error 2
| make[2]: Leaving directory '/<>'
| dh_auto_build: error: make -j1 gnuefi ARCH=x86_64 returned exit code 2
| make[1]: *** [debian/rules:33: override_dh_auto_build] Error 25
| make[1]: Leaving directory '/<>'
| make: *** [debian/rules:26: build] Error 2
| dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2

Also seen by crossqa:
http://crossqa.debian.net

Reproduced natively on arm64 by reproducible builds:
https://tests.reproducible-builds.org/debian/rbuild/unstable/arm64/refind_0.12.0-1.rbuild.log.gz

Helmut

Bug#995621: openni-sensor-pointclouds does not trap errors during build

[Helmut Grohne]

Source: openni-sensor-pointclouds
Version: 5.1.0.41.9-3
Severity: serious
Justification: policy 4.6

When a compilation step in openni-sensor-pointclouds fails, the
RedistMaker script that wraps the build, does not propagate the failure.
You can find a relevant invocation at:
https://sources.debian.org/src/openni-sensor-pointclouds/5.1.0.41.9-3/Platform/Linux/CreateRedist/RedistMaker/#L78

A very simple fix would be adding "set -e" to the top of the script.
Not propagating failure poses the risk of producing broken packages and
violates Debian policy section 4.6. This kind of bug therefore is
release-critical.

Helmut

Bug#995594: libhdf5[-openmpi]-dev: missing Depends: libcurl-dev

[Drew Parsons]

On 2021-10-03 12:15, Gilles Filippini wrote:

Drew Parsons a écrit le 02/10/2021 à 22:17 :


Why h5cc needs -lcurl is a separate question! What is it trying to
download?


I guess this is a consequence of enabling access to HDF5 on S3. See 
#972537.


Ah yes, that makes sense.  S3 support will need network access of 
course.


Drew

Bug#995594: libhdf5[-openmpi]-dev: missing Depends: libcurl-dev

[Gilles Filippini]

Hi,

Drew Parsons a écrit le 02/10/2021 à 22:17 :

Package: libhdf5-openmpi-dev
Version: 1.10.7+repack-2
Severity: serious
Justification: FTBFS
Control: affects -1 src:fenics-dolfinx

The hdf5 compiler wrappers declare -lcurl as a linked library
e.g.
$ h5cc -showconfig | grep curl
 Extra libraries: -lcrypto -lcurl -lpthread -lsz -lz -ldl -lm
$ h5pcc -showconfig | grep curl
 Extra libraries: -lcrypto -lcurl -lsz -lz -ldl -lm


But libcurl-dev is not declared as a Dependency for libhdf5-openmpi-dev.
This means that compiling with h5pcc (or h5cc) fails unless [a]
libcurl-dev is installed.

This affects client packages using cmake that check HDF5
configuration using find_package(hdf5),
e.g. a trivial sample CMakeLists.txt

--
project(TEST_hdf5)

set(HDF5_PREFER_PARALLEL TRUE)
find_package(HDF5 REQUIRED COMPONENTS C)
--

gives the result,

   -- HDF5 C compiler wrapper is unable to compile a minimal HDF5 program.
   CMake Error at 
/usr/share/cmake-3.21/Modules/FindPackageHandleStandardArgs.cmake:230 (message):
 Could NOT find HDF5 (missing: HDF5_LIBRARIES HDF5_INCLUDE_DIRS C) (found
 version "")


A current example is the broken build of fenics-dolfinx on i386,
https://buildd.debian.org/status/fetch.php?pkg=fenics-dolfinx=i386=1%3A0.3.0-3=1633198410=0


cmake is desparately opaque, but with enough sweat and tears
(ultimately, by compiling the cmake hdf5 test file manually with
h5pcc) one can eventually discover that the problem is the -lcurl flag
in h5pcc,

   CMakeFiles/hdf5$ h5pcc cmake_hdf5_test.c
   /usr/bin/ld: cannot find -lcurl



I'm filing this bug against libhdf5-openmpi-dev, providing h5pcc,
since I want to use hdf5-mpi, but the problem also affects libhdf5-dev
(providing h5cc).

Since h5pcc and h5cc invoke -lcurl, libhdf5-openmpi-dev, libhdf5-dev (and
probably libhdf5-mpich-dev also) should declare Depends: libcurl-dev

Finally, since libcurl-dev is virtual, the actual declaration should be
(following hdf5's Build-Depends)

   Depends: libcurl4-openssl-dev

or possibly Depends: libcurl4-openssl-dev | libcurl-dev
(the libcurl variants seem to be interchangeable)


Why h5cc needs -lcurl is a separate question! What is it trying to
download?


I guess this is a consequence of enabling access to HDF5 on S3. See #972537.

Best,

_g.

Bug#995115: /usr/bin/ruby: symbol lookup error: /lib/x86_64-linux-gnu/libruby-2.7.so.2.7: undefined symbol: rb_st_numhash

[xiscu]

Package: libruby2.7
Followup-For: Bug #995115

Thank you David, Francesco,
uncommenting DPkg::Pre-Install-Pkgs {"/usr/bin/apt-listbugs apt";};
allowed me to upgrade the system without the apt-listbugs blocker
issue. Just for the records, in that process I hat to use:
apt --fix-broken install (may be unrelated):

You might want to run 'apt --fix-broken install' to correct these.
The following packages have unmet dependencies:
 chromium : Depends: chromium-common (= 90.0.4430.212-1) but 93.0.4577.82-1 is 
installed
 chromium-common : Breaks: chromium (< 93.0.4577.82-1) but 90.0.4430.212-1 is 
installed
 chromium-sandbox : Breaks: chromium (< 93.0.4577.82-1) but 90.0.4430.212-1 is 
installed
 ffmpeg : Depends: libavfilter7 (= 7:4.4-6+b2)
 libavdevice58 : Depends: libavfilter7 (= 7:4.4-6+b2)
 libavfilter7 : Depends: libavcodec58 (= 7:4.4-5)
Depends: libavformat58 (= 7:4.4-5)
Depends: libavutil56 (= 7:4.4-5) but 7:4.4-6+b2 is installed
Setting up libx32ubsan1 (11.2.0-7) ...
Setting up dconf-gsettings-backend:amd64 (0.40.0-2) ...
Setting up libqt5gui5:amd64 (5.15.2+dfsg-12) ...
Setting up libatspi2.0-0:amd64 (2.42.0-1) ...
Setting up lib32ubsan1 (11.2.0-7) ...
Setting up libavutil56:amd64 (7:4.4-6+b2) ...


after that I was able to apt dist-upgrade again:
...
Preparing to unpack .../191-ruby-rubygems_3.2.27-1_all.deb ...
Unpacking ruby-rubygems (3.2.27-1) over (3.2.5-2) ...
Preparing to unpack .../192-ruby-unf-ext_0.0.7.7-1_amd64.deb ...
Unpacking ruby-unf-ext (0.0.7.7-1) over (0.0.7.6-1+b3) ...
Preparing to unpack .../193-ruby2.7_2.7.4-1+b1_amd64.deb ...
Unpacking ruby2.7 (2.7.4-1+b1) over (2.7.4-1) ...
Preparing to unpack .../194-rust-doc_1.50.0+dfsg1-1_all.deb ...
...

And currently, it seems that the system is OK.
FWIW, apt-listbugs is active again, and runs without failure:
~> apt-listbugs -v
0.1.35

Thanks, for me, the issue was resolved!
xiscu


-- System Information:
Debian Release: bookworm/sid
  APT prefers testing
  APT policy: (900, 'testing'), (10, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 5.10.0-8-amd64 (SMP w/4 CPU threads)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages libruby2.7 depends on:
ii  libc62.32-4
ii  libcrypt11:4.4.25-2
ii  libedit2 3.1-20210910-1
ii  libffi8  3.4.2-2
ii  libgdbm-compat4  1.21-1
ii  libgdbm6 1.21-1
ii  libgmp10 2:6.2.1+dfsg-2
ii  libssl1.11.1.1l-1
ii  libyaml-0-2  0.2.2-1
ii  rake 13.0.3-1
ii  ruby-minitest5.13.0-1
ii  ruby-net-telnet  0.1.1-2
ii  ruby-test-unit   3.3.9-1
ii  ruby-xmlrpc  0.3.0-2
ii  zlib1g   1:1.2.11.dfsg-2

libruby2.7 recommends no packages.

libruby2.7 suggests no packages.

-- no debconf information

Bug#994969: jackd2: segfaults after today's upgrade of other Debian testing packages

[‍小太]

On Sun, 3 Oct 2021 at 20:47, Ryan Thoryk  wrote:
>
> When I had jack dump out it's module filenames during library load, it
> only appeared to load jack_firewire once.  The clue as to what's
> happening is that valgrind reports "Bad permissions for mapped region",
> if you look at the function, it's trying to pass a string literal, the
> valgrind error means that it's trying to modify the string, and since
> it's read-only, it results in a segfault.  The string and address are valid.

"Bad permissions for mapped region at address" can also mean it tried
to read from unreadable memory. The memory was mapped at some
point in the past, so it doesn't say unallocated memory

Also consider the segfault comes from strcmp(). Why would strcmp()
ever need to write to memory? You can verify with a disassember the
segfault comes from a read

> or to create a C string and pass it to the function:

I suspect this "worked" to fix the issue only due to a memory layout
change, and luck would have it that after your rebuild it now tries to
read from readable memory (albeit still not the expected memory)

Bug#994969: jackd2: segfaults after today's upgrade of other Debian testing packages

[Ryan Thoryk]

I also reported my solution comment to your upstream ticket.

--
Ryan Thoryk
r...@thoryk.com
r...@tliquest.net

Bug#994969: jackd2: segfaults after today's upgrade of other Debian testing packages

[Ryan Thoryk]

When I had jack dump out it's module filenames during library load, it 
only appeared to load jack_firewire once.  The clue as to what's 
happening is that valgrind reports "Bad permissions for mapped region", 
if you look at the function, it's trying to pass a string literal, the 
valgrind error means that it's trying to modify the string, and since 
it's read-only, it results in a segfault.  The string and address are valid.


The appropriate fix appears to be to either use your alternative 
function, or to create a C string and pass it to the function:


---
char binding[] = "glibmm__Glib::Binding::manage");
GQuark quark_manage = g_quark_from_static_string(binding);
---
or
---
GQuark quark_manage = g_quark_from_string("glibmm__Glib::Binding::manage");
---

Both of those changes work on my system, and jack_firewire now works for 
me again.  One thing online says about that function, "This function 
must not be used before library constructors have finished running."


--
Ryan Thoryk
r...@thoryk.com
r...@tliquest.net

Bug#995608: linux-image-5.14.0-1-amd64: Boot immediately hangs.

[Salvatore Bonaccorso]

Control: tags -1 + moreinfo

Hi Nathanael,

On Sun, Oct 03, 2021 at 10:02:35AM +0200, Nathanael Schweers wrote:
> Package: src:linux
> Version: 5.14.6-3
> Severity: grave
> Justification: renders package unusable
> 
> Dear Maintainer,
> 
> using this kernel, my machine no longer boots.  Instead of showing a prompt to
> enter the LUKS passphrase (as is done in version linux-image-5.10.0-7-amd64) a
> non-blinking cursor is shown.  Nothing happens afterwards.
> 
> Version linux-image-5.10.0-7-amd64 still works, but newer versions
> (linux-image-5.10.0-8-amd64 and the version this report is for) produce the
> behaviour mentioned above.
> 
> I’m afraid that I don’t have a decent idea on what extra information to 
> provide.

Could you please confirm that booting with the 'mem_encrypt=off'
kernel command line heps?

Regards,
Salvatore

Processed: Re: Bug#995608: linux-image-5.14.0-1-amd64: Boot immediately hangs.

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + moreinfo
Bug #995608 [src:linux] linux-image-5.14.0-1-amd64: Boot immediately hangs.
Added tag(s) moreinfo.

-- 
995608: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995608
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: closing 992668

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> close 992668
Bug #992668 [ricochet-im] ricochet-im: does not start
Marked Bug as done
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
992668: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=992668
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems