Bug#1052136: marked as done (libcdb1: tries to overwrite /usr/share/man/man5/cdb.5.gz in tinycdb 0.78+b1)

[Debian Bug Tracking System]

Your message dated Mon, 18 Sep 2023 05:33:54 +
with message-id 
and subject line Bug#1052136: fixed in tinycdb 0.80-2
has caused the Debian Bug report #1052136,
regarding libcdb1: tries to overwrite /usr/share/man/man5/cdb.5.gz in tinycdb 
0.78+b1
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.)


-- 
1052136: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052136
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libcdb1
Version: 0.80-1
Severity: serious

When upgrading, I got:

Unpacking libcdb1:amd64 (0.80-1) over (0.78+b1) ...
dpkg: error processing archive 
/tmp/apt-dpkg-install-DmVfNl/25-libcdb1_0.80-1_amd64.deb (--unpack):
 trying to overwrite '/usr/share/man/man5/cdb.5.gz', which is also in package 
tinycdb 0.78+b1

Missing Breaks+Replaces?

-- System Information:
Debian Release: trixie/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'stable-updates'), (500, 
'stable-security'), (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 
'experimental')
merged-usr: no
Architecture: amd64 (x86_64)

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

Versions of packages libcdb1 depends on:
ii  libc6  2.37-10

libcdb1 recommends no packages.

libcdb1 suggests no packages.

-- no debconf information

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)
--- End Message ---
--- Begin Message ---
Source: tinycdb
Source-Version: 0.80-2
Done: Michael Tokarev 

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

Debian distribution maintenance software
pp.
Michael Tokarev  (supplier of updated tinycdb package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 18 Sep 2023 08:03:55 +0300
Source: tinycdb
Architecture: source
Version: 0.80-2
Distribution: unstable
Urgency: medium
Maintainer: Michael Tokarev 
Changed-By: Michael Tokarev 
Closes: 1052136
Changes:
 tinycdb (0.80-2) unstable; urgency=medium
 .
   * since cdb.5 has been moved from tinycdb to libcdb1 (since this manpage
 is referenced in cdb.3 too), add Replaces/Breaks (Closes: #1052136)
   * install NEWS to tinycdb too
Checksums-Sha1:
 c4eae705f3ed0c37a89b368db8146f80ff2dce7a 1472 tinycdb_0.80-2.dsc
 3fbf86ebb809cbc94b456b8a6dd544d48915bf63 5768 tinycdb_0.80-2.debian.tar.xz
 c124e5354ffbc614b9df8c7043c5cabd998f6360 6342 tinycdb_0.80-2_source.buildinfo
Checksums-Sha256:
 4958a3fc58bef0bdbdfbc2855622667442f797d8fef32e2b3fb2056673d1bbc6 1472 
tinycdb_0.80-2.dsc
 7ee9a6270c9e59b40ae7cc08b2912cef51fccfad0558d0b96a11cba3f2dfdd55 5768 
tinycdb_0.80-2.debian.tar.xz
 f3e065ff92f20517b7668092564ead6933314bfd0ae98f0dfde91de59c63dbdc 6342 
tinycdb_0.80-2_source.buildinfo
Files:
 35c2ae46f12c65308eb3ff2ed3c819b8 1472 utils optional tinycdb_0.80-2.dsc
 d110cf08bb182dad0e55e9774c18b025 5768 utils optional 
tinycdb_0.80-2.debian.tar.xz
 acc04ac1edb0a8fddc44d7f405bac2f9 6342 utils optional 
tinycdb_0.80-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQFDBAEBCgAtFiEEe3O61ovnosKJMUsicBtPaxppPlkFAmUH2ksPHG1qdEB0bHMu
bXNrLnJ1AAoJEHAbT2saaT5Z0c4H/RPLKcw9ZeKeqJFIbokKv7MZ6XwTZ6jAklBk
wQ6F4Zt6FcuGtvas35DvKz+JNZpEFhIiG38/E8P4xoxvzhUBs1eQKR5aQt9h0S1F
G24pFWd42UxD/lCFuIY785AI090x32ELU9CPTASikXKsPvRXvDqddbqx0mc0h5gy
OSNqZpsoSwcCQQ5vEn6L/5Gwaah6vtsqRYdTxOvYO7k9Tj40xlc/jeTvoZHakCCw
mUCbHMtNqm3cV5t1Jqq1mPQ861oLnnkW3uXDFnCibMs54n94EK06QNnwvBCMJi7q
vO4RV2oWHnjarK6TbaAnH/aQM2MieVdjxwUfSaceJE5YgAEDAGs=
=Pp7b
-END PGP SIGNATURE End Message ---

Bug#1052139: dead upstream, popcon <10

[Johannes Schauer Marin Rodrigues]

Source: morty
Severity: serious

Hi,

last upstream commit was in April 2021. This package was mainly useful
together with searx (from the same developer) but that project got
abandoned in favour of searxng by different people which does not need
morty anymore. Additionally, morty has a very low popcon.

Lets make sure that this package does not make it into the next stable
release by accident.

Thanks!

cheers, josch

Bug#1051563: Backporting mutt patches to Debian Buster

[Chris Frey]

On Sun, Sep 17, 2023 at 08:34:57PM +0300, Santiago Ruano Rincón wrote:
> Chris, thanks for preparing the patches. Much appreciated. I have a
> question though: Why are you placing those two patches in
> debian-specific, and not in upstream/? They come from the upstream repo.

I only put them there because I had to modify them for a clean patch.
I changed the headers to make it clear that I edited them, but kept
the original wording as well.

I didn't think it was right to modify the patch contents without
changing the name of who did it.

- Chris

Bug#1052136: libcdb1: tries to overwrite /usr/share/man/man5/cdb.5.gz in tinycdb 0.78+b1

[Vincent Lefevre]

Package: libcdb1
Version: 0.80-1
Severity: serious

When upgrading, I got:

Unpacking libcdb1:amd64 (0.80-1) over (0.78+b1) ...
dpkg: error processing archive 
/tmp/apt-dpkg-install-DmVfNl/25-libcdb1_0.80-1_amd64.deb (--unpack):
 trying to overwrite '/usr/share/man/man5/cdb.5.gz', which is also in package 
tinycdb 0.78+b1

Missing Breaks+Replaces?

-- System Information:
Debian Release: trixie/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'stable-updates'), (500, 
'stable-security'), (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 
'experimental')
merged-usr: no
Architecture: amd64 (x86_64)

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

Versions of packages libcdb1 depends on:
ii  libc6  2.37-10

libcdb1 recommends no packages.

libcdb1 suggests no packages.

-- no debconf information

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

Bug#1052040: marked as done (mmm-mode: post-install script fails)

[Debian Bug Tracking System]

Your message dated Sun, 17 Sep 2023 23:50:40 +
with message-id 
and subject line Bug#1052040: fixed in mmm-mode 0.5.9-2
has caused the Debian Bug report #1052040,
regarding mmm-mode: post-install script fails
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.)


-- 
1052040: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052040
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: mmm-mode
Version: 0.5.9-1
Severity: grave
Justification: renders package unusable
X-Debbugs-Cc: mister...@web.de

Dear Maintainer,

installation/upgrading of the package fails with the following output
(please excuse the automatic line wrapping of thunderbirds plain text mode):

# LANG=C apt -f install
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
0 upgraded, 0 newly installed, 0 to remove and 2 not upgraded.
1 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Setting up mmm-mode (0.5.9-1) ...
Install emacsen-common for emacs
emacsen-common: Handling install of emacsen flavor emacs
Install mmm-mode for emacs
install/mmm-mode: Handling install of emacsen flavor emacs
install/mmm-mode: byte-compiling for emacs

In toplevel form:
mmm-auto.el:178:4: Error: Wrong number of arguments: (3 . 4), 2

In toplevel form:
mmm-class.el:36:2: Error: Eager macro-expansion failure:
(wrong-number-of-arguments (3 . 4) 2)

In toplevel form:
mmm-cmds.el:36:2: Error: Eager macro-expansion failure:
(wrong-number-of-arguments (3 . 4) 2)

In toplevel form:
mmm-cweb.el:35:2: Error: Eager macro-expansion failure:
(wrong-number-of-arguments (3 . 4) 2)

In toplevel form:
mmm-defaults.el:37:2: Error: Eager macro-expansion failure:
(wrong-number-of-arguments (3 . 4) 2)

In toplevel form:
mmm-erb.el:62:2: Error: Eager macro-expansion failure:
(wrong-number-of-arguments (3 . 4) 2)

In toplevel form:
mmm-mason.el:36:2: Error: Eager macro-expansion failure:
(wrong-number-of-arguments (3 . 4) 2)

In toplevel form:
mmm-mode.el:93:2: Error: Eager macro-expansion failure:
(wrong-number-of-arguments (3 . 4) 2)

In toplevel form:
mmm-myghty.el:41:2: Error: Eager macro-expansion failure:
(wrong-number-of-arguments (3 . 4) 2)

In toplevel form:
mmm-noweb.el:44:2: Error: Eager macro-expansion failure:
(wrong-number-of-arguments (3 . 4) 2)

In toplevel form:
mmm-region.el:42:2: Error: Eager macro-expansion failure:
(wrong-number-of-arguments (3 . 4) 2)

In toplevel form:
mmm-rpm.el:45:2: Error: Eager macro-expansion failure:
(wrong-number-of-arguments (3 . 4) 2)

In toplevel form:
mmm-sample.el:38:2: Error: Eager macro-expansion failure:
(wrong-number-of-arguments (3 . 4) 2)

In toplevel form:
mmm-univ.el:35:2: Error: Eager macro-expansion failure:
(wrong-number-of-arguments (3 . 4) 2)
ERROR: install script from mmm-mode package failed
dpkg: error processing package mmm-mode (--configure):
 installed mmm-mode package post-installation script subprocess returned
error exit status 1
Errors were encountered while processing:
 mmm-mode
needrestart is being skipped since dpkg has failed
E: Sub-process /usr/bin/dpkg returned an error code (1)



Thanks for maintaining mmm-mode

Marcel

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

Kernel: Linux 6.5.3-1-siduction-amd64 (SMP w/12 CPU threads; PREEMPT)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8),
LANGUAGE=de:en_US
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages mmm-mode depends on:
ii  emacs-gtk [emacsen]  1:29.1+1-5
ii  emacsen-common   3.0.5

mmm-mode recommends no packages.

mmm-mode suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: mmm-mode
Source-Version: 0.5.9-2
Done: Alexander Zangerl 

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

Debian distribution maintenance software
pp.
Alexander Zangerl  (supplier of updated mmm-mode package)

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

Bug#1037370: marked as done (entangle: build-depends on transitional package libgdk-pixbuf2.0-dev)

[Debian Bug Tracking System]

Your message dated Sun, 17 Sep 2023 21:20:00 +
with message-id 
and subject line Bug#1037370: fixed in entangle 3.0-4
has caused the Debian Bug report #1037370,
regarding entangle: build-depends on transitional package libgdk-pixbuf2.0-dev
to be marked as done.

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

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


-- 
1037370: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037370
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: entangle
Version: 3.0-3
Severity: important
Tags: trixie sid
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: split-gdk-pixbuf

This package Build-Depends on libgdk-pixbuf2.0-dev.

In Debian 11, libgdk-pixbuf2.0-dev was split into two packages:

- libgdk-pixbuf-2.0-dev contains the supported gdk-pixbuf-2.0 library

- libgdk-pixbuf-xlib-2.0-dev contains the deprecated, unmaintained
  Xlib integration layer, gdk-pixbuf-xlib-2.0

If this package only requires functionality from gdk-pixbuf-2.0.pc
and , please update the build-dependency to
libgdk-pixbuf-2.0-dev.

If it also requires the Xlib integration gdk-pixbuf-xlib-2.0.pc and
 (unlikely), then you can also build-depend on
libgdk-pixbuf-xlib-2.0-dev until the package can be updated to remove
that requirement.

libgdk-pixbuf-2.0-dev was present in both Debian 11 and Debian 12, so
it is not necessary to have a "| libgdk-pixbuf2.0-dev" alternative
dependency, even for packages that are expected to be backported.

We should remove the libgdk-pixbuf2.0-dev transitional package during
the Debian 13 'trixie' cycle, so this bug is likely to become RC later.

Thanks,
smcv
--- End Message ---
--- Begin Message ---
Source: entangle
Source-Version: 3.0-4
Done: Bastian Germann 

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

Debian distribution maintenance software
pp.
Bastian Germann  (supplier of updated entangle package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 17 Sep 2023 22:35:09 +0200
Source: entangle
Architecture: source
Version: 3.0-4
Distribution: unstable
Urgency: medium
Maintainer: Debian PhotoTools Maintainers 

Changed-By: Bastian Germann 
Closes: 1037370
Changes:
 entangle (3.0-4) unstable; urgency=medium
 .
   * Team upload.
   * debian/control: move to libgdk-pixbuf-2.0-dev b-dep. (Closes: #1037370)
 .
   [ Debian Janitor ]
   * Refer to common license file for CC0-1.0.
   * Update standards version to 4.6.1, no changes needed.
Checksums-Sha1:
 c60107b806b0a6e301bcdf3734e48ac896d8b212 2211 entangle_3.0-4.dsc
 1f87f99fa6fd4bb2a19c295c7acd38376543db96 6632 entangle_3.0-4.debian.tar.xz
 879634bdd8936ff2cbe662aeac9d6ffafc16b75e 15416 entangle_3.0-4_source.buildinfo
Checksums-Sha256:
 cfea7c6297a46bf97b308fd152c341242728ce4df684e51ba3c8dee171ffa76e 2211 
entangle_3.0-4.dsc
 b9796ac49eab323e68d80b5cd37fa74f367ff813ccea44234f5daec8c923ae93 6632 
entangle_3.0-4.debian.tar.xz
 38a41fa8be17f56430bf4b3e080d060999b7c6150c489eb0049123d30ab626f8 15416 
entangle_3.0-4_source.buildinfo
Files:
 27a8857b64144cf0414df45c77b99ef8 2211 utils optional entangle_3.0-4.dsc
 2df9ac3fe2bed4749a93077da89a9e5f 6632 utils optional 
entangle_3.0-4.debian.tar.xz
 87dd8ed108abba07bc124a0123a2c2c6 15416 utils optional 
entangle_3.0-4_source.buildinfo

-BEGIN PGP SIGNATURE-

iQHEBAEBCgAuFiEEQGIgyLhVKAI3jM5BH1x6i0VWQxQFAmUHZJkQHGJhZ2VAZGVi
aWFuLm9yZwAKCRAfXHqLRVZDFP6gDAC5o7MhCtkPLbA0Syertkn99xIZpEa9iE/r
VgYRBkv3IiI3UapjXjlaBUaaOikeoM64Yb2JRyIXUQm7rSfDJ6GixDU6+bsyXrk0
Ku2aEzFu507N3OISzHi6Aisa8HPJaWGvJyekxWTbEJBF6yGDnswrVy7wzsZhWuLV
cfNcd1vfUGLVabt31bAxqQ3p04hh1nV2Z0+3n6sDV+13SkHXCRaKUaok94R+Lf+B
/MB7f7OAx/Tgumi0Ixa3lq3kwLaKO/kQ/Sttd5B8fhYLsYE9jaqQBrYxPjcY9WI/
tieHQhRPjDhKX5vfkisHDnQ/K/CSynBrPUcjMMizuWvUpMv1iDOim0nYtY79YH9w
Ej2fhbA0uBe4tSAnoXcz5KxxBJYqigqqdMuGURjRD8y099tTaJjNiAzJzYB+T+K4
JHFX2YUCdQhpIbU25ivlJ2FBzRj+fsqsbMkGJZMGdnOikFdweKVrMzhMMsXa/uCT
9iL0U4r5CJeHQOfFQtH9z8ua5xs3INQ=
=iqjS
-END PGP SIGNATURE End Message ---

Bug#1037374: giggle: build-depends on transitional package libgdk-pixbuf2.0-dev

[Bastian Germann]

Version: 0.7-6

Bug#1037374: marked as done (giggle: build-depends on transitional package libgdk-pixbuf2.0-dev)

[Debian Bug Tracking System]

Your message dated Sun, 17 Sep 2023 22:48:46 +0200
with message-id 
and subject line Re: giggle: build-depends on transitional package 
libgdk-pixbuf2.0-dev
has caused the Debian Bug report #1037374,
regarding giggle: build-depends on transitional package libgdk-pixbuf2.0-dev
to be marked as done.

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

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


-- 
1037374: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037374
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: giggle
Version: 0.7-5
Severity: important
Tags: trixie sid
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: split-gdk-pixbuf

This package Build-Depends on libgdk-pixbuf2.0-dev.

In Debian 11, libgdk-pixbuf2.0-dev was split into two packages:

- libgdk-pixbuf-2.0-dev contains the supported gdk-pixbuf-2.0 library

- libgdk-pixbuf-xlib-2.0-dev contains the deprecated, unmaintained
  Xlib integration layer, gdk-pixbuf-xlib-2.0

If this package only requires functionality from gdk-pixbuf-2.0.pc
and , please update the build-dependency to
libgdk-pixbuf-2.0-dev.

If it also requires the Xlib integration gdk-pixbuf-xlib-2.0.pc and
 (unlikely), then you can also build-depend on
libgdk-pixbuf-xlib-2.0-dev until the package can be updated to remove
that requirement.

libgdk-pixbuf-2.0-dev was present in both Debian 11 and Debian 12, so
it is not necessary to have a "| libgdk-pixbuf2.0-dev" alternative
dependency, even for packages that are expected to be backported.

We should remove the libgdk-pixbuf2.0-dev transitional package during
the Debian 13 'trixie' cycle, so this bug is likely to become RC later.

Thanks,
smcv
--- End Message ---
--- Begin Message ---

Version: 0.7-6--- End Message ---

Bug#1052087: marked as done (CVE-2023-42464: 0-day vulnerability in afpd Spotlight RPC)

[Debian Bug Tracking System]

Your message dated Sun, 17 Sep 2023 20:41:40 +
with message-id 
and subject line Bug#1052087: fixed in netatalk 3.1.17~ds-1
has caused the Debian Bug report #1052087,
regarding CVE-2023-42464: 0-day vulnerability in afpd Spotlight RPC
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.)


-- 
1052087: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052087
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: netatalk
Version: 3.1.12~ds-3
Severity: critical
Tags: security
Justification: root security hole

A 0-day vulnerability patch has been published for the upstream project.

The CVE record has not been made public yet, but this is the body of the
advisory for the record:

A Type Confusion vulnerability was found in the Spotlight RPC functions
in Netatalk's afpd daemon. When parsing Spotlight RPC packets, one
encoded data structure is a key-value style dictionary where the keys
are character strings, and the values can be any of the supported types
in the underlying protocol. Due to a lack of type checking in callers of
the dalloc_value_for_key() function, which returns the object associated
with a key, a malicious actor may be able to fully control the value of
the pointer and theoretically achieve Remote Code Execution on the host.

The underlying code for Spotlight queries in Netatalk shares a common
heritage with Samba, and hence the root cause and fix are logically
identical with those described in CVE-2023-34967.

https://github.com/Netatalk/netatalk/issues/486

-- System Information:
Debian Release: 10.13
  APT prefers oldoldstable
  APT policy: (500, 'oldoldstable')
Architecture: amd64 (x86_64)

Kernel: Linux 6.1.0-12-amd64 (SMP w/4 CPU cores; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL 
set to C.UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to 
C.UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: unable to detect

Versions of packages netatalk depends on:
ii  libacl1  2.2.53-4
ii  libattr1 1:2.4.48-4
ii  libavahi-client3 0.7-4+deb10u1
ii  libavahi-common3 0.7-4+deb10u1
ii  libc62.28-10+deb10u1
ii  libdb5.3 5.3.28+dfsg1-0.5
ii  libdbus-1-3  1.12.20-0+deb10u1
ii  libdbus-glib-1-2 0.110-4
ii  libgcrypt20  1.8.4-5+deb10u1
ii  libglib2.0-0 2.58.3-2+deb10u3
ii  libldap-2.4-22.4.47+dfsg-3+deb10u7
ii  libpam-modules   1.3.1-5
ii  libpam0g 1.3.1-5
ii  libtalloc2   2.1.14-2
ii  libtdb1  1.3.16-2+b1
ii  libtracker-sparql-2.0-0  2.1.8-2
ii  libwrap0 7.6.q-28
ii  lsb-base 10.2019051400
ii  netbase  5.6
ii  perl 5.28.1-6+deb10u1

Versions of packages netatalk recommends:
ii  avahi-daemon  0.7-4+deb10u1
ii  dbus  1.12.20-0+deb10u1
ii  lsof  4.91+dfsg-1
ii  procps2:3.3.15-2
ii  python3   3.7.3-1
ii  python3-dbus  1.2.8-3
ii  tracker   2.1.8-2

Versions of packages netatalk suggests:
pn  quota  

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: netatalk
Source-Version: 3.1.17~ds-1
Done: Jonas Smedegaard 

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

Debian distribution maintenance software
pp.
Jonas Smedegaard  (supplier of updated netatalk package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 17 Sep 2023 21:58:16 +0200
Source: netatalk
Architecture: source
Version: 3.1.17~ds-1
Distribution: unstable
Urgency: high
Maintainer: Debian Netatalk team 
Changed-By: Jonas Smedegaard 
Closes: 1040065 1052087
Changes:
 netatalk (3.1.17~ds-1) unstable; urgency=high
 .
   [ upstream ]
   * new release(s)
 + Use non-interactive PAM session when available
   closes: bug#1040065, thanks to Richard van den Berg
 + Renames asip-status.pl to asip-status
 + Removes uniconv and cnid2_create from distribution
 + FIX CVE-2023-42464:
 

Bug#1051860: marked as done (ccls: FTBFS with llvm-toolchain-16 das default)

[Debian Bug Tracking System]

Your message dated Sun, 17 Sep 2023 20:34:58 +
with message-id 
and subject line Bug#1051860: fixed in ccls 0.20230717-1
has caused the Debian Bug report #1051860,
regarding ccls: FTBFS with llvm-toolchain-16 das default
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.)


-- 
1051860: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1051860
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ccls
Version: 0.20220729-2
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: sramac...@debian.org

https://buildd.debian.org/status/fetch.php?pkg=ccls=arm64=0.20220729-2%2Bb1=1694628056=0

/usr/bin/c++  -I/<>/src -isystem /<>/third_party 
-isystem /usr/lib/llvm-16/include -g -O2 -ffile-prefix-map=/<>=. 
-fstack-protector-strong -fstack-clash-protection -Wformat 
-Werror=format-security -mbranch-protection=standard -Wdate-time 
-D_FORTIFY_SOURCE=2 -std=c++17 -Wall -Wno-sign-compare -Wno-return-type 
-Wno-unused-result -MD -MT CMakeFiles/ccls.dir/src/pipeline.cc.o -MF 
CMakeFiles/ccls.dir/src/pipeline.cc.o.d -o 
CMakeFiles/ccls.dir/src/pipeline.cc.o -c /<>/src/pipeline.cc
/<>/src/indexer.cc:1097:8: error: ‘void 
ccls::{anonymous}::IndexPPCallbacks::InclusionDirective(clang::SourceLocation, 
const clang::Token&, llvm::StringRef, bool, clang::CharSourceRange, 
llvm::Optional, llvm::StringRef, llvm::StringRef, const 
clang::Module*, clang::SrcMgr::CharacteristicKind)’ marked ‘override’, but does 
not override
 1097 |   void InclusionDirective(SourceLocation hashLoc, const Token ,
  |^~

Cheers
-- 
Sebastian Ramacher
--- End Message ---
--- Begin Message ---
Source: ccls
Source-Version: 0.20230717-1
Done: Shengjing Zhu 

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

Debian distribution maintenance software
pp.
Shengjing Zhu  (supplier of updated ccls 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: Thu, 14 Sep 2023 19:25:36 +0800
Source: ccls
Architecture: source
Version: 0.20230717-1
Distribution: unstable
Urgency: medium
Maintainer: Shengjing Zhu 
Changed-By: Shengjing Zhu 
Closes: 1051860
Changes:
 ccls (0.20230717-1) unstable; urgency=medium
 .
   * New upstream release 0.20230717
 + Supports LLVM-16 (Closes: #1051860)
Checksums-Sha1:
 8a10fc7ea6fe333173e41f48c6a2dd2532923e24 1323 ccls_0.20230717-1.dsc
 10fafaa3c1ec34e15576c50b3e05a15ea0387aff 161857 ccls_0.20230717.orig.tar.gz
 08d1c63d85219462c647caf0a342313aa432db43 8172 ccls_0.20230717-1.debian.tar.xz
 aee5c5f1e3febd0c138ff4f0cbdcac2edd22ec5f 7584 ccls_0.20230717-1_amd64.buildinfo
Checksums-Sha256:
 f1e829a955d9e186f5ec64d4e4344f264c4110d7e679804eaad96438ef36056d 1323 
ccls_0.20230717-1.dsc
 ede854033f6d93583e83325a611e5dc4eaf961e5ef48a84f22f7bd6daadf84b8 161857 
ccls_0.20230717.orig.tar.gz
 f62c211897c2cafa4890d2a3fabcb1d7383f0a941a5f48ca8938ae7fa3fef8e6 8172 
ccls_0.20230717-1.debian.tar.xz
 9a343f8b7f8717324f31538e9db800eae2e046dcf736d65017bbcbf964fa41ed 7584 
ccls_0.20230717-1_amd64.buildinfo
Files:
 6b3bb70fe568f21b9b9ed2151720a4cc 1323 devel optional ccls_0.20230717-1.dsc
 2b48d1d45426e788c20ca1b6ede75ba6 161857 devel optional 
ccls_0.20230717.orig.tar.gz
 2480ed4fe05098ac54decc3f35e9f715 8172 devel optional 
ccls_0.20230717-1.debian.tar.xz
 f338c4a555f4a27e0c5278312b05e14b 7584 devel optional 
ccls_0.20230717-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iHUEARYIAB0WIQSRhdT1d2eu7mxV1B5/RPol6lUUywUCZQdW+QAKCRB/RPol6lUU
y198AP0aZwzjmpSP8QXl4p730KHMVbreUEi3sQHB2AbDYiYspAEAwA8Nwhtz91Jk
stqW09EBXx4oo91h03rbX1j06Gh4YwI=
=b15V
-END PGP SIGNATURE End Message ---

Bug#1037373: marked as done (geany-plugins: build-depends on transitional package libgdk-pixbuf2.0-dev)

[Debian Bug Tracking System]

Your message dated Sun, 17 Sep 2023 20:37:05 +
with message-id 
and subject line Bug#1037373: fixed in geany-plugins 1.38+dfsg-2.1
has caused the Debian Bug report #1037373,
regarding geany-plugins: build-depends on transitional package 
libgdk-pixbuf2.0-dev
to be marked as done.

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

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


-- 
1037373: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037373
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: geany-plugins
Version: 1.38+dfsg-2
Severity: important
Tags: trixie sid
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: split-gdk-pixbuf

This package Build-Depends on libgdk-pixbuf2.0-dev.

In Debian 11, libgdk-pixbuf2.0-dev was split into two packages:

- libgdk-pixbuf-2.0-dev contains the supported gdk-pixbuf-2.0 library

- libgdk-pixbuf-xlib-2.0-dev contains the deprecated, unmaintained
  Xlib integration layer, gdk-pixbuf-xlib-2.0

If this package only requires functionality from gdk-pixbuf-2.0.pc
and , please update the build-dependency to
libgdk-pixbuf-2.0-dev.

If it also requires the Xlib integration gdk-pixbuf-xlib-2.0.pc and
 (unlikely), then you can also build-depend on
libgdk-pixbuf-xlib-2.0-dev until the package can be updated to remove
that requirement.

libgdk-pixbuf-2.0-dev was present in both Debian 11 and Debian 12, so
it is not necessary to have a "| libgdk-pixbuf2.0-dev" alternative
dependency, even for packages that are expected to be backported.

We should remove the libgdk-pixbuf2.0-dev transitional package during
the Debian 13 'trixie' cycle, so this bug is likely to become RC later.

Thanks,
smcv
--- End Message ---
--- Begin Message ---
Source: geany-plugins
Source-Version: 1.38+dfsg-2.1
Done: Bastian Germann 

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

Debian distribution maintenance software
pp.
Bastian Germann  (supplier of updated geany-plugins package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 17 Sep 2023 19:58:30 +
Source: geany-plugins
Architecture: source
Version: 1.38+dfsg-2.1
Distribution: unstable
Urgency: medium
Maintainer: Geany Packaging Team 
Changed-By: Bastian Germann 
Closes: 1037373 1041807
Changes:
 geany-plugins (1.38+dfsg-2.1) unstable; urgency=medium
 .
   * Non-maintainer upload
   * Drop unused Build-Depends: libwnck-dev (Closes: #1041807)
   * Move to Build-Depends: libgdk-pixbuf-2.0-dev (Closes: #1037373)
Checksums-Sha1:
 0c2c71d7c44d5d801c0947538872786d14d98a43 5544 geany-plugins_1.38+dfsg-2.1.dsc
 839b414446c4d976f8a4616dc437f6828fd5105c 26072 
geany-plugins_1.38+dfsg-2.1.debian.tar.xz
 606639341cc69c4d121f561d7760edd60c77eee4 19734 
geany-plugins_1.38+dfsg-2.1_source.buildinfo
Checksums-Sha256:
 f81a07855223b8ee3ba0f514c81a1140dcaef91b627f6c7f2ea812a26c1c4d5d 5544 
geany-plugins_1.38+dfsg-2.1.dsc
 a0c7678349281fc6e671580e540026a130eaa9489bf96e0d205310fc416fd9c9 26072 
geany-plugins_1.38+dfsg-2.1.debian.tar.xz
 cb135adab872c90c8273e9f7757b6dc6f71ec445eff34cde38020ffdc07e9f5c 19734 
geany-plugins_1.38+dfsg-2.1_source.buildinfo
Files:
 10ed1680ef7301da366d6306f1f9d21f 5544 devel optional 
geany-plugins_1.38+dfsg-2.1.dsc
 0b99aefd3b0c429043934eed1e88ae4d 26072 devel optional 
geany-plugins_1.38+dfsg-2.1.debian.tar.xz
 0729c3bde2e7ddc4130499d091989329 19734 devel optional 
geany-plugins_1.38+dfsg-2.1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQHEBAEBCgAuFiEEQGIgyLhVKAI3jM5BH1x6i0VWQxQFAmUHYDIQHGJhZ2VAZGVi
aWFuLm9yZwAKCRAfXHqLRVZDFMTCC/0e22R4gq/TqatWd/Hgo75m9LhQO9o2nBBt
ifZwRv3TzBLxHKWuTT7eKArqqrgBye/UbVOU/pIS3+L9HokE7Q6HDaCvP5Ke0Wm6
CpZzBiTYX+M+G1r61F+ebCsy2zzRKluscr/u41aH+QZTd8rkpB4kJoxw/D85jDsF
v1rhnayGM8V+8tLRDz4YTiMCebM/9Zbj9XMZdxf8Gm61ImPsu8Uk+FCIuZObw80G
7nN4Nn0GpUQ+wlrNQg46scp1iALY849PE8VPWFvHc6FGpWPT9J5QAk8vlZTwvj/M
0jUZbSacrmeqD0rfMDhS1kokiRLYES/XxJ5Cnn95H5QaQtTBH7yxBRe/E0TjUBKg
hJ9qQoPV7fJWbGL02U9ZwlVOs7BfmUJ7ujabrGbgSEP5zvuIT7WdqG/HqRVWhq9D
CDhbQOg0Q4BA45RznO++M6AtlEsqY629RxmXBKKosTsMPFO0DnwOg0lDLeidmRjr
Yo7UkOoa24sv7101NmZJg0VL3rTaSS4=
=J1y1
-END PGP SIGNATURE 

Bug#1037373: geany-plugins: NMU 1.38+dfsg-2.1

[Bastian Germann]

I am uploading a NMU to fix this. The debdiff is attached.diff -Nru geany-plugins-1.38+dfsg/debian/changelog 
geany-plugins-1.38+dfsg/debian/changelog
--- geany-plugins-1.38+dfsg/debian/changelog2022-12-15 03:11:13.0 
+
+++ geany-plugins-1.38+dfsg/debian/changelog2023-09-17 19:58:30.0 
+
@@ -1,3 +1,11 @@
+geany-plugins (1.38+dfsg-2.1) unstable; urgency=medium
+
+  * Non-maintainer upload
+  * Drop unused Build-Depends: libwnck-dev (Closes: #1041807)
+  * Move to Build-Depends: libgdk-pixbuf-2.0-dev (Closes: #1037373)
+
+ -- Bastian Germann   Sun, 17 Sep 2023 19:58:30 +
+
 geany-plugins (1.38+dfsg-2) unstable; urgency=medium
 
   * [386780f] Refresh patches and add patch to drop bundled gpgme.m4.
diff -Nru geany-plugins-1.38+dfsg/debian/control 
geany-plugins-1.38+dfsg/debian/control
--- geany-plugins-1.38+dfsg/debian/control  2022-12-15 03:11:13.0 
+
+++ geany-plugins-1.38+dfsg/debian/control  2023-09-17 19:57:28.0 
+
@@ -18,11 +18,10 @@
python3-docutils,
libxml2-dev (>= 2.6.27),
libsoup2.4-dev (>= 2.4.0),
-   libgdk-pixbuf2.0-dev (>= 2.0),
+   libgdk-pixbuf-2.0-dev (>= 2.0),
libgpgme11-dev,
libvte-2.91-dev,
libwebkit2gtk-4.0-dev,
-   libwnck-dev (>= 2.10.0),
libmarkdown2-dev,
libgit2-dev,
valac (>= 0.7.0),

Bug#1051883: marked as done (qttools-opensource-src: FTBFS with llvm-toolchain-16 as default)

[Debian Bug Tracking System]

Your message dated Sun, 17 Sep 2023 19:38:33 +
with message-id 
and subject line Bug#1051883: fixed in qttools-opensource-src 5.15.10-5
has caused the Debian Bug report #1051883,
regarding qttools-opensource-src: FTBFS with llvm-toolchain-16 as default
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.)


-- 
1051883: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1051883
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: qttools-opensource-src
Version: 5.15.10-3
Severity: serious
Tags: ftbfs sid trixie
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: sramac...@debian.org

https://buildd.debian.org/status/fetch.php?pkg=qttools-opensource-src=amd64=5.15.10-3%2Bb1=1694632815=0

* Start testing of tst_QtDiag *
Config: Using QtTest library 5.15.10, Qt 5.15.10 (x86_64-little_endian-lp64 
shared (dynamic) release build; by GCC 13.1.0), debian unknown
PASS   : tst_QtDiag::initTestCase()
QDEBUG : tst_QtDiag::run() Launching  "/<>/bin/qtdiag"
QDEBUG : tst_QtDiag::run() 
Qt 5.15.10 (x86_64-little_endian-lp64 shared (dynamic) release build; by GCC 
13.1.0) on "minimal" 
OS: Debian GNU/Linux trixie/sid [linux version 5.10.0-25-amd64]

Architecture: x86_64; features: SSE2 SSE3 SSSE3 SSE4.1 SSE4.2 AVX AVX2

Environment:
  QMAKE="/usr/lib/qt5/bin/qmake"
  QT_PLUGIN_PATH="/usr/lib/x86_64-linux-gnu/qt5/plugins"
  QT_QPA_PLATFORM="minimal"
  QT_QTESTLIB_RUNNING="1"
  QT_SELECT="qt5"

Features: QT_NO_EXCEPTIONS

Library info:
  PrefixPath: /usr
  DocumentationPath: /usr/share/qt5/doc
  HeadersPath: /usr/include/x86_64-linux-gnu/qt5
  LibrariesPath: /usr/lib/x86_64-linux-gnu
  LibraryExecutablesPath: /usr/lib/x86_64-linux-gnu/qt5/libexec
  BinariesPath: /usr/lib/qt5/bin
  PluginsPath: /usr/lib/x86_64-linux-gnu/qt5/plugins
  ImportsPath: /usr/lib/x86_64-linux-gnu/qt5/imports
  Qml2ImportsPath: /usr/lib/x86_64-linux-gnu/qt5/qml
  ArchDataPath: /usr/lib/x86_64-linux-gnu/qt5
  DataPath: /usr/share/qt5
  TranslationsPath: /usr/share/qt5/translations
  ExamplesPath: /usr/lib/x86_64-linux-gnu/qt5/examples
  TestsPath: /usr/tests
  SettingsPath: /etc/xdg

Standard paths [*...* denote writable entry]:
  DesktopLocation: "Desktop" 
*/<>/debian/.debhelper/generated/_source/home/Desktop*
  DocumentsLocation: "Documents" 
*/<>/debian/.debhelper/generated/_source/home/Documents*
  FontsLocation: "Fonts" 
*/<>/debian/.debhelper/generated/_source/home/.local/share/fonts* 
/<>/debian/.debhelper/generated/_source/home/.fonts 
/usr/local/share/fonts /usr/share/fonts
  ApplicationsLocation: "Applications" 
*/<>/debian/.debhelper/generated/_source/home/.local/share/applications*
 /usr/local/share/applications /usr/share/applications
  MusicLocation: "Music" 
*/<>/debian/.debhelper/generated/_source/home/Music*
  MoviesLocation: "Movies" 
*/<>/debian/.debhelper/generated/_source/home/Videos*
  PicturesLocation: "Pictures" 
*/<>/debian/.debhelper/generated/_source/home/Pictures*
  TempLocation: "Temporary Directory" */tmp*
  HomeLocation: "Home" 
*/<>/debian/.debhelper/generated/_source/home*
  AppLocalDataLocation: "Application Data" 
*/<>/debian/.debhelper/generated/_source/home/.local/share/QtProject/qtdiag*
 /usr/local/share/QtProject/qtdiag /usr/share/QtProject/qtdiag
  CacheLocation: "Cache" 
*/<>/debian/.debhelper/generated/_source/home/.cache/QtProject/qtdiag*
  GenericDataLocation: "Shared Data" 
*/<>/debian/.debhelper/generated/_source/home/.local/share* 
/usr/local/share /usr/share
  RuntimeLocation: "Runtime" */tmp/dh-xdg-rundir-ueoJZ1G6*
  ConfigLocation: "Configuration" 
*/<>/debian/.debhelper/generated/_source/home/.config* /etc/xdg
  DownloadLocation: "Download" 
*/<>/debian/.debhelper/generated/_source/home/Downloads*
  GenericCacheLocation: "Shared Cache" 
*/<>/debian/.debhelper/generated/_source/home/.cache*
  GenericConfigLocation: "Shared Configuration" 
*/<>/debian/.debhelper/generated/_source/home/.config* /etc/xdg
  AppDataLocation: "Application Data" 
*/<>/debian/.debhelper/generated/_source/home/.local/share/QtProject/qtdiag*
 /usr/local/share/QtProject/qtdiag /usr/share/QtProject/qtdiag
  AppConfigLocation: "Application Configuration" 
*/<>/debian/.debhelper/generated/_source/home/.config/QtProject/qtdiag*
 /etc/xdg/QtProject/qtdiag

File selectors (increasing order of precedence):
  C unix linux debian

Network:
  Using "OpenSSL 3.0.10 1 Aug 2023", version: 0x30a0

Platform capabilities: ThreadedPixmaps MultipleWindows NonFullScreenWindows 
NativeWidgets WindowManagement

Style hints:
  mouseDoubleClickInterval: 400
  

Bug#1052129: acpica-unix: Failed to migrate to Testing; missing s390x build not properly handled

[Adam D. Barratt]

On Sun, 2023-09-17 at 14:58 -0400, Boyuan Yang wrote:
> If you are clear that upstream is completely not supporting big-
> endian build anymore, please
> submit a package removal request to Debian Release Team (using
> reportbug tool) to remove
> the current s390x package in Debian Testing.

No. Architecture-specific removals happen in unstable, so the request
needs to be made to the FTP Team.

Regards,

Adam

Bug#1052129: acpica-unix: Failed to migrate to Testing; missing s390x build not properly handled

[Boyuan Yang]

Source: acpica-unix
Version: 20230628-1
Severity: serious
X-Debbugs-CC: ivan...@canonical.com
Tags: sid

Hi Ivan Hu,

In the latest Debian package upload of acpica-unix/20230628-1, you removed 
big-endian support
for this package. However, you did not request to sync such changes with Debian 
Testing to
have existing big-endian packages (notably the s390x in Debian Testing). As a 
result, your
new upload cannot migrate to Debian Testing. It is likely that your package 
also stuck in
Ubuntu's -proposed repo for the same reason. You can check the package's 
condition at [1]
(and [2] for Ubuntu).

If you are clear that upstream is completely not supporting big-endian build 
anymore, please
submit a package removal request to Debian Release Team (using reportbug tool) 
to remove
the current s390x package in Debian Testing. If you don't know how to do it, 
please let me
know via email asap and I can help to make the report. Some similar effort may 
also be
necessary on the Ubuntu side.

Thanks, and please let me know if you have further questions.

[1] https://tracker.debian.org/pkg/acpica-unix
[2] https://launchpad.net/ubuntu/+source/acpica-unix

Regards,
Boyuan Yang


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

Bug#1051822: marked as done (installed chrony package post-installation script subprocess returned error exit status 1)

[Debian Bug Tracking System]

Your message dated Sun, 17 Sep 2023 18:34:25 +
with message-id 
and subject line Bug#1051822: fixed in chrony 4.4-2
has caused the Debian Bug report #1051822,
regarding installed chrony package post-installation script subprocess returned 
error 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.)


-- 
1051822: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1051822
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: chrony
Version: 4.2-2
Severity: critical

# dpkg -i /mnt/apt/archives/chrony_4.4-1_i386.deb
(Reading database ... 34682 files and directories currently installed.)
Preparing to unpack .../archives/chrony_4.4-1_i386.deb ...
Failed to stop chronyd-restricted.service: Unit chronyd-restricted.service not 
loaded.
Unpacking chrony (4.4-1) over (4.3-4) ...
Setting up chrony (4.4-1) ...
Unknown option: comment
adduser [--home DIR] [--shell SHELL] [--no-create-home] [--uid ID]
[--firstuid ID] [--lastuid ID] [--gecos GECOS] [--ingroup GROUP | --gid ID]
[--disabled-password] [--disabled-login] [--add_extra_groups] USER
   Add a normal user

adduser --system [--home DIR] [--shell SHELL] [--no-create-home] [--uid ID]
[--gecos GECOS] [--group | --ingroup GROUP | --gid ID] [--disabled-password]
[--disabled-login] [--add_extra_groups] USER
   Add a system user

adduser --group [--gid ID] GROUP
addgroup [--gid ID] GROUP
   Add a user group

addgroup --system [--gid ID] GROUP
   Add a system group

adduser USER GROUP
   Add an existing user to an existing group

general options:
  --quiet | -q  don't give process information to stdout
  --force-badname   allow usernames which do not match the
NAME_REGEX configuration variable
  --help | -h   usage message
  --version | -vversion number and copyright
  --conf | -c FILE  use FILE as configuration file

dpkg: error processing package chrony (--install):
 installed chrony package post-installation script subprocess returned error 
exit status 1
Processing triggers for man-db (2.11.2-3) ...
Errors were encountered while processing:
 chrony
--- End Message ---
--- Begin Message ---
Source: chrony
Source-Version: 4.4-2
Done: Vincent Blut 

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

Debian distribution maintenance software
pp.
Vincent Blut  (supplier of updated chrony 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: Thu, 14 Sep 2023 20:28:27 +0200
Source: chrony
Architecture: source
Version: 4.4-2
Distribution: unstable
Urgency: medium
Maintainer: Vincent Blut 
Changed-By: Vincent Blut 
Closes: 1051822
Changes:
 chrony (4.4-2) unstable; urgency=medium
 .
   * debian/control:
 - Add version constraint on adduser. (Closes: #1051822)
 .
   * debian/.gitlab-ci.yml:
 - Run CI on unstable.
Checksums-Sha1:
 d080cf6b984bfdf5bdca2cfc7cda520a2bbeac19 2350 chrony_4.4-2.dsc
 56b4984236472a73cddd382a35de0acb324a5e39 40816 chrony_4.4-2.debian.tar.xz
Checksums-Sha256:
 5722d03586a47e2ca1e5a45f61c828e1e219e6ff466b6e59abaaf7fc75cd348c 2350 
chrony_4.4-2.dsc
 cce0654567296c9f161d5353026e42fa94ff001aed452c5b613e094614520730 40816 
chrony_4.4-2.debian.tar.xz
Files:
 fd94fd1dbdb08d0c3133b49137d9b8ca 2350 net optional chrony_4.4-2.dsc
 ae8269a226d2dd5b24d014345a895bdb 40816 net optional chrony_4.4-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQEzBAEBCAAdFiEEWLZtSHNr6TsFLeZynFyZ6wW9dQoFAmUHQLgACgkQnFyZ6wW9
dQp40AgAkHRQlVnG8VIXw275RjlbzgROBrQtc9CA2UQ5JLF5DSIDbpsr5z35N6xJ
XNo5hOyMN+gmOr+d0H30AjSRhbXyXs5wucir6HLu1XC6iYMPdqt8QHpFWKrAq3kP
xO9IOtyqOWOHNYfQGtH9K1lFXyIkNcUArmbotBL8r1gCeRMudqBRtvCLOzd5/tbX
xQeH49Hv2JJhFD1PSQ+32uUou9tMPpanmelckbsi+7noRGcTHo9I27xutCTVmPAf
mBDZhPJOuTTYoirwohhBxQ1AYo26yRb7VChneezSBpSdSdmJOEVDE3vd/k1iwhC4
SD2tqKXzbT6owMfVSJWjHK8BDgWbRQ==
=4tcv
-END PGP SIGNATURE End Message ---

Bug#1051883: marked as pending in qttools-opensource-src

[Dmitry Shachnev]

Hi Sebastian!

On Sun, Sep 17, 2023 at 08:14:44PM +0200, Sebastian Ramacher wrote:
> Control: reopen -1
> 
> On 2023-09-17 14:13:08 +, Dmitry Shachnev wrote:
> > Control: tag -1 pending
> > 
> > Hello,
> > 
> > Bug #1051883 in qttools-opensource-src 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/qt-kde-team/qt/qttools/-/commit/c29ff951dc40dd804542a6dbbb9a32854e3087d8
> > 
> > 
> > Build with LLVM 15 for now.
> > 
> > Closes: #1051883.
> 
> The build fails with llvm-toolchain-15 in the same way. Looks like llvm
> is not the cause of the FTBFS.

No, it fails not in the same way.

With llvm-toolchain-16 the failed tests were qdoc tests:
tst_generatedOutput::webXmlFromCpp() and tst_generatedOutput::preparePhase(),
which are directly related to LLVM (qdoc uses it to parse C++ code). I spent
some time searching for an upstream fix, but with no luck (upstream does not
support 5.15 branch officially anymore, and with 6.4.2 I get different
failures in this test).

Now, these two tests passed, but tst_QHelpEngineCore::setCollectionFile()
failed, which is something new (it did not fail in my local build).

I will investigate.

--
Dmitry Shachnev


signature.asc
Description: PGP signature

Processed: Re: Bug#1051883: marked as pending in qttools-opensource-src

[Debian Bug Tracking System]

Processing control commands:

> reopen -1
Bug #1051883 {Done: Dmitry Shachnev } 
[src:qttools-opensource-src] qttools-opensource-src: FTBFS with 
llvm-toolchain-16 as default
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions qttools-opensource-src/5.15.10-4.

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

Bug#1051883: marked as pending in qttools-opensource-src

[Sebastian Ramacher]

Control: reopen -1

On 2023-09-17 14:13:08 +, Dmitry Shachnev wrote:
> Control: tag -1 pending
> 
> Hello,
> 
> Bug #1051883 in qttools-opensource-src 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/qt-kde-team/qt/qttools/-/commit/c29ff951dc40dd804542a6dbbb9a32854e3087d8
> 
> 
> Build with LLVM 15 for now.
> 
> Closes: #1051883.

The build fails with llvm-toolchain-15 in the same way. Looks like llvm
is not the cause of the FTBFS.

Cheers
-- 
Sebastian Ramacher

Bug#1051563: Backporting mutt patches to Debian Buster

[Santiago Ruano Rincón]

hi!

El 16/09/23 a las 15:44, Utkarsh Gupta escribió:
> Hi Chris,
> 
> On Fri, Sep 15, 2023 at 8:09 PM Chris Frey  wrote:
> > Attached is a patch that applies to the unpackaged sources of Debian 
> > Buster's
> > version of mutt 1.10.
> >
> > It includes 3 patches:
> >
> > upstream/Fix-rfc2047-base64-decoding-to-abort-on-illegal-char.patch
> > debian-specific/Check-for-NULL-userhdrs.patch
> > debian-specific/Fix-write_one_header-illegal-header-check.patch
> >
> > First one applied from Bullseye.  The other two I modified slightly
> > to match the older sources.
> 
> Many thanks, as usual. I'll look into it and let you know if we hit a
> bump backporting it.

Utkarsh, I have claimed mutt in both {d,e}la-needed, and started to work
preparing the repo. I am also OK if you want to finish the work.

Chris, thanks for preparing the patches. Much appreciated. I have a
question though: Why are you placing those two patches in
debian-specific, and not in upstream/? They come from the upstream repo.

Cheers!

 -- Santiago


signature.asc
Description: PGP signature

Bug#1043124: [Pkg-zfsonlinux-devel] Bug#1043124: consider skipping trying to build on affected kernels?

[M. Zhou]

On Sun, 2023-09-17 at 14:12 +0200, Ari wrote:
> Have you, maintainers of zfs, considered configuring the packages so
> that it skips trying to build of affected kernels?
> This would at least reduce the time of installing any packages
> drastically - currently my system tries to build it for two kernels
> every time I install any package, because the kernel packages fail
> the configuration stage.
> Maybe with this approach it would be even feasible that the kernels'
> installation state would not be failed for which compilation failed?
> After all, the kernel installed correctly, but it's rather the zfs
> package that is broken.

While it indeed increases the speed of dpkg configuration steps,
skipping the build or silently leave the kernel installation without
failure is seriously wrong for many use cases, I believe.

Bug#1010589: marked as done (cgreen: links to libraries from binutils which are not considered stable)

[Debian Bug Tracking System]

Your message dated Sun, 17 Sep 2023 17:19:09 +
with message-id 
and subject line Bug#1010589: fixed in cgreen 1.6.2-1~exp1
has caused the Debian Bug report #1010589,
regarding cgreen: links to libraries from binutils which are not considered 
stable
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.)


-- 
1010589: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1010589
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: cgreen
Version: 1.5.1-1
Severity: serious
X-Debbugs-Cc: gin...@debian.org, d...@debian.org

Dear maintainer,

Quoting from bug #949570:
Your package should not use the private binutils shared libraries.  If
it cannot be dropped, then please link those statically and document
it with the Built-Using tag in the binary package.

libbfd and libopcodes seem to be considered as a private interface
because their API/ABI is too unstable. This is stated in the
description:

Description: GNU binary utilities (BFD development files)
 This package includes header files and static libraries necessary to build
 programs which use the GNU BFD library, which is part of binutils.  Note
 that building Debian packages which depend on the shared libbfd is Not
 Allowed.

Paul
--- End Message ---
--- Begin Message ---
Source: cgreen
Source-Version: 1.6.2-1~exp1
Done: Gavin Lai (賴建宇) 

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

Debian distribution maintenance software
pp.
Gavin Lai (賴建宇)  (supplier of updated cgreen package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 15 Aug 2023 23:18:11 +0800
Source: cgreen
Architecture: source
Version: 1.6.2-1~exp1
Distribution: experimental
Urgency: medium
Maintainer: Gavin Lai (賴建宇) 
Changed-By: Gavin Lai (賴建宇) 
Closes: 1010589
Changes:
 cgreen (1.6.2-1~exp1) experimental; urgency=medium
 .
   * Import new upstream release
   * d/control:
 - Bump Standards-Version to 4.6.2
 - Remove libbdf-dev from build-deps (Closes: #1010589)
 - Add libxml2-dev to build-deps
 - Add Recommends libcgreen1-dev in cgreen1
   * Update symbols
   * Add a patch to fix man page error
Checksums-Sha1:
 c062f00285e4cc7f99e804d02a7e43f35da6b676 2123 cgreen_1.6.2-1~exp1.dsc
 4c8c14ab54fc89b6519fe3e3886d4eaed6db5c9d 460983 cgreen_1.6.2.orig.tar.gz
 a3a3df5453737846f12645315ed2a63291975074 6084 cgreen_1.6.2-1~exp1.debian.tar.xz
Checksums-Sha256:
 eb59d00993128d049048f44799e53a6bc5cda613d012e2d1ebd184b396722448 2123 
cgreen_1.6.2-1~exp1.dsc
 fe6be434cbe280330420106bd5d667f1bc84ae9468960053100dbf17071036b9 460983 
cgreen_1.6.2.orig.tar.gz
 15e8025d867968342053fbdeabce492fa2a2e906981dd72ebf420f5a66483355 6084 
cgreen_1.6.2-1~exp1.debian.tar.xz
Files:
 49675564bb6b7df87b9b66dbce44c570 2123 libs optional cgreen_1.6.2-1~exp1.dsc
 6bf879c0d8c5ea4c17a925b30c0878e9 460983 libs optional cgreen_1.6.2.orig.tar.gz
 97a3b587ab86c2660f141e2fbf1c88ad 6084 libs optional 
cgreen_1.6.2-1~exp1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEOqx5beTsH5XZFt4rQPKZLOx+xqsFAmUHLm4ACgkQQPKZLOx+
xqutSg/7Bmf/sj28QfYbdVOCmbG0gNarFc5YVCjFXyklsmIz8H3DTMPOxltpv/XW
mNXal2VSDvUvKyoByVgT1t//qDSYJrsvnK3GGIraJ99TgwUPf/l4DiSxAJn4dP4x
AkTlrWW6EmoIQrQhAI9+woDREyASI/6BFEKWbSQCvHCye2r3cIdnESlSTPja7w/A
ry1B444uxk+jxMQpu9VKjq7wORX2uxT2N4cx5minnJz9Ns/nozE8KkOHDp/ketYy
IkB30/sNlF9tVd52g4yIT4ru2mpzG7DOTU9JmY/ZBcO02bCoUTS22Vu6yaNrXlLS
uCYSpUVGQlwoiNoqK+FDF0F3v9eniKfgesQvXEPYRH378KZK+IOe+6gby/HmYbsY
Om9X93UwT0g79yh1JHFWFFcSzEVp8oNJ6KuMO9RWYsLQw6Q8tm00q8PsyNlGE0q8
XX1h4JHcCuE2u4Qq+M9g2XYFiAvtGgJ7yKGxq4eD9Sapborqg9hvRmDu0v5yodUg
hSqcxPUcm1WhfIVdf8hY1BbL4X1aRO/O7ASBBpOfAaOQ6B3z4R2JimOkd6pbeo0q
2h8+NyD0vKSpfOwvuKo0KBe4WjDDswDJQcTHK+xKDC60F8LoiSvOR2ZdH5dF3y2D
hjAfehTUdGXeeowRGdrKiNOIV6xZfFzxzfPSr8Z4qStyjRbX8U0=
=LxFC
-END PGP SIGNATURE End Message ---

Bug#1051883: marked as done (qttools-opensource-src: FTBFS with llvm-toolchain-16 as default)

[Debian Bug Tracking System]

Your message dated Sun, 17 Sep 2023 16:23:03 +
with message-id 
and subject line Bug#1051883: fixed in qttools-opensource-src 5.15.10-4
has caused the Debian Bug report #1051883,
regarding qttools-opensource-src: FTBFS with llvm-toolchain-16 as default
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.)


-- 
1051883: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1051883
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: qttools-opensource-src
Version: 5.15.10-3
Severity: serious
Tags: ftbfs sid trixie
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: sramac...@debian.org

https://buildd.debian.org/status/fetch.php?pkg=qttools-opensource-src=amd64=5.15.10-3%2Bb1=1694632815=0

* Start testing of tst_QtDiag *
Config: Using QtTest library 5.15.10, Qt 5.15.10 (x86_64-little_endian-lp64 
shared (dynamic) release build; by GCC 13.1.0), debian unknown
PASS   : tst_QtDiag::initTestCase()
QDEBUG : tst_QtDiag::run() Launching  "/<>/bin/qtdiag"
QDEBUG : tst_QtDiag::run() 
Qt 5.15.10 (x86_64-little_endian-lp64 shared (dynamic) release build; by GCC 
13.1.0) on "minimal" 
OS: Debian GNU/Linux trixie/sid [linux version 5.10.0-25-amd64]

Architecture: x86_64; features: SSE2 SSE3 SSSE3 SSE4.1 SSE4.2 AVX AVX2

Environment:
  QMAKE="/usr/lib/qt5/bin/qmake"
  QT_PLUGIN_PATH="/usr/lib/x86_64-linux-gnu/qt5/plugins"
  QT_QPA_PLATFORM="minimal"
  QT_QTESTLIB_RUNNING="1"
  QT_SELECT="qt5"

Features: QT_NO_EXCEPTIONS

Library info:
  PrefixPath: /usr
  DocumentationPath: /usr/share/qt5/doc
  HeadersPath: /usr/include/x86_64-linux-gnu/qt5
  LibrariesPath: /usr/lib/x86_64-linux-gnu
  LibraryExecutablesPath: /usr/lib/x86_64-linux-gnu/qt5/libexec
  BinariesPath: /usr/lib/qt5/bin
  PluginsPath: /usr/lib/x86_64-linux-gnu/qt5/plugins
  ImportsPath: /usr/lib/x86_64-linux-gnu/qt5/imports
  Qml2ImportsPath: /usr/lib/x86_64-linux-gnu/qt5/qml
  ArchDataPath: /usr/lib/x86_64-linux-gnu/qt5
  DataPath: /usr/share/qt5
  TranslationsPath: /usr/share/qt5/translations
  ExamplesPath: /usr/lib/x86_64-linux-gnu/qt5/examples
  TestsPath: /usr/tests
  SettingsPath: /etc/xdg

Standard paths [*...* denote writable entry]:
  DesktopLocation: "Desktop" 
*/<>/debian/.debhelper/generated/_source/home/Desktop*
  DocumentsLocation: "Documents" 
*/<>/debian/.debhelper/generated/_source/home/Documents*
  FontsLocation: "Fonts" 
*/<>/debian/.debhelper/generated/_source/home/.local/share/fonts* 
/<>/debian/.debhelper/generated/_source/home/.fonts 
/usr/local/share/fonts /usr/share/fonts
  ApplicationsLocation: "Applications" 
*/<>/debian/.debhelper/generated/_source/home/.local/share/applications*
 /usr/local/share/applications /usr/share/applications
  MusicLocation: "Music" 
*/<>/debian/.debhelper/generated/_source/home/Music*
  MoviesLocation: "Movies" 
*/<>/debian/.debhelper/generated/_source/home/Videos*
  PicturesLocation: "Pictures" 
*/<>/debian/.debhelper/generated/_source/home/Pictures*
  TempLocation: "Temporary Directory" */tmp*
  HomeLocation: "Home" 
*/<>/debian/.debhelper/generated/_source/home*
  AppLocalDataLocation: "Application Data" 
*/<>/debian/.debhelper/generated/_source/home/.local/share/QtProject/qtdiag*
 /usr/local/share/QtProject/qtdiag /usr/share/QtProject/qtdiag
  CacheLocation: "Cache" 
*/<>/debian/.debhelper/generated/_source/home/.cache/QtProject/qtdiag*
  GenericDataLocation: "Shared Data" 
*/<>/debian/.debhelper/generated/_source/home/.local/share* 
/usr/local/share /usr/share
  RuntimeLocation: "Runtime" */tmp/dh-xdg-rundir-ueoJZ1G6*
  ConfigLocation: "Configuration" 
*/<>/debian/.debhelper/generated/_source/home/.config* /etc/xdg
  DownloadLocation: "Download" 
*/<>/debian/.debhelper/generated/_source/home/Downloads*
  GenericCacheLocation: "Shared Cache" 
*/<>/debian/.debhelper/generated/_source/home/.cache*
  GenericConfigLocation: "Shared Configuration" 
*/<>/debian/.debhelper/generated/_source/home/.config* /etc/xdg
  AppDataLocation: "Application Data" 
*/<>/debian/.debhelper/generated/_source/home/.local/share/QtProject/qtdiag*
 /usr/local/share/QtProject/qtdiag /usr/share/QtProject/qtdiag
  AppConfigLocation: "Application Configuration" 
*/<>/debian/.debhelper/generated/_source/home/.config/QtProject/qtdiag*
 /etc/xdg/QtProject/qtdiag

File selectors (increasing order of precedence):
  C unix linux debian

Network:
  Using "OpenSSL 3.0.10 1 Aug 2023", version: 0x30a0

Platform capabilities: ThreadedPixmaps MultipleWindows NonFullScreenWindows 
NativeWidgets WindowManagement

Style hints:
  mouseDoubleClickInterval: 400
  

Bug#1051883: marked as pending in qttools-opensource-src

[Dmitry Shachnev]

Control: tag -1 pending

Hello,

Bug #1051883 in qttools-opensource-src 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/qt-kde-team/qt/qttools/-/commit/c29ff951dc40dd804542a6dbbb9a32854e3087d8


Build with LLVM 15 for now.

Closes: #1051883.


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1051883

Processed: Bug#1051883 marked as pending in qttools-opensource-src

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1051883 [src:qttools-opensource-src] qttools-opensource-src: FTBFS with 
llvm-toolchain-16 as default
Added tag(s) pending.

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

Bug#1052078: smifb2-dkms: module does not build for kernels w/o DRM or I2C

[Sudip Mukherjee]

On Sun, 17 Sept 2023 at 08:00, Andreas Beckmann  wrote:
>
> Package: smifb2-dkms
> Version: 2.2.3.4.g1828e79-1
> Severity: serious
>
> Hi,
>
> the smifb2 module does not build for the -cloud kernel due to missing
> I2C symbols and does not build for the armel and s390x kernels due to
> missign DRM symbols.
>
> https://ci.debian.net/packages/s/smifb2/
>
> Probably all that is needed is to add
>
> BUILD_EXCLUSIVE_CONFIG="CONFIG_DRM CONFIG_I2C"

Thanks a lot Andreas. I have not used dkms before and I was struggling
to find this out. And now that you have mentioned it, I can find it in
the man page.


-- 
Regards
Sudip

Bug#1051116: maildrop: depends on libgcc1, which is no longer in the archive

[Vincent Lefevre]

On 2023-09-17 13:05:16 +0200, Sebastian Ramacher wrote:
> On 2023-09-03 02:26:55 +0200, Vincent Lefevre wrote:
> > Package: maildrop
> > Version: 2.9.3-2+b1
> > Severity: grave
> > Justification: renders package unusable
> > 
> > maildrop depends on libgcc1, which is no longer in the archive.
> > This can be checked on
> > 
> >   https://packages.debian.org/en/bullseye/maildrop
> > 
> > which says:
> > 
> >   dep: libgcc1 (>= 1:3.0) [not armel, armhf, i386, mipsel]
> >   Package not available
> 
> libgcc1 is provided by libgcc-s1:
[...]

Indeed. I think that I got confused by bug 557328 (which I noticed only
after the upgrade to bookworm). While libgcc-s1 was installed, libgcc1
was not removed by "apt autoremove", and "aptitude why libgcc1" said
that maildrop depended on it, hence the confusion.

BTW, I'm wondering why libgcc-s1 doesn't have a "Breaks:" on libgcc1
in order to have libgcc1 uninstalled automatically. This would have
avoided the issue.

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

Bug#1052090: gnome-shell-extension-bluetooth-quick-connect: needs update for GNOME Shell 45

[Simon McVittie]

Package: gnome-shell-extension-bluetooth-quick-connect
Version: 36-2
Severity: serious
Tags: trixie sid upstream
Forwarded: https://github.com/bjarosze/gnome-bluetooth-quick-connect/issues/88
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: gnome-shell-45
X-Debbugs-Cc: debian-gtk-gn...@lists.debian.org

As with every 6-month GNOME Shell release cycle, extensions will need to
be updated for GNOME Shell 45, which is currently being prepared in
experimental. A porting guide is available here:
https://gjs.guide/extensions/upgrading/gnome-shell-45.html

For the 44 -> 45 transition, most or all extensions will need
incompatible code changes, because GNOME Shell has switched from
non-standard gjs modules ("const Foo = imports.gi.Foo") to ECMAScript
modules ("import Foo from 'gi://Foo'") and all extensions need to do
the same. This means most or all extensions will split into a branch
for Shell <= 44 (which might not be maintained upstream any more) and
a branch for Shell >= 45.

I don't intend to put time into this change myself, because I no longer
use this extension (see #1043008), so I'm marking this as serious already
(justification: "in the package maintainer's opinion, makes the package
unsuitable for release"). If anyone else in the GNOME team wants to see
this extension stay available in Debian, now is your chance to take over
the package, at which point the severity of this bug becomes your choice.

If nobody steps up to maintain it, I will ask for this extension to be
removed when we are ready for the GNOME Shell 45 transition.

Thanks,
smcv

Processed: bug 1052087 is forwarded to https://github.com/Netatalk/netatalk/issues/486, tagging 1052087

[Debian Bug Tracking System]

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

> forwarded 1052087 https://github.com/Netatalk/netatalk/issues/486
Bug #1052087 [netatalk] CVE-2023-42464: 0-day vulnerability in afpd Spotlight 
RPC
Set Bug forwarded-to-address to 
'https://github.com/Netatalk/netatalk/issues/486'.
> tags 1052087 + upstream
Bug #1052087 [netatalk] CVE-2023-42464: 0-day vulnerability in afpd Spotlight 
RPC
Added tag(s) upstream.
> thanks
Stopping processing here.

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

Bug#1051374: breaks existing setups using /etc/default/mini-httpd

[Alexandru Mihail]

Hello,

> I successfully tested the following patch to the .service file:
> 
> @@ -5,7 +5,8 @@
>  [Service]
>  Type=forking
>  PIDFile=/run/mini_httpd.pid
> -ExecStart=/usr/sbin/mini_httpd -C /etc/mini-httpd.conf
> +EnvironmentFile=-/etc/default/mini-httpd
> +ExecStart=/usr/sbin/mini_httpd -C /etc/mini-httpd.conf $DAEMON_OPTS
> -i /run/mini_httpd.pid
>  
>  [Install]
>  WantedBy=multi-user.target
> 
Thanks for your input and suggestions :)
> The EnvironmentFile uses "=-" to support a non-existant
> /etc/default/mini-httpd. The ExecStart line also adds a -i option to
> make sure
> that neither /etc/mini-httpd.conf nor $DAEMON_OPTS can set -i to
> something that
> is different from the path in PIDFile.
> 
> What do you think?
This is great, I successfully tested your proposed service file changes
and everything appears to work great !
We're currently on mini-httpd/unstable,now 1.30-4;
The next release (1.30-5) will incorporate your fix, closing this bug.

> 
> Thanks!
> 
> cheers, josch
Thanks to you too !
Best,
Alexandru 



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

Bug#1052087: Versions affected

[Daniel Markstedt]

Please note: The vulnerability also affects 3.1.12~ds-8 in oldstable, and 
3.1.15~ds-3 in unstable.

stable isn't distributing a netatalk package.

Bug#1052087: CVE-2023-42464: 0-day vulnerability in afpd Spotlight RPC

[Daniel Markstedt]

Package: netatalk
Version: 3.1.12~ds-3
Severity: critical
Tags: security
Justification: root security hole

A 0-day vulnerability patch has been published for the upstream project.

The CVE record has not been made public yet, but this is the body of the
advisory for the record:

A Type Confusion vulnerability was found in the Spotlight RPC functions
in Netatalk's afpd daemon. When parsing Spotlight RPC packets, one
encoded data structure is a key-value style dictionary where the keys
are character strings, and the values can be any of the supported types
in the underlying protocol. Due to a lack of type checking in callers of
the dalloc_value_for_key() function, which returns the object associated
with a key, a malicious actor may be able to fully control the value of
the pointer and theoretically achieve Remote Code Execution on the host.

The underlying code for Spotlight queries in Netatalk shares a common
heritage with Samba, and hence the root cause and fix are logically
identical with those described in CVE-2023-34967.

https://github.com/Netatalk/netatalk/issues/486

-- System Information:
Debian Release: 10.13
  APT prefers oldoldstable
  APT policy: (500, 'oldoldstable')
Architecture: amd64 (x86_64)

Kernel: Linux 6.1.0-12-amd64 (SMP w/4 CPU cores; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL 
set to C.UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to 
C.UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: unable to detect

Versions of packages netatalk depends on:
ii  libacl1  2.2.53-4
ii  libattr1 1:2.4.48-4
ii  libavahi-client3 0.7-4+deb10u1
ii  libavahi-common3 0.7-4+deb10u1
ii  libc62.28-10+deb10u1
ii  libdb5.3 5.3.28+dfsg1-0.5
ii  libdbus-1-3  1.12.20-0+deb10u1
ii  libdbus-glib-1-2 0.110-4
ii  libgcrypt20  1.8.4-5+deb10u1
ii  libglib2.0-0 2.58.3-2+deb10u3
ii  libldap-2.4-22.4.47+dfsg-3+deb10u7
ii  libpam-modules   1.3.1-5
ii  libpam0g 1.3.1-5
ii  libtalloc2   2.1.14-2
ii  libtdb1  1.3.16-2+b1
ii  libtracker-sparql-2.0-0  2.1.8-2
ii  libwrap0 7.6.q-28
ii  lsb-base 10.2019051400
ii  netbase  5.6
ii  perl 5.28.1-6+deb10u1

Versions of packages netatalk recommends:
ii  avahi-daemon  0.7-4+deb10u1
ii  dbus  1.12.20-0+deb10u1
ii  lsof  4.91+dfsg-1
ii  procps2:3.3.15-2
ii  python3   3.7.3-1
ii  python3-dbus  1.2.8-3
ii  tracker   2.1.8-2

Versions of packages netatalk suggests:
pn  quota  

-- no debconf information

Bug#1043124: consider skipping trying to build on affected kernels?

[Ari]

Have you, maintainers of zfs, considered configuring the packages so that it 
skips trying to build of affected kernels?
This would at least reduce the time of installing any packages drastically - 
currently my system tries to build it for two kernels every time I install any 
package, because the kernel packages fail the configuration stage.
Maybe with this approach it would be even feasible that the kernels' 
installation state would not be failed for which compilation failed? After all, 
the kernel installed correctly, but it's rather the zfs package that is broken.

thanks!null

Processed: Re: Bug#1052058: apt: refuses to downgrade itself to a version that works on the system

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #1052058 [apt] apt: refuses to downgrade itself to a version that works on 
the system
Severity set to 'serious' from 'important'

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

Bug#1052085: golang-github-traefik-yaegi: FTBFS: test failures

[Sebastian Ramacher]

Source: golang-github-traefik-yaegi
Version: 0.15.1-2
Severity: serious
Tags: ftbfs sid trixie
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: sramac...@debian.org

https://buildd.debian.org/status/fetch.php?pkg=golang-github-traefik-yaegi=amd64=0.15.1-2%2Bb2=1694894705=0

=== RUN   TestInterpConsistencyBuild/cli7.go
runtime: marked free object in span 0x7f24ecbf6c48, elemsize=176 freeindex=1 
(bad use of unsafe.Pointer? try -d=checkptr)
0xc000544000 alloc marked  
0xc0005440b0 free  unmarked
0xc000544160 free  unmarked
0xc000544210 free  unmarked
0xc0005442c0 free  unmarked
0xc000544370 free  unmarked
0xc000544420 free  unmarked
0xc0005444d0 free  unmarked
0xc000544580 free  unmarked
0xc000544630 free  unmarked
0xc0005446e0 free  unmarked
0xc000544790 free  marked   zombie
0x00c000544790:  0x00c000586120  0x00ce89c0 
0x00c0005447a0:  0x00ce8780  0x00c00015c5a0 
0x00c0005447b0:  0x  0x00ce8960 
0x00c0005447c0:  0x00c00034d4a0  0x 
0x00c0005447d0:  0x  0x 
0x00c0005447e0:  0x  0x00c00043bab0 
0x00c0005447f0:  0x00e6e0a6  0x 
0x00c000544800:  0x  0x00916400 
 
0x00c000544810:  0x00ce8960  0x00c0005447e0 
0x00c000544820:  0x00c000128d10  0x 
0x00c000544830:  0x  0x00c000586120 
0xc000544840 free  marked   zombie
0x00c000544840:  0x  0x 
0x00c000544850:  0x00ccf540  0x00c00034d680 
0x00c000544860:  0x  0x009163c0 
 
0x00c000544870:  0x00c0005447f8  0x00c00015c5a0 
0x00c000544880:  0x00ccf540  0x00c0003ec400 
0x00c000544890:  0x00c0003ec400  0x00ce89c0 
0x00c0005448a0:  0x0001  0x 
0x00c0005448b0:  0x00ce8960  0x 
0x00c0005448c0:  0x  0x 
0x00c0005448d0:  0x  0x00ce89c0 
0x00c0005448e0:  0x00c000544838  0x 
0xc0005448f0 free  unmarked
0xc0005449a0 free  unmarked
0xc000544a50 free  unmarked
0xc000544b00 free  unmarked
0xc000544bb0 free  unmarked
0xc000544c60 free  unmarked
0xc000544d10 free  unmarked
0xc000544dc0 free  unmarked
0xc000544e70 free  unmarked
0xc000544f20 free  unmarked
0xc000544fd0 free  unmarked
0xc000545080 free  unmarked
0xc000545130 free  unmarked
0xc0005451e0 free  unmarked
0xc000545290 free  unmarked
0xc000545340 free  unmarked
0xc0005453f0 free  unmarked
0xc0005454a0 free  unmarked
0xc000545550 free  unmarked
0xc000545600 free  unmarked
0xc0005456b0 free  unmarked
0xc000545760 free  unmarked
0xc000545810 free  unmarked
0xc0005458c0 free  unmarked
0xc000545970 free  unmarked
0xc000545a20 free  unmarked
0xc000545ad0 free  unmarked
0xc000545b80 free  unmarked
0xc000545c30 free  unmarked
0xc000545ce0 free  unmarked
0xc000545d90 free  unmarked
0xc000545e40 free  unmarked
0xc000545ef0 free  unmarked
fatal error: found pointer to free object

runtime stack:
runtime.throw({0xe80d7a?, 0xc0005448f0?})
/usr/lib/go-1.21/src/runtime/panic.go:1077 +0x5c fp=0x7f24eee00b68 
sp=0x7f24eee00b38 pc=0x440a3c
runtime.(*mspan).reportZombies(0x7f24ecbf6c48)
/usr/lib/go-1.21/src/runtime/mgcsweep.go:861 +0x2e5 fp=0x7f24eee00be8 
sp=0x7f24eee00b68 pc=0x42ece5
runtime.(*sweepLocked).sweep(0x2030001?, 0x0)
/usr/lib/go-1.21/src/runtime/mgcsweep.go:644 +0xa88 fp=0x7f24eee00cf0 
sp=0x7f24eee00be8 pc=0x42e508
runtime.(*mcentral).uncacheSpan(0x7f24eee00d68?, 0x436046?)
/usr/lib/go-1.21/src/runtime/mcentral.go:228 +0x98 fp=0x7f24eee00d18 
sp=0x7f24eee00cf0 pc=0x41e918
runtime.(*mcache).releaseAll(0x7f2536158f18)
/usr/lib/go-1.21/src/runtime/mcache.go:291 +0x13c fp=0x7f24eee00d80 
sp=0x7f24eee00d18 pc=0x41e37c
runtime.(*mcache).prepareForSweep(0x7f2536158f18)
/usr/lib/go-1.21/src/runtime/mcache.go:328 +0x35 fp=0x7f24eee00da8 
sp=0x7f24eee00d80 pc=0x41e475
runtime.gcMarkTermination.func4.1(0xc5ef00)
/usr/lib/go-1.21/src/runtime/mgc.go:1115 +0x25 fp=0x7f24eee00dd0 
sp=0x7f24eee00da8 pc=0x46e6e5
runtime.forEachP(0xec7d20)
/usr/lib/go-1.21/src/runtime/proc.go:1787 +0x124 fp=0x7f24eee00e38 
sp=0x7f24eee00dd0 pc=0x4465c4
runtime.gcMarkTermination.func4()
/usr/lib/go-1.21/src/runtime/mgc.go:1114 +0x1a fp=0x7f24eee00e50 
sp=0x7f24eee00e38 pc=0x46e81a
runtime.systemstack()
/usr/lib/go-1.21/src/runtime/asm_amd64.s:509 +0x4a fp=0x7f24eee00e60 
sp=0x7f24eee00e50 pc=0x47614a

goroutine 60 [running]:
runtime.systemstack_switch()
/usr/lib/go-1.21/src/runtime/asm_amd64.s:474 +0x8 fp=0xc66530 
sp=0xc66520 pc=0x4760e8
runtime.gcMarkTermination()
/usr/lib/go-1.21/src/runtime/mgc.go:1113 +0x4b7 fp=0xc666f8 
sp=0xc66530 pc=0x423797
runtime.gcMarkDone()

Bug#1052084: oci-seccomp-bpf-hook: FTBFS: make[1]: *** [debian/rules:18: copyright-scan] Error 255

[Sebastian Ramacher]

Source: oci-seccomp-bpf-hook
Version: 1.2.8+ds-1
Severity: serious
Tags: ftbfs sid trixie
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: sramac...@debian.org

https://buildd.debian.org/status/fetch.php?pkg=oci-seccomp-bpf-hook=amd64=1.2.8%2Bds-1%2Bb7=1694886724=0

   debian/rules execute_before_dh_auto_configure
make[1]: Entering directory '/<>'
scan-copyrights >debian/copyright-scan.new.tmp 
2>debian/copyright-scan.new.todo.tmp
make[1]: *** [debian/rules:18: copyright-scan] Error 255
make[1]: Leaving directory '/<>'
make: *** [debian/rules:7: binary-arch] Error 2

Cheers
-- 
Sebastian Ramacher

Processed: tagging 1010445, tagging 1016957, tagging 1035639, tagging 1035640, tagging 1035694, tagging 1037604

[Debian Bug Tracking System]

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

> tags 1010445 + sid trixie
Bug #1010445 [mono-complete] mono-complete: Mono package in Debian is very 
outdated (6.8 but should be 6.12)
Added tag(s) trixie and sid.
> tags 1016957 + sid trixie
Bug #1016957 [src:kbd-chooser] kbd-chooser: please add support for riscv64
Added tag(s) trixie and sid.
> tags 1035639 + sid trixie
Bug #1035639 {Done: Paul Wise } [src:git-imerge] git-imerge: 
FTBFS with tox 4
Added tag(s) sid and trixie.
> tags 1035640 + sid trixie
Bug #1035640 {Done: Christoph Biedl } 
[src:python-magic] python-magic: FTBFS with tox 4
Added tag(s) trixie and sid.
> tags 1035694 + sid trixie
Bug #1035694 {Done: Stefano Rivera } [src:python-bottle] 
python-bottle: tox 4 support: Build-Depend on python3-wheel
Added tag(s) trixie and sid.
> tags 1037604 + sid trixie
Bug #1037604 {Done: Timothy Pearson } 
[src:chromium] chromium: ftbfs with GCC-13
Added tag(s) trixie and sid.
> thanks
Stopping processing here.

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

Bug#1051116: marked as done (maildrop: depends on libgcc1, which is no longer in the archive)

[Debian Bug Tracking System]

Your message dated Sun, 17 Sep 2023 13:05:16 +0200
with message-id 
and subject line Re: Bug#1051116: maildrop: depends on libgcc1, which is no 
longer in the archive
has caused the Debian Bug report #1051116,
regarding maildrop: depends on libgcc1, which is no longer in the archive
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.)


-- 
1051116: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1051116
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: maildrop
Version: 2.9.3-2+b1
Severity: grave
Justification: renders package unusable

maildrop depends on libgcc1, which is no longer in the archive.
This can be checked on

  https://packages.debian.org/en/bullseye/maildrop

which says:

  dep: libgcc1 (>= 1:3.0) [not armel, armhf, i386, mipsel]
  Package not available

This means that some obsolete packages such as libgcc1 cannot be
removed before the upgrade to bookworm.

-- System Information:
Debian Release: 11.7
  APT prefers oldstable-updates
  APT policy: (500, 'oldstable-updates'), (500, 'oldstable-security'), (500, 
'oldstable-debug'), (500, 'oldstable')
Architecture: amd64 (x86_64)

Kernel: Linux 5.10.0-25-amd64 (SMP w/1 CPU thread)
Locale: LANG=POSIX, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages maildrop depends on:
ii  courier-authlib  0.71.1-2
ii  libc62.31-13+deb11u6
ii  libcourier-unicode4  2.1.2-2
ii  libgcc-s1 [libgcc1]  10.2.1-6
ii  libgcc1  1:8.3.0-6
ii  libgdbm6 1.19-2
ii  libpcre3 2:8.39-13
ii  libstdc++6   10.2.1-6

Versions of packages maildrop recommends:
ii  postfix [mail-transport-agent]  3.5.18-0+deb11u1

maildrop suggests no packages.

-- no debconf information

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)
--- End Message ---
--- Begin Message ---
On 2023-09-03 02:26:55 +0200, Vincent Lefevre wrote:
> Package: maildrop
> Version: 2.9.3-2+b1
> Severity: grave
> Justification: renders package unusable
> 
> maildrop depends on libgcc1, which is no longer in the archive.
> This can be checked on
> 
>   https://packages.debian.org/en/bullseye/maildrop
> 
> which says:
> 
>   dep: libgcc1 (>= 1:3.0) [not armel, armhf, i386, mipsel]
>   Package not available

libgcc1 is provided by libgcc-s1:

$ apt-cache show libgcc-s1
Package: libgcc-s1
Source: gcc-10
Version: 10.2.1-6
Installed-Size: 116
Maintainer: Debian GCC Maintainers 
Architecture: amd64
Replaces: libgcc1 (<< 1:10)
Provides: libgcc1 (= 1:10.2.1-6)
Depends: gcc-10-base (= 10.2.1-6), libc6 (>= 2.14)
Breaks: cryptsetup-initramfs (<< 2:2.2.2-3~)
Description: GCC support library
Description-md5: bbd60d723e97d8e06c04228ee4c76f10
Multi-Arch: same
Homepage: http://gcc.gnu.org/
Important: yes
Protected: yes
Tag: role::shared-lib
Section: libs
Priority: optional
Filename: pool/main/g/gcc-10/libgcc-s1_10.2.1-6_amd64.deb
Size: 41400
MD5sum: 662ac9938f503745221bd777b5a94cab
SHA256: e478f2709d8474165bb664de42e16950c391f30eaa55bc9b3573281d83a29daf

Cheers
-- 
Sebastian Ramacher--- End Message ---

Processed: tagging 1051510

[Debian Bug Tracking System]

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

> tags 1051510 + sid trixie
Bug #1051510 [src:searx] searx: SearX upstream is no longer maintained
Added tag(s) trixie and sid.
> thanks
Stopping processing here.

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

Bug#1050019: Reporting an issue

[Anton Gladky]

forwarded 1050019 https://github.com/google/cctz/issues/274
thanks

Hi, I have reported the issue here [1]

[1] https://github.com/google/cctz/issues/274

Best regards

Anton

Processed: Reporting an issue

[Debian Bug Tracking System]

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

> forwarded 1050019 https://github.com/google/cctz/issues/274
Bug #1050019 [src:cctz] cctz: FTBFS due to time_zone_lookup_test failure
Set Bug forwarded-to-address to 'https://github.com/google/cctz/issues/274'.
> thanks
Stopping processing here.

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

Bug#1037398: marked as done (optgeo: build-depends on transitional package libgdk-pixbuf2.0-dev)

[Debian Bug Tracking System]

Your message dated Sun, 17 Sep 2023 10:13:47 +
with message-id 
and subject line Bug#1037398: fixed in optgeo 2.25-3
has caused the Debian Bug report #1037398,
regarding optgeo: build-depends on transitional package libgdk-pixbuf2.0-dev
to be marked as done.

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

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


-- 
1037398: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037398
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: optgeo
Version: 2.25-2
Severity: important
Tags: trixie sid
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: split-gdk-pixbuf

This package Build-Depends on libgdk-pixbuf2.0-dev.

In Debian 11, libgdk-pixbuf2.0-dev was split into two packages:

- libgdk-pixbuf-2.0-dev contains the supported gdk-pixbuf-2.0 library

- libgdk-pixbuf-xlib-2.0-dev contains the deprecated, unmaintained
  Xlib integration layer, gdk-pixbuf-xlib-2.0

If this package only requires functionality from gdk-pixbuf-2.0.pc
and , please update the build-dependency to
libgdk-pixbuf-2.0-dev.

If it also requires the Xlib integration gdk-pixbuf-xlib-2.0.pc and
 (unlikely), then you can also build-depend on
libgdk-pixbuf-xlib-2.0-dev until the package can be updated to remove
that requirement.

libgdk-pixbuf-2.0-dev was present in both Debian 11 and Debian 12, so
it is not necessary to have a "| libgdk-pixbuf2.0-dev" alternative
dependency, even for packages that are expected to be backported.

We should remove the libgdk-pixbuf2.0-dev transitional package during
the Debian 13 'trixie' cycle, so this bug is likely to become RC later.

Thanks,
smcv
--- End Message ---
--- Begin Message ---
Source: optgeo
Source-Version: 2.25-3
Done: Georges Khaznadar 

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

Debian distribution maintenance software
pp.
Georges Khaznadar  (supplier of updated optgeo 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: Sun, 17 Sep 2023 11:18:42 +0200
Source: optgeo
Architecture: source
Version: 2.25-3
Distribution: unstable
Urgency: medium
Maintainer: Georges Khaznadar 
Changed-By: Georges Khaznadar 
Closes: 1037398
Changes:
 optgeo (2.25-3) unstable; urgency=medium
 .
   * bumped Standards-Version: 4.2.0
   * replaced the build dependency libgdk-pixbuf2.0-dev by
 libgdk-pixbuf-2.0-dev. Closes: #1037398
Checksums-Sha1:
 0c740c742dacfda4d254a74625ec69851f78564c 1919 optgeo_2.25-3.dsc
 9ea1f3e259d47ee2d9c2772d054e5320cb6afe69 9232 optgeo_2.25-3.debian.tar.xz
 61fd74dba9de586d5ec59438f6764c4b87855b22 12322 optgeo_2.25-3_amd64.buildinfo
Checksums-Sha256:
 7db49f08e6d0de19ef99462ed141bd17e7ff6dddb37d7b471230400e9facf122 1919 
optgeo_2.25-3.dsc
 c549a88bd3e6985eb6986a144dfcdeb00331c92e4781d971dbf3987a527af37c 9232 
optgeo_2.25-3.debian.tar.xz
 f35ee9be9670e38ea8e1ea99c531134fbe203155d6b76ba1b79be34a31013e21 12322 
optgeo_2.25-3_amd64.buildinfo
Files:
 bc5e7f2e84c35819e98f807d8b0fed1b 1919 science extra optgeo_2.25-3.dsc
 6508d24c3e1a6bbb9c574190e534c70a 9232 science extra optgeo_2.25-3.debian.tar.xz
 a3a2e4dd94a5a3a22b821fbba4143c6b 12322 science extra 
optgeo_2.25-3_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEM0CzZP9nFT+3zK6FHCgWkHE2rjkFAmUGxdkACgkQHCgWkHE2
rjlZJw//R6V/IgR5TMP2A/eW5AXsX5+pwFYAavggOqrAISTk2ZmonSYjGbpy0i77
bg+Ct/1ifkOcKz9/P6LT2lVXwuliHrlObZKsZ20Ow26K8ksjcVml0jHmM1RhntsO
LP6u+FPzOaluckhjdc8QH9DZHhBG/N1HaX7jIXDIa6YG6g8MwJg1Xh8nJ0yEKf+E
CeHHCex5Nqt7xSYSaH31HNcUZjNp2vQquKSd92fv5cC2MiMKDmEoo3vbzsiOCOuQ
ZmjLmH6fGC3el1uKxO32b913jMUCiwGy7ZPhiOmyJLMhoup6W2YQAilOjAcZz+7I
j8jWPn0VJkrcSyQsLJfA+jy+wDH5OsY7Vwswt1amtR1P0qkYu+xUyxwzO4WNCIKv
0Gqrb0NMRNC/v3d7ojUZJkmoEXft3LMtZ7fFpy3r/SXLYfx+s3M474dCflJwuYT4
YMKMn2BGLQLiV14W1RybYOOyE3YCodvZ8oxjfgDhRYSRAJhcpR+JgW044N9EbBrd
lg1pKM/MjdNrE6Kj3LbGDv7RFDjXDkur1ipnOBfot3zi7LwsNXYjqGmPLc2thJPq
auUox/RdATa6W/DO64RAQJ/dB8GWVWjmXiDx78Ukv9ABhzNsZY0kaSHOrorXO6DM
2B3miw5ci47liKOh86NZO6ChrhoXoLLNhaFJP6sidFgws2kg6cc=
=Ydfw
-END PGP SIGNATURE End Message ---

Bug#1037368: marked as done (dozzaqueux: build-depends on transitional package libgdk-pixbuf2.0-dev)

[Debian Bug Tracking System]

Your message dated Sun, 17 Sep 2023 09:34:47 +
with message-id 
and subject line Bug#1037368: fixed in dozzaqueux 3.51-3
has caused the Debian Bug report #1037368,
regarding dozzaqueux: build-depends on transitional package libgdk-pixbuf2.0-dev
to be marked as done.

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

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


-- 
1037368: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037368
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: dozzaqueux
Version: 3.51-2.1
Severity: important
Tags: trixie sid
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: split-gdk-pixbuf

This package Build-Depends on libgdk-pixbuf2.0-dev.

In Debian 11, libgdk-pixbuf2.0-dev was split into two packages:

- libgdk-pixbuf-2.0-dev contains the supported gdk-pixbuf-2.0 library

- libgdk-pixbuf-xlib-2.0-dev contains the deprecated, unmaintained
  Xlib integration layer, gdk-pixbuf-xlib-2.0

If this package only requires functionality from gdk-pixbuf-2.0.pc
and , please update the build-dependency to
libgdk-pixbuf-2.0-dev.

If it also requires the Xlib integration gdk-pixbuf-xlib-2.0.pc and
 (unlikely), then you can also build-depend on
libgdk-pixbuf-xlib-2.0-dev until the package can be updated to remove
that requirement.

libgdk-pixbuf-2.0-dev was present in both Debian 11 and Debian 12, so
it is not necessary to have a "| libgdk-pixbuf2.0-dev" alternative
dependency, even for packages that are expected to be backported.

We should remove the libgdk-pixbuf2.0-dev transitional package during
the Debian 13 'trixie' cycle, so this bug is likely to become RC later.

Thanks,
smcv
--- End Message ---
--- Begin Message ---
Source: dozzaqueux
Source-Version: 3.51-3
Done: Georges Khaznadar 

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

Debian distribution maintenance software
pp.
Georges Khaznadar  (supplier of updated dozzaqueux 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: Sun, 17 Sep 2023 11:02:16 +0200
Source: dozzaqueux
Architecture: source
Version: 3.51-3
Distribution: unstable
Urgency: medium
Maintainer: Georges Khaznadar 
Changed-By: Georges Khaznadar 
Closes: 1037368
Changes:
 dozzaqueux (3.51-3) unstable; urgency=medium
 .
   * added a logo for salsa.debian.org
   * added VCS stuff
   * bumped Standards-Version: 4.6.2, debhelper-compat (= 13)
   * replaced the build-dependency on libgdk-pixbuf2.0-dev by
 libgdk-pixbuf-2.0-dev. Closes: #1037368
Checksums-Sha1:
 71fe75fda17cfec13ddd7fdc8f1b8812f6b5e94e 2149 dozzaqueux_3.51-3.dsc
 02bd60f3e9aa54fa5a59723b995781262f6162a8 16664 dozzaqueux_3.51-3.debian.tar.xz
 b1873b865026ca3ce4903f4f26332c59df179edf 12664 
dozzaqueux_3.51-3_amd64.buildinfo
Checksums-Sha256:
 dd19705c233cfdde1064ff538cd15e25577f75b6c0943678e365d6c5d3d688d1 2149 
dozzaqueux_3.51-3.dsc
 5eea10cf67991ab37ffef6453e7c3641a901d9fac5d448d015b9ad6e311974d8 16664 
dozzaqueux_3.51-3.debian.tar.xz
 c1b2514b833f90873b6aa67417f6c6fb241af14a6f8a12c3417d32d97c4d4373 12664 
dozzaqueux_3.51-3_amd64.buildinfo
Files:
 c23ec6f47987ae63f3a2dae3ab8ab01e 2149 science extra dozzaqueux_3.51-3.dsc
 a399a2cdf7c5253d2970ece85b3329c6 16664 science extra 
dozzaqueux_3.51-3.debian.tar.xz
 d68a538c06d2d497eb20245acb1a5b81 12664 science extra 
dozzaqueux_3.51-3_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEM0CzZP9nFT+3zK6FHCgWkHE2rjkFAmUGwqQACgkQHCgWkHE2
rjk2Yg/+L5ZGCnBzsJ6AbEeGH3fkaoVBLLAvQ5WN3++Mr5bZifWWkO2ghd+Z4quJ
c8ZSRKto857uu+r70MDLb3VifjDKmfKs4aO2zl94uruO1pGSJfrTW1a6qyeO/2oo
2zC+m3GDLauzoOLnmC/e/6EuJLC4FU7oMp6UrS7KcJsJPcdCeBIT0n4Udo1TCc72
z47+caG45OKXD0OMR7VvomyzqNmtSCNqQalJqdyStFd4A8tgRFCwDhhEd/UdH2K0
vzHARpFzAfk9fTaeLS1Uxvb/a2k2d/V+MlSqwTGst+SLlFm6ZP1FUyy8QwUL2S4l
45laZLJ2aXHh0WwyWJ+syZ84zfog7WYIBxc1QsTgO+HdJKKvpnLv9U+y5IH/S3yO
ehb7APsH3fq3XaFckxAsPl6SsOtA71CM4hpCumTlykWoH8p2o4mtWr8/1b4LxQst
wkv86CRowvLmQR+iLf/E8OrvYZbHj5G/4l+3l/FsJ0jnrTYSMAo2XW355LwcIPZy
aMx7xF8S+dNaJsyAHO/bVqfvdRgS9xCbrP4/QoKkOw4Dcj0IfKTAp1TsRY0CKpWr
AzVwPl0nV8kHUgCiJ/KAsrWveVqji0/jfH42r/ei9VncZ1KQmv8XXyw9fXKKzRuH

Bug#1052080: golango-ginkgo: ginkgo now provided by golang-github-onsi-ginkgo-v2

[Sebastian Ramacher]

Source: golang-ginkgo
Version: 1.16.5-3
Severity: serious
Tags: ftbfs sid trixie
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: sramac...@debian.org

The ginkgo binary package has been taken over by
golang-github-onsi-ginkgo-v2. Hence, golang-ginko can no longer be built
on buildds (uploads are rejected since they would be violating version
constraints).

Cheers
-- 
Sebastian Ramacher

Bug#1052034: procps: FTBFS on amd64, i386: # of unexpected failures 1

[Craig Small]

Looks like another "guess what strange thing the buildd is doing this time"
problem.
The failing test is (effectively)
pmap -XX $pid $pid | grep KB

And make sure the first numbers of each row are the same. Because it is the
same process, it should be the same.
There is the same test for pmap -X and that passed.

The test works every time I have tried, on any system I have tried, so the
buildd is doing something odd, but without anything else to go on that's
going to be impossible to fix.
I'm going to adjust the error messages to see which match is failing, but
that's only in the upstream package at the moment.

 - Craig


On Sat, 16 Sept 2023 at 20:57, Sebastian Ramacher 
wrote:

> Source: procps
> Version: 2:4.0.4-1
> Severity: serious
> Tags: ftbfs
> Justification: fails to build from source (but built successfully in the
> past)
> X-Debbugs-Cc: sramac...@debian.org
>
>
> https://buildd.debian.org/status/fetch.php?pkg=procps=amd64=2%3A4.0.4-1=1694089907=0
>
> WARNING: Couldn't find tool init file
> Test run by buildd on Thu Sep  7 12:31:32 2023
> Native configuration is x86_64-pc-linux-gnu
>
> === pmap tests ===
>
> Schedule of variations:
> unix
>
> Running target unix
> Using /usr/share/dejagnu/baseboards/unix.exp as board description file for
> target.
> Using /usr/share/dejagnu/config/unix.exp as generic interface file for
> target.
> Using /<>/testsuite/config/unix.exp as
> tool-and-target-specific interface file.
> Running /<>/testsuite/pmap.test/pmap.exp ...
> FAIL: pmap XX pid pid has same total
>
> === pmap Summary ===
>
> # of expected passes13
> # of unexpected failures1
> /<>/src/pmap version 4.0.4
>
> WARNING: Couldn't find tool init file
> Test run by buildd on Thu Sep  7 12:31:32 2023
> Native configuration is x86_64-pc-linux-gnu
>
>
> Cheers
> --
> Sebastian Ramacher
>

Bug#1052078: smifb2-dkms: module does not build for kernels w/o DRM or I2C

[Andreas Beckmann]

Package: smifb2-dkms
Version: 2.2.3.4.g1828e79-1
Severity: serious

Hi,

the smifb2 module does not build for the -cloud kernel due to missing
I2C symbols and does not build for the armel and s390x kernels due to
missign DRM symbols.

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

Probably all that is needed is to add 

BUILD_EXCLUSIVE_CONFIG="CONFIG_DRM CONFIG_I2C"

to debian/smifb2-dkms.dkms in order to skip building the module for
kernels that don't have these config options enabled.

On arm64 the issue is a bit more involved, since there is an
incompatible redefinition of the macro FIELD_GET:

https://ci.debian.net/data/autopkgtest/testing/arm64/s/smifb2/36811223/log.gz

 84s   CC [M]  /var/lib/dkms/smifb2/2.2.3.4.g1828e79/build/ddk750/ddk750_chip.o
 84s In file included from 
/usr/src/linux-headers-6.4.0-2-common/arch/arm64/include/asm/mte.h:13,
 84s  from 
/usr/src/linux-headers-6.4.0-2-common/arch/arm64/include/asm/pgtable.h:12,
 84s  from 
/usr/src/linux-headers-6.4.0-2-common/include/linux/pgtable.h:6,
 84s  from 
/usr/src/linux-headers-6.4.0-2-common/arch/arm64/include/asm/io.h:12,
 84s  from 
/usr/src/linux-headers-6.4.0-2-common/include/linux/io.h:13,
 84s  from 
/var/lib/dkms/smifb2/2.2.3.4.g1828e79/build/ddk750/ddk750_help.h:7,
 84s  from 
/var/lib/dkms/smifb2/2.2.3.4.g1828e79/build/ddk750/ddk750_chip.c:7:
 84s /usr/src/linux-headers-6.4.0-2-common/include/linux/bitfield.h:152: 
warning: "FIELD_GET" redefined
 84s   152 | #define FIELD_GET(_mask, _reg) 
 \
 84s   |
 84s In file included from 
/var/lib/dkms/smifb2/2.2.3.4.g1828e79/build/ddk750/ddk750_chip.c:1:
 84s /var/lib/dkms/smifb2/2.2.3.4.g1828e79/build/ddk750/ddk750_defs.h:19: note: 
this is the location of the previous definition
 84s19 | #define FIELD_GET(x, reg, field) \
 84s   |
 84s /var/lib/dkms/smifb2/2.2.3.4.g1828e79/build/ddk750/ddk750_chip.c: In 
function ‘ddk750_getFrameBufSize’:
 84s /var/lib/dkms/smifb2/2.2.3.4.g1828e79/build/ddk750/ddk750_chip.c:45:86: 
error: macro "FIELD_GET" passed 3 arguments, but takes just 2
 84s45 | sizeSymbol = FIELD_GET(peekRegisterDWord(MISC_CTRL), 
MISC_CTRL, LOCALMEM_SIZE);
 84s   |
  ^
 84s /usr/src/linux-headers-6.4.0-2-common/include/linux/bitfield.h:152: note: 
macro "FIELD_GET" defined here
 84s   152 | #define FIELD_GET(_mask, _reg) 
 \
 84s   |
 84s /var/lib/dkms/smifb2/2.2.3.4.g1828e79/build/ddk750/ddk750_chip.c:45:22: 
error: ‘FIELD_GET’ undeclared (first use in this function); did you mean 
‘FOLL_GET’?
 84s45 | sizeSymbol = FIELD_GET(peekRegisterDWord(MISC_CTRL), 
MISC_CTRL, LOCALMEM_SIZE);
 84s   |  ^
 84s   |  FOLL_GET
 84s /var/lib/dkms/smifb2/2.2.3.4.g1828e79/build/ddk750/ddk750_chip.c:45:22: 
note: each undeclared identifier is reported only once for each function it 
appears in


Andreas

PS: the git repository is not yet populated