Processing control commands:
> severity -1 grave
Bug #1010269 [wine-development] crashes immediately at start
Severity set to 'grave' from 'normal'
> affects -1 src:dxvk
Bug #1010269 [wine-development] crashes immediately at start
Added indication that 1010269 affects src:dxvk
--
1010269: https:
Your message dated Mon, 02 May 2022 06:03:49 +
with message-id
and subject line Bug#1010429: fixed in gddrescue 1.26-2
has caused the Debian Bug report #1010429,
regarding gddrescue: autopkgtest regression
to be marked as done.
This means that you claim that the problem has been dealt with.
I
* Paul Gevers [Sun May 01, 2022 at 02:39:15PM +0200]:
> With a recent upload of gddrescue the autopkgtest of gddrescue fails in
> testing when that autopkgtest is run with the binary packages of gddrescue
> from unstable. It passes when run with only packages from testing. In
> tabular form:
[...]
Hi,
On 24-04-2022 12:00, Paul Gevers wrote:
On Sat, 29 Jan 2022 19:32:53 +0100 Paul Gevers wrote:
With a recent upload of luajit the autopkgtest of knot-resolver fails
in testing when that autopkgtest is run with the binary packages of
luajit from unstable. It passes when run with only packag
Processing control commands:
> severity -1 serious
Bug #1009079 [src:mdtraj] mdtraj: autopkgtest timeout on arm64 (downloading pdb
file?)
Severity set to 'serious' from 'important'
> user debian...@lists.debian.org
Unknown command or malformed arguments to command.
> usertag -1 flaky needs-inter
Your message dated Mon, 02 May 2022 05:04:39 +
with message-id
and subject line Bug#997742: fixed in pyrlp 0.5.1-3
has caused the Debian Bug report #997742,
regarding pyrlp: FTBFS: There is a syntax error in your configuration file:
Missing parentheses in call to 'print'. Did you mean print(s
Hi,
On 02-05-2022 02:39, Debian Bug Tracking System wrote:
macaulay2 (1.19.1+ds-9) unstable; urgency=medium
.
* debian/tests/control
- Mark package-tests as flaky since it regularly times out on armhf
(Closes: #1010453).
Hmmm. May I recommend something else?
Marking auto
Your message dated Mon, 02 May 2022 00:34:22 +
with message-id
and subject line Bug#1010453: fixed in macaulay2 1.19.1+ds-9
has caused the Debian Bug report #1010453,
regarding macaulay2: autopkgtest regularly times out on armhf
to be marked as done.
This means that you claim that the problem
Your message dated Sun, 01 May 2022 23:06:01 +
with message-id
and subject line Bug#984083: fixed in lasi 1.1.0-3
has caused the Debian Bug report #984083,
regarding lasi: ftbfs with GCC-11
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not th
Your message dated Sun, 01 May 2022 21:33:23 +
with message-id
and subject line Bug#1000271: fixed in jupyter-client 7.3.0-1
has caused the Debian Bug report #1000271,
regarding jupyter-client breaks dask.distributed autopkgtest: ERROR - Workers
don't have promised key: ['tcp://127.0.0.1:3393
Processing commands for cont...@bugs.debian.org:
> affects 984865 src:rust-kmon
Bug #984865 [src:rust-tui] rust-tui: depends on multiple unavailable packages
Ignoring request to set affects of bug 984865 to the same value previously set
> thanks
Stopping processing here.
Please contact me if you
Processing commands for cont...@bugs.debian.org:
> tags 984865 + ftbfs
Bug #984865 [src:rust-tui] rust-tui: depends on multiple unavailable packages
Ignoring request to alter tags of bug #984865 to the same tags previously set
> thanks
Stopping processing here.
Please contact me if you need assis
Processing commands for cont...@bugs.debian.org:
> affects 984865 src:rust-kmon
Bug #984865 [src:rust-tui] rust-tui: depends on multiple unavailable packages
Added indication that 984865 affects src:rust-kmon
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
984865:
Processing commands for cont...@bugs.debian.org:
> tags 984865 + ftbfs
Bug #984865 [src:rust-tui] rust-tui: depends on multiple unavailable packages
Added tag(s) ftbfs.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
984865: https://bugs.debian.org/cgi-bin/bugrepo
Processing control commands:
> tag -1 pending
Bug #1000271 [src:jupyter-client, src:dask.distributed] jupyter-client breaks
dask.distributed autopkgtest: ERROR - Workers don't have promised key:
['tcp://127.0.0.1:33937']
Added tag(s) pending.
--
1000271: https://bugs.debian.org/cgi-bin/bugrepo
Control: tag -1 pending
Hello,
Bug #1000271 in jupyter-client 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/jupyter-client/-/commit/9b99a
Source: docker.io
Version: 20.10.14+dfsg1-1
Severity: serious
Tags: ftbfs sid bookworm
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: sramac...@debian.org
https://buildd.debian.org/status/fetch.php?pkg=docker.io&arch=s390x&ver=20.10.14%2Bdfsg1-1%2Bb1&s
Source: macaulay2
Version: 1.19.1+ds-4
Severity: serious
User: debian...@lists.debian.org
Usertags: flaky timeout
Dear maintainer(s),
I looked at the results of the autopkgtest of you package because it was
showing up as a regression for the upload of gcc-12. I noticed that the
test regularly
Processing commands for cont...@bugs.debian.org:
> severity 1005382 serious
Bug #1005382 [gitlab-ci-multi-runner] "couldn't load configuration template
file: Near line 1 (last key parsed '-'): expected key separator '=', but got
',' instead"
Severity set to 'serious' from 'important'
> thanks
St
Processing commands for cont...@bugs.debian.org:
> tags 1005382 + ftbfs
Bug #1005382 [gitlab-ci-multi-runner] "couldn't load configuration template
file: Near line 1 (last key parsed '-'): expected key separator '=', but got
',' instead"
Added tag(s) ftbfs.
> thanks
Stopping processing here.
Pl
Source: gitlab-ci-multi-runner
Version: 13.3.1+dfsg-4
Severity: serious
Tags: ftbfs sid bookworm
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: sramac...@debian.org
gitlab-ci-multi-runner FTBFS:
=== RUN TestRmFile/pwsh
integration_tests.go:15: p
Source: gdb-avr
Version: 7.7-5
Severity: serious
Tags: ftbfs
https://buildd.debian.org/status/logs.php?pkg=gdb-avr&ver=7.7-5%2Bb1
...
checking for libgmp... no
configure: error: GMP is missing or unusable
make[1]: *** [Makefile:9783: configure-gdb] Error 1
make[1]: Leaving directory '/<>/build'
m
Your message dated Sun, 01 May 2022 19:57:33 +
with message-id
and subject line Bug#1004847: fixed in nvidia-graphics-drivers
470.103.01-3~deb11u1
has caused the Debian Bug report #1004847,
regarding nvidia-graphics-drivers: CVE-2022-21813, CVE-2022-21814
to be marked as done.
This means tha
Am Sun, May 01, 2022 at 01:27:39PM +0200 schrieb Étienne Mollier:
> Thank you for the clarification. In any case, I believe the mv
> makes a random static library disappear, so I'll replace by cp.
> This is looking like a safe maneuver.
Uh, that's actually true and should for sure have been a
Your message dated Sun, 1 May 2022 21:40:57 +0200
with message-id
and subject line Closing transient build errors
has caused the Debian Bug report #1008375,
regarding apertium-crh-tur: FTBFS: configure: error: You don't have lrx-comp
installed
to be marked as done.
This means that you claim tha
Your message dated Sun, 1 May 2022 21:40:57 +0200
with message-id
and subject line Closing transient build errors
has caused the Debian Bug report #1008364,
regarding apertium-urd-hin: FTBFS: configure: error: You don't have lrx-comp
installed.
to be marked as done.
This means that you claim th
Your message dated Sun, 1 May 2022 21:40:57 +0200
with message-id
and subject line Closing transient build errors
has caused the Debian Bug report #1008330,
regarding apertium-spa: FTBFS: configure: error: You don't have lrx-comp
installed
to be marked as done.
This means that you claim that th
Your message dated Sun, 01 May 2022 19:34:03 +
with message-id
and subject line Bug#1010164: fixed in bart 0.7.00-3
has caused the Debian Bug report #1010164,
regarding fails autopkgtest against Octave 7
to be marked as done.
This means that you claim that the problem has been dealt with.
If
Your message dated Sun, 1 May 2022 21:31:31 +0200
with message-id
and subject line Closing transient build errors
has caused the Debian Bug report #1008378,
regarding apertium-spa-cat: FTBFS: configure: error: Package requirements
(apertium-lex-tools >= 0.2.2) were not met
to be marked as done.
Your message dated Sun, 1 May 2022 21:31:31 +0200
with message-id
and subject line Closing transient build errors
has caused the Debian Bug report #1008331,
regarding apertium-fra-frp: FTBFS: configure: error: Package requirements
(apertium-lex-tools >= 0.2.6) were not met
to be marked as done.
Your message dated Sun, 1 May 2022 21:16:16 +0200
with message-id
and subject line Closing transient build errors
has caused the Debian Bug report #1008390,
regarding apertium-nno-nob: FTBFS: configure: error: Package requirements
(apertium-lex-tools >= 0.2.2) were not met
to be marked as done.
Your message dated Sun, 1 May 2022 21:16:16 +0200
with message-id
and subject line Closing transient build errors
has caused the Debian Bug report #1008389,
regarding apertium-spa-ita: FTBFS: configure: error: Package requirements
(apertium-lex-tools >= 0.2.7) were not met
to be marked as done.
Your message dated Sun, 1 May 2022 21:16:16 +0200
with message-id
and subject line Closing transient build errors
has caused the Debian Bug report #1008388,
regarding apertium-swe-nor: FTBFS: configure: error: Package requirements
(apertium-lex-tools >= 0.2.2) were not met
to be marked as done.
Your message dated Sun, 1 May 2022 21:16:16 +0200
with message-id
and subject line Closing transient build errors
has caused the Debian Bug report #1008373,
regarding apertium-hbs-eng: FTBFS: configure: error: Package requirements
(apertium-lex-tools >= 0.2.6) were not met
to be marked as done.
Your message dated Sun, 1 May 2022 21:16:16 +0200
with message-id
and subject line Closing transient build errors
has caused the Debian Bug report #1008363,
regarding apertium-por-cat: FTBFS: configure: error: Package requirements
(apertium-lex-tools >= 0.2.3) were not met
to be marked as done.
Your message dated Sun, 1 May 2022 21:16:16 +0200
with message-id
and subject line Closing transient build errors
has caused the Debian Bug report #1008371,
regarding apertium-pol-szl: FTBFS: configure: error: Package requirements
(apertium-lex-tools >= 0.2.2) were not met
to be marked as done.
Your message dated Sun, 1 May 2022 21:16:16 +0200
with message-id
and subject line Closing transient build errors
has caused the Debian Bug report #1008370,
regarding apertium-bel-rus: FTBFS: configure: error: Package requirements
(apertium-lex-tools >= 0.2.3) were not met
to be marked as done.
Your message dated Sun, 1 May 2022 21:16:16 +0200
with message-id
and subject line Closing transient build errors
has caused the Debian Bug report #1008367,
regarding apertium-swe-dan: FTBFS: configure: error: Package requirements
(apertium-lex-tools >= 0.2.2) were not met
to be marked as done.
Your message dated Sun, 1 May 2022 21:16:16 +0200
with message-id
and subject line Closing transient build errors
has caused the Debian Bug report #1008365,
regarding apertium-arg-cat: FTBFS: configure: error: Package requirements
(apertium-lex-tools >= 0.2.7) were not met
to be marked as done.
Your message dated Sun, 1 May 2022 21:16:16 +0200
with message-id
and subject line Closing transient build errors
has caused the Debian Bug report #1008362,
regarding apertium-dan-nor: FTBFS: configure: error: Package requirements
(apertium-lex-tools >= 0.2.2) were not met
to be marked as done.
Your message dated Sun, 1 May 2022 21:16:16 +0200
with message-id
and subject line Closing transient build errors
has caused the Debian Bug report #1008359,
regarding apertium-fra-cat: FTBFS: configure: error: Package requirements
(apertium-lex-tools >= 0.2.3) were not met
to be marked as done.
Your message dated Sun, 1 May 2022 21:16:16 +0200
with message-id
and subject line Closing transient build errors
has caused the Debian Bug report #1008353,
regarding apertium-cat-ita: FTBFS: configure: error: Package requirements
(apertium-lex-tools >= 0.2.2) were not met
to be marked as done.
Your message dated Sun, 1 May 2022 21:16:16 +0200
with message-id
and subject line Closing transient build errors
has caused the Debian Bug report #1008335,
regarding apertium-hbs-slv: FTBFS: configure: error: Package requirements
(apertium-lex-tools >= 0.2.6) were not met
to be marked as done.
Your message dated Sun, 1 May 2022 21:16:16 +0200
with message-id
and subject line Closing transient build errors
has caused the Debian Bug report #1008347,
regarding apertium-es-gl: FTBFS: configure: error: Package requirements
(apertium-lex-tools >= 0.2.7) were not met
to be marked as done.
T
Your message dated Sun, 1 May 2022 21:16:16 +0200
with message-id
and subject line Closing transient build errors
has caused the Debian Bug report #1008339,
regarding apertium-eng-cat: FTBFS: configure: error: Package requirements
(apertium-lex-tools >= 0.2.2) were not met
to be marked as done.
Your message dated Sun, 1 May 2022 21:16:16 +0200
with message-id
and subject line Closing transient build errors
has caused the Debian Bug report #1008341,
regarding apertium-srd-ita: FTBFS: configure: error: Package requirements
(apertium-lex-tools >= 0.2.7) were not met
to be marked as done.
Your message dated Sun, 1 May 2022 21:16:16 +0200
with message-id
and subject line Closing transient build errors
has caused the Debian Bug report #1008346,
regarding apertium-rus-ukr: FTBFS: configure: error: Package requirements
(apertium-lex-tools >= 0.2.6) were not met
to be marked as done.
Your message dated Sun, 1 May 2022 21:16:16 +0200
with message-id
and subject line Closing transient build errors
has caused the Debian Bug report #1008334,
regarding apertium-oci-fra: FTBFS: configure: error: Package requirements
(apertium-lex-tools >= 0.2.2) were not met
to be marked as done.
Your message dated Sun, 1 May 2022 21:16:16 +0200
with message-id
and subject line Closing transient build errors
has caused the Debian Bug report #1008333,
regarding apertium-afr-nld: FTBFS: configure: error: Package requirements
(apertium-lex-tools >= 0.2.2) were not met
to be marked as done.
Your message dated Sun, 1 May 2022 21:16:16 +0200
with message-id
and subject line Closing transient build errors
has caused the Debian Bug report #1008332,
regarding apertium-cat-srd: FTBFS: configure: error: Package requirements
(apertium-lex-tools >= 0.2.7) were not met
to be marked as done.
Your message dated Sun, 1 May 2022 21:16:16 +0200
with message-id
and subject line Closing transient build errors
has caused the Debian Bug report #1008329,
regarding apertium-spa-arg: FTBFS: configure: error: Package requirements
(apertium-lex-tools >= 0.2.7) were not met
to be marked as done.
Your message dated Sun, 01 May 2022 19:04:18 +
with message-id
and subject line Bug#1010287: fixed in perl-openssl-defaults 6
has caused the Debian Bug report #1010287,
regarding perl-openssl-defaults: generated substvar should not end in a newline
to be marked as done.
This means that you cl
Processing control commands:
> fixed -1 nodejs/16.14.2+dfsg-1
Bug #1010446 [nodejs] nodejs 14.19 hangs on mipsel/mips64el when building
qtwebengine frontend with rollup and terser plugin
Marked as fixed in versions nodejs/16.14.2+dfsg-1.
--
1010446: https://bugs.debian.org/cgi-bin/bugreport.cgi
Package: nodejs
Version: 16.13.2+really14.19.1~dfsg-6
Severity: serious
Control: fixed -1 nodejs/16.14.2+dfsg-1
Affects: src:qtwebengine-opensource-src
Dear nodejs maintainers,
Currently qtwebengine-opensource-src FTBFS on mipsel and mips64el:
https://buildd.debian.org/status/logs.php?pkg=qtweben
Your message dated Sun, 01 May 2022 18:18:59 +
with message-id
and subject line Bug#1009041: fixed in guile-git 0.5.2-4
has caused the Debian Bug report #1009041,
regarding guile-git: FTBFS with libgit2 1.3.0
to be marked as done.
This means that you claim that the problem has been dealt with
Processing control commands:
> reassign -1 src:yade
Bug #1009739 [src:python3.10, src:yade] python3.10 breaks yade autopkgtest on
i386: Segmentation fault
Bug reassigned from package 'src:python3.10, src:yade' to 'src:yade'.
No longer marked as found in versions yade/2022.01a-7 and python3.10/3.1
Control: reassign -1 src:yade
yade was removed from testing, and also is not installable on i386. Reassigning
until we can investigate if that's a Python issue.
Your message dated Sun, 01 May 2022 18:00:11 +
with message-id
and subject line Bug#984203: fixed in libpgf 7.21.7+ds-1
has caused the Debian Bug report #984203,
regarding libpgf: ftbfs with GCC-11
to be marked as done.
This means that you claim that the problem has been dealt with.
If this i
Processing control commands:
> forwarded 1009041 https://gitlab.com/guile-git/guile-git/-/issues/23
Bug #1009041 [guile-git] guile-git: FTBFS with libgit2 1.3.0
Set Bug forwarded-to-address to
'https://gitlab.com/guile-git/guile-git/-/issues/23'.
--
1009041: https://bugs.debian.org/cgi-bin/bugr
Control: forwarded 1009041 https://gitlab.com/guile-git/guile-git/-/issues/23
On 2022-04-06, Mohammed Bilal wrote:
> guile-git was found to fail to build during a test rebuild with
> libgit2 1.3.0 in unstable. Attaching the build logs as well.
>
> Relevant part(hopefully) :
>
> FAIL: tests/proxy
>
On 01/05/2022 14:00, Fabian Grünbichler wrote:
currently progress is blocked on
- itoa/serde_json transition (anybody working actively on that?)
I just uploaded the new itoa to experimental and took a quick look
through the reverse dependencies.
rust-cssparser - already broken and not in t
[ Paul Gevers, 2022-05-01 ]
> It seems that with the fix for bug #1010102 you either picked the
> wrong Depends of two, or you forgot to update the postinst for the
> change as update-mime lives in mailcap.
AFAICT calling update-mime in d-e-c.postinst is unneeded since the
obsolete debian-edu-m
Processing commands for cont...@bugs.debian.org:
> fixed 999066 0.1.2.0-5
Bug #999066 [src:tmexpand] tmexpand: missing required debian/rules targets
build-arch and/or build-indep
The source 'tmexpand' and version '0.1.2.0-5' do not appear to match any binary
packages
Marked as fixed in versions
On Mon, 25 Apr 2022 17:23:25 +0200 =?utf-8?q?S=C3=A9bastien_Villemot?=
wrote:
> Package: octave-bart
> Version: 0.7.00-2
> Severity: serious
> Tags: patch
> Control: block 1009865 by -1
>
> Dear Maintainer,
>
> The autopkgtest for octave-bart fails against octave 7.1.0-2 recently uploaded
> to
Your message dated Sun, 01 May 2022 15:20:08 +
with message-id
and subject line Bug#1010428: fixed in twine 4.0.0-3
has caused the Debian Bug report #1010428,
regarding twine: autopkgtest needs update for new version of
python-readme-renderer: error message changed
to be marked as done.
This
Processing control commands:
> tag -1 pending
Bug #1010428 [src:twine] twine: autopkgtest needs update for new version of
python-readme-renderer: error message changed
Added tag(s) pending.
--
1010428: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1010428
Debian Bug Tracking System
Contact
Control: tag -1 pending
Hello,
Bug #1010428 in twine 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/twine/-/commit/8e043effc84790c579657a3
Le 01/05/2022 à 15:29, Christoph Biedl a écrit :
Control: tag 1003463 confirmed
Roman Lebedev wrote...
Package: arcanist
Version: 0~git20200925-2
Severity: grave
@Sylvestre,
as previously mentioned in IRC (possibly got lost), I am considering
rebasing the src:phabricator package to the lat
Processing commands for cont...@bugs.debian.org:
> severity 1009041 serious
Bug #1009041 [guile-git] guile-git: FTBFS with libgit2 1.3.0
Severity set to 'serious' from 'important'
> severity 1009029 serious
Bug #1009029 [julia] julia: FTBFS with libgit2 1.3.0
Severity set to 'serious' from 'import
Processing commands for cont...@bugs.debian.org:
> severity 1009017 serious
Bug #1009017 [src:criterion] criterion: FTBFS with libgit2 1.3.0
Severity set to 'serious' from 'important'
>
End of message, stopping processing here.
Please contact me if you need assistance.
--
1009017: https://bugs.d
Your message dated Sun, 01 May 2022 13:48:46 +
with message-id
and subject line Bug#999050: fixed in cldump 0.11~dfsg-5
has caused the Debian Bug report #999050,
regarding cldump: missing required debian/rules targets build-arch and/or
build-indep
to be marked as done.
This means that you cl
Control: tag 1003463 confirmed
Roman Lebedev wrote...
> Package: arcanist
> Version: 0~git20200925-2
> Severity: grave
@Sylvestre,
as previously mentioned in IRC (possibly got lost), I am considering
rebasing the src:phabricator package to the latest git commit in the
respective upstream reposi
Processing control commands:
> tag 1003463 confirmed
Bug #1003463 [arcanist] Functionally broken with current PHP
Added tag(s) confirmed.
--
1003463: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1003463
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Am Sun, May 01, 2022 at 02:09:21PM +0200 schrieb Étienne Mollier:
> > Note that `sort` is locale dependant, so if that's really the proper way
> > to do it (tbh doing find|head feels *very* brittle to me… it's probably
> > better if you can think of a better way to achieve whatever that piece
> > o
On April 20, 2022 11:39 am, Fabian Grünbichler wrote:
> On April 20, 2022 12:33 am, Peter Michael Green wrote:
>> Package: rust-h2
>> Version: 0.1.26-1
>> X-debbugs-cc: d...@jones.dk
>>
>> I noticed that Jonas had set a number of bugs about broken rust packages as
>> blockers of 900928, so I decid
Source: debian-edu-config
Version: 2.12.21
Severity: serious
User: debian...@lists.debian.org
Usertags: regression
Dear maintainer(s),
With a recent upload of debian-edu-config the autopkgtest of
debian-edu-config fails in testing when that autopkgtest is run with the
binary packages of debian
Source: ensmallen
Version: 2.19.0-1
Severity: serious
User: debian...@lists.debian.org
Usertags: regression
Dear maintainer(s),
With a recent upload of ensmallen the autopkgtest of ensmallen fails in
testing on i386 when that autopkgtest is run with the binary packages of
ensmallen from unstab
Processing control commands:
> found -1 tifffile/20220426-1
Bug #1010430 [src:tifffile, src:skimage] tifffile breaks skimage autopkgtest:
asarray() got an unexpected keyword argument 'multifile'
Marked as found in versions tifffile/20220426-1.
> found -1 skimage/0.18.3-2
Bug #1010430 [src:tifffil
Source: tifffile, skimage
Control: found -1 tifffile/20220426-1
Control: found -1 skimage/0.18.3-2
Severity: serious
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: breaks needs-update
Dear maintainer(s),
With a recent upload of tifffile the autopkgtest of skimage fails in
testing
Dear developers,
I have the same issue in my machine (Debian Bullseye Stable with Gnome
3.38): Evolution doesn't start at all.
But I could add that this issue affects also Gnome Online Accounts. To
have it working we have to launch
WEBKIT_FORCE_SANDBOX=0 gnome-control-center online-accounts
Source: gddrescue
Version: 1.26-1
Severity: serious
User: debian...@lists.debian.org
Usertags: regression
Dear maintainer(s),
With a recent upload of gddrescue the autopkgtest of gddrescue fails in
testing when that autopkgtest is run with the binary packages of
gddrescue from unstable. It pas
Source: twine
Version: 4.0.0-2
Severity: serious
X-Debbugs-CC: python-readme-rende...@packages.debian.org
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: needs-update
Control: affects -1 src:python-readme-renderer
Dear maintainer(s),
With a recent upload of python-readme-renderer t
Processing control commands:
> affects -1 src:python-readme-renderer
Bug #1010428 [src:twine] twine: autopkgtest needs update for new version of
python-readme-renderer: error message changed
Added indication that 1010428 affects src:python-readme-renderer
--
1010428: https://bugs.debian.org/cgi
Your message dated Sun, 01 May 2022 12:34:17 +
with message-id
and subject line Bug#1010276: fixed in parasail 2.5+dfsg-4
has caused the Debian Bug report #1010276,
regarding parasail: compiles something extra (or less) depending on the CPU
features available
to be marked as done.
This means
Processing control commands:
> reassign -1 perl-openssl-defaults 5
Bug #1010287 [src:libnet-ssleay-perl] libnet-ssleay-perl: FTBFS: bad line in
substvars file debian/libnet-ssleay-perl.substvars at line 2
Bug reassigned from package 'src:libnet-ssleay-perl' to 'perl-openssl-defaults'.
No longer m
Control: reassign -1 perl-openssl-defaults 5
Control: tag -1 sid bookworm
Control: retitle -1 perl-openssl-defaults: generated substvar should not end in
a newline
Control: affects -1 src:libnet-ssleay-perl
On Wed, Apr 27, 2022 at 03:28:06PM -0700, Daniel Schepler wrote:
> Source: libnet-ssleay-p
On Sun, May 01, 2022 at 10:50:16AM +0200, Étienne Mollier wrote:
> Upstream implements run time
> CPU detection to avoid baseline violation on older CPU.
Great! Thank you for confirming this bit. I figured it might be the
case, but I didn't verify it myself (as I noted in my first email).
> So
Your message dated Sun, 01 May 2022 10:51:21 +
with message-id
and subject line Bug#1009460: fixed in python-marathon 0.13.0-4
has caused the Debian Bug report #1009460,
regarding python-marathon: FTBFS: FAILED
tests/test_model_event.py::MarathonEventTest::test_marathon_event - At...
to be ma
Processing control commands:
> tag -1 pending
Bug #1009460 [src:python-marathon] python-marathon: FTBFS: FAILED
tests/test_model_event.py::MarathonEventTest::test_marathon_event - At...
Added tag(s) pending.
--
1009460: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009460
Debian Bug Tracki
Control: tag -1 pending
Hello,
Bug #1009460 in python-marathon 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/openstack-team/libs/python-marathon/-/commit/e9ed
Source: gir-to-d
Version: 0.22.0-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: sramac...@debian.org
gir-to-d FTBFS with ldc 1.29:
FAILED: girtod
ldc2 -of=girtod girtod.p/source_girtod.d.o girtod.p/source_gtd_DefReade
Processing commands for cont...@bugs.debian.org:
> close 984913 0.3.51-1
Bug #984913 {Done: Peter Michael Green }
[src:rust-backtrace] librust-backtrace+rustc-dep-of-std-dev: depends on
unavailable librust-cfg-if-0.1+rustc-dep-of-std-dev
Marked as fixed in versions rust-backtrace/0.3.51-1.
Bug #
Hi Étienne,
Am Sun, May 01, 2022 at 10:50:16AM +0200 schrieb Étienne Mollier:
> I'm still looking up this issue, but I wrap up a status to clear
> my mind.
>
> To me, the main topic of the bug is the reproducibility issue[1]
> observed on i386, but other architectures may be affected. The
> diff
Your message dated Sun, 01 May 2022 07:18:54 +
with message-id
and subject line Bug#1005978: fixed in vdk2 2.4.0-5.6
has caused the Debian Bug report #1005978,
regarding Please migrate away from dpatch
to be marked as done.
This means that you claim that the problem has been dealt with.
If th
94 matches
Mail list logo
