Processed: Re: Bug#982273: libbsd0-udeb: depends on libmd0

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 src:libbsd 0.11.1-1
Bug #982273 [src:libbsd0-udeb] libbsd0-udeb: depends on libmd0
Warning: Unknown package 'src:libbsd0-udeb'
Bug reassigned from package 'src:libbsd0-udeb' to 'src:libbsd'.
No longer marked as found in versions libbsd0-udeb/0.11.1-1.
Ignoring request to alter fixed versions of bug #982273 to the same values 
previously set
Bug #982273 [src:libbsd] libbsd0-udeb: depends on libmd0
Marked as found in versions libbsd/0.11.1-1.

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

Bug#982273: libbsd0-udeb: depends on libmd0

[Andrei POPESCU]

Control: reassign -1 src:libbsd 0.11.1-1

On Lu, 08 feb 21, 02:25:01, Samuel Thibault wrote:
> Source: libbsd0-udeb

The BTS interprets this as Package: src:libbsd0-udeb (which doesn't 
exist).

> Version: 0.11.1-1
> Severity: serious
> Justification: makes debian-installer FTBFS
> 
> Hello,
> 
> The "new upstream" upload of libbsd builds a udeb that depends on a
> non-udeb:
> 
> The following packages have unmet dependencies:
>  libbsd0-udeb : Depends: libmd0 (>= 1.0.3) but it is not installable
> 
> Please avoid linking against libmd0, or else add a libmd0-udeb package
> to libmd.
> 
> Samuel
> 
> -- System Information:
> Debian Release: bullseye/sid
>   APT prefers testing
>   APT policy: (990, 'testing'), (500, 'unstable-debug'), (500, 
> 'testing-debug'), (500, 'stable-debug'), (500, 'proposed-updates-debug'), 
> (500, 'proposed-updates'), (500, 'oldoldstable'), (500, 'buildd-unstable'), 
> (500, 'unstable'), (500, 'stable'), (500, 'oldstable'), (1, 
> 'experimental-debug'), (1, 'buildd-experimental'), (1, 'experimental')
> Architecture: amd64 (x86_64)
> Foreign Architectures: i386
> 
> Kernel: Linux 5.10.0-1-amd64 (SMP w/8 CPU threads)
> Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
> Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE not 
> set
> Shell: /bin/sh linked to /usr/bin/dash
> Init: systemd (via /run/systemd/system)
> LSM: AppArmor: enabled
> 
> -- 
> Samuel
> c> ah (on trouve fluide glacial sur le net, ou il faut aller dans le monde 
> reel ?)
> s> dans le monde reel
> c> zut

Kind regards,
Andrei
-- 
Looking after bugs assigned to unknown or inexistent packages


signature.asc
Description: PGP signature

Bug#982046: marked as done (golang-github-avast-apkverifier: Missing test dependency on ca-certificates)

[Debian Bug Tracking System]

Your message dated Mon, 08 Feb 2021 07:33:32 +
with message-id 
and subject line Bug#982046: fixed in golang-github-avast-apkverifier 
0.0~git20191015.7330a51-5
has caused the Debian Bug report #982046,
regarding golang-github-avast-apkverifier: Missing test dependency on 
ca-certificates
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.)


-- 
982046: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=982046
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: golang-github-avast-apkverifier
Version: 0.0~git20191015.7330a51-4
Severity: serious

https://ci.debian.net/data/autopkgtest/testing/amd64/g/golang-github-avast-apkverifier/10269472/log.gz

...
autopkgtest [21:30:24]: test command1: ./runtests.sh
autopkgtest [21:30:24]: test command1: [---
+ [ -d apksig_for_tests ]
+ git clone --depth=1 -b android-o-mr1-iot-release-1.0.14 
https://android.googlesource.com/platform/tools/apksig apksig_for_tests
Cloning into 'apksig_for_tests'...
fatal: unable to access 
'https://android.googlesource.com/platform/tools/apksig/': server certificate 
verification failed. CAfile: none CRLfile: none
autopkgtest [21:30:25]: test command1: ---]
autopkgtest [21:30:25]: test command1:  - - - - - - - - - - results - - - - - - 
- - - -
command1 FAIL non-zero exit status 128
autopkgtest [21:30:25]: test command1:  - - - - - - - - - - stderr - - - - - - 
- - - -
+ [ -d apksig_for_tests ]
+ git clone --depth=1 -b android-o-mr1-iot-release-1.0.14 
https://android.googlesource.com/platform/tools/apksig apksig_for_tests
Cloning into 'apksig_for_tests'...
fatal: unable to access 
'https://android.googlesource.com/platform/tools/apksig/': server certificate 
verification failed. CAfile: none CRLfile: none
...
--- End Message ---
--- Begin Message ---
Source: golang-github-avast-apkverifier
Source-Version: 0.0~git20191015.7330a51-5
Done: Hans-Christoph Steiner 

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

Debian distribution maintenance software
pp.
Hans-Christoph Steiner  (supplier of updated 
golang-github-avast-apkverifier package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 08 Feb 2021 08:24:59 +0100
Source: golang-github-avast-apkverifier
Architecture: source
Version: 0.0~git20191015.7330a51-5
Distribution: unstable
Urgency: medium
Maintainer: Debian Go Packaging Team 
Changed-By: Hans-Christoph Steiner 
Closes: 982046
Changes:
 golang-github-avast-apkverifier (0.0~git20191015.7330a51-5) unstable; 
urgency=medium
 .
   * autopkgtest needs ca-certificates (Closes: #982046)
Checksums-Sha1:
 491470c3b00e31c5cdd08d9f51579bcaeaa20a9c 2212 
golang-github-avast-apkverifier_0.0~git20191015.7330a51-5.dsc
 b3a96538f4ebcad1b9778e521bfa178c6a1266c6 4824 
golang-github-avast-apkverifier_0.0~git20191015.7330a51-5.debian.tar.xz
 5247ba0d5f55a4bb98ebf0f3941ab4776e5a9c35 6008 
golang-github-avast-apkverifier_0.0~git20191015.7330a51-5_source.buildinfo
Checksums-Sha256:
 c1c00352155a6c6f1909d4c419dd18ecc5dabdb23576a1757fb43302bbc854c8 2212 
golang-github-avast-apkverifier_0.0~git20191015.7330a51-5.dsc
 32e02f56f3859e1ed6dd1a9be819ac0746ee8f0ecd054e7be9b40588cfc1eb15 4824 
golang-github-avast-apkverifier_0.0~git20191015.7330a51-5.debian.tar.xz
 9c9c96233dac8e0781b4d8bd3620fc0bd4b8b80127d8abf7070921e607fdcc69 6008 
golang-github-avast-apkverifier_0.0~git20191015.7330a51-5_source.buildinfo
Files:
 2db7acef47bc8351ca0ef1b88a4464f6 2212 devel optional 
golang-github-avast-apkverifier_0.0~git20191015.7330a51-5.dsc
 a2169615a4194826cfa2a09380c246b5 4824 devel optional 
golang-github-avast-apkverifier_0.0~git20191015.7330a51-5.debian.tar.xz
 ee2a93ec98439a92da64f071ba223e1d 6008 devel optional 
golang-github-avast-apkverifier_0.0~git20191015.7330a51-5_source.buildinfo

-BEGIN PGP SIGNATURE-

iQEzBAEBCAAdFiEElyI52+aGmfUmwGoFPhd4F7obm/oFAmAg54YACgkQPhd4F7ob
m/oKGQf8C2Mg9YniXyvmo1Nz1ssZixMxGZV82JaW2D/AahyjK3VA65z9xlbFoJW6

Processed: Bug#982046 marked as pending in golang-github-avast-apkverifier

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #982046 {Done: Hans-Christoph Steiner } 
[src:golang-github-avast-apkverifier] golang-github-avast-apkverifier: Missing 
test dependency on ca-certificates
Added tag(s) pending.

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

Bug#982046: marked as pending in golang-github-avast-apkverifier

[Hans-Christoph Steiner]

Control: tag -1 pending

Hello,

Bug #982046 in golang-github-avast-apkverifier 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/go-team/packages/golang-github-avast-apkverifier/-/commit/10b6ee64330ddc9a90328db8e6b5de650c0f8d1e


autopkgtest needs ca-certificates (Closes: #982046)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/982046

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

[andrew]

Any chance this bug is the root cause of 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=982157 ?

Bug#942988: Is there any forward movement on this bug?

[Charlie Hagedorn]

I've been a happy user of dispcalgui for years. I just rebooted my machine
(Debian testing, uptime > 140 days) and went to recalibrate, only to find
that displaycal had disappeared.

Looking at this thread upstream ( https://hub.displaycal.net/issue/17813/ )
it appears that the ETA for a port to Python3 is somewhere between 1/1/2020
and "when it's done".

As far as I am aware, displaycal is the premier display calibration gui for
linux. It works and works well. How can we help upstream bring it into
alignment with Debian requirements? Is a beta python3 port available for
community contributions/testing/debugging? Will donations help free up
upstream-maintainer's time to finish the port?

In the interim -- are there any workarounds for both generating new monitor
profiles and installing them?  Is calibration straightforward for a Spyder
5 via ArgyllCMS and the command line? A quick survey suggests I have a
bunch of unexpected learning to do.

Thanks!

Charlie

Bug#962844: mdadm: Assembling RAID using IMSM in initrd fails due to lack of module efivarfs

[Felix Lechner]

Hi Chris,

On Sun, Feb 7, 2021 at 9:22 AM Chris Hofstaedtler  wrote:
>
> friendly ping here, are you planning to fix this for bullseye?

Thanks for the reminder! I will probably include efivars in the next
couple of days.

Kind regards
Felix

Bug#982275: debianutils: add-shell depends on non-essential package

[Michael Gilbert]

package: src:debianutils
severity: serious
version: 4.11.2
tag: patch

debianutil's add-shell script uses awk, but awk is not an
Essential:yes package.  For systems where awk is not yet installed
(chroots), installation of dash will currently fail since it's
postinst calls add-shell from debianutils.

A simple fix seems possible, just change add-shell to use cat, which
is in coreutils (Essential:yes).  Proposed update attached.

Best wishes,
Mike
--- debianutils-4.11.2/add-shell	2020-05-22 20:00:40.0 -0400
+++ debianutils-4.11.3/add-shell	2021-02-07 21:47:27.0 -0500
@@ -17,7 +17,7 @@
 }
 trap cleanup EXIT
 
-if ! awk '{print}' "$file" > "$tmpfile"
+if ! cat "$file" > "$tmpfile"
 then
 cat 1>&2 <

Bug#982059: And another file conflict: /usr/share/man/de/man1/killall.1.gz

[Daniel Leidert]

And yet another file conflict with manpages-de:

[..]
dpkg: error processing archive /var/cache/apt/archives/psmisc_23.4-1_amd64.deb 
(--unpack):
 trying to overwrite '/usr/share/man/de/man1/killall.1.gz', which is also in 
package manpages-de 4.2.0-1
[..]

Regards, Daniel
-- 
Regards,
Daniel Leidert  | https://www.wgdd.de/
GPG-Key RSA4096 / BEED4DED5544A4C03E283DC74BCD0567C296D05D
GPG-Key ED25519 / BD3C132D8B3805D1808123AB7ACE00941E338C78

If you like my work consider sponsoring me via
https://www.patreon.com/join/dleidert


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

Bug#982273: libbsd0-udeb: depends on libmd0

[Samuel Thibault]

Source: libbsd0-udeb
Version: 0.11.1-1
Severity: serious
Justification: makes debian-installer FTBFS

Hello,

The "new upstream" upload of libbsd builds a udeb that depends on a
non-udeb:

The following packages have unmet dependencies:
 libbsd0-udeb : Depends: libmd0 (>= 1.0.3) but it is not installable

Please avoid linking against libmd0, or else add a libmd0-udeb package
to libmd.

Samuel

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

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

-- 
Samuel
c> ah (on trouve fluide glacial sur le net, ou il faut aller dans le monde reel 
?)
s> dans le monde reel
c> zut

Processed: closing 785813

[Debian Bug Tracking System]

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

> close 785813 0.9.0.88.g69f48b1-1
Bug #785813 [src:gnome-activity-journal] gnome-activity-journal: Please update 
to GStreamer 1.x
Marked as fixed in versions gnome-activity-journal/0.9.0.88.g69f48b1-1.
Bug #785813 [src:gnome-activity-journal] gnome-activity-journal: Please update 
to GStreamer 1.x
Marked Bug as done
> thanks
Stopping processing here.

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

Processed: closing 790583

[Debian Bug Tracking System]

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

> close 790583 0.9.0.88.g69f48b1-1
Bug #790583 [src:gnome-activity-journal] gnome-activity-journal: depends on 
python-gnome2 which is deprecated
Marked as fixed in versions gnome-activity-journal/0.9.0.88.g69f48b1-1.
Bug #790583 [src:gnome-activity-journal] gnome-activity-journal: depends on 
python-gnome2 which is deprecated
Marked Bug as done
> thanks
Stopping processing here.

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

Processed: unarchiving 785813, reopening 785813, unarchiving 790583, reopening 790583, unarchiving 577155 ...

[Debian Bug Tracking System]

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

> # src:gnome-activity-journal was reintroduced: 
> https://lists.debian.org/msgid-search/546c2c3d77eaef6dc2b26c7ed7663f16df847bda.ca...@debian.org
> unarchive 785813
Bug #785813 {Done: Debian FTP Masters } 
[src:gnome-activity-journal] gnome-activity-journal: Please update to GStreamer 
1.x
Unarchived Bug 785813
> reopen 785813
Bug #785813 {Done: Debian FTP Masters } 
[src:gnome-activity-journal] gnome-activity-journal: Please update to GStreamer 
1.x
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions 0.8.0-2.1+rm.
> unarchive 790583
Bug #790583 {Done: Debian FTP Masters } 
[src:gnome-activity-journal] gnome-activity-journal: depends on python-gnome2 
which is deprecated
Unarchived Bug 790583
> reopen 790583
Bug #790583 {Done: Debian FTP Masters } 
[src:gnome-activity-journal] gnome-activity-journal: depends on python-gnome2 
which is deprecated
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions 0.8.0-2.1+rm.
> unarchive 577155
Bug #577155 {Done: Debian FTP Masters } 
[gnome-activity-journal] Doesn't update on new events
Unarchived Bug 577155
> reopen 577155
Bug #577155 {Done: Debian FTP Masters } 
[gnome-activity-journal] Doesn't update on new events
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions 0.8.0-2.1+rm.
> unarchive 744191
Bug #744191 {Done: Debian FTP Masters } 
[gnome-activity-journal] gnome-activity-journal: doesn't start, import error
Unarchived Bug 744191
> reopen 744191
Bug #744191 {Done: Debian FTP Masters } 
[gnome-activity-journal] gnome-activity-journal: doesn't start, import error
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions 0.8.0-2.1+rm.
> unarchive 636362
Bug #636362 {Done: Debian FTP Masters } 
[gnome-activity-journal] gnome-activity-journal: ERROR:dbus.connection:Unable 
to set arguments
Unarchived Bug 636362
> reopen 636362
Bug #636362 {Done: Debian FTP Masters } 
[gnome-activity-journal] gnome-activity-journal: ERROR:dbus.connection:Unable 
to set arguments
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions 0.8.0-2.1+rm.
> unarchive 875855
Bug #875855 {Done: Debian FTP Masters } 
[gnome-activity-journal] Missing dependency on gnome-activity-journal package
Unarchived Bug 875855
> reopen 875855
Bug #875855 {Done: Debian FTP Masters } 
[gnome-activity-journal] Missing dependency on gnome-activity-journal package
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions 0.8.0-2.1+rm.
> unarchive 592253
Bug #592253 {Done: Debian FTP Masters } 
[gnome-activity-journal] [gnome-activity-journal] Don't recognize items from 
gnome-shell resent items
Unarchived Bug 592253
> reopen 592253
Bug #592253 {Done: Debian FTP Masters } 
[gnome-activity-journal] [gnome-activity-journal] Don't recognize items from 
gnome-shell resent items
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions 0.8.0-2.1+rm.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
577155: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=577155
592253: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=592253
636362: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=636362
744191: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=744191
785813: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=785813
790583: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=790583
875855: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875855
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: severity of 981524 is serious

[Debian Bug Tracking System]

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

> severity 981524 serious
Bug #981524 [src:mrd6] mrd6 - do not ship with bullseye?
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

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

Processed: closing 956902

[Debian Bug Tracking System]

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

> close 956902 1.7.0-1
Bug #956902 [python-reclass] python-reclass: Depends on cruft package 
python-yaml
There is no source info for the package 'python-reclass' at version '1.7.0-1' 
with architecture ''
Unable to make a source version for version '1.7.0-1'
Marked as fixed in versions 1.7.0-1.
Bug #956902 [python-reclass] python-reclass: Depends on cruft package 
python-yaml
Marked Bug as done
> thanks
Stopping processing here.

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

Processed: closing 938340

[Debian Bug Tracking System]

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

> close 938340 1.7.0-1
Bug #938340 [src:reclass] reclass: Python2 removal in sid/bullseye
Marked as fixed in versions reclass/1.7.0-1.
Bug #938340 [src:reclass] reclass: Python2 removal in sid/bullseye
Marked Bug as done
> thanks
Stopping processing here.

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

Processed (with 1 error): unarchiving 938340, reopening 938340, unarchiving 956902, reopening 956902, unarchiving 954458 ...

[Debian Bug Tracking System]

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

> # src:reclass was reintroduced: 
> https://lists.debian.org/msgid-search/546c2c3d77eaef6dc2b26c7ed7663f16df847bda.ca...@debian.org
> unarchive 938340
Bug #938340 {Done: Debian FTP Masters } 
[src:reclass] reclass: Python2 removal in sid/bullseye
Unarchived Bug 938340
> reopen 938340
Bug #938340 {Done: Debian FTP Masters } 
[src:reclass] reclass: Python2 removal in sid/bullseye
'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 1.4.1-3.1+rm.
> unarchive 956902
> reopen 956902
Bug #956902 {Done: Debian FTP Masters } 
[python-reclass] python-reclass: Depends on cruft package python-yaml
'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 1.4.1-3.1+rm.
> unarchive 954458
Bug #954458 {Done: Debian FTP Masters } 
[reclass] reclass: diff for NMU version 1.4.1-3.1
Unarchived Bug 954458
> reopen 954458
Bug #954458 {Done: Debian FTP Masters } 
[reclass] reclass: diff for NMU version 1.4.1-3.1
'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 1.4.1-3.1+rm.
> thanks
Stopping processing here.

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

Processed: unarchiving 956472, reopening 956472

[Debian Bug Tracking System]

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

> # src:atitvout was reintroduced: 
> https://lists.debian.org/msgid-search/546c2c3d77eaef6dc2b26c7ed7663f16df847bda.ca...@debian.org
> unarchive 956472
Bug #956472 {Done: Debian FTP Masters } 
[src:atitvout] atitvout: Consider removing this package
Unarchived Bug 956472
> reopen 956472
Bug #956472 {Done: Debian FTP Masters } 
[src:atitvout] atitvout: Consider removing this package
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions 0.4-13+rm.
> thanks
Stopping processing here.

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

Processed: closing 956472

[Debian Bug Tracking System]

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

> close 956472
Bug #956472 [src:atitvout] atitvout: Consider removing this package
Marked Bug as done
> thanks
Stopping processing here.

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

Processed: closing 945682

[Debian Bug Tracking System]

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

> close 945682 0.8.0-1
Bug #945682 [src:hatop] hatop: Python2 removal in sid/bullseye
Marked as fixed in versions hatop/0.8.0-1.
Bug #945682 [src:hatop] hatop: Python2 removal in sid/bullseye
Marked Bug as done
> thanks
Stopping processing here.

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

Processed: unarchiving 945682, reopening 945682

[Debian Bug Tracking System]

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

> # src:hatop was reintroduced: 
> https://lists.debian.org/msgid-search/546c2c3d77eaef6dc2b26c7ed7663f16df847bda.ca...@debian.org
> unarchive 945682
Bug #945682 {Done: Debian FTP Masters } 
[src:hatop] hatop: Python2 removal in sid/bullseye
Unarchived Bug 945682
> reopen 945682
Bug #945682 {Done: Debian FTP Masters } 
[src:hatop] hatop: Python2 removal in sid/bullseye
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions 0.7.7-1+rm.
> thanks
Stopping processing here.

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

Bug#948346: [PATCH] Ensure graceful signal handling when the pid file exists

[Chris Hofstaedtler]

* Eduard Bloch  [210208 00:43]:
> > Could you make an upload to DELAYED instead of further waiting?
> 
> I am no longer waiting, today is timeout day. Will use 7-DAY DELAYED
> queue, should be appropriate.

That upload somehow did not make it into the archive?

Chris

Bug#982266: marked as done (fltk1.1: ftbfs in sid)

[Debian Bug Tracking System]

Your message dated Mon, 08 Feb 2021 00:18:55 +
with message-id 
and subject line Bug#982266: fixed in fltk1.1 1.1.10-29
has caused the Debian Bug report #982266,
regarding fltk1.1: ftbfs in sid
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.)


-- 
982266: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=982266
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: fltk1.1
Version: 1.1.10-28
tags: patch
severity: serious

Hello, looks like the package fails because of:

   dh_missing
dh_missing: warning: usr/bin/fluid exists in debian/tmp but is not installed to 
anywhere 
dh_missing: warning: usr/share/man/cat1/fltk-config.1 exists in debian/tmp but 
is not installed to anywhere 
dh_missing: warning: usr/share/man/cat1/fluid.1 exists in debian/tmp but is not 
installed to anywhere 
dh_missing: warning: usr/share/man/cat3/fltk.3 exists in debian/tmp but is not 
installed to anywhere 
dh_missing: warning: usr/share/man/man1/fltk-config.1 exists in debian/tmp but 
is not installed to anywhere 
dh_missing: warning: usr/share/man/man1/fluid.1 exists in debian/tmp but is not 
installed to anywhere 
dh_missing: warning: usr/share/man/man3/fltk.3 exists in debian/tmp but is not 
installed to anywhere 
dh_missing: error: missing files, aborting
The following debhelper tools have reported what they installed (with 
files per package)
 * dh_install: fltk1.1-doc (1), fltk1.1-games (11), libfltk1.1 (4), 
libfltk1.1-dev (11)
 * dh_installdocs: fltk1.1-doc (4), fltk1.1-games (2), libfltk1.1 (2), 
libfltk1.1-dev (2)
 * dh_installman: fltk1.1-doc (0), fltk1.1-games (0), libfltk1.1 (0), 
libfltk1.1-dev (2)
If the missing files are installed by another tool, please file a bug 
against it.
When filing the report, if the tool is not part of debhelper itself, 
please reference the
"Logging helpers and dh_missing" section from the "PROGRAMMING" guide 
for debhelper (10.6.3+).
  (in the debhelper package: /usr/share/doc/debhelper/PROGRAMMING.gz)
Be sure to test with dpkg-buildpackage -A/-B as the results may vary 
when only a subset is built
If the omission is intentional or no other helper can take care of this 
consider adding the
paths to debian/not-installed.
make: *** [debian/rules:16: binary] Error 25
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2


(this is probably due to compat=13 change)

I think, to fix we can just add
override_dh_missing:
dh_missing --list-missing

Or do something else, like removing files, start installing them, or something 
different (e.g. debian/not-installed).

Please have a look if possible!

thanks

Gianfranco
--- End Message ---
--- Begin Message ---
Source: fltk1.1
Source-Version: 1.1.10-29
Done: Aaron M. Ucko 

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

Debian distribution maintenance software
pp.
Aaron M. Ucko  (supplier of updated fltk1.1 package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 07 Feb 2021 18:56:37 -0500
Source: fltk1.1
Architecture: source
Version: 1.1.10-29
Distribution: unstable
Urgency: high
Maintainer: Aaron M. Ucko 
Changed-By: Aaron M. Ucko 
Closes: 982266
Changes:
 fltk1.1 (1.1.10-29) unstable; urgency=high
 .
   * Address dh_missing errors in compat 13 mode.  (Closes: #982266.)
 - debian/rules: Skip installation of fluid, which fltk1.3 took over
   years ago.
 - debian/not-installed (new): Acknowledge deliberate omission of
   uncompressed man pages.
   * libfltk1.1.symbols: Mark a symbol that GCC 10 presumably introduced
 as optional and available as of 1.1.10-28~.
Checksums-Sha1:
 e4a99ada6a3be256c0dc2bc29cfbb803eff3114a 2356 fltk1.1_1.1.10-29.dsc
 842df6bee191a918c94259c62a46e32a6cf49bf6 44336 fltk1.1_1.1.10-29.debian.tar.xz
Checksums-Sha256:
 07c9d31b97c9320b41a872c656b0e6cb990b05d3db897798268b91f0c78cc49c 2356 
fltk1.1_1.1.10-29.dsc
 e10ed63dea468962260a2b78c443248320b9c03ce69e16ba89886ec54b6d 44336 

Bug#982144: php-klogger: Useless in Bullseye

[James Valleroy]

Hi Paul,

On 2/7/21 2:56 PM, Paul Gevers wrote:
> Hi James,
> 
> On 07-02-2021 18:23, James Valleroy wrote:
>> It has no dependencies in Buster, so there is no reason for an end user to 
>> install it.
>>
>> A PHP developer could use the package though. But I think they are more 
>> likely to use composer to download/install what they need.
> 
> So, you're saying it was useless to ship in buster?
> 

Yes, it was useless to ship in buster.

Regards,
James



OpenPGP_signature
Description: OpenPGP digital signature

Bug#982266: fltk1.1: ftbfs in sid

[Aaron M. Ucko]

Gianfranco Costamagna  writes:

> dh_missing: error: missing files, aborting

Oops!  Thanks for pointing it out; I'm surprised the autobuilders didn't.

> (this is probably due to compat=13 change)

Indeed.

I'm on it now, with a mixed approach of skipping fluid installation and
meanwhile listing uncompressed man (and cat!) pages in
debian/not-installed.

-- 
Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org)
http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu

Processed: assign myself bugs

[Debian Bug Tracking System]

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

> owner 980668 !
Bug #980668 [src:golang-github-cznic-lldb] golang-github-cznic-lldb: FTBFS: 
expects import "modernc.org/fileutil"
Bug #980573 [src:golang-github-cznic-lldb] golang-github-cznic-lldb 1.0.1-1 
fails to build from source (ftbfs)
Owner recorded as Aloïs Micard .
Owner recorded as Aloïs Micard .
> owner 980573 !
Bug #980573 [src:golang-github-cznic-lldb] golang-github-cznic-lldb 1.0.1-1 
fails to build from source (ftbfs)
Bug #980668 [src:golang-github-cznic-lldb] golang-github-cznic-lldb: FTBFS: 
expects import "modernc.org/fileutil"
Ignoring request to set the owner of bug #980573 to the same value
Ignoring request to set the owner of bug #980668 to the same value
> --
Stopping processing here.

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

Processed: assign myself bugs

[Debian Bug Tracking System]

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

> owner 980379 !
Bug #980379 [src:golang-github-cznic-b] FTBFS: expects import 
"modernc.org/mathutil"
Owner recorded as Aloïs Micard .
> owner 980706 !
Bug #980706 [src:golang-github-cznic-ql] golang-github-cznic-ql: FTBFS: expects 
import "modernc.org/mathutil"
Bug #980572 [src:golang-github-cznic-ql] golang-github-cznic-ql 1.0.6-1 fails 
to build from source (ftbfs)
Owner recorded as Aloïs Micard .
Owner recorded as Aloïs Micard .
> owner 980572 !
Bug #980572 [src:golang-github-cznic-ql] golang-github-cznic-ql 1.0.6-1 fails 
to build from source (ftbfs)
Bug #980706 [src:golang-github-cznic-ql] golang-github-cznic-ql: FTBFS: expects 
import "modernc.org/mathutil"
Ignoring request to set the owner of bug #980572 to the same value
Ignoring request to set the owner of bug #980706 to the same value
> --
Stopping processing here.

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

Bug#982266: fltk1.1: ftbfs in sid

[Gianfranco Costamagna]

Source: fltk1.1
Version: 1.1.10-28
tags: patch
severity: serious

Hello, looks like the package fails because of:

   dh_missing
dh_missing: warning: usr/bin/fluid exists in debian/tmp but is not installed to 
anywhere 
dh_missing: warning: usr/share/man/cat1/fltk-config.1 exists in debian/tmp but 
is not installed to anywhere 
dh_missing: warning: usr/share/man/cat1/fluid.1 exists in debian/tmp but is not 
installed to anywhere 
dh_missing: warning: usr/share/man/cat3/fltk.3 exists in debian/tmp but is not 
installed to anywhere 
dh_missing: warning: usr/share/man/man1/fltk-config.1 exists in debian/tmp but 
is not installed to anywhere 
dh_missing: warning: usr/share/man/man1/fluid.1 exists in debian/tmp but is not 
installed to anywhere 
dh_missing: warning: usr/share/man/man3/fltk.3 exists in debian/tmp but is not 
installed to anywhere 
dh_missing: error: missing files, aborting
The following debhelper tools have reported what they installed (with 
files per package)
 * dh_install: fltk1.1-doc (1), fltk1.1-games (11), libfltk1.1 (4), 
libfltk1.1-dev (11)
 * dh_installdocs: fltk1.1-doc (4), fltk1.1-games (2), libfltk1.1 (2), 
libfltk1.1-dev (2)
 * dh_installman: fltk1.1-doc (0), fltk1.1-games (0), libfltk1.1 (0), 
libfltk1.1-dev (2)
If the missing files are installed by another tool, please file a bug 
against it.
When filing the report, if the tool is not part of debhelper itself, 
please reference the
"Logging helpers and dh_missing" section from the "PROGRAMMING" guide 
for debhelper (10.6.3+).
  (in the debhelper package: /usr/share/doc/debhelper/PROGRAMMING.gz)
Be sure to test with dpkg-buildpackage -A/-B as the results may vary 
when only a subset is built
If the omission is intentional or no other helper can take care of this 
consider adding the
paths to debian/not-installed.
make: *** [debian/rules:16: binary] Error 25
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2


(this is probably due to compat=13 change)

I think, to fix we can just add
override_dh_missing:
dh_missing --list-missing

Or do something else, like removing files, start installing them, or something 
different (e.g. debian/not-installed).

Please have a look if possible!

thanks

Gianfranco

Bug#982256: marked as done (spyder-line-profiler FTBFS with Spyder 4.2.1)

[Debian Bug Tracking System]

Your message dated Sun, 07 Feb 2021 22:39:04 +
with message-id 
and subject line Bug#982256: fixed in spyder-line-profiler 0.2.1-1
has caused the Debian Bug report #982256,
regarding spyder-line-profiler FTBFS with Spyder 4.2.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.)


-- 
982256: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=982256
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: spyder-line-profiler
Version: 0.1.1-1.1
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/fetch.php?pkg=spyder-line-profiler=all=0.1.1-1.1=1612695817=0

...
 ERRORS 
_ ERROR collecting 
.pybuild/cpython3_3.9_spyder-line-profiler/build/spyder_line_profiler/widgets/tests/test_lineprofiler.py
 _
ImportError while importing test module 
'/<>/.pybuild/cpython3_3.9_spyder-line-profiler/build/spyder_line_profiler/widgets/tests/test_lineprofiler.py'.
Hint: make sure your test modules/packages have valid Python names.
Traceback:
/usr/lib/python3.9/importlib/__init__.py:127: in import_module
return _bootstrap._gcd_import(name[level:], package, level)
spyder_line_profiler/__init__.py:12: in 
from .lineprofiler import LineProfiler
spyder_line_profiler/lineprofiler.py:18: in 
from spyder.plugins import SpyderPluginWidget, runconfig
E   ImportError: cannot import name 'SpyderPluginWidget' from 'spyder.plugins' 
(/usr/lib/python3/dist-packages/spyder/plugins/__init__.py)
--- Captured stdout 
Update LANGUAGE_CODES (inside config/base.py) if a new translation has been 
added to Spyder
--- Captured stderr 
QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-buildd'
=== short test summary info 
ERROR spyder_line_profiler/widgets/tests/test_lineprofiler.py
 Interrupted: 1 error during collection 
=== 1 error in 0.65s ===
E: pybuild pybuild:353: test: plugin distutils failed with: exit code=2: cd 
/<>/.pybuild/cpython3_3.9_spyder-line-profiler/build; python3.9 -m 
pytest 
dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.9 
returned exit code 13
make: *** [debian/rules:12: build-indep] Error 25



Compatibility withg Spyder 4 seems to be in the latest upstream version.
--- End Message ---
--- Begin Message ---
Source: spyder-line-profiler
Source-Version: 0.2.1-1
Done: Julian Gilbey 

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

Debian distribution maintenance software
pp.
Julian Gilbey  (supplier of updated spyder-line-profiler 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 07 Feb 2021 21:38:57 +
Source: spyder-line-profiler
Architecture: source
Version: 0.2.1-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Julian Gilbey 
Closes: 896427 904188 982256
Changes:
 spyder-line-profiler (0.2.1-1) unstable; urgency=medium
 .
   * Team upload.
   * New upstream version (closes: #982256, #896427, #904188)
   * Bump Standards-Version to 4.5.1
Checksums-Sha1:
 6730f51733ce3ea64304b803ef866a1e507a624e 2420 spyder-line-profiler_0.2.1-1.dsc
 585005dfe42b485484c92a804fe562ce4b08b68b 16712 
spyder-line-profiler_0.2.1.orig.tar.gz
 b01c612b3065e5c7471bb85756851ad3743af522 2304 
spyder-line-profiler_0.2.1-1.debian.tar.xz
 ad98313f051c67f29f58cbfbada0d4cf0b713bd9 15898 
spyder-line-profiler_0.2.1-1_amd64.buildinfo
Checksums-Sha256:
 9b8b6b94823648f010bf4ed0d418de974696d91d0ae9167d30c3d99bfdb50d20 2420 
spyder-line-profiler_0.2.1-1.dsc
 5b6272cd3b8d21700289f58ad10ed72c689d8d8fb742fce1a22e93a6d3f63f1f 16712 
spyder-line-profiler_0.2.1.orig.tar.gz
 cda2df4b7649abf7ae712cafdad718fbfb2cd8b5aa0abaac7ee87c8e6e17e3f0 2304 
spyder-line-profiler_0.2.1-1.debian.tar.xz
 

Bug#980655: marked as done (lbzip2: FTBFS: /usr/bin/gnulib-tool: *** minimum supported autoconf version is 2.64. Try adding AC_PREREQ([2.64]) to your configure.ac.)

[Debian Bug Tracking System]

Your message dated Sun, 07 Feb 2021 22:36:53 +
with message-id 
and subject line Bug#980655: fixed in lbzip2 2.5-2.1
has caused the Debian Bug report #980655,
regarding lbzip2: FTBFS: /usr/bin/gnulib-tool: *** minimum supported autoconf 
version is 2.64. Try adding AC_PREREQ([2.64]) to your configure.ac.
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.)


-- 
980655: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=980655
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: lbzip2
Version: 2.5-2
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):
>  fakeroot debian/rules binary
> dh binary 
> dh: warning: Compatibility levels before 10 are deprecated (level 9 in use)
>debian/rules build-arch
> make[1]: Entering directory '/<>'
> sh build-aux/autogen.sh
> + perl ./build-aux/make-crctab.pl
> + perl ./build-aux/make-scantab.pl
> + gnulib-tool --avoid=xalloc-die --add-import pthread utimens warnings 
> timespec-add timespec-sub dtotimespec stat-time lstat malloc-gnu 
> fprintf-posix inttypes xalloc largefile gitlog-to-changelog
> /usr/bin/gnulib-tool: *** minimum supported autoconf version is 2.64. Try 
> adding AC_PREREQ([2.64]) to your configure.ac.
> /usr/bin/gnulib-tool: *** Stop.
> make[1]: *** [debian/rules:12: build-arch] Error 1

The full build log is available from:
   http://qa-logs.debian.net/2021/01/20/lbzip2_2.5-2_unstable.log

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

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

If you fail to reproduce this, please provide a build log and diff it with me
so that we can identify if something relevant changed in the meantime.

About the archive rebuild: The rebuild was done on 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: lbzip2
Source-Version: 2.5-2.1
Done: Boyuan Yang 

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 04 Feb 2021 16:37:24 -0500
Source: lbzip2
Architecture: source
Version: 2.5-2.1
Distribution: unstable
Urgency: high
Maintainer: Mikolaj Izdebski 
Changed-By: Boyuan Yang 
Closes: 980655
Changes:
 lbzip2 (2.5-2.1) unstable; urgency=high
 .
   * Non-maintainer upload.
   * debian/control: Replace obsolete Priority: extra with
 Priority: optional.
   * debian/patches/0001-configure-ac: Bump AC_PREREQ to 2.64.
 This fixes FTBFS with newer gnulib. (Closes: #980655)
Checksums-Sha1:
 74ad8e029373df50df712b9ce128cc3ab743e239 1824 lbzip2_2.5-2.1.dsc
 e0ed740c4a85ae7b23dba4f30470b11342d1756f 514852 lbzip2_2.5.orig.tar.bz2
 7861b448c0696063d97ea451a3d4224671c434e2 6156 lbzip2_2.5-2.1.debian.tar.bz2
 91470a6083560114b1b193708c9c0976e069b2d2 5636 lbzip2_2.5-2.1_amd64.buildinfo
Checksums-Sha256:
 a85d9cb38aee20860bd7bada6fbe70abbdda8d3e080d20cc48665317d7888d27 1824 
lbzip2_2.5-2.1.dsc
 eec4ff08376090494fa3710649b73e5412c3687b4b9b758c93f73aa7be27555b 514852 
lbzip2_2.5.orig.tar.bz2
 8e001944b9b77e5c80b9a87249ea5a7964f100d605fe03eaf0f337c088bd7497 6156 
lbzip2_2.5-2.1.debian.tar.bz2
 d37db5a9802517a481402e5773c27e917f583e2cc6a406db77d248701bd183c9 5636 
lbzip2_2.5-2.1_amd64.buildinfo
Files:
 b33e6e80e63abba3bc3eeb16ad42e6a1 1824 utils optional lbzip2_2.5-2.1.dsc
 91d2d25798229cb34c1258ecee503fd4 514852 utils optional lbzip2_2.5.orig.tar.bz2
 4d8637436cad51d7af4f65623dd8955a 6156 utils optional 
lbzip2_2.5-2.1.debian.tar.bz2
 5eb5b9d88764ab5ca81b5e0964cbd911 5636 utils optional 

Bug#968131: marked as done (hdate-applet FTBFS with gcc-10)

[Debian Bug Tracking System]

Your message dated Sun, 07 Feb 2021 22:36:41 +
with message-id 
and subject line Bug#968131: fixed in hdate-applet 0.15.11-4
has caused the Debian Bug report #968131,
regarding hdate-applet 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.)


-- 
968131: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=968131
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: hdate-applet
Version: 0.15.11-3
Severity: serious
Tags: ftbfs

hdate-applet fails to build from source in unstable:

| gcc  -g -O2 -ffile-prefix-map=/build/1st/hdate-applet-0.15.11=. 
-fstack-protector-strong -Wformat -Werror=format-security  -Wl,-z,relro -o 
ghcal ghcal-main.o ghcal-interface.o ghcal-callbacks.o  -lm -lhdate 
-lgtk-x11-2.0 -lgdk-x11-2.0 -lpangocairo-1.0 -latk-1.0 -lcairo -lgdk_pixbuf-2.0 
-lgio-2.0 -lpangoft2-1.0 -lpango-1.0 -lgobject-2.0 -lglib-2.0 -lharfbuzz 
-lfontconfig -lfreetype
| /usr/bin/ld: ghcal-interface.o:./src/ghcal-interface.h:46: multiple 
definition of `label_month'; ghcal-main.o:./src/ghcal-interface.h:46: first 
defined here
| /usr/bin/ld: ghcal-interface.o:./src/ghcal-interface.h:47: multiple 
definition of `label_year'; ghcal-main.o:./src/ghcal-interface.h:47: first 
defined here
| /usr/bin/ld: ghcal-interface.o:./src/ghcal-interface.h:50: multiple 
definition of `label_hebrew_month_and_year'; 
ghcal-main.o:./src/ghcal-interface.h:50: first defined here
| /usr/bin/ld: ghcal-interface.o:./src/ghcal-interface.h:54: multiple 
definition of `event_box_day_of_month'; 
ghcal-main.o:./src/ghcal-interface.h:54: first defined here
| /usr/bin/ld: ghcal-interface.o:./src/ghcal-interface.h:51: multiple 
definition of `index_day_of_month'; ghcal-main.o:./src/ghcal-interface.h:51: 
first defined here
| /usr/bin/ld: ghcal-interface.o:./src/ghcal-interface.h:53: multiple 
definition of `label_day_of_month'; ghcal-main.o:./src/ghcal-interface.h:53: 
first defined here
| /usr/bin/ld: ghcal-interface.o:./src/ghcal-interface.h:55: multiple 
definition of `tooltip_day_of_month'; ghcal-main.o:./src/ghcal-interface.h:55: 
first defined here
| /usr/bin/ld: ghcal-interface.o:./src/ghcal-interface.h:45: multiple 
definition of `today'; ghcal-main.o:./src/ghcal-interface.h:45: first defined 
here
| /usr/bin/ld: ghcal-interface.o:./src/ghcal-interface.h:52: multiple 
definition of `hdate_day_of_month'; ghcal-main.o:./src/ghcal-interface.h:52: 
first defined here
| /usr/bin/ld: ghcal-interface.o:./src/ghcal-interface.h:49: multiple 
definition of `spinbutton_year'; ghcal-main.o:./src/ghcal-interface.h:49: first 
defined here
| /usr/bin/ld: ghcal-interface.o:./src/ghcal-interface.h:48: multiple 
definition of `combobox_month'; ghcal-main.o:./src/ghcal-interface.h:48: first 
defined here
| /usr/bin/ld: ghcal-callbacks.o:./src/ghcal-interface.h:45: multiple 
definition of `today'; ghcal-main.o:./src/ghcal-interface.h:45: first defined 
here
| /usr/bin/ld: ghcal-callbacks.o:./src/ghcal-interface.h:54: multiple 
definition of `event_box_day_of_month'; 
ghcal-main.o:./src/ghcal-interface.h:54: first defined here
| /usr/bin/ld: ghcal-callbacks.o:./src/ghcal-interface.h:46: multiple 
definition of `label_month'; ghcal-main.o:./src/ghcal-interface.h:46: first 
defined here
| /usr/bin/ld: ghcal-callbacks.o:./src/ghcal-interface.h:47: multiple 
definition of `label_year'; ghcal-main.o:./src/ghcal-interface.h:47: first 
defined here
| /usr/bin/ld: ghcal-callbacks.o:./src/ghcal-interface.h:53: multiple 
definition of `label_day_of_month'; ghcal-main.o:./src/ghcal-interface.h:53: 
first defined here
| /usr/bin/ld: ghcal-callbacks.o:./src/ghcal-interface.h:52: multiple 
definition of `hdate_day_of_month'; ghcal-main.o:./src/ghcal-interface.h:52: 
first defined here
| /usr/bin/ld: ghcal-callbacks.o:./src/ghcal-interface.h:55: multiple 
definition of `tooltip_day_of_month'; ghcal-main.o:./src/ghcal-interface.h:55: 
first defined here
| /usr/bin/ld: ghcal-callbacks.o:./src/ghcal-interface.h:50: multiple 
definition of `label_hebrew_month_and_year'; 
ghcal-main.o:./src/ghcal-interface.h:50: first defined here
| /usr/bin/ld: ghcal-callbacks.o:./src/ghcal-interface.h:51: multiple 
definition of `index_day_of_month'; ghcal-main.o:./src/ghcal-interface.h:51: 
first defined here
| /usr/bin/ld: ghcal-callbacks.o:./src/ghcal-interface.h:49: multiple 
definition of `spinbutton_year'; ghcal-main.o:./src/ghcal-interface.h:49: first 
defined here
| /usr/bin/ld: ghcal-callbacks.o:./src/ghcal-interface.h:48: multiple 
definition of `combobox_month'; ghcal-main.o:./src/ghcal-interface.h:48: first 
defined here
| collect2: error: ld 

Processed: Re: Bug#980592: clamav: FTBFS: check_jsnorm.c:250:57: error: format not a string literal and no format arguments [-Werror=format-security]

[Debian Bug Tracking System]

Processing control commands:

> tags -1 patch fixed-upstream
Bug #980592 [src:clamav] clamav: FTBFS: check_jsnorm.c:250:57: error: format 
not a string literal and no format arguments [-Werror=format-security]
Added tag(s) patch and fixed-upstream.
> forwarded -1 https://github.com/Cisco-Talos/clamav-devel/commit/18306
Bug #980592 [src:clamav] clamav: FTBFS: check_jsnorm.c:250:57: error: format 
not a string literal and no format arguments [-Werror=format-security]
Set Bug forwarded-to-address to 
'https://github.com/Cisco-Talos/clamav-devel/commit/18306'.

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

Bug#980592: clamav: FTBFS: check_jsnorm.c:250:57: error: format not a string literal and no format arguments [-Werror=format-security]

[John Scott]

Control: tags -1 patch fixed-upstream
Control: forwarded -1 https://github.com/Cisco-Talos/clamav-devel/commit/18306

I found that the build succeeds with the upstream patch. It seems like
ck_assert_msg() was missing an argument.

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

Bug#982059: manpages-de,psmisc: File conflict between psmisc and manpages-de: '/usr/share/man/de/man1/fuser.1.gz

[Craig Small]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Hi,
  I think you have the control lines wrong.  You have both the lines from
psmisc and manpages-de there.

Breaks: manpages-de (<= 2.16-1), psmisc (<< 23.4-2)
Replaces: manpages-de (<= 2.16-1)

Think of Breaks as "someone won't have the manpage or there will be two of
them if this happens"
Replaces is "we took the file from that package", its replacing files not
packages.

So, manpage-de should have "Breaks: psmisc ( << 23.4-2)"
This means:
  * If you install this new manpage-de and have psmisc below 23.4-2 you
won't have the German psmisc manpages.

The next psmisc release will have "Breaks: manpage-de (<< 4.9.1-1),
Replaces: manpages-de ( << 4.9.1-1)"
This means:
  * If you install a new psmisc and old manpage-de then there are TWO
manpages, so don't do that.
  * The new psmisc replaces files in the old manpage-de

manpages-de *only* needs the Breaks psmisc bit.

The Breaks line sort of force an update of the other package too.

 - Craig

On 2021-02-07 at 17:17, deb...@helgefjell.de wrote:
> tags 982059 + pending
> thanks
>
> Hello Craig,
> the manpage-l10n package is ready to go. You can either pick it up
> from git https://salsa.debian.org/debian/manpages-l10n.git and perfom
> "gbp buildpackage" or you can download the packages "ready to sign and
> upload" from my site:
> https://www.helgefjell.de/data/manpages-l10n_4.9.1-1.tar.xz
> https://www.helgefjell.de/data/manpages-l10n_4.9.1-1.tar.xz.sig
>
> Since the Freeze is rapidly approaching an upload at your earliest
> possiblity would be highly appreciated.
>
> In case of problems I'll respond within 24 hours.
>
> Thanks for your support.
>
> Greetings
>
>  Helge
> --
>   Dr. Helge Kreutzmann deb...@helgefjell.de
>Dipl.-Phys.
http://www.helgefjell.de/debian.php
> 64bit GNU powered gpg signed mail preferred
>Help keep free software "libre": http://www.ffii.de/
-BEGIN PGP SIGNATURE-
Version: FlowCrypt Email Encryption 8.0.2
Comment: Seamlessly send and receive encrypted email

wsFzBAEBCgAGBQJgIGDQACEJEAIhZsD/PITjFiEEXT3w9TizJ8CqeneiAiFm
wP88hOPAcg/+K2tS6kBZWdimiP9o87j5hEjcnUGFJsfAE1I6lMLvQWYABY+b
PRodB42Hj9CRF7+iGxL/QyHdpyUEKiaA/sYmYZAfUkr6mg+NNfzcNG94EbU8
BRkvXm5IB0J4v9x4ORKU8NwJcLTvMC1jCQuX8SuDm3hFVnmTzTXI5wfJ1ObF
tWIiYbAydh7OUlpmMvydDlvilqazcQFWoZsJUglYHziio2/y1yUlxBTL+dAt
MPjwHKd4i030gIhG/EwlGMVVtlDobs0AZeUFemsEN67uq3Zb34wG+g8XKDQZ
bUIo2ZA0NcZrNQXpcmGUTBpswb1chU2bGW7cDBenJKB74HBGHODW70De8D2i
763yvHDlB6doZdJnulmBcfFkUDpLz2wY1t+6urthYjYPCGzHNjK7luqSEsmK
dwLgCb+V95flpyxWmS3ZAiceT6W20vXRsGaX03XPdkbQa4f0TbId6Q9FsYSy
c1lVvfLE2a3hh0oCdzDVBtAoWfShuWHsX8DL1C8SmEFSnz/sh54bPZ0UAwDq
2kif8jAvYjPegbHow6Px3m2fvRVUBacwO22QzM1p/QcJ8DZC3WEoNdeY6+ST
1oWGeP0DbARbGVocqmjCxNJtywTWf2Wl2QCyxRAJV68d+mMJMP4znXA3Ed5r
nysOB2gsttFpj63ZkxyG8kIN2tIHd4hMiuQ=
=gRs1
-END PGP SIGNATURE-


0x3938F96BDF50FEA5.asc
Description: application/pgp-keys

Bug#977765: [Pkg-fonts-devel] Bug#977765: src:gsfonts: package superseded by fonts-urw-base35

[Jonas Smedegaard]

Quoting Paul Gevers (2021-02-07 22:04:25)
> Hi Jonas,
> 
> On 07-02-2021 13:44, Jonas Smedegaard wrote:
> > Quoting Paul Gevers (2021-02-07 12:07:08)
> >> With "quite some work" I mean that there are > 20 packages in testing 
> >> that need to change (are bugs already filed?). I understand from your 
> >> explanation that we already have a "Provides" in the fontconfig ID, 
> >> how bad would it be if fonts-urw-base35 add the Debian Provides: 
> >> gsfonts too? If that happens, we can (technically at least) drop 
> >> gsfonts, but how bad would that look (for those that rely on the 
> >> additional features of gsfonts)?
> > 
> > I think you are asking the wrong question here:
> 
> ? I'm wearing my Release Team member hat here. Fixing > 20 packages
> isn't great at this stage of the release. So, *if* this bug is indeed so
> severe as you claim, them I'm looking for options. Adding the Provides
> to fonts-urw-base35 enables us to remove gsfonts, which is what you
> want. I now realize I didn't make that totally clear and I think you
> misread my intentions.

I know that you are wearing your Release Team member hat. I appreciate 
your looking into this issue - with or without that hat on.

I agree with your reasoning that changing 20 packages isn't great and 
that alternative options are more relevant.

I only dismissed the question - i.e. last half of your last sentence: 
"how bad would instead getting fonts-urw-base35 be for those that rely 
on additional features of gsfonts?"

I am sorry if I misunderstood that question.  If I _did_ understand it 
then I don't know how to sensibly answer it, because those that rely on 
additional features of gsfonts _already_ do not (reliably) use gsfonts.


> > Those that rely on the undocumented additional features of gsfonts 
> > already today cannot be certain that they have them!  Most systems 
> > have ghostscript installed and therefore not *only* gsfonts but 
> > *both* that and fonts-urw-base35.
> 
> I understood that from your earlier mail, thanks.

I thought you did, but got uncertain due to that question of yours.

Again, I am sorry if I missed the meaning of that question :-(


> >  a) ensure that 20+ packages declaring a dependency on "look-alike 
> > fonts of the Adobe PostScript fonts" get the most accurate 
> > look-alike for the Adobe PostScript fonts: Have the package 
> > fonts-urw-base35 declare "Provides: gsfonts"
> 
> This is what I had in mind. You forgot to add, and drop gsfonts the 
> binary.

Right, when a) is implemented, this bug can be solved because then this 
package should no longer be used by any packages.

NB! I have *not* closely examined each case e.g. for versioned 
dependencies, but I guess even that should be possible nowadays to 
address without messing directly with those packages, using versioned 
Provides.


> >  b) ensure that 20+ packages declaring a dependency on "look-alike 
> > fonts of the Adobe PostScript fonts" get a specific (known 
> > inaccurate!) look-alike for the Adobe PostScript fonts: Have 
> > each of those packages declare "Conflicts: fonts-urw-base35" 
> > (unless they do *not* use fontconfig but explicit file paths to 
> > load those fonts)
> 
> In my opinion, too late. And again, are the bug reports for those
> packages already there?

I have done no preparations for this option - I don't like this option. 
It's just part of my answering my own question - to clarify why as I see 
it the only sensible approach here does _not_ involve directy messing 
with 20+ packages.


> >  c) ensure that 20+ packages declaring a dependency on "look-alike 
> > fonts of the Adobe PostScript fonts" continue to only maybe get 
> > what they declared - depending on whether their system happens 
> > to provide them different fonts instead.
> 
> But you claim that this is RC worthy. What's more, you claim that very 
> late in the release cycle (I think the issue hasn't changed since 
> buster, jessie or even longer) when there is not much time to decide 
> what to do and gsfonts is *currently* a key package that can't just be 
> removed so we need to decide the path to continue, autoremoval won't 
> do the work for you. Is this font issue really worth all that *now*?

I think that this namespace clash is a real issue, regardless of it 
having existed a long time.

If the only options available to solve this issue involved messing 
directly with 20+ packages, then (if I had a Release Team member hat) I 
would probably judge it too late and flag it as ignore-for-this-release.


> > My own answer would be that b) is the most work, c) is the least work, 
> > but b) is reasonably little work while solving this bug.
>   ^^ I assume you meant a) here. So I think we agree?

Yes!  Arrgh, sorry for that crucial and confusing mistake.


> > ...which gets us back to the original question of filing this 
> > bugreport: Is this bug real, and if so is it worth fixing for 
> > bullseye?
> 
> That's 

Bug#982144: php-klogger: Useless in Bullseye

[Petter Reinholdtsen]

[James Valleroy]
> Yes, it was useless to ship in buster.

While I can not vouch for php-klogger, I do know as a Debian user that I
often are pleasently surprised to find libraries I need for software
packages not currently in Debian.  Such library might lack reverse
dependencies in the Debian archive, but still provide value to the users
that need it. :)

This make it very hard to verify if a package is truly useless to ship
in a stable release. :)

-- 
Vennlig hilsen
Petter Reinholdtsen

Bug#980705: marked as done (golang-github-cznic-strutil: FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && go test -vet=off -v -p 1 github.com/cznic/strutil returned exit code 1)

[Debian Bug Tracking System]

Your message dated Sun, 7 Feb 2021 22:19:23 +0100
with message-id <54acf531-b0f8-cf25-aa98-f5b85dbb9...@micard.lu>
and subject line close 980705
has caused the Debian Bug report #980705,
regarding golang-github-cznic-strutil: FTBFS: dh_auto_test: error: cd 
obj-x86_64-linux-gnu && go test -vet=off -v -p 1 github.com/cznic/strutil 
returned exit code 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.)


-- 
980705: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=980705
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: golang-github-cznic-strutil
Version: 0.0~git20150430.0.1eb03e3-2
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):
>  debian/rules build
> dh build --buildsystem=golang --with=golang
> dh: warning: Compatibility levels before 10 are deprecated (level 9 in use)
>dh_update_autotools_config -O--buildsystem=golang
>dh_auto_configure -O--buildsystem=golang
> dh_auto_configure: warning: Compatibility levels before 10 are deprecated 
> (level 9 in use)
>dh_auto_build -O--buildsystem=golang
> dh_auto_build: warning: Compatibility levels before 10 are deprecated (level 
> 9 in use)
>   cd obj-x86_64-linux-gnu && go install -trimpath -v -p 1 
> github.com/cznic/strutil
> internal/unsafeheader
> internal/cpu
> internal/bytealg
> runtime/internal/atomic
> runtime/internal/sys
> runtime/internal/math
> runtime
> internal/reflectlite
> errors
> internal/race
> sync/atomic
> sync
> io
> unicode
> unicode/utf8
> bytes
> math/bits
> math
> strconv
> encoding/base32
> reflect
> encoding/binary
> encoding/base64
> sort
> internal/fmtsort
> internal/oserror
> syscall
> internal/syscall/unix
> time
> internal/poll
> internal/syscall/execenv
> internal/testlog
> os
> fmt
> strings
> github.com/cznic/strutil
>dh_auto_test -O--buildsystem=golang
> dh_auto_test: warning: Compatibility levels before 10 are deprecated (level 9 
> in use)
>   cd obj-x86_64-linux-gnu && go test -vet=off -v -p 1 
> github.com/cznic/strutil
> # github.com/cznic/strutil
> src/github.com/cznic/strutil/all_test.go:10:2: code in directory 
> /<>/obj-x86_64-linux-gnu/src/github.com/cznic/mathutil expects 
> import "modernc.org/mathutil"
> FAIL  github.com/cznic/strutil [setup failed]
> FAIL
> dh_auto_test: error: cd obj-x86_64-linux-gnu && go test -vet=off -v -p 1 
> github.com/cznic/strutil returned exit code 1

The full build log is available from:
   
http://qa-logs.debian.net/2021/01/20/golang-github-cznic-strutil_0.0~git20150430.0.1eb03e3-2_unstable.log

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

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

If you fail to reproduce this, please provide a build log and diff it with me
so that we can identify if something relevant changed in the meantime.

About the archive rebuild: The rebuild was done on 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 ---

This bug has been fixed by the new release of golang-github-cznic-mathutil 
(0.0~git20201220.c6aa83b-2),
I've only forgotten to mention it in the changelog.

Cheers,

--
Aloïs Micard (creekorful) 

GPG: DA4A A436 9BFA E299 67CD E85B F733 E871 0859 FCD2--- End Message ---

Bug#982144: php-klogger: Useless in Bullseye

[James Valleroy]

On 2/7/21 2:54 AM, Paul Gevers wrote:
> Hi James,
> 
> On Sat, 06 Feb 2021 15:10:04 -0500 James Valleroy
>> This is a dependency only for shaarli, which will not be included in 
>> Bullseye.
> 
> We already shipped this package in buster. Do you really think it's
> useless for users there without shaarli? Is it enough useless to not
> ship it?

It has no dependencies in Buster, so there is no reason for an end user to 
install it.

A PHP developer could use the package though. But I think they are more likely 
to use composer to download/install what they need.

I opened bugs like this for all the dependencies of shaarli, after discussion 
in #980134.
Do you agree with this approach in general?

Regards,
James



OpenPGP_signature
Description: OpenPGP digital signature

Bug#982212: marked as done (simka: autopkgtest needs same architecture list as simka)

[Debian Bug Tracking System]

Your message dated Sun, 07 Feb 2021 21:18:31 +
with message-id 
and subject line Bug#982212: fixed in simka 1.5.3-2
has caused the Debian Bug report #982212,
regarding simka: autopkgtest needs same architecture list as simka
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.)


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

On armhf:

https://ci.debian.net/data/autopkgtest/testing/armhf/s/simka/10291613/log.gz

...
autopkgtest [04:46:22]: test run-unit-test: [---
cp: cannot stat '/usr/share/doc/simka/example': No such file or directory
autopkgtest [04:46:23]: test run-unit-test: ---]
autopkgtest [04:46:23]: test run-unit-test:  - - - - - - - - - - results - - - 
- - - - - - -
run-unit-testFAIL non-zero exit status 1



The autopkgtest cannot work with only simkamin installed.
--- End Message ---
--- Begin Message ---
Source: simka
Source-Version: 1.5.3-2
Done: Shayan Doust 

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

Debian distribution maintenance software
pp.
Shayan Doust  (supplier of updated simka package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 07 Feb 2021 20:06:22 +
Source: simka
Architecture: source
Version: 1.5.3-2
Distribution: unstable
Urgency: high
Maintainer: Debian Med Packaging Team 

Changed-By: Shayan Doust 
Closes: 982212
Changes:
 simka (1.5.3-2) unstable; urgency=high
 .
   * Make autopkgtest have the same arch list as d/control (Closes: #982212)
Checksums-Sha1:
 ae07908ccc408acad0d4012ec88ca25563a570a7 2199 simka_1.5.3-2.dsc
 a76b3350c683cc32ea784bb44118f87b2cc309d3 21056 simka_1.5.3-2.debian.tar.xz
 f8a2fd556434dc7e493a56a8859452c8e99a9cb2 7850 simka_1.5.3-2_amd64.buildinfo
Checksums-Sha256:
 620a2530964f79f85032a0304ca68c56667e64419dfdc9d71fd6d57cc69db253 2199 
simka_1.5.3-2.dsc
 bf4bbc7d65bdf8444556bf1424e124c69a472b2ee81b02693a1580f2d8039f98 21056 
simka_1.5.3-2.debian.tar.xz
 870186a8253249610d02b7b8f63946dc96341afbd6113f60e35a976f927c13a6 7850 
simka_1.5.3-2_amd64.buildinfo
Files:
 190bd91718482c00f6147583fe2c0286 2199 science optional simka_1.5.3-2.dsc
 a36a7ac9a61c20f5b87e85a8612a2d46 21056 science optional 
simka_1.5.3-2.debian.tar.xz
 2380bc1cc0b62342c2cefd12ae191936 7850 science optional 
simka_1.5.3-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJJBAEBCgAzFiEEBAGoEKbyQwMeo5dZbX1EGRnQI5UFAmAgU38VHGhlbGxvQHNo
YXlhbmRvdXN0Lm1lAAoJEG19RBkZ0COVcSIP/3QiNWc1PvJ2O9tLfxZdQbWv/DBE
oMSiCOeWsfOuUR5X3xBd1+eOPwY8hDPW5k68B3GGvErkUFNz2+FY3oqCqE/42li8
+mQPc4nzwbPYEBa1SnGJlhX9UtyBzyC1qitgVDReQtuly6w8cThUdMpPzDr2qpkj
hc6u2yohkXaGmD4iknj0uFLvi6umEAParee0fb1YEDbCjvFN3+Fg6GWH2Vn1eWbo
PDH7Etn/kf76hmcnayUR2K/sqeXk1cR99Z6mVZaQRqVViH5aHVNDLwiX/nPwBhZU
FHtif011UOmBYAPpyMA6YPl15Ddi/hSifrQvkUcfO0RDpF1I8A1QNxJQq4FL79FV
e4pySg0Vrvf641vc52XcdrnsLRgqNA/KCV4yb3pzi4Mtifkna1RCkEc0Hrb4dUd7
kh5eDagkFLYQFIf0E8I2d4fR3XxzufmaD7IpKBda03W0CC0YP1iBxKGES3syPwG9
ndSc9KpNK1UxewE1JElBwLe+Gf+Mtkc2WLEZhyxtYi5JWIs31wFjv9sAjBARuPhG
wuTmxrm+Vr3kfxPe0P4bDtuj9ekMp//E6vnQKPUtNVoy6mvqWPKe6WFQlhyHZjjJ
PHkSGmNNBLJ9n37LeUMsHi+F80aazM/icQlmRcwk0tyWRVzjqdzznvlkQYPS7cId
T33x4ABhbOuDKcee
=0gvr
-END PGP SIGNATURE End Message ---

Processed: Re: Bug#977060: cwltool FTBFS with pytest 6

[Debian Bug Tracking System]

Processing control commands:

> tag -1 unreproducible
Bug #977067 [src:igdiscover] igdiscover FTBFS with pytest 6
Added tag(s) unreproducible.
> tag -1 moreinfo
Bug #977067 [src:igdiscover] igdiscover FTBFS with pytest 6
Added tag(s) moreinfo.

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

Bug#977067: Bug#977060: cwltool FTBFS with pytest 6

[Étienne Mollier]

Control: tag -1 unreproducible
Control: tag -1 moreinfo

Hi there,

I tried to reproduce the bug by building igdiscover 0.11-3 using
sbuild in a clean Sid chroot which did include pytest 6:

$ schroot -c unstable-amd64-sbuild -d / \
  -- apt-cache show python3-pytest  \
  | grep Version:
Version: 6.0.2-2

I haven't been able to reproduce the problem, the build went
through.  I'm not sure what I'm missing.  Can someone else
reproduce the issue ?

Kind Regards,
-- 
Étienne Mollier 
Fingerprint:  8f91 b227 c7d6 f2b1 948c  8236 793c f67e 8f0d 11da
Sent from /dev/pts/2, please excuse my verbosity.


signature.asc
Description: PGP signature

Bug#974686: marked as done (python3-blockdev: Missing dependencies, without deps to gir1.2-blockdev-2.0 the python module in unsable)

[Debian Bug Tracking System]

Your message dated Sun, 07 Feb 2021 21:05:30 +
with message-id 
and subject line Bug#974686: fixed in libblockdev 2.25-1
has caused the Debian Bug report #974686,
regarding python3-blockdev: Missing dependencies, without deps to 
gir1.2-blockdev-2.0 the python module in unsable
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.)


-- 
974686: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=974686
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python3-blockdev
Version: 2.20-7+deb10u1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

What's need to be done:
- Play arround with the BlockDev API within python

What exactly did you do (or not do) that was effective (or ineffective)?
- Do a simple apt install python3-blockdev and install with deps
- Run this piece of code with the offcial pyobject docs as reference 
  - 

=== Python Source ===
import gi
from gi import Repository
version = Repository.get_default().enumerate_versions("BlockDev")
gi.require_version("BlockDev", version[0] if version else "2.0")
from gi.repository import BlockDev
print(BlockDev.__name__)
===

What was the outcome of this action?

Traceback (most recent call last):
  File "", line 1, in 
  File "/usr/lib/python3/dist-packages/gi/__init__.py", line 129, in 
require_version
raise ValueError('Namespace %s not available' % namespace)
ValueError: Namespace Blockdev not available

* What outcome did you expect instead?

gi.repository.BlockDev to stdout

* Found Workarround:

Run apt install gir1.2-blockdev-2.0 install with deps and rerun the python 
snippet

* Proposed Solution:
Make python3-blockdev depends on gir1.2-blockdev-2.0 OR maka a reference in 
suggested package


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

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

Versions of packages python3-blockdev depends on:
ii  libblockdev2  2.20-7+deb10u1
ii  python3   3.7.3-1
ii  python3-gi3.30.4-1

python3-blockdev recommends no packages.

python3-blockdev suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: libblockdev
Source-Version: 2.25-1
Done: Michael Biebl 

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

Debian distribution maintenance software
pp.
Michael Biebl  (supplier of updated libblockdev package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 07 Feb 2021 21:45:49 +0100
Source: libblockdev
Architecture: source
Version: 2.25-1
Distribution: unstable
Urgency: medium
Maintainer: Utopia Maintenance Team 

Changed-By: Michael Biebl 
Closes: 974686
Changes:
 libblockdev (2.25-1) unstable; urgency=medium
 .
   * Team upload
   * New upstream release
   * Bump Standards-Version to 4.5.1
   * Fix bd_lvm_vdopooldata_* symbols
   * Set upstream metadata fields: Bug-Submit, Bug-Database, Repository,
 Repository-Browse
   * Fix dependencies of python3-blockdev.
 It requires gir1.2-blockdev-2.0, libblockdev2 is only an indirect
 dependency. (Closes: #974686)
   * Bump debhelper-compat to 13
Checksums-Sha1:
 3f476cfe0841205278600792f6fb3733ccb94fa2 5075 libblockdev_2.25-1.dsc
 31c783ce1c4ea2adbd8dc10162782c7f7f2ac0b7 397576 libblockdev_2.25.orig.tar.gz
 93c8738bd2708f267dc6d12c365aa0a5d9963f5b 10716 libblockdev_2.25-1.debian.tar.xz
 250b35d86cedeacb49a51a5690021237a68a6b48 14442 
libblockdev_2.25-1_source.buildinfo
Checksums-Sha256:
 5207d80070b473fc1c3453ca2bedc553d1e1aa64095d256d740fb41a8f23348b 5075 
libblockdev_2.25-1.dsc
 

Bug#977765: [Pkg-fonts-devel] Bug#977765: src:gsfonts: package superseded by fonts-urw-base35

[Paul Gevers]

Hi Jonas,

On 07-02-2021 13:44, Jonas Smedegaard wrote:
> Quoting Paul Gevers (2021-02-07 12:07:08)
>> With "quite some work" I mean that there are > 20 packages in testing 
>> that need to change (are bugs already filed?). I understand from your 
>> explanation that we already have a "Provides" in the fontconfig ID, 
>> how bad would it be if fonts-urw-base35 add the Debian Provides: 
>> gsfonts too? If that happens, we can (technically at least) drop 
>> gsfonts, but how bad would that look (for those that rely on the 
>> additional features of gsfonts)?
> 
> I think you are asking the wrong question here:

? I'm wearing my Release Team member hat here. Fixing > 20 packages
isn't great at this stage of the release. So, *if* this bug is indeed so
severe as you claim, them I'm looking for options. Adding the Provides
to fonts-urw-base35 enables us to remove gsfonts, which is what you
want. I now realize I didn't make that totally clear and I think you
misread my intentions.

> Those that rely on the undocumented additional features of gsfonts 
> already today cannot be certain that they have them!  Most systems have 
> ghostscript installed and therefore not *only* gsfonts but *both* that 
> and fonts-urw-base35.

I understood that from your earlier mail, thanks.

> For its documented purpose, gsfonts is *known* to be slightly broken - 
> and using fonts-urw-base35 is the solution to that bug.  But as long as 
> gsfonts is *also* installed, each and every user must *bypass* 
> fontconfig and explicitly use file paths to ensure that they get the 
> non-broken fonts.

Ack.

> Instead, I would ask which of these is more work:
> 
>  a) ensure that 20+ packages declaring a dependency on "look-alike fonts 
> of the Adobe PostScript fonts" get the most accurate look-alike for 
> the Adobe PostScript fonts: Have the package fonts-urw-base35 
> declare "Provides: gsfonts"

This is what I had in mind. You forgot to add, and drop gsfonts the binary.

>  b) ensure that 20+ packages declaring a dependency on "look-alike fonts 
> of the Adobe PostScript fonts" get a specific (known inaccurate!) 
> look-alike for the Adobe PostScript fonts: Have each of those 
> packages declare "Conflicts: fonts-urw-base35" (unless they do *not* 
> use fontconfig but explicit file paths to load those fonts)

In my opinion, too late. And again, are the bug reports for those
packages already there?

>  c) ensure that 20+ packages declaring a dependency on "look-alike fonts 
> of the Adobe PostScript fonts" continue to only maybe get what they
> declared - depending on whether their system happens to provide them
> different fonts instead.

But you claim that this is RC worthy. What's more, you claim that very
late in the release cycle (I think the issue hasn't changed since
buster, jessie or even longer) when there is not much time to decide
what to do and gsfonts is *currently* a key package that can't just be
removed so we need to decide the path to continue, autoremoval won't do
the work for you. Is this font issue really worth all that *now*?

> My own answer would be that b) is the most work, c) is the least work, 
> but b) is reasonably little work while solving this bug.
  ^^ I assume you meant a) here. So I think we agree?

> ...which gets us back to the original question of filing this bugreport: 
> Is this bug real, and if so is it worth fixing for bullseye?

That's exactly my question too. And I'm really leaning now to "not for
bullseye, it's too late". This is no regression from the last couple of
releases after all.

> Answering that question involves the maintainer of fonts-urw-base35, who 
> seems to agree that the issue is real, but seems to consider c) more 
> reasonably to preserve than to fix this bug (hence my comment that I can 
> choose to ignore this bug for 10 more years if need be).

So, is the maintainer in the loop? He replied once, but do you know if
he follows our conversation?

Paul



OpenPGP_signature
Description: OpenPGP digital signature

Bug#957342: marked as done (hspell-gui: ftbfs with GCC-10)

[Willy nilly]

close  #957342

On Sun, Feb 7, 2021 at 8:51 PM Debian Bug Tracking System <
ow...@bugs.debian.org> wrote:

> Your message dated Sun, 07 Feb 2021 20:49:12 +
> with message-id 
> and subject line Bug#957342: fixed in hspell-gui 0.2.6-7
> has caused the Debian Bug report #957342,
> regarding hspell-gui: 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.)
>
>
> --
> 957342: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957342
> Debian Bug Tracking System
> Contact ow...@bugs.debian.org with problems
>
>
>
> -- Forwarded message --
> From: Matthias Klose 
> To: mainto...@bugs.debian.org
> Cc:
> Bcc:
> Date: Fri, 17 Apr 2020 11:02:32 +
> Subject: hspell-gui: ftbfs with GCC-10
> Package: src:hspell-gui
> Version: 0.2.6-6
> 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/hspell-gui_0.2.6-6_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
>
> [...]
> /usr/include/glib-2.0/glib/gtypes.h:551:8: note: declared here
>   551 | struct _GTimeVal
>   |^
> gcc -DHAVE_CONFIG_H -I. -I.. -DPACKAGE_DATA_DIR=\""/usr/share"\"
> -DPACKAGE_LOCALE_DIR=\""/usr/share/locale"\" -pthread
> -I/usr/include/gtk-2.0 -I/usr/lib/x86_64-linux-gnu/gtk-2.0/include
> -I/usr/include/pango-1.0 -I/usr/include/atk-1.0 -I/usr/include/cairo
> -I/usr/include/pixman-1 -I/usr/include/gdk-pixbuf-2.0
> -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/pango-1.0
> -I/usr/include/harfbuzz -I/usr/include/pango-1.0 -I/usr/include/fribidi
> -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include
> -I/usr/include/uuid -I/usr/include/freetype2 -I/usr/include/libpng16-g
> -O2 -c -o callbacks.o callbacks.c
> In file included from /usr/include/gtk-2.0/gtk/gtkobject.h:37,
>  from /usr/include/gtk-2.0/gtk/gtkwidget.h:36,
>  from /usr/include/gtk-2.0/gtk/gtkcontainer.h:35,
>  from /usr/include/gtk-2.0/gtk/gtkbin.h:35,
>  from /usr/include/gtk-2.0/gtk/gtkwindow.h:36,
>  from /usr/include/gtk-2.0/gtk/gtkdialog.h:35,
>  from /usr/include/gtk-2.0/gtk/gtkaboutdialog.h:32,
>  from /usr/include/gtk-2.0/gtk/gtk.h:33,
>  from callbacks.c:5:
> /usr/include/gtk-2.0/gtk/gtktypeutils.h:236:1: warning: ‘GTypeDebugFlags’
> is deprecated [-Wdeprecated-declarations]
>   236 | voidgtk_type_init   (GTypeDebugFlagsdebug_flags);
>   | ^~~~
> In file included from /usr/include/glib-2.0/gobject/gobject.h:24,
>  from /usr/include/glib-2.0/gobject/gbinding.h:29,
>  from /usr/include/glib-2.0/glib-object.h:23,
>  from /usr/include/glib-2.0/gio/gioenums.h:28,
>  from /usr/include/glib-2.0/gio/giotypes.h:28,
>  from /usr/include/glib-2.0/gio/gio.h:26,
>  from /usr/include/gtk-2.0/gdk/gdkapplaunchcontext.h:30,
>  from /usr/include/gtk-2.0/gdk/gdk.h:32,
>  from /usr/include/gtk-2.0/gtk/gtk.h:32,
>  from callbacks.c:5:
> /usr/include/glib-2.0/gobject/gtype.h:679:1: note: declared here
>   679 | {
>   | ^
> In file included from /usr/include/gtk-2.0/gtk/gtktoolitem.h:31,
>  from /usr/include/gtk-2.0/gtk/gtktoolbutton.h:30,
>  from /usr/include/gtk-2.0/gtk/gtkmenutoolbutton.h:30,
>  from /usr/include/gtk-2.0/gtk/gtk.h:126,
> 

Bug#981600: nghttp2: util_localtime_date test fails in arch-only build

[Helmut Grohne]

On Sun, Feb 07, 2021 at 08:51:36PM +0100, Chris Hofstaedtler wrote:
> I'm just passing by, but a local rebuild with `sbuild -d unstable
> -j8 --no-arch-all` did not show this problem (on amd64). There has
> to be more to it.

Thank you. I retried it to day (sbuild -d unstable --no-arch-all
nghttp2 on amd64) and it failed in the same way. I'm left puzzled what
could be different here. One aspect that certainly is not entirely usual
is that my chroot lives on a large tmpfs. Could that pose any problems?

Any other details I could add to help better understand the issue?

Helmut

Bug#980085: open-iscsi: initiator does not connect

[Heinrich Schuchardt]

On 2/7/21 8:36 PM, Chris Hofstaedtler wrote:

Hello Heinrich,

I'm going to upload upstream's fix. Maybe you can give it a try.

Best,
Chris


Debian release 2.1.3-2 added

+upstream/0001-iscsiadm-Fix-memory-leak-in-iscsiadm.patch
+upstream/0002-Fix-iscsiadm-segfault-when-exiting.patch
+upstream/0003-Fix-iscsistart-login-issue-when-target-is-delayed.patch

I have built the package from
https://salsa.debian.org/linux-blocks-team/open-iscsi
commit 7334ed475e26b8

This works for me but still shows the warning

iscsistart: initiator reported error (15 - session exists)

Tested-by: Heinrich Schuchardt 

Bug#957342: marked as done (hspell-gui: ftbfs with GCC-10)

[Debian Bug Tracking System]

Your message dated Sun, 07 Feb 2021 20:49:12 +
with message-id 
and subject line Bug#957342: fixed in hspell-gui 0.2.6-7
has caused the Debian Bug report #957342,
regarding hspell-gui: 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.)


-- 
957342: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957342
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:hspell-gui
Version: 0.2.6-6
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/hspell-gui_0.2.6-6_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

[...]
/usr/include/glib-2.0/glib/gtypes.h:551:8: note: declared here
  551 | struct _GTimeVal
  |^
gcc -DHAVE_CONFIG_H -I. -I.. -DPACKAGE_DATA_DIR=\""/usr/share"\" 
-DPACKAGE_LOCALE_DIR=\""/usr/share/locale"\" -pthread -I/usr/include/gtk-2.0 
-I/usr/lib/x86_64-linux-gnu/gtk-2.0/include -I/usr/include/pango-1.0 
-I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pixman-1 
-I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libmount -I/usr/include/blkid 
-I/usr/include/pango-1.0 -I/usr/include/harfbuzz -I/usr/include/pango-1.0 
-I/usr/include/fribidi -I/usr/include/glib-2.0 
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/uuid 
-I/usr/include/freetype2 -I/usr/include/libpng16-g -O2 -c -o callbacks.o 
callbacks.c
In file included from /usr/include/gtk-2.0/gtk/gtkobject.h:37,
 from /usr/include/gtk-2.0/gtk/gtkwidget.h:36,
 from /usr/include/gtk-2.0/gtk/gtkcontainer.h:35,
 from /usr/include/gtk-2.0/gtk/gtkbin.h:35,
 from /usr/include/gtk-2.0/gtk/gtkwindow.h:36,
 from /usr/include/gtk-2.0/gtk/gtkdialog.h:35,
 from /usr/include/gtk-2.0/gtk/gtkaboutdialog.h:32,
 from /usr/include/gtk-2.0/gtk/gtk.h:33,
 from callbacks.c:5:
/usr/include/gtk-2.0/gtk/gtktypeutils.h:236:1: warning: ‘GTypeDebugFlags’ is 
deprecated [-Wdeprecated-declarations]
  236 | voidgtk_type_init   (GTypeDebugFlagsdebug_flags);
  | ^~~~
In file included from /usr/include/glib-2.0/gobject/gobject.h:24,
 from /usr/include/glib-2.0/gobject/gbinding.h:29,
 from /usr/include/glib-2.0/glib-object.h:23,
 from /usr/include/glib-2.0/gio/gioenums.h:28,
 from /usr/include/glib-2.0/gio/giotypes.h:28,
 from /usr/include/glib-2.0/gio/gio.h:26,
 from /usr/include/gtk-2.0/gdk/gdkapplaunchcontext.h:30,
 from /usr/include/gtk-2.0/gdk/gdk.h:32,
 from /usr/include/gtk-2.0/gtk/gtk.h:32,
 from callbacks.c:5:
/usr/include/glib-2.0/gobject/gtype.h:679:1: note: declared here
  679 | {
  | ^
In file included from /usr/include/gtk-2.0/gtk/gtktoolitem.h:31,
 from /usr/include/gtk-2.0/gtk/gtktoolbutton.h:30,
 from /usr/include/gtk-2.0/gtk/gtkmenutoolbutton.h:30,
 from /usr/include/gtk-2.0/gtk/gtk.h:126,
 from callbacks.c:5:
/usr/include/gtk-2.0/gtk/gtktooltips.h:73:3: warning: ‘GTimeVal’ is deprecated: 
Use 'GDateTime' instead [-Wdeprecated-declarations]
   73 |   GTimeVal last_popdown;
  |   ^~~~
In file included from /usr/include/glib-2.0/glib/galloca.h:32,
 from /usr/include/glib-2.0/glib.h:30,
 from /usr/include/glib-2.0/gobject/gbinding.h:28,
 from 

Processed: Bug#982212 marked as pending in simka

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #982212 [src:simka] simka: autopkgtest needs same architecture list as simka
Added tag(s) pending.

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

Bug#982212: marked as pending in simka

[Shayan Doust]

Control: tag -1 pending

Hello,

Bug #982212 in simka 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/med-team/simka/-/commit/3f2bd5ec6aec77dd4e97d9281f8114927d4de765


Make autopkgtest have the same arch list as d/control
(Closes: #982212)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/982212

Bug#982253: netkit telnetd: ship with bullseye with open security problems?

[Salvatore Bonaccorso]

Hi,

[Not a conclusive answer]

On Sun, Feb 07, 2021 at 06:49:25PM +0100, Chris Hofstaedtler wrote:
> 2) possibly unpatched exploit here: https://www.exploit-db.com/exploits/48170

JFTR, this one was CVE-2020-10188 and in Debian was fixed in earlier
times.

Replacing telnetd package with an empy package and depending on
inetutils-telnetd: is it possible to basically interchangably replace
those two? If so this might be an option but I'm not sure if at this
stage of the preparations for bullseye it might be too late.

> 1) open bug #974428, causes telnetd to crash, remotely triggerable

The first issue, if there a verified patch might be good to fix in
time for bullseye.

Regards,
Salvatore

Processed: closing 982257

[Debian Bug Tracking System]

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

> close 982257 1.0.14-2
Bug #982257 [src:courier] courier: binary-all FTBFS
The source 'courier' and version '1.0.14-2' do not appear to match any binary 
packages
Marked as fixed in versions courier/1.0.14-2.
Bug #982257 [src:courier] courier: binary-all FTBFS
Marked Bug as done
> thanks
Stopping processing here.

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

Bug#982144: php-klogger: Useless in Bullseye

[Paul Gevers]

Hi James,

On 07-02-2021 18:23, James Valleroy wrote:
> It has no dependencies in Buster, so there is no reason for an end user to 
> install it.
>
> A PHP developer could use the package though. But I think they are more 
> likely to use composer to download/install what they need.

So, you're saying it was useless to ship in buster?

> I opened bugs like this for all the dependencies of shaarli, after discussion 
> in #980134.
> Do you agree with this approach in general?

You may have noticed (or may do so tomorrow ;)) that I already removed
all those packages. I refrained from this one because it's shipped with
buster.

Paul



OpenPGP_signature
Description: OpenPGP digital signature

Bug#979840: dns-root-data: autopkgtest regression in testing: failed to query server 127.0.0.1@53

[Chris Hofstaedtler]

Hello Paul,
Hello knot-resolver Maintainers,

* Paul Gevers  [210207 19:52]:
> With a not so recent change (beginning 2020) somewhere outside your
> package the autopkgtest of your package started to fail. I copied some
> of the output at the bottom of this report. Can you please investigate
> the situation and fix it?
[..]
> https://ci.debian.net/data/autopkgtest/testing/amd64/d/dns-root-data/9516338/log.gz
> 
> autopkgtest [17:42:10]: test baseline: [---
> ;; WARNING: response timeout for 127.0.0.1@53(UDP)
> ;; WARNING: response timeout for 127.0.0.1@53(UDP)
> ;; WARNING: response timeout for 127.0.0.1@53(UDP)
> ;; ERROR: failed to query server 127.0.0.1@53(UDP)
> autopkgtest [17:42:25]: test baseline: ---]

It would appear knot-resolver made changes and now kresd no longer
starts when the package gets installed.
I don't know if this is an intentional change at all?

Chris

Bug#981600: nghttp2: util_localtime_date test fails in arch-only build

[Chris Hofstaedtler]

Hi Helmut,

* Helmut Grohne  [210207 19:50]:
> An arch-only build (but not a full build) of nghttp2 seems to reliably
> fail at test util_localtime_date:
[..]
> Since reproducible only performs full builds, it doesn't see this issue.
> Likewise crossqa skips tests and does not see it either. I don't
> understand the cause here and just report it. I hope it reproduces
> reliably elsewhere as well.

I'm just passing by, but a local rebuild with `sbuild -d unstable
-j8 --no-arch-all` did not show this problem (on amd64). There has
to be more to it.

Chris

Bug#980085: marked as done (open-iscsi: initiator does not connect)

[Debian Bug Tracking System]

Your message dated Sun, 07 Feb 2021 19:49:07 +
with message-id 
and subject line Bug#980085: fixed in open-iscsi 2.1.3-2
has caused the Debian Bug report #980085,
regarding open-iscsi: initiator does not connect
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.)


-- 
980085: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=980085
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: open-iscsi
Version: 2.1.3-1
Severity: important

On my system open-iscsi and libopeniscsiusr where upgraded to 2.1.3-1.

With a kernel installed after this upgrade my system cannot boot from an
iSCSI LUN:

iscsistart: version 2.1.3
iscsistart: Logging into iqn.2000-01.de.xypron:disk1 192.168.0.1:3260,1
iscsistart: initiator reported error (32 - target likely not connected)

I downgraded to open-iscsi and libopeniscsiusr to version 2.1.2-2 and
reinstalled the kernel package.

Now the system boots with:

iscsistart: Logging into iqn.2000-01.de.xypron:disk1 192.168.0.1:3260,1
iscsistart: initiator reported error (15 - session exists)
iscsistart: version 2.1.2
iscsistart: Logging into iqn.2000-01.de.xypron:disk1 192.168.0.1:3260,1
iscsistart: Connection1:0 to [target: iqn.2000-01.de.xypron:disk1,
portal: 192.168.0.1,3260] through [iface: default] is operational now

-- System Information:
Debian Release: bullseye/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: arm64 (aarch64)

Kernel: Linux 5.10.7-fwts-arm64+ (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 /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages open-iscsi depends on:
ii  debconf [debconf-2.0]  1.5.74
ii  libc6  2.31-9
ii  libisns0   0.100-3
ii  libkmod2   28-1
ii  libmount1  2.36.1-4
ii  libopeniscsiusr2.1.3-1
ii  libssl1.1  1.1.1i-1
ii  libsystemd0247.2-4
ii  udev   247.2-4
--- End Message ---
--- Begin Message ---
Source: open-iscsi
Source-Version: 2.1.3-2
Done: Chris Hofstaedtler 

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 07 Feb 2021 19:23:13 +
Source: open-iscsi
Architecture: source
Version: 2.1.3-2
Distribution: unstable
Urgency: medium
Maintainer: Debian iSCSI Maintainers 
Changed-By: Chris Hofstaedtler 
Closes: 898758 980085
Changes:
 open-iscsi (2.1.3-2) unstable; urgency=medium
 .
   * [c3b7109] Fix FTCBFS:
 Let dh_auto_configure pass --host to iscsiuio/configure.
 Thanks to Helmut Grohne  (Closes: #898758)
   * [efb5512] Add patches from upstream:
 Fix memory leak in iscsiadm, Fix iscsiadm segfault when exiting, and
 Fix iscsistart login issue when target is delayed. The last one should
 fix #980085. (Closes: #980085)
Checksums-Sha1:
 5c9ad959cec737485fee8dde8d4175e71a162b0e 2578 open-iscsi_2.1.3-2.dsc
 e9d564fce48480be039d9c1c3f433d8fb56aa943 53548 open-iscsi_2.1.3-2.debian.tar.xz
 78a1f19ab0a588a4feac09f0cb1d0cbf95ee61a4 6066 
open-iscsi_2.1.3-2_source.buildinfo
Checksums-Sha256:
 3dbab1078374d10f6647c2fc2906064f16dca45035ed6021ec1df337dc639f41 2578 
open-iscsi_2.1.3-2.dsc
 094858a4ce49aae54f683613745f365b271f066bb1f41145579696424cebc77c 53548 
open-iscsi_2.1.3-2.debian.tar.xz
 a064f627ba81aa3438f2c4dc4a83d073d5f94f79a2a3062f5ff7991e789aeb20 6066 
open-iscsi_2.1.3-2_source.buildinfo
Files:
 c4d63b4250b7384b2ab63de767f42322 2578 net optional open-iscsi_2.1.3-2.dsc
 4c8e9ff6c84457a67574faa3f8d9cedb 53548 net optional 
open-iscsi_2.1.3-2.debian.tar.xz
 74135bce62e58f44331b857a9022015f 6066 net optional 
open-iscsi_2.1.3-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEfRrP+tnggGycTNOSXBPW25MFLgMFAmAgQMoACgkQXBPW25MF

Bug#980085: open-iscsi: initiator does not connect

[Chris Hofstaedtler]

Hello Heinrich,

I'm going to upload upstream's fix. Maybe you can give it a try.

Best,
Chris

Processed: your mail

[Debian Bug Tracking System]

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

> notfixed 980482 88.0.4324.96-0.1
Bug #980482 {Done: Michael Gilbert } [chromium] chromium: 
upgrade to 87 breaks browser window rendering
Bug #979017 {Done: Michael Gilbert } [chromium] chromium 
87 with hw accel, opening a second window freezes the UI
No longer marked as fixed in versions chromium/88.0.4324.96-0.1.
No longer marked as fixed in versions chromium/88.0.4324.96-0.1.
> thanks
Stopping processing here.

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

Bug#979017: marked as done (chromium 87 with hw accel, opening a second window freezes the UI)

[Debian Bug Tracking System]

Your message dated Sun, 7 Feb 2021 14:28:12 -0500
with message-id 

and subject line Re: Bug#980482: chromium: upgrade to 87 breaks browser window 
rendering
has caused the Debian Bug report #980482,
regarding chromium 87 with hw accel, opening a second window freezes the UI
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.)


-- 
980482: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=980482
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: chromium
Version: 87.0.4280.88-0.4~deb10u1
Severity: normal

Dear Maintainer,

First of all: thank you VERY much for working on chromium in Debian!

With the new version in stable-security, when I open a second window by 
pressing Ctrl-N or Ctrl-Shift-N, all browser windows (even the first) 
stop redrawing and appear frozen.

The browser actually still responds to input, the cursor changes if I 
mouseover different things, the right-click menu appears and works fine, 
only the browser windows never redraw. I can force it to redraw by 
resizing the window, but it stays frozen the rest of the time.

If I disable hardware acceleration, the problem goes away and everything 
seems to work normally.

I am not running any desktop environment, just "awesome" as window 
manager. I'm also not running any X compositing manager such as 
xcompmgr.

GPU info from chrome://gpu: VENDOR=0x8086 [Google Inc.], DEVICE=0x1916 [ANGLE 
(Intel Open Source Technology Center, Mesa DRI Intel(R) HD Graphics 520 
(Skylake GT2), OpenGL 4.5 core)] *ACTIVE*

Please, let me know if I can provide any further information, or if I 
should send this upstream.

thank you,
Ryan



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

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

Versions of packages chromium depends on:
ii  chromium-common  87.0.4280.88-0.4~deb10u1
ii  libasound2   1.1.8-1
ii  libatk-bridge2.0-0   2.30.0-5
ii  libatk1.0-0  2.30.0-2
ii  libatomic1   8.3.0-6
ii  libatspi2.0-02.30.0-7
ii  libavcodec58 7:4.1.6-1~deb10u1
ii  libavformat587:4.1.6-1~deb10u1
ii  libavutil56  7:4.1.6-1~deb10u1
ii  libc62.28-10
ii  libcairo21.16.0-4
ii  libcups2 2.2.10-6+deb10u4
ii  libdbus-1-3  1.12.20-0+deb10u1
ii  libdrm2  2.4.97-1
ii  libevent-2.1-6   2.1.8-stable-4
ii  libexpat12.2.6-2+deb10u1
ii  libflac8 1.3.2-3
ii  libfontconfig1   2.13.1-2
ii  libfreetype6 2.9.1-3+deb10u2
ii  libgbm1  18.3.6-2+deb10u1
ii  libgcc1  1:8.3.0-6
ii  libgdk-pixbuf2.0-0   2.38.1+dfsg-1
ii  libglib2.0-0 2.58.3-2+deb10u2
ii  libgtk-3-0   3.24.5-1
ii  libharfbuzz0b2.3.1-1
ii  libicu63 63.1-6+deb10u1
ii  libjpeg62-turbo  1:1.5.2-2+deb10u1
ii  libjsoncpp1  1.7.4-3
ii  liblcms2-2   2.9-3
ii  libminizip1  1.1-8+b1
ii  libnspr4 2:4.20-1
ii  libnss3  2:3.42.1-1+deb10u3
ii  libopenjp2-7 2.3.0-2+deb10u1
ii  libopus0 1.3-1
ii  libpango-1.0-0   1.42.4-8~deb10u1
ii  libpangocairo-1.0-0  1.42.4-8~deb10u1
ii  libpng16-16  1.6.36-6
ii  libpulse012.2-4+deb10u1
ii  libre2-5 20190101+dfsg-2
ii  libsnappy1v5 1.1.7-1
ii  libstdc++6   8.3.0-6
ii  libwebp6 0.6.1-2
ii  libwebpdemux20.6.1-2
ii  libwebpmux3  0.6.1-2
ii  libx11-6 2:1.6.7-1+deb10u1
ii  libx11-xcb1  2:1.6.7-1+deb10u1
ii  libxcb1  1.13.1-2
ii  libxcomposite1   1:0.4.4-2
ii  libxdamage1  1:1.1.4-3+b3
ii  libxext6 2:1.3.3-1+b2
ii  libxfixes3   1:5.0.3-1
ii  libxml2  2.9.4+dfsg1-7+deb10u1
ii  libxrandr2   2:1.5.1-1
ii  libxslt1.1   1.1.32-2.2~deb10u1
ii  zlib1g   1:1.2.11.dfsg-1

Versions of packages chromium recommends:
ii  chromium-sandbox  87.0.4280.88-0.4~deb10u1

Versions of packages chromium suggests:
pn  chromium-driver  
pn  chromium-l10n
pn  chromium-shell   

Versions of packages chromium-common depends on:
ii  libc6   2.28-10
ii  libstdc++6  8.3.0-6
ii  libx11-62:1.6.7-1+deb10u1
ii  libxext62:1.3.3-1+b2
ii  x11-utils   7.7+4
ii  xdg-utils   

Bug#980482: marked as done (chromium: upgrade to 87 breaks browser window rendering)

[Debian Bug Tracking System]

Your message dated Sun, 7 Feb 2021 14:28:12 -0500
with message-id 

and subject line Re: Bug#980482: chromium: upgrade to 87 breaks browser window 
rendering
has caused the Debian Bug report #980482,
regarding chromium: upgrade to 87 breaks browser window rendering
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.)


-- 
980482: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=980482
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: chromium
Version: 87.0.4280.141-0.1~deb10u1
Severity: serious
Tags: buster

Dear Maintainer,

I upgraded chromium on Debian stable (buster) from
83.0.4103.116-1~deb10u3 to 87.0.4280.141-0.1~deb10u1.

After this upgrade chromium becomes completely unusable to me, which
means, that the chromium window isn't rendered as expected.
When I open a website or click on a link the web page doesn't show,
also the tab title isn't updated, only the window title changes to the
new page.
Sometimes (if page is already in cache) it seems that the web page is
shown, but usually not completely updated.
But there is a trick to get the web page rendered: Switch to a
different screen and back here and after this the browser window is
rendered as expected.

This at least works sometimes after freshly starting chromium and
keeping it in foreground.  If I once iconize and after this un-iconize
the chromium windows, only the window border is alive, while
everything else looks like I had sent a STOP signal to the browser
process (for example by pressing Ctrl-Z in the shell without entering
fg or bg afterwards), but it was not suspended, as you can see in the
process list.

I observe this strange behavior after the upgrade of chromium on two
different machines (both amd64 buster, but with different home
directories etc.)

I usually use fvwm as window manager, but observe the same problem, if
I start KDE plasma on one of the machines for testing purpose.  The
problem persists, but I'm not sure how to switch screens there to
trigger the "workaround".

A downgrade to 83.0.4103.116-1~deb10u3 solves the issue, upgrading to
87.0.4280.141-0.1~deb10u1 triggers it again.

Using google-chrome-stable 87.0.4280.141-1 works without problems.

Trying to remove ~/.config/chromium or ~/.cache/chromium doesn't solve
the issue.

No entries in dmesg output, while I observe the problems.

No idea what's going wrong here.  It's very astonishing, that I didn't
find tons of bug reports about this.  Am I the only one affected by
this?  But what makes my systems different?

Greetings
Roland


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

Kernel: Linux 4.19.0-13-amd64 (SMP w/4 CPU cores)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=de_DE.utf-8, LC_CTYPE=de_DE.utf-8 (charmap=UTF-8), 
LANGUAGE=de_DE:de:en_GB:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages chromium depends on:
ii  chromium-common  87.0.4280.141-0.1~deb10u1
ii  libasound2   1.1.8-1
ii  libatk-bridge2.0-0   2.30.0-5
ii  libatk1.0-0  2.30.0-2
ii  libatomic1   8.3.0-6
ii  libatspi2.0-02.30.0-7
ii  libavcodec58 7:4.1.6-1~deb10u1
ii  libavformat587:4.1.6-1~deb10u1
ii  libavutil56  7:4.1.6-1~deb10u1
ii  libc62.28-10
ii  libcairo21.16.0-4
ii  libcups2 2.2.10-6+deb10u4
ii  libdbus-1-3  1.12.20-0+deb10u1
ii  libdrm2  2.4.97-1
ii  libevent-2.1-6   2.1.8-stable-4
ii  libexpat12.2.6-2+deb10u1
ii  libflac8 1.3.2-3
ii  libfontconfig1   2.13.1-2
ii  libfreetype6 2.9.1-3+deb10u2
ii  libgbm1  18.3.6-2+deb10u1
ii  libgcc1  1:8.3.0-6
ii  libgdk-pixbuf2.0-0   2.38.1+dfsg-1
ii  libglib2.0-0 2.58.3-2+deb10u2
ii  libgtk-3-0   3.24.5-1
ii  libharfbuzz0b2.3.1-1
ii  libicu63 63.1-6+deb10u1
ii  libjpeg62-turbo  1:1.5.2-2+deb10u1
ii  libjsoncpp1  1.7.4-3
ii  liblcms2-2   2.9-3
ii  libminizip1  1.1-8+b1
ii  libnspr4 2:4.20-1
ii  libnss3  2:3.42.1-1+deb10u3
ii  libopenjp2-7 2.3.0-2+deb10u1
ii  libopus0 1.3-1
ii  libpango-1.0-0   1.42.4-8~deb10u1
ii  libpangocairo-1.0-0  1.42.4-8~deb10u1
ii  libpng16-16  1.6.36-6
ii  libpulse012.2-4+deb10u1
ii  libre2-5 20190101+dfsg-2
ii  libsnappy1v5 

Bug#957599: marked as done (netpbm-free: ftbfs with GCC-10)

[Debian Bug Tracking System]

Your message dated Sun, 07 Feb 2021 19:23:08 +
with message-id 
and subject line Bug#957599: fixed in netpbm-free 2:10.0-15.4
has caused the Debian Bug report #957599,
regarding netpbm-free: 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.)


-- 
957599: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957599
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:netpbm-free
Version: 2:10.0-15.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/netpbm-free_10.0-15.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

[...]
  | ^~~
/<>/pnm/fiasco/lib/dither.c: In function ‘display_24_bit_rgb’:
/<>/pnm/fiasco/lib/dither.c:1184:41: warning: variable ‘b_table’ 
set but not used [-Wunused-but-set-variable]
 1184 |   unsigned int *r_table, *g_table, *b_table;
  | ^~~
/<>/pnm/fiasco/lib/dither.c:1184:31: warning: variable ‘g_table’ 
set but not used [-Wunused-but-set-variable]
 1184 |   unsigned int *r_table, *g_table, *b_table;
  |   ^~~
/<>/pnm/fiasco/lib/dither.c:1184:21: warning: variable ‘r_table’ 
set but not used [-Wunused-but-set-variable]
 1184 |   unsigned int *r_table, *g_table, *b_table;
  | ^~~
/<>/pnm/fiasco/lib/dither.c:1515:21: warning: variable ‘y_table’ 
set but not used [-Wunused-but-set-variable]
 1515 |   unsigned int *y_table;
  | ^~~
At top level:
/<>/pnm/fiasco/lib/dither.c:347:1: warning: ‘free_bits_at_top’ 
defined but not used [-Wunused-function]
  347 | free_bits_at_top (unsigned long a)
  | ^~~~
gcc -c -I../../../shhopt -I.. -I ../../../include/ `dpkg-buildflags --get 
CFLAGS` -pedantic -O3 -Wall -Wno-uninitialized `dpkg-buildflags --get CPPFLAGS` 
 -o error.o /<>/pnm/fiasco/lib/error.c
/<>/pnm/fiasco/lib/error.c: In function ‘set_error’:
/<>/pnm/fiasco/lib/error.c:98:7: warning: variable ‘dummy’ set but 
not used [-Wunused-but-set-variable]
   98 |   int dummy;
  |   ^
/<>/pnm/fiasco/lib/error.c:104:7: warning: variable ‘dummy’ set 
but not used [-Wunused-but-set-variable]
  104 |   int dummy;
  |   ^
/<>/pnm/fiasco/lib/error.c: In function ‘error’:
/<>/pnm/fiasco/lib/error.c:152:7: warning: variable ‘dummy’ set 
but not used [-Wunused-but-set-variable]
  152 |   int dummy;
  |   ^
/<>/pnm/fiasco/lib/error.c:158:7: warning: variable ‘dummy’ set 
but not used [-Wunused-but-set-variable]
  158 |   int dummy;
  |   ^
gcc -c -I../../../shhopt -I.. -I ../../../include/ `dpkg-buildflags --get 
CFLAGS` -pedantic -O3 -Wall -Wno-uninitialized `dpkg-buildflags --get CPPFLAGS` 
 -o image.o /<>/pnm/fiasco/lib/image.c
In file included from /usr/include/string.h:495,
 from /<>/pnm/fiasco/lib/image.c:19:
In function ‘strcpy’,
inlined from ‘alloc_image’ at /<>/pnm/fiasco/lib/image.c:203:4:
/usr/include/x86_64-linux-gnu/bits/string_fortified.h:90:10: warning: 
‘__builtin___strcpy_chk’ writing 8 bytes into a region of size 7 
[-Wstringop-overflow=]
   90 |   return __builtin___strcpy_chk (__dest, __src, __bos (__dest));
  |  ^~
In file included from /<>/pnm/fiasco/lib/image.c:27:
/<>/pnm/fiasco/lib/image.c: In function ‘alloc_image’:
/<>/pnm/fiasco/lib/image.h:31:14: note: at offset 0 to object ‘id’ 
with size 7 declared here
   31 

Processed: your mail

[Debian Bug Tracking System]

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

> forcemerge 980482 979017
Bug #980482 [chromium] chromium: upgrade to 87 breaks browser window rendering
Bug #980482 [chromium] chromium: upgrade to 87 breaks browser window rendering
Marked as found in versions chromium/87.0.4280.88-0.4~deb10u1.
Added tag(s) fixed-upstream and upstream.
Bug #979017 [chromium] chromium 87 with hw accel, opening a second window 
freezes the UI
Severity set to 'serious' from 'normal'
Marked as fixed in versions chromium/88.0.4324.96-0.1.
Marked as found in versions chromium/87.0.4280.141-0.1~deb10u1.
Added tag(s) buster.
Merged 979017 980482
> thanks
Stopping processing here.

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

Bug#982257: courier: binary-all FTBFS

[Adrian Bunk]

Source: courier
Version: 1.0.14-1
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/fetch.php?pkg=courier=all=1.0.14-1=1609168389=0

...
dh_install
dh_missing --fail-missing
dh_missing: warning: usr/bin/deliverquota exists in debian/tmp but is not 
installed to anywhere 
dh_missing: warning: usr/bin/lockmail exists in debian/tmp but is not installed 
to anywhere 
dh_missing: warning: usr/bin/maildirmake exists in debian/tmp but is not 
installed to anywhere 
dh_missing: warning: usr/bin/makedat exists in debian/tmp but is not installed 
to anywhere (related file: "debian/tmp/usr/lib/courier/makedat")
dh_missing: warning: usr/bin/preline exists in debian/tmp but is not installed 
to anywhere 
dh_missing: warning: usr/lib/courier/mkesmtpdcert exists in debian/tmp but is 
not installed to anywhere (related file: "debian/tmp/usr/sbin/mkesmtpdcert")
dh_missing: warning: usr/sbin/showconfig exists in debian/tmp but is not 
installed to anywhere 
dh_missing: warning: usr/share/man/man1/lockmail.1 exists in debian/tmp but is 
not installed to anywhere 
dh_missing: warning: usr/share/man/man1/maildirmake.1 exists in debian/tmp but 
is not installed to anywhere 
dh_missing: warning: usr/share/man/man1/makedat.1 exists in debian/tmp but is 
not installed to anywhere 
dh_missing: warning: usr/share/man/man1/preline.1 exists in debian/tmp but is 
not installed to anywhere 
dh_missing: warning: usr/share/man/man5/maildir.5 exists in debian/tmp but is 
not installed to anywhere 
dh_missing: warning: usr/share/man/man7/maildirquota.7 exists in debian/tmp but 
is not installed to anywhere 
dh_missing: warning: usr/share/man/man8/deliverquota.8 exists in debian/tmp but 
is not installed to anywhere 
dh_missing: error: missing files, aborting

While detecting missing files, dh_missing noted some files with a 
similar name to those
that were missing.  This error /might/ be resolved by replacing 
references to the
missing files with the similarly named ones that dh_missing found - 
assuming the content
is identical.

As an example, you might want to replace:
 * debian/tmp/usr/lib/courier/makedat
with:
 * usr/bin/makedat
in a file in debian/ or as argument to one of the dh_* tools called 
from debian/rules.
(Note it is possible the paths are not used verbatim but instead 
directories 
containing or globs matching them are used instead)

Alternatively, add the missing file to debian/not-installed if it 
cannot and should not
be used.

The following debhelper tools have reported what they installed (with 
files per package)
 * dh_install: courier-base (33), courier-doc (84), courier-faxmail 
(17), courier-imap (15), courier-ldap (8), courier-mlm (8), courier-mta (112), 
courier-pcp (2), courier-pop (18), courier-webadmin (22), sqwebmail (65)
If the missing files are installed by another tool, please file a bug 
against it.
When filing the report, if the tool is not part of debhelper itself, 
please reference the
"Logging helpers and dh_missing" section from the "PROGRAMMING" guide 
for debhelper (10.6.3+).
  (in the debhelper package: /usr/share/doc/debhelper/PROGRAMMING.gz)
Be sure to test with dpkg-buildpackage -A/-B as the results may vary 
when only a subset is built
If the omission is intentional or no other helper can take care of this 
consider adding the
paths to debian/not-installed.
make[1]: *** [debian/rules:155: override_dh_install] Error 25

Bug#982256: spyder-line-profiler FTBFS with Spyder 4.2.1

[Adrian Bunk]

Source: spyder-line-profiler
Version: 0.1.1-1.1
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/fetch.php?pkg=spyder-line-profiler=all=0.1.1-1.1=1612695817=0

...
 ERRORS 
_ ERROR collecting 
.pybuild/cpython3_3.9_spyder-line-profiler/build/spyder_line_profiler/widgets/tests/test_lineprofiler.py
 _
ImportError while importing test module 
'/<>/.pybuild/cpython3_3.9_spyder-line-profiler/build/spyder_line_profiler/widgets/tests/test_lineprofiler.py'.
Hint: make sure your test modules/packages have valid Python names.
Traceback:
/usr/lib/python3.9/importlib/__init__.py:127: in import_module
return _bootstrap._gcd_import(name[level:], package, level)
spyder_line_profiler/__init__.py:12: in 
from .lineprofiler import LineProfiler
spyder_line_profiler/lineprofiler.py:18: in 
from spyder.plugins import SpyderPluginWidget, runconfig
E   ImportError: cannot import name 'SpyderPluginWidget' from 'spyder.plugins' 
(/usr/lib/python3/dist-packages/spyder/plugins/__init__.py)
--- Captured stdout 
Update LANGUAGE_CODES (inside config/base.py) if a new translation has been 
added to Spyder
--- Captured stderr 
QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-buildd'
=== short test summary info 
ERROR spyder_line_profiler/widgets/tests/test_lineprofiler.py
 Interrupted: 1 error during collection 
=== 1 error in 0.65s ===
E: pybuild pybuild:353: test: plugin distutils failed with: exit code=2: cd 
/<>/.pybuild/cpython3_3.9_spyder-line-profiler/build; python3.9 -m 
pytest 
dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.9 
returned exit code 13
make: *** [debian/rules:12: build-indep] Error 25



Compatibility withg Spyder 4 seems to be in the latest upstream version.

Bug#978389: marked as done (easyh10: FTBFS: configure.in:184: error: possibly undefined macro: AM_LANGINFO_CODESET (caused by gettext 0.19 -> 0.21?))

[Debian Bug Tracking System]

Your message dated Sun, 07 Feb 2021 19:03:17 +
with message-id 
and subject line Bug#978389: fixed in easyh10 1.5-4.1
has caused the Debian Bug report #978389,
regarding easyh10: FTBFS: configure.in:184: error: possibly undefined macro: 
AM_LANGINFO_CODESET (caused by gettext 0.19 -> 0.21?)
to be marked as done.

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

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


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

Hi,

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

Relevant part (hopefully):
>  debian/rules build
> dh build --with autoreconf
>dh_update_autotools_config
>dh_autoreconf
> aclocal: warning: autoconf input should be named 'configure.ac', not 
> 'configure.in'
> configure.in:184: warning: macro 'AM_LANGINFO_CODESET' not found in library
> libtoolize: putting auxiliary files in '.'.
> libtoolize: copying file './ltmain.sh'
> libtoolize: Consider adding 'AC_CONFIG_MACRO_DIRS([m4])' to configure.in,
> libtoolize: and rerunning libtoolize and aclocal.
> libtoolize: Consider adding '-I m4' to ACLOCAL_AMFLAGS in Makefile.am.
> aclocal: warning: autoconf input should be named 'configure.ac', not 
> 'configure.in'
> configure.in:184: warning: macro 'AM_LANGINFO_CODESET' not found in library
> configure.in:184: error: possibly undefined macro: AM_LANGINFO_CODESET
>   If this token and others are legitimate, please use m4_pattern_allow.
>   See the Autoconf documentation.
> autoreconf: /usr/bin/autoconf failed with exit status: 1
> dh_autoreconf: error: autoreconf -f -i returned exit code 1
> make: *** [debian/rules:8: build] Error 25

The full build log is available from:
   http://qa-logs.debian.net/2020/12/26/easyh10_1.5-4_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: easyh10
Source-Version: 1.5-4.1
Done: Adrian Bunk 

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

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

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

Debian distribution maintenance software
pp.
Adrian Bunk  (supplier of updated easyh10 package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 25 Jan 2021 01:08:02 +0200
Source: easyh10
Architecture: source
Version: 1.5-4.1
Distribution: unstable
Urgency: medium
Maintainer: Allan Dixon Jr. 
Changed-By: Adrian Bunk 
Closes: 978389
Changes:
 easyh10 (1.5-4.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Remove usage of obsolete AM_LANGINFO_CODESET. (Closes: #978389)
Checksums-Sha1:
 c49a5883e34c7dfbd4f548767e00919080a74076 1718 easyh10_1.5-4.1.dsc
 54c8cc8107eefc559662f4673b1d3b5edf80356b 6756 easyh10_1.5-4.1.debian.tar.xz
Checksums-Sha256:
 1f95c5b6fa616a477bed62f70277b182bcb3f0897346b6b327a5e5247b27f607 1718 
easyh10_1.5-4.1.dsc
 bc316bb9d5dd0fc9bc852bf1f6dc00e7dff57c066069aa8b1420af9ddce3deb2 6756 
easyh10_1.5-4.1.debian.tar.xz
Files:
 ba96ae8fd03d9484d653b28dda0fbc29 1718 sound optional easyh10_1.5-4.1.dsc
 80da184711d2b18e249acf0524c092a8 6756 sound optional 
easyh10_1.5-4.1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAmAN/rMACgkQiNJCh6LY
mLGBCxAAjWeZwgGzh9dMtpeR0olkq5Y55ZIF//CfPZwXuEFxJHvBnucE4yNkvtk3
S2TrtH0/fKx6eHdf7TWZYHguWN/YARjbXZAwx3/mII/uh7fSb4w6Q6+Ea4oFd5Jx

Bug#978170: marked as done (gdb-avr: FTBFS: tar (child): /usr/src/gdb.tar.bz2: Cannot open: No such file or directory)

[Debian Bug Tracking System]

Your message dated Sun, 07 Feb 2021 19:03:21 +
with message-id 
and subject line Bug#978170: fixed in gdb-avr 7.7-4.1
has caused the Debian Bug report #978170,
regarding gdb-avr: FTBFS: tar (child): /usr/src/gdb.tar.bz2: Cannot open: No 
such file or directory
to be marked as done.

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

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


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

Hi,

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

Relevant part (hopefully):
>  debian/rules build
> tar xjf /usr/src/gdb.tar.bz2
> tar (child): /usr/src/gdb.tar.bz2: Cannot open: No such file or directory
> tar (child): Error is not recoverable: exiting now
> tar: Child returned status 2
> tar: Error is not recoverable: exiting now
> make: *** [debian/rules:32: unpack-stamp] Error 2

The full build log is available from:
   http://qa-logs.debian.net/2020/12/26/gdb-avr_7.7-4_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: gdb-avr
Source-Version: 7.7-4.1
Done: Adrian Bunk 

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

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

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

Debian distribution maintenance software
pp.
Adrian Bunk  (supplier of updated gdb-avr package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 24 Jan 2021 23:30:28 +0200
Source: gdb-avr
Architecture: source
Version: 7.7-4.1
Distribution: unstable
Urgency: medium
Maintainer: Hakan Ardo 
Changed-By: Adrian Bunk 
Closes: 978170
Changes:
 gdb-avr (7.7-4.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Adjust to gdb-source changes. (Closes: #978170)
Checksums-Sha1:
 1f75d05e655f6eb717a73ae3e71519d70484cfd9 1631 gdb-avr_7.7-4.1.dsc
 534c94eb2959b7418ff812c123fbd448c3757919 2446260 gdb-avr_7.7-4.1.tar.gz
Checksums-Sha256:
 5ac95a924391211df3deb3621b05fbcc060ecbc45ce072d10facd8f0a10bf0b0 1631 
gdb-avr_7.7-4.1.dsc
 01513a34d7b04bd072c9b942d8bef9055bed10a4dbe6b6b3d8eb5cf257a3fa4e 2446260 
gdb-avr_7.7-4.1.tar.gz
Files:
 c53ea3142ecdd23d8deed3c736f65bdc 1631 devel extra gdb-avr_7.7-4.1.dsc
 5b671249ce820622006af70463f15e25 2446260 devel extra gdb-avr_7.7-4.1.tar.gz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAmAN6eEACgkQiNJCh6LY
mLGqCQ//WzrgGpM6Inn/AkL/Li7Soe+umIr0rWpLgO4V9ijDjRh5f3XOWZS6WiLW
9wB4j3x3vrMtQby9NkzHYllhQLLzZIV8mVO2Y7uxQtakZkP67/ncW5moVT8SEX9N
9JWifZ6dp4t2H1PoRD6rVxSEwtFpjmKsjAdOs44tnNaCsEced/7iaAKZVMZJ4nsG
vlFVpmz+/H1ylrB5lSNbhzFS5SDVvma9N87LmoHQ+j7Xywm5NDdw6YIShCA93kVv
IXTMZiCfVVQjNBswA51CnDssCSBIMFbeTlKkiF+nPky/OI4oDRGDdy1eCrDtXVV4
K4qPUacW4RA9IrIvdtQ5c3fGePGxd2JyfQIDnWYEvXH6fBPFmA+DiA5L+1VB/Hq/
r+E8biO/6C1KLsPjrg5kSQG/Xm0l5eYTAGlcIkpGEUSyfjSWhycLRR31DBSS09x+
GkIStOD1uWOAwmuORuR5FbmEXUD+yd6v1b+G/HOJ3X0frNf4BzlzSIq/clIHekUL
jBhPu0xHjuSnvhhdRGKiVIUZL7xaXPomowXfkXX8+qDQ1AUmDdlVpQ5fTVtDgTb3
v6ycOo7umiGzhyo8VE7aENCF2V9+wAOp0fxb+YTIkSl800ipYFc4leI0z7JCi7tx
DqB/lXx04Iw4Yjk3DuMQZcn6UqL2/6eclJ93tg0BeNDIrM30PIM=
=u2Ak
-END PGP SIGNATURE End Message ---

Bug#957599: netpbm-free: ftbfs with GCC-10

[Chris Hofstaedtler]

Hi Logan,

* Logan Rosen  [210207 18:53]:
> In Ubuntu, the attached patch was applied to achieve the following:
> 
>   * d/p/gcc-10.patch: Fix FTBFS with GCC 10.

Thanks for the patch. It appears _our_ GCC 10 also needs -fcommon in
CFLAGS. Not sure why it works for you without that.

Chris

Bug#960153:

[Chris Hofstaedtler]

* Robert Nelson  [210207 18:23]:
> I fixed this locally in our BeagleBoard.org Debian Repo with this quick patch:

> -java -Xmx64m -jar $JAR -storepass "$storepass"
> +java -Xmx64m -XX:-AssumeMP -jar $JAR -storepass "$storepass"

If this helps, someone please explain why this is not a bug in the
used JRE/JDK?
I fail to see how this is a bug in ca-certificates-java.

Chris

Processed: tagging 981330

[Debian Bug Tracking System]

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

> tags 981330 + patch
Bug #981330 [coturn] coturn: wrong logic for the dpkg-statoverride handling in 
coturn.postrm
Added tag(s) patch.
> thanks
Stopping processing here.

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

Bug#981330: coturn: wrong logic for the dpkg-statoverride handling in coturn.postrm

[Michael Prokop]

* Salvatore Bonaccorso [Sun Feb 07, 2021 at 04:47:40PM +0100]:
> On Fri, Jan 29, 2021 at 01:52:15PM +0100, Michael Prokop wrote:

> > the coturn.postrm uses a wrong logic for the dpkg-statoverride handling,
> > causing to properly handle package (re)installation/removal, quoting from
> > a piuparts run:

> > | Fetched 36.8 MB in 0s (85.1 MB/s)
> > | dpkg: unrecoverable fatal error, aborting:
> > |  unknown system group 'turnserver' in statoverride file; the system group 
> > got removed
> > | before the override, which is most probably a packaging bug, to recover 
> > you
> > | can remove the override manually with dpkg-statoverride
> > | E: Sub-process /usr/bin/dpkg returned an error code (2)

> > I'll provide a PR as soon as I've a bug number from Debian's BTS.

> > FTR: I tend to call this a RC bug, but leaving this up to the
> > maintainer to decide (though it would be great if the package gets
> > fixed for bullseye).

> Not the maintainer here, but I think from policy point of view that
> indeed would be RC. I'm raising the severity with this message.

> Did you looked alreayd into a fix?

Yes, I prepared a PR already:

  https://github.com/coturn/coturn/pull/710

regards
-mika-


signature.asc
Description: Digital signature

Processed: Re: Bug#979432: ruby-rack FTBFS on IPV6-only buildds

[Debian Bug Tracking System]

Processing control commands:

> found -1 2.1.4-1
Bug #979432 [src:ruby-rack] ruby-rack FTBFS on IPV6-only buildds
The source 'ruby-rack' and version '2.1.4-1' do not appear to match any binary 
packages
Marked as found in versions ruby-rack/2.1.4-1.
> tags -1 - unreproducible
Bug #979432 [src:ruby-rack] ruby-rack FTBFS on IPV6-only buildds
Removed tag(s) unreproducible.

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

Bug#979432: ruby-rack FTBFS on IPV6-only buildds

[Chris Hofstaedtler]

Control: found -1 2.1.4-1
Control: tags -1 - unreproducible

* Chris Hofstaedtler  [210207 18:19]:
> Thanks. However that info appears outdated, as on a current Debian
> unstable, I always get a `lo` interface with 127.0.0.1 and ::1
> bound. The tests want 127.0.0.1, so that works.
> 
> Without more info on how the buildd setup looks like, I cannot
> reproduce this. Or maybe the failure has gone anyway?

So, if I actually do this:
   ip a del 127.0.0.1/8 dev lo

Then the tests indeed crash.

But now that modern kernels apparently always hand one a working
"127.0.0.1", do we really want to bother with this?

I guess one can change all the tests to use ::1 instead of
127.0.0.1, but that will just introduce other failure modes.

Chris

Processed: Re: Bug#979432: ruby-rack FTBFS on IPV6-only buildds

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + unreproducible moreinfo
Bug #979432 [src:ruby-rack] ruby-rack FTBFS on IPV6-only buildds
Added tag(s) moreinfo and unreproducible.

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

Bug#979432: ruby-rack FTBFS on IPV6-only buildds

[Chris Hofstaedtler]

Control: tags -1 + unreproducible moreinfo

Hi,

* Adrian Bunk  [210207 18:14]:
> On Sun, Feb 07, 2021 at 06:30:20PM +0100, Chris Hofstaedtler wrote:
> > > /usr/lib/ruby/vendor_ruby/eventmachine.rb:532:in `start_tcp_server': no 
> > > acceptor (port is in use or requires root privileges) (RuntimeError)
> > 
> > Please explain what "IPv6-only buildd" actually means. How can one
> > reproduce this?
> 
> Some buildds no longer have IPV4 connectivity, and the release team 
> considers FTBFS on these release critical bugs.
> 
> The best information I am aware of is:
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962019#26

Thanks. However that info appears outdated, as on a current Debian
unstable, I always get a `lo` interface with 127.0.0.1 and ::1
bound. The tests want 127.0.0.1, so that works.

Without more info on how the buildd setup looks like, I cannot
reproduce this. Or maybe the failure has gone anyway?
 
> cu
> Adrian

Cheers,
Chris

Processed: tagging 974428

[Debian Bug Tracking System]

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

> tags 974428 + security
Bug #974428 [telnetd] in.telnetd crashes on running Nessus security scan
Added tag(s) security.
> thanks
Stopping processing here.

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

Bug#981793: marked as done (varmon: maintainer address bounces)

[Debian Bug Tracking System]

Your message dated Sun, 07 Feb 2021 18:04:17 +
with message-id 
and subject line Bug#981793: fixed in varmon 1.2.1-2
has caused the Debian Bug report #981793,
regarding varmon: maintainer address bounces
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.)


-- 
981793: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=981793
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
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
--- End Message ---
--- Begin Message ---
Source: varmon
Source-Version: 1.2.1-2
Done: Chris Hofstaedtler 

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 07 Feb 2021 16:53:44 +
Source: varmon
Architecture: source
Version: 1.2.1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: Chris Hofstaedtler 
Closes: 981793
Changes:
 varmon (1.2.1-2) unstable; urgency=medium
 .
   * QA upload.
   * Orphan package, Julien Danjou  is not active anymore.
 (Closes: #981793)
   * Use compat 13 and dh sequencer
   * Depend on makedev, used in postinst
Checksums-Sha1:
 78ed13bb8e3f0a8b2fd1580a1bf194a4d7371f84 1672 varmon_1.2.1-2.dsc
 a6ec083864245c06d88dcbde342cfb03bdf6ad93 3056 varmon_1.2.1-2.debian.tar.xz
 4ea3d19c496993bcf65f6aa680018dc514f40cca 5842 varmon_1.2.1-2_source.buildinfo
Checksums-Sha256:
 041fdc603176426a8d5b1c14f29f918ed9298e41e2251ee03ec465bd4ff420e6 1672 
varmon_1.2.1-2.dsc
 ae9230d60bbb67a31903c3d0e06e895af52c31902a3ca2829d13cc9710847431 3056 
varmon_1.2.1-2.debian.tar.xz
 4b20d5c2022e2b5950e3c3d3d58d10cca5a700731f52515f1eac64220a77d71e 5842 
varmon_1.2.1-2_source.buildinfo
Files:
 4020e7437b4222451b594c3a90cda81f 1672 admin extra varmon_1.2.1-2.dsc
 4fc6f75bf73fbc8621549ec848da9b88 3056 admin extra varmon_1.2.1-2.debian.tar.xz
 e0de76d96bc5413b443025aafa4e4dcc 5842 admin extra 
varmon_1.2.1-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEfRrP+tnggGycTNOSXBPW25MFLgMFAmAgJL0ACgkQXBPW25MF
LgNAIQ/9G+NEq5iTpuP2XjFM+/J4VsD0cLz9Oi2CfaRgD960zyDu+ZqGFyEigmNT
80jW4n97ym4mfQ37B4FAZsU7oNMW4Qqw1M894pGm95qk3u4k+nKFHjtN64DxzQ8e
WpUt2mFTVzGglYOKlITZtpZrhXayM9cf3MiYtGD23KL0NeuvSelifssDiEErdVtY
Qgqrg3OUBFLh4D8sa2VS6f6LaWW/vckl/t05LK+hOMwUKAJ/litHC2nqUW3+7rkc
+NnjbaeBgU580GrsWFlWWZBADzyUvT3MZeppgWztT8BfeNh4laryI+RIW3B1vaSw
XqnhyQue+YR0l5jrlIM134ZJp50bN7mBUxZ65FSYZ98AR4CTEma+epJuuQdZKrXq
EaQ1gZUfk1B6OYgGjqO0exK5u6AnA+LYRK7A6dVGWgqveMPXC+Juk0b3ehvPGURR
qLilnftxEUSxg87RkVFXJmC7kBx7sDuY7ZDpH1048Wrd1V+T0/8DFLhC1N6lehZR
uEDFPH3M0kwpkeohDqnCZTPUkbqa7WYbwFNedN8EmiJ2OuGqphwKcY3uS92dzxcH
c+dI+e2wydU/ZJ13zorvbpQzXXuwNz0G/kifd6art9DX84SZqIpgPYRJl4J3jhdf
yK7BWlHsTcBPEh7j2JQhNTcYHAKNhmigS6cWsONH5CkZ3EQW3AQ=
=lnFz
-END PGP SIGNATURE End Message ---

Bug#982122: redis: experimental package OOMs s390x buildds

[Chris Lamb]

Hi Adam,

> Both s390x buildds hit OOM conditions while attempting to build redis
> 6.2 in experimental.
>
> The log from zani ends with:
>
> [..]

Thanks. I can't seem to find the full log anywhere thoug; can you
help? I might need that before I can raise it with upstream.


Regards,

--
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org  chris-lamb.co.uk
   `-

Bug#981300: marked as done (arduino-mk: needs to depend on arduino 2:1.8.13+dfsg1-1)

[Willy nilly]

*closes: #12345*

On Sun, Feb 7, 2021 at 5:51 PM Debian Bug Tracking System <
ow...@bugs.debian.org> wrote:

> Your message dated Sun, 07 Feb 2021 17:48:19 +
> with message-id 
> and subject line Bug#981300: fixed in arduino-mk 1.5.2-2.1
> has caused the Debian Bug report #981300,
> regarding arduino-mk: needs to depend on arduino 2:1.8.13+dfsg1-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.)
>
>
> --
> 981300: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=981300
> Debian Bug Tracking System
> Contact ow...@bugs.debian.org with problems
>
>
>
> -- Forwarded message --
> From: debi...@the-jedi.co.uk
> To: sub...@bugs.debian.org
> Cc:
> Bcc:
> Date: Thu, 28 Jan 2021 21:42:40 +
> Subject: arduino-core-avr breaks arduino-mk
> Package: arduino
> Version: 1.8.13+dfsg1-1
>
> The recent rename of arduino-core to arduino-core-avr breaks the Depends
> in arduino-mk:
>
> Depends:
>   arduino-core (>= 1:1.0+dfsg-8),
>
> So doing a dist-upgrade and pulling in the new arduino, arduino-core-avr
> etc; removes arduino-core and arduino-mk
>
> Also why are you just now packaging arduino-builder when arduino-cli has
> already replaced it?
>
> Regards.
>
> --
> Simon John
>
>
>
> -- Forwarded message --
> From: Debian FTP Masters 
> To: 981300-cl...@bugs.debian.org
> Cc:
> Bcc:
> Date: Sun, 07 Feb 2021 17:48:19 +
> Subject: Bug#981300: fixed in arduino-mk 1.5.2-2.1
> Source: arduino-mk
> Source-Version: 1.5.2-2.1
> Done: Carsten Schoenert 
>
> We believe that the bug you reported is fixed in the latest version of
> arduino-mk, 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.
> Carsten Schoenert  (supplier of updated
> arduino-mk package)
>
> (This message was generated automatically at their request; if you
> believe that there is a problem with it please contact the archive
> administrators by mailing ftpmas...@ftp-master.debian.org)
>
>
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA512
>
> Format: 1.8
> Date: Thu, 04 Feb 2021 17:33:41 +0100
> Source: arduino-mk
> Architecture: source
> Version: 1.5.2-2.1
> Distribution: unstable
> Urgency: medium
> Maintainer: Debian Science Maintainers <
> debian-science-maintain...@lists.alioth.debian.org>
> Changed-By: Carsten Schoenert 
> Closes: 981300
> Changes:
>  arduino-mk (1.5.2-2.1) unstable; urgency=medium
>  .
>* Non-maintainer upload
>* [a802500] d/control: depend on arduino >= 2:1.8.13+dfsg1-1
>  Change the dependency to the arduino package, arduino-core isn't a
> real
>  package any more since the update of the arduino package to
> 1.8.13+dfsg1.
>  (Closes: #981300)
> Checksums-Sha1:
>  e18c4aae6ac6e6fb5a5afe7724f707032d616411 2033 arduino-mk_1.5.2-2.1.dsc
>  36aad1591c560ab224730ae835369fca55f22de7 4156
> arduino-mk_1.5.2-2.1.debian.tar.xz
>  9d027275a0b05c0f1aba3debc42b6bfb67bc64a2 5877
> arduino-mk_1.5.2-2.1_amd64.buildinfo
> Checksums-Sha256:
>  5e3ce89b325319c2311a498d053093207a20c2577cfd968bdec7893811a2ad8c 2033
> arduino-mk_1.5.2-2.1.dsc
>  c6c44c01651c99cce8e6bbef93ebc31a3c3aa941deee418a869517139e128c7f 4156
> arduino-mk_1.5.2-2.1.debian.tar.xz
>  45df1546b4fbbf1abfedf3f5393cdd9a2733d1aefaa6c43798178df61f615f4e 5877
> arduino-mk_1.5.2-2.1_amd64.buildinfo
> Files:
>  fd22a46eddb3b9563ebfcacb65e1a476 2033 electronics optional
> arduino-mk_1.5.2-2.1.dsc
>  5fc7ed019bec5591de5b2720a88d2e33 4156 electronics optional
> arduino-mk_1.5.2-2.1.debian.tar.xz
>  21782bf17c91ddcf340f20c9f48ef9c0 5877 electronics optional
> arduino-mk_1.5.2-2.1_amd64.buildinfo
>
> -BEGIN PGP SIGNATURE-
>
> iQJMBAEBCgA2FiEEtw38bxNP7PwBHmKqgwFgFCUdHbAFAmAgIoMYHGMuc2Nob2Vu
> ZXJ0QHQtb25saW5lLmRlAAoJEIMBYBQlHR2wowoP/Ray/uzm9jO8uO4H8nglmINy
> wiQQrHvPdYKrFIvCCuYe/z8YbWY+b+c1ZYhW9NGso4sTV34XTwwiV2RoyT6yN+oU
> GxKZNzNufqlFQeFplI5b33jekirq9+mshA7gf1op6wbBJB6b6JJ9kEf5+2FQDV8i
> 6n7I9wO3e8OwgivU5kNErfSAaMBhlWxqAtKsgP5UnYa4zqGGX8vIa1i5Ss0RTT5s
> l7eKyKRz6+8iBnLd2liL+jvnHCQL7GjWaLgI0GdEZFAeg6g2IzHLB16soXUvJDDl
> q0eJJDXbu2tYwuh0KC1Y+rhN/UyreYvM8YxuYg58QUlA+Z9r3DORqSvYiyvuvHey
> /GUbNY/lvp4/l4NdAj2zLDOdr3SE6zzyLp0KEAXqgy+ZsSxw0qhVKDzmMPFFQwv1
> rJnUA/L3SZsXLqc/iohpPVteQh7AXam4jLgT4QQ4Nkhy02AJFqowdQalJFuUJBAe
> Q+u+tqpTlIQNi22/7Dzw4lLwpV2Mh0HbJXV0gmDumA3Rd4xoLwoAd/2pn+tO9Xnj
> 

Bug#981300: marked as done (arduino-mk: needs to depend on arduino 2:1.8.13+dfsg1-1)

[Debian Bug Tracking System]

Your message dated Sun, 07 Feb 2021 17:48:19 +
with message-id 
and subject line Bug#981300: fixed in arduino-mk 1.5.2-2.1
has caused the Debian Bug report #981300,
regarding arduino-mk: needs to depend on arduino 2:1.8.13+dfsg1-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.)


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

Package: arduino
Version: 1.8.13+dfsg1-1

The recent rename of arduino-core to arduino-core-avr breaks the Depends 
in arduino-mk:


Depends:
 arduino-core (>= 1:1.0+dfsg-8),

So doing a dist-upgrade and pulling in the new arduino, arduino-core-avr 
etc; removes arduino-core and arduino-mk


Also why are you just now packaging arduino-builder when arduino-cli has 
already replaced it?


Regards.

--
Simon John
--- End Message ---
--- Begin Message ---
Source: arduino-mk
Source-Version: 1.5.2-2.1
Done: Carsten Schoenert 

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 04 Feb 2021 17:33:41 +0100
Source: arduino-mk
Architecture: source
Version: 1.5.2-2.1
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Carsten Schoenert 
Closes: 981300
Changes:
 arduino-mk (1.5.2-2.1) unstable; urgency=medium
 .
   * Non-maintainer upload
   * [a802500] d/control: depend on arduino >= 2:1.8.13+dfsg1-1
 Change the dependency to the arduino package, arduino-core isn't a real
 package any more since the update of the arduino package to 1.8.13+dfsg1.
 (Closes: #981300)
Checksums-Sha1:
 e18c4aae6ac6e6fb5a5afe7724f707032d616411 2033 arduino-mk_1.5.2-2.1.dsc
 36aad1591c560ab224730ae835369fca55f22de7 4156 
arduino-mk_1.5.2-2.1.debian.tar.xz
 9d027275a0b05c0f1aba3debc42b6bfb67bc64a2 5877 
arduino-mk_1.5.2-2.1_amd64.buildinfo
Checksums-Sha256:
 5e3ce89b325319c2311a498d053093207a20c2577cfd968bdec7893811a2ad8c 2033 
arduino-mk_1.5.2-2.1.dsc
 c6c44c01651c99cce8e6bbef93ebc31a3c3aa941deee418a869517139e128c7f 4156 
arduino-mk_1.5.2-2.1.debian.tar.xz
 45df1546b4fbbf1abfedf3f5393cdd9a2733d1aefaa6c43798178df61f615f4e 5877 
arduino-mk_1.5.2-2.1_amd64.buildinfo
Files:
 fd22a46eddb3b9563ebfcacb65e1a476 2033 electronics optional 
arduino-mk_1.5.2-2.1.dsc
 5fc7ed019bec5591de5b2720a88d2e33 4156 electronics optional 
arduino-mk_1.5.2-2.1.debian.tar.xz
 21782bf17c91ddcf340f20c9f48ef9c0 5877 electronics optional 
arduino-mk_1.5.2-2.1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJMBAEBCgA2FiEEtw38bxNP7PwBHmKqgwFgFCUdHbAFAmAgIoMYHGMuc2Nob2Vu
ZXJ0QHQtb25saW5lLmRlAAoJEIMBYBQlHR2wowoP/Ray/uzm9jO8uO4H8nglmINy
wiQQrHvPdYKrFIvCCuYe/z8YbWY+b+c1ZYhW9NGso4sTV34XTwwiV2RoyT6yN+oU
GxKZNzNufqlFQeFplI5b33jekirq9+mshA7gf1op6wbBJB6b6JJ9kEf5+2FQDV8i
6n7I9wO3e8OwgivU5kNErfSAaMBhlWxqAtKsgP5UnYa4zqGGX8vIa1i5Ss0RTT5s
l7eKyKRz6+8iBnLd2liL+jvnHCQL7GjWaLgI0GdEZFAeg6g2IzHLB16soXUvJDDl
q0eJJDXbu2tYwuh0KC1Y+rhN/UyreYvM8YxuYg58QUlA+Z9r3DORqSvYiyvuvHey
/GUbNY/lvp4/l4NdAj2zLDOdr3SE6zzyLp0KEAXqgy+ZsSxw0qhVKDzmMPFFQwv1
rJnUA/L3SZsXLqc/iohpPVteQh7AXam4jLgT4QQ4Nkhy02AJFqowdQalJFuUJBAe
Q+u+tqpTlIQNi22/7Dzw4lLwpV2Mh0HbJXV0gmDumA3Rd4xoLwoAd/2pn+tO9Xnj
nejZ9rhvHOoxBzd7PiM7wYsvJJR2nEdTYN/ra2oaWui58yuRMFghiEMqD7Qh6sOw
VRK82gylyZ6s42pfeMJo9hPMHB0jOti4v0VpB4rFlYXmLyMOIlnzdDaP2No5+dvH
qKx18flko5fpC+1XxtFl
=Slmd
-END PGP SIGNATURE End Message ---

Bug#966942: marked as done (ipxe: FTBFS: ld: bin-i386-pcbios/blib.a(dmfe.o):(.bss+0x0): multiple definition of `_shared_bss'; bin-i386-pcbios/blib.a(davicom.o):(.bss+0x0): first defined here)

[Debian Bug Tracking System]

Your message dated Sun, 07 Feb 2021 17:49:02 +
with message-id 
and subject line Bug#966942: fixed in ipxe 1.0.0+git-20190125.36a4c85-5.1
has caused the Debian Bug report #966942,
regarding ipxe: FTBFS: ld: bin-i386-pcbios/blib.a(dmfe.o):(.bss+0x0): multiple 
definition of `_shared_bss'; bin-i386-pcbios/blib.a(davicom.o):(.bss+0x0): 
first defined here
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.)


-- 
966942: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966942
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ipxe
Version: 1.0.0+git-20190125.36a4c85-5
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200802 ftbfs-bullseye

Hi,

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

Relevant part (hopefully):
> make[2]: Entering directory '/<>/src'
> gcc -DARCH=i386 -DPLATFORM=pcbios -DSECUREBOOT=0 -march=i386 
> -fomit-frame-pointer -fstrength-reduce -falign-jumps=1 -falign-loops=1 
> -falign-functions=1 -mpreferred-stack-boundary=2 -mregparm=3 -mrtd 
> -freg-struct-return -m32 -fshort-wchar -Ui386 -Ulinux -DNVALGRIND -Iinclude 
> -I. -Iarch/x86/include -Iarch/i386/include -Iarch/i386/include/pcbios -Os -g 
> -ffreestanding -Wall -W -Wformat-nonliteral -fno-stack-protector 
> -fno-dwarf2-cfi-asm -fno-exceptions  -fno-unwind-tables 
> -fno-asynchronous-unwind-tables -Wno-address -Wno-stringop-truncation 
> -fno-PIE -no-pie   -ffunction-sections  -include include/compiler.h 
> -DASM_TCHAR='@' -DASM_TCHAR_OPS='@'   -DOBJECT=version 
> -DBUILD_NAME="\"ipxe.lkrn\"" \
>   -DVERSION_MAJOR=1 \
>   -DVERSION_MINOR=0 \
>   -DVERSION_PATCH=0 \
>   -DVERSION="\"1.0.0+git-20190125.36a4c85-5\"" \
>   -c core/version.c -o bin-i386-pcbios/version.ipxe.lkrn.o
> ld -m elf_i386 -N --no-check-sections --section-start=.prefix=0   
> --gc-sections -static -T arch/x86/scripts/pcbios.lds  -u _lkrn_start --defsym 
> check__lkrn_start=_lkrn_start   -u obj_3c509_eisa --defsym 
> check_obj_3c509_eisa=obj_3c509_eisa   -u obj_3c509 --defsym 
> check_obj_3c509=obj_3c509   -u obj_3c515 --defsym check_obj_3c515=obj_3c515   
> -u obj_3c529 --defsym check_obj_3c529=obj_3c529   -u obj_3c595 --defsym 
> check_obj_3c595=obj_3c595   -u obj_3c90x --defsym check_obj_3c90x=obj_3c90x   
> -u obj_amd8111e --defsym check_obj_amd8111e=obj_amd8111e   -u obj_atl1e 
> --defsym check_obj_atl1e=obj_atl1e   -u obj_b44 --defsym 
> check_obj_b44=obj_b44   -u obj_cs89x0 --defsym check_obj_cs89x0=obj_cs89x0   
> -u obj_davicom --defsym check_obj_davicom=obj_davicom   -u obj_depca --defsym 
> check_obj_depca=obj_depca   -u obj_dmfe --defsym check_obj_dmfe=obj_dmfe   -u 
> obj_eepro --defsym check_obj_eepro=obj_eepro   -u obj_eepro100 --defsym 
> check_obj_eepro100=obj_eepro100   -u obj_ena --defsym check_obj_ena=obj_ena   
> -u obj_epic100 --defsym check_obj_epic100=obj_epic100   -u obj_etherfabric 
> --defsym check_obj_etherfabric=obj_etherfabric   -u obj_exanic --defsym 
> check_obj_exanic=obj_exanic   -u obj_forcedeth --defsym 
> check_obj_forcedeth=obj_forcedeth   -u obj_icplus --defsym 
> check_obj_icplus=obj_icplus   -u obj_intel --defsym check_obj_intel=obj_intel 
>   -u obj_intelx --defsym check_obj_intelx=obj_intelx   -u obj_intelxl 
> --defsym check_obj_intelxl=obj_intelxl   -u obj_intelxvf --defsym 
> check_obj_intelxvf=obj_intelxvf   -u obj_jme --defsym check_obj_jme=obj_jme   
> -u obj_myri10ge --defsym check_obj_myri10ge=obj_myri10ge   -u obj_myson 
> --defsym check_obj_myson=obj_myson   -u obj_natsemi --defsym 
> check_obj_natsemi=obj_natsemi   -u obj_ne2k_isa --defsym 
> check_obj_ne2k_isa=obj_ne2k_isa   -u obj_ns8390 --defsym 
> check_obj_ns8390=obj_ns8390   -u obj_pcnet32 --defsym 
> check_obj_pcnet32=obj_pcnet32   -u obj_pnic --defsym check_obj_pnic=obj_pnic  
>  -u obj_prism2_pci --defsym check_obj_prism2_pci=obj_prism2_pci   -u 
> obj_prism2_plx --defsym check_obj_prism2_plx=obj_prism2_plx   -u obj_realtek 
> --defsym check_obj_realtek=obj_realtek   -u obj_rhine --defsym 
> check_obj_rhine=obj_rhine   -u obj_sis190 --defsym 
> check_obj_sis190=obj_sis190   -u obj_sis900 --defsym 
> check_obj_sis900=obj_sis900   -u obj_skeleton --defsym 
> check_obj_skeleton=obj_skeleton   -u obj_skge --defsym 
> check_obj_skge=obj_skge   -u obj_sky2 --defsym check_obj_sky2=obj_sky2   -u 
> obj_smc9000 --defsym check_obj_smc9000=obj_smc9000   -u obj_sundance --defsym 
> check_obj_sundance=obj_sundance   -u obj_thunderx --defsym 
> check_obj_thunderx=obj_thunderx   -u obj_tlan --defsym 
> check_obj_tlan=obj_tlan   -u obj_tulip --defsym 

Bug#979432: ruby-rack FTBFS on IPV6-only buildds

[Adrian Bunk]

On Sun, Feb 07, 2021 at 06:30:20PM +0100, Chris Hofstaedtler wrote:
> > /usr/lib/ruby/vendor_ruby/eventmachine.rb:532:in `start_tcp_server': no 
> > acceptor (port is in use or requires root privileges) (RuntimeError)
> 
> Please explain what "IPv6-only buildd" actually means. How can one
> reproduce this?

Some buildds no longer have IPV4 connectivity, and the release team 
considers FTBFS on these release critical bugs.

The best information I am aware of is:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962019#26

> Chris

cu
Adrian

Bug#982253: netkit telnetd: ship with bullseye with open security problems?

[Chris Hofstaedtler]

Package: telnetd
Version: 0.17-41.2
Severity: serious

Hi,

telnetd from netkit appears to have multiple problems, which make me
think we shouldn't ship it:

1) open bug #974428, causes telnetd to crash, remotely triggerable
2) possibly unpatched exploit here: https://www.exploit-db.com/exploits/48170
3) no upstream?
4) maintainer in Debian appears to be missing from the action

The first bug has a patch applied, but overall I think we should
still not ship it. Security team, your opinion please?

I'd suggest we replace telnetd with an empty package depending on
inetutils-telnetd, or if thats a bad idea, just remove telnetd from
the netkit-telnet sources.

I've CCed the inetutils-telnetd maintainer.

Chris

Bug#980587: marked as done (liblightify: FTBFS: sh: 1: error: Problems running dot: exit code=127, command='dot', arguments='"/<>/doc/doxygen/latex/liblightify_09_09_8hpp__dep__incl.dot"

[Debian Bug Tracking System]

Your message dated Sun, 07 Feb 2021 17:34:08 +
with message-id 
and subject line Bug#980587: fixed in liblightify 0~git20160911-2
has caused the Debian Bug report #980587,
regarding liblightify: FTBFS: sh: 1: error: Problems running dot: exit 
code=127, command='dot', 
arguments='"/<>/doc/doxygen/latex/liblightify_09_09_8hpp__dep__incl.dot"
 -Tpdf -o 
"/<>/doc/doxygen/latex/liblightify_09_09_8hpp__dep__incl.pdf"'
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.)


-- 
980587: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=980587
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: liblightify
Version: 0~git20160911-1
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):
> make[2]: Entering directory '/<>'
> mkdir -p doc/doxygen
> rm -rf doc/doxygen
> SRCDIR='.' PROJECT='lightify' VERSION='0' PERL_PATH='/usr/bin/perl' 
> HAVE_DOT='NO' GENERATE_MAN='NO' GENERATE_RTF='NO' GENERATE_XML='NO' 
> GENERATE_HTMLHELP='NO' GENERATE_CHI='NO' GENERATE_HTML='YES' 
> GENERATE_LATEX='NO' DOCDIR=doc/doxygen /usr/bin/doxygen Doxyfile
> warning: Tag 'TCL_SUBST' at line 247 of file 'Doxyfile' has become obsolete.
>  To avoid this warning please remove this line from your 
> configuration file or upgrade it using "doxygen -u"
> warning: Tag 'COLS_IN_ALPHA_INDEX' at line 1071 of file 'Doxyfile' has become 
> obsolete.
>  To avoid this warning please remove this line from your 
> configuration file or upgrade it using "doxygen -u"
> warning: Tag 'PERL_PATH' at line 2125 of file 'Doxyfile' has become obsolete.
>  To avoid this warning please remove this line from your 
> configuration file or upgrade it using "doxygen -u"
> warning: Tag 'MSCGEN_PATH' at line 2147 of file 'Doxyfile' has become 
> obsolete.
>  To avoid this warning please remove this line from your 
> configuration file or upgrade it using "doxygen -u"
> /<>/src/liblightify++/liblightify++.hpp:34: warning: the name 
> 'lightify++.h' supplied as the argument in the \file statement is not an 
> input file
> Doxygen version used: 1.9.1
> Notice: Output directory 'doc/doxygen' does not exist. I have created it for 
> you.
> Searching for include files...
> Searching for example files...
> Searching for images...
> Searching for dot files...
> Searching for msc files...
> Searching for dia files...
> Searching for files to exclude
> Searching INPUT for files to process...
> Searching for files in directory /<>/src
> Searching for files in directory /<>/src/liblightify
> Searching for files in directory /<>/src/liblightify++
> Searching for files in directory /<>/src/tests
> Searching for files in directory /<>/src/tools
> Reading and parsing tag files
> Parsing files
> Preprocessing /<>/src/context.c...
> Parsing file /<>/src/context.c...
> Preprocessing /<>/src/context.h...
> Parsing file /<>/src/context.h...
> Preprocessing /<>/src/groups.c...
> Parsing file /<>/src/groups.c...
> Preprocessing /<>/src/groups.h...
> Parsing file /<>/src/groups.h...
> Preprocessing /<>/src/liblightify/liblightify.h...
> Parsing file /<>/src/liblightify/liblightify.h...
> 
> Preprocessing /<>/src/liblightify++/liblightify++.hpp...
> Parsing file /<>/src/liblightify++/liblightify++.hpp...
> Preprocessing /<>/src/liblightify-private.h...
> Parsing file /<>/src/liblightify-private.h...
> Preprocessing /<>/src/liblightify.c...
> Parsing file /<>/src/liblightify.c...
> Preprocessing /<>/src/log.c...
> Parsing file /<>/src/log.c...
> Preprocessing /<>/src/log.h...
> Parsing file /<>/src/log.h...
> Preprocessing /<>/src/node.c...
> Parsing file /<>/src/node.c...
> Preprocessing /<>/src/node.h...
> Parsing file /<>/src/node.h...
> Preprocessing /<>/src/socket.c...
> Parsing file /<>/src/socket.c...
> Preprocessing /<>/src/socket.h...
> Parsing file /<>/src/socket.h...
> Preprocessing /<>/src/tests/test-lightify.c...
> Parsing file /<>/src/tests/test-lightify.c...
> Preprocessing /<>/src/tools/lightify-example.cpp...
> Parsing file /<>/src/tools/lightify-example.cpp...
> Preprocessing /<>/src/tools/lightify-util.c...
> Parsing file /<>/src/tools/lightify-util.c...
> Building macro definition list...
> Building group list...
> Building directory list...
> Building namespace list...
> Building file list...
> Building class list...
> Computing nesting relations for classes...
> Associating documentation with classes...
> Building example 

Processed: fixed 972767 in frr/7.4-2

[Debian Bug Tracking System]

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

> # 7.4-2 reverts the NMU, but fixed the FTBFS without closing the bug
> fixed 972767 frr/7.4-2
Bug #972767 {Done: Adrian Bunk } [src:frr] frr ftbfs with 
python3.9
Marked as fixed in versions frr/7.4-2.
> thanks
Stopping processing here.

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

Bug#981850: [DRE-maint] Bug#981850: Failed: rspec-core, rspec-support

[Ritesh Raj Sarraf]

Hi Antonio,

On Thu, 2021-02-04 at 20:19 -0300, Antonio Terceiro wrote:
> Can you please share more information about the environment where you
> did this build?
> 

So this was run on an Open Build Server instance, where a chroot for
the target system is created on-the-fly, for every build.

> I can reproduce a test failure with a non-UTF-8 locale, is that the
> case?

Probably. Because I'm getting a similar case for some Haskell packages
and so far the hint has been that it could be because of the non-utf8
locale. But I'm yet to confirm that.

Thanks,
Ritesh

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


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

Bug#979432: ruby-rack FTBFS on IPV6-only buildds

[Chris Hofstaedtler]

> /usr/lib/ruby/vendor_ruby/eventmachine.rb:532:in `start_tcp_server': no 
> acceptor (port is in use or requires root privileges) (RuntimeError)

Please explain what "IPv6-only buildd" actually means. How can one
reproduce this?

Chris

Bug#962844: mdadm: Assembling RAID using IMSM in initrd fails due to lack of module efivarfs

[Chris Hofstaedtler]

Hi Felix,

friendly ping here, are you planning to fix this for bullseye?

* Felix Lechner  [210207 17:20]:
> I would like to make sure any new module requirements are also
> compatible with systems booting in legacy BIOS mode.

While that's great, adding the module to the initramfs would at
least unbreak it for all UEFI installations (which should be more
common with such hardware).

Chris

Processed: Re: Bug#982059: manpages-de,psmisc: File conflict between psmisc and manpages-de: '/usr/share/man/de/man1/fuser.1.gz

[Debian Bug Tracking System]

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

> tags 982059 + pending
Bug #982059 [manpages-de,psmisc] manpages-de,psmisc: File conflict between 
psmisc and manpages-de: '/usr/share/man/de/man1/fuser.1.gz
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#982059: manpages-de,psmisc: File conflict between psmisc and manpages-de: '/usr/share/man/de/man1/fuser.1.gz

[Helge Kreutzmann]

tags 982059 + pending
thanks

Hello Craig,
the manpage-l10n package is ready to go. You can either pick it up
from git https://salsa.debian.org/debian/manpages-l10n.git and perfom
"gbp buildpackage" or you can download the packages "ready to sign and
upload" from my site:
https://www.helgefjell.de/data/manpages-l10n_4.9.1-1.tar.xz
https://www.helgefjell.de/data/manpages-l10n_4.9.1-1.tar.xz.sig

Since the Freeze is rapidly approaching an upload at your earliest
possiblity would be highly appreciated. 

In case of problems I'll respond within 24 hours.

Thanks for your support.

Greetings

 Helge
-- 
  Dr. Helge Kreutzmann deb...@helgefjell.de
   Dipl.-Phys.   http://www.helgefjell.de/debian.php
64bit GNU powered gpg signed mail preferred
   Help keep free software "libre": http://www.ffii.de/


signature.asc
Description: PGP signature

Processed: Re: Bug#954977: "Daily Limit Exceeded" connection error

[Debian Bug Tracking System]

Processing control commands:

> forwarded -1 https://gitlab.gnome.org/GNOME/gnome-online-accounts/-/issues/89
Bug #954977 [evolution] "Daily Limit Exceeded" connection error
Bug #955458 [evolution] evolution: daily limit exceeded cannot connect to 
google calandar
Set Bug forwarded-to-address to 
'https://gitlab.gnome.org/GNOME/gnome-online-accounts/-/issues/89'.
Set Bug forwarded-to-address to 
'https://gitlab.gnome.org/GNOME/gnome-online-accounts/-/issues/89'.
> severity -1 normal
Bug #954977 [evolution] "Daily Limit Exceeded" connection error
Bug #955458 [evolution] evolution: daily limit exceeded cannot connect to 
google calandar
Severity set to 'normal' from 'grave'
Severity set to 'normal' from 'grave'

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

Bug#954977: "Daily Limit Exceeded" connection error

[Chris Hofstaedtler]

Control: forwarded -1 
https://gitlab.gnome.org/GNOME/gnome-online-accounts/-/issues/89
Control: severity -1 normal

This isn't a code bug, but a limitation of a proprietary service,
which we have no influence over. Given Evolution can be used with
other services and not just Gmail, it's certainly not gravely
broken.

Either upstream will request higher limits, or affected users could
try the workarounds suggested in the upstream issue tracker.

Processed: Re: Bug#933150: evolution crashes on loading external contents

[Debian Bug Tracking System]

Processing control commands:

> severity -1 normal
Bug #933150 [evolution] evolution crashes on loading external contents
Severity set to 'normal' from 'grave'

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

Processed: Re: Bug#930733: evolution: Can't open evolution

[Debian Bug Tracking System]

Processing control commands:

> severity -1 normal
Bug #930733 [evolution] evolution: Can't open evolution
Severity set to 'normal' from 'grave'

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

Bug#930733: evolution: Can't open evolution

[Chris Hofstaedtler]

Control: severity -1 normal

* Diane Trout  [210207 17:10]:
> I was looking through Debian release-critical bugs and saw this report
> that no one had followed up on. Evolution 3.38.2 is working for me and
> I was wondering if you were still having trouble.

Given there was no feedback and its generally working for other
peopgle, I'm downgrading severity of this bug.

Chris

Bug#933150: evolution crashes on loading external contents

[Chris Hofstaedtler]

Control: severity -1 normal

Given lack of feedback, no useful backtrace and that we have many
newer versions by now, I'm downgrading severity of this bug for now.

Chris

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

[Debian Bug Tracking System]

Your message dated Sun, 07 Feb 2021 17:04:46 +
with message-id 
and subject line Bug#917729: fixed in weresync 1.0.9-1
has caused the Debian Bug report #917729,
regarding weresync: FTBFS: dpkg-buildpackage: error: dpkg-source -b . 
subprocess returned exit status 2
to be marked as done.

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

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


-- 
917729: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=917729
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: weresync
Version: 1.0.7-1
Severity: serious
Justification: FTBFS on amd64
Tags: buster sid
Usertags: ftbfs-20181229 ftbfs-buster

Hi,

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

Relevant part (hopefully):
>  fakeroot debian/rules clean
> dh clean --with python3,sphinxdoc --buildsystem=pybuild 
>dh_auto_clean -O--buildsystem=pybuild
> I: pybuild base:217: python3.7 setup.py clean 
> running clean
> removing '/<>/.pybuild/cpython3_3.7/build' (and everything under 
> it)
> 'build/bdist.linux-amd64' does not exist -- can't clean it
> 'build/scripts-3.7' does not exist -- can't clean it
>dh_autoreconf_clean -O--buildsystem=pybuild
>dh_clean -O--buildsystem=pybuild
>  dpkg-source -b .
> dpkg-source: info: using source format '3.0 (quilt)'
> dpkg-source: info: building weresync using existing 
> ./weresync_1.0.7.orig.tar.gz
> dpkg-source: error: cannot represent change to 
> src/weresync/resources/locale/en/LC_MESSAGES/weresync.mo: binary file 
> contents changed
> dpkg-source: error: add 
> src/weresync/resources/locale/en/LC_MESSAGES/weresync.mo in 
> debian/source/include-binaries if you want to store the modified binary in 
> the debian tarball
> dpkg-source: error: unrepresentable changes to source
> dpkg-buildpackage: error: dpkg-source -b . subprocess returned exit status 2
> 
> Build finished at 2018-12-29T12:40:29Z

The full build log is available from:
   http://aws-logs.debian.net/2018/12/29/weresync_1.0.7-1_unstable.log

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

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

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

Debian distribution maintenance software
pp.
Boyuan Yang  (supplier of updated weresync package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 07 Feb 2021 11:39:38 -0500
Source: weresync
Architecture: source
Version: 1.0.9-1
Distribution: unstable
Urgency: high
Maintainer: Debian Python Team 
Changed-By: Boyuan Yang 
Closes: 872103 917729
Changes:
 weresync (1.0.9-1) unstable; urgency=high
 .
   * Team upload.
   * New upstream release before switching to dbus and weresync-daemon.
   * Rebuild package. (Closes: #917729)
 .
   [ Ondřej Nový ]
   * d/copyright: Use https protocol in Format field
   * d/changelog: Remove trailing whitespaces
   * d/control: Remove Testsuite field, not needed anymore
   * d/rules: Remove trailing whitespaces
   * d/control: Remove ancient X-Python3-Version field
   * Use debhelper-compat instead of debian/compat.
   * d/control: Update Maintainer field with new Debian Python Team
 contact address.
   * d/control: Update Vcs-* fields with new Debian Python Team Salsa
 layout.
 .
   [ Debian Janitor ]
   * Bump debhelper from old 10 to 13.
   * Enarmor upstream signing key.
   * Set upstream metadata fields: Bug-Database, Bug-Submit, Repository,
 Repository-Browse.
   * Apply multi-arch hints.
 + weresync-doc: Add Multi-Arch: foreign.
 .
   [ Boyuan Yang ]
   * debian/rules: Use dh13 syntax.
   * debian/control: Add missing dependency fdisk. (Closes: #872103)
   * 

Bug#872103: marked as done (weresync: fdisk dependency needed)

[Debian Bug Tracking System]

Your message dated Sun, 07 Feb 2021 17:04:46 +
with message-id 
and subject line Bug#872103: fixed in weresync 1.0.9-1
has caused the Debian Bug report #872103,
regarding weresync: fdisk dependency 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.)


-- 
872103: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=872103
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: weresync
Version: 1.0.7-1
Severity: important
User: util-li...@packages.debian.org
Usertags: fdisk-dependency

Hello,

As recently announced on debian-devel-announce[1] packages who need
any of sfdisk, cfdisk or fdisk will need to add a dependency on the
new fdisk package.

Your package weresync showed up on codesearch.debian.net and a very
quick analysis suggested you might want to add a dependency (and/or
build-dependency if you use it at build-time, eg. tests).

Please use the backwards-compatible way of specifying the dependency
as suggested in the debian-devel-announce mail:

fdisk | util-linux (<< 2.29.2-3~)

(and if only for tests you might want to add the build profile
)

Please reassign this bug report to the binary package shipping the
affected part of your source.

If your more detailed analysis shows this should be a recommends,
suggests or even no relationship at all to the fdisk package then
please just close this bug report stating the results of your
analysis (and if so sorry for bothering you).

Regards, Andreas Henriksson

[1]:
https://lists.debian.org/debian-devel-announce/2017/08/msg5.html 
--- End Message ---
--- Begin Message ---
Source: weresync
Source-Version: 1.0.9-1
Done: Boyuan Yang 

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

Debian distribution maintenance software
pp.
Boyuan Yang  (supplier of updated weresync package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 07 Feb 2021 11:39:38 -0500
Source: weresync
Architecture: source
Version: 1.0.9-1
Distribution: unstable
Urgency: high
Maintainer: Debian Python Team 
Changed-By: Boyuan Yang 
Closes: 872103 917729
Changes:
 weresync (1.0.9-1) unstable; urgency=high
 .
   * Team upload.
   * New upstream release before switching to dbus and weresync-daemon.
   * Rebuild package. (Closes: #917729)
 .
   [ Ondřej Nový ]
   * d/copyright: Use https protocol in Format field
   * d/changelog: Remove trailing whitespaces
   * d/control: Remove Testsuite field, not needed anymore
   * d/rules: Remove trailing whitespaces
   * d/control: Remove ancient X-Python3-Version field
   * Use debhelper-compat instead of debian/compat.
   * d/control: Update Maintainer field with new Debian Python Team
 contact address.
   * d/control: Update Vcs-* fields with new Debian Python Team Salsa
 layout.
 .
   [ Debian Janitor ]
   * Bump debhelper from old 10 to 13.
   * Enarmor upstream signing key.
   * Set upstream metadata fields: Bug-Database, Bug-Submit, Repository,
 Repository-Browse.
   * Apply multi-arch hints.
 + weresync-doc: Add Multi-Arch: foreign.
 .
   [ Boyuan Yang ]
   * debian/rules: Use dh13 syntax.
   * debian/control: Add missing dependency fdisk. (Closes: #872103)
   * debian/weresync-doc.doc-base: Update documentation path.
Checksums-Sha1:
 41c485d9d1861b12bd3001567a476dd1024ea4c0 2425 weresync_1.0.9-1.dsc
 9cbf13e348bfcbb653a34e514cfabe0eb9d35121 157260 weresync_1.0.9.orig.tar.gz
 e7d27c119a70118161ff8a9ecfbee2d5a0c2b0fd 473 weresync_1.0.9.orig.tar.gz.asc
 86f5b46e6c4bf2576718532a567188abbca16b67 7308 weresync_1.0.9-1.debian.tar.xz
 fabe3761add7d9d5deff8874a95d91e5662159af 7761 weresync_1.0.9-1_amd64.buildinfo
Checksums-Sha256:
 ff45d39f429168709a9a16a999278d66b3229c63fe59c4faae8d3699732a8b0b 2425 
weresync_1.0.9-1.dsc
 6bdf15dfabe1177e6a9f2b67f5ebb2e1c28a264cfcea80695a9d5ced6488cc6e 157260 
weresync_1.0.9.orig.tar.gz
 d5362927cafcdab5e9f6eb36f25ef8487b7ed97403a7c7a58ea67cb6c73421ad 473 
weresync_1.0.9.orig.tar.gz.asc
 f6136bef108b33d576559fa3826980bf92f35f47a65f3dce266fd80dc0a329a8 7308 
weresync_1.0.9-1.debian.tar.xz
 

Processed: Re: Bug#981330: coturn: wrong logic for the dpkg-statoverride handling in coturn.postrm

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #981330 [coturn] coturn: wrong logic for the dpkg-statoverride handling in 
coturn.postrm
Severity set to 'serious' from 'important'

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

Bug#950761: RFS: ipmitool/1.8.18-11 [RC] -- utility for IPMI control with kernel driver or LAN interface (daemon)

[Salvatore Bonaccorso]

Hi Jörg,

On Sun, Jan 03, 2021 at 05:21:42PM +0100, Jörg Frings-Fürst wrote:
> tags 950761 - pending
> thanks
> 
> Hello Salvatore,
> hello @All,
> 
> 
> following a tip from Salvatore, I have added the missing commits.
> Although these can be incorporated manually, they are not reliably
> functional in at least two places due to the different code base.
> 
> I think the best thing will be to wait for the next upstream release.
> 
> I am therefore withdrawing the RFS bug again.

Did you had a chance to look into these? (Or alternatively to rebase
to the new upstream version)?

Regards,
Salvatore

Processed: Re: Bug#981394: sane-airscan: zzz

[Debian Bug Tracking System]

Processing control commands:

> retitle -1 sane-airscan: missing dependency on sane-utils
Bug #981394 [sane-airscan] Dependency missing?
Changed Bug title to 'sane-airscan: missing dependency on sane-utils' from 
'Dependency missing?'.
> severity -1 important
Bug #981394 [sane-airscan] sane-airscan: missing dependency on sane-utils
Severity set to 'important' from 'grave'
> tags -1 +pending
Bug #981394 [sane-airscan] sane-airscan: missing dependency on sane-utils
Added tag(s) pending.

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