Latest version of wajig (3.2.20) on https://github.com/gjwgit/wajig has
resolved the issue. Currently working on an update to Debian repo.
Regards,
Graham
Processing commands for cont...@bugs.debian.org:
> fixed 971178 20.44.18297-1
Bug #971178 [src:intel-compute-runtime] intel-compute-runtime: FTBFS: make[3]:
***
[igdrcl_lib_release/scheduler/CMakeFiles/scheduler_Gen9core.dir/build.make:84:
bin/scheduler/x64/gen9/scheduler_Gen9core.bin] Error 24
Your message dated Sat, 14 Nov 2020 05:33:19 +
with message-id
and subject line Bug#974560: fixed in mpi4py 3.0.3-7
has caused the Debian Bug report #974560,
regarding mpi4py: autopkgtest regression on amd64, arm64 and ppc64el:
Segmentation fault
to be marked as done.
This means that you cla
Your message dated Sat, 14 Nov 2020 05:33:19 +
with message-id
and subject line Bug#974560: fixed in mpi4py 3.0.3-7
has caused the Debian Bug report #974560,
regarding mpi4py: autopkgtest regression on amd64, arm64 and ppc64el:
Segmentation fault
to be marked as done.
This means that you cla
Control: tag -1 pending
Hello,
Bug #974560 in mpi4py 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/science-team/mpi4py/-/commit/1ee01a245b7097a46da95489a5e962
Processing control commands:
> tag -1 pending
Bug #974560 [src:mpi4py] mpi4py: autopkgtest regression on amd64, arm64 and
ppc64el: Segmentation fault
Bug #974564 [src:mpi4py] mpi4py: autopkgtest regression on amd64, arm64 and
ppc64el: Segmentation fault
Added tag(s) pending.
Added tag(s) pending
Processing commands for cont...@bugs.debian.org:
> reassign 930908 mailcap
Bug #930908 [mime-support] general: incorrect rules for %s in /etc/mailcap
yielding potentially unquoted metacharacters
Bug reassigned from package 'mime-support' to 'mailcap'.
Ignoring request to alter found versions of b
Am Freitag, den 13.11.2020, 23:13 -0300 schrieb Alejandro Taboada:
> Hello Markus,
>
> It doesn’t work. The output log is quite different. I throws a timeout and
> just at the end the “unprivileged client crmd”.
> See attached log.
I'm sorry but I uploaded an older version that missed a do_reply
Package: dash
Version: 0.5.11+git20200708+dd9ef66-2
Severity: serious
Hi,
the latest update of dash seems to have broken the systemd autopkgtest
suite, specifically
https://salsa.debian.org/systemd-team/systemd/-/blob/debian/master/debian/tests/timedated
Afaics, the sh script get's stuck at the
Processing commands for cont...@bugs.debian.org:
> severity 974686 serious
Bug #974686 [python3-blockdev] python3-blockdev: Missing dependencies, without
deps to gir1.2-blockdev-2.0 the python module in unsable
Severity set to 'serious' from 'grave'
> thanks
Stopping processing here.
Please cont
Processing control commands:
> block 968912 with -1
Bug #968912 [release.debian.org] transition: perl 5.32
968912 was blocked by: 968913 972274 974061 961157 974021 964902 961208 974134
974058 974055 972275 974143 961154 961152 973010 974063 974574 960863 961155
974170
968912 was not blocking an
Source: pcp
Version: 5.2.2-1
Severity: serious
Justification: FTBFS on archs that previously worked
User: debian-p...@lists.debian.org
Usertags: perl-5.32-transition
Control: block 968912 with -1
This package FTBFS on the architectures which don't have bpftrace as a
dependency since:
dh_install:
Package: intel-opencl-icd
Followup-For: Bug #974702
Some additional information: I have tried downgrading to previous
versions of the package, and I found out that:
intel-opencl-icd 20.13.16352-1 has the issue
intel-opencl-icd 20.02.15268-1 has not
In fact, with 20.02 clinfo at least works, even
Package: intel-opencl-icd
Version: 20.37.17906-1
Severity: critical
When this package is installed, any OpenCL program will abort with the
message
Abort was called at 42 line in file:
/build/intel-compute-runtime-WsWnhf/intel-compute-runtime-20.37.17906/shared/source/built_ins/built_ins.cpp
Appli
Processing commands for cont...@bugs.debian.org:
> forwarded 970878 https://bugs.ghostscript.com/show_bug.cgi?id=703143
Bug #970878 [src:ghostscript] ghostscript breaks doc-rfc autopkgtest:
segmentation fault
Set Bug forwarded-to-address to
'https://bugs.ghostscript.com/show_bug.cgi?id=703143'.
Thank you for the 9u1.3 packages. Just installed on one of my QA
clusters and it's working.
Phil Ward.
The University achieved an overall 5 stars in the QS World University Rankings
2020
UK Sports University of the Year 2020 (Times Higher Good University Guide)
Th
Your message dated Fri, 13 Nov 2020 22:00:14 +
with message-id
and subject line Bug#973010: fixed in pcp 5.2.2-1
has caused the Debian Bug report #973010,
regarding pcp is uninstallable on many architectures due to new bpftrace
dependency
to be marked as done.
This means that you claim that
Your message dated Fri, 13 Nov 2020 22:00:12 +
with message-id
and subject line Bug#973160: fixed in pbbam 1.6.0+dfsg-1
has caused the Debian Bug report #973160,
regarding pbbam: FTBFS: optional.hpp:1591:3: error: static assertion failed: If
you want to output boost::optional, include header
Your message dated Fri, 13 Nov 2020 14:15:25 -0700
with message-id <20201113211525.ga1526...@debian-e431.fok>
and subject line Bug#974096: fixed in golang-github-c-bata-go-prompt 0.2.5-1
has caused the Debian Bug report #974096,
regarding golang-github-c-bata-go-prompt: autopkgtest regression: cann
Hi,
I am not able to reproduce the FTBFS with cowbuilder. It builds just fine
on my side.
Would it be possible to try the rebuild again?
Best regards
Ruben
Am Donnerstag, den 12.11.2020, 15:50 -0300 schrieb Alejandro Taboada:
> Hi !
>
> Just tested v1.1 and the issue persists. The problem is quiet local
> connection when using with corosync
Hello,
I believe I have found and fixed the problem. The refactored code in lrmd.c
caused the regression. Sin
On 2020-11-13 18:23 +0100, Niels Thykier wrote:
> Control: reassign -1 perl-base
> Control: affects -1 upgrade-reports
> Control: severity -1 grave
>
> Hi Perl team,
>
> I have reassigned this bug to perl because perl-base being essential
> must remain functional during an upgrade and AFAICT perl-
Processing commands for cont...@bugs.debian.org:
> severity 974177 important
Bug #974177 [libnss3] libnss3: Handshake failed (-12251) with Pidgin since
2:3.58-1
Severity set to 'important' from 'serious'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
974177: htt
Your message dated Fri, 13 Nov 2020 19:48:28 +
with message-id
and subject line Bug#957369: fixed in ipband 0.8.1-5.1
has caused the Debian Bug report #957369,
regarding ipband: ftbfs with GCC-10
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is
severity 974177 important
thanks
Oops, I thought the bug was on the pidgin package, sorry.
Processing commands for cont...@bugs.debian.org:
> severity 974177 serious
Bug #974177 [libnss3] libnss3: Handshake failed (-12251) with Pidgin since
2:3.58-1
Severity set to 'serious' from 'important'
>
End of message, stopping processing here.
Please contact me if you need assistance.
--
9741
Package: python3-blockdev
Version: 2.20-7+deb10u1
Severity: grave
Justification: renders package unusable
Dear Maintainer,
What's need to be done:
- Play arround with the BlockDev API within python
What exactly did you do (or not do) that was effective (or ineffective)?
- Do a simple apt
Your message dated Fri, 13 Nov 2020 18:48:32 +
with message-id
and subject line Bug#974619: fixed in systemd 247~rc2-2
has caused the Debian Bug report #974619,
regarding FTBFS on mips*el: ../src/basic/macro.h:415:9: error: static assertion
failed: "__NR_close_range == systemd_NR_close_range"
Processing control commands:
> tag -1 pending
Bug #973126 [src:responses] responses: FTBFS: dh_auto_test: error: pybuild
--test --test-pytest -i python{version} -p "3.9 3.8" returned exit code 13
Added tag(s) pending.
--
973126: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973126
Debian Bu
Control: tag -1 pending
Hello,
Bug #973126 in responses 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/responses/-/commit/a6fd876548eb5971
Source: trafficserver
Version: 8.1.0+ds-1
Severity: serious
Justification: ftp-master autoreject ruling
Hi,
Your package has an autopkgtest, awesome. However, I noticed that it
installs Python code using pip. Running downloaded code from internet is
not allowed in the Debian archive; see the ftp-
Processing control commands:
> tag -1 pending
Bug #974538 [libkscreenlocker5] libkscreenlocker5: kwin cannot start due to
missing libkscreenunlocker5 symbols
Added tag(s) pending.
--
974538: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=974538
Debian Bug Tracking System
Contact ow...@bugs.d
Control: tag -1 pending
Hello,
Bug #974538 in kscreenlocker 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/qt-kde-team/kde/kscreenlocker/-/commit/5b5d09c5a06ca
Control: reassign -1 perl-base
Control: affects -1 upgrade-reports
Control: severity -1 grave
Hi Perl team,
I have reassigned this bug to perl because perl-base being essential
must remain functional during an upgrade and AFAICT perl-base fails in
this case here.
If it is a direct linkage, then
Processing control commands:
> reassign -1 perl-base
Bug #974552 [upgrade-reports] upgrade-reports: libc6/libcrypt split breaks perl
during buster->bullseye upgrade
Bug reassigned from package 'upgrade-reports' to 'perl-base'.
Ignoring request to alter found versions of bug #974552 to the same va
The new release 1.1.2 should fix the bug:
https://github.com/postgrespro/pg_wait_sampling/releases
Your message dated Fri, 13 Nov 2020 14:46:01 +
with message-id
and subject line Bug#973129: fixed in pglogical 2.3.3-2
has caused the Debian Bug report #973129,
regarding pglogical: FTBFS: ld: cannot find -lreadline
to be marked as done.
This means that you claim that the problem has been dea
Also comment that this bug doesn't happen when the program is run as a
flatpak, only when run as a native program.
El 13/11/20 a las 15:15, Debian Bug Tracking System escribió:
Thank you for filing a new Bug report with Debian.
You can follow progress on this Bug here: 974666:
https://bugs.de
Processing control commands:
> tag -1 pending
Bug #973129 [src:pglogical] pglogical: FTBFS: ld: cannot find -lreadline
Added tag(s) pending.
--
973129: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973129
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Control: tag -1 pending
Hello,
Bug #973129 in pglogical 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/postgresql/pglogical/-/commit/fb637b5dfef2228a666be59fc5
Package: gnome-sound-recorder
Version: 3.38.0-1
Severity: grave
Tags: patch
Justification: causes non-serious data loss
X-Debbugs-Cc: rasters...@gmail.com
Dear Maintainer,
After doing a recording, pressing the "export" button shows, as expected, a
file dialog to choose where to export the file. T
Processing commands for cont...@bugs.debian.org:
> tags 958610 + pending
Bug #958610 [src:open-iscsi] open-iscsi: Build-Depends on deprecated dh-systemd
which is going away
Added tag(s) pending.
> tags 958592 + pending
Bug #958592 [src:open-isns] open-isns: Build-Depends on deprecated dh-systemd
On Thu, 23 Apr 2020 22:37:30 +0200 bi...@debian.org wrote:
> Source: open-isns
> Severity: normal
> User: pkg-systemd-maintain...@lists.alioth.debian.org
> Usertags: dh-systemd-removal
>
> Hi,
>
> your package open-isns declares a build dependency on dh-systemd.
> dh-systemd was merged into debhe
On Thu, 23 Apr 2020 22:37:30 +0200 bi...@debian.org wrote:
> Source: open-iscsi
> Severity: normal
> User: pkg-systemd-maintain...@lists.alioth.debian.org
> Usertags: dh-systemd-removal
>
> Hi,
>
> your package open-iscsi declares a build dependency on dh-systemd.
> dh-systemd was merged into deb
Your message dated Fri, 13 Nov 2020 13:18:22 +
with message-id
and subject line Bug#974660: fixed in ginkgocadx 3.8.8-5
has caused the Debian Bug report #974660,
regarding ginkgocadx: FTBFS in sid
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is
Control: tag -1 pending
Hello,
Bug #974660 in ginkgocadx 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/med-team/ginkgocadx/-/commit/ad586a4734a3ef02267b713efe
Processing control commands:
> tag -1 pending
Bug #974660 [src:ginkgocadx] ginkgocadx: FTBFS in sid
Added tag(s) pending.
--
974660: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=974660
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processing control commands:
> tags -1 patch
Bug #974660 [src:ginkgocadx] ginkgocadx: FTBFS in sid
Added tag(s) patch.
> forwarded -1 https://github.com/gerddie/ginkgocadx/pull/53
Bug #974660 [src:ginkgocadx] ginkgocadx: FTBFS in sid
Set Bug forwarded-to-address to 'https://github.com/gerddie/gink
control: tags -1 patch
control: forwarded -1 https://github.com/gerddie/ginkgocadx/pull/53
https://github.com/gerddie/ginkgocadx/pull/53
I fixed the build failure by adding the missing include, and opened a Pull
Request upstream.
cheers,
Gianfranco
On Tue, Sep 01, 2020 at 12:29:02PM +0200, Michael Hanke wrote:
> It seems that upstream has changed the way they set the SO version
> information:
>
> https://salsa.debian.org/med-team/nifticlib/-/commit/eabee0938978a7f5e8e28522be3d856dee3975cf#48dc04d58c3c3f29ad0415ca64d38e3231bffd87_0_17
>
> an
Processing commands for cont...@bugs.debian.org:
> tags 974660 + ftbfs
Bug #974660 [src:ginkgocadx] ginkgocadx: FTBFS in sid
Added tag(s) ftbfs.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
974660: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=974660
Debian
Control: severity -1 important
On Sat, 07 Nov 2020 14:52:56 +0100 ORL wrote:
> Package: suckless-tools
> Version: 45-1
> Severity: grave
> Justification: renders package unusable
(well, it makes one command unusable, not the whole package)
I see you have filed #973515; the description of that o
Processing commands for cont...@bugs.debian.org:
> retitle 972420 Adios FTBFS with python3.9 due to cython
Bug #972420 [src:adios] adios ignores errors in the packaging and ftbfs with
python3.9
Changed Bug title to 'Adios FTBFS with python3.9 due to cython' from 'adios
ignores errors in the pa
Processing control commands:
> severity -1 important
Bug #973919 [suckless-tools] suckless-tools: dmenu disappears when typing in
i3wm
Severity set to 'important' from 'grave'
--
973919: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973919
Debian Bug Tracking System
Contact ow...@bugs.debia
Source: ginkgocadx
Version: 3.8.8-4
Severity: serious
Hello, looks like the current version in sid now FTBFS against new libdcmtk15
can you please have a look?
https://buildd.debian.org/status/fetch.php?pkg=ginkgocadx&arch=amd64&ver=3.8.8-4%2Bb1&stamp=1605242581&raw=0
A snip of the failing log i
Processing control commands:
> block -1 by 968730
Bug #974649 [release.debian.org] release.debian.org: new libnifti2 broke
runtime (see #968730)
974649 was not blocked by any bugs.
974649 was not blocking any bugs.
Added blocking bug(s) of 974649: 968730
> tags -1 + moreinfo
Bug #974649 [release.
Processing commands for cont...@bugs.debian.org:
> forwarded 974619 https://github.com/systemd/systemd/issues/17591
Bug #974619 [src:systemd] FTBFS on mips*el: ../src/basic/macro.h:415:9: error:
static assertion failed: "__NR_close_range == systemd_NR_close_range"
Set Bug forwarded-to-address to
Processing control commands:
> tags -1 + patch
Bug #973195 [src:python-asyncssh] python-asyncssh: FTBFS: dh_auto_test: error:
pybuild --test -i python{version} -p "3.9 3.8" --system=custom
"--test-args={interpreter} -m unittest discover -v" returned exit code 13
Added tag(s) patch.
--
973195:
Control: tags -1 + patch
the new upstream 2.4.2 fixes the 3.9 issues, and the package also seems to work
with python3-pycryptodome
one test is failing with both 3.8 and 3.9:
==
ERROR: test_confirm (tests.test_agent._TestAgent)
T
Processing commands for cont...@bugs.debian.org:
> severity 974571 important
Bug #974571 [libx11-6] libx11-6: the locale is not supported by Xlib,
continuing without locale support
Severity set to 'important' from 'grave'
> thanks
Stopping processing here.
Please contact me if you need assistanc
Severity: -1 important
That's not a grave bug.
On 13/11/2020 12:23, Alejandro Taboada wrote:
> Maybe Corocync is not using peer communication? Could you check someway the
> packet source address .. if it’s form localhost just allow, other check
> permissions
> I know is not ideal but will solve a tot of production issues in the
> meanwhile.
Processing commands for cont...@bugs.debian.org:
> found 972155 5.2.2.2-1~exp1
Bug #972155 {Done: Dmitry Shachnev } [src:dtkwidget]
dtkwidget: FTBFS with Qt 5.15: error: aggregate 'QPainterPath borderPath' has
incomplete type and cannot be defined
Marked as found in versions dtkwidget/5.2.2.2-1~
Your message dated Fri, 13 Nov 2020 11:33:33 +
with message-id
and subject line Bug#974545: fixed in fraqtive 0.4.8-12
has caused the Debian Bug report #974545,
regarding fraqtive FTBFS: error: aggregate ‘QPainterPath path’ has incomplete
type and cannot be defined
to be marked as done.
This
Maybe Corocync is not using peer communication? Could you check someway the
packet source address .. if it’s form localhost just allow, other check
permissions
I know is not ideal but will solve a tot of production issues in the meanwhile.
> On 12 Nov 2020, at 23:20, Alejandro Taboada
> wrote
Your message dated Fri, 13 Nov 2020 11:03:33 +
with message-id
and subject line Bug#973889: fixed in raptor2 2.0.14-1.1~deb10u1
has caused the Debian Bug report #973889,
regarding raptor2: CVE-2017-18926
to be marked as done.
This means that you claim that the problem has been dealt with.
If
Your message dated Fri, 13 Nov 2020 11:03:37 +
with message-id
and subject line Bug#973748: fixed in sddm 0.18.0-1+deb10u1
has caused the Debian Bug report #973748,
regarding sddm: CVE-2020-28049: local privilege escalation due to race
condition in creation of the Xauthority file
to be marked
Le 13/11/2020 à 11:45, Adrian Bunk a écrit :
On Fri, Nov 13, 2020 at 09:02:52AM +0100, Sylvestre Ledru wrote:
Le 13/11/2020 à 08:44, Aurelien Jarno a écrit :
Source: rust-zoxide
Version: 0.4.3-1
Severity: serious
Could the rust tooling create "Section: fixme" instead?
This would give you the l
Control: forwarded -1
https://github.com/unified-font-object/ufoNormalizer/issues/73
deprecated features in Python 3.4 ...
there's a proposal to re-introduce the deprecated Data class to work around it.
Processing control commands:
> forwarded -1 https://github.com/unified-font-object/ufoNormalizer/issues/73
Bug #973167 [src:ufonormalizer] ufonormalizer: FTBFS: dh_auto_test: error:
pybuild --test -i python{version} -p "3.9 3.8" returned exit code 13
Set Bug forwarded-to-address to
'https://gith
On Fri, Nov 13, 2020 at 09:02:52AM +0100, Sylvestre Ledru wrote:
> Le 13/11/2020 à 08:44, Aurelien Jarno a écrit :
> > Source: rust-zoxide
> > Version: 0.4.3-1
> > Severity: serious
> >
> > rust-zoxide contains an invalid Section for the Source package:
> >
> > | Source: rust-zoxide
> > | Section
Processing control commands:
> severity -1 serious
Bug #968730 [libnifti2] libnifti2: libniftiio.so.2 not provided
Severity set to 'serious' from 'normal'
--
968730: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=968730
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processing control commands:
> severity -1 important
Bug #968339 [src:kodi] kodi: FTBFS in sid (test failures)
Severity set to 'important' from 'serious'
> close -1
Bug #968339 [src:kodi] kodi: FTBFS in sid (test failures)
Marked Bug as done
--
968339: https://bugs.debian.org/cgi-bin/bugreport.c
Control: severity -1 important
Control: close -1
On Wed, 09 Sep 2020 08:33:00 + Vasyl Gello wrote:
> Control: reopen !
>
> I am reopening this bug as mipsel test failures are caused by ld.gold usage
filed separately.
Those issue* seems not to be related to this bug, so I don't think reopeni
Control: tags -1 + patch
fixed by new upstream 0.8
example packaging (no changes) at
https://launchpad.net/ubuntu/+source/parso/0.8.0-0ubuntu1
Your message dated Fri, 13 Nov 2020 10:17:08 +
with message-id
and subject line Bug#973660: fixed in thunderbird 1:78.4.2-1~deb10u1
has caused the Debian Bug report #973660,
regarding thunderbird: FTBFS on s390x in buster
to be marked as done.
This means that you claim that the problem has be
Processing control commands:
> tags -1 + patch
Bug #973193 [src:parso] parso: FTBFS: dh_auto_test: error: pybuild --test
--test-pytest -i python{version} -p "3.9 3.8" returned exit code 13
Added tag(s) patch.
--
973193: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973193
Debian Bug Trackin
Control: tags -1 + patch
patch at
http://launchpadlibrarian.net/506790173/python-future_0.18.2-4_0.18.2-4ubuntu1.diff.gz
Processing control commands:
> tags -1 + patch
Bug #973114 [src:python-future] python-future: FTBFS: dh_auto_test: error:
pybuild --test --test-pytest -i python{version} -p "3.9 3.8" returned exit code
13
Added tag(s) patch.
--
973114: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973114
D
Control: tags -1 + patch
fixed in new upstream version 1.2.0.
example packaging at
https://launchpad.net/ubuntu/+source/cairocffi/1.2.0-0ubuntu3
this disables the flake8 tests, and the isort tests, pytest-isort is not yet
packaged for Debian.
Processing control commands:
> tags -1 + patch
Bug #973121 [src:cairocffi] cairocffi: FTBFS: dh_auto_test: error: pybuild
--test -i python{version} -p "3.9 3.8" returned exit code 13
Added tag(s) patch.
--
973121: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973121
Debian Bug Tracking Syst
new upstream 0.12. 0.11 is said to support 3.9, 0.10 is said to support 3.8
Your message dated Fri, 13 Nov 2020 08:44:54 +
with message-id
and subject line Bug#974639: fixed in rust-zoxide 0.4.3-2
has caused the Debian Bug report #974639,
regarding rust-zoxide: wrong section in debian/control
to be marked as done.
This means that you claim that the problem has been d
Processing control commands:
> tags -1 + patch
Bug #973134 [src:python-webob] python-webob: FTBFS: tests failed
Added tag(s) patch.
--
973134: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973134
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Control: tags -1 + patch
fixed by upstream pull request 411, uploaded to the delayed queue
Hi
On Fri, 13 Nov 2020 at 09:45, Aurelien Jarno wrote:
> Version check failed:
> Your upload included the binary package biosig-tools, version 1.9.5-1+b2, for
> mipsel,
> however testing already has version 2.0.6-1+b1.
> Uploads to unstable must have a higher version than present in testing.
It
Le 13/11/2020 à 08:44, Aurelien Jarno a écrit :
Source: rust-zoxide
Version: 0.4.3-1
Severity: serious
rust-zoxide contains an invalid Section for the Source package:
| Source: rust-zoxide
| Section: FIXME-(source.section)
| Priority: optional
| Build-Depends: debhelper (>= 11),
| dh-cargo (>=
87 matches
Mail list logo
