Bug#1016732: node-sockjs throws: TypeError: Cannot read properties of undefined (reading 'addEventListener') at WebSocketReceiver.setUp

[Yadd]

On 10/08/2022 19:32, Nilesh Patra wrote:

Hi,

Sorry to bother you over this again, but would you have any idea?
I'd be OK with a workaround if you don't have the bandwidth at the moment, but 
this
seems to come from coffee related modifications only.


Hi,

not enough time this week, I'll try next one.

Cheers,
Yadd

Processed: bug 1016972 is forwarded to https://bugs.php.net/bug.php?id=81723

[Debian Bug Tracking System]

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

> forwarded 1016972 https://bugs.php.net/bug.php?id=81723
Bug #1016972 [src:php8.1] php8.1: CVE-2022-31627
Set Bug forwarded-to-address to 'https://bugs.php.net/bug.php?id=81723'.
> thanks
Stopping processing here.

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

Processed: bug 1016978 is forwarded to https://github.com/FRRouting/frr/issues/11698

[Debian Bug Tracking System]

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

> forwarded 1016978 https://github.com/FRRouting/frr/issues/11698
Bug #1016978 [src:frr] frr: CVE-2022-37035
Set Bug forwarded-to-address to 'https://github.com/FRRouting/frr/issues/11698'.
> thanks
Stopping processing here.

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

Processed: tagging 1016971, tagging 1016972, tagging 1016974, tagging 1016973, tagging 1016975, tagging 1016980 ...

[Debian Bug Tracking System]

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

> tags 1016971 + upstream
Bug #1016971 [src:fava] fava: CVE-2022-2514 CVE-2022-2523 CVE-2022-2589
Added tag(s) upstream.
> tags 1016972 + upstream
Bug #1016972 [src:php8.1] php8.1: CVE-2022-31627
Added tag(s) upstream.
> tags 1016974 + upstream
Bug #1016974 [src:sofia-sip] sofia-sip: CVE-2022-31001 CVE-2022-31002 
CVE-2022-31003
Added tag(s) upstream.
> tags 1016973 + upstream
Bug #1016973 [src:kopanocore] kopanocore: CVE-2022-26562
Added tag(s) upstream.
> tags 1016975 + upstream
Bug #1016975 [src:libxerces2-java] libxerces2-java: CVE-2022-23437
Added tag(s) upstream.
> tags 1016980 + upstream
Bug #1016980 [src:nova] nova: CVE-2022-37394
Added tag(s) upstream.
> tags 1016977 + upstream
Bug #1016977 [src:php-laravel-framework] php-laravel-framework: CVE-2022-34943
Added tag(s) upstream.
> tags 1016976 + upstream
Bug #1016976 [src:connman] connman: CVE-2022-32292 CVE-2022-32293
Added tag(s) upstream.
> tags 1016981 + upstream
Bug #1016981 [src:wolfssl] wolfssl: CVE-2022-34293
Added tag(s) upstream.
> tags 1016978 + upstream
Bug #1016978 [src:frr] frr: CVE-2022-37035
Added tag(s) upstream.
> tags 1016979 + upstream
Bug #1016979 [src:radare2] radare2: CVE-2022-34502 CVE-2022-34520
Added tag(s) upstream.
> tags 1016982 + upstream
Bug #1016982 [src:rails] rails: CVE-2022-2
Added tag(s) upstream.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1016971: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1016971
1016972: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1016972
1016973: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1016973
1016974: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1016974
1016975: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1016975
1016976: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1016976
1016977: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1016977
1016978: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1016978
1016979: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1016979
1016980: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1016980
1016981: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1016981
1016982: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1016982
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1016996: marked as done (libnl-3-200-udeb: uninstallable, depends on non-udeb sgml-base)

[Debian Bug Tracking System]

Your message dated Thu, 11 Aug 2022 00:48:59 +
with message-id 
and subject line Bug#1016996: fixed in libnl3 3.7.0-0.2
has caused the Debian Bug report #1016996,
regarding libnl-3-200-udeb: uninstallable, depends on non-udeb sgml-base
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.)


-- 
1016996: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1016996
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libnl-3-200-udeb
Version: 3.7.0-0.1
Severity: grave
Tags: d-i patch
Justification: renders package unusable
X-Debbugs-Cc: Matthieu Baerts , Adam Borowski 
, debian-b...@lists.debian.org

Hi Matthieu, hi Adam,

The set of packages you uploaded contains uninstallable udebs, as they
depend on sgml-base, which doesn't exist in the installer context
(there's no udeb for it. Current dependencies are as follows:

$ dpkg --info libnl-3-200-udeb_3.7.0-0.1_amd64.udeb|grep Depends
 Depends: sgml-base (>= 1.28), libc6-udeb (>= 2.34)

$ dpkg --info libnl-genl-3-200-udeb_3.4.0-1+b1_amd64.udeb|grep Depends
 Depends: libnl-3-200-udeb (= 3.4.0-1+b1), libc6-udeb (>= 2.28)

This leads to the following build failure for the daily builds of the
installer:

The following packages have unmet dependencies:
 libnl-3-200-udeb : Depends: sgml-base (>= 1.28) but it is not installable
 libnl-genl-3-200-udeb : Depends: sgml-base (>= 1.28) but it is not 
installable
E: Unable to correct problems, you have held broken packages.

(Note that I'm filing this bug report against only one of those udebs.)

This is not your fault, that's debhelper's #1015263:
  https://bugs.debian.org/1015263

but I thought I'd loop you in so that you know about this issue, and
about my current plan: the installer team (X-D-Cc'd) doesn't require an
immediate fix, but since I'm not sure when the debhelper bug is getting
fixed (and packages binNMU'd), I thought I'd prepare a workaround to
make sure this source package isn't a blocker when we plan for a Debian
Installer release.

I'll upload shortly, source debdiff attached. Please let me know if you
have any comments or questions.


In passing, thanks for your work on this package!


Cheers,
-- 
Cyril Brulebois (k...@debian.org)
D-I release manager -- Release team member -- Freelance Consultant
diff -Nru libnl3-3.7.0/debian/changelog libnl3-3.7.0/debian/changelog
--- libnl3-3.7.0/debian/changelog   2022-08-01 15:53:32.0 +
+++ libnl3-3.7.0/debian/changelog   2022-08-10 23:43:51.0 +
@@ -1,3 +1,12 @@
+libnl3 (3.7.0-0.2) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Dodge debhelper's #1015263 by resetting misc:Depends via
+DEB_DH_GENCONTROL_ARGS_libnl{,-genl}-3-200-udeb to avoid pulling
+sgml-base.
+
+ -- Cyril Brulebois   Wed, 10 Aug 2022 23:43:51 +
+
 libnl3 (3.7.0-0.1) unstable; urgency=low
 
   * Non-maintainer upload (Closes: #1016485)
diff -Nru libnl3-3.7.0/debian/rules libnl3-3.7.0/debian/rules
--- libnl3-3.7.0/debian/rules   2022-08-01 14:30:22.0 +
+++ libnl3-3.7.0/debian/rules   2022-08-10 23:43:11.0 +
@@ -34,6 +34,10 @@
 
 DEB_CONFIGURE_EXTRA_FLAGS += --libdir=\$${prefix}/lib/$(DEB_HOST_MULTIARCH)
 
+# Dodge debhelper's #1015263, pulling sgml-base for udebs:
+DEB_DH_GENCONTROL_ARGS_$(udeb_libnl) = -- -Vmisc:Depends=
+DEB_DH_GENCONTROL_ARGS_$(udeb_libnl_genl) = -- -Vmisc:Depends=
+
 clean::
# from some unknown reason CDBS does not remove the builddir
rm -rf $(DEB_BUILDDIR)
--- End Message ---
--- Begin Message ---
Source: libnl3
Source-Version: 3.7.0-0.2
Done: Cyril Brulebois 

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

Debian distribution maintenance software
pp.
Cyril Brulebois  (supplier of updated libnl3 package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 10 Aug 2022 23:43:51 +
Source: libnl3
Architecture: source
Version: 3.7.0-0.2
Distribution: unstable
Urgency: medium
Maintainer: Heiko Stuebner 
Changed-By: Cyril Brulebois 

Bug#1015263: libidn2-0: Depends sgml-base

[Cyril Brulebois]

Cyril Brulebois  (2022-08-11):
> This breaks d-i builds, (at least) via libnl udebs picking up a
> dependency on sgml-base, which doesn't exist in a udeb context.

For completeness, I've just uploaded a workaround for src:libnl3 (see
https://bugs.debian.org/1016996 for details), so that particular
instance is covered; but it'd still be nice to contain the problem
before more packages get that buggy dependency.

Thanks already!


Cheers,
-- 
Cyril Brulebois (k...@debian.org)
D-I release manager -- Release team member -- Freelance Consultant


signature.asc
Description: PGP signature

Bug#1016996: libnl-3-200-udeb: uninstallable, depends on non-udeb sgml-base

[Cyril Brulebois]

Package: libnl-3-200-udeb
Version: 3.7.0-0.1
Severity: grave
Tags: d-i patch
Justification: renders package unusable
X-Debbugs-Cc: Matthieu Baerts , Adam Borowski 
, debian-b...@lists.debian.org

Hi Matthieu, hi Adam,

The set of packages you uploaded contains uninstallable udebs, as they
depend on sgml-base, which doesn't exist in the installer context
(there's no udeb for it. Current dependencies are as follows:

$ dpkg --info libnl-3-200-udeb_3.7.0-0.1_amd64.udeb|grep Depends
 Depends: sgml-base (>= 1.28), libc6-udeb (>= 2.34)

$ dpkg --info libnl-genl-3-200-udeb_3.4.0-1+b1_amd64.udeb|grep Depends
 Depends: libnl-3-200-udeb (= 3.4.0-1+b1), libc6-udeb (>= 2.28)

This leads to the following build failure for the daily builds of the
installer:

The following packages have unmet dependencies:
 libnl-3-200-udeb : Depends: sgml-base (>= 1.28) but it is not installable
 libnl-genl-3-200-udeb : Depends: sgml-base (>= 1.28) but it is not 
installable
E: Unable to correct problems, you have held broken packages.

(Note that I'm filing this bug report against only one of those udebs.)

This is not your fault, that's debhelper's #1015263:
  https://bugs.debian.org/1015263

but I thought I'd loop you in so that you know about this issue, and
about my current plan: the installer team (X-D-Cc'd) doesn't require an
immediate fix, but since I'm not sure when the debhelper bug is getting
fixed (and packages binNMU'd), I thought I'd prepare a workaround to
make sure this source package isn't a blocker when we plan for a Debian
Installer release.

I'll upload shortly, source debdiff attached. Please let me know if you
have any comments or questions.


In passing, thanks for your work on this package!


Cheers,
-- 
Cyril Brulebois (k...@debian.org)
D-I release manager -- Release team member -- Freelance Consultant
diff -Nru libnl3-3.7.0/debian/changelog libnl3-3.7.0/debian/changelog
--- libnl3-3.7.0/debian/changelog   2022-08-01 15:53:32.0 +
+++ libnl3-3.7.0/debian/changelog   2022-08-10 23:43:51.0 +
@@ -1,3 +1,12 @@
+libnl3 (3.7.0-0.2) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Dodge debhelper's #1015263 by resetting misc:Depends via
+DEB_DH_GENCONTROL_ARGS_libnl{,-genl}-3-200-udeb to avoid pulling
+sgml-base.
+
+ -- Cyril Brulebois   Wed, 10 Aug 2022 23:43:51 +
+
 libnl3 (3.7.0-0.1) unstable; urgency=low
 
   * Non-maintainer upload (Closes: #1016485)
diff -Nru libnl3-3.7.0/debian/rules libnl3-3.7.0/debian/rules
--- libnl3-3.7.0/debian/rules   2022-08-01 14:30:22.0 +
+++ libnl3-3.7.0/debian/rules   2022-08-10 23:43:11.0 +
@@ -34,6 +34,10 @@
 
 DEB_CONFIGURE_EXTRA_FLAGS += --libdir=\$${prefix}/lib/$(DEB_HOST_MULTIARCH)
 
+# Dodge debhelper's #1015263, pulling sgml-base for udebs:
+DEB_DH_GENCONTROL_ARGS_$(udeb_libnl) = -- -Vmisc:Depends=
+DEB_DH_GENCONTROL_ARGS_$(udeb_libnl_genl) = -- -Vmisc:Depends=
+
 clean::
# from some unknown reason CDBS does not remove the builddir
rm -rf $(DEB_BUILDDIR)

Bug#1016740: marked as done (golang-github-cli-go-gh: autopkgtest regression: TestGQLClientDoWithContext/http_fail_request_timed_out)

[Debian Bug Tracking System]

Your message dated Wed, 10 Aug 2022 22:49:16 +
with message-id 
and subject line Bug#1016740: fixed in golang-github-cli-go-gh 
0.0.3+git20220623.91ca4ef-2
has caused the Debian Bug report #1016740,
regarding golang-github-cli-go-gh: autopkgtest regression: 
TestGQLClientDoWithContext/http_fail_request_timed_out
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.)


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

Source: golang-github-cli-go-gh
Version: 0.0.3+git20220623.91ca4ef-1
Severity: serious
User: debian...@lists.debian.org
Usertags: regression

Dear maintainer(s),

With a recent upload of golang-github-cli-go-gh the autopkgtest of 
golang-github-cli-go-gh fails in testing when that autopkgtest is run 
with the binary packages of golang-github-cli-go-gh from unstable. It 
passes when run with only packages from testing. In tabular form:


   passfail
golang-github-cli-go-gh from testing0.0.3+git20220623.91ca4ef-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=golang-github-cli-go-gh

https://ci.debian.net/data/autopkgtest/testing/amd64/g/golang-github-cli-go-gh/24389592/log.gz


=== RUN   TestGQLClientDoWithContext/http_fail_request_canceled
gql_client_test.go:170: Error Trace:gql_client_test.go:170
Error:  An error is expected but got nil.
Test:   
TestGQLClientDoWithContext/http_fail_request_canceled
=== RUN   TestGQLClientDoWithContext/http_fail_request_timed_out
gql_client_test.go:170: Error Trace:gql_client_test.go:170
Error:  An error is expected but got nil.
	Test: 
TestGQLClientDoWithContext/http_fail_request_timed_out

--- FAIL: TestGQLClientDoWithContext (0.00s)
--- FAIL: TestGQLClientDoWithContext/http_fail_request_canceled (0.00s)
--- FAIL: TestGQLClientDoWithContext/http_fail_request_timed_out 
(0.00s)




=== RUN   TestRESTClientDoWithContext/http_fail_request_canceled
rest_client_test.go:341:Error Trace:rest_client_test.go:341
Error:  An error is expected but got nil.
	Test: 
TestRESTClientDoWithContext/http_fail_request_canceled

=== RUN   TestRESTClientDoWithContext/http_fail_request_timed_out
rest_client_test.go:341:Error Trace:rest_client_test.go:341
Error:  An error is expected but got nil.
	Test: 
TestRESTClientDoWithContext/http_fail_request_timed_out

--- FAIL: TestRESTClientDoWithContext (0.00s)
--- FAIL: TestRESTClientDoWithContext/http_fail_request_canceled 
(0.00s)
--- FAIL: TestRESTClientDoWithContext/http_fail_request_timed_out 
(0.00s)



=== RUN   TestRESTClientRequestWithContext
=== RUN   TestRESTClientRequestWithContext/http_fail_request_canceled
rest_client_test.go:394:Error Trace:rest_client_test.go:394
Error:  An error is expected but got nil.
	Test: 
TestRESTClientRequestWithContext/http_fail_request_canceled

=== RUN   TestRESTClientRequestWithContext/http_fail_request_timed_out
rest_client_test.go:394:Error Trace:rest_client_test.go:394
Error:  An error is expected but got nil.
	Test: 
TestRESTClientRequestWithContext/http_fail_request_timed_out

--- FAIL: TestRESTClientRequestWithContext (0.00s)
--- FAIL: 
TestRESTClientRequestWithContext/http_fail_request_canceled (0.00s)
--- FAIL: 
TestRESTClientRequestWithContext/http_fail_request_timed_out (0.00s)

=== RUN   TestRestPrefix
=== RUN   TestRestPrefix/github
=== RUN   TestRestPrefix/localhost
=== RUN   TestRestPrefix/enterprise
--- PASS: TestRestPrefix (0.00s)
--- PASS: TestRestPrefix/github (0.00s)
--- PASS: TestRestPrefix/localhost (0.00s)
--- PASS: TestRestPrefix/enterprise (0.00s)
FAIL
FAILgithub.com/cli/go-gh/internal/api   0.007s




OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: golang-github-cli-go-gh
Source-Version: 0.0.3+git20220623.91ca4ef-2
Done: Anthony Fok 

We 

Processed: Re: Bug#1015263: libidn2-0: Depends sgml-base

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #1015263 [debhelper] libidn2-0: Depends sgml-base
Severity set to 'serious' from 'normal'

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

Processed: Bug#1016740 marked as pending in golang-github-cli-go-gh

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1016740 [src:golang-github-cli-go-gh] golang-github-cli-go-gh: autopkgtest 
regression: TestGQLClientDoWithContext/http_fail_request_timed_out
Added tag(s) pending.

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

Bug#1016740: marked as pending in golang-github-cli-go-gh

[Anthony Fok]

Control: tag -1 pending

Hello,

Bug #1016740 in golang-github-cli-go-gh 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/go-team/packages/golang-github-cli-go-gh/-/commit/cd17edeaba7168e08b77180e549a006d1d0eeafe


Depend on golang-gopkg-h2non-gock.v1-dev (>= 1.1.2) version explicitly

Thanks: Paul Gevers for the autopkgtest regression report!
Closes: #1016740


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1016740

Bug#993088: tootle FTBFS: error: The name `get_phrase' does not exist in the context of `Soup.Status'

[Evangelos Ribeiro Tzaras]

Hi Adrian,

On Fri, 27 Aug 2021 13:32:22 +0300 Adrian Bunk  wrote:
> Source: tootle
> Version: 1.0-alpha2-1
> Severity: serious
> Tags: ftbfs bookworm sid

> ...
> ../../src/Services/Network.vala:69.19-69.40: error: The name `get_phrase' does
not exist in the context of `Soup.Status' (libsoup-2.4)
>   var reason = Soup.Status.get_phrase (code);
>    ^^

This was fixed with the latest upload.

because the there was a small oversight with the changelog [0]
(1.0-3 never actually made it to unstable)
the bug did not get autoclosed.

[0]
https://metadata.ftp-master.debian.org/changelogs/main/t/tootle/tootle_1.0-ds1-4_changelog

-- 
Cheers,

Evangelos
PGP: B938 6554 B7DD 266B CB8E 29A9 90F0 C9B1 8A6B 4A19


signature.asc
Description: This is a digitally signed message part

Bug#993088: marked as done (tootle FTBFS: error: The name `get_phrase' does not exist in the context of `Soup.Status')

[Debian Bug Tracking System]

Your message dated Thu, 11 Aug 2022 00:19:48 +0200
with message-id 
<2b228a503f1ddaa163a5a70bf0d9f29904a0a05b.ca...@fortysixandtwo.eu>
and subject line Re: tootle FTBFS: error: The name `get_phrase' does not exist 
in the context of `Soup.Status'
has caused the Debian Bug report #993088,
regarding tootle FTBFS: error: The name `get_phrase' does not exist in the 
context of `Soup.Status'
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.)


-- 
993088: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=993088
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: tootle
Version: 1.0-alpha2-1
Severity: serious
Tags: ftbfs bookworm sid

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/tootle.html

...
../../src/Services/Network.vala:69.19-69.40: error: The name `get_phrase' does 
not exist in the context of `Soup.Status' (libsoup-2.4)
var reason = Soup.Status.get_phrase (code);
 ^^
--- End Message ---
--- Begin Message ---
Hi Adrian,

On Fri, 27 Aug 2021 13:32:22 +0300 Adrian Bunk  wrote:
> Source: tootle
> Version: 1.0-alpha2-1
> Severity: serious
> Tags: ftbfs bookworm sid

> ...
> ../../src/Services/Network.vala:69.19-69.40: error: The name `get_phrase' does
not exist in the context of `Soup.Status' (libsoup-2.4)
>   var reason = Soup.Status.get_phrase (code);
>    ^^

This was fixed with the latest upload.

because the there was a small oversight with the changelog [0]
(1.0-3 never actually made it to unstable)
the bug did not get autoclosed.

[0]
https://metadata.ftp-master.debian.org/changelogs/main/t/tootle/tootle_1.0-ds1-4_changelog

-- 
Cheers,

Evangelos
PGP: B938 6554 B7DD 266B CB8E 29A9 90F0 C9B1 8A6B 4A19


signature.asc
Description: This is a digitally signed message part
--- End Message ---

Bug#1016965: marked as done (gitlab upgrading to 15.1.3 fails with ActiveRecord::DangerousAttributeError: gitlab_schema is defined by Active Record)

[Debian Bug Tracking System]

Your message dated Wed, 10 Aug 2022 21:55:10 +
with message-id 
and subject line Bug#1016965: fixed in gitlab 15.1.4+ds1-1
has caused the Debian Bug report #1016965,
regarding gitlab upgrading to 15.1.3 fails with 
ActiveRecord::DangerousAttributeError: gitlab_schema is defined by Active Record
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.)


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

Package: gitlab
Version: 15.0.4+ds1-1
Severity: grave

Updating gitlab to 15.1.3 fails during db migrations with the following 
error. 15.1.3 is available from staging and fasttrack-staging repos 
(see wiki.debian.org/gitlab).


main: == 20220512190659 RemoveWebHooksWebHookLogsWebHookIdFk: migrated 
(0.0252s)



main: == 20220513043344 RescheduleExpireOAuthTokens: migrating 
=

=
main: -- transaction_open?()
main: -> 0.s
main: -- transaction_open?()
main: -> 0.s
rake aborted!
StandardError: An error has occurred, all later migrations canceled:

gitlab_schema is defined by Active Record. Check to make sure that you 
don't hav

e an attribute or method with the same name.
/usr/share/rubygems-integration/all/gems/activerecord-6.1.4.7/lib/active_record/
attribute_methods.rb:93:in `instance_method_already_implemented?'
/usr/share/rubygems-integration/all/gems/activerecord-6.1.4.7/lib/active_record/
attribute_methods/primary_key.rb:60:in 
`instance_method_already_implemented?'

/usr/share/rubygems-integration/all/gems/activemodel-6.1.4.7/lib/active_model/at
tribute_methods.rb:293:in `block (2 levels) in define_attribute_method'
/usr/share/rubygems-integration/all/gems/activemodel-6.1.4.7/lib/active_model/at
tribute_methods.rb:290:in `each'
/usr/share/rubygems-integration/all/gems/activemodel-6.1.4.7/lib/active_model/at
tribute_methods.rb:290:in `block in define_attribute_method'
/usr/share/rubygems-integration/all/gems/activemodel-6.1.4.7/lib/active_model/at
tribute_methods.rb:342:in `batch'
/usr/share/rubygems-integration/all/gems/activemodel-6.1.4.7/lib/active_model/at
tribute_methods.rb:289:in `define_attribute_method'
/usr/share/rubygems-integration/all/gems/activemodel-6.1.4.7/lib/active_model/at
tribute_methods.rb:255:in `block (2 levels) in define_attribute_methods'
/usr/share/rubygems-integration/all/gems/activemodel-6.1.4.7/lib/active_model/at
tribute_methods.rb:255:in `each'
/usr/share/rubygems-integration/all/gems/activemodel-6.1.4.7/lib/active_model/at
tribute_methods.rb:255:in `block in define_attribute_methods'
/usr/share/rubygems-integration/all/gems/activemodel-6.1.4.7/lib/active_model/at
tribute_methods.rb:345:in `batch'
/usr/share/rubygems-integration/all/gems/activemodel-6.1.4.7/lib/active_model/at
tribute_methods.rb:254:in `define_attribute_methods'
/usr/share/rubygems-integration/all/gems/activerecord-6.1.4.7/lib/active_record/
attribute_methods.rb:65:in `block in define_attribute_methods'
/usr/share/rubygems-integration/all/gems/activerecord-6.1.4.7/lib/active_record/
attribute_methods.rb:62:in `define_attribute_methods'
/usr/share/rubygems-integration/all/gems/activerecord-6.1.4.7/lib/active_record/
core.rb:775:in `init_internals'
/usr/share/rubygems-integration/all/gems/activerecord-6.1.4.7/lib/active_record/
associations.rb:344:in `init_internals'
/usr/share/rubygems-integration/all/gems/activerecord-6.1.4.7/lib/active_record/
core.rb:507:in `initialize'
/usr/share/rubygems-integration/all/gems/activerecord-6.1.4.7/lib/active_record/
inheritance.rb:72:in `new'
/usr/share/rubygems-integration/all/gems/activerecord-6.1.4.7/lib/active_record/
inheritance.rb:72:in `new'
/usr/share/gitlab/lib/gitlab/database/migrations/batched_background_migration_he
lpers.rb:102:in `queue_batched_background_migration'
/usr/share/gitlab/db/post_migrate/20220513043344_reschedule_expire_o_auth_tokens
.rb:16:in `up'
/usr/share/rubygems-integration/all/gems/activerecord-6.1.4.7/lib/active_record/
migration.rb:870:in `public_send'
/usr/share/rubygems-integration/all/gems/activerecord-6.1.4.7/lib/active_record/
migration.rb:870:in `exec_migration'
/usr/share/gitlab/lib/gitlab/database/migration_helpers/restrict_gitlab_schema.r
b:33:in `block in exec_migration'
/usr/share/gitlab/lib/gitlab/database/query_analyzer.rb:37:in `within'
/usr/share/gitlab/lib/gitlab/database/migration_helpers/restrict_gitlab_schema.r
b:30:in `exec_migration'
/usr/share/rubygems-integration/all/gems/activerecord-6.1.4.7/lib/active_record/
migration.rb:851:in `block (2 levels) in migrate'

Bug#1012898: marked as done (assimp: ftbfs with GCC-12)

[Debian Bug Tracking System]

Your message dated Wed, 10 Aug 2022 21:49:17 +
with message-id 
and subject line Bug#1012898: fixed in assimp 5.2.4~ds0-1.1
has caused the Debian Bug report #1012898,
regarding assimp: ftbfs with GCC-12
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.)


-- 
1012898: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1012898
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:assimp
Version: 5.2.4~ds0-1
Severity: normal
Tags: sid bookworm
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-12

[This bug is targeted to the upcoming bookworm release]

Please keep this issue open in the bug tracker for the package it
was filed for.  If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-12/g++-12, but succeeds to build with gcc-11/g++-11. The
severity of this report will be raised before the bookworm release.

The full build log can be found at:
http://qa-logs.debian.net/2022/06/09/gcc12/assimp_5.2.4~ds0-1_unstable_gcc12.log
The last lines of the build log are at the end of this report.

To build with GCC 11, either set CC=gcc-11 CXX=g++-11 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t=experimental install g++ 

Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-11/porting_to.html

GCC 11 defaults to the GNU++17 standard.  If your package installs
header files in /usr/include, please don't work around C++17 issues
by choosing a lower C++ standard for the package build, but fix these
issues to build with the C++17 standard.

[...]
cd "/<>/obj-x86_64-linux-gnu/code" && /usr/bin/c++ 
-DASSIMP_BUILD_DLL_EXPORT -DASSIMP_BUILD_NO_C4D_IMPORTER 
-DASSIMP_BUILD_NO_M3D_EXPORTER -DASSIMP_BUILD_NO_M3D_IMPORTER 
-DASSIMP_BUILD_NO_OWN_ZLIB -DASSIMP_IMPORTER_GLTF_USE_OPEN3DGC=1 
-DMINIZ_USE_UNALIGNED_LOADS_AND_STORES=0 -DOPENDDLPARSER_BUILD 
-DRAPIDJSON_HAS_STDSTRING=1 -DRAPIDJSON_NOMEMBERITERATORCLASS -Dassimp_EXPORTS 
-I"/<>/obj-x86_64-linux-gnu/include" 
-I"/<>/obj-x86_64-linux-gnu" -I"/<>/include" 
-I"/<>/code" -I"/<>/." 
-I"/<>/code/../contrib/pugixml/src" 
-I"/<>/code/../contrib/rapidjson/include" 
-I"/<>/code/../contrib" 
-I"/<>/code/../contrib/openddlparser/include" 
-I"/<>/code/../include" 
-I"/<>/obj-x86_64-linux-gnu/code/../include" 
-I/usr/include/minizip -fvisibility=hidden -fno-strict-aliasing -Wall -g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong -Wfo
 rmat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 
-DASSIMP_ENABLE_DRACO=1 -fPIC   -D'ASSIMP_BUILD_ARCHITECTURE="amd64"' -Wall 
-Werror -std=gnu++11 -MD -MT 
code/CMakeFiles/assimp.dir/AssetLib/SIB/SIBImporter.cpp.o -MF 
CMakeFiles/assimp.dir/AssetLib/SIB/SIBImporter.cpp.o.d -o 
CMakeFiles/assimp.dir/AssetLib/SIB/SIBImporter.cpp.o -c 
"/<>/code/AssetLib/SIB/SIBImporter.cpp"
[ 68%] Building CXX object 
code/CMakeFiles/assimp.dir/AssetLib/SMD/SMDLoader.cpp.o
cd "/<>/obj-x86_64-linux-gnu/code" && /usr/bin/c++ 
-DASSIMP_BUILD_DLL_EXPORT -DASSIMP_BUILD_NO_C4D_IMPORTER 
-DASSIMP_BUILD_NO_M3D_EXPORTER -DASSIMP_BUILD_NO_M3D_IMPORTER 
-DASSIMP_BUILD_NO_OWN_ZLIB -DASSIMP_IMPORTER_GLTF_USE_OPEN3DGC=1 
-DMINIZ_USE_UNALIGNED_LOADS_AND_STORES=0 -DOPENDDLPARSER_BUILD 
-DRAPIDJSON_HAS_STDSTRING=1 -DRAPIDJSON_NOMEMBERITERATORCLASS -Dassimp_EXPORTS 
-I"/<>/obj-x86_64-linux-gnu/include" 
-I"/<>/obj-x86_64-linux-gnu" -I"/<>/include" 
-I"/<>/code" -I"/<>/." 
-I"/<>/code/../contrib/pugixml/src" 
-I"/<>/code/../contrib/rapidjson/include" 
-I"/<>/code/../contrib" 
-I"/<>/code/../contrib/openddlparser/include" 
-I"/<>/code/../include" 
-I"/<>/obj-x86_64-linux-gnu/code/../include" 
-I/usr/include/minizip -fvisibility=hidden -fno-strict-aliasing -Wall -g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong -Wfo
 rmat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 
-DASSIMP_ENABLE_DRACO=1 -fPIC   -D'ASSIMP_BUILD_ARCHITECTURE="amd64"' -Wall 
-Werror -std=gnu++11 -MD -MT 
code/CMakeFiles/assimp.dir/AssetLib/SMD/SMDLoader.cpp.o -MF 
CMakeFiles/assimp.dir/AssetLib/SMD/SMDLoader.cpp.o.d -o 
CMakeFiles/assimp.dir/AssetLib/SMD/SMDLoader.cpp.o -c 
"/<>/code/AssetLib/SMD/SMDLoader.cpp"
[ 69%] Building CXX object 
code/CMakeFiles/assimp.dir/AssetLib/STL/STLLoader.cpp.o
cd 

Bug#1014003: marked as done (iwyu 0.18 requires clang-14)

[Debian Bug Tracking System]

Your message dated Wed, 10 Aug 2022 21:05:00 +
with message-id 
and subject line Bug#1014003: fixed in iwyu 8.18-2
has caused the Debian Bug report #1014003,
regarding iwyu 0.18 requires clang-14
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.)


-- 
1014003: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1014003
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: iwyu
Version: 8.18-1
Severity: grave
Justification: renders package unusable
X-Debbugs-Cc: alx.manpa...@gmail.com


Hi,

iwyu 0.18 requires clang 14 to work, as specified on their documentation.
Having an older version of clang causes iwyu to fail for the most basic
stuff, such as finding compiler builtin headers (e.g., ).

Just by installing the correct clang version, the problem was fixed
(I'm not sure if installing a clang library, without installing the full
clang would have been enough, though).

Cheers,

Alex


-- System Information:
Debian Release: bookworm/sid
Architecture: amd64 (x86_64)

Kernel: Linux 5.18.0-2-amd64 (SMP w/16 CPU threads; PREEMPT)
Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)
LSM: AppArmor: enabled

Versions of packages iwyu depends on:
ii  clang   1:13.0-54
ii  clang-111:11.1.0-6+b2
ii  clang-131:13.0.1-6
ii  clang-141:14.0.6-1
ii  libc6   2.33-7
ii  libclang-cpp14  1:14.0.6-1
ii  libllvm14   1:14.0.6-1
ii  libstdc++6  12.1.0-4
ii  python3 3.10.4-1+b1

iwyu recommends no packages.

iwyu suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: iwyu
Source-Version: 8.18-2
Done: Sylvestre Ledru 

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

Debian distribution maintenance software
pp.
Sylvestre Ledru  (supplier of updated iwyu 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, 10 Aug 2022 22:36:00 +0200
Source: iwyu
Architecture: source
Version: 8.18-2
Distribution: unstable
Urgency: medium
Maintainer: LLVM Packaging Team 
Changed-By: Sylvestre Ledru 
Closes: 1003487 1010495 1014003 1016949
Changes:
 iwyu (8.18-2) unstable; urgency=medium
 .
   * Build using release.
 Thanks to Steven Trabert
 (Closes: #1016949)
   * Force the usage of clang-14 (Closes: #1014003, #1010495, #1003487)
Checksums-Sha1:
 65529b278ee0ca4c1f22f30a1678c2158e3a90f9 1999 iwyu_8.18-2.dsc
 7ba1d7941d39eedc8ffd40165d82adfbd17db02f 8880 iwyu_8.18-2.debian.tar.xz
 f464d64358e2bce98c32d1be0518ec9e22b23619 8696 iwyu_8.18-2_amd64.buildinfo
Checksums-Sha256:
 0cd776bf4322b0ae351e3904345457e009b2c16fae87d41ce4b1fc024c3538a2 1999 
iwyu_8.18-2.dsc
 ee91ca8844406e4c137b26ed3c1a9f67e4c1642be6ad9f666da306b4e3e87939 8880 
iwyu_8.18-2.debian.tar.xz
 07b5032502854104065bcb7fa1e160e752c8506552c710761fb6d1fc3c98ca35 8696 
iwyu_8.18-2_amd64.buildinfo
Files:
 1167b45bf9c44b1e78cf091c77098f6a 1999 devel optional iwyu_8.18-2.dsc
 bf0f6ee3e5de425355c1c28398b42f27 8880 devel optional iwyu_8.18-2.debian.tar.xz
 d3734eceb23c582046d40dd5b454f115 8696 devel optional 
iwyu_8.18-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEtg21mU05vsTRqVzPfmUo2nUvG+EFAmL0GJwACgkQfmUo2nUv
G+E+CxAAn74rCWlL9/umX64SphgxQhs3UlaXTXb3rFAMb/75wo5iUkT/BWjvEyLS
Ir4HkuX6D5Dqc8awpL75eFiNWmCWVRkXKxgrR8SYu2WHXZ24KdbhAseEfmygdiNm
U2B4VG5r+JWhl/yWTmTnfzofM1YCYALouxhjkQlyXlXXA800OncqSJz0gOJqsJ0S
GZBiCG58W7TitMjkvC2Py4wQywrnsnOocdAVyiNZyYtx6hoeF9dIb97KBak7cJLw
6SF1lqp4GqYoIInmBmqwmiOlQ9SUiHwKi0JjQli/aMFMtZqk11yBJMUjT6Ogev37
4xRdUZhk1DSqVgGe4Wcoz6DdlHdUNw/BUq5rGkxdixUB8tmiSdWpySZYRnID6F7W
6KA7154Vjj3jCAXI06oDbVufOsLfoumwqOgsOV0o3vOZ6qcFJp+M8uQfjQU1QACi
MrWzcsEWYLys2r1iBK0CH1g29DHNjYHbf/8awnf8LOXAD9u1o8iei2kAmTD4UhCb
6IVphmmcawFWoIqS/8X2tfPEpBHqBWSgvCPXuXfYN+ZhdqrHoUGA3DcY89HAkAF/
GuoXSx3dW5EFY6M/zsnKl8OokUDE8nlsvjSZpPl86QlrHG0MZhYh5K+43XZs6QaZ
8utbYgy6JNjxTjHpUUuoXZe7fNyUQAN5UzU5M6uu+CbZPfKEJ+4=
=7Jqg
-END PGP SIGNATURE End Message ---

Bug#1016989: manpages-fr: trying to overwrite tree.1.gz, which is also in package tree 2.0.2-1

[Vincent Lefevre]

Package: manpages-fr
Version: 4.15.0-3
Severity: grave
Justification: renders package unusable

manpages-fr 4.15.0-3 cannot be installed:

Unpacking manpages-fr (4.15.0-3) over (4.14.0-4) ...
dpkg: error processing archive 
/tmp/apt-dpkg-install-n3cIma/18-manpages-fr_4.15.0-3_all.deb (--unpack):
 trying to overwrite '/usr/share/man/fr/man1/tree.1.gz', which is also in 
package tree 2.0.2-1
dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)

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

Kernel: Linux 5.18.0-3-amd64 (SMP w/12 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=POSIX, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

manpages-fr depends on no packages.

manpages-fr recommends no packages.

Versions of packages manpages-fr suggests:
ii  man-db [man-browser]  2.10.2-1
ii  manpages  5.13-1

-- no debconf information

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Bug#936777: k3d: Python2 removal in sid/bullseye

[Manuel A. Fernandez Montecelo]

Hi,

On Sun, 10 Apr 2022 at 22:04, Moritz Mühlenhoff  wrote:
>
> Revisiting this two years later; I really think k3d should be removed now?
> Nothing changed upstream and at this point it's uninstallable in unstable
> for many other libraries besides Python 2:
>
> -
> The following packages have unmet dependencies:
>  k3d : Depends: libboost-program-options1.67.0 but it is not installable
>Depends: libboost-python1.67.0 but it is not installable
>Depends: libboost-regex1.67.0 (>= 1.67.0-10) but it is not installable
>Depends: libcgal13 but it is not installable
>Depends: libopenexr24 (>= 2.3.0) but it is not installable
> E: Unable to correct problems, you have held broken packages.
> -

Indeed, I paid attention to your other bug report  (sorry but I hadn't
seen this yet, terrible months for me and huge backlog) and sent the
necessary incantations to control@ to ask for removal, I hope.

If upstream keeps inactive there's not much that we can do at this point.

Thanks for keeping an eye on this!

-- 
Manuel A. Fernandez Montecelo 

Processed (with 1 error): Re: Bug#1016983: Should k3d be removed?

[Debian Bug Tracking System]

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

> severity 1016983 normal
Bug #1016983 [src:k3d] Should k3d be removed?
Severity set to 'normal' from 'serious'
> reassign 1016983 ftp.debian.org
Bug #1016983 [src:k3d] Should k3d be removed?
Bug reassigned from package 'src:k3d' to 'ftp.debian.org'.
No longer marked as found in versions k3d/0.8.0.6-8.
Ignoring request to alter fixed versions of bug #1016983 to the same values 
previously set
> retitle 1016983 RM: k3d -- RoM; unmaintained upstream and depends on
Bug #1016983 [ftp.debian.org] Should k3d be removed?
Changed Bug title to 'RM: k3d -- RoM; unmaintained upstream and depends on' 
from 'Should k3d be removed?'.
> Python2 and GTK2
Unknown command or malformed arguments to command.
> stop
Stopping processing here.

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

Bug#1016983: Should k3d be removed?

[Manuel A. Fernandez Montecelo]

Hi Moritz,

On Wed, 10 Aug 2022 at 22:33, Moritz Muehlenhoff  wrote:
>
> Source: k3d
> Version: 0.8.0.6-8
> Severity: serious
>
> Your package came up as a candidate for removal from Debian:
>
> - Python 2 will finally be removed in Bookworm and there's no
> upstream porting activity
> - Last upload four years ago
> - Multiple other FTBFS issue
>
> If you disagree and want to continue to maintain this package,
> please just close this bug (and fix the open issues).
>
> If you agree with the removal, please reassign to ftp.debian.org
> by sending the following commands to cont...@bugs.debian.org:
>
> --
> severity $BUGNUM normal
> reassign $BUGNUM ftp.debian.org
> retitle $BUGNUM RM:  -- RoM; 
> thx
> --
>
> Otherwise I'll move forward and request it's removal in a month.

Thanks, I'll ask for removal because upstream is basically dead and
hadn't moved when I requested to migrate away from GTK2 and Python2...
I very much doubt that there's any advance before the freezes...

https://github.com/K-3D/k3d/issues/38
https://github.com/K-3D/k3d/issues/30

Cheers.

-- 
Manuel A. Fernandez Montecelo 

Bug#1016986: Should pd-py be removed?

[Moritz Muehlenhoff]

Source: pd-py
Version: 0.2.2+git20170625.1.88fc77a-2
Severity: serious

Your package came up as a candidate for removal from Debian:
- Still depends on Python 2, which is finally being removed in Bookworm
- Last upload in 2018

If you disagree and want to continue to maintain this package,
please just close this bug (and fix the open issues).

If you agree with the removal, please reassign to ftp.debian.org
by sending the following commands to cont...@bugs.debian.org:

--
severity $BUGNUM normal
reassign $BUGNUM ftp.debian.org
retitle $BUGNUM RM:  -- RoM; 
thx
--

Otherwise I'll move forward and request it's removal in a month.

Cheers,
Moritz

Bug#1016985: nautilus-dropbox: Not compatible with nautilus 43

[Jeremy Bicha]

Source: nautilus-dropbox
Version: 2019.02.14-1
Severity: serious
Tags: bookworm sid
Forwarded: https://github.com/dropbox/nautilus-dropbox/issues/101

nautilus-dropbox doesn't build with nautilus 43. nautilus 43 has
switched to GTK4 and its API has received significant changes.
nautilus-dropbox will need major changes to work with the new release.

Nautilus 43 is available in Debian experimental. However, it may be
difficult to install because it uses gnome-desktop 43 and you'll need
everything you're using to be built against gnome-desktop 43 also.
Perhaps the easiest way to handle installing if you don't want to wait for
the gnome-desktop transition to begin is to revert 4420025 in nautilus
and the corresponding bump in debian/control.in and rebuild nautilus.

Thank you,
Jeremy Bicha

Bug#1016983: Should k3d be removed?

[Moritz Muehlenhoff]

Source: k3d
Version: 0.8.0.6-8
Severity: serious

Your package came up as a candidate for removal from Debian:

- Python 2 will finally be removed in Bookworm and there's no
upstream porting activity
- Last upload four years ago
- Multiple other FTBFS issue

If you disagree and want to continue to maintain this package,
please just close this bug (and fix the open issues).

If you agree with the removal, please reassign to ftp.debian.org
by sending the following commands to cont...@bugs.debian.org:

--
severity $BUGNUM normal
reassign $BUGNUM ftp.debian.org
retitle $BUGNUM RM:  -- RoM; 
thx
--

Otherwise I'll move forward and request it's removal in a month.

Cheers,
Moritz

Processed: Re: Bug#1016953: intel-media-driver: FTBFS on i386: error: format ‘%lu’ expects argument of type ‘long unsigned int’, but argument 3 has type ‘uint64_t’

[Debian Bug Tracking System]

Processing control commands:

> forwarded -1 https://github.com/intel/media-driver/issues/1468
Bug #1016953 [src:intel-media-driver] intel-media-driver: FTBFS on i386: error: 
format ‘%lu’ expects argument of type ‘long unsigned int’, but argument 3 has 
type ‘uint64_t’
Set Bug forwarded-to-address to 
'https://github.com/intel/media-driver/issues/1468'.
> tags -1 upstream
Bug #1016953 [src:intel-media-driver] intel-media-driver: FTBFS on i386: error: 
format ‘%lu’ expects argument of type ‘long unsigned int’, but argument 3 has 
type ‘uint64_t’
Added tag(s) upstream.

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

Bug#1016953: intel-media-driver: FTBFS on i386: error: format ‘%lu’ expects argument of type ‘long unsigned int’, but argument 3 has type ‘uint64_t’

[Sebastian Ramacher]

Control: forwarded -1 https://github.com/intel/media-driver/issues/1468
Control: tags -1 upstream

On 2022-08-10 21:13:47 +0100, Simon McVittie wrote:
> Control: tags -1 - patch
> 
> On Wed, 10 Aug 2022 at 20:55:44 +0100, Simon McVittie wrote:
> > Yes, that seems to work.
> 
> Sorry, no, that change is not sufficient. I also get:
> 
> In file included from 
> /<>/media_common/agnostic/common/os/mos_os.h:31,
>  from 
> /<>/media_driver/agnostic/common/os/mos_context.h:30,
>  from 
> /<>/media_driver/linux/common/ddi/media_libva_common.h:37,
>  from 
> /<>/media_driver/linux/common/cm/ddi/media_libva_cm.h:30,
>  from 
> /<>/media_driver/linux/common/cm/hal/cm_def_os.h:41,
>  from 
> /<>/media_driver/agnostic/common/cm/cm_def.h:30,
>  from 
> /<>/media_driver/agnostic/common/cm/cm_kernel.h:30,
>  from 
> /<>/media_driver/agnostic/common/cm/cm_kernel_rt.h:30,
>  from 
> /<>/media_driver/agnostic/common/cm/cm_kernel_ex.h:28,
>  from 
> /<>/media_driver/agnostic/common/cm/cm_kernel_ex.cpp:27:
> In static member function ‘static _Ty* MosUtilities::MosNewArrayUtil(size_t) 
> [with _Ty = unsigned char; _Types = {}]’,
> inlined from ‘virtual int32_t CmKernelEx::Initialize(const char*, const 
> char*)’ at 
> /<>/media_driver/agnostic/common/cm/cm_kernel_ex.cpp:192:22,
> inlined from ‘virtual int32_t CmKernelEx::Initialize(const char*, const 
> char*)’ at 
> /<>/media_driver/agnostic/common/cm/cm_kernel_ex.cpp:70:9:
> /<>/media_softlet/agnostic/common/os/mos_utilities.h:2790:16: 
> error: argument 1 range [2147483649, 4294967295] exceeds maximum object size 
> 2147483647 [-Werror=alloc-size-larger-than=]
>  2790 | _Ty* ptr = new (std::nothrow) _Ty[numElements]();
>   |^
> In file included from /usr/include/c++/12/bits/exception_ptr.h:40,
>  from /usr/include/c++/12/exception:168,
>  from /usr/include/c++/12/ios:39,
>  from /usr/include/c++/12/ostream:38,
>  from /usr/include/c++/12/iostream:39,
>  from 
> /<>/media_driver/linux/common/cm/hal/cm_def_os.h:34:
> /usr/include/c++/12/new: In member function ‘virtual int32_t 
> CmKernelEx::Initialize(const char*, const char*)’:
> /usr/include/c++/12/new:142:26: note: in a call to allocation function ‘void* 
> operator new [](std::size_t, const std::nothrow_t&)’ declared here
>   142 | _GLIBCXX_NODISCARD void* operator new[](std::size_t, const 
> std::nothrow_t&) _GLIBCXX_USE_NOEXCEPT
>   |  ^~~~

Forwarded upstream.

Cheers
-- 
Sebastian Ramacher

Processed: gnome-user-share: Drop nautilus extension

[Debian Bug Tracking System]

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

> severity 1014933 important
Bug #1014933 [src:gnome-user-share] gnome-user-share: needs to be ported to gtk4
Severity set to 'important' from 'serious'
> retitle 1014933 gnome-user-share: Drop nautilus extension
Bug #1014933 [src:gnome-user-share] gnome-user-share: needs to be ported to gtk4
Changed Bug title to 'gnome-user-share: Drop nautilus extension' from 
'gnome-user-share: needs to be ported to gtk4'.
>
End of message, stopping processing here.

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

Bug#1016982: rails: CVE-2022-27777

[Moritz Mühlenhoff]

Source: rails
X-Debbugs-CC: t...@security.debian.org
Severity: grave
Tags: security

Hi,

The following vulnerability was published for rails.

CVE-2022-2[0]:
| A XSS Vulnerability in Action View tag helpers = 5.2.0 and 
| 5.2.0 which would allow an attacker to inject content if able to
| control input into specific attributes.

Fixed by: 
https://github.com/rails/rails/commit/123f42a573f7fcbf391885c135ca809f21615180 
(v6.1.5.1)
Regression fix: 
https://github.com/rails/rails/commit/7c2da9e51c5c02643f30d83aaad3ed5062adcad8 
(6.1.6)

Fixed by: 
https://github.com/rails/rails/commit/36a6dad07d572a0098c29d6d96a226638a7caa38 
(v6.0.4.8)
Regression fix: 
https://github.com/rails/rails/commit/1b5df893d82a27da907e9b8b75deff13179d1df3 
(v6.0.5)

If you fix the vulnerability please also make sure to include the
CVE (Common Vulnerabilities & Exposures) id in your changelog entry.

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2022-2
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-2

Please adjust the affected versions in the BTS as needed.

Processed: Re: Bug#1016953: intel-media-driver: FTBFS on i386: error: format ‘%lu’ expects argument of type ‘long unsigned int’, but argument 3 has type ‘uint64_t’

[Debian Bug Tracking System]

Processing control commands:

> tags -1 - patch
Bug #1016953 [src:intel-media-driver] intel-media-driver: FTBFS on i386: error: 
format ‘%lu’ expects argument of type ‘long unsigned int’, but argument 3 has 
type ‘uint64_t’
Removed tag(s) patch.

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

Bug#1016953: intel-media-driver: FTBFS on i386: error: format ‘%lu’ expects argument of type ‘long unsigned int’, but argument 3 has type ‘uint64_t’

[Simon McVittie]

Control: tags -1 - patch

On Wed, 10 Aug 2022 at 20:55:44 +0100, Simon McVittie wrote:
> Yes, that seems to work.

Sorry, no, that change is not sufficient. I also get:

In file included from 
/<>/media_common/agnostic/common/os/mos_os.h:31,
 from 
/<>/media_driver/agnostic/common/os/mos_context.h:30,
 from 
/<>/media_driver/linux/common/ddi/media_libva_common.h:37,
 from 
/<>/media_driver/linux/common/cm/ddi/media_libva_cm.h:30,
 from 
/<>/media_driver/linux/common/cm/hal/cm_def_os.h:41,
 from 
/<>/media_driver/agnostic/common/cm/cm_def.h:30,
 from 
/<>/media_driver/agnostic/common/cm/cm_kernel.h:30,
 from 
/<>/media_driver/agnostic/common/cm/cm_kernel_rt.h:30,
 from 
/<>/media_driver/agnostic/common/cm/cm_kernel_ex.h:28,
 from 
/<>/media_driver/agnostic/common/cm/cm_kernel_ex.cpp:27:
In static member function ‘static _Ty* MosUtilities::MosNewArrayUtil(size_t) 
[with _Ty = unsigned char; _Types = {}]’,
inlined from ‘virtual int32_t CmKernelEx::Initialize(const char*, const 
char*)’ at 
/<>/media_driver/agnostic/common/cm/cm_kernel_ex.cpp:192:22,
inlined from ‘virtual int32_t CmKernelEx::Initialize(const char*, const 
char*)’ at 
/<>/media_driver/agnostic/common/cm/cm_kernel_ex.cpp:70:9:
/<>/media_softlet/agnostic/common/os/mos_utilities.h:2790:16: 
error: argument 1 range [2147483649, 4294967295] exceeds maximum object size 
2147483647 [-Werror=alloc-size-larger-than=]
 2790 | _Ty* ptr = new (std::nothrow) _Ty[numElements]();
  |^
In file included from /usr/include/c++/12/bits/exception_ptr.h:40,
 from /usr/include/c++/12/exception:168,
 from /usr/include/c++/12/ios:39,
 from /usr/include/c++/12/ostream:38,
 from /usr/include/c++/12/iostream:39,
 from 
/<>/media_driver/linux/common/cm/hal/cm_def_os.h:34:
/usr/include/c++/12/new: In member function ‘virtual int32_t 
CmKernelEx::Initialize(const char*, const char*)’:
/usr/include/c++/12/new:142:26: note: in a call to allocation function ‘void* 
operator new [](std::size_t, const std::nothrow_t&)’ declared here
  142 | _GLIBCXX_NODISCARD void* operator new[](std::size_t, const 
std::nothrow_t&) _GLIBCXX_USE_NOEXCEPT
  |  ^~~~

Bug#1016976: connman: CVE-2022-32292 CVE-2022-32293

[Moritz Mühlenhoff]

Source: connman
X-Debbugs-CC: t...@security.debian.org
Severity: grave
Tags: security

Hi,

The following vulnerabilities were published for connman.

CVE-2022-32292[0]:
| In ConnMan through 1.41, remote attackers able to send HTTP requests
| to the gweb component are able to exploit a heap-based buffer overflow
| in received_data to execute code.

https://lore.kernel.org/connman/20220801080043.4861-5-w...@monom.org/
https://bugzilla.suse.com/show_bug.cgi?id=1200189

CVE-2022-32293[1]:
| In ConnMan through 1.41, a man-in-the-middle attack against a WISPR
| HTTP query could be used to trigger a use-after-free in WISPR
| handling, leading to crashes or code execution.

https://lore.kernel.org/connman/20220801080043.4861-1-w...@monom.org/
https://lore.kernel.org/connman/20220801080043.4861-3-w...@monom.org/
https://bugzilla.suse.com/show_bug.cgi?id=1200190

If you fix the vulnerabilities please also make sure to include the
CVE (Common Vulnerabilities & Exposures) ids in your changelog entry.

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2022-32292
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-32292
[1] https://security-tracker.debian.org/tracker/CVE-2022-32293
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-32293

Please adjust the affected versions in the BTS as needed.

Bug#1016978: frr: CVE-2022-37035

[Moritz Mühlenhoff]

Source: frr
X-Debbugs-CC: t...@security.debian.org
Severity: grave
Tags: security

Hi,

The following vulnerability was published for frr.

CVE-2022-37035[0]:
| An issue was discovered in bgpd in FRRouting (FRR) 8.3. In
| bgp_notify_send_with_data() and bgp_process_packet() in bgp_packet.c,
| there is a possible use-after-free due to a race condition. This could
| lead to Remote Code Execution or Information Disclosure by sending
| crafted BGP packets. User interaction is not needed for exploitation.

https://github.com/FRRouting/frr/issues/11698

If you fix the vulnerability please also make sure to include the
CVE (Common Vulnerabilities & Exposures) id in your changelog entry.

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2022-37035
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-37035

Please adjust the affected versions in the BTS as needed.

Bug#1016974: sofia-sip: CVE-2022-31001 CVE-2022-31002 CVE-2022-31003

[Moritz Mühlenhoff]

Source: sofia-sip
X-Debbugs-CC: t...@security.debian.org
Severity: grave
Tags: security

Hi,

The following vulnerabilities were published for sofia-sip.

CVE-2022-31001[0]:
| Sofia-SIP is an open-source Session Initiation Protocol (SIP) User-
| Agent library. Prior to version 1.13.8, an attacker can send a message
| with evil sdp to FreeSWITCH, which may cause crash. This type of crash
| may be caused by `#define MATCH(s, m) (strncmp(s, m, n = sizeof(m) -
| 1) == 0)`, which will make `n` bigger and trigger out-of-bound access
| when `IS_NON_WS(s[n])`. Version 1.13.8 contains a patch for this
| issue.

https://github.com/freeswitch/sofia-sip/security/advisories/GHSA-79jq-hh82-cv9g
https://github.com/freeswitch/sofia-sip/commit/a99804b336d0e16d26ab7119d56184d2d7110a36
 (v1.13.8)

CVE-2022-31002[1]:
| Sofia-SIP is an open-source Session Initiation Protocol (SIP) User-
| Agent library. Prior to version 1.13.8, an attacker can send a message
| with evil sdp to FreeSWITCH, which may cause a crash. This type of
| crash may be caused by a URL ending with `%`. Version 1.13.8 contains
| a patch for this issue.

https://github.com/freeswitch/sofia-sip/security/advisories/GHSA-g3x6-p824-x6hm
https://github.com/freeswitch/sofia-sip/commit/51841eb53679434a386fb2dcbca925dcc48d58ba
 (v1.13.8)

CVE-2022-31003[2]:
| Sofia-SIP is an open-source Session Initiation Protocol (SIP) User-
| Agent library. Prior to version 1.13.8, when parsing each line of a
| sdp message, `rest = record + 2` will access the memory behind `\0`
| and cause an out-of-bounds write. An attacker can send a message with
| evil sdp to FreeSWITCH, causing a crash or more serious consequence,
| such as remote code execution. Version 1.13.8 contains a patch for
| this issue.

https://github.com/freeswitch/sofia-sip/security/advisories/GHSA-8w5j-6g2j-pxcp
https://github.com/freeswitch/sofia-sip/commit/907f2ac0ee504c93ebfefd676b4632a3575908c9
 (v1.13.8)

If you fix the vulnerabilities please also make sure to include the
CVE (Common Vulnerabilities & Exposures) ids in your changelog entry.

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2022-31001
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-31001
[1] https://security-tracker.debian.org/tracker/CVE-2022-31002
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-31002
[2] https://security-tracker.debian.org/tracker/CVE-2022-31003
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-31003

Please adjust the affected versions in the BTS as needed.

Bug#1016972: php8.1: CVE-2022-31627

[Moritz Mühlenhoff]

Source: php8.1
X-Debbugs-CC: t...@security.debian.org
Severity: grave
Tags: security

Hi,

The following vulnerability was published for php8.1.

It's specific to 8.1.x

CVE-2022-31627[0]:
| In PHP versions 8.1.x below 8.1.8, when fileinfo functions, such as
| finfo_buffer, due to incorrect patch applied to the third party code
| from libmagic, incorrect function may be used to free allocated
| memory, which may lead to heap corruption.

PHP Bug: https://bugs.php.net/bug.php?id=81723
https://github.com/php/php-src/commit/ca6d511fa54b34d5b75bf120a86482a1b9e1e686


If you fix the vulnerability please also make sure to include the
CVE (Common Vulnerabilities & Exposures) id in your changelog entry.

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2022-31627
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-31627

Please adjust the affected versions in the BTS as needed.

Bug#1016953: intel-media-driver: FTBFS on i386: error: format ‘%lu’ expects argument of type ‘long unsigned int’, but argument 3 has type ‘uint64_t’

[Simon McVittie]

Control: tags -1 + patch

On Wed, 10 Aug 2022 at 15:07:09 +0100, Simon McVittie wrote:
> The solution might be as simple as including  or ,
> and using "%" PRIu64 instead of "%lu".

Yes, that seems to work.

smcv
From: Simon McVittie 
Date: Wed, 10 Aug 2022 14:49:50 +0100
Subject: media_softlet: Use PRIu64 to print 64-bit integer

%lu is appropriate for a 64-bit integer on x86_64, but not on IA32.

Bug-Debian: https://bugs.debian.org/1016953
Signed-off-by: Simon McVittie 
---
 media_softlet/linux/common/os/osservice/mos_utilities_specific.cpp | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/media_softlet/linux/common/os/osservice/mos_utilities_specific.cpp b/media_softlet/linux/common/os/osservice/mos_utilities_specific.cpp
index bd1c5d1..fdd81ed 100644
--- a/media_softlet/linux/common/os/osservice/mos_utilities_specific.cpp
+++ b/media_softlet/linux/common/os/osservice/mos_utilities_specific.cpp
@@ -28,6 +28,7 @@
 #include // atoi
 #include // strlen, strcat, etc.
 #include  // strerror(errno)
+#include   // PRIu64
 #include   // get_clocktime
 #include  // dlopen, dlsym, dlclose
 #include 
@@ -1020,7 +1021,7 @@ MOS_STATUS MosUtilitiesSpecificNext::UserFeatureDumpDataToFile(const char *szFil
 *(uint32_t*)(pKeyTmp->pElem->pValueArray[j].ulValueBuf));
 break;
 case UF_QWORD:
-fprintf(File, "\t\t\t%lu\n",
+fprintf(File, "\t\t\t%" PRIu64 "\n",
 *(uint64_t*)(pKeyTmp->pElem->pValueArray[j].ulValueBuf));
 break;
 default:

Processed: Re: Bug#1016953: intel-media-driver: FTBFS on i386: error: format ‘%lu’ expects argument of type ‘long unsigned int’, but argument 3 has type ‘uint64_t’

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + patch
Bug #1016953 [src:intel-media-driver] intel-media-driver: FTBFS on i386: error: 
format ‘%lu’ expects argument of type ‘long unsigned int’, but argument 3 has 
type ‘uint64_t’
Added tag(s) patch.

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

Bug#1013939: marked as done (python-xarray: autopkgtest regression: Left and right DataArray objects are not close)

[Debian Bug Tracking System]

Your message dated Wed, 10 Aug 2022 18:49:27 +
with message-id 
and subject line Bug#1013939: fixed in python-xarray 2022.06.0-2
has caused the Debian Bug report #1013939,
regarding python-xarray: autopkgtest regression: Left and right DataArray 
objects are not close
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.)


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

Source: python-xarray
Version: 2022.06.0~rc1-1
Severity: serious
User: debian...@lists.debian.org
Usertags: regression

Dear maintainer(s),

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


   passfail
python-xarray  from testing2022.06.0~rc1-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=python-xarray

https://ci.debian.net/data/autopkgtest/testing/amd64/p/python-xarray/23134419/log.gz

=== FAILURES 
===
___ test_weighted_operations_nonequal_coords 
___


def test_weighted_operations_nonequal_coords():
# There are no weights for a == 4, so that data point is ignored.
weights = DataArray(np.random.randn(4), dims=("a",), 
coords=dict(a=[0, 1, 2, 3]))
data = DataArray(np.random.randn(4), dims=("a",), 
coords=dict(a=[1, 2, 3, 4]))

check_weighted_operations(data, weights, dim="a", skipna=None)
q = 0.5
result = data.weighted(weights).quantile(q, dim="a")
# Expected value computed using code from 
https://aakinshin.net/posts/weighted-quantiles/ with values at a=1,2,3
expected = DataArray([0.9308707], coords={"quantile": 
[q]}).squeeze()

  assert_allclose(result, expected)

E   AssertionError: Left and right DataArray objects are not close
E   E   Differing values:
E   L
E   array(-0.289754)
E   R
E   array(0.930871)

/usr/lib/python3/dist-packages/xarray/tests/test_weighted.py:667: 
AssertionError


OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: python-xarray
Source-Version: 2022.06.0-2
Done: Alastair McKinstry 

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

Debian distribution maintenance software
pp.
Alastair McKinstry  (supplier of updated python-xarray 
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, 10 Aug 2022 17:51:26 +0100
Source: python-xarray
Architecture: source
Version: 2022.06.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Alastair McKinstry 
Closes: 1013939
Changes:
 python-xarray (2022.06.0-2) unstable; urgency=medium
 .
   * Update  no-installer.patch to avoid accidentally claiming we're
still at 0.16.1; this was breaking cfgrib
   * Temporarily drop zarr support as it segfaults tests
   * Temporarily drop rasterio support as python3-rasterio can't find
 proj.db in tests
   * Drop bottleneck patch; 1.3.2 now in Debian
   * Bug fixed in recent upload: Closes: #1013939
Checksums-Sha1:
 5dfc97d56f07955a94b082c389577c832634c5a7 3345 python-xarray_2022.06.0-2.dsc
 e2e6ee7fd6f998fc6051205f3dc9ec26630f4626 13800 
python-xarray_2022.06.0-2.debian.tar.xz
Checksums-Sha256:
 c5fd2611897c690c73563d13d75e90a5e7ed7162c2b1bf11357129a5cf370942 3345 
python-xarray_2022.06.0-2.dsc
 

Bug#1016574: marked as done (adduser: dpkg conffile prompt for adduser.conf even though unmodified)

[Debian Bug Tracking System]

Your message dated Wed, 10 Aug 2022 18:04:50 +
with message-id 
and subject line Bug#1016574: fixed in adduser 3.126
has caused the Debian Bug report #1016574,
regarding adduser: dpkg conffile prompt for adduser.conf even though unmodified
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.)


-- 
1016574: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1016574
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: autopkgtest
Version: 5.22
Severity: minor
X-Debbugs-Cc: ja...@oneway.dev

Hi,

Severity: minor because this is probably an exotic corner case. I'm
filing this anyway becuse it is probably easily fixed.

I'm on the adduser team. Adduser is part of the minimal install and is
therefore installed in every environment that autopkgtest is run in. In
current experimental, adduser has migrated /etc/adduser.conf to being an
dpkg-conffile. Before that, adduser.conf was kind of "managed" in
postinst.

adduser.conf suddenly becoming a dpkg-conffile causes dpkg to emit a
conffile prompt in every case of adduser <= 3.123 being updated to
adduse >= 3.125.

This also happens when the newly built adduser.deb gets installed during
autopkgtest. The autopkgtest run stalls in this case and needs manual
intervention to continue.

Is this autopkgtest's intended behavior? If not, would passing
--force-confnew to dpkg solve this issue?

This most probably only happens iff:

- the package in test is already part of the base install AND
- the package in test has recently changed a maintainer-managed
  configuration file to being a dpkg-conffile.

Since this is probably exotic, I'm holding off uploading a new version
of adduser to unstable until Friday Aug 5 to give you a chance to
reproduce this behavior. Let me know when I can upload earlier please.

I am setting Jason Franklin, my team colleague who investgated this in
depth, as Cc so that he can give additional information that I might
have forgotten.

Greetings
Marc
--- End Message ---
--- Begin Message ---
Source: adduser
Source-Version: 3.126
Done: Marc Haber 

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

Debian distribution maintenance software
pp.
Marc Haber  (supplier of updated adduser 
package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 09 Aug 2022 15:19:57 +0200
Source: adduser
Architecture: source
Version: 3.126
Distribution: experimental
Urgency: medium
Maintainer: Debian Adduser Developers 
Changed-By: Marc Haber 
Closes: 1016574
Changes:
 adduser (3.126) experimental; urgency=medium
 .
   * more clear conffile handling in debian/preinst.
 Thanks to Simon McVittie (Closes: #1016574)
   * add postrm script cleaning up better after purge
   * add a Debian README, move too long DIR_MODE explanation from
 NEWS.Debian to README.
Checksums-Sha1:
 ad8927dc0b4943db5f41e8dc19d6cf83c64e2b18 1671 adduser_3.126.dsc
 ae0d4bc5e40b745981cd64911f0779a774dbd366 227784 adduser_3.126.tar.xz
 26e9ccd1ac63693dd2824412a984c859f249816c 5683 adduser_3.126_source.buildinfo
Checksums-Sha256:
 22edf211f553dd048e65c40767607da9ffa28f029207411cd7c86f9e7acd8084 1671 
adduser_3.126.dsc
 7be4c52bcbab85ad6ef5dbdd0601f79f547159613d3b1476b573a076a902327f 227784 
adduser_3.126.tar.xz
 3a4efd60b162679462a4b777449af628f64b30e86fce1ec1ffc429eaaf7a86a0 5683 
adduser_3.126_source.buildinfo
Files:
 3feb55f7561296742875aa452319dc3a 1671 admin important adduser_3.126.dsc
 9ded5d2052ea601cebd4520d275fca02 227784 admin important adduser_3.126.tar.xz
 87c71ac96b6984a0a781e288f5a0189b 5683 admin important 
adduser_3.126_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEE6QL5UJ/L0pcuNEbjj3cgEwEyBEIFAmLz8EoACgkQj3cgEwEy
BEL3JhAAwVG9zOWqXOQ1UUXPrHBy4kQhBZ7dARrQFPao0Sm0+hydsopuuJY8Xvfs
v5jdIvSg4Cl0+hYAOsne+9OPlkyCHrL44ydNwdOvboVpArVAHbN9i9Vas8ybAT7V
I9d+xookjPdzVES7dhhmSNmbn4/xmYIgXNzFAb5ZjisEFM+t/OD0wFr7CFGG+7bC
q/b+To6Pxqp63RPLe+2wSZ9kEzCxFrAsHRzSIDzSJIpoy2WF8T7uc5syd91mKl2W
omv+LpIpZiHkq/ISy8zTnB5I8TMIWGjtGnm4Sm5+pc2SBgrLQQlKIZc2JhcqRWWz

Processed: tagging 937085

[Debian Bug Tracking System]

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

> tags 937085 + patch
Bug #937085 [src:mozilla-devscripts] mozilla-devscripts: Python2 removal in 
sid/bullseye
Added tag(s) patch.
> thanks
Stopping processing here.

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

Bug#1016732: node-sockjs throws: TypeError: Cannot read properties of undefined (reading 'addEventListener') at WebSocketReceiver.setUp

[Nilesh Patra]

Hi,

Sorry to bother you over this again, but would you have any idea?
I'd be OK with a workaround if you don't have the bandwidth at the moment, but 
this
seems to come from coffee related modifications only.

On Sun, 7 Aug 2022 11:42:45 +0530 Nilesh Patra  wrote:
> On 8/7/22 11:04 AM, Yadd wrote:
> > On 06/08/2022 14:59, Nilesh Patra wrote:
> >> Yadd,
> >>
> >> Since you added in coffeescript patch for this package, I'd highly 
> >> appreciate if
> >> you could consider taking a look.
> > 
> > Hi,
> > 
> > is there a test somewhere to see this error ?
> 
> I'm not aware of any specific test that could trigger this code 
> unfortunately, but I can reproduce
> it on running shiny-server.
> (Sorry for the long procedure)
> 
> | # apt install shiny-server
> | # cd /srv
> | # mkdir -p shiny-server
> | # cd shiny-server
> | # mkdir covid
> | # cd covid
> | # wget 
> https://raw.githubusercontent.com/eebrown/covidprobability_shiny/main/app.R
> | # R -e 'install.packages(c("covidprobability", "shinyjs"))'
> | # # Start shiny server
> | # shiny-server
> |
> |  ===> This will start on localhost:3838. Migrate to localhost:3838/covid, 
> click on any of the bars and you will see this on terminal
> |
> | [2022-08-06T23:03:16.777] [INFO] shiny-server - Shiny Server v1.5.19.0 
> (Node.js v18.6.0)
> | [2022-08-06T23:03:16.779] [INFO] shiny-server - Using config file 
> "/etc/shiny-server/shiny-server.conf"
> | [2022-08-06T23:03:16.830] [WARN] shiny-server - Running as root 
> unnecessarily is a security risk! You could be running more securely as 
> non-root.
> | [2022-08-06T23:03:16.836] [INFO] shiny-server - Starting listener on 
> http://[::]:3838
> | [2022-08-06T23:03:33.825] [ERROR] shiny-server - Uncaught exception: 
> TypeError: Cannot read properties of undefined (reading 'addEventListener')
> | [2022-08-06T23:03:33.829] [ERROR] shiny-server - TypeError: Cannot read 
> properties of undefined (reading 'addEventListener')
> | at WebSocketReceiver.setUp 
> (/usr/share/nodejs/sockjs/lib/trans-websocket.js:76:24)
> | at new GenericReceiver (/usr/share/nodejs/sockjs/lib/transport.js:313:12)
> | at new WebSocketReceiver 
> (/usr/share/nodejs/sockjs/lib/trans-websocket.js:63:9)
> | at ws.onopen (/usr/share/nodejs/sockjs/lib/trans-websocket.js:31:55)
> | at WebSocket.dispatchEvent 
> (/usr/share/nodejs/faye-websocket/lib/faye/websocket/api/event_target.js:24:30)
> | at WebSocket._open 
> (/usr/share/nodejs/faye-websocket/lib/faye/websocket/api.js:144:10)
> | at Hybi. 
> (/usr/share/nodejs/faye-websocket/lib/faye/websocket/api.js:35:49)
> | at Hybi.emit (node:events:513:28)
> | at Hybi._open 
> (/usr/share/nodejs/websocket-driver/lib/websocket/driver/base.js:148:10)
> | at Hybi.start 
> (/usr/share/nodejs/websocket-driver/lib/websocket/driver/base.js:105:34)
> | [2022-08-06T23:03:33.839] [INFO] shiny-server - Stopping listener on 
> http://[::]:3838
> | [2022-08-06T23:03:33.839] [INFO] shiny-server - Shutting down worker 
> processes (with notification)
> | /usr/lib/shiny-server/lib/main.js:391
> |   throw err;
> |   ^
> |
> | TypeError: Cannot read properties of undefined (reading 'addEventListener')
> | at WebSocketReceiver.setUp 
> (/usr/share/nodejs/sockjs/lib/trans-websocket.js:76:24)
> | at new GenericReceiver (/usr/share/nodejs/sockjs/lib/transport.js:313:12)
> | at new WebSocketReceiver 
> (/usr/share/nodejs/sockjs/lib/trans-websocket.js:63:9)
> | at ws.onopen (/usr/share/nodejs/sockjs/lib/trans-websocket.js:31:55)
> | at WebSocket.dispatchEvent 
> (/usr/share/nodejs/faye-websocket/lib/faye/websocket/api/event_target.js:24:30)
> | at WebSocket._open 
> (/usr/share/nodejs/faye-websocket/lib/faye/websocket/api.js:144:10)
> | at Hybi. 
> (/usr/share/nodejs/faye-websocket/lib/faye/websocket/api.js:35:49)
> | at Hybi.emit (node:events:513:28)
> | at Hybi._open 
> (/usr/share/nodejs/websocket-driver/lib/websocket/driver/base.js:148:10)

-- 
Best,
Nilesh


signature.asc
Description: PGP signature

Bug#1016963: u-boot: delay migration to testing to test more platforms

[Vagrant Cascadian]

Source: u-boot
Version: 2022.07+dfsg-1
Severity: serious
X-Debbugs-Cc: Vagrant Cascadian 

This bug is just to delay migration to testing while more platforms get
tested. If you have a relevent board, please consider testing and
reporting the status:

  https://wiki.debian.org/U-boot/Status

live well,
  vagrant


signature.asc
Description: PGP signature

Bug#1012996: mes: ftbfs with GCC-12

[Vagrant Cascadian]

Control: severity 1012996 important

On 2022-07-22, Vagrant Cascadian wrote:
> Looks like mes 0.24 test suite failed with GCC-12?
>
> I have not yet tried to reproduce it myself, but this is a bigger issue
> now that GCC-12 is the default compiler in Debian.

Yup, definitely fails with gcc-12.

I've uploaded 0.24-2 to Debian which uses gcc-11 to work around the
problem for now; downgrading the severity accordingly.


live well,
  vagrant


signature.asc
Description: PGP signature

Processed: Re: Bug#1012996: mes: ftbfs with GCC-12

[Debian Bug Tracking System]

Processing control commands:

> severity 1012996 important
Bug #1012996 [src:mes] mes: ftbfs with GCC-12
Severity set to 'important' from 'serious'

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

Bug#1016960: nautilus-python: Doesn't work with nautilus 43

[Jeremy Bicha]

Source: nautilus-python
Severity: serious
Version: 1.2.3-3.1
Forwarded: https://gitlab.gnome.org/GNOME/nautilus-python/-/merge_requests/9

nautilus-python doesn't work with nautilus 43. Sadly, nautilus-python
looks unmaintained upstream so it's unclear when this issue will be
resolved.

nautilus 43 is a major upgrade. It switched to GTK4. The extension API
had major changes.

Nautilus 43 is available in Debian experimental. However, it may be
difficult to install because it uses gnome-desktop 43 and you'll need
everything you're using to be built against gnome-desktop 43 also.
Perhaps the easiest way to handle this if you don't want to wait for
the gnome-desktop transition to begin is to revert 4420025 in nautilus
and the corresponding bump in debian/control.in and rebuild nautilus.

Thank you,
Jeremy Bicha

Processed: Re: Bug#1016224: binutils-z80: FTBFS: stdlib.h:134:10: error: argument 1 is null but the corresponding size argument 3 value is [128, 9223372036854775807] [-Werror=nonnull]

[Debian Bug Tracking System]

Processing control commands:

> tags -1 fixed-upstream
Bug #1016224 [src:binutils-z80] binutils-z80: FTBFS: stdlib.h:134:10: error: 
argument 1 is null but the corresponding size argument 3 value is [128, 
9223372036854775807] [-Werror=nonnull]
Added tag(s) fixed-upstream.

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

Bug#1016224: binutils-z80: FTBFS: stdlib.h:134:10: error: argument 1 is null but the corresponding size argument 3 value is [128, 9223372036854775807] [-Werror=nonnull]

[Alberto Garcia]

Control: tags -1 fixed-upstream

On Fri, Jul 29, 2022 at 06:20:14PM +0200, Lucas Nussbaum wrote:

> During a rebuild of all packages in sid, your package failed to build
> on amd64.

> > In function ‘mbstowcs’,
> > inlined from ‘read_symbol_name’ at read.c:1670:11:
> > /usr/include/x86_64-linux-gnu/bits/stdlib.h:134:10: error: argument 1 is 
> > null but the corresponding size argument 3 value is [128, 
> > 9223372036854775807] [-Werror=nonnull]
> >   134 |   return __mbstowcs_alias (__dst, __src, __len);
> >   |  ^~

Hi,

this has been fixed in binutils upstream, is the normal binutils
package not affected?

   
https://sourceware.org/git/?p=binutils-gdb.git;a=commitdiff;h=5858ac626e548772407c038b09b7837550b127dd

I can fix this in binutils-z80 but I'd rather have the fix in the
binutils-source package directly.

Berto

Bug#1014488: marked as done (scapy: flaky autopkgtest: No such file or directory: 'isotpsend')

[Debian Bug Tracking System]

Your message dated Wed, 10 Aug 2022 14:37:37 +
with message-id 
and subject line Bug#1014488: fixed in scapy 2.4.4-5
has caused the Debian Bug report #1014488,
regarding scapy: flaky autopkgtest: No such file or directory: 'isotpsend'
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.)


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

Source:  scapy
Version: 2.4.4-4
Severity: serious
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: flaky

Dear maintainer(s),

I looked at the results of the autopkgtest of you package on arm64 
because it was showing up as a regression for the upload of openssl. I 
noticed that the test regularly fails and I saw failures on other 
architectures too, even in stable.


Because the unstable-to-testing migration software now blocks on
regressions in testing, flaky tests, i.e. tests that flip between
passing and failing without changes to the list of installed packages,
are causing people unrelated to your package to spend time on these
tests.

Don't hesitate to reach out if you need help and some more information
from our infrastructure.

Paul

https://ci.debian.net/packages/s/scapy/

https://ci.debian.net/data/autopkgtest/testing/amd64/s/scapy/23043408/log.gz

###(006)=[failed] Check if can-isotp and can-utils are installed on this 
system


>>> p1 = subprocess.Popen(['lsmod'], stdout = subprocess.PIPE)
>>> p2 = subprocess.Popen(['grep', '^can_isotp'], stdout = 
subprocess.PIPE, stdin=p1.stdout)

>>> p1.stdout.close()
>>> if p1.wait() == 0 and p2.wait() == 0 and b"can_isotp" in 
p2.stdout.read():
... p = subprocess.Popen(["isotpsend", "-s1", "-d0", iface0], stdin 
= subprocess.PIPE)

... p.communicate(b"01")
... if p.returncode == 0:
... ISOTP_KERNEL_MODULE_AVAILABLE = True
...
Traceback (most recent call last):
  File "", line 3, in 
  File "/usr/lib/python3.10/subprocess.py", line 969, in __init__
self._execute_child(args, executable, preexec_fn, close_fds,
  File "/usr/lib/python3.10/subprocess.py", line 1845, in _execute_child
raise child_exception_type(errno_num, err_msg, err_filename)
FileNotFoundError: [Errno 2] No such file or directory: 'isotpsend'


sys:1: ResourceWarning: unclosed file <_io.BufferedReader name=9>


OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: scapy
Source-Version: 2.4.4-5
Done: Neil Williams 

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

Debian distribution maintenance software
pp.
Neil Williams  (supplier of updated scapy package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 09 Aug 2022 13:11:48 +0100
Source: scapy
Architecture: source
Version: 2.4.4-5
Distribution: unstable
Urgency: medium
Maintainer: Debian Security Tools 
Changed-By: Neil Williams 
Closes: 1014488
Changes:
 scapy (2.4.4-5) unstable; urgency=medium
 .
   * Team upload.
   * Lintian brush updates
   * Fix d.watch file
   * Add can-utils package to autopkgtest dependencies. (Closes: #1014488)
   * Add the basic Python autopkgtest
   * Freshen existing patches
Checksums-Sha1:
 67e79aad927ae5b70fe17f92a478074ca5b7c156 2182 scapy_2.4.4-5.dsc
 16ef4e022a9db4d7ab27a7af460cbe0589ceeadd 20040 scapy_2.4.4-5.debian.tar.xz
 488e8ea111eb41deef1347dc68b09225eacba6da 8077 scapy_2.4.4-5_amd64.buildinfo
Checksums-Sha256:
 96f51e305fe9853c192315383973ecfe0e2053ae4896f52596ffbfab4a91 2182 
scapy_2.4.4-5.dsc
 2bfa87248a09cdd67f11f72473350aba770c132c7415afe54b0365e216aa2306 20040 
scapy_2.4.4-5.debian.tar.xz
 1f4178e2ab915333b416ac0da7b9053664d471ffbcc827fdf659f61146128db1 8077 
scapy_2.4.4-5_amd64.buildinfo
Files:
 c1d0dbe967b59264fa1ef810fef6ab54 2182 python optional scapy_2.4.4-5.dsc
 7f61c23797457d7bbbe1aa998bb74a55 20040 python optional 
scapy_2.4.4-5.debian.tar.xz
 bb91f14e98d2a1559534c299b9c999f7 8077 python optional 
scapy_2.4.4-5_amd64.buildinfo

-BEGIN PGP SIGNATURE-

Bug#1016953: intel-media-driver: FTBFS on i386: error: format ‘%lu’ expects argument of type ‘long unsigned int’, but argument 3 has type ‘uint64_t’

[Simon McVittie]

Source: intel-media-driver
Version: 22.5.1+dfsg1-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)

intel-media-driver failed to build on i386, breaking multiarch
co-installation of amd64 and i386 driver libraries.

https://buildd.debian.org/status/fetch.php?pkg=intel-media-driver=i386=22.5.1%2Bdfsg1-1=1659479611=0

/<>/media_softlet/linux/common/os/osservice/mos_utilities_specific.cpp:
 In static member function ‘static MOS_STATUS 
MosUtilitiesSpecificNext::UserFeatureDumpDataToFile(const char*, 
MOS_PUF_KEYLIST)’:
/<>/media_softlet/linux/common/os/osservice/mos_utilities_specific.cpp:1023:44:
 error: format ‘%lu’ expects argument of type ‘long unsigned int’, but argument 
3 has type ‘uint64_t’ {aka ‘long long unsigned int’} [-Werror=format=]
 1023 | fprintf(File, "\t\t\t%lu\n",
  |  ~~^
  ||
  |long unsigned int
  |  %llu
 1024 | 
*(uint64_t*)(pKeyTmp->pElem->pValueArray[j].ulValueBuf));
  | 
~~~
  | |
  | uint64_t {aka long long unsigned int}

The solution might be as simple as including  or ,
and using "%" PRIu64 instead of "%lu". I'm testing that now.

smcv

Bug#998499: marked as done (jekyll: FTBFS: ERROR: Test "ruby3.0" failed.)

[Debian Bug Tracking System]

Your message dated Wed, 10 Aug 2022 15:30:26 +0200
with message-id 

and subject line jekyll: FTBFS: ERROR: Test "ruby3.0" failed.
has caused the Debian Bug report #998499,
regarding jekyll: FTBFS: ERROR: Test "ruby3.0" failed.
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.)


-- 
998499: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998499
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: jekyll
Version: 3.9.0+dfsg-3
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211104 ftbfs-bookworm

Hi,

During a rebuild of all packages in sid, your package failed to build
on amd64.


Relevant part (hopefully):
> /usr/bin/ruby3.0 /usr/bin/gem2deb-test-runner
> 
> ┌──┐
> │ Checking Rubygems dependency resolution on ruby3.0  
>  │
> └──┘
> 
> GEM_PATH=/<>/debian/jekyll/usr/share/rubygems-integration/all:/var/lib/gems/3.0.0:/usr/local/lib/ruby/gems/3.0.0:/usr/lib/ruby/gems/3.0.0:/usr/lib/x86_64-linux-gnu/ruby/gems/3.0.0:/usr/share/rubygems-integration/3.0.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/3.0.0
>  ruby3.0 -e gem\ \"jekyll\"
> 
> ┌──┐
> │ Run tests for ruby3.0 from debian/ruby-tests.rake   
>  │
> └──┘
> 
> RUBYLIB=/<>/debian/jekyll/usr/lib/ruby/vendor_ruby:. 
> GEM_PATH=/<>/debian/jekyll/usr/share/rubygems-integration/all:/var/lib/gems/3.0.0:/usr/local/lib/ruby/gems/3.0.0:/usr/lib/ruby/gems/3.0.0:/usr/lib/x86_64-linux-gnu/ruby/gems/3.0.0:/usr/share/rubygems-integration/3.0.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/3.0.0
>  ruby3.0 -S rake -f debian/ruby-tests.rake
> /usr/bin/ruby3.0 -w -I"test" 
> /usr/lib/ruby/gems/3.0.0/gems/rake-13.0.3/lib/rake/rake_test_loader.rb 
> "test/test_ansi.rb" "test/test_cleaner.rb" "test/test_collections.rb" 
> "test/test_command.rb" "test/test_commands_serve.rb" 
> "test/test_commands_serve_servlet.rb" "test/test_configuration.rb" 
> "test/test_convertible.rb" "test/test_data_reader.rb" 
> "test/test_doctor_command.rb" "test/test_document.rb" "test/test_drop.rb" 
> "test/test_entry_filter.rb" "test/test_excerpt.rb" 
> "test/test_excerpt_drop.rb" "test/test_filters.rb" 
> "test/test_front_matter_defaults.rb" "test/test_generated_site.rb" 
> "test/test_kramdown.rb" "test/test_layout_reader.rb" 
> "test/test_liquid_extensions.rb" "test/test_liquid_renderer.rb" 
> "test/test_log_adapter.rb" "test/test_page.rb" 
> "test/test_page_without_a_file.rb" "test/test_path_sanitization.rb" 
> "test/test_plugin_manager.rb" "test/test_rdiscount.rb" 
> "test/test_redcarpet.rb" "test/test_regenerator.rb" 
> "test/test_related_posts.rb" "test/test_sass.rb" "test/test_site.rb" 
> "test/test_site_drop.rb" "test/test_static_file.rb" "test/test_tags.rb" 
> "test/test_url.rb" "test/test_utils.rb" -v
> # -
> # SPECS AND TESTS ARE RUNNING WITH WARNINGS OFF.
> # SEE: https://github.com/Shopify/liquid/issues/730
> # SEE: https://github.com/jekyll/jekyll/issues/4719
> # -
> 
> File does not exist: webrick
> 
> rake aborted!
> Command failed with status (1): [ruby -w -I"test" 
> /usr/lib/ruby/gems/3.0.0/gems/rake-13.0.3/lib/rake/rake_test_loader.rb 
> "test/test_ansi.rb" "test/test_cleaner.rb" "test/test_collections.rb" 
> "test/test_command.rb" "test/test_commands_serve.rb" 
> "test/test_commands_serve_servlet.rb" "test/test_configuration.rb" 
> "test/test_convertible.rb" "test/test_data_reader.rb" 
> "test/test_doctor_command.rb" "test/test_document.rb" "test/test_drop.rb" 
> "test/test_entry_filter.rb" "test/test_excerpt.rb" 
> "test/test_excerpt_drop.rb" "test/test_filters.rb" 
> "test/test_front_matter_defaults.rb" "test/test_generated_site.rb" 
> "test/test_kramdown.rb" "test/test_layout_reader.rb" 
> "test/test_liquid_extensions.rb" "test/test_liquid_renderer.rb" 
> "test/test_log_adapter.rb" "test/test_page.rb" 
> "test/test_page_without_a_file.rb" "test/test_path_sanitization.rb" 
> "test/test_plugin_manager.rb" "test/test_rdiscount.rb" 
> "test/test_redcarpet.rb" "test/test_regenerator.rb" 
> "test/test_related_posts.rb" "test/test_sass.rb" "test/test_site.rb" 
> 

Bug#1016951: intel-compute-runtime: FTBFS with GCC 12

[Andreas Beckmann]

Source: intel-compute-runtime
Version: 22.14.22890-2
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)

intel-compute-runtime started to FTBFS when GCC 12 was made the default
compiler:

In file included from /usr/include/c++/12/string:50,
 from 
/build/intel-compute-runtime-22.14.22890/shared/source/utilities/const_stringref.h:13,
 from 
/build/intel-compute-runtime-22.14.22890/shared/source/device_binary_format/ar/ar.h:10,
 from 
/build/intel-compute-runtime-22.14.22890/shared/source/device_binary_format/ar/ar_encoder.h:10,
 from 
/build/intel-compute-runtime-22.14.22890/shared/source/device_binary_format/ar/ar_encoder.cpp:8:
In static member function 'static _Tp* std::__copy_move<_IsMove, true, 
std::random_access_iterator_tag>::__copy_m(const _Tp*, const _Tp*, _Tp*) [with 
_Tp = unsigned char; bool _IsMove = true]',
inlined from '_OI std::__copy_move_a2(_II, _II, _OI) [with bool _IsMove = 
true; _II = unsigned char*; _OI = unsigned char*]' at 
/usr/include/c++/12/bits/stl_algobase.h:495:30,
inlined from '_OI std::__copy_move_a1(_II, _II, _OI) [with bool _IsMove = 
true; _II = unsigned char*; _OI = unsigned char*]' at 
/usr/include/c++/12/bits/stl_algobase.h:522:42,
inlined from '_OI std::__copy_move_a(_II, _II, _OI) [with bool _IsMove = 
true; _II = unsigned char*; _OI = unsigned char*]' at 
/usr/include/c++/12/bits/stl_algobase.h:529:31,
inlined from '_OI std::copy(_II, _II, _OI) [with _II = 
move_iterator; _OI = unsigned char*]' at 
/usr/include/c++/12/bits/stl_algobase.h:620:7,
inlined from 'static _ForwardIterator 
std::__uninitialized_copy::__uninit_copy(_InputIterator, _InputIterator, 
_ForwardIterator) [with _InputIterator = std::move_iterator; 
_ForwardIterator = unsigned char*]' at /usr/include/c++/12/bits/stl_unini
tialized.h:147:27,
inlined from '_ForwardIterator std::uninitialized_copy(_InputIterator, 
_InputIterator, _ForwardIterator) [with _InputIterator = move_iterator; _ForwardIterator = unsigned char*]' at 
/usr/include/c++/12/bits/stl_uninitialized.h:185:15,
inlined from '_ForwardIterator std::__uninitialized_copy_a(_InputIterator, 
_InputIterator, _ForwardIterator, allocator<_Tp>&) [with _InputIterator = 
move_iterator; _ForwardIterator = unsigned char*; _Tp = 
unsigned char]' at /usr/include/c++/12/bits/st
l_uninitialized.h:372:37,
inlined from '_ForwardIterator 
std::__uninitialized_move_if_noexcept_a(_InputIterator, _InputIterator, 
_ForwardIterator, _Allocator&) [with _InputIterator = unsigned char*; 
_ForwardIterator = unsigned char*; _Allocator = allocator]' at 
/usr/include/c++
/12/bits/stl_uninitialized.h:397:2,
inlined from 'void std::vector<_Tp, _Alloc>::_M_range_insert(iterator, 
_ForwardIterator, _ForwardIterator, std::forward_iterator_tag) [with 
_ForwardIterator = const unsigned char*; _Tp = unsigned char; _Alloc = 
std::allocator]' at /usr/include/c++/12/b
its/vector.tcc:801:9,
inlined from 'void std::vector<_Tp, _Alloc>::_M_insert_dispatch(iterator, 
_InputIterator, _InputIterator, std::__false_type) [with _InputIterator = const 
unsigned char*; _Tp = unsigned char; _Alloc = std::allocator]' 
at /usr/include/c++/12/bits/stl_vec
tor.h:1779:19,
inlined from 'std::vector<_Tp, _Alloc>::iterator std::vector<_Tp, 
_Alloc>::insert(const_iterator, _InputIterator, _InputIterator) [with 
_InputIterator = const unsigned char*;  = void; _Tp = 
unsigned char; _Alloc = std::allocator
]' at /usr/include/c++/12/bits/stl_vector.h:1481:22,
inlined from 'std::vector NEO::Ar::ArEncoder::encode() 
const' at 
/build/intel-compute-runtime-22.14.22890/shared/source/device_binary_format/ar/ar_encoder.cpp:58:15:
/usr/include/c++/12/bits/stl_algobase.h:431:30: error: 'void* 
__builtin_memcpy(void*, const void*, long unsigned int)' writing between 1 and 
18446744073709551615 bytes into a region of size 0 [-Werror=stringop-overflow=]
  431 | __builtin_memmove(__result, __first, sizeof(_Tp) * _Num);
  | ~^~~
In file included from 
/usr/include/x86_64-linux-gnu/c++/12/bits/c++allocator.h:33,
 from /usr/include/c++/12/bits/allocator.h:46,
 from /usr/include/c++/12/string:41:
In member function '_Tp* std::__new_allocator<_Tp>::allocate(size_type, const 
void*) [with _Tp = unsigned char]',
inlined from 'static _Tp* std::allocator_traits 
>::allocate(allocator_type&, size_type) [with _Tp = unsigned char]' at 
/usr/include/c++/12/bits/alloc_traits.h:464:28,
inlined from 'std::_Vector_base<_Tp, _Alloc>::pointer 
std::_Vector_base<_Tp, _Alloc>::_M_allocate(std::size_t) [with _Tp = unsigned 
char; _Alloc = std::allocator]' at 
/usr/include/c++/12/bits/stl_vector.h:378:33,
inlined from 'void std::vector<_Tp, _Alloc>::_M_range_insert(iterator, 
_ForwardIterator, _ForwardIterator, std::forward_iterator_tag) [with 

Bug#1012999: marked as done (msc-generator: ftbfs with GCC-12)

[Debian Bug Tracking System]

Your message dated Wed, 10 Aug 2022 13:53:17 +0200
with message-id <20220810115317.7snwni64u5mp3...@gpm.stappers.nl>
and subject line Avoiding removal from testing
has caused the Debian Bug report #1012999,
regarding msc-generator: ftbfs with GCC-12
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.)


-- 
1012999: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1012999
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:msc-generator
Version: 7.2.1-1
Severity: normal
Tags: sid bookworm
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-12

[This bug is targeted to the upcoming bookworm release]

Please keep this issue open in the bug tracker for the package it
was filed for.  If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-12/g++-12, but succeeds to build with gcc-11/g++-11. The
severity of this report will be raised before the bookworm release.

The full build log can be found at:
http://qa-logs.debian.net/2022/06/09/gcc12/msc-generator_7.2.1-1_unstable_gcc12.log
The last lines of the build log are at the end of this report.

To build with GCC 11, either set CC=gcc-11 CXX=g++-11 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t=experimental install g++ 

Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-11/porting_to.html

GCC 11 defaults to the GNU++17 standard.  If your package installs
header files in /usr/include, please don't work around C++17 issues
by choosing a lower C++ standard for the package build, but fix these
issues to build with the C++17 standard.

[...]
   } >version.h \
|| echo 'gen_version_h error: I need the version as 
[v].[.]'
make  all-am
make[5]: Entering directory 
'/<>/debian/build-gui/src/libcgencommon'
g++ -DPACKAGE_NAME=\"msc-generator\" -DPACKAGE_TARNAME=\"msc-generator\" 
-DPACKAGE_VERSION=\"7.2.1\" -DPACKAGE_STRING=\"msc-generator\ 7.2.1\" 
-DPACKAGE_BUGREPORT=\"tek...@gmail.com\" -DPACKAGE_URL=\"\" 
-DPACKAGE=\"msc-generator\" -DVERSION=\"7.2.1\" -DYYTEXT_POINTER=1 
-DHAVE_STDIO_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_INTTYPES_H=1 
-DHAVE_STDINT_H=1 -DHAVE_STRINGS_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_SYS_TYPES_H=1 
-DHAVE_UNISTD_H=1 -DSTDC_HEADERS=1 -I. -I../../../../src/libcgencommon  
-I../../../../src/libcgencommon -Wdate-time -D_FORTIFY_SOURCE=2 -DNDEBUG 
-std=c++20 -I/usr/include/cairo -I/usr/include/glib-2.0 
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/pixman-1 
-I/usr/include/uuid -I/usr/include/freetype2 -I/usr/include/libpng16 
-I/usr/include/graphviz   -Wall -Wextra -Wno-unused-parameter 
-Wno-missing-field-initializers -DYY_TYPEDEF_YY_SIZE_T -Dyy_size_t=ssize_t -g 
-O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security
  -c -o contour_distance.o ../../../../src/libcgencommon/contour_distance.cpp
g++ -DPACKAGE_NAME=\"msc-generator\" -DPACKAGE_TARNAME=\"msc-generator\" 
-DPACKAGE_VERSION=\"7.2.1\" -DPACKAGE_STRING=\"msc-generator\ 7.2.1\" 
-DPACKAGE_BUGREPORT=\"tek...@gmail.com\" -DPACKAGE_URL=\"\" 
-DPACKAGE=\"msc-generator\" -DVERSION=\"7.2.1\" -DYYTEXT_POINTER=1 
-DHAVE_STDIO_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_INTTYPES_H=1 
-DHAVE_STDINT_H=1 -DHAVE_STRINGS_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_SYS_TYPES_H=1 
-DHAVE_UNISTD_H=1 -DSTDC_HEADERS=1 -I. -I../../../../src/libcgencommon  
-I../../../../src/libcgencommon -Wdate-time -D_FORTIFY_SOURCE=2 -DNDEBUG 
-std=c++20 -I/usr/include/cairo -I/usr/include/glib-2.0 
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/pixman-1 
-I/usr/include/uuid -I/usr/include/freetype2 -I/usr/include/libpng16 
-I/usr/include/graphviz   -Wall -Wextra -Wno-unused-parameter 
-Wno-missing-field-initializers -DYY_TYPEDEF_YY_SIZE_T -Dyy_size_t=ssize_t -g 
-O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security
  -c -o contour_edge.o ../../../../src/libcgencommon/contour_edge.cpp
g++ -DPACKAGE_NAME=\"msc-generator\" -DPACKAGE_TARNAME=\"msc-generator\" 
-DPACKAGE_VERSION=\"7.2.1\" -DPACKAGE_STRING=\"msc-generator\ 7.2.1\" 
-DPACKAGE_BUGREPORT=\"tek...@gmail.com\" -DPACKAGE_URL=\"\" 
-DPACKAGE=\"msc-generator\" -DVERSION=\"7.2.1\" -DYYTEXT_POINTER=1 

Processed: Avoiding removal from testing (attempt)

[Debian Bug Tracking System]

Processing control commands:

> notfound -1 8.1-2
Bug #1012999 [src:msc-generator] msc-generator: ftbfs with GCC-12
Ignoring request to alter found versions of bug #1012999 to the same values 
previously set

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

Processed: Avoiding removal from testing (attempt)

[Debian Bug Tracking System]

Processing control commands:

> notfound -1 8.1-2
Bug #1012999 [src:msc-generator] msc-generator: ftbfs with GCC-12
Ignoring request to alter found versions of bug #1012999 to the same values 
previously set

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

Bug#1012999: Avoiding removal from testing (attempt)

[Geert Stappers]

Control: notfound -1 8.1-2

Hi,

This e-mail is (an attempt) to prevent
that msc-generator gets removed from testing.


Originally was the bugreport serverity normal
and had the request "leave it to us".

Later became the serverity "serious"

The "leave it us" is still a good thing.
Yes, I appriciate the work that "archive rebuild people" do.

But the unpredicable next rebuild run.

http://qa-logs.debian.net/2022/04/
Index of /2022/04
[ICO]   NameLast modified   SizeDescription
[PARENTDIR] Parent Directory-
[DIR]   12/ 2022-04-12 18:36-
Apache/2.4.54 (Debian) Server at qa-logs.debian.net Port 80

http://qa-logs.debian.net/2022/05/
Index of /2022/05
[ICO]   NameLast modified   SizeDescription
[PARENTDIR] Parent Directory-
[DIR]   25/ 2022-05-26 05:47-
Apache/2.4.54 (Debian) Server at qa-logs.debian.net Port 80

http://qa-logs.debian.net/2022/06/
Index of /2022/06
[ICO]   NameLast modified   SizeDescription
[PARENTDIR] Parent Directory-
[DIR]   09/ 2022-06-10 18:50-
[DIR]   10/ 2022-06-11 20:24-
[DIR]   23/ 2022-06-23 06:25-
[DIR]   24/ 2022-06-24 06:40-
Apache/2.4.54 (Debian) Server at qa-logs.debian.net Port 80

http://qa-logs.debian.net/2022/07/
Index of /2022/07
[ICO]   NameLast modified   SizeDescription
[PARENTDIR] Parent Directory-
[DIR]   16/ 2022-07-16 12:45-
[DIR]   28/ 2022-07-29 13:20-
Apache/2.4.54 (Debian) Server at qa-logs.debian.net Port 80

http://qa-logs.debian.net/2022/08/
Not Found

The requested URL was not found on this server.
Apache/2.4.54 (Debian) Server at qa-logs.debian.net Port 80



At https://buildd.debian.org/status/logs.php?pkg=msc-generator
could I not find a full log. But I have seen that msc-generator
builds with GCC 12.1, so now this close message.
That is what the 'Control: notfound -1 8.1-2' should do.


Regards
Geert Stappers
DD

P.S.
The https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1012999#29
question: 'Where to find information about the rebuild schedule?'
is still valid
-- 
Silence is hard to parse

Processed: found 1010358 in 40.1+dfsg-1, severity of 1010358 is serious

[Debian Bug Tracking System]

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

> found 1010358 40.1+dfsg-1
Bug #1010358 [ugene] ugene: Fix for non-constant SIGSTKSZ
Marked as found in versions ugene/40.1+dfsg-1.
> severity 1010358 serious
Bug #1010358 [ugene] ugene: Fix for non-constant SIGSTKSZ
Severity set to 'serious' from 'normal'
> thanks
Stopping processing here.

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

Bug#1014488: scapy: flaky autopkgtest: No such file or directory: 'isotpsend'

[Neil Williams]

On Wed, 6 Jul 2022 21:42:22 +0200 Paul Gevers  wrote:
> 
> I looked at the results of the autopkgtest of you package on arm64 
> because it was showing up as a regression for the upload of openssl.
> I noticed that the test regularly fails and I saw failures on other 
> architectures too, even in stable.
> 
> Because the unstable-to-testing migration software now blocks on
> regressions in testing, flaky tests, i.e. tests that flip between
> passing and failing without changes to the list of installed packages,
> are causing people unrelated to your package to spend time on these
> tests.
> 
> Don't hesitate to reach out if you need help and some more information
> from our infrastructure.

The autopkgtests work in Salsa but are also quite messy & the package
isn't in great shape overall. For now, I'm going to adjust the
dependencies to see if isotpsend support can be provided inside
autopkgtest. If that fails, the upstream tests will need to be confined
to Salsa and autopkgtests limited only to autopkgtest-pkg-python.

https://salsa.debian.org/pkg-security-team/scapy/-/commit/59a4c0e2ed8c24cf5a3d4412cecdd5086a5b0395

-- 
Neil Williams
=
https://linux.codehelp.co.uk/


pgpx8r_BkNHta.pgp
Description: OpenPGP digital signature

Bug#1016540: marked as done (wmanager: FTBFS / autopkgtest regression with glibc 2.34)

[Debian Bug Tracking System]

Your message dated Wed, 10 Aug 2022 10:34:21 +
with message-id 
and subject line Bug#1016540: fixed in wmanager 0.3.1-1
has caused the Debian Bug report #1016540,
regarding wmanager: FTBFS / autopkgtest regression with glibc 2.34
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.)


-- 
1016540: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1016540
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: wmanager
Version: 0.3.0-2
Severity: important
Tags: upstream patch
Forwarded: https://gitlab.com/wmanager/wmanager/-/merge_requests/1

wmanager fails to build when built against glibc 2.34, and the
autopkgtest fails when run against glibc 2.34 due to a timeout:

https://ci.debian.net/data/autopkgtest/unstable/amd64/w/wmanager/24248015/log.gz

The problem has already been reported upstream with a patch available:
https://gitlab.com/wmanager/wmanager/-/merge_requests/1

Could you please do an upload with this fix?

Thanks
Aurelien
--- End Message ---
--- Begin Message ---
Source: wmanager
Source-Version: 0.3.1-1
Done: Peter Pentchev 

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

Debian distribution maintenance software
pp.
Peter Pentchev  (supplier of updated wmanager package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 10 Aug 2022 13:09:56 +0300
Source: wmanager
Architecture: source
Version: 0.3.1-1
Distribution: unstable
Urgency: medium
Maintainer: Peter Pentchev 
Changed-By: Peter Pentchev 
Closes: 1016540
Changes:
 wmanager (0.3.1-1) unstable; urgency=medium
 .
   * Add the year 2021 to my debian/* copyright notice.
   * Explicitly declare dh-sequence-single-binary.
   * Declare compliance with Policy 4.6.1 with no changes.
   * Add the year 2022 to my debian/* copyright notice.
   * New upstream release:
 - fixes an out-of-bounds memory write in option parsing;
   Closes: #1016540
Checksums-Sha1:
 dbe104556dbeb19057e34ce0902ef61eb9c7e94c 2398 wmanager_0.3.1-1.dsc
 bd81f34ec7aea3c44e91825d5aa33732bf26 23408 wmanager_0.3.1.orig.tar.xz
 935fcc48c8387461b1651b62399732b1d1706d53 833 wmanager_0.3.1.orig.tar.xz.asc
 400efe0eddd2bd2d05a4131dd2420b3d4af611df 9928 wmanager_0.3.1-1.debian.tar.xz
Checksums-Sha256:
 ddcfaf721210fec93c00dac03d7cd52b00928cab0e1523901005433d675694db 2398 
wmanager_0.3.1-1.dsc
 e594aaf8647c4475e3c9c1b3bf7cf978b4f031212c3e04e4dbd63ea978814f05 23408 
wmanager_0.3.1.orig.tar.xz
 cb28b159de965551d815b6310177d536a5e5adfe23e4f795a8363f81703343b4 833 
wmanager_0.3.1.orig.tar.xz.asc
 1207f6d94720482a2acb57531d2da1185a0bb27713a43e9fbcdec8ec0616d9d6 9928 
wmanager_0.3.1-1.debian.tar.xz
Files:
 24a2777f2208e267c989ea53215f87d9 2398 x11 optional wmanager_0.3.1-1.dsc
 2821d12e723f089171a5fd8ef89a8f94 23408 x11 optional wmanager_0.3.1.orig.tar.xz
 11be20b06dd63beddd2f97c8ec22b4c4 833 x11 optional 
wmanager_0.3.1.orig.tar.xz.asc
 87470a3c6d7d10aaf306804cf2e3bebc 9928 x11 optional 
wmanager_0.3.1-1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQJEBAEBCgAuFiEELuenpRf8EkzxFcNUZR7vsCUn3xMFAmLzhWYQHHJvYW1AZGVi
aWFuLm9yZwAKCRBlHu+wJSffE65dEACea8yyOz4zw7WV/wXHef3cfOv0b5T5Ck/3
Ygwr2JYWbN4KorP30nHBnro8yhoSxXsNBZL76hJdXrzQ1KRAyngrWkzpeH/gcFeJ
bpglIsexR7YpiCNb/6kOAq93VDxySdEznjM9KT5CrQWQz8zpyCkuVHIWwGRKeZKS
jrSiJYmvS+92gMR+tpUPB6HRHZCCFZ/JABA3V46Tr8eRjuO1Ups+gkW4bd8lgmTG
S2ZdYvL+a1PJcSZQhjt2WY0Ug4ir+atGHHYV688PrPadpog8zZo+AHZvbpRzDp7L
FIwK3l+tTgCIktLXAmD4yTTiFQdC6j0w3BTDuYYYkjsdLAvCkMXk82m7LBqBbBoG
ldJXIeAQfwQ2IKVnFOC/KMFF8tlH20XXb3eKt9u5RYVDEXMEHxgQeyttQDqbAV0z
QBN83B7571kBmua5vDikCVDl8DCc+QFGNKcBVZniduCR+lsyk1zhiMQ52D5dSGZ+
AXoGE5M6Uqzrr+q783KrD1snrP0Ab+sFVKCMpMY5G15NJq8nMiTI7pZj2Tli8VeC
j1X+zH2LHxZnc/0I74V0FBwjkP/maPasfuPZiAFOi8dbcxu3dKxhW8xHZ/d1OLyM
ya5hx+786J08ca+j2CJuTbebxy11KxXR/locYyU4/8WlsStOiO3XO1uSuNweCXlh
hbfTVtOnfA==
=K1Kx
-END PGP SIGNATURE End Message ---

Bug#1016937: atop: autopkgtest regression on arm64 and armhf and times out on s390x

[Marc Haber]

On Wed, Aug 10, 2022 at 08:06:29AM +0200, Paul Gevers wrote:
> I looked at the results of the autopkgtest of you package because it was
> showing up on our page for long running tests on s390x. I noticed that the
> test always fails on s390x with an autopkgtest timeout. Your package
> regressed on armhf and arm64 around April 2022.
> 
> Regressions in testing on amd64 and arm64 are considered RC by the release
> team [1]. Tests that time out and fail while normally running quickly are a
> serious burden on our infrastructure, please try to prevent the apparent
> hang.
> 
> Don't hesitate to reach out if you need help and some more information
> from our infrastructure.
> 
> Paul
> 
> https://ci.debian.net/packages/m/mercurial/testing/amd64/
> 
> [1] https://release.debian.org/testing/rc_policy.txt (section 6.a)

Unfortunately, this bug report suffers from multiple cut or
template error. The ci link points to the mercurial page for amd64, the
text alternates between s390s, armhf, arm64 and amd64.

I tried the (dead simple) autopkgtest on the s390s and arm64 porterboxes
and it succeeded in a second's time. I have sharpened the expression
that counts the CPUs in lscpu's output and hope this will fix the issue.

I also fixed a syntax error in the test, but that should cause the test
to error out and not hang.

Can you find out in which line the autopkgtest stalls?

Greetings
Marc

-- 
-
Marc Haber | "I don't trust Computers. They | Mailadresse im Header
Leimen, Germany|  lose things."Winona Ryder | Fon: *49 6224 1600402
Nordisch by Nature |  How to make an American Quilt | Fax: *49 6224 1600421

Bug#1016942: marked as done (ptl: autopkgtest regression: ‘strlen’ was not declared in this scope)

[Debian Bug Tracking System]

Your message dated Wed, 10 Aug 2022 09:09:55 +
with message-id 
and subject line Bug#1016942: fixed in ptl 2.3.3-2
has caused the Debian Bug report #1016942,
regarding ptl: autopkgtest regression: ‘strlen’ was not declared in this scope
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.)


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

Source: ptl
Version: 2.3.3-1
Severity: serious
User: debian...@lists.debian.org
Usertags: regression

Dear maintainer(s),

With a recent change in testing the autopkgtest of ptl started to fail.

Paul

https://ci.debian.net/packages/p/ptl/

https://ci.debian.net/data/autopkgtest/testing/ppc64el/p/ptl/24565458/log.gz

autopkgtest [07:07:19]: test examples: [---
-- The C compiler identification is GNU 12.1.0
-- The CXX compiler identification is GNU 12.1.0
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Check for working C compiler: /usr/bin/cc - skipped
-- Detecting C compile features
-- Detecting C compile features - done
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Check for working CXX compiler: /usr/bin/c++ - skipped
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- Performing Test CMAKE_HAVE_LIBC_PTHREAD
-- Performing Test CMAKE_HAVE_LIBC_PTHREAD - Failed
-- Check if compiler accepts -pthread
-- Check if compiler accepts -pthread - yes
-- Found Threads: TRUE
-- OpenCV not found! Skipping example 'extended/rotation'
-- Configuring done
-- Generating done
-- Build files have been written to: 
/tmp/autopkgtest-lxc.xiql938s/downtmp/autopkgtest_tmp/builddir

[ 10%] Building CXX object minimal/CMakeFiles/ptl-minimal.dir/minimal.cc.o
In file included from /usr/include/PTL/PTL.hh:23,
 from 
/tmp/autopkgtest-lxc.xiql938s/downtmp/autopkgtest_tmp/minimal/minimal.cc:22:
/usr/include/PTL/Backtrace.hh: In static member function ‘static void 
PTL::Backtrace::Message(int, siginfo_t*, std::ostream&)’:
/usr/include/PTL/Backtrace.hh:511:12: error: ‘strlen’ was not declared 
in this scope

  511 | if(strlen(itr) == 0)
  |^~
/usr/include/PTL/Backtrace.hh:191:1: note: ‘strlen’ is defined in header 
‘’; did you forget to ‘#include ’?

  190 | #include 
  +++ |+#include 
  191 | #include 
make[2]: *** [minimal/CMakeFiles/ptl-minimal.dir/build.make:76: 
minimal/CMakeFiles/ptl-minimal.dir/minimal.cc.o] Error 1
make[1]: *** [CMakeFiles/Makefile2:173: 
minimal/CMakeFiles/ptl-minimal.dir/all] Error 2

make: *** [Makefile:91: all] Error 2
autopkgtest [07:07:24]: test examples: ---]


OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: ptl
Source-Version: 2.3.3-2
Done: Stephan Lachnit 

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

Debian distribution maintenance software
pp.
Stephan Lachnit  (supplier of updated ptl package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 10 Aug 2022 10:28:32 +0200
Source: ptl
Architecture: source
Version: 2.3.3-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Stephan Lachnit 
Closes: 1016942
Changes:
 ptl (2.3.3-2) unstable; urgency=medium
 .
   * Fix compilation with GCC12 (Closes: #1016942)
   * Update standards version to 4.6.1, no changes needed
Checksums-Sha1:
 c41aac61fc97d4de4cc46e8a35e498ab9359062f 2061 ptl_2.3.3-2.dsc
 03192b5be283875f1cb1e3f073996c4d6852cd24 3232 ptl_2.3.3-2.debian.tar.xz
 d3e00b1a34e5b63eccb8d46f60b1392d64484da2 7430 ptl_2.3.3-2_amd64.buildinfo
Checksums-Sha256:
 e679094a3818364129a3f69ab9f11fb7280a99032514ecf6da3156cb5a0e 2061 
ptl_2.3.3-2.dsc
 ee9effa908683250f282ca583490e018bec6186e30ac2c17a91fac550f3b085f 3232 
ptl_2.3.3-2.debian.tar.xz
 e9489128b5928c5e360e205bf2446ca5958cfc967eaf9718ae190f88e5a92141 7430 
ptl_2.3.3-2_amd64.buildinfo
Files:
 eea6de14b30685cbd275a7ff9560d6be 2061 libs 

Bug#1012943: marked as done (herbstluftwm: ftbfs with GCC-12)

[Debian Bug Tracking System]

Your message dated Wed, 10 Aug 2022 07:34:16 +
with message-id 
and subject line Bug#1012943: fixed in herbstluftwm 0.9.5-2
has caused the Debian Bug report #1012943,
regarding herbstluftwm: ftbfs with GCC-12
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.)


-- 
1012943: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1012943
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:herbstluftwm
Version: 0.9.4-5
Severity: normal
Tags: sid bookworm
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-12

[This bug is targeted to the upcoming bookworm release]

Please keep this issue open in the bug tracker for the package it
was filed for.  If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-12/g++-12, but succeeds to build with gcc-11/g++-11. The
severity of this report will be raised before the bookworm release.

The full build log can be found at:
http://qa-logs.debian.net/2022/06/09/gcc12/herbstluftwm_0.9.4-5_unstable_gcc12.log
The last lines of the build log are at the end of this report.

To build with GCC 11, either set CC=gcc-11 CXX=g++-11 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t=experimental install g++ 

Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-11/porting_to.html

GCC 11 defaults to the GNU++17 standard.  If your package installs
header files in /usr/include, please don't work around C++17 issues
by choosing a lower C++ standard for the package build, but fix these
issues to build with the C++17 standard.

[...]
=== FAILURES ===
__ test_foreach_invalid_flag ___

hlwm = 

def test_foreach_invalid_flag(hlwm):
hlwm.call_xfail('foreach C --filter-typo=X tags. echo C') \
.expect_stderr('"" has no child named "--filter-typo=X"')
hlwm.call_xfail('foreach C --filter-name=( tags. echo C') \
>   .expect_stderr('Parenthesis is not closed')

../tests/test_meta_commands.py:718: 
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 

self2 = 
CompletedProcess(args=['/<>/obj-x86_64-linux-gnu/herbstclient', 
'-n', 'forea..., stdout='', stderr='foreach: Cannot parse flag 
"--filter-name=(": Mismatched \'(\' and \')\' in regular expression\n')
needle = 'Parenthesis is not closed', regex = True

def f(self2, needle, regex=True):
if regex:
>   assert re.search(needle, self2.stderr)
E   assert None
E+  where None = ('Parenthesis 
is not closed', 'foreach: Cannot parse flag "--filter-name=(": Mismatched \'(\' 
and \')\' in regular expression\n')
E+where  = re.search
E+and   'foreach: Cannot parse flag "--filter-name=(": 
Mismatched \'(\' and \')\' in regular expression\n' = 
CompletedProcess(args=['/<>/obj-x86_64-linux-gnu/herbstclient', 
'-n', 'forea..., stdout='', stderr='foreach: Cannot parse flag 
"--filter-name=(": Mismatched \'(\' and \')\' in regular expression\n').stderr

../tests/conftest.py:107: AssertionError
 Captured stdout setup -
Running: Xvfb -nolisten tcp -screen 0 800x600x24 -noreset +extension RENDER 
-displayfd 20
Xvfb is using the display ":1"
hlwm started
 Captured stderr setup -
_XSERVTransSocketUNIXCreateListener: ...SocketCreateListener() failed
_XSERVTransMakeAllCOTSServerListeners: server already running
The XKEYBOARD keymap compiler (xkbcomp) reports:
> Warning:  Could not resolve keysym XF86EmojiPicker
Errors from xkbcomp are not fatal to the X server
EWMH: 0 desktops:
0 managed clients: 
./src/xconnection.cpp: 227: compositing manager = 0
- Captured stdout call -
Client command ['foreach', 'C', '--filter-typo=X', 'tags.', 'echo', 'C'] failed 
with output:
foreach: Cannot parse argument "--filter-typo=X": Object "" has no child named 
"--filter-typo=X"


Client command ['foreach', 'C', '--filter-name=(', 'tags.', 'echo', 'C'] failed 
with output:
foreach: Cannot parse flag 

Bug#1016139: For Review: Bug#1016139: (net-snmp: CVE-2022-24810 CVE-2022-24809 CVE-2022-24808 CVE-2022-24807 CVE-2022-24806 CVE-2022-24805)

[Moritz Muehlenhoff]

On Wed, Aug 10, 2022 at 05:05:12PM +1000, Craig Small wrote:
> > Do you have capacity to prepare updates for bullseye?
> >
> Yes, see attached debdiff for review. It's just those two patches.

Looks good, thanks! Please upload to security-master.

Cheers,
Moritz

Bug#1016942: ptl: autopkgtest regression: ‘strlen’ was not declared in this scope

[Paul Gevers]

Source: ptl
Version: 2.3.3-1
Severity: serious
User: debian...@lists.debian.org
Usertags: regression

Dear maintainer(s),

With a recent change in testing the autopkgtest of ptl started to fail.

Paul

https://ci.debian.net/packages/p/ptl/

https://ci.debian.net/data/autopkgtest/testing/ppc64el/p/ptl/24565458/log.gz

autopkgtest [07:07:19]: test examples: [---
-- The C compiler identification is GNU 12.1.0
-- The CXX compiler identification is GNU 12.1.0
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Check for working C compiler: /usr/bin/cc - skipped
-- Detecting C compile features
-- Detecting C compile features - done
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Check for working CXX compiler: /usr/bin/c++ - skipped
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- Performing Test CMAKE_HAVE_LIBC_PTHREAD
-- Performing Test CMAKE_HAVE_LIBC_PTHREAD - Failed
-- Check if compiler accepts -pthread
-- Check if compiler accepts -pthread - yes
-- Found Threads: TRUE
-- OpenCV not found! Skipping example 'extended/rotation'
-- Configuring done
-- Generating done
-- Build files have been written to: 
/tmp/autopkgtest-lxc.xiql938s/downtmp/autopkgtest_tmp/builddir

[ 10%] Building CXX object minimal/CMakeFiles/ptl-minimal.dir/minimal.cc.o
In file included from /usr/include/PTL/PTL.hh:23,
 from 
/tmp/autopkgtest-lxc.xiql938s/downtmp/autopkgtest_tmp/minimal/minimal.cc:22:
/usr/include/PTL/Backtrace.hh: In static member function ‘static void 
PTL::Backtrace::Message(int, siginfo_t*, std::ostream&)’:
/usr/include/PTL/Backtrace.hh:511:12: error: ‘strlen’ was not declared 
in this scope

  511 | if(strlen(itr) == 0)
  |^~
/usr/include/PTL/Backtrace.hh:191:1: note: ‘strlen’ is defined in header 
‘’; did you forget to ‘#include ’?

  190 | #include 
  +++ |+#include 
  191 | #include 
make[2]: *** [minimal/CMakeFiles/ptl-minimal.dir/build.make:76: 
minimal/CMakeFiles/ptl-minimal.dir/minimal.cc.o] Error 1
make[1]: *** [CMakeFiles/Makefile2:173: 
minimal/CMakeFiles/ptl-minimal.dir/all] Error 2

make: *** [Makefile:91: all] Error 2
autopkgtest [07:07:24]: test examples: ---]


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1016139: For Review: Bug#1016139: (net-snmp: CVE-2022-24810 CVE-2022-24809 CVE-2022-24808 CVE-2022-24807 CVE-2022-24806 CVE-2022-24805)

[Craig Small]

On Sun, 7 Aug 2022 at 23:29, Salvatore Bonaccorso  wrote:

> Did you got confirmation from upstream back if those are the only two
> needed ones?
>
I got no message at all. However, these are the only two that mention the
people that found the bug and fixed it (two sets of people).


> Do you have capacity to prepare updates for bullseye?
>
Yes, see attached debdiff for review. It's just those two patches.

 - Craig
diff -Nru net-snmp-5.9+dfsg/debian/changelog net-snmp-5.9+dfsg/debian/changelog
--- net-snmp-5.9+dfsg/debian/changelog	2020-09-25 09:10:00.0 +1000
+++ net-snmp-5.9+dfsg/debian/changelog	2022-08-10 16:16:59.0 +1000
@@ -1,3 +1,12 @@
+net-snmp (5.9+dfsg-4+deb11u1) bullseye-security; urgency=high
+
+  * Backport upstream security patches from v5.9.3 Closes: #1016139
+  * snmpd_fix_bounds_checking: CVE-2022-24805, CVE-2022-24809
+  * snmpd_recover_set_status: CVE-2022-24806, CVE-2022-24807, CVE-2022-24808,
+CVE-2022-24810
+
+ -- Craig Small   Wed, 10 Aug 2022 16:16:59 +1000
+
 net-snmp (5.9+dfsg-3) unstable; urgency=medium
 
   * Source only upload - no changes Closes: #970798
diff -Nru net-snmp-5.9+dfsg/debian/patches/series net-snmp-5.9+dfsg/debian/patches/series
--- net-snmp-5.9+dfsg/debian/patches/series	2020-09-25 09:10:00.0 +1000
+++ net-snmp-5.9+dfsg/debian/patches/series	2022-08-10 16:16:59.0 +1000
@@ -37,3 +37,5 @@
 Link-libnetsnmptrapd-against-MYSQL_LIBS.patch
 pkgconfig_install_mode
 perl_makefile_man3pods
+snmpd_fix_bounds_checking
+snmpd_recover_set_status
diff -Nru net-snmp-5.9+dfsg/debian/patches/snmpd_fix_bounds_checking net-snmp-5.9+dfsg/debian/patches/snmpd_fix_bounds_checking
--- net-snmp-5.9+dfsg/debian/patches/snmpd_fix_bounds_checking	1970-01-01 10:00:00.0 +1000
+++ net-snmp-5.9+dfsg/debian/patches/snmpd_fix_bounds_checking	2022-08-10 16:16:59.0 +1000
@@ -0,0 +1,123 @@
+Description: snmpd: fix bounds checking in MIBS
+ Fix bounds checking in NET-SNMP-AGENT-MIB, NET-SNMP-VACM-MIB,
+ SNMP-VIEW-BASED-ACM-MIB, SNMP-USER-BASED-SM-MIB
+
+ Reported by: Yu Zhang of VARAS@IIE, Nanyu Zhong of VARAS@IIE
+ Fixes by: Arista Networks
+
+ References: CVE-2022-24805, CVE-2022-24809 
+Author: Bill Fenner 
+Origin: upstream, https://github.com/net-snmp/net-snmp/commit/67ebb43e9038b2dae6e74ae8838b36fcc10fc937`
+Bug-Debian: https://bugs.debian.org/1016139
+Reviewed-by: Craig Small 
+Last-Update: 2022-08-10
+---
+This patch header follows DEP-3: http://dep.debian.net/deps/dep3/
+--- a/agent/mibgroup/agent/nsLogging.c
 b/agent/mibgroup/agent/nsLogging.c
+@@ -147,6 +147,8 @@
+ continue;
+ logh = (netsnmp_log_handler*)netsnmp_extract_iterator_context(request);
+ table_info  =netsnmp_extract_table_info(request);
++if (!table_info || !table_info->indexes)
++continue;
+ 
+ switch (table_info->colnum) {
+ case NSLOGGING_TYPE:
+@@ -201,6 +203,8 @@
+ }
+ logh = (netsnmp_log_handler*)netsnmp_extract_iterator_context(request);
+ table_info  = netsnmp_extract_table_info(request);
++if (!table_info || !table_info->indexes)
++continue;
+ 
+ switch (table_info->colnum) {
+ case NSLOGGING_TYPE:
+@@ -394,6 +398,8 @@
+ continue;
+ logh = (netsnmp_log_handler*)netsnmp_extract_iterator_context(request);
+ table_info  = netsnmp_extract_table_info(request);
++if (!table_info || !table_info->indexes)
++continue;
+ 
+ switch (table_info->colnum) {
+ case NSLOGGING_TYPE:
+--- a/agent/mibgroup/agent/nsVacmAccessTable.c
 b/agent/mibgroup/agent/nsVacmAccessTable.c
+@@ -170,9 +170,13 @@
+ entry = (struct vacm_accessEntry *)
+ netsnmp_extract_iterator_context(request);
+ table_info = netsnmp_extract_table_info(request);
++if (!table_info || !table_info->indexes)
++continue;
+ 
+ /* Extract the authType token from the list of indexes */
+ idx = table_info->indexes->next_variable->next_variable->next_variable->next_variable;
++if (idx->val_len >= sizeof(atype))
++continue;
+ memset(atype, 0, sizeof(atype));
+ memcpy(atype, (char *)idx->val.string, idx->val_len);
+ viewIdx = se_find_value_in_slist(VACM_VIEW_ENUM_NAME, atype);
+@@ -212,6 +216,8 @@
+ entry = (struct vacm_accessEntry *)
+ netsnmp_extract_iterator_context(request);
+ table_info = netsnmp_extract_table_info(request);
++if (!table_info || !table_info->indexes)
++continue;
+ ret = SNMP_ERR_NOERROR;
+ 
+ switch (table_info->colnum) {
+@@ -247,6 +253,8 @@
+  * Extract the authType token from the list of indexes
+  */
+   

Bug#1016941: phyml: flaky autopkgtest on armel: test duration around autopkgtest timeout

[Paul Gevers]

Source: phyml
Version: 3:3.3.20200621-1
Severity: serious
User: debian...@lists.debian.org
Usertags: flaky

Dear maintainer(s),

I looked at the results of the autopkgtest of you package because it was 
showing up as a regression for the upload of glibc [0]. I noticed that 
the test regularly fails on armel [1] in unstable, testing and stable. 
Somehow running the test takes significantly longer on armel than on our 
other ci architectures and most of the time it's getting close to the 
autopkgtest timeout of 2:47 h. Do you have any idea why armel would be 
so much slower? If the armel specific slow down can't be fixed, an 
autopkgtest work around could be to split the test into multiple tests, 
because each autopkgtest gets the timeout. Otherwise, I recommend adding 
an "Architecture: !armel" line to the d/t/control test stanza.


Because the unstable-to-testing migration software now blocks on
regressions in testing, flaky tests, i.e. tests that flip between
passing and failing without changes to the list of installed packages,
are causing people unrelated to your package to spend time on these
tests.

Don't hesitate to reach out if you need help and some more information
from our infrastructure.

Paul

[0] 
https://ci.debian.net/data/autopkgtest/testing/armel/p/phyml/24557743/log.gz

[1] https://ci.debian.net/packages/p/phyml/


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1016940: php-luasandbox: flaky autopkgtest: timer pausing and unpausing [tests/timer.phpt]

[Paul Gevers]

Source: php-luasandbox
Version: 3.0.3-2
Severity: serious
User: debian...@lists.debian.org
Usertags: flaky

Dear maintainer(s),

I looked at the results of the autopkgtest of you package because it was 
showing up as a regression for the upload of glibc. I noticed that the 
test regularly fails on all architectures [1]. It seems that the "timer 
pausing and unpausing [tests/timer.phpt]" is too sensitive to be used in 
autopkgtest.


Because the unstable-to-testing migration software now blocks on
regressions in testing, flaky tests, i.e. tests that flip between
passing and failing without changes to the list of installed packages,
are causing people unrelated to your package to spend time on these
tests.

Don't hesitate to reach out if you need help and some more information
from our infrastructure.

Paul

[1] https://ci.debian.net/packages/p/php-luasandbox/


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1016939: : flaky autopkgtest: padthv1_jack: no process found

[Paul Gevers]

Source: padthv1
Version: 0.9.17-1
Severity: serious
User: debian...@lists.debian.org
Usertags: flaky

Dear maintainer(s),

I looked at the results of the autopkgtest of you package because it was 
showing up as a regression for the upload of glibc. I noticed that the 
test regularly fails on ppc64el [1].


Because the unstable-to-testing migration software now blocks on
regressions in testing, flaky tests, i.e. tests that flip between
passing and failing without changes to the list of installed packages,
are causing people unrelated to your package to spend time on these
tests.

Don't hesitate to reach out if you need help and some more information
from our infrastructure.

Paul

[1] https://ci.debian.net/packages/p/padthv1/testing/ppc64el/

E.g. 
https://ci.debian.net/data/autopkgtest/testing/ppc64el/p/padthv1/24099886/log.gz


autopkgtest [18:54:41]: test simpletest: [---
Simple test success!
We kill padthv1_jack because it doesn’t close itself in the testbed
padthv1_jack: no process found
autopkgtest [18:54:42]: test simpletest: ---]


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1016556: marked as done (fpc: glibc 2.34 breaks fpc autopkgtest on arm64: undefined reference to `__libc_csu_init')

[Debian Bug Tracking System]

Your message dated Wed, 10 Aug 2022 06:36:22 +
with message-id 
and subject line Bug#1016556: fixed in fpc 3.2.2+dfsg-12
has caused the Debian Bug report #1016556,
regarding fpc: glibc 2.34 breaks fpc autopkgtest on arm64: undefined reference 
to `__libc_csu_init'
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.)


-- 
1016556: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1016556
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: fpc
Version: 3.2.2+dfsg-10
Severity: important
Tags: patch
User: debian-gl...@lists.debian.org
Usertags: glibc2.34

Dear maintainer,

The autopkgtest of fpc fails in sid on amd64 when that autopkgtest is
run with the binary packages of glibc from experimental. It passes when
run with only packages from sid. In tabular form:

 passfail
glibcfrom sid2.34-0experimental5
fpc  from sid3.2.2+dfsg-10
all others   from sidfrom sid

Here is the relevant part of the test log:

/usr/bin/ppca64 fpmake.pp -n -Fu../../rtl/units/aarch64-linux 
-Fu../../packages/paszlib -Fu../../packages/fcl-process -Fu../../packages/hash 
-Fu../../packages/libtar -Fu../../packages/fpmkunit/units_bs/aarch64-linux  
@/tmp/autopkgtest-lxc.pdlnszmr/downtmp/build.u8l/src/debian/deb-build-fpc.cfg
/usr/bin/ld.bfd: 
/tmp/autopkgtest-lxc.pdlnszmr/downtmp/build.u8l/src/fpcsrc/rtl/units/aarch64-linux/cprt0.o:
 in function `_start':
(.text+0x54): undefined reference to `__libc_csu_init'
/usr/bin/ld.bfd: (.text+0x58): undefined reference to `__libc_csu_init'
/usr/bin/ld.bfd: (.text+0x5c): undefined reference to `__libc_csu_fini'
/usr/bin/ld.bfd: (.text+0x60): undefined reference to `__libc_csu_fini'
fpmake.pp(258) Error: Error while linking
fpmake.pp(258) Fatal: There were 1 errors compiling module, stopping
Fatal: Compilation aborted

The full test log is available there:
https://ci.debian.net/data/autopkgtest/unstable/arm64/f/fpc/24224856/log.gz

It seems that the startup code has to be adjusted for glibc 2.34, Ubuntu
has a patch available there:
https://patches.ubuntu.com/f/fpc/fpc_3.2.2+dfsg-11ubuntu1.patch

Regards
Aurelien
--- End Message ---
--- Begin Message ---
Source: fpc
Source-Version: 3.2.2+dfsg-12
Done: Paul Gevers 

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

Debian distribution maintenance software
pp.
Paul Gevers  (supplier of updated fpc 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, 10 Aug 2022 07:42:49 +0200
Source: fpc
Architecture: source
Version: 3.2.2+dfsg-12
Distribution: unstable
Urgency: medium
Maintainer: Pascal Packaging Team 
Changed-By: Paul Gevers 
Closes: 1016556
Changes:
 fpc (3.2.2+dfsg-12) unstable; urgency=medium
 .
   * Add glibc2.34.patch to adjust startup code for glibc2.34 (Closes:
 #1016556)
Checksums-Sha1:
 791f8ce51dac66a052b6e058953de1d3701f362e 4016 fpc_3.2.2+dfsg-12.dsc
 68c20e40509f75219e01994e3748289623f1273f 124224 fpc_3.2.2+dfsg-12.debian.tar.xz
Checksums-Sha256:
 faa1f4f380156b572d322c34e38cff1cbe7a22912ef7526d1acfb5f8546ff71c 4016 
fpc_3.2.2+dfsg-12.dsc
 bc793e809291334dd5859ae33b848936700d3fd3c230903fb7f10b044736abf4 124224 
fpc_3.2.2+dfsg-12.debian.tar.xz
Files:
 7a0748fcd8a7ac607a35e2ee549ade6a 4016 devel optional fpc_3.2.2+dfsg-12.dsc
 e8beea4d56a4d05911622507bffecb58 124224 devel optional 
fpc_3.2.2+dfsg-12.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQEzBAEBCAAdFiEEWLZtSHNr6TsFLeZynFyZ6wW9dQoFAmLzRqYACgkQnFyZ6wW9
dQpbHwf/UQ/IdxFxufzCRRNSkilnjNcFnK3HGHAQVbc7xqCZCqQHekc3ucw3MIcg
Zht31GRXaLYcKh+JmN5OUJK5EKg/Yo1CtHZtzQBXqR+YqCs9omw75hTgxVPsaT9O
4I1I6CIVKMDCmkxG+Kgs1WbVQzQYIjrdwN/hDZ0mysXSjPwe9KXw9HKk2fxRhuED
O5KzZJY2ZXi5TTGr4/oUFJpxE7qNFEgpgJsSOIDu/laKlmHGlyIYNTc/s/u7sh7j
BAPy0JeKeS7OwUfD/K1UoeHcnq1Do4j+qS6bFo5FPaNTa5paKc31V49TG7Tq74M2
jDxh3lWVNBsgoSGpDkxirw1y5yp1mg==
=YdUR
-END PGP SIGNATURE End Message ---

Bug#1016938: konclude: autopkgtest regression on armhf, flaky test on s390x (with timeout)

[Paul Gevers]

Source: konclude
Version: 0.7.0+1137~dfsg-1
Severity: serious
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: timeout regression flaky

Dear maintainer(s),

I looked at the results of the autopkgtest of your package because it 
was showing up on our page for long running tests on s390x. I noticed 
that the test regularly fails on s390x with an autopkgtest timeout. 
Additionally I noticed that your package regressed on armhf around 
August 2021.


Because the unstable-to-testing migration software now blocks on
regressions in testing, flaky tests, i.e. tests that flip between
passing and failing without changes to the list of installed packages,
are causing people unrelated to your package to spend time on these
tests. Tests that time out and fail while normally running quickly are a 
serious burden on our infrastructure, please try to prevent the apparent 
hang.


Regressions in testing on release architectures are considered RC by the 
release team [1].


Don't hesitate to reach out if you need help and some more information
from our infrastructure.

Paul

https://ci.debian.net/packages/k/konclude/

[1] https://release.debian.org/testing/rc_policy.txt (section 6.a)


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1016937: atop: autopkgtest regression on arm64 and armhf and times out on s390x

[Paul Gevers]

Source: atop
Version: 2.7.1-1
Severity: serious
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: timeout regression

Dear maintainer(s),

I looked at the results of the autopkgtest of you package because it was 
showing up on our page for long running tests on s390x. I noticed that 
the test always fails on s390x with an autopkgtest timeout. Your package 
regressed on armhf and arm64 around April 2022.


Regressions in testing on amd64 and arm64 are considered RC by the 
release team [1]. Tests that time out and fail while normally running 
quickly are a serious burden on our infrastructure, please try to 
prevent the apparent hang.


Don't hesitate to reach out if you need help and some more information
from our infrastructure.

Paul

https://ci.debian.net/packages/m/mercurial/testing/amd64/

[1] https://release.debian.org/testing/rc_policy.txt (section 6.a)


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1016936: dwz: fails while building assaultcube

[Andreas Beckmann]

Package: dwz
Version: 0.14-1
Severity: serious
Control: block 1016935 with -1

Hi,

assaultcube recently started to FTBFS with a dwz error. Since both
src:assaultcube and src:dwz haven't been changed for a long time and
successfully built previously, I suspect this is related to GCC 12
becoming the default compiler recently.

   dh_dwz -O--sourcedirectory=source/src
dwz: debian/assaultcube/usr/lib/games/assaultcube/ac_client: Unknown debugging 
section .debug_addr
dwz: debian/assaultcube/usr/lib/games/assaultcube/ac_server: Unknown debugging 
section .debug_addr
dwz: Too few files for multifile optimization
dh_dwz: error: dwz 
-mdebian/assaultcube/usr/lib/debug/.dwz/x86_64-linux-gnu/assaultcube.debug 
-M/usr/lib/debug/.dwz/x86_64-linux-gnu/assaultcube.debug -- 
debian/assaultcube/usr/lib/games/assaultcube/ac_client 
debian/assaultcube/usr/lib/games/assaultcube/ac_server returned exit code 1
dh_dwz: error: Aborting due to earlier error
make: *** [debian/rules:9: binary] Error 25

(the full buildlog can be found in #1016935)

(my most recent successful assaultcube build in sid was on July 11)

Andreas

Processed: dwz: fails while building assaultcube

[Debian Bug Tracking System]

Processing control commands:

> block 1016935 with -1
Bug #1016935 [src:assaultcube] assaultcube: FTBFS with GCC 12: dwz fails
1016935 was not blocked by any bugs.
1016935 was not blocking any bugs.
Added blocking bug(s) of 1016935: 1016936

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