Bug#1017711: bug#58956: mark_object, mark_objects(?) crash

[Eli Zaretskii]

> Cc: 58...@debbugs.gnu.org, 1017...@bugs.debian.org
> Date: Thu, 3 Nov 2022 04:00:46 +0100
> From: Vincent Lefevre 
> 
> On 2022-11-02 14:24:51 +0200, Eli Zaretskii wrote:
> > Signal 1 is SIGHUP, AFAIU.  Why should Emacs receive SIGHUP in the
> > middle of GC, I have no idea.  Maybe ask the user what was he doing at
> > that time.  E.g., could that be a remote Emacs session?
> 
> No, it is on my local machine.

So how come Emacs gets a SIGHUP?  This is the crucial detail that is
missing here.  Basically, if SIGHUP is delivered to Emacs, Emacs is
supposed to die a violent death.

> I run emacs, and quit it immediately. The generation of the core dump
> is almost 100% reproducible. Ditto with "emacs -nw".

Wait, you mean the crash is during exiting Emacs?  That could mean
Emacs receives some input event when it's half-way through the
shutdown process, and the input descriptor is already closed.

But the backtrace you posted shows SIGHUP during GC, which is AFAIU a
very different case.

Processed: Bugs severity

[Debian Bug Tracking System]

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

> severity 1023273 grave
Bug #1023273 [ghostscript] Breaks packages like ocrmypdf
Severity set to 'grave' from 'important'
> thanks
Stopping processing here.

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

Processed: tagging 1023327, tagging 1023328

[Debian Bug Tracking System]

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

> tags 1023327 + ftbfs
Bug #1023327 [notepadqq] notepadqq: Fail to build with rollup 3
Added tag(s) ftbfs.
> tags 1023328 + ftbfs
Bug #1023328 [janus] janus: Fail to build with rollup 3
Added tag(s) ftbfs.
> thanks
Stopping processing here.

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

Processed: severity of 1023327 is serious, severity of 1023328 is serious

[Debian Bug Tracking System]

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

> severity 1023327 serious
Bug #1023327 [notepadqq] notepadqq: Fail to build with rollup 3
Severity set to 'serious' from 'important'
> severity 1023328 serious
Bug #1023328 [janus] janus: Fail to build with rollup 3
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

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

Bug#1017711: bug#58956: mark_object, mark_objects(?) crash

[Vincent Lefevre]

On 2022-11-02 14:24:51 +0200, Eli Zaretskii wrote:
> Signal 1 is SIGHUP, AFAIU.  Why should Emacs receive SIGHUP in the
> middle of GC, I have no idea.  Maybe ask the user what was he doing at
> that time.  E.g., could that be a remote Emacs session?

No, it is on my local machine.

On 2022-11-02 14:43:41 -0700, Sean Whitton wrote:
> Upstream says there isn't enough information in the backtrace to say
> anything helpful about this.  Could you take a look at
>  and consider supplying more information
> over there, please?
> 
> Also, are you able to reproduce this with 'emacs -q' (not -Q)?

This is not reproducible with "emacs -q".

I can reproduce it in a firejail private directory[*] (so that the
behavior doesn't depend on my own config files), where there is no
.emacs file. There is a .emacs.d directory with just a eln-cache
subdirectory:

zira% ls -la .emacs.d 
total 12
drwx-- 3 vinc17 vinc17 4096 2022-11-01 00:40:05 .
drwx-- 4 vinc17 vinc17 4096 2022-11-03 03:53:23 ..
drwxr-xr-x 3 vinc17 vinc17 4096 2022-11-01 00:40:05 eln-cache
zira% ls -la .emacs.d/eln-cache 
total 12
drwxr-xr-x 3 vinc17 vinc17 4096 2022-11-01 00:40:05 .
drwx-- 3 vinc17 vinc17 4096 2022-11-01 00:40:05 ..
drwxr-xr-x 2 vinc17 vinc17 4096 2022-11-01 00:40:05 28.2-43f520ab
zira% ls -la .emacs.d/eln-cache/28.2-43f520ab 
total 8
drwxr-xr-x 2 vinc17 vinc17 4096 2022-11-01 00:40:05 .
drwxr-xr-x 3 vinc17 vinc17 4096 2022-11-01 00:40:05 ..
zira% 

[*] firejail --ignore=read-only --ignore='noexec ${HOME}' 
--noblacklist='${HOME}/*' --private=fj-dir zsh

I run emacs, and quit it immediately. The generation of the core dump
is almost 100% reproducible. Ditto with "emacs -nw".

But note that the bug is also reproducible without firejail, but
harder to reproduce.

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

Bug#999280: empire-lafe: diff for NMU version 1.1-1.1

[Drake Diedrich]

No need to delay.  Total possible impact one way or another would be really
low, and they can rebuild if they need to.  I haven't used it in a decade,
and am surprised my deadline hacks have survived all this time.  I don't
currently have a known working build system.
-Dtake



On Wed, Nov 2, 2022, 2:15 PM Marcos Talau  wrote:

> Control: tags 999280 + patch
> Control: tags 999280 + pending
>
>
> Dear maintainer,
>
> I've prepared an NMU for empire-lafe (versioned as 1.1-1.1) and
> uploaded it to DELAYED/2. Please feel free to tell me if I
> should delay it longer.
>
> Regards.
>

Bug#1023284: libevent: FTBFS with glibc 2.36

[Samuel Thibault]

Nicolas Mora, le mer. 02 nov. 2022 19:14:51 -0400, a ecrit:
> If I understand correctly, removing the symbols evutil_secure_rng_add_bytes 
> from the symbols files is enough to fix this bug?

It will make the package build again. But possibly some binaries in
Debian are using that symbol, that'd have to be checked before accepting
that this symbol disappears, otherwise those binaries will break.

Samuel

Bug#1023317: Bug#1023318 / Bug#1023317: {screen,zsh}: re-adds /usr/bin/{screen,zsh} to /etc/shells on upgrade

[Axel Beckert]

Hi Helmut,

thanks for these bug reports and making us aware of this type of
issue.

Some more hints about how this all is meant to work and why it
actually works would have been appreciated, though:

Helmut Grohne wrote:
> When upgrading or reinstalling screen, it adds /usr/bin/screen to
> /etc/shells even if one locally removed it there. Such behaviour
> violates Debian policy section 10.7.3. I propose managing the entry
> declaratively using dpkg triggers and am attaching a patch for your
> convenience.
> + install -D -m644 debian/shells 
> $(ROOT)/usr/share/debianutils/shells.d/screen
[…]
> -  add-shell /usr/bin/screen || true
[…]
> -if [ "$1" = disappear ]; then
> -  remove-shell /usr/bin/screen || true
> -fi

It took me quite a while to where this
/usr/share/debianutils/shells.d/ comes from and where it is this
documented,

/usr/share/doc/debianutils/README.shells.gz clearly states that I
should use add-shell and remove-shell:

| So, if a package contains something that the maintainer thinks ought
| to be a valid login shell, it's postinst should, (on initial install
| only, to allow a sysadmin to take it out again), run:
|
| /usr/sbin/add-shell /path/to/shell
|
| In the postrm, probably on remove, the package should call
| 
| /usr/sbin/remove-shell /path/to/shell
| 
| As the various shells start to use it, the default shells list will
| shrink.

No mention of that directory. The man pages add-shell(8) and
remove-shell(8) don't mention this directory either.

Also can't find it mentioned in
/usr/share/doc/debianutils/changelog.Debian.gz.

I also found no mentioning of triggers inside the functional part of
the patches. So I assume you meant to refer to
/var/lib/dpkg/info/debianutils.triggers (which also seems not to be
mentioned in /usr/share/doc/debianutils/changelog.Debian.gz).

Finally when looking /var/lib/dpkg/info/debianutils.postinst, I found
a pointer to update-shells whose man-page explains that whole
mechanism and also why it actually track changes made by the
administrator. An early pointer to that or #990440 would have been
nice…

Regards, Axel
-- 
 ,''`.  |  Axel Beckert , https://people.debian.org/~abe/
: :' :  |  Debian Developer, ftp.ch.debian.org Admin
`. `'   |  4096R: 2517 B724 C5F6 CA99 5329  6E61 2FF9 CD59 6126 16B5
  `-|  1024D: F067 EA27 26B9 C3FC 1486  202E C09E 1D89 9593 0EDE

Bug#1023373: bibledit:

[Bastian Germann]

Source: bibledit
Version: 5.0.988-3
Severity: serious
Control: affects -1 bibledit-cloud

This is a follow-up on #1017083.

Aside from the embedded quill still not being built from source,
quill/source/docs/_includes/analytics.html is clearly a non-source
file that applies Google Analytics, which is not acceptable.

Processed: bibledit:

[Debian Bug Tracking System]

Processing control commands:

> affects -1 bibledit-cloud
Bug #1023373 [src:bibledit] bibledit:
Added indication that 1023373 affects bibledit-cloud

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

Processed: icmpush: diff for NMU version 2.2-6.2

[Debian Bug Tracking System]

Processing control commands:

> tags 999158 + patch
Bug #999158 [src:icmpush] icmpush: missing required debian/rules targets 
build-arch and/or build-indep
Added tag(s) patch.
> tags 999158 + pending
Bug #999158 [src:icmpush] icmpush: missing required debian/rules targets 
build-arch and/or build-indep
Added tag(s) pending.

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

Bug#999158: icmpush: diff for NMU version 2.2-6.2

[Marcos Talau]

Control: tags 999158 + patch
Control: tags 999158 + pending


Dear maintainer,

I've prepared an NMU for icmpush (versioned as 2.2-6.2) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should delay it longer.

Regards.
diff -u icmpush-2.2/debian/changelog icmpush-2.2/debian/changelog
--- icmpush-2.2/debian/changelog
+++ icmpush-2.2/debian/changelog
@@ -1,3 +1,10 @@
+icmpush (2.2-6.2) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * debian/rules: Add build-{arch,indep} (Closes: #999158).
+
+ -- Marcos Talau   Wed, 02 Nov 2022 20:19:02 -0300
+
 icmpush (2.2-6.1) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -u icmpush-2.2/debian/rules icmpush-2.2/debian/rules
--- icmpush-2.2/debian/rules
+++ icmpush-2.2/debian/rules
@@ -53,4 +53,8 @@
 	dh_builddeb
 
 binary: binary-indep binary-arch
-.PHONY: build clean binary-indep binary-arch binary install
+
+build-arch: build
+build-indep: build
+
+.PHONY: build build-arch build-indep clean binary-indep binary-arch binary install

Bug#1023284: libevent: FTBFS with glibc 2.36

[Nicolas Mora]

Hello,

If I understand correctly, removing the symbols evutil_secure_rng_add_bytes 
from the symbols files is enough to fix this bug? If no objection, I'll upload 
the fixed package tomorrow.

Processed: icheck: diff for NMU version 0.9.7-6.4

[Debian Bug Tracking System]

Processing control commands:

> tags 999090 + patch
Bug #999090 [src:icheck] icheck: missing required debian/rules targets 
build-arch and/or build-indep
Added tag(s) patch.
> tags 999090 + pending
Bug #999090 [src:icheck] icheck: missing required debian/rules targets 
build-arch and/or build-indep
Added tag(s) pending.

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

Bug#999090: icheck: diff for NMU version 0.9.7-6.4

[Marcos Talau]

Control: tags 999090 + patch
Control: tags 999090 + pending


Dear maintainer,

I've prepared an NMU for icheck (versioned as 0.9.7-6.4) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should delay it longer.

Regards.
diff -u icheck-0.9.7/debian/changelog icheck-0.9.7/debian/changelog
--- icheck-0.9.7/debian/changelog
+++ icheck-0.9.7/debian/changelog
@@ -1,3 +1,10 @@
+icheck (0.9.7-6.4) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * debian/rules: Add build-{arch,indep} (Closes: #999090).
+
+ -- Marcos Talau   Wed, 02 Nov 2022 20:15:09 -0300
+
 icheck (0.9.7-6.3) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -u icheck-0.9.7/debian/rules icheck-0.9.7/debian/rules
--- icheck-0.9.7/debian/rules
+++ icheck-0.9.7/debian/rules
@@ -49,4 +49,8 @@
 	dh_builddeb
 
 binary: binary-indep binary-arch
-.PHONY: build clean binary-indep binary-arch binary install 
+
+build-arch: build
+build-indep: build
+
+.PHONY: build build-arch build-indep clean binary-indep binary-arch binary install 

Processed: grpn: diff for NMU version 1.4.1-1.1

[Debian Bug Tracking System]

Processing control commands:

> tags 999170 + patch
Bug #999170 [src:grpn] grpn: missing required debian/rules targets build-arch 
and/or build-indep
Added tag(s) patch.
> tags 999170 + pending
Bug #999170 [src:grpn] grpn: missing required debian/rules targets build-arch 
and/or build-indep
Added tag(s) pending.

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

Bug#999170: grpn: diff for NMU version 1.4.1-1.1

[Marcos Talau]

Control: tags 999170 + patch
Control: tags 999170 + pending


Dear maintainer,

I've prepared an NMU for grpn (versioned as 1.4.1-1.1) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should delay it longer.

Regards.
diff -Nru grpn-1.4.1/debian/changelog grpn-1.4.1/debian/changelog
--- grpn-1.4.1/debian/changelog	2017-11-12 06:53:32.0 -0200
+++ grpn-1.4.1/debian/changelog	2022-11-02 20:11:17.0 -0300
@@ -1,3 +1,10 @@
+grpn (1.4.1-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * debian/rules: Add build-{arch,indep} (Closes: #999170).
+
+ -- Marcos Talau   Wed, 02 Nov 2022 20:11:17 -0300
+
 grpn (1.4.1-1) unstable; urgency=low
 
   [ Jens Getreu  ]
diff -Nru grpn-1.4.1/debian/rules grpn-1.4.1/debian/rules
--- grpn-1.4.1/debian/rules	2017-11-12 06:41:00.0 -0200
+++ grpn-1.4.1/debian/rules	2022-11-02 20:11:17.0 -0300
@@ -57,4 +57,7 @@
 
 binary: binary-indep binary-arch
 
-.PHONY: build clean binary-indep binary-arch binary
+build-arch: build
+build-indep: build
+
+.PHONY: build build-arch build-indep clean binary-indep binary-arch binary

Processed: gpsim-doc: diff for NMU version 0.22.0-2.2

[Debian Bug Tracking System]

Processing control commands:

> tags 999299 + patch
Bug #999299 [src:gpsim-doc] gpsim-doc: missing required debian/rules targets 
build-arch and/or build-indep
Added tag(s) patch.
> tags 999299 + pending
Bug #999299 [src:gpsim-doc] gpsim-doc: missing required debian/rules targets 
build-arch and/or build-indep
Added tag(s) pending.

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

Bug#999299: gpsim-doc: diff for NMU version 0.22.0-2.2

[Marcos Talau]

Control: tags 999299 + patch
Control: tags 999299 + pending


Dear maintainer,

I've prepared an NMU for gpsim-doc (versioned as 0.22.0-2.2) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should delay it longer.

Regards.
diff -u gpsim-doc-0.22.0/debian/changelog gpsim-doc-0.22.0/debian/changelog
--- gpsim-doc-0.22.0/debian/changelog
+++ gpsim-doc-0.22.0/debian/changelog
@@ -1,3 +1,10 @@
+gpsim-doc (0.22.0-2.2) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * debian/rules: Add build-{arch,indep} (Closes: #999299).
+
+ -- Marcos Talau   Wed, 02 Nov 2022 20:08:20 -0300
+
 gpsim-doc (0.22.0-2.1) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -u gpsim-doc-0.22.0/debian/rules gpsim-doc-0.22.0/debian/rules
--- gpsim-doc-0.22.0/debian/rules
+++ gpsim-doc-0.22.0/debian/rules
@@ -47,4 +47,8 @@
 	dh_builddeb
 
 binary: binary-indep binary-arch
-.PHONY: build clean binary-indep binary-arch binary install configure
+
+build-arch: build
+build-indep: build
+
+.PHONY: build build-arch build-indep clean binary-indep binary-arch binary install configure

Processed: gnuboy: diff for NMU version 1.0.3-7.2

[Debian Bug Tracking System]

Processing control commands:

> tags 998967 + patch
Bug #998967 [src:gnuboy] gnuboy: missing required debian/rules targets 
build-arch and/or build-indep
Added tag(s) patch.
> tags 998967 + pending
Bug #998967 [src:gnuboy] gnuboy: missing required debian/rules targets 
build-arch and/or build-indep
Added tag(s) pending.

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

Bug#998967: gnuboy: diff for NMU version 1.0.3-7.2

[Marcos Talau]

Control: tags 998967 + patch
Control: tags 998967 + pending


Dear maintainer,

I've prepared an NMU for gnuboy (versioned as 1.0.3-7.2) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should delay it longer.

Regards.
diff -u gnuboy-1.0.3/debian/changelog gnuboy-1.0.3/debian/changelog
--- gnuboy-1.0.3/debian/changelog
+++ gnuboy-1.0.3/debian/changelog
@@ -1,3 +1,11 @@
+gnuboy (1.0.3-7.2) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Bump debhelper compat to 7.
+  * debian/rules: Add build-{arch,indep} (Closes: #998967).
+
+ -- Marcos Talau   Wed, 02 Nov 2022 19:51:44 -0300
+
 gnuboy (1.0.3-7.1) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -u gnuboy-1.0.3/debian/compat gnuboy-1.0.3/debian/compat
--- gnuboy-1.0.3/debian/compat
+++ gnuboy-1.0.3/debian/compat
@@ -1 +1 @@
-5
+7
diff -u gnuboy-1.0.3/debian/control gnuboy-1.0.3/debian/control
--- gnuboy-1.0.3/debian/control
+++ gnuboy-1.0.3/debian/control
@@ -2,7 +2,7 @@
 Section: contrib/games
 Priority: optional
 Maintainer: Davide Puricelli (evo) 
-Build-Depends: debhelper (>> 5), libx11-dev, libxext-dev, libxt-dev, x11proto-xext-dev, libsdl1.2-dev, libaa1-dev, libncurses5-dev  
+Build-Depends: debhelper (>= 7), libx11-dev, libxext-dev, libxt-dev, x11proto-xext-dev, libsdl1.2-dev, libaa1-dev, libncurses5-dev  
 Standards-Version: 3.8.3.0
 
 Package: gnuboy-sdl
diff -u gnuboy-1.0.3/debian/rules gnuboy-1.0.3/debian/rules
--- gnuboy-1.0.3/debian/rules
+++ gnuboy-1.0.3/debian/rules
@@ -48,4 +48,8 @@
 	dh_builddeb -a
 
 binary: binary-indep binary-arch
-.PHONY: build clean binary-indep binary-arch binary 
+
+build-arch: build
+build-indep: build
+
+.PHONY: build build-arch build-indep clean binary-indep binary-arch binary 

Processed: g3data: diff for NMU version 1:1.5.3-3.1

[Debian Bug Tracking System]

Processing control commands:

> tags 999267 + patch
Bug #999267 [src:g3data] g3data: missing required debian/rules targets 
build-arch and/or build-indep
Added tag(s) patch.
> tags 999267 + pending
Bug #999267 [src:g3data] g3data: missing required debian/rules targets 
build-arch and/or build-indep
Added tag(s) pending.

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

Bug#999267: g3data: diff for NMU version 1:1.5.3-3.1

[Marcos Talau]

Control: tags 999267 + patch
Control: tags 999267 + pending


Dear maintainer,

I've prepared an NMU for g3data (versioned as 1:1.5.3-3.1) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should delay it longer.

Regards.
diff -u g3data-1.5.3/debian/changelog g3data-1.5.3/debian/changelog
--- g3data-1.5.3/debian/changelog
+++ g3data-1.5.3/debian/changelog
@@ -1,3 +1,10 @@
+g3data (1:1.5.3-3.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * debian/rules: Add build-{arch,indep} (Closes: #999267).
+
+ -- Marcos Talau   Wed, 02 Nov 2022 19:47:41 -0300
+
 g3data (1:1.5.3-3) unstable; urgency=medium
 
   * Bug fix FTCBFS, thanks to Helmut Grohne  for the
diff -u g3data-1.5.3/debian/rules g3data-1.5.3/debian/rules
--- g3data-1.5.3/debian/rules
+++ g3data-1.5.3/debian/rules
@@ -79,4 +79,8 @@
 	dh_builddeb
 
 binary: binary-indep binary-arch
-.PHONY: build clean binary-indep binary-arch binary install configure
+
+build-arch: build
+build-indep: build
+
+.PHONY: build build-arch build-indep clean binary-indep binary-arch binary install configure

Processed: floatbg: diff for NMU version 1.0-28.1

[Debian Bug Tracking System]

Processing control commands:

> tags 999330 + patch
Bug #999330 [src:floatbg] floatbg: missing required debian/rules targets 
build-arch and/or build-indep
Added tag(s) patch.
> tags 999330 + pending
Bug #999330 [src:floatbg] floatbg: missing required debian/rules targets 
build-arch and/or build-indep
Added tag(s) pending.

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

Bug#999330: floatbg: diff for NMU version 1.0-28.1

[Marcos Talau]

Control: tags 999330 + patch
Control: tags 999330 + pending


Dear maintainer,

I've prepared an NMU for floatbg (versioned as 1.0-28.1) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should delay it longer.

Regards.
diff -u floatbg-1.0/debian/rules floatbg-1.0/debian/rules
--- floatbg-1.0/debian/rules
+++ floatbg-1.0/debian/rules
@@ -54,4 +54,8 @@
 	@echo >&2 'source and diff are obsolete - use dpkg-source -b'; false
 
 binary: binary-indep binary-arch
-.PHONY: build clean binary-indep binary-arch binary
+
+build-arch: build
+build-indep: build
+
+.PHONY: build build-arch build-indep clean binary-indep binary-arch binary
diff -u floatbg-1.0/debian/changelog floatbg-1.0/debian/changelog
--- floatbg-1.0/debian/changelog
+++ floatbg-1.0/debian/changelog
@@ -1,3 +1,10 @@
+floatbg (1.0-28.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * debian/rules: Add build-{arch,indep} (Closes: #999330).
+
+ -- Marcos Talau   Wed, 02 Nov 2022 19:42:42 -0300
+
 floatbg (1.0-28) unstable; urgency=low
 
   * hacked in support for running under Xfce 4.6 or later (-xfce flag)

Bug#998942: farpd: diff for NMU version 0.2-11.1

[Marcos Talau]

Control: tags 998942 + patch
Control: tags 998942 + pending


Dear maintainer,

I've prepared an NMU for farpd (versioned as 0.2-11.1) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should delay it longer.

Regards.
diff -u farpd-0.2/debian/rules farpd-0.2/debian/rules
--- farpd-0.2/debian/rules
+++ farpd-0.2/debian/rules
@@ -90,4 +90,8 @@
 	dh_builddeb -a
 
 binary: binary-indep binary-arch
-.PHONY: build clean binary-indep binary-arch binary install 
+
+build-arch: build
+build-indep: build
+
+.PHONY: build build-arch build-indep clean binary-indep binary-arch binary install 
diff -u farpd-0.2/debian/changelog farpd-0.2/debian/changelog
--- farpd-0.2/debian/changelog
+++ farpd-0.2/debian/changelog
@@ -1,3 +1,10 @@
+farpd (0.2-11.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * debian/rules: Add build-{arch,indep} (Closes: #998942).
+
+ -- Marcos Talau   Wed, 02 Nov 2022 19:34:16 -0300
+
 farpd (0.2-11) unstable; urgency=low
 
   * configure.in: Fix FTBFS: configure: error: libevent not found with the

Processed: farpd: diff for NMU version 0.2-11.1

[Debian Bug Tracking System]

Processing control commands:

> tags 998942 + patch
Bug #998942 [src:farpd] farpd: missing required debian/rules targets build-arch 
and/or build-indep
Added tag(s) patch.
> tags 998942 + pending
Bug #998942 [src:farpd] farpd: missing required debian/rules targets build-arch 
and/or build-indep
Added tag(s) pending.

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

Bug#1020456: marked as done (cypari2 FTBFS with PARI 2.15.0)

[Debian Bug Tracking System]

Your message dated Wed, 02 Nov 2022 22:20:59 +
with message-id 
and subject line Bug#1020456: fixed in cypari2 2.1.2-3
has caused the Debian Bug report #1020456,
regarding cypari2 FTBFS with PARI 2.15.0
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.)


-- 
1020456: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020456
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: cypari2
Version: 2.1.2-2
Severity: serious
Tags: ftbfs bookworm sid

https://buildd.debian.org/status/logs.php?pkg=cypari2&ver=2.1.2-2%2Bb3

...
   debian/rules override_dh_auto_test
make[1]: Entering directory '/<>'
python3 tests/rundoctest.py
  ***   user warning: test
/usr/lib/python3.10/doctest.py:1350: RuntimeWarning: cypari2 leaked 197450664 
bytes on the PARI stack
  exec(compile(example.source, filename, "single",
/usr/lib/python3.10/doctest.py:1350: RuntimeWarning: cypari2 leaked 241740752 
bytes on the PARI stack
  exec(compile(example.source, filename, "single",
/usr/lib/python3.10/doctest.py:1350: RuntimeWarning: cypari2 leaked 248010168 
bytes on the PARI stack
  exec(compile(example.source, filename, "single",
/usr/lib/python3.10/doctest.py:1350: RuntimeWarning: cypari2 leaked 252956360 
bytes on the PARI stack
  exec(compile(example.source, filename, "single",
/usr/lib/python3.10/doctest.py:1350: RuntimeWarning: cypari2 leaked 258607552 
bytes on the PARI stack
  exec(compile(example.source, filename, "single",
/usr/lib/python3.10/doctest.py:1350: RuntimeWarning: cypari2 leaked 209447264 
bytes on the PARI stack
  exec(compile(example.source, filename, "single",
/usr/lib/python3.10/doctest.py:1350: RuntimeWarning: cypari2 leaked 215847936 
bytes on the PARI stack
  exec(compile(example.source, filename, "single",
/usr/lib/python3.10/doctest.py:1350: RuntimeWarning: cypari2 leaked 190613912 
bytes on the PARI stack
  exec(compile(example.source, filename, "single",
/usr/lib/python3.10/doctest.py:1350: RuntimeWarning: cypari2 leaked 178484864 
bytes on the PARI stack
  exec(compile(example.source, filename, "single",
/usr/lib/python3.10/doctest.py:1350: RuntimeWarning: cypari2 leaked 180449432 
bytes on the PARI stack
  exec(compile(example.source, filename, "single",

Testing cypari2.closure
**
File 
"/<>/.pybuild/cpython3_3.10_cypari2/build/cypari2/closure.cpython-310-x86_64-linux-gnu.so",
 line ?, in cypari2.closure.__test__.objtoclosure (line 145)
Failed example:
mul([1], [2])
Differences (ndiff with -expected +actual):
  Traceback (most recent call last):
- ...
- PariError: call_python: forbidden multiplication t_VEC (1 elts) * t_VEC 
(1 elts)
+   File "/usr/lib/python3.10/doctest.py", line 1350, in __run
+ exec(compile(example.source, filename, "single",
+   File "", 
line 1, in 
+ mul([1], [2])
+   File "cypari2/gen.pyx", line 4107, in cypari2.gen.Gen.__call__
+ sig_on()
+   File "cypari2/handle_error.pyx", line 213, in 
cypari2.handle_error._pari_err_handle
+ raise PariError(errnum, pari_error_string, clone_gen_noclear(E))
+ PariError: call_python: incorrect type in qfbcomp (t_VEC)
**
File 
"/<>/.pybuild/cpython3_3.10_cypari2/build/cypari2/closure.cpython-310-x86_64-linux-gnu.so",
 line ?, in cypari2.closure.objtoclosure
Failed example:
mul([1], [2])
Differences (ndiff with -expected +actual):
  Traceback (most recent call last):
- ...
- PariError: call_python: forbidden multiplication t_VEC (1 elts) * t_VEC 
(1 elts)
+   File "/usr/lib/python3.10/doctest.py", line 1350, in __run
+ exec(compile(example.source, filename, "single",
+   File "", line 1, in 
+ mul([1], [2])
+   File "cypari2/gen.pyx", line 4107, in cypari2.gen.Gen.__call__
+ sig_on()
+   File "cypari2/handle_error.pyx", line 213, in 
cypari2.handle_error._pari_err_handle
+ raise PariError(errnum, pari_error_string, clone_gen_noclear(E))
+ PariError: call_python: incorrect type in qfbcomp (t_VEC)
**
2 items had failures:
   1 of  19 in cypari2.closure.__test__.objtoclosure (line 145)
   1 of  19 in cypari2.closure.objtoclosure
***Test Failed*** 2 failures.

Testing cypari2.convert
==

Processed: closing 1022385

[Debian Bug Tracking System]

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

> close 1022385 3.0.6-1
Bug #1022385 [src:pcb-rnd] pcb-rnd: FTBFS: diff: out.copper_p2.svg: No such 
file or directory
The source 'pcb-rnd' and version '3.0.6-1' do not appear to match any binary 
packages
Marked as fixed in versions pcb-rnd/3.0.6-1.
Bug #1022385 [src:pcb-rnd] pcb-rnd: FTBFS: diff: out.copper_p2.svg: No such 
file or directory
Marked Bug as done
> thanks
Stopping processing here.

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

Bug#1017711: emacs-gtk: terminated with signal SIGABRT, 137 MB coredump

[Sean Whitton]

Hello Vincent,

Upstream says there isn't enough information in the backtrace to say
anything helpful about this.  Could you take a look at
 and consider supplying more information
over there, please?

Also, are you able to reproduce this with 'emacs -q' (not -Q)?

Currently we have no way to reproduce this, and you're the only person
who's seen anything like this, so we'll probably have to move the
severity back down to 'important'.

-- 
Sean Whitton


signature.asc
Description: PGP signature

Bug#1023365: prusa-slicer: Wrong wxWidgets Version linked during debian Build resulting in instant SIGSEGV on launch (due to lacking wxWidgets 3.2 support)

[vertuxt]

Package: prusa-slicer
Version: 2.5.0+dfsg-2
Severity: grave
Justification: renders package unusable
X-Debbugs-Cc: t...@beamnet.de, t...@debian.org, onit...@gmail.com

The wrong wxWidgets Version is linked during the build. Normally debian/rules
specifies WX_STABLE=1 which should result in the usage of wxWidgets 3.0 which
is in stable. However, wx-config always returns wx3.2 which is then used by
CMake even if CMakeLists.txt is changed to especially require wxWidgets 3.0
and wx-config options set to --version=3.0.


As already stated in https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022234
and
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020702 upstream does not
have wxWidgets 3.2 support yet.

I verified, the package is usable if linked against wxWidgets 3.0 by setting my
wx-config alternative to 3.0 (update-alternatives).

BR Jan


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

Kernel: Linux 6.0.0-2-amd64 (SMP w/24 CPU threads; PREEMPT)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), 
LANGUAGE=de_DE.UTF-8
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages prusa-slicer depends on:
ii  fonts-noto-hinted  20201225-1
ii  libboost-chrono1.74.0  1.74.0-17
ii  libboost-filesystem1.74.0  1.74.0-17
ii  libboost-iostreams1.74.0   1.74.0-17
ii  libboost-locale1.74.0  1.74.0-17
ii  libboost-log1.74.0 1.74.0-17
ii  libboost-regex1.74.0 [libboost-regex1.74.0-icu71]  1.74.0-17
ii  libboost-thread1.74.0  1.74.0-17
ii  libc6  2.35-4
ii  libcurl3-gnutls    7.85.0-1
ii  libdbus-1-3    1.14.4-1
ii  libexpat1  2.5.0-1
ii  libgcc-s1  12.2.0-3
ii  libgl1 1.5.0-1
ii  libglew2.2 2.2.0-4+b1
ii  libglib2.0-0   2.74.1-1
ii  libgmp10   2:6.2.1+dfsg1-1.1
ii  libgtk-3-0 3.24.34-3
ii  libimath-3-1-29    3.1.5-1+b1
ii  libjpeg62-turbo    1:2.1.2-1+b1
ii  libmpfr6   4.1.0-3
ii  libnlopt0  2.7.1-4+b2
ii  libocct-data-exchange-7.6  7.6.3+dfsg1-5
ii  libocct-foundation-7.6 7.6.3+dfsg1-5
ii  libocct-modeling-algorithms-7.6    7.6.3+dfsg1-5
ii  libocct-modeling-data-7.6  7.6.3+dfsg1-5
ii  libocct-ocaf-7.6   7.6.3+dfsg1-5
ii  libopenvdb9.1  9.1.0-7+b1
ii  libpng16-16    1.6.38-2
ii  libstdc++6 12.2.0-3
ii  libtbb12   2021.5.0-15
ii  libwxbase3.2-0 3.2.1+dfsg-1
ii  libwxgtk3.2-0  3.2.1+dfsg-1

prusa-slicer recommends no packages.

prusa-slicer suggests no packages.

-- no debconf information

Bug#999280: empire-lafe: diff for NMU version 1.1-1.1

[Marcos Talau]

Control: tags 999280 + patch
Control: tags 999280 + pending


Dear maintainer,

I've prepared an NMU for empire-lafe (versioned as 1.1-1.1) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should delay it longer.

Regards.
diff -u empire-lafe-1.1/debian/changelog empire-lafe-1.1/debian/changelog
--- empire-lafe-1.1/debian/changelog
+++ empire-lafe-1.1/debian/changelog
@@ -1,3 +1,10 @@
+empire-lafe (1.1-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * debian/rules: Add build-{arch,indep} (Closes: #999280).
+
+ -- Marcos Talau   Wed, 02 Nov 2022 18:09:17 -0300
+
 empire-lafe (1.1-1) unstable; urgency=low
 
   * New upstream (Closes: #554326)
diff -u empire-lafe-1.1/debian/rules empire-lafe-1.1/debian/rules
--- empire-lafe-1.1/debian/rules
+++ empire-lafe-1.1/debian/rules
@@ -68,4 +68,8 @@
 	@echo >&2 'source and diff are obsolete - use dpkg-source -b'; false
 
 binary: binary-indep binary-arch
-.PHONY: build clean binary-indep binary-arch binary
+
+build-arch: build
+build-indep: build
+
+.PHONY: build build-arch build-indep clean binary-indep binary-arch binary

Processed: empire-lafe: diff for NMU version 1.1-1.1

[Debian Bug Tracking System]

Processing control commands:

> tags 999280 + patch
Bug #999280 [src:empire-lafe] empire-lafe: missing required debian/rules 
targets build-arch and/or build-indep
Added tag(s) patch.
> tags 999280 + pending
Bug #999280 [src:empire-lafe] empire-lafe: missing required debian/rules 
targets build-arch and/or build-indep
Added tag(s) pending.

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

Bug#1023361: jupyter-core: CVE-2022-39286: Execution with Unnecessary Privileges in JupyterApp

[Salvatore Bonaccorso]

Source: jupyter-core
Version: 4.11.1-1
Severity: grave
Tags: security upstream
X-Debbugs-Cc: car...@debian.org, Debian Security Team 

Hi,

The following vulnerability was published for jupyter-core.

CVE-2022-39286[0]:
| Jupyter Core is a package for the core common functionality of Jupyter
| projects. Jupyter Core prior to version 4.11.2 contains an arbitrary
| code execution vulnerability in `jupyter_core` that stems from
| `jupyter_core` executing untrusted files in CWD. This vulnerability
| allows one user to run code as another. Version 4.11.2 contains a
| patch for this issue. There are no known workarounds.


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-39286
https://www.cve.org/CVERecord?id=CVE-2022-39286
[1] 
https://github.com/jupyter/jupyter_core/security/advisories/GHSA-m678-f26j-3hrp
[2] 
https://github.com/jupyter/jupyter_core/commit/1118c8ce01800cb689d51f655f5ccef19516e283

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore

Bug#1016070: marked as done (sbuild: autopkgtest fails with "No space left on device")

[Debian Bug Tracking System]

Your message dated Wed, 02 Nov 2022 21:06:14 +
with message-id 
and subject line Bug#1016070: fixed in sbuild 0.84.0
has caused the Debian Bug report #1016070,
regarding sbuild: autopkgtest fails with "No space left on device"
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.)


-- 
1016070: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1016070
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: sbuild
Version: 0.83.1
Severity: serious
X-Debbugs-Cc: jo...@debian.org, debian...@lists.debian.org

Dear Maintainer(s),

The autopkgtest run for sbuild keeps failing in debci, blocking other
packages migrations. The failure manifests in two different error
types, but both related to "No space left on device" when running
mmdebstrap.

This seems to have started on July the 22nd. List of recent failures:

https://ci.debian.net/packages/s/sbuild/testing/amd64/

Eg:

https://ci.debian.net/data/autopkgtest/unstable/amd64/s/sbuild/23951901/log.gz

+ mmdebstrap --mode=unshare --variant=apt unstable /tmp/chroot.tar
I: chroot architecture amd64 is equal to the host's architecture
I: automatically chosen format: tar
I: using /tmp/mmdebstrap.1Pi2WSLk6H as tempdir
I: running apt-get update...
I: downloading packages with apt...
I: extracting archives...
I: installing essential packages...
Selecting previously unselected package gcc-12-base:amd64.
(Reading database ... 0 files and directories currently installed.)
Preparing to unpack .../gcc-12-base_12.1.0-7_amd64.deb ...
Unpacking gcc-12-base:amd64 (12.1.0-7) ...
Selecting previously unselected package libc6:amd64.
Preparing to unpack .../libc6_2.33-8_amd64.deb ...
Use of uninitialized value in concatenation (.) or string at 
/usr/share/perl5/Debconf/Config.pm line 22.
Unpacking libc6:amd64 (2.33-8) ...
dpkg: error processing archive /var/cache/apt/archives/libc6_2.33-8_amd64.deb 
(--install):
 cannot copy extracted data for './usr/lib/x86_64-linux-gnu/gconv/IBM904.so' to 
'/usr/lib/x86_64-linux-gnu/gconv/IBM904.so.dpkg-new': failed to write (No space 
left on device)

Or:

https://ci.debian.net/data/autopkgtest/unstable/amd64/s/sbuild/24064827/log.gz

+ mmdebstrap --mode=unshare --variant=apt unstable /tmp/chroot.tar
I: chroot architecture amd64 is equal to the host's architecture
I: automatically chosen format: tar
I: using /tmp/mmdebstrap.CcPte840kk as tempdir
I: running apt-get update...
I: downloading packages with apt...
I: extracting archives...
tar: ./sbin/ldconfig: Wrote only 6144 of 10240 bytes
tar: ./usr/bin/catchsegv: Cannot write: No space left on device

-- 
Kind regards,
Luca Boccassi


signature.asc
Description: This is a digitally signed message part
--- End Message ---
--- Begin Message ---
Source: sbuild
Source-Version: 0.84.0
Done: Johannes Schauer Marin Rodrigues 

We believe that the bug you reported is fixed in the latest version of
sbuild, 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.
Johannes Schauer Marin Rodrigues  (supplier of updated sbuild 
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, 02 Nov 2022 21:42:11 +0100
Source: sbuild
Architecture: source
Version: 0.84.0
Distribution: unstable
Urgency: medium
Maintainer: sbuild maintainers 
Changed-By: Johannes Schauer Marin Rodrigues 
Closes: 1006135 1010665 1014574 1016070
Changes:
 sbuild (0.84.0) unstable; urgency=medium
 .
   [ Johannes Schauer Marin Rodrigues ]
   * bin/sbuild-createchroot: die if move() fails
   * bin/sbuild-debian-developer-setup: Don't alias to sid/UNRELEASED if suite
 is not unstable (Closes: #1014574)
   * debian/copyright: update copyright for makefiles and debian/*
   * debian/tests/unshare-qemuwrapper: allow ~/.ssh to exist already
   * debian/tests/unshare-qemuwrapper: bump disk size to 4G (Closes: #1016070)
   * debian/tests/unshare: don't fail if gpghome cannot be removed
   * debian/tests/unshare: gpgconf --kill all before removing gpghome
   * debian/tests/unshare: run with --no-source-only-changes
   * debian/tests/unshare: run with --nolog to output log to stdout
   * lib/Sbuild/Bui

Processed: dsh: diff for NMU version 0.25.10-1.5

[Debian Bug Tracking System]

Processing control commands:

> tags 999207 + patch
Bug #999207 [src:dsh] dsh: missing required debian/rules targets build-arch 
and/or build-indep
Added tag(s) patch.
> tags 999207 + pending
Bug #999207 [src:dsh] dsh: missing required debian/rules targets build-arch 
and/or build-indep
Added tag(s) pending.

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

Bug#999207: dsh: diff for NMU version 0.25.10-1.5

[Marcos Talau]

Control: tags 999207 + patch
Control: tags 999207 + pending


Dear maintainer,

I've prepared an NMU for dsh (versioned as 0.25.10-1.5) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should delay it longer.

Regards.
diff -u dsh-0.25.10/debian/changelog dsh-0.25.10/debian/changelog
--- dsh-0.25.10/debian/changelog
+++ dsh-0.25.10/debian/changelog
@@ -1,3 +1,10 @@
+dsh (0.25.10-1.5) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * debian/rules: Add build-{arch,indep} (Closes: #999207).
+
+ -- Marcos Talau   Wed, 02 Nov 2022 18:03:11 -0300
+
 dsh (0.25.10-1.4) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -u dsh-0.25.10/debian/rules dsh-0.25.10/debian/rules
--- dsh-0.25.10/debian/rules
+++ dsh-0.25.10/debian/rules
@@ -85,4 +85,8 @@
 	dh_builddeb
 
 binary: binary-indep binary-arch
-.PHONY: build clean binary-indep binary-arch binary install configure
+
+build-arch: build
+build-indep: build
+
+.PHONY: build build-arch build-indep clean binary-indep binary-arch binary install configure

Processed: dircproxy: diff for NMU version 1.0.5-6.1

[Debian Bug Tracking System]

Processing control commands:

> tags 999031 + patch
Bug #999031 [src:dircproxy] dircproxy: missing required debian/rules targets 
build-arch and/or build-indep
Added tag(s) patch.
> tags 999031 + pending
Bug #999031 [src:dircproxy] dircproxy: missing required debian/rules targets 
build-arch and/or build-indep
Added tag(s) pending.

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

Bug#999031: dircproxy: diff for NMU version 1.0.5-6.1

[Marcos Talau]

Control: tags 999031 + patch
Control: tags 999031 + pending


Dear maintainer,

I've prepared an NMU for dircproxy (versioned as 1.0.5-6.1) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should delay it longer.

Regards.
diff -u dircproxy-1.0.5/debian/changelog dircproxy-1.0.5/debian/changelog
--- dircproxy-1.0.5/debian/changelog
+++ dircproxy-1.0.5/debian/changelog
@@ -1,3 +1,10 @@
+dircproxy (1.0.5-6.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * debian/rules: Add build-{arch,indep} (Closes: #999031).
+
+ -- Marcos Talau   Wed, 02 Nov 2022 17:57:57 -0300
+
 dircproxy (1.0.5-6) unstable; urgency=medium
 
   * Upgrade to debhelper 9. (Closes: #817431)
diff -u dircproxy-1.0.5/debian/rules dircproxy-1.0.5/debian/rules
--- dircproxy-1.0.5/debian/rules
+++ dircproxy-1.0.5/debian/rules
@@ -80,4 +80,8 @@
 	dh_builddeb
 
 binary: binary-indep binary-arch
-.PHONY: build clean binary-indep binary-arch binary install configure
+
+build-arch: build
+build-indep: build
+
+.PHONY: build build-arch build-indep clean binary-indep binary-arch binary install configure

Processed: deps: diff for NMU version 0.13-4.2

[Debian Bug Tracking System]

Processing control commands:

> tags 999186 + patch
Bug #999186 [src:deps] deps: missing required debian/rules targets build-arch 
and/or build-indep
Added tag(s) patch.
> tags 999186 + pending
Bug #999186 [src:deps] deps: missing required debian/rules targets build-arch 
and/or build-indep
Added tag(s) pending.

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

Bug#999186: deps: diff for NMU version 0.13-4.2

[Marcos Talau]

Control: tags 999186 + patch
Control: tags 999186 + pending


Dear maintainer,

I've prepared an NMU for deps (versioned as 0.13-4.2) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should delay it longer.

Regards.
diff -u deps-0.13/debian/changelog deps-0.13/debian/changelog
--- deps-0.13/debian/changelog
+++ deps-0.13/debian/changelog
@@ -1,3 +1,10 @@
+deps (0.13-4.2) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * debian/rules: Add build-{arch,indep} (Closes: #999186).
+
+ -- Marcos Talau   Wed, 02 Nov 2022 17:52:37 -0300
+
 deps (0.13-4.1) unstable; urgency=medium
 
   * Non maintainer upload by the Reproducible Builds team.
diff -u deps-0.13/debian/rules deps-0.13/debian/rules
--- deps-0.13/debian/rules
+++ deps-0.13/debian/rules
@@ -76,4 +76,8 @@
 	@echo >&2 'source and diff are obsolete - use dpkg-source -b'; false
 
 binary: binary-indep binary-arch
-.PHONY: build clean binary-indep binary-arch binary
+
+build-arch: build
+build-indep: build
+
+.PHONY: build build-arch build-indep clean binary-indep binary-arch binary

Processed: cappuccino: diff for NMU version 0.5.1-10.1

[Debian Bug Tracking System]

Processing control commands:

> tags 999145 + patch
Bug #999145 [src:cappuccino] cappuccino: missing required debian/rules targets 
build-arch and/or build-indep
Added tag(s) patch.
> tags 999145 + pending
Bug #999145 [src:cappuccino] cappuccino: missing required debian/rules targets 
build-arch and/or build-indep
Added tag(s) pending.

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

Bug#999145: cappuccino: diff for NMU version 0.5.1-10.1

[Marcos Talau]

Control: tags 999145 + patch
Control: tags 999145 + pending


Dear maintainer,

I've prepared an NMU for cappuccino (versioned as 0.5.1-10.1) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should delay it longer.

Regards.
diff -u cappuccino-0.5.1/debian/changelog cappuccino-0.5.1/debian/changelog
--- cappuccino-0.5.1/debian/changelog
+++ cappuccino-0.5.1/debian/changelog
@@ -1,3 +1,10 @@
+cappuccino (0.5.1-10.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * debian/rules: Add build-{arch,indep} (Closes: #999145).
+
+ -- Marcos Talau   Wed, 02 Nov 2022 17:41:30 -0300
+
 cappuccino (0.5.1-10) unstable; urgency=medium
 
   * Bumped the compat version to 7. Closes: #965446
diff -u cappuccino-0.5.1/debian/rules cappuccino-0.5.1/debian/rules
--- cappuccino-0.5.1/debian/rules
+++ cappuccino-0.5.1/debian/rules
@@ -82,4 +82,8 @@
 binary-arch: build install
 
 binary: binary-indep binary-arch
-.PHONY: build clean binary-indep binary-arch binary install 
+
+build-arch: build
+build-indep: build
+
+.PHONY: build build-arch build-indep clean binary-indep binary-arch binary install 

Bug#1020995: marked as done (opengv: binary-all FTBFS)

[Debian Bug Tracking System]

Your message dated Wed, 02 Nov 2022 20:35:14 +
with message-id 
and subject line Bug#1020995: fixed in opengv 1.0+1git91f4b1-6
has caused the Debian Bug report #1020995,
regarding opengv: binary-all FTBFS
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1020995: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020995
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: opengv
Version: 1.0+1git91f4b1-5
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/fetch.php?pkg=opengv&arch=all&ver=1.0%2B1git91f4b1-5&stamp=1664256853&raw=0

...
   dh_auto_install -i
cd obj-x86_64-linux-gnu && make -j4 install 
DESTDIR=/<>/opengv-1.0\+1git91f4b1/debian/tmp AM_UPDATE_INFO_DIR=no 
"INSTALL=install --strip-program=true"
make[1]: Entering directory '/<>/obj-x86_64-linux-gnu'
/usr/bin/cmake -S/<> -B/<>/obj-x86_64-linux-gnu 
--check-build-system CMakeFiles/Makefile.cmake 0
make  -f CMakeFiles/Makefile2 preinstall
make[2]: Entering directory '/<>/obj-x86_64-linux-gnu'
make[2]: Nothing to be done for 'preinstall'.
make[2]: Leaving directory '/<>/obj-x86_64-linux-gnu'
Install the project...
/usr/bin/cmake -P cmake_install.cmake
-- Install configuration: "Release"
CMake Error at cmake_install.cmake:52 (file):
  file INSTALL cannot find
  "/<>/obj-x86_64-linux-gnu/lib/libopengv.so.1.0":
  No such file or directory.


make[1]: *** [Makefile:113: install] Error 1
--- End Message ---
--- Begin Message ---
Source: opengv
Source-Version: 1.0+1git91f4b1-6
Done: Dima Kogan 

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

Debian distribution maintenance software
pp.
Dima Kogan  (supplier of updated opengv 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, 02 Nov 2022 10:34:56 -0700
Source: opengv
Architecture: source
Version: 1.0+1git91f4b1-6
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Dima Kogan 
Closes: 1020995
Changes:
 opengv (1.0+1git91f4b1-6) unstable; urgency=medium
 .
   * Arch:all builds work (Closes: #1020995)
   * Added Build-Depends to fully build the docs
Checksums-Sha1:
 dfb24a905a29ba5e7e7be065efba828dfbaf7656 2333 opengv_1.0+1git91f4b1-6.dsc
 55f9f94a74b9ecf2a620cf024409a744394671ba 4552 
opengv_1.0+1git91f4b1-6.debian.tar.xz
 fb7f8f1a69a805ed05042cd1f764f6f1b0018000 12039 
opengv_1.0+1git91f4b1-6_amd64.buildinfo
Checksums-Sha256:
 81510ff267e588583c3038594b7833093bf7b1415e09c91c8d9d154e235b 2333 
opengv_1.0+1git91f4b1-6.dsc
 cce8232e60356b237a0ce99460c703aaadc4f1afca8cc75b37c40f9c915dc3ab 4552 
opengv_1.0+1git91f4b1-6.debian.tar.xz
 5c4463ed4eef8cc764e8a76acfa5ccac02b792e610fe5b8fbbc575f5c104b308 12039 
opengv_1.0+1git91f4b1-6_amd64.buildinfo
Files:
 6b1df975bfff348fa8791819fe940863 2333 libdevel optional 
opengv_1.0+1git91f4b1-6.dsc
 2246b48091876f6c8ce4f7594c9ff22e 4552 libdevel optional 
opengv_1.0+1git91f4b1-6.debian.tar.xz
 8ce1c306d820cdfa2b9d3eb4991c41e3 12039 libdevel optional 
opengv_1.0+1git91f4b1-6_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEteL6GQ/fmv4hiInPrMfCzzCUEYgFAmNiylwACgkQrMfCzzCU
EYj4YA/+JzGkyRi0wOeq84K/exJ9mEga8j2wMQgQHEFdGsaSNaw2rnIw5VkwZL+b
U/1iJPyfk0EzYot75wstlU6wPAG7ckO+Hz/rj4QEAk+wQkjz/iGUdFPQdpTmhYmC
bzrRM6xj8VKa2/tR5t+LTqQcBceno/GjobbO73rsBL1BJJc7Ogs1pOsC529DcsVY
jZUoTOQpzT7tZtvcykP5pNyRnCkdX2Xuh8mngBedqTpvVboTCwb9fSmb4c9VQn0+
/B0s9irAcJT/IxA1WhmtZ1zwlcS8a0ADpCIpYPVhrtZBPXne3XGCC8UX0RuvaHHB
bOEIf/osOv4Yb6EvyMZAN6Udp8k7lG9NqJz+Dozh0lH/iMRaIz/vAOp3XPlbfWSe
ckbpCvJ19VoX90esP4DUnnGUVApZ+ZtlqJNeSrDW1eHQTMsHECV8oevgZi2H5Zzw
+UZeWYU0sYF2EiAIk5/t/6VYaw0P7GQcunKd4OZ3EwNA8j2BkYTPZMO+G1zwATgy
aFVnstnZ7pY/XXV1/2iwMkd+6tH/WYedEEKndACHJtd7OfXMTK6sJ3xLD6JqvR+/
OhXnD+14q0O731FxxP8V4zKkWxZ0nf8F9knJXMHMDnzBWnmTF210iykHBZVheV3x
WzMi6t768JMIjUp42CpbwE9ERveiaxws4nNSHbCgXDQ9Q4rYQGg=
=SmFn
-END PGP SIGNATURE End Message ---

Bug#1023357: python3-morse-simulator: depends on non-existing python3 (< 3.9)

[Ralf Treinen]

Package: python3-morse-simulator
Version: 1.4-6+b1
Severity: serious

Hi,

python3-morse-simulator depends on python3 (< 3.9) which is only
satisfiable in oldstable or older.

-Ralf.

Bug#1023356: libdune-pdelab-dev: unsatisfiable dependency on libdune-common-2.7.0

[Ralf Treinen]

Package: libdune-pdelab-dev
Version: 2.7~20200605-2
Severity: serious

Hi,

this package depends on libdune-common-2.7.0 which does not exist in sid.

-Ralf.

Bug#1023355: limereg: depends on non-existing libboost-program-options1.67.0

[Ralf Treinen]

Package: limereg
Version: 1.4.1-4+b1
Severity: serious

Hi,

limereg depends on libboost-program-options1.67.0 which only exists in
oldstable.

-Ralf.

Bug#1019995: marked as done (supercollider: FTBFS: sndfile.h:356:33: error: conflicting declaration ‘typedef struct sf_private_tag SNDFILE’)

[Debian Bug Tracking System]

Your message dated Wed, 02 Nov 2022 19:14:24 +
with message-id 
and subject line Bug#1019995: fixed in supercollider 1:3.12.2+repack-1
has caused the Debian Bug report #1019995,
regarding supercollider: FTBFS: sndfile.h:356:33: error: conflicting 
declaration ‘typedef struct sf_private_tag SNDFILE’
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.)


-- 
1019995: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1019995
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: supercollider
Version: 1:3.11.2+repack-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220917 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> /usr/bin/c++ -DBOOST_CHRONO_HEADER_ONLY 
> -DBOOST_CONFIG_SUPPRESS_OUTDATED_MESSAGE -DBOOST_NO_AUTO_PTR 
> -DDiskIO_UGens_EXPORTS -DNOVA_SIMD -DSC_DATA_DIR=\"/usr/share/SuperCollider\" 
> -DSC_PLUGIN_EXT=\".so\" -I/<>/obj-x86_64-linux-gnu/common 
> -I/<>/external_libraries 
> -I/<>/external_libraries/nova-simd 
> -I/<>/external_libraries/nova-tt 
> -I/<>/include/common -I/<>/common 
> -I/<>/include/plugin_interface -g -O2 
> -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -D_LARGEFILE64_SOURCE 
> -fvisibility-inlines-hidden -O2 -g -DNDEBUG -fPIC   -fschedule-insns2 
> -fomit-frame-pointer -Wreturn-type -fno-math-errno -fno-signaling-nans 
> -fsigned-zeros -fno-associative-math -pthread -fvisibility=hidden 
> -fno-finite-math-only -std=gnu++11 -MD -MT 
> server/plugins/CMakeFiles/DiskIO_UGens.dir/DiskIO_UGens.cpp.o -MF 
> server/plugins/CMakeFiles/DiskIO_UGens.dir/DiskIO_UGens.cpp.o.d -o 
> server/plugins/CMakeFiles/DiskIO_UGens.dir/DiskIO_UGens.cpp.o -c 
> /<>/server/plugins/DiskIO_UGens.cpp
> In file included from /<>/server/plugins/DiskIO_UGens.cpp:27:
> /usr/include/sndfile.h:356:33: error: conflicting declaration ‘typedef struct 
> sf_private_tag SNDFILE’
>   356 | typedef struct sf_private_tag   SNDFILE ;
>   | ^~~
> In file included from /<>/include/plugin_interface/SC_World.h:26,
>  from 
> /<>/include/plugin_interface/SC_PlugIn.h:23,
>  from /<>/server/plugins/DiskIO_UGens.cpp:25:
> /<>/include/plugin_interface/SC_SndBuf.h:25:28: note: previous 
> declaration as ‘typedef struct SNDFILE_tag SNDFILE’
>25 | typedef struct SNDFILE_tag SNDFILE;
>   |^~~
> [68/571] /usr/bin/c++ -DBOOST_CHRONO_HEADER_ONLY 
> -DBOOST_CONFIG_SUPPRESS_OUTDATED_MESSAGE -DBOOST_NO_AUTO_PTR 
> -DChaosUGens_supernova_EXPORTS -DNOVA_SIMD 
> -DSC_DATA_DIR=\"/usr/share/SuperCollider\" -DSC_PLUGIN_EXT=\".so\" 
> -DSUPERNOVA -I/<>/obj-x86_64-linux-gnu/common 
> -I/<>/external_libraries 
> -I/<>/external_libraries/nova-simd 
> -I/<>/external_libraries/nova-tt 
> -I/<>/include/common -I/<>/common 
> -I/<>/include/plugin_interface -g -O2 
> -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -D_LARGEFILE64_SOURCE 
> -fvisibility-inlines-hidden -O2 -g -DNDEBUG -fPIC   -fschedule-insns2 
> -fomit-frame-pointer -Wreturn-type -fno-math-errno -fno-signaling-nans 
> -fsigned-zeros -fno-associative-math -pthread -fvisibility=hidden 
> -fno-finite-math-only -std=gnu++11 -MD -MT 
> server/plugins/CMakeFiles/ChaosUGens_supernova.dir/ChaosUGens.cpp.o -MF 
> server/plugins/CMakeFiles/ChaosUGens_supernova.dir/ChaosUGens.cpp.o.d -o 
> server/plugins/CMakeFiles/ChaosUGens_supernova.dir/ChaosUGens.cpp.o -c 
> /<>/server/plugins/ChaosUGens.cpp
> [69/571] /usr/bin/c++ -DBOOST_CHRONO_HEADER_ONLY 
> -DBOOST_CONFIG_SUPPRESS_OUTDATED_MESSAGE -DBOOST_NO_AUTO_PTR 
> -DDemandUGens_supernova_EXPORTS -DNOVA_SIMD 
> -DSC_DATA_DIR=\"/usr/share/SuperCollider\" -DSC_PLUGIN_EXT=\".so\" 
> -DSUPERNOVA -I/<>/obj-x86_64-linux-gnu/common 
> -I/<>/external_libraries 
> -I/<>/external_libraries/nova-simd 
> -I/<>/external_libraries/nova-tt 
> -I/<>/include/common -I/<>/common 
> -I/<>/include/plugin_interface -g -O2 
> -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -D_LARGEFILE64_SOURCE 
> -fvisibility-inlines-hidden -O2 -g -DNDEBUG -fPIC   -fschedule-insns2 
> -fomit-frame-pointer -Wreturn-type -fno-math-errno -fno-signaling-nans 
> -fsigned-zeros -fno-associative-math -pthread -fvisibility=hidden 
> -fno-finite-math-only -std=gnu++11 -MD -MT 
> server/plugins/CMakeFiles/DemandUGens_supernova.dir/

Bug#1022991: marked as done (libc6: broken y2038 support in fstatat on mips64el)

[Debian Bug Tracking System]

Your message dated Wed, 02 Nov 2022 19:06:24 +
with message-id 
and subject line Bug#1022991: fixed in glibc 2.36-4
has caused the Debian Bug report #1022991,
regarding libc6: broken y2038 support in fstatat on mips64el
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.)


-- 
1022991: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022991
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libc6
Version: 2.35-1
Severity: critical
Tags: upstream
Justification: breaks unrelated software

On mips64el the fstat/fstatat/lstat functions return EOVERFLOW when they
are called on files with a mtime, atime or ctime that can't be
represented within a 32-bit time_t. This should not happen as time_t is
64-bit on mips64el. This is a regression from glibc 2.34 and can be
reproduce with:

(sid_mips64el-dchroot)aurel32@eller:~$ touch -d 20390101 t
(sid_mips64el-dchroot)aurel32@eller:~$ chmod +x t
chmod: cannot access 't': Value too large for defined data type
(sid_mips64el-dchroot)aurel32@eller:~$ 

This breaks unrelated software, for instance the build of gcc-12 on the
build daemons:

https://buildd.debian.org/status/fetch.php?pkg=gcc-12&arch=mips64el&ver=12.2.0-7&stamp=1666806816&raw=0
--- End Message ---
--- Begin Message ---
Source: glibc
Source-Version: 2.36-4
Done: Aurelien Jarno 

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

Debian distribution maintenance software
pp.
Aurelien Jarno  (supplier of updated glibc 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, 02 Nov 2022 19:43:41 +0100
Source: glibc
Architecture: source
Version: 2.36-4
Distribution: unstable
Urgency: medium
Maintainer: GNU Libc Maintainers 
Changed-By: Aurelien Jarno 
Closes: 1022991
Changes:
 glibc (2.36-4) unstable; urgency=medium
 .
   [ Aurelien Jarno ]
   * debian/patches/git-updates.diff: update from upstream stable branch:
 - Fix y2038 support in fstatat on mips64el.  Closes: #1022991.
Checksums-Sha1:
 2f65a0280dd4bba00369ec73af11df0b4c77b100 9689 glibc_2.36-4.dsc
 2eae0688fb1ec9aae0a71176053190c379d34924 816032 glibc_2.36-4.debian.tar.xz
 d30cabdfb9f3b72d749c48e3e502c1e632ff3172 9480 glibc_2.36-4_source.buildinfo
Checksums-Sha256:
 bf163e3b70bddfea14798ac3e1bd132e774ab16cf033c7491aa42c0afd7d4c63 9689 
glibc_2.36-4.dsc
 181cd7afb6026445a6917249f5e7327f522ed6693bde511777934c11f457668b 816032 
glibc_2.36-4.debian.tar.xz
 5eba89048850cc8b66468916dc44666c68c6a7a0a5caf1404e6ba4cb9a9003f7 9480 
glibc_2.36-4_source.buildinfo
Files:
 4621f14ddc2aa6290ebd590501a51f31 9689 libs required glibc_2.36-4.dsc
 3b8940e5bf199866e031a7b39d4252db 816032 libs required 
glibc_2.36-4.debian.tar.xz
 0e790c8978dc058873051a5449643729 9480 libs required 
glibc_2.36-4_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEUryGlb40+QrX1Ay4E4jA+JnoM2sFAmNivUMACgkQE4jA+Jno
M2vAFxAAkbaLAAWKFRmDQ7UDAMFUcKFf5oC+LbFelNvMyx+jcGp9yxHEDLssHkh1
R2AWmYSsxJVRzFz21dCk9wTde4kN0Lm7ta2RY7NLAdTR1UTT2rziuM+8VLb7EVDw
pJH1GQhcIdn6GYmrDcvJL8ooww5DKBQJrgrDWgR9Sk9yKuZJRD9fBj4bk4qVtOAj
1RdQGSFZ4PBGWZWSsP8ioLKncSK72KYycjBJN3i0vJKT5cNAeueaCBJ+h0pREhq/
6klxxTVuRnJztXcMt/FnE+YBMgHlPt8atWcJVSwVZPdw7QxpCTdgFEHtwaaLQsqe
oqZj05Urx4PIqxl9hqg2ZeAbwO29Rz4gyqCiMaReKeLxxFKtGmpk76yxTyGLARqX
lb32L7d+oRYWTV4Zc9yZsO9icBai5ku5dTmEcxqKf5czCMYo3w9SKaHerHaJVnZD
eTEejGUiy6zlKezWHGTMymeGYSu+7IKHd9y4l+kGLAJBzyQNA6PVxMrkMKUAB2Ho
CXXTsHtTyhIRKTkqf9NCXzUDZVFSbv5ghj/6D9a+id138xJTudCnW8yhbxNYNI50
BvjnitsDMdm5jWWsts11uZpVIsEZjX70iVaZBDV5J4VnNtnJGWfurRVMHlUiyFKL
u5mJXirHdJh01GHHorL8RLOxdXvTh5e9TDLVeNalJdfqv9ckrDI=
=iQ+l
-END PGP SIGNATURE End Message ---

Processed: Bug#1022991 marked as pending in glibc

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1022991 [libc6] libc6: broken y2038 support in fstatat on mips64el
Added tag(s) pending.

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

Bug#1022991: marked as pending in glibc

[Aurelien Jarno]

Control: tag -1 pending

Hello,

Bug #1022991 in glibc 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/glibc-team/glibc/-/commit/ce84023382625e960fa6e975d24893d516cfc63d


debian/patches/git-updates.diff: update from upstream stable branch:

* debian/patches/git-updates.diff: update from upstream stable branch:
  - Fix y2038 support in fstatat on mips64el.  Closes: #1022991.


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1022991

Bug#1007984: netpbm-free ready to upload

[Andreas Tille]

Hi Andreas,

Am Thu, Oct 06, 2022 at 07:09:13PM +0200 schrieb Andreas Metzler:
> > I noticed you added some missing information to d/copyright
> > of netpbm-free.  Thanks a lot for doing so.  Do you think it
> > is time for another upload?
> 
> I invested a couple of hours but sadly it is not a finished effort.

Thanks a lot again for spending your time.  I would appreciate if we
could make it some team effort to finally get this package in good
shape.  I'm personally quite occupied by fixing a couple of RC bugs in
Debian Med team so netpbm-free (which I do not use personally) has low
priority for me.  So any help is welcome.

Kind regards

 Andreas.

-- 
http://fam-tille.de

Processed: closing 1022458

[Debian Bug Tracking System]

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

> close 1022458 2.1.0-3
Bug #1022458 [src:pgl-ddl-deploy] pgl-ddl-deploy: FTBFS: Error: debian/control 
needs updating from debian/control.in. Run 'pg_buildext updatecontrol'.
Marked as fixed in versions pgl-ddl-deploy/2.1.0-3.
Bug #1022458 [src:pgl-ddl-deploy] pgl-ddl-deploy: FTBFS: Error: debian/control 
needs updating from debian/control.in. Run 'pg_buildext updatecontrol'.
Marked Bug as done
> thanks
Stopping processing here.

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

Processed: Re: Bug#1023348: Null dereference in dentry_unlink_inode / kswapd

[Debian Bug Tracking System]

Processing control commands:

> severity -1 normal
Bug #1023348 [src:linux] Null dereference in dentry_unlink_inode / kswapd
Severity set to 'normal' from 'critical'

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

Bug#1023348: Null dereference in dentry_unlink_inode / kswapd

[Diederik de Haas]

Control: severity -1 normal

On Wednesday, 2 November 2022 18:16:12 CET nmr wrote:
> Package: src:linux
> Version: 5.10.4-1

This is one of the very first 5.10.x versions! ...

> -- System Information:
> Debian Release: 11.5
>   APT prefers stable-security
>   APT policy: (500, 'stable-security'), (500, 'stable-debug'), (500, 'stable')

Stable-security currently has 5.10.149-2 and Debian release 11.5 was released
less then 2 months ago.
Your system seems configured correctly and up-to-date, but that doesn't match
your kernel version. Even the initial release of Bullseye was with a much newer
kernel version from the 5.10 series.

Lowering the severity until you can reproduce this issue with an up-to-date
kernel version.

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

Bug#998933: marked as done (cgilib: missing required debian/rules targets build-arch and/or build-indep)

[Debian Bug Tracking System]

Your message dated Wed, 02 Nov 2022 18:19:16 +
with message-id 
and subject line Bug#998933: fixed in cgilib 0.6-2
has caused the Debian Bug report #998933,
regarding cgilib: missing required debian/rules targets build-arch and/or 
build-indep
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.)


-- 
998933: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998933
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: cgilib
Version: 0.6-1.1
Severity: important
Justification: Debian Policy section 4.9
Tags: bookworm sid
User: debian...@lists.debian.org
Usertags: missing-build-arch-indep

Dear maintainer,

Your package does not include build-arch and/or build-indep targets in
debian/rules. This is required by Debian Policy section 4.9, since 2012.
https://www.debian.org/doc/debian-policy/ch-source.html#main-building-script-debian-rules

Please note that this is also a sign that the packaging of this software
could benefit from a refresh. For example, packages using 'dh' cannot be
affected by this issue.

This mass bug filing was discussed on debian-devel@ in
https://lists.debian.org/debian-devel/2021/11/msg00052.html .
The severity of this bug will be changed to 'serious' after a month.

Best,

Lucas
--- End Message ---
--- Begin Message ---
Source: cgilib
Source-Version: 0.6-2
Done: Marcos Talau 

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

Debian distribution maintenance software
pp.
Marcos Talau  (supplier of updated cgilib 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, 02 Nov 2022 14:51:59 -0300
Source: cgilib
Architecture: source
Version: 0.6-2
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: Marcos Talau 
Closes: 998933
Changes:
 cgilib (0.6-2) unstable; urgency=medium
 .
   * QA upload.
   * Set maintainer to Debian QA Group . (see: #934416)
   * debian/rules: Add build-{arch,indep} (Closes: #998933).
Checksums-Sha1:
 fd811adc266fe13d36e9977bfff0029e3ad718d6 1574 cgilib_0.6-2.dsc
 3497b90b718f02f0dd480937e7dd658b675d61d6 5431 cgilib_0.6-2.diff.gz
 5e3b86fac5b6e2cb800d453c741575b37bd1ba6e 4757 cgilib_0.6-2_source.buildinfo
Checksums-Sha256:
 af6762203d7c16b4c26a22cb606df0613562bc6e981e132be81d59f3c4b9f893 1574 
cgilib_0.6-2.dsc
 4390eb9736386e1a4d750a5dcbcf96301c565d1731a107ec5d082140aa13d598 5431 
cgilib_0.6-2.diff.gz
 ae14eb0bbf410cfc387fe21e39bd88ee6bead30e13699e658b6a94fcb6d5c8a6 4757 
cgilib_0.6-2_source.buildinfo
Files:
 74e33e98ab4a17192c62090221645a4e 1574 web optional cgilib_0.6-2.dsc
 5c1787952a6393dfaf61ef43db9d50de 5431 web optional cgilib_0.6-2.diff.gz
 503043951dd43e9a81a81b1233e06cad 4757 web optional 
cgilib_0.6-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEtSLzkVnaB9053AsR9LqqgNsoukwFAmNir2MACgkQ9LqqgNso
ukwqig/+Nm8ScbgqK1Uo9c+fy9tVxetPEiyK70sc4y8fgaSEH+mH2kcJHQVkWD9c
Fk0Kri0NnRxvVhnMHTf7oNWp2o1BrZnOaMiAH/K11AwizOL2a8vsikA3i4o8bzg5
tA+fCyYpVENi3JoLwmclNpixyw3SJn45Rh0Vrt0xdAiU2sTHtddh8cxzU4ARZl6I
5yiIK/8shR59AF9ioId3id6m5FUHKAlAPh13JGV8sTzThz3NBLibZR8IQwPKQsnS
R5US4/I5SHYvCNnIKH1PZ4OGNsSMz7B9pj6n2etCZFSIwl9jJc5Osddjaaatw5g9
iL6om+zyUoc+Plb2jgj7ls3OE9Iuqxbr6MZYwETxGmfdvDiZILT/989LCm8tLZWv
KzmZm8MYWBdGEeGi5kGoy0pcpesfHLxxI7qljspcyrbq43o2Q2IZxNTzdIHMlR3k
NWix+Ex6/YnNK8V9JuWkAS8/69Pl3jBKVcKQmB3dXnuoRZ5U70yLZPes+rN7Tf1n
Uyhsqe3mS0u/3oVNbFawO8WClrgyuBFvStovlnxrvSExz5fnE10eQPNc5QjfGWtO
LUiIZwbHQN/UYdK/xwxu/oU7Yxte0Y4FRNOC+s7ju9yLpXJP2c94D4VpUXoT4Z6h
HlFS4FXFz8c0uJnhnf5CKSpQPhxycXLaiLafpmvihW7csRh6K6k=
=PHzU
-END PGP SIGNATURE End Message ---

Bug#1023224: [Pkg-swan-devel] Bug#1023224: strongswan: autopkgtest regression: depends on no longer built strongswan-scepclient

[Paul Gevers]

Hi Yves-Alexis,

On 02-11-2022 17:27, Yves-Alexis Perez wrote:

I'm not sure why the test is failing then and what I should have done
differently. Could you give me some pointers here?


https://sources.debian.org/src/strongswan/5.9.8-1/debian/tests/control/

line 2 says that the *first* two tests Depends on strongswan-scepclient. 
That means that autopkgtests tries to install that binary package, which 
fails because it's no longer available. Either remove the tests (if they 
need that binary), or adapt the Depends line to what is required for the 
test.


Paul


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1022478: closing 1022478

[Christoph Berg]

close 1022478 1.4.2-2
thanks

Processed: closing 1022522

[Debian Bug Tracking System]

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

> close 1022522 1:2.0.10-5
Bug #1022522 {Done: Christoph Berg } [src:postgresql-pllua] 
postgresql-pllua: FTBFS: Error: debian/control needs updating from 
debian/control.in. Run 'pg_buildext updatecontrol'.
Ignoring request to alter fixed versions of bug #1022522 to the same values 
previously set
Bug #1022522 {Done: Christoph Berg } [src:postgresql-pllua] 
postgresql-pllua: FTBFS: Error: debian/control needs updating from 
debian/control.in. Run 'pg_buildext updatecontrol'.
Bug 1022522 is already marked as done; not doing anything.
> thanks
Stopping processing here.

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

Bug#1022522: closing 1022522

[Christoph Berg]

close 1022522 1:2.0.10-5
thanks

Processed: closing 1022478

[Debian Bug Tracking System]

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

> close 1022478 1.4.2-2
Bug #1022478 {Done: Christoph Berg } [src:pg-cron] pg-cron: 
FTBFS: Error: debian/control needs updating from debian/control.in. Run 
'pg_buildext updatecontrol'.
Ignoring request to alter fixed versions of bug #1022478 to the same values 
previously set
Bug #1022478 {Done: Christoph Berg } [src:pg-cron] pg-cron: 
FTBFS: Error: debian/control needs updating from debian/control.in. Run 
'pg_buildext updatecontrol'.
Bug 1022478 is already marked as done; not doing anything.
> thanks
Stopping processing here.

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

Processed: closing 1022522

[Debian Bug Tracking System]

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

> close 1022522 1:2.0.10-5
Bug #1022522 [src:postgresql-pllua] postgresql-pllua: FTBFS: Error: 
debian/control needs updating from debian/control.in. Run 'pg_buildext 
updatecontrol'.
Marked as fixed in versions postgresql-pllua/1:2.0.10-5.
Bug #1022522 [src:postgresql-pllua] postgresql-pllua: FTBFS: Error: 
debian/control needs updating from debian/control.in. Run 'pg_buildext 
updatecontrol'.
Marked Bug as done
> thanks
Stopping processing here.

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

Processed: closing 1022478

[Debian Bug Tracking System]

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

> close 1022478 1.4.2-2
Bug #1022478 [src:pg-cron] pg-cron: FTBFS: Error: debian/control needs updating 
from debian/control.in. Run 'pg_buildext updatecontrol'.
Marked as fixed in versions pg-cron/1.4.2-2.
Bug #1022478 [src:pg-cron] pg-cron: FTBFS: Error: debian/control needs updating 
from debian/control.in. Run 'pg_buildext updatecontrol'.
Marked Bug as done
> thanks
Stopping processing here.

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

Processed: found 1022957 in 0.0.0+git.2021.03.30.1a3320dab9-2

[Debian Bug Tracking System]

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

> found 1022957 0.0.0+git.2021.03.30.1a3320dab9-2
Bug #1022957 [nex] nex: /usr/bin/nex is already provided by the nvi package
Marked as found in versions 
golang-github-blynn-nex/0.0.0+git.2021.03.30.1a3320dab9-2.
> thanks
Stopping processing here.

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

Bug#1023348: amended syslog snippet

[Nathan Ramsey]

I missed the first three lines of the syslog snippet
containing the BUG event, inlined here:

Oct 31 16:27:48 gonzo kernel: BUG: kernel NULL pointer dereference, address: 
0028
Oct 31 16:27:48 gonzo kernel: #PF: supervisor write access in kernel mode
Oct 31 16:27:48 gonzo kernel: #PF: error_code(0x0002) - not-present page
Oct 31 16:27:49 gonzo kernel: PGD 800121c24067 P4D 800121c24067 PUD 
1079bf067 PMD 0 
Oct 31 16:27:49 gonzo kernel: Oops: 0002 [#1] SMP PTI
Oct 31 16:27:49 gonzo kernel: CPU: 9 PID: 296 Comm: kswapd0 Tainted: G  
I   5.10.0-1-amd64 #1 Debian 5.10.4-1
Oct 31 16:27:49 gonzo kernel: Hardware name: System manufacturer System Product 
Name/ROG STRIX X299-E GAMING, BIOS 1503 08/03/2018
Oct 31 16:27:49 gonzo kernel: RIP: 0010:dentry_unlink_inode+0x51/0x100
Oct 31 16:27:49 gonzo kernel: Code: a9 00 00 08 00 74 08 65 48 ff 05 8a 45 75 
52 48 8b 85 b8 00 00 00 48 85 c0 74 29 48 8b 95 b0 00 00 00 48 89 10 48 85 d2 
74 04 <4>
Oct 31 16:27:49 gonzo kernel: RSP: 0018:b59d00a13b58 EFLAGS: 00010202
Oct 31 16:27:49 gonzo kernel: RAX: 9e2fbb8db9f8 RBX: 9e335a601740 RCX: 

Oct 31 16:27:49 gonzo kernel: RDX: 0020 RSI: 9e3466229350 RDI: 
9e34662292c0
Oct 31 16:27:49 gonzo kernel: RBP: 9e34662292c0 R08: 9e34662282d0 R09: 
9e2706d3e260
Oct 31 16:27:49 gonzo kernel: R10:  R11:  R12: 
9e2fbb8db8c0
Oct 31 16:27:49 gonzo kernel: R13: 9e3466229318 R14: 9e2760c01870 R15: 

Oct 31 16:27:49 gonzo kernel: FS:  () 
GS:9e365fa4() knlGS:
Oct 31 16:27:49 gonzo kernel: CS:  0010 DS:  ES:  CR0: 80050033
Oct 31 16:27:49 gonzo kernel: CR2: 0028 CR3: 000107aac004 CR4: 
003706e0
Oct 31 16:27:49 gonzo kernel: DR0:  DR1:  DR2: 

Oct 31 16:27:49 gonzo kernel: DR3:  DR6: fffe0ff0 DR7: 
0400
Oct 31 16:27:49 gonzo kernel: Call Trace:
Oct 31 16:27:49 gonzo kernel:  __dentry_kill+0xe4/0x180
Oct 31 16:27:49 gonzo kernel:  shrink_dentry_list+0x4e/0xc0
Oct 31 16:27:49 gonzo kernel:  prune_dcache_sb+0x54/0x80
Oct 31 16:27:49 gonzo kernel:  super_cache_scan+0x12c/0x1e0
Oct 31 16:27:49 gonzo kernel:  do_shrink_slab+0x145/0x240
Oct 31 16:27:49 gonzo kernel:  shrink_slab+0x188/0x2a0
Oct 31 16:27:49 gonzo kernel:  shrink_node+0x2c0/0x6e0
Oct 31 16:27:49 gonzo kernel:  balance_pgdat+0x2e5/0x600
Oct 31 16:27:49 gonzo kernel:  kswapd+0x1f6/0x380
Oct 31 16:27:49 gonzo kernel:  ? add_wait_queue_exclusive+0x70/0x70
Oct 31 16:27:49 gonzo kernel:  ? balance_pgdat+0x600/0x600
Oct 31 16:27:49 gonzo kernel:  kthread+0x11b/0x140
Oct 31 16:27:49 gonzo kernel:  ? __kthread_bind_mask+0x60/0x60
Oct 31 16:27:49 gonzo kernel:  ret_from_fork+0x22/0x30
Oct 31 16:27:49 gonzo kernel: Modules linked in: xt_MASQUERADE xt_mark 
nft_compat nft_chain_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 
nft_counter nf_tab>
Oct 31 16:27:49 gonzo kernel:  mei_me sg watchdog mei ioatdma dca evdev drm 
fuse configfs efivarfs ip_tables x_tables autofs4 ext4 crc16 mbcache jbd2 
raid10 raid456>
Oct 31 16:27:49 gonzo kernel: CR2: 0028
Oct 31 16:27:49 gonzo kernel: ---[ end trace 3c3f518d326d4df8 ]---
Oct 31 16:27:49 gonzo kernel: RIP: 0010:dentry_unlink_inode+0x51/0x100
Oct 31 16:27:49 gonzo kernel: Code: a9 00 00 08 00 74 08 65 48 ff 05 8a 45 75 
52 48 8b 85 b8 00 00 00 48 85 c0 74 29 48 8b 95 b0 00 00 00 48 89 10 48 85 d2 
74 04 <4>
Oct 31 16:27:49 gonzo kernel: RSP: 0018:b59d00a13b58 EFLAGS: 00010202
Oct 31 16:27:49 gonzo kernel: RAX: 9e2fbb8db9f8 RBX: 9e335a601740 RCX: 

Oct 31 16:27:49 gonzo kernel: RDX: 0020 RSI: 9e3466229350 RDI: 
9e34662292c0
Oct 31 16:27:49 gonzo kernel: RBP: 9e34662292c0 R08: 9e34662282d0 R09: 
9e2706d3e260
Oct 31 16:27:49 gonzo kernel: R10:  R11:  R12: 
9e2fbb8db8c0
Oct 31 16:27:49 gonzo kernel: R13: 9e3466229318 R14: 9e2760c01870 R15: 

Oct 31 16:27:49 gonzo kernel: FS:  () 
GS:9e365fa4() knlGS:
Oct 31 16:27:49 gonzo kernel: CS:  0010 DS:  ES:  CR0: 80050033
Oct 31 16:27:49 gonzo kernel: CR2: 0028 CR3: 000107aac004 CR4: 
003706e0
Oct 31 16:27:49 gonzo kernel: DR0:  DR1:  DR2: 

Oct 31 16:27:49 gonzo kernel: DR3:  DR6: fffe0ff0 DR7: 
0400

Bug#1023348: Null dereference in dentry_unlink_inode / kswapd

[nmr]

Package: src:linux
Version: 5.10.4-1
Severity: critical
Tags: upstream
X-Debbugs-Cc: nat...@acmeaom.com

Apologies if this isn't the right venue for this, doing
my best here.

Attachment descriptions

b1 - syslog from BUG event 
b2 - syslog from 12+ hours later preceding total system hang
b3 - hdparm -I /dev/sda
b4 - smartctl -a /dev/sda

As seen in /dev/sda appears to be running old firmware, and
it is hosting the swap volume.


-- Package-specific info:
** Version:
Linux version 5.10.0-1-amd64 (debian-ker...@lists.debian.org) (gcc-10 (Debian 
10.2.1-3) 10.2.1 20201224, GNU ld (GNU Binutils for Debian) 2.35.1) #1 SMP 
Debian 5.10.4-1 (2020-12-31)

** Command line:
BOOT_IMAGE=/boot/vmlinuz-5.10.0-1-amd64 
root=UUID=25ffc6b2-d247-4531-8a8e-b6e8da5c6b36 ro quiet

** Tainted: I (2048)
 * workaround for bug in platform firmware applied

** Kernel log:
[5.389178] platform regulatory.0: firmware: failed to load regulatory.db 
(-2)
[5.389202] firmware_class: See https://wiki.debian.org/Firmware for 
information about missing firmware
[5.389226] platform regulatory.0: Direct firmware load for regulatory.db 
failed with error -2
[5.389228] cfg80211: failed to load regulatory.db
[5.411695] Adding 66771964k swap on /dev/sda5.  Priority:-2 extents:1 
across:66771964k SSFS
[5.457679] audit: type=1400 audit(1667325565.555:2): apparmor="STATUS" 
operation="profile_load" profile="unconfined" name="libreoffice-senddoc" 
pid=764 comm="apparmor_parser"
[5.457792] audit: type=1400 audit(1667325565.555:3): apparmor="STATUS" 
operation="profile_load" profile="unconfined" name="postgresql_akonadi" pid=762 
comm="apparmor_parser"
[5.457859] audit: type=1400 audit(1667325565.555:4): apparmor="STATUS" 
operation="profile_load" profile="unconfined" name="libreoffice-xpdfimport" 
pid=763 comm="apparmor_parser"
[5.457885] audit: type=1400 audit(1667325565.555:5): apparmor="STATUS" 
operation="profile_load" profile="unconfined" name="/usr/sbin/haveged" pid=767 
comm="apparmor_parser"
[5.457940] audit: type=1400 audit(1667325565.555:6): apparmor="STATUS" 
operation="profile_load" profile="unconfined" name="lsb_release" pid=771 
comm="apparmor_parser"
[5.458475] audit: type=1400 audit(1667325565.555:7): apparmor="STATUS" 
operation="profile_load" profile="unconfined" 
name="/usr/libexec/ibus-engine-hangul" pid=758 comm="apparmor_parser"
[5.458545] audit: type=1400 audit(1667325565.555:8): apparmor="STATUS" 
operation="profile_load" profile="unconfined" name="libreoffice-oopslash" 
pid=765 comm="apparmor_parser"
[5.458708] audit: type=1400 audit(1667325565.555:9): apparmor="STATUS" 
operation="profile_load" profile="unconfined" name="/usr/bin/man" pid=769 
comm="apparmor_parser"
[5.458711] audit: type=1400 audit(1667325565.555:10): apparmor="STATUS" 
operation="profile_load" profile="unconfined" name="man_filter" pid=769 
comm="apparmor_parser"
[5.458713] audit: type=1400 audit(1667325565.555:11): apparmor="STATUS" 
operation="profile_load" profile="unconfined" name="man_groff" pid=769 
comm="apparmor_parser"
[5.577234] snd_hda_intel :65:00.1: Disabling MSI
[5.577274] snd_hda_intel :65:00.1: Handle vga_switcheroo audio client
[5.578996] alg: No test for fips(ansi_cprng) (fips_ansi_cprng)
[5.631557] input: HDA NVidia HDMI/DP,pcm=3 as 
/devices/pci:64/:64:00.0/:65:00.1/sound/card1/input9
[5.631597] input: HDA NVidia HDMI/DP,pcm=7 as 
/devices/pci:64/:64:00.0/:65:00.1/sound/card1/input10
[5.631632] input: HDA NVidia HDMI/DP,pcm=8 as 
/devices/pci:64/:64:00.0/:65:00.1/sound/card1/input11
[5.631663] input: HDA NVidia HDMI/DP,pcm=9 as 
/devices/pci:64/:64:00.0/:65:00.1/sound/card1/input12
[5.631726] input: HDA NVidia HDMI/DP,pcm=10 as 
/devices/pci:64/:64:00.0/:65:00.1/sound/card1/input13
[5.631779] input: HDA NVidia HDMI/DP,pcm=11 as 
/devices/pci:64/:64:00.0/:65:00.1/sound/card1/input14
[5.631821] input: HDA NVidia HDMI/DP,pcm=12 as 
/devices/pci:64/:64:00.0/:65:00.1/sound/card1/input15
[5.641972] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC1220: 
line_outs=3 (0x14/0x15/0x16/0x0/0x0) type:line
[5.641974] snd_hda_codec_realtek hdaudioC0D0:speaker_outs=0 
(0x0/0x0/0x0/0x0/0x0)
[5.641975] snd_hda_codec_realtek hdaudioC0D0:hp_outs=1 
(0x1b/0x0/0x0/0x0/0x0)
[5.641976] snd_hda_codec_realtek hdaudioC0D0:mono: mono_out=0x0
[5.641977] snd_hda_codec_realtek hdaudioC0D0:dig-out=0x1e/0x0
[5.641977] snd_hda_codec_realtek hdaudioC0D0:inputs:
[5.641978] snd_hda_codec_realtek hdaudioC0D0:  Front Mic=0x19
[5.641979] snd_hda_codec_realtek hdaudioC0D0:  Rear Mic=0x18
[5.641980] snd_hda_codec_realtek hdaudioC0D0:  Line=0x1a
[5.649634] rtw_8822be :02:00.0: enabling device ( -> 0003)
[5.654652] rtw_8822be :02:00.0: firmware: direct-loading firmware 
rtw88/rtw8822b_fw.bin
[5.65

Bug#998933: cgilib: diff for NMU version 0.6-1.2

[Marcos Talau]

Hi Andreas!

On Wed, Nov 02, 2022 at 02:50:12PM +0100, Andreas Beckmann wrote:
[...]
> cgilib is orphaned, so you should rather do a QA upload ;-)
> 

Heheh, sorry for that, and thanks for the info :D

The Maintainer field has not been changed, and I prepared a series of NMUs
against the same issue.

I will cancel the NMU and do a QA to fix the issue, and I'm going to take the
opportunity to update the Maintainer field to Debian QA Group.


Best Regards,
mt


signature.asc
Description: PGP signature

Bug#1023224: [Pkg-swan-devel] Bug#1023224: strongswan: autopkgtest regression: depends on no longer built strongswan-scepclient

[Yves-Alexis Perez]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

On Mon, 2022-10-31 at 21:01 +0100, Paul Gevers wrote:
> With a recent upload of strongswan the autopkgtest of strongswan fails 
> in testing when that autopkgtest is run with the binary packages of 
> strongswan from unstable. It passes when run with only packages from 
> testing. In tabular form:
> 
>     pass    fail
> strongswan from testing    5.9.8-1
> all others from testing    from testing
> 
> I copied some of the output at the bottom of this report. The 
> autopkgtest d/t/control files says the first test depends on 
> strongswan-scepclient, but src:strongswan no long build it.

Hi Paul, thanks for the report but I'm not sure I totally understand it. The
strongswan-scepclient has indeed been removed in the 5.9.8 upload, so it's
definitely gone.

I'm not sure why the test is failing then and what I should have done
differently. Could you give me some pointers here?

Regards,
- -- 
Yves-Alexis
-BEGIN PGP SIGNATURE-

iQEzBAEBCAAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAmNimmoACgkQ3rYcyPpX
RFtBzQf9H4dH0IMrBRuVBPPuYYm7l+61bvbp/+dtmqkw2dKGJFKTEKkH1+pEb8jl
0uWNXEONd1CjiwcNigt5/O+qhhsrX5t08RlQ3QdALuOyb8vpFmAX/mlI2peakRyF
daAuXvyyYRxa1827X894dsuKA/YZMe6UtlvraxyJsJTjZCTOI9LpeMDaMnXv5hwO
GXt/Dyg399FY9IZCgotIwY/8VbTLxPSCNE72vNyx9djJRBk5s+jtyMcc51jzwf+4
wm0TSpShtuw8odPWzkNYSMAPKAPn6wqYlx6D66YPLIAxNACTSBPz2iPRoYE5dRN4
IFOMmvN/z96Mz5rQPguANT4SURuaiA==
=6Bds
-END PGP SIGNATURE-

Bug#1019804: marked as done (plee-the-bear: Please transition to wxwidgets3.2)

[Debian Bug Tracking System]

Your message dated Wed, 02 Nov 2022 16:05:30 +
with message-id 
and subject line Bug#1019804: fixed in plee-the-bear 0.6.0-8
has caused the Debian Bug report #1019804,
regarding plee-the-bear: Please transition to wxwidgets3.2
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1019804: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1019804
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: plee-the-bear
Severity: normal
Control: block 1019416 by -1

Hi,

Please transition plee-the-bear from wxwidgets3.0 to wxwidgets3.2.

wxWidgets 3.2 (a new API/ABI stable release) has been released a few
months ago and is now packaged in unstable as wxwidgets3.2. Upstream
has stopped supporting wxWidgets 3.0, so the Debian wx team would
like to migrate all wx package users to wxwidgets3.2 for bullseye,
with the plan to remove wxwidgets3.0 before release.

For most packages, the transition should be as simple as changing
Build-Depends from libwxgtk3.0-gtk3-dev to libwxgtk3.2-dev. Some
packages may require small patches; I'm happy to help with those (and
I have some already from working on this transition in Fedora
already).

Thanks, Scott 
--- End Message ---
--- Begin Message ---
Source: plee-the-bear
Source-Version: 0.6.0-8
Done: Scott Talbert 

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

Debian distribution maintenance software
pp.
Scott Talbert  (supplier of updated plee-the-bear 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: Thu, 27 Oct 2022 20:07:32 -0400
Source: plee-the-bear
Architecture: source
Version: 0.6.0-8
Distribution: unstable
Urgency: medium
Maintainer: Debian Games Team 
Changed-By: Scott Talbert 
Closes: 1019804
Changes:
 plee-the-bear (0.6.0-8) unstable; urgency=medium
 .
   * Team upload.
   * Transition to wxWidgets 3.2 (Closes: #1019804)
Checksums-Sha1:
 1bbfa1c687c9a62538169e0de4fd68927cdab52a 2693 plee-the-bear_0.6.0-8.dsc
 fd3b15523f94a6a3e00032cd67545ff60b5b6015 20120 
plee-the-bear_0.6.0-8.debian.tar.xz
 2e1af8bf06e7e85db1ddcf34e04349bac16e7bcb 16421 
plee-the-bear_0.6.0-8_amd64.buildinfo
Checksums-Sha256:
 6e8091c04ac82700de039e18ba823505466eae8678c70ba63bcaa418eeaeab90 2693 
plee-the-bear_0.6.0-8.dsc
 f116dbce319df9b52ee9d9050d5475718f91f969efe53121e9cd0958c528f8f6 20120 
plee-the-bear_0.6.0-8.debian.tar.xz
 52f73566cc5dd91b962f9c7a8400cbc18c39d8cb4b39f337199947fb55cee7eb 16421 
plee-the-bear_0.6.0-8_amd64.buildinfo
Files:
 7fd0f6ef669c4dd2b2eaecb3ae58 2693 games optional plee-the-bear_0.6.0-8.dsc
 738dc1ade8d10e22cf04f33a168c74f1 20120 games optional 
plee-the-bear_0.6.0-8.debian.tar.xz
 d92af43ebc05f9fb2048dcee643b20a6 16421 games optional 
plee-the-bear_0.6.0-8_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJDBAEBCgAtFiEEbnQ09Yl9Q7F/zVe3U9W8ZLUjeKIFAmNijkQPHHN3dEB0ZWNo
aWUubmV0AAoJEFPVvGS1I3iiiFYP/22lhRFv9ZoRgJZ01JTyszg4Dm6Cdfhl7QDk
cN9r5bsS0IiE/Xl363mjYIEBdqUflMqg886ARAE4wsESIOlUdRpqLkU9YCzfJeIt
Jl++qNUB4RHvX4ceYkIf/RpxwVDkaxQcNcKySmfTIHijhe6U7SRgF7qigmaBywdv
a0nq1vzHV7Q3bHTYEUoQXsa98Pqe8F9osK3TJO00W8TADwgXGUYeYya/RLgkr5Vj
0gjye5eS2cfmM2qtd1X1mCpV4bCLnBZbgRU2jgsaOmJNIRYi781Jne4GnbYCPvOx
AroievxypnnVaycY4EkLV+okjTx09CkwWkp2UHb04knVkb9t4MBRDyZdP1FUkx4W
4vt/p8I8+ey56ud01Wt+omlrTt6Aib/NHw2ow5DovTHBuX50+Ujy1jZAPwzIrU1W
So6a6GPn3M8dasZRjm4yzyj0O7bMYWQmAU7odzJ8JWHzYMYdIGa+2qkYFvaU4vK2
3fUEIzJBlPyXObcKK8QukjhAHDLvHVOfabdtc2zeFfOSkiKSAQ2YJnsCeAo8qT1S
usJxsuFNhmDE1f/+xkobzJ40Yadunf2J06tDjSWI3VVCz+NkLpd6wkz56klVXlDP
hSR0bCC+Q5TAA4Lr0qtb3tvqHURpqHYlUGzRrwCGG2HIve8WvCGGJ2bdqnuxbQan
Fjh/+jus
=vhPq
-END PGP SIGNATURE End Message ---

Bug#1023341: Fails to add any event due to too new python3-tzlocal

[Guido Günther]

Package: khal
Version: 1:0.10.4~ds-4
Severity: grave

Hi,
Adding a any new events on bookworm fails like (example is copied from
the manpage):

$ khal new 18:00 Awesome Event 
/usr/lib/python3/dist-packages/khal/icalendar.py:104: PytzUsageWarning: The 
localize method is no longer necessary, as this time zone supports the fold 
attribute (PEP 495). For more details on migrating to a PEP 495-compliant 
implementation, see 
https://pytz-deprecation-shim.readthedocs.io/en/latest/migration.html
  dtstart = timezone.localize(dtstart)
/usr/lib/python3/dist-packages/khal/icalendar.py:105: PytzUsageWarning: The 
localize method is no longer necessary, as this time zone supports the fold 
attribute (PEP 495). For more details on migrating to a PEP 495-compliant 
implementation, see 
https://pytz-deprecation-shim.readthedocs.io/en/latest/migration.html
  dtend = timezone.localize(dtend)
/usr/lib/python3/dist-packages/icalendar/parser.py:54: PytzUsageWarning: The 
zone attribute is specific to pytz's interface; please migrate to a new time 
zone provider. For more details on how to do so, see 
https://pytz-deprecation-shim.readthedocs.io/en/latest/migration.html
  if hasattr(dt.tzinfo, 'zone'):
/usr/lib/python3/dist-packages/icalendar/parser.py:55: PytzUsageWarning: The 
zone attribute is specific to pytz's interface; please migrate to a new time 
zone provider. For more details on how to do so, see 
https://pytz-deprecation-shim.readthedocs.io/en/latest/migration.html
  tzid = dt.tzinfo.zone  # pytz implementation
Traceback (most recent call last):
  File "/usr/bin/khal", line 5, in 
main_khal()
  File "/usr/lib/python3/dist-packages/click/core.py", line 1128, in __call__
return self.main(*args, **kwargs)
  File "/usr/lib/python3/dist-packages/click/core.py", line 1053, in main
rv = self.invoke(ctx)
  File "/usr/lib/python3/dist-packages/click/core.py", line 1659, in invoke
return _process_result(sub_ctx.command.invoke(sub_ctx))
  File "/usr/lib/python3/dist-packages/click/core.py", line 1395, in invoke
return ctx.invoke(self.callback, **ctx.params)
  File "/usr/lib/python3/dist-packages/click/core.py", line 754, in invoke
return __callback(*args, **kwargs)
  File "/usr/lib/python3/dist-packages/click/decorators.py", line 26, in 
new_func
return f(get_current_context(), *args, **kwargs)
  File "/usr/lib/python3/dist-packages/khal/cli.py", line 388, in new
new_func(
  File "/usr/lib/python3/dist-packages/khal/controllers.py", line 355, in 
new_from_string
new_from_args(
  File "/usr/lib/python3/dist-packages/khal/controllers.py", line 381, in 
new_from_args
collection.new(event)
  File "/usr/lib/python3/dist-packages/khal/khalendar/khalendar.py", line 208, 
in new
event.href, event.etag = self._storages[calendar].upload(event)
  File "/usr/lib/python3/dist-packages/khal/khalendar/vdir.py", line 212, in 
upload
if not isinstance(item.raw, str):
  File "/usr/lib/python3/dist-packages/khal/khalendar/event.py", line 382, in 
raw
timezone = create_timezone(tzinfo, self.start)
  File "/usr/lib/python3/dist-packages/khal/khalendar/event.py", line 858, in 
create_timezone
for one, two in iter(tz._tzinfos.items())
AttributeError: '_PytzShimTimezone' object has no attribute '_tzinfos'

This because khal can't cope with recent python3-tzlocal from bookworm (4.2-1),
downgrading python3-tzlocal (2.1-1) makes adding events work again (Got that
hint https://github.com/pimutils/khal/issues/1092)

As it fails to add any events I've picked grave severity. Please adjust
if you disagree.

Cheers,
  -- Guido


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

Kernel: Linux 6.0.0-2-amd64 (SMP w/12 CPU threads; PREEMPT)
Kernel taint flags: TAINT_WARN, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages khal depends on:
ii  python33.10.6-1
ii  python3-atomicwrites   1.4.1-1
ii  python3-click  8.0.3-1
ii  python3-click-log  0.3.2-1
ii  python3-configobj  5.0.6-5
ii  python3-dateutil   2.8.2-1
ii  python3-icalendar  4.0.3-5
ii  python3-packaging  21.3-1.1
ii  python3-pkg-resources  65.5.0-1
ii  python3-tz 2022.4-1
ii  python3-tzlocal4.2-1
ii  python3-urwid  2.1.2-2+b2
ii  python3-xdg0.27-3

Versions of packages khal recommends:
ii  python3-setproctitle  1.3.1-1

Versions of packages khal suggests:
pn  khal-doc  

-- no debconf information

Bug#1022348: marked as done (gpgme1.0: FTBFS: Could not find gpg-error-config. Please install the libgpg-error development package.)

[Debian Bug Tracking System]

Your message dated Wed, 02 Nov 2022 15:50:31 +
with message-id 
and subject line Bug#1022348: fixed in gpgme1.0 1.18.0-2
has caused the Debian Bug report #1022348,
regarding gpgme1.0: FTBFS: Could not find gpg-error-config.  Please install the 
libgpg-error development package.
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.)


-- 
1022348: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022348
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gpgme1.0
Version: 1.18.0-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20221023 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> make[4]: Entering directory '/<>/build/lang/python'
> ln -sf "../../../src/data.h" .
> ln -sf "../../conf/config.h" .
> ln -sf "../../../lang/python/src" gpg
> touch copystamp
> set -e ; for PYTHON in /usr/bin/python3.10 ; do \
>   CPP="gcc -E" \
>   CFLAGS="-g -O2 -ffile-prefix-map=/<>=. 
> -fstack-protector-strong -Wformat -Werror=format-security -Wall -Wcast-align 
> -Wshadow -Wstrict-prototypes -Wno-format-y2k -Wno-missing-field-initializers 
> -Wno-sign-compare -Wno-format-zero-length -Wno-format-truncation 
> -Wno-sizeof-pointer-div" \
>   srcdir="../../../lang/python" \
>   top_builddir="../.." \
> $PYTHON setup.py build --verbose --build-base="$(basename 
> "${PYTHON}")-gpg" ; \
> done
> /<>/build/lang/python/setup.py:21: DeprecationWarning: The 
> distutils package is deprecated and slated for removal in Python 3.12. Use 
> setuptools or check PEP 632 for potential alternatives
>   from distutils.core import setup, Extension
> running build
> Using gpgme.h from ../../src/gpgme.h
> Could not find gpg-error-config.  Please install the libgpg-error development 
> package.
> make[4]: *** [Makefile:760: all-local] Error 1


The full build log is available from:
http://qa-logs.debian.net/2022/10/23/gpgme1.0_1.18.0-1_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20221023;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20221023&fusertaguser=lu...@debian.org&allbugs=1&cseverity=1&ctags=1&caffected=1#results

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

If you reassign this bug to another package, please marking it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Source: gpgme1.0
Source-Version: 1.18.0-2
Done: Daniel Kahn Gillmor 

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

Debian distribution maintenance software
pp.
Daniel Kahn Gillmor  (supplier of updated gpgme1.0 
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, 02 Nov 2022 10:54:12 -0400
Source: gpgme1.0
Architecture: source
Version: 1.18.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian GnuPG Maintainers 
Changed-By: Daniel Kahn Gillmor 
Closes: 1022348
Changes:
 gpgme1.0 (1.18.0-2) unstable; urgency=medium
 .
   [ Andreas Metzler ]
   * Fix FTBFS after removal of gpg-error-config (Closes: #1022348)
   * gpgme-config not installed anymore
 .
   [ Jelmer Vernooij ]
   * debian/upstream/metadata: Set Repository and Repository-Browse.
 .
   [ Daniel Kahn Gillmor ]
   * d/upstream/metadata: add upstream bug reporting details
Checksums-Sha1:
 9ae0b17642bc17a27f4e515afcfcf4ef8a2e611b 2258 gpgme1.0_1.18.0-2.dsc
 fc909c5af329cd9b770f07edcd662bd8a5aa28e0 22520 gpgme1.0_1.18.0-2.debian.tar.xz
 fc60a1d2ade9d91c4f9fd24bb40d42ff742dc523 20331 
gpgme1.0_1.18.0-2_amd64.buildinfo
Checksums-Sha256:
 29bd969a0f27a6050fd69b120ae808b1db

Bug#1020456: cypari2 FTBFS with PARI 2.15.0

[Bill Allombert]

On Fri, Oct 28, 2022 at 07:26:09PM +, Tobias Hansen wrote:
> Thanks! I will apply the patch once the pari version with the other fixes is 
> uploaded.

Great! I uploaded it today (pari 2.15.1~pre1-1). I hope it will be OK.

Cheers,
-- 
Bill. 

Imagine a large red swirl here. 

Bug#1022348: [pkg-gnupg-maint] Bug#1022348: gpgme1.0: FTBFS: Could not find gpg-error-config. Please install the libgpg-error development package.

[Daniel Kahn Gillmor]

On Wed 2022-10-26 18:17:11 +0200, Andreas Metzler wrote:
> On 2022-10-26 Andreas Metzler  wrote:
> [...]
>> Which has been promptly fixed. Find attached debdiffs for a proposed
>> upload. - I can also massage this into a mergew-request or push
>> directly to https://salsa.debian.org/debian/gpgme Just give me a
>> heads-up.
> [...]
>
> https://salsa.debian.org/debian/gpgme/-/merge_requests/7
>
> (Sending now since I will not have time tomorrow and on Friday.)
> cu Andreas

Thanks for this work, Andreas.  I'm working on rolling it up into a new
release which i hope to land in unstable later today.

Of course, this might cause knock-on effects for projects that
themselves think they should be dependent on gpgme-config, but i'll try
to sort those through as well.

--dkg


signature.asc
Description: PGP signature

Bug#1022289: marked as done (libassuan: FTBFS: configure: error: libgpg-error was not found)

[Debian Bug Tracking System]

Your message dated Wed, 02 Nov 2022 14:49:08 +
with message-id 
and subject line Bug#1022289: fixed in libassuan 2.5.5-5
has caused the Debian Bug report #1022289,
regarding libassuan: FTBFS: configure: error: libgpg-error was not found
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1022289: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022289
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libassuan
Version: 2.5.5-4
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20221023 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> ../configure: line 15745: /usr/i686-w64-mingw32/bin/gpg-error-config: No such 
> file or directory
> ../configure: line 15756: test: : integer expression expected
> ../configure: line 15759: test: : integer expression expected
> ../configure: line 15766: test: : integer expression expected
> checking for GPG Error - version >= 1.17... no
> configure: error: libgpg-error was not found
> make[1]: *** [debian/rules:27: override_dh_auto_build-indep] Error 1
> make[1]: Leaving directory '/<>'


The full build log is available from:
http://qa-logs.debian.net/2022/10/23/libassuan_2.5.5-4_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20221023;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20221023&fusertaguser=lu...@debian.org&allbugs=1&cseverity=1&ctags=1&caffected=1#results

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

If you reassign this bug to another package, please marking it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Source: libassuan
Source-Version: 2.5.5-5
Done: Daniel Kahn Gillmor 

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

Debian distribution maintenance software
pp.
Daniel Kahn Gillmor  (supplier of updated libassuan 
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, 01 Nov 2022 18:00:16 -0400
Source: libassuan
Architecture: source
Version: 2.5.5-5
Distribution: unstable
Urgency: medium
Maintainer: Debian GnuPG-Maintainers 
Changed-By: Daniel Kahn Gillmor 
Closes: 1022289
Changes:
 libassuan (2.5.5-5) unstable; urgency=medium
 .
   [ Andreas Metzler ]
   * Stop forcing gpg-error-config usage, fixing FTBFS. (Closes: #1022289)
 .
   [ Daniel Kahn Gillmor ]
   * drop explicit dpkg dependency, part of essential
   * reflow text description of win32 linker error patch to
 avoid very-long-line-length-in-source-file
   * lintian-overrides: rewrite for parameterized tags
Checksums-Sha1:
 c08472af6058f74dbdd05eea7cfaafe41afe0e13 1997 libassuan_2.5.5-5.dsc
 9ce275a4cc29f0fdbc82b875cbc50b5fc130695a 14256 libassuan_2.5.5-5.debian.tar.xz
 9045ba440a140253ccbe980ac75094fb9fd7582a 8992 libassuan_2.5.5-5_amd64.buildinfo
Checksums-Sha256:
 60be1d43dd5a7c4bce7a97f58513915990c8c615ea02c68b8cd5cf1e33b84a0c 1997 
libassuan_2.5.5-5.dsc
 9d46fe972ba45692e28a2618e457a7f9141afc122281a862bcb4aa16716c97d7 14256 
libassuan_2.5.5-5.debian.tar.xz
 726471079cad383cc50958593c2b47f4308bd822e3d931dd60d3a3cd29d3e352 8992 
libassuan_2.5.5-5_amd64.buildinfo
Files:
 546a5b2469bf634e3307e38c04c0e2e0 1997 libs optional libassuan_2.5.5-5.dsc
 d93665abe4bafb8a3d9c68374cf8e37a 14256 libs optional 
libassuan_2.5.5-5.debian.tar.xz
 82d90eed5dadb653e1e38e88a42f3028 8992 libs optional 
libassuan_2.5.5-5_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iHUEARYIAB0WIQQttUkcnfDcj0MoY88+nXFzcd5WXAUCY2J0mwAKCRA+nXFzcd5W
XG1QAQDFIvXiDQv1KGxsBi+P4kBDRxaPuL7d+6udpDLp

Bug#998933: cgilib: diff for NMU version 0.6-1.2

[Andreas Beckmann]

Hi Marcos,

On Wed, 2 Nov 2022 00:21:56 -0300 Marcos Talau  wrote:

I've prepared an NMU for cgilib (versioned as 0.6-1.2) and

cgilib is orphaned, so you should rather do a QA upload ;-)

Andreas

Bug#1022674: marked as done (three.js: Unable to build with rollup 3)

[Debian Bug Tracking System]

Your message dated Wed, 02 Nov 2022 13:22:24 +
with message-id 
and subject line Bug#1022674: fixed in three.js 111+dfsg1-3
has caused the Debian Bug report #1022674,
regarding three.js: Unable to build with rollup 3
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.)


-- 
1022674: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022674
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: three.js
Severity: important
Tags: ftbfs
User: pkg-javascript-de...@lists.alioth.debian.org
Usertags: rollup-3

Sent with mass-bug

three.js's build failed with rollup 3. This is often due to a bad
rollup.config.js which was accepted before (ES in a .js file).

To fix it, try to move rollup.config.js into rollup.config.mjs or
rewrite it into CommonJS.

rollup 3.x is available in experimental branch. 
--- End Message ---
--- Begin Message ---
Source: three.js
Source-Version: 111+dfsg1-3
Done: Yadd 

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

Debian distribution maintenance software
pp.
Yadd  (supplier of updated three.js 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, 02 Nov 2022 13:55:16 +0100
Source: three.js
Architecture: source
Version: 111+dfsg1-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Javascript Maintainers 

Changed-By: Yadd 
Closes: 1022674
Changes:
 three.js (111+dfsg1-3) unstable; urgency=medium
 .
   * Team upload
 .
   [ Michael R. Crusoe ]
   * mark libjs-three as Multi-Arch: foreign
 .
   [ lintian-brush ]
   * Update standards version to 4.6.1, no changes needed.
 .
   [ Yadd ]
   * Add fix for rollup 3 (Closes: #1022674)
Checksums-Sha1: 
 4e11ea558ff27c15184a6cd81dcb7c8a7e0db164 2080 three.js_111+dfsg1-3.dsc
 77ff80351885d61fba781141d2830b70158e0e9f 5540 
three.js_111+dfsg1-3.debian.tar.xz
Checksums-Sha256: 
 1c3ca15aeb78c781b734b55d2958177c7a4f968568930150b8e4d3d5ddba77c9 2080 
three.js_111+dfsg1-3.dsc
 05a99cf6e8e78177352dc238f5131ff431f819963cff466a38696e0df136 5540 
three.js_111+dfsg1-3.debian.tar.xz
Files: 
 802b471fa928d99b12bb752681db46f8 2080 javascript optional 
three.js_111+dfsg1-3.dsc
 48a51443953f4daadfa6409b477173ee 5540 javascript optional 
three.js_111+dfsg1-3.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEAN/li4tVV3nRAF7J9tdMp8mZ7ukFAmNiaRAACgkQ9tdMp8mZ
7unr+w//V9HnDop27BoRqVBQCLf6f7YI7Q52JKcQUfUpXhag794vvTUEGqMG3QOT
0HsJTLIzg2qiAYG/xlYw/Wcgb+NjJ68GxnVYyUfrUmGUSBGp9+dm2yMuLf6IUfxT
w4umorqTnc43cnC/kSzGsZcRzWIbYzJXCfYqdYhVCjL/UhpiakbngXu+GpwO6TG2
9TmGd2wo6Co5Ej7a9J9v+i8BTSmdPZfoIRtij7gjb7t/LLOm0c56jCzeGGYZvhxt
V5jMKppSGuZUbPvVcfux9DE0yw8yC7JMTqz+hnIGwg5AS1wfZtnl1k4VAIxyvaXP
zDGgu51boYaJyFj4frJXB4g6l5eh+Twequ149NUyg9R4v+o68shoB4LDXH2vD6+I
rB+JGwbCOaKW9jvqh+RhZPJqLPTDvlUrk3kqd/moroSoBSQ9CHpIn09wVlSSQgoV
IXQ+amJuokErYYjdPTJmQXgp4aD53tNg1TbSvvI+GX+mUPasSQ9kWbAqZ8cdZQPI
aIGDPxhL/WzdBvKfEdIVLIwEiSMGjvcazaxDVhABGyqQI4eJ/QiN4JP5EEOFgZAl
r8PM6Y3cMWAhoiinb82obJo1wlrqSXace/2hsOe4NtUvkQhn5MMMVkROzR0cOD4q
QLkizioq0H9M0H8F7HZ8aDhKQgja1ITEU3IBRpQuzBWiihX3CQw=
=eipZ
-END PGP SIGNATURE End Message ---

Processed: bug 1022577 is forwarded to https://github.com/llvm/llvm-project/issues/58514

[Debian Bug Tracking System]

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

> forwarded 1022577 https://github.com/llvm/llvm-project/issues/58514
Bug #1022577 [src:llvm-toolchain-15] llvm-toolchain-15 fails with LLVM ERROR 
when using mesa
Set Bug forwarded-to-address to 
'https://github.com/llvm/llvm-project/issues/58514'.
> thanks
Stopping processing here.

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

Bug#1006022: marked as done (puma: flaky tests)

[Debian Bug Tracking System]

Your message dated Wed, 02 Nov 2022 12:50:08 +
with message-id 
and subject line Bug#1006022: fixed in puma 5.6.5-2
has caused the Debian Bug report #1006022,
regarding puma: flaky tests
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.)


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

Source: puma
Version: 5.5.2-2
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 because it was 
showing up as a regression for the upload of glibc. I noticed that the 
test regularly fails on all architectures, particularly since version 
5.5.2-2


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/data/autopkgtest/testing/armhf/p/puma/19335931/log.gz

  1) Failure:
TestIntegrationSingle#test_hot_restart_does_not_drop_connections_threads 
[/tmp/autopkgtest-lxc.4tg64laj/downtmp/build.gqr/src/test/helpers/integration.rb:313]:

  0 unexpected_response
  1 refused
  0 read timeout
  0 reset
999 success
893 success after restart
  2 restart count
Expected no refused connections.
Expected: 0
  Actual: 1

412 runs, 1423 assertions, 1 failures, 0 errors, 6 skips


OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: puma
Source-Version: 5.6.5-2
Done: Antonio Terceiro 

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

Debian distribution maintenance software
pp.
Antonio Terceiro  (supplier of updated puma 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, 02 Nov 2022 09:26:37 -0300
Source: puma
Architecture: source
Version: 5.6.5-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Team 

Changed-By: Antonio Terceiro 
Closes: 1006022
Changes:
 puma (5.6.5-2) unstable; urgency=medium
 .
   * debian/ruby-tests.rake: skip test that fails often (Closes: #1006022)
   * debian/ruby-tests.rake: exclude tests that fail often but not always
Checksums-Sha1:
 e00184f08ef0f371ebac3d264c9f997bb5adff2a 2087 puma_5.6.5-2.dsc
 6079087745483597cd19c8636ca31456626cd518 9384 puma_5.6.5-2.debian.tar.xz
 b43f438329d2fa5c8935dc2667041ff1bad34af8 10056 puma_5.6.5-2_amd64.buildinfo
Checksums-Sha256:
 49812f45f3ee19f894c8a53420634411d0bb9de51e9ef443236762ecf29db89a 2087 
puma_5.6.5-2.dsc
 4daa1af80bcf84b7c8fb6a568f461405ce6ac3034f75d87f5d79305aeb6e6345 9384 
puma_5.6.5-2.debian.tar.xz
 f0bb236804ac086d674e65d227e85b978de5f7466980e27ac97cafbc48504477 10056 
puma_5.6.5-2_amd64.buildinfo
Files:
 f9e9abe2551b22b8e9bb5acd4de60bc2 2087 web optional puma_5.6.5-2.dsc
 358e63eaf35cf7ddb8544ca49b13d12c 9384 web optional puma_5.6.5-2.debian.tar.xz
 3bfcad5a557c3190e54739d1e6f23b0e 10056 web optional 
puma_5.6.5-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEst7mYDbECCn80PEM/A2xu81GC94FAmNiY3cACgkQ/A2xu81G
C96KLg/+KDqdbEsZ0K0iS13r+RmEnAwolcdSilu0XZjytliB0pch2NeGXRtIg6nP
8g8pbltNk1QajJPD9okBxsSawNFBtf0001EWdVyHe85nd4mARmARO9JjV0OJ9R4k
2dlamyb7cAJHjWc/R/+OQqzvWAwK5Y5vCvvH3/ZegCp3ubfuVeql7dRfZQe22Zcd
DU/C7uUhGjDIFk6ACkkfxQ12mfKMzgu2G+RlI8fmlTa8rdkQ+y40goygL+Ta29jV
DUS9SGAwKgNbrghIblj7JRlOFyQlfSDgjD18jXzHPIu18mczfDHWTEJHFBCTGFsS
EWPjEZZnfLs3fWWjaXz8EyyL20ZCjQptOEtmwavAN2bO9/wBsHA5dlZQX52ujnhk
udXNbPLmtoxYWZ2P8IjZvAbcT3/Ew6yoinNaFTFHPzOOX6jSPfDD6lNA2LiC
DFPJmjyJP3djEupFNmJxNLqwA5HIudFMY1l0aMzNCyrSVqdxkj2cHYQ6nPGG3SVd
QANF2KBl1eyOCEmYRi8YY1nlHlp7g3DD44qAZ87KrJ1LvArqR0hZDfZPLSknUaHp
kHfcNqG7ip6wIroHQ9udRRgVc7ZcpZE/jTfe9FirKsHAyFuPTY8QEBkOEwDuCsvb
ubU9OEhxF1h2vjRAl7xz26eLA3LCwvPjCXTwXpi+9IxP/recn2U=
=DHG0
-END 

Bug#1021317: salt-master: Fails to start with "zmq.error.ZMQError: Invalid argument"

[Benoit Friry]

It can be linked to https://github.com/saltstack/salt/issues/62092.
I have the same issue, and python3-zmq on my system is 24.0.1-1.

Bug#1019991: marked as done (ovn: ovn-controller incremental processing FAILED)

[Debian Bug Tracking System]

Your message dated Wed, 02 Nov 2022 12:37:49 +
with message-id 
and subject line Bug#1019991: fixed in ovn 22.03.1-6
has caused the Debian Bug report #1019991,
regarding ovn: ovn-controller incremental processing 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.)


-- 
1019991: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1019991
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ovn
Version: 22.03.1-5
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220917 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> make[4]: Entering directory '/<>'
> set /bin/bash './tests/testsuite' -C tests 
> AUTOTEST_PATH=/<>/ovs/utilities:/<>/ovs/vswitchd:/<>/ovs/ovsdb:/<>/ovs/vtep:tests:::controller-vtep:northd:utilities:controller:ic;
>  \
> "$@" --recheck || \
> (test -z "$(find /<>/tests/testsuite.dir -name 'asan.*')" && \
>  test X'' = Xyes && "$@" --recheck)
> ## --- ##
> ## ovn 22.03.1 test suite. ##
> ## --- ##
> 
> OVN end-to-end tests
> 
> 612: Dynamic neighbor between LRs -- ovn-northd -- dp-groups=no ok
> 752: ovn-controller incremental processing   FAILED 
> (ovn-performance.at:477)
> 
> ## - ##
> ## Test results. ##
> ## - ##
> 
> ERROR: All 2 tests were run,
> 1 failed unexpectedly.
> ## -- ##
> ## testsuite.log was created. ##
> ## -- ##
> 
> Please send `tests/testsuite.log' and all information you think might help:
> 
>To: 
>Subject: [ovn 22.03.1] testsuite: 752 failed
> 
> You may investigate any problem if you feel able to do so, in which
> case the test suite provides a good starting point.  Its output may
> be found below `tests/testsuite.dir'.
> 
> make[4]: *** [Makefile:3628: check-local] Error 1
> make[4]: Leaving directory '/<>'
> make[3]: *** [Makefile:2888: check-am] Error 2
> make[3]: Leaving directory '/<>'
> make[2]: *** [Makefile:2890: check] Error 2
> make[2]: Leaving directory '/<>'
> ## --- ##
> ## ovn 22.03.1 test suite. ##
> ## --- ##
> 
> testsuite: command line was:
>   $ ./tests/testsuite -C tests 
> AUTOTEST_PATH=/<>/ovs/utilities:/<>/ovs/vswitchd:/<>/ovs/ovsdb:/<>/ovs/vtep:tests:::controller-vtep:northd:utilities:controller:ic
>  --recheck
> 
> ## - ##
> ## Platform. ##
> ## - ##
> 
> hostname = ip-10-84-234-46
> uname -m = x86_64
> uname -r = 5.10.0-9-cloud-amd64
> uname -s = Linux
> uname -v = #1 SMP Debian 5.10.70-1 (2021-09-30)
> 
> /usr/bin/uname -p = unknown
> /bin/uname -X = unknown
> 
> /bin/arch  = unknown
> /usr/bin/arch -k   = unknown
> /usr/convex/getsysinfo = unknown
> /usr/bin/hostinfo  = unknown
> /bin/machine   = unknown
> /usr/bin/oslevel   = unknown
> /bin/universe  = unknown
> 
> PATH: /<>/ovs/utilities/
> PATH: /<>/ovs/vswitchd/
> PATH: /<>/ovs/ovsdb/
> PATH: /<>/ovs/vtep/
> PATH: /<>/tests/
> PATH: /<>/
> PATH: /<>/controller-vtep/
> PATH: /<>/northd/
> PATH: /<>/utilities/
> PATH: /<>/controller/
> PATH: /<>/ic/
> PATH: /usr/local/sbin/
> PATH: /usr/local/bin/
> PATH: /usr/sbin/
> PATH: /usr/bin/
> PATH: /sbin/
> PATH: /bin/
> PATH: /usr/games/
> 
> testsuite: atconfig:
> | # Configurable variable values for building test suites.
> | # Generated by ./config.status.
> | # Copyright (C) 2021 Free Software Foundation, Inc.
> | 
> | # The test suite will define top_srcdir=/../.. etc.
> | at_testdir='tests'
> | abs_builddir='/<>/tests'
> | at_srcdir='.'
> | abs_srcdir='/<>/tests'
> | at_top_srcdir='..'
> | abs_top_srcdir='/<>'
> | at_top_build_prefix='../'
> | abs_top_builddir='/<>'
> | 
> | # Backward compatibility with Autotest <= 2.59b:
> | at_top_builddir=$at_top_build_prefix
> | 
> | 
> | EXEEXT=''
> | AUTOTEST_PATH='tests'
> | 
> | SHELL=${CONFIG_SHELL-'/bin/bash'}
> 
> testsuite: atlocal:
> | # -*- shell-script -*-
> | HAVE_OPENSSL='yes'
> | OPENSSL_SUPPORTS_SNI='yes'
> | HAVE_UNBOUND='yes'
> | EGREP='/bin/grep -E'
> | 
> | if test x"$PYTHON3" = x; then
> | PYTHON3='/usr/bin/python3'
> | PYTHON='/usr/bin/python3'
> | # PYTHONCOERCECLOCALE=0 disables the Unicode compatibility warning on
> | # stderr that breaks almost any Python3 test (PEP 0538)
> | PYTHONCOERCECLOCALE=0
> | export PYTHONCOERCECLOCALE
> | fi
> | 
> | PYTHONPATH=$ovs_srcdir/python:$abs_top_builddir/tests:$PYTHONPATH
> | export PYTHONPATH
> | 
> | PYTHONIOENCODING=utf_8
> | export PY

Processed: Bug#1006022 marked as pending in puma

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1006022 [src:puma] puma: flaky tests
Added tag(s) pending.

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

Bug#1006022: marked as pending in puma

[Antonio Terceiro]

Control: tag -1 pending

Hello,

Bug #1006022 in puma 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/ruby-team/puma/-/commit/e6961fbc2125bcaccb759b4c7fb05576ed37545e


debian/ruby-tests.rake: skip test that fails often

I tried rebuilding 10 times, and that one test failed in 2 of those
builds.

Closes: #1006022


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1006022

Bug#1023325: cron-daemon-common: insufficient Breaks+Replaces against cronie

[Andreas Beckmann]

Package: cron-daemon-common
Version: 3.0pl1-150
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package has file conflicts
with cronie/experimental.
There are Breaks+Replaces: cronie (<< 1.6.1-4), but cronie had a new
upload yesterday without adding support for cron-daemon-common,
invalidating the B+R versions.
I don't see any bug (and patch) against cronie to make it use
cron-daemon-common ...

>From the attached log (scroll to the bottom...):

  Preparing to unpack .../cron-daemon-common_3.0pl1-150_all.deb ...
  Unpacking cron-daemon-common (3.0pl1-150) ...
  dpkg: error processing archive 
/var/cache/apt/archives/cron-daemon-common_3.0pl1-150_all.deb (--unpack):
   trying to overwrite '/etc/cron.d/.placeholder', which is also in package 
cronie 1.6.1-4
  Errors were encountered while processing:
   /var/cache/apt/archives/cron-daemon-common_3.0pl1-150_all.deb


cheers,

Andreas


cronie=1.6.1-4_cron-daemon-common=3.0pl1-150.log.gz
Description: application/gzip

Bug#1023324: gm2-12-doc: missing Breaks+Replaces: gm2-12 (<< 12.2.0-8)

[Andreas Beckmann]

Package: gm2-12-doc
Version: 12.2.0-8
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'sid' to 'experimental'.
It installed fine in 'sid', then the upgrade to 'experimental' fails
because it tries to overwrite other packages files without declaring a
Breaks+Replaces relation.
This error may also be triggered by having a predecessor package from
'sid 'installed while installing the package from 'experimental'.

See policy 7.6 at
https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces

>From the attached log (scroll to the bottom...):

  Preparing to unpack .../gm2-12-doc_12.2.0-8_all.deb ...
  Unpacking gm2-12-doc (12.2.0-8) ...
  dpkg: error processing archive 
/var/cache/apt/archives/gm2-12-doc_12.2.0-8_all.deb (--unpack):
   trying to overwrite '/usr/share/doc/gcc-12-base/m2/gm2.html', which is also 
in package gm2-12 12.2.0-7
  dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
  Errors were encountered while processing:
   /var/cache/apt/archives/gm2-12-doc_12.2.0-8_all.deb


cheers,

Andreas


gm2-12=12.2.0-7_gm2-12-doc=12.2.0-8.log.gz
Description: application/gzip

Bug#1023323: cockroachdb-datadriven: missing Breaks+Replaces: golang-github-cockroachdb-datadriven-dev (<< 1.0.2-2)

[Andreas Beckmann]

Package: cockroachdb-datadriven
Version: 1.0.2-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'testing'.
It installed fine in 'testing', then the upgrade to 'sid' fails
because it tries to overwrite other packages files without declaring a
Breaks+Replaces relation.

See policy 7.6 at
https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces

>From the attached log (scroll to the bottom...):

  Preparing to unpack .../cockroachdb-datadriven_1.0.2-2_amd64.deb ...
  Unpacking cockroachdb-datadriven (1.0.2-2) ...
  dpkg: error processing archive 
/var/cache/apt/archives/cockroachdb-datadriven_1.0.2-2_amd64.deb (--unpack):
   trying to overwrite '/usr/bin/datadriven-clear', which is also in package 
golang-github-cockroachdb-datadriven-dev 1.0.2-1+b2
  dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
  Errors were encountered while processing:
   /var/cache/apt/archives/cockroachdb-datadriven_1.0.2-2_amd64.deb


cheers,

Andreas


golang-github-cockroachdb-datadriven-dev=1.0.2-1+b2_cockroachdb-datadriven=1.0.2-2.log.gz
Description: application/gzip

Processed: severity of 1022674 is serious, severity of 1022630 is serious

[Debian Bug Tracking System]

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

> severity 1022674 serious
Bug #1022674 [three.js] three.js: Unable to build with rollup 3
Severity set to 'serious' from 'important'
> severity 1022630 serious
Bug #1022630 [node-mermaid] node-mermaid: Unable to build with rollup 3
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

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

Processed: closing 1022490

[Debian Bug Tracking System]

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

> close 1022490 2.17-1
Bug #1022490 [src:postgresql-hll] postgresql-hll: FTBFS: Error: debian/control 
needs updating from debian/control.in. Run 'pg_buildext updatecontrol'.
Marked as fixed in versions postgresql-hll/2.17-1.
Bug #1022490 [src:postgresql-hll] postgresql-hll: FTBFS: Error: debian/control 
needs updating from debian/control.in. Run 'pg_buildext updatecontrol'.
Marked Bug as done
> thanks
Stopping processing here.

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

Bug#1022490: closing 1022490

[Christoph Berg]

close 1022490 2.17-1
thanks

Bug#1020056:

[Raphael Hertzog]

Hello,

Le jeudi 13 octobre 2022, Thomas Braun a écrit :
> so I think it should be as easy as adding cppzmq-dev to the build
> dependencies.
> 
>  $diff -Nur control control.new
> --- control 2022-10-13 16:19:07.384578078 +0200
> +++ control.new 2022-10-13 16:19:03.972578004 +0200
> @@ -7,6 +7,7 @@
> default-libmysqlclient-dev,
> libcos4-dev,
> libzmq5-dev | libzmq3-dev,
> +   cppzmq-dev,
> omniidl,
> po-debconf
>  Build-Depends-Indep: doxygen,

FWIW, there's also a related MR here:
https://salsa.debian.org/science-team/tango/-/merge_requests/3

That MR replaces the "libzmq5-dev | libzmq3-dev" build dep with
cppzmq-dev. But the CI in the MR failed, though it seems to be for
unrelated reasons.

Adrian, I see you tagged this bug as pending. Why? I don't see any
fix pushed to git yet.

Cheers,
-- 
Raphaël Hertzog

Bug#1020073: marked as done (pyfai: FTBFS: distutils.errors.DistutilsError: Command '['/usr/bin/python3.10', '-m', 'pip', '--disable-pip-version-check', 'wheel', '--no-deps', '-w', '/tmp/tmpymrbi1ta',

[Debian Bug Tracking System]

Your message dated Wed, 02 Nov 2022 11:04:52 +
with message-id 
and subject line Bug#1020073: fixed in pyfai 0.21.3+dfsg1-2
has caused the Debian Bug report #1020073,
regarding pyfai: FTBFS: distutils.errors.DistutilsError: Command 
'['/usr/bin/python3.10', '-m', 'pip', '--disable-pip-version-check', 'wheel', 
'--no-deps', '-w', '/tmp/tmpymrbi1ta', '--quiet', 'setuptools<60.0.0']' 
returned non-zero exit status 1.
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.)


-- 
1020073: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020073
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pyfai
Version: 0.21.3+dfsg1-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220917 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
>  fakeroot debian/rules clean
> dh clean --buildsystem=pybuild
>dh_auto_clean -O--buildsystem=pybuild
>   install -d 
> /<>/pyfai-0.21.3\+dfsg1/debian/.debhelper/generated/_source/home
>   pybuild --clean -i python{version} -p 3.10
> I: pybuild base:240: python3.10 setup.py clean 
> /<>/setup.py:43: DeprecationWarning: The distutils package is 
> deprecated and slated for removal in Python 3.12. Use setuptools or check PEP 
> 632 for potential alternatives
>   from distutils.command.clean import clean as Clean
> /usr/lib/python3/dist-packages/_distutils_hack/__init__.py:18: UserWarning: 
> Distutils was imported before Setuptools, but importing Setuptools also 
> replaces the `distutils` module in `sys.modules`. This may lead to 
> undesirable behaviors or errors. To avoid these issues, avoid using distutils 
> directly, ensure that setuptools is installed in the traditional way (e.g. 
> not an editable install), and/or make sure that setuptools is always imported 
> before distutils.
>   warnings.warn(
> /usr/lib/python3/dist-packages/_distutils_hack/__init__.py:33: UserWarning: 
> Setuptools is replacing distutils.
>   warnings.warn("Setuptools is replacing distutils.")
> INFO: Disabling color, you really want to install colorlog.
> INFO:pythran:Disabling color, you really want to install colorlog.
> INFO:pyFAI.setup:Use setuptools with cython
> INFO:pyFAI.setup:Use setuptools.setup
> /usr/lib/python3/dist-packages/setuptools/installer.py:27: 
> SetuptoolsDeprecationWarning: setuptools.installer is deprecated. 
> Requirements should be satisfied by a PEP 517 installer.
>   warnings.warn(
> /usr/lib/python3/dist-packages/setuptools/installer.py:34: UserWarning: 
> Unbuilt egg for pyFAI [unknown version] (/<>)
>   pkg_resources.get_distribution('wheel')
> WARNING: The wheel package is not available.
> /usr/lib/python3/dist-packages/setuptools/installer.py:60: UserWarning: 
> Unbuilt egg for pyFAI [unknown version] (/<>)
>   environment = pkg_resources.Environment()
> /usr/bin/python3.10: No module named pip
> Traceback (most recent call last):
>   File "/usr/lib/python3/dist-packages/setuptools/installer.py", line 82, in 
> fetch_build_egg
> subprocess.check_call(cmd)
>   File "/usr/lib/python3.10/subprocess.py", line 369, in check_call
> raise CalledProcessError(retcode, cmd)
> subprocess.CalledProcessError: Command '['/usr/bin/python3.10', '-m', 'pip', 
> '--disable-pip-version-check', 'wheel', '--no-deps', '-w', 
> '/tmp/tmpymrbi1ta', '--quiet', 'setuptools<60.0.0']' returned non-zero exit 
> status 1.
> 
> The above exception was the direct cause of the following exception:
> 
> Traceback (most recent call last):
>   File "/<>/setup.py", line 1137, in 
> setup_package()
>   File "/<>/setup.py", line 1133, in setup_package
> setup(**setup_kwargs)
>   File "/usr/lib/python3/dist-packages/setuptools/__init__.py", line 86, in 
> setup
> _install_setup_requires(attrs)
>   File "/usr/lib/python3/dist-packages/setuptools/__init__.py", line 80, in 
> _install_setup_requires
> dist.fetch_build_eggs(dist.setup_requires)
>   File "/usr/lib/python3/dist-packages/setuptools/dist.py", line 875, in 
> fetch_build_eggs
> resolved_dists = pkg_resources.working_set.resolve(
>   File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 789, 
> in resolve
> dist = best[req.key] = env.best_match(
>   File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 1075, 
> in best_match
> return self.obtain(req, installer)
>   File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 1087, 
> in obtain
> return installer(requirement)
>   File "/usr/lib/python3/dist-packages

Bug#1023025: linux-image-6.0.0-2-686: kernel BUG at mm/memory.c:2660!

[Luiz Fellipe Carneiro]

Package: src:linux
Version: 6.0.5-1
Followup-For: Bug #1023025
X-Debbugs-Cc: l...@duck.com

Dear Maintainer,

Computer boot to a black screen and looks unresponsive from the keyboard and 
mouse after the update. 
In recover mode it boots to a black screen with the mouse pointer only, but 
accessible via SSH, and with dmesg found the bug in message:
[  117.318446] kernel BUG at mm/memory.c:2660!


-- Package-specific info:
** Version:
Linux version 6.0.0-2-686 (debian-ker...@lists.debian.org) (gcc-12 (Debian 
12.2.0-7) 12.2.0, GNU ld (GNU Binutils for Debian) 2.39) #1 SMP PREEMPT_DYNAMIC 
Debian 6.0.5-1 (2022-10-28)

** Command line:
BOOT_IMAGE=/boot/vmlinuz-6.0.0-2-686 
root=UUID=aedd93f3-399d-4ce4-a2c9-a507d37ef2fb ro single

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

** Kernel log:
[   33.943988] platform regulatory.0: firmware: direct-loading firmware 
regulatory.db
[   33.965904] input: HDA Digital PCBeep as 
/devices/pci:00/:00:1b.0/sound/card0/input9
[   33.976303] input: HDA Intel Mic as 
/devices/pci:00/:00:1b.0/sound/card0/input10
[   33.978326] input: HDA Intel Headphone as 
/devices/pci:00/:00:1b.0/sound/card0/input11
[   33.995462] platform regulatory.0: firmware: direct-loading firmware 
regulatory.db.p7s
[   34.096544] mc: Linux media interface: v0.10
[   34.354065] videodev: Linux video capture interface: v2.00
[   34.828689] ath: phy0: Enable LNA combining
[   34.836113] ath: phy0: ASPM enabled: 0x42
[   34.838973] ath: EEPROM regdomain: 0x65
[   34.838987] ath: EEPROM indicates we should expect a direct regpair map
[   34.838997] ath: Country alpha2 being used: 00
[   34.839003] ath: Regpair used: 0x65
[   34.846942] ieee80211 phy0: Selected rate control algorithm 'minstrel_ht'
[   34.923261] ieee80211 phy0: Atheros AR9285 Rev:2 mem=0xf7ec, irq=16
[   34.980443] ath9k :01:00.0 wls1: renamed from wlan0
[   35.217646] usb 5-2: Found UVC 1.00 device WebCam (0c45:62c0)
[   35.262889] input: WebCam: USB Camera as 
/devices/pci:00/:00:1d.7/usb5/5-2/5-2:1.0/input/input12
[   35.269416] usbcore: registered new interface driver uvcvideo
[   35.480559] Adding 999420k swap on /dev/sda5.  Priority:-2 extents:1 
across:999420k FS
[   63.314469] RPC: Registered named UNIX socket transport module.
[   63.316656] RPC: Registered udp transport module.
[   63.318684] RPC: Registered tcp transport module.
[   63.320698] RPC: Registered tcp NFSv4.1 backchannel transport module.
[   69.651676] alg: No test for fips(ansi_cprng) (fips_ansi_cprng)
[   73.012935] Bluetooth: Core ver 2.22
[   73.015890] NET: Registered PF_BLUETOOTH protocol family
[   73.019760] Bluetooth: HCI device and connection manager initialized
[   73.023933] Bluetooth: HCI socket layer initialized
[   73.026588] Bluetooth: L2CAP socket layer initialized
[   73.029041] Bluetooth: SCO socket layer initialized
[   79.076546] kauditd_printk_skb: 6 callbacks suppressed
[   79.076567] audit: type=1400 audit(1667385008.692:18): apparmor="DENIED" 
operation="capable" profile="/usr/sbin/cupsd" pid=554 comm="cupsd" 
capability=12  capname="net_admin"
[   79.245803] wls1: authenticate with 24:4b:fe:dc:3f:00
[   79.268328] wls1: bad VHT capabilities, disabling VHT
[   79.271146] wls1: 80 MHz not supported, disabling VHT
[   79.294527] wls1: send auth to 24:4b:fe:dc:3f:00 (try 1/3)
[   79.299564] wls1: authenticated
[   79.320286] wls1: associate with 24:4b:fe:dc:3f:00 (try 1/3)
[   79.338359] wls1: RX AssocResp from 24:4b:fe:dc:3f:00 (capab=0x411 status=0 
aid=12)
[   79.342379] wls1: associated
[   79.352240] ath: EEPROM regdomain: 0x8054
[   79.352267] ath: EEPROM indicates we should expect a country code
[   79.352280] ath: doing EEPROM country->regdmn map search
[   79.352292] ath: country maps to regdmn code: 0x55
[   79.352307] ath: Country alpha2 being used: BZ
[   79.352320] ath: Regpair used: 0x55
[   79.352333] ath: regdomain 0x8054 dynamically updated by country element
[   79.564997] IPv6: ADDRCONF(NETDEV_CHANGE): wls1: link becomes ready
[   79.633216] NET: Registered PF_QIPCRTR protocol family
[  117.318419] [ cut here ]
[  117.318446] kernel BUG at mm/memory.c:2660!
[  117.318470] invalid opcode:  [#1] PREEMPT SMP
[  117.318490] CPU: 1 PID: 640 Comm: Xorg Not tainted 6.0.0-2-686 #1  Debian 
6.0.5-1
[  117.318508] Hardware name: Acer   Aspire one  /Aspire one  , 
BIOS V1.08 07/09/2009
[  117.318520] EIP: __apply_to_page_range+0x370/0x470
[  117.318548] Code: 8b 7d cc 81 7d e4 e0 46 c4 c6 74 0e 89 c2 e9 71 ff ff ff 
8d b4 26 00 00 00 00 8b 7d d8 89 c1 e9 3f fd ff ff 8d b6 00 00 00 00 <0f> 0b 8d 
b6 00 00 00 00 85 c0 0f 84 c3 00 00 00 89 f7 89 c2 c1 ef
[  117.318564] EAX: 0001 EBX: a940 ECX: c4057a90 EDX: 02a4
[  117.318579] ESI: a936 EDI: a945 EBP: c3b63dcc ESP: c3b63d90
[  117.318592] DS: 007b ES: 007b FS: 00d8 GS: 0033 SS: 0068 EFLAGS: 00210202
[  117.318608] CR0: 80050033 CR2: a936 CR3: 04057000 CR4: 0

Bug#1021846: grub-install is broken since 2.06-3: error: unknown filesystem

[Steve McIntyre]

Hi!

On Thu, Oct 20, 2022 at 06:20:26PM +0100, Steve McIntyre wrote:
>On Thu, Oct 20, 2022 at 08:09:15PM +0300, программист некто wrote:
>># fsck.f2fs -f /dev/sda1
>>didn't report any errors.
>
>OK, that's good to know.
>
>>I can continue testing - rebuild without patches in turn, to reveal patch 
>>which break f2fs support.
>
>If you're happy to do that, then that would be excellent!

Did you get anywhere with this please? I'd like to try and fix this
for the next grub upload if we can! :-)

-- 
Steve McIntyre, Cambridge, UK.st...@einval.com
"Because heaters aren't purple!" -- Catherine Pitt

Bug#1011532: marked as done (icedtea-web: FTBFS with OpenJDK 17 due to pack200 removal)

[Debian Bug Tracking System]

Your message dated Wed, 02 Nov 2022 10:19:15 +
with message-id 
and subject line Bug#1011532: fixed in icedtea-web 1.8.8-2
has caused the Debian Bug report #1011532,
regarding icedtea-web: FTBFS with OpenJDK 17 due to pack200 removal
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.)


-- 
1011532: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011532
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: icedtea-web
Version: 1.8.8-1
Severity: important
Tags: ftbfs sid bookworm
User: debian-j...@lists.debian.org
Usertags: default-java17

icedtea-web fails to build with OpenJDK 17 due to the removal of the pack200 
tool and API:


  checking for pack200... checking for pack200... 
/usr/lib/jvm/default-java/bin/pack200
  configure: WARNING: "pack200 not found so custom part of run-netx-dist will 
fail"
  
  checking for hg... no
  checking for distribution package version... 1.8.8
  checking what version string to use... 1.8.8 (1.8.8)
  checking whether to build the browser plugin... no
  checking whether make supports the include directive... yes (GNU style)
  checking for pkg-config... /usr/bin/pkg-config
  checking pkg-config is at least version 0.9.0... yes
  checking whether to build plugin jar for javaws -html... no
  checking if java.util.jar.Pack200 is available from some.pkg (module "")... no
  configure: error: java.util.jar.Pack200 not found.
  make[1]: *** [debian/rules:12: override_dh_auto_configure] Error 1
  make[1]: Leaving directory '/<>'
  make: *** [debian/rules:8: build] Error 2
  dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2
--- End Message ---
--- Begin Message ---
Source: icedtea-web
Source-Version: 1.8.8-2
Done: Emmanuel Bourg 

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

Debian distribution maintenance software
pp.
Emmanuel Bourg  (supplier of updated icedtea-web 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, 02 Nov 2022 10:52:30 +0100
Source: icedtea-web
Architecture: source
Version: 1.8.8-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Java Maintainers 

Changed-By: Emmanuel Bourg 
Closes: 1011532
Changes:
 icedtea-web (1.8.8-2) unstable; urgency=medium
 .
   * Team upload.
   * Removed pack200 support to build with Java 17 (Closes: #1011532)
   * Standards-Version updated to 4.6.1
   * Updated the Homepage field
Checksums-Sha1:
 8d5ed747c6b3a9f72e308d1ef72edb021d2db555 2054 icedtea-web_1.8.8-2.dsc
 237b766c512e4549196876806541be9e3b804e22 27736 
icedtea-web_1.8.8-2.debian.tar.xz
 2d93f7f9a4cb6410bcc7838165f37131c92bed31 10716 
icedtea-web_1.8.8-2_source.buildinfo
Checksums-Sha256:
 7fdeaf1bb8d2731f588df3a4f6a6386d2d1e5b90f39d908bd128376c54ad004f 2054 
icedtea-web_1.8.8-2.dsc
 b4f3e238e94cf1a78f1580d000d31401d9578f1f6d56e4845256de6d4f75e101 27736 
icedtea-web_1.8.8-2.debian.tar.xz
 e32058669642e2ad3b1bfb5499b7c4702415b5ef2135c7e80b468e395d0ffee4 10716 
icedtea-web_1.8.8-2_source.buildinfo
Files:
 8c618149549abb09d627044b97390bf4 2054 java optional icedtea-web_1.8.8-2.dsc
 87169a26c930d6c46fe99caa598c17ca 27736 java optional 
icedtea-web_1.8.8-2.debian.tar.xz
 928d3685260aa77988dd3da8185d0a18 10716 java optional 
icedtea-web_1.8.8-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJGBAEBCgAwFiEEuM5N4hCA3PkD4WxA9RPEGeS50KwFAmNiPkUSHGVib3VyZ0Bh
cGFjaGUub3JnAAoJEPUTxBnkudCs5a4QAIdu717z57cY72ALfz1o1UylxaTn1QsH
GXMbf9DKwFjz3r+1iTMKCUppLsPxF2rv1SJfJl1xtY+GrdePf/cmMduqbqVx/pMi
xM23kBhg1xn5CwGB2WminmLkpU79u9j6Dp8D0R4Vd8EulUlD+bYqOYoHBHw8+1rL
Vi4aaxBecCtFvj8YhI/LAoh9ZHC/EhbPBj86f+Md1sT3dTcSuNKdajsB25no50O2
SkED4RBj6F8EU3slHfhaSj56qE1G10qmD/Q3qgp9m9NOMiPjJ27qN2/ZfPMPAZnT
NflT0GbyuIPWGFNTYv9MDBfJu0JEGvpKrne3DkB4uZyJZhDmIFgRq0Nig0I3FPIP
RJrwQVvOMlnO0kmc64KmizXQDGp561ttcP9COxvXhxEykk07wDr5qHUw7HIbDfrP
/D9qwJdq4RKbYQwe798ATf73yTLhgEzO79/h22JuXk+UZrDsoeySz9KSjJTTSXhN
2wd8b2m9sv1HoFS0/y4aiTe12WR67k0bl8g/4OGACATapLcls6PXFth8uOl8ZOWE
QPSy6XwI36KXoLwRbmaq9IfVYK9GpOqJ2l5DKnVdj5fkhS7UJd3PdO9Jb4azM+0j
NRom8dGIbTgP+UNGrPF0FJGhitokyZ+aFxOUqLj8

Bug#1011532: marked as pending in icedtea-web

[Emmanuel Bourg]

Control: tag -1 pending

Hello,

Bug #1011532 in icedtea-web 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/java-team/icedtea-web/-/commit/184c05ab121ad4f71a1ad7bd1d1de4fbc62cd2d0


Removed pack200 support to build with Java 17 (Closes: #1011532)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1011532

Processed: Bug#1011532 marked as pending in icedtea-web

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1011532 [src:icedtea-web] icedtea-web: FTBFS with OpenJDK 17 due to 
pack200 removal
Added tag(s) pending.

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

Bug#1023318: screen: re-adds /usr/bin/screen to /etc/shells on upgrade

[Helmut Grohne]

Source: screen
Version: 4.9.0-2
Tags: patch
Severity: serious
Justification: Debian policy 10.7.3

When upgrading or reinstalling screen, it adds /usr/bin/screen to
/etc/shells even if one locally removed it there. Such behaviour
violates Debian policy section 10.7.3. I propose managing the entry
declaratively using dpkg triggers and am attaching a patch for your
convenience.

Helmut
diff --minimal -Nru screen-4.9.0/debian/changelog screen-4.9.0/debian/changelog
--- screen-4.9.0/debian/changelog   2022-08-24 03:45:18.0 +0200
+++ screen-4.9.0/debian/changelog   2022-11-02 10:03:05.0 +0100
@@ -1,3 +1,10 @@
+screen (4.9.0-2.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Update /etc/shells using dpkg triggers. (Closes: #-1)
+
+ -- Helmut Grohne   Wed, 02 Nov 2022 10:03:05 +0100
+
 screen (4.9.0-2) unstable; urgency=medium
 
   * Add patch to fix bash example in man page. (LP: #1986839) Thanks to
diff --minimal -Nru screen-4.9.0/debian/control screen-4.9.0/debian/control
--- screen-4.9.0/debian/control 2022-08-23 19:15:25.0 +0200
+++ screen-4.9.0/debian/control 2022-11-02 10:03:05.0 +0100
@@ -18,7 +18,8 @@
 Package: screen
 Architecture: any
 Depends: ${misc:Depends},
- ${shlibs:Depends}
+ ${shlibs:Depends},
+ debianutils (>= 5.3-1~)
 Suggests: byobu | screenie | iselect (>= 1.4.0-1),
   ncurses-term
 Description: terminal multiplexer with VT100/ANSI terminal emulation
diff --minimal -Nru screen-4.9.0/debian/rules screen-4.9.0/debian/rules
--- screen-4.9.0/debian/rules   2021-08-05 15:30:52.0 +0200
+++ screen-4.9.0/debian/rules   2022-11-02 10:03:02.0 +0100
@@ -63,6 +63,7 @@
rm -f $(ROOT)/usr/share/info/dir*
# Remove documentation from udeb
rm -rf $(ROOT_UDEB)/usr/share/info $(ROOT_UDEB)/usr/share/man
+   install -D -m644 debian/shells 
$(ROOT)/usr/share/debianutils/shells.d/screen
 
 override_dh_installinit:
dh_installinit --no-start --init-script=screen-cleanup
diff --minimal -Nru screen-4.9.0/debian/screen.postinst 
screen-4.9.0/debian/screen.postinst
--- screen-4.9.0/debian/screen.postinst 2021-02-23 11:18:41.0 +0100
+++ screen-4.9.0/debian/screen.postinst 2022-11-02 10:00:59.0 +0100
@@ -30,8 +30,6 @@
   if [ ! -e $servicefile ]; then
   ln -s /dev/null $servicefile
   fi
-
-  add-shell /usr/bin/screen || true
 fi
 
 #DEBHELPER#
diff --minimal -Nru screen-4.9.0/debian/screen.postrm 
screen-4.9.0/debian/screen.postrm
--- screen-4.9.0/debian/screen.postrm   2021-02-18 09:51:15.0 +0100
+++ screen-4.9.0/debian/screen.postrm   2022-11-02 10:01:12.0 +0100
@@ -13,8 +13,4 @@
   rmdir -p --ignore-fail-on-non-empty /lib/systemd/system
 fi
 
-if [ "$1" = disappear ]; then
-  remove-shell /usr/bin/screen || true
-fi
-
 #DEBHELPER#
diff --minimal -Nru screen-4.9.0/debian/screen.prerm 
screen-4.9.0/debian/screen.prerm
--- screen-4.9.0/debian/screen.prerm2021-02-18 09:51:15.0 +0100
+++ screen-4.9.0/debian/screen.prerm1970-01-01 01:00:00.0 +0100
@@ -1,8 +0,0 @@
-#!/bin/sh
-set -e
-
-if [ "$1" = remove ] || [ "$1" = deconfigure ]; then
-  remove-shell /usr/bin/screen || true
-fi 
-
-#DEBHELPER#
diff --minimal -Nru screen-4.9.0/debian/shells screen-4.9.0/debian/shells
--- screen-4.9.0/debian/shells  1970-01-01 01:00:00.0 +0100
+++ screen-4.9.0/debian/shells  2022-11-02 10:02:02.0 +0100
@@ -0,0 +1 @@
+/usr/bin/screen

Bug#1023317: zsh: re-adds /bin/zsh to /etc/shells on upgrade

[Helmut Grohne]

Package: zsh,zsh-static
Version: 5.9-1
Tags: patch
Severity: serious
Justification: Debian policy 10.7.3

When upgrading or reinstalling zsh or zsh-static, it adds /bin/zsh or
/bin/zsh-static respectively to /etc/shells even if one locally removed
it there. Such behaviour violates Debian policy section 10.7.3. I
propose managing the entry declaratively using dpkg triggers and am
attaching a patch for your convenience.

Helmut
diff --minimal -Nru zsh-5.9/debian/changelog zsh-5.9/debian/changelog
--- zsh-5.9/debian/changelog2022-05-15 01:20:26.0 +0200
+++ zsh-5.9/debian/changelog2022-11-02 10:35:53.0 +0100
@@ -1,3 +1,10 @@
+zsh (5.9-1.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Manage /etc/shells using dpkg triggers. (Closes: #-1)
+
+ -- Helmut Grohne   Wed, 02 Nov 2022 10:35:53 +0100
+
 zsh (5.9-1) unstable; urgency=low
 
   * [73d31738,d4d20348,2ae4a398] Import new upstream release 5.9.
diff --minimal -Nru zsh-5.9/debian/control zsh-5.9/debian/control
--- zsh-5.9/debian/control  2022-05-15 01:17:30.0 +0200
+++ zsh-5.9/debian/control  2022-11-02 10:35:51.0 +0100
@@ -56,7 +56,8 @@
 Architecture: any
 Depends: zsh-common (= ${source:Version}),
  ${misc:Depends},
- ${shlibs:Depends}
+ ${shlibs:Depends},
+ debianutils (>= 5.3-1~)
 Pre-Depends: ${misc:Pre-Depends}
 Recommends: ${shlibs:Recommends}
 Suggests: zsh-doc
@@ -88,7 +89,8 @@
 
 Package: zsh-static
 Architecture: any
-Depends: ${misc:Depends}
+Depends: ${misc:Depends},
+ debianutils (>= 5.3-1~)
 Recommends: zsh-common
 Suggests: zsh-doc
 Built-Using: ${Built-Using}
diff --minimal -Nru zsh-5.9/debian/rules zsh-5.9/debian/rules
--- zsh-5.9/debian/rules2022-02-25 11:41:52.0 +0100
+++ zsh-5.9/debian/rules2022-11-02 10:35:22.0 +0100
@@ -158,6 +158,8 @@
  xargs sed -e 's@\.\./config\.h@config.h@;s@#\(\s*\)include 
"\([^"]\+\)"@#\1include @' -i
 
cd debian/zsh-dev/usr/share/aclocal; mv aczshoot.m4 zshoot.m4
+   install -D -m644 debian/zsh.shells 
debian/zsh/usr/share/debianutils/shells.d/zsh
+   install -D -m644 debian/zsh-static.shells 
debian/zsh-static/usr/share/debianutils/shells.d/zsh-static
 
 override_dh_gencontrol-arch:
dh_gencontrol -a -- -VBuilt-Using="$(BUILT_USING)"
diff --minimal -Nru zsh-5.9/debian/zsh-static.postinst 
zsh-5.9/debian/zsh-static.postinst
--- zsh-5.9/debian/zsh-static.postinst  2022-02-12 20:54:36.0 +0100
+++ zsh-5.9/debian/zsh-static.postinst  2022-11-02 10:33:49.0 +0100
@@ -4,9 +4,6 @@
 
 case "$1" in
 (configure)
-#if test -z "$2"; then
-   add-shell /bin/zsh-static
-#fi
 ;;
 
 abort-upgrade|abort-remove|abort-deconfigure)
diff --minimal -Nru zsh-5.9/debian/zsh-static.postrm 
zsh-5.9/debian/zsh-static.postrm
--- zsh-5.9/debian/zsh-static.postrm2022-02-12 20:54:36.0 +0100
+++ zsh-5.9/debian/zsh-static.postrm1970-01-01 01:00:00.0 +0100
@@ -1,11 +0,0 @@
-#!/bin/sh
-
-set -e
-
-case "$1" in
-   (remove)
-   remove-shell /bin/zsh-static
-   ;;
-esac
-
-#DEBHELPER#
diff --minimal -Nru zsh-5.9/debian/zsh-static.shells 
zsh-5.9/debian/zsh-static.shells
--- zsh-5.9/debian/zsh-static.shells1970-01-01 01:00:00.0 +0100
+++ zsh-5.9/debian/zsh-static.shells2022-11-02 10:33:46.0 +0100
@@ -0,0 +1 @@
+/bin/zsh-static
diff --minimal -Nru zsh-5.9/debian/zsh.postinst zsh-5.9/debian/zsh.postinst
--- zsh-5.9/debian/zsh.postinst 2022-02-12 20:54:36.0 +0100
+++ zsh-5.9/debian/zsh.postinst 2022-11-02 10:34:19.0 +0100
@@ -12,9 +12,6 @@
 
 case "$1" in
 (configure)
-add-shell /bin/zsh
-add-shell /usr/bin/zsh
-
# New hardcoded symlinks which unfortunately can't be shipped inside
# the package itself since some people want to merge /bin and /usr/bin
# against FHS and all Unix tradition.
diff --minimal -Nru zsh-5.9/debian/zsh.postrm zsh-5.9/debian/zsh.postrm
--- zsh-5.9/debian/zsh.postrm   2022-02-12 20:54:36.0 +0100
+++ zsh-5.9/debian/zsh.postrm   2022-11-02 10:34:27.0 +0100
@@ -4,9 +4,6 @@
 
 case "$1" in
(remove)
-   remove-shell /bin/zsh
-   remove-shell /usr/bin/zsh
-
# Remove hardcoded symlink again
if [ -L /usr/bin/zsh ]; then
  rm -f /usr/bin/zsh
diff --minimal -Nru zsh-5.9/debian/zsh.shells zsh-5.9/debian/zsh.shells
--- zsh-5.9/debian/zsh.shells   1970-01-01 01:00:00.0 +0100
+++ zsh-5.9/debian/zsh.shells   2022-11-02 10:34:14.0 +0100
@@ -0,0 +1,2 @@
+/bin/zsh
+/usr/bin/zsh

Bug#1023316: 9base: re-adds /bin/rc to /etc/shells on upgrade

[Helmut Grohne]

Source: 9base
Version: 1:6-12
Tags: patch
Severity: serious
Justification: Debian policy 10.7.3

If I remove /bin/rc from /etc/shells and then upgrade or reinstall
9base, it will re-add itself to /etc/shells. Such behaviour violates
Debian policy section 10.7.3. I propose moving to dpkg triggers and
update-shells to fix this issue and attach a patch for your convenience.

Helmut
diff --minimal -Nru 9base-6/debian/changelog 9base-6/debian/changelog
--- 9base-6/debian/changelog2022-03-17 21:15:01.0 +0100
+++ 9base-6/debian/changelog2022-11-02 09:45:01.0 +0100
@@ -1,3 +1,9 @@
+9base (1:6-13) UNRELEASED; urgency=medium
+
+  * Update /etc/shells via dpkg triggers. (Closes: #-1)
+
+ -- Helmut Grohne   Wed, 02 Nov 2022 09:45:01 +0100
+
 9base (1:6-12) unstable; urgency=medium
 
   * QA upload.
diff --minimal -Nru 9base-6/debian/control 9base-6/debian/control
--- 9base-6/debian/control  2022-03-17 21:15:01.0 +0100
+++ 9base-6/debian/control  2022-11-02 09:45:01.0 +0100
@@ -11,7 +11,7 @@
 
 Package: 9base
 Architecture: any
-Depends: ${misc:Depends}, ${shlibs:Depends}
+Depends: ${misc:Depends}, ${shlibs:Depends}, debianutils (>= 5.3-1~)
 Description: Plan 9 userland tools
  9base is a port of following original Plan 9 userland tools to Unix:
  ascii, awk, basename, bc, cal, cat, cleanname, cmp, date, dc, dd, diff, du,
diff --minimal -Nru 9base-6/debian/postinst 9base-6/debian/postinst
--- 9base-6/debian/postinst 2022-03-17 21:15:01.0 +0100
+++ 9base-6/debian/postinst 2022-11-02 09:45:01.0 +0100
@@ -5,10 +5,6 @@
 # and so we can maintain compatibility with rc scripts expecting /bin/rc
 update-alternatives --install /bin/rc rc /usr/lib/plan9/bin/rc 20
 
-# allow use of 9base' rc as a login shell:
-add-shell /bin/rc
-add-shell /usr/lib/plan9/bin/rc
-
 #DEBHELPER#
 
 exit 0
diff --minimal -Nru 9base-6/debian/postrm 9base-6/debian/postrm
--- 9base-6/debian/postrm   2022-03-17 21:15:01.0 +0100
+++ 9base-6/debian/postrm   1970-01-01 01:00:00.0 +0100
@@ -1,9 +0,0 @@
-#!/bin/sh
-set -e
-
-if [ "$1" = "remove" ]; then
-remove-shell /bin/rc
-remove-shell /usr/lib/plan9/bin/rc
-fi
-
-#DEBHELPER#
diff --minimal -Nru 9base-6/debian/rules 9base-6/debian/rules
--- 9base-6/debian/rules2022-03-17 21:15:01.0 +0100
+++ 9base-6/debian/rules2022-11-02 09:45:01.0 +0100
@@ -52,6 +52,8 @@
mv $$MANPAGE $${MANPAGE}$(MANEXT); \
done
 
+   install -D -m644 debian/shells 
$(PKGDIR)$(DATADIR)/debianutils/shells.d/plan9
+
 override_dh_fixperms:
dh_fixperms
 
diff --minimal -Nru 9base-6/debian/shells 9base-6/debian/shells
--- 9base-6/debian/shells   1970-01-01 01:00:00.0 +0100
+++ 9base-6/debian/shells   2022-11-02 09:45:01.0 +0100
@@ -0,0 +1,2 @@
+/bin/rc
+/usr/lib/plan9/bin/rc

Bug#1013259: samba-libs: Possible policy violation (now with unnecessary soname bump libndr.so.2 => libndr.so.3)

[Andreas Schneider]

On Tuesday, 1 November 2022 11:21:55 CET Michael Tokarev wrote:
> 01.11.2022 13:14, Ralph Boehme wrote:
> > On 11/1/22 09:15, Michael Tokarev via samba-technical wrote:
> >> Control: tag -1 + upstream
> >> 
> >> Original context was at http://bugs.debian.org/1013259 , but whole
> >> thing *now* has is about completely unnecessary soname bump of libndr
> >> in 4.17 due to debugging refinements.
> > 
> > to me this looks like a packaging bug.
> 
> It indeed is, I fixed it already.
> 
> The question remains though: why the .3 bump happened in the first
> place, due to a change just in a debug helper routine, which was
> trivial to avoid (like I've shown in the patches just posted to
> the list).

libndr is not a stable API it can change any time!

The only stable APIs in Samba are:

libtalloc
libtevent
libtdb
libsmbclient
libwbclient
libnetapi



Andreas


-- 
Andreas Schneider  a...@samba.org
Samba Team www.samba.org
GPG-ID: 8DFF53E18F2ABC8D8F3C92237EE0FC4DCC014E3D

Bug#1013259: samba-libs: Possible policy violation (now with unnecessary soname bump libndr.so.2 => libndr.so.3)

[Andreas Schneider]

On Tuesday, 1 November 2022 11:21:55 CET Michael Tokarev via samba-technical 
wrote:
> 01.11.2022 13:14, Ralph Boehme wrote:
> > On 11/1/22 09:15, Michael Tokarev via samba-technical wrote:
> >> Control: tag -1 + upstream
> >> 
> >> Original context was at http://bugs.debian.org/1013259 , but whole
> >> thing *now* has is about completely unnecessary soname bump of libndr
> >> in 4.17 due to debugging refinements.
> > 
> > to me this looks like a packaging bug.
> 
> It indeed is, I fixed it already.

See

https://src.fedoraproject.org/rpms/samba/blob/rawhide/f/samba.spec#_148


-- 
Andreas Schneider  a...@samba.org
Samba Team www.samba.org
GPG-ID: 8DFF53E18F2ABC8D8F3C92237EE0FC4DCC014E3D