Processed: Re: Processed: Re: tpm2-abrmd: Daemon fails to start: needs to be rebuilt against newer libtss2-esys0

[Debian Bug Tracking System]

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

> tags 972118 + sid bullseye
Bug #972118 {Done: Ying-Chun Liu (PaulLiu) } [tpm2-abrmd] 
tpm2-abrmd: Daemon fails to start: needs to be rebuilt against newer 
libtss2-esys0
Added tag(s) sid and bullseye.
> stop
Stopping processing here.

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

Bug#975228: marked as done (xdg-utils: FTBFS: tests failed)

[Debian Bug Tracking System]

Your message dated Mon, 18 Jan 2021 07:03:45 +
with message-id 
and subject line Bug#975228: fixed in xdg-utils 1.1.3-3
has caused the Debian Bug report #975228,
regarding xdg-utils: FTBFS: tests 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.)


-- 
975228: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=975228
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: xdg-utils
Version: 1.1.3-2
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201119 ftbfs-bullseye

Hi,

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

Relevant part (hopefully):
> make[3]: Entering directory '/<>/autotests'
> rm -f failed-tests
> * Testing that xdg-email
>   - uses kmailservice to launch the default e-mail client in KDE3
>   - uses kde-open to launch the default e-mail client in KDE4
>   - uses kde-open5 to launch the default e-mail client in KDE5
>   - uses run_thunderbird if default e-mail client is Thunderbird in KDE5
> * Testing that xdg-icon-resource
>   - installs a png icon system-wide
> * Testing that xdg-mime query default
>   - reads $XDG_CONFIG_HOME/mimeapps.list
> * Testing that xdg-open
>   - opens a URL with gio open in recent GNOME 3, and Cinnamon
> ASSERTION FAILED: expected command to be run: gio open 
> http://www.freedesktop.org/
> ASSERTION FAILED: expected command to be run: gio open 
> http://www.freedesktop.org/
>   - opens a URL with gvfs-open if gio open is missing in GNOME 3, GNOME 2, 
> and Cinnamon
>   - opens a URL with gnome-open if gio open and gvfs-open are missing in 
> GNOME 2
>   - opens a URL with the generic method if gio open and gvfs-open are missing 
> in GNOME 3, and Cinnamon
>   - opens a URL with the generic method if gio open, gvfs-open and gnome-open 
> are missing in GNOME 2
>   - opens a URL with kfmclient in KDE 3
>   - opens a URL with kde-open in KDE 4
>   - opens a URL with kde-open5 in KDE 5
>   - opens a URL with gvfs-open in MATE
>   - opens a URL with mate-open if gio open and gvfs-open are missing in MATE
>   - opens a URL with exo-open in XFCE
>   - opens a URL with enlightenment_open in Enlightenment
>   - opens a file path with pcmanfm in LXDE
>   - percent-decodes a file:// URL and opens it with pcmanfm in LXDE
>   - opens files with spaces in their name in LXDE
>   - looks up x-scheme-handler/* in LXDE
>   - looks up x-scheme-handler/* in generic mode
>   - works with multi-word $BROWSER commands
>   - is not vulnerable to command injection in URLs when using $BROWSER in 
> generic mode
>   - is not vulnerable to argument injection in URLs when using $BROWSER in 
> generic mode
>   - opens files in generic mode
>   - opens files with # characters in their name in generic mode
>   - opens files with spaces in their name in generic mode
> * Testing that xdg-screensaver
>   - calls xset -dpms, xset +dpms and xset dpms force when performing reset
> * Testing that xdg-settings
>   - determines default browser using GConf in GNOME 2
>   - determines default browser from $XDG_CONFIG_HOME/mimeapps.list in gnome3
>   - determines default URL handler from $XDG_CONFIG_HOME/mimeapps.list in 
> gnome3
>   - determines default browser from $XDG_CONFIG_HOME/mimeapps.list in cinnamon
>   - determines default URL handler from $XDG_CONFIG_HOME/mimeapps.list in 
> cinnamon
>   - determines default browser from $XDG_CONFIG_HOME/mimeapps.list in lxde
>   - determines default URL handler from $XDG_CONFIG_HOME/mimeapps.list in lxde
>   - determines default browser from $XDG_CONFIG_HOME/mimeapps.list in mate
>   - determines default URL handler from $XDG_CONFIG_HOME/mimeapps.list in mate
>   - determines default browser from $XDG_CONFIG_HOME/mimeapps.list in generic
>   - determines default URL handler from $XDG_CONFIG_HOME/mimeapps.list in 
> generic
>   - uses $BROWSER in generic mode
> 
> TEST FAILURES:
> 
> t-xdg-open.sh: Assertion failed when testing that xdg-open opens a URL with 
> gio open in recent GNOME 3, and Cinnamon: expected command to be run: gio 
> open http://www.freedesktop.org/
> t-xdg-open.sh: Assertion failed when testing that xdg-open opens a URL with 
> gio open in recent GNOME 3, and Cinnamon: expected command to be run: gio 
> open http://www.freedesktop.org/
> 
> make[3]: *** [Makefile:6: test] Error 1

The full build log is available from:
   http://qa-logs.debian.net/2020/11/19/xdg-utils_1.1.3-2_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!

About 

Bug#973096: marked as done (python-bleach: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.9 3.8" returned exit code 13)

[Debian Bug Tracking System]

Your message dated Mon, 18 Jan 2021 06:48:52 +
with message-id 
and subject line Bug#973096: fixed in python-bleach 3.2.1-2
has caused the Debian Bug report #973096,
regarding python-bleach: FTBFS: dh_auto_test: error: pybuild --test 
--test-pytest -i python{version} -p "3.9 3.8" returned exit code 13
to be marked as done.

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

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


-- 
973096: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973096
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-bleach
Version: 3.2.1-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201027 ftbfs-bullseye

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 -O--buildsystem=pybuild
> I: pybuild base:217: /usr/bin/python3.9 setup.py build 
> running build
> running build_py
> creating /<>/.pybuild/cpython3_3.9_bleach/build/bleach
> copying bleach/callbacks.py -> 
> /<>/.pybuild/cpython3_3.9_bleach/build/bleach
> copying bleach/__init__.py -> 
> /<>/.pybuild/cpython3_3.9_bleach/build/bleach
> copying bleach/html5lib_shim.py -> 
> /<>/.pybuild/cpython3_3.9_bleach/build/bleach
> copying bleach/linkifier.py -> 
> /<>/.pybuild/cpython3_3.9_bleach/build/bleach
> copying bleach/sanitizer.py -> 
> /<>/.pybuild/cpython3_3.9_bleach/build/bleach
> copying bleach/utils.py -> 
> /<>/.pybuild/cpython3_3.9_bleach/build/bleach
> creating /<>/.pybuild/cpython3_3.9_bleach/build/bleach/_vendor
> copying bleach/_vendor/__init__.py -> 
> /<>/.pybuild/cpython3_3.9_bleach/build/bleach/_vendor
> creating 
> /<>/.pybuild/cpython3_3.9_bleach/build/bleach/_vendor/html5lib
> copying bleach/_vendor/html5lib/_inputstream.py -> 
> /<>/.pybuild/cpython3_3.9_bleach/build/bleach/_vendor/html5lib
> copying bleach/_vendor/html5lib/__init__.py -> 
> /<>/.pybuild/cpython3_3.9_bleach/build/bleach/_vendor/html5lib
> copying bleach/_vendor/html5lib/_utils.py -> 
> /<>/.pybuild/cpython3_3.9_bleach/build/bleach/_vendor/html5lib
> copying bleach/_vendor/html5lib/_tokenizer.py -> 
> /<>/.pybuild/cpython3_3.9_bleach/build/bleach/_vendor/html5lib
> copying bleach/_vendor/html5lib/constants.py -> 
> /<>/.pybuild/cpython3_3.9_bleach/build/bleach/_vendor/html5lib
> copying bleach/_vendor/html5lib/html5parser.py -> 
> /<>/.pybuild/cpython3_3.9_bleach/build/bleach/_vendor/html5lib
> copying bleach/_vendor/html5lib/serializer.py -> 
> /<>/.pybuild/cpython3_3.9_bleach/build/bleach/_vendor/html5lib
> copying bleach/_vendor/html5lib/_ihatexml.py -> 
> /<>/.pybuild/cpython3_3.9_bleach/build/bleach/_vendor/html5lib
> creating 
> /<>/.pybuild/cpython3_3.9_bleach/build/bleach/_vendor/html5lib/filters
> copying bleach/_vendor/html5lib/filters/lint.py -> 
> /<>/.pybuild/cpython3_3.9_bleach/build/bleach/_vendor/html5lib/filters
> copying bleach/_vendor/html5lib/filters/__init__.py -> 
> /<>/.pybuild/cpython3_3.9_bleach/build/bleach/_vendor/html5lib/filters
> copying bleach/_vendor/html5lib/filters/alphabeticalattributes.py -> 
> /<>/.pybuild/cpython3_3.9_bleach/build/bleach/_vendor/html5lib/filters
> copying bleach/_vendor/html5lib/filters/whitespace.py -> 
> /<>/.pybuild/cpython3_3.9_bleach/build/bleach/_vendor/html5lib/filters
> copying bleach/_vendor/html5lib/filters/inject_meta_charset.py -> 
> /<>/.pybuild/cpython3_3.9_bleach/build/bleach/_vendor/html5lib/filters
> copying bleach/_vendor/html5lib/filters/optionaltags.py -> 
> /<>/.pybuild/cpython3_3.9_bleach/build/bleach/_vendor/html5lib/filters
> copying bleach/_vendor/html5lib/filters/base.py -> 
> /<>/.pybuild/cpython3_3.9_bleach/build/bleach/_vendor/html5lib/filters
> copying bleach/_vendor/html5lib/filters/sanitizer.py -> 
> /<>/.pybuild/cpython3_3.9_bleach/build/bleach/_vendor/html5lib/filters
> creating 
> /<>/.pybuild/cpython3_3.9_bleach/build/bleach/_vendor/html5lib/treewalkers
> copying bleach/_vendor/html5lib/treewalkers/__init__.py -> 
> /<>/.pybuild/cpython3_3.9_bleach/build/bleach/_vendor/html5lib/treewalkers
> copying bleach/_vendor/html5lib/treewalkers/etree.py -> 
> /<>/.pybuild/cpython3_3.9_bleach/build/bleach/_vendor/html5lib/treewalkers
> copying bleach/_vendor/html5lib/treewalkers/genshi.py -> 
> /<>/.pybuild/cpython3_3.9_bleach/build/bleach/_vendor/html5lib/treewalkers
> copying bleach/_vendor/html5lib/treewalkers/etree_lxml.py -> 
> /<>/.pybuild/cpython3_3.9_bleach/build/bleach/_vendor/html5lib/treewalkers
> copying bleach/_vendor/html5lib/treewalkers/dom.py -> 
> /<>/.pybuild/cpython3_3.9_bleach/build/bleach/_vendor/html5lib/treewalkers
> copying 

Processed (with 1 error): Re: RFS closes some bugs in xdg-utils

[Debian Bug Tracking System]

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

> # fix the number of the main bug
> unblock 847164 by 964877
Bug #847164 [src:xdg-utils] Updating the xdg-utils Uploaders list
847164 was blocked by: 964877
847164 was not blocking any bugs.
Removed blocking bug(s) of 847164: 964877
> unblock 964877 by 964877
Bug #964877 [xdg-utils] xdg-email: open_generic code path doesn't handle 
Terminal=true
Failed to set blocking bugs of 964877: It is nonsensical for a bug to block 
itself (or a merged partner): 964877.

> unblock 970203 by 964877
Bug #970203 [xdg-utils] xdg-screensaver: does not work on windows with no title 
or non-ASCII title
970203 was blocked by: 964877
970203 was not blocking any bugs.
Removed blocking bug(s) of 970203: 964877
> unblock 975228 by 964877
Bug #975228 [src:xdg-utils] xdg-utils: FTBFS: tests failed
975228 was blocked by: 964877
975228 was not blocking any bugs.
Removed blocking bug(s) of 975228: 964877
> block 847164 by 980357
Bug #847164 [src:xdg-utils] Updating the xdg-utils Uploaders list
847164 was not blocked by any bugs.
847164 was not blocking any bugs.
Added blocking bug(s) of 847164: 980357
> block 964877 by 980357
Bug #964877 [xdg-utils] xdg-email: open_generic code path doesn't handle 
Terminal=true
964877 was not blocked by any bugs.
964877 was not blocking any bugs.
Added blocking bug(s) of 964877: 980357
> block 970203 by 980357
Bug #970203 [xdg-utils] xdg-screensaver: does not work on windows with no title 
or non-ASCII title
970203 was not blocked by any bugs.
970203 was not blocking any bugs.
Added blocking bug(s) of 970203: 980357
> block 975228 by 980357
Bug #975228 [src:xdg-utils] xdg-utils: FTBFS: tests failed
975228 was not blocked by any bugs.
975228 was not blocking any bugs.
Added blocking bug(s) of 975228: 980357
>
End of message, stopping processing here.

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

Processed (with 1 error): RFS closes some bugs in xdg-utils

[Debian Bug Tracking System]

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

> block 809877 by 980357
Bug #809877 [xdg-utils] xdg-utils: fix for #801048 breaks xdg-open if 
whitespaces in the filename on Debian/Cinnamon
809877 was not blocked by any bugs.
809877 was not blocking any bugs.
Added blocking bug(s) of 809877: 980357
> block 847164 by 964877
Bug #847164 [src:xdg-utils] Updating the xdg-utils Uploaders list
847164 was not blocked by any bugs.
847164 was not blocking any bugs.
Added blocking bug(s) of 847164: 964877
> block 964877 by 964877
Bug #964877 [xdg-utils] xdg-email: open_generic code path doesn't handle 
Terminal=true
Failed to set blocking bugs of 964877: It is nonsensical for a bug to block 
itself (or a merged partner): 964877.

> block 970203 by 964877
Bug #970203 [xdg-utils] xdg-screensaver: does not work on windows with no title 
or non-ASCII title
970203 was not blocked by any bugs.
970203 was not blocking any bugs.
Added blocking bug(s) of 970203: 964877
> block 975228 by 964877
Bug #975228 [src:xdg-utils] xdg-utils: FTBFS: tests failed
975228 was not blocked by any bugs.
975228 was not blocking any bugs.
Added blocking bug(s) of 975228: 964877
>
End of message, stopping processing here.

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

Bug#975228: bug marked as pending in xdg-utils

[Nicholas Guriev]

Control: tag -1 pending

Hello,

I made a fix of this bug by myself and committed it into the xdg-utils
repository and now it is awaiting an upload. You can check the diff at:


https://salsa.debian.org/freedesktop-team/xdg-utils/-/commit/628e0246c37260db118d71ffec47802f042b7773



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

Processed: bug marked as pending in xdg-utils

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #975228 [src:xdg-utils] xdg-utils: FTBFS: tests failed
Added tag(s) pending.

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

Bug#980050: marked as done (mdtraj: FTBFS with jupyter-client 6.1.11)

[Debian Bug Tracking System]

Your message dated Mon, 18 Jan 2021 06:04:45 +
with message-id 
and subject line Bug#980050: fixed in mdtraj 1.9.5-1
has caused the Debian Bug report #980050,
regarding mdtraj: FTBFS with jupyter-client 6.1.11
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.)


-- 
980050: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=980050
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: mdtraj
Severity: normal
Tags: ftbfs

Dear Maintainer,

mdtraj appears to FTBFS when trying to migrate jupyter-client 6.1.6 ->
6.1.11

The failure is trying to build the example notebook examples/nmr.ipynb;
it appears to fail trying to find an external dependency (sparta) which
as far as I can tell was never installed for autopkgtests. I'm not quite
sure why this regression is visible at this point, since I can't see why
this test would have succeeded before. Presumably a change in jupyter
client affected the custom notebook executor in the testsuite.

see https://ci.debian.net/data/autopkgtest/testing/amd64/m/mdtraj/9644331/log.gz

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

Kernel: Linux 5.10.0-1-amd64 (SMP w/1 CPU thread)
Kernel taint flags: TAINT_WARN
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
--- End Message ---
--- Begin Message ---
Source: mdtraj
Source-Version: 1.9.5-1
Done: Drew Parsons 

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

Debian distribution maintenance software
pp.
Drew Parsons  (supplier of updated mdtraj package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 18 Jan 2021 16:30:54 +1100
Source: mdtraj
Architecture: source
Version: 1.9.5-1
Distribution: unstable
Urgency: medium
Maintainer: Debichem Team 
Changed-By: Drew Parsons 
Closes: 980050
Changes:
 mdtraj (1.9.5-1) unstable; urgency=medium
 .
   * New upstream release.
   * Standards-Version: 4.5.1
   * debian/tests: skip nmr.ipynb, it requires SPARTA+ which is not
 available. Closes: #980050.
Checksums-Sha1:
 1e432fb2668a9e04cb1ea0f75dd8f9d551b02158 2592 mdtraj_1.9.5-1.dsc
 7db579a63370fc047be4b3ffa4f2d7e74cb3a27f 21487803 mdtraj_1.9.5.orig.tar.gz
 88c8d5fc681a4c509bf82d260c6544da5f68c5dc 295596 mdtraj_1.9.5-1.debian.tar.xz
Checksums-Sha256:
 3d06a1b3bcfaad7423e6d173fcd2187b1eb68cd50a809eeb8887653d4f25 2592 
mdtraj_1.9.5-1.dsc
 ed2a72b85e765024f8d533da26dad026944d0e385b04af7b66572f676ef92040 21487803 
mdtraj_1.9.5.orig.tar.gz
 df92f102aa175ce4ba689f4486d7c8fb15e46e3efed8ae2b436351df1854ac2e 295596 
mdtraj_1.9.5-1.debian.tar.xz
Files:
 7fce3709e374388514a4e55d914afce1 2592 python optional mdtraj_1.9.5-1.dsc
 74ffbce786aa7524e99bee9d95462701 21487803 python optional 
mdtraj_1.9.5.orig.tar.gz
 ed728d470689c78f5f7013453cf31451 295596 python optional 
mdtraj_1.9.5-1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEI8mpPlhYGekSbQo2Vz7x5L1aAfoFAmAFIaUACgkQVz7x5L1a
Afqjzg/+N6GhRpijUb6ZEWl5ci2HYS1guE+NMX2uKzoWRKWBRgu6GQvWbb1Mcwsx
KTAfzI+Yjfwjvzx700wBhs9AzCV431SPkPEvtIxAV5HWlcVKPOe2BbGIt3y/Yqld
DaEOTGhr8BWdreq2woRNyjBuWeNDqTnNZURflJht5l0u3VxgkNz1WwefdDzIWnQ4
Lo+dbWPNJeFWN0/70b2SWvFjC5mjBDknBRfexQUXYTeBb5TSNCwat4S6xbKqHWn3
taLwQ2Y+O5gh64IbYjdsRNdeVejEVQTz52C5zO0qkpjsE19oAWXUmMlxyVkyng4N
Fxh0r8zJ6trGxBmyK1Jp4mMHR8umG5mdrybCy3u4UWtJZEsD4y0SHMVyezN32JUO
wExOVAJELfQahLGkQ5ENzSL67z8o2vmbiDw+wzR09W9YY1d0iFqTgMd7BPcNVwZu
WIpBE0D3jcnumGCX+DB5mhCwEJHDtS8a1M16YmdR93WUmvKApy/+pXgCa9yIkWTA
N0pgONPyhRpPGVga0H2w4K7IR6m4/ZMiGxpWX+YrBEUa5UNDNN7GYtvwzQfXIJRv
lf3p15VkVB6H/1NAI1cy5jPm11Jiwv8RWjlQV13HPOz/WnoyvEASJksTUZIicOrc
m5k3lb1WHv5qi35pZhICprg3/LGyDoAwuE/8jYJjj6NpO0y+tgk=
=omz1
-END PGP SIGNATURE End Message ---

Bug#971040: marked as done (gnome-shell-extension-easyscreencast: please test with GNOME Shell 3.38 and update dependency)

[Debian Bug Tracking System]

Your message dated Mon, 18 Jan 2021 04:33:57 +
with message-id 
and subject line Bug#971040: fixed in gnome-shell-extension-easyscreencast 
1.1.0+git20210116.3252312-1
has caused the Debian Bug report #971040,
regarding gnome-shell-extension-easyscreencast: please test with GNOME Shell 
3.38 and update dependency
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.)


-- 
971040: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=971040
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gnome-shell-extension-easyscreencast
Version: 1.1.0-2
Severity: grave
Justification: renders package unusable
Control: block 969321 by -1

GNOME Shell 3.38 is on its way into unstable, which makes
gnome-shell-extension-easyscreencast uninstallable. Please test with GNOME
Shell 3.38, and if possible upload a version that is compatible.

If it isn't possible to make this extension compatible, then this
extension will need to be removed from testing to let the new GNOME
release migrate.

A new version 1.2.0 seems to be available upstream. I don't know whether
it will work with 3.38, but it seems more likely than 1.1.0.

Thanks,
smcv
--- End Message ---
--- Begin Message ---
Source: gnome-shell-extension-easyscreencast
Source-Version: 1.1.0+git20210116.3252312-1
Done: Samuel Henrique 

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

Debian distribution maintenance software
pp.
Samuel Henrique  (supplier of updated 
gnome-shell-extension-easyscreencast package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 18 Jan 2021 04:16:39 +
Source: gnome-shell-extension-easyscreencast
Architecture: source
Version: 1.1.0+git20210116.3252312-1
Distribution: unstable
Urgency: medium
Maintainer: Debian GNOME Maintainers 

Changed-By: Samuel Henrique 
Closes: 971040
Changes:
 gnome-shell-extension-easyscreencast (1.1.0+git20210116.3252312-1) unstable; 
urgency=medium
 .
   * New upstream version 1.1.0+git20210116.3252312
   * Bump DH to 13
   * Bump Standards-Version to 4.5.1
   * Add support for Gnome 3.38 with patch submitted on Github (closes: #971040)
 Thanks to Ian2020 for the patch and Bruno Kleinert 
 for the help.
   * d/p/makefile.patch: Add Forwarded field with 'not-needed' value
Checksums-Sha1:
 69a5f7249735c37b1f2605194fa0ef5174aacdff 2496 
gnome-shell-extension-easyscreencast_1.1.0+git20210116.3252312-1.dsc
 5ce50efb281ddf9bf44962b95af22d88bc38c59b 223688 
gnome-shell-extension-easyscreencast_1.1.0+git20210116.3252312.orig.tar.xz
 548e88194e22dbbac6a648d6f41d7605a772114b 6852 
gnome-shell-extension-easyscreencast_1.1.0+git20210116.3252312-1.debian.tar.xz
 9a74e758a109b186500ffdad661c060606d35089 6323 
gnome-shell-extension-easyscreencast_1.1.0+git20210116.3252312-1_amd64.buildinfo
Checksums-Sha256:
 177a8b3b9c1bc44cc0edbc4d255bd20bb11be72ea56475a3012ca3a14a07a995 2496 
gnome-shell-extension-easyscreencast_1.1.0+git20210116.3252312-1.dsc
 cd416dfeea0ca9b48cb9c708914b45a07b7db25593fb14124f7a97d0403206e6 223688 
gnome-shell-extension-easyscreencast_1.1.0+git20210116.3252312.orig.tar.xz
 935014ca995b7dfc13f8af723d903b4b64d645b9af7fbd8c6ba73b7f72a54de7 6852 
gnome-shell-extension-easyscreencast_1.1.0+git20210116.3252312-1.debian.tar.xz
 2d849bded457bc9dd73afb2ef2001247ef334d4c67ee6e43918e702debcf 6323 
gnome-shell-extension-easyscreencast_1.1.0+git20210116.3252312-1_amd64.buildinfo
Files:
 96a9d6a3aba55eb86138efe9b89e2033 2496 gnome optional 
gnome-shell-extension-easyscreencast_1.1.0+git20210116.3252312-1.dsc
 26f1e2fd6324e259ecdb80f38e371146 223688 gnome optional 
gnome-shell-extension-easyscreencast_1.1.0+git20210116.3252312.orig.tar.xz
 aca6752aba5d5f6375f1dc176c07ec88 6852 gnome optional 
gnome-shell-extension-easyscreencast_1.1.0+git20210116.3252312-1.debian.tar.xz
 825be81ca18d716f94bfd4c5db03f539 6323 gnome optional 
gnome-shell-extension-easyscreencast_1.1.0+git20210116.3252312-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

Bug#979534: wolfssl: CVE-2020-36177

[Felix Lechner]

Hi,

On Thu, Jan 7, 2021 at 12:12 PM Salvatore Bonaccorso  wrote:
>
> CVE-2020-36177[0]:

This vulnerability will be fixed in the next couple of days via upload
of version 4.6.0 to unstable. A backport of the fix is not possible
(freeze notwithstanding). Also, the patches from #978676 do not apply,
or apply only partially, because we are changing the way the sources
are repackaged.

Kind regards
Felix Lechner

Processed: tagging 976401

[Debian Bug Tracking System]

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

> tags 976401 + pending
Bug #976401 [src:uftp] uftp: autopkgtest regression in testing: rm: cannot 
remove '/tmp/uftp-test-data': Operation not permitted
Added tag(s) pending.
> thanks
Stopping processing here.

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

Processed: Re: gringotts: ftbfs with GCC-10

[Debian Bug Tracking System]

Processing control commands:

> tags -1 patch
Bug #957312 [src:gringotts] gringotts: ftbfs with GCC-10
Added tag(s) patch.

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

Bug#957312: gringotts: ftbfs with GCC-10

[Logan Rosen]

Package: gringotts
Version: 1.2.10-3
Followup-For: Bug #957312
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu hirsute ubuntu-patch
Control: tags -1 patch

Hi,

In Ubuntu, the attached patch was applied to achieve the following:

  * d/p/fix-build-with-gcc10.patch: Cherrypick/modify upstream Git commit to
fix FTBFS with GCC 10.

Thanks for considering the patch.

Logan
diff -Nru gringotts-1.2.10/debian/patches/fix-build-with-gcc-10.patch 
gringotts-1.2.10/debian/patches/fix-build-with-gcc-10.patch
--- gringotts-1.2.10/debian/patches/fix-build-with-gcc-10.patch 1969-12-31 
19:00:00.0 -0500
+++ gringotts-1.2.10/debian/patches/fix-build-with-gcc-10.patch 2021-01-17 
22:14:40.0 -0500
@@ -0,0 +1,225 @@
+From dfeb8b6a4b2fdc9ba61ed64a72a73c44cc5a9faf Mon Sep 17 00:00:00 2001
+From: Shlomi Fish 
+Date: Tue, 26 May 2020 12:23:14 +0300
+Subject: [PATCH] extern decls fix for recent gcc.
+
+---
+ src/grg_attachs.h|  2 +-
+ src/grg_entries.h|  2 +-
+ src/grg_menus.c  | 15 +++
+ src/grg_menus.h  | 14 +++---
+ src/grg_pix.h| 14 +++---
+ src/grg_prefs.h  | 36 ++--
+ src/grg_recent_dox.h |  8 
+ src/grg_widgets.h|  2 +-
+ src/gringotts.h  |  6 +++---
+ 10 files changed, 58 insertions(+), 42 deletions(-)
+
+diff --git a/src/grg_attachs.h b/src/grg_attachs.h
+index d8df7ac..1442ff9 100644
+--- a/src/grg_attachs.h
 b/src/grg_attachs.h
+@@ -24,7 +24,7 @@
+ 
+ #include 
+ 
+-gint current_attach_ID;
++extern gint current_attach_ID;
+ 
+ gint grg_attach_file (gchar * path, GtkWidget * parent);
+ void grg_remove_attachment (void);
+diff --git a/src/grg_entries.h b/src/grg_entries.h
+index 63102d3..dc3872a 100644
+--- a/src/grg_entries.h
 b/src/grg_entries.h
+@@ -24,7 +24,7 @@
+ 
+ /* current element. */
+ /* MUST BE USED ONLY BY grg_attachs.h  */
+-GList *current;
++extern GList *current;
+ 
+ /* Appends a new entry to the list */
+ void grg_entries_append (void);
+diff --git a/src/grg_menus.c b/src/grg_menus.c
+index f952e2a..50163a1 100644
+--- a/src/grg_menus.c
 b/src/grg_menus.c
+@@ -31,6 +31,21 @@
+ 
+ #include 
+ 
++/* menu File */
++GtkWidget *bnew, *bopen, *bsave, *bsas, *brev, *bclose, *bquit;
++
++/* menu Edit */
++GtkWidget *badd, *brem, *bcut, *bcop, *bpaste, *bfind, *bfinda, *bpwd, *bpref;
++
++/* menu Navigation */
++GtkWidget *bmfirst, *bmback, *bmfor, *bmlast, *bmind;
++
++/* menu Tools */
++GtkWidget *bwipe;
++
++/* menu Help */
++GtkWidget *babo;
++
+ #define NEW_MENU_ITEM(var, text, cb, data, parent, img, key, mod) \
+   var = gtk_image_menu_item_new_with_mnemonic(text); \
+   gtk_menu_shell_append (GTK_MENU_SHELL (parent), var); \
+diff --git a/src/grg_menus.h b/src/grg_menus.h
+index 47e5088..eb1ca45 100644
+--- a/src/grg_menus.h
 b/src/grg_menus.h
+@@ -25,22 +25,22 @@
+ #include 
+ 
+ /* menu File */
+-GtkWidget *bnew, *bopen, *bsave, *bsas, *brev, *bclose, *bquit;
++extern GtkWidget *bnew, *bopen, *bsave, *bsas, *brev, *bclose, *bquit;
+ 
+ /* menu Edit */
+-GtkWidget *badd, *brem, *bcut, *bcop, *bpaste, *bfind, *bfinda, *bpwd, *bpref;
++extern GtkWidget *badd, *brem, *bcut, *bcop, *bpaste, *bfind, *bfinda, *bpwd, 
*bpref;
+ 
+ /* menu Navigation */
+-GtkWidget *bmfirst, *bmback, *bmfor, *bmlast, *bmind;
++extern GtkWidget *bmfirst, *bmback, *bmfor, *bmlast, *bmind;
+ 
+ /* menu Tools */
+-GtkWidget *bwipe;
++extern GtkWidget *bwipe;
+ 
+ /* menu Help */
+-GtkWidget *babo;
++extern GtkWidget *babo;
+ 
+ /*Makes a menubar, within a handlebox, and returns the GtkWidget */
+-GtkWidget *grg_menu_create (GtkWidget * window);
++extern GtkWidget *grg_menu_create (GtkWidget * window);
+ 
+-void grg_menu_update (void);
++extern void grg_menu_update (void);
+ #endif
+diff --git a/src/grg_pix.h b/src/grg_pix.h
+index bbb92b2..23937b6 100644
+--- a/src/grg_pix.h
 b/src/grg_pix.h
+@@ -22,13 +22,13 @@
+ #ifndef GRG_PIX_H
+ #define GRG_PIX_H
+ 
+-const char *red_xpm[58];
+-const char *yellow_xpm[58];
+-const char *green_xpm[58];
+-const char *optimal_xpm[94];
++extern const char *red_xpm[58];
++extern const char *yellow_xpm[58];
++extern const char *green_xpm[58];
++extern const char *optimal_xpm[94];
+ 
+-const char *splash_xpm[180];
++extern const char *splash_xpm[180];
+ 
+-const char *wait_xpm[82];
+-const char *clip_xpm[17];
++extern const char *wait_xpm[82];
++extern const char *clip_xpm[17];
+ #endif
+diff --git a/src/grg_prefs.h b/src/grg_prefs.h
+index 7510633..cf37ced 100644
+--- a/src/grg_prefs.h
 b/src/grg_prefs.h
+@@ -24,24 +24,24 @@
+ 
+ #include 
+ 
+-gboolean grg_prefs_warn4overwrite;
+-gboolean grg_prefs_bak_files;
+-gboolean grg_prefs_splash;
+-gboolean grg_prefs_tray;
+-gboolean grg_prefs_clip_clear_on_close;
+-gboolean grg_prefs_clip_clear_on_quit;
+-gint grg_prefs_xpire;
+-gint grg_prefs_wipe_passes;
+-gint grg_prefs_mainwin_width, grg_prefs_mainwin_height;
++extern gboolean grg_prefs_warn4overwrite;
++extern gboolean 

Processed: Re: hdate-applet FTBFS with gcc-10

[Debian Bug Tracking System]

Processing control commands:

> tags -1 patch
Bug #968131 [src:hdate-applet] hdate-applet FTBFS with gcc-10
Added tag(s) patch.

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

Bug#968131: hdate-applet FTBFS with gcc-10

[Logan Rosen]

Package: hdate-applet
Version: 0.15.11-3
Followup-For: Bug #968131
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu hirsute ubuntu-patch
Control: tags -1 patch

Hi,

In Ubuntu, the attached patch was applied to achieve the following:

  * d/p/gcc-10: Fix FTBFS with GCC 10 due to multiple definitions.

Thanks for considering the patch.

Logan
diff -Nru hdate-applet-0.15.11/debian/patches/gcc-10 
hdate-applet-0.15.11/debian/patches/gcc-10
--- hdate-applet-0.15.11/debian/patches/gcc-10  1969-12-31 19:00:00.0 
-0500
+++ hdate-applet-0.15.11/debian/patches/gcc-10  2021-01-17 22:00:18.0 
-0500
@@ -0,0 +1,51 @@
+--- a/src/ghcal-interface.c
 b/src/ghcal-interface.c
+@@ -33,6 +33,18 @@
+ #include "ghcal-callbacks.h"
+ #include "ghcal-interface.h"
+ 
++hdate_struct today;
++GtkWidget *label_month;
++GtkWidget *label_year;
++GtkWidget *combobox_month;
++GtkWidget *spinbutton_year;
++GtkWidget *label_hebrew_month_and_year;
++int index_day_of_month[42];
++hdate_struct hdate_day_of_month[42];
++GtkWidget *label_day_of_month[42];
++GtkWidget *event_box_day_of_month[42];
++GtkTooltips *tooltip_day_of_month[42];
++
+ GtkWidget *
+ create_window (void)
+ {
+--- a/src/ghcal-interface.h
 b/src/ghcal-interface.h
+@@ -42,16 +42,16 @@
+ #  define N_(String) (String)
+ #endif
+ 
+-hdate_struct today;
+-GtkWidget *label_month;
+-GtkWidget *label_year;
+-GtkWidget *combobox_month;
+-GtkWidget *spinbutton_year;
+-GtkWidget *label_hebrew_month_and_year;
+-int index_day_of_month[42];
+-hdate_struct hdate_day_of_month[42];
+-GtkWidget *label_day_of_month[42];
+-GtkWidget *event_box_day_of_month[42];
+-GtkTooltips *tooltip_day_of_month[42];
++extern hdate_struct today;
++extern GtkWidget *label_month;
++extern GtkWidget *label_year;
++extern GtkWidget *combobox_month;
++extern GtkWidget *spinbutton_year;
++extern GtkWidget *label_hebrew_month_and_year;
++extern int index_day_of_month[42];
++extern hdate_struct hdate_day_of_month[42];
++extern GtkWidget *label_day_of_month[42];
++extern GtkWidget *event_box_day_of_month[42];
++extern GtkTooltips *tooltip_day_of_month[42];
+ 
+ GtkWidget *create_window (void);
diff -Nru hdate-applet-0.15.11/debian/patches/series 
hdate-applet-0.15.11/debian/patches/series
--- hdate-applet-0.15.11/debian/patches/series  2018-07-30 02:28:28.0 
-0400
+++ hdate-applet-0.15.11/debian/patches/series  2021-01-17 21:58:42.0 
-0500
@@ -3,3 +3,4 @@
 swedish-translation
 use-locale
 no-bonobo.patch
+gcc-10

Bug#980341: Remove this package from testing/next Debian

[William Desportes]

Package: dasprid-enum
Severity: serious

[ Filed by the maintainer to see the package removed from testing. ]

Hi,

This package is not used by anyone one at Debian, it can be removed for the 
next release and will be used afterwards.
Yes, baconqrcode depends on it and a bug is filed to also remove it.

Regards,
William Desportes

Bug#980342: Remove this package from testing/next Debian

[William Desportes]

Package: baconqrcode
Severity: serious

[ Filed by the maintainer to see the package removed from testing. ]

Hi,

This package is not used by anyone one at Debian, it can be removed for the 
next release and will be used afterwards.

Regards,
William Desportes

Processed: unarchiving 821656, reopening 821656

[Debian Bug Tracking System]

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

> # src:shaarli was reintroduced: 
> https://lists.debian.org/msgid-search/546c2c3d77eaef6dc2b26c7ed7663f16df847bda.ca...@debian.org
> unarchive 821656
Bug #821656 {Done: Debian FTP Masters } 
[shaarli] shaarli: PHP 7.0 Transition
Unarchived Bug 821656
> reopen 821656
Bug #821656 {Done: Debian FTP Masters } 
[shaarli] shaarli: PHP 7.0 Transition
'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 0.0.42~beta~dfsg1-2+rm.
> thanks
Stopping processing here.

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

Processed: closing 821656

[Debian Bug Tracking System]

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

> close 821656 0.12.0+dfsg-2
Bug #821656 [shaarli] shaarli: PHP 7.0 Transition
Marked as fixed in versions shaarli/0.12.0+dfsg-2.
Bug #821656 [shaarli] shaarli: PHP 7.0 Transition
Marked Bug as done
> thanks
Stopping processing here.

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

Bug#976935: marked as done (inkscape: FTBFS on ppc64el: make[3]: *** No rule to make target 'po/zh_TW.gmo', needed by 'share/templates/default_templates.timestamp'. Stop.)

[Debian Bug Tracking System]

Your message dated Mon, 18 Jan 2021 01:18:44 +
with message-id 
and subject line Bug#976935: fixed in inkscape 1.0.2-1
has caused the Debian Bug report #976935,
regarding inkscape: FTBFS on ppc64el: make[3]: *** No rule to make target 
'po/zh_TW.gmo', needed by 'share/templates/default_templates.timestamp'. Stop.
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.)


-- 
976935: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976935
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: inkscape
Version: 1.0.1-2
Severity: serious
Justification: FTBFS on ppc64el
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201209 ftbfs-bullseye ftbfs-ppc64el

Hi,

During a rebuild of all packages in sid, your package failed to build
on ppc64el. At the same time, it did not fail on amd64.

I'm marking this bug as severity:serious since your package currently has
ppc64el binary packages in unstable (so this is a regression).

Relevant part (hopefully):
> make[3]: Entering directory '/<>/obj-powerpc64le-linux-gnu'
> make[3]: Nothing to be done for 
> 'share/templates/CMakeFiles/templates_h.dir/build'.
> make[3]: Leaving directory '/<>/obj-powerpc64le-linux-gnu'
> make[3]: Leaving directory '/<>/obj-powerpc64le-linux-gnu'
> make  -f share/templates/CMakeFiles/default_templates.dir/build.make 
> share/templates/CMakeFiles/default_templates.dir/build
> cd /<>/obj-powerpc64le-linux-gnu/man && /usr/bin/pod2man --utf8 
> --section="1" --center="Inkscape\ Commands\ Manual" --release="1.0.1" 
> --name="INKSCAPE" /<>/obj-powerpc64le-linux-gnu/man/inkscape.pod 
> /<>/obj-powerpc64le-linux-gnu/man/inkscape.tmp
> cd /<>/obj-powerpc64le-linux-gnu/src/extension/dbus && 
> dbus-binding-tool --mode=glib-server 
> --output=/<>/obj-powerpc64le-linux-gnu/src/extension/dbus/document-server-glue.h
>  --prefix=document_interface 
> /<>/src/extension/dbus/document-interface.xml
> make[3]: Entering directory '/<>/obj-powerpc64le-linux-gnu'
> make[3]: *** No rule to make target 'po/zh_TW.gmo', needed by 
> 'share/templates/default_templates.timestamp'.  Stop.
> make[3]: Leaving directory '/<>/obj-powerpc64le-linux-gnu'
> make[2]: *** [CMakeFiles/Makefile2:6529: 
> share/templates/CMakeFiles/default_templates.dir/all] Error 2

The full build log is available from:
   http://qa-logs.debian.net/2020/12/09/inkscape_1.0.1-2_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 me
so that we can identify if something relevant changed in the meantime.

About the archive rebuild: The rebuild was done on a Power8 cluster part of the
Grid'5000 testbed. Hardware specs: 
https://www.grid5000.fr/w/Grenoble:Hardware#drac
--- End Message ---
--- Begin Message ---
Source: inkscape
Source-Version: 1.0.2-1
Done: Mattia Rizzolo 

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

Debian distribution maintenance software
pp.
Mattia Rizzolo  (supplier of updated inkscape package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 18 Jan 2021 00:40:50 +0100
Source: inkscape
Architecture: source
Version: 1.0.2-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Multimedia Maintainers 
Changed-By: Mattia Rizzolo 
Closes: 976935
Changes:
 inkscape (1.0.2-1) unstable; urgency=medium
 .
   * New upstream version 1.0.2.
 https://wiki.inkscape.org/wiki/index.php/Release_notes/1.0.2
 https://inkscape.org/release/inkscape-1.0.2/
 https://inkscape.org/news/2021/01/17/102-and-11alpha/
   * Drop patches applied upstream.
   * Switch build system from cmake+make to cmake+ninja.
 + Fixes FTBFS with a very high level of parallelism.  Closes: #976935
Checksums-Sha1:
 701c7698e3d3aecaa194f1c1aea700575007d805 2895 inkscape_1.0.2-1.dsc
 

Bug#938509: Intent to request the removal from Debian

[Markus Koschany]

Hi,

thanks for the patch. I have pushed your changes to 

https://salsa.debian.org/games-team/snowballz/-/tree/experimental


However I can't build the package as is. The build system seems to require
python-distutils instead of pybuild and all the dependencies haven't been
updated yet.

Regards,

Markus


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

Processed: Bug#938509 marked as pending in snowballz

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #938509 [src:snowballz] snowballz: Python2 removal in sid/bullseye
Added tag(s) pending.

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

Bug#938509: marked as pending in snowballz

[Markus Koschany]

Control: tag -1 pending

Hello,

Bug #938509 in snowballz reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:

https://salsa.debian.org/games-team/snowballz/-/commit/fc50641b8fb2245f4d5d804dc7c72b90d192cc7b


Port snowballz to Python 3.

Closes: #938509,#912492


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/938509

Bug#980050: (no subject)

[Gordon Ball]

A sufficient patch is

```
diff --git a/debian/tests/control b/debian/tests/control
index bc03117..d765359 100644
--- a/debian/tests/control
+++ b/debian/tests/control
@@ -1,4 +1,4 @@
-Test-Command: pytest-3
+Test-Command: pytest-3 -k 'not nmr.ipynb'
 Depends: python3-mdtraj,
   python3-ipykernel,
   python3-jupyter-client,
```

Processed: Re: jabber-muc: ftbfs with GCC-10

[Debian Bug Tracking System]

Processing control commands:

> tags -1 patch
Bug #957384 [src:jabber-muc] jabber-muc: ftbfs with GCC-10
Added tag(s) patch.

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

Bug#957384: jabber-muc: ftbfs with GCC-10

[Logan Rosen]

Package: jabber-muc
Version: 0.8-7
Followup-For: Bug #957384
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu hirsute ubuntu-patch
Control: tags -1 patch

Hi,

In Ubuntu, the attached patch was applied to achieve the following:

  * d/p/gcc_10.diff: Fix FTBFS with GCC 10 due to multiple definitions.

Thanks for considering the patch.

Logan
diff -Nru jabber-muc-0.8/debian/patches/gcc_10.diff 
jabber-muc-0.8/debian/patches/gcc_10.diff
--- jabber-muc-0.8/debian/patches/gcc_10.diff   1969-12-31 19:00:00.0 
-0500
+++ jabber-muc-0.8/debian/patches/gcc_10.diff   2021-01-17 18:13:34.0 
-0500
@@ -0,0 +1,51 @@
+--- a/include/jcomp-compat.h
 b/include/jcomp-compat.h
+@@ -66,6 +66,6 @@
+ handel hds;
+ };
+ 
+-int deliver__flag;
++extern int deliver__flag;
+ 
+ typedef void(*shutdown_func)(void *arg);
+--- a/src/conference_user.c
 b/src/conference_user.c
+@@ -19,7 +19,7 @@
+  */
+ 
+ #include "conference.h"
+-extern int deliver__flag;
++int deliver__flag;
+ 
+ cnu con_user_new(cnr room, jid id)
+ {
+--- a/include/jcomp.h
 b/include/jcomp.h
+@@ -98,7 +98,7 @@
+ #define _STREAM_ERROR4
+ #define _STREAM_SHUTDOWN   5
+ 
+-jcr_instance jcr;
++extern jcr_instance jcr;
+ 
+ void log_debug(char *, const char *, ...) G_GNUC_PRINTF(2, 3);
+ void log_warn(char *, const char *, ...) G_GNUC_PRINTF(2, 3);
+--- a/src/conference.c
 b/src/conference.c
+@@ -20,6 +20,8 @@
+ 
+ #include "conference.h"
+ 
++jcr_instance jcr;
++
+ void con_server_browsewalk(gpointer key, gpointer data, gpointer arg)
+ {
+   cnr room = (cnr)data;
+@@ -1064,7 +1066,6 @@
+ /*** everything starts here ***/
+ void conference(instance i, xmlnode x)
+ {
+-  extern jcr_instance jcr;
+   cni master;
+   xmlnode cfg;
+   jid sadmin;
diff -Nru jabber-muc-0.8/debian/patches/series 
jabber-muc-0.8/debian/patches/series
--- jabber-muc-0.8/debian/patches/series2019-05-12 04:13:37.0 
-0400
+++ jabber-muc-0.8/debian/patches/series2021-01-17 18:09:44.0 
-0500
@@ -1,2 +1,3 @@
 cflags_hardening.diff
 cross.diff
+gcc_10.diff

Bug#955488: marked as done (nat-rtsp-dkms: Does not build with kernel >= 5.3)

[Debian Bug Tracking System]

Your message dated Sun, 17 Jan 2021 23:05:22 +
with message-id 
and subject line Bug#955488: fixed in nat-rtsp 0.7+5.3-0.1
has caused the Debian Bug report #955488,
regarding nat-rtsp-dkms: Does not build with kernel >= 5.3
to be marked as done.

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

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


-- 
955488: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=955488
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: nat-rtsp-dkms
Version: 0.7+4.18-0.1
Severity: grave
Justification: renders package unusable

Hi,

There is a new package on upstream, that should fix this.

However, it renders the package unusable with current kernel.

Thanks for this package,

Adrien

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

Kernel: Linux 5.4.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8),
LANGUAGE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages nat-rtsp-dkms depends on:
ii  dkms  2.8.1-5

nat-rtsp-dkms recommends no packages.

nat-rtsp-dkms suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: nat-rtsp
Source-Version: 0.7+5.3-0.1
Done: Chris Hofstaedtler 

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

Debian distribution maintenance software
pp.
Chris Hofstaedtler  (supplier of updated nat-rtsp package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 17 Jan 2021 22:31:56 +
Source: nat-rtsp
Architecture: source
Version: 0.7+5.3-0.1
Distribution: unstable
Urgency: medium
Maintainer: Julien Muchembled 
Changed-By: Chris Hofstaedtler 
Closes: 955488
Changes:
 nat-rtsp (0.7+5.3-0.1) unstable; urgency=medium
 .
   * Non-maintainer upload
   * New upstream release:
 - Add support for linux 5.3 (Closes: #955488)
Checksums-Sha1:
 9be3dc4ecf2417eec4989ffcdc1691de35064686 1751 nat-rtsp_0.7+5.3-0.1.dsc
 7cd871cdf26d7010b68f162c736d4f4921b2b0cd 11624 nat-rtsp_0.7+5.3.orig.tar.xz
 89414963f7d1bbf683089a3ad07f93e346b5911d 3064 
nat-rtsp_0.7+5.3-0.1.debian.tar.xz
 445e3ecea260a8711e2129d5ea6e4f6ec665a0e7 6225 
nat-rtsp_0.7+5.3-0.1_source.buildinfo
Checksums-Sha256:
 3c8f6e6fd99347dd6298b052f82a9e9e277cb146b1c9915eb2959268811c973f 1751 
nat-rtsp_0.7+5.3-0.1.dsc
 b13e4c5bd9a25c0a2463c3a5823807d9a93059deacdb25f8f04bc1ddf79dbd0a 11624 
nat-rtsp_0.7+5.3.orig.tar.xz
 7a0a9b22219c997a3e184e41869c551eef5f7fd6a5a1411351368ba84988b14a 3064 
nat-rtsp_0.7+5.3-0.1.debian.tar.xz
 efd3c33a75227fe734ef4f752b21576af78cb103a7e9968bfdca441aac841ce7 6225 
nat-rtsp_0.7+5.3-0.1_source.buildinfo
Files:
 904250ccc8790d7f75bf6e921e450fd2 1751 kernel optional nat-rtsp_0.7+5.3-0.1.dsc
 62addaca1065f79206566a8ab1cc7cbf 11624 kernel optional 
nat-rtsp_0.7+5.3.orig.tar.xz
 68932cd3ede2015b18eb1f5a0f132607 3064 kernel optional 
nat-rtsp_0.7+5.3-0.1.debian.tar.xz
 81e5e0491a33e813b3f2b5eb8f6aa888 6225 kernel optional 
nat-rtsp_0.7+5.3-0.1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEfRrP+tnggGycTNOSXBPW25MFLgMFAmAEvOUACgkQXBPW25MF
LgO3BQ//aVTuh8tMg6Wq8YiTYYzDcJHssAoK1xaSUF5znjCS8+wLK0BjVRYO0c4b
/q9dLUViMIN3cIUk7AQAHaD3mZekTgz3pSiQAz6juP+0C+kO7WwcRpQHfiSM20pb
B4hZTLd7+r9OYOrIRrmrhZm13cusnbkxoQFXXPDO2sCm7DLhVf6FFd/Lwi1dLaWJ
/VlNZizKCeGMtEH6BRd3plDZ2eRQ/h7Sd8uv4cZDOmSgiPkAqpQYTnsTVw/xiCfl
ib/rVo8sKDpRx+z/NT6abUn0yFlV+1UuYbSgBmEGTO/VRI8iCfTn8Xmq2vt3ai2G
S3FDws67Dz5cb5x6figvtuQCVEvvJEoya/7JB3ZFxOXcFwHQvHHZOHfCr04Z3EqJ
ewOcx6nUkBzVap4uO2rFbEvnm2cnC/z978P/2z91f7Yfnj46mdzkHFSn/jg35JN6
5+YxC+9YtebmVG7DqSO3jFa68JaFDx5nqxv7ni1oSn3PZYOqWAQM8VOO8+JK6cm0
nqoFdY0BGIAGpdJuqZKnmbwJ+7QXlU6/DvP57rA0vzNxqaUnlZk0nXOcoGE2e2ey
iDBdVX/3BdqBYm3/qeDbogYDWgdaNqGoh+OEC+Pi+Nz7MnngUC7I2TSQjwaRAitX
r8D+hOd6otSONZcLMizoedmlcYyNb9SgsjewiZADn03Moc0qqvc=
=6EC5
-END PGP SIGNATURE End Message ---

Bug#980292: workaround

[Tupshin Harper]

The following appears to be a sufficient workaround to make freecad work
for me with unstable:

 sudo ln -s ../../share/freecad/3Dconnexion/ ../../share/freecad/Ext/
../../share/freecad/Mod/ ./

Bug#957839: sptk: ftbfs with GCC-10

[Giulio Paci]

Hi Logan,
   thank you for this patch.

I have included it in the Debian package (I just opened RFS) as well
and submitted upstream.

Cheers,
Giulio

On Sun, Jan 10, 2021 at 12:36 AM Logan Rosen  wrote:
>
> Package: sptk
> Version: 3.9-2
> Followup-For: Bug #957839
> User: ubuntu-de...@lists.ubuntu.com
> Usertags: origin-ubuntu hirsute ubuntu-patch
> X-Debbugs-Cc: lo...@ubuntu.com
> Control: tags -1 patch
>
> Hi,
>
> In Ubuntu, the attached patch was applied to achieve the following:
>
>   * d/p/gcc-10.patch: Fix compilation with GCC 10.
>
> Thanks for considering the patch.
>
> Logan

Bug#966714: guile-gnutls: FTBFS against guile 3.0.4-1+b1

[Juhani Numminen]

Control: fixed -1 3.7.0-1

Right now the bug system still thinks this bug applies to sid and
bullseye but currently guile-gnutls does not use guile 3.0.
(https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964284#19)


Juhani

Bug#979502: marked as done (src:liblingua-en-namecase-perl: invalid maintainer address)

[Debian Bug Tracking System]

Your message dated Sun, 17 Jan 2021 21:23:44 +
with message-id 
and subject line Bug#979502: fixed in liblingua-en-namecase-perl 1.21-1
has caused the Debian Bug report #979502,
regarding src:liblingua-en-namecase-perl: invalid maintainer address
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.)


-- 
979502: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979502
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: liblingua-en-namecase-perl
Version: 1.15-1
Severity: serious
Tags: bullseye sid
X-Debbugs-Cc: Holger Levsen 

The maintainer address is invalid, see below.

Ansgar

 Start of forwarded message 
From: Mail Delivery System 
Subject: Mail delivery failed: returning message to sender
Date: Wed, 06 Jan 2021 19:06:15 +

This message was created automatically by mail delivery software.

A message that you sent could not be delivered to one or more of its
recipients. This is a permanent error. The following address(es) failed:

  cwall...@lodgingcompany.com
host mail.lodgingcompany.com [75.157.242.131]
SMTP error from remote mail server after RCPT 
TO::
550 5.1.1 : Recipient address rejected:
User unknown in local recipient table
Reporting-MTA: dns; muffat.debian.org

Action: failed
Final-Recipient: rfc822;cwallace@lodgingcompany.com
Status: 5.0.0
Remote-MTA: dns; mail.lodgingcompany.com
Diagnostic-Code: smtp; 550 5.1.1 : Recipient address rejected: User unknown in local recipient table
--- End Message ---
--- Begin Message ---
Source: liblingua-en-namecase-perl
Source-Version: 1.21-1
Done: gregor herrmann 

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

Debian distribution maintenance software
pp.
gregor herrmann  (supplier of updated 
liblingua-en-namecase-perl package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 17 Jan 2021 21:53:03 +0100
Source: liblingua-en-namecase-perl
Architecture: source
Version: 1.21-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Perl Group 
Changed-By: gregor herrmann 
Closes: 965658 979502
Changes:
 liblingua-en-namecase-perl (1.21-1) unstable; urgency=medium
 .
   * Take over for the Debian Perl Group on request of the MIA team.
   * debian/control: Added: Vcs-Git field (source stanza); Vcs-Browser
 field (source stanza); ${misc:Depends} to Depends: field. Changed:
 Homepage field changed to metacpan.org URL; Maintainer set to Debian
 Perl Group  (was: C.
 Chad Wallace ).
 Fixes "invalid maintainer address" (Closes: #979502)
   * debian/watch: use uscan version 4.
   * debian/watch: use metacpan-based URL.
   * Mark package as autopkgtest-able.
   * Declare compliance with Debian Policy 4.5.1.
   * Set Rules-Requires-Root: no.
   * Drop unneeded version constraints from (build) dependencies.
   * Switch to source format "3.0 (quilt)".
   * Bump debhelper-compat to 13.
 Fixes "Removal of obsolete debhelper compat 5 and 6 in bookworm"
 (Closes: #965658)
   * debian/rules: use dh(1). And stop installing README.
   * debian/copyright: use Copyright-Format 1.0.
   * Add /me to Uploaders.
   * Mention module name in long description.
 .
   * Import upstream version 1.21.
   * Update upstream maintainer, copyright holders, and license.
   * Add debian/upstream/metadata.
   * Add build-dependency on libtest-most-perl.
Checksums-Sha1:
 dfdb2dbbb4ab305f45b407f5dd9700e8d643d152 2489 
liblingua-en-namecase-perl_1.21-1.dsc
 96a21e702d9189ab2c34676b3897fd5751538974 12160 
liblingua-en-namecase-perl_1.21.orig.tar.gz
 2d7dacd0f7e8265c3a697b701317aa7eaa32fb5d 5548 
liblingua-en-namecase-perl_1.21-1.debian.tar.xz
Checksums-Sha256:
 19854fe395ff8cc45baaed53cf7adf38ee9ee6efd2473c84bcccbe012727e9c6 2489 
liblingua-en-namecase-perl_1.21-1.dsc
 d8ef2b0236aa4c9d0d3d17d13c770792a1b10c81e7a115c1e9e22ffd3a93962f 12160 
liblingua-en-namecase-perl_1.21.orig.tar.gz
 41460a2be2c922f14f50ff78c69b32c043358ddef82051bbff10b2124da2fe96 5548 

Processed: Re: guile-gnutls: FTBFS against guile 3.0.4-1+b1

[Debian Bug Tracking System]

Processing control commands:

> fixed -1 3.7.0-1
Bug #966714 {Done: Paul Gevers } [guile-gnutls] 
guile-gnutls: FTBFS against guile 3.0.4-1+b1
Marked as fixed in versions gnutls28/3.7.0-1.

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

Bug#980309: marked as done (opam: trying to overwrite '/usr/share/doc/opam-installer/README.md.gz', which is also in package opam-installer 2.0.5-1)

[Debian Bug Tracking System]

Your message dated Sun, 17 Jan 2021 20:57:13 +
with message-id 
and subject line Bug#980309: fixed in opam 2.0.7-2
has caused the Debian Bug report #980309,
regarding opam: trying to overwrite 
'/usr/share/doc/opam-installer/README.md.gz', which is also in package 
opam-installer 2.0.5-1
to be marked as done.

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

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


-- 
980309: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=980309
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: opam
Version: 2.0.7-1
Severity: serious
Control: affects -1 opam-installer

Unpacking opam (2.0.7-1) over (2.0.5-1) ...
dpkg: error processing archive 
/tmp/apt-dpkg-install-8hvj8T/08-opam_2.0.7-1_amd64.deb (--unpack):
 trying to overwrite '/usr/share/doc/opam-installer/README.md.gz', which is 
also in package opam-installer 2.0.5-1
--- End Message ---
--- Begin Message ---
Source: opam
Source-Version: 2.0.7-2
Done: Mehdi Dogguy 

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

Debian distribution maintenance software
pp.
Mehdi Dogguy  (supplier of updated opam package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 17 Jan 2021 21:21:31 +0100
Source: opam
Architecture: source
Version: 2.0.7-2
Distribution: unstable
Urgency: medium
Maintainer: Debian OCaml Maintainers 
Changed-By: Mehdi Dogguy 
Closes: 980309
Changes:
 opam (2.0.7-2) unstable; urgency=medium
 .
   * Move documentation files back in opam-installer and update needed
 Breaks/Replaces in opam-installer's stanza (Closes: #980309)
Checksums-Sha1:
 b4a64ce38b1e6d4cd77e7e3d330a3a88e761e4c4 2595 opam_2.0.7-2.dsc
 b2f1c219184f02a759870a27dd3995b4f8d08144 8688 opam_2.0.7-2.debian.tar.xz
 9f6e308eb8db0225d9797a3316d711a8f42585ae 8230 opam_2.0.7-2_source.buildinfo
Checksums-Sha256:
 7b3745b510fe9e24b0bd314ec600051d1fbede2c7aad7c97b22a0f05efdf1d03 2595 
opam_2.0.7-2.dsc
 b2d7dd9bea82f38b5e4ccf0cf05a2cc7da927357b698a1b6eff6f35d9f855c48 8688 
opam_2.0.7-2.debian.tar.xz
 725907cbb0a2e0f6a27908f6c40a231084c8b5b18484d64afff924e899f0704c 8230 
opam_2.0.7-2_source.buildinfo
Files:
 9196bd569c2c4ef2e5b7e5cb96c46867 2595 ocaml optional opam_2.0.7-2.dsc
 a9a270e06ffd4dc8270767d8c1a38045 8688 ocaml optional opam_2.0.7-2.debian.tar.xz
 3fbaf156c57a218d2ba209a759be32fb 8230 ocaml optional 
opam_2.0.7-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJFBAEBCAAvFiEE/IeFmw45V03XKU7GPfRgADmhQMQFAmAEnbcRHG1laGRpQGRl
Ymlhbi5vcmcACgkQPfRgADmhQMRaXBAAmOvsOyPQuFvTVd+fDLW84Z6sptWiefbK
b9R1+U9O9uw+LLCZQc8EPAG4S4sixjjcjWYA4P3NgmCH5d/0NWoOJQ05p/42TeI6
f70onD0+j2wCPjtQF0ODE58mf7vsSyt6wH8Dc4jk1l8Kaj5uLleKGBX1l9ETeY7c
muLrqyi7mu7hi4KtPBdNNVpGgQ2ZlYfnBSFonPQoq8gVSvWA982pReLm+7eZ5vRU
W78IzOLT4KObCoWifGAW3AEMxPNvGnjEYjiLYKkSGmAqgHBufWbWJd8a61t07Gu8
KNbaN2bM6jqGHmytkdJMqKA6QQUFZGh5WpcN9w8rhECIaekltPDg9WcnfXgUlFuf
d4czCVoA0qa7qA9/62sfao2nbbby7s9yHL4IhHVMdjlgXV/dG/4YNb3FVYUt1mSs
OafzooQNC8hbdO/QgNtuKwjc8qGyFDMbzZZjMrcM0TmsZu/gPZY4t82XuM1oIqvT
vFpz71zAJBFdPuhGChoHglN3nXN1IZnKbLrpngVCfI0Y3XLLzfIlRvXnmwe483aq
eiEivBmlqvps18SJT1M1fxT1uXw+aN3PYDANU9XmrnJ+hn8Fr6JKRWkrKrR5+laO
hlUHZ36qIpy/iuOlh8bbS6AqBLSioK8wPQyu0IMzAbt20c2rrqJV8Df/EnZRrwQ3
MomsR8NE8to=
=VD/o
-END PGP SIGNATURE End Message ---

Bug#980291: marked as done (libjs-jquery-flot: breaking API change)

[Debian Bug Tracking System]

Your message dated Sun, 17 Jan 2021 20:49:28 +
with message-id 
and subject line Bug#980291: fixed in flot 4.2.1+dfsg-3
has caused the Debian Bug report #980291,
regarding libjs-jquery-flot: breaking API change
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.)


-- 
980291: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=980291
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libjs-jquery-flot
Version: 4.2.1+dfsg-2
Severity: important
Control: affects -1 debci

Dear Maintainer,

Thanks for updating flot.

The previous version provided minified files, but the new version drops
those. Below is the diff between the version currently in testing and the
one in unstable. You will notice that a bunch of new files (features) is
being added, but all the .min.js files that were there are dropped.

--- /tmp/testing2021-01-16 21:16:34.438430552 -0300
+++ /tmp/unstable   2021-01-16 21:16:52.158243268 -0300
@@ -5,45 +5,43 @@
 /usr/share/doc/libjs-jquery-flot
 /usr/share/doc/libjs-jquery-flot/API.md.gz
 /usr/share/doc/libjs-jquery-flot/changelog.Debian.gz
+/usr/share/doc/libjs-jquery-flot/changelog.gz
+/usr/share/doc/libjs-jquery-flot/CONTRIBUTING.md
 /usr/share/doc/libjs-jquery-flot/copyright
 /usr/share/doc/libjs-jquery-flot/FAQ.md
 /usr/share/doc/libjs-jquery-flot/NEWS.Debian.gz
-/usr/share/doc/libjs-jquery-flot/NEWS.md.gz
-/usr/share/doc/libjs-jquery-flot/PLUGINS.md.gz
 /usr/share/doc/libjs-jquery-flot/README.Debian
+/usr/share/doc/libjs-jquery-flot/README.md
 /usr/share/javascript
 /usr/share/javascript/jquery-flot
-/usr/share/javascript/jquery-flot/flot.jquery.json
+/usr/share/javascript/jquery-flot/jquery.canvaswrapper.js
 /usr/share/javascript/jquery-flot/jquery.colorhelpers.js
-/usr/share/javascript/jquery-flot/jquery.colorhelpers.min.js
-/usr/share/javascript/jquery-flot/jquery.flot.canvas.js
-/usr/share/javascript/jquery-flot/jquery.flot.canvas.min.js
+/usr/share/javascript/jquery-flot/jquery.flot.axislabels.js
+/usr/share/javascript/jquery-flot/jquery.flot.browser.js
 /usr/share/javascript/jquery-flot/jquery.flot.categories.js
-/usr/share/javascript/jquery-flot/jquery.flot.categories.min.js
+/usr/share/javascript/jquery-flot/jquery.flot.composeImages.js
 /usr/share/javascript/jquery-flot/jquery.flot.crosshair.js
-/usr/share/javascript/jquery-flot/jquery.flot.crosshair.min.js
+/usr/share/javascript/jquery-flot/jquery.flot.drawSeries.js
 /usr/share/javascript/jquery-flot/jquery.flot.errorbars.js
-/usr/share/javascript/jquery-flot/jquery.flot.errorbars.min.js
 /usr/share/javascript/jquery-flot/jquery.flot.fillbetween.js
-/usr/share/javascript/jquery-flot/jquery.flot.fillbetween.min.js
+/usr/share/javascript/jquery-flot/jquery.flot.flatdata.js
+/usr/share/javascript/jquery-flot/jquery.flot.hover.js
 /usr/share/javascript/jquery-flot/jquery.flot.image.js
-/usr/share/javascript/jquery-flot/jquery.flot.image.min.js
 /usr/share/javascript/jquery-flot/jquery.flot.js
+/usr/share/javascript/jquery-flot/jquery.flot.js.map
+/usr/share/javascript/jquery-flot/jquery.flot.legend.js
+/usr/share/javascript/jquery-flot/jquery.flot.logaxis.js
 /usr/share/javascript/jquery-flot/jquery.flot.min.js
 /usr/share/javascript/jquery-flot/jquery.flot.navigate.js
-/usr/share/javascript/jquery-flot/jquery.flot.navigate.min.js
 /usr/share/javascript/jquery-flot/jquery.flot.pack.js
 /usr/share/javascript/jquery-flot/jquery.flot.pie.js
-/usr/share/javascript/jquery-flot/jquery.flot.pie.min.js
 /usr/share/javascript/jquery-flot/jquery.flot.resize.js
-/usr/share/javascript/jquery-flot/jquery.flot.resize.min.js
+/usr/share/javascript/jquery-flot/jquery.flot.saturated.js
 /usr/share/javascript/jquery-flot/jquery.flot.selection.js
-/usr/share/javascript/jquery-flot/jquery.flot.selection.min.js
 /usr/share/javascript/jquery-flot/jquery.flot.stack.js
-/usr/share/javascript/jquery-flot/jquery.flot.stack.min.js
 /usr/share/javascript/jquery-flot/jquery.flot.symbol.js
-/usr/share/javascript/jquery-flot/jquery.flot.symbol.min.js
 /usr/share/javascript/jquery-flot/jquery.flot.threshold.js
-/usr/share/javascript/jquery-flot/jquery.flot.threshold.min.js
 /usr/share/javascript/jquery-flot/jquery.flot.time.js
-/usr/share/javascript/jquery-flot/jquery.flot.time.min.js
+/usr/share/javascript/jquery-flot/jquery.flot.touch.js
+/usr/share/javascript/jquery-flot/jquery.flot.touchNavigate.js
+/usr/share/javascript/jquery-flot/jquery.flot.uiConstants.js

This currently makes debci FTBFS, because it checks and symlinks two
files from flot into its own directory structure. I could switch to the
non-minified versions, but I would 

Bug#980033: marked as done (libucx0: UCX ERROR rdma_create_event_channel failed: No such device)

[Debian Bug Tracking System]

Your message dated Sun, 17 Jan 2021 20:37:51 +
with message-id 
and subject line Close bug
has caused the Debian Bug report #980033,
regarding libucx0: UCX  ERROR rdma_create_event_channel failed: No such device
to be marked as done.

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

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


-- 
980033: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=980033
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libucx0
Version: 1.10.0~rc1-2
Severity: serious
Justification: debci

Our next round of whack-a-mole comes from the new UCX.
pmix 4.0.0-3 seems to have fixed the pmix error from bug#979744.

debci tests next report a problem with UCX, with
  openmpi 4.1.0-5
  pmix 4.0.0-3
  ucx 1.10.0~rc1-2

The openmpi debci test at
https://ci.debian.net/data/autopkgtest/testing/arm64/o/openmpi/9650495/log.gz
reports:

autopkgtest [15:16:16]: test hello4: [---
[1610522176.588740] [ci-013-36a60f22:1417 :0]  rdmacm_cm.c:638  UCX  ERROR 
rdma_create_event_channel failed: No such device
[1610522176.588779] [ci-013-36a60f22:1417 :0] ucp_worker.c:1432 UCX  ERROR 
failed to open CM on component rdmacm with status Input/output error
[ci-013-36a60f22:01417] ../../../../../../ompi/mca/pml/ucx/pml_ucx.c:273  
Error: Failed to create UCP worker
 node   0 : Hello world
autopkgtest [15:16:17]: test hello4: ---]
autopkgtest [15:16:18]: test hello4:  - - - - - - - - - - results - - - - - - - 
- - -
hello4   FAIL stderr: [ci-013-36a60f22:01417] 
../../../../../../ompi/mca/pml/ucx/pml_ucx.c:273  Error: Failed to create UCP 
worker
autopkgtest [15:16:18]: test hello4:  - - - - - - - - - - stderr - - - - - - - 
- - -
[ci-013-36a60f22:01417] ../../../../../../ompi/mca/pml/ucx/pml_ucx.c:273  
Error: Failed to create UCP worker
autopkgtest [15:16:18]:  summary
hello1   FAIL stderr: [ci-013-36a60f22:01292] 
../../../../../../ompi/mca/pml/ucx/pml_ucx.c:273  Error: Failed to create UCP 
worker
hello2   FAIL stderr: [ci-013-36a60f22:01218] 
../../../../../../ompi/mca/pml/ucx/pml_ucx.c:273  Error: Failed to create UCP 
worker
hello4   FAIL stderr: [ci-013-36a60f22:01417] 
../../../../../../ompi/mca/pml/ucx/pml_ucx.c:273  Error: Failed to create UCP 
worker



Other client applications fail with the same error.


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

Kernel: Linux 5.10.0-1-amd64 (SMP w/8 CPU threads)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_AU:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages libucx0 depends on:
ii  ibverbs-providers  33.0-1
ii  libbinutils2.35.1-7
ii  libc6  2.31-9
ii  libibverbs133.0-1
ii  libnuma1   2.0.12-1+b1
ii  librdmacm1 33.0-1

libucx0 recommends no packages.

libucx0 suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---

close 980033

thanks

Bug was closed in openmpi 4.1.0-6


--
Alastair McKinstry, , , 
https://diaspora.sceal.ie/u/amckinstry
Misentropy: doubting that the Universe is becoming more disordered. 

--- End Message ---

Bug#976620: marked as done (xlrd: if defusedxml installed, AttributeError: 'ElementTree' object has no attribute 'getiterator')

[Debian Bug Tracking System]

Your message dated Sun, 17 Jan 2021 20:39:16 +
with message-id 
and subject line Bug#976620: fixed in python-xlrd 1.2.0-2
has caused the Debian Bug report #976620,
regarding xlrd: if defusedxml installed, AttributeError: 'ElementTree' object 
has no attribute 'getiterator'
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.)


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

Package: python3-xlrd
Version: 1.2.0-1
Tags: patch

xlrd 1.2.0 started using defusedxml if available.

As defusedxml.cElementTree does not have a top-level ElementTree 
attribute, Element_has_iter gets set to False 
(https://sources.debian.org/src/python-xlrd/1.2.0-1/xlrd/xlsx.py/#L59). 
However, ET.parse returns a standard library ElementTree, which does 
have iter and not getiterator.  This causes the error:


E   AttributeError: 'ElementTree' object has no attribute 'getiterator'

/usr/lib/python3/dist-packages/xlrd/xlsx.py:266: AttributeError

This shows up in the pandas autopkgtest, as python3-pandas 
recommends/test-depends on python3-odf and hence python3-defusedxml.


Untested fix:

--- /usr/lib/python3/dist-packages/xlrd/xlsx.py.old 2020-12-05 
22:07:52.009976382 +
+++ /usr/lib/python3/dist-packages/xlrd/xlsx.py 2020-12-05 
22:13:19.330486195 +

@@ -56,7 +56,7 @@ def ensure_elementtree_imported(verbosit
 ET_has_iterparse = True
 except NotImplementedError:
 pass
-Element_has_iter = hasattr(ET, 'ElementTree') and 
hasattr(ET.ElementTree, 'iter')
+Element_has_iter = hasattr(ET.parse(BYTES_IO(b'')), 
'iter')

 if verbosity:
 etree_version = repr([
 (item, getattr(ET, item))

Known upstream as https://github.com/python-excel/xlrd/pull/360, which 
suggests basically the same fix.
--- End Message ---
--- Begin Message ---
Source: python-xlrd
Source-Version: 1.2.0-2
Done: Josue Ortega 

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

Debian distribution maintenance software
pp.
Josue Ortega  (supplier of updated python-xlrd package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 17 Jan 2021 13:56:21 -0600
Source: python-xlrd
Architecture: source
Version: 1.2.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team 
Changed-By: Josue Ortega 
Closes: 976573 976620
Changes:
 python-xlrd (1.2.0-2) unstable; urgency=medium
 .
   * Team upload.
   * Add patch 0002-fix-python39-compat: In order to fix FTBS issue.
 Closes: #976573
   * Add 0003-python39-compat-iter-detection.patch in order to fix iter()
 call when defusedxml is installed. Closes: #976620
   * Bump Standards-Version to 4.5.1. No changes required
   * debian/watch: Bump file standard version  to 4
   * debian/control: Document Rules-Requires-Root field as 'no'
Checksums-Sha1:
 f52ac3383da787a2757c79f7a2ec5f4ec865741b 2143 python-xlrd_1.2.0-2.dsc
 a83a56ad625e6ed7469f1ce08923b89b63921fa9 7420 python-xlrd_1.2.0-2.debian.tar.xz
 f0bbf58fd4760bb6fb82b2d3f79da19315ec8223 7490 
python-xlrd_1.2.0-2_amd64.buildinfo
Checksums-Sha256:
 cb3489a6697cac03d919d20c6ad304ac31959aeab9413bccad95de21e70525e1 2143 
python-xlrd_1.2.0-2.dsc
 4cce60cea03c274015235102930f216bd4f5c3952ece983647c167880f78efda 7420 
python-xlrd_1.2.0-2.debian.tar.xz
 3e325bf108ef5bb529e3af998fcee141c2faa3ed6e448023d62dbbbf2609417e 7490 
python-xlrd_1.2.0-2_amd64.buildinfo
Files:
 b3097a7b946161dc3d81b6d5440142a8 2143 python optional python-xlrd_1.2.0-2.dsc
 59cea77e4283a7a2f571e92996ba7134 7420 python optional 
python-xlrd_1.2.0-2.debian.tar.xz
 d3892ae54c9572aef737139b84936693 7490 python optional 
python-xlrd_1.2.0-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJFBAEBCgAvFiEEdzOzKNJ5X1viMlrdAVCdXKtK/T8FAmAEl7ERHGpvc3VlQGRl
Ymlhbi5vcmcACgkQAVCdXKtK/T89CxAAj4uRTsvVUpqcIa426CHc+JAuK7Tl+DWS
ffyW45jkhCRDdzQrWsnt9SHZNHXRJq0Vq1plvkNYl3CkcTpjLJggK+RmK/iyMcFh
QtpQAAM1McFzgQ+VoOBlb+Qzqf1JOcZ3445Q89x9ce/EAJ2oRduk4mNAHULFbrXm

Bug#976573: marked as done (xlrd: AttributeError if defusedxml is installed)

[Debian Bug Tracking System]

Your message dated Sun, 17 Jan 2021 20:39:16 +
with message-id 
and subject line Bug#976620: fixed in python-xlrd 1.2.0-2
has caused the Debian Bug report #976620,
regarding xlrd: AttributeError if defusedxml is 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.)


-- 
976620: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976620
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pandas
Version: 1.1.4+dfsg-1
Severity: serious
Justification: FTBFS on arm64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201205 ftbfs-bullseye

Hi,

During a rebuild of all packages in sid, your package failed to build
on arm64 (I don't know if it also fails on amd64).

Relevant part (hopefully):
>  18 passed, 121 skipped in 1.39 seconds 
> 
> E: pybuild pybuild:353: test: plugin custom failed with: exit code=1: 
> TEST_SUCCESS=true; cd /<>/.pybuild/cpython3_3.9/build ; for 
> TEST_SUBSET in /<>/.pybuild/cpython3_3.9/build/pandas/tests/* ; 
> do LOCALE_OVERRIDE=C xvfb-run -a -s "-screen 0 1280x1024x24 -noreset" 
> python3.9 -m pytest -s -v -m "not network and not slow" -k "not 
> test_register_entrypoint" 
> --confcutdir=/<>/.pybuild/cpython3_3.9/build/pandas 
> --deb-data-root-dir=/<>/pandas/tests --strict-data-files 
> $TEST_SUBSET || test $? = 5 || TEST_SUCCESS=false ; done ; LOCALE_OVERRIDE=C 
> python3.9 -m pytest -s -v -m "not network and not slow" --forked --runxfail 
> --confcutdir=/<>/.pybuild/cpython3_3.9/build/pandas 
> --deb-data-root-dir=/<>/pandas/tests --strict-data-files 
> /<>/.pybuild/cpython3_3.9/build/pandas/tests/groupby/transform/test_numba.py
>  
> /<>/.pybuild/cpython3_3.9/build/pandas/tests/window/test_numba.py
>  
> /<>/.pybuild/cpython3_3.9/build/pandas/tests/window/test_apply.py
>  || true ; $TEST_SUCCESS
> dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.8 
> 3.9" returned exit code 13

The full build log is available from:
   http://qa-logs.debian.net/2020/12/05/pandas_1.1.4+dfsg-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 me
so that we can identify if something relevant changed in the meantime.

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
Source: python-xlrd
Source-Version: 1.2.0-2
Done: Josue Ortega 

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

Debian distribution maintenance software
pp.
Josue Ortega  (supplier of updated python-xlrd package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 17 Jan 2021 13:56:21 -0600
Source: python-xlrd
Architecture: source
Version: 1.2.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team 
Changed-By: Josue Ortega 
Closes: 976573 976620
Changes:
 python-xlrd (1.2.0-2) unstable; urgency=medium
 .
   * Team upload.
   * Add patch 0002-fix-python39-compat: In order to fix FTBS issue.
 Closes: #976573
   * Add 0003-python39-compat-iter-detection.patch in order to fix iter()
 call when defusedxml is installed. Closes: #976620
   * Bump Standards-Version to 4.5.1. No changes required
   * debian/watch: Bump file standard version  to 4
   * debian/control: Document Rules-Requires-Root field as 'no'
Checksums-Sha1:
 f52ac3383da787a2757c79f7a2ec5f4ec865741b 2143 python-xlrd_1.2.0-2.dsc
 a83a56ad625e6ed7469f1ce08923b89b63921fa9 7420 python-xlrd_1.2.0-2.debian.tar.xz
 f0bbf58fd4760bb6fb82b2d3f79da19315ec8223 7490 
python-xlrd_1.2.0-2_amd64.buildinfo
Checksums-Sha256:
 

Bug#976620: marked as done (xlrd: if defusedxml installed, AttributeError: 'ElementTree' object has no attribute 'getiterator')

[Debian Bug Tracking System]

Your message dated Sun, 17 Jan 2021 20:39:16 +
with message-id 
and subject line Bug#976573: fixed in python-xlrd 1.2.0-2
has caused the Debian Bug report #976573,
regarding xlrd: if defusedxml installed, AttributeError: 'ElementTree' object 
has no attribute 'getiterator'
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.)


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

Package: python3-xlrd
Version: 1.2.0-1
Tags: patch

xlrd 1.2.0 started using defusedxml if available.

As defusedxml.cElementTree does not have a top-level ElementTree 
attribute, Element_has_iter gets set to False 
(https://sources.debian.org/src/python-xlrd/1.2.0-1/xlrd/xlsx.py/#L59). 
However, ET.parse returns a standard library ElementTree, which does 
have iter and not getiterator.  This causes the error:


E   AttributeError: 'ElementTree' object has no attribute 'getiterator'

/usr/lib/python3/dist-packages/xlrd/xlsx.py:266: AttributeError

This shows up in the pandas autopkgtest, as python3-pandas 
recommends/test-depends on python3-odf and hence python3-defusedxml.


Untested fix:

--- /usr/lib/python3/dist-packages/xlrd/xlsx.py.old 2020-12-05 
22:07:52.009976382 +
+++ /usr/lib/python3/dist-packages/xlrd/xlsx.py 2020-12-05 
22:13:19.330486195 +

@@ -56,7 +56,7 @@ def ensure_elementtree_imported(verbosit
 ET_has_iterparse = True
 except NotImplementedError:
 pass
-Element_has_iter = hasattr(ET, 'ElementTree') and 
hasattr(ET.ElementTree, 'iter')
+Element_has_iter = hasattr(ET.parse(BYTES_IO(b'')), 
'iter')

 if verbosity:
 etree_version = repr([
 (item, getattr(ET, item))

Known upstream as https://github.com/python-excel/xlrd/pull/360, which 
suggests basically the same fix.
--- End Message ---
--- Begin Message ---
Source: python-xlrd
Source-Version: 1.2.0-2
Done: Josue Ortega 

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

Debian distribution maintenance software
pp.
Josue Ortega  (supplier of updated python-xlrd package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 17 Jan 2021 13:56:21 -0600
Source: python-xlrd
Architecture: source
Version: 1.2.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team 
Changed-By: Josue Ortega 
Closes: 976573 976620
Changes:
 python-xlrd (1.2.0-2) unstable; urgency=medium
 .
   * Team upload.
   * Add patch 0002-fix-python39-compat: In order to fix FTBS issue.
 Closes: #976573
   * Add 0003-python39-compat-iter-detection.patch in order to fix iter()
 call when defusedxml is installed. Closes: #976620
   * Bump Standards-Version to 4.5.1. No changes required
   * debian/watch: Bump file standard version  to 4
   * debian/control: Document Rules-Requires-Root field as 'no'
Checksums-Sha1:
 f52ac3383da787a2757c79f7a2ec5f4ec865741b 2143 python-xlrd_1.2.0-2.dsc
 a83a56ad625e6ed7469f1ce08923b89b63921fa9 7420 python-xlrd_1.2.0-2.debian.tar.xz
 f0bbf58fd4760bb6fb82b2d3f79da19315ec8223 7490 
python-xlrd_1.2.0-2_amd64.buildinfo
Checksums-Sha256:
 cb3489a6697cac03d919d20c6ad304ac31959aeab9413bccad95de21e70525e1 2143 
python-xlrd_1.2.0-2.dsc
 4cce60cea03c274015235102930f216bd4f5c3952ece983647c167880f78efda 7420 
python-xlrd_1.2.0-2.debian.tar.xz
 3e325bf108ef5bb529e3af998fcee141c2faa3ed6e448023d62dbbbf2609417e 7490 
python-xlrd_1.2.0-2_amd64.buildinfo
Files:
 b3097a7b946161dc3d81b6d5440142a8 2143 python optional python-xlrd_1.2.0-2.dsc
 59cea77e4283a7a2f571e92996ba7134 7420 python optional 
python-xlrd_1.2.0-2.debian.tar.xz
 d3892ae54c9572aef737139b84936693 7490 python optional 
python-xlrd_1.2.0-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJFBAEBCgAvFiEEdzOzKNJ5X1viMlrdAVCdXKtK/T8FAmAEl7ERHGpvc3VlQGRl
Ymlhbi5vcmcACgkQAVCdXKtK/T89CxAAj4uRTsvVUpqcIa426CHc+JAuK7Tl+DWS
ffyW45jkhCRDdzQrWsnt9SHZNHXRJq0Vq1plvkNYl3CkcTpjLJggK+RmK/iyMcFh
QtpQAAM1McFzgQ+VoOBlb+Qzqf1JOcZ3445Q89x9ce/EAJ2oRduk4mNAHULFbrXm

Bug#976573: marked as done (xlrd: AttributeError if defusedxml is installed)

[Debian Bug Tracking System]

Your message dated Sun, 17 Jan 2021 20:39:16 +
with message-id 
and subject line Bug#976573: fixed in python-xlrd 1.2.0-2
has caused the Debian Bug report #976573,
regarding xlrd: AttributeError if defusedxml is 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.)


-- 
976573: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976573
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pandas
Version: 1.1.4+dfsg-1
Severity: serious
Justification: FTBFS on arm64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201205 ftbfs-bullseye

Hi,

During a rebuild of all packages in sid, your package failed to build
on arm64 (I don't know if it also fails on amd64).

Relevant part (hopefully):
>  18 passed, 121 skipped in 1.39 seconds 
> 
> E: pybuild pybuild:353: test: plugin custom failed with: exit code=1: 
> TEST_SUCCESS=true; cd /<>/.pybuild/cpython3_3.9/build ; for 
> TEST_SUBSET in /<>/.pybuild/cpython3_3.9/build/pandas/tests/* ; 
> do LOCALE_OVERRIDE=C xvfb-run -a -s "-screen 0 1280x1024x24 -noreset" 
> python3.9 -m pytest -s -v -m "not network and not slow" -k "not 
> test_register_entrypoint" 
> --confcutdir=/<>/.pybuild/cpython3_3.9/build/pandas 
> --deb-data-root-dir=/<>/pandas/tests --strict-data-files 
> $TEST_SUBSET || test $? = 5 || TEST_SUCCESS=false ; done ; LOCALE_OVERRIDE=C 
> python3.9 -m pytest -s -v -m "not network and not slow" --forked --runxfail 
> --confcutdir=/<>/.pybuild/cpython3_3.9/build/pandas 
> --deb-data-root-dir=/<>/pandas/tests --strict-data-files 
> /<>/.pybuild/cpython3_3.9/build/pandas/tests/groupby/transform/test_numba.py
>  
> /<>/.pybuild/cpython3_3.9/build/pandas/tests/window/test_numba.py
>  
> /<>/.pybuild/cpython3_3.9/build/pandas/tests/window/test_apply.py
>  || true ; $TEST_SUCCESS
> dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.8 
> 3.9" returned exit code 13

The full build log is available from:
   http://qa-logs.debian.net/2020/12/05/pandas_1.1.4+dfsg-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 me
so that we can identify if something relevant changed in the meantime.

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
Source: python-xlrd
Source-Version: 1.2.0-2
Done: Josue Ortega 

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

Debian distribution maintenance software
pp.
Josue Ortega  (supplier of updated python-xlrd package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 17 Jan 2021 13:56:21 -0600
Source: python-xlrd
Architecture: source
Version: 1.2.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team 
Changed-By: Josue Ortega 
Closes: 976573 976620
Changes:
 python-xlrd (1.2.0-2) unstable; urgency=medium
 .
   * Team upload.
   * Add patch 0002-fix-python39-compat: In order to fix FTBS issue.
 Closes: #976573
   * Add 0003-python39-compat-iter-detection.patch in order to fix iter()
 call when defusedxml is installed. Closes: #976620
   * Bump Standards-Version to 4.5.1. No changes required
   * debian/watch: Bump file standard version  to 4
   * debian/control: Document Rules-Requires-Root field as 'no'
Checksums-Sha1:
 f52ac3383da787a2757c79f7a2ec5f4ec865741b 2143 python-xlrd_1.2.0-2.dsc
 a83a56ad625e6ed7469f1ce08923b89b63921fa9 7420 python-xlrd_1.2.0-2.debian.tar.xz
 f0bbf58fd4760bb6fb82b2d3f79da19315ec8223 7490 
python-xlrd_1.2.0-2_amd64.buildinfo
Checksums-Sha256:
 

Processed: Bug#980309 marked as pending in opam

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #980309 [opam] opam: trying to overwrite 
'/usr/share/doc/opam-installer/README.md.gz', which is also in package 
opam-installer 2.0.5-1
Added tag(s) pending.

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

Bug#980309: marked as pending in opam

[Mehdi Dogguy]

Control: tag -1 pending

Hello,

Bug #980309 in opam reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:

https://salsa.debian.org/ocaml-team/opam/-/commit/c6686267c0a384112dfa7b0c406c0f6f7d1b5460


Move documentation files back in opam-installer and update needed 
Breaks/Replaces in opam-installer's stanza (Closes: #980309)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/980309

Processed: Bug#980291 marked as pending in flot

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #980291 [libjs-jquery-flot] libjs-jquery-flot: breaking API change
Added tag(s) pending.

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

Bug#980291: marked as pending in flot

[Xavier Guimard]

Control: tag -1 pending

Hello,

Bug #980291 in flot reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:

https://salsa.debian.org/js-team/flot/-/commit/b5108692905fb31a8639474d22bdd5a109aefbc6


Provide minified files and related maps

Closes: #980291


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/980291

Processed: severity of 976938 is important

[Debian Bug Tracking System]

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

> severity 976938 important
Bug #976938 [src:idlastro] idlastro: FTBFS on ppc64el (arch:all-only src pkg): 
tests failed
Severity set to 'important' from 'serious'
> thanks
Stopping processing here.

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

Processed: tagging 977079

[Debian Bug Tracking System]

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

> tags 977079 + ftbfs
Bug #977079 [src:pytest-bdd] pytest-bdd FTBFS with pytest 6
Added tag(s) ftbfs.
> thanks
Stopping processing here.

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

Processed: tagging 977095

[Debian Bug Tracking System]

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

> tags 977095 + ftbfs
Bug #977095 [src:sentry-python] sentry-python FTBFS with pytest 6
Added tag(s) ftbfs.
> thanks
Stopping processing here.

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

Processed: tagging 977068

[Debian Bug Tracking System]

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

> tags 977068 + ftbfs
Bug #977068 [src:indexed-gzip] indexed-gzip FTBFS with pytest 6
Added tag(s) ftbfs.
> thanks
Stopping processing here.

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

Bug#976620: marked as pending in python-xlrd

[Josué Ortega]

Control: tag -1 pending

Hello,

Bug #976620 in python-xlrd reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:

https://salsa.debian.org/python-team/packages/python-xlrd/-/commit/4f06dc25979485272169fdfaea1475189130dc75


Add 0003-python39-compat-iter-detection.patch in order to fix iter() call when 
defusedxml is installed. Closes: #976620


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/976620

Processed: Bug#976573 marked as pending in python-xlrd

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #976573 [python3-xlrd] xlrd: AttributeError if defusedxml is installed
Bug #976620 [python3-xlrd] xlrd: if defusedxml installed, AttributeError: 
'ElementTree' object has no attribute 'getiterator'
Added tag(s) pending.
Added tag(s) pending.

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

Processed: Bug#976620 marked as pending in python-xlrd

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #976620 [python3-xlrd] xlrd: if defusedxml installed, AttributeError: 
'ElementTree' object has no attribute 'getiterator'
Bug #976573 [python3-xlrd] xlrd: AttributeError if defusedxml is installed
Ignoring request to alter tags of bug #976620 to the same tags previously set
Ignoring request to alter tags of bug #976573 to the same tags previously set

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

Bug#976573: marked as pending in python-xlrd

[Josué Ortega]

Control: tag -1 pending

Hello,

Bug #976573 in python-xlrd reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:

https://salsa.debian.org/python-team/packages/python-xlrd/-/commit/d1c0948992ef67ecb7f4a01723249d3e040e6f00


Add debian/patches/0002-fix-python39-compat.patch Closes: #976573


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/976573

Processed: your mail

[Debian Bug Tracking System]

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

> severity 980050 serious
Bug #980050 [src:mdtraj] mdtraj: FTBFS with jupyter-client 6.1.11
Severity set to 'serious' from 'normal'
>
End of message, stopping processing here.

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

Processed: #951948 fixed-upstream

[Debian Bug Tracking System]

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

> tags 951948 + fixed-upstream
Bug #951948 [src:vdirsyncer] vdirsyncer: FTBFS: LookupError: setuptools-scm was 
unable to detect version for '/<>'.
Added tag(s) fixed-upstream.
>
End of message, stopping processing here.

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

Bug#918526: mtail: FTBFS randomly

[Filippo Giunchedi]

On Sun, Jan 17, 2021 at 04:55:20PM +0100, Santiago Vila wrote:
> On Sun, Jan 17, 2021 at 03:42:30PM +, Filippo Giunchedi wrote:
> 
> > I've uploaded 3.0.0~rc41-1 yesterday with the flaky tests fixed, and indeed
> > mtail built fine on all release architectures:
> > 
> > https://buildd.debian.org/status/package.php?p=mtail
> > 
> > I'm resolving the bug since I think it is fixed, of course please reopen if 
> > sth is amiss!
> 
> Hi. This is still a package which FTBFS randomly in buster, the
> current supported stable distribution. Would you please consider
> fixing this FTBFS bug in stable, where people will still have
> to deal with it?

I agree that the FTBFS in buster is a problem, ATM I'm focusing more on
bullseye and won't have time. Although repurposing this bug or filing a new
one seems right to me!

HTH,
Filippo

Bug#978386: marked as done (xdemorse: FTBFS: configure:5266: error: possibly undefined macro: AM_INTL_SUBDIR (caused by gettext 0.19 -> 0.21?))

[Debian Bug Tracking System]

Your message dated Sun, 17 Jan 2021 18:13:55 +
with message-id 
and subject line Bug#978386: fixed in xdemorse 3.6.2-2
has caused the Debian Bug report #978386,
regarding xdemorse: FTBFS: configure:5266: error: possibly undefined macro: 
AM_INTL_SUBDIR (caused by gettext 0.19 -> 0.21?)
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.)


-- 
978386: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=978386
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: xdemorse
Version: 3.6.2-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201226 ftbfs-bullseye

Hi,

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

Relevant part (hopefully):
> DC-Build-Header: xdemorse 3.6.2-1 / 2020-12-26 18:40:08 +
> DC-Task: type:rebuild-full source:xdemorse version:3.6.2-1 chroot:unstable 
> esttime:58 logfile:/tmp/xdemorse_3.6.2-1_unstable.log modes:
> DC-Sbuild-call: su user42 -c 'sbuild -n -A -s --force-orig-source 
> --apt-update -d unstable -v --no-run-lintian xdemorse_3.6.2-1'
> sbuild (Debian sbuild) 0.78.1 (09 February 2019) on 
> ip-172-31-1-222.eu-central-1.compute.internal
> 
> +==+
> | xdemorse 3.6.2-1 (amd64) Sat, 26 Dec 2020 18:40:09 
> + |
> +==+
> 
> Package: xdemorse
> Version: 3.6.2-1
> Source Version: 3.6.2-1
> Distribution: unstable
> Machine Architecture: amd64
> Host Architecture: amd64
> Build Architecture: amd64
> Build Type: full
> 
> I: NOTICE: Log filtering will replace 
> 'var/run/schroot/mount/sid-amd64-sbuild-e7df248f-ddfa-48e3-8aa7-7a8b4c41c497' 
> with '<>'
> I: NOTICE: Log filtering will replace 'build/xdemorse-ss4TSw/resolver-j8vHvh' 
> with '<>'
> 
> +--+
> | Update chroot   
>  |
> +--+
> 
> Get:1 http://127.0.0.1:12990/debian sid InRelease [153 kB]
> Get:2 http://127.0.0.1:12990/debian sid/main Sources.diff/Index [27.9 kB]
> Get:3 http://127.0.0.1:12990/debian sid/main amd64 Packages.diff/Index [27.9 
> kB]
> Get:4 http://127.0.0.1:12990/debian sid/main Sources 2020-12-26-0800.12.pdiff 
> [3765 B]
> Get:5 http://127.0.0.1:12990/debian sid/main Sources 2020-12-26-1401.32.pdiff 
> [20.3 kB]
> Get:5 http://127.0.0.1:12990/debian sid/main Sources 2020-12-26-1401.32.pdiff 
> [20.3 kB]
> Get:6 http://127.0.0.1:12990/debian sid/main amd64 Packages 
> 2020-12-26-0800.12.pdiff [3354 B]
> Get:7 http://127.0.0.1:12990/debian sid/main amd64 Packages 
> 2020-12-26-1401.32.pdiff [25.2 kB]
> Get:7 http://127.0.0.1:12990/debian sid/main amd64 Packages 
> 2020-12-26-1401.32.pdiff [25.2 kB]
> Fetched 262 kB in 1s (260 kB/s)
> Reading package lists...
> Reading package lists...
> Building dependency tree...
> Calculating upgrade...
> The following packages will be upgraded:
>   libsystemd0 libudev1
> 2 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
> Need to get 540 kB of archives.
> After this operation, 0 B of additional disk space will be used.
> Get:1 http://127.0.0.1:12990/debian sid/main amd64 libsystemd0 amd64 247.2-3 
> [374 kB]
> Get:2 http://127.0.0.1:12990/debian sid/main amd64 libudev1 amd64 247.2-3 
> [166 kB]
> debconf: delaying package configuration, since apt-utils is not installed
> Fetched 540 kB in 0s (9194 kB/s)
> (Reading database ... 
(Reading database ... 5%
(Reading database ... 10%
(Reading database ... 15%
(Reading database ... 20%
(Reading database ... 25%
(Reading database ... 30%
(Reading database ... 35%
(Reading database ... 40%
(Reading database ... 45%
(Reading database ... 50%
(Reading database ... 55%
(Reading database ... 60%
(Reading database ... 65%
(Reading database ... 70%
(Reading database ... 75%
(Reading database ... 80%
(Reading database ... 85%
(Reading database ... 90%
(Reading database ... 95%
(Reading database ... 100%
(Reading database ... 12355 files and directories currently installed.)
> Preparing to unpack .../libsystemd0_247.2-3_amd64.deb ...
> Unpacking libsystemd0:amd64 (247.2-3) over (247.2-2) ...
> Setting up libsystemd0:amd64 (247.2-3) ...
> (Reading database ... 
(Reading database ... 5%
(Reading database ... 10%
(Reading database ... 15%
(Reading database ... 20%
(Reading database ... 25%
(Reading database ... 30%
(Reading database ... 35%
(Reading database 

Processed: notfound 978172 in evolution-data-server/evolution-data-server ...

[Debian Bug Tracking System]

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

> notfound 978172 evolution-data-server/evolution-data-server
Bug #978172 [src:evolution-data-server,src:libphonenumber] 
evolution-data-server: FTBFS: libphonenumber-dev no longer depends on 
libboost-dev as needed when defining I18N_PHONENUMBERS_USE_BOOST
The source evolution-data-server and version evolution-data-server do not 
appear to match any binary packages
No longer marked as found in versions 
evolution-data-server/evolution-data-server.
> notfound 978172 libphonenumber/evolution-data-server
Bug #978172 [src:evolution-data-server,src:libphonenumber] 
evolution-data-server: FTBFS: libphonenumber-dev no longer depends on 
libboost-dev as needed when defining I18N_PHONENUMBERS_USE_BOOST
The source libphonenumber and version evolution-data-server do not appear to 
match any binary packages
No longer marked as found in versions libphonenumber/evolution-data-server.
> thanks
Stopping processing here.

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

Processed: found 978172 in evolution-data-server/3.38.2-2, notfound 978172 in src/3.38.2-2

[Debian Bug Tracking System]

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

> found 978172 evolution-data-server/3.38.2-2
Bug #978172 [src:evolution-data-server,src:libphonenumber] 
evolution-data-server: FTBFS: libphonenumber-dev no longer depends on 
libboost-dev as needed when defining I18N_PHONENUMBERS_USE_BOOST
Marked as found in versions evolution-data-server/3.38.2-2.
> notfound 978172 src/3.38.2-2
Bug #978172 [src:evolution-data-server,src:libphonenumber] 
evolution-data-server: FTBFS: libphonenumber-dev no longer depends on 
libboost-dev as needed when defining I18N_PHONENUMBERS_USE_BOOST
The source src and version 3.38.2-2 do not appear to match any binary packages
No longer marked as found in versions src/3.38.2-2.
> thanks
Stopping processing here.

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

Bug#979298: marked as done (python-mechanicalsoup autopkgtests fail with pytest 6)

[Debian Bug Tracking System]

Your message dated Sun, 17 Jan 2021 17:50:58 +
with message-id 
and subject line Bug#979298: fixed in python-mechanicalsoup 0.10.0-4
has caused the Debian Bug report #979298,
regarding python-mechanicalsoup autopkgtests fail with pytest 6
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.)


-- 
979298: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979298
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-mechanicalsoup
Version: 0.10.0-3
Severity: important
User: pyt...@packages.debian.org
Usertags: pytest-v6

Hi,

python-mechanicalsoup autopkgtests fail with pytest 6 in unstable
because it uses a feature that has been removed:


https://docs.pytest.org/en/stable/deprecations.html#raises-warns-with-a-string-as-the-second-argument

The fragment of the CI error log below has more details.

> === FAILURES 
> ===
> __ test_form_noaction 
> __
> 
> def test_form_noaction():
> browser, url = setup_mock_browser()
> browser.open_fake_page(submit_form_noaction)
> browser.select_form('#choose-submit-form')
>>   with pytest.raises(ValueError, message="no URL to submit to"):
> E   TypeError: Unexpected keyword arguments passed to pytest.raises: 
> message
> E   Use context-manager form instead?
> 
> tests/test_stateful_browser.py:261: TypeError
> === short test summary info 
> 
> FAILED tests/test_stateful_browser.py::test_form_noaction - TypeError: 
> Unexpe...
>  1 failed, 63 passed in 13.45s 
> =
--- End Message ---
--- Begin Message ---
Source: python-mechanicalsoup
Source-Version: 0.10.0-4
Done: Ondřej Nový 

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

Debian distribution maintenance software
pp.
Ondřej Nový  (supplier of updated python-mechanicalsoup 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 17 Jan 2021 18:24:31 +0100
Source: python-mechanicalsoup
Architecture: source
Version: 0.10.0-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team 
Changed-By: Ondřej Nový 
Closes: 979298
Changes:
 python-mechanicalsoup (0.10.0-4) unstable; urgency=medium
 .
   [ Ondřej Nový ]
   * Team upload.
   * Bump Standards-Version to 4.4.1.
   * d/control: Update Maintainer field with new Debian Python Team
 contact address.
   * d/control: Update Vcs-* fields with new Debian Python Team Salsa
 layout.
   * Fix compatibility with pytest 6 (Closes: #979298).
 .
   [ Debian Janitor ]
   * Set upstream metadata fields: Repository, Repository-Browse.
   * Wrap long lines in changelog entries: 0.10.0-2.
   * Set upstream metadata fields: Bug-Database, Bug-Submit, Repository.
   * Update standards version to 4.5.0, no changes needed.
Checksums-Sha1:
 fcb1f10ab957ac59366d8bb024b1f4f67e9d9481 2304 
python-mechanicalsoup_0.10.0-4.dsc
 662fee041291e1afd955acbe6efe3f3420816288 6028 
python-mechanicalsoup_0.10.0-4.debian.tar.xz
 6405e68ab82e41a5a5882ad15b9b8097b712fd90 6826 
python-mechanicalsoup_0.10.0-4_amd64.buildinfo
Checksums-Sha256:
 5801d170dcfa1be21d15fdfede3830cd0b14a896c29446ab75edbf9f41461aa4 2304 
python-mechanicalsoup_0.10.0-4.dsc
 1884f2efe83a5a806298566b57385f9bcc3bd151c066274816af446246820caa 6028 
python-mechanicalsoup_0.10.0-4.debian.tar.xz
 a07400a4359e9a98b289501f724c9de03dc3f649c13c15d2da79ddc282e2849c 6826 
python-mechanicalsoup_0.10.0-4_amd64.buildinfo
Files:
 911ed73788ceac559f3bb6b500035da0 2304 python optional 
python-mechanicalsoup_0.10.0-4.dsc
 24112e71f67df2d372c4868db47c358b 6028 python optional 
python-mechanicalsoup_0.10.0-4.debian.tar.xz
 6b635acdb474cf8f3b0d944d5773b14e 6826 python optional 
python-mechanicalsoup_0.10.0-4_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEPZg8UuuFmAxGpWCQNXMSVZ0eBksFAmAEc14ACgkQNXMSVZ0e

Processed: reassign 978172 to src:evolution-data-server,src:libphonenumber ...

[Debian Bug Tracking System]

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

> reassign 978172 src:evolution-data-server,src:libphonenumber
Bug #978172 [src:evolution-data-server] evolution-data-server: FTBFS: 
libphonenumber-dev no longer depends on libboost-dev as needed when defining 
I18N_PHONENUMBERS_USE_BOOST
Bug reassigned from package 'src:evolution-data-server' to 
'src:evolution-data-server,src:libphonenumber'.
No longer marked as found in versions evolution-data-server/3.38.2-2.
Ignoring request to alter fixed versions of bug #978172 to the same values 
previously set
> found 978172 evolution-data-server,src/3.38.2-2
Bug #978172 [src:evolution-data-server,src:libphonenumber] 
evolution-data-server: FTBFS: libphonenumber-dev no longer depends on 
libboost-dev as needed when defining I18N_PHONENUMBERS_USE_BOOST
The source 'evolution-data-server' and version 'evolution-data-server' do not 
appear to match any binary packages
The source 'libphonenumber' and version 'evolution-data-server' do not appear 
to match any binary packages
The source src and version 3.38.2-2 do not appear to match any binary packages
Marked as found in versions src/3.38.2-2, libphonenumber/evolution-data-server, 
and evolution-data-server/evolution-data-server.
> found 978172 libphonenumber/7.1.0-7
Bug #978172 [src:evolution-data-server,src:libphonenumber] 
evolution-data-server: FTBFS: libphonenumber-dev no longer depends on 
libboost-dev as needed when defining I18N_PHONENUMBERS_USE_BOOST
Marked as found in versions libphonenumber/7.1.0-7.
> thanks
Stopping processing here.

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

Bug#977092: marked as done (python-pyscss FTBFS with pytest 6)

[Debian Bug Tracking System]

Your message dated Sun, 17 Jan 2021 17:36:09 +
with message-id 
and subject line Bug#977092: fixed in python-pyscss 1.3.7-3
has caused the Debian Bug report #977092,
regarding python-pyscss FTBFS with pytest 6
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.)


-- 
977092: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977092
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-pyscss
Version: 1.3.7-2
Severity: important
User: pyt...@packages.debian.org
Usertags: pytest-v6

Hi,

python-pyscss  FTBFS with pytest 6 in experimental. See the relevant
part of the changelog as to why:

https://docs.pytest.org/en/stable/changelog.html#id170

The error log below has more details.

> I: pybuild base:232: cd /<>/.pybuild/cpython3_3.9_pyscss/build; 
> python3.9 -m pytest /<>/scss/tests
> /<>/scss/selector.py:26: FutureWarning: Possible nested set at 
> position 329
>   SELECTOR_TOKENIZER = re.compile(r'''
> = test session starts 
> ==
> platform linux -- Python 3.9.1, pytest-6.0.2, py-1.9.0, pluggy-0.13.0
> rootdir: /<>/scss
> collected 0 items / 1 error
> 
>  ERRORS 
> 
>  ERROR collecting test session 
> _
> /usr/lib/python3/dist-packages/pluggy/hooks.py:286: in __call__
> return self._hookexec(self, self.get_hookimpls(), kwargs)
> /usr/lib/python3/dist-packages/pluggy/manager.py:92: in _hookexec
> return self._inner_hookexec(hook, methods, kwargs)
> /usr/lib/python3/dist-packages/pluggy/manager.py:83: in 
> self._inner_hookexec = lambda hook, methods, kwargs: hook.multicall(
> ../../../conftest.py:61: in pytest_collect_file
> return SassFile(path, parent)
> /usr/lib/python3/dist-packages/_pytest/nodes.py:95: in __call__
> warnings.warn(NODE_USE_FROM_PARENT.format(name=self.__name__), 
> stacklevel=2)
> E   pytest.PytestDeprecationWarning: Direct construction of SassFile has been 
> deprecated, please use SassFile.from_parent.
> E   See 
> https://docs.pytest.org/en/stable/deprecations.html#node-construction-changed-to-node-from-parent
>  for more details.
> === short test summary info 
> 
> ERROR ../../../scss - pytest.PytestDeprecationWarning: Direct construction 
> of...
>  Interrupted: 1 error during collection 
> 
> === 1 error in 0.06s 
> ===
> E: pybuild pybuild:353: test: plugin distutils failed with: exit code=2: cd 
> /<>/.pybuild/cpython3_3.9_pyscss/build; python3.9 -m pytest 
> {dir}/scss/tests
> dh_auto_test: error: pybuild --test -i python{version} -p 3.9 returned exit 
> code 13
> make: *** [debian/rules:17: build] Error 25
> dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2
--- End Message ---
--- Begin Message ---
Source: python-pyscss
Source-Version: 1.3.7-3
Done: Ondřej Nový 

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

Debian distribution maintenance software
pp.
Ondřej Nový  (supplier of updated python-pyscss package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 17 Jan 2021 18:10:38 +0100
Source: python-pyscss
Architecture: source
Version: 1.3.7-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team 
Changed-By: Ondřej Nový 
Closes: 977092
Changes:
 python-pyscss (1.3.7-3) unstable; urgency=medium
 .
   * Team upload.
   * d/control: Update Maintainer field with new Debian Python Team
 contact address.
   * d/control: Update Vcs-* fields with new Debian Python Team Salsa
 layout.
   * Fix pytest 6 compatibility (Closes: #977092).
Checksums-Sha1:
 11edccaa6f8c7a50b6e4ddb60c0314e00e004a4a 2137 python-pyscss_1.3.7-3.dsc
 a77f72a673ebe5e469c403df63a4df03d144f10a 5900 
python-pyscss_1.3.7-3.debian.tar.xz
 48aa397cb093923ec3c0ee0b98a2bfdea67a8788 8097 

Processed: Update yarnpkg to 2.x versions using corepack repo

[Debian Bug Tracking System]

Processing control commands:

> block 956423 by -1
Bug #956423 [node-request] node-request: deprecated upstream: should not be 
part of next stable Debian release
956423 was blocked by: 958682 958690 958680 958679 958692 958686 958681 976861 
958696 958691 958688 958695 958685 958689 958687 958694 958693 958683 958684 
958697
956423 was not blocking any bugs.
Added blocking bug(s) of 956423: 980316

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

Bug#979298: marked as pending in python-mechanicalsoup

[Ondřej Nový]

Control: tag -1 pending

Hello,

Bug #979298 in python-mechanicalsoup reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:

https://salsa.debian.org/python-team/packages/python-mechanicalsoup/-/commit/2a1e61977ae7151d2066dafc553d0282b439b8e3


Fix compatibility with pytest 6 (Closes: #979298).


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/979298

Processed: Bug#979298 marked as pending in python-mechanicalsoup

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #979298 [src:python-mechanicalsoup] python-mechanicalsoup autopkgtests fail 
with pytest 6
Added tag(s) pending.

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

Processed: Bug#977092 marked as pending in python-pyscss

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #977092 [src:python-pyscss] python-pyscss FTBFS with pytest 6
Added tag(s) pending.

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

Bug#977092: marked as pending in python-pyscss

[Ondřej Nový]

Control: tag -1 pending

Hello,

Bug #977092 in python-pyscss reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:

https://salsa.debian.org/python-team/packages/python-pyscss/-/commit/5f6785fdf687eaffb6a22f0e90c0aa9a0c4b2b6f


Fix pytest 6 compatibility (Closes: #977092).


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/977092

Bug#971368: marked as done (libfcgi-perl: missing source for FCGI_COMMON_CHECKS)

[Debian Bug Tracking System]

Your message dated Sun, 17 Jan 2021 17:06:46 +
with message-id 
and subject line Bug#971368: fixed in libfcgi-perl 0.79+ds-1
has caused the Debian Bug report #971368,
regarding libfcgi-perl: missing source for FCGI_COMMON_CHECKS
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.)


-- 
971368: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=971368
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libfcgi-perl
Version: 0.79-1
Severity: serious
Justification: missing source

I've looked into libfcgi-perl and noticed that the macro
FCGI_COMMON_CHECKS used in configure.in misses source code in the
libfcgi-perl package. I've looked in the archive and it seems that there
is another copy of this macro in another package that might do here:
https://sources.debian.org/src/libfcgi/2.4.0-10/acinclude.m4/?hl=3#L3

However, libfcgi-perl does not depend on that package in anyway, so it
definitely doesn't use it and it also does not prevent removal of
libfcgi, which is required for honouring DFSG (if that copy is indeed
the relevant source). Therefore, a bug of severity serious is
appropriate in my opinion.

A simple way out of this mess would be adding it to the debian
directory. That's still not nice as that prevents running autoreconf and
that prevents us from using dh_auto_configure, but it solves the rc-ness
part.

Another solution could be adding the macro to the libfcgi-dev binary
package and adding it as an (unused) build dependency. Doing so would
ensure that the source code for configure is available in the archive.

A better solution would likely be solving #841078 although doing so is
more involved.

Helmut
--- End Message ---
--- Begin Message ---
Source: libfcgi-perl
Source-Version: 0.79+ds-1
Done: gregor herrmann 

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

Debian distribution maintenance software
pp.
gregor herrmann  (supplier of updated libfcgi-perl package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 17 Jan 2021 17:25:44 +0100
Source: libfcgi-perl
Architecture: source
Version: 0.79+ds-1
Distribution: experimental
Urgency: medium
Maintainer: Debian Perl Group 
Changed-By: gregor herrmann 
Closes: 841078 971368
Changes:
 libfcgi-perl (0.79+ds-1) experimental; urgency=medium
 .
   * Team upload.
 .
   [ Debian Janitor ]
   * Update standards version to 4.5.0, no changes needed.
 .
   [ gregor herrmann ]
   * Update 'DEB_BUILD_MAINT_OPTIONS = hardening=+bindnow' to '=+all'.
 .
   [ Debian Janitor ]
   * Apply multi-arch hints.
 .
   [ gregor herrmann ]
   * Add repacking framework to get rid of embedded libfcgi files.
 (Closes: #971368)
   * Import upstream version 0.79+ds.
   * Drop CVE-2012-6687.patch which patched a now removed file.
   * debian/copyright: remove stanza about excluded file.
   * Build against the system libfcgi.
 Build-depend on libfcgi-dev, and tell Makefile.PL to use the system
 version. (Closes: #841078)
   * Declare compliance with Debian Policy 4.5.1.
   * Set Rules-Requires-Root: no.
   * Bump debhelper-compat to 13.
   * Upload to experimental to get some more testing.
Checksums-Sha1:
 b2d1c2f7232629c811c5575729a7681023f175ef 2326 libfcgi-perl_0.79+ds-1.dsc
 179d1a8ad58c9e288da832647005dac003fdfe1e 15760 libfcgi-perl_0.79+ds.orig.tar.xz
 a3c143d0af004c95917348fe1b51eeef9da5126b 5512 
libfcgi-perl_0.79+ds-1.debian.tar.xz
Checksums-Sha256:
 2a90b1d076ace393df0a6093fb98771cb6a8cc5af4fde378469a6a957c5d6804 2326 
libfcgi-perl_0.79+ds-1.dsc
 b2a9ebca6d6499c05ec098ff5a68a639d7e5701c2a9d7d623dd6dc8052500375 15760 
libfcgi-perl_0.79+ds.orig.tar.xz
 533841570f13c1bc4eb8e0882f9a314c25eb6cb38e61ca0dfcbfeb5468d4288b 5512 
libfcgi-perl_0.79+ds-1.debian.tar.xz
Files:
 624cc0b626df2841aad5103f32c0b91b 2326 perl optional libfcgi-perl_0.79+ds-1.dsc
 30307ac4e5bb6f90d97ceb3e69cc5415 15760 perl optional 
libfcgi-perl_0.79+ds.orig.tar.xz
 301558f135f5a513a73b7f4ceaf3ebac 5512 perl optional 
libfcgi-perl_0.79+ds-1.debian.tar.xz

-BEGIN PGP SIGNATURE-

Bug#977064: marked as done (flask-gravatar FTBFS with pytest 6)

[Debian Bug Tracking System]

Your message dated Sun, 17 Jan 2021 17:07:42 +
with message-id 
and subject line Bug#977064: fixed in pytest-pep8 1.0.6-3
has caused the Debian Bug report #977064,
regarding flask-gravatar FTBFS with pytest 6
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.)


-- 
977064: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977064
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: flask-gravatar
Version: 0.4.2-2
Severity: important
User: pyt...@packages.debian.org
Usertags: pytest-v6

Hi,

flask-gravatar FTBFS with pytest 6 in experimental because it uses a
deprecated feature that will be removed soon, and that, by default,
considered an error in pytest 6.

The error log below has more details.

> I: pybuild base:232: cd 
> /<>/.pybuild/cpython3_3.9_flask-gravatar/build; python3.9 -m 
> pytest tests
> Coverage.py warning: No data was collected. (no-data-collected)
> = test session starts 
> ==
> platform linux -- Python 3.9.1, pytest-6.0.2, py-1.9.0, pluggy-0.13.0
> rootdir: /<>, configfile: pytest.ini
> plugins: pep8-1.0.6, cov-2.8.1
> collected 0 items / 1 error
> 
>  ERRORS 
> 
>  ERROR collecting test session 
> _
> /usr/lib/python3/dist-packages/pluggy/hooks.py:286: in __call__
> return self._hookexec(self, self.get_hookimpls(), kwargs)
> /usr/lib/python3/dist-packages/pluggy/manager.py:92: in _hookexec
> return self._inner_hookexec(hook, methods, kwargs)
> /usr/lib/python3/dist-packages/pluggy/manager.py:83: in 
> self._inner_hookexec = lambda hook, methods, kwargs: hook.multicall(
> /usr/lib/python3/dist-packages/pytest_pep8.py:38: in pytest_collect_file
> return Pep8Item(path, parent, pep8ignore, config._max_line_length)
> /usr/lib/python3/dist-packages/_pytest/nodes.py:95: in __call__
> warnings.warn(NODE_USE_FROM_PARENT.format(name=self.__name__), 
> stacklevel=2)
> E   pytest.PytestDeprecationWarning: Direct construction of Pep8Item has been 
> deprecated, please use Pep8Item.from_parent.
> E   See 
> https://docs.pytest.org/en/stable/deprecations.html#node-construction-changed-to-node-from-parent
>  for more details.
> 
> --- coverage: platform linux, python 3.9.1-final-0 ---
> Name Stmts   Miss  Cover   Missing
> --
> flask_gravatar/__init__.py  54 54 0%   13-135
> flask_gravatar/version.py2  2 0%   10-19
> --
> TOTAL   56 56 0%
> 
> === short test summary info 
> 
> ERROR ../../.. - pytest.PytestDeprecationWarning: Direct construction of 
> Pep8...
>  Interrupted: 1 error during collection 
> 
> === 1 error in 0.07s 
> ===
> E: pybuild pybuild:353: test: plugin distutils failed with: exit code=2: cd 
> /<>/.pybuild/cpython3_3.9_flask-gravatar/build; python3.9 -m 
> pytest tests
> dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.9 
> returned exit code 13
> make: *** [debian/rules:7: build] Error 25
> dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2
--- End Message ---
--- Begin Message ---
Source: pytest-pep8
Source-Version: 1.0.6-3
Done: Ondřej Nový 

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

Debian distribution maintenance software
pp.
Ondřej Nový  (supplier of updated pytest-pep8 package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 17 Jan 2021 17:29:19 +0100
Source: pytest-pep8
Architecture: source
Version: 1.0.6-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team 
Changed-By: Ondřej Nový 
Closes: 977064
Changes:
 pytest-pep8 (1.0.6-3) unstable; urgency=medium

Bug#977085: marked as done (python-crontab FTBFS with pytest 6)

[Debian Bug Tracking System]

Your message dated Sun, 17 Jan 2021 18:01:52 +0100
with message-id 

and subject line Can't reproduce
has caused the Debian Bug report #977085,
regarding python-crontab FTBFS with pytest 6
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.)


-- 
977085: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977085
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-crontab
Version: 2.5.1-1
Severity: important
User: pyt...@packages.debian.org
Usertags: pytest-v6

Hi,


python-crontab FTBFS with pytest 6 in experimental. The pytest changelog
may offer clues as to why:

https://docs.pytest.org/en/stable/changelog.html


The error log below has more details.

> I: pybuild base:232: python3.9 -m pytest
> = test session starts 
> ==
> platform linux -- Python 3.9.1, pytest-6.0.2, py-1.9.0, pluggy-0.13.0
> rootdir: /<>
> collected 170 items
> 
> tests/test_compatibility.py s[  
> 5%]
> tests/test_context.py .  [  
> 5%]
> tests/test_croniter.py . [  
> 8%]
> tests/test_crontabs.py . [ 
> 11%]
> tests/test_description.py ss [ 
> 12%]
> tests/test_enums.py  [ 
> 17%]
> tests/test_env.py ...[ 
> 24%]
> tests/test_equality.py   [ 
> 26%]
> tests/test_every.py .[ 
> 31%]
> tests/test_frequency.py .[ 
> 41%]
> tests/test_interaction.py ...[ 
> 60%]
> tests/test_log.py ...[ 
> 64%]
> tests/test_range.py  [ 
> 68%]
> tests/test_removal.py    [ 
> 75%]
> tests/test_scheduler.py ...F.[ 
> 78%]
> tests/test_system_cron.py .. [ 
> 84%]
> tests/test_usage.py ..   [ 
> 95%]
> tests/test_utf8.py   
> [100%]
> 
> === FAILURES 
> ===
>  SchedulerTestCase.test_04_schedule_ten 
> 
> 
> self =  testMethod=test_04_schedule_ten>
> 
> def test_04_schedule_ten(self):
> """Every Ten Minutes"""
>>   self.assertSchedule("*/10 * * * *", 12, 1)
> 
> tests/test_scheduler.py:104: 
> _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
> _ 
> tests/test_scheduler.py:82: in assertSchedule
> self.assertEqual(len(ret), result)
> E   AssertionError: 2 != 1
> === warnings summary 
> ===
> tests/test_compatibility.py:111
>   /<>/tests/test_compatibility.py:111: DeprecationWarning: 
> invalid escape sequence \#
> cron = crontab.CronTab(tab="""
> 
> :111
> :111
>   :111: DeprecationWarning: invalid escape sequence \#
> 
> tests/test_interaction.py:51
>   /<>/tests/test_interaction.py:51: DeprecationWarning: invalid 
> escape sequence \%
> RESULT_TAB = """# First Comment
> 
> :51
>   :51: DeprecationWarning: invalid escape sequence \%
> 
> -- Docs: https://docs.pytest.org/en/stable/warnings.html
> === short test summary info 
> 
> FAILED tests/test_scheduler.py::SchedulerTestCase::test_04_schedule_ten - 
> Ass...
> = 1 failed, 166 passed, 3 skipped, 5 warnings in 0.92s 
> =
> E: pybuild pybuild:353: test: plugin custom failed with: exit code=1: 
> python3.9 -m pytest
> dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.9 
> returned exit code 13
> make[1]: *** [debian/rules:9: override_dh_auto_test] Error 25
> make: *** [debian/rules:6: binary] Error 2
> dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 
> 2
> make[1]: Leaving directory '/<>'
--- End Message ---
--- Begin Message ---
Can't reproduce this, probably just a flaky test and looks unrelated to
pytest 6 upgrade.

-- 
Best regards
 Ondřej Nový
--- End Message ---

Processed: Bug#971368 marked as pending in libfcgi-perl

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #971368 [src:libfcgi-perl] libfcgi-perl: missing source for 
FCGI_COMMON_CHECKS
Added tag(s) pending.

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

Bug#971368: marked as pending in libfcgi-perl

[gregor herrmann]

Control: tag -1 pending

Hello,

Bug #971368 in libfcgi-perl reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:

https://salsa.debian.org/perl-team/modules/packages/libfcgi-perl/-/commit/80ec29996698e9f8ed55cb45f99854ef1bb27745


Add repacking framework to get rid of embedded libfcgi files.

Closes: #971368


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/971368

Bug#971368: libfcgi-perl: missing source for FCGI_COMMON_CHECKS

[gregor herrmann]

On Tue, 29 Sep 2020 17:16:07 +0200, gregor herrmann wrote:

> On Tue, 29 Sep 2020 15:09:09 +0200, Helmut Grohne wrote:

> > A better solution would likely be solving #841078 although doing so is
> > more involved.
> 
> Actually, I believe this would be as simple as updating libfcgi from
> 2.4.0 to 2.4.2; at least a quick look at the newer version and a diff
> against the files included in libfcgi-perl show hardly any difference
> (and the FCGX_Attach/Detach functions are included there).
> 
> Then libfcgi-perl only needs a repackage, a build dependency, and a
> parameter to perl Makefile.PL - at least from a quick look.
> 
> Cloning a wishlist bug against libfcgi …

And libfcgi 2.4.2 is now in unstable and testing.

I've made the above mentioned changes to libfcgi-perl, and the binary
package gets a dependency on libfcgi0ldbl and the test.pl works
(which it doesn't when building against libfcgi in stable because of
the missing attach/detach functions).

So I think this looks all pretty good.
I've uploaded libfcgi-perl to experimental for the time being, and
I'd appreciate tests or reviews before I upload to unstable.


Cheers,
gregor

-- 
 .''`.  https://info.comodo.priv.at -- Debian Developer https://www.debian.org
 : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D  85FA BB3A 6801 8649 AA06
 `. `'  Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe
   `-   NP: Leonard Cohen: Show Me The Place


signature.asc
Description: Digital Signature

Processed: Bug#977064 marked as pending in pytest-pep8

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #977064 [pytest-pep8] flask-gravatar FTBFS with pytest 6
Added tag(s) pending.

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

Bug#977064: marked as pending in pytest-pep8

[Ondřej Nový]

Control: tag -1 pending

Hello,

Bug #977064 in pytest-pep8 reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:

https://salsa.debian.org/python-team/packages/pytest-pep8/-/commit/4b4849a0d1c2f9526f6a2f80240a46db387ebf5e


Fix pytest 6 compatibility (Closes: #977064).


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/977064

Processed: opam: trying to overwrite '/usr/share/doc/opam-installer/README.md.gz', which is also in package opam-installer 2.0.5-1

[Debian Bug Tracking System]

Processing control commands:

> affects -1 opam-installer
Bug #980309 [opam] opam: trying to overwrite 
'/usr/share/doc/opam-installer/README.md.gz', which is also in package 
opam-installer 2.0.5-1
Added indication that 980309 affects opam-installer

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

Bug#980309: opam: trying to overwrite '/usr/share/doc/opam-installer/README.md.gz', which is also in package opam-installer 2.0.5-1

[Adrian Bunk]

Package: opam
Version: 2.0.7-1
Severity: serious
Control: affects -1 opam-installer

Unpacking opam (2.0.7-1) over (2.0.5-1) ...
dpkg: error processing archive 
/tmp/apt-dpkg-install-8hvj8T/08-opam_2.0.7-1_amd64.deb (--unpack):
 trying to overwrite '/usr/share/doc/opam-installer/README.md.gz', which is 
also in package opam-installer 2.0.5-1

Bug#978280: marked as done (sunpy: FTBFS: dpkg-buildpackage: error: dpkg-source -b . subprocess returned exit status 2)

[Debian Bug Tracking System]

Your message dated Sun, 17 Jan 2021 16:20:28 +
with message-id 
and subject line Bug#978280: fixed in sunpy 2.0.7-1
has caused the Debian Bug report #978280,
regarding sunpy: FTBFS: dpkg-buildpackage: error: dpkg-source -b . subprocess 
returned exit status 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.)


-- 
978280: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=978280
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: sunpy
Version: 2.0.5-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201226 ftbfs-bullseye

Hi,

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

Relevant part (hopefully):
> dpkg-buildpackage
> -
> 
> Command: dpkg-buildpackage -us -uc -sa -rfakeroot
> dpkg-buildpackage: info: source package sunpy
> dpkg-buildpackage: info: source version 2.0.5-1
> dpkg-buildpackage: info: source distribution unstable
> dpkg-buildpackage: info: source changed by Ole Streicher 
>  dpkg-source --before-build .
> dpkg-buildpackage: info: host architecture amd64
>  debian/rules clean
> dh clean --with python3 --buildsystem=pybuild
>dh_auto_clean -O--buildsystem=pybuild
> I: pybuild base:232: python3.9 setup.py clean 
> running clean
> removing '/<>/.pybuild/cpython3_3.9_sunpy/build' (and everything 
> under it)
> 'build/bdist.linux-x86_64' does not exist -- can't clean it
> 'build/scripts-3.9' does not exist -- can't clean it
>dh_autoreconf_clean -O--buildsystem=pybuild
>dh_clean -O--buildsystem=pybuild
>  dpkg-source -b .
> dpkg-source: info: using source format '3.0 (quilt)'
> dpkg-source: info: building sunpy using existing ./sunpy_2.0.5.orig.tar.gz
> dpkg-source: info: using patch list from debian/patches/series
> dpkg-source: info: local changes detected, the modified files are:
>  sunpy-2.0.5/sunpy/_version.py
> dpkg-source: error: aborting due to unexpected upstream changes, see 
> /tmp/sunpy_2.0.5-1.diff.gRUUPR
> dpkg-source: info: you can integrate the local changes with dpkg-source 
> --commit
> dpkg-buildpackage: error: dpkg-source -b . subprocess returned exit status 2
> 
> Build finished at 2020-12-26T18:27:38Z

The full build log is available from:
   http://qa-logs.debian.net/2020/12/26/sunpy_2.0.5-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 me
so that we can identify if something relevant changed in the meantime.

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
Source: sunpy
Source-Version: 2.0.7-1
Done: Ole Streicher 

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

Debian distribution maintenance software
pp.
Ole Streicher  (supplier of updated sunpy package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 17 Jan 2021 16:53:19 +0100
Source: sunpy
Architecture: source
Version: 2.0.7-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Astronomy Team 

Changed-By: Ole Streicher 
Closes: 978280
Changes:
 sunpy (2.0.7-1) unstable; urgency=medium
 .
   * New upstream version 2.0.7
   * Push Standards-Version to 4.5.1. No changes needed
   * Rediff patches
   * Remove version.py: generated during build. Closes: #978280
Checksums-Sha1:
 0beef78515bf6ce0b0e453482cb10fd466344af6 2692 sunpy_2.0.7-1.dsc
 f545e841c9ae7049265d9813c27ac9712760cc71 8060871 sunpy_2.0.7.orig.tar.gz
 bf6fd67053f3363e7345263d745d8d81a236b315 7212 sunpy_2.0.7-1.debian.tar.xz
Checksums-Sha256:
 

Processed: reassign 977064 to pytest-pep8

[Debian Bug Tracking System]

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

> reassign 977064 pytest-pep8
Bug #977064 [src:flask-gravatar] flask-gravatar FTBFS with pytest 6
Bug reassigned from package 'src:flask-gravatar' to 'pytest-pep8'.
No longer marked as found in versions flask-gravatar/0.4.2-2.
Ignoring request to alter fixed versions of bug #977064 to the same values 
previously set
> thanks
Stopping processing here.

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

Bug#918526: mtail: FTBFS randomly

[Santiago Vila]

On Sun, Jan 17, 2021 at 03:42:30PM +, Filippo Giunchedi wrote:

> I've uploaded 3.0.0~rc41-1 yesterday with the flaky tests fixed, and indeed
> mtail built fine on all release architectures:
> 
> https://buildd.debian.org/status/package.php?p=mtail
> 
> I'm resolving the bug since I think it is fixed, of course please reopen if 
> sth is amiss!

Hi. This is still a package which FTBFS randomly in buster, the
current supported stable distribution. Would you please consider
fixing this FTBFS bug in stable, where people will still have
to deal with it?

I believe that disabling the tests completely in cases like this one,
where a failure does not mean there is something wrong, is a much
better option than doing nothing.

Thanks.

Bug#979372: marked as done (asterisk: CVE-2020-35652)

[Debian Bug Tracking System]

Your message dated Sun, 17 Jan 2021 15:48:29 +
with message-id 
and subject line Bug#979372: fixed in asterisk 1:16.15.1~dfsg-1
has caused the Debian Bug report #979372,
regarding asterisk: CVE-2020-35652
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.)


-- 
979372: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979372
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: asterisk
Version: 1:16.15.0~dfsg-1
Severity: grave
Tags: security upstream
Justification: user security hole
X-Debbugs-Cc: car...@debian.org, Debian Security Team 
Control: found -1 1:16.2.1~dfsg-1+deb10u2

Hi,

The following vulnerability was published for asterisk.

Rationale: Choosed RC severity orthogonally to a potential no-dsa
decision, but ideally it get fixed in time for the bullseye release.

CVE-2020-35652[0]:
| remote crash in res_pjsip_diversion

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-2020-35652
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-35652
[1] https://issues.asterisk.org/jira/browse/ASTERISK-29191
[2] https://issues.asterisk.org/jira/browse/ASTERISK-29219
[3] https://downloads.asterisk.org/pub/security/AST-2020-003.html
[4] https://downloads.asterisk.org/pub/security/AST-2020-004.html

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: asterisk
Source-Version: 1:16.15.1~dfsg-1
Done: Bernhard Schmidt 

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

Debian distribution maintenance software
pp.
Bernhard Schmidt  (supplier of updated asterisk package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 17 Jan 2021 15:56:22 +0100
Source: asterisk
Architecture: source
Version: 1:16.15.1~dfsg-1
Distribution: unstable
Urgency: medium
Maintainer: Debian VoIP Team 
Changed-By: Bernhard Schmidt 
Closes: 979372
Changes:
 asterisk (1:16.15.1~dfsg-1) unstable; urgency=medium
 .
   * New upstream version 16.15.1~dfsg
 - CVE-2020-35652 / AST-2020-003 + AST-2020-004 (Closes: #979372)
   Remote crash in res_pjsip_diversion
Checksums-Sha1:
 5e6bb9c59ec223cebeb9f27f6ebb3f610ae8ba0f 4201 asterisk_16.15.1~dfsg-1.dsc
 634cf576f6d8c6a6611d0f296b2eb3148ba60e76 7047652 
asterisk_16.15.1~dfsg.orig.tar.xz
 7986a9e747d87a98f4affd50c0da6c28a5c5ed52 5948884 
asterisk_16.15.1~dfsg-1.debian.tar.xz
 4984d4a2fc35d949e6c7e88d6043e6b381e5eb40 27113 
asterisk_16.15.1~dfsg-1_amd64.buildinfo
Checksums-Sha256:
 ce69265e87976eb27ac01d16b0a59d8d552e0b9d18b0857dbcbb18d142898f63 4201 
asterisk_16.15.1~dfsg-1.dsc
 fdacf454098cce11f8a1961dd51411d05a96c50ea594e64883be111f99b36287 7047652 
asterisk_16.15.1~dfsg.orig.tar.xz
 882720af13cfc62ec060189a402a8ce982704a98d4d07917860dbcf70f98e29e 5948884 
asterisk_16.15.1~dfsg-1.debian.tar.xz
 67392743a8867de9836180d3522fc2b89f97eae69e93df84458e83c4fcb57af6 27113 
asterisk_16.15.1~dfsg-1_amd64.buildinfo
Files:
 6d3ee0b8683e82d13bee3f1fda05203e 4201 comm optional asterisk_16.15.1~dfsg-1.dsc
 c11c103eca25588a7e78da0d55d76d7a 7047652 comm optional 
asterisk_16.15.1~dfsg.orig.tar.xz
 4284b89561a1b53c00ae816a6a51dcfe 5948884 comm optional 
asterisk_16.15.1~dfsg-1.debian.tar.xz
 e96c31525535130046854f0699e82aed 27113 comm optional 
asterisk_16.15.1~dfsg-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJFBAEBCgAvFiEE1uAexRal3873GVbTd1B55bhQvJMFAmAEWCARHGJlcm5pQGRl
Ymlhbi5vcmcACgkQd1B55bhQvJMSpA/8CABnClT0X1TyWGB/WWCnL6Lc6pPL2wXc
r7f6uPh3aOndfnsEqPnkAdIAIgFhcfI67ryxcVQHP+S448/HBTjBN4h87hLAZbwg
/1pKY3esujlNdzmvg6MioSZW7khzWvRlRs1zFrDsdmEuH3D1O23yoGUJI8qZG8wp
Vm/gWFuzjzwDyJ5IWH7b9ASH0LvxwbG5LpE7pPgUQDL434VckcMQN2+rBzhqo/iR
HvSyjS8P2XVbWbasF6/ajrU86eh5tXRo53krhNEGinxixyo9DwHn0eY4OdIcGJjv
vC720WgTQi/TOPheDNsfFn15/3A2jPDxe7nUdLRi0zG4wmxDp+X2vtkhlpLpakhJ
N04MG5blFNCnxh7YbWNlwzGzPbjgRSNmymk1S/FVj91HW+iVbOTCiQ0cnjmuByAk
FYwMEvsi5LberfyXwbXk4kvFGsDgANeV9Ub7xVV2SSfC6Mjt0m0U8VRNmYsVtvdf

Bug#918526: marked as done (mtail: FTBFS randomly / flaky autopkgtests)

[Debian Bug Tracking System]

Your message dated Sun, 17 Jan 2021 15:42:30 +
with message-id <20210117154230.ga11...@esaurito.net>
and subject line Re: Bug#918526: mtail: FTBFS randomly
has caused the Debian Bug report #918526,
regarding mtail: FTBFS randomly / flaky autopkgtests
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.)


-- 
918526: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918526
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:mtail
Version: 3.0.0~rc16-1
Severity: important
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster but it failed:


[...]
 debian/rules build-arch
dh build-arch --buildsystem=golang --with=golang 
--builddirectory=/<>/build
   dh_update_autotools_config -a -O--buildsystem=golang 
-O--builddirectory=/<>/mtail-3.0.0\~rc16/build
   dh_autoreconf -a -O--buildsystem=golang 
-O--builddirectory=/<>/mtail-3.0.0\~rc16/build
   dh_auto_configure -a -O--buildsystem=golang 
-O--builddirectory=/<>/mtail-3.0.0\~rc16/build
   debian/rules override_dh_auto_build
make[1]: Entering directory '/<>'
dh_auto_build -- -ldflags " -X main.Version=3.0.0~rc16 -X 
main.Revision=3.0.0~rc16-1"
cd build && go generate -v -ldflags " -X main.Version=3.0.0~rc16 -X 
main.Revision=3.0.0~rc16-1" github.com/google/mtail 
github.com/google/mtail/exporter github.com/google/mtail/logline 
github.com/google/mtail/metrics github.com/google/mtail/metrics/datum 
github.com/google/mtail/mtail github.com/google/mtail/tailer 
github.com/google/mtail/tailer/file github.com/google/mtail/testutil 
github.com/google/mtail/vm github.com/google/mtail/watcher
src/github.com/google/mtail/bench_test.go
src/github.com/google/mtail/ex_test.go
src/github.com/google/mtail/main.go
src/github.com/google/mtail/exporter/collectd.go
src/github.com/google/mtail/exporter/export.go

[... snipped ...]

--- PASS: TestInstrs/cmp_ge (0.00s)
--- PASS: TestInstrs/cmp_eq_string_string_true (0.00s)
--- PASS: TestInstrs/cmp_eq_string_string_false (0.00s)
--- PASS: TestInstrs/cmp_gt_int_float (0.00s)
--- PASS: TestInstrs/cmp_gt_float_float (0.00s)
--- PASS: TestInstrs/cmp_gt (0.00s)
--- PASS: TestInstrs/cmp_gt_float_int (0.00s)
--- PASS: TestInstrs/cmp_ne (0.00s)
--- PASS: TestInstrs/cmp_le (0.00s)
--- PASS: TestInstrs/cmp_eq (0.00s)
--- PASS: TestInstrs/cmp_lt (0.00s)
=== RUN   TestDatumSetInstrs
--- PASS: TestDatumSetInstrs (0.00s)
=== RUN   TestStrptimeWithTimezone
--- PASS: TestStrptimeWithTimezone (0.00s)
=== RUN   TestStrptimeWithoutTimezone
--- PASS: TestStrptimeWithoutTimezone (0.00s)
=== RUN   TestDatumFetchInstrs
--- PASS: TestDatumFetchInstrs (0.00s)
=== RUN   TestWalkPanicsOnUnknown
--- PASS: TestWalkPanicsOnUnknown (0.00s)
PASS
ok  github.com/google/mtail/vm  0.098s
=== RUN   TestFakeWatcher
--- PASS: TestFakeWatcher (0.00s)
=== RUN   TestFakeWatcherUnwatchedFiles
--- PASS: TestFakeWatcherUnwatchedFiles (0.00s)
=== RUN   TestNoSuchHandle
--- PASS: TestNoSuchHandle (0.00s)
=== RUN   TestLogWatcher
--- PASS: TestLogWatcher (0.00s)
=== RUN   TestNewLogWatcherError
--- PASS: TestNewLogWatcherError (0.00s)
=== RUN   TestLogWatcherAddError
--- PASS: TestLogWatcherAddError (0.00s)
=== RUN   TestLogWatcherAddWhilePermissionDenied
--- PASS: TestLogWatcherAddWhilePermissionDenied (0.00s)
=== RUN   TestWatcherErrors
E1208 18:50:34.156489   32599 log_watcher.go:85] fsnotify error: Injected error 
for test
--- PASS: TestWatcherErrors (0.00s)
PASS
ok  github.com/google/mtail/watcher 0.013s
dh_auto_test: cd build && go test -vet=off -v -p 2 github.com/google/mtail 
github.com/google/mtail/exporter github.com/google/mtail/logline 
github.com/google/mtail/metrics github.com/google/mtail/metrics/datum 
github.com/google/mtail/mtail github.com/google/mtail/tailer 
github.com/google/mtail/tailer/file github.com/google/mtail/testutil 
github.com/google/mtail/vm github.com/google/mtail/watcher returned exit code 1
make[1]: *** [debian/rules:25: override_dh_auto_test] Error 1
make[1]: Leaving directory '/<>'
make: *** [debian/rules:18: build-arch] Error 2
dpkg-buildpackage: error: debian/rules build-arch subprocess returned exit 
status 2


This is just how the build ends and not necessarily the most relevant part,
so I've put a bunch of my build logs here:

https://people.debian.org/~sanvila/build-logs/mtail/

The test which usually fails for me is this one:

FAILgithub.com/google/mtail/tailer  0.018s

Bug#979537: marked as done (pipewire occupies devices preventing driver unbinding)

[Debian Bug Tracking System]

Your message dated Sun, 17 Jan 2021 15:09:40 +
with message-id 
and subject line Bug#979537: fixed in pipewire 0.3.19-1
has caused the Debian Bug report #979537,
regarding pipewire occupies devices preventing driver unbinding
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.)


-- 
979537: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979537
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: pipewire
Version: 0.3.15-1
Severity: serious
Tags: upstream patch
Justification: makes unrelated software on the system break
X-Debbugs-Cc: schmid...@gmx.de

Dear Maintainer,

Im suffering from the same Upstream Bug 
https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/369 (fixed)

> I have a VM where I tend to assign/bind a graphics card using VFIO/OVMF and 
> it stopped working after the move (completely freezes libvirtd when I tried 
> booting). After fair amount of debugging I realized that stopping pipewire 
> fixes this problem. 

-- System Information:
Debian Release: bullseye/sid
  APT prefers testing
  APT policy: (990, 'testing'), (490, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.9.0-5-amd64 (SMP w/4 CPU threads)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_GB:en_US
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages pipewire depends on:
ii  init-system-helpers  1.60
ii  libpipewire-0.3-modules  0.3.15-1
ii  pipewire-bin 0.3.15-1

pipewire recommends no packages.

pipewire suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: pipewire
Source-Version: 0.3.19-1
Done: Simon McVittie 

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 979...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Simon McVittie  (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: SHA256

Format: 1.8
Date: Sun, 17 Jan 2021 13:38:28 +
Source: pipewire
Architecture: source
Version: 0.3.19-1
Distribution: unstable
Urgency: medium
Maintainer: Utopia Maintenance Team 

Changed-By: Simon McVittie 
Closes: 976654 979309 979537 979791
Changes:
 pipewire (0.3.19-1) unstable; urgency=medium
 .
   * Team upload
   * New upstream release (Closes: #979309)
 - Fix cleanup of acp card objects (Closes: #979537)
 - Provide pipewire-pulse, pipewire's replacement for the PulseAudio
   daemon (Closes: #976654). Note that this is not enabled by default
   for bullseye. systemd user units to start it can be found in
   /usr/share/doc/pipewire/examples/systemd/user.
   * Drop patch, applied upstream
   * Remove pw-pulse from pipewire-audio-client-libraries, no longer
 supported upstream
   * Fix installation path for example 99-pipewire-default.conf
   * Install example ld.so.conf.d fragments into
 /usr/share/doc/pipewire/examples/ld.so.conf.d to replace libjack with
 Pipewire as suggested by upstream. These can be copied into
 /etc/ld.so.conf.d if desired. This is not done by default and is
 considered to be experimental
   * Add Build-Conflicts with non-free libfdk-aac-dev.
 This makes the build more predictable by not compiling a plugin that
 would depend on that library.
   * d/control: Add new dependencies for Bluetooth codecs
   * Build-depend on libncurses-dev for the new pw-top utility
   * d/copyright: Update
   * d/pipewire-bin.install: Install pw-dump and pw-top
   * Don't automatically start pipewire for root logins (Closes: #979791)
   * Standards-Version: 4.5.1 (no changes required)
   * Update symbols file
   * Remove unnecessary RUNPATH from bluez5 plugin (workaround for #980297)
   * Silence library-not-linked-against-libc lintian error for JACK
 libraries.
 These libraries genuinely don't directly need anything from glibc.
Checksums-Sha1:
 b02da89cb57975924eaeda01e460cb391976506a 3601 

Processed: Re: tpm2-abrmd: Daemon fails to start: needs to be rebuilt against newer libtss2-esys0

[Debian Bug Tracking System]

Processing control commands:

> notfound -1 tpm2-abrmd/2.3.3-1
Bug #972118 {Done: Ying-Chun Liu (PaulLiu) } [tpm2-abrmd] 
tpm2-abrmd: Daemon fails to start: needs to be rebuilt against newer 
libtss2-esys0
No longer marked as found in versions tpm2-abrmd/2.3.3-1.
> notfixed -1 tpm2-abrmd/2.3.3-1+b1
Bug #972118 {Done: Ying-Chun Liu (PaulLiu) } [tpm2-abrmd] 
tpm2-abrmd: Daemon fails to start: needs to be rebuilt against newer 
libtss2-esys0
The source tpm2-abrmd and version 2.3.3-1+b1 do not appear to match any binary 
packages
Ignoring request to alter fixed versions of bug #972118 to the same values 
previously set

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

Bug#972118: tpm2-abrmd: Daemon fails to start: needs to be rebuilt against newer libtss2-esys0

[Juhani Numminen]

Control: notfound -1 tpm2-abrmd/2.3.3-1
Control: notfixed -1 tpm2-abrmd/2.3.3-1+b1

Juhani Numminen kirjoitti 17.1.2021 klo 16.36:
> Control: fixed -1 2.3.3-1
> 
> For version tracking, mark this version fixed because the system
> considers current version of source package to be 2.3.3-1.

Possibly that first command did not achieve the desired result.
I'll try again.

Processed: Re: libsrtp2: FTBFS: running cipher self-test for AES-128 GCM using NSS...failed with error code 8

[Debian Bug Tracking System]

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

> tags 963363 -patch
Bug #963363 [src:libsrtp2] libsrtp2: FTBFS: running cipher self-test for 
AES-128 GCM using NSS...failed with error code 8
Removed tag(s) patch.
> stop
Stopping processing here.

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

Processed: Bug#980294: libjs-jquery-flot: breaking API change

[Debian Bug Tracking System]

Processing control commands:

> retitle -1 libjs-jquery-flot: breaking API change
Bug #980291 [libjs-jquery-flot] libjs-jquery-flot: version 4.2.1+dfsg-2 drops 
minified files
Changed Bug title to 'libjs-jquery-flot: breaking API change' from 
'libjs-jquery-flot: version 4.2.1+dfsg-2 drops minified files'.
> severity -1 serious
Bug #980291 [libjs-jquery-flot] libjs-jquery-flot: breaking API change
Severity set to 'serious' from 'important'

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

Processed: Re: libsrtp2: FTBFS: running cipher self-test for AES-128 GCM using NSS...failed with error code 8

[Debian Bug Tracking System]

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

> unmerge 963363
Bug #963363 {Done: Jonas Smedegaard } [src:libsrtp2] libsrtp2: 
FTBFS: running cipher self-test for AES-128 GCM using NSS...failed with error 
code 8
Bug #957480 {Done: Jonas Smedegaard } [src:libsrtp2] libsrtp2: 
FTBFS: running cipher self-test for AES-128 GCM using NSS...failed with error 
code 8
Disconnected #963363 from all other report(s).
> notfound 963363 2.3.0-2
Bug #963363 {Done: Jonas Smedegaard } [src:libsrtp2] libsrtp2: 
FTBFS: running cipher self-test for AES-128 GCM using NSS...failed with error 
code 8
No longer marked as found in versions libsrtp2/2.3.0-2.
> notfixed 963363 2.3.0-3
Bug #963363 {Done: Jonas Smedegaard } [src:libsrtp2] libsrtp2: 
FTBFS: running cipher self-test for AES-128 GCM using NSS...failed with error 
code 8
No longer marked as fixed in versions 2.3.0-3.
> found963363 2.3.0-4
Bug #963363 {Done: Jonas Smedegaard } [src:libsrtp2] libsrtp2: 
FTBFS: running cipher self-test for AES-128 GCM using NSS...failed with error 
code 8
Did not alter found versions and reopened.
> notfound 957480 2.3.0-4
Bug #957480 {Done: Jonas Smedegaard } [src:libsrtp2] libsrtp2: 
FTBFS: running cipher self-test for AES-128 GCM using NSS...failed with error 
code 8
No longer marked as found in versions libsrtp2/2.3.0-4.
> retitle  957480 libsrtp2: ftbfs with GCC-10
Bug #957480 {Done: Jonas Smedegaard } [src:libsrtp2] libsrtp2: 
FTBFS: running cipher self-test for AES-128 GCM using NSS...failed with error 
code 8
Changed Bug title to 'libsrtp2: ftbfs with GCC-10' from 'libsrtp2: FTBFS: 
running cipher self-test for AES-128 GCM using NSS...failed with error code 8'.
> thanks
Stopping processing here.

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

Bug#963363: libsrtp2: FTBFS: running cipher self-test for AES-128 GCM using NSS...failed with error code 8

[Juhani Numminen]

unmerge 963363
notfound 963363 2.3.0-2
notfixed 963363 2.3.0-3
found963363 2.3.0-4

notfound 957480 2.3.0-4
retitle  957480 libsrtp2: ftbfs with GCC-10

thanks

On Fri, 25 Dec 2020 22:16:35 +0100 Jonas Smedegaard  wrote:

> Yes, evidently it does: I applied that patch since release 2.3.0-3 and 
> it built fine - I simply forgot to close this bugreport.

Dear Jonas,

because https://tracker.debian.org/pkg/libsrtp2 reports an FTBFS during
reproducibility testing, I'd like to separate the two bug reports.

In other words, I think that "FTBFS: running cipher self-test for
AES-128 GCM using NSS...failed with error code 8" is still relevant.

--
Juhani

Bug#976097: marked as done (postorius: autopkgtest failure)

[Debian Bug Tracking System]

Your message dated Sun, 17 Jan 2021 14:46:25 +
with message-id 
and subject line Bug#976097: fixed in postorius 1.3.3-1
has caused the Debian Bug report #976097,
regarding postorius: autopkgtest failure
to be marked as done.

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

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


-- 
976097: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976097
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:postorius
Version: 1.3.2-2.1
Severity: serious
Tags: sid bullseye

python3-django-postorius cannot be installed in testing. The autopkg tests pass
in unstable but fail in testing.

see https://ci.debian.net/packages/p/postorius/testing/amd64/

[...]
Updating certificates in /etc/ssl/certs...
126 added, 0 removed; done.
Setting up libpython3.8-stdlib:amd64 (3.8.6-1) ...
Setting up python3.8 (3.8.6-1) ...
Processing triggers for ca-certificates (20200601) ...
Updating certificates in /etc/ssl/certs...
0 added, 0 removed; done.
Running hooks in /etc/ca-certificates/update.d...
done.
autopkgtest: WARNING: package python3-django-postorius is not installed though
it should be
autopkgtest: WARNING: Test dependencies are unsatisfiable - calling apt install
on test deps directly for further data about failing dependencies in test logs
python3-django-postorius FAIL badpkg
blame: postorius
badpkg: Test dependencies are unsatisfiable. A common reason is that your
testbed is out of date with respect to the archive, and you need to use a
current testbed or run apt-get update or use -U.
autopkgtest [02:09:49]:  summary
python3-django-postorius FAIL badpkg
blame: postorius
badpkg: Test dependencies are unsatisfiable. A common reason is that your
testbed is out of date with respect to the archive, and you need to use a
current testbed or run apt-get update or use -U.
--- End Message ---
--- Begin Message ---
Source: postorius
Source-Version: 1.3.3-1
Done: Jonas Meurer 

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

Debian distribution maintenance software
pp.
Jonas Meurer  (supplier of updated postorius package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 17 Jan 2021 14:52:58 +0100
Source: postorius
Architecture: source
Version: 1.3.3-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Mailman Team 
Changed-By: Jonas Meurer 
Closes: 976097
Changes:
 postorius (1.3.3-1) unstable; urgency=medium
 .
   * New upstream release
   * d/control: Bump Standards-Version to 4.5.1
   * d/upstream/signing-key.asc: Re-export as minimal key
   * d/rules: Replace all glyphicons-halflings-regular font files with symlinks
 to the files from package fonts-glyphicons-halflings
   * d/tests: Fix tests, update test dependencies (Closes: #976097)
   * d/p/0002-Remove-cloudflare-dependency-from-the-frontent.patch:
 Remove cloudflare dependency from the frontend
   * d/missing-sources/popper-v1.11.0.js: Add missing popperjs source file
Checksums-Sha1:
 2ad585cade290a7c1c5af10dd819fba81d82e08e 2611 postorius_1.3.3-1.dsc
 7de51cb13ad1400f7e96a58d580297504aab236c 2704738 postorius_1.3.3.orig.tar.gz
 c21a27cc5440a4f5320ea24d5be09b6aa285bf48 833 postorius_1.3.3.orig.tar.gz.asc
 62535a29fee88bd1cf2f13998ced992e0af2dc48 118452 postorius_1.3.3-1.debian.tar.xz
 cd115bced9db18203f69b95dc539feb7fd66a16e 7822 postorius_1.3.3-1_amd64.buildinfo
Checksums-Sha256:
 5c70b1c56672262e751586ed7a05e77bb063872c4e5a13f60c7026b509b7ec1e 2611 
postorius_1.3.3-1.dsc
 8ae734509fb334566480c9503d2053b5a671abbe6b7a8a13a06e2ebade105622 2704738 
postorius_1.3.3.orig.tar.gz
 90fc54b4c8540a856ebe2685591605f334e347731b563172bd9a45dbd3ac550d 833 
postorius_1.3.3.orig.tar.gz.asc
 bff84568e447bf57c8eebbf7415f22dc5f5c4ad740b51f921f792a6cf9bc7345 118452 
postorius_1.3.3-1.debian.tar.xz
 b9c8b7c17c457d89c48e410295bbd308493f88d6ca5a1bdf59f1c284f72dbaba 7822 
postorius_1.3.3-1_amd64.buildinfo
Files:
 7989d06df7e0eca7da318ec3a150e67a 2611 python optional postorius_1.3.3-1.dsc
 7e6da4db3fe643985db5e5f0bed5b1c4 2704738 python optional 
postorius_1.3.3.orig.tar.gz
 

Processed: Re: bug fixed in openmpi 4.1.0-2

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 src:openmpi
Bug #978203 {Done: Alastair McKinstry } [src:fckit] 
fckit: FTBFS: dh_auto_test: error: cd debian/build-gfortran && make -j4 test 
ARGS\+=-j4 returned exit code 2
Bug reassigned from package 'src:fckit' to 'src:openmpi'.
No longer marked as found in versions fckit/0.9.0-4.
No longer marked as fixed in versions openmpi/4.1.0-2.
> fixed -1 openmpi/4.1.0-2
Bug #978203 {Done: Alastair McKinstry } [src:openmpi] 
fckit: FTBFS: dh_auto_test: error: cd debian/build-gfortran && make -j4 test 
ARGS\+=-j4 returned exit code 2
Marked as fixed in versions openmpi/4.1.0-2.
> affects -1 src:fckit
Bug #978203 {Done: Alastair McKinstry } [src:openmpi] 
fckit: FTBFS: dh_auto_test: error: cd debian/build-gfortran && make -j4 test 
ARGS\+=-j4 returned exit code 2
Added indication that 978203 affects src:fckit

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

Bug#978203: bug fixed in openmpi 4.1.0-2

[Juhani Numminen]

Control: reassign -1 src:openmpi
Control: fixed -1 openmpi/4.1.0-2
Control: affects -1 src:fckit

On Sun, 27 Dec 2020 21:48:47 +0100 Lucas Nussbaum  wrote:
> Hi,
> 
> This failure was caused by a bug in openmpi , fixed in openmpi 4.1.0-2.
> so I'm closing this bug.
> 
> Lucas

The bug was left lingering in the cleaner view in https://udd.debian.org/bugs/
because it was opened against one package and closed in another, I'm
trying to close it for good now.

--
Juhani

Processed: Re: tpm2-abrmd: Daemon fails to start: needs to be rebuilt against newer libtss2-esys0

[Debian Bug Tracking System]

Processing control commands:

> fixed -1 2.3.3-1
Bug #972118 {Done: Ying-Chun Liu (PaulLiu) } [tpm2-abrmd] 
tpm2-abrmd: Daemon fails to start: needs to be rebuilt against newer 
libtss2-esys0
Marked as fixed in versions tpm2-abrmd/2.3.3-1.

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

Bug#972118: tpm2-abrmd: Daemon fails to start: needs to be rebuilt against newer libtss2-esys0

[Juhani Numminen]

Control: fixed -1 2.3.3-1

For version tracking, mark this version fixed because the system
considers current version of source package to be 2.3.3-1.

Regards,
Juhani Numminen

Bug#979942: [Pkg-javascript-devel] Bug#979942: Bug#979942: Bug#979942: embedding dead code is no fix to bug for removing that same dead code

[Bastien ROUCARIES]

Le mar. 12 janv. 2021 à 21:02, Jonas Smedegaard  a écrit :
>
> Quoting Bastien ROUCARIES (2021-01-12 21:17:36)
> > Fixed it was a little bit hard to test options of compression one by
> > one but it work now.

Hi,

It was harder than I thought.

This time I document the requirement for this package under
https://salsa.debian.org/js-team/node-browser-pack/-/blob/master/debian/rules#L13

And I think I have suffisantly documented the bandaid method in case
of future problems

Could you confirm I am clear ?

Bastien
>
> Great!  Thanks!
>
>  - Jonas
>
> --
>  * Jonas Smedegaard - idealist & Internet-arkitekt
>  * Tlf.: +45 40843136  Website: http://dr.jones.dk/
>
>  [x] quote me freely  [ ] ask before reusing  [ ] keep private

Bug#969907: libpoppler-glib8: introduces new ABI without bumping shlibs version

[Francesco Poli]

Hello,
I wonder what's the status of [this bug].
Is there any progress?

Please let me know, thanks for your time and dedication.


[this bug]: 

-- 
 http://www.inventati.org/frx/
 There's not a second to spare! To the laboratory!
. Francesco Poli .
 GnuPG key fpr == CA01 1147 9CD2 EFDF FB82  3925 3E1C 27E1 1F69 BFFE


pgpngf2ZSVDxO.pgp
Description: PGP signature

Processed: Re: firefox-esr: after upgrade from 78.6.0esr-1~deb10u1 to 78.6.1esr-1

[Debian Bug Tracking System]

Processing control commands:

> severity -1 normal
Bug #979612 [firefox-esr] firefox-esr: after upgrade from 78.6.0esr-1~deb10u1 
to 78.6.1esr-1~deb10u1 gnome interface behave erratically
Severity set to 'normal' from 'serious'

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

Bug#979612: firefox-esr: after upgrade from 78.6.0esr-1~deb10u1 to 78.6.1esr-1

[Stefan Benter]

Package: firefox-esr
Version: 78.6.1esr-1
Control: severity -1 normal


Hi Damien,

I have upgraded 78.6.0esr-1~deb10u1 to 78.6.1esr-1~deb10u1 in bullseye 
and cannot replicate your issues.


1. Moving windows, while running 78.6.1esr-1~deb10u1 does work as expected.
2. Did not test
3. Works with thunderbird, keepassxc and gedit while running 
78.6.1esr-1~deb10u1.


the severity should therefore be modified to normal in my opinion.

The file /usr/lib/firefox-esr/browser/omni.ja is available in older 
versions as well. Unfortunately I do not know what it is for either...


Best regards,
Stefan Benter (not a maintainer)

Bug#957214: marked as done (flowgrind: ftbfs with GCC-10)

[Debian Bug Tracking System]

Your message dated Sun, 17 Jan 2021 13:34:34 +
with message-id 
and subject line Bug#957214: fixed in flowgrind 0.8.2-2
has caused the Debian Bug report #957214,
regarding flowgrind: ftbfs with GCC-10
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.)


-- 
957214: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957214
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:flowgrind
Version: 0.8.0-1
Severity: normal
Tags: sid bullseye
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-10

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-10/g++-10, but succeeds to build with gcc-9/g++-9. The
severity of this report will be raised before the bullseye release,
so nothing has to be done for the buster release.

The full build log can be found at:
http://people.debian.org/~doko/logs/gcc10-20200225/flowgrind_0.8.0-1_unstable_gcc10.log
The last lines of the build log are at the end of this report.

To build with GCC 10, either set CC=gcc-10 CXX=g++-10 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-10/porting_to.html

[...]
src/fg_rpc_client.c:51:21: note: did you mean to dereference the pointer?
   51 | if (sepptr != '\0' && *sepptr == ':')
  | ^
cc -DHAVE_CONFIG_H -I. -I./src-Wall -Wextra -Werror=implicit -std=gnu99 
-fgnu89-inline  -I/usr/include  -I/usr/include -g -O2 -c -o 
src/flowgrind-fg_log.o `test -f 'src/fg_log.c' || echo './'`src/fg_log.c
cc -DHAVE_CONFIG_H -I. -I./src-Wall -Wextra -Werror=implicit -std=gnu99 
-fgnu89-inline  -I/usr/include  -I/usr/include -g -O2 -c -o 
src/flowgrind-fg_list.o `test -f 'src/fg_list.c' || echo './'`src/fg_list.c
cc -Wall -Wextra -Werror=implicit -std=gnu99 -fgnu89-inline  -I/usr/include  
-I/usr/include -g -O2   -o flowgrind src/flowgrind-debug.o 
src/flowgrind-fg_error.o src/flowgrind-fg_progname.o src/flowgrind-fg_string.o 
src/flowgrind-fg_time.o src/flowgrind-flowgrind.o src/flowgrind-fg_argparser.o 
src/flowgrind-fg_rpc_client.o src/flowgrind-fg_log.o src/flowgrind-fg_list.o 
-luuid -lpthread -lm  -lcurl -L/usr/lib/x86_64-linux-gnu  -lxmlrpc_client 
-lxmlrpc  -lxmlrpc_xmlparse -lxmlrpc_xmltok -lxmlrpc_util -lcurl  
-L/usr/lib/x86_64-linux-gnu -lgsl -lgslcblas -lm -luuid -lpthread -lm 
cc -DHAVE_CONFIG_H -I. -I./src-Wall -Wextra -Werror=implicit -std=gnu99 
-fgnu89-inline  -I/usr/include  -g -O2 -c -o src/flowgrind_stop-fg_error.o 
`test -f 'src/fg_error.c' || echo './'`src/fg_error.c
cc -DHAVE_CONFIG_H -I. -I./src-Wall -Wextra -Werror=implicit -std=gnu99 
-fgnu89-inline  -I/usr/include  -g -O2 -c -o src/flowgrind_stop-fg_progname.o 
`test -f 'src/fg_progname.c' || echo './'`src/fg_progname.c
cc -DHAVE_CONFIG_H -I. -I./src-Wall -Wextra -Werror=implicit -std=gnu99 
-fgnu89-inline  -I/usr/include  -g -O2 -c -o 
src/flowgrind_stop-flowgrind_stop.o `test -f 'src/flowgrind_stop.c' || echo 
'./'`src/flowgrind_stop.c
cc -DHAVE_CONFIG_H -I. -I./src-Wall -Wextra -Werror=implicit -std=gnu99 
-fgnu89-inline  -I/usr/include  -g -O2 -c -o src/flowgrind_stop-fg_argparser.o 
`test -f 'src/fg_argparser.c' || echo './'`src/fg_argparser.c
cc -DHAVE_CONFIG_H -I. -I./src-Wall -Wextra -Werror=implicit -std=gnu99 
-fgnu89-inline  -I/usr/include  -g -O2 -c -o src/flowgrind_stop-fg_rpc_client.o 
`test -f 'src/fg_rpc_client.c' || echo './'`src/fg_rpc_client.c
src/fg_rpc_client.c: In function ‘parse_rpc_address’:
src/fg_rpc_client.c:51:28: warning: comparison between pointer and zero 
character constant [-Wpointer-compare]
   51 | if (sepptr != '\0' && *sepptr == ':')
  |^~
src/fg_rpc_client.c:51:21: note: did you mean to dereference the pointer?
   51 | if (sepptr != '\0' && *sepptr == ':')
  | ^
cc -Wall -Wextra -Werror=implicit -std=gnu99 -fgnu89-inline  -I/usr/include  -g 
-O2   -o flowgrind-stop src/flowgrind_stop-fg_error.o 
src/flowgrind_stop-fg_progname.o src/flowgrind_stop-flowgrind_stop.o 

Bug#975853: marked as done (opam: FTBFS: grep: opam.install: No such file or directory)

[Debian Bug Tracking System]

Your message dated Sun, 17 Jan 2021 11:48:28 +
with message-id 
and subject line Bug#975853: fixed in opam 2.0.7-1
has caused the Debian Bug report #975853,
regarding opam: FTBFS: grep: opam.install: No such file or directory
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.)


-- 
975853: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=975853
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: opam
Version: 2.0.5-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201125 ftbfs-bullseye

Hi,

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

Relevant part (hopefully):
> make[2]: Entering directory '/<>/doc'
> Entering directory '/<>'
> Entering directory '/<>'
> rm -rf man
> mkdir -p man
> dune exec --profile=release -- opam --help=groff > man/opam.1 2> man/err
> for i in help admin clean lint source unpin pin switch remote repository env 
> exec var config upgrade update reinstall uninstall remove install info show 
> search list init; do\
>   dune exec --profile=release -- opam $i --help=groff > man/opam-$i.1 2>> 
> man/err ; \
> done
> dune exec --profile=release -- opam admin --help=groff > man/opam-admin.1 2>> 
> man/err
> for i in cache filter index lint list upgrade; do\
>   dune exec --profile=release -- opam admin $i --help=groff > 
> man/opam-admin-$i.1 2>> man/err ; \
> done
> dune exec --profile=release -- opam-installer --help=groff > 
> man/opam-installer.1 2>> man/err
> make[2]: Leaving directory '/<>/doc'
> grep: opam.install: No such file or directory
> make[1]: *** [Makefile:111: opam-actual.install] Error 2

The full build log is available from:
   http://qa-logs.debian.net/2020/11/25/opam_2.0.5-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!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
Source: opam
Source-Version: 2.0.7-1
Done: Mehdi Dogguy 

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

Debian distribution maintenance software
pp.
Mehdi Dogguy  (supplier of updated opam package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 17 Jan 2021 11:00:31 +0100
Source: opam
Architecture: source
Version: 2.0.7-1
Distribution: unstable
Urgency: medium
Maintainer: Debian OCaml Maintainers 
Changed-By: Mehdi Dogguy 
Closes: 975853
Changes:
 opam (2.0.7-1) unstable; urgency=medium
 .
   * New minor upstream release (Closes: #975853)
   * Bump Build-Depend on libopam-file-format-ocaml-dev to (>= 2.1.2-2~)
   * Update opam{,-installer}.install files following changes made upstream
Checksums-Sha1:
 92f02970ec3093f7d812e5997571b213b3e5e2ec 2595 opam_2.0.7-1.dsc
 88a54e9982c607f98715e405e63973493cbff65a 628783 opam_2.0.7.orig.tar.gz
 5f55945bd8cea6bfbab44417703c77b91d7ccd7d 8640 opam_2.0.7-1.debian.tar.xz
 c52bde5fdb113a905351170a6ee02dd7c29eb2d8 8230 opam_2.0.7-1_source.buildinfo
Checksums-Sha256:
 27fafd1acdccd9df78d8a61d5a217cae2469d6f23dbbbc6a6793071e35ca43f2 2595 
opam_2.0.7-1.dsc
 afdaabedafbf707261d1cd0109f1e7bddd57c5b48c402cc0507d2cea13cd13c4 628783 
opam_2.0.7.orig.tar.gz
 d598498fb4bc67b7c26f43ce2522cb5e86770004c448f8fe2402c40c9a09e406 8640 
opam_2.0.7-1.debian.tar.xz
 eaabff72ccd57582a7e2bf0386b99e1b1f5c828c446c8f3961bdac84cdcf732f 8230 
opam_2.0.7-1_source.buildinfo
Files:
 a43a242ab05fc90d7b6bec7ce8a4d4f1 2595 ocaml optional opam_2.0.7-1.dsc
 fe0a01ff89a83151f03010ff3443d713 628783 ocaml optional opam_2.0.7.orig.tar.gz
 7ec92db642369c282999638230f2da35 8640 ocaml optional opam_2.0.7-1.debian.tar.xz
 08207fa00a83b5003128783cfaa1b1b0 8230 ocaml optional 
opam_2.0.7-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJFBAEBCAAvFiEE/IeFmw45V03XKU7GPfRgADmhQMQFAmAEIHkRHG1laGRpQGRl

Processed: fixed 979984 in 1:1.0.0-6

[Debian Bug Tracking System]

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

> fixed 979984 1:1.0.0-6
Bug #979984 [pyzor] breaks on check with "NameError: name 'get_binary_stdin' is 
not defined"
Marked as fixed in versions pyzor/1:1.0.0-6.
> thanks
Stopping processing here.

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