Bug#975129: qwt: FTBFS: qwt_painter_command.h:85:22: error: field ‘clipPath’ has incomplete type ‘QPainterPath’

[Gudjon I. Gudjonsson]

Hi

On Sunday, 13 December 2020 18:06:22 CET you wrote:
> Please go ahead, I have been sponsoring QWT and even made the latest
> binNMU, and we can't risk this many packages being removed just now.
> Ping me if you need help!

Sorry, I won't have any time until at least from now. Please go ahead.

Regards
Gudjon

Processed: reopening 972921 (Was: shasta: binary-all FTBFS)

[Debian Bug Tracking System]

Processing control commands:

> tags -1 moreinfo
Bug #972921 {Done: Nilesh Patra } [src:shasta] shasta: 
binary-all FTBFS
Added tag(s) moreinfo.

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

Bug#972921: reopening 972921 (Was: shasta: binary-all FTBFS)

[Andreas Tille]

Control: tags -1 moreinfo

Hi Adrian,

On Tue, Dec 08, 2020 at 12:12:31PM +, Debian Bug Tracking System wrote:
> Please contact me if you need assistance.

I think I need assistance.  The Auto-Building page[1] shows green for
all, amd64 and arm64 and

   
https://buildd.debian.org/status/fetch.php?pkg=shasta=all=0.6.0-4=1607534158=0

looks OK.

So I wonder why that bug was reopened (may be you mistyped the bug number?)

Kind regards

   Andreas.

[1] https://buildd.debian.org/status/package.php?p=shasta

-- 
http://fam-tille.de

Processed: libstatgen: FTBFS on arm64: E: Build killed with signal TERM after 150 minutes of inactivity

[Debian Bug Tracking System]

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

> severity 976570 normal
Bug #976570 [src:libstatgen] libstatgen: FTBFS on arm64: E: Build killed with 
signal TERM after 150 minutes of inactivity
Severity set to 'normal' from 'serious'
> thanks
Stopping processing here.

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

Bug#976570: libstatgen: FTBFS on arm64: E: Build killed with signal TERM after 150 minutes of inactivity

[Dylan Aïssi]

severity 976570 normal
thanks

Hi,

arm64 is not on the architecture list for libstatgen, so I decrease
the severity of the bug.

Best,
Dylan

Bug#977407: marked as done (jitterdebugger-utils: missing Breaks+Replaces: jitterdebugger (<< 0.3.1+git20200117.b90ff3a-2))

[Debian Bug Tracking System]

Your message dated Tue, 15 Dec 2020 06:18:41 +
with message-id 
and subject line Bug#977407: fixed in jitterdebugger 0.3.1+git20200117.b90ff3a-3
has caused the Debian Bug report #977407,
regarding jitterdebugger-utils: missing Breaks+Replaces: jitterdebugger (<< 
0.3.1+git20200117.b90ff3a-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.)


-- 
977407: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977407
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: jitterdebugger-utils
Version: 0.3.1+git20200117.b90ff3a-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'testing'.
It installed fine in 'testing', then the upgrade to 'sid' fails
because it tries to overwrite other packages files without declaring a
Breaks+Replaces relation.

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

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

  Preparing to unpack 
.../jitterdebugger-utils_0.3.1+git20200117.b90ff3a-2_amd64.deb ...
  Unpacking jitterdebugger-utils (0.3.1+git20200117.b90ff3a-2) ...
  dpkg: error processing archive 
/var/cache/apt/archives/jitterdebugger-utils_0.3.1+git20200117.b90ff3a-2_amd64.deb
 (--unpack):
   trying to overwrite '/usr/bin/jitterplot', which is also in package 
jitterdebugger 0.3.1+git20200117.b90ff3a-1
  Errors were encountered while processing:
   
/var/cache/apt/archives/jitterdebugger-utils_0.3.1+git20200117.b90ff3a-2_amd64.deb


cheers,

Andreas


jitterdebugger=0.3.1+git20200117.b90ff3a-1_jitterdebugger-utils=0.3.1+git20200117.b90ff3a-2.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: jitterdebugger
Source-Version: 0.3.1+git20200117.b90ff3a-3
Done: =?utf-8?b?U1ogTGluICjmnpfkuIrmmbop?= 

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

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

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

Debian distribution maintenance software
pp.
SZ Lin (林上智)  (supplier of updated jitterdebugger package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 15 Dec 2020 13:36:20 +0800
Source: jitterdebugger
Architecture: source
Version: 0.3.1+git20200117.b90ff3a-3
Distribution: unstable
Urgency: medium
Maintainer: SZ Lin (林上智) 
Changed-By: SZ Lin (林上智) 
Closes: 977407
Changes:
 jitterdebugger (0.3.1+git20200117.b90ff3a-3) unstable; urgency=medium
 .
   * Add missing Breaks+Replaces fields (Closes: #977407)
Checksums-Sha1:
 88abd6a3010983aebae35302051b35630a5ccbe4 2194 
jitterdebugger_0.3.1+git20200117.b90ff3a-3.dsc
 419076212f7eb49f81d49062e35ab3a0841f0976 2720 
jitterdebugger_0.3.1+git20200117.b90ff3a-3.debian.tar.xz
 71a5598ed2ea0899ec3151b2c4659940a6a90099 7592 
jitterdebugger_0.3.1+git20200117.b90ff3a-3_amd64.buildinfo
Checksums-Sha256:
 2a73edd42f47c8eef0a620cf7fc7d8f1b459867dbe6be700c9c9dfb8d92d50ad 2194 
jitterdebugger_0.3.1+git20200117.b90ff3a-3.dsc
 5cc38f5583bead105a53a064c80b9ea24cf06aa690b0b1ec1f4203024738cf00 2720 
jitterdebugger_0.3.1+git20200117.b90ff3a-3.debian.tar.xz
 2e270818dc364c3a1ca9bc9d8ee8172975e02298cc325ade3de3fce2415ffe72 7592 
jitterdebugger_0.3.1+git20200117.b90ff3a-3_amd64.buildinfo
Files:
 dd0078c082016972d6898c356a67df3c 2194 misc optional 
jitterdebugger_0.3.1+git20200117.b90ff3a-3.dsc
 d8c2f29743ce4ded13199ffecf47b135 2720 misc optional 
jitterdebugger_0.3.1+git20200117.b90ff3a-3.debian.tar.xz
 b243b63842f946a0ecde067a1f6c62f5 7592 misc optional 
jitterdebugger_0.3.1+git20200117.b90ff3a-3_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEF4+DOLMUAeME/ES6qVmzipVh8/kFAl/YT6gACgkQqVmzipVh
8/n9nA//SP29FPTjOz+8fqUtqwcnDiWMcNGy/6xWnxLRUrqpn9KQD04HIvbQ0Kdw
4/o0AZrkf76IFu4vdR/gzNNEwrC19MZG29asYkslMWWAahd4hTjm96/uVu0zDQBn
iNyLEG9/6VS6dV3/onjeIZxg493dx1yebl1huPDUfkjdDCHBFP3wi5S2LQhxmVo4
Bn7mCR5JxEzePrNQVqhpRXV9wupfWA5g01Plmx9QE93GudSqNcMnAQ0M9vSWIg91
+p4pAJ0gif+GO+Puqz+qBdoMhVTG2mdBOK1wmHW4BPqSDOGbx7ozGSUQWBTUJWEr
z6g2v/vUf09UW2WiI0rXevxQV43p+4/UapFgELgYe/kBhxvS5E/sQ8jtxcvx6uO4

Bug#912880: gprename ported to GTK3

[Christoph Anton Mitterer]

Hey.

Seems gprename has been ported to GTK3... would be awesome if this
could find it's way back into Debian :-)

https://sourceforge.net/p/gprename/bugs/18/

Cheers,
Chris.

Processed: tagging 962203

[Debian Bug Tracking System]

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

> tags 962203 + patch
Bug #962203 [debdelta] DeprecationWarning: isAlive() is deprecated, use 
is_alive() instead
Bug #954420 [debdelta] Python deprecation warning
Added tag(s) patch.
Added tag(s) patch.
> thanks
Stopping processing here.

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

Processed: forcibly merging 962203 954420

[Debian Bug Tracking System]

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

> forcemerge 962203 954420
Bug #962203 [debdelta] DeprecationWarning: isAlive() is deprecated, use 
is_alive() instead
Bug #954420 [debdelta] Python deprecation warning
Severity set to 'grave' from 'minor'
Merged 954420 962203
> thanks
Stopping processing here.

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

Bug#977423: marked as done (maintainer address bounces)

[Debian Bug Tracking System]

Your message dated Tue, 15 Dec 2020 02:49:47 +0100
with message-id 
and subject line Re: maintainer address bounces
has caused the Debian Bug report #977423,
regarding 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.)


-- 
977423: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977423
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: apt-listchanges
Severity: serious

I just tried to file a bug report against apt-listchanges and got this
reply

Reporting-MTA: dns;VI1EUR04HT091.mail.protection.outlook.com
Received-From-MTA: dns;DBAPR01MB7126.eurprd01.prod.exchangelabs.com
Arrival-Date: Mon, 14 Dec 2020 23:33:24 +

Final-Recipient: rfc822;amdln...@googlemail.com
Action: failed
Status: 5.1.1
Diagnostic-Code: smtp;550-5.1.1 The email account that you tried to reach does 
not exist. Please try
 550-5.1.1 double-checking the recipient's email address for typos or
 550-5.1.1 unnecessary spaces. Learn more at
 550 5.1.1  https://support.google.com/mail/?p=NoSuchUser w1si79431edl.297 - 
gsmtp
Remote-MTA: dns;mx.google.com



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

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

-- debconf information excluded
--- End Message ---
--- Begin Message ---
Am Dienstag, dem 15.12.2020 um 01:22 +0100 schrieb Ansgar:
> Hi,
> 
> On Tue, 15 Dec 2020 00:36:23 +0100 Michael Biebl wrote:
> > I just tried to file a bug report against apt-listchanges and got
> > this
> > reply
> > 
> > Reporting-MTA: dns;VI1EUR04HT091.mail.protection.outlook.com
> > Received-From-MTA: dns;DBAPR01MB7126.eurprd01.prod.exchangelabs.com
> > Arrival-Date: Mon, 14 Dec 2020 23:33:24 +
> > 
> > Final-Recipient: rfc822;amdln...@googlemail.com
> > Action: failed
> > Status: 5.1.1
> > Diagnostic-Code: smtp;550-5.1.1 The email account that you tried to
> > reach does not exist. Please try
> 
> I don't think this is the maintainer address, but someone being
> subscribed to mailing lists and Microsoft's electronic telefax[1]
> solution sending error messages to the address given in the "From"
> header instead of the envelope address (which should be the mailing
> list software).
> 

Ok, thanks for the explanation. I assume you mean the RC bugs mailing
list. Closing this issue then.

Regards,
Michael


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

Bug#977397: uim-el: missing *-uim in input-method-alist on Emacs 27

[dai]

Control: tag -1 patch fixed-upstream

On Tue, Dec 15, 2020 at 02:31:46AM +0900, Nobuhiro Ban wrote:
> I used the japanese-anthy-utf8-uim input-method on my Debian Emacs 26 env.
> But after upgrading Emacs 27,
> I cannot set input-method to japanese-anthy-utf8-uim.
> 
> (Same cause as #977257)
> 
> There is a problem at initializing uim-el.
> So none of the input methods *-uim are prepared on startup.
> 
> From *Message* buffer:
> >Error while loading 50uim-el: Symbol’s function definition is void: 
> >process-kill-without-query
> 
> 
> How to fix:
> 
> Replace process-kill-without-query with set-process-query-on-exit-flag
> in /usr/share/emacs/site-lisp/uim-el/*.el .

Reproduced.  This is already fixed in upstream, so I will backport it:

https://github.com/uim/uim/commit/164e2eb050b5fec25033124834cf49ea1a7d8cbb
-- 
Regards,
dai

GPG Fingerprint = 0B29 D88E 42E6 B765 B8D8 EA50 7839 619D D439 668E


signature.asc
Description: PGP signature

Processed: Re: Bug#977397: uim-el: missing *-uim in input-method-alist on Emacs 27

[Debian Bug Tracking System]

Processing control commands:

> tag -1 patch fixed-upstream
Bug #977397 [uim-el] uim-el: missing *-uim in input-method-alist on Emacs 27
Added tag(s) fixed-upstream.

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

Processed: Re: Bug#977257: uim-el: "Active processes exist" prompt upon exiting emacs

[Debian Bug Tracking System]

Processing control commands:

> tags -1 confirmed
Bug #977257 [uim-el] uim-el: "Active processes exist" prompt upon exiting emacs
Added tag(s) confirmed.
> block -1 by 977397
Bug #977257 [uim-el] uim-el: "Active processes exist" prompt upon exiting emacs
977257 was not blocked by any bugs.
977257 was not blocking any bugs.
Added blocking bug(s) of 977257: 977397

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

Processed: Re: This package only builds Arch:all binary packages

[Debian Bug Tracking System]

Processing control commands:

> severity -1 normal
Bug #976548 [src:akuma] akuma: FTBFS on arm64,ppc64el (arch:all-only src pkg): 
dh_auto_test: error: /usr/lib/jvm/default-java/bin/java -noverify -cp 
/usr/share/maven/boot/plexus-classworlds-2.x.jar -Dmaven.home=/usr/share/maven 
-Dmaven.multiModuleProjectDirectory=/<> 
-Dclassworlds.conf=/etc/maven/m2-debian.conf 
-Dproperties.file.manual=/<>/debian/maven.properties 
org.codehaus.plexus.classworlds.launcher.Launcher 
-s/etc/maven/settings-debian.xml -Ddebian.dir=/<>/debian 
-Dmaven.repo.local=/<>/debian/maven-repo --batch-mode test 
returned exit code 1
Severity set to 'normal' from 'serious'

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

Bug#976548: This package only builds Arch:all binary packages

[Markus Koschany]

Control: severity -1 normal

The package is arch:all and builds fine on amd64 but FTBFS on other supported
architectures. Apparently one or two arch-dependent tests fail which is the
root cause of this failure. I'm downgrading the severity to normal as discussed
on the debian-java list. This is still a bug which should be fixed but it is
not release critical.

Markus


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

Bug#977108: marked as done (ruby-gollum-rugged-adapter, autopkgtest failure with ruby-rugged 1.1.0)

[Debian Bug Tracking System]

Your message dated Tue, 15 Dec 2020 00:49:35 +
with message-id 
and subject line Bug#977108: fixed in ruby-gollum-rugged-adapter 
0.4.4.3~gitlab.1-1
has caused the Debian Bug report #977108,
regarding ruby-gollum-rugged-adapter, autopkgtest failure with ruby-rugged 1.1.0
to be marked as done.

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

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


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

package: ruby-gollum-rugged-apapter
Version: 0.4.4.2-2
Severity: serious

The autopkgtest for ruby-gollum-rugged-adapter is failing with ruby-rugged 
1.1.0.


┌──┐
│ Checking Rubygems dependency resolution on ruby2.7   │
└──┘

GEM_PATH= ruby2.7 -e gem\ \"gitlab-gollum-rugged_adapter\"
/usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1398:in `rescue in block in 
activate_dependencies': Could not find 'rugged' (~> 0.25) among 60 total gem(s) 
(Gem::MissingSpecError)
Checked in 
'GEM_PATH=/home/debci/.local/share/gem/ruby/2.7.0:/var/lib/gems/2.7.0:/usr/local/lib/ruby/gems/2.7.0:/usr/lib/ruby/gems/2.7.0:/usr/lib/x86_64-linux-gnu/ruby/gems/2.7.0:/usr/share/rubygems-integration/2.7.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.7.0'
 at: 
/usr/share/rubygems-integration/all/specifications/gitlab-gollum-rugged_adapter-0.4.4.2.gemspec,
 execute `gem env` for more information
from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1395:in `block 
in activate_dependencies'
from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1384:in `each'
from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1384:in 
`activate_dependencies'
from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1366:in 
`activate'
from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in 
`block in gem'
from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in 
`synchronize'
from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in 
`gem'
from -e:1:in `'
/usr/lib/ruby/vendor_ruby/rubygems/dependency.rb:309:in `to_specs': Could not find 
'rugged' (~> 0.25) - did find: [rugged-1.1.0] (Gem::MissingSpecVersionError)
Checked in 
'GEM_PATH=/home/debci/.local/share/gem/ruby/2.7.0:/var/lib/gems/2.7.0:/usr/local/lib/ruby/gems/2.7.0:/usr/lib/ruby/gems/2.7.0:/usr/lib/x86_64-linux-gnu/ruby/gems/2.7.0:/usr/share/rubygems-integration/2.7.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.7.0'
 , execute `gem env` for more information
from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1396:in `block 
in activate_dependencies'
from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1384:in `each'
from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1384:in 
`activate_dependencies'
from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1366:in 
`activate'
from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in 
`block in gem'
from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in 
`synchronize'
from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in 
`gem'
from -e:1:in `'


This is blocking ruby-rugged 1.1.0 (which is needed for the libgit2 transition) 
from migrating to
testing.
--- End Message ---
--- Begin Message ---
Source: ruby-gollum-rugged-adapter
Source-Version: 0.4.4.3~gitlab.1-1
Done: Pirate Praveen 

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

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

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

Debian distribution maintenance software
pp.
Pirate Praveen  (supplier of updated 
ruby-gollum-rugged-adapter package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 15 Dec 2020 00:34:26 +0530
Source: ruby-gollum-rugged-adapter
Architecture: source
Version: 0.4.4.3~gitlab.1-1
Distribution: 

Bug#976915: marked as done (service-wrapper-java: FTBFS on ppc64el: [exec] wrapper.c:(.text+0x3598): undefined reference to `pow')

[Debian Bug Tracking System]

Your message dated Tue, 15 Dec 2020 00:49:40 +
with message-id 
and subject line Bug#976915: fixed in service-wrapper-java 3.5.30-3
has caused the Debian Bug report #976915,
regarding service-wrapper-java: FTBFS on ppc64el:  [exec] 
wrapper.c:(.text+0x3598): undefined reference to `pow'
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.)


-- 
976915: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976915
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: service-wrapper-java
Version: 3.5.30-1
Severity: serious
Justification: FTBFS on ppc64el
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201209 ftbfs-bullseye ftbfs-ppc64el

Hi,

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

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

Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> dh_testdir
> jh_build
> warning: [options] bootstrap class path not set in conjunction with -source 7
> ./src/java/org/tanukisoftware/wrapper/test/WrapperPrintParam.java:31: 
> warning: non-varargs call of varargs method with inexact argument type for 
> last parameter;
>  null );
>  ^
>   cast to Class for a varargs call
>   cast to Class[] for a non-varargs call and to suppress this warning
> ./src/java/org/tanukisoftware/wrapper/test/WrapperPrintParam.java:33: 
> warning: non-varargs call of varargs method with inexact argument type for 
> last parameter;
>   null );
>   ^
>   cast to Class for a varargs call
>   cast to Class[] for a non-varargs call and to suppress this warning
> ./src/java/org/tanukisoftware/wrapper/test/DeadLockBase.java:96: warning: 
> non-varargs call of varargs method with inexact argument type for last 
> parameter;
> rentrantLockClass.getMethod( "lock", null ).invoke( lock2,
>  ^
>   cast to Class for a varargs call
>   cast to Class[] for a non-varargs call and to suppress this warning
> ./src/java/org/tanukisoftware/wrapper/test/DeadLockBase.java:104: warning: 
> non-varargs call of varargs method with inexact argument type for last 
> parameter;
> rentrantLockClass.getMethod( "unlock", null ).invoke( 
> lock2,
>^
>   cast to Class for a varargs call
>   cast to Class[] for a non-varargs call and to suppress this warning
> ./src/java/org/tanukisoftware/wrapper/test/DeadLockBase.java:162: warning: 
> non-varargs call of varargs method with inexact argument type for last 
> parameter;
> rentrantLockClass.getMethod( "lock", null ).invoke( lock1,
>  ^
>   cast to Class for a varargs call
>   cast to Class[] for a non-varargs call and to suppress this warning
> ./src/java/org/tanukisoftware/wrapper/test/DeadLockBase.java:170: warning: 
> non-varargs call of varargs method with inexact argument type for last 
> parameter;
> rentrantLockClass.getMethod( "unlock", null ).invoke( 
> lock1,
>^
>   cast to Class for a varargs call
>   cast to Class[] for a non-varargs call and to suppress this warning
> Note: Some input files use or override a deprecated API.
> Note: Recompile with -Xlint:deprecation for details.
> Note: Some input files use unchecked or unsafe operations.
> Note: Recompile with -Xlint:unchecked for details.
> 7 warnings
> Creating destination directory: "debian/_jh_build.javadoc/api/"
> ./src/java/org/tanukisoftware/wrapper/WrapperListener.java:146: warning - 
> invalid usage of tag &
> ./src/java/org/tanukisoftware/wrapper/WrapperListener.java:146: warning - 
> invalid usage of tag &
> ./src/java/org/tanukisoftware/wrapper/WrapperListener.java:146: warning - 
> invalid usage of tag &
> ./src/java/org/tanukisoftware/wrapper/WrapperListener.java:146: warning - 
> invalid usage of tag &
> ./src/java/org/tanukisoftware/wrapper/WrapperListener.java:146: warning - 
> invalid usage of tag &
> ./src/java/org/tanukisoftware/wrapper/WrapperListener.java:146: warning - 
> invalid usage of tag &
> 

Bug#976915: marked as pending in service-wrapper-java

[Markus Koschany]

Control: tag -1 pending

Hello,

Bug #976915 in service-wrapper-java 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/java-team/service-wrapper-java/-/commit/65259fc6c8acfa889d7bd23f4597e7e3395f3469


Fix FTBFS on ppc64el and s390x.

Thanks: Logan Rosen and Dimitri John Ledkov for the patch.
Closes: #976915


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/976915

Processed: Bug#976915 marked as pending in service-wrapper-java

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #976915 [src:service-wrapper-java] service-wrapper-java: FTBFS on ppc64el:  
[exec] wrapper.c:(.text+0x3598): undefined reference to `pow'
Added tag(s) pending.

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

Bug#977423: maintainer address bounces

[Ansgar]

Hi,

On Tue, 15 Dec 2020 00:36:23 +0100 Michael Biebl wrote:
> I just tried to file a bug report against apt-listchanges and got this
> reply
> 
> Reporting-MTA: dns;VI1EUR04HT091.mail.protection.outlook.com
> Received-From-MTA: dns;DBAPR01MB7126.eurprd01.prod.exchangelabs.com
> Arrival-Date: Mon, 14 Dec 2020 23:33:24 +
> 
> Final-Recipient: rfc822;amdln...@googlemail.com
> Action: failed
> Status: 5.1.1
> Diagnostic-Code: smtp;550-5.1.1 The email account that you tried to reach 
> does not exist. Please try

I don't think this is the maintainer address, but someone being
subscribed to mailing lists and Microsoft's electronic telefax[1]
solution sending error messages to the address given in the "From"
header instead of the envelope address (which should be the mailing
list software).

ftpmaster got several bounces as well for mails sent to debian-devel-
changes@.

The error message from the telefax service should contain the original
message headers which should help finding out which Outlook address
produces the problem (e.g. X-MS-Exchange-Inbox-Rules-Loop and others)
and where they are subscribed (e.g. the mailing list in the "List-Id"
field or similar).

If the error messages are related to list mail, you should probably
contact listmaster@l.d.o; I've done so for the bounces I saw.

Ansgar

  [1]: It certainly doesn't seem to be normal email in many ways ;-)

Bug#973848: chromium: Unsupported version, many security bugs unfixed

[Michel Le Bihan]

Hello,

> I suspect that debian's libvpx might need to be build with
experimental features enabled (similar to a previous bug report), in
order to include the absent header files.

This will build the lib, but the header isn't correctly exported. They
don't export the header file for that and the internal header used by
Chromium requires many other internal headers.

> Are you sure that fixes/sequence-point.patch is necessary? I don't
recall getting any warnings related to this when compiling.

I don't know. I don't see the warning mentioned in the commit without
that patch, but I also don't see the commit in Chromium that could
change that.

> Looking at the last couple of commits for the file affected by the
ozone problem [1], it appears to be already fixed upstream.

Great! That will make one less patch to update on next release!

I'm still missing 4 patches:
buster/icu63: Without that one it might be difficult to get the update
in Buster
system/vpx: It's better to use system libs it it isn't too difficult.
There is one commit in Chromium introducing the usage of that
experimental feature. Maybe the patch could revert it?
system/harfbuzz: I didn't investigate what's wrong with it. Just used
in tree version.
A patch for proprietary codecs + system ffmpeg.

Maybe more will be needed for Lintian warnings and errors.

Does anybody have any of the mentioned patches updated/written? It
would avoid duplicate work. I know those are the most difficult patches
to update.

Michel Le Bihan

Bug#975533: [Pkg-privacy-maintainers] Bug#975533: mat2's autopkg tests fail with Python 3.9

[Georg Faerber]

Hi nicoo,

On 20-12-14 15:57:10, nicoo wrote:
> There doesn't seem to be anyone else handling the mat2 RC bug (FTBFS &
> autopkgtest failure) so I will do it.

I'm well aware and will handle this accordingly once there is a new
upstream release, which should happen soon.

Cheers,
Georg

Bug#971713: sysstat: init or systemd file has overlapping runlevels

[Robert Luberda]

Trek pisze:

Hi,

> 
> so the fix would be like the one attached to this mail

I've tried this update-rc.d -f sysstat command manually, and then I run
'apt install --reinstall sysstat', and as the result the warning about
default stop level is fixed, but the original warning about overlapping
run-levels is not.


>> insserv: Script ssh has overlapping Default-Start and Default-Stop
>> runlevels (2 3 4 5) and (2 3 4 5). This should be fixed.

What is surprising the ssh warning is shown even if I run insserv from
the command line without giving any other arguments:

robert@vox:/tmp$ sudo insserv
insserv: Script ssh has overlapping Default-Start and Default-Stop
runlevels (2 3 4 5) and (2 3 4 5). This should be fixed.
insserv: FATAL: service mountkernfs has to exist for service udev
insserv: FATAL: service mountdevsubfs has to exist for service hwclock
insserv: FATAL: service urandom has to exist for service networking
insserv: exiting now!

While the sysstat warning is shown only on upgrades.

Anyway I've just checked what the ssh links are:

robert@vox:/tmp$ sudo ls -la /etc/rc*.d/*ssh*
lrwxrwxrwx 1 root root 13 2017-03-27  /etc/rc2.d/K01ssh -> ../init.d/ssh
lrwxrwxrwx 1 root root 13 2017-03-27  /etc/rc3.d/K01ssh -> ../init.d/ssh
lrwxrwxrwx 1 root root 13 2017-03-27  /etc/rc4.d/K01ssh -> ../init.d/ssh
lrwxrwxrwx 1 root root 13 2017-03-27  /etc/rc5.d/K01ssh -> ../init.d/ssh

Removing the links removes the warning as well:

robert@vox:/tmp$ sudo update-rc.d -f ssh remove
insserv: Script ssh has overlapping Default-Start and Default-Stop
runlevels (2 3 4 5) and (2 3 4 5). This should be fixed.

robert@vox:/tmp$ sudo insserv
insserv: FATAL: service mountkernfs has to exist for service udev
insserv: FATAL: service mountdevsubfs has to exist for service hwclock
insserv: FATAL: service urandom has to exist for service networking
insserv: exiting now!

Even apt install --reinstall sysstat does not display any warning.

But when I re-add the K01ssh links, 'apt install --reinstall sysstat'
warns about ssh, and no longer about sysstat service...

Oh, wait, I've just read my email from Sunday, and it looks like the
warning on my system was always about ssh:
>> insserv: warning: current stop runlevel(s) (empty) of script
>>`sysstat' overrides LSB defaults (0 1 6).
>> insserv: Script ssh has overlapping Default-Start and Default-Stop
   ^^^
>> runlevels (2 3 4 5) and (2 3 4 5). This should be fixed.

Sorry about not noticing it before, I must have been too strongly
suggested by the Julian's original bug report :(

So it looks like the warning says that run-level links were customized
by a user. IMHO it would be nice if the warning message stated this
simple fact in a more explicit way.

> 
> this instead comes from ssh, that have an empty Default-Stop too
> 
> @Robert Luberda: I ran out of ideas, your script was correct with an
> empty Default-Stop field, like the ssh one!

I looked into insserv(8) man page before changing the script, and was
under impression that Default-Start and Default-Stop must contain at
least one run level, as the example given at the top of the man page says:

# Default-Start: run_level_1 [ run_level_2 ...]
# Default-Stop:  run_level_1 [ run_level_2 ...]


But if you're sure they can be empty, I will revert the change in
sysstat's init.d script.

Regards,
robert

Bug#971713: sysstat: init or systemd file has overlapping runlevels

[Trek]

On Mon, 14 Dec 2020 03:54:28 +0100
Lorenzo  wrote:

> if you are searching in the source under /debian directory, the code
> that you are looking for will be written by dh-installinit in place of
> the #DEBHEPLER# placeholder, during the build of the package.

@Lorenzo oh yeah, many thanks :)

so the fix would be like the one attached to this mail

but reading the init.d script I see that it does not stop anything, so
an empty Default-Stop should be correct

what I really don't understand now it's from where those messages come
from:

> insserv: Script sysstat has overlapping Default-Start and
> Default-Stop runlevels (2 3 4 5) and (2 3 4 5). This should be fixed.

running insserv on a script with an empty Default-Stop field does not
print this message, at least with buster and sid versions

reading the source, it could set an empty Default-Stop to the value of
Default-Start, but only when compiled with the -DSUSE flag enabled:

  https://sources.debian.org/src/insserv/1.21.0-1/insserv.c/#L3727

and this flag is not enabled on debian builds


> insserv: Script ssh has overlapping Default-Start and Default-Stop
> runlevels (2 3 4 5) and (2 3 4 5). This should be fixed.

this instead comes from ssh, that have an empty Default-Stop too

@Robert Luberda: I ran out of ideas, your script was correct with an
empty Default-Stop field, like the ssh one!

Actually I'm running a buster installation, but using the sid insserv
binary it does not show this issue, so I can't debug further for now

ciao!
diff --git a/debian/sysstat.postinst b/debian/sysstat.postinst
index f4730d0..3ea1596 100644
--- a/debian/sysstat.postinst
+++ b/debian/sysstat.postinst
@@ -114,6 +114,11 @@ if [ "$1" = "configure" ] ; then
 --slave /usr/share/man/man1/sar.1.gz sar.1.gz \
 /usr/share/man/man1/sar.sysstat.1.gz
 fi
+
+# new Default-Stop (see #971713)
+if dpkg --compare-versions "$2" le '12.4.1-2'; then
+update-rc.d -f sysstat remove
+fi
 fi
 
 #DEBHELPER#

Bug#977423: maintainer address bounces

[Michael Biebl]

Source: apt-listchanges
Severity: serious

I just tried to file a bug report against apt-listchanges and got this
reply

Reporting-MTA: dns;VI1EUR04HT091.mail.protection.outlook.com
Received-From-MTA: dns;DBAPR01MB7126.eurprd01.prod.exchangelabs.com
Arrival-Date: Mon, 14 Dec 2020 23:33:24 +

Final-Recipient: rfc822;amdln...@googlemail.com
Action: failed
Status: 5.1.1
Diagnostic-Code: smtp;550-5.1.1 The email account that you tried to reach does 
not exist. Please try
 550-5.1.1 double-checking the recipient's email address for typos or
 550-5.1.1 unnecessary spaces. Learn more at
 550 5.1.1  https://support.google.com/mail/?p=NoSuchUser w1si79431edl.297 - 
gsmtp
Remote-MTA: dns;mx.google.com



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

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

-- debconf information excluded

Processed: rust-sha1collisiondetection: FTBFS on architectures with unsigned char

[Debian Bug Tracking System]

Processing control commands:

> forwarded -1 https://gitlab.com/sequoia-pgp/sha1collisiondetection/-/issues/1
Bug #977421 [rust-sha1collisiondetection] rust-sha1collisiondetection: FTBFS on 
architectures with unsigned char
Warning: Unknown package 'rust-sha1collisiondetection'
Set Bug forwarded-to-address to 
'https://gitlab.com/sequoia-pgp/sha1collisiondetection/-/issues/1'.
Warning: Unknown package 'rust-sha1collisiondetection'

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

Bug#977421: rust-sha1collisiondetection: FTBFS on architectures with unsigned char

[Daniel Kahn Gillmor]

Package: rust-sha1collisiondetection
Version: 0.2.2-1
Severity: critical
Control: forwarded -1 
https://gitlab.com/sequoia-pgp/sha1collisiondetection/-/issues/1

Looks like rust-sha1collisiondetection code isn't as portable as
upstream expected it to be.  It is failing on platforms with an unsigned
char, with errors like:

~~~
error[E0308]: mismatched types
   --> lib/lib.rs:252:31
|
252 | ...   input.as_ptr() as *const i8,
|   ^^^ expected `u8`, found 
`i8`
|
= note: expected raw pointer `*const u8`
   found raw pointer `*const i8`
~~~

This means that the package fails to build from source on arm, powerpc,
riscv, and s390 architectures.

This is reported to upstream at
https://gitlab.com/sequoia-pgp/sha1collisiondetection/-/issues/1 so
hopefully they'll sort it out shortly.

 --dkg


signature.asc
Description: PGP signature

Processed: Re: Bug#976653: dfwinreg FTBFS: missing: pycreg

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + patch
Bug #976653 [src:dfwinreg] dfwinreg FTBFS: missing: pycreg
Added tag(s) patch.

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

Bug#976653: dfwinreg FTBFS: missing: pycreg

[Sergio Durigan Junior]

Control: tags -1 + patch
On Sunday, December 06 2020, Adrian Bunk wrote:

> https://buildd.debian.org/status/fetch.php?pkg=dfwinreg=all=20201006-1=1607180871=0
>
> ...
>debian/rules override_dh_auto_test
> make[1]: Entering directory '/<>'
> python3 run_tests.py
> Using Python version 3.9.1rc1 (default, Nov 27 2020, 19:38:39) 
> [GCC 10.2.0]
> Checking availability and versions of dependencies.
> [OK]  dfdatetime version: 20200824
> [OK]  dtfabric version: 20200621
> [FAILURE] missing: pycreg
> [OK]  pyregf version: 20201007
> [OK]  yaml version: 5.3.1
>
> make[1]: *** [debian/rules:20: override_dh_auto_test] Error 1

I tried opening an MR against the package, but the git repository is not
up-to-date.  I am therefore proposing the following debdiff here.  I've
uploaded it to DELAYED/5, just in case this bug doesn't get the
necessary attention.

Hilko or anyone from pkg-security, feel free to remove my upload and
prepare on yourselves, if you want :-).

Thanks,

-- 
Sergio
GPG key ID: 237A 54B1 0287 28BF 00EF  31F4 D0EB 7628 65FC 5E36
Please send encrypted e-mail if possible
https://sergiodj.net/

diff -Nru dfwinreg-20201006/debian/changelog dfwinreg-20201006/debian/changelog
--- dfwinreg-20201006/debian/changelog  2020-12-05 08:36:37.0 -0500
+++ dfwinreg-20201006/debian/changelog  2020-12-14 17:14:54.0 -0500
@@ -1,3 +1,11 @@
+dfwinreg (20201006-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * B-D on python3-libcreg, which solves a FTBFS during testing.
+  (Closes: #976653)
+
+ -- Sergio Durigan Junior   Mon, 14 Dec 2020 17:14:54 
-0500
+
 dfwinreg (20201006-1) unstable; urgency=medium
 
   [ Samuel Henrique ]
diff -Nru dfwinreg-20201006/debian/control dfwinreg-20201006/debian/control
--- dfwinreg-20201006/debian/control2020-12-05 08:36:37.0 -0500
+++ dfwinreg-20201006/debian/control2020-12-14 17:14:08.0 -0500
@@ -12,6 +12,7 @@
  python3-mock,
  python3-six (>= 1.1.0),
  python3-yaml (>= 3.10),
+ python3-libcreg ,
 Standards-Version: 4.3.0
 Homepage: https://github.com/log2timeline/dfwinreg
 Vcs-Git: https://salsa.debian.org/pkg-security-team/dfwinreg.git


signature.asc
Description: PGP signature

Processed: Re: nomacs: "charset=Ascii" appears before the comment of the image

[Debian Bug Tracking System]

Processing control commands:

> retitle -1 nomacs uses internal libexiv2 functions to get the user comment
Bug #974616 [nomacs] nomacs: "charset=Ascii" or "charset=Unicode" appears 
before the "User Comment" metadata of the image
Changed Bug title to 'nomacs uses internal libexiv2 functions to get the user 
comment' from 'nomacs: "charset=Ascii" or "charset=Unicode" appears before the 
"User Comment" metadata of the image'.
> severity -1 serious
Bug #974616 [nomacs] nomacs uses internal libexiv2 functions to get the user 
comment
Severity set to 'serious' from 'minor'
> tags -1 - patch
Bug #974616 [nomacs] nomacs uses internal libexiv2 functions to get the user 
comment
Removed tag(s) patch.

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

Processed: Re: gthumb uses internal libexiv2 functions

[Debian Bug Tracking System]

Processing control commands:

> retitle -1 gthumb uses internal libexiv2 functions to get the user comment
Bug #974608 [gthumb] gthumb: "charset=Ascii" appears before the comment of the 
image
Changed Bug title to 'gthumb uses internal libexiv2 functions to get the user 
comment' from 'gthumb: "charset=Ascii" appears before the comment of the image'.

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

Bug#974608: gthumb uses internal libexiv2 functions

[Vincent Lefevre]

Control: retitle -1 gthumb uses internal libexiv2 functions to get the user 
comment

The bug should be retitled accordingly.

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

Processed: gthumb uses internal libexiv2 functions

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #974608 [gthumb] gthumb: "charset=Ascii" appears before the comment of the 
image
Severity set to 'serious' from 'normal'

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

Bug#962203: NMU

[Calum McConnell]

I have prepared an NMU for this package.  It is currently at
https://mentors.debian.net/package/debdelta/ .  While I need a sponsor to
get it into Debian, I am now reaching out to ment...@lists.debian.org to
see if I can expedite the process.


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

Bug#973033: marked as done (python-molotov's autopkg tests are failing with python3.9)

[Debian Bug Tracking System]

Your message dated Mon, 14 Dec 2020 22:18:54 +
with message-id 
and subject line Bug#973033: fixed in python-molotov 2.1-1
has caused the Debian Bug report #973033,
regarding python-molotov's autopkg tests are failing with python3.9
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.)


-- 
973033: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973033
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:python-molotov
Version: 1.6-7
Severity: serious
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: python3.9

see
https://ci.debian.net/data/autopkgtest/testing/amd64/p/python-molotov/7759352/log.gz
--- End Message ---
--- Begin Message ---
Source: python-molotov
Source-Version: 2.1-1
Done: Emmanuel Arias 

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

Debian distribution maintenance software
pp.
Emmanuel Arias  (supplier of updated python-molotov 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, 14 Dec 2020 16:13:35 -0300
Source: python-molotov
Architecture: source
Version: 2.1-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team 
Changed-By: Emmanuel Arias 
Closes: 973033
Changes:
 python-molotov (2.1-1) unstable; urgency=medium
 .
   * Team upload.
 .
   [ Ondřej Nový ]
   * d/control: Update Maintainer field with new Debian Python Team
 contact address.
   * d/control: Update Vcs-* fields with new Debian Python Team Salsa
 layout.
 .
   [ Emmanuel Arias ]
   * New upstream version 2.1 (Closes: #973033).
   * d/patches: Update patches.
 - Remove already patch applied for usptream.
   * d/salsa-ci.yml: enable salsa-ci.
   * d/watch: bump version to 4 (from 3).
Checksums-Sha1:
 cd2be09c1342ae41df98b2158a859621e546742d 2255 python-molotov_2.1-1.dsc
 38a8fd43145e55bf4698d6053d59946663719a4d 38967 python-molotov_2.1.orig.tar.gz
 73cae0fa0596baabbf83b991e20f6db0438a050f 3880 
python-molotov_2.1-1.debian.tar.xz
 6f3d739ee1078b2c248193b8410f3690fbcec688 7555 
python-molotov_2.1-1_source.buildinfo
Checksums-Sha256:
 561344c4d31192b4a173ed681c3bd598979e93c7d28a6adc3a34f6a9869af8c6 2255 
python-molotov_2.1-1.dsc
 3b0b58f32665c1a92dd153cacbcc98dbf8080f7685a4955290eac29b615457a2 38967 
python-molotov_2.1.orig.tar.gz
 a0063c6e5e2f9de8fd30260acb7c2b6760b527159f9cd1ba4bf2e48b67c920ad 3880 
python-molotov_2.1-1.debian.tar.xz
 08c5f8a3ba1a99fb85e194e1a3293dcc8b78ad5052b5ff537035cd815539bca6 7555 
python-molotov_2.1-1_source.buildinfo
Files:
 b481466d384b568c54dc35e25f05101b 2255 python optional python-molotov_2.1-1.dsc
 f6164dc7546d44032bda301c4c3d951d 38967 python optional 
python-molotov_2.1.orig.tar.gz
 aa215cb945f922ef576663f8515047d8 3880 python optional 
python-molotov_2.1-1.debian.tar.xz
 615c2862990e4e40d6dc2ba747c1e400 7555 python optional 
python-molotov_2.1-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJEBAEBCAAuFiEE1WVxuIqLuvFAv2PWvX6qYHePpvUFAl/X3g4QHGRva29AZGVi
aWFuLm9yZwAKCRC9fqpgd4+m9Si/D/4/+p2yJof90T+XqdYMdhEwUM62Bs/fkIro
uHMi4x0Uan1J0OluzLkhFgnGCLztQk/DWS/en+hSAjUJPjO4+DJBPU3wH5zyhzXc
3Ld0BszflR6UgG5i8+C6BHExQSiLr4DaHxJSRq0h6J8kSNxRnDg7QluBBesQtXmA
dL8A+wKVyHEsUAi/3nZofiBkHLXkf4FAdESkNGxY+gMKPuMibV37847j/ZZlRAO2
ttqHGE4gPx1gofAwlu2bNW9s4WA0dAVHJx5iOWZE29PKEC133EEEVlx6rBJVOyd9
Rfzm+fXBj/+Nn8yalrrkrLIoG2cnXU3fX2zj6h73MNhAr0HlXP79kNu7hdYKkMhx
p2SF7LjcjLpP1JuRqnIPTIlx00GWsmvqZ2Bdc2zuFBhvAChtwxyduJY5h6HQ1klY
Yv2PPCBNWnbC8FPAyJElVQ79PuJAFW15TyYpjV37BJUafWArOfVA3o90CbcLO99O
9ioDZRu2L77jzcbC2gtjBnP+gyJDh2P+MUYyuYWAlpG13NmVGkoKHkTD1l6m7D94
r8w+H/Didh+DiTeOTGO0EuOZymswiMGldyCp3hRuw2Yy3V3VvtPfwJmrmoUZJM02
HAH6Ga2cXhseG7EWGPO793gKd1gAy7FlPHzRIQKXK+9OBeH4Prr4cKcpxkGKxb1I
i1Lsx9oKXA==
=8fTX
-END PGP SIGNATURE End Message ---

Bug#976535: marked as done (nickle: FTBFS: latex errors)

[Debian Bug Tracking System]

Your message dated Mon, 14 Dec 2020 22:06:40 +
with message-id 
and subject line Bug#976535: fixed in nickle 2.88
has caused the Debian Bug report #976535,
regarding nickle: FTBFS: latex errors
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.)


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

Hi,

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

Relevant part (hopefully):
> make[4]: Entering directory '/<>/doc/tutorial'
> docbook2tex nickle-tutorial.sgml && \
> pdfjadetex '\pdfinfo{/CreationDate(Tue Sep  1 00:00:00 UTC 2020)/ModDate(Tue 
> Sep  1 00:00:00 UTC 2020)}\input{nickle-tutorial.tex}' >/dev/null && \
> pdfjadetex '\pdfinfo{/CreationDate(Tue Sep  1 00:00:00 UTC 2020)/ModDate(Tue 
> Sep  1 00:00:00 UTC 2020)}\input{nickle-tutorial.tex}' >/dev/null && \
> pdfjadetex '\pdfinfo{/CreationDate(Tue Sep  1 00:00:00 UTC 2020)/ModDate(Tue 
> Sep  1 00:00:00 UTC 2020)}\input{nickle-tutorial.tex}' >/dev/null && \
> sed -i '/^\/ID \[<[0-9A-F][0-9A-F]*> <[0-9A-F][0-9A-F]*>\]/d' 
> nickle-tutorial.pdf && \
> rm nickle-tutorial.aux nickle-tutorial.log *out *tex
> Using catalogs: /etc/sgml/catalog
> Using stylesheet: /usr/share/docbook-utils/docbook-utils.dsl#print
> Working on: /<>/doc/tutorial/nickle-tutorial.sgml
> Done.
> make[4]: *** [Makefile:487: nickle-tutorial.pdf] Error 1

The full build log is available from:
   http://qa-logs.debian.net/2020/12/05/nickle_2.87_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: nickle
Source-Version: 2.88
Done: Keith Packard 

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

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

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

Debian distribution maintenance software
pp.
Keith Packard  (supplier of updated nickle 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, 14 Dec 2020 13:28:22 -0800
Source: nickle
Architecture: source
Version: 2.88
Distribution: unstable
Urgency: medium
Maintainer: Keith Packard 
Changed-By: Keith Packard 
Closes: 976535
Changes:
 nickle (2.88) unstable; urgency=medium
 .
   * Switch tutorial to asciidoctor. Closes: #976535.
Checksums-Sha1:
 a3761008ccaad6bde2b5ee1254dab02c4fcf0767 1492 nickle_2.88.dsc
 7aaa7b2d18cdd6d9309586f9f8432acd48c1ae41 478296 nickle_2.88.tar.xz
 0d8d3112a156c18c3007e81ced773704daed9dfc 7508 nickle_2.88_amd64.buildinfo
Checksums-Sha256:
 49f699a9484ab48a13ceaa11dcecc725becec1ff86e26703c05a81433b932202 1492 
nickle_2.88.dsc
 8bc51826f0ec12585a8b2b015532c8eca94b89ea4a575c163d1becbf693279d3 478296 
nickle_2.88.tar.xz
 a1e369ca8c21b5f0c75f8a1f65024ea397bee5ad2c949db1ac99cfe051a2fde0 7508 
nickle_2.88_amd64.buildinfo
Files:
 409450b9cc84225988acad876b817c56 1492 interpreters optional nickle_2.88.dsc
 e1f42a1436be08fbdfdad9e051f86a62 478296 interpreters optional 
nickle_2.88.tar.xz
 b41f122a69069625a3cbce52842923d6 7508 interpreters optional 
nickle_2.88_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEw4O3eCVWE9/bQJ2R2yIaaQAAABEFAl/X3j4ACgkQ2yIaaQAA
ABHFhA//f+iwD37n8curCtpBwk5JG5ZYpzajttxiNVcohtM+NXXw1gZpXP+RTBwB
q8lH7MXbw/wxlPPO0LL9O4RoEZeRlejVVfxpl2W2CO0kn7imu2wxNoZMAFFCw7B0

Bug#956776: marked as done (osdlyrics: Depends on deprecated libappindicator)

[Debian Bug Tracking System]

Your message dated Mon, 14 Dec 2020 22:06:47 +
with message-id 
and subject line Bug#956776: fixed in osdlyrics 0.5.5~rc2+dfsg1-2
has caused the Debian Bug report #956776,
regarding osdlyrics: Depends on deprecated libappindicator
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.)


-- 
956776: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=956776
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: osdlyrics
Version: 0.5.5~rc1+dfsg1-2
Tags: sid bullseye
Severity: important
Control: block 895037 by -1
User: pkg-ayatana-de...@lists.alioth.debian.org
Usertags: ayatana-appindicator

This package Build-Depends on libappindicator-dev, which is
deprecated and unmaintained. The supported replacement appears to be
libayatana-appindicator-dev.

Please see #895037 and
https://wiki.debian.org/Ayatana/IndicatorsTransition for more details
of this deprecation.

This bug might get escalated to 'serious' severity (making it
release-critical) if the maintainers of the Ayatana stack are serious about
getting libappindicator removed from Debian before bullseye.

smcv
--- End Message ---
--- Begin Message ---
Source: osdlyrics
Source-Version: 0.5.5~rc2+dfsg1-2
Done: Boyuan Yang 

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

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

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

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 12 Dec 2020 23:38:40 -0500
Source: osdlyrics
Architecture: source
Version: 0.5.5~rc2+dfsg1-2
Distribution: unstable
Urgency: medium
Maintainer: Boyuan Yang 
Changed-By: Boyuan Yang 
Closes: 956776
Changes:
 osdlyrics (0.5.5~rc2+dfsg1-2) unstable; urgency=medium
 .
   * debian/control: Drop obsolete libappindicator support.
 (Closes: #956776)
   * Add patch to fix upstream issue 48.
   * Bump Standards-Version to 4.5.1.
Checksums-Sha1:
 66a77397a02e35525f965f9794bf2975f1fbeed5 2038 osdlyrics_0.5.5~rc2+dfsg1-2.dsc
 9f1b03ebc04ac91e1e231a830dcf359f304dc717 533722 
osdlyrics_0.5.5~rc2+dfsg1.orig.tar.gz
 2a76633856e19319c4d08fac601ece8d0db07c63 5068 
osdlyrics_0.5.5~rc2+dfsg1-2.debian.tar.xz
 67fb2487cc8d841e41be83c6233a5a802b269748 12369 
osdlyrics_0.5.5~rc2+dfsg1-2_amd64.buildinfo
Checksums-Sha256:
 05b8a7cdba1217fe1c1ee7c93e8df7fb970a4278161d195696b5a2e98f1e4343 2038 
osdlyrics_0.5.5~rc2+dfsg1-2.dsc
 06d0578f2b8c470105fca44bf07e4757c3567cd7f26694c6b93bc944e6cefeda 533722 
osdlyrics_0.5.5~rc2+dfsg1.orig.tar.gz
 a51b41e1a2fcf8ee8b3bbe00a67617d61413d43aed3589c678a62667df8b8a77 5068 
osdlyrics_0.5.5~rc2+dfsg1-2.debian.tar.xz
 1fb8ad98714b44a2aa4c77ff7ba664454e4e14fb52618d22398381c5e173561c 12369 
osdlyrics_0.5.5~rc2+dfsg1-2_amd64.buildinfo
Files:
 69532642ef87141126e00ef5464e40f2 2038 utils optional 
osdlyrics_0.5.5~rc2+dfsg1-2.dsc
 e609c2615db1382308a2b76f17348267 533722 utils optional 
osdlyrics_0.5.5~rc2+dfsg1.orig.tar.gz
 cb4210fc2fbbb40751e7f06adedcb6ff 5068 utils optional 
osdlyrics_0.5.5~rc2+dfsg1-2.debian.tar.xz
 b8ee9d45631f66e03c2251846bcc0ca4 12369 utils optional 
osdlyrics_0.5.5~rc2+dfsg1-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEfncpR22H1vEdkazLwpPntGGCWs4FAl/X26EACgkQwpPntGGC
Ws4o/A//cRLqKdghn01kOzUUYtTdXXxU764PHjhHhnsiZ/xqXDdaKAPi2HHu5O2J
BHw7gqhgmeixU2EP3JBEl/u/FyTg4juh94kieS1wAbHEHD2Q3NdH10gSwHhl3MII
fSkIWyy00iD8ytzvnu00rhJaT2LETV58I5IkLHQAmmX5sdX/TSVpHWxaM9WvbDDW
fbaW5cQDH15NqBs/3NkNTmaewkTqbfXGOdZhuwNz+bQaB0/u5eIeGHt1j9Ek0rBu
SLflfL/vaolzCtQt3GNc7zMkFG3Lu4hMkAceo3C+Vfly1iR5HyR7yw+Z/eBkZBQN
Pgzk3I8fHHKlYstyiLTT8BrJhszvlfRu7feGWbPyaN0enyspwuVsyS81J49IiGI/
CA+8Plsho3yH6E6ehe+aXrxL0x7zQlM/e/k4ACBJ9eLnhFu+BFUHDx7K99WOxShx
irPW6hoSLRYJW+6nXSysF7NWVhiJ64rMEaktjvlpOmiMAZNpAbvgaavdwbWHpjUv
IJ0Rp2DEI+x1JezXmFo4XdPYaKaLvsif2xxMv9D1f76NZPkFEyQutkIsm+p/gMJM
lB+RVU9CXysrLIShJaYq15v9+cPpkBNBLDEaPe74Gk3eMVYN7Muyt4D+PU+azksa
0/vbak5HkA8yr47BI6Ya6EgwN+0UYNH+4zDfNm53v1ahQRRtvGY=
=s7b+
-END PGP SIGNATURE End Message ---

Bug#977349: marked as done (Current package does not ensure a smooth upgrade from stable due to breakage of past config and new binary modules.)

[Debian Bug Tracking System]

Your message dated Mon, 14 Dec 2020 22:00:14 +
with message-id 
and subject line Bug#977349: fixed in proftpd-dfsg 1.3.7a+dfsg-3
has caused the Debian Bug report #977349,
regarding Current package does not ensure a smooth upgrade from stable due to 
breakage of past config and new binary modules.
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.)


-- 
977349: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977349
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: proftpd-dfsg
Version: 1.3.7a+dfsg-2
Severity: serious

After upgrade:

$ sudo proftpd -t
Checking syntax of configuration file
2020-12-14 09:59:09,942 legolas proftpd[5444]: mod_dso/0.5: unable to load 
'mod_tls.c'; check to see if '/usr/lib/proftpd/mod_tls.la' exists
2020-12-14 09:59:09,942 legolas proftpd[5444]: fatal: LoadModule: error loading 
module 'mod_tls.c': No such file or directory on line 22 of 
'/etc/proftpd/modules.conf'
2020-12-14 09:59:09,942 legolas proftpd[5444]: warning: unable to include 
'/etc/proftpd/modules.conf': Operation not permitted
2020-12-14 09:59:09,943 legolas proftpd[5444]: mod_dso/0.5: unable to load 
'mod_wrap.c'; check to see if '/usr/lib/proftpd/mod_wrap.la' exists
2020-12-14 09:59:09,943 legolas proftpd[5444]: fatal: LoadModule: error loading 
module 'mod_wrap.c': No such file or directory on line 8 of 
'/etc/proftpd/proftpd.conf'

That's due to mod_wrap and mod_tls move to distinct binaries in the new
version of the package. A transitional package is required, the same problem
is expected in dist-upgrade from stable.

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

Kernel: Linux 4.19.0-12-amd64 (SMP w/32 CPU cores)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8), 
LANGUAGE=it_IT.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
--- End Message ---
--- Begin Message ---
Source: proftpd-dfsg
Source-Version: 1.3.7a+dfsg-3
Done: Francesco Paolo Lovergine 

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

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

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

Debian distribution maintenance software
pp.
Francesco Paolo Lovergine  (supplier of updated 
proftpd-dfsg 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, 14 Dec 2020 16:12:56 +0100
Source: proftpd-dfsg
Binary: proftpd-basic proftpd-core proftpd-core-dbgsym proftpd-dev proftpd-doc 
proftpd-mod-crypto proftpd-mod-crypto-dbgsym proftpd-mod-geoip 
proftpd-mod-geoip-dbgsym proftpd-mod-ldap proftpd-mod-ldap-dbgsym 
proftpd-mod-mysql proftpd-mod-mysql-dbgsym proftpd-mod-odbc 
proftpd-mod-odbc-dbgsym proftpd-mod-pgsql proftpd-mod-pgsql-dbgsym 
proftpd-mod-snmp proftpd-mod-snmp-dbgsym proftpd-mod-sqlite 
proftpd-mod-sqlite-dbgsym proftpd-mod-wrap proftpd-mod-wrap-dbgsym
Architecture: source all amd64
Version: 1.3.7a+dfsg-3
Distribution: unstable
Urgency: medium
Maintainer: ProFTPD Maintainance Team 

Changed-By: Francesco Paolo Lovergine 
Description:
 proftpd-basic - Transitional dummy package for ProFTPD
 proftpd-core - Versatile, virtual-hosting FTP daemon - binaries
 proftpd-dev - Versatile, virtual-hosting FTP daemon - development files
 proftpd-doc - Versatile, virtual-hosting FTP daemon - documentation
 proftpd-mod-crypto - Versatile, virtual-hosting FTP daemon - TLS/SSL/SFTP 
modules
 proftpd-mod-geoip - Versatile, virtual-hosting FTP daemon - GeoIP module
 proftpd-mod-ldap - Versatile, virtual-hosting FTP daemon - LDAP module
 proftpd-mod-mysql - Versatile, virtual-hosting FTP daemon - MySQL module
 proftpd-mod-odbc - Versatile, virtual-hosting FTP daemon - ODBC module
 proftpd-mod-pgsql - Versatile, virtual-hosting FTP daemon - PostgreSQL module
 proftpd-mod-snmp - Versatile, virtual-hosting FTP daemon - SNMP module
 proftpd-mod-sqlite - Versatile, virtual-hosting FTP daemon - SQLite3 

Bug#957378: isoqlog: diff for NMU version 2.2.1-9.1

[Sudip Mukherjee]

Control: tags 957378 + patch
Control: tags 957378 + pending
--

Dear maintainer,

I've prepared an NMU for isoqlog (versioned as 2.2.1-9.1) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should cancel it.

--
Regards
Sudip

diff -Nru isoqlog-2.2.1/debian/changelog isoqlog-2.2.1/debian/changelog
--- isoqlog-2.2.1/debian/changelog  2013-12-30 07:10:08.0 +
+++ isoqlog-2.2.1/debian/changelog  2020-12-14 21:55:29.0 +
@@ -1,3 +1,11 @@
+isoqlog (2.2.1-9.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix ftbfs with GCC-10. (Closes: #957378)
+- Add -fcommon to CFLAGS.
+
+ -- Sudip Mukherjee   Mon, 14 Dec 2020 21:55:29 
+
+
 isoqlog (2.2.1-9) unstable; urgency=low
 
   * Fixes wrong langfile after non-interactive install (Closes: #670225)
diff -Nru isoqlog-2.2.1/debian/rules isoqlog-2.2.1/debian/rules
--- isoqlog-2.2.1/debian/rules  2012-04-24 00:45:27.0 +0100
+++ isoqlog-2.2.1/debian/rules  2020-12-14 21:53:44.0 +
@@ -20,6 +20,8 @@
 ifneq (,$(findstring debug,$(DEB_BUILD_OPTIONS)))
CFLAGS += -g
 endif
+CFLAGS += -fcommon
+
 ifeq (,$(findstring nostrip,$(DEB_BUILD_OPTIONS)))
INSTALL_PROGRAM += -s
 endif

Processed: isoqlog: diff for NMU version 2.2.1-9.1

[Debian Bug Tracking System]

Processing control commands:

> tags 957378 + patch
Bug #957378 [src:isoqlog] isoqlog: ftbfs with GCC-10
Added tag(s) patch.
> tags 957378 + pending
Bug #957378 [src:isoqlog] isoqlog: ftbfs with GCC-10
Added tag(s) pending.

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

Bug#936604: marked as done (getmail: Python2 removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Mon, 14 Dec 2020 21:39:05 +
with message-id 
and subject line Bug#977291: Removed package(s) from unstable
has caused the Debian Bug report #936604,
regarding getmail: Python2 removal in sid/bullseye
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.)


-- 
936604: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936604
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:getmail
Version: 5.13-1
Severity: normal
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: py2removal

Python2 becomes end-of-live upstream, and Debian aims to remove
Python2 from the distribution, as discussed in
https://lists.debian.org/debian-python/2019/07/msg00080.html

Your package either build-depends, depends on Python2, or uses Python2
in the autopkg tests.  Please stop using Python2, and fix this issue
by one of the following actions.

- Convert your Package to Python3. This is the preferred option.  In
  case you are providing a Python module foo, please consider dropping
  the python-foo package, and only build a python3-foo package.  Please
  don't drop Python2 modules, which still have reverse dependencies,
  just document them.
  
  This is the preferred option.

- If the package is dead upstream, cannot be converted or maintained
  in Debian, it should be removed from the distribution.  If the
  package still has reverse dependencies, raise the severity to
  "serious" and document the reverse dependencies with the BTS affects
  command.  If the package has no reverse dependencies, confirm that
  the package can be removed, reassign this issue to ftp.debian.org,
  make sure that the bug priority is set to normal and retitle the
  issue to "RM: PKG -- removal triggered by the Python2 removal".

- If the package has still many users (popcon >= 300), or is needed to
  build another package which cannot be removed, document that by
  adding the "py2keep" user tag (not replacing the py2remove tag),
  using the debian-pyt...@lists.debian.org user.  Also any
  dependencies on an unversioned python package (python, python-dev)
  must not be used, same with the python shebang.  These have to be
  replaced by python2/python2.7 dependencies and shebang.

  This is the least preferred option.

If the conversion or removal needs action on another package first,
please document the blocking by using the BTS affects command, like

  affects  + src:getmail

If there is no py2removal bug for that reverse-dependency, please file
a bug on this package (similar to this bug report).

If there are questions, please refer to the wiki page for the removal:
https://wiki.debian.org/Python/2Removal, or ask for help on IRC
#debian-python, or the debian-pyt...@lists.debian.org mailing list.
--- End Message ---
--- Begin Message ---
Version: 5.13-1+rm

Dear submitter,

as the package getmail has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/977291

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

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

Debian distribution maintenance software
pp.
Joerg Jaspert (the ftpmaster behind the curtain)--- End Message ---

Bug#974061: marked as done (postgresql-12 should not be part of the next release, remove from testing)

[Debian Bug Tracking System]

Your message dated Mon, 14 Dec 2020 21:38:29 +
with message-id 
and subject line Bug#977289: Removed package(s) from unstable
has caused the Debian Bug report #974061,
regarding postgresql-12 should not be part of the next release, remove from 
testing
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.)


-- 
974061: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=974061
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: postgresql-12
Version: 12.4-3
Severity: serious
Justification: ftbfs
Tags: ftbfs
User: debian-p...@lists.debian.org
Usertags: perl-5.32-transition
Control: block 968912 with -1

postgresql-12 FTBFS on multiple archs, eg:

https://buildd.debian.org/status/fetch.php?pkg=postgresql-12=amd64=12.4-3%2Bb1=1604914304=0

2020-11-09 09:31:39.067 UTC [386] LOG:  received fast shutdown request
2020-11-09 09:31:39.067 UTC [386] LOG:  aborting any active transactions
2020-11-09 09:31:39.070 UTC [386] LOG:  background worker "logical replication 
launcher" (PID 395) exited with exit code 1
2020-11-09 09:31:39.073 UTC [390] LOG:  shutting down
2020-11-09 09:31:39.073 UTC [390] LOG:  checkpoint starting: shutdown immediate
2020-11-09 09:31:39.185 UTC [390] LOG:  checkpoint complete: wrote 10234 
buffers (62.5%); 0 WAL file(s) added, 0 removed, 13 recycled; write=0.092 s, 
sync=0.000 s, total=0.111 s; sync files=0, longest=0.000 s, average=0.000 s; 
distance=206300 kB, estimate=206300 kB
2020-11-09 09:31:39.206 UTC [386] LOG:  database system is shut down
make[1]: *** [debian/rules:196: override_dh_auto_test-arch] Error 1
make[1]: Leaving directory '/<>'
make: *** [debian/rules:95: build-arch] Error 2
dpkg-buildpackage: error: debian/rules build-arch subprocess returned exit 
status 2

FWIW, 12.4-1 did not fail on our test rebuilds in September:

http://perl.debian.net/rebuild-logs/perl-5.32-throwaway/postgresql-12_12.4-1/postgresql-12_12.4-1_amd64.build

Please could you take a look?

Cheers
Dominic
--- End Message ---
--- Begin Message ---
Version: 12.4-3+rm

Dear submitter,

as the package postgresql-12 has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/977289

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

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

Debian distribution maintenance software
pp.
Joerg Jaspert (the ftpmaster behind the curtain)--- End Message ---

Bug#975548: marked as done (mariadb-10.3_10.3.27-1~exp1_all.changes REJECTED])

[Debian Bug Tracking System]

Your message dated Mon, 14 Dec 2020 21:38:03 +
with message-id 
and subject line Bug#977254: Removed package(s) from unstable
has caused the Debian Bug report #975548,
regarding mariadb-10.3_10.3.27-1~exp1_all.changes REJECTED]
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.)


-- 
975548: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=975548
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: mariadb-10.3
Version: 10.3.27-1~exp1
Severity: serious

- Forwarded message from Debian FTP Masters 
 -

From: Debian FTP Masters 
To: all Build Daemon 
Date: Mon, 23 Nov 2020 11:20:26 +
Subject: mariadb-10.3_10.3.27-1~exp1_all.changes REJECTED
Message-Id: 



Version check failed:
Your upload included the binary package mariadb-client, version 
1:10.3.27-1~exp1, for all,
however unstable already has version 1:10.5.8-2.
Uploads to experimental must have a higher version than present in unstable.



===

Please feel free to respond to this email if you don't understand why
your files were rejected, or if you upload new files which address our
concerns.




- End forwarded message -
--- End Message ---
--- Begin Message ---
Version: 1:10.3.24-2+rm

Dear submitter,

as the package mariadb-10.3 has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/977254

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

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

Debian distribution maintenance software
pp.
Joerg Jaspert (the ftpmaster behind the curtain)--- End Message ---

Bug#961982: marked as done (node-request-promise: deprecated upstream: should not be part of next stable Debian release)

[Debian Bug Tracking System]

Your message dated Mon, 14 Dec 2020 21:36:01 +
with message-id 
and subject line Bug#977059: Removed package(s) from unstable
has caused the Debian Bug report #961982,
regarding node-request-promise: deprecated upstream: should not be part of next 
stable Debian release
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.)


-- 
961982: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=961982
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: node-request
Version: 2.88.1-4
Severity: grave
Justification: renders package unusable

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Upstream has deprecated this module:
https://github.com/request/request/issues/3142

It already has seen no new updates for a year,
and is not expected to do so:
This module is unsuitable for next stable Debian release!

Upstream issue discusses alternatives to use instead.


 - Jonas

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAl6Q6LkACgkQLHwxRsGg
ASHgqg/9FXRMJxxxpyv7BZHDM+dj3CMBHCHqjd29i+I3kyHND8HBe4sncafdXN9/
0gAQsxtG3Ad81jqY0gGV2wMTf7jMQUGnF4F58TJCbZXcsDehfb4DGjTT4Z20rEoA
bd+pc8uMEojCYq+/Qd8yw9FW/MUgFmNEjZBG6MSM9O4QhxHEfVL4HlERK+DR+wok
f5WyvIfQrx5jlpiXcIT+mA0WmbI+kYqCnfF8zf09q2R1uMLr1XgRVkCei1BXI51d
PgLFWVgLXDshHJJJ2S/DNCdPRaW6vB0U9v31slnZcGgPuMvyz8rXuZqI8VlcaPo5
DAIAeJBV0ZLZx+gM1gxcYZdmoDB1OOvyTmSKkDb7axoiFLQZCScou+XMCCSP2QNW
NknuCkVphX4t4iNIgBZbypm4vw3xRyBJq+tdD3G4A1Myy/52ItXiPfx0GfgtuQsQ
OnNUceTZcYr/qHqptnxvRQ09yBQWQhuckkbVWWEddHIUJohlDs1M3Tjpu71rdULc
O85hZHZX/hUN0vyPBKfDTO7zlQJxpwyYYuVniRN7PQNLa3sY/En3cUZ6sQNTKKwM
JbG+Jxw4pHao7M6tYHslaTX19rh6QvLcCZI7526Qm2Ktc9Oi6VoP/5b14UzLIbdB
fPrPcnFRuY6ymbtGb27zqq+7ww2r2MWnRqVR1E8kNLY2Zrg8blM=
=nQxC
-END PGP SIGNATURE-
--- End Message ---
--- Begin Message ---
Version: 4.2.5-2+rm

Dear submitter,

as the package node-request-promise has just been removed from the Debian 
archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/977059

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

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

Debian distribution maintenance software
pp.
Joerg Jaspert (the ftpmaster behind the curtain)--- End Message ---

Bug#925546: marked as done (panic: Can't find the package clause)

[Debian Bug Tracking System]

Your message dated Mon, 14 Dec 2020 21:34:11 +
with message-id 
and subject line Bug#976642: Removed package(s) from unstable
has caused the Debian Bug report #925546,
regarding panic: Can't find the package clause
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.)


-- 
925546: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925546
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gocode
Version: 20150303-3+b1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

The gocode server only returns "PANIC" autocompletion because of the
following panic:

panic: Can't find the package clause
1(runtime.call32): /usr/lib/go-1.7/src/runtime/asm_amd64.s:479
2(runtime.gopanic): /usr/lib/go-1.7/src/runtime/panic.go:458
3(main.(*package_file_cache).process_package_data): 
/build/gocode-WMuvMl/gocode-20150303/obj-x86_64-linux-gnu/src/github.com/nsf/gocode/package.go:108
4(main.(*package_file_cache).update_cache): 
/build/gocode-WMuvMl/gocode-20150303/obj-x86_64-linux-gnu/src/github.com/nsf/gocode/package.go:91
5(main.update_packages.func1): 
/build/gocode-WMuvMl/gocode-20150303/obj-x86_64-linux-gnu/src/github.com/nsf/gocode/autocompletecontext.go:332
6(runtime.goexit): /usr/lib/go-1.7/src/runtime/asm_amd64.s:2086

panic: One of the package cache updaters panicked
1(runtime.call32): /usr/lib/go-1.7/src/runtime/asm_amd64.s:479
2(runtime.gopanic): /usr/lib/go-1.7/src/runtime/panic.go:458
3(main.update_packages): 
/build/gocode-WMuvMl/gocode-20150303/obj-x86_64-linux-gnu/src/github.com/nsf/gocode/autocompletecontext.go:340
4(main.(*auto_complete_context).update_caches): 
/build/gocode-WMuvMl/gocode-20150303/obj-x86_64-linux-gnu/src/github.com/nsf/gocode/autocompletecontext.go:165
5(main.(*auto_complete_context).apropos): 
/build/gocode-WMuvMl/gocode-20150303/obj-x86_64-linux-gnu/src/github.com/nsf/gocode/autocompletecontext.go:253
6(main.server_auto_complete): 
/build/gocode-WMuvMl/gocode-20150303/obj-x86_64-linux-gnu/src/github.com/nsf/gocode/server.go:155
7(main.(*RPC).RPC_auto_complete): 
/build/gocode-WMuvMl/gocode-20150303/obj-x86_64-linux-gnu/src/github.com/nsf/gocode/rpc.go:26
8(runtime.call64): /usr/lib/go-1.7/src/runtime/asm_amd64.s:480
9(reflect.Value.call): /usr/lib/go-1.7/src/reflect/value.go:434
10(reflect.Value.Call): /usr/lib/go-1.7/src/reflect/value.go:302
11(net/rpc.(*service).call): /usr/lib/go-1.7/src/net/rpc/server.go:383
12(runtime.goexit): /usr/lib/go-1.7/src/runtime/asm_amd64.s:2086


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

Kernel: Linux 4.9.0-8-amd64 (SMP w/2 CPU cores)
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 /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages gocode depends on:
ii  libc6  2.24-11+deb9u3

gocode recommends no packages.

gocode suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 20170907-3+rm

Dear submitter,

as the package gocode has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/976642

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

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

Debian distribution maintenance software
pp.
Joerg Jaspert (the ftpmaster behind the curtain)--- End Message ---

Bug#954180: marked as done (pillow-python2: has failing autopkgtests for python3)

[Debian Bug Tracking System]

Your message dated Mon, 14 Dec 2020 21:27:51 +
with message-id 
and subject line Bug#971746: Removed package(s) from unstable
has caused the Debian Bug report #954180,
regarding pillow-python2: has failing autopkgtests for python3
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.)


-- 
954180: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954180
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
package: pillow-python2
version: 6.2.1-3
severity: serious

Hi,

The autopkgtests for pillow-python2 fail with
"selftest-py3 FAIL non-zero exit status 1"

I suspect the python 3 tests need to be removed (as the rest of the python3
packaging is in src:pillow).

Note that pillow-python2 currently doesn't migrate to testing, also blocking
the migration of src:pillow.

Ivo
--- End Message ---
--- Begin Message ---
Version: 6.2.1-3+rm

Dear submitter,

as the package pillow-python2 has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/971746

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

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

Debian distribution maintenance software
pp.
Joerg Jaspert (the ftpmaster behind the curtain)--- End Message ---

Bug#953220: marked as done (pillow-python2: Python2 removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Mon, 14 Dec 2020 21:27:51 +
with message-id 
and subject line Bug#971746: Removed package(s) from unstable
has caused the Debian Bug report #953220,
regarding pillow-python2: Python2 removal in sid/bullseye
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.)


-- 
953220: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953220
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pillow-python2
Version: 6.2.1-3
Severity: normal
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: py2removal

Python2 becomes end-of-live upstream, and Debian aims to remove
Python2 from the distribution, as discussed in
https://lists.debian.org/debian-python/2019/07/msg00080.html

Your package either build-depends, depends on Python2, or uses Python2
in the autopkg tests, in details:

(source:pillow-python2)Build-Depends->python-all-dev
(source:pillow-python2)Build-Depends->python-all-dbg
(source:pillow-python2)Build-Depends->python-setuptools
(source:pillow-python2)Build-Depends->python-tk
(source:pillow-python2)Build-Depends->python-tk-dbg
(source:pillow-python2)Build-Depends->python-pytest
(source:pillow-python2)Build-Depends->python-olefile
(binary:python-pil)Depends->python2
(binary:python-pil)Depends->python2
(binary:python-pil)Depends->python2:any
(binary:python-pil)Depends->python2:any
(binary:python-pil)Depends->python-pil.imagetk
(binary:python-pil)Recommends->python-olefile
(binary:python-pil-dbg)Depends->python-pil
(binary:python-pil-dbg)Depends->python2-dbg
(binary:python-pil.imagetk)Depends->python-pil
(binary:python-pil.imagetk)Depends->python-tk
(binary:python-pil.imagetk)Depends->python2
(binary:python-pil.imagetk)Depends->python2
(binary:python-pil.imagetk)Depends->python2:any
(binary:python-pil.imagetk)Depends->python2:any
(binary:python-pil.imagetk-dbg)Depends->python-pil.imagetk
(binary:python-pil.imagetk-dbg)Depends->python-pil-dbg
(binary:python-pil.imagetk-dbg)Depends->python2-dbg

Please stop using Python2, and fix this issue by one of the following
actions.

- Convert your Package to Python3. This is the preferred option.  In
  case you are providing a Python module foo, please consider dropping
  the python-foo package, and only build a python3-foo package.  Please
  don't drop Python2 modules, which still have reverse dependencies,
  just document them.
  
  This is the preferred option.

- If the package is dead upstream, cannot be converted or maintained
  in Debian, it should be removed from the distribution.  If the
  package still has reverse dependencies, raise the severity to
  "serious" and document the reverse dependencies with the BTS affects
  command.  If the package has no reverse dependencies, confirm that
  the package can be removed, reassign this issue to ftp.debian.org,
  make sure that the bug priority is set to normal and retitle the
  issue to "RM: PKG -- removal triggered by the Python2 removal".

- If the package has still many users (popcon >= 300), or is needed to
  build another package which cannot be removed, document that by
  adding the "py2keep" user tag (not replacing the py2remove tag),
  using the debian-pyt...@lists.debian.org user.  Also any
  dependencies on an unversioned python package (python, python-dev)
  must not be used, same with the python shebang.  These have to be
  replaced by python2/python2.7 dependencies and shebang.

  This is the least preferred option.

If there are questions, please refer to the wiki page for the removal:
https://wiki.debian.org/Python/2Removal, or ask for help on IRC
#debian-python, or the debian-pyt...@lists.debian.org mailing list.
--- End Message ---
--- Begin Message ---
Version: 6.2.1-3+rm

Dear submitter,

as the package pillow-python2 has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/971746

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

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

Debian distribution maintenance software
pp.
Joerg Jaspert (the ftpmaster behind the curtain)--- End Message ---

Bug#952969: marked as done (pillow-python2: d/copyright issues)

[Debian Bug Tracking System]

Your message dated Mon, 14 Dec 2020 21:27:51 +
with message-id 
and subject line Bug#971746: Removed package(s) from unstable
has caused the Debian Bug report #952969,
regarding pillow-python2: d/copyright issues
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.)


-- 
952969: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952969
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pillow-python2
Version: 6.2.1-3
Severity: serious

Hello,

Justification: Policy 2.3, 4.5, 12.5

During review in binary-NEW, I found the following issues with
d/copyright.  Since the issues already exist in the archive I did not
REJECT, but they should be fixed.

Note that I am filing an identical list of problems against src:pillow
as the orig.tar is now in the archive twice.

- Needs "Alex Clark **and contributors**" from LICENSE

- Copyright information for Tests/fonts not in d/copyright.

- Google suggests that Tests/images/bmp is GPL-3 and also that the files
  are generated using C code.  If that's right, we would need to at
  least include that code for generating the images in
  debian/missing-sources/ (and ideally regenerate them).

- Tests/images/pillow3.icns looks like it contains a colour space
  copyright 1998 Hewlett-Packard Company; unclear how licensed.

- Tests/test_file_fli.py says that Tests/images/a.fli came from the web
  and I cannot see any free license; probably needs to be filtered out.

- Tests/test_file_mcidas.py says something similar for some other
  images; this should be accounted for.

- Several files matching {docs/example,src/PIL}/*ImagePlugin.py and
  src/libImaging/BcnDecode.c are public domain/CC0.

- Most files matching
  src/PIL/{ImageMorph,MspImagePlugin,SpiderImagePlugin,_binary}.py and
  src/libImaging/{Jpeg2K*,Quant*,SgiRleDecode.c,UnsharpMask.c} have
  different copyright holders.

- src/Tk/_tkmini.h has different copyright holders and license; possibly
  not DFSG-free due to "GOVERNMENT USE" section.

- src/libImaging/{QuantOctree.c,raqm.h,nmake.opt} have different
  licenses and copyright holders.

-- 
Sean Whitton


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Version: 6.2.1-3+rm

Dear submitter,

as the package pillow-python2 has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/971746

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

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

Debian distribution maintenance software
pp.
Joerg Jaspert (the ftpmaster behind the curtain)--- End Message ---

Bug#977185: nheko: switch to Boost 1.74

[Hubert Chathi]

On Sat, 12 Dec 2020 09:42:27 +0100, Sebastian Ramacher  
said:

> nheko currently hardcodes its boost build dependencies with an
> explicit version. Since the default boost version is now 1.74 and we
> are trying to remove boost 1.71 before the release of bullseye, please
> switch to 1.74 or to the unversioned boost packages.

Thanks.  The hard-coding was done when the default boost in sid was too
old for nheko.  I'll switch to the unversioned boost packages.

-- 
Hubert Chathi  -- https://www.uhoreg.ca/
Jabber: hub...@uhoreg.ca -- Matrix: @uhoreg:matrix.org
PGP/GnuPG key: 4096R/F24C F749 6C73 DDB8 DCB8  72DE B2DE 88D3 113A 1368

Processed: fbxkb: diff for NMU version 0.6-2.1

[Debian Bug Tracking System]

Processing control commands:

> tags 975673 + patch
Bug #975673 [src:fbxkb] fbxkb: requires gdk-pixbuf-xlib-2.0.pc but does not 
build-depend on a package containing it
Ignoring request to alter tags of bug #975673 to the same tags previously set
> tags 975673 + pending
Bug #975673 [src:fbxkb] fbxkb: requires gdk-pixbuf-xlib-2.0.pc but does not 
build-depend on a package containing it
Ignoring request to alter tags of bug #975673 to the same tags previously set
> tags 975771 + patch
Bug #975771 [src:fbxkb] fbxkb: FTBFS: fbxkb.c:17:10: fatal error: gtk/gtk.h: No 
such file or directory
Ignoring request to alter tags of bug #975771 to the same tags previously set
> tags 975771 + pending
Bug #975771 [src:fbxkb] fbxkb: FTBFS: fbxkb.c:17:10: fatal error: gtk/gtk.h: No 
such file or directory
Ignoring request to alter tags of bug #975771 to the same tags previously set

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

Bug#975673: fbxkb: diff for NMU version 0.6-2.1

[Sudip Mukherjee]

Control: tags 975673 + patch
Control: tags 975673 + pending
Control: tags 975771 + patch
Control: tags 975771 + pending
--

Dear maintainer,

I've prepared an NMU for fbxkb (versioned as 0.6-2.1) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should cancel it.

--
Regards
Sudip

diff -Nru fbxkb-0.6/debian/changelog fbxkb-0.6/debian/changelog
--- fbxkb-0.6/debian/changelog  2014-11-05 15:38:59.0 +
+++ fbxkb-0.6/debian/changelog  2020-12-14 20:31:49.0 +
@@ -1,3 +1,11 @@
+fbxkb (0.6-2.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Add dependency on libgdk-pixbuf-xlib-2.0-dev. (Closes: #975673)
+- The dependency also fixes FTBFS with gtk/gtk.h. (Closes: #975771)
+
+ -- Sudip Mukherjee   Mon, 14 Dec 2020 20:31:49 
+
+
 fbxkb (0.6-2) unstable; urgency=low
 
   * New maintainer (Closes: #767970)
diff -Nru fbxkb-0.6/debian/control fbxkb-0.6/debian/control
--- fbxkb-0.6/debian/control2014-11-04 23:53:40.0 +
+++ fbxkb-0.6/debian/control2020-12-14 20:00:07.0 +
@@ -2,7 +2,7 @@
 Section: x11
 Priority: optional
 Maintainer: Dmitry Borisyuk 
-Build-Depends: debhelper (>= 9), libgtk2.0-dev, libxmu-dev
+Build-Depends: debhelper (>= 9), libgtk2.0-dev, libxmu-dev, 
libgdk-pixbuf-xlib-2.0-dev
 Standards-Version: 3.9.6
 Homepage: http://fbxkb.sourceforge.net
 

Processed: fbxkb: diff for NMU version 0.6-2.1

[Debian Bug Tracking System]

Processing control commands:

> tags 975673 + patch
Bug #975673 [src:fbxkb] fbxkb: requires gdk-pixbuf-xlib-2.0.pc but does not 
build-depend on a package containing it
Added tag(s) patch.
> tags 975673 + pending
Bug #975673 [src:fbxkb] fbxkb: requires gdk-pixbuf-xlib-2.0.pc but does not 
build-depend on a package containing it
Added tag(s) pending.
> tags 975771 + patch
Bug #975771 [src:fbxkb] fbxkb: FTBFS: fbxkb.c:17:10: fatal error: gtk/gtk.h: No 
such file or directory
Added tag(s) patch.
> tags 975771 + pending
Bug #975771 [src:fbxkb] fbxkb: FTBFS: fbxkb.c:17:10: fatal error: gtk/gtk.h: No 
such file or directory
Added tag(s) pending.

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

Bug#976830: marked as done (src:mia: invalid maintainer address)

[Debian Bug Tracking System]

Your message dated Mon, 14 Dec 2020 21:04:31 +
with message-id 
and subject line Bug#976830: fixed in mia 2.4.7-4
has caused the Debian Bug report #976830,
regarding src:mia: invalid maintainer address
to be marked as done.

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

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


-- 
976830: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976830
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: mia
Version: 2.4.7-3
Severity: serious
X-Debbugs-Cc: Andreas Tille 

The maintainer address is invalid, see below.

Ansgar

 Forwarded Message 
Subject: Mail delivery failed: returning message to sender
Date: Mon, 07 Dec 2020 16:09:54 +

> This message was created automatically by mail delivery software.
> 
> A message that you sent could not be delivered to one or more of its
> recipients. This is a permanent error. The following address(es)
> failed:
> 
>   debian-med-packag...@lists.debian.org
>     host bendel.debian.org [2001:41b8:202:deb:216:36ff:fe40:4002]
>     SMTP error from remote mail server after RCPT
> TO::
>     550 5.1.1 :
>     Recipient address rejected: User unknown in virtual alias table
--- End Message ---
--- Begin Message ---
Source: mia
Source-Version: 2.4.7-4
Done: Andreas Tille 

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

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

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

Debian distribution maintenance software
pp.
Andreas Tille  (supplier of updated mia 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, 14 Dec 2020 21:15:21 +0100
Source: mia
Architecture: source
Version: 2.4.7-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Andreas Tille 
Closes: 976830
Changes:
 mia (2.4.7-4) unstable; urgency=medium
 .
   * Team upload.
   * Fix maintainer address
 Closes: #976830
Checksums-Sha1:
 a4d371afe239f1b82020210a5f76ad9b6458eee2 2839 mia_2.4.7-4.dsc
 cb31c02fc7374b7ecb5cdbeaacbc09a872f6bc73 10308 mia_2.4.7-4.debian.tar.xz
 71732d02f98ad8418a0a92277a3f223707241df8 24488 mia_2.4.7-4_amd64.buildinfo
Checksums-Sha256:
 30c0c8d77cd8ba21513efd056af6fdc7b5e8f6f9f202f4d1069a88466d427546 2839 
mia_2.4.7-4.dsc
 2abb6fdd0dc7b909d8b13f75e9011b2a4aca2ed566d863021caecba52cc7356b 10308 
mia_2.4.7-4.debian.tar.xz
 461b912f70ca111b6f08218434feba804ddd844c8258d44adf57fc10c8b2d895 24488 
mia_2.4.7-4_amd64.buildinfo
Files:
 e17341d97886d199f6f76006d6becce2 2839 science optional mia_2.4.7-4.dsc
 436219b50e6234432d9cde7bfb6dd8c2 10308 science optional 
mia_2.4.7-4.debian.tar.xz
 ab957e788c5a9b946ce2845e1b88f06e 24488 science optional 
mia_2.4.7-4_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJFBAEBCgAvFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAl/Xze0RHHRpbGxlQGRl
Ymlhbi5vcmcACgkQV4oElNHGRtFW2g//TIohx3FtC3EMwxKcXCr2g04DWaEt3Xi2
YJvs/d627wQNV1+sqg1Mtm6krVYkSWUydRbIYF6Qe9CLgvwbIhRj1uokf6/iwkxD
tXZgnchJ6VsBX6jMrqnc5bSvFf/bbgGjiSGMo6PIROHsQ+1hgwUIwNBOtO0WMfxI
k+xjFM68Av1+02+VMeTxtNTrB0GXyLL+bwgTMuji8pqbwepdWTW+P2mbR5F1vV6r
+tuhufbjmefGU+S/xahDUhvLBMB5grrLIzlw31PM+SKualWOYJWFH15A6mQDB9tW
FQq2qoKmYrd7vw+7mKWley4IjqwpyKXJ90nDeo3Kg7X3bY2nfYJuY4reFs5ePe8T
hOtvXNVn4lVxop0xCHfHgUlT/N/4JsZjPG2qRqjTTFnMEvcF0hlxYjcN+99jOA6L
9gsmOdF1eHEXwAhynXLZFz0+f9P6TmrQBVf7g69DEG+jehiMv3htSg8L359PTubn
Ir3oVgW5a88lsByRb2br/+jPG5a2TdXQkoyHeZY5w7kFO8UXwAhmJ26VdQbe53I4
bf5zPQ4/fYfZ+0z5wdrTxQ5Wnx8geuMrenMF7M26xqrIp2wyNf18Du9CrwYne5W5
TlPoTl6raKArSIEtUO2mmDTtaI1M6kR0vQXLmKTdJArljG0Y4mnnX9n6CvzaqmgH
SdA0ylloGBM=
=47q8
-END PGP SIGNATURE End Message ---

Bug#977408: libstdc++-11-doc: missing Conflicts: libstdc++-10-doc

[Andreas Beckmann]

Followup-For: Bug #977408

Add libgccjit-11-doc which misses a Conflicts: libgccjit-10-doc to the list.

There are file conflicts on .png files with very generic names:

usr/share/info/factorial.png
usr/share/info/factorial1.png
usr/share/info/libgccjit.info.gz
usr/share/info/sum-of-squares.png
usr/share/info/sum-of-squares1.png

which could easily lead to clashes with other packages in the future.


Andreas

Bug#977409: libgm2-17: contains only libraries with SOVERSION 15

[Andreas Beckmann]

Package: libgm2-17
Version: 11-20201208-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package ships 

-rw-r--r-- root/root 31064 2020-12-08 14:08 
./usr/lib/x86_64-linux-gnu/libm2cor.so.15.0.0
-rw-r--r-- root/root189592 2020-12-08 14:08 
./usr/lib/x86_64-linux-gnu/libm2iso.so.15.0.0
-rw-r--r-- root/root 56168 2020-12-08 14:08 
./usr/lib/x86_64-linux-gnu/libm2log.so.15.0.0
-rw-r--r-- root/root 13968 2020-12-08 14:08 
./usr/lib/x86_64-linux-gnu/libm2min.so.15.0.0
-rw-r--r-- root/root172720 2020-12-08 14:08 
./usr/lib/x86_64-linux-gnu/libm2pim.so.15.0.0
lrwxrwxrwx root/root 0 2020-12-08 14:08 
./usr/lib/x86_64-linux-gnu/libm2cor.so.15 -> libm2cor.so.15.0.0
lrwxrwxrwx root/root 0 2020-12-08 14:08 
./usr/lib/x86_64-linux-gnu/libm2iso.so.15 -> libm2iso.so.15.0.0
lrwxrwxrwx root/root 0 2020-12-08 14:08 
./usr/lib/x86_64-linux-gnu/libm2log.so.15 -> libm2log.so.15.0.0
lrwxrwxrwx root/root 0 2020-12-08 14:08 
./usr/lib/x86_64-linux-gnu/libm2min.so.15 -> libm2min.so.15.0.0
lrwxrwxrwx root/root 0 2020-12-08 14:08 
./usr/lib/x86_64-linux-gnu/libm2pim.so.15 -> libm2pim.so.15.0.0

which is inconsistent with being renamed to libgm2-17.
It also causes file conflicts with libgm2-15 in sid.


Andreas

Processed: diff NMU for anytun_0.3.7-1.3

[Debian Bug Tracking System]

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

> tags 977219 +pending +patch
Bug #977219 [src:anytun] anytun: FTBFS with boost 1.74
Added tag(s) pending.
Bug #977219 [src:anytun] anytun: FTBFS with boost 1.74
Added tag(s) patch.
> user team+bo...@tracker.debian.org
Setting user to team+bo...@tracker.debian.org (was gladky.an...@gmail.com).
> usertag 977219 +boost174
There were no usertags set.
Usertags are now: boost174.
> thanks
Stopping processing here.

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

Bug#977219: diff NMU for anytun_0.3.7-1.3

[Anton Gladky]

tags 977219 +pending +patch
user team+bo...@tracker.debian.org
usertag 977219 +boost174
thanks

Dear maintainer,

I have prepared an NMU (versioned as 0.3.7-1.3) and
uploaded to DELAYED/5.

Please feel free to tell me if I should delay it longer, cancel
or reschedule.

Diff is attached.

Best regards

Anton


nmu.debdiff
Description: Binary data

Bug#900821: workaround confirmed

[Florian Kain]

Hi all,

we were experiencing this bug in a debian 10.4 docker container (FROM 
php:apache)
it only happens with plain http not with https.

I can confirm that workaround from  Stefan Fritsch  by 
turning EnableMMAP off is working for us!

Cheers,
Florian

Bug#977408: libstdc++-11-doc: missing Conflicts: libstdc++-10-doc

[Andreas Beckmann]

Package: libstdc++-11-doc
Version: 11-20201208-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'sid' to 'experimental'.
It installed fine in 'sid', then the upgrade to 'experimental' fails
because it tries to overwrite other packages files without declaring a
Breaks+Replaces relation.

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

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

  Preparing to unpack .../libstdc++-11-doc_11-20201208-1_all.deb ...
  Unpacking libstdc++-11-doc (11-20201208-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/libstdc++-11-doc_11-20201208-1_all.deb (--unpack):
   trying to overwrite '/usr/share/man/man3/C++Intro.3cxx.gz', which is also in 
package libstdc++-10-doc 10.2.1-1
  dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
  Errors were encountered while processing:
   /var/cache/apt/archives/libstdc++-11-doc_11-20201208-1_all.deb

You should consider adding Conflicts+Replaces+Provides on some (internally
used) virtual package to avoid running into this problem again in the
future.


cheers,

Andreas


libstdc++-10-doc=10.2.1-1_libstdc++-11-doc=11-20201208-1.log.gz
Description: application/gzip

Bug#976900: marked as done (pyside2 hard-codes Python 3.8 in it's install files)

[Debian Bug Tracking System]

Your message dated Mon, 14 Dec 2020 20:37:02 +
with message-id 
and subject line Bug#976900: fixed in pyside2 5.15.0-6
has caused the Debian Bug report #976900,
regarding pyside2 hard-codes Python 3.8 in it's install files
to be marked as done.

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

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


-- 
976900: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976900
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:pyside2
Version: 5.15.0-5
Tags: ftbfs sid bullseye
Severity: serious

$ fgrep 3.8 debian/shiboken2-doc.docs
pyside3_build/py3.8-*-relwithdebinfo/shiboken2/doc/html
--- End Message ---
--- Begin Message ---
Source: pyside2
Source-Version: 5.15.0-6
Done: Dmitry Shachnev 

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

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

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

Debian distribution maintenance software
pp.
Dmitry Shachnev  (supplier of updated pyside2 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, 14 Dec 2020 20:31:39 +0300
Source: pyside2
Architecture: source
Version: 5.15.0-6
Distribution: unstable
Urgency: medium
Maintainer: Debian Qt/KDE Maintainers 
Changed-By: Dmitry Shachnev 
Closes: 976516 976900
Changes:
 pyside2 (5.15.0-6) unstable; urgency=medium
 .
   * Team upload.
 .
   [ Debian Janitor ]
   * Apply multi-arch hints.
 + python-pyside2-doc, shiboken2-doc: Add Multi-Arch: foreign.
 + libshiboken2-dev, python3-pyside2.qt*: Add Multi-Arch: same.
 .
   [ Dmitry Shachnev ]
   * Drop ftbfs-old-qt.patch. Not needed since Debian has Qt 5.15.
   * Stop hardcoding py3.8 in debian/shiboken2-doc.docs (closes: #976900).
   * Blacklist QtWidgets::bug_307 test for now (closes: #976516).
Checksums-Sha1:
 9850f8abf775f70c8e4278691eacd673136a9b13 7272 pyside2_5.15.0-6.dsc
 9e10ed0d2892b298b02a4a2b5da29a1a5db01037 40708 pyside2_5.15.0-6.debian.tar.xz
 06838f8cdcf026a8076dbd43af63cc9e49c13825 8404 pyside2_5.15.0-6_source.buildinfo
Checksums-Sha256:
 cc843ab1b1913b4615c550b37da3c17365659f67e8fd3705b0d8d92c1bcff7f7 7272 
pyside2_5.15.0-6.dsc
 72b8ba50e5e95c4e09d76692a1b37c7748fc860cdb24a4ce4b3c8295b2321eab 40708 
pyside2_5.15.0-6.debian.tar.xz
 269faedc9f8bb49c9e2a36fa6c725877a244c1e87e56871b0b7a501f108a5740 8404 
pyside2_5.15.0-6_source.buildinfo
Files:
 6eb61088bed982584e21503362cb6ce4 7272 python optional pyside2_5.15.0-6.dsc
 c811a583b1dc5d7606b03a0ac84db785 40708 python optional 
pyside2_5.15.0-6.debian.tar.xz
 ce0ef421fa1c6077a146acbe8a5c2792 8404 python optional 
pyside2_5.15.0-6_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJHBAEBCgAxFiEE5688gqe4PSusUZcLZkYmW1hrg8sFAl/XofwTHG1pdHlhNTdA
ZGViaWFuLm9yZwAKCRBmRiZbWGuDyzIHD/9XEJfehjrcqaXbEW1gWGKxqYdg+s5N
oMiv+QOpKE+A7ywVE9BmibwVDq56YbSlkfo6q/VXU4QBb7Mt4t8X7/uW4TiAcLlQ
fJnYjAMWuEKHk1v5XqZnhmxJQv9JlcBGtcCYvyfV6p+jBQZdDR+Wkg/takERwOI8
JTif2TgXEY/2ezIbsTEvRXFVI2Ol51l/wzVrqQ0FCXP6VLsvyt3+eeRcCe41o9+s
CBc9KGWpluQJFoGPZql5QG/7cziAjPWIVF1+utw60SupJxRofPNF2OT8SCxM19u4
82UmpYYQbGk08/HpwmzpLtoPlWarcpRDW9SeYsbMK33G/9qT9r1vuASKrqwLWdFf
vjXBobEHx9RgkjUEishDlqdtDYxZItnSGdY+4HLOqhYz3rqZuEnkrvoMLq4xKMad
EzAnAmDPcMuD2jN/pZ7NkuU9WsJN+uNSLGf8u8ln4u3a6Mk2CQtkMqcl4D5smSwW
Ci+m/FkmLceomEjyGUIYit0Yi94DS87csEhM1JQZo9sTsX1qMak+Jb1x+MKWDykP
Ypm0cNj9Wxh9uFRW/9iUast20Jw3BycFffgIwDLC5oFNyuDn1JzNG3UrfF9/7Mi7
cWNek8N+/vSZxJW/EnGLS0q98InsV14mrUfVJiwfJ+d3xRMuv3sG34WceGNq4cNK
igdL37y4ZBOhXw==
=EaCI
-END PGP SIGNATURE End Message ---

Bug#976561: marked as done (sword-text-web: FTBFS: Binary files engWEB2015eb/nt.bzs and modules/texts/ztext/engWEB2015eb/nt.bzs differ)

[Debian Bug Tracking System]

Your message dated Mon, 14 Dec 2020 20:37:17 +
with message-id 
and subject line Bug#976561: fixed in sword-text-web 353.0-1
has caused the Debian Bug report #976561,
regarding sword-text-web: FTBFS: Binary files engWEB2015eb/nt.bzs and 
modules/texts/ztext/engWEB2015eb/nt.bzs differ
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.)


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

Hi,

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

Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> diff engWEB2015eb modules/texts/ztext/engWEB2015eb
> Binary files engWEB2015eb/nt.bzs and modules/texts/ztext/engWEB2015eb/nt.bzs 
> differ
> Binary files engWEB2015eb/nt.bzv and modules/texts/ztext/engWEB2015eb/nt.bzv 
> differ
> Binary files engWEB2015eb/nt.bzz and modules/texts/ztext/engWEB2015eb/nt.bzz 
> differ
> Binary files engWEB2015eb/ot.bzs and modules/texts/ztext/engWEB2015eb/ot.bzs 
> differ
> Binary files engWEB2015eb/ot.bzv and modules/texts/ztext/engWEB2015eb/ot.bzv 
> differ
> Binary files engWEB2015eb/ot.bzz and modules/texts/ztext/engWEB2015eb/ot.bzz 
> differ
> make[1]: *** [debian/rules:14: override_dh_auto_test-indep] Error 1

The full build log is available from:
   http://qa-logs.debian.net/2020/12/05/sword-text-web_349.0-1_unstable.log

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

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

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

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

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

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

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

Debian distribution maintenance software
pp.
Teus Benschop  (supplier of updated sword-text-web 
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, 14 Dec 2020 21:03:16 +0100
Source: sword-text-web
Architecture: source
Version: 353.0-1
Distribution: unstable
Urgency: medium
Maintainer: CrossWire Packaging Team 

Changed-By: Teus Benschop 
Closes: 976561
Changes:
 sword-text-web (353.0-1) unstable; urgency=medium
 .
   [ Bastian Germann ]
   * Team upload
   * New upstream version 353.0
   * Remove test against the published mod (Closes: #976561)
Checksums-Sha1:
 0f233ad295816ad70345d04ef78710d6387e1bc5 2393 sword-text-web_353.0-1.dsc
 6719f7f46ce2f3527faf120ede3db6194c1e63ed 3877228 
sword-text-web_353.0.orig-osis.tar.gz
 b077883c84d1d9905b2b164946545ae3bffb91f0 3997738 
sword-text-web_353.0.orig.tar.gz
 3ed2ba98c27773ea96dabeecae6367bda7efb499 3368 
sword-text-web_353.0-1.debian.tar.xz
 d2a079fa303b9d886d3d498e8fa123b0b379b56c 6558 
sword-text-web_353.0-1_source.buildinfo
Checksums-Sha256:
 b0606e84774d935e1cbc3212b564daa8bd1f3ab2c346f7ad8e18d93da8fd803e 2393 
sword-text-web_353.0-1.dsc
 73f667e848b56ae58b960310159f55e0312dd7c5527cad217fdf1e334b70c1b6 3877228 
sword-text-web_353.0.orig-osis.tar.gz
 85aa93dcd145a0eae9837fd910d676a3a31648feebcd02167465ff4147b3a444 3997738 
sword-text-web_353.0.orig.tar.gz
 fbe8173c841569e79fe347a37d11a91b9395706d029e66e9b4b5385823578a1b 3368 
sword-text-web_353.0-1.debian.tar.xz
 97aa7a2049d73f9551f4c164b807e61fa8d79d77f97c5f7040ee9cd85a4ff0dd 6558 
sword-text-web_353.0-1_source.buildinfo
Files:
 

Bug#977407: jitterdebugger-utils: missing Breaks+Replaces: jitterdebugger (<< 0.3.1+git20200117.b90ff3a-2)

[Andreas Beckmann]

Package: jitterdebugger-utils
Version: 0.3.1+git20200117.b90ff3a-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'testing'.
It installed fine in 'testing', then the upgrade to 'sid' fails
because it tries to overwrite other packages files without declaring a
Breaks+Replaces relation.

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

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

  Preparing to unpack 
.../jitterdebugger-utils_0.3.1+git20200117.b90ff3a-2_amd64.deb ...
  Unpacking jitterdebugger-utils (0.3.1+git20200117.b90ff3a-2) ...
  dpkg: error processing archive 
/var/cache/apt/archives/jitterdebugger-utils_0.3.1+git20200117.b90ff3a-2_amd64.deb
 (--unpack):
   trying to overwrite '/usr/bin/jitterplot', which is also in package 
jitterdebugger 0.3.1+git20200117.b90ff3a-1
  Errors were encountered while processing:
   
/var/cache/apt/archives/jitterdebugger-utils_0.3.1+git20200117.b90ff3a-2_amd64.deb


cheers,

Andreas


jitterdebugger=0.3.1+git20200117.b90ff3a-1_jitterdebugger-utils=0.3.1+git20200117.b90ff3a-2.log.gz
Description: application/gzip

Processed: Re: Bug#976487: grpc-java: FTBFS: CensusStatsModule.java:21: error: cannot find symbol

[Debian Bug Tracking System]

Processing control commands:

> tag -1 confirmed
Bug #976487 [src:grpc-java] grpc-java: FTBFS: CensusStatsModule.java:21: error: 
cannot find symbol
Added tag(s) confirmed.

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

Bug#976487: grpc-java: FTBFS: CensusStatsModule.java:21: error: cannot find symbol

[Olek Wojnar]

Control: tag -1 confirmed

Thank you for the bug report! I am able to replicate this locally. It
looks like this was caused by a recent upload of opencensus-java that
removed two symbols. I am working on an upload of an updated grpc-java
package that no longer requires those symbols.

-Olek




signature.asc
Description: OpenPGP digital signature

Bug#977348: ulfius: missing runtime zlib dependency?

[Nicolas Mora]

On Mon, 14 Dec 2020 10:53:53 +0100 Gianfranco Costamagna 
 wrote:


Hello, looks like the new ulfius version is missing a zlib1g-dev dependency on 
the -dev package, leading to reverse-dependencies FTBFS in tests (e.g. in 
src:iddawc)


Indeed, I missed that one, thanks!


OpenPGP_0xFE82139440BD22B9.asc
Description: application/pgp-keys


OpenPGP_signature
Description: OpenPGP digital signature

Bug#976561: uploaded

[Teus Benschop]

Thanks for the fix.
That is great.
The package was built, reviewed and uploaded.

Bug#977405: libgtkdatabox-dev,libgtkdatabox-doc: both ship /usr/share/doc/libgtkdatabox-dev/{AUTHORS,README}

[Andreas Beckmann]

Package: libgtkdatabox-dev,libgtkdatabox-doc
Version: 1:0.9.3.1-1.1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package failed to install
because it tries to overwrite other packages files.

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

  Preparing to unpack .../libgtkdatabox-doc_1%3a0.9.3.1-1.1_all.deb ...
  Unpacking libgtkdatabox-doc (1:0.9.3.1-1.1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/libgtkdatabox-doc_1%3a0.9.3.1-1.1_all.deb (--unpack):
   trying to overwrite '/usr/share/doc/libgtkdatabox-dev/AUTHORS', which is 
also in package libgtkdatabox-dev 1:0.9.3.1-1.1+b1
  dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
  Errors were encountered while processing:
   /var/cache/apt/archives/libgtkdatabox-doc_1%3a0.9.3.1-1.1_all.deb


cheers,

Andreas


libgtkdatabox-dev=1:0.9.3.1-1.1+b1_libgtkdatabox-doc=1:0.9.3.1-1.1.gz
Description: application/gzip

Bug#976943: golang-github-seccomp-libseccomp-golang: FTBFS on ppc64el (arch:all-only src pkg): dh_auto_test: error: cd obj-powerpc64le-linux-gnu && go test -vet=off -v -p 160 github.com/seccomp/libsec

[Reinhard Tartler]

> === RUN   TestRuleAddAndLoad
> seccomp_test.go:588: Syscall should have returned error code!
> --- FAIL: TestRuleAddAndLoad (0.00s)


Source code is here: 
https://sources.debian.org/src/golang-github-seccomp-libseccomp-golang/0.9.1-2/seccomp_test.go/#L529-L589

This test is basically loading a seccomp rule and expects that the
getpid() syscall fails with the rule loaded, but in that test it seems
to pass. This might mean that seccomp isn't working on that box.

Lucas, can you elaborate a bit what kind of test system you were using?
Do you have any explanation what might be going on with the test setup that
would make seccomp not work or only under certain conditions?

-rt

Bug#976831: marked as done (src:amide: invalid maintainer address)

[Debian Bug Tracking System]

Your message dated Mon, 14 Dec 2020 18:18:30 +
with message-id 
and subject line Bug#976831: fixed in amide 1.0.5-15
has caused the Debian Bug report #976831,
regarding src:amide: invalid maintainer address
to be marked as done.

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

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


-- 
976831: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976831
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: amide
Version: 1.0.5-14
Severity: serious
X-Debbugs-Cc: Gert Wollny 

The maintainer address is invalid, see below.

Ansgar

 Forwarded Message 
Subject: Mail delivery failed: returning message to sender
Date: Sat, 05 Dec 2020 22:04:10 +

> This message was created automatically by mail delivery software.
> 
> A message that you sent could not be delivered to one or more of its
> recipients. This is a permanent error. The following address(es)
> failed:
> 
>   debian-med-packag...@lists.debian.org
>     host bendel.debian.org [2001:41b8:202:deb:216:36ff:fe40:4002]
>     SMTP error from remote mail server after RCPT
> TO::
>     550 5.1.1 :
>     Recipient address rejected: User unknown in virtual alias table
--- End Message ---
--- Begin Message ---
Source: amide
Source-Version: 1.0.5-15
Done: Andreas Tille 

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

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

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

Debian distribution maintenance software
pp.
Andreas Tille  (supplier of updated amide 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, 14 Dec 2020 18:55:13 +0100
Source: amide
Architecture: source
Version: 1.0.5-15
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Andreas Tille 
Closes: 976831
Changes:
 amide (1.0.5-15) unstable; urgency=medium
 .
   * Fix maintainer address
 Closes: #976831
Checksums-Sha1:
 971ca9e10aeb956726ad39e0a1c0711ab9fa6591 2159 amide_1.0.5-15.dsc
 2df47c06087f1ce8065e69048f9b7e6dac6ab67c 14132 amide_1.0.5-15.debian.tar.xz
 de220ced15bc2b3d2e5217c24c011f632297c1f3 15538 amide_1.0.5-15_amd64.buildinfo
Checksums-Sha256:
 3ef35784bc22b310a6fe4c8afdafb93593ac87599a92691d497aa0199854b810 2159 
amide_1.0.5-15.dsc
 5763f2ed5842c1851719ab40a463452f1d100465705b2751aa66c82a7ba5a711 14132 
amide_1.0.5-15.debian.tar.xz
 71f1f575a474b4b69dfc379b937fc0234b0aec558f88b8fdee56dac17bf4a1c9 15538 
amide_1.0.5-15_amd64.buildinfo
Files:
 077e74e2d7848c1f70712ce935ed33ce 2159 graphics optional amide_1.0.5-15.dsc
 f2cfc29d62f814a9f28b0ae1d3dec731 14132 graphics optional 
amide_1.0.5-15.debian.tar.xz
 33ae96a4a43f18bb100677cb39080567 15538 graphics optional 
amide_1.0.5-15_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJFBAEBCAAvFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAl/XqLURHHRpbGxlQGRl
Ymlhbi5vcmcACgkQV4oElNHGRtGigA//ea50U7WBkdaFSM9yaIo7Ji9hf/FBVLaM
H5VFrJq6LFTiyKM8KSraHQF3FbYGcPS8Aet2GooSaNIasjbwuGyZQ9IBLTaOALBu
pQaVpOqmpqBQeEu7GniqNPxeLWt/8YnDlhrhi3c14jxg7y6ND8OUHay5Zt86X8zL
INST37R0sj8zX0Wa0jDmhzd2baGhZbYwEVZr6lg22FinZiVqBDJHgVt1UbecvpxQ
dmvo6habQfHbCAl9ovu/Jk8ltVGh3OeegzAOAW98BfxHHQHhcuWYBJTXVhR3KPrq
YEdpbwa5gCmMrAKZjXqo7YVkGRK1VjB8NoBG8t3huaq2qtCNJKEm54Ewr10bcZYI
zWrSVwtwGIONWSD/FiNgLzcMEySOkLNeFOkNGQhAQl8NzCfXF5uDQ8eG25/glrNO
iPksX9bJe5ju66TPi6NAmJa03J7M2Y7koxco2Yyiw7vsvMuZBKxu0fVjH8XSQy+G
bNyj927SENzV5fXCcwBIUB5Dvkj+Lz6zFEsItMhrMVlZ0D/mVswpdpV9sqRZ5age
0EptTM/lqF0nPT84FSbBO3l/ZWv88IkdUF16nMdugZhNc114kQOBflxOqXLMsyfY
BCVar8Ux6b1cM1B3lyG4/4Y7oSSES/jt39AUT+K7TNH+4z+VgClwEr/7Cgmrk+Nl
Yh35NaMOPqY=
=TLtp
-END PGP SIGNATURE End Message ---

Bug#977354: marked as done (libmagics++-dev: Invalid dependency on "i" package)

[Debian Bug Tracking System]

Your message dated Mon, 14 Dec 2020 18:05:07 +
with message-id 
and subject line Bug#977354: fixed in magics++ 4.5.2-2
has caused the Debian Bug report #977354,
regarding libmagics++-dev: Invalid dependency on "i" package
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.)


-- 
977354: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977354
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libmagics++-dev
Version: 4.5.2-1
Severity: grave
Justification: renders package unusable

I was alerted by a strange log in the package tracker:
/usr/lib/python3/dist-packages/debian/deb822.py:1403: UserWarning: cannot parse 
package
relationship "i", returning it raw

I looked up what package would depend on "i" and I found libmagics++-dev:

$ apt show libmagics++-dev
Package: libmagics++-dev
Version: 4.5.2-1
Priority: optional
Section: libdevel
Source: magics++
Maintainer: Alastair McKinstry 
Installed-Size: 587 kB
Depends: libmagplus3v5 (= 4.5.2-1), i, python3, libmagics++-metview-dev, 
libterralib-dev, magics++, libodc-dev
[...]

Obviously that package doesn't exist and is not installable so your package
can't migrate.

Please upload a fixed package ASAP as it generates annoying noise
every 6 hours in my INBOX ;-)

Cheers,

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

Kernel: Linux 4.19.0-6-amd64 (SMP w/4 CPU threads)
Kernel taint flags: 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

-- 
  ⢀⣴⠾⠻⢶⣦⠀   Raphaël Hertzog 
  ⣾⠁⢠⠒⠀⣿⡁
  ⢿⡄⠘⠷⠚⠋The Debian Handbook: https://debian-handbook.info/get/
  ⠈⠳⣄   Debian Long Term Support: https://deb.li/LTS
--- End Message ---
--- Begin Message ---
Source: magics++
Source-Version: 4.5.2-2
Done: Alastair McKinstry 

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

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

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

Debian distribution maintenance software
pp.
Alastair McKinstry  (supplier of updated magics++ 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, 14 Dec 2020 14:55:21 +
Source: magics++
Architecture: source
Version: 4.5.2-2
Distribution: unstable
Urgency: medium
Maintainer: Alastair McKinstry 
Changed-By: Alastair McKinstry 
Closes: 977354
Changes:
 magics++ (4.5.2-2) unstable; urgency=medium
 .
   * Fix serious typo in d/control. Closes: #977354
Checksums-Sha1:
 f6960e2602d3f9a4fc3383d9b842fc64a1e584c4 2774 magics++_4.5.2-2.dsc
 f3b46c162eb8d700d5a16cdc22dd7eee54e7dcda 18672 magics++_4.5.2-2.debian.tar.xz
Checksums-Sha256:
 89f1568995e96b2f3c2eada3b4d5aae955088da8cce4f50952e22d6404d3609b 2774 
magics++_4.5.2-2.dsc
 457537082f4f373ee423d8509db19b6ca0d5f2cad23e86ca3dd1566aad705327 18672 
magics++_4.5.2-2.debian.tar.xz
Files:
 6ea4028cd7ffadf16d105b71ca0676ed 2774 science optional magics++_4.5.2-2.dsc
 772502ac32fba75aa75c72717cd8308b 18672 science optional 
magics++_4.5.2-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEgjg86RZbNHx4cIGiy+a7Tl2a06UFAl/Xo/oACgkQy+a7Tl2a
06WH8Q/6A34g5GVl4EN5HWpj4cWMLcBxBVITUCuKc/01yNiI7GivvOw1kIEY2E+u
kGKwQeieIiF2+sJy6oJ4kdi1lH7qti7W+pSlgJQxK29XKZ/wb3pLYTY4nRLhTck9
+qssDmWtCOoIxIrvjiQoklMU+uLC7w695upU4nAv4K1kaFmpXZNBoGjQX+X07ZIR
a24x9rIg2/qzO1AoTPvbEtG4upoy8ERBFVcrrxedUh//gLSJnWNSFKdfkfaIK9Eb
3AdCFV7HkSsTmp2VW7Ykf91J4L4pxt03psY5UHQSkxH06TIvmoKx7RsQzwOcCAH7
FG47LUu9cH4eq5M2jVzdMhTZFpDZeih/NellFKER26u97mPdd9i92wUmOycUT8Zz
+MgvvwrMeophWf7FTYxbKTJr8LYwiahSuqcN9WDiLV4qi+xu/FltZyseQ852Gdnx
dBV3dpai5IPy/ZwBI3VBxJFgzXH/079JBCrTBP/1RHiIh1//hsb6e+4tBjzWCJho
xiJA8AirIYVHdGKS7erTHCuHGoM2Bc4dfs2p+uKwuun5P18A+XbhG5GJ9eWbq80v
QqNcqgpW9gO1+fSNhims9Tc9BFaUNimlHRRfzUNBt1Hxrn+c8MYAKlyDjt/WbaEt
9Rm/hPF2m1X4jH6Rshy/Zp/cZJdxFuCzwIEKq8d2anPZFZPVTSk=
=9Ypb
-END PGP SIGNATURE End Message ---

Bug#977246: lutris should depend on python3-dbus

[Stephan Lachnit]

Hi,

thanks for discovering this missing dependency.

Since I closely follow the upstream Debian sources, I created a PR there:
https://github.com/lutris/lutris/pull/3349

Depending on the schedule for a new release I will either backport this or wait 
for the new release.
Kinda depends on how much time I have.

Regards,
Stephan

Bug#977308: shasta: hardcoded dependencies on boost 1.71

[Andreas Tille]

Hi Shayan,

did you had some reasons to add this hardcoded dependency?

Kind regards

 Andreas.

On Sun, Dec 13, 2020 at 10:15:44PM +0200, Graham Inggs wrote:
> Source: shasta
> Version: 0.6.0-4
> Severity: serious
> Tags: ftbfs
> 
> Hi Maintainer
> 
> Binary package shasta has a hardcoded dependency on
> libboost-chrono1.71.0 and binary package python3-shasta has a
> hardcoded dependency on libboost-program-options1.71.0.
> 
> Boost 1.71 will be removed after the Boost 1.74 transition, which is ongoing.
> 
> Regards
> Graham
> 
> ___
> Debian-med-packaging mailing list
> debian-med-packag...@alioth-lists.debian.net
> https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-med-packaging

-- 
http://fam-tille.de

Processed: Bug#976516 marked as pending in pyside2

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #976516 [src:pyside2] pyside2: FTBFS: ValueError: At least one failure was 
not blacklisted and met the criterion 'FAIL! >= 3'
Added tag(s) pending.

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

Bug#976516: marked as pending in pyside2

[Dmitry Shachnev]

Control: tag -1 pending

Hello,

Bug #976516 in pyside2 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/qt-kde-team/qt/pyside2/-/commit/d25ac99d676f5b5304923415a559b170f12b713c


Blacklist QtWidgets::bug_307 test for now.

Closes: #976516.


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/976516

Bug#977397: uim-el: missing *-uim in input-method-alist on Emacs 27

[Nobuhiro Ban]

Package: uim-el
Version: 1:1.8.8-6.1+b2
Severity: grave
Justification: renders package unusable
Tags: patch

Dear Maintainer,

I used the japanese-anthy-utf8-uim input-method on my Debian Emacs 26 env.
But after upgrading Emacs 27,
I cannot set input-method to japanese-anthy-utf8-uim.

(Same cause as #977257)

There is a problem at initializing uim-el.
So none of the input methods *-uim are prepared on startup.

>From *Message* buffer:
>Error while loading 50uim-el: Symbol’s function definition is void: 
>process-kill-without-query


How to fix:

Replace process-kill-without-query with set-process-query-on-exit-flag
in /usr/share/emacs/site-lisp/uim-el/*.el .
This patch fixes this problem.
- Begin
--- uim-1.8.8.orig/emacs/uim-helper.el
+++ uim-1.8.8/emacs/uim-helper.el
@@ -106,7 +106,7 @@
 (if (not proc)
 (error "uim.el: Couldn't invoke uim-el-helper-agent."))

-(process-kill-without-query proc)
+(set-process-query-on-exit-flag proc nil)

 ;; wait "OK"
 (let ((patience uim-startup-timeout) (ok nil))
--- uim-1.8.8.orig/emacs/uim.el
+++ uim-1.8.8/emacs/uim.el
@@ -488,7 +488,7 @@
 (error "uim.el: Couldn't invoke uim-el-agent."))

 ;; don't ask kill
-(process-kill-without-query proc)
+(set-process-query-on-exit-flag proc nil)

 ;; wait "OK"
 (let ((patience uim-startup-timeout) (ok nil))
- End


Regards,
Nobuhiro Ban




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

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

Versions of packages uim-el depends on:
ii  emacs1:27.1+1-3
ii  emacs-gtk [emacsen]  1:27.1+1-3
ii  libc62.31-5
ii  libuim8  1:1.8.8-6.1+b2
ii  uim  1:1.8.8-6.1+b2
ii  uim-data 1:1.8.8-6.1

uim-el recommends no packages.

uim-el suggests no packages.

-- no debconf information

Processed: [bts-link] source package scapy

[Debian Bug Tracking System]

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

> #
> # bts-link upstream status pull for source package scapy
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> # https://bts-link-team.pages.debian.net/bts-link/
> #
> user debian-bts-l...@lists.debian.org
Setting user to debian-bts-l...@lists.debian.org (was 
debian-bts-l...@lists.debian.org).
> # remote status report for #973171 (http://bugs.debian.org/973171)
> # Bug title: dhcpcanon: FTBFS: dh_auto_test: error: pybuild --test 
> --test-pytest -i python{version} -p "3.9 3.8" returned exit code 13
> #  * https://github.com/secdev/scapy/pull/3000
> #  * remote status changed: open -> closed
> #  * closed upstream
> tags 973171 + fixed-upstream
Bug #973171 [python3-scapy] dhcpcanon: FTBFS: dh_auto_test: error: pybuild 
--test --test-pytest -i python{version} -p "3.9 3.8" returned exit code 13
Added tag(s) fixed-upstream.
> usertags 973171 - status-open
Usertags were: status-open.
Usertags are now: .
> usertags 973171 + status-closed
There were no usertags set.
Usertags are now: status-closed.
> thanks
Stopping processing here.

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

Processed: [bts-link] source package src:firefox

[Debian Bug Tracking System]

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

> #
> # bts-link upstream status pull for source package src:firefox
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> # https://bts-link-team.pages.debian.net/bts-link/
> #
> user debian-bts-l...@lists.debian.org
Setting user to debian-bts-l...@lists.debian.org (was 
debian-bts-l...@lists.debian.org).
> # remote status report for #976731 (http://bugs.debian.org/976731)
> # Bug title: firefox: FTBFS on arm64 (explicit specialization in 
> non-namespace scope class js::wasm::BaseRegAlloc)
> #  * https://bugzilla.mozilla.org/show_bug.cgi?id=1677690
> #  * remote status changed: (?) -> RESOLVED
> #  * remote resolution changed: (?) -> FIXED
> #  * closed upstream
> tags 976731 + fixed-upstream
Bug #976731 [src:firefox] firefox: FTBFS on arm64 (explicit specialization in 
non-namespace scope ‘class js::wasm::BaseRegAlloc’)
Added tag(s) fixed-upstream.
> usertags 976731 + status-RESOLVED resolution-FIXED
There were no usertags set.
Usertags are now: resolution-FIXED status-RESOLVED.
> thanks
Stopping processing here.

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

Processed: [bts-link] source package src:odoo

[Debian Bug Tracking System]

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

> #
> # bts-link upstream status pull for source package src:odoo
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> # https://bts-link-team.pages.debian.net/bts-link/
> #
> user debian-bts-l...@lists.debian.org
Setting user to debian-bts-l...@lists.debian.org (was 
debian-bts-l...@lists.debian.org).
> # remote status report for #973605 (http://bugs.debian.org/973605)
> # Bug title: odoo: Multiple privacy-breach-generic (fetching data from an 
> external website at runtime)
> #  * https://github.com/odoo/odoo/pull/61199
> #  * remote status changed: open -> closed
> #  * closed upstream
> tags 973605 + fixed-upstream
Bug #973605 [src:odoo] odoo: Multiple privacy-breach-generic (fetching data 
from an external website at runtime)
Added tag(s) fixed-upstream.
> usertags 973605 - status-open
Usertags were: status-open.
Usertags are now: .
> usertags 973605 + status-closed
There were no usertags set.
Usertags are now: status-closed.
> thanks
Stopping processing here.

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

Processed: Re: Bug#974940 closed by Paul Gevers (src:xserver-xorg-video-ati: fails to migrate to testing for too long: FTBFS on mips*el)

[Debian Bug Tracking System]

Processing control commands:

> reopen -1
Bug #974940 {Done: Paul Gevers } 
[src:xserver-xorg-video-ati] src:xserver-xorg-video-ati: fails to migrate to 
testing for too long: FTBFS on mips*el
'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 xserver-xorg-video-ati/1:19.1.0-2.

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

Bug#974940: closed by Paul Gevers (src:xserver-xorg-video-ati: fails to migrate to testing for too long: FTBFS on mips*el)

[Helmut Grohne]

Control: reopen -1

Hi Paul,

On Mon, Nov 16, 2020 at 08:21:05PM +, Debian Bug Tracking System wrote:
> It has been closed by Paul Gevers .

I fail to understand why you closed this bug. As of today, builds for
mipsel and mips64el are still missing. A local cross build for mips64el
fails in exactly the same way. Thus reopening the bug. I think your
closure was in error.

Helmut

Bug#975863: marked as done (leatherman: /usr/include/boost/nowide/ are shipped by boost_1.74)

[Debian Bug Tracking System]

Your message dated Mon, 14 Dec 2020 17:05:19 +
with message-id 
and subject line Bug#975863: fixed in leatherman 1.12.1+dfsg-1.1
has caused the Debian Bug report #975863,
regarding leatherman: /usr/include/boost/nowide/ are shipped by boost_1.74
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.)


-- 
975863: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=975863
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: leatherman
Version: 1.12.1+dfsg-1
Severity: serious
Tags: patch
Justification: Policy 10.1
User: team+bo...@tracker.debian.org
Usertags: boost174

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Dear maintainer,

it was discovered that your package ships some
files, which are now shipped by libboost1.74-dev [1]:

/usr/include/boost/nowide/args.hpp
/usr/include/boost/nowide/cenv.hpp
/usr/include/boost/nowide/config.hpp
/usr/include/boost/nowide/convert.hpp
/usr/include/boost/nowide/cstdio.hpp
/usr/include/boost/nowide/cstdlib.hpp
/usr/include/boost/nowide/filebuf.hpp
/usr/include/boost/nowide/fstream.hpp
/usr/include/boost/nowide/integration/filesystem.hpp
/usr/include/boost/nowide/iostream.hpp
/usr/include/boost/nowide/stackstring.hpp
/usr/include/boost/nowide/system.hpp
/usr/include/boost/nowide/utf8_codecvt.hpp
/usr/include/boost/nowide/windows.hpp



I have prepared an updated version of your package with the fix
but it can only be uploaded after we start a transition to boost_1.74,
so libleatherman-dev can have libboost-nowide-dev in build-depends.


[1] https://packages.debian.org/sid/alpha/libboost1.74-dev/filelist

Best regards

Anton

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

Kernel: Linux 5.9.0-1-amd64 (SMP w/8 CPU threads)
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 not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

-BEGIN PGP SIGNATURE-

iQJFBAEBCgAvFiEEu71F6oGKuG/2fnKF0+Fzg8+n/wYFAl++1PIRHGdsYWRrQGRl
Ymlhbi5vcmcACgkQ0+Fzg8+n/waB/Q//fM6sQs9VHnXY831uV74rog1xJdXdUT/D
RM15+ITwY+IcZ88n7w1g5nWwsVBlL5MEfwHtw3ChXmAgMaYpbcFJZq9yT1xjwdW5
5pteEpZrb2KdFNPnkGFN/DmD0SqdRdF4ZN2AKV44pUJ8+64pGKXOFWfSXuOoRaV1
QDdE4IWVghwafaGHklIalfWElRuooj2VHIiW+oBX8jN61i+HVAQwRvX65G1nuISY
UtJ2Nu+NF4V+cB4NiMJAs/aUl6MgXwqyf+yLQVAz0A+RtBo+csfSf3KegY7QoiKY
gCOZAI6Qb01ha+N4bhQBE3oCR2hvtgjWWSulbZkdAhmYq8vY9RHhveRXbhtSBp39
ItnZrKVL6CyqwrUO+CeHM3FSOFWIolgFRLCn/tuRRHbEzksju+PerBmxpomaxpLr
Q1hw+/NoDs0keBa5QyuGpkaKZp1waDV0FQfJc8+YTAa98I7xi78LymASPw3EyHZZ
n4Bxzwqu1pwTS5NTYSxRpqqbRIpn060OlzxxQdsoH4rmINwCF2w+yDwGgtx0oSd2
r75kv7DXU6A4J9pXhAUPnixLjpJH2u54b7RvQ5yAXVNdIl5OCB4R7vTf4l21kRx4
MN44ulvoJM2+3m+xjRmtBPdQKcWOWTe5AEjvZBA9Z3liDAL8jVOWKnZC1Kmy+E37
QWXcNN4NqGw=
=u+Ew
-END PGP SIGNATURE-
--- End Message ---
--- Begin Message ---
Source: leatherman
Source-Version: 1.12.1+dfsg-1.1
Done: Anton Gladky 

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

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

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

Debian distribution maintenance software
pp.
Anton Gladky  (supplier of updated leatherman 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, 13 Dec 2020 23:11:38 +0100
Source: leatherman
Architecture: source
Version: 1.12.1+dfsg-1.1
Distribution: unstable
Urgency: medium
Maintainer: Puppet Package Maintainers 

Changed-By: Anton Gladky 
Closes: 975863
Changes:
 leatherman (1.12.1+dfsg-1.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * [517b59d] Add .gitlab-ci.yml
   * [37dd667] Use packaged libboost-nowide. (Closes: #975863)
Checksums-Sha1:
 d0a3e27b3d5894631223b77e9a7cab45a39b0719 2382 leatherman_1.12.1+dfsg-1.1.dsc
 d10c414eaa89c053324c60fe1877b40341ec6ca4 6776 
leatherman_1.12.1+dfsg-1.1.debian.tar.xz
 1e8191485db1baeb2e31e1767bcf814998ea59be 7410 
leatherman_1.12.1+dfsg-1.1_source.buildinfo
Checksums-Sha256:
 64f3a0112af162a7bf910d7ad9fc886486c8d8381dce1c1bef773d926bc49728 2382 

Bug#973848: chromium: Unsupported version, many security bugs unfixed

[Michel Le Bihan]

Hello,

My work is in this repo:
https://salsa.debian.org/mimi8/chromium/-/tree/master

I'm updating the commit every time I make a change. Making a new commit
for each file doesn't really make sense, since those are separate files
anyway.


There is another repo from another person that also started work:
https://github.com/berkley4/ungoogled-chromium-debian/commits/87.0.4280.88

And another one somebody told me about yesterday:
https://www.zap.org.au/git-browser/debian-packages/pkg-chromium-browser.git/

Could you please commit your work to a fork of the Chromium repo on
Salsa so we can compare patches?

Also, maybe we could meet on IRC/XMPP/Matrix or somewhere?

Michel Le Bihan

On Mon, 14 Dec 2020 13:12:06 +0100 Jan Luca Naumann  
wrote:
> Hallo everybody,
> 
> I have done some of the work as well since I have not seen your message
> about your efforts. I have uploaded a working build for unstable to
> mentors including updated version of the patches:
> 
> https://mentors.debian.net/package/chromium/
> 
> This version is using the vendor-shipped version of libvpx which should
> be changed but maybe we can put together the work done so far in a Git
> repo and fixes the remaining stuff?
> 
> Best,
> Jan
> 
> On Sun, 13 Dec 2020 14:45:01 -0800 David Worsham  wrote:
> >  Hi there,
> > 
> > Thank you for all of the great work on this so far!
> > 
> > I'm interested in helping with this effort, and very familiar with C++ code
> > and processes in Google code (though not specifically Chromium).  I have
> > gotten the 83/84 versions in unstable/experimental building locally in a
> > container as a sanity check.  I also have a fork on salsa to work from
> > now:  https://salsa.debian.org/arbreng/chromium
> > 
> > However, I am very new to Debian packaging and so not sure what the "ideal"
> > workspace setup and workflow is for this kind of work.  I just kinda made
> > things up as I went along yesterday.  If one of ya'll could walk me through
> > it that would be greatly appreciated - I only know what I learned from
> > the debian Wiki.  I know how to build and hack on Chromium itself -- it's
> > just the packaging bits that are still a bit mystifying to me.
> > 
> > Thanks again for all the effort!
> 
> 

Processed: tagging 921339, reassign 972422 to libarcus3, fixed 972422 in 4.7.1-2, affects 972422, tagging 972333

[Debian Bug Tracking System]

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

> tags 921339 + sid bullseye
Bug #921339 [psensor] Please switch to Ayatana AppIndicator
Added tag(s) bullseye and sid.
> reassign 972422 libarcus3 4.7.1-1
Bug #972422 {Done: Christoph Berg } [cura-engine] cura-engine: 
Segfault if using CuraEngine 4.7.1 with libarcus3 4.5
Bug reassigned from package 'cura-engine' to 'libarcus3'.
No longer marked as found in versions cura-engine/1:4.7.1-1.
No longer marked as fixed in versions libarcus/4.7.1-2.
Bug #972422 {Done: Christoph Berg } [libarcus3] cura-engine: 
Segfault if using CuraEngine 4.7.1 with libarcus3 4.5
Marked as found in versions libarcus/4.7.1-1.
> fixed 972422 4.7.1-2
Bug #972422 {Done: Christoph Berg } [libarcus3] cura-engine: 
Segfault if using CuraEngine 4.7.1 with libarcus3 4.5
Marked as fixed in versions libarcus/4.7.1-2.
> affects 972422 + cura-engine
Bug #972422 {Done: Christoph Berg } [libarcus3] cura-engine: 
Segfault if using CuraEngine 4.7.1 with libarcus3 4.5
Added indication that 972422 affects cura-engine
> tags 972333 - sid bullseye
Bug #972333 {Done: Sylvestre Ledru } 
[src:llvm-toolchain-11] llvm-toolchain-11: FTBFS on ppc64el: realloc(): invalid 
old size
Removed tag(s) bullseye and sid.
> thanks
Stopping processing here.

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

Bug#973848: chromium: Unsupported version, many security bugs unfixed

[Jeff Blake]

On Sat, 12 Dec 2020 19:47:32 +0100 Michel Le Bihan  wrote:
> Hello,
> 
> Thank you for your reply. libvpx got updated in Debian, but I can't use
> it because it's missing a lib. I also had issues with harfbuzz, so I'm
> using bundled versions of those libs as you are. I also used your ozone
> patch because it is match cleaner than mine. With that I was able to
> build Chromium, but with many lint errors and many missing patches.
> 
> BTW, have you tried opening a bug upstream or submitting your ozone
> patch upstream?
> 
> Michel Le Bihan

Hi,

I suspect that debian's libvpx might need to be build with experimental 
features enabled (similar to a previous bug report), in order to include 
the absent header files.

Are you sure that fixes/sequence-point.patch is necessary? I don't recall 
getting any warnings related to this when compiling.

Looking at the last couple of commits for the file affected by the ozone 
problem [1], it appears to be already fixed upstream.

[1] - https://tinyurl.com/yc8y4ah4


Regards,

Jeff

Bug#977390: src:vtk7: invalid maintainer address

[Ansgar]

Source: vtk7
Version: 7.1.1+dfsg2-5
Severity: serious
X-Debbugs-Cc: Gianfranco Costamagna 

The maintainer address is invalid, see below.

Ansgar

 Forwarded Message 
Subject: Mail delivery failed: returning message to sender
Date: Fri, 11 Dec 2020 22:07:20 +

> This message was created automatically by mail delivery software.
> 
> A message that you sent could not be delivered to one or more of its
> recipients. This is a permanent error. The following address(es)
> failed:
> 
>   debian-science-maintain...@lists.debian.org
>     host bendel.debian.org [2001:41b8:202:deb:216:36ff:fe40:4002]
>     SMTP error from remote mail server after RCPT
> TO::
>     550 5.1.1 :
>     Recipient address rejected: User unknown in virtual alias table

Bug#977348: marked as done (ulfius: missing runtime zlib dependency?)

[Debian Bug Tracking System]

Your message dated Mon, 14 Dec 2020 16:38:44 +
with message-id 
and subject line Bug#977348: fixed in ulfius 2.7.0-3
has caused the Debian Bug report #977348,
regarding ulfius: missing runtime zlib dependency?
to be marked as done.

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

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


-- 
977348: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977348
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ulfius
Version: 2.7.0-1
Severity: serious
tags: patch
affects: iddawc

Hello, looks like the new ulfius version is missing a zlib1g-dev dependency on 
the -dev package, leading to reverse-dependencies FTBFS in tests (e.g. in 
src:iddawc)

(Reading database ... 71222 files and directories currently installed.)
Removing autopkgtest-satdep (0) ...
autopkgtest [17:13:11]: test unit-test: [---
cd ../src && make debug
make[1]: Entering directory '/tmp/autopkgtest.Xwj6Nt/build.u2N/src/src'
Config file ../include/iddawc-cfg.h generated
gcc -c -pedantic -std=gnu99 -fPIC -Wall -Werror -Wextra -D_REENTRANT 
-I../include -DDEBUG -g -O0  iddawc.c
In file included from ../include/iddawc.h:34,
 from iddawc.c:30:
/usr/include/ulfius.h:49:12: fatal error: zlib.h: No such file or directory
   49 |   #include 
  |^~~~
compilation terminated.
make[1]: *** [Makefile:71: iddawc.o] Error 1
make[1]: Leaving directory '/tmp/autopkgtest.Xwj6Nt/build.u2N/src/src'
make: *** [Makefile:26: ../src/libiddawc.so] Error 2
autopkgtest [17:13:11]: test unit-test: ---]
unit-testFAIL non-zero exit status 2
autopkgtest [17:13:12]: test unit-test:  - - - - - - - - - - results - - - - - 
- - - - -
autopkgtest [17:13:12]:  summary
unit-testFAIL non-zero exit status 2
Exit request sent.
Creating nova instance adt-hirsute-amd64-iddawc-20201212-171139 from image 
adt/ubuntu-hirsute-amd64-server-20201212.img (UUID 
970e9eed-fd53-4251-b461-2b45c54f493a)...
--- End Message ---
--- Begin Message ---
Source: ulfius
Source-Version: 2.7.0-3
Done: Nicolas Mora 

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

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

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

Debian distribution maintenance software
pp.
Nicolas Mora  (supplier of updated ulfius 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, 14 Dec 2020 10:57:51 -0500
Source: ulfius
Architecture: source
Version: 2.7.0-3
Distribution: unstable
Urgency: medium
Maintainer: Debian IoT Maintainers 

Changed-By: Nicolas Mora 
Closes: 977348
Changes:
 ulfius (2.7.0-3) unstable; urgency=medium
 .
   * d/control: add libulfius-dev dependency zlib1g-dev (Closes: #977348)
Checksums-Sha1:
 18f6550668bf23af65966afe42117a9fdc5d29f3 2383 ulfius_2.7.0-3.dsc
 781902c3c52b71b982694cc1abbd123e12619eda 7108 ulfius_2.7.0-3.debian.tar.xz
 111c3df3fe131ddb7c53fa2e3c53a0e72f6b7285 8959 ulfius_2.7.0-3_amd64.buildinfo
Checksums-Sha256:
 a94665c56fe13437826640aa6c94c6a5ecca02c708ac4c479b3fe0da29e8f5a5 2383 
ulfius_2.7.0-3.dsc
 120fce5ee74e65bc840958ea6b028e500b544e056f35290efb9f9a7a708432ab 7108 
ulfius_2.7.0-3.debian.tar.xz
 caf27096f608d4d8d455c45b9f05310a4e766e9126e63cafa3b708053384479c 8959 
ulfius_2.7.0-3_amd64.buildinfo
Files:
 6178743313b91220333fc06d9f09ea16 2383 devel optional ulfius_2.7.0-3.dsc
 5f7cb1d227f2314d0fa9fa63c4788add 7108 devel optional 
ulfius_2.7.0-3.debian.tar.xz
 0fc140fc733bcfdbb474482deba8cac5 8959 devel optional 
ulfius_2.7.0-3_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEhAWwL8wo75dEyPJT/oITlEC9IrkFAl/Xi/sACgkQ/oITlEC9
Irlj0Q/9FLufhM0x5tUv2BykVdNXEiOdC5mTL6qF3Jz7MmcxAymcd4h+GmAZBzpt
MwXxozUNw5+x43owrYqOKvLkDG5Y3cCqN0NK+O/gHUIhlPDqA8qYs975bsOlXMUN
wXXW5IhxA2XwSpwoZ3B8fdmzcD+jYm1X55pkLW0uXzxrfF2uAcLblF5RO8yJPXTL
l3LicfuKGeD1DnTEHu+9m0MsiDM/rpKd51bcpDsP8iAYHC2otkzEaTvWCLYNw2Gq
3+qJtFTonYsMJuSzZQSTxAc9RER9pTiiKounnymEY78ARxl6ei0MFO4mJTnLl5eF
B4o2/cMqW0Lmx2g45oSaj92779IBVNZwb2EkS5r3OGAaJpB9bpKvtpRzkoAsWWJd
U9pP5sf4R52qVi7D/mRXgNDG/d5YEf8U6pTevwtpTrIPzDbvUQIoqMCmHUvwEhRA
7ZlbRTJc260o68K0RGjdR6z3wAdPBWrIAEVaLe5SZxCaN4r+CZj0sXclIdDyQW4N

Processed: tagging 973033

[Debian Bug Tracking System]

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

> tags 973033 + pending
Bug #973033 [src:python-molotov] python-molotov's autopkg tests are failing 
with python3.9
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#976549: marked as done (golang-github-robertkrimen-otto: FTBFS on arm64,ppc64el (arch:all-only src pkg): dh_auto_test: error: cd obj-aarch64-linux-gnu && go test -vet=off -v -p 4 github.com/robert

[Debian Bug Tracking System]

Your message dated Mon, 14 Dec 2020 15:22:33 +
with message-id 
and subject line Bug#976549: fixed in golang-github-robertkrimen-otto 
0.0~git20200922.ef014fd-1
has caused the Debian Bug report #976549,
regarding golang-github-robertkrimen-otto: FTBFS on arm64,ppc64el 
(arch:all-only src pkg): dh_auto_test: error: cd obj-aarch64-linux-gnu && go 
test -vet=off -v -p 4 github.com/robertkrimen/otto 
github.com/robertkrimen/otto/ast github.com/robertkrimen/otto/dbg 
github.com/robertkrimen/otto/file github.com/robertkrimen/otto/otto 
github.com/robertkrimen/otto/parser github.com/robertkrimen/otto/registry 
github.com/robertkrimen/otto/repl github.com/robertkrimen/otto/terst 
github.com/robertkrimen/otto/test github.com/robertkrimen/otto/token 
github.com/robertkrimen/otto/underscore 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.)


-- 
976549: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976549
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: golang-github-robertkrimen-otto
Version: 0.0~git20180617.15f95af-3
Severity: serious
Justification: FTBFS on arm64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201205 ftbfs-bullseye

Hi,

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

Relevant part (hopefully):
>  debian/rules build
> dh build --buildsystem=golang --with=golang
>dh_update_autotools_config -O--buildsystem=golang
>dh_autoreconf -O--buildsystem=golang
>dh_auto_configure -O--buildsystem=golang
>dh_auto_build -O--buildsystem=golang
>   cd obj-aarch64-linux-gnu && go install -trimpath -v -p 4 
> github.com/robertkrimen/otto github.com/robertkrimen/otto/ast 
> github.com/robertkrimen/otto/dbg github.com/robertkrimen/otto/file 
> github.com/robertkrimen/otto/otto github.com/robertkrimen/otto/parser 
> github.com/robertkrimen/otto/registry github.com/robertkrimen/otto/repl 
> github.com/robertkrimen/otto/terst github.com/robertkrimen/otto/test 
> github.com/robertkrimen/otto/token github.com/robertkrimen/otto/underscore
> internal/cpu
> runtime/internal/sys
> runtime/internal/atomic
> internal/unsafeheader
> runtime/internal/math
> internal/race
> sync/atomic
> internal/bytealg
> unicode
> unicode/utf8
> encoding
> math/bits
> internal/testlog
> runtime
> unicode/utf16
> math
> github.com/robertkrimen/otto/registry
> github.com/robertkrimen/otto/underscore
> container/list
> internal/nettrace
> runtime/cgo
> crypto/internal/subtle
> crypto/subtle
> vendor/golang.org/x/crypto/cryptobyte/asn1
> vendor/golang.org/x/crypto/internal/subtle
> internal/reflectlite
> sync
> math/rand
> internal/singleflight
> errors
> sort
> io
> internal/oserror
> strconv
> vendor/golang.org/x/net/dns/dnsmessage
> syscall
> bytes
> strings
> reflect
> gopkg.in/sourcemap.v1/base64vlq
> github.com/robertkrimen/otto/token
> bufio
> path
> internal/syscall/unix
> time
> internal/syscall/execenv
> regexp/syntax
> hash
> hash/crc32
> crypto
> crypto/internal/randutil
> internal/poll
> context
> regexp
> encoding/binary
> internal/fmtsort
> os
> crypto/hmac
> encoding/base64
> crypto/cipher
> crypto/sha512
> crypto/ed25519/internal/edwards25519
> crypto/md5
> fmt
> path/filepath
> net
> io/ioutil
> os/signal
> runtime/debug
> encoding/gob
> encoding/hex
> encoding/json
> net/url
> log
> github.com/robertkrimen/otto/dbg
> flag
> math/big
> gopkg.in/sourcemap.v1
> github.com/robertkrimen/otto/file
> runtime/trace
> github.com/robertkrimen/otto/ast
> testing
> github.com/robertkrimen/otto/parser
> compress/flate
> github.com/robertkrimen/otto/terst
> compress/gzip
> github.com/robertkrimen/otto
> crypto/aes
> crypto/des
> crypto/elliptic
> crypto/rand
> encoding/asn1
> crypto/ed25519
> crypto/rc4
> vendor/golang.org/x/crypto/cryptobyte
> crypto/rsa
> crypto/ecdsa
> crypto/sha1
> crypto/sha256
> crypto/dsa
> gopkg.in/readline.v1
> crypto/x509/pkix
> encoding/pem
> vendor/golang.org/x/crypto/chacha20
> crypto/x509
> vendor/golang.org/x/crypto/poly1305
> vendor/golang.org/x/crypto/chacha20poly1305
> vendor/golang.org/x/crypto/curve25519
> vendor/golang.org/x/crypto/hkdf
> vendor/golang.org/x/text/transform
> vendor/golang.org/x/text/unicode/bidi
> vendor/golang.org/x/text/unicode/norm
> crypto/tls
> vendor/golang.org/x/text/secure/bidirule
> net/textproto
> vendor/golang.org/x/net/http2/hpack
> vendor/golang.org/x/net/idna
> mime
> mime/quotedprintable
> github.com/robertkrimen/otto/otto
> github.com/robertkrimen/otto/repl
> vendor/golang.org/x/net/http/httpguts
> vendor/golang.org/x/net/http/httpproxy
> 

Bug#975533: mat2's autopkg tests fail with Python 3.9

[nicoo]

Hi,

There doesn't seem to be anyone else handling the mat2 RC bug (FTBFS &
autopkgtest failure) so I will do it.

AFAICT this is only a matter of importing the right upstream commit
(62ec8f6c1efc06364eb5f8c3d81e1b5dbcfc6e64) as a Debian patch.


Best,

  nicoo

On Mon, Nov 23, 2020 at 11:15:06AM +0100, Matthias Klose wrote:
> Package: src:mat2
> Version: 0.11.0-1
> Severity: serious
> Tags: sid bullseye
> User: debian-pyt...@lists.debian.org
> Usertags: python3.9
> 
> [...]
> autopkgtest [14:10:22]: test command1: [---
> = test session starts 
> ==
> platform linux -- Python 3.9.0+, pytest-4.6.11, py-1.9.0, pluggy-0.13.0
> rootdir: /tmp/autopkgtest-lxc.lpxn4tf6/downtmp/build.HJV/src
> collected 119 items
> 
> tests/test_climat2.py FF...  [ 
> 21%]
> tests/test_corrupted_files.py .. [ 
> 56%]
>  [ 
> 56%]
> tests/test_deep_cleaning.py .[ 
> 60%]
> tests/test_libmat2.py .. [ 
> 95%]
> tests/test_lightweight_cleaning.py ..[ 
> 97%]
> tests/test_policy.py ... 
> [100%]
> 
> === FAILURES 
> ===
> __ TestHelp.test_help 
> __
> 
> self = 
> 
> def test_help(self):
> proc = subprocess.Popen(mat2_binary + ['--help'], 
> stdout=subprocess.PIPE)
> stdout, _ = proc.communicate()
> self.assertIn(b'mat2 [-h] [-V]', stdout)
> self.assertIn(b'[--unknown-members policy]', stdout)
> self.assertIn(b'[--inplace]', stdout)
> self.assertIn(b'[--no-sandbox]', stdout)
> self.assertIn(b' [-v] [-l]', stdout)
> self.assertIn(b'[--check-dependencies]', stdout)
> self.assertIn(b'[-L | -s]', stdout)
> >   self.assertIn(b'[files [files ...]]', stdout)
> E   AssertionError: b'[files [files ...]]' not found in b"usage: mat2 [-h]
> [-V] [--unknown-members policy] [--inplace] [--no-sandbox]\n[-v]
> [-l] [--check-dependencies] [-L | -s]\n[files ...]\n\nMetadata
> anonymisation toolkit 2\n\npositional arguments:\n  files the
> files to process\n\noptional arguments:\n  -h, --helpshow this 
> help
> message and exit\n  -V, --verbose show more verbose status 
> information\n
>  --unknown-members policy\nhow to handle unknown 
> members
> of archive-style files\n(policy should be one of: 
> abort,
> omit, keep) [Default:\nabort]\n  --inplace
> clean in place, without backup\n  --no-sandbox  Disable bubblewrap's
> sandboxing\n  -v, --version show program's version number and exit\n
> -l, --listlist all supported fileformats\n  --check-dependencies
> check if mat2 has all the dependencies it needs\n  -L, --lightweight 
> remove
> SOME metadata\n  -s, --showlist harmful metadata detectable by 
> mat2
> without\nremoving them\n"
> 
> tests/test_climat2.py:32: AssertionError
> _ TestHelp.test_no_arg 
> _
> 
> self = 
> 
> def test_no_arg(self):
> proc = subprocess.Popen(mat2_binary, stdout=subprocess.PIPE)
> stdout, _ = proc.communicate()
> self.assertIn(b'mat2 [-h] [-V]', stdout)
> self.assertIn(b'[--unknown-members policy]', stdout)
> self.assertIn(b'[--inplace]', stdout)
> self.assertIn(b'[--no-sandbox]', stdout)
> self.assertIn(b' [-v] [-l] [--check-dependencies] [-L | -s]', stdout)
> >   self.assertIn(b'[files [files ...]]', stdout)
> E   AssertionError: b'[files [files ...]]' not found in b"usage: mat2 [-h]
> [-V] [--unknown-members policy] [--inplace] [--no-sandbox]\n[-v]
> [-l] [--check-dependencies] [-L | -s]\n[files ...]\n\nMetadata
> anonymisation toolkit 2\n\npositional arguments:\n  files the
> files to process\n\noptional arguments:\n  -h, --helpshow this 
> help
> message and exit\n  -V, --verbose show more verbose status 
> information\n
>  --unknown-members policy\nhow to handle unknown 
> members
> of archive-style files\n(policy should be one of: 
> abort,
> omit, keep) [Default:\nabort]\n  --inplace
> clean in place, without backup\n  --no-sandbox  Disable bubblewrap's
> sandboxing\n  -v, --version show program's version number and exit\n
> -l, --listlist all supported fileformats\n  --check-dependencies
> check if mat2 has all the dependencies it 

Bug#976902: marked as done (topydo: provides /usr/bin/todo with incompatible interface compared to devtodo)

[Debian Bug Tracking System]

Your message dated Mon, 14 Dec 2020 09:51:44 -0500
with message-id 

and subject line 
has caused the Debian Bug report #976902,
regarding topydo: provides /usr/bin/todo with incompatible interface compared 
to devtodo
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.)


-- 
976902: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976902
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: topydo
Version: 0.13-5
Severity: serious

Example use of `todo` from devtodo:

+---
| Add a task, like so:
|
| $ todo -a I should really update my homepage
|
| List all open tasks:
|
| $ todo
|
| Mark a task as complete:
|
| $ todo -d 1.2
+---[ https://swapoff.org/devtodo1.html ]

Example use of `topydo`:

+---
| topydo add "Water the flowers @Home rec:1w"
| topydo ls
| topydo do 2
+---[ https://github.com/topydo/topydo ]

But postinst registers topydo as an alternative for /usr/bin/todo.

Debian Policy[1] requires binaries with the same name to provide the
same functionality; given the command-line interfaces are
incompatible, this doesn't seem to be the case here.

I've reported this bug against topydo as it seems to just have taken
over the name, but already has topydo and wouldn't need to take over
the todo binary.

Ansgar

  [1]: https://www.debian.org/doc/debian-policy/ch-files.html#binaries
--- End Message ---
--- Begin Message ---
Version: 0.14-1
--- End Message ---

Bug#973171: marked as pending in scapy

[Sophie Brun]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/pkg-security-team/scapy/-/commit/a4bdedbe30fde8df7b9f8ef373b1fa0aed93aeff


Add a patch to fix issue with Python 3.9 (Closes: #973171)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/973171

Processed: Bug#973171 marked as pending in scapy

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #973171 [python3-scapy] dhcpcanon: FTBFS: dh_auto_test: error: pybuild 
--test --test-pytest -i python{version} -p "3.9 3.8" returned exit code 13
Added tag(s) pending.

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

Processed: Re: Bug#976552: dune-localfunctions: FTBFS: tests failed

[Debian Bug Tracking System]

Processing control commands:

> severity -1 minor
Bug #976552 [src:dune-localfunctions] dune-localfunctions: FTBFS on 
arm64,ppc64el (arch:all-only src pkg): tests failed
Severity set to 'minor' from 'serious'

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

Bug#976552: dune-localfunctions: FTBFS: tests failed

[Ansgar]

Control: severity -1 minor

On Sat, 2020-12-05 at 14:22 +0100, Lucas Nussbaum wrote:
> > 28/32 Test #28: test-orthonormal4 ***Failed
[...]
> > i = 115, j = 124: 1.33896e-09
> > i = 124, j = 115: 1.33896e-09
> >    FAILED !

These should be 0, but the epsilon for comparison seems to large for
arm64. Given arch:all packages are only built on amd64, I think this
shouldn't be release critical.

Ansgar

Bug#976916: dune-functions: FTBFS on ppc64el (arch:all-only src pkg): Dune reported error: Dune::Exception [testScalarBasisConst:/<>/dune/functions/functionspacebases/test/gridviewfunctio

[Ansgar]

Control: severity -1 minor

On Wed, 2020-12-09 at 09:58 +0100, Lucas Nussbaum wrote:
> > Error: integral value is wrong!

Probably some difference in floating-point arithmetic between amd64 and
ppc64el.  Given the error is only in a test and on ppc64el where Debian
doesn't build arch:all packages, I don't think it should be release
critical.

Ansgar

Processed: Re: Bug#976916: dune-functions: FTBFS on ppc64el (arch:all-only src pkg): Dune reported error: Dune::Exception [testScalarBasisConst:/<>/dune/functions/functionspacebases/test/

[Debian Bug Tracking System]

Processing control commands:

> severity -1 minor
Bug #976916 [src:dune-functions] dune-functions: FTBFS on ppc64el 
(arch:all-only src pkg): Dune reported error: Dune::Exception 
[testScalarBasisConst:/<>/dune/functions/functionspacebases/test/gridviewfunctionspacebasistest.cc:233]:
 Error: integral value is wrong!
Severity set to 'minor' from 'serious'

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

Bug#973848: chromium: Unsupported version, many security bugs unfixed

[Jan Luca Naumann]

Hallo everybody,

I have done some of the work as well since I have not seen your message
about your efforts. I have uploaded a working build for unstable to
mentors including updated version of the patches:

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

This version is using the vendor-shipped version of libvpx which should
be changed but maybe we can put together the work done so far in a Git
repo and fixes the remaining stuff?

Best,
Jan

On Sun, 13 Dec 2020 14:45:01 -0800 David Worsham  wrote:
>  Hi there,
> 
> Thank you for all of the great work on this so far!
> 
> I'm interested in helping with this effort, and very familiar with C++ code
> and processes in Google code (though not specifically Chromium).  I have
> gotten the 83/84 versions in unstable/experimental building locally in a
> container as a sanity check.  I also have a fork on salsa to work from
> now:  https://salsa.debian.org/arbreng/chromium
> 
> However, I am very new to Debian packaging and so not sure what the "ideal"
> workspace setup and workflow is for this kind of work.  I just kinda made
> things up as I went along yesterday.  If one of ya'll could walk me through
> it that would be greatly appreciated - I only know what I learned from
> the debian Wiki.  I know how to build and hack on Chromium itself -- it's
> just the packaging bits that are still a bit mystifying to me.
> 
> Thanks again for all the effort!

Bug#977357: libgdf ftbfs on s390x (test failures)

[Matthias Klose]

Package: src:libgdf
Version: 0.1.3-6
Severity: serious
Tags: sid bullseye

see
https://buildd.debian.org/status/fetch.php?pkg=libgdf=s390x=0.1.3-6=1606417737=0

stalls migration to testing.


[...]
43% tests passed, 4 tests failed out of 7

Total Test time (real) =   0.04 sec

The following tests FAILED:
  4 - testRWConsistency (Child aborted)
  5 - testSparseSampling (Child aborted)
  6 - testHeader3 (Child aborted)
  7 - testDataTypes (Child aborted)
Errors while running CTest
make[1]: *** [Makefile:152: test] Error 8
make[1]: Leaving directory '/<>/obj-s390x-linux-gnu'
dh_auto_test: error: cd obj-s390x-linux-gnu && make -j1 test ARGS\+=-j1 returned
exit code 2
make: *** [debian/rules:33: binary-arch] Error 25

Bug#957003: marked as done (aqemu: ftbfs with GCC-10)

[Debian Bug Tracking System]

Your message dated Mon, 14 Dec 2020 11:03:33 +
with message-id 
and subject line Bug#957003: fixed in aqemu 0.9.2-3
has caused the Debian Bug report #957003,
regarding aqemu: 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.)


-- 
957003: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957003
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:aqemu
Version: 0.9.2-2.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/aqemu_0.9.2-2.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

[...]
/<>/src/docopt/docopt.h:21:9: note:   no known conversion for 
argument 1 from ‘const char [43]’ to ‘docopt::DocoptLanguageError&&’
/<>/src/docopt/docopt.cpp: In function 
‘std::map, docopt::value> 
docopt::docopt_parse(const string&, const 
std::vector >&, bool, bool, bool)’:
/<>/src/docopt/docopt.cpp:1016:41: error: no matching function for 
call to ‘docopt::DocoptLanguageError::DocoptLanguageError(const char*)’
 1016 |   throw DocoptLanguageError(error.what());
  | ^
In file included from /<>/src/docopt/docopt.cpp:9:
/<>/src/docopt/docopt.h:21:9: note: candidate: ‘constexpr 
docopt::DocoptLanguageError::DocoptLanguageError()’
   21 |  struct DocoptLanguageError : std::runtime_error { using 
runtime_error::runtime_error; };
  | ^~~
/<>/src/docopt/docopt.h:21:9: note:   candidate expects 0 
arguments, 1 provided
/<>/src/docopt/docopt.h:21:9: note: candidate: ‘constexpr 
docopt::DocoptLanguageError::DocoptLanguageError(const 
docopt::DocoptLanguageError&)’
/<>/src/docopt/docopt.h:21:9: note:   no known conversion for 
argument 1 from ‘const char*’ to ‘const docopt::DocoptLanguageError&’
/<>/src/docopt/docopt.h:21:9: note: candidate: ‘constexpr 
docopt::DocoptLanguageError::DocoptLanguageError(docopt::DocoptLanguageError&&)’
/<>/src/docopt/docopt.h:21:9: note:   no known conversion for 
argument 1 from ‘const char*’ to ‘docopt::DocoptLanguageError&&’
/<>/src/docopt/docopt.cpp:1023:41: error: no matching function for 
call to ‘docopt::DocoptArgumentError::DocoptArgumentError(const char*)’
 1023 |   throw DocoptArgumentError(error.what());
  | ^
In file included from /<>/src/docopt/docopt.cpp:9:
/<>/src/docopt/docopt.h:24:9: note: candidate: ‘constexpr 
docopt::DocoptArgumentError::DocoptArgumentError()’
   24 |  struct DocoptArgumentError : std::runtime_error { using 
runtime_error::runtime_error; };
  | ^~~
/<>/src/docopt/docopt.h:24:9: note:   candidate expects 0 
arguments, 1 provided
/<>/src/docopt/docopt.h:24:9: note: candidate: ‘constexpr 
docopt::DocoptArgumentError::DocoptArgumentError(const 
docopt::DocoptArgumentError&)’
/<>/src/docopt/docopt.h:24:9: note:   no known conversion for 
argument 1 from ‘const char*’ to ‘const docopt::DocoptArgumentError&’
/<>/src/docopt/docopt.h:24:9: note: candidate: ‘constexpr 
docopt::DocoptArgumentError::DocoptArgumentError(docopt::DocoptArgumentError&&)’
/<>/src/docopt/docopt.h:24:9: note:   no known conversion for 
argument 1 from ‘const char*’ to ‘docopt::DocoptArgumentError&&’
/<>/src/docopt/docopt.cpp:1047:63: error: no matching function for 
call to 
‘docopt::DocoptArgumentError::DocoptArgumentError(std::__cxx11::basic_string)’
 1047 |   throw DocoptArgumentError("Unexpected argument: " + leftover);
  |   ^
In file 

Bug#977354: libmagics++-dev: Invalid dependency on "i" package

[Raphael Hertzog]

Package: libmagics++-dev
Version: 4.5.2-1
Severity: grave
Justification: renders package unusable

I was alerted by a strange log in the package tracker:
/usr/lib/python3/dist-packages/debian/deb822.py:1403: UserWarning: cannot parse 
package
relationship "i", returning it raw

I looked up what package would depend on "i" and I found libmagics++-dev:

$ apt show libmagics++-dev
Package: libmagics++-dev
Version: 4.5.2-1
Priority: optional
Section: libdevel
Source: magics++
Maintainer: Alastair McKinstry 
Installed-Size: 587 kB
Depends: libmagplus3v5 (= 4.5.2-1), i, python3, libmagics++-metview-dev, 
libterralib-dev, magics++, libodc-dev
[...]

Obviously that package doesn't exist and is not installable so your package
can't migrate.

Please upload a fixed package ASAP as it generates annoying noise
every 6 hours in my INBOX ;-)

Cheers,

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

Kernel: Linux 4.19.0-6-amd64 (SMP w/4 CPU threads)
Kernel taint flags: 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

-- 
  ⢀⣴⠾⠻⢶⣦⠀   Raphaël Hertzog 
  ⣾⠁⢠⠒⠀⣿⡁
  ⢿⡄⠘⠷⠚⠋The Debian Handbook: https://debian-handbook.info/get/
  ⠈⠳⣄   Debian Long Term Support: https://deb.li/LTS