Bug#1066554: iec16022: FTBFS: iec16022.c:158:17: error: implicit declaration of function ‘close’; did you mean ‘pclose’? [-Werror=implicit-function-declaration]
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
Bug#1062953: python3-pyocd: Module is unusable (missing runtime dependencies)
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 problem is the usage of an abomination called "libusb_packaging" which needs to be replaced completely. I have a locally patched version that looks good, will try and upload a new version later today. Cheers, sur5r -- ceterum censeo microsoftem esse delendam. pgplgWh6L4M0m.pgp Description: OpenPGP digital signature
Bug#1043131: hcrypto: rename abort to _afscrypto_abort
> 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: ‘struct ctl_table’ has no member named ‘child’ 250 | .child = afs_sysctl_table | ^ /var/lib/dkms/openafs/1.8.10/build/src/libafs/MODLOAD-6.5.0-1-amd64-SP/osi_sysctl.c:250:27: error: positional initialization of field in ‘struct’ declared with ‘designated_init’ attribute [-Werror=designated-init] 250 | .child = afs_sysctl_table | ^~~~ /var/lib/dkms/openafs/1.8.10/build/src/libafs/MODLOAD-6.5.0-1-amd64-SP/osi_sysctl.c:250:27: note: (near initialization for ‘fs_sysctl_table[0]’) /var/lib/dkms/openafs/1.8.10/build/src/libafs/MODLOAD-6.5.0-1-amd64-SP/osi_sysctl.c:250:27: error: incompatible types when initializing type ‘enum ’ using type ‘struct ctl_table *’ /var/lib/dkms/openafs/1.8.10/build/src/libafs/MODLOAD-6.5.0-1-amd64-SP/osi_sysctl.c: In function ‘osi_sysctl_init’: /var/lib/dkms/openafs/1.8.10/build/src/libafs/MODLOAD-6.5.0-1-amd64-SP/osi_sysctl.c:263:18: error: implicit declaration of function ‘register_sysctl_table’; did you mean ‘unregister_sysctl_table’? [-Werror=implicit-function-declaration] 263 | afs_sysctl = register_sysctl_table(fs_sysctl_table, 0); | ^ | unregister_sysctl_table /var/lib/dkms/openafs/1.8.10/build/src/libafs/MODLOAD-6.5.0-1-amd64-SP/osi_sysctl.c:263:16: warning: assignment to ‘struct ctl_table_header *’ from ‘int’ makes pointer from integer without a cast [-Wint-conversion] 263 | afs_sysctl = register_sysctl_table(fs_sysctl_table, 0); |^ cc1: some warnings being treated as errors make[5]: *** [/usr/src/linux-headers-6.5.0-1-common/scripts/Makefile.build:248: /var/lib/dkms/openafs/1.8.10/build/src/libafs/MODLOAD-6.5.0-1-amd64-SP/osi_sysctl.o] Error 1 make[4]: *** [/usr/src/linux-headers-6.5.0-1-common/Makefile:2057: /var/lib/dkms/openafs/1.8.10/build/src/libafs/MODLOAD-6.5.0-1-amd64-SP] Error 2 make[3]: *** [/usr/src/linux-headers-6.5.0-1-common/Makefile:246: __sub-make] Error 2 make[3]: Leaving directory '/usr/src/linux-headers-6.5.0-1-amd64' FAILURE: make exit code 2 make[2]: *** [Makefile.afs:283: openafs.ko] Error 1 make[2]: Leaving directory '/var/lib/dkms/openafs/1.8.10/build/src/libafs/MODLOAD-6.5.0-1-amd64-SP' make[1]: *** [Makefile:188: linux_compdirs] Error 2 make[1]: Leaving directory '/var/lib/dkms/openafs/1.8.10/build/src/libafs' make: *** [Makefile:15: all] Error 2 Upstream commit fb31d299e6caa015f6288ba9186da6277d3d6a8d seems related, will have to test. pgpuvuYjDoEze.pgp Description: OpenPGP digital signature
Bug#1037494: marked as pending in redmine
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: https://salsa.debian.org/ruby-team/redmine/-/commit/db3cc98104c8136b82a093d8178b5101be71e505 Bump nokogiri (Closes: #1037494) (this message was generated automatically) -- Greetings https://bugs.debian.org/1037494
Bug#1037494: marked as pending in redmine
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: https://salsa.debian.org/ruby-team/redmine/-/commit/db3cc98104c8136b82a093d8178b5101be71e505 Bump nokogiri (Closes: #1037494) (this message was generated automatically) -- Greetings https://bugs.debian.org/1037494
Bug#1037494: marked as pending in redmine
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: https://salsa.debian.org/ruby-team/redmine/-/commit/db3cc98104c8136b82a093d8178b5101be71e505 Bump nokogiri (Closes: #1037494) (this message was generated automatically) -- Greetings https://bugs.debian.org/1037494
Bug#1037494: marked as pending in redmine
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: https://salsa.debian.org/ruby-team/redmine/-/commit/6dad08aa478f4f521b0b18ccb0887c99ad72abd5 Bump nokogiri (Closes: #1037494) (this message was generated automatically) -- Greetings https://bugs.debian.org/1037494
Bug#1037494: marked as pending in redmine
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: https://salsa.debian.org/ruby-team/redmine/-/commit/6dad08aa478f4f521b0b18ccb0887c99ad72abd5 Bump nokogiri (Closes: #1037494) (this message was generated automatically) -- Greetings https://bugs.debian.org/1037494
Bug#1037494: marked as pending in redmine
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: https://salsa.debian.org/ruby-team/redmine/-/commit/6dad08aa478f4f521b0b18ccb0887c99ad72abd5 Bump nokogiri (Closes: #1037494) (this message was generated automatically) -- Greetings https://bugs.debian.org/1037494
Bug#1037494: marked as pending in redmine
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: https://salsa.debian.org/ruby-team/redmine/-/commit/6dad08aa478f4f521b0b18ccb0887c99ad72abd5 Bump nokogiri (Closes: #1037494) (this message was generated automatically) -- Greetings https://bugs.debian.org/1037494
Bug#1004729: bind9-dyndb-ldap: fails to load dyndb-ldap backend
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 automatically. Otherwise > bind9-dyndb-ldap will be permanently broken. This is, unfortunately, not as simple as you write there. bind9-dyndb-ldap is not as independent from bind9 upstream as we all would like. To make it compile with bind9 9.18.11, a tiny change is required, see [1]. So even if Debian packaging would do things like "recompile triggers", it wouldn't help here. > Should I open another bug? I don't think it's necessary, but if you want this tracked in the BTS then it needs to be a new one as it's a different issue, even if similar in nature. Cheers, sur5r [1] https://pagure.io/bind-dyndb-ldap/pull-request/218 -- ceterum censeo microsoftem esse delendam. pgpIi6WeHhtLD.pgp Description: OpenPGP digital signature
Bug#1029726: marked as pending in ruby-cfpropertylist
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: https://salsa.debian.org/ruby-team/ruby-cfpropertylist/-/commit/e6615f195927f380c7adcd7c3eed7d15fce09517 Drop 1.8 compatibility (Closes: #1029726) (this message was generated automatically) -- Greetings https://bugs.debian.org/1029726
Bug#1029726: ruby-cfpropertylist: Injects Enumerable::Enumerator into global namespace, breaks unrelated software
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 Enumerable::Enumerator class
into the global namespace, thus breaking unrelated software.
It can be reproduced by:
require 'cfpropertylist'
class FakeParser
include Enumerable
def parse()
Enumerator.new { |x| x << :hi }
end
end
FakeParser.new.parse.to_a
This has been fixed upstream in [1].
I would like to prepare an NMU containing:
- the unreleased changes available on salsa
- cherry-picking the fix from upstream
[1]
https://github.com/ckruse/CFPropertyList/commit/c450984de42ded990a9edd30ce9d7ee0e5e0b103
-- System Information:
Debian Release: bookworm/sid
APT prefers testing-debug
APT policy: (500, 'testing-debug'), (500, 'stable-updates'), (500,
'stable-security'), (500, 'stable-debug'), (500, 'proposed-updates'), (500,
'testing'), (500, 'stable'), (500, 'oldstable'), (400, 'unstable'), (1,
'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 6.0.0-6-amd64 (SMP w/4 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_WARN, TAINT_OOT_MODULE,
TAINT_UNSIGNED_MODULE
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages ruby-cfpropertylist depends on:
ii ruby 1:3.1
ruby-cfpropertylist recommends no packages.
ruby-cfpropertylist suggests no packages.
-- no debconf information
Bug#1015302: Upgrading 14.10.5 to 15.0.4 aborts on db:migrate
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 ++++-+--- 17 | 4 | BackfillNamespaceIdForNamespaceRoute | routes | id | [] 18 | 4 | BackfillIssueSearchData| issues | id | [] 19 | 4 | BackfillMemberNamespaceForGroupMembers | members| id | [] 23 | 4 | BackfillGroupFeatures | namespaces | id | [1] After reading around the docs Patrick linked, I noticed that both Feature.enabled?(:execute_batched_migrations_on_schedule) and Feature.enabled?(:optimize_batched_migrations) returned false. I enabled both features as the docs suggest they should be. After that, I went to /admin/background_migrations and restarted all failed jobs. Shortly after, they finished successfully. I am unsure whether those two features being disabled had anything do to with the issue at all but AIUI it shouldn't hurt to have them enabled. I had a slight hope that this would also resolve #1014904 but it did not. Note: To get gitlab-rails-console to work again, I had to fix /var/lib/gitlab/.gem/bin/rails as that was still pointing to ruby2.5: # gitlab-rails-console /usr/bin/env: ‘ruby2.5’: No such file or directory Cheers, sur5r -- ceterum censeo microsoftem esse delendam. pgpHdYvWeUZxR.pgp Description: OpenPGP digital signature
Bug#1012609: marked as pending in schroot
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: https://salsa.debian.org/debian/schroot/-/commit/f49c88a1bf393ed73f9676cbcd9717415f4575c3 Fix arch-indep build (Closes: #1012609) Locales were not generated in an arch-indep-only build, so install failed. Also, no longer build doxygen docs as they were not installed anyway. (this message was generated automatically) -- Greetings https://bugs.debian.org/1012609
Bug#1012609: marked as pending in schroot
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: https://salsa.debian.org/debian/schroot/-/commit/f49c88a1bf393ed73f9676cbcd9717415f4575c3 Fix arch-indep build (Closes: #1012609) Locales were not generated in an arch-indep-only build, so install failed. Also, no longer build doxygen docs as they were not installed anyway. (this message was generated automatically) -- Greetings https://bugs.debian.org/1012609
Bug#999074: iec16022: missing required debian/rules targets build-arch and/or build-indep
Debdiff attached -- ceterum censeo microsoftem esse delendam. iec16022_0.2.4-1.3.debdiff Description: Binary data pgp1MGui9kV9T.pgp Description: OpenPGP digital signature
Bug#999074: iec16022: missing required debian/rules targets build-arch and/or build-indep
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 glabels. Cheers, sur5r -- ceterum censeo microsoftem esse delendam. pgpRWgJjEQFT3.pgp Description: OpenPGP digital signature
Bug#998108: Rebuild w/ new toolchain
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 microsoftem esse delendam. pgp_NIZBxyXUA.pgp Description: OpenPGP digital signature
Bug#998108: Acknowledgement (firefox freezes shortly after start)
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. Wonderful... I just deleted the LastVersion line from compatibility.ini in my profile and had no problems so far. YMMV. -- ceterum censeo microsoftem esse delendam. pgpl22Us0oRU7.pgp Description: OpenPGP digital signature
Bug#998108: Does not happen on a fresh unstable installation
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 Description: OpenPGP digital signature
Bug#998108: Still present in 94.0-1
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.
Bug#998114: Missing egg info directory prevents asciidoc cli tools from running
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 deleted by d/rules, however, so
the CLI tools are unable to run:
$ asciidoc
Traceback (most recent call last):
File "/usr/bin/asciidoc", line 33, in
sys.exit(load_entry_point('asciidoc==10.0.1', 'console_scripts',
'asciidoc')())
File "/usr/bin/asciidoc", line 22, in importlib_load_entry_point
for entry_point in distribution(dist_name).entry_points
File "/usr/lib/python3.9/importlib/metadata.py", line 524, in distribution
return Distribution.from_name(distribution_name)
File "/usr/lib/python3.9/importlib/metadata.py", line 187, in from_name
raise PackageNotFoundError(name)
importlib.metadata.PackageNotFoundError: asciidoc
I did a local rebuild with the attached patch applied which resulted in
a working asciidoc CLI tool.
Given the package-contains-python-dot-directory lintian tag it results
in, I am unsure if that's the correct fix as I'm no python expert.
--
ceterum censeo microsoftem esse delendam.
diff -Nru asciidoc-10.0.1/debian/rules asciidoc-10.0.1/debian/rules
--- asciidoc-10.0.1/debian/rules 2021-10-29 16:29:00.0 +
+++ asciidoc-10.0.1/debian/rules 2021-10-30 13:00:52.0 +
@@ -11,7 +11,6 @@
mv debian/asciidoc-tests/usr/bin/testasciidoc.py debian/asciidoc-tests/usr/bin/testasciidoc
find debian -type d -name __pycache__ -prune -exec rm -rf {} \;
rm -rf debian/asciidoc-base/usr/lib/python*/dist-packages/asciidoc/resources
- rm -rf debian/asciidoc-base/usr/lib/python*/dist-packages/asciidoc-*.egg-info
rm -rf debian/asciidoc-common/etc/asciidoc/dblatex
rm -rf debian/asciidoc-common/etc/asciidoc/icons
rm -rf debian/asciidoc-common/etc/asciidoc/javascripts
pgphiarRo67Bt.pgp
Description: OpenPGP digital signature
Bug#933749: fail2ban: ever-growing fail2ban sqlite database
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 installed 0.11.1-1 a long time ago and disabled my script. The DB size has been small since then. Cheers, sur5r -- ceterum censeo microsoftem esse delendam. pgpHS26rwOsfc.pgp Description: OpenPGP digital signature
Bug#957349: Should be fixed already
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. -- ceterum censeo microsoftem esse delendam pgpE16tagnEWL.pgp Description: OpenPGP digital signature
Bug#874839: Bareos: Switch to qt5
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 the binary. Starting with
Qt 5.9, however, qmake no longer allows to override the install program
by setting QMAKE_INSTALL_PROGRAM. See [1].
So without any adjustments, the libtool wrapper script ends up being
installed instead of the real binary.
As there does not seem to be a away to integrate libtool and qmake
anymore, I went the plain qmake way.
Note that upstream switched to cmake in 18.2 which already checks for
Qt5, so this patch can be dropped once 18.2 lands in Debian.
[1] https://lists.qt-project.org/pipermail/development/2017-July/030478.html
--
ceterum censeo microsoftem esse delendam
diff --git a/autoconf/configure.in b/autoconf/configure.in
index 28bb3ae51..a291f7f76 100644
--- a/autoconf/configure.in
+++ b/autoconf/configure.in
@@ -402,7 +402,7 @@ AC_ARG_ENABLE(traymonitor,
AC_HELP_STRING([--enable-traymonitor], [enable build of traymonitor @<:@default=no@:>@]),
[
if test x$enableval = xyes; then
- AC_DEFINE(HAVE_TRAYMONITOR, 1, [Define to 1 if tray-monitor Qt4 GUI support should be enabled])
+ AC_DEFINE(HAVE_TRAYMONITOR, 1, [Define to 1 if tray-monitor Qt5 GUI support should be enabled])
support_traymonitor=yes
fi
]
@@ -411,13 +411,13 @@ AC_ARG_ENABLE(traymonitor,
TRAY_MONITOR_DIR=
DEBIAN_CONTROL_TRAYMONITOR=/dev/null
if test x$support_traymonitor = xyes; then
- abc=`$PKGCONFIG --atleast-version=4.6 QtGui`
+ abc=`$PKGCONFIG --atleast-version=5.0 Qt5Gui`
pkg=$?
if test $pkg = 0; then
TRAY_MONITOR_DIR=src/qt-tray-monitor
DEBIAN_CONTROL_TRAYMONITOR=./debian/control.bareos-traymonitor
else
- AC_MSG_ERROR(Unable to find suitable Qt4 installation needed by tray-monitor)
+ AC_MSG_ERROR(Unable to find suitable Qt5 installation needed by tray-monitor)
fi
fi
diff --git a/src/qt-tray-monitor/tray-monitor.pro.in b/src/qt-tray-monitor/tray-monitor.pro.in
index c0351293a..9011bae49 100644
--- a/src/qt-tray-monitor/tray-monitor.pro.in
+++ b/src/qt-tray-monitor/tray-monitor.pro.in
@@ -15,9 +15,12 @@ CONFIG( debug, debug|release ) {
CONFIG += release
}
-QMAKE_LIBDIR += ../lib
+QMAKE_LIBDIR += ../lib/.libs/
QMAKE_CXXFLAGS += @JANSSON_INC@
-LIBS += -lbareoscfg -lbareos
+QMAKE_LFLAGS += '-Wl,-rpath,/usr/lib/bareos'
+LIBS += -lbareoscfg -lbareos -ljansson
+
+QT += widgets
bins.path= /$(DESTDIR)@bindir@
bins.files = bareos-tray-monitor
@@ -43,10 +46,6 @@ TARGET = bareos-tray-monitor
DEPENDPATH += .
INCLUDEPATH += ../include .. .
-LIBTOOL_LINK = @QMAKE_LIBTOOL@ --silent --tag=CXX --mode=link
-LIBTOOL_INSTALL = @QMAKE_LIBTOOL@ --silent --mode=install
-QMAKE_LINK = $${LIBTOOL_LINK} $(CXX)
-QMAKE_INSTALL_PROGRAM = $${LIBTOOL_INSTALL} install -m @SBINPERM@ -p
QMAKE_CLEAN += .libs/* bareos-tray-monitor release/bareos-tray-monitor
RESOURCES= main.qrc
diff --git a/src/qt-tray-monitor/traymenu.cpp b/src/qt-tray-monitor/traymenu.cpp
index 9e2ef06f8..1f840f92b 100644
--- a/src/qt-tray-monitor/traymenu.cpp
+++ b/src/qt-tray-monitor/traymenu.cpp
@@ -47,7 +47,7 @@ void TrayMenu::createAction(QString objName, QString text, QWidget* mainWindow)
const QString& translate = QApplication::translate("TrayMonitor",
text.toUtf8(),
0,
- QApplication::UnicodeUTF8);
+ 0);
QAction *action = new QAction(translate, mainWindow);
pgpHHsaLOi7RY.pgp
Description: OpenPGP digital signature
Bug#933749: Workaround
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 basis to keep the database at a sane size. (It previously grew up to 2.5GB which put some load on the machine...) -- ceterum censeo microsoftem esse delendam. fail2ban-cleanup Description: Binary data pgpsvdniGeYnM.pgp Description: OpenPGP digital signature
Bug#874839: Bug#933019: Adjust for GlusterFS API change
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
Bug#933019: Adjust for GlusterFS API change
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 buster via backports. I could do an NMU as well if you want. Cheers, sur5r [1] https://github.com/bareos/bareos/pull/221/ [2] https://salsa.debian.org/sur5r/bareos/tree/bts933019 -- ceterum censeo microsoftem esse delendam pgpYeKDG3rW6x.pgp Description: OpenPGP digital signature
Bug#939754: gimp: Crashes when I try to open an image or create a new one
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 from sid on an bullseye system did not resolve the segfault issue. This was the first thing i tried. > See also #939768 for more info, which appears to be the same bug. See > especially message #20. #939876 also looks like the same bug. All > three of these bugs should probably be merged. Yes, I tend to agree on that one. But I'll leave that to the GIMP maintainers to decide. -- ceterum censeo microsoftem esse delendam. pgpiXAfTnbUZs.pgp Description: OpenPGP digital signature
Bug#939754: gimp: Crashes when I try to open an image or create a new one
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 0.4.14-1 built fine for me on bullseye/amd64. Debdiff attached. For convenience, binaries bullseye/amd64 can be found at: deb https://debian.sur5r.net/bts939754 bullseye main deb-src https://debian.sur5r.net/bts939754 bullseye main The repository is signed by E3CA1A89941C42E6. (Fingerprint BFD90F4DAAEFA72B67BBAF48E3CA1A89941C42E6) Cheers, sur5r -- ceterum censeo microsoftem esse delendam gimp_939754_fix.debdiff Description: Binary data pgpT4TprlLpsA.pgp Description: OpenPGP digital signature
Bug#925913: uhubctl: autopkgtest always fails
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 changed to contain the full path, passed. diff --git a/debian/tests/run-uhubctl-v b/debian/tests/run-uhubctl-v index ad9ad39..ecefbff 100644 --- a/debian/tests/run-uhubctl-v +++ b/debian/tests/run-uhubctl-v @@ -4,4 +4,4 @@ exec 2>&1 set -e -uhubctl -v +/usr/sbin/uhubctl -v -- ceterum censeo microsoftem esse delendam pgpIClu5hdbm9.pgp Description: OpenPGP digital signature
Bug#916610: Upstream patch, NMU available
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] https://github.com/FreeSpacenav/spacenavd/commit/34ddda1246ad07e8ff2e6606224e710852e3e3d8 [2] https://mentors.debian.net/package/spacenavd -- ceterum censeo microsoftem esse delendam. pgpeLl9tJmNZL.pgp Description: OpenPGP digital signature
Bug#915050: (gitlab) Re: Bug#915050: Keep out of testing
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 dumping 2/3 of an outdated(*) Linux system to /opt. Pirate Praveen is doing an awesome job of packaging this very complex piece of software in a proper way and I at least am very grateful for this. Even if it is only available in unstable, it's a lot better than those blobs provided upstream. Cheers, sur5r (*) - Postgres 9.6 - openSSL 1.0.0 (??!) - Python 3.4 ... the list goes on
Bug#872838:
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: OpenPGP digital signature
Bug#872115: confuse: ABI change without SONAME change breaks other packages
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: https://github.com/martinh/libconfuse/issues/101 Regards, sur5r
Bug#856849: glabels: gdk_pixbuf_from_pixdata() called on:Aborted
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
Bug#854405: reportbug: Should handle missing optional runtime depencies more gracefully
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 as documented. If, however, python3-gi is install, but gir1.2-vte-2.91 is missing, it fails to fall back and emits the reported traceback. It would be nice if reportbug handled this the same way as if python3-gi was missing. Cheers, sur5r
Bug#763769: Thanks
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
Bug#625631: rrdtool update can't work on existing RRD files: This RRD was created on another architecture
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 censeo microsoftem esse delendam. signature.asc Description: PGP signature
Bug#606670: Bug#607525: RM: minitube/1.1-1
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 to be made via backports, rather than volatile. I have no particular preference which route is taken, but thought it was worth spelling out the consequences. I would either like to see a freeze exception for 1.3 or, if that's not possible, a removal of 1.1. Releasing Squeeze with 1.1 makes no sense for me. But it's up to the release team to decide on this. Cheers, sur5r -- ceterum censeo microsoftem esse delendam. signature.asc Description: PGP signature
Bug#606670: [minitube] New upstream release fixes broken API
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 trade-off might be worth it). I think it's unlikely to get a freeze exception this late. If it is in the Squeeze release, remember that it must be supported for at least the next couple of years, maybe three or four depending on Wheezy. Although I've asked about it on IRC anyway*, I think removing this package from Squeeze is the best option and unless I hear otherwise or an exception is granted, I'll suggest this to the release team. I completely agree to removing 1.1-1 from Squeeze and hereby ask for this to be done. If 1.3 get's no freeze exception, I'm fine with that as well. Given youtube's unstable API, I would like minitube to be moved to volatile anyway, if possible. Cheers, sur5r -- ceterum censeo microsoftem esse delendam. signature.asc Description: PGP signature
Bug#590320: Please upload a git 20010-07-25 commit to fix Y0utube interface change
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 a7ce2f4f133804233e7c078fb3ca1bdd4dc23e0f, which fixes this issue. Let's hope i don't have to time-travel 18000 years to the future for this ;) Greetings, Jakob -- ceterum censeo microsoftem esse delendam. signature.asc Description: PGP signature
Bug#555325: Bug located, patch will follow
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. Regards, Jakob -- ceterum censeo microsoftem esse delendam. signature.asc Description: PGP signature
Bug#555325: Bug located, patch will follow
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
Bug#537954: ziptorrent: Needs to depend on libzip = 0.9
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 symbol: zip_set_archive_flag Regards, Jakob -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.30-1-amd64 (SMP w/2 CPU cores) Locale: LANG=C, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages ziptorrent depends on: ii libc6 2.9-12GNU C Library: Shared libraries ii libzip10.8-1 library for reading, creating, ii zlib1g 1:1.2.3.3.dfsg-13 compression library - runtime ziptorrent recommends no packages. ziptorrent suggests no packages. -- no debconf information -- ceterum censeo microsoftem esse delendam. signature.asc Description: PGP signature
