Bug#964002: librostime1d: missing Breaks+Replaces: librostime0d (>= 0.7.2)

2020-06-30 Thread Andreas Beckmann
Package: librostime1d Version: 0.7.2-3 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'sid' to 'experimental'. It installed fine in 'sid', then the upgrade to 'experimental' fails because it tries

Processed: closing 964002

2020-06-30 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > close 964002 0.7.2-4 Bug #964002 [librostime1d] librostime1d: missing Breaks+Replaces: librostime0d (>= 0.7.2) Marked as fixed in versions ros-roscpp-core/0.7.2-4. Bug #964002 [librostime1d] librostime1d: missing Breaks+Replaces: librostime0d (>

Bug#964004: jest: missing Breaks+Replaces: node-typescript-types (<< 20200626)

2020-06-30 Thread Andreas Beckmann
Package: jest Version: 24.9.0+ds-3 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'testing'. It installed fine in 'testing', then the upgrade to 'sid' fails because it tries to overwrite other pack

Bug#964002: closing 964002

2020-06-30 Thread Jochen Sprickerhof
close 964002 0.7.2-4 thanks

Bug#959507: marked as done (dub: flaky autopkgtest: Package dub not found for registry at https://code.dlang.org/)

2020-06-30 Thread Debian Bug Tracking System
Your message dated Tue, 30 Jun 2020 08:34:36 + with message-id and subject line Bug#959507: fixed in dub 1.19.0-1.1 has caused the Debian Bug report #959507, regarding dub: flaky autopkgtest: Package dub not found for registry at https://code.dlang.org/ to be marked as done. This means that

Bug#960880: marked as done (pev: autopkgtest failure: pehash did not report ASLR status)

2020-06-30 Thread Debian Bug Tracking System
Your message dated Tue, 30 Jun 2020 08:35:48 + with message-id and subject line Bug#960880: fixed in pev 0.80-5 has caused the Debian Bug report #960880, regarding pev: autopkgtest failure: pehash did not report ASLR status to be marked as done. This means that you claim that the problem has

Bug#963933: glib2.0: autopkgtext: ld: cannot find -lcryptsetup

2020-06-30 Thread Chris Hofstaedtler
* Simon McVittie [200629 01:16]: > On Sun, 28 Jun 2020 at 22:00:58 +0200, Chris Hofstaedtler wrote: > > the autopkgtest suite offers quite interesting behaviour: > > With an installed libcryptsetup-dev, ld fails with "cannot find > > -lcryptsetup". > ... > > I imagine this might be caused by libcr

Bug#963853: [Pkg-clamav-devel] Bug#963853: clamav: FTBFS on IPv6-only environments

2020-06-30 Thread Dominic Hargreaves
On Tue, Jun 30, 2020 at 08:28:15AM +0200, Sebastian Andrzej Siewior wrote: > On 2020-06-28 12:48:20 [+0100], Dominic Hargreaves wrote: > > Source: clamav > > Version: 0.102.3+dfsg-1 > > Severity: serious > > Justification: FTBFS (when it built before) > > > > During archive-wide test rebuilding of

Bug#955020: marked as done (php-horde-form: CVE-2020-8866)

2020-06-30 Thread Debian Bug Tracking System
Your message dated Tue, 30 Jun 2020 09:04:19 + with message-id and subject line Bug#955020: fixed in php-horde-form 2.0.20-1 has caused the Debian Bug report #955020, regarding php-horde-form: CVE-2020-8866 to be marked as done. This means that you claim that the problem has been dealt with.

Bug#955019: marked as done (php-horde-trean: CVE-2020-8865)

2020-06-30 Thread Debian Bug Tracking System
Your message dated Tue, 30 Jun 2020 09:04:25 + with message-id and subject line Bug#955019: fixed in php-horde-trean 1.1.10-1 has caused the Debian Bug report #955019, regarding php-horde-trean: CVE-2020-8865 to be marked as done. This means that you claim that the problem has been dealt with

Bug#963990: marked as done (libemf: FTBFS everywhere)

2020-06-30 Thread Debian Bug Tracking System
Your message dated Tue, 30 Jun 2020 09:18:51 + with message-id and subject line Bug#963990: fixed in libemf 1.0.13-2 has caused the Debian Bug report #963990, regarding libemf: FTBFS everywhere to be marked as done. This means that you claim that the problem has been dealt with. If this is no

Bug#963933: glib2.0: autopkgtext: ld: cannot find -lcryptsetup

2020-06-30 Thread Simon McVittie
On Tue, 30 Jun 2020 at 10:51:39 +0200, Chris Hofstaedtler wrote: > I'm not sure it was a good idea before. Is static linking something > you actively want to support for glib? It has worked in the past, Policy says the static library "is usually provided", and we occasionally get bug reports from

Bug#963335: marked as done (autogen: FTBFS: E: Build killed with signal TERM after 150 minutes of inactivity)

2020-06-30 Thread Debian Bug Tracking System
Your message dated Tue, 30 Jun 2020 09:34:30 + with message-id and subject line Bug#963335: fixed in make-dfsg 4.3-4 has caused the Debian Bug report #963335, regarding autogen: FTBFS: E: Build killed with signal TERM after 150 minutes of inactivity to be marked as done. This means that you

Bug#963734: marked as done (make: breaks autogen make check)

2020-06-30 Thread Debian Bug Tracking System
Your message dated Tue, 30 Jun 2020 09:34:30 + with message-id and subject line Bug#963335: fixed in make-dfsg 4.3-4 has caused the Debian Bug report #963335, regarding make: breaks autogen make check to be marked as done. This means that you claim that the problem has been dealt with. If thi

Bug#963933: glib2.0: autopkgtext: ld: cannot find -lcryptsetup

2020-06-30 Thread Chris Hofstaedtler
* Simon McVittie [200630 11:23]: > On Tue, 30 Jun 2020 at 10:51:39 +0200, Chris Hofstaedtler wrote: > > I'm not sure it was a good idea before. Is static linking something > > you actively want to support for glib? > > It has worked in the past, Policy says the static library "is usually > provid

Bug#963393: marked as pending in harvid

2020-06-30 Thread IOhannes zmölnig
Control: tag -1 pending Hello, Bug #963393 in harvid 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/multimedia-team/harvid/-/commit/b881a3e91f3edd5cefba1463441

Processed: Bug#963393 marked as pending in harvid

2020-06-30 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #963393 [src:harvid] harvid: FTBFS: Makefile:20: *** "libjpeg is required - install libjpeg-dev, libjpeg8-dev or libjpeg62-dev". Stop. Added tag(s) pending. -- 963393: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963393 Debian Bug Tracking

Bug#963393: marked as done (harvid: FTBFS: Makefile:20: *** "libjpeg is required - install libjpeg-dev, libjpeg8-dev or libjpeg62-dev". Stop.)

2020-06-30 Thread Debian Bug Tracking System
Your message dated Tue, 30 Jun 2020 11:18:47 + with message-id and subject line Bug#963393: fixed in harvid 0.8.3-2 has caused the Debian Bug report #963393, regarding harvid: FTBFS: Makefile:20: *** "libjpeg is required - install libjpeg-dev, libjpeg8-dev or libjpeg62-dev". Stop. to be mark

Bug#962424: zfsutils-linux: systemd zfs-mount-generator breaks boot if multiple datasets have the same mountpoint

2020-06-30 Thread Antonio Russo
Control: tags -1 +moreinfo Hello! Is that attached file literally what is in /etc/zfs/zfs-list.cache ? How was it generated, and how did it get there? Because it's wrong---it's space separated, and must be tab separated. Use -H, per man zfs-mount-generator, if it must be done by hand. Best,

Processed: Re: zfsutils-linux: systemd zfs-mount-generator breaks boot if multiple datasets have the same mountpoint

2020-06-30 Thread Debian Bug Tracking System
Processing control commands: > tags -1 +moreinfo Bug #962424 [zfsutils-linux] zfsutils-linux: systemd zfs-mount-generator breaks boot if multiple datasets have the same mountpoint Added tag(s) moreinfo. -- 962424: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962424 Debian Bug Tracking Syst

Bug#733094: uvcdynctrl still filling the disk

2020-06-30 Thread Simon John
Any movement on this, the issue was fixed upstream 5+ years ago but as of today, /lib/udev/uvcdynctrl in sid still contains debug=1 OK users can change that, but on the next upgrade it'll get reverted and fill the disk. Seems like a simple patch to change it to debug=0 by default and/or mark

Processed: severity of 962650 is serious

2020-06-30 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > severity 962650 serious Bug #962650 [src:libcamera] libcamera: API and ABI appear to be changing without a SONAME bump Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 96

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

2020-06-30 Thread Timo Jyrinki
Just to tie a loose end, it _does_ work fine on buster if you're actually on the latest kernel. If you have a long uptime and not rebooted, you will have these problems when it tries to compile wireguard for your currently used, old kernel, but there's no problem as such 4.19.0-9 anymore. -Timo

Processed: Bug#963419 marked as pending in kombu

2020-06-30 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #963419 [src:kombu] kombu: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.8 --system=custom "--test-args={interpreter} setup.py test" returned exit code 13 Added tag(s) pending. -- 963419: https://bugs.debian.o

Bug#963419: marked as pending in kombu

2020-06-30 Thread Michael Fladischer
Control: tag -1 pending Hello, Bug #963419 in kombu 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/kombu/-/commit/ae26cccabec9ec3d50dba5fed

Bug#963419: marked as done (kombu: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.8 --system=custom "--test-args={interpreter} setup.py test" returned exit code 13)

2020-06-30 Thread Debian Bug Tracking System
Your message dated Tue, 30 Jun 2020 13:49:12 + with message-id and subject line Bug#963419: fixed in kombu 4.6.11-1 has caused the Debian Bug report #963419, regarding kombu: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.8 --system=custom "--test-args={inter

Bug#963420: marked as done (zsh: FTBFS: sh: 1: colcrt: not found)

2020-06-30 Thread Debian Bug Tracking System
Your message dated Tue, 30 Jun 2020 16:19:40 + with message-id and subject line Bug#963420: fixed in zsh 5.8-5 has caused the Debian Bug report #963420, regarding zsh: FTBFS: sh: 1: colcrt: not found to be marked as done. This means that you claim that the problem has been dealt with. If this

Bug#964026: libelogind0: `Provides: libsystemd0` causes unrelated packages to fail to build (unmet dependencies)

2020-06-30 Thread Ansgar
Package: libelogind0 Version: 243.7-1+debian1 Severity: serious libelogind0's `Provides: libsystemd0` causes unrelated packages to fail to build due to unmet dependencies. See [1] for an example. The relevant log part is: +--- | The following packages have unmet dependencies: | libelogind0 : C

Bug#964026: libelogind0: `Provides: libsystemd0` causes unrelated packages to fail to build (unmet dependencies)

2020-06-30 Thread Mark Hindley
Ansgar, Thanks for this. On Tue, Jun 30, 2020 at 06:27:20PM +0200, Ansgar wrote: > Package: libelogind0 > Version: 243.7-1+debian1 > Severity: serious > > libelogind0's `Provides: libsystemd0` causes unrelated packages to > fail to build due to unmet dependencies. See [1] for an example. > > T

Bug#964027: incompatible with kernel 5.7.0: ERROR: modpost: "__pagevec_lru_add" [...] undefined!

2020-06-30 Thread Ryan Kavanagh
Package: openafs-modules-dkms Version: 1.8.6~pre1-3 Severity: grave Justification: package is not compatible with the current kernel The package cannot successfully be installed under 5.7.0-1-amd64. The build fails with: LD [M] /var/lib/dkms/openafs/1.8.6pre1/build/src/libafs/MODLOAD-5.7.0-1-

Bug#964027: incompatible with kernel 5.7.0: ERROR: modpost: "__pagevec_lru_add" [...] undefined!

2020-06-30 Thread Benjamin Kaduk
tags 964027 pending fixed-upstream thanks On Tue, Jun 30, 2020 at 12:48:41PM -0400, Ryan Kavanagh wrote: > Package: openafs-modules-dkms > Version: 1.8.6~pre1-3 > Severity: grave > Justification: package is not compatible with the current kernel > > The package cannot successfully be installed un

Processed: Re: Bug#964027: incompatible with kernel 5.7.0: ERROR: modpost: "__pagevec_lru_add" [...] undefined!

2020-06-30 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 964027 pending fixed-upstream Bug #964027 [openafs-modules-dkms] incompatible with kernel 5.7.0: ERROR: modpost: "__pagevec_lru_add" [...] undefined! Added tag(s) fixed-upstream and pending. > thanks Stopping processing here. Please contact

Bug#963975: blender: Blender crashes on launch (failed assert)

2020-06-30 Thread Alex Andreotti
Package: blender Version: 2.83.1+dfsg-1 Followup-For: Bug #963975 Dear Maintainer, I have updated to 2.83.1 + dfsg-1 and have the same problem (I don't remember if I used 2.81 or 2.82 previously but it worked) In my case, however, the fonts in question are not installed by blender-data, the fo

Bug#962424: zfsutils-linux: systemd zfs-mount-generator breaks boot if multiple datasets have the same mountpoint

2020-06-30 Thread Wxcafé
Sorry, it's been three weeks and lots of stuff happened since there, I don't know if I edited that file or not now, but I guess probably yeah. Here's something pulled from my server right now. Cheers On Tue, 2020-06-30 at 06:24 -0600, Antonio Russo wrote: > Control: tags -1 +moreinfo > > Hello!

Bug#964026: libelogind0: `Provides: libsystemd0` causes unrelated packages to fail to build (unmet dependencies)

2020-06-30 Thread Ansgar
On Tue, 2020-06-30 at 17:45 +0100, Mark Hindley wrote: > I am struggling to understand how libelogind0 came to be installed in the > build > in the first place. Can you help me understand that? No idea; apt's resolver is sometimes creative. Other examples include [1], [2], [3]. [1]: https://

Bug#937490: pynifti: Python2 removal in sid/bullseye

2020-06-30 Thread Moritz Mühlenhoff
On Mon, Jun 29, 2020 at 08:41:26PM +0200, Michael Hanke wrote: > Hi, > > yes, that sounds like to best course of action to me. Ack, I've filed an RM bug. Cheers, Moritz

Bug#960762: libvirt: random (?) test hangs

2020-06-30 Thread Andrea Bolognani
On Sat, May 16, 2020 at 03:00:46PM +0300, Adrian Bunk wrote: > Source: libvirt > Version: 6.0.0-7 > Severity: serious > Tags: ftbfs > > https://buildd.debian.org/status/fetch.php?pkg=libvirt&arch=all&ver=6.0.0-7&stamp=1589452859&raw=0 > https://buildd.debian.org/status/fetch.php?pkg=libvirt&arch=i

Processed: cloning 948989, reassign -1 to src:ksh93

2020-06-30 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > clone 948989 -1 Bug #948989 {Done: Boyuan Yang } [src:ksh] ksh: CVE-2019-14868 Bug 948989 cloned as bug 964034 > reassign -1 src:ksh93 93u+20120801-7 Bug #964034 {Done: Boyuan Yang } [src:ksh] ksh: CVE-2019-14868 Bug reassigned from package 'src:k

Processed: Both ship /etc/skel/.kshrc

2020-06-30 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > fixed 950762 ksh/2020.0.0+really93u+20120801-6 Bug #950762 [ksh,ksh93] ksh,ksh93: both ship /etc/skel/.kshrc with insufficient Conflicts/Breaks/Replaces Marked as fixed in versions ksh/2020.0.0+really93u+20120801-6. > thanks Stopping processing h

Processed: retitle 964034 to ksh93: CVE-2019-14868, reopening 964034

2020-06-30 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > retitle 964034 ksh93: CVE-2019-14868 Bug #964034 {Done: Boyuan Yang } [src:ksh93] ksh: CVE-2019-14868 Changed Bug title to 'ksh93: CVE-2019-14868' from 'ksh: CVE-2019-14868'. > reopen 964034 Bug #964034 {Done: Boyuan Yang } [src:ksh93] ksh93: CV

Bug#963325: marked as pending in alot

2020-06-30 Thread Jordan Justen
Control: tag -1 pending Hello, Bug #963325 in alot 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/applications/alot/-/commit/1f5013b4619ec108a0cc99

Processed: Bug#963325 marked as pending in alot

2020-06-30 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #963325 [src:alot] alot: FTBFS: dh_auto_test: error: pybuild --test -i python{version} -p 3.8 returned exit code 13 Added tag(s) pending. -- 963325: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963325 Debian Bug Tracking System Contact ow..

Processed: src:quickfix: fails to migrate to testing for too long: FTBFS on i386

2020-06-30 Thread Debian Bug Tracking System
Processing control commands: > close -1 1.15.1+dfsg-4 Bug #964037 [src:quickfix] src:quickfix: fails to migrate to testing for too long: FTBFS on i386 Marked as fixed in versions quickfix/1.15.1+dfsg-4. Bug #964037 [src:quickfix] src:quickfix: fails to migrate to testing for too long: FTBFS on i

Bug#964037: src:quickfix: fails to migrate to testing for too long: FTBFS on i386

2020-06-30 Thread Paul Gevers
Source: quickfix Version: 1.15.1+dfsg-3 Severity: serious Control: close -1 1.15.1+dfsg-4 Tags: sid bullseye User: release.debian@packages.debian.org Usertags: out-of-sync Dear maintainer(s), As recently announced [1], the Release Team now considers packages that are out-of-sync between testi

Bug#964039: vg: FTBFS on mips64el

2020-06-30 Thread Sebastian Ramacher
Source: vg Version: 1.25.0+ds-1 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) vg failed to build on mips64el: | Test Summary Report | --- | t/34_vg_pack.t (Wstat: 0 Tests: 18 Failed: 2) | Failed tests: 16-17 | t

Bug#964040: git-buildpackage: FTBFS: E741 ambiguous variable name 'l'

2020-06-30 Thread Niko Tyni
Source: git-buildpackage Version: 0.9.19 Severity: serious Tags: ftbfs This package fails to build on current sid. >From my build log: make[2]: Entering directory '/<>' flake8 ./.pybuild/cpython3_3.8/build/gbp/patch_series.py:108:81: E741 ambiguous variable name 'l' ./.pybuild/cpython3

Bug#964041: git-repair: FTBFS: duration parse error

2020-06-30 Thread Niko Tyni
Source: git-repair Version: 1.20200102-1 Severity: serious Tags: ftbfs This package fails to build on current sid. >From my build log: [21 of 69] Compiling Utility.HumanTime ( Utility/HumanTime.hs, dist/build/git-repair/git-repair-tmp/Utility/HumanTime.o ) Utility/HumanTime.hs:58:21: err

Bug#964042: gitaly: FTBFS: 'go install' fails

2020-06-30 Thread Niko Tyni
Source: gitaly Version: 1.78.0+dfsg-2 Severity: serious Tags: ftbfs This package fails to build on current sid. >From my build log: dh_auto_build: error: cd obj-x86_64-linux-gnu && go install -trimpath -v -p 16 -ldflags "-X gitlab.com/gitlab-org/gitaly/internal/version.version=1.78.0" gitlab

Bug#964044: mrpt: FTBFS: test failure

2020-06-30 Thread Sebastian Ramacher
Source: mrpt Version: 1:2.0.4-1 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) binNMUs of mrpt failed to build: | [--] 1 test from RawlogGrabberApp | [ RUN ] RawlogGrabberApp.CGenericCamera_AVI | [CCameraSensor::initialize]

Bug#964043: golang-github-caarlos0-env: FTBFS: TestParseInvalidURL fails

2020-06-30 Thread Niko Tyni
Source: golang-github-caarlos0-env Version: 6.0.0-1 Severity: serious Tags: ftbfs This package fails to build on current sid. >From my build log: dh_auto_test -O--buildsystem=golang cd obj-x86_64-linux-gnu && go test -vet=off -v -p 4 github.com/caarlos0/env === RUN TestParsesEn

Bug#964045: golang-github-shirou-gopsutil: FTBFS: Test_Process_memory_maps failure

2020-06-30 Thread Niko Tyni
Source: golang-github-shirou-gopsutil Version: 2.19.11-1 Severity: serious Tags: ftbfs This package fails to build from source on current sid. >From my build log: === RUN Test_SendSignal --- PASS: Test_SendSignal (0.00s) === RUN Test_Pids --- PASS: Test_Pids (0.00s) === RUN

Bug#937645: python-cjson: Python2 removal in sid/bullseye

2020-06-30 Thread Moritz Mühlenhoff
On Fri, Aug 30, 2019 at 07:37:25AM +, Matthias Klose wrote: > Package: src:python-cjson > Version: 1.2.1-1 > 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 from th

Bug#964046: python3-skimage: missing (unversioned) Breaks+Replaces: python-skimage

2020-06-30 Thread Andreas Beckmann
Package: python3-skimage Version: 0.17.2-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'stable'. It installed fine in 'stable', then the upgrade to 'sid' fails because it tries to overwrite othe

Bug#964048: golang-github-tsenart-tb: FTBFS: TestThrottler_Wait failure

2020-06-30 Thread Niko Tyni
Source: golang-github-tsenart-tb Version: 0.0~git20151208.0.19f4c3d-2 Severity: serious Tags: ftbfs This package fails to build on current sid. >From my build log: --- PASS: TestBucket_Take_throughput (1.70s) TestBucket_Wait: bucket_test.go:178: bucket.Wait(2000) with cap=1000, freq=1ms

Bug#964047: golang-github-src-d-gcfg: FTBFS: TestScanFully failure

2020-06-30 Thread Niko Tyni
Source: golang-github-src-d-gcfg Version: 1.4.0-1 Severity: serious Tags: ftbfs This package fails to build on current sid. >From my build log: === RUN TestEnumParserBool TestEnumParserBool: enum_test.go:26: "tRuE": got true, TestEnumParserBool: enum_test.go:26: "False": got fal

Bug#937645: python-cjson: Python2 removal in sid/bullseye

2020-06-30 Thread Bernd Zeimetz
On 6/30/20 10:41 PM, Moritz Mühlenhoff wrote: > There's no movement on https://github.com/AGProjects/python-cjson/issues/6 > and at this point there are no reverse dependencies left, let's remove it? yes, good plan - I've filed a ROM removal bug. Bernd -- Bernd Zeimetz

Bug#964042: [pkg-go] Bug#964042: gitaly: FTBFS: 'go install' fails

2020-06-30 Thread Pirate Praveen
On 2020, ജൂലൈ 1 1:57:21 AM IST, Niko Tyni wrote: >Source: gitaly >Version: 1.78.0+dfsg-2 >Severity: serious >Tags: ftbfs > >This package fails to build on current sid. The version in experimental works, but it is blocked by rails 6 transition. Around first week of August, we plan to upload ra

Bug#964053: haskell-diagrams-gtk: FTBFS: Encountered missing or private dependencies

2020-06-30 Thread Niko Tyni
Source: haskell-diagrams-gtk Version: 1.4-6 Severity: serious Tags: ftbfs This package fails to build on current sid. >From my build log: Configuring diagrams-gtk-1.4... CallStack (from HasCallStack): die', called at libraries/Cabal/Cabal/Distribution/Simple/Configure.hs:1022:20 in Cab

Bug#964055: hddemux: FTBFS: failed to query server

2020-06-30 Thread Niko Tyni
Source: hddemux Version: 0.4-7 Severity: serious Tags: ftbfs This package fails to build on current sid. >From my build log: Signing certificate... make knot-resolver configuration on 127.64.173.140:8853 --- make hddeumx configur

Bug#964056: Should ksh93 be removed?

2020-06-30 Thread Adrian Bunk
Package: ksh93 Severity: serious ksh (2020.0.0+really93u+20120801-6) unstable; urgency=high * v2020 of ksh is no longer being maintained and upstream repository has been reverted back to the last stable version of 93u+. This update reverts back the ksh2020 changes back to the original k

Bug#937645: [Python-modules-team] Bug#937645: python-cjson: Python2 removal in sid/bullseye

2020-06-30 Thread Emmanuel Arias
Cheers, Arias Emmanuel @eamanu http://eamanu.com El mar., 30 de jun. de 2020 a la(s) 17:51, Bernd Zeimetz (b...@debian.org) escribió: > > > > On 6/30/20 10:41 PM, Moritz Mühlenhoff wrote: > > There's no movement on https://github.com/AGProjects/python-cjson/issues/6 > > and at this point there ar

Bug#964056: Should ksh93 be removed?

2020-06-30 Thread Anuradha Weeraman
On Wed, Jul 01, 2020 at 12:40:17AM +0300, Adrian Bunk wrote: > Package: ksh93 > Severity: serious > > ksh (2020.0.0+really93u+20120801-6) unstable; urgency=high > > * v2020 of ksh is no longer being maintained and upstream repository has > been reverted back to the last stable version of 93

Bug#964053: marked as done (haskell-diagrams-gtk: FTBFS: Encountered missing or private dependencies)

2020-06-30 Thread Debian Bug Tracking System
Your message dated Tue, 30 Jun 2020 22:33:59 + with message-id and subject line Bug#964053: fixed in haskell-diagrams-gtk 1.4-7 has caused the Debian Bug report #964053, regarding haskell-diagrams-gtk: FTBFS: Encountered missing or private dependencies to be marked as done. This means that y

Processed: closing 964042

2020-06-30 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > close 964042 13.1.0+dfsg-1 Bug #964042 [src:gitaly] gitaly: FTBFS: 'go install' fails Marked as fixed in versions gitaly/13.1.0+dfsg-1. Bug #964042 [src:gitaly] gitaly: FTBFS: 'go install' fails Marked Bug as done > thanks Stopping processing here

Processed: tagging 964048

2020-06-30 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 964048 + bullseye sid Bug #964048 [src:golang-github-tsenart-tb] golang-github-tsenart-tb: FTBFS: TestThrottler_Wait failure Added tag(s) bullseye and sid. > thanks Stopping processing here. Please contact me if you need assistance. -- 964

Bug#960073: Package:python-pyqt5 Run the example code with Trace and crash (SIGABRT)【请注意,邮件由mity...@gmail.com代发】

2020-06-30 Thread pengzon...@uniontech.com
Hi! Some information on this, it look like the same issue as #963709. (gdb) r PnsAppWebX.py Starting program: /usr/bin/python PnsAppWebX.py [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/aarch64-linux-gnu/libthread_db.so.1". [New Thread 0xe6bc41e0 (LWP 2

Bug#964027: marked as done (incompatible with kernel 5.7.0: ERROR: modpost: "__pagevec_lru_add" [...] undefined!)

2020-06-30 Thread Debian Bug Tracking System
Your message dated Wed, 01 Jul 2020 06:05:18 + with message-id and subject line Bug#964027: fixed in openafs 1.8.6-1 has caused the Debian Bug report #964027, regarding incompatible with kernel 5.7.0: ERROR: modpost: "__pagevec_lru_add" [...] undefined! to be marked as done. This means that