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

Your message dated Wed, 15 Jan 2020 09:15:49 +0200 with message-id and subject line Re: Bug#947748: xorg-server: FTBFS in sid (probably due to newer mesa) has caused the Debian Bug report #947748, regarding xorg-server: FTBFS in sid (probably due to newer mesa) to be marked as done. This means

Bug#948393: marked as done (foxtrotgps: fails to connect to gpsd despite SUCCESS message)

Your message dated Wed, 15 Jan 2020 06:34:14 + with message-id and subject line Bug#948393: fixed in foxtrotgps 1.2.2-2 has caused the Debian Bug report #948393, regarding foxtrotgps: fails to connect to gpsd despite SUCCESS message to be marked as done. This means that you claim that the

Bug#946624: marked as done (python-scipy: autopkgtest regularly times out)

Your message dated Wed, 15 Jan 2020 06:12:56 + with message-id and subject line Bug#948946: Removed package(s) from unstable has caused the Debian Bug report #946624, regarding python-scipy: autopkgtest regularly times out to be marked as done. This means that you claim that the problem has

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

Your message dated Wed, 15 Jan 2020 06:12:56 + with message-id and subject line Bug#948946: Removed package(s) from unstable has caused the Debian Bug report #938157, regarding python-scipy: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has

Bug#948937: marked as done (gr-fcdproplus FTBFS missing build-dependencies on dh-python and liborc-0.4-dev)

Your message dated Wed, 15 Jan 2020 05:34:17 + with message-id and subject line Bug#948937: fixed in gr-fcdproplus 3.8~20190817-3 has caused the Debian Bug report #948937, regarding gr-fcdproplus FTBFS missing build-dependencies on dh-python and liborc-0.4-dev to be marked as done. This

Bug#948828: marked as done (python-whoosh ftbfs in unstable)

On Mon, Jan 13, 2020, 3:42 PM Debian Bug Tracking System < ow...@bugs.debian.org> wrote: > Your message dated Mon, 13 Jan 2020 15:39:25 -0500 > with message-id ffovz...@mail.gmail.com> > and subject line Re: [Python-modules-team] Bug#948828: python-whoosh ftbfs > in unstable > has caused the

Bug#948938: marked as done (gr-iqbal FTBFS missing build-dependency on dh-python)

Your message dated Wed, 15 Jan 2020 05:04:11 + with message-id and subject line Bug#948938: fixed in gr-iqbal 0.38-4 has caused the Debian Bug report #948938, regarding gr-iqbal FTBFS missing build-dependency on dh-python to be marked as done. This means that you claim that the problem has

Processed (with 1 error): your mail

Processing commands for cont...@bugs.debian.org: > # Reassign and forcemerge to properly > # deal with this false XCA FTBFS bug. > # These commands written at the suggestion of > # the #debian-devel IRC channel. > reassign 947328 debhelper 12.7.1 Bug #947328 {Done: Thomas Ward } [src:xca] FTBFS:

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

On Mon, Jan 13, 2020 at 9:08 PM Drew Parsons wrote: > > On 2020-01-14 02:13, Sandro Tosi wrote: > >> >It's just that there is no extra effort required in this case. > >> >python3-scipy does indeed need the effort taken, but once that effort > >> >is > >> >done, it's no more effort to apply the

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

Your message dated Wed, 15 Jan 2020 03:34:51 + with message-id and subject line Bug#937580: fixed in python-argcomplete 1.8.1-1.1 has caused the Debian Bug report #937580, regarding python-argcomplete: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the

Processed: py2removal bugs severity updates - 2020-01-15 03:36:05.154125+00:00

Processing commands for cont...@bugs.debian.org: > # This is an automated script, part of the effort for the removal of Python 2 > from bullseye > # * https://wiki.debian.org/Python/2Removal > # * http://sandrotosi.me/debian/py2removal/index.html > # See

Processed: retitle 849087 to gourmet: Port to Python 3 and python3-gst-1.0

Processing commands for cont...@bugs.debian.org: > retitle 849087 gourmet: Port to Python 3 and python3-gst-1.0 Bug #849087 [src:gourmet] Port to Python 3 and python3-gst-1.0 Bug #936641 [src:gourmet] gourmet: Python2 removal in sid/bullseye Changed Bug title to 'gourmet: Port to Python 3 and

Bug#937580: python-argcomplete: diff for NMU version 1.8.1-1.1

Control: tags 937580 + patch Dear maintainer, I've prepared an NMU for python-argcomplete (versioned as 1.8.1-1.1). The diff is attached to this message. Please consider maintaining this package with DPMT Regards. diff -Nru python-argcomplete-1.8.1/debian/changelog

Processed: python-argcomplete: diff for NMU version 1.8.1-1.1

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

Processed: tagging 948393

Processing commands for cont...@bugs.debian.org: > # not an optimal patch > tags 948393 - patch Bug #948393 [foxtrotgps] foxtrotgps: fails to connect to gpsd despite SUCCESS message Removed tag(s) patch. > thanks Stopping processing here. Please contact me if you need assistance. -- 948393:

Bug#948942: pglogical: FTBFS: mismatch with the default postgres

Source: pglogical Version: 2.2.2-1 Severity: serious Tags: ftbfs Dear maintainer, your package failed to rebuild in a standard sid/amd64 chroot. Attached is the full build log, hopefully relevant excerpt follows: dpkg-buildpackage: info: source package pglogical dpkg-buildpackage: info: source

Bug#948943: php-solr: FTBFS: all tests fail

Source: php-solr Version: 2.5.0-1 Severity: serious Tags: ftbfs Dear maintainer, your package failed to rebuild in a standard sid/amd64 chroot. Attached is the full build log, hopefully relevant excerpt follows: = TIME END

Processed: tagging 948917 ..., found 948914 in 0~1.0-2 ..., tagging 948914 ..., tagging 948876, tagging 948859 ...

Processing commands for cont...@bugs.debian.org: > tags 948917 + sid bullseye Bug #948917 [src:screengrab] FTBFS: No rule to make target '/usr/lib/x86_64-linux-gnu/libglib-2.0.so' Added tag(s) sid and bullseye. > retitle 948917 screengrab: FTBFS: No rule to make target >

Bug#948257: depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could not open builtin file '/var/tmp/mkinitramfs_N1a1Mk/lib/modules/5.4.0-1-amd64/modules.builtin.bin'

Package: initramfs-tools Version: 0.135 Followup-For: Bug #948257 Just want to confirm Pierrick's observation that rolling back kmod and libkmod2 to version 26-3 fixes the logspam.

Bug#948940: FTBFS: /plugins/owncloud-ui/owncloud.cpp:54:23: error: invalid use of incomplete type ‘class QWindow’

Source: kaccounts-providers Version: 4:17.08.3-1 Severity: serious Tags: ftbfs Justification: FTBFS on all archs Hi! During a rebuild of your package it FTBFS with the following error: /plugins/owncloud-ui/owncloud.cpp:54:23: error: invalid use of incomplete type ‘class QWindow’ The build logs

Bug#948939: FTBFS: rkward/windows/rkworkplace.cpp:71:2: error: ‘QVBoxLayout’ was not declared in this scope

Source: rkward Version: 0.7.0b-1.1 Severity: serious Tags: ftbfs Justification: FTBFS on all archs Hi! During a rebuild of your package it FTBFS with the following error: /<>/rkward/windows/../dataeditor/twintable.h:117:7: warning: ‘virtual void TwinTable::objectMetaChanged(RObject*)’ can be

Bug#947996: marked as done (golang-github-mailru-easyjson FTBFS in testing/unstable)

Your message dated Wed, 15 Jan 2020 00:34:08 + with message-id and subject line Bug#947996: fixed in golang-github-mailru-easyjson 0.7.0-1 has caused the Debian Bug report #947996, regarding golang-github-mailru-easyjson FTBFS in testing/unstable to be marked as done. This means that you

Bug#948268: marked as done (Crashes after startup)

Your message dated Wed, 15 Jan 2020 00:35:12 + with message-id and subject line Bug#948268: fixed in slirp 1:1.0.17-9 has caused the Debian Bug report #948268, regarding Crashes after startup to be marked as done. This means that you claim that the problem has been dealt with. If this is not

Bug#948937: gr-fcdproplus FTBFS missing build-dependencies on dh-python and liborc-0.4-dev

Package: gr-fcdproplus Version: 3.8~20190817-2 Severity: serious Tags: patch. gr-fcdproplus fails to build due to a missing dh-python, I initially noticed this on a raspbian autobuilder, but it's also happening on the reproducible builds site, so it's not raspbian specific. dh: unable to

Bug#948938: gr-iqbal FTBFS missing build-dependency on dh-python

Package: gr-iqbal Version: 0.38-3 Severity: serious Tags: patch gr-rds FTBFS due to a missing build-dependency on dh-python, dh clean --with python3 dh: unable to load addon python3: Can't locate Debian/Debhelper/Sequence/python3.pm in @INC (you may need to install the

Bug#948936: gr-rds FTBFS missing build-dependency on dh-python

Package: gr-rds Version: 3.8.0.0.f1c584a-2 Severity: serious Tags: patch gr-rds FTBFS due to a missing build-dependency on dh-python, dh clean --with python3 dh: unable to load addon python3: Can't locate Debian/Debhelper/Sequence/python3.pm in @INC (you may need to install the

Processed: RM python-wxmpl

Processing control commands: > reassign -1 ftp.debian.org Bug #938269 [src:python-wxmpl] python-wxmpl: Python2 removal in sid/bullseye Bug reassigned from package 'src:python-wxmpl' to 'ftp.debian.org'. No longer marked as found in versions python-wxmpl/2.0.0-2.1. Ignoring request to alter fixed

Bug#938269: RM python-wxmpl

Control: reassign -1 ftp.debian.org Control: retitle -1 RM: python-wxmpl -- RoQA; dead upstream; unmaintained; low popcon; blocking py2 removal

Bug#937033: marked as done (mgltools-scenario2: Python2 removal in sid/bullseye)

Your message dated Tue, 14 Jan 2020 23:20:40 + with message-id and subject line Bug#948879: Removed package(s) from unstable has caused the Debian Bug report #937033, regarding mgltools-scenario2: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the

Processed: Bug#947996 marked as pending in golang-github-mailru-easyjson

Processing control commands: > tag -1 pending Bug #947996 [src:golang-github-mailru-easyjson] golang-github-mailru-easyjson FTBFS in testing/unstable Added tag(s) pending. -- 947996: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947996 Debian Bug Tracking System Contact

Bug#768898: marked as done (libmapper: Unsuitable for Testing, please keep it in Unstable for a while)

Your message dated Tue, 14 Jan 2020 23:21:55 + with message-id and subject line Bug#948883: Removed package(s) from unstable has caused the Debian Bug report #768898, regarding libmapper: Unsuitable for Testing, please keep it in Unstable for a while to be marked as done. This means that

Bug#937037: marked as done (mgltools-utpackages: Python2 removal in sid/bullseye)

Your message dated Tue, 14 Jan 2020 23:21:05 + with message-id and subject line Bug#948880: Removed package(s) from unstable has caused the Debian Bug report #937037, regarding mgltools-utpackages: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the

Bug#768901: marked as done (python-libmapper: Unsuitable for Testing, please keep it in Unstable for a while)

Your message dated Tue, 14 Jan 2020 23:21:55 + with message-id and subject line Bug#948883: Removed package(s) from unstable has caused the Debian Bug report #768898, regarding python-libmapper: Unsuitable for Testing, please keep it in Unstable for a while to be marked as done. This means

Bug#936891: marked as done (libmapper: Python2 removal in sid/bullseye)

Your message dated Tue, 14 Jan 2020 23:21:55 + with message-id and subject line Bug#948883: Removed package(s) from unstable has caused the Debian Bug report #936891, regarding libmapper: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has

Bug#947996: marked as pending in golang-github-mailru-easyjson

Control: tag -1 pending Hello, Bug #947996 in golang-github-mailru-easyjson 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:

Bug#937042: marked as done (mgltools-webservices: Python2 removal in sid/bullseye)

Your message dated Tue, 14 Jan 2020 23:23:12 + with message-id and subject line Bug#948893: Removed package(s) from unstable has caused the Debian Bug report #937042, regarding mgltools-webservices: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the

Bug#937038: marked as done (mgltools-viewerframework: Python2 removal in sid/bullseye)

Your message dated Tue, 14 Jan 2020 23:21:29 + with message-id and subject line Bug#948882: Removed package(s) from unstable has caused the Debian Bug report #937038, regarding mgltools-viewerframework: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the

Bug#937039: marked as done (mgltools-vision: Python2 removal in sid/bullseye)

Your message dated Tue, 14 Jan 2020 23:22:19 + with message-id and subject line Bug#948887: Removed package(s) from unstable has caused the Debian Bug report #937039, regarding mgltools-vision: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem

Bug#937030: marked as done (mgltools-pyautodock: Python2 removal in sid/bullseye)

Your message dated Tue, 14 Jan 2020 23:20:06 + with message-id and subject line Bug#948878: Removed package(s) from unstable has caused the Debian Bug report #937030, regarding mgltools-pyautodock: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the

Bug#768900: marked as done (libmapper-dev: Unsuitable for Testing, please keep it in Unstable for a while)

Your message dated Tue, 14 Jan 2020 23:21:55 + with message-id and subject line Bug#948883: Removed package(s) from unstable has caused the Debian Bug report #768898, regarding libmapper-dev: Unsuitable for Testing, please keep it in Unstable for a while to be marked as done. This means

Bug#937041: marked as done (mgltools-volume: Python2 removal in sid/bullseye)

Your message dated Tue, 14 Jan 2020 23:22:41 + with message-id and subject line Bug#948889: Removed package(s) from unstable has caused the Debian Bug report #937041, regarding mgltools-volume: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem

Bug#936488: marked as done (epylog: Python2 removal in sid/bullseye)

Your message dated Tue, 14 Jan 2020 23:23:36 + with message-id and subject line Bug#948896: Removed package(s) from unstable has caused the Debian Bug report #936488, regarding epylog: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has been

Bug#948257: depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could not open builtin file '/var/tmp/mkinitramfs_XXXXXXX/lib/modules/5.4.0-1-amd64/modules.builtin.bin'

Yes, this fix https://salsa.debian.org/kernel-team/initramfs-tools/merge_requests/23/diffs indeed at least silenced (maybe fixed) those wornings after update-initramfs -u Hope you will pull that in initramfs-tools-core as shown by dpkg -S ./mkinitramfs And *I hope* it will happen faster than

Processed: tagging 948393

Processing commands for cont...@bugs.debian.org: > tags 948393 + patch Bug #948393 [foxtrotgps] foxtrotgps: fails to connect to gpsd despite SUCCESS message Added tag(s) patch. > thanks Stopping processing here. Please contact me if you need assistance. -- 948393:

Bug#948935: pius ftbfs, doesn't install multiple build dependencies

Package: src:pius Version: 3.0.0-1 Severity: serious Tags:sid bullseye patch pius ftbfs, doesn't install multiple build dependencies. The alternatives in the b-d are bogus. please just b-d on python3-all. patch at http://launchpadlibrarian.net/460610285/pius_3.0.0-1build1_3.0.0-1ubuntu1.diff.gz

Bug#948777: marked as done (viking: FTBFS error: incompatible types when initializing type 'time_t')

Your message dated Tue, 14 Jan 2020 22:06:53 + with message-id and subject line Bug#948777: fixed in viking 1.7-2 has caused the Debian Bug report #948777, regarding viking: FTBFS error: incompatible types when initializing type 'time_t' to be marked as done. This means that you claim that

Processed: severity of 948393 is serious

Processing commands for cont...@bugs.debian.org: > severity 948393 serious Bug #948393 [foxtrotgps] foxtrotgps: fails to connect to gpsd despite SUCCESS message Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 948393:

Bug#948388: navit: fails to connect to gpsd

Hi, On 1/9/20 12:43 AM, Paul Wise wrote: > On Wed, 2020-01-08 at 23:45 +0100, Bernd Zeimetz wrote: > >> If necessary I can upload 3.19 to unstable again as 3.20-1+3.19 or so. > > Personally, I think just go ahead with the transition, inform the > release team of the ABI break and file the

Processed: severity of 948388 is serious

Processing commands for cont...@bugs.debian.org: > severity 948388 serious Bug #948388 [navit] navit: fails to connect to gpsd Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 948388:

Bug#948930: python-socksipychain: autopkgtest regression: No module named sockschain

Source: python-socksipychain Version: 2.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 python-socksipychain the autopkgtest of python-socksipychain fails in testing when that

Bug#948918: marked as done (libbiod FTBFS on i386)

Your message dated Tue, 14 Jan 2020 21:35:38 + with message-id and subject line Bug#948918: fixed in libbiod 0.2.3+git20191120.b8eecef-2 has caused the Debian Bug report #948918, regarding libbiod FTBFS on i386 to be marked as done. This means that you claim that the problem has been dealt

Processed: py2removal bugs severity updates - 2020-01-14 21:35:57.381298+00:00

Processing commands for cont...@bugs.debian.org: > # This is an automated script, part of the effort for the removal of Python 2 > from bullseye > # * https://wiki.debian.org/Python/2Removal > # * http://sandrotosi.me/debian/py2removal/index.html > # See

Processed: severity of 943015 is serious, severity of 943073 is serious, severity of 943066 is serious ...

Processing commands for cont...@bugs.debian.org: > severity 943015 serious Bug #943015 [src:fonts-ebgaramond] fonts-ebgaramond: Python2 removal in sid/bullseye Severity set to 'serious' from 'normal' > severity 943073 serious Bug #943073 [src:fonts-fantasque-sans] fonts-fantasque-sans: Python2

Bug#948929: mawk: autopkgtest regression: new output to stderr

Source: mawk Version: 1.3.3-19 X-Debbugs-CC: debian...@lists.debian.org Severity: serious User: debian...@lists.debian.org Usertags: regression Dear maintainers, With a recent upload of mawk the autopkgtest of mawk fails in testing when that autopkgtest is run with the binary packages of mawk

Bug#948931: sumo-tools depends on both python and python3

Package: sumo-tools Version: 1.3.1-5 Severity: serious Tags: sid bullseye sumo-tools depends on both python and python3. Is this really intended?

Bug#948925: pbseqlib ftbfs with libpbbam1.0.6

Hi Paul, thanks for your bug report. On Tue, Jan 14, 2020 at 09:45:59PM +0100, Paul Gevers wrote: > Source: pbseqlib > Version: 5.3.1+dfsg-2.1 > Severity: serious > Justification: ftbfs > Tags: ftbfs sid bullseye > > Dear maintainer, > > pbbam started a transition and I scheduled binNMUs for

Bug#948926: blasr ftbfs with libpbbam1.0.6

Source: blasr Version: 5.3.3+dfsg-2 Severity: serious Justification: ftbfs Tags: ftbfs sid bullseye Dear maintainer, pbbam started a transition and I scheduled binNMUs for blasr. However, they failed. Please investigate. Paul https://buildd.debian.org/status/package.php?p=blasr Tail of log

Bug#948925: pbseqlib ftbfs with libpbbam1.0.6

Source: pbseqlib Version: 5.3.1+dfsg-2.1 Severity: serious Justification: ftbfs Tags: ftbfs sid bullseye Dear maintainer, pbbam started a transition and I scheduled binNMUs for pbseqlib. However, they failed. Please investigate. Paul https://buildd.debian.org/status/package.php?p=pbseqlib

Processed: Re: Bug#948919: sambamba FTBFS: undefined reference to 'cram_to_bam'

Processing control commands: > tags -1 help Bug #948919 [src:sambamba] sambamba FTBFS: undefined reference to 'cram_to_bam' Added tag(s) help. > tags -1 upstream Bug #948919 [src:sambamba] sambamba FTBFS: undefined reference to 'cram_to_bam' Added tag(s) upstream. > forwarded -1 Pjotr Prins Bug

Bug#915209: Info received (perl: FTBFS in the year 2020: cpan/Time-Local/t/Local.t failure)

On Tue, Jan 14, 2020 at 03:26:33PM +1100, Dean Hamstead wrote: > The attached patch is for 5.24.1 old-stable and is derived from > https://rt.cpan.org/Public/Bug/Display.html?id=124787 Thanks! I'll try to get this in the next oldstable point release, currently scheduled for February. -- Niko

Bug#944455: marked as done (pgcli: missing dependency on python3-pkg-resources)

Your message dated Tue, 14 Jan 2020 20:44:20 + with message-id and subject line Bug#944455: fixed in pgcli 2.2.0-3 has caused the Debian Bug report #944455, regarding pgcli: missing dependency on python3-pkg-resources to be marked as done. This means that you claim that the problem has been

Bug#948919: sambamba FTBFS: undefined reference to 'cram_to_bam'

Control: tags -1 help Control: tags -1 upstream Control: forwarded -1 Pjotr Prins Hi Matthias and Pjotr, I'd like to forward another bug in Sambabma. Any idea how to finally get sambamba build smoothly? Kind regards Andreas. On Tue, Jan 14, 2020 at 08:32:08PM +0200, Juhani Numminen

Processed: Re: Bug#948901: open-infrastructure-service-tools: FTBFS: a2x: error: argument --asciidoc-opts: expected one argument

Processing commands for cont...@bugs.debian.org: > tag 948901 + pending Bug #948901 [src:open-infrastructure-service-tools] open-infrastructure-service-tools: FTBFS: a2x: error: argument --asciidoc-opts: expected one argument Added tag(s) pending. > tag 948902 + pending Bug #948902

Bug#948756: scgi: should this package be removed?

Latest code is on github: https://github.com/nascheme/scgi Latest commit was in Sept 2019. I would upload a new package to Debian but my GPG key has been removed and I have not yet been able to find someone to sign a new key for me. OTOH, I don't object to removing the package from Debian

Bug#948901: open-infrastructure-service-tools: FTBFS: a2x: error: argument --asciidoc-opts: expected one argument

tag 948901 + pending tag 948902 + pending tag 948903 + pending thanks On 1/14/20 5:40 PM, Mattia Rizzolo wrote: > your package failed to rebuild in a standard sid chroot. thanks for the reports. asciidoc changed the order of arguments or something like that, I already fixed it in one of my

Processed: Oops, I filed a bug against the wrong package...

Processing commands for cont...@bugs.debian.org: > reassign 948919 src:sambamba Bug #948919 [src:libbiod] sambamba FTBFS: undefined reference to 'cram_to_bam' Bug reassigned from package 'src:libbiod' to 'src:sambamba'. No longer marked as found in versions libbiod/0.7.1-1. Ignoring request to

Bug#948920: package build-depends on python-doc

Package: src:python-gmusicapi Version: 12.1.1-2 Severity: serious Tags: sid bullseye The package build-depends on python-doc, but uses Python3 otherwise.

Processed: sambamba and libbiod FTBFS blocking libundead removal

Processing commands for cont...@bugs.debian.org: > block 908670 by 948918 948919 Bug #908670 [ftp.debian.org] ROM: libundead: Please remove this package from Debian 908670 was not blocked by any bugs. 908670 was not blocking any bugs. Added blocking bug(s) of 908670: 948919 and 948918 > thanks

Bug#948919: sambamba FTBFS: undefined reference to 'cram_to_bam'

Source: libbiod Version: 0.7.1-1 Severity: serious Tags: ftbfs Hello, This new FTBFS is also being discussed on #907489 but I think they are separate issues. I have quoted the error message from the log below. https://buildd.debian.org/status/fetch.php?pkg=sambamba=amd64=0.7.1-1=1576381970=0

Bug#948918: libbiod FTBFS on i386

Source: libbiod Version: 0.2.3+git20191120.b8eecef-1 Severity: serious Tags: ftbfs Dear maintainers, libbiod FTBFS on i386. In case the software intentionally doesn't support 32-bit, the old binary package should be removed as it's currently preventing libundead removal. I have quoted the

Processed: Tag ftbfs

Processing commands for cont...@bugs.debian.org: > tag 948917 ftbfs Bug #948917 [src:screengrab] FTBFS: No rule to make target '/usr/lib/x86_64-linux-gnu/libglib-2.0.so' Added tag(s) ftbfs. > thanks Stopping processing here. Please contact me if you need assistance. -- 948917:

Bug#948917: FTBFS: No rule to make target '/usr/lib/x86_64-linux-gnu/libglib-2.0.so'

Source: screengrab Version: 1.101-1 Severity: serious Justification: FTBFS on all archs Hi! During a rebuild your package FTBFS on all affected archs:

Processed (with 6 errors): Two different FTBFS separated

Processing commands for cont...@bugs.debian.org: > clone 907489 -1 Bug #907489 {Done: Matthias Klumpp } [src:sambamba] sambamba FTBFS Bug 907489 cloned as bug 948916 Failed to clone 907489: Not altering archived bugs; see unarchive. > reopen -1 Failed to reopen -1: The 'bug' parameter ("-1") to

Processed: Tagging bugs

Processing commands for cont...@bugs.debian.org: > tag 948911 ftbfs Bug #948911 [src:klog] klog: FTBFS on mipsel: {standard input}:107582: Error: branch out of range Added tag(s) ftbfs. > tag 948912 ftbfs Bug #948912 [src:regina-normal] FTBFS: can not find boost >= 1.55 Added tag(s) ftbfs. > tag

Bug#948914: FTBFS: The qmake executable '/usr/bin/qmake' failed with exit code 1.

Source: qmath3d Version: 0~1.0-2) Severity: serious Justification: FTBFS on all archs Hi Wookey! During a rebuild of your package it FTBFS: The error seems to be: WARNING: Error setting up Qt for

Processed: Tagging FTBFS

Processing commands for cont...@bugs.debian.org: > tag 948783 ftbfs Bug #948783 {Done: Bastian Germann } [src:gambas3] gambas3: FTBFS: error: 'ABSTIMEOID' undeclared (first use in this function) Ignoring request to alter tags of bug #948783 to the same tags previously set > tag 948790 ftbfs Bug

Bug#948913: FTBFS: No rule to make target 'QtWebKit/QWebView', needed by 'ui_report.h'. Stop

Source: sleepyhead Version: 1.0.0-beta-2+dfsg-7 Severity: serious Justification: FTBFS: can not complete target Hi! During a rebuild your package FTBFS: The error seems to be:

Bug#948912: FTBFS: can not find boost >= 1.55

Source: regina-normal Version: 5.1-6 Severity: serious Justification: Fails to build from source: can't find boost During a rebuild your package failed to build form source: CMake outputs the following

Bug#948911: klog: FTBFS on mipsel: {standard input}:107582: Error: branch out of range

Source: klog Version: 0.9.8.1-1.1 Severity: serious Justification: Fails to build from source on mipsel Hi! During a rebuild your package FTBFS: The bug

Bug#948908: plasma-desktop: FTBFS: error: ‘targetDesktop’ was not declared in this scope

Source: plasma-desktop Version: 4:5.14.5.1-4 Severity: serious Tags: ftbfs sid Dear maintainer, During a recent rebuild plasma-desktop failed with the following error: /<>/applets/pager/plugin/pagermodel.cpp: In member function ‘void PagerModel::moveWindow(int, double, double, int, int,

Bug#948907: ktp-call-ui: FTBFS: QDBusArgument: No such file or directory

Source: ktp-call-ui Version: 17.08.3-1 Severity: serious Tags: ftbfs sid Dear maintainer, During a recent rebuild ktp-call-ui failed with the following error: [ 35%] Building CXX object libqtf/CMakeFiles/qtf.dir/qtf_autogen/mocs_compilation.cpp.o [...] In file included from

Bug#938625: marked as done (tap.py: Python2 removal in sid/bullseye)

Your message dated Tue, 14 Jan 2020 17:04:41 + with message-id and subject line Bug#938625: fixed in tap.py 2.6.2-3 has caused the Debian Bug report #938625, regarding tap.py: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has been dealt

Bug#938625: marked as pending in tap.py

Control: tag -1 pending Hello, Bug #938625 in tap.py 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#938625 marked as pending in tap.py

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

Bug#948903: open-infrastructure-system-tools: FTBFS: a2x: error: argument --asciidoc-opts: expected one argument

Source: open-infrastructure-system-tools Version: 20190301-lts1-1 Severity: serious Tags: ftbfs Dear maintainer, your package failed to rebuild in a standard sid chroot. Attached is the full build log, hopefully relevant excerpt follows: debian/rules override_dh_auto_build make[1]: Entering

Bug#948902: open-infrastructure-storage-tools: FTBFS: a2x: error: argument --asciidoc-opts: expected one argument

Source: open-infrastructure-storage-tools Version: 20190301-lts1-1 Severity: serious Tags: ftbfs Dear maintainer, your package failed to rebuild in a standard sid chroot. Attached is the full build log, hopefully relevant excerpt follows: dh_auto_install --

Bug#948901: open-infrastructure-service-tools: FTBFS: a2x: error: argument --asciidoc-opts: expected one argument

Source: open-infrastructure-service-tools Version: 20190301-lts1-1 Severity: serious Tags: ftbfs Dear maintainer, your package failed to rebuild in a standard sid chroot. Attached is the full build log, hopefully relevant excerpt follows: dh_auto_install --

Bug#925629: aghermann: ftbfs with GCC-9

> what is the canonical upstream source for this project? It would be https://gitlab.com/hmmr/aghermann. I'll amend the links on my page shortly. On Tue, 14 Jan 2020 at 17:51, Matthew Fernandez wrote: > > Thanks for being clear, Andrei. And thanks for your work building and > maintaining this

Processed: your mail

Processing commands for cont...@bugs.debian.org: > severity 948867 serious Bug #948867 [gst-plugins-base1.0] The dev shoulds depends on libx11-xcb-dev Severity set to 'serious' from 'normal' > retitle 948867 gst-plugins-base1.0 FTBFS: dpkg-gensymbols: error: some > symbols or patterns

Bug#936488: epylog: Python2 removal in sid/bullseye

On 2020-01-14 10:13, Stuart Prescott wrote: > This package appears to be dead upstream (upstream URL doesn't work and I > can't find it anywhere else). > > With a low popcon (inst: 9), perhaps it's time to remove this package. Indeed. I've asked for removal:

Bug#948897: Subject: openbios: FTBFS: error: taking address of packed member of 'struct ' may result in an unaligned pointer value

Source: openbios Version: 1.1.git20181001-1 Severity: serious Tags: ftbfs Dear maintainer, your package failed to rebuild in a standard sid chroot: powerpc-linux-gnu-gcc $EXTRACFLAGS -m32 -mcpu=604 -msoft-float -fno-builtin-bcopy -fno-builtin-log2 -Os -g

Bug#925629: aghermann: ftbfs with GCC-9

Thanks for being clear, Andrei. And thanks for your work building and maintaining this package. I jumped into this thread knowing nothing about this package but merely recognizing a compiler error. Now that I look up what it does, I don’t have the necessary background to fully understand its

Processed: py2removal bugs severity updates - 2020-01-14 15:36:07.932268+00:00

Processing commands for cont...@bugs.debian.org: > # This is an automated script, part of the effort for the removal of Python 2 > from bullseye > # * https://wiki.debian.org/Python/2Removal > # * http://sandrotosi.me/debian/py2removal/index.html > # See

Bug#948895: neomutt: FTBFS: test failure

Source: neomutt Version: 2019+dfsg.1-1 Severity: serious Tags: ftbfs Dear maintainer, your package failed to rebuild in a standard sid chroot: test/neomutt-test Test test_mutt_addr_cat... [ OK ] Test test_mutt_addr_cmp... [ OK ] Test

Bug#936488: epylog: Python2 removal in sid/bullseye

This package appears to be dead upstream (upstream URL doesn't work and I can't find it anywhere else). With a low popcon (inst: 9), perhaps it's time to remove this package. -- Stuart Prescotthttp://www.nanonanonano.net/ stu...@nanonanonano.net Debian Developer http://www.debian.org/

Processed: limit source to python-pyknon, tagging 938072

Processing commands for cont...@bugs.debian.org: > limit source python-pyknon Limiting to bugs with field 'source' containing at least one of 'python-pyknon' Limit currently set to 'source':'python-pyknon' > tags 938072 + pending Bug #938072 [src:python-pyknon] python-pyknon: Python2 removal in

Bug#948422: marked as done (python-pint ftbfs with Python 3.8)

Your message dated Tue, 14 Jan 2020 14:44:05 + with message-id and subject line Bug#948422: fixed in python-pint 0.10.1-1 has caused the Debian Bug report #948422, regarding python-pint ftbfs with Python 3.8 to be marked as done. This means that you claim that the problem has been dealt

Bug#947573: Nuitka and scons

Hello, Nuitka is very much ported to Python3 for a long time. I have done the changes to the packaging, which remove Python2 dependencies for Bullseye and Sid, but I wanted to keep the packaging working for Wheezy and higher, so this took more time. Nuitka has been not building due to rst2pdf

Bug#945225: cppreference-doc: Fails to build from source: tries to install not generated qch file.

Hi! On 20/01/14 02:03, Michael Crusoe wrote: > On Wed, 27 Nov 2019 16:00:05 +0200 Povilas Kanapickas > wrote: > > On 11/27/19 1:19 PM, Michael Crusoe wrote: > > > Maybe this patch from Ubuntu will help? > > > >

Bug#945225: cppreference-doc: Fails to build from source: tries to install not generated qch file.

On Wed, 27 Nov 2019 16:00:05 +0200 Povilas Kanapickas wrote: > On 11/27/19 1:19 PM, Michael Crusoe wrote: > > Maybe this patch from Ubuntu will help? > > http://patches.ubuntu.com/c/cppreference-doc/cppreference-doc_20170409-1.1ubuntu1.patch > > Hi, > > I will look into this bug ASAP. Couldn't do

  1   2   >