Control: forcemerge 902411 -1
Am 02.07.2018 um 22:45 schrieb Eric Valette:
> Package: upower
> Version: 0.99.8-1
> Severity: grave
> Justification: renders package unusable
>
> I had no upowerd daemon running on all my boxes:
>
> Jul 02 20:52:00 htpc1 systemd[1]: Starting Daemon for power
Processing control commands:
> forcemerge 902411 -1
Bug #902411 {Done: Jan Gerber } [upower] upower fails to start
with MemoryDenyWriteExecute=true
Bug #902884 [upower] upowerd fails to start
Severity set to 'important' from 'grave'
Marked Bug as done
Merged 902411 902884
--
902411:
Source: ant
Version: 1.10.3-2
Severity: serious
Justification: makes the package in question unusable or mostly so
Control: affects -1 src:josm
Dear Maintainer,
As mentioned on the list [0], the change in ant (1.10.3-2) to
automatically set the value of the javac --release attribute breaks the
Processing control commands:
> affects -1 src:josm
Bug #902895 [src:ant] ant: Automatically setting the value of the javac
--release attribute breaks josm build.
Added indication that 902895 affects src:josm
--
902895: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=902895
Debian Bug
Your message dated Tue, 03 Jul 2018 04:34:44 +
with message-id
and subject line Bug#902766: fixed in twisted 18.4.0-2
has caused the Debian Bug report #902766,
regarding python3-twisted fails in the post-installation script when doing a
first-time install
to be marked as done.
This means
Control: found -1 4.9.88-1+deb9u1
Hi,
On Sun, Jul 01, 2018 at 03:42:12AM +0100, Ben Hutchings wrote:
Is this bug still present?
It still reproduces with the current stretch kernel:
debian@debian:~/openldap-2.4.44+dfsg/debian/build/tests$ ./run -b mdb
test060-mt-hot
Cleaning up test run
Processing control commands:
> found -1 4.9.88-1+deb9u1
Bug #866122 [src:linux] test060-mt-hot failing on ppc64el buildd
Bug #866371 [src:linux] openldap FTBFS on ppc64{,el}: slapd-mtread failed (139)
Marked as found in versions linux/4.9.88-1+deb9u1.
Marked as found in versions
Processing control commands:
> reassign -1 python3.7
Bug #902788 [python3-minimal] python3-minimal needs Breaks for software/modules
broken by 3.7
Bug reassigned from package 'python3-minimal' to 'python3.7'.
No longer marked as found in versions python3-defaults/3.6.6-1.
Ignoring request to
Control: reassign -1 python3.7
On 30.06.2018 22:58, Adrian Bunk wrote:
Package: python3-minimal
Version: 3.6.6-1
Severity: serious
Control: block -1 by 902757 902631 902766 902646 902715 902650
Control: block 902582 by -1
Plenty of packages fail to work or even install with Python 3.7
for
Package: plinth
Version: 0.33.0
Severity: grave
Justification: renders package unusable
If plinth has a single admin user account, and any changes are made to
that user account, the user will be locked out of plinth.
More information and logs:
On Mon, 2018-07-02 at 22:15 +0200, Mathieu Parent wrote:
> Package: src:talloc
> Version: 2.1.13-1
> Severity: serious
>
> Regression since python3 support:
>
> [...]
> dh_makeshlibs -ppython-talloc -ppython3-talloc -Xtalloc. -- -c3
> dpkg-gensymbols: warning: new libraries appeared in the
Processing commands for cont...@bugs.debian.org:
> reassign 902868 src:nvidia-graphics-drivers
Bug #902868 [src:linux] linux-image-4.16.0-2-amd64 fails to boot
Bug reassigned from package 'src:linux' to 'src:nvidia-graphics-drivers'.
No longer marked as found in versions linux/4.16.16-2.
Ignoring
Your message dated Mon, 02 Jul 2018 22:49:13 +
with message-id
and subject line Bug#901110: fixed in libgdamm5.0 4.99.11-2
has caused the Debian Bug report #901110,
regarding libgdamm5.0: FTBFS when built with dpkg-buildpackage -A
to be marked as done.
This means that you claim that the
On 2018-07-02 20:10, gregor herrmann wrote:
> On Mon, 02 Jul 2018 09:19:11 +0200, Guillaume Bougard wrote:
>
>> in fact, and regarding the package history, the bug should have
>> been opened with 2.3.10 and closed with not releases 2.3.15...
>>
>> How to avoid this case becomes blocking for the
Package: upower
Version: 0.99.8-1
Severity: grave
Justification: renders package unusable
I had no upowerd daemon running on all my boxes:
Jul 02 20:52:00 htpc1 systemd[1]: Starting Daemon for power management...
Jul 02 20:52:01 htpc1 upowerd[1106]: /usr/lib/upower/upowerd: error
while loading
Processing commands for cont...@bugs.debian.org:
> found 902786 0.7.3-7
Bug #902786 {Done: Andreas Tille } [src:libquazip]
CVE-2018-1002209
Marked as found in versions libquazip/0.7.3-7.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
902786:
Package: src:talloc
Version: 2.1.13-1
Severity: serious
Regression since python3 support:
[...]
dh_makeshlibs -ppython-talloc -ppython3-talloc -Xtalloc. -- -c3
dpkg-gensymbols: warning: new libraries appeared in the symbols file:
libpytalloc-util.cpython-36m-aarch64-linux-gnu.so.2
On Mon, Jul 02, 2018 at 08:43:04PM +0100, Chris Lamb wrote:
> > This particular error is fixed by d6f1d04 (and I did include the bug
> > number in the commit).
>
> Are we talking about the right commit? I only ask because I do not see
> the bug number in the commit... :)
>
>
Control: owner -1 !
Control: tag -1 pending
On Mon, Jul 02, 2018 at 06:52:15PM +0100, Chris Lamb wrote:
> Are we still seeing this on current master? (As-of writing, that is
> a6b4effc). I ask because, as mentioned previously, I cannot reproduce
> this. :)
This particular error is fixed by
Processing control commands:
> owner -1 !
Bug #902709 [diffoscope] diffoscope: FTBFS: /usr/lib/python3.6/tempfile.py:509:
FileNotFoundError
Owner recorded as Mattia Rizzolo .
> tag -1 pending
Bug #902709 [diffoscope] diffoscope: FTBFS: /usr/lib/python3.6/tempfile.py:509:
FileNotFoundError
Added
Hi Mattia,
> This particular error is fixed by d6f1d04 (and I did include the bug
> number in the commit).
Are we talking about the right commit? I only ask because I do not see
the bug number in the commit... :)
https://salsa.debian.org/reproducible-builds/diffoscope/commit/
Package: debian-installer
Version: 20180610
Severity: grave
I tried to install Debian Testing on VirtualBox using a weekly build of Debian
Installer. Everything went OK until the disk partitioning stage. In this
stage, installer warned me that the kernel doesn't support LVM and I should
load
Processing commands for cont...@bugs.debian.org:
> found 902726 10.7.5+dfsg-1
Bug #902726 [gitlab] 2018/06/25 security release
There is no source info for the package 'gitlab' at version '10.7.5+dfsg-1'
with architecture ''
Unable to make a source version for version '10.7.5+dfsg-1'
Marked as
Processing commands for cont...@bugs.debian.org:
> found 902726 10.7.5+dfsg-3
Bug #902726 [gitlab] 2018/06/25 security release
Marked as found in versions gitlab/10.7.5+dfsg-3.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
902726:
On Mon, Jul 02, 2018 at 06:36:54PM +0100, Simon McVittie wrote:
> On Wed, 06 Sep 2017 at 14:58:37 -0700, Josh Triplett wrote:
> > (It might also help to add Ctrl-Alt-Delete to the list of shortcuts
> > provided in the gnome-boxes keyboard menu, alongside Ctrl-Alt-Backspace
> > and similar.)
>
>
On Mon, Jul 02, 2018 at 06:14:44PM +0100, Simon McVittie wrote:
> On Mon, 02 Jul 2018 at 01:39:24 -0700, Josh Triplett wrote:
> > On Mon, Jul 02, 2018 at 08:14:48AM +0100, Simon McVittie wrote:
> > > This seems to work under GNOME 3.28 (probably also 3.26). I'm prompted
> > > while starting up the
Processing commands for cont...@bugs.debian.org:
> found 902721 1.7.2-1
Bug #902721 [ruby-json-jwt] CVE-2018-1000539
Marked as found in versions ruby-json-jwt/1.7.2-1.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
902721:
Processing commands for cont...@bugs.debian.org:
> forwarded 902721 https://github.com/nov/json-jwt/pull/62
Bug #902721 [ruby-json-jwt] CVE-2018-1000539
Set Bug forwarded-to-address to 'https://github.com/nov/json-jwt/pull/62'.
> thanks
Stopping processing here.
Please contact me if you need
Processing commands for cont...@bugs.debian.org:
> forwarded 902723 https://github.com/gosa-project/gosa-core/issues/14
Bug #902723 {Done: Mike Gabriel } [src:gosa]
CVE-2018-1000528
Set Bug forwarded-to-address to
'https://github.com/gosa-project/gosa-core/issues/14'.
> thanks
Stopping
Processing commands for cont...@bugs.debian.org:
> found 902723 2.7.4+reloaded3-1
Bug #902723 {Done: Mike Gabriel } [src:gosa]
CVE-2018-1000528
Marked as found in versions gosa/2.7.4+reloaded3-1.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
902723:
On Mon, 02 Jul 2018 09:19:11 +0200, Guillaume Bougard wrote:
> in fact, and regarding the package history, the bug should have
> been opened with 2.3.10 and closed with not releases 2.3.15...
>
> How to avoid this case becomes blocking for the migration to
> testing planned in 8 days now ?
Processing commands for cont...@bugs.debian.org:
> tags 902720 + upstream
Bug #902720 [ruby-zip] CVE-2018-1000544
Added tag(s) upstream.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
902720: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=902720
Debian Bug
Processing commands for cont...@bugs.debian.org:
> forwarded 902720 https://github.com/rubyzip/rubyzip/issues/369
Bug #902720 [ruby-zip] CVE-2018-1000544
Set Bug forwarded-to-address to 'https://github.com/rubyzip/rubyzip/issues/369'.
> thanks
Stopping processing here.
Please contact me if you
Processing commands for cont...@bugs.debian.org:
> found 902720 1.2.1-1
Bug #902720 [ruby-zip] CVE-2018-1000544
Marked as found in versions ruby-zip/1.2.1-1.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
902720:
Hi Mattia,
> So, autopkgtest is failing
[…]
> The ubuntu build also failed with a very similar error
[…]
> And also the reproducible builds build FTBFS with the same errors.
Are we still seeing this on current master? (As-of writing, that is
a6b4effc). I ask because, as mentioned previously, I
Processing commands for cont...@bugs.debian.org:
> found 902774 9.2.24-1
Bug #902774 [jetty9] jetty9: CVE-2017-7656 CVE-2017-7657 CVE-2017-7658
CVE-2018-12536
Marked as found in versions jetty9/9.2.24-1.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
902774:
Processing commands for cont...@bugs.debian.org:
> retitle 902774 jetty9: CVE-2017-7656 CVE-2017-7657 CVE-2017-7658
> CVE-2018-12536
Bug #902774 [jetty9] jetty9: CVE-2017-7656 CVE-2017-7657 CVE-2017-7658
CVE-2018-12536 CVE-2018-12538
Changed Bug title to 'jetty9: CVE-2017-7656 CVE-2017-7657
Package: src:linux
Version: 4.16.16-2
--- Please enter the report below this line. ---
Ich kann den Fehler bestätigen und weiter eingrenzen. Ich komme bis zum
Start des X-Servers und dann kommt erst der Fehler. Ein neu kompilieren
des NVIDIA Treibers brachte keinen erfolgt. Mein System friert
On Wed, 06 Sep 2017 at 14:58:37 -0700, Josh Triplett wrote:
> (It might also help to add Ctrl-Alt-Delete to the list of shortcuts
> provided in the gnome-boxes keyboard menu, alongside Ctrl-Alt-Backspace
> and similar.)
This is now provided in the keyboard menu for both gnome-boxes and
Processing control commands:
> retitle -1 Keyboard grab doesn't (always?) work under Wayland
Bug #874526 {Done: Simon McVittie } [gnome-boxes] Keyboard
grab doesn't work under Wayland
Changed Bug title to 'Keyboard grab doesn't (always?) work under Wayland' from
'Keyboard grab doesn't work
Control: retitle -1 Keyboard grab doesn't (always?) work under Wayland
Control: reopen -1
Control: tags -1 + moreinfo
On Mon, 02 Jul 2018 at 01:39:24 -0700, Josh Triplett wrote:
> On Mon, Jul 02, 2018 at 08:14:48AM +0100, Simon McVittie wrote:
> > This seems to work under GNOME 3.28 (probably
Control: tag -1 pending
Hello,
Bug #901110 in libgdamm5.0 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 #901110 [src:libgdamm5.0] libgdamm5.0: FTBFS when built with
dpkg-buildpackage -A
Added tag(s) pending.
--
901110: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=901110
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Your message dated Mon, 02 Jul 2018 16:47:12 +
with message-id
and subject line Bug#895599: fixed in ganeti 2.15.2-7+deb9u2
has caused the Debian Bug report #895599,
regarding ganeti-2.15 - Fails to export vm: certificate is valid but its
commonName does not match hostname
to be marked as
Your message dated Mon, 02 Jul 2018 16:47:13 +
with message-id
and subject line Bug#897429: fixed in tclreadline 2.1.0-15+deb9u1
has caused the Debian Bug report #897429,
regarding ppc64el: Shared Object not available in the platform
to be marked as done.
This means that you claim that the
Package: sagemath
Version: 8.2-5
Severity: grave
Justification: renders package unusable
Dear Maintainer,
see sage crash log below.
-- System Information:
Debian Release: buster/sid
APT prefers testing
APT policy: (800, 'testing'), (750, 'unstable'), (500, 'unstable-debug'),
(500,
Control: severity -1 important
Control: tag -1 + moreinfo
在 2018年7月2日星期一 CST 下午10:33:29，Prescott 写道：
> Package: flameshot
> Version: 0.5.1+git20180601-1
> Severity: grave
> Justification: renders package unusable
>
> Dear Maintainer,
>
>Upgraded to testing from stable for help in bugs
Processing control commands:
> severity -1 important
Bug #902866 [flameshot] flameshot: Will not run, exits with error "Could not
connect to display"
Severity set to 'important' from 'grave'
> tag -1 + moreinfo
Bug #902866 [flameshot] flameshot: Will not run, exits with error "Could not
connect
Package: src:linux
Version: 4.16.16-2
Severity: critical
Justification: breaks the whole system
Dear Maintainer,
* What led up to the situation?
Up to date Debian testing on 2 July 2018
apt-get update
apt-get upgrade
linux-image-4.16.0-2-amd64 updated (I think)
reboot
* What was the
Your message dated Mon, 02 Jul 2018 14:39:20 +
with message-id
and subject line Bug#899704: fixed in sympa 6.2.32~dfsg-2
has caused the Debian Bug report #899704,
regarding sympa: Invalid maintainer address
pkg-sympa-de...@lists.alioth.debian.org
to be marked as done.
This means that you
Your message dated Mon, 02 Jul 2018 14:35:30 +
with message-id
and subject line Bug#899765: fixed in libmime-lite-html-perl 1.24-3
has caused the Debian Bug report #899765,
regarding libmime-lite-html-perl: Invalid maintainer address
pkg-sympa-de...@lists.alioth.debian.org
to be marked as
Package: flameshot
Version: 0.5.1+git20180601-1
Severity: grave
Justification: renders package unusable
Dear Maintainer,
Upgraded to testing from stable for help in bugs finding and for
some newer packages I needed from Buster.
I originally used my sxhkd keybinding "flameshot gui -p
Your message dated Mon, 02 Jul 2018 13:34:45 +
with message-id
and subject line Bug#902715: fixed in psycopg2 2.7.5-2
has caused the Debian Bug report #902715,
regarding python3-psycopg2 fails to install with Python 3.7
to be marked as done.
This means that you claim that the problem has
Le 02/07/2018 à 14:51, Emmanuel Bourg a écrit :
> axis fails to build with Java 10 due to the removal of the com.sun.net.ssl
> API:
>
>
> ./axis/src/org/apache/axis/components/net/SunFakeTrustSocketFactory.java:24:
> error: package com.sun.net.ssl does not exist
> import
Control: tag -1 pending
Hello,
Bug #902715 in psycopg2 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 #902715 [python3-psycopg2] python3-psycopg2 fails to install with Python 3.7
Added tag(s) pending.
--
902715: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=902715
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Source: axis
Severity: serious
Tags: sid buster
User: debian-j...@lists.debian.org
Usertags: default-java10
axis fails to build with Java 10 due to the removal of the com.sun.net.ssl API:
./axis/src/org/apache/axis/components/net/SunFakeTrustSocketFactory.java:24:
error: package
close 902410 5:4.0.10-1
# for the BTS graph
found 902410 2:2.8.17-1
thanks
Processing commands for cont...@bugs.debian.org:
> close 902410 5:4.0.10-1
Bug #902410 [redis] redis: CVE-2018-12326
Marked as fixed in versions redis/5:4.0.10-1.
Bug #902410 [redis] redis: CVE-2018-12326
Marked Bug as done
> # for the BTS graph
> found 902410 2:2.8.17-1
Bug #902410 {Done:
Processing commands for cont...@bugs.debian.org:
> retitle 902644 upower: no longer emits plug/unplug events after upgrade to
> 0.99.8
Bug #902644 [upower] upower: Upower breaks power saving settings after upgrade
to 0.99.8-1
Changed Bug title to 'upower: no longer emits plug/unplug events
Processing commands for cont...@bugs.debian.org:
> severity 902644 serious
Bug #902644 [upower] upower: Upower breaks power saving settings after upgrade
to 0.99.8-1
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
Your message dated Mon, 02 Jul 2018 10:00:37 +
with message-id
and subject line Bug#901043: fixed in vkd3d 1.0-3
has caused the Debian Bug report #901043,
regarding vkd3d-demos: /usr/bin/triangle is already shipped by the triangle-bin
package
to be marked as done.
This means that you claim
Your message dated Mon, 02 Jul 2018 10:00:30 +
with message-id
and subject line Bug#899684: fixed in reportbug 7.5.0
has caused the Debian Bug report #899684,
regarding reportbug: Invalid maintainer address
reportbug-ma...@lists.alioth.debian.org
to be marked as done.
This means that you
Your message dated Mon, 02 Jul 2018 10:00:10 +
with message-id
and subject line Bug#896619: fixed in bottleneck 1.2.1+ds1-1
has caused the Debian Bug report #896619,
regarding FTBFS with sphinx 1.7.2: exception: cannot import name 'Directive'
to be marked as done.
This means that you claim
Your message dated Mon, 02 Jul 2018 10:00:21 +
with message-id
and subject line Bug#893953: fixed in imagemagick 8:6.9.10.2+dfsg-1
has caused the Debian Bug report #893953,
regarding imagemagick: FTBFS on i386: testsuite failure in
Magick++/tests/tests.tap 2
to be marked as done.
This means
Your message dated Mon, 02 Jul 2018 10:00:21 +
with message-id
and subject line Bug#893953: fixed in imagemagick 8:6.9.10.2+dfsg-1
has caused the Debian Bug report #893953,
regarding imagemagick: FTBFS on any-i386
to be marked as done.
This means that you claim that the problem has been
Your message dated Mon, 02 Jul 2018 10:00:29 +
with message-id
and subject line Bug#892574: fixed in pike8.0 8.0.610-1
has caused the Debian Bug report #892574,
regarding pike8.0 FTBFS with glibc 2.27
to be marked as done.
This means that you claim that the problem has been dealt with.
If
Your message dated Mon, 02 Jul 2018 10:00:29 +
with message-id
and subject line Bug#885673: fixed in pike8.0 8.0.610-1
has caused the Debian Bug report #885673,
regarding pike8.0-gtk: Depends on old GNOME libraries
to be marked as done.
This means that you claim that the problem has been
Processing control commands:
> block 895025 by 857260
Bug #895025 [src:libindicate] deprecate/remove libindicate in Debian
895025 was blocked by: 895027 895031 895026
895025 was not blocking any bugs.
Added blocking bug(s) of 895025: 857260
> severity 857260 serious
Bug #857260
Control: block 895025 by 857260
Control: severity 857260 serious
On Mon, 02 Jul 2018 at 10:38:53 +0100, Simon McVittie wrote:
> On Fri, 06 Apr 2018 at 10:58:00 +, Mike Gabriel wrote:
> > So, in a nutshell, these packages need to be addressed: smuxi,
> > pidgin-libnotify and mopidy-mpris
On Fri, 06 Apr 2018 at 10:58:00 +, Mike Gabriel wrote:
> So, in a nutshell, these packages need to be addressed: smuxi,
> pidgin-libnotify and mopidy-mpris require changes to have libindicate
> removed from Debian.
If you do not intend to ship libindicate in buster, should the remaining
bugs
Processing commands for cont...@bugs.debian.org:
> tags 895599 + pending
Bug #895599 [ganeti] ganeti-2.15 - Fails to export vm: certificate is valid but
its commonName does not match hostname
Added tag(s) pending.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
On Sun, 2018-07-01 at 13:05 +, Santiago Vila wrote:
> Dear maintainer:
>
> I tried to build this package in stretch + security + stretch-
> proposed-updates but it failed:
Must be some very minor delta in the path. We don't really have any big
patches. I'll look into it over the weekend.
Processing control commands:
> tag -1 - patch
Bug #901462 [seabios] seabios: SeaBIOS fails to build from source on sid and
testing
Removed tag(s) patch.
--
901462: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=901462
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Control: tag -1 - patch
Apparently this is not so simple. As per upstream,
https://mail.coreboot.org/pipermail/seabios/2018-July/012353.html
- they say only particular versions of IASL produce correct code,
more recent IASL produces instructions not understood by older
OSes (which is what qemu
Control: tags -1 + patch
On Wed, 15 Nov 2017 at 18:16:17 +0100, Helmut Grohne wrote:
> | cp `pwd`/debian/mbr/sbin/install-mbr `pwd`/debian/mbr-udeb/sbin/
> | cp: cannot create regular file '/<>/debian/mbr-udeb/sbin/': No
> such file or directory
>
>
Processing control commands:
> tags -1 + patch
Bug #881835 [src:mbr] mbr FTBFS on !amd64 !i386: debhelper got stricter
Added tag(s) patch.
--
881835: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=881835
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Hi,
in fact, and regarding the package history, the bug should have been opened
with 2.3.10 and closed with not releases 2.3.15...
How to avoid this case becomes blocking for the migration to testing planned in
8 days now ?
Kind regards,
Guillaume Bougard
Ingénieur R
gboug...@teclib.com
Your message dated Mon, 2 Jul 2018 08:14:48 +0100
with message-id <20180702071448.ga7...@espresso.pseudorandom.co.uk>
and subject line Re: Bug#874526: Keyboard grab doesn't work under Wayland
has caused the Debian Bug report #874526,
regarding Keyboard grab doesn't work under Wayland
to be marked
Your message dated Mon, 02 Jul 2018 06:19:04 +
with message-id
and subject line Bug#902646: fixed in pexpect 4.6.0-1
has caused the Debian Bug report #902646,
regarding python3-pexpect: Failure to install with Python 3.7
to be marked as done.
This means that you claim that the problem has
80 matches
Mail list logo
