Package: libh2o-dev-common
Version: 2.2.5+dfsg2-2+deb10u1
Severity: serious
Justification: 8
Dear Maintainer,
https://wiki.debian.org/Multiarch/Implementation#Multi-Arch:_foreign_support_packages
states that an architecture all package which is used a dependency for an
Architecture: any package
For what it's worth, I could rebuild containerd packages from the 1.2
series, starting from [1] and iterating with different containerd versions.
Starting from containerd version 1.2.7, the containerd binary produced
works. So it looks like we're looking for a change between 1.2.6 and 1.2.7.
Processing control commands:
> severity -1 important
Bug #953996 [src:julia] julia: FTBFS on ppc64el
Severity set to 'important' from 'serious'
--
953996: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953996
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Control: severity -1 important
Downgrading severity since julia was removed on ppc64el.
On 4/12/20 7:49 PM, Chris Lamb wrote:
severity 956502 serious
thanks
Hi,
docker: Error response from daemon: no status provided on response: unknown.
This, too, happens for me. Downgrading to 19.03.6+dfsg1-2 (from
19.03.6+dfsg1-3) restores all functionality.
Marking as RC merely to
Your message dated Mon, 13 Apr 2020 03:34:30 +
with message-id
and subject line Bug#954634: fixed in vulture 1.4-1
has caused the Debian Bug report #954634,
regarding vulture: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i
python{version} -p 3.8 returned exit code 13
to be
Your message dated Mon, 13 Apr 2020 03:34:30 +
with message-id
and subject line Bug#950861: fixed in vulture 1.4-1
has caused the Debian Bug report #950861,
regarding vulture needs a new upstream for Python 3.8
to be marked as done.
This means that you claim that the problem has been dealt
Your message dated Mon, 13 Apr 2020 03:54:31 +0100
with message-id <0e51220b-4409-177a-a4e8-873103457...@p10link.net>
and subject line re: rust-core-arch: FTBFS: dh_auto_test: error:
/usr/share/cargo/bin/cargo build returned exit code 101
has caused the Debian Bug report #952228,
regarding
Package: photocollage
Version: 1.4.3-2.1
Followup-For: Bug #952336
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu focal ubuntu-patch
Hi,
In Ubuntu, the attached patch was applied to achieve the following:
* Build-depend on dh-python to fix FTBFS due to missing python3.pm.
Thanks
Control: tags -1 + patch
Dear maintainers,
unbound can now drop its Python 2 module package as there are no users of that
package left in bullseye.
I've just opened a merge request on salsa to do so:
https://salsa.debian.org/dns-team/unbound/-/merge_requests/8
thanks
Stuart
--
Processing control commands:
> tags -1 + patch
Bug #938752 [src:unbound] unbound: Python2 removal in sid/bullseye
Added tag(s) patch.
--
938752: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=938752
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Hi Ondřej,
src:hash-slinger seems to have been pseudo-orphaned during the move from
alioth to salsa; the maintainer email address no longer works, the VCS was not
copied across to salsa and hash-slinger was removed from testing 21 months
ago.
Upstream, the package has moved from the URL
Nick Gasson writes:
> I had a look at this. It's possible to reproduce the failure inside
> qemu-mipsel-static. The test set-process-filter-t is fundamentally racy:
> it reads output from a sub-process and compares that to an expected
> value. But on a slow machine it's possible to get a partial
Source: gulkan
Followup-For: Bug #955604
Hi,
gulkan builds now on s390x:
https://buildd.debian.org/status/fetch.php?pkg=gulkan=s390x=0.14.0-2=1586175154=0
Best regards,
-Andrew
close 955604
thanks
Processing commands for cont...@bugs.debian.org:
> close 955604
Bug #955604 [src:gulkan] gulkan: unsatisfiable Build-Depends on s390x
Marked Bug as done
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
955604:
Processing control commands:
> severity -1 serious
Bug #955638 [cargo] cargo: please package recent version
Severity set to 'serious' from 'important'
--
955638: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=955638
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Your message dated Mon, 13 Apr 2020 06:48:35 +0900
with message-id <20200412214835.ga15...@burischnitzel.preining.info>
and subject line Re: Bug#956538: kde-config-fcitx5: cannot connect to fcitx via
dbus error message
has caused the Debian Bug report #956538,
regarding kde-config-fcitx5: cannot
Source: coinst
Version: 1.9.3-1
Severity: serious
Tags: ftbfs bullseye sid
https://buildd.debian.org/status/package.php?p=coinst
...
usr/bin/make opt
make[2]: Entering directory '/<>'
ocamlfind ocamlc -package unix,str,bigarray,cudf -g -I viewer -annot -bin-annot
-safe-string -c ptset.mli
Your message dated Sun, 12 Apr 2020 21:18:45 +
with message-id
and subject line Bug#942928: fixed in automake-1.16 1:1.16.2-1
has caused the Debian Bug report #942928,
regarding automake-1.16: Python2 removal in sid/bullseye
to be marked as done.
This means that you claim that the problem
Your message dated Sun, 12 Apr 2020 22:06:06 +0100
with message-id
and subject line re: rust-goblin: autopkgtest failure
has caused the Debian Bug report #947711,
regarding rust-goblin: autopkgtest failure
to be marked as done.
This means that you claim that the problem has been dealt with.
If
Your message dated Sun, 12 Apr 2020 20:40:38 +
with message-id
and subject line Bug#950038: fixed in python-wsgi-intercept 1.9.2-1
has caused the Debian Bug report #950038,
regarding python-wsgi-intercept FTBFS: test failures
to be marked as done.
This means that you claim that the problem
Your message dated Sun, 12 Apr 2020 20:37:23 +
with message-id
and subject line Bug#956488: Removed package(s) from unstable
has caused the Debian Bug report #937658,
regarding python-concurrent.futures: Python2 removal in sid/bullseye
to be marked as done.
This means that you claim that the
Your message dated Sun, 12 Apr 2020 20:37:58 +
with message-id
and subject line Bug#956489: Removed package(s) from unstable
has caused the Debian Bug report #938476,
regarding shedskin: Python2 removal in sid/bullseye
to be marked as done.
This means that you claim that the problem has been
Control: tag -1 pending
Hello,
Bug #950038 in python-wsgi-intercept 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 #950038 [python-wsgi-intercept] python-wsgi-intercept FTBFS: test failures
Added tag(s) pending.
--
950038: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=950038
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Your message dated Sun, 12 Apr 2020 19:03:47 +
with message-id
and subject line Bug#956474: fixed in meep 1.12.0-3
has caused the Debian Bug report #956474,
regarding src:meep: missing several Breaks+Replaces
to be marked as done.
This means that you claim that the problem has been dealt
Your message dated Sun, 12 Apr 2020 19:03:47 +
with message-id
and subject line Bug#953677: fixed in meep 1.12.0-3
has caused the Debian Bug report #953677,
regarding python3-meep: prerm script fails - cannot get content of python-meep
to be marked as done.
This means that you claim that the
Your message dated Sun, 12 Apr 2020 20:36:55 +0200
with message-id <68327bd2-1a78-2572-67e6-3a89b0812...@debian.org>
and subject line Fixed in 1.1.2-1
has caused the Debian Bug report #956323,
regarding sunpy: FTBFS on armel
to be marked as done.
This means that you claim that the problem has
Processing control commands:
> close -1 0.14.1-1
Bug #956550 [src:umockdev] src:umockdev: fails to migrate to testing for too
long
Marked as fixed in versions umockdev/0.14.1-1.
Bug #956550 [src:umockdev] src:umockdev: fails to migrate to testing for too
long
Marked Bug as done
--
956550:
Source: umockdev
Version: 0.13.2-1
Severity: serious
Control: close -1 0.14.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
Processing commands for cont...@bugs.debian.org:
> found 955672 pandas/0.25.3+dfsg-8
Bug #955672 {Done: Scott Talbert } [src:pandas]
python-apptools: FTBFS: ERROR: Failure: ModuleNotFoundError (No module named
'matplotlib')
Marked as found in versions pandas/0.25.3+dfsg-8 and reopened.
> fixed
Processing commands for cont...@bugs.debian.org:
> fixed 955672 pandas/0.25.3+dfsg-9
Bug #955672 {Done: Scott Talbert } [src:python-apptools]
python-apptools: FTBFS: ERROR: Failure: ModuleNotFoundError (No module named
'matplotlib')
Marked as fixed in versions pandas/0.25.3+dfsg-9.
> reassign
Processing commands for cont...@bugs.debian.org:
> notfound 955672 python-apptools/4.5.0-1
Bug #955672 [src:python-apptools] python-apptools: FTBFS: ERROR: Failure:
ModuleNotFoundError (No module named 'matplotlib')
No longer marked as found in versions python-apptools/4.5.0-1.
> found 955672
Your message dated Sun, 12 Apr 2020 13:27:48 -0400 (EDT)
with message-id
and subject line fixed
has caused the Debian Bug report #955672,
regarding python-apptools: FTBFS: ERROR: Failure: ModuleNotFoundError (No
module named 'matplotlib')
to be marked as done.
This means that you claim that the
Your message dated Sun, 12 Apr 2020 16:36:06 +
with message-id
and subject line Bug#954524: fixed in golang-github-koofr-go-httpclient
0.0~git20190818.e0dc8fd-2
has caused the Debian Bug report #954524,
regarding golang-github-koofr-go-httpclient: FTBFS: dh_auto_test: error: cd
Your message dated Sun, 12 Apr 2020 18:38:14 +0200
with message-id <20200412163813.ga30...@debian.org>
and subject line Re: Bug#923698: gcc-mingw-w64 miscompiles PARI
has caused the Debian Bug report #923698,
regarding gcc-mingw-w64 miscompiles PARI
to be marked as done.
This means that you claim
Your message dated Sun, 12 Apr 2020 17:36:01 +0200 (CEST)
with message-id
and subject line closing this bug
has caused the Debian Bug report #940491,
regarding src:meep: missing several Breaks+Replaces
to be marked as done.
This means that you claim that the problem has been dealt with.
If this
Control: tag -1 pending
Hello,
Bug #954524 in golang-github-koofr-go-httpclient 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 #954524 [src:golang-github-koofr-go-httpclient]
golang-github-koofr-go-httpclient: FTBFS: dh_auto_test: error: cd
obj-x86_64-linux-gnu && go test -vet=off -v -p 4 github.com/koofr/go-httpclient
returned exit code 1
Added tag(s) pending.
--
Source: python-cassandra-driver
Version: 3.20.2-1
Severity: serious
Tags: ftbfs sid bullseye
Justification: fails to build from source (but built successfully in the past)
python-cassandra-driver FTBFS on 32 bit arches with
| ==
Your message dated Sun, 12 Apr 2020 15:49:42 +
with message-id
and subject line Bug#956512: fixed in node-unicode-data 0~20200315+gitfc57d75a-3
has caused the Debian Bug report #956512,
regarding node-unicode-data: autopkgtest requires outdated version
to be marked as done.
This means that
Control: tag -1 pending
Hello,
Bug #956512 in node-unicode-data 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 #956512 [node-unicode-13.0.0] node-unicode-data: autopkgtest requires
outdated version
Added tag(s) pending.
--
956512: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=956512
Debian Bug Tracking System
Contact ow...@bugs.debian.org with
Processing commands for cont...@bugs.debian.org:
> tags 953967 + fixed-upstream
Bug #953967 [src:grip] grip: autopkgtest failure with Python 3.8 as default
Added tag(s) fixed-upstream.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
953967:
Source: preprocess
Version: 1.1.0+ds-1
Severity: serious
X-Debbugs-CC: joha...@simula.no
Dear package proprocess maintainer in Debian,
I just took a look at this package, finding that
* It saw no upload since initial upload back in 2011
* Its upstream has no activity since 2009
* It depends on
Your message dated Sun, 12 Apr 2020 14:48:53 +
with message-id
and subject line Bug#953734: fixed in golang-golang-x-tools
1:0.0~git20200410.79a7a31+ds-1
has caused the Debian Bug report #953734,
regarding golang-golang-x-tools: FTBFS with golang-1.14
to be marked as done.
This means that
Your message dated Sun, 12 Apr 2020 14:48:53 +
with message-id
and subject line Bug#953725: fixed in golang-golang-x-tools
1:0.0~git20200410.79a7a31+ds-1
has caused the Debian Bug report #953725,
regarding golang-golang-x-tools: Extremely generic and conflicting binary names
to be marked as
Your message dated Sun, 12 Apr 2020 10:45:50 -0400
with message-id
and subject line Re: urwid-satext: Please make another source-only upload to
allow testing migration
has caused the Debian Bug report #952479,
regarding urwid-satext: Please make another source-only upload to allow testing
Your message dated Sun, 12 Apr 2020 14:36:06 +
with message-id
and subject line Bug#954756: fixed in yt 3.6.0-1
has caused the Debian Bug report #954756,
regarding puppet-module-aboe-chrony depends on obsolete transitional package.
to be marked as done.
This means that you claim that the
Your message dated Sun, 12 Apr 2020 14:35:15 +
with message-id
and subject line Bug#938275: fixed in python-xlib 0.27-1
has caused the Debian Bug report #938275,
regarding python-xlib: Python2 removal in sid/bullseye
to be marked as done.
This means that you claim that the problem has been
Control: tag -1 pending
Hello,
Bug #953725 in golang-go.tools 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 #953725 [golang-golang-x-tools] golang-golang-x-tools: Extremely generic
and conflicting binary names
Added tag(s) pending.
--
953725: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953725
Debian Bug Tracking System
Contact
Processing control commands:
> tags -1 +unreproducible +moreinfo
Bug #956538 [kde-config-fcitx5] kde-config-fcitx5: cannot connect to fcitx via
dbus error message
Added tag(s) unreproducible.
Bug #956538 [kde-config-fcitx5] kde-config-fcitx5: cannot connect to fcitx via
dbus error message
Added
Control: tags -1 +unreproducible +moreinfo
Hi Norbert,
在 2020-04-12星期日的 23:03 +0900，Norbert Preining写道：
> Package: kde-config-fcitx5
> Version: 0.0~git20200403.8afa921-1
> Severity: grave
> Justification: renders package unusable
>
> Dear all,
>
> I am trying to configure fcitx via the
Processing commands for cont...@bugs.debian.org:
> merge 952008 948354
Bug #952008 [src:numpy] numpy: FTBFS: ./_configtest.c:6: undefined reference to
`exp'
Bug #948354 [src:numpy] numpy: hardcodes python2 call into rules file
Added tag(s) sid and bullseye.
Added tag(s) bullseye and sid.
Bug
Package: kde-config-fcitx5
Version: 0.0~git20200403.8afa921-1
Severity: grave
Justification: renders package unusable
Dear all,
I am trying to configure fcitx via the plasma/kde panel, but it gave me
an error
Cannot connect to Fcitx by DBus, is Fcitx running?
Then I tried to start it
Processing commands for cont...@bugs.debian.org:
> merge 948354 956527
Bug #948354 [src:numpy] numpy: hardcodes python2 call into rules file
Bug #956527 [src:numpy] FTBFS: debian/rules still uses python(2) without havind
an explicit dependency
Added tag(s) patch.
Bug #948354 [src:numpy] numpy:
> jp includes /usr/bin/jp, which is already "taken" since ~2013 by
> something completely different, sat-xmpp-jp. Given that jp has
> not yet been part of Debian release, it is probably easy to just
> rename the binary, e.g. jp-cli, jp-jmespath, or jmespath. Thanks!
If we do that, are we
On Sun, Apr 12, 2020 at 02:41:00PM +0200, Ivo De Decker wrote:
> > I very much like to see a chaangelog that tell what changed betwee 8.2
> > and 8.3 that could have fixed this.
>
> So I guess the current version in testing is ok, and the bug can be closed
> there?
>
> If it works on gcc 8.3,
Processing commands for cont...@bugs.debian.org:
> severity 956502 serious
Bug #956502 [docker.io] docker: Error response from daemon: no status provided
on response: unknown.
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.
Please contact me if you need assistance.
Hi,
Thanks for checking the history.
On Sun, Apr 12, 2020 at 01:50:12PM +0200, Bill Allombert wrote:
> > Is this stil an issue with the newer versions of gcc-mingw-w64?
> >
> > Should this bug really be marked as serious?
>
> Please note that I reported the bug as severity normal but Stephen
Control: tag -1 pending
Hello,
Bug #938275 in python-xlib 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 #938275 [src:python-xlib] python-xlib: Python2 removal in sid/bullseye
Added tag(s) pending.
--
938275: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=938275
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Source: numpy
Version: 1:1.17.4-5
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
Hello,
numpy FTBFS with the following error:
python debian/versions3.helper >> debian/python3-numpy.substvars
/bin/sh: 1: python: not found
It
I had a look at this. It's possible to reproduce the failure inside
qemu-mipsel-static. The test set-process-filter-t is fundamentally racy:
it reads output from a sub-process and compares that to an expected
value. But on a slow machine it's possible to get a partial read from
the child process
Your message dated Sun, 12 Apr 2020 12:59:11 +0100
with message-id <20200412115911.ga91...@espresso.pseudorandom.co.uk>
and subject line Re: Bug#956451: gnome-shell-extension-appindicator:
uninstallable in unstable: please update for GNOME Shell 3.36.x
has caused the Debian Bug report #956451,
Control: severity -1 important
Control: tags -1 + moreinfo
Control: user pkg-gnome-maintain...@lists.alioth.debian.org
Control: usertags -1 + wayland
On Tue, 08 Oct 2019 at 13:59:12 -0400, Zack Weinberg wrote:
> On my computer, after upgrading to gnome-shell 3.34, I consistently get a
>
Processing control commands:
> severity -1 important
Bug #941991 [gnome-shell] gnome-shell: crashes on startup (Wayland only) with
"JS ERROR: TypeError: actor.get_meta_window(...) is null"
Severity set to 'important' from 'grave'
> tags -1 + moreinfo
Bug #941991 [gnome-shell] gnome-shell:
On Sun, Apr 12, 2020 at 12:02:38PM +0200, Ivo De Decker wrote:
> Hi Stephen, Bill,
>
> While looking at RC bugs that have been open for I while, I noticed this one.
>
> On Thu, Mar 07, 2019 at 09:07:15AM +0100, Stephen Kitt wrote:
> > Subject: Re: Bug#923698: gcc-mingw-w64 miscompiles PARI
>
>
Your message dated Sun, 12 Apr 2020 11:48:52 +
with message-id
and subject line Bug#93: fixed in haproxy 2.1.4-1
has caused the Debian Bug report #93,
regarding haproxy - unreachable maintainer
to be marked as done.
This means that you claim that the problem has been dealt with.
If
Package: mousetweaks
Version: 3.12.0-5
Severity: grave
Dear Debian maintainers,
This tool is not working at all and dumps core.
gdb outputs are attached, generated in 2 runs by the commands
gdb -batch -n -ex 'set pagination off' -ex run -ex bt -ex 'bt full' -ex
'thread apply all bt full'
Per upstream's currently supported platforms [1]:
PowerPC (64-bit) is tier3:
Julia may or may not build. If it does, it is unlikely to pass tests.
Binaries may be available in some cases. When they are, they should be
considered experimental. Ongoing support is dependent on community
efforts.
I
Package: node-rw
Version: 1.3.3-1
Severity: serious
Tags: patch
One of this package's upstream tests (encoding-async) requires
(node-)d3-queue. It build-depends on this, but does not test-depend on
it (debian/tests/control last test), so the autopkgtest fails.
Tags 952228 +patch
Thanks
> = help: add `#![feature(custom_inner_attributes)]` to the crate attributes
to enable
After doing some googling to find out what "crate attributes" were I was able
to put together a patch that makes the package build successfully.
Debdiff is attached, I may or
Processing commands for cont...@bugs.debian.org:
> Tags 952228 +patch
Bug #952228 [src:rust-core-arch] rust-core-arch: FTBFS: dh_auto_test: error:
/usr/share/cargo/bin/cargo build returned exit code 101
Added tag(s) patch.
> Thanks
Stopping processing here.
Please contact me if you need
Processing commands for cont...@bugs.debian.org:
> fixed 955678 0.10.0+really0.0.3-1
Bug #955678 {Done: Pirate Praveen }
[src:ruby-mail-room] ruby-mail-room: FTBFS: ERROR: Test "ruby2.7" failed:
Failure/Error: expect(redis.client.instance_variable_get(:@connector)).to be_a
Your message dated Sun, 12 Apr 2020 15:55:19 +0530
with message-id <7m7o8q.axi5t14j9u...@onenetbeyond.org>
and subject line fixed in last upload
has caused the Debian Bug report #955678,
regarding ruby-mail-room: FTBFS: ERROR: Test "ruby2.7" failed: Failure/Error:
On Sat, 2020-04-11 at 09:54 +0800, Paul Wise wrote:
> Actually it looks like this is not fixed after all.
In addition to the bug not being fixed, today I got a false positive on
the message that a package needs a conffile prompt. The package got
upgraded successfully and didn't fail due to a
Hi Stephen, Bill,
While looking at RC bugs that have been open for I while, I noticed this one.
On Thu, Mar 07, 2019 at 09:07:15AM +0100, Stephen Kitt wrote:
> Subject: Re: Bug#923698: gcc-mingw-w64 miscompiles PARI
[...]
> I don’t have any practical suggestion right now, but given that
Processing commands for cont...@bugs.debian.org:
> severity 946921 important
Bug #946921 [src:rust-spin] Project abandoned
Severity set to 'important' from 'serious'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
946921:
severity 946921 important
thanks
On Sun, Apr 12, 2020 at 09:28:52AM +0100, peter green wrote:
> > https://rustsec.org/advisories/RUSTSEC-2019-0031.html was issued to flag
> > that
> > rust-spin development stop. I suppose that means it should not enter
> > bullseye
> > / get removed.
> This
Your message dated Sun, 12 Apr 2020 09:49:14 +
with message-id
and subject line Bug#952164: fixed in golang-github-go-stack-stack 1.8.0-1
has caused the Debian Bug report #952164,
regarding golang-github-go-stack-stack: FTBFS: dh_auto_test: error: cd
obj-x86_64-linux-gnu && go test -vet=off
Package: node-unicode-13.0.0
Version: 0~20200315+gitfc57d75a-2
Severity: serious
Tags: patch
The autopkgtest includes the versioned package name (in both
debian/tests/control and debian/tests/require). As these were not
updated when this changed from 12 to 13, the autopkgtest fails as
Your message dated Sun, 12 Apr 2020 09:30:26 +
with message-id
and subject line Bug#956507: fixed in pegjs 0.10.0-2
has caused the Debian Bug report #956507,
regarding pegjs: stray Provides: nodejs
to be marked as done.
This means that you claim that the problem has been dealt with.
If this
Your message dated Sun, 12 Apr 2020 09:29:49 +
with message-id
and subject line Bug#956149: fixed in cclib-data 1.6.2-2
has caused the Debian Bug report #956149,
regarding cclib-data: FTBFS with python3.8: ModuleNotFoundError: No module
named 'pybel'
to be marked as done.
This means that
Your message dated Sun, 12 Apr 2020 09:30:20 +
with message-id
and subject line Bug#956503: fixed in node-lodash-reevaluate 3.0.0-2
has caused the Debian Bug report #956503,
regarding node-lodash-reevaluate: mis-spelled test dependency
to be marked as done.
This means that you claim that the
Processing control commands:
> tags -1 - wontfix
Bug #953590 [libplacebo21] libplacebo21: Upload to unstable, please
Removed tag(s) wontfix.
> block -1 by 956510
Bug #953590 [libplacebo21] libplacebo21: Upload to unstable, please
953590 was not blocked by any bugs.
953590 was not blocking any
On 2020-04-12 11:04:38 +0200, Sebastian Ramacher wrote:
> Package: spirv-tools
> Version: 2020.2-1
> Severity: serious
>
> libplacebo now manually links the libraries from spirv-tools
> (libSPIRV-Tools and libSPIRV-Tools-opt) to work-around #951988 and
> #955431. Since the switch to shared
Package: spirv-tools
Version: 2020.2-1
Severity: serious
libplacebo now manually links the libraries from spirv-tools
(libSPIRV-Tools and libSPIRV-Tools-opt) to work-around #951988 and
#955431. Since the switch to shared libraries, however, dpkg-shlibdeps
is unable to produce the correct
Control: tag -1 pending
Hello,
Bug #956503 in node-lodash-reevaluate 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 #956503 [node-lodash-reevaluate] node-lodash-reevaluate: mis-spelled test
dependency
Added tag(s) pending.
--
956503: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=956503
Debian Bug Tracking System
Contact ow...@bugs.debian.org with
Control: tag -1 pending
Hello,
Bug #956507 in pegjs 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 #956507 [pegjs] pegjs: stray Provides: nodejs
Added tag(s) pending.
--
956507: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=956507
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processing control commands:
> tag -1 pending
Bug #952061 [src:ibsim] ibsim: FTBFS: umad2sim.c:110:30: error: ‘UMAD_DEV_DIR’
undeclared here (not in a function)
Added tag(s) pending.
--
952061: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952061
Debian Bug Tracking System
Contact
https://rustsec.org/advisories/RUSTSEC-2019-0031.html was issued to flag that
rust-spin development stop. I suppose that means it should not enter bullseye
/ get removed.
This bug is currently one of several blockers for getting rust-cbindgen back
into testing and thus making the
Control: tag -1 pending
Hello,
Bug #952061 in ibsim 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:
Package: pegjs
Version: 0.10.0-1
Tags: patch
Severity: serious
debian/control lists a Provides: nodejs.
This is obviously wrong, and also causes the autopkgtest to fail by not
installing the real nodejs.
Package: src:freecad
Followup-For: Bug #953721
Control: tags -1 -pending
I've just cancelled the NMU, because the updated package would be affected by
the pyside bug #945376, which breaks the PartDesign Workbench and thus would
would severly break freecads functionality.
--
tobi
Processing control commands:
> tags -1 -pending
Bug #953721 [src:freecad] freecad: FTBFS with Python 3.8
Removed tag(s) pending.
--
953721: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953721
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
1 - 100 of 104 matches
Mail list logo
