Processing control commands:
> tags 935438 + patch
Bug #935438 [src:chaussette] Please update to Python 3 or remove
Bug #936291 [src:chaussette] chaussette: Python2 removal in sid/bullseye
Added tag(s) patch.
Added tag(s) patch.
> tags 935438 + pending
Bug #935438 [src:chaussette] Please update
Control: tags 935438 + patch
Control: tags 935438 + pending
Dear maintainer,
I've prepared an NMU for chaussette (versioned as
1.3.0+git20170419+82ac44a-0.2) and
uploaded it to DELAYED/3. Please feel free to tell me if I
should delay it longer.
Regards.
diff -Nru
Processing commands for cont...@bugs.debian.org:
> limit source chaussette
Limiting to bugs with field 'source' containing at least one of 'chaussette'
Limit currently set to 'source':'chaussette'
> tags 935438 + pending
Bug #935438 [src:chaussette] Please update to Python 3 or remove
Bug
A quick update:
I have booted up the Debian live USB on another machine and was able to
reproduce this bug with it.
The machine had the Ryzen 5 2600 CPU (the one I swapped with the machine
I have originally found the problem on).
The Mainboard is: ASUS PRIME B350-PLUS
BIOS Version: 5216
On Mon, 29 Apr 2019 14:46:18 +0200 Axel Beckert wrote:
> Package: postfix
> Version: 3.1.12-0+deb9u1
> Severity: grave
> Affects: procmail
> Justfication: causes data loss (after a few days), breaks (more or less)
unrelated packages (procmail)
>
> Dear Debian Postfix Maintainers,
>
>* What
Processing commands for cont...@bugs.debian.org:
> tags 928175 + moreinfo
Bug #928175 [postfix] postfix: [Regression/Stretch] No more delivers mails to
mailboxes > ca. 500 MB via procmail since upgrade from 3.1.9-0+deb9u2 to
3.1.12-0+deb9u1
Added tag(s) moreinfo.
> thanks
Stopping processing
Your message dated Mon, 23 Sep 2019 03:34:45 +
with message-id
and subject line Bug#939800: fixed in rtl-sdr 0.6-3
has caused the Debian Bug report #939800,
regarding librtlsdr-dev: Incomplete pkg-config file
to be marked as done.
This means that you claim that the problem has been dealt
Processing commands for cont...@bugs.debian.org:
> reassign 940931 2.10.8-2
Bug #940931 [gimp amd64 2.10.8-2+b1] Gimp bug
Warning: Unknown package 'amd64'
Warning: Unknown package '2.10.8-2+b1'
Bug reassigned from package 'gimp amd64 2.10.8-2+b1' to '2.10.8-2'.
Warning: Unknown package '2.10.8-2'
Processing commands for cont...@bugs.debian.org:
> reassign 940924 src:rope 0.14.0-1
Bug #940924 [python3-rope] python3-rope: the license has been changed without
the main author's consent
Bug reassigned from package 'python3-rope' to 'src:rope'.
No longer marked as found in versions
Hi Andreas,
On Sat, Sep 21, 2019 at 06:39:51PM +0200, Andreas Tille wrote:
> Control: tags -1 help
>
> Dear Ana,
>
> On Sat, Sep 21, 2019 at 05:41:27PM +0200, Ana Guerrero Lopez wrote:
> > This new version of cycle, ported to python3, doesn't read the data file
> > ( under .cycle) and prompts
Package: dnsmasq
Version: 2.80-1
Tags: upstream
Severity: serious
dnsmasq_ecdsa_verify() (in crypto.c) uses the addresses of nettle_secp_256r1
and nettle_secp_384r1 directly. As the comment in ecc-curve.h explains, "Due
to ABI subtleties, applications should not refer to these directly, but use
Source: python-biggles
Severity: serious
Hello,
as part of https://wiki.debian.org/Python/2Removal i noticed python-biggles and
i believe we should remove it from Debian:
- maybe it was sophisiticated when it was created, but there are better
alternatives now (but i may be bias as i maintainer
Package: rust-sha-1
Version: 0.8.1-2
Severity: serious
If rust-sha-1 is re-built, the version mentioned in virtual package names in the provides changes from
"0.4" to "0.8", but the version mentioned in the virtual package names in the depends
stays at "0.4", thus breaking dependencies between
Package: planet-venus
Severity: serious
Hello,
as part of https://wiki.debian.org/Python/2Removal i noticed planet-venus, and i
believe we should remove it from Debian:
- RC buggy
- pretty low pop-con
- python2-only, also upstream
- https://github.com/rubys/venus/issues/37 showed some possible
Package: doconce
Severity: serious
Hello,
as part of https://wiki.debian.org/Python/2Removal i noticed doconce, and i
believe we should remove it from Debian:
- last upload to debian 7 years go
- low popcon
- Uploader seems to have lost interest in Debian
- python2 only (in debian)
- upstream
Your message dated Sun, 22 Sep 2019 21:19:21 +
with message-id
and subject line Bug#940703: fixed in augustus 3.3.3+dfsg-2
has caused the Debian Bug report #940703,
regarding augustus_3.3.3+dfsg-1_mips64el.changes REJECTED
to be marked as done.
This means that you claim that the problem has
Your message dated Sun, 22 Sep 2019 20:49:10 +
with message-id
and subject line Bug#940972: fixed in litl 0.1.9-7
has caused the Debian Bug report #940972,
regarding litl: flacky autopkgtest: FAIL:
test_litl_write_multiple_threads(|_flush)
to be marked as done.
This means that you claim
Control: clone -1 -2
Control: severity -2 normal
Control: forwarded -2 litl-de...@fusionforge.int-evry.fr
Control: tag -1 + pending
Control: tag -2 - pending
Hello,
Paul Gevers, le dim. 22 sept. 2019 21:32:39 +0200, a ecrit:
> it fails once in a while with one or the other multiple_threads test.
Processing control commands:
> clone -1 -2
Bug #940972 [src:litl] litl: flacky autopkgtest: FAIL:
test_litl_write_multiple_threads(|_flush)
Bug 940972 cloned as bug 940978
> severity -2 normal
Bug #940978 [src:litl] litl: flacky autopkgtest: FAIL:
test_litl_write_multiple_threads(|_flush)
Source: libfte
Severity: serious
Hello,
as part of https://wiki.debian.org/Python/2Removal i noticed libfte, and i
believe we should remove this package from Debian:
- single maintainer upload, immediately followed by a NMU
- python2 only, even upstream
- last upstream release 5 years ago,
Your message dated Sun, 22 Sep 2019 20:36:21 +
with message-id
and subject line Bug#817713: fixed in vdk2-tutorial 1.1-3.1
has caused the Debian Bug report #817713,
regarding vdk2-tutorial: Removal of debhelper compat 4
to be marked as done.
This means that you claim that the problem has
Package: python-avc
Severity: serious
Hello,
As part of https://wiki.debian.org/Python/2Removal i stumbled across this
package, and i believe we should remove it:
- popcon very low
- no maintainer upload to debian in 8 years
- last upload, NMU, 5 years ago
- last upstream release 3.5years ago
Processing commands for cont...@bugs.debian.org:
> tags 940972 + pending
Bug #940972 [src:litl] litl: flacky autopkgtest: FAIL:
test_litl_write_multiple_threads(|_flush)
Added tag(s) pending.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
940972:
Hi Paul,
> ok 20 - t/fixtures/zip/bug_803503.zip.in
> Reading ZIP archive failed: IO error: reading local extra field :
>
> error: becoming Archive::Zip::DirectoryMember
> # Looks like your test exited with 29 just after 20.
> Tests failed
These is likely related:
Processing commands for cont...@bugs.debian.org:
> limit source cigi-ccl
Limiting to bugs with field 'source' containing at least one of 'cigi-ccl'
Limit currently set to 'source':'cigi-ccl'
> tags 896368 + pending
Bug #896368 [python3-cigi] python3-cigi: cigi fails to import
Added tag(s)
Processing control commands:
> found -1 libarchive-zip-perl/1.66-1
Bug #940973 [src:libarchive-zip-perl, src:strip-nondeterminism]
libarchive-zip-perl breaks strip-nondeterminism autopkgtest: error: becoming
Archive::Zip::DirectoryMember
Marked as found in versions libarchive-zip-perl/1.66-1.
>
Source: libarchive-zip-perl, strip-nondeterminism
Control: found -1 libarchive-zip-perl/1.66-1
Control: found -1 strip-nondeterminism/1.6.0-1
Severity: serious
Tags: sid bullseye
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: breaks needs-update
Dear
Your message dated Sun, 22 Sep 2019 19:34:18 +
with message-id
and subject line Bug#886306: fixed in python-pyocr 0.7.2-1
has caused the Debian Bug report #886306,
regarding python-pyocr: FTBFS: "Unable to parse Tesseract version"
to be marked as done.
This means that you claim that the
Source: litl
Version: 0.1.9-6
Severity: serious
Tags: sid bullseye
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: flaky
Dear Samuel,
With a recent upload of glibc the autopkgtest of litl failed in testing
when that autopkgtest was run with the binary packages
Hello,
Sorry for the confusion, the fix proposal is in https://phabricator.kde.org/
D24147 .
Best regards
Your message dated Sun, 22 Sep 2019 19:19:00 +
with message-id
and subject line Bug#940119: fixed in sdaps 1.9.7-0.2
has caused the Debian Bug report #940119,
regarding sdaps build-depends on package that is cruft in unstable and gone in
testing.
to be marked as done.
This means that you
Your message dated Sun, 22 Sep 2019 19:19:00 +
with message-id
and subject line Bug#940119: fixed in sdaps 1.9.7-0.2
has caused the Debian Bug report #940119,
regarding sdaps: please switch from texlive-generic-recommended to
texlive-plain-generic
to be marked as done.
This means that you
Processing commands for cont...@bugs.debian.org:
> reassign 940939 src:kirigami2 5.62.0-1
Bug #940939 [plasma-discover] plasma-discover: After KDE Frameworks 5.62 update
plasma-discover doesn't start
Bug reassigned from package 'plasma-discover' to 'src:kirigami2'.
No longer marked as found in
I submitted a self-service giveback request and had this package rebuilt on
ppc64el. It is still failing with GCC 9. Looks like further investigation is
needed.
https://buildd.debian.org/status/package.php?p=check
Thanks,
Boyuan Yang
On Fri, 20 Sep 2019 09:57:02 +0200 "Thierry
Processing control commands:
> severity -1 grave
Bug #940963 [samba] samba doesn't start anymore
Severity set to 'grave' from 'normal'
> reassign -1 samba-common-bin
Bug #940963 [samba] samba doesn't start anymore
Bug reassigned from package 'samba' to 'samba-common-bin'.
No longer marked as
Hi Vagrant,
On 21/09/19 23:49, Vagrant Cascadian wrote:
>> Preparing to unpack .../15-libubootenv-tool_0.1-1_amd64.deb ...
>> Unpacking libubootenv-tool (0.1-1) ...
>> dpkg: error processing archive
>> /tmp/apt-dpkg-install-S5V5yb/15-libubootenv-tool_0.1-1_amd64.deb (--unpack
>> ):
>> trying to
I couldn't find a bug report on the zfsonlinux bug tracker, so I opened one for
this issue [1].
Thanks for looking into this,
Antonio
[1] https://github.com/zfsonlinux/zfs/issues/9346
Processing commands for cont...@bugs.debian.org:
> severity 940938 minor
Bug #940938 [telegram-desktop] telegram-desktop: Could not start Telegram
Desktop!
Severity set to 'minor' from 'grave'
> tag 940938 moreinfo
Bug #940938 [telegram-desktop] telegram-desktop: Could not start Telegram
Control: tags -1 patch
Running the test suite (of -7) under gdb a few times produced a crash in
pandas/tests/indexes/interval/test_astype.py::TestDatetimelikeSubtype::test_astype_category[index4]
(4 not 3).
The trace points to Cython-generated C from _Timedelta._has_ns, which
(among other
Severity: minor
Tags: moreinfo
Hi!
22.09.2019 12:41, Utkarsh Gupta пишет:
> [2019.09.22 15:07:08] FATAL: Could not move logging to
> '/home/utkarsh2102/.local/share/TelegramDesktop/log.txt'!
Please check that Telegram can write to this file, especially that it
isn't immutable. See lsattr(1),
Processing control commands:
> tags -1 patch
Bug #940679 [src:pandas] pandas: random test crashes
Added tag(s) patch.
--
940679: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=940679
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Le dimanche, 22 septembre 2019, 13.25:19 h CEST Brian Potkin a écrit :
> On Sat 21 Sep 2019 at 17:39:20 +0200, Didier 'OdyX' Raboud wrote:
> > Le samedi, 21 septembre 2019, 16.24:30 h CEST Brian Potkin a écrit :
> > > > There's clearly a regression in ghostscript 9.28 that started
> > > >
On Sat 21 Sep 2019 at 17:39:20 +0200, Didier 'OdyX' Raboud wrote:
> Le samedi, 21 septembre 2019, 16.24:30 h CEST Brian Potkin a écrit :
> > > There's clearly a regression in ghostscript 9.28 that started segfaulting
> > > in the c2esp filter chain. But I can't manage to reproduce it outside of
>
On Sat 21 Sep 2019 at 17:39:20 +0200, Didier 'OdyX' Raboud wrote:
> Le samedi, 21 septembre 2019, 16.24:30 h CEST Brian Potkin a écrit :
> > > There's clearly a regression in ghostscript 9.28 that started segfaulting
> > > in the c2esp filter chain. But I can't manage to reproduce it outside of
>
Processing commands for cont...@bugs.debian.org:
> block 938629 by 936095 938433
Bug #938629 [src:taurus] taurus: Python2 removal in sid/bullseye
938629 was not blocked by any bugs.
938629 was blocking: 937304 937513 938545
Added blocking bug(s) of 938629: 936095 and 938433
> thanks
Stopping
Your message dated Sun, 22 Sep 2019 15:04:05 +
with message-id
and subject line Bug#929949: fixed in duplicity 0.8.04-1
has caused the Debian Bug report #929949,
regarding New upstream version 0.8 available, compatible with python3
to be marked as done.
This means that you claim that the
Processing commands for cont...@bugs.debian.org:
> clone 938884 -1
Bug #938884 [src:zeitgeist] zeitgeist: Python2 removal in sid/bullseye
Bug 938884 cloned as bug 940945
936371 was blocked by: 936981 938944 936104 849086 936987 938595 937688 937513
938588 938642 938316 938584 938591 938637
[adding x...@lists.x.org to CC, dropping t...@security.debian.org; please
retain all CCs]
Dear Xorg developers,
> […]
I recently became a co-maintainer for the xtrlock screen locking
utility. As part of this, I noticed a bug report filed by Antoine
Amarilli which points out that so-called
Your message dated Sun, 22 Sep 2019 14:49:41 +
with message-id
and subject line Bug#933057: fixed in csh 20110502-5
has caused the Debian Bug report #933057,
regarding csh: bsd-csh eval command always dies with segmentation fault
to be marked as done.
This means that you claim that the
Your message dated Sun, 22 Sep 2019 10:34:38 +
with message-id
and subject line Bug#940909: fixed in xserver-xorg-video-tdfx 1:1.5.0-2
has caused the Debian Bug report #940909,
regarding xserver-xorg-video-tdfx: missing dependencies
to be marked as done.
This means that you claim that the
Package: telegram-desktop
Version: 1.8.8-1
Severity: grave
Dear Maintainer,
While opening up telegram-desktop, I encountered the following problems:
Could not start Telegram Desktop!
You can see complete log below:
[2019.09.22 15:07:07] Executable path before check:
/usr/bin/telegram-desktop
On Sat, 21 Sep 2019, Mark Hindley wrote:
> On Sat, Sep 21, 2019 at 06:51:16PM +0200, Cristian Ionescu-Idbohrn wrote:
> > > Would you, please, start a new bug for this unless you really think
> > > it is the same issue (apt being broken by continuing to uninstall
> > > libsystemd0 after systemd
52 matches
Mail list logo
