Actually, the fix is probably even simpler.
The bug does not happen with an original libwww. It only happens with an LWP
which contains Debian patches. Specifically the patch
drop-non-blocking-socket.patch causes the problem since it keeps the socket
blocking while the original libwww explicitly
Package: pacemaker-common
Version: 2.0.1-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.
>From the attached log (scroll
Your message dated Sun, 12 May 2019 03:33:29 +
with message-id
and subject line Bug#924397: fixed in corekeeper 1.7
has caused the Debian Bug report #924397,
regarding corekeeper: insecure use of world-writable /var/crash
to be marked as done.
This means that you claim that the problem has be
On Sat, May 11, 2019 at 08:56:42PM +0200, Andreas Beckmann wrote:
> raqm/experimental fails to build twice in a row. The first build
> succeeds, but the subsequent clean deletes
> docs/html/* which is not regenerated during the
> second build, fausing this to fail with:
---end quoted text---
I che
On Sat, 11 May 2019 21:56:01 +0200, Steffen Ullrich wrote:
> I think the issue is a bit different than what was analyzed so far.
[…]
Thank you for this detailed analysis!
> The following small patch for LWP::protocol::http seems to fix the
> problem for me:
>
> --- /usr/share/perl5/LWP/Protoco
On Sat, 11 May 2019, Hilmar Preuße wrote:
> Is even in unstable a rather huge package. Do you known, why Karl made
> this step?
Not Karl, Petr Olsak, the author of cstex.
> I personally tend to test, which langs are really needed, although I
> have only little hope, that it is significantly small
On 11.05.19 18:41, Norbert Preining wrote:
> On Sat, 11 May 2019, Hilmar Preuße wrote:
Hi,
>> ! I can't find file `hyph-en-gb'.
>
> indeed, cstex switched to load *loads* of patterns in 3/2019. What a
> pain. See
> http://git.texlive.info/texlive/commit/?id=e6ecf62a1727571cc47129fa4b4e198eadbe2e
Processing commands for cont...@bugs.debian.org:
> user debian...@lists.debian.org
Setting user to debian...@lists.debian.org (was a...@debian.org).
> affects 904297 + dms
Bug #904297 [dms-core] dms-core: fails to install: calls /etc/init.d/procps
incorrectly
Added indication that 904297 affects
I think the issue is a bit different than what was analyzed so far.
As far as I can see it has nothing to do with SSL_MODE_AUTO_RETRY but
instead is caused by expectations on the behavior of select which are wrong
with TLS 1.3.
I've added some more debugging to IO::Socket::SSL and what I saw was:
Source: raqm
Version: 0.6.0-2
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
Hi,
raqm/experimental fails to build twice in a row. The first build
succeeds, but the subsequent clean deletes
docs/html/* which is not regenerated during th
Processing commands for cont...@bugs.debian.org:
> found 924168 9.4.18-1
Bug #924168 [jetty9] jetty9: broken symlink:
/usr/share/jetty9/lib/apache-jsp/jdt-core.jar -> ../../../java/ecj.jar
Marked as found in versions jetty9/9.4.18-1.
> unarchive 905415
Bug #905415 {Done: Jérémy Lal } [libnode-dev
Umpf,...
On Sat, 11 May 2019, Hilmar Preuße wrote:
> ! I can't find file `hyph-en-gb'.
indeed, cstex switched to load *loads* of patterns in 3/2019. What a
pain. See
http://git.texlive.info/texlive/commit/?id=e6ecf62a1727571cc47129fa4b4e198eadbe2ed3
That needs some serious rework ... I tend to d
Hi,
it seems as though geany-plugin-webhelper was removed from buster/sid.
Looking at the changelog, there's the following entry:
geany-plugins (1.32+dfsg-3) unstable; urgency=medium
* [67b34ed] Disable webkit-using plugins: markdown, webhelper
webkitgtk-3.0 is not to be used as it is depr
Your message dated Sat, 11 May 2019 15:34:29 +
with message-id
and subject line Bug#927943: fixed in libxmlada 18-4
has caused the Debian Bug report #927943,
regarding libxmlada: FTBFS with unicode-data >= 12.0.0
to be marked as done.
This means that you claim that the problem has been dealt
On 11.05.19 15:55, Andreas Beckmann wrote:
> during a test with piuparts I noticed your package failed to install. As
> per definition of the release team this makes the package too buggy for
> a release, thus the severity.
>
Error message from fmtutil:
(/usr/share/texlive/texmf-dist/tex/csplain
Package: texlive-lang-czechslovak
Version: 2019.20190508-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package failed to install. As
per definition of the release team this makes the package too buggy for
a release, thus the
Your message dated Sat, 11 May 2019 13:48:58 +
with message-id
and subject line Bug#926857: fixed in mesa 18.3.6-2
has caused the Debian Bug report #926857,
regarding mesa-vdpau-drivers: broken symlink:
/usr/lib/x86_64-linux-gnu/vdpau/libvdpau_gallium.so -> libvdpau_gallium.so.1.0.0
to be mar
Your message dated Sat, 11 May 2019 13:03:28 +
with message-id
and subject line Bug#928304: fixed in groonga 9.0.0-1+deb10u1
has caused the Debian Bug report #928304,
regarding groonga-httpd: Privilege escalation due to insecure use of logrotate
(CVE-2019-11675)
to be marked as done.
This me
Hi,
On Mon, 29 Apr 2019 21:42:09 +0200 Paul Gevers wrote:
> As it turned out that the failure was *not* only a failure in the
> autopkgtest, but also in the build, we need a fix for buster. The above
> changes don't qualify, can you please revert the changes and upload the
> old version (version
Thanks for upping the limit in libdebian-installer :)
But doesn't it require a rebuild for cdebootstrap-static to pick up this
change? If so, could you do or request it?
TIA,
Diederik
signature.asc
Description: This is a digitally signed message part.
Source: congress
Version: 9.0.0+dfsg1-2
Severity: serious
Tags: ftbfs
Justification: fails to build from source
Hi,
congress/experimental fails to build twice in a row:
Traceback (most recent call last):
File
"/build/congress-9.0.0+dfsg1/congress/tests/api/test_datasource_model.py", line
45,
Hi Jonathan,
besides the excellent summary from Simon, I can mainly provide some
personal feedback. Every now and then, I try the GNOME/Wayland session,
but so far I've always switched back to GNOME/Xorg.
My biggest gripe is
https://bugzilla.gnome.org/show_bug.cgi?id=745032
I.e. mouse animation un
Your message dated Sat, 11 May 2019 11:07:02 +0200
with message-id <20190511090702.gd28...@argenau.bebt.de>
and subject line Re: Bug#737921: reassign 737921 to src:gnutls28, found 737921
in 2.12.20-8+deb7u2, reassign 782630 to src:gnutls28 ...
has caused the Debian Bug report #737921,
regarding [T
Your message dated Sat, 11 May 2019 11:07:02 +0200
with message-id <20190511090702.gd28...@argenau.bebt.de>
and subject line Re: Bug#737921: reassign 737921 to src:gnutls28, found 737921
in 2.12.20-8+deb7u2, reassign 782630 to src:gnutls28 ...
has caused the Debian Bug report #737921,
regarding gn
On 2019-05-11 Andreas Beckmann wrote:
[gnutls26 vs gnutls28]
> PS: do you plan the rename the source package post-buster to remove the
> version confusion?
Hello,
No, I do not plan on renaming the source-package unless I am forced to
do that. The downsides are too big (loss of history for tracker
Processing commands for cont...@bugs.debian.org:
> # Lets assign these back, and close them in a separate message
> # 2nd try.
> reassign 737921 libgnutls26
Bug #737921 [src:gnutls26] [TLS1.2] gnutls only likes SHA1 and SHA256
certificates
Bug #740160 [src:gnutls26] gnutls unusable with cacert SH
Processing commands for cont...@bugs.debian.org:
> # Lets assign these back, and close them in a separate message
> reassign 737921 src:gnutls26
Bug #737921 [src:gnutls28] [TLS1.2] gnutls only likes SHA1 and SHA256
certificates
Bug #740160 [src:gnutls28] gnutls unusable with cacert SHA2-512 sigs
On 2019-05-11 10:22, Andreas Metzler wrote:
> Hello,
> Are you sure about that? Version 2.12.23-10 was shipped in src:gnutls26
> and the issue is fixed in GnuTLS version 3 (i.e. gnutls28).
So obviously you can close that bug with an appropriate version :-)
Therefore I reassigned the three remainin
Hi Helmut,
Am 08.05.19 um 19:23 schrieb Helmut Grohne:
Thank you for the detailed analysis. The actual failure we see here is
secondary. It tries to log an error and fails. Changing the
LOG_DESTINATION fixes the secondary error. The primary cause seems to
live in JShrink though and I guess that
On 2019-05-10 Andreas Beckmann wrote:
> reassign 737921 src:gnutls28 2.12.23-10
> found 737921 2.12.20-8+deb7u2
> reassign 782630 src:gnutls28 2.12.20-8+deb7u2
> reassign 810814 src:gnutls28 2.12.20-8+deb7u5
> thanks
Hello,
Are you sure about that? Version 2.12.23-10 was shipped in src:gnutls26
a
30 matches
Mail list logo
