Package: qemu-system-ppc
Version: 1:4.2-2
Severity: grave
Justification: renders package uninstallable
Hi!
Upon upgrading or a fresh install:
Unpacking qemu-system-ppc (1:4.2-2) ...
dpkg: error processing archive «TMP»/3-qemu-system-ppc_1%3a4.2-2_amd64.deb
(--unpack):
trying to overwrite
tags 950433 +patch
tags 944055 +patch
thanks
As has been reported linbox is currently blocked from migrating to testing by
build failures on armhf and mipsel autobuilders.
In some armhf environments (notablly on Debian porterboxes and buildds with
arm64 kernels), linbox fails to build with
Processing commands for cont...@bugs.debian.org:
> tags 950433 +patch
Bug #950433 [linbox] linbox FTBFS on mipsel, oom while building tests.
Added tag(s) patch.
> tags 944055 +patch
Bug #944055 [src:linbox] linbox ftbfs on armhf, bus errors in the test suite
Added tag(s) patch.
> thanks
Stopping
Hi Hilko,
On Sat, Feb 01, 2020 at 12:57:27AM +0100, Hilko Bengen wrote:
> * Moritz Mühlenhoff:
>
> >> FTR, this was as well raised back in [1]. AFAIK there was no direct
> >> feedback to the question from Moritz back then.
> >
> > Yeah, we should at least remove radare2 from oldstable (IIRC for
Package: libm4rie-0.0.20200125
Version: 20200125-1
Severity: serious
Hi,
seems that something went wrong with the binary upload of libm4rie on amd64. On
this architecture libm4rie-0.0.20200125 depends on libm4ri-0.0.20200115 which
makes it uninstallable. This might be fixable with a
Processing commands for cont...@bugs.debian.org:
> forcemerge 942989 936370
Bug #942989 [src:dblatex] dblatex: Python2 removal in sid/bullseye
Bug #936370 [src:dblatex] dblatex: Python2 removal in sid/bullseye
937695 was blocked by: 937816 937122 938557 936557 937373 938366 936366 942930
938909
Control: forwarded -1 https://phabricator.kde.org/D25269
Control: tags -1 fixed-upstream patch
Control: reassign 949238 src:ktp-common-internals
Control: reassign 949239 src:ktp-common-internals
Control: forcemerge -1 949238 949239
Control: affects -1 + src:ktp-text-ui
Control: affects -1 +
Control: forwarded -1
https://cgit.kde.org/kaccounts-providers.git/commit/?id=fd6b3ebf
Control: tags -1 patch fixed-upstream
This was caused by the newer version of Qt and builds with the patch.
signature.asc
Description: This is a digitally signed message part.
Processing control commands:
> forwarded -1 https://cgit.kde.org/kaccounts-providers.git/commit/?id=fd6b3ebf
Bug #948940 [src:kaccounts-providers] kaccounts-providers: FTBFS:
/plugins/owncloud-ui/owncloud.cpp:54:23: error: invalid use of incomplete type
‘class QWindow’
Set Bug
Processing control commands:
> forwarded -1 https://phabricator.kde.org/D25269
Bug #949236 [src:ktp-common-internals] ktp-common-internals: FTBFS on various
archs
Set Bug forwarded-to-address to 'https://phabricator.kde.org/D25269'.
> tags -1 fixed-upstream patch
Bug #949236
Your message dated Sat, 01 Feb 2020 15:10:41 +
with message-id
and subject line Bug#941218: fixed in guile-2.0 2.0.13+1-5.4
has caused the Debian Bug report #941218,
regarding guile-2.0: FTBFS on ppc64el
to be marked as done.
This means that you claim that the problem has been dealt with.
If
> I'd preffer to drop pyexiv2 completely. The recommended upstream
> approach was to use GI (and gir1.2-gexiv2-0.10) and that's where most
> of the reverese dependencies have migrated.
Sure, that sounds like a good plan: do you want me to file the RM bug?
--
Sandro "morph" Tosi
My website:
Your message dated Sat, 01 Feb 2020 17:34:21 +
with message-id
and subject line Bug#933105: fixed in makebootfat 1.4-7
has caused the Debian Bug report #933105,
regarding makebootfat FTBFS when /etc/mtab does not exist
to be marked as done.
This means that you claim that the problem has been
Your message dated Sat, 01 Feb 2020 19:36:17 +
with message-id
and subject line Bug#950431: fixed in qemu 1:4.2-3
has caused the Debian Bug report #950431,
regarding qemu-system-ppc: file conflict between qemu-system-{data,ppc}
to be marked as done.
This means that you claim that the problem
Your message dated Sat, 01 Feb 2020 22:49:21 +
with message-id
and subject line Bug#947621: fixed in comitup 1.10-1
has caused the Debian Bug report #947621,
regarding comitup: autopkgtest regression: 'NoneType' object has no attribute
'Reset'
to be marked as done.
This means that you claim
Control: tags 947558 + patch
Control: tags 947558 + pending
Dear maintainer,
I've prepared an NMU for d1x-rebirth (versioned as 0.58.1-1.1) and
uploaded it to DELAYED/5. Please feel free to tell me if I
should delay it longer.
Regards,
Stephen
diff -Nru d1x-rebirth-0.58.1/debian/changelog
Processing control commands:
> tags 947558 + patch
Bug #947558 [src:d1x-rebirth] FTBFS with scons 3.1.2-1
Added tag(s) patch.
> tags 947558 + pending
Bug #947558 [src:d1x-rebirth] FTBFS with scons 3.1.2-1
Added tag(s) pending.
--
947558: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947558
On Sunday, 2 February 2020 2:28:04 AM AEDT Stephen Kitt wrote:
> I've prepared an NMU for d1x-rebirth (versioned as 0.58.1-1.1) and
> uploaded it to DELAYED/5.
Thank you very much for doing this, Stephen. Much appreciated.
--
Cheers,
Dmitry Smirnov.
---
The cure for the evils of democracy is
Package: python-couchdb
Severity: serious
Hello,
i believe this package should be removed from debian:
* currently py2 only in Debian, with py3 support upstream
* no reverse dependencies
* low popcon
* deprecated upstram, python-cloudant suggested as a better replacement
On 01.02.20 13:44, Andreas Beckmann wrote:
> On Wed, 29 Jan 2020 19:51:22 +0100 =?utf-8?q?Tim_R=C3=BChsen?=
> The manpage (dated Feb 25 2002) says:
>
> RESTRICTIONS
>pstack currently works only on Linux, only on an x86 machine
>running 32 bit ELF binaries (64 bit not
According to upstream's notice on http://pyblosxom.github.io/, Pyblosxom
is no longer in active development. There was the attempt to port it to
Python 3 but this one was never completed. Nowadays we have several good
alternatives in Debian that achieve the same thing, e.g. hugo or jekyll.
I
Package: haproxy
Version: 2.0.12-1
Severity: serious
haproxy build-depends-indep on python-mako, which is no longer built by the
mako source package, it is still present in unstable as a cruft package, but is
completely gone from testing.
Processing commands for cont...@bugs.debian.org:
> reassign 941534 src:khronos-api
Bug #941534 [khronos-api] khronos-api: build-depend on texlive-plain-generic,
not obsolete texlive-generic-recommended
Bug reassigned from package 'khronos-api' to 'src:khronos-api'.
No longer marked as found in
Your message dated Sat, 01 Feb 2020 18:19:14 +
with message-id
and subject line Bug#949749: fixed in freeboard 1.1.0+dfsg.1-3
has caused the Debian Bug report #949749,
regarding freeboard: Depends: libjs-codemirror (< 5.49.2.0~) but 5.50.2-1 is to
be installed
to be marked as done.
This
Your message dated Sat, 01 Feb 2020 22:21:39 +
with message-id
and subject line Bug#932532: fixed in getlive 2.4+cvs20120801-1.1
has caused the Debian Bug report #932532,
regarding getlive: Uses manual dh sequence operations that are going to be
removed
to be marked as done.
This means that
Package: getlive
Severity: grave
https://bugs.launchpad.net/ubuntu/+source/getlive/+bug/1654811
https://sourceforge.net/p/getlive/news/2014/05/the-end-of-getlive---stay-tuned/
After more than 7 years being able of implementing change-after-change
on hotmail and hotmail live, I need to give
reopen 94
found 94 1.31.1+dfsg-1
fixed 94 33.0+dfsg-1
thanks
Reopening because packages in stable must build in stable.
Processing commands for cont...@bugs.debian.org:
> reopen 94
Bug #94 {Done: Andreas Tille } [src:ugene] ugene: FTBFS
in buster (dpkg-shlibdeps error)
'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
Package: linbox
Version: 1.6.3-1
Severity: serious
Since I was looking at the linbox failure on armhf, I figured i'd have a look
at the mipsel one too. Based on past experiences with other packages, I was
expecting it to also be related to alignment issues.
However I was wrong! It seems it is
Processing commands for cont...@bugs.debian.org:
> tags 950435 + pending
Bug #950435 [haproxy] haproxy build-depends on package that has been dropped.
Added tag(s) pending.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
950435:
This bug is due to a gap in Python 3 support for pagekite. I submitted
upstream patches to fix the problem. New or patched versions of
socksipychain and pagekite will be needed.
https://github.com/pagekite/PySocksipyChain/pull/10
https://github.com/pagekite/PyPagekite/pull/75
Thanks,
--
Sunil
Processing commands for cont...@bugs.debian.org:
> reassign 941534 src:khronos-api
Bug #941534 [src:khronos-api] khronos-api: build-depend on
texlive-plain-generic, not obsolete texlive-generic-recommended
Ignoring request to reassign bug #941534 to the same package
>
End of message, stopping
01.02.2020 18:53, Adam Borowski wrote:
> Package: qemu-system-ppc
> Version: 1:4.2-2
> Severity: grave
> Justification: renders package uninstallable
>
> Hi!
> Upon upgrading or a fresh install:
>
> Unpacking qemu-system-ppc (1:4.2-2) ...
> dpkg: error processing archive
Your message dated Sat, 01 Feb 2020 21:19:22 +
with message-id
and subject line Bug#950433: fixed in linbox 1.6.3-2
has caused the Debian Bug report #950433,
regarding linbox FTBFS on mipsel, oom while building tests.
to be marked as done.
This means that you claim that the problem has been
Your message dated Sat, 01 Feb 2020 21:19:22 +
with message-id
and subject line Bug#944055: fixed in linbox 1.6.3-2
has caused the Debian Bug report #944055,
regarding linbox ftbfs on armhf, bus errors in the test suite
to be marked as done.
This means that you claim that the problem has
Processing commands for cont...@bugs.debian.org:
> reopen 947884
Bug #947884 {Done: Michael Gilbert } [src:wine]
wine-development: patches for arm64 build 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
Your message dated Sun, 02 Feb 2020 00:49:19 +
with message-id
and subject line Bug#947571: fixed in netpanzer 0.8.7+ds-3
has caused the Debian Bug report #947571,
regarding FTBFS with scons 3.1.2-1
to be marked as done.
This means that you claim that the problem has been dealt with.
If this
Your message dated Sun, 02 Feb 2020 00:49:08 +
with message-id
and subject line Bug#936541: fixed in fonts-rit-sundar 2.0.0+20170909-2
has caused the Debian Bug report #936541,
regarding fonts-rit-sundar: Python2 removal in sid/bullseye
to be marked as done.
This means that you claim that
Processing control commands:
> tag -1 pending
Bug #948420 [src:python-future] python-future ftbfs with Python 3.8
Bug #948506 [src:python-future] python-future ftbfs with 3.8
Added tag(s) pending.
Added tag(s) pending.
--
948420: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=948420
948506:
Control: tag -1 pending
Hello,
Bug #948420 in python-future 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:
libm4ri is in NEW
I would guess that the maintainer uploaded libm4ri and libm4rie to the new
queue together, but the ftpmasters only released the latter and not the former.
The question I guess is whether it is worth doing a source only upload of
libm4rie now, only to have to get it rebuilt
Your message dated Sun, 02 Feb 2020 03:37:22 +
with message-id
and subject line Bug#948420: fixed in python-future 0.18.2-1
has caused the Debian Bug report #948420,
regarding python-future ftbfs with 3.8
to be marked as done.
This means that you claim that the problem has been dealt with.
Processing commands for cont...@bugs.debian.org:
> forwarded 948420 https://github.com/PythonCharmers/python-future/issues/508
Bug #948420 [src:python-future] python-future ftbfs with Python 3.8
Bug #948506 [src:python-future] python-future ftbfs with 3.8
Set Bug forwarded-to-address to
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=896360
I have problems installing flask_socketio (when running flask, I get
"ModuleNotFoundError: No module named 'flask_socketio'"). I tried setting
FLASK_DEBUG=0 (apparently that worked for someone I read) and tried
uninstalling and
Your message dated Sun, 02 Feb 2020 03:37:22 +
with message-id
and subject line Bug#948420: fixed in python-future 0.18.2-1
has caused the Debian Bug report #948420,
regarding python-future ftbfs with Python 3.8
to be marked as done.
This means that you claim that the problem has been dealt
Your message dated Sun, 02 Feb 2020 04:49:52 +
with message-id
and subject line Bug#948841: fixed in openpyxl 3.0.3-1
has caused the Debian Bug report #948841,
regarding openpyxl fails almost all its tests
to be marked as done.
This means that you claim that the problem has been dealt with.
Your message dated Sun, 02 Feb 2020 07:04:54 +
with message-id
and subject line Bug#950061: fixed in pypureomapi 0.8-1
has caused the Debian Bug report #950061,
regarding pypureomapi: missing build dependency on dh-python
to be marked as done.
This means that you claim that the problem has
Your message dated Sat, 1 Feb 2020 21:10:25 -0300
with message-id
and subject line Re: Bug#950396: libqtcore4: libcore4 and 5
has caused the Debian Bug report #950396,
regarding libqtcore4: libcore4 and 5
to be marked as done.
This means that you claim that the problem has been dealt with.
If
Processing commands for cont...@bugs.debian.org:
> found 949896 16.1.3+ds-2
Bug #949896 [src:ecl] ecl: Frequent (parallel?) FTBFS
Marked as found in versions ecl/16.1.3+ds-2.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
949896:
Your message dated Sat, 01 Feb 2020 10:49:30 +
with message-id
and subject line Bug#813596: fixed in coq-float 1:8.9.0-1
has caused the Debian Bug report #813596,
regarding coq-float: FTBFS: make[2]: *** No rule to make target 'depend'. Stop.
to be marked as done.
This means that you claim
Your message dated Sat, 01 Feb 2020 11:04:18 +
with message-id
and subject line Bug#949896: fixed in ecl 16.1.3+ds-4
has caused the Debian Bug report #949896,
regarding ecl: Frequent (parallel?) FTBFS
to be marked as done.
This means that you claim that the problem has been dealt with.
If
* On 1/31/20 8:57 PM, Neal Gompa wrote:
> As for yum and yum-utils, their replacements are dnf and
> dnf-plugins-core (which have subpackages yum and yum-utils
> respectively to act as legacy interfaces).
>
> My understanding is that Mihai Moldovan was working on this for Debian
> for the past
Control: tag -1 pending
Hello,
Bug #950219 in ruby-gnome2 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:
Processing control commands:
> tag -1 pending
Bug #950219 [src:ruby-gnome] ruby-gnome: please Build-Depend on
libgirepository1.0-dev (>= 1.62.0-4~) and libffi-dev (>= 3.3)
Added tag(s) pending.
--
950219: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=950219
Debian Bug Tracking System
Processing control commands:
> tags -1 -moreinfo
Bug #950272 [release.debian.org] buster-pu: package mariadb-10.3
10.3.22-0+deb10u1
Removed tag(s) moreinfo.
> severity -1 normal
Bug #950272 [release.debian.org] buster-pu: package mariadb-10.3
10.3.22-0+deb10u1
Severity set to 'normal' from
Processing commands for cont...@bugs.debian.org:
> affects 950348 src:docker-swarm
Bug #950348 [src:golang-github-docker-engine-api]
golang-github-docker-engine-api: obsolete, incompatible with current docker
version
Added indication that 950348 affects src:docker-swarm
> thanks
Stopping
Control: tags -1 -moreinfo
Control: severity -1 normal
Based on #950309 security updates don't seem to warrant 'serious', so
dropping to 'normal'.
Also removing tag moreinfo that was inherited from a stable update bug
report template. apparently it is not part of the process.
Your message dated Sat, 01 Feb 2020 08:45:39 +
with message-id
and subject line Bug#949731: fixed in qemu 1:4.2-2
has caused the Debian Bug report #949731,
regarding qemu: CVE-2020-1711: block: iscsi: OOB heap access via an unexpected
response of iSCSI Server
to be marked as done.
This
Your message dated Sat, 01 Feb 2020 09:04:23 +
with message-id
and subject line Bug#950219: fixed in ruby-gnome 3.4.1-2
has caused the Debian Bug report #950219,
regarding ruby-gnome: please Build-Depend on libgirepository1.0-dev (>=
1.62.0-4~) and libffi-dev (>= 3.3)
to be marked as done.
Processing commands for cont...@bugs.debian.org:
> forwarded 946267
> https://lists.gnu.org/archive/html/bug-cpio/2020-01/msg1.html
Bug #946267 [cpio] cpio -i --no-absolute-filenames breaks symlinks starting
with / or /..
Bug #946469 [cpio] initramfs-tools-core: unmkinitrams creates broken
On Wed, 29 Jan 2020 19:51:22 +0100 =?utf-8?q?Tim_R=C3=BChsen?=
wrote:
> Web searches so far didn't help.
>
> Any ideas / hints ?
The manpage (dated Feb 25 2002) says:
RESTRICTIONS
pstack currently works only on Linux, only on an x86 machine
running 32 bit ELF binaries (64 bit
Hi Preston!
El vie., 31 ene. 2020 23:36, preston escribió:
> Package: libqtcore4
> Version: libqtcore4
> Severity: serious
> Tags: newcomer ftbfs
> Justification: fails to build from source
>
> Dear Maintainer,
>
> *** Reporter, please consider answering these questions, where appropriate
> ***
Processing commands for cont...@bugs.debian.org:
> notfixed 950103 4.004+git20190612-1
Bug #950103 {Done: Boyuan Yang } [src:fonts-lemonada]
fonts-lemonada FTBFS: KeyError: "glyph 'M' already exists"
No longer marked as fixed in versions 4.004+git20190612-1.
> tags 950340 + sid bullseye
Bug
Processing control commands:
> block 945308 with -1
Bug #945308 [ftp.debian.org] RM: node-array-from -- ROM; is only used by
node-command-join
945308 was not blocked by any bugs.
945308 was not blocking any bugs.
Added blocking bug(s) of 945308: 950422
--
945308:
Package: node-sinon
Version: 8.1.0+ds-1
Severity: serious
Control: block 945308 with -1
Hi,
node-command-join has been requested to be removed (#945308), but
node-sinon still (build-)depends on it.
Please find a solution.
Andreas
Your message dated Sat, 01 Feb 2020 13:34:11 +
with message-id
and subject line Bug#946469: fixed in cpio 2.13+dfsg-2
has caused the Debian Bug report #946469,
regarding cpio -i --no-absolute-filenames breaks symlinks starting with / or /..
to be marked as done.
This means that you claim
Your message dated Sat, 01 Feb 2020 13:34:32 +
with message-id
and subject line Bug#888670: fixed in gnome-system-tools 3.0.0-9
has caused the Debian Bug report #888670,
regarding gnome-system-tools: has been unmaintained upstream for a long time
to be marked as done.
This means that you
Your message dated Sat, 01 Feb 2020 13:34:11 +
with message-id
and subject line Bug#946469: fixed in cpio 2.13+dfsg-2
has caused the Debian Bug report #946469,
regarding initramfs-tools-core: unmkinitrams creates broken binaries
to be marked as done.
This means that you claim that the
Your message dated Sat, 01 Feb 2020 13:34:11 +
with message-id
and subject line Bug#946267: fixed in cpio 2.13+dfsg-2
has caused the Debian Bug report #946267,
regarding initramfs-tools-core: unmkinitrams creates broken binaries
to be marked as done.
This means that you claim that the
Your message dated Sat, 01 Feb 2020 13:34:11 +
with message-id
and subject line Bug#946267: fixed in cpio 2.13+dfsg-2
has caused the Debian Bug report #946267,
regarding cpio -i --no-absolute-filenames breaks symlinks starting with / or /..
to be marked as done.
This means that you claim
Hi,
>Personally, I was surprised that LXDE was kept in Debian; I thought it
>was going to be replaced by LXQt. Are you planning to keep LXDE in
>Bullseye?
Actually LXDE and LXQt are just similar but pretty different desktop
environments and not every LXDE user may feel happy to be forced to use
71 matches
Mail list logo
