Hi!
Michael Stapelberg successfully located the problematic piece of code. For
some reason, the problem is only visible on amd64. On i386, gq behaves just
fine and shows an error message.
The problem is an incorrect reuse of a va_list structure in errorchain.c.
I'm currently preparing a patch.
Please ignore my previous message, it was targeting a different gq bug. But
somehow i fear it might be related.
signature.asc
Description: PGP signature
Package: ziptorrent
Version: 0.9-1
Severity: grave
Justification: renders package unusable
Installing ziptorrent on my Debian/testing system, I end up
with libzip1 from testing, which does not have zip_set_archive_flag.
$ ziptorrent foo.zip
ziptorrent: symbol lookup error: ziptorrent: undefined
tag 590320 pending
thanks
Thanks for your report, Dererk.
I was already aware of the issue but had not yet found time to investigate.
I'm going to package a fixed version later today.
Please, take seriously into account packaging git revision higher than
20010-07-25
Hi,
as Sven Hartge already pointed out, the real fix is
http://oss.oetiker.ch/rrdtool-trac/changeset/2069
But there's already a new upstream version (1.4.4 and 1.4.5), which both
include the fix. Is there a specific reason, why those versions are not yet
packaged?
Cheers,
sur5r
--
ceterum
On Sat, 18 Dec 2010 17:04:05 +
Jonathan Wiltshire j...@debian.org wrote:
I've investigates the new upstream release and the diffstat is large [1].
Upstream 1.3 is not a targetted fix. There are also comments on the
upstream page that suggest other things get broken instead (though the
On Sun, 19 Dec 2010 15:04:13 +
Adam D. Barratt a...@funky-badger.org wrote:
As a side-effect, it will not be possible to include packages which are
not part of the corresponding stable release. If we remove minitube
from Squeeze now, further updates once Squeeze is stable would then need
tag 763769 + pending
I've been pretty busy during the last weeks and the last time I looked
at this bug, the upstream patch didn't exist yet.
I will prepare a 3.2.0 upload including the upstream patch.
--
ceterum censeo microsoftem esse delendam.
signature.asc
Description: PGP signature
reopen 854405
retitle 854405 reportbug: Should handle missing optional runtime depencies more
gracefully
severity 84405 normal
kthxbye
The issue is a little more complex. Reportbug behaves differently
depending on which packages are missing.
If python3-gi is missing, it falls back to text mode
Control: severity -1 normal
Control: tags -1 + unreproducible moreinfo
I can't reproduce this on any of my machines. Could you please describe in
more detail what exactly you did?
Is there any additional output, debug or otherwiese?
pgpL0x_SbfAjk.pgp
Description: OpenPGP digital signature
Package: confuse
Version: 3.2+dfsg-1
Severity: serious
Justification: Policy 8.6.2
Upstream commit 0285479 introduced a new field 'comment' in the middle of
'struct cfg_t' which causes an ABI break.
This broke i3status (Debian #872078).
Upstream bug report:
tags 872838 + fixed-upstream
kthxbye
Just a short note:
This is due to [1]. Fixed upstream in ff88ccb1cd35fa8e8362de4d6f08af678b9966e4.
[1]
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit?id=2a1f062a4acf0be50516ceece92a7182a173d55a
pgpMbni6MqwIk.pgp
Description:
On Fri, 30 Nov 2018 18:01:26 +0200
Jan Groenewald wrote:
> There is https://packages.gitlab.com/gitlab/gitlab-ce
>
> (deb https://packages.gitlab.com/gitlab/gitlab-ce/debian/ stretch main)
Sorry, but no. Just no, no, no and no. Those binary dumps are horrible. They
are essentially just
Control: tags -1 + patch upstream
There's an upstream commit[1] fixing this issue. I've prepared an NMU
and uploaded it to mentors [2].
I would like to try and get it sponsored and uploaded to the DELaYED
queue and ideally get it unblocked for buster.
Cheers,
sur5r
[1]
On Mon, 09 Sep 2019 14:59:02 -0400
Asher Gordon wrote:
> I think that its the GEGL version that fixed it, not the patch. The
> bug appears to be caused because the GIMP was built against GEGL
> 0.4.14 (in sid), but bullseye only has GEGL 0.4.12.
I doubt this is correct. Installing GEGL 0.4.14-1
The crash seems to be caused by gimp_gegl_mask_is_empty() in
app/gegl/gimp-gegl-mask.c
I cherry-picked 986a298a from upstream (which is also contained in
2.10.10+) and rebuilt gimp. This fixes the issue for me. This patch,
however, needs gegl >= 0.4.14 which is stuck in unstable ATM.
gegl
On Wed, 3 Apr 2019 09:40:06 +0800 gustavo panizzo wrote:
> I've just uploaded 2.0.0-4 to experimental
Please note that this still fails on DebCI, presumably because tests
are run as non-root by default, which means /usr/sbin is not in $PATH.
A local test, with debian/tests/run-uhubctl-v
Dear Bareos maintainers,
this FTBFS can be fixed rather easily.
Based on [1] I created [2].
An upcoming 18.2 upstream release will contain a fallback for GlusterFS
5 as well, but I don't see a point in backporting this logic to the
autotools stuff in 17.2 as GlusterFS 6 is available even in
Control: tags + pending
I will prepare an NMU fixing this and #874839 and will upload it to
DELAYED/5.
--
ceterum censeo microsoftem esse delendam
pgpGOmrx2QhE0.pgp
Description: OpenPGP digital signature
Control: tags + patch
Control: tags + pending
This turned out to be a little tricker than expected. While the
tray-monitor code itself only needed a tiny adjustment to compile
against Qt5, getting the actual binary into the package needed more
work.
Upstream is using libtool to link and install
fail2ban up and including to 0.10.4 does not contain code to actually
purge DB entries based on dbpurgeage.
Code for this has been introduced in
681bc2ef07ebdf749ccef624d8d598de42b0c6b6 in branch 0.11 but this has
not seen a release yet.
I am currently running the attached script on a daily
Hi all,
I forgot about this, so a quick followup from my side:
On Wed, 1 Apr 2020 05:29:21 +0200 Salvatore Bonaccorso
wrote:
> Understandable, would not do as as well to install unstable packages
> into production systems. Was just hoping you have a way to
> trigger/reproduce and confirm.
I
On Fri, 17 Apr 2020 17:30:00 +0200 Michael Stapelberg wrote:
> This was fixed upstream with
> https://github.com/i3/i3/commit/f517b5aa57216a6c55fc00053dfaad378d9392fa
Which in turn is part of 4.18. So this should already be fixed. I will
do a rebuild with GCC 10 and update this bug accordingly.
Source: asciidoc
Version: 10.0.1-1
Severity: grave
Justification: Causes builds of packages using asciidoc to build documentation
to fail
Tags: patch
X-Debbugs-Cc: su...@debian.org
/usr/bin/asciidoc and /usr/bin/a2x rely on python distribution info to
locate the entry point. These files are
Package: firefox
Version: 94.0-1
Followup-For: Bug #998108
X-Debbugs-Cc: su...@debian.org
I just tried 94.0-1 and it froze a couple of seconds after entering a
BBB session.
Package: firefox
Version: 94.0-1
Followup-For: Bug #998108
I just did a fresh unstable installation and I can not reproduce the
bug there.
So some difference in dependencies between bookworm and sid might be
causing this.
Any idea how to systematically find this?
pgpZDaeY0EbLa.pgp
On Wed, 03 Nov 2021 18:44:12 +0100
Christoph Anton Mitterer wrote:
> Oh and as a warning for everyone who wants to try out.
>
> Stupid *zilla seems to no prevent downgrade of the profiles... so once
> upgraded you cannot downgrade without throwing away your old profile
> with all data in it.
On Mon, 8 Nov 2021 10:25:24 +0100
Matthias Urlichs wrote:
> Looks like the problem is a toolchain matter and requires a rebuild with
> Rust 1.56.
>
> https://bugzilla.opensuse.org/show_bug.cgi?id=1192067
According to the build log, 94.0-1 has been built with 1.56.
--
ceterum censeo
I just had a look at this and so far it looks easy to convert to dh.
I intend to prepare an NMU for this. Debdiff will follow.
Jan: Is that ok with you? Also: Would you be interested in a
co-maintainer for iec16022?
I am sort of scratching my own itch here as iec16022 is a reverse
dependency of
Debdiff attached
--
ceterum censeo microsoftem esse delendam.
iec16022_0.2.4-1.3.debdiff
Description: Binary data
pgp1MGui9kV9T.pgp
Description: OpenPGP digital signature
> https://git.openafs.org/?p=openafs.git;a=commit;h=c4c1689
That by itself is not enough it seems:
CC [M]
/var/lib/dkms/openafs/1.8.10/build/src/libafs/MODLOAD-6.5.0-1-amd64-SP/osi_sysctl.o
/var/lib/dkms/openafs/1.8.10/build/src/libafs/MODLOAD-6.5.0-1-amd64-SP/osi_sysctl.c:250:10:
error:
Control: tag -1 pending
Hello,
Bug #1012609 in schroot 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:
Control: tag -1 pending
Hello,
Bug #1012609 in schroot 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:
I have not upgraded to 15.0.4 yet but found the following jobs being
in failed state on my instance:
id | status | job_class_name | table_name |
column_name | job_arguments
++++-+---
Package: ruby-cfpropertylist
Version: 2.2.8-1.1
Severity: serious
Tags: patch upstream
Justification: Breaks unrelated software
While the infamous "Showing diffs returns 500" problem on Debian
packaged gitlab, it was noticed that the current version of
ruby-cfpropertylist in Debian injects an
Control: tag -1 pending
Hello,
Bug #1029726 in ruby-cfpropertylist 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:
On Wed, 1 Feb 2023 21:10:57 +0100
Matej Zagiba wrote:
> I believe real problem lies in package management procedures - there
> should be trigger to recompile and repackage (and retest)
> bind9-dyndb-ldap after each version change and/or repackage of
> bind9-libs. This action should be done
Control: tag -1 pending
Hello,
Bug #1037494 in redmine 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:
Control: tag -1 pending
Hello,
Bug #1037494 in redmine 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:
Control: tag -1 pending
Hello,
Bug #1037494 in redmine 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:
Control: tag -1 pending
Hello,
Bug #1037494 in redmine 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:
Control: tag -1 pending
Hello,
Bug #1037494 in redmine 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:
Control: tag -1 pending
Hello,
Bug #1037494 in redmine 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:
Control: tag -1 pending
Hello,
Bug #1037494 in redmine 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:
Hi,
thanks for the report.
I also noticed this while working on the adoption of the package.
This particular problem can be worked around easily, but it's unfortunately
not the only one.
My current plan is to disable jlink support as a first step as it needs
non-free components.
The other
Control: fixed -1 0.2.5
This has been fixed upstream by [1]. I'm working on updating iec16022 to 0.3.1.
[1]
https://github.com/rdoeffinger/iec16022/commit/bcd23c55d7176fdea9d40e68b93100567903ce14
pgpYAUOZIOflm.pgp
Description: OpenPGP digital signature
46 matches
Mail list logo
