Bug#1051819: marked as done (fluidsynth: Consider building with pipewire support)

[Debian Bug Tracking System]

Your message dated Fri, 15 Sep 2023 06:49:00 +
with message-id 
and subject line Bug#1051819: fixed in fluidsynth 2.3.3-2.1
has caused the Debian Bug report #1051819,
regarding fluidsynth: Consider building with pipewire support
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.)


-- 
1051819: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1051819
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: fluidsynth
Version: 2.3.1-2
Severity: wishlist

Dear Maintainer,

Please consider building fluidsynth with pipewire support.
While it is working adequately via the pulseaudio compatibility layer,
it would be nice to utilize the native support added in 2.3.0 as it is
the default sound server in Debian 12.

It looks like all that is needed is a Build-Depends on libpipewire-0.3-dev
to have cmake pick up on it.

-- System Information:
Debian Release: 12.1
  APT prefers stable-security
  APT policy: (500, 'stable-security'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

Versions of packages fluidsynth depends on:
ii  init-system-helpers  1.65.2
ii  libc62.36-9+deb12u1
ii  libfluidsynth3   2.3.1-2
ii  libglib2.0-0 2.74.6-2
ii  libsdl2-2.0-02.26.5+dfsg-1
ii  libsystemd0  252.12-1~deb12u1

Versions of packages fluidsynth recommends:
ii  qsynth  0.9.9-1

fluidsynth suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: fluidsynth
Source-Version: 2.3.3-2.1
Done: Gianfranco Costamagna 

We believe that the bug you reported is fixed in the latest version of
fluidsynth, 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.
Gianfranco Costamagna  (supplier of updated 
fluidsynth 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 07:22:04 +0200
Source: fluidsynth
Built-For-Profiles: noudeb
Architecture: source
Version: 2.3.3-2.1
Distribution: unstable
Urgency: medium
Maintainer: Debian Multimedia Maintainers 
Changed-By: Gianfranco Costamagna 
Closes: 1051819
Changes:
 fluidsynth (2.3.3-2.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Fixup previous upload, also runtime depend on libpipewire-0.3-dev,
 on libfluidsynth-dev (Closes: #1051819)
Checksums-Sha1:
 eb96ebda40226ee0598403b69126a46a749729ea 2545 fluidsynth_2.3.3-2.1.dsc
 bf0198870f06f540b60b9e4039267bc0e183c425 19724 
fluidsynth_2.3.3-2.1.debian.tar.xz
 49cd3c51107b55c056668cc83cfd02a456132d0e 14375 
fluidsynth_2.3.3-2.1_source.buildinfo
Checksums-Sha256:
 43b1afb3a418f7223fa91b110074545429f59ea8c5f0c872d0768722206a7da7 2545 
fluidsynth_2.3.3-2.1.dsc
 1fe1bb371ef8f4d32a30a2d4ea95fe6f0f7750ee83d917066e91fe546f59b747 19724 
fluidsynth_2.3.3-2.1.debian.tar.xz
 86ee96f279d66c1b56fd8b3e654d82f95424e4ac119f334d5ac24ef509d65a6d 14375 
fluidsynth_2.3.3-2.1_source.buildinfo
Files:
 afbc9303a33a40ba3f685659891af5d8 2545 sound optional fluidsynth_2.3.3-2.1.dsc
 ba6637e07ba0e0fe2a3501d9e81ca501 19724 sound optional 
fluidsynth_2.3.3-2.1.debian.tar.xz
 dcd45afd87a73e7b0cd899cbe9bfd77e 14375 sound optional 
fluidsynth_2.3.3-2.1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEkpeKbhleSSGCX3/w808JdE6fXdkFAmUD+KAACgkQ808JdE6f
XdmInw/9FQKuOc7GZI8stfqgcNsI9dYT9Fx9BUkGqVIyI58WXKCg3xo3FBtrTNSq
AlkfrQy+TR0/CpKzvMb2HVYty41k5dfXZckr+oWn5wbq+Y35MS4dCq5bxW9VbSjS
sJkhzshC5amx/kpfsRjhqca8BJn2S3p0BnHDgW/A4IVn9gwK7en+RI75GcRubsjO
mcStR9f4PbOhRJ+k8yGHpF5FCOmBQcP5KGnr5d+LDvNfSrSFpsP3LfNvF+v/aT43
lxrk1sRRUeoy2IiLCVFdxuTgWaz4L/NHcThCNrM/Vqu/EjHfFdHg/BwK0/+gIrMP
Ul2Yf6EIW9hEhq32zdgimZJ56aCRpwh78ydgoO1zZpV1HEOuEAcGjDWLYSnt3WqY
YD3JGjsz5XjhLiL6n4+LW1INcwiJsrDf97aa03LCuxCVlABvbREa8x4EGzMVuAKc
UawUzInYRtDLvl8PqANK1spQxG3pVVDcw+a5krd7sCSg6m1FWE+smkPK6emEuCKw
mDBW9VDJJW4zB4ZjLBkU6futlqsTGs4ZKtOvCssDGRUHh+5TDFUFjJW7KBoYJluG
TwPvsTU0tkyZKn2ok

Bug#1035043: alex4-data: please request assets be explictly licensed

[Alexandre Detiste]

Hi,

> [Phil Morrell ]
> I have no personal incentive to follow up.

I understand

It's disappointing, but we'll need to move on.

This game is now in the same situation as opentyrian...

The assets can be made packageable with data-game-data-packager
and alex4 engine will have to be moved to contrib.

Greets

> alex4 is marked for autoremoval from testing

> Hi there,
>
> glad to hear you like the game!
> The license only applies to the source code.
>
> Johan

Processed: Re: fluidsynth: Consider building with pipewire support

[Debian Bug Tracking System]

Processing control commands:

> tags 1051819 + patch
Bug #1051819 [fluidsynth] fluidsynth: Consider building with pipewire support
Ignoring request to alter tags of bug #1051819 to the same tags previously set
> tags 1051819 + pending
Bug #1051819 [fluidsynth] fluidsynth: Consider building with pipewire support
Added tag(s) pending.

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

Bug#1051819: fluidsynth: Consider building with pipewire support

[Gianfranco Costamagna]

Control: tags 1051819 + patch
Control: tags 1051819 + pending

Dear maintainer,

I've prepared an NMU for fluidsynth (versioned as 2.3.3-2.1) and
uploaded it.

Regards.

diff -Nru fluidsynth-2.3.3/debian/changelog fluidsynth-2.3.3/debian/changelog
--- fluidsynth-2.3.3/debian/changelog   2023-09-13 02:52:50.0 +0200
+++ fluidsynth-2.3.3/debian/changelog   2023-09-14 07:22:04.0 +0200
@@ -1,3 +1,11 @@
+fluidsynth (2.3.3-2.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Fixup previous upload, also runtime depend on libpipewire-0.3-dev,
+on libfluidsynth-dev (Closes: #1051819)
+
+ -- Gianfranco Costamagna   Thu, 14 Sep 2023 
07:22:04 +0200
+
 fluidsynth (2.3.3-2) unstable; urgency=medium

   * Team upload.
diff -Nru fluidsynth-2.3.3/debian/control fluidsynth-2.3.3/debian/control
--- fluidsynth-2.3.3/debian/control 2023-09-13 02:52:50.0 +0200
+++ fluidsynth-2.3.3/debian/control 2023-09-14 07:22:04.0 +0200
@@ -82,6 +82,7 @@
  libdbus-1-dev [linux-any],
  libinstpatch-dev (>= 1.1.0),
  libjack-dev | libjack-jackd2-dev,
+ libpipewire-0.3-dev,
  libpulse-dev,
  libreadline-dev,
  libsdl2-dev,


OpenPGP_signature
Description: OpenPGP digital signature

Processed (with 1 error): Re: ldap-account-manager: Multiple embeded and minified javascript library

[Debian Bug Tracking System]

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

> tags 1042528 - FTBFS
Unknown tag/s: FTBFS.
Recognized are: patch wontfix moreinfo unreproducible help security upstream 
pending confirmed ipv6 lfs d-i l10n newcomer a11y ftbfs fixed-upstream fixed 
fixed-in-experimental sid experimental potato woody sarge sarge-ignore etch 
etch-ignore lenny lenny-ignore squeeze squeeze-ignore wheezy wheezy-ignore 
jessie jessie-ignore stretch stretch-ignore buster buster-ignore bullseye 
bullseye-ignore bookworm bookworm-ignore trixie trixie-ignore forky 
forky-ignore.

Bug #1042528 [src:ldap-account-manager] ldap-account-manager: Multiple embeded 
and minified javascript library
Requested to remove no tags; doing nothing.
> thanks
Stopping processing here.

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

Processed: Re: Bug#1051752 closed by Debian FTP Masters (reply to Jonas Smedegaard ) (Bug#1051752: fixed in uwsgi 2.0.22-2)

[Debian Bug Tracking System]

Processing control commands:

> reopen -1
Bug #1051752 {Done: Jonas Smedegaard } [src:uwsgi] uwsgi: remove 
uwsgi-plugin-glusterfs on 32 bit architectures
'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 uwsgi/2.0.22-2.

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

Bug#1051752: closed by Debian FTP Masters (reply to Jonas Smedegaard ) (Bug#1051752: fixed in uwsgi 2.0.22-2)

[Sebastian Ramacher]

Control: reopen -1

On 2023-09-13 21:48:07 +, Debian Bug Tracking System wrote:
> This is an automatic notification regarding your Bug report
> which was filed against the src:uwsgi package:
> 
> #1051752: uwsgi: remove uwsgi-plugin-glusterfs on 32 bit architectures

Reopening as a fix for this bug also requires the removal of
libglusterfs-dev from Build-Depends:

https://buildd.debian.org/status/package.php?p=uwsgi

Dependency installability problem for uwsgi on armel:

uwsgi build-depends on missing:
- libglusterfs-dev:armel

Dependency installability problem for uwsgi on armhf:

uwsgi build-depends on missing:
- libglusterfs-dev:armhf

Dependency installability problem for uwsgi on i386:

uwsgi build-depends on missing:
- libglusterfs-dev:i386

Cheers
-- 
Sebastian Ramacher

Processed: Re: Bug#1051972: jami-daemon: Fails to start with libopendht2 2.6.0.4-1

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 libopendht2 2.6.0.4-1
Bug #1051972 [jami-daemon] jami-daemon: Fails to start with libopendht2 
2.6.0.4-1
Bug reassigned from package 'jami-daemon' to 'libopendht2'.
No longer marked as found in versions ring/20230206.0~ds2-1.3.
Ignoring request to alter fixed versions of bug #1051972 to the same values 
previously set
Bug #1051972 [libopendht2] jami-daemon: Fails to start with libopendht2 
2.6.0.4-1
Marked as found in versions opendht/2.6.0.4-1.
> retitle -1 libopendht2: broke ABI without SONAME bump
Bug #1051972 [libopendht2] jami-daemon: Fails to start with libopendht2 
2.6.0.4-1
Changed Bug title to 'libopendht2: broke ABI without SONAME bump' from 
'jami-daemon: Fails to start with libopendht2 2.6.0.4-1'.
> affects -1 jami-daemon
Bug #1051972 [libopendht2] libopendht2: broke ABI without SONAME bump
Added indication that 1051972 affects jami-daemon

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

Bug#1051972: jami-daemon: Fails to start with libopendht2 2.6.0.4-1

[Sebastian Ramacher]

Control: reassign -1 libopendht2 2.6.0.4-1
Control: retitle -1 libopendht2: broke ABI without SONAME bump
Control: affects -1 jami-daemon

On 2023-09-15 03:07:58 +, Asher Gordon wrote:
> Package: jami-daemon
> Version: 20230206.0~ds2-1.3
> Severity: grave
> X-Debbugs-Cc: none, Asher Gordon 
> 
> Dear Maintainer,
> 
> After upgrading libopendht2, jami-daemon fails to start, making Jami
> unusable. Downgrading libopendht2 fixes the problem.
> 
> $ apt-cache policy libopendht2 | grep Installed:
>   Installed: 2.6.0.4-1
> $ jami
> Using Qt runtime version: 6.4.2
> "notify server name: dunst, vendor: knopwob, version: 1.9.2 (2023-04-20), 
> spec: 1.2"
> "Using locale: en_US"
> "Error : jamid is not available, make sure it is running"
> terminate called after throwing an instance of 'char const*'
> Aborted
> $ /usr/libexec/jamid 
> /usr/libexec/jamid: symbol lookup error: /usr/libexec/jamid: undefined 
> symbol: 
> _ZN3dht4http8ResolverC1ERN4asio10io_contextERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt10shared_ptrINS_6LoggerEE

So libopendht2 broke its ABI without a transition. This needs to be
fixed in opendht.

Cheers

> 
> Downgrading:
> 
> $ sudo sed -i~ s/trixie/bookworm/g /etc/apt/sources.list
> $ sudo apt-get update
> Get:1 tor+https://deb.debian.org/debian bookworm InRelease [151 kB]
> [...]
> Fetched 88.2 MB in 42s (2,120 kB/s)
> Reading package lists... Done
> $ sudo apt-get install libopendht2=2.4.12-7
> Reading package lists... Done
> Building dependency tree... Done
> Reading state information... Done
> The following packages will be DOWNGRADED:
>   libopendht2
> 0 upgraded, 0 newly installed, 1 downgraded, 0 to remove and 0 not 
> upgraded.
> Need to get 806 kB of archives.
> After this operation, 377 kB disk space will be freed.
> Do you want to continue? [Y/n] y
> Get:1 tor+https://deb.debian.org/debian bookworm/main amd64 libopendht2 
> amd64 2.4.12-7 [806 kB]
> Fetched 806 kB in 2s (335 kB/s)
> debconf: unable to initialize frontend: Dialog
> debconf: (Dialog frontend will not work on a dumb terminal, an emacs 
> shell buffer, or without a controlling terminal.)
> debconf: falling back to frontend: Readline
> dpkg: warning: downgrading libopendht2:amd64 from 2.6.0.4-1 to 2.4.12-7
> (Reading database ... 586843 files and directories currently installed.)
> Preparing to unpack .../libopendht2_2.4.12-7_amd64.deb ...
> Unpacking libopendht2:amd64 (2.4.12-7) over (2.6.0.4-1) ...
> Setting up libopendht2:amd64 (2.4.12-7) ...
> Processing triggers for libc-bin (2.37-8) ...
> $ apt-cache policy libopendht2 | grep Installed:
>   Installed: 2.4.12-7
> $ jami
> Using Qt runtime version: 6.4.2
> "notify server name: dunst, vendor: knopwob, version: 1.9.2 (2023-04-20), 
> spec: 1.2"
> "Using locale: en_US"
> No migration required
> [...]
> $ /usr/libexec/jamid 
> Jami Daemon 13.7.0, by Savoir-faire Linux Inc. 2004-2023
> https://jami.net/
> [Video support enabled]
> [Plugins support enabled]
> 
> 22:56:59.121 os_core_unix.c !pjlib 2.12.1 for POSIX initialized
>   C-c C-cCaught signal Interrupt, terminating...
> 
> Jami runs as expected.
> 
> It looks like jamid references an undefined symbol,
> _ZN3dht4http8ResolverC1ERN4asio10io_contextERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt10shared_ptrINS_6LoggerEE,
> which is likely present in the old version of libopendht2. I don't know
> a whole lot about C++ and name mangling, but I would guess that Jami had
> been using a deprecated or undocumented symbol, which has been removed
> or renamed in libopendht2. It's also possible that the new libopendht2
> was compiled with a newer compiler, which mangled the name differently,
> but as far as I know, name mangling is supposed to be fairly stable
> (again, I don't know a whole lot about this).
> 
> Also, the name unmangled:
> 
> $ echo 
> _ZN3dht4http8ResolverC1ERN4asio10io_contextERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt10shared_ptrINS_6LoggerEE
>  | c++filt
> dht::http::Resolver::Resolver(asio::io_context&, 
> std::__cxx11::basic_string, std::allocator 
> > const&, std::shared_ptr)
> 
> Thanks,
> Asher
> 
> -- System Information:
> Debian Release: trixie/sid
>   APT prefers testing-debug
>   APT policy: (500, 'testing-debug'), (500, 'testing')
> Architecture: amd64 (x86_64)
> 
> Kernel: Linux 6.4.0-4-amd64 (SMP w/12 CPU threads; PREEMPT)
> Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
> Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not 
> set
> Shell: /bin/sh linked to /usr/bin/dash
> Init: systemd (via /run/systemd/system)
> LSM: AppArmor: enabled
> 
> Versions of packages jami-daemon depends on:
> ii  libarchive13 3.6.2-1
> ii  libasound2   1.2.9-2
> ii  libavcodec60   

Bug#1051870: marked as done (libpmix2: broken library symlink)

[Debian Bug Tracking System]

Your message dated Fri, 15 Sep 2023 05:37:02 +
with message-id 
and subject line Bug#1051870: fixed in pmix 5.0.1-2
has caused the Debian Bug report #1051870,
regarding libpmix2: broken library symlink
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.)


-- 
1051870: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1051870
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libpmix2
Version: 5.0.1-1
Severity: grave
Justification: renders package unusable

Dear maintainer,

Starting with version 5.0.1-1, the libpmix2 package ships a dead symlink
for /usr/lib//libpmix.so.2. For instance:

$ dpkg -c libpmix2_5.0.1-1_amd64.deb  | grep libpmix.so
-rw-r--r-- root/root   2184040 2023-08-08 10:50 
./usr/lib/x86_64-linux-gnu/pmix2/lib/libpmix.so.2.13.1
lrwxrwxrwx root/root 0 2023-08-08 10:50 
./usr/lib/x86_64-linux-gnu/libpmix.so.2 -> pmix2/lib/libpmix.so.2.13.0
lrwxrwxrwx root/root 0 2023-08-08 10:50 
./usr/lib/x86_64-linux-gnu/libpmix.so.2.13.0 -> pmix2/lib/libpmix.so.2.13.0
lrwxrwxrwx root/root 0 2023-08-08 10:50 
./usr/lib/x86_64-linux-gnu/pmix2/lib/libpmix.so.2 -> libpmix.so.2.13.1

This breaks libraries depending on it and causes packages to FTBFS.

Regards
Aurelien
--- End Message ---
--- Begin Message ---
Source: pmix
Source-Version: 5.0.1-2
Done: Alastair McKinstry 

We believe that the bug you reported is fixed in the latest version of
pmix, 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.
Alastair McKinstry  (supplier of updated pmix 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 16:32:00 +0100
Source: pmix
Architecture: source
Version: 5.0.1-2
Distribution: unstable
Urgency: medium
Maintainer: Alastair McKinstry 
Changed-By: Alastair McKinstry 
Closes: 1049253 1051870
Changes:
 pmix (5.0.1-2) unstable; urgency=medium
 .
   * Broken symlink: soname is 2.13.1 now. Closes: #1051870
   * Enable build-twice (delete autogenerated files).
 Closes: #1049253
Checksums-Sha1:
 3ce1727e5eb63fb24a268ac999262ea318ac83e6 2375 pmix_5.0.1-2.dsc
 a49ea749311cd2c19eb5a8d68ae6196f2b7b0748 11712 pmix_5.0.1-2.debian.tar.xz
Checksums-Sha256:
 2bb94de65778dfb35a2639aac661df01f84773573c1fb6a0dfc8d11b3a875739 2375 
pmix_5.0.1-2.dsc
 716f9656b392ce0e5b2dd274d4d77a52a311e52ccf01e86dbe49b55542d18995 11712 
pmix_5.0.1-2.debian.tar.xz
Files:
 54e9b627d882e60d5cb086137fe7adf9 2375 net optional pmix_5.0.1-2.dsc
 357a97dea08cb7fe7ea3d7cf0169ec7c 11712 net optional pmix_5.0.1-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEgjg86RZbNHx4cIGiy+a7Tl2a06UFAmUD6cgACgkQy+a7Tl2a
06XClg//Wi9Dxp2gc32sDr7ikekFMdqbArl1FaG+tHfIGRlSCp4tnyJW3DshwNaZ
T7EN01ZLq+gpjETHpQV6yh+jlbwmMAjPry3f2kvSiG5oFH3e3S4adVerxskcGRa8
nHZ107BhZPvluKiUjdw+zfqo/B3htfI/65KIGVZvU5nTwbQnQq8DvWP3Awl1kS1w
HHzcHWqioYn/DV+QywrzfVq5C4zxnulOSmxAzGx7NnsVUXq5z2viqiAJiPOmeiJE
KsgXESq8BCbHC01V1VD1mu6Sx7rKAhbcor54Bpq7BlQygZwNot3P6zJhe1TlBv52
qKvD689gubyfJLrfdxz3aNZ6ehLXMXzipGWNMywJ/jP8q0mgYEVSqIakrin+rnzJ
Jnq+//m7Tjt57BbE3vK0Thtq2nD3tTbxS/kdcVDwsqsllLy02c/mgoVrvP3TE7wq
xX79oZhWEyy2Ks8s22Lfmldbxs7oG0UNHan073HhoJcKvMTS/g19Rs+5VaK0eczh
1H53p9fXiooGbJCJ8/+xc7NCmctGm6TMq4D6tDRb7VgRnfz7NxOIvCLfHfE1uxFo
WkHb7YhQbr9vQbQo6dZe4n66Qd8Egj/YKtkS8RlrU2mLzzDjXs1kZ3o1N4XHZKSE
dAAYx6PvT75xUHYm2hGyaMc4LH/bjl7iSVEQB3r+zmcOnEHriIE=
=iz8l
-END PGP SIGNATURE End Message ---

Bug#1050676: enblend-enfuse: FTBFS: dot: maze.c:311: chkSgraph: Assertion `np->cells[0]' failed.

[GCS]

Hi Andreas,

On Sun, Sep 10, 2023 at 9:21 PM Andreas Metzler  wrote:
> I tried to do a test build of enblend against graphviz 8.1.0 from
> experimental. I had no luck, since dot seems to be built without support
> for png output:
 Please try graphviz 9.0.0 from experimental.

> /usr/bin/m4 --fatal-warnings --prefix-builtins --synclines 
> --define='dot_output_type=png' ../../doc/uml-dot.m4 
> ../../doc/external-mask-workflow.dot | \
> /usr/bin/dot  -Tpng -Gbgcolor=transparent -Gresolution=600 | \
> /usr/bin/convert png:- -transparent white -resize $(( ((96 * 
> 1000) / 600) / 10 ))% external-mask-workflow.png
> Format: "png" not recognized. Use one of: canon cmap cmapx cmapx_np dot 
> dot_json eps fig gv imap imap_np ismap json json0 mp pic plain plain-ext pov 
> ps ps2 svg svgz tk xdot xdot1.2 xdot1.4 xdot_json
> convert: improper image header 
> `/dev/shm/magick-u_9y0p39jcrUpQwvjHcDxiLBtxK8jlEu' @ 
> error/png.c/ReadPNGImage/4107.
 There's still a font issue, you will get something like:
fontconfig: Didn't find expected font family. Perhaps URW Type 1 fonts
need installing?

I don't know why this is happening, as if I check the intermediate dot
file then only the node font settings cause this error. Other uses of
the Helvetica font are fine. As per source change, you will need this
patch for enblend-enfuse.
Please check if the resulting package works as you expected or not and
report back your findings.

Regards,
Laszlo/GCS
Description: use Times font instead of Helvetica for testing
 For testing the font Helvetica used. This is fine, but for some reason
 recently fontconfig can't find it as URW Type 1 font for dot nodes. For
 other uses, Helvetica font is found by the way.
Author: Laszlo Boszormenyi (GCS) 
Forwarded: no
Last-Update: 2023-09-15

---

--- enblend-enfuse-4.2.orig/doc/uml-dot.m4
+++ enblend-enfuse-4.2/doc/uml-dot.m4
@@ -10,7 +10,7 @@ m4_dnl  (`uml_'), we treat only `Activit
 m4_dnl  need more for the Enblend/Enfuse documentation.
 
 
-m4_define(`uml_font', `Helvetica')
+m4_define(`uml_font', `Times')
 
 
 m4_dnl  Graph Attributes

Processed: Re: calculix-cgx - build-depends on dropped transitional package.

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + patch
Bug #1049440 [calculix-cgx] calculix-cgx - build-depends on dropped 
transitional package.
Added tag(s) patch.

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

Bug#1049440: calculix-cgx - build-depends on dropped transitional package.

[Matthias Klose]

Control: tags -1 + patch

patch at
https://patches.ubuntu.com/c/calculix-cgx/calculix-cgx_2.17+dfsg-2ubuntu1.patch

Bug#1051972: jami-daemon: Fails to start with libopendht2 2.6.0.4-1

[Asher Gordon]

Package: jami-daemon
Version: 20230206.0~ds2-1.3
Severity: grave
X-Debbugs-Cc: none, Asher Gordon 

Dear Maintainer,

After upgrading libopendht2, jami-daemon fails to start, making Jami
unusable. Downgrading libopendht2 fixes the problem.

$ apt-cache policy libopendht2 | grep Installed:
  Installed: 2.6.0.4-1
$ jami
Using Qt runtime version: 6.4.2
"notify server name: dunst, vendor: knopwob, version: 1.9.2 (2023-04-20), 
spec: 1.2"
"Using locale: en_US"
"Error : jamid is not available, make sure it is running"
terminate called after throwing an instance of 'char const*'
Aborted
$ /usr/libexec/jamid 
/usr/libexec/jamid: symbol lookup error: /usr/libexec/jamid: undefined 
symbol: 
_ZN3dht4http8ResolverC1ERN4asio10io_contextERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt10shared_ptrINS_6LoggerEE

Downgrading:

$ sudo sed -i~ s/trixie/bookworm/g /etc/apt/sources.list
$ sudo apt-get update
Get:1 tor+https://deb.debian.org/debian bookworm InRelease [151 kB]
[...]
Fetched 88.2 MB in 42s (2,120 kB/s)
Reading package lists... Done
$ sudo apt-get install libopendht2=2.4.12-7
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following packages will be DOWNGRADED:
  libopendht2
0 upgraded, 0 newly installed, 1 downgraded, 0 to remove and 0 not upgraded.
Need to get 806 kB of archives.
After this operation, 377 kB disk space will be freed.
Do you want to continue? [Y/n] y
Get:1 tor+https://deb.debian.org/debian bookworm/main amd64 libopendht2 
amd64 2.4.12-7 [806 kB]
Fetched 806 kB in 2s (335 kB/s)
debconf: unable to initialize frontend: Dialog
debconf: (Dialog frontend will not work on a dumb terminal, an emacs shell 
buffer, or without a controlling terminal.)
debconf: falling back to frontend: Readline
dpkg: warning: downgrading libopendht2:amd64 from 2.6.0.4-1 to 2.4.12-7
(Reading database ... 586843 files and directories currently installed.)
Preparing to unpack .../libopendht2_2.4.12-7_amd64.deb ...
Unpacking libopendht2:amd64 (2.4.12-7) over (2.6.0.4-1) ...
Setting up libopendht2:amd64 (2.4.12-7) ...
Processing triggers for libc-bin (2.37-8) ...
$ apt-cache policy libopendht2 | grep Installed:
  Installed: 2.4.12-7
$ jami
Using Qt runtime version: 6.4.2
"notify server name: dunst, vendor: knopwob, version: 1.9.2 (2023-04-20), 
spec: 1.2"
"Using locale: en_US"
No migration required
[...]
$ /usr/libexec/jamid 
Jami Daemon 13.7.0, by Savoir-faire Linux Inc. 2004-2023
https://jami.net/
[Video support enabled]
[Plugins support enabled]

22:56:59.121 os_core_unix.c !pjlib 2.12.1 for POSIX initialized
  C-c C-cCaught signal Interrupt, terminating...

Jami runs as expected.

It looks like jamid references an undefined symbol,
_ZN3dht4http8ResolverC1ERN4asio10io_contextERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt10shared_ptrINS_6LoggerEE,
which is likely present in the old version of libopendht2. I don't know
a whole lot about C++ and name mangling, but I would guess that Jami had
been using a deprecated or undocumented symbol, which has been removed
or renamed in libopendht2. It's also possible that the new libopendht2
was compiled with a newer compiler, which mangled the name differently,
but as far as I know, name mangling is supposed to be fairly stable
(again, I don't know a whole lot about this).

Also, the name unmangled:

$ echo 
_ZN3dht4http8ResolverC1ERN4asio10io_contextERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt10shared_ptrINS_6LoggerEE
 | c++filt
dht::http::Resolver::Resolver(asio::io_context&, 
std::__cxx11::basic_string, std::allocator > 
const&, std::shared_ptr)

Thanks,
Asher

-- System Information:
Debian Release: trixie/sid
  APT prefers testing-debug
  APT policy: (500, 'testing-debug'), (500, 'testing')
Architecture: amd64 (x86_64)

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

Versions of packages jami-daemon depends on:
ii  libarchive13 3.6.2-1
ii  libasound2   1.2.9-2
ii  libavcodec60 7:6.0-6
ii  libavdevice607:6.0-6
ii  libavfilter9 7:6.0-6
ii  libavformat607:6.0-6
ii  libavutil58  7:6.0-6
ii  libc62.37-8
ii  libdbus-c++-1-0v50.9.0-12
ii  libfmt9  9.1.0+ds1-2
ii  libgcc-s113.2.0-3
ii  libgit2-1.5  1.5.1+ds-1
ii  libgnutls30  3.8.1-4+b1
ii  libixml111:1.14.18-1
ii  libjsoncpp25 1.9.

Processed: Re: (many packages): build-depends on transitional package libgdk-pixbuf2.0-dev

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #1037406 [src:view3dscene] view3dscene: build-depends on transitional 
package libgdk-pixbuf2.0-dev
Severity set to 'serious' from 'important'

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

Processed: Re: (many packages): build-depends on transitional package libgdk-pixbuf2.0-dev

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #1037404 [src:transgui] transgui: build-depends on transitional package 
libgdk-pixbuf2.0-dev
Severity set to 'serious' from 'important'

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

Processed: Re: (many packages): build-depends on transitional package libgdk-pixbuf2.0-dev

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #1037398 [src:optgeo] optgeo: build-depends on transitional package 
libgdk-pixbuf2.0-dev
Severity set to 'serious' from 'important'

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

Processed: Re: (many packages): build-depends on transitional package libgdk-pixbuf2.0-dev

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #1037400 [src:spacefm] spacefm: build-depends on transitional package 
libgdk-pixbuf2.0-dev
Severity set to 'serious' from 'important'

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

Processed: Re: (many packages): build-depends on transitional package libgdk-pixbuf2.0-dev

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #1037395 [src:mediascanner2] mediascanner2: build-depends on transitional 
package libgdk-pixbuf2.0-dev
Severity set to 'serious' from 'important'

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

Processed: Re: (many packages): build-depends on transitional package libgdk-pixbuf2.0-dev

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #1037393 [src:lomiri-thumbnailer] lomiri-thumbnailer: build-depends on 
transitional package libgdk-pixbuf2.0-dev
Severity set to 'serious' from 'important'

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

Processed: Re: (many packages): build-depends on transitional package libgdk-pixbuf2.0-dev

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #1037392 [src:librm] librm: build-depends on transitional package 
libgdk-pixbuf2.0-dev
Severity set to 'serious' from 'important'

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

Processed: Re: (many packages): build-depends on transitional package libgdk-pixbuf2.0-dev

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #1037389 [src:libgom] libgom: build-depends on transitional package 
libgdk-pixbuf2.0-dev
Severity set to 'serious' from 'important'

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

Processed: Re: (many packages): build-depends on transitional package libgdk-pixbuf2.0-dev

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #1037382 [src:kwin-effect-xrdesktop] kwin-effect-xrdesktop: build-depends 
on transitional package libgdk-pixbuf2.0-dev
Severity set to 'serious' from 'important'

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

Processed: Re: (many packages): build-depends on transitional package libgdk-pixbuf2.0-dev

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #1037379 [src:gnome-nds-thumbnailer] gnome-nds-thumbnailer: build-depends 
on transitional package libgdk-pixbuf2.0-dev
Severity set to 'serious' from 'important'

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

Processed: Re: (many packages): build-depends on transitional package libgdk-pixbuf2.0-dev

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #1037380 {Done: Nilesh Patra } [src:go-dlib] go-dlib: 
build-depends on transitional package libgdk-pixbuf2.0-dev
Severity set to 'serious' from 'important'

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

Processed: Re: (many packages): build-depends on transitional package libgdk-pixbuf2.0-dev

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #1037376 [src:gnome-chemistry-utils] gnome-chemistry-utils: build-depends 
on transitional package libgdk-pixbuf2.0-dev
Severity set to 'serious' from 'important'

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

Processed: Re: (many packages): build-depends on transitional package libgdk-pixbuf2.0-dev

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #1037378 [src:gnome-hwp-support] gnome-hwp-support: build-depends on 
transitional package libgdk-pixbuf2.0-dev
Severity set to 'serious' from 'important'

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

Processed: Re: (many packages): build-depends on transitional package libgdk-pixbuf2.0-dev

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #1037374 [src:giggle] giggle: build-depends on transitional package 
libgdk-pixbuf2.0-dev
Severity set to 'serious' from 'important'

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

Processed: Re: (many packages): build-depends on transitional package libgdk-pixbuf2.0-dev

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #1037375 [src:gnome-books] gnome-books: build-depends on transitional 
package libgdk-pixbuf2.0-dev
Severity set to 'serious' from 'important'

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

Processed: Re: (many packages): build-depends on transitional package libgdk-pixbuf2.0-dev

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #1037373 [src:geany-plugins] geany-plugins: build-depends on transitional 
package libgdk-pixbuf2.0-dev
Severity set to 'serious' from 'important'

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

Processed: Re: (many packages): build-depends on transitional package libgdk-pixbuf2.0-dev

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #1037371 [src:exult] exult: build-depends on transitional package 
libgdk-pixbuf2.0-dev
Severity set to 'serious' from 'important'

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

Processed: Re: (many packages): build-depends on transitional package libgdk-pixbuf2.0-dev

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #1037370 [src:entangle] entangle: build-depends on transitional package 
libgdk-pixbuf2.0-dev
Severity set to 'serious' from 'important'

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

Processed: Re: (many packages): build-depends on transitional package libgdk-pixbuf2.0-dev

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #1037368 [src:dozzaqueux] dozzaqueux: build-depends on transitional package 
libgdk-pixbuf2.0-dev
Severity set to 'serious' from 'important'

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

Processed: Re: (many packages): build-depends on transitional package libgdk-pixbuf2.0-dev

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #1037367 {Done: David Mohammed } 
[src:desktopfolder] desktopfolder: build-depends on transitional package 
libgdk-pixbuf2.0-dev
Severity set to 'serious' from 'important'

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

Bug#1051967: marked as done (php-fig-log-test: ships /usr/share/php/Psr/Log/Test/*.php, already in php-psr-log-test)

[Debian Bug Tracking System]

Your message dated Fri, 15 Sep 2023 04:45:09 +0530
with message-id 
and subject line Re: [pkg-php-pear] Bug#1051967: php-fig-log-test: ships 
/usr/share/php/Psr/Log/Test/*.php, already in php-psr-log-test
has caused the Debian Bug report #1051967,
regarding php-fig-log-test: ships /usr/share/php/Psr/Log/Test/*.php, already in 
php-psr-log-test
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.)


-- 
1051967: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1051967
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: php-fig-log-test
Version: 1.1.0-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package failed to install
because it tries to overwrite other packages files:

  Preparing to unpack .../php-psr-log-test_1.1.0-1_all.deb ...
  Unpacking php-psr-log-test (1.1.0-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/php-psr-log-test_1.1.0-1_all.deb (--unpack):
   trying to overwrite '/usr/share/php/Psr/Log/Test/DummyTest.php', which is 
also in package php-fig-log-test 1.1.0-1
  Errors were encountered while processing:
   /var/cache/apt/archives/php-psr-log-test_1.1.0-1_all.deb

The conflicting files are

usr/share/php/Psr/Log/Test/DummyTest.php
usr/share/php/Psr/Log/Test/LoggerInterfaceTest.php
usr/share/php/Psr/Log/Test/TestLogger.php
usr/share/php/Psr/Log/Test/autoload.php


cheers,

Andreas
--- End Message ---
--- Begin Message ---

Hi,

Le 15/09/2023 à 04:24, Andreas Beckmann a écrit :

Package: php-fig-log-test
Version: 1.1.0-1

[…]

   dpkg: error processing archive […]/php-psr-log-test_1.1.0-1_all.deb 
(--unpack):
trying to overwrite […] which is also in package php-fig-log-test 1.1.0-1


Seems like a false positive: a package trying to overwrite files from 
the same package (and same version…).


Regards.--- End Message ---

Bug#1051967: php-fig-log-test: ships /usr/share/php/Psr/Log/Test/*.php, already in php-psr-log-test

[Andreas Beckmann]

Package: php-fig-log-test
Version: 1.1.0-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package failed to install
because it tries to overwrite other packages files:

  Preparing to unpack .../php-psr-log-test_1.1.0-1_all.deb ...
  Unpacking php-psr-log-test (1.1.0-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/php-psr-log-test_1.1.0-1_all.deb (--unpack):
   trying to overwrite '/usr/share/php/Psr/Log/Test/DummyTest.php', which is 
also in package php-fig-log-test 1.1.0-1
  Errors were encountered while processing:
   /var/cache/apt/archives/php-psr-log-test_1.1.0-1_all.deb

The conflicting files are

usr/share/php/Psr/Log/Test/DummyTest.php
usr/share/php/Psr/Log/Test/LoggerInterfaceTest.php
usr/share/php/Psr/Log/Test/TestLogger.php
usr/share/php/Psr/Log/Test/autoload.php


cheers,

Andreas

Processed: severity of 1043124 is serious

[Debian Bug Tracking System]

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

> severity 1043124 serious
Bug #1043124 [zfs-dkms] zfs-dkms: module fails to build for Linux 6.5: None of 
the expected "bops->release()" interfaces were detected.
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

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

Bug#1051965: compat-el: new upstream release 29.1.4.2 needed by elpa-hl-todo/sid

[Andreas Beckmann]

Package: compat-el
Version: 29.1.4.1-2
Severity: serious

elpa-hl-todo/sid is currently uninstallable since it depends on
elpa-compat (>= 29.1.4.2).


Andreas

Bug#1025574: marked as done (hplip: dependency on transitional policykit-1 package)

[Debian Bug Tracking System]

Your message dated Thu, 14 Sep 2023 21:52:44 +
with message-id 
and subject line Bug#1025574: fixed in hplip 3.22.10+dfsg0-3
has caused the Debian Bug report #1025574,
regarding hplip: dependency on transitional policykit-1 package
to be marked as done.

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

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


-- 
1025574: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025574
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: hplip
Version: 3.22.6+dfsg0-1
Severity: normal
User: pkg-utopia-maintain...@lists.alioth.debian.org
Usertags: policykit-1
Control: block 1025540 by -1

This package has a Build-Depends and Recommends on the transitional
package policykit-1, which has been separated into polkitd, pkexec and
(deprecated) polkitd-pkla packages.

If this package communicates with polkitd via D-Bus, please represent that
as a Depends, Recommends or Suggests on polkitd, whichever is appropriate
for the strength of the requirement.

If this package runs /usr/bin/pkexec, please represent that as a Depends,
Recommends or Suggests on pkexec, whichever is appropriate for the strength
of the requirement.

If this package requires polkit at build-time (usually for the gettext
extensions polkit.its and polkit.loc), please build-depend on **both**
libpolkit-gobject-1-dev and polkitd, even if the package does not
actually depend on libpolkit-gobject-1 at runtime. This is because
the gettext extensions are currently in polkitd, but might be moved to
libpolkit-gobject-1-dev in future (see #955204). pkexec is usually not
required at build-time.

For packages that are expected to be backported to bullseye, it's OK to
use an alternative dependency: polkitd | policykit-1 and/or
pkexec | policykit-1.

This is part of a mass bug filing, see
.

Thanks,
smcv
--- End Message ---
--- Begin Message ---
Source: hplip
Source-Version: 3.22.10+dfsg0-3
Done: Thorsten Alteholz 

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

Debian distribution maintenance software
pp.
Thorsten Alteholz  (supplier of updated hplip package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 14 Sep 2023 22:39:02 +0200
Source: hplip
Architecture: source
Version: 3.22.10+dfsg0-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Printing Team 
Changed-By: Thorsten Alteholz 
Closes: 1025574
Changes:
 hplip (3.22.10+dfsg0-3) unstable; urgency=medium
 .
   * debian/control: replace policykit-1 by pkexec, polkitd
 (Closes: #1025574)
Checksums-Sha1:
 c5a573fbe0c8c15d946b8590bd7daed586c70f13 3216 hplip_3.22.10+dfsg0-3.dsc
 1d42f53b0df1e51867019f48407bc5a8028a2c67 140184 
hplip_3.22.10+dfsg0-3.debian.tar.xz
 e095812e55168bc453a94ea94cee420417011d98 19690 
hplip_3.22.10+dfsg0-3_amd64.buildinfo
Checksums-Sha256:
 4d8cfcfe55e46261d99eed267cb49200525efc8abff59ca35f554eacb0823565 3216 
hplip_3.22.10+dfsg0-3.dsc
 dc6d49e0309a6b00b4428a121cbcfef464511aec5ae560bfc976f693c8d7d405 140184 
hplip_3.22.10+dfsg0-3.debian.tar.xz
 19b9761d45810c98121ef41ead46121748fd17f31fbc7d4e067b9ca90b15c34c 19690 
hplip_3.22.10+dfsg0-3_amd64.buildinfo
Files:
 1130394123c592a4965f932e9be48e5c 3216 utils optional hplip_3.22.10+dfsg0-3.dsc
 020a6374bef16477c06eaa77492dea5a 140184 utils optional 
hplip_3.22.10+dfsg0-3.debian.tar.xz
 b6e54c3316bbdeb01df4457f6e60db00 19690 utils optional 
hplip_3.22.10+dfsg0-3_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQKnBAEBCgCRFiEEYgH7/9u94Hgi6ruWlvysDTh7WEcFAmUDfHpfFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDYy
MDFGQkZGREJCREUwNzgyMkVBQkI5Njk2RkNBQzBEMzg3QjU4NDcTHGRlYmlhbkBh
bHRlaG9sei5kZQAKCRCW/KwNOHtYR3N3EACpZ+DtBjc89FVaEBE1nb/rjNwXOpTe
gB1QnRxKzup2wwW0zRLRrJrwmIyaKQB3Uc2Ju6MtkzlxEAdhqzWl9LJXkior0dpA
V25aV5IP4/xdIv22Qlliu9Hb01vBUB6YTK/GjupyMeuqVGRfjc/fD4bzE5bLsNbB
LSClpiEc2yHXP40m81e5eRdwqHHdwYJETOcNc6DPy6br5UmbIkx01ytNHePisaOE
aA9MxejYgCnepBkDM5tHB1noSA7al96TZuxi+YHPZbo0xfAjVj7MHUa6PFSiIazs
D0w579myx+dSLmSGqzrDeWFk3Enb8jal7/rP5wHe2WqfzqQA1dAcVnq/CpARsnJl
QmL

Bug#1051787: marked as done (Subject: CVE-2023-4863: Heap buffer overflow in WebP)

[Debian Bug Tracking System]

Your message dated Thu, 14 Sep 2023 21:22:29 +
with message-id 
and subject line Bug#1051786: fixed in libwebp 1.2.4-0.3
has caused the Debian Bug report #1051786,
regarding Subject: CVE-2023-4863: Heap buffer overflow in WebP
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.)


-- 
1051786: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1051786
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: chromium
Version: 116.0.5845.180-1
Severity: grave
Tags: security
Justification: user security hole
X-Debbugs-Cc: Debian Security Team 

Dear Maintainer,

116.0.5845.187 fixes a critical remote vulnerability in chrome

[$NA][1479274] Critical CVE-2023-4863: Heap buffer overflow in WebP.
Reported by Apple Security Engineering and Architecture (SEAR) and The Citizen
Lab at The University of Torontoʼs Munk School on 2023-09-06

https://chromereleases.googleblog.com/2023/09/stable-channel-update-for-desktop_11.html

Might want to look into this at least

(attempt 3, my reportbug broke sorry)

Jeff Cliff

-- System Information:
Debian Release: trixie/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'stable-debug'), (500,
'oldstable-debug')
Architecture: amd64 (x86_64)

Kernel: Linux 6.5.0-gnulibre (SMP w/2 CPU threads; PREEMPT)
Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8),
LANGUAGE=en_CA:en
Shell: /bin/sh linked to /usr/bin/dash
Init: sysvinit (via /sbin/init)
LSM: AppArmor: enabled


Versions of packages chromium depends on:
pn  chromium-common
ii  libasound2 1.2.9-2
ii  libatk-bridge2.0-0 2.49.91-2
ii  libatk1.0-02.49.91-2
ii  libatomic1 13.2.0-3
ii  libatspi2.0-0  2.49.91-2
ii  libbrotli1 1.0.9-2+b6
ii  libc6  2.37-7
ii  libcairo2  1.17.8-3
ii  libcups2   2.4.2-5
ii  libdbus-1-31.14.10-1devuan1
ii  libdouble-conversion3  3.3.0-1
ii  libdrm22.4.115-1
ii  libevent-2.1-7 2.1.12-stable-8
ii  libexpat1  2.5.0-2
ii  libflac12  1.4.3+ds-2
ii  libfontconfig1 2.14.2-5
ii  libfreetype6   2.13.2+dfsg-1
ii  libgbm123.1.7-1
ii  libgcc-s1  13.2.0-3
ii  libglib2.0-0   2.77.3-1
ii  libgtk-3-0 3.24.38-4
ii  libjpeg62-turbo1:2.1.5-2
ii  libjsoncpp25   1.9.5-6
ii  liblcms2-2 2.14-2
ii  libminizip11:1.2.13.dfsg-3
ii  libnspr4   2:4.35-1.1
ii  libnss32:3.92-1
pn  libopenh264-7  
ii  libopenjp2-7   2.5.0-2
ii  libopus0   1.4-1
ii  libpango-1.0-0 1.51.0+ds-2
ii  libpng16-161.6.40-1
ii  libpulse0  16.1+dfsg1-2+b1
ii  libsnappy1v5   1.1.10-1
ii  libstdc++6 13.2.0-3
ii  libwebp7   1.2.4-0.2
ii  libwebpdemux2  1.2.4-0.2
ii  libwebpmux31.2.4-0.2
ii  libwoff1   1.0.2-2
ii  libx11-6   2:1.8.6-1
ii  libxcb11.15-1
ii  libxcomposite1 1:0.4.5-1
ii  libxdamage11:1.1.6-1
ii  libxext6   2:1.3.4-1+b1
ii  libxfixes3 1:6.0.0-2
ii  libxkbcommon0  1.5.0-1
ii  libxml22.9.14+dfsg-1.3
ii  libxnvctrl0525.125.06-1
ii  libxrandr2 2:1.5.2-2+b1
ii  libxslt1.1 1.1.35-1
ii  zlib1g 1:1.2.13.dfsg-3

Versions of packages chromium recommends:
pn  chromium-sandbox  

Versions of packages chromium suggests:
pn  chromium-driver  
pn  chromium-l10n
pn  chromium-shell   
--- End Message ---
--- Begin Message ---
Source: libwebp
Source-Version: 1.2.4-0.3
Done: Gianfranco Costamagna 

We believe that the bug you reported is fixed in the latest version of
libwebp, 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.
Gianfranco Costamagna  (supplier of updated libwebp 
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 17:44:43 +0200
Source: libwebp
Built-For-Profiles: noudeb
Architecture

Bug#1051786: marked as done (CVE-2023-4863: Heap buffer overflow in WebP)

[Debian Bug Tracking System]

Your message dated Thu, 14 Sep 2023 21:22:29 +
with message-id 
and subject line Bug#1051786: fixed in libwebp 1.2.4-0.3
has caused the Debian Bug report #1051786,
regarding CVE-2023-4863: Heap buffer overflow in WebP
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.)


-- 
1051786: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1051786
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Subject: CVE-2023-4863: Heap buffer overflow in WebP
Package: chromium
Version: 116.0.5845.180-1
Severity: grave
Tags: security
Justification: user security hole
X-Debbugs-Cc: Debian Security Team 



On Tue, Sep 12, 2023 at 9:07 AM Jeffrey Cliff  wrote:
>
> Dear Maintainer,
>
> 116.0.5845.187 fixes a critical remote vulnerability in chrome
>
> [$NA][1479274] Critical CVE-2023-4863: Heap buffer overflow in WebP.
> Reported by Apple Security Engineering and Architecture (SEAR) and The Citizen
> Lab at The University of Torontoʼs Munk School on 2023-09-06
>
> https://chromereleases.googleblog.com/2023/09/stable-channel-update-for-desktop_11.html
>
> Might want to look into this at least
>
> Jeff Cliff
>
>
> -- System Information:
> Debian Release: trixie/sid
>   APT prefers unstable-debug
>   APT policy: (500, 'unstable-debug'), (500, 'stable-debug'), (500,
> 'oldstable-debug')
> Architecture: amd64 (x86_64)
>
> Kernel: Linux 6.5.0-gnulibre (SMP w/2 CPU threads; PREEMPT)
> Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8),
> LANGUAGE=en_CA:en
> Shell: /bin/sh linked to /usr/bin/dash
> Init: sysvinit (via /sbin/init)
> LSM: AppArmor: enabled
>
>
> Versions of packages chromium depends on:
> pn  chromium-common
> ii  libasound2 1.2.9-2
> ii  libatk-bridge2.0-0 2.49.91-2
> ii  libatk1.0-02.49.91-2
> ii  libatomic1 13.2.0-3
> ii  libatspi2.0-0  2.49.91-2
> ii  libbrotli1 1.0.9-2+b6
> ii  libc6  2.37-7
> ii  libcairo2  1.17.8-3
> ii  libcups2   2.4.2-5
> ii  libdbus-1-31.14.10-1devuan1
> ii  libdouble-conversion3  3.3.0-1
> ii  libdrm22.4.115-1
> ii  libevent-2.1-7 2.1.12-stable-8
> ii  libexpat1  2.5.0-2
> ii  libflac12  1.4.3+ds-2
> ii  libfontconfig1 2.14.2-5
> ii  libfreetype6   2.13.2+dfsg-1
> ii  libgbm123.1.7-1
> ii  libgcc-s1  13.2.0-3
> ii  libglib2.0-0   2.77.3-1
> ii  libgtk-3-0 3.24.38-4
> ii  libjpeg62-turbo1:2.1.5-2
> ii  libjsoncpp25   1.9.5-6
> ii  liblcms2-2 2.14-2
> ii  libminizip11:1.2.13.dfsg-3
> ii  libnspr4   2:4.35-1.1
> ii  libnss32:3.92-1
> pn  libopenh264-7  
> ii  libopenjp2-7   2.5.0-2
> ii  libopus0   1.4-1
> ii  libpango-1.0-0 1.51.0+ds-2
> ii  libpng16-161.6.40-1
> ii  libpulse0  16.1+dfsg1-2+b1
> ii  libsnappy1v5   1.1.10-1
> ii  libstdc++6 13.2.0-3
> ii  libwebp7   1.2.4-0.2
> ii  libwebpdemux2  1.2.4-0.2
> ii  libwebpmux31.2.4-0.2
> ii  libwoff1   1.0.2-2
> ii  libx11-6   2:1.8.6-1
> ii  libxcb11.15-1
> ii  libxcomposite1 1:0.4.5-1
> ii  libxdamage11:1.1.6-1
> ii  libxext6   2:1.3.4-1+b1
> ii  libxfixes3 1:6.0.0-2
> ii  libxkbcommon0  1.5.0-1
> ii  libxml22.9.14+dfsg-1.3
> ii  libxnvctrl0525.125.06-1
> ii  libxrandr2 2:1.5.2-2+b1
> ii  libxslt1.1 1.1.35-1
> ii  zlib1g 1:1.2.13.dfsg-3
>
> Versions of packages chromium recommends:
> pn  chromium-sandbox  
>
> Versions of packages chromium suggests:
> pn  chromium-driver  
> pn  chromium-l10n
> pn  chromium-shell   



-- 

End the campaign to Cancel Richard Stallman - go to stallmansupport.org !

--- End Message ---
--- Begin Message ---
Source: libwebp
Source-Version: 1.2.4-0.3
Done: Gianfranco Costamagna 

We believe that the bug you reported is fixed in the latest version of
libwebp, 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 mai

Processed: Re: libtk-img-doc: dpkg extraction error during upgrading

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #1051797 [libtk-img-doc] libtk-img-doc: dpkg extraction error during 
upgrading
Severity set to 'serious' from 'normal'
> notfound -1 1:1.4.14+dfsg-2
Bug #1051797 [libtk-img-doc] libtk-img-doc: dpkg extraction error during 
upgrading
No longer marked as found in versions libtk-img/1:1.4.14+dfsg-2.
> found -1 1:1.4.15+dfsg-1
Bug #1051797 [libtk-img-doc] libtk-img-doc: dpkg extraction error during 
upgrading
Marked as found in versions libtk-img/1:1.4.15+dfsg-1.

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

Bug#1051523: marked as done (krb5: FTBFS: cp: cannot stat 'rst_apiref/*.rst': No)

[Debian Bug Tracking System]

Your message dated Thu, 14 Sep 2023 19:07:56 +
with message-id 
and subject line Bug#1051523: fixed in krb5 1.20.1-4
has caused the Debian Bug report #1051523,
regarding krb5: FTBFS: cp: cannot stat 'rst_apiref/*.rst': No
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.)


-- 
1051523: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1051523
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: krb5
Version: 1.20.1-3
Severity: serious
Tags: ftbfs
X-Debbugs-Cc: sweetyf...@deepin.org

Hi,

During a local rebuild of krb5, your package failed to build.

[ 1121s] make[1]: Entering directory '/usr/src/packages/BUILD/build/doc'
[ 1121s] sed -e 's|@SRC@|../../src|g' \
[ 1121s] -e 's|@DOC@|../../src/../doc|g' ../../src/doc/Doxyfile.in 
> Doxyfile
[ 1122s] rm -f ../../src/../doc/version.py
[ 1122s] gcc -E -I../../src - < ../../src/doc/version.py.in > 
../../src/../doc/version.py
[ 1122s] rm -rf doxy rst_apiref rst_composite
[ 1122s] doxygen
[ 1122s] warning: Tag 'CLASS_DIAGRAMS' at line 14 of file 'Doxyfile' 
has become obsolete.
[ 1122s]  To avoid this warning please remove this line from 
your configuration file or upgrade it using "doxygen -u"
[ 1122s] warning: Changing CLASS_GRAPH option to TEXT because obsolete 
option CLASS_DIAGRAM was found and set to NO.
[ 1123s] (cwd=`pwd`; cd ../../src/../doc/tools && \
[ 1123s]python3 doxy.py -i $cwd/doxy/xml -o $cwd/rst_apiref)
[ 1123s] /usr/src/packages/BUILD/doc/tools/docmodel.py:209: 
SyntaxWarning: "is" with a literal. Did you mean "=="?
[ 1123s]   if p.type is "... " :
[ 1124s] mkdir -p rst_composite
[ 1124s] do_subdirs="_static _templates conf.py index.rst admin appdev 
basic build formats plugindev user about.rst build_this.rst copyright.rst 
mitK5defaults.rst mitK5features.rst mitK5license.rst notice.rst resources.rst" 
; \
[ 1124s] for i in $do_subdirs; do \
[ 1124s]cp -r ../../src/../doc/$i rst_composite; \
[ 1124s] done
[ 1125s] cp rst_apiref/*.rst rst_composite/appdev/refs/api
[ 1125s] cp: cannot stat 'rst_apiref/*.rst': No such file or directory
[ 1125s] make[1]: *** [Makefile:722: composite] Error 1
[ 1125s] make[1]: Leaving directory '/usr/src/packages/BUILD/build/doc'
[ 1125s] make: *** [debian/rules:59: build-indep-stamp] Error 2
[ 1125s] dpkg-buildpackage: error: debian/rules build subprocess 
returned exit status 2
[ 1127s] 
[ 1127s] k3s-worker-ci-amd-646d595fb7-nl9xc failed "build 
krb5_1.20.1-3.dsc" at Sat Sep  9 05:41:48 UTC 2023.

Good day,
Tianyu Chen

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

Kernel: Linux 5.10.0-amd64-desktop (SMP w/16 CPU threads)
Kernel taint flags: TAINT_WARN
Locale: LANG=zh_CN.UTF-8, LC_CTYPE=zh_CN.UTF-8 (charmap=UTF-8), LANGUAGE=zh_CN
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
--- End Message ---
--- Begin Message ---
Source: krb5
Source-Version: 1.20.1-4
Done: Sam Hartman 

We believe that the bug you reported is fixed in the latest version of
krb5, 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.
Sam Hartman  (supplier of updated krb5 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: Mon, 11 Sep 2023 11:06:57 -0600
Source: krb5
Architecture: source
Version: 1.20.1-4
Distribution: unstable
Urgency: low
Maintainer: Sam Hartman 
Changed-By: Sam Hartman 
Closes: 213316 751203 1017763 1043184 1051523
Changes:
 krb5 (1.20.1-4) unstable; urgency=low
 .
   [ Steve Langasek ]
   * libkrb5support0: require strict binary dependency to deal with glibc 2.38, 
Closes: #1043184
 .
   [Jelmer Vernooij]
   * krb5-user: Use alternatives for kinit, klist, kswitch, ksu, kpasswd,
 kdestroy, kadmin and ktutil. This allows installation
 together with heimdal-clients. Closes: #213316, #751203
 .
   [ Sam Ha

Bug#1051955: gpac: CVE-2023-41000

[Salvatore Bonaccorso]

Source: gpac
Version: 2.2.1+dfsg1-3
Severity: grave
Tags: security upstream
Justification: user security hole
Forwarded: https://github.com/gpac/gpac/issues/2550
X-Debbugs-Cc: car...@debian.org, Debian Security Team 

Hi,

The following vulnerability was published for gpac.

CVE-2023-41000[0]:
| GPAC through 2.2.1 has a use-after-free vulnerability in the
| function gf_bifs_flush_command_list in bifs/memory_decoder.c.


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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2023-41000
https://www.cve.org/CVERecord?id=CVE-2023-41000
[1] https://github.com/gpac/gpac/issues/2550
[2] https://github.com/gpac/gpac/commit/0018b5e4e07a1465287e7dff69b387929f5a75fa

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore

Bug#1051953: cups: CVE-2023-32360

[Salvatore Bonaccorso]

Source: cups
Version: 2.4.2-5
Severity: grave
Tags: security upstream
X-Debbugs-Cc: car...@debian.org, Debian Security Team 

Hi,

The following vulnerability was published for cups.

CVE-2023-32360[0]:
| An authentication issue was addressed with improved state
| management. This issue is fixed in macOS Big Sur 11.7.7, macOS
| Monterey 12.6.6, macOS Ventura 13.4. An unauthenticated user may be
| able to access recently printed documents.

Severity choosen on RC level, due to an unautnethicated user beeing
able to access recently printed documents.

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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2023-32360
https://www.cve.org/CVERecord?id=CVE-2023-32360
[1] 
https://github.com/OpenPrinting/cups/commit/a0c8b9c9556882f00c68b9727a95a1b6d1452913

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore

Processed: [bts-link] source package src:numba

[Debian Bug Tracking System]

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

> #
> # bts-link upstream status pull for source package src:numba
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> # https://bts-link-team.pages.debian.net/bts-link/
> #
> user debian-bts-l...@lists.debian.org
Setting user to debian-bts-l...@lists.debian.org (was 
debian-bts-l...@lists.debian.org).
> # remote status report for #1033907 (http://bugs.debian.org/1033907)
> # Bug title: numba: autopkgtest regression: segmentation fault on arm64
> #  * https://github.com/numba/numba/issues/9109
> #  * remote status changed: closed -> open
> #  * reopen upstream
> tags 1033907 - fixed-upstream
Bug #1033907 [src:numba] numba: autopkgtest regression: segmentation fault on 
arm64
Removed tag(s) fixed-upstream.
> usertags 1033907 - status-closed
Usertags were: status-closed.
There are now no usertags set.
> usertags 1033907 + status-open
There were no usertags set.
Usertags are now: status-open.
> thanks
Stopping processing here.

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

Processed: [bts-link] source package src:nomacs

[Debian Bug Tracking System]

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

> #
> # bts-link upstream status pull for source package src:nomacs
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> # https://bts-link-team.pages.debian.net/bts-link/
> #
> user debian-bts-l...@lists.debian.org
Setting user to debian-bts-l...@lists.debian.org (was 
debian-bts-l...@lists.debian.org).
> # remote status report for #1014124 (http://bugs.debian.org/1014124)
> # Bug title: nomacs: CVE-2020-23884
> #  * https://github.com/nomacs/nomacs/issues/516
> #  * remote status changed: open -> closed
> #  * closed upstream
> tags 1014124 + fixed-upstream
Bug #1014124 [src:nomacs] nomacs: CVE-2020-23884
Added tag(s) fixed-upstream.
> usertags 1014124 - status-open
Usertags were: status-open.
There are now no usertags set.
> usertags 1014124 + status-closed
There were no usertags set.
Usertags are now: status-closed.
> thanks
Stopping processing here.

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

Processed: limit source to krb5, tagging 1051523, tagging 751203, tagging 1017763, tagging 213316

[Debian Bug Tracking System]

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

> limit source krb5
Limiting to bugs with field 'source' containing at least one of 'krb5'
Limit currently set to 'source':'krb5'

> tags 1051523 + pending
Bug #1051523 [src:krb5] krb5: FTBFS: cp: cannot stat 'rst_apiref/*.rst': No
Added tag(s) pending.
> tags 751203 + pending
Bug #751203 [krb5-user] krb5-user: use alternatives to avoid conflict with 
heimdal-clients
Bug #810681 [krb5-user] heimdal-clients: installing package forces krb5-user to 
be removed
Added tag(s) pending.
Added tag(s) pending.
> tags 1017763 + pending
Bug #1017763 [krb5] krb5: re-enable (some) build-time tests
Added tag(s) pending.
> tags 213316 + pending
Bug #213316 [krb5-user] krb5-user: kinit doesn't use alternatives system
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#1051786: CVE-2023-4863: Heap buffer overflow in WebP

[Gianfranco Costamagna]

control: tags -1 pending

Hello, since the package libwebp looks a little bit maintained via NMU and 
package is on salsa.d.o/debian namespace, I'll just do it and git push/git push 
--tags.

G.

On Tue, 12 Sep 2023 09:08:55 -0600 Jeffrey Cliff  
wrote:

Subject: CVE-2023-4863: Heap buffer overflow in WebP
Package: chromium
Version: 116.0.5845.180-1
Severity: grave
Tags: security
Justification: user security hole
X-Debbugs-Cc: Debian Security Team 



On Tue, Sep 12, 2023 at 9:07 AM Jeffrey Cliff  wrote:
>
> Dear Maintainer,
>
> 116.0.5845.187 fixes a critical remote vulnerability in chrome
>
> [$NA][1479274] Critical CVE-2023-4863: Heap buffer overflow in WebP.
> Reported by Apple Security Engineering and Architecture (SEAR) and The Citizen
> Lab at The University of Torontoʼs Munk School on 2023-09-06
>
> 
https://chromereleases.googleblog.com/2023/09/stable-channel-update-for-desktop_11.html
>
> Might want to look into this at least
>
> Jeff Cliff
>
>
> -- System Information:
> Debian Release: trixie/sid
>   APT prefers unstable-debug
>   APT policy: (500, 'unstable-debug'), (500, 'stable-debug'), (500,
> 'oldstable-debug')
> Architecture: amd64 (x86_64)
>
> Kernel: Linux 6.5.0-gnulibre (SMP w/2 CPU threads; PREEMPT)
> Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8),
> LANGUAGE=en_CA:en
> Shell: /bin/sh linked to /usr/bin/dash
> Init: sysvinit (via /sbin/init)
> LSM: AppArmor: enabled
>
>
> Versions of packages chromium depends on:
> pn  chromium-common
> ii  libasound2 1.2.9-2
> ii  libatk-bridge2.0-0 2.49.91-2
> ii  libatk1.0-02.49.91-2
> ii  libatomic1 13.2.0-3
> ii  libatspi2.0-0  2.49.91-2
> ii  libbrotli1 1.0.9-2+b6
> ii  libc6  2.37-7
> ii  libcairo2  1.17.8-3
> ii  libcups2   2.4.2-5
> ii  libdbus-1-31.14.10-1devuan1
> ii  libdouble-conversion3  3.3.0-1
> ii  libdrm22.4.115-1
> ii  libevent-2.1-7 2.1.12-stable-8
> ii  libexpat1  2.5.0-2
> ii  libflac12  1.4.3+ds-2
> ii  libfontconfig1 2.14.2-5


OpenPGP_signature
Description: OpenPGP digital signature

Processed: Re: CVE-2023-4863: Heap buffer overflow in WebP

[Debian Bug Tracking System]

Processing control commands:

> tags -1 pending
Bug #1051786 [libwebp] CVE-2023-4863: Heap buffer overflow in WebP
Bug #1051787 [libwebp] Subject: CVE-2023-4863: Heap buffer overflow in WebP
Added tag(s) pending.
Added tag(s) pending.

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

Bug#1051916: marked as done (mingw-w64 add loongarch support.)

[Debian Bug Tracking System]

Your message dated Thu, 14 Sep 2023 13:10:37 +
with message-id 
and subject line Bug#1051916: fixed in mingw-w64 11.0.1-3
has caused the Debian Bug report #1051916,
regarding mingw-w64 add loongarch support.
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.)


-- 
1051916: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1051916
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: mingw-w64
Version: 11.0.1-2
Severity: serious
Tags: patch ftbfs
Justification: fails to build from source

Hello!

The mingw-w64 build failed in buildd , we should add loongarch support
for this . Please help to fix this problem .

Thanks,
JiaLing

[1] 
https://buildd.debian.org/status/fetch.php?pkg=mingw-w64&arch=loong64&ver=11.0.1-2&stamp=1692597666&raw=0
Description: Add loongarch support
Author: JiaLing Zhang 

--- mingw-w64-11.0.1.orig/mingw-w64-tools/widl/include/basetsd.h
+++ mingw-w64-11.0.1/mingw-w64-tools/widl/include/basetsd.h
@@ -331,6 +331,8 @@ typedef ULONG_PTR KAFFINITY, *PKAFFINITY
 # define WORDS_BIGENDIAN
 #elif defined(__hppa__)
 # undef  WORDS_BIGENDIAN
+#elif defined(__loongarch__) && defined(__loongarch64)
+# undef  WORDS_BIGENDIAN
 #elif defined(__m68k__)
 # define WORDS_BIGENDIAN
 #elif defined(__riscv) && __riscv_xlen == 64
--- End Message ---
--- Begin Message ---
Source: mingw-w64
Source-Version: 11.0.1-3
Done: Stephen Kitt 

We believe that the bug you reported is fixed in the latest version of
mingw-w64, 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.
Stephen Kitt  (supplier of updated mingw-w64 package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 14 Sep 2023 13:53:03 +0200
Source: mingw-w64
Architecture: source
Version: 11.0.1-3
Distribution: unstable
Urgency: medium
Maintainer: Stephen Kitt 
Changed-By: Stephen Kitt 
Closes: 1051916
Changes:
 mingw-w64 (11.0.1-3) unstable; urgency=medium
 .
   * Add support for loongarch; thanks to JiaLing Zhang for the patch!
 Closes: #1051916.
Checksums-Sha1:
 93eace00db629781facbd1e97b824e95f5d06be8 2605 mingw-w64_11.0.1-3.dsc
 0d029152beb16ab32efcd0fc38ad9c4e300f8ab8 108664 
mingw-w64_11.0.1-3.debian.tar.xz
 19571a1d5690335c803cde5ce070e31d240bed87 6510 
mingw-w64_11.0.1-3_source.buildinfo
Checksums-Sha256:
 722f0e2358ce5dd1278c6e6c32d34d56a4ad834cc70ed38762b154500cf63a51 2605 
mingw-w64_11.0.1-3.dsc
 bc0206149eaf6c9e9fa3995e91aa76878bd58448ce8568fbeac017358d1ab673 108664 
mingw-w64_11.0.1-3.debian.tar.xz
 fa2d21cc62a9133830c2450c1e1f6e2b15ca3d262e58bd6d212af63d048c4c14 6510 
mingw-w64_11.0.1-3_source.buildinfo
Files:
 c0399395ff4f6230d508fd13039db72c 2605 devel optional mingw-w64_11.0.1-3.dsc
 7387a486b3d835111b04698a0bc74932 108664 devel optional 
mingw-w64_11.0.1-3.debian.tar.xz
 c737ea3d02be7f8b7139bafa65e4de59 6510 devel optional 
mingw-w64_11.0.1-3_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEnPVX/hPLkMoq7x0ggNMC9Yhtg5wFAmUDAeUACgkQgNMC9Yht
g5wDow/9E8N9WRVDTLarLv0RfUHEUr4OTWrOCK3ryJdIvvqFOCJsHn74FMXHP1KE
QQMzo0t+MKpaWNPiwqBiYKZE2l2B2UmCtIMblG5UHAOrXGujB+S/Yi21m/CPHV2y
h1vbezMV3BZWIQfuykhmhbi/ExlSGQBrmmQknsmEWnkLb8Zeozfsvr8HJLzfFpUJ
g7vdsnECacBQLZH9RRTtlLmxPn/qIlcxbozEBiIWO4gBn8zAI2kspKaB2ONX0TDF
wCcnwMfXHo4t5xjxagWTJgL5vonq4ojyFk77LaHXKGJkyr+tMtxvlxsauBCEKqGm
WmH/zjZKWHNGPAgwDsZGQPw4uq4zKuX1POKJSu5OOwQVwkx+OrpwEe1XR2EgmYFX
pHfkaK2XQbetMQJ0Pl3k7yCedc7qU0dajYLPeO/MqsrAOstGXNz+fcyc2DY7UaZK
9QUyQCzlBT/NrF+JieRACSQoVyMNStlTIIM90bV82XjJAajgF1NIGx9vXWg6kyfL
f9AQrx9JTWXPJyebIqtjhhbnuBf+YUTgBTQECF3CanQxUgdOwJgiXhXEGKso8UwE
sYmxmKA1Au4q6b5Pg9vBByOfo3y91FC0gmAPRyy7gFBgcSxr59+jdZrhEGaXm403
U8R3UO6UKaAKa5GYIedLsSyvdEstPWeWwSogs45xblY46RvpmDY=
=7IjJ
-END PGP SIGNATURE End Message ---

Processed: python3-pysnmp-pysmi has an undeclared file conflict

[Debian Bug Tracking System]

Processing control commands:

> affects -1 + python3-pysmi
Bug #1051933 [python3-pysnmp-pysmi] python3-pysnmp-pysmi has an undeclared file 
conflict
Added indication that 1051933 affects python3-pysmi

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

Bug#1051933: python3-pysnmp-pysmi has an undeclared file conflict

[Helmut Grohne]

Package: python3-pysnmp-pysmi
Version: 1.0.4-1
Severity: serious
User: debian...@lists.debian.org
Usertags: fileconflict
Control: affects -1 + python3-pysmi

python3-pysnmp-pysmi has an undeclared file conflict. This may result in
an unpack error from dpkg.

The files
 * /usr/lib/python3/dist-packages/pysmi/__init__.py
 * /usr/lib/python3/dist-packages/pysmi/borrower/__init__.py
 * /usr/lib/python3/dist-packages/pysmi/borrower/anyfile.py
 * /usr/lib/python3/dist-packages/pysmi/borrower/base.py
 * /usr/lib/python3/dist-packages/pysmi/borrower/pyfile.py
 * /usr/lib/python3/dist-packages/pysmi/codegen/__init__.py
 * /usr/lib/python3/dist-packages/pysmi/codegen/base.py
 * /usr/lib/python3/dist-packages/pysmi/codegen/jsondoc.py
 * /usr/lib/python3/dist-packages/pysmi/codegen/null.py
 * /usr/lib/python3/dist-packages/pysmi/codegen/pysnmp.py
 * /usr/lib/python3/dist-packages/pysmi/codegen/symtable.py
 * /usr/lib/python3/dist-packages/pysmi/compat.py
 * /usr/lib/python3/dist-packages/pysmi/compiler.py
 * /usr/lib/python3/dist-packages/pysmi/debug.py
 * /usr/lib/python3/dist-packages/pysmi/error.py
 * /usr/lib/python3/dist-packages/pysmi/lexer/__init__.py
 * /usr/lib/python3/dist-packages/pysmi/lexer/base.py
 * /usr/lib/python3/dist-packages/pysmi/lexer/smi.py
 * /usr/lib/python3/dist-packages/pysmi/mibinfo.py
 * /usr/lib/python3/dist-packages/pysmi/parser/__init__.py
 * /usr/lib/python3/dist-packages/pysmi/parser/base.py
 * /usr/lib/python3/dist-packages/pysmi/parser/dialect.py
 * /usr/lib/python3/dist-packages/pysmi/parser/null.py
 * /usr/lib/python3/dist-packages/pysmi/parser/smi.py
 * /usr/lib/python3/dist-packages/pysmi/parser/smiv1.py
 * /usr/lib/python3/dist-packages/pysmi/parser/smiv1compat.py
 * /usr/lib/python3/dist-packages/pysmi/parser/smiv2.py
 * /usr/lib/python3/dist-packages/pysmi/reader/__init__.py
 * /usr/lib/python3/dist-packages/pysmi/reader/base.py
 * /usr/lib/python3/dist-packages/pysmi/reader/callback.py
 * /usr/lib/python3/dist-packages/pysmi/reader/ftpclient.py
 * /usr/lib/python3/dist-packages/pysmi/reader/httpclient.py
 * /usr/lib/python3/dist-packages/pysmi/reader/localfile.py
 * /usr/lib/python3/dist-packages/pysmi/reader/url.py
 * /usr/lib/python3/dist-packages/pysmi/reader/zipreader.py
 * /usr/lib/python3/dist-packages/pysmi/searcher/__init__.py
 * /usr/lib/python3/dist-packages/pysmi/searcher/anyfile.py
 * /usr/lib/python3/dist-packages/pysmi/searcher/base.py
 * /usr/lib/python3/dist-packages/pysmi/searcher/pyfile.py
 * /usr/lib/python3/dist-packages/pysmi/searcher/pypackage.py
 * /usr/lib/python3/dist-packages/pysmi/searcher/stub.py
 * /usr/lib/python3/dist-packages/pysmi/writer/__init__.py
 * /usr/lib/python3/dist-packages/pysmi/writer/base.py
 * /usr/lib/python3/dist-packages/pysmi/writer/callback.py
 * /usr/lib/python3/dist-packages/pysmi/writer/localfile.py
 * /usr/lib/python3/dist-packages/pysmi/writer/pyfile.py
are contained in the packages
 * python3-pysmi
   * 0.3.2-2 as present in bullseye
   * 0.3.2-3 as present in bookworm|trixie|unstable
 * python3-pysnmp-pysmi/1.0.4-1 as present in unstable

These packages can be unpacked concurrently, because there is no
relevant Replaces or Conflicts relation. Attempting to unpack these
packages concurrently results in an unpack error from dpkg, because none
of the packages installs a diversion for the affected files.

Kind regards

The Debian Usr Merge Analysis Tool

This bug report has been automatically filed with no human intervention.
The source code is available at https://salsa.debian.org/helmutg/dumat.
If the filing is unclear or in error, don't hesitate to contact
hel...@subdivi.de for assistance.

Bug#1051934: python3-pyasn1-modules-lextudio has an undeclared file conflict

[Helmut Grohne]

Package: python3-pyasn1-modules-lextudio
Version: 0.2.9-1
Severity: serious
User: debian...@lists.debian.org
Usertags: fileconflict
Control: affects -1 + python3-pyasn1-modules

python3-pyasn1-modules-lextudio has an undeclared file conflict. This
may result in an unpack error from dpkg.

The files
 * /usr/lib/python3/dist-packages/pyasn1_modules/__init__.py
 * /usr/lib/python3/dist-packages/pyasn1_modules/pem.py
 * /usr/lib/python3/dist-packages/pyasn1_modules/rfc1155.py
 * /usr/lib/python3/dist-packages/pyasn1_modules/rfc1157.py
 * /usr/lib/python3/dist-packages/pyasn1_modules/rfc1901.py
 * /usr/lib/python3/dist-packages/pyasn1_modules/rfc1902.py
 * /usr/lib/python3/dist-packages/pyasn1_modules/rfc1905.py
 * /usr/lib/python3/dist-packages/pyasn1_modules/rfc2251.py
 * /usr/lib/python3/dist-packages/pyasn1_modules/rfc2314.py
 * /usr/lib/python3/dist-packages/pyasn1_modules/rfc2315.py
 * /usr/lib/python3/dist-packages/pyasn1_modules/rfc2437.py
 * /usr/lib/python3/dist-packages/pyasn1_modules/rfc2459.py
 * /usr/lib/python3/dist-packages/pyasn1_modules/rfc2511.py
 * /usr/lib/python3/dist-packages/pyasn1_modules/rfc2560.py
 * /usr/lib/python3/dist-packages/pyasn1_modules/rfc2631.py
 * /usr/lib/python3/dist-packages/pyasn1_modules/rfc2634.py
 * /usr/lib/python3/dist-packages/pyasn1_modules/rfc2985.py
 * /usr/lib/python3/dist-packages/pyasn1_modules/rfc2986.py
 * /usr/lib/python3/dist-packages/pyasn1_modules/rfc3114.py
 * /usr/lib/python3/dist-packages/pyasn1_modules/rfc3161.py
 * /usr/lib/python3/dist-packages/pyasn1_modules/rfc3274.py
 * /usr/lib/python3/dist-packages/pyasn1_modules/rfc3279.py
 * /usr/lib/python3/dist-packages/pyasn1_modules/rfc3280.py
 * /usr/lib/python3/dist-packages/pyasn1_modules/rfc3281.py
 * /usr/lib/python3/dist-packages/pyasn1_modules/rfc3412.py
 * /usr/lib/python3/dist-packages/pyasn1_modules/rfc3414.py
 * /usr/lib/python3/dist-packages/pyasn1_modules/rfc3447.py
 * /usr/lib/python3/dist-packages/pyasn1_modules/rfc3560.py
 * /usr/lib/python3/dist-packages/pyasn1_modules/rfc3565.py
 * /usr/lib/python3/dist-packages/pyasn1_modules/rfc3709.py
 * /usr/lib/python3/dist-packages/pyasn1_modules/rfc3770.py
 * /usr/lib/python3/dist-packages/pyasn1_modules/rfc3779.py
 * /usr/lib/python3/dist-packages/pyasn1_modules/rfc3852.py
 * /usr/lib/python3/dist-packages/pyasn1_modules/rfc4043.py
 * /usr/lib/python3/dist-packages/pyasn1_modules/rfc4055.py
 * /usr/lib/python3/dist-packages/pyasn1_modules/rfc4073.py
 * /usr/lib/python3/dist-packages/pyasn1_modules/rfc4108.py
 * /usr/lib/python3/dist-packages/pyasn1_modules/rfc4210.py
 * /usr/lib/python3/dist-packages/pyasn1_modules/rfc4211.py
 * /usr/lib/python3/dist-packages/pyasn1_modules/rfc4334.py
 * /usr/lib/python3/dist-packages/pyasn1_modules/rfc4985.py
 * /usr/lib/python3/dist-packages/pyasn1_modules/rfc5035.py
 * /usr/lib/python3/dist-packages/pyasn1_modules/rfc5083.py
 * /usr/lib/python3/dist-packages/pyasn1_modules/rfc5084.py
 * /usr/lib/python3/dist-packages/pyasn1_modules/rfc5208.py
 * /usr/lib/python3/dist-packages/pyasn1_modules/rfc5280.py
 * /usr/lib/python3/dist-packages/pyasn1_modules/rfc5480.py
 * /usr/lib/python3/dist-packages/pyasn1_modules/rfc5649.py
 * /usr/lib/python3/dist-packages/pyasn1_modules/rfc5652.py
 * /usr/lib/python3/dist-packages/pyasn1_modules/rfc5751.py
 * /usr/lib/python3/dist-packages/pyasn1_modules/rfc5755.py
 * /usr/lib/python3/dist-packages/pyasn1_modules/rfc5913.py
 * /usr/lib/python3/dist-packages/pyasn1_modules/rfc5914.py
 * /usr/lib/python3/dist-packages/pyasn1_modules/rfc5915.py
 * /usr/lib/python3/dist-packages/pyasn1_modules/rfc5916.py
 * /usr/lib/python3/dist-packages/pyasn1_modules/rfc5917.py
 * /usr/lib/python3/dist-packages/pyasn1_modules/rfc5924.py
 * /usr/lib/python3/dist-packages/pyasn1_modules/rfc5934.py
 * /usr/lib/python3/dist-packages/pyasn1_modules/rfc5940.py
 * /usr/lib/python3/dist-packages/pyasn1_modules/rfc5958.py
 * /usr/lib/python3/dist-packages/pyasn1_modules/rfc5990.py
 * /usr/lib/python3/dist-packages/pyasn1_modules/rfc6010.py
 * /usr/lib/python3/dist-packages/pyasn1_modules/rfc6019.py
 * /usr/lib/python3/dist-packages/pyasn1_modules/rfc6031.py
 * /usr/lib/python3/dist-packages/pyasn1_modules/rfc6032.py
 * /usr/lib/python3/dist-packages/pyasn1_modules/rfc6120.py
 * /usr/lib/python3/dist-packages/pyasn1_modules/rfc6170.py
 * /usr/lib/python3/dist-packages/pyasn1_modules/rfc6187.py
 * /usr/lib/python3/dist-packages/pyasn1_modules/rfc6210.py
 * /usr/lib/python3/dist-packages/pyasn1_modules/rfc6211.py
 * /usr/lib/python3/dist-packages/pyasn1_modules/rfc6402.py
 * /usr/lib/python3/dist-packages/pyasn1_modules/rfc6482.py
 * /usr/lib/python3/dist-packages/pyasn1_modules/rfc6486.py
 * /usr/lib/python3/dist-packages/pyasn1_modules/rfc6487.py
 * /usr/lib/python3/dist-packages/pyasn1_modules/rfc6664.py
 * /usr/lib/python3/dist-packages/pyasn1_modules/rfc6955.py
 * /usr/lib/python3/dist-packages/pyasn1_modules/rfc6960.py
 * /usr/lib/python3/dist-packages/pyasn1_modules/rfc7030.py
 * /usr/lib/python3/di

Processed: python3-pyasn1-modules-lextudio has an undeclared file conflict

[Debian Bug Tracking System]

Processing control commands:

> affects -1 + python3-pyasn1-modules
Bug #1051934 [python3-pyasn1-modules-lextudio] python3-pyasn1-modules-lextudio 
has an undeclared file conflict
Added indication that 1051934 affects python3-pyasn1-modules

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

Processed: Re: Bug#1051822: installed chrony package post-installation script subprocess returned error exit status 1

[Debian Bug Tracking System]

Processing control commands:

> tags -1 - moreinfo
Bug #1051822 [chrony] installed chrony package post-installation script 
subprocess returned error exit status 1
Removed tag(s) moreinfo.

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

Bug#1051881: marked as done (postgresql-15: FTBFS with llvm-toolchain-16 as default)

[Debian Bug Tracking System]

Your message dated Thu, 14 Sep 2023 08:45:13 +
with message-id 
and subject line Bug#1051881: fixed in postgresql-16 16.0-2
has caused the Debian Bug report #1051881,
regarding postgresql-15: 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.)


-- 
1051881: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1051881
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: postgresql-15
Version: 15.4-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=postgresql-15&arch=amd64&ver=15.4-2%2Bb1&stamp=1694632271&raw=0

2023-09-13 19:10:56.959 UTC checkpointer[931151] LOG:  checkpoint complete: 
wrote 857 buffers (5.2%); 0 WAL file(s) added, 0 removed, 0 recycled; 
write=0.013 s, sync=0.001 s, total=0.020 s; sync files=0, longest=0.000 s, 
average=0.000 s; distance=9001 kB, estimate=132962 kB
2023-09-13 19:10:57.025 UTC postmaster[931148] LOG:  database system is shut 
down
 build/src/test/regress/regression.out 
test test_setup   ... FAILED  357 ms
test tablespace   ... FAILED  399 ms
parallel group (20 tests):  int8 oid name varchar bit char regproc boolean 
pg_lsn text int4 txid int2 money float8 enum uuid float4 rangetypes numeric
 boolean  ... FAILED  225 ms
 char ... FAILED  214 ms
 name ... FAILED  198 ms
 varchar  ... FAILED  205 ms
 text ... FAILED  239 ms
 int2 ... FAILED  252 ms
 int4 ... FAILED  246 ms
 int8 ... FAILED  182 ms
 oid  ... FAILED  188 ms
 float4   ... FAILED  278 ms
 float8   ... FAILED  260 ms
 bit  ... FAILED  205 ms
 numeric  ... FAILED  604 ms
 txid ... FAILED  244 ms
 uuid ... FAILED  267 ms
 enum ... FAILED  265 ms
 money... FAILED  250 ms
 rangetypes   ... FAILED  601 ms
 pg_lsn   ... FAILED  230 ms
 regproc  ... FAILED  211 ms
parallel group (19 tests):  circle time lseg line numerology point macaddr path 
timetz date macaddr8 inet interval strings polygon multirangetypes box 
timestamp timestamptz
 strings  ... FAILED  307 ms
 numerology   ... FAILED  172 ms
 point... FAILED  183 ms
 lseg ... FAILED  150 ms
 line ... FAILED  167 ms
 box  ... FAILED  436 ms
 path ... FAILED  195 ms
 polygon  ... FAILED  412 ms
 circle   ... FAILED  130 ms
 date ... FAILED  219 ms
 time ... FAILED  136 ms
 timetz   ... FAILED  207 ms
 timestamp... FAILED  535 ms
 timestamptz  ... FAILED  572 ms
 interval ... FAILED  253 ms
 inet ... FAILED  244 ms
 macaddr  ... FAILED  190 ms
 macaddr8 ... FAILED  218 ms
 multirangetypes  ... FAILED  417 ms
parallel group (12 tests):  comments unicode mvcc misc_sanity expressions 
tstypes xid horology geometry type_sanity opr_sanity regex
 geometry ... FAILED  195 ms
 horology ... FAILED  190 ms
 tstypes  ... FAILED  159 ms
 regex... FAILED  608 ms
 type_sanity  ... FAILED  210 ms
 opr_sanity   ... FAILED  462 ms
 misc_sanity  ... FAILED  124 ms
 comments ... FAILED  110 ms
 expressions  ... FAILED  156 ms
 unicode  ... FAILED  118 ms
 xid  ... FAILED  159 ms
 mvcc  

Bug#1051881: marked as done (postgresql-15: FTBFS with llvm-toolchain-16 as default)

[Debian Bug Tracking System]

Your message dated Thu, 14 Sep 2023 08:44:10 +
with message-id 
and subject line Bug#1051881: fixed in postgresql-15 15.4-3
has caused the Debian Bug report #1051881,
regarding postgresql-15: 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.)


-- 
1051881: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1051881
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: postgresql-15
Version: 15.4-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=postgresql-15&arch=amd64&ver=15.4-2%2Bb1&stamp=1694632271&raw=0

2023-09-13 19:10:56.959 UTC checkpointer[931151] LOG:  checkpoint complete: 
wrote 857 buffers (5.2%); 0 WAL file(s) added, 0 removed, 0 recycled; 
write=0.013 s, sync=0.001 s, total=0.020 s; sync files=0, longest=0.000 s, 
average=0.000 s; distance=9001 kB, estimate=132962 kB
2023-09-13 19:10:57.025 UTC postmaster[931148] LOG:  database system is shut 
down
 build/src/test/regress/regression.out 
test test_setup   ... FAILED  357 ms
test tablespace   ... FAILED  399 ms
parallel group (20 tests):  int8 oid name varchar bit char regproc boolean 
pg_lsn text int4 txid int2 money float8 enum uuid float4 rangetypes numeric
 boolean  ... FAILED  225 ms
 char ... FAILED  214 ms
 name ... FAILED  198 ms
 varchar  ... FAILED  205 ms
 text ... FAILED  239 ms
 int2 ... FAILED  252 ms
 int4 ... FAILED  246 ms
 int8 ... FAILED  182 ms
 oid  ... FAILED  188 ms
 float4   ... FAILED  278 ms
 float8   ... FAILED  260 ms
 bit  ... FAILED  205 ms
 numeric  ... FAILED  604 ms
 txid ... FAILED  244 ms
 uuid ... FAILED  267 ms
 enum ... FAILED  265 ms
 money... FAILED  250 ms
 rangetypes   ... FAILED  601 ms
 pg_lsn   ... FAILED  230 ms
 regproc  ... FAILED  211 ms
parallel group (19 tests):  circle time lseg line numerology point macaddr path 
timetz date macaddr8 inet interval strings polygon multirangetypes box 
timestamp timestamptz
 strings  ... FAILED  307 ms
 numerology   ... FAILED  172 ms
 point... FAILED  183 ms
 lseg ... FAILED  150 ms
 line ... FAILED  167 ms
 box  ... FAILED  436 ms
 path ... FAILED  195 ms
 polygon  ... FAILED  412 ms
 circle   ... FAILED  130 ms
 date ... FAILED  219 ms
 time ... FAILED  136 ms
 timetz   ... FAILED  207 ms
 timestamp... FAILED  535 ms
 timestamptz  ... FAILED  572 ms
 interval ... FAILED  253 ms
 inet ... FAILED  244 ms
 macaddr  ... FAILED  190 ms
 macaddr8 ... FAILED  218 ms
 multirangetypes  ... FAILED  417 ms
parallel group (12 tests):  comments unicode mvcc misc_sanity expressions 
tstypes xid horology geometry type_sanity opr_sanity regex
 geometry ... FAILED  195 ms
 horology ... FAILED  190 ms
 tstypes  ... FAILED  159 ms
 regex... FAILED  608 ms
 type_sanity  ... FAILED  210 ms
 opr_sanity   ... FAILED  462 ms
 misc_sanity  ... FAILED  124 ms
 comments ... FAILED  110 ms
 expressions  ... FAILED  156 ms
 unicode  ... FAILED  118 ms
 xid  ... FAILED  159 ms
 mvcc  

Processed: Re: Bug#1051766: lintian-brush: apply-multiarch-hints does not finish

[Debian Bug Tracking System]

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

> tags 1051766 + confirmed
Bug #1051766 [lintian-brush] lintian-brush: apply-multiarch-hints does not 
finish
Added tag(s) confirmed.
> thanks
Stopping processing here.

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

Bug#1051766: lintian-brush: apply-multiarch-hints does not finish

[Jelmer Vernooij]

tags 1051766 + confirmed
thanks


On Tue, Sep 12, 2023 at 12:29:31PM +0200, Andreas Tille wrote:
> after upgrading to lintian-brush 0.150 apply-multiarch-hints just does
> not end and I need to kill the actual xterm (even ^C does not back the
> prompt).  After killing the xterm it leaves a broken git repository.
> 
> I cloned my test repository freshly from salsa and  downgraded to
> lintian-brush 0.149.  Then I get:
> 
> 
>  $ apply-multiarch-hints 
> Traceback (most recent call last):
>   File "/usr/bin/apply-multiarch-hints", line 8, in 
> sys.exit(main())
>  ^^
>   File "/usr/lib/python3/dist-packages/lintian_brush/multiarch_hints.py", 
> line 512, in main
> MultiArchHintFixer(hints),
> ^
> TypeError: No constructor defined
> 
> 
> No idea whether this gives some hint - but at least neither the git
> repository is broken nor I have to interrupt really hard.

Thanks for the report. I've got a fix for this in progress, will
hopefully upload this weekend.

Jelmer

Bug#1043383: python-pcre2 now available in sid

[Michael R. Crusoe]

python-pcre2[0] from https://github.com/grtetrault/pcre2.py has passed 
the NEW queue and is now in the archive[1].


Upstream is responsive and seems easy to work with.

Already I've patched what appears to be the only user of python3-pcre to 
use python3-pcre2: debmutate [2].


Once that updated debmutate has migrated to testing, then this package 
(python-pcre) can be removed from the archive.


Cheers,

[0] https://tracker.debian.org/pkg/python-pcre2
[1] https://packages.debian.org/unstable/python3-pcre2
[2] https://salsa.debian.org/jelmer/debmutate/-/merge_requests/15

--
Michael R. Crusoe



OpenPGP_signature
Description: OpenPGP digital signature

Bug#1051881: marked as pending in postgresql

[Christoph Berg]

Control: tag -1 pending

Hello,

Bug #1051881 in postgresql 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/postgresql/postgresql/-/commit/4c4b928993b8c4a517f055ce63cbeb2e52036ae6


Stop building lib packages, postgresql-16 is in unstable.

Use LLVM 15 for JIT support, 16 is not supported yet. (Closes: #1051881)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1051881

Processed: Bug#1051881 marked as pending in postgresql

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1051881 [src:postgresql-15] postgresql-15: FTBFS with llvm-toolchain-16 as 
default
Ignoring request to alter tags of bug #1051881 to the same tags previously set

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

Bug#1043071: marked as done (crowdsec: FTBFS on amd64: test failure)

[Debian Bug Tracking System]

Your message dated Thu, 14 Sep 2023 09:56:43 +0200
with message-id <20230914075643.4s62zejdgirqq...@debamax.com>
and subject line Re: Bug#1043071: crowdsec: FTBFS on amd64: test failure
has caused the Debian Bug report #1043071,
regarding crowdsec: FTBFS on amd64: test failure
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.)


-- 
1043071: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1043071
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: crowdsec
Version: 1.4.6-6
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=crowdsec&arch=amd64&ver=1.4.6-6%2Bb1&stamp=1691250195&raw=0

panic: test timed out after 10m0s
running tests:
TestPluginWatcherInterval (9m21s)

goroutine 1446 [running]:
testing.(*M).startAlarm.func1()
/usr/lib/go-1.20/src/testing/testing.go:2241 +0x3c5
created by time.goFunc
/usr/lib/go-1.20/src/time/sleep.go:176 +0x32

goroutine 1 [chan receive, 9 minutes]:
testing.(*T).Run(0xc0003649c0, {0xbc3e75?, 0x5282e5?}, 0xc04718)
/usr/lib/go-1.20/src/testing/testing.go:1630 +0x405
testing.runTests.func1(0x10f5680?)
/usr/lib/go-1.20/src/testing/testing.go:2036 +0x45
testing.tRunner(0xc0003649c0, 0xc00029fc88)
/usr/lib/go-1.20/src/testing/testing.go:1576 +0x10b
testing.runTests(0xc000372b40?, {0x109db80, 0xb, 0xb}, {0xc00035c190?, 
0x100c00029fd10?, 0x10f4c60?})
/usr/lib/go-1.20/src/testing/testing.go:2034 +0x489
testing.(*M).Run(0xc000372b40)
/usr/lib/go-1.20/src/testing/testing.go:1906 +0x63a
main.main()
_testmain.go:67 +0x1aa

goroutine 194 [chan receive, 9 minutes]:
gopkg.in/tomb%2ev2.(*Tomb).Wait(0xc0004927d0)
/<>/_build/src/gopkg.in/tomb.v2/tomb.go:126 +0x35
github.com/crowdsecurity/crowdsec/pkg/csplugin.resetTestTomb(0xcba2e0?, 
0xc7eb40)

/<>/_build/src/github.com/crowdsecurity/crowdsec/pkg/csplugin/watcher_test.go:20
 +0x45
github.com/crowdsecurity/crowdsec/pkg/csplugin.TestPluginWatcherInterval(0xc00036be00?)

/<>/_build/src/github.com/crowdsecurity/crowdsec/pkg/csplugin/watcher_test.go:76
 +0x2b4
testing.tRunner(0xc00041fd40, 0xc04718)
/usr/lib/go-1.20/src/testing/testing.go:1576 +0x10b
created by testing.(*T).Run
/usr/lib/go-1.20/src/testing/testing.go:1629 +0x3ea

goroutine 163 [select]:
github.com/crowdsecurity/crowdsec/pkg/csplugin.(*PluginBroker).Run(0xc000278640,
 0xc0004139f0)

/<>/_build/src/github.com/crowdsecurity/crowdsec/pkg/csplugin/broker.go:104
 +0x12f
created by 
github.com/crowdsecurity/crowdsec/pkg/csplugin.TestBrokerRunTimeThreshold

/<>/_build/src/github.com/crowdsecurity/crowdsec/pkg/csplugin/broker_test.go:499
 +0x45b

goroutine 164 [select]:
github.com/crowdsecurity/crowdsec/pkg/csplugin.(*PluginWatcher).watchPluginTicker(0xc000278688,
 {0xcc05e0, 0xd})

/<>/_build/src/github.com/crowdsecurity/crowdsec/pkg/csplugin/watcher.go:113
 +0x1a5
github.com/crowdsecurity/crowdsec/pkg/csplugin.(*PluginWatcher).Start.func1()

/<>/_build/src/github.com/crowdsecurity/crowdsec/pkg/csplugin/watcher.go:72
 +0x25
gopkg.in/tomb%2ev2.(*Tomb).run(0xc000413a40, 0xc0003b0380?)
/<>/_build/src/gopkg.in/tomb.v2/tomb.go:163 +0x36
created by gopkg.in/tomb%2ev2.(*Tomb).Go
/<>/_build/src/gopkg.in/tomb.v2/tomb.go:159 +0xee

goroutine 32 [select, 9 minutes]:
github.com/crowdsecurity/crowdsec/pkg/csplugin.(*PluginBroker).Run(0xc000372460,
 0xc0004932c0)

/<>/_build/src/github.com/crowdsecurity/crowdsec/pkg/csplugin/broker.go:104
 +0x12f
created by github.com/crowdsecurity/crowdsec/pkg/csplugin.TestBrokerNoThreshold

/<>/_build/src/github.com/crowdsecurity/crowdsec/pkg/csplugin/broker_test.go:282
 +0x30d

goroutine 175 [select]:
github.com/crowdsecurity/crowdsec/pkg/csplugin.(*PluginWatcher).watchPluginTicker(0xc000372fe8,
 {0xc3b6f0, 0xd})

/<>/_build/src/github.com/crowdsecurity/crowdsec/pkg/csplugin/watcher.go:113
 +0x1a5
github.com/crowdsecurity/crowdsec/pkg/csplugin.(*PluginWatcher).Start.func1()

/<>/_build/src/github.com/crowdsecurity/crowdsec/pkg/csplugin/watcher.go:72
 +0x25
gopkg.in/tomb%2ev2.(*Tomb).run(0xc0004925a0, 0xc000486288?)
/<>/_build/src/gopkg.in/tomb.v2/tomb.go:163 +0x36
created by gopkg.in/tomb%2ev2.(*Tomb).Go
/<>/_build/src/gopkg.in/tomb.v2/tomb.go:159 +0xee

goroutine 176 [select, 9 minutes]:
github.com/crowdsecurity/crowdsec/pkg/csplugin.(*PluginWatcher).watchPluginAlertCounts(0xc000372fe8)
   

Processed: Re: fluidsynth: Consider building with pipewire support

[Debian Bug Tracking System]

Processing control commands:

> affects -1 + src:ardour src:blockattack src:calf src:chocolate-doom 
> src:crispy-doom src:denemo src:fluidsynth-dssi src:freedink src:frotz 
> src:gambas3 src:gargoyle-free src:gst-plugins-bad1.0 src:jag src:pianobooster 
> src:planetblupi src:qsynth src:qtads src:scummvm src:toppler src:ufoai src:vlc
Bug #1051819 [fluidsynth] fluidsynth: Consider building with pipewire support
Added indication that 1051819 affects src:ardour, src:blockattack, src:calf, 
src:chocolate-doom, src:crispy-doom, src:denemo, src:fluidsynth-dssi, 
src:freedink, src:frotz, src:gambas3, src:gargoyle-free, 
src:gst-plugins-bad1.0, src:jag, src:pianobooster, src:planetblupi, src:qsynth, 
src:qtads, src:scummvm, src:toppler, src:ufoai, and src:vlc

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

Bug#1051819: fluidsynth: Consider building with pipewire support

[Johannes Schauer Marin Rodrigues]

Control: affects -1 + src:ardour src:blockattack src:calf src:chocolate-doom 
src:crispy-doom src:denemo src:fluidsynth-dssi src:freedink src:frotz 
src:gambas3 src:gargoyle-free src:gst-plugins-bad1.0 src:jag src:pianobooster 
src:planetblupi src:qsynth src:qtads src:scummvm src:toppler src:ufoai src:vlc

Hi,

On Thu, 14 Sep 2023 07:23:22 +0200 Gianfranco Costamagna 
 wrote:
> And also a -dev dependency on the library package, as shown by autopkgtests
> now being regressed (and vlc build broken).

ah you were faster than me! :D

(i made the mistake of first trying to compile all its reverse dependencies for
more evidence)

This not only breaks vlc but also (at least) the source packages I listed in
the "effects" bts control line above.

I verified that those packages build again when libpipewire-0.3-dev is
installed as is done by Gianfranco's patch.

Thanks!

cheers, josch

signature.asc
Description: signature

Processed: Bug#1051881 marked as pending in postgresql

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1051881 [src:postgresql-15] postgresql-15: FTBFS with llvm-toolchain-16 as 
default
Added tag(s) pending.

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

Bug#1051881: marked as pending in postgresql

[Christoph Berg]

Control: tag -1 pending

Hello,

Bug #1051881 in postgresql 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/postgresql/postgresql/-/commit/8a5b631833508c9ee61d41433c1073a3c2ce9b56


Use LLVM 15 for JIT support, 16 is not supported yet. (Closes: #1051881)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1051881

Bug#1050688: poetry: needs internet access during build?

[Gianfranco Costamagna]

Hello,
On Tue, 12 Sep 2023 21:59:46 -0300 Emmanuel Arias  wrote:

Hi,

I can confirm that the next 4 tests needs internet to work:

* tests/installation/test_installer.py::test_installer_with_pypi_repository
* tests/installation/test_chef.py::test_prepare_directory_editable
* tests/installation/test_chef.py::test_prepare_directory
* tests/installation/test_chef.py::test_prepare_directory_with_extensions

I will thank you if you can tell me how run in a not internet builder.
My solution was just disconnect my RJ-45 from the computer to test the
no internet because I didn't found a solution from autopkgtest or sbuild
:-D.



Uploading in an Ubuntu ppa is the quicker way to test this :)

Probably you can export some non-existing proxy but I don't know if this works 
or not with the code.
I also unplug RJ-45 or export some iptables during build:

sudo iptables -P OUTPUT DROP

sudo iptables -P OUTPUT ACCEPT

But I don't know how much this can work or disrupt Debian builders.

G.


Cheers,
Emmanuel

Bug#1051916: mingw-w64 add loongarch support.

[JiaLing Zhang]

Source: mingw-w64
Version: 11.0.1-2
Severity: serious
Tags: patch ftbfs
Justification: fails to build from source

Hello!

The mingw-w64 build failed in buildd , we should add loongarch support
for this . Please help to fix this problem .

Thanks,
JiaLing

[1] 
https://buildd.debian.org/status/fetch.php?pkg=mingw-w64&arch=loong64&ver=11.0.1-2&stamp=1692597666&raw=0
Description: Add loongarch support
Author: JiaLing Zhang 

--- mingw-w64-11.0.1.orig/mingw-w64-tools/widl/include/basetsd.h
+++ mingw-w64-11.0.1/mingw-w64-tools/widl/include/basetsd.h
@@ -331,6 +331,8 @@ typedef ULONG_PTR KAFFINITY, *PKAFFINITY
 # define WORDS_BIGENDIAN
 #elif defined(__hppa__)
 # undef  WORDS_BIGENDIAN
+#elif defined(__loongarch__) && defined(__loongarch64)
+# undef  WORDS_BIGENDIAN
 #elif defined(__m68k__)
 # define WORDS_BIGENDIAN
 #elif defined(__riscv) && __riscv_xlen == 64