Bug#948895: neomutt: FTBFS: test failure

[Andreas Henriksson]

Hello,

On Thu, Mar 12, 2020 at 05:25:50PM -0700, Stefano Rivera wrote:
> Control: reopen -1
> Control: notfixed -1 20191207+dfsg.1-1
[...]

If you're going to claim neomutt still FTBFS despite what
https://buildd.debian.org/status/package.php?p=neomutt
says, then I think you could atleast provide a build log backing up your
claim. (And even with that I'd personally likely not agree with your
claim that FTBFS on anything but official buildd is RC severity, but
that's up to the neomutt maintainers to finally decide on I guess.)

(IOW Please don't repurpose old bug reports when new ones are free.)

Regards,
Andreas Henriksson

Bug#953759: marked as done (debootstrap: mandatory security support breaks too many things)

[Debian Bug Tracking System]

Your message dated Fri, 13 Mar 2020 05:04:08 +
with message-id 
and subject line Bug#953759: fixed in debootstrap 1.0.122
has caused the Debian Bug report #953759,
regarding debootstrap: mandatory security support breaks too many things
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.)


-- 
953759: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953759
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: debootstrap
Version: 1.0.120
Severity: serious
Justification: RoM

Hi,

It seems my comments in [1] were ignored, so filing an RC bug to make
sure this is tracked at least by the BTS and britney.

 1. https://lists.debian.org/debian-boot/2020/03/msg00103.html

The latest batch of bug reports filed by Johannes 'josch' Schauer seems
to confirm my initial assessment: this will break (too) many use cases
(#953404, #953588, #953593, #953594, #953617).

Right now, my current plan would be:
 - creating a branch called “mandatory-security-support” (or something
   similar) at 1.0.121, so that people wanting to turn that into something
   suitable can try to do so, but I'm still unconvinced even having that as
   an option (disabled by default) would be appropriate, for all the
   problems that can come up when trying to drive apt.
 - remove support in master entirely, for the time being.

Rationale for plain removal is: we need to be able to upload debootstrap
with bugfixes, without having to suffer from all the side effects coming
from that recent change.


Cheers,
-- 
Cyril Brulebois (k...@debian.org)
D-I release manager -- Release team member -- Freelance Consultant
--- End Message ---
--- Begin Message ---
Source: debootstrap
Source-Version: 1.0.122
Done: Cyril Brulebois 

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

Debian distribution maintenance software
pp.
Cyril Brulebois  (supplier of updated debootstrap package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 13 Mar 2020 05:43:24 +0100
Source: debootstrap
Architecture: source
Version: 1.0.122
Distribution: unstable
Urgency: medium
Maintainer: Debian Install System Team 
Changed-By: Cyril Brulebois 
Closes: 953588 953593 953594 953617 953759
Changes:
 debootstrap (1.0.122) unstable; urgency=medium
 .
   * Revert the addition of (mandatory) security support as debootstrap's
 goal is to provide with a basic Debian system that many provisioning
 systems are built upon. Changing behaviour now seems to be doing a
 disservice to all those tools that would need adapting. In addition to
 not seeming to be a good idea, that triggers regressions for a number
 of use cases (Closes: #953759, #953588, #953593, #953594, #953617).
Checksums-Sha1:
 ff3186a084c91b776423003cba2b20343f58ed81 1919 debootstrap_1.0.122.dsc
 31ec8dddceb54dde4272d01a5dea8bd17ad195b8 77405 debootstrap_1.0.122.tar.gz
 66fa1b72d250953bf01529483bd36befc9473f20 6704 
debootstrap_1.0.122_source.buildinfo
Checksums-Sha256:
 88f92b2651d7884584a2739f2fe4b2a9cdc4e21ab2b306ccaafd96e009d542d1 1919 
debootstrap_1.0.122.dsc
 30711aa32868a1a7000da225b4abd71b32ef924c290619a443ac7ec2cf6c1f12 77405 
debootstrap_1.0.122.tar.gz
 6e3352b93fafe2f2bbc3ced4bff8f57e9fee3cd8708c45bc27266a65f075bf96 6704 
debootstrap_1.0.122_source.buildinfo
Files:
 63239e8f6874c545437be5c44b4e1f0a 1919 admin optional debootstrap_1.0.122.dsc
 30b4b8d3698f58f31c0e203b399dd9aa 77405 admin optional 
debootstrap_1.0.122.tar.gz
 cd2fa15b0de39a42e32a6f12750945f3 6704 admin optional 
debootstrap_1.0.122_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEtg6/KYRFPHDXTPR4/5FK8MKzVSAFAl5rECQACgkQ/5FK8MKz
VSC0Pg//YtBs9dYRiCYDnBPGxjh47aHvjQc3kzO6cib0CSH6L+MK5VLeWhI2z8bf
IZAEANqgETY/pWTPXsjmkr8WLIPNxvK6BOTtpyuxzWQDEbejSpCJ49XEF54ebCen
uzlBh3dbUygKlmJcYqV6Gk7F3fkkdUfWRRoigPeVE3qXNiIlhR8CKhiuPkGQWOrJ
Ole7HyoWboyGd8dKKlkl98jn1CSuK1fJXXGIZUJeUFJVtLkkN6kv9PbvE9Pcmgv7
g39CYehBddxp5Uwu/YqiwjIUhuJtej53cNEgqfFDlvVIsmwRXiGCi9TIwELFaTFI

Processed: Bug#953759 marked as pending in debootstrap

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #953759 [debootstrap] debootstrap: mandatory security support breaks too 
many things
Added tag(s) pending.

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

Bug#953759: marked as pending in debootstrap

[Cyril Brulebois]

Control: tag -1 pending

Hello,

Bug #953759 in debootstrap 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/installer-team/debootstrap/-/commit/da7dd6831bf3c36a8590cc1a6bce213d1213a616


Revert the addition of (mandatory) security support (Closes: #953759).

debootstrap's goal is to provide with a basic Debian system that many
provisioning systems are built upon. Changing behaviour now seems to be
doing a disservice to all those tools that would need adapting. In
addition to not seeming to be a good idea, that triggers regressions for
a number of use cases (also-Closes: #953588, #953593, #953594, #953617).


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/953759

Processed: found 953747 in 57.1-1

[Debian Bug Tracking System]

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

> # for the bts graph
> found 953747 57.1-1
Bug #953747 {Done: Laszlo Boszormenyi (GCS) } [src:icu] icu: 
CVE-2020-10531
Marked as found in versions icu/57.1-1.
> thanks
Stopping processing here.

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

Bug#953742: vim: FTBFS on armel, armhf, i386, mips64el, mipsel, s390x

[James McCoy]

On Thu, Mar 12, 2020 at 08:28:19PM +, Ivo De Decker wrote:
> The latest upload of vim to unstable fails on armel, armhf, i386, mips64el, 
> mipsel, s390x:
> 
> https://buildd.debian.org/status/package.php?p=vim

At least the 32-bit arch failures are understood and I've already given
upstream a fix.  Will upload a new version soon with that fix.

The others look like more of Vim's flaky tests, which I don't yet have a
good way to manage.

Cheers,
-- 
James
GPG Key: 4096R/91BF BF4D 6956 BD5D F7B7  2D23 DFE6 91AE 331B A3DB

Bug#953760: check-service autopkgtest fails while parsing systemctl output

[Michael Biebl]

Source: gpsd
Version: 3.20-5
Severity: serious

Hi,

the autopkgtest shipped by gpsd fails with the latest systemd v245
version:

https://ci.debian.net/data/autopkgtest/testing/amd64/g/gpsd/4543825/log.gz

One immediate problem is, that check-service tries to parse the
systemctl list-unit-files output, which gained a "VENDOR PRESET" column
in v245.

If you want to get the enabled state, my recommendation would be to use 
systemctl is-enabled $unit


The same goes for checking the active state: I would use
systemctl is-active $unit

Regards,
Michael


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

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

Bug#952366:

[Mybillserv Inc]

Model

Bug#953759: debootstrap: mandatory security support breaks too many things

[Steve McIntyre]

On Fri, Mar 13, 2020 at 02:26:04AM +0100, Cyril Brulebois wrote:
>Package: debootstrap
>Version: 1.0.120
>Severity: serious
>Justification: RoM
>
>Hi,
>
>It seems my comments in [1] were ignored, so filing an RC bug to make
>sure this is tracked at least by the BTS and britney.
>
> 1. https://lists.debian.org/debian-boot/2020/03/msg00103.html
>
>The latest batch of bug reports filed by Johannes 'josch' Schauer seems
>to confirm my initial assessment: this will break (too) many use cases
>(#953404, #953588, #953593, #953594, #953617).
>
>Right now, my current plan would be:
> - creating a branch called “mandatory-security-support” (or something
>   similar) at 1.0.121, so that people wanting to turn that into something
>   suitable can try to do so, but I'm still unconvinced even having that as
>   an option (disabled by default) would be appropriate, for all the
>   problems that can come up when trying to drive apt.
> - remove support in master entirely, for the time being.
>
>Rationale for plain removal is: we need to be able to upload debootstrap
>with bugfixes, without having to suffer from all the side effects coming
>from that recent change.

Sounds sensible enough to me...

-- 
Steve McIntyre, Cambridge, UK.st...@einval.com
We don't need no education.
We don't need no thought control.

Bug#953759: debootstrap: mandatory security support breaks too many things

[Cyril Brulebois]

Package: debootstrap
Version: 1.0.120
Severity: serious
Justification: RoM

Hi,

It seems my comments in [1] were ignored, so filing an RC bug to make
sure this is tracked at least by the BTS and britney.

 1. https://lists.debian.org/debian-boot/2020/03/msg00103.html

The latest batch of bug reports filed by Johannes 'josch' Schauer seems
to confirm my initial assessment: this will break (too) many use cases
(#953404, #953588, #953593, #953594, #953617).

Right now, my current plan would be:
 - creating a branch called “mandatory-security-support” (or something
   similar) at 1.0.121, so that people wanting to turn that into something
   suitable can try to do so, but I'm still unconvinced even having that as
   an option (disabled by default) would be appropriate, for all the
   problems that can come up when trying to drive apt.
 - remove support in master entirely, for the time being.

Rationale for plain removal is: we need to be able to upload debootstrap
with bugfixes, without having to suffer from all the side effects coming
from that recent change.


Cheers,
-- 
Cyril Brulebois (k...@debian.org)
D-I release manager -- Release team member -- Freelance Consultant

Bug#953747: marked as done (icu: CVE-2020-10531)

[Debian Bug Tracking System]

Your message dated Fri, 13 Mar 2020 01:19:44 +
with message-id 
and subject line Bug#953747: fixed in icu 66.1-2
has caused the Debian Bug report #953747,
regarding icu: CVE-2020-10531
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.)


-- 
953747: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953747
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: icu
Version: 63.2-2
Severity: grave
Tags: security upstream
Justification: user security hole
Forwarded: https://github.com/unicode-org/icu/pull/971

Hi,

The following vulnerability was published for icu.

CVE-2020-10531[0]:
| An issue was discovered in International Components for Unicode (ICU)
| for C/C++ through 66.1. An integer overflow, leading to a heap-based
| buffer overflow, exists in the UnicodeString::doAppend() function in
| common/unistr.cpp.


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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2020-10531
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-10531
[1] https://bugs.chromium.org/p/chromium/issues/detail?id=1044570 (not public)
[2] https://unicode-org.atlassian.net/browse/ICU-20958 (private)
[3] https://github.com/unicode-org/icu/pull/971
[4] 
https://github.com/unicode-org/icu/commit/b7d08bc04a4296982fcef8b6b8a354a9e4e7afca

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: icu
Source-Version: 66.1-2
Done: Laszlo Boszormenyi (GCS) 

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

Debian distribution maintenance software
pp.
Laszlo Boszormenyi (GCS)  (supplier of updated icu package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 13 Mar 2020 00:18:02 +
Source: icu
Architecture: source
Version: 66.1-2
Distribution: experimental
Urgency: high
Maintainer: Laszlo Boszormenyi (GCS) 
Changed-By: Laszlo Boszormenyi (GCS) 
Closes: 953747
Changes:
 icu (66.1-2) experimental; urgency=high
 .
   * Backport upstream security fix for CVE-2020-10531: SEGV_MAPERR in
 UnicodeString::doAppend() (closes: #953747).
Checksums-Sha1:
 bfa37f16cb015239c011c2622f1524147872f18e 2219 icu_66.1-2.dsc
 312e58407e7a8ea8bddcceb4000fa8d3e7919baa 25268 icu_66.1-2.debian.tar.xz
Checksums-Sha256:
 432957d8b62dc3add1c9f9f2c8925ebd59519404c87c2ea8768bf453d2da8a79 2219 
icu_66.1-2.dsc
 fb94f46b655af3ad0ce9d7e14ba24b4e72ae4fdb27b7fe8a36ba037f3a593b6e 25268 
icu_66.1-2.debian.tar.xz
Files:
 c4934c0292793482caa84cd76641d06f 2219 libs optional icu_66.1-2.dsc
 4e3a56d2e3f3148329ff832a60691025 25268 libs optional icu_66.1-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEfYh9yLp7u6e4NeO63OMQ54ZMyL8FAl5q20IACgkQ3OMQ54ZM
yL+GkhAAgCkq+ViUDO1QxaNj12GAIVuHkp/HA/uYN4lat1GQteKuKRWc8bBKi1Fz
bhjzHEV1Omz5zb7d44hI2Vwx3yeOPdxspWekGre+YaFvnM1Ue+I4V6yCubkA/fgn
4PGMXJ88G8DGTo9gKbNVvoxdqrif4tE+JevFe6fjbToVrUc0EPQWqozr09U8Mkmp
T3sxL3lH6bw8jO9XvznWU3NsmRhnKqDdMnckH2KGAIfPVpEMLxUi3cZTJROpMr+k
EM0NurehxXs4k0n7UBKaEMcTibbh9bXoF7joxq7SoaxwBvfbphaD0tySYYv/XId3
/PJwiVxYkmTze5TiQo1lKEMp7J/4hHLD4WBkEM//akx+cymhsgzZZwqrHUOrmzTf
LLrIYNTDfZt9Dp1yDCDxX3ewEAeXh62QElE/TqKHz9/hfXkrg8BYQVaSiAU3hG7G
PyHriRGXzvjDj7iwrQp+bxVvvLxvgk5TuJRh/lTZAD7A3SVIjQ8HtmEPX+KO7qbL
0ILCz1dtQGGqQWgyS2nEXkBXOJVwnO52kFPPRTuWUipcD58B2ux7kdeCwDhkiQck
j/RyTn9AP7eyXpqPn0u5Hya6iSD98uAdc1TJCtPJsRA1O8UjXmp/5cY2QKsdJG3x
X1ZZ/LEs0KBCc4TAgakDldaDvQtI5gBnGXFntVxoJhJcIoolpB4=
=HhKj
-END PGP SIGNATURE End Message ---

Bug#953747: marked as done (icu: CVE-2020-10531)

[Debian Bug Tracking System]

Your message dated Fri, 13 Mar 2020 01:04:28 +
with message-id 
and subject line Bug#953747: fixed in icu 63.2-3
has caused the Debian Bug report #953747,
regarding icu: CVE-2020-10531
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.)


-- 
953747: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953747
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: icu
Version: 63.2-2
Severity: grave
Tags: security upstream
Justification: user security hole
Forwarded: https://github.com/unicode-org/icu/pull/971

Hi,

The following vulnerability was published for icu.

CVE-2020-10531[0]:
| An issue was discovered in International Components for Unicode (ICU)
| for C/C++ through 66.1. An integer overflow, leading to a heap-based
| buffer overflow, exists in the UnicodeString::doAppend() function in
| common/unistr.cpp.


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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2020-10531
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-10531
[1] https://bugs.chromium.org/p/chromium/issues/detail?id=1044570 (not public)
[2] https://unicode-org.atlassian.net/browse/ICU-20958 (private)
[3] https://github.com/unicode-org/icu/pull/971
[4] 
https://github.com/unicode-org/icu/commit/b7d08bc04a4296982fcef8b6b8a354a9e4e7afca

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: icu
Source-Version: 63.2-3
Done: Laszlo Boszormenyi (GCS) 

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

Debian distribution maintenance software
pp.
Laszlo Boszormenyi (GCS)  (supplier of updated icu package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 13 Mar 2020 00:10:21 +
Source: icu
Architecture: source
Version: 63.2-3
Distribution: unstable
Urgency: high
Maintainer: Laszlo Boszormenyi (GCS) 
Changed-By: Laszlo Boszormenyi (GCS) 
Closes: 953747
Changes:
 icu (63.2-3) unstable; urgency=high
 .
   * Backport upstream security fix for CVE-2020-10531: SEGV_MAPERR in
 UnicodeString::doAppend() (closes: #953747).
Checksums-Sha1:
 412a8c4f8421d62085c66514f09bc6df9334d0c9 1965 icu_63.2-3.dsc
 ea5c73bcf4de9e7f7ac15315e41dd3ac23143ce1 35520 icu_63.2-3.debian.tar.xz
 cae41ff7481231e4e30e9ec82b782bef3e56ee43 8207 icu_63.2-3_amd64.buildinfo
Checksums-Sha256:
 7dc78f17c16387df8290f23bfd811faea030c21155d28ab460e429c581a41773 1965 
icu_63.2-3.dsc
 06b5b42f146a7cf39145db0b6582a108f1a8192326128f97a1181e726032ea2c 35520 
icu_63.2-3.debian.tar.xz
 256d54f8de7405650a2ec331af72c8090826e9fe49733ebdb14e668a297e319d 8207 
icu_63.2-3_amd64.buildinfo
Files:
 f4eb2c165f2cba9a173db2eeb659c193 1965 libs optional icu_63.2-3.dsc
 6d2d364f5b78105035a10467dac0c2db 35520 libs optional icu_63.2-3.debian.tar.xz
 c5cbe93176383366c9d3d65d1bce72df 8207 libs optional icu_63.2-3_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEfYh9yLp7u6e4NeO63OMQ54ZMyL8FAl5q2DMACgkQ3OMQ54ZM
yL9OuRAApGUj7WahYR3hhyKWErrSkHWWFGk8DraGAhWrMkIzhVT68q958wuMlC/v
y6Hknj198IBCHoT79oiWK0W+ymMvXU6J13M79qAqAvSi4zZi4peZH/Br+FQWEc+D
TiJVdKDCOK0hIUGc6UACPNJZ3hszNE1AhJ5vzWHDU5N0J2aNvjjgv7Z4tWrjkdDb
dl0F0HZluQ6DHGj3fnjWf7aeAgjC4JF6i/5hudMKMjLV3deguTnCFyjVs2wH0Rbp
HM0ykkNswMVzD0rgUT2reiVgjoo2AYv4v0bgzG3p4WWxHeBrVznTzhZ8Fq3/kDhD
ACzQ0oWxl7PIkrssm/x7+V0xoVkzveJMSylx61GqJFsHGJo3TmcvLCpI9uYBR4Hj
/k/C13KZFKSwh8B2KuJQ4xPYDrLEpptpzQuiadjHeUd685UnLWD0nmYrS2J+6gPK
+Gb2r6FDIjTSNFt8NRQchJXjgVzTFvwZUasVdJbs89+vYrtrFSKiLPw4d2RmBWUz
h+5R1Ti4mgFRXpMRL2thZGHsoyU72eiYfF/hGW9HsacM7BLgheiV+F1ABOra5KOf
QkpiL3ucfIUALgo6SRZoAzqCyD2FFgXADPlAGaV55O3G0hNUms48EKFeEr49Xj6S
6VlPaH3YrD/D8ogrnBsCO8TrMQRp40oD0zgbyshCqeTd48PYccg=
=UW73
-END PGP SIGNATURE End Message ---

Processed: Re: Bug#948895: neomutt: FTBFS: test failure

[Debian Bug Tracking System]

Processing control commands:

> reopen -1
Bug #948895 {Done: Andreas Henriksson } [src:neomutt] 
neomutt: FTBFS: test failure
'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 neomutt/20191207+dfsg.1-1.
> notfixed -1 20191207+dfsg.1-1
Bug #948895 [src:neomutt] neomutt: FTBFS: test failure
Ignoring request to alter fixed versions of bug #948895 to the same values 
previously set

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

Bug#948895: neomutt: FTBFS: test failure

[Stefano Rivera]

Control: reopen -1
Control: notfixed -1 20191207+dfsg.1-1

> This is fixed by:
> https://github.com/neomutt/neomutt/commit/6a98d598bf0443516146c6a856b965f5e0fb35a1#diff-80e4b64ac703024c17f04c3d0d014e40
> 
> In other words updating to the latest release (20191207) would
> fix this issue.

That is just one of the failures here.

Here's another one:
https://github.com/neomutt/neomutt/commit/26a6b07c728aa88414057cff257cdebfd2967907

SR

-- 
Stefano Rivera
  http://tumbleweed.org.za/
  +1 415 683 3272

Bug#951204: marked as done (libdleyna-core-1.0-5 can't be upgraded: trying to overwrite '/usr/lib/x86_64-linux-gnu/libdleyna-core-1.0.so.5.0.0', which is also in package libdleyna-core-1.0-3:amd64 0.6

[Debian Bug Tracking System]

Your message dated Thu, 12 Mar 2020 23:49:44 +
with message-id 
and subject line Bug#951204: fixed in dleyna-core 0.6.0-4
has caused the Debian Bug report #951204,
regarding libdleyna-core-1.0-5 can't be upgraded: trying to overwrite 
'/usr/lib/x86_64-linux-gnu/libdleyna-core-1.0.so.5.0.0', which is also in 
package libdleyna-core-1.0-3:amd64 0.6.0-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.)


-- 
951204: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=951204
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libdleyna-core-1.0-5
Version: 0.6.0-3
Severity: serious

Heya,

Disclaimer: this happened on Ubuntu and I haven't tried on Debian yet.
Not sure if this bug should be RC since this affects only people who
picked up 0.6.0-1 from experimental. (Ubuntu synced this so it's a more
important problem for us on that side.)

When upgrading, apt bombed out like this:

  Selecting previously unselected package libdleyna-core-1.0-5:amd64.^M
  Preparing to unpack .../064-libdleyna-core-1.0-5_0.6.0-3_amd64.deb ...^M
  Unpacking libdleyna-core-1.0-5:amd64 (0.6.0-3) ...^M
  dpkg: error processing archive 
/tmp/apt-dpkg-install-B5lolQ/064-libdleyna-core-1.0-5_0.6.0-3_amd64.deb 
(--unpack):
   trying to overwrite '/usr/lib/x86_64-linux-gnu/libdleyna-core-1.0.so.5.0.0', 
which is also in package libdleyna-core-1.0-3:amd64 0.6.0-1

Looks like a missing Breaks/Replaces: 0.6.0-1 had the bumped SONAME but
the package wasn't renamed until later, so there's a file conflict with
upgrades from that version only.

Cheers,

-- 
Iain Lane  [ i...@orangesquash.org.uk ]
Debian Developer   [ la...@debian.org ]
Ubuntu Developer   [ la...@ubuntu.com ]
--- End Message ---
--- Begin Message ---
Source: dleyna-core
Source-Version: 0.6.0-4
Done: Andreas Beckmann 

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

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

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

Debian distribution maintenance software
pp.
Andreas Beckmann  (supplier of updated dleyna-core package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 13 Mar 2020 00:32:08 +0100
Source: dleyna-core
Architecture: source
Version: 0.6.0-4
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: Andreas Beckmann 
Closes: 951204
Changes:
 dleyna-core (0.6.0-4) unstable; urgency=medium
 .
   * QA upload.
   * Breaks+Replaces: libdleyna-core-1.0-3 (>= 0.6.0)
 (Closes: #951204) (LP: #1862714, #1862757, #1862782)
   * Set Rules-Requires-Root: no.
   * Bump Standards-Version to 4.5.0.
Checksums-Sha1:
 d22f96ad67e06e7f9d3bcaa420e283d891dde3ca 2014 dleyna-core_0.6.0-4.dsc
 c8136cfdf03a8682fc592b5432870f8ecfb1f62e 4192 dleyna-core_0.6.0-4.debian.tar.xz
 251eef41dff245627d8c8545501496ca33df7709 8164 
dleyna-core_0.6.0-4_source.buildinfo
Checksums-Sha256:
 4f7c398a82c3f947b5d71528f1268f70f120610267259d78299f3ea71b0b3a23 2014 
dleyna-core_0.6.0-4.dsc
 c1d9a1ce04c0191caf7ade2012affdc6e9da747b62e35a376a0d1cd69ed943b2 4192 
dleyna-core_0.6.0-4.debian.tar.xz
 75cf12517d5b04a218bbd95d9d282e21ab361c27b22b933fbf47c952a9f130ac 8164 
dleyna-core_0.6.0-4_source.buildinfo
Files:
 207197e64e253f57e259838a23230eb0 2014 libs optional dleyna-core_0.6.0-4.dsc
 34609501c2f937062eff81b8d724ec97 4192 libs optional 
dleyna-core_0.6.0-4.debian.tar.xz
 404098dd93cc735bebf1b24fae49a971 8164 libs optional 
dleyna-core_0.6.0-4_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJEBAEBCAAuFiEE6/MKMKjZxjvaRMaUX7M/k1np7QgFAl5qx+EQHGFuYmVAZGVi
aWFuLm9yZwAKCRBfsz+TWentCPiGD/9ujVEveWl4Keh4jLP7QO2F/ejIy7h5h6Ty
HNqcFTaq1iRiZepsz9cYMasg23p27W6/0oGX0bKXippzJd6UvdseYmX/uGCtIISd
HT2mRpt3RHxrsEO50R1llYrAPHl91ha7XYLba/MDN1Dp7t1EtV/wTOaDl0LUpIQc
5G2H+kEoO8kbvGwM4jjsZJZ5h5ASMbTNOH95/71fb8tCwsqDmVY7kg2YyX/njaQ6
1ndY5vtsmXA3ySKtjNGyo5xt3e4Zde9XXqWlOB1XWHCqZdo4wJ4GV1zji+fUsU/Z
IK1rjeoX9rT+8O7Hk8OUucJJKxuupVyQM7SepAnVGqOe16N1R0coqzNr+SqFw/e1
Iwk5hb5Nl838Ge8dHi84z+nj6SsHCd8UEMTz08lX/clbZn2HpRNdhDHK2crDHW+U

Bug#905877: marked as done (regression in 1.4: upgrades random packages from testing to experimental (doesn't respect pinning?))

[Debian Bug Tracking System]

Your message dated Thu, 12 Mar 2020 23:34:52 +
with message-id 
and subject line Bug#905877: fixed in unattended-upgrades 2.0
has caused the Debian Bug report #905877,
regarding regression in 1.4: upgrades random packages from testing to 
experimental (doesn't respect pinning?)
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.)


-- 
905877: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=905877
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: unattended-upgrades
Version: 1.4
Severity: serious

Recently I have had unattended-upgrades upgrade random packages from
testing to experimental. If I downgrade the packages upgraded, I won't
get the same packages upgraded the next day. I run apt-show-versions
daily and save the output to my mail store. Using my mail store I found
that the first instance of this happening was on 2018-07-06, there were
earlier instances but they were from me manually installing packages
from experimental and u-u doing subsequent upgrades. I noticed that I
upgraded unattended-upgrades on that date from 1.3 to 1.4. I'm not
sure, but the changelog indicates some package candidate changes,
perhaps this caused the issue? I think this bug should be fixed before Debian 
releases buster, this could break some setups.

$ notmuch search --output files --format text0 subject:apt-show-versions AND 
experimental | xargs -0 grep -Zl ^+.*/experimental | xargs -0 grep ^Date:
grep: /home/pabs/mail/cur/1533911695.H364727P6217.chianamo:2,: No such file or 
directory
/home/pabs/mail/.archives.chianamo/cur/1533738479.H931450P19950.chianamo:2,S:Date:
 Wed, 08 Aug 2018 22:27:59 +0800
/home/pabs/mail/.archives.chianamo/cur/1533452480.H469089P20113.chianamo:2,S:Date:
 Sun, 05 Aug 2018 15:01:20 +0800
/home/pabs/mail/.archives.chianamo/cur/1532469048.H39195P10262.chianamo:2,S:Date:
 Wed, 25 Jul 2018 05:50:47 +0800
/home/pabs/mail/.archives.chianamo/cur/1532009473.H904807P26370.chianamo:2,S:Date:
 Thu, 19 Jul 2018 22:11:13 +0800
/home/pabs/mail/.archives.chianamo/cur/1531406466.H36620P31910.chianamo:2,S:Date:
 Thu, 12 Jul 2018 22:41:05 +0800
/home/pabs/mail/.archives.chianamo/cur/1531318643.H907159P2397.chianamo:2,S:Date:
 Wed, 11 Jul 2018 22:17:23 +0800
/home/pabs/mail/.archives.chianamo/cur/1531231937.H239897P6579.chianamo:2,S:Date:
 Tue, 10 Jul 2018 22:12:17 +0800
/home/pabs/mail/.archives.chianamo/cur/1531145728.H178673P15461.chianamo:2,S:Date:
 Mon, 09 Jul 2018 22:15:28 +0800
/home/pabs/mail/.archives.chianamo/cur/1530973747.H830435P12225.chianamo:2,S:Date:
 Sat, 07 Jul 2018 22:29:07 +0800
/home/pabs/mail/.archives.chianamo/cur/1530887497.H217865P26358.chianamo:2,S:Date:
 Fri, 06 Jul 2018 22:31:36 +0800
/home/pabs/mail/.archives.chianamo/cur/1528812402.H467547P3507.chianamo:2,S:Date:
 Tue, 12 Jun 2018 22:06:42 +0800
/home/pabs/mail/.archives.chianamo/cur/1528121929.H964004P25155.chianamo:2,S:Date:
 Mon, 04 Jun 2018 22:18:49 +0800
/home/pabs/mail/.archives.chianamo/cur/1527948341.H185749P9358.chianamo:2,S:Date:
 Sat, 02 Jun 2018 22:05:41 +0800
/home/pabs/mail/.archives.chianamo/cur/1527863815.H640051P20918.chianamo:2,S:Date:
 Fri, 01 Jun 2018 22:36:55 +0800
...

$ which-pkg-broke unattended-upgrades | grep -C3 'Jul *6'
libpython3.6-stdlib:amd64  Sun Jul  1 13:07:11 2018
python3.6-minimal  Sun Jul  1 13:07:14 2018
libpython3.6-minimal:amd64 Sun Jul  1 13:07:19 2018
unattended-upgradesFri Jul  6 21:03:10 2018
install-info   Sat Jul  7 12:22:43 2018
libapt-pkg5.0:amd64Mon Jul 16 15:38:37 2018
libapt-inst2.0:amd64   Mon Jul 16 15:38:43 2018

$ zgrep -B2 -A1 unattended-upgrades /var/log/apt/history.log.1.gz 
Start-Date: 2018-07-06  21:03:00
Requested-By: pabs (1000)
Upgrade: unattended-upgrades:amd64 (1.3, 1.4)
End-Date: 2018-07-06  21:03:21

unattended-upgrades (1.4) unstable; urgency=medium
...
  * Adjust candidates only for packages to be possibly installed
(Closes: #892028, #899366) (LP: #1396787)

-- System Information:
Debian Release: buster/sid
  APT prefers testing-debug
  APT policy: (900, 'testing-debug'), (900, 'testing'), (800, 
'unstable-debug'), (800, 'unstable'), (790, 'buildd-unstable'), (700, 
'experimental-debug'), (700, 'experimental'), (690, 'buildd-experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 4.17.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_AU.utf8, LC_CTYPE=en_AU.utf8 (charmap=UTF-8), 
LANGUAGE=en_AU.utf8 

Bug#952649: marked as done (uap-core: CVE-2020-5243)

[Debian Bug Tracking System]

Your message dated Thu, 12 Mar 2020 23:20:52 +
with message-id 
and subject line Bug#952649: fixed in uap-core 1:0.8.0-1
has caused the Debian Bug report #952649,
regarding uap-core: CVE-2020-5243
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.)


-- 
952649: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952649
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: uap-core
Version: 20190213-2
Severity: grave
Tags: security upstream

Hi,

The following vulnerability was published for uap-core.

CVE-2020-5243[0]:
| uap-core before 0.7.3 is vulnerable to a denial of service attack when
| processing crafted User-Agent strings. Some regexes are vulnerable to
| regular expression denial of service (REDoS) due to overlapping
| capture groups. This allows remote attackers to overload a server by
| setting the User-Agent header in an HTTP(S) request to maliciously
| crafted long strings. This has been patched in uap-core 0.7.3.


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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2020-5243
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-5243
[1] 
https://github.com/ua-parser/uap-core/security/advisories/GHSA-cmcx-xhr8-3w9p

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: uap-core
Source-Version: 1:0.8.0-1
Done: Edward Betts 

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

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

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

Debian distribution maintenance software
pp.
Edward Betts  (supplier of updated uap-core package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 12 Mar 2020 22:11:08 +
Source: uap-core
Binary: uap-core
Architecture: source all
Version: 1:0.8.0-1
Distribution: unstable
Urgency: medium
Maintainer: Edward Betts 
Changed-By: Edward Betts 
Description:
 uap-core   - User Agent Parser core - collection of regular expressions
Closes: 952649
Changes:
 uap-core (1:0.8.0-1) unstable; urgency=medium
 .
   * New upstream release Closes: #952649
 - CVE-2020-5243: Regular Expression Denial of Service
   * Switch from github master to github tag and add version epoch.
   * Update debian/watch to check for new github tag.
   * Update Standards-Version.
   * Set Rules-Requires-Root to no.
   * Use debhelper-compat instead of debian/compat.
   * Update copyright year.
   * Use git for debian packaging.
Checksums-Sha1:
 19f2cdbd317077cbaeea1598a3a934a65819ec18 1835 uap-core_0.8.0-1.dsc
 935d8eb91a0331c6c6b99c8f32080726ac534fa0 827193 uap-core_0.8.0.orig.tar.gz
 feb6f6b9ac816888404debb4d9cd7ab58627491d 2060 uap-core_0.8.0-1.debian.tar.xz
 5e0d7dc942616c12b6f5e378ddb42719ae3d86c6 41168 uap-core_0.8.0-1_all.deb
 030cc2ba4f22b80c87ef0e3633665acd5ff92b04 5618 uap-core_0.8.0-1_amd64.buildinfo
Checksums-Sha256:
 2cf2c2ce577ed7145a38733518174d9824205948849fcc96a84714e9195cddf3 1835 
uap-core_0.8.0-1.dsc
 765adef5f2fc212cd49200a0f8487d2e91617bcdbc459bfa38bf439e7db08022 827193 
uap-core_0.8.0.orig.tar.gz
 65924dca042363b3ea423b1c74322fdbe7169e7cadd87f9369026a9e4202a75a 2060 
uap-core_0.8.0-1.debian.tar.xz
 e915bf69ea7de389ce72dfdfb23c622b10983c2e8b151c88677a140137b2ca08 41168 
uap-core_0.8.0-1_all.deb
 556a741f3f4906c9552a478e842f6abb585de778d6f2c11de56189d48f37a148 5618 
uap-core_0.8.0-1_amd64.buildinfo
Files:
 65ed7ae403888267bd129efc6dc6b14e 1835 web optional uap-core_0.8.0-1.dsc
 4437d12b3ad5f59d7229cde2e2c73b43 827193 web optional uap-core_0.8.0.orig.tar.gz
 c75803c1b643c6840b94ffa42dfb0cef 2060 web optional 
uap-core_0.8.0-1.debian.tar.xz
 9bb8dff2bd62c28ba894abe88779a5c7 41168 web optional uap-core_0.8.0-1_all.deb
 a717440739a54531362344c74df76a8c 5618 web optional 
uap-core_0.8.0-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEE+4rPp4xyYInDitAmlgWhCYxjuSoFAl5qvxAACgkQlgWhCYxj
uSpQug//RR0fRMcyRd+7YV68Tp7GUiOmMylfGYvhPm5RMMbLrkZZbYS+M0GBp6Bg
DWaOB5A7CBJlh84DOWbAr38xlNh0EAvJtz4U3ZRxr+IfspJdGHqFu1aN4Hr3v3gb

Bug#942617: fixed in kexec-tools 1:2.0.20-2

[Ivo De Decker]

Hi,

On Thu, Mar 12, 2020 at 08:41:52PM +, Debian FTP Masters wrote:
> Architecture: source amd64

>  kexec-tools (1:2.0.20-2) unstable; urgency=medium
>  .
>* Fix FTBFS issue on x86 (Closes: #942617)

Thanks for fixing this bug.

Please note that you did a binary upload. To migrate to testing, all binaries
must be built on the buildds, so they must not be uploaded by the maintainer.

More info here:
https://lists.debian.org/debian-devel-announce/2019/07/msg2.html

I scheduled a binNMU to rebuild the amd64 binaries on the buildd for this
upload. That should allow this version to migrate. For future uploads, please
do a source-only upload.

Cheers,

Ivo

Bug#949887: munin autopkgtest failure for sysvinit based tests

[devel]

Hello Andreas,

just as Holger said: thank you for your detailed and helpful analysis!


On Fri, 7 Feb 2020 03:36:28 +0100 Andreas Henriksson  wrote:
>
> When the autopkgtest is booted into sysvinit I assume there's a
> race between the munin init script starting and the actual
> tests running.

you are right - it turns out that exactly this is happening.

I did some more digging in the autopkgtest code and I think, I found the
culprit: autopkgtest explicitly waits for systemd services to be ready (waiting
for "network-online.target"), but it does not wait for sysvinit services.

I proposed a patch against autopkgtest that solves this issue:
 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953655

Until this is fixed in autopkgtest, I added a conditional wait to munin's
test code. After some more dozens of successful tests runs I am convinced that
the issue is fixed.

Thank you for your help!

Cheers,
Lars

Bug#953744: marked as done (blender: FTBFS on mipsel)

[Debian Bug Tracking System]

Your message dated Thu, 12 Mar 2020 22:19:56 +
with message-id 
and subject line Bug#953744: fixed in blender 2.82+dfsg-2
has caused the Debian Bug report #953744,
regarding blender: FTBFS on mipsel
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.)


-- 
953744: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953744
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
package: src:blender
version: 2.82+dfsg-1
severity: serious
tags: ftbfs

Hi,

The latest upload of blender to unstable fails on mipsel:

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

Cheers,

Ivo
--- End Message ---
--- Begin Message ---
Source: blender
Source-Version: 2.82+dfsg-2
Done: m...@debian.org (Matteo F. Vescovi)

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

Debian distribution maintenance software
pp.
Matteo F. Vescovi  (supplier of updated blender package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 12 Mar 2020 22:41:23 +0100
Source: blender
Architecture: source
Version: 2.82+dfsg-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Multimedia Maintainers 
Changed-By: Matteo F. Vescovi 
Closes: 953744
Changes:
 blender (2.82+dfsg-2) unstable; urgency=medium
 .
   * debian/rules: fix FTBFS on mipsel (Closes: #953744)
Checksums-Sha1:
 5d2865eefefd133352ea794456cb7cfb13e6ff56 3060 blender_2.82+dfsg-2.dsc
 78fa32406e9ca2b842babc239a412e0d95dccefa 33184 
blender_2.82+dfsg-2.debian.tar.xz
 bb0dccf5c109b331c720ec08a1a05e00d38ec6e1 7656 
blender_2.82+dfsg-2_source.buildinfo
Checksums-Sha256:
 d39415df3bfa33178f0334f84c35ce245ec3f0a098e13adf292036a1035e3ee5 3060 
blender_2.82+dfsg-2.dsc
 74ebc2320f1cd100f5ba7662e4a8a721aad5bbc9a8fe6cdf5a42797096922563 33184 
blender_2.82+dfsg-2.debian.tar.xz
 ccb8098aae5c3a4fb3126ed83a5c27ac25b3a199fe36f6f3a909e4dbf886301e 7656 
blender_2.82+dfsg-2_source.buildinfo
Files:
 43165942d9009e749f5fbb34117f6eac 3060 graphics optional blender_2.82+dfsg-2.dsc
 c59dea96c86ca48253e06c5df8e8f2df 33184 graphics optional 
blender_2.82+dfsg-2.debian.tar.xz
 c53dd5ea5b6081eccbb4e4480846612c 7656 graphics optional 
blender_2.82+dfsg-2_source.buildinfo

-BEGIN PGP SIGNATURE-
Comment: Debian powered!

iQKTBAEBCgB9FiEE890J+NqH0d9QRsmbBhL0lE7NzVoFAl5qrO5fFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEYz
REQwOUY4REE4N0QxREY1MDQ2Qzk5QjA2MTJGNDk0NEVDRENENUEACgkQBhL0lE7N
zVqd7w/+J8YehKZHiOIzsJDkJClFnxq/rshk7Lt5rI67krH2m4pHHhwKFkhnYnwF
Sml7Bj43vMy0SAKEMr22ZI+Jc81OZAmdwrvH0HZL9k7im0BeN98vXF/m1Dj/qwb9
iEoDKtmGe0RakBU2+cyQqIgp39/xQT0D0fDebt3wg6i+fQm4A0dQke8xsRcDMMem
UnX3tlaXwcHeBMdPJ1dKRFvsOW5OoTTaosCtIiFoMfk5r6FSbA8KcXrEKbI3Woeo
1G6ufgC13wULdwenAKI0PtW7uSQMp3cXsz2OJeaq3l2Gn4ak0we2qHTgCKHWshAe
HIwj3uInCCtngy8AUHcwpS8i0zAzJtS5iXf5QJ13wWb/46pzPSR+4zBC3Ji+KO0X
uTj8focwn8n6DwepOFGyoWHUfXFV5ibfe1vjIS8SdOhP/AdgsOkbY7AkH9znlqFL
wkRXN8KMSj2lk7MWgMrXGgB7AOwIWtwnIkgsoMN/LlB4pMo6CzMgPuZMehm0xNhr
+Jf9k8uyfNSds3J6MP1w/kxNZk4cHbBAVUFpl/6M+TCpwk+4UbQXb1TXWHjgIukA
klr6K1GlXAA55aMvueDxvAR0ml9yROMRkQB5hrjwq+sTsExUHbDSCgtRteDHtvMj
14VnCFzHTp/GRx+7enQEo5ZO5bAg/cqp3eULkzvsw+sWYZmjE4o=
=/27G
-END PGP SIGNATURE End Message ---

Bug#953744: marked as pending in blender

[Matteo F. Vescovi]

Control: tag -1 pending

Hello,

Bug #953744 in blender 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/multimedia-team/blender/-/commit/33162c2cd10c22bb012937072cc8119bc6b89ad8


debian/rules: fix FTBFS on mipsel

Closes: #953744


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/953744

Processed: Bug#953744 marked as pending in blender

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #953744 [src:blender] blender: FTBFS on mipsel
Added tag(s) pending.

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

Bug#952811: [apt-cacher-ng] 500 Bad redirection (path)

[Eduard Bloch]

Control: severity 952811 important
Control: tags 952811 +upstream

Hallo,
* Eduard Bloch [Fri, Mar 06 2020, 07:48:22AM]:
> Control: tags 952811 +moreinfo
>
> Hallo,
> * Jean-Marc LACROIX [Sat, Feb 29 2020, 05:25:53PM]:
> > Package: apt-cacher-ng
> > Version: 3.2-2
> > Severity: grave
>
> That's hardly grave because not clearly reproducible. But I have seen
> this 502 in development a couple of times, appeared and disappeared
> without trace.
>
> Please share your config, i.e. all *.conf and *.backend files.

Thanks for the config but still not really reproducible. That said, I
see where the error message comes from and the code there is probably
not correct.

If you wish to rebuild your package with the fix, get this patch
https://salsa.debian.org/blade/apt-cacher-ng/-/commit/145e608a48c20ad2cd0d1a87ba63e3a9e32a62bc
or checkout the branch
https://salsa.debian.org/blade/apt-cacher-ng/-/tree/debian/sid_v3.3.x
or alternative I will probably make a release anyway in the next days.

Sorry for the delay.

Best regads,
Eduard.

--
"Lassen Sie sich 'Sklaventreiber' auf die Stirn tätowieren. Das ist
ehrlich, da wissen wir alle woran wir sind".
-- Volker Pispers

Processed: Re: Bug#952811: [apt-cacher-ng] 500 Bad redirection (path)

[Debian Bug Tracking System]

Processing control commands:

> severity 952811 important
Bug #952811 [apt-cacher-ng] [apt-cacher-ng] 500 Bad redirection (path)
Severity set to 'important' from 'grave'
> tags 952811 +upstream
Bug #952811 [apt-cacher-ng] [apt-cacher-ng] 500 Bad redirection (path)
Added tag(s) upstream.

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

Bug#952286: libpostscriptbarcode: FTBFS: GPL Ghostscript 9.50: Unrecoverable error, exit code 1

[Terry Burton]

On Sun, 23 Feb 2020 at 14:03, Lucas Nussbaum  wrote:
> During a rebuild of all packages in sid, your package failed to build
> on amd64.

As the package maintainer I acknowledge this bug and have prepared a
fixed source package that have been refreshed against upstream (also
me). This is currently being reviewed by the DD responsible for
uploading.

Thank you for alerting us of the issue.

Bug#953670: systemd: uncommanded switch to Plymouth boot screen

[Ben Caradoc-Davies]

Thanks, Michael. Confirmed fixed in 245-2.

For the record, the VT switch to tty1 occurred for me with 245-1 the 
first time apt-listbugs.timer ran, and only the first time. Not sure the 
exact causal chain for the switch, but it no longer occurs with 245-2, 
and plymouth is no longer on tty1.


Kind regards,

--
Ben Caradoc-Davies 
Director
Transient Software Limited 
New Zealand

Bug#953751: drf-extensions: autopkgtest failure: No module named 'djangorestframework_extensions'

[Paul Gevers]

Source: drf-extensions
Version: 0.6.0-1
X-Debbugs-CC: debian...@lists.debian.org
Severity: serious
User: debian...@lists.debian.org
Usertags: fails-always

Dear maintainers,

With a recent upload of drf-extensions you added an autopkgtest, great.
However, it fails. I copied some of the output at the bottom of this
report. You're using autodep8 to trigger the test, but it seems your
package naming and Python module name aren't aligned for autodep8.
autodep8 recently acquired a new feature that enables you to tell
autode8 what the real module name is that should be tested [1].

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

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

Paul

[1]
https://manpages.debian.org/unstable/autodep8/autodep8.1.en.html#PYTHON_PACKAGES
[2] https://qa.debian.org/excuses.php?package=drf-extensions

https://ci.debian.net/data/autopkgtest/testing/amd64/d/drf-extensions/4365527/log.gz
[1]
https://manpages.debian.org/unstable/autodep8/autodep8.1.en.html#PYTHON_PACKAGES

autopkgtest [03:10:46]: test autodep8-python3: set -e ; for py in
$(py3versions -r 2>/dev/null) ; do cd "$AUTOPKGTEST_TMP" ; echo "Testing
with $py:" ; $py -c "import djangorestframework_extensions;
print(djangorestframework_extensions)" ; done
autopkgtest [03:10:46]: test autodep8-python3: [---
Testing with python3.8:
Traceback (most recent call last):
  File "", line 1, in 
ModuleNotFoundError: No module named 'djangorestframework_extensions'
autopkgtest [03:10:46]: test autodep8-python3: ---]



signature.asc
Description: OpenPGP digital signature

Bug#953749: ceph: FTBFS on armel, armhf, i386, mips64el, mipsel, s390x

[Ivo De Decker]

package: src:ceph
version: 14.2.8-1
severity: serious
tags: ftbfs

Hi,

The latest upload of ceph to unstable fails on armel, armhf, i386, mips64el, 
mipsel, s390x:

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

Cheers,

Ivo

Processed: found 953747 in 63.1-6, found 953747 in 57.1-6+deb9u3, found 953747 in 57.1-6

[Debian Bug Tracking System]

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

> found 953747 63.1-6
Bug #953747 [src:icu] icu: CVE-2020-10531
Marked as found in versions icu/63.1-6.
> # I think this seems the case from a quick check:
> found 953747 57.1-6+deb9u3
Bug #953747 [src:icu] icu: CVE-2020-10531
Marked as found in versions icu/57.1-6+deb9u3.
> found 953747 57.1-6
Bug #953747 [src:icu] icu: CVE-2020-10531
Marked as found in versions icu/57.1-6.
> thanks
Stopping processing here.

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

Processed: found 953747 in 66.1-1

[Debian Bug Tracking System]

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

> found 953747 66.1-1
Bug #953747 [src:icu] icu: CVE-2020-10531
Marked as found in versions icu/66.1-1.
> thanks
Stopping processing here.

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

Bug#953748: cfgrib: autopkgtest failure: file or package not found: cfgrib

[Paul Gevers]

Source: cfgrib
Version: 0.9.7.7-1
X-Debbugs-CC: debian...@lists.debian.org
Severity: serious
User: debian...@lists.debian.org
Usertags: fails-always

Dear maintainers,

With a recent upload of cfgrib you added an autopkgtest, great. However,
it fails. I copied some of the output at the bottom of this report.

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

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

Paul

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

https://ci.debian.net/data/autopkgtest/testing/amd64/c/cfgrib/4362673/log.gz

autopkgtest [15:10:21]: test command1: set -e ; for py in $(py3versions
-r 2>/dev/null) ; do cd "$AUTOPKGTEST_TMP" ; echo "Testing with $py:" ;
$py -m pytest -v --pyargs cfgrib ; done
autopkgtest [15:10:21]: test command1: [---
Testing with python3.8:
= test session starts
==
platform linux -- Python 3.8.2rc2, pytest-4.6.9, py-1.8.1, pluggy-0.13.0
-- /usr/bin/python3.8
cachedir: .pytest_cache
rootdir: /tmp/autopkgtest-lxc.4u93syer/downtmp/autopkgtest_tmp
collecting ... collected 0 items

= no tests ran in 0.00 seconds
=
ERROR: file or package not found: cfgrib (missing __init__.py?)

autopkgtest [15:10:22]: test command1: ---]
autopkgtest [15:10:22]: test command1:  - - - - - - - - - - results - -
- - - - - - - -



signature.asc
Description: OpenPGP digital signature

Bug#953747: icu: CVE-2020-10531

[Salvatore Bonaccorso]

Source: icu
Version: 63.2-2
Severity: grave
Tags: security upstream
Justification: user security hole
Forwarded: https://github.com/unicode-org/icu/pull/971

Hi,

The following vulnerability was published for icu.

CVE-2020-10531[0]:
| An issue was discovered in International Components for Unicode (ICU)
| for C/C++ through 66.1. An integer overflow, leading to a heap-based
| buffer overflow, exists in the UnicodeString::doAppend() function in
| common/unistr.cpp.


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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2020-10531
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-10531
[1] https://bugs.chromium.org/p/chromium/issues/detail?id=1044570 (not public)
[2] https://unicode-org.atlassian.net/browse/ICU-20958 (private)
[3] https://github.com/unicode-org/icu/pull/971
[4] 
https://github.com/unicode-org/icu/commit/b7d08bc04a4296982fcef8b6b8a354a9e4e7afca

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore

Bug#936629: gnukhata-core-engine: Python2 removal in sid/bullseye

[Moritz Mühlenhoff]

On Wed, Mar 11, 2020 at 11:31:02AM +0530, Pirate Praveen wrote:
> 
> 
> On 2020, മാർച്ച് 11 3:18:36 AM IST, "Moritz Mühlenhoff"  
> wrote:
> >On Fri, Aug 30, 2019 at 07:19:09AM +, Matthias Klose wrote:
> >> Package: src:gnukhata-core-engine
> >> Version: 2.6.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.  Please stop using Python2, and fix this issue
> >> by one of the following actions.
> >
> >There hasn't been a gnukhata-core-engine upload since four years,
> >should it be removed or are you planning to port it to Python 3?
> 
> This was supposed to be removed after gnukhata-core was accepted, but that 
> did not happen. gnukhata-core also got removed for lack of python 3 support, 
> so this should be removed as well. Upstream is aware of the lack of python 3 
> support, but I don't know if they fixed it recently.

Ack, I've filed an RM bug.

Cheers,
Moritz

Bug#953744: blender: FTBFS on mipsel

[Ivo De Decker]

package: src:blender
version: 2.82+dfsg-1
severity: serious
tags: ftbfs

Hi,

The latest upload of blender to unstable fails on mipsel:

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

Cheers,

Ivo

Bug#942617: marked as done (FTBFS on i386)

[Debian Bug Tracking System]

Your message dated Thu, 12 Mar 2020 20:41:52 +
with message-id 
and subject line Bug#942617: fixed in kexec-tools 1:2.0.20-2
has caused the Debian Bug report #942617,
regarding FTBFS on i386
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.)


-- 
942617: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=942617
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: kexec-tools
Severity: serious
Version: 1:2.0.20-1

Hi,

kexec-tools failed to build on i386:

https://buildd.debian.org/status/fetch.php?pkg=kexec-tools=i386=1%3A2.0.20-1=1571349228=0

Regards,
Daniel
--- End Message ---
--- Begin Message ---
Source: kexec-tools
Source-Version: 1:2.0.20-2
Done: Khalid Aziz 

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

Debian distribution maintenance software
pp.
Khalid Aziz  (supplier of updated kexec-tools package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 12 Mar 2020 13:31:02 -0600
Source: kexec-tools
Binary: kexec-tools kexec-tools-dbgsym kexec-tools-udeb
Architecture: source amd64
Version: 1:2.0.20-2
Distribution: unstable
Urgency: medium
Maintainer: Khalid Aziz 
Changed-By: Khalid Aziz 
Description:
 kexec-tools - tools to support fast kexec reboots
 kexec-tools-udeb - tools to support fast kexec reboots (udeb) (udeb)
Closes: 942617
Changes:
 kexec-tools (1:2.0.20-2) unstable; urgency=medium
 .
   * Fix FTBFS issue on x86 (Closes: #942617)
Checksums-Sha1:
 b67d6d918de1800f92f87911802131630e70 2249 kexec-tools_2.0.20-2.dsc
 910dffbd37538f0a1467f1678357d9f105c26ca2 20568 
kexec-tools_2.0.20-2.debian.tar.xz
 661be23a04407ee997fa22157e788aa17a1b12fb 224748 
kexec-tools-dbgsym_2.0.20-2_amd64.deb
 b6d43ec8e19232a07974044fe4ffa8afecd38e80 57840 
kexec-tools-udeb_2.0.20-2_amd64.udeb
 d89971eacc82a7b54f525a58a564330b00325cce 6043 
kexec-tools_2.0.20-2_amd64.buildinfo
 78253f999fb056efaa88708f0131b2bf49cceeb9 85164 kexec-tools_2.0.20-2_amd64.deb
Checksums-Sha256:
 e4f478db274745ded5120a78204ec78cdda0df4dfb17639f43c615f6bd3e52cc 2249 
kexec-tools_2.0.20-2.dsc
 50e048b6a2826f81ea24e485318f3e0ef534ec0a80ac070458c6a2e50c406b6e 20568 
kexec-tools_2.0.20-2.debian.tar.xz
 feb2b5b9c58b3a716896cf1374cf38e2aed2054ed18a186236d8708657c6a131 224748 
kexec-tools-dbgsym_2.0.20-2_amd64.deb
 50de449ca3c57ed8e2be46cf37b9c394a5bc8e2d8b18e6f84b0fe20bc7923510 57840 
kexec-tools-udeb_2.0.20-2_amd64.udeb
 a76c5f5237c9311595e2556daf3f6bbb712945e3312ccc4e8e8b44ca0afe98a1 6043 
kexec-tools_2.0.20-2_amd64.buildinfo
 7cc9b268282da3611964de98609b13d57e77211814b60c817ddf1f77fb368adc 85164 
kexec-tools_2.0.20-2_amd64.deb
Files:
 5dcd8a5b707706fcc4b40400a311a6d3 2249 admin optional kexec-tools_2.0.20-2.dsc
 734379ff638b2905fad4e17019ee33f5 20568 admin optional 
kexec-tools_2.0.20-2.debian.tar.xz
 5f8b332e6ee0440fbe6e7f72aa4bf716 224748 debug optional 
kexec-tools-dbgsym_2.0.20-2_amd64.deb
 80b4f0e1377f0abed86883a36beb6507 57840 debian-installer optional 
kexec-tools-udeb_2.0.20-2_amd64.udeb
 2a49296faae5245aedf5500fb8e06258 6043 admin optional 
kexec-tools_2.0.20-2_amd64.buildinfo
 517989799fb471072847d246bb96bfcb 85164 admin optional 
kexec-tools_2.0.20-2_amd64.deb
Package-Type: udeb

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEELNgYv/ZGGerbWCE0zVihsX7QM/oFAl5qlXEACgkQzVihsX7Q
M/rsiQ/+L48nJduEN1+G+zWcT5Fu7rLOnYqJJi1sJXnneHTqTXcNjljjJMi3wfCA
n4634c9I8c9m1U8OgdO5MxtflrmllCLm5vtVogC3AZY8vsEn83uUGAJafNDoZukx
jE6vcuAhu254CqLRdhrpP5maFDjLk2aP149aZQzgK6rZouZhN9nsUDu03a7CQhtW
gjyTwwYzCDNbIaUcRu9fc5EwxUCc3zv/6rNqUeqiQODhIMPni7a+nZ0jmDq+Y9mR
rR8R5k5puuq1D/ZWTLT2+wsTkDMlRhpLHr67XDNzwkI4Dv4mt5opE7Ab+IR2xWmq
52l6Y8tiCIrN9fdeKsmVqCcPBZ8FxiPNXN/bCpOtVR8xvR2az4lazqV4YwATIUtT
UClweg3nsuCEiJBav1Fi2yYdPNxiwigh4o7fxk3+9ZwutGuQR5NT28GP5MSewX6s
2fkxjM35R06KTbdL1N6aqSoVTX+t72XN+1BjsU44MerC5FV4UXQKiVcpZ+2ghSJv
QMJ9+fWdsFfOD4oPb6ebyYYW0UXHyDy4AZVvNC1d9Posvle88DA8dAXykY8VyTu+
0Xij3sohtfiBxlFkwmeNpP7sFNhkNIXf5uIYZwhoyImcxNhvtVwDAC8+jKt8koif
5CgQ7zt/vTAp8FdLdax2a7ZjlQXpChXQqVnJuXsU7VmqkFlB4hE=
=YVUB
-END PGP SIGNATURE End Message ---

Bug#953742: vim: FTBFS on armel, armhf, i386, mips64el, mipsel, s390x

[Ivo De Decker]

package: src:vim
version: 2:8.2.0368-1
severity: serious
tags: ftbfs

Hi,

The latest upload of vim to unstable fails on armel, armhf, i386, mips64el, 
mipsel, s390x:

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

Cheers,

Ivo

Bug#951821: gegl: FTBFS on arm*/mips* architectures; testing migration blocked

[Boyuan Yang]

X-Debbugs-CC: andr...@fatal.se

Hi Andreas,

On Sun, 23 Feb 2020 00:05:54 +0100 Andreas Henriksson 
wrote:
> On Sat, Feb 22, 2020 at 06:23:36PM +0100, Andreas Henriksson wrote:
> > On Sat, Feb 22, 2020 at 05:21:08PM +0100, Andreas Henriksson wrote:
> > > Hello Boyuan Yang,
> > > 
> > > Thanks for your bug report.
> > > 
> > > On Sat, Feb 22, 2020 at 12:23:13AM -0500, Boyuan Yang wrote:
> > > > Source: gegl
> > > > Version: 0.4.18-2
> > > > Severity: serious
> > > > Justification: out-of-sync unstable-to-testing
> > > > X-Debbugs-CC: jbi...@debian.org
> > > [...]
> > 
> > FWIW I might have noticed that the problem is possibly related
> > to building on a single core machine rather than an arch- or
> > machinespeed-specific problem.
> > 
> > Atleast using MESON_TESTTHREADS=1 when running the test-suite makes
> > the gegl:simple / backend-file timeout for me.
> 
> Oh, SORRY! Actually it's the opposite. When running the tests in
> parallel the backend-file test times out.
> 
> I'm disabling parallel tests via 'dh_auto_test --no-parallel' now
> but it seems there are more test failures on the archs where
> the build failed previously.
> 
> Also see the previously filed bug #888769 for more (mips-specific?)
> investigations.

Any progress on it?  If it still takes much time, I suggest we force single-
thread build first and investigate later since the current FTBFS is blocking
many packages.

-- 
Thanks,
Boyuan Yang


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

Bug#952637: Close bug 952637

[Keith Packard]

Pirate Praveen  writes:

> On Mon, 09 Mar 2020 12:41:41 -0700 kei...@keithp.com ("Keith Packard") wrote:
>> 
>> Source: ruby-asciidoctor-pdf
>> Version: 1.5.3-1
>> 
>> Updated gemspec dependency on concurrent-ruby to ~> 1.1.0 which matches 1.1.6
>
> ~> 1.1 should be enough, see
> https://github.com/asciidoctor/asciidoctor-pdf/pull/1601

Thanks. I'll update the patch here and expect to delete it when
asciidoctor-pdf gets a new release.

-- 
-keith


signature.asc
Description: PGP signature

Bug#951938: marked as done (tigervnc: FTBFS: ./obj-x86_64-linux-gnu/unix/xserver/os/././unix/xserver/os/inputthread.c:321: undefined reference to `ddxInputThreadInit')

[Debian Bug Tracking System]

Your message dated Thu, 12 Mar 2020 19:06:21 +
with message-id 
and subject line Bug#951938: fixed in tigervnc 1.10.1+dfsg-2
has caused the Debian Bug report #951938,
regarding tigervnc: FTBFS: 
./obj-x86_64-linux-gnu/unix/xserver/os/././unix/xserver/os/inputthread.c:321: 
undefined reference to `ddxInputThreadInit'
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.)


-- 
951938: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=951938
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: tigervnc
Version: 1.10.1+dfsg-1
Severity: serious
Justification: FTBFS on amd64
Tags: buster sid
Usertags: ftbfs-20200222 ftbfs-buster

Hi,

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

Relevant part (hopefully):
> /usr/bin/ld: ../../os/.libs/libos.a(inputthread.o): in function 
> `InputThreadDoWork':
> ./obj-x86_64-linux-gnu/unix/xserver/os/././unix/xserver/os/inputthread.c:321: 
> undefined reference to `ddxInputThreadInit'
> collect2: error: ld returned 1 exit status

The full build log is available from:
   http://qa-logs.debian.net/2020/02/22/tigervnc_1.10.1+dfsg-1_unstable.log

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

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: tigervnc
Source-Version: 1.10.1+dfsg-2
Done: Joachim Falk 

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

Debian distribution maintenance software
pp.
Joachim Falk  (supplier of updated tigervnc 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: Thu, 12 Mar 2020 18:57:16 +0100
Source: tigervnc
Architecture: source
Version: 1.10.1+dfsg-2
Distribution: unstable
Urgency: medium
Maintainer: TigerVNC Packaging Team 
Changed-By: Joachim Falk 
Closes: 951938
Changes:
 tigervnc (1.10.1+dfsg-2) unstable; urgency=medium
 .
   [ Joachim Falk ]
   * Build fix for xorg-server-source 1.20.7, which moved ddxInputThread
 call from os layer into ddx layer (Closes: #951938).
Checksums-Sha1:
 60e6d0bdf7df0960ee3bca55c53910646b36d8d5 4007 tigervnc_1.10.1+dfsg-2.dsc
 3a949405785a03953ceae4c1d4907aab989f9318 59080 
tigervnc_1.10.1+dfsg-2.debian.tar.xz
 3d16a6333d8328e83ba4efc36d352946bdcfd227 6722 
tigervnc_1.10.1+dfsg-2_source.buildinfo
Checksums-Sha256:
 7a74e650e1cd1d127bfb5b56543f21a7ab6672fda695b17c7889cca6e97782e8 4007 
tigervnc_1.10.1+dfsg-2.dsc
 b7b978d3f590bf610199ff10122d72f273178885ebc6fbd747752a429e152c4b 59080 
tigervnc_1.10.1+dfsg-2.debian.tar.xz
 f59c5fffb67fd2f5a2c0560f217f0d8fd95efa637024da61936b9b7cd7a9542c 6722 
tigervnc_1.10.1+dfsg-2_source.buildinfo
Files:
 782c017fecca6975f7f1a40dba979131 4007 x11 optional tigervnc_1.10.1+dfsg-2.dsc
 68ff46ba07c50e78f20fbc68aafffe8e 59080 x11 optional 
tigervnc_1.10.1+dfsg-2.debian.tar.xz
 aaca475874e4e55b7aca72351cc78ca6 6722 x11 optional 
tigervnc_1.10.1+dfsg-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJIBAEBCAAyFiEEd0JxOxv4oYU15116MFSGLSVGoYAFAl5qgscUHGpvYWNoaW0u
ZmFsa0BnbXguZGUACgkQMFSGLSVGoYAGahAA2a5fKoctvnAVZ/KpW7bMBOWMjP2Z
jAJ8xonxkSlOOge8j2NG38Lza79PKAhC7zHSxu40mxOIooe8oO2FoxekvhqKdn7R
4VehFxal/akduc8afHvaJ7Qh7KhyhE+MDRvqJf5Db4OjTrD4G+01j3BT4taj8OfD
/xtvrUkEKy15mmP4dSHtNcPDEuIUkyhqJl7dnGmPEOak9G94UjvCq3wLCl2bF6Xa
qwImLo1GIEvtWLZ9hk9bCO9dCKyE4M+TrDlmwk0yZAZjjvELQckVxSuovtCmw3XN
Y2teDaPYzxsY2VWQ6cx4XZwH1TXwg57Y5I2adayF5KGA9GSJ6wJ+en2tDmkSxxvk
UMc71LtDew2sTtNJTIn3KP9m4dxvPpi5WE9edVZy4LojVFn9YMBtj+6NkX9c8izh
xuShX2cMPwY11m/z/KJgoqpwTn3g/s/O7qHG5r0Ud9AmCMvk3G1ikIWprMUBD7vQ
qnIOIy6Y8iw86q7avrWeiPvWLyEuN6ftNZwBs1dATKoIwC3c8CYRoO3YWf2LnIuu
a0cjkezdP6EmcXJ0Iu0KVvtOgEPC++OL8vrJhbLKZAsw2wZSyDwza6YwloizfUFB
Y4ej5jsU5QxFF//O2GuTfYPcd0iZUkRFEshNzQY6wc9o9x5hqFMzjmCQw6CCg5Ga
VXit4hVMrpXnsTw=
=/28e
-END PGP SIGNATURE End Message ---

Bug#953739: aac-tactics: FTBFS in sid

[Gianfranco Costamagna]

Source: aac-tactics
Version: 8.9.0-1
Severity: serious

Hello, looks like some changes in sid made aac-tactics FTBFS in sid, log is 
available here:
http://debomatic-amd64.debian.net/distribution#unstable/aac-tactics/8.9.0-1/buildlog

I: Running cd /build/aac-tactics-8.9.0/ && env 
PATH="/usr/sbin:/usr/bin:/sbin:/bin" HOME="/nonexistent" dpkg-buildpackage -us 
-uc 
dpkg-buildpackage: info: source package aac-tactics
dpkg-buildpackage: info: source version 8.9.0-1
dpkg-buildpackage: info: source distribution unstable
dpkg-buildpackage: info: source changed by Stéphane Glondu 
 dpkg-source --before-build .
dpkg-buildpackage: info: host architecture amd64
 debian/rules clean
dh clean --with ocaml
   debian/rules override_dh_auto_clean
make[1]: Entering directory '/build/aac-tactics-8.9.0'
/usr/bin/make clean
make[2]: Entering directory '/build/aac-tactics-8.9.0'
coq_makefile -f _CoqProject -o Makefile.coq
camlp5 macro files not supported anymore, please port src/aac.ml4 to coqpp
Usage summary:

coq_makefile  [file.v] ... [file.ml[ig]?] ... [file.ml{lib,pack}]
  ... [any] ... [-extra[-phony] result dependencies command]
  ... [-I dir] ... [-R physicalpath logicalpath]
  ... [-Q physicalpath logicalpath] ... [VARIABLE = value]
  ...  [-arg opt] ... [-opt|-byte] [-no-install] [-f file] [-o file]
  [-h] [--help]

Full list of options:

[file.v]: Coq file to be compiled
[file.ml[ig]?]: Objective Caml file to be compiled
[file.ml{lib,pack}]: ocamlbuild-style file that describes a Objective Caml
  library/module
[any] : subdirectory that should be "made" and has a Makefile itself
  to do so. Very fragile and discouraged.
[-extra result dependencies command]: add target "result" with command
  "command" and dependencies "dependencies". If "result" is not
  generic (do not contains a %), "result" is built by _make all_ and
  deleted by _make clean_.
[-extra-phony result dependencies command]: add a PHONY target "result"
 with command "command" and dependencies "dependencies". Note that
 _-extra-phony foo bar ""_ is a regular way to add the target "bar" as
 as a dependencies of an already defined target "foo".
[-I dir]: look for Objective Caml dependencies in "dir"
[-R physicalpath logicalpath]: look for Coq dependencies recursively
  starting from "physicalpath". The logical path associated to the
  physical path is "logicalpath".
[-Q physicalpath logicalpath]: look for Coq dependencies starting from
  "physicalpath". The logical path associated to the physical path
  is "logicalpath".
[VARIABLE = value]: Add the variable definition "VARIABLE=value"
[-byte]: compile with byte-code version of coq
[-opt]: compile with native-code version of coq
[-arg opt]: send option "opt" to coqc
[-install opt]: where opt is "user" to force install into user directory,
  "none" to build a makefile with no install target or
  "global" to force install in $COQLIB directory
[-f file]: take the contents of file as arguments
[-o file]: output should go in file file (recommended)
Output file outside the current directory is forbidden.
[-h]: print this usage summary
[--help]: equivalent to [-h]
make[2]: *** [Makefile:9: Makefile.coq] Error 1
make[2]: Leaving directory '/build/aac-tactics-8.9.0'
make[1]: *** [debian/rules:21: override_dh_auto_clean] Error 2
make[1]: Leaving directory '/build/aac-tactics-8.9.0'
make: *** [debian/rules:18: clean] Error 2
dpkg-buildpackage: error: debian/rules clean subprocess returned exit status 2
I: copying local configuration


Can you please have a look?

G.

Bug#953063: closed by Debian FTP Masters (reply to Andreas Tille ) (Bug#953063: fixed in mrtrix3 3.0~rc3+git135-g2b8e7d0c2-5)

[Moritz Muehlenhoff]

On Thu, Mar 12, 2020 at 02:42:07PM +, Debian Bug Tracking System wrote:
> This is an automatic notification regarding your Bug report
> which was filed against the src:mrtrix3 package:
> 
>* Architecture: any-amd64 arm64
>  Closes: #953063, #916284

JFTR; this also needs a bug against ftp.debian.org to remove the outdated i386 
binaries.

Cheers,
Moritz

Processed: Help to package nest-simulator to enable upgrading pynn

[Debian Bug Tracking System]

Processing control commands:

> tags -1 help
Bug #813821 [src:pynn] pynn: FTBFS: TypeError: 'float' object cannot be 
interpreted as an index
Added tag(s) help.

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

Bug#813821: Help to package nest-simulator to enable upgrading pynn

[Andreas Tille]

Control: tags -1 help

[debian-mentors readers please start reading at this mark @debian-mentors]

Hi Steffen,

I'm working on upgrading the Debian package of pynn.  While I assume the
latest upstream version of pynn will fix all Python3 migration issues it
also has the new dependency on nest-simulator.  Thus I commited
preliminary packaging for this to the Debian development Git[1].  Thanks
for your great initial work for Debian packaging inside the upstream
tarball.  I left you as Uploader in d/control and I hope you would like
to maintain the Debian packaging inside the Debian Med team who is
traditionally very welcoming to newcomers.  If you agree please register
at salsa.debian.org and ask for membership in the Debian Med team (or
ping me by mentioning your salsa user name).  If you agree the easiest
way for maintenance would be if you drop the debian/ dir from the
upstream source and we maintain it here directly with the goal of
uploadin it to official Debian (and from there propagating to all Debian
derivatives).


@debian-mentors

To update pynn to a Python3 aware version we need the new package
nest-simulator.  I've prepared the packaging[1] based on some work by
upstream (thanks for this Steffen).  Unfortunately I'm stumbling upon
ctest:

PATH=/build/nest-simulator-2.20.0/bin:/usr/sbin:/usr/bin:/sbin:/bin dh_auto_test
cd build && make -j4 test ARGS\+=-j4
make[2]: Entering directory '/build/nest-simulator-2.20.0/build'
Running tests...
/usr/bin/ctest --force-new-ctest-process -j4
Test project /build/nest-simulator-2.20.0/build
Start   1: selftests/test_pass.sli
Could not find executable /usr/bin/nest
Looked in the following places:
/usr/bin/nest
/usr/bin/nest
/usr/bin/Release/nest
/usr/bin/Release/nest
/usr/bin/Debug/nest
/usr/bin/Debug/nest
/usr/bin/MinSizeRel/nest


I wonder how I can tell ctest that the executable that is needed can be
found in /build/nest-simulator-2.20.0/bin.  Seems my means in d/rules

PATH=$(CURDIR)/bin:$(PATH) dh_auto_test

is not sufficient.

Any better idea?

Kind regards

  Andreas.

[1] https://salsa.debian.org/med-team/nest-simulator

-- 
http://fam-tille.de

Processed: Help to package nest-simulator to enable upgrading pynn

[Debian Bug Tracking System]

Processing control commands:

> tags -1 help
Bug #937491 [src:pynn] pynn: Python2 removal in sid/bullseye
Added tag(s) help.

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

Bug#952610: fixed in meson 0.53.2-2

[Jussi Pakkanen]

On Tue, 10 Mar 2020 at 11:30, Gianfranco Costamagna
 wrote:

> > Can you test if the issue is fixed fro you if you add
> > stderr=subprocess.DEVNULL to debcrossgen line 38?
> >
>
> ./debian/tests/crossbuild 1> /dev/null
> dpkg-architecture: warning: specified GNU system type arm-linux-gnueabihf 
> does not match CC system type x86_64-linux-gnu, try setting a correct CC 
> environment variable

D'oh, that line number should have been 83, not 38. :facepalm:

Bug#951944: ariba: FTBFS: dh_auto_test: error: pybuild --test --test-nose -i python{version} -p 3.7 returned exit code 13

[Andreas Tille]

Hi again,

On Wed, Mar 11, 2020 at 10:55:58AM +0100, Andreas Tille wrote:
> Hi again,
> 
> I've did a test build with fermi-lite 0.1-7[1].  I can confirm that ariba
> builds nicely against this version.  *All* build-time tests are running.
> I guess the spades test did not fail since spades is not in Build-Depends
> (hmmm, is it a bug that spades is neither in Build-Depends nor Depends or
> Recommends? Its not in the documentation but there are some references
> inside the code!)

I now found out that the change that affects ariba was done in fermi-lite
0.1-8 and reverted this very change in 0.1-10.  This might affect portability
but I think its a sensible tradeof to make sure we get ariba working again
on the important architectures.

So in principle we could close bug #951944 and give the package back for
rebuilding.  However, this does not help much for testing migration ...
 
> However, despite the build-time tests are running there are issues in
> autopkgtest.

... since the autopkgtest remains broken.  So we could rather try to
approach a new upload with fixed test which would trigger a new (now
hopefully successful test.)  I do not really have any clue how to fix
the test issue but I'm experimenting with some higher verbosity
currently.

Kind regards

  Andreas.

-- 
http://fam-tille.de

Processed: Bug#951938 marked as pending in tigervnc

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #951938 [src:tigervnc] tigervnc: FTBFS: 
./obj-x86_64-linux-gnu/unix/xserver/os/././unix/xserver/os/inputthread.c:321: 
undefined reference to `ddxInputThreadInit'
Added tag(s) pending.

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

Bug#951938: marked as pending in tigervnc

[Joachim Falk]

Control: tag -1 pending

Hello,

Bug #951938 in tigervnc 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/debian-remote-team/tigervnc/-/commit/f26dacf9ef856ce164627aad7882e76d202a88db


Build fix for xorg-server-source 1.20.7, which moved ddxInputThread call from 
os layer into ddx layer (Closes: #951938).


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/951938

Bug#953734: golang-golang-x-tools: FTBFS with golang-1.14

[Guillem Jover]

Source: golang-golang-x-tools
Source-Version: 1:0.0~git20200213.88e652f+ds-1
Severity: serious

Hi!

This package FTBFS with golang-1.14, and it built fine when downgrading to
golang-1.13:

  ,---
  === RUN   TestGorootTest
  […]
TestGorootTest: interp_test.go:136: Input: 
/usr/lib/go-1.14/test/recover2.go
  panic: (string, want: unhashable type main.T; have: runtime error: 
[]interp.value is unhashable)
  TestGorootTest: interp_test.go:187: interpreting 
/usr/lib/go-1.14/test/recover2.go: exit code was 2
  FAIL
  To trace execution, run:
  % go build golang.org/x/tools/cmd/ssadump && ./ssadump -build=C -test -run 
--interp=T /usr/lib/go-1.14/test/recover2.go

  --- FAIL: TestGorootTest (0.34s)
  FAIL
  FAIL  golang.org/x/tools/go/ssa/interp0.407s
  […]
  FAIL
  dh_auto_test: error: cd _build && go test -vet=off -v -p 8 -test.short 
golang.org/x/tools/benchmark/parse golang.org/x/tools/blog 
golang.org/x/tools/blog/atom golang.org/x/tools/cmd/auth/authtest 
golang.org/x/tools/cmd/auth/cookieauth golang.org/x/tools/cmd/auth/gitauth 
golang.org/x/tools/cmd/auth/netrcauth golang.org/x/tools/cmd/benchcmp 
golang.org/x/tools/cmd/bundle golang.org/x/tools/cmd/callgraph 
golang.org/x/tools/cmd/compilebench golang.org/x/tools/cmd/digraph 
golang.org/x/tools/cmd/eg golang.org/x/tools/cmd/fiximports 
golang.org/x/tools/cmd/getgo golang.org/x/tools/cmd/getgo/server 
golang.org/x/tools/cmd/go-contrib-init golang.org/x/tools/cmd/godex 
golang.org/x/tools/cmd/godoc golang.org/x/tools/cmd/goimports 
golang.org/x/tools/cmd/gomvpkg golang.org/x/tools/cmd/gorename 
golang.org/x/tools/cmd/gotype golang.org/x/tools/cmd/goyacc 
golang.org/x/tools/cmd/guru golang.org/x/tools/cmd/guru/serial 
golang.org/x/tools/cmd/html2article golang.org/x/tools/cmd/present 
golang.org/x/tools/cmd/splitdwarf 
golang.org/x/tools/cmd/splitdwarf/internal/macho golang.org/x/tools/cmd/ssadump 
golang.org/x/tools/cmd/stress golang.org/x/tools/cmd/stringer 
golang.org/x/tools/cmd/toolstash golang.org/x/tools/container/intsets 
golang.org/x/tools/cover golang.org/x/tools/go/analysis 
golang.org/x/tools/go/analysis/analysistest 
golang.org/x/tools/go/analysis/internal/analysisflags 
golang.org/x/tools/go/analysis/internal/checker 
golang.org/x/tools/go/analysis/internal/facts 
golang.org/x/tools/go/analysis/multichecker 
golang.org/x/tools/go/analysis/passes/asmdecl 
golang.org/x/tools/go/analysis/passes/assign 
golang.org/x/tools/go/analysis/passes/atomic 
golang.org/x/tools/go/analysis/passes/atomicalign 
golang.org/x/tools/go/analysis/passes/bools 
golang.org/x/tools/go/analysis/passes/buildssa 
golang.org/x/tools/go/analysis/passes/buildtag 
golang.org/x/tools/go/analysis/passes/cgocall 
golang.org/x/tools/go/analysis/passes/composite 
golang.org/x/tools/go/analysis/passes/copylock 
golang.org/x/tools/go/analysis/passes/ctrlflow 
golang.org/x/tools/go/analysis/passes/deepequalerrors 
golang.org/x/tools/go/analysis/passes/errorsas 
golang.org/x/tools/go/analysis/passes/findcall 
golang.org/x/tools/go/analysis/passes/findcall/cmd/findcall 
golang.org/x/tools/go/analysis/passes/httpresponse 
golang.org/x/tools/go/analysis/passes/inspect 
golang.org/x/tools/go/analysis/passes/internal/analysisutil 
golang.org/x/tools/go/analysis/passes/loopclosure 
golang.org/x/tools/go/analysis/passes/lostcancel 
golang.org/x/tools/go/analysis/passes/lostcancel/cmd/lostcancel 
golang.org/x/tools/go/analysis/passes/nilfunc 
golang.org/x/tools/go/analysis/passes/nilness 
golang.org/x/tools/go/analysis/passes/nilness/cmd/nilness 
golang.org/x/tools/go/analysis/passes/pkgfact 
golang.org/x/tools/go/analysis/passes/printf 
golang.org/x/tools/go/analysis/passes/shadow 
golang.org/x/tools/go/analysis/passes/shadow/cmd/shadow 
golang.org/x/tools/go/analysis/passes/shift 
golang.org/x/tools/go/analysis/passes/sortslice 
golang.org/x/tools/go/analysis/passes/stdmethods 
golang.org/x/tools/go/analysis/passes/structtag 
golang.org/x/tools/go/analysis/passes/testinggoroutine 
golang.org/x/tools/go/analysis/passes/tests 
golang.org/x/tools/go/analysis/passes/unmarshal 
golang.org/x/tools/go/analysis/passes/unmarshal/cmd/unmarshal 
golang.org/x/tools/go/analysis/passes/unreachable 
golang.org/x/tools/go/analysis/passes/unsafeptr 
golang.org/x/tools/go/analysis/passes/unusedresult 
golang.org/x/tools/go/analysis/singlechecker 
golang.org/x/tools/go/analysis/unitchecker golang.org/x/tools/go/ast/astutil 
golang.org/x/tools/go/ast/inspector golang.org/x/tools/go/buildutil 
golang.org/x/tools/go/callgraph golang.org/x/tools/go/callgraph/cha 
golang.org/x/tools/go/callgraph/rta golang.org/x/tools/go/callgraph/static 
golang.org/x/tools/go/cfg golang.org/x/tools/go/expect 
golang.org/x/tools/go/gccgoexportdata golang.org/x/tools/go/gcexportdata 
golang.org/x/tools/go/internal/cgo golang.org/x/tools/go/internal/gccgoimporter 
golang.org/x/tools/go/internal/gcimporter 
golang.org/x/tools/go/internal/packagesdriver golang.org/x/tools/go/loader 

Bug#953729: openafs: FTBFS on armhf

[Ivo De Decker]

package: src:openafs
version: 1.8.5-1
severity: serious
tags: ftbfs

Hi,

The latest upload of openafs to unstable fails on armhf:

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

Cheers,

Ivo

Bug#953728: gambc: FTBFS on s390x

[Ivo De Decker]

package: src:gambc
version: 4.9.3-1
severity: serious
tags: ftbfs

Hi,

The latest upload of gambc to unstable fails on s390x:

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

Cheers,

Ivo

Bug#952038: marked as done (nanoc: FTBFS: ERROR: Test "ruby2.5" failed: Failure/Error: it { is_expected.to eql output })

[Debian Bug Tracking System]

Your message dated Thu, 12 Mar 2020 16:04:34 +
with message-id 
and subject line Bug#952038: fixed in nanoc 4.11.0-4
has caused the Debian Bug report #952038,
regarding nanoc: FTBFS: ERROR: Test "ruby2.5" failed:  Failure/Error: it { 
is_expected.to eql output }
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.)


-- 
952038: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952038
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: nanoc
Version: 4.11.0-3
Severity: serious
Justification: FTBFS on amd64
Tags: buster sid
Usertags: ftbfs-20200222 ftbfs-buster

Hi,

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

Relevant part (hopefully):
>  Failure/Error: it { is_expected.to eql output }
> 
>expected: "before\n class=\"rouge-table\">\nfoo\n   class=\"k\">end\n\nafter\n"
> got: "before\n class=\"rouge-table\">\n\n   class=\"k\">end\n\n\nafter\n"
> 
>(compared using eql?)
> 
>Diff:
>@@ -4,7 +4,8 @@
> 2
> 
>   def  class="nf">foo
>-  end
>+  end
>+
> 
> after
>  # ./nanoc/spec/nanoc/filters/colorize_syntax/rouge_spec.rb:151:in `block 
> (5 levels) in '
>  # ./common/spec/spec_helper_foot.rb:27:in `block (4 levels) in  (required)>'
>  # 
> ./debian/nanoc/usr/share/rubygems-integration/all/gems/nanoc-4.11.0/lib/nanoc/spec.rb:10:in
>  `chdir'
>  # ./common/spec/spec_helper_foot.rb:27:in `block (3 levels) in  (required)>'
>  # ./common/spec/spec_helper_foot.rb:26:in `block (2 levels) in  (required)>'
>  # ./common/spec/spec_helper_foot.rb:16:in `block (2 levels) in  (required)>'
> 
> Finished in 40.95 seconds (files took 1.31 seconds to load)
> 2716 examples, 4 failures, 7 pending
> 
> Failed examples:
> 
> rspec ./nanoc/spec/nanoc/cli/commands/check_spec.rb:13 # 
> Nanoc::CLI::Commands::Check#run without options and arguments no issues for 
> any checks succeeds
> rspec ./nanoc/spec/nanoc/cli/commands/check_spec.rb:24 # 
> Nanoc::CLI::Commands::Check#run without options and arguments issues for 
> deploy check fails
> rspec ./nanoc/spec/nanoc/filters/colorize_syntax/rouge_spec.rb:72 # 
> Nanoc::Filters::ColorizeSyntax with Rouge with legacy with line number is 
> expected to eql "before\n class=\"rouge-table\">\nfoo\n   class=\"k\">end\n\nafter\n"
> rspec ./nanoc/spec/nanoc/filters/colorize_syntax/rouge_spec.rb:151 # 
> Nanoc::Filters::ColorizeSyntax with Rouge with formater with table is 
> expected to eql "before\n class=\"rouge-table\">\nfoo\n   class=\"k\">end\n\nafter\n"
> 
> /usr/bin/ruby2.5 
> -I/usr/share/rubygems-integration/all/gems/rspec-support-3.9.2/lib:/usr/share/rubygems-integration/all/gems/rspec-core-3.9.1/lib
>  /usr/share/rubygems-integration/all/gems/rspec-core-3.9.1/exe/rspec 
> --pattern ./nanoc/spec/\*\*/\*_spec.rb  --exclude-pattern 
> ./nanoc/spec/nanoc/\{filters/less_spec.rb,cli/commands/view_spec.rb\} -r 
> ./nanoc/spec/spec_helper.rb --color failed
> ERROR: Test "ruby2.5" failed: 

The full build log is available from:
   http://qa-logs.debian.net/2020/02/22/nanoc_4.11.0-3_unstable.log

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

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: nanoc
Source-Version: 4.11.0-4
Done: =?utf-8?q?C=C3=A9dric_Boutillier?= 

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

Debian distribution maintenance software
pp.
Cédric Boutillier  (supplier of updated nanoc package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 12 Mar 2020 14:14:23 +0100
Source: nanoc
Architecture: source
Version: 4.11.0-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Extras Maintainers 

Processed: xdebug breaks php-codecoverage autopkgtest: Class 'DOMDocument' not found

[Debian Bug Tracking System]

Processing control commands:

> found -1 xdebug/2.9.2+2.8.1+2.5.5-1
Bug #953727 [src:xdebug, src:php-codecoverage] xdebug breaks php-codecoverage 
autopkgtest: Class 'DOMDocument' not found
Marked as found in versions xdebug/2.9.2+2.8.1+2.5.5-1.
> found -1 php-codecoverage/7.0.10+dfsg-1
Bug #953727 [src:xdebug, src:php-codecoverage] xdebug breaks php-codecoverage 
autopkgtest: Class 'DOMDocument' not found
Marked as found in versions php-codecoverage/7.0.10+dfsg-1.

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

Bug#953727: xdebug breaks php-codecoverage autopkgtest: Class 'DOMDocument' not found

[Paul Gevers]

Source: xdebug, php-codecoverage
Control: found -1 xdebug/2.9.2+2.8.1+2.5.5-1
Control: found -1 php-codecoverage/7.0.10+dfsg-1
Severity: serious
Tags: sid bullseye
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: breaks needs-update

Dear maintainers,

With a recent upload of xdebug the autopkgtest of php-codecoverage fails
in testing when that autopkgtest is run with the binary packages of
xdebug from unstable. It passes when run with only packages from
testing. In tabular form:
   passfail
xdebug from testing2.9.2+2.8.1+2.5.5-1
php-codecoverage   from testing7.0.10+dfsg-1
all others from testingfrom testing

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

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

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

Paul

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

https://ci.debian.net/data/autopkgtest/testing/amd64/p/php-codecoverage/4525763/log.gz

autopkgtest [09:15:56]: test command1: mkdir --parents vendor ; cp
debian/autoload.php vendor ; phpunit
autopkgtest [09:15:56]: test command1: [---
Class 'DOMDocument' not found
autopkgtest [09:15:56]: test command1: ---]



signature.asc
Description: OpenPGP digital signature

Bug#953725: golang-golang-x-tools: Extremely generic and conflicting binary names

[Guillem Jover]

Package: golang-golang-x-tools
Version: 1:0.0~git20200213.88e652f+ds-1
Severity: serious

Hi!

I just noticed that this package contains a bunch of extremely generic
and in many cases conflicting program names. Ideally these would be
hidden behind a command dispatched (like «git » or similar), a
private bin/ directory (say under /usr/libexec// or similar), or
otherwise they should IMO be namespaced all with go, like it has
already been done with some of the programs:

Currently colliding:

  /usr/bin/authtest courier-authlib: /usr/sbin/authtest
  /usr/bin/bundle   ruby-bundler: /usr/bin/bundle
(many other ship their bundle program
 under /usr/share//bin/bundle)
  /usr/bin/eg   easygit: /usr/bin/eg
  /usr/bin/stress   stress: /usr/bin/stress

(!?):

  /usr/bin/benchcmp
  /usr/bin/callgraph
  /usr/bin/compilebench
  /usr/bin/cookieauth
  /usr/bin/digraph
  /usr/bin/findcall
  /usr/bin/fiximports
  /usr/bin/gitauth
  /usr/bin/helper
  /usr/bin/html2article
  /usr/bin/netrcauth
  /usr/bin/present
  /usr/bin/server
  /usr/bin/shadow
  /usr/bin/splitdwarf
  /usr/bin/unmarshal

Somewhat problematic:

  /usr/bin/guru
  /usr/bin/lostcancel
  /usr/bin/nilness
  /usr/bin/ssadump
  /usr/bin/stringer
  /usr/bin/toolstash

Thanks,
Guillem

Bug#952252: marked as done (wpebackend-fdo: FTBFS: /bin/sh: 1: client-header: not found)

[Debian Bug Tracking System]

Your message dated Thu, 12 Mar 2020 14:43:37 +
with message-id 
and subject line Bug#952252: fixed in wpebackend-fdo 1.6.0-1
has caused the Debian Bug report #952252,
regarding wpebackend-fdo: FTBFS: /bin/sh: 1: client-header: not found
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.)


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

Hi,

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

Relevant part (hopefully):
> make[3]: Entering directory '/<>/obj-x86_64-linux-gnu'
> [  6%] Generating bridge/wpe-bridge-protocol.c, 
> bridge/wpe-bridge-client-protocol.h, bridge/wpe-bridge-server-protocol.h
> < /<>/src/bridge/wpe-bridge.xml > 
> /<>/obj-x86_64-linux-gnu/bridge/wpe-bridge-protocol.c
> client-header < /<>/src/bridge/wpe-bridge.xml > 
> /<>/obj-x86_64-linux-gnu/bridge/wpe-bridge-client-protocol.h
> /bin/sh: 1: client-header: not found
> make[3]: *** [CMakeFiles/WPEBackend-fdo.dir/build.make:66: 
> bridge/wpe-bridge-protocol.c] Error 127

The full build log is available from:
   http://qa-logs.debian.net/2020/02/22/wpebackend-fdo_1.4.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!

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: wpebackend-fdo
Source-Version: 1.6.0-1
Done: Alberto Garcia 

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

Debian distribution maintenance software
pp.
Alberto Garcia  (supplier of updated wpebackend-fdo 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: Thu, 12 Mar 2020 14:51:33 +0100
Source: wpebackend-fdo
Architecture: source
Version: 1.6.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian WebKit Maintainers 

Changed-By: Alberto Garcia 
Closes: 952252
Changes:
 wpebackend-fdo (1.6.0-1) unstable; urgency=medium
 .
   * New upstream release.
   * Set the debhelper compatibility level to 12:
 + Get rid of debian/compat.
 + Add build dependency on debhelper-compat.
   * debian/control:
 + Add build dependency on libwayland-dev (Closes: #952252).
 + Add Rules-Requires-Root: no.
 + Update Standards-Version to 4.5.0 (no changes).
 + Require libwpe-1.0-dev >= 1.5.90.
   * debian/copyright:
 + Update copyright years.
   * debian/libwpebackend-fdo-1.0-1.symbols:
 + Update symbols.
   * Add upstream metadata file.
Checksums-Sha1:
 c97351c9cd493bde928fd673db58dfa223d9d984 2421 wpebackend-fdo_1.6.0-1.dsc
 d128e2c7ff273d9b9f31217f6ac25be3b266d805 35004 wpebackend-fdo_1.6.0.orig.tar.xz
 ab00f645390fb6189218c9e458df76ea320b561e 195 
wpebackend-fdo_1.6.0.orig.tar.xz.asc
 e9190ba8166d80306d76c44faf3522a78c4dfca4 6704 
wpebackend-fdo_1.6.0-1.debian.tar.xz
 0af0366d4176466473dabf660fac8ffbd096aa7e 9786 
wpebackend-fdo_1.6.0-1_source.buildinfo
Checksums-Sha256:
 458ef0ec4df5c84f25716694858eeef8c19d5bf120c89de190505565a9ed1a28 2421 
wpebackend-fdo_1.6.0-1.dsc
 7f5bd7b9d8f97b1655f4dcd39fad92719d0fb3985b251da5802df13aaa09f567 35004 
wpebackend-fdo_1.6.0.orig.tar.xz
 3ebe6ae999a888a50955588c853615997d3f711151845006c39e59f44a409e46 195 
wpebackend-fdo_1.6.0.orig.tar.xz.asc
 dd48d6bc4af5547d2115808848902d014fb328a198d2d4faa1ecee4c3ee53c07 6704 
wpebackend-fdo_1.6.0-1.debian.tar.xz
 fb4b8810cde4f898bcce8f0278d81c192da0b23e0d211b4742f707ae511d5c35 9786 
wpebackend-fdo_1.6.0-1_source.buildinfo
Files:
 36f8e31cc78a7916e21367e3c1c728ff 2421 libs optional wpebackend-fdo_1.6.0-1.dsc
 456afeed22f6749f7b2a97c11660835d 35004 libs optional 
wpebackend-fdo_1.6.0.orig.tar.xz
 

Bug#953063: marked as done (FTBFS on i386)

[Debian Bug Tracking System]

Your message dated Thu, 12 Mar 2020 14:39:15 +
with message-id 
and subject line Bug#953063: fixed in mrtrix3 3.0~rc3+git135-g2b8e7d0c2-5
has caused the Debian Bug report #953063,
regarding FTBFS on i386
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.)


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

mrtrix3 FTBFS on i386, which means that the stale i386 build still uses
Qt4.

There's the existing "#916284 mrtrix3 seems to be amd64-only", so I suggest
to simply restrict the arch list to amd64 and file an RM bug for the outdated
i386 binaries?

Cheers,
Moritz
--- End Message ---
--- Begin Message ---
Source: mrtrix3
Source-Version: 3.0~rc3+git135-g2b8e7d0c2-5
Done: Andreas Tille 

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

Debian distribution maintenance software
pp.
Andreas Tille  (supplier of updated mrtrix3 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: Thu, 12 Mar 2020 14:18:14 +0100
Source: mrtrix3
Architecture: source
Version: 3.0~rc3+git135-g2b8e7d0c2-5
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Andreas Tille 
Closes: 916284 949526 953063
Changes:
 mrtrix3 (3.0~rc3+git135-g2b8e7d0c2-5) unstable; urgency=medium
 .
   * Team upload.
   * Build-Depends: s/qtbase5-dev-tools/qtbase5-dev/
 Closes: #949526
   * Architecture: any-amd64 arm64
 Closes: #953063, #916284
   * Standards-Version: 4.5.0 (routine-update)
   * debhelper-compat 12 (routine-update)
   * Respect DEB_BUILD_OPTIONS in override_dh_auto_test target (routine-
 update)
   * Add salsa-ci file (routine-update)
   * Rules-Requires-Root: no (routine-update)
Checksums-Sha1:
 486c2f090f28b5ce36a7cc5deaed9766adf23228 2402 
mrtrix3_3.0~rc3+git135-g2b8e7d0c2-5.dsc
 7d9e9293e3f7a92a49d65ee959844e43a40f345f 44188 
mrtrix3_3.0~rc3+git135-g2b8e7d0c2-5.debian.tar.xz
 601f958e54b8c610209c407b30ecc540aea001cc 21115 
mrtrix3_3.0~rc3+git135-g2b8e7d0c2-5_source.buildinfo
Checksums-Sha256:
 f7ea83fbd97197bc39b7af25c139484d11b15729e2469b73ecdfaf5cf1b3db9e 2402 
mrtrix3_3.0~rc3+git135-g2b8e7d0c2-5.dsc
 9ad6c978c4a4843169e3d9267717d351fa16c2cad052a7587ade507a93f58f66 44188 
mrtrix3_3.0~rc3+git135-g2b8e7d0c2-5.debian.tar.xz
 3647e31db7380d5177d499095d7cb5c8411a34fc9dfc5ac0acd17d373e699a06 21115 
mrtrix3_3.0~rc3+git135-g2b8e7d0c2-5_source.buildinfo
Files:
 0d5847a4773da4745bc02a5b19b2216f 2402 science optional 
mrtrix3_3.0~rc3+git135-g2b8e7d0c2-5.dsc
 69414b5dcd841ed25de326cc91ebec52 44188 science optional 
mrtrix3_3.0~rc3+git135-g2b8e7d0c2-5.debian.tar.xz
 a5f8862afd06c5e427b2d4c3ed6ef7e6 21115 science optional 
mrtrix3_3.0~rc3+git135-g2b8e7d0c2-5_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJCBAEBCAAsFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAl5qQe8OHHRpbGxlYUBy
a2kuZGUACgkQV4oElNHGRtEISA/+PSg5JSxp4mznMx8QoNLP+dmNJQCMzmFxdtxl
eaU658xEBGdTBRS6ve+jRcU4cjOTiLlD2Kfx/dyvkST9iuaZd/CMZYrQh7+8WrLC
6t2gQ28bt7oQjpx+4vC2kc8uRSZqzSupzIithx7mE/vWHQy1HDb8LV50klIkVLgs
z30toW/wGlTLCEDbctJRrostNkGc7QVzAyUYOa1Pvrit6pQZqqJ6SOdBwZtRe3m5
ZYwu4kPh3NTXmiToNwA2zsGcw92FceasZJKNOalL8yJlPdJF6SxVpVajXjmFFCwp
gdcHsqE0FwwCxz6IhjcAY8ps9fvs7dGPxlLH45FDLxP0KwXwBL/u3mVeOsFcQnBm
WDMeT5ZolG+UXlpRKRueosL2qAuov8u8t3qVTaJ3UGqHl9tzq7pV+cK+ZzRDKgHf
wU13l4fg563IqLRYYnYI6ndF0CKTgmaefgUulxy08nvqNV2UvjgaBpGqP7r1jxa2
r8lFqwyXi2GrkSqQmTjWv4oLPSjHpTsFxLHekXuNxZ38qR0JE7BhaNVDw/6Q1ohr
e0XxzcFqrMqXv0tqog9pifPdgdVaejxHRdHUz6QR2E2jgZMS3bjGHuqg6+GRgWSj
ClpdxXBokOhku6wMZ4F723ZEovhHNo6xup7ZQOTUxkJj068SewnnJ5J0RJ2VtPtv
ZsPO2XU=
=F/F4
-END PGP SIGNATURE End Message ---

Bug#953670: marked as done (systemd: uncommanded switch to Plymouth boot screen)

[Debian Bug Tracking System]

Your message dated Thu, 12 Mar 2020 13:37:16 +
with message-id 
and subject line Bug#953670: fixed in systemd 245-2
has caused the Debian Bug report #953670,
regarding systemd: uncommanded switch to Plymouth boot screen
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.)


-- 
953670: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953670
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: systemd
Version: 245-1
Severity: critical
Justification: breaks the whole system

Dear Maintainer,

about 20 minutes after boot, regardless of what the user is doing, the
graphical desktop is replaced with an unresponsive Plymouth boot screen. It
looks like this is on virtual console one. The X desktop can be restored by
pressing Alt-F7. Users unaware that they can switch back to X with Alt-F7 are
completely locked out. Other virtual consoles can be selected. The system
remains up. Rogue timer?

Behaviour started today after upgrade:

libsystemd0:amd64 (244.3-1, 245-1)
udev:amd64 (244.3-1, 245-1)
libudev1:amd64 (244.3-1, 245-1)
libudev-dev:amd64 (244.3-1, 245-1)
systemd-sysv:amd64 (244.3-1, 245-1)
libpam-systemd:amd64 (244.3-1, 245-1)
systemd:amd64 (244.3-1, 245-1)
libnss-systemd:amd64 (244.3-1, 245-1)

journalctl contains these log entries for the time at which the uncommanded
switch occurs:

Mar 12 14:12:56 ripley systemd[1]: Condition check resulted in FUSE Control
File System being skipped.
Mar 12 14:12:56 ripley systemd[1]: Condition check resulted in Kernel
Configuration File System being skipped.
Mar 12 14:12:56 ripley systemd[1]: Starting Wait for network to be configured
by ifupdown...
Mar 12 14:12:56 ripley systemd[1]: Starting Tell Plymouth To Write Out Runtime
Data...
Mar 12 14:12:56 ripley systemd[1]: Starting Show Plymouth Boot Screen...
Mar 12 14:12:56 ripley systemd[1]: Condition check resulted in Set Up
Additional Binary Formats being skipped.
Mar 12 14:12:56 ripley systemd[1]: Condition check resulted in Store a System
Token in an EFI Variable being skipped.
Mar 12 14:12:56 ripley systemd[1]: Condition check resulted in Rebuild Hardware
Database being skipped.
Mar 12 14:12:56 ripley systemd[1]: Condition check resulted in Commit a
transient machine-id on disk being skipped.
Mar 12 14:12:56 ripley systemd[1]: Received SIGRTMIN+20 from PID 1439
(plymouthd).
Mar 12 14:12:56 ripley systemd[1]: Finished Wait for network to be configured
by ifupdown.
Mar 12 14:12:56 ripley systemd[1]: plymouth-read-write.service: Succeeded.
Mar 12 14:12:56 ripley systemd[1]: Finished Tell Plymouth To Write Out Runtime
Data.
Mar 12 14:12:56 ripley systemd[1]: Starting Network Manager Wait Online...
Mar 12 14:12:56 ripley systemd[1]: Finished Network Manager Wait Online.
Mar 12 14:12:56 ripley systemd[1]: Reached target Network is Online.
Mar 12 14:12:56 ripley systemd[1]: Starting Daily apt-listbugs preferences
cleanup...
Mar 12 14:12:56 ripley systemd[1]: apt-listbugs.service: Succeeded.
Mar 12 14:12:56 ripley systemd[1]: Finished Daily apt-listbugs preferences
cleanup.
Mar 12 14:12:56 ripley systemd[1]: Started Show Plymouth Boot Screen.

Kind regards,
Ben.



-- Package-specific info:

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

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

Versions of packages systemd depends on:
ii  adduser  3.118
ii  libacl1  2.2.53-6
ii  libapparmor1 2.13.3-7
ii  libaudit11:2.8.5-2+b1
ii  libblkid12.34-0.1
ii  libc62.29-10
ii  libcap2  1:2.32-1
ii  libcrypt11:4.4.15-1
ii  libcryptsetup12  2:2.3.0-1
ii  libgcrypt20  1.8.5-5
ii  libgnutls30  3.6.12-2
ii  libgpg-error01.37-1
ii  libidn2-02.3.0-1
ii  libip4tc21.8.4-3
ii  libkmod2 27-1
ii  liblz4-1 1.9.2-2
ii  liblzma5 5.2.4-1+b1
ii  libmount12.34-0.1
ii  libpam0g 1.3.1-5
ii  libpcre2-8-0 10.34-7
ii  libseccomp2  2.4.2-2
ii  libselinux1  3.0-1+b1
ii  libsystemd0  245-1
ii  mount2.34-0.1
ii  util-linux   2.34-0.1

Versions of packages systemd recommends:
ii  dbus  1.12.16-2

Versions of packages systemd suggests:
ii  policykit-10.105-26
pn  systemd-container  

Versions of packages systemd is related to:
pn  dracut   
ii  initramfs-tools  0.136
ii  libnss-systemd   245-1
ii  libpam-systemd   245-1

Bug#953670: marked as pending in systemd

[Michael Biebl]

Control: tag -1 pending

Hello,

Bug #953670 in systemd 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/systemd-team/systemd/-/commit/9967bfe5274fd9875834e25eff8e7741eaf48f95


Revert "job: Don't mark as redundant if deps are relevant"

This change negatively affects plymouth which was no longer properly
stopped after the system has completed booting. The running plymouth
daemon can trigger a VT switch (to tty1).

Closes: #953670


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/953670

Processed: Bug#953670 marked as pending in systemd

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #953670 [systemd] systemd: uncommanded switch to Plymouth boot screen
Added tag(s) pending.

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

Bug#951688: [Debian-in-workers] Bug#951688: no-change source-only upload to DELAYED/15 done

[Kartik Mistry]

On Thu, Mar 12, 2020 at 6:27 PM Paul Gevers  wrote:
> Hi,
>
> To fix this issue, I have just done a no-change source-only upload to
> DELAYED/15. Please let me know if I should delay or cancel the upload.

Hi Paul,

Please go ahead!

-- 
Kartik Mistry | કાર્તિક મિસ્ત્રી
kartikm.wordpress.com

Bug#951688: no-change source-only upload to DELAYED/15 done

[Paul Gevers]

Hi,

To fix this issue, I have just done a no-change source-only upload to
DELAYED/15. Please let me know if I should delay or cancel the upload.

Paul



signature.asc
Description: OpenPGP digital signature

Processed: Re: libgnatcoll-db: FTBFS on mipsel with assembler message: branch out of range

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #953069 [src:libgnatcoll-db] libgnatcoll-db: FTBFS on mipsel with assembler 
message: branch out of range
Severity set to 'serious' from 'normal'

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

Bug#949887: fixed in munin 2.0.56-1

[Michael Biebl]

Hi Holger, hi Lars

On Sat, 8 Feb 2020 16:12:40 +0100 Michael Biebl  wrote:
> Am 08.02.20 um 16:11 schrieb Michael Biebl:
> > The sysvinit based munin-cron still fails in 2.0.56-1 so re-opening
> > accordingly.
> 
> Sorry, meant master-cron:
> 
> 
> autopkgtest [04:00:42]:  summary
> master-cron  PASS
> master-cgi   PASS
> master-cron  FAIL non-zero exit status 1
> master-cgi   PASS
> node PASS
> command1 PASS


Could you also please disable the sysvinit based master-cron please?

https://ci.debian.net/data/autopkgtest/testing/amd64/m/munin/4531280/log.gz
is another instance of this test failing, making the autopkgtest results
unreliable for gating testing migration.

Regards,
Michael



signature.asc
Description: OpenPGP digital signature

Bug#953721: freecad: FTBFS with Python 3.8

[Graham Inggs]

Source: freecad
Version: 0.18.4+dfsg2-1
Severity: serious
Tags: ftbfs

Hi Maintainer

In a recent rebuild for Python 3.8, freecad FTBFS [1].
Ubuntu are carrying some patches which may be relevant [2].

Regards

Graham


[1] https://buildd.debian.org/status/package.php?p=freecad
[2] https://launchpad.net/ubuntu/+source/freecad/0.18.4+dfsg2-1ubuntu1

Processed: src:librdf-doap-perl: fails to migrate to testing for too long

[Debian Bug Tracking System]

Processing control commands:

> fixed -1 0.104-1
Bug #953718 [src:librdf-doap-perl] src:librdf-doap-perl: fails to migrate to 
testing for too long
Marked as fixed in versions librdf-doap-perl/0.104-1.

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

Bug#953719: src:libhandy: fails to migrate to testing for too long

[Paul Gevers]

Source: libhandy
Version: 0.0.10-1
Severity: serious
Control: fixed -1 0.0.12-1
Tags: sid bullseye
User: release.debian@packages.debian.org
Usertags: out-of-sync

Dear maintainer(s),

As recently announced [1], the Release Team now considers packages that
are out-of-sync between testing and unstable for more than 60 days as
having a Release Critical bug in testing. Your package src:libhandy in
its current version in unstable has been trying to migrate for 91 days
[2]. Hence, I am filing this bug.

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

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

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

If you believe your package is unable to migrate to testing due to
issues beyond your control, don't hesitate to contact the Release Team.

Paul

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




signature.asc
Description: OpenPGP digital signature

Processed: src:snek: fails to migrate to testing for too long

[Debian Bug Tracking System]

Processing control commands:

> fixed -1 1.3-1
Bug #953720 [src:snek] src:snek: fails to migrate to testing for too long
Marked as fixed in versions snek/1.3-1.

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

Bug#953720: src:snek: fails to migrate to testing for too long

[Paul Gevers]

Source: snek
Version: 1.1-1.1
Severity: serious
Control: fixed -1 1.3-1
Tags: sid bullseye
User: release.debian@packages.debian.org
Usertags: out-of-sync

Dear maintainer(s),

As recently announced [1], the Release Team now considers packages that
are out-of-sync between testing and unstable for more than 60 days as
having a Release Critical bug in testing. Your package src:snek in its
current version in unstable has been trying to migrate for 87 days [2].
Hence, I am filing this bug.

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

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

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

If you believe your package is unable to migrate to testing due to
issues beyond your control, don't hesitate to contact the Release Team.

Paul

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




signature.asc
Description: OpenPGP digital signature

Bug#953718: src:librdf-doap-perl: fails to migrate to testing for too long

[Paul Gevers]

Source: librdf-doap-perl
Version: 0.100-1
Severity: serious
Control: fixed -1 0.104-1
Tags: sid bullseye
User: release.debian@packages.debian.org
Usertags: out-of-sync

Dear maintainer(s),

As recently announced [1], the Release Team now considers packages that
are out-of-sync between testing and unstable for more than 60 days as
having a Release Critical bug in testing. Your package
src:librdf-doap-perl in its current version in unstable has been trying
to migrate for 92 days [2]. Hence, I am filing this bug.

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

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

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

If you believe your package is unable to migrate to testing due to
issues beyond your control, don't hesitate to contact the Release Team.

Paul

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




signature.asc
Description: OpenPGP digital signature

Processed: src:libhandy: fails to migrate to testing for too long

[Debian Bug Tracking System]

Processing control commands:

> fixed -1 0.0.12-1
Bug #953719 [src:libhandy] src:libhandy: fails to migrate to testing for too 
long
Marked as fixed in versions libhandy/0.0.12-1.

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

Bug#953717: src:gimp: fails to migrate to testing for too long

[Paul Gevers]

Source: gimp
Version: 2.10.12-1
Severity: serious
Control: fixed -1 2.10.14-2
Tags: sid bullseye
User: release.debian@packages.debian.org
Usertags: out-of-sync

Dear maintainer(s),

As recently announced [1], the Release Team now considers packages that
are out-of-sync between testing and unstable for more than 60 days as
having a Release Critical bug in testing. Your package src:gimp in its
current version in unstable has been trying to migrate for 111 days [2].
Hence, I am filing this bug.

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

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

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

If you believe your package is unable to migrate to testing due to
issues beyond your control, don't hesitate to contact the Release Team.

Paul

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




signature.asc
Description: OpenPGP digital signature

Processed: src:libvirt: fails to migrate to testing for too long

[Debian Bug Tracking System]

Processing control commands:

> fixed -1 5.6.0-3
Bug #953716 [src:libvirt] src:libvirt: fails to migrate to testing for too long
Marked as fixed in versions libvirt/5.6.0-3.

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

Processed: src:gimp: fails to migrate to testing for too long

[Debian Bug Tracking System]

Processing control commands:

> fixed -1 2.10.14-2
Bug #953717 [src:gimp] src:gimp: fails to migrate to testing for too long
Marked as fixed in versions gimp/2.10.14-2.

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

Bug#953716: src:libvirt: fails to migrate to testing for too long

[Paul Gevers]

Source: libvirt
Version: 5.6.0-2
Severity: serious
Control: fixed -1 5.6.0-3
Tags: sid bullseye
User: release.debian@packages.debian.org
Usertags: out-of-sync

Dear maintainer(s),

As recently announced [1], the Release Team now considers packages that
are out-of-sync between testing and unstable for more than 60 days as
having a Release Critical bug in testing. Your package src:libvirt in
its current version in unstable has been trying to migrate for 97 days
[2]. Hence, I am filing this bug.

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

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

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

If you believe your package is unable to migrate to testing due to
issues beyond your control, don't hesitate to contact the Release Team.

Paul

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




signature.asc
Description: OpenPGP digital signature

Processed: src:runescape: fails to migrate to testing for too long

[Debian Bug Tracking System]

Processing control commands:

> fixed -1 0.6-2
Bug #953714 [src:runescape] src:runescape: fails to migrate to testing for too 
long
The source 'runescape' and version '0.6-2' do not appear to match any binary 
packages
Marked as fixed in versions runescape/0.6-2.

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

Bug#953714: src:runescape: fails to migrate to testing for too long

[Paul Gevers]

Source: runescape
Version: 0.5-1
Severity: serious
Control: fixed -1 0.6-2
Tags: sid bullseye
User: release.debian@packages.debian.org
Usertags: out-of-sync

Dear maintainer(s),

As recently announced [1], the Release Team now considers packages that
are out-of-sync between testing and unstable for more than 60 days as
having a Release Critical bug in testing. Your package src:runescape in
its current version in unstable has been trying to migrate for 120 days
[2]. Hence, I am filing this bug.

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

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

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

If you believe your package is unable to migrate to testing due to
issues beyond your control, don't hesitate to contact the Release Team.

Paul

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




signature.asc
Description: OpenPGP digital signature

Processed: src:transgui: fails to migrate to testing for too long

[Debian Bug Tracking System]

Processing control commands:

> fixed -1 5.18.0+dfsg-1
Bug #953713 [src:transgui] src:transgui: fails to migrate to testing for too 
long
Marked as fixed in versions transgui/5.18.0+dfsg-1.

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

Bug#953713: src:transgui: fails to migrate to testing for too long

[Paul Gevers]

Source: transgui
Version: 5.17.0+dfsg-1
Severity: serious
Control: fixed -1 5.18.0+dfsg-1
Tags: sid bullseye
User: release.debian@packages.debian.org
Usertags: out-of-sync

Dear maintainer(s),

As recently announced [1], the Release Team now considers packages that
are out-of-sync between testing and unstable for more than 60 days as
having a Release Critical bug in testing. Your package src:transgui in
its current version in unstable has been trying to migrate for 124 days
[2]. Hence, I am filing this bug.

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

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

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

If you believe your package is unable to migrate to testing due to
issues beyond your control, don't hesitate to contact the Release Team.

Paul

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




signature.asc
Description: OpenPGP digital signature

Bug#953711: src:autofdo: fails to migrate to testing for too long

[Paul Gevers]

Source: autofdo
Version: 0.18-2
Severity: serious
Control: fixed -1 0.19-2
Tags: sid bullseye
User: release.debian@packages.debian.org
Usertags: out-of-sync

Dear maintainer(s),

As recently announced [1], the Release Team now considers packages that
are out-of-sync between testing and unstable for more than 60 days as
having a Release Critical bug in testing. Your package src:autofdo in
its current version in unstable has been trying to migrate for 136 days
[2]. Hence, I am filing this bug.

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

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

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

If you believe your package is unable to migrate to testing due to
issues beyond your control, don't hesitate to contact the Release Team.

Paul

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




signature.asc
Description: OpenPGP digital signature

Processed: src:autofdo: fails to migrate to testing for too long

[Debian Bug Tracking System]

Processing control commands:

> fixed -1 0.19-2
Bug #953711 [src:autofdo] src:autofdo: fails to migrate to testing for too long
Marked as fixed in versions autofdo/0.19-2.

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

Processed: src:austin: fails to migrate to testing for too long

[Debian Bug Tracking System]

Processing control commands:

> fixed -1 1.0.0-1
Bug #953712 [src:austin] src:austin: fails to migrate to testing for too long
Marked as fixed in versions austin/1.0.0-1.

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

Bug#953712: src:austin: fails to migrate to testing for too long

[Paul Gevers]

Source: austin
Version: 0.7.0-1
Severity: serious
Control: fixed -1 1.0.0-1
Tags: sid bullseye
User: release.debian@packages.debian.org
Usertags: out-of-sync

Dear maintainer(s),

As recently announced [1], the Release Team now considers packages that
are out-of-sync between testing and unstable for more than 60 days as
having a Release Critical bug in testing. Your package src:austin in its
current version in unstable has been trying to migrate for 136 days [2].
Hence, I am filing this bug.

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

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

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

If you believe your package is unable to migrate to testing due to
issues beyond your control, don't hesitate to contact the Release Team.

Paul

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




signature.asc
Description: OpenPGP digital signature

Bug#953710: src:golang-github-keltia-archive: fails to migrate to testing for too long

[Paul Gevers]

Source: golang-github-keltia-archive
Version: 0.3.3-1
Severity: serious
Control: fixed -1 0.7.0-1
Tags: sid bullseye
User: release.debian@packages.debian.org
Usertags: out-of-sync

Dear maintainer(s),

As recently announced [1], the Release Team now considers packages that
are out-of-sync between testing and unstable for more than 60 days as
having a Release Critical bug in testing. Your package
src:golang-github-keltia-archive in its current version in unstable has
been trying to migrate for 136 days [2]. Hence, I am filing this bug.

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

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

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

If you believe your package is unable to migrate to testing due to
issues beyond your control, don't hesitate to contact the Release Team.

Paul

[1] https://lists.debian.org/debian-devel-announce/2020/02/msg5.html
[2] https://qa.debian.org/excuses.php?package=golang-github-keltia-archive




signature.asc
Description: OpenPGP digital signature

Processed: src:golang-github-keltia-archive: fails to migrate to testing for too long

[Debian Bug Tracking System]

Processing control commands:

> fixed -1 0.7.0-1
Bug #953710 [src:golang-github-keltia-archive] 
src:golang-github-keltia-archive: fails to migrate to testing for too long
Marked as fixed in versions golang-github-keltia-archive/0.7.0-1.

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

Bug#953709: src:openafs: fails to migrate to testing for too long

[Paul Gevers]

Source: openafs
Version: 1.8.4~pre1-1
Severity: serious
Control: fixed -1 1.8.5-1
Tags: sid bullseye
User: release.debian@packages.debian.org
Usertags: out-of-sync

Dear maintainer(s),

As recently announced [1], the Release Team now considers packages that
are out-of-sync between testing and unstable for more than 60 days as
having a Release Critical bug in testing. Your package src:openafs in
its current version in unstable has been trying to migrate for 136 days
[2]. Hence, I am filing this bug.

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

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

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

If you believe your package is unable to migrate to testing due to
issues beyond your control, don't hesitate to contact the Release Team.

Paul

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




signature.asc
Description: OpenPGP digital signature

Processed: src:openafs: fails to migrate to testing for too long

[Debian Bug Tracking System]

Processing control commands:

> fixed -1 1.8.5-1
Bug #953709 [src:openafs] src:openafs: fails to migrate to testing for too long
Marked as fixed in versions openafs/1.8.5-1.

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

Bug#953708: src:urwid-satext: fails to migrate to testing for too long

[Paul Gevers]

Source: urwid-satext
Version: 0.7.0.a2-1
Severity: serious
Control: fixed -1 0.8.0~hg143.144bdf877d21-1
Tags: sid bullseye
User: release.debian@packages.debian.org
Usertags: out-of-sync

Dear maintainer(s),

As recently announced [1], the Release Team now considers packages that
are out-of-sync between testing and unstable for more than 60 days as
having a Release Critical bug in testing. Your package src:urwid-satext
in its current version in unstable has been trying to migrate for 136
days [2]. Hence, I am filing this bug.

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

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

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

If you believe your package is unable to migrate to testing due to
issues beyond your control, don't hesitate to contact the Release Team.

Paul

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




signature.asc
Description: OpenPGP digital signature

Processed: src:urwid-satext: fails to migrate to testing for too long

[Debian Bug Tracking System]

Processing control commands:

> fixed -1 0.8.0~hg143.144bdf877d21-1
Bug #953708 [src:urwid-satext] src:urwid-satext: fails to migrate to testing 
for too long
Marked as fixed in versions urwid-satext/0.8.0~hg143.144bdf877d21-1.

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

Processed: src:rust-futures: fails to migrate to testing for too long

[Debian Bug Tracking System]

Processing control commands:

> fixed -1 0.1.29-1
Bug #953705 [src:rust-futures] src:rust-futures: fails to migrate to testing 
for too long
Marked as fixed in versions rust-futures/0.1.29-1.

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

Processed: src:php-horde-text-filter-jsmin: fails to migrate to testing for too long

[Debian Bug Tracking System]

Processing control commands:

> fixed -1 1.0.2-6
Bug #953706 [src:php-horde-text-filter-jsmin] src:php-horde-text-filter-jsmin: 
fails to migrate to testing for too long
The source 'php-horde-text-filter-jsmin' and version '1.0.2-6' do not appear to 
match any binary packages
Marked as fixed in versions php-horde-text-filter-jsmin/1.0.2-6.

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

Bug#953706: src:php-horde-text-filter-jsmin: fails to migrate to testing for too long

[Paul Gevers]

Source: php-horde-text-filter-jsmin
Version: 1.0.2-5
Severity: serious
Control: fixed -1 1.0.2-6
Tags: sid bullseye
User: release.debian@packages.debian.org
Usertags: out-of-sync

Dear maintainer(s),

As recently announced [1], the Release Team now considers packages that
are out-of-sync between testing and unstable for more than 60 days as
having a Release Critical bug in testing. Your package
src:php-horde-text-filter-jsmin in its current version in unstable has
been trying to migrate for 145 days [2]. Hence, I am filing this bug.

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

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

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

If you believe your package is unable to migrate to testing due to
issues beyond your control, don't hesitate to contact the Release Team.

Paul

[1] https://lists.debian.org/debian-devel-announce/2020/02/msg5.html
[2] https://qa.debian.org/excuses.php?package=php-horde-text-filter-jsmin




signature.asc
Description: OpenPGP digital signature

Bug#953704: src:kexec-tools: fails to migrate to testing for too long

[Paul Gevers]

Source: kexec-tools
Version: 1:2.0.18-1
Severity: serious
Control: fixed -1 1:2.0.20-1
Tags: sid bullseye
User: release.debian@packages.debian.org
Usertags: out-of-sync

Dear maintainer(s),

As recently announced [1], the Release Team now considers packages that
are out-of-sync between testing and unstable for more than 60 days as
having a Release Critical bug in testing. Your package src:kexec-tools
in its current version in unstable has been trying to migrate for 146
days [2]. Hence, I am filing this bug.

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

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

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

If you believe your package is unable to migrate to testing due to
issues beyond your control, don't hesitate to contact the Release Team.

Paul

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




signature.asc
Description: OpenPGP digital signature

Bug#953707: src:libsoxr: fails to migrate to testing for too long

[Paul Gevers]

Source: libsoxr
Version: 0.1.3-1
Severity: serious
Control: fixed -1 0.1.3-2
Tags: sid bullseye
User: release.debian@packages.debian.org
Usertags: out-of-sync

Dear maintainer(s),

As recently announced [1], the Release Team now considers packages that
are out-of-sync between testing and unstable for more than 60 days as
having a Release Critical bug in testing. Your package src:libsoxr in
its current version in unstable has been trying to migrate for 143 days
[2]. Hence, I am filing this bug.

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

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

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

If you believe your package is unable to migrate to testing due to
issues beyond your control, don't hesitate to contact the Release Team.

Paul

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




signature.asc
Description: OpenPGP digital signature

Processed: src:kexec-tools: fails to migrate to testing for too long

[Debian Bug Tracking System]

Processing control commands:

> fixed -1 1:2.0.20-1
Bug #953704 [src:kexec-tools] src:kexec-tools: fails to migrate to testing for 
too long
Marked as fixed in versions kexec-tools/1:2.0.20-1.

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

Processed: src:libsoxr: fails to migrate to testing for too long

[Debian Bug Tracking System]

Processing control commands:

> fixed -1 0.1.3-2
Bug #953707 [src:libsoxr] src:libsoxr: fails to migrate to testing for too long
Marked as fixed in versions libsoxr/0.1.3-2.

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

Bug#953705: src:rust-futures: fails to migrate to testing for too long

[Paul Gevers]

Source: rust-futures
Version: 0.1.28-2
Severity: serious
Control: fixed -1 0.1.29-1
Tags: sid bullseye
User: release.debian@packages.debian.org
Usertags: out-of-sync

Dear maintainer(s),

As recently announced [1], the Release Team now considers packages that
are out-of-sync between testing and unstable for more than 60 days as
having a Release Critical bug in testing. Your package src:rust-futures
in its current version in unstable has been trying to migrate for 145
days [2]. Hence, I am filing this bug.

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

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

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

If you believe your package is unable to migrate to testing due to
issues beyond your control, don't hesitate to contact the Release Team.

Paul

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




signature.asc
Description: OpenPGP digital signature

Processed: src:klog: fails to migrate to testing for too long

[Debian Bug Tracking System]

Processing control commands:

> fixed -1 0.9.8.1-1.1
Bug #953703 [src:klog] src:klog: fails to migrate to testing for too long
Marked as fixed in versions klog/0.9.8.1-1.1.

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

Bug#953702: src:genetic: fails to migrate to testing for too long

[Paul Gevers]

Source: genetic
Version: 0.1.1b-11
Severity: serious
Control: fixed -1 0.1.1b+git20170527.98255cb-1
Tags: sid bullseye
User: release.debian@packages.debian.org
Usertags: out-of-sync

Dear maintainer(s),

As recently announced [1], the Release Team now considers packages that
are out-of-sync between testing and unstable for more than 60 days as
having a Release Critical bug in testing. Your package src:genetic in
its current version in unstable has been trying to migrate for 151 days
[2]. Hence, I am filing this bug.

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

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

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

If you believe your package is unable to migrate to testing due to
issues beyond your control, don't hesitate to contact the Release Team.

Paul

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




signature.asc
Description: OpenPGP digital signature

Bug#953703: src:klog: fails to migrate to testing for too long

[Paul Gevers]

Source: klog
Version: 0.9.7.1-1
Severity: serious
Control: fixed -1 0.9.8.1-1.1
Tags: sid bullseye
User: release.debian@packages.debian.org
Usertags: out-of-sync

Dear maintainer(s),

As recently announced [1], the Release Team now considers packages that
are out-of-sync between testing and unstable for more than 60 days as
having a Release Critical bug in testing. Your package src:klog in its
current version in unstable has been trying to migrate for 150 days [2].
Hence, I am filing this bug.

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

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

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

If you believe your package is unable to migrate to testing due to
issues beyond your control, don't hesitate to contact the Release Team.

Paul

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




signature.asc
Description: OpenPGP digital signature