Package: python-argcomplete
Version: 1.8.1-1
Followup-For: Bug #981846
Control: reopen -1
The issue is not fixed in the latest NMU, i.e. 1.8.1-1.4
Attached is full build log
-- System Information:
Debian Release: bullseye/sid
APT prefers unstable
APT policy: (990, 'unstable'), (990, 'testin
Processing control commands:
> reopen -1
Bug #981846 {Done: Sebastian Ramacher }
[python-argcomplete] python-argcomplete: multiple tests 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 reopen
It appears a simple git commit upstream corrects this bug.
https://github.com/loads/molotov/commit/5e8854d95a74fb8820020335a8368c19f9f658b4?branch=5e8854d95a74fb8820020335a8368c19f9f658b4&diff=unified
Thanks to tianon on #debian-mentors for sharing this solution and link.
Control: tag -1 patch
On Fri, 26 Feb 2021 03:21:36 +0200
Faidon Liambotis wrote:
[...]
>
> pa_cpu_init_orc() returns true only if cpu_info.cpu_type ==
> PA_CPU_X86. This should not be the case here, but cpu_info is being
> passed to the function uninitialized, and... as luck would have it,
> cpu_info.cpu_type's "rando
Processing commands for cont...@bugs.debian.org:
> forwarded 982740
> https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/511
Bug #982740 [pulseaudio] pulseaudio: FTBFS on ppc64el
Set Bug forwarded-to-address to
'https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requ
Processing control commands:
> tags -1 patch
Bug #982740 [pulseaudio] pulseaudio: FTBFS on ppc64el
Added tag(s) patch.
--
982740: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=982740
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Control: tags -1 patch
On Sat, Feb 13, 2021 at 02:53:58PM -0500, Andres Salomon wrote:
> Pulseaudio is failing to build on ppc64el. The version of pulseaudio in
> bullseye suffers from a pretty serious usability bug (see #980836)
> which should arguably be a higher severity, but let's focus on get
Package: src:vinagre
Severity: grave
Version: 3.22.0-8
For a while now, vinagre when running against FreeRDP >= 2.0.0 has
been broken in Debian. When launching an RDP session, the user sees a
GTK window with a black rectangle in the middle.
A fix proposed by FreeRDP upstream is
https://gitl
Your message dated Thu, 25 Feb 2021 22:50:20 +
with message-id
and subject line Bug#982530: fixed in pam 1.4.0-5
has caused the Debian Bug report #982530,
regarding libpam-modules: unable to login when using pam_tally2 after upgrade
to libpam-modules >1.4.0
to be marked as done.
This means t
Your message dated Thu, 25 Feb 2021 22:18:38 +
with message-id
and subject line Bug#983512: fixed in debuerreotype 0.10-2
has caused the Debian Bug report #983512,
regarding debuerreotype: autopkgtest needs update for new version of
debian-archive-keyring: Release signed by unknown key (key i
Your message dated Thu, 25 Feb 2021 22:18:38 +
with message-id
and subject line Bug#983513: fixed in debuerreotype 0.10-2
has caused the Debian Bug report #983513,
regarding debuerreotype: autopkgtest seems to hard-code amd64 signature
to be marked as done.
This means that you claim that the
Processing commands for cont...@bugs.debian.org:
> unblock 938731 with 938637
Bug #938731 [src:twisted] twisted: Python2 removal in sid/bullseye
938731 was blocked by: 936966 943240 936731 937620 937174 938427 936799 938564
938759 938734 938232 936167 938675 938637 936269 938220 936544 936235 936
On Sat, Feb 13, 2021 at 11:23:58AM +0100, Pietro Battiston wrote:
> Thank you again!
>
> Meanwhile, I merged your changes back in salsa, where there is a new
> version in principle ready to be uploaded:
> https://salsa.debian.org/debian/gedit-latex-plugin
> It fixes a number of small other issues
Hello,
I'm just writing this email as it seems like intake is going to be
autoremoved soon, due to a FTBFS [bug]. Unfortunately, due to life
events, I am going to be occupied elsewhere for a week or so. If anyone
kindly has time to look at this package, please feel free to do so.
Just a note
Processing commands for cont...@bugs.debian.org:
> limit source pam
Limiting to bugs with field 'source' containing at least one of 'pam'
Limit currently set to 'source':'pam'
> tags 982295 + pending
Bug #982295 [libpam0g] libpam0g.postinst: `installed_services` function is not
systemd aware
Add
Your message dated Thu, 25 Feb 2021 20:35:14 +
with message-id
and subject line Bug#982795: fixed in neat 2.3.2-1
has caused the Debian Bug report #982795,
regarding neat: autopkgtest failure on several architectures
to be marked as done.
This means that you claim that the problem has been de
On Thu, 25 Feb 2021 at 12:09, Paul Gevers wrote:
> On 25-02-2021 20:40, Tianon Gravi wrote:
> > Hi Paul! Thanks for filing these -- I've pushed two commits to the
> > Git repo which fix both 983512 and 983513 (and made it more forgiving
> > of other architectures for the future).
>
> Can't you sk
Hi Tianon,
On 25-02-2021 20:40, Tianon Gravi wrote:
> Hi Paul! Thanks for filing these -- I've pushed two commits to the
> Git repo which fix both 983512 and 983513 (and made it more forgiving
> of other architectures for the future).
Can't you skip the hash test (but still run all the rest) on
Sorry missed your email.
Weitergeleitete Nachricht
Betreff: Re: Bug#974828: printer-driver-hpcups: SIGABRT with "free():
invalid next size (normal)" in HPCupsFilter::cleanup
Datum: Thu, 25 Feb 2021 17:03:02 +0100
Von: Bernhard Übelacker
An: 974...@bugs.debian.org
Hello Ia
Hello Ian,
I tried to collect some informations for the
maintainer in the other report #972339.
Therefore I tried to reproduce this issue now too, because
my amd64 hardware is much faster as my armhf systems...
But I failed to reproduce maybe because I use the wrong ppd file,
or something else mi
I already looked at this, and in the mipsel build gcc runs out of
address space even with "OPTIMIZE = 0".
My suggestion would be to file architecture-specific RM bugs,
MAME is anyway unlikely to have users there.
cu
Adrian
The file rules.patch got mangled in transit. Attached is the
integrous version.
rules.patch.gz
Description: application/gzip
On Thu, 25 Feb 2021 at 04:18, Paul Gevers wrote:
> Your package has an autopkgtest, great. However, it always fails on
> non-amd64 architectures. Looking at the error message, it seems to
> compare the build tar ball with a pre-computed hash that's only valid on
> amd64. (And then the log becomes
Hi Chris,
On Thu, Feb 25, 2021 at 04:47:34PM +, Chris Lamb wrote:
> Sébastien Delafond wrote:
>
> > > > Django is vulnerable because it embeds parse_qsl:
> > > >
> > > > https://www.djangoproject.com/weblog/2021/feb/19/security-releases/
> > >
> > > Security team, let me know if you would
Processing control commands:
> found -1 3.20.11+dfsg0-1
Bug #974828 [printer-driver-hpcups] printer-driver-hpcups: SIGABRT with
"free(): invalid next size (normal)" in HPCupsFilter::cleanup
Marked as found in versions hplip/3.20.11+dfsg0-1.
--
974828: https://bugs.debian.org/cgi-bin/bugreport.c
Your message dated Thu, 25 Feb 2021 11:02:24 -0800
with message-id <20210225190224.htkdsx64z7h7y...@haydn.kardiogramm.net>
and subject line Re: Bug#983382: python-mitogen: uninstallable in sid
has caused the Debian Bug report #983382,
regarding python-mitogen: uninstallable in sid
to be marked as d
Processing control commands:
> found -1 3.20.11+dfsg0-2
Bug #974828 [printer-driver-hpcups] printer-driver-hpcups: SIGABRT with
"free(): invalid next size (normal)" in HPCupsFilter::cleanup
Marked as found in versions hplip/3.20.11+dfsg0-2.
> found -1 3.21.2+dfsg1-1
Bug #974828 [printer-driver-hp
Control: found -1 3.20.11+dfsg0-2
Control: found -1 3.21.2+dfsg1-1
On Thu, 2021-02-25 at 18:32 +, Ian Campbell wrote:
> I'll see if I can upgrade and repeat.
Confirmed I see this with both the current bullseye and sid versions of
printer-driver-hpcups.
Ian.
In adapting your first patch, I narrowed things down a bit.
I search /etc/pam.d files containing only a-z0-9A-Z, which I believe
should catch all the active pam.d files but not editor backups, .pam-new
files and the like.
I also specifically recommend looking at pam_faillock.
--Sam
Processing commands for cont...@bugs.debian.org:
> fixed 982969 28.1
Bug #982969 [emacs] emacs: expects working network in tests
There is no source info for the package 'emacs' at version '28.1' with
architecture ''
Unable to make a source version for version '28.1'
Marked as fixed in versions 28
On Thu, Feb 25, 2021 at 12:05:39PM +0100, Jerome BENOIT wrote:
> I was rather wondering if setting Rules-Requires-Root to yes in d/rules
> will ask to bbuild to act as "needs-root" for autopkgtest.
No. Rules-Requires-Root is only to tell the build scripts that some
parts of the build requires rea
Control: tag -1 + confirmed sid bullseye
I looked into this the past days, and I think this is actually a bug
in d/rules in src:linphone. I'm beginning to suspect that this is due
to this line:
-DENABLE_DB_STORAGE=NO \
Apparently the code for the once separate chat history and c
Processing control commands:
> tag -1 + confirmed sid bullseye
Bug #983365 [linphone-desktop] linphone-desktop: chat messages
Added tag(s) sid, bullseye, and confirmed.
--
983365: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=983365
Debian Bug Tracking System
Contact ow...@bugs.debian.org wi
Hi Moritz,
> given that this only affects 32 bit archs and only with an inherently insecure
> setup (opening up the default bulk size to such high values might impact all
> kinds of stability / availability I guess) I don't think this needs a DSA.
> So s-p-u or piggybacking with the next DSA seems
Hello Paul,
hello Holger,
manpages-it comes back, just from a new source package
(manpages-l10n). The reason this was delayed is that I cannot get this
through NEW myself, as I'm only a Debian Maintainer, so I needed a
sponsor (Toddy is currently unavailable). This has been resolved, so
now manpage
Your message dated Thu, 25 Feb 2021 16:48:31 +
with message-id
and subject line Bug#983433: fixed in libemail-outlook-message-perl 0.920-2
has caused the Debian Bug report #983433,
regarding libemail-outlook-message-perl: msgconvert: missing dependency on
libemail-address-perl
to be marked as
Sébastien Delafond wrote:
> > > Django is vulnerable because it embeds parse_qsl:
> > >
> > > https://www.djangoproject.com/weblog/2021/feb/19/security-releases/
> >
> > Security team, let me know if you would like an update for stable.
[…]
> we think this should rather go via s-p-u.
ACK. Hav
Processing commands for cont...@bugs.debian.org:
> forwarded 982969 https://debbugs.gnu.org/46641
Bug #982969 [emacs] emacs: expects working network in tests
Set Bug forwarded-to-address to 'https://debbugs.gnu.org/46641'.
>
End of message, stopping processing here.
Please contact me if you need
Your message dated Thu, 25 Feb 2021 15:18:55 +
with message-id
and subject line Bug#983019: fixed in x11vnc 0.9.16-7
has caused the Debian Bug report #983019,
regarding x11vnc: flaky autopkgtest: /tmp/x11vnc_allow-connections_result: No
such file or directory
to be marked as done.
This means
Control: tag -1 pending
Hello,
Bug #983019 in x11vnc 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/x11vnc/-/commit/295aa6a2051cc5cdbb98eee1
Processing control commands:
> tag -1 pending
Bug #983019 [src:x11vnc] x11vnc: flaky autopkgtest:
/tmp/x11vnc_allow-connections_result: No such file or directory
Ignoring request to alter tags of bug #983019 to the same tags previously set
--
983019: https://bugs.debian.org/cgi-bin/bugreport.cg
Source: python2.7
Version: 2.7.18-2
X-Debbugs-CC: debian...@lists.debian.org
Severity: serious
User: debian...@lists.debian.org
Usertags: regression
Dear maintainer(s),
With a recent upload of python2.7 the autopkgtest of python2.7 fails in
testing when that autopkgtest is run with the binary pac
Source: paperwork
Version: 2.0.2-2
X-Debbugs-CC: debian...@lists.debian.org
Severity: serious
User: debian...@lists.debian.org
Usertags: regression
Dear maintainer(s),
With a recent upload of paperwork the autopkgtest of paperwork fails in
testing when that autopkgtest is run with the binary pack
Source: debuerreotype
Version: 0.10-1
Severity: serious
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: fails-always
Dear maintainer(s),
Your package has an autopkgtest, great. However, it always fails on
non-amd64 architectures. Looking at the error message, i
Processing control commands:
> affects -1 src:debian-archive-keyring
Bug #983512 [src:debuerreotype] debuerreotype: autopkgtest needs update for new
version of debian-archive-keyring: Release signed by unknown key (key id
7638D0442B90D010)
Added indication that 983512 affects src:debian-archive-
Source: debuerreotype
Version: 0.10-1
Severity: serious
Tags: sid bullseye
User: debian...@lists.debian.org
Usertags: needs-update
Control: affects -1 src:debian-archive-keyring
[X-Debbugs-CC: debian...@lists.debian.org,
debian-archive-keyr...@packages.debian.org]
Dear maintainer(s),
With a rece
Source: cdebootstrap
Version: 0.7.7
Severity: serious
Tags: sid bullseye
User: debian...@lists.debian.org
Usertags: needs-update
Control: affects -1 src:debian-archive-keyring
[X-Debbugs-CC: debian...@lists.debian.org,
debian-archive-keyr...@packages.debian.org]
Dear maintainer(s),
With a recent
Processing control commands:
> affects -1 src:debian-archive-keyring
Bug #983511 [src:cdebootstrap] cdebootstrap: autopkgtest needs update for new
version of debian-archive-keyring:
Added indication that 983511 affects src:debian-archive-keyring
--
983511: https://bugs.debian.org/cgi-bin/bugrep
Hi
On Mon, 15 Feb 2021 at 10:07, Matthias Klose wrote:
> On 2/14/21 5:58 PM, Simon McVittie wrote:
>> Obviously, the transitional packages would ideally be built by src:gcc-10
>> rather than being a separate source package, and Ryan only prototyped them
>> as a separate source package to be able
Dear Dennis, thanks for your reply.
I was rather wondering if setting Rules-Requires-Root to yes in d/rules
will ask to bbuild to act as "needs-root" for autopkgtest.
Jerome
Source: mame
Version: 0.228+dfsg.1-1
Severity: serious
Tags: ftbfs
Hi Maintainer,
Your last upload of mime FTBFS on armel and mipsel.
Paul
https://buildd.debian.org/status/package.php?p=mame
tail on armel:
/usr/bin/ld.gold: fatal error: ../../../../../mame: mmap: failed to
allocate 372463976
Processing control commands:
> severity -1 serious
Bug #818432 [src:espresso] espresso: FTBFS on armel: hangs during the build
Severity set to 'serious' from 'normal'
--
818432: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=818432
Debian Bug Tracking System
Contact ow...@bugs.debian.org with
Hi Markus,
On Thu, Feb 25, 2021 at 09:11:47AM +0100, Markus Koschany wrote:
> Hello security team, hello Hugo, I hope you are doing well!
>
> I have just uploaded a NMU for xcftools fixing CVE-2019-5086 and
> CVE-2019-5087.
> The new patch also addresses the 32 bit portability issues. The basic
Processing control commands:
> found -1 4.5.1527308405.8b586d5-4.2
Bug #983266 {Done: Paul Gevers } [src:os-autoinst]
src:os-autoinst: fails to migrate to testing for too long: unresolved RC bug
Ignoring request to alter found versions of bug #983266 to the same values
previously set
--
983266
Control: found -1 4.5.1527308405.8b586d5-4.2
Hi Frédéric, Hideki,
On 17-02-2021 22:01, Paul Gevers wrote:
> If the forth time worked because of sheer luck, then please no, keep the
> bug open until the build is less flaky. We need packages to be build
> without failure [1]. Having to baby-sit fla
Processing control commands:
> found -1 4.5.1527308405.8b586d5-4.2
Bug #977990 [src:os-autoinst] os-autoinst: FTBFS on i386: 3/3 Test #3:
test-perl-testsuite ..***Failed 332.81 sec
Marked as found in versions os-autoinst/4.5.1527308405.8b586d5-4.2.
--
977990: https://bugs.debian.or
Your message dated Thu, 25 Feb 2021 08:16:31 +
with message-id
and subject line Bug#983480: fixed in gitlab 13.6.7-4
has caused the Debian Bug report #983480,
regarding yarnpkg 2.4.0 is broken with typescript 4.2 and this breaks gitlab
installation
to be marked as done.
This means that you c
Your message dated Thu, 25 Feb 2021 08:17:48 +
with message-id
and subject line Bug#945317: fixed in xcftools 1.0.7-6.1
has caused the Debian Bug report #945317,
regarding xcftools: CVE-2019-5086 CVE-2019-5087
to be marked as done.
This means that you claim that the problem has been dealt wit
Hello security team, hello Hugo, I hope you are doing well!
I have just uploaded a NMU for xcftools fixing CVE-2019-5086 and CVE-2019-5087.
The new patch also addresses the 32 bit portability issues. The basic idea
behind it is to limit possible values of width and height (which can only be
posit
59 matches
Mail list logo
