Processed: affects 1050349

[Debian Bug Tracking System]

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

> affects 1050349 + src:kimageformats
Bug #1050349 [libimath-dev] libimath-dev: CMake fails because of missing python 
bindings
Bug #1051110 [libimath-dev] kimageformats: FTBFS: CMake Error at 
/usr/lib/x86_64-linux-gnu/cmake/Imath/ImathTargets.cmake:115
Added indication that 1050349 affects src:kimageformats
Added indication that 1051110 affects src:kimageformats
> thanks
Stopping processing here.

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

Processed: Re: Bug#1041508: tex-common: fmutil fails to rebuild formats

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #1041508 [tex-common] tex-common: fmutil fails to rebuild formats
Severity set to 'serious' from 'important'

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

Processed: severity of 1050349 is serious, forcibly merging 1050349 1051110, affects 1050349

[Debian Bug Tracking System]

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

> severity 1050349 serious
Bug #1050349 [libimath-dev] libimath-dev: CMake fails because of missing python 
bindings
Severity set to 'serious' from 'normal'
> forcemerge 1050349 1051110
Bug #1050349 [libimath-dev] libimath-dev: CMake fails because of missing python 
bindings
Bug #1050349 [libimath-dev] libimath-dev: CMake fails because of missing python 
bindings
Added tag(s) ftbfs.
Bug #1051110 [libimath-dev] kimageformats: FTBFS: CMake Error at 
/usr/lib/x86_64-linux-gnu/cmake/Imath/ImathTargets.cmake:115
Removed indication that 1051110 affects src:kimageformats
Merged 1050349 1051110
> affects 1050349 + src:kio-extras
Bug #1050349 [libimath-dev] libimath-dev: CMake fails because of missing python 
bindings
Bug #1051110 [libimath-dev] kimageformats: FTBFS: CMake Error at 
/usr/lib/x86_64-linux-gnu/cmake/Imath/ImathTargets.cmake:115
Added indication that 1050349 affects src:kio-extras
Added indication that 1051110 affects src:kio-extras
> thanks
Stopping processing here.

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

Processed: reassign 1051110 to libimath-dev, affects 1051110

[Debian Bug Tracking System]

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

> reassign 1051110 libimath-dev imath/3.1.9-2
Bug #1051110 [src:kimageformats] kimageformats: FTBFS: CMake Error at 
/usr/lib/x86_64-linux-gnu/cmake/Imath/ImathTargets.cmake:115
Bug reassigned from package 'src:kimageformats' to 'libimath-dev'.
No longer marked as found in versions kimageformats/5.107.0-3.
Ignoring request to alter fixed versions of bug #1051110 to the same values 
previously set
Bug #1051110 [libimath-dev] kimageformats: FTBFS: CMake Error at 
/usr/lib/x86_64-linux-gnu/cmake/Imath/ImathTargets.cmake:115
Marked as found in versions imath/3.1.9-2.
> affects 1051110 + src:kimageformats
Bug #1051110 [libimath-dev] kimageformats: FTBFS: CMake Error at 
/usr/lib/x86_64-linux-gnu/cmake/Imath/ImathTargets.cmake:115
Added indication that 1051110 affects src:kimageformats
> thanks
Stopping processing here.

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

Bug#1040963: src:starpu: fails to migrate to testing for too long: unsatisfiable dependency on armel, mipsel and s390x + segfault

[Paul Gevers]

Hi,

On Thu, 13 Jul 2023 11:18:41 +0200 Paul Gevers  wrote:
If you believe your package is unable to migrate to testing due to 
issues beyond your control, don't hesitate to contact the Release Team.


The only remaining issue (autopkgtest failures on armel and armhf) is 
caused due to bug 1043238 in libpfm4, which is triggered by bug 1036818 
in lxcfs. I'm going to let starpu migrate.


Paul


OpenPGP_signature.asc
Description: OpenPGP digital signature

Processed: Re: Bug#1050256: autopkgtest fails on debci

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #1050256 [apparmor,lxc] apparmor makes systemd autopkgtests fail on bookworm
Severity set to 'serious' from 'important'

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

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

[Vincent Lefevre]

Package: maildrop
Version: 2.9.3-2+b1
Severity: grave
Justification: renders package unusable

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

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

which says:

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

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

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

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

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

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

maildrop suggests no packages.

-- no debconf information

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

Bug#1050424: marked as done (progress-linux-gnome-desktop: Unsatisfiable dependencies after GNOME Shell 44 transition)

[Debian Bug Tracking System]

Your message dated Sat, 2 Sep 2023 20:24:52 -0400
with message-id 

and subject line close metapackage bugs
has caused the Debian Bug report #1050424,
regarding progress-linux-gnome-desktop: Unsatisfiable dependencies after GNOME 
Shell 44 transition
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.)


-- 
1050424: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1050424
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: progress-linux-gnome-desktop
Severity: serious
Version: 20221002-9
Tags: trixie sid
Control: block -1 by 1041575
Control: block -1 by 1050421

progress-linux-gnome-desktop depends on
gnome-shell-extension-impatience and
gnome-shell-extension-no-annoyance but those extensions, as packaged
in Debian, are not compatible with GNOME Shell 44 and will be removed
from Testing.

That means that progress-linux-metapackages will be unable to migrate
to Testing until it drops those dependencies or the extensions are
made compatible with GNOME Shell 44.

Thank you,
Jeremy Bícha
--- End Message ---
--- Begin Message ---
thanks--- End Message ---

Bug#1050422: marked as done (bfh-gnome-desktop: Unsatisfiable dependencies after GNOME Shell 44 transition)

[Debian Bug Tracking System]

Your message dated Sat, 2 Sep 2023 20:24:52 -0400
with message-id 

and subject line close metapackage bugs
has caused the Debian Bug report #1050422,
regarding bfh-gnome-desktop: Unsatisfiable dependencies after GNOME Shell 44 
transition
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.)


-- 
1050422: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1050422
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: bfh-gnome-desktop
Severity: serious
Version: 20211009-20
Tags: trixie sid
Control: blocks -1 by 1041575
Control: block -1 by 1050421

bfh-gnome-desktop depends on gnome-shell-extension-impatience and
gnome-shell-extension-no-annoyance but those extensions, as packaged
in Debian, are not compatible with GNOME Shell 44 and will be removed
from Testing.

That means that bfh-metapackages will also be removed from Testing
until it drops those dependencies or the extensions are made
compatible with GNOME Shell 44.

Thank you,
Jeremy Bícha
--- End Message ---
--- Begin Message ---
thanks--- End Message ---

Bug#1051003: libgdbm6: trap divide error in libgdbm.so.6.0.0

[Nicolas Mora]

Hello,

On Fri, 01 Sep 2023 11:13:22 +0200 Schnitzi 
 wrote:


Journal-Output:
Aug 31 18:02:34 xyz dovecot[2451]: auth: Error: auth-worker: Aborted PASSV 
request for x...@xyz.xyz: Worker process died unexpectedly
Aug 31 18:02:34 xyz dovecot[2451]: auth-worker: Fatal: master: 
service(auth-worker): child 118182 killed with signal 8
Aug 31 18:02:34 xyz kernel: traps: auth[118182] trap divide error 
ip:7f7366d16f06 sp:7ffc44386580 error:0 in libgdbm.so.6.0.0[7f7366d12000+a000]



I don't know if the problem comes from gdbm or pam_shield yet. The 
pam_shield package, although orphaned, could be updated. The original 
pam-shield repository is archived [1], but there seems to be a more 
recent fork [2].


Could you test with h0tw1r3's 0.9.7 release [3] if the problem persist? 
If this fixes the problem, then updating pam-shield package would fix 
this issue.


/Nicolas

[1] https://github.com/jtniehof/pam_shield
[2] https://github.com/h0tw1r3/pam_shield
[3] https://github.com/h0tw1r3/pam_shield/releases/tag/0.9.7

Bug#1038412: marked as done (gnome-shell-extension-weather: Update to 121 to support GNOME 44)

[Debian Bug Tracking System]

Your message dated Sat, 02 Sep 2023 22:49:00 +
with message-id 
and subject line Bug#1041583: fixed in gnome-shell-extension-weather 121-1
has caused the Debian Bug report #1041583,
regarding gnome-shell-extension-weather: Update to 121 to support GNOME 44
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.)


-- 
1041583: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1041583
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gnome-shell-extension-weather
Version: 119-1
Severity: normal
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: gnome-shell-44

Dear Maintainer,

Please update to 121 to support GNOME 44.

Best,
Amr


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

Kernel: Linux 6.1.0-9-amd64 (SMP w/8 CPU threads; PREEMPT)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.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 gnome-shell-extension-weather depends on:
ii  ca-certificates  20230311
ii  dconf-gsettings-backend [gsettings-backend]  0.40.0-4
ii  gir1.2-clutter-1.0   1.26.4+dfsg-4
ii  gir1.2-glib-2.0  1.74.0-3
ii  gir1.2-gtk-3.0   3.24.37-2
ii  gir1.2-soup-3.0  3.2.2-2
ii  gnome-shell  43.6-1

Versions of packages gnome-shell-extension-weather recommends:
ii  gnome-tweaks  42~beta-4

gnome-shell-extension-weather suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: gnome-shell-extension-weather
Source-Version: 121-1
Done: Jeremy Bícha 

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

Debian distribution maintenance software
pp.
Jeremy Bícha  (supplier of updated 
gnome-shell-extension-weather 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: Sat, 02 Sep 2023 18:30:58 -0400
Source: gnome-shell-extension-weather
Built-For-Profiles: noudeb
Architecture: source
Version: 121-1
Distribution: unstable
Urgency: high
Maintainer: Debian GNOME Maintainers 

Changed-By: Jeremy Bícha 
Closes: 1018285 1038412 1041583
Changes:
 gnome-shell-extension-weather (121-1) unstable; urgency=high
 .
   [ Jeremy Bícha ]
   * New upstream release (Closes: #1018285, #1038412, #1041583)
   * Bump compatible GNOME Shell versions per metadata.json
 .
   [ Debian Janitor ]
   * Add debian/upstream/metadata
   * Update standards version to 4.6.2, no changes needed
Checksums-Sha1:
 b313b153a3d3cf5cec7d48d4da77f44189c48a9e 2200 
gnome-shell-extension-weather_121-1.dsc
 389ebc6915c28535063602daba5d56295be7ed3c 171925 
gnome-shell-extension-weather_121.orig.tar.bz2
 5ed182a0aa6ab8cc057ee66973ae1cdb5a62b4ca 5684 
gnome-shell-extension-weather_121-1.debian.tar.xz
 bb2f686f3e868f6c1a7dcea687a24530a80c4435 8268 
gnome-shell-extension-weather_121-1_source.buildinfo
Checksums-Sha256:
 e32b4996cd2f807450b958302f613b12f84572df7af9db52614e9670a3be7c48 2200 
gnome-shell-extension-weather_121-1.dsc
 a14a056f98010e8e8234b803dc9b576693dcd47645a688dd34597763f4c12c79 171925 
gnome-shell-extension-weather_121.orig.tar.bz2
 ae320e60ad496100d139436534bb3a6be3fc5b5d73f3f616629faa9266cc1be4 5684 
gnome-shell-extension-weather_121-1.debian.tar.xz
 6b83b94621fc397d42c884e99db9e8fad83f1a26c4b817df5d477af74f854092 8268 
gnome-shell-extension-weather_121-1_source.buildinfo
Files:
 013e7b88024fb63e7dbe22f4453b580a 2200 gnome optional 
gnome-shell-extension-weather_121-1.dsc
 bf935124b538bcfb04f0a570a69ec227 171925 gnome optional 
gnome-shell-extension-weather_121.orig.tar.bz2
 0b81722de5474dba2ded5e04c52c7587 5684 gnome optional 
gnome-shell-extension-weather_121-1.debian.tar.xz
 ea276acb6789f7c424027dfcfb7f3a04 8268 gnome optional 

Bug#1041583: marked as done (gnome-shell-extension-weather: needs update for GNOME Shell 44)

[Debian Bug Tracking System]

Your message dated Sat, 02 Sep 2023 22:49:00 +
with message-id 
and subject line Bug#1041583: fixed in gnome-shell-extension-weather 121-1
has caused the Debian Bug report #1041583,
regarding gnome-shell-extension-weather: needs update for GNOME Shell 44
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.)


-- 
1041583: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1041583
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gnome-shell-extension-weather
Version: 119-1
Severity: important
Tags: trixie sid
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: gnome-shell-44

This extension has not been checked for compatibility with GNOME Shell
44. Depending how compatible it is, it will either need an update to
its metadata.json and debian/control to declare compatibility with the
new version, or code changes to adapt it to the new Shell version.

If not updated, it will have to be removed from testing for the GNOME
Shell 44 transition (I don't know when that will be). This bug will be
raised to serious severity when the transition is ready to go ahead.

If a new upstream version is compatible with Shell 44 but not 43,
please upload to experimental for now.

Thanks,
smcv
--- End Message ---
--- Begin Message ---
Source: gnome-shell-extension-weather
Source-Version: 121-1
Done: Jeremy Bícha 

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

Debian distribution maintenance software
pp.
Jeremy Bícha  (supplier of updated 
gnome-shell-extension-weather 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: Sat, 02 Sep 2023 18:30:58 -0400
Source: gnome-shell-extension-weather
Built-For-Profiles: noudeb
Architecture: source
Version: 121-1
Distribution: unstable
Urgency: high
Maintainer: Debian GNOME Maintainers 

Changed-By: Jeremy Bícha 
Closes: 1018285 1038412 1041583
Changes:
 gnome-shell-extension-weather (121-1) unstable; urgency=high
 .
   [ Jeremy Bícha ]
   * New upstream release (Closes: #1018285, #1038412, #1041583)
   * Bump compatible GNOME Shell versions per metadata.json
 .
   [ Debian Janitor ]
   * Add debian/upstream/metadata
   * Update standards version to 4.6.2, no changes needed
Checksums-Sha1:
 b313b153a3d3cf5cec7d48d4da77f44189c48a9e 2200 
gnome-shell-extension-weather_121-1.dsc
 389ebc6915c28535063602daba5d56295be7ed3c 171925 
gnome-shell-extension-weather_121.orig.tar.bz2
 5ed182a0aa6ab8cc057ee66973ae1cdb5a62b4ca 5684 
gnome-shell-extension-weather_121-1.debian.tar.xz
 bb2f686f3e868f6c1a7dcea687a24530a80c4435 8268 
gnome-shell-extension-weather_121-1_source.buildinfo
Checksums-Sha256:
 e32b4996cd2f807450b958302f613b12f84572df7af9db52614e9670a3be7c48 2200 
gnome-shell-extension-weather_121-1.dsc
 a14a056f98010e8e8234b803dc9b576693dcd47645a688dd34597763f4c12c79 171925 
gnome-shell-extension-weather_121.orig.tar.bz2
 ae320e60ad496100d139436534bb3a6be3fc5b5d73f3f616629faa9266cc1be4 5684 
gnome-shell-extension-weather_121-1.debian.tar.xz
 6b83b94621fc397d42c884e99db9e8fad83f1a26c4b817df5d477af74f854092 8268 
gnome-shell-extension-weather_121-1_source.buildinfo
Files:
 013e7b88024fb63e7dbe22f4453b580a 2200 gnome optional 
gnome-shell-extension-weather_121-1.dsc
 bf935124b538bcfb04f0a570a69ec227 171925 gnome optional 
gnome-shell-extension-weather_121.orig.tar.bz2
 0b81722de5474dba2ded5e04c52c7587 5684 gnome optional 
gnome-shell-extension-weather_121-1.debian.tar.xz
 ea276acb6789f7c424027dfcfb7f3a04 8268 gnome optional 
gnome-shell-extension-weather_121-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEETQvhLw5HdtiqzpaW5mx3Wuv+bH0FAmTzt9cACgkQ5mx3Wuv+
bH2THQ/+J7ST3jzI26VMjPWWpHsxk6qANE8h//sf01Rbn2vtxx/vgvGNuX5++RgK
9Ax4I2brWZZ3RbASFpyNvsBtVPFkftjuoe+iWFyRTI8Zd4AJjXOxtMSYifNI2gKi
p364sLbAE/Mt5NcTwTfAvqSE49P2U6GzTccE8Pz7a99XddqzU1pc9y2/K5b9v/SS
QmBqfmnx6ayq6yz5glc8PxYxpUYRcouQ6tJ3PY5xFm6Kmwch3PMWeKQWBHSe8KAB
GLp6tBJVWdSBS2+6VGdydnL8GAHRk34108PUbjyru9RWU8BRgF51x9Efrmyrmzhg
DBbBx94ugvvT2592hewZcfxKqzC3bjt4HMHHv3+783bqGJ/HWICb6Id/MJu6gvvs

Bug#1041583: marked as done (gnome-shell-extension-weather: needs update for GNOME Shell 44)

[Debian Bug Tracking System]

Your message dated Sat, 02 Sep 2023 22:49:00 +
with message-id 
and subject line Bug#1038412: fixed in gnome-shell-extension-weather 121-1
has caused the Debian Bug report #1038412,
regarding gnome-shell-extension-weather: needs update for GNOME Shell 44
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.)


-- 
1038412: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1038412
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gnome-shell-extension-weather
Version: 119-1
Severity: important
Tags: trixie sid
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: gnome-shell-44

This extension has not been checked for compatibility with GNOME Shell
44. Depending how compatible it is, it will either need an update to
its metadata.json and debian/control to declare compatibility with the
new version, or code changes to adapt it to the new Shell version.

If not updated, it will have to be removed from testing for the GNOME
Shell 44 transition (I don't know when that will be). This bug will be
raised to serious severity when the transition is ready to go ahead.

If a new upstream version is compatible with Shell 44 but not 43,
please upload to experimental for now.

Thanks,
smcv
--- End Message ---
--- Begin Message ---
Source: gnome-shell-extension-weather
Source-Version: 121-1
Done: Jeremy Bícha 

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

Debian distribution maintenance software
pp.
Jeremy Bícha  (supplier of updated 
gnome-shell-extension-weather 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: Sat, 02 Sep 2023 18:30:58 -0400
Source: gnome-shell-extension-weather
Built-For-Profiles: noudeb
Architecture: source
Version: 121-1
Distribution: unstable
Urgency: high
Maintainer: Debian GNOME Maintainers 

Changed-By: Jeremy Bícha 
Closes: 1018285 1038412 1041583
Changes:
 gnome-shell-extension-weather (121-1) unstable; urgency=high
 .
   [ Jeremy Bícha ]
   * New upstream release (Closes: #1018285, #1038412, #1041583)
   * Bump compatible GNOME Shell versions per metadata.json
 .
   [ Debian Janitor ]
   * Add debian/upstream/metadata
   * Update standards version to 4.6.2, no changes needed
Checksums-Sha1:
 b313b153a3d3cf5cec7d48d4da77f44189c48a9e 2200 
gnome-shell-extension-weather_121-1.dsc
 389ebc6915c28535063602daba5d56295be7ed3c 171925 
gnome-shell-extension-weather_121.orig.tar.bz2
 5ed182a0aa6ab8cc057ee66973ae1cdb5a62b4ca 5684 
gnome-shell-extension-weather_121-1.debian.tar.xz
 bb2f686f3e868f6c1a7dcea687a24530a80c4435 8268 
gnome-shell-extension-weather_121-1_source.buildinfo
Checksums-Sha256:
 e32b4996cd2f807450b958302f613b12f84572df7af9db52614e9670a3be7c48 2200 
gnome-shell-extension-weather_121-1.dsc
 a14a056f98010e8e8234b803dc9b576693dcd47645a688dd34597763f4c12c79 171925 
gnome-shell-extension-weather_121.orig.tar.bz2
 ae320e60ad496100d139436534bb3a6be3fc5b5d73f3f616629faa9266cc1be4 5684 
gnome-shell-extension-weather_121-1.debian.tar.xz
 6b83b94621fc397d42c884e99db9e8fad83f1a26c4b817df5d477af74f854092 8268 
gnome-shell-extension-weather_121-1_source.buildinfo
Files:
 013e7b88024fb63e7dbe22f4453b580a 2200 gnome optional 
gnome-shell-extension-weather_121-1.dsc
 bf935124b538bcfb04f0a570a69ec227 171925 gnome optional 
gnome-shell-extension-weather_121.orig.tar.bz2
 0b81722de5474dba2ded5e04c52c7587 5684 gnome optional 
gnome-shell-extension-weather_121-1.debian.tar.xz
 ea276acb6789f7c424027dfcfb7f3a04 8268 gnome optional 
gnome-shell-extension-weather_121-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEETQvhLw5HdtiqzpaW5mx3Wuv+bH0FAmTzt9cACgkQ5mx3Wuv+
bH2THQ/+J7ST3jzI26VMjPWWpHsxk6qANE8h//sf01Rbn2vtxx/vgvGNuX5++RgK
9Ax4I2brWZZ3RbASFpyNvsBtVPFkftjuoe+iWFyRTI8Zd4AJjXOxtMSYifNI2gKi
p364sLbAE/Mt5NcTwTfAvqSE49P2U6GzTccE8Pz7a99XddqzU1pc9y2/K5b9v/SS
QmBqfmnx6ayq6yz5glc8PxYxpUYRcouQ6tJ3PY5xFm6Kmwch3PMWeKQWBHSe8KAB
GLp6tBJVWdSBS2+6VGdydnL8GAHRk34108PUbjyru9RWU8BRgF51x9Efrmyrmzhg
DBbBx94ugvvT2592hewZcfxKqzC3bjt4HMHHv3+783bqGJ/HWICb6Id/MJu6gvvs

Bug#1038412: marked as done (gnome-shell-extension-weather: Update to 121 to support GNOME 44)

[Debian Bug Tracking System]

Your message dated Sat, 02 Sep 2023 22:49:00 +
with message-id 
and subject line Bug#1038412: fixed in gnome-shell-extension-weather 121-1
has caused the Debian Bug report #1038412,
regarding gnome-shell-extension-weather: Update to 121 to support GNOME 44
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.)


-- 
1038412: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1038412
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gnome-shell-extension-weather
Version: 119-1
Severity: normal
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: gnome-shell-44

Dear Maintainer,

Please update to 121 to support GNOME 44.

Best,
Amr


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

Kernel: Linux 6.1.0-9-amd64 (SMP w/8 CPU threads; PREEMPT)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.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 gnome-shell-extension-weather depends on:
ii  ca-certificates  20230311
ii  dconf-gsettings-backend [gsettings-backend]  0.40.0-4
ii  gir1.2-clutter-1.0   1.26.4+dfsg-4
ii  gir1.2-glib-2.0  1.74.0-3
ii  gir1.2-gtk-3.0   3.24.37-2
ii  gir1.2-soup-3.0  3.2.2-2
ii  gnome-shell  43.6-1

Versions of packages gnome-shell-extension-weather recommends:
ii  gnome-tweaks  42~beta-4

gnome-shell-extension-weather suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: gnome-shell-extension-weather
Source-Version: 121-1
Done: Jeremy Bícha 

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

Debian distribution maintenance software
pp.
Jeremy Bícha  (supplier of updated 
gnome-shell-extension-weather 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: Sat, 02 Sep 2023 18:30:58 -0400
Source: gnome-shell-extension-weather
Built-For-Profiles: noudeb
Architecture: source
Version: 121-1
Distribution: unstable
Urgency: high
Maintainer: Debian GNOME Maintainers 

Changed-By: Jeremy Bícha 
Closes: 1018285 1038412 1041583
Changes:
 gnome-shell-extension-weather (121-1) unstable; urgency=high
 .
   [ Jeremy Bícha ]
   * New upstream release (Closes: #1018285, #1038412, #1041583)
   * Bump compatible GNOME Shell versions per metadata.json
 .
   [ Debian Janitor ]
   * Add debian/upstream/metadata
   * Update standards version to 4.6.2, no changes needed
Checksums-Sha1:
 b313b153a3d3cf5cec7d48d4da77f44189c48a9e 2200 
gnome-shell-extension-weather_121-1.dsc
 389ebc6915c28535063602daba5d56295be7ed3c 171925 
gnome-shell-extension-weather_121.orig.tar.bz2
 5ed182a0aa6ab8cc057ee66973ae1cdb5a62b4ca 5684 
gnome-shell-extension-weather_121-1.debian.tar.xz
 bb2f686f3e868f6c1a7dcea687a24530a80c4435 8268 
gnome-shell-extension-weather_121-1_source.buildinfo
Checksums-Sha256:
 e32b4996cd2f807450b958302f613b12f84572df7af9db52614e9670a3be7c48 2200 
gnome-shell-extension-weather_121-1.dsc
 a14a056f98010e8e8234b803dc9b576693dcd47645a688dd34597763f4c12c79 171925 
gnome-shell-extension-weather_121.orig.tar.bz2
 ae320e60ad496100d139436534bb3a6be3fc5b5d73f3f616629faa9266cc1be4 5684 
gnome-shell-extension-weather_121-1.debian.tar.xz
 6b83b94621fc397d42c884e99db9e8fad83f1a26c4b817df5d477af74f854092 8268 
gnome-shell-extension-weather_121-1_source.buildinfo
Files:
 013e7b88024fb63e7dbe22f4453b580a 2200 gnome optional 
gnome-shell-extension-weather_121-1.dsc
 bf935124b538bcfb04f0a570a69ec227 171925 gnome optional 
gnome-shell-extension-weather_121.orig.tar.bz2
 0b81722de5474dba2ded5e04c52c7587 5684 gnome optional 
gnome-shell-extension-weather_121-1.debian.tar.xz
 ea276acb6789f7c424027dfcfb7f3a04 8268 gnome optional 

Bug#1051112: planetblupi: FTBFS: /usr/bin/ld: /usr/lib/riscv64-linux-gnu/libSDL_kitchensink.so: undefined reference to `av_register_all'

[Aurelien Jarno]

Source: planetblupi
Version: 1.14.2-3
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)

Dear maintainer,

planetblupi fails to build from source. From my build log on amd64:

| [100%] Linking CXX executable planetblupi
| /usr/bin/cmake -E cmake_link_script CMakeFiles/planetblupi.dir/link.txt 
--verbose=1
| /usr/bin/c++ -g -O2 -ffile-prefix-map=/<>=. 
-fstack-protector-strong -fstack-clash-protection -Wformat 
-Werror=format-security -fcf-protection -Wdate-time -D_FORTIFY_SOURCE=2 -Wall 
-std=c++11 -L/usr/lib -Wl,-z,relro -rdynamic 
CMakeFiles/planetblupi.dir/src/action.cxx.o 
CMakeFiles/planetblupi.dir/src/blupi.cxx.o 
CMakeFiles/planetblupi.dir/src/button.cxx.o 
CMakeFiles/planetblupi.dir/src/decblupi.cxx.o 
CMakeFiles/planetblupi.dir/src/decgoal.cxx.o 
CMakeFiles/planetblupi.dir/src/decio.cxx.o 
CMakeFiles/planetblupi.dir/src/decmap.cxx.o 
CMakeFiles/planetblupi.dir/src/decmove.cxx.o 
CMakeFiles/planetblupi.dir/src/decor.cxx.o 
CMakeFiles/planetblupi.dir/src/decstat.cxx.o 
CMakeFiles/planetblupi.dir/src/display.cxx.o 
CMakeFiles/planetblupi.dir/src/event.cxx.o 
CMakeFiles/planetblupi.dir/src/fifo.cxx.o 
CMakeFiles/planetblupi.dir/src/fix.cxx.o 
CMakeFiles/planetblupi.dir/src/fog.cxx.o 
CMakeFiles/planetblupi.dir/src/menu.cxx.o 
CMakeFiles/planetblupi.dir/src/misc.cxx.o 
CMakeFiles/planetblupi.dir/src/movie.cxx.o 
CMakeFiles/planetblupi.dir/src/obstacle.cxx.o 
CMakeFiles/planetblupi.dir/src/path.cxx.o 
CMakeFiles/planetblupi.dir/src/pixmap.cxx.o 
CMakeFiles/planetblupi.dir/src/platform/platform_sdl.cxx.o 
CMakeFiles/planetblupi.dir/src/progress.cxx.o 
CMakeFiles/planetblupi.dir/src/sound.cxx.o 
CMakeFiles/planetblupi.dir/src/text.cxx.o -o planetblupi  -lSDL2 -lSDL2_mixer 
-lSDL2 -lSDL2_image -lSDL2 -lSDL_kitchensink -lpthread -lSDL2_mixer 
-lSDL2_image -lSDL_kitchensink -lpthread 
| /usr/bin/ld: 
/usr/lib/gcc/x86_64-linux-gnu/13/../../../x86_64-linux-gnu/libSDL_kitchensink.so:
 undefined reference to `av_register_all'
| collect2: error: ld returned 1 exit status
| make[3]: *** [CMakeFiles/planetblupi.dir/build.make:486: planetblupi] Error 1
| make[3]: Leaving directory '/<>/obj-x86_64-linux-gnu'
| make[2]: *** [CMakeFiles/Makefile2:116: CMakeFiles/planetblupi.dir/all] Error 
2
| make[2]: Leaving directory '/<>/obj-x86_64-linux-gnu'
| make[1]: *** [Makefile:139: all] Error 2
| make[1]: Leaving directory '/<>/obj-x86_64-linux-gnu'
| dh_auto_build: error: cd obj-x86_64-linux-gnu && make -j12 "INSTALL=install 
--strip-program=true" VERBOSE=1 returned exit code 2
| make: *** [debian/rules:4: binary-arch] Error 25
| dpkg-buildpackage: error: debian/rules binary-arch subprocess returned exit 
status 2

A full build log on riscv64 is also available:
https://buildd.debian.org/status/fetch.php?pkg=planetblupi=riscv64=1.14.2-3=1693633255=0

Regards
Aurelien 

Bug#1051111: notmuch: FTBFS: 6 tests failed.

[Aurelien Jarno]

Source: notmuch
Version: 0.37-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)

Dear maintainer,

notmuch fails to build from source due to testsuite issues. From my
build log on amd64:
| 
|   make -j12 test "TESTSUITEFLAGS=-j12 --verbose" VERBOSE=1
| make[1]: Entering directory '/<>'
| Use "make V=1" to see the verbose compile lines.
| CC -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong 
-fstack-clash-protection -Wformat -Werror=format-security -fcf-protection 
test/arg-test.o
| CC -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong 
-fstack-clash-protection -Wformat -Werror=format-security -fcf-protection 
test/hex-xcode.o
| CC -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong 
-fstack-clash-protection -Wformat -Werror=format-security -fcf-protection 
test/random-corpus.o
| CC -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong 
-fstack-clash-protection -Wformat -Werror=format-security -fcf-protection 
test/database-test.o
| CC -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong 
-fstack-clash-protection -Wformat -Werror=format-security -fcf-protection 
test/parse-time.o
| CC -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong 
-fstack-clash-protection -Wformat -Werror=format-security -fcf-protection 
test/smtp-dummy.o
| CXX -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong 
-fstack-clash-protection -Wformat -Werror=format-security -fcf-protection 
test/symbol-test.o
| CXX -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong 
-fstack-clash-protection -Wformat -Werror=format-security -fcf-protection 
test/make-db-version.o
| CXX -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong 
-fstack-clash-protection -Wformat -Werror=format-security -fcf-protection 
test/ghost-report.o
| CC -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong 
-fstack-clash-protection -Wformat -Werror=format-security -fcf-protection 
test/message-id-parse.o
| CC test/arg-test
| CC test/parse-time
| CC test/smtp-dummy
| CC test/hex-xcode
| CC test/message-id-parse
| CXX test/random-corpus
| CXX test/symbol-test
| CXX test/make-db-version
| CXX test/ghost-report
| Use "make V=1" to see the details for passing and known broken tests.
| INFO: using 2m timeout for tests
| 
| T030-config: Testing "notmuch config"
|  BROKEN Round trip config item with leading spaces
|  BROKEN Round trip config item with leading tab
| 
| T040-setup: Testing "notmuch setup"
|  FAIL   Create a new config interactively
|   --- T040-setup.2.config-with-comments   2023-09-01 08:05:51.105192140 
+
|   +++ T040-setup.2.new-notmuch-config 2023-09-01 08:05:51.105192140 
+
|   @@ -1,7 +1,3 @@
|   -# .notmuch-config - Configuration file for the notmuch mail system
|   -#
|   -# For more information about notmuch, see https://notmuchmail.org
|   -
|# Database configuration
|#
|# The only value supported here is 'path' which should be the top-level
|   @@ -12,7 +8,6 @@
|#
|[database]
|path=/path/to/maildir
|   -
|# User configuration
|#
|# Here is where you can let notmuch know how you would like to be
|   @@ -32,7 +27,6 @@
|name=Test Suite
|primary_email=test.su...@example.com
|other_email=another.su...@example.com
|   -
|# Configuration for "notmuch new"
|#
|# The following options are supported here:
|   @@ -49,7 +43,6 @@
|#
|[new]
|tags=foo;bar;
|   -
|# Search configuration
|#
|# The following option is supported here:
|   @@ -61,7 +54,6 @@
|#
|[search]
|exclude_tags=baz
|   -
|# Maildir compatibility configuration
|#
|# The following option is supported here:
| 
| T050-new: Testing "notmuch new" in several variations
|  BROKEN RFC822 group names are indexed
|  BROKEN Long directory names don't cause rescan
| add_file: A Xapian exception occurred
| A Xapian exception occurred finding/creating a directory: Term too long (> 
245): 
XDDIRENTRY2:zz.
| Note: A fatal error was encountered: A Xapian exception occurred
| add_file: A Xapian exception occurred
| A Xapian exception occurred finding/creating a directory: Term too long (> 
245): 

Bug#1051110: kimageformats: FTBFS: CMake Error at /usr/lib/x86_64-linux-gnu/cmake/Imath/ImathTargets.cmake:115

[Aurelien Jarno]

Source: kimageformats
Version: 5.107.0-3
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)

Dear maintainer,

kimageformats fails to build from source. From my build log on amd64:

| -- Performing Test BSYMBOLICFUNCTIONS_AVAILABLE - Success
| -- Could not set up the appstream test. appstreamcli is missing.
| -- Found PkgConfig: /usr/bin/pkg-config (found version "1.8.1") 
| CMake Error at /usr/lib/x86_64-linux-gnu/cmake/Imath/ImathTargets.cmake:115 
(message):
|   The imported target "Imath::PyImath_Python3_11" references the file
| 
|  "/usr/lib/x86_64-linux-gnu/libPyImath_Python3_11-3_1.so.29.8.0"
| 
|   but this file does not exist.  Possible reasons include:
| 
|   * The file was deleted, renamed, or moved to another location.
| 
|   * An install or uninstall procedure did not complete successfully.
| 
|   * The installation package was faulty and contained
| 
|  "/usr/lib/x86_64-linux-gnu/cmake/Imath/ImathTargets.cmake"
| 
|   but not all the files it references.
| 
| Call Stack (most recent call first):
|   /usr/lib/x86_64-linux-gnu/cmake/Imath/ImathConfig.cmake:40 (include)
|   /usr/share/cmake-3.27/Modules/CMakeFindDependencyMacro.cmake:76 
(find_package)
|   /usr/lib/x86_64-linux-gnu/cmake/OpenEXR/OpenEXRConfig.cmake:47 
(find_dependency)
|   CMakeLists.txt:45 (find_package)
| 
| 
| -- Configuring incomplete, errors occurred!

A full build log on riscv64 is also available:
https://buildd.debian.org/status/fetch.php?pkg=kimageformats=riscv64=5.107.0-3=1693586471=0

It seems there is a missing build-dependency on python3-imath.

Regards
Aurelien

Bug#1032584: marked as done (xdg-desktop-portal-gnome: 44 causes long delay in portal apps for non-GNOME desktops)

[Debian Bug Tracking System]

Your message dated Sat, 02 Sep 2023 21:28:18 +
with message-id 
and subject line Bug#1032584: fixed in xdg-desktop-portal-gnome 44.2-2
has caused the Debian Bug report #1032584,
regarding xdg-desktop-portal-gnome: 44 causes long delay in portal apps for 
non-GNOME desktops
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.)


-- 
1032584: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1032584
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: xdg-desktop-portal-gnome
Version: 44~beta-1
Severity: serious
Control: forwarded -1
https://gitlab.gnome.org/GNOME/xdg-desktop-portal-gnome/-/issues/74

If xdg-desktop-portal-gnome 44~beta-1 is installed and a non-GNOME
desktop is used (like MATE), the first time trying to use something
like the file chooser in a portal-confined app will do nothing until
the systemd user service times out (90 seconds??). Afterwards, the
file chooser works normally.

In Debian (and Ubuntu), it's not expected that
xdg-desktop-portal-gnome would be installed on a system that does not
have GNOME installed (it is not a dependency of other things).
However, it is easily possible for someone to have multiple desktops
installed on their system and they would experience this bug then.

Thank you,
Jeremy Bícha
--- End Message ---
--- Begin Message ---
Source: xdg-desktop-portal-gnome
Source-Version: 44.2-2
Done: Jeremy Bícha 

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

Debian distribution maintenance software
pp.
Jeremy Bícha  (supplier of updated xdg-desktop-portal-gnome 
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: Sat, 02 Sep 2023 17:01:39 -0400
Source: xdg-desktop-portal-gnome
Built-For-Profiles: noudeb
Architecture: source
Version: 44.2-2
Distribution: unstable
Urgency: medium
Maintainer: Debian GNOME Maintainers 

Changed-By: Jeremy Bícha 
Closes: 1032584
Launchpad-Bugs-Fixed: 1971168 2012341 2013116
Changes:
 xdg-desktop-portal-gnome (44.2-2) unstable; urgency=medium
 .
   * Bump minimum xdg-desktop-portal to 1.17.1 (LP: #2013116) (Closes: #1032584)
   * Release to unstable
 .
 xdg-desktop-portal-gnome (44.2-1) experimental; urgency=medium
 .
   * New upstream release
   * Update standards version to 4.6.2, no changes needed
 .
 xdg-desktop-portal-gnome (44.1-2) experimental; urgency=medium
 .
   * Add patch to send remote file URIs as local FUSE URIs (LP: #1971168)
 .
 xdg-desktop-portal-gnome (44.1-1) experimental; urgency=medium
 .
   * New upstream release
 - Improve handling of non-existing files on the filechooser portal
 - Minor debugging improvements to the backgrounds portal
 - More precise initialization timing
   (https://gitlab.gnome.org/GNOME/xdg-desktop-portal-gnome/-/issues/79)
 - Fix duplicate monitor and window streams (LP: #2012341)
   (https://gitlab.gnome.org/GNOME/xdg-desktop-portal-gnome/-/issues/76)
 - Translation updates
   * Drop screencast-Duplicate-monitor-and-window-stream-info.patch,
 included in the 44.1 upstream release.
 .
 xdg-desktop-portal-gnome (44.0-1) experimental; urgency=medium
 .
   [ Matthias Geiger ]
   * New upstream release
 - Grant restore permission to transient mode by default
 - Translation updates
 .
   [ Iain Lane ]
   * d/p/screencast-Duplicate-monitor-and-window-stream-info.patch:
 Cherry-pick.  Fix use-after-free crash when window list changes between
 being shown and the user making their selection. (LP: #2012341)
 .
 xdg-desktop-portal-gnome (44~beta-1) experimental; urgency=medium
 .
   * New upstream release
   * debian/control.in: Bump minimum meson
Checksums-Sha1:
 4701b89a68939a04e1835753991cc48a0357ef11 2482 
xdg-desktop-portal-gnome_44.2-2.dsc
 fa29147232dde59caee95f01bbfd554136a97511 5960 
xdg-desktop-portal-gnome_44.2-2.debian.tar.xz
 8aadda04c2bbc41605c2077063fd58da907b951c 17376 
xdg-desktop-portal-gnome_44.2-2_source.buildinfo
Checksums-Sha256:
 dd9b4cccf422f322260664caeb3212aba7d471b7be8f20295ad6e10374ddf095 2482 

Bug#1050421: marked as done (gnome-shell-extension-no-annoyance: needs update for GNOME Shell 44)

[Debian Bug Tracking System]

Your message dated Sat, 02 Sep 2023 21:22:57 +
with message-id 
and subject line Bug#1050421: fixed in gnome-shell-extension-no-annoyance 
0+20220925-c6804a4-3.1
has caused the Debian Bug report #1050421,
regarding gnome-shell-extension-no-annoyance: needs update for GNOME Shell 44
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.)


-- 
1050421: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1050421
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gnome-shell-extension-no-annoyance
Version: 0+20220925-c6804a4-3
Severity: serious
Tags: trixie sid
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: gnome-shell-44
Control: forwarded -1 https://github.com/sindex/no-annoyance/issues/11

This extension has not been checked for compatibility with GNOME Shell
44. Depending how compatible it is, it will either need an update to
its metadata.json and debian/control to declare compatibility with the
new version, or code changes to adapt it to the new Shell version.

Because GNOME Shell 44 is migrating to Testing, this extension will
have to be removed from testing for the GNOME Shell 44 transition now.

Please see the upstream bug report which suggests a possible path
forward for this extension.

Also, please do like other GNOME Shell extensions and add strict upper
and lower Depends against gnome-shell versions the package is
compatible with according to its metadata.json. That would allow users
to automatically see that installing a new GNOME Shell version
(perhaps from experimental) would break their packaged extensions that
aren't yet compatible. For instance, this matches the current
metadata.json:

gnome-shell (>= 40~),
gnome-shell (<< 44~),

Thank you,
Jeremy Bícha
--- End Message ---
--- Begin Message ---
Source: gnome-shell-extension-no-annoyance
Source-Version: 0+20220925-c6804a4-3.1
Done: Jeremy Bícha 

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

Debian distribution maintenance software
pp.
Jeremy Bícha  (supplier of updated 
gnome-shell-extension-no-annoyance 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: Sat, 02 Sep 2023 15:56:09 -0400
Source: gnome-shell-extension-no-annoyance
Built-For-Profiles: noudeb
Architecture: source
Version: 0+20220925-c6804a4-3.1
Distribution: unstable
Urgency: high
Maintainer: Andres Salomon 
Changed-By: Jeremy Bícha 
Closes: 1041576 1050421
Changes:
 gnome-shell-extension-no-annoyance (0+20220925-c6804a4-3.1) unstable; 
urgency=high
 .
   * Non-maintainer upload
   * Add patch to declare compatible with GNOME Shell 44
 (Closes: #1050421, #1041576)
   * debian/control: Set maximum GNOME Shell version to 44
Checksums-Sha1:
 d7c034e1606013001c4dc07d0f42ffb0d2890e44 2211 
gnome-shell-extension-no-annoyance_0+20220925-c6804a4-3.1.dsc
 a7320b22c3bc7a13579995432e7a22d935b958ee 2508 
gnome-shell-extension-no-annoyance_0+20220925-c6804a4-3.1.debian.tar.xz
 2186a9441201f884ae8ff01229d9b36eef15ca50 7272 
gnome-shell-extension-no-annoyance_0+20220925-c6804a4-3.1_source.buildinfo
Checksums-Sha256:
 829c0ea40555e422412f45bfb22b7df068027401c1921ad81c216d9498be4929 2211 
gnome-shell-extension-no-annoyance_0+20220925-c6804a4-3.1.dsc
 dfdda2e1ba20b0a256698d1ef8e87a5848900c07ef4adad7dc904a983e303a2c 2508 
gnome-shell-extension-no-annoyance_0+20220925-c6804a4-3.1.debian.tar.xz
 5b5f9273009bc18625c385bf32ad347b885480769ea63b5fb4e060c7817b6b42 7272 
gnome-shell-extension-no-annoyance_0+20220925-c6804a4-3.1_source.buildinfo
Files:
 2af72594ccd3a263a25e42615f8e57bf 2211 gnome optional 
gnome-shell-extension-no-annoyance_0+20220925-c6804a4-3.1.dsc
 31c30e61f3be42791860614627019213 2508 gnome optional 
gnome-shell-extension-no-annoyance_0+20220925-c6804a4-3.1.debian.tar.xz
 077ae3b1fdbf6a1d4c5ed116e54bd8fc 7272 gnome optional 
gnome-shell-extension-no-annoyance_0+20220925-c6804a4-3.1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEETQvhLw5HdtiqzpaW5mx3Wuv+bH0FAmTznwgACgkQ5mx3Wuv+

Bug#1051107: marked as done (cog: FTBFS: ERROR: Dependency "epoxy" not found, tried pkgconfig)

[Debian Bug Tracking System]

Your message dated Sat, 02 Sep 2023 21:19:16 +
with message-id 
and subject line Bug#1051107: fixed in cog 0.18.0-3
has caused the Debian Bug report #1051107,
regarding cog: FTBFS: ERROR: Dependency "epoxy" not found, tried pkgconfig
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.)


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

Dear maintainer,

cog fails to build from source. From my build log on amd64:

| Run-time dependency libsoup-3.0 found: YES 3.4.2
| Run-time dependency wpe-1.0 found: YES 1.14.0
| Run-time dependency manette-0.2 found: YES 0.2.6
| Configuring cog-config.h using configuration
| Run-time dependency wpebackend-fdo-1.0 found: YES 1.14.2
| Run-time dependency epoxy found: NO (tried pkgconfig)
| 
| ../platform/common/meson.build:3:4: ERROR: Dependency "epoxy" not found, 
tried pkgconfig
| 
| A full log can be found at 
/<>/obj-x86_64-linux-gnu/meson-logs/meson-log.txt
|   cd obj-x86_64-linux-gnu && tail -v -n \+0 meson-logs/meson-log.txt
| ==> meson-logs/meson-log.txt <==
| Build started at 2023-09-02T20:09:58.358110

...

| Called: `/usr/bin/pkg-config --modversion epoxy` -> 1
| stderr:
| Package epoxy was not found in the pkg-config search path.
| Perhaps you should add the directory containing `epoxy.pc'
| to the PKG_CONFIG_PATH environment variable
| Package 'epoxy', required by 'virtual:world', not found
| ---
| CMake binary for 1 is cached as not found
| Dependency lookup for epoxy with method 'cmake' failed: CMake binary for 
machine 1 not found. Giving up.
| Run-time dependency epoxy found: NO (tried pkgconfig)
| 
| ../platform/common/meson.build:3:4: ERROR: Dependency "epoxy" not found, 
tried pkgconfig
| dh_auto_configure: error: cd obj-x86_64-linux-gnu && 
DEB_PYTHON_INSTALL_LAYOUT=deb LC_ALL=C.UTF-8 meson setup .. 
--wrap-mode=nodownload --buildtype=plain --prefix=/usr --sysconfdir=/etc 
--localstatedir=/var --libdir=lib/x86_64-linux-gnu -Dpython.bytecompile=-1 
returned exit code 1
| make: *** [debian/rules:6: binary-arch] Error 25
| dpkg-buildpackage: error: debian/rules binary-arch subprocess returned exit 
status 2

A full build log on riscv64 is also available:
https://buildd.debian.org/status/fetch.php?pkg=cog=riscv64=0.18.0-2=1693678320=0

Regards
Aurelien
--- End Message ---
--- Begin Message ---
Source: cog
Source-Version: 0.18.0-3
Done: Alberto Garcia 

We believe that the bug you reported is fixed in the latest version of
cog, 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.
Alberto Garcia  (supplier of updated cog 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: Sat, 02 Sep 2023 22:30:44 +0200
Source: cog
Architecture: source
Version: 0.18.0-3
Distribution: unstable
Urgency: medium
Maintainer: Alberto Garcia 
Changed-By: Alberto Garcia 
Closes: 1051107
Changes:
 cog (0.18.0-3) unstable; urgency=medium
 .
   * debian/control:
 - Add build dependency on libepoxy-dev (Closes: #1051107).
Checksums-Sha1:
 2c5b73bf8d112a53cfb7538e584a4b8e7f4c161b 2201 cog_0.18.0-3.dsc
 bbe627209260a6bf7e830ee1339b05c380c99df2 5188 cog_0.18.0-3.debian.tar.xz
 4ecceffb2c7639e9074d0d65f32c720c41d0b284 10368 cog_0.18.0-3_source.buildinfo
Checksums-Sha256:
 22e9544bb2613493cf54471002781ae48c395f8281ec3b9073a99481f5b43c33 2201 
cog_0.18.0-3.dsc
 3743f5e3ea0b5f8dd25fdf2419e3e39efc2478da0a70e7fd6394221c6b4a7466 5188 
cog_0.18.0-3.debian.tar.xz
 4d030624805a4d02a9555624dd2f0275c558a52694fa4b9cd619b4b516896ba2 10368 
cog_0.18.0-3_source.buildinfo
Files:
 1a2f50d416de61a2c3a92aed31097d6a 2201 web optional cog_0.18.0-3.dsc
 348b12f1161f797ca414190f969e8734 5188 web optional cog_0.18.0-3.debian.tar.xz
 f3032f84dc21a69a46d9773d8abc797f 10368 web optional 
cog_0.18.0-3_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEYrwugQBKzlHMYFizAAyEYu0C2AIFAmTznoYACgkQAAyEYu0C

Bug#1032584: marked as done (xdg-desktop-portal-gnome: 44 causes long delay in portal apps for non-GNOME desktops)

[Debian Bug Tracking System]

Your message dated Sat, 02 Sep 2023 20:48:15 +
with message-id 
and subject line Bug#1032584: fixed in xdg-desktop-portal 1.17.2-1
has caused the Debian Bug report #1032584,
regarding xdg-desktop-portal-gnome: 44 causes long delay in portal apps for 
non-GNOME desktops
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.)


-- 
1032584: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1032584
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: xdg-desktop-portal-gnome
Version: 44~beta-1
Severity: serious
Control: forwarded -1
https://gitlab.gnome.org/GNOME/xdg-desktop-portal-gnome/-/issues/74

If xdg-desktop-portal-gnome 44~beta-1 is installed and a non-GNOME
desktop is used (like MATE), the first time trying to use something
like the file chooser in a portal-confined app will do nothing until
the systemd user service times out (90 seconds??). Afterwards, the
file chooser works normally.

In Debian (and Ubuntu), it's not expected that
xdg-desktop-portal-gnome would be installed on a system that does not
have GNOME installed (it is not a dependency of other things).
However, it is easily possible for someone to have multiple desktops
installed on their system and they would experience this bug then.

Thank you,
Jeremy Bícha
--- End Message ---
--- Begin Message ---
Source: xdg-desktop-portal
Source-Version: 1.17.2-1
Done: Simon McVittie 

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

Debian distribution maintenance software
pp.
Simon McVittie  (supplier of updated xdg-desktop-portal 
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: Sat, 02 Sep 2023 10:27:12 +0100
Source: xdg-desktop-portal
Architecture: source
Version: 1.17.2-1
Distribution: unstable
Urgency: medium
Maintainer: Utopia Maintenance Team 

Changed-By: Simon McVittie 
Closes: 1032584
Changes:
 xdg-desktop-portal (1.17.2-1) unstable; urgency=medium
 .
   * New upstream release
   * Release to unstable
 .
 xdg-desktop-portal (1.17.1-1) experimental; urgency=medium
 .
   * New upstream release
 - d/patches: Drop all patches, applied in new release
   * d/control, d/x-d-p.manpages: Build and install portals.conf(5)
   * d/NEWS: Add a NEWS file to direct users to portals.conf(5)
   * d/p/debian/portal-impl-Hard-code-x-d-p-gtk-as-a-last-resort-fallback.patch:
 Add patch to fall back to x-d-p-gtk if nothing better can be found.
 This is a temporary measure to give desktop environment maintainers
 a chance to add a portals.conf(5) for their desktop, and should be
 removed later.
 .
 xdg-desktop-portal (1.17.0-1) experimental; urgency=medium
 .
   * Team upload
   * New upstream release
 - Fixes portal delay with x-d-p-gnome 44 and non-GNOME desktops
   (LP: #2013116) (Closes: #1032584)
   * debian/control: Build-Depend on python3-dbusmock & python3-pytest
 for build tests
   * Drop all patches: applied in new release
   * Cherry-pick 3 bug fixes from upstream repo
Checksums-Sha1:
 10e588cd956325b358160db01dfbf2de8da037d9 2818 xdg-desktop-portal_1.17.2-1.dsc
 636f17cb6670d024c77ecebc60d5f689922e97ae 260332 
xdg-desktop-portal_1.17.2.orig.tar.xz
 1b1febb1c3be2d8e364080e8a6ef76a688dcd9cb 11104 
xdg-desktop-portal_1.17.2-1.debian.tar.xz
 84f98b1298f7f1cf2a2172555e5c1ca7444642f0 12301 
xdg-desktop-portal_1.17.2-1_source.buildinfo
Checksums-Sha256:
 6c55516679eb7470781b5a7309b6e775a7b60e31b2ec10a632f8c0abf0ea55d7 2818 
xdg-desktop-portal_1.17.2-1.dsc
 1e861eb991e60e56b06c64dc03284c02f9913f9a426d8955f8d529ff8f3f6d96 260332 
xdg-desktop-portal_1.17.2.orig.tar.xz
 871c36fee91f26934871f014dbc1030af514d19888613858b6ea314358e481b4 11104 
xdg-desktop-portal_1.17.2-1.debian.tar.xz
 15f2946b064d0fae730a0b597a3212d7464ef6dd179b75e2b5b3d13750e7f98b 12301 
xdg-desktop-portal_1.17.2-1_source.buildinfo
Files:
 434d115583336261eea006c5186e0ce4 2818 admin optional 
xdg-desktop-portal_1.17.2-1.dsc
 71e149cc205be79362fc07b4ca235411 260332 admin optional 
xdg-desktop-portal_1.17.2.orig.tar.xz
 2df606bfd0eef7079298fc259058a438 11104 

Bug#1051109: gtkpod: Intent to request removal from Debian

[Jeremy Bícha]

Source: gtkpod
Version: 2.1.5-10
Severity: serious

I intend to request removal of gtkpod from Debian soon. I no longer
wish for Anjuta to be included in Debian; there are much better
alternatives such as GNOME Builder. However, gtkpod uses libanjuta so
gtkpod is interfering with my being able to remove Anjuta from Debian.

Here are a list of select important bugs:
https://bugs.debian.org/993375
https://bugs.debian.org/1018127
https://bugs.debian.org/1018853

Thank you,
Jeremy Bícha

Bug#1051108: anjuta: FTBFS: 1 failed unexpectedly

[Aurelien Jarno]

Source: anjuta
Version: 2:3.34.0-8
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)

Dear maintainer,

anjuta fails to build from source. From my build log on amd64:

| x - created directory gnucash/src/gnome-utils/test.
| x - extracting gnucash/src/gnome-utils/test/Makefile.am (text)
| x - removed lock directory _sh32349.
| ./gnucash.at:6: $abs_builddir/../projectparser --no-id -o output load gnucash 
\
|list
| 
/<>/plugins/am-project/tests/testsuite.dir/at-groups/10/test-source:
 line 1862: 2401173 Bus error   (core dumped) ( $at_check_trace; 
$abs_builddir/../projectparser --no-id -o output load empty12 move empty13 set 
0:2 instdir 'bindir' list save ) >> "$at_stdout" 2>> "$at_stderr" 5>&-
| stderr:
| stdout:
| ./properties.at:488: exit code was 135, expected 0
| 10. properties.at:1:  FAILED (properties.at:488)
| stderr:
| stdout:
| ./gnucash.at:8: diff -b output $srcdir/gnucash.lst
| 19. gnucash.at:1:  ok
| 
| ## - ##
| ## Test results. ##
| ## - ##
| 
| ERROR: All 19 tests were run,
| 1 failed unexpectedly.
| ## -- ##
| ## testsuite.log was created. ##
| ## -- ##
| 
| Please send `plugins/am-project/tests/testsuite.log' and all information you 
think might help:
| 
|To: 
|Subject: [Anjuta 3.34.0] testsuite: 10 failed
| 
| You may investigate any problem if you feel able to do so, in which
| case the test suite provides a good starting point.  Its output may
| be found below `plugins/am-project/tests/testsuite.dir'.
| 
| make[5]: *** [Makefile:636: check-local] Error 1
| make[5]: Leaving directory '/<>/plugins/am-project/tests'
| make[4]: *** [Makefile:498: check-am] Error 2
| make[4]: Leaving directory '/<>/plugins/am-project/tests'
| make[3]: *** [Makefile:1212: check-recursive] Error 1
| make[3]: Leaving directory '/<>/plugins/am-project'
| make[2]: *** [Makefile:527: check-recursive] Error 1
| make[2]: Leaving directory '/<>/plugins'
| make[1]: *** [Makefile:699: check-recursive] Error 1
| make[1]: Leaving directory '/<>'
| dh_auto_test: error: make -j12 check "TESTSUITEFLAGS=-j12 --verbose" 
VERBOSE=1 returned exit code 2
| make: *** [debian/rules:12: build-arch] Error 25
| dpkg-buildpackage: error: debian/rules build-arch subprocess returned exit 
status 2

A full build log on riscv64 is also available:
https://buildd.debian.org/status/fetch.php?pkg=anjuta=riscv64=2%3A3.34.0-8=1693376704=0

Regards
Aurelien

Bug#1051107: cog: FTBFS: ERROR: Dependency "epoxy" not found, tried pkgconfig

[Aurelien Jarno]

Source: cog
Version: 0.18.0-2
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)

Dear maintainer,

cog fails to build from source. From my build log on amd64:

| Run-time dependency libsoup-3.0 found: YES 3.4.2
| Run-time dependency wpe-1.0 found: YES 1.14.0
| Run-time dependency manette-0.2 found: YES 0.2.6
| Configuring cog-config.h using configuration
| Run-time dependency wpebackend-fdo-1.0 found: YES 1.14.2
| Run-time dependency epoxy found: NO (tried pkgconfig)
| 
| ../platform/common/meson.build:3:4: ERROR: Dependency "epoxy" not found, 
tried pkgconfig
| 
| A full log can be found at 
/<>/obj-x86_64-linux-gnu/meson-logs/meson-log.txt
|   cd obj-x86_64-linux-gnu && tail -v -n \+0 meson-logs/meson-log.txt
| ==> meson-logs/meson-log.txt <==
| Build started at 2023-09-02T20:09:58.358110

...

| Called: `/usr/bin/pkg-config --modversion epoxy` -> 1
| stderr:
| Package epoxy was not found in the pkg-config search path.
| Perhaps you should add the directory containing `epoxy.pc'
| to the PKG_CONFIG_PATH environment variable
| Package 'epoxy', required by 'virtual:world', not found
| ---
| CMake binary for 1 is cached as not found
| Dependency lookup for epoxy with method 'cmake' failed: CMake binary for 
machine 1 not found. Giving up.
| Run-time dependency epoxy found: NO (tried pkgconfig)
| 
| ../platform/common/meson.build:3:4: ERROR: Dependency "epoxy" not found, 
tried pkgconfig
| dh_auto_configure: error: cd obj-x86_64-linux-gnu && 
DEB_PYTHON_INSTALL_LAYOUT=deb LC_ALL=C.UTF-8 meson setup .. 
--wrap-mode=nodownload --buildtype=plain --prefix=/usr --sysconfdir=/etc 
--localstatedir=/var --libdir=lib/x86_64-linux-gnu -Dpython.bytecompile=-1 
returned exit code 1
| make: *** [debian/rules:6: binary-arch] Error 25
| dpkg-buildpackage: error: debian/rules binary-arch subprocess returned exit 
status 2

A full build log on riscv64 is also available:
https://buildd.debian.org/status/fetch.php?pkg=cog=riscv64=0.18.0-2=1693678320=0

Regards
Aurelien

Bug#1041567: marked as done (gnome-shell-extension-arc-menu: needs update for GNOME Shell 44)

[Debian Bug Tracking System]

Your message dated Sat, 2 Sep 2023 15:44:45 -0400
with message-id 

and subject line Re: gnome-shell-extension-arc-menu: needs update for GNOME 
Shell 44
has caused the Debian Bug report #1041567,
regarding gnome-shell-extension-arc-menu: needs update for GNOME Shell 44
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.)


-- 
1041567: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1041567
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gnome-shell-extension-arc-menu
Version: 49+forkv29-3
Severity: important
Tags: trixie sid
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: gnome-shell-44

This extension has not been checked for compatibility with GNOME Shell
44. Depending how compatible it is, it will either need an update to
its metadata.json and debian/control to declare compatibility with the
new version, or code changes to adapt it to the new Shell version.

If not updated, it will have to be removed from testing for the GNOME
Shell 44 transition (I don't know when that will be). This bug will be
raised to serious severity when the transition is ready to go ahead.

If a new upstream version is compatible with Shell 43 but not 44,
please upload to experimental for now.

Thanks,
smcv
--- End Message ---
--- Begin Message ---
Version: 49+forkv29-4--- End Message ---

Bug#1051092: marked as done (gir-rust-code-generator: FTBFS: error: failed to select a version for the requirement `toml = "^0.5"`)

[Debian Bug Tracking System]

Your message dated Sat, 02 Sep 2023 19:04:26 +
with message-id 
and subject line Bug#1051092: fixed in gir-rust-code-generator 0.18.1-3
has caused the Debian Bug report #1051092,
regarding gir-rust-code-generator: FTBFS: error: failed to select a version for 
the requirement `toml = "^0.5"`
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.)


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

Dear maintainer,

gir-rust-code-generator fails to build from source. From my build log on
amd64:
| 
| debian cargo wrapper: rust_type, gnu_type: x86_64-unknown-linux-gnu, 
x86_64-linux-gnu
| debian cargo wrapper: running subprocess (['env', 'RUST_BACKTRACE=1', 
'/usr/bin/cargo', '-Zavoid-dev-deps', 'build', '--verbose', '--verbose', 
'-j12', '--target', 'x86_64-unknown-linux-gnu'],) {}
| error: failed to select a version for the requirement `toml = "^0.5"`
| candidate versions found which didn't match: 0.7.6
| location searched: directory source `/<>/debian/cargo_registry` 
(which is replacing registry `crates-io`)
| required by package `gir v0.0.1 (/<>)`
| perhaps a crate was updated and forgotten to be re-vendored?
| dh_auto_test: error: /usr/share/cargo/bin/cargo build returned exit code 101
| make: *** [debian/rules:16: binary-arch] Error 25
| dpkg-buildpackage: error: debian/rules binary-arch subprocess returned exit 
status 2

A full build log on riscv64 is also available:
https://buildd.debian.org/status/fetch.php?pkg=gir-rust-code-generator=riscv64=0.18.1-2=1693535398=0

Regards
Aurelien
--- End Message ---
--- Begin Message ---
Source: gir-rust-code-generator
Source-Version: 0.18.1-3
Done: Jeremy Bícha 

We believe that the bug you reported is fixed in the latest version of
gir-rust-code-generator, 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.
Jeremy Bícha  (supplier of updated gir-rust-code-generator 
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: Sat, 02 Sep 2023 14:53:02 -0400
Source: gir-rust-code-generator
Built-For-Profiles: noudeb
Architecture: source
Version: 0.18.1-3
Distribution: unstable
Urgency: medium
Maintainer: Debian GNOME Maintainers 

Changed-By: Jeremy Bícha 
Closes: 1051092
Changes:
 gir-rust-code-generator (0.18.1-3) unstable; urgency=medium
 .
   * Team upload
   * Update relax-deps.diff for rust-toml 0.7 (Closes: #1051092)
Checksums-Sha1:
 617c6b9dc45fa7c40ae21aab3ce438a5984ea1fd 2462 
gir-rust-code-generator_0.18.1-3.dsc
 0a3554046c291a014d0fd93b2299a18be8e61666 3916 
gir-rust-code-generator_0.18.1-3.debian.tar.xz
 90400087a5539fdcea12f575e53b9460e4dbf54a 8404 
gir-rust-code-generator_0.18.1-3_source.buildinfo
Checksums-Sha256:
 c1a07133ff719bc99267aa8f43dbb9864b09db2637a43f0b9cd173f495680439 2462 
gir-rust-code-generator_0.18.1-3.dsc
 e261e095b5f247dbc5190eba8363898b2a31d552107acc099eb8630ddcb20550 3916 
gir-rust-code-generator_0.18.1-3.debian.tar.xz
 a96021fe62164c685a3977e3dfe7adce90c6b76e806d2e3f7390a39e7bbb3fce 8404 
gir-rust-code-generator_0.18.1-3_source.buildinfo
Files:
 05fefdc0612e27abc9bdc99abca84b31 2462 gnome optional 
gir-rust-code-generator_0.18.1-3.dsc
 1ac47654f3dba822432e83eb88960d59 3916 gnome optional 
gir-rust-code-generator_0.18.1-3.debian.tar.xz
 3c579aef7ade6e20f51320c7fab68dd0 8404 gnome optional 
gir-rust-code-generator_0.18.1-3_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEETQvhLw5HdtiqzpaW5mx3Wuv+bH0FAmTzhMoACgkQ5mx3Wuv+
bH2gXQ/+OA9VX/Y5Z3nAq/eVkcq7Z6lIU4kiubsHe8mTtqYW6iGhjypbfsPvMf8T
E6BpATHSqPx8trtX2hy7Gn2labungjVc0TBoaYcg/mbPmByJ3WzZ3gAwhw0qYQql
uN3hS9+Kxk9vUEgkqY0GBw90ipIdcknVy+kpzmbSgdiX+jRqAeDs9/AFrDP482r3
JuG606DosRdq+v+OaQQIwvYv8P9TtKQh5xUgmHaY3k//pgLz9ria1YaeCwmhxCF6
dNpJ3x36suxVr9J0H+PnhHYPyAvyoPIYgqoRQ85rI2bPYRf8m/737hvfmByrIRce
aHp4qqK9QaesmsRgruArfgx7FOXdAyttzNkG5z94VuNKBb7JLaRgp0P/CJqoQksh

Bug#1043477: marked as done (php8.2: CVE-2023-3823 CVE-2023-3824)

[Debian Bug Tracking System]

Your message dated Sat, 2 Sep 2023 20:54:37 +0200
with message-id 
and subject line [ftpmas...@ftp-master.debian.org: Accepted php8.2 8.2.10-1 
(source) into unstable]
has caused the Debian Bug report #1043477,
regarding php8.2: CVE-2023-3823 CVE-2023-3824
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.)


-- 
1043477: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1043477
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: php8.2
Version: 8.2.7-1
Severity: grave
Tags: security upstream
Justification: user security hole
X-Debbugs-Cc: car...@debian.org, Debian Security Team 
Control: found -1 8.2.7-1~deb12u1

Hi,

The following vulnerabilities were published for php8.2.

CVE-2023-3823[0]:
| In PHP versions 8.0.* before 8.0.30, 8.1.* before 8.1.22, and 8.2.*
| before 8.2.8 various XML functions rely on libxml global state to
| track configuration variables, like whether external entities are
| loaded. This state is assumed to be unchanged unless the user
| explicitly changes it by calling appropriate function. However,
| since the state is process-global, other modules - such
| as ImageMagick - may also use this library within the same process,
| and change that global state for their internal purposes, and leave
| it in a state where external entities loading is enabled. This can
| lead to the situation where external XML is parsed with external
| entities loaded, which can lead to disclosure of any local files
| accessible to PHP. This vulnerable state may persist in the same
| process across many requests, until the process is shut down.


CVE-2023-3824[1]:
| In PHP version 8.0.* before 8.0.30,  8.1.* before 8.1.22, and 8.2.*
| before 8.2.8, when loading phar file, while reading PHAR directory
| entries, insufficient length checking may lead to a stack buffer
| overflow, leading potentially to memory corruption or RCE.


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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2023-3823
https://www.cve.org/CVERecord?id=CVE-2023-3823
[1] https://security-tracker.debian.org/tracker/CVE-2023-3824
https://www.cve.org/CVERecord?id=CVE-2023-3824

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: php8.2
Source-Version: 8.2.10-1

This upload fixes as well #1043477, tracking bug for CVE-2023-3823 and
CVE-2023-3824.

- Forwarded message from Debian FTP Masters 
 -

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 02 Sep 2023 08:31:05 +0200
Source: php8.2
Architecture: source
Version: 8.2.10-1
Distribution: unstable
Urgency: medium
Maintainer: Debian PHP Maintainers 
Changed-By: Ondřej Surý 
Changes:
 php8.2 (8.2.10-1) unstable; urgency=medium
 .
   * New upstream version 8.2.10
   * Enable DTrace on all architectures
Checksums-Sha1:
 9fb1d06aa69fcadbc447f400afbd96368c2dcda6 5694 php8.2_8.2.10-1.dsc
 677c4f2c1091afdedb9455dac77ce2e8efc973c0 12041348 php8.2_8.2.10.orig.tar.xz
 852d4d8ab95c239a927ed2ad0b68822c5dafe5af 858 php8.2_8.2.10.orig.tar.xz.asc
 9231fdcd753025966bc280f3b34cc386373acdfc 69500 php8.2_8.2.10-1.debian.tar.xz
 65a037944703da7079f13300ff6089676ae7d0e9 32858 php8.2_8.2.10-1_amd64.buildinfo
Checksums-Sha256:
 c4a4fcafce9d2323cd0b9f7c17977d56e5db77688dbae27bc53bb07c773048e6 5694 
php8.2_8.2.10-1.dsc
 561dc4acd5386e47f25be76f2c8df6ae854756469159248313bcf276e282fbb3 12041348 
php8.2_8.2.10.orig.tar.xz
 7697adb0dbbc66d3edfa32cdca7dbd2c5d548974e6594eddc91fa23526c22a8c 858 
php8.2_8.2.10.orig.tar.xz.asc
 a8954e3cfa3199b6984511875702da260605c17266f55e951e19fddb4ca11240 69500 
php8.2_8.2.10-1.debian.tar.xz
 b0c6589d8bd3ae0feb7e8a2e55b414b1f3767de0b757410380ce6562f4c9fc74 32858 
php8.2_8.2.10-1_amd64.buildinfo
Files:
 ba4b051ada62d347bd40921bb612a4c3 5694 php optional php8.2_8.2.10-1.dsc
 7cf41ae950f76e031599129f7cac6719 12041348 php optional 
php8.2_8.2.10.orig.tar.xz
 44ea3744a42f39a86235b4efc7026181 858 php optional php8.2_8.2.10.orig.tar.xz.asc
 2e7fdad7613dd249bdf3aa809132ada9 69500 php optional 
php8.2_8.2.10-1.debian.tar.xz
 15d73db1556a5e75cb2064fc9b3455c3 32858 php optional 
php8.2_8.2.10-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQKTBAEBCgB9FiEEw2Gx4wKVQ+vGJel9g3Kkd++uWcIFAmTy6oVfFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEMz
NjFCMUUzMDI5NTQzRUJDNjI1RTk3RDgzNzJBNDc3RUZBRTU5QzIACgkQg3Kkd++u
WcK32hAAlcSes+txDocfhBc1/3b/HEU3/ybU/ifnJkjyWJxPVhytpaKqY2fBVXGv
aPf36viOY1lGP/wd3PAPvGHgxSN8AGXgsvo+Huful2ztyIVyUaTHFhPGzmZ+zMVx

Bug#1043477: [ftpmas...@ftp-master.debian.org: Accepted php8.2 8.2.10-1 (source) into unstable]

[Salvatore Bonaccorso]

Source: php8.2
Source-Version: 8.2.10-1

This upload fixes as well #1043477, tracking bug for CVE-2023-3823 and
CVE-2023-3824.

- Forwarded message from Debian FTP Masters 
 -

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 02 Sep 2023 08:31:05 +0200
Source: php8.2
Architecture: source
Version: 8.2.10-1
Distribution: unstable
Urgency: medium
Maintainer: Debian PHP Maintainers 
Changed-By: Ondřej Surý 
Changes:
 php8.2 (8.2.10-1) unstable; urgency=medium
 .
   * New upstream version 8.2.10
   * Enable DTrace on all architectures
Checksums-Sha1:
 9fb1d06aa69fcadbc447f400afbd96368c2dcda6 5694 php8.2_8.2.10-1.dsc
 677c4f2c1091afdedb9455dac77ce2e8efc973c0 12041348 php8.2_8.2.10.orig.tar.xz
 852d4d8ab95c239a927ed2ad0b68822c5dafe5af 858 php8.2_8.2.10.orig.tar.xz.asc
 9231fdcd753025966bc280f3b34cc386373acdfc 69500 php8.2_8.2.10-1.debian.tar.xz
 65a037944703da7079f13300ff6089676ae7d0e9 32858 php8.2_8.2.10-1_amd64.buildinfo
Checksums-Sha256:
 c4a4fcafce9d2323cd0b9f7c17977d56e5db77688dbae27bc53bb07c773048e6 5694 
php8.2_8.2.10-1.dsc
 561dc4acd5386e47f25be76f2c8df6ae854756469159248313bcf276e282fbb3 12041348 
php8.2_8.2.10.orig.tar.xz
 7697adb0dbbc66d3edfa32cdca7dbd2c5d548974e6594eddc91fa23526c22a8c 858 
php8.2_8.2.10.orig.tar.xz.asc
 a8954e3cfa3199b6984511875702da260605c17266f55e951e19fddb4ca11240 69500 
php8.2_8.2.10-1.debian.tar.xz
 b0c6589d8bd3ae0feb7e8a2e55b414b1f3767de0b757410380ce6562f4c9fc74 32858 
php8.2_8.2.10-1_amd64.buildinfo
Files:
 ba4b051ada62d347bd40921bb612a4c3 5694 php optional php8.2_8.2.10-1.dsc
 7cf41ae950f76e031599129f7cac6719 12041348 php optional 
php8.2_8.2.10.orig.tar.xz
 44ea3744a42f39a86235b4efc7026181 858 php optional php8.2_8.2.10.orig.tar.xz.asc
 2e7fdad7613dd249bdf3aa809132ada9 69500 php optional 
php8.2_8.2.10-1.debian.tar.xz
 15d73db1556a5e75cb2064fc9b3455c3 32858 php optional 
php8.2_8.2.10-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQKTBAEBCgB9FiEEw2Gx4wKVQ+vGJel9g3Kkd++uWcIFAmTy6oVfFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEMz
NjFCMUUzMDI5NTQzRUJDNjI1RTk3RDgzNzJBNDc3RUZBRTU5QzIACgkQg3Kkd++u
WcK32hAAlcSes+txDocfhBc1/3b/HEU3/ybU/ifnJkjyWJxPVhytpaKqY2fBVXGv
aPf36viOY1lGP/wd3PAPvGHgxSN8AGXgsvo+Huful2ztyIVyUaTHFhPGzmZ+zMVx
CvN8hfN+RspUvV5B6klKUMA1vT8g2BryBJL3QbM8KW/mI+AMAPpBd/wEZOD+aIAc
/ri8WBxgCRTQh5NEs5ss7DIRiFmI0dbL41qQ67sej2ETntkFKdmcfGcxlmWENYcL
Zl7gzN/aJnTStXUG9tkvbnZrLLUnd7sOjLjTQvHj3CevHkEZq1xXoYYVd+x59tZQ
85qiWiTo5oVoBWIURKc0MGG8UeqyxX+ylp2oAp2cpqlTe96FBhqRkzzNirwq1M1r
lOhoxuJRuoosGt8nYAN+hv0jYEOj+X/sxcRspM09QN11um9sbeDjczOa49rOW5TN
jcbuPCYg0ftirCx+/Kmfe24AXKVg2xRRPRYvzNYDtwEw4MOmVtYMPtUz9LnGDZj1
lPAABxGT6ft79bm7BIaEOiazU08kujpNbW3hIZXcCsyg2/fTY8LKlHzQ5NlrNlKq
Bi99Sjf3A/C44F+/eCt4J1NfI0ZoZAiOIDGGlVvL5y2uQNNFqW5oh2rN3V2KazfI
chEkhCPzYx0kxeLzsyr1Uu+SzHwH0acDhZesV5ijhjsRtkmfqn0=
=LrF2
-END PGP SIGNATURE-


- End forwarded message -

Bug#1051097: cyrus-imapd: autopkgtest failure because package is not installable

[Jeremy Bícha]

Source: cyrus-imapd
Version: 3.8.0-4
Severity: serious
X-Debbugs-CC: y...@debian.org

The autopkgtest for cyrus-imapd 3.8.0-4 is failing but 3.8.0-3 succeeded.

https://ci.debian.net/packages/c/cyrus-imapd/testing/amd64/

autogpktest log excerpt
=
Setting up cyrus-common (3.8.0-4) ...
 79s You must update cyrus-imapd to at least version 3.2.6-2+deb11u2~
 79s before updating it to version 3.6.x and run it, else your mailboxes
 79s may be corrupted
 79s dpkg: error processing package cyrus-common (--configure):
 79s  installed cyrus-common package post-installation script
subprocess returned error exit status 1
 79s dpkg: dependency problems prevent configuration of cyrus-imapd:
 79s  cyrus-imapd depends on cyrus-common (= 3.8.0-4); however:
 79s   Package cyrus-common is not configured yet.
 79s
 79s dpkg: error processing package cyrus-imapd (--configure):
 79s  dependency problems - leaving unconfigured
 79s dpkg: dependency problems prevent configuration of autopkgtest-satdep:
 79s  autopkgtest-satdep depends on cyrus-imapd; however:
 79s   Package cyrus-imapd is not configured yet.
 79s
 79s dpkg: error processing package autopkgtest-satdep (--configure):
 79s  dependency problems - leaving unconfigured
 79s Processing triggers for libc-bin (2.37-7) ...
 79s Errors were encountered while processing:
 79s  cyrus-common
 79s  cyrus-imapd
 79s  autopkgtest-satdep
 79s E: Sub-process /usr/bin/dpkg returned an error code (1)


Thank you,
Jeremy Bícha

Bug#1051096: nfoview: recommends a non-existent package

[paula]

Package: nfoview
Version: 1.29-2
Severity: serious
X-Debbugs-Cc: paula@cs.email

Dear Maintainer,

nfoview currently Recommends the package fonts-cascadia-code which is
not packaged in stable version of debian. This is a policy violation.

Please fix thank you.

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

Kernel: Linux 6.1.0-11-amd64 (SMP w/2 CPU threads; PREEMPT)
Locale: LANG=C.UTF-8, LC_CTYPE=C.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 nfoview depends on:
ii  gir1.2-gtk-3.0  3.24.37-2
ii  python3 3.11.2-1+b1
ii  python3-gi  3.42.2-3+b1

Versions of packages nfoview recommends:
pn  fonts-cascadia-code  

nfoview suggests no packages.

-- no debconf information

Bug#1051092: gir-rust-code-generator: FTBFS: error: failed to select a version for the requirement `toml = "^0.5"`

[Aurelien Jarno]

Source: gir-rust-code-generator
Version: 0.18.1-2
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)

Dear maintainer,

gir-rust-code-generator fails to build from source. From my build log on
amd64:
| 
| debian cargo wrapper: rust_type, gnu_type: x86_64-unknown-linux-gnu, 
x86_64-linux-gnu
| debian cargo wrapper: running subprocess (['env', 'RUST_BACKTRACE=1', 
'/usr/bin/cargo', '-Zavoid-dev-deps', 'build', '--verbose', '--verbose', 
'-j12', '--target', 'x86_64-unknown-linux-gnu'],) {}
| error: failed to select a version for the requirement `toml = "^0.5"`
| candidate versions found which didn't match: 0.7.6
| location searched: directory source `/<>/debian/cargo_registry` 
(which is replacing registry `crates-io`)
| required by package `gir v0.0.1 (/<>)`
| perhaps a crate was updated and forgotten to be re-vendored?
| dh_auto_test: error: /usr/share/cargo/bin/cargo build returned exit code 101
| make: *** [debian/rules:16: binary-arch] Error 25
| dpkg-buildpackage: error: debian/rules binary-arch subprocess returned exit 
status 2

A full build log on riscv64 is also available:
https://buildd.debian.org/status/fetch.php?pkg=gir-rust-code-generator=riscv64=0.18.1-2=1693535398=0

Regards
Aurelien

Bug#1051091: giara: FTBFS: error: Expected string or translated string

[Aurelien Jarno]

Source: giara
Version: 1.0.1-2
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)

Dear maintainer,

giara fails to build from source. From my build log on amd64:

| [28/29] /usr/bin/blueprint-compiler batch-compile data/. ../data 
../data/ui/comment_box.blp ../data/ui/headerbar.blp 
../data/ui/choice_picker_popover_content.blp ../data/ui/login_view.blp 
../data/ui/headerbar_with_back_and_squeezer.blp ../data/ui/inbox_item_view.blp 
../data/ui/main_ui.blp ../data/ui/post_body.blp 
../data/ui/post_details_headerbar.blp ../data/ui/shortcutsWindow.blp 
../data/ui/image_viewer_window.blp ../data/ui/redditor_heading.blp 
../data/ui/subreddit_heading.blp ../data/ui/subreddit_view_headerbar.blp
| FAILED: data 
| /usr/bin/blueprint-compiler batch-compile data/. ../data 
../data/ui/comment_box.blp ../data/ui/headerbar.blp 
../data/ui/choice_picker_popover_content.blp ../data/ui/login_view.blp 
../data/ui/headerbar_with_back_and_squeezer.blp ../data/ui/inbox_item_view.blp 
../data/ui/main_ui.blp ../data/ui/post_body.blp 
../data/ui/post_details_headerbar.blp ../data/ui/shortcutsWindow.blp 
../data/ui/image_viewer_window.blp ../data/ui/redditor_heading.blp 
../data/ui/subreddit_heading.blp ../data/ui/subreddit_view_headerbar.blp
| error: Expected string or translated string
| at ../data/ui/headerbar.blp line 26 column 24:
|   26 |item { custom: profile; }
|  |   ^
| 
| error: Unexpected tokens
| at ../data/ui/headerbar.blp line 26 column 22:
|   26 |item { custom: profile; }
|  | ^
| 
| 2 errors
| ninja: build stopped: subcommand failed.
| dh_auto_build: error: cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 ninja -j12 -v 
returned exit code 1
| make: *** [debian/rules:7: binary-arch] Error 25
| dpkg-buildpackage: error: debian/rules binary-arch subprocess returned exit 
status 2

A full build log on riscv64 is also available:
https://buildd.debian.org/status/fetch.php?pkg=giara=riscv64=1.0.1-2=1693562930=0

Regards
Aurelien

Bug#1051090: emacsql: FTBFS: 5 unexpected results

[Aurelien Jarno]

Source: emacsql
Version: 3.1.1+ds-1 
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)

Dear maintainer,

emacsql fails to build from source with errors in the testsuite. From my
build log on amd64:

| Ran 24 tests, 19 results as expected, 5 unexpected (2023-09-01 08:04:24+, 
0.351282 sec)
| 
| 5 unexpected results:
|FAILED  emacsql-basic
|FAILED  emacsql-error
|FAILED  emacsql-foreign-key
|FAILED  emacsql-nul-character
|FAILED  emacsql-special-chars
| 
| dh_elpa_test: error: emacs -batch -Q -l package --eval "(add-to-list 
'package-directory-list \"/usr/share/emacs/site-lisp/elpa\")" --eval 
"(add-to-list 'package-directory-list \"/usr/share/emacs/site-lisp/elpa-src\")" 
-f package-initialize -L . -L tests --eval "(unless (and (getenv 
\"AUTOPKGTEST_TMP\") (file-directory-p (getenv \"AUTOPKGTEST_TMP\"))) (setq 
emacsql-sqlite-executable (concat default-directory 
\"sqlite/emacsql-sqlite\")))" -l tests/emacsql-compiler-tests.el -l 
tests/emacsql-external-tests.el --eval \(ert-run-tests-batch-and-exit\) 
returned exit code 1
| make: *** [debian/rules:4: binary-arch] Error 25
| dpkg-buildpackage: error: debian/rules binary-arch subprocess returned exit 
status 2

A full build log on riscv64 is also available:
https://buildd.debian.org/status/fetch.php?pkg=emacsql=riscv64=3.1.1%2Bds-1=1693407418=0

Regards
Aurelien

Bug#1051089: ruby-rails-assets-punycode: Depends on NBS libjs-punycode

[Jeremy Bícha]

Source: ruby-rails-assets-punycode
Version: 2.2.3+dfsg-1
Severity: serious

ruby-rails-assets-punycode depends on libjs-punycode but nothing
builds that package. It used to be provided by the same source
package.

https://salsa.debian.org/ruby-team/ruby-rails-assets-punycode/-/commit/615fdacd

Thank you,
Jeremy Bícha

Bug#1042933: marked as done (octave-statistics autopkg tests fail in unstable on amd64)

[Debian Bug Tracking System]

Your message dated Sat, 02 Sep 2023 14:57:58 +
with message-id 
and subject line Bug#1042933: fixed in octave-statistics 1.6.0-2
has caused the Debian Bug report #1042933,
regarding octave-statistics autopkg tests fail in unstable on amd64
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.)


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

Package: src:octave-statistics
Version: 1.6.0-1
Severity: serious
Tags: sid trixie

octave autopkg tests fail in unstable on amd64 (triggered by gcc-13).

https://ci.debian.net/data/autopkgtest/testing/amd64/o/octave-statistics/36329437/log.gz

Not sure which ones are the regressions, because all failures seem to be marked 
as "known failure".
--- End Message ---
--- Begin Message ---
Source: octave-statistics
Source-Version: 1.6.0-2
Done: Sébastien Villemot 

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

Debian distribution maintenance software
pp.
Sébastien Villemot  (supplier of updated 
octave-statistics 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: Sat, 02 Sep 2023 15:59:18 +0200
Source: octave-statistics
Architecture: source
Version: 1.6.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Octave Group 
Changed-By: Sébastien Villemot 
Closes: 1042933
Changes:
 octave-statistics (1.6.0-2) unstable; urgency=medium
 .
   * test-failures-cameratarget.patch: new patch by Graham Inggs.
 Taken from Ubuntu. Fixes random autopkgtest failures. (Closes: #1042933)
Checksums-Sha1:
 244ab9464fa6c2c7666fbfbafbd3b0a182b77a38 2202 octave-statistics_1.6.0-2.dsc
 bf4ba538fabf5ce09423ce6200902aacf5f119e5 9048 
octave-statistics_1.6.0-2.debian.tar.xz
 7096bc631677b831d1d9294c2f1614a455af9d1f 25635 
octave-statistics_1.6.0-2_source.buildinfo
Checksums-Sha256:
 f8875a480cebf2036ace945500e6c4d9e208e46863b2262674029649eeccd3c3 2202 
octave-statistics_1.6.0-2.dsc
 bba30cabc774ee3fbeb15772e031c33f13e3fe18908d9e7eca02324f5b4ed06a 9048 
octave-statistics_1.6.0-2.debian.tar.xz
 bb470d8057570de399a1af1a8d2f66a42c575da20e5edf06655f2dc50b9a7042 25635 
octave-statistics_1.6.0-2_source.buildinfo
Files:
 c2fc2151afe4d6cd2aadb0767fd353ca 2202 math optional 
octave-statistics_1.6.0-2.dsc
 cfd9c537887ae8ce790637433a8ae0a1 9048 math optional 
octave-statistics_1.6.0-2.debian.tar.xz
 e3708190b23b0c8eeef2bf1e02a07529 25635 math optional 
octave-statistics_1.6.0-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEU5UdlScuDFuCvoxKLOzpNQ7OvkoFAmTzQH4ACgkQLOzpNQ7O
vko8OQ/9FV+L6eec82ciDthlY/KMNuhlwbZmTRGx4RDnfNnsZDckfUPBsZN1Rpmr
JkYKXofVAr/vXBlLNDYEOLAvkjY9kG0O5GB++E8LSASo/8Y2Yp3bUn7fVYk5M0zU
ixrfqmNnoWUHM3wZU3M1CWb3lY8Tcb2KO/D+6Wdai+zJ8yzm3Y5nf8SbmRTuSNmK
Mtu1cqHcb2PxUl440AEu0cJtufBkCBP5hgsvbQPaYWG6fpY4uRaxWIs1lfZ/t7M1
iM3qptZwiIcmnYGZ573w6nLyIArdr10dajEbqu+Lz1yGvLZ6IWKYgXJnf94f7KTY
yW+10oWWG0M/YoHrrd9jMQ2EvRwzAhOwA5A3wIuaAqc7swC6SMEoWExjm/jqRH00
avQiAnvxZaJWCn3p+Lcew2oTsrJ4uEuSZewz9KCMIjEGw+WOL21QBN3LSDLG3cQ5
UczbAzmybszbC0T6ufS8bLczdUwsKuCm5KdevMw4ARKF5IyYz9Z9zKj1HtJtMZCx
B0tO0xvreDpRfvBsUbqhdlM+4GaZqFY3A5LOwBGwMo3nRs1QTF9XS+UBaU9fPJUV
JwlRXbNMeK/BgX+46pCRd6fKTDMuX9hYUtZhweNGxCm+nlVyemMzMvbFRS6Bu8nZ
RgTc+ztMeK0TRWurOh4jlJpfb3vj3HpxYXg6xGNhvrIBAIEXyRM=
=hFIu
-END PGP SIGNATURE End Message ---

Bug#1042747: marked as done (dahdi-dkms: dkms.conf still lists removed pciradio.ko)

[Debian Bug Tracking System]

Your message dated Sat, 02 Sep 2023 14:51:50 +
with message-id 
and subject line Bug#1042747: fixed in dahdi-linux 1:3.1.0+git20230717~dfsg-3
has caused the Debian Bug report #1042747,
regarding dahdi-dkms: dkms.conf still lists removed pciradio.ko
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.)


-- 
1042747: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042747
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: dahdi-dkms
Version: 1:3.1.0+git20230717~dfsg-1
Severity: serious

Buiding the modules fails because pciradio.ko is no longer built, but
still required by dkms.conf:

I: Trying to build dahdi/3.1.0+git20230717 for 6.3.0-2-amd64
Sign command: /usr/lib/linux-kbuild-6.3/scripts/sign-file
Signing key: /var/lib/dkms/mok.key
Public certificate (MOK): /var/lib/dkms/mok.pub
Creating symlink /var/lib/dkms/dahdi/3.1.0+git20230717/source -> 
/usr/src/dahdi-3.1.0+git20230717

Building module:
Cleaning build area...
(make modules KVERS=6.3.0-2-amd64 MODULES_EXTRA='dahdi_dummy 
dahdi_echocan_oslec'; make KVERS=6.3.0-2-amd64)
Error!  Build of pciradio.ko failed for: 6.3.0-2-amd64 (x86_64)
Make sure the name of the generated module is correct and at the root of the
build directory, or consult make.log in the build directory
/var/lib/dkms/dahdi/3.1.0+git20230717/build for more information.
E: dahdi/3.1.0+git20230717 failed to build for 6.3.0-2-amd64

make.log has no mention of pciradio at all and does not report any
failures, thus it is not attached.

While updating d/dkms.conf.in, you can probably drop CONFIG_PCI from
BUILD_EXCLUSIVE_CONFIG (and update the comment) and
switch from BUILD_EXCLUSIVE_KERNEL=...(regex)... to the more readable
BUILD_EXCLUSIVE_KERNEL_MIN="5.6" (supported since dkms in trixie).


Andreas
--- End Message ---
--- Begin Message ---
Source: dahdi-linux
Source-Version: 1:3.1.0+git20230717~dfsg-3
Done: Tzafrir Cohen 

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

Debian distribution maintenance software
pp.
Tzafrir Cohen  (supplier of updated dahdi-linux 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: Sat, 02 Sep 2023 16:00:47 +0300
Source: dahdi-linux
Architecture: source
Version: 1:3.1.0+git20230717~dfsg-3
Distribution: unstable
Urgency: medium
Maintainer: Debian VoIP Team 
Changed-By: Tzafrir Cohen 
Closes: 592745 1042747
Changes:
 dahdi-linux (1:3.1.0+git20230717~dfsg-3) unstable; urgency=medium
 .
   * Fix building module-assistant package without dkms
 (Regression from -2).
   * Fixed in previous release: Closes: #1042747.
   * wcfxo no longer included: Closes: #592745.
   * Switch to debhelper-compat.
   * Policy version 4.6.2.
   * Remove obsolete backports/ directory
Checksums-Sha1:
 1997ad01cb86a33d587ea3b4ef6bd5862b6bb871 2231 
dahdi-linux_3.1.0+git20230717~dfsg-3.dsc
 55a35c1c35a16b218bdea1a60f9b63c29518ffd4 45708 
dahdi-linux_3.1.0+git20230717~dfsg-3.debian.tar.xz
 1e9aef232168abd238e1ff8f69782d290b451c1a 7186 
dahdi-linux_3.1.0+git20230717~dfsg-3_amd64.buildinfo
Checksums-Sha256:
 50b7040f0fc032581c7ac1c4a8d156750ece9cbdc45ab474403b41686e71f7de 2231 
dahdi-linux_3.1.0+git20230717~dfsg-3.dsc
 5ba0d21600a2515662edc1d28606260a3cc4a31c9e4bc53c1530479eddb0bb1e 45708 
dahdi-linux_3.1.0+git20230717~dfsg-3.debian.tar.xz
 ef75b3881ec47e1965608fbcaac26ed552a80110c37200bc0cf22a8fba57c0f5 7186 
dahdi-linux_3.1.0+git20230717~dfsg-3_amd64.buildinfo
Files:
 24ab1447630ef81b6dabf19ee8fff915 2231 comm optional 
dahdi-linux_3.1.0+git20230717~dfsg-3.dsc
 c14f6cad75a0873fab61634f7b0a265b 45708 comm optional 
dahdi-linux_3.1.0+git20230717~dfsg-3.debian.tar.xz
 4ac512e576714a8c2e2104e96924801d 7186 comm optional 
dahdi-linux_3.1.0+git20230717~dfsg-3_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQGzBAEBCAAdFiEEjhGGa0mM+W3ykQJyjv1MLwMloM4FAmTzO9AACgkQjv1MLwMl
oM5P3gv9HNPEDrDI6dmq6OC6D4K2NOgDflf/kiAzLZME0lJ0LHohCaXU+mz8zMlV
ZQr+Ag2ff0GTA6jTwfs2/Z8KFciXaZcGylU26NouoOFBBYh0awOuNDU/4C69hSmM
c8ch9xmHDhCaLc/xsmguQcsH1WPPhZm7tVbwiq9I/yZe2pTtQ/Q7nTr9qNjVBT4v

Bug#1042933: marked as pending in octave-statistics

[Sébastien Villemot]

Control: tag -1 pending

Hello,

Bug #1042933 in octave-statistics 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/pkg-octave-team/octave-statistics/-/commit/548989993dc2aa7c39380e1dc49f016158875763


test-failures-cameratarget.patch: new patch by Graham Inggs

Taken from Ubuntu. Fixes random autopkgtest failures.

Closes: #1042933
Gbp-Dch: Full


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1042933

Processed: Bug#1042933 marked as pending in octave-statistics

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1042933 [src:octave-statistics] octave-statistics autopkg tests fail in 
unstable on amd64
Added tag(s) pending.

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

Bug#1042933: octave-statistics autopkg tests fail in unstable on amd64

[Sébastien Villemot]

Le jeudi 31 août 2023 à 15:12 +0200, Rafael Laboissière a écrit :
> * Rafael Laboissière  [2023-08-31 15:01]:
> 
> > * Sébastien Villemot  [2023-08-31 12:05]:
> > 
> > > Le jeudi 03 août 2023 à 08:33 +0200, Rafael Laboissière a écrit :
> > > > 
> > > > Just for the record, this is the offending unit test:
> > > > 
> > > > 308s [inst/ConfusionMatrixChart.m]
> > > > 308s >
> > > > 
> > > > /tmp/autopkgtest-lxc.9x_h6bvs/downtmp/build.BGX/src/inst/ConfusionMatrixChart.m
> > > > 308s * demo
> > > > 308s  ## Create a simple ConfusionMatrixChart Object
> > > > 308s
> > > > 308s  cm = ConfusionMatrixChart (gca, [1 2; 1 2], 
> > > > {"A","B"},{"XLabel","LABEL A"})
> > > > 308s  NormalizedValues = cm.NormalizedValues
> > > > 308s  ClassLabels = cm.ClassLabels
> > > > 308s * shared visibility_setting
> > > > 308s  visibility_setting = get (0, "DefaultFigureVisible");
> > > > 308s * test
> > > > 308s  set (0, "DefaultFigureVisible", "off");
> > > > 308s  cm = ConfusionMatrixChart (gca, [1 2; 1 2], 
> > > > {"A","B"},{"XLabel","LABEL A"});
> > > > 308s  assert (isa (cm, "ConfusionMatrixChart"), true);
> > > > 308s  set (0, "DefaultFigureVisible", visibility_setting);
> > > > 308s warning: Non-positive limit for logarithmic axis ignored
> > > > 308s ! test failed
> > > > 308s set: "cameratarget" must be finite
> > > > 308s shared variables visibility_setting = on
> > > > 308s 1 test, 0 passed, 0 known failure, 0 skipped
> > > > 
> > > > We have seen this problem already elsewhere. I will try to 
> > > > investigate it.
> > > 
> > > Did you get to a conclusion?
> > 
> > No progress on my side, sorry.
> 
> At any rate, the last autopkgtest run (on 2023-08-26) succeded: 
> https://ci.debian.net/data/autopkgtest/unstable/amd64/o/octave-statistics/37186503/log.gz
> 
> Should we close this bug report?

It seems that the failures are random. They also occurred on Ubuntu.
I’m going to apply the patch that was added there.

-- 
⢀⣴⠾⠻⢶⣦⠀  Sébastien Villemot
⣾⠁⢠⠒⠀⣿⡁  Debian Developer
⢿⡄⠘⠷⠚⠋⠀  https://sebastien.villemot.name
⠈⠳⣄  https://www.debian.org



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

Processed: categorize bug 1050903

[Debian Bug Tracking System]

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

> tag 1050903 confirmed
Bug #1050903 [telegram-desktop] telegram-desktop: segmentation fault
Added tag(s) confirmed.
>
End of message, stopping processing here.

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

Processed: Re: Bug#1051076: dash: test does not support s1 < s2 or s1 > s2

[Debian Bug Tracking System]

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

> severity 1051076 grave
Bug #1051076 [dash] dash: test does not support s1 < s2 or s1 > s2
Severity set to 'grave' from 'normal'
> thanks
Stopping processing here.

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

Bug#1051081: dart: binary-any FTBFS with recent jdupes

[Aurelien Jarno]

Source: dart
Version: 6.12.1+dfsg4-12
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)

Dear maintainer,

dart fails to build from source when building only binary-any and not
binary-all. From my build log on amd64:

| make[1]: Leaving directory '/<>/.pybuild/cpython3_3.11/build'
|debian/rules execute_after_dh_auto_install
| make[1]: Entering directory '/<>'
| rm -f debian/tmp/usr/share/doc/dart/data/screencap/.KEEP
| make[1]: Leaving directory '/<>'
|dh_install -a -O--buildsystem=pybuild
|dh_installdocs -a -O--buildsystem=pybuild
|dh_installchangelogs -a -O--buildsystem=pybuild
|dh_python3 -a -O--buildsystem=pybuild
|dh_installsystemduser -a -O--buildsystem=pybuild
|dh_perl -a -O--buildsystem=pybuild
|debian/rules execute_before_dh_link
| make[1]: Entering directory '/<>'
| jdupes -rl debian/dart-doc/usr
| 
| could not stat dir debian/dart-doc/usr
| No duplicates found.
| make[1]: *** [debian/rules:40: execute_before_dh_link] Error 1
| make[1]: Leaving directory '/<>'
| make: *** [debian/rules:19: binary-arch] Error 2
| dpkg-buildpackage: error: debian/rules binary-arch subprocess returned exit 
status 2

A full build log on riscv64 is also available:
https://buildd.debian.org/status/fetch.php?pkg=dart=riscv64=6.12.1%2Bdfsg4-12=1693507283=0

The return value of jdupes changed after bookworm to no longer return
success when the given paths do not exist, which causes this failure in
binary-any builds.

A possible untested patch is:

--- dart-6.12.1+dfsg4/debian/rules
+++ dart-6.12.1+dfsg4/debian/rules
@@ -36,5 +36,5 @@
 -X.sdf -X.skel -X.urdf -X.vsk -X.world \
 -X.c3d -X.changelog -X.dof -X.path -X.tris
 
-execute_before_dh_link:
+execute_before_dh_link-indep:
jdupes -rl debian/dart-doc/usr

Regards
Aurelien

Bug#1042038: marked as done (mfem: FTBFS: hash.hpp:1001:39: error: ISO C++ forbids declaration of ‘type name’ with no type [-fpermissive])

[Debian Bug Tracking System]

Your message dated Sat, 02 Sep 2023 12:20:48 +
with message-id 
and subject line Bug#1042038: fixed in mfem 4.5.2+ds-1.1
has caused the Debian Bug report #1042038,
regarding mfem: FTBFS: hash.hpp:1001:39: error: ISO C++ forbids declaration of 
‘type name’ with no type [-fpermissive]
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.)


-- 
1042038: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042038
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: mfem
Version: 4.5.2+ds-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs

Hi,

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


Relevant part (hopefully):
> /usr/bin/c++ 
> -DMFEM_CONFIG_FILE=\"/<>/obj-x86_64-linux-gnu/config/_config.hpp\"
>  -Dmfem_EXPORTS -I/<>/obj-x86_64-linux-gnu -I/<> 
> -I/usr/include/hypre -I/usr/lib/x86_64-linux-gnu/openmpi/include 
> -I/usr/lib/x86_64-linux-gnu/openmpi/include/openmpi -g -O2 
> -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -O2 -g -DNDEBUG 
> -std=c++11 -fPIC -MD -MT CMakeFiles/mfem.dir/general/gecko.cpp.o -MF 
> CMakeFiles/mfem.dir/general/gecko.cpp.o.d -o 
> CMakeFiles/mfem.dir/general/gecko.cpp.o -c /<>/general/gecko.cpp
> In file included from /<>/general/hash.cpp:12:
> /<>/general/hash.hpp: In member function ‘mfem::HashFunction& 
> mfem::HashFunction::EncodeAndHashDoubles(double_const_iter, 
> double_const_iter)’:
> /<>/general/hash.hpp:1001:39: error: ISO C++ forbids declaration 
> of ‘type name’ with no type [-fpermissive]
>  1001 |   auto k = reinterpret_cast(*begin);
>   |   ^~~~
> /<>/general/hash.hpp:1001:39: error: expected ‘>’ before 
> ‘uint64_t’
> /<>/general/hash.hpp:1001:39: error: expected ‘(’ before 
> ‘uint64_t’
>  1001 |   auto k = reinterpret_cast(*begin);
>   |   ^~~~
>   |   (
> /<>/general/hash.hpp:1001:39: error: ‘uint64_t’ was not declared 
> in this scope
>  1001 |   auto k = reinterpret_cast(*begin);
>   |   ^~~~
> /<>/general/hash.hpp:17:1: note: ‘uint64_t’ is defined in header 
> ‘’; did you forget to ‘#include ’?
>16 | #include "array.hpp"
>   +++ |+#include 
>17 | #include "globals.hpp"
> /<>/general/hash.hpp:1001:49: error: expected primary-expression 
> before ‘>’ token
>  1001 |   auto k = reinterpret_cast(*begin);
>   | ^
> /<>/general/hash.hpp:1001:58: error: expected ‘)’ before ‘;’ 
> token
>  1001 |   auto k = reinterpret_cast(*begin);
>   |  ^
>   |  )
> [  2%] Building CXX object CMakeFiles/mfem.dir/general/isockstream.cpp.o
> /usr/bin/c++ 
> -DMFEM_CONFIG_FILE=\"/<>/obj-x86_64-linux-gnu/config/_config.hpp\"
>  -Dmfem_EXPORTS -I/<>/obj-x86_64-linux-gnu -I/<> 
> -I/usr/include/hypre -I/usr/lib/x86_64-linux-gnu/openmpi/include 
> -I/usr/lib/x86_64-linux-gnu/openmpi/include/openmpi -g -O2 
> -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -O2 -g -DNDEBUG 
> -std=c++11 -fPIC -MD -MT CMakeFiles/mfem.dir/general/isockstream.cpp.o -MF 
> CMakeFiles/mfem.dir/general/isockstream.cpp.o.d -o 
> CMakeFiles/mfem.dir/general/isockstream.cpp.o -c 
> /<>/general/isockstream.cpp
> make[3]: *** [CMakeFiles/mfem.dir/build.make:121: 
> CMakeFiles/mfem.dir/general/hash.cpp.o] Error 1


The full build log is available from:
http://qa-logs.debian.net/2023/07/24/mfem_4.5.2+ds-1_unstable.log

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

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

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Source: mfem
Source-Version: 4.5.2+ds-1.1
Done: Gianfranco Costamagna 

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

Bug#1042038: mfem: diff for NMU version 4.5.2+ds-1.1

[Gianfranco Costamagna]

Control: tags 1042038 + patch
Control: tags 1042038 + pending

Dear maintainer,

I've prepared an NMU for mfem (versioned as 4.5.2+ds-1.1) and
uploaded it.


Regards.
From: Gianfranco Costamagna 
To:   1042...@bugs.debian.org
Cc:
Bcc: 
Subject: mfem: diff for NMU version 4.5.2+ds-1.1
Date: Sat, 02 Sep 2023 14:12:16 +0200
X-NMUDIFF-Version: 2.22.1ubuntu1

Control: tags 1042038 + patch
Control: tags 1042038 + pending

[Replace XX with correct value]

Dear maintainer,

I've prepared an NMU for mfem (versioned as 4.5.2+ds-1.1) and
uploaded it to DELAYED/XX. Please feel free to tell me if I
should delay it longer.

Regards.

diff -Nru mfem-4.5.2+ds/debian/changelog mfem-4.5.2+ds/debian/changelog
--- mfem-4.5.2+ds/debian/changelog	2023-03-28 10:25:56.0 +0200
+++ mfem-4.5.2+ds/debian/changelog	2023-09-02 14:09:24.0 +0200
@@ -1,3 +1,13 @@
+mfem (4.5.2+ds-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+
+  [ Amin Bandali  ]
+  * Add upstream patch to fix FTBFS with gcc-13 (Closes: #1042038)
+- debian/patches/fix-ftbfs-gcc-13.patch
+
+ -- Gianfranco Costamagna   Sat, 02 Sep 2023 14:09:24 +0200
+
 mfem (4.5.2+ds-1) unstable; urgency=medium
 
   * Initial release. (Closes: #1023223)
diff -Nru mfem-4.5.2+ds/debian/patches/fix-ftbfs-gcc-13.patch mfem-4.5.2+ds/debian/patches/fix-ftbfs-gcc-13.patch
--- mfem-4.5.2+ds/debian/patches/fix-ftbfs-gcc-13.patch	1970-01-01 01:00:00.0 +0100
+++ mfem-4.5.2+ds/debian/patches/fix-ftbfs-gcc-13.patch	2023-09-02 14:09:24.0 +0200
@@ -0,0 +1,53 @@
+From 314a32af2ee80af8c9af7d8ad71babd51851154c Mon Sep 17 00:00:00 2001
+From: David Dement 
+Origin: https://github.com/mfem/mfem/commit/314a32af2ee80af8c9af7d8ad71babd51851154c
+Date: Thu, 27 Apr 2023 10:33:51 -0400
+Subject: [PATCH] Fixes comilation errors when compiling with gcc-13 on Fedora
+ 38
+
+When compiling with gcc-13, types such as uint64_t are not defined.
+It is likely that  is included implicitly with older compiler
+versions.
+---
+ general/hash.hpp| 1 +
+ general/mem_manager.cpp | 1 +
+ mesh/vtk.hpp| 2 ++
+ 3 files changed, 4 insertions(+)
+
+diff --git a/general/hash.hpp b/general/hash.hpp
+index 86d987d8029..288d51288df 100644
+--- a/general/hash.hpp
 b/general/hash.hpp
+@@ -16,6 +16,7 @@
+ #include "array.hpp"
+ #include "globals.hpp"
+ #include 
++#include 
+ 
+ namespace mfem
+ {
+diff --git a/general/mem_manager.cpp b/general/mem_manager.cpp
+index 416a6ac6203..37b80c878ad 100644
+--- a/general/mem_manager.cpp
 b/general/mem_manager.cpp
+@@ -16,6 +16,7 @@
+ #include  // std::memcpy, std::memcmp
+ #include 
+ #include  // std::max
++#include 
+ 
+ // Uncomment to try _WIN32 platform
+ //#define _WIN32
+diff --git a/mesh/vtk.hpp b/mesh/vtk.hpp
+index a59bed27592..50eeea5bc78 100644
+--- a/mesh/vtk.hpp
 b/mesh/vtk.hpp
+@@ -12,6 +12,8 @@
+ #ifndef MFEM_VTK
+ #define MFEM_VTK
+ 
++#include 
++
+ #include "../fem/geom.hpp"
+ #include "../general/binaryio.hpp"
+ 
diff -Nru mfem-4.5.2+ds/debian/patches/series mfem-4.5.2+ds/debian/patches/series
--- mfem-4.5.2+ds/debian/patches/series	2023-03-01 14:14:12.0 +0100
+++ mfem-4.5.2+ds/debian/patches/series	2023-09-02 14:09:24.0 +0200
@@ -1,2 +1,3 @@
 static-no-shared-yes
 not-makefile
+fix-ftbfs-gcc-13.patch


OpenPGP_signature
Description: OpenPGP digital signature

Processed: mfem: diff for NMU version 4.5.2+ds-1.1

[Debian Bug Tracking System]

Processing control commands:

> tags 1042038 + patch
Bug #1042038 [src:mfem] mfem: FTBFS: hash.hpp:1001:39: error: ISO C++ forbids 
declaration of ‘type name’ with no type [-fpermissive]
Ignoring request to alter tags of bug #1042038 to the same tags previously set
> tags 1042038 + pending
Bug #1042038 [src:mfem] mfem: FTBFS: hash.hpp:1001:39: error: ISO C++ forbids 
declaration of ‘type name’ with no type [-fpermissive]
Added tag(s) pending.

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

Bug#1041249: cpp-httplib: FTBFS on s390x: ../test/test.cc:5462: Failure

[Sebastian Ramacher]

Control: severity -1 important

On 2023-09-01 20:51:11 -0400, Jeremy Bícha wrote:
> Sebastian,
> 
> cpp-httplib has built on all release architectures now. This bug is
> now blocking migration to Testing.

There are still flaky tests to either be fixed or disabled, though.
Since it built on the buildds, let's downgrade it to important.

Cheers
-- 
Sebastian Ramacher

Processed: Re: Bug#1041249: cpp-httplib: FTBFS on s390x: ../test/test.cc:5462: Failure

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #1041249 [src:cpp-httplib] cpp-httplib: FTBFS on s390x, armhf due to flaky 
tests
Severity set to 'important' from 'serious'

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

Bug#1037842: marked as done (ring: ftbfs with GCC-13)

[Debian Bug Tracking System]

Your message dated Sat, 02 Sep 2023 10:22:24 +
with message-id 
and subject line Bug#1037842: fixed in ring 20230206.0~ds2-1.3
has caused the Debian Bug report #1037842,
regarding ring: ftbfs with GCC-13
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.)


-- 
1037842: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037842
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:ring
Version: 20230206.0~ds2-1.1
Severity: normal
Tags: sid trixie
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-13

[This bug is targeted to the upcoming trixie release]

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

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

The full build log can be found at:
http://qa-logs.debian.net/2023/05/22/logs/ring_20230206.0~ds2-1.1_unstable_gccexp.log
The last lines of the build log are at the end of this report.

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

  apt-get -t=experimental install g++ 

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

[...]
  147 | nbChannels = f->channels;
  | ^~~~
/usr/include/x86_64-linux-gnu/libavutil/frame.h:643:9: note: declared here
  643 | int channels;
  | ^~~~
fileutils.cpp: In function ‘std::vector > 
jami::fileutils::readDirectory(const std::string&)’:
fileutils.cpp:541:22: warning: ‘int readdir_r(DIR*, dirent*, dirent**)’ is 
deprecated [-Wdeprecated-declarations]
  541 | while (!readdir_r(dp, reinterpret_cast(buf.data()), 
) && entry) {
  | ~^~~
In file included from /usr/include/features.h:489,
 from /usr/include/x86_64-linux-gnu/c++/13/bits/os_defines.h:39,
 from /usr/include/x86_64-linux-gnu/c++/13/bits/c++config.h:679,
 from /usr/include/c++/13/cstddef:49,
 from /usr/include/fmt/core.h:11,
 from logger.h:27,
 from fileutils.cpp:25:
/usr/include/dirent.h:191:12: note: declared here
  191 | extern int __REDIRECT (readdir_r,
  |^~
depbase=`echo threadloop.lo | sed 's|[^/]*$|.deps/&|;s|\.lo$||'`;\
/bin/bash ../libtool  --tag=CXX   --mode=compile g++ -std=gnu++17 
-DHAVE_CONFIG_H -I. -I..  -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 
-fvisibility=hidden -DLIBJAMI_BUILD -DASIO_STANDALONE 
-I/<>/daemon/contrib/x86_64-linux-gnu/include  -DPJ_AUTOCONF=1 
-I/usr/include/jsoncpp  -I/<>/daemon/src 
-I/<>/daemon/src/config -I/<>/daemon/src/media 
-I/<>/daemon/test -I/<>/daemon/src/jami  
-DPREFIX=\"/usr\" -DJAMI_DATADIR=\"/usr/share/jami\" -DENABLE_TRACE 
-DJAMI_REVISION=\"\" -DJAMI_DIRTY_REPO=\"dirty\" -DPJSIP_MAX_PKT_LEN=8000 
-DPJ_AUTOCONF=1 -I../src/jamidht/eth -Wdate-time -D_FORTIFY_SOURCE=2 -DNDEBUG=1 
-O3 -Wno-deprecated -g -O2 -ffile-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -D_LARGEFILE_SOURCE 
-D_FILE_OFFSET_BITS=64 -MT threadloop.lo -MD -MP -MF $depbase.Tpo -c -o 
threadloop.lo threadloop.cpp &&\
mv -f $depbase.Tpo $depbase.Plo
libtool: compile:  g++ -std=gnu++17 -DHAVE_CONFIG_H -I. -I.. 
-D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -fvisibility=hidden -DLIBJAMI_BUILD 
-DASIO_STANDALONE "-I/<>/daemon/contrib/x86_64-linux-gnu/include" 
-DPJ_AUTOCONF=1 -I/usr/include/jsoncpp "-I/<>/daemon/src" 
"-I/<>/daemon/src/config" "-I/<>/daemon/src/media" 
"-I/<>/daemon/test" "-I/<>/daemon/src/jami" 
-DPREFIX=\"/usr\" -DJAMI_DATADIR=\"/usr/share/jami\" -DENABLE_TRACE 
-DJAMI_REVISION=\"\" -DJAMI_DIRTY_REPO=\"dirty\" -DPJSIP_MAX_PKT_LEN=8000 
-DPJ_AUTOCONF=1 -I../src/jamidht/eth -Wdate-time -D_FORTIFY_SOURCE=2 -DNDEBUG=1 
-O3 -Wno-deprecated -g -O2 "-ffile-prefix-map=/<>=." 
-fstack-protector-strong -Wformat -Werror=format-security -D_LARGEFILE_SOURCE 
-D_FILE_OFFSET_BITS=64 -MT threadloop.lo -MD -MP -MF .deps/threadloop.Tpo -c 
threadloop.cpp -o threadloop.o
depbase=`echo 

Bug#1042953: smokeping: Recommends non-existing package 'echoping'

[Christoph Biedl]

Control: tags 1042953 + patch pending

IOhannes m zmölnig (Debian/GNU) wrote...

> The current version of smokeping in Debian (2.7.3-4.1) still depends on
> 'echoping' which was removed from the archives on 2020-08-07, so the
> last release that shipped it was buster (currently: old-old-stable).

For reference: The removal bug against echoping was
https://bugs.debian.org/1002897 and ultimately the removal was on 2022-01-02,
according to https://ftp-master.debian.org/removals-2022.txt

> Please remove this dependency (as it violates Debian policy §2.2.1, see
> https://www.debian.org/doc/debian-policy/ch-archive.html#the-main-archive-area)

Since echoping is optional in smokeping and I'm glad to confirm that
package otherwise does what it's supposed to do, the fix is trivial, so
here we go:

Dear maintainer,

to fix the issues with this package, I've prepared an NMU for smokeping
(versioned as 2.7.3-4.2), debdiff below. An upload to DELAYED/5 will
follow shortly. Please feel free to tell me if I should delay it
longer.

Regards,

Christoph
diff -Nru smokeping-2.7.3/debian/changelog smokeping-2.7.3/debian/changelog
--- smokeping-2.7.3/debian/changelog2022-10-15 12:46:49.0 +0200
+++ smokeping-2.7.3/debian/changelog2023-09-02 11:50:51.0 +0200
@@ -1,3 +1,11 @@
+smokeping (2.7.3-4.2) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Remove recommendation on echoping which is no longer in Debian.
+Closes: #1042953
+
+ -- Christoph Biedl   Sat, 02 Sep 2023 
11:50:51 +0200
+
 smokeping (2.7.3-4.1) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -Nru smokeping-2.7.3/debian/control smokeping-2.7.3/debian/control
--- smokeping-2.7.3/debian/control  2022-04-24 20:44:58.0 +0200
+++ smokeping-2.7.3/debian/control  2023-09-02 11:41:39.0 +0200
@@ -49,7 +49,6 @@
 Recommends: apache2 | httpd-cgi
  , libsocket6-perl
  , dnsutils
- , echoping
  , ${misc:Recommends}
 Suggests: curl
  , libauthen-radius-perl


signature.asc
Description: PGP signature

Processed: Re: smokeping: Recommends non-existing package 'echoping'

[Debian Bug Tracking System]

Processing control commands:

> tags 1042953 + patch pending
Bug #1042953 [src:smokeping] smokeping: Recommends non-existing package 
'echoping'
Added tag(s) pending and patch.

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

Bug#1037842: ring: diff for NMU version 20230206.0~ds2-1.3

[Gianfranco Costamagna]

Control: tags 1037842 + patch
Control: tags 1037842 + pending


Dear maintainer,

I've prepared an NMU for ring (versioned as 20230206.0~ds2-1.3) and
uploaded it.

Regards.
From: Gianfranco Costamagna 
To:   1037...@bugs.debian.org
Cc:
Bcc: 
Subject: ring: diff for NMU version 20230206.0~ds2-1.3
Date: Sat, 02 Sep 2023 11:57:01 +0200
X-NMUDIFF-Version: 2.22.1ubuntu1

Control: tags 1037842 + patch
Control: tags 1037842 + pending

[Replace XX with correct value]

Dear maintainer,

I've prepared an NMU for ring (versioned as 20230206.0~ds2-1.3) and
uploaded it to DELAYED/XX. Please feel free to tell me if I
should delay it longer.

Regards.

diff -Nru ring-20230206.0~ds2/debian/changelog ring-20230206.0~ds2/debian/changelog
--- ring-20230206.0~ds2/debian/changelog	2023-07-01 23:23:01.0 +0200
+++ ring-20230206.0~ds2/debian/changelog	2023-09-02 10:00:03.0 +0200
@@ -1,3 +1,14 @@
+ring (20230206.0~ds2-1.3) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * debian/patches/d5e6509975bfaa67f7b3c54db72336b810454fc2.patch:
+- gcc-13 upstream build fix (Closes: #1037842)
+  * debian/patches/bfa5a93114266caf791ff62c84918249c6d75bdf.patch:
+  * debian/patches/fc975f0cacde4b06c6adde3d7f0c02f71abfb38c.patch:
+- ffmpeg 6.0 upstream build fix.
+
+ -- Gianfranco Costamagna   Sat, 02 Sep 2023 10:00:03 +0200
+
 ring (20230206.0~ds2-1.2) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -Nru ring-20230206.0~ds2/debian/patches/bfa5a93114266caf791ff62c84918249c6d75bdf.patch ring-20230206.0~ds2/debian/patches/bfa5a93114266caf791ff62c84918249c6d75bdf.patch
--- ring-20230206.0~ds2/debian/patches/bfa5a93114266caf791ff62c84918249c6d75bdf.patch	1970-01-01 01:00:00.0 +0100
+++ ring-20230206.0~ds2/debian/patches/bfa5a93114266caf791ff62c84918249c6d75bdf.patch	2023-09-02 10:00:03.0 +0200
@@ -0,0 +1,256 @@
+From bfa5a93114266caf791ff62c84918249c6d75bdf Mon Sep 17 00:00:00 2001
+From: Adrien Beraud 
+Date: Sun, 5 Mar 2023 11:05:25 -0500
+Subject: [PATCH] debug utils: use ffmpeg for WavWriter
+
+The previous writer was not working, the format was not
+recognized by most players.
+The new version uses ffmpeg APIs to produce working wav files
+(tested stereo s16 and mono f32).
+The API remains the same and it should be a drop-in
+replacement for existing code.
+
+Change-Id: I328e32427d94a44085ddb1567b5a1bbee5a6a8bc
+---
+ contrib/src/ffmpeg/rules.mak |   9 +-
+ src/debug_utils.h| 211 +--
+ 2 files changed, 111 insertions(+), 109 deletions(-)
+
+diff --git a/daemon/src/debug_utils.h b/daemon/src/debug_utils.h
+index 8572790599..3e519b7e7e 100644
+--- a/daemon/src/debug_utils.h
 b/daemon/src/debug_utils.h
+@@ -75,127 +75,122 @@ private:
+ };
+ 
+ /**
+- * Minimally invasive audio logger. Writes a wav file from raw PCM or AVFrame. Helps debug what goes
+- * wrong with audio.
++ * Audio logger. Writes a wav file from raw PCM or AVFrame. Helps debug what goes wrong with audio.
+  */
+-class WavWriter
+-{
++class WavWriter {
+ public:
+-WavWriter(std::string filename, AVFrame* frame)
+-: format_(static_cast(frame->format))
+-, channels_(frame->channels)
+-, planar_(av_sample_fmt_is_planar(format_))
+-, depth_(av_get_bytes_per_sample(format_))
+-, stepPerSample_(planar_ ? depth_ : depth_ * channels_)
++WavWriter(const char* filename, AVFrame* frame)
+ {
+-std::vector v {AV_SAMPLE_FMT_FLT,
+-   AV_SAMPLE_FMT_FLTP,
+-   AV_SAMPLE_FMT_DBL,
+-   AV_SAMPLE_FMT_DBLP};
+-f_ = std::ofstream(filename, std::ios_base::out | std::ios_base::binary);
+-f_.imbue(std::locale::classic());
+-f_ << "RIFFWAVEfmt ";
+-if (std::find(v.begin(), v.end(), format_) == v.end()) {
+-write(16, 4); // Chunk size
+-write(1, 2);  // WAVE_FORMAT_PCM
+-write(frame->channels, 2);
+-write(frame->sample_rate, 4);
+-write(frame->sample_rate * depth_ * frame->channels, 4); // Bytes per second
+-write(depth_ * frame->channels, 2);  // Multi-channel sample size
+-write(8 * depth_, 2);// Bits per sample
+-f_ << "data";
+-dataChunk_ = f_.tellp();
+-f_ << "";
+-} else {
+-write(18, 4); // Chunk size
+-write(3, 2);  // Non PCM data
+-write(frame->channels, 2);
+-write(frame->sample_rate, 4);
+-write(frame->sample_rate * depth_ * frame->channels, 4); // Bytes per second
+-write(depth_ * frame->channels, 2);  // Multi-channel sample size
+-write(8 * depth_, 2);// Bits per sample
+-write(0, 2); // Extension size
+-   

Processed: ring: diff for NMU version 20230206.0~ds2-1.3

[Debian Bug Tracking System]

Processing control commands:

> tags 1037842 + patch
Bug #1037842 [src:ring] ring: ftbfs with GCC-13
Added tag(s) patch.
> tags 1037842 + pending
Bug #1037842 [src:ring] ring: ftbfs with GCC-13
Added tag(s) pending.

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

Bug#1051066: [Pkg-netatalk-devel] Bug#1051066: netatalk: 9 outstanding CVEs in Bullseye with available patches

[Jonas Smedegaard]

Quoting Daniel Markstedt (2023-09-02 00:00:14)
> Package: netatalk
> Version: 3.1.12~ds-8
> Severity: critical
> Tags: patch security
> Justification: root security hole
> X-Debbugs-Cc: pkg-netatalk-de...@alioth-lists.debian.net, Debian Security 
> Team 
> 
> Nine CVE security advisories were addressed in netatalk upstream
> releases between 3.1.13 and 3.1.15. The full list is below:
> 
> CVE-2022-45188
> CVE-2022-43634
> CVE-2022-23125
> CVE-2022-23124
> CVE-2022-23123
> CVE-2022-23122
> CVE-2022-23121
> CVE-2022-0194
> CVE-2021-31439
> 
> Current status of patching these vulnerabilities:
> - netatalk oldoldstable has already been patched by the Security Team.
> - netatalk unstable has already been patched by the maintainer team.
> - The netatalk package was excluded from stable, no action required.
> - What remains is to patch oldstable, hence this ticket.
> 
> A debpatch has been attached to the related Release bug ticket,
> where approval to proceed with an oldstable release has been requested.
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1049325

This is one bugreport about multiple issues.  That easily gets confusing
to track, e.g. if some of the issues are solved and some are not, for a
certain release of the package (and consequently a Debian release where
that package release is included).

It is generally easier to track when instead filing one bugreport per
issue.

I tried lookup one of above CVEs inn the Debian security tracker:
https://security-tracker.debian.org/tracker/CVE-2022-43634

It references an already filed bugreport about that issue, bug#1034170,
which is tagged as found only as early as 3.1.14~ds-1.  If earlier
Debian package releases are also affected by that particular issue, then
please update that bugreport to reflect that fact.

This bugreport is flagged as "archived" (which is done automatically
after being done for a while, to reduce spam). Before doing other
changes you therefore need to first unachive it.

E.g. something like this:

  bts unarchive 1034170 . found 1034170 3.1.13~ds-1

The other CVEs seemingly have no related bugreport (from a quick look at
the security tracker - but I suspect that database does not list
bugreports not involving the security team at first, and only later
mentioning a CVE if at all).  If you don't happen to be aware of
bugreports exisisting for those other issues, then I suggest to file new
individual bugreports for each issue (also because it is easy to merge
issues later as needed).


Kind regards, and thanks a lot for looking into this,

 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/
 * Sponsorship: https://ko-fi.com/drjones

 [x] quote me freely  [ ] ask before reusing  [ ] keep private

signature.asc
Description: signature

Bug#1050186: [Pkg-nginx-maintainers] Bug#1050186: Bug#1050186: Bug#1050186: libnginx-mod-http-lua: depends on obsolete pcre3 library

[Jan Mojzis]

> https://github.com/swananan/lua-resty-core/tree/support_pcre2
uploaded: 0.1.27-2~exp1

> https://github.com/swananan/lua-nginx-module/commits/support_pcre2
uploaded: 1:0.10.25-2~exp2

> https://github.com/swananan/stream-lua-nginx-module/commits/support_pcre2
not in debian

Bug#1051070: RM: gtimer -- RoQA; low popcon; depends on gtk2

[Bastian Germann]

Source: gtimer
Severity: serious

gtimer does not seem to be used a lot and is unmaintained upstream.

I intend to file a RM bug.
If you have any reasons to keep it in Debian please voice them here.
To get people's attention, I am filing as a serious bug and will reassign to the FTP team when the package is 
autoremoved from testing.

Bug#1037213: Awstats bug #1037213 - is bug really fixed?

[Christian Marillat]

On 01 sept. 2023 13:55, Lourisvaldo Figueredo Junior 
 wrote:

> Hi Christian,
>
> I saw now that you adopted the awstats package and that you closed this bug 
> (1037213).
> But I believe the bug is not resolved yet. It happens on bookworm. I have two 
> bugs open right now to fix this. [1]
>
> Since you are the maintainer now, how do you want to resolve this issue?

I noticed that you have filed a bug 1050591 to backport cahnges added in
7.8-4 to bulleye. May be you can do the same for bookworm ?

Christian