Hi,
> The assaultcube package got updated to version 1.2.0.2.1-1, but the
> matching assaultcube-data package has not been uploaded which makes
> the former to be currently uninstallable in unstable.
I have made some changes to debian/control, please review the package again. If
it continues to
Control: tag -1 pending
Hello,
Bug #935669 in assaultcube-data 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:
Processing control commands:
> tag -1 pending
Bug #935669 [assaultcube-data] assaultcube-data: Outdated version makes
assaultcube uninstallable
Added tag(s) pending.
--
935669: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=935669
Debian Bug Tracking System
Contact ow...@bugs.debian.org
Hi dod,
On Mon, 26 Aug 2019 at 16:45, Dominique Dumont wrote:
>
> On mercredi 21 août 2019 13:08:42 CEST Ivo De Decker wrote:
> > A binnmu of rakudo in unstable fails on amd64:
> >
> > https://buildd.debian.org/status/package.php?p=rakudo
>
> Rakudo fails to build with latest version of libuv1
Your message dated Tue, 27 Aug 2019 03:02:49 +
with message-id
and subject line Bug#875165: fixed in qwt 6.1.4-1.1
has caused the Debian Bug report #875165,
regarding [qwt] Future Qt4 removal from Buster
to be marked as done.
This means that you claim that the problem has been dealt with.
If
Your message dated Tue, 27 Aug 2019 02:37:37 +
with message-id
and subject line Bug#925637: fixed in bcal 2.1+git20190806.6c8d325-1
has caused the Debian Bug report #925637,
regarding bcal: ftbfs with GCC-9
to be marked as done.
This means that you claim that the problem has been dealt with.
Your message dated Tue, 27 Aug 2019 01:02:40 +
with message-id
and subject line Bug#935841: Removed package(s) from unstable
has caused the Debian Bug report #927169,
regarding python-googlecloudapis: unsatisfiable build-dependencies in sid
to be marked as done.
This means that you claim
Your message dated Tue, 27 Aug 2019 01:02:40 +
with message-id
and subject line Bug#935841: Removed package(s) from unstable
has caused the Debian Bug report #838638,
regarding /usr/bin/python3-google-api-tools broken; missing several
dependencies, does not work even after doing so
to be
Your message dated Tue, 27 Aug 2019 01:04:16 +
with message-id
and subject line Bug#935848: Removed package(s) from unstable
has caused the Debian Bug report #875061,
regarding [musique] Future Qt4 removal from Buster
to be marked as done.
This means that you claim that the problem has been
Your message dated Tue, 27 Aug 2019 01:04:39 +
with message-id
and subject line Bug#935850: Removed package(s) from unstable
has caused the Debian Bug report #875178,
regarding [qxmlrpc] Future Qt4 removal from Buster
to be marked as done.
This means that you claim that the problem has been
Your message dated Tue, 27 Aug 2019 01:03:09 +
with message-id
and subject line Bug#935840: Removed package(s) from unstable
has caused the Debian Bug report #904603,
regarding python3-protorpc-standalone: fails to install with Python 3.7
to be marked as done.
This means that you claim that
Your message dated Tue, 27 Aug 2019 01:03:47 +
with message-id
and subject line Bug#935847: Removed package(s) from unstable
has caused the Debian Bug report #874822,
regarding [automoc] Future Qt4 removal from Buster
to be marked as done.
This means that you claim that the problem has been
Your message dated Tue, 27 Aug 2019 00:58:00 +
with message-id
and subject line Bug#935747: Removed package(s) from unstable
has caused the Debian Bug report #842763,
regarding choreonoid FTBFS on armel and armhf: no matching function for call to
'QTransform::map(int, int, double*, double*)'
Your message dated Tue, 27 Aug 2019 00:58:27 +
with message-id
and subject line Bug#935751: Removed package(s) from unstable
has caused the Debian Bug report #875059,
regarding [ntrack] Future Qt4 removal from Buster
to be marked as done.
This means that you claim that the problem has been
Your message dated Tue, 27 Aug 2019 00:58:00 +
with message-id
and subject line Bug#935747: Removed package(s) from unstable
has caused the Debian Bug report #874844,
regarding [choreonoid] Future Qt4 removal from Buster
to be marked as done.
This means that you claim that the problem has
Your message dated Tue, 27 Aug 2019 00:58:00 +
with message-id
and subject line Bug#935747: Removed package(s) from unstable
has caused the Debian Bug report #834718,
regarding choreonoid: maintainer address bounces
to be marked as done.
This means that you claim that the problem has been
Your message dated Tue, 27 Aug 2019 00:59:59 +
with message-id
and subject line Bug#935835: Removed package(s) from unstable
has caused the Debian Bug report #866431,
regarding htmlgen: depends on obsolete python-imaging (replace with python3-pil
or python-pil)
to be marked as done.
This
Your message dated Tue, 27 Aug 2019 00:57:30 +
with message-id
and subject line Bug#935742: Removed package(s) from unstable
has caused the Debian Bug report #874864,
regarding [daemonfs] Future Qt4 removal from Buster
to be marked as done.
This means that you claim that the problem has been
Your message dated Tue, 27 Aug 2019 01:22:43 +0200
with message-id
and subject line Re: Bug#911078: triplea: Fails to start with
NullPointerException
has caused the Debian Bug report #911078,
regarding triplea: Fails to start with NullPointerException
to be marked as done.
This means that you
Hello,
On Wed, 7 Aug 2019 08:36:38 -0700 Dan Van Atta wrote:
> Apologies for the long delay, updates to Debian are a deeper issue than I
> initially realized. TripleA has had a history of maintenance overhead
> problems, seeing the Debian fork has me realize that it is a fork with its
> own
Your message dated Mon, 26 Aug 2019 23:06:57 +
with message-id
and subject line Bug#916182: fixed in dbacl 1.14.1-2
has caused the Debian Bug report #916182,
regarding dbacl FTBFS with glibc 2.28
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is
Your message dated Mon, 26 Aug 2019 22:36:57 +
with message-id
and subject line Bug#934930: fixed in novnc 1:1.0.0-2
has caused the Debian Bug report #934930,
regarding python-novnc: depends on cruft package.
to be marked as done.
This means that you claim that the problem has been dealt
Control: tag -1 pending
Hello,
Bug #934930 in novnc 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:
Processing control commands:
> tag -1 pending
Bug #934930 [python-novnc] python-novnc: depends on cruft package.
Added tag(s) pending.
--
934930: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=934930
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Your message dated Mon, 26 Aug 2019 21:34:23 +
with message-id
and subject line Bug#925645: fixed in blender 2.80+dfsg-3
has caused the Debian Bug report #925645,
regarding blender: ftbfs with GCC-9
to be marked as done.
This means that you claim that the problem has been dealt with.
If this
Your message dated Mon, 26 Aug 2019 20:45:00 +
with message-id
and subject line Bug#933580: fixed in debian-edu-config 2.10.65+deb10u1
has caused the Debian Bug report #933580,
regarding etc/network/if-up.d/hostname causes loss of dynamic v4 IP address
to be marked as done.
This means that
Hi,
> qpxtool seems dead upstream.
Yes, I know.
> Are you planning to port it to Qt5 yourself
Yes.
> or should it be removed from the archive?
I prefer to try port to Qt5 at first. If I will see that it requires too much
time I'll send "rm" request myself.
Best regards,
Boris
On Sat, Sep 09, 2017 at 11:06:28PM +0200, Lisandro Damián Nicanor Pérez Meyer
wrote:
> Source: qpxtool
> Version: 0.7.2-4.1
> Severity: wishlist
> User: debian-qt-...@lists.debian.org
> Usertags: qt4-removal
>
>
> Hi! As you might know we the Qt/KDE team are preparing to remove Qt4
> as
On Sat, Sep 09, 2017 at 11:01:46PM +0200, Lisandro Damián Nicanor Pérez Meyer
wrote:
> Source: qimageblitz
> Version: 1:0.0.6-5
> Severity: wishlist
> User: debian-qt-...@lists.debian.org
> Usertags: qt4-removal
>
>
> Hi! As you might know we the Qt/KDE team are preparing to remove Qt4
> as
Your message dated Mon, 26 Aug 2019 19:56:47 +
with message-id
and subject line Bug#935833: fixed in python-os-testr 1.0.0-6
has caused the Debian Bug report #935833,
regarding python-os-testr: fix autopkgtests for python2 drop
to be marked as done.
This means that you claim that the problem
Processing control commands:
> affects -1 src:node-lodash
Bug #935845 [src:node-globule] node-globule: autopkgtest fails on deprecation
warning with new version of node-lodash
Added indication that 935845 affects src:node-lodash
--
935845:
Source: node-globule
Version: 0.2.0-1
Severity: serious
Tags: sid bullseye
User: debian...@lists.debian.org
Usertags: needs-update
Control: affects -1 src:node-lodash
[X-Debbugs-CC: debian...@lists.debian.org, node-lod...@packages.debian.org]
Dear maintainers,
With a recent upload of
Processing commands for cont...@bugs.debian.org:
> #
> # bts-link upstream status pull for source package irqbalance
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> # https://bts-link-team.pages.debian.net/bts-link/
> #
> user debian-bts-l...@lists.debian.org
Processing control commands:
> affects -1 src:node-lodash
Bug #935843 [src:node-babel-plugin-transform-define]
node-babel-plugin-transform-define: autopkgtest fails on deprecation warning
with new version of node-lodash
Added indication that 935843 affects src:node-lodash
--
935843:
Source: node-babel-plugin-transform-define
Version: 1.3.0-2
Severity: serious
Tags: sid bullseye
User: debian...@lists.debian.org
Usertags: needs-update
Control: affects -1 src:node-lodash
[X-Debbugs-CC: debian...@lists.debian.org, node-lod...@packages.debian.org]
Dear maintainers,
With a
Processing commands for cont...@bugs.debian.org:
> #
> # bts-link upstream status pull for source package clutter-1.0
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> # https://bts-link-team.pages.debian.net/bts-link/
> #
> user debian-bts-l...@lists.debian.org
Processing control commands:
> affects -1 src:node-lodash
Bug #935839 [src:node-applause] node-applause: autopkgtest fails on deprecation
warning with new version of node-lodash
Added indication that 935839 affects src:node-lodash
--
935839:
Source: node-applause
Version: 1.2.2-2
Severity: serious
Tags: sid bullseye
User: debian...@lists.debian.org
Usertags: needs-update
Control: affects -1 src:node-lodash
[X-Debbugs-CC: debian...@lists.debian.org, node-lod...@packages.debian.org]
Dear maintainers,
With a recent upload of
Your message dated Mon, 26 Aug 2019 19:17:28 +
with message-id
and subject line Bug#934957: fixed in cups 2.2.1-8+deb9u4
has caused the Debian Bug report #934957,
regarding cups: multiple security issues (including CVEified CVE-2019-8675 and
CVE-2019-8696)
to be marked as done.
This means
Your message dated Mon, 26 Aug 2019 19:17:08 +
with message-id
and subject line Bug#934957: fixed in cups 2.2.10-6+deb10u1
has caused the Debian Bug report #934957,
regarding cups: multiple security issues (including CVEified CVE-2019-8675 and
CVE-2019-8696)
to be marked as done.
This means
Your message dated Mon, 26 Aug 2019 19:17:09 +
with message-id
and subject line Bug#933742: fixed in slirp4netns 0.2.3-1
has caused the Debian Bug report #933742,
regarding slirp4netns: CVE-2019-14378: heap buffer overflow during packet
reassembly
to be marked as done.
This means that you
Your message dated Mon, 26 Aug 2019 19:17:08 +
with message-id
and subject line Bug#932598: fixed in sendmail 8.15.2-14~deb10u1
has caused the Debian Bug report #932598,
regarding Upgrade to buster fails with start-stop-daemon error
to be marked as done.
This means that you claim that the
Processing control commands:
> block -1 by 935073
Bug #935838 [ftp.debian.org] RM: python-visual -- RoQA; orphaned; RC-buggy;
broken
935838 was not blocked by any bugs.
935838 was not blocking any bugs.
Added blocking bug(s) of 935838: 935073
> block -1 by 911171
Bug #935838 [ftp.debian.org] RM:
Package: python-os-testr
Version: 1.0.0-5
Severity: serious
Tags: patch
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu eoan ubuntu-patch
Dear maintainers,
The python-os-testr autopkgtests now fail because they have not been updated
in the face of the removal of the python2 package.
Your message dated Mon, 26 Aug 2019 18:28:24 +
with message-id
and subject line Bug#935611: fixed in lablgtk3 3.0~beta6-2
has caused the Debian Bug report #935611,
regarding liblablgtk3-ocaml-dev: missing Breaks+Replaces: liblablgtk3-ocaml (<<
3.0~beta6)
to be marked as done.
This means
Your message dated Mon, 26 Aug 2019 17:59:12 +
with message-id
and subject line Bug#875133: fixed in qca2 2.2.1-2
has caused the Debian Bug report #875133,
regarding [qca2] Future Qt4 removal from Buster
to be marked as done.
This means that you claim that the problem has been dealt with.
If
Your message dated Mon, 26 Aug 2019 17:59:42 +
with message-id
and subject line Bug#934340: fixed in zeroinstall-injector 2.14.1-1
has caused the Debian Bug report #934340,
regarding Please remove the dependency on obus and camlp4
to be marked as done.
This means that you claim that the
Control: tag -1 pending
Hello,
Bug #875133 in qca2 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:
Processing control commands:
> tag -1 pending
Bug #875133 [src:qca2] [qca2] Future Qt4 removal from Buster
Added tag(s) pending.
--
875133: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875133
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processing commands for cont...@bugs.debian.org:
> reassign 874843 wnpp
Bug #874843 [src:cdcat] [cdcat] Future Qt4 removal from Buster
Bug reassigned from package 'src:cdcat' to 'wnpp'.
No longer marked as found in versions cdcat/1.8-1.
Ignoring request to alter fixed versions of bug #874843 to
On mercredi 21 août 2019 13:08:42 CEST Ivo De Decker wrote:
> A binnmu of rakudo in unstable fails on amd64:
>
> https://buildd.debian.org/status/package.php?p=rakudo
Rakudo fails to build with latest version of libuv1 but it builds fine with
libuv1 1.24.1-1 (from stable).
I guess that latest
Il giovedì 22 agosto 2019, 19:56:46 CEST, Roger Shimizu
ha scritto:
>
> Since buster is already released, let's let the package migrate to
> testing and upload to backports as before.
On Fri, Aug 23, 2019 at 08:33:09AM +, Gianfranco Costamagna wrote:
> I'm not sure backports team will
Your message dated Mon, 26 Aug 2019 16:19:25 +
with message-id
and subject line Bug#875078: fixed in oxygen 4:5.14.5-2
has caused the Debian Bug report #875078,
regarding [oxygen] Future Qt4 removal from Buster
to be marked as done.
This means that you claim that the problem has been dealt
Your message dated Mon, 26 Aug 2019 16:18:59 +
with message-id
and subject line Bug#931921: fixed in clutter-1.0 1.26.2+dfsg-11
has caused the Debian Bug report #931921,
regarding clutter's autopkgtests hang when ran with a libglib2.0-0 built with
gcc-9
to be marked as done.
This means that
Source: gr-dab
Version: 0.3-4
Severity: serious
Hello, looks like the latest gnuradio uploads broke gr-dab build and testsuite.
Basically the new version broke CMake script, as well as missing libgmp-dev
library, and also the Python2 drop made the python code incompatible with the
latest
Processing control commands:
> severity -1 important
Bug #934673 [libgit2-glib] libgit2-glib ftbfs when chroot has ccache installed
Severity set to 'important' from 'serious'
--
934673: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=934673
Debian Bug Tracking System
Contact
Control: severity -1 important
On Tue, 13 Aug 2019 at 12:07:35 +0100, Simon McVittie wrote:
> On Tue, 13 Aug 2019 at 14:14:01 +0530, Pirate Praveen wrote:
> > Compiler stderr:
> > ccache: error: Failed to create directory
> > /sbuild-nonexistent/.ccache/tmp: Permission denied
>
> If my guess
Processing control commands:
> severity -1 important
Bug #933799 [geary] geary (and other mason based projects) ftbs in clean chroot
with ccache installed
Severity set to 'important' from 'serious'
--
933799: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933799
Debian Bug Tracking System
Processing control commands:
> block 933799 by -1
Bug #933799 [geary] geary (and other mason based projects) ftbs in clean chroot
with ccache installed
933799 was not blocked by any bugs.
933799 was not blocking any bugs.
Added blocking bug(s) of 933799: 935817
> block 934673 by -1
Bug #934673
Processing control commands:
> tag -1 - moreinfo
Bug #935759 [postgresql-9.4] postgresql-9.4: fails to purge: RET=10
postgresql-9.4/postrm_purge_data doesn't exist
Removed tag(s) moreinfo.
--
935759: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=935759
Debian Bug Tracking System
Contact
Control: tag -1 - moreinfo
On 26/08/2019 14.29, Christoph Berg wrote:
> Re: Andreas Beckmann 2019-08-25
> <156677006728.19083.14847313544790792807.report...@zam581.zam.kfa-juelich.de>
>> during a test with piuparts I noticed your package failed to purge.
>> According to policy 7.2 you cannot
Processing control commands:
> reassign -1 python3-googleapi 1.7.11-1
Bug #935562 [goobook] goobook raises exception about google-auth-httplib2
Bug reassigned from package 'goobook' to 'python3-googleapi'.
No longer marked as found in versions goobook/3.3-1.
Ignoring request to alter fixed
Control: reassign -1 python3-googleapi 1.7.11-1
Control: retitle -1 Missing dependency on 'google-auth-httplib2>=0.0.3'
Control: affects -1 goobook
Dear Matthew,
On Fri, Aug 23, 2019 at 06:52PM, Matthew Moore wrote:
> Dear Maintainer,
>
> Running goobook results in a traceback:
>
> Traceback
Package: src:thumbor
Version: 6.7.0-1
Severity: serious
I tried to rebuild the package without the python-celery B-D and got one test
failure:
FAIL: test_can_get_304_with_last_modified
(tests.handlers.test_base_handler.ImageOperationsWithLastModifiedTestCase)
Your message dated Mon, 26 Aug 2019 13:04:23 +
with message-id
and subject line Bug#932506: fixed in elastalert 0.2.1-1
has caused the Debian Bug report #932506,
regarding elastalert: (build-)depends on cruft packages.
to be marked as done.
This means that you claim that the problem has been
Your message dated Mon, 26 Aug 2019 12:49:00 +
with message-id
and subject line Bug#935702: fixed in cryptsetup 2:2.2.0-3
has caused the Debian Bug report #935702,
regarding DM device size ≥2³² 512-bits sectors is truncated on 32-bits platforms
to be marked as done.
This means that you claim
Processing control commands:
> tag -1 moreinfo
Bug #935759 [postgresql-9.4] postgresql-9.4: fails to purge: RET=10
postgresql-9.4/postrm_purge_data doesn't exist
Added tag(s) moreinfo.
--
935759: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=935759
Debian Bug Tracking System
Contact
Control: tag -1 moreinfo
Re: Andreas Beckmann 2019-08-25
<156677006728.19083.14847313544790792807.report...@zam581.zam.kfa-juelich.de>
> during a test with piuparts I noticed your package failed to purge.
> According to policy 7.2 you cannot rely on the depends being available
> during purge,
Your message dated Mon, 26 Aug 2019 12:24:11 +
with message-id
and subject line Bug#792197: fixed in pysdl2 0.9.6+dfsg1-1
has caused the Debian Bug report #792197,
regarding FTBFS: SDLTimerTest.test_SDL_GetTicks fails, others flaky
to be marked as done.
This means that you claim that the
Your message dated Mon, 26 Aug 2019 11:19:07 +
with message-id
and subject line Bug#874840: fixed in breeze 4:5.14.5-2
has caused the Debian Bug report #874840,
regarding [breeze] Future Qt4 removal from Buster
to be marked as done.
This means that you claim that the problem has been dealt
Your message dated Mon, 26 Aug 2019 11:19:46 +
with message-id
and subject line Bug#929334: fixed in libvirt 5.6.0-1
has caused the Debian Bug report #929334,
regarding libvirt: CVE-2019-10132: Insecure permissions for systemd socket for
virtlockd/virtlogd
to be marked as done.
This means
Your message dated Mon, 26 Aug 2019 11:06:50 +
with message-id
and subject line Bug#934802: fixed in ruby-nokogiri 1.10.4+dfsg1-1
has caused the Debian Bug report #934802,
regarding ruby-nokogiri: CVE-2019-5477: command injection vulnerability
to be marked as done.
This means that you claim
Package: rss2email
Version: 1:3.9-4.1
Severity: grave
rss2email no longer works:
$ r2e run
Traceback (most recent call last):
File "/usr/bin/r2e", line 5, in
rss2email.main.run()
File "/usr/lib/python3/dist-packages/rss2email/main.py", line 163, in run
Your message dated Mon, 26 Aug 2019 10:35:01 +
with message-id
and subject line Bug#935788: fixed in vte2.91 0.57.90-2
has caused the Debian Bug report #935788,
regarding vte2.91: dh_missing --fail-missing fails during arch:all build
to be marked as done.
This means that you claim that the
Processing control commands:
> tag -1 fixed-upstream
Bug #935702 [cryptsetup-bin] DM device size ≥2³² 512-bits sectors is truncated
on 32-bits platforms
Added tag(s) fixed-upstream.
--
935702: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=935702
Debian Bug Tracking System
Contact
Control: tag -1 fixed-upstream
On Mon, 26 Aug 2019 at 11:08:35 +0200, Milan Broz wrote:
> Fixed here
> https://gitlab.com/cryptsetup/cryptsetup/commit/8f8f0b3258152a260c6a40be89b485f943f81484
Thanks, Milan!
> I'll do minor release soon, but perhaps it would be better to
> cherrypick the patch
Your message dated Mon, 26 Aug 2019 10:04:45 +
with message-id
and subject line Bug#935783: fixed in bbmap 38.63+dfsg-1
has caused the Debian Bug report #935783,
regarding bbmap: override_dh_installman fails during binary-arch build
to be marked as done.
This means that you claim that the
Control: tag -1 pending
Hello,
Bug #935788 in vte2.91 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:
Processing control commands:
> tag -1 pending
Bug #935788 [src:vte2.91] vte2.91: dh_missing --fail-missing fails during
arch:all build
Added tag(s) pending.
--
935788: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=935788
Debian Bug Tracking System
Contact ow...@bugs.debian.org with
Processing commands for cont...@bugs.debian.org:
> severity 794466 serious
Bug #794466 [src:virtualbox] virtualbox: might not be suitable for stable
releases due to lack of cooperation from upstream on security support for older
releases
Severity set to 'serious' from 'normal'
> thanks
Stopping
Processing commands for cont...@bugs.debian.org:
> tags 875242 + experimental
Bug #875242 {Done: Reiner Herrmann } [src:yabause]
[yabause] Future Qt4 removal from Buster
Added tag(s) experimental.
> tags 784479 - buster buster-ignore
Bug #784479 {Done: Debian FTP Masters }
[src:kde4libs]
Source: xfce4-sntray-plugin
Version: 0.4.11-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
Hi,
xfce4-sntray-plugin doesn't seem to build from source anymore. We
noticed that as part of the xfconf transition (part of the Xfce 4.14
Package: libglx-mesa0
Version: 18.3.6-2
Severity: serious
Justification: Policy 3.5
Dear Maintainer,
the update from Stretch to Buster failed with
Unpacking libglx-mesa0:amd64 (18.3.6-2) ...
dpkg: error processing archive
/var/cache/apt/archives/libglx-mesa0_18.3.6-2_amd64.deb
On 26/08/2019 08:03, Milan Broz wrote:
> No need to report it upstream, I'll fix it. This is really stupid bug, all
> sizes in code
> must be uint_64t. I just wonder why no static analysis screamed here, I run
> it on 32bit...
Fixed here
Hi,
On Sun, 25 Aug 2019, Scott Kitterman wrote:
> If you have lost interest in the package, please let me know so I can ask to
> have it removed.
Don't remove rekall please. There's a new upstream release with Python 3
support. We will get to it eventually.
Cheers,
--
Raphaël Hertzog ◈ Debian
Your message dated Mon, 26 Aug 2019 11:00:32 +0200
with message-id <09a3dbda-4205-dea2-4365-fd2f85383...@debian.org>
and subject line deal.ii: ftbfs with GCC-9
has caused the Debian Bug report #925668,
regarding deal.ii: ftbfs with GCC-9
to be marked as done.
This means that you claim that the
Processing commands for cont...@bugs.debian.org:
> fixed 931948 r-cran-lwgeom/0.1-7-1
Bug #931948 {Done: Andreas Tille } [src:r-cran-lwgeom]
r-cran-lwgeom: FTBFS with PROJ 6
Marked as fixed in versions r-cran-lwgeom/0.1-7-1.
> thanks
Stopping processing here.
Please contact me if you need
Your message dated Mon, 26 Aug 2019 10:49:04 +0200
with message-id <20190826084904.ejolj4yykd2ki...@an3as.eu>
and subject line Re: Bug#931948: r-cran-lwgeom: FTBFS with PROJ 6
has caused the Debian Bug report #931948,
regarding r-cran-lwgeom: FTBFS with PROJ 6
to be marked as done.
This means
Processing commands for cont...@bugs.debian.org:
> limit source lablgtk3
Limiting to bugs with field 'source' containing at least one of 'lablgtk3'
Limit currently set to 'source':'lablgtk3'
> tags 935611 + pending
Bug #935611 [liblablgtk3-ocaml-dev] liblablgtk3-ocaml-dev: missing
Source: vte2.91
Version: 0.57.90-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
Hi,
vte2.91/experimental fails during the arch:all build:
https://buildd.debian.org/status/fetch.php?pkg=vte2.91=all=0.57.90-1=1566403260=0
Processing commands for cont...@bugs.debian.org:
> tags 935782 + pending
Bug #935782 [src:at-spi2-atk] at-spi2-atk: bump B-D: libatk1.0-dev (>=
2.33.3+really2.33.3)
Added tag(s) pending.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
935782:
Source: epiphany-browser
Version: 3.33.91-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
Hi,
epiphany-browser/experimental fails during the arch:all build:
Package: bbmap
Version: 38.43+dfsg-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source
bbmap FTBFS during all binary-arch builds:
https://buildd.debian.org/status/package.php?p=bbmap=experimental
debian/rules override_dh_installman
make[1]: Entering directory '/<>'
Source: at-spi2-atk
Version: 2.33.91-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
libatk1.0-dev 2.33.3+really2.32.0-4 from unstable is insufficient:
meson.build:49:0: ERROR: Invalid version of dependency, need 'atk' ['>=
2.33.3']
Your message dated Mon, 26 Aug 2019 07:49:00 +
with message-id
and subject line Bug#932525: fixed in adns 1.5.0~rc1-1.2
has caused the Debian Bug report #932525,
regarding adns: Uses manual dh sequence operations that are going to be removed
to be marked as done.
This means that you claim
Processing commands for cont...@bugs.debian.org:
> forcemerge 916783 935556
Bug #916783 [command-not-found] command-not-found unable to open database file
Bug #917455 [command-not-found] command-not-found: "local variable 'cnf'
referenced before assignment" shown when entering an unknown command
Package: debhelper
Version: 12.5.3
Severity: serious
Hi,
debhelper 12.5.* breaks the arch:all (only) build of nvidia-cuda-toolkit
(debhelper-compat (= 12)).
The binary-indep now runs the override_dh_makeshlibs (no-op) and
override_dh_shlibdeps (fails) targets, the latter does not expect being
reassign 874843 wnpp
retitle 874843 RFA: cdcat - maintain disk media contents catalog
thanks
Hallo Moritz,
* Moritz Mühlenhoff [Thu, Aug 22 2019, 11:16:12PM]:
> On Sat, Sep 09, 2017 at 09:03:03PM +0200, Lisandro Damián Nicanor Pérez Meyer
> wrote:
> > Source: cdcat
> >
> > Hi! As you might know
On 2019-08-26 09:04, Andreas Tille wrote:
Upstream is aware of the issue, see:
https://github.com/r-spatial/lwgeom/issues/42
I have rebuild r-cran-lwgeom 0.1-7-1 with the recent proj in unstable.
Here is a grep from the build log:
[...]
The package builds fine. Do you agree that I can
Hi,
On Fri, Jul 12, 2019 at 08:55:02PM +0200, Bas Couwenberg wrote:
> Source: r-cran-lwgeom
> Version: 0.1-5+repack-1
> Severity: important
> Tags: upstream
> User: debian-...@lists.debian.org
> Usertags: proj-6
>
> Your package FTBFS with PROJ 6 from experimental.
>
> It fails at configure
1 - 100 of 105 matches
Mail list logo
