Processed: Re: Bug#921257: khal: FTBFS randomly when built with eatmydata and overlayfs

2020-04-22 Thread Debian Bug Tracking System
Processing control commands: > retitle -1 khal: FTBFS randomly when built Bug #921257 [src:khal] khal: FTBFS randomly when built with eatmydata and overlayfs Changed Bug title to 'khal: FTBFS randomly when built' from 'khal: FTBFS randomly when built with eatmydata and overlayfs'. > severity -1

Bug#953144: origami install fails with "ERROR: WGET RETRIEVAL FAILED!"

2020-04-22 Thread Scott Baer
On Sat, 07 Mar 2020 23:35:29 +0100 Andreas Beckmann wrote: > Followup-For: Bug #953144 > > origami is missing a dependency on lsb-release (needed for os > identification). > > The URL https://zelut.org/projects/misc/finstall is no longer available > and causes the reported error. > > There is no

Processed: Tag bug

2020-04-22 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tag 951891 + help Bug #951891 [src:open-ath9k-htc-firmware] open-ath9k-htc-firmware FTBFS with binutils 2.34 Added tag(s) help. > thanks Stopping processing here. Please contact me if you need assistance. -- 951891:

Processed: severity of 956959 is normal, tagging 956959

2020-04-22 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > severity 956959 normal Bug #956959 [xpra] can no longer connect after dist-upgrading server Severity set to 'normal' from 'grave' > tags 956959 + unreproducible moreinfo Bug #956959 [xpra] can no longer connect after dist-upgrading server Added

Bug#952022: marked as done (ruby-puppet-syntax: FTBFS: ERROR: Test "ruby2.7" failed: LoadError:)

2020-04-22 Thread Debian Bug Tracking System
Your message dated Wed, 22 Apr 2020 23:33:38 + with message-id and subject line Bug#952022: fixed in ruby-puppet-syntax 2.6.1-2 has caused the Debian Bug report #952022, regarding ruby-puppet-syntax: FTBFS: ERROR: Test "ruby2.7" failed: LoadError: to be marked as done. This means that you

Bug#958499: eclipse: fails to launch

2020-04-22 Thread Mark Lehky
Package: eclipse Version: 3.8.1-11 Severity: grave Justification: renders package unusable Dear Maintainer, * What led up to the situation? 1. `sudo apt install eclipse` 2. Launch Eclipse from the menu or from commandline. 3. I get 'An error has occurred.' There is a log generated: !SESSION

Bug#958497: geoclue-2.0 violates GDPR

2020-04-22 Thread Heinrich Schuchardt
Package: geoclue-2.0 Version: 2.5.6-1 Severity: serious The geoclue package collects SSIDs in the neighborhood and sends them to Mozilla location services. The SSID of an adhoc network (which for instance is set up for tethering via a mobile phone) is personally identifiable information. Sending

Bug#956598: marked as done (ruby-combustion autopkgtest is failing with NoMethodError: undefined method `expect' for #)

2020-04-22 Thread Debian Bug Tracking System
Your message dated Wed, 22 Apr 2020 22:49:06 + with message-id and subject line Bug#956598: fixed in ruby-combustion 1.1.1-3 has caused the Debian Bug report #956598, regarding ruby-combustion autopkgtest is failing with NoMethodError: undefined method `expect' for # to be marked as done.

Bug#953537: Goffredo's patch

2020-04-22 Thread Joseph Carter
I'm curious if there's some problem with Goffredo's patch which hasn't been acknowledged. (In fact the bug itself hasn't been.) This is a grave functionality bug rendering the package uninstallable for all users upgrading from an installation of Buster. Certainly sid is sid, but as it required

Bug#956598: marked as pending in ruby-combustion

2020-04-22 Thread Daniel Leidert
Control: tag -1 pending Hello, Bug #956598 in ruby-combustion 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:

Processed: Bug#956598 marked as pending in ruby-combustion

2020-04-22 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #956598 [ruby-combustion] ruby-combustion autopkgtest is failing with NoMethodError: undefined method `expect' for # Added tag(s) pending. -- 956598: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=956598 Debian Bug Tracking System Contact

Bug#958496: python3-m2crypto: broken by Python3.8 - python3.8 http.client module expects that m2crypto handles short read

2020-04-22 Thread Norbert Preining
Package: python3-m2crypto Version: 0.31.0-9+b1 Severity: grave Justification: renders package unusable Dear maintainer, >From https://gitlab.com/m2crypto/m2crypto/-/merge_requests/242: In python3.8 the fp is wrapped in a Buffer. SSL.Connection.makefile returns a socketIO which is

Processed: closing 953689

2020-04-22 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > close 953689 Bug #953689 [src:rust-enum-as-inner] src:rust-enum-as-inner: fails to migrate to testing for too long Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 953689:

Processed: closing 953690

2020-04-22 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > close 953690 Bug #953690 {Done: Ximin Luo } [src:rust-cpp-demangle] src:rust-cpp-demangle: fails to migrate to testing for too long Bug 953690 is already marked as done; not doing anything. > thanks Stopping processing here. Please contact me

Processed: closing 953179

2020-04-22 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > close 953179 Bug #953179 [src:rust-glob] src:rust-glob: fails to migrate to testing for too long Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 953179:

Processed: closing 953688

2020-04-22 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > close 953688 Bug #953688 [src:rust-tempfile] src:rust-tempfile: fails to migrate to testing for too long Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 953688:

Processed: closing 953690

2020-04-22 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > close 953690 Bug #953690 [src:rust-cpp-demangle] src:rust-cpp-demangle: fails to migrate to testing for too long Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 953690:

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-22 Thread Debian Bug Tracking System
Processing control commands: > tag -1 + patch Bug #955694 [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). Added tag(s) patch. -- 955694:

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-22 Thread Gilles Filippini
Control: tag -1 + patch Gilles Filippini a écrit le 22/04/2020 à 19:35 : > Gilles Filippini a écrit le 22/04/2020 à 09:59 : >> Hi, >> >> Matthias Klose a écrit le 20/04/2020 à 12:49 : >>> On 4/20/20 11:52 AM, Gilles Filippini wrote: I'd like to do a bisect between openjdk-11 11.0.6+10-2 and

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

2020-04-22 Thread Bill Allombert
Package: gap-io Version: 4.7.0+ds-1 Severity: serious Dear Debian Science Maintainers, Please update gap-io for the new GAP ABI. 1) GAP 4.11.0 includes libgap7, libgap-dev as a normal Debian shared library package. 2) There is now an officially supported ABI for the GAP kernel. the current

Bug#958430: closing 958430

2020-04-22 Thread Emmanuel Kasper
close 958430 # error on user side, the libvirt box is fine. thanks

Bug#955078: marked as done (aodh: FTBFS with Sphinx 2.4: AttributeError: 'Sphinx' object has no attribute 'info')

2020-04-22 Thread Debian Bug Tracking System
Your message dated Wed, 22 Apr 2020 23:19:52 +0200 with message-id <2d0a2ed9-985d-6802-db77-bf3d64125...@debian.org> and subject line Issue was in sphinxcontrib-pecanwsme has caused the Debian Bug report #955078, regarding aodh: FTBFS with Sphinx 2.4: AttributeError: 'Sphinx' object has no

Processed: closing 958430

2020-04-22 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > close 958430 Bug #958430 [cloud.debian.org] Vagrant libvirt image debian/buster64 version 10.3.0 grub error Marked Bug as done > # error on user side, the libvirt box is fine. > thanks Stopping processing here. Please contact me if you need

Processed: tagging 958430

2020-04-22 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 958430 + unreproducible Bug #958430 [cloud.debian.org] Vagrant libvirt image debian/buster64 version 10.3.0 grub error Added tag(s) unreproducible. > thanks Stopping processing here. Please contact me if you need assistance. -- 958430:

Bug#958430: Vagrant libvirt

2020-04-22 Thread Emmanuel Kasper
> Call to virDomainCreateWithFlags failed: internal error: process > exited while connecting to monitor: ioctl(KVM_CREATE_VM) failed: 16 > Device or resource busy > 2020-04-22T19:06:13.421798Z qemu-system-x86_64: failed to initialize > KVM: Device or resource busy > And this fatal error in

Bug#958493: sphinxcontrib-bibtex: autopkgtest regression

2020-04-22 Thread Sebastian Ramacher
Source: sphinxcontrib-bibtex Version: 1.0.0-1 Severity: serious The autopkgtest of sphinxcontrib-bibtex fails, preventing its migration to testing. See https://ci.debian.net/data/autopkgtest/testing/amd64/s/sphinxcontrib-bibtex/5114485/log.gz Cheers -- Sebastian Ramacher signature.asc

Bug#955084: marked as done (panko: FTBFS with Sphinx 2.4: AttributeError: 'Sphinx' object has no attribute 'info')

2020-04-22 Thread Debian Bug Tracking System
Your message dated Wed, 22 Apr 2020 23:07:45 +0200 with message-id <585496d4-79d1-d5e0-746e-06738b5e4...@debian.org> and subject line The issue was in python3-sphinxcontrib-pecanwsme has caused the Debian Bug report #955084, regarding panko: FTBFS with Sphinx 2.4: AttributeError: 'Sphinx' object

Bug#958492: xfonts-terminus: Provide gtk-compatible fonts

2020-04-22 Thread rharwood
Package: xfonts-terminus Version: 4.40-2 Severity: grave Justification: renders package unusable Dear Maintainer, With pango 1.44, bitmap fonts are no longer supported: https://gitlab.gnome.org/GNOME/pango/issues/386 This means that trying to render Terminus in gtk applications looks like...

Bug#958491: acpica-unix: FTBFS on s390x

2020-04-22 Thread Sebastian Ramacher
Source: acpica-unix Version: 20200326-1 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) acpica-unix failed to build on s390x: https://buildd.debian.org/status/fetch.php?pkg=acpica-unix=s390x=20200326-1=1585774833=0 Cheers -- Sebastian

Bug#958191: marked as done (dracut: processor microcode is not loaded (early cpio is not generated))

2020-04-22 Thread Debian Bug Tracking System
Your message dated Wed, 22 Apr 2020 20:34:07 + with message-id and subject line Bug#958191: fixed in dracut 050+35-3 has caused the Debian Bug report #958191, regarding dracut: processor microcode is not loaded (early cpio is not generated) to be marked as done. This means that you claim

Bug#958471: marked as done (src:kineticstools: Non-free data included in source)

2020-04-22 Thread Debian Bug Tracking System
Your message dated Wed, 22 Apr 2020 20:35:11 + with message-id and subject line Bug#958471: fixed in kineticstools 0.6.1+git20200325.3558942+dfsg-1 has caused the Debian Bug report #958471, regarding src:kineticstools: Non-free data included in source to be marked as done. This means that

Processed: severity of 956672 is serious

2020-04-22 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > severity 956672 serious Bug #956672 [rtkit] rtkit activation fails, because service unit is installed at the wrong place Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. --

Bug#958430: Vagrant libvirt

2020-04-22 Thread Pascal De Vuyst
Hi, Thanks for you reply. I already tried the mentioned commands before, but it did not see the hint up until now: Vagrant-libvirt plugin removed box only from you LOCAL ~/.vagrant/boxes directory >From libvirt storage pool you have to delete image manually(virsh, virt-manager or by any other

Bug#940215: Acknowledgement and Gratitude

2020-04-22 Thread Rock Storm
Hi Bouyan Yang, Thanks a lot for taking care of this. I also appreciate the fact that you prepared a PR. It's merged now I'm happy with all the changes. Thank you for the upload. I don't know if it's possible but feel free to upload straight away if you want. Regards, -- Rock Storm GPG KeyID:

Bug#956732: marked as done (gxr: Backends not packaged)

2020-04-22 Thread Debian Bug Tracking System
Your message dated Wed, 22 Apr 2020 18:00:12 + with message-id and subject line Bug#956732: fixed in gxr 0.14.0-3 has caused the Debian Bug report #956732, regarding gxr: Backends not packaged to be marked as done. This means that you claim that the problem has been dealt with. If this is

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-22 Thread Gilles Filippini
Gilles Filippini a écrit le 22/04/2020 à 09:59 : > Hi, > > Matthias Klose a écrit le 20/04/2020 à 12:49 : >> On 4/20/20 11:52 AM, Gilles Filippini wrote: >>> I'd like to do a bisect between openjdk-11 11.0.6+10-2 and 11.0.7+9-1 to >>> better understand the problem but I can't find the

Bug#875584: Can jhdf be uploaded?

2020-04-22 Thread Andreas Tille
Hi, On Wed, Apr 22, 2020 at 06:32:55PM +0200, Giovanni Mascellani wrote: > Apparently jhdf has a patch committed in Salsa which would fix a FTBFS > (which currently prevents hdfview from installing in sid). Is there are > reason for not uploading it? Pretty please upload! Thank you

Bug#953694: marked as done (src:contextfree: fails to migrate to testing for too long)

2020-04-22 Thread Debian Bug Tracking System
Your message dated Wed, 22 Apr 2020 17:33:34 + with message-id and subject line Bug#953694: fixed in contextfree 3.3+dfsg1-1 has caused the Debian Bug report #953694, regarding src:contextfree: fails to migrate to testing for too long to be marked as done. This means that you claim that the

Bug#951939: marked as done (contextfree: FTBFS: src-common/cfdg.cpp:75:71: error: no matching function for call to ‘find(std::array, 18>::const_iterator, std::array

2020-04-22 Thread Debian Bug Tracking System
Your message dated Wed, 22 Apr 2020 17:33:34 + with message-id and subject line Bug#951939: fixed in contextfree 3.3+dfsg1-1 has caused the Debian Bug report #951939, regarding contextfree: FTBFS: src-common/cfdg.cpp:75:71: error: no matching function for call to ‘find(std::array,

Bug#875584: Can jhdf be uploaded?

2020-04-22 Thread Giovanni Mascellani
Apparently jhdf has a patch committed in Salsa which would fix a FTBFS (which currently prevents hdfview from installing in sid). Is there are reason for not uploading it? Thanks, Giovanni. -- Giovanni Mascellani Postdoc researcher - Université Libre de Bruxelles signature.asc Description:

Bug#954227: marked as done (node-eslint-plugin-node: unsuitable for stable release: too broken)

2020-04-22 Thread Debian Bug Tracking System
Your message dated Wed, 22 Apr 2020 16:04:08 + with message-id and subject line Bug#954227: fixed in node-eslint-plugin-node 8.0.1~ds-3 has caused the Debian Bug report #954227, regarding node-eslint-plugin-node: unsuitable for stable release: too broken to be marked as done. This means that

Bug#936797: marked as done (kineticstools: Python2 removal in sid/bullseye)

2020-04-22 Thread Debian Bug Tracking System
Your message dated Wed, 22 Apr 2020 16:00:09 + with message-id and subject line Bug#936797: fixed in kineticstools 0.6.1+git20200325.3558942-1 has caused the Debian Bug report #936797, regarding kineticstools: Python2 removal in sid/bullseye to be marked as done. This means that you claim

Processed: printrun: diff for NMU version 2.0.0~rc5-1.1

2020-04-22 Thread Debian Bug Tracking System
Processing control commands: > tags -1 +patch +pending Bug #940215 [src:printrun] printrun: missing Breaks+Replaces: printrun (<< 2) for package split Added tag(s) patch. Bug #940215 [src:printrun] printrun: missing Breaks+Replaces: printrun (<< 2) for package split Ignoring request to alter

Processed: printrun: diff for NMU version 2.0.0~rc5-1.1

2020-04-22 Thread Debian Bug Tracking System
Processing control commands: > tags -1 +patch +pending Bug #956842 [src:printrun] printrun: FTBFS with python 3.8 Ignoring request to alter tags of bug #956842 to the same tags previously set Bug #956842 [src:printrun] printrun: FTBFS with python 3.8 Added tag(s) pending. -- 956842:

Bug#940215: printrun: diff for NMU version 2.0.0~rc5-1.1

2020-04-22 Thread Boyuan Yang
Control: tags -1 +patch +pending X-Debbugs-CC: rockst...@gmx.com Dear maintainer, I've prepared an NMU for printrun (versioned as 2.0.0~rc5-1.1) and uploaded it to DELAYED/5. Please feel free to tell me if I should delay it longer. Let me know asap if you have any questions or issues.

Bug#958471: src:kineticstools: Non-free data included in source

2020-04-22 Thread Scott Kitterman
Package: src:kineticstools Version: 0.6.1+20161222-1 Severity: serious Justification: Policy 2.1 All versions of kineticstools in the archive include a non-free data file: doc/whitepaper/kinetics.tex The file includes the following statement: For Research Use Only. Not for use in diagnostic

Processed: Add missing sources

2020-04-22 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 787599 patch Bug #787599 [ganglia-web] Some sources are not included in your package Added tag(s) patch. > thank you Stopping processing here. Please contact me if you need assistance. -- 787599:

Bug#947089: marked as done (uftrace: blocked migration to testing: autopkgtest times out on arm64 and FTBFS on armhf)

2020-04-22 Thread Debian Bug Tracking System
Your message dated Wed, 22 Apr 2020 14:35:21 + with message-id and subject line Bug#947089: fixed in uftrace 0.9.4-0.2 has caused the Debian Bug report #947089, regarding uftrace: blocked migration to testing: autopkgtest times out on arm64 and FTBFS on armhf to be marked as done. This

Bug#796536: criu: package not yet ready for stable release / fast moving (blocking bug)

2020-04-22 Thread Salvatore Bonaccorso
On Sat, Aug 22, 2015 at 02:24:48PM +0200, Salvatore Bonaccorso wrote: > Source: criu > Version: 1.6-2 > Severity: serious > > I'm filling this bug as blocking bug for criu for testing. Criu is by > now still a fast moving project and at this point it is not yet ready > to be effectively used in a

Bug#947089: uftrace: diff for NMU version 0.9.4-0.2

2020-04-22 Thread Adrian Bunk
Dear maintainer, I've prepared an NMU for uftrace (versioned as 0.9.4-0.2) and uploaded it. cu Adrian diff -Nru uftrace-0.9.4/debian/changelog uftrace-0.9.4/debian/changelog --- uftrace-0.9.4/debian/changelog 2020-04-13 16:18:27.0 +0300 +++ uftrace-0.9.4/debian/changelog 2020-04-22

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

2020-04-22 Thread Thomas Goirand
On 4/22/20 6:23 AM, Valentin Vidić wrote: > On Tue, Apr 21, 2020 at 11:20:16PM +0200, Thomas Goirand wrote: >> You can remove all of the python-oslo* from the list. The versions in >> Experimental, which are the next version of OpenStack, are fixed. In 2 >> weeks of time, I'll upload all what I

Bug#942988: displaycal: Python2 removal in sid/bullseye

2020-04-22 Thread Scott Talbert
On Wed, 22 Apr 2020, Christian Marillat wrote: On 17 avril 2020 11:32, Scott Talbert wrote: [...] It looks like upstream doesn't seem to be making much progress on this. Do you think that we need to start working on Python 3 support ourselves? Duplicate work is a bad idea. Otherwise

Processed: retitle 958191

2020-04-22 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > retitle 958191 dracut: processor microcode is not loaded (early cpio is not > generated) Bug #958191 [dracut] processor microcode is not loaded (not dracut: early cpio is not produced) Changed Bug title to 'dracut: processor microcode is not

Processed: notfound 958180 in roundcube/1.4.3+dfsg.1-1~bpo10+1

2020-04-22 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > notfound 958180 roundcube/1.4.3+dfsg.1-1~bpo10+1 Bug #958180 {Done: Guilhem Moulin } [roundcube-core] roundcube: roundcube cannot be installed from the backport No longer marked as found in versions roundcube/1.4.3+dfsg.1-1~bpo10+1. > thanks

Bug#958180: marked as done (roundcube: roundcube cannot be installed from the backport)

2020-04-22 Thread Debian Bug Tracking System
Your message dated Wed, 22 Apr 2020 13:46:56 +0200 with message-id <20200422114656.ga1015...@debian.org> and subject line Re: [Pkg-roundcube-maintainers] Bug#958180: roundcube: roundcube cannot be installed from the backport has caused the Debian Bug report #958180, regarding roundcube: roundcube

Bug#958460: FTBFS with no network

2020-04-22 Thread Sven Mueller
Package: appstream-generator Version: 0.8.1-1 Severity: serious This is a policy violation, as the build process must not rely on network accessibility. Error message: [139/147] /usr/bin/xsltproc --nonet --stringparam man.output.quietly 1 --stringparam funcsynopsis.style ansi --stringparam

Processed: Re: Bug#955715 closed by Alastair McKinstry (FIxed in toolchain)

2020-04-22 Thread Debian Bug Tracking System
Processing control commands: > notfound -1 adios/1.13.1-21 Bug #955715 {Done: Alastair McKinstry } [src:adios] adios: FTBFS (error: could not find mpi library for Fortran) No longer marked as found in versions adios/1.13.1-21. > severity -1 normal Bug #955715 {Done: Alastair McKinstry }

Bug#955715: closed by Alastair McKinstry (FIxed in toolchain)

2020-04-22 Thread Sebastiaan Couwenberg
Control: notfound -1 adios/1.13.1-21 Control: severity -1 normal On 4/22/20 12:42 PM, Debian Bug Tracking System wrote: > This was caused due to errors in the OpenMPI toolchain, which have since > been fixed. > > Adios builds Just closing the bug is not sufficient, it's still marked as

Bug#952300: marked as done (construct: FTBFS: dh: error: unable to load addon python3: Can't locate Debian/Debhelper/Sequence/python3.pm in @INC (you may need to install the Debian::Debhelper::Sequenc

2020-04-22 Thread Debian Bug Tracking System
Your message dated Wed, 22 Apr 2020 10:48:37 + with message-id and subject line Bug#952300: fixed in construct 2.8.16-0.4 has caused the Debian Bug report #952300, regarding construct: FTBFS: dh: error: unable to load addon python3: Can't locate Debian/Debhelper/Sequence/python3.pm in @INC

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

2020-04-22 Thread Ondrej Novy
Hi, út 21. 4. 2020 v 23:24 odesílatel Thomas Goirand napsal: > > But that still leaves the question of what to do about the dependency of > > pytest on pypy-funcsigs ? should pypy modules be removed from pytest and > > it's reverse-dependencies in the same way that regular python2 modules > >

Bug#958450: chromium: Please update chromium to 81.0.4044.113 for security reasons

2020-04-22 Thread jim_p
Package: chromium Version: 81.0.4044.92-1 Severity: grave Tags: upstream security Justification: user security hole Dear Maintainer, As the title suggests, please update chromium to 81.0.4044.113 (or later), because it includes a patch for CVE-2020-6457, which is a critical security issue. More

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

2020-04-22 Thread jim_p
Package: nvidia-legacy-340xx-driver Version: 340.108-4 Severity: grave Tags: patch Justification: renders package unusable Dear Maintainer, As with my previous bug reports, nvidia legacy 340 fails to build again. Here is the full log https://pastebin.com/i5wR0s5V Here is the patch, again from

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-22 Thread Sylvestre Ledru
Le 22/04/2020 à 09:59, Gilles Filippini a écrit : Hi, Matthias Klose a écrit le 20/04/2020 à 12:49 : On 4/20/20 11:52 AM, Gilles Filippini wrote: I'd like to do a bisect between openjdk-11 11.0.6+10-2 and 11.0.7+9-1 to better understand the problem but I can't find the corresponding branch on

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-22 Thread Gilles Filippini
Hi, Matthias Klose a écrit le 20/04/2020 à 12:49 : > On 4/20/20 11:52 AM, Gilles Filippini wrote: >> I'd like to do a bisect between openjdk-11 11.0.6+10-2 and 11.0.7+9-1 to >> better understand the problem but I can't find the corresponding branch >> on the openjdk Mercurial repo. > >

Bug#953487: Bugs fixed in runescape/0.8-1

2020-04-22 Thread Carlos Donizete Froes
Hi, Improvements were made to the Runescape launcher, as reported. BUG #953487: - This bug contains "XS-Autobuild: yes" in d/control and also a warning about "Autobuilding" in d/copyright since the runescape/0.5-2 package which has not been changed since recent versions. BUG #956275: - Own icon

Bug#958430: (no subject)

2020-04-22 Thread Manu Ka
Thank you for your interest in the vagrant boxes. A fresh vagrant env with libvirt and 10.3 works for me (see: http://paste.debian.net/1142057/) Can you reproduce the problem in a fresh environment ? ie erase your current box and create a new vagrant env vagrant box remove debian/buster64

Bug#958430: Vagrant libvirt

2020-04-22 Thread Emmanuel Kasper
Thank you for your interest in the vagrant boxes. A fresh vagrant env with libvirt and 10.3 works for me (see: http://paste.debian.net/1142057/) Can you reproduce the problem in a fresh environment ? ie erase your current box and create a new vagrant env vagrant box remove debian/buster64

Bug#942988: displaycal: Python2 removal in sid/bullseye

2020-04-22 Thread Christian Marillat
On 17 avril 2020 11:32, Scott Talbert wrote: [...] > It looks like upstream doesn't seem to be making much progress on > this. Do you think that we need to start working on Python 3 support > ourselves? Duplicate work is a bad idea. Otherwise upstream is still active in displaycal forums