Processed: bug 936557 is forwarded to https://github.com/freeorion/freeorion/pull/2653

2020-04-30 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > forwarded 936557 https://github.com/freeorion/freeorion/pull/2653 Bug #936557 [src:freeorion] freeorion: Python2 removal in sid/bullseye Changed Bug forwarded-to-address to 'https://github.com/freeorion/freeorion/pull/2653' from 'https://freeori

Bug#956324: Clustalo bus error on mipsel (Was: Bug#956324: python-biopython: FTBFS on mipsel)

2020-04-30 Thread Andreas Tille
Hi Matthew, On Thu, Apr 30, 2020 at 05:53:29PM -0700, Matthew Fernandez wrote: > > Is the priority goal here to simply ship a non-crashing clustalo mipsel > binary that BioPython can depend on? If so, maybe we can just disable > compiler optimisation (-O0) and this may avoid provoking the bus e

Processed: your mail

2020-04-30 Thread Debian Bug Tracking System
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 ring/20190215.1.f

Bug#959201: Acknowledgement (jami-daemon: dring does not start due to a symbol lookup error)

2020-04-30 Thread Bruno Kleinert
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 _ZN4YAML6det

Bug#936723: marked as done (ifeffit: Python2 removal in sid/bullseye)

2020-04-30 Thread Debian Bug Tracking System
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 t

Bug#959157: fix for CVE-2020-1749 in linux-image-4.19.0-9 breaks wireguard

2020-04-30 Thread Jason A. Donenfeld
https://git.zx2c4.com/wireguard-linux-compat/commit/?id=4602590adee92557847e61c8cd14445d35fbfa2e

Bug#956324: Clustalo bus error on mipsel (Was: Bug#956324: python-biopython: FTBFS on mipsel)

2020-04-30 Thread Matthew Fernandez
> 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 stri

Processed: reassign 959157 to wireguard-dkms

2020-04-30 Thread Debian Bug Tracking System
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 wireguard/1.0.20200319-1~bpo1

Bug#937431: pyepl: Python2 removal in sid/bullseye

2020-04-30 Thread Yaroslav Halchenko
> > 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

Bug#955064: marked as done (grpc: FTBFS with Sphinx 2.4: distutils.errors.DistutilsError: Could not find suitable distribution for Requirement.parse('Sphinx~=1.8.1'))

2020-04-30 Thread Debian Bug Tracking System
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 Requirement.parse('Sphi

Bug#955064: Simply allowing any version of Sphinx in setup.py fixes the problem

2020-04-30 Thread GCS
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. Che

Bug#956324: Clustalo bus error on mipsel (Was: Bug#956324: python-biopython: FTBFS on mipsel)

2020-04-30 Thread Andreas Tille
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 err

Bug#955064: Simply allowing any version of Sphinx in setup.py fixes the problem

2020-04-30 Thread Thomas Goirand
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/changelog2020-03-21

Bug#958515: marked as done (diamond-aligner breaks proteinortho autopkgtest on arm64: Error: wrong fromat)

2020-04-30 Thread Debian Bug Tracking System
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 tha

Bug#958090: marked as done (diamond-aligner 0.9.31-1 fails on architectures where char is unsigned)

2020-04-30 Thread Debian Bug Tracking System
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 cl

Bug#937431: pyepl: Python2 removal in sid/bullseye

2020-04-30 Thread Moritz Muehlenhoff
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 bullsey

Bug#958802: marked as done (gap-float: please update for new GAP ABI)

2020-04-30 Thread Debian Bug Tracking System
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 deal

Bug#956324: Clustalo bus error on mipsel (Was: Bug#956324: python-biopython: FTBFS on mipsel)

2020-04-30 Thread Jeffrey Walton
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 https://salsa.debian.org/med-team/clustalo/-/blob/master/src/clustal/prog

Bug#958495: marked as done (gap-io: please update for new GAP ABI)

2020-04-30 Thread Debian Bug Tracking System
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 with

Bug#956371: marked as done (deal.ii: FTBFS with opencascade 7.4 (library transistion))

2020-04-30 Thread Debian Bug Tracking System
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

Bug#932197: Bug#937144: Request to join the Neurodebian group

2020-04-30 Thread Yaroslav Halchenko
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&heudiconv: I made it optional for previous version of the > > >

Bug#937431: pyepl: Python2 removal in sid/bullseye

2020-04-30 Thread Yaroslav Halchenko
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 be

Bug#958554: marked as done (beautifulsoup4: autopkgtest failure.)

2020-04-30 Thread Debian Bug Tracking System
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

Processed: Bug#958554 marked as pending in beautifulsoup4

2020-04-30 Thread Debian Bug Tracking System
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

Bug#958554: marked as pending in beautifulsoup4

2020-04-30 Thread Stefano Rivera
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: https://salsa.debian.org/python-team/modules/beautifulsoup4/-/commit/2afce5c

Bug#956324: Clustalo bus error on mipsel (Was: Bug#956324: python-biopython: FTBFS on mipsel)

2020-04-30 Thread Jeffrey Walton
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 debian/test

Processed: Re: Bug#958554: beautifulsoup4: autopkgtest failure.

2020-04-30 Thread Debian Bug Tracking System
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: https://bugs.debian.org/cgi

Bug#958554: beautifulsoup4: autopkgtest failure.

2020-04-30 Thread Stefano Rivera
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

Bug#959110: we need to run more scripts in Makefile than just gulp build

2020-04-30 Thread Pirate Praveen
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.

Bug#956324: Clustalo bus error on mipsel (Was: Bug#956324: python-biopython: FTBFS on mipsel)

2020-04-30 Thread Jeffrey Walton
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 ins

Bug#959202: src:php-defaults: fails to migrate to testing for too long

2020-04-30 Thread Paul Gevers
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 out-of-s

Processed: src:php-defaults: fails to migrate to testing for too long

2020-04-30 Thread Debian Bug Tracking System
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 -

Bug#959201: jami-daemon: dring does not start due to a symbol lookup error

2020-04-30 Thread Bruno Kleinert
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: _

Bug#950619: marked as done (dbus-c++ build depends on the removed libecore-dev)

2020-04-30 Thread Debian Bug Tracking System
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 b

Bug#951947: marked as done (decopy: FTBFS: dh_auto_test: error: pybuild --test -i python{version} -p "3.8 3.7" returned exit code 13)

2020-04-30 Thread Debian Bug Tracking System
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 do

Bug#932197: Bug#937144: Request to join the Neurodebian group

2020-04-30 Thread Moritz Mühlenhoff
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&heudiconv: I made it optional for previous version of the > > package: > > > > $> quilt series > > deb-no-de

Bug#937144: Bug#937769: getting python-linecache2/python-traceback2 fixes into testing (FAO traceback2, funcsigs nipype and numba maintainers).

2020-04-30 Thread Moritz Mühlenhoff
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 th

Bug#937431: pyepl: Python2 removal in sid/bullseye

2020-04-30 Thread Moritz Mühlenhoff
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 > Python2

Bug#950619: dbus-c++ build depends on the removed libecore-dev

2020-04-30 Thread peter green
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.

Bug#952689: libcddb2: freedb service is closing down

2020-04-30 Thread nito
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 i

Bug#956324: Clustalo bus error on mipsel (Was: Bug#956324: python-biopython: FTBFS on mipsel)

2020-04-30 Thread Andreas Tille
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

Processed: tagging 936251

2020-04-30 Thread Debian Bug Tracking System
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: https://bugs.debian.org/cgi-bin/bugrep

Bug#959193: libperl5i-perl: Test failures with Devel::Declare 0.006022-1

2020-04-30 Thread gregor herrmann
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

Bug#959189: bbswitch-dkms: fails to build for kernel 5.6.7

2020-04-30 Thread Luca Boccassi
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 thes

Processed: Re: Bug#959189: bbswitch-dkms: fails to build for kernel 5.6.7

2020-04-30 Thread Debian Bug Tracking System
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 wi

Bug#951151: marked as done (polymake: test failure on mips64el)

2020-04-30 Thread Debian Bug Tracking System
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. If

Processed: Re: Bug#956371: deal.ii: diff for NMU version 9.1.1-9.1

2020-04-30 Thread Debian Bug Tracking System
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 w

Bug#956371: deal.ii: diff for NMU version 9.1.1-9.1

2020-04-30 Thread Graham Inggs
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 up

Bug#959089: marked as done (localslackirc: missing build dependencies on python3-requests and python3-websocket)

2020-04-30 Thread Debian Bug Tracking System
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 th

Bug#959137: lasagne: (autopkgtest) needs update for new version of numpy: 'numpy.float64' object cannot be interpreted as an integer

2020-04-30 Thread Stephen Sinclair
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 bull

Bug#958446: nvidia-legacy-340xx-driver: Fails to build with kernel 5.6

2020-04-30 Thread jim_p
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 -

Bug#956324: Clustalo bus error on mipsel (Was: Bug#956324: python-biopython: FTBFS on mipsel)

2020-04-30 Thread Matthew Fernandez
> 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 sud

Processed: bug 954535 is forwarded to deve...@faert.net

2020-04-30 Thread Debian Bug Tracking System
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

Processed: Re: Bug#954762: systraq: Annoying as Hell

2020-04-30 Thread Debian Bug Tracking System
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: https://bugs.debian

Bug#958446: nvidia-legacy-340xx-driver: Fails to build with kernel 5.6

2020-04-30 Thread S R Wright
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.

Bug#958419: swi-prolog 8.1.29 in Debian

2020-04-30 Thread 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 the leading "swipl-" with "swi-prolog-abi-". I think adding

Bug#958419: swi-prolog 8.1.29 in Debian

2020-04-30 Thread Lev Lamberov
Чт 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 the

Bug#958419: swi-prolog-nox: compiler and runtime execution shipped in same package

2020-04-30 Thread Jonas Smedegaard
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 lot

Bug#958419: swi-prolog-nox: compiler and runtime execution shipped in same package

2020-04-30 Thread Jan Wielemaker
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 bundl

Processed: Re: 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).

2020-04-30 Thread Debian Bug Tracking System
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 versions

Bug#955694: 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).

2020-04-30 Thread Gilles Filippini
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. >> >> H

Bug#958419: swi-prolog 8.1.29 in Debian

2020-04-30 Thread Jonas Smedegaard
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 ca

Bug#958419: swi-prolog 8.1.29 in Debian

2020-04-30 Thread Lev Lamberov
Чт 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 "swi-

Bug#958419: swi-prolog 8.1.29 in Debian

2020-04-30 Thread 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 "swi-prolog" for Debian. --- Jan

Bug#959134: marked as done (astroml: (autopkgtest) needs update for new version of numpy: object of type cannot be safely interpreted as an integer)

2020-04-30 Thread Debian Bug Tracking System
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 integer

Processed: bug 959064 is forwarded to https://gitlab.kitware.com/cmake/cmake/-/issues/20652

2020-04-30 Thread Debian Bug Tracking System
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. Pleas

Bug#959064: ignition-transport FTBFS in testing.

2020-04-30 Thread Brad King
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 ignition-t

Processed: 936251 is fixed-upstream

2020-04-30 Thread Debian Bug Tracking System
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: https://bugs.debian.org/cgi-bin

Bug#958419: swi-prolog 8.1.29 in Debian

2020-04-30 Thread Lev Lamberov
Чт 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 generat

Bug#958419: swi-prolog 8.1.29 in Debian

2020-04-30 Thread Jonas Smedegaard
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 t

Bug#959176: gammu-smsd: cannot start (wrong path in systemd service file)

2020-04-30 Thread Raphaël Halimi
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 "${CMAKE_INST

Bug#958446: nvidia-legacy-340xx-driver: Fails to build with kernel 5.6

2020-04-30 Thread Andreas Beckmann
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

Bug#958419: swi-prolog 8.1.29 in Debian

2020-04-30 Thread 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 generates this hash. What kind of > >> support would be

Bug#954554: python-asynctest: FTBFS: tests failed

2020-04-30 Thread Jonas Smedegaard
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, fro

Bug#958419: swi-prolog 8.1.29 in Debian

2020-04-30 Thread Lev Lamberov
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 woul

Bug#958446: nvidia-legacy-340xx-driver: Fails to build with kernel 5.6

2020-04-30 Thread jim_p
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,

Bug#958495: Fwd: gap-io: please update for new GAP ABI

2020-04-30 Thread Bill Allombert
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

Bug#958419: swi-prolog 8.1.29 in Debian

2020-04-30 Thread 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 would be needed from SWI-Prolog to make this work? Some script

Processed: unarchiving 759410, fixed 759410 in 0.12-2+deb9u1

2020-04-30 Thread Debian Bug Tracking System
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] Sh

Bug#958446: marked as done (nvidia-legacy-340xx-driver: Fails to build with kernel 5.6)

2020-04-30 Thread Debian Bug Tracking System
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 nvidia-legacy-340xx-d

Processed: Re: Bug#954554: python-asynctest: FTBFS: tests failed

2020-04-30 Thread Debian Bug Tracking System
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

Processed: closing 958571

2020-04-30 Thread Debian Bug Tracking System
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: https://bugs.debian.org/cgi-bin/bugre

Bug#954554: python-asynctest: FTBFS: tests failed

2020-04-30 Thread Andrej Shadura
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 be

Bug#958571: hypercorn build-depends on package that is not in testing.

2020-04-30 Thread Andrej Shadura
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 to

Processed: Re: hypercorn build-depends on package that is not in testing.

2020-04-30 Thread Debian Bug Tracking System
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.

Bug#956324: Clustalo bus error on mipsel (Was: Bug#956324: python-biopython: FTBFS on mipsel)

2020-04-30 Thread Andreas Tille
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 >