Hi again, Paul.
On 3/10/22 6:28 PM, Nilesh Patra wrote:
On Thu, Mar 10, 2022 at 01:09:41PM +0100, Paul Gevers wrote:
I was finally able to make time and do this. I first ran
admin@ci-worker08:/tmp/toil$ apt source toil/unstable
admin@ci-worker08:/tmp/toil/toil-5.6.0$ autopkgtest --shell
control: reassign -1 toil
control: found -1 5.6.0-2
control: fixed -1 5.6.0-4
control: close -1
On Sat, 29 Jan 2022 19:41:25 +0100 Paul Gevers wrote:
> [0] You can see what packages were added from the second line of the log
> file quoted below. The migration software adds source package from
>
Processing control commands:
> reassign -1 toil
Bug #1004516 [src:cwltool, src:toil] cwltool breaks toil autopkgtest: No such
file or directory: '/home/debci/tmp/tmpgxz5j85g'
Bug reassigned from package 'src:cwltool, src:toil' to 'toil'.
No longer marked as found in versions toil/5.6.0-2 and
On Thu, 10 Mar 2022 18:19:09 + Debian FTP Masters wrote:
> Changes:
> libwebp (1.2.2-1) unstable; urgency=medium
> .
> * New upstream release.
> * Fixes test failure on mipsel architecture (closes: #1006110)
> * Fixes test failure on mipsel architecture (closes: #1006009)
> Checksums-Sha1:
>
Processing control commands:
> severity -1 serious
Bug #994619 [xpra] xpra: recommends gir1.2-appindicator3-0.1 which is no longer
available
Severity set to 'serious' from 'normal'
> found -1 3.1-1
Bug #994619 [xpra] xpra: recommends gir1.2-appindicator3-0.1 which is no longer
available
Marked
Processing control commands:
> tag -1 + moreinfo
Bug #1006953 [fonts-creep2] fonts-creep2: Font does not install correctly, so
does not show up in GUI font lists
Added tag(s) moreinfo.
--
1006953: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006953
Debian Bug Tracking System
Contact
Control: tag -1 + moreinfo
Hi David,
it does not show up in e.g. the font list in AbiWord,
or the font list in Konsole, etc., despite being a TrueType font supposedly.
As you may have figured out, "creep2" is a "special" font because it is
shipped as a TrueType font but it contains a bitmap
I just tested `playitslowly` on a Debian 11/Bullseye box & it works for me.
It worked for me in (Debian) `testing` ~until I filed the Ubuntu bug
report (or a few days before hand; Nov-2021)
Yes loads of messages appear if you run it at terminal; but it starts
and runs on Debian Bullseye, Ubuntu
Your message dated Thu, 10 Mar 2022 23:19:37 +
with message-id
and subject line Bug#999120: fixed in hpsockd 0.17+nmu1
has caused the Debian Bug report #999120,
regarding hpsockd: missing required debian/rules targets build-arch and/or
build-indep
to be marked as done.
This means that you
Your message dated Thu, 10 Mar 2022 23:19:37 +
with message-id
and subject line Bug#965582: fixed in hpsockd 0.17+nmu1
has caused the Debian Bug report #965582,
regarding hpsockd: Removal of obsolete debhelper compat 5 and 6 in bookworm
to be marked as done.
This means that you claim that
Processing commands for cont...@bugs.debian.org:
> limit source hpsockd
Limiting to bugs with field 'source' containing at least one of 'hpsockd'
Limit currently set to 'source':'hpsockd'
> tags 1007074 + pending
Bug #1007074 [src:hpsockd] hpsockd: please consider upgrading to 3.0 source
format
Package: rust-weedle
Version: 0.12.0-1
Severity: serious
x-debbugs-cc: g...@rxv.cc, james...@debian.org
James McCoy and I are currently working on updating the rust-nom package
in Debian from version 5 to version 7. Debian also has version 4 of
nom packaged as a separate source package.
The
Hi Michael,
On Fri, 28 Jan 2022 01:17:08 +0200 Adrian Bunk wrote:
> This is due to:
>
> (sid_armhf-dchroot)bunk@amdahl:~$ python3
> Python 3.9.10 (main, Jan 16 2022, 17:12:18)
> [GCC 11.2.0] on linux
> Type "help", "copyright", "credits" or "license" for more information.
> >>> import mappy
>
Package: evdi-dkms
Version: 1.9.0+dfsg-1
Followup-For: Bug #994892
Dear Maintainer,
There's a newer version out these days which installs fine on Sid, perhaps
the package could be updated to fix the build issues?
Kind regards,
Jan
-- System Information:
Debian Release: bookworm/sid
APT
Your message dated Thu, 10 Mar 2022 18:30:47 +
with message-id
and subject line Bug#1006983: Removed package(s) from unstable
has caused the Debian Bug report #999085,
regarding gtk-nodoka-engine: missing required debian/rules targets build-arch
and/or build-indep
to be marked as done.
This
Your message dated Thu, 10 Mar 2022 18:30:47 +
with message-id
and subject line Bug#1006983: Removed package(s) from unstable
has caused the Debian Bug report #965573,
regarding gtk-nodoka-engine: Removal of obsolete debhelper compat 5 and 6 in
bookworm
to be marked as done.
This means that
Your message dated Thu, 10 Mar 2022 18:26:22 +
with message-id
and subject line Bug#1000550: Removed package(s) from unstable
has caused the Debian Bug report #975535,
regarding elpy's autopkg tests fail with Python 3.9
to be marked as done.
This means that you claim that the problem has
Your message dated Thu, 10 Mar 2022 18:25:49 +
with message-id
and subject line Bug#1006761: Removed package(s) from unstable
has caused the Debian Bug report #1006017,
regarding playitslowly doesn't start (hasn't for awhile)
to be marked as done.
This means that you claim that the problem
Your message dated Thu, 10 Mar 2022 18:18:55 +
with message-id
and subject line Bug#1006139: fixed in libdeflate 1.10-2
has caused the Debian Bug report #1006139,
regarding libdeflate FTBFS on armhf
to be marked as done.
This means that you claim that the problem has been dealt with.
If this
Your message dated Thu, 10 Mar 2022 18:19:09 +
with message-id
and subject line Bug#1006110: fixed in libwebp 1.2.2-1
has caused the Debian Bug report #1006110,
regarding graphicsmagick: FTBFS on mipsel: test failure
to be marked as done.
This means that you claim that the problem has been
Your message dated Thu, 10 Mar 2022 18:19:09 +
with message-id
and subject line Bug#1006009: fixed in libwebp 1.2.2-1
has caused the Debian Bug report #1006009,
regarding qtimageformats-opensource-src: FTBFS on mipsel: test failure
to be marked as done.
This means that you claim that the
Processing commands for cont...@bugs.debian.org:
> #
> # bts-link upstream status pull for source package myhdl
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> # https://bts-link-team.pages.debian.net/bts-link/
> #
> user debian-bts-l...@lists.debian.org
Setting
control: fixed -1 5.3.5+dfsg-4
control: close -1
On Thu, 24 Feb 2022 16:09:55 +0100 Paul Gevers wrote:
> Currently this regression is blocking the migration to testing [1]. Can
> you please investigate the situation and fix it?
This has been fixed with my latest upload, everything is green now.
Processing control commands:
> fixed -1 5.3.5+dfsg-4
Bug #1006376 [src:blasr] blasr: autopkgtest regression: Segmentation fault
Marked as fixed in versions blasr/5.3.5+dfsg-4.
> close -1
Bug #1006376 [src:blasr] blasr: autopkgtest regression: Segmentation fault
Marked Bug as done
--
1006376:
Processing commands for cont...@bugs.debian.org:
> severity 995735 normal
Bug #995735 [src:dask.distributed] dask.distributed: autopkgtest sometimes
times out on ci.d.n worker since dask migrated
Severity set to 'normal' from 'serious'
> thanks
Stopping processing here.
Please contact me if you
Your message dated Thu, 10 Mar 2022 14:34:50 +
with message-id
and subject line Bug#888995: fixed in dbus-cpp 5.0.3-3
has caused the Debian Bug report #888995,
regarding dbus-cpp: async_execution_load_test fails sometimes (randomly?)
to be marked as done.
This means that you claim that the
Processing control commands:
> found -1 wine/6.0.2~repack-3
Bug #1007014 [src:wine] wine breaks multiple autopkgtests: failed to load
l_intl.nls
Marked as found in versions wine/6.0.2~repack-3.
> affects -1 src:libassuan src:gnupg2 src:libgpg-error
Bug #1007014 [src:wine] wine breaks multiple
Source: wine
Control: found -1 wine/6.0.2~repack-3
Control: affects -1 src:libassuan src:gnupg2 src:libgpg-error
Severity: serious
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: breaks
[X-Debbugs-CC:
Source: freecad
Version: 0.19.4+dfsg1-1
Severity: serious
User: debian...@lists.debian.org
Usertags: regression
Dear maintainer(s),
With a recent upload of freecad the autopkgtest of freecad fails in
testing on arm64 and armhf when that autopkgtest is run with the binary
packages of freecad
Processing control commands:
> found -1 python-reportlab/3.6.7-1
Bug #1007012 [src:python-reportlab, src:xhtml2pdf] python-reportlab breaks
xhtml2pdf autopkgtest: cannot import name 'getStringIO' from
'reportlab.lib.utils'
Marked as found in versions python-reportlab/3.6.7-1.
> found -1
Source: python-reportlab, xhtml2pdf
Control: found -1 python-reportlab/3.6.7-1
Control: found -1 xhtml2pdf/0.2.4-1
Severity: serious
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: breaks needs-update
Dear maintainer(s),
With a recent upload of python-reportlab the autopkgtest of
Source: python3.10
Version: 3.10.2-5
Severity: serious
User: debian...@lists.debian.org
Usertags: regression
Dear maintainer(s),
With a recent upload of python3.10 the autopkgtest of python3.10 fails
in testing when that autopkgtest is run with the binary packages of
python3.10 from unstable.
Your message dated Thu, 10 Mar 2022 13:21:16 +
with message-id
and subject line Bug#1005479: fixed in toil 5.6.0-3
has caused the Debian Bug report #1005479,
regarding toil: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i
python{version} -p "3.10 3.9" returned exit code 13
to be
On Thu, Mar 10, 2022 at 01:09:41PM +0100, Paul Gevers wrote:
> I was finally able to make time and do this. I first ran
>
> admin@ci-worker08:/tmp/toil$ apt source toil/unstable
>
> admin@ci-worker08:/tmp/toil/toil-5.6.0$ autopkgtest --shell --shell-fail .
> -- lxc --sudo
Processing control commands:
> tag -1 pending
Bug #1005479 [src:toil] toil: FTBFS: dh_auto_test: error: pybuild --test
--test-pytest -i python{version} -p "3.10 3.9" returned exit code 13
Ignoring request to alter tags of bug #1005479 to the same tags previously set
--
1005479:
Control: tag -1 pending
Hello,
Bug #1005479 in toil 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 #1005479 [src:toil] toil: FTBFS: dh_auto_test: error: pybuild --test
--test-pytest -i python{version} -p "3.10 3.9" returned exit code 13
Added tag(s) pending.
--
1005479: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1005479
Debian Bug
Control: tag -1 pending
Hello,
Bug #1005479 in toil 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:
Hi,
On 03-03-2022 21:35, Paul Gevers wrote:
On 03-03-2022 21:01, Paul Gevers wrote:
b) If you could bypass the unlink (patch pasted below to do so) and
check once, that would be
great
That's a bit hard to do on the infra. I just started the test locally
to see if it reproduces on my
Processing commands for cont...@bugs.debian.org:
> retitle 1006022 puma: flaky tests
Bug #1006022 [src:puma] pume: flaky tests
Changed Bug title to 'puma: flaky tests' from 'pume: flaky tests'.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1006022:
Processing commands for cont...@bugs.debian.org:
> tag 1006994 ftbfs
Bug #1006994 [src:thin] thin: FTBFS on s390x
Added tag(s) ftbfs.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1006994: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006994
Debian Bug
Control: retitle -1 pume: flaky tests
Control: tags -1 ftbfs
Hi,
On Sat, 19 Feb 2022 07:15:51 +0100 Paul Gevers wrote:
I looked at the results of the autopkgtest of you package because it was
showing up as a regression for the upload of glibc. I noticed that the
test regularly fails on all
Processing control commands:
> retitle -1 pume: flaky tests
Bug #1006022 [src:puma] puma: flaky autopkgtest
Changed Bug title to 'pume: flaky tests' from 'puma: flaky autopkgtest'.
> tags -1 ftbfs
Bug #1006022 [src:puma] pume: flaky tests
Added tag(s) ftbfs.
--
1006022:
Your message dated Thu, 10 Mar 2022 11:08:12 +
with message-id
and subject line Bug#1004923: fixed in llvm-toolchain-12 1:12.0.1-20
has caused the Debian Bug report #1004923,
regarding autopkgtest failure due to removed libRemoteIndex*.a
to be marked as done.
This means that you claim that
Source: thin
Version: 1.8.0-1
Severity: serious
Tags: ftbfs
https://buildd.debian.org/status/fetch.php?pkg=thin=amd64=1.8.0-1%2Bb2=1646907946=0
...
Thin::Server robustness
#>/spec/spec_helper.rb:191 run>
terminated with exception (report_on_exception is true):
Source: python-plac
Version: 1.3.4-1
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org
Tags: fbtfs
Dear maintainer,
python-plac will randomly fail to build because
Hi,
On 10-03-2022 10:28, PICCA Frederic-Emmanuel wrote:
Hello Paul, just for info, I have already reported this issue here
https://github.com/g1257/dmrgpp/issues/38
Excellent. I missed the fact that this was part of that bug (I did look
into the upstream before sending my e-mail). I think
Hello Paul, just for info, I have already reported this issue here
https://github.com/g1257/dmrgpp/issues/38
cheers
Fred.
Processing commands for cont...@bugs.debian.org:
> reassign 1006657 src:optimir 1.1-1
Bug #1006657 {Done: Andreas Tille } [src:bowtie2,
src:optimir] bowtie2 breaks optimir autopkgtest: Error with system call:
Bowtie2 index creation failed
Bug reassigned from package 'src:bowtie2, src:optimir'
Dear Neil,
[I try to give feedback to achieve higher quality, but it may sound a
bit pushy. Please read this with best intentions in mind.]
On 08-03-2022 13:36, Debian Bug Tracking System wrote:
Changed-By: Neil Williams
Closes: 1003061
Changes:
dmrgpp (6.02-3) unstable; urgency=medium
.
Your message dated Thu, 10 Mar 2022 08:34:25 +
with message-id
and subject line Bug#1006657: fixed in optimir 1.1-2
has caused the Debian Bug report #1006657,
regarding bowtie2 breaks optimir autopkgtest: Error with system call: Bowtie2
index creation failed
to be marked as done.
This means
Source: thin
Version: 1.8.0-1
Severity: serious
Justification: FTBFS
Dear maintainer(s),
I binNMU'd your package for the ruby2.7 removal transition. Your package fails
to build from source on s390x.
Paul
https://buildd.debian.org/status/fetch.php?pkg=thin=s390x=1.8.0-1%2Bb2=1646899039=0
52 matches
Mail list logo
