Fedora have decided to disable the failing part of that test.[1]
Python docs for the tested function now state "Changed in version 3.9:
This method now accepts zero for k."[2]
[1]
https://src.fedoraproject.org/rpms/python-random2/blob/master/f/python-random2.spec#_39
[2]
Package: src:gevent-websocket
Version: 0.10.1-3
Severity: serious
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: python3.9
gevent-websocket's autopkg tests fail:
[...]
autopkgtest [12:02:51]: test command1: python3 -c "import geventwebsocket"
autopkgtest [12:02:51]: test
Package: src:python-typing-inspect
Version: 0.6.0-1
Severity: serious
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: python3.9
python-typing-inspect's autopkg test fails:
autopkgtest [14:48:01]: test unittests: [---
=== python3.9 ===
Your message dated Sat, 07 Nov 2020 01:42:00 +0100
with message-id <8b824ea3f34ca0a3e3d4a9897bf082cd78d277ec.ca...@debian.org>
and subject line FTBFS fixed by closing #972702
has caused the Debian Bug report #973159,
regarding ruby-joiner: FTBFS: ERROR: Test "ruby2.7" failed: Failure/Error:
Your message dated Sat, 07 Nov 2020 01:42:00 +0100
with message-id <8b824ea3f34ca0a3e3d4a9897bf082cd78d277ec.ca...@debian.org>
and subject line FTBFS fixed by closing #972702
has caused the Debian Bug report #973155,
regarding ruby-puma-worker-killer: FTBFS: ERROR: Test "ruby2.7" failed.
to be
Your message dated Sat, 07 Nov 2020 03:03:44 +
with message-id
and subject line Bug#973156: fixed in sketch 1:0.3.7-12
has caused the Debian Bug report #973156,
regarding sketch: FTBFS: Error: /undefined in .setopacityalpha
to be marked as done.
This means that you claim that the problem has
Your message dated Sat, 07 Nov 2020 01:42:00 +0100
with message-id <8b824ea3f34ca0a3e3d4a9897bf082cd78d277ec.ca...@debian.org>
and subject line FTBFS fixed by closing #972702
has caused the Debian Bug report #973139,
regarding ruby-bootsnap: FTBFS: ERROR: Test "ruby2.7" failed.
to be marked as
Your message dated Sat, 07 Nov 2020 01:42:00 +0100
with message-id <8b824ea3f34ca0a3e3d4a9897bf082cd78d277ec.ca...@debian.org>
and subject line FTBFS fixed by closing #972702
has caused the Debian Bug report #973142,
regarding ruby-arbre: FTBFS: ERROR: Test "ruby2.7" failed: LoadError:
to be
Your message dated Sat, 07 Nov 2020 01:42:00 +0100
with message-id <8b824ea3f34ca0a3e3d4a9897bf082cd78d277ec.ca...@debian.org>
and subject line FTBFS fixed by closing #972702
has caused the Debian Bug report #973140,
regarding ruby-invisible-captcha: FTBFS: ERROR: Test "ruby2.7" failed:
Your message dated Sat, 07 Nov 2020 01:42:00 +0100
with message-id <8b824ea3f34ca0a3e3d4a9897bf082cd78d277ec.ca...@debian.org>
and subject line FTBFS fixed by closing #972702
has caused the Debian Bug report #973146,
regarding ruby-voight-kampff: FTBFS: ERROR: Test "ruby2.7" failed: LoadError:
to
Your message dated Sat, 07 Nov 2020 01:49:05 +
with message-id
and subject line Bug#973133: fixed in ruby-jquery-ui-rails 6.0.1+dfsg-6
has caused the Debian Bug report #973133,
regarding ruby-jquery-ui-rails: FTBFS: Command failed with status (127): [git
submodule update --init...]
to be
Control: tag -1 pending
Hello,
Bug #973133 in ruby-jquery-ui-rails 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 #973133 [src:ruby-jquery-ui-rails] ruby-jquery-ui-rails: FTBFS: Command
failed with status (127): [git submodule update --init...]
Added tag(s) pending.
--
973133: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973133
Debian Bug Tracking
Your message dated Sat, 07 Nov 2020 01:42:00 +0100
with message-id <8b824ea3f34ca0a3e3d4a9897bf082cd78d277ec.ca...@debian.org>
and subject line FTBFS fixed by closing #972702
has caused the Debian Bug report #973110,
regarding ruby-ahoy-email: FTBFS: ERROR: Test "ruby2.7" failed.
to be marked as
Your message dated Sat, 07 Nov 2020 01:42:00 +0100
with message-id <8b824ea3f34ca0a3e3d4a9897bf082cd78d277ec.ca...@debian.org>
and subject line FTBFS fixed by closing #972702
has caused the Debian Bug report #973127,
regarding ruby-combustion: FTBFS: ERROR: Test "ruby2.7" failed: Failure/Error:
Your message dated Sat, 07 Nov 2020 01:42:00 +0100
with message-id <8b824ea3f34ca0a3e3d4a9897bf082cd78d277ec.ca...@debian.org>
and subject line FTBFS fixed by closing #972702
has caused the Debian Bug report #973108,
regarding ruby-sassc-rails: FTBFS: ERROR: Test "ruby2.7" failed.
to be marked as
Your message dated Sat, 07 Nov 2020 01:42:00 +0100
with message-id <8b824ea3f34ca0a3e3d4a9897bf082cd78d277ec.ca...@debian.org>
and subject line FTBFS fixed by closing #972702
has caused the Debian Bug report #973107,
regarding ruby-premailer-rails: FTBFS: ERROR: Test "ruby2.7" failed: LoadError:
Your message dated Sat, 07 Nov 2020 01:42:00 +0100
with message-id <8b824ea3f34ca0a3e3d4a9897bf082cd78d277ec.ca...@debian.org>
and subject line FTBFS fixed by closing #972702
has caused the Debian Bug report #973064,
regarding ruby-rails-controller-testing: FTBFS: ERROR: Test "ruby2.7" failed.
to
Processing commands for cont...@bugs.debian.org:
> close 851048 0.12.0-1
Bug #851048 [src:dipy] dipy: FTBFS: x86_64-linux-gnu-gcc: error: /arch:SSE2: No
such file or directory
Marked as fixed in versions dipy/0.12.0-1.
Bug #851048 [src:dipy] dipy: FTBFS: x86_64-linux-gnu-gcc: error: /arch:SSE2:
Your message dated Fri, 06 Nov 2020 22:49:23 +
with message-id
and subject line Bug#957503: fixed in lpe 1.2.8-2.1
has caused the Debian Bug report #957503,
regarding lpe: ftbfs with GCC-10
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not
Control: tags -1 patch
Hi,
I'm attaching my patch for Stretch to this bug report. Since the
versions in Stretch and unstable are identical, it should work there
too. However I don't intend to NMU guacamole-server because I believe a
new upstream version should be packaged instead.
Processing control commands:
> tags -1 patch
Bug #964195 [src:guacamole-server] CVE-2020-9497 CVE-2020-9498
Added tag(s) patch.
--
964195: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964195
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processing commands for cont...@bugs.debian.org:
> tags 973889 + fixed-upstream
Bug #973889 [src:raptor2] raptor2: CVE-2017-18926
Added tag(s) fixed-upstream.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
973889:
Processing control commands:
> tags 973889 + patch
Bug #973889 [src:raptor2] raptor2: CVE-2017-18926
Added tag(s) patch.
> tags 973889 + pending
Bug #973889 [src:raptor2] raptor2: CVE-2017-18926
Added tag(s) pending.
--
973889: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973889
Debian Bug
Control: tags 973889 + patch
Control: tags 973889 + pending
Dear maintainer,
I've prepared an NMU for raptor2 (versioned as 2.0.14-1.1) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should delay it longer.
Regards,
Salvatore
diff -Nru raptor2-2.0.14/debian/changelog
Source: raptor2
Version: 2.0.14-1
Severity: grave
Tags: security upstream
Justification: user security hole
X-Debbugs-Cc: car...@debian.org, Debian Security Team
Hi,
The following vulnerability was published for raptor2.
CVE-2017-18926[0]:
| raptor_xml_writer_start_element_common in
Thanks for doing that. I unfortunately haven't taken any time for
opensource since the beginning of this COVID madness.
Feel free to push it now. It's totally fine with me.
Thanks
Joseph
Source: dolfin
Followup-For: Bug #973767
Yeah, I'm more certain SLEPc is the problem. In the new release they
abolishing SLEPc.pc, renaming it slepc.pc. Since pkg-config is
case-sensitive, the unexpected change is causing problems.
Notice how the reported error is only with dolfin64. Because
Your message dated Fri, 06 Nov 2020 17:33:31 +
with message-id
and subject line Bug#972490: fixed in rubygems 3.2.0~rc.1-3
has caused the Debian Bug report #972490,
regarding rubygems_3.2.0~rc.1-2_all-buildd.changes REJECTED
to be marked as done.
This means that you claim that the problem
Your message dated Fri, 6 Nov 2020 16:35:18 +0100
with message-id
and subject line enigmail has been removed from stretch
has caused the Debian Bug report #949736,
regarding enigmail: uninstallable in stretch (since thunderbird was upgraded to
version 68 due to security upgrade)
to be marked as
Your message dated Fri, 06 Nov 2020 15:33:36 +
with message-id
and subject line Bug#973095: fixed in cmake-extras 1.5-7
has caused the Debian Bug report #973095,
regarding ros-rospack ftbfs with new googletest
to be marked as done.
This means that you claim that the problem has been dealt
Your message dated Fri, 06 Nov 2020 15:33:36 +
with message-id
and subject line Bug#973095: fixed in cmake-extras 1.5-7
has caused the Debian Bug report #973095,
regarding ros-ros ftbfs in unstable with python3.9
to be marked as done.
This means that you claim that the problem has been dealt
Your message dated Fri, 06 Nov 2020 15:33:36 +
with message-id
and subject line Bug#973095: fixed in cmake-extras 1.5-7
has caused the Debian Bug report #973095,
regarding ros-angles: FTBFS: make[5]: *** No rule to make target
'gmock/libgmock.a', needed by 'devel/lib/angles/utest'. Stop.
to
Processing control commands:
> tag -1 pending
Bug #973095 [cmake-extras] ros-angles: FTBFS: make[5]: *** No rule to make
target 'gmock/libgmock.a', needed by 'devel/lib/angles/utest'. Stop.
Bug #973290 [cmake-extras] ros-ros ftbfs in unstable with python3.9
Bug #973291 [cmake-extras]
Control: tag -1 pending
Hello,
Bug #973095 in cmake-extras 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:
Your message dated Fri, 06 Nov 2020 14:49:51 +
with message-id
and subject line Bug#971171: fixed in libvirt-dbus 1.4.0-2
has caused the Debian Bug report #971171,
regarding libvirt-dbus: FTBFS: dh_auto_test: error: cd debian/build &&
LC_ALL=C.UTF-8 MESON_TESTTHREADS=4 ninja test returned
Package: apt-cacher-ng
Version: 3.2.1-1
Severity: grave
Dear maintainers,
It seems there is one bad exit code issue (=0) when trying to start
démon if internal check is bad. (/etc/init.d/apt-cacher-ng start)
ansible@srv-apt-cache-400:~$ dpkg -l |grep apt-cache
ii apt-cacher-ng
Your message dated Fri, 06 Nov 2020 14:50:33 +
with message-id
and subject line Bug#922589: fixed in opencfu 3.9.0-4
has caused the Debian Bug report #922589,
regarding FTBFS against opencv 4.0.1 (exp)
to be marked as done.
This means that you claim that the problem has been dealt with.
If
Processing control commands:
> severity -1 important
Bug #972769 [src:libsigrokdecode] libsigrokdecode ftbfs with python3.9
Severity set to 'important' from 'serious'
> tag -1 pending
Bug #972769 [src:libsigrokdecode] libsigrokdecode ftbfs with python3.9
Added tag(s) pending.
--
972769:
Control: severity -1 important
Control: tag -1 pending
This is still building fine with the python3-defaults in unstable so
doesn't warrant the serious severity. Upstream has a minor fix to enable
Python3.9 which I will pull in.
J.
--
/-\ | 101 things you can't have
Package: chromium
Version: 84.0.4147.105-1
Severity: grave
Tags: security
Justification: user security hole
X-Debbugs-Cc: Debian Security Team
Versions in Debian, even that in experimental have 100+ open unfixed CVE listed
in the tracker.
Hi there
I encounter the exact same behaviour with:
/etc/debian_version: bullseye/sid
dpkg -l | grep uwsgi:
ii uwsgi-core2.0.19.1-3+b1 amd64
fast, self-healing application container server (core)
ii uwsgi-emperor
Processing commands for cont...@bugs.debian.org:
> close 871564
Bug #871564 [src:manpages-fr] manpages-fr outdated
Marked Bug as done
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
871564: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871564
Debian Bug
close 871564
thanks
This is probably fixed by the switch to a new upstream
Your message dated Fri, 06 Nov 2020 11:03:33 +
with message-id
and subject line Bug#973232: fixed in minexpert2 7.3.0-1
has caused the Debian Bug report #973232,
regarding minexpert2: FTBFS: ProgramWindow.cpp:2318:58: error: no matching
function for call to
Your message dated Fri, 06 Nov 2020 10:48:28 +
with message-id
and subject line Bug#972140: fixed in libsass-python 0.20.1-2
has caused the Debian Bug report #972140,
regarding libsass-python tries to download code from the net for the build
to be marked as done.
This means that you claim
Your message dated Fri, 06 Nov 2020 10:49:57 +
with message-id
and subject line Bug#950929: fixed in python-biom-format 2.1.9-1
has caused the Debian Bug report #950929,
regarding python-biom-format: FTBFS with pandas 1.0: test failures
to be marked as done.
This means that you claim that
Your message dated Fri, 06 Nov 2020 10:49:49 +
with message-id
and subject line Bug#973794: fixed in pybind11 2.6.0-2
has caused the Debian Bug report #973794,
regarding pybind11's autopkg tests fail
to be marked as done.
This means that you claim that the problem has been dealt with.
If
Your message dated Fri, 06 Nov 2020 10:33:22 +
with message-id
and subject line Bug#973804: fixed in bcbio 1.2.4-2
has caused the Debian Bug report #973804,
regarding bcbio: FTBFS undeclared build-dependency on git
to be marked as done.
This means that you claim that the problem has been
Source: gnustep-icons
Version: 1.0-8
Severity: serious
X-Debbugs-Cc: Gürkan Myczko , ba...@debian.org
The maintainer address is invalid, see bounce message below.
Three other packages also have the same invalid address: chess.app,
fontmanager.app and price.app.
Ansgar
On Wed, 2020-11-04 at
Source: satpy
Version: 0.23.0-1
Severity: serious
Tags: ftbfs
Justification: makes the package in question unusable or mostly so
Dear Maintainer,
The autopkgtest of your package fail with pyproj 3.0.0:
=== python3.9 ===
satpy (unittest.loader._FailedTest) ... ERROR
Source: pyresample
Version: 1.16.0+ds-2
Severity: serious
Tags: ftbfs
Justification: makes the package in question unusable or mostly so
Dear Maintainer,
The autopkgtest of your package fail with python-pyproj 3.0.0,
the log shows many issues like this:
E ModuleNotFoundError: No module named
Your message dated Fri, 06 Nov 2020 09:34:11 +
with message-id
and subject line Bug#973846: fixed in manpages 5.09-2
has caused the Debian Bug report #973846,
regarding manpages: file conflict with manpages-dev=5.08-1
to be marked as done.
This means that you claim that the problem has been
Processing commands for cont...@bugs.debian.org:
> # Issue also present in Buster
> found 961534 0.8.3-1
Bug #961534 [s-tui] s-tui: Missing package relation with stress/stress-ng
(Suggests or Recommends)
Marked as found in versions s-tui/0.8.3-1.
> thanks
Stopping processing here.
Please
On 06 nov. 2020 09:02, Moritz Muehlenhoff wrote:
[...]
> 966416 was a RoM (Request of maintainer), if the current maintainer wants to
> get argyll removed, then you should adopt it instead or make a QA upload, but
> you can't simply do an NMU and override the maintainer's request.
>
> Reopening
Processing control commands:
> severity -1 serious
Bug #961534 [s-tui] Please "Recommend: stress-ng/stress"
Severity set to 'serious' from 'wishlist'
> found -1 1.0.2-1
Bug #961534 [s-tui] Please "Recommend: stress-ng/stress"
Marked as found in versions s-tui/1.0.2-1.
> retitle -1 s-tui: Missing
Your message dated Fri, 06 Nov 2020 08:49:24 +
with message-id
and subject line Bug#958607: fixed in pppconfig 2.3.25
has caused the Debian Bug report #958607,
regarding pppconfig: Build-Depends on deprecated dh-systemd which is going away
to be marked as done.
This means that you claim that
Package: uwsgi-emperor
Version: 2.0.19.1-3+b1
Followup-For: Bug #969372
Hi Thomas,
indeed, I have a number of vassals configured, actually I use emperor
for web development for several years now.
At first, I noticed that the emperor haven't start after reboot.
I have tried to start it with
To help integrating these I have opened
https://salsa.debian.org/libvirt-team/libvirt-dbus/-/merge_requests/4
--
Christian Ehrhardt
Staff Engineer, Ubuntu Server
Canonical Ltd
On Mon, 2 Nov 2020 10:34:35 +0100 Timo van Roermund
wrote:
> On Sun, 01 Nov 2020 14:25:03 -0800 Bill Wohler wrote:
>
> > Thanks for explaining the situation. Sounds like just some bad luck.
> > Even so, it would still be good if a mechanism could be created that
> > would prevent this from
60 matches
Mail list logo
