Bug#1068376: RFP: python-chainstream -- a subclass of io.RawIOBase, to chain I/O streams together into a single stream
Package: wnpp Severity: wishlist X-Debbugs-Cc: team+pyt...@tracker.debian.org * Package name: python-chainstream Version : 1.0.1 Upstream Contact: Reuben Thomas * URL : https://github.com/rrthomas/chainstream * License : CC-BY-SA-4.0 Programming Lang: Python Description : a subclass of io.RawIOBase, to chain I/O streams together into a single stream Chainstream provides the class ChainStream, a subclass of io.RawIOBase, to chain I/O streams together into a single stream. See below for example usage, and the module help for more information. I would be happy if someone could package this, I also could be a sponsor. I require it for newer versions of my rpl package.
Bug#1043106: needrestart: Do not restart run services (started via systemd-run)
tag -1 - patch thanks Am 06.08.2023 um 09:41 schrieb Volker Klasen: Package: needrestart Version: 3.6-5 Severity: normal Tags: patch Dear Maintainer, I am using a service created via systemd-run to run unattended-upgrade. Today, needrestart restarted this service as some libraries have been updated, which resulted in two runs, one failed and another one. I suspect that commands started/run via systemd-run will most likely be oneshot commands, which shouldn't be restarted. Therefore, I added run services to override_rc and would like to see this in the default configuration for needrestart. I attached a patch which will do this. Hello, I dont think this would be a good idea. Also if it is a oneshot service you may want to know if it is maybe vulnerable. -- /* Mit freundlichem Gruß / With kind regards, Patrick Matthäi GNU/Linux Debian Developer Blog: https://www.linux-dev.org/ E-Mail: pmatth...@debian.org patr...@linux-dev.org */
Bug#1059859: glusterfs: Update gluster.bash source location in glusterfs-cli.install
Hey Am 09.01.2024 um 16:53 schrieb Lena Voytek: Hi Patrick, Thanks for the reply. I looked into it again and realized this bug only shows up if the bash-completion package is installed beforehand. If so, then due to upstream commit 064328f7dd307916 the install directory changes to /usr/share/bash-completion/completions. This actually causes an issue in Ubuntu, but it looks like Debian's build system handles it correctly as is. Sorry for the invalid issue! Hm good point, thanks for testing. I think in this case it would be "build" safer also in not clean environments to b-d on bash-completion and let glusterfs then use the correct path. I will test it in the next days if it builds clean in both ways On Tue, Jan 9, 2024 at 2:49 AM Patrick Matthäi wrote: Hi Lena, Am 02.01.2024 um 15:29 schrieb Lena Voytek: Source: glusterfs Version: 11.1-3 Followup-For: Bug #1059859 X-Debbugs-Cc:l...@voytek.dev Here is the patch Thanks for your patch, but building it on sid gives me this error: find debian/tmp/usr/lib -type f -name \*.la -delete dh_install Failed to copy '/usr/share/bash-completion/completions/gluster.bash': No such file or directory at /usr/share/dh-exec/dh-exec-install-rename line 70, <> line 2. dh_install: error: debian/glusterfs-cli.install (executable config) returned exit code 127 make[1]: *** [debian/rules:34: override_dh_install] Error 127 make[1]: Leaving directory '/build/glusterfs-11.1' make: *** [debian/rules:20: binary] Error 2
Bug#1059859: glusterfs: Update gluster.bash source location in glusterfs-cli.install
Hi Lena, Am 02.01.2024 um 15:29 schrieb Lena Voytek: Source: glusterfs Version: 11.1-3 Followup-For: Bug #1059859 X-Debbugs-Cc:l...@voytek.dev Here is the patch Thanks for your patch, but building it on sid gives me this error: find debian/tmp/usr/lib -type f -name \*.la -delete dh_install Failed to copy '/usr/share/bash-completion/completions/gluster.bash': No such file or directory at /usr/share/dh-exec/dh-exec-install-rename line 70, <> line 2. dh_install: error: debian/glusterfs-cli.install (executable config) returned exit code 127 make[1]: *** [debian/rules:34: override_dh_install] Error 127 make[1]: Leaving directory '/build/glusterfs-11.1' make: *** [debian/rules:20: binary] Error 2
Bug#1059980: xine-ui: Please move from liblircclient-dev to liblirc-dev
Hey, upload planned for this week Am 08.01.2024 um 12:56 schrieb Gianfranco Costamagna: Hello, On Thu, 4 Jan 2024 11:28:11 +0100 Gianfranco Costamagna wrote: Source: xine-ui Version: 0.99.14-1 Tags: patch Hello, as you might know, lirc renamed it's library from liblircclient-dev into liblirc-dev (there were multiple split libraries that have been unified into one single library). To finish this transition we would like to remove the liblircclient-dev provided now since 2019 from the main liblirc-dev binary. In order to achieve this we found a total of 8 packages still using the old one, so I'm asking you to update it and let us drop that old cruft from src:lirc. sed s/liblircclient-dev/liblirc-dev/g -i debian/control Note, since this is a no-op change, and a trivial one, I might also NMU/Team upload if I find your package to be one of the last blockers. At the end, after only 4 days, this one looks the last blocker :) G.
Bug#1001132: kdenlive: Unable to Start with Use GPU processing (Movit libary) enabled
Hello @JB
Am 13.12.2023 um 01:57 schrieb Bob Wong:
kf.kio.core: Malformed JSON protocol file for protocol: "trash" , number
of the ExtraNames fields should match the number of ExtraTypes fields
kf.kio.core: Malformed JSON protocol file for protocol: "trash" , number
of the ExtraNames fields should match the number of ExtraTypes fields
[New Thread 0x7fff3fcf16c0 (LWP 6090)]
=== /// CANNOT ACCESS SPEECH DICTIONARIES FOLDER
[New Thread 0x7fff3dfff6c0 (LWP 6091)]
[New Thread 0x7fff2ebff6c0 (LWP 6092)]
QQmlEngine::setContextForObject(): Object already has a QQmlContext
[New Thread 0x7fff2ddfe6c0 (LWP 6093)]
[New Thread 0x7fff2d5fd6c0 (LWP 6094)]
Hspell: can't open /usr/share/hspell/hebrew.wgz.sizes.
kf.sonnet.clients.hspell: HSpellDict::HSpellDict: Init failed
QQmlEngine::setContextForObject(): Object already has a QQmlContext
[New Thread 0x7fff1ff366c0 (LWP 6095)]
[New Thread 0x7fff1f7356c0 (LWP 6096)]
QQmlEngine::setContextForObject(): Object already has a QQmlContext
QQmlEngine::setContextForObject(): Object already has a QQmlContext
[New Thread 0x7fff1cfff6c0 (LWP 6097)]
[New Thread 0x7fff0ebff6c0 (LWP 6098)]
[New Thread 0x7fff0e3fe6c0 (LWP 6099)]
[New Thread 0x7fff0dbfd6c0 (LWP 6100)]
[New Thread 0x7fff0d3fc6c0 (LWP 6101)]
[New Thread 0x7fff0cbfb6c0 (LWP 6102)]
[New Thread 0x7ffef7fff6c0 (LWP 6103)]
[New Thread 0x7ffef77fe6c0 (LWP 6104)]
[New Thread 0x7ffef6ffd6c0 (LWP 6105)]
[New Thread 0x7ffef67fc6c0 (LWP 6106)]
[New Thread 0x7ffef5ffb6c0 (LWP 6107)]
[New Thread 0x7ffef57fa6c0 (LWP 6108)]
[New Thread 0x7ffef4ff96c0 (LWP 6109)]
[New Thread 0x7ffed7fff6c0 (LWP 6110)]
[New Thread 0x7ffed77fe6c0 (LWP 6111)]
[New Thread 0x7ffed6ffd6c0 (LWP 6112)]
[New Thread 0x7ffed67fc6c0 (LWP 6113)]
[New Thread 0x7ffed5ffb6c0 (LWP 6114)]
[New Thread 0x7ffed57fa6c0 (LWP 6115)]
[New Thread 0x7ffed4ff96c0 (LWP 6116)]
[New Thread 0x7ffeb7fff6c0 (LWP 6117)]
[New Thread 0x7ffeb77fe6c0 (LWP 6118)]
[New Thread 0x7ffeb6ffd6c0 (LWP 6119)]
[New Thread 0x7ffeb67fc6c0 (LWP 6120)]
[New Thread 0x7ffeb5ffb6c0 (LWP 6121)]
[New Thread 0x7ffeb57fa6c0 (LWP 6122)]
[New Thread 0x7ffeb4ff96c0 (LWP 6123)]
[New Thread 0x7ffe97fff6c0 (LWP 6124)]
[New Thread 0x7ffe977fe6c0 (LWP 6125)]
[New Thread 0x7ffe96ffd6c0 (LWP 6126)]
[New Thread 0x7ffe967fc6c0 (LWP 6127)]
[New Thread 0x7ffe95ffb6c0 (LWP 6128)]
[New Thread 0x7ffe957fa6c0 (LWP 6129)]
[New Thread 0x7ffe94ff96c0 (LWP 6130)]
[New Thread 0x7ffe77fff6c0 (LWP 6131)]
[New Thread 0x7ffe777fe6c0 (LWP 6132)]
[New Thread 0x7ffe76ffd6c0 (LWP 6133)]
[New Thread 0x7ffe767fc6c0 (LWP 6134)]
[New Thread 0x7ffe75ffb6c0 (LWP 6135)]
[New Thread 0x7ffe757fa6c0 (LWP 6136)]
[New Thread 0x7ffe74ff96c0 (LWP 6137)]
NOT FOUND DOCUMENT GUIDES !!!
!
[New Thread 0x7ffe57fff6c0 (LWP 6138)]
QQmlEngine::setContextForObject(): Object already has a QQmlContext
qrc:/qml/timeline.qml:502: ReferenceError: proxy is not defined
qrc:/qml/timeline.qml:482: ReferenceError: proxy is not defined
[New Thread 0x7ffe577fe6c0 (LWP 6139)]
[New Thread 0x7ffe56ffd6c0 (LWP 6140)]
[New Thread 0x7ffe567fc6c0 (LWP 6141)]
[New Thread 0x7ffe55ffb6c0 (LWP 6142)]
NO PREVIOUS TIMELINE
::: connecting timeline:
QUuid("{4bc97da3-95d1-4f61-a39c-ae3ac1c1ad9b}") , DUR: 0
[New Thread 0x7fff1e39f6c0 (LWP 6143)]
[New Thread 0x7ffe557fa6c0 (LWP 6144)]
root context get sub model new function
[New Thread 0x7ffe54ff96c0 (LWP 6145)]
[New Thread 0x7ffe33fff6c0 (LWP 6146)]
[New Thread 0x7ffe337fe6c0 (LWP 6147)]
[New Thread 0x7ffe32ffd6c0 (LWP 6148)]
[New Thread 0x7ffe327fc6c0 (LWP 6149)]
INVALID BIN PLAYLIST...
=== OPENING FILE WITH TRACKS: 5
[New Thread 0x7ffe31ffb6c0 (LWP 6150)]
QWaylandGLContext::makeCurrent: eglError: 3002, this: 0x5c0a70c0
Could you have a look here? I think this eglError is the relevant part.
Full information could be found here: https://bugs.debian.org/1001132
@Bob:
Please also report your issue here and mail me the bugid after that:
https://kdenlive.org/en/bug-reports/
Bug#1001132: kdenlive: Unable to Start with Use GPU processing (Movit libary) enabled
Can you install the dbgsym packages and run it with gdb and send a backtrace? Am 12.12.2023 um 16:21 schrieb Bob Wong: 在 2023年12月12日星期二 CST 下午11:05:29，您写道： Hey Am 05.12.2021 um 02:22 schrieb Bob Wong: Package: kdenlive Version: 21.08.3-1 Severity: normal X-Debbugs-Cc:ybx...@gmail.com Dear Maintainer, The software crashes with Use GPU processing function enabled. Do you still have this issue with kdenlive 23.08.4-1? Yes. If I enable the GPU rendering, the software will still crash. -- System Information: Debian Release: trixie/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.5.0-5-amd64 (SMP w/12 CPU threads; PREEMPT) Locale: LANG=zh_CN.UTF-8, LC_CTYPE=zh_CN.UTF-8 (charmap=UTF-8), LANGUAGE=zh_CN:zh Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages kdenlive depends on: ii breeze 4:5.27.9-1 ii breeze-icon-theme 4:5.107.0-1 ii ffmpeg 7:6.1-5 ii gstreamer1.0-plugins-bad 1.22.7-1 ii kded5 5.107.0-1 ii kdenlive-data 23.08.3-1 ii kinit 5.107.0-1 ii kio5.107.0-1 ii libc6 2.37-12 ii libkf5archive5 5.107.0-1 ii libkf5bookmarks5 5.107.0-1 ii libkf5codecs5 5.107.0-1 ii libkf5completion5 5.107.0-1 ii libkf5configcore5 5.107.0-1 ii libkf5configgui5 5.107.0-1 ii libkf5configwidgets5 5.107.0-2 ii libkf5coreaddons5 5.107.0-1 ii libkf5crash5 5.107.0-1 ii libkf5dbusaddons5 5.107.0-1 ii libkf5filemetadata35.107.0-1+b1 ii libkf5guiaddons5 5.107.0-1 ii libkf5i18n55.107.0-1+b1 ii libkf5iconthemes5 5.107.0-1+b1 ii libkf5itemviews5 5.107.0-1 ii libkf5jobwidgets5 5.107.0-1 ii libkf5kiocore5 5.107.0-1 ii libkf5kiofilewidgets5 5.107.0-1 ii libkf5kiogui5 5.107.0-1 ii libkf5kiowidgets5 5.107.0-1 ii libkf5newstuffwidgets5 5.107.0-2 ii libkf5notifications5 5.107.0-1 ii libkf5notifyconfig55.107.0-1 ii libkf5purpose-bin 5.107.0-1 ii libkf5purpose5 5.107.0-1 ii libkf5solid5 5.107.0-1 ii libkf5textwidgets5 5.107.0-1 ii libkf5widgetsaddons5 5.107.0-1 ii libkf5xmlgui5 5.107.0-1+b1 ii libmlt++7 7.22.0-1 ii libmlt77.22.0-1 ii libqt5core5a 5.15.10+dfsg-5 ii libqt5dbus55.15.10+dfsg-5 ii libqt5gui5 5.15.10+dfsg-5 ii libqt5multimedia5 5.15.10-2 ii libqt5network5 5.15.10+dfsg-5 ii libqt5networkauth5 5.15.10-2 ii libqt5qml5 5.15.10+dfsg-2 ii libqt5quick5 5.15.10+dfsg-2 ii libqt5quickcontrols2-5 5.15.10+dfsg-2 ii libqt5quickwidgets55.15.10+dfsg-2 ii libqt5svg5 5.15.10-2 ii libqt5widgets5 5.15.10+dfsg-5 ii libqt5xml5 5.15.10+dfsg-5 ii libstdc++6 13.2.0-7 ii melt 7.22.0-1 ii qml-module-org-kde-kcm 5.107.0-1 ii qml-module-org-kde-newstuff5.107.0-2 ii qml-module-qtgraphicaleffects 5.15.10-2 ii qml-module-qtqml-models2 5.15.10+dfsg-2 ii qml-module-qtquick-controls5.15.10-2 ii qml-module-qtquick-controls2 5.15.10+dfsg-2 ii qml-module-qtquick-dialogs 5.15.10-2 ii qml-module-qtquick-layouts 5.15.10+dfsg-2 ii qml-module-qtquick-window2 5.15.10+dfsg-2 ii qml-module-qtquick25.15.10+dfsg-2 Versions of packages kdenlive recommends: ii dvdauthor 0.7.2-2 ii dvgrab 3.5+git20160707.1.e46042e-1+b1 ii frei0r-plugins 1.8.0-1+b1 ii genisoimage9:1.1.11-3.4 ii oxygen-icon-theme 5:5.107.0-1 ii recordmydesktop0.4.0-1+b1 ii swh-plugins0.4.17-3 Versions of packages kdenlive suggests: ii khelpcenter 4:23.08.3-1 ii vlc 3.0.20-1+b1 -- no debconf information
Bug#1003378: More more data for Bug 1003378
Hey Am 22.01.2022 um 01:35 schrieb Kingsley G. Morse Jr.: Hi Patrick, Thanks again. I tried your suggestion Does it work for you again if you only downgrade kdenlive and kdenlive-data again to 21.12.0-1? I downgraded kdenlive and kdenlive-data to version 21.12.0-1. I still got the same error. The following is attached... 1.) Stdout and stderr recorded by $ kdenlive 2>&1 | tee /tmp/kdenlive.log 2.) A screen shot of kdenlive's orange error box. Do you still have this issue with kdenlive 23.08.4-1?
Bug#1001132: kdenlive: Unable to Start with Use GPU processing (Movit libary) enabled
Hey Am 05.12.2021 um 02:22 schrieb Bob Wong: Package: kdenlive Version: 21.08.3-1 Severity: normal X-Debbugs-Cc:ybx...@gmail.com Dear Maintainer, The software crashes with Use GPU processing function enabled. Do you still have this issue with kdenlive 23.08.4-1?
Bug#1013285: needrestart: Failed to check for processor microcode upgrades.
Hey Am 21.11.2023 um 17:23 schrieb Antoine Beaupré: Control: reopen -1 Control: subscribe -1 On 2023-11-15 15:46:24, Antoine Beaupré wrote: Control: tags -1 +patch On 2023-11-15 14:54:26, Antoine Beaupré wrote: On 2022-06-20 13:54:38, Nick Lewycky wrote: Package: needrestart Version: 3.6-1 Severity: normal `sudo needrestart -w` always prints "Failed to check for processor microcode upgrades." on my AMD Ryzen 9 3900X 12-Core Processor. [...] There's now a PR for this upstream: https://github.com/liske/needrestart/pull/285 People suffering from this issue are encouraged to test this and report back upstream (or here, if you can't upstream). I tested it and it doesn't work. It only *seemed* to work because the author tested with -v, which *does* work around the issue. I found the issue, and sent this PR upstream to fix it: https://github.com/liske/needrestart/pull/288 Patch attached, people are again encouraged to test and report back. I also attach upstream commit v3.6-9-ge85bfe3 which also seem necessary to fix firmware checks on my end... It doesn't *quite* fix it just yet. For platforms where the ucode is *not* provided (e.g. in my case it's the pcengines APU that don't have firmware upgrades), this *still* yields a UNKNOWN warning. After a brief discussion in the issue tracker, I decided to submit *another* PR as such: https://github.com/liske/needrestart/pull/290 ... and I think we should ship this in Debian as well. I also think we should make a stable update for this. This affects a bunch of machines on our end and we need this fixed in bookworm. So I'll file a bug with the release team and prepare a stable update. Patrick: objections? A. I will upload this patch now with 3.6-7. I am fine with a stable update and would welcome it if you could do it in this case (I am a bit busy these weeks) Thanks!
Bug#1056193: is actually a bug, sorry
tag #1056193 + pending
thanks
Hey,
I will upload the attached patch with my next upload. But this is
nothing I can fix in stable => since an update will break again now
working setups using /usr/lib/ssl/..
The best option would be if gluster would make the paths configureable
btw I may also upload 11.x this year to bookworm-backports
Am 03.12.2023 um 01:40 schrieb David Bremner:
That's all very well, but glusterd is not looking in a subdirectory of
/usr/lib/ssl it is looking for /usr/lib/ssl/glusterfs.pem, as pointed
out above.
FYI, upstreams docs [1] show gluster looking in /etc/ssl, not in a
subdirectory.
https://docs.gluster.org/en/latest/Administrator-Guide/SSL/
*# On Debian like systems the output of openssl version -d is /usr/lib/ssl,
# where are symlinks in it to the correct directories in /etc/ssl.
# But glusterfs hardcodes the certificate files to be placed directly in
# /usr/lib/ssl, without the correct subdirectories. So that it is possible
# again to store the certificate data in /etc/ssl/ we hardcode the path now.
# A better solution would be to configure the paths in the volfiles, but
that
# is not possible, yet.
# Closes: #1056193
diff -Naur glusterfs-11.1.orig/configure glusterfs-11.1/configure
--- glusterfs-11.1.orig/configure 2023-11-06 16:24:29.990040453 +0100
+++ glusterfs-11.1/configure 2023-12-12 11:59:03.930931968 +0100
@@ -14553,7 +14553,7 @@
{ $as_echo "$as_me:${as_lineno-$LINENO}: checking for OpenSSL trusted
certificates path" >&5
$as_echo_n "checking for OpenSSL trusted certificates path... " >&6; }
-SSL_CERT_PATH=$(openssl version -d | sed -e 's|OPENSSLDIR: "\(.*\)".*|\1|')
+SSL_CERT_PATH=/etc/ssl
if test -d "${SSL_CERT_PATH}" 1>/dev/null 2>&1; then
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: $SSL_CERT_PATH" >&5
$as_echo "$SSL_CERT_PATH" >&6; }
diff -Naur glusterfs-11.1.orig/configure.ac glusterfs-11.1/configure.ac
--- glusterfs-11.1.orig/configure.ac 2023-11-06 16:24:25.401026631 +0100
+++ glusterfs-11.1/configure.ac 2023-12-12 11:59:20.278889134 +0100
@@ -803,7 +803,7 @@
dnl Find out OpenSSL trusted certificates path
AC_MSG_CHECKING([for OpenSSL trusted certificates path])
-SSL_CERT_PATH=$(openssl version -d | sed -e 's|OPENSSLDIR: "\(.*\)".*|\1|')
+SSL_CERT_PATH=/etc/ssl
if test -d "${SSL_CERT_PATH}" 1>/dev/null 2>&1; then
AC_MSG_RESULT([$SSL_CERT_PATH])
AC_DEFINE_UNQUOTED(SSL_CERT_PATH, ["$SSL_CERT_PATH"], [Path to
OpenSSL trusted certificates.])
*
Bug#1057724: imvirt FTCBFS: confuses build and host
tag #1057724 + pending thanks Thanks for your patch, it will be fixed with the next upload Am 07.12.2023 um 12:46 schrieb Helmut Grohne: Source: imvirt Version: 0.9.6-11 Tags: patch User: debian-cr...@lists.debian.org Usertags: ftcbfs imvirt fails to cross build from source, because it confuses build and host in a number of occasions: * configure is run without the --host parameter thus defaulting to build. * debian/rules matches on host rather than build. * configure examines uname, which is host, while it should be examining host_alias and things derived from that. I'm attaching a patch fixing all of that. Consider applying it. Helmut
Bug#1056358: bookworm-pu: package needrestart/3.6-4+deb12u1
thanks for taking care! Am 21.11.2023 um 17:35 schrieb Antoine Beaupre: Package: release.debian.org Severity: normal Tags: bookworm User: release.debian@packages.debian.org Usertags: pu X-Debbugs-Cc: needrest...@packages.debian.org, pmatth...@debian.org Control: affects -1 + src:needrestart [ Reason ] needrestart, starting with bookworm, supports more microcode checks than before. In particular, it now checks AMD CPUs. The amd64-microcode package seem to ship *less* firmware files than its Intel counterpart, which leads to *many* machines (half a dozen) in our fleet to suddenly start warning us about "UNKNOWN" firmware status. [ Impact ] Spurious warnings lead to alert fatigue and consequently untimely security upgrades, which is the main reason why I'm considering this serious enough to warrant a stable update. [ Tests ] The provided patches were tested in production on a fleet (~50 machines) of Debian bookworm servers on torproject.org. [ Risks ] Code is relatively simple. There's a risk that operators who did *not* install the amd64-microcode package will not get a warning, but that's consider an operator error, and out of scope for this. [ Checklist ] [x] *all* changes are documented in the d/changelog [x] I reviewed all changes and I approve them [x] attach debdiff against the package in (old)stable [~] the issue is verified as fixed in unstable [ Changes ] There are three patches here: 1. 05-fix-AMD-ucode-checking-in-non-debug-mode.patch - fixes a bug where AMD microcode checks would fail unless -v is passed 2. 06-uCode-fix-uninitialized-value-in-logging-of-processo.patch - fix uninitialized variable error, required for the other patches to work 3. 07-mark-unavailable-firmware-as-CURRENT.patch - do not mark unavailable firmware as "UNKNOWN" The first and second patches have shipped into unstable with the -6 release, the last patch is pending. [ Other info ] anarcat@angela:dist$ debdiff needrestart_3.6-4.dsc needrestart_3.6-4+deb12u1.dsc| diffstat dpkg-source: warning: extracting unsigned source package (/home/anarcat/dist/needrestart_3.6-4+deb12u1.dsc) changelog |6 patches/05-fix-AMD-ucode-checking-in-non-debug-mode.patch | 33 + patches/06-uCode-fix-uninitialized-value-in-logging-of-processo.patch | 30 patches/07-mark-unavailable-firmware-as-CURRENT.patch | 61 ++ patches/series|3 5 files changed, 133 insertions(+) We might also want to consider updating to the unstable version directly, as the patch is relatively similar, in fact it's currently *smaller* because it's lacking the third patch here: anarcat@angela:dist[1]$ debdiff needrestart_3.6-4.dsc needrestart_3.6-6.dsc | diffstat NEWS |8 -- changelog| 26 +++ control |1 patches/05-fix-AMD-ucode-checking-in-non-debug-mode.diff | 33 ++ patches/06-uCode-fix-uninitialized-value-in-logging-of-processo.diff | 30 + patches/series |2 6 files changed, 91 insertions(+), 9 deletions(-)
Bug#1054398: bing: error "not enough hosts were found to perform the bandwidth analysis"
Hey,
Am 23.10.2023 um 12:21 schrieb Sanjoy Mahajan:
Package: bing
Version: 1.3.5-5
Severity: grave
X-Debbugs-Cc: none, Sanjoy Mahajan
Bing has not worked for me for many versions. bing 1.1 works fine, but
1.3 in all versions that I've tried for years always fails. Here's the
log from a typical example ("gw" is the router on the local network).
It always fails with the error "not enough hosts were found to perform
the bandwidth analysis".
# bing localhost gw
Found 2 key hosts
0: localhost (127.0.0.1)
1: gw (192.168.7.1)
--
What happens if you use bing 192.168.7.123 192.168.7.1
where .1 is your gw and .123 your own ipv4 in this subnet instead of
localhost
Bug#1039604: glusterfs: Drop support for 32-bit architectures
Hey Am 24.08.2023 um 18:48 schrieb Michael Tokarev: So, it looks like after dropping support for 32bit architectures from this package, but did you file ANAIS bug report against ftp.debian.org? Without such a bug report, new glusterfs will never migrate to testing due to missing builds on 32bit architectures, and this will hold all dependent packages in unstable too. /mjt Yes sorry it is now removed -- /* Mit freundlichem Gruß / With kind regards, Patrick Matthäi GNU/Linux Debian Developer Blog: https://www.linux-dev.org/ E-Mail: pmatth...@debian.org patr...@linux-dev.org */
Bug#1050487: RM: glusterfs [armel armhf i386 mipsel alpha arc hppa hurd-i386 loong64 m68k powerpc sh4 x32] -- ANAIS; 32bit support has been dropped from glusterfs
Package: ftp.debian.org Severity: normal User: ftp.debian@packages.debian.org Usertags: remove X-Debbugs-Cc: gluste...@packages.debian.org Control: affects -1 + src:glusterfs Please remove the package from the above architectures to unblock the dependencies and itself. Thank you
Bug#1049587: znc: Fails to build binary packages again after successful build
Hello Lucas, Am 16.08.2023 um 09:42 schrieb Lucas Nussbaum: Source: znc Version: 1.8.2-3.1 Severity: minor Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-binary-20230816 ftbfs-binary-after-build User: debian...@lists.debian.org Usertags: qa-doublebuild I have fixed now all bugs submitted from you, all bugs? Nooo, not this one ;) I can not reproduce this specific issue. I am using pbuilder with --twice for it (which also works for the other packages+bugs). Could you retest it with an up-to-date sid toolchain? Maybe it was a temporary bug, or a problem with the build host.. cd /<>/obj-x86_64-linux-gnu/modules/modperl && /usr/bin/cmake -E tar xz /<>/modules/modperl/generated.tar.gz [ 3%] Generating swigpyrun.h, znc_core.py, modpython_biglib.cpp, pyfunctions.cpp cd /<>/obj-x86_64-linux-gnu/modules/modpython && /usr/bin/cmake -E tar xz /<>/modules/modpython/generated.tar.gz make[3]: Leaving directory '/<>/obj-x86_64-linux-gnu' make -f modules/po/CMakeFiles/po_admindebug_bg_BG.dir/build.make modules/po/CMakeFiles/po_admindebug_bg_BG.dir/build make[3]: Entering directory '/<>/obj-x86_64-linux-gnu' make[3]: Leaving directory '/<>/obj-x86_64-linux-gnu' make -f modules/po/CMakeFiles/po_admindebug_ru_RU.dir/build.make modules/po/CMakeFiles/po_admindebug_ru_RU.dir/build make[3]: Entering directory '/<>/obj-x86_64-linux-gnu' CMake Error: Problem with archive_write_header(): Can't create 'modperl_biglib.cpp' CMake Error: Current file: modperl_biglib.cpp CMake Error: Problem extracting tar: /<>/modules/modperl/generated.tar.gz make[3]: *** [modules/modperl/CMakeFiles/modperl_swig.dir/build.make:77: modules/modperl/swigperlrun.h] Error 1 This is the only thing I can find in the build logs, but this does not happen on my host Thank you
Bug#1041998: glusterfs uploaded to unstable
severity #1041999 serious severity #1041998 serious thanks Hey, glusterfs 11.0 is now in unstable
Bug#1041999: tgt: Drop glusterfs support for 32-bit architectures
Source: tgt Version: 1:1.0.85-1 Severity: important Hello, because of the bug #1039604 [0] I will drop glusterfs completly from non x64 architectures. You package has a reverse dependency on. So you should change your (build)-dependeny e.g. on libglusterfs-dev to: libglusterfs-dev [amd64 arm64 ppc64el ppc64 riscv64 mips64el s390x ia64 sparc64] In experimental with glusterfs 11.0-1 the !x64 support has been already dropped. I plan to upload it to unstable after the reverse dependencies are fixed. If you need help, please let me know :) [0]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1039604 -- System Information: Debian Release: 12.1 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 6.1.0-10-amd64 (SMP w/2 CPU threads; PREEMPT) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
Bug#1041996: samba: Drop glusterfs support for 32-bit architectures
Source: samba Version: 2:4.18.5+dfsg-1 Severity: important Hello, because of the bug #1039604 [0] I will drop glusterfs completly from non x64 architectures. You package has a reverse dependency on. So you should change your (build)-dependeny e.g. on libglusterfs-dev to: libglusterfs-dev [amd64 arm64 ppc64el ppc64 riscv64 mips64el s390x ia64 sparc64] In experimental with glusterfs 11.0-1 the !x64 support has been already dropped. I plan to upload it to unstable after the reverse dependencies are fixed. If you need help, please let me know :) [0]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1039604 -- System Information: Debian Release: 12.1 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 6.1.0-10-amd64 (SMP w/2 CPU threads; PREEMPT) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
Bug#1041998: nfs-ganesha: Drop glusterfs support for 32-bit architectures
Source: nfs-ganesha Version: 4.3-2 Severity: important Hello, because of the bug #1039604 [0] I will drop glusterfs completly from non x64 architectures. You package has a reverse dependency on. So you should change your (build)-dependeny e.g. on libglusterfs-dev to: libglusterfs-dev [amd64 arm64 ppc64el ppc64 riscv64 mips64el s390x ia64 sparc64] In experimental with glusterfs 11.0-1 the !x64 support has been already dropped. I plan to upload it to unstable after the reverse dependencies are fixed. If you need help, please let me know :) [0]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1039604 -- System Information: Debian Release: 12.1 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 6.1.0-10-amd64 (SMP w/2 CPU threads; PREEMPT) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
Bug#1041995: fio: Drop glusterfs support for 32-bit architectures
Source: fio Version: 3.35-1 Severity: important Hello, because of the bug #1039604 [0] I will drop glusterfs completly from non x64 architectures. You package has a reverse dependency on. So you should change your (build)-dependeny e.g. on libglusterfs-dev to: libglusterfs-dev [amd64 arm64 ppc64el ppc64 riscv64 mips64el s390x ia64 sparc64] In experimental with glusterfs 11.0-1 the !x64 support has been already dropped. I plan to upload it to unstable after the reverse dependencies are fixed. If you need help, please let me know :) [0]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1039604 -- System Information: Debian Release: 12.1 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 6.1.0-10-amd64 (SMP w/2 CPU threads; PREEMPT) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
Bug#1041997: libvirt: Drop glusterfs support for 32-bit architectures
Source: libvirt Version: 9.5.0-1 Severity: important Hello, because of the bug #1039604 [0] I will drop glusterfs completly from non x64 architectures. You package has a reverse dependency on. So you should change your (build)-dependeny e.g. on libglusterfs-dev to: libglusterfs-dev [amd64 arm64 ppc64el ppc64 riscv64 mips64el s390x ia64 sparc64] In experimental with glusterfs 11.0-1 the !x64 support has been already dropped. I plan to upload it to unstable after the reverse dependencies are fixed. If you need help, please let me know :) [0]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1039604 -- System Information: Debian Release: 12.1 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 6.1.0-10-amd64 (SMP w/2 CPU threads; PREEMPT) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
Bug#1039604: glusterfs: Drop support for 32-bit architectures
Hello, Am 15.07.2023 um 08:54 schrieb Michael Tokarev: Yes, I use libglusterfs-dev in Build-Depends of samba and qemu. I think it is already reduced to 64bits on ubuntu for samba (or, rather, i386 is excluded). The question is: how to specify dependencies properly and more important, how to specify lists of files to install? I have uploaded glusterfs 11.0-1 to experimental, it is limited to these architectures: amd64 arm64 ppc64el ppc64 riscv64 mips64el s390x ia64 sparc64 So if nobody rises up I would start to fill bugs for the reverse dependencies in the next days and after that uploading glusterfs 11.x to unstable. What happens with stable, there I do not have an answer, yet. Right now I have: d/control: Build-Depends: libglusterfs-dev d/foo.install: /usr/lib/foo/gluster.so I can change the first one to be something like Build-Depends: libglusterfs-dev [amd64 arm64] So in your depends you should use: libglusterfs-dev [amd64 arm64 ppc64el ppc64 riscv64 mips64el s390x ia64 sparc64] (with a few questions remaining: what is the complete list? How about non-linux?). But what to do with the second, - move the handling to d/rules, like if [ -f debian/tmp/usr/lib/foo/gluster.so ]; then install -D debian/tmp/usr/lib/foo/gluster.so -t debian/foo/usr/lib/foo/ fi IMO the best way would be continue to use dh_install, there you can also limit the architectures: [amd64 arm64 ppc64el ppc64 riscv64 mips64el s390x ia64 sparc64] debian/tmp/usr/lib/foo/gluster.so You way would work, too. But if you want to build the glusterfs module, but it is not available (for whatever reason) you wouldnt notice it.
Bug#1039604: glusterfs: Drop support for 32-bit architectures
*ping* (also adding some other maintainers of reverse depends) Am 04.07.2023 um 16:12 schrieb Patrick Matthäi: Hey, (@debian-release, pls CC me) Am 27.06.2023 um 20:13 schrieb Sergio Durigan Junior: Source: glusterfs Version: 10.3-5 Severity: important Hi, Upstream glusterfs has given several indications that they do not care about/support 32-bit architectures, as can be seen in this (non-exhaustive) list of issues: - https://github.com/gluster/glusterfs/issues/3911 - https://github.com/gluster/glusterfs/issues/702 Moreover, in Ubuntu, where glusterfs is built for armhf, some issues have been filed about problems related to this lack of 32-bit support, like: - https://bugs.launchpad.net/ubuntu/+source/glusterfs/+bug/1991441 - https://bugs.launchpad.net/ubuntu/+source/glusterfs/+bug/1951408 The underlying issue in these two bugs happen to be correlated: glusterfs requires that the host supports 64-bit atomic operations, but armhf and other 32-bit architectures don't offer such feature. Therefore, I would like to request that the support for 32-bit architecture in Debian's glusterfs package be dropped, please. A quick investigation tells me that these packages will likely need to be adjusted because they depend on glusterfs: Reverse-Build-Depends * fio (for libglusterfs-dev) * libvirt (for libglusterfs-dev) * nfs-ganesha (for libglusterfs-dev) * qemu (for libglusterfs-dev) * qemu (for glusterfs-common) * tgt (for libglusterfs-dev) * uwsgi (for libglusterfs-dev) Reverse-Build-Depends-Arch * samba (for libglusterfs-dev) Let me know if there's anything I can do to help here. Thanks, OK I think this is a realy bad situation, also just so short after the bookworm release.. @Release team: What is your opinion about it, should we remove glusterfs on 32 bit platforms from bookworm? How should we coordinate it also with the other reverse dependencies? Or should we leave it as it is (for bookworm) and change it for the upcoming releases?
Bug#1040957: xine-lib-1.2: FTBFS on hurd-i386
Am 13.07.2023 um 07:05 schrieb Pino Toscano: Source: xine-lib-1.2 Version: 1.2.13+hg20230710-1 Severity: important Tags: patch User: debian-h...@lists.debian.org Usertags: hurd Control: found -1 1.2.12-1 Hi, xine-lib-1.2 currently FTBFSes on hurd-i386 [1]. The problem is that the VAAPI support is not available on hurd-i386, and libxine2-x unconditionally installs files that are built for that. The attached patch fixes the issue, by limiting the VAAPI plugins that were not already limited on some architectures (e.g. the wayland one) as !hurd-any, like the libva-dev build dependency. As I was tweaking/fixing the packaging for hurd-i386, I included also few more Hurd-related changes: - enable the smb plugin also on the Hurd, as samba is now built there - change the exclusion architecture pattern for the vcdo plugin to !hurd-any, as it applies to any Hurd architecture and not only to hurd-i386 [1] https://buildd.debian.org/status/fetch.php?pkg=xine-lib-1.2=hurd-i386=1.2.13%2Bhg20230710-1=1689013434=0 Thanks, Thank you very much for your patch and improvements, I will include it with the next upload
Bug#1040201: closed by Debian FTP Masters (reply to Patrick Matthäi ) (Bug#1040201: fixed in xine-lib-1.2 1.2.13+hg20230704-1)
Hey Am 07.07.2023 um 14:31 schrieb Janek Stolarek: Thanks. Would it be possible to make another pull from libxine2 upstream? One more fix was added and we need that to fix volume in TDE. Done, I have just uploaded 1.2.13+hg20230710-1 Also, what needs to happen for this upstream version of libxine2 to be migrated to testing? Janek It needs some "aging" and should not introduce new critical bugs, also the other dependencies have to fullfil these requirements. The last upload from me just migrated to testing. You can check the status (why is it not in testing yet) here https://qa.debian.org/excuses.php?package=xine-lib-1.2
Bug#1038176: criticalmass: Depends on SDL 1.2
Am 04.07.2023 um 16:55 schrieb Simon McVittie:
On Tue, 04 Jul 2023 at 16:03:56 +0200, Patrick Matthäi wrote:
In this case I still require the addons libsdl-image1.2-dev and
libsdl-mixer1.2-dev, without criticalmass does not work / build. What to do
here? The package is upstream dead.
In the short term, please test with libsdl1.2-compat-{shim,dev} and
report any regressions as sdl12-compat bugs, then leave this bug open,
without any changes to the package.
The problem is without the mixer and image extension it does not build
at all or should I mix the dependencies (using mixer and image as before
and just switch main sdl to the compat one?)
Bug#1039604: glusterfs: Drop support for 32-bit architectures
Hey, (@debian-release, pls CC me) Am 27.06.2023 um 20:13 schrieb Sergio Durigan Junior: Source: glusterfs Version: 10.3-5 Severity: important Hi, Upstream glusterfs has given several indications that they do not care about/support 32-bit architectures, as can be seen in this (non-exhaustive) list of issues: - https://github.com/gluster/glusterfs/issues/3911 - https://github.com/gluster/glusterfs/issues/702 Moreover, in Ubuntu, where glusterfs is built for armhf, some issues have been filed about problems related to this lack of 32-bit support, like: - https://bugs.launchpad.net/ubuntu/+source/glusterfs/+bug/1991441 - https://bugs.launchpad.net/ubuntu/+source/glusterfs/+bug/1951408 The underlying issue in these two bugs happen to be correlated: glusterfs requires that the host supports 64-bit atomic operations, but armhf and other 32-bit architectures don't offer such feature. Therefore, I would like to request that the support for 32-bit architecture in Debian's glusterfs package be dropped, please. A quick investigation tells me that these packages will likely need to be adjusted because they depend on glusterfs: Reverse-Build-Depends * fio (for libglusterfs-dev) * libvirt (for libglusterfs-dev) * nfs-ganesha (for libglusterfs-dev) * qemu (for libglusterfs-dev) * qemu (for glusterfs-common) * tgt (for libglusterfs-dev) * uwsgi (for libglusterfs-dev) Reverse-Build-Depends-Arch * samba (for libglusterfs-dev) Let me know if there's anything I can do to help here. Thanks, OK I think this is a realy bad situation, also just so short after the bookworm release.. @Release team: What is your opinion about it, should we remove glusterfs on 32 bit platforms from bookworm? How should we coordinate it also with the other reverse dependencies? Or should we leave it as it is (for bookworm) and change it for the upcoming releases?
Bug#1038376: guichan: Depends on SDL 1.2
Hey Am 17.06.2023 um 11:49 schrieb Simon McVittie: Source: guichan Tags: trixie sid User: pkg-sdl-maintain...@lists.alioth.debian.org Usertags: libsdl1.2 In this case the package also requires the libsdl-image1.2-dev extension to build the binary package libguichan-sdl-0.8.1-1v5 The problem is I can not drop it, because it still has rlvm and mokomaze as reverse dependencies and guichan itself is upstream dead.
Bug#1038176: criticalmass: Depends on SDL 1.2
Hey, Am 16.06.2023 um 13:42 schrieb Simon McVittie: Source: criticalmass Tags: trixie sid User: pkg-sdl-maintain...@lists.alioth.debian.org Usertags: libsdl1.2 In this case I still require the addons libsdl-image1.2-dev and libsdl-mixer1.2-dev, without criticalmass does not work / build. What to do here? The package is upstream dead.
Bug#1038506: libmlt7: Contains a plugin for an obsolete version of SDL
Hey Am 18.06.2023 um 18:42 schrieb Simon McVittie: Package: libmlt7 Version: 7.14.0-1 Tags: trixie sid User: pkg-sdl-maintain...@lists.alioth.debian.org Usertags: libsdl1.2 libmlt7 appears to contain plugins for both SDL 1.2 and SDL 2, and as a result, it depends on both libsdl1.2debian and libsdl2-2.0-0. SDL 1.2 is unmaintained upstream and we should be trying to move away from it. Various Debian packages depend on mlt: - flowblade Flowblade itself still uses SDL 1.2: https://sourceforge.net/p/mlt/mailman/message/37862164/ - kdenlive - shotcut - synfig - synfigstudio but as far as I can see, none of them need SDL 1.2 specifically. Would it be possible to disable/remove the SDL 1.2 plugin in mlt? Thanks, smcv -- /* Mit freundlichem Gruß / With kind regards, Patrick Matthäi GNU/Linux Debian Developer Blog: https://www.linux-dev.org/ E-Mail: pmatth...@debian.org patr...@linux-dev.org */
Bug#1036989: unblock: needrestart/3.6-4
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
X-Debbugs-Cc: tho...@fiasko-nw.net
Please unblock package needrestart
[ Reason ]
In the past I have used the wrong version number, to remove a leftover config
file.
Also this update should close two noisy bugs (ignore serial-getty) and
especially
make the VM & microcode detection work again (just produced by a small typo).
[ Impact ]
Some smaller but noisy bugs.
[ Tests ]
Automated: debian/tests/sanity-test.sh
I also manual tested the update
[ Risks ]
Small diffs, I do not see a risk here.
[ Checklist ]
[x ] all changes are documented in the d/changelog
[x ] I reviewed all changes and I approve them
[x ] attach debdiff against the package in testing
unblock needrestart/3.6-4
diff -Nru needrestart-3.6/debian/changelog needrestart-3.6/debian/changelog
--- needrestart-3.6/debian/changelog2023-01-12 11:08:33.0 +0100
+++ needrestart-3.6/debian/changelog2023-05-31 16:47:03.0 +0200
@@ -1,3 +1,15 @@
+needrestart (3.6-4) unstable; urgency=medium
+
+ * Remove leftover conffile 30-pacman with 3.6-4.
+Closes: #1036526
+ * Add patch 03-ignore-serial-getty from Helmut Grohne to ignore serial-getty.
+Closes: #1035721
+ * Add upstream patch 04-vm-detection to fix a typo, which prevents the VM and
+microcode detection.
+Closes: #1026026
+
+ -- Patrick Matthäi Wed, 31 May 2023 16:47:03 +0200
+
needrestart (3.6-3) unstable; urgency=medium
* Adjust debian/watch to work again with GitHub.
diff -Nru needrestart-3.6/debian/needrestart.postinst
needrestart-3.6/debian/needrestart.postinst
--- needrestart-3.6/debian/needrestart.postinst 2023-01-12 11:08:33.0
+0100
+++ needrestart-3.6/debian/needrestart.postinst 2023-05-31 16:47:03.0
+0200
@@ -2,6 +2,6 @@
set -e
-dpkg-maintscript-helper rm_conffile /etc/needrestart/hook.d/30-pacman 3.5-4 --
"$@"
+dpkg-maintscript-helper rm_conffile /etc/needrestart/hook.d/30-pacman 3.6-4 --
"$@"
#DEBHELPER#
diff -Nru needrestart-3.6/debian/needrestart.postrm
needrestart-3.6/debian/needrestart.postrm
--- needrestart-3.6/debian/needrestart.postrm 2023-01-12 11:08:33.0
+0100
+++ needrestart-3.6/debian/needrestart.postrm 2023-05-31 16:47:03.0
+0200
@@ -2,6 +2,6 @@
set -e
-dpkg-maintscript-helper rm_conffile /etc/needrestart/hook.d/30-pacman 3.5-4 --
"$@"
+dpkg-maintscript-helper rm_conffile /etc/needrestart/hook.d/30-pacman 3.6-4 --
"$@"
#DEBHELPER#
diff -Nru needrestart-3.6/debian/needrestart.preinst
needrestart-3.6/debian/needrestart.preinst
--- needrestart-3.6/debian/needrestart.preinst 2023-01-12 11:08:33.0
+0100
+++ needrestart-3.6/debian/needrestart.preinst 2023-05-31 16:47:03.0
+0200
@@ -2,6 +2,6 @@
set -e
-dpkg-maintscript-helper rm_conffile /etc/needrestart/hook.d/30-pacman 3.5-4 --
"$@"
+dpkg-maintscript-helper rm_conffile /etc/needrestart/hook.d/30-pacman 3.6-4 --
"$@"
#DEBHELPER#
diff -Nru needrestart-3.6/debian/patches/03-ignore-serial-getty.diff
needrestart-3.6/debian/patches/03-ignore-serial-getty.diff
--- needrestart-3.6/debian/patches/03-ignore-serial-getty.diff 1970-01-01
01:00:00.0 +0100
+++ needrestart-3.6/debian/patches/03-ignore-serial-getty.diff 2023-05-31
16:47:03.0 +0200
@@ -0,0 +1,13 @@
+Subject: do not restart serial-getty@*.service
+Author: Helmut Grohne
+
+--- a/ex/needrestart.conf
b/ex/needrestart.conf
+@@ -98,6 +98,7 @@ $nrconf{override_rc} = {
+
+ # gettys
+ qr(^getty@.+\.service) => 0,
++qr(^serial-getty@.+\.service) => 0,
+
+ # systemd --user
+ qr(^user@\d+\.service) => 0,
diff -Nru needrestart-3.6/debian/patches/04-vm-detection.diff
needrestart-3.6/debian/patches/04-vm-detection.diff
--- needrestart-3.6/debian/patches/04-vm-detection.diff 1970-01-01
01:00:00.0 +0100
+++ needrestart-3.6/debian/patches/04-vm-detection.diff 2023-05-31
16:47:03.0 +0200
@@ -0,0 +1,22 @@
+From 27bf4678bb92f68dfadd04ab04e96cba6ea2c376 Mon Sep 17 00:00:00 2001
+From: zxyrepf <53189615+zxyr...@users.noreply.github.com>
+Date: Sun, 24 Jul 2022 08:30:19 +
+Subject: [PATCH] Fix VM detection regression introduced in f54d85c
+
+---
+ needrestart | 2 +-
+ 1 file changed, 1 insertion(+), 1 deletion(-)
+
+diff --git a/needrestart b/needrestart
+index 64509ba..bcec62b 100755
+--- a/needrestart
b/needrestart
+@@ -51,7 +51,7 @@ my $is_tty = (-t *STDERR || -t *STDOUT || -t *STDIN);
+ my $is_vm;
+ my $is_container;
+
+-if($is_systemd && -x q(/usr/bin/systemds-detect-virt)) {
++if($is_systemd && -x q(/usr/bin/systemd-detect-virt)) {
+ # check if we are inside of a vm
+ my $ret = system(qw(/usr/bin/systemd-detect-virt --vm --quiet));
+ unless($? == -1 || $? & 127) {
diff -Nru needrestart-3.6/debian/patches/series
needrestart-3.6/debian/patches/series
-
Bug#1036675: unblock: manaplus/2.1.3.17-5
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package manaplus [ Reason ] fonts-mplus removed the ttf versions of the required fonts, this also results in broken symlinks. I am shipping the embedded version of both font files again [ Impact ] Broken/missing fonts [ Tests ] Manual [ Risks ] -Standards-Version: 4.6.1 +Standards-Version: 4.6.2 I hope this is okay, or had to create an extra branch just for that ;) [ Checklist ] [x ] all changes are documented in the d/changelog [x ] I reviewed all changes and I approve them [x ] attach debdiff against the package in testing unblock manaplus/2.1.3.17-5 diff -Nru manaplus-2.1.3.17/debian/changelog manaplus-2.1.3.17/debian/changelog --- manaplus-2.1.3.17/debian/changelog 2022-09-15 09:04:25.0 +0200 +++ manaplus-2.1.3.17/debian/changelog 2023-05-24 10:40:29.0 +0200 @@ -1,3 +1,11 @@ +manaplus (2.1.3.17-5) unstable; urgency=high + + * Bump Standards-Version to 4.6.2. + * Fix broken symlinks to mplus fonts by shipping the embedded versions. +Closes: #1035874 + + -- Patrick Matthäi Wed, 24 May 2023 10:40:29 +0200 + manaplus (2.1.3.17-4) unstable; urgency=medium * Fix FTBFS with last upload. diff -Nru manaplus-2.1.3.17/debian/control manaplus-2.1.3.17/debian/control --- manaplus-2.1.3.17/debian/control2022-09-15 09:04:25.0 +0200 +++ manaplus-2.1.3.17/debian/control2023-05-24 10:40:29.0 +0200 @@ -3,7 +3,7 @@ Priority: optional Homepage: http://manaplus.org/ Maintainer: Patrick Matthäi -Standards-Version: 4.6.1 +Standards-Version: 4.6.2 Rules-Requires-Root: no Build-Depends: debhelper-compat (= 13), libcurl4-gnutls-dev, @@ -41,7 +41,6 @@ fonts-dejavu-core, fonts-liberation Recommends: manaplus, - fonts-mplus, fonts-wqy-microhei Description: Extended client for Evol Online and The Mana World (data files) ManaPlus is an extended client for Evol Online, The Mana World, and similar diff -Nru manaplus-2.1.3.17/debian/manaplus-data.install manaplus-2.1.3.17/debian/manaplus-data.install --- manaplus-2.1.3.17/debian/manaplus-data.install 2022-09-15 09:04:25.0 +0200 +++ manaplus-2.1.3.17/debian/manaplus-data.install 2023-05-24 10:40:29.0 +0200 @@ -9,3 +9,4 @@ usr/share/manaplus/data/sfx/system usr/share/manaplus/data/perserver usr/share/manaplus/data/translations +usr/share/manaplus/data/fonts/mplus-1p-*.ttf diff -Nru manaplus-2.1.3.17/debian/manaplus-data.links manaplus-2.1.3.17/debian/manaplus-data.links --- manaplus-2.1.3.17/debian/manaplus-data.links2022-09-15 09:04:25.0 +0200 +++ manaplus-2.1.3.17/debian/manaplus-data.links2023-05-24 10:40:29.0 +0200 @@ -6,6 +6,4 @@ usr/share/fonts/truetype/liberation/LiberationSans-Regular.ttf usr/share/manaplus/data/fonts/liberationsans.ttf usr/share/fonts/truetype/liberation/LiberationMono-Bold.ttf usr/share/manaplus/data/fonts/liberationsansmono-bold.ttf usr/share/fonts/truetype/liberation/LiberationMono-Regular.ttf usr/share/manaplus/data/fonts/liberationsansmono.ttf -usr/share/fonts/truetype/mplus/mplus-1p-bold.ttf usr/share/manaplus/data/fonts/mplus-1p-bold.ttf -usr/share/fonts/truetype/mplus/mplus-1p-regular.ttf usr/share/manaplus/data/fonts/mplus-1p-regular.ttf usr/share/fonts/truetype/wqy/wqy-microhei.ttc usr/share/manaplus/data/fonts/wqy-microhei.ttf diff -Nru manaplus-2.1.3.17/debian/not-installed manaplus-2.1.3.17/debian/not-installed --- manaplus-2.1.3.17/debian/not-installed 2022-09-15 09:04:25.0 +0200 +++ manaplus-2.1.3.17/debian/not-installed 2023-05-24 10:40:29.0 +0200 @@ -9,8 +9,6 @@ usr/share/manaplus/data/fonts/liberationsansmono.ttf usr/share/manaplus/data/fonts/dejavuserifcondensed-bold.ttf usr/share/manaplus/data/fonts/wqy-microhei.ttf -usr/share/manaplus/data/fonts/mplus-1p-bold.ttf -usr/share/manaplus/data/fonts/mplus-1p-regular.ttf usr/share/manaplus/data/fonts/dejavusansmono-bold.ttf usr/share/manaplus/data/fonts/liberationsans.ttf usr/share/manaplus/data/fonts/dejavuserifcondensed.ttf
Bug#1036673: unblock: glusterfs/10.3-5
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Please unblock package glusterfs
[ Reason ]
I have applied a patch from 10.4, which fixes a security issue as described in
CVE-2023-26253, #1031731 and https://github.com/gluster/glusterfs/issues/3954
[ Impact ]
Stack buffer overflow
[ Tests ]
Manual and tests driven by upstream
[ Risks ]
Small patch already shipped by upstream, I do not see a risk
[ Checklist ]
[x ] all changes are documented in the d/changelog
[x ] I reviewed all changes and I approve them
[x ] attach debdiff against the package in testing
unblock glusterfs/10.3-5
diff -Nru glusterfs-10.3/debian/changelog glusterfs-10.3/debian/changelog
--- glusterfs-10.3/debian/changelog 2023-01-06 15:56:57.0 +0100
+++ glusterfs-10.3/debian/changelog 2023-05-24 10:48:08.0 +0200
@@ -1,3 +1,12 @@
+glusterfs (10.3-5) unstable; urgency=high
+
+ * Add upstream patch 09-CVE-2023-26253: Resolve asan bug in during receive
+event notification, which results in a stack-buffer-overflow. This
+addresses CVE-2023-26253.
+Closes: #1031731
+
+ -- Patrick Matthäi Wed, 24 May 2023 10:48:08 +0200
+
glusterfs (10.3-4) unstable; urgency=medium
* Add adduser dependency on glusterfs-common.
diff -Nru glusterfs-10.3/debian/patches/09-CVE-2023-26253.diff
glusterfs-10.3/debian/patches/09-CVE-2023-26253.diff
--- glusterfs-10.3/debian/patches/09-CVE-2023-26253.diff1970-01-01
01:00:00.0 +0100
+++ glusterfs-10.3/debian/patches/09-CVE-2023-26253.diff2023-05-24
10:48:08.0 +0200
@@ -0,0 +1,67 @@
+From 0cbf51a9827af0e3a35f5cfa823bfa39740bbc58 Mon Sep 17 00:00:00 2001
+From: mohit84
+Date: Thu, 30 Mar 2023 13:02:19 +0530
+Subject: [PATCH] fuse: Resolve asan bug in during receive event notification
+ (#4024)
+
+The fuse xlator notify function tries to assign data object to graph
+object without checking an event. In case of upcall event data object
+represents upcall object so during access of graph object the process
+crashed for asan build.
+
+Solution: Access the graph->id only while an event is associated
+specifically to fuse xlator
+
+> Fixes: #3954
+> Change-Id: I6b2869256b26d22163879737dcf163510d1cd8bf
+> Signed-off-by: Mohit Agrawal moagr...@redhat.com
+> (Reviewed on upstream link #4019)
+
+Fixes: #3954
+Change-Id: I6b2869256b26d22163879737dcf163510d1cd8bf
+---
+ xlators/mount/fuse/src/fuse-bridge.c | 14 +++---
+ 1 file changed, 11 insertions(+), 3 deletions(-)
+
+diff --git a/xlators/mount/fuse/src/fuse-bridge.c
b/xlators/mount/fuse/src/fuse-bridge.c
+index 89e7725ca7c..583a135fac2 100644
+--- a/xlators/mount/fuse/src/fuse-bridge.c
b/xlators/mount/fuse/src/fuse-bridge.c
+@@ -6484,6 +6484,7 @@ notify(xlator_t *this, int32_t event, void *data, ...)
+ int32_t ret = 0;
+ fuse_private_t *private = NULL;
+ gf_boolean_t start_thread = _gf_false;
++gf_boolean_t event_graph = _gf_true;
+ glusterfs_graph_t *graph = NULL;
+ struct pollfd pfd = {0};
+
+@@ -6492,9 +6493,6 @@ notify(xlator_t *this, int32_t event, void *data, ...)
+
+ graph = data;
+
+-gf_log("fuse", GF_LOG_DEBUG, "got event %d on graph %d", event,
+- ((graph) ? graph->id : 0));
+-
+ switch (event) {
+ case GF_EVENT_GRAPH_NEW:
+ break;
+@@ -6584,9 +6582,19 @@ notify(xlator_t *this, int32_t event, void *data, ...)
+ }
+
+ default:
++/* Set the event_graph to false so that event
++ debug msg would not try to access invalid graph->id
++ while data object is not matched to graph object
++ for ex in case of upcall event data object represents
++ gf_upcall object
++*/
++event_graph = _gf_false;
+ break;
+ }
+
++gf_log("fuse", GF_LOG_DEBUG, "got event %d on graph %d", event,
++ ((graph && event_graph) ? graph->id : -1));
++
+ return ret;
+ }
+
diff -Nru glusterfs-10.3/debian/patches/series
glusterfs-10.3/debian/patches/series
--- glusterfs-10.3/debian/patches/series2023-01-06 15:56:57.0
+0100
+++ glusterfs-10.3/debian/patches/series2023-05-24 10:48:08.0
+0200
@@ -4,3 +4,4 @@
06-spelling-error.diff
07-spelling-error.diff
08-bash-term-in-posix-shell.diff
+09-CVE-2023-26253.diff
Bug#1036671: RM: roarplaylistd -- ROM; Dead upstream project, not maintained and used anymore
Package: ftp.debian.org Severity: normal Please remove the package
Bug#1036672: RM: vclt-tools -- ROM; Dead upstream project, not maintained and used anymore
Package: ftp.debian.org Severity: normal Please remove the package
Bug#1036670: RM: roaraudio -- ROM; Dead upstream project, not maintained and used anymore
Package: ftp.debian.org Severity: normal Please remove the package
Bug#1036669: RM: muroard -- ROM; Dead upstream project, not maintained and used anymore
Package: ftp.debian.org Severity: normal Please remove the package
Bug#1036668: RM: muroar -- ROM; Dead upstream project, not maintained and used anymore
Package: ftp.debian.org Severity: normal Please remove the package
Bug#1036667: RM: ckport -- ROM; Dead upstream project, not maintained and used anymore
Package: ftp.debian.org Severity: normal Please remove the package
Bug#1034774: xine-ui: aborts/killed when trying to play certain videos
Hey Torsten, Am 24.04.2023 um 05:35 schrieb Brian Sammon: Package: xine-ui Version: 0.99.14-1 Severity: normal Dear Maintainer, When I try to view certain videos (one example is at http://br1an.fastmail.fm.user.fm/debian/The_Banshees_Of_Inisherin.mp4 [4MB movie trailer] ) xine aborts/is killed immediately (sometimes after 1/2 sec of sound, but never any video). The following messages appear on the commandline where I ran xine: libva info: VA-API version 1.17.0 libva info: Trying to open /usr/lib/i386-linux-gnu/dri/iHD_drv_video.so libva info: va_openDriver() returns -1 X Error of failed request: BadValue (integer parameter out of range for operation) Major opcode of failed request: 150 (XVideo) Minor opcode of failed request: 13 () Value in failed request: 0x2 Serial number of failed request: 772 Current serial number in output stream: 774 Let me know if there's things I can do to troubleshoot this further. -- System Information: Architecture: i386 (i686) Kernel: Linux 4.19.0-23-686-pae (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages xine-ui depends on: ii libc62.36-9 ii libcurl3-gnutls 7.43.0-1 ii libjpeg62-turbo 1:2.0.6-4 ii liblirc-client0 0.9.4c-9 ii libpng16-16 1.6.37-3 ii libreadline8 8.1-2 ii libx11-6 2:1.8.4-2 ii libxext6 2:1.3.4-1+b1 ii libxft2 2.3.1-2 ii libxine2 1.2.13-1 ii libxine2-ffmpeg 1.2.13-1 ii libxine2-x 1.2.13-1 ii libxinerama1 2:1.1.4-2 ii libxtst6 2:1.2.2-1 ii libxv1 2:1.0.11-1.1 ii libxxf86vm1 1:1.1.3-1+b1 Versions of packages xine-ui recommends: ii xdg-utils 1.1.3-1+deb10u1 xine-ui suggests no packages. -- no debconf information Could you help here?
Bug#1033570: unblock: kdenlive/22.12.3-2
Am 15.04.2023 um 21:51 schrieb Paul Gevers: Control: tags -1 confirmed Hi Patrick, Thanks. On 14-04-2023 10:45, Patrick Matthäi wrote: You may have guessed from the silence (see also our FAQ [1]) that we're not enthusiastic about mlt. I'm currently leaning towards the tpu route for kdenlive. Please upload the version you have in unstable to testing-proposed-uploads with only an added changelog entry. I prefer a +deb12u1 version bump (because that will automatically be synced to unstable), but I can live with ~deb12u1 too if you prefer that. Paul Thank you, I have uploaded it :) PS: It works better with testing-proposed-updates instead of testing-proposed-uploads :D
Bug#1033812: Security of systemd service file should be improved
Hello Sergio, Am 02.04.2023 um 06:38 schrieb Sergio Durigan Junior: Source: znc Version: 1.8.2-3 Severity: important Hello, I noticed that ZNC's service file comes with just a few settings that improve security: --8<---cut here---start->8--- ... PrivateTmp=true ProtectSystem=full ProtectHome=no PrivateDevices=true LimitNOFILE=1024 ... --8<---cut here---end--->8--- IMHO, these settings should be improved. Here's what I recommend: 1) "ProtectHome=yes", because ZNC's $HOME is not located inside /home, so it's OK to make /home, /root and /run/user inaccessible. Thank you for testing this. ProtectHome is the only thing with a question mark for me. I think most users are using znc under a normal user inside home, because running it as a "normal" service was just added three years ago with 1.7.4-2. So people still running it with an user inside /home could get problems, if they just adopt the new service file or using documentations copying this file and using it for their own user. What do you think? -- /* Mit freundlichem Gruß / With kind regards, Patrick Matthäi GNU/Linux Debian Developer Blog: https://www.linux-dev.org/ E-Mail: pmatth...@debian.org patr...@linux-dev.org */
Bug#1033570: unblock: kdenlive/22.12.3-2
Hello Paul, Am 12.04.2023 um 21:09 schrieb Paul Gevers: Control: tags -1 moreinfo Hi Patrick On 27-03-2023 17:06, Patrick Matthäi wrote: as mentioned in my unblock #1033554 for mlt I were a bit too stupid to read the freeze policy correctly. I would like to see kdenlive 22.12.3-2 in bookworm, it just fixes some upstream bugs and two Debian bugs (missing dependencies). Can you please elaborate? It appears that this is a bug fix only release, can you confirm? What's the upstream policy for such releases? I didn't spot any upstream changelog, can you describe what the changes are supposed to achieve? Yes, normaly the minor versions just contains bugfixes. Here are the release notes: https://kdenlive.org/de/2023/03/kdenlive-22-12-3/ The debdiff is - except of the translation files - small. Might have been nice to filter them out :). Attached :) Fixing annoying upstream bugs and missing dependencies in the packaging. Any pointers to which bugs those are? * Fix subtitle scrolling. Commit. <http://commits.kde.org/kdenlive/bdbf0bf5122ae5fce7334203a7d990dd7032a129> * Fix language model combobox too small. Commit. <http://commits.kde.org/kdenlive/7432631c675d034bfbf266443cc2f7ab6774128b>Fixes bug #465787 <https://bugs.kde.org/465787> * Scroll timeline when moving a subtitle. Related to #1634. Commit. <http://commits.kde.org/kdenlive/b53e78e697793e8fff51dc5ef7cc8eb3584147df> * Fix subtitles overlap on import. Commit. <http://commits.kde.org/kdenlive/ffda87a8de2bed6812edc23cc9536a01d3d58f0c> * Fix subtitle move regression. Commit. <http://commits.kde.org/kdenlive/cbc0201a7179834dc63a517919238400bb233d5b> * Fix subtitle offset on group move. Commit. <http://commits.kde.org/kdenlive/56d4646ec9ac56b09c64a7cae39fda98848e927e> * Fix subtitles snapping. Commit. <http://commits.kde.org/kdenlive/c3cfcd9e0254b2b74a5b58d49591bbc08d4c719c> * Fix compilation. Commit. <http://commits.kde.org/kdenlive/7e2421b2aa82e2658a31291f0a769543e3cddada> * Fix crash and offset when moving a group with subtitle. Commit. <http://commits.kde.org/kdenlive/998ddfa5e0471b7dba34ebb16909931cae3d7922> [ Risks ] If mlt is not allowed to enter bookworm the "risk" would be that I would like to request a upload of this kdenlive version directly to testing? You may have guessed from the silence (see also our FAQ [1]) that we're not enthusiastic about mlt. I'm currently leaning towards the tpu route for kdenlive. Paul [1] https://release.debian.org/testing/FAQ.html Yes especially for the mlt case it is understandable for me. -- /* Mit freundlichem Gruß / With kind regards, Patrick Matthäi GNU/Linux Debian Developer Blog:https://www.linux-dev.org/ E-Mail:pmatth...@debian.org patr...@linux-dev.org */ diff -Nru kdenlive-22.12.2/debian/changelog kdenlive-22.12.3/debian/changelog --- kdenlive-22.12.2/debian/changelog 2023-02-03 09:49:23.0 +0100 +++ kdenlive-22.12.3/debian/changelog 2023-03-10 09:43:45.0 +0100 @@ -1,3 +1,19 @@ +kdenlive (22.12.3-2) unstable; urgency=medium + + * Add missing dependency on qml-module-org-kde-newstuff. +Closes: #1032470 + + -- Patrick Matthäi Fri, 10 Mar 2023 09:43:45 +0100 + +kdenlive (22.12.3-1) unstable; urgency=medium + + * New upstream release. + * Add dependency on qml-module-org-kde-kcm. + Closes: #1030782 + * Update signing-key.asc. + + -- Patrick Matthäi Tue, 07 Mar 2023 09:13:27 +0100 + kdenlive (22.12.2-1) unstable; urgency=medium * New upstream release. diff -Nru kdenlive-22.12.2/debian/control kdenlive-22.12.3/debian/control --- kdenlive-22.12.2/debian/control 2023-02-03 09:49:23.0 +0100 +++ kdenlive-22.12.3/debian/control 2023-03-10 09:43:45.0 +0100 @@ -60,6 +60,8 @@ qml-module-qtquick-dialogs, qml-module-qtquick-layouts, qml-module-qtquick-window2, + qml-module-org-kde-kcm, + qml-module-org-kde-newstuff, breeze, breeze-icon-theme (>= 4:5.83.0), kinit, diff -Nru kdenlive-22.12.2/debian/upstream/signing-key.asc kdenlive-22.12.3/debian/upstream/signing-key.asc --- kdenlive-22.12.2/debian/upstream/signing-key.asc2023-02-03 09:49:23.0 +0100 +++ kdenlive-22.12.3/debian/upstream/signing-key.asc2023-03-10 09:43:45.0 +0100 @@ -11,19 +11,147 @@ P0B3l1E4Ccw1ne2/O1BdsnXeUaI3YVYz9aZkVlL7ywda3h/goRKxc1b18bmgu/Ed QmcTEMj29B3szMpetWNt1ZbaMJzfDw+z+SiQ3toOTUiqMuWq+l+JK0dVUzOvpGhG VHv5m9CtJFP671ivEc4it0hJRH5kdW9aNbeG0g9TxHQqQMJIpeLvRq5WKwARAQAB -tCFBbGJlcnQgQXN0YWxzIENpZCA8YWFjaWRAa2RlLm9yZz6JAlQEEwEIAD4CGwMF -CwkIBwIGFQgJCgsCBBYCAwECHgECF4AWIQTKJixsg95NL7KKMyo6ak24Oeqm1wUC -Yv52/wUJDRPXIAAKCRA6ak24Oeqm1zksD/95HdsLbCMlQWImftxAY0wUNVLTvt7+ -9rjpt/unyCqdtD9uS7J6Tfldmd2zPxIJFxpDx3AK5gJGAl8hBuARBTG6mzDSyohy -0ldLAroab2zKn/hGfnAlxZtsa8DGmNhKKb8zEyKraM2grdc2bCF/sQ5yKmC0THAQ -wMBjLHoszKYV+y/R34o1nZZaufPrNWMPd3hmiyCl5vzmRDQJatmkDvueY
Bug#1033555: unblock: fraqtive/0.4.8.1-1
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Please unblock package fraqtive
This is just a short maintainance release from upstream after many
years, mainly just merged already in Debian applied patches, so that
fraqtive still builds in modern environments.
As described in my mlt unblock request I thought it will migrate after
20 days and it looks cleaner for me to have the new upstream release, why
I had done this upload for targeting bookworm
[ Reason ]
New upstream release, which just covers already applied patches.
[ Impact ]
No impact here
[ Tests ]
Tested if it still starts, manual
[ Risks ]
I do not see any risk
[ Checklist ]
[x] all changes are documented in the d/changelog
[x] I reviewed all changes and I approve them
[x] attach debdiff against the package in testing
unblock fraqtive/0.4.8.1-1
diff -Nru fraqtive-0.4.8/configure fraqtive-0.4.8.1/configure
--- fraqtive-0.4.8/configure2008-03-21 11:49:25.78354 +0100
+++ fraqtive-0.4.8.1/configure 2023-03-06 09:30:22.0 +0100
@@ -81,7 +81,7 @@
if test "$version" != "**Unknown**"; then
major=`echo $version | sed -e "s/\([0-9][0-9]*\).*/\1/"`
minor=`echo $version | sed -e "s/[0-9][0-9]*\.\([0-9][0-9]*\).*/\1/"`
-if test $major -eq 4 -a $minor -ge 3; then
+if test $major -eq 5; then
QMAKE=$i
break
fi
@@ -89,7 +89,7 @@
done
if test -z "$QMAKE"; then
-echo "*** ERROR: Cannot find 'qmake' from Qt 4.3 or newer." >&2
+echo "*** ERROR: Cannot find 'qmake' from Qt 5." >&2
exit 1
fi
diff -Nru fraqtive-0.4.8/debian/changelog fraqtive-0.4.8.1/debian/changelog
--- fraqtive-0.4.8/debian/changelog 2023-01-12 11:07:55.0 +0100
+++ fraqtive-0.4.8.1/debian/changelog 2023-03-13 12:00:59.0 +0100
@@ -1,3 +1,11 @@
+fraqtive (0.4.8.1-1) unstable; urgency=medium
+
+ * New upstream release.
+- Remove merged patch 03-use-qt5.
+- Remove merged patch 04-fix-includes.
+
+ -- Patrick Matthäi Mon, 13 Mar 2023 12:00:59 +0100
+
fraqtive (0.4.8-17) unstable; urgency=medium
* Adjust debian/watch to work again with GitHub.
diff -Nru fraqtive-0.4.8/debian/patches/03-use-qt5.diff
fraqtive-0.4.8.1/debian/patches/03-use-qt5.diff
--- fraqtive-0.4.8/debian/patches/03-use-qt5.diff 2023-01-12
11:07:55.0 +0100
+++ fraqtive-0.4.8.1/debian/patches/03-use-qt5.diff 1970-01-01
01:00:00.0 +0100
@@ -1,19 +0,0 @@
-Description: Fix build system to use Qt5 instead of Qt4
-Author: Sune Vuorela
-Forwarded: yes
-
-Origin: other
-Last-Update: 2018-08-15
-
fraqtive-0.4.8.orig/configure
-+++ fraqtive-0.4.8/configure
-@@ -81,7 +81,7 @@ for i in $paths; do
- if test "$version" != "**Unknown**"; then
- major=`echo $version | sed -e "s/\([0-9][0-9]*\).*/\1/"`
- minor=`echo $version | sed -e "s/[0-9][0-9]*\.\([0-9][0-9]*\).*/\1/"`
--if test $major -eq 4 -a $minor -ge 3; then
-+if test $major -eq 5 -a $minor -ge 3; then
- QMAKE=$i
- break
- fi
diff -Nru fraqtive-0.4.8/debian/patches/04-fix-includes.diff
fraqtive-0.4.8.1/debian/patches/04-fix-includes.diff
--- fraqtive-0.4.8/debian/patches/04-fix-includes.diff 2023-01-12
11:07:55.0 +0100
+++ fraqtive-0.4.8.1/debian/patches/04-fix-includes.diff1970-01-01
01:00:00.0 +0100
@@ -1,30 +0,0 @@
-Description: Add missing includes
- Qt5 has had a bit of includes cleanups. Apply those.
-Author: Sune Vuorela
-Forwarded: yes
-
-Origin: other
-Forwarded: no
-Last-Update: 2018-08-15
-
fraqtive-0.4.8.orig/src/configurationdata.cpp
-+++ fraqtive-0.4.8/src/configurationdata.cpp
-@@ -27,6 +27,7 @@
-
- #include
- #include
-+#include
-
- ConfigurationData::ConfigurationData()
- {
fraqtive-0.4.8.orig/src/fractalgenerator.h
-+++ fraqtive-0.4.8/src/fractalgenerator.h
-@@ -22,6 +22,7 @@
- #include
- #include
- #include
-+#include
-
- #include "abstractjobprovider.h"
- #include "datastructures.h"
diff -Nru fraqtive-0.4.8/debian/patches/series
fraqtive-0.4.8.1/debian/patches/series
--- fraqtive-0.4.8/debian/patches/series2023-01-12 11:07:55.0
+0100
+++ fraqtive-0.4.8.1/debian/patches/series 2023-03-13 12:00:59.0
+0100
@@ -1,5 +1,3 @@
01-desktop-keywords.diff
02-spelling-error.diff
-03-use-qt5.diff
-04-fix-includes.diff
05-fix-ftbfs.diff
diff -Nru fraqtive-0.4.8/.gitignore fraqtive-0.4.8.1/.gitignore
--- fraqtive-0.4.8/.gitignore 1970-01-01 01:00:00.0 +0100
+++ fraqtive-0.4.8.1/.gitignore 2023-03-06 09:30:22.0 +0100
@@ -0,0 +1,12 @@
+debug
+release
+src/fraqtive_pch.h.cpp
+src/fraqtive.vcxproj
+src/fraqtive.vcxproj.filters
+src/fraqtive.vcxproj.user
+tmp
+.qmake.stash
+config.pri
+configure-msvc.bat
+fraqtive.sln
+fraqtive.v12.suo
diff -Nru fraqtive-0.4.8/src/configurationdata.cpp
fraq
Bug#1033554: unblock: mlt/7.14.0-1
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package mlt First I am very sorry for this mess! I missunderstood the text in the time of the soft freeze and thought key packages with autopkgtests only and that non key-packages will still migrate after 20 days.. After I have done those uploads I still wanted to see in bookworm it was already too late.. My fault and also a good hint for me to indroduce autopkgtests in my packages So the problem is now, mlt 7.14 about 7.12 has some fixed bugs and improvided ffmpeg support for further releases. And now it is already in unstable.. Sorry.. I have done this update along with kdenlive (unblock for it follows), because it has a bugfix release. Which is not complicated, but if you dont see a chance to let 7.14 to bookworm I had for example to do a upload of kdenlive directly to testing? [ Reason ] Several fixed bugs. [ Impact ] It is uploaded to unstable, could be problematic for the release process (dependencies) if updates are required. [ Tests ] I have tested mlt on my system along with kdenlive. [ Risks ] It is a new upstream release, which also introduces new features, compability with ffmpeg 6.0 (which would be nice for later backports in bookworm), risk that something new could break something else. But it looks good from my view [ Checklist ] [x] all changes are documented in the d/changelog [y] I reviewed all changes and I approve them (as possible for myself with the upstream code) [x] attach debdiff against the package in testing unblock mlt/7.14.0-1 mlt.debdiff.gz Description: application/gzip
Bug#1032951: RFP: python3-pytest-executable -- pytest plugin for simplifying the black-box testing of an executable
Package: wnpp Severity: wishlist X-Debbugs-Cc: r...@sc3d.org * Package name: python3-pytest-executable Version : 0.5.4 Upstream Author : Antoine Dechaume * URL : https://pypi.org/project/pytest-executable/ https://github.com/CS-SI/pytest-executable * License : Apache Software License 2.0 Programming Lang: Python Description : pytest plugin for simplifying the black-box testing of an executable I require this new dependency for the "rpl" package in version 1.15.2.
Bug#1030764: Do not migrate to testing/bookworm
Package: vclt-tools Version: 0.1.4-9 Severity: serious Dont migrate again to testing
Bug#1030763: Do not migrate to testing/bookworm
Package: ckport Version: 0.1~rc1-11 Severity: serious Dont migrate again to testing
Bug#1030762: Do not migrate to testing/bookworm
Package: roarplaylistd Version: 0.1.9-10 Severity: serious Dont migrate again to testing
Bug#1030761: Do not migrate to testing/bookworm
Package: muroar Version: 0.1.13-8 Severity: serious Dont migrate again to testing
Bug#1030760: Do not migrate to testing/bookworm
Package: roaraudio Version: 1.0~beta12-5 Severity: serious Dont migrate again to testing
Bug#1030759: Do not migrate to testing/bookworm
Package: muroard Version: 0.1.14-9 Severity: serious Dont migrate again to testing
Bug#1030755: RM: roaraudio/1.0~beta12-5
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: rm Please remove the package from testing. I have decided that it is better to release bookworm without the whole roaraudio stuff, because of the lack of users, reverse dependencies, support and missing releases. The last reverse dependency (cmus) also removed the support now with #1030662
Bug#1030666: RM: vclt-tools/0.1.4-9
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: rm Please remove the package from testing. I have decided that it is better to release bookworm without the whole roaraudio stuff, because of the lack of users, reverse dependencies, support and missing releases.
Bug#1030665: RM: roarplaylistd/0.1.9-10
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: rm Please remove the package from testing. I have decided that it is better to release bookworm without the whole roaraudio stuff, because of the lack of users, reverse dependencies, support and missing releases.
Bug#1030664: RM: muroard/0.1.14-9
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: rm Please remove the package from testing. I have decided that it is better to release bookworm without the whole roaraudio stuff, because of the lack of users, reverse dependencies, support and missing releases.
Bug#1030663: RM: muroar/0.1.13-8
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: rm Please remove the package from testing. I have decided that it is better to release bookworm without the whole roaraudio stuff, because of the lack of users, reverse dependencies, support and missing releases.
Bug#1030662: RM: ckport/0.1~rc1-11
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: rm Please remove the package from testing. I have decided that it is better to release bookworm without the whole roaraudio stuff, because of the lack of users, reverse dependencies, support and missing releases.
Bug#1030661: cmus: Remove roaraudio dependency
Package: cmus Version: 2.10.0-2+b1 Severity: grave Tags: patch Justification: renders package unusable Hello, I am maintaining the roaraudio packages. I have decided, because of the lack of users and no new releses for years, to remove it from testing/bookworm and maybe from unstable, too. cmus is the only reverse dependency, so please remove the roaraudio support, so I could go ahead with removing the package. Patch: diff -Naur old/cmus-2.10.0/debian/control cmus-2.10.0/debian/control --- old/cmus-2.10.0/debian/control 2022-07-13 23:01:12.0 +0200 +++ cmus-2.10.0/debian/control 2023-02-06 10:17:03.431864752 +0100 @@ -25,7 +25,6 @@ libncursesw5-dev, libopusfile-dev, libpulse-dev, - libroar-dev, libsamplerate0-dev, libsystemd-dev, libvorbis-dev, diff -Naur old/cmus-2.10.0/debian/files cmus-2.10.0/debian/files --- old/cmus-2.10.0/debian/files1970-01-01 01:00:00.0 +0100 +++ cmus-2.10.0/debian/files2023-02-06 10:17:56.627639054 +0100 @@ -0,0 +1 @@ +cmus_2.10.0-2.1_source.buildinfo sound optional diff -Naur old/cmus-2.10.0/debian/rules cmus-2.10.0/debian/rules --- old/cmus-2.10.0/debian/rules2022-07-13 23:01:12.0 +0200 +++ cmus-2.10.0/debian/rules2023-02-06 10:17:31.383746159 +0100 @@ -21,7 +21,7 @@ DPKG_EXPORT_BUILDFLAGS= 1 include /usr/share/dpkg/buildflags.mk -suggested_deps = pulse roar jack +suggested_deps = pulse jack EXTRA_CMUS_DIR_OP_PLUGINS = debian/cmus/usr/lib/cmus/op/ EXTRA_CMUS_PLUGINS := $(foreach plugin,$(suggested_deps),$(plugin).so)
Bug#1026927: More analysis and improved patch
fixed #1026927 3.6-1
thanks
Am 14.01.2023 um 19:21 schrieb George Robbert:
Hey,
I think I found why you still get the error after applying the patch.
The same thing happened to me on another of my systems. The
difference was whether the package amd64-microcode was installed or
not. I think I have a patch (attached) for both. Here's what I found.
It looks like there are actually 2 related bugs here. The first one
(which my original patch for line 182 addresses) applies when there is
microcode available. The second, when there is not. Here's what I've
found:
Both of these are exposed on line 904 of /usr/sbin/needrestart
print "NEEDRESTART-UCEXP: $ucode_vars{AVAIL}\n";
when $ucode_vars{AVAIL} never gets set. There are 2 ways this can
happen. The second (which I just found), comes when AMD.pm finds an
AMD cpu, but does not find microcode for it (namely _scan_ucodes does
not find a matching file in /lib/firmware/amd-ucode/microcode_*.bin).
This will, under -v, print
"$LOGPREF #$info->{processor} no ucode updates available\n"
and return NRM_CURRENT (indicating no reboot for microcode needed),
but still leave $ucode_vars{AVAIL} unset. The fix is to make sure
that it is set even when there are no microcode updates available (on
line 176).
The first (original patch) bug comes when needrestart finds a matching
microcode. There, on line 182 of /usr/share/perl5/NeedRestart/uCode/AMD.pm
the line ends with a comma (,) instead of a semicolon (;), which means
that the assignment to $ucode_vars{AVAIL} is subsumed under the if ($debug)
condoling the printing of microcode version under. Thus,
$ucode_vars{AVAIL} is only set under needrestart -v.
The attached patch fixes both of these cases.
Thanks,
George
--- /tmp/AMD.pm 2023-01-14 09:09:28.324414456 -0700
+++ /usr/share/perl5/NeedRestart/uCode/AMD.pm 2023-01-14 09:11:39.210705528
-0700
@@ -173,13 +173,13 @@
_scan_ucodes();
}
-my %vars = ( CURRENT => sprintf( "0x%08x", $ucode ), );
+my %vars = ( CURRENT => sprintf( "0x%08x", $ucode ), AVAIL =>
"unavailable");
# check for microcode updates
if ( exists( $_ucodes->{cpuid}->{$cpuid} ) ) {
my $prid = $_ucodes->{cpuid}->{$cpuid};
if ( exists( $_ucodes->{prid}->{$prid} ) ) {
-$vars{AVAIL} = sprintf( "0x%08x", $_ucodes->{prid}->{$prid} ),
+$vars{AVAIL} = sprintf( "0x%08x", $_ucodes->{prid}->{$prid} );
print STDERR "$LOGPREF #$info->{processor} found ucode $vars{AVAIL}\n" if ($debug);
if ( $_ucodes->{prid}->{$prid} > $ucode ) {
Thanks for your new investigation, you were faster than me :)
I verified your patch, working also on my system now. I have filled
#1029147 and will upload a fixed package to stable after I have got the
approve from -release
Thanks for it!
Bug#1029147: bullseye-pu: package needrestart/3.5-4+deb11u3
Package: release.debian.org
Severity: normal
Tags: bullseye
User: release.debian@packages.debian.org
Usertags: pu
[ Reason ]
needrestart on stable reports a uninitialized perl warning on some amd64
systems when using option "-b"
[ Tests ]
Verified on my own Ryzen notebook: stable not working and patch approved
[ Checklist ]
[x ] *all* changes are documented in the d/changelog
[x ] I reviewed all changes and I approve them
[x ] attach debdiff against the package in (old)stable
[x ] the issue is verified as fixed in unstable
debdiff against current stable version:
diff -Naur tags/3.5-4+deb11u2/debian/changelog
branches/bullseye/debian/changelog
--- tags/3.5-4+deb11u2/debian/changelog 2022-05-29 09:57:10.173934775 +0200
+++ branches/bullseye/debian/changelog 2023-01-18 16:18:34.571042767 +0100
@@ -1,3 +1,11 @@
+needrestart (3.5-4+deb11u3) bullseye; urgency=medium
+
+ * Add patch 10-amd-reporting from George Robbert to fix a Perl warning on
+AMD64 systems.
+Closes: #1026927
+
+ -- Patrick Matthäi Wed, 18 Jan 2023 16:18:28 +0100
+
needrestart (3.5-4+deb11u2) bullseye; urgency=medium
* Add upstream patch 09-cgroupv2 to fix broken detection with cgroupv2.
diff -Naur tags/3.5-4+deb11u2/debian/patches/10-amd-reporting.diff
branches/bullseye/debian/patches/10-amd-reporting.diff
--- tags/3.5-4+deb11u2/debian/patches/10-amd-reporting.diff 1970-01-01
01:00:00.0 +0100
+++ branches/bullseye/debian/patches/10-amd-reporting.diff 2023-01-18
15:56:59.058848074 +0100
@@ -0,0 +1,22 @@
+# Fix Perl warning with needrestart -b on AMD64 systems.
+# Closes: #1026927
+
+diff -Naur needrestart-3.5.orig/perl/lib/NeedRestart/uCode/AMD.pm
needrestart-3.5/perl/lib/NeedRestart/uCode/AMD.pm
+--- needrestart-3.5.orig/perl/lib/NeedRestart/uCode/AMD.pm 2020-03-22
17:40:19.0 +0100
needrestart-3.5/perl/lib/NeedRestart/uCode/AMD.pm 2023-01-18
15:53:14.522822806 +0100
+@@ -173,13 +173,13 @@
+ _scan_ucodes();
+ }
+
+-my %vars = ( CURRENT => sprintf( "0x%08x", $ucode ), );
++my %vars = ( CURRENT => sprintf( "0x%08x", $ucode ), AVAIL =>
"unavailable");
+
+ # check for microcode updates
+ if ( exists( $_ucodes->{cpuid}->{$cpuid} ) ) {
+ my $prid = $_ucodes->{cpuid}->{$cpuid};
+ if ( exists( $_ucodes->{prid}->{$prid} ) ) {
+-$vars{AVAIL} = sprintf( "0x%08x", $_ucodes->{prid}->{$prid} ),
++$vars{AVAIL} = sprintf( "0x%08x", $_ucodes->{prid}->{$prid} );
+
+ print STDERR "$LOGPREF #$info->{processor} found ucode
$vars{AVAIL}\n" if ($debug);
+ if ( $_ucodes->{prid}->{$prid} > $ucode ) {
diff -Naur tags/3.5-4+deb11u2/debian/patches/series
branches/bullseye/debian/patches/series
--- tags/3.5-4+deb11u2/debian/patches/series2022-05-29 09:57:10.233934382
+0200
+++ branches/bullseye/debian/patches/series 2023-01-18 15:56:00.978841509
+0100
@@ -7,3 +7,4 @@
07-runit.diff
08-anchor-interp-re.diff
09-cgroupv2.diff
+10-amd-reporting.diff
Bug#1026927: needrestart -b on AMD processors complains of perl uninitialized variable
Hey
Am 24.12.22 um 02:25 schrieb George Robbert:
Package: needrestart
Version: 3.5-4+deb11u2
Severity: normal
Dear Maintainer,
When running 'needrestart -b' on an AMD system, I get the following
uninitialized variable warning. It also does not report the expected
microcode version (NEEDRESTART-UCEXP). See output: section below for
example output of needrestart -b.
Use of uninitialized value $ucode_vars{"AVAIL"} in concatenation (.) or string
at /usr/sbin/needrestart line 904.
This perl warning disappears when adding the -v option (needrestart -b -v),
and the correct value is reported for NEEDRESTART-UCEXP.
The processor, in this system, is:
vendor_id : AuthenticAMD
cpu family : 18
model : 1
model name : AMD A4-3400 APU with Radeon(tm) HD Graphics
stepping: 0
microcode : 0x327
It looks to me like the problem is that line 182 of
/usr/share/perl5/NeedRestart/uCode/AMD.pm ends in a comma (,) instead
of a semicolon (;). This means that assignment is subsumed into the
next line which is under if ($debug).
See the attached patch.
Thanks for your investigation. I have tested it on my (sid/unstable) AMD
notebook and I can reproduce your issue with needrestart from stable.
But your patch does not produce another result for me. Are you sure,
that you didnt changed something else?
OpenPGP_0x12D9B04A90CBD8E4.asc
Description: OpenPGP public key
OpenPGP_signature
Description: OpenPGP digital signature
Bug#1025490: fastnetmon: FTBFS with grpc 1.51+
Am 05.12.2022 um 19:34 schrieb László Böszörményi (GCS): Source: fastnetmon Version: 1.2.3-2 Severity: important Usertags: grpc1_51 Tags: ftbfs bookworm sid patch Hi, I would like to start the gRPC v1.51 transition real soon. Your package fails to build with it. I have a simple patch for you which fixes the problem. Please be prepared to apply it when time comes. Thanks, Laszlo/GCS Hey, thanks for your patch. do you know when you will start? @Pavel: is this relevant for you maybe (I think for your CI?)
Bug#1025467: glusterfs: test suite failure: xfs filesystem too small
Am 05.12.2022 um 10:53 schrieb Julian Andres Klode: In Ubuntu, the attached patch was applied to achieve the following: * debian/tests/create-volume: Bump volume size to 500MB to accomodate mkfs.xfs lower limit in xfsprogs 6.0 (+ some headroom) Thanks for considering the patch. Thanks, it is applied and will be closed with the next upload
Bug#1024703: rename binary package to znuny too
Hey Am 23.11.2022 um 14:44 schrieb Daniel Baumann: Package: znuny Version: 6.4.3-1 Hi, thank you for maintaining znuny in Debian. It would be nice if you could also rename the binary package to match the name of the otrs fork. Should you need help, let me know and I'll send a patch. Regards, Daniel Yes help would be realy nice, because it is not trivial with all those conffiles and maybe also changing the database name for new installations (if possible), without breaking upgrades
Bug#1023622: glusterfs-server: glusterfs-cli is only Recommends instead of Requires
Am 07.11.2022 um 19:38 schrieb Alex Ruddick: Package: glusterfs-server Version: 10.1-1 Severity: normal X-Debbugs-Cc: a.rudd...@numat-tech.com See https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=991383 In 9.3.2 the 'gluster' binary was moved out to a new 'gluster-cli' package. Part of the rationale given was to match Fedora. https://fedora.pkgs.org/37/fedora-updates-testing-aarch64/glusterfs-server-10.3-1.fc37.aarch64.rpm.html However, the new package is only Recommended in Debian/Ubuntu, but Required in Fedora. In default setups recommends are installed like dependencies (I also deactivate this always). This means that the server package is basically broken (in a patch release, no less!) since the 'gluster' binary is critical to actually setting up or running a server. Refer to e.g. the upstream Quick Start Guide which references 'gluster' left and right. https://docs.gluster.org/en/main/Quick-Start-Guide/Quickstart/ So why is it broken? If you also require the cli package you can simply install it. -- /* Mit freundlichem Gruß / With kind regards, Patrick Matthäi GNU/Linux Debian Developer Blog: https://www.linux-dev.org/ E-Mail: pmatth...@debian.org patr...@linux-dev.org */
Bug#1023555: fastnetmon: FTBFS with libbpf 1.0
Am 08.11.2022 um 17:55 schrieb Pavel Odintsov: Hello! Added copy to all. I think I fixed it with these commits: https://github.com/pavel-odintsov/fastnetmon/commit/c48497a6f109fc1a9f5da596b055c3b7cffb96d4 and https://github.com/pavel-odintsov/fastnetmon/commit/c718e88d0b25dcfbd724e9820f592fd5782eca6c Thank you, I have uploaded a package with both patches and it builds fine again: https://buildd.debian.org/status/package.php?p=fastnetmon I've used https://lore.kernel.org/bpf/20220202225916.3313522-7-and...@kernel.org/ and https://lxr.missinglinkelectronics.com/linux+v5.19/samples/bpf/xdp1_user.c as examples as this code was my reference during implementation. Would be great if you could review it a second time. Thank you! On Mon, 7 Nov 2022 at 11:59, Sudip Mukherjee wrote: Hi Pavel, On Mon, Nov 7, 2022 at 11:53 AM Pavel Odintsov wrote: > > Hello! > > Thank you for reaching me. > > Sure, I'll be happy to check. > > May I kindly ask what exactly changed to trigger these errors? I believe it was successfully built previously. Its the update of libbpf to v1.0.1 which removed some of the deprecated API. -- Regards Sudip -- Sincerely yours, Pavel Odintsov
Bug#1023555: fastnetmon: FTBFS with libbpf 1.0
Hey, Am 06.11.2022 um 19:32 schrieb Sudip Mukherjee: On Sun, Nov 6, 2022 at 3:51 PM Sebastian Ramacher wrote: Source: fastnetmon Version: 1.2.3-1 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) X-Debbugs-Cc: sramac...@debian.org, sudipm.mukher...@gmail.com https://buildd.debian.org/status/fetch.php?pkg=fastnetmon=amd64=1.2.3-1%2Bb1=1667748889=0 oops, sorry I missed it in my list of packages depending on libbpf. It seems "fastnetmon" added the dependency on libbpf with the last upload and I generated my list before that. :( Please let me know if you want me to help with a patch to port the code to libbpf. Yeah it is a new feature and was just added, dont worry :-) @Pavel: This is for you, if you need help maybe dont hestiate to ask Sudip (thanks for your offer!) -- /* Mit freundlichem Gruß / With kind regards, Patrick Matthäi GNU/Linux Debian Developer Blog: https://www.linux-dev.org/ E-Mail: pmatth...@debian.org patr...@linux-dev.org */
Bug#985457: geoip-database update
Am 23.09.2022 um 07:54 schrieb Marco d'Itri: Am 11.03.2021 um 00:02 schrieb Marco d'Itri: Did you consider packaging https://mailfud.org/geoip-legacy/, which is derived from the current GeoLite2 database? Can we get any feedback on this? A three years old database is more harmful than useful at this point. Are you still interested in maintaining this package? Hey, hm I think there was an issue with them why I cant use them... I will check it again, but maybe first after my vacation it is on my todo now!
Bug#703190: closed by Patrick Matthäi (Closing already long fixed bugs)
Hi, Am 15.09.2022 um 15:07 schrieb Dmitry Katsubo: On 2022-09-08 18:15, Debian Bug Tracking System wrote: Please feel free to reopen if I am wrong, but retest it with 0.99.13 Would it be not so difficult for you to push v0.99.13 to bullseye-backports? I will happily test it. Thanks! I have uploaded here an untested backport for you for the next days: https://cloud.linux-dev.org/index.php/s/jBZmioEZWRP9ebb You have to update libxine and xine-ui
Bug#1019696: devscripts: uscan does not work with github anymore
Package: devscripts Version: 2.22.2 Severity: important Hello, github made some annoying changes to the release download pages (lazy loading?) All debian/watch files using github are failing now: version=4 https://github.com/liske/needrestart/releases \ /liske/needrestart/archive/refs/tags/v(.+)\.tar\.gz $ uscan -v --debug uscan info: uscan (version 2.22.2~bpo11+1) See uscan(1) for help uscan info: Scan watch files in . uscan info: Check debian/watch and debian/changelog in . uscan info: package="needrestart" version="3.6-2" (as seen in debian/changelog) uscan info: package="needrestart" version="3.6" (no epoch/revision) uscan info: ./debian/changelog sets package="needrestart" version="3.6" uscan info: Process watch file at: debian/watch package = needrestart version = 3.6 pkg_dir = . uscan info: Last orig.tar.* tarball version (from debian/changelog): 3.6 uscan info: Last orig.tar.* tarball version (dversionmangled): 3.6 uscan info: Requesting URL: https://github.com/liske/needrestart/releases uscan info: Matching pattern: (?:(?:https://github.com)?\/liske\/needrestart\/)?/liske/needrestart/archive/refs/tags/v(.+)\.tar\.gz uscan warn: In debian/watch no matching files for watch line https://github.com/liske/needrestart/releases /liske/needrestart/archive/refs/tags/v(.+)\.tar\.gz uscan info: Scan finished -- Package-specific info: --- /etc/devscripts.conf --- Empty. --- ~/.devscripts --- export DGET_VERIFY=no -- System Information: Debian Release: 11.5 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 5.10.0-18-amd64 (SMP w/2 CPU threads) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages devscripts depends on: ii dpkg-dev 1.20.12 ii fakeroot 1.25.3-1.1 ii file 1:5.39-3 ii gnupg 2.2.27-2+deb11u2 ii gnupg22.2.27-2+deb11u2 ii gpgv 2.2.27-2+deb11u2 ii libc6 2.31-13+deb11u4 ii libfile-dirlist-perl 0.05-2 ii libfile-homedir-perl 1.006-1 ii libfile-touch-perl0.11-1 ii libfile-which-perl1.23-1 ii libipc-run-perl 20200505.0-1 ii libmoo-perl 2.004004-1 ii libwww-perl 6.52-1 ii patchutils0.4.2-1 ii perl 5.32.1-4+deb11u2 ii python3 3.9.2-3 ii sensible-utils0.0.14 ii wdiff 1.2.2-2+b1 Versions of packages devscripts recommends: ii apt 2.2.4 ii curl7.74.0-1.3+deb11u3 ii dctrl-tools 2.24-3+b1 pn debian-keyring ii dput1.1.0 ii dupload 2.9.7 pn equivs ii libdistro-info-perl 1.0 ii libdpkg-perl1.20.12 ii libencode-locale-perl 1.05-1.1 pn libgit-wrapper-perl pn libgitlab-api-v4-perl ii liblist-compare-perl0.55-1 ii liblwp-protocol-https-perl 6.10-1 pn libsoap-lite-perl ii libstring-shellquote-perl 1.04-1 ii libtry-tiny-perl0.30-1 ii liburi-perl 5.08-1 ii licensecheck3.1.1-2 ii lintian 2.115.3 ii man-db 2.9.4-2 ii patch 2.7.6-7 pn pristine-tar ii python3-apt 2.2.1 ii python3-debian 0.1.39 pn python3-magic ii python3-requests2.25.1+dfsg-2 pn python3-unidiff pn python3-xdg ii strace 5.10-1 ii unzip 6.0-26+deb11u1 ii wget1.21-1+deb11u1 ii xz-utils5.2.5-2.1~deb11u1 Versions of packages devscripts suggests: pn adequate ii at 3.1.23-1.1 pn autopkgtest pn bls-standalone ii bsd-mailx [mailx]8.1.2-0.20180807cvs-2 ii build-essential 12.9 pn check-all-the-things pn cvs-buildpackage ii debhelper13.3.4 pn diffoscope pn disorderfs pn dose-extra pn duck pn elpa-devscripts pn faketime pn gnuplot pn how-can-i-help pn libauthen-sasl-perl pn libdbd-pg-perl pn libfile-desktopentry-perl pn libnet-smtps-perl pn libterm-size-perl ii libtimedate-perl 2.3300-2 pn libyaml-syck-perl pn mmdebstrap pn mozilla-devscripts ii mutt 2.0.5-4.1+deb11u1 ii openssh-client
Bug#881514: Take over maintainance
retitle 881516 ITA: xine-ui -- the xine video player, user interface owner 881516 ! retitle 881514 ITA: xine-lib-1.2 -- xine video player library – documentation files owner 881514 ! thanks Hi, I will take over the maintainance of both packages
Bug#1011198: bullseye-pu: package needrestart/3.5-4+deb11u2
Package: release.debian.org
Severity: normal
Tags: bullseye
User: release.debian@packages.debian.org
Usertags: pu
X-Debbugs-Cc: tho...@fiasko-nw.net
Hello,
we require a small update for stable of needrestart to fix #1005953
This update already includes the security update from yesterday (3.5-4+deb11u1),
to be on the safe side I attached the full debdiff (with the approved security
update).
[ Reason ]
It is required, because the initial changes were introduced with a systemd
update
[ Impact ]
Detection of restarts does not work as excepted in every case
[ Tests ]
Manual tested by myself, patch already in unstable/testing
[ Risks ]
No risk
[ Checklist ]
[x ] *all* changes are documented in the d/changelog
[x ] I reviewed all changes and I approve them
[x ] attach debdiff against the package in (old)stable
[x ] the issue is verified as fixed in unstable
diff -Naur tags/3.5-4/debian/changelog branches/bullseye/debian/changelog
--- tags/3.5-4/debian/changelog 2021-04-12 10:08:42.636804816 +0200
+++ branches/bullseye/debian/changelog 2022-05-18 08:34:23.358456321 +0200
@@ -1,3 +1,17 @@
+needrestart (3.5-4+deb11u2) bullseye; urgency=medium
+
+ * Add upstream patch 09-cgroupv2 to fix broken detection with cgroupv2.
+Closes: #1005953
+
+ -- Patrick Matthäi Wed, 18 May 2022 08:32:47 +0200
+
+needrestart (3.5-4+deb11u1) bullseye-security; urgency=high
+
+ * Add patch 08-anchor-interp-re to fix not anchored regular expressions.
+This fixes CVE-2022-30688.
+
+ -- Patrick Matthäi Thu, 13 May 2022 10:50:07 +0200
+
needrestart (3.5-4) unstable; urgency=medium
* New source only upload.
diff -Naur tags/3.5-4/debian/patches/08-anchor-interp-re.diff
branches/bullseye/debian/patches/08-anchor-interp-re.diff
--- tags/3.5-4/debian/patches/08-anchor-interp-re.diff 1970-01-01
01:00:00.0 +0100
+++ branches/bullseye/debian/patches/08-anchor-interp-re.diff 2022-05-18
08:31:50.143457667 +0200
@@ -0,0 +1,42 @@
+# Upstream patch to fix not anchored regular expressions.
+
+diff --git a/perl/lib/NeedRestart/Interp/Perl.pm
b/perl/lib/NeedRestart/Interp/Perl.pm
+index 40aabb4..5031679 100644
+--- a/perl/lib/NeedRestart/Interp/Perl.pm
b/perl/lib/NeedRestart/Interp/Perl.pm
+@@ -43,7 +43,7 @@ sub isa {
+ my $pid = shift;
+ my $bin = shift;
+
+-return 1 if($bin =~ m@/usr/(local/)?bin/perl@);
++return 1 if($bin =~ m@^/usr/(local/)?bin/perl(5[.\d]*)?$@);
+
+ return 0;
+ }
+diff --git a/perl/lib/NeedRestart/Interp/Python.pm
b/perl/lib/NeedRestart/Interp/Python.pm
+index 559666c..a30121d 100644
+--- a/perl/lib/NeedRestart/Interp/Python.pm
b/perl/lib/NeedRestart/Interp/Python.pm
+@@ -42,7 +42,7 @@ sub isa {
+ my $pid = shift;
+ my $bin = shift;
+
+-return 1 if($bin =~ m@/usr/(local/)?bin/python@);
++return 1 if($bin =~ m@^/usr/(local/)?bin/python([23][.\d]*)?$@);
+
+ return 0;
+ }
+diff --git a/perl/lib/NeedRestart/Interp/Ruby.pm
b/perl/lib/NeedRestart/Interp/Ruby.pm
+index d02973d..72920f3 100644
+--- a/perl/lib/NeedRestart/Interp/Ruby.pm
b/perl/lib/NeedRestart/Interp/Ruby.pm
+@@ -42,7 +42,7 @@ sub isa {
+ my $pid = shift;
+ my $bin = shift;
+
+-return 1 if($bin =~ m@/usr/(local/)?bin/ruby@);
++return 1 if($bin =~ m@^/usr/(local/)?bin/ruby$@);
+
+ return 0;
+ }
+
diff -Naur tags/3.5-4/debian/patches/09-cgroupv2.diff
branches/bullseye/debian/patches/09-cgroupv2.diff
--- tags/3.5-4/debian/patches/09-cgroupv2.diff 1970-01-01 01:00:00.0
+0100
+++ branches/bullseye/debian/patches/09-cgroupv2.diff 2022-05-18
08:32:21.755251053 +0200
@@ -0,0 +1,24 @@
+From 29fcd57cd89a962bb94adbf116acd9a61036b6eb Mon Sep 17 00:00:00 2001
+From: Thomas Liske
+Date: Mon, 16 May 2022 20:00:17 +0200
+Subject: [PATCH] [Core] Make cgroup detection for services and user sessions
+ cgroup v2 aware.
+
+closes #203, closes #213
+---
+ needrestart | 2 +-
+ 1 file changed, 1 insertion(+), 1 deletion(-)
+
+diff --git a/needrestart b/needrestart
+index 6bf2e6b..bc690aa 100755
+--- a/needrestart
b/needrestart
+@@ -648,7 +648,7 @@ if(defined($opt_l)) {
+ my ($rc) = map {
+ chomp;
+ my ($id, $type, $value) = split(/:/);
+- if($type ne q(name=systemd)) {
++ if($id != 0 && $type ne q(name=systemd)) {
+ ();
+ }
+ else {
diff -Naur tags/3.5-4/debian/patches/series
branches/bullseye/debian/patches/series
--- tags/3.5-4/debian/patches/series2021-04-12 10:08:42.636804816 +0200
+++ branches/bullseye/debian/patches/series 2022-05-18 08:32:36.875152228
+0200
@@ -5,3 +5,5 @@
05-ignore-nvidia-memfd.diff
06-dont-restart-bluetooth.diff
07-runit.diff
+08-anchor-interp-re.diff
+09-cgroupv2.diff
Bug#1004860: glusterfs-client: no real dependency on fuse
Hello Andreas, Am 02.02.2022 um 15:22 schrieb Andreas Hasenack: For this to work, two conditions need to be met: a) the gluster provided /usr/bin/fusermount-glusterfs binary must be built and used (the fuse provided one is ignored) b) it must be installed SUID root, just like fuse's /usr/bin/fusermount If a privileged user is doing the mount, then gluster uses a direct mount and fusermount-glusterfs is not used. Can we then perhaps disable gluster's fusermount, and use the one provided by fuse (/usr/bin/fusermount), which is installed suid root already? No. gluster will not even attempt to use the fuse fusermount command. This then goes down to technical differences between fuse's and gluster's fusermount, some of which are explained in https://github.com/gluster/glusterfs/discussions/2212 The Debian and Ubuntu packaging, as is, do not allow unprivileged mounts, because they ship /usr/bin/fusermount-glusterfs without the SUID root bit set. It might have been a conscious decision, letting the sysadmin decide if they want to enable that bit or not, and keep it during upgrades. Or it's a bug. In any case, they way it is shipped, we could be using --disable-fusermount and would see no difference in behavior. I cant say how it was in the long long gone past, but it is not a wanted or documented behaviour nor I didn't know of that. Furthermore, I'll file one or two debian bugs to at least have the discussion started on these respective issues: a) remove fuse build-depends and Depends, since they are not needed b) either disable fusermount-glusterfs, or install it suid root, or leave it as is, but document that for it to work the admin needs to chmod u+s that binary and use dpkg-statoverride to not lose that during upgrades. What would be your favorite for b)? ``` This is the upstream bug I filed to have glusterfs use the system installed fuse: https://github.com/gluster/glusterfs/issues/3145 It would be helpful if you could double check my findings, and then maybe we could drop the fuse build-depends and depends? Unless I overlooked something. Looks fine and I think you are more in this topic than myself now :D Cheers!
Bug#1007211: libmlt++7 has circular Depends on libmlt7
Hi
Am 13.03.2022 um 17:24 schrieb Bill Allombert:
Package: libmlt++7
Version: 7.4.0-1
Severity: important
Hello Patrick,
There is a circular dependency between libmlt++7 and libmlt7:
libmlt++7 :Depends: libmlt7 (>= 7.4.0)
libmlt7 :Depends: libmlt++7 (>= 7.4.0)
Circular dependencies involving shared libraries are known to cause problems
during upgrade between stable releases, so we should try to avoid them.
Cheers,
I know this warning, but I never had problems with upgrades of the mlt
stack with this, also I dont know how to solve it, since the
dependencies are added (and required) by ${shlibs:Depends}
--
/*
Mit freundlichem Gruß / With kind regards,
Patrick Matthäi
GNU/Linux Debian Developer
Blog: https://www.linux-dev.org/
E-Mail: pmatth...@debian.org
patr...@linux-dev.org
*/
Bug#1006608: RM: aroarfw -- ROM; not used / developed / required anymore
Package: ftp.debian.org Severity: normal Hello, I have also talked with upstream about this package, please remove it from unstable (and testing if possible for you). popcon is just 2.
Bug#1003378: More data for Bug 1003378
Hi,
@JB:
Maybe you have got an idea?
Full report: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1003378
On 09.01.22 07:37, Kingsley G. Morse Jr. wrote:
I tried again.
This time, I did
$ aptitude install kde-standard
and then tried adding the same .mp4 file to
Kdenlive's project bin.
Kdenlive didn't crash this time, but it
1.) openned an orange error window that says
"Cannot open file
/home/kingsley/doc/movies/public_domain/
Twelve+Days+of+Christmas+(Instrumental)+(feat.
+Public+Domain+Royalty+Free+Music)-F-b6WYUHBWY.mp4"
and
2.) printed this on the console
=== REG FOCUS: true
qml: item not found
=== REG FOCUS: false
/// starting to add bin clips
/// found list
(QUrl("file:///home/kingsley/doc/movies/public_domain/Twelve+Days+of+Christmas+(Instrumental)+(feat.+Public+Domain+Royalty+Free+Music)-F-b6WYUHBWY.mp4"))
/// creatclipsfromlist
(QUrl("file:///home/kingsley/doc/movies/public_domain/Twelve+Days+of+Christmas+(Instrumental)+(feat.+Public+Domain+Royalty+Free+Music)-F-b6WYUHBWY.mp4"))
true "-1"
/// createClipFromFile
"/home/kingsley/doc/movies/public_domain/Twelve+Days+of+Christmas+(Instrumental)+(feat.+Public+Domain+Royalty+Free+Music)-F-b6WYUHBWY.mp4"
"-1"
=== GOT DROPPED MIME: "video/mp4"
/// final xml "\n /home/kingsley/doc/movies/public_domain/Twelve+Days+of+Christmas+(Instrumental)+(feat.+Public+Domain+Royalty+Free+Music)-F-b6WYUHBWY.mp4\n\n"
== STARTING TASK FOR: 4
/// creatclipsfromlist return false
STARTING LOAD TASK FOR:
"/home/kingsley/doc/movies/public_domain/Twelve+Days+of+Christmas+(Instrumental)+(feat.+Public+Domain+Royalty+Free+Music)-F-b6WYUHBWY.mp4"
:::
QFSFileEngine::open: No file name specified
// WARNING EMPTY CLIP HASH:
== READY FOR TASK DELETION ON: 4
= REMOVING MASTER PRODUCER; CURRENT COUNT: 0
:::
You can try to replicate it with the video at
https://invidious.snopyta.org/watch?v=F-b6WYUHBWY
Download the version...
"audio/mp4 @ 131.141k audio only"
I wonder if a bug is in
creatclipsfromlist
or
createClipFromFile
Thanks,
Kingsley
I couldnt reproduce your issue. I tried:
* My current testing state with kdenlive 21.12.0 => working
* Testing and just upgrade kdenlive to 21.12.1 => working
* Full upgrade to unstable => working
* Also with your filename full of special chars => working
"kf.service.services: KServiceTypeTrader: serviceType "ThumbCreator" not
found
/// found list
(QUrl("file:///home/me/Twelve+Days+of+Christmas+(Instrumental)+(feat.+Public+Domain+Royalty+Free+Music)-F-b6WYUHBWY.mp4"))
/// creatclipsfromlist
(QUrl("file:///home/me/Twelve+Days+of+Christmas+(Instrumental)+(feat.+Public+Domain+Royalty+Free+Music)-F-b6WYUHBWY.mp4"))
true "-1"
/// createClipFromFile
"/home/me/Twelve+Days+of+Christmas+(Instrumental)+(feat.+Public+Domain+Royalty+Free+Music)-F-b6WYUHBWY.mp4"
"-1"
=== GOT DROPPED MIME: "video/mp4"
/// final xml "\n name=\"resource\">/home/me/Twelve+Days+of+Christmas+(Instrumental)+(feat.+Public+Domain+Royalty+Free+Music)-F-b6WYUHBWY.mp4\n\n"
== STARTING TASK FOR: 2
STARTING LOAD TASK FOR:
"/home/me/Twelve+Days+of+Christmas+(Instrumental)+(feat.+Public+Domain+Royalty+Free+Music)-F-b6WYUHBWY.mp4"
:::
/// creatclipsfromlist return false
qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 3304,
resource id: 18874443, major code: 40 (TranslateCoords), minor code: 0
### ProjectClip::setproducer
### ClipController::updateProducer
### ClipController::addmasterproducer
=
READY FOR THUMB ClipType::AV "
Does it work for you again if you only downgrade kdenlive and
kdenlive-data again to 21.12.0-1?
OpenPGP_0x12D9B04A90CBD8E4.asc
Description: OpenPGP public key
OpenPGP_signature
Description: OpenPGP digital signature
Bug#1002007: [glusterfs-server] Does not include an init script
Hi, Am 20.12.2021 um 10:24 schrieb Roman Mamedov: Package: glusterfs-server Version: 9.2-1~bpo10+1 Severity: normal From package description: "This package installs init scripts and configuration files to turn GlusterFS into a fully fledged file server." But it does not actually include any init scripts: ls /etc/init.d/*gluster* ls: cannot access '/etc/init.d/*gluster*': No such file or directory Only includes systemd service files, but I do not use systemd. As far as I'm aware it was never made mandatory in Debian. As is, it is unclear how to actually start the server. Thanks for spotting this old text. I will remove the init script wording from it. But I will not support (from myself, volunters are welcome) different init systems.
Bug#993846: otrs2: CVE-2021-36096 CVE-2021-36095 CVE-2021-36094 CVE-2021-36093
CVE-2021-36095: may not be fixed with 6.1.2 CVE-2021-36093: znuny not affected / not reproduceable Am 07.09.2021 um 09:49 schrieb Neil Williams: > Package: otrs2 > Version: 6.0.36-2 > Severity: important > Tags: security upstream > > > Hi, > > The following vulnerabilities were published for otrs2. Couldn't > find any Znuny references yet. > > CVE-2021-36096[0] > Generated Support Bundles contains private S/MIME and PGP keys if > containing folder is not hidden. This issue affects: OTRS AG ((OTRS)) > Community Edition 6.0.x version 6.0.1 and later versions. OTRS AG OTRS > 7.0.x version 7.0.28 and prior versions; 8.0.x version 8.0.15 and prior > versions. > https://otrs.com/release-notes/otrs-security-advisory-2021-10/ > > CVE-2021-36095[1] > Malicious attacker is able to find out valid user logins by using the > "lost password" feature. This issue affects: OTRS AG ((OTRS)) Community > Edition version 6.0.1 and later versions. OTRS AG OTRS 7.0.x version > 7.0.28 and prior versions. > https://otrs.com/release-notes/otrs-security-advisory-2021-18/ > > CVE-2021-36094[2] > It's possible to craft a request for appointment edit screen, which > could lead to the XSS attack. This issue affects: OTRS AG ((OTRS)) > Community Edition 6.0.x version 6.0.1 and later versions. OTRS AG OTRS > 7.0.x version 7.0.28 and prior versions. > https://otrs.com/release-notes/otrs-security-advisory-2021-17/ > > CVE-2021-36093[3] > It's possible to create an email which can be stuck while being > processed by PostMaster filters, causing DoS. This issue affects: OTRS > AG ((OTRS)) Community Edition 6.0.x version 6.0.1 and later versions. > OTRS AG OTRS 7.0.x version 7.0.28 and prior versions; 8.0.x version > 8.0.15 and prior versions. > https://otrs.com/release-notes/otrs-security-advisory-2021-16/ > > [0] https://security-tracker.debian.org/tracker/CVE-2021-36096 > https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-36096 > > [1] https://security-tracker.debian.org/tracker/CVE-2021-36095 > https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-36095 > > [2] https://security-tracker.debian.org/tracker/CVE-2021-36094 > https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-36094 > > [3] https://security-tracker.debian.org/tracker/CVE-2021-36093 > https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-36093 > > > -- System Information: > Debian Release: 10.10 > APT prefers oldstable-updates > APT policy: (500, 'oldstable-updates'), (500, 'oldstable') > Architecture: amd64 (x86_64) > > Kernel: Linux 4.19.0-17-amd64 (SMP w/4 CPU cores) > Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), > LANGUAGE=en_GB:en (charmap=UTF-8) > Shell: /bin/sh linked to /usr/bin/dash > Init: systemd (via /run/systemd/system) > LSM: AppArmor: enabled -- /* Mit freundlichem Gruß / With kind regards, Patrick Matthäi GNU/Linux Debian Developer Blog: https://www.linux-dev.org/ E-Mail: pmatth...@debian.org patr...@linux-dev.org */
Bug#994407: Binaries with same name
Whops, fix is uploaded! Am 10.10.2021 um 23:27 schrieb Thomas Liske: > Hi, > > @Patrick > > this looks like a regression of #752114, doesn't it? > > > Regards, > Thomas > > > On Wed, 2021-09-15 at 18:22 +0200, ThePPK wrote: >> Package: needrestart >> Version: 3.5-4 >> >> Needrestart while run once of scripts on >> /etc/needrestart/hook.d/30-pacman, execute pacman binary (which is >> Arch >> Linux package manager). In Debian we have a game with this same >> executable file name, 'pacman' and needrestart create process of >> pacman >> what run game window. >> It's possible to force change name of pacman game or block running >> script while pacman (package manager) isn't installed in /sbin/, >> /bin/, >> /usr/bin/ or /usr/sbin/? >>
Bug#995906: gitlab: Upgrading buster to bullseye needs some more gitlab-apt-pin-preferences adjustments
Package: gitlab Version: 14.1.7+ds1-2~fto11+1 Severity: important Hi, I am just upgrading our buster gitlab (13.12.8+ds1-1~fto10+1) to bullseye (14.1.7+ds1-2~fto11+1) along with the whole system. On upgrading I get some errors like: Could not find gem 'bootsnap (~> 1.4)' in any of the gem sources listed in your Gemfile. dpkg: Fehler beim Bearbeiten des Paketes gitlab (--configure): »installiertes gitlab-Skript des Paketes post-installation«-Unterprozess gab den Fehlerwert 1 zurück gitaly (14.1.7+dfsg-1~fto11+1) wird eingerichtet ... Could not find gem 'rbtrace' in any of the gem sources listed in your Gemfile. or: gitaly (14.1.7+dfsg-1~fto11+1) wird eingerichtet ... Resolving dependencies... Bundler could not find compatible versions for gem "ffi": In Gemfile: rbtrace was resolved to 0.4.11, which depends on ffi (>= 1.0.6) x86_64-linux Could not find gem 'ffi (>= 1.0.6)', which is required by gem 'rbtrace', in any of the sources. dpkg: Fehler beim Bearbeiten des Paketes gitaly (--configure): To solve it after the failed dist-upgrade I had to install the following versions: apt install ruby-bootsnap=1.4.6-1+b2 ruby-rbtrace=0.4.11-3+b3 ruby-ffi=1.12.2+dfsg-2+b3 ruby-character-set/bullseye ruby-concurrent/bullseye ruby-concurrent-ext/bullseye ruby-enumerable-statistics/bullseye ruby-gpgme/bullseye ruby-grape-path-helpers=1.6.3-1~bpo11+1 ruby-hitimes/bullseye ruby-js-regex/bullseye ruby-json/bullseye ruby-murmurhash3/bullseye ruby-pg/bullseye ruby-prof/bullseye ruby-re2/bullseye ruby-redcloth/bullseye ruby-rinku/bullseye ruby-stackprof/bullseye ruby-unf-ext/bullseye ruby-yajl/bullseye unicorn/bullseye The main problem is, that most packages are not upgraded from the fto10 version to the bullseye one, because the fto10 version was "higher". Thanks for your great work :-) -- System Information: Debian Release: 11.0 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 5.10.0-8-amd64 (SMP w/2 CPU threads) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
Bug#994481: kdenlive: Kdenlive cannot find your MLT profiles
You need kdenlive 21.08 from unstable (not migrated yet). does it work for you? Am 16.09.2021 um 15:03 schrieb Bob Wong: > Package: kdenlive > Version: 21.04.3-3 > Severity: important > > Dear Maintainer, > > After upgrading the MLT to the version 7, the kdenlive cannot find > the MLT profiles. However, if I manually set the path, I cannot add > the video clip into the project. > > > -- System Information: > Debian Release: bookworm/sid > APT prefers testing-proposed-updates > APT policy: (500, 'testing-proposed-updates'), (500, 'testing') > Architecture: amd64 (x86_64) > Foreign Architectures: i386 > > Kernel: Linux 5.10.0-8-amd64 (SMP w/4 CPU threads) > Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, > TAINT_UNSIGNED_MODULE > Locale: LANG=zh_CN.UTF-8, LC_CTYPE=zh_CN.UTF-8 (charmap=UTF-8), > LANGUAGE=zh_CN:zh > Shell: /bin/sh linked to /usr/bin/dash > Init: systemd (via /run/systemd/system) > LSM: AppArmor: enabled > > Versions of packages kdenlive depends on: > ii breeze 4:5.21.5-2 > ii breeze-icon-theme 4:5.85.0-2 > ii ffmpeg 7:4.4-5 > ii gstreamer1.0-plugins-bad 1.18.4-3 > ii kded5 5.85.0-2 > ii kdenlive-data 21.04.3-3 > ii kinit 5.83.0-2 > ii kio 5.83.0-2 > ii libc6 2.31-17 > ii libkf5archive5 5.85.0-2 > ii libkf5bookmarks5 5.85.0-2 > ii libkf5completion5 5.85.0-2 > ii libkf5configcore5 5.85.0-2 > ii libkf5configgui5 5.85.0-2 > ii libkf5configwidgets5 5.85.0-2 > ii libkf5coreaddons5 5.85.0-2 > ii libkf5crash5 5.85.0-2 > ii libkf5dbusaddons5 5.85.0-2 > ii libkf5declarative5 5.83.0-2 > ii libkf5filemetadata3 5.85.0-2 > ii libkf5guiaddons5 5.85.0-2 > ii libkf5i18n5 5.85.0-2 > ii libkf5iconthemes5 5.85.0-2 > ii libkf5itemviews5 5.85.0-2 > ii libkf5jobwidgets5 5.85.0-2 > ii libkf5kiocore5 5.83.0-2 > ii libkf5kiofilewidgets5 5.83.0-2 > ii libkf5kiogui5 5.83.0-2 > ii libkf5kiowidgets5 5.83.0-2 > ii libkf5newstuff5 5.83.0-2 > ii libkf5notifications5 5.85.0-3 > ii libkf5notifyconfig5 5.83.0-2 > ii libkf5purpose-bin 5.83.0-2 > ii libkf5purpose5 5.83.0-2 > ii libkf5service-bin 5.85.0-2 > ii libkf5service5 5.85.0-2 > ii libkf5solid5 5.85.0-2 > ii libkf5textwidgets5 5.85.0-2 > ii libkf5widgetsaddons5 5.85.0-2 > ii libkf5xmlgui5 5.85.0-3 > ii libmlt++3 6.26.1-1 > ii libmlt6 6.26.1-1 > ii libqt5concurrent5 5.15.2+dfsg-10 > ii libqt5core5a 5.15.2+dfsg-10 > ii libqt5dbus5 5.15.2+dfsg-10 > ii libqt5gui5 5.15.2+dfsg-10 > ii libqt5multimedia5 5.15.2-3 > ii libqt5network5 5.15.2+dfsg-10 > ii libqt5networkauth5 5.15.2-2 > ii libqt5qml5 5.15.2+dfsg-8 > ii libqt5quick5 5.15.2+dfsg-8 > ii libqt5quickcontrols2-5 5.15.2+dfsg-4 > ii libqt5quickwidgets5 5.15.2+dfsg-8 > ii libqt5svg5 5.15.2-3 > ii libqt5widgets5 5.15.2+dfsg-10 > ii libqt5xml5 5.15.2+dfsg-10 > ii libstdc++6 11.2.0-4 > ii melt 7.0.1-3 > ii qml-module-qtgraphicaleffects 5.15.2-2 > ii qml-module-qtqml-models2 5.15.2+dfsg-8 > ii qml-module-qtquick-controls 5.15.2-2 > ii qml-module-qtquick-controls2 5.15.2+dfsg-4 > ii qml-module-qtquick-dialogs 5.15.2-2 > ii qml-module-qtquick-layouts 5.15.2+dfsg-8 > ii qml-module-qtquick-window2 5.15.2+dfsg-8 > ii qml-module-qtquick2 5.15.2+dfsg-8 > > Versions of packages kdenlive recommends: > ii dvdauthor 0.7.2-1+b3 > ii dvgrab 3.5+git20160707.1.e46042e-1+b1 > ii frei0r-plugins 1.7.0-1 > ii genisoimage 9:1.1.11-3.2 > ii oxygen-icon-theme 5:5.85.0-2 > ii recordmydesktop 0.4.0-1+b1 > ii swh-plugins 0.4.17-2 > > Versions of packages kdenlive suggests: > ii khelpcenter 4:21.08.0-1 > ii vlc 3.0.16-1+b3 -- /* Mit freundlichem Gruß / With kind regards, Patrick Matthäi GNU/Linux Debian Developer Blog: https://www.linux-dev.org/ E-Mail: pmatth...@debian.org patr...@linux-dev.org */
Bug#993569: RFP: libtext-diff-formattedhtml-perl -- Generate a colorful HTML diff of strings/files
Package: wnpp Severity: wishlist X-Debbugs-Cc: pkg-perl-maintain...@lists.alioth.debian.org * Package name: libtext-diff-formattedhtml-perl Version : 0.08 Upstream Author : Alberto Simoes, * URL : https://metacpan.org/pod/Text::Diff::FormattedHTML * License : GPL Programming Lang: Perl Description : Generate a colorful HTML diff of strings/files Presents in a nice HTML table the difference between two files or strings. Inspired on GitHub diff view. I require this package as a new dependency in otrs2/znuny version 6.1.1. @pkg-perl maintainers: I would be happy if you would package and maintain it, thanks for your always nice job :)
Bug#985638: kdenlive: speed effect from right click does not change video speed
Hi Am 21.03.21 um 07:41 schrieb will: Package: kdenlive Version: 20.12.3-1 Severity: normal X-Debbugs-Cc: wiiliamchung...@gmail.com Dear Maintainer, Changing the video speed in the timeline via right click menu does not change the video speed, despite changing the corresponding time length. Playing back the "slowed" or "sped up" video will only display the default video speed, but cropped. This happens on both 20.12.2-1, and 20.12.3-1 Could you please retest this with version 21.04.3-3 from unstable and 21.08.0-1 from experimental and give a feedback? Thanks OpenPGP_0x12D9B04A90CBD8E4.asc Description: OpenPGP public key OpenPGP_signature Description: OpenPGP digital signature
Bug#992336: RM: kdenlive [armel mips64el ppc64el s390x] -- ANAIS; Package requires qtwebengine5-dev, not available on every architecture
Package: ftp.debian.org Severity: normal Hi, with kdenlive >= 21.04 qtwebengine5 is required, which is missing on armel mips64el ppc64el s390x. Could you please remove kdenlive in testing/unstable from these four architectures, so it also could migrate to testing again?
Bug#991915: unblock: otrs2/6.0.32-6
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package otrs2 It fixes three open CVEs, I hope you can still include it for bullseye changelog |8 patches/16-CVE-2021-36091.diff | 31 +++ patches/17-CVE-2021-21440.diff | 56 patches/18-CVE-2021-21443.diff | 24 patches/series |3 +++ 5 files changed, 122 insertions(+) unblock otrs2/6.0.32-6 -- System Information: Debian Release: 10.10 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'proposed-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-17-amd64 (SMP w/2 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled otrs2.diff.gz Description: application/gzip
Bug#990037: Acknowledgement (unblock: kid3/3.8.5-2)
retitle 990037 unblock: kid3/3.8.5-3
thanks
Am 18.06.21 um 16:15 schrieb Debian Bug Tracking System:
Thank you for filing a new Bug report with Debian.
You can follow progress on this Bug here: 990037:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=990037.
Hi,
sorry pls unblock 3.8.5-3. I have added a missing breaks / replaces for
safety (apt and apt-get do not complain, hmkay):
diff -Naur 3.8.5-2/debian/changelog 3.8.5-3/debian/changelog
--- 3.8.5-2/debian/changelog 2021-06-18 15:59:46.355258057 +0200
+++ 3.8.5-3/debian/changelog 2021-06-19 13:17:55.952281139 +0200
@@ -1,3 +1,9 @@
+kid3 (3.8.5-3) unstable; urgency=medium
+
+ * Add missing breaks and replaces from the last upload.
+
+ -- Patrick Matthäi Sat, 19 Jun 2021 13:17:06 +0200
+
kid3 (3.8.5-2) unstable; urgency=medium
* Cleanup manpage installing. The old method is obsolet and buggy. All
diff -Naur 3.8.5-2/debian/control 3.8.5-3/debian/control
--- 3.8.5-2/debian/control 2021-06-18 15:59:46.351258076 +0200
+++ 3.8.5-3/debian/control 2021-06-19 13:17:56.008280861 +0200
@@ -32,8 +32,12 @@
Architecture: any
Depends: ${shlibs:Depends},
${misc:Depends}
-Breaks: kid3 (<< 3.0.2-2)
-Replaces: kid3 (<< 3.0.2-2)
+Breaks: kid3 (<< 3.8.5-2),
+ kid3-cli (<< 3.8.5-2),
+ kid3-qt (<< 3.8.5-2)
+Replaces: kid3 (<< 3.8.5-2),
+ kid3-cli (<< 3.8.5-2),
+ kid3-qt (<< 3.8.5-2)
Description: Audio tag editor core libraries and data
With Kid3, an ID3 tag editor for KDE you can:
* Edit ID3v1.1 tags in your MP3 files
Bug#990037: unblock: kid3/3.8.5-2
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package kid3. It fixes the fucked-up manpages about the whole packaging and simplifies it by just installing all manpage stuff to the kid3-core package. The old behaviour was required in the past, but it is obsolete and simplified by upstream since a longer time, but it wasn't adopted to the packaging. diff -Naur 3.8.5-1/debian/changelog 3.8.5-2/debian/changelog --- 3.8.5-1/debian/changelog2021-02-01 11:45:07.735498453 +0100 +++ 3.8.5-2/debian/changelog2021-06-18 15:59:46.355258057 +0200 @@ -1,3 +1,11 @@ +kid3 (3.8.5-2) unstable; urgency=medium + + * Cleanup manpage installing. The old method is obsolet and buggy. All +manpages are now installed to the kid3-core package. +Closes: #990018 + + -- Patrick Matthäi Fri, 18 Jun 2021 15:56:17 +0200 + kid3 (3.8.5-1) unstable; urgency=medium * New upstream release. diff -Naur 3.8.5-1/debian/kid3-cli.install 3.8.5-2/debian/kid3-cli.install --- 3.8.5-1/debian/kid3-cli.install 2021-02-01 11:45:07.835497918 +0100 +++ 3.8.5-2/debian/kid3-cli.install 2021-06-18 15:59:46.351258076 +0200 @@ -1 +1 @@ -/usr/bin/kid3-cli +usr/bin/kid3-cli diff -Naur 3.8.5-1/debian/kid3-cli.manpages 3.8.5-2/debian/kid3-cli.manpages --- 3.8.5-1/debian/kid3-cli.manpages2021-02-01 11:45:07.771498261 +0100 +++ 3.8.5-2/debian/kid3-cli.manpages1970-01-01 01:00:00.0 +0100 @@ -1,2 +0,0 @@ -deb/kid3-cli.1 -deb/kid3-cli.de.1 diff -Naur 3.8.5-1/debian/kid3-core.install 3.8.5-2/debian/kid3-core.install --- 3.8.5-1/debian/kid3-core.install2021-02-01 11:45:07.735498453 +0100 +++ 3.8.5-2/debian/kid3-core.install2021-06-18 15:59:46.355258057 +0200 @@ -1,4 +1,10 @@ -/usr/lib/kid3/* -/usr/share/dbus-1/interfaces/org.kde.Kid3.xml -/usr/share/kid3/translations/* -/usr/share/kid3/qml/script/* +usr/lib/kid3/* +usr/share/dbus-1/interfaces/org.kde.Kid3.xml +usr/share/kid3/translations/* +usr/share/kid3/qml/script/* +usr/share/man/*/man1/kid3-cli.1.gz +usr/share/man/*/man1/kid3-qt.1.gz +usr/share/man/*/man1/kid3.1.gz +usr/share/man/man1/kid3-cli.1.gz +usr/share/man/man1/kid3-qt.1.gz +usr/share/man/man1/kid3.1.gz diff -Naur 3.8.5-1/debian/kid3.install 3.8.5-2/debian/kid3.install --- 3.8.5-1/debian/kid3.install 2021-02-01 11:45:07.791498153 +0100 +++ 3.8.5-2/debian/kid3.install 2021-06-18 15:59:46.287258395 +0200 @@ -1,6 +1,6 @@ -/usr/bin/kid3 -/usr/share/icons/hicolor/*/apps/kid3.* -/usr/share/applications/org.kde.kid3.desktop -/usr/share/metainfo/org.kde.kid3.appdata.xml -/usr/share/doc/HTML/*/kid3/* -/usr/share/kxmlgui5/kid3/kid3ui.rc +usr/bin/kid3 +usr/share/icons/hicolor/*/apps/kid3.* +usr/share/applications/org.kde.kid3.desktop +usr/share/metainfo/org.kde.kid3.appdata.xml +usr/share/doc/HTML/*/kid3/* +usr/share/kxmlgui5/kid3/kid3ui.rc diff -Naur 3.8.5-1/debian/kid3.manpages 3.8.5-2/debian/kid3.manpages --- 3.8.5-1/debian/kid3.manpages2021-02-01 11:45:07.719498539 +0100 +++ 3.8.5-2/debian/kid3.manpages1970-01-01 01:00:00.0 +0100 @@ -1,2 +0,0 @@ -deb/kid3.1 -deb/kid3.de.1 diff -Naur 3.8.5-1/debian/kid3-qt.install 3.8.5-2/debian/kid3-qt.install --- 3.8.5-1/debian/kid3-qt.install 2021-02-01 11:45:07.947497319 +0100 +++ 3.8.5-2/debian/kid3-qt.install 2021-06-18 15:59:46.351258076 +0200 @@ -1,5 +1,5 @@ -/usr/bin/kid3-qt -/usr/share/doc/kid3-qt/* -/usr/share/applications/org.kde.kid3-qt.desktop -/usr/share/metainfo/org.kde.kid3-qt.appdata.xml -/usr/share/icons/hicolor/*/apps/kid3-qt.* +usr/bin/kid3-qt +usr/share/doc/kid3-qt/* +usr/share/applications/org.kde.kid3-qt.desktop +usr/share/metainfo/org.kde.kid3-qt.appdata.xml +usr/share/icons/hicolor/*/apps/kid3-qt.* diff -Naur 3.8.5-1/debian/kid3-qt.manpages 3.8.5-2/debian/kid3-qt.manpages --- 3.8.5-1/debian/kid3-qt.manpages 2021-02-01 11:45:07.855497812 +0100 +++ 3.8.5-2/debian/kid3-qt.manpages 1970-01-01 01:00:00.0 +0100 @@ -1,2 +0,0 @@ -deb/kid3-qt.1 -deb/kid3-qt.de.1 diff -Naur 3.8.5-1/debian/not-installed 3.8.5-2/debian/not-installed --- 3.8.5-1/debian/not-installed2021-02-01 11:45:07.927497426 +0100 +++ 3.8.5-2/debian/not-installed1970-01-01 01:00:00.0 +0100 @@ -1,24 +0,0 @@ -usr/share/man/pt/man1/kid3-cli.1.gz -usr/share/man/pt/man1/kid3.1.gz -usr/share/man/pt/man1/kid3-qt.1.gz -usr/share/man/man1/kid3-cli.1.gz -usr/share/man/man1/kid3.1.gz -usr/share/man/man1/kid3-qt.1.gz -usr/share/man/ca/man1/kid3-cli.1.gz -usr/share/man/ca/man1/kid3.1.gz -usr/share/man/ca/man1/kid3-qt.1.gz -usr/share/man/nl/man1/kid3-cli.1.gz -usr/share/man/nl/man1/kid3.1.gz -usr/share/man/nl/man1/kid3-qt.1.gz -usr/share/man/it/man1/kid3-cli.1.gz -usr/share/man/it/man1/kid3.1.gz -usr/share/man/it/man1/kid3-qt.1.gz -usr/share/man/sv/man1/kid3-cli.1.gz -usr/share/man/sv/man1/kid3.1.gz -usr/share/man/sv/man1/kid3-qt.1.gz -usr/share/man/de/man1/kid3-cli.1.gz -usr/share/man/de/man1/kid3.1.gz -usr/share/man/de/man1/kid3-qt.1.gz -usr/share/man/uk/man1
Bug#990030: unblock: otrs2/6.0.32-5
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package otrs2 It fixes two security issues with the upstream patches. changelog | 15 ++ patches/14-ZSA-2021-03.diff | 100 patches/15-ZSA-2021-06.diff | 92 patches/series |2 4 files changed, 209 insertions(+) Full diff attached. Thanks :) unblock otrs2/6.0.32-5 -- System Information: Debian Release: 10.10 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'proposed-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-16-amd64 (SMP w/2 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled otrs.diff.gz Description: application/gzip
Bug#989227: Still some porblems
Am 10.06.2021 um 08:08 schrieb Bob Wong: > I am under the testing branch, but even after a dist-upgrade, I still > don't find the feature motion tracker. By the way, when can you > release version 21.04? I'm glad to use some more features. The fix comes after the bullseye release. We are in freeze so no new feature releases. But I intent to backport this to bullseye -- /* Mit freundlichem Gruß / With kind regards, Patrick Matthäi GNU/Linux Debian Developer Blog: https://www.linux-dev.org/ E-Mail: pmatth...@debian.org patr...@linux-dev.org */
Bug#989376: unblock: glusterfs/9.2-1
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package glusterfs Hi, sadly I need again an unblock of an upstream release. It is again a bugfix only release (also one important [0] bug introduced with 9.1, sic...). The upstream changelog could be found here [1]. The filtered diffstat: $ diff -Naur glusterfs-9.1/ glusterfs-9.2/ -x tests -x .pc -x ChangeLog -x VERSION -x glusterfs.spec |diffstat api/src/glfs-fops.c |3 cli/src/cli-rpc-ops.c |6 configure | 20 - contrib/umountd/Makefile |8 debian/changelog |6 extras/group-distributed-virt |1 extras/group-gluster-block|1 extras/group-virt.example |1 rpc/rpc-lib/src/protocol-common.h |3 xlators/cluster/afr/src/afr-dir-read.c| 11 xlators/cluster/afr/src/afr-inode-read.c | 254 +- xlators/features/index/src/index.c| 79 +- xlators/features/locks/src/posix.c| 25 +- xlators/mgmt/glusterd/src/glusterd-mgmt-handler.c |6 xlators/mgmt/glusterd/src/glusterd-store.c| 12 + xlators/mount/fuse/src/fuse-bridge.c |3 xlators/mount/fuse/src/fuse-bridge.h | 21 + xlators/protocol/client/src/client-helpers.c | 10 xlators/protocol/client/src/client-lk.c | 85 --- xlators/protocol/client/src/client.h |8 xlators/storage/posix/src/posix-inode-fd-ops.c| 10 21 files changed, 337 insertions(+), 236 deletions(-) I have attached the full diff. [0]: https://github.com/gluster/glusterfs/issues/2351 [1]: https://docs.gluster.org/en/latest/release-notes/9.2/ unblock glusterfs/9.2-1 -- System Information: Debian Release: 10.9 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'proposed-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-16-amd64 (SMP w/2 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled glusterfs92.diff.gz Description: application/gzip
Bug#989227: kdenlive: feature missing "motion tracker"
reassign 989227 src:mlt tag 989227 + pending thanks Am 29.05.21 um 16:53 schrieb ybx332: Package: kdenlive Version: 20.12.3-1 Severity: normal X-Debbugs-Cc: ybx...@gmail.com Dear Maintainer, The upstream released the motion tracker function since version 20.08. But now even under 20.12.3, I still can't find the function motion tracker. Hi, this is because mlt is not build with the opencv module. At the point, where I tested it, there wasnt the correct version available in the Debian repo. It looks now much better. I comitted a fix, but this is for bullseye+1 OpenPGP_0x12D9B04A90CBD8E4.asc Description: OpenPGP public key OpenPGP_signature Description: OpenPGP digital signature
Bug#810584: needrestart: add an as-installed DEP-8 test suite
tag 810584 + pending thanks Hi Lukasz, thanks for your patch! I have comitted it and will see after the next upload, if it may require some adjustments for other arches. Am 10.05.2021 um 16:03 schrieb Lukasz Zemczak: > Tags: patch > > Hello! > > In Ubuntu we have created a very very simple sanity testing > autopkgtest (in version 3.5-2ubuntu2) for needrestart, checking for > very basic functionality as we wanted to have at least a quick smoke > test to identify any obvious breakages. It creates a dummy service > file, causes an artificial refresh of a dependent library, runs > needrestart in batch mode, checks if it succeeds, checks if the dummy > service is marked for restart and - if possible - checks if the kernel > checks are performed. > > Forwarding it here in case it's of any use! And I'd love to get rid of > the delta in Ubuntu - either by getting this accepted, or having > someone prepare something much better! > > Thank you! > > On Sun, 10 Jan 2016 12:51:58 +0800 Paul Wise wrote: >> Package: needrestart >> Severity: wishlist >> >> It would be nice for needrestart to have a test suite that could verify >> that it is working. At the moment it appears to produce different >> results to checkrestart so I'm worried it isn't working, but I don't >> have time to write a proper bug report about this. A DEP-8 test would >> mean that users don't have to file bugs as the CI system would >> automatically and continuously test the package. >> >> http://dep.debian.net/deps/dep8/ >> https://ci.debian.net/ >> >> -- >> bye, >> pabs >> >> https://wiki.debian.org/PaulWise >> >> -- /* Mit freundlichem Gruß / With kind regards, Patrick Matthäi GNU/Linux Debian Developer Blog: https://www.linux-dev.org/ E-Mail: pmatth...@debian.org patr...@linux-dev.org */
Bug#988708: unblock: otrs2/6.0.32-4
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package otrs2 It fixes the debian/watch location on github, fixed symlinks to the dejavu fonts (#985751) and adds an upstream patch 13-CVE-2021-21252 to fix a small security issue in an embedded JS lib (#980891). changelog | 16 + otrs2.links| 17 - patches/13-CVE-2021-21252.diff | 583 + patches/series |1 watch |2 5 files changed, 609 insertions(+), 10 deletions(-) unblock otrs2/6.0.32-4 -- System Information: Debian Release: 10.9 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'proposed-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-16-amd64 (SMP w/2 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled otrs2.diff.gz Description: application/gzip
Bug#987988: unblock: glusterfs/9.1-2
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package glusterfs. It is a new upstream release, which has to be included in bullseye, because it fixes some high severity bugs. I have filtered the attached full diff with: diff -Naur glusterfs-9.0/ glusterfs-9.1/ -x ChangeLog -x VERSION -x glusterfs.spec* -x tests* The changelog for all applied changes and commits can be found here: https://docs.gluster.org/en/latest/release-notes/9.1/#issues-addressed-in-this-release You can "ignore" the biggest line change in the configure scripts, it addresses https://github.com/gluster/glusterfs/issues/2063 Normaly I forget to add the new dependency liburing-dev with 9.0-1, because of this bug. But to keep the functionality of the current testing state (liburing-dev is deactivated) I pass now for bullseye --disable-linux-io_uring in debian/rules. cli/src/cli-cmd-parser.c |3 configure| 88 +++--- configure.ac | 20 +- contrib/umountd/Makefile |8 debian/changelog | 14 + debian/rules |2 extras/hook-scripts/set/post/S32gluster_enable_shared_storage.sh |2 libglusterfs/src/glusterfs/syscall.h |3 libglusterfs/src/libglusterfs.sym|1 libglusterfs/src/syscall.c |6 xlators/cluster/afr/src/afr-common.c |3 xlators/cluster/afr/src/afr-inode-write.c| 40 ++-- xlators/cluster/afr/src/afr-self-heal-data.c |6 xlators/cluster/afr/src/afr-transaction.c|2 xlators/cluster/afr/src/afr.c|8 xlators/cluster/afr/src/afr.h|2 xlators/cluster/dht/src/dht-common.c |8 xlators/cluster/ec/src/ec.c |2 xlators/features/locks/src/posix.c |1 xlators/storage/posix/src/posix-inode-fd-ops.c | 14 + 20 files changed, 127 insertions(+), 106 deletions(-) unblock glusterfs/9.1-2 -- System Information: Debian Release: 10.9 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'proposed-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-16-amd64 (SMP w/2 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled glusterfs.diff.gz Description: application/gzip
Bug#987987: unblock: needrestart/3.5-4
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Please unblock package needrestart
It adds some upstream patches to fix some small bugs:
$ diff -Naur 3.5-2/ 3.5-4/ |diffstat
changelog | 24
patches/02-ruby-relative-path.diff | 19
patches/03-fix-wrong-default-comment.diff | 21 ++
patches/04-verbose-and-verbosity-confusion.diff | 19
patches/05-ignore-nvidia-memfd.diff | 20 +
patches/06-dont-restart-bluetooth.diff | 25
patches/07-runit.diff | 36
patches/series |6
watch |2 -
9 files changed, 171 insertions(+), 1 deletion(-)
I have attached the full diff.
unblock needrestart/3.5-4
-- System Information:
Debian Release: 10.9
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'proposed-updates'), (500,
'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 4.19.0-16-amd64 (SMP w/2 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8),
LANGUAGE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
diff -Naur 3.5-2/debian/changelog 3.5-4/debian/changelog
--- 3.5-2/debian/changelog 2020-11-19 15:10:20.971201274 +0100
+++ 3.5-4/debian/changelog 2021-04-12 10:08:42.636804816 +0200
@@ -1,3 +1,27 @@
+needrestart (3.5-4) unstable; urgency=medium
+
+ * New source only upload.
+
+ -- Patrick Matthäi Mon, 12 Apr 2021 10:04:21 +0200
+
+needrestart (3.5-3) unstable; urgency=medium
+
+ * debian/watch: Adjust github URL.
+ * Add stable upstream patch 02-ruby-relative-path to fix detection for ruby
+script started from relative paths.
+ * Add stable upstream patch 03-fix-wrong-default-comment to fix comment for
+default value of skip_mapfiles.
+ * Add stable upstream patch 04-verbose-and-verbosity-confusion to fix
+verbose/verbosity confusion in needrestart.conf.
+ * Add stable upstream patch 05-ignore-nvidia-memfd to ignore memfd used by
+nvidia binary drivers.
+ * Add stable upstream patch 06-dont-restart-bluetooth to ignore restarting
+bluetooth by default.
+ * Add stable upstream patch 07-runit to add support for runit.
+Closes: #972685
+
+ -- Patrick Matthäi Fri, 09 Apr 2021 11:17:52 +0200
+
needrestart (3.5-2) unstable; urgency=medium
* Adjust lintian overrides.
diff -Naur 3.5-2/debian/patches/02-ruby-relative-path.diff
3.5-4/debian/patches/02-ruby-relative-path.diff
--- 3.5-2/debian/patches/02-ruby-relative-path.diff 1970-01-01
01:00:00.0 +0100
+++ 3.5-4/debian/patches/02-ruby-relative-path.diff 2021-04-12
10:08:42.636804816 +0200
@@ -0,0 +1,19 @@
+commit 6c32e54d57af4f70e0bb4e8504d752d394c773e5
+Author: Alexander Neumann
+Date: Wed May 20 12:10:30 2020 +0200
+
+[Interp] Fix detection for ruby script started from relative paths.
+
+diff --git a/perl/lib/NeedRestart/Interp/Ruby.pm
b/perl/lib/NeedRestart/Interp/Ruby.pm
+index a333504..88d39c6 100644
+--- a/perl/lib/NeedRestart/Interp/Ruby.pm
b/perl/lib/NeedRestart/Interp/Ruby.pm
+@@ -171,7 +171,7 @@ sub files {
+ print STDERR "$LOGPREF #$pid: could not get a source file, skipping\n"
if($self->{debug});
+ return ();
+ }
+-my $src = $ARGV[0];
++my $src = abs_path($ARGV[0]);
+ unless(-r $src && -f $src) {
+ chdir($cwd);
+ print STDERR "$LOGPREF #$pid: source file '$src' not found, skipping\n"
if($self->{debug});
diff -Naur 3.5-2/debian/patches/03-fix-wrong-default-comment.diff
3.5-4/debian/patches/03-fix-wrong-default-comment.diff
--- 3.5-2/debian/patches/03-fix-wrong-default-comment.diff 1970-01-01
01:00:00.0 +0100
+++ 3.5-4/debian/patches/03-fix-wrong-default-comment.diff 2021-04-12
10:08:42.636804816 +0200
@@ -0,0 +1,21 @@
+commit 621e7bf65b86adcd2fc0448944d1ac9659e1d317
+Author: iasdeoupxe <39667843+iasdeou...@users.noreply.github.com>
+Date: Sat Apr 4 21:16:31 2020 +0200
+
+[Core] Fix comment for default value of `skip_mapfiles`.
+
+diff --git a/ex/needrestart.conf b/ex/needrestart.conf
+index b327855..c83bddb 100644
+--- a/ex/needrestart.conf
b/ex/needrestart.conf
+@@ -165,8 +165,8 @@ $nrconf{blacklist_mappings} = [
+ ];
+
+ # Verify mapped files in fileystem:
+-# 0 : enabled (default)
+-# -1: ignore non-existing files, workaround for chroots and broken grsecurity
kernels
++# 0 : enabled
++# -1: ignore non-existing files, workaround for chroots and broken grsecurity
kernels (default)
+ # 1 : disable check completely, rely on content of maps file only
+ $nrconf{skip_mapfiles} = -1;
+
diff -Naur 3.5-2/debian/patches/04-verbose-and-verbosity-confusion.diff
3.5-4/debian/patches
Bug#986037: kdenlive: crashes on audio setup
Am 07.04.21 um 16:16 schrieb Norbert Preining: Hi Patrick, good that you remind me of that ... Since (for myself?) this issue does not affect Debian bullseye downgrading the severity, because this release could not migrate then.. Fine with me. I actually found the problem, I guess I have to report it upstream: I have changed monitor and the new monitor has a higher resolution. Now what has happened that in the kdenliverc (.config/) there was a section [MainWindow] HDMI-A-0 Height 1080=1024 HDMI-A-0 Height 2048x1152=480 HDMI-A-0 Width 1920=1920 HDMI-A-0 Width 2048x1152=664 HDMI-A-0 Window-Maximized 1080x1920=true HDMI-A-0 XPosition=0 HDMI-A-0 XPosition 2048x1152=0 HDMI-A-0 YPosition=29 HDMI-A-0 YPosition 2048x1152=30 Height 1080=702 RestorePositionForNextInstance=false State=/wD9AQIAAAKYAAABN/wBD/sYAG4AbwB0AGUAcwBfAHcAaQBkAGcAZQB0AAD/ZwEAAAP7DgBsAGkAYgByAGEAcgB5AAD/ZwEAAAP7FABzAGMAcgBlAGUAbgBnAHIAYQBiAAD/YAEAAAP7GgBhAHUAZABpAG8AcwBwAGUAYwB0AHIAdQBtAQBmZgEAAAP7FgBwAHIAbwBqAGUAYwB0AF8AYgBpAG4BZwAAAGBgAQAAA/wAAADIiwAAAIsA+gEBAvsYAGUAZgBmAGUAYwB0AF8AcwB0AGEAYwBrAQD/VwEAAAP7HgBjAGwAaQBwAF8AcAByAG8AcABlAHIAdABpAGUAcwEA/wAAAFcBAAAD/n0AAAGAAAD6/wEC+wAAAB4AdAByAGEAbgBzAGkAdABpAG8AbgBfAGwAaQBzAHQAAP8AAABgAQAAA/sWAGUAZgBmAGUAYwB0AF8AbABpAHMAdAAA/wAAAGABAAAD/VQAAAFEAAABRAD6AQEC+wAAABgAYwBsAGkAcABfAG0AbwBuAGkAdABvAHIBAP8AAAFEAQAAA/seAHAAcgBvAGoAZQBjAHQAXwBtAG8AbgBpAHQAbwByAQD/AAABRAEAAAP7GAB1AG4AZABvAF8AaABpAHMAdABvAHIAeQAA/wAAAGABAAAD+woAbQBpAHgAZQByBlwAAAEkYwEAAAP7FgB2AGUAYwB0AG8AcgBzAGMAbwBwAGUAAP8AAAEyAQAAA/sQAHcAYQB2AGUAZgBvAHIAbQAA/wAAAKgBAAAD+wAAABQAcgBnAGIAXwBwAGEAcgBhAGQAZQAA/wAAAKQBAAAD+wAAABIAaABpAHMAdABvAGcAcgBhAG0AAP8AAAFKAQAAA/sSAFMAdQBiAHQAaQB0AGwAZQBzAAD/9AEAAAMAAAKYOAQECAj8AQICFgBtAGEAaQBuAFQAbwBvAGwAQgBhAHIBAP8AABgAZQB4AHQAcgBhAFQAbwBvAGwAQgBhAHIBAAACHv8AAA== ToolBarsMovable=Disabled Width 1920=1280 Window-Maximized 1080x1920=true eDP-1 Height 1080=702 eDP-1 Width 1920=1280 eDP-1 XPosition=640 eDP-1 YPosition=29 but the new monitor has different resolution (2560x1440) and with that monitor kdenlive simply crashed. Removing this section made kdenlive start up again. Looking into the newly generate kdenlive I actually don't see entries about eDP-1 HDMI-A-0 etc but only: [MainWindow] HDMI-A-0 Height 2048x1152=1020 HDMI-A-0 Width 2048x1152=1540 HDMI-A-0 XPosition 2048x1152=0 HDMI-A-0 YPosition 2048x1152=30 State=/wD9AQIAAAYEAAAByfwBD/sYAG4AbwB0AGUAcwBfAHcAaQBkAGcAZQB0AAD/ZwEAAAP7DgBsAGkAYgByAGEAcgB5AAD/ZwEAAAP7EgBTAHUAYgB0AGkAdABsAGUAcwAA/wAAAPQBAAAD+wAAABQAcwBjAHIAZQBlAG4AZwByAGEAYgAA/wAAAGABAAAD+wAAABoAYQB1AGQAaQBvAHMAcABlAGMAdAByAHUAbQAA/wAAAGYBAAAD+wAAABYAcAByAG8AagBlAGMAdABfAGIAaQBuAQDiYAEAAAP84wAAANwAAABgAPoAAQL7GABlAGYAZgBlAGMAdABfAHMAdABhAGMAawEA/wAAAGABAAAD+wAAAB4AYwBsAGkAcABfAHAAcgBvAHAAZQByAHQAaQBlAHMAAP8AAABgAQAAA/wAAAHBTwAAAIsA+gEBAvseAHQAcgBhAG4AcwBpAHQAaQBvAG4AXwBsAGkAcwB0AQD/BAEAAAP7FgBlAGYAZgBlAGMAdABfAGwAaQBzAHQBAP8EAQAAA/wAAAMQAAAC9UQA+gEBAvsYAGMAbABpAHAAXwBtAG8AbgBpAHQAbwByAQD/AAABRAEAAAP7HgBwAHIAbwBqAGUAYwB0AF8AbQBvAG4AaQB0AG8AcgEA/wAAAUQBAAAD+wAAABgAdQBuAGQAbwBfAGgAaQBzAHQAbwByAHkAAP8AAABgAQAAA/sKAG0AaQB4AGUAcgAA/wAAAGMBAAAD+wAAABYAdgBlAGMAdABvAHIAcwBjAG8AcABlAAD/AAABMgEAAAP7EAB3AGEAdgBlAGYAbwByAG0AAP8AAACoAQAAA/sUAHIAZwBiAF8AcABhAHIAYQBkAGUAAP8AAACkAQAAA/sSAGgAaQBzAHQAbwBnAHIAYQBtAAD/AAABSgEAAAMAAAYEAAABwgQECAj8AQICFgBtAGEAaQBuAFQAbwBvAGwAQgBhAHIBAP8AABgAZQB4AHQAcgBhAFQAbwBvAGwAQgBhAHIBAAACMf8AAA== ToolBarsMovable=Disabled so maybe some info of that couldn't be digested by kdenlive. Anyway - feel free to close the bug or do whatever you think is correct. If you want, I can reproduce this - just tried it and adding the section makes it crash again ;-) Best Norbert -- PREINING Norbert https://www.preining.info Fujitsu + IFMGA Guide + TU Wien + TeX Live + Debian Dev GPG: 0x860CDC13 fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13 Oh nice bug, good that you have found the reason! :) Could you set the bug to forwarded here after your report, then we can track this issue here as well and add the patch later OpenPGP_0x12D9B04A90CBD8E4.asc Description: OpenPGP public key OpenPGP_signature Description: OpenPGP digital signature
Bug#986664: unblock: luckybackup/0.5.0-5
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package luckybackup This release just fixes the start-as-root command, which was not working anymore. full diff: diff -Naur '--exclude=.svn' 0.5.0-4/debian/changelog 0.5.0-5/debian/changelog --- 0.5.0-4/debian/changelog2020-11-19 15:10:17.755212916 +0100 +++ 0.5.0-5/debian/changelog2021-03-18 15:31:40.217179052 +0100 @@ -1,3 +1,10 @@ +luckybackup (0.5.0-5) unstable; urgency=medium + + * Add patch 02-fix-pkexec from Bob to fix starting luckybackup as superuser. +Closes: #985169 + + -- Patrick Matthäi Thu, 18 Mar 2021 15:26:12 +0100 + luckybackup (0.5.0-4) unstable; urgency=medium * Adjust lintian overrides. diff -Naur '--exclude=.svn' 0.5.0-4/debian/patches/02-fix-pkexec.diff 0.5.0-5/debian/patches/02-fix-pkexec.diff --- 0.5.0-4/debian/patches/02-fix-pkexec.diff 1970-01-01 01:00:00.0 +0100 +++ 0.5.0-5/debian/patches/02-fix-pkexec.diff 2021-03-18 15:31:40.201179138 +0100 @@ -0,0 +1,11 @@ +# Fix luckybackup is not starting as superuser. Tested on KDE. +# Closes: #985169 + +diff -Naur luckybackup-0.5.0.orig/menu/luckybackup-pkexec luckybackup-0.5.0/menu/luckybackup-pkexec +--- luckybackup-0.5.0.orig/menu/luckybackup-pkexec 2018-11-02 15:36:19.0 +0100 luckybackup-0.5.0/menu/luckybackup-pkexec 2021-03-18 15:23:14.183871758 +0100 +@@ -1,3 +1,3 @@ + #!/bin/sh +-pkexec "/usr/bin/luckybackup" "$@" + ++pkexec env DISPLAY=$DISPLAY XAUTHORITY=$XAUTHORITY "/usr/bin/luckybackup" "$@" diff -Naur '--exclude=.svn' 0.5.0-4/debian/patches/series 0.5.0-5/debian/patches/series --- 0.5.0-4/debian/patches/series 2020-11-19 15:10:17.747212945 +0100 +++ 0.5.0-5/debian/patches/series 2021-03-18 15:31:40.205179117 +0100 @@ -1 +1,2 @@ 01-spelling-error.diff +02-fix-pkexec.diff unblock luckybackup/0.5.0-5 -- System Information: Debian Release: 10.9 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'proposed-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-16-amd64 (SMP w/2 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
