Bug#1069234: bcftools: gff2gff.py and guess-ploidy.py fails to run
Package: bcftools Version: 1.19-1+b1 Severity: normal Dear Maintainer, gff2gff.py fails to run with the error: $ gff2gff.py --help Traceback (most recent call last): File "/usr/bin/gff2gff.py", line 13, in import gffutils ModuleNotFoundError: No module named 'gffutils' And guess-ploidy.py fails to run with the error: $ guess-ploidy.py --help Traceback (most recent call last): File "/usr/bin/guess-ploidy.py", line 29, in import matplotlib as mpl ModuleNotFoundError: No module named 'matplotlib' Its missing the runtime dependencies. -- Regards Sudip -- System Information: Debian Release: trixie/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 6.6.13-amd64 (SMP w/8 CPU threads; PREEMPT) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages bcftools depends on: ii libc6 2.37-17 ii libhts3t64 1.19+ds-1.1+b1 Versions of packages bcftools recommends: ii perl 5.38.2-3 Versions of packages bcftools suggests: ii python33.11.8-1 pn python3-matplotlib pn python3-numpy pn texlive-latex-recommended
Bug#1069117: python3-evtx: evtx_filter_records.py fails to run
Package: python3-evtx Version: 0.7.4-1 Severity: normal X-Debbugs-Cc: sudipm.mukher...@gmail.com Dear Maintainer, evtx_filter_records.py fails to run in a Debian unstable docker image with the error: $ evtx_filter_records.py Traceback (most recent call last): File "/usr/bin/evtx_filter_records.py", line 3, in from lxml import etree ModuleNotFoundError: No module named 'lxml' It will need a runtime dependency on python3-lxml. -- Regards Sudip -- System Information: Debian Release: trixie/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 6.1.0-18-amd64 (SMP w/16 CPU threads; PREEMPT) Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: unable to detect Versions of packages python3-evtx depends on: ii python3 3.11.8-1 ii python3-more-itertools 10.2.0-1 ii python3-pyparsing 3.1.1-1 ii python3-six 1.16.0-6 ii python3-zipp1.0.0-6 python3-evtx recommends no packages. python3-evtx suggests no packages.
Bug#1069071: libadios-bin: adiosxml2h fails to run
Package: libadios-bin Version: 1.13.1-36 Severity: normal Dear Maintainer, adiosxml2h fails to run with the error: $ adiosxml2h Traceback (most recent call last): File "/usr/bin/adiosxml2h", line 13, in import ad_config ModuleNotFoundError: No module named 'ad_config' Also, from the same package "skel" fails to run with the error: $ skel File "/usr/bin/skel", line 61 print parser.description SyntaxError: Missing parentheses in call to 'print'. Did you mean print(...)? -- Regards Sudip -- System Information: Debian Release: trixie/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 6.6.13-amd64 (SMP w/8 CPU threads; PREEMPT) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages libadios-bin depends on: ii libblosc1 1.21.5+ds-1+b1 ii libbz2-1.01.0.8-5.1 ii libc6 2.37-17 ii libhdf5-mpich-103-1t641.10.10+repack-3.3 ii libhdf5-mpich-hl-100t64 1.10.10+repack-3.3 ii libhdf5-openmpi-103-1t64 1.10.10+repack-3.3 ii liblz4-1 1.9.4-2 ii libmpich124.2.0-5.1 ii libnetcdf-mpi-19 1:4.9.0-1+b3 ii libnetcdf19t641:4.9.2-5+b1 ii libopenmpi3t644.1.6-9 ii libsz21.1.3-1 ii python3 3.11.8-1 ii zlib1g1:1.3.dfsg-3.1 Versions of packages libadios-bin recommends: ii libadios-dev 1.13.1-36 libadios-bin suggests no packages.
Bug#1069069: reportbug: mma does not work on Python-3
Package: mma Version: 21.09-1 Severity: normal Dear Maintainer, Most of the scripts in the package does not work with Python3. $ mma-mnx File "/usr/bin/mma-mnx", line 262 x=0L ^ SyntaxError: invalid decimal literal $ pg2mma File "/usr/bin/pg2mma", line 9 print "pg2mma, (c) Bob van der Poel" SyntaxError: Missing parentheses in call to 'print'. Did you mean print(...)? $ mma-rm2std File "/usr/bin/mma-rm2std", line 31 print m ^^^ SyntaxError: Missing parentheses in call to 'print'. Did you mean print(...)? $ synthsplit File "/usr/bin/synthsplit", line 13 print "synthsplit, (c) Bob van der Poel" SyntaxError: Missing parentheses in call to 'print'. Did you mean print(...)? -- Regards Sudip -- System Information: Debian Release: trixie/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 6.6.13-amd64 (SMP w/8 CPU threads; PREEMPT) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages mma depends on: ii python3 3.11.8-1 ii python3-tk 3.12.3-1 Versions of packages mma recommends: ii timidity 2.14.0-8.2 mma suggests no packages.
Bug#1069067: xxdiff-scripts: xx-svn-review fails to run
Package: xxdiff-scripts Version: 1:5.1+git20220924+dfsg-1 Severity: normal Dear Maintainer, xx-svn-review fails to run with the error: $ xx-svn-review --help Traceback (most recent call last): File "/usr/bin/xx-svn-review", line 7, in from StringIO import StringIO ModuleNotFoundError: No module named 'StringIO' -- Regards Sudip -- System Information: Debian Release: trixie/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 6.6.13-amd64 (SMP w/8 CPU threads; PREEMPT) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages xxdiff-scripts depends on: ii python3 3.11.8-1 ii xxdiff 1:5.1+git20220924+dfsg-1+b1 Versions of packages xxdiff-scripts recommends: ii gnupg 2.2.40-1.1 ii patch 2.7.6-7 xxdiff-scripts suggests no packages.
Bug#1068998: xgridfit: ttx2xgf fails to run
Package: xgridfit Version: 2.3-4 Severity: normal Dear Maintainer, ttx2xgf fails to run with the error: $ ttx2xgf Traceback (most recent call last): File "/usr/bin/ttx2xgf", line 3, in from xgflib import run_ttx2xgf ModuleNotFoundError: No module named 'xgflib' -- Regards Sudip -- System Information: Debian Release: trixie/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 6.6.13-amd64 (SMP w/8 CPU threads; PREEMPT) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages xgridfit depends on: ii python33.11.6-1 ii python3-fontforge 1:20230101~dfsg-1.1 ii python3-libxml22.9.14+dfsg-1.3+b2 ii xsltproc 1.1.35-1 xgridfit recommends no packages. Versions of packages xgridfit suggests: pn fontforge pn fonttools
Bug#1068996: python3-bx: maf_word_frequency.py fails to run
Another problem with the same package: $ maf_tile_2.py Traceback (most recent call last): File "/usr/bin/maf_tile_2.py", line 34, in from cookbook import doc_optparse ModuleNotFoundError: No module named 'cookbook' -- Regards Sudip
Bug#1068996: python3-bx: maf_word_frequency.py fails to run
Package: python3-bx Version: 0.11.0-3 Severity: normal Dear Maintainer, maf_word_frequency.py fails to run with the error: $ maf_word_frequency.py Traceback (most recent call last): File "/usr/bin/maf_word_frequency.py", line 15, in import psyco ModuleNotFoundError: No module named 'psyco' -- Regards Sudip -- System Information: Debian Release: trixie/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 6.6.13-amd64 (SMP w/8 CPU threads; PREEMPT) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages python3-bx depends on: ii libc6 2.37-15 ii python3 3.11.6-1 ii python3-lzo 1.14-1+b4 ii python3-numpy [python3-numpy-abi9] 1:1.26.4+ds-6 ii zlib1g 1:1.3.dfsg-3+b1 python3-bx recommends no packages. python3-bx suggests no packages.
Bug#1068767: php-matthiasmullie-minify: minifycss fails to run
On Wed, Apr 10, 2024 at 07:07:34PM +0100, Sudip Mukherjee wrote:
> On Wed, Apr 10, 2024 at 06:38:36PM +0100, Sudip Mukherjee wrote:
> > Package: php-matthiasmullie-minify
> > Version: 1.3.68-6
> > Severity: normal
> >
> > Dear Maintainer,
> >
> > minifycss fails to run with the error:
> >
> > $ minifycss
> > PHP Warning: require_once(/usr/bin/../src/Minify.php): Failed to open
> > stream: No such file or directory in /usr/bin/minifycss on line 10
> > PHP Fatal error: Uncaught Error: Failed opening required
> > '/usr/bin/../src/Minify.php' (include_path='.:/usr/share/php') in
> > /usr/bin/minifycss:10
> > Stack trace:
> > #0 {main}
> > thrown in /usr/bin/minifycss on line 10
>
> The attached patch should fix the problem.
Sorry, the previous patch will not work properly. New patch added.
--
Regards
Sudip
diff -Nru matthiasmullie-minify-1.3.68/debian/changelog
matthiasmullie-minify-1.3.68/debian/changelog
--- matthiasmullie-minify-1.3.68/debian/changelog 2023-07-28
17:05:19.0 +0100
+++ matthiasmullie-minify-1.3.68/debian/changelog 2024-04-13
13:00:21.0 +0100
@@ -1,3 +1,10 @@
+matthiasmullie-minify (1.3.68-4.1) UNRELEASED; urgency=medium
+
+ * Non-maintainer upload.
+ * Fix paths of the required files.
+
+ -- Sudip Mukherjee Sat, 13 Apr 2024 13:00:21
+0100
+
matthiasmullie-minify (1.3.68-4) unstable; urgency=medium
* Team upload.
diff -Nru matthiasmullie-minify-1.3.68/debian/patches/fix-path.patch
matthiasmullie-minify-1.3.68/debian/patches/fix-path.patch
--- matthiasmullie-minify-1.3.68/debian/patches/fix-path.patch 1970-01-01
01:00:00.0 +0100
+++ matthiasmullie-minify-1.3.68/debian/patches/fix-path.patch 2024-04-13
13:00:21.0 +0100
@@ -0,0 +1,44 @@
+Description: Fix paths of the files minify required
+ PathConverter has been split into separate package and the paths needs
+ to be included as mentioned in the upstream issue.
+Author: Sudip Mukherjee
+Bug: https://github.com/matthiasmullie/minify/issues/48#issuecomment-90708149
+Bug-Debian: https://bugs.debian.org/1068767
+Forwarded: not-needed
+Last-Update: 2024-04-12
+---
+
+--- matthiasmullie-minify-1.3.68.orig/bin/minifycss
matthiasmullie-minify-1.3.68/bin/minifycss
+@@ -7,9 +7,11 @@ if (file_exists(__DIR__ . '/../../../aut
+ // if composer install
+ require_once __DIR__ . '/../../../autoload.php';
+ } else {
+-require_once __DIR__ . '/../src/Minify.php';
+-require_once __DIR__ . '/../src/CSS.php';
+-require_once __DIR__ . '/../src/Exception.php';
++require_once __DIR__ . '/../share/php/MatthiasMullie/Minify/Minify.php';
++require_once __DIR__ . '/../share/php/MatthiasMullie/Minify/CSS.php';
++require_once __DIR__ .
'/../share/php/MatthiasMullie/Minify/Exception.php';
++require_once __DIR__ .
'/../share/php/MatthiasMullie/PathConverter/ConverterInterface.php';
++require_once __DIR__ .
'/../share/php/MatthiasMullie/PathConverter/Converter.php';
+ }
+
+ error_reporting(E_ALL);
+--- matthiasmullie-minify-1.3.68.orig/bin/minifyjs
matthiasmullie-minify-1.3.68/bin/minifyjs
+@@ -7,9 +7,11 @@ if (file_exists(__DIR__ . '/../../../aut
+ // if composer install
+ require_once __DIR__ . '/../../../autoload.php';
+ } else {
+-require_once __DIR__ . '/../src/Minify.php';
+-require_once __DIR__ . '/../src/JS.php';
+-require_once __DIR__ . '/../src/Exception.php';
++require_once __DIR__ . '/../share/php/MatthiasMullie/Minify/Minify.php';
++require_once __DIR__ . '/../share/php/MatthiasMullie/Minify/JS.php';
++require_once __DIR__ .
'/../share/php/MatthiasMullie/Minify/Exception.php';
++require_once __DIR__ .
'/../share/php/MatthiasMullie/PathConverter/ConverterInterface.php';
++require_once __DIR__ .
'/../share/php/MatthiasMullie/PathConverter/Converter.php';
+ }
+
+ error_reporting(E_ALL);
diff -Nru matthiasmullie-minify-1.3.68/debian/patches/series
matthiasmullie-minify-1.3.68/debian/patches/series
--- matthiasmullie-minify-1.3.68/debian/patches/series 2023-07-28
17:05:19.0 +0100
+++ matthiasmullie-minify-1.3.68/debian/patches/series 2024-04-13
12:21:58.0 +0100
@@ -1,3 +1,4 @@
update_dataDir_to_live_in_proper_dir.patch
skip_scrapbook_test_if_not_installed.patch
support_phpunit10.patch
+fix-path.patch
Bug#1068855: hxtools: gpsh fails to run
Package: hxtools Version: 20231224-2 Severity: normal X-Debbugs-Cc: sudipm.mukher...@gmail.com Dear Maintainer, On a Debian container gpsh fails to run with the error: # gpsh Can't locate File/Find/Rule.pm in @INC (you may need to install the File::Find::Rule module) (@INC entries checked: . /etc/perl /usr/local/lib/x86_64-linux-gnu/perl/5.38.2 /usr/local/share/perl/5.38.2 /usr/lib/x86_64-linux-gnu/perl5/5.38 /usr/share/perl5 /usr/lib/x86_64-linux-gnu/perl-base /usr/lib/x86_64-linux-gnu/perl/5.38 /usr/share/perl/5.38 /usr/local/lib/site_perl) at /usr/bin/gpsh line 11. BEGIN failed--compilation aborted at /usr/bin/gpsh line 11. It will need a runtime dependency on libfile-find-rule-perl. -- Regards Sudip -- System Information: Debian Release: trixie/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 6.1.0-18-amd64 (SMP w/16 CPU threads; PREEMPT) Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: unable to detect Versions of packages hxtools depends on: ii libc6 2.37-15.1 ii libgcc-s1 14-20240330-1 ii libhx32 4.19-1 ii libstdc++6 14-20240330-1 ii perl5.38.2-3.2+b2 hxtools recommends no packages. hxtools suggests no packages.
Bug#1068845: fwbuilder: fwbuilder crashes when trying to create almost any type of new object
Package: fwbuilder
Version: 5.3.7-5+b2
Severity: normal
Tags: patch
Dear Maintainer,
fwbuilder crashes when trying to create almost any type of new object
To reproduce:
* start fwbuilder without any arguments
* click "New Object"
* click "New Library"
* fwbuilder will crash
The attached debdiff with upstream commit will fix the problem.
--
Regards
Sudip
-- System Information:
Debian Release: trixie/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 6.6.13-amd64 (SMP w/8 CPU threads; PREEMPT)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8),
LANGUAGE=en_GB:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages fwbuilder depends on:
ii fwbuilder-common5.3.7-5
ii libc6 2.37-15
ii libgcc-s1 14-20240201-3
ii libqt5core5t64 5.15.10+dfsg-7.2+b1
ii libqt5gui5t64 5.15.10+dfsg-7.2+b1
ii libqt5network5t64 5.15.10+dfsg-7.2+b1
ii libqt5printsupport5t64 5.15.10+dfsg-7.2+b1
ii libqt5widgets5t64 5.15.10+dfsg-7.2+b1
ii libsnmp40t645.9.4+dfsg-1.1+b1
ii libstdc++6 14-20240201-3
ii libxml2 2.9.14+dfsg-1.3+b2
ii libxslt1.1 1.1.35-1
ii zlib1g 1:1.3.dfsg-3+b1
Versions of packages fwbuilder recommends:
ii fwbuilder-doc 5.3.7-5
ii rcs5.10.1-1
fwbuilder suggests no packages.
-- no debconf information
diff -Nru fwbuilder-5.3.7/debian/changelog fwbuilder-5.3.7/debian/changelog
--- fwbuilder-5.3.7/debian/changelog2022-01-23 23:01:26.0 +
+++ fwbuilder-5.3.7/debian/changelog2024-04-11 23:04:28.0 +0100
@@ -1,3 +1,10 @@
+fwbuilder (5.3.7-5.1) UNRELEASED; urgency=medium
+
+ * Non-maintainer upload.
+ * Add upstream commit to fix crash creating new object.
+
+ -- Sudip Mukherjee Thu, 11 Apr 2024 23:04:28
+0100
+
fwbuilder (5.3.7-5) unstable; urgency=medium
[ Lukas Mardian ]
diff -Nru
fwbuilder-5.3.7/debian/patches/0001-adding-fix-for-crash-if-you-create-some-new-objects-.patch
fwbuilder-5.3.7/debian/patches/0001-adding-fix-for-crash-if-you-create-some-new-objects-.patch
---
fwbuilder-5.3.7/debian/patches/0001-adding-fix-for-crash-if-you-create-some-new-objects-.patch
1970-01-01 01:00:00.0 +0100
+++
fwbuilder-5.3.7/debian/patches/0001-adding-fix-for-crash-if-you-create-some-new-objects-.patch
2024-04-11 23:04:28.0 +0100
@@ -0,0 +1,38 @@
+From 102d68c3917950c688c1a3ca9bee42c3ff24b57f Mon Sep 17 00:00:00 2001
+From: bluelineXY
+Date: Thu, 22 Feb 2018 21:43:53 +0100
+Subject: [PATCH] adding fix for crash if you create some new objects type out
+ of the menu (e.g. ip addess)
+
+Origin: upstream,
https://github.com/fwbuilder/fwbuilder/commit/102d68c3917950c688c1a3ca9bee42c3ff24b57f
+Last-Update: 2024-04-11
+---
+ src/libgui/ObjectManipulator_tree_ops.cpp | 12
+ 1 file changed, 8 insertions(+), 4 deletions(-)
+
+diff --git a/src/libgui/ObjectManipulator_tree_ops.cpp
b/src/libgui/ObjectManipulator_tree_ops.cpp
+index ec80537d5..b3327f375 100644
+--- a/src/libgui/ObjectManipulator_tree_ops.cpp
b/src/libgui/ObjectManipulator_tree_ops.cpp
+@@ -774,10 +774,14 @@ void ObjectManipulator::moveItems(ObjectTreeViewItem
*dest,
+ const list )
+ {
+ string folder;
+-if (dest->getUserFolderParent() != 0) {
+-folder = dest->getUserFolderName().toUtf8().constData();
+-} else {
+-folder = dest->getFWObject()->getStr("folder");
++
++if(dest != NULL)
++{
++if (dest->getUserFolderParent() != 0) {
++folder = dest->getUserFolderName().toUtf8().constData();
++} else {
++folder = dest->getFWObject()->getStr("folder");
++}
+ }
+
+ FWCmdMacro *macro = new FWCmdMacro(tr("Move objects"));
+--
+2.39.2
+
diff -Nru fwbuilder-5.3.7/debian/patches/series
fwbuilder-5.3.7/debian/patches/series
--- fwbuilder-5.3.7/debian/patches/series 2022-01-20 13:09:55.0
+
+++ fwbuilder-5.3.7/debian/patches/series 2024-04-11 23:04:10.0
+0100
@@ -6,3 +6,4 @@
pkg-config_libxml2.patch
pkg-config_libxslt.patch
ed4db20ec6cabfaea9c36187b7ce40d9d93c6c79.patch
+0001-adding-fix-for-crash-if-you-create-some-new-objects-.patch
Bug#1068838: freecell-solver-bin: gen-multiple-pysol-layouts crashed with ModuleNotFoundError
Package: freecell-solver-bin Version: 5.0.0-2+b1 Severity: normal Dear Maintainer, gen-multiple-pysol-layouts crashed immediately with the error: $ gen-multiple-pysol-layouts Traceback (most recent call last): File "/usr/bin/gen-multiple-pysol-layouts", line 16, in from fc_solve_find_index_s2ints import CardRenderer ModuleNotFoundError: No module named 'fc_solve_find_index_s2ints' -- Regards Sudip -- System Information: Debian Release: trixie/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 6.6.13-amd64 (SMP w/8 CPU threads; PREEMPT) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages freecell-solver-bin depends on: ii libc62.37-15 ii libfreecell-solver0 5.0.0-2+b1 ii python3 3.11.6-1 freecell-solver-bin recommends no packages. freecell-solver-bin suggests no packages.
Bug#1068807: fstransform: fsattr fails to run
Package: fstransform Version: 0.9.4-1 Severity: normal Dear Maintainer, The package description says it has been tested on ext4 but it fails to run with the error: $ sudo fsattr ERROR: fsattr: this program is a NOT functional because it was compiled without -lext2fs -lcom_err -- Regards Sudip -- System Information: Debian Release: trixie/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 6.6.13-amd64 (SMP w/8 CPU threads; PREEMPT) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages fstransform depends on: ii libc62.37-15 ii libgcc-s1 [libgcc1] 14-20240201-3 ii libstdc++6 14-20240201-3 fstransform recommends no packages. fstransform suggests no packages.
Bug#1068772: uhd-host: usrpctl fails to run
Package: uhd-host Version: 4.6.0.0+ds1-5.1+b1 Severity: normal Dear Maintainer, usrpctl fails to run with the error: $ usrpctl Traceback (most recent call last): File "/usr/bin/usrpctl", line 15, in import uhd ModuleNotFoundError: No module named 'uhd' It should have a runtime dependency on python3-uhd. -- Regards Sudip -- System Information: Debian Release: trixie/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 6.6.13-amd64 (SMP w/8 CPU threads; PREEMPT) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages uhd-host depends on: ii libboost-filesystem1.83.0 1.83.0-2.1+b1 ii libboost-program-options1.83.0 1.83.0-2.1+b1 ii libboost-test1.83.0 1.83.0-2.1+b1 ii libboost-thread1.83.0 1.83.0-2.1+b1 ii libc6 2.37-15 ii libgcc-s1 14-20240201-3 ii libncurses6 6.4+20240113-1 ii libstdc++6 14-20240201-3 ii libtinfo6 6.4+20240113-1 ii libuhd4.6.0t64 4.6.0.0+ds1-5.1+b1 ii python3 3.11.6-1 ii python3-numpy [python3-numpy-abi9] 1:1.26.4+ds-6 ii python3-requests2.31.0+dfsg-1 Versions of packages uhd-host recommends: ii curl8.7.1-2 ii procps 2:4.0.4-4 Versions of packages uhd-host suggests: ii fdisk 2.39.3-6 pn gnuradio
Bug#1068771: xbtop: xbtop fails to run
Package: libxrt-utils Version: 202210.2.13.466+dfsg-8 Severity: normal Dear Maintainer, xbtop fails to run with the error: $ xbtop python3: can't open file '/usr/bin/../python/xbtop.py': [Errno 2] No such file or directory -- Regards Sudip -- System Information: Debian Release: trixie/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 6.6.13-amd64 (SMP w/8 CPU threads; PREEMPT) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages libxrt-utils depends on: ii libboost-filesystem1.74.0 1.74.0+ds1-23.1+b1 ii libc6 2.37-15 ii libgcc-s1 14-20240201-3 ii libstdc++6 14-20240201-3 ii libudev1 255.3-2 ii libxrt1202210.2.13.466+dfsg-8 ii python33.11.6-1 libxrt-utils recommends no packages. libxrt-utils suggests no packages.
Bug#1068768: librdf-query-perl: rqsh fails to run
Package: librdf-query-perl Version: 2.918-4 Severity: normal Dear Maintainer, rqsh fails to run with the error: $ rqsh Can't locate Term/ReadKey.pm in @INC (you may need to install the Term::ReadKey module) (@INC entries checked: /etc/perl /usr/local/lib/x86_64-linux-gnu/perl/5.38.2 /usr/local/share/perl/5.38.2 /usr/lib/x86_64-linux-gnu/perl5/5.38 /usr/share/perl5 /usr/lib/x86_64-linux-gnu/perl-base /usr/lib/x86_64-linux-gnu/perl/5.38 /usr/share/perl/5.38 /usr/local/lib/site_perl) at /usr/bin/rqsh line 14. BEGIN failed--compilation aborted at /usr/bin/rqsh line 14. -- Regards Sudip -- System Information: Debian Release: trixie/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 6.6.13-amd64 (SMP w/8 CPU threads; PREEMPT) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages librdf-query-perl depends on: ii libcgi-pm-perl 4.64-1 ii libdatetime-format-w3cdtf-perl 0.08-1 ii liberror-perl 0.17029-2 ii libjson-perl4.1-1 ii libmodule-pluggable-perl5.2-5 ii libossp-uuid-perl 1.6.2-1.5+b13 ii libparse-recdescent-perl1.967015+dfsg-4 ii librdf-trine-perl 1.019-4 ii libset-scalar-perl 1.29-3 ii liburi-perl 5.26-1 ii perl [libfile-spec-perl]5.38.2-3.2+b2 Versions of packages librdf-query-perl recommends: ii libgeo-distance-perl 0.25-3 ii libgetopt-simple-perl 1.52-7 ii libwww-perl6.76-1 librdf-query-perl suggests no packages.
Bug#1068767: php-matthiasmullie-minify: minifycss fails to run
On Wed, Apr 10, 2024 at 06:38:36PM +0100, Sudip Mukherjee wrote:
> Package: php-matthiasmullie-minify
> Version: 1.3.68-6
> Severity: normal
>
> Dear Maintainer,
>
> minifycss fails to run with the error:
>
> $ minifycss
> PHP Warning: require_once(/usr/bin/../src/Minify.php): Failed to open
> stream: No such file or directory in /usr/bin/minifycss on line 10
> PHP Fatal error: Uncaught Error: Failed opening required
> '/usr/bin/../src/Minify.php' (include_path='.:/usr/share/php') in
> /usr/bin/minifycss:10
> Stack trace:
> #0 {main}
> thrown in /usr/bin/minifycss on line 10
The attached patch should fix the problem.
--
Regards
Sudip
diff -Nru matthiasmullie-minify-1.3.68/debian/changelog
matthiasmullie-minify-1.3.68/debian/changelog
--- matthiasmullie-minify-1.3.68/debian/changelog 2023-07-28
17:05:19.0 +0100
+++ matthiasmullie-minify-1.3.68/debian/changelog 2024-04-10
19:00:59.0 +0100
@@ -1,3 +1,10 @@
+matthiasmullie-minify (1.3.68-4.1) UNRELEASED; urgency=medium
+
+ * Non-maintainer upload.
+ * Fix paths of the required files. (Closes: #1068767)
+
+ -- Sudip Mukherjee Wed, 10 Apr 2024 19:00:59
+0100
+
matthiasmullie-minify (1.3.68-4) unstable; urgency=medium
* Team upload.
diff -Nru matthiasmullie-minify-1.3.68/debian/patches/fix-path.patch
matthiasmullie-minify-1.3.68/debian/patches/fix-path.patch
--- matthiasmullie-minify-1.3.68/debian/patches/fix-path.patch 1970-01-01
01:00:00.0 +0100
+++ matthiasmullie-minify-1.3.68/debian/patches/fix-path.patch 2024-04-10
19:00:43.0 +0100
@@ -0,0 +1,36 @@
+Description: Fix paths of the files minify required
+Author: Sudip Mukherjee
+Forwarded: not-needed
+Last-Update: 2024-04-10
+---
+
+--- matthiasmullie-minify-1.3.68.orig/bin/minifycss
matthiasmullie-minify-1.3.68/bin/minifycss
+@@ -7,9 +7,9 @@ if (file_exists(__DIR__ . '/../../../aut
+ // if composer install
+ require_once __DIR__ . '/../../../autoload.php';
+ } else {
+-require_once __DIR__ . '/../src/Minify.php';
+-require_once __DIR__ . '/../src/CSS.php';
+-require_once __DIR__ . '/../src/Exception.php';
++require_once __DIR__ . '/../share/php/MatthiasMullie/Minify/Minify.php';
++require_once __DIR__ . '/../share/php/MatthiasMullie/Minify/CSS.php';
++require_once __DIR__ .
'/../share/php/MatthiasMullie/Minify/Exception.php';
+ }
+
+ error_reporting(E_ALL);
+--- matthiasmullie-minify-1.3.68.orig/bin/minifyjs
matthiasmullie-minify-1.3.68/bin/minifyjs
+@@ -7,9 +7,9 @@ if (file_exists(__DIR__ . '/../../../aut
+ // if composer install
+ require_once __DIR__ . '/../../../autoload.php';
+ } else {
+-require_once __DIR__ . '/../src/Minify.php';
+-require_once __DIR__ . '/../src/JS.php';
+-require_once __DIR__ . '/../src/Exception.php';
++require_once __DIR__ . '/../share/php/MatthiasMullie/Minify/Minify.php';
++require_once __DIR__ . '/../share/php/MatthiasMullie/Minify/CSS.php';
++require_once __DIR__ .
'/../share/php/MatthiasMullie/Minify/Exception.php';
+ }
+
+ error_reporting(E_ALL);
diff -Nru matthiasmullie-minify-1.3.68/debian/patches/series
matthiasmullie-minify-1.3.68/debian/patches/series
--- matthiasmullie-minify-1.3.68/debian/patches/series 2023-07-28
17:05:19.0 +0100
+++ matthiasmullie-minify-1.3.68/debian/patches/series 2024-04-10
18:44:19.0 +0100
@@ -1,3 +1,4 @@
update_dataDir_to_live_in_proper_dir.patch
skip_scrapbook_test_if_not_installed.patch
support_phpunit10.patch
+fix-path.patch
Bug#1068767: php-matthiasmullie-minify: minifycss fails to run
Package: php-matthiasmullie-minify
Version: 1.3.68-6
Severity: normal
Dear Maintainer,
minifycss fails to run with the error:
$ minifycss
PHP Warning: require_once(/usr/bin/../src/Minify.php): Failed to open stream:
No such file or directory in /usr/bin/minifycss on line 10
PHP Fatal error: Uncaught Error: Failed opening required
'/usr/bin/../src/Minify.php' (include_path='.:/usr/share/php') in
/usr/bin/minifycss:10
Stack trace:
#0 {main}
thrown in /usr/bin/minifycss on line 10
--
Regards
Sudip
-- System Information:
Debian Release: trixie/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 6.6.13-amd64 (SMP w/8 CPU threads; PREEMPT)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8),
LANGUAGE=en_GB:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages php-matthiasmullie-minify depends on:
ii php-cli2:8.2+93
ii php-common 2:93
ii php-matthiasmullie-path-converter 1.1.3-2
ii php8.2-cli [php-cli] 8.2.17-1+b1
php-matthiasmullie-minify recommends no packages.
Versions of packages php-matthiasmullie-minify suggests:
pn php-psr-cache-implementation
Bug#1068759: quickml: quickml fails to install
Package: quickml Version: 0.8-1 Severity: normal Dear Maintainer, quickml fails to install with the error: Setting up quickml (0.8-1) ... Job for quickml.service failed because the control process exited with error code. See "systemctl status quickml.service" and "journalctl -xeu quickml.service" for details. invoke-rc.d: initscript quickml, action "start" failed. × quickml.service Loaded: loaded (/etc/init.d/quickml; generated) Active: failed (Result: exit-code) since Wed 2024-04-10 13:32:44 BST; 7ms ago Docs: man:systemd-sysv-generator(8) Process: 2597 ExecStart=/etc/init.d/quickml start (code=exited, status=1/FAILURE) CPU: 84ms Apr 10 13:32:44 debian quickml[2603]: from /usr/lib/ruby/vendor_ruby/quickml/server.rb:16:in `' Apr 10 13:32:44 debian quickml[2603]: from :86:in `require' Apr 10 13:32:44 debian quickml[2603]: from :86:in `require' Apr 10 13:32:44 debian quickml[2603]: from /usr/lib/ruby/vendor_ruby/quickml.rb:7:in `' Apr 10 13:32:44 debian quickml[2603]: from :86:in `require' Apr 10 13:32:44 debian quickml[2603]: from :86:in `require' Apr 10 13:32:44 debian quickml[2603]: from /usr/sbin/quickml:15:in `' Apr 10 13:32:44 debian systemd[1]: quickml.service: Control process exited, code=exited, status=1/FAILURE Apr 10 13:32:44 debian systemd[1]: quickml.service: Failed with result 'exit-code'. Apr 10 13:32:44 debian systemd[1]: Failed to start quickml.service. dpkg: error processing package quickml (--configure): installed quickml package post-installation script subprocess returned error exit status 1 Processing triggers for libc-bin (2.37-15) ... Processing triggers for man-db (2.12.0-3) ... Processing triggers for fontconfig (2.14.2-6+b1) ... Errors were encountered while processing: quickml E: Sub-process /usr/bin/dpkg returned an error code (1) It will need a runtime dependency on ruby-thwait and needs to have a file "/etc/mailname" to start. -- Regards Sudip -- System Information: Debian Release: trixie/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 6.6.13-amd64 (SMP w/8 CPU threads; PREEMPT) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages quickml depends on: ii init-system-helpers1.66 ii ruby 1:3.1+nmu1 ii sysvinit-utils [lsb-base] 3.08-6 quickml recommends no packages. quickml suggests no packages.
Bug#1068729: translate-toolkit: get_moz_enUS fails to run
Package: translate-toolkit Version: 3.12.2-1 Severity: normal Dear Maintainer, get_moz_enUS fails to run with the error: $ get_moz_enUS Traceback (most recent call last): File "/usr/bin/get_moz_enUS", line 160, in process_l10n_ini(product_ini) File "/usr/bin/get_moz_enUS", line 46, in process_l10n_ini with open(path_neutral(inifile)) as fh: ^^^ FileNotFoundError: [Errno 2] No such file or directory: 'mozilla/locales/l10n.ini' -- Regards Sudip -- System Information: Debian Release: trixie/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 6.6.13-amd64 (SMP w/8 CPU threads; PREEMPT) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages translate-toolkit depends on: ii python33.11.6-1 ii python3-pkg-resources 68.1.2-2 ii python3-translate 3.12.2-1 Versions of packages translate-toolkit recommends: ii translate-toolkit-doc 3.12.2-1 translate-toolkit suggests no packages.
Bug#1068728: translate-toolkit: tmserver fails to run
Package: translate-toolkit Version: 3.12.2-1 Severity: normal Dear Maintainer, tmserver fails to run with the error: $ tmserver Traceback (most recent call last): File "/usr/bin/tmserver", line 5, in from translate.services.tmserver import main File "/usr/lib/python3/dist-packages/translate/services/tmserver.py", line 30, in from translate.misc import selector, wsgi File "/usr/lib/python3/dist-packages/translate/misc/wsgi.py", line 23, in from cheroot.wsgi import Server ModuleNotFoundError: No module named 'cheroot' It needs a runtime dependency on python3-cheroot. -- Regards Sudip -- System Information: Debian Release: trixie/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 6.6.13-amd64 (SMP w/8 CPU threads; PREEMPT) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages translate-toolkit depends on: ii python33.11.6-1 ii python3-pkg-resources 68.1.2-2 ii python3-translate 3.12.2-1 Versions of packages translate-toolkit recommends: ii translate-toolkit-doc 3.12.2-1 translate-toolkit suggests no packages.
Bug#1068727: libhtml-formfu-perl: html_formfu_dumpconf.pl fails to run
Package: libhtml-formfu-perl Version: 2.07000-1 Severity: normal Dear Maintainer, html_formfu_dumpconf.pl fails to run with the error: $ html_formfu_dumpconf.pl Can't locate Regexp/Assemble.pm in @INC (you may need to install the Regexp::Assemble module) (@INC entries checked: /etc/perl /usr/local/lib/x86_64-linux-gnu/perl/5.38.2 /usr/local/share/perl/5.38.2 /usr/lib/x86_64-linux-gnu/perl5/5.38 /usr/share/perl5 /usr/lib/x86_64-linux-gnu/perl-base /usr/lib/x86_64-linux-gnu/perl/5.38 /usr/share/perl/5.38 /usr/local/lib/site_perl) at /usr/bin/html_formfu_dumpconf.pl line 7. BEGIN failed--compilation aborted at /usr/bin/html_formfu_dumpconf.pl line 7. It will need a runtime dependency on libregexp-assemble-perl. -- Regards Sudip -- System Information: Debian Release: trixie/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 6.6.13-amd64 (SMP w/8 CPU threads; PREEMPT) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages libhtml-formfu-perl depends on: ii libcgi-pm-perl 4.64-1 ii libclone-perl 0.46-1+b1 ii libconfig-any-perl 0.33-1 ii libdata-visitor-perl 0.32-1 ii libdatetime-format-builder-perl0.8300-1 ii libdatetime-format-natural-perl1.18-1 ii libdatetime-format-strptime-perl 1.7900-1 ii libdatetime-locale-perl1:1.41-1 ii libdatetime-perl 2:1.65-1+b1 ii libemail-valid-perl1.204-1 ii libfile-sharedir-perl 1.118-3 ii libhash-flatten-perl 1.19-5 ii libhtml-scrubber-perl 0.19-2 ii libhtml-tokeparser-simple-perl 3.16-4 ii libjson-maybexs-perl 1.004005-1 ii liblist-moreutils-perl 0.430-2 ii libmoose-perl 2.2207-1+b1 ii libmoosex-aliases-perl 0.11-2 ii libmoosex-attribute-chained-perl 1.0.3-2 ii libnumber-format-perl 1.76-1 ii libpath-class-perl 0.37-4 ii libreadonly-perl 2.050-3 ii libregexp-common-perl 2017060201-3 ii libtask-weaken-perl1.06-2 ii libwww-perl6.76-1 ii libyaml-libyaml-perl 0.89+ds-1+b1 ii perl 5.38.2-3.2+b2 ii perl-base [libscalar-list-utils-perl] 5.38.2-3.2+b2 libhtml-formfu-perl recommends no packages. Versions of packages libhtml-formfu-perl suggests: pn libcgi-simple-perl pn libhtml-formfu-model-dbic-perl
Bug#1068716: pdl: dh_pdl fails with "compilation aborted"
Package: pdl Version: 1:2.087-1 Severity: normal Dear Maintainer, dh_pdl fails with the error: Can't locate Debian/Debhelper/Dh_Lib.pm in @INC (you may need to install the Debian::Debhelper::Dh_Lib module) (@INC entries checked: /etc/perl /usr/local/lib/x86_64-linux-gnu/perl/5.38.2 /usr/local/share/perl/5.38.2 /usr/lib/x86_64-linux-gnu/perl5/5.38 /usr/share/perl5 /usr/lib/x86_64-linux-gnu/perl-base /usr/lib/x86_64-linux-gnu/perl/5.38 /usr/share/perl/5.38 /usr/local/lib/site_perl) at /usr/bin/dh_pdl line 12. BEGIN failed--compilation aborted at /usr/bin/dh_pdl line 12. It will need a runtime dependency on libdebhelper-perl. -- Regards Sudip -- System Information: Debian Release: trixie/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 6.6.13-amd64 (SMP w/8 CPU threads; PREEMPT) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages pdl depends on: ii libc6 2.37-15 ii libfile-which-perl1.27-2 ii libgd32.3.3-9+b1 ii libgfortran5 14-20240201-3 ii libgsl27 2.7.1+dfsg-6+b1 ii libhdf4-0-alt 4.2.16-4+b1 ii libncurses6 6.4+20240113-1 ii libpod-parser-perl1.67-1 ii libproj25 9.4.0-1+b1 ii libterm-readkey-perl 2.38-2+b3 ii libtinfo6 6.4+20240113-1 ii perl [libtext-balanced-perl] 5.38.2-3.2+b2 ii perl-base [perlapi-5.38.2]5.38.2-3.2+b2 ii sensible-utils0.0.22 Versions of packages pdl recommends: ii libpgplot-perl 1:2.28-1+b3 ii libterm-readline-gnu-perl 1.46-1+b2 Versions of packages pdl suggests: pn doc-base pn libastro-fits-header-perl pn libdevel-repl-perl pn libextutils-f77-perl pn libfile-map-perl ii libgl1 1.7.0-1 pn libinline-c-perl pn libinline-perl pn libmodule-compile-perl pn libopengl-perl pn netpbm | imagemagick pn proj-bin
Bug#1068241: authselect: pam_lastlog.so is gone
On Tue, 2 Apr 2024 at 15:45, Chris Hofstaedtler wrote: > > Source: authselect > Version: 1.5.0-1 > > Hi, > > it appears authselect references pam_lastlog.so. However, this > module has been disabled in PAM upstream, and is also no longer > shipped in Debian's PAM. Thanks for reporting this. > > Please adapt your package. I think I will wait a few more days to see the outcome of the discussion at #1068017 and #1066060. then check with upstream before doing anything. -- Regards Sudip
Bug#1068474: yforth segfaults immediately on launching
On Sat, 6 Apr 2024 at 00:50, Bdale Garbee wrote: > > Sudip Mukherjee writes: > > > yforth is causing a segfault immediately on startup. > > Thanks for the bug report. I haven't had reason to use yforth in many > years, (the package was last updated on 11 October 2012), so I hadn't > noticed! I dont use forth, just happened to notice the bug reported in Ubuntu. > > My guess is that this is a simple 64-bit system incompatibility, as a > quick rebuild of the package on my current 64-bit laptop yields a large > number of warnings about casts of pointer from integer of different size... I tried to debug it, the first segfault is at https://sources.debian.org/src/yforth/0.2.1-1/search.c/#L84 and is caused by "_align();" at https://sources.debian.org/src/yforth/0.2.1-1/search.c/#L81 which completely changed the address and so it now tried to set NULL to an invalid location. I stopped after seeing there are many such macros like "_align()" which are modifying the pointers and imho, it will be a nightmare to fix it. -- Regards Sudip
Bug#1068474: yforth segfaults immediately on launching
Source: yforth Version: 0.2.1-1 Severity: important X-Debbugs-Cc: sudipm.mukher...@gmail.com Dear Maintainer, yforth is causing a segfault immediately on startup. $ yforth yForth? v0.2 Copyright (C) 2012 Luca Padovani This program comes with ABSOLUTELY NO WARRANTY. This is free software, and you are welcome to redistribute it under certain conditions; see LICENSE for details. error(17): segmentation fault. Segmentation fault Though "yforth -h" works and shows the help message. -- Regards Sudip
Bug#1062636: close
Control: close -1 -- Closing this as the ABI is unaffected in time_t transition. Adding irc chat for reference: Mar 16 18:01:25 sudip: libsrm> it appears a later analysis showed the ABI was unaffected but we missed closing the bug so far, sorry. You can close it with this explanation (referencing https://adrien.dcln.fr/misc/armhf-time_t/2024-02-26T12%3A07%3A00/summary/results_none.txt if you wish) -- Regards Sudip
Bug#1027756: RFP: vncdotool -- command line VNC client
Control: retitle -1 ITP: vncdotool -- command line VNC client Control: owner -1 ! -- I was looking for something to use with VNC for a personal project I was planning and found about vncdotool. Initial test showed it will work perfectly for me. -- Regards Sudip
Bug#849712: motion: Motion starts but immediately exits when run as a daemon using systemd
Control: severity -1 important
Control: tags -1 patch
--
Marking this bug as important as the package is mostly unusable by a
non-technical user.
The motion.service can only start if the user manually creates /var/log/motion
folder.
Patch attached to fix this. The suggested change was already part of the
motion init script but was dropped when updating it to systemd service.
The old code can be seen at:
https://sources.debian.org/src/motion/4.1.1-1.1/debian/motion.init/#L60
--
Regards
Sudip
diff -Nru motion-4.6.0/debian/changelog motion-4.6.0/debian/changelog
--- motion-4.6.0/debian/changelog 2023-11-12 19:17:59.0 +
+++ motion-4.6.0/debian/changelog 2024-03-05 22:24:01.0 +
@@ -1,3 +1,10 @@
+motion (4.6.0-1.1) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Create log folder if it does not exist. (Closes: #849712)
+
+ -- Sudip Mukherjee Tue, 05 Mar 2024 22:24:01
+
+
motion (4.6.0-1) unstable; urgency=medium
* New upstream release
diff -Nru motion-4.6.0/debian/motion.postinst
motion-4.6.0/debian/motion.postinst
--- motion-4.6.0/debian/motion.postinst 2023-02-03 12:28:41.0 +
+++ motion-4.6.0/debian/motion.postinst 2024-03-05 22:24:01.0 +
@@ -24,8 +24,16 @@
fi
}
+add_log_if_missing() {
+if ! [ -d /var/log/motion ]; then
+ mkdir -m 02750 /var/log/motion
+ chown motion:adm /var/log/motion
+fi
+}
+
add_group_if_missing
add_user_if_missing
+add_log_if_missing
db_stop
Bug#1064030: lcov: Please re-enable tests
Source: lcov Version: 2.0-3 Severity: wishlist Tags: patch X-Debbugs-Cc: sudipm.mukher...@gmail.com Dear Maintainer, The tests during the build time have been disabled. But the tests are failing due to parallel builds. I have raised a MR in salsa [1] with the changes to disable parallel builds and to enable the tests. A build can also be seen at [2]. [1] https://salsa.debian.org/mckinstry/lcov/-/merge_requests/2 [2] https://salsa.debian.org/sudip/lcov/-/jobs/5195976 -- Regards Sudip
Bug#1063740: lxqt-archiver: Can't create .zip archive. "Failed to execute command." and "Archive not found" errors
Source: lxqt-archiver Version: 0.7.0-3 Severity: important Tags: upstream X-Debbugs-Cc: sudipm.mukher...@gmail.com Dear Maintainer, lxqt-archiver depends on p7zip-full which now is a transitional package and installs 7zip. Creating zip files with lxqt-archiver is now using 7z and the option '-l' is invalid with 7z. As a result it fails to create zip files. Upstream issue: https://github.com/lxqt/lxqt-archiver/issues/379 -- Regards Sudip
Bug#1063447: ModuleNotFoundError: No module named 'keyring'
Package: lptools
Version: 0.3.0-1
Severity: important
X-Debbugs-Cc: sudipm.mukher...@gmail.com
Dear Maintainer,
lptools fails to run and gives the following error on a fresh install of Debian
Trixie.
Traceback (most recent call last):
File "/usr/bin/lp-list-bugs", line 60, in
main()
File "/usr/bin/lp-list-bugs", line 40, in main
launchpad = config.get_launchpad("list-bugs")
^
File "/usr/lib/python3/dist-packages/lptools/config.py", line 53, in
get_launchpad
return Launchpad.login_with("lptools-%s" % appname, instance)
^^
File "/usr/lib/python3/dist-packages/launchpadlib/launchpad.py", line 700, in
login_with
return cls._authorize_token_and_login(
^^^
File "/usr/lib/python3/dist-packages/launchpadlib/launchpad.py", line 445, in
_authorize_token_and_login
cached_credentials = credential_store.load(
^^
File "/usr/lib/python3/dist-packages/launchpadlib/credentials.py", line 345,
in load
return self.do_load(unique_key)
File "/usr/lib/python3/dist-packages/launchpadlib/credentials.py", line 423,
in do_load
self._ensure_keyring_imported()
File "/usr/lib/python3/dist-packages/launchpadlib/credentials.py", line 388,
in _ensure_keyring_imported
import keyring
ModuleNotFoundError: No module named 'keyring'
Steps to reproduce the error:
1. Create a fresh install of Debian.
2. While installing, select xfce.
3, Install lptools
4. Try use lptools, I used "lp-list-bugs 2052663".
-- System Information:
Debian Release: trixie/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 6.6.13-amd64 (SMP w/8 CPU threads; PREEMPT)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages lptools depends on:
ii python3 3.11.6-1
ii python3-breezy3.3.4-1.1
ii python3-launchpadlib 1.11.0-2
ii python3-xdg 0.28-2
ii sensible-utils0.0.22
Versions of packages lptools recommends:
ii python3-chameleon 3.8.1-1
pn python3-indicate
Versions of packages lptools suggests:
pn python3-tdb
-- no debconf information
This is easily reproducible and I will be happy to test or provide any extra
log if needed.
--
Regards
Sudip
Bug#1061515: transition: ace
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: transition X-Debbugs-Cc: sudipm.mukher...@gmail.com Control: affects -1 + src:ace Hi, Small transition with only two affected packages: diagnostics, ivtools, Both of them builds fine with ace 7.1.3+dfsg-1 in experimental. The autogenerated ben tracker looks good. Please consider 'ace' for transition. Thanks in advance. -- Regards Sudip
Bug#1043009: lcovutil.pm is missing
Control: fixed -1 lcov/2.0-4 Control: close -1 lcov/2.0-4 -- On Fri, Aug 04, 2023 at 10:19:08AM +0100, Danilo Egea Gondolfo wrote: > Package: lcov > Version: 2.0-1 > Severity: important > > Dear Maintainer, > > The new version of the lcov package (2.0-1) is not installing the file > lib/lcovutil.pm. > This file didn't exist in the previous version so I guess it's just a matter > of updating d/rules accordingly. I tested on Debian Sid and I see lcov is working. $ lsb_release -a No LSB modules are available. Distributor ID: Debian Description:Debian GNU/Linux trixie/sid Release:n/a Codename: trixie $ lcov --version lcov: LCOV version 2.0-1 Marking it as fixed 2.0-4. -- Regards Sudip
Bug#1038961: AttributeError
I can reproduce the issue. I think it is because it is an X11 app which is being run through Wayland directly. Please try the following command from a terminal: GDK_BACKEND=x11 flowblade -- Regards Sudip
Bug#1058796: pure-ftpd: diff for NMU version 1.0.50-2.2
Control: tags 1058796 + patch
Control: tags 1058796 + pending
--
Dear maintainer,
I've prepared an NMU for pure-ftpd (versioned as 1.0.50-2.2) and
uploaded it to DELAYED/10. Please feel free to tell me if I
should delay it longer.
--
Regards
Sudip
diff -Nru pure-ftpd-1.0.50/debian/changelog pure-ftpd-1.0.50/debian/changelog
--- pure-ftpd-1.0.50/debian/changelog 2022-01-31 18:42:16.0 +
+++ pure-ftpd-1.0.50/debian/changelog 2024-01-11 19:40:01.0 +
@@ -1,3 +1,11 @@
+pure-ftpd (1.0.50-2.2) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Apply upstream patch to fix segfault by parsing
+port number properly. (Closes: #1058796)
+
+ -- Sudip Mukherjee Thu, 11 Jan 2024 19:40:01
+
+
pure-ftpd (1.0.50-2.1) unstable; urgency=medium
* Non-maintainer upload.
diff -Nru pure-ftpd-1.0.50/debian/patches/fix-port.patch
pure-ftpd-1.0.50/debian/patches/fix-port.patch
--- pure-ftpd-1.0.50/debian/patches/fix-port.patch 1970-01-01
01:00:00.0 +0100
+++ pure-ftpd-1.0.50/debian/patches/fix-port.patch 2024-01-11
19:39:57.0 +
@@ -0,0 +1,45 @@
+From c3f0f3c91d86939e6fabf5f65c6c6fc964e6032e Mon Sep 17 00:00:00 2001
+From: Frank Denis
+Date: Thu, 20 Jan 2022 19:54:27 +0100
+Subject: [PATCH] PostgreSQL: don't escape the port number in the connection
string
+
+It's already an integer, not a string.
+
+Reported by Artyom Davidov, thanks!
+
+Origin: upstream,
https://github.com/jedisct1/pure-ftpd/commit/c3f0f3c91d86939e6fabf5f65c6c6fc964e6032e
+Bug-Debian: https://bugs.debian.org/1058796
+Last-Update: 2024-01-11
+---
+ src/log_pgsql.c | 4 +---
+ 1 file changed, 1 insertion(+), 3 deletions(-)
+
+diff --git a/src/log_pgsql.c b/src/log_pgsql.c
+index 875b71f..bb08c3b 100644
+--- a/src/log_pgsql.c
b/src/log_pgsql.c
+@@ -278,7 +278,6 @@ static int pw_pgsql_connect(PGconn ** const id_sql_server)
+ *id_sql_server = NULL;
+
+ if ((escaped_server = pw_pgsql_escape_conninfo(server)) == NULL ||
+-(escaped_port = pw_pgsql_escape_conninfo(port)) == NULL ||
+ (escaped_db = pw_pgsql_escape_conninfo(db)) == NULL ||
+ (escaped_user = pw_pgsql_escape_conninfo(user)) == NULL ||
+ (escaped_pw = pw_pgsql_escape_conninfo(pw)) == NULL) {
+@@ -296,7 +295,7 @@ static int pw_pgsql_connect(PGconn ** const id_sql_server)
+ }
+ if (SNCHECK(snprintf(conninfo, sizeof_conninfo,
+ PGSQL_CONNECT_FMTSTRING,
+- escaped_server, escaped_port, escaped_db,
++ escaped_server, port, escaped_db,
+ escaped_user, escaped_pw), sizeof_conninfo)) {
+ goto bye;
+ }
+@@ -314,7 +313,6 @@ static int pw_pgsql_connect(PGconn ** const id_sql_server)
+ bye:
+ free(conninfo);
+ free(escaped_server);
+-free(escaped_port);
+ free(escaped_db);
+ free(escaped_user);
+ free(escaped_pw);
diff -Nru pure-ftpd-1.0.50/debian/patches/series
pure-ftpd-1.0.50/debian/patches/series
--- pure-ftpd-1.0.50/debian/patches/series 2022-01-31 18:42:16.0
+
+++ pure-ftpd-1.0.50/debian/patches/series 2024-01-11 17:25:32.0
+
@@ -1 +1,2 @@
maria-db-cross.diff
+fix-port.patch
Bug#1057935: ncurses-hexedit: diff for NMU version 0.9.7+orig-7.3
Control: tags 1057935 + pending
--
Dear maintainer,
I've prepared an NMU for ncurses-hexedit (versioned as 0.9.7+orig-7.3) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should delay it longer.
--
Regards
Sudip
diff -Nru ncurses-hexedit-0.9.7+orig/debian/changelog
ncurses-hexedit-0.9.7+orig/debian/changelog
--- ncurses-hexedit-0.9.7+orig/debian/changelog 2023-02-10 00:03:53.0
+
+++ ncurses-hexedit-0.9.7+orig/debian/changelog 2024-01-05 15:59:12.0
+
@@ -1,3 +1,11 @@
+ncurses-hexedit (0.9.7+orig-7.3) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * d/p/ncurses_ftbfs.patch:
+Stop using fields of opaque _WINDOW struct (Closes: #1057935)
+
+ -- Mate Kukri Fri, 05 Jan 2024 15:59:12 +
+
ncurses-hexedit (0.9.7+orig-7.2) unstable; urgency=medium
* Non-maintainer upload.
diff -Nru ncurses-hexedit-0.9.7+orig/debian/patches/fix_ncurses_ftbfs.patch
ncurses-hexedit-0.9.7+orig/debian/patches/fix_ncurses_ftbfs.patch
--- ncurses-hexedit-0.9.7+orig/debian/patches/fix_ncurses_ftbfs.patch
1970-01-01 01:00:00.0 +0100
+++ ncurses-hexedit-0.9.7+orig/debian/patches/fix_ncurses_ftbfs.patch
2024-01-05 15:59:12.0 +
@@ -0,0 +1,175 @@
+Description: Stop using fields of opaque _WINDOW struct
+Author: Mate Kukri
+Last-Update: 2024-01-08
+---
+This patch header follows DEP-3: http://dep.debian.net/deps/dep3/
+--- a/src/widgets.c
b/src/widgets.c
+@@ -99,11 +99,11 @@
+ case KEY_LEFT:
+ if (i > 0)
+ {
+- if (win->_curx > x)
++ if (getcurx(win) > x)
+/* not at left hand side */
+{
+ i--;
+- wmove (win, y, win->_curx - 1);
++ wmove (win, y, getcurx(win) - 1);
+}
+else if (i > 0)
+/* left hand side */
+@@ -128,11 +128,11 @@
+ }
+ break;
+ case KEY_RIGHT:
+-if (win->_curx < (x + max - 1))
++if (getcurx(win) < (x + max - 1))
+ /* not at right hand side */
+ {
+i++;
+- wmove (win, y, win->_curx + 1);
++ wmove (win, y, getcurx(win) + 1);
+ }
+ else if (i < len - 1)
+ /* right hand side */
+@@ -163,7 +163,7 @@
+ #endif
+ if (i > 0)
+ {
+- if (win->_curx > x)
++ if (getcurx(win) > x)
+/* not at left hand side */
+{
+ i--;
+@@ -172,7 +172,7 @@
+ for (n = i; n < len; n++)
+ *(str + n) = *(str + n + 1);
+ *(str + n) = 0;
+- oldx = win->_curx;
++ oldx = getcurx(win);
+ wmove (win, y, x);
+ for (n = left; n <= right; n++)
+ {
+@@ -209,8 +209,8 @@
+do_beep ();
+ break;
+ case SPACEBAR:
+-oldx = win->_curx;
+-if ((win->_curx < x + max - 1)
++oldx = getcurx(win);
++if ((getcurx(win) < x + max - 1)
+ && (i < len - 1) && (*(str + len - 1) <= ' '))
+ {
+for (n = len - 1; n > i; n--)
+@@ -230,7 +230,7 @@
+}
+wmove (win, y, oldx + 1);
+ }
+-else if ((win->_curx == x + max - 1)
++else if ((getcurx(win) == x + max - 1)
+ && (i < len - 1) && (*(str + len - 1) <= ' '))
+ {
+for (n = len - 1; n > i; n--)
+@@ -255,7 +255,7 @@
+}
+wmove (win, y, x + max - 1);
+ }
+-else if ((win->_curx == x + max - 1)
++else if ((getcurx(win) == x + max - 1)
+ && (i == len - 1))
+ {
+*(str + len - 1) = ' ';
+@@ -285,12 +285,12 @@
+ default: /* normal input */
+ if (isprintable (in))
+ {
+- if (win->_curx != (x + max - 1))
++ if (getcurx(win) != (x + max - 1))
+/* not at right hand side */
+{
+ *(str + i) = in;
+ i++;
+- oldx = win->_curx;
++ oldx = getcurx(win);
+ wmove (win, y, x);
+ for (n = left; n <= right; n++)
+ {
+--- a/src/file.c
b/src/file.c
+@@ -644,7 +644,7 @@
+ wprintw (Globals.wmain, "%s", trunc_file);
+ fp = fp->p;
+
+- for (result = Globals.wmain->_curx; result < COLS; result++)
++ for (result = getcurx(Globals.wmain); result < COLS; result++)
+ wprintw (Globals.wmain, " ");
+}
+
+--- a/src/misc.c
b/src/misc.c
+@@ -641,10 +641,8 @@
+if (!newlines)
+ die_horribly (NOT_ENOUGH_MEMORY, NULL);
+
+- Globals.wmain->_cury = cursor_y - 1;
+- Globals.wmain->_curx =
Bug#1057930: cunit: diff for NMU version 2.1-3-dfsg-2.7
Control: tags 1057930 + pending
--
Dear maintainer,
I've prepared an NMU for cunit (versioned as 2.1-3-dfsg-2.7) and
uploaded it to DELAYED/5. Please feel free to tell me if I
should delay it longer.
--
Regards
Sudip
diff -Nru cunit-2.1-3-dfsg/debian/changelog cunit-2.1-3-dfsg/debian/changelog
--- cunit-2.1-3-dfsg/debian/changelog 2023-04-01 07:01:17.0 +0100
+++ cunit-2.1-3-dfsg/debian/changelog 2024-01-11 16:36:37.0 +
@@ -1,3 +1,17 @@
+cunit (2.1-3-dfsg-2.7) unstable; urgency=medium
+
+ * Non-maintainer upload.
+
+ [ Mate Kukri ]
+ * d/p/curses_ftbfs.patch:
+Fix FTBFS caused by incorrect use of WINDOW. (Closes: #1057930)
+
+ [ Sudip Mukherjee ]
+ * Fixed the patch from Mate Kukri.
+- Thanks to Sven Joachim for pointing out getmaxx and getmaxy.
+
+ -- Sudip Mukherjee Thu, 11 Jan 2024 16:36:37
+
+
cunit (2.1-3-dfsg-2.6) unstable; urgency=medium
* Non-maintainer upload.
diff -Nru cunit-2.1-3-dfsg/debian/patches/curses_ftbfs.patch
cunit-2.1-3-dfsg/debian/patches/curses_ftbfs.patch
--- cunit-2.1-3-dfsg/debian/patches/curses_ftbfs.patch 1970-01-01
01:00:00.0 +0100
+++ cunit-2.1-3-dfsg/debian/patches/curses_ftbfs.patch 2024-01-11
16:36:37.0 +
@@ -0,0 +1,52 @@
+Description: Use getters for accessing fields of opaque type WINDOW in Curses.c
+Author: Mate Kukri
+Last-Update: 2024-01-04
+---
+This patch header follows DEP-3: http://dep.debian.net/deps/dep3/
+--- a/CUnit/Sources/Curses/Curses.c
b/CUnit/Sources/Curses/Curses.c
+@@ -256,10 +256,10 @@
+
+ start_color();
+
+- f_nLeft = application_windows.pMainWin->_begx;
+- f_nTop = application_windows.pMainWin->_begy;
+- f_nWidth = application_windows.pMainWin->_maxx;
+- f_nHeight = application_windows.pMainWin->_maxy;
++ f_nLeft = getbegx(application_windows.pMainWin);
++ f_nTop = getbegy(application_windows.pMainWin);
++ f_nWidth = getmaxx(application_windows.pMainWin) - 1;
++ f_nHeight = getmaxy(application_windows.pMainWin) - 1;
+
+ if (NULL == (application_windows.pTitleWin = newwin(3, f_nWidth, 0, 0))) {
+ goto title_fail;
+@@ -358,10 +358,10 @@
+ {
+ refresh();
+
+- f_nLeft = application_windows.pMainWin->_begx;
+- f_nTop = application_windows.pMainWin->_begy;
+- f_nWidth = application_windows.pMainWin->_maxx;
+- f_nHeight = application_windows.pMainWin->_maxy;
++ f_nLeft = getbegx(application_windows.pMainWin);
++ f_nTop = getbegy(application_windows.pMainWin);
++ f_nWidth = getmaxx(application_windows.pMainWin) - 1;
++ f_nHeight = getmaxy(application_windows.pMainWin) - 1;
+
+ refresh_title_window();
+ refresh_progress_window();
+@@ -907,10 +907,10 @@
+ pPad->uiColumns = uiCols;
+ pPad->uiPadRow = 0;
+ pPad->uiPadCol = 0;
+- pPad->uiWinLeft = application_windows.pDetailsWin->_begx + 1;
+- pPad->uiWinTop = application_windows.pDetailsWin->_begy + 1;
+- pPad->uiWinColumns = application_windows.pDetailsWin->_maxx - 2;
+- pPad->uiWinRows = application_windows.pDetailsWin->_maxy - 2;
++ pPad->uiWinLeft = getbegx(application_windows.pDetailsWin) + 1;
++ pPad->uiWinTop = getbegy(application_windows.pDetailsWin) + 1;
++ pPad->uiWinColumns = getmaxx(application_windows.pDetailsWin) - 3;
++ pPad->uiWinRows = getmaxy(application_windows.pDetailsWin) - 3;
+
+ bStatus = true;
+
diff -Nru cunit-2.1-3-dfsg/debian/patches/series
cunit-2.1-3-dfsg/debian/patches/series
--- cunit-2.1-3-dfsg/debian/patches/series 2023-03-31 14:53:05.0
+0100
+++ cunit-2.1-3-dfsg/debian/patches/series 2024-01-11 16:03:54.0
+
@@ -1,3 +1,4 @@
0003-fix-warnings-in-man.patch
0004-doc-intorduction-fix-links-to-headers-4K-in-size.patch
fix-string-format-errors-with-recent-ncu.patch
+curses_ftbfs.patch
Bug#1058796: pure-ftpd-postgresql unable to connect to PostgreSQL with segfault at 1538
I can confirm that I can reproduce the segfault and can also confirm that the upstream commit at https://github.com/jedisct1/pure-ftpd/commit/c3f0f3c91d86939e6fabf5f65c6c6fc964e6032e has fixed the problem for me. -- Regards Sudip
Bug#1060293: gnome-nettool: Aborts with assert failure: *** stack smashing detected ***
Package: gnome-nettool Version: 42.0-1 Severity: important X-Debbugs-Cc: sudipm.mukher...@gmail.com Dear Maintainer, gnome-nettool crashes with the message "assert failure: *** stack smashing detected ***". Steps to reproduce: 1. Open gnome-nettool 2. Select the lookup tab 3. Enter "codethink.co.uk" in the space for Network address. 4. In the information type dropdown menu select "Any / All Information" 5. Click the "Lookup" button. Note: Other options in the "information type dropdown menu" works without any error. The issue is seen only with "Any / All Information". -- Regards Sudip
Bug#1037606: clog: diff for NMU version 1.3.0-1.1
Control: tags 1037606 + pending Dear maintainer, I've prepared an NMU for clog (versioned as 1.3.0-1.1) and uploaded it to DELAYED/1. Please feel free to tell me if I should delay it longer. Regards. -- Sudip diff -Nru clog-1.3.0/debian/changelog clog-1.3.0/debian/changelog --- clog-1.3.0/debian/changelog 2016-07-07 23:14:04.0 +0100 +++ clog-1.3.0/debian/changelog 2024-01-05 11:40:11.0 + @@ -1,3 +1,11 @@ +clog (1.3.0-1.1) unstable; urgency=medium + + * Non-maintainer upload. + * Fix FTBFS with gcc13 by adding a missing include. (Closes: #1037606) +- Thanks Mate Kukri and Jonathan Bergh. (LP: #2048084) + + -- Sudip Mukherjee Fri, 05 Jan 2024 11:40:11 + + clog (1.3.0-1) unstable; urgency=medium * New upstream release. diff -Nru clog-1.3.0/debian/patches/json2_cstdint_ftbfs.patch clog-1.3.0/debian/patches/json2_cstdint_ftbfs.patch --- clog-1.3.0/debian/patches/json2_cstdint_ftbfs.patch 1970-01-01 01:00:00.0 +0100 +++ clog-1.3.0/debian/patches/json2_cstdint_ftbfs.patch 2024-01-05 11:40:07.0 + @@ -0,0 +1,15 @@ +Description: Fix FTBFS by adding cstdint include to JSON2.h +Author: Mate Kukri +Last-Update: 2024-01-04 +--- + +--- a/src/libshared/src/JSON2.h b/src/libshared/src/JSON2.h +@@ -27,6 +27,7 @@ + #ifndef INCLUDED_JSON2 + #define INCLUDED_JSON2 + ++#include + #include + + class JSON2 diff -Nru clog-1.3.0/debian/patches/series clog-1.3.0/debian/patches/series --- clog-1.3.0/debian/patches/series2016-07-07 23:01:34.0 +0100 +++ clog-1.3.0/debian/patches/series2024-01-05 10:55:20.0 + @@ -1 +1,2 @@ FixManMinusSign.diff +json2_cstdint_ftbfs.patch
Bug#1060003: color-picker segfaults if built with LTO
Package: color-picker Version: 1.0.3-2 Severity: important Tags: upstream patch X-Debbugs-Cc: sudipm.mukher...@gmail.com Dear Maintainer, It was reported in Ubuntu that color-picker ends with a segfault. It was found to be caused by LTO. An upstream issue has been opened and also a fix provided which upstream has now merged. upstream issue at: https://github.com/keshavbhatt/ColorPicker/issues/23 patch at: https://github.com/keshavbhatt/ColorPicker/commit/c8852896071c6f1f8bb6fc9dcb1cedd998cd89e4 It will be great if you can add the upstream patch to Debian package also. -- Regards Sudip
Bug#1059743: Libsail should depend on sail-codecs
On Sun, 31 Dec 2023 at 10:06, Dmitry Baryshev wrote: > > Package: libsail0 > Version: 0.9.0+repack-1 > > Libsail is a high-level API for SAIL codecs. Since sail-codecs is not a > dependency and most likely is not installed, libsail is unusable in this > configuration. > > The fix is to make libsail dependent on sail-codecs of the same version (e.g. > =version). Thanks for the report. I was initially trying to combine the codecs with the library and then later missed adding the dependency. I will upload the fixed package later today. -- Regards Sudip
Bug#1059333: mirage: Please disable LTO
Control: close -1 -- Real issue has been found. There is no need to disable LTO. https://gitlab.com/thomasross/mirage/-/merge_requests/7 -- Regards Sudip
Bug#1059333: mirage: Please disable LTO
Source: mirage Version: 0.11.1-1 Severity: wishlist Tags: patch X-Debbugs-Cc: sudipm.mukher...@gmail.com Dear Maintainer, Please disable LTO for the issue at https://gitlab.com/thomasross/mirage/-/issues/24. The attached patch will disable LTO. -- Regars Sudip diff --git a/debian/rules b/debian/rules index 18bed59..a0d5054 100755 --- a/debian/rules +++ b/debian/rules @@ -5,7 +5,7 @@ export DH_VERBOSE = 1 export PYBUILD_NAME=mirage export PYBUILD_DISABLE=test -export DEB_BUILD_MAINT_OPTIONS = hardening=+all +export DEB_BUILD_MAINT_OPTIONS = hardening=+all optimize=-lto %: dh "$@" --with python3 --buildsystem=pybuild
Bug#1055493: [Emc-developers] Bug#1055493: linuxcnc-uspace, linuxcnc-uspace-dev: both packages ship the manpages
On Wed, 20 Dec 2023 at 01:06, andy pugh wrote: > > On Mon, 18 Dec 2023 at 18:31, Sudip Mukherjee > wrote: > > > > However I haven't so far worked out why the man3 sections are being > > > included in the main package installer. > > > (the commands in man3 are only of interest to developers) > > > > From > > https://sources.debian.org/src/linuxcnc/2.9.1-2/debian/linuxcnc-uspace.manpages/#L2 > > OK, so where does _that_ file come from? I don't see it in our source > repository: > https://github.com/LinuxCNC/linuxcnc-gbp/tree/debian/unstable/debian I dont think you have this file in your source and even your scripts to prepare the source are not adding it. It has been added by "Steffen Moeller " in 2.9.1-2 version and the changelog says it was done to address build failure. You might want to check with him about this. I am attaching the diff between 2.9.1-1 and 2.9.1-2 for your reference. -- Regards Sudip diff --git a/debian/changelog b/debian/changelog index e173d46..f432914 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,3 +1,9 @@ +linuxcnc (2.9.1-2) unstable; urgency=medium + + * Addressed build failure. + + -- Steffen Moeller Sun, 05 Nov 2023 12:59:16 +0100 + linuxcnc (2.9.1-1) unstable; urgency=medium * New upstream version 2.9.1 diff --git a/debian/control b/debian/control index e58c61c..5f25e28 100644 --- a/debian/control +++ b/debian/control @@ -25,7 +25,7 @@ Build-Depends: libgtk2.0-dev, libgtk-3-dev, libmodbus-dev (>= 3.0), -libeditreadline-dev, +libeditreadline-dev | libreadline-dev, libtirpc-dev, libusb-1.0-0-dev, libxmu-dev, diff --git a/debian/linuxcnc-uspace.install b/debian/linuxcnc-uspace.install index d429141..acd44f5 100644 --- a/debian/linuxcnc-uspace.install +++ b/debian/linuxcnc-uspace.install @@ -116,7 +116,7 @@ usr/lib/python3 usr/lib/tcltk usr/share/axis -usr/share/glade3 +usr/share/glade usr/share/gmoccapy usr/share/gscreen usr/share/gtksourceview-2.0 @@ -144,111 +144,111 @@ usr/share/linuxcnc/touchy.glade usr/share/locale -usr/share/man/man1/5axisgui.1 -usr/share/man/man1/axis.1 -usr/share/man/man1/axis-remote.1 -usr/share/man/man1/debuglevel.1 -usr/share/man/man1/elbpcom.1 -usr/share/man/man1/gladevcp.1 -usr/share/man/man1/gladevcp_demo.1 -usr/share/man/man1/gmoccapy.1 -usr/share/man/man1/gremlin_view.1 -usr/share/man/man1/gs2_vfd.1 -usr/share/man/man1/gscreen.1 -usr/share/man/man1/halcmd.1 -usr/share/man/man1/halcmd_twopass.1 -usr/share/man/man1/hal-histogram.1 -usr/share/man/man1/hal_input.1 -usr/share/man/man1/hal_manualtoolchange.1 -usr/share/man/man1/halmeter.1 -usr/share/man/man1/hal_parport.1 -usr/share/man/man1/halreport.1 -usr/share/man/man1/halrmt.1 -usr/share/man/man1/halrun.1 -usr/share/man/man1/halsampler.1 -usr/share/man/man1/halscope.1 -usr/share/man/man1/halshow.1 -usr/share/man/man1/halstreamer.1 -usr/share/man/man1/haltcl.1 -usr/share/man/man1/halui.1 -usr/share/man/man1/hbmgui.1 -usr/share/man/man1/hexagui.1 -usr/share/man/man1/hy_gt_vfd.1 -usr/share/man/man1/hy_vfd.1 -usr/share/man/man1/image-to-gcode.1 -usr/share/man/man1/inivar.1 -usr/share/man/man1/io.1 -usr/share/man/man1/iocontrol.1 -usr/share/man/man1/iov2.1 -usr/share/man/man1/latency-histogram.1 -usr/share/man/man1/latency-plot.1 -usr/share/man/man1/latency-test.1 -usr/share/man/man1/lineardelta.1 -usr/share/man/man1/linuxcnc.1 -usr/share/man/man1/linuxcnc_info.1 -usr/share/man/man1/linuxcnclcd.1 -usr/share/man/man1/linuxcncmkdesktop.1 -usr/share/man/man1/linuxcnc_module_helper.1 -usr/share/man/man1/linuxcncrsh.1 -usr/share/man/man1/linuxcncsvr.1 -usr/share/man/man1/linuxcnctop.1 -usr/share/man/man1/linuxcnc_var.1 -usr/share/man/man1/maho600gui.1 -usr/share/man/man1/max5gui.1 -usr/share/man/man1/mb2hal.1 -usr/share/man/man1/mdi.1 -usr/share/man/man1/mdro.1 -usr/share/man/man1/milltask.1 -usr/share/man/man1/mitsub_vfd.1 -usr/share/man/man1/monitor-xhc-hb04.1 -usr/share/man/man1/motion-logger.1 -usr/share/man/man1/moveoff_gui.1 -usr/share/man/man1/mqtt-publisher.1 -usr/share/man/man1/ngcgui.1 -usr/share/man/man1/panelui.1 -usr/share/man/man1/pi500_vfd.1 -usr/share/man/man1/pmx485.1 -usr/share/man/man1/pmx485-test.1 -usr/share/man/man1/pncconf.1 -usr/share/man/man1/puma560gui.1 -usr/share/man/man1/pumagui.1 -usr/share/man/man1/pyngcgui.1 -usr/share/man/man1/pyui.1 -usr/share/man/man1/pyvcp.1 -usr/share/man/man1/pyvcp_demo.1 -usr/share/man/man1/qtplasmac-cfg2prefs.1 -usr/share/man/man1/qtplasmac-materials.1 -usr/share/man/man1/qtplasmac-plasmac2qt.1 -usr/share/man/man1/qtplasmac-setup.1 -usr/share/man/man1/qtvcp.1 -usr/share/man/man1/rotarydelta.1 -usr/share/man/man1/rs274.1 -usr/share/man/man1/rtapi_app.1 -usr/share/man/man1/scaragui.1 -usr/share/man/man1/schedrmt.1 -usr/share/man/man1/scorbot-er-3.1 -usr/share/man/man1/sendkeys.1 -usr/share/man/man1/shuttle.1 -usr/share/man/man1/sim_pin.1 -usr/share/man/man1/sim-torch.1 -usr/share/man/man1/sim
Bug#1055493: [Emc-developers] Bug#1055493: linuxcnc-uspace, linuxcnc-uspace-dev: both packages ship the manpages
On Tue, Nov 07, 2023 at 11:06:01AM +, andy pugh wrote: > On Tue, 7 Nov 2023 at 10:45, Andreas Beckmann wrote: > > > > Package: linuxcnc-uspace,linuxcnc-uspace-dev > > Version: 2.9.1-2 > > Severity: serious > > User: debian...@lists.debian.org > > Usertags: piuparts > > > > Hi, > > > > during a test with piuparts I noticed your package failed to install > > because it tries to overwrite other packages files: > > I assume that this could be fixed by deleting the last line here: > https://github.com/LinuxCNC/linuxcnc/blob/2.9/debian/linuxcnc-uspace-dev.install > > However I haven't so far worked out why the man3 sections are being > included in the main package installer. > (the commands in man3 are only of interest to developers) >From >https://sources.debian.org/src/linuxcnc/2.9.1-2/debian/linuxcnc-uspace.manpages/#L2 -- Regards Sudip
Bug#1053729: RFP: SAIL image decoding library
Hi Andrius, On Wed, Oct 18, 2023 at 08:38:52AM +0300, Andrius Merkys wrote: > Hi Dmitry, > > On 2023-10-17 16:25, Dmitry Baryshev wrote: > > > Does it produce desired Debian packages? > > > > I've just pushed a couple of fixes to the Debian rules. I'm able to > > build packages on LUbuntu 23.04. Maybe a couple of small fixes are still > > needed to build packages on Debian. So the recommended git sha to use is > > 4705cb4cf96. It's a release candidate and ready to use in client > > applications. > > > OK, makes sense. > > Since this is an image decoding library, my personal opinion is that it > would better fit the scope of Debian Multimedia Team instead of Debian > Science Team. Just wanted to check if you are planning to package this. Its still a RFP so I guess not, but still want to confirm. If you are not packaging this then I can take it up. -- Regards Sudip
Bug#1057540: transition: ace
On Wed, Dec 06, 2023 at 11:22:30AM +0100, Emilio Pozuelo Monfort wrote: > Control: tags -1 confirmed > > On 05/12/2023 22:45, Sudip Mukherjee wrote: > > Package: release.debian.org > > Severity: normal > > User: release.debian@packages.debian.org > > Usertags: transition > > X-Debbugs-Cc: sudipm.mukher...@gmail.com > > Control: affects -1 + src:ace > > > > Hi, > > > > Small transition with only two affected packages: diagnostics, ivtools, > > Both of them builds fine with ace 7.1.2+dfsg-1 in experimental. > > > > The autogenerated ben tracker looks good. Please consider 'ace' for > > transition. > > Thanks in advance. > > Go ahead. Thanks. It has now migrated to Testing. -- Regards Sudip
Bug#1057540: transition: ace
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: transition X-Debbugs-Cc: sudipm.mukher...@gmail.com Control: affects -1 + src:ace Hi, Small transition with only two affected packages: diagnostics, ivtools, Both of them builds fine with ace 7.1.2+dfsg-1 in experimental. The autogenerated ben tracker looks good. Please consider 'ace' for transition. Thanks in advance. -- Regards Sudip
Bug#1057290: bpftool: please build from https://github.com/libbpf/bpftool
Package: bpftool Severity: wishlist X-Debbugs-Cc: sudipm.mukher...@gmail.com, debian-ker...@lists.debian.org, debian-de...@lists.debian.org The official home for bpftool is now the github repo [1] but keeps the kernel as the authoritative source code of bpftool and is developed as part of the bpf-next Linux source tree. The Maintainers have said "Please use this Github repository for building and packaging bpftool" at [2] The announcement was at [3]. imho, packaging it from the github instead of the kernel source will fix three issues: 1. bpftool will use libbpf available in Debian, whereas now it is building a libbpf.a from the development codes of libbpf in the kernel source and using that. 2. The official releases of bpftool is done in the github repo when the bpf maintainers decides the code is ready for a release. But the Debian bpftool package is done from the kernel source and so follows the kernel releases. And as a result, when a new kernel is released which Debian kernel team will then pickup may not have a bpftool release worthy code. For example, bpftool v7.3 was released on 23/11/2023, 3. bpftool package in Debian is from the kernel v6.5.13 and so looking at the source and git commits I can see the that the Debian package is missing 25 commits which is in the bpftool v7.3 release. Do we package bpftool from their github repo independent of the kernel update? Then we will need to remove the bpftool building bits from the Debian kernel source and create a separate package for bpftool. And so, it will be great if kernel team will like to package and maintain it, if not, then I will be happy to do it. Please reject this bug report if you think bpftool should not be done separately and should live inside kernel source package. [1]. https://github.com/libbpf/bpftool [2]. https://github.com/libbpf/bpftool/blob/main/README.md?plain=1#L18 [3]. https://lore.kernel.org/bpf/267a35a6-a045-c025-c2d9-78afbf6fc...@isovalent.com/ -- Regards Sudip
Bug#1056209: ITP: authselect -- Configures authentication and identity sources from supported profiles
Package: wnpp Severity: wishlist Owner: Sudip Mukherjee X-Debbugs-Cc: debian-de...@lists.debian.org, sudipm.mukher...@gmail.com * Package name: authselect Version : 1.4.3 Upstream Contact: Pavel Březina . * URL : https://github.com/authselect/authselect/ * License : GPL-3.0 Programming Lang: C Description : Authselect is a tool to select system authentication and identity sources from a list of supported profiles Authselect is designed to be a replacement for authconfig but it takes a different approach to configure the system. Instead of letting the administrator build the PAM stack with a tool (which may potentially end up with a broken configuration), it would ship several tested stacks (profiles) that solve a use-case and are well tested and supported. At the same time, some obsolete features of authconfig are not supported by authselect. -- Regards Sudip
Bug#1055469: alacarte should depend on python3-cairo
Source: alacarte Version: 3.44.2-1 Severity: important X-Debbugs-Cc: sudipm.mukher...@gmail.com Dear Maintainer, alacarte v3.44.2 onwards needs python3-cairo to execute. 'Alacarte/ItemEditor.py' is doing "import cairo". And if alacarte is installed in any system where python3-cairo is not installed then alacarte fails to run with the error: Traceback (most recent call last): File "/usr/bin/alacarte", line 23, in from Alacarte.MainWindow import main File "/usr/share/alacarte/Alacarte/MainWindow.py", line 37, in from Alacarte.ItemEditor import LauncherEditor, DirectoryEditor File "/usr/share/alacarte/Alacarte/ItemEditor.py", line 19, in import cairo ModuleNotFoundError: No module named 'cairo' -- System Information: Debian Release: 12.2 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 6.1.0-13-amd64 (SMP w/16 CPU threads; PREEMPT) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled -- Regards Sudip
Bug#1052078: smifb2-dkms: module does not build for kernels w/o DRM or I2C
On Sun, 17 Sept 2023 at 08:00, Andreas Beckmann wrote: > > Package: smifb2-dkms > Version: 2.2.3.4.g1828e79-1 > Severity: serious > > Hi, > > the smifb2 module does not build for the -cloud kernel due to missing > I2C symbols and does not build for the armel and s390x kernels due to > missign DRM symbols. > > https://ci.debian.net/packages/s/smifb2/ > > Probably all that is needed is to add > > BUILD_EXCLUSIVE_CONFIG="CONFIG_DRM CONFIG_I2C" Thanks a lot Andreas. I have not used dkms before and I was struggling to find this out. And now that you have mentioned it, I can find it in the man page. -- Regards Sudip
Bug#1043288: ITP: qad -- A simple, REST-API compliant daemon for automated testing
Package: wnpp Severity: wishlist Owner: Sudip Mukherjee X-Debbugs-Cc: debian-de...@lists.debian.org, sudipm.mukher...@gmail.com * Package name: qad Version : 0.0~git20230710.75f9d50 Upstream Contact: James Thomas Scott Clarke * URL : https://gitlab.com/CodethinkLabs/qad/qad/ * License : GPL and MIT Programming Lang: C and Perl Description : A simple, REST-API compliant daemon for automated testing This is a simple, REST-API compliant daemon which makes automated testing on hardware possible by removing the need for physical intervention as Q.A.D allows inputs to be injected via http/https requests. This both eliminates the need to physically interact with the rig and allows for tasks to be carried out entirely automatically. Q.A.D. can also take a screenshot and send it back to invoker. It can be integrated with openQA for automated testing. I use it as part of my $dayjob and will maintain it. -- Regards Sudip
Bug#1028532: copyright fixed
Upstream has fixed the copyright information. -- Regards Sudip
Bug#1028532: license
The license information is not correct, so packaging this for Debian will be postponed until upstream fixes the copyright. An example from https://github.com/teddywlq/smifb2/blob/main/ddk750/ddk750_2d.c: * Copyright (c) 2007 by Silicon Motion, Inc. (SMI) * * All rights are reserved. Reproduction or in part is prohibited * without the written consent of the copyright owner.. -- Regards Sudip
Bug#1035868: unblock: kernelshark/2.2.0-2
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
X-Debbugs-Cc: sudipm.mukher...@gmail.com
Hi,
Please unblock package kernelshark
Its a simple change to rename the links which fixes the RC bug.
[ Reason ]
It fixes the RC bug.
[ Impact ]
User will not be able to use libkshark.
[ Tests ]
manual tests to confirm symlinks are pointing to the correct file.
[ Risks ]
No risk in unblocking it. :)
[ 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 kernelshark/2.2.0-2
--
Regards
Sudip
diff -Nru kernelshark-2.2.0/debian/changelog kernelshark-2.2.0/debian/changelog
--- kernelshark-2.2.0/debian/changelog 2023-02-05 00:47:33.0 +
+++ kernelshark-2.2.0/debian/changelog 2023-05-05 20:37:24.0 +0100
@@ -1,3 +1,9 @@
+kernelshark (2.2.0-2) unstable; urgency=medium
+
+ * Fix symlink names. (Closes: #1035449)
+
+ -- Sudip Mukherjee Fri, 05 May 2023 20:37:24
+0100
+
kernelshark (2.2.0-1) unstable; urgency=medium
* New upstream version 2.2.0
diff -Nru kernelshark-2.2.0/debian/libkshark2.links
kernelshark-2.2.0/debian/libkshark2.links
--- kernelshark-2.2.0/debian/libkshark2.links 2022-04-26 20:16:02.0
+0100
+++ kernelshark-2.2.0/debian/libkshark2.links 2023-05-05 20:05:16.0
+0100
@@ -1,2 +1,2 @@
-usr/lib/${DEB_HOST_MULTIARCH}/libkshark-gui.so.2.0.0
usr/lib/${DEB_HOST_MULTIARCH}/libkshark-gui.so.2
-usr/lib/${DEB_HOST_MULTIARCH}/libkshark-plot.so.2.0.0
usr/lib/${DEB_HOST_MULTIARCH}/libkshark-plot.so.2
+usr/lib/${DEB_HOST_MULTIARCH}/libkshark-gui.so.2.2.0
usr/lib/${DEB_HOST_MULTIARCH}/libkshark-gui.so.2
+usr/lib/${DEB_HOST_MULTIARCH}/libkshark-plot.so.2.2.0
usr/lib/${DEB_HOST_MULTIARCH}/libkshark-plot.so.2
Bug#1033892: stoken: Request to update to v0.93
Source: stoken Version: 0.92-1 Severity: wishlist X-Debbugs-Cc: sudipm.mukher...@gmail.com Dear Maintainer, stoken source is now available at https://github.com/stoken-dev/stoken and upstream has released v0.93 last month. It will be good to have it in Debian. -- Regards Sudip
Bug#1032323: ITP: moulin -- A meta build system capable of building multiple images at once.
Package: wnpp Severity: wishlist Owner: Sudip Mukherjee X-Debbugs-Cc: debian-de...@lists.debian.org, sudipm.mukher...@gmail.com * Package name: moulin Version : 0.0~git20230227.1630f49 Upstream Author : many * URL : https://github.com/xen-troops/moulin * License : Apache Programming Lang: Python Description : A meta build system capable of building multiple images at once. Main purpose of moulin is to build complex images for embedded devices. Imagine that you are running hypervisor (like Xen or KVM) on your device and you want to build multiple VM images with one simple command. moulin is made exactly for this task. As part of my role in Elisa (https://elisa.tech/) I had to use moulin, but being a Debian user I did not like installing moulin from their git. So, this ITP. I can maintain it under the umbrella of Debian Python team. -- Regards Sudip
Bug#1030196: RFP: libzbd Zoned Block device Manipulation library and tools
Control: close -1 -- Hi Tommy, On Wed, Feb 01, 2023 at 12:59:09PM +0900, Tommy McGee wrote: > > Package: wnnp > Severity: wishlist > > * Package name: libzbd > * Version : 2.0.4 > * URL :https://github.com/westerndigitalcorporation/libzbd > * License : GPL > Programming Language: C > Description :libzbd is a library providing functions > simplifying access to zoned block device information and the > execution of zone management operations. libzbd is already in Debian - https://tracker.debian.org/pkg/libzbd -- Regards Sudip
Bug#1030143: buildstream is not compatible with python 3.11
Package: buildstream Version: 1.6.8-1 Severity: grave Tags: upstream Justification: renders package unusable X-Debbugs-Cc: sudipm.mukher...@gmail.com Dear Maintainer, I have been using buildstream v1.6.8 today to build an image and had a failure with flex.bst from freedesktop-sdk. I had a chat with the maintainers, its a known bug and I was pointed to the upstream issue: https://github.com/apache/buildstream/issues/1758 Since Bookworm now has python3.11, that makes buildstream unusable. I will be happy to give any logs needed or to give steps to reproduce. -- Regards Sudip
Bug#1028532: ITP: smifb2 -- SiliconMotion SM750/SM768 Graphics PCI-E DRM Driver
Package: wnpp Severity: wishlist Owner: Sudip Mukherjee X-Debbugs-Cc: debian-de...@lists.debian.org, sudipm.mukher...@gmail.com * Package name: smifb2 Version : 2.2.1 Upstream Author : Teddy Wang * URL : https://github.com/teddywlq/smifb2 * License : GPLv2 Programming Lang: C Description : SiliconMotion SM750/SM768 Graphics PCI-E DRM Driver SM768 is high performance graphics processor which provides dual display channels and supports multiple output interfaces, including HDMI, DisplayPort, DVI, VGA, LVDS and digital interfaces. SM768 has 128-bit graphics engine to accelerate graphics displays and provides color space conversion and scaling features. Display resolution supports up to 4K UHD (3840x2160@30p) or 2K/Full HD@60p. SM768 supports H.264/MJPEG hardware video decoding. . SM750, Dual Display Graphics Chip is a PCI Express 2D multimedia mobile display controller device providing video and 2D capability to the embedded industry in a 265-pin BGA package. SM750 framebuffer driver is available in the mainline kernel but the drm driver is not in the mainline kernel yet. This driver using dkms will be a combined drm driver for SM750 and SM768. The work for upstreaming the drm driver to mainline kernel is ongoing which is the final goal. I can maintain this package. -- Regards Sudip
Bug#1023550: transition: qcustomplot
Hi Filippo,
On Thu, Nov 24, 2022 at 09:59:49PM +0100, Filippo Rusconi wrote:
> Greetings Sebastian,
>
> On Thu, Nov 24, 2022 at 09:05:07PM +0100, Sebastian Ramacher wrote:
> > Hi Filippo
>
> [...]
>
> > > > Thanks! Please go ahead with the transition.
> > >
> > > I just uploaded the package to unstable. I have not closed the bug yet,
> > > waiting
> > > to check that everything goes fine.
> >
> > qcustomplot's autopkgtests are failing. Could you please take a look at
> > them? Thanks
>
> It is weeks that I monitor the salsa stuff, but I do not understand what these
> tests mean. One example (bear with me):
The failures are because cmake could not find the library and so the
variable 'QCustomPlot_LIBRARIES' was empty and so while linking it did not
ask 'ld' to link with libqcustomplot. Please dont ask why.
Try the attached patch which will explicitely ask cmake to find the library
and save it to the variable. It worked in my schroot.
--
Regards
Sudip
diff -Nru qcustomplot-2.1.0+dfsg1/debian/changelog qcustomplot-2.1.0+dfsg1/debian/changelog
--- qcustomplot-2.1.0+dfsg1/debian/changelog 2022-11-25 10:01:09.0 +
+++ qcustomplot-2.1.0+dfsg1/debian/changelog 2022-12-01 17:36:10.0 +
@@ -1,3 +1,10 @@
+qcustomplot (2.1.0+dfsg1-3.1) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Fix autopkgtest.
+
+ -- Sudip Mukherjee Thu, 01 Dec 2022 17:36:10 +
+
qcustomplot (2.1.0+dfsg1-3) unstable; urgency=low
* Fix the autopkgtest by fixing the dependencies of libqcustomplot-dev: when
diff -Nru qcustomplot-2.1.0+dfsg1/debian/tests/buildtest-axis qcustomplot-2.1.0+dfsg1/debian/tests/buildtest-axis
--- qcustomplot-2.1.0+dfsg1/debian/tests/buildtest-axis 2022-11-25 10:01:09.0 +
+++ qcustomplot-2.1.0+dfsg1/debian/tests/buildtest-axis 2022-12-01 16:27:01.0 +
@@ -19,6 +19,7 @@
FIND_PACKAGE(QCustomPlot REQUIRED)
FIND_PACKAGE(Qt5PrintSupport REQUIRED)
+find_library(QCustomPlot_LIBRARIES QCustomPlot REQUIRED)
set(CMAKE_MODULE_PATH "\${CMAKE_CURRENT_SOURCE_DIR}/cMake")
set(CMAKE_AUTOMOC ON)
diff -Nru qcustomplot-2.1.0+dfsg1/debian/tests/buildtest-inter qcustomplot-2.1.0+dfsg1/debian/tests/buildtest-inter
--- qcustomplot-2.1.0+dfsg1/debian/tests/buildtest-inter 2022-11-25 10:01:09.0 +
+++ qcustomplot-2.1.0+dfsg1/debian/tests/buildtest-inter 2022-12-01 17:26:26.0 +
@@ -19,6 +19,7 @@
FIND_PACKAGE(QCustomPlot REQUIRED)
FIND_PACKAGE(Qt5PrintSupport REQUIRED)
+find_library(QCustomPlot_LIBRARIES QCustomPlot REQUIRED)
set(CMAKE_MODULE_PATH "\${CMAKE_CURRENT_SOURCE_DIR}/cMake")
set(CMAKE_AUTOMOC ON)
diff -Nru qcustomplot-2.1.0+dfsg1/debian/tests/buildtest-plot qcustomplot-2.1.0+dfsg1/debian/tests/buildtest-plot
--- qcustomplot-2.1.0+dfsg1/debian/tests/buildtest-plot 2022-11-25 10:01:09.0 +
+++ qcustomplot-2.1.0+dfsg1/debian/tests/buildtest-plot 2022-12-01 17:26:40.0 +
@@ -19,6 +19,7 @@
FIND_PACKAGE(QCustomPlot REQUIRED)
FIND_PACKAGE(Qt5PrintSupport REQUIRED)
+find_library(QCustomPlot_LIBRARIES QCustomPlot REQUIRED)
set(CMAKE_MODULE_PATH "\${CMAKE_CURRENT_SOURCE_DIR}/cMake")
set(CMAKE_AUTOMOC ON)
diff -Nru qcustomplot-2.1.0+dfsg1/debian/tests/buildtest-scroll qcustomplot-2.1.0+dfsg1/debian/tests/buildtest-scroll
--- qcustomplot-2.1.0+dfsg1/debian/tests/buildtest-scroll 2022-11-25 10:01:09.0 +
+++ qcustomplot-2.1.0+dfsg1/debian/tests/buildtest-scroll 2022-12-01 17:26:50.0 +
@@ -19,6 +19,7 @@
FIND_PACKAGE(QCustomPlot REQUIRED)
FIND_PACKAGE(Qt5PrintSupport REQUIRED)
+find_library(QCustomPlot_LIBRARIES QCustomPlot REQUIRED)
set(CMAKE_MODULE_PATH "\${CMAKE_CURRENT_SOURCE_DIR}/cMake")
set(CMAKE_AUTOMOC ON)
diff -Nru qcustomplot-2.1.0+dfsg1/debian/tests/buildtest-text qcustomplot-2.1.0+dfsg1/debian/tests/buildtest-text
--- qcustomplot-2.1.0+dfsg1/debian/tests/buildtest-text 2022-11-25 10:01:09.0 +
+++ qcustomplot-2.1.0+dfsg1/debian/tests/buildtest-text 2022-12-01 17:27:05.0 +
@@ -19,6 +19,7 @@
FIND_PACKAGE(QCustomPlot REQUIRED)
FIND_PACKAGE(Qt5PrintSupport REQUIRED)
+find_library(QCustomPlot_LIBRARIES QCustomPlot REQUIRED)
set(CMAKE_MODULE_PATH "\${CMAKE_CURRENT_SOURCE_DIR}/cMake")
set(CMAKE_AUTOMOC ON)
diff -Nru qcustomplot-2.1.0+dfsg1/debian/tests/control qcustomplot-2.1.0+dfsg1/debian/tests/control
--- qcustomplot-2.1.0+dfsg1/debian/tests/control 2022-11-25 10:01:09.0 +
+++ qcustomplot-2.1.0+dfsg1/debian/tests/control 2022-12-01 17:35:46.0 +
@@ -1,2 +1,3 @@
Tests: buildtest-axis buildtest-inter buildtest-plot buildtest-scroll buildtest-text
Depends: libqcustomplot-dev, build-essential, cmake
+Restrictions: allow-stderr
Bug#1024106: traceshark: QCustomPlot transition
Hi Filippo, On Mon, Nov 14, 2022 at 9:15 PM Filippo Rusconi wrote: > > Source: traceshark > Version: 0.9.12~beta-2 > Severity: serious > Tags: ftbfs > Justification: fails to build from source (but built successfully in the past) I think this should not have "Severity: serious" yet. The qcustomplot transition has not yet started. imho, It will start when Sebastian confirms and its uploaded to unstable and then these are serious severity. -- Regards Sudip
Bug#1018945: transition: libbpf
Hi Sebastian, On Thu, Nov 10, 2022 at 10:01 PM Sebastian Ramacher wrote: > > On 2022-11-06 11:36:16 +, Sudip Mukherjee wrote: > > On Sat, Nov 5, 2022 at 8:14 PM Sebastian Ramacher > > wrote: > > > > > > Control: tags -1 confirmed > > > > > > On 2022-11-05 00:11:07 +, Sudip Mukherjee wrote: > > > > Control: tags -1 - moreinfo > > > > -- > > > > > > > > On Mon, Oct 24, 2022 at 10:22:32PM +0100, Sudip Mukherjee wrote: > > > > > > > > Please consider libbpf for transition. > > > > > > Please go ahead > > > > Thanks. Has been uploaded. > > The autopkgtests of dpdk regressed on amd64: > https://ci.debian.net/data/autopkgtest/testing/amd64/d/dpdk/28081847/log.gz > Could you please take a look? I have seen that, and also noticed that the test was with dpdk from testing which is not rebuilt with libbpf from unstable. So I triggered a new job to see the result of dpdk/unstable with libbpf/unstable. https://ci.debian.net/data/autopkgtest/unstable/amd64/d/dpdk/28109044/log.gz The job you linked uses dpdk/21.11-5+b1 And, the job I triggered uses dpdk/21.11-5+b2 which is the binnmu for libbpf transition. And, the test passed. Not sure if I need to do something for it. -- Regards Sudip
Bug#1018818: bpfcc: FTBFS with libbpf 1.0.0
On Wed, Aug 31, 2022 at 09:50:39AM +0100, Sudip Mukherjee wrote: > Source: bpfcc > Version: 0.24.0+ds-1 > Severity: important > X-Debbugs-Cc: sudipm.mukher...@gmail.com > Tags: ftbfs > Usertags: libbpf1 > > Dear Maintainer, > > bpfcc FTBFS with libbpf 1.0.0 (available in experimental). let me know if you need some help with the code changes for libbpf and I will be happy to help. -- Regards Sudip
Bug#1023555: fastnetmon: FTBFS with libbpf 1.0
On Tue, Nov 8, 2022 at 6:06 PM Pavel Odintsov wrote:
>
> Hello!
>
> I think I have one more question.
>
> For most of the platforms we support libbpf 1.0.1 works fine but I noticed
> issues with Debian 11 and Ubuntu 20 about enum declarations:
Can you please give me the steps to reproduce this enum error. libbpf
1.0.1 is not available in Debian-11, so I built a backport package for
libbpf/1.0.1 and then tried building fastnetmon with the backported
libbpf in a Bullseye chroot. I did not see the enum issue, but I got a
different error:
/<>/src/fastnetmon.cpp: In function ‘int main(int, char**)’:
/<>/src/fastnetmon.cpp:1540:14: error: ‘std::filesystem’
has not been declared
1540 | if (std::filesystem::exists(backtrace_path)) {
| ^~
/<>/src/fastnetmon.cpp:1550:14: error: ‘std::filesystem’
has not been declared
1550 | std::filesystem::remove(backtrace_path);
| ^~
make[3]: *** [CMakeFiles/fastnetmon.dir/build.make:85:
CMakeFiles/fastnetmon.dir/fastnetmon.cpp.o] Error 1
Note: I saw that you have commented on the upstream issue about the
enum problem and noticed you are using "latest C++ compiler (not from
Linux distro) and C++ 2022."
--
Regards
Sudip
Bug#1023555: fastnetmon: FTBFS with libbpf 1.0
On Tue, Nov 8, 2022 at 4:55 PM Pavel Odintsov wrote: > > 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 Thanks. > > 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. lgtm. -- Regards Sudip
Bug#1023555: fastnetmon: FTBFS with libbpf 1.0
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
Bug#1023555: fastnetmon: FTBFS with libbpf 1.0
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. -- Regards Sudip
Bug#1018945: transition: libbpf
On Sat, Nov 5, 2022 at 8:14 PM Sebastian Ramacher wrote: > > Control: tags -1 confirmed > > On 2022-11-05 00:11:07 +, Sudip Mukherjee wrote: > > Control: tags -1 - moreinfo > > -- > > > > On Mon, Oct 24, 2022 at 10:22:32PM +0100, Sudip Mukherjee wrote: > > > As of today only v4l-utils and bpfcc still fails to build with libbpf > > > in experimental. > > > > > > v4l-utils is a key package, I will look into its fix and request the > > > libbpf transition after that. > > > > All the packages except bpfcc (#1018818) now builds fine with libbpf/1.0.1-1 > > from experimental. I can help bpfcc maintainers with the porting to new > > libbpf > > but they have not replied to the bug report or to my mails. > > > > Please consider libbpf for transition. > > Please go ahead Thanks. Has been uploaded. -- Regards Sudip
Bug#1018945: transition: libbpf
Control: tags -1 - moreinfo -- On Mon, Oct 24, 2022 at 10:22:32PM +0100, Sudip Mukherjee wrote: > As of today only v4l-utils and bpfcc still fails to build with libbpf > in experimental. > > v4l-utils is a key package, I will look into its fix and request the > libbpf transition after that. All the packages except bpfcc (#1018818) now builds fine with libbpf/1.0.1-1 from experimental. I can help bpfcc maintainers with the porting to new libbpf but they have not replied to the bug report or to my mails. Please consider libbpf for transition. -- Regards Sudip
Bug#1018915: v4l-utils: FTBFS with libbpf 1.0.0
On Tue, Nov 1, 2022 at 5:19 PM Sean Young wrote: > > Hi Sudip, > > On Sat, Oct 29, 2022 at 11:17:03PM +0100, Sudip Mukherjee wrote: > > Can you please test the attached patch and confirm that it does not break > > any of the functionality. This is the only one now which is blocking me > > from requesting libbbpf transition. > > Looks good, everything is working fine. Thanks for testing. > > Thanks for writing the patch. Before it can be accepted, it should be posted > on linux-me...@vger.kernel.org with a `Signed-off-by:`. If there are no > review comments I can merge it into v4l-utils upstream. I will send it tonight after I am back from $dayjob. -- Regards Sudip
Bug#1018915: v4l-utils: FTBFS with libbpf 1.0.0
On Mon, Oct 31, 2022 at 10:44 AM Gregor Jasny wrote: > > Hi Sudip, > > thanks for working on the patch! > > On 10/30/22 10:43 AM, Sean Young wrote: > > On Sat, Oct 29, 2022 at 11:17:03PM +0100, Sudip Mukherjee wrote: > >>>> Sean, would you be able to port the existing code to libbpf 1.0? I > >>>> noticed > >>>> that the current code already triggers deprecation warnings with libbpf > >>>> 0.8.0. > >>> > >>> This needs porting, I'll add it to my todo list. > >> > >> Can you please test the attached patch and confirm that it does not break > >> any of the functionality. This is the only one now which is blocking me > >> from requesting libbbpf transition. > > > > That looks great, I'll give some good testing. Thanks for writing this > > patch. > > > > The way to get this merged upstream is to send to > > linux-me...@vger.kernel.org > > and then get a review from the wider community. > > Will you handle upstreaming it? Unfortunately, I don't have any Infrared > Receiver hardware, anymore and cannot test it. So I'll wait for an ACK > by Sean before applying it. Sure, I was planning to send it today/tomorrow. > > One thing I miss in the patch is tightening the pkg-config rule to a > minimum required version which provides LIBBPF_OPTS. Proper place would > be here: > > https://git.linuxtv.org/v4l-utils.git/tree/configure.ac#n567 Ok, I might need help for this one. I will first check what will be the minimum libbpf version required for this change. afaik, libbpf/0.8 is ok with these changes. -- Regards Sudip
Bug#1020299: equinox-p2: wrong information in the manifest files
Control: tags -1 patch -- On Mon, Sep 19, 2022 at 03:58:29PM +0100, Sudip Mukherjee wrote: > Source: equinox-p2 > Version: 4.21-1 > Severity: important > X-Debbugs-Cc: sudipm.mukher...@gmail.com > > Dear Maintainer, > > The manifest file of equinox-p2 mentions that it needs bouncycastle > version="1.65.0" but in Debian we have bouncycastle 1.71 and as a result any > eclipse based application is not able to use equinox-p2 and it gives the > errors like: > > org.eclipse.equinox.p2.engine [130] > Unresolved requirement: Import-Package: org.bouncycastle.openpgp; > version="1.65.0" > > org.eclipse.equinox.p2.core [131] > Unresolved requirement: Import-Package: org.bouncycastle.bcpg; > version="1.65.0" The attached patch is the minimum required to unblock eclipse-tracecompass. But Emmanuel Bourg did not agree so I am not doing an upload but keeping the patch here for record. Ref: https://lists.debian.org/debian-java/2022/09/msg2.html -- Regards Sudip diff -Nru equinox-p2-4.21/debian/changelog equinox-p2-4.21/debian/changelog --- equinox-p2-4.21/debian/changelog 2021-10-18 15:14:21.0 +0100 +++ equinox-p2-4.21/debian/changelog 2022-09-07 21:02:34.0 +0100 @@ -1,3 +1,10 @@ +equinox-p2 (4.21-1.1) UNRELEASED; urgency=medium + + * Team upload. + * Fix Manifest. (Closes: #1020299) + + -- Sudip Mukherjee Wed, 07 Sep 2022 21:02:34 +0100 + equinox-p2 (4.21-1) unstable; urgency=medium * New upstream release diff -Nru equinox-p2-4.21/debian/patches/manifest.patch equinox-p2-4.21/debian/patches/manifest.patch --- equinox-p2-4.21/debian/patches/manifest.patch 1970-01-01 01:00:00.0 +0100 +++ equinox-p2-4.21/debian/patches/manifest.patch 2022-09-07 21:02:34.0 +0100 @@ -0,0 +1,73 @@ +Description: Fix Manifest + +Author: Sudip Mukherjee + +--- + +Bug-Debian: https://bugs.debian.org/1020299 +Forwarded: no + +--- equinox-p2-4.21.orig/bundles/org.eclipse.equinox.p2.artifact.repository/META-INF/MANIFEST.MF equinox-p2-4.21/bundles/org.eclipse.equinox.p2.artifact.repository/META-INF/MANIFEST.MF +@@ -38,14 +38,14 @@ Require-Bundle: org.eclipse.equinox.comm + org.eclipse.equinox.p2.metadata, + org.tukaani.xz;bundle-version="1.3.0" + Import-Package: javax.xml.parsers, +- org.bouncycastle.bcpg;version="1.65.0", +- org.bouncycastle.jce.provider;version="1.65.1", +- org.bouncycastle.openpgp;version="1.65.0", +- org.bouncycastle.openpgp.bc;version="1.65.0", +- org.bouncycastle.openpgp.jcajce;version="1.65.0", +- org.bouncycastle.openpgp.operator;version="1.65.0", +- org.bouncycastle.openpgp.operator.bc;version="1.65.0", +- org.bouncycastle.openpgp.operator.jcajce;version="1.65.0", ++ org.bouncycastle.bcpg;version="1.71.0", ++ org.bouncycastle.jce.provider;version="1.71.0", ++ org.bouncycastle.openpgp;version="1.71.0", ++ org.bouncycastle.openpgp.bc;version="1.71.0", ++ org.bouncycastle.openpgp.jcajce;version="1.71.0", ++ org.bouncycastle.openpgp.operator;version="1.71.0", ++ org.bouncycastle.openpgp.operator.bc;version="1.71.0", ++ org.bouncycastle.openpgp.operator.jcajce;version="1.71.0", + org.eclipse.core.runtime.jobs, + org.eclipse.equinox.internal.p2.core.helpers, + org.eclipse.equinox.internal.p2.jarprocessor, +--- equinox-p2-4.21.orig/bundles/org.eclipse.equinox.p2.core/META-INF/MANIFEST.MF equinox-p2-4.21/bundles/org.eclipse.equinox.p2.core/META-INF/MANIFEST.MF +@@ -70,8 +70,8 @@ Require-Bundle: org.eclipse.equinox.comm + Bundle-RequiredExecutionEnvironment: JavaSE-11 + Bundle-ActivationPolicy: lazy + Service-Component: OSGI-INF/eventBus.xml, OSGI-INF/agentProvider.xml +-Import-Package: org.bouncycastle.bcpg;version="1.65.0", +- org.bouncycastle.openpgp;version="1.65.0", ++Import-Package: org.bouncycastle.bcpg;version="1.71.0", ++ org.bouncycastle.openpgp;version="1.71.0", + org.eclipse.osgi.framework.eventmgr;version="1.2.0", + org.eclipse.osgi.framework.log;version="1.0.0", + org.eclipse.osgi.service.debug;version="1.0.0", +--- equinox-p2-4.21.orig/bundles/org.eclipse.equinox.p2.engine/META-INF/MANIFEST.MF equinox-p2-4.21/bundles/org.eclipse.equinox.p2.engine/META-INF/MANIFEST.MF +@@ -26,7 +26,7 @@ Bundle-RequiredExecutionEnvironment: Jav + Bundle-ActivationPolicy: lazy + Service-Component: OSGI-INF/profileRegistry.xml, OSGI-INF/engine.xml + Import-Package: javax.xml.parsers, +- org.bouncycastle.openpgp;version="1.65.0", ++ org.bouncycastle.openpgp;version="1.71.0", + org.eclipse.core.internal.preferences, + org.eclipse.core.runtime.preferences, + org.eclipse.equinox.internal.p2.artifact.processors.pgp, +--- equinox-p2-4.21.orig/bundles/org.eclipse.equinox.p2.ui/META-INF
Bug#1019488: bouncycastle: incomplete information in the manifest files
Control: tags -1 patch -- On Sat, Sep 10, 2022 at 01:09:06PM +0100, Sudip Mukherjee wrote: > Source: bouncycastle > Version: 1.71-1 > Severity: important > X-Debbugs-Cc: sudipm.mukher...@gmail.com > > Dear Maintainer, > > The META-INF/MANIFEST.MF file of libbcpg-java contains only the following: > > > Which is incomplete and does not contain all the other required information > like Bundle-Version, Bundle-Name, Export-Package etc. And this lack of > information > makes the package unusable when using a SimpleConfigurator based bundles.info > file. The attached patch is the minimum required to unblock eclipse-tracecompass. But Emmanuel Bourg did not agree so I am not doing an upload but keeping the patch here for record. Ref: https://lists.debian.org/debian-java/2022/09/msg2.html -- Regards Sudip diff -Nru bouncycastle-1.71/debian/changelog bouncycastle-1.71/debian/changelog --- bouncycastle-1.71/debian/changelog 2022-05-03 18:51:47.0 +0100 +++ bouncycastle-1.71/debian/changelog 2022-09-19 12:20:40.0 +0100 @@ -1,3 +1,10 @@ +bouncycastle (1.71-2) UNRELEASED; urgency=medium + + * Team upload. + * Fix Manifest. (Closes: #1019488) + + -- Sudip Mukherjee Mon, 19 Sep 2022 12:20:40 +0100 + bouncycastle (1.71-1) unstable; urgency=medium * New upstream release diff -Nru bouncycastle-1.71/debian/patches/manifest.patch bouncycastle-1.71/debian/patches/manifest.patch --- bouncycastle-1.71/debian/patches/manifest.patch 1970-01-01 01:00:00.0 +0100 +++ bouncycastle-1.71/debian/patches/manifest.patch 2022-09-19 12:20:40.0 +0100 @@ -0,0 +1,31 @@ +Description: Fix manifest + +Author: Sudip Mukherjee + +--- +Bug-Debian: https://bugs.debian.org/1019488 +Forwarded: no + +--- bouncycastle-1.71.orig/ant/bc+-build.xml bouncycastle-1.71/ant/bc+-build.xml +@@ -414,6 +414,10 @@ + + + ++ ++ ++ ++ + + + +@@ -882,6 +886,9 @@ + + + ++ ++ ++ + + + diff -Nru bouncycastle-1.71/debian/patches/series bouncycastle-1.71/debian/patches/series --- bouncycastle-1.71/debian/patches/series 2022-05-03 10:10:16.0 +0100 +++ bouncycastle-1.71/debian/patches/series 2022-09-19 12:20:40.0 +0100 @@ -1,3 +1,4 @@ 02_index.patch fix-encoding.patch backward-compatibility.patch +manifest.patch
Bug#1020298: eclipse-platform-runtime: wrong information in the manifest files
Control: tags -1 patch -- On Mon, Sep 19, 2022 at 03:55:54PM +0100, Sudip Mukherjee wrote: > Source: eclipse-platform-runtime > Version: 4.19-1 > Severity: important > X-Debbugs-Cc: sudipm.mukher...@gmail.com > > Dear Maintainer, > > eclipse-platform-runtime needs javax.annotation.PostConstruct and > javax.annotation.PreDestroy and the MANIFEST.MF file mentions: > > Import-Package: javax.annotation;version="1.3.5" and also mentions > javax.annotation;bundle-version="[1.3.5,2.0.0)" in Require-Bundle. The attached patch is the minimum required to unblock eclipse-tracecompass. But Emmanuel Bourg did not agree so I am not doing an upload but keeping the patch here for record. Ref: https://lists.debian.org/debian-java/2022/09/msg2.html -- Regards Sudip diff -Nru eclipse-platform-runtime-4.19/debian/changelog eclipse-platform-runtime-4.19/debian/changelog --- eclipse-platform-runtime-4.19/debian/changelog 2021-10-09 15:47:19.0 +0100 +++ eclipse-platform-runtime-4.19/debian/changelog 2022-05-27 23:58:33.0 +0100 @@ -1,3 +1,10 @@ +eclipse-platform-runtime (4.19-1.1) UNRELEASED; urgency=medium + + * Team upload. + * Fix manifest information. (Closes: #1020298) + + -- Sudip Mukherjee Fri, 27 May 2022 23:58:33 +0100 + eclipse-platform-runtime (4.19-1) unstable; urgency=medium * New upstream release diff -Nru eclipse-platform-runtime-4.19/debian/patches/manifest.patch eclipse-platform-runtime-4.19/debian/patches/manifest.patch --- eclipse-platform-runtime-4.19/debian/patches/manifest.patch 1970-01-01 01:00:00.0 +0100 +++ eclipse-platform-runtime-4.19/debian/patches/manifest.patch 2022-05-27 23:58:33.0 +0100 @@ -0,0 +1,47 @@ +Description: Fix Manifest + +Author: Sudip Mukherjee + +--- + +Bug-Debian: https://bugs.debian.org/1020298 +Forwarded: no + +--- eclipse-platform-runtime-4.19.orig/bundles/org.eclipse.e4.core.di.extensions.supplier/META-INF/MANIFEST.MF eclipse-platform-runtime-4.19/bundles/org.eclipse.e4.core.di.extensions.supplier/META-INF/MANIFEST.MF +@@ -17,7 +17,7 @@ Import-Package: org.eclipse.core.runtime + org.osgi.service.component.annotations;version="1.3.0";resolution:=optional, + org.osgi.service.event;version="1.3.0", + org.osgi.service.log;version="1.3.0", +- javax.annotation;version="1.3.5" ++ javax.annotation;version="[1.3,1.3.5]" + Service-Component: OSGI-INF/org.eclipse.e4.core.di.internal.extensions.OSGiObjectSupplier.xml, + OSGI-INF/org.eclipse.e4.core.di.internal.extensions.EventObjectSupplier.xml, + OSGI-INF/org.eclipse.e4.core.di.internal.extensions.PreferencesObjectSupplier.xml, +--- eclipse-platform-runtime-4.19.orig/bundles/org.eclipse.e4.core.di/META-INF/MANIFEST.MF eclipse-platform-runtime-4.19/bundles/org.eclipse.e4.core.di/META-INF/MANIFEST.MF +@@ -12,10 +12,10 @@ Export-Package: org.eclipse.e4.core.di;v + org.eclipse.e4.core.internal.di;x-friends:="org.eclipse.e4.core.contexts", + org.eclipse.e4.core.internal.di.osgi;x-internal:=true, + org.eclipse.e4.core.internal.di.shared;x-friends:="org.eclipse.e4.core.contexts,org.eclipse.e4.core.di.extensions.supplier" +-Require-Bundle: org.eclipse.e4.core.di.annotations;bundle-version="[1.4.0,2.0.0)";visibility:=reexport, +- javax.annotation;bundle-version="[1.3.5,2.0.0)" ++Require-Bundle: org.eclipse.e4.core.di.annotations;bundle-version="[1.4.0,2.0.0)";visibility:=reexport + Import-Package: javax.inject;version="1.0.0", + org.eclipse.osgi.framework.log;version="1.1.0", + org.osgi.framework;version="1.8.0", +- org.osgi.util.tracker;version="1.5.1" ++ org.osgi.util.tracker;version="1.5.1", ++ javax.annotation;version="[1.3,1.3.5]" + Automatic-Module-Name: org.eclipse.e4.core.di +--- eclipse-platform-runtime-4.19.orig/bundles/org.eclipse.e4.core.services/META-INF/MANIFEST.MF eclipse-platform-runtime-4.19/bundles/org.eclipse.e4.core.services/META-INF/MANIFEST.MF +@@ -7,7 +7,7 @@ Bundle-Localization: plugin + Bundle-Version: 2.2.600.qualifier + Bundle-ActivationPolicy: lazy + Bundle-RequiredExecutionEnvironment: JavaSE-1.8 +-Import-Package: javax.annotation;version="1.3.5", ++Import-Package: javax.annotation;version="[1.3,1.3.5]", + javax.inject;version="1.0.0", + org.eclipse.osgi.service.debug;version="1.1.0", + org.eclipse.osgi.service.localization;version="1.1.0", diff -Nru eclipse-platform-runtime-4.19/debian/patches/series eclipse-platform-runtime-4.19/debian/patches/series --- eclipse-platform-runtime-4.19/debian/patches/series 1970-01-01 01:00:00.0 +0100 +++ eclipse-platform-runtime-4.19/debian/patches/series 2022-05-27 23:58:33.0 +0100 @@ -0,0 +1 @@ +manifest.patch
Bug#1018915: v4l-utils: FTBFS with libbpf 1.0.0
Control: tags -1 patch
--
Hi Sean, Gregor,
On Wed, Sep 14, 2022 at 05:29:57PM +0100, Sean Young wrote:
> Hi Gregor,
>
> On Wed, Sep 07, 2022 at 02:53:49PM +0200, Gregor Jasny wrote:
> > Hello Sudip,
> >
> > thanks for the report.
> >
> > On 02.09.22 01:19, Sudip Mukherjee wrote:
> > > Package: v4l-utils
> > > Version: 1.22.1-4
> > > Severity: important
> > > Tags: ftbfs
> > > X-Debbugs-Cc: sudipm.mukher...@gmail.com
> > > Usertags: libbpf1
> > >
> > > Dear Maintainer,
> > >
> > > v4l-utils FTBFS with libbpf 1.0.0 (available in experimental).
> > > This is the first error from the build log:
> > >
> >
> > Sean, would you be able to port the existing code to libbpf 1.0? I noticed
> > that the current code already triggers deprecation warnings with libbpf
> > 0.8.0.
>
> This needs porting, I'll add it to my todo list.
Can you please test the attached patch and confirm that it does not break
any of the functionality. This is the only one now which is blocking me
from requesting libbbpf transition.
--
Regards
Sudip
diff -Nru v4l-utils-1.22.1/debian/changelog v4l-utils-1.22.1/debian/changelog
--- v4l-utils-1.22.1/debian/changelog 2022-05-22 14:08:50.0 +0100
+++ v4l-utils-1.22.1/debian/changelog 2022-10-29 11:33:37.0 +0100
@@ -1,3 +1,10 @@
+v4l-utils (1.22.1-4.1) UNRELEASED; urgency=medium
+
+ * Non-maintainer upload.
+ * Port changes for libbpf/1.0.1
+
+ -- Sudip Mukherjee Sat, 29 Oct 2022 11:33:37 +0100
+
v4l-utils (1.22.1-4) unstable; urgency=high
* Bump standards to version 4.6.1.0 (no changes needed)
diff -Nru v4l-utils-1.22.1/debian/patches/libbpf.patch v4l-utils-1.22.1/debian/patches/libbpf.patch
--- v4l-utils-1.22.1/debian/patches/libbpf.patch 1970-01-01 01:00:00.00000 +0100
+++ v4l-utils-1.22.1/debian/patches/libbpf.patch 2022-10-29 11:33:37.0 +0100
@@ -0,0 +1,113 @@
+Description: Changes for libbpf/1.0.1
+
+Author: Sudip Mukherjee
+
+---
+
+Bug-Debian: https://bugs.debian.org/1018915
+Forwarded: no
+
+--- v4l-utils-1.22.1.orig/utils/keytable/bpf_load.c
v4l-utils-1.22.1/utils/keytable/bpf_load.c
+@@ -63,19 +63,16 @@ struct bpf_file {
+
+ static int load_and_attach(int lirc_fd, struct bpf_file *bpf_file, struct bpf_insn *prog, int size)
+ {
+- struct bpf_load_program_attr load_attr;
+- int fd, err;
++ LIBBPF_OPTS(bpf_prog_load_opts, opts);
++ int fd, err, insn_cnt;
+
+- memset(_attr, 0, sizeof(struct bpf_load_program_attr));
++ insn_cnt = size / sizeof(struct bpf_insn);
+
+- load_attr.prog_type = BPF_PROG_TYPE_LIRC_MODE2;
+- load_attr.expected_attach_type = BPF_LIRC_MODE2;
+- load_attr.name = bpf_file->name;
+- load_attr.insns = prog;
+- load_attr.insns_cnt = size / sizeof(struct bpf_insn);
+- load_attr.license = bpf_file->license;
++ opts.expected_attach_type = BPF_LIRC_MODE2;
++ opts.log_buf = bpf_log_buf;
++ opts.log_size = LOG_BUF_SIZE;
+
+- fd = bpf_load_program_xattr(_attr, bpf_log_buf, LOG_BUF_SIZE);
++ fd = bpf_prog_load(BPF_PROG_TYPE_LIRC_MODE2, bpf_file->name, bpf_file->license, prog, insn_cnt, );
+ if (fd < 0) {
+ printf("bpf_load_program() err=%m\n%s", bpf_log_buf);
+ return -1;
+@@ -95,6 +92,9 @@ static int build_raw_map(struct bpf_map_
+ int no_patterns, value_size, fd, key, i;
+ struct raw_entry *e;
+ struct raw_pattern *p;
++ LIBBPF_OPTS(bpf_map_create_opts, opts,
++ .map_flags = map->def.map_flags,
++ );
+
+ no_patterns = 0;
+
+@@ -110,14 +110,13 @@ static int build_raw_map(struct bpf_map_
+
+ value_size = sizeof(struct raw_pattern) + max_length * sizeof(short);
+
+- fd = bpf_create_map_node(map->def.type,
+- map->name,
+- map->def.key_size,
+- value_size,
+- no_patterns,
+- map->def.map_flags,
+- numa_node);
+-
++ opts.numa_node = numa_node;
++ fd = bpf_map_create(map->def.type,
++ map->name,
++ map->def.key_size,
++ value_size,
++ no_patterns,
++ );
+ if (fd < 0) {
+ printf(_("failed to create a map: %d %s\n"),
+ errno, strerror(errno));
+@@ -174,27 +173,34 @@ static int load_maps(struct bpf_file *bp
+
+ if (maps[i].def.type == BPF_MAP_TYPE_ARRAY_OF_MAPS ||
+ maps[i].def.type == BPF_MAP_TYPE_HASH_OF_MAPS) {
+- int inner_map_fd = bpf_file->map_fd[maps[i].def.inner_map_idx];
++ LIBBPF_OPTS(bpf_map_create_opts, opts,
++.inner_map_fd = bpf_file->map_fd[maps[i].def.inner_map_idx],
++.map_flags = maps[i].def.map_flags,
++.numa_node = numa_node,
++ );
+
+- bpf_file->map_fd[i] = bpf_create_map_in_map_node(
++ bpf_file->map_fd[i] = bpf_map_create(
+ maps[i].def.type,
+ maps[i].name,
+ maps[i].def.key_size,
+- inner_map_fd,
++ 4,
+ maps[i].def.max_entries,
+- maps[i].def.map_flags,
+- numa_node);
++ );
+ } el
Bug#1018945: transition: libbpf
As of today only v4l-utils and bpfcc still fails to build with libbpf in experimental. v4l-utils is a key package, I will look into its fix and request the libbpf transition after that. -- Regards Sudip
Bug#1021215: Kind request for backports of libtraceevent and libtracefs
On Mon, Oct 3, 2022 at 11:45 PM Hans van Kranenburg wrote:
>
> Package: src:libtraceevent
> Version: 1:1.1.2-1
>
> Hi maintainer, :)
>
> Linux commit fe4d0d5dde ("rtla/Makefile: Properly handle dependencies")
> helps making the dependency on libtraceevent and libtracefs more
> explicit, so that the users run into less weird problems on the go.
>
> Linux 5.19 is in Debian unstable now, and for the stable-backports
> packages that our kernel team is providing, this means that it will
> FTBFS, unless we either:
> - exclude rtla for bullseye-backports
> - have backports for libtraceevent and libtracefs present
>
> So, the question for you is: Do you want to also provide
> bullseye-backports packages for libtraceevent and libtracefs?
Sure, will do it over this weekend.
--
Regards
Sudip
Bug#1012912: diagnostics: diff for NMU version 0.3.3-12.3
Control: tags 1012912 + patch
Control: tags 1012912 + pending
--
Dear maintainer,
I've prepared an NMU for diagnostics (versioned as 0.3.3-12.3) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should delay it longer.
--
Regards
Sudip
diff -Nru diagnostics-0.3.3/debian/changelog diagnostics-0.3.3/debian/changelog
--- diagnostics-0.3.3/debian/changelog 2022-02-07 18:37:08.0 +
+++ diagnostics-0.3.3/debian/changelog 2022-09-19 21:46:06.0 +0100
@@ -1,3 +1,11 @@
+diagnostics (0.3.3-12.3) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Fix ftbfs with GCC-12. (Closes: #1012912)
+- Thanks Adnan from Codethink for helping with the fix.
+
+ -- Sudip Mukherjee Mon, 19 Sep 2022 21:46:06
+0100
+
diagnostics (0.3.3-12.2) unstable; urgency=medium
* Non-maintainer upload.
diff -Nru diagnostics-0.3.3/debian/patches/fix-ftbfs.patch
diagnostics-0.3.3/debian/patches/fix-ftbfs.patch
--- diagnostics-0.3.3/debian/patches/fix-ftbfs.patch1970-01-01
01:00:00.0 +0100
+++ diagnostics-0.3.3/debian/patches/fix-ftbfs.patch2022-09-19
21:45:20.0 +0100
@@ -0,0 +1,40 @@
+Description: Fix FTBFS with GCC-12.
+ Thanks Adnan for finding out the header file fix.
+
+Author: Sudip Mukherjee
+
+---
+
+Bug-Debian: https://bugs.debian.org/1012912
+Forwarded: no
+
+--- diagnostics-0.3.3.orig/diagnostics/util/marshaling.cpp
diagnostics-0.3.3/diagnostics/util/marshaling.cpp
+@@ -74,13 +74,13 @@ bool read(::std::istream & stream, ::std
+ char * const target_buffer(new char[length]);
+ stream.read(target_buffer,length);
+ if(!stream.good()) {
+- delete target_buffer;
++ delete[] target_buffer;
+ return false;
+ }
+
+ // convert
+ target= ::std::string(target_buffer,length);
+-delete target_buffer;
++delete[] target_buffer;
+ return true;
+ }
+
+--- diagnostics-0.3.3.orig/diagnostics/util/to_string.hpp
diagnostics-0.3.3/diagnostics/util/to_string.hpp
+@@ -45,6 +45,9 @@
+ #define DIAGNOSTICS__UTIL__TO_STRING_HPP__INCLUDE_GUARD
+
+ #include
++#include
++#include
++#include
+
+ // used in the implementation by value
+ #include
diff -Nru diagnostics-0.3.3/debian/patches/series
diagnostics-0.3.3/debian/patches/series
--- diagnostics-0.3.3/debian/patches/series 2022-02-07 17:57:51.0
+
+++ diagnostics-0.3.3/debian/patches/series 2022-09-19 21:45:37.0
+0100
@@ -6,3 +6,4 @@
test-run-cleanup
no-ltdl-convenience.patch
remove-dynamic-exception.patch
+fix-ftbfs.patch
Bug#1020299: equinox-p2: wrong information in the manifest files
Source: equinox-p2 Version: 4.21-1 Severity: important X-Debbugs-Cc: sudipm.mukher...@gmail.com Dear Maintainer, The manifest file of equinox-p2 mentions that it needs bouncycastle version="1.65.0" but in Debian we have bouncycastle 1.71 and as a result any eclipse based application is not able to use equinox-p2 and it gives the errors like: org.eclipse.equinox.p2.engine [130] Unresolved requirement: Import-Package: org.bouncycastle.openpgp; version="1.65.0" org.eclipse.equinox.p2.core [131] Unresolved requirement: Import-Package: org.bouncycastle.bcpg; version="1.65.0" -- Regards Sudip
Bug#1020298: eclipse-platform-runtime: wrong information in the manifest files
Source: eclipse-platform-runtime Version: 4.19-1 Severity: important X-Debbugs-Cc: sudipm.mukher...@gmail.com Dear Maintainer, eclipse-platform-runtime needs javax.annotation.PostConstruct and javax.annotation.PreDestroy and the MANIFEST.MF file mentions: Import-Package: javax.annotation;version="1.3.5" and also mentions javax.annotation;bundle-version="[1.3.5,2.0.0)" in Require-Bundle. But in Debian these are provided by libgeronimo-annotation-1.3-spec-java which has a version of 1.3, also the bundle name of this package is not "javax.annotation", and so as a result any eclipse based application is not able to use eclipse-platform-runtime and gives the error: org.eclipse.e4.core.services [83] Unresolved requirement: Import-Package: javax.annotation; version="1.3.5" org.eclipse.e4.core.di [81] Unresolved requirement: Require-Bundle: javax.annotation; bundle-version="[1.3.5,2.0.0)" org.eclipse.e4.core.services [83] Unresolved requirement: Import-Package: javax.annotation; version="1.3.5" -- Regards Sudip
Bug#1019488: bouncycastle: incomplete information in the manifest files
Source: bouncycastle Version: 1.71-1 Severity: important X-Debbugs-Cc: sudipm.mukher...@gmail.com Dear Maintainer, The META-INF/MANIFEST.MF file of libbcpg-java contains only the following: Manifest-Version: 1.0 Ant-Version: Apache Ant 1.10.12 Application-Library-Allowable-Codebase: * Application-Name: Bouncy Castle OpenPGP API Automatic-Module-Name: org.bouncycastle.pg Caller-Allowable-Codebase: * Class-Path: bcprov.jar Codebase: * Created-By: 11.0.15+10-post-Debian-1 (Debian) Extension-Name: org.bouncycastle.bcpg Implementation-Vendor: BouncyCastle.org Implementation-Vendor-Id: org.bouncycastle Implementation-Version: 1.71.00.0 Permissions: all-permissions Specification-Vendor: BouncyCastle.org Specification-Version: 1.1 Trusted-Library: true Which is incomplete and does not contain all the other required information like Bundle-Version, Bundle-Name, Export-Package etc. And this lack of information makes the package unusable when using a SimpleConfigurator based bundles.info file. But if I see the jar file in the maven repository I can see the manifest file in that contains all the required information. The jar can be found at: https://repo1.maven.org/maven2/org/bouncycastle/bcpg-jdk18on/1.71/bcpg-jdk18on-1.71.jar -- Regards Sudip
Bug#1018906: dwarves: FTBFS with libbpf 1.0.0
On Tue, Sep 6, 2022 at 3:16 PM Domenico Andreoli wrote: > > On Tue, Sep 06, 2022 at 10:47:44AM +0100, Sudip Mukherjee wrote: > > Hi Dom, > > > > On Sun, Sep 4, 2022 at 5:54 PM Domenico Andreoli wrote: > > > > > > On Thu, Sep 01, 2022 at 08:57:21PM +0100, Sudip Mukherjee wrote: > > > > > > > > Dear Maintainer, > > > > > > Hi Sudip, > > > > > > > > > > > dwarves FTBFS with libbpf 1.0.0 (available in experimental). > > > > Hopefully this is the error from the build log: > > > > > > It does look like libbpf has now added a hard dependency on v6.0+ > > kernel even though they said it will have "transparent handling of > > older kernels". > > I have mentioned it in > > https://github.com/libbpf/libbpf/issues/562#issuecomment-1237299951. > > So, we either need to wait for some fix from libbpf upstream or wait > > for the Debian kernel team to update to v6.0 after its released next > > month. > > This already happened in the past, I solved it by adding linux-libc-dev > to dwarves' build depends. > > It's not obvious why this is visible only when building dwarves and > not libbpf itself. I nevertheless think it should be libbpf to depend > on the right linux-libc-dev, not the packages using it. > > What do you think? yes, if libbpf upstream can not fix it then I will need to update libbpf with a dependency like linux-libc-dev (>= 6.0) -- Regards Sudip
Bug#1018906: dwarves: FTBFS with libbpf 1.0.0
Hi Dom, On Sun, Sep 4, 2022 at 5:54 PM Domenico Andreoli wrote: > > On Thu, Sep 01, 2022 at 08:57:21PM +0100, Sudip Mukherjee wrote: > > > > Dear Maintainer, > > Hi Sudip, > > > > > dwarves FTBFS with libbpf 1.0.0 (available in experimental). > > Hopefully this is the error from the build log: > > > > In file included from /home/sudip/test/dwarves-1.23/btf_encoder.c:18: > > /usr/include/bpf/btf.h: In function 'btf_enum64_value': > > /usr/include/bpf/btf.h:496:25: error: invalid use of undefined type 'const > > struct btf_enum64' > > 496 | return ((__u64)e->val_hi32 << 32) | e->val_lo32; > > | ^~ > > /usr/include/bpf/btf.h:496:46: error: invalid use of undefined type 'const > > struct btf_enum64' > > 496 | return ((__u64)e->val_hi32 << 32) | e->val_lo32; > > | ^~ > > Which version of linux-libc-dev are you using? I see that struct > btf_enum64 is introduced only in kernel 6.0, not yet packaged. It does look like libbpf has now added a hard dependency on v6.0+ kernel even though they said it will have "transparent handling of older kernels". I have mentioned it in https://github.com/libbpf/libbpf/issues/562#issuecomment-1237299951. So, we either need to wait for some fix from libbpf upstream or wait for the Debian kernel team to update to v6.0 after its released next month. -- Regards Sudip
Bug#1018945: transition: libbpf
On Fri, Sep 02, 2022 at 11:13:26AM +0100, Sudip Mukherjee wrote: > > The autogenerated ben tracker looks good. Please consider 'libbpf' for > transition. Ok, please dont consider it yet. As mentioned in https://github.com/libbpf/libbpf/issues/562#issuecomment-1237299951 libbpf has now added a hard dependency on v6.0+ kernel. -- Regards Sudip
Bug#1018916: xdp-tools: FTBFS with libbpf 1.0.0
Hi, As discussed at https://github.com/libbpf/libbpf/issues/562#issuecomment-1237392994 v1.2.7 of xdp-tools should fix the build problem. -- Regards Sudip
Bug#1018274: gnome-shell-extension-panel-osd: unmaintained upstream
Hi Simon, On Sun, Aug 28, 2022 at 11:03 AM Simon McVittie wrote: > > Source: gnome-shell-extension-panel-osd > Version: 1.0.50.gc032923-1 > Severity: important > Tags: upstream > User: pkg-gnome-maintain...@lists.alioth.debian.org > Usertags: unmaintained-upstream > > The Gitlab project https://gitlab.com/jenslody/gnome-shell-extension-panel-osd > referred to by this package's Homepage field has been archived, meaning > that it no longer accepts code contributions or issue reports. > > For this extension to have a future, someone (perhaps its Debian maintainer > or perhaps unrelated) will need to fork the project and continue development. Thanks for the bug report. I have asked Fran Diéguez at https://gitlab.com/frandieguez/gnome-shell-extension-panel-osd/-/issues/1 if he wants to maintain it as an upstream, to which I have not replied yet. I will ping him in the issue and maybe mail him again to check. I have also asked a gnome team member (my colleague from $dayjob) if he knows someone who might be interested. I am now waiting to hear back from them. If both my options fail then I will fork the project as you have suggested. -- Regards Sudip
Bug#984256: nextepc: diff for NMU version 0.3.10+nods-4.2
Control: tags 984256 + pending
--
Dear maintainer,
I've prepared an NMU for nextepc (versioned as 0.3.10+nods-4.2) and
uploaded it to DELAYED/5. Please feel free to tell me if I
should delay it longer.
--
Regards
Sudip
diff -Nru nextepc-0.3.10+nods/debian/changelog
nextepc-0.3.10+nods/debian/changelog
--- nextepc-0.3.10+nods/debian/changelog2021-02-06 16:02:21.0
+
+++ nextepc-0.3.10+nods/debian/changelog2022-09-04 00:29:25.0
+0100
@@ -1,3 +1,11 @@
+nextepc (0.3.10+nods-4.2) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Fix ftbfs with GCC-11. (Closes: #984256)
+- Thanks Steve for the patch.
+
+ -- Sudip Mukherjee Sun, 04 Sep 2022 00:29:25
+0100
+
nextepc (0.3.10+nods-4.1) unstable; urgency=medium
* Non-maintainer upload.
diff -Nru nextepc-0.3.10+nods/debian/patches/gcc-11.patch
nextepc-0.3.10+nods/debian/patches/gcc-11.patch
--- nextepc-0.3.10+nods/debian/patches/gcc-11.patch 1970-01-01
01:00:00.0 +0100
+++ nextepc-0.3.10+nods/debian/patches/gcc-11.patch 2022-09-04
00:23:48.0 +0100
@@ -0,0 +1,27 @@
+Description: fix build failure with gcc-11.
+Author: Steve Langasek
+Bug-Debian: https://bugs.debian.org/984256
+Last-Update: 2021-11-18
+
+Index: nextepc-0.3.10+nods/lib/core/test/testatomic.c
+===
+--- nextepc-0.3.10+nods.orig/lib/core/test/testatomic.c
nextepc-0.3.10+nods/lib/core/test/testatomic.c
+@@ -100,7 +100,7 @@
+
+ static void test_casptr_equal_nonnull(abts_case *tc, void *data)
+ {
+-int a, b;
++int a = 0, b = 0;
+ void *target_ptr =
+ void *old_ptr;
+
+@@ -111,7 +111,7 @@
+
+ static void test_casptr_notequal(abts_case *tc, void *data)
+ {
+-int a, b;
++int a = 0, b = 0;
+ void *target_ptr =
+ void *old_ptr;
+
diff -Nru nextepc-0.3.10+nods/debian/patches/series
nextepc-0.3.10+nods/debian/patches/series
--- nextepc-0.3.10+nods/debian/patches/series 2021-01-23 22:35:09.0
+
+++ nextepc-0.3.10+nods/debian/patches/series 2022-09-04 00:23:48.0
+0100
@@ -5,3 +5,4 @@
0005-Set-install-dir-for-freediameter-libs.patch
0006-Fix-big-endian-bug.patch
0007-Patch-deprecated-sys-sysctl.h-problem.patch
+gcc-11.patch
Bug#984298: psensor: diff for NMU version 1.1.5-1.4
Control: tags 984298 + patch Control: tags 984298 + pending -- Dear maintainer, I've prepared an NMU for psensor (versioned as 1.1.5-1.4) and uploaded it to DELAYED/2. Please feel free to tell me if I should delay it longer. -- Regards Sudip diff -Nru psensor-1.1.5/debian/changelog psensor-1.1.5/debian/changelog --- psensor-1.1.5/debian/changelog 2021-02-06 19:50:55.0 + +++ psensor-1.1.5/debian/changelog 2022-09-02 23:33:53.0 +0100 @@ -1,3 +1,10 @@ +psensor (1.1.5-1.4) unstable; urgency=medium + + * Non-maintainer upload. + * Fix FTBFS with gcc-11. (Closes: #984298) + + -- Sudip Mukherjee Fri, 02 Sep 2022 23:33:53 +0100 + psensor (1.1.5-1.3) unstable; urgency=medium * Non-maintainer upload. diff -Nru psensor-1.1.5/debian/patches/fix-ftbfs.patch psensor-1.1.5/debian/patches/fix-ftbfs.patch --- psensor-1.1.5/debian/patches/fix-ftbfs.patch1970-01-01 01:00:00.0 +0100 +++ psensor-1.1.5/debian/patches/fix-ftbfs.patch2022-09-02 23:32:48.0 +0100 @@ -0,0 +1,20 @@ +Description: Fix FTBFS with gcc-11 + Fix the indentation while keeping the logic same as before. + +Author: Sudip Mukherjee +--- + +Bug-Debian: https://bugs.debian.org/984298 +Forwarded: no + +--- psensor-1.1.5.orig/src/lib/pudisks2.c psensor-1.1.5/src/lib/pudisks2.c +@@ -83,7 +83,7 @@ static void smart_update(struct psensor + PROVIDER_NAME, + data->path); + +- data->last_smart_update = t; ++ data->last_smart_update = t; + } + + void udisks2_psensor_list_update(struct psensor **sensors) diff -Nru psensor-1.1.5/debian/patches/series psensor-1.1.5/debian/patches/series --- psensor-1.1.5/debian/patches/series 2021-02-06 19:50:55.0 + +++ psensor-1.1.5/debian/patches/series 2022-09-02 23:33:02.0 +0100 @@ -1,3 +1,4 @@ 0001-Update-rsensor.c-drop-is_error-macro-definition.patch 14.patch ayatana-appindicator.patch +fix-ftbfs.patch
Bug#716386: [Mayhem] Bug report on tetradraw: tetraview crashes with exit status 139
On Fri, Feb 18, 2022 at 03:12:14PM +0100, Rhonda D'Vine wrote:
> Dear Lee,
>
> * Lee Garrett [2022-02-09 18:27:38 CET]:
> > Package: tetradraw
> > Version: 2.0.3-9+b2
> > Followup-For: Bug #716386
> > X-Debbugs-Cc: deb...@rocketjump.eu
> >
> > Hi Rhonda,
> >
> > sorry to grave dig this bug report, but it seems that tetradraw might be
> > broken
> > for a couple of releases now. On bullseye it segfaults with rc 139. A few
> > people
> > in #debian reported the same issue, so it looks like it's 100% reproducible.
> > Since I'd love to make some nice ascii art for my /etc/motd, it would be
> > nice if
> > you could find the time to fix it. Thanks in advance!
>
> You are definitely right on that. I think in one of the bugs there is
> a workaround for the issue: It runs smoothly on a virtual console
> instead of within a terminal in Xorg. So if that's possible, I suggest
> to go that path.
>
> What also works is starting it with TERM=linux. This gives a hint in
> what area the issue may lie. I am unfortunately not a well enough coder
> to dig further into it, but those are the workarounds that I am aware
> of, and might give people a hint on where to look into for fixing this.
I was looking at this and the segfault is from src/term.c, line 205.
The part of the code is:
for(count = 1; count < COLOR_PAIRS; count++) {
init_pair(count, count % COLORS, count / COLORS);
colours[count % COLORS][count / COLORS] = count;
}
Further debugging showed COLOR_PAIRS was 65536, so the value of count can be
65535, and COLORS is defined as 256. So, colours[count % COLORS][count / COLORS]
can become colours[65535 % 256][65535 / 256] which means the max array location
it can try to access of colours[0][255]. But colours is declared as
colours[8][8],
so its trying to access memory locations beyond what has been allocated to it.
The following patch will stop the segfault but I dont know what tetradraw is
supposed
to do to check if it has other impact or not.
--- tetradraw-2.0.3.orig/src/global.h
+++ tetradraw-2.0.3/src/global.h
@@ -5,7 +5,7 @@
extern coordinate td_maxx;
extern coordinate td_maxy;
-extern colour colours[COLOURS][COLOURS];
+extern colour colours[256][256];
extern int remote;
extern int pagecnt;
extern char default_highascii[20][10];
--- tetradraw-2.0.3.orig/src/tetradraw.c
+++ tetradraw-2.0.3/src/tetradraw.c
@@ -45,7 +45,7 @@ void load_options();
coordinate td_maxx = 0;
coordinate td_maxy = 0;
-colour colours[COLOURS][COLOURS];
+colour colours[256][256];
canvas *pages[9] = {
NULL,
NULL,
--- tetradraw-2.0.3.orig/src/tetraview.c
+++ tetradraw-2.0.3/src/tetraview.c
@@ -41,7 +41,7 @@
coordinate td_maxx = 0;
coordinate td_maxy = 0;
-colour colours[COLOURS][COLOURS];
+colour colours[256][256];
int remote = 0;
--
Regards
Sudip
Bug#1018945: transition: libbpf
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: transition X-Debbugs-Cc: sudipm.mukher...@gmail.com Hi, This is the most complicated transition I have ever asked for. Please bear with me. 10 affected packages. Dependency level 2: Fails to build and bug raised with "Severity: important": bpfcc - #1018818 dwarves - #1018906 knot - #1018911 qemu - #1018913 suricata - #1018914 v4l-utils - #1018915 xdp-tools - #1018916 dpdk/21.11-5 - builds fine with libbpf from experimental. iproute2/5.19.0-1 - builds fine with libbpf from experimental. Dependency level 3: bpftrace - could not test as it will also need bpfcc. The autogenerated ben tracker looks good. Please consider 'libbpf' for transition. Thanks in advance. -- Regards Sudip
Bug#1018876: transition: ace
On Thu, Sep 1, 2022 at 10:36 PM Sebastian Ramacher wrote: > > Control: tags -1 confirmed > > On 2022-09-01 10:53:10 +0100, Sudip Mukherjee wrote: > > Package: release.debian.org > > Severity: normal > > User: release.debian@packages.debian.org > > Usertags: transition > > X-Debbugs-Cc: sudipm.mukher...@gmail.com > > > > Hi, > > > > Small transition with only two affected packages: diagnostics, ivtools. > > > > diagnostics already has a FTBFS due to #1012912, so could not test it. > > ivtools builds fine with ace 7.0.8+dfsg-1 version in experimental. > > > > The autogenerated ben tracker looks good. Please consider 'ace' for > > transition. > > Thanks in advance. > > Please go ahead Thanks. Uploaded now. I have a fix for the diagnostics FTBFS also. Do you want me to upload it to DELAYED/1-day queue now or upload after this transition is over? -- Regards Sudip
Bug#1018916: xdp-tools: FTBFS with libbpf 1.0.0
Package: xdp-tools
Version: 1.2.6-2
Severity: important
Tags: ftbfs
X-Debbugs-Cc: sudipm.mukher...@gmail.com
Usertags: libbpf1
Dear Maintainer,
xdp-tools FTBFS with libbpf 1.0.0 (available in experimental).
This is the first error from the build log:
dh_auto_configure
./configure --build=x86_64-linux-gnu --prefix=/usr
--includedir=\${prefix}/include --mandir=\${prefix}/share/man
--infodir=\${prefix}/share/info --sysconfdir=/etc --localstatedir=/var
--disable-option-checking --disable-silent-rules
--libdir=\${prefix}/lib/x86_64-linux-gnu --runstatedir=/run
--disable-maintainer-mode --disable-dependency-tracking
Found clang binary 'clang' with version 14 (from 'Debian clang version
14.0.6-2')
libbpf support: FORCE_SYSTEM_LIBBPF is set, but no usable libbpf found on system
error: In file included from config.TN0geB/libbpftest.c:3:
/usr/include/bpf/btf.h: In function 'btf_enum64_value':
/usr/include/bpf/btf.h:496:25: error: invalid use of undefined type 'const
struct btf_enum64'
496 | return ((__u64)e->val_hi32 << 32) | e->val_lo32;
| ^~
/usr/include/bpf/btf.h:496:46: error: invalid use of undefined type 'const
struct btf_enum64'
496 | return ((__u64)e->val_hi32 << 32) | e->val_lo32;
| ^~
dh_auto_configure: error: ./configure --build=x86_64-linux-gnu --prefix=/usr
--includedir=\${prefix}/include --mandir=\${prefix}/share/man
--infodir=\${prefix}/share/info --sysconfdir=/etc --localstatedir=/var
--disable-option-checking --disable-silent-rules
--libdir=\${prefix}/lib/x86_64-linux-gnu --runstatedir=/run
--disable-maintainer-mode --disable-dependency-tracking returned exit code 1
--
Regards
Sudip
Bug#1018915: v4l-utils: FTBFS with libbpf 1.0.0
Package: v4l-utils Version: 1.22.1-4 Severity: important Tags: ftbfs X-Debbugs-Cc: sudipm.mukher...@gmail.com Usertags: libbpf1 Dear Maintainer, v4l-utils FTBFS with libbpf 1.0.0 (available in experimental). This is the first error from the build log: bpf_load.c: In function 'load_and_attach': bpf_load.c:66:38: error: storage size of 'load_attr' isn't known 66 | struct bpf_load_program_attr load_attr; | ^ bpf_load.c:69:38: error: invalid application of 'sizeof' to incomplete type 'struct bpf_load_program_attr' 69 | memset(_attr, 0, sizeof(struct bpf_load_program_attr)); | ^~ bpf_load.c:78:14: warning: implicit declaration of function 'bpf_load_program_xattr' [-Wimplicit-function-declaration] 78 | fd = bpf_load_program_xattr(_attr, bpf_log_buf, LOG_BUF_SIZE); | ^~ bpf_load.c:66:38: warning: unused variable 'load_attr' [-Wunused-variable] 66 | struct bpf_load_program_attr load_attr; | ^ bpf_load.c: In function 'build_raw_map': bpf_load.c:113:14: warning: implicit declaration of function 'bpf_create_map_node' [-Wimplicit-function-declaration] 113 | fd = bpf_create_map_node(map->def.type, | ^~~ bpf_load.c: In function 'load_maps': bpf_load.c:179:47: warning: implicit declaration of function 'bpf_create_map_in_map_node' [-Wimplicit-function-declaration] 179 | bpf_file->map_fd[i] = bpf_create_map_in_map_node( | ^~ -- Regards Sudip
Bug#1018914: suricata: FTBFS with libbpf 1.0.0
Package: suricata Version: 1:6.0.6-1 Severity: important Tags: ftbfs X-Debbugs-Cc: sudipm.mukher...@gmail.com Usertags: libbpf1 Dear Maintainer, suricata FTBFS with libbpf 1.0.0 (available in experimental). This is the first error from the build log: util-ebpf.c: In function 'EBPFLoadFile': util-ebpf.c:375:17: error: implicit declaration of function 'bpf_program__set_socket_filter'; did you mean 'bpf_program__set_log_level'? [-Werror=implicit-function-declaration] 375 | bpf_program__set_socket_filter(bpfprog); | ^~ | bpf_program__set_log_level util-ebpf.c:377:17: error: implicit declaration of function 'bpf_program__set_xdp'; did you mean 'bpf_program__set_type'? [-Werror=implicit-function-declaration] 377 | bpf_program__set_xdp(bpfprog); | ^~~~ | bpf_program__set_type -- Regards Sudip
Bug#1018913: qemu: FTBFS with libbpf 1.0.0
Package: qemu Version: 1:7.0+dfsg-7 Severity: important Tags: ftbfs X-Debbugs-Cc: sudipm.mukher...@gmail.com Usertags: libbpf1 Dear Maintainer, qemu FTBFS with libbpf 1.0.0 (available in experimental). This is the first error from the build log: FAILED: qemu-system-aarch64 c++ -m64 -mcx16 @qemu-system-aarch64.rsp /usr/bin/ld: libcommon.fa.p/ebpf_ebpf_rss.c.o: in function `ebpf_rss_load': ./b/qemu/../../ebpf/ebpf_rss.c:52: undefined reference to `bpf_program__set_socket_filter' collect2: error: ld returned 1 exit status -- Regards Sudip
Bug#1018911: knot: FTBFS with libbpf 1.0.0
Package: knot Version: 3.2.0-1 Severity: important Tags: ftbfs X-Debbugs-Cc: sudipm.mukher...@gmail.com Usertags: libbpf1 Dear Maintainer, knot FTBFS with libbpf 1.0.0 (available in experimental). Hopefully this is the error from the build log: In file included from libknot/xdp/bpf-user.c:27: ./libknot/xdp/bpf-user.h:28:10: fatal error: bpf/xsk.h: No such file or directory 28 | #include | ^~~ libknot/xdp/eth.c: In function 'knot_eth_xdp_mode': libknot/xdp/eth.c:213:30: error: storage size of 'info' isn't known 213 | struct xdp_link_info info; | ^~~~ libknot/xdp/eth.c:214:19: error: implicit declaration of function 'bpf_get_link_xdp_info' [-Werror=implicit-function-declaration] 214 | int ret = bpf_get_link_xdp_info(if_index, , sizeof(info), 0); | ^ libknot/xdp/eth.c:213:30: warning: unused variable 'info' [-Wunused-variable] 213 | struct xdp_link_info info; | ^~~~ libknot/xdp/eth.c:228:1: warning: control reaches end of non-void function [-Wreturn-type] 228 | } | ^ -- Regards Sudip
