Processing commands for cont...@bugs.debian.org:
> reassign 959201 libyaml-cpp0.6 0.6.3-1
Bug #959201 [jami-daemon] jami-daemon: dring does not start due to a symbol
lookup error
Bug reassigned from package 'jami-daemon' to 'libyaml-cpp0.6'.
No longer marked as found in versions
Hi,
the cause seems to be an ABI change in /usr/lib/x86_64-linux-
gnu/libyaml-cpp.so.0.6.3 in package libyaml-cpp0.6 between versions
0.6.2-4 and 0.6.3-1:
While 0.6.2-4 exported
0006bd60 B _ZN4YAML6detail9node_data12empty_scalarB5cxx11E
0.6.3-1 now exports
00029af0 T
Your message dated Fri, 01 May 2020 14:30:24 +1000
with message-id <58836028.v9rg4Cycpm@simurgh>
and subject line Re: Bug#936723: ifeffit: Python2 removal in sid/bullseye
has caused the Debian Bug report #936723,
regarding ifeffit: Python2 removal in sid/bullseye
to be marked as done.
This means
https://git.zx2c4.com/wireguard-linux-compat/commit/?id=4602590adee92557847e61c8cd14445d35fbfa2e
> One small issue... Valgrind recommends -O0 or -O1
TIL :) Thanks, Jeff!
> You can sometimes locate a bus error at build time with -Wcast-align.
> At runtime you can usually locate them with -fsanitize=undefined.
I had previously tried UBSan and, while it turned up a number of shifting and
Processing commands for cont...@bugs.debian.org:
> reassign 959157 wireguard-dkms
Bug #959157 [wireguard] fix for CVE-2020-1749 in linux-image-4.19.0-9 breaks
wireguard
Bug reassigned from package 'wireguard' to 'wireguard-dkms'.
No longer marked as found in versions
> > yes, AFAIK it is dead. Let's RM. you ? me ? ;)
> Please go ahead :-)
FTR #959213
--
Yaroslav O. Halchenko
Center for Open Neuroscience http://centerforopenneuroscience.org
Dartmouth College, 419 Moore Hall, Hinman Box 6207, Hanover, NH 03755
Phone: +1 (603) 646-9834
Your message dated Thu, 30 Apr 2020 22:05:15 +
with message-id
and subject line Bug#955064: fixed in grpc 1.26.0-3
has caused the Debian Bug report #955064,
regarding grpc: FTBFS with Sphinx 2.4: distutils.errors.DistutilsError: Could
not find suitable distribution for
Hi Thomas,
On Thu, Apr 30, 2020 at 11:03 PM Thomas Goirand wrote:
> Attached debdiff fixes the issue. Can I NMU it? A bunch of the OpenStack
> packages that I maintain will otherwise be auto-removed soon...
Thanks, but I've the same in the queue. Uploading shortly not to risk
your packages.
Hi Jeffrey,
thanks a lot for this analysis. Any chance that somebody could
turn this into a patch I could try?
Kind regards
Andreas.
On Thu, Apr 30, 2020 at 03:40:12PM -0400, Jeffrey Walton wrote:
> On Fri, Apr 17, 2020 at 7:21 AM Andreas Tille wrote:
> > ...
> > So it seems the bus
Hi Laszlo,
Attached debdiff fixes the issue. Can I NMU it? A bunch of the OpenStack
packages that I maintain will otherwise be auto-removed soon...
Cheers,
Thomas Goirand (zigo)
diff -Nru grpc-1.26.0/debian/changelog grpc-1.26.0/debian/changelog
--- grpc-1.26.0/debian/changelog
Your message dated Thu, 30 Apr 2020 20:35:42 +
with message-id
and subject line Bug#958515: fixed in diamond-aligner 0.9.32-2
has caused the Debian Bug report #958515,
regarding diamond-aligner breaks proteinortho autopkgtest on arm64: Error:
wrong fromat
to be marked as done.
This means
Your message dated Thu, 30 Apr 2020 20:35:42 +
with message-id
and subject line Bug#958090: fixed in diamond-aligner 0.9.32-2
has caused the Debian Bug report #958090,
regarding diamond-aligner 0.9.31-1 fails on architectures where char is unsigned
to be marked as done.
This means that you
On Thu, Apr 30, 2020 at 03:06:57PM -0400, Yaroslav Halchenko wrote:
>
> On Thu, 30 Apr 2020, Moritz Mühlenhoff wrote:
>
> > On Fri, Aug 30, 2019 at 07:33:35AM +, Matthias Klose wrote:
> > > Package: src:pyepl
> > > Version: 1.1.0+git12-g365f8e3-3
> > > Severity: normal
> > > Tags: sid
Your message dated Thu, 30 Apr 2020 19:48:45 +
with message-id
and subject line Bug#958802: fixed in gap-float 0.9.1+ds-6
has caused the Debian Bug report #958802,
regarding gap-float: please update for new GAP ABI
to be marked as done.
This means that you claim that the problem has been
On Fri, Apr 17, 2020 at 7:21 AM Andreas Tille wrote:
> ...
> So it seems the bus error occures somehow here:
>
>
> https://salsa.debian.org/med-team/clustalo/-/blob/master/src/clustal/pair_dist.c#L346
NewProgress is at
Your message dated Thu, 30 Apr 2020 19:34:19 +
with message-id
and subject line Bug#958495: fixed in gap-io 4.7.0+ds-2
has caused the Debian Bug report #958495,
regarding gap-io: please update for new GAP ABI
to be marked as done.
This means that you claim that the problem has been dealt
Your message dated Thu, 30 Apr 2020 19:33:48 +
with message-id
and subject line Bug#956371: fixed in deal.ii 9.1.1-10
has caused the Debian Bug report #956371,
regarding deal.ii: FTBFS with opencascade 7.4 (library transistion)
to be marked as done.
This means that you claim that the problem
On Thu, 30 Apr 2020, Moritz Mühlenhoff wrote:
> On Wed, Feb 26, 2020 at 04:15:03PM +0100, Andreas Tille wrote:
> > On Wed, Feb 26, 2020 at 08:37:30AM -0500, Yaroslav Halchenko wrote:
> > > thank you Andreas!!!
> > > re etelemetry: I made it optional for previous version of the
> > > package:
On Thu, 30 Apr 2020, Moritz Mühlenhoff wrote:
> On Fri, Aug 30, 2019 at 07:33:35AM +, Matthias Klose wrote:
> > Package: src:pyepl
> > Version: 1.1.0+git12-g365f8e3-3
> > Severity: normal
> > Tags: sid bullseye
> > User: debian-pyt...@lists.debian.org
> > Usertags: py2removal
> > Python2
Your message dated Thu, 30 Apr 2020 19:03:26 +
with message-id
and subject line Bug#958554: fixed in beautifulsoup4 4.9.0-2
has caused the Debian Bug report #958554,
regarding beautifulsoup4: autopkgtest failure.
to be marked as done.
This means that you claim that the problem has been dealt
Processing control commands:
> tag -1 pending
Bug #958554 [src:beautifulsoup4] beautifulsoup4: autopkgtest failure.
Added tag(s) pending.
--
958554: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=958554
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Control: tag -1 pending
Hello,
Bug #958554 in beautifulsoup4 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:
On Fri, Apr 17, 2020 at 7:21 AM Andreas Tille wrote:
>
> Control: tags -1 help
>
> as it can be seen on the recent build log of clustalo on mips[1] the
> build fails with
>
> # Run additional test from python-biopython package to verify that
> # this will work as well
> src/clustalo -i
Processing control commands:
> forwarded -1 https://bugs.launchpad.net/beautifulsoup/+bug/1872279
Bug #958554 [src:beautifulsoup4] beautifulsoup4: autopkgtest failure.
Set Bug forwarded-to-address to
'https://bugs.launchpad.net/beautifulsoup/+bug/1872279'.
--
958554:
Control: forwarded -1 https://bugs.launchpad.net/beautifulsoup/+bug/1872279
> From diffing test logs I belive this was most-likely caused by the
> update to python-soupsieve
Yep.
SR
--
Stefano Rivera
http://tumbleweed.org.za/
+1 415 683 3272
at least packages/babel-plugin-transform-runtime/scripts/build-dist.js
should be run during build to fix this.
I think it is safer to run make build.
On Thu, Apr 30, 2020 at 10:33 AM Matthew Fernandez
wrote:
>
> > On Apr 30, 2020, at 00:31, Andreas Tille wrote:
> >
> > On Wed, Apr 29, 2020 at 05:51:26PM -0700, Matthew Fernandez wrote:
> >
> >> The other option I suggested was Valgrind, but if you can’t run apt-file
> >> you probably can’t
Source: php-defaults
Version: 73
Severity: serious
Control: close -1 75
Tags: sid bullseye
User: release.debian@packages.debian.org
Usertags: out-of-sync
Control: block -1 by 958423 958424
Dear maintainer(s),
As recently announced [1], the Release Team now considers packages that
are
Processing control commands:
> close -1 75
Bug #959202 [src:php-defaults] src:php-defaults: fails to migrate to testing
for too long
Marked as fixed in versions php-defaults/75.
Bug #959202 [src:php-defaults] src:php-defaults: fails to migrate to testing
for too long
Marked Bug as done
> block
Package: jami-daemon
Version: 20190215.1.f152c98~ds1-1+b1
Severity: grave
Justification: renders package unusable
Hi,
Jami fails to connect to its daemon dring because it cannot start due to a
symbol lookup error:
/usr/lib/ring/dring: symbol lookup error: /usr/lib/ring/dring: undefined
symbol:
Your message dated Thu, 30 Apr 2020 18:03:40 +
with message-id
and subject line Bug#950619: fixed in dbus-c++ 0.9.0-8.2
has caused the Debian Bug report #950619,
regarding dbus-c++ build depends on the removed libecore-dev
to be marked as done.
This means that you claim that the problem has
Your message dated Thu, 30 Apr 2020 18:03:45 +
with message-id
and subject line Bug#951947: fixed in decopy 0.2.4.2-1
has caused the Debian Bug report #951947,
regarding decopy: FTBFS: dh_auto_test: error: pybuild --test -i python{version}
-p "3.8 3.7" returned exit code 13
to be marked as
On Wed, Feb 26, 2020 at 04:15:03PM +0100, Andreas Tille wrote:
> On Wed, Feb 26, 2020 at 08:37:30AM -0500, Yaroslav Halchenko wrote:
> > thank you Andreas!!!
> >
> > re etelemetry: I made it optional for previous version of the
> > package:
> >
> > $> quilt series
> >
On Mon, Apr 20, 2020 at 09:57:30AM +0200, Thomas Goirand wrote:
> On 4/20/20 4:36 AM, peter green wrote:
>
> Funcsigs is a backport of the PEP 362 function signature features from
> Python 3.3's inspect module. Python 2 has never been removed from this
> package. Though instead, we shall remove
On Fri, Aug 30, 2019 at 07:33:35AM +, Matthias Klose wrote:
> Package: src:pyepl
> Version: 1.1.0+git12-g365f8e3-3
> Severity: normal
> Tags: sid bullseye
> User: debian-pyt...@lists.debian.org
> Usertags: py2removal
>
> Python2 becomes end-of-live upstream, and Debian aims to remove
>
Looking at the changelog for efl, the maintainer decided to give up on dev
packages for the individual libraries and only provide one dev package (
libefl-all-dev ) for all the efl libraries. Transitional packages were provided
for the buster release, but have now been dropped in bullseye/sid.
On Thu, 27 Feb 2020 16:19:48 +0100 Andreas Ronnquist
wrote:> Package: libcddb2
> Version: 1.3.2-6+b1
> Severity: important
>
> Dear Maintainer,
>
> According to a notice on https://freedb.org, that service is closing
> down. I assume that libcddb is using that server, and only that -
> please
On Thu, Apr 30, 2020 at 07:17:50AM -0700, Matthew Fernandez wrote:
>
> Valgrind, in its default mode, checks for a variety of memory issues
> (use-after-free, write out-of bounds, …). You don’t need any special
> configure/build options, but you probably want to enable debug symbols
> (`export
Processing commands for cont...@bugs.debian.org:
> tags 936251 - fixed-upstream
Bug #936251 [src:bup] bup: Python2 removal in sid/bullseye
Removed tag(s) fixed-upstream.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
936251:
Source: libperl5i-perl
Version: 2.13.2-1
Severity: serious
Tags: upstream ftbfs sid bullseye
Justification: fails to build from source (but built successfully in the past)
Forwarded: https://rt.cpan.org/Public/Bug/Display.html?id=131226
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
As noted on
On Thu, 2020-04-30 at 17:14 +0200, Andreas Beckmann wrote:
> Control: severity -1 serious
>
> On 30/04/2020 16.54, Giacomo Mulas wrote:
> > ./include/linux/proc_fs.h:64:24: note: expected ‘const struct proc_ops *’
> > but argument is of type ‘struct file_operations *’
>
> OK, another one of
Processing control commands:
> severity -1 serious
Bug #959189 [bbswitch-dkms] bbswitch-dkms: fails to build for kernel 5.6.7
Severity set to 'serious' from 'important'
--
959189: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=959189
Debian Bug Tracking System
Contact ow...@bugs.debian.org
Your message dated Thu, 30 Apr 2020 14:35:24 +
with message-id
and subject line Bug#951151: fixed in polymake 4.0r1-1
has caused the Debian Bug report #951151,
regarding polymake: test failure on mips64el
to be marked as done.
This means that you claim that the problem has been dealt with.
Processing control commands:
> tags -1 + fixed-upstream
Bug #956371 [src:deal.ii] deal.ii: FTBFS with opencascade 7.4 (library
transistion)
Added tag(s) fixed-upstream.
--
956371: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=956371
Debian Bug Tracking System
Contact ow...@bugs.debian.org
Control: tags -1 + fixed-upstream
Hi Tobias
On Wed, 29 Apr 2020 at 21:39, Tobias Frost wrote:
> I've prepared an NMU for deal.ii (versioned as 9.1.1-9.1) and
> uploaded it to DELAYED/5. Please feel free to tell me if I
> should delay it longer.
Mattias Maier pointed out this is already fixed
Your message dated Thu, 30 Apr 2020 14:34:03 +
with message-id
and subject line Bug#959089: fixed in localslackirc 1.9-2
has caused the Debian Bug report #959089,
regarding localslackirc: missing build dependencies on python3-requests and
python3-websocket
to be marked as done.
This means
The package has been updated in salsa and is awaiting sponsorship.
regards,
Steve
On Wed, Apr 29, 2020 at 9:48 PM Paul Gevers wrote:
>
> Source: lasagne
> Version: 0.1+git20181019.a61b76f-2
> Severity: serious
> X-Debbugs-CC: debian...@lists.debian.org, nu...@packages.debian.org
> Tags: sid
Package: nvidia-legacy-340xx-driver
Followup-For: Bug #958446
It works! I noticed that 5.6 reached unstable today, so I tried it asap.
The driver compiles as it should, 3d acceleration works, vdpau works, even the
temperatures work!
Thank you for everything :)
-- Package-specific info:
uname
> On Apr 30, 2020, at 00:31, Andreas Tille wrote:
>
> On Wed, Apr 29, 2020 at 05:51:26PM -0700, Matthew Fernandez wrote:
>
>> The other option I suggested was Valgrind, but if you can’t run apt-file you
>> probably can’t install Valgrind either.
>
> Well, I guess apt-get is permitted for
Processing commands for cont...@bugs.debian.org:
> forwarded 954535 deve...@faert.net
Bug #954535 [src:guymager] guymager: FTBFS: aewf.cpp:143:12: error: flexible
array member ‘::OffsetArr’ not at end of ‘struct’
Bug #957321 [src:guymager] guymager: ftbfs with GCC-10
Set Bug forwarded-to-address
Processing commands for cont...@bugs.debian.org:
> severity 954762 normal
Bug #954762 {Done: Juhani Numminen } [systraq]
systraq: Annoying as Hell
Severity set to 'normal' from 'critical'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
954762:
DKMS works for me using kernel 5.6.8 -- sRw
On 2020-04-30 06:09, Andreas Beckmann wrote:
On 30/04/2020 12.09, jim_p wrote:
And then the reference to #956458, which is for nvidia legacy 390xx.
So I would like to ask if the bug I mentioned here is indeed fixed in the -5
revision of the package.
On 4/30/20 2:50 PM, Jonas Smedegaard wrote:
Quoting Lev Lamberov (2020-04-30 14:40:53)
Чт 30 апр 2020 @ 14:06 Jan Wielemaker :
On 4/30/20 1:41 PM, Jonas Smedegaard wrote:
I think we can use the format almost as-is - just replacing the
leading "swipl-" with "swi-prolog-abi-".
I think adding
Чт 30 апр 2020 @ 14:56 Jan Wielemaker :
> On 4/30/20 2:50 PM, Jonas Smedegaard wrote:
>> Quoting Lev Lamberov (2020-04-30 14:40:53)
>>> Чт 30 апр 2020 @ 14:06 Jan Wielemaker :
>>>
On 4/30/20 1:41 PM, Jonas Smedegaard wrote:
> I think we can use the format almost as-is - just replacing
Quoting Jan Wielemaker (2020-04-30 14:40:58)
> In theory we could have a package that merely contains /usr/bin/swipl
> and /usr/lib/libswipl.so.8.2.0. That is enough to run saved states
> (provided they have been built such that no dependencies need to be
> loaded at runtime) and is indeed a
Hi Jonas,
In theory we could have a package that merely contains /usr/bin/swipl
and /usr/lib/libswipl.so.8.2.0. That is enough to run saved states
(provided they have been built such that no dependencies need to be
loaded at runtime) and is indeed a lot smaller than swi-prolog-nox.
Possibly
Processing control commands:
> found -1 5.5.2-4
Bug #955694 {Done: Julien Puydt } [src:scilab] scilab:
FTBFS: Scilab cannot create Scilab Java Main-Class (we have not been able to
find the main Scilab class. Check if the Scilab and thirdparty packages are
available).
Marked as found in
Control: found -1 5.5.2-4
Control: found -1 6.0.1-10
Julien Puydt a écrit le 23/04/2020 à 09:37 :
> Hi,
>
> Le jeudi 23 avril 2020 à 00:20 +0200, Gilles Filippini a écrit :
>> Gilles Filippini a écrit le 22/04/2020 à 09:59 :
>>> I think I've eventually found a fix for Scilab. Please hold.
>>
>>
Quoting Lev Lamberov (2020-04-30 14:40:53)
> Чт 30 апр 2020 @ 14:06 Jan Wielemaker :
>
> > On 4/30/20 1:41 PM, Jonas Smedegaard wrote:
> >> I think we can use the format almost as-is - just replacing the
> >> leading "swipl-" with "swi-prolog-abi-".
> >
> > I think adding "abi" makes sense. I
Чт 30 апр 2020 @ 14:06 Jan Wielemaker :
> On 4/30/20 1:41 PM, Jonas Smedegaard wrote:
>> I think we can use the format almost as-is - just replacing the leading
>> "swipl-" with "swi-prolog-abi-".
>
> I think adding "abi" makes sense. I can replace "swipl" with the
> package name, which is
On 4/30/20 1:41 PM, Jonas Smedegaard wrote:
I think we can use the format almost as-is - just replacing the leading
"swipl-" with "swi-prolog-abi-".
I think adding "abi" makes sense. I can replace "swipl" with the
package name, which is "swi-prolog" for Debian.
--- Jan
Your message dated Thu, 30 Apr 2020 12:18:26 +
with message-id
and subject line Bug#959134: fixed in astroml 0.4.post1-6
has caused the Debian Bug report #959134,
regarding astroml: (autopkgtest) needs update for new version of numpy: object
of type cannot be safely interpreted as an
Processing commands for cont...@bugs.debian.org:
> forwarded 959064 https://gitlab.kitware.com/cmake/cmake/-/issues/20652
Bug #959064 [cmake] cmake breaks on -isystem
Set Bug forwarded-to-address to
'https://gitlab.kitware.com/cmake/cmake/-/issues/20652'.
> thanks
Stopping processing here.
On 4/29/2020 10:40 PM, peter green wrote:
The behavior of pkg-config has changed
This lets though a -isystem parameter with a space which was previously
suppressed
And the space in said parameter breaks cmake.
I think cmake should handle -isystem¹ and as this is reproducible without
Processing commands for cont...@bugs.debian.org:
> tags 936251 + fixed-upstream
Bug #936251 [src:bup] bup: Python2 removal in sid/bullseye
Added tag(s) fixed-upstream.
>
End of message, stopping processing here.
Please contact me if you need assistance.
--
936251:
Чт 30 апр 2020 @ 12:42 Jonas Smedegaard :
> Quoting Jan Wielemaker (2020-04-30 11:40:32)
>> On 4/28/20 5:26 PM, Jonas Smedegaard wrote:
>> > Quoting Jan Wielemaker (2020-04-28 16:56:30)
>>
>> >> That is worth a try. I guess that implies that generating
>> >> SWI-Prolog (as package) also
Quoting Lev Lamberov (2020-04-30 12:16:31)
> Чт 30 апр 2020 @ 11:40 Jan Wielemaker :
> > On 4/28/20 5:26 PM, Jonas Smedegaard wrote:
> >> Quoting Jan Wielemaker (2020-04-28 16:56:30)
> >
> >>> That is worth a try. I guess that implies that generating
> >>> SWI-Prolog (as package) also generates
Package: gammu-smsd
Version: 1.41.0-1
Severity: grave
Tags: patch
Dear maintainer,
The current version (1.41.0-1) of gammu-smsd cannot start the service
because the systemd service file installed in the package uses cmake
substitutions, so instead of "/usr/bin", the service file has
On 30/04/2020 12.09, jim_p wrote:
> And then the reference to #956458, which is for nvidia legacy 390xx.
> So I would like to ask if the bug I mentioned here is indeed fixed in the -5
> revision of the package. I can't test it right now, but I probably will
> tomorrow or on Saturday.
I backported
Quoting Jan Wielemaker (2020-04-30 11:40:32)
> On 4/28/20 5:26 PM, Jonas Smedegaard wrote:
> > Quoting Jan Wielemaker (2020-04-28 16:56:30)
>
> >> That is worth a try. I guess that implies that generating
> >> SWI-Prolog (as package) also generates this hash. What kind of
> >> support would
Quoting Andrej Shadura (2020-04-30 10:36:45)
> Control: tag -1 patch
>
> On Tue, 31 Mar 2020 11:39:34 +0200 Jonas Smedegaard wrote:
> > Control: https://github.com/Martiusweb/asynctest/issues/132
>
> The upstream issue has a patch fixing the issue that still has not been
> applied upstream,
Hi,
Чт 30 апр 2020 @ 11:40 Jan Wielemaker :
> Hi Jonas,
>
> On 4/28/20 5:26 PM, Jonas Smedegaard wrote:
>> Quoting Jan Wielemaker (2020-04-28 16:56:30)
>
>>> That is worth a try. I guess that implies that generating SWI-Prolog
>>> (as package) also generates this hash. What kind of support
Package: nvidia-legacy-340xx-driver
Version: 340.108-4
Followup-For: Bug #958446
Dear Maintainer,
I just got the email that the bug was closed and I got really happy! Then I
checked the report here and I noticed this bit
Closed the wrong bug in the upload ...
And then the reference to #956458,
On Thu, Apr 30, 2020 at 10:35:49AM +0400, Jerome BENOIT wrote:
> Dear Bill, thanks for your message.
Hello Jerome
> I understand that GAP comes now with an official ABI.
Yes, one for gap-core which is gap-kernel-7,
and one for libgap which is libgap7, but they should be
compatible.
> Currently
Hi Jonas,
On 4/28/20 5:26 PM, Jonas Smedegaard wrote:
Quoting Jan Wielemaker (2020-04-28 16:56:30)
That is worth a try. I guess that implies that generating SWI-Prolog
(as package) also generates this hash. What kind of support would be
needed from SWI-Prolog to make this work? Some
Processing commands for cont...@bugs.debian.org:
> unarchive 759410
Bug #759410 {Done: Francois Marier } [safe-rm] Should not
install /usr/bin/rm conflicting with /bin/rm (blocks /bin -> /usr/bin)
Unarchived Bug 759410
> fixed 759410 0.12-2+deb9u1
Bug #759410 {Done: Francois Marier } [safe-rm]
Your message dated Thu, 30 Apr 2020 11:38:03 +0200
with message-id <5a8ca749-5e29-4255-d7c7-d7f9a7f7e...@debian.org>
and subject line Fwd:
nvidia-graphics-drivers-legacy-340xx_340.108-5_source.changes ACCEPTED into
unstable
has caused the Debian Bug report #958446,
regarding
Processing control commands:
> tag -1 patch
Bug #954554 [src:python-asynctest] python-asynctest: incompatible with Python
3.8
Added tag(s) patch.
--
954554: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954554
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processing commands for cont...@bugs.debian.org:
> close 958571
Bug #958571 [src:hypercorn] hypercorn build-depends on package that is not in
testing.
Marked Bug as done
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
958571:
Control: tag -1 patch
On Tue, 31 Mar 2020 11:39:34 +0200 Jonas Smedegaard wrote:
Control: https://github.com/Martiusweb/asynctest/issues/132
The upstream issue has a patch fixing the issue that still has not been
applied upstream, from my understanding of the code it seems sane enough
to
notfound 958571 0.9.4-1
thanks
On Thu, 23 Apr 2020 21:09:46 +0100 peter green wrote:
hypercorn build-depends on python3-uvloop which is not available in testing due
to https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=950165 . Either uvloop
needs to be fixed, hypercorn needs to be modified
Processing commands for cont...@bugs.debian.org:
> notfound 958571 0.9.4-1
Bug #958571 [src:hypercorn] hypercorn build-depends on package that is not in
testing.
No longer marked as found in versions hypercorn/0.9.4-1.
> thanks
Stopping processing here.
Please contact me if you need assistance.
Hi Matthew,
On Wed, Apr 29, 2020 at 05:51:26PM -0700, Matthew Fernandez wrote:
> > Any more help from debian-mipsel is really appreciated.
>
> Hm yes, “--disable-libsanitizer” is rather ominous. I guess the mipsel GCC
> package has been built without ASan support. Surprising that it fails so
>
Dear Bill, thanks for your message.
I understand that GAP comes now with an official ABI.
Currently the package gap-io depends for building on gap and gap-dev,
while the package itseld depends only on gap.
You asked to make it depends on gap-kernel-7.
My understanding is that gap-kernel-7 is
85 matches
Mail list logo
