Bug#1019420: marked as done (xfce4-pulseaudio-plugin volume icon flickers)

[Debian Bug Tracking System]

Your message dated Sat, 01 Oct 2022 04:22:14 +
with message-id 
and subject line Bug#1019420: fixed in xfce4-pulseaudio-plugin 0.4.5-1
has caused the Debian Bug report #1019420,
regarding xfce4-pulseaudio-plugin volume icon flickers
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.)


-- 
1019420: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1019420
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: xfce4-pulseaudio-plugin
Version: 0.4.4-1
Severity: normal
X-Debbugs-Cc: none

After upgrading to 0.4.4-1, adjusting the volume seems to make the
panel icon flicker. Other actions like seeking on a video in VLC or
Parole, or using a video conferencing in a web browser also cause
this.

I tried compiling the latest version. It still happens there but not
as reliably.

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

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

Versions of packages xfce4-pulseaudio-plugin depends on:
ii  libc62.34-7
ii  libexo-2-0   4.16.4-1
ii  libglib2.0-0 2.73.3-3
ii  libgtk-3-0   3.24.34-3
ii  libkeybinder-3.0-0   0.3.2-1.1
ii  libnotify4   0.8.1-1
ii  libpulse-mainloop-glib0  15.0+dfsg1-4+b1
ii  libpulse015.0+dfsg1-4+b1
ii  libwnck-3-0  40.1-1
ii  libxfce4panel-2.0-4  4.16.5-1
ii  libxfce4ui-2-0   4.16.1-1
ii  libxfce4util74.16.0-1
ii  libxfconf-0-34.16.0-2

Versions of packages xfce4-pulseaudio-plugin recommends:
ii  pavucontrol  5.0-2
ii  pulseaudio   15.0+dfsg1-4+b1

xfce4-pulseaudio-plugin suggests no packages.
--- End Message ---
--- Begin Message ---
Source: xfce4-pulseaudio-plugin
Source-Version: 0.4.5-1
Done: Unit 193 

We believe that the bug you reported is fixed in the latest version of
xfce4-pulseaudio-plugin, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1019...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Unit 193  (supplier of updated xfce4-pulseaudio-plugin 
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: SHA384

Format: 1.8
Date: Fri, 30 Sep 2022 23:53:17 -0400
Source: xfce4-pulseaudio-plugin
Architecture: source
Version: 0.4.5-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Xfce Maintainers 
Changed-By: Unit 193 
Closes: 1019420
Changes:
 xfce4-pulseaudio-plugin (0.4.5-1) unstable; urgency=medium
 .
   [ Akbarkhon Variskhanov ]
   * Update upstream metadata
 .
   [ Unit 193 ]
   * New upstream version 0.4.5.
 - Use Source Output Info for recording indicator to reduce flickering
   (#81) and to hide it with pavucontrol (#80) (Closes: #1019420)
Checksums-Sha1:
 c6abeeba67ec5f542b97283dd7e761d23481199e 2383 
xfce4-pulseaudio-plugin_0.4.5-1.dsc
 c0a2e50c1075a800c82c60b1609ea7bd6e9abcc5 394671 
xfce4-pulseaudio-plugin_0.4.5.orig.tar.bz2
 b888ad5152e1f9f50929e495ab1bab5a6533f5da 3468 
xfce4-pulseaudio-plugin_0.4.5-1.debian.tar.xz
 a71c9e387519f89309a915030a1386ca15bd84d4 15919 
xfce4-pulseaudio-plugin_0.4.5-1_amd64.buildinfo
Checksums-Sha256:
 cda2af1d52eeac3014abadcfbe150610d1b8ad898d2425b1c303d9508618f142 2383 
xfce4-pulseaudio-plugin_0.4.5-1.dsc
 4425397dea6ba2599a91653dfb8ca91300faaf40be5bf5a73c3e6064bf13c115 394671 
xfce4-pulseaudio-plugin_0.4.5.orig.tar.bz2
 c678b417a6c18ce7b5699faf3794e0e6caf4be74f9f5f04e424ce247c44e1043 3468 
xfce4-pulseaudio-plugin_0.4.5-1.debian.tar.xz
 cdf4a488d3e7af936936632fc3631e93a2e709e7b198f35eceed0e7d17e960b7 15919 
xfce4-pulseaudio-plugin_0.4.5-1_amd64.buildinfo
Files:
 d9f2c7242705b1c77df46eaa830a87aa 2383 xfce optional 
xfce4-pulseaudio-plugin_0.4.5-1.dsc
 c6fe6cef01aa1786d388c51a6ed2ec5c 394671 xfce optional 

Bug#1021015: marked as done (tinyproxy: CVE-2022-40468)

[Debian Bug Tracking System]

Your message dated Sat, 01 Oct 2022 02:36:02 +
with message-id 
and subject line Bug#1021015: fixed in tinyproxy 1.11.1-2
has caused the Debian Bug report #1021015,
regarding tinyproxy: CVE-2022-40468
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.)


-- 
1021015: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1021015
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: tinyproxy
X-Debbugs-CC: t...@security.debian.org
Severity: important
Tags: security

Hi,

The following vulnerability was published for tinyproxy.

CVE-2022-40468[0]:
| Tinyproxy commit 84f203f and earlier does not process HTTP request
| lines in the process_request() function and is using uninitialized
| buffers. This vulnerability allows attackers to access sensitive
| information at system runtime.

https://github.com/tinyproxy/tinyproxy/issues/457
https://github.com/tinyproxy/tinyproxy/commit/3764b8551463b900b5b4e3ec0cd9bb9182191cb7

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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2022-40468
https://www.cve.org/CVERecord?id=CVE-2022-40468

Please adjust the affected versions in the BTS as needed.
--- End Message ---
--- Begin Message ---
Source: tinyproxy
Source-Version: 1.11.1-2
Done: Unit 193 

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

Debian distribution maintenance software
pp.
Unit 193  (supplier of updated tinyproxy 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: SHA384

Format: 1.8
Date: Fri, 30 Sep 2022 22:08:37 -0400
Source: tinyproxy
Architecture: source
Version: 1.11.1-2
Distribution: unstable
Urgency: medium
Maintainer: Mike Gabriel 
Changed-By: Unit 193 
Closes: 1021015
Changes:
 tinyproxy (1.11.1-2) unstable; urgency=medium
 .
   * d/tinyproxy.service: Change reload signal from SIGHUP to SIGUSR1.
   * d/p/0001-prevent-junk-from-showing-up-in-error-page-in-invali.patch:
 - Grab upstream commit to fix a potential leak of left-over heap data if
   custom error page templates are used. (Closes: #1021015, CVE-2022-40468)
Checksums-Sha1:
 849725233ccef612108d3e50002095e0b7cc3a23 2017 tinyproxy_1.11.1-2.dsc
 215fc3011d16506e26c8f34cb51a34e8378ce391 182080 tinyproxy_1.11.1.orig.tar.xz
 7e2fc75e1aa341dcbb8ff9f7fad38b55ce207a7e 23348 tinyproxy_1.11.1-2.debian.tar.xz
 6cecde38f71eabc30f94f5b59bfab1167319b4d0 7014 
tinyproxy_1.11.1-2_amd64.buildinfo
Checksums-Sha256:
 44bfa5cacfaebc780420a4e60ff1d5aca7f5191bbd5aa4d8faf6bd3a477106fa 2017 
tinyproxy_1.11.1-2.dsc
 d66388448215d0aeb90d0afdd58ed00386fb81abc23ebac9d80e194fceb40f7c 182080 
tinyproxy_1.11.1.orig.tar.xz
 0eb27e20a8bb2840be68750de5908b95f1a27513fdb9b7d525fdadb344d43e38 23348 
tinyproxy_1.11.1-2.debian.tar.xz
 b1cd9f346ad44e331c2ad23ee51737f2f3866047178187f27af5f807f163deb2 7014 
tinyproxy_1.11.1-2_amd64.buildinfo
Files:
 39accd353b10ec8a2f37953539dd62bf 2017 web optional tinyproxy_1.11.1-2.dsc
 19cad9f7c3d45f477a7333f2d8babb62 182080 web optional 
tinyproxy_1.11.1.orig.tar.xz
 a48716fda230e23f1476bada25ff7083 23348 web optional 
tinyproxy_1.11.1-2.debian.tar.xz
 5e9def5e1cb5202d28fc780b4adc636c 7014 web optional 
tinyproxy_1.11.1-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCQAdFiEEjbPlhoZdK0orGFpcUAHhsJqjdEsFAmM3osEACgkQUAHhsJqj
dEuYRw//Ss+E1TX9g0s4PLFk/xYHPrMIRukg95KuIVjD6H8l7jhAPcGtHl/I3ga8
KUsV4qj1Wn7sp+MqQA052cLQDdmbWAhmBXbGC71cb/4WHGihTZyRwlkIhMvwwtET
5vEa6oA1+JH4JzTIkH3uHfISfBUpMCnGtZaiqe9OaDPJJ5wglj7aH9FJTzESTiiq
c12IMZJM9kxa7k7hUdKNyLYCelMPu9rMUpOyeODqvnzWFyTLAijFcEkX8Cqz9n9b
xNY6EJCCG/PBEWxN5jGlLDL6jbRfXl8tFFuiQcOyEivUaZDbyX6IlpmTSN8dryJB
nvZg6/0o4nxnQhP4kgcIuR5DmcIgeXSvaVxmS/rO0QP9kkKQSXkT1Q61Z6SXj2TS
x69ZJLrq8zF/SQy3DR7ppkgwIHr7h5PDE52tz98hehax5EKbSlEGxxu3Qm/3y9XG
ZYsj0cnCzvzxNsuk93Lg2PFSXAbrGRc8BCIzlwHoGDL/eytRYdJb4GwKZ6LpfHg5
jX6gjv56dp2vwGB64w15dBe9yinZ5hC1MlQO9KZIUv4LAHcnnKp3TG0N+CrJvc8Q
KHfiCHtAXlq/XEf8T1HwsiwX0tqGZgZaHJrv20JS+6++5vdb+YIcyRxxoYzRmEwL

Bug#990004: marked as done (support aliases by default or manual for suite names)

[Debian Bug Tracking System]

Your message dated Sat, 1 Oct 2022 01:53:21 +0200
with message-id 
and subject line Re: support aliases by default or manual for suite names
has caused the Debian Bug report #990004,
regarding support aliases by default or manual for suite names
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.)


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

Package: debspawn
Version: 0.5.0-1
Severity: wishlist

I have a container named sid-amd64 but it cannot be used if I mention 
suite as unstable. I think it would be a good idea to have this mapping 
by default for official names.


$ debspawn build unstable
[sudo] password for pravi:
ERROR: The container image for "unstable-amd64" does not exist. Please 
create it first.

$ debspawn list
[sid-amd64]
Architecture = amd64
Suite = sid
Size = 234.6MiB
--- End Message ---
--- Begin Message ---

Source: debspawn
Source-Version: 0.5.1-1
Done: Matthias Klumpp 

Hi!
This issue was actually already addressed in debspawn 0.5.1, but somehow 
this bug report fell through the cracks.
Images can now have arbitrary names (but if none is given, they will 
pick the suite name by default).


Cheers,
   Matthias--- End Message ---

Bug#978703: marked as done (gives strange error messages on outdated images)

[Debian Bug Tracking System]

Your message dated Sat, 1 Oct 2022 01:50:23 +0200
with message-id 

and subject line Re: Bug#978703: gives strange error messages on outdated images
has caused the Debian Bug report #978703,
regarding gives strange error messages on outdated images
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.)


-- 
978703: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=978703
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: debspawn
Version: 0.4.1-1
Severity: minor

Hi,

I recently tried to use debspawn build building into a slightly outdated
image of Debian sid and received a message that dsrun didn't like the
"--suite sid" option that was given to it. Updating the image solved the
issue for me.

I suspect that the "outside" debspawn calls things that are inside the
image, and while the outside debspawn was a 0.4.1, the inside was still
at 0.4.0 or even older and the interface between the outside and inside
code changed with the 0.4.0 to 0.4.1 transition. If my suspicion is
true, than this might also apply to images of testing or stable, but
without the possibility of just fixing this by updating the image.

I understand that this issue is probably hard to fix, but if it doesn't
seem possible to just inject the code needed on the inside from the
outside at run time (therefore forcing them to be in sync, but possibly
introducing python version issues) then there should be at least a more
helpful error message than just bombing out with a usage message of an
internal tool.

Greetings
Marc



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

Kernel: Linux 5.10.2-zgws1 (SMP w/12 CPU threads)
Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8), LANGUAGE=en
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages debspawn depends on:
ii  debootstrap1.0.123
ii  python33.9.1-1
ii  python3-toml   0.10.1-1
ii  systemd-container  247.2-2
ii  zstd   1.4.5+dfsg-4

Versions of packages debspawn recommends:
ii  build-essential  12.8
ii  devscripts   2.20.5

Versions of packages debspawn suggests:
ii  sudo  1.9.4p2-1

-- no debconf information
--- End Message ---
--- Begin Message ---
Hi!
I'm closing this issue, as there isn't much we can do about it
retroactively, and it shouldn't happen this way again in future, as
the respective code is now able to either fix the found issue or at
the very least give a better error message :-)

Cheers,
Matthias--- End Message ---

Bug#1008422: marked as done (jupyter-notebook: FTBFS: Module not found: Error: Can't resolve './../../../buffer' in '/<>/node_modules/postcss/lib')

[Debian Bug Tracking System]

Your message dated Fri, 30 Sep 2022 23:51:01 +
with message-id 
and subject line Bug#1008422: fixed in jupyter-notebook 6.4.12-2
has caused the Debian Bug report #1008422,
regarding jupyter-notebook: FTBFS: Module not found: Error: Can't resolve 
'./../../../buffer' in '/<>/node_modules/postcss/lib'
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.)


-- 
1008422: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008422
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: jupyter-notebook
Version: 6.4.8-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220326 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> dh_auto_build --buildsystem nodejs
> Found debian/nodejs/additional_components
> Adding component(s): @jupyterlab/apputils
> Adding component(s): klona
> Adding component(s): parse-srcset
> Adding component(s): sanitize-html
> Adding component(s): @types/sanitize-html
> No build command found, searching known files
> Found debian/nodejs/@jupyterlab/apputils/build
>   cd ./\@jupyterlab/apputils && sh -ex 
> ../../debian/nodejs/\@jupyterlab/apputils/build
> + tsc -b
> Found debian/nodejs/klona/build
>   cd ./klona && sh -ex ../debian/nodejs/klona/build
> + mkdir dist
> + cp src/index.js dist/index.mjs
> + cp src/index.js dist/index.js
> + sed -i s/export // dist/index.js
> + echo \nexports.klona = klona;\n
> No build command found, searching known files
> No build command found, searching known files
> webpack
> Hash: 0b431f028a6abb800be1
> Version: webpack 4.43.0
> Time: 6068ms
> Built at: 03/26/2022 7:35:22 PM
>  1 asset
> Entrypoint main = index.js
>  [4] ./sanitize-html/index.js 27.8 KiB {0} [built]
> [13] source-map-js (ignored) 15 bytes {0} [built]
> [14] path (ignored) 15 bytes {0} [built]
> [31] ./terminal-highlight (ignored) 15 bytes {0} [built]
> [35] url (ignored) 15 bytes {0} [built]
> [40] multi regenerator-runtime/runtime @jupyterlab/apputils/lib/sanitizer 40 
> bytes {0} [built]
> [42] (webpack)/buildin/module.js 552 bytes {0} [built]
> [43] ./@jupyterlab/apputils/lib/sanitizer.js 39.9 KiB {0} [built]
> [57] ./klona/dist/index.mjs 2 KiB {0} [built]
> [60] ./parse-srcset/src/parse-srcset.js 11.7 KiB {0} [built]
> [62] /usr/share/nodejs/process/browser.js 4.96 KiB {0} [built]
> [65] fs (ignored) 15 bytes {0} [built]
> + 59 hidden modules
> 
> WARNING in configuration
> The 'mode' option has not been set, webpack will fallback to 'production' for 
> this value. Set 'mode' option to 'development' or 'production' to enable 
> defaults for each environment.
> You can also set it to 'none' to disable any default behavior. Learn more: 
> https://webpack.js.org/configuration/mode/
> 
> ERROR in ./node_modules/postcss/lib/map-generator.js
> Module not found: Error: Can't resolve './../../../buffer' in 
> '/<>/node_modules/postcss/lib'
>  @ ./node_modules/postcss/lib/map-generator.js 1:0-28
>  @ ./node_modules/postcss/lib/lazy-result.js
>  @ ./node_modules/postcss/lib/postcss.js
>  @ ./sanitize-html/index.js
>  @ ./@jupyterlab/apputils/lib/sanitizer.js
>  @ multi regenerator-runtime/runtime @jupyterlab/apputils/lib/sanitizer
> 
> ERROR in ./node_modules/postcss/lib/previous-map.js
> Module not found: Error: Can't resolve './../../../buffer' in 
> '/<>/node_modules/postcss/lib'
>  @ ./node_modules/postcss/lib/previous-map.js 1:0-28
>  @ ./node_modules/postcss/lib/fromJSON.js
>  @ ./node_modules/postcss/lib/postcss.js
>  @ ./sanitize-html/index.js
>  @ ./@jupyterlab/apputils/lib/sanitizer.js
>  @ multi regenerator-runtime/runtime @jupyterlab/apputils/lib/sanitizer
> make[1]: *** [debian/rules:130: override_dh_auto_build] Error 2


The full build log is available from:
http://qa-logs.debian.net/2022/03/26/jupyter-notebook_6.4.8-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 marking it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Source: jupyter-notebook
Source-Version: 6.4.12-2
Done: Gordon Ball 

We believe that the bug you reported is fixed in the latest version of
jupyter-notebook, which is due to 

Processed: your mail

[Debian Bug Tracking System]

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

> close 1013005
Bug #1013005 [src:onednn] onednn: ftbfs with GCC-12
Marked Bug as done
> thanks
Stopping processing here.

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

Bug#1014317: marked as done (ITP: yarsync -- file synchronization and backup tool)

[Debian Bug Tracking System]

Your message dated Fri, 30 Sep 2022 23:10:09 +
with message-id 
and subject line Bug#1014317: fixed in yarsync 0.1.1+deb-1
has caused the Debian Bug report #1014317,
regarding ITP: yarsync -- file synchronization and backup tool
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.)


-- 
1014317: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1014317
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: wnpp
Severity: wishlist
Owner: Josenilson Ferreira da Silva 
X-Debbugs-Cc: debian-de...@lists.debian.org, nilsonfsi...@hotmail.com

* Package name: yarsync
  Version : 0.1.1
  Upstream Author : Yaroslav Nikitenko .
* URL : https://github.com/ynikitenko/yarsync
* License : GPL3
  Programming Lang: Python
  Description : file synchronization and backup tool

 can be used to synchronize data between different hosts
 or locally. (eg for a backup drive).
 .
 provides a familiar git command interface when working with files.
--- End Message ---
--- Begin Message ---
Source: yarsync
Source-Version: 0.1.1+deb-1
Done: Josenilson Ferreira da Silva 

We believe that the bug you reported is fixed in the latest version of
yarsync, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1014...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Josenilson Ferreira da Silva  (supplier of updated 
yarsync package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 29 Aug 2022 10:00:21 +0530
Source: yarsync
Binary: yarsync
Architecture: source all
Version: 0.1.1+deb-1
Distribution: experimental
Urgency: medium
Maintainer: Debian Python Team 
Changed-By: Josenilson Ferreira da Silva 
Description:
 yarsync- file sync and backup too
Closes: 1014317
Changes:
 yarsync (0.1.1+deb-1) experimental; urgency=medium
 .
   * Initial release. (Closes: #1014317)
Checksums-Sha1:
 39e2925c3fee97cf9552ab8bc7d4144539dbad4a 2182 yarsync_0.1.1+deb-1.dsc
 2b22cd0125bf9fdce4bf61f83b6975e7e8cafc6e 91244 yarsync_0.1.1+deb.orig.tar.gz
 47188ee8bc15ee58587b8c996e6eca9f0b8156a7 3356 yarsync_0.1.1+deb-1.debian.tar.xz
 ff25a7b206f890c1ef8e8fea53928d9d2b8cf209 37588 yarsync_0.1.1+deb-1_all.deb
 ab8e2ef8c1d4a9a4d0757bc671a378b1331ce1c7 7557 
yarsync_0.1.1+deb-1_amd64.buildinfo
Checksums-Sha256:
 3219f83ece7c9167be5b3fc412401bf9b16362f4894257c5ebff95123508b970 2182 
yarsync_0.1.1+deb-1.dsc
 f334afb8df02cdf6880674000b495835c7674b3c26b8b6a0271068cf940b1117 91244 
yarsync_0.1.1+deb.orig.tar.gz
 92a8500b5fdaf3e53e76f9c352bc710b3900faf688e0bfbf8200c5add35559a7 3356 
yarsync_0.1.1+deb-1.debian.tar.xz
 306bddd85951a8bd9dadc547d59ba66d1cbdab49d86c5d0cc0b6a5cb74910dbe 37588 
yarsync_0.1.1+deb-1_all.deb
 504ac5f09ea6b7db8f1cc56c6b1913cf91b5aeccd539e740adac2e9ffdf8b04d 7557 
yarsync_0.1.1+deb-1_amd64.buildinfo
Files:
 01053dd9da4c4d7afff11dd6f331b255 2182 utils optional yarsync_0.1.1+deb-1.dsc
 985115a53f1628a9db0e0fe314093000 91244 utils optional 
yarsync_0.1.1+deb.orig.tar.gz
 c591a9ed7e9721c77cda7ef01ad6e056 3356 utils optional 
yarsync_0.1.1+deb-1.debian.tar.xz
 e719b21cd52f559cc61ba53d0068ff16 37588 utils optional 
yarsync_0.1.1+deb-1_all.deb
 532b8a0391accbe839b4662e157a36ad 7557 utils optional 
yarsync_0.1.1+deb-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJGBAEBCgAwFiEEPpmlJvXcwMu/HO6mALrnSzQzafEFAmM2eLoSHG5pbGVzaEBk
ZWJpYW4ub3JnAAoJEAC650s0M2nxjKoP/ilhKIkilCUnc4hjnoyNDOLjvUxYeIJ1
T1DXhp8lC2IbxMOR5EMKfVHMxZWQymsBGCAwJoJdCYFgUkifE/XMLve5F7bnWtta
7q49U6DpFaAul5tRrI5gbpfl58X42bk8rZna2/i+yzzZd5xbYHbF3a360WCYHpkA
6U/l2ExUnjP/fizTlPo24X8w4f9KSkTMYsrt5WWxYnWV93lMrIEPASIF+MSCq/Rn
wnijlsGLEeS1VssmIQ2h6Oyhy03PiJEeUVjR03UiAVw7iF4+iJ9ADHPbohuwF8Wj
8PzAGqmyChB1knZDFIY5LJmI/QiZ9+0JV8rEAOiixk8h6+TqjbNxgGZ/JeImwB8i
ulKhsquGsBhdh1/OLt3vKU07ntuQoRZVUK6RZWIS82WRK5kbwYVcy8tF2L3wMW+2
gjWqIRJOdnUfy8olcqD6NiimtLhafTVXAvUrG/t5BElxbvXv1kYuK8D+xAg94T3R
p6F1tEM+guM9p2DK9J0ROr2ZE8cV/pFWmFWiH6xsUD7n8nbWUtFRA2NioNimHAJU
A3pWCRnug71kujgGxSCiytJD4GdUmZXoySfMisW0Jj8wXKqBPyWqOCUSRctvy5Dn
QAvkncdzkkgv7WPHUO5aTgJoRlu4DXrj24pMhwNJOiBBmzPcpxMst8wNmu/aBvpT
YbQpsWa7EiQ2
=7Rm6
-END PGP SIGNATURE End Message ---

Bug#1020967: marked as done (New upstream version 5.1.2)

[Debian Bug Tracking System]

Your message dated Fri, 30 Sep 2022 22:25:00 +
with message-id 
and subject line Bug#1020967: fixed in nuspell 5.1.2-1
has caused the Debian Bug report #1020967,
regarding New upstream version 5.1.2
to be marked as done.

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

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


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

Dear Maintainer,
there is new upstream version available.
https://github.com/nuspell/nuspell/releases/tag/v5.1.2
Please update when possible.--- End Message ---
--- Begin Message ---
Source: nuspell
Source-Version: 5.1.2-1
Done: Thorsten Alteholz 

We believe that the bug you reported is fixed in the latest version of
nuspell, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1020...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Thorsten Alteholz  (supplier of updated nuspell 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: Fri, 30 Sep 2022 22:36:33 +0200
Source: nuspell
Architecture: source
Version: 5.1.2-1
Distribution: unstable
Urgency: medium
Maintainer: Thorsten Alteholz 
Changed-By: Thorsten Alteholz 
Closes: 1020967
Changes:
 nuspell (5.1.2-1) unstable; urgency=medium
 .
   * New upstream release. (Closes: #1020967)
Checksums-Sha1:
 56a26c88984588f29eab9213559824bdbab0d28d 2123 nuspell_5.1.2-1.dsc
 2fc6a4b1dba1f6f26d51add3bbe21addfb3e60b4 371092 nuspell_5.1.2.orig.tar.gz
 87f156c21d3c170b44a7364eecee2bd6282a0e47 8440 nuspell_5.1.2-1.debian.tar.xz
 6b48b5bdc271266814db2bbd3430784047b669bd 8155 nuspell_5.1.2-1_amd64.buildinfo
Checksums-Sha256:
 f34b14b1da9fbb8e5b97ed495e949741d552fc707bf2a4f32feea2b9bbb61b79 2123 
nuspell_5.1.2-1.dsc
 82f5f2faa82df30099555dca94b3a908d38fdba408e31e74535c523f7e6ea18d 371092 
nuspell_5.1.2.orig.tar.gz
 37fa8311203c6ba80da813050a2dc1ed4c4b5ce1abc40c49bfa5a75c161672e6 8440 
nuspell_5.1.2-1.debian.tar.xz
 e7aed7f66c2d2b8701fd2be0ed4fd82c634c20826418c54194a5b212636496ba 8155 
nuspell_5.1.2-1_amd64.buildinfo
Files:
 6db313a52888eea67a81d758d3c14759 2123 text optional nuspell_5.1.2-1.dsc
 8ca8e48cceb5c897df53c3a131b1ebe2 371092 text optional nuspell_5.1.2.orig.tar.gz
 c77a0fdb75d27baf06656172960c75f5 8440 text optional 
nuspell_5.1.2-1.debian.tar.xz
 2f8213bbdf27ac15cf53cffef776be24 8155 text optional 
nuspell_5.1.2-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQKnBAEBCgCRFiEEYgH7/9u94Hgi6ruWlvysDTh7WEcFAmM3ZsdfFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDYy
MDFGQkZGREJCREUwNzgyMkVBQkI5Njk2RkNBQzBEMzg3QjU4NDcTHGRlYmlhbkBh
bHRlaG9sei5kZQAKCRCW/KwNOHtYR//3EACuCCfp2hgEfQMHd0zF7Stlam/wqFEx
txEODK6N7oWRqaFqBwkiBWly7r6jTkrBfnM0rxKt0ywo3SRfz4CYEjaJCzzNg7pK
EvTt9PHyKPYp1G9tGQCNBvfiOon0YofdZa/wymHTUBlYsW9RE2QcKqul86crrLn6
8GwrUmweaDKXLXRaYJpOusHoFH/vjfAQ6oMnRK0J8jIn6FR9Ypg5a0nN5CekNfFq
A2PrG1RThivXD4ATrAjQ7O0krjF4qE5vH9qJ1JuyhUxTogSp26FFnRv6JPpy9WgC
IhTGc2DcMIaUwPXGaZeYhyCYSiA/qfxM+yeVBW8lSDFdke3p/TECZqel8XPqTrUS
stga3/lJfo7SY/Rjuha8z1dyBMYY0p2omrX1Ryt6ZtUP0UBReo7Iyx/NMIwK0a5c
o2vnrgJME1xCUeO02ROqh7oif3E/05oYHu6lVDakudRbh79WuUBaxlsyGH8IdtCB
W10B7/mhZqiP6k88wg7q/70q73nnzPuWHtOgarllgtPkJX4WD61t3DcAEVRKYGBj
gcXLfYS1sdWn9DXy/pJ9vaZ/f5OW/ifDslcUGo1XIVNgLvArcYmKtgpYS2f4BL8M
klbPr/FQVpOMuVHY4BA37g8t9glPJIanMS8MDQg2qLCsnDA0/Aa4bfrKT29GYTUd
smwQ3+X42pLzCg==
=Wvhx
-END PGP SIGNATURE End Message ---

Bug#997252: marked as done (qt-gstreamer: FTBFS: gatomic.h:113:19: error: argument 2 of ‘__atomic_load’ must not be a pointer to a ‘volatile’ type)

[Debian Bug Tracking System]

Your message dated Fri, 30 Sep 2022 22:25:08 +
with message-id 
and subject line Bug#997252: fixed in qt-gstreamer 1.2.0-5.2
has caused the Debian Bug report #997252,
regarding qt-gstreamer: FTBFS: gatomic.h:113:19: error: argument 2 of 
‘__atomic_load’ must not be a pointer to a ‘volatile’ type
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.)


-- 
997252: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997252
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: qt-gstreamer
Version: 1.2.0-5.1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs

Hi,

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


Relevant part (hopefully):
> cd /<>/obj-x86_64-linux-gnu/elements/gstqtvideosink && 
> /usr/bin/c++ -DGST_DISABLE_LOADSAVE -DGST_DISABLE_XML 
> -DPACKAGE=\"qt-gstreamer\" -DPACKAGE_NAME="\"QtGStreamer (Debian)\"" 
> -DPACKAGE_ORIGIN=\"https://packages.qa.debian.org/qt-gstreamer\; 
> -DPACKAGE_VERSION=\"1.2.0\" -DQTGLVIDEOSINK_NAME=qt5glvideosink 
> -DQTVIDEOSINK_NAME=qt5videosink -DQT_CORE_LIB -DQT_GUI_LIB -DQT_NETWORK_LIB 
> -DQT_NO_DEBUG -DQT_OPENGL_LIB -DQT_QMLMODELS_LIB -DQT_QML_LIB -DQT_QUICK_LIB 
> -DQT_WIDGETS_LIB -DQWIDGETVIDEOSINK_NAME=qwidget5videosink 
> -Dgstqt5videosink_EXPORTS 
> -I/<>/obj-x86_64-linux-gnu/elements/gstqtvideosink 
> -I/<>/elements/gstqtvideosink 
> -I/<>/obj-x86_64-linux-gnu/elements/gstqtvideosink/gstqt5videosink_autogen/include
>  -I/usr/include/gstreamer-1.0 -I/usr/include/glib-2.0 
> -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -isystem 
> /usr/include/x86_64-linux-gnu/qt5 -isystem 
> /usr/include/x86_64-linux-gnu/qt5/QtCore -isystem 
> /usr/lib/x86_64-linux-gnu/qt5/mkspecs/linux-g++ -isystem 
> /usr/include/x86_64-linux-gnu/qt5/QtGui -isystem 
> /usr/include/x86_64-linux-gnu/qt5/QtWidgets -isystem 
> /usr/include/x86_64-linux-gnu/qt5/QtQuick -isystem 
> /usr/include/x86_64-linux-gnu/qt5/QtQmlModels -isystem 
> /usr/include/x86_64-linux-gnu/qt5/QtQml -isystem 
> /usr/include/x86_64-linux-gnu/qt5/QtNetwork -isystem 
> /usr/include/x86_64-linux-gnu/qt5/QtOpenGL -g -O2 
> -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -Wall -Wextra 
> -Wformat-security -Wundef -Wpointer-arith -fno-common -O2 -g -DNDEBUG -fPIC   
> -pthread -I/usr/include/gstreamer-1.0 -I/usr/include/x86_64-linux-gnu 
> -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -fPIC 
> -MD -MT 
> elements/gstqtvideosink/CMakeFiles/gstqt5videosink.dir/gstqwidgetvideosink.cpp.o
>  -MF CMakeFiles/gstqt5videosink.dir/gstqwidgetvideosink.cpp.o.d -o 
> CMakeFiles/gstqt5videosink.dir/gstqwidgetvideosink.cpp.o -c 
> /<>/elements/gstqtvideosink/gstqwidgetvideosink.cpp
> In file included from /usr/include/glib-2.0/glib/gthread.h:32,
>  from /usr/include/glib-2.0/glib/gasyncqueue.h:32,
>  from /usr/include/glib-2.0/glib.h:32,
>  from /usr/include/gstreamer-1.0/gst/gst.h:27,
>  from 
> /<>/elements/gstqtvideosink/gstqtvideosinkplugin.h:20,
>  from 
> /<>/elements/gstqtvideosink/gstqtvideosinkbase.h:21,
>  from 
> /<>/elements/gstqtvideosink/gstqtvideosinkbase.cpp:18:
> /<>/elements/gstqtvideosink/gstqtvideosinkbase.cpp: In static 
> member function ‘static GType GstQtVideoSinkBase::get_type()’:
> /usr/include/glib-2.0/glib/gatomic.h:113:19: error: argument 2 of 
> ‘__atomic_load’ must not be a pointer to a ‘volatile’ type
>   113 | __atomic_load (gapg_temp_atomic, _temp_newval, 
> __ATOMIC_SEQ_CST); \
>   | 
> ~~^~~
> /usr/include/glib-2.0/glib/gthread.h:260:7: note: in expansion of macro 
> ‘g_atomic_pointer_get’
>   260 | (!g_atomic_pointer_get (location) && \
>   |   ^~~~
> /<>/elements/gstqtvideosink/gstqtvideosinkplugin.h:31:13: note: 
> in expansion of macro ‘g_once_init_enter’
>31 | if (g_once_init_enter(_data)) { \
>   | ^
> /<>/elements/gstqtvideosink/gstqtvideosinkplugin.h:56:5: note: 
> in expansion of macro ‘DEFINE_TYPE_FULL’
>56 | DEFINE_TYPE_FULL(cpp_type, #cpp_type "_qt5", parent_type, 
> Q_UNUSED)
>   | ^~~~
> /<>/elements/gstqtvideosink/gstqtvideosinkbase.cpp:32:1: note: 
> in expansion of macro ‘DEFINE_TYPE’
>32 | DEFINE_TYPE(GstQtVideoSinkBase, GST_TYPE_VIDEO_SINK)
>   | ^~~
> make[4]: *** 
> 

Bug#906882: marked as done (libqt5gstreamer-dev: pkg-config fails unless libgstreamer-plugins-base1.0-dev is also installed)

[Debian Bug Tracking System]

Your message dated Fri, 30 Sep 2022 22:25:08 +
with message-id 
and subject line Bug#906882: fixed in qt-gstreamer 1.2.0-5.2
has caused the Debian Bug report #906882,
regarding libqt5gstreamer-dev: pkg-config fails unless 
libgstreamer-plugins-base1.0-dev is also installed
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.)


-- 
906882: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906882
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libqt5gstreamer-dev
Version: 1.2.0-5
Severity: normal

* aptitude install libqt5gstreamer-dev
* pkg-config --cflags Qt5GStreamer-1.0

  /
  | Package gstreamer-audio-1.0 was not found in the pkg-config search path.
  | Perhaps you should add the directory containing `gstreamer-audio-1.0.pc'
  | to the PKG_CONFIG_PATH environment variable
  | Package 'gstreamer-audio-1.0', required by 'Qt5GStreamer-1.0', not found
  \

* aptitude install libgstreamer-plugins-base1.0-dev
* pkg-config --cflags Qt5GStreamer-1.0

  (now works)

This package should have a dependency (at least Recommends) on
libgstreamer-plugins-base1.0-dev, otherwise its pkg-config file is
unusable.

Alternatively, perhaps the pc files need to be shuffled between packages?

-- System Information:
Debian Release: buster/sid
  APT prefers testing
  APT policy: (900, 'testing'), (900, 'stable'), (400, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386, armel

Kernel: Linux 4.17.0-1-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages libqt5gstreamer-dev depends on:
ii  libboost-dev1.62.0.1
ii  libqt5glib-2.0-01.2.0-5
ii  libqt5gstreamer-1.0-0   1.2.0-5
ii  libqt5gstreamerquick-1.0-0  1.2.0-5
ii  libqt5gstreamerui-1.0-0 1.2.0-5
ii  libqt5gstreamerutils-1.0-0  1.2.0-5
ii  qtbase5-dev 5.11.1+dfsg-6

libqt5gstreamer-dev recommends no packages.

Versions of packages libqt5gstreamer-dev suggests:
pn  qtgstreamer-doc  

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: qt-gstreamer
Source-Version: 1.2.0-5.2
Done: Sebastian Ramacher 

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

Debian distribution maintenance software
pp.
Sebastian Ramacher  (supplier of updated qt-gstreamer 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 28 Sep 2022 23:40:14 +0200
Source: qt-gstreamer
Architecture: source
Version: 1.2.0-5.2
Distribution: unstable
Urgency: medium
Maintainer: Debian/Kubuntu KDE Extras Team 

Changed-By: Sebastian Ramacher 
Closes: 906882 997252
Changes:
 qt-gstreamer (1.2.0-5.2) unstable; urgency=medium
 .
   * Non-maintainer upload.
 .
   [ Simon McVittie ]
   * debian/patches: Fix arguments passed to __atomic_load (Closes: #997252)
   * debian/control: Add missing dependencies on Glib/GStreamer -dev packages
 (Closes: #906882)
Checksums-Sha1:
 b3795dbd4906ac0bc4c4281713760f7279006fde 2886 qt-gstreamer_1.2.0-5.2.dsc
 ecfb955823d26b70f56e9eccf8e7f1fd298fb969 18520 
qt-gstreamer_1.2.0-5.2.debian.tar.xz
Checksums-Sha256:
 88b3c74c9a31c6786b54f7efc8b325d4ccceafe7ef9ebec7f6e88c6ca43d65e6 2886 
qt-gstreamer_1.2.0-5.2.dsc
 8d75b28f4d4bbebc9acaf2a243a5c0b8478c2be8aabcf83d104f2a2880e849c4 18520 
qt-gstreamer_1.2.0-5.2.debian.tar.xz
Files:
 384b17e1f3233aca176cc15b43399075 2886 libs optional qt-gstreamer_1.2.0-5.2.dsc
 5b93ade2a7f74cfdb69f5236ae281160 18520 libs optional 
qt-gstreamer_1.2.0-5.2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEE94y6B4F7sUmhHTOQafL8UW6nGZMFAmM0wQUACgkQafL8UW6n
GZMwmxAAnRJIKCPX7brXwrD6J2DUBcfIjvTiIKRHxqjnbpvuf/qwoWuqThwWQuN4
/KUJ3LzD3aD9EoDqdSAJ7ngAxEWk8KcRbj1cyhO4+QrD2sX1H0Uih67Qpw3Wl9Qc
5Fy3BnUO3QrZgubpuSx+ou9A4pnWl1tXmHHQS8d2/pOfCDVHxeU6308fxd1+/VmB
E8X3WmJD65gwRrQoXdB9BobXElyXLaexSW43aT0YcrTKkhPAHesADKeSAy6VyJ+p
1Kvp2JKXM0bmxTbrL3IJZ3XwcsMSxYaZlE+W2z9JzRzfLwEC9nuAfNL8XBJQDyKc

Bug#1021029: marked as done (src:rust-resource-proof: fails to migrate to testing for too long: autopkgtest regression)

[Debian Bug Tracking System]

Your message dated Fri, 30 Sep 2022 22:25:17 +
with message-id 
and subject line Bug#1021029: fixed in rust-resource-proof 1.0.39-3
has caused the Debian Bug report #1021029,
regarding src:rust-resource-proof: fails to migrate to testing for too long: 
autopkgtest regression
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.)


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

Source: rust-resource-proof
Version: 1.0.38-2
Severity: serious
Control: close -1 1.0.39-2
Tags: sid bookworm
User: release.debian@packages.debian.org
Usertags: out-of-sync

Dear maintainer(s),

The Release Team considers packages that are out-of-sync between testing 
and unstable for more than 60 days as having a Release Critical bug in 
testing [1]. Your package src:rust-resource-proof has been trying to 
migrate for 61 days [2]. Hence, I am filing this bug. The current 
version is blocked from migrating because it has an autopkgtest regression.


If a package is out of sync between unstable and testing for a longer 
period, this usually means that bugs in the package in testing cannot be 
fixed via unstable. Additionally, blocked packages can have impact on 
other packages, which makes preparing for the release more difficult. 
Finally, it often exposes issues with the package and/or
its (reverse-)dependencies. We expect maintainers to fix issues that 
hamper the migration of their package in a timely manner.


This bug will trigger auto-removal when appropriate. As with all new 
bugs, there will be at least 30 days before the package is auto-removed.


I have immediately closed this bug with the version in unstable, so if 
that version or a later version migrates, this bug will no longer affect 
testing. I have also tagged this bug to only affect sid and bookworm, so 
it doesn't affect (old-)stable.


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.


Paul

[1] https://lists.debian.org/debian-devel-announce/2020/02/msg5.html
[2] https://qa.debian.org/excuses.php?package=rust-resource-proof



OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: rust-resource-proof
Source-Version: 1.0.39-3
Done: Jonas Smedegaard 

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

Debian distribution maintenance software
pp.
Jonas Smedegaard  (supplier of updated rust-resource-proof 
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: Fri, 30 Sep 2022 23:58:35 +0200
Source: rust-resource-proof
Architecture: source
Version: 1.0.39-3
Distribution: unstable
Urgency: medium
Maintainer: Jonas Smedegaard 
Changed-By: Jonas Smedegaard 
Closes: 1021029
Changes:
 rust-resource-proof (1.0.39-3) unstable; urgency=medium
 .
   * extend patch to also relax clap versioning;
 closes: bug#1021029, thanks to Paul Gevers
Checksums-Sha1:
 c1aad2d0e169062782cb4bd0fab112a6045f970c 2343 rust-resource-proof_1.0.39-3.dsc
 2844e0cb44b9a74c56380d87d0ea7587535eca6b 5008 
rust-resource-proof_1.0.39-3.debian.tar.xz
 3992d2892e7b9f4ec9242091e09bcc42e986f6e6 11659 
rust-resource-proof_1.0.39-3_amd64.buildinfo
Checksums-Sha256:
 8621b618a9317ef392056e10f0fded298aa1add2dc6092a2df5fa6902605195d 2343 
rust-resource-proof_1.0.39-3.dsc
 1a1097819c10c5db3b8f55976aada1f87eaf35b9d33cb6e79a145f291b9ae777 5008 
rust-resource-proof_1.0.39-3.debian.tar.xz
 b0383ed31f4082a17d69d9cad31eaf50d8a9bdab7dc332e0ce881780aace245c 11659 
rust-resource-proof_1.0.39-3_amd64.buildinfo
Files:
 1e84d69e57243dec30c81484525c7256 2343 rust optional 
rust-resource-proof_1.0.39-3.dsc
 960bc8ab298c8410c8134e6a13e573e6 5008 rust optional 
rust-resource-proof_1.0.39-3.debian.tar.xz
 1fd3baf75d387657ec5946d89ffa1766 11659 rust optional 
rust-resource-proof_1.0.39-3_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmM3aNsACgkQLHwxRsGg

Bug#1016254: marked as done (lomiri-url-dispatcher: FTBFS: overlay-tracker-mir.cpp:95:45: error: variable ‘std::array urls’ has initializer but incomplete type)

[Debian Bug Tracking System]

Your message dated Fri, 30 Sep 2022 22:24:47 +
with message-id 
and subject line Bug#1016254: fixed in lomiri-url-dispatcher 0.1.0-8
has caused the Debian Bug report #1016254,
regarding lomiri-url-dispatcher: FTBFS: overlay-tracker-mir.cpp:95:45: error: 
variable ‘std::array urls’ has initializer but incomplete type
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.)


-- 
1016254: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1016254
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: lomiri-url-dispatcher
Version: 0.1.0-7
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220728 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> cd /<>/obj-x86_64-linux-gnu/tests/googletest && /usr/bin/c++  
> -I/usr/src/googletest/googletest/include -I/usr/src/googletest/googletest -g 
> -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -Wall -Wpedantic 
> -Wextra -std=c++11 -fPIC -g -Wno-old-style-cast 
> -Wno-missing-field-initializers -Wno-ctor-dtor-privacy -Wno-switch-default 
> -Wall -Wshadow -Wno-error=dangling-else -DGTEST_HAS_PTHREAD=1 -fexceptions 
> -Wextra -Wno-unused-parameter -Wno-missing-field-initializers -MD -MT 
> /<>/obj-x86_64-linux-gnu/tests/googletest/CMakeFiles/gtest.dir/src/gtest-all.cc.o
>  -MF CMakeFiles/gtest.dir/src/gtest-all.cc.o.d -o 
> CMakeFiles/gtest.dir/src/gtest-all.cc.o -c 
> /usr/src/googletest/googletest/src/gtest-all.cc
> make[3]: Leaving directory '/<>/obj-x86_64-linux-gnu'
> [ 65%] Built target lib-test-no-main
> /<>/service/overlay-tracker-mir.cpp: In lambda function:
> /<>/service/overlay-tracker-mir.cpp:95:45: error: variable 
> ‘std::array urls’ has initializer but incomplete type
>95 | std::array urls { surl.c_str(), 
> nullptr };
>   | ^~~~
> make[3]: *** [service/CMakeFiles/dispatcher-lib.dir/build.make:121: 
> service/CMakeFiles/dispatcher-lib.dir/overlay-tracker-mir.cpp.o] Error 1


The full build log is available from:
http://qa-logs.debian.net/2022/07/28/lomiri-url-dispatcher_0.1.0-7_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20220728;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20220728=lu...@debian.org=1=1=1=1#results

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

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

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Source: lomiri-url-dispatcher
Source-Version: 0.1.0-8
Done: Mike Gabriel 

We believe that the bug you reported is fixed in the latest version of
lomiri-url-dispatcher, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1016...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Mike Gabriel  (supplier of updated lomiri-url-dispatcher 
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: Fri, 30 Sep 2022 23:51:42 +0200
Source: lomiri-url-dispatcher
Architecture: source
Version: 0.1.0-8
Distribution: unstable
Urgency: medium
Maintainer: Debian UBports Team 
Changed-By: Mike Gabriel 
Closes: 1016254
Changes:
 lomiri-url-dispatcher (0.1.0-8) unstable; urgency=medium
 .
   * debian/:
 + Update upstream Git repo URL.
   * debian/patches:
 + Add 0004_gcc-12-fix.patch. (Closes: #1016254).
Checksums-Sha1:
 6334e4146537142c43b207a24158dd4ba336417d 2923 lomiri-url-dispatcher_0.1.0-8.dsc
 ba57796090ab582a6319bb21e3cf9a10d60c3b66 10924 
lomiri-url-dispatcher_0.1.0-8.debian.tar.xz
 cd84a09bb4c2d1b6bb22ccf39a41a91d4ef02cb9 10786 
lomiri-url-dispatcher_0.1.0-8_source.buildinfo

Bug#1015783: marked as done (Please update jupyter-notebook to 6.4.12)

[Debian Bug Tracking System]

Your message dated Fri, 30 Sep 2022 20:39:42 +
with message-id 
and subject line Bug#1015783: fixed in jupyter-notebook 6.4.12-1
has caused the Debian Bug report #1015783,
regarding Please update jupyter-notebook to 6.4.12
to be marked as done.

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

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


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

Hello,

Please update jupyter-notebook to 6.4.12, and change the watch file to track 
the 6.4.x and later 6.5.x releases before the major update to version 7.

https://github.com/jupyter/notebook/tree/6.4.x
https://github.com/jupyter/notebook/tree/6.5.x

Quoting from https://github.com/jupyter/notebook#maintained-versions:

Maintained versions
We maintain the two most recently released major versions of Jupyter Notebook, 
Notebook v5 and Classic Notebook v6. After Notebook v7.0 is released, we will 
no longer maintain Notebook v5. All Notebook v5 users are strongly advised to 
upgrade to Classic Notebook v6 as soon as possible.

The Jupyter Notebook project is currently undertaking a transition to a more 
modern code base built from the ground-up using JupyterLab components and 
extensions.

There is a new stream of work which was submitted and then accepted as a 
Jupyter Enhancement Proposal (JEP) as part of the next version (v7): 
https://jupyter.org/enhancement-proposals/79-notebook-v7/notebook-v7.html

There is also a plan to continue maintaining Notebook v6 with bug and security 
fixes only, to ease the transition to Notebook v7: 
jupyter/notebook-team-compass#5 (comment)

Notebook v7
The next major version of Notebook will be based on:

JupyterLab components for the frontend
Jupyter Server for the Python server
This represents a significant change to the jupyter/notebook code base.

To learn more about Notebook v7: 
https://jupyter.org/enhancement-proposals/79-notebook-v7/notebook-v7.html

Classic Notebook v6
Maintenance and security-related issues are now being addressed in the 6.4.x 
branch.

A 6.5.x branch will be soon created and will depend on nbclassic for the 
HTML/JavaScript/CSS assets.

New features and continuous improvement is now focused on Notebook v7 (see 
section above).

Best,
Amr--- End Message ---
--- Begin Message ---
Source: jupyter-notebook
Source-Version: 6.4.12-1
Done: Gordon Ball 

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

Debian distribution maintenance software
pp.
Gordon Ball  (supplier of updated jupyter-notebook 
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: Fri, 30 Sep 2022 19:25:29 +
Source: jupyter-notebook
Architecture: source
Version: 6.4.12-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team 
Changed-By: Gordon Ball 
Closes: 1013272 1014771 1015783
Changes:
 jupyter-notebook (6.4.12-1) unstable; urgency=medium
 .
   [ Jerome Benoit ]
   * Remove myself from the Uploaders list.
 .
   [ Julien Puydt ]
   * Package new upstream (Closes: #1015783, #1013272, #1014771).
   * Refresh patches.
   * Add patch to drop dep on google caja.
   * Add missing build-depends.
Checksums-Sha1:
 a6c918d273593cc9b2023a05fd0fc1891efdab93 3751 jupyter-notebook_6.4.12-1.dsc
 775de8a2dbc8dc35c0415823cea95b0c4f73bfb9 8501209 
jupyter-notebook_6.4.12.orig.tar.gz
 8f33da119556a6c6f4869479a535e248b20a1ade 48772 
jupyter-notebook_6.4.12-1.debian.tar.xz
 a00a711bc9a87fdc52695f6d8efb25286b6bdb2d 23835 
jupyter-notebook_6.4.12-1_amd64.buildinfo
Checksums-Sha256:
 65bb106e7a727cd0c79cacef0d5688f8367929c24aa05db4e316b10d0274a7e2 3751 
jupyter-notebook_6.4.12-1.dsc
 5f98ee21f90d84620ab87bfa0b31a71f1dc03953305704ac056e62579d0e1618 8501209 
jupyter-notebook_6.4.12.orig.tar.gz
 4240d5b079f5e0bb6d90324f9bb1b9f5a634b264a7944d871a65b495d2dd6bae 48772 
jupyter-notebook_6.4.12-1.debian.tar.xz
 b9e721e9072a960b07be53c2f1bc4d2aba27a4247ded793b1f66e9991085a7d7 23835 
jupyter-notebook_6.4.12-1_amd64.buildinfo
Files:
 ed53e429d1118914d162fb632341a19a 3751 

Bug#1014771: marked as done (jupyter-notebook: CVE-2022-24758)

[Debian Bug Tracking System]

Your message dated Fri, 30 Sep 2022 20:39:42 +
with message-id 
and subject line Bug#1014771: fixed in jupyter-notebook 6.4.12-1
has caused the Debian Bug report #1014771,
regarding jupyter-notebook: CVE-2022-24758
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.)


-- 
1014771: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1014771
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: jupyter-notebook
X-Debbugs-CC: t...@security.debian.org
Severity: important
Tags: security

Hi,

The following vulnerability was published for jupyter-notebook.

CVE-2022-24758[0]:
| The Jupyter notebook is a web-based notebook environment for
| interactive computing. Prior to version 6.4.9, unauthorized actors can
| access sensitive information from server logs. Anytime a 5xx error is
| triggered, the auth cookie and other header values are recorded in
| Jupyter server logs by default. Considering these logs do not require
| root access, an attacker can monitor these logs, steal sensitive
| auth/cookie information, and gain access to the Jupyter server.
| Jupyter notebook version 6.4.x contains a patch for this issue. There
| are currently no known workarounds.

https://github.com/jupyter/notebook/security/advisories/GHSA-m87f-39q9-6f55
https://github.com/jupyter/notebook/commit/c219ce43c1ea25123fa70d264e7735bdf4585b1e
 (6.4.10)

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

For further information see:

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

Please adjust the affected versions in the BTS as needed.
--- End Message ---
--- Begin Message ---
Source: jupyter-notebook
Source-Version: 6.4.12-1
Done: Gordon Ball 

We believe that the bug you reported is fixed in the latest version of
jupyter-notebook, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1014...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Gordon Ball  (supplier of updated jupyter-notebook 
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: Fri, 30 Sep 2022 19:25:29 +
Source: jupyter-notebook
Architecture: source
Version: 6.4.12-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team 
Changed-By: Gordon Ball 
Closes: 1013272 1014771 1015783
Changes:
 jupyter-notebook (6.4.12-1) unstable; urgency=medium
 .
   [ Jerome Benoit ]
   * Remove myself from the Uploaders list.
 .
   [ Julien Puydt ]
   * Package new upstream (Closes: #1015783, #1013272, #1014771).
   * Refresh patches.
   * Add patch to drop dep on google caja.
   * Add missing build-depends.
Checksums-Sha1:
 a6c918d273593cc9b2023a05fd0fc1891efdab93 3751 jupyter-notebook_6.4.12-1.dsc
 775de8a2dbc8dc35c0415823cea95b0c4f73bfb9 8501209 
jupyter-notebook_6.4.12.orig.tar.gz
 8f33da119556a6c6f4869479a535e248b20a1ade 48772 
jupyter-notebook_6.4.12-1.debian.tar.xz
 a00a711bc9a87fdc52695f6d8efb25286b6bdb2d 23835 
jupyter-notebook_6.4.12-1_amd64.buildinfo
Checksums-Sha256:
 65bb106e7a727cd0c79cacef0d5688f8367929c24aa05db4e316b10d0274a7e2 3751 
jupyter-notebook_6.4.12-1.dsc
 5f98ee21f90d84620ab87bfa0b31a71f1dc03953305704ac056e62579d0e1618 8501209 
jupyter-notebook_6.4.12.orig.tar.gz
 4240d5b079f5e0bb6d90324f9bb1b9f5a634b264a7944d871a65b495d2dd6bae 48772 
jupyter-notebook_6.4.12-1.debian.tar.xz
 b9e721e9072a960b07be53c2f1bc4d2aba27a4247ded793b1f66e9991085a7d7 23835 
jupyter-notebook_6.4.12-1_amd64.buildinfo
Files:
 ed53e429d1118914d162fb632341a19a 3751 python optional 
jupyter-notebook_6.4.12-1.dsc
 9640422b192c2d144950811cd60b1574 8501209 python optional 
jupyter-notebook_6.4.12.orig.tar.gz
 60a9df9d5f9c62abf1a1e4917b246bf5 48772 python optional 
jupyter-notebook_6.4.12-1.debian.tar.xz
 4bda1b4950dcedac456c26a4ce807a88 23835 python optional 
jupyter-notebook_6.4.12-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEE6PwpXIa418BJ+Xuno12v+60p6N4FAmM3ScoACgkQo12v+60p
6N7tkA//ToZ3EbqSROFXezs9uRi8CcSJpIGJ9IwPx4asiC7JhI6vZF2ctP9pppG1
Z4ukBDTWSj0UflPGJzHwLVEUD9ivJPauR4UM2bdB70O2vEEZB9JI0A596ICn35xO

Bug#1013272: marked as done (jupyter-notebook: CVE-2022-29238)

[Debian Bug Tracking System]

Your message dated Fri, 30 Sep 2022 20:39:42 +
with message-id 
and subject line Bug#1013272: fixed in jupyter-notebook 6.4.12-1
has caused the Debian Bug report #1013272,
regarding jupyter-notebook: CVE-2022-29238
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.)


-- 
1013272: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013272
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: jupyter-notebook
X-Debbugs-CC: t...@security.debian.org
Severity: important
Tags: security

Hi,

The following vulnerability was published for jupyter-notebook.

CVE-2022-29238[0]:
| Jupyter Notebook is a web-based notebook environment for interactive
| computing. Prior to version 6.4.12, authenticated requests to the
| notebook server with `ContentsManager.allow_hidden = False` only
| prevented listing the contents of hidden directories, not accessing
| individual hidden files or files in hidden directories (i.e. hidden
| files were 'hidden' but not 'inaccessible'). This could lead to
| notebook configurations allowing authenticated access to files that
| may reasonably be expected to be disallowed. Because fully
| authenticated requests are required, this is of relatively low impact.
| But if a server's root directory contains sensitive files whose only
| protection from the server is being hidden (e.g. `~/.ssh` while
| serving $HOME), then any authenticated requests could access files if
| their names are guessable. Such contexts also necessarily have full
| access to the server and therefore execution permissions, which also
| generally grants access to all the same files. So this does not
| generally result in any privilege escalation or increase in
| information access, only an additional, unintended means by which the
| files could be accessed. Version 6.4.12 contains a patch for this
| issue. There are currently no known workarounds.

https://github.com/jupyter/notebook/security/advisories/GHSA-v7vq-3x77-87vg

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

For further information see:

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

Please adjust the affected versions in the BTS as needed.
--- End Message ---
--- Begin Message ---
Source: jupyter-notebook
Source-Version: 6.4.12-1
Done: Gordon Ball 

We believe that the bug you reported is fixed in the latest version of
jupyter-notebook, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1013...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Gordon Ball  (supplier of updated jupyter-notebook 
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: Fri, 30 Sep 2022 19:25:29 +
Source: jupyter-notebook
Architecture: source
Version: 6.4.12-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team 
Changed-By: Gordon Ball 
Closes: 1013272 1014771 1015783
Changes:
 jupyter-notebook (6.4.12-1) unstable; urgency=medium
 .
   [ Jerome Benoit ]
   * Remove myself from the Uploaders list.
 .
   [ Julien Puydt ]
   * Package new upstream (Closes: #1015783, #1013272, #1014771).
   * Refresh patches.
   * Add patch to drop dep on google caja.
   * Add missing build-depends.
Checksums-Sha1:
 a6c918d273593cc9b2023a05fd0fc1891efdab93 3751 jupyter-notebook_6.4.12-1.dsc
 775de8a2dbc8dc35c0415823cea95b0c4f73bfb9 8501209 
jupyter-notebook_6.4.12.orig.tar.gz
 8f33da119556a6c6f4869479a535e248b20a1ade 48772 
jupyter-notebook_6.4.12-1.debian.tar.xz
 a00a711bc9a87fdc52695f6d8efb25286b6bdb2d 23835 
jupyter-notebook_6.4.12-1_amd64.buildinfo
Checksums-Sha256:
 65bb106e7a727cd0c79cacef0d5688f8367929c24aa05db4e316b10d0274a7e2 3751 
jupyter-notebook_6.4.12-1.dsc
 5f98ee21f90d84620ab87bfa0b31a71f1dc03953305704ac056e62579d0e1618 8501209 
jupyter-notebook_6.4.12.orig.tar.gz
 4240d5b079f5e0bb6d90324f9bb1b9f5a634b264a7944d871a65b495d2dd6bae 48772 
jupyter-notebook_6.4.12-1.debian.tar.xz
 b9e721e9072a960b07be53c2f1bc4d2aba27a4247ded793b1f66e9991085a7d7 23835 
jupyter-notebook_6.4.12-1_amd64.buildinfo
Files:
 

Bug#1007960: marked as done (RFP: pedidos de empacotamento)

[Debian Bug Tracking System]

Your message dated Fri, 30 Sep 2022 22:29:45 +0200
with message-id <20220930202945.gfg3k4q4bzl2c...@jwilk.net>
and subject line Re: Bug#1007960: RFP: signal-desktop
has caused the Debian Bug report #1007960,
regarding RFP: pedidos de empacotamento
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.)


-- 
1007960: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1007960
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: wnpp
Severity: wishlist
Owner: https://github.com/signalapp/Signal-Desktop


* Package name: Signal-Desktop
  Version : N/A
  Upstream Author : https://github.com/signalapp/Signal-Desktop
* URL : https://github.com/signalapp/Signal-Desktop
* License : AGPLv3:
  Description : Signal — Private Messenger for Windows, Mac, and Linux


Signal-desktop is an open source messenger that would be nice to have
it packaged for debian

-- 
Wellington Almeida
Rio de Janeiro - Brasil
--- End Message ---
--- Begin Message ---

Closing as a duplicate of #842943.

(I wanted to merge the bugs, but that didn't work out, presumably 
because of #962175.)


--
Jakub Wilk--- End Message ---

Bug#1018777: marked as done (pari-nflistdata: Unhandled data compression by dh_compress)

[Debian Bug Tracking System]

Your message dated Fri, 30 Sep 2022 19:43:54 +0200
with message-id 
and subject line Re: Bug#1018777: pari-nflistdata: Unhandled data compression 
by dh_compress
has caused the Debian Bug report #1018777,
regarding pari-nflistdata: Unhandled data compression by dh_compress
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.)


-- 
1018777: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1018777
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: pari-nflistdata
Version: 0.20220729-1
Severity: important
X-Debbugs-CC: ballo...@debian.org

Dear Debian pari-nflistdata package maintainer,

As seen in https://packages.debian.org/sid/all/pari-nflistdata/filelist ,
some files are compressed into .gz file (QT --> QT.gz). I believe this is
due to automatic compression made by dh_compress.

The unhandled compression may make these data unavailable if the
uncompressed version were to be used. Please consider adjusting the
compression handling in debian/rules file.

Thanks,
Boyuan Yang


signature.asc
Description: This is a digitally signed message part
--- End Message ---
--- Begin Message ---
On Thu, Sep 08, 2022 at 10:03:42AM +0200, Bill Allombert wrote:
> > Package: pari-nflistdata
> > Version: 0.20220729-1
> > Severity: important
> > X-Debbugs-CC: ballo...@debian.org
> > 
> > Dear Debian pari-nflistdata package maintainer,
> > 
> > As seen in https://packages.debian.org/sid/all/pari-nflistdata/filelist ,
> > some files are compressed into .gz file (QT --> QT.gz). I believe this is
> > due to automatic compression made by dh_compress.
> > 
> > The unhandled compression may make these data unavailable if the
> > uncompressed version were to be used. Please consider adjusting the
> > compression handling in debian/rules file.
> 
> Dear Boyuan Yang,
> 
> Fundamentally I do not understand your sentence. 
> What is "unhandled compression", what would the "uncompressed version" to be 
> used ?
> What is the actual problem you are reporting ?
> 
> I have uploaded pari 2.15.0~pre1 to experimental and it passes it test-suite, 
> so
> pari-nflistdata is read correctly.

pari 2.15.0 is in unstable, so I close this report.

Cheers,
-- 
Bill. 

Imagine a large red swirl here.--- End Message ---

Bug#1017220: marked as done (camitk: FTBFS: unsatisfiable build-dependencies)

[Debian Bug Tracking System]

Your message dated Fri, 30 Sep 2022 19:50:36 +
with message-id 
and subject line Bug#1017220: fixed in camitk 5.0.2-4
has caused the Debian Bug report #1017220,
regarding camitk: FTBFS: unsatisfiable build-dependencies
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.)


-- 
1017220: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017220
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: camitk
Version: 5.0.2-3
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220813 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> +--+
> | Install package build dependencies  
>  |
> +--+
> 
> 
> Setup apt archive
> -
> 
> Merged Build-Depends: debhelper-compat (= 13), cmake, libvtk7-dev, 
> libvtk7-qt-dev, qtbase5-dev, libqt5xmlpatterns5-dev, libqt5opengl5-dev, 
> qttools5-dev-tools, xsdcxx, libinsighttoolkit5-dev, libfftw3-dev, 
> libgdcm-dev, libgdcm-tools, libvtkgdcm-dev, xvfb, xauth, doxygen, graphviz, 
> debhelper, build-essential, fakeroot
> Filtered Build-Depends: debhelper-compat (= 13), cmake, libvtk7-dev, 
> libvtk7-qt-dev, qtbase5-dev, libqt5xmlpatterns5-dev, libqt5opengl5-dev, 
> qttools5-dev-tools, xsdcxx, libinsighttoolkit5-dev, libfftw3-dev, 
> libgdcm-dev, libgdcm-tools, libvtkgdcm-dev, xvfb, xauth, doxygen, graphviz, 
> debhelper, build-essential, fakeroot
> dpkg-deb: building package 'sbuild-build-depends-main-dummy' in 
> '/<>/apt_archive/sbuild-build-depends-main-dummy.deb'.
> Ign:1 copy:/<>/apt_archive ./ InRelease
> Get:2 copy:/<>/apt_archive ./ Release [957 B]
> Ign:3 copy:/<>/apt_archive ./ Release.gpg
> Get:4 copy:/<>/apt_archive ./ Sources [481 B]
> Get:5 copy:/<>/apt_archive ./ Packages [563 B]
> Fetched 2001 B in 0s (147 kB/s)
> Reading package lists...
> Reading package lists...
> 
> Install main build dependencies (apt-based resolver)
> 
> 
> Installing build dependencies
> Reading package lists...
> Building dependency tree...
> Some packages could not be installed. This may mean that you have
> requested an impossible situation or if you are using the unstable
> distribution that some required packages have not yet been created
> or been moved out of Incoming.
> The following information may help to resolve the situation:
> 
> The following packages have unmet dependencies:
> E: Unable to correct problems, you have held broken packages.
>  sbuild-build-depends-main-dummy : Depends: libinsighttoolkit5-dev but it is 
> not installable
> apt-get failed.


The full build log is available from:
http://qa-logs.debian.net/2022/08/13/camitk_5.0.2-3_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20220813;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20220813=lu...@debian.org=1=1=1=1#results

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

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

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Source: camitk
Source-Version: 5.0.2-4
Done: Étienne Mollier 

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

Debian distribution maintenance software
pp.
Étienne Mollier  (supplier of updated camitk 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: Fri, 30 Sep 2022 21:09:45 +0200
Source: camitk
Architecture: source

Bug#1013040: marked as done (sleef: ftbfs with GCC-12)

[Debian Bug Tracking System]

Your message dated Fri, 30 Sep 2022 19:34:17 +
with message-id 
and subject line Bug#1013040: fixed in sleef 3.5.1-2
has caused the Debian Bug report #1013040,
regarding sleef: ftbfs with GCC-12
to be marked as done.

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

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


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

[This bug is targeted to the upcoming bookworm release]

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

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

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

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

  apt-get -t=experimental install g++ 

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

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

[...]
28: atanf_u1 : OK
27: tanhf_u35 : OK
27: asinhf : OK
27: acoshf : OK
28: atan2f : OK
27: atanhf : OK
27: exp2f : OK
28: atan2f_u1 : OK
27: exp10f : OK
28: sinhf : OK
28: coshf : OK
27: exp2f_u35 : OK
28: tanhf : OK
27: exp10f_u35 : OK
28: sinhf_u35 : OK
28: coshf_u35 : OK
27: expm1f : OK
28: tanhf_u35 : OK
27: log10f : OK
28: asinhf : OK
28: acoshf : OK
27: log2f : OK
28: atanhf : OK
28: exp2f : OK
27: log2f_u35 : OK
27: log1pf : OK
28: exp10f : OK
27: lgammaf_u1 : OK
28: exp2f_u35 : OK
28: exp10f_u35 : OK
27: tgammaf_u1 : OK
27: erff_u1 : OK
28: expm1f : OK
28: log10f : OK
27: erfcf_u15 : OK
27: 
27: 
27: *** All tests passed
27: 
27: 
27: *** Now testing /<>/obj-x86_64-linux-gnu/bin/iutdsp128
27/28 Test #27: iutdsp128 .   Passed   41.44 sec
28: log2f : OK
28: log2f_u35 : OK
28: log1pf : OK
28: lgammaf_u1 : OK
28: tgammaf_u1 : OK
28: erff_u1 : OK
28: erfcf_u15 : OK
28: 
28: 
28: *** All tests passed
28: 
28: 
28: *** Now testing /<>/obj-x86_64-linux-gnu/bin/iutdsp256
28/28 Test #28: iutdsp256 .   Passed   42.83 sec

93% tests passed, 2 tests failed out of 28

Total Test time (real) = 159.66 sec

The following tests FAILED:
 20 - iutpurecfma_scalar (Failed)
 21 - iutypurecfma_scalar (Failed)
Errors while running CTest
make[1]: *** [Makefile:74: test] Error 8
make[1]: Leaving directory '/<>/obj-x86_64-linux-gnu'
dh_auto_test: error: cd obj-x86_64-linux-gnu && make -j8 test ARGS\+=--verbose 
ARGS\+=-j8 returned exit code 2
make: *** [debian/rules:5: binary] Error 25
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2
--- End Message ---
--- Begin Message ---
Source: sleef
Source-Version: 3.5.1-2
Done: Mo Zhou 

We believe that the bug you reported is fixed in the latest version of
sleef, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1013...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Mo Zhou  (supplier of updated sleef 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: Fri, 30 Sep 2022 15:18:34 -0400
Source: sleef
Architecture: source
Version: 3.5.1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Bug#840266: marked as done (no CHANGES file)

[Debian Bug Tracking System]

Your message dated Fri, 30 Sep 2022 20:36:06 +0200
with message-id <87tu4ok8vd@hands.com>
and subject line text in question no longer present in manual
has caused the Debian Bug report #840266,
regarding no CHANGES file
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.)


-- 
840266: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=840266
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: perltidy
Version: 20140328-1
Severity: wishlist
File: /usr/share/man/man1/perltidy.1p.gz

We read on the man page

   Many others have supplied key ideas, suggestions, and bug reports; see
   the CHANGES file.

There is
/usr/share/doc/perltidy/changelog.Debian.gz
/usr/share/doc/perltidy/changelog.gz
but no CHANGES file.


   LICENSE
   This package is free software; you can redistribute it and/or modify it
   under the terms of the "GNU General Public License".

   Please refer to the file "COPYING" for details.

Same for COPYING.
--- End Message ---
--- Begin Message ---
The reference to CHANGES has gone, as has the section about key ideas,
as can be seen here:

$ man perltidy | grep '\b\(CHANGES\|key\|ideas\)\b' 
   "undo" key.
   push @{ $self->{$module}{$key} },
   push @{ $self->{$module}{$key} }, {

Since the other part about the ommision of the COPYING file is just a
matter of policy, I'm closing this bug.--- End Message ---

Bug#564260: marked as done (perltidy (-pbp) desalign hashes in given-when construct)

[Debian Bug Tracking System]

Your message dated Fri, 30 Sep 2022 20:18:00 +0200
with message-id <87zgegk9pj@hands.com>
and subject line fixed since 20220613-1 (or probably before that)
has caused the Debian Bug report #564260,
regarding perltidy (-pbp) desalign hashes in given-when construct
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.)


-- 
564260: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=564260
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: perltidy
Version: 20090616-1
Severity: minor

Hi Don

I have a small sample.pl showing the problem, running perltidy on it,
causes the hash to 'de-align':

---(sample.pl)
#!/usr/bin/perl

use 5.010;
use feature "switch";

my $self;

open( FH, '<', '/tmp/foo.txt' ) or die "Cannot open file: $!\n";
while ( my $line =  ) {
given ($line) {
when (/^#/) {
$self = {
what => 'comment',
help => 'help',
};
}
when (/^foo/) {
$self = {
what => 'foo',
help => 'bar',
};
}
}
}
--

Now running 'perltidy -pbp' on sample.pl, causes following output:
---(output)---
#!/usr/bin/perl

use 5.010;
use feature "switch";

my $self;

open( FH, '<', '/tmp/foo.txt' ) or die "Cannot open file: $!\n";
while ( my $line =  ) {
given ($line) {
when (/^#/) {
$self = {
what => 'comment',
help => 'help',
};
}
when (/^foo/) {
$self = {
what => 'foo',
help => 'bar',
};
}
}
}
--

The diff now shows the problem (I evne had an example where a
semicolon was added, but I need to find first a smaller example to
reproduce that.
---(diff)-
--- sample.pl   2010-01-08 20:26:50.0 +0100 
   
+++ sample.perltidyfied 2010-01-08 20:27:22.0 +0100
@@ -10,14 +10,14 @@
 given ($line) {
 when (/^#/) {
 $self = {
-what => 'comment',
-help => 'help',
+what => 'comment',
+help => 'help',
 };
 }
 when (/^foo/) {
 $self = {
-what => 'foo',
-help => 'bar',
+what => 'foo',
+help => 'bar',
 };
 }
 }
--

Many thanks in case for looking into it,
Bests
Salvatore

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

Kernel: Linux 2.6.26-2-amd64 (SMP w/8 CPU cores)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/dash

Versions of packages perltidy depends on:
ii  perl  5.10.1-8   Larry Wall's Practical Extraction 

perltidy recommends no packages.

perltidy suggests no packages.

-- no debconf information
#!/usr/bin/perl

use 5.010;
use feature "switch";

my $self;

open( FH, '<', '/tmp/foo.txt' ) or die "Cannot open file: $!\n";
while ( my $line =  ) {
given ($line) {
when (/^#/) {
$self = {
what => 'comment',
help => 'help',
};
}
when (/^foo/) {
$self = {
what => 'foo',
help => 'bar',
};
}
}
}
--- End Message ---
--- Begin Message ---
fixed - 20220613-1
done

In recent versions, this seems to work fine:

$ cat tidytest.pl
#!/usr/bin/perl

use 5.010;
use feature "switch";

my $self;

open( FH, '<', '/tmp/foo.txt' ) or die "Cannot open file: $!\n";
while ( my $line =  ) {
given ($line) {
when (/^#/) {
$self = {
what => 'comment',
help => 'help',
};
}
when (/^foo/) {
$self = {
what => 'foo',
help => 'bar',
};
}
}
}
$ perltidy -st tidytest.pl
#!/usr/bin/perl

use 5.010;
use feature "switch";

my $self;

open( FH, '<', '/tmp/foo.txt' ) or die "Cannot open file: $!\n";
while ( my $line =  ) {
given ($line) {
 

Bug#475930: marked as done (attempted to not indent an non-long line)

[Debian Bug Tracking System]

Your message dated Fri, 30 Sep 2022 20:08:19 +0200
with message-id <8735c8loq4@hands.com>
and subject line fixed in 20220613-1 (if not before)
has caused the Debian Bug report #475930,
regarding attempted to not indent an non-long line
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.)


-- 
475930: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=475930
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
X-Debbugs-Cc: perlt...@users.sourceforge.net
Package: perltidy
Version: 20071205-2
Severity: minor

The long line below ends up not being indented.
Shorten it by even one character and it gets indented.

while (<>) {
s/a/b/;
tr (ㄆㄇㄈㄉㄊㄋㄌㄍㄎㄏㄐㄑㄒㄖㄗㄘㄙㄚㄛㄜㄝㄧㄨㄩ)
(i);
tr{p}{q};
}

OK, I notice the same happens with long lines of ASCII too, but the
above wide characters take only two columns of window space each, not
even reaching column 60.

Maybe perltidy is counting them as three characters each via their
UTF-8 encoding.

Anyway, if a line is long it will wrap anyway usually, and perltidy
shouldn't mess up the indentation in any case, good intentions or not.


--- End Message ---
--- Begin Message ---
fixed - 20220613-1
done

This now works, as seen here:

$ cat tidytest.pl
while (<>) {
s/a/b/;
tr (ㄆㄇㄈㄉㄊㄋㄌㄍㄎㄏㄐㄑㄒㄖㄗㄘㄙㄚㄛㄜㄝㄧㄨㄩ)
(i);
tr{p}{q};
}
$ perltidy -st tidytest.pl
while (<>) {
s/a/b/;
tr (ㄆㄇㄈㄉㄊㄋㄌㄍㄎㄏㄐㄑㄒㄖㄗㄘㄙㄚㄛㄜㄝㄧㄨㄩ)
(i);
tr{p}{q};
}
--- End Message ---

Bug#916681: marked as done (Perl::Tidy: tries to access file "SCALAR(0x...)" in cwd)

[Debian Bug Tracking System]

Your message dated Fri, 30 Sep 2022 19:57:16 +0200
with message-id <875yh4lp8j@hands.com>
and subject line no longer reproducible
has caused the Debian Bug report #916681,
regarding Perl::Tidy: tries to access file "SCALAR(0x...)" in cwd
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.)


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

Package: perltidy
Version: 20180220-1
Control: affects -1 libperl-critic-perl

The attached test program print its own tidied source.
It seems to work correctly:

  $ perl selftidy
  #!/usr/bin/perl
  use Perl::Tidy qw(perltidy);
  my $dst;
  perltidy( source => $0, destination => \$dst );
  print($dst);

But in strace output you can see a spurious filesystem access:

  $ strace -o '| grep -w SCALAR >&2' perl selftidy > /dev/null
  stat64("SCALAR(0x56bcb8a8)", 0x56bac2b0) = -1 ENOENT (No such file or 
directory)

I tracked it down to this code in Perl/Tidy.pm, lines 1278-1291:

   # set output file permissions
   if ( $output_file && -f $output_file && !-l $output_file ) {
   if ($input_file_permissions) {

   # give output script same permissions as input script, but
   # make it user-writable or else we can't run perltidy again.
   # Thus we retain whatever executable flags were set.
   if ( $rOpts->{'format'} eq 'tidy' ) {
   chmod( $input_file_permissions | oct(600), $output_file );
   }

   # else use default permissions for html and any other format
   }
   }

Apparently this is run even when $output_file is a reference, not a 
pathname.



-- System Information:
Architecture: i386

Versions of packages perltidy depends on:
ii  perl  5.28.1-3

--
Jakub Wilk
#!/usr/bin/perl
use Perl::Tidy qw(perltidy);
my $dst;
perltidy(source => $0, destination => \$dst);
print($dst);
--- End Message ---
--- Begin Message ---
fixed - 20220613-1
done

Looking at the code (in 20220613-1), it's changed considerably, and the
bug is no longer reproducible.--- End Message ---

Processed: src:rust-resource-proof: fails to migrate to testing for too long: autopkgtest regression

[Debian Bug Tracking System]

Processing control commands:

> close -1 1.0.39-2
Bug #1021029 [src:rust-resource-proof] src:rust-resource-proof: fails to 
migrate to testing for too long: autopkgtest regression
Marked as fixed in versions rust-resource-proof/1.0.39-2.
Bug #1021029 [src:rust-resource-proof] src:rust-resource-proof: fails to 
migrate to testing for too long: autopkgtest regression
Marked Bug as done

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

Bug#528898: marked as done (please add info-dir-section to your info files)

[Debian Bug Tracking System]

Your message dated Fri, 30 Sep 2022 18:57:42 +0200
with message-id 
and subject line Re: please add info-dir-section to your info files
has caused the Debian Bug report #528898,
regarding please add info-dir-section to your info files
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.)


-- 
528898: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=528898
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: vflib3-doc
Version: 3.6.14.dfsg-1
Severity: normal
Usertags: texinfo-transition

Dear maintainer,

we are currently replacing the dpkg install-info with GNU install-info
and at the same time reworking the installation method for info files
with triggers (see http://wiki.debian.org/Transitions/DpkgToGnuInstallInfo
for details).

As a package maintainer your only job is to drop info files below
/usr/share/info and the package install-info will care for the rest
by recreating the dir file from all installed info files.

There is one problem in the info files of your packages
vflib3-doc
because the files:
usr/share/info/VFlib-36.info.gz
do not ship info dir sections. Thus, calling install-info (the GNU version)
on these files issue a warning:
install-info: warning: no info dir entry in `/usr/share/info/...'
and the file is not included in the dir file.

The source of this problem is the following missing entry in the
texinfo source:
@dircategory Package short info
@direntry
* menu item 1: (infofile).  Description.
* menu item 2: (infofile2). Description.
@end direntry
In the experimental package we still let the above warnings go through,
but with an upload to unstable they will be probably supressed.

Can you please add an info dir entry to the texinfo files of your package
to fix these warnings.

If you have any questions please see the texinfo manual available in info 
format in texinfo-doc-nonfree, chapter 21 Creating and Installing Info Files,
and do not hesitate to contact us at
debian-tex-ma...@lists.debian.org

Thanks a lot and all the best

Norbert Preining
texinfo maintainer



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

Version: 3.7.2+dfsg-0.1

The info file is no longer shipped. It was a non-source file.
It might be generated from the texinfo file again.--- End Message ---

Bug#1020282: marked as done (openmotor: git build fail when $HOME is not writable)

[Debian Bug Tracking System]

Your message dated Fri, 30 Sep 2022 10:25:27 -0600 (MDT)
with message-id <20220930162527.189db24e0...@rover.gag.com>
and subject line fixed in latest upload
has caused the Debian Bug report #1020282,
regarding openmotor: git build fail when $HOME is not writable
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.)


-- 
1020282: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020282
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: openmotor
Version: 0.5.0-1
Severity: wishlist

The current git repository of openmotor fail to build when HOME points
to a nonexisting directory, like it do with pbuilder.  To reproduce it,
for example build using 'HOME=/nonexisting debuild'.  The build failure
look like this:

  [...]
  make[1]: Entering directory '/home/pere/src/debian/openmotor'
  python3 setup.py build_ui
  Matplotlib created a temporary config/cache directory at
/tmp/matplotlib-adek6nzq because the default path
(/nonexisting/.config/matplotlib) is not a writable directory; it is
highly recommended to set the MPLCONFIGDIR environment variable to a
writable directory, in particular to speed up the import of Matplotlib
and to better support multiprocessing.
  Traceback (most recent call last):
File "/home/pere/src/debian/openmotor/setup.py", line 2, in 
  from uilib.fileIO import appVersionStr
File "/home/pere/src/debian/openmotor/uilib/fileIO.py", line 10, in 
  from .logger import logger
File "/home/pere/src/debian/openmotor/uilib/logger.py", line 40, in 
  logger = Logger()
File "/home/pere/src/debian/openmotor/uilib/logger.py", line 13, in __init__
  self._openLogFile()
File "/home/pere/src/debian/openmotor/uilib/logger.py", line 21, in 
_openLogFile
  os.makedirs(path)
File "/usr/lib/python3.10/os.py", line 215, in makedirs
  makedirs(head, exist_ok=exist_ok)
File "/usr/lib/python3.10/os.py", line 215, in makedirs
  makedirs(head, exist_ok=exist_ok)
File "/usr/lib/python3.10/os.py", line 215, in makedirs
  makedirs(head, exist_ok=exist_ok)
File "/usr/lib/python3.10/os.py", line 225, in makedirs
  mkdir(name, mode)
  PermissionError: [Errno 13] Permission denied: '/nonexisting'
  [...]

The code in question try to create the directories leading up to
/nonexisting/.cache/openMotor/log to be able to log to file.  A
workaround is to make sure HOME point to a writable location during
build, for example like this:

diff --git a/debian/rules b/debian/rules
index 43f3bc2..5a151ef 100755
--- a/debian/rules
+++ b/debian/rules
@@ -9,7 +9,7 @@ export PYBUILD_DISABLE=test
dh $@ --with python3 --buildsystem=pybuild
 
 override_dh_auto_build:
-   python3 setup.py build_ui
+   export TMPHOME="$(tempfile -d)"; HOME="$TMPHOME" python3 setup.py 
build_ui; rm -rf $TMPHOME
touch uilib/views/__init__.py
dh_auto_build
 
A better approach might be to convince openmotor/uilib/logger.py to not
create anything in $HOME during build.

-- 
Happy hacking
Petter Reinholdtsen
--- End Message ---
--- Begin Message ---
I neglected to mark this bug closed in the latest upload, which fixed the issue.

Bdale--- End Message ---

Bug#1021009: marked as done (Unindent the .pc files for pkgconf compatibility)

[Debian Bug Tracking System]

Your message dated Fri, 30 Sep 2022 16:37:01 +
with message-id 
and subject line Bug#1021009: fixed in glslang 11.11.0-2
has caused the Debian Bug report #1021009,
regarding Unindent the .pc files for pkgconf compatibility
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.)


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

Package: pkgconf
Version: 1.6.0-1

glslang-dev provides spirv.pc, unfortunately it seems
pkgconf is unable to use it. This leads to builds of
filament breaking if pkgconf happens to be installed.


root@cuboxi4x4:/filament# pkg-config --libs spirv
Package spirv was not found in the pkg-config search path.
Perhaps you should add the directory containing `spirv.pc'
to the PKG_CONFIG_PATH environment variable
Package 'spirv', required by 'virtual:world', not found
root@cuboxi4x4:/filament# 
PKG_CONFIG_PATH=/usr/lib/arm-linux-gnueabihf/pkgconfig/ pkg-config --libs spirv
Package spirv was not found in the pkg-config search path.
Perhaps you should add the directory containing `spirv.pc'
to the PKG_CONFIG_PATH environment variable
Package 'spirv', required by 'virtual:world', not found
root@cuboxi4x4:/filament# which pkg-config
/usr/bin/pkg-config
root@cuboxi4x4:/filament# ls -l /usr/bin/pkg-config
lrwxrwxrwx 1 root root 7 Aug 23  2021 /usr/bin/pkg-config -> pkgconf
<--snip removal of pkgconf and installation of pkg-config-->
root@cuboxi4x4:/filament# pkg-config --libs spirv
-lSPIRV -lSPIRV-Tools-opt -lSPIRV-Tools -lSPIRV-Tools-link -lglslang 
-lMachineIndependent -lOSDependent -lHLSL -lOGLCompiler -lGenericCodeGen 
-lSPVRemapper -lpthread
--- End Message ---
--- Begin Message ---
Source: glslang
Source-Version: 11.11.0-2
Done: Timo Aaltonen 

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

Debian distribution maintenance software
pp.
Timo Aaltonen  (supplier of updated glslang 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: Fri, 30 Sep 2022 19:08:12 +0300
Source: glslang
Built-For-Profiles: noudeb
Architecture: source
Version: 11.11.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian X Strike Force 
Changed-By: Timo Aaltonen 
Closes: 1021009
Changes:
 glslang (11.11.0-2) unstable; urgency=medium
 .
   * patches: Unindent pc files. (Closes: #1021009)
Checksums-Sha1:
 5ef3bba5e3a10b3c9e812f335fc6c954c1fc40b3 2118 glslang_11.11.0-2.dsc
 31fc9c6fe85f3247f35816f2c8949f58f522db46 14242 glslang_11.11.0-2.diff.gz
 15cf6af150f458fc427eb8d1711b8454d8a2ea21 8748 
glslang_11.11.0-2_source.buildinfo
Checksums-Sha256:
 bab85a957198ad061bd97a17502941af8185422f60f86b96ec9e3772c80f9f20 2118 
glslang_11.11.0-2.dsc
 fc8c290434395659f40a914f626f0ce44654ded2dc5973683da3c498d0478527 14242 
glslang_11.11.0-2.diff.gz
 6a6ed2665637c35de5d4d232c8af61165fd1d88acd7f4e1ebd403939a9b1222b 8748 
glslang_11.11.0-2_source.buildinfo
Files:
 b39d78159a943df391c9b08970021568 2118 libdevel optional glslang_11.11.0-2.dsc
 d5b3205a683a6fb60d38da776f60ec03 14242 libdevel optional 
glslang_11.11.0-2.diff.gz
 d19d34fbd08e5f97d9f52fd109a3c71b 8748 libdevel optional 
glslang_11.11.0-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEdS3ifE3rFwGbS2Yjy3AxZaiJhNwFAmM3FHsACgkQy3AxZaiJ
hNxvrQ/9G2JMG3bO1+t7sZwLAk8iXvoM+UCjs6eIeyQO0Aa7Jug0HwqLZ1sp4L1+
uM2v24VJpaHCALip/IUxGdyPA1lZSyXQ8NTKzKtawz6/fISP0EO/yfw52ttTMNxe
DbAlAMN+qs1Vt2Ku18IYc/YYhD5iQJxx651SDXAV1WANFn9Nsqp1A3l3rRAjD8Zp
ePROnn6dXdagGxBvj1E5ad0K2dGUcXyJZsGCVeLH4LL9yu5Mp9SUWsw3gmZks72q
SLVRc/RupMeF7ND7TfnmAsx41g1IhKBJfqB+p1OOdlRVW3zIOwxlzNzTGBXJa17F
U6qqc4xiK8s4iFdiVTirE5zKgmRI6utFE2uFIvy2PmEaGJSbyBdfdpDsgrMx2tAL
4vhjmuHt/lRxXu34qnhLBUwoBngnelelEPdXnlBU9uWL6qS2+jK5gEMQbpEGHAC6
QxRfpexQdoBYJTFV9XhVQHr0Ep8hN0mo7JL55MMb6IdT7a/8mqlvNaKAOAWdT90F
3rY1djO0PRcyko9nFPHktNSmCUtreiL5V1AsOn0jGPPsEdRHmnWAUjLKEdpULU3y
0GMzfBkijwg4fGF+rKnf3TX6RVOqAvNMuabtD49PKzgkmYLlCdDRNDLp/bxyFyLo
ixzbumWuFznmZsE0RFDrbJ+loZOEqVYDIWUY46Pi5lq5Mh5o4/Q=
=Iom7
-END PGP SIGNATURE End Message ---

Bug#916679: marked as done (broken Perl::Tidy man page)

[Debian Bug Tracking System]

Your message dated Fri, 30 Sep 2022 18:12:08 +0200
with message-id <878rm0lu3r@hands.com>
and subject line perltidy: fixed since 20200110-1
has caused the Debian Bug report #916679,
regarding broken Perl::Tidy man page
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.)


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

Package: perltidy
Version: 20180220-1

The Perl::Tidy man page looks completely broken:

  $ man Perl::Tidy
  Perl::Tidy(3pm)   User Contributed Perl Documentation  Perl::Tidy(3pm)
  
  # compare input/output indentation except for continuation lines

  # (because they have an unknown amount of initial blank space)
  # and lines which are quotes (because they may have been outdented)
  # Note: this test is placed here because we know the continuation flag
  # at this point, which allows us to avoid non-meaningful checks.
  my $structural_indentation_level = $rLL->[$Kfirst]->[_LEVEL_];
  compare_indentation_levels( $guessed_indentation_level,
  $structural_indentation_level )
unless ( $rLL->[$Kfirst]->[_CI_LEVEL_] > 0
  || $guessed_indentation_level == 0
  && $rLL->[$Kfirst]->[_TYPE_] eq 'Q' );
  
  POD ERRORS

 Hey! The above document had some coding errors, which are
 explained below:
  
 Around line 8631:

 =pod directives shouldn’t be over one line long!  Ignoring
 all 3 lines of content
  
  perl v5.26.2  2018-08-11   Perl::Tidy(3pm)




-- System Information:
Architecture: i386

--
Jakub Wilk
--- End Message ---
--- Begin Message ---
fixed 916679 20200110-1
fixed 922406 20200110-1
merge 916679 922406
done

Having checked this on the original report verson, 20200110-1 and
20220613-1, it's been fixed since 20200110-1 (which it the version in
the current stable release).
-- 
|)|  Philip Hands  [+44 (0)20 8530 9560]  HANDS.COM Ltd.
|-|  http://www.hands.com/http://ftp.uk.debian.org/
|(|  Hugo-Klemm-Strasse 34,   21075 Hamburg,GERMANY--- End Message ---

Bug#922406: marked as done (man Perl::Tidy disaster)

[Debian Bug Tracking System]

Your message dated Fri, 30 Sep 2022 17:58:30 +0200
with message-id <87bkqwluqh@hands.com>
and subject line perltidy: fixed since 20200110-1
has caused the Debian Bug report #922406,
regarding man Perl::Tidy disaster
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.)


-- 
922406: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=922406
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: perltidy
Version: 20180220-1
File: /usr/share/man/man3/Perl::Tidy.3pm.gz

Why is this so short?
$ man Perl::Tidy|wc -l
21

And it says:

POD ERRORS
   Hey! The above document had some coding errors, which are explained 
below:

   Around line 8631:
   =pod directives shouldn't be over one line long!  Ignoring all 3 
lines of content


$ man -w Perl::Tidy|xargs zcat|wc -l
93
--- End Message ---
--- Begin Message ---
Having checked this on the original report verson, 20200110-1 and
20220613-1, it's been fixed since 20200110-1 (which it the version in
the current stable release).--- End Message ---

Bug#949490: marked as done (raptor2: FTBFS with libxml2 not shipping xml2-config)

[Debian Bug Tracking System]

Your message dated Fri, 30 Sep 2022 16:08:47 +
with message-id 
and subject line Bug#949490: fixed in raptor2 2.0.15-3
has caused the Debian Bug report #949490,
regarding raptor2: FTBFS with libxml2 not shipping xml2-config
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.)


-- 
949490: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=949490
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: raptor2
Version: 2.0.14-1
Severity: important
Tags: ftbfs
User: libx...@packages.debian.org
Usertags: xml2-config


Dear maintainer,

your package is using `xml2-config` to detect and use libxml2.  I'm
removing that script, so please update your build system to use
pkg-config instead.

The libxml2 package in experimental already doesn't ship the xml2-config
script.

Attached is the full build log, hopefully relevant excerpt follows:


/usr/bin/xslt-config: 1: /usr/bin/xml2-config: not found
/usr/bin/xslt-config: 1: /usr/bin/xml2-config: not found
checking for xsltSaveResultToString... yes
checking for system libxslt library... yes - version 1.1.32
checking for xsltInit... yes
checking libxslt/xslt.h usability... no
checking libxslt/xslt.h presence... no
checking for libxslt/xslt.h... no
configure: WARNING: libxslt library found but not headers - disabling
checking for yajl installation... /usr
checking for yajl_parse in -lyajl... yes
checking for yajl_tree_parse in -lyajl... yes
checking yajl/yajl_parse.h usability... yes
checking yajl/yajl_parse.h presence... yes
checking for yajl/yajl_parse.h... yes
checking YAJL API version... 2
checking GRDDL parser requirements... no - libxml2 and libxslt are both not 
available
checking JSON parser requirements... yes
checking RDF parsers required... all
checking RDF serializers required... all
checking XML names version... 1.0
checking for curl/curl.h... (cached) yes
checking for curl_easy_init... (cached) yes
checking for libcurl library... yes - version 7.67.0 via curl-config
checking WWW libraries available...  libcurl 7.67.0
checking WWW library to use... libcurl 7.67.0 via curl-config
checking NFC library to use... none
checking libinn.h usability... no
checking libinn.h presence... no
checking for libinn.h... no
checking date parsing source... libcurl curl_getdate
configure: error: libxml2 is not available - please get it from 
http://xmlsoft.org/
make: *** [/usr/share/cdbs/1/class/autotools.mk:46: debian/stamp-autotools] 
Error 1
dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2


-- 
regards,
Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
More about me:  https://mapreri.org : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-
I: Using pkgname logfile
I: Current time: Tue Jan 21 05:09:20 UTC 2020
I: pbuilder-time-stamp: 1579583360
I: Obtaining the cached apt archive contents
I: Copying source file
I: copying [pkgs/raptor2_2.0.14-1.dsc]
I: copying [pkgs/raptor2_2.0.14.orig.tar.gz]
I: copying [pkgs/raptor2_2.0.14-1.debian.tar.xz]
I: Extracting source
gpgv: unknown type of key resource 'trustedkeys.kbx'
gpgv: keyblock resource '/home/mattia/.gnupg/trustedkeys.kbx': General error
gpgv: Signature made Mon May  5 18:38:09 2014 UTC
gpgv:using DSA key 43EC92504F71955A
gpgv: Can't check signature: No public key
dpkg-source: warning: failed to verify signature on ./raptor2_2.0.14-1.dsc
dpkg-source: info: extracting raptor2 in raptor2-2.0.14
dpkg-source: info: unpacking raptor2_2.0.14.orig.tar.gz
dpkg-source: info: unpacking raptor2_2.0.14-1.debian.tar.xz
I: using fakeroot in build.
I: Installing the build-deps
I: -> Attempting to satisfy build-dependencies
Note, using file '/build/raptor2_2.0.14-1.dsc' to get the build dependencies
Reading package lists...
Building dependency tree...
Reading state information...
The following NEW packages will be installed:
  autoconf automake autopoint autotools-dev bsdmainutils cdbs debhelper
  dh-autoreconf dh-strip-nondeterminism diffstat docbook docbook-to-man
  docbook-xml docbook-xsl dwz file gettext gettext-base groff-base
  gtk-doc-tools intltool-debian libarchive-zip-perl libbrotli1 libbsd0
  libcroco3 libcurl3-gnutls libcurl4-gnutls-dev libdebhelper-perl libelf1
  libfile-stripnondeterminism-perl libglib2.0-0 libgssapi-krb5-2 libk5crypto3
  libkeyutils1 libkrb5-3 libkrb5support0 libldap-2.4-2 

Bug#1016922: marked as done (pkgconf doesn’t handle indented .pc files)

[Debian Bug Tracking System]

Your message dated Fri, 30 Sep 2022 16:08:14 +
with message-id 
and subject line Bug#1016922: fixed in pkgconf 1.8.0-6
has caused the Debian Bug report #1016922,
regarding pkgconf doesn’t handle indented .pc files
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.)


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

Package: pkgconf
Version: 1.6.0-1

glslang-dev provides spirv.pc, unfortunately it seems
pkgconf is unable to use it. This leads to builds of
filament breaking if pkgconf happens to be installed.


root@cuboxi4x4:/filament# pkg-config --libs spirv
Package spirv was not found in the pkg-config search path.
Perhaps you should add the directory containing `spirv.pc'
to the PKG_CONFIG_PATH environment variable
Package 'spirv', required by 'virtual:world', not found
root@cuboxi4x4:/filament# 
PKG_CONFIG_PATH=/usr/lib/arm-linux-gnueabihf/pkgconfig/ pkg-config --libs spirv
Package spirv was not found in the pkg-config search path.
Perhaps you should add the directory containing `spirv.pc'
to the PKG_CONFIG_PATH environment variable
Package 'spirv', required by 'virtual:world', not found
root@cuboxi4x4:/filament# which pkg-config
/usr/bin/pkg-config
root@cuboxi4x4:/filament# ls -l /usr/bin/pkg-config
lrwxrwxrwx 1 root root 7 Aug 23  2021 /usr/bin/pkg-config -> pkgconf
<--snip removal of pkgconf and installation of pkg-config-->
root@cuboxi4x4:/filament# pkg-config --libs spirv
-lSPIRV -lSPIRV-Tools-opt -lSPIRV-Tools -lSPIRV-Tools-link -lglslang 
-lMachineIndependent -lOSDependent -lHLSL -lOGLCompiler -lGenericCodeGen 
-lSPVRemapper -lpthread
--- End Message ---
--- Begin Message ---
Source: pkgconf
Source-Version: 1.8.0-6
Done: Andrej Shadura 

We believe that the bug you reported is fixed in the latest version of
pkgconf, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1016...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Andrej Shadura  (supplier of updated pkgconf 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: Fri, 30 Sep 2022 17:34:39 +0200
Source: pkgconf
Architecture: source
Version: 1.8.0-6
Distribution: unstable
Urgency: medium
Maintainer: Andrej Shadura 
Changed-By: Andrej Shadura 
Closes: 1016922
Changes:
 pkgconf (1.8.0-6) unstable; urgency=medium
 .
   * Ignore whitespace indentation in .pc files (Closes: #1016922).
Checksums-Sha1:
 066d0e5eaa652596c44bb3838e8408021b2fe60b 1513 pkgconf_1.8.0-6.dsc
 6ae94a231af3fb9719b56e128ffe2f45d2ebe75f 9188 pkgconf_1.8.0-6.debian.tar.xz
Checksums-Sha256:
 679d371478bae1f41d8839d325b0230bab94809432f47e983ba851e7861f04f4 1513 
pkgconf_1.8.0-6.dsc
 9c8498a5db1218907b0442d14c732d65af530b62ee68bacc36c292cd5df25797 9188 
pkgconf_1.8.0-6.debian.tar.xz
Files:
 c663863e3acff07a02919ce7476580c9 1513 devel optional pkgconf_1.8.0-6.dsc
 79256b088ebc650bab7334b2822fa89a 9188 devel optional 
pkgconf_1.8.0-6.debian.tar.xz

-BEGIN PGP SIGNATURE-

iHUEARYIAB0WIQSD3NF/RLIsyDZW7aHoRGtKyMdyYQUCYzcMsQAKCRDoRGtKyMdy
YayHAQCZQsEfZIL6ya6AB9B1vYljglNCiPeNrcW0/HSPgSPlnAD/Qkrfc7KPHp/O
lL4YnGX+2FqJ66WfBV2wwSPTwKWqKwI=
=1XwT
-END PGP SIGNATURE End Message ---

Bug#1021014: marked as done (snakeyaml: CVE-2022-38752)

[Debian Bug Tracking System]

Your message dated Fri, 30 Sep 2022 15:38:07 +
with message-id 
and subject line Bug#1021014: fixed in snakeyaml 1.33-1
has caused the Debian Bug report #1021014,
regarding snakeyaml: CVE-2022-38752
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.)


-- 
1021014: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1021014
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: snakeyaml
X-Debbugs-CC: t...@security.debian.org
Severity: important
Tags: security

Hi,

The following vulnerability was published for snakeyaml.

CVE-2022-38752[0]:
| Using snakeYAML to parse untrusted YAML files may be vulnerable to
| Denial of Service attacks (DOS). If the parser is running on user
| supplied input, an attacker may supply content that causes the parser
| to crash by stack-overflow.

Fixed in 1.32:
https://bitbucket.org/snakeyaml/snakeyaml/issues/531/stackoverflow-oss-fuzz-47081
https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=47081 (not public)

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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2022-38752
https://www.cve.org/CVERecord?id=CVE-2022-38752

Please adjust the affected versions in the BTS as needed.
--- End Message ---
--- Begin Message ---
Source: snakeyaml
Source-Version: 1.33-1
Done: tony mancill 

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

Debian distribution maintenance software
pp.
tony mancill  (supplier of updated snakeyaml 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: Fri, 30 Sep 2022 07:52:55 -0700
Source: snakeyaml
Architecture: source
Version: 1.33-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Java Maintainers 

Changed-By: tony mancill 
Closes: 1021014
Changes:
 snakeyaml (1.33-1) unstable; urgency=medium
 .
   * Team upload.
   * New upstream version 1.33 (Closes: #1021014)
 - CVE-2022-38752 was deemed a false-positive by upstream and marked as
   resolved via a unit-test in 1.32
   (https://bitbucket.org/snakeyaml/snakeyaml/issues/531/)
   * Add debian/README.source to document manual tarball handling
Checksums-Sha1:
 229a0896b6415f5fb0aaf30e658c6b9eacd3374d 2445 snakeyaml_1.33-1.dsc
 b2968dd878868d643157cda19ab8729a2a7f82dd 291972 snakeyaml_1.33.orig.tar.xz
 ec24fe74ff515533c6207d4ceeea5626b13a4817 10152 snakeyaml_1.33-1.debian.tar.xz
 0fe161ebe31926aa06a4587085c5e74c794a864a 14149 snakeyaml_1.33-1_amd64.buildinfo
Checksums-Sha256:
 afcf08aebd3d1f17223344b07028c77e41d74daddca7204c7d5bc1a2d80f2f21 2445 
snakeyaml_1.33-1.dsc
 ae0817543e96991fed3460b510f1683fbb491f0863e3b76f39f809c175d36609 291972 
snakeyaml_1.33.orig.tar.xz
 145b8c5d71e81274db4f8832c7e14780e72efe6f9b48854880b32525d4e654b6 10152 
snakeyaml_1.33-1.debian.tar.xz
 6e159a03030513cf22263f444b8cdc9e2496d0d9445246ab565058be5b0ad070 14149 
snakeyaml_1.33-1_amd64.buildinfo
Files:
 dbf3d7b99137316d8542ad0e7e55948f 2445 java optional snakeyaml_1.33-1.dsc
 15b9a3a88a1db9790f86f2463dfba2c1 291972 java optional 
snakeyaml_1.33.orig.tar.xz
 a7f038854dff543d2105fc9c9bd40cbb 10152 java optional 
snakeyaml_1.33-1.debian.tar.xz
 4cbbf473c478f60397b15cdb4fb2b67a 14149 java optional 
snakeyaml_1.33-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJIBAEBCgAyFiEE5Qr9Va3SequXFjqLIdIFiZdLPpYFAmM3BdgUHHRtYW5jaWxs
QGRlYmlhbi5vcmcACgkQIdIFiZdLPpZ/VQ//Yn3VPmk9o5fuqhpDgJJ8QvH6Wnev
LvrK1uZNIW5Du+BKFhB7lKLGL/nhwuPVeMcJWtMkMoQYD6GTRi4vliN1wEtfVS9E
G6N8el/MZebof8TB+tezT1AkaG8lozS0aesvO1C4RJhMbNnhlhg3eSVwWswTzRMG
cfFwtyINNncX6gx57yM4g+SX9wZ5H9izbHB8laSo4gRj6DcJT/3xkE6o7tCvUY0I
cYMjyd4+A/4+af6u2XToHSbymm5p17DQT4iDf2IfWjainGwgnmsPwQGt+RA22KAp
FxBc2A9tqaji5mKoITtc/JF65XrsAtqNx5t+hMKEsaDw7yz7EVAuRAQD+2+zzIM+
3ZBoIb81XxWeZMTETaxSpoR9JUUA/9j9Vsn9cF4lzZP1yx32WYYj53oBf/Ht3IJc
YVU3x7bqPK/YV93S2Y7bFiTdMHZ3fFmFXXx6Yt/2i0KXyBFslFD2s37LXZ2teGGV
BnP3RRyA96/zmObrWlWkL7Tl2yn9mxW6H59+Wv72rf6eVGSbjxwREf3bVINTlJYi

Bug#1020951: marked as done (RFS: raptor2/2.0.15-3 [QA] -- Raptor 2 RDF syntax library)

[Debian Bug Tracking System]

Your message dated Fri, 30 Sep 2022 17:36:17 +0200
with message-id 
and subject line Re: RFS: raptor2/2.0.15-3 [QA] -- Raptor 2 RDF syntax library
has caused the Debian Bug report #1020951,
regarding RFS: raptor2/2.0.15-3 [QA] -- Raptor 2 RDF syntax library
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.)


-- 
1020951: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020951
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: sponsorship-requests
Severity: normal

Dear mentors,

I am looking for a sponsor for my package "raptor2":

 * Package name : raptor2
   Version  : 2.0.15-3
   Upstream contact : Dave Beckett 
 * URL  : https://librdf.org/raptor/
 * License  : GPL-3+, LGPL-2.1+ or GPL-2+ or Apache-2.0,
LGPL-2.1+, public-domain
 * Vcs  : [fill in URL of packaging vcs]
   Section  : devel

The source builds the following binary packages:

  libraptor2-dev - Raptor 2 RDF syntax library development libraries and headers
  libraptor2-0 - Raptor 2 RDF syntax library
  raptor2-utils - Raptor 2 RDF parser and serializer utilities
  libraptor2-doc - Documentation for the Raptor 2 RDF syntax library

raptor2 does not have a repository on Salsa yet. As this is a QA Team
upload, can someone please create an empty repository in the Debian
namespace and grant me (hmc) privileges, so I can build it out?

To access further information about this package, please visit the
following URL:

  https://mentors.debian.net/package/raptor2/

Alternatively, you can download the package with 'dget' using this command:

  dget -x 
https://mentors.debian.net/debian/pool/main/r/raptor2/raptor2_2.0.15-3.dsc

Changes since the last upload:

 raptor2 (2.0.15-3) unstable; urgency=medium
 .
   * QA upload.
   * debian/changelog: Fix some typos.
   * debian/control:
 + libraptor2-dev: Drop Depends on pkg-config.
 + raptor2-utils: Drop Conflicts/Replaces (no longer needed).
 + libraptor2-doc:
   - Mark package Multi-Arch: foreign.
   - Remove documentation path from package description.
   * debian/patches:
 + Fix FTBFS when libxml2 is detected via pkg-config (Closes: #949490).
 + Fix a typo in an existing patch name.
   * debian/rules:
 + Don't install upstream's README file in all binary packages.
   The README file is now only installed in libraptor2-doc.
 + Drop dh_installchangelogs override.
 + Drop dh_strip override; dbgsym-migration is complete.
   * Drop "debian/tmp" from installation paths.
   * libraptor2-0: Add symbols file.
   * libraptor2-doc: Replace .install file with .docs.
   * lintian-overrides: Add overrides for very-long-line-length-in-source-file
 and source-is-missing messages.
   * Add debian/upstream/metadata file.

Regards,
-- 
  Hugh McMaster
--- End Message ---
--- Begin Message ---

Thanks for the QA work!--- End Message ---

Bug#1020630: marked as done (diffoscope: cbfstool is finally available in Debian)

[Debian Bug Tracking System]

Your message dated Fri, 30 Sep 2022 15:34:45 +
with message-id 
and subject line Bug#1020630: fixed in diffoscope 223
has caused the Debian Bug report #1020630,
regarding diffoscope: cbfstool is finally available in Debian
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.)


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

Dear diffoscope maintainers,

since this Thursday src:coreboot is finally (*) in unstable and thus cbfstool
is finally there too (via binary:coreboot-utils), see
https://tracker.debian.org/news/1364252/accepted-coreboot-415dfsg-2-source-into-unstable/

I believe this needs some minor changes to diffoscope which already can
make use of cbfstool if installed, just it needs to learn to recommend
coreboot-utils.

Thanks for your work on diffoscope!

(*) just 16 years after it's ITP bug :)


-- 
cheers,
Holger

 ⢀⣴⠾⠻⢶⣦⠀
 ⣾⠁⢠⠒⠀⣿⡁  holger@(debian|reproducible-builds|layer-acht).org
 ⢿⡄⠘⠷⠚⠋⠀  OpenPGP: B8BF54137B09D35CF026FE9D 091AB856069AAA1C
 ⠈⠳⣄

In Europe there are people prosecuted by courts because they saved other people
from drowning in the  Mediterranean Sea.  That is almost as absurd  as if there
were people being prosecuted because they save humans from drowning in the sea.


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: diffoscope
Source-Version: 223
Done: Chris Lamb 

We believe that the bug you reported is fixed in the latest version of
diffoscope, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1020...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Chris Lamb  (supplier of updated diffoscope 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: Fri, 30 Sep 2022 08:25:31 -0700
Source: diffoscope
Built-For-Profiles: nocheck
Architecture: source
Version: 223
Distribution: unstable
Urgency: medium
Maintainer: Reproducible builds folks 

Changed-By: Chris Lamb 
Closes: 1020630
Changes:
 diffoscope (223) unstable; urgency=medium
 .
   [ Chris Lamb ]
   * The cbfstools utility is now provided in Debian via the coreboot-utils
 Debian package, so we can enable that functionality within Debian.
 (Closes: #1020630)
 .
   [ Mattia Rizzolo ]
   * Also include coreboot-utils in Build-Depends and Test-Depends so it is
 available for the tests.
 .
   [ Jelle van der Waa ]
   * Add support for file 5.43.
Checksums-Sha1:
 b4840dd4975a6cf98d1f5cde4b2351493ff892bc 5002 diffoscope_223.dsc
 8896271d0ae91c2bec49a8cd5eb8440f090cf188 2440820 diffoscope_223.tar.xz
 ad1a28dab82bc5d0ffbf425ac28a98696c7ab18a 7307 diffoscope_223_amd64.buildinfo
Checksums-Sha256:
 08c650f1b9d953987ec09c7af8fea2ce90f1e03ba270b198a5c5a4589c50596f 5002 
diffoscope_223.dsc
 fbf081fc99219ae908d1f5caf43076f0bd139a64ce89a654858c84a311723b28 2440820 
diffoscope_223.tar.xz
 5a5a9b0529377839432c7bf2f675ec74914d1d1a2232d7985675f4950ba3b4b1 7307 
diffoscope_223_amd64.buildinfo
Files:
 ed71959627a2d5f08d8ceb2f0dbbd157 5002 devel optional diffoscope_223.dsc
 934dbd6eb47a90ea5125c4360e076d0d 2440820 devel optional diffoscope_223.tar.xz
 7d5f5fdd82bd4a61c5d1d93b1d93d1b9 7307 devel optional 
diffoscope_223_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEwv5L0nHBObhsUz5GHpU+J9QxHlgFAmM3CpUACgkQHpU+J9Qx
Hlh+DRAAptsO302W6RJy498ExCiT58bPIDcSnYX14EaZjR3kIhIlWa8pEWbyvMWx
JAn0f/TgrdJLoaEYCcoKbOZ3Jm50qY6vtgPAwCIGIf9nQUVV6j3yQQrgzJU8b8QN
gIlnb8qyiJz+jupfC3yH0xzcmznNaBGect+AzWjmMQxk8Sgpb1KHsykrdHl0Omis
XdkX5jPY2h3PmN4OpscpVy38dai5ZneORQwaFNr53fq1/iPYmuFGcv1prEfgvES3
7n4TAN9Bj3E3G73Fh1p1qWifKvaSDgRmafYZqm2qooOFUEKT8kawMFR6rxXnLV7T
gDqVeh3onXWEK5rGpRWLgf/wjA6hCXOZ2/vYyGDi4XpIsxDT6B3n6cJtWjUTqMp6
BVR3Xr/7h0VQfVt76hUdNP5QHxQaeDAKiAgurh1uVmZiaf6xRHA66Rt8QaUa7I6B
pM/DVeXyGK0ddFjaZigQUpU+QNZaoMtZM1VUu2GVDJqJP7X8pPgqYx/ltDrsD9dB
hwjurmOewwFQ9qe3GrOArGZGrhCkF5QdjBxwhrO2qIwIzw0p4pugSvEHJZ0fxh5V
fz3mQ2oND5ifnaoLzssRvR9woZus0M0mi1e/wnOFztZ/dAoNXkFbvJxuJxiMCROV
AkgLfAogRbc/gnqS2SSFW0zBmlsVEEzUuQAy6K2DjEE9+hk1H84=
=ft/E
-END PGP SIGNATURE End Message 

Processed: notfound 1020301 in 1:10.3.36-0+deb10u, found 1020301 in 1:10.3.36-0+deb10u1, closing 1020301

[Debian Bug Tracking System]

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

> # typo in version
> notfound 1020301 1:10.3.36-0+deb10u
Bug #1020301 [mariadb-server-10.3] mariadb-server-10.3: postinst called with 
unknown argument 'triggered'
There is no source info for the package 'mariadb-server-10.3' at version 
'1:10.3.36-0+deb10u' with architecture ''
Unable to make a source version for version '1:10.3.36-0+deb10u'
No longer marked as found in versions 1:10.3.36-0+deb10u.
> found 1020301 1:10.3.36-0+deb10u1
Bug #1020301 [mariadb-server-10.3] mariadb-server-10.3: postinst called with 
unknown argument 'triggered'
There is no source info for the package 'mariadb-server-10.3' at version 
'1:10.3.36-0+deb10u1' with architecture ''
Unable to make a source version for version '1:10.3.36-0+deb10u1'
Marked as found in versions 1:10.3.36-0+deb10u1.
> close 1020301 1:10.3.36-0+deb10u2
Bug #1020301 [mariadb-server-10.3] mariadb-server-10.3: postinst called with 
unknown argument 'triggered'
There is no source info for the package 'mariadb-server-10.3' at version 
'1:10.3.36-0+deb10u2' with architecture ''
Unable to make a source version for version '1:10.3.36-0+deb10u2'
Marked as fixed in versions 1:10.3.36-0+deb10u2.
Bug #1020301 [mariadb-server-10.3] mariadb-server-10.3: postinst called with 
unknown argument 'triggered'
Marked Bug as done
> thanks
Stopping processing here.

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

Bug#1018076: marked as done (mini-transition: gjs built against mozjs102)

[Debian Bug Tracking System]

Your message dated Fri, 30 Sep 2022 16:22:11 +0100
with message-id 
and subject line Re: Bug#1018076: mini-transition: gjs built against mozjs102
has caused the Debian Bug report #1018076,
regarding mini-transition: gjs built against mozjs102
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.)


-- 
1018076: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1018076
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: rele...@debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: transition
X-Debbugs-Cc: debian-...@lists.debian.org, debian-gtk-gn...@lists.debian.org

The plan is for Debian 12 to release with GNOME 43, which is currently in
beta upstream. Beta versions of individual GNOME 43 packages are gradually
making their way into either unstable if they are not disruptive, or
experimental if they are. One of the new packages we need is an update
to gjs, GNOME's JavaScript environment, which depends on mozjs102
(Spidermonkey), the latest stable-branch of Mozilla's JavaScript engine.

mozjs102 makes more use of atomic operations, which are available on
all architectures except for armel (because armel is ARMv5, and useful
atomics are ARMv6 or ARMv7 instructions). This has led to a few different
failure modes when building mozjs102 on armel (#1017979, #1017961).
Even if we can solve them eventually, I think delaying GNOME 43 for the
benefit of machines that are not powerful enough to run GNOME would be
doing a disservice to our users.

So I think we need to be looking at the possibility of doing
architecture-specific removals of gjs and dependent packages from armel.
Based on prior experience of similar architecture-specific removals from
s390x when mozjs was compiling-but-broken on that architecture, I think
this would involve:

- removing gjs
- removing gnome-shell (and its extensions)
- removing gdm3
- either hacking gnome-panel to be able to compile without gdm3, or
  removing it
- either hacking meta-gnome3 to install a non-GNOME display manager and
  the GNOME Flashback desktop environment (basically a GNOME 2 fork)
  instead of real GNOME, or leaving it unmodified but accepting that
  gnome-core and therefore task-gnome-desktop are uninstallable on armel
- disabling a subset of unit tests in src:ostree (which want gjs)
- removing leaf apps written in JavaScript, such as polari

Obviously that's quite a bit of churn, mostly in packages that, in
practice, have never been useful to run on the 2009-2010 plug computers
that seem to be the main use-case for armel.

Is armel a realistic candidate for being a Debian 12 release
architecture? It's already lacking other important packages like Firefox,
and if it ceased to be treated as a release architecture very soon,
then we wouldn't have to do all this work to coax GNOME into testing
despite armel.

Or, failing that, is it still the release team's position that all task
packages are required to be installable on all architectures, and that it
is preferable to have a task install the wrong things rather than have
it be uninstallable? If we could have task-gnome-desktop and gnome-core
just be uninstallable on armel, and have the testing machinery accept
and ignore that, then that would seem more honest than having to modify
them like we did for s390x[1].

As with my previous work on mozjs + s390x, it is worth noting that I
am not an ARM porter or an ARM desktop user, my only armel machine is
no longer supported as of Debian 11 and was never able to run GNOME
in any case, and I have no special knowledge of mozjs. However, the
release-architecture constraints demand that someone sorts this out
before we can have a new GNOME release in testing, and I am someone, so
I'm doing my best. Anyone with useful knowledge of these architectures
and packages is very welcome to help!

Thanks,
smcv

[1] https://lists.debian.org/debian-release/2018/12/msg00287.html
--- End Message ---
--- Begin Message ---
On Sun, 25 Sep 2022 at 14:07:58 +0100, Simon McVittie wrote:
> If these versions reach testing without incident, which should happen
> next week if all goes well, then no release team action will be required,
> and the only remaining cleanup before closing this bug will be to remove
> mozjs91 from unstable (which I'm intentionally not doing until after
> mozjs102 migrates).

mozjs102 and the gjs that uses it have migrated to testing, so this
mini-transition can be considered finished, and I've requested removal of
mozjs91 in #1016878.

smcv--- End Message ---

Bug#1020971: marked as done (usrmerge: Fails to install on Windows Subsystem for Linux (WSL) 1.0)

[Debian Bug Tracking System]

Your message dated Fri, 30 Sep 2022 16:15:42 +0100
with message-id <1016eb1a2c286573e6cb97c3fe77fb3571e43d30.ca...@debian.org>
and subject line Re: Bug#1020971: usrmerge: Fails to install on Windows 
Subsystem for Linux (WSL) 1.0
has caused the Debian Bug report #1020971,
regarding usrmerge: Fails to install on Windows Subsystem for Linux (WSL) 1.0
to be marked as done.

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

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


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

Package: usrmerge
Version: 31
Severity: normal
X-Debbugs-Cc: none

Dear Maintainer,

When installing usrmerge on Debian Bookworm under the Windows Subsystem
for Linux (WSL) 1.0, installation fails at the setup stage.

**This bug effectively breaks the entire install of Debian Bookworm on
WSL 1.0**, because usrmerge is now a required dependency of the
essential/system-critical package init-system-helpers, as of version
1.65~exp1 through the current version (1.65.2) of that package.

I suspect the cause of this issue is related to the fact that WSL 1.0
uses a Microsoft-provided kernel for all Linux distributions that run on
WSL 1.0. WSL 2.0 allows the use of the actual distribution's kernel,
because it uses the Hyper-V hypervisor on the host Windows operating
system. However, WSL 2.0 is not an option for me (and I assume many
others), who use other virtualization products on Windows, or use a
cloud-hosted virtual Windows desktop, such as AWS Workspaces or C
itrix.

--
Setting up usrmerge (31) ...
mv: cannot move '/lib/x86_64-linux-gnu/security' to
'/usr/lib/x86_64-linux-gnu/security': Permission denied

FATAL ERROR:
mv --no-clobber /lib/x86_64-linux-gnu/security
/usr/lib/x86_64-linux-gnu/security: rc=1

You can try correcting the errors reported and running again
/usr/lib/usrmerge/convert-usrmerge until it will complete without errors.
Do not install or update other Debian packages until the program
has been run successfully.

E: usrmerge failed.
dpkg: error processing package usrmerge (--configure):
 installed usrmerge package post-installation script subprocess
returned error exit status 1
Errors were encountered while processing:
 usrmerge
E: Sub-process /usr/bin/dpkg returned an error code (1)
--

Attempting to run sudo mv --no-clobber /lib/x86_64-linux-gnu/security
/usr/lib/x86_64-linux-gnu/security manually results in the same
permission denied error.

-- System Information:
Debian Release: bookw
orm/sid
  APT prefers testing
  APT policy: (500, 'testing')
merged-usr: no
Architecture: amd64 (x86_64)

Kernel: Linux 4.4.0-22000-Microsoft
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE
not set
Shell: /bin/sh linked to /usr/bin/dash
Init: unable to detect

Versions of packages usrmerge depends on:
ii  libfile-find-rule-perl  0.34-2
ii  perl5.34.0-5

usrmerge recommends no packages.

usrmerge suggests no packages.

-- no debconf information


signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Control: forwarded -1 https://github.com/microsoft/WSL/issues/8927

On Thu, 29 Sep 2022 21:44:29 + Sean Whalen  wrote:
> I just created a bug report in the official Microsoft WSL project on
> GitHub to track the issue there as well, and maybe get some eyeballs
> from Microsoft.
> 
> https://github.com/microsoft/WSL/issues/8927

I've talked with both the internal team and the Debian maintainer of
the WSL image. This is a WSL 1.0 specific issue, and there's not much
we can do in usrmerge about it, as it's related to the underlying
filesystem that we can't touch anyway.

The Debian stable WSL image in the store will be updated shortly to be
merged-usr out of the box, so this won't happen again for new
installations, and on upgrade to bookworm it will be a no-op. Older
installations on WSL 1.0 will have to remove and reinstall, unless a
workaround is found, but for that please use the upstream bug tracker
as here we really can't figure out what the problem is.

Also please note that it would be a good idea to just move to WSL 2.0
for all use cases at this point.

Hence, setting the forwarded address and closing.

-- 
Kind regards,
Luca Boccassi


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

Bug#1020813: marked as done (bible-kjv: reproducible-builds: differing buildid in various binaries)

[Debian Bug Tracking System]

Your message dated Fri, 30 Sep 2022 15:04:05 +
with message-id 
and subject line Bug#1020813: fixed in bible-kjv 4.38
has caused the Debian Bug report #1020813,
regarding bible-kjv: reproducible-builds: differing buildid in various binaries
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.)


-- 
1020813: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020813
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: bible-kjv
Severity: normal
Tags: patch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: buildpath
X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org

The buildid differs in in various binaries when build a different build
path:

  
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/diffoscope-results/bible-kjv.html

The attached patches fix this by patching the upstream Makefile to pass
-ffile-prefix-map and patching debian/rules to pass -ffile-prefix-map to
a CC call.

According to my local tests, with these patches applied bible-kjv should
build reproducibly on tests.reproducible-builds.org!

Thanks for maintaining bible-kjv!

live well,
  vagrant
From d5d57c09389cd4e5205c4f9aaa560dfc2ffbbebd Mon Sep 17 00:00:00 2001
From: Vagrant Cascadian 
Date: Tue, 27 Sep 2022 01:14:43 +
Subject: [PATCH 1/2] Makefile: Add -ffile-prefix-map to CFLAGS to avoid
 embedding build paths.

https://reproducible-builds.org/docs/build-path/
---
 Makefile | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/Makefile b/Makefile
index 3b998b8..6365c54 100644
--- a/Makefile
+++ b/Makefile
@@ -88,7 +88,7 @@ DESTMAN1  = $(DESTMAN)/man1
 
 # I use environment variables for these...
 #CFLAGS	  = -g
-CFLAGS	  = -Wall -Wformat -Werror -Wshadow -W -Wmissing-declarations -Wmissing-prototypes -Wstrict-prototypes -Wcast-align -Wcast-qual -Wbad-function-cast -Wpointer-arith -g2 -ggdb -DDESTLIB=\"$(DESTLIB)\"
+CFLAGS	  = -Wall -Wformat -Werror -Wshadow -W -Wmissing-declarations -Wmissing-prototypes -Wstrict-prototypes -Wcast-align -Wcast-qual -Wbad-function-cast -Wpointer-arith -g2 -ggdb -DDESTLIB=\"$(DESTLIB)\" -ffile-prefix-map=$(CURDIR)=.
 LDFLAGS   = 
 LDADD = -lreadline
 
-- 
2.37.2

From 270b47fdbe2fd7ada4814438d4059fe383398cb7 Mon Sep 17 00:00:00 2001
From: Vagrant Cascadian 
Date: Tue, 27 Sep 2022 01:15:16 +
Subject: [PATCH 2/2] debian/rules: Add -ffile-prefix-map to CC call to avoid
 embedding build paths.

https://reproducible-builds.org/docs/build-path/
---
 debian/rules | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/debian/rules b/debian/rules
index 64fdebb..57e8174 100755
--- a/debian/rules
+++ b/debian/rules
@@ -23,7 +23,7 @@ build:
 	dpkg-architecture -a$(DEB_BUILD_ARCH) -f -c dh_auto_build --no-parallel -- bible-index.c bible.data bible.data.conc 'LD=$$(CC)'
 	rm -f *.o
 	dh_auto_build --no-parallel -- bible 'LD=$$(CC)'
-	cd debian && $(CC) -g -O2 -o randverse randverse.c
+	cd debian && $(CC) -g -O2 -ffile-prefix-map=$(CURDIR)=. -o randverse randverse.c
 	touch build
 
 build-arch: build
-- 
2.37.2



signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: bible-kjv
Source-Version: 4.38
Done: Matthew Vernon 

We believe that the bug you reported is fixed in the latest version of
bible-kjv, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1020...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Matthew Vernon  (supplier of updated bible-kjv 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: Fri, 30 Sep 2022 15:22:50 +0100
Source: bible-kjv
Binary: bible-kjv bible-kjv-text
Architecture: source
Version: 4.38
Distribution: unstable
Urgency: medium
Maintainer: Matthew Vernon 
Changed-By: Matthew Vernon 
Description:
 bible-kjv  - King James Version of the Bible: user interface program.
 bible-kjv-text - King James Version of the Bible - text and concordance
Closes: 1020813
Changes:
 bible-kjv (4.38) unstable; urgency=medium
 .
   * Patches from Vagrant Cascadian to use -ffile-prefix-map to make build
 reproducible (Closes: #1020813)
Checksums-Sha1:
 

Bug#994089: marked as done (ITP: node-rollup-plugin-strip -- Rollup plugin to remove debugger statements and functions)

[Debian Bug Tracking System]

Your message dated Fri, 30 Sep 2022 15:00:13 +
with message-id 
and subject line Bug#994089: fixed in node-rollup-plugin-strip 2.1.0+ds-1
has caused the Debian Bug report #994089,
regarding ITP: node-rollup-plugin-strip -- Rollup plugin to remove debugger 
statements and functions
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.)


-- 
994089: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=994089
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: wnpp
Severity: wishlist
Owner: Vivek K J 
X-Debbugs-Cc: debian-de...@lists.debian.org, vive...@protonmail.com

* Package name: node-rollup-plugin-strip
  Version : 2.1.0
  Upstream Author : 2021, Rich Harris
* URL : 
https://github.com/rollup/plugins/tree/master/packages/strip#readme
* License : Expat
  Programming Lang: Javascript
  Description : Rollup plugin to remove debugger statements and functions
 This is a plugin for rollup module bundler to remove debugger statements
 and functions like assert.equal and console.log from your code. This package 
will be maintained
 by javascript maintainers.
--- End Message ---
--- Begin Message ---
Source: node-rollup-plugin-strip
Source-Version: 2.1.0+ds-1
Done: Yadd 

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

Debian distribution maintenance software
pp.
Yadd  (supplier of updated node-rollup-plugin-strip package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 06 Sep 2022 15:36:21 +0200
Source: node-rollup-plugin-strip
Binary: node-rollup-plugin-strip
Built-For-Profiles: nocheck
Architecture: source all
Version: 2.1.0+ds-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Javascript Maintainers 

Changed-By: Yadd 
Description:
 node-rollup-plugin-strip - Rollup plugin to remove debugger statements and 
functions
Closes: 994089
Changes:
 node-rollup-plugin-strip (2.1.0+ds-1) unstable; urgency=medium
 .
   [ Vivek K J, Yadd ]
   * Initial release (Closes: #994089)
Checksums-Sha1:
 73ac813754f18215ec8aae72a1a4915ac7af5ac2 2364 
node-rollup-plugin-strip_2.1.0+ds-1.dsc
 db0209e9bfb37e042b4e46daa6322d1946979c55 119204 
node-rollup-plugin-strip_2.1.0+ds.orig.tar.xz
 db0dd6cad6e3e6b965b0cb2692ba31ff84e27254 2972 
node-rollup-plugin-strip_2.1.0+ds-1.debian.tar.xz
 417433762e47ac811f2a435ce92e036010b255f0 6096 
node-rollup-plugin-strip_2.1.0+ds-1_all.deb
 633e2fc724c2d6e60fa1e1992b9d437caa99f568 8073 
node-rollup-plugin-strip_2.1.0+ds-1_amd64.buildinfo
Checksums-Sha256:
 7807d3378bcffce181d94fa6f9b8a5d784e61ace430a59fbf161f489135adbf7 2364 
node-rollup-plugin-strip_2.1.0+ds-1.dsc
 8aaf7d4e2692df054742c930543617c121224e2ea2f78532ab3b96737a1929f0 119204 
node-rollup-plugin-strip_2.1.0+ds.orig.tar.xz
 dc1bfa50b7f51f84250f04c100e8f39cdd20f23faeb8e2ef96c005b83576f9ac 2972 
node-rollup-plugin-strip_2.1.0+ds-1.debian.tar.xz
 01fdf2ee48e1292dee45ce3c36dabbd2fc8a165e5da01e5f487f98ee571b05b3 6096 
node-rollup-plugin-strip_2.1.0+ds-1_all.deb
 5b1b5473a31cc48641bee44e49759e0bf49c476489c007f6b5fc8cd3cecb604e 8073 
node-rollup-plugin-strip_2.1.0+ds-1_amd64.buildinfo
Files:
 dbcf23f2fd90e3684b58078a568f94af 2364 javascript optional 
node-rollup-plugin-strip_2.1.0+ds-1.dsc
 38f30c7957fb7db7764044e21410fd8b 119204 javascript optional 
node-rollup-plugin-strip_2.1.0+ds.orig.tar.xz
 1b3fb5b15e1f2e71fb5e9442ea60e3ef 2972 javascript optional 
node-rollup-plugin-strip_2.1.0+ds-1.debian.tar.xz
 4ed3a72354b1abc7cecd8f3b7f47235f 6096 javascript optional 
node-rollup-plugin-strip_2.1.0+ds-1_all.deb
 e70339c89c6d3bc9fbc9be424db8bdb8 8073 javascript optional 
node-rollup-plugin-strip_2.1.0+ds-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEAN/li4tVV3nRAF7J9tdMp8mZ7ukFAmMXTocACgkQ9tdMp8mZ
7unvEg//QL4I+I6oF17cCORcXZD8Y8VB0qeqSNMWcS5DuM3sI8b7FJ9ICQP1Pxky
JlSRt01ESGJp1g6J/JDiE5h5LbWYSPl5jH3mwd9fAsk51Ssj8veuEcG7LBcP0U76
ebYMvnCkAuqC0wG71grNUdBUKCM+N/KZr2+kvQurRiS4VILxVTYKO9wR+L+oKCT7
mZm2mEDNlO7P4Ut2OT0hp1cr5qlxVF4FYug0LgPxG9jmSDCZG/HPbx2DW05qiTm+

Bug#1019546: marked as done (ITP: emacs-pass-mode -- major mode for password-store)

[Debian Bug Tracking System]

Your message dated Fri, 30 Sep 2022 15:00:12 +
with message-id 
and subject line Bug#1019546: fixed in emacs-pass-mode 2.0-1
has caused the Debian Bug report #1019546,
regarding ITP: emacs-pass-mode -- major mode for password-store
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.)


-- 
1019546: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1019546
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: wnpp
Owner: Martin 
Severity: wishlist

* Package name: emacs-pass-mode
  Version : 2.0
  Upstream Author : Nicolas Petton , Damien Cassou 

* URL or Web page : https://github.com/NicolasPetton/pass
* License : GPL-3+
  Description : major mode for password-store

Major mode to work with the password-store ("pass").
View, generate, edit, delete, and rename entries.
--- End Message ---
--- Begin Message ---
Source: emacs-pass-mode
Source-Version: 2.0-1
Done: Martin 

We believe that the bug you reported is fixed in the latest version of
emacs-pass-mode, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1019...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Martin  (supplier of updated emacs-pass-mode package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 11 Sep 2022 21:39:40 +
Source: emacs-pass-mode
Binary: elpa-pass
Architecture: source all
Version: 2.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Emacsen team 
Changed-By: Martin 
Description:
 elpa-pass  - major mode for password-store
Closes: 1019546
Changes:
 emacs-pass-mode (2.0-1) unstable; urgency=medium
 .
   * Initial package (Closes: #1019546)
Checksums-Sha1:
 2fd8c0addae9e3a1063b4f2685c8df982df4e67c 1955 emacs-pass-mode_2.0-1.dsc
 db0abd5f22bb1b144b748e450869defda43ed378 21693 emacs-pass-mode_2.0.orig.tar.gz
 0e625f8043b5e1f41383058cf6d24470d1b290ea 2408 
emacs-pass-mode_2.0-1.debian.tar.xz
 f73033c38f0a3f6dd5219d3a7c8821efbade3c75 9988 elpa-pass_2.0-1_all.deb
 cfc456a1529603dbdf79680b68133b3ae9f4398d 8003 
emacs-pass-mode_2.0-1_amd64.buildinfo
Checksums-Sha256:
 4d9c314a837e6a7d80e6c5481cce3e44982cbe3f4ea03f22d71abb11733c42a0 1955 
emacs-pass-mode_2.0-1.dsc
 65f75e8144341787b5df4499089e01cdd3a9bcd4fe8a6e94a82321583be99db2 21693 
emacs-pass-mode_2.0.orig.tar.gz
 e01de330a329a6df485c774684c547987ac6aedab271fbe2eb358bd19f8475aa 2408 
emacs-pass-mode_2.0-1.debian.tar.xz
 664c8c7103e2f678c34a1038ed3f9be6ea4a3156adb4b898578ec48469024a04 9988 
elpa-pass_2.0-1_all.deb
 cde3b7ab8da9b083da30ea5bea440da9741dee01f37eb10d6506814d86f09659 8003 
emacs-pass-mode_2.0-1_amd64.buildinfo
Files:
 e2369539f42cb4403673f616d5fcac8b 1955 editors optional 
emacs-pass-mode_2.0-1.dsc
 140fae7709b1013b52600121f29c1275 21693 editors optional 
emacs-pass-mode_2.0.orig.tar.gz
 4b5f2bbfcde1d2ef40adefbabba12ba5 2408 editors optional 
emacs-pass-mode_2.0-1.debian.tar.xz
 9d312f2d0854c1e1acb61c70483fcb29 9988 editors optional elpa-pass_2.0-1_all.deb
 6a7e469c019f1ef0394e52d6b12542e7 8003 editors optional 
emacs-pass-mode_2.0-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEftHeo0XZoKEY1KdA4+Chwoa5Y+oFAmMeXe8ACgkQ4+Chwoa5
Y+re1hAAnfN9iMZuOdsFF1g+ZtF148dKVLV7z8gvXGbiYqGF8faEOHRvdW/QtiNx
Fbo+O2V0OAhyba8nJClH013onCtVDPZEHzmDtB6R6NxKmm/4n9+Ip6IyZRtswGKw
+FNfw61JOOxlG67yXV1y7QzzbYclaGuLh7TCbLh0lw/R/oZwilSP2beeqYK93l6Q
Vpnhj1M3j/oelSuJhPO2sdD3BTuud0nRknanpuieyGTFAoJM0e0ReXD/5wQ9w1Xu
XAed2wfx8R+DMuNh1aNCObpQjTGY9Y+A9y5odggqW4chzekI1qRu/+yfi65BqQyn
+3xSpSD23dxRjbL4//GutnpT46ZYNlbkf1y6Xq1I/HVmd2cVtFFMlQubd0G+RVMy
k9smE6wl3zJ7n2tHiBz0aA3QFhKvkKqOVU44Tdm8UeMWqcfSZVPHf/kMtpV0FjZs
6ulDDEAYyV3lr/ZzJygNa5ysPP09NBUnkEsaJRCjNoGQoGyUU6S46H1Bb1R66Yfe
DsVwcFYekiNPYedXPmUfZJW0n708hvdSBs5OuYmFjWgRSXonAE5AE/dNyM+b9+7k
FPe7p448Zwi+YNXWBSZxRHBA+nvi4MPd0rImwGhNA/CBt1GAm3mmLQ2nc/ilrbNp
2Cy7FBfQ3ZfXUz6Rc+C8GtLJJEEdtEOM14i/7xmJdlJ6k/ctnqY=
=FG48
-END PGP SIGNATURE End Message ---

Bug#1019208: marked as done (ITP: viagee -- support for Gmail as the preferred email application in GNOME)

[Debian Bug Tracking System]

Your message dated Fri, 30 Sep 2022 15:00:14 +
with message-id 
and subject line Bug#1019208: fixed in viagee 3.0-1
has caused the Debian Bug report #1019208,
regarding ITP: viagee -- support for Gmail as the preferred email application 
in GNOME
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.)


-- 
1019208: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1019208
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: wnpp
Severity: wishlist
Owner: David Steele 

* Package name: viagee
  Version : 3.0-1
  Upstream Author : David Steele 
* URL : https://github.com/davesteele/viagee/tree/debian
* License : GPL
  Programming Lang: Python
  Description : support for Gmail as the preferred email
application in GNOME

This is a rename of the existing package "gnome-gmail". The name had
to be changed due to branding contention.

A transitional gnome-gmail package is included in the repository [1].

[1]: https://github.com/davesteele/viagee/tree/debian
--- End Message ---
--- Begin Message ---
Source: viagee
Source-Version: 3.0-1
Done: David Steele 

We believe that the bug you reported is fixed in the latest version of
viagee, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1019...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
David Steele  (supplier of updated viagee package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 04 Sep 2022 23:04:51 -0400
Source: viagee
Binary: gnome-gmail viagee
Architecture: source all
Version: 3.0-1
Distribution: unstable
Urgency: medium
Maintainer: David Steele 
Changed-By: David Steele 
Description:
 gnome-gmail - transitional package
 viagee - support for Gmail as the preferred email application in GNOME
Closes: 1019208
Changes:
 viagee (3.0-1) unstable; urgency=medium
 .
   * Name change (Closes: #1019208)
Checksums-Sha1:
 8c6e608ede30b33e848a0f744430b130585e3343 2288 viagee_3.0-1.dsc
 4a107e36fff47e19d17263ebcf2383fe6a92ff97 68559 viagee_3.0.orig.tar.gz
 97b026a95247dd04f92c341320d992bfe3f83d0e 833 viagee_3.0.orig.tar.gz.asc
 f427678ddcf8b0b3fc781a8fee73196b01c4c33a 15556 viagee_3.0-1.debian.tar.xz
 fbd93d8bc654dc159ff6bd477b69e88aa3562b79 7556 gnome-gmail_3.0-1_all.deb
 c503cc9c488ce42ff122de6ae8835144d9fc144d 41408 viagee_3.0-1_all.deb
 dfe7ef28a7046701fa51fcece7ba914461510d41 7635 viagee_3.0-1_amd64.buildinfo
Checksums-Sha256:
 820ae63f8b7480fcf0536a6a20f8d453106b84172f3c9ba1c0dbbf5dc5b18bd7 2288 
viagee_3.0-1.dsc
 59b4d6b3943858089ffe08f20329bf40bf50727f2294e13e38a7321460dcc340 68559 
viagee_3.0.orig.tar.gz
 073a983053983a6b9e8d9e36f4ce13f157be8799698b7f1575763eef7c34e89f 833 
viagee_3.0.orig.tar.gz.asc
 19d3e66dd470dfa87c81cec5ad2097b35de3c1628f2d32da78ef09662e622981 15556 
viagee_3.0-1.debian.tar.xz
 b972298703e40f09c0e241b5b43d8eb45bf9f6e4fc4a22c0bec806bac00269ca 7556 
gnome-gmail_3.0-1_all.deb
 d7c7dd155fb5979a95bdaf19fd5c7d4a6607e44e479d9583a61f45015eef29ab 41408 
viagee_3.0-1_all.deb
 d3f651d87f2cb1f0fd4ab21da5c9a83ccad2ed8333748981b77e610cce62fa8b 7635 
viagee_3.0-1_amd64.buildinfo
Files:
 08e858ae949475038b519fefd676de48 2288 mail optional viagee_3.0-1.dsc
 31b2c749601860802c2521e85709700a 68559 mail optional viagee_3.0.orig.tar.gz
 a50c6587d913876bcd7cb14990ca681f 833 mail optional viagee_3.0.orig.tar.gz.asc
 c4e8c88493f715d48daba27a55e5a1bf 15556 mail optional viagee_3.0-1.debian.tar.xz
 c84fe045f005dd7574a0f3bd686b2e27 7556 oldlibs optional 
gnome-gmail_3.0-1_all.deb
 7122b75ee8ec78817285fd5884342cf7 41408 mail optional viagee_3.0-1_all.deb
 09d3d144eaf0cf9b439871e8595b186d 7635 mail optional 
viagee_3.0-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJGBAEBCgAwFiEEi4SQsUoAbTYxHS3FCVnEo9z4n78FAmMXY+4SHHN0ZWVsZUBk
ZWJpYW4ub3JnAAoJEAlZxKPc+J+/TVcP/jUjCgxopNlX2yM/VfqKl6ocAG5xYesW
hUO8JSre538au+GfLbmYPiWDilxubp3CNASfu6BB2ylUy6IFEEwNqDGiUnPYVjh8
pvgK4jUytfKn/jm7atEyAghC8OTCM+y9a3RxS2hJz+g7ao9QPmyucotb7e5e7uOC
BrCp6uxmH+06/J4yz6WK7ye24EvTML23H4kxYz+0f18cbjjxazYhwTUcGOWIcUxR
R6bmVy9GzW1VR/sN7N9J6RCDoOKJ3saCnc+OR2Yn8SkYGhltzw6RrhZX+zmnnlrj
C9+LE1UsqqB0T4xbJW2fi07GLP9ecjhdFx55J2Xg9j2uR2tkkW6v+5kQ70QmBbkJ

Bug#1019507: marked as done (ITP: libquazip1-qt6 -- Qt/C++ wrapper over minizip - Version 1 (Qt6))

[Debian Bug Tracking System]

Your message dated Fri, 30 Sep 2022 15:00:13 +
with message-id 
and subject line Bug#1019507: fixed in libquazip1-qt6 1.3-1
has caused the Debian Bug report #1019507,
regarding ITP: libquazip1-qt6 -- Qt/C++ wrapper over minizip - Version 1 (Qt6)
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.)


-- 
1019507: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1019507
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: wnpp
X-Debbugs-Cc: debian-de...@lists.debian.org
Owner: Ben Westover 
Severity: wishlist

* Package name: libquazip1-qt6
  Version : 1.3
  Upstream Author : Sergey A. Tachenov 
* URL : https://github.com/stachenov/quazip
* License : zlib, LGPL-2.1 with static linking exception
  Programming Lang: C, C++
  Description : Qt/C++ wrapper over minizip - Version 1 (Qt6)

QuaZip is the C++ wrapper for Gilles Vollant's ZIP/UNZIP package (AKA
Minizip) using Trolltech's Qt library.

While quazip is already packaged in Debian, it's version 0.9.1. The
author of quazip has stated that versions 1.x are meant to be used
alongside 0.x and not as an upgrade/replacement, like how Qt5 is still
packaged alongside Qt6.
This package is for versions 1.x of quazip built for Qt6. I'm packaging
it because it's a dependency of PolyMC. If needed, I can also package a
Qt5 version. I do not plan to package this inside a team, unless one
expresses interest. I will need a sponsor at first as I'm only a DM.

Thanks,
--
Ben Westover


OpenPGP_signature
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: libquazip1-qt6
Source-Version: 1.3-1
Done: Ben Westover 

We believe that the bug you reported is fixed in the latest version of
libquazip1-qt6, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1019...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Ben Westover  (supplier of updated libquazip1-qt6 
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, 10 Sep 2022 17:06:16 -0400
Source: libquazip1-qt6
Binary: libquazip1-qt6-1 libquazip1-qt6-1-dbgsym libquazip1-qt6-dev 
libquazip1-qt6-doc
Architecture: source amd64 all
Version: 1.3-1
Distribution: unstable
Urgency: medium
Maintainer: Ben Westover 
Changed-By: Ben Westover 
Description:
 libquazip1-qt6-1 - Qt/C++ wrapper over minizip - Version 1 (Qt6)
 libquazip1-qt6-dev - Qt/C++ wrapper over minizip - Version 1 (Qt6) - 
development files
 libquazip1-qt6-doc - Qt/C++ wrapper over minizip - Version 1 (Qt6) - 
documentation
Closes: 1019507
Changes:
 libquazip1-qt6 (1.3-1) unstable; urgency=medium
 .
   * Initial Package (Closes: #1019507)
Checksums-Sha1:
 e702a4ed0ceeaad25aa4f398199f1e4660dd2a7b 2119 libquazip1-qt6_1.3-1.dsc
 797087cb724065aa5a43a74b0e3dabcb5d75e4e7 156138 libquazip1-qt6_1.3.orig.tar.gz
 05ebf55c73d2a23fd71966ccb031e125abf75fe8 4092 
libquazip1-qt6_1.3-1.debian.tar.xz
 d189e3b159dc69f01672dc71efd2c77cef6123ba 1409620 
libquazip1-qt6-1-dbgsym_1.3-1_amd64.deb
 fc56cd23f7d55f581b238c673dc9b9bad73fb819 85180 libquazip1-qt6-1_1.3-1_amd64.deb
 6bd5740f96144fd2d633ecca21c26e99c33cfef5 35920 
libquazip1-qt6-dev_1.3-1_amd64.deb
 9ba3e33dfefd0a3fc52372beb6d8545070bcd8b5 216100 
libquazip1-qt6-doc_1.3-1_all.deb
 a04f6f377262a4524f486efacdd767ac05ec4c3f 12253 
libquazip1-qt6_1.3-1_amd64.buildinfo
Checksums-Sha256:
 b98e5bf8dc6b39fc03f6311ff76b16abbb409373b7795c98586d70303a533f97 2119 
libquazip1-qt6_1.3-1.dsc
 c1239559cd6860cab80a0fd81f4204e606f9324f702dab6166b0960676ee1754 156138 
libquazip1-qt6_1.3.orig.tar.gz
 73f50c7d19b8ad62a5dfb8b344b8e7a8fefead5fc942a074606b87e379b0b342 4092 
libquazip1-qt6_1.3-1.debian.tar.xz
 efa50136003380031b092f0a0fb0098f8d6a2a43a4d61ca52a02081a35bd5ea0 1409620 
libquazip1-qt6-1-dbgsym_1.3-1_amd64.deb
 195eee22e109bf2a89faedaf2aea96c73a2be597819fe346eca6c13293d5cb83 85180 
libquazip1-qt6-1_1.3-1_amd64.deb
 e0284fadab42e88eb80a18482fb439a19826825154deb18ce0241fae49954e4c 35920 
libquazip1-qt6-dev_1.3-1_amd64.deb
 640dbdaa70805c035fb0f87503510dd17cfe31d7d4f777a02e466434cf7b0839 216100 
libquazip1-qt6-doc_1.3-1_all.deb
 

Bug#1009142: marked as done (ITP: org-appear -- auto-toggle visibility of org mode elements)

[Debian Bug Tracking System]

Your message dated Fri, 30 Sep 2022 15:00:14 +
with message-id 
and subject line Bug#1009142: fixed in org-appear 0.3.0-1
has caused the Debian Bug report #1009142,
regarding ITP: org-appear -- auto-toggle visibility of org mode elements
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.)


-- 
1009142: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009142
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: wnpp
Owner: Martin 
Severity: wishlist

* Package name: org-appear
  Version : 0.3.0
  Upstream Author : Alice Istleyeva 
* URL or Web page : https://github.com/awth13/org-appear
* License : MIT
  Description : auto-toggle visibility of org mode elements

Org mode provides a way to toggle visibility of hidden elements such as
emphasis markers, links, etc. by customising specific variables, e.g.,
org-hide-emphasis-markers. This package, inspired by org-fragtog,
enables automatic visibility toggling depending on cursor position.
Hidden element parts appear when the cursor enters an element and
disappear when it leaves.

https://raw.githubusercontent.com/awth13/org-appear/master/demo.gif

(Very useful, should be part of org-mode itself.)
--- End Message ---
--- Begin Message ---
Source: org-appear
Source-Version: 0.3.0-1
Done: Martin 

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

Debian distribution maintenance software
pp.
Martin  (supplier of updated org-appear package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 11 Sep 2022 09:14:35 +
Source: org-appear
Binary: elpa-org-appear
Architecture: source all
Version: 0.3.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Emacsen team 
Changed-By: Martin 
Description:
 elpa-org-appear - auto-toggle visibility of org mode elements
Closes: 1009142
Changes:
 org-appear (0.3.0-1) unstable; urgency=medium
 .
   * Initial package (Closes: #1009142)
Checksums-Sha1:
 ebb88c585e596ebcef155065737c1f55aa21a872 1935 org-appear_0.3.0-1.dsc
 02031fa290b283a9e3bd1ea56e0cd4b3f5d8f572 95423 org-appear_0.3.0.orig.tar.gz
 e5a3cf1f203f0d40dc24393115a28c6f55b009b7 1840 org-appear_0.3.0-1.debian.tar.xz
 0d48c0d2cbb445b37ab1ac8877f431f8460b8360 95440 elpa-org-appear_0.3.0-1_all.deb
 c7d65a0e1cd35918d51f9ecaf6608e55dc345ea3 8021 
org-appear_0.3.0-1_amd64.buildinfo
Checksums-Sha256:
 1931b6dccb7757c12e600b9f882467bbbe8fac1876c379b499579e2925ce7da5 1935 
org-appear_0.3.0-1.dsc
 a0d4b9d90bcf52caef0fb761554a9c5cd0fd1f596bad13c711aa935f50554fb6 95423 
org-appear_0.3.0.orig.tar.gz
 3b968a7576467a72ebffb3d7c0fe25292011101e326395fd884db204f1d468a0 1840 
org-appear_0.3.0-1.debian.tar.xz
 4ffc7fe888f8c40e81c9c684a1af455fe86c34060b978a7a4a6aa4b5548a499c 95440 
elpa-org-appear_0.3.0-1_all.deb
 459957d632e20d0ea61b8bd0c8a27976b8a998167ebea774d0d797303b811659 8021 
org-appear_0.3.0-1_amd64.buildinfo
Files:
 5ad6f7c350cdcf25773d690089d8922c 1935 editors optional org-appear_0.3.0-1.dsc
 c35e3e65161e155ada62279613e04271 95423 editors optional 
org-appear_0.3.0.orig.tar.gz
 002ec40fdfd6c7de20d7cdcbbb48accb 1840 editors optional 
org-appear_0.3.0-1.debian.tar.xz
 3810b923b1c49ae395e1a61ffa745a15 95440 editors optional 
elpa-org-appear_0.3.0-1_all.deb
 5608452e542ee2f90f0241c893f0a56c 8021 editors optional 
org-appear_0.3.0-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEftHeo0XZoKEY1KdA4+Chwoa5Y+oFAmMdsZoACgkQ4+Chwoa5
Y+qOnBAAm3sSyWJy2RSRBdfMu2rNCNIq7Uma28NTwUgCQU8+0ICYkUm4wfjKkEXO
lhq6y83BleHsWzknRNpKzWnqpv3zWBCV15/KYo72TJ3za8RBQhrZWeBLwCWdkZtJ
AxJAjaQk2Ktjjypp3HDsHpPTG6fTx8ZbYvamgu6iy2MJ/Q+rhQ3NSjKA2Fhq0wOd
DPv5yapyWnDkhOgCuVeFK4fbBXOztvnd7XMWaWEfsg84N6yjKOISo9fgVeKCpLOO
6IEMc8ARXcCQxdQ8s27QgqTgWOMSHE9Xka3iWspbOySrJinbKZRw+wKLrsOhXDJo
45ZM4jATm0DtxEcjlbAtV+s9/kYpfSQPSuAxswTbG0Te6I9Ie6MJ1QRkdOrBkGps
BfzXtzEe6QfFDy1+u7M3zGuvlXE6J64B0y5SLrLQhWzBA2EfcdevULTM9utMTL+0
1vH1CezZSmGq4zTKxUlrVVRFkn9+gsHMdzcv1DgCjcTjdIQQ+qWVVBW+jBIrlEyw
ycV4DApx2wyf4Ts+AlMxBj0Os9+74RsblvZIr+bqjI2TvyfEgNghEYX+NNBC530N

Bug#1020012: marked as done (python-fluids: FTBFS: ModuleNotFoundError: No module named 'setuptools')

[Debian Bug Tracking System]

Your message dated Fri, 30 Sep 2022 14:43:10 +
with message-id 
and subject line Bug#1020012: fixed in python-fluids 1.0.22-2
has caused the Debian Bug report #1020012,
regarding python-fluids: FTBFS: ModuleNotFoundError: No module named 
'setuptools'
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.)


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

Hi,

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


Relevant part (hopefully):
>  debian/rules clean
> dh clean --with python3,sphinxdoc --buildsystem=pybuild --test-pytest
>dh_auto_clean -O--buildsystem=pybuild -O--test-pytest
> I: pybuild base:240: python3.10 setup.py clean 
> Traceback (most recent call last):
>   File "/<>/setup.py", line 23, in 
> from setuptools import setup
> ModuleNotFoundError: No module named 'setuptools'
> E: pybuild pybuild:379: clean: plugin distutils failed with: exit code=1: 
> python3.10 setup.py clean 
> dh_auto_clean: error: pybuild --clean -i python{version} -p 3.10 returned 
> exit code 13
> make: *** [debian/rules:11: clean] Error 25


The full build log is available from:
http://qa-logs.debian.net/2022/09/17/python-fluids_1.0.22-1_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20220917;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20220917=lu...@debian.org=1=1=1=1#results

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

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

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Source: python-fluids
Source-Version: 1.0.22-2
Done: Nilesh Patra 

We believe that the bug you reported is fixed in the latest version of
python-fluids, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1020...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Nilesh Patra  (supplier of updated python-fluids 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: Fri, 30 Sep 2022 18:38:45 +0530
Source: python-fluids
Architecture: source
Version: 1.0.22-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Nilesh Patra 
Closes: 1020012
Changes:
 python-fluids (1.0.22-2) unstable; urgency=medium
 .
   * Team Upload.
   * B-D on python3-setuptools (Closes: #1020012)
Checksums-Sha1:
 5bd09ff0e382ce8f47a51345f5d9737a281dd041 2506 python-fluids_1.0.22-2.dsc
 c831142fb9d65375b3ccb61c35a7a07b46a90f21 6356 
python-fluids_1.0.22-2.debian.tar.xz
 6e017554cb8e6e6208d232b7307a25305bcca463 12682 
python-fluids_1.0.22-2_amd64.buildinfo
Checksums-Sha256:
 a6254ebb53d89706b2badbf5d82aa18bc35dc4e976893ec77db628cefef91b7b 2506 
python-fluids_1.0.22-2.dsc
 988e1d006d4b67558e4e60023b83956aecd34344719459e1e4da21ce902a099a 6356 
python-fluids_1.0.22-2.debian.tar.xz
 87f94dab87ce81785b1a100fe40e82c9a11a76ada40a59bd921138c3b73068d8 12682 
python-fluids_1.0.22-2_amd64.buildinfo
Files:
 2aba9ed3850d4eaf05b9e917187c11c0 2506 python optional 
python-fluids_1.0.22-2.dsc
 dbaf4c0cac9dbb83fb66320e5e4375be 6356 python optional 
python-fluids_1.0.22-2.debian.tar.xz
 4548447dec018f92246af3e25080d46f 12682 python optional 
python-fluids_1.0.22-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJGBAEBCgAwFiEEPpmlJvXcwMu/HO6mALrnSzQzafEFAmM29+ISHG5pbGVzaEBk
ZWJpYW4ub3JnAAoJEAC650s0M2nxcUcP/2KFWt1wNcCgsYeq33ntqQVhOQGvxi0n
OIizEjuNDLjeq17ihI4gzs3l/K2uD8L4DIbltf3XAznXL89NqosBoDBOnN+zEq8J
hxE5cYd/VDvBdsomNk/t8DAYWUhxscJ7fSqaVHLswOkzqIvuFlPmMHYzikbKVqg6

Bug#529152: marked as done (vflib3: please upgrade your watch file)

[Debian Bug Tracking System]

Your message dated Fri, 30 Sep 2022 14:44:01 +
with message-id 
and subject line Bug#529152: fixed in vflib3 3.7.2+dfsg-0.1
has caused the Debian Bug report #529152,
regarding vflib3: please upgrade your watch file
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.)


-- 
529152: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=529152
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: vflib3
Version: 3.6.14.dfsg-1
Severity: minor
Usertags: versionless-watch

Hi,

Your package ships a version 1 debian/watch file, but this is
deprecated and support for it is going to be removed soon from uscan.

It is strongly recommended that you rewrite it in the version 3
format, as described by uscan's man page, since it brings more
flexibility and support for it will not be dropped any time soon.

If you need help rewriting it don't hesitate to reply to this
message, or tag the bug as 'help'.

Kind regards,
Raphael Geissert 


--- End Message ---
--- Begin Message ---
Source: vflib3
Source-Version: 3.7.2+dfsg-0.1
Done: Bastian Germann 

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

Debian distribution maintenance software
pp.
Bastian Germann  (supplier of updated vflib3 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: Fri, 30 Sep 2022 12:05:36 +0200
Source: vflib3
Architecture: source
Version: 3.7.2+dfsg-0.1
Distribution: unstable
Urgency: medium
Maintainer: OHURA Makoto 
Changed-By: Bastian Germann 
Closes: 449781 515724 529152
Changes:
 vflib3 (3.7.2+dfsg-0.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * New upstream version.
   * d/watch: Fix to scan for new versions (Closes: #449781, #529152).
   * Fix upstream source URL (Closes: #515724).
   * Exclude non-source documentation.
Checksums-Sha1:
 ea5ae4c8e93cc57576028ee853199a30f0fedc78 1827 vflib3_3.7.2+dfsg-0.1.dsc
 b98e4298296bfb813afa56e3d2fd814290ef5c7a 2330768 vflib3_3.7.2+dfsg.orig.tar.xz
 048782d51b4fd7d13216b69e380b01bd68b6b4fa 16824 
vflib3_3.7.2+dfsg-0.1.debian.tar.xz
 211b0756b962666e18beb3176dbea5f087afc9b9 6566 
vflib3_3.7.2+dfsg-0.1_source.buildinfo
Checksums-Sha256:
 6bf3a8ab8052cb6c1603ebf38c2feed1d1c09199a3d2df1545842f2b06def9a8 1827 
vflib3_3.7.2+dfsg-0.1.dsc
 e2ca7d459123dcb908ab3c8416b22a7b8e9b88eb716b1ecac416d6c66a8df9ff 2330768 
vflib3_3.7.2+dfsg.orig.tar.xz
 c94bd65f6e969e2f10d6580bfb0192e8f1effe4cf391f5fc3d7a1621ca53576c 16824 
vflib3_3.7.2+dfsg-0.1.debian.tar.xz
 a78df9d9ea82392c1e594fcea7bd6a10582212bfb71d4d3c56b72d641ff2af67 6566 
vflib3_3.7.2+dfsg-0.1_source.buildinfo
Files:
 ac2560f2c179973412a24c46808d47bc 1827 devel optional vflib3_3.7.2+dfsg-0.1.dsc
 1d4a12a8cea8800d5de7ebf1065a3400 2330768 devel optional 
vflib3_3.7.2+dfsg.orig.tar.xz
 67f5f5e3f5e0d394d6e94eec95705708 16824 devel optional 
vflib3_3.7.2+dfsg-0.1.debian.tar.xz
 335f2994d5acf6de09a270c80ede657f 6566 devel optional 
vflib3_3.7.2+dfsg-0.1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQHEBAEBCgAuFiEEQGIgyLhVKAI3jM5BH1x6i0VWQxQFAmM2+NEQHGJhZ2VAZGVi
aWFuLm9yZwAKCRAfXHqLRVZDFAEUC/0VEEu/8EfJLPN6/RfJ9NPSTXNjIrzLbzIx
AmlpMmhONjVWvCvW3KFIutYv5ADaxXZ+fP3lnbbQFcoHePiHC4BWJZMcc78iCsm7
DH+Bgoep8Uvx+QWGbqzRnbb93HSX+IdBbdoWW7IgGgfxcsNXHGCHYU2gfz54PNAk
1IVI5qsvifgs2JERL08TAMAuJVmJzi/YyFl0ghnwamYq1wDYEkjUxFSbppGAsfP/
fpLz/SWMRiseUtk7b4nQfoKCCmA0aY5Owt7/w0JJfmf3vJGQ0cBVg5i8VkEWRSF9
+M7/KZpMjGMVaJrMxvijyjDuZkODgG372nt9uHbJbSy0rGdjMcaCQWI0mw92mDRb
q90ekMiVuy3J1bmmUmnrRm2Z7O4RgusVTeS+iB8FsRrCs/691WT5bM6ISRFEr3yL
vfSKAJiMT++JNEt1A6+d3afkNa6qwHvMtEU+TQ0Kga9Gu+UxZwNMhPihAW/PLvy4
mMA7myUAZFFyg53BsphajZs3nOX6cLE=
=9EpA
-END PGP SIGNATURE End Message ---

Bug#449781: marked as done (vflib3: debian/watch fails to report upstream's version)

[Debian Bug Tracking System]

Your message dated Fri, 30 Sep 2022 14:44:01 +
with message-id 
and subject line Bug#449781: fixed in vflib3 3.7.2+dfsg-0.1
has caused the Debian Bug report #449781,
regarding vflib3: debian/watch fails to report upstream's version
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.)


-- 
449781: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=449781
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: vflib3
Version: 3.6.13.dfsg-1
Severity: minor
Usertags: dehs-no-upstream

Hello maintainer,

The debian/watch file of your package on the unstable distribution fails to 
report upstream's version.
Uscan's message follows:


uscan warning: /tmp/vflib3_watchi0tUtC is an obsolete version 1 watchfile;
  please upgrade to a higher version
  (see uscan(1) for details).


Please note that this message is auto-generated by extracting the information
 from the Debian External Health Status (a.k.a. DEHS) no_upstream page[1].
At the moment of running the package version found is the one indicated in the 
report.
If you have already fixed this issue please ignore and close this report.

If you belive this message can be improved in any way don't hesitate to contact 
me
 by replying to n-submit...@bugs.debian.org (where N is the number of 
this bug report).

If you wish not to be notified in the future contact me so I add you to the 
ignore list.

[1] http://dehs.alioth.debian.org/no_upstream.html

Kind regards, Raphael Geissert.


--- End Message ---
--- Begin Message ---
Source: vflib3
Source-Version: 3.7.2+dfsg-0.1
Done: Bastian Germann 

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

Debian distribution maintenance software
pp.
Bastian Germann  (supplier of updated vflib3 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: Fri, 30 Sep 2022 12:05:36 +0200
Source: vflib3
Architecture: source
Version: 3.7.2+dfsg-0.1
Distribution: unstable
Urgency: medium
Maintainer: OHURA Makoto 
Changed-By: Bastian Germann 
Closes: 449781 515724 529152
Changes:
 vflib3 (3.7.2+dfsg-0.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * New upstream version.
   * d/watch: Fix to scan for new versions (Closes: #449781, #529152).
   * Fix upstream source URL (Closes: #515724).
   * Exclude non-source documentation.
Checksums-Sha1:
 ea5ae4c8e93cc57576028ee853199a30f0fedc78 1827 vflib3_3.7.2+dfsg-0.1.dsc
 b98e4298296bfb813afa56e3d2fd814290ef5c7a 2330768 vflib3_3.7.2+dfsg.orig.tar.xz
 048782d51b4fd7d13216b69e380b01bd68b6b4fa 16824 
vflib3_3.7.2+dfsg-0.1.debian.tar.xz
 211b0756b962666e18beb3176dbea5f087afc9b9 6566 
vflib3_3.7.2+dfsg-0.1_source.buildinfo
Checksums-Sha256:
 6bf3a8ab8052cb6c1603ebf38c2feed1d1c09199a3d2df1545842f2b06def9a8 1827 
vflib3_3.7.2+dfsg-0.1.dsc
 e2ca7d459123dcb908ab3c8416b22a7b8e9b88eb716b1ecac416d6c66a8df9ff 2330768 
vflib3_3.7.2+dfsg.orig.tar.xz
 c94bd65f6e969e2f10d6580bfb0192e8f1effe4cf391f5fc3d7a1621ca53576c 16824 
vflib3_3.7.2+dfsg-0.1.debian.tar.xz
 a78df9d9ea82392c1e594fcea7bd6a10582212bfb71d4d3c56b72d641ff2af67 6566 
vflib3_3.7.2+dfsg-0.1_source.buildinfo
Files:
 ac2560f2c179973412a24c46808d47bc 1827 devel optional vflib3_3.7.2+dfsg-0.1.dsc
 1d4a12a8cea8800d5de7ebf1065a3400 2330768 devel optional 
vflib3_3.7.2+dfsg.orig.tar.xz
 67f5f5e3f5e0d394d6e94eec95705708 16824 devel optional 
vflib3_3.7.2+dfsg-0.1.debian.tar.xz
 335f2994d5acf6de09a270c80ede657f 6566 devel optional 
vflib3_3.7.2+dfsg-0.1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQHEBAEBCgAuFiEEQGIgyLhVKAI3jM5BH1x6i0VWQxQFAmM2+NEQHGJhZ2VAZGVi
aWFuLm9yZwAKCRAfXHqLRVZDFAEUC/0VEEu/8EfJLPN6/RfJ9NPSTXNjIrzLbzIx
AmlpMmhONjVWvCvW3KFIutYv5ADaxXZ+fP3lnbbQFcoHePiHC4BWJZMcc78iCsm7
DH+Bgoep8Uvx+QWGbqzRnbb93HSX+IdBbdoWW7IgGgfxcsNXHGCHYU2gfz54PNAk
1IVI5qsvifgs2JERL08TAMAuJVmJzi/YyFl0ghnwamYq1wDYEkjUxFSbppGAsfP/
fpLz/SWMRiseUtk7b4nQfoKCCmA0aY5Owt7/w0JJfmf3vJGQ0cBVg5i8VkEWRSF9
+M7/KZpMjGMVaJrMxvijyjDuZkODgG372nt9uHbJbSy0rGdjMcaCQWI0mw92mDRb
q90ekMiVuy3J1bmmUmnrRm2Z7O4RgusVTeS+iB8FsRrCs/691WT5bM6ISRFEr3yL

Bug#515724: marked as done (vflib3: incorrect upstream URL in copyright file)

[Debian Bug Tracking System]

Your message dated Fri, 30 Sep 2022 14:44:01 +
with message-id 
and subject line Bug#515724: fixed in vflib3 3.7.2+dfsg-0.1
has caused the Debian Bug report #515724,
regarding vflib3: incorrect upstream URL in copyright file
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.)


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

The upstream homepage is here:

http://www-masu.ist.osaka-u.ac.jp/~kakugawa/VFlib/

Please replace the broken one in the copyright file and add a Homepage
field to the control file.

-- 
bye,
pabs

http://wiki.debian.org/PaulWise


signature.asc
Description: This is a digitally signed message part
--- End Message ---
--- Begin Message ---
Source: vflib3
Source-Version: 3.7.2+dfsg-0.1
Done: Bastian Germann 

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

Debian distribution maintenance software
pp.
Bastian Germann  (supplier of updated vflib3 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: Fri, 30 Sep 2022 12:05:36 +0200
Source: vflib3
Architecture: source
Version: 3.7.2+dfsg-0.1
Distribution: unstable
Urgency: medium
Maintainer: OHURA Makoto 
Changed-By: Bastian Germann 
Closes: 449781 515724 529152
Changes:
 vflib3 (3.7.2+dfsg-0.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * New upstream version.
   * d/watch: Fix to scan for new versions (Closes: #449781, #529152).
   * Fix upstream source URL (Closes: #515724).
   * Exclude non-source documentation.
Checksums-Sha1:
 ea5ae4c8e93cc57576028ee853199a30f0fedc78 1827 vflib3_3.7.2+dfsg-0.1.dsc
 b98e4298296bfb813afa56e3d2fd814290ef5c7a 2330768 vflib3_3.7.2+dfsg.orig.tar.xz
 048782d51b4fd7d13216b69e380b01bd68b6b4fa 16824 
vflib3_3.7.2+dfsg-0.1.debian.tar.xz
 211b0756b962666e18beb3176dbea5f087afc9b9 6566 
vflib3_3.7.2+dfsg-0.1_source.buildinfo
Checksums-Sha256:
 6bf3a8ab8052cb6c1603ebf38c2feed1d1c09199a3d2df1545842f2b06def9a8 1827 
vflib3_3.7.2+dfsg-0.1.dsc
 e2ca7d459123dcb908ab3c8416b22a7b8e9b88eb716b1ecac416d6c66a8df9ff 2330768 
vflib3_3.7.2+dfsg.orig.tar.xz
 c94bd65f6e969e2f10d6580bfb0192e8f1effe4cf391f5fc3d7a1621ca53576c 16824 
vflib3_3.7.2+dfsg-0.1.debian.tar.xz
 a78df9d9ea82392c1e594fcea7bd6a10582212bfb71d4d3c56b72d641ff2af67 6566 
vflib3_3.7.2+dfsg-0.1_source.buildinfo
Files:
 ac2560f2c179973412a24c46808d47bc 1827 devel optional vflib3_3.7.2+dfsg-0.1.dsc
 1d4a12a8cea8800d5de7ebf1065a3400 2330768 devel optional 
vflib3_3.7.2+dfsg.orig.tar.xz
 67f5f5e3f5e0d394d6e94eec95705708 16824 devel optional 
vflib3_3.7.2+dfsg-0.1.debian.tar.xz
 335f2994d5acf6de09a270c80ede657f 6566 devel optional 
vflib3_3.7.2+dfsg-0.1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQHEBAEBCgAuFiEEQGIgyLhVKAI3jM5BH1x6i0VWQxQFAmM2+NEQHGJhZ2VAZGVi
aWFuLm9yZwAKCRAfXHqLRVZDFAEUC/0VEEu/8EfJLPN6/RfJ9NPSTXNjIrzLbzIx
AmlpMmhONjVWvCvW3KFIutYv5ADaxXZ+fP3lnbbQFcoHePiHC4BWJZMcc78iCsm7
DH+Bgoep8Uvx+QWGbqzRnbb93HSX+IdBbdoWW7IgGgfxcsNXHGCHYU2gfz54PNAk
1IVI5qsvifgs2JERL08TAMAuJVmJzi/YyFl0ghnwamYq1wDYEkjUxFSbppGAsfP/
fpLz/SWMRiseUtk7b4nQfoKCCmA0aY5Owt7/w0JJfmf3vJGQ0cBVg5i8VkEWRSF9
+M7/KZpMjGMVaJrMxvijyjDuZkODgG372nt9uHbJbSy0rGdjMcaCQWI0mw92mDRb
q90ekMiVuy3J1bmmUmnrRm2Z7O4RgusVTeS+iB8FsRrCs/691WT5bM6ISRFEr3yL
vfSKAJiMT++JNEt1A6+d3afkNa6qwHvMtEU+TQ0Kga9Gu+UxZwNMhPihAW/PLvy4
mMA7myUAZFFyg53BsphajZs3nOX6cLE=
=9EpA
-END PGP SIGNATURE End Message ---

Bug#1020903: marked as done (pipewire-pulse: Is the conflict with pulseaudio necessary?)

[Debian Bug Tracking System]

Your message dated Fri, 30 Sep 2022 13:39:45 +
with message-id 
and subject line Bug#1020903: fixed in pipewire 0.3.59-1
has caused the Debian Bug report #1020903,
regarding pipewire-pulse: Is the conflict with pulseaudio necessary?
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.)


-- 
1020903: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020903
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: pipewire-pulse
Version: 0.3.58-1, 0.3.58-2
Severity: normal
X-Debbugs-Cc: neel...@gmail.com

Hello,

I was wondering, could both services (pulseaudio and pipewire-pulse) still be
co-installed at the same time?
That way it would be easy to stop one and start the other in case of any
issues.
Or it would be possible to have one system user (with pro-audio preference)
using pipewire-pulse by default and other users sticking to pulseaudio due to
additional features.

If the idea is about full migration to the new service, perhaps that should be
achieved using additional package? Any thoughts here?

Have a nice day,
Daniel


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

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

Versions of packages pipewire-pulse depends on:
ii  init-system-helpers  1.65.2
ii  pipewire 0.3.57-1

pipewire-pulse recommends no packages.

Versions of packages pipewire-pulse suggests:
ii  libspa-0.2-bluetooth  0.3.57-1
ii  pulseaudio-utils  16.1+dfsg1-2

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: pipewire
Source-Version: 0.3.59-1
Done: Dylan Aïssi 

We believe that the bug you reported is fixed in the latest version of
pipewire, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1020...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Dylan Aïssi  (supplier of updated pipewire 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: Fri, 30 Sep 2022 15:04:20 +0200
Source: pipewire
Architecture: source
Version: 0.3.59-1
Distribution: unstable
Urgency: medium
Maintainer: Utopia Maintenance Team 

Changed-By: Dylan Aïssi 
Closes: 1020330 1020903
Changes:
 pipewire (0.3.59-1) unstable; urgency=medium
 .
   * New upstream release
   * Remove conflict between pipewire-pulse and pulseaudio to allow users
 to switch from one to the other just by disabling/enabling services.
   (Closes: #1020330, #1020903)
Checksums-Sha1:
 7dac94d400c95d6850113904d081cfd545877eea 4026 pipewire_0.3.59-1.dsc
 59b4c3b92dc44f4f726224547350fa36fcfce9ed 1443372 pipewire_0.3.59.orig.tar.bz2
 072a1b0e99d0d02fe502f9ae05f2446f41fa9ef7 22272 pipewire_0.3.59-1.debian.tar.xz
 429bc967044e480dc9c77f6ece04c0c7cc1d1cd0 23095 
pipewire_0.3.59-1_amd64.buildinfo
Checksums-Sha256:
 a34925be686ffa3b46f28aa55810d631df2574bffdff428c2abbfd1a63079933 4026 
pipewire_0.3.59-1.dsc
 32a6db3f42f00eb95a07369160a614420443ca4f4e90ac628db8ca508e08538e 1443372 
pipewire_0.3.59.orig.tar.bz2
 337260292595fc28c5019eb7a2f0e0cf56fcb1a24520afc1127cef26162265c0 22272 
pipewire_0.3.59-1.debian.tar.xz
 08702a14e2979fc5f52cb5301a2319d3f7ef4f4bf84803d0c1d77048cef08e5e 23095 
pipewire_0.3.59-1_amd64.buildinfo
Files:
 935e2b2956c92360606c933b46815553 4026 libs optional pipewire_0.3.59-1.dsc
 d310bf1f3cc5b2b446aecfa97c2cde82 1443372 libs optional 
pipewire_0.3.59.orig.tar.bz2
 623d94aeb839bdde7722684b43cab58d 22272 libs optional 
pipewire_0.3.59-1.debian.tar.xz
 8de142bc2bb0975271513424c22c6cc7 23095 libs optional 
pipewire_0.3.59-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEmjwHvQbeL0FugTpdYS7xYT4FD1QFAmM26t0ACgkQYS7xYT4F
D1Ty3g//cdoMyXI1MLKvGEaW0AplAJA66lnU/oVZ5zkMekbE5Ex7yu1GR85X7KoP
V6P22wQ57KnCsWuvwjfO/+ZzeqMb2kw8yOQwK0+SFQriJnplwu3k+YHwxRbRZ/Zo
EuHyRkyfsnGpCctrM3/kOdxo3Uq450lkW3GCgKuUEghrBis9pHTK39TxtJwGQ68e

Bug#1020330: marked as done (pipewire-pulse: Conflict with pulseaudio is badly resolved by apt full-upgrade)

[Debian Bug Tracking System]

Your message dated Fri, 30 Sep 2022 13:39:45 +
with message-id 
and subject line Bug#1020330: fixed in pipewire 0.3.59-1
has caused the Debian Bug report #1020330,
regarding pipewire-pulse: Conflict with pulseaudio is badly resolved by apt 
full-upgrade
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.)


-- 
1020330: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020330
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: pipewire-pulse
Version: 0.3.58-1
Severity: important
X-Debbugs-Cc: raph...@freexian.com, seb...@debian.org, de...@lists.debian.org

APT will not let me upgrade pipewire-pulse to the latest version because
I have gnome-core installed. It will prefer to deinstall pipewire-pulse:

$ sudo apt full-upgrade
[...]
The following packages were automatically installed and are no longer required:
  libappstream-glib8 libatk1.0-data libmalcontent-ui-0-0 
libnautilus-extension1a libqpdf28
Use 'sudo apt autoremove' to remove them.
The following packages will be REMOVED:
  nautilus-extension-brasero pipewire-pulse
The following packages have been kept back:
  python3-twisted-bin tryton-client
The following packages will be upgraded:
  gstreamer1.0-pipewire libpipewire-0.3-0 libpipewire-0.3-modules 
libspa-0.2-modules nautilus
  nautilus-data pipewire pipewire-bin
8 upgraded, 0 newly installed, 2 to remove and 2 not upgraded.
Need to get 3958 kB of archives.
After this operation, 938 kB disk space will be freed.
Do you want to continue? [Y/n] n

If I try to force install pipewire-pulse, it will propose to remove
gnome-core:
$ LANG=C sudo apt install pipewire-pulse
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following packages were automatically installed and are no longer required:
  hyphen-en-us libappstream-glib8 libatk1.0-data libbox2d2 libfreehand-0.1-1 
libgsf-bin
  libmalcontent-ui-0-0 libmspub-0.1-1 libpagemaker-0.0-0 
libproxy1-plugin-gsettings
  libproxy1-plugin-networkmanager libproxy1-plugin-webkit libqpdf28 
libqxp-0.0-0 libreoffice-draw
  libreoffice-gnome libreoffice-impress libzmf-0.0-0 mythes-en-us
Use 'sudo apt autoremove' to remove them.
The following additional packages will be installed:
  gstreamer1.0-pipewire libldacbt-abr2 libpipewire-0.3-0 
libpipewire-0.3-modules libspa-0.2-bluetooth
  libspa-0.2-modules pipewire pipewire-bin
The following packages will be REMOVED:
  gnome gnome-core pulseaudio pulseaudio-module-bluetooth task-gnome-desktop
The following NEW packages will be installed:
  libldacbt-abr2 libspa-0.2-bluetooth
The following packages will be upgraded:
  gstreamer1.0-pipewire libpipewire-0.3-0 libpipewire-0.3-modules 
libspa-0.2-modules pipewire
  pipewire-bin pipewire-pulse
7 upgraded, 2 newly installed, 5 to remove and 4 not upgraded.
Need to get 1993 kB of archives.
After this operation, 5930 kB disk space will be freed.
Do you want to continue? [Y/n] n

The only way to get the latest version is to manually provide the working
solution by indicating that we also need libspa-0.2-bluetooth (to satisfy
gnome-core's "pulseaudio-module-bluetooth | libspa-0.2-bluetooth" together
with its "pulseaudio | pipewire-pulse").

$ LANG=C sudo apt install pipewire-pulse libspa-0.2-bluetooth
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following packages were automatically installed and are no longer required:
  libappstream-glib8 libatk1.0-data libmalcontent-ui-0-0 libqpdf28
Use 'sudo apt autoremove' to remove them.
The following additional packages will be installed:
  gstreamer1.0-pipewire libldacbt-abr2 libpipewire-0.3-0 
libpipewire-0.3-modules libspa-0.2-modules
  pipewire pipewire-bin
The following packages will be REMOVED:
  pulseaudio pulseaudio-module-bluetooth
The following NEW packages will be installed:
  libldacbt-abr2 libspa-0.2-bluetooth
The following packages will be upgraded:
  gstreamer1.0-pipewire libpipewire-0.3-0 libpipewire-0.3-modules 
libspa-0.2-modules pipewire
  pipewire-bin pipewire-pulse
7 upgraded, 2 newly installed, 2 to remove and 4 not upgraded.
Need to get 1993 kB of archives.
After this operation, 5848 kB disk space will be freed.
Do you want to continue? [Y/n]

That looks like it will be a disaster for users doing a dist upgrade.
But I'm not sure what we can do about it.

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

Bug#1017286: marked as done (fonts-inter: FTBFS: fontmake: Error: In 'src/Inter.glyphs' -> 'master_ufo/Inter.designspace': Generating fonts from Designspace failed: fonts contains incompatible glyphs:

[Debian Bug Tracking System]

Your message dated Fri, 30 Sep 2022 13:37:04 +
with message-id 
and subject line Bug#1017286: fixed in fonts-inter 4.0~beta1+ds-1
has caused the Debian Bug report #1017286,
regarding fonts-inter: FTBFS: fontmake: Error: In 'src/Inter.glyphs' -> 
'master_ufo/Inter.designspace': Generating fonts from Designspace failed: fonts 
contains incompatible glyphs: 'uni0369', 'uni1DE8', 'uni20B7'
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.)


-- 
1017286: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017286
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: fonts-inter
Version: 3.19+ds-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220813 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> fontmake --expand-features-to-instances -i -o otf -g src/Inter.glyphs
> INFO:fontmake.font_project:Building master UFOs and designspace from Glyphs 
> source
> INFO:glyphsLib.classes:Parsing "src/Inter.glyphs" file into 
> WARNING:glyphsLib.builder.components:Glyph 'A': All components of the 
> background layer of 'Black' will be decomposed.
> WARNING:glyphsLib.builder.components:Glyph 'Lambda': All components of the 
> background layer of 'Regular' will be decomposed.
> WARNING:glyphsLib.builder.components:Glyph 'Lambda': All components of the 
> background layer of 'Black' will be decomposed.
> WARNING:glyphsLib.builder.components:Glyph 'AE': All components of the 
> background layer of 'Regular' will be decomposed.
> WARNING:glyphsLib.builder.components:Glyph 'AE': All components of the 
> background layer of 'Black' will be decomposed.
> WARNING:glyphsLib.builder.components:Glyph 'AE': All components of the 
> background layer of 'Italic' will be decomposed.
> WARNING:glyphsLib.builder.components:Glyph 'C': All components of the 
> background layer of 'Regular' will be decomposed.
> WARNING:glyphsLib.builder.components:Glyph 'C': All components of the 
> background layer of 'Black' will be decomposed.
> WARNING:glyphsLib.builder.components:Glyph 'C': All components of the 
> background layer of 'Black Italic' will be decomposed.
> WARNING:glyphsLib.builder.components:Glyph 'Oopen': All components of the 
> background layer of 'Italic' will be decomposed.
> WARNING:glyphsLib.builder.components:Glyph 'Oopen': All components of the 
> background layer of 'Thin Italic' will be decomposed.
> WARNING:glyphsLib.builder.components:Glyph 'F': All components of the 
> background layer of 'Regular' will be decomposed.
> WARNING:glyphsLib.builder.components:Glyph 'F': All components of the 
> background layer of 'Black' will be decomposed.
> WARNING:glyphsLib.builder.components:Glyph 'G': All components of the 
> background layer of 'Regular' will be decomposed.
> WARNING:glyphsLib.builder.components:Glyph 'G': All components of the 
> background layer of 'Black' will be decomposed.
> WARNING:glyphsLib.builder.components:Glyph 'G': All components of the 
> background layer of 'Black Italic' will be decomposed.
> WARNING:glyphsLib.builder.components:Glyph 'G.1': All components of the 
> background layer of 'Regular' will be decomposed.
> WARNING:glyphsLib.builder.components:Glyph 'G.1': All components of the 
> background layer of 'Black' will be decomposed.
> WARNING:glyphsLib.builder.components:Glyph 'uni01F6': All components of the 
> background layer of 'Regular' will be decomposed.
> WARNING:glyphsLib.builder.components:Glyph 'uni01F6': All components of the 
> background layer of 'Black' will be decomposed.
> WARNING:glyphsLib.builder.components:Glyph 'Khook': All components of the 
> background layer of 'Regular' will be decomposed.
> WARNING:glyphsLib.builder.components:Glyph 'Khook': All components of the 
> background layer of 'Black' will be decomposed.
> WARNING:glyphsLib.builder.components:Glyph 'Khook': All components of the 
> background layer of 'Italic' will be decomposed.
> WARNING:glyphsLib.builder.components:Glyph 'Khook': All components of the 
> background layer of 'Black Italic' will be decomposed.
> WARNING:glyphsLib.builder.components:Glyph 'Rx': All components of the 
> background layer of 'Regular' will be decomposed.
> WARNING:glyphsLib.builder.components:Glyph 'Rx': All components of the 
> background layer of 'Italic' will be decomposed.
> WARNING:glyphsLib.builder.components:Glyph 'Thook': All components of the 
> background layer of 'Regular' will be decomposed.
> 

Bug#1020171: marked as done (paredit-everywhere: FTBFS: make: *** [debian/rules:7: binary] Error 25)

[Debian Bug Tracking System]

Your message dated Fri, 30 Sep 2022 12:20:10 +
with message-id 
and subject line Bug#1020171: fixed in paredit-everywhere 0.4git10-1
has caused the Debian Bug report #1020171,
regarding paredit-everywhere: FTBFS: make: *** [debian/rules:7: binary] Error 25
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.)


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

Hi,

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


Relevant part (hopefully):
>  fakeroot debian/rules binary
> dh binary --with elpa
>dh_testroot
>dh_prep
>dh_auto_install --destdir=debian/elpa-paredit-everywhere/
>dh_elpa
> dh_elpa: 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 dh-elpa.el -f dhelpa-batch-install-file 
> debian/elpa-paredit-everywhere//usr/share/emacs/site-lisp/elpa-src 
> ./paredit-everywhere.el /<>/debian/.debhelper/elpa 1611539536 
> returned exit code 255
> Debugger entered--Lisp error: (error "Invalid version syntax: ‘DEV’ (must 
> start with a n...")
>   error("Invalid version syntax: `%s' (must start with a nu..." "DEV")
>   version-to-list("DEV")
>   package-strip-rcs-id("DEV")
>   (or (package-strip-rcs-id (lm-header "package-version")) 
> (package-strip-rcs-id (lm-header "version")) (dhelpa-getenv-version))
>   (let* ((requires-str (lm-header "package-requires")) (pkg-version (or 
> (package-strip-rcs-id (lm-header "package-version")) (package-strip-rcs-id 
> (lm-header "version")) (dhelpa-getenv-version))) (homepage (lm-homepage))) 
> (if pkg-version nil (error "Package lacks a \"Version\" or 
> \"Package-Version\"\nhea...")) (package-desc-from-define file-name 
> pkg-version desc (if requires-str (package--prepare-dependencies 
> (package-read-from-string requires-str))) :kind 'single :url homepage))
>   (let ((file-name (match-string-no-properties 1)) (desc 
> (match-string-no-properties 2)) (start (line-beginning-position))) (if 
> (search-forward (concat ";;; " file-name ".el ends here")) nil (error 
> "Package lacks a terminating comment")) (forward-line) (narrow-to-region 
> start (point)) (require 'lisp-mnt) (let* ((requires-str (lm-header 
> "package-requires")) (pkg-version (or (package-strip-rcs-id (lm-header 
> "package-version")) (package-strip-rcs-id (lm-header "version")) 
> (dhelpa-getenv-version))) (homepage (lm-homepage))) (if pkg-version nil 
> (error "Package lacks a \"Version\" or \"Package-Version\"\nhea...")) 
> (package-desc-from-define file-name pkg-version desc (if requires-str 
> (package--prepare-dependencies (package-read-from-string requires-str))) 
> :kind 'single :url homepage)))
>   dhelpa-buffer-info()
>   (if (derived-mode-p 'tar-mode) (package-tar-file-info) (dhelpa-buffer-info))
>   (let ((pkg-desc (if (derived-mode-p 'tar-mode) (package-tar-file-info) 
> (dhelpa-buffer-info (dhelpa-unpack pkg-desc destdir epoch-time) pkg-desc)
>   dhelpa-install-from-buffer("/<>/paredit-everywher..." 
> "1611539536")
>   (let ((desc (dhelpa-install-from-buffer (expand-file-name dest) 
> epoch-time))) (if desc-dir (progn (dhelpa-write-desc desc desc-dir
>   (progn (insert-file-contents-literally el-file) (if (string-match 
> "\\.tar\\'" el-file) (progn (tar-mode))) (let ((desc 
> (dhelpa-install-from-buffer (expand-file-name dest) epoch-time))) (if 
> desc-dir (progn (dhelpa-write-desc desc desc-dir)
>   (unwind-protect (progn (insert-file-contents-literally el-file) (if 
> (string-match "\\.tar\\'" el-file) (progn (tar-mode))) (let ((desc 
> (dhelpa-install-from-buffer (expand-file-name dest) epoch-time))) (if 
> desc-dir (progn (dhelpa-write-desc desc desc-dir) (and (buffer-name 
> temp-buffer) (kill-buffer temp-buffer)))
>   (save-current-buffer (set-buffer temp-buffer) (unwind-protect (progn 
> (insert-file-contents-literally el-file) (if (string-match "\\.tar\\'" 
> el-file) (progn (tar-mode))) (let ((desc (dhelpa-install-from-buffer 
> (expand-file-name dest) epoch-time))) (if desc-dir (progn (dhelpa-write-desc 
> desc desc-dir) (and (buffer-name temp-buffer) (kill-buffer temp-buffer
>   (let ((temp-buffer (generate-new-buffer " *temp*" t))) (save-current-buffer 
> (set-buffer temp-buffer) 

Bug#1012988: marked as done (librg-blast-parser-perl: ftbfs with GCC-12)

[Debian Bug Tracking System]

Your message dated Fri, 30 Sep 2022 11:04:40 +
with message-id 
and subject line Bug#1012988: fixed in librg-blast-parser-perl 0.03-9
has caused the Debian Bug report #1012988,
regarding librg-blast-parser-perl: ftbfs with GCC-12
to be marked as done.

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

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


-- 
1012988: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1012988
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:librg-blast-parser-perl
Version: 0.03-8
Severity: normal
Tags: sid bookworm
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-12

[This bug is targeted to the upcoming bookworm release]

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

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

The full build log can be found at:
http://qa-logs.debian.net/2022/06/09/gcc12/librg-blast-parser-perl_0.03-8_unstable_gcc12.log
The last lines of the build log are at the end of this report.

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

  apt-get -t=experimental install g++ 

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

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

[...]
  523 | operator<<(basic_ostream& __out, char __c)
  | ^~~~
/usr/include/c++/12/ostream:523:5: note:   template argument 
deduction/substitution failed:
/usr/include/rostlab/aux_functions.h:186:43: note:   cannot convert 
‘v_i.__gnu_cxx::__normal_iterator >::operator*()’ (type ‘const 
rostlab::blast::hit’) to type ‘char’
  186 |   { if( v_i != v.begin() ) os << ", "; os << *v_i; }
  |~~~^~~
/usr/include/c++/12/ostream:534:5: note: candidate: ‘template 
std::basic_ostream& std::operator<<(basic_ostream&, signed char)’
  534 | operator<<(basic_ostream& __out, signed char __c)
  | ^~~~
/usr/include/c++/12/ostream:534:5: note:   template argument 
deduction/substitution failed:
/usr/include/rostlab/aux_functions.h:186:43: note:   cannot convert 
‘v_i.__gnu_cxx::__normal_iterator >::operator*()’ (type ‘const 
rostlab::blast::hit’) to type ‘signed char’
  186 |   { if( v_i != v.begin() ) os << ", "; os << *v_i; }
  |~~~^~~
/usr/include/c++/12/ostream:539:5: note: candidate: ‘template 
std::basic_ostream& std::operator<<(basic_ostream&, unsigned char)’
  539 | operator<<(basic_ostream& __out, unsigned char __c)
  | ^~~~
/usr/include/c++/12/ostream:539:5: note:   template argument 
deduction/substitution failed:
/usr/include/rostlab/aux_functions.h:186:43: note:   cannot convert 
‘v_i.__gnu_cxx::__normal_iterator >::operator*()’ (type ‘const 
rostlab::blast::hit’) to type ‘unsigned char’
  186 |   { if( v_i != v.begin() ) os << ", "; os << *v_i; }
  |~~~^~~
/usr/include/c++/12/ostream:598:5: note: candidate: ‘template std::basic_ostream<_CharT, _Traits>& 
std::operator<<(basic_ostream<_CharT, _Traits>&, const _CharT*)’
  598 | operator<<(basic_ostream<_CharT, _Traits>& __out, const _CharT* __s)
  | ^~~~
/usr/include/c++/12/ostream:598:5: note:   template argument 
deduction/substitution failed:
/usr/include/rostlab/aux_functions.h:186:43: note:   mismatched types ‘const 
_CharT*’ and ‘rostlab::blast::hit’
  186 |   { if( v_i != v.begin() ) os << ", "; os << *v_i; }
  |~~~^~~
/usr/include/c++/12/bits/ostream.tcc:302:5: note: candidate: ‘template std::basic_ostream<_CharT, _Traits>& 
std::operator<<(basic_ostream<_CharT, _Traits>&, const char*)’
  302 | operator<<(basic_ostream<_CharT, _Traits>& __out, const char* __s)
  | ^~~~
/usr/include/c++/12/bits/ostream.tcc:302:5: note:   template argument 

Processed: closing 1017401

[Debian Bug Tracking System]

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

> close 1017401 3.4.1.0-3
Bug #1017401 [src:haskell-cabal-install] haskell-cabal-install: FTBFS in 
bookworm: Depends: libghc-resolv-dev (>= 0.1.1) but it is not installable
Ignoring request to alter fixed versions of bug #1017401 to the same values 
previously set
Bug #1017401 [src:haskell-cabal-install] haskell-cabal-install: FTBFS in 
bookworm: Depends: libghc-resolv-dev (>= 0.1.1) but it is not installable
Marked Bug as done
> thanks
Stopping processing here.

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

Processed: closing 1017227

[Debian Bug Tracking System]

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

> close 1017227 1.1.2.0-2
Bug #1017227 [src:haskell-snap-server] haskell-snap-server: FTBFS: 
unsatisfiable build-dependency: libghc-attoparsec-dev (< 0.14) but 0.14.4-2 is 
to be installed
Marked as fixed in versions haskell-snap-server/1.1.2.0-2.
Bug #1017227 [src:haskell-snap-server] haskell-snap-server: FTBFS: 
unsatisfiable build-dependency: libghc-attoparsec-dev (< 0.14) but 0.14.4-2 is 
to be installed
Marked Bug as done
> thanks
Stopping processing here.

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

Bug#1020991: marked as done (php-twig: CVE-2022-39261)

[Debian Bug Tracking System]

Your message dated Fri, 30 Sep 2022 10:20:48 +
with message-id 
and subject line Bug#1020991: fixed in php-twig 3.4.3-1
has caused the Debian Bug report #1020991,
regarding php-twig: CVE-2022-39261
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.)


-- 
1020991: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020991
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: php-twig
Version: 3.4.2-1
Severity: grave
Tags: security upstream
X-Debbugs-Cc: car...@debian.org, Debian Security Team 

Hi,

The following vulnerability was published for php-twig.

CVE-2022-39261[0]:
| Twig is a template language for PHP. Versions 1.x prior to 1.44.7, 2.x
| prior to 2.15.3, and 3.x prior to 3.4.3 encounter an issue when the
| filesystem loader loads templates for which the name is a user input.
| It is possible to use the `source` or `include` statement to read
| arbitrary files from outside the templates' directory when using a
| namespace like `@somewhere/../some.file`. In such a case, validation
| is bypassed. Versions 1.44.7, 2.15.3, and 3.4.3 contain a fix for
| validation of such template names. There are no known workarounds
| aside from upgrading.


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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2022-39261
https://www.cve.org/CVERecord?id=CVE-2022-39261
[1] https://github.com/twigphp/Twig/security/advisories/GHSA-52m2-vc4m-jj33
[2] 
https://github.com/twigphp/Twig/commit/35f3035c5deb0041da7b84daf02dea074ddc7a0b

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: php-twig
Source-Version: 3.4.3-1
Done: David Prévot 

We believe that the bug you reported is fixed in the latest version of
php-twig, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1020...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
David Prévot  (supplier of updated php-twig 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: Fri, 30 Sep 2022 10:59:34 +0200
Source: php-twig
Architecture: source
Version: 3.4.3-1
Distribution: unstable
Urgency: medium
Maintainer: Debian PHP PEAR Maintainers 
Changed-By: David Prévot 
Closes: 1020991
Changes:
 php-twig (3.4.3-1) unstable; urgency=medium
 .
   [ Fabien Potencier ]
   * Fix a security issue on filesystem loader (possibility to load a
 template outside a configured directory)
 [CVE-2022-39261] (Closes: #1020991)
   * Prepare the 3.4.3 release
 .
   [ David Prevot ]
   * Update Standards-Version to 4.6.1
Checksums-Sha1:
 59308c88c56efa96703a5c9e3008a3d0b90ce08a 2854 php-twig_3.4.3-1.dsc
 6a4d5ae906fc12b8cf6cfe4cc8b6c0158578568a 201928 php-twig_3.4.3.orig.tar.xz
 a4e5923acc3b461a9b03d64e97ab0e2c1af53e63 18424 php-twig_3.4.3-1.debian.tar.xz
 776ece42f3e933e9fa4ddf78342c9272daee2b71 8929 php-twig_3.4.3-1_source.buildinfo
Checksums-Sha256:
 3ced43ffca09d5bb84795af05c060d14d758b48e4e76713bd7e1a54a6fdd1595 2854 
php-twig_3.4.3-1.dsc
 fed79cc640e6bd8511d62c56c65226d0e6999e3f34492bf986ec925a2147947b 201928 
php-twig_3.4.3.orig.tar.xz
 1831bb4887155aaace6fbc39af4543ef5af99e1fb0537dfcc89e54d536e9728f 18424 
php-twig_3.4.3-1.debian.tar.xz
 433f343d66058b10e23a42c3bb99ab22bc689f491ca9cda6314653cfee9d9851 8929 
php-twig_3.4.3-1_source.buildinfo
Files:
 e66286228be8d710b0ffb220abfca581 2854 php optional php-twig_3.4.3-1.dsc
 fd37a06822a6b28c718e8a0d8889f9cc 201928 php optional php-twig_3.4.3.orig.tar.xz
 3042b2e518127f70b7aafcfbeddc1e19 18424 php optional 
php-twig_3.4.3-1.debian.tar.xz
 d4b7d75650adbfb28a6d6dedb1b39698 8929 php optional 
php-twig_3.4.3-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQEzBAEBCAAdFiEEeHVNB7wJXHRI941mBYwc+UT2vTwFAmM2v7gACgkQBYwc+UT2
vTyF8wf/RUMLYZBRQjBXQipzj0Dtx0VrBJbq7fUh7I3vl5IygOJUzJGuO/t5WhBV
zGTosVy02T7nQna3lpZ6Mx3ufH4suseiykP4RJjhDbLMlaA0kSGHesQG1k+W2qNz
7EBlP1bqZt2bE4gzYhvKNbNXt3TkOYYZAqkTcz9H8GEnmeemQOOw8aIw/tMMpuHU
RkhQ/K3H88DpZSqHdsZz1usCe+NWO6q9GtnUkEsyhyoEIJYJoLEtzwQzjzyFPY4j

Processed: reassign 1019685 to node-rollup-plugin-node-resolve, found 1019685 in 14.0.0+ds-1 ...

[Debian Bug Tracking System]

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

> reassign 1019685 node-rollup-plugin-node-resolve
Bug #1019685 {Done: Yadd } [src:node-babel7] node-babel7: 
FTBFS in sid
Bug reassigned from package 'src:node-babel7' to 
'node-rollup-plugin-node-resolve'.
No longer marked as found in versions node-babel7/7.18.13+~cs214.250.184-2.
No longer marked as fixed in versions node-babel7/7.18.13+~cs214.250.184-3.
> found 1019685 14.0.0+ds-1
Bug #1019685 {Done: Yadd } [node-rollup-plugin-node-resolve] 
node-babel7: FTBFS in sid
Marked as found in versions node-rollup-plugin-node-resolve/14.0.0+ds-1 and 
reopened.
> fixed 1019685 14.1.0+ds-1
Bug #1019685 [node-rollup-plugin-node-resolve] node-babel7: FTBFS in sid
There is no source info for the package 'node-rollup-plugin-node-resolve' at 
version '14.1.0+ds-1' with architecture ''
Unable to make a source version for version '14.1.0+ds-1'
Marked as fixed in versions 14.1.0+ds-1.
> reopen 1020201
Bug #1020201 {Done: Yadd } [node-rollup-plugin-node-resolve] 
Update @rollup/plugin-node-resolve to 14.1.0 due to regression in 14.0.0
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions 14.1.0+ds-1.
> forcemerge 1019685 1020201
Bug #1019685 [node-rollup-plugin-node-resolve] node-babel7: FTBFS in sid
Bug #1020201 [node-rollup-plugin-node-resolve] Update 
@rollup/plugin-node-resolve to 14.1.0 due to regression in 14.0.0
Removed indication that 1020201 affects node-rollup-plugin-node-polyfills
There is no source info for the package 'node-rollup-plugin-node-resolve' at 
version '14.1.0+ds-1' with architecture ''
Unable to make a source version for version '14.1.0+ds-1'
Marked as fixed in versions 14.1.0+ds-1.
Bug #1019685 [node-rollup-plugin-node-resolve] node-babel7: FTBFS in sid
Added tag(s) ftbfs, bookworm, and sid.
Merged 1019685 1020201
> close 1019685
Bug #1019685 [node-rollup-plugin-node-resolve] node-babel7: FTBFS in sid
Bug #1020201 [node-rollup-plugin-node-resolve] Update 
@rollup/plugin-node-resolve to 14.1.0 due to regression in 14.0.0
Marked Bug as done
Marked Bug as done
> thanks
Stopping processing here.

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

Bug#976269: marked as done ([20201202] mirror.intergrid.com.au: sync-frequency, ftpsync-version)

[Debian Bug Tracking System]

Your message dated Fri, 30 Sep 2022 10:16:40 +
with message-id <6336c2089c161_2528496010...@godard.mail>
and subject line Bug#976269 fixed in mirrors
has caused the Debian Bug report #976269,
regarding [20201202] mirror.intergrid.com.au: sync-frequency, ftpsync-version
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.)


-- 
976269: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976269
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: mirrors
Severity: normal
X-Debbugs-Cc: Javed Ali 

Hi,

I was checking some things in the Debian mirror universe and noticed
a problem with your mirror:

Looking at
https://mirror-master.debian.org/status/mirror-info/mirror.intergrid.com.au.html
it seems you only sync about once a day.  The Debian archive updates 4 times a
day, and we expect mirrors listed in our mirror list to follow that
cadence.

A couple other things to note:

o The tracefile at
  http://mirror.intergrid.com.au/debian/project/trace/mirror.intergrid.com.au
  is missing some required information.

  We expect at least the Maintainer and Upstream-mirror values to be filled in,
  and your tracefile is missing one or both of them.

o The tracefile
  http://mirror.intergrid.com.au/debian/project/trace/mirror.intergrid.com.au
  suggests that the ftpsync version you are using is old.  Please upgrade.

  Using a modern ftpsync ensures updates are done in the correct order
  so apt clients don't get confused.   In particular, it processes
  translations, contents, and more files that have been added to the
  archive in recent years in the correct stage.  It also should produce
  trace files that contain more information that is useful for us and helps
  downstream mirrors sync better.

  http://mirror.intergrid.com.au/debian/project/ftpsync/ftpsync-current.tar.gz

Thanks,
Julien
--- End Message ---
--- Begin Message ---
Hello,

Bug #976269 in mirrors reported by you has been fixed in the Git repository.
You can see the commit message below and you can check the diff of the fix at:

https://salsa.debian.org/mirror-team/masterlist/-/commit/f974ccd16c2ed1885256f5c9f823ac3b993bbab7


Remove mirror.intergrid.com.au

Out of date for over a year.

Closes: #976269


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/976269--- End Message ---

Bug#1014797: marked as done (FTBFS: test failures with new libgd3)

[Debian Bug Tracking System]

Your message dated Fri, 30 Sep 2022 09:49:09 +
with message-id 
and subject line Bug#1014797: fixed in gbrowse 2.56+dfsg-11
has caused the Debian Bug report #1014797,
regarding FTBFS: test failures with new libgd3
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.)


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

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

While working on libgd-perl and libgd-graph-perl (#1014741) I noticed
that gbrowse has issues with the new lbgd(3) as well:

On ci.debian.net we have e.g.
https://ci.debian.net/data/autopkgtest/testing/amd64/g/gbrowse/23582883/log.gz

Test Summary Report
- ---
t/05.deferredrendering.t (Wstat: 6400 Tests: 15 Failed: 6)
  Failed tests:  5, 7, 9, 11, 13-14
  Non-zero exit status: 25
  Parse errors: Bad plan.  You planned 19 tests but ran 15.
Files=6, Tests=222, 17 wallclock secs ( 0.03 usr  0.01 sys +  4.67 cusr  0.79 
csys =  5.50 CPU)
Result: FAIL


During a local rebuild, even more tests fail:

Test Summary Report
- ---
t/03.render.t   (Wstat: 6400 Tests: 48 Failed: 0)
  Non-zero exit status: 25
  Parse errors: Bad plan.  You planned 150 tests but ran 48.
t/04.remoteserver.t (Wstat: 0 Tests: 39 Failed: 10)
  Failed tests:  8, 11, 14, 20, 23, 26, 32, 35, 38-39
  Parse errors: Bad plan.  You planned 43 tests but ran 39.
t/05.deferredrendering.t (Wstat: 6400 Tests: 15 Failed: 6)
  Failed tests:  5, 7, 9, 11, 13-14
  Non-zero exit status: 25
  Parse errors: Bad plan.  You planned 19 tests but ran 15.
Files=10, Tests=338, 33 wallclock secs ( 0.08 usr  0.03 sys + 14.09 cusr  1.71 
csys = 15.91 CPU)
Result: FAIL


In my limited understanding, error like

GD Warning: GD2 image support has been disabled
gdImageGd2Ptr error at /usr/lib/x86_64-linux-gnu/perl/5.34/Storable.pm line 
285, at /build/gbrowse-2.56+dfsg/t/../lib/Bio/Graphics/Browser2/CachedTrack.pm 
line 158.

come from the removal of some formats in libgd(3).


Cheers,
gregor


-BEGIN PGP SIGNATURE-

iQKTBAEBCgB9FiEE0eExbpOnYKgQTYX6uzpoAYZJqgYFAmLNMWBfFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEQx
RTEzMTZFOTNBNzYwQTgxMDREODVGQUJCM0E2ODAxODY0OUFBMDYACgkQuzpoAYZJ
qgZ+MRAAqCv4lC4CwC55QB4vGWqQTrvarhaXnGUFmJDxgyTRTI0rTpV8emBTNbhO
n6ruxd/Y47kIcys6V4JXlfQORAiKBNe680k1kK0I+nSU11/udtHllElxFc9Lk6ng
VTTtdNk6QQgtJUiHlNGkvGsEw3p6738ARJDcCeYD2nLYQRsgAG8m15lMP/DDVd1z
3CLC7Z7fER7CLbPdruLbuSMO9k5aq/BwfhRMJLHD6ieft3cWPjudOHy02PoyyP3d
nFbWWnski5Go46RtVH4wWmCKHwjw/VmjxQ3Dk8cxhrWJjX2GMrwXyYb+iYFkOES2
VfPDEGnq1hH33rbib0mIFMuKc3hmyRsC4ncgrOySZz0Gl/MS/wIhnlozJYUNCO91
6wMjQvUYXs+0GuD4msJDtDxZaEkJo0uT8NzlhnJ4z8KioslyEY0vhwXdnptaDso7
96XM+tdS/+uibtjwMUe0lX32kMgM0X9NxCxeCE4yKIIXo8FnOhASahj4oYQz6VPZ
J3M3nvu/G5PTwOPW/m8GkMe1iMXWBgQhKFDjY4e+qQZToNTot7lDvsuYPBfxcnRV
SlxSUgAE+EDKtUpqrOWD9C/7dgR1sBmBtACYMzDhMtKbIptrXEjXBvOdZQ54yA2C
Rwo8kus9L08fqQalrs1QZXkkNEPVLPAvkI4x8/lr8jz3HYL4zT8=
=VAVx
-END PGP SIGNATURE-
--- End Message ---
--- Begin Message ---
Source: gbrowse
Source-Version: 2.56+dfsg-11
Done: Olivier Sallou 

We believe that the bug you reported is fixed in the latest version of
gbrowse, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1014...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Olivier Sallou  (supplier of updated gbrowse 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: Fri, 30 Sep 2022 09:26:00 +
Source: gbrowse
Architecture: source
Version: 2.56+dfsg-11
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Olivier Sallou 
Closes: 1014797
Changes:
 gbrowse (2.56+dfsg-11) unstable; urgency=medium
 .
   * Remove gd2 deprecated calls and use png for images
 (tests and build are fine but could not test rendering)
 Closes: #1014797.
Checksums-Sha1:
 0c7841a4f093c1fe827e0f0c0744f1cdd4ad495a 2678 gbrowse_2.56+dfsg-11.dsc
 

Processed: closing 1017215

[Debian Bug Tracking System]

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

> close 1017215 0.19.6-2
Bug #1017215 [src:haskell-shake] libghc-shake-dev and libghc-shake-data both 
ship /usr/lib/haskell-packages/extra-packages/shake-0.19.6
Marked as fixed in versions haskell-shake/0.19.6-2.
Bug #1017215 [src:haskell-shake] libghc-shake-dev and libghc-shake-data both 
ship /usr/lib/haskell-packages/extra-packages/shake-0.19.6
Marked Bug as done
> thanks
Stopping processing here.

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

Bug#1019390: marked as done (o2: autopkgtest regression on i386 and s390x: Assertion `arg->v.vf[i] == 123.456F + i' failed.)

[Debian Bug Tracking System]

Your message dated Fri, 30 Sep 2022 09:18:57 +
with message-id 
and subject line Bug#1019390: fixed in o2 1.1~ds-2
has caused the Debian Bug report #1019390,
regarding o2: autopkgtest regression on i386 and s390x: Assertion `arg->v.vf[i] 
== 123.456F + i' failed.
to be marked as done.

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

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


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

Source: o2
Version: 1.1~ds-1
Severity: serious
User: debian...@lists.debian.org
Usertags: regression

Dear maintainer(s),

With a recent upload of o2 the autopkgtest of o2 fails in testing on 
i386 and s390x when that autopkgtest is run with the binary packages of 
o2 from unstable. It passes when run with only packages from testing. In 
tabular form:


   passfail
o2 from testing1.1~ds-1
all others from testingfrom testing

I copied some of the output on i386 at the bottom of this report.

Currently this regression is blocking the migration to testing [1]. Can 
you please investigate the situation and fix it?


More information about this bug and the reason for filing it can be found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation

Paul

[1] https://qa.debian.org/excuses.php?package=o2

https://ci.debian.net/data/autopkgtest/testing/i386/o/o2/24929151/log.gz

make: Entering directory 
'/tmp/autopkgtest-lxc.xo3rn8r3/downtmp/build.74d/src/debian/tests'

./arraytest
DONE sending [3456]
DONE sending []
DONE sending [123, 234]
DONE sending [xixdx] messages
DONE sending 456,[456,12345][1234.56,1234.567,2345.678],1234.567
arraytest: ../../test/arraytest.c:502: service_ifvxif: Assertion 
`arg->v.vf[i] == 123.456F + i' failed.

make: *** [Makefile:64: arraytest.test] Aborted
make: Leaving directory 
'/tmp/autopkgtest-lxc.xo3rn8r3/downtmp/build.74d/src/debian/tests'

autopkgtest [19:16:11]: test simple_run



OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: o2
Source-Version: 1.1~ds-2
Done: IOhannes m zmölnig (Debian/GNU) 

We believe that the bug you reported is fixed in the latest version of
o2, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1019...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
IOhannes m zmölnig (Debian/GNU)  (supplier of updated o2 
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: Fri, 30 Sep 2022 10:55:44 +0200
Source: o2
Architecture: source
Version: 1.1~ds-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Multimedia Maintainers 
Changed-By: IOhannes m zmölnig (Debian/GNU) 
Closes: 1019390
Changes:
 o2 (1.1~ds-2) unstable; urgency=medium
 .
   [ IOhannes m zmölnig (Debian/GNU) ]
   * Add patch to fix hashing on BIGendian machine
   * Add patch to fix float-comparision (use epsilon)
 (Closes: #1019390)
 .
   [ Debian Janitor ]
   * Update renamed lintian tag names in lintian overrides.
Checksums-Sha1:
 f53aa2a3d4e2e2180c78fc55db2d3aa93fa52732 2162 o2_1.1~ds-2.dsc
 1d2703a53cc02250ed927cab0a07017265a3f2d9 7544 o2_1.1~ds-2.debian.tar.xz
Checksums-Sha256:
 4907f3ba2ff7d22d0252bf7a8fb26cff4fe92e266cec90794fe152510f1e66cc 2162 
o2_1.1~ds-2.dsc
 823afeecaa940601b66b6318f48e422e64c7b3e5eeb8742be19546459b702fb7 7544 
o2_1.1~ds-2.debian.tar.xz
Files:
 012338782aef84571d29380cfec4ad32 2162 libs optional o2_1.1~ds-2.dsc
 7be09f46a8970a942f9b977db149ee86 7544 libs optional o2_1.1~ds-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEdAXnRVdICXNIABVttlAZxH96NvgFAmM2sAAACgkQtlAZxH96
NviW0g/+PWD4CrsgavEBYLnHTKm2wT1XBlRBZogcWSaPZ4LtkVKJLQcipGavrGP3
mX0moYIPm3efBsL+a02WehB4SnACFy5oPq9rlqLPZLU1//k+Xah6dBxxpO5SbGoW
m4NYGjtef0PiVlg/IMCKQpFkvsaLWuYUXfsQvu1UYrZtlFlEIUADmhIbzA/5b0Fl
dD6B7ms+BHDCwPSuRUdcFmda6ceuAPQ8+rkvf9Gm3gqEE2AJBIbHiZVbSFxvwbnu
N7SfkD38AoDcvct3MXEq0s1fANUaYWOlqlNt0nAAH0ckcKZQPtOq7u8Vwbv6gxQd
/+zG5rdJ8mf1o8VKupJvFENq5piebs77U5iKe0RaqA/yeA66hj/kKniPQG+5PmbJ
fHNU6IHJXKgivuNBHDNKTOnlV1N3lSKnBmK6h7qWNEbm5ql+F8k3HqRKL2LLJkc7

Processed: closing 1020993

[Debian Bug Tracking System]

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

> close 1020993 3.3.21-3
Bug #1020993 [src:haskell-warp] haskell-warp: FTBFS on mipsel: E: Build killed 
with signal TERM after 150 minutes of inactivity
The source 'haskell-warp' and version '3.3.21-3' do not appear to match any 
binary packages
Marked as fixed in versions haskell-warp/3.3.21-3.
Bug #1020993 [src:haskell-warp] haskell-warp: FTBFS on mipsel: E: Build killed 
with signal TERM after 150 minutes of inactivity
Marked Bug as done
> thanks
Stopping processing here.

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

Bug#1015328: marked as done (ruby-netcdf: FTBFS: ERROR: Test "ruby3.1" failed.)

[Debian Bug Tracking System]

Your message dated Fri, 30 Sep 2022 07:50:15 +
with message-id 
and subject line Bug#1015328: fixed in ruby-netcdf 0.8.0-3
has caused the Debian Bug report #1015328,
regarding ruby-netcdf: FTBFS: ERROR: Test "ruby3.1" failed.
to be marked as done.

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

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


-- 
1015328: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1015328
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-netcdf
Version: 0.8.0-2
Severity: important
Justification: FTBFS
Tags: bookworm sid ftbfs
User: debian-r...@lists.debian.org
Usertags: ruby3.1

Hi,

We are about to start the ruby3.1 transition in unstable. While trying to
rebuild ruby-netcdf with ruby3.1 enabled, the build failed.

Relevant part of the build log (hopefully):
> /usr/bin/ruby3.1 /usr/bin/gem2deb-test-runner
> 
> ┌──┐
> │ Run tests for ruby3.1 from debian/ruby-test-files.yaml  
>  │
> └──┘
> 
> RUBYLIB=/<>/debian/ruby-netcdf/usr/lib/x86_64-linux-gnu/ruby/vendor_ruby/3.1.0:/<>/debian/ruby-netcdf/usr/lib/ruby/vendor_ruby:.
>  
> GEM_PATH=/<>/debian/ruby-netcdf/usr/share/rubygems-integration/3.1.0:/var/lib/gems/3.1.0:/usr/local/lib/ruby/gems/3.1.0:/usr/lib/ruby/gems/3.1.0:/usr/lib/x86_64-linux-gnu/ruby/gems/3.1.0:/usr/share/rubygems-integration/3.1.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/3.1.0
>  ruby3.1 -ryaml -e YAML.load_file\(\"debian/ruby-test-files.yaml\"\).each\ 
> \{\ \|f\|\ require\ f\ \}
> Loaded suite -e
> Started
> F
> ===
> Failure: test_clone_netcdf_clone(TestClone):  is not true.
> /<>/test/clone.rb:43:in `test_clone_netcdf_clone'
>  40: 
>  41:   def test_clone_netcdf_clone
>  42: f = @f.clone
>   => 43: assert(@f.frozen? == f.frozen?)
>  44: # d = @d.dup
>  45: # v = @v.dup
>  46: # a = @a.dup
> ===
> F
> ===
> Failure: test_clone_netcdf_path(TestClone):  is not true.
> /<>/test/clone.rb:32:in `test_clone_netcdf_path'
>  29:   def test_clone_netcdf_path
>  30: f = @f.clone
>  31: assert_equal @f.path, f.path
>   => 32: assert(@f.frozen? == f.frozen?)
>  33: d = @d.clone
>  34: assert_equal @d, d
>  35: v = @v.clone
> ===
> .E
> ===
> Error: test_unpack_type_fixed_to_sfloat(TestFactorOffset): NetcdfBadid: 
> NetCDF: Not a valid ID
> /<>/debian/ruby-netcdf/usr/lib/ruby/vendor_ruby/numru/netcdf.rb:316:in
>  `put_attraw'
> /<>/debian/ruby-netcdf/usr/lib/ruby/vendor_ruby/numru/netcdf.rb:316:in
>  `put_att'
> /<>/test/factor_offset.rb:16:in `setup'
> ===
> 
> Finished in 0.063008154 seconds.
> ---
> 20 tests, 122 assertions, 2 failures, 1 errors, 0 pendings, 0 omissions, 0 
> notifications
> 85% passed
> ---
> 317.42 tests/s, 1936.26 assertions/s
> ERROR: Test "ruby3.1" failed.


The full build log is available from:
https://people.debian.org/~terceiro/ruby3.1/ruby-netcdf_0.8.0-2+rebuild1658139020_amd64.log

To reproduce this, you need to install ruby-all-dev >= 1:3.0+2 (in 
experimental).
If you fail to reproduce, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.

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

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


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: ruby-netcdf
Source-Version: 0.8.0-3
Done: Youhei SASAKI 

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

Bug#1006818: marked as done (intermediary files embed arch-specific path)

[Debian Bug Tracking System]

Your message dated Fri, 30 Sep 2022 06:35:00 +
with message-id 
and subject line Bug#1006818: fixed in eye 22.0203.1955~ds-2
has caused the Debian Bug report #1006818,
regarding intermediary files embed arch-specific path
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.)


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

Source: eye
Version: 19.0221.2026~ds-1
Severity: serious
User: debian...@lists.debian.org
Usertags: fails-always

Dear maintainer(s),

You package has an autopkgtest, great. However, it fails on all 
architectures but amd64. Can you please investigate the situation and 
fix it?


I copied some of the output at the bottom of this report. It seems that 
eye is expecting the run on amd64 exclusively. If that can't be 
reasonably be fixed, then please mark your test for amd64 exclusively 
(with the relatively new "Architecture" field in d/t/control).


More information about this bug and the reason for filing it can be found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation

Paul

[1] https://ci.debian.net/packages/e/eye/

https://ci.debian.net/data/autopkgtest/testing/arm64/e/eye/19245228/log.gz

autopkgtest [11:10:11]: test command1: prove debian/tests/*.t
autopkgtest [11:10:11]: test command1: [---

#   Failed test 'Check return from 'eye.pvm' is 0'
#   at debian/tests/eye.pvm.t line 9.
#  got: '127'
# expected: '0'

#   Failed test 'bare command, stderr'
#   at debian/tests/eye.pvm.t line 11.
#   '/usr/bin/eye.pvm: 3: exec: 
/usr/lib/swi-prolog/bin/x86_64-linux/swipl: not found

# '
# doesn't match '(?^:Usage: eye.pvm)'

#   Failed test 'Check return from 'eye.pvm --help' is 0'
#   at debian/tests/eye.pvm.t line 13.
#  got: '127'
# expected: '0'

#   Failed test 'help, stderr'
#   at debian/tests/eye.pvm.t line 15.
#   '/usr/bin/eye.pvm: 3: exec: 
/usr/lib/swi-prolog/bin/x86_64-linux/swipl: not found

# '
# doesn't match '(?^:Usage: eye.pvm)'

#   Failed test 'Check return from 'eye.pvm --n3 
reasoning/socrates/socrates.n3 --query 
reasoning/socrates/socrates-query.n3' is 0'

#   at debian/tests/eye.pvm.t line 17.
#  got: '127'
# expected: '0'

#   Failed test 'help, stderr'
#   at debian/tests/eye.pvm.t line 18.
#   ''
# doesn't match '(?^:r:because)'

#   Failed test 'help, stderr'
#   at debian/tests/eye.pvm.t line 19.
#   '/usr/bin/eye.pvm: 3: exec: 
/usr/lib/swi-prolog/bin/x86_64-linux/swipl: not found

# '
# doesn't match '(?^s:starting .*\nGET .*\nnetworking .*\nreasoning)'
# Looks like you failed 7 tests of 15.
debian/tests/eye.pvm.t ..
Dubious, test returned 7 (wstat 1792, 0x700)
Failed 7/15 subtests

Test Summary Report
---
debian/tests/eye.pvm.t (Wstat: 1792 Tests: 15 Failed: 7)
  Failed tests:  3, 5, 8, 10, 13-15
  Non-zero exit status: 7
Files=1, Tests=15,  0 wallclock secs ( 0.02 usr  0.00 sys +  0.06 cusr 
0.02 csys =  0.10 CPU)

Result: FAIL
autopkgtest [11:10:11]: test command1: ---]


OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: eye
Source-Version: 22.0203.1955~ds-2
Done: Jonas Smedegaard 

We believe that the bug you reported is fixed in the latest version of
eye, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1006...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Jonas Smedegaard  (supplier of updated eye 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: Fri, 30 Sep 2022 08:20:17 +0200
Source: eye
Architecture: source
Version: 22.0203.1955~ds-2
Distribution: unstable
Urgency: medium
Maintainer: Jonas Smedegaard 
Changed-By: Jonas Smedegaard 
Closes: 1006818
Changes:
 eye (22.0203.1955~ds-2) unstable; urgency=medium
 .
   * fix use swipl executable in PATH;
 tighten build-dependency on swi-prolog-nox;
 closes: bug#1006818,
 thanks to Paul Gevers, Adrian Bunk, and Lev Lamberov
Checksums-Sha1: