Bug#937465: marked as done (pykerberos: Python2 removal in sid/bullseye)

Your message dated Mon, 30 Dec 2019 07:19:57 + with message-id and subject line Bug#937465: fixed in pykerberos 1.1.14-3.1 has caused the Debian Bug report #937465, regarding pykerberos: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has been

Processed: python-jedi: diff for NMU version 0.14.1-1.1

Processing control commands: > tags 937849 + pending Bug #937849 [src:python-jedi] python-jedi: Python2 removal in sid/bullseye Added tag(s) pending. -- 937849: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=937849 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#943012: marked as done (dfwinreg: Python2 removal in sid/bullseye)

Your message dated Mon, 30 Dec 2019 07:04:14 + with message-id and subject line Bug#943012: fixed in dfwinreg 20190122-1.1 has caused the Debian Bug report #943012, regarding dfwinreg: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has been

Bug#937849: python-jedi: diff for NMU version 0.14.1-1.1

Control: tags 937849 + pending Dear maintainer, I've prepared an NMU for python-jedi (versioned as 0.14.1-1.1) and uploaded it to DELAYED/3. Please feel free to tell me if I should delay it longer. I didnt think a new upstream release is necessary to fix this bug, so in the spirit of keeping

Bug#937465: pykerberos: diff for NMU version 1.1.14-3.1

Control: tags 937465 + patch Dear maintainer, I've prepared an NMU for pykerberos (versioned as 1.1.14-3.1). The diff is attached to this message. Regards. diff -Nru pykerberos-1.1.14/debian/changelog pykerberos-1.1.14/debian/changelog --- pykerberos-1.1.14/debian/changelog 2019-11-30

Processed: pykerberos: diff for NMU version 1.1.14-3.1

Processing control commands: > tags 937465 + patch Bug #937465 [src:pykerberos] pykerberos: Python2 removal in sid/bullseye Added tag(s) patch. -- 937465: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=937465 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#947757: pysparse: should this package be removed?

Source: pysparse Severity: serious Hello, it seeems to me there are several issues with this package: * python2 only, and there's already another `python3-sparse` from another src * no upstream commits since 2013, https://sourceforge.net/p/pysparse/git/commit_browser * no upstream releases

Bug#943012: dfwinreg: diff for NMU version 20190122-1.1

Dear maintainer, I've prepared an NMU for dfwinreg (versioned as 20190122-1.1). The diff is attached to this message. Regards. diff -Nru dfwinreg-20190122/debian/changelog dfwinreg-20190122/debian/changelog --- dfwinreg-20190122/debian/changelog 2019-01-23 04:45:44.0 -0500 +++

Bug#947424: marked as done (qtltools 1.2+dfsg-1 ftbfs on mipsel)

Your message dated Mon, 30 Dec 2019 07:31:41 +0100 with message-id and subject line has caused the Debian Bug report #947424, regarding qtltools 1.2+dfsg-1 ftbfs on mipsel to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now

Bug#947717: pbcopper FTBFS on all architectures except x32

On Sun, Dec 29, 2019 at 07:00:54PM +0100, Michael Crusoe wrote: > pbcopper's latest release has slipped in a code copy of libssw which uses > x86 SIMD intrinsics. I've pushed up a fix along the lines I made to libssw > to enable cross architecture compilation at >

Bug#945723: marked as done (weevely: Python2 removal in sid/bullseye)

Your message dated Mon, 30 Dec 2019 02:47:15 + with message-id and subject line Bug#945723: fixed in weevely 4.0.0-1 has caused the Debian Bug report #945723, regarding weevely: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has been dealt

Bug#937267: Is there any Python3 version of pebl

I haven’t made a py3 port and actually haven’t worked on Pebl in years. There are some forks though (on github) and they may have py3 versions. On Sun, Dec 29, 2019 at 5:38 AM Andreas Tille wrote: > Control: tags -1 upstream > Control: forwarded -1 abhiks...@gmail.com > > Hi, > > Python2 is

Bug#925822: marked as done (scanbd: ftbfs with GCC-9)

Your message dated Mon, 30 Dec 2019 01:50:55 + with message-id and subject line Bug#925822: fixed in scanbd 1.5.1-5 has caused the Debian Bug report #925822, regarding scanbd: ftbfs with GCC-9 to be marked as done. This means that you claim that the problem has been dealt with. If this is

Bug#946857: marked as done (pyfftw: FTBFS in unstable)

Your message dated Sun, 29 Dec 2019 23:49:24 + with message-id and subject line Bug#946857: fixed in pyfftw 0.11.1-4 has caused the Debian Bug report #946857, regarding pyfftw: FTBFS in unstable to be marked as done. This means that you claim that the problem has been dealt with. If this is

Bug#937848: marked as done (python-itsdangerous: Python2 removal in sid/bullseye)

Your message dated Sun, 29 Dec 2019 23:19:22 + with message-id and subject line Bug#937848: fixed in python-itsdangerous 0.24+dfsg1-2.1 has caused the Debian Bug report #937848, regarding python-itsdangerous: Python2 removal in sid/bullseye to be marked as done. This means that you claim

Bug#945469: marked as done (yarl fails a test at least with Python 3.8)

Your message dated Sun, 29 Dec 2019 23:19:56 + with message-id and subject line Bug#945469: fixed in yarl 1.4.2-1 has caused the Debian Bug report #945469, regarding yarl fails a test at least with Python 3.8 to be marked as done. This means that you claim that the problem has been dealt

Bug#947748: xorg-server: FTBFS in sid (probably due to newer mesa)

Source: xorg-server Version: 2:1.20.6-1 Severity: serious Tags: patch Justification: FTBFS Hello, Probably since the upload of the newer mesa, xorg-server now FTBFS, because it misses dri.pc and x11-xcb.pc. The attached patch fixes this. Samuel -- System Information: Debian Release:

Bug#947360: marked as done (coinor-libdylp-dev: ships headers owned by coinor-libcoinutils-dev, coinor-libosi-dev)

Your message dated Sun, 29 Dec 2019 22:05:07 + with message-id and subject line Bug#947360: fixed in coinor-dylp 1.10.4-2 has caused the Debian Bug report #947360, regarding coinor-libdylp-dev: ships headers owned by coinor-libcoinutils-dev, coinor-libosi-dev to be marked as done. This

Bug#947745: recent version for stable-(updates|backports)

Package: youtube-dl Version: 2019.01.17-1.1 Severity: grave Justification: renders package unusable Dear maintainer, the buster version has quit working with yt. The error message is: "YouTube said: This video is unavailable." 2019.09.28-1 works. Due to the package's volatility (which causes

Bug#943509: marked as done (python-django: FTBFS due to failed tests: failures=7, skipped=891, expected failures=4)

Your message dated Sun, 29 Dec 2019 21:54:23 + with message-id and subject line Bug#943509: fixed in sqlite3 3.30.1+fossil191229-1 has caused the Debian Bug report #943509, regarding python-django: FTBFS due to failed tests: failures=7, skipped=891, expected failures=4 to be marked as done.

Bug#947744: installation-reports: Debian Live Testing LXQt + nonfree - install fails with: "Bad unsquash configuration"

Package: installation-reports Severity: grave Justification: renders package unusable Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit From: Scott Jacobs To: Debian Bug Tracking System Subject: installation-reports: Debian Live Testing LXQt +

Bug#916107: mongodb: MongoDB should not be part of a stable release

> I propose to now remove it from unstable, per > https://www.mongodb.com/support-policy > support for 3.4 ends in January 2020. ive opened #947743 to ask for mongodb removal Regards, -- Sandro "morph" Tosi My website: http://sandrotosi.me/ Me at Debian: http://wiki.debian.org/SandroTosi

Processed: Re: Processed (with 1 error): help bts & britney

Processing commands for cont...@bugs.debian.org: > # Oops. > fixed 946984 2019.12~git~0~e74819ea-6 Bug #946984 {Done: Anton Gladky } [src:yade] yade: Ships python3.8 scripts, without any python3 or python3.8 deps Marked as fixed in versions yade/2019.12~git~0~e74819ea-6. > thanks Stopping

Processed (with 1 error): help bts & britney

Processing commands for cont...@bugs.debian.org: > reassign 946984 src:yade 2019.12~git~0~e74819ea-4 Bug #946984 {Done: Anton Gladky } [yade] yade: Ships python3.8 scripts, without any python3 or python3.8 deps Bug reassigned from package 'yade' to 'src:yade'. No longer marked as found in

Bug#943509: python-django: FTBFS due to failed tests: failures=7, skipped=891, expected failures=4

Hi Chris, On Sun, Dec 29, 2019 at 5:57 PM Chris Lamb wrote: > I don't fully understand the ramifications or risks of uploading the > current Fossil tree I'm afraid so I will have to leave that judgement > to you. Can you let me know your intention either way so that we don't > lose this down the

Bug#947482: marked as done (txt2tags: missing Depends: python3-pkg-resources)

Your message dated Sun, 29 Dec 2019 20:55:09 + with message-id and subject line Bug#947482: fixed in txt2tags 3.4-2 has caused the Debian Bug report #947482, regarding txt2tags: missing Depends: python3-pkg-resources to be marked as done. This means that you claim that the problem has been

Bug#947717: marked as done (pbcopper FTBFS on all architectures except x32)

Your message dated Sun, 29 Dec 2019 20:52:27 + with message-id and subject line Bug#947717: fixed in pbcopper 1.3.0+dfsg-2 has caused the Debian Bug report #947717, regarding pbcopper FTBFS on all architectures except x32 to be marked as done. This means that you claim that the problem has

Bug#943458: marked as done (python-redis: missing test dep on python3-all)

Your message dated Sun, 29 Dec 2019 19:10:09 + with message-id and subject line Bug#943458: fixed in python-redis 3.3.11-2 has caused the Debian Bug report #943458, regarding python-redis: missing test dep on python3-all to be marked as done. This means that you claim that the problem has

Processed: watson: FTBFS in bullseye and sid

Processing commands for cont...@bugs.debian.org: > tags 947733 + sid bullseye Bug #947733 [src:watson] watson: FTBFS in bullseye and sid Added tag(s) sid and bullseye. > thanks Stopping processing here. Please contact me if you need assistance. -- 947733:

Bug#947237: gnome-software: Crashes on click over any software icon

On Mon, 23 Dec 2019 11:45:45 +0100 definetti wrote: > Dear Maintainer, Hello, > upon updating to 3.34.2, the application crashes when I click over any software > icon, before the relative page is loaded. > Valgrind reports a segmentation fault with the error > > ==186020== Thread 5

Processed: found 947237 in 3.34.2-1

Processing commands for cont...@bugs.debian.org: > found 947237 3.34.2-1 Bug #947237 [gnome-software-plugin-snap] gnome-software: Crashes on click over any software icon Marked as found in versions gnome-software/3.34.2-1. > thanks Stopping processing here. Please contact me if you need

Processed: reassign 947237 to gnome-software-plugin-snap

Processing commands for cont...@bugs.debian.org: > reassign 947237 gnome-software-plugin-snap Bug #947237 [gnome-software] gnome-software: Crashes on click over any software icon Bug reassigned from package 'gnome-software' to 'gnome-software-plugin-snap'. No longer marked as found in versions

Bug#937170: marked as done (nvpy: Python2 removal in sid/bullseye)

Your message dated Sun, 29 Dec 2019 13:30:20 -0500 with message-id and subject line Re: nvpy: Python2 removal in sid/bullseye has caused the Debian Bug report #937170, regarding nvpy: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has been dealt

Bug#947726: marked as done (BD on texlive-generic-extra which isn't build anymore and isn't in bullseye)

Your message dated Sun, 29 Dec 2019 18:19:58 + with message-id and subject line Bug#947726: fixed in osmnx 0.11+ds-2 has caused the Debian Bug report #947726, regarding BD on texlive-generic-extra which isn't build anymore and isn't in bullseye to be marked as done. This means that you

Bug#947717: pbcopper FTBFS on all architectures except x32

pbcopper's latest release has slipped in a code copy of libssw which uses x86 SIMD intrinsics. I've pushed up a fix along the lines I made to libssw to enable cross architecture compilation at https://salsa.debian.org/med-team/pbcopper/commit/f9678ed29590b57fe30638eed3d6819577b4ace1 and it awaits

Bug#936493: marked as done (exactimage: Python2 removal in sid/bullseye)

Your message dated Sun, 29 Dec 2019 17:34:32 + with message-id and subject line Bug#936493: fixed in exactimage 1.0.2-7 has caused the Debian Bug report #936493, regarding exactimage: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has been

Processed: tagging 938766

Processing commands for cont...@bugs.debian.org: > tags 938766 + upstream Bug #938766 [src:uwsgi] uwsgi: Python2 removal in sid/bullseye Added tag(s) upstream. > thanks Stopping processing here. Please contact me if you need assistance. -- 938766:

Processed: python-redis: missing test dep on python3-all

Processing commands for cont...@bugs.debian.org: > severity 943458 serious Bug #943458 [python-redis] python-redis: missing test dep on python3-all Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 943458:

Bug#943509: python-django: FTBFS due to failed tests: failures=7, skipped=891, expected failures=4

Hi László, > scheduled to 31st of December, this year but it was delayed with a > whole month later I don't fully understand the ramifications or risks of uploading the current Fossil tree I'm afraid so I will have to leave that judgement to you. Can you let me know your intention either way so

Processed: Re: Bug#947717: pbcopper FTBFS on all architectures except x32

Processing control commands: > tags -1 help Bug #947717 [src:pbcopper] pbcopper FTBFS on all architectures except x32 Added tag(s) help. -- 947717: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947717 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#947717: pbcopper FTBFS on all architectures except x32

Control: tags -1 help Hi, it might be that the new upstream version is targeting only at amd64 (and by chance builds on x32). If there is a hint from porters how to fix the build the only idea I have is to restrict it to amd64 (and x32). Kind regards Andreas. On Sun, Dec 29, 2019 at

Processed: closing 946563

Processing commands for cont...@bugs.debian.org: > close 946563 1:4.4.10-8 Bug #946563 [src:libxcrypt] there is no need for a versioned libxcrypt1-dev package The source 'libxcrypt' and version '1:4.4.10-8' do not appear to match any binary packages Marked as fixed in versions

Processed: Re: Bug#947729: radicale: broken after upgrade from stretch

Processing control commands: > severity -1 normal Bug #947729 [radicale] radicale: broken after upgrade from stretch Severity set to 'normal' from 'grave' -- 947729: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947729 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#947729: radicale: broken after upgrade from stretch

control: severity -1 normal Hi Stefan, Quoting Stefan Fritsch (2019-12-29 16:14:36) > Severity: grave > Justification: renders package unusable Severity lowered: Package is certainly not unusable (even if upgrade feature failed to work for you). - Jonas -- * Jonas Smedegaard - idealist &

Bug#943509: python-django: FTBFS due to failed tests: failures=7, skipped=891, expected failures=4

Hi Paul, Chris, On Sun, Dec 29, 2019 at 4:27 PM Chris Lamb wrote: > > @python-django maintainers what does this mean for the functionality of > > python-django in bullseye? Is it "only" the test that fails and can that > > thus be temporarily disabled? > > I would be amenable to disabling the

Bug#947733: watson: FTBFS in bullseye and sid

Source: watson Version: 1.6.0-6 Severity: serious Tags: ftbfs Hi Maintainer Both watson 1.6.0-6 in bullseye and 1.7.0-5 in sid FTBFS [1]. The upload to sid did not migrate to testing [2]. Please do source-only uploads, unless there are NEW binaries. Not built on buildd: arch all binaries

Bug#929954: [Python-apps-team] Bug#929954: what about just uploading relevant patch for now?

On Fri, 09 Aug 2019, Elena ``of Valhalla'' wrote: > Yaroslav Halchenko wrote: > > If new version building is problematic, why not to upload just a patched > > version? > That would only delay the removal a bit: I'm sure that the current > version doesn't work with python3, so it's going to be

Processed: python-jellyfish: autopkgtest fails if more than one supported python version

Processing commands for cont...@bugs.debian.org: > severity 943454 serious Bug #943454 [python-jellyfish] python-jellyfish: autopkgtest fails if more than one supported python version Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contact me if you need

Bug#947723: devede BD on python-scour which isn't build anymore and isn't in sid/bullseye

Quoting Paul Gevers (2019-12-29 15:07:13) > Recently the scour package has stopped building the python-scour > package. This is an issue for your package as it build-depends on it. > Please update the building of your package. The _command-line tool_ "scour" has moved to its own package "scour"

Processed: rdflib: Build-Depends on python-rdflib-jsonld

Processing commands for cont...@bugs.debian.org: > clone 938336 -1 Bug #938336 [src:rdflib] rdflib: Python2 removal in sid/bullseye Bug 938336 cloned as bug 947730 936709 was blocked by: 937911 937614 938336 943193 936973 937236 938216 936678 938845 938528 936196 938712 936270 938518 937182

Bug#947729: radicale: broken after upgrade from stretch

Package: radicale Version: 2.1.11-6 Severity: grave Justification: renders package unusable Hi, I have upgraded my system from stretch. After some head scratching due to the new disk format, I have installed the package listen in NEWS.debian, did radicale --export-storage /var/tmp/radicale

Bug#943509: python-django: FTBFS due to failed tests: failures=7, skipped=891, expected failures=4

Hi Paul, > @python-django maintainers what does this mean for the functionality of > python-django in bullseye? Is it "only" the test that fails and can that > thus be temporarily disabled? I would be amenable to disabling the test in python-django if a response or fix in sqlite3 is not

Bug#933284: marked as done (BD on texlive-generic-extra which isn't build anymore and isn't in bullseye)

Your message dated Sun, 29 Dec 2019 15:20:37 + with message-id and subject line Bug#933284: fixed in highlight.js 9.12.0+dfsg1-5 has caused the Debian Bug report #933284, regarding BD on texlive-generic-extra which isn't build anymore and isn't in bullseye to be marked as done. This means

Bug#943509: python-django: FTBFS due to failed tests: failures=7, skipped=891, expected failures=4

Hi, On Sat, 26 Oct 2019 19:17:01 +0100 "Chris Lamb" wrote: > Hi László, > > > But you mean plural packages? I knew only python-django. I meant > > sure, it's a FTBFS in experimental where […] > > I see what you mean now, thanks. I assumed it affected more packages > and was more severe than

Processed: BD on texlive-generic-extra which isn't build anymore and isn't in bullseye

Processing commands for cont...@bugs.debian.org: > clone 933284 -1 Bug #933284 [highlight.js] BD on texlive-generic-extra which isn't build anymore and isn't in bullseye Bug 933284 cloned as bug 947726 > reassign -1 osmnx 0.10+ds-2 Bug #947726 [highlight.js] BD on texlive-generic-extra which

Bug#947129: marked as done (x2goclient: regression caused by CVE-2019-14889/libssh fix)

Your message dated Sun, 29 Dec 2019 14:44:56 + with message-id and subject line Bug#947129: fixed in x2goclient 4.0.5.2-2+deb9u1 has caused the Debian Bug report #947129, regarding x2goclient: regression caused by CVE-2019-14889/libssh fix to be marked as done. This means that you claim that

Bug#947723: devede BD on python-scour which isn't build anymore and isn't in sid/bullseye

Source: devede Version: 4.15.0-1 Severity: serious Tags: ftbfs sid bullseye Dear maintainer, Recently the scour package has stopped building the python-scour package. This is an issue for your package as it build-depends on it. Please update the building of your package. Unfortunately the

Bug#937267: Is there any Python3 version of pebl

Control: tags -1 upstream Control: forwarded -1 abhiks...@gmail.com Hi, Python2 is End Or Life at 1.1.2020 and Debian is about to remove all Python2 dependencies. I wonder if there is any Python2 port of Pebl. I just found https://pypi.org/project/pebl/ which is at version 1.01 while it

Processed: Is there any Python3 version of pebl

Processing control commands: > tags -1 upstream Bug #937267 [src:pebl] pebl: Python2 removal in sid/bullseye Added tag(s) upstream. > forwarded -1 abhiks...@gmail.com Bug #937267 [src:pebl] pebl: Python2 removal in sid/bullseye Set Bug forwarded-to-address to 'abhiks...@gmail.com'. -- 937267:

Bug#947720: sollya ftbfs with libfplll6

Source: sollya Version: 7.0+ds-3 Severity: serious Justification: ftbfs Tags: ftbfs sid bullseye Dear maintainer, Your package is part of the libfpll6 transition. I scheduled binNMU's, but your package fails everywhere. Please have a look. Paul

Bug#947718: fplll ftbfs on armel and mipsel (and m68k, powerpc and sh4)

Source: fplll Version: 5.3.1-1 Severity: serious Justification: ftbfs Tags: ftbfs sid bullseye Dear maintainer, Your package fails to build from source on armel and mipsel. Because it started a transition, this failure has more widespread impact than just your package. Please have a look. Paul

Bug#947717: pbcopper FTBFS on all architectures except x32

Source: pbcopper Version: 1.3.0+dfsg-1 Severity: serious Justification: ftbfs Tags: ftbfs sid bullseye Dear maintainer, Your package fails to build from source on all buildds except x32. Your package is involved in the pbbam and htslib transitions and blocking progress. Please have a look. Paul

Bug#947076: marked as done (xchat.desktop file has invalid Exec line (at least for KDE))

Your message dated Sun, 29 Dec 2019 12:55:29 + with message-id and subject line Bug#947076: fixed in xchat 2.8.8-19 has caused the Debian Bug report #947076, regarding xchat.desktop file has invalid Exec line (at least for KDE) to be marked as done. This means that you claim that the problem

Bug#944277: marked as done (FTBFS with OCaml 4.08.1 (Error while running external preprocessor))

Your message dated Sun, 29 Dec 2019 12:51:55 + with message-id and subject line Bug#944277: fixed in hol-light 20190729-3 has caused the Debian Bug report #944277, regarding FTBFS with OCaml 4.08.1 (Error while running external preprocessor) to be marked as done. This means that you claim

Bug#947613: [Pkg-utopia-maintainers] Bug#947613: network-manager: Wi-Fi not working (does not get IPv4 address) with 1.22.2-1

Can you provide a full, verbose debug log: https://wiki.gnome.org/Projects/NetworkManager/Debugging Which dhcp client do you use: internal, isc-dhcp-client, ...? signature.asc Description: OpenPGP digital signature

Processed: libgtk2.0-0: is deprecated and mostly unmaintained

Processing control commands: > block -1 by 885135 Bug #947713 [libgtk2.0-0] libgtk2.0-0: is deprecated and mostly unmaintained 947713 was not blocked by any bugs. 947713 was not blocking any bugs. Added blocking bug(s) of 947713: 885752 and 885135 -- 947713:

Bug#947712: autopkgtest regressions in python-dbusmock with newer network-manager 1.22.2-1

Package: network-manager, python-dbusmock Version: 1.22.2-1 Severity: serious The latest update of network-manager causes an autopkgtest regression in python-dbusmock. https://ci.debian.net/data/autopkgtest/testing/amd64/p/python-dbusmock/3793816/log.gz

Bug#944277: actually a bug in camlp5

Le 29/12/2019 à 13:05, Stéphane Glondu a écrit : >> This is probably caused by a bug in camlp5, caught by a stricter dynamic >> linker in OCaml 4.08. It is fixed in camlp5 7.10. >> >> See https://github.com/camlp5/camlp5/pull/46 > > I've updated camlp5 to 7.10, and given back hol-light on amd64.

Bug#947711: rust-goblin: autopkgtest failure

Source: rust-goblin Version: 0.1.0-1 X-Debbugs-CC: debian...@lists.debian.org Severity: serious User: debian...@lists.debian.org Usertags: regression Dear maintainers, With a recent upload of rust-goblin you added an autopkgtest to your package, great. However, it fails. I copied some of the

Bug#947678: marked as done (FTBFS: /usr/bin/ld: cannot find -lGL)

Your message dated Sun, 29 Dec 2019 13:24:40 +0100 with message-id <9649c8b9-b92d-efef-9298-b73991d77...@physik.fu-berlin.de> and subject line Re: Bug#947678: FTBFS: /usr/bin/ld: cannot find -lGL has caused the Debian Bug report #947678, regarding FTBFS: /usr/bin/ld: cannot find -lGL to be marked

Bug#947710: rust-fallible-iterator: autopkgtest failure

Source: rust-fallible-iterator Version: 0.2.0-1 X-Debbugs-CC: debian...@lists.debian.org Severity: serious User: debian...@lists.debian.org Usertags: regression Dear maintainers, With a recent upload of rust-fallible-iterator you added an autopkgtest to your package, great. However, it fails. I

Bug#944277: actually a bug in camlp5

Le 19/12/2019 à 23:39, Christopher Cramer a écrit : > This is probably caused by a bug in camlp5, caught by a stricter dynamic > linker in OCaml 4.08. It is fixed in camlp5 7.10. > > See https://github.com/camlp5/camlp5/pull/46 I've updated camlp5 to 7.10, and given back hol-light on amd64. It

Bug#947709: rust-clang-sys: autopkgtest failure: all tests fail

Source: rust-clang-sys Version: 0.28.1-3 X-Debbugs-CC: debian...@lists.debian.org Severity: serious User: debian...@lists.debian.org Usertags: regression Dear maintainers, With a recent upload of rust-clang-sys you added an autopkgtest to rust-clang-sys, great. However, it fails. I copied some

Bug#916107: mongodb: MongoDB should not be part of a stable release

On Sat, Nov 16, 2019 at 08:47:13PM -0500, Sandro Tosi wrote: > On Mon, 10 Dec 2018 11:01:11 +0200 Apollon Oikonomopoulos > wrote: > > Source: mongodb > > Version: 1:3.4.15-1 > > Severity: serious > > Justification: Cannot be properly supported > > > > MongoDB should not be part of (at least)

Bug#947678: FTBFS: /usr/bin/ld: cannot find -lGL

On 12/29/19 12:58 PM, Patrick Matthäi wrote: >> It pretty much looks like the development files for OpenGL are missing >> and the linker is complaining it can't find libGL to link against. > > > I think this just happens because of the added -latomic flag. See the > build logs and the changelog

Bug#942972: marked as done (csound: Python2 removal in sid/bullseye)

Your message dated Sun, 29 Dec 2019 12:00:12 + with message-id and subject line Bug#942972: fixed in csound 1:6.13.0~dfsg-2 has caused the Debian Bug report #942972, regarding csound: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has been

Bug#947678: FTBFS: /usr/bin/ld: cannot find -lGL

Am 29.12.2019 um 10:51 schrieb John Paul Adrian Glaubitz: > Hi! > > On 12/29/19 10:36 AM, Patrick Matthäi wrote: >>> collect2: error: ld returned 1 exit status >>> make[3]: *** [Makefile:61: ../libmltopengl.so] Error 1 >>> make[3]: Leaving directory '/<>/src/modules/opengl' >> Yes, I already

Bug#885140: [pkg-wicd-maint] Bug#885140: wicd: Depends on unmaintained pygtk

Il giorno sab, 28/12/2019 alle 15.49 +0100, Axel Beckert ha scritto: > look at that issue, i.e. Debian bug report #946380?) sure, sorry... was having some time off keyboard as well :) ...I'll spend some time on it in the upcoming week best, GMS

Bug#947129: marked as done (x2goclient: regression caused by CVE-2019-14889/libssh fix)

Your message dated Sun, 29 Dec 2019 11:47:19 + with message-id and subject line Bug#947129: fixed in x2goclient 4.1.2.1-2+deb10u1 has caused the Debian Bug report #947129, regarding x2goclient: regression caused by CVE-2019-14889/libssh fix to be marked as done. This means that you claim

Bug#942315: marked as done (tcpdump: Version in oldoldstable is higher than oldstable and stable)

Your message dated Sun, 29 Dec 2019 11:26:20 + with message-id <877e2fl6eb.fsf@lusus> and subject line Closing has caused the Debian Bug report #942315, regarding tcpdump: Version in oldoldstable is higher than oldstable and stable to be marked as done. This means that you claim that the

Bug#936493: marked as done (exactimage: Python2 removal in sid/bullseye)

Your message dated Sun, 29 Dec 2019 11:00:11 + with message-id and subject line Bug#936493: fixed in exactimage 1.0.2-6 has caused the Debian Bug report #936493, regarding exactimage: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has been

Bug#925729: marked as done (lammps: ftbfs with GCC-9)

Your message dated Sun, 29 Dec 2019 11:00:14 + with message-id and subject line Bug#925729: fixed in lammps 20190919+dfsg2-1 has caused the Debian Bug report #925729, regarding lammps: ftbfs with GCC-9 to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#937730: marked as done (python-envisage: Python2 removal in sid/bullseye)

Your message dated Sun, 29 Dec 2019 11:00:19 + with message-id and subject line Bug#937730: fixed in python-envisage 4.9.0-1 has caused the Debian Bug report #937730, regarding python-envisage: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem

Bug#902513: marked as done (openturns: FTBFS in buster/sid (nlopt.hpp: No such file or directory))

Your message dated Sun, 29 Dec 2019 11:00:17 + with message-id and subject line Bug#902513: fixed in openturns 1.14-1 has caused the Debian Bug report #902513, regarding openturns: FTBFS in buster/sid (nlopt.hpp: No such file or directory) to be marked as done. This means that you claim that

Bug#946734: marked as done (rust-addr2line Build-Depends on librust-fallible-iterator-0.1+default-dev which isn't available)

Your message dated Sun, 29 Dec 2019 11:00:21 + with message-id and subject line Bug#946734: fixed in rust-addr2line 0.10.0-1 has caused the Debian Bug report #946734, regarding rust-addr2line Build-Depends on librust-fallible-iterator-0.1+default-dev which isn't available to be marked as

Bug#938051: marked as done (python-psycogreen: Python2 removal in sid/bullseye)

Your message dated Sun, 29 Dec 2019 11:00:19 + with message-id and subject line Bug#938051: fixed in python-psycogreen 1.0.1-1 has caused the Debian Bug report #938051, regarding python-psycogreen: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the

Bug#938184: marked as done (python-socksipychain: Python2 removal in sid/bullseye)

Your message dated Sun, 29 Dec 2019 11:00:20 + with message-id and subject line Bug#938184: fixed in python-socksipychain 2.1.0-1 has caused the Debian Bug report #938184, regarding python-socksipychain: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the

Bug#937214: marked as done (openturns: Python2 removal in sid/bullseye)

Your message dated Sun, 29 Dec 2019 11:00:17 + with message-id and subject line Bug#937214: fixed in openturns 1.14-1 has caused the Debian Bug report #937214, regarding openturns: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has been dealt

Bug#937697: marked as done (python-demgengeo: Python2 removal in sid/bullseye)

Your message dated Sun, 29 Dec 2019 11:00:18 + with message-id and subject line Bug#937697: fixed in python-demgengeo 1.4-1 has caused the Debian Bug report #937697, regarding python-demgengeo: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem

Bug#920456: marked as done (i2p: modifies conffiles (policy 10.7.3): /etc/i2p/wrapper.config)

Your message dated Sun, 29 Dec 2019 10:49:34 + with message-id and subject line Bug#920456: fixed in i2p 0.9.44-2 has caused the Debian Bug report #920456, regarding i2p: modifies conffiles (policy 10.7.3): /etc/i2p/wrapper.config to be marked as done. This means that you claim that the

Bug#947053: marked as done (pep8 uses python instead of python2 in the autopkg tests)

Your message dated Sun, 29 Dec 2019 10:04:40 + with message-id and subject line Bug#947053: fixed in pep8 1.7.1-8 has caused the Debian Bug report #947053, regarding pep8 uses python instead of python2 in the autopkg tests to be marked as done. This means that you claim that the problem has

Processed: reassign 947060 to network-manager, forcibly merging 947003 947060

Processing commands for cont...@bugs.debian.org: > reassign 947060 network-manager Bug #947060 [resolvconf] resolvconf: dots stipped from dhcp search domain Bug reassigned from package 'resolvconf' to 'network-manager'. No longer marked as found in versions resolvconf/1.81. Ignoring request to

Bug#947263: marked as done (python3-iniparse: missing Breaks+Replaces: python-iniparse)

Your message dated Sun, 29 Dec 2019 09:52:43 + with message-id and subject line Bug#947263: fixed in python-iniparse 0.4-3 has caused the Debian Bug report #947263, regarding python3-iniparse: missing Breaks+Replaces: python-iniparse to be marked as done. This means that you claim that the

Bug#947678: FTBFS: /usr/bin/ld: cannot find -lGL

Hi! On 12/29/19 10:36 AM, Patrick Matthäi wrote: >> collect2: error: ld returned 1 exit status >> make[3]: *** [Makefile:61: ../libmltopengl.so] Error 1 >> make[3]: Leaving directory '/<>/src/modules/opengl' > > Yes, I already asked for help here: >

Bug#947678: FTBFS: /usr/bin/ld: cannot find -lGL

Hi Am 29.12.2019 um 01:58 schrieb Lisandro Damián Nicanor Pérez Meyer: > Source: mlt > Version: 6.18.0-3 > Severity: serious > Justification: FTBFS on all archs > > Hi! Your package failed to build form source on all archs: > > > > The error

Processed: Re: Processed: Tag

Processing commands for cont...@bugs.debian.org: > tag 947678 + help Bug #947678 [src:mlt] FTBFS: /usr/bin/ld: cannot find -lGL Added tag(s) help. > thanks Stopping processing here. Please contact me if you need assistance. -- 947678: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947678

Bug#947678: Processed: Tag

tag 947678 + help thanks Am 29.12.2019 um 02:18 schrieb Debian Bug Tracking System: > Processing commands for cont...@bugs.debian.org: > >> tag 947678 ftbfs > Bug #947678 [src:mlt] FTBFS: /usr/bin/ld: cannot find -lGL > Added tag(s) ftbfs. >> thanks > Stopping processing here. > > Please contact