Your message dated Thu, 11 Nov 2021 07:33:41 +
with message-id
and subject line Bug#997516: fixed in guile-ssh 0.13.1-5
has caused the Debian Bug report #997516,
regarding guile-ssh: FTBFS: dh_auto_test: error: cd debian/build/guile-3.0 &&
make -j1 check VERBOSE=1 returned exit code 2
to be m
Processing commands for cont...@bugs.debian.org:
> tags 996364 fixed-upstream
Bug #996364 [src:ruby-recursive-open-struct] ruby-recursive-open-struct: FTBFS
with ruby3.0: ERROR: Test "ruby3.0" failed: Failure/Error: alias_method
:modifiable?, :modifiable
Added tag(s) fixed-upstream.
> thanks
Sto
Processing control commands:
> severity -1 serious
Bug #994335 [src:pynfft] pynfft: Removal of the python3-*-dbg packages in
sid/bookworm
Severity set to 'serious' from 'important'
--
994335: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=994335
Debian Bug Tracking System
Contact ow...@bugs.
Processing control commands:
> severity -1 serious
Bug #994304 [src:libgpuarray] libgpuarray: Removal of the python3-*-dbg
packages in sid/bookworm
Severity set to 'serious' from 'important'
--
994304: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=994304
Debian Bug Tracking System
Contact o
Your message dated Thu, 11 Nov 2021 03:18:31 +
with message-id
and subject line Bug#998449: fixed in golang-github-containernetworking-plugins
0.9.1+ds1-1
has caused the Debian Bug report #998449,
regarding autopkgtest: dh-golang-autopkgtest FAIL non-zero exit status 2
to be marked as done.
Source: golang-github-containerd-stargz-snapshotter
Version: 0.8.0-3
Severity: serious
X-Debbugs-Cc: z...@debian.org
https://buildd.debian.org/status/fetch.php?pkg=golang-github-containerd-stargz-snapshotter&arch=all&ver=0.8.0-4&stamp=1636327998&raw=0
=== RUN TestLayerConvertFunc
estargz_te
Your message dated Thu, 11 Nov 2021 03:03:29 +
with message-id
and subject line Bug#998358: fixed in grepmail 5.3104-4
has caused the Debian Bug report #998358,
regarding Subject: grepmail: autopkgtest doesn't do anything
to be marked as done.
This means that you claim that the problem has be
Em qua., 10 de nov. de 2021 às 18:55, Paul Gevers escreveu:
>
> Hi Eriberto,
>
> On Tue, 2 Nov 2021 19:57:37 -0300 Eriberto wrote:
> > ow, Marcos will package the new upstream
> > release and he will fix this mistake. In a final action, he will send
> > a SPU to fix a specific issue.
>
> Please b
On Tue, 2021-11-09 at 22:56 +1100, David Bannon wrote:
> No, sorry, I cannot do a sensible test of my app using FPC and/or
> Lazarus from sid.
>
> I can install FPC3.2.2 from Sid by using priorities.
>
> But the Lazarus in Sid is non functional, blocked, because of an
> issue
OK, I have
Your message dated Thu, 11 Nov 2021 01:18:47 +
with message-id
and subject line Bug#997300: fixed in ruby-mini-portile2 2.5.0-3
has caused the Debian Bug report #997300,
regarding ruby-mini-portile2: FTBFS: ERROR: Test "ruby2.7" failed:
RuntimeError: Failed to complete configure task
to be ma
Processing commands for cont...@bugs.debian.org:
> # https://github.com/hashicorp/vagrant/pull/12427
> tags 996529 + patch
Bug #996529 [src:vagrant] vagrant: FTBFS with ruby3.0: ERROR: Test "ruby3.0"
failed: RuntimeError:
Added tag(s) patch.
> thanks
Stopping processing here.
Please contact
On 11/10/21 16:25, Simon Josefsson wrote:
James Valleroy via "Discussion list for GNU Internationalized Domain
Name library (Libidn)" writes:
On 11/10/21 6:40 AM, Simon Josefsson wrote:
James, what do you think? Is the libidn11-java package important for
you to have in Debian? My perception
Your message dated Thu, 11 Nov 2021 00:33:29 +
with message-id
and subject line Bug#997394: fixed in libjpeg-turbo 1:2.1.1-1
has caused the Debian Bug report #997394,
regarding libjpeg-turbo: FTBFS: dh_auto_configure: error: cd
obj-x86_64-linux-gnu && cmake -DCMAKE_INSTALL_PREFIX=/usr
-DCMAK
On Fri, 5 Nov 2021 05:55:52 +0100 Florian Schlichting wrote:
> Hi Ryan (and Max please see below):
>
> please, for now, delete or comment out the pid_file line
I'm responding to this bug as commenting out the pid_file line was the solution
for me too, but my 'symptoms' are (a bit) different.
Fo
Unfortunately the system which exhibited the problem has now been
updated with a working version after I kludged it to work.
However, what happens is the shared libraries are all linked twice. The
first time it is linked to libraries in the build tree (and do not have
links to the old . They a
Your message dated Wed, 10 Nov 2021 23:03:50 +
with message-id
and subject line Bug#984199: fixed in libpappsomspp 0.8.39-1
has caused the Debian Bug report #984199,
regarding libpappsomspp: ftbfs with GCC-11
to be marked as done.
This means that you claim that the problem has been dealt with
On Thu, 11 Nov 2021 at 10:49, Paul Gevers wrote:
> Hi Michael,
>
> On Wed, 10 Nov 2021 16:16:53 +1300 Michael Hudson-Doyle
> wrote:
> > Hi, thanks for this fix. I think it meets the threshold for NMU (and also
> > the maintainer seems to have been awol since 2015) so I'm uploading it to
> > DELA
Hi Eriberto,
On Tue, 2 Nov 2021 19:57:37 -0300 Eriberto wrote:
> ow, Marcos will package the new upstream
> release and he will fix this mistake. In a final action, he will send
> a SPU to fix a specific issue.
Please be aware that grepmail will be removed from testing in 7 days if
the issue isn
Hi Michael,
On Wed, 10 Nov 2021 16:16:53 +1300 Michael Hudson-Doyle
wrote:
> Hi, thanks for this fix. I think it meets the threshold for NMU (and also
> the maintainer seems to have been awol since 2015) so I'm uploading it to
> DELAYED/10.
I was working on this yesterday and uploaded to DELAYED
Control: tags -1 + patch
Hi Simon
On 10.11.21 20:44, Michael Biebl wrote:
Simon,
any news here?
Would you mind if I prepare an NMU with
26bbf5a314d833beaf0f147d24409969f05f3dba ?
I decided to follow the rules in [1] and uploaded a fixed package to
DELAYED/2. Please holler if you want me t
Processing control commands:
> tags -1 + patch
Bug #995655 [dnsmasq] dnsmasq breaks systemd autopkgtest: b'megasearch.net:
192.168.42.1' not found in b'megasearch.net: 207.148.248.143
Added tag(s) patch.
--
995655: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995655
Debian Bug Tracking Sys
Source: guix
Version: 1.2.0-4
Severity: serious
Control: close -1 1.3.0-2
Tags: sid bookworm
User: release.debian@packages.debian.org
Usertags: out-of-sync
Dear maintainer(s),
The Release Team considers packages that are out-of-sync between testing
and unstable for more than 60 days as having
Processing control commands:
> close -1 1.3.0-2
Bug #999429 [src:guix] src:guix: fails to migrate to testing for too long:
FTBFS on i386
Marked as fixed in versions guix/1.3.0-2.
Bug #999429 [src:guix] src:guix: fails to migrate to testing for too long:
FTBFS on i386
Marked Bug as done
--
9994
Hi,
Any help needed for this?
Regards,
Gabriel
Processing commands for cont...@bugs.debian.org:
> reassign 998449 src:golang-github-containernetworking-plugins,src:libpod
Bug #998449 [src:golang-github-containernetworking-plugin,src:libpod]
autopkgtest: dh-golang-autopkgtest FAIL non-zero exit status 2
Warning: Unknown package 'src:golang-git
Processing commands for cont...@bugs.debian.org:
> reassign 998449 src:golang-github-containernetworking-plugin,src:libpod
Bug #998449 [src:libpod] autopkgtest: dh-golang-autopkgtest FAIL non-zero exit
status 2
Bug reassigned from package 'src:libpod' to
'src:golang-github-containernetworking-pl
reassign 998449 src:golang-github-containernetworking-plugin,src:libpod
found 998449 golang-github-containernetworking-plugins/0.9.1-1
found 998449 libpod/3.4.1+ds1-2
thanks
Hi,
I'm seeing this bug as caused by the
golang-github-containernetworking-plugin upload in the excuses of that
package. He
Control: tags 994239 + patch
Control: tags 994239 + pending
Dear maintainer,
I've prepared an NMU for micropython (versioned as 1.17+ds-1.1) and
uploaded it to DELAYED/5. Please feel free to tell me if I
should delay it longer.
Regards.
diff -Nru micropython-1.17+ds/debian/changelog micropython
Processing control commands:
> tags 994239 + patch
Bug #994239 [src:micropython] work around ftbfs with GCC 11
Added tag(s) patch.
> tags 994239 + pending
Bug #994239 [src:micropython] work around ftbfs with GCC 11
Added tag(s) pending.
--
994239: https://bugs.debian.org/cgi-bin/bugreport.cgi?bu
On Wed, 10 Nov 2021 00:59:02 +0100 Christoph Anton Mitterer
wrote:
> Not sure if this is related, but since a while I've noted even bigger
> than the usual performance problems of firefox...
>
> Crackling sound is something I've heard for a month now... but since
> about FF93 came out CPU utilisa
Package: deluge
Version: 2.0.3-3.1
Severity: grave
When starting Deluge it fails when it attempts to import deluge.libtorrent.
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/deluge/_libtorrent.py", line 23, in
import deluge.libtorrent as lt
ModuleNotFoundError: No
On 2021-11-09 19:26, Chris Carr wrote:
> - please could you explain why it is not suitable for inclusion in
> bullseye? What is it that I am not seeing or experiencing in my daily
> use of it?
Problem is, that Trac (up to version 1.4) used to be a Python 2 program.
Python 2 is not supported any
Simon,
any news here?
Would you mind if I prepare an NMU with
26bbf5a314d833beaf0f147d24409969f05f3dba ?
Regards,
Michael
On Sun, 3 Oct 2021 21:32:53 +0200 Michael Biebl
wrote:
> Control: reassign -1 dnsmasq/2.86-1
>
> It's a (known) regression in dnsmasq 2.86-1
>
> CCing what I sent Simon p
Your message dated Wed, 10 Nov 2021 18:38:33 +0100
with message-id
and subject line Re: view3dscene: FTBFS with fpc 3.2.2
has caused the Debian Bug report #997940,
regarding view3dscene: FTBFS with fpc 3.2.2
to be marked as done.
This means that you claim that the problem has been dealt with.
If
Your message dated Wed, 10 Nov 2021 17:34:34 +
with message-id
and subject line Bug#997565: fixed in golang-github-xeipuuv-gojsonschema 1.2.0-2
has caused the Debian Bug report #997565,
regarding golang-github-xeipuuv-gojsonschema: FTBFS: dh_auto_test: error: cd
obj-x86_64-linux-gnu && go tes
Your message dated Wed, 10 Nov 2021 17:35:31 +
with message-id
and subject line Bug#984372: fixed in tripwire 2.4.3.7-4
has caused the Debian Bug report #984372,
regarding tripwire: ftbfs with GCC-11
to be marked as done.
This means that you claim that the problem has been dealt with.
If this
Control: tag -1 patch
On Wed, Nov 10, 2021 at 7:55 AM Shengjing Zhu wrote:
>
> > > Cloud you backport following commit?
> > >
> > >
> https://github.com/containers/libocispec/commit/8489d9b60105e487564c9966b5748e2a6ea2855b
> > >
>
> This patch updates libocispec/Makefile.am, which is needed to b
Processing control commands:
> tag -1 patch
Bug #997225 [src:crun] crun: FTBFS:
./libocispec/src/runtime_spec_schema_config_schema.c:2661: undefined reference
to `gen_runtime_spec_schema_config_zos'
Added tag(s) patch.
--
997225: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997225
Debian
Sorry, the second copy of my previous email was actually sent first,
from a defunct email account, I had accidentally set the From field
wrong. Apologies for the duplication.
Your message dated Wed, 10 Nov 2021 16:48:57 +
with message-id
and subject line Bug#998894: fixed in wlcs 1.3.0-3
has caused the Debian Bug report #998894,
regarding wlcs FTBFS with GTest 1.11
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not
Processing control commands:
> reassign -1 python3-typed-ast
Bug #998854 [python3.9] undefined symbol: _PyUnicode_DecodeUnicodeEscape
Bug reassigned from package 'python3.9' to 'python3-typed-ast'.
No longer marked as found in versions python3.9/3.9.8-1.
Ignoring request to alter fixed versions of
Your message dated Wed, 10 Nov 2021 17:05:30 +0100
with message-id
and subject line Re: Bug#998414: mimeo: autopkgtest regression: test depends on
postgresql-14-pgtap which doesn't exist (yet)
has caused the Debian Bug report #998414,
regarding mimeo: autopkgtest regression: test depends on postg
Your message dated Wed, 10 Nov 2021 15:34:14 +
with message-id
and subject line Bug#996781: fixed in luarocks 3.8.0+dfsg1-1
has caused the Debian Bug report #996781,
regarding luarocks: Installation fails with dpkg error
to be marked as done.
This means that you claim that the problem has bee
Your message dated Wed, 10 Nov 2021 15:22:37 +
with message-id
and subject line Bug#996931: fixed in python-django 2:3.2.9-2
has caused the Debian Bug report #996931,
regarding python3-django needs Breaks for the bullseye lava-server
to be marked as done.
This means that you claim that the pr
Your message dated Wed, 10 Nov 2021 15:22:37 +
with message-id
and subject line Bug#983618: fixed in python-django 2:3.2.9-2
has caused the Debian Bug report #983618,
regarding python3-django 3.2 breaks python3-django-pyscss
to be marked as done.
This means that you claim that the problem has
Your message dated Wed, 10 Nov 2021 15:19:02 +
with message-id
and subject line Bug#998542: fixed in devscripts 2.21.5
has caused the Debian Bug report #998542,
regarding devscripts: FTBFS: dh_auto_test: error: make -j4 test returned exit
code 2
to be marked as done.
This means that you clai
Processing control commands:
> tag -1 pending
Bug #983618 [python3-django] python3-django 3.2 breaks python3-django-pyscss
Added tag(s) pending.
--
983618: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=983618
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Control: tag -1 pending
Hello,
Bug #983618 in python-django 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/python-team/packages/python-django/-/commit/5d11c246
yep, that, sorry. I mean it's missing a Replaces.
On Wed, Nov 10, 2021 at 3:24 PM Axel Beckert wrote:
>
> Hi Mattia,
>
> Mattia Rizzolo wrote:
> > Control: reopen -1
> >
> > On Wed, Nov 10, 2021 at 03:01:11PM +0100, Axel Beckert wrote:
> > > I also noticed just now that I got it the wrong way ar
Control: tag -1 pending
Hello,
Bug #996931 in python-django 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/python-team/packages/python-django/-/commit/55f258c3
Processing control commands:
> tag -1 pending
Bug #996931 [python3-django] python3-django needs Breaks for the bullseye
lava-server
Added tag(s) pending.
--
996931: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996931
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Your message dated Wed, 10 Nov 2021 14:48:39 +
with message-id
and subject line Bug#997150: fixed in bitwise 0.43-1
has caused the Debian Bug report #997150,
regarding bitwise: FTBFS: src/interactive.c:117:17: error: format not a string
literal and no format arguments [-Werror=format-security
Hi Mattia,
Mattia Rizzolo wrote:
> Control: reopen -1
>
> On Wed, Nov 10, 2021 at 03:01:11PM +0100, Axel Beckert wrote:
> > I also noticed just now that I got it the wrong way around in that
> > comment: These headers need to go into node-slice-ansi, not into
> > node-string-width. But luckily Ma
Processing control commands:
> reopen -1
Bug #998911 {Done: Yadd } [node-string-width,node-slice-ansi]
node-string-width: file conflict with node-slice-ansi
Bug #998886 {Done: Yadd } [node-string-width,node-slice-ansi]
node-string-width,node-slice-ansi: both ship
/usr/share/nodejs/is-fullwidth-
Control: reopen -1
On Wed, Nov 10, 2021 at 03:01:11PM +0100, Axel Beckert wrote:
> I also noticed just now that I got it the wrong way around in that
> comment: These headers need to go into node-slice-ansi, not into
> node-string-width. But luckily Mattia got it right:
>
> Mattia Rizzolo wrote:
Processing commands for cont...@bugs.debian.org:
> # Re-add fixed version again as well
> fixed 998886 node-string-width/4.2.3+~9.2.2-1
Bug #998886 {Done: Yadd } [node-string-width,node-slice-ansi]
node-string-width,node-slice-ansi: both ship
/usr/share/nodejs/is-fullwidth-code-point/*
Bug #9989
Processing commands for cont...@bugs.debian.org:
> # Missing Breaks and Replaces headers were actually in node-slice-ansi, sorry
> for the confusion
> notfound 998886 node-string-width/4.2.3+~9.2.2-1
Bug #998886 {Done: Yadd } [node-string-width,node-slice-ansi]
node-string-width,node-slice-ansi:
Source: libayatana-indicator
Version: 0.8.4-2
Severity: serious
On 2021-11-10 13:49, Debian FTP Masters wrote:
> Version check failed:
> Your upload included the binary package ayatana-indicator-common, version
> 0.8.4-3, for all,
> however testing already has version 0.9.5-1.
> Uploads to unstab
Hi Yadd,
Yadd wrote:
> you reopened this bug, however node-string-width is really fixed in
> version 4.2.3+~9.2.2-1 (no more is-fullwidth-code-point). What should I do ?
I mentioned it in my mail which reopened the bug:
| # Missing Breaks and Replaces headers in node-string-width/4.2.3+~9.2.2-1
Your message dated Wed, 10 Nov 2021 13:34:59 +
with message-id
and subject line Bug#998886: fixed in node-slice-ansi 5.0.0+~4.0.0-3
has caused the Debian Bug report #998886,
regarding node-string-width: file conflict with node-slice-ansi
to be marked as done.
This means that you claim that th
Your message dated Wed, 10 Nov 2021 13:34:59 +
with message-id
and subject line Bug#998886: fixed in node-slice-ansi 5.0.0+~4.0.0-3
has caused the Debian Bug report #998886,
regarding node-string-width,node-slice-ansi: both ship
/usr/share/nodejs/is-fullwidth-code-point/*
to be marked as done
On Wed, Nov 10, 2021 at 02:13:46PM +0100, Yadd wrote:
> you reopened this bug, however node-string-width is really fixed in
> version 4.2.3+~9.2.2-1 (no more is-fullwidth-code-point). What should I do ?
Without too many checks, I believe node-slice-ansi should have a
Breaks+Replace: node-string-wi
Control: tag -1 pending
Hello,
Bug #998886 in node-slice-ansi 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/js-team/node-slice-ansi/-/commit/55b4a3725ace58c24
Processing control commands:
> tag -1 pending
Bug #998886 [node-string-width,node-slice-ansi]
node-string-width,node-slice-ansi: both ship
/usr/share/nodejs/is-fullwidth-code-point/*
Bug #998911 [node-string-width,node-slice-ansi] node-string-width: file
conflict with node-slice-ansi
Added tag(
Your message dated Wed, 10 Nov 2021 13:18:38 +
with message-id
and subject line Bug#998233: fixed in gcc-doc-defaults 5:23
has caused the Debian Bug report #998233,
regarding gcc-doc-defaults: FTBFS with gcc-11 being the default
to be marked as done.
This means that you claim that the problem
Control: tags -1 + moreinfo
Hi Axel,
you reopened this bug, however node-string-width is really fixed in
version 4.2.3+~9.2.2-1 (no more is-fullwidth-code-point). What should I do ?
Cheers,
Yadd
$ dpkg -l node-string-width && dpkg -L node-string-width
||/ Name VersionArchit
Processing control commands:
> tags -1 + moreinfo
Bug #998911 [node-string-width,node-slice-ansi] node-string-width: file
conflict with node-slice-ansi
Bug #998886 [node-string-width,node-slice-ansi]
node-string-width,node-slice-ansi: both ship
/usr/share/nodejs/is-fullwidth-code-point/*
Added
Processing commands for cont...@bugs.debian.org:
> forwarded 996323
> https://github.com/steveklabnik/mono_logger/commit/58b71f0fb830272dd45bdf01c0fe03c478a9e085
Bug #996323 [src:ruby-mono-logger] ruby-mono-logger: FTBFS with ruby3.0: ERROR:
Test "ruby3.0" failed: ArgumentError: wrong number of
Processing commands for cont...@bugs.debian.org:
> forwarded 996320
> https://github.com/seattlerb/minitest-excludes/commit/7ed688995be9a49c0f6b65bd07eb9cb87053676a
Bug #996320 [src:ruby-minitest-excludes] ruby-minitest-excludes: FTBFS with
ruby3.0: ERROR: Test "ruby3.0" failed.
Set Bug forwarde
Processing commands for cont...@bugs.debian.org:
> tags 996296 fixed-upstream
Bug #996296 [src:ruby-ice-cube] ruby-ice-cube: FTBFS with ruby3.0: ERROR: Test
"ruby3.0" failed:ArgumentError:
Added tag(s) fixed-upstream.
> thanks
Stopping processing here.
Please contact me if you need assis
On Wed, Nov 10, 2021 at 07:27:58AM -0500, Reinhard Tartler wrote:
> That's not sufficient.
>
> the commit you point out does two things:
>
> - update the submodules for 'image-spec' and 'runtime-spec' (which the
> Debian package currently overrides with the distro-provided copies)
> - zos-rela
Processing commands for cont...@bugs.debian.org:
> tags 984028 + fixed-in-experimental
Bug #984028 {Done: Kari Pahula } [src:cxxtools] cxxtools:
ftbfs with GCC-11
Added tag(s) fixed-in-experimental.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
984028: https://
Processing commands for cont...@bugs.debian.org:
> tags 984053 fixed-upstream
Bug #984053 [src:etl] etl: ftbfs with GCC-11
Bug #984355 [src:etl] synfig: ftbfs with GCC-11
Bug #984357 [src:etl] synfigstudio: ftbfs with GCC-11
Added tag(s) fixed-upstream.
Added tag(s) fixed-upstream.
Added tag(s) fi
Looking more into it, here are more observations:
- crun upstream has a git submodule on 'libocispec' (the repo you asked me
to backport). The release tarballs contain a copy of the submodule contents
at the time of the release
- the 'libocispec' submodule contains two additional submodules
'image
Control: forwarded -1
https://git.codesynthesis.com/cgit/odb/libodb/commit/?id=13dd928ae18ef9610bc820b7b3e65629addea1d2
Control: tags -1 patch
On Wed, Mar 03, 2021 at 04:14:40PM +, Matthias Klose wrote:
> Package: src:libodb
> Version: 2.4.0-1
> Severity: normal
> Tags: sid bookworm
> User: d
Processing control commands:
> forwarded -1
> https://git.codesynthesis.com/cgit/odb/libodb/commit/?id=13dd928ae18ef9610bc820b7b3e65629addea1d2
Bug #984191 [src:libodb] libodb: ftbfs with GCC-11
Bug #984189 [src:libodb] libodb-boost: ftbfs with GCC-11
Bug #984192 [src:libodb] libodb-qt: ftbfs wit
That's not sufficient.
the commit you point out does two things:
- update the submodules for 'image-spec' and 'runtime-spec' (which the
Debian package currently overrides with the distro-provided copies)
- zos-related changes to the rust bindings (which the Debian package
doesn't have at all a
Control: tags 984027 + patch
Control: tags 984027 + pending
Dear maintainer,
I've prepared an NMU for darkice (versioned as 1.3-0.3) and uploaded
it to DELAYED/15. Please feel free to tell me if I should cancel it.
cu
Adrian
diff -Nru darkice-1.3/debian/changelog darkice-1.3/debian/changelog
---
Processing control commands:
> tags 984027 + patch
Bug #984027 [src:darkice] darkice: ftbfs with GCC-11
Added tag(s) patch.
> tags 984027 + pending
Bug #984027 [src:darkice] darkice: ftbfs with GCC-11
Added tag(s) pending.
--
984027: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984027
Debia
Processing control commands:
> reassign -1 src:opencv
Bug #998141 [src:opencv, src:auto-multiple-choice] opencv breaks
auto-multiple-choice autopkgtest
Bug reassigned from package 'src:opencv, src:auto-multiple-choice' to
'src:opencv'.
No longer marked as found in versions auto-multiple-choice/1
control: reassign -1 src:opencv
On Sun, 31 Oct 2021 22:04:15 +0100 Paul Gevers
wrote:
> I think that means you must bump the SONAME (if not done upstream,
with
> a Debian specific version), go through NEW, ask for a transition
block
> with the release team and have all reverse dependencies rebuil
Your message dated Wed, 10 Nov 2021 11:20:35 +
with message-id
and subject line Bug#997783: fixed in silkaj 0.9.0-2
has caused the Debian Bug report #997783,
regarding silkaj: FTBFS: test -s debian/bash-completion => fails
to be marked as done.
This means that you claim that the problem has b
Processing commands for cont...@bugs.debian.org:
> reopen 998886
Bug #998886 {Done: Yadd } [node-string-width,node-slice-ansi]
node-string-width,node-slice-ansi: both ship
/usr/share/nodejs/is-fullwidth-code-point/*
Bug #998911 {Done: Yadd } [node-string-width,node-slice-ansi]
node-string-width
Your message dated Wed, 10 Nov 2021 10:20:48 +
with message-id
and subject line Bug#997481: fixed in textdistance 4.2.2-1
has caused the Debian Bug report #997481,
regarding textdistance: FTBFS: dh_auto_test: error: pybuild --test
--test-pytest -i python{version} -p 3.9 returned exit code 13
Your message dated Wed, 10 Nov 2021 09:50:10 +
with message-id
and subject line Bug#997335: fixed in python-fakeredis 1.6.1-1
has caused the Debian Bug report #997335,
regarding python-fakeredis: FTBFS: unsatisfiable build-dependency:
python3-pytest-cov (< 3.0) but 3.0.0-1 is to be installed
Control: tag -1 pending
Hello,
Bug #997335 in python-fakeredis 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/python-team/packages/python-fakeredis/-/commit/5a
Processing control commands:
> tag -1 pending
Bug #997335 [src:python-fakeredis] python-fakeredis: FTBFS: unsatisfiable
build-dependency: python3-pytest-cov (< 3.0) but 3.0.0-1 is to be installed
Added tag(s) pending.
--
997335: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997335
Debian Bu
Source: gtk-d
Version: 3.9.0-4
Severity: serious
Tags: ftbfs sid bookworm
Justification: fails to build from source (but built successfully in the past)
| ldc2 -O -g -release -wi -Igenerated/gtkd -Idemos/gtkD/TestWindow -c
demos/gtkD/TestWindow/TestText.d -ofdemos/gtkD/TestWindow/TestText.o
| dem
On 9.11.2021 10.53, Ondřej Surý wrote:
Hi Timo,
On 5. 11. 2021, at 8:09, Timo Aaltonen wrote:
On 5.11.2021 1.37, peter green wrote:
bind9-dev : Depends: bind9-libs (= 1:9.16.21-1) but it is not going to be
installed
It looks like bind8 no longer builds the bind9-dev package. It's still p
Control: forcemerge 998633 -1
Control: tags = 998633 ftbfs bookworm pending sid
On 2021-11-10 07:58:54 +0100, Helmut Grohne wrote:
> Source: shadow
> Version: 1:4.8.1-1.1
> Severity: serious
> Tags: ftbfs patch
> User: helm...@debian.org
> Usertags: rebootstrap
>
> shadow fails to build from sour
Processing control commands:
> forcemerge 998633 -1
Bug #998633 [src:shadow] shadow: Please switch libsemanage1-dev BD to
libsemanage-dev
Bug #998633 [src:shadow] shadow: Please switch libsemanage1-dev BD to
libsemanage-dev
Added tag(s) ftbfs and patch.
Bug #999342 [src:shadow] shadow FTBFS: bd-
91 matches
Mail list logo
