Bug#970633: tt-rss: Packaging work for new upstream release 21.1

[Johannes Schauer Marin Rodrigues]

Hi Sunil,

Quoting Sunil Mohan Adapa (2021-02-04 03:17:55)
> tag 970633 + patch
> tag 932924 + patch
> thanks
> 
> Hello,
> 
> Eagerly looking forward to tt-rss being in good shape for FreedomBox in
> Bullseye, I have done the packaging work needed for uploading 21.1
> version of tt-rss. Please merge and upload the package into Debian
> unstable before the Bullseye Soft Freeze date February 12th. Since this
> is a collab-maint package, I assume it would be okay to for others to
> upload as well.
> 
> * New upstream release based on latest revision 6d8f2221 on 2021-01-29
> 11:52:21 UTC+0300.
>   - Contains security fixes for CVE-2020-25787 CVE-2020-25788
> CVE-2020-25789 (Closes: #970633).
> * Use latest version of libjs-prototype.
> * Refresh patches.
> * Ability to update to latest schema version 140.
> * Update Debian Standards Version to 4.5.1.
> * Update debhelper compatibility to 13 the latest.
> * Mark as not requiring root for rules file.
> * Add self to list of uploaders.
> * Fix various lintian warnings and info messages.
> * Document upstream changes since 19.8.
> * Add directory for caching feeds.
> * Remove the default feed to tt-rss forum to improve privacy. (Closes:
> #932924)
> * Use material design icons from Debian package.
> * Add documentation link in systemd service file.
> * Redirect stderr to journal instead of syslog.
> 
> Apart from the https://salsa.debian.org/sunilmohan/tt-rss/-/tree/master
> branch please also pull in branches
> https://salsa.debian.org/sunilmohan/tt-rss/-/tree/pristine-tar and
> https://salsa.debian.org/sunilmohan/tt-rss/-/tree/upstream along with
> the tags.
> 
> I have tested new version as follows:
> 
> - DONE: lintian does not show messages with --info --display-info --pedantic
> - DONE: SELF_URL_PATH may need a proper value.
> - DONE: Prototype JS is working fine (no change since last version)
> - DONE: Dojo is loading fine the following pages:
>   - DONE: feeds.php
>   - DONE: public.php: popup in Feeds -> Bookmarklets -> Share with TTRSS
>   - DONE: public.php: forgot password page
>   - DONE: public.php: db update page
>   - DONE: public.php: subscribe to feed page (possible dead code)
>   - DONE: installer: unused in Debian
>   - DONE: login_form.php
> - DONE: Debian configured DB works
> - DONE: Theme looks good, dark theme works
> - DONE: Upstream changes files contains changes for 21.1
> - DONE: No messages in Apache error log
> - DONE: Update service works properly, feeds are updated offline
> - DONE: Updates error log is successfully redirected to journal
> - DONE: No error messages in journal for updates
> - DONE: Material design icons are linked to properly in .deb
> - DONE: Material design icons show up in web interface properly
> - DONE: Installed DB schema version is 140
>   - DONE: Install fresh on MySQL/MariaDB
>   - DONE: Install fresh on PostgreSQL
>   - DONE: Upgraded from 19.8 on MySQL/MariaDB
>   - DONE: Upgraded from 19.8 on PostgreSQL
> - DONE: Install fresh on bare Debian works fine
> - DONE: With MySQL/MariaDB
> - DONE: With PostgreSQL
> - DONE: Upgrade from 19.8 on bare Debian work fine
>   - DONE: With MySQL
>   - DONE: With PostgreSQL
> - DONE: Default feed Tiny Tiny RSS Forum is not present by default
>   - DONE: On MySQL installation
>   - DONE: On PostgreSQL installation
>   - DONE: When a new user is created in prefs.

oh wow! Thanks a ton for all your work! This is phantastic. :)

Do you want to do the upload yourself? Just add yourself to Uploaders as well
while you are at it, you seem to know what you are doing and I'd love somebody
to help out with packaging. Feel free to just put your commits directly into
the packaging repo on salsa!

Thanks!

cheers, josch

signature.asc
Description: signature

Processed: severity of 953728 is important

[Debian Bug Tracking System]

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

> severity 953728 important
Bug #953728 [src:gambc] gambc: FTBFS on s390x
Severity set to 'important' from 'serious'
> thanks
Stopping processing here.

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

Bug#976735: spyder needs source upload for Python 3.9 transition

[Julian Gilbey]

On Mon, Feb 01, 2021 at 09:45:24PM +0530, Nilesh Patra wrote:
> Hi Julian
> I read through the rest of the thread.
> 
> On Mon, 1 Feb, 2021, 6:31 pm Julian Gilbey,  wrote:
> 
>   I have a package of Spyder 4 waiting to upload, but it requires five
>   packages to be accepted into unstable from NEW first (pyls-server,
>   pyls-black, pyls-spyder, abydos, textdistance); once that happens, the
>   rest of the packages are almost ready to
> 
>   go.
> 
> I requested on IRC (probably again after you) to process these ASAP, however I
> don't see pyls-server in NEW or at the archive yet.
> Has this been rejected, or am I missing something?
> Nilesh

It seems like you might have done some magic - they've now all been
accepted!  I should have a new version of spyder uploaded within a
couple of days.

Best wishes,

   Julian

Bug#981810: python-fabio: regression in autopkgtest tests

[Sandro Tosi]

Source: python-fabio
Version: 0.11.0+dfsg-1
Severity: serious

Hello,
autopkgtests are failing, please check the logs at:

https://ci.debian.net/data/autopkgtest/testing/amd64/p/python-fabio/10229362/log.gz

The same tests are not executed during build time, and that's why the package
builds fine (i verify that just now) but then autopkgtests fail.

Regards,
Sandro

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

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

Bug#981725: libdap-dev no longer provides dap-config

[Sebastiaan Couwenberg]

On 2/3/21 12:37 PM, Sebastiaan Couwenberg wrote:
> On 2/3/21 12:03 PM, Sebastiaan Couwenberg wrote:
>> On 2/3/21 10:48 AM, Gianfranco Costamagna wrote:
>>> Hello, the new libdap broke in some way the gdal configure script, and now 
>>> the configure step fails with:
>>>
>>> checking for libqhull/libqhull.h... yes
>>> checking for qh_new_qhull in -lqhull... no
>>> configure: error: --with-qhull requested, but library not found!
>>>
>>>
>>> I don't really understand what is going on here, looks like qhull is not 
>>> found anymore.
>>>
>>> libdap might be the library to blame here, feel free to reassign if needed
>>
>> libdap-dev no longer provides /usr/bin/dap-config, gdal configure then
>> adds dap++ to LIBS which breaks the compile test for qhull.
>>
>> dap-config should really be provided by libdap-dev instead of
>> libdap-bin. Or libdap-bin needs to be a dependency of libdap-dev.
> 
> This is also the cause of the autopkgtest failure which prevents testing
> migration:
> 
>  Test-Command: set -e
>; dap-config --help 2> /dev/null
>  Depends: libdap-dev
> 
> The attached patch should fix the issue.

The patch has been updated with the changed from -4.

To clarify the issue:

Moving dap-config* from libdap-dev to libdap-bin is wrong,
from the Debian Library Packaging guide:

"
-DEV package (e.g. libfooX-dev) should contain the development symlink
used when linking, static libraries, and header files, and if they
exist, package configuration scripts.

Table 4.1. Annotated list of files that usually reside in -DEV package

+--+
|files |meaning|
|--+---|
|usr/lib/*.so  |development linkage file, used when other  |
|  |programs are linked with -lxxx |
|--+---|
|usr/lib/*.a   |static link files  |
|--+---|
|usr/lib/*.la  |libtool linkage information file   |
|--+---|
|usr/include/* |Development include files  |
|--+---|
|usr/bin/*-config  |Some configuration script used in obtaining|
|  |the library paths, like gtk-config |
|--+-- |
|usr/lib/pkgconfig/*.pc|Some information required for pkgconfig|
+--+
"

https://www.netfort.gr.jp/~dancer/column/libpkg-guide/libpkg-guide.html#id249952

Alastair, if you won't move dap-config* back to the -dev package (e.g.
by applying the attached patch), you must add Depends: libdap-bin to
libdap-dev to have dap-config available when installing libdap-dev.

Kind Regards,

Bas

-- 
 GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146  50D1 6750 F10A E88D 4AF1
diff -Nru libdap-3.20.7/debian/changelog libdap-3.20.7/debian/changelog
--- libdap-3.20.7/debian/changelog  2021-02-03 13:27:57.0 +0100
+++ libdap-3.20.7/debian/changelog  2021-02-04 05:07:14.0 +0100
@@ -1,3 +1,11 @@
+libdap (3.20.7-5) UNRELEASED; urgency=medium
+
+  * Team upload.
+  * Move usr/bin/dap-config* back to libdap-dev.
+(closes: #981725)
+
+ -- Bas Couwenberg   Thu, 04 Feb 2021 05:07:14 +0100
+
 libdap (3.20.7-4) unstable; urgency=medium
 
   * Update dependencies on autopkgtests to libdap-bin
diff -Nru libdap-3.20.7/debian/control libdap-3.20.7/debian/control
--- libdap-3.20.7/debian/control2021-02-03 13:27:57.0 +0100
+++ libdap-3.20.7/debian/control2021-02-04 05:07:14.0 +0100
@@ -94,6 +94,8 @@
 Architecture: any
 Multi-Arch: same
 Depends: libdap27 ( = ${binary:Version} ), libdapserver7v5 
(=${binary:Version}), libdapclient6v5 (=${binary:Version}) , ${misc:Depends}, 
libxml2-dev, libcurl4-gnutls-dev | libcurl-dev, uuid-dev, pkg-config
+Breaks: libdap-bin (<< 3.20.7-5~)
+Replaces: libdap-bin (<< 3.20.7-5~)
 Description: Development files (headers and static libraries) for libdap
  OPeNDAP provides software that allows you to access data over the internet,
  from programs that weren't originally designed for that purpose, as well
@@ -109,8 +111,6 @@
 Architecture: all
 Multi-Arch: foreign
 Depends: ${misc:Depends}, libjs-jquery
-Breaks: libdap-dev (<< 3.20.7)
-Replaces: libdap-dev (<< 3.20.7)
 Description: Documentation for the libdap Data Access Protocol library
  OPeNDAP provides software that allows you to access data over the internet,
  from programs that weren't originally designed for that purpose, as well
diff -Nru libdap-3.20.7/debian/libdap-bin.install 
libdap-3.20.7/debian/libd

Bug#981765: marked as done (docknot: autopkgtest failure)

[Debian Bug Tracking System]

Your message dated Thu, 04 Feb 2021 04:18:22 +
with message-id 
and subject line Bug#981765: fixed in docknot 4.00-2
has caused the Debian Bug report #981765,
regarding docknot: 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.)


-- 
981765: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=981765
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: docknot
Version: 4.00-1
Severity: serious

https://ci.debian.net/data/autopkgtest/testing/amd64/d/docknot/10221864/log.gz

...
Test Summary Report
---
t/cli/generate.t  (Wstat: 512 Tests: 2 Failed: 0)
  Non-zero exit status: 2
  Parse errors: Bad plan.  You planned 7 tests but ran 2.
t/dist/commands.t (Wstat: 512 Tests: 1 Failed: 0)
  Non-zero exit status: 2
  Parse errors: Bad plan.  You planned 7 tests but ran 1.
t/generate/output.t   (Wstat: 512 Tests: 1 Failed: 0)
  Non-zero exit status: 2
  Parse errors: Bad plan.  You planned 7 tests but ran 1.
t/generate/self.t (Wstat: 512 Tests: 1 Failed: 0)
  Non-zero exit status: 2
  Parse errors: Bad plan.  You planned 5 tests but ran 1.
t/style/module-version.t  (Wstat: 512 Tests: 0 Failed: 0)
  Non-zero exit status: 2
  Parse errors: No plan found in TAP output
t/style/strict.t  (Wstat: 512 Tests: 87 Failed: 2)
  Failed tests:  2-3
  Non-zero exit status: 2
Files=21, Tests=386, 12 wallclock secs ( 0.12 usr  0.02 sys + 10.12 cusr  1.34 
csys = 11.60 CPU)
Result: FAIL
...
--- End Message ---
--- Begin Message ---
Source: docknot
Source-Version: 4.00-2
Done: Russ Allbery 

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

Debian distribution maintenance software
pp.
Russ Allbery  (supplier of updated docknot package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 03 Feb 2021 19:56:38 -0800
Source: docknot
Architecture: source
Version: 4.00-2
Distribution: unstable
Urgency: medium
Maintainer: Russ Allbery 
Changed-By: Russ Allbery 
Closes: 981765
Changes:
 docknot (4.00-2) unstable; urgency=medium
 .
   * Configure the autopkgtest-pkg-perl tests.  (Closes: #981765)
 - Disable doc and style tests, which don't test functionality and are
   therefore outside the remit of autopkgtest, and which depend on bits
   of the source tree.
 - Include the package metadata that is used as input to some of the
   tests when running the smoke test.
Checksums-Sha1:
 3833b799c0338aa4915b8d77b2538bc88d8be433 2270 docknot_4.00-2.dsc
 ae50bcca6dea000d4d6a08b736ff84794359381b 12240 docknot_4.00-2.debian.tar.xz
Checksums-Sha256:
 9936481515988bcdc74fb13430e07fd552492f44915aa213760860ad059a0166 2270 
docknot_4.00-2.dsc
 df578d7ded6b2b3d45e1f514b88e4a57b4f758aba9e91756fce8f8c648468da2 12240 
docknot_4.00-2.debian.tar.xz
Files:
 824919d544eb99fea0fa402dcb507dd4 2270 text optional docknot_4.00-2.dsc
 44ccbde33cbfd53f9f769cb1f9707a9d 12240 text optional 
docknot_4.00-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQEzBAEBCgAdFiEE1zk0tJZ0z1zNmsJ4fYAxXFc23nUFAmAbcREACgkQfYAxXFc2
3nXVggf+PcWjLbk0aKke1/dSPuaAbxWab3YURJvDsV5aoHm0h9rJmqQUcBmwM0Mo
5VexPq0Q+GCCjA9xnX8oYR2OhGI3m5Lw7I+5BAOlVbtYaB/p/scW73pvhhPYRNxk
poHhgMQ+B0PboMTIETOyOTauwfG76y4q5ZFz3Dn1MqtV78V95m9OyRflZxHZDeXV
Mn/sFV6JPYt3KQgrthVm+KR0IT4ONM4rNo+/K4bmCwKzWZEd8WIXleouR4fGO/FJ
Nc4M/KVfMz7s0bOQhV/jJ4IqutXImZ64fXfqEm78ClEQJaLWaoqaqm+rwk/v+pPI
Zbt7ERx+oWFZWP35Zq1PeC8FAi8UAQ==
=Ia6E
-END PGP SIGNATURE End Message ---

Bug#981403: marked as done (pylev: Another source-only upload is needed)

[Debian Bug Tracking System]

Your message dated Wed, 03 Feb 2021 22:19:19 -0500
with message-id 
and subject line Re: pylev: Another source-only upload is needed
has caused the Debian Bug report #981403,
regarding pylev: Another source-only upload is needed
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.)


-- 
981403: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=981403
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pylev
Version: 1.2.0-1
Severity: important

Dear Debian pylev package maintainer,

According to https://tracker.debian.org/pkg/pylev , this package was
not updated since its initial upload. As a result, it misses a source-
only upload and cannot migrate to Debian Testing.

Please make another source-only upload before Debian 11 soft freeze
following https://wiki.debian.org/SourceOnlyUpload .

Thanks,
Boyuan Yang


signature.asc
Description: This is a digitally signed message part
--- End Message ---
--- Begin Message ---
Version: 1.2.0-2

This is fixed in the most recent upload.

Thanks,
Boyuan Yang


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

Processed: tt-rss: Packaging work for new upstream release 21.1

[Debian Bug Tracking System]

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

> tag 970633 + patch
Bug #970633 [src:tt-rss] tt-rss: CVE-2020-25787 CVE-2020-25788 CVE-2020-25789
Added tag(s) patch.
> tag 932924 + patch
Bug #932924 [src:tt-rss] tt-rss: privacy violation -- ttrss Forum und New 
Releases subscribed to by default
Added tag(s) patch.
> thanks
Stopping processing here.

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

Bug#970633: tt-rss: Packaging work for new upstream release 21.1

[Sunil Mohan Adapa]

tag 970633 + patch
tag 932924 + patch
thanks

Hello,

Eagerly looking forward to tt-rss being in good shape for FreedomBox in
Bullseye, I have done the packaging work needed for uploading 21.1
version of tt-rss. Please merge and upload the package into Debian
unstable before the Bullseye Soft Freeze date February 12th. Since this
is a collab-maint package, I assume it would be okay to for others to
upload as well.

* New upstream release based on latest revision 6d8f2221 on 2021-01-29
11:52:21 UTC+0300.
  - Contains security fixes for CVE-2020-25787 CVE-2020-25788
CVE-2020-25789 (Closes: #970633).
* Use latest version of libjs-prototype.
* Refresh patches.
* Ability to update to latest schema version 140.
* Update Debian Standards Version to 4.5.1.
* Update debhelper compatibility to 13 the latest.
* Mark as not requiring root for rules file.
* Add self to list of uploaders.
* Fix various lintian warnings and info messages.
* Document upstream changes since 19.8.
* Add directory for caching feeds.
* Remove the default feed to tt-rss forum to improve privacy. (Closes:
#932924)
* Use material design icons from Debian package.
* Add documentation link in systemd service file.
* Redirect stderr to journal instead of syslog.

Apart from the https://salsa.debian.org/sunilmohan/tt-rss/-/tree/master
branch please also pull in branches
https://salsa.debian.org/sunilmohan/tt-rss/-/tree/pristine-tar and
https://salsa.debian.org/sunilmohan/tt-rss/-/tree/upstream along with
the tags.

I have tested new version as follows:

- DONE: lintian does not show messages with --info --display-info --pedantic
- DONE: SELF_URL_PATH may need a proper value.
- DONE: Prototype JS is working fine (no change since last version)
- DONE: Dojo is loading fine the following pages:
  - DONE: feeds.php
  - DONE: public.php: popup in Feeds -> Bookmarklets -> Share with TTRSS
  - DONE: public.php: forgot password page
  - DONE: public.php: db update page
  - DONE: public.php: subscribe to feed page (possible dead code)
  - DONE: installer: unused in Debian
  - DONE: login_form.php
- DONE: Debian configured DB works
- DONE: Theme looks good, dark theme works
- DONE: Upstream changes files contains changes for 21.1
- DONE: No messages in Apache error log
- DONE: Update service works properly, feeds are updated offline
- DONE: Updates error log is successfully redirected to journal
- DONE: No error messages in journal for updates
- DONE: Material design icons are linked to properly in .deb
- DONE: Material design icons show up in web interface properly
- DONE: Installed DB schema version is 140
  - DONE: Install fresh on MySQL/MariaDB
  - DONE: Install fresh on PostgreSQL
  - DONE: Upgraded from 19.8 on MySQL/MariaDB
  - DONE: Upgraded from 19.8 on PostgreSQL
- DONE: Install fresh on bare Debian works fine
- DONE: With MySQL/MariaDB
- DONE: With PostgreSQL
- DONE: Upgrade from 19.8 on bare Debian work fine
  - DONE: With MySQL
  - DONE: With PostgreSQL
- DONE: Default feed Tiny Tiny RSS Forum is not present by default
  - DONE: On MySQL installation
  - DONE: On PostgreSQL installation
  - DONE: When a new user is created in prefs.

Thanks,

-- 
Sunil

Bug#980609: missing i386-cpuinfo.h

[Andrea Pappacoda]

Followup-For: Bug #980609
source: gcc-10

Is this fix going to be backported to bullseye/sid? I'm too facing this issue 
with gcc-10 10.2.1-6.

Bug#981428: python3-fido2: Version 0.9 breaks yubikey-manager

[Taowa Munene-Tardif]

howdy nicoo,

nicoo, 2021-01-30 20:21 -0500:
> python-fido2 had minor API-breaking changes, which breaks (at least)
> yubikey-manager.  Let's hold it back from transitionning to testing until
> upstream cuts a new release.

fyi the breaking of yubikey-manager seems to break yubioath-desktop too,
just so you know :)

<3,
taowa

-- 
Taowa (they/them)
LOC FN35EM

Bug#981804: yubioath-desktop: fails to read yubikey

[Norbert Preining]

It seems some Python files got missing, the stderr gives

nhandled PyOtherSide error: Cannot import module: yubikey (Traceback (most 
recent call last):

  File "qrc:///py/yubikey.py", line 12, in 
from ykman.descriptor import (

ModuleNotFoundError: No module named 'ykman.descriptor'
)
Unhandled PyOtherSide error: Function not found: 'yubikey.init' (Traceback 
(most recent call last):

  File "", line 1, in 

NameError: name 'yubikey' is not defined

...

Best

Norbert

--
PREINING Norbert  https://www.preining.info
Fujitsu Research Labs  +  IFMGA Guide + TU Wien + TeX Live + Debian Dev
GPG: 0x860CDC13   fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13

Bug#981804: yubioath-desktop: fails to read yubikey

[Norbert Preining]

Package: yubioath-desktop
Version: 5.0.4-2
Severity: grave
Justification: renders package unusable
X-Debbugs-Cc: norb...@preining.info

Hi all,

A flush of updates came in, besides that some yubi package updates,
and this morning the yubioath desktop application does not recognize my
yubikey (4, USB) anymore. No reaction. Yesterday it was still working.

[~] ykls
Reader:  Yubico Yubikey NEO OTP+U2F+CCID 00 00
Version: 0.1.3


Thanks

Norbert



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

Kernel: Linux 5.10.13 (SMP w/4 CPU threads)
Kernel taint flags: TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages yubioath-desktop depends on:
ii  libc6  2.31-9
ii  libgcc-s1  10.2.1-6
ii  libqt5core5a   5.15.2+dfsg-4
ii  libqt5gui5 5.15.2+dfsg-4
ii  libqt5qml5 5.15.2+dfsg-3
ii  libqt5quick5   5.15.2+dfsg-3
ii  libqt5quickcontrols2-5 5.15.2+dfsg-2
ii  libqt5widgets5 5.15.2+dfsg-4
ii  libstdc++6 10.2.1-6
ii  pcscd  1.9.0-1
ii  python3-yubikey-manager4.0.0~a1-1
ii  qml-module-io-thp-pyotherside  1.5.9-2+b3
ii  qml-module-qt-labs-platform5.15.2+dfsg-2
ii  qml-module-qt-labs-settings5.15.2+dfsg-3
ii  qml-module-qtquick-controls5.15.2-2
ii  qml-module-qtquick-controls2   5.15.2+dfsg-2
ii  qml-module-qtquick-dialogs 5.15.2-2

yubioath-desktop recommends no packages.

yubioath-desktop suggests no packages.

-- no debconf information

Bug#957822: marked as done (snapd-glib: ftbfs with GCC-10)

[Debian Bug Tracking System]

Your message dated Wed, 03 Feb 2021 23:50:34 +
with message-id 
and subject line Bug#957822: fixed in snapd-glib 1.58-1
has caused the Debian Bug report #957822,
regarding snapd-glib: 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.)


-- 
957822: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957822
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:snapd-glib
Version: 1.54-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/snapd-glib_1.54-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

[...]
Installing /<>/snapd-qt/Snapd/WrappedObject to 
/<>/debian/tmp/usr/include/snapd-qt/Snapd
Installing /<>/obj-x86_64-linux-gnu/meson-private/snapd-glib.pc to 
/<>/debian/tmp/usr/lib/x86_64-linux-gnu/pkgconfig
Installing /<>/obj-x86_64-linux-gnu/meson-private/snapd-glib.deps 
to /<>/debian/tmp/usr/share/vala/vapi
Installing /<>/obj-x86_64-linux-gnu/meson-private/snapd-qt.pc to 
/<>/debian/tmp/usr/lib/x86_64-linux-gnu/pkgconfig
Installing /<>/snapd-qt/qmldir to 
/<>/debian/tmp/usr/lib/x86_64-linux-gnu/qt5/qml/Snapd
Installing /<>/obj-x86_64-linux-gnu/snapd-qt/SnapdConfig.cmake to 
/<>/debian/tmp/usr/lib/x86_64-linux-gnu/cmake/Snapd
Installing 
/<>/obj-x86_64-linux-gnu/snapd-qt/SnapdConfigVersion.cmake to 
/<>/debian/tmp/usr/lib/x86_64-linux-gnu/cmake/Snapd
Installing /<>/snapd-qt/qmldir to 
/<>/debian/tmp/usr/lib/x86_64-linux-gnu/qt5/qml/Snapd
Installing /<>/obj-x86_64-linux-gnu/tests/test-glib.test to 
/<>/debian/tmp/usr/share/installed-tests/snapd-glib
Installing /<>/obj-x86_64-linux-gnu/tests/test-markdown-glib.test 
to /<>/debian/tmp/usr/share/installed-tests/snapd-glib
Installing /<>/obj-x86_64-linux-gnu/tests/test-qt.test to 
/<>/debian/tmp/usr/share/installed-tests/snapd-glibBuilding 
documentation for snapd-glib
html/SnapdAlias.html:211: warning: no link for: "NULL:CAPS" -> (NULL).
html/SnapdApp.html:122: warning: no link for: "GStrv" -> (GStrv).
html/SnapdApp.html:251: warning: no link for: "TRUE:CAPS" -> (TRUE).
html/SnapdChange.html:148: warning: no link for: "GDateTime" -> (GDateTime).
html/SnapdChange.html:172: warning: no link for: "GPtrArray" -> (GPtrArray).
html/SnapdClient.html:1400: warning: no link for: "GCancellable" -> (GCancellable).
html/SnapdClient.html:1416: warning: no link for: "GObject" -> (GObject).
html/SnapdClient.html:1650: warning: no link for: "GSocket" -> (GSocket).
html/SnapdClient.html:1827: warning: no link for: "GError" -> (GError).
html/SnapdClient.html:1869: warning: no link for: "GAsyncReadyCallback" -> 
(GAsyncReadyCallback).
html/SnapdClient.html:1912: warning: no link for: "GAsyncResult" -> (GAsyncResult).
html/SnapdClient.html:3737: warning: no link for: "GHashTable" -> (GHashTable).
html/SnapdClient.html:4558: warning: no link for: "FALSE:CAPS" -> (FALSE).
html/SnapdClient.html:6596: warning: no link for: "GInputStream" -> (GInputStream).
html/SnapdConnection.html:411: warning: no link for: "g-strfreev" -> (g_strfreev()).
html/SnapdIcon.html:73: warning: no link for: "GBytes" -> (GBytes).
html/snapd-glib-Errors.html:95: warning: no link for: "GQuark" -> (GQuark).


Installing /<>/obj-x86_64-linux-gnu/tests/test-markdown-qt.test to 
/<>/debian/tmp/usr/share/installed-tests/snapd-glib
Running custom install script '/usr/bin/meson --internal gtkdoc 
--sourcedir=/<> --builddir=/<>/obj-x86_64-linux-gnu 
--subdir=doc/reference 
--headerdirs=/<>/snapd-glib@@/<>/obj-x86_64-linux-gnu/snapd-glib
 
--mainfile=/<>/obj-x86_64-linu

Processed: Re: [Pkg-utopia-maintainers] Bug#981747: network-manager: NetworkManager does not start in sysvinit system

[Debian Bug Tracking System]

Processing control commands:

> forcemerge 964139 -1
Bug #964139 [network-manager] network-manager: Please restore removed init 
script.
Bug #981747 [network-manager] network-manager: NetworkManager does not start in 
sysvinit system
Severity set to 'wishlist' from 'grave'
981747 was not blocked by any bugs.
981747 was not blocking any bugs.
Added blocking bug(s) of 981747: 975075
Marked as found in versions network-manager/1.25.91-1.
Bug #964139 [network-manager] network-manager: Please restore removed init 
script.
Marked as found in versions network-manager/1.28.0-2.
Added tag(s) newcomer.
Merged 964139 981747
> tags 964139  + wontfix
Bug #964139 [network-manager] network-manager: Please restore removed init 
script.
Bug #981747 [network-manager] network-manager: NetworkManager does not start in 
sysvinit system
Added tag(s) wontfix.
Added tag(s) wontfix.

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

Bug#981747: [Pkg-utopia-maintainers] Bug#981747: network-manager: NetworkManager does not start in sysvinit system

[Michael Biebl]

Control: forcemerge 964139 -1
Control: tags 964139  + wontfix


Merging with the duplicate.
I don't intend to restore the deprecated SysV init script. So marking as 
wontfix.

Bug#981420: marked as done (libglib2.0-0: gnome-keyring unable to unlock login keyring on some systems since GLib 2.66.4-2)

[Debian Bug Tracking System]

Your message dated Wed, 03 Feb 2021 21:48:44 +
with message-id 
and subject line Bug#981555: fixed in glib2.0 2.66.5-1
has caused the Debian Bug report #981555,
regarding libglib2.0-0: gnome-keyring unable to unlock login keyring on some 
systems since GLib 2.66.4-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.)


-- 
981555: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=981555
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libglib2.0-0
Version: 2.66.4-1
Severity: important
Tags: upstream
X-Debbugs-Cc: malahee...@gmx.fr

Dear maintainer,

After the recent update of libglib2.0 to 2.66.4-3, gnome-keyring is not able to
unlock "Login" keyring. For example, it does not allow to unlock saved ssh keys
automatically; ssh/ssh-agent starts to ask for a password in CLI instead of
fancy popup window.

The downgrading to 2.66.4-1 solves the problem.

Could you take a look?

Thank you!



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

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

Versions of packages libglib2.0-0 depends on:
ii  libc62.31-9
ii  libffi7  3.3-5
ii  libmount12.36.1-6
ii  libpcre3 2:8.39-13
ii  libselinux1  3.1-2+b2
ii  zlib1g   1:1.2.11.dfsg-2

Versions of packages libglib2.0-0 recommends:
hi  libglib2.0-data   2.66.4-1
ii  shared-mime-info  2.0-1
ii  xdg-user-dirs 0.17-2

libglib2.0-0 suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: glib2.0
Source-Version: 2.66.5-1
Done: Simon McVittie 

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

Debian distribution maintenance software
pp.
Simon McVittie  (supplier of updated glib2.0 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: Wed, 03 Feb 2021 19:16:01 +
Source: glib2.0
Architecture: source
Version: 2.66.5-1
Distribution: unstable
Urgency: medium
Maintainer: Debian GNOME Maintainers 

Changed-By: Simon McVittie 
Closes: 981420 981555
Changes:
 glib2.0 (2.66.5-1) unstable; urgency=medium
 .
   * New upstream release, equivalent to 2.66.4-27-g0051c0635
   * Drop patches that were applied upstream
 .
 glib2.0 (2.66.4-4) unstable; urgency=medium
 .
   * d/patches: Update patch series to upstream commit 2.66.4-27-g0051c0635
 - Improve test coverage for #977961
 - Stop valgrind reporting memory leaks in GSpawn in most cases
 - Partially revert security hardening from 2.66.4-2: allow
   DBUS_SESSION_BUS_ADDRESS to be taken from the environment by
   setcap executables (to avoid regressing gnome-keyring) and by
   setgid executables (to avoid regressing msmtp).
   (Closes: #981420, #981555)
   Note that this is likely to be reverted in GLib 2.70.x to provide
   better hardening. The D-Bus session bus is not designed to be used
   by processes that have elevated privileges.
Checksums-Sha1:
 60c615b5d5842ee13e4c89492b054381683e8e19 3383 glib2.0_2.66.5-1.dsc
 0a33c26556f8169c16945c77f4966efcc693e444 4841456 glib2.0_2.66.5.orig.tar.xz
 334a3f78b59c8210dc5f29ca25975e459930f5bd 98068 glib2.0_2.66.5-1.debian.tar.xz
 8331112985fe6f602bf99aae6b25ce4c7ee2 7874 glib2.0_2.66.5-1_source.buildinfo
Checksums-Sha256:
 106938a689f183c5be398d27bd2b7e648d70c1e663a14daffd24a7a0c13e5d58 3383 
glib2.0_2.66.5-1.dsc
 44b1d382752733bd3d38e8416def3801c746568507d726de09b820e20a1337a8 4841456 
glib2.0_2.66.5.orig.tar.xz
 ece83fe6c101ac0304b14b477062b8458f86174b7ff479228be41b1dfcc1a210 98068 
glib2.0_2.66.5-1.debian.tar.xz
 4a4ffb8737afc5439af02d495fc5af82a4c5ad4574265bac7731e752ede1faa9 7874 
glib2.0_2.66.5-1_source.buildinfo
Files:
 fc6b132e09a4dff757a660b062f85d64 3383 libs

Bug#981555: marked as done (gnome-keyring: unable to connect to D-Bus when using dbus-x11)

[Debian Bug Tracking System]

Your message dated Wed, 03 Feb 2021 21:48:44 +
with message-id 
and subject line Bug#981555: fixed in glib2.0 2.66.5-1
has caused the Debian Bug report #981555,
regarding gnome-keyring: unable to connect to D-Bus when using dbus-x11
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.)


-- 
981555: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=981555
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gnome-keyring
Version: 3.36.0-1
Severity: important

Dear maintainers,

Since this work week Evolution on my laptop does not ask for GNOME keyring
password anymore. Instead after some kind of a timeout it directly asks
for the password of the connection.

It does so for retrieving mails, for sending mails, for calendar and 
addressbook access. I am using Evolution EWS with Office 365.

Since this worked before I do not consider this to be an upstream issue.
However also 'gnome-keyring' package does not appear to have been changed
recently. So it may be related to the upgrade of a different package.

I do see

kdeinit5: Got EXEC_NEW 'dbus-send' from launcher.
kdeinit5: preparing to launch 'libkdeinit5_dbus-send'
Could not open dbus-send using a library: Cannot load library 
libkdeinit5_dbus-send: (libkdeinit5_dbus-send: Kann die Shared-Object-Datei 
nicht öffnen: Datei oder Verzeichnis nicht gefunden)
kdeinit5: PID 13520 terminated.

in ~/.xsession-errors which may be related.

However I did not find 'libkdeinit5_dbus-send' anywhere with 'apt-file search'.

GNOME Keyring daemon, which to my understanding provides Secrets Services
DBUS API, is running, excerpt from 'ps aux':

someuser   13491  0.0  0.0  15756  4984 ?SL   08:52   0:00 
/usr/bin/gnome-keyring-daemon --daemonize --login

However also 'qdbus' reports that the DBUS API is not accessible:

% qdbus org.freedesktop.secrets 
Error: org.freedesktop.DBus.Error.NoReply
Did not receive a reply. Possible causes include: the remote application did 
not send a reply, the message bus security policy blocked the reply, the reply 
timeout expired, or the network connection was broken.

It does not even seem to exist:

% qdbus | grep secrets
[… nothing …]

However also if started manually GNOME Keyring does not report an error:

% /usr/bin/gnome-keyring-daemon --login
[… keeps running, no output, even after Evolution failing to connect DBUS
API …]

I am using Runit as PID 1. This has not been an issue before.

Thanks,
Martin

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

Kernel: Linux 5.11.0-rc6-tp520 (SMP w/4 CPU threads; PREEMPT)
Kernel taint flags: TAINT_WARN, TAINT_OOT_MODULE
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: runit (via /run/runit.stopit)
LSM: AppArmor: enabled

Versions of packages gnome-keyring depends on:
ii  dbus-x11 [dbus-session-bus]  1.12.20-1
ii  dconf-gsettings-backend [gsettings-backend]  0.38.0-1
ii  gcr  3.38.1-1
ii  libc62.31-9
ii  libcap-ng0   0.7.9-2.2+b1
ii  libcap2-bin  1:2.44-1
ii  libgck-1-0   3.38.1-1
ii  libgcr-base-3-1  3.38.1-1
ii  libgcrypt20  1.8.7-2
ii  libglib2.0-0 2.66.4-3
ii  p11-kit  0.23.22-1
ii  pinentry-gnome3  1.1.0-4

Versions of packages gnome-keyring recommends:
ii  gnome-keyring-pkcs11  3.36.0-1
ii  libpam-gnome-keyring  3.36.0-1

gnome-keyring suggests no packages.

-- debconf-show failed
--- End Message ---
--- Begin Message ---
Source: glib2.0
Source-Version: 2.66.5-1
Done: Simon McVittie 

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

Debian distribution maintenance software
pp.
Simon McVittie  (supplier of updated glib2.0 package)

(This message was generated automatically at their request; if you
believe that there is a p

Bug#981555: marked as done (gnome-keyring: unable to connect to D-Bus when using dbus-x11)

[Debian Bug Tracking System]

Your message dated Wed, 03 Feb 2021 21:48:43 +
with message-id 
and subject line Bug#981420: fixed in glib2.0 2.66.5-1
has caused the Debian Bug report #981420,
regarding gnome-keyring: unable to connect to D-Bus when using dbus-x11
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.)


-- 
981420: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=981420
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gnome-keyring
Version: 3.36.0-1
Severity: important

Dear maintainers,

Since this work week Evolution on my laptop does not ask for GNOME keyring
password anymore. Instead after some kind of a timeout it directly asks
for the password of the connection.

It does so for retrieving mails, for sending mails, for calendar and 
addressbook access. I am using Evolution EWS with Office 365.

Since this worked before I do not consider this to be an upstream issue.
However also 'gnome-keyring' package does not appear to have been changed
recently. So it may be related to the upgrade of a different package.

I do see

kdeinit5: Got EXEC_NEW 'dbus-send' from launcher.
kdeinit5: preparing to launch 'libkdeinit5_dbus-send'
Could not open dbus-send using a library: Cannot load library 
libkdeinit5_dbus-send: (libkdeinit5_dbus-send: Kann die Shared-Object-Datei 
nicht öffnen: Datei oder Verzeichnis nicht gefunden)
kdeinit5: PID 13520 terminated.

in ~/.xsession-errors which may be related.

However I did not find 'libkdeinit5_dbus-send' anywhere with 'apt-file search'.

GNOME Keyring daemon, which to my understanding provides Secrets Services
DBUS API, is running, excerpt from 'ps aux':

someuser   13491  0.0  0.0  15756  4984 ?SL   08:52   0:00 
/usr/bin/gnome-keyring-daemon --daemonize --login

However also 'qdbus' reports that the DBUS API is not accessible:

% qdbus org.freedesktop.secrets 
Error: org.freedesktop.DBus.Error.NoReply
Did not receive a reply. Possible causes include: the remote application did 
not send a reply, the message bus security policy blocked the reply, the reply 
timeout expired, or the network connection was broken.

It does not even seem to exist:

% qdbus | grep secrets
[… nothing …]

However also if started manually GNOME Keyring does not report an error:

% /usr/bin/gnome-keyring-daemon --login
[… keeps running, no output, even after Evolution failing to connect DBUS
API …]

I am using Runit as PID 1. This has not been an issue before.

Thanks,
Martin

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

Kernel: Linux 5.11.0-rc6-tp520 (SMP w/4 CPU threads; PREEMPT)
Kernel taint flags: TAINT_WARN, TAINT_OOT_MODULE
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: runit (via /run/runit.stopit)
LSM: AppArmor: enabled

Versions of packages gnome-keyring depends on:
ii  dbus-x11 [dbus-session-bus]  1.12.20-1
ii  dconf-gsettings-backend [gsettings-backend]  0.38.0-1
ii  gcr  3.38.1-1
ii  libc62.31-9
ii  libcap-ng0   0.7.9-2.2+b1
ii  libcap2-bin  1:2.44-1
ii  libgck-1-0   3.38.1-1
ii  libgcr-base-3-1  3.38.1-1
ii  libgcrypt20  1.8.7-2
ii  libglib2.0-0 2.66.4-3
ii  p11-kit  0.23.22-1
ii  pinentry-gnome3  1.1.0-4

Versions of packages gnome-keyring recommends:
ii  gnome-keyring-pkcs11  3.36.0-1
ii  libpam-gnome-keyring  3.36.0-1

gnome-keyring suggests no packages.

-- debconf-show failed
--- End Message ---
--- Begin Message ---
Source: glib2.0
Source-Version: 2.66.5-1
Done: Simon McVittie 

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

Debian distribution maintenance software
pp.
Simon McVittie  (supplier of updated glib2.0 package)

(This message was generated automatically at their request; if you
believe that there is a p

Bug#981420: marked as done (libglib2.0-0: gnome-keyring unable to unlock login keyring on some systems since GLib 2.66.4-2)

[Debian Bug Tracking System]

Your message dated Wed, 03 Feb 2021 21:48:43 +
with message-id 
and subject line Bug#981420: fixed in glib2.0 2.66.5-1
has caused the Debian Bug report #981420,
regarding libglib2.0-0: gnome-keyring unable to unlock login keyring on some 
systems since GLib 2.66.4-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.)


-- 
981420: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=981420
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libglib2.0-0
Version: 2.66.4-1
Severity: important
Tags: upstream
X-Debbugs-Cc: malahee...@gmx.fr

Dear maintainer,

After the recent update of libglib2.0 to 2.66.4-3, gnome-keyring is not able to
unlock "Login" keyring. For example, it does not allow to unlock saved ssh keys
automatically; ssh/ssh-agent starts to ask for a password in CLI instead of
fancy popup window.

The downgrading to 2.66.4-1 solves the problem.

Could you take a look?

Thank you!



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

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

Versions of packages libglib2.0-0 depends on:
ii  libc62.31-9
ii  libffi7  3.3-5
ii  libmount12.36.1-6
ii  libpcre3 2:8.39-13
ii  libselinux1  3.1-2+b2
ii  zlib1g   1:1.2.11.dfsg-2

Versions of packages libglib2.0-0 recommends:
hi  libglib2.0-data   2.66.4-1
ii  shared-mime-info  2.0-1
ii  xdg-user-dirs 0.17-2

libglib2.0-0 suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: glib2.0
Source-Version: 2.66.5-1
Done: Simon McVittie 

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

Debian distribution maintenance software
pp.
Simon McVittie  (supplier of updated glib2.0 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: Wed, 03 Feb 2021 19:16:01 +
Source: glib2.0
Architecture: source
Version: 2.66.5-1
Distribution: unstable
Urgency: medium
Maintainer: Debian GNOME Maintainers 

Changed-By: Simon McVittie 
Closes: 981420 981555
Changes:
 glib2.0 (2.66.5-1) unstable; urgency=medium
 .
   * New upstream release, equivalent to 2.66.4-27-g0051c0635
   * Drop patches that were applied upstream
 .
 glib2.0 (2.66.4-4) unstable; urgency=medium
 .
   * d/patches: Update patch series to upstream commit 2.66.4-27-g0051c0635
 - Improve test coverage for #977961
 - Stop valgrind reporting memory leaks in GSpawn in most cases
 - Partially revert security hardening from 2.66.4-2: allow
   DBUS_SESSION_BUS_ADDRESS to be taken from the environment by
   setcap executables (to avoid regressing gnome-keyring) and by
   setgid executables (to avoid regressing msmtp).
   (Closes: #981420, #981555)
   Note that this is likely to be reverted in GLib 2.70.x to provide
   better hardening. The D-Bus session bus is not designed to be used
   by processes that have elevated privileges.
Checksums-Sha1:
 60c615b5d5842ee13e4c89492b054381683e8e19 3383 glib2.0_2.66.5-1.dsc
 0a33c26556f8169c16945c77f4966efcc693e444 4841456 glib2.0_2.66.5.orig.tar.xz
 334a3f78b59c8210dc5f29ca25975e459930f5bd 98068 glib2.0_2.66.5-1.debian.tar.xz
 8331112985fe6f602bf99aae6b25ce4c7ee2 7874 glib2.0_2.66.5-1_source.buildinfo
Checksums-Sha256:
 106938a689f183c5be398d27bd2b7e648d70c1e663a14daffd24a7a0c13e5d58 3383 
glib2.0_2.66.5-1.dsc
 44b1d382752733bd3d38e8416def3801c746568507d726de09b820e20a1337a8 4841456 
glib2.0_2.66.5.orig.tar.xz
 ece83fe6c101ac0304b14b477062b8458f86174b7ff479228be41b1dfcc1a210 98068 
glib2.0_2.66.5-1.debian.tar.xz
 4a4ffb8737afc5439af02d495fc5af82a4c5ad4574265bac7731e752ede1faa9 7874 
glib2.0_2.66.5-1_source.buildinfo
Files:
 fc6b132e09a4dff757a660b062f85d64 3383 libs

Processed: bug 981404 is forwarded to https://github.com/facebook/zstd/issues/1630, tagging 981404

[Debian Bug Tracking System]

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

> forwarded 981404 https://github.com/facebook/zstd/issues/1630
Bug #981404 [zstd] compressed file is world readable, while zstd is running
Set Bug forwarded-to-address to 'https://github.com/facebook/zstd/issues/1630'.
> tags 981404 + upstream fixed-upstream
Bug #981404 [zstd] compressed file is world readable, while zstd is running
Added tag(s) upstream and fixed-upstream.
> thanks
Stopping processing here.

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

Bug#981798: imagemagick breaks gscan2pdf autopkgtest: expected format changed

[Jeff]

This is more or less a duplicate of #980202

To unblock gscan2pdf, in case -60 didn't fix things, I uploaded 
gscan2pdf-2.11.0-1 yesterday and replaced imagemagick with 
graphicsmagick for the tests in question.


However, this doesn't solve the problem in imagemagick, which is 
described in #980202, and for which imagemagick upstream claims to have 
a solutions, but evidently doesn't.




OpenPGP_signature
Description: OpenPGP digital signature

Processed: fixed 979521 in openboard/1.5.4+dfsg1-1

[Debian Bug Tracking System]

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

> fixed 979521 openboard/1.5.4+dfsg1-1
Bug #979521 {Done: Mike Gabriel } [openboard-common] 
openboard-common depends on libjs-jquery-i18n-properties that was removed from 
unstable
Marked as fixed in versions openboard/1.5.4+dfsg1-1.
> thanks
Stopping processing here.

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

Bug#980575: kworkflow: autopkgtest needs update for new version of git

[Steve Langasek]

Package: kworkflow
Followup-For: Bug #980575
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu hirsute ubuntu-patch

Hello,

Please find attached a trivial patch to make the kworkflow autopkgtest
compatible with git 2.30.  I have uploaded this change to Ubuntu to unblock
the transition of git to the upcoming release.

Thanks for considering,
-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developer   https://www.debian.org/
slanga...@ubuntu.com vor...@debian.org
diff -Nru kworkflow-20191112/debian/tests/kw-basic-test 
kworkflow-20191112/debian/tests/kw-basic-test
--- kworkflow-20191112/debian/tests/kw-basic-test   2019-12-12 
09:19:30.0 -0800
+++ kworkflow-20191112/debian/tests/kw-basic-test   2021-02-03 
13:27:25.0 -0800
@@ -25,6 +25,7 @@
 
 git config --global user.email "deb...@debian.com"
 git config --global user.name "Debian SO"
+git config --global init.defaultBranch master
 
 ./run_tests.sh
 

Processed: Re: Bug#979480: fixed in openmpi 4.1.0-7

[Debian Bug Tracking System]

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

> # version tracking gets confused is bug is closed in different package
> reassign 979480 openmpi
Bug #979480 {Done: Alastair McKinstry } [src:mpi4py] 
mpi4py: autopkgtest failure on arm64, armhf and ppc64el
Bug reassigned from package 'src:mpi4py' to 'openmpi'.
No longer marked as found in versions mpi4py/3.0.3-7.
No longer marked as fixed in versions openmpi/4.1.0-7.
> fixed 979480 openmpi/4.1.0-7
Bug #979480 {Done: Alastair McKinstry } [openmpi] mpi4py: 
autopkgtest failure on arm64, armhf and ppc64el
Marked as fixed in versions openmpi/4.1.0-7.
> thanks
Stopping processing here.

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

Bug#981798: imagemagick breaks gscan2pdf autopkgtest: expected format changed

[Paul Gevers]

Source: imagemagick, gscan2pdf
Control: found -1 imagemagick/8:6.9.11.60+dfsg-1
Control: found -1 gscan2pdf/2.10.2-1
Severity: serious
Tags: sid bullseye
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: breaks needs-update

Dear maintainer(s),

With a recent upload of imagemagick the autopkgtest of gscan2pdf fails
in testing when that autopkgtest is run with the binary packages of
imagemagick from unstable. It passes when run with only packages from
testing. In tabular form:

   passfail
imagemagickfrom testing8:6.9.11.60+dfsg-1
gscan2pdf  from testing2.10.2-1
all others from testingfrom testing

I copied some of the output at the bottom of this report. The error for
the first two sets of failures hit at a missing test dependency, but the
other...

Currently this regression is blocking the migration of imagemagick to
testing [1]. Due to the nature of this issue, I filed this bug report
against both packages. Can you please investigate the situation and
reassign the bug to the right package?

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

Paul

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

https://ci.debian.net/data/autopkgtest/testing/amd64/g/gscan2pdf/10225709/log.gz

(1122_save_pdf_with_hocr.t:18459): dbind-WARNING **: 04:43:40.160:
AT-SPI: Error retrieving accessibility bus address:
org.freedesktop.DBus.Error.ServiceUnknown: The name org.a11y.Bus was not
provided by any .service files
Your system does not have Image::PNG::Libpng installed, so some
PNG functions may not run correctly.
Use of uninitialized value within @tags in concatenation (.) or string
at
/tmp/autopkgtest-lxc.fpzvb_nx/downtmp/build.uHw/src/blib/lib/Gscan2pdf/Bboxtree.pm
line 534.

#   Failed test 'import text layer'
#   at t/1122_save_pdf_with_hocr.t line 77.
#   '
# http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd";>
# http://www.w3.org/1999/xhtml"; xml:lang="en" lang="en">
#  
#   
#   
#   
#  
#  
# 
#  
# 
# '
# doesn't match '(?^msx:bbox\s0\s0\s525\s21)'

#   Failed test 'PDF with expected text'
#   at t/1122_save_pdf_with_hocr.t line 89.
#   ''
# doesn't match '(?^:The\s*quick\s*brown\s*fox)'
# Looks like you failed 2 tests of 2.
t/1122_save_pdf_with_hocr.t ...
1..2
not ok 1 - import text layer
not ok 2 - PDF with expected text
Dubious, test returned 2 (wstat 512, 0x200)
Failed 2/2 subtests


[...]


(113_save_pdf_with_downsample.t:18616): dbind-WARNING **: 04:43:49.175:
AT-SPI: Error retrieving accessibility bus address:
org.freedesktop.DBus.Error.ServiceUnknown: The name org.a11y.Bus was not
provided by any .service files

(113_save_pdf_with_downsample.t:18616): GdkPixbuf-CRITICAL **:
04:43:50.307: gdk_pixbuf_new_from_file_at_scale: assertion 'height > 0
|| height == -1' failed
Your system does not have Image::PNG::Libpng installed, so some
PNG functions may not run correctly.

#   Failed test 'downsampled PDF smaller than original'
#   at t/113_save_pdf_with_downsample.t line 52.
#  got: ''
# expected: '1'

#   Failed test 'downsampled'
#   at t/113_save_pdf_with_downsample.t line 55.
#   'PBM 485x1 485x1+0+0 1-bit DirectClass Gray '
# doesn't match '(?^:PBM 2\d\dx2\d 2\d\dx2\d[+]0[+]0 1-bit
DirectClass Gray)'
# Looks like you failed 2 tests of 2.
t/113_save_pdf_with_downsample.t ..
1..2
not ok 1 - downsampled PDF smaller than original
not ok 2 - downsampled
Dubious, test returned 2 (wstat 512, 0x200)
Failed 2/2 subtests


[...]


(134_save_tiff_alpha.t:19208): dbind-WARNING **: 04:44:21.007: AT-SPI:
Error retrieving accessibility bus address:
org.freedesktop.DBus.Error.ServiceUnknown: The name org.a11y.Bus was not
provided by any .service files

(134_save_tiff_alpha.t:19208): GdkPixbuf-CRITICAL **: 04:44:21.751:
gdk_pixbuf_new_from_file_at_scale: assertion 'height > 0 || height ==
-1' failed

#   Failed test 'valid TIFF created'
#   at t/134_save_tiff_alpha.t line 47.
#   'test.tif TIFF 485x1 485x1+0+0 16-bit sRGB 690B
0.000u 0:00.000
# '
# doesn't match '(?^:test.tif TIFF 4\d\dx\d\d 4\d\dx\d\d\+0\+0
16-bit sRGB)'
# Looks like you failed 1 test of 1.
t/134_save_tiff_alpha.t ...
1..1
not ok 1 - valid TIFF created
Dubious, test returned 1 (wstat 256, 0x100)
Failed 1/1 subtests


Test Summary Report
---
t/1122_save_pdf_with_hocr.t (Wstat: 512 Tests: 2 Failed: 2)
  Failed tests:  1-2
  Non-zero exit status: 2
t/113_save_pdf_with_downsample.t(Wstat: 512 Tests: 2 Failed: 2)
  Failed tests:  1-2
  Non-zero exit status: 2
t/134_save_tiff_alpha.t (Wstat: 256 Tests: 1 Failed: 1)
  Failed test:  1
  Non-zero exit status: 1
Files=242, Tests=1168, 374 wallclock secs ( 0.86 usr  0.32 sys + 201.15
cusr 2

Processed: imagemagick breaks gscan2pdf autopkgtest: expected format changed

[Debian Bug Tracking System]

Processing control commands:

> found -1 imagemagick/8:6.9.11.60+dfsg-1
Bug #981798 [src:imagemagick, src:gscan2pdf] imagemagick breaks gscan2pdf 
autopkgtest: expected format changed
Marked as found in versions imagemagick/8:6.9.11.60+dfsg-1.
> found -1 gscan2pdf/2.10.2-1
Bug #981798 [src:imagemagick, src:gscan2pdf] imagemagick breaks gscan2pdf 
autopkgtest: expected format changed
Marked as found in versions gscan2pdf/2.10.2-1.

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

Processed: Re: Bug#919058: fixed in debmake-doc 1.16-1

[Debian Bug Tracking System]

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

> # this bug is about the issue in its-tools, which isn't fixed yet
> # the FTBFS in debmake-doc (which is fixed) is tracked in #948781
> reopen 919058
Bug #919058 {Done: Osamu Aoki } [itstool] its-tools: crashes 
when freeing xmlDocs
'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 debmake-doc/1.16-1.
> thanks
Stopping processing here.

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

Processed: Re: notfound 948781 in itstool/2.0.4-1

[Debian Bug Tracking System]

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

> # this bug is about the FTBFS in debmake-doc, so reassign it there, to make
> # sure version tracking is correct
> # the bug in its-tools is 919058
> reassign 948781 debmake-doc
Bug #948781 {Done: Osamu Aoki } [itstool] debmake-doc: FTBFS: 
Segmentation fault
Bug reassigned from package 'itstool' to 'debmake-doc'.
Ignoring request to alter found versions of bug #948781 to the same values 
previously set
No longer marked as fixed in versions debmake-doc/1.16-1.
> fixed 948781 debmake-doc/1.16-1
Bug #948781 {Done: Osamu Aoki } [debmake-doc] debmake-doc: 
FTBFS: Segmentation fault
Marked as fixed in versions debmake-doc/1.16-1.
> close 948781
Bug #948781 {Done: Osamu Aoki } [debmake-doc] debmake-doc: 
FTBFS: Segmentation fault
Bug 948781 is already marked as done; not doing anything.
> thanks
Stopping processing here.

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

Processed: tagging 979641

[Debian Bug Tracking System]

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

> tags 979641 + pending
Bug #979641 [src:kboot-utils] src:kboot-utils: invalid maintainer address
Added tag(s) pending.
> thanks
Stopping processing here.

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

Processed: notfound 948781 in itstool/2.0.4-1

[Debian Bug Tracking System]

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

> # this is about the FTBFS in debmake-doc - see #919058 for the bug in itstool
> notfound 948781 itstool/2.0.4-1
Bug #948781 {Done: Osamu Aoki } [itstool] debmake-doc: FTBFS: 
Segmentation fault
No longer marked as found in versions itstool/2.0.4-1.
> thanks
Stopping processing here.

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

Bug#980115: connection failure when rx initialized after 08:25:36 GMT 14 Jan 2021

[Benjamin Kaduk]

Hi Salvatore,

On Wed, Feb 03, 2021 at 09:39:25PM +0100, Salvatore Bonaccorso wrote:
> HI Benjamin,
> 
> On Mon, Jan 18, 2021 at 07:19:14PM -0800, Benjamin Kaduk wrote:
> > On Mon, Jan 18, 2021 at 06:04:39PM +, Jeremy Stanley wrote:
> > > Thanks for pulling this into unstable and testing! Is there any work
> > > in progress to fix it in stable as well? I took a quick peek in
> > > Salsa and didn't see any merge requests or an obvious branch for
> > > Buster's 1.8.2 (just the debian/1.8.2-1 tag).
> > 
> > It is a clear candidate to fix in stable, though the only concrete steps
> > I've been able to take so far are to confirm with the security team that it
> > is not a candidate for being fixed via a DSA.
> > 
> > The actual work of backporting the patches should be ~trivial, so the
> > process work of engaging with the release team will be the dominating
> > factor.
> 
> Do you still have this on your radar? While as discussed this is not a
> DSA candidate a fix can be released out of order from a point release
> via the stable-updates mechanism, and this would be defintively a
> canddiate for it.

Yes, it's still on my radar but process has been slower than expected.
In order to do testing in a real buster environment I had to re-create my
VM infrastructure since I have gotten a new machine since I last did so.

> The procedure would be the same as proposing the fix to be rleased in
> a point release, but mentioning to the SRM that the fix actually needs
> to go out sooner (should be clear from context here), and pushed via a
> SUA.
> 
> https://lists.debian.org/debian-devel-announce/2011/03/msg00010.html
> https://lists.debian.org/debian-stable-announce/
> https://wiki.debian.org/StableUpdates
> 
> I think this becomes now even more urgent as users will roll out the
> linux update released as DSA 4843-1 or latest at the 10.8 point
> release on weekend and make the issue more urgent.

I've put the needed packaging changes into the 'buster' branch at
https://salsa.debian.org/debian/openafs/ and know of a few sites that are
running packages using that code in production.  I've been able to do local
testing of the client-side functionality as well, and just need to test the
server functionality before I file the bug with the release team.

Thanks for checking in and the pointers for the process to follow!

-Ben

Bug#979641: src:kboot-utils: invalid maintainer address

[Baptiste Beauplat]

On 2021/02/03 07:10 PM, Antonio Ospite wrote:
> On Wed, 3 Feb 2021 09:43:30 +0100
> Baptiste Beauplat  wrote:
> 
> [...]
> > 
> > I could open the RM bug on your behalf if you want me to.
> > 
> 
> Thank you, I would appreciate that.

Created as #981795

https://bugs.debian.org/981795

-- 
Baptiste Beauplat - lyknode


signature.asc
Description: PGP signature

Bug#979521: marked as done (openboard-common depends on libjs-jquery-i18n-properties that was removed from unstable)

[Debian Bug Tracking System]

Your message dated Wed, 03 Feb 2021 21:00:11 +
with message-id 
and subject line Bug#979521: fixed in jquery-i18n-properties 1.2.7+dfsg1-1
has caused the Debian Bug report #979521,
regarding openboard-common depends on libjs-jquery-i18n-properties that was 
removed from unstable
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.)


-- 
979521: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979521
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: openboard-common
Version: 1.5.4+dfsg1-1
Severity: serious

The following packages have unmet dependencies:
 openboard-common : Depends: libjs-jquery-i18n-properties but it is not 
installable

https://tracker.debian.org/pkg/jquery-i18n-properties
--- End Message ---
--- Begin Message ---
Source: jquery-i18n-properties
Source-Version: 1.2.7+dfsg1-1
Done: Mike Gabriel 

We believe that the bug you reported is fixed in the latest version of
jquery-i18n-properties, 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.
Mike Gabriel  (supplier of updated jquery-i18n-properties 
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: Wed, 20 Jan 2021 15:12:04 +0100
Source: jquery-i18n-properties
Binary: libjs-jquery-i18n-properties
Architecture: source all
Version: 1.2.7+dfsg1-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Javascript Maintainers 

Changed-By: Mike Gabriel 
Description:
 libjs-jquery-i18n-properties - lightweight jQuery internationalization plugin
Closes: 979521 980416
Changes:
 jquery-i18n-properties (1.2.7+dfsg1-1) unstable; urgency=medium
 .
   * Re-upload to unstable as NEW. (Closes: #980416).
 This also solves a missing-dependency-problem for
 openboard(-common). (Closes: #979521).
 .
   * New upstream release.
   * debian/:
 + Repack orig tarball (drop min.js file).
   * debian/*:
 + Update to new upstream origin.
   * debian/patches/2001_use-Debian-s-jquery.patch:
 + Don't use external URL for loading jQuery. Use local paths for loading
   Javascript library files.
   * debian/{control,compat}:
 + Switch to debhelper-compat notation, bump to DH compat level version 13.
   * debian/control:
 + Update Vcs-*: fields. Package has long ago been moved to Salsa.
 + Add myself to Uploaders: field. Drop Daniel Pocock.
 + Add Rules-Requires-Root: field and set it to 'no'.
 + Re-arrange packages in B-D and D fields.
 + Bump Standards-Version: to 4.5.1. No changes needed.
 + White-space fix.
 * Change Section: to 'javascript'.
   * debian/copyright:
 + Rename MIT license tag to Expat.
 + Use https URL in Format: field.
   * debian/rules:
 + Add get-orig-source target.
 + Add dh_clean override, Remove generated *-min.js file during clean-up.
   * debian/{rules,docs,examples}:
 + Handle example files by dh_installexamples.
   * debian/libjs-jquery-i18n-properties.lintian-overrides:
 + Rename lintian tag.
   * debian/upstream/metadata:
 + Add file. Comply with DEP-12.
   * debian/libjs-jquery-i18n-properties.install:
 + Install -min.js and .js file.
Checksums-Sha1:
 f14b7fa19b81350acf92055629b74fc1438901e7 2205 
jquery-i18n-properties_1.2.7+dfsg1-1.dsc
 c7d36d59ae886d32d96f3d0895cea19f83f4fd86 131344 
jquery-i18n-properties_1.2.7+dfsg1.orig.tar.xz
 04469ab68c5e8dda1b1736744997e70204e870ca 3720 
jquery-i18n-properties_1.2.7+dfsg1-1.debian.tar.xz
 e22e2987b1393d6fccf26d459dc976a48f31444d 7631 
jquery-i18n-properties_1.2.7+dfsg1-1_amd64.buildinfo
 60835ea3ecf276b80b1274e5461a3a06427b19a4 133488 
libjs-jquery-i18n-properties_1.2.7+dfsg1-1_all.deb
Checksums-Sha256:
 b26e4db210734265b3ad2c1c30e938eac1fed96c3a8e9afc758272e88e967e22 2205 
jquery-i18n-properties_1.2.7+dfsg1-1.dsc
 a14000aa2252b2e41c9223f06ad28d7952afa4b0d2b18d7d3557be6b43d3a6f1 131344 
jquery-i18n-properties_1.2.7+dfsg1.orig.tar.xz
 d79853ffe348db60c8f12977bf12eb81b60b7afabec89278b2bb3c7defcfa4a7 3720 
jquery-i18n-properties_1.2.7+dfsg1-1.debian.tar.xz
 b1588e1c1ffad94be55aac001addb835cfc1d767ea60efed502b7480512ab5e9 7631 
jquery-i18n-properties_1.2

Processed: Re: Bug#980956 closed by Debian FTP Masters (reply to cru...@debian.org (Michael R. Crusoe)) (Bug#980956: fixed in r-cran-dbplyr 2.0.0-2)

[Debian Bug Tracking System]

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

> # fix meta data, otherwise bts and britney can't figure it out
> reassign 980956 src:r-cran-dbplyr 1.4.4-1
Bug #980956 {Done: Michael R. Crusoe } [src:r-cran-magrittr, 
src:r-cran-dbplyr] r-cran-magrittr breaks r-cran-dbplyr autopkgtest: could not 
find function "split_chain"
Bug reassigned from package 'src:r-cran-magrittr, src:r-cran-dbplyr' to 
'src:r-cran-dbplyr'.
No longer marked as found in versions r-cran-magrittr/2.0.1-1 and 
r-cran-dbplyr/1.4.4-1.
No longer marked as fixed in versions r-cran-dbplyr/2.0.0-2.
Bug #980956 {Done: Michael R. Crusoe } [src:r-cran-dbplyr] 
r-cran-magrittr breaks r-cran-dbplyr autopkgtest: could not find function 
"split_chain"
Marked as found in versions r-cran-dbplyr/1.4.4-1.
> affects 980956 src:r-cran-magrittr
Bug #980956 {Done: Michael R. Crusoe } [src:r-cran-dbplyr] 
r-cran-magrittr breaks r-cran-dbplyr autopkgtest: could not find function 
"split_chain"
Added indication that 980956 affects src:r-cran-magrittr
> fixed 980956 2.0.0-2
Bug #980956 {Done: Michael R. Crusoe } [src:r-cran-dbplyr] 
r-cran-magrittr breaks r-cran-dbplyr autopkgtest: could not find function 
"split_chain"
Marked as fixed in versions r-cran-dbplyr/2.0.0-2.
> thanks
Stopping processing here.

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

Bug#980115: connection failure when rx initialized after 08:25:36 GMT 14 Jan 2021

[Salvatore Bonaccorso]

HI Benjamin,

On Mon, Jan 18, 2021 at 07:19:14PM -0800, Benjamin Kaduk wrote:
> On Mon, Jan 18, 2021 at 06:04:39PM +, Jeremy Stanley wrote:
> > Thanks for pulling this into unstable and testing! Is there any work
> > in progress to fix it in stable as well? I took a quick peek in
> > Salsa and didn't see any merge requests or an obvious branch for
> > Buster's 1.8.2 (just the debian/1.8.2-1 tag).
> 
> It is a clear candidate to fix in stable, though the only concrete steps
> I've been able to take so far are to confirm with the security team that it
> is not a candidate for being fixed via a DSA.
> 
> The actual work of backporting the patches should be ~trivial, so the
> process work of engaging with the release team will be the dominating
> factor.

Do you still have this on your radar? While as discussed this is not a
DSA candidate a fix can be released out of order from a point release
via the stable-updates mechanism, and this would be defintively a
canddiate for it.

The procedure would be the same as proposing the fix to be rleased in
a point release, but mentioning to the SRM that the fix actually needs
to go out sooner (should be clear from context here), and pushed via a
SUA.

https://lists.debian.org/debian-devel-announce/2011/03/msg00010.html
https://lists.debian.org/debian-stable-announce/
https://wiki.debian.org/StableUpdates

I think this becomes now even more urgent as users will roll out the
linux update released as DSA 4843-1 or latest at the 10.8 point
release on weekend and make the issue more urgent.

Hope this helps!

Regards,
Salvatore

Bug#980626: marked as done (pocl: FTBFS: E: Build killed with signal TERM after 150 minutes of inactivity)

[Debian Bug Tracking System]

Your message dated Wed, 03 Feb 2021 20:33:37 +
with message-id 
and subject line Bug#980626: fixed in pocl 1.6-4
has caused the Debian Bug report #980626,
regarding pocl: FTBFS: E: Build killed with signal TERM after 150 minutes of 
inactivity
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.)


-- 
980626: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=980626
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pocl
Version: 1.6-3
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20210120 ftbfs-bullseye

Hi,

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

Relevant part (hopefully):
> 132/141 Test  #81: regression/test_program_from_binary_with_local_1_1_1_LOOPS 
> ..   Passed2.52 sec
> Start  84: regression/passing_a_constant_array_as_an_arg
> 133/141 Test  #82: 
> regression/setting_a_buffer_argument_to_NULL_causes_a_segfault 
> ..   Passed2.10 sec
> Start  85: 
> regression/case_with_multiple_variable_length_loops_and_a_barrier_in_one
> 134/141 Test  #83: 
> regression/clSetKernelArg_overwriting_the_previous_kernel's_args 
>    Passed1.89 sec
> Start  86: regression/autolocals_in_constexprs
> 135/141 Test  #84: regression/passing_a_constant_array_as_an_arg 
> ...   Passed1.72 sec
> Start  87: regression/struct_kernel_arguments
> 136/141 Test  #85: 
> regression/case_with_multiple_variable_length_loops_and_a_barrier_in_one 
>    Passed1.91 sec
> Start  88: regression/vector_kernel_arguments
> 137/141 Test  #86: regression/autolocals_in_constexprs 
> .   Passed1.78 sec
> Start 137: examples/vecadd_large_grid
> 138/141 Test #137: examples/vecadd_large_grid 
> ..   Passed0.66 
> sec
> 139/141 Test  #87: regression/struct_kernel_arguments 
> ..   Passed2.08 sec
> 140/141 Test  #88: regression/vector_kernel_arguments 
> ..   Passed1.25 sec
> E: Build killed with signal TERM after 150 minutes of inactivity

The full build log is available from:
   http://qa-logs.debian.net/2021/01/20/pocl_1.6-3_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: pocl
Source-Version: 1.6-4
Done: Andreas Beckmann 

We believe that the bug you reported is fixed in the latest version of
pocl, 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.
Andreas Beckmann  (supplier of updated pocl 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: Wed, 03 Feb 2021 21:21:03 +0100
Source: pocl
Architecture: source
Version: 1.6-4
Distribution: unstable
Urgency: medium
Maintainer: Debian OpenCL Maintainers 
Changed-By: Andreas Beckmann 
Closes: 980626
Changes:
 pocl (1.6-4) unstable; urgency=medium
 .
   * Restore setting unroll-threshold on LLVM 9 to avoid kernel/test_rotate
 hanging on avx512 capable cpus.  (Closes: #980626)
   * Kill hanging tests after 30 minutes.
   * Let dh_shlibdeps find libpocl-devices-basic.so.
   * Do not use the embedded copy of the OpenCL headers.
   * Build with -fvisibility-inlines-hidden.
   * Drop hidden symbols.
   * Bump Standards-V

Bug#981793: varmon: maintainer address bounces

[Chris Hofstaedtler]

Source: varmon
Version: 1.2.1-1
Severity: serious

Julien Danjou  is no longer a Debian Developer, and
his mail address has started bouncing.

Someone will need to take care of this package.

Chris

Bug#981763: marked as done (json2file-go: missing dependency on libcap2-bin)

[Debian Bug Tracking System]

Your message dated Wed, 03 Feb 2021 20:21:55 +
with message-id 
and subject line Bug#981763: fixed in json2file-go 1.14
has caused the Debian Bug report #981763,
regarding json2file-go: missing dependency on libcap2-bin
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.)


-- 
981763: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=981763
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: json2file-go
Version: 1.13
Severity: serious

https://piuparts.debian.org/sid/fail/json2file-go_1.13.log

...
  Unpacking json2file-go (1.13) ...
  Setting up json2file-go (1.13) ...
  /var/lib/dpkg/info/json2file-go.postinst: 23: setcap: not found
  dpkg: error processing package json2file-go (--configure):
   installed json2file-go package post-installation script subprocess returned 
error exit status 127
  Errors were encountered while processing:
   json2file-go
  E: Sub-process /usr/bin/dpkg returned an error code (1)
--- End Message ---
--- Begin Message ---
Source: json2file-go
Source-Version: 1.14
Done: Sergio Talens-Oliag 

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

Debian distribution maintenance software
pp.
Sergio Talens-Oliag  (supplier of updated json2file-go 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: Wed, 03 Feb 2021 21:01:39 +0100
Source: json2file-go
Binary: json2file-go
Architecture: source amd64
Version: 1.14
Distribution: unstable
Urgency: medium
Maintainer: Sergio Talens-Oliag 
Changed-By: Sergio Talens-Oliag 
Description:
 json2file-go - simple web server that stores JSON files sent by WebHooks
Closes: 981763
Changes:
 json2file-go (1.14) unstable; urgency=medium
 .
   * Added dependency on libcap2-bin (closes: Bug#981763).
   * Updated standards (no changes).
Checksums-Sha1:
 c01ae253f26f58e5724dddc121d117bee9e0bfdd 1761 json2file-go_1.14.dsc
 45f549fe9b366bdfcf83569784f38cca38a9f8b1 17644 json2file-go_1.14.tar.xz
 1030a6e5424bff34bbc2614b1ddd97f053bb5a83 6325 json2file-go_1.14_amd64.buildinfo
 8a3a04205f124a867ff81b07b0eade593c96e492 1582496 json2file-go_1.14_amd64.deb
Checksums-Sha256:
 65c7e09b12ad54fe45a5e9183e0b5aadbdc7c78a7c1d0009adc732d7c6ab036c 1761 
json2file-go_1.14.dsc
 178a3d48d46a90ca0165dcb53b5e718d65b24f99d80af7e21c83eb11f1ec47ca 17644 
json2file-go_1.14.tar.xz
 fa78ffbd476e747268630fb93c1dca60de1c39f39f6f0d0c8fcf82f69d6d2a7f 6325 
json2file-go_1.14_amd64.buildinfo
 6e8e6785b647ec41754f4827915a00f4336c22ee66d56b939e1eea3766e7634c 1582496 
json2file-go_1.14_amd64.deb
Files:
 25e892c72c740c411cab3b5184441834 1761 net optional json2file-go_1.14.dsc
 f430b422287511d6b2d3ac04d8db7949 17644 net optional json2file-go_1.14.tar.xz
 febd6449c4162f608ea94000a6911fa9 6325 net optional 
json2file-go_1.14_amd64.buildinfo
 e49a6747c4c0cc11cc2b9b73048acbab 1582496 net optional 
json2file-go_1.14_amd64.deb

-BEGIN PGP SIGNATURE-

iQJDBAEBCAAtFiEE+pCORxrTfX8jY9ePghruD9Fn+98FAmAbAaYPHHN0b0BkZWJp
YW4ub3JnAAoJEIIa7g/RZ/vf7xMQAJpNpFlmWDSOWqSkshtwg0UVX+zB8VZ8u2Qj
aalIywaWlPpopeSme/0E18zuXSw08zhZ+CDr7BtRaLTzGwOQrIbxYpjGUAiehgcd
2QHXAvS0WMpBe44ecYaPEfENVostBpmT3pyrgvzOL2cozEyZ2WTXh4tzlnfcYUFN
s3UAtR+CvmntR2cqd9aSingAedou4yr7xfRdSROGqhWGCmNkP/Q+OhXDO1XlC239
2cf2XfRHJYO9OI04H7+WNDNxXevdfB0YZcUUIkJdDvqDltoiayTJLeXJF5rafWF7
kzWzmEN3pdp/4q3Ig29kU3wPDMPdDYVCbFrTBW0JcY8he7fZ8G/d1eSl6k3ICiPb
wFnA1rqGAPpjDfj0STp+dxubFzUGHmPDOZS9Y8W4zHXYHef0wLeL15+gxr0/FCp4
PoZtpNPl93tr51hIzFQ+O/Vw7Eeki/3MI8v/HrAVKZ07O5MJjKLqcgpVJWVUQCBf
RR5njje4wE/dRb7im6BkUWHJXajDaQp9Zu1MI+tpRSZyCHbHZgrDUNsaF50HTcu0
j6U87XLMqj8FZ4tkYOVYXW0gSBY2b06/eVWXNd/DrLe4IvHm69u/HKmmViiLbB5e
5aEQLOfhxgzmJcheae5use96aWTM4WCTpsEb4K+rBj4gXPqvrvNxwF6QmNFQsFlF
fpWLCFiR
=AsQZ
-END PGP SIGNATURE End Message ---

Bug#981672: marked as done (libnitrokey FTBFS on !amd64/arm64: symbol differences)

[Debian Bug Tracking System]

Your message dated Wed, 03 Feb 2021 20:22:00 +
with message-id 
and subject line Bug#981672: fixed in libnitrokey 3.5-3.3
has caused the Debian Bug report #981672,
regarding libnitrokey FTBFS on !amd64/arm64: symbol differences
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.)


-- 
981672: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=981672
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libnitrokey
Version: 3.5-3.1
Severity: serious
Tags: ftbfs

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

Symbol files for C++ libraries are usually problematic:
https://wiki.debian.org/UsingSymbolsFiles
--- End Message ---
--- Begin Message ---
Source: libnitrokey
Source-Version: 3.5-3.3
Done: Patryk Cisek 

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

Debian distribution maintenance software
pp.
Patryk Cisek  (supplier of updated libnitrokey 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: Wed, 03 Feb 2021 11:34:35 -0800
Source: libnitrokey
Architecture: source
Version: 3.5-3.3
Distribution: unstable
Urgency: high
Maintainer: Scott Kitterman 
Changed-By: Patryk Cisek 
Closes: 981672
Changes:
 libnitrokey (3.5-3.3) unstable; urgency=high
 .
   * Non-maintainer upload.
   * Source-only upload to make the fix into Bullseye. (Closes: 981672)
Checksums-Sha1:
 a2b3acd1ac53075dfabbeca262a93ef1082fc5cd 1750 libnitrokey_3.5-3.3.dsc
 aaab353a9f553a05080002ef41db4f89eee6912c 4568 libnitrokey_3.5-3.3.debian.tar.xz
 47ad6fc93fc78102f1aaf9ae545c9d2363db44fd 7702 
libnitrokey_3.5-3.3_amd64.buildinfo
Checksums-Sha256:
 2d81a69a936ddd46ed9b513b966c1daf603ea22aa27db9d945af90b6d9f56f2d 1750 
libnitrokey_3.5-3.3.dsc
 13ce7398f1685e016c73cb2a6835580d6eff28759b86622e770c315fd7707318 4568 
libnitrokey_3.5-3.3.debian.tar.xz
 d259bbc540c72e7f664ebc77c8e375f5ef1f0e1d787ee0f6fd5be2af7e328035 7702 
libnitrokey_3.5-3.3_amd64.buildinfo
Files:
 57cc7769fcbbcfd325771f4da593b149 1750 libs optional libnitrokey_3.5-3.3.dsc
 fddfb76d255029ce6d93ddbd8527a160 4568 libs optional 
libnitrokey_3.5-3.3.debian.tar.xz
 61146afa4701ad214a7217fc90bf52bf 7702 libs optional 
libnitrokey_3.5-3.3_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQFGBAEBCAAwFiEEWOLp/jzhNNGOMgPUXJhqlBtsgvUFAmAa/6wSHHBhdHJ5a0Bk
ZWJpYW4ub3JnAAoJEFyYapQbbIL1heYH+wT16Yw1EHID3ZCafYx/5TZVKHtatRsS
SgjakRX5uPC38D7AdVXZP4Xz/fmLQWyWZdCm/1FYQ+suEM1q5U/oO/jOETW6NN2h
twXn1I/yoywbMddCAeMGuu3O8ASoIcw+MeIpKWpwio7keVmfJnbh8ZaYRM805i70
DldS9aBW2jSy7rC1QCI0W48h4zSj/5DQMrQf4w12TV+XfhvW6nW6W1qFuIy+0mN+
9GPxdv7q3oUOEU0njM7ZYoUPLI/E8B0Gi1Enpb9SjTroWKB1bZD2ORqyVSa0tb1v
HkzyRX/7HtYPcgvXCkD6I0I92ap4W3aN+7bus+mbWVB8LxJoVKNa+Bc=
=leLK
-END PGP SIGNATURE End Message ---

Bug#980134: Keep shaarli (and dependencies) out of Bullseye? (Was: Bug#980134: shaarli: Missing minified js and css for frontend)

[David Prévot]

Hi James,

Le Thu, Jan 14, 2021 at 07:05:21PM -0500, James Valleroy a écrit :
[…]
> While the packaged shaarli is technically usable, it is missing both
> functionality and styling that would be expected by users. Therefore
> it should be kept out of stable releases until this issue is fixed.

Given the above (and the freeze schedule), it looks like shaarli won’t
be part of Bullseye. Do you intend to also request the removal of its
(build-)dependencies (e.g., via such kind of RC-bug), or do you intend
to maintain them all during the Bullseye lifetime (wrt security issues)?

Regards

David


signature.asc
Description: PGP signature

Bug#981420: marked as done (libglib2.0-0: gnome-keyring unable to unlock login keyring on some systems since GLib 2.66.4-2)

[Debian Bug Tracking System]

Your message dated Wed, 03 Feb 2021 19:33:21 +
with message-id 
and subject line Bug#981555: fixed in glib2.0 2.66.4-4
has caused the Debian Bug report #981555,
regarding libglib2.0-0: gnome-keyring unable to unlock login keyring on some 
systems since GLib 2.66.4-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.)


-- 
981555: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=981555
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libglib2.0-0
Version: 2.66.4-1
Severity: important
Tags: upstream
X-Debbugs-Cc: malahee...@gmx.fr

Dear maintainer,

After the recent update of libglib2.0 to 2.66.4-3, gnome-keyring is not able to
unlock "Login" keyring. For example, it does not allow to unlock saved ssh keys
automatically; ssh/ssh-agent starts to ask for a password in CLI instead of
fancy popup window.

The downgrading to 2.66.4-1 solves the problem.

Could you take a look?

Thank you!



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

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

Versions of packages libglib2.0-0 depends on:
ii  libc62.31-9
ii  libffi7  3.3-5
ii  libmount12.36.1-6
ii  libpcre3 2:8.39-13
ii  libselinux1  3.1-2+b2
ii  zlib1g   1:1.2.11.dfsg-2

Versions of packages libglib2.0-0 recommends:
hi  libglib2.0-data   2.66.4-1
ii  shared-mime-info  2.0-1
ii  xdg-user-dirs 0.17-2

libglib2.0-0 suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: glib2.0
Source-Version: 2.66.4-4
Done: Simon McVittie 

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

Debian distribution maintenance software
pp.
Simon McVittie  (supplier of updated glib2.0 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: Wed, 03 Feb 2021 13:55:41 +
Source: glib2.0
Architecture: source
Version: 2.66.4-4
Distribution: unstable
Urgency: medium
Maintainer: Debian GNOME Maintainers 

Changed-By: Simon McVittie 
Closes: 981420 981555
Changes:
 glib2.0 (2.66.4-4) unstable; urgency=medium
 .
   * d/patches: Update patch series to upstream commit 2.66.4-27-g0051c0635
 - Improve test coverage for #977961
 - Stop valgrind reporting memory leaks in GSpawn in most cases
 - Partially revert security hardening from 2.66.4-2: allow
   DBUS_SESSION_BUS_ADDRESS to be taken from the environment by
   setcap executables (to avoid regressing gnome-keyring) and by
   setgid executables (to avoid regressing msmtp).
   (Closes: #981420, #981555)
   Note that this is likely to be reverted in GLib 2.70.x to provide
   better hardening. The D-Bus session bus is not designed to be used
   by processes that have elevated privileges.
Checksums-Sha1:
 d0e92077e8af39e2eea4a1595b753133d814c693 3386 glib2.0_2.66.4-4.dsc
 bb44ba8896126491bde309cd95f4d965f557438a 110116 glib2.0_2.66.4-4.debian.tar.xz
 0a0f1577b386264431f0647f4ab20c51b00bee4a 7874 glib2.0_2.66.4-4_source.buildinfo
Checksums-Sha256:
 03a827db68245e90a6a3b7b7b777eafa8173678ae97110649d2a6bba50b6 3386 
glib2.0_2.66.4-4.dsc
 5a61aa6f9f88803a3ec6703b12567343f19362e518e1826f094e0bcfac6a6259 110116 
glib2.0_2.66.4-4.debian.tar.xz
 11724677ff6af3d8a1e6cc22c2d5e8f91bf0b5f91ad47fb4f24598591a524129 7874 
glib2.0_2.66.4-4_source.buildinfo
Files:
 5b5b5bce7f861fc97d59a5bc55e48953 3386 libs optional glib2.0_2.66.4-4.dsc
 322dda88d7b12b8373de2a175920f7f8 110116 libs optional 
glib2.0_2.66.4-4.debian.tar.xz
 699e6f6cfe9cbd4d48e669555e50ca81 7874 libs optional 
glib2.0_2.66.4-4_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEENuxaZEik9e95vv6Y4FrhR4+BTE8FAmAa9SEACgkQ4FrhR4+B
TE9X1A/8DqIfOtQzIBEtfXIUcbEHqqio

Bug#981555: marked as done (gnome-keyring: unable to connect to D-Bus when using dbus-x11)

[Debian Bug Tracking System]

Your message dated Wed, 03 Feb 2021 19:33:21 +
with message-id 
and subject line Bug#981555: fixed in glib2.0 2.66.4-4
has caused the Debian Bug report #981555,
regarding gnome-keyring: unable to connect to D-Bus when using dbus-x11
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.)


-- 
981555: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=981555
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gnome-keyring
Version: 3.36.0-1
Severity: important

Dear maintainers,

Since this work week Evolution on my laptop does not ask for GNOME keyring
password anymore. Instead after some kind of a timeout it directly asks
for the password of the connection.

It does so for retrieving mails, for sending mails, for calendar and 
addressbook access. I am using Evolution EWS with Office 365.

Since this worked before I do not consider this to be an upstream issue.
However also 'gnome-keyring' package does not appear to have been changed
recently. So it may be related to the upgrade of a different package.

I do see

kdeinit5: Got EXEC_NEW 'dbus-send' from launcher.
kdeinit5: preparing to launch 'libkdeinit5_dbus-send'
Could not open dbus-send using a library: Cannot load library 
libkdeinit5_dbus-send: (libkdeinit5_dbus-send: Kann die Shared-Object-Datei 
nicht öffnen: Datei oder Verzeichnis nicht gefunden)
kdeinit5: PID 13520 terminated.

in ~/.xsession-errors which may be related.

However I did not find 'libkdeinit5_dbus-send' anywhere with 'apt-file search'.

GNOME Keyring daemon, which to my understanding provides Secrets Services
DBUS API, is running, excerpt from 'ps aux':

someuser   13491  0.0  0.0  15756  4984 ?SL   08:52   0:00 
/usr/bin/gnome-keyring-daemon --daemonize --login

However also 'qdbus' reports that the DBUS API is not accessible:

% qdbus org.freedesktop.secrets 
Error: org.freedesktop.DBus.Error.NoReply
Did not receive a reply. Possible causes include: the remote application did 
not send a reply, the message bus security policy blocked the reply, the reply 
timeout expired, or the network connection was broken.

It does not even seem to exist:

% qdbus | grep secrets
[… nothing …]

However also if started manually GNOME Keyring does not report an error:

% /usr/bin/gnome-keyring-daemon --login
[… keeps running, no output, even after Evolution failing to connect DBUS
API …]

I am using Runit as PID 1. This has not been an issue before.

Thanks,
Martin

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

Kernel: Linux 5.11.0-rc6-tp520 (SMP w/4 CPU threads; PREEMPT)
Kernel taint flags: TAINT_WARN, TAINT_OOT_MODULE
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: runit (via /run/runit.stopit)
LSM: AppArmor: enabled

Versions of packages gnome-keyring depends on:
ii  dbus-x11 [dbus-session-bus]  1.12.20-1
ii  dconf-gsettings-backend [gsettings-backend]  0.38.0-1
ii  gcr  3.38.1-1
ii  libc62.31-9
ii  libcap-ng0   0.7.9-2.2+b1
ii  libcap2-bin  1:2.44-1
ii  libgck-1-0   3.38.1-1
ii  libgcr-base-3-1  3.38.1-1
ii  libgcrypt20  1.8.7-2
ii  libglib2.0-0 2.66.4-3
ii  p11-kit  0.23.22-1
ii  pinentry-gnome3  1.1.0-4

Versions of packages gnome-keyring recommends:
ii  gnome-keyring-pkcs11  3.36.0-1
ii  libpam-gnome-keyring  3.36.0-1

gnome-keyring suggests no packages.

-- debconf-show failed
--- End Message ---
--- Begin Message ---
Source: glib2.0
Source-Version: 2.66.4-4
Done: Simon McVittie 

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

Debian distribution maintenance software
pp.
Simon McVittie  (supplier of updated glib2.0 package)

(This message was generated automatically at their request; if you
believe that there is a p

Bug#981555: marked as done (gnome-keyring: unable to connect to D-Bus when using dbus-x11)

[Debian Bug Tracking System]

Your message dated Wed, 03 Feb 2021 19:33:21 +
with message-id 
and subject line Bug#981420: fixed in glib2.0 2.66.4-4
has caused the Debian Bug report #981420,
regarding gnome-keyring: unable to connect to D-Bus when using dbus-x11
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.)


-- 
981420: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=981420
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gnome-keyring
Version: 3.36.0-1
Severity: important

Dear maintainers,

Since this work week Evolution on my laptop does not ask for GNOME keyring
password anymore. Instead after some kind of a timeout it directly asks
for the password of the connection.

It does so for retrieving mails, for sending mails, for calendar and 
addressbook access. I am using Evolution EWS with Office 365.

Since this worked before I do not consider this to be an upstream issue.
However also 'gnome-keyring' package does not appear to have been changed
recently. So it may be related to the upgrade of a different package.

I do see

kdeinit5: Got EXEC_NEW 'dbus-send' from launcher.
kdeinit5: preparing to launch 'libkdeinit5_dbus-send'
Could not open dbus-send using a library: Cannot load library 
libkdeinit5_dbus-send: (libkdeinit5_dbus-send: Kann die Shared-Object-Datei 
nicht öffnen: Datei oder Verzeichnis nicht gefunden)
kdeinit5: PID 13520 terminated.

in ~/.xsession-errors which may be related.

However I did not find 'libkdeinit5_dbus-send' anywhere with 'apt-file search'.

GNOME Keyring daemon, which to my understanding provides Secrets Services
DBUS API, is running, excerpt from 'ps aux':

someuser   13491  0.0  0.0  15756  4984 ?SL   08:52   0:00 
/usr/bin/gnome-keyring-daemon --daemonize --login

However also 'qdbus' reports that the DBUS API is not accessible:

% qdbus org.freedesktop.secrets 
Error: org.freedesktop.DBus.Error.NoReply
Did not receive a reply. Possible causes include: the remote application did 
not send a reply, the message bus security policy blocked the reply, the reply 
timeout expired, or the network connection was broken.

It does not even seem to exist:

% qdbus | grep secrets
[… nothing …]

However also if started manually GNOME Keyring does not report an error:

% /usr/bin/gnome-keyring-daemon --login
[… keeps running, no output, even after Evolution failing to connect DBUS
API …]

I am using Runit as PID 1. This has not been an issue before.

Thanks,
Martin

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

Kernel: Linux 5.11.0-rc6-tp520 (SMP w/4 CPU threads; PREEMPT)
Kernel taint flags: TAINT_WARN, TAINT_OOT_MODULE
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: runit (via /run/runit.stopit)
LSM: AppArmor: enabled

Versions of packages gnome-keyring depends on:
ii  dbus-x11 [dbus-session-bus]  1.12.20-1
ii  dconf-gsettings-backend [gsettings-backend]  0.38.0-1
ii  gcr  3.38.1-1
ii  libc62.31-9
ii  libcap-ng0   0.7.9-2.2+b1
ii  libcap2-bin  1:2.44-1
ii  libgck-1-0   3.38.1-1
ii  libgcr-base-3-1  3.38.1-1
ii  libgcrypt20  1.8.7-2
ii  libglib2.0-0 2.66.4-3
ii  p11-kit  0.23.22-1
ii  pinentry-gnome3  1.1.0-4

Versions of packages gnome-keyring recommends:
ii  gnome-keyring-pkcs11  3.36.0-1
ii  libpam-gnome-keyring  3.36.0-1

gnome-keyring suggests no packages.

-- debconf-show failed
--- End Message ---
--- Begin Message ---
Source: glib2.0
Source-Version: 2.66.4-4
Done: Simon McVittie 

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

Debian distribution maintenance software
pp.
Simon McVittie  (supplier of updated glib2.0 package)

(This message was generated automatically at their request; if you
believe that there is a p

Bug#981420: marked as done (libglib2.0-0: gnome-keyring unable to unlock login keyring on some systems since GLib 2.66.4-2)

[Debian Bug Tracking System]

Your message dated Wed, 03 Feb 2021 19:33:21 +
with message-id 
and subject line Bug#981420: fixed in glib2.0 2.66.4-4
has caused the Debian Bug report #981420,
regarding libglib2.0-0: gnome-keyring unable to unlock login keyring on some 
systems since GLib 2.66.4-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.)


-- 
981420: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=981420
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libglib2.0-0
Version: 2.66.4-1
Severity: important
Tags: upstream
X-Debbugs-Cc: malahee...@gmx.fr

Dear maintainer,

After the recent update of libglib2.0 to 2.66.4-3, gnome-keyring is not able to
unlock "Login" keyring. For example, it does not allow to unlock saved ssh keys
automatically; ssh/ssh-agent starts to ask for a password in CLI instead of
fancy popup window.

The downgrading to 2.66.4-1 solves the problem.

Could you take a look?

Thank you!



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

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

Versions of packages libglib2.0-0 depends on:
ii  libc62.31-9
ii  libffi7  3.3-5
ii  libmount12.36.1-6
ii  libpcre3 2:8.39-13
ii  libselinux1  3.1-2+b2
ii  zlib1g   1:1.2.11.dfsg-2

Versions of packages libglib2.0-0 recommends:
hi  libglib2.0-data   2.66.4-1
ii  shared-mime-info  2.0-1
ii  xdg-user-dirs 0.17-2

libglib2.0-0 suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: glib2.0
Source-Version: 2.66.4-4
Done: Simon McVittie 

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

Debian distribution maintenance software
pp.
Simon McVittie  (supplier of updated glib2.0 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: Wed, 03 Feb 2021 13:55:41 +
Source: glib2.0
Architecture: source
Version: 2.66.4-4
Distribution: unstable
Urgency: medium
Maintainer: Debian GNOME Maintainers 

Changed-By: Simon McVittie 
Closes: 981420 981555
Changes:
 glib2.0 (2.66.4-4) unstable; urgency=medium
 .
   * d/patches: Update patch series to upstream commit 2.66.4-27-g0051c0635
 - Improve test coverage for #977961
 - Stop valgrind reporting memory leaks in GSpawn in most cases
 - Partially revert security hardening from 2.66.4-2: allow
   DBUS_SESSION_BUS_ADDRESS to be taken from the environment by
   setcap executables (to avoid regressing gnome-keyring) and by
   setgid executables (to avoid regressing msmtp).
   (Closes: #981420, #981555)
   Note that this is likely to be reverted in GLib 2.70.x to provide
   better hardening. The D-Bus session bus is not designed to be used
   by processes that have elevated privileges.
Checksums-Sha1:
 d0e92077e8af39e2eea4a1595b753133d814c693 3386 glib2.0_2.66.4-4.dsc
 bb44ba8896126491bde309cd95f4d965f557438a 110116 glib2.0_2.66.4-4.debian.tar.xz
 0a0f1577b386264431f0647f4ab20c51b00bee4a 7874 glib2.0_2.66.4-4_source.buildinfo
Checksums-Sha256:
 03a827db68245e90a6a3b7b7b777eafa8173678ae97110649d2a6bba50b6 3386 
glib2.0_2.66.4-4.dsc
 5a61aa6f9f88803a3ec6703b12567343f19362e518e1826f094e0bcfac6a6259 110116 
glib2.0_2.66.4-4.debian.tar.xz
 11724677ff6af3d8a1e6cc22c2d5e8f91bf0b5f91ad47fb4f24598591a524129 7874 
glib2.0_2.66.4-4_source.buildinfo
Files:
 5b5b5bce7f861fc97d59a5bc55e48953 3386 libs optional glib2.0_2.66.4-4.dsc
 322dda88d7b12b8373de2a175920f7f8 110116 libs optional 
glib2.0_2.66.4-4.debian.tar.xz
 699e6f6cfe9cbd4d48e669555e50ca81 7874 libs optional 
glib2.0_2.66.4-4_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEENuxaZEik9e95vv6Y4FrhR4+BTE8FAmAa9SEACgkQ4FrhR4+B
TE9X1A/8DqIfOtQzIBEtfXIUcbEHqqio

Processed: Bug#981420 marked as pending in glib2.0

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #981420 [libglib2.0-0] libglib2.0-0: gnome-keyring unable to unlock login 
keyring on some systems since GLib 2.66.4-2
Bug #981555 [libglib2.0-0] gnome-keyring: unable to connect to D-Bus when using 
dbus-x11
Added tag(s) pending.
Added tag(s) pending.

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

Bug#981555: marked as pending in glib2.0

[Simon McVittie]

Control: tag -1 pending

Hello,

Bug #981555 in glib2.0 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/gnome-team/glib/-/commit/90a7c8c91bdd7254aa266ce2f2ab42998a2bfdcc


Update patch series to upstream commit 2.66.4-27-g0051c0635

Closes: #981420
Closes: #981555


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/981555

Processed: Bug#981555 marked as pending in glib2.0

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #981555 [libglib2.0-0] gnome-keyring: unable to connect to D-Bus when using 
dbus-x11
Bug #981420 [libglib2.0-0] libglib2.0-0: gnome-keyring unable to unlock login 
keyring on some systems since GLib 2.66.4-2
Ignoring request to alter tags of bug #981555 to the same tags previously set
Ignoring request to alter tags of bug #981420 to the same tags previously set

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

Bug#981420: marked as pending in glib2.0

[Simon McVittie]

Control: tag -1 pending

Hello,

Bug #981420 in glib2.0 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/gnome-team/glib/-/commit/90a7c8c91bdd7254aa266ce2f2ab42998a2bfdcc


Update patch series to upstream commit 2.66.4-27-g0051c0635

Closes: #981420
Closes: #981555


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/981420

Bug#975822: patch attached

[Maximilian Engelhardt]

Control: tags -1 + patch

Attached is a simple patch fixing this issue in my local test build.

Adrian Bunk, you marked this bug as pending, are you planning to upload a 
fixed version or has this been a mix up in bug numbers like in your other mail 
in this bug?

Thanks,
Maxidiff -ur pyramid-jinja2-2.7+dfsg/debian/control new/pyramid-jinja2-2.7+dfsg/debian/control
--- pyramid-jinja2-2.7+dfsg/debian/control	2019-09-15 07:04:51.0 +0200
+++ new/pyramid-jinja2-2.7+dfsg/debian/control	2021-02-03 19:50:23.514196939 +0100
@@ -10,6 +10,7 @@
  python3-jinja2,
  python3-zope.deprecation,
  python3-pyramid,
+ python3-webtest,
 Standards-Version: 3.9.8
 Homepage: https://pypi.python.org/pypi/pyramid_jinja2
 X-Python3-Version: >= 3.2


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

Processed: patch attached

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + patch
Bug #975822 [src:pyramid-jinja2] pyramid-jinja2: Missing build dependency on 
python3-webtest
Added tag(s) patch.

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

Processed: retitle 981720 eventlet: doc builds fail when no resolv.conf

[Debian Bug Tracking System]

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

> retitle 981720 eventlet: doc build fails when no resolv.conf
Bug #981720 [python-eventlet] FTBFS: FileNotFoundError: [Errno 2] No such file 
or directory: '/etc/resolv.conf'
Changed Bug title to 'eventlet: doc build fails when no resolv.conf' from 
'FTBFS: FileNotFoundError: [Errno 2] No such file or directory: 
'/etc/resolv.conf''.
> severity 981720 important
Bug #981720 [python-eventlet] eventlet: doc build fails when no resolv.conf
Severity set to 'important' from 'serious'
> thanks
Stopping processing here.

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

Bug#981720: FTBFS: FileNotFoundError: [Errno 2] No such file or directory: '/etc/resolv.conf'

[Thomas Goirand]

On 2/3/21 4:10 PM, Ritesh Raj Sarraf wrote:
> On Wed, 2021-02-03 at 14:11 +0100, Thomas Goirand wrote:
>> Hi,
>>
> 
> Hi Thomas,
> 
>> Could you please explain in which build environment you don't have a
>> resolv.conf file?
>>
> 
> In an OBS build environment, where it creates chroots for the target,
> on the fly. I haven't thoroughly checked but given the error I'm fairly
> sure that the chroot may not have the file.

Ok, make sense.

>> Also, could you please send the full build log? Because like this, I
>> can't tell at which stage this happened. Was it during the build of
>> the
>> documentation?
> 
> The Reproducible Builds logs have the same issue along with the full
> build log.
> 
> https://tests.reproducible-builds.org/debian/rb-pkg/bullseye/amd64/python-eventlet.html

Ok, so as I thought, the issue is when building the docs, so probably we
can fix it by patching conf.py. I'll try to investigate it...

Cheers,

Thomas Goirand (zigo)

Bug#981765: docknot: autopkgtest failure

[Russ Allbery]

Adrian Bunk  writes:

> Source: docknot
> Version: 4.00-1
> Severity: serious

> https://ci.debian.net/data/autopkgtest/testing/amd64/d/docknot/10221864/log.gz

Thank you for relaying those results!  I forgot to go explicitly check.
Will fix shortly.

-- 
Russ Allbery (r...@debian.org)  

Processed: fixed 964195 in 1.3.0-1

[Debian Bug Tracking System]

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

> fixed 964195 1.3.0-1
Bug #964195 [src:guacamole-server] CVE-2020-9497 CVE-2020-9498
Marked as fixed in versions guacamole-server/1.3.0-1.
> thanks
Stopping processing here.

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

Bug#979641: src:kboot-utils: invalid maintainer address

[Antonio Ospite]

On Wed, 3 Feb 2021 09:43:30 +0100
Baptiste Beauplat  wrote:

[...]
> 
> I could open the RM bug on your behalf if you want me to.
> 

Thank you, I would appreciate that.

Ciao,
   Antonio

-- 
Antonio Ospite
https://ao2.it
https://twitter.com/ao2it

A: Because it messes up the order in which people normally read text.
   See http://en.wikipedia.org/wiki/Posting_style
Q: Why is top-posting such a bad thing?

Bug#888321: marked as done (guacamole-server: migrate to freerdp2)

[Debian Bug Tracking System]

Your message dated Wed, 3 Feb 2021 20:06:55 +0200
with message-id <20210203180655.GA14117@localhost>
and subject line Re: Bug#888321: guacamole-server: migrate to freerdp2
has caused the Debian Bug report #888321,
regarding guacamole-server: migrate to freerdp2
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.)


-- 
888321: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=888321
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: guacamole-server
Version: 0.9.9-2
Severity: serious

freerdp is scheduled for removal from buster. Please migrate to freerdp2.

Emilio
--- End Message ---
--- Begin Message ---
Version: 1.3.0-1

This is now fixed in unstable.

cu
Adrian--- End Message ---

Bug#900447: marked as done (Build against freerdp2)

[Debian Bug Tracking System]

Your message dated Wed, 3 Feb 2021 20:06:55 +0200
with message-id <20210203180655.GA14117@localhost>
and subject line Re: Bug#888321: guacamole-server: migrate to freerdp2
has caused the Debian Bug report #888321,
regarding Build against freerdp2
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.)


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

Package: src:guacamole-client
Severity: serious
Version: 0.9.9+dfsg-1

This bug is for tracking the efforts of porting guacamole-client to  
FreeRDP v2.


The guacamole-client package is the last blocker to having the really  
rotten old freerdp (v1.1) src:package removed from Debian unstable.


Nik and I sat down at miniDebConf HH to hack a patch together. It is  
still on my notebook and I (Nik had to leave some time during the  
work) got that far, that the configure run succeeds.


But nothing builds so far...

Greets,
Mike
--

DAS-NETZWERKTEAM
mike gabriel, herweg 7, 24357 fleckeby
mobile: +49 (1520) 1976 148
landline: +49 (4354) 8390 139

GnuPG Fingerprint: 9BFB AEE8 6C0A A5FF BF22  0782 9AF4 6B30 2577 1B31
mail: mike.gabr...@das-netzwerkteam.de, http://das-netzwerkteam.de



pgph7FvLJyQc9.pgp
Description: Digitale PGP-Signatur
--- End Message ---
--- Begin Message ---
Version: 1.3.0-1

This is now fixed in unstable.

cu
Adrian--- End Message ---

Bug#981774: fastnetmon FTBFS with ndpi 3.4

[Adrian Bunk]

Source: fastnetmon
Version: 1.1.4-1
Severity: serious
Tags: ftbfs

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/fastnetmon.html

...
/build/1st/fastnetmon-1.1.4/src/fast_dpi.cpp: In function 
'ndpi_detection_module_struct* init_ndpi()':
/build/1st/fastnetmon-1.1.4/src/fast_dpi.cpp:39:36: error: too few arguments to 
function 'ndpi_detection_module_struct* 
ndpi_init_detection_module(ndpi_init_prefs)'
   39 | ndpi_init_detection_module();
  |^
In file included from /build/1st/fastnetmon-1.1.4/src/fast_dpi.h:5,
 from /build/1st/fastnetmon-1.1.4/src/fast_dpi.cpp:1:
/usr/include/ndpi/ndpi_api.h:193:40: note: declared here
  193 |   struct ndpi_detection_module_struct 
*ndpi_init_detection_module(ndpi_init_prefs prefs);
  |^~
make[3]: *** [CMakeFiles/fast_dpi.dir/build.make:85: 
CMakeFiles/fast_dpi.dir/fast_dpi.cpp.o] Error 1
...

Bug#981770: erfs: Missing dependency on openssl

[Adrian Bunk]

Package: erfs
Version: 1.3-1
Severity: serious

https://ci.debian.net/data/autopkgtest/testing/amd64/e/erfs/10222343/log.gz

...
autopkgtest [02:03:35]: test upstream-tests: [---
/usr/bin/erfs: line 146: openssl: command not found
/usr/bin/erfs: line 146: openssl: command not found
/usr/bin/erfs: line 147: openssl: command not found
/usr/bin/erfs: line 147: openssl: command not found
/usr/bin/erfs: line 148: openssl: command not found
/usr/bin/erfs: line 148: openssl: command not found
/usr/bin/erfs: line 149: openssl: command not found
/usr/bin/erfs: line 149: openssl: command not found
fuse: device not found, try 'modprobe fuse' first
ERROR: sshfs failed.
1. The volume is already mounted.
2. Wrong SHARE-SECRET.
3. The server can not be reached.
autopkgtest [02:03:36]: test upstream-tests: ---]
autopkgtest [02:03:36]: test upstream-tests:  - - - - - - - - - - results - - - 
- - - - - - -
upstream-tests   FAIL non-zero exit status 1
autopkgtest [02:03:36]: test upstream-tests:  - - - - - - - - - - stderr - - - 
- - - - - - -
/usr/bin/erfs: line 146: openssl: command not found
/usr/bin/erfs: line 146: openssl: command not found
/usr/bin/erfs: line 147: openssl: command not found
/usr/bin/erfs: line 147: openssl: command not found
/usr/bin/erfs: line 148: openssl: command not found
/usr/bin/erfs: line 148: openssl: command not found
/usr/bin/erfs: line 149: openssl: command not found
/usr/bin/erfs: line 149: openssl: command not found
fuse: device not found, try 'modprobe fuse' first
autopkgtest [02:03:36]:  summary
upstream-tests   FAIL non-zero exit status 1

Bug#981768: python-javaobj: missing test dependencies

[Adrian Bunk]

Source: python-javaobj
Version: 0.4.1-1
Severity: serious

https://ci.debian.net/data/autopkgtest/testing/amd64/p/python-javaobj/10222335/log.gz

...
autopkgtest [02:02:41]: test command2: python3 setup.py test
autopkgtest [02:02:41]: test command2: [---
Traceback (most recent call last):
  File "/tmp/autopkgtest-lxc.ayi2uz65/downtmp/build.3OW/src/setup.py", line 34, 
in 
from setuptools import setup
ModuleNotFoundError: No module named 'setuptools'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/tmp/autopkgtest-lxc.ayi2uz65/downtmp/build.3OW/src/setup.py", line 36, 
in 
from distutils.core import setup
ModuleNotFoundError: No module named 'distutils.core'
autopkgtest [02:02:42]: test command2: ---]
autopkgtest [02:02:42]: test command2:  - - - - - - - - - - results - - - - - - 
- - - -
command2 FAIL non-zero exit status 1
autopkgtest [02:02:42]:  summary
command1 PASS
command2 FAIL non-zero exit status 1


Perhaps debian/tests/control should state something like (untested)
  Depends: @, @builddeps@

Bug#981342: marked as done (mpich: autopkgtest failure on s390x)

[Debian Bug Tracking System]

Your message dated Wed, 03 Feb 2021 17:33:33 +
with message-id 
and subject line Bug#981342: fixed in mpich 3.4.1-2
has caused the Debian Bug report #981342,
regarding mpich: autopkgtest failure on s390x
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.)


-- 
981342: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=981342
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: mpich
Version: 3.4-4
Severity: serious
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: regression

Hi Maintainer

Since the upload of mpich 3.4-4, its own autopkgtests have been
failing on s390x [1] and continue to fail in the same way with
3.4.1-1.

I've copied what I hope is the relevant part of the log below.

Regards
Graham


[1] https://ci.debian.net/packages/m/mpich/unstable/s390x/


autopkgtest [21:55:17]: test hello1: [---
Abort(1615247) on node 0 (rank 0 in comm 0): Fatal error in PMPI_Init:
Other MPI error, error stack:
MPIR_Init_thread(152)...:
MPID_Init(597)..:
MPIDI_OFI_mpi_init_hook(689):
addr_exchange_root_vni(1931): OFI get endpoint name failed
(ofi_init.c:1931:addr_exchange_root_vni:Provided buffer is too small)
autopkgtest [21:55:18]: test hello1: ---]
hello1   FAIL non-zero exit status 143
autopkgtest [21:55:18]: test hello1:  - - - - - - - - - - results - -
- - - - - - - -
autopkgtest [21:55:18]: test hello1:  - - - - - - - - - - stderr - - -
- - - - - - -
Abort(1615247) on node 0 (rank 0 in comm 0): Fatal error in PMPI_Init:
Other MPI error, error stack:
MPIR_Init_thread(152)...:
MPID_Init(597)..:
MPIDI_OFI_mpi_init_hook(689):
addr_exchange_root_vni(1931): OFI get endpoint name failed
(ofi_init.c:1931:addr_exchange_root_vni:Provided buffer is too small)
--- End Message ---
--- Begin Message ---
Source: mpich
Source-Version: 3.4.1-2
Done: Alastair McKinstry 

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

Debian distribution maintenance software
pp.
Alastair McKinstry  (supplier of updated mpich 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: Wed, 03 Feb 2021 16:08:32 +
Source: mpich
Architecture: source
Version: 3.4.1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Alastair McKinstry 
Closes: 981342
Changes:
 mpich (3.4.1-2) unstable; urgency=medium
 .
   * Don't use ch4 on s390x arch. Closes: #981342
Checksums-Sha1:
 dadf5c637cbf6ef90f6fe6f9ec27866f481913f6 2702 mpich_3.4.1-2.dsc
 e52ec98af97f8d40d0d69a1b5aaf085f57a98b28 344764 mpich_3.4.1-2.debian.tar.xz
Checksums-Sha256:
 e1359dee4a57798bdf74830e0cccb7a42ca2845952f801b009273d2f1ce6c7e3 2702 
mpich_3.4.1-2.dsc
 8f64132812784de6c1e8a65983af714333901b5a8d831b99d7df7a7af322ba59 344764 
mpich_3.4.1-2.debian.tar.xz
Files:
 20cdaf5a61d25fc9b90efd7f56c60ede 2702 devel optional mpich_3.4.1-2.dsc
 0a16bd0534d5c4e1fbec7f51410cdbff 344764 devel optional 
mpich_3.4.1-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEgjg86RZbNHx4cIGiy+a7Tl2a06UFAmAa18EACgkQy+a7Tl2a
06WzCRAAowO10BiT4pyelmykuqt7HqqAD4DU7Rc64QEyFXstIlc8VzcNy48BHwdo
T22g8x9DMh/2366AtonGPvbPFL2yt/G32En1IyEmCToappCjuXbCHFxjPEICEk7U
16fJ/9wQCLLuvBdl5D08Ruuof7FlORhBNrtgIEUkpZ7XuFjEppCqELEajyERndlH
5LHFcG5iFdxYddpTP62XrejBoVeLyAcUBkgup3Q9JBLRoN1/WZIf0RXiBvPzchbM
ZAD/AR0pvq2OjxhcRgqZV25Cqxhx/k/X21r99Xm+lJPay4w6KE4CDJ0QTNUr2HjK
jz/dqhDF0UQJQPY5QsRuvOhOdZMkmujYh5q/uopykkXm0zsZRlZO1dxxfQ/UEMXp
eClmnf9NTd8xmclvTJTV2HDnq2iDoDjx7OXItTXfSwBNeTBgA+kb4ALQYk9U0YJG
oW1u2I1o+2wWnCqiOQNp96GuuNDzL6eGiBkhsdfiaIZ2SpPFKoPWQME8wXyPc/Mg
BOp7n8QgmknZuNCgMt8x/gG22yswnCfHjiqtpgXANfjNB1AXYL5TUDt35hu+XEgR
EWrI4zAp/Z9vPMRId2Q+8KxxWJhxiXpjxBEMasVRvmG7Jyja6aEP7pGQ5an4Q6ES
MI6jf8xb/lq30XnW4oLxMF7P+nC098GrKuzwxSMTsp5B1ntZDR8=
=+/0T
-END PGP SIGNATURE End Message ---

Bug#981765: docknot: autopkgtest failure

[Adrian Bunk]

Source: docknot
Version: 4.00-1
Severity: serious

https://ci.debian.net/data/autopkgtest/testing/amd64/d/docknot/10221864/log.gz

...
Test Summary Report
---
t/cli/generate.t  (Wstat: 512 Tests: 2 Failed: 0)
  Non-zero exit status: 2
  Parse errors: Bad plan.  You planned 7 tests but ran 2.
t/dist/commands.t (Wstat: 512 Tests: 1 Failed: 0)
  Non-zero exit status: 2
  Parse errors: Bad plan.  You planned 7 tests but ran 1.
t/generate/output.t   (Wstat: 512 Tests: 1 Failed: 0)
  Non-zero exit status: 2
  Parse errors: Bad plan.  You planned 7 tests but ran 1.
t/generate/self.t (Wstat: 512 Tests: 1 Failed: 0)
  Non-zero exit status: 2
  Parse errors: Bad plan.  You planned 5 tests but ran 1.
t/style/module-version.t  (Wstat: 512 Tests: 0 Failed: 0)
  Non-zero exit status: 2
  Parse errors: No plan found in TAP output
t/style/strict.t  (Wstat: 512 Tests: 87 Failed: 2)
  Failed tests:  2-3
  Non-zero exit status: 2
Files=21, Tests=386, 12 wallclock secs ( 0.12 usr  0.02 sys + 10.12 cusr  1.34 
csys = 11.60 CPU)
Result: FAIL
...

Bug#981763: json2file-go: missing dependency on libcap2-bin

[Adrian Bunk]

Package: json2file-go
Version: 1.13
Severity: serious

https://piuparts.debian.org/sid/fail/json2file-go_1.13.log

...
  Unpacking json2file-go (1.13) ...
  Setting up json2file-go (1.13) ...
  /var/lib/dpkg/info/json2file-go.postinst: 23: setcap: not found
  dpkg: error processing package json2file-go (--configure):
   installed json2file-go package post-installation script subprocess returned 
error exit status 127
  Errors were encountered while processing:
   json2file-go
  E: Sub-process /usr/bin/dpkg returned an error code (1)

Bug#981762: chibi-scheme-images fails to install: chibi-scheme: not found

[Adrian Bunk]

Package: chibi-scheme-images
Version: 0.9.1-3
Severity: serious

https://piuparts.debian.org/sid/fail/chibi-scheme-images_0.9.1-3.log

...
  Setting up chibi-scheme-images (0.9.1-3) ...
  /var/lib/dpkg/info/chibi-scheme-images.postinst: 26: chibi-scheme: not found
  dpkg: error processing package chibi-scheme-images (--configure):
   installed chibi-scheme-images package post-installation script subprocess 
returned error exit status 127
  Processing triggers for libc-bin (2.31-9) ...
  Errors were encountered while processing:
   chibi-scheme-images
  E: Sub-process /usr/bin/dpkg returned an error code (1)

Bug#981761: netopeer2 installs world-writable files

[Adrian Bunk]

Package: netopeer2
Version: 1.1.39-1
Severity: serious

https://piuparts.debian.org/sid/fail/netopeer2_1.1.39-1.log

...
  ERROR: BAD PERMISSIONS
  drwxrwxrwx 4 root root  100 Feb  1 03:12 /etc/sysrepo
  drwxrwxrwx 3 root root  500 Feb  1 03:12 /etc/sysrepo/data
  -rw-rw-rw- 1 root root7 Feb  1 03:12 
/etc/sysrepo/data/ietf-datastores.startup
  -rw-rw-rw- 1 root root7 Feb  1 03:12 
/etc/sysrepo/data/ietf-netconf-notifications.startup
  -rw-rw-rw- 1 root root7 Feb  1 03:12 
/etc/sysrepo/data/ietf-netconf-with-defaults.startup
  -rw-rw-rw- 1 root root7 Feb  1 03:12 /etc/sysrepo/data/ietf-origin.startup
  -rw-rw-rw- 1 root root7 Feb  1 03:12 
/etc/sysrepo/data/ietf-yang-library.startup
  drwxrwxrwx 2 root root   40 Feb  1 03:12 /etc/sysrepo/data/notif
  -rw-rw-rw- 1 root root 3372 Feb  1 03:12 /etc/sysrepo/data/sysrepo.startup
  -rw-rw-rw- 1 root root7 Feb  1 03:12 /etc/sysrepo/data/yang.startup
  -rw-rw-rw- 1 root root0 Feb  1 03:12 /etc/sysrepo/sr_main_lock
  drwxrwxrwx 2 root root  560 Feb  1 03:12 /etc/sysrepo/yang
...

Bug#981759: usbguard fails to install in chroot

[Adrian Bunk]

Package: usbguard
Version: 1.0.0+ds-1
Severity: serious

https://piuparts.debian.org/sid/fail/usbguard_1.0.0+ds-1.log

...
  Setting up libusbguard0 (1.0.0+ds-1) ...
  Setting up usbguard (1.0.0+ds-1) ...
  ERROR: loadFiles: /sys/bus/usb/devices: No such file or directory
  dpkg: error processing package usbguard (--configure):
   installed usbguard package post-installation script subprocess returned 
error exit status 1
  Processing triggers for libc-bin (2.31-9) ...
  Errors were encountered while processing:
   usbguard
  E: Sub-process /usr/bin/dpkg returned an error code (1)

Bug#979133: marked as done (rails: build failure is silently ignored)

[Debian Bug Tracking System]

Your message dated Wed, 03 Feb 2021 17:04:12 +
with message-id 
and subject line Bug#979133: fixed in rails 2:6.0.3.4+dfsg-3
has caused the Debian Bug report #979133,
regarding rails: build failure is silently ignored
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.)


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

Package: rails
Version: 2:6.0.3.4+dfsg-2
Severity: serious

When I rebuilt all the packages during the rollup plugin transitions, 
rails did not ftbfs, even though the rollup command actually failed.


cd activestorage; mkdir node_modules; \
ln -s rollup-plugin-commonjs node_modules; rollup -c; cd -
[!] Error: Cannot find module 'rollup-plugin-node-resolve'
Require stack:
- /<>/activestorage/rollup.config.js
- /usr/share/nodejs/rollup/dist/shared/loadConfigFile.js
- /usr/share/nodejs/rollup/dist/bin/rollup
Error: Cannot find module 'rollup-plugin-node-resolve'
Require stack:
- /<>/activestorage/rollup.config.js
- /usr/share/nodejs/rollup/dist/shared/loadConfigFile.js
- /usr/share/nodejs/rollup/dist/bin/rollup
   at Function.Module._resolveFilename 
(internal/modules/cjs/loader.js:831:15)

   at Function.Module._load (internal/modules/cjs/loader.js:687:27)
   at Module.require (internal/modules/cjs/loader.js:903:19)
   at require (internal/modules/cjs/helpers.js:74:18)
   at Object. 
(/<>/activestorage/rollup.config.js:5:15)

   at Module._compile (internal/modules/cjs/loader.js:1015:30)
   at Object.require.extensions. [as .js] 
(/usr/share/nodejs/rollup/cli/run/loadConfigFile.ts:91:38)

   at Module.load (internal/modules/cjs/loader.js:879:32)
   at Function.Module._load (internal/modules/cjs/loader.js:724:14)
   at Module.require (internal/modules/cjs/loader.js:903:19)
--- End Message ---
--- Begin Message ---
Source: rails
Source-Version: 2:6.0.3.4+dfsg-3
Done: Utkarsh Gupta 

We believe that the bug you reported is fixed in the latest version of
rails, 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.
Utkarsh Gupta  (supplier of updated rails 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: Wed, 03 Feb 2021 22:12:15 +0530
Source: rails
Architecture: source
Version: 2:6.0.3.4+dfsg-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Team 

Changed-By: Utkarsh Gupta 
Closes: 979133
Changes:
 rails (2:6.0.3.4+dfsg-3) unstable; urgency=medium
 .
   [ Pirate Praveen ]
   * Fix silent build failure and adapt rollup.config.js for
 recent changes. (Closes: #979133)
Checksums-Sha1:
 5bae35ef8cc95c35b0c32d54169b5f0668b5b53b 4874 rails_6.0.3.4+dfsg-3.dsc
 d0389f6351f881f893af6510397d762b8f633a95 97528 
rails_6.0.3.4+dfsg-3.debian.tar.xz
 776968afe56a0da0139b830924feb6a435abde9b 34350 
rails_6.0.3.4+dfsg-3_amd64.buildinfo
Checksums-Sha256:
 f857d1e73b6d2054d8d3bce39306aacf681fe78bab71440ccf66dad6b2b7 4874 
rails_6.0.3.4+dfsg-3.dsc
 e6b2f6547003f61c20aae905c2a7129df215862ebf99ae7823e0a655d2797443 97528 
rails_6.0.3.4+dfsg-3.debian.tar.xz
 674c4001951c3385d49a6a0c2b388080d155e94724810e7693f83436aa786787 34350 
rails_6.0.3.4+dfsg-3_amd64.buildinfo
Files:
 59ab6f3a8f44aacde4fbf811badd474b 4874 ruby optional rails_6.0.3.4+dfsg-3.dsc
 2d92fb507571382a94562db1a7cc80a9 97528 ruby optional 
rails_6.0.3.4+dfsg-3.debian.tar.xz
 b49803c94a53199d5ba981adf54ec917 34350 ruby optional 
rails_6.0.3.4+dfsg-3_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJHBAEBCAAxFiEEbJ0QSEqa5Mw4X3xxgj6WdgbDS5YFAmAa0/kTHHV0a2Fyc2hA
ZGViaWFuLm9yZwAKCRCCPpZ2BsNLliLyD/9W0DNLq+PbU5ibcKGBBIIEQO/3ACBy
hR7X2/lqcaXj6i9KnxtxRoHamNJdxRwcGq77vJYissbs2l1KB8s1dS6ofIzYKqZs
KiWFDliOM2KkUx0+FGkIpbAYzCzRIYzZRSqWWKAhmd/eme+aj4Hy95nZKJDdD6Ta
0CK9tfYWdT49iSyq16Y9efYIvbL4r3zXuwHERzTIGg7rwVccHXFeE4Zlqu8k/UhE
b/3MAaRf9p8OVhoi5y36pWAhuXzLdLwshdBTTCP/YnqPIly25jEG+tx2VDtYaHqf
OcxG5VDanPQ/oTtvfza4kCC/twVnCTPi+sh8w93yrynobe9jGVmhyOGkd0CTnm+9
AvVjvcKMgWAyuiR6wy+/YG92B54rRnYGwUBPjuaCmwbSkKJXy0Obs5niXfPvcIOp
5IwA/1kfxFsKc8j5M2ARhMnxwDRS1rbZl98cJ91W0yOuw9O5RsfbQS9oZd/BTkn7
/a2AtQjDL1jNnu+CacMKbJG3t8tTud00VSAvy1qHLZ

Bug#981758: apt-clone: autopkgtest failure on i386

[Adrian Bunk]

Source: apt-clone
Version: 0.4.3
Severity: serious

https://ci.debian.net/data/autopkgtest/testing/i386/a/apt-clone/10238817/log.gz

...
==
ERROR: test_clone_upgrade_synthetic (__main__.TestCloneUpgrade)
test clone upgrade with on-the-fly generated chroots
--
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/apt/cache.py", line 281, in __getitem__
rawpkg = self._cache[key]
KeyError: 'ubuntu-standard'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File 
"/tmp/autopkgtest-lxc.9v3096th/downtmp/build.b2q/src/tests/test_clone_upgrade.py",
 line 52, in test_clone_upgrade_synthetic
new = self._create_fake_upgradable_root(supported[-1], meta=meta)
  File 
"/tmp/autopkgtest-lxc.9v3096th/downtmp/build.b2q/src/tests/test_clone_upgrade.py",
 line 105, in _create_fake_upgradable_root
if not cache[meta].is_installed:
  File "/usr/lib/python3/dist-packages/apt/cache.py", line 283, in __getitem__
raise KeyError('The cache has no package named %r' % key)
KeyError: "The cache has no package named 'ubuntu-standard'"

--
Ran 2 tests in 9.408s

FAILED (errors=1, skipped=1)
make: *** [Makefile:7: test] Error 1
autopkgtest [13:54:32]: test run-tests: ---]
autopkgtest [13:54:32]: test run-tests:  - - - - - - - - - - results - - - - - 
- - - - -
run-testsFAIL non-zero exit status 2
autopkgtest [13:54:32]: test run-tests:  - - - - - - - - - - stderr - - - - - - 
- - - -
make: *** [Makefile:7: test] Error 1
autopkgtest [13:54:32]:  summary
run-testsFAIL non-zero exit status 2

Processed (with 1 error): archiving 937166

[Debian Bug Tracking System]

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

> archive 937166
Bug #937166 [src:nuitka] nuitka: Python2 removal in sid/bullseye
Bug #966764 [src:nuitka] nuitka: Unversioned Python removal in sid/bullseye
Bug 937166 cannot be archived
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#981681: marked as done (python3-colors: missing Breaks+Replaces: python3-ansicolors)

[Debian Bug Tracking System]

Your message dated Wed, 03 Feb 2021 16:34:16 +
with message-id 
and subject line Bug#981681: fixed in python-ansicolors 1.1.8-4
has caused the Debian Bug report #981681,
regarding python3-colors: missing Breaks+Replaces: python3-ansicolors
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.)


-- 
981681: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=981681
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python3-colors
Version: 1.1.8-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package failed to install
because it tries to overwrite other packages files without declaring a
Breaks+Replaces relation.

See policy 7.6 at
https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces

>From the attached log (scroll to the bottom...):

  Preparing to unpack .../python3-colors_1.1.8-3_all.deb ...
  Unpacking python3-colors (1.1.8-3) ...
  dpkg: error processing archive 
/var/cache/apt/archives/python3-colors_1.1.8-3_all.deb (--unpack):
   trying to overwrite 
'/usr/lib/python3/dist-packages/ansicolors-1.1.8.egg-info/PKG-INFO', which is 
also in package python3-ansicolors 1.1.8-1
  Errors were encountered while processing:
   /var/cache/apt/archives/python3-colors_1.1.8-3_all.deb


cheers,

Andreas


python3-ansicolors=1.1.8-1_python3-colors=1.1.8-3.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: python-ansicolors
Source-Version: 1.1.8-4
Done: nicoo 

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

Debian distribution maintenance software
pp.
nicoo  (supplier of updated python-ansicolors package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 03 Feb 2021 15:57:49 +0100
Source: python-ansicolors
Architecture: source
Version: 1.1.8-4
Distribution: unstable
Urgency: high
Maintainer: Debian Python Team 
Changed-By: nicoo 
Closes: 981681
Changes:
 python-ansicolors (1.1.8-4) unstable; urgency=high (RC)
 .
   * python3-colors: Breaks+Replaces python3-ansicolors.
 Closes: #981681
Checksums-Sha1:
 deddaccc75c21747430875fb8df6d55a5da2285a 2057 python-ansicolors_1.1.8-4.dsc
 6140f35af2bc34fe2ba60088021dd1f650d2a9f4 2000 
python-ansicolors_1.1.8-4.debian.tar.xz
 4199e42e694c0f491fb7db581a2b44c869bdd877 6813 
python-ansicolors_1.1.8-4_amd64.buildinfo
Checksums-Sha256:
 dbd8dda6cc1f3ce07a670b193e71480b79ae022b7a02b7d7cd831af694c608ec 2057 
python-ansicolors_1.1.8-4.dsc
 9012592cbc3615a3f89fc7c82540a263b904e8426f8317c80df0e6d6d17e4935 2000 
python-ansicolors_1.1.8-4.debian.tar.xz
 f63c21e1fad6b6328e53453ce00bf09c8d909ba5a12eb14f52d8a3a71705886e 6813 
python-ansicolors_1.1.8-4_amd64.buildinfo
Files:
 264f194948b66d225e7049d880cb6df8 2057 python optional 
python-ansicolors_1.1.8-4.dsc
 a44797ef3eb72151e3c65271da14caf2 2000 python optional 
python-ansicolors_1.1.8-4.debian.tar.xz
 454fce2e76bda0920624ab7c9f733ccf 6813 python optional 
python-ansicolors_1.1.8-4_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEU7EqA8ZVHYoLJhPE5vmO4pLV7MsFAmAayiwACgkQ5vmO4pLV
7Mum8A/7BQMNziXcf1VuyV8q/aZFyfnA53cxsKbxX55tbW5nAQuwdaNtzhItA+19
4ZRpU9TFrX4gEGE2LlrNQ2VvBBy9IJrUIq0Cyp9V+9SL/dRGovTlEqoZomdOkDfK
ZIxvkBNoAmn2wSaqnVk8OSwRYa1guRN2+GoMaA66TTxzsdhQ/QgqSaRucWCFckFC
Kz7pytgVzYUYDfLJOQy67OsNAvd1/F4V1KWirHVByMj9bnMiN8LiJwZp1DIkTSh8
nMx9u8aTau48OVwMpJXnacXf3NMY18tS7pt1nPxEPu/J9qraIhkAraBoTjk4EtLw
26scNxBwRcW1iCENNr5xj2N6DqubIXa5Nu/s8iXlcPkAM+x3dj7ax8Z1/NyoaXNe
CXXWtYAXG43O76muxN7SoyYAu6uhrC1uhPqyGxj7Sq5/OeZeEbGh7NNhbO9LAphZ
70mM3vXIvHA6JY8twSW3aKPuK7Ra5kO93I78rg4UzT3qXHDV2bsnwGjqHEkEMIOj
pXld8AylB+EU+8ic7ZNaJi147VTCxCK8qjnDWaV0swryMQ71hn1qGXn7ugykBNFp
bTwu/lslZT81neUx/3u9XcB8ceoHzz2vjE6jSctOwBqZyfBqja+lOi/kjtZpPw5X
oYhKDtEZw6KVdZhXE2MOZWboFaBI+8xq/eJsYyj9CBSkgvw1itI=
=KEZF
-END PGP SIGNATURE End Message ---

Bug#981640: marked as done (python3-easyansi: Missing Breaks and Replaces headers → trying to overwrite '/usr/lib/python3/dist-packages/easy_ansi-0.3.egg-info/PKG-INFO', which is also in package pytho

[Debian Bug Tracking System]

Your message dated Wed, 03 Feb 2021 16:34:22 +
with message-id 
and subject line Bug#981640: fixed in python-easy-ansi 0.3-4
has caused the Debian Bug report #981640,
regarding python3-easyansi: Missing Breaks and Replaces headers → trying to 
overwrite '/usr/lib/python3/dist-packages/easy_ansi-0.3.egg-info/PKG-INFO', 
which is also in package python3-easy-ansi 0.3-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.)


-- 
981640: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=981640
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python3-easyansi
Severity: serious

Hi,

upgrading multiplex, which switched from python3-easy-ansi to
python3-easyansi, caused the following installation failure:

Preparing to unpack .../multiplex_0.5.1-3_all.deb ...
Unpacking multiplex (0.5.1-3) over (0.5.1-1) ...
Selecting previously unselected package python3-easyansi.
Preparing to unpack .../python3-easyansi_0.3-3_all.deb ...
Unpacking python3-easyansi (0.3-3) ...
dpkg: error processing archive 
/var/cache/apt/archives/python3-easyansi_0.3-3_all.deb (--unpack):
 trying to overwrite 
'/usr/lib/python3/dist-packages/easy_ansi-0.3.egg-info/PKG-INFO', which is also 
in package python3-easy-ansi 0.3-1
Preparing to unpack .../python3-multiplex_0.5.1-3_all.deb ...
Unpacking python3-multiplex (0.5.1-3) over (0.5.1-1) ...
Errors were encountered while processing:
 /var/cache/apt/archives/python3-easyansi_0.3-3_all.deb

Reason is the common one in such cases: Missing Breaks and Replaces
headers.

P.S.: Are such package renamings really necessary that shortly before
the freeze? O.o

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

Kernel: Linux 5.10.0-1-amd64 (SMP w/4 CPU threads)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)
LSM: AppArmor: enabled
--- End Message ---
--- Begin Message ---
Source: python-easy-ansi
Source-Version: 0.3-4
Done: nicoo 

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

Debian distribution maintenance software
pp.
nicoo  (supplier of updated python-easy-ansi package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 03 Feb 2021 17:15:31 +0100
Source: python-easy-ansi
Architecture: source
Version: 0.3-4
Distribution: unstable
Urgency: high
Maintainer: Debian Python Team 
Changed-By: nicoo 
Closes: 981640
Changes:
 python-easy-ansi (0.3-4) unstable; urgency=high (RC)
 .
   * Breaks+Replaces python3-easy-ansi.  (Closes: #981640)
Checksums-Sha1:
 0267ab0bccea4135327b4842ea76ca5f3ea69246 2020 python-easy-ansi_0.3-4.dsc
 2cb37c4c9ff29823a8599807eb6cf6f7176f86d5 2188 
python-easy-ansi_0.3-4.debian.tar.xz
 762afe75b6c15230e79ea47cd44c919ea264d1f9 6431 
python-easy-ansi_0.3-4_amd64.buildinfo
Checksums-Sha256:
 41edd2778eeef99a9dc943a87221b727dcdc53bd4df696a1908b30df7379854d 2020 
python-easy-ansi_0.3-4.dsc
 c0b080f14c3ee246fd5bc7a699620d55b5bfcc5676ee6eb2b163ed62c663e7ab 2188 
python-easy-ansi_0.3-4.debian.tar.xz
 e68c1d61851d072bcb60e0ab35022af5d9c8294850d2ddc6a24624d089d88f0d 6431 
python-easy-ansi_0.3-4_amd64.buildinfo
Files:
 eb7383015c90123a20fb1c115a79bc55 2020 python optional 
python-easy-ansi_0.3-4.dsc
 a2e00ffe63fea761f0be814a5bfeeda6 2188 python optional 
python-easy-ansi_0.3-4.debian.tar.xz
 6acadf74ab147f247caf22fd8f350e2e 6431 python optional 
python-easy-ansi_0.3-4_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEU7EqA8ZVHYoLJhPE5vmO4pLV7MsFAmAazkMACgkQ5vmO4pLV
7Muucw//b3DUa9/JP2uWDBe0l3gTJDhFygrrLPf0Bk8/4EhVHZvbabXdF1pC2zxj
lFSQ02J+qXodCN9atw2ELXbwAUaDteJKLnTcrjKTxqHhJncjY2sQO3E1H1dXg1QE
gsrvK4DZJ7aV3Z0CAHObQlBHBjtKf824LTdLd2hcMNDNL5EvMb7FmbT9p+Fc6LFX
/dzvO14P92FuOyPmokkvpVmxOSOR3qXC7d7WrLlffHXo+n6Z+dfU1q8F9MHrNwxt
TfaQdR+L

Processed: Bug#981640 marked as pending in python-easy-ansi

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #981640 [python3-easyansi] python3-easyansi: Missing Breaks and Replaces 
headers → trying to overwrite 
'/usr/lib/python3/dist-packages/easy_ansi-0.3.egg-info/PKG-INFO', which is also 
in package python3-easy-ansi 0.3-1
Added tag(s) pending.

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

Bug#981640: marked as pending in python-easy-ansi

[nicoo]

Control: tag -1 pending

Hello,

Bug #981640 in python-easy-ansi 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/easy-ansi/-/commit/84593da74038fb824008b2bbe5116246ce36a156


python3-easyansi: Breaks+Replaces python3-easy-ansi

Closes: #981640


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/981640

Bug#981428: marked as done (python3-fido2: Version 0.9 breaks yubikey-manager)

[Debian Bug Tracking System]

Your message dated Wed, 03 Feb 2021 16:22:35 +
with message-id 
and subject line Bug#981428: fixed in yubikey-manager 4.0.0~a1-1
has caused the Debian Bug report #981428,
regarding python3-fido2: Version 0.9 breaks yubikey-manager
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.)


-- 
981428: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=981428
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python3-fido2
Version: 0.9.0-1
Severity: serious
Justification: breaks other packages

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

python-fido2 had minor API-breaking changes, which breaks (at least)
yubikey-manager.  Let's hold it back from transitionning to testing until
upstream cuts a new release.


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

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

Versions of packages python3-fido2 depends on:
ii  python3   3.9.1-1
ii  python3-cryptography  3.3.1-1
ii  python3-six   1.15.0-2

python3-fido2 recommends no packages.

python3-fido2 suggests no packages.

- -- no debconf information

-BEGIN PGP SIGNATURE-

iQJFBAEBCgAvFiEEU7EqA8ZVHYoLJhPE5vmO4pLV7MsFAmAWAe0RHG5pY29vQGRl
Ymlhbi5vcmcACgkQ5vmO4pLV7MumKxAAsG7kFEmlr41ApF4VZQCqQkCadPEWYvt6
qRU/53nKKfZWis27IDSsaq1m4xOsVGD9++1W4cClk3UXWe3qNFZxJFFeMxdiPGiQ
ZuJQtOJnE603zoL8S/QNpBx+8s4poahb1RF7BYHDqL8xeY4yQK3v5dHQyMJ8Iwfi
RqT8RWPEGlviPF5TtqQCaZgmolxCYPRGoRSXt5lYb6iOeBMnOKjuvd+B5ZFleItk
c6ENVNWwvPI3avuME1fJQqnmw4fFRIPGIDjUqKO5+WnaRdpHgAaWYaj9Wwi+kkO2
M6DENFSiFKQcZN6fG2S/ql0/iRbaYnfjqImjZ863/7sr41Hfk6o5bqFBvunB73aR
M2Lksxlrvp85iqLBf0AoliD8esf7vOrbFiCJf/0jnorOkQ8tmi68hIb/xcaUuUrk
dn/icZerXxBuHPM2BcL0N8ZYtiXB3sa//cpfdk6rxGANK+k5KVNtQg9/8sEiQc+U
Is5Dc2SR/rdPL1AGyIab6mDWf+fEvFjC2l9Pse6t6DFbxJABLVGnAie9+Aq3kFY/
a21OALS/A2OJIznXpS36BNLAauohbAZ+IPUnSC5xUozZ020ZVjkhlRLa89fmYCFP
7xdePPT8FVNT9y5HlShnq1Ebp3r/zTGyF4oSPEmo84PxJxRH0KgHU3x7Hg0voPNE
z+tFjpB+hTY=
=khui
-END PGP SIGNATURE-
--- End Message ---
--- Begin Message ---
Source: yubikey-manager
Source-Version: 4.0.0~a1-1
Done: nicoo 

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

Debian distribution maintenance software
pp.
nicoo  (supplier of updated yubikey-manager package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 03 Feb 2021 17:02:28 +0100
Source: yubikey-manager
Architecture: source
Version: 4.0.0~a1-1
Distribution: unstable
Urgency: high
Maintainer: Debian Authentication Maintainers 

Changed-By: nicoo 
Closes: 981428
Changes:
 yubikey-manager (4.0.0~a1-1) unstable; urgency=high (RC)
 .
   * New upstream version 4.0.0~a1
 + Supports fido2 0.9.x (Closes: #981428)
 + Adds NFC support to the FIDO and OTP functionality
 + Adds "ykman --diagnose" to aid in troubleshooting.
 + Restructures subcommands
   Aliases for old versions to be removed in a future release.
 + New module “yubikit” provides a high-level API for advanced users.
 .
   * d/rules: Temporarily disable tests
 Some test dependencies are not yet packaged in Debian
 .
   * Convert upstream's buildsystem to setuptools using dephell.
 This is necessary, as poetry is not yet packaged in Debian.
   * yubikey-manager: Depend on python3-ykman, not the transitional pkg
   * Upgrade to debhelper compatibility level 13
 `dh_missing --fail-missing` is now the default.
 .
   * debian/copyright
 + Fix syntax of Upstream-Contact
 + Update for new version
   * d/control
 + Use a versioned relationship to the fido2 library
 + Declare compliance with policy v4.5.1.  (no change required)
Checksums-Sha1:
 edcc5d58fe43b07a406fda40ad14667fe570c8c6 2370 

Bug#957828: marked as done (sparskit: ftbfs with GCC-10)

[Debian Bug Tracking System]

Your message dated Wed, 03 Feb 2021 16:22:25 +
with message-id 
and subject line Bug#957828: fixed in sparskit 2.0.0-4
has caused the Debian Bug report #957828,
regarding sparskit: 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.)


-- 
957828: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957828
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:sparskit
Version: 2.0.0-3
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/sparskit_2.0.0-3_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

[...]
  |   1
Warning: Array reference at (1) out of bounds (2 > 1) in loop beginning at (2)
/<>/MATGEN/FEM/elmtlib2.f:684:17:

  683 |   do i=2,nx+1
  | 2
  684 | ia(i)=ia(i)+i-1
  | 1
Warning: Array reference at (1) out of bounds (2 > 1) in loop beginning at (2)
/<>/MATGEN/FEM/elmtlib2.f:686:12:

  683 |   do i=2,nx+1
  | 2
..
  686 | jwk(i)=0
  |1
Warning: Array reference at (1) out of bounds (2 > 1) in loop beginning at (2)
[ 22%] Building Fortran object CMakeFiles/skit.dir/MATGEN/FEM/femgen.f.o
[ 23%] Building Fortran object CMakeFiles/skit.dir/MATGEN/FEM/meshes.f.o
[ 24%] Building Fortran object CMakeFiles/skit.dir/MATGEN/MISC/sobel.f.o
[ 25%] Building Fortran object CMakeFiles/skit.dir/MATGEN/MISC/zlatev.f.o
/<>/MATGEN/MISC/zlatev.f:138:16:

  138 | 20RNR(I) = I
  |1
Warning: Fortran 2018 deleted feature: DO termination statement which is not 
END DO or CONTINUE with label 20 at (1)
/<>/MATGEN/MISC/zlatev.f:148:21:

  148 | 22RNR(NZ + I) = I
  | 1
Warning: Fortran 2018 deleted feature: DO termination statement which is not 
END DO or CONTINUE with label 22 at (1)
/<>/MATGEN/MISC/zlatev.f:149:17:

  149 | 21NZ = NZ + N
  | 1
Warning: Fortran 2018 deleted feature: DO termination statement which is not 
END DO or CONTINUE with label 21 at (1)
/<>/MATGEN/MISC/zlatev.f:174:26:

  174 | 30RNR(NZ + I) = N2 + I
  |  1
Warning: Fortran 2018 deleted feature: DO termination statement which is not 
END DO or CONTINUE with label 30 at (1)
/<>/MATGEN/MISC/zlatev.f:184:26:

  184 | 42RNR(NZ + I) = N2 + I
  |  1
Warning: Fortran 2018 deleted feature: DO termination statement which is not 
END DO or CONTINUE with label 42 at (1)
/<>/MATGEN/MISC/zlatev.f:185:17:

  185 | 41NZ = NZ +M2
  | 1
Warning: Fortran 2018 deleted feature: DO termination statement which is not 
END DO or CONTINUE with label 41 at (1)
[ 26%] Building Fortran object CMakeFiles/skit.dir/ORDERINGS/ccn.f.o
/<>/ORDERINGS/ccn.f:152:37:

  150 |call csrcsc(n, job, ipos, amat, ja, ia, izs(iamat),
  | 2
  151 |  * izs(ijat), izs(iiat))
  152 |call csrcsc(n, job, ipos, izs(iamat), izs(ijat), izs(iiat),
  | 1
Error: Type mismatch between actual argument at (1) and actual argument at (2) 
(INTEGER(4)/REAL(8)).
make[4]: *** [CMakeFiles/skit.dir/build.make:245: 
CMakeFiles/skit.dir/ORDERINGS/ccn.f.o] Error 1
make[4]: Leaving directory '/<>/DEB_build_static'
make[3]: *** [CMakeFiles/Makefile2:315: CMakeFiles/skit.dir/all] Error 2
make[3]: Leaving directory '/<>/DEB_build_static'
make[2]: *** [Makefile:130: all] Error 2
make[2]: L

Bug#946863: freewheeling: patched v0.6.4 in mentors repo

[bill-auger]

Package: freewheeling
Followup-For: Bug #946863
X-Debbugs-Cc: bill-au...@programmer.net

this RC bug has caused freewheeling to be dropped from [testing]
this week

i have uploaded a patched v0.6.4 to the mentors repo (0.6.4-1.1);
which includes the necessary changes for fluidsynth2 support,
back-ported from the current upstream

https://mentors.debian.net/package/freewheeling/
https://mentors.debian.net/debian/pool/main/f/freewheeling/

i have filed a RFS bug (#981751), and at the suggestion of the
debian-mia team, i have also filed an ITS bug (#981633)

Processed: severity

[Debian Bug Tracking System]

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

> severity 981646 normal
Bug #981646 [libarpack2-dev] arpack: dseupd randomly fails on mips64el arch
Severity set to 'normal' from 'serious'
> thanks
Stopping processing here.

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

Processed: arpack: dseupd randomly fails on mips64el arch

[Debian Bug Tracking System]

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

> forwarded 981646 https://github.com/opencollab/arpack-ng/issues/294
Bug #981646 [libarpack2-dev] arpack: dseupd randomly fails on mips64el arch
Set Bug forwarded-to-address to 
'https://github.com/opencollab/arpack-ng/issues/294'.
> thanks
Stopping processing here.

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

Bug#981720: FTBFS: FileNotFoundError: [Errno 2] No such file or directory: '/etc/resolv.conf'

[Ritesh Raj Sarraf]

On Wed, 2021-02-03 at 14:11 +0100, Thomas Goirand wrote:
> Hi,
> 

Hi Thomas,

> Could you please explain in which build environment you don't have a
> resolv.conf file?
> 

In an OBS build environment, where it creates chroots for the target,
on the fly. I haven't thoroughly checked but given the error I'm fairly
sure that the chroot may not have the file.

> Also, could you please send the full build log? Because like this, I
> can't tell at which stage this happened. Was it during the build of
> the
> documentation?

The Reproducible Builds logs have the same issue along with the full
build log.

https://tests.reproducible-builds.org/debian/rb-pkg/bullseye/amd64/python-eventlet.html


-- 
Ritesh Raj Sarraf | http://people.debian.org/~rrs
Debian - The Universal Operating System


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

Bug#981747: network-manager: NetworkManager does not start in sysvinit system

[Luis]

Package: network-manager
Version: 1.28.0-2+b1
Severity: grave
Tags: newcomer
Justification: renders package unusable
X-Debbugs-Cc: lui...@mailnesia.com

(Alternatively taggable as Severity: critical - see below)

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?

Upgraded from Debian Buster to Debian Bullseye, then rebooted the system into a
new session.

   * What exactly did you do (or not do) that was effective (or
 ineffective)?

Rebooting the system was ineffective.

Copying a previous init file from a cached version of the package was
effective.


   * What was the outcome of this action?

UPGRADE -> Network Manager did not start, nor was listed among the manageable
services. /etc/init.d/network-manager did not exist.

   * What outcome did you expect instead?

UPGRADE -> Network Manager would start, /etc/init.d/network-manager exists and
is runnable, and NM would be listed among the manageable services.

*** End of the template - remove these template lines ***

Machine is using sysvinit as init, and has done so since the times of Debian
Wheezy (except for a clean Stretch install where sysvinit was installed after a
reboot).

Upgrading the system from Debian Buster to Debian Bullseye (at the current apt
tag of 'testing') then rebooting led to NetworkManager no longer starting as
/etc/init.d/network-manager was missing. Without a connection to the internet,
the only reasonable solution was to unpack the previous version of 'network-
manager' in the package cache and copy the required file manually. Had the
cache not been available, this upgrade would have rendered the machine much
more unusable.

Note this is *not* a duplicate of BR #964139 ("please restore init file"). That
BR is a mere wishlist, whereas this bug report is marked "grave" due to real
world problems caused by a removal of a behaviour that is the entire point of a
*service* existing, and the only reason it's not marked as "critical" is that
other network-related utilities were not auto-removed during the upgrade, and
were not affected by this init-removal behaviour; however note that "another
package does not have bugs" should not be a factor in the severity of a bug in
*this* package.

Without previous understanding of available network commands and without a
local package cache, restoring the affected capability requires having
previously installed and disabled an alternative network manager like 'wicd',
or manually writing a compatible init script.




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

Kernel: Linux 5.10.0-1-amd64 (SMP w/2 CPU threads)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=es_CL.UTF-8, LC_CTYPE=es_CL.UTF-8 (charmap=UTF-8), 
LANGUAGE=es_CL:es
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)
LSM: AppArmor: enabled

Versions of packages network-manager depends on:
ii  adduser3.118
ii  dbus   1.12.20-1
ii  eudev [udev]   232:3.2.7.3
ii  libaudit1  1:2.8.5-3.1
ii  libbluetooth3  5.55-1
ii  libc6  2.31-5
ii  libcurl3-gnutls7.72.0-1
ii  libelogind0 [libsystemd0]  246.9.1-1+debian1
ii  libeudev1 [libudev1]   232:3.2.7.3
ii  libglib2.0-0   2.66.4-1
ii  libgnutls303.7.0-5
ii  libjansson42.13.1-1
ii  libmm-glib01.14.8-0.1
ii  libndp01.6-1+b1
ii  libnewt0.520.52.21-4+b2
ii  libnm0 1.28.0-2+b1
ii  libpsl50.21.0-1.1
ii  libreadline8   8.1~rc3-1
ii  libselinux13.1-2+b1
ii  libteamdctl0   1.31-1
ii  libuuid1   2.36.1-1
ii  policykit-10.105-25.0nosystemd2
ii  wpasupplicant  2:2.9.0-15

Versions of packages network-manager recommends:
pn  dnsmasq-base
ii  iptables1.8.6-1
ii  libpam-elogind-compat [libpam-systemd]  1.3
pn  modemmanager
ii  ppp 2.4.9-1+1
ii  wireless-regdb  2020.04.29-2

Versions of packages network-manager suggests:
ii  isc-dhcp-client  4.4.1-2.1+b2
pn  libteam-utils

-- Configuration Files:
/etc/NetworkManager/NetworkManager.conf changed [not included]

-- no debconf information

Bug#955095: cyrus-sasl2: FTBFS with Sphinx 2.4: Extension error: Could not import extension sphinxlocal.builders.manpage

[Ritesh Raj Sarraf]

Source: cyrus-sasl2
Version: 2.1.27+dfsg-2
Followup-For: Bug #955095

Hi,

We've hit this build failure when re-building the package in our
downstream. As it stands now, this issue is also seen on the
Reproducible Builds.


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

Kernel: Linux 5.10.0-3-amd64 (SMP w/8 CPU threads)
Kernel taint flags: TAINT_USER
Locale: LANG=en_IN.UTF-8, LC_CTYPE=en_IN.UTF-8 (charmap=UTF-8), LANGUAGE=en_US
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Bug#956822: marked as done (xpra: FTBFS on armel and armhf)

[Debian Bug Tracking System]

Your message dated Wed, 03 Feb 2021 13:51:41 +
with message-id 
and subject line Bug#956822: fixed in xpra 3.0.9+dfsg1-1.1
has caused the Debian Bug report #956822,
regarding xpra: FTBFS on armel and armhf
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.)


-- 
956822: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=956822
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: xpra
Version: 3.0.8+dfsg1-1
Severity: serious
Tags: ftbfs sid bullseye
Justification: fails to build from source (but built successfully in the past)

xpra failed to build on armel and armhf. See
https://buildd.debian.org/status/fetch.php?pkg=xpra&arch=armel&ver=3.0.8%2Bdfsg1-1&stamp=1586872010&raw=0

Cheers

-- System Information:
Debian Release: bullseye/sid
  APT prefers unstable-debug
  APT policy: (650, 'unstable-debug'), (650, 'unstable'), (601, 'testing'), 
(600, 'experimental-debug'), (600, 'buildd-unstable'), (600, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.5.0-1-amd64 (SMP w/8 CPU cores)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8), LANGUAGE=en_US:en 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

-- 
Sebastian Ramacher


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: xpra
Source-Version: 3.0.9+dfsg1-1.1
Done: Antonio Russo 

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

Debian distribution maintenance software
pp.
Antonio Russo  (supplier of updated xpra 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: Tue, 02 Feb 2021 23:22:38 -0700
Source: xpra
Architecture: source
Version: 3.0.9+dfsg1-1.1
Distribution: unstable
Urgency: medium
Maintainer: Dmitry Smirnov 
Changed-By: Antonio Russo 
Closes: 921700 956822
Changes:
 xpra (3.0.9+dfsg1-1.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Tweak fix-xvfb-patch.patch (Closes: #921700, #956822).
Checksums-Sha1:
 6ed43b95a0576b593398ae7c00f2ab1ccd8884d8 2459 xpra_3.0.9+dfsg1-1.1.dsc
 40c1e747fb00ff1e52c84418b535b1ea40afa43c 36480 
xpra_3.0.9+dfsg1-1.1.debian.tar.xz
 e9e421b8fdf04ab1e2894820d10bcfc24fff5e27 15939 
xpra_3.0.9+dfsg1-1.1_armhf.buildinfo
Checksums-Sha256:
 0e73bf9c18b633415d3098b7c71172e9c915eaaed1d49aaef8f33785f34c3762 2459 
xpra_3.0.9+dfsg1-1.1.dsc
 92a2712f02b7c456053b7e496aaad94f4cd09679cde0bec40a535dbab2de81fb 36480 
xpra_3.0.9+dfsg1-1.1.debian.tar.xz
 2091359a2293958d4feeb35453fd498e47599d9a2ee9e31e4611185df17c4b6c 15939 
xpra_3.0.9+dfsg1-1.1_armhf.buildinfo
Files:
 1c19791c7dc857779e480e95f6ec67be 2459 x11 optional xpra_3.0.9+dfsg1-1.1.dsc
 b7ab448ae9c5f24dc02aaf4fb9f02b06 36480 x11 optional 
xpra_3.0.9+dfsg1-1.1.debian.tar.xz
 3ef5ecc5b55d829477ad486306256622 15939 x11 optional 
xpra_3.0.9+dfsg1-1.1_armhf.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEER4nvI8Pe/wVWh5yq+4YyUahvnkcFAmAapw0ACgkQ+4YyUahv
nkf64xAAu+s+8C7zyq5DZWdWudDKdGrIxPp7f4ZnHsqxKmHZYi5Up7TdMrcZkQdf
4Pjhdz0z86fpIiimNgnDlNTAYsKIge0E4UDC1C+JCE+fSLxKebRYRcjdHKiLm3hD
60+TLoYmpIk6w8tyTC3sbqPlxJofDixpPjiVMKc2NprTc1xKIOXKj+JY16iDCw0t
1UDPixRcl2AeGDCpqAZ5QSVKTQ3FkVcGstQx7ZZfJevdMP2nQryMfCGBZaeT0lGq
G3nNklNa6o5G9ljqCnzG0tCydEDuDlFrk6U1lYJ2fuCVurCR9i3Yd9r0MbVQOPD9
58JUO5z/2etpPJ535WMtqlJ5Sr236fUgw51ZyjdP/IU6MVrqwJrSlsFMv1WfD4fp
8Py+62tqBWz+dZKW9sYB3G3MgclvovA+CxtWTZrkz/c1RdHf4JOl1+VY66NhjT8x
ToVjt2MEhgVTX+2qa4nrAnwssvN9ANlZWE60EL0Jbc/vxYvIvfHPrrgeRQ/9DeSF
3WPOc/ukXhmISV1y9tw8RqXnFWLR/Ik1jaKFkmsQPTRwMu1nvvHUdsPA7Dzsbg1D
iARi5Y9kql1mSkzEPygBJFIXYkmWxp5MTgAm0agkPmAtTnDpu/ZiqECIzb+PQv9c
YUhgNUzCz6LODGh45+3ZJS8g9pNr+dYGPlMZJ7LGTSaAAOpTIZE=
=aNgC
-END PGP SIGNATURE End Message ---

Processed: Re: Bug#981555: does not appear to respond to DBUS interface anymore

[Debian Bug Tracking System]

Processing control commands:

> retitle -1 gnome-keyring: unable to connect to D-Bus when using dbus-x11
Bug #981555 [gnome-keyring] does not appear to respond to DBUS interface anymore
Changed Bug title to 'gnome-keyring: unable to connect to D-Bus when using 
dbus-x11' from 'does not appear to respond to DBUS interface anymore'.
> reassign -1 libglib2.0-0 2.66.4-2
Bug #981555 [gnome-keyring] gnome-keyring: unable to connect to D-Bus when 
using dbus-x11
Bug reassigned from package 'gnome-keyring' to 'libglib2.0-0'.
No longer marked as found in versions gnome-keyring/3.36.0-1.
Ignoring request to alter fixed versions of bug #981555 to the same values 
previously set
Bug #981555 [libglib2.0-0] gnome-keyring: unable to connect to D-Bus when using 
dbus-x11
Marked as found in versions glib2.0/2.66.4-2.
> severity -1 serious
Bug #981555 [libglib2.0-0] gnome-keyring: unable to connect to D-Bus when using 
dbus-x11
Severity set to 'serious' from 'important'
> affects -1 + msmtp gnome-keyring
Bug #981555 [libglib2.0-0] gnome-keyring: unable to connect to D-Bus when using 
dbus-x11
Added indication that 981555 affects msmtp and gnome-keyring
> tags -1 = upstream
Bug #981555 [libglib2.0-0] gnome-keyring: unable to connect to D-Bus when using 
dbus-x11
Added tag(s) upstream.
> tags 981420 = upstream
Bug #981420 [libglib2.0-0] libglib2.0-0: gnome-keyring unable to unlock login 
keyring on some systems since GLib 2.66.4-2
Removed tag(s) moreinfo.
> forcemerge 981420 -1
Bug #981420 [libglib2.0-0] libglib2.0-0: gnome-keyring unable to unlock login 
keyring on some systems since GLib 2.66.4-2
Bug #981555 [libglib2.0-0] gnome-keyring: unable to connect to D-Bus when using 
dbus-x11
Set Bug forwarded-to-address to 
'https://gitlab.gnome.org/GNOME/glib/-/issues/2305'.
Marked as found in versions glib2.0/2.66.4-3.
Bug #981420 [libglib2.0-0] libglib2.0-0: gnome-keyring unable to unlock login 
keyring on some systems since GLib 2.66.4-2
Marked as found in versions glib2.0/2.66.4-2.
Merged 981420 981555

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

Bug#956822: Bug#981715: RFS: xpra/3.0.9+dfsg1-1.1 [NMU] [RC] -- tool to detach/reattach running X programs

[Wookey]

On 2021-02-02 23:42 -0700, Antonio Russo wrote:

> I am looking for a sponsor for my NMU of the "xpra" package, which is blocked
> migrating to testing for the last ~6 months [1] due to a FTBS on armel and
> armhf [2].
> 
> Also, I do not have access to arm* hardware to test this on, so, while I can
> confirm that this builds (and works) on amd64, it would be nice if someone
> could check that it works correctly on arm.

I've tested the builds on arm64 and armhf. I'm short of non-headless
boxes here to test the X functionality on.

So I've uploaded to get the migration going and allow others to test. I
should be able to contrive a non-headless armhf machine too, given a
bit of time (not today)

Wookey
-- 
Principal hats:  Linaro, Debian, Wookware, ARM
http://wookware.org/


signature.asc
Description: PGP signature

Processed: severity of 961896 is serious

[Debian Bug Tracking System]

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

> severity 961896 serious
Bug #961896 [src:nuitka] nuitka: Please make another source-only upload to 
allow testing migration
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

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

Bug#981673: marked as done (puppet-module-puppetlabs-mount-core fails to install)

[Debian Bug Tracking System]

Your message dated Wed, 03 Feb 2021 13:35:21 +
with message-id 
and subject line Bug#981673: fixed in puppet-module-puppetlabs-mount-core 
1.0.4+dfsg1-2
has caused the Debian Bug report #981673,
regarding puppet-module-puppetlabs-mount-core fails to install
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.)


-- 
981673: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=981673
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: puppet-module-puppetlabs-mount-core
Version: 1.0.4+dfsg1-1
Severity: serious

https://piuparts.debian.org/sid/fail/puppet-module-puppetlabs-mount-core_1.0.4+dfsg1-1.log

...
  Preparing to unpack 
.../puppet-module-puppetlabs-mount-core_1.0.4+dfsg1-1_all.deb ...
  Unpacking puppet-module-puppetlabs-mount-core (1.0.4+dfsg1-1) ...
  Setting up puppet-module-puppetlabs-mount-core (1.0.4+dfsg1-1) ...
  update-alternatives: using 
/usr/share/puppet/modules.available/puppetlabs-mount-core to provide 
/usr/share/puppet/modules/mount_core (puppet-module-mount-core) in auto mode
  update-alternatives: error: error creating symbolic link 
'/usr/share/puppet/modules/mount_core.dpkg-tmp': No such file or directory
  dpkg: error processing package puppet-module-puppetlabs-mount-core 
(--configure):
   installed puppet-module-puppetlabs-mount-core package post-installation 
script subprocess returned error exit status 2
  Errors were encountered while processing:
   puppet-module-puppetlabs-mount-core
  E: Sub-process /usr/bin/dpkg returned an error code (1)
...
--- End Message ---
--- Begin Message ---
Source: puppet-module-puppetlabs-mount-core
Source-Version: 1.0.4+dfsg1-2
Done: Thomas Goirand 

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

Debian distribution maintenance software
pp.
Thomas Goirand  (supplier of updated 
puppet-module-puppetlabs-mount-core 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: Wed, 03 Feb 2021 14:15:05 +0100
Source: puppet-module-puppetlabs-mount-core
Architecture: source
Version: 1.0.4+dfsg1-2
Distribution: unstable
Urgency: medium
Maintainer: Puppet Package Maintainers 

Changed-By: Thomas Goirand 
Closes: 981673
Changes:
 puppet-module-puppetlabs-mount-core (1.0.4+dfsg1-2) unstable; urgency=medium
 .
   * Do a mkdir -p /usr/share/puppet/modules in postinst (Closes: #981673).
Checksums-Sha1:
 170887a3618f0ee3363b01a5eebf68f300f31b31 2302 
puppet-module-puppetlabs-mount-core_1.0.4+dfsg1-2.dsc
 fd86e7e7a9aeba0c3764f2d155935d900dd213a0 2300 
puppet-module-puppetlabs-mount-core_1.0.4+dfsg1-2.debian.tar.xz
 15b5ca2533df4eaf51929727ecca6acb655d948f 6790 
puppet-module-puppetlabs-mount-core_1.0.4+dfsg1-2_amd64.buildinfo
Checksums-Sha256:
 3767739de087a455cc96a4a0c2b0f9647ced090bed90071d219fb22956d5f41a 2302 
puppet-module-puppetlabs-mount-core_1.0.4+dfsg1-2.dsc
 c11ae4a156035d67c6a47fdcba6816c7d4f65fe8eb8d56aac3f8dfd7e522fa23 2300 
puppet-module-puppetlabs-mount-core_1.0.4+dfsg1-2.debian.tar.xz
 00ee80be1157936c0d1ff2b122c2e4651c1b561255428ad16eda8802603df11b 6790 
puppet-module-puppetlabs-mount-core_1.0.4+dfsg1-2_amd64.buildinfo
Files:
 a30b05b5cba89149a401345c545f812f 2302 admin optional 
puppet-module-puppetlabs-mount-core_1.0.4+dfsg1-2.dsc
 fad34dd2a946cd2bed6822fcc7931095 2300 admin optional 
puppet-module-puppetlabs-mount-core_1.0.4+dfsg1-2.debian.tar.xz
 28738598fd2177a1b9ee1ac06c214abf 6790 admin optional 
puppet-module-puppetlabs-mount-core_1.0.4+dfsg1-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEoLGp81CJVhMOekJc1BatFaxrQ/4FAmAaolYACgkQ1BatFaxr
Q/7ApA/6An0cB7QK3DBUm195IMnUDUwAH/v0nO2TDc+A8fJRhFfL7pg9Gi6wjGWS
lpXRWI007Vf5pT94R4Jz6TrcEpckO9q3qUhsYyvIOKiODUJDroCbWDsdFuhxlA0M
J72/45F3oDP/vZSkIw3wKupe9blCpGdUI/82mLRnqKCVkAC8HLgy40tbDvexQxOX
pRbEKvltluakAJE49hSZzyGLALg1GIwfaAuHFvJxtOona157C56rB7IIN/hGpFoR
6QvsAuUIfHR1dPB+LgjNDXGdl6ETfjl5DHTOCvQ41CwyHEyCQ0QOPyaSL6W293Z3
z2rBEFT3mcacdS1UD4zPIO3YFz1VlZy0/JKpmGFsWZzHbiTtobvsJqLgE/4+KENT
wcWeBjU++Ozd2YWlI/MfqcpSOKg1XIRZir0A346pY8ia19qStjn3+or+5auSoWy5
5iBESpNJYgpbMBFNio

Bug#981739: marked as done (manpages-posix: no-one built the package for debian archive (non-free, source-only upload))

[Debian Bug Tracking System]

Your message dated Wed, 03 Feb 2021 13:34:36 +
with message-id 
and subject line Bug#981739: fixed in manpages-posix 2017a-2
has caused the Debian Bug report #981739,
regarding manpages-posix: no-one built the package for debian archive 
(non-free, source-only upload)
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.)


-- 
981739: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=981739
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: manpages-posix
Version: 2017a-1
Severity: grave

Hello,

The latest upload of manpages-posix was source-only but was not built
on the buildd network either. So, no binaries are available.
I think the text of this lintian tag applies in this case:
https://lintian.debian.org/tags/source-only-upload-to-non-free-without-autobuild.html

regards,
Juhani
--- End Message ---
--- Begin Message ---
Source: manpages-posix
Source-Version: 2017a-2
Done: Francesco Paolo Lovergine 

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

Debian distribution maintenance software
pp.
Francesco Paolo Lovergine  (supplier of updated 
manpages-posix package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 03 Feb 2021 14:13:29 +0100
Source: manpages-posix
Binary: manpages-posix manpages-posix-dev
Architecture: source all
Version: 2017a-2
Distribution: unstable
Urgency: medium
Maintainer: Francesco Paolo Lovergine 
Changed-By: Francesco Paolo Lovergine 
Description:
 manpages-posix - Manual pages about using POSIX system
 manpages-posix-dev - Manual pages about using a POSIX system for development
Closes: 981739
Changes:
 manpages-posix (2017a-2) unstable; urgency=medium
 .
   * Binary upload is due for non-free.
 (closes: #981739)
Checksums-Sha1:
 1f841cb57b754df675dd095d04dcf024ec6791a7 1916 manpages-posix_2017a-2.dsc
 253316056ebedbe97898b8785b60893e773e55bc 3984 
manpages-posix_2017a-2.debian.tar.xz
 368402087f7747bde6cfba4769e34f924b125285 1786976 
manpages-posix-dev_2017a-2_all.deb
 0a20f04822ce83509fdc7ed723aad63ba08d5406 931952 manpages-posix_2017a-2_all.deb
 01ac32b4bbe7c2b2f6b6c7b3c4d95962902574e7 5930 
manpages-posix_2017a-2_amd64.buildinfo
Checksums-Sha256:
 e37522e124c15d3079e135ba9c9260a6f08b614b713d7c89b5aa4b679ad62a8b 1916 
manpages-posix_2017a-2.dsc
 5b9a74f21d49c00932130b76295028867524cd3116cf8448663bf3ab6d2dbb2f 3984 
manpages-posix_2017a-2.debian.tar.xz
 eda156e5da4c260c8e124075a8d816de3d69831c316979998c4d5b28883fb65e 1786976 
manpages-posix-dev_2017a-2_all.deb
 3d8ad2a028a7f56c4ef0ef909b7e56bc7b362c64b36ac066ce70b6b36bafd55a 931952 
manpages-posix_2017a-2_all.deb
 1dbdee391173e74b2dd4a0050cf6777c7d3ee55846daca430d3143e7589d9201 5930 
manpages-posix_2017a-2_amd64.buildinfo
Files:
 6259e903a5b7d404809d1e1b3dab6a22 1916 non-free/doc optional 
manpages-posix_2017a-2.dsc
 62fe787e8167dd8054a0b75fc6753094 3984 non-free/doc optional 
manpages-posix_2017a-2.debian.tar.xz
 b17cbfd4c908c0fc72e06ff830bd1dcf 1786976 non-free/doc optional 
manpages-posix-dev_2017a-2_all.deb
 cfd373b952b195246446c432ec43136c 931952 non-free/doc optional 
manpages-posix_2017a-2_all.deb
 8ca26fae19792a79c160f3fd42923735 5930 non-free/doc optional 
manpages-posix_2017a-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJHBAEBCgAxFiEEBXmpeiI46/m+Ye0CDwKl4RY2hqQFAmAaoeUTHGZyYW5raWVA
ZGViaWFuLm9yZwAKCRAPAqXhFjaGpDWjEACeg7nT3QDHZIFBt+7nWpLkWFqZ7IH7
KmLWb4OLpSvn92GA6k26ezd5H6z5LMOoq6LN6aMe4uvPzMNlqAzVn4im1005SHU7
igAMQIBh3YQI63MSher2h3BF+iN8Y81kqqJdsxKI3K22veZpr2pgK5Zqz4QgiwxE
WlblHc+tmGT33VMCS49W5XXEgwtc5yhH23b5PICddmSlqeVFHdlLWCD6glsM3gJE
tIOZCMj5bURHLLlDhQ0PrF7Ljw39l3EhEWfRVvsM+kpW/Nn++uX9efrifrG4KlxS
/c6imP82WJiwgmsZPxDIDdRqFRedvc5Tl0Ev2H3FBByepa3h/EkRLDRljO7jFzQq
TldmDvD++rqmym49j6vkjBE90b2iSpG0qQ9DFah/fqeS0FYoeaMH0Ch7fW7woRQ4
ugFcQisIXkfgzTlDr0D95m6BH5uWCepQ6+ls52IAfMvSYC60GpA4cKfCux0V2hTZ
9OvfMu/+CkDxnfIC2m/WmB2on8TQDKgTRIz853GuEdZf53ZQVV2BpE7ZgJBdUq42
bZ6O5nPBM0EjdY2V8cfcf0bcC36WyQlNGNsBnne58x+1VUatvcM2wEsqHlzncXkh
6T7JmIij75YsCb8lx65vLYx80O3df55FgY1f7/X/SHrslnt/7ZE2C5y9wgAwoqeJ
Y6Z//Lqqzyj0Iw==
=FB2B

Bug#980844: marked as done (src:libbiblio-isis-perl: invalid maintainer address)

[Debian Bug Tracking System]

Your message dated Wed, 03 Feb 2021 13:33:37 +
with message-id 
and subject line Bug#980844: fixed in libbiblio-isis-perl 0.24-1.3
has caused the Debian Bug report #980844,
regarding src:libbiblio-isis-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.)


-- 
980844: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=980844
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libbiblio-isis-perl
Version: 0.24-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, 13 Jan 2021 15:57:04 +

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:

  joseparre...@cantv.net
retry timeout exceeded
Reporting-MTA: dns; mailly.debian.org

Action: failed
Final-Recipient: rfc822;joseparrella@cantv.net
Status: 5.0.0
--- End Message ---
--- Begin Message ---
Source: libbiblio-isis-perl
Source-Version: 0.24-1.3
Done: Baptiste Beauplat 

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

Debian distribution maintenance software
pp.
Baptiste Beauplat  (supplier of updated libbiblio-isis-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: Tue, 02 Feb 2021 21:03:11 +0100
Source: libbiblio-isis-perl
Architecture: source
Version: 0.24-1.3
Distribution: unstable
Urgency: medium
Maintainer: Jose Parrella 
Changed-By: Baptiste Beauplat 
Closes: 980844
Changes:
 libbiblio-isis-perl (0.24-1.3) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Fix Maintainer email address (Closes: #980844)
Checksums-Sha1:
 7718d3dec9f9561313b10f13c2ca8bd817af4925 1776 libbiblio-isis-perl_0.24-1.3.dsc
 614705806db12df300d7bb1cd6726dad65802025 2161 
libbiblio-isis-perl_0.24-1.3.diff.gz
 159f581454e36a0f226ff03058de5bf670990c04 5755 
libbiblio-isis-perl_0.24-1.3_amd64.buildinfo
Checksums-Sha256:
 fb9eb49f0950158b4eda4992469dd4310b7934f11c9b7242b788b01b05503228 1776 
libbiblio-isis-perl_0.24-1.3.dsc
 46f74a6da0bd466b0dd09a6316e0fc7a0c1123b50b51aef2a645ec4d45f5b47c 2161 
libbiblio-isis-perl_0.24-1.3.diff.gz
 5fba494c2118870d1e8114846e2f3a3688a0ed67f8abab384788471847b2efce 5755 
libbiblio-isis-perl_0.24-1.3_amd64.buildinfo
Files:
 efe071dccbf9452b5db23a4da71c5bc4 1776 perl optional 
libbiblio-isis-perl_0.24-1.3.dsc
 2f7f70d4c4d688b65c22f5a09afeea1e 2161 perl optional 
libbiblio-isis-perl_0.24-1.3.diff.gz
 82886af26113e6bf88ceee73edd71e3d 5755 perl optional 
libbiblio-isis-perl_0.24-1.3_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEi3hoeGwz5cZMTQpICBa54Yx2K60FAmAao6kACgkQCBa54Yx2
K62p4RAAgHGaS6TRP96X90n0CCEco5ZNYV12fiGgFajNwPkxtp/YbdEcdDJoxgdS
jdXroS+/CfMgybi4lhfuueFlOIBChdwL8zv/pMUWI5NLhPbGnlKb+sigy+75gFXh
HcINXXwiwud3BRv7Ye1QQtKqrJJPaQyCVzXkx5vAUTeReO2US9zEhzyazbleLzlz
mKbxxDDO2ORIjqJvYidepCEuopz8qLlLMwsl9ngm+IrdE7Llj9H2kpBc6ikZdEdf
2UUa44H6t3fwnk3YEXQIGtuIsFA7w++Fz+CQ1q7CUlGwYMqqX2yqWU3uXpKVlIJk
HNFse+5vO0f1dBu6s1OQQcHOZyQ2Pprp+dM2bsmANfNwM/Es6OmDOLpTNEGiJg5j
MS6Uqp4baxQoO3eNEQgUeeY/6y5gMG/bzTx5UuCP267gxNyVhBodc2mlNhz1ppqd
ezxYLrDQ18L0KD4un+fxatxfbV/vynTny3q3Z5dVbeDYoTT8V5OelZXweY7MFxKd
j5X7A5ITvsv88YfUCedVe/w8iLd2dRhtvzfkCxaLBAxU10LOgljUsTU9ln0Cdnfh
vUnAVz4WHhjFZwptMqiIITmRS0oAZeM24U+jCGGm4WP7p3arCfv3msONu8Y2D6kl
9kaTUFiJt1g3ZBSJQG/hpYxGmsOvq8ybTjsxhEL/bYazaUO74n4=
=bZn3
-END PGP SIGNATURE End Message ---

Bug#979052: marked as done (src:nam: invalid maintainer address)

[Debian Bug Tracking System]

Your message dated Wed, 03 Feb 2021 13:34:42 +
with message-id 
and subject line Bug#979052: fixed in nam 1.15-5.2
has caused the Debian Bug report #979052,
regarding src:nam: 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.)


-- 
979052: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979052
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: nam
Version: 1.15-5
Severity: serious
X-Debbugs-Cc: YunQiang Su , 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: Sat, 02 Jan 2021 00:37:27 +

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:

  pkg-netsim-de...@lists.alioth.debian.org
host alioth-lists-mx.debian.net [2001:ba8:0:2c77:0:4:0:1]
SMTP error from remote mail server after RCPT 
TO::
550 Unrouteable address
--- End Message ---
--- Begin Message ---
Source: nam
Source-Version: 1.15-5.2
Done: Baptiste Beauplat 

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 02 Feb 2021 19:55:11 +0100
Source: nam
Architecture: source
Version: 1.15-5.2
Distribution: unstable
Urgency: medium
Maintainer: Debian Network Simulators Team 
Changed-By: Baptiste Beauplat 
Closes: 979052
Changes:
 nam (1.15-5.2) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Fix Maintainer email address (Closes: #979052)
Checksums-Sha1:
 5f9433438aa9783d344d7657e195b343bbaecffb 2115 nam_1.15-5.2.dsc
 853533fc8804e91094b3ccb19645a742593362ce 9324 nam_1.15-5.2.debian.tar.xz
 3dc04e97eb2f6fe20226b8238c367612979fb67a 8766 nam_1.15-5.2_amd64.buildinfo
Checksums-Sha256:
 f7ead5ee5a054e3f4067d3b586cca1917739fbf998baff77d0a384512643872b 2115 
nam_1.15-5.2.dsc
 689fbbcc661f1f88b9b46d74dd95e370bcf6084099dff39d36c17a6909839b12 9324 
nam_1.15-5.2.debian.tar.xz
 aadab649825d561ab78402fc7168e8fdcee8da5532f1901a20d75ab53268c3ff 8766 
nam_1.15-5.2_amd64.buildinfo
Files:
 935c9fec3dedd1aa4868e3d99cd7f9ca 2115 net optional nam_1.15-5.2.dsc
 a4890224ab18a2181c99c3f6a17e54c2 9324 net optional nam_1.15-5.2.debian.tar.xz
 4d701a2c04a27e02e7c36512be8bcc4e 8766 net optional nam_1.15-5.2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEi3hoeGwz5cZMTQpICBa54Yx2K60FAmAaoxcACgkQCBa54Yx2
K61Hfg/9F3hPW97wL1tgHGespeVMwat5CT0brkc09H7RgNgRK7Z7Q7OZviElLzl/
juCu+sQfZgbfV7+KZ5kjcQMzbNhHtXGo7fLGGDjk6cZtMB/9CH7Tij2g+bLKYzFw
JlI2VeRA0G7vZ5F5F4faoLNZzLxET/YX0cO/8clcwouI7MzWuDDGb/MzHcd1ESxs
zbBY7on9WlETF5MdW7AOpF79dskdydSNA9Y4MgwcxVSJmA6Oyqri9+QzEo4QKfXa
d0S7jtW6nXwJ7xGPri+9sYgJWXdbLZZH436DNSvESKrpJCkh5d5jtRE+b9Kjssog
iNTFMhPH3OBJbXHD2uzR8pf2uceEBGGFoL3aNXu1FO5rRdGvVxdmQb1sV1EpJH9g
z5KqV2tT3BIhE+tV9+P+ThaU20pGC6ypuZrD29oDXUirwu2M8ZG32DI4HrfJNuJl
L5faozg81W5sIHeiOn4YYijtDcxrUKw+wcjEaPCOZ2cK6X/yW4217kGOfk9BazHh
MgbFamlfxFVlyS3Flj8RkNCQc0ywBMuhss9qI+ej5+lVllmUbaP9ogG8qGJXNuy7
YewVrxn4SvK8bePk9nhhmWxlfaRAO0oEz0Nfhv+os86CTq9uoy7mjc2ojSrm05Ig
vcDhWubVUDHpF5AoZvccUjCRVcC2wOCf1UllEPLqdg56d/yxl24=
=vsDY
-END PGP SIGNATURE End Message ---

Processed: ITP: python-makefun -- Small library to dynamically create Python functions

[Debian Bug Tracking System]

Processing control commands:

> block 981428 by -1
Bug #981428 [python3-fido2] python3-fido2: Version 0.9 breaks yubikey-manager
981428 was not blocked by any bugs.
981428 was not blocking any bugs.
Added blocking bug(s) of 981428: 981742

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

Bug#981720: FTBFS: FileNotFoundError: [Errno 2] No such file or directory: '/etc/resolv.conf'

[Thomas Goirand]

Hi,

Could you please explain in which build environment you don't have a
resolv.conf file?

Also, could you please send the full build log? Because like this, I
can't tell at which stage this happened. Was it during the build of the
documentation?

Cheers,

Thomas Goirand (zigo)

Bug#981739: manpages-posix: no-one built the package for debian archive (non-free, source-only upload)

[Francesco Paolo Lovergine]

On Wed, Feb 03, 2021 at 02:58:27PM +0200, Juhani Numminen wrote:

Package: manpages-posix
Version: 2017a-1
Severity: grave

Hello,

The latest upload of manpages-posix was source-only but was not built
on the buildd network either. So, no binaries are available.
I think the text of this lintian tag applies in this case:
https://lintian.debian.org/tags/source-only-upload-to-non-free-without-autobuild.html

regards,
Juhani



Ah finally someone noted it, eh? Yes, it has been my oversight at upload time.


--
Francesco P. Lovergine

Bug#980773: marked as done (python-pysaml2: CVE-2021-21238: Processing of invalid SAML XML documents)

[Debian Bug Tracking System]

Your message dated Wed, 03 Feb 2021 13:06:22 +
with message-id 
and subject line Bug#980773: fixed in python-pysaml2 6.5.1-1
has caused the Debian Bug report #980773,
regarding python-pysaml2: CVE-2021-21238: Processing of invalid SAML XML 
documents
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.)


-- 
980773: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=980773
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-pysaml2
Version: 6.1.0-3
Severity: grave
Tags: security upstream
Justification: user security hole
X-Debbugs-Cc: car...@debian.org, Debian Security Team 

Hi,

The following vulnerability was published for python-pysaml2.

CVE-2021-21238[0]:
| PySAML2 is a pure python implementation of SAML Version 2 Standard.
| PySAML2 before 6.5.0 has an improper verification of cryptographic
| signature vulnerability. All users of pysaml2 that need to validate
| signed SAML documents are impacted. The vulnerability is a variant of
| XML Signature wrapping because it did not validate the SAML document
| against an XML schema. This allowed invalid XML documents to be
| processed and such a document can trick pysaml2 with a wrapped
| signature. This is fixed in PySAML2 6.5.0.


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-2021-21238
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-21238
[1] 
https://github.com/IdentityPython/pysaml2/security/advisories/GHSA-f4g9-h89h-jgv9
[2] 
https://github.com/IdentityPython/pysaml2/commit/3b707723dcf1bf60677b424aac398c0c3557641d

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: python-pysaml2
Source-Version: 6.5.1-1
Done: Thomas Goirand 

We believe that the bug you reported is fixed in the latest version of
python-pysaml2, 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.
Thomas Goirand  (supplier of updated python-pysaml2 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: Wed, 03 Feb 2021 12:41:36 +0100
Source: python-pysaml2
Architecture: source
Version: 6.5.1-1
Distribution: unstable
Urgency: medium
Maintainer: Debian OpenStack 
Changed-By: Thomas Goirand 
Closes: 980772 980773
Changes:
 python-pysaml2 (6.5.1-1) unstable; urgency=medium
 .
   * New upstream release.
 - Fix CVE-2021-21238 and CVE-2021-21239 (Closes: #980772, #980773).
   * Update patches to match new upstream release.
   * Add python3-importlib-resources and python3-xmlschema as (build-)depends.
   * Reworked python3.9-use-encodebytes-not-encodestring.patch.
Checksums-Sha1:
 636afd201fd1b5812191836aca0966a8a6584a68 2619 python-pysaml2_6.5.1-1.dsc
 71aa7a915949a6f24f09518ad32c001b0f1870b1 3962132 
python-pysaml2_6.5.1.orig.tar.xz
 e44e89f5d7d02f78f34dd06f30c92d8845fef14e 7760 
python-pysaml2_6.5.1-1.debian.tar.xz
 110b40d081633b4b782c8db21b9a5b523288faa8 8986 
python-pysaml2_6.5.1-1_amd64.buildinfo
Checksums-Sha256:
 0f1a7b57eab819f52a433864a84844a64d6f68e9278072630a7fd571f7fc2f47 2619 
python-pysaml2_6.5.1-1.dsc
 7afdbc5e8c41a265564e3fb37f8b7c6a01c2aacb61ac868d9b31ed1bd0ac82af 3962132 
python-pysaml2_6.5.1.orig.tar.xz
 4b5141bd8afc551c5b112c484259cecff0a02ed46ff6af82ce4ad970d07a52ca 7760 
python-pysaml2_6.5.1-1.debian.tar.xz
 1bfa6252140dd433c5a02fb8e46d31d1a171541a72bc94f44775771b006a5457 8986 
python-pysaml2_6.5.1-1_amd64.buildinfo
Files:
 df963b7f6cc0b69043da5059a12bb2c1 2619 python optional 
python-pysaml2_6.5.1-1.dsc
 b2d9d12f682d6556712f119d2cd0e1f8 3962132 python optional 
python-pysaml2_6.5.1.orig.tar.xz
 7cd5858374a51a3c0785215c798d1605 7760 python optional 
python-pysaml2_6.5.1-1.debian.tar.xz
 f3d994dabba3e0eee09a0772771d89d9 8986 python optional 
python-pysaml2_6.5.1-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEoLGp81CJVhMOekJc1BatFaxrQ/4FAmAanMUACgkQ1BatFaxr
Q/5ruA//c5YixzYKUc1uzMhHOdlCeqm6G/LDyj0nqJgIizUGFArKePVkkQIqX/om
SyWJ78CbN4HWUU

Bug#980772: marked as done (python-pysaml2: CVE-2021-21239: Unspecified xmlsec1 key-type preference)

[Debian Bug Tracking System]

Your message dated Wed, 03 Feb 2021 13:06:22 +
with message-id 
and subject line Bug#980772: fixed in python-pysaml2 6.5.1-1
has caused the Debian Bug report #980772,
regarding python-pysaml2: CVE-2021-21239: Unspecified xmlsec1 key-type 
preference
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.)


-- 
980772: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=980772
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-pysaml2
Version: 6.1.0-3
Severity: grave
Tags: security upstream
Justification: user security hole
X-Debbugs-Cc: car...@debian.org, Debian Security Team 

Hi,

The following vulnerability was published for python-pysaml2.

CVE-2021-21239[0]:
| PySAML2 is a pure python implementation of SAML Version 2 Standard.
| PySAML2 before 6.5.0 has an improper verification of cryptographic
| signature vulnerability. Users of pysaml2 that use the default
| CryptoBackendXmlSec1 backend and need to verify signed SAML documents
| are impacted. PySAML2 does not ensure that a signed SAML document is
| correctly signed. The default CryptoBackendXmlSec1 backend is using
| the xmlsec1 binary to verify the signature of signed SAML documents,
| but by default xmlsec1 accepts any type of key found within the given
| document. xmlsec1 needs to be configured explicitly to only use only
| _x509 certificates_ for the verification process of the SAML document
| signature. This is fixed in PySAML2 6.5.0.


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-2021-21239
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-21239
[1] 
https://github.com/IdentityPython/pysaml2/commit/751dbf50a51131b13d55989395f9b115045f9737
[2] 
https://github.com/IdentityPython/pysaml2/security/advisories/GHSA-5p3x-r448-pc62

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: python-pysaml2
Source-Version: 6.5.1-1
Done: Thomas Goirand 

We believe that the bug you reported is fixed in the latest version of
python-pysaml2, 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.
Thomas Goirand  (supplier of updated python-pysaml2 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: Wed, 03 Feb 2021 12:41:36 +0100
Source: python-pysaml2
Architecture: source
Version: 6.5.1-1
Distribution: unstable
Urgency: medium
Maintainer: Debian OpenStack 
Changed-By: Thomas Goirand 
Closes: 980772 980773
Changes:
 python-pysaml2 (6.5.1-1) unstable; urgency=medium
 .
   * New upstream release.
 - Fix CVE-2021-21238 and CVE-2021-21239 (Closes: #980772, #980773).
   * Update patches to match new upstream release.
   * Add python3-importlib-resources and python3-xmlschema as (build-)depends.
   * Reworked python3.9-use-encodebytes-not-encodestring.patch.
Checksums-Sha1:
 636afd201fd1b5812191836aca0966a8a6584a68 2619 python-pysaml2_6.5.1-1.dsc
 71aa7a915949a6f24f09518ad32c001b0f1870b1 3962132 
python-pysaml2_6.5.1.orig.tar.xz
 e44e89f5d7d02f78f34dd06f30c92d8845fef14e 7760 
python-pysaml2_6.5.1-1.debian.tar.xz
 110b40d081633b4b782c8db21b9a5b523288faa8 8986 
python-pysaml2_6.5.1-1_amd64.buildinfo
Checksums-Sha256:
 0f1a7b57eab819f52a433864a84844a64d6f68e9278072630a7fd571f7fc2f47 2619 
python-pysaml2_6.5.1-1.dsc
 7afdbc5e8c41a265564e3fb37f8b7c6a01c2aacb61ac868d9b31ed1bd0ac82af 3962132 
python-pysaml2_6.5.1.orig.tar.xz
 4b5141bd8afc551c5b112c484259cecff0a02ed46ff6af82ce4ad970d07a52ca 7760 
python-pysaml2_6.5.1-1.debian.tar.xz
 1bfa6252140dd433c5a02fb8e46d31d1a171541a72bc94f44775771b006a5457 8986 
python-pysaml2_6.5.1-1_amd64.buildinfo
Files:
 df963b7f6cc0b69043da5059a12bb2c1 2619 python optional 
python-pysaml2_6.5.1-1.dsc
 b2d9d12f682d6556712f119d2cd0e1f8 3962132 python optional 
python-pysaml2_6.5.1.orig.tar.xz
 7cd5858374a51a3c0785215c798d1605 7760 python optional 
python-pysaml2_6.5.1-1.debian.tar.xz
 f3d994dabba3e0eee09a0772771d89d9 8986 python option

Bug#981739: manpages-posix: no-one built the package for debian archive (non-free, source-only upload)

[Juhani Numminen]

Package: manpages-posix
Version: 2017a-1
Severity: grave

Hello,

The latest upload of manpages-posix was source-only but was not built
on the buildd network either. So, no binaries are available.
I think the text of this lintian tag applies in this case:
https://lintian.debian.org/tags/source-only-upload-to-non-free-without-autobuild.html

regards,
Juhani

Processed: Bug#980773 marked as pending in python-pysaml2

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #980773 [src:python-pysaml2] python-pysaml2: CVE-2021-21238: Processing of 
invalid SAML XML documents
Added tag(s) pending.

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

Processed: Bug#980772 marked as pending in python-pysaml2

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #980772 [src:python-pysaml2] python-pysaml2: CVE-2021-21239: Unspecified 
xmlsec1 key-type preference
Added tag(s) pending.

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

Bug#980773: marked as pending in python-pysaml2

[Thomas Goirand]

Control: tag -1 pending

Hello,

Bug #980773 in python-pysaml2 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/openstack-team/python/python-pysaml2/-/commit/09588831e5c44773976cde966a48eb36d2a60511


* New upstream release.
- Fix CVE-2021-21238 and CVE-2021-21239 (Closes: #980772, #980773).


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/980773

Bug#980772: marked as pending in python-pysaml2

[Thomas Goirand]

Control: tag -1 pending

Hello,

Bug #980772 in python-pysaml2 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/openstack-team/python/python-pysaml2/-/commit/09588831e5c44773976cde966a48eb36d2a60511


* New upstream release.
- Fix CVE-2021-21238 and CVE-2021-21239 (Closes: #980772, #980773).


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/980772