On Mon, May 13, 2019 at 01:02:45AM +0200, Guilhem Moulin
wrote:
> Thanks for your analysis, Steffen. Dropping the Debian-specific patch
> is definitely the way to go for libwww/LWP. However I still believe
> IO::Socket::SSL should provide a way to clear SSL_MODE_AUTO_RETRY in
> order to fix
Processing commands for cont...@bugs.debian.org:
> unarchive 661015
Bug #661015 {Done: Andreas Beckmann } [gnats-user,gnats]
gnats-user: fails to purge if gnats is not purged
Unarchived Bug 661015
> found 661015 4.1.0-0.5
Bug #661015 {Done: Andreas Beckmann } [gnats-user,gnats]
gnats-user:
Hi,
Did you see this bug on the megadown package ?
I saw that your maintainer email (vivia.nikolai...@puri.sm) is not the one you
used when creating bugs before (n.vi...@gmail.com), so I am mailing both just
in case.
On Sat, 20 Apr 2019 09:12:53 +0300 jim_p wrote:
> Package: megadown
>
Hi,
On Wed, 17 Apr 2019 15:27:19 +0300 Joonas Kylmälä wrote:
> Hi,
> > Hilko Bengen:
> > I can get rid of the issues by backporting a number of commits from
> > github.com/nsf/gocode and will submnit an updated package for
> > stretch-proposed-updates.
> > Thanks for investigating.
> > > Are you
Thanks for your analysis, Steffen. Dropping the Debian-specific patch
is definitely the way to go for libwww/LWP. However I still believe
IO::Socket::SSL should provide a way to clear SSL_MODE_AUTO_RETRY in
order to fix applications relying on the former OpenSSL defaults, as
suggested in the
Hi,
Le 12/05/2019 à 22:10, Julien Puydt a écrit :
> Hi,
>
> On 12/05/2019 11:46, Alexis Murzeau wrote:
>
>> I saw that there is a bugfix release 6.0.2 with many fixes [0].
>
> I had started to package 6.0.2 on salsa already in february.
I was wondering, will such bug-fix upstream release be
> Committed to git, tag pending.
Thanks!
Norbert
--
PREINING Norbert http://www.preining.info
Accelia Inc. +JAIST +TeX Live +Debian Developer
GPG: 0x860CDC13 fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13
Processing commands for cont...@bugs.debian.org:
> tags 928805 + pending
Bug #928805 [texlive-lang-czechslovak] texlive-lang-czechslovak: fails to
install: fmtutil failed
Added tag(s) pending.
> stop
Stopping processing here.
Please contact me if you need assistance.
--
928805:
tags 928805 + pending
stop
On 11.05.19 15:55, Andreas Beckmann wrote:
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 severity.
>
Committed to git, tag pending.
H.
--
Your message dated Sun, 12 May 2019 20:48:36 +
with message-id
and subject line Bug#927471: fixed in curl 7.64.0-3
has caused the Debian Bug report #927471,
regarding curl: Regression that fails to exhaust socket data
to be marked as done.
This means that you claim that the problem has been
Hi,
On 12/05/2019 11:46, Alexis Murzeau wrote:
> I saw that there is a bugfix release 6.0.2 with many fixes [0].
I had started to package 6.0.2 on salsa already in february. I removed
the patch about Linenum as that was supposed to have been reworked and
fixed, and it now fails with :
ocamlopt
Control: tags -1 moreinfo
Hello,
I don't know asterisk at all but maybe I can help with triaging this bug.
On Thu, 9 May 2019 12:10:08 -0400 PICCORO McKAY Lenz
wrote:
> Cited from upstream For a native x86_64 build, you need to REMOVE {{-fPIE}}
> from the CFLAGS and {{-fPIE -pie}} from
Processing control commands:
> tags -1 moreinfo
Bug #928717 [src:asterisk] Build link error bundled pjproject : relocation
against symbol cant be used when shared object
Added tag(s) moreinfo.
--
928717: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=928717
Debian Bug Tracking System
Processing control commands:
> tag -1 pending patch fixed-upstream
Bug #928367 [src:papi] libpapi5: SOVERSION is too wide for the runtime check in
PAPI_library_init()
Added tag(s) pending, fixed-upstream, and patch.
--
928367: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=928367
Debian Bug
Control: tag -1 pending patch fixed-upstream
On 2019-05-12 20:15, Andreas Tille wrote:
> in the thread on the upstream mailing list[1] you proposed a patch that
> was confirmed working by upstream. Do you think this patch should be
> submitted to Debian BTS and the bug tagged patch?
It's
On 11.05.19 18:41, Norbert Preining wrote:
Hi Norbert,
> That needs some serious rework ... I tend to depend on texlive-lang-all
> ..
>
Here is the list of not found files and the packages I had to install:
hyph-en-gb texlive-lang-english
hyph-it texlive-lang-italian
hyph-de-1996
Hi Andreas,
in the thread on the upstream mailing list[1] you proposed a patch that
was confirmed working by upstream. Do you think this patch should be
submitted to Debian BTS and the bug tagged patch?
Kind regards
Andreas.
[1]
On Sun, May 12, 2019 at 04:30:01PM +0200, Andreas Beckmann wrote:
> Please do a dummy 2.10-2 upload to fix this ...
I am in fact considering a not-so-dummy upload with minor changes,
because after all this is a package to be copied and pasted, but I'll
have to ask for permission to
On Mon, 06 May 2019 11:48:47 + HIGUCHI Daisuke (VDR dai)
wrote:
> Source: ruby-pygments.rb
> Source-Version: 1.2.0-4
>
> We believe that the bug you reported is fixed in the latest version of
> ruby-pygments.rb, which is due to be installed in the Debian FTP archive.
>
Hi dai,
We will
On Sun, May 12, 2019 at 03:16:10PM +0300, Ilias Tsitsimpis wrote:
> On Mon, Mar 11, 2019 at 12:05PM, Adrian Bunk wrote:
> > On Thu, Jan 31, 2019 at 08:12:17PM +0100, Bernhard Übelacker wrote:
> > > See attached file with several debugging attempts.
> >
> > Looking at the code, the bug seems to be
(note: I'm just someone taking a look to see what is blocking the unicode-data
"transition", i'm not a maintainer of this package or a member of the release
team).
unicode-data 12.0.0 is now in unstable/testing (Buster).
gucharmap FTBFS with this;
It seems upstream have updated gucharmap
Hi!
On Tue, 2019-05-07 at 14:57:53 +0200, Guillem Jover wrote:
> Thanks! I tried yesterday and today to get a deterministic reproducer
> with the version from unstable, but I'm not sure what's the trigger,
> perhaps the torrent peers or the chunk arrival order or something. In
> any case I was
On Sun, May 12, 2019 at 04:30:01PM +0200, Andreas Beckmann wrote:
> Package: hello
> Version: 2.10-1
> Severity: serious
> Tags: sid buster
> User: debian...@lists.debian.org
> Usertags: piuparts
>
> Hi,
>
> during a test with piuparts I noticed your package violates version
> ordering:
>
>
Package: hello
Version: 2.10-1
Severity: serious
Tags: sid buster
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package violates version
ordering:
hello | 2.10-1| stretch | source
hello | 2.10-1| buster
Your message dated Sun, 12 May 2019 13:48:47 +
with message-id
and subject line Bug#928841: fixed in pacemaker 2.0.1-4
has caused the Debian Bug report #928841,
regarding pacemaker-common: fails to upgrade from 'testing': dpkg-statoverride:
error: an override for '/var/lib/pacemaker/pengine'
Processing control commands:
> severity -1 serious
Bug #921694 [src:mdk4] mdk4: FTBFS randomly when built in parallel (undefined
reference to `getFrequencyFromChannel')
Severity set to 'serious' from 'normal'
--
921694: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921694
Debian Bug
On 2019-05-12 04:38, أحمد المحمودي wrote:
> I checked the diff between upstream sources 0.5.0 (the one in testing) &
> 0.6.0, and I don't see any significant difference in Makefiles or docs/
> to cause this. It might something in experimental's toolchain ?
This is probably reproducible in sid
On Mon, Mar 11, 2019 at 12:05PM, Adrian Bunk wrote:
> On Thu, Jan 31, 2019 at 08:12:17PM +0100, Bernhard Übelacker wrote:
> > See attached file with several debugging attempts.
>
> Looking at the code, the bug seems to be in
>
Package: libzorpll-dev
Version: 7.0.1.0~alpha1-1
Severity: serious
Tags: patch
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package fails to upgrade from
'stretch' in some scenarios, and the old version from stretch is kept
installed. This is
Source: cohomcalg
Version: 0.32+ds-1
Severity: serious
Tags: patch ftbfs
Justification: fails to build from source
cohomcalg fails to cross build from source, because it uses the build
architecture linker. One has to pass LD as well.
I also noticed that it fails an arch-only build everywhere,
Control: reassign -1 libwww-perl 6.36-1
Control: retitle -1 libwww-perl: ancient patch causes TLSv1.3 connection
deadlock
Control: tag -1 + patch
On Sun, 12 May 2019 07:31:57 +0200, Steffen Ullrich wrote:
> Actually, the fix is probably even simpler.
>
> The bug does not happen with an
Processing control commands:
> reassign -1 libwww-perl 6.36-1
Bug #914034 [libio-socket-ssl-perl] libio-socket-ssl-perl: TLSv1.3 connection
deadlock
Bug reassigned from package 'libio-socket-ssl-perl' to 'libwww-perl'.
No longer marked as found in versions libio-socket-ssl-perl/2.060-3.
Ignoring
Followup-For: Bug #857653
Control: tag -1 patch
Hi,
this bug was fixed in -4.0 and -5.0, but somehow the corresponding
changes got lost in a merge on the move to -6.0.
So please apply your old patch again ... and merge this into -7, -8, -9.
Andreas
>From
Processing control commands:
> tag -1 patch
Bug #857653 [liblld-6.0] liblld-4.0: missing liblld-4.0.so.1
Added tag(s) patch.
--
857653: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=857653
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Le 08/05/2019 à 00:50, Alexis Murzeau a écrit :
> Where the working log has a java.lang.IllegalStateException
> exception instead. Maybe there is a memory corruption somewhere in
> native code that doesn't always cause a jvm crash.
>
> I fear the crash happen in java code, this stacktrace is not
Your message dated Sun, 12 May 2019 09:49:08 +
with message-id
and subject line Bug#925178: fixed in ruby-globalid 0.4.2+REALLY.0.3.6-1
has caused the Debian Bug report #925178,
regarding ruby-globalid: FTBFS due to failing tests
to be marked as done.
This means that you claim that the
Your message dated Sun, 12 May 2019 07:18:27 +
with message-id
and subject line Bug#928363: fixed in gau2grid 1.3.1-2
has caused the Debian Bug report #928363,
regarding gau2grid: FTBFS if build directory contains "-D"
to be marked as done.
This means that you claim that the problem has been
37 matches
Mail list logo
