Your message dated Tue, 19 Mar 2019 22:25:24 -0300
with message-id
and subject line Done in 0.8.2-2
has caused the Debian Bug report #924811,
regarding derpconf: FTBFS: build-dependency not installable: python-tox
to be marked as done.
This means that you claim that the problem has been dealt
Control: tag -1 pending
Hello,
Bug #924814 in grub2 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 #924814 [src:grub-efi-amd64-signed] grub-efi-amd64-signed: FTBFS:
build-dependency not installable: grub-efi-amd64-bin (= 2.02+dfsg1-11)
Added tag(s) pending.
--
924814: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924814
Debian Bug
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Control: severity -1 normal
The RC issue was fixed in version 1.3.6+git20160731+dfsg1-2. Let's
keep this bug open for Debian 11. For Buster we can still depend on
the hinted fonts thus there is no risk of breaking anything.
-BEGIN PGP
Processing control commands:
> severity -1 normal
Bug #922947 [retroarch-assets] retroarch-assets: please don’t use hinted Roboto
fonts
Severity set to 'normal' from 'serious'
--
922947: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=922947
Debian Bug Tracking System
Contact
Control: severity -1 normal
Hi Lenz,
failing to backport a package to some ancient release is not release
critical.
Let me see if I managed to understand what you want to achieve:
* your target architecture is i386 (any other achitectures?)
* you want to backport src:libsrtp2 to jessie (and
Processing control commands:
> severity -1 normal
Bug #924941 [src:d-shlibs] d-shlibmove: fails in opensuse build service
Severity set to 'normal' from 'serious'
--
924941: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924941
Debian Bug Tracking System
Contact ow...@bugs.debian.org with
Control: tags -1 confirmed pending
On Fri, 22 Feb 2019 09:18:51 +0100 Andrej Shadura
wrote:
> Package: retroarch-assets
> Severity: normal
>
> Dear Maintainer,
>
> The Roboto upstream no longer provides hinted fonts, so
> fonts-roboto-hinted is now a transitional package providing symlinks to
Processing control commands:
> tags -1 confirmed pending
Bug #922947 [retroarch-assets] retroarch-assets: please don’t use hinted Roboto
fonts
Added tag(s) pending and confirmed.
--
922947: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=922947
Debian Bug Tracking System
Contact
Processing commands for cont...@bugs.debian.org:
> fixed 917738 1.16.3-1
Bug #917738 {Done: tony mancill }
[src:openhft-chronicle-threads] openhft-chronicle-threads: FTBFS: [ERROR]
/<>/src/main/java/net/openhft/chronicle/threads/MonitorEventLoop.java:[123,32]
cannot find symbol
Marked as fixed
* Kurt Roeckx [2019-03-19 22:59]:
> On Tue, Mar 19, 2019 at 10:28:06PM +0100, Holger Weiß wrote:
> > Yes, it's an OpenSSL bug. If TLSv1.3 is used, SSL_get_psk_identity()¹
> > unexpectedly returns NULL. I now avoid the function to work around the
> > issue.
>
> This is documented here:
>
On Tue, Mar 19, 2019 at 10:28:06PM +0100, Holger Weiß wrote:
> Just for the record:
>
> * Sebastian Andrzej Siewior [2018-11-05 00:28]:
> > It is a TLS1.3 issue. If I limit max protocol to TLS1.2 then the
> > testsuite passes.
>
> Yes, it's an OpenSSL bug. If TLSv1.3 is used,
Source: mariadb-10.3
Version: 1:10.3.13-1
Severity: serious
Hi Otto,
please drop the transitional libmariadbclient18 package with the next
upload. I think this will prevent a lot of upgrade problems, because
packages from stretch will not suddenly start to use libmariadb3.
(I just remember the
Just for the record:
* Sebastian Andrzej Siewior [2018-11-05 00:28]:
> It is a TLS1.3 issue. If I limit max protocol to TLS1.2 then the
> testsuite passes.
Yes, it's an OpenSSL bug. If TLSv1.3 is used, SSL_get_psk_identity()¹
unexpectedly returns NULL. I now avoid the function to work around
Hi Santiago,
> The relevant thing, IMO, is that proposed-updates and point
> releases still exist for stretch, so I don't see it overkill
Sure. Can you still loop the SRMs in on this before I backport this
patch and create a stretchpu bug, etc. etc.? Thanks. :)
> I don't see how the release
On Tue, Mar 19, 2019 at 03:29:52PM -0400, Chris Lamb wrote:
> Hi Santiago,
>
> > Ok, but this still should be fixed in stretch, right?
> > (Packages in stretch must build in stretch).
>
> Sure thing, but this would require a stable update which seems a
> little overkill, especially at this point
Hi Santiago,
> Ok, but this still should be fixed in stretch, right?
> (Packages in stretch must build in stretch).
Sure thing, but this would require a stable update which seems a
little overkill, especially at this point in the buster release cycle…?
Fancy pinging the SRMs on this? Not had to
On Tue, Mar 19, 2019 at 03:22:26PM -0400, Chris Lamb wrote:
> I believe this was address on the diffoscope side here:
>
>
> https://salsa.debian.org/reproducible-builds/diffoscope/commit/4a35e55497fac9845ca55be28fbd9e25b4e8576f
>
> ... which was released in diffoscope 112.
Ok, but this
Processing commands for cont...@bugs.debian.org:
> fixed 925051 112
Bug #925051 [src:diffoscope] diffoscope: FTBFS in stretch (failing tests)
Marked as fixed in versions diffoscope/112.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
925051:
fixed 925051 112
thanks
Hi Santiago,
> I tried to build this package in stretch but it failed:
[…]
This is because ghostscript was updated in stretch and it
(unfortunately) now generates different output.
I believe this was address on the diffoscope side here:
* Laurent Bigonville:
> Package: libc6-dev
> Version: 2.28-8
> Severity: serious
>
> Hi,
>
> The crypt.3 manpage, state that _XOPEN_SOURCE should be define for
> crypt() to be available.
>
> But it looks that it's currently the opposite, if _XOPEN_SOURCE is
> defined, the function cannot be
On Sun, Mar 17, 2019 at 07:09:52PM +0100, Bruno Kleinert wrote:
Hi Jonathan,
please find attached a debdiff that updates the path to the manpage.
Thanks for this, I will endeavour to apply and upload Tomorrow (hit a
snag locally, my sbuild environment hath borken)
Your message dated Tue, 19 Mar 2019 17:49:24 +
with message-id
and subject line Bug#900152: fixed in nsca-ng 1.6-1~exp1
has caused the Debian Bug report #900152,
regarding nsca-ng: FTBFS against openssl 1.1.1
to be marked as done.
This means that you claim that the problem has been dealt
Your message dated Tue, 19 Mar 2019 17:49:10 +
with message-id
and subject line Bug#900152: fixed in nsca-ng 1.5-4
has caused the Debian Bug report #900152,
regarding nsca-ng: FTBFS against openssl 1.1.1
to be marked as done.
This means that you claim that the problem has been dealt with.
If
Processing commands for cont...@bugs.debian.org:
> fixed 915723 8u202-b26-1
Bug #915723 [src:openjdk-8] openjdk-8 needs a build dependency preventing build
attempts on zero architectures
Marked as fixed in versions openjdk-8/8u202-b26-1.
> thanks
Stopping processing here.
Please contact me if
Your message dated Tue, 19 Mar 2019 17:34:16 +
with message-id
and subject line Bug#920709: fixed in distcc 3.3.2-8
has caused the Debian Bug report #920709,
regarding distcc: fails to upgrade from 'testing': causes dpkg trigger loop
to be marked as done.
This means that you claim that the
Processing commands for cont...@bugs.debian.org:
> found 920709 3.3.2-6
Bug #920709 [distcc] distcc: fails to upgrade from 'testing': causes dpkg
trigger loop
Marked as found in versions distcc/3.3.2-6.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
920709:
Package: lirc
Version: 0.10.1-5.1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package failed the piuparts
upgrade test because dpkg detected a conffile as being modified and then
prompted the user for an action. As there is
Your message dated Tue, 19 Mar 2019 16:49:11 +
with message-id
and subject line Bug#924805: fixed in python-molotov 1.6-3
has caused the Debian Bug report #924805,
regarding python-molotov: FTBFS: dh_auto_test: pybuild --test --test-pytest -i
python{version} -p 3.7 returned exit code 13
to
Just ping this bug since even if a fix would be uploaded now a fixed
package will not reach testing before the autoremoval would have removed
the package.
Andreas.
--
http://fam-tille.de
Your message dated Tue, 19 Mar 2019 16:04:04 +
with message-id
and subject line Bug#924697: fixed in cider 0.19.0+dfsg-2
has caused the Debian Bug report #924697,
regarding elpa-cider: broken by leiningen 2.9.0
to be marked as done.
This means that you claim that the problem has been dealt
Your message dated Tue, 19 Mar 2019 16:04:12 +
with message-id
and subject line Bug#923012: fixed in squirrel3 3.1-6
has caused the Debian Bug report #923012,
regarding squirrel3: FTBFS (Could not import extension sphinx.ext.pngmath)
to be marked as done.
This means that you claim that the
Package: src:diffoscope
Version: 78
Severity: serious
Tags: ftbfs
Dear maintainer:
I tried to build this package in stretch but it failed:
[...]
debian/rules build-indep
dh build-indep --with python3 --with
Processing commands for cont...@bugs.debian.org:
> tags 924697 + buster
Bug #924697 [elpa-cider] elpa-cider: broken by leiningen 2.9.0
Added tag(s) buster.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
924697:
Processing commands for cont...@bugs.debian.org:
> #this is an important feature not limited to the python bindings
> severity 921599 serious
Bug #921599 [src:mariadb-10.3] python-mysqldb: always connects to localhost
ignoring host entry in option file
Severity set to 'serious' from 'normal'
>
Your message dated Tue, 19 Mar 2019 15:19:26 +
with message-id
and subject line Bug#924495: fixed in shimdandy 1.2.0-3
has caused the Debian Bug report #924495,
regarding shimdandy: FTBFS (Could not resolve dependencies for project
org.projectodd.shimdandy:shimdandy-impl:jar:1.2.0)
to be
Processing commands for cont...@bugs.debian.org:
> tags 919481 - pending
Bug #919481 [src:guile-2.0] guile-2.0 ftbfs on ppc64el
Removed tag(s) pending.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
919481:
Your message dated Tue, 19 Mar 2019 14:39:17 +
with message-id
and subject line Bug#884463: fixed in passenger 5.0.30-1.1
has caused the Debian Bug report #884463,
regarding passenger: CVE-2017-16355: arbitrary file read
to be marked as done.
This means that you claim that the problem has
Package: src:guile-2.0
Version: 2.0.13+1-5
Control: tags -1 patch pending
--
I forgot to mention, the issue now appears because schroots seem to have
all locale created which was not the case before and the tests were
just skipped as UNRESOLVED (see the build log history). Now they run..
and
Processing control commands:
> tags -1 patch pending
Bug #919481 [src:guile-2.0] guile-2.0 ftbfs on ppc64el
Added tag(s) patch and pending.
--
919481: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919481
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
On 2019-03-18 15:29, Thomas Goirand wrote:
> On 3/18/19 12:56 PM, Andreas Beckmann wrote:
>> I'm again investigating openstack-dashboard related upgrade failures.
> Indeed, django-openstack-auth has been removed upstream and included
> directly in django-horizon. I'm not sure what's the best way
Hi,
this bug is actually not ppc64el specific, I could also reproduce it on
barriere.d.o (amd64).
That said, it seems to be an encoding issue.
In i18n tests, some test fail because of strings not being
lexicographically equal, specifically due to the nonbreaking space.
The tests convert values
Package: src:scilab
Version: 6.0.1-7
Severity: serious
Tags: sid buster
scilab terminates immediately when started from the desktop, while starting from
a terminal works.
patch taken from upstream, at
http://launchpadlibrarian.net/415737336/scilab_6.0.1-7build2_6.0.1-7ubuntu1.diff.gz
Control: tag -1 pending
Hello,
Bug #924495 in shimdandy 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 #924495 [src:shimdandy] shimdandy: FTBFS (Could not resolve dependencies
for project org.projectodd.shimdandy:shimdandy-impl:jar:1.2.0)
Added tag(s) pending.
--
924495: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924495
Debian Bug
Processing control commands:
> severity -1 important
Bug #924973 [g3dviewer] g3dviewer: 'debian/rules clean' after build causes
removal of mkinstalldirs
Severity set to 'important' from 'serious'
> block -1 with 670796
Bug #924973 [g3dviewer] g3dviewer: 'debian/rules clean' after build causes
Control: severity -1 important
Control: block -1 with 670796
On 2019-03-19 12:00, Sven Eckelmann wrote:
> Looks like dh-autoreconf (used by debhelper by default) bug #670796. Also
Thanks.
Andreas
On Tuesday, 19 March 2019 11:30:07 CET Andreas Beckmann wrote:
[...]
> g3dviewer/experimental fails to build twice in a row. The first build
> succeeds, but during subsequent debian/rules clean the following files
> disappear:
[...]
> causing the second build to fail:
>
> [...]
> Making install
Package: devscripts
Version: 2.19.3
Severity: grave
Running `dpkg-buildpackage` in a devscripts git checkout does weird
things to $HOME. I don't think it's deleting any files (or else I
would have opened this as critical), but this needs some attention.
The first symptom is that there's
Hi,
On Sun, 27 Jan 2019 15:35:35 + Julian Andres Klode wrote:
> Source: software-properties
> Binary: python3-software-properties software-properties-common
> software-properties-gtk software-properties-kde
> Architecture: source
> Version: 0.96.24.32.7-1
> Distribution: experimental
Do
Your message dated Tue, 19 Mar 2019 11:06:42 +
with message-id
and subject line Bug#924972: fixed in openjdk-11-jre-dcevm 11.0.3+1-1
has caused the Debian Bug report #924972,
regarding openjdk-11-jre-dcevm: Incompatible with openjdk/11.0.3+1-1 (Error
occurred during initialization of VM)
to
Package: python3-celery
Version: 4.2.1-3
Severity: grave
Justification: renders package unusable
Should be fixed in the upstream, but current versions in repository are
incompatible.
https://github.com/celery/celery/issues/5175
-- System Information:
Debian Release: buster/sid
APT prefers
Processing commands for cont...@bugs.debian.org:
> fixed 924839 0.11-3.1
Bug #924839 [src:sphinxcontrib-programoutput] sphinxcontrib-programoutput:
FTBFS: tests failed
Marked as fixed in versions sphinxcontrib-programoutput/0.11-3.1.
>
End of message, stopping processing here.
Please contact me
Package: g3dviewer
Version: 0.2.99.5~svn130-9
Severity: serious
Justification: fails to build from source (but built successfully in the past)
Hi,
g3dviewer/experimental fails to build twice in a row. The first build
succeeds, but during subsequent debian/rules clean the following files
Processing control commands:
> tag -1 pending
Bug #924972 [openjdk-11-jre-dcevm] openjdk-11-jre-dcevm: Incompatible with
openjdk/11.0.3+1-1 (Error occurred during initialization of VM)
Added tag(s) pending.
--
924972: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924972
Debian Bug Tracking
Control: tag -1 pending
Hello,
Bug #924972 in openjdk-11-jre-dcevm 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:
Package: openjdk-11-jre-dcevm
Version: 11.0.1+8-1
Severity: grave
Justification: renders package unusable
Forwarded: https://github.com/HotswapProjects/openjdk-jdk11u-dcevm/issues/2
openjdk-11-jre-dcevm doesn't work with openjdk-11/11.0.3+1-1, any invocation
of 'java -dcevm' returns the following
Processing commands for cont...@bugs.debian.org:
> severity 924374 serious
Bug #924374 [busybox] busybox ip -oneline link show displays nothing
Severity set to 'serious' from 'important'
> # breaks other packages
>
End of message, stopping processing here.
Please contact me if you need
Source: openhft-chronicle-threads
Version: 1.16.3-1
Severity: serious
Justification: fails to build from source
Hi,
openhft-chronicle-threads/experimental recently started to FTBFS:
[...]
[ESC[1;34mINFOESC[m]
-
[ESC[1;33mWARNINGESC[m]
Processing commands for cont...@bugs.debian.org:
> severity 922717 serious
Bug #922717 {Done: Edward Betts } [src:uap-core] uap-core:
CVE-2018-20164
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
922717:
Control: tag -1 moreinfo
Re: Robie Basak 2019-03-18 <20190318165800.gc12...@mal.justgohome.co.uk>
> It is well understood that the OpenSSL license is not "compatible" with
> the GPL (either version 2 or 3); and furthermore, Debian has long taken
> the position that, unless a license exception is
Processing control commands:
> tag -1 moreinfo
Bug #924937 [libpq5] libpq5: OpenSSL license contamination of GPL
reverse-dependencies
Added tag(s) moreinfo.
--
924937: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924937
Debian Bug Tracking System
Contact ow...@bugs.debian.org with
Processing control commands:
> found -1 4.0.3-1+deb9u3
Bug #924966 [src:pdns] pdns: CVE-2019-3871: Insufficient validation in the HTTP
remote backend
Marked as found in versions pdns/4.0.3-1+deb9u3.
> found -1 4.0.3-1
Bug #924966 [src:pdns] pdns: CVE-2019-3871: Insufficient validation in the
Source: pdns
Version: 4.1.6-1
Severity: grave
Tags: security upstream
Forwarded: https://github.com/PowerDNS/pdns/issues/7573
Control: found -1 4.0.3-1+deb9u3
Control: found -1 4.0.3-1
Hi,
The following vulnerability was published for pdns.
CVE-2019-3871[0]:
Insufficient validation in the HTTP
Processing control commands:
> found -1 1.7.0-1
Bug #924965 [src:libssh2] libssh2: CVE-2019-3855 CVE-2019-3856 CVE-2019-3857
CVE-2019-3858 CVE-2019-3859 CVE-2019-3860 CVE-2019-3861 CVE-2019-3862
CVE-2019-3863
Marked as found in versions libssh2/1.7.0-1.
--
924965:
Source: libssh2
Version: 1.8.0-2
Severity: grave
Tags: security upstream
Control: found -1 1.7.0-1
Hi,
The following vulnerabilities were published for libssh2.
CVE-2019-3855[0]:
Possible integer overflow in transport read allows out-of-bounds write
CVE-2019-3856[1]:
|Possible integer overflow
On Fri, Aug 03, 2018 at 02:47:44PM +0200, Thomas Pierson wrote:
> severity 901148 critical
> found 901148 2.14.0-8
> thanks
>
> Hi,
>
> I just spend 1 hour of time debugging my sound playback to finally
> discover it was just the timidity package that get the sound device blocked.
>
Same
67 matches
Mail list logo
