Control: tags -1 - moreinfo
Control: tags -1 + confirmed
Control: block -1 by 949288 949290
On Sun, 19 Jan 2020 at 13:12, Matthias Klose wrote:
> these are now filed, with patches.
Thanks! Please go ahead.
Source: r-cran-ranger
Version: 0.12.1-1
X-Debbugs-CC: debian...@lists.debian.org
Severity: serious
User: debian...@lists.debian.org
Usertags: regression
Hi Maintainer
Since the upload of r-cran-ranger 0.12.1-1, its own autopkgtests have
been failing [1] on at least arm64, ppc64el and s390x.
I've
On 2020/01/20 19:12, Hans-Christoph Steiner wrote:
If the android-tools maintainer doesn't respond, then yes, I suppose
removing it is the right option. Its no longer maintained by the
Android Tools team, I suppose we should correct that in the package.
Who is the android-tools maintainer then
Control: reopen -1
Control: retitle -1 kazoo: autopkgtest regression
Hi Thomas
Just to be clear, the problem is an autopkgtest regression.
I'm re-opening this bug as it is still not fixed [1].
You can run the autopkgtests locally to check that they are fixed before
uploading.
More informati
Source: r-cran-rlang
Version: 0.4.2-1
X-Debbugs-CC: debian...@lists.debian.org
Severity: serious
User: debian...@lists.debian.org
Usertags: regression
Hi Maintainer
Since the upload of r-cran-rlang 0.4.2-1, its own autopkgtests have been
failing when tested against packages in testing [1], with
Source: r-cran-parameters
Version: 0.3.0-1
X-Debbugs-CC: debian...@lists.debian.org
Severity: serious
User: debian...@lists.debian.org
Usertags: regression
Hi Maintainer
Sometime between 2020-01-13 and 2010-01-18, r-cran-parameters'
autopkgtests started to fail in unstable [1] with the followin
Hi Andreas
On Fri, 24 Jan 2020 at 11:21, Andreas Tille wrote:
> and I have no idea how to fix this. May be there is some unspecified
> versioned Build-Depends or something like this.
This is the kind of bug that autopkgtests blocking testing migration
is supposed to catch.
I see you uploaded r
Source: haskell-hledger-lib
Version: 1.14.1-1
Severity: serious
Tags: ftbfs
Control: affects -1 + src:haskell-hledger
Control: affects -1 + src:haskell-hledger-ui
Control: affects -1 + src:haskell-hledger-web
Hi Maintainer
Since the upload of haskell-hledger-lib 1.14.1-1, it has FTBFS on s390x.
Package: ftp.debian.org
Severity: normal
android-tools builds android-tools-mkbootimg 5.1.1.r38-1.1, but it is
superceded by android-tools-mkbootimg 1:8.1.0+r23-5 built by
android-platform-system-core
android-tools is no longer maintained by the Android Tools team (#949149)
and blocks Python2 rem
Hi Sandro
Are you planning to upload the new version of sphinx-copybutton soon?
sphinx-copybutton [1] is currently blocked for migration:
Not built on buildd: arch all binaries uploaded by morph, a new
source-only upload is needed to allow migration
...which in turn blocks skimage [2]:
Invalid
Source: watson
Version: 1.6.0-6
Severity: serious
Tags: ftbfs
Hi Maintainer
Both watson 1.6.0-6 in bullseye and 1.7.0-5 in sid FTBFS [1].
The upload to sid did not migrate to testing [2]. Please do
source-only uploads, unless there are NEW binaries.
Not built on buildd: arch all binaries upload
Control: reopen -1
Hi Drew
The test gets a little further [1], and now fails at:
___ test_inr ___
def test_inr():
this_dir = os.path.dirname(os.path.abspath(__file__))
mesh = pygalmesh.generate_from_inr(
As of now, lazarus 2.0.6+dfsg-3 has failed its autopkgtests 2 out of
11 times on amd64 [1], and 3 out of 11 times on arm64 [2].
I am hesitant to re-open this bug as RC, as it potentially removes all
packages built with lazarus for no good reason.
[1] https://ci.debian.net/packages/l/lazarus/test
Source: fontforge
Version: 1:20190801~dfsg-2
Severity: normal
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: python3.8 python3-all-dev
The package build-depends on python3-all-dev, but does not build
extensions/libraries for all supported python3 versions. This
is seen on the t
Source: libguestfs
Version: 1:1.40.2-4
Severity: normal
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: python3.8 python3-all-dev
The package build-depends on python3-all-dev, but does not build
extensions/libraries for all supported python3 versions. This
is seen on the transit
Source: stimfit
Version: 0.16.0-1
Severity: normal
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: python3.8 python3-all-dev
The package build-depends on python3-all-dev, but does not build
extensions/libraries for all supported python3 versions. This
is seen on the transition t
Source: getfem++
Version: 5.3+dfsg1-3
Severity: normal
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: python3.8 python3-all-dev
The package build-depends on python3-all-dev, but does not build
extensions/libraries for all supported python3 versions. This
is seen on the transiti
Source: ceph
Version: 14.2.4-8
Severity: normal
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: python3.8 python3-all-dev
The package build-depends on python3-all-dev, but does not build
extensions/libraries for all supported python3 versions. This
is seen on the transition trac
Source: libimobiledevice
Version: 1.2.1~git20190929.60823f9-2
Severity: normal
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: python3.8 python3-all-dev
The package build-depends on python3-all-dev, but does not build
extensions/libraries for all supported python3 versions. This
Hi Dmitry
On Sun, 5 Jan 2020 at 10:51, Dmitry Shachnev wrote:
> And binNMU all packages marked as bad.
I only see 8 packages marked bad.
Many of those, e.g. qt-gstreamer and kadu, FTBFS during the previous
rebuild to pick up libqt5gui5-gles.
I've only binNMU'd piperka for now.
Regards
Graham
Control: tags -1 + patch
On Wed, 8 Jan 2020 at 21:57, Paul Gevers wrote:
> autopkgtest [07:15:08]: test f2py: [---
> /tmp/autopkgtest-lxc.jhh9qajz/downtmp/build.odB/src/debian/tests/f2py:
> 24: Syntax error: Unterminated quoted string
> autopkgtest [07:15:08]: test f2py: -
Hi Christoph
On 2020/01/13 15:20, Christoph Berg wrote:
I think this is a bug in lazarus on arm64, but maybe I'm wrong:
https://buildd.debian.org/status/fetch.php?pkg=cqrlog&arch=arm64&ver=2.4.0-3&stamp=1578918606&raw=0
700 291.337/324.064 Kb Used
800 291.987/324.064 Kb Used
(9009) Assembling
I think this is #948803 in binutils.
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=948803
Source: cp2k
Version: 6.1-3
Hi Maintainer
Since switching from libint to libint2 in cp2k 6.1-3, the builds on
armhf and i386 have been showing many failures similar to the
following [1]:
>>> /<>/tools/regtesting/../..//TEST-Linux-armv7l-gfortran-popt-2019-08-30_01-25-24/tests/QS/regtest-mp2-grad
Source: haskell-hgettext
Version: 0.1.31.0-5
Severity: serious
User: debian...@lists.debian.org
Usertags: regression
X-Debbugs-CC: debian...@lists.debian.org
Hi Maintainer
Some time in August 2020, haskell-hgettext's autopkgtests regressed in
testing [1].
I've copied what I hope is the relevant p
Control: reopen -1
Hi Alastair
This same test also fails on i386 [1].
tests/test_dataarray.py::TestDataArray::test_pad_constant FAILED [ 56%]
Regards
Graham
[1] https://ci.debian.net/packages/p/python-xarray/testing/i386/
This appears to be fixed, at least on arm64 and ppc64el, by the upload
of armadillo/1:10.6.2+dfsg-1.
Source: dolfinx
Version: 2019.2.0~git20210130.c14cb0a-5
Severity: important
Hi Maintainer
Your package uses a vendored copy of catch.hpp. It will FTBFS once
glibc is upgraded to 2.34 due to MINSIGSTKSZ and SIGSTKSZ no longer
being defined.
You could take this opportunity to switch to using the
Source: spdlog
Version: 1:1.8.5+ds-2
Severity: important
Hi Maintainer
Your package uses a vendored copy of catch.hpp. It will FTBFS once
glibc is upgraded to 2.34 due to MINSIGSTKSZ and SIGSTKSZ no longer
being defined.
You could take this opportunity to switch to using the catch2 package
[1]
Source: openmsx
Version: 17.0-1
Severity: important
Hi Maintainer
Your package uses a vendored copy of catch.hpp. It will FTBFS once
glibc is upgraded to 2.34 due to MINSIGSTKSZ and SIGSTKSZ no longer
being defined.
You could take this opportunity to switch to using the catch2 package
[1] in De
Source: ensmallen
Version: 2.17.0-1
Severity: important
Hi Maintainer
Your package uses a vendored copy of catch.hpp. It will FTBFS once
glibc is upgraded to 2.34 due to MINSIGSTKSZ and SIGSTKSZ no longer
being defined.
You could take this opportunity to switch to using the catch2 package
[1] i
Source: catch
Version: 1.12.1-1.1
Severity: important
Hi Maintainer
Catch will FTBFS once glibc is upgraded to 2.34 due to MINSIGSTKSZ and
SIGSTKSZ no longer being defined.
This was fixed Catch2's upstream [1]. I'm not sure if this can be
adapted for Catch(1).
Another approach is to simply repl
Source: dolfin
Version: 2019.2.0~git20201207.b495043-5
Severity: important
Hi Maintainer
Your package uses a vendored copy of catch.hpp. It will FTBFS once
glibc is upgraded to 2.34 due to MINSIGSTKSZ and SIGSTKSZ no longer
being defined.
You could take this opportunity to switch to using the c
Source: dazzdb
Version: 1.0+git20201103.8d98c37-1
Severity: serious
Forwarded: https://github.com/thegenemyers/DAZZ_DB/issues/41
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: needs-update
Hi Maintainer
Since the upload of glibc 2.32-1 to unstable, dazzdb's au
The entry below was dropped from debian/changelog and I think it's the
reason why the BTS thinks this bug is not fixed in 2021.08.1+dfsg-2 in
unstable.
dask (2021.01.0+dfsg-1) unstable; urgency=medium
[ Diane Trout ]
* New upstream release
* Fix fake http proxy url as dask's build system p
Control: severity -1 serious
The autopkgtest always fails in testing [1] but passes in unstable,
where the boost1.71 packages are still available.
[1] https://ci.debian.net/packages/b/boost1.74/testing/amd64/
Source: r-bioc-deseq2
Version: 1.30.1+dfsg-1
Severity: serious
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: regression
Hi Maintainer
The autopkgtests of r-bioc-deseq2 regressed in testing sometime after
2021-09-07 11:35:05 UTC [1].
E: Package 'r-bioc-tximpo
Source: boost1.74
Version: 1.74.0-10
Severity: serious
Tags: patch
Hi Maintainer
After #992223 was fixed, I noticed that the mpi-python autopkgtest still fails.
I found that mpi.cpython-39-x86_64-linux-gnu.so was not installed in
the libboost-mpi-python1.74.0 package.
I was able to fix this with
Hi Drew
On Sat, 5 Jun 2021 at 06:15, Drew Parsons wrote:
> az_aztec.h is in libtrilinos-aztecoo-dev. Hence the fix is to set
> libtrilinos-ml-dev Depends: libtrilinos-aztecoo-dev
Please feel free to make a team upload, or even better, add yourself
to Uploaders ;-)
Regards
Graham
On Sat, 5 Jun 2021 at 11:09, Drew Parsons wrote:
> True, you do have other things on your mind at this period of time :)
:)
> It's probably worth fixing this problem for bullseye, I think.
I agree. Please consider this a pre-approval.
Control: tags -1 + confirmed
Hi Nicola
On Thu, 10 Jun 2021 at 08:33, Nicola Di Lieto wrote:
> as requested I attach the source debdiff. Thank you.
Please go ahead and upoad to unstable, then remove the moreinfo tag.
Regards
Graham
Control: tags -1 + moreinfo confirmed
Hi Andrius
On Thu, 10 Jun 2021 at 13:45, Andrius Merkys wrote:
> I am seeking pre-approval to upload openbabel/3.1.1+dfsg-6.
Please go ahead and upoad to unstable, then remove the moreinfo tag.
Regards
Graham
Control: tags -1 + moreinfo confirmed
Hi Håvard
On Thu, 10 Jun 2021 at 10:21, Håvard Flaget Aasen
wrote:
> Please unblock package libexplain
Please go ahead and upoad to unstable, then remove the moreinfo tag.
Regards
Graham
Source: libyang
Version: 1.0.184-2
Severity: serious
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: regression
Hi Maintainer
The autopkgtest of libyang fails in testing where it succeeded in the past [1].
The current failure seems to be due python3-yang being
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Please unblock package libgee-0.8
[ Reason ]
libgee-0.8/0.20.3-1 in testing currently FTBFS against the current
valac (#988020)
[ Impact ]
libgee-0.8 is not able to be updated in testing
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Please unblock package joblib
[ Reason ]
joblib/0.17.0-3 fails its autopkgtests on s390x, a big-endian architecture
[ Impact ]
As per upstream issue #1123 [1], joblib.load() on a big-endia
Control: tags -1 + moreinfo confirmed
Hi Stephen
There's a typo in your changelog, the bug number should be #989862:
+gcc-mingw-w64 (24.2) unstable; urgency=medium
+
+ * Fix gcov handling: we need to tell GCC that we have headers, without
+telling it where, and then we need to correct its d
Control: tags -1 + moreinfo
Hi Samuel
As can be seen in aeskeyfind's excuses [1]:
not blocked: has successful autopkgtest
You'll need to file a RoM; ANAIS bug against ftp.debian.org [2]
requesting removal of aeskyfind's binaries on the architectures where
it no longer builds.
Please close this
Control: tags -1 + moreinfo
Hi Thomas
On Mon, 14 Jun 2021 at 21:12, Thomas Goirand wrote:
> [x] attach debdiff against the package in testing
You've attached a debdiff against uwsgi/2.0.19.1-7 in unstable, which
is currently blocked [1].
I think it will be best if 2.0.19.1-7 migrates to testi
Hi Thomas, Jonas
On Wed, 16 Jun 2021 at 16:07, Thomas Goirand wrote:
> I'm hereby attaching the output of:
> git diff -u -r debian/2.0.19.1-6 -r debian/2.0.19.1-7
Thanks.
> Maybe you could unblock debian/2.0.19.1-7 considering this is a target
> patch? Otherwise, Jonas may agree to revert the p
Control: tags -1 + confirmed
On Wed, 16 Jun 2021 at 17:21, Jonas Smedegaard wrote:
> Correct: the changes in debian/2.0.19.1-7 should not affect Debian.
Thanks. That was fortunate timing, uwsgi/2.0.19.1-7 and
uwsgi-plugin-php/0.0.12 are both in testing now.
> Sorry for the mess.
No harm done.
Control: severity -1 serious
Control: tags -1 + bullseye-ignore
Hi Andrius
While unblocking openbabel/3.1.1+dfsg-6, I noticed that the
autopkgtests are skipped on arm64 [1], and this would have blocked
migration to testing.
It would be great if you could improve this situation, but seeing it
is
Control: tags -1 + moreinfo
Hi Daniele
On Tue, 15 Jun 2021 at 03:12, Daniele Tricoli wrote:
> The code for the fix is trivial, I packaged the new release because when I
> looked at diff between the 2 tags, there were: the fix for CVE-2021-33503,
> some
> fix for deprecation warnings emitted in
uwsgi's testing excuses [1] currently shows (amd64 only for clarity):
migrating uwsgi-core/2.0.19.1-7.1/amd64 to testing makes
uwsgi-plugin-luajit/2.0.19.1+5+0.0.6/amd64 uninstallable
migrating uwsgi-core/2.0.19.1-7.1/amd64 to testing makes
uwsgi-plugin-mongo/2.0.19.1+5+0.0.7/amd64 uninstallable
m
Control: tags -1 + moreinfo confirmed
Hi Kumar
On Mon, 21 Jun 2021 at 06:27, Kumar Appaiah wrote:
> Please permit me to upload the attached targeted fix from upstream
> that fixed erroneous calculations relating to sparse diagonal
> matrices. This fix is needed to prevent some numerical errors,
Control: tags -1 - moreinfo
Hi Daniele
On Sun, 27 Jun 2021 at 18:34, Daniele Tricoli wrote:
> Is there something I can do now? Sorry for the new amount of work... :/
These things happen. :) I don't think there's anything we can do now,
except wait to see the results of the autopkgtests.
Regar
Control: tags -1 + moreinfo confirmed
Hi Salvatore
On Mon, 28 Jun 2021 at 09:30, Salvatore Bonaccorso wrote:
> Please unblock package nfs-utils, or rather this is a pre-approval
> request for it.
...
> Okay to upload?
Please go ahead and upload to unstable, and remove the moreinfo tag
once it h
Control: tags -1 + moreinfo confirmed
Hi Matthias
On Wed, 23 Jun 2021 at 03:12, Matthias Klumpp wrote:
> Let me know what you think!
Assuming it can happen soon, please go ahead upload to unstable, and
remove the moreinfo tag once it has built.
Regards
Graham
Control: tags -1 + moreinfo confirmed
Hi Andreas
On Wed, 7 Jul 2021 at 16:09, Andreas Beckmann wrote:
> I'd like to drop the Recommends: libomp-9-dev from clang-9
> libomp-*-dev are not co-installable and libomp-dev depends on
> libomp-11-dev. Having the Recomends on the non-default libomp-9-dev
Control: tags -1 + moreinfo confirmed
Hi Andrey
On Sat, 10 Jul 2021 at 10:42, Andrey Rahmatullin wrote:
> unblock kvirc/4:5.0.0+dfsg-5
I don't see 4:5.0.0+dfsg-5 in unstable yet, so I'm not sure if this
was meant to be a pre-approval request. Assuming it was, please go
ahead and upload to unst
Control: tags -1 + moreinfo confirmed
Hi Peter
On Sat, 10 Jul 2021 at 14:03, Peter Pentchev wrote:
> This is a pre-approval request before I upload nomad to unstable to
> fix a security problem (CVE-2021-32575).
Assuming it can happen soon, please go ahead upload to unstable, and
remove the mor
Control: tags -1 + moreinfo confirmed
Control: retitle -1 unblock: libserialport/0.1.1-4
Hi Jonathan
On Sat, 10 Jul 2021 at 19:03, Jonathan McDowell wrote:
> unblock libserialport/0.1.1-3
I'm assuming this bug was meant as a pre-approval request for 0.1.1-4.
Please go ahead and upload to unstab
Control: tags -1 + moreinfo confirmed
Hi Benjamin
On Mon, 12 Jul 2021 at 08:57, Benjamin Hof wrote:
> I'd be happy to provide a new upload with a more useful autopkgtest
> that executes the test suite, if that'd work for you.
That sounds good! Please go ahead with a new upload and remove the
m
Control: tags -1 + moreinfo confirmed
Hi Marcos
On Tue, 13 Jul 2021 at 17:33, Marcos Fouces wrote:
> I still not uploaded the package to sid waiting for aproval.
Please go ahead and upload, then remove the moreinfo tag once it has built.
Regards
Graham
Control: tags -1 + moreinfo confirmed
Hi David
On Tue, 13 Jul 2021 at 22:33, David Mohammed wrote:
> Please unblock package budgie-desktop
Please go ahead and upload to unstable, then remove the moreinfo tag
once it has built.
Regards
Graham
Control: tags -1 + moreinfo confirmed
Control: tags 990808 -1 -moreinfo confirmed
Sorry, I managed to reply to the wrong bug.
Hi Marcos
On Tue, 13 Jul 2021 at 17:33, Marcos Fouces wrote:
> I still not uploaded the package to sid waiting for aproval.
Please go ahead and upload, then remove th
Control: tags -1 + moreinfo
Hi Salvatore
On Fri, 16 Jul 2021 at 21:24, Salvatore Bonaccorso wrote:
> fail2ban is affected by CVE-2021-32749, see detailed advisory in
> https://github.com/fail2ban/fail2ban/security/advisories/GHSA-m985-3f3v-cwmm,
> which is a possible remote code execution vulner
Control: tags -1 + moreinfo
Hi Kartik
On Sun, 18 Jul 2021 at 08:33, Kartik Mistry wrote:
> Please unblock apertium-apy (0.11.7-2) which will fix #990917
>
> Let me know if any additional information is needed.
Please see the 'Appropriate changes during Hard and Full Freeze'
section and the 'App
Control: tags -1 + moreinfo
Hi Stig
Please attach a filtered debdiff to this bug. Something like:
filterdiff -x '*/build-aux/*' -x '*/doc/html/*'
varnish-6.5.1-1--6.5.2-1.debdiff >filtered.debdiff
Please also show the command that you end up using, so we can see
which parts were excluded.
Reg
Hi Kartik
On Sun, 18 Jul 2021 at 10:48, Kartik Mistry wrote:
> [x] attach debdiff against the package in testing
It looks like you've attached a binary debdiff. We are looking for a
source debdiff between the version in testing and unstable.
i.e.
debdiff apertium-apy_0.11.6-1.dsc apertium-ap
Control: tags -1 + confirmed
Hi Stig
On Mon, 19 Jul 2021 at 13:00, Stig Sandbeck Mathisen wrote:
> Attached is the diff. Changes are the upstream bugfix, as well as two commits
> in the packaging repository:
Thanks. Please go ahead and upload to unstable, then remove the
moreinfo tag once it h
Control: tags -1 + moreinfo confirmed
Hi Sascha
On Mon, 19 Jul 2021 at 13:57, Sascha Steinbiss wrote:
> I have added a debdiff to this bugreport that illustrates the
> situation. I could upload to unstable anytime. Please let me know if the
> fix is appropriate and I will initiate an upload if c
Control: tags -1 + moreinfo confirmed
Hi Kyle
Please go ahead and upload to unstable, then remove the moreinfo tag
once it has built.
Regards
Graham
Source: xmltooling
Version: 3.2.0-2
Severity: serious
User: debian...@lists.debian.org
Usertags: regression
X-Debbugs-CC: debian...@lists.debian.org
Hi Maintainer
Sometime around mid-July 2021, xmltooling's autopkgtests started to
fail in testing [1].
I've copied what I hope is the relevant part
Control: tags -1 + confirmed moreinfo
Hi Andreas
On Thu, 29 Jul 2021 at 14:33, Andreas Beckmann wrote:
> The fix is not yet uploaded, I intend to 2-day NMU it.
Please go ahead and upload to unstable, then remove the moreinfo tag
once it has built.
Regards
Graham
Control: tags -1 + moreinfo
Hi Praveen
On Sat, 31 Jul 2021 at 21:21, wrote:
> + * Bump debhelper from old 10 to 12.
Please revert this change. See 'Target fixes' section of the freeze policy [1].
Regards
Graham
[1] https://release.debian.org/bullseye/freeze_policy.html#full
Control: tags -1 + confirmed moreinfo
Hi Étienne
Please go ahead and upload to unstable, then remove the moreinfo tag
once it has built.
Regards
Graham
://bugs.launchpad.net/ubuntu/+source/cron/+bug/1938924
Author: Graham Inggs
Last-Update: 2021-08-06
--- a/crontab.5
+++ b/crontab.5
@@ -91,7 +91,7 @@
.IR cron (8)
daemon.
SHELL is set to /bin/sh, and LOGNAME and HOME are set from the /etc/passwd
-line of the crontab's owner. PATH is set to "/us
source: libvpd
Version: 2.2.7-1
Severity: normal
Tags: sid bookworm
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-11
Forwarded: https://github.com/power-ras/libvpd/pull/5
[This bug is not targeted to the upcoming bullseye release]
Please keep this issue open in the bug tracker for the pac
Source: mpi4py
Version: 3.0.3-8
Severity: serious
User: debian...@lists.debian.org
Usertags: regression
X-Debbugs-CC: debian...@lists.debian.org
Hi Maintainer
Some time around 2021-08-25, mpi4py's autopkgtests regressed in testing [1].
This seems to coincide with the migration of pmix/4.1.0-3 to
Hi Drew
I followed the discussion on the upstream issue.
What do you think of adding some extra test dependencies to mpi4py's
debian/tests/control?
Depends: python3-mpi4py,
+libpmix-dev,
+libucx-dev [amd64 arm64 ppc64el],
python3-cffi,
python3-dill,
python3-distutils,
Thi
Even better would be to add the following section to debian/tests/control:
# Dummy test so that changes to other packages trigger our autopkgtests
# on ci.debian.net
Test-Command: /bin/true
Depends: libpmix-dev,
libucx-dev [amd64 arm64 ppc64el],
Restrictions: hint-testsuite-triggers
Refer
ht
On Mon, 30 Aug 2021 at 00:22, Drew Parsons wrote:
> Graham, when I run autopkgtest, it skips the dummy test, which is what
> we want, but it does so with the message
>
>SKIP unknown restriction hint-testsuite-triggers
>
>
> "unknown restriction", is this normal? If so it's a bit misleading
>
Source: boost1.74
Version: 1.74.0-10
Severity: serious
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: regression
Hi Maintainer
The 'context' autopkgtest of boost1.74 fails on non-amd64 architectures [1].
I've copied what I hope is the relevant output below.
R
Control: severity -1 serious
Per Debian Policy 4.9, packages in main must not attempt network
access during the build.
Source: python-reportlab, python-biopython
Control: found -1 python-reportlab/3.5.67-2
Control: found -1 python-biopython/1.78+dfsg-5
Severity: serious
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: breaks needs-update
Hi Maintainers
The recent upload of pytho
Source: r-cran-testthat
Version: 3.0.4-1
Severity: important
Hi Maintainer
Your package uses a vendored copy of catch.hpp. It will FTBFS once
glibc is upgraded to 2.34 due to MINSIGSTKSZ and SIGSTKSZ no longer
being defined.
You could take this opportunity to switch to using the catch package
[
Source: python-fabio
Version: 0.11.0+dfsg-2
Severity: serious
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: needs-update
Hi Maintainer
Sometime around 2021-04-28, python-fabio's autopkgtests started to
fail in testing [1].
I've copied what I hope is the relev
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Please unblock package htop
[ Reason ]
Fix a division by zero in ZfsCompressedArcMeter
[ Impact ]
Users of ZFS-on-Linux, with ZfsCompressedArcMeter enabled in htop, but
no ZFS volumes moun
Control: severity -1 serious
This same issue prevents lmfit-py/1.0.1-5 from migrating to testing.
Issues preventing migration:
blocked by freeze: autopkgtest not fully successful
I'll make a team upload shortly, disabling test_model_nan_policy and
test_manypeaks_speed during the build and autopk
Hi Ole
On Thu, 6 May 2021 at 14:13, Ole Streicher wrote:
> You are right, however it should be ensured to migrate before Bullseye,
> as it downgrades an RC bug. This is not directly visible, since I
> downgraded the bug already after the upload.
>
> --> if you plan to release before May 24, the m
Source: node-millstone
Version: 0.6.19-3
Severity: serious
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: needs-update
Hi Maintainer
Sometime around 2021-04-21, node-millstone's autopkgtests started to
fail in testing [1].
I've copied what I hope is the releva
Control: forwarded -1 https://sourceforge.net/p/mcj/tickets/120/
Control: tags -1 + patch
This was reported upstream by Michael Hudson-Doyle .
Source: lintian-brush
Version: 0.99
Severity: serious
Tags: ftbfs
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: needs-update
Hi Maintainer
Sometime between 2021-03-30 and 2021-04-06, lintian-brush's
autopkgtests started to fail in testing [1]. I've copied wh
Control: forwarded -1 https://deb.li/6f4z
TMB upstream have submitted a bug report [1] to R-forge.
> Headers need update corresponding to new SuiteSparse version 5.7.1
>
> SuiteSparse was recently updated from version 4.2.1 to 5.7.1, however without
> updating the header `inst/cholmod.h` accordi
Control: tags -1 + fixed-upstream
Fixed in Matrix upstream svn rev 3376 [1].
[1]
https://r-forge.r-project.org/scm/viewvc.php?view=rev&root=matrix&revision=3376
Source: boxer-data
Version: 10.8.20
Severity: serious
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: regression
Hi Maintainer
The autopkgtest of boxer-data fails in testing where it succeeded in
the past [1].
The current failure seems to be due to the removal
Source: pexpect
Version: 4.8.0-1
Severity: serious
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: flaky
Hi Maintainer
The autopkgtests of pexpect fail regularly and are therefore
unsuitable for regression testing. I've copied below what I hope is
the relevant
Control: tags -1 + moreinfo
Hi Frédéric
You didn't include a source debdiff with your unblock request. Also,
the Vcs-Browser URL [1] in debian/control returns 404.
I generated a diff and got the following:
61 files changed, 19938 insertions(+), 2005 deletions(-)
This is unreviewable by us. On
Control: tags -1 + moreinfo
Hi Javier
On Mon, 19 Apr 2021 at 23:27, Chris Hofstaedtler wrote:
>
> > $ debdiff snort_2.9.15.1-4_i386.deb snort_2.9.15.1-5_i386.deb
> [..]
>
> The debdiff does not seem to show any actual packaging changes. Are
> you sure you diffed the correct files?
This looks li
201 - 300 of 2172 matches
Mail list logo
