Bug#982669: buster-pu: package portaudio19/19.6.0-1

2021-02-12 Thread Thorsten Glaser
Dixi quod… >built. Without the crash fix backporting polyphone makes >no sense I must correct myself here: polyphone is usable without it *if* the user manually starts jackd first. (It will still crash upon terminating, but that’s after saving all data. I’m documenting this.) >[ Tests ] >No auto

Bug#982669: buster-pu: package portaudio19/19.6.0-1

2021-02-12 Thread Thorsten Glaser
Package: release.debian.org Severity: normal Tags: buster User: release.debian@packages.debian.org Usertags: pu X-Debbugs-Cc: t...@mirbsd.de I would like to upload the contents of portaudio19 19.6.0-1.1 to buster. [ Reason ] The current library makes applications crash. Please see Debian #944

Re: Bug#978440: RFS: paperwork/2.0.2-1 -- Personal document manager

2021-02-12 Thread Jérémy Lal
Hi Thomas, i've successfully built paperwork 2.0.2 in a clean sid chroot, using gbp buildpackage (and sbuild). The package is lintian clean. However, i don't quite understand the usefulness of these packages: - openpaperwork-core - openpaperwork-core-doc - openpaperwork-gtk - openpaperwork-gtk-do

Bug#982598: incomplete logs for autopkg tests

2021-02-12 Thread Holger Levsen
On Fri, Feb 12, 2021 at 08:35:11PM +0100, Paul Gevers wrote: > Unfortunately, we're hitting infrastructure issues if we don't cap the > logs [1]. However, I think we should save the last part (and not the > first part) if we have to cap, because normally the failure happens in > the end. I'd keep

Bug#982606: marked as done (unblock: win32-loader/0.10.4)

2021-02-12 Thread Debian Bug Tracking System
Your message dated Fri, 12 Feb 2021 20:47:43 +0100 with message-id and subject line Re: Bug#982606: unblock: win32-loader/0.10.4 has caused the Debian Bug report #982606, regarding unblock: win32-loader/0.10.4 to be marked as done. This means that you claim that the problem has been dealt with. I

Bug#982598: incomplete logs for autopkg tests

2021-02-12 Thread Paul Gevers
reassign -1 debci Hi Matthias, On 12-02-2021 10:54, Matthias Klose wrote: > Package: release.debian.org It's not the release team that runs ci.debian.net. Reassigning appropriately. > As seen with glibc autopkg tests [1], the Debian CI infrastructure doesn't > store > complete build logs, cutt

Bug#976094: buster-pu: package grub2/2.02+dfsg1-20+deb10u3

2021-02-12 Thread Colin Watson
On Fri, Feb 12, 2021 at 08:16:46PM +0100, Romain Francoise wrote: > On Mon, Jan 11, 2021 at 03:57:10PM +0100, Cyril Brulebois wrote: > > If I'm getting this right, the udeb part shouldn't be much of an issue, > > but the change regarding the fresh install vs. grub-install /could/ have > > side effe

Bug#976094: buster-pu: package grub2/2.02+dfsg1-20+deb10u3

2021-02-12 Thread Romain Francoise
On Mon, Jan 11, 2021 at 03:57:10PM +0100, Cyril Brulebois wrote: > If I'm getting this right, the udeb part shouldn't be much of an issue, > but the change regarding the fresh install vs. grub-install /could/ have > side effects. As documented, the installer /should/ be doing the right > thing alre

Bug#982606: unblock: win32-loader/0.10.4

2021-02-12 Thread Didier 'OdyX' Raboud
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock X-Debbugs-Cc: debian-b...@lists.debian.org Please unblock package win32-loader in its 0.10.4 version [ Reason ] win32-loader is one of the rare packages always blocked, because it has a 'by

Re: planning to upload binutils 2.35.2

2021-02-12 Thread Matthias Klose
On 2/1/21 7:57 PM, Paul Gevers wrote: > Hi > > On 29-01-2021 12:13, Matthias Klose wrote: >>> We would be happy with either of the following: >>> 1) upload to unstable with PR27218 only >>> 2) upload to experimental first (with a 2.36+really2.35.2 version) to >>> check all is fine. >> >> so I don'

Bug#982598: incomplete logs for autopkg tests

2021-02-12 Thread Matthias Klose
Package: release.debian.org Severity: important Tags: sid bullseye As seen with glibc autopkg tests [1], the Debian CI infrastructure doesn't store complete build logs, cutting these to 20MB (uncompressed), resulting in ~450k compressed logs. This might not be important for successful tests, but