Bug#1018157: wsclean: FTBFS on riscv64 (undefined reference to `__atomic_exchange_1')
Source: wsclean
Version: 3.1-1
Severity: important
Tags: ftbfs patch
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: i...@hack3r.moe
Dear maintainer,
wsclean failed to build on riscv64:
```
[100%] Built target wsclean-shared
/usr/bin/ld: libwsclean.a(msgridderbase.cpp.o): in function
`MSGridderBase::getAvailableMemory(double, double)':
./obj-riscv64-linux-gnu/./gridding/msgridderbase.cpp:300: undefined reference
to `__atomic_exchange_1'
collect2: error: ld returned 1 exit status
make[3]: *** [CMakeFiles/wsclean.dir/build.make:154: wsclean] Error 1
make[3]: Leaving directory '/<>/obj-riscv64-linux-gnu'
make[2]: *** [CMakeFiles/Makefile2:286: CMakeFiles/wsclean.dir/all] Error 2
make[2]: Leaving directory '/<>/obj-riscv64-linux-gnu'
make[1]: *** [Makefile:139: all] Error 2
make[1]: Leaving directory '/<>/obj-riscv64-linux-gnu'
dh_auto_build: error: cd obj-riscv64-linux-gnu && make -j4 "INSTALL=install
--strip-program=true" VERBOSE=1 returned exit code 2
make: *** [debian/rules:10: binary-arch] Error 25
dpkg-buildpackage: error: debian/rules binary-arch subprocess returned exit
status 2
```
Full buildd log:
https://buildd.debian.org/status/fetch.php?pkg=wsclean=riscv64=3.1-1=1653411048=0
Attached is a patch that links libatomic on riscv64 and fixes FTBFS, tested on
my QEMU riscv64 machine. Please let me know if I missed something.
Cheers,
Eric
-- System Information:
Debian Release: bookworm/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 5.18.0-4-amd64 (SMP w/8 CPU threads; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
LANGUAGE=en_US:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Description: Link libatomic against wsclean-lib on riscv64 and fix FTBFS
Author: Eric Long
Last-Update: 2022-08-26
--- a/CMakeLists.txt
+++ b/CMakeLists.txt
@@ -381,6 +381,9 @@
add_library(wsclean-lib STATIC ${WSCLEANFILES})
target_link_libraries(wsclean-lib PRIVATE pybind11::embed ${ALL_LIBRARIES})
+if(${CMAKE_SYSTEM_PROCESSOR} STREQUAL "riscv64")
+target_link_libraries(wsclean-lib PRIVATE -latomic)
+endif()
set_target_properties(wsclean-lib PROPERTIES OUTPUT_NAME wsclean)
set_target_properties(wsclean-lib PROPERTIES SOVERSION ${WSCLEAN_VERSION_SO})
Bug#1018156: nftables: list ruleset shows negative ipv6 address
Package: nftables
Version: 0.9.8-3.1
Severity: normal
X-Debbugs-Cc: r...@homemail.org
Dear Maintainer,
As shown below, I created a file call "junk" that makes a few simple nftables
chains.
When I list the chains, nftables shows what looks like a negative number in the
last one.
I would expect it to show the canonical form of ff00::/8 as given in the
previous line.
This simple example is extracted from a complex script to show the problem
concisely.
root@biden:/srv/nftables# cat junk
#!/usr/sbin/nft -f
flush ruleset
table ip6 whatever {
chain junk {
ip6 saddr ff00::/8 drop
ip6 saddr fe80::/10 drop
ip6 saddr { ff00::/8, fe80::/10 } drop
}
}
root@biden:/srv/nftables# /sbin/nft -f junk
root@biden:/srv/nftables# /sbin/nft list ruleset
table ip6 whatever {
chain junk {
ip6 saddr ff00::/8 drop
ip6 saddr fe80::/10 drop
ip6 saddr { fe80::/10,
ff00::-::::::: } drop
}
}
root@biden:/srv/nftables#
-- System Information:
Debian Release: 11.4
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 5.10.0-16-amd64 (SMP w/16 CPU threads)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.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 nftables depends on:
ii dpkg 1.20.11
ii libc6 2.31-13+deb11u3
ii libedit2 3.1-20191231-2+b1
ii libnftables1 0.9.8-3.1
nftables recommends no packages.
Versions of packages nftables suggests:
pn firewalld
-- Configuration Files:
/etc/nftables.conf changed [not included]
-- no debconf information
Bug#1018098: bullseye-pu: package foxtrotgps/1.2.2+bzr331-1~deb11u1
On Thu, 2022-08-25 at 19:21 +0300, Adrian Bunk wrote: > Paul, please ACK/NAK whether you as maintainer consider this appropriate. Looks good to me, thanks. -- bye, pabs https://wiki.debian.org/PaulWise signature.asc Description: This is a digitally signed message part
Bug#1018004: qt6-tools: does not build and link with system litehtml
Hi Lisandro, It's a good suggestion about doing a MR using Salsa in future, an option that I didn't consider (three years ago I did make a Salsa account for one task with another package, so an MR is possible). There are actually two issues here. A key one is certainly with the missing litehtmlConfig.cmake file, which I did actually mention in the first paragraph of the bug report. So until litehtml is updated it does block this bug being resolved. However, there is another issue with qt6-tools CMake logic causing the CMake configure phase to error out when trying to build with a system litehtml package. Here are the errors (can be confirmed by attempting to build qt6-tools with a version of litehtml that does include litehtmlConfig.cmake): ``` CMake Error at /usr/lib/x86_64-linux-gnu/cmake/Qt6/QtFlagHandlingHelpers.cmake:171 (target_compile_definitions): Cannot specify compile definitions for target "litehtml" which is not built by this project. Call Stack (most recent call first): src/assistant/CMakeLists.txt:34 (qt_internal_set_exceptions_flags) CMake Error at /usr/lib/x86_64-linux-gnu/cmake/Qt6/QtFlagHandlingHelpers.cmake:190 (get_target_property): get_target_property() called with non-existent target "litehtml". Call Stack (most recent call first): src/assistant/CMakeLists.txt:35 (qt_disable_warnings) CMake Error at /usr/lib/x86_64-linux-gnu/cmake/Qt6/QtFlagHandlingHelpers.cmake:190 (get_target_property): get_target_property() called with non-existent target "gumbo". Call Stack (most recent call first): src/assistant/CMakeLists.txt:37 (qt_disable_warnings) ``` These errors cause FTBFS unless src/assistant/CMakeLists.txt in qt6-tools is also patched. In the patch I attached to this bug report is then a proposed patch to include in qt6-tools package. The proposed patch to include in qt6-tools package simply removes the three offending CMake commands that cause the above quoted errors. So it appears to be an upstream bug with CMake logic used by qt6-tools as well (though I haven't filed a bug with Qt directly yet as I first wanted to report it here). It seems that upstream does not properly cater to using a system litehtml library after all. Also a change to the header path for litehtml will be required if a version of litehtml > 0.5 is packaged by the maintainer due to newer litehtml moving headers into a litehtml directory. Thus, the patch that I proposed to include in qt6-tools would also modify this file: src/assistant/qlitehtml/src/container_qpainter_p.h The header path in that file would be changed from litehtml.h to litehtml/litehtml.h as per litehtml > 0.5 source. Therefore it does certainly seem easier just to use the litehtml source included in qt6-tools in the end! However, as litehtml is already packaged in Debian and given that qt6-tools has a BD on liblitehtml-dev that was not actually being used it is indeed a bug (and with both packages, as explained above). At least in terms of the intended outcomes! So that's why I filed the two bug reports.
Bug#1018155: remrun: autopkgtests should declare needs-root
Package: remrun Version: 0.2.1-1 Severity: minor Tags: patch User: ubuntu-de...@lists.ubuntu.com Usertags: origin-ubuntu kinetic ubuntu-patch Hi Peter, As of the latest upload of openssh in Ubuntu, the remrun autopkgtest is failing on armhf. This is because: - Ubuntu uses lxd runners for autopkgtests on armhf (only) - the latest upload of openssh uses socket-based activation, so sshd is not started on installation and /run/sshd is not created - the remrun autopkgtests allow for this by creating /run/sshd on demand, but the autopkgtests are not declared as "Restrictions: needs-root", therefore do not have access to create a directory underneath /run. The attached patch adjusts debian/tests/control to make the autopkgtests more portable. Thanks for considering, -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developer https://www.debian.org/ slanga...@ubuntu.com vor...@debian.org diff -Nru remrun-0.2.1/debian/tests/control remrun-0.2.1/debian/tests/control --- remrun-0.2.1/debian/tests/control 2022-07-13 15:18:37.0 -0700 +++ remrun-0.2.1/debian/tests/control 2022-08-25 16:05:08.0 -0700 @@ -1,9 +1,9 @@ Test-Command: set -e; for py in $(py3versions -i); do printf '\n\n=== %s\n\n' "$py"; env PYTHONPATH="$(pwd)/tests/python" "$py" -B -u -m run_sshd_test -v /usr/bin/remrun; done Depends: @, openssh-client, openssh-server, python3-all, python3-cfg-diag, python3-utf8-locale Features: test-name=upstream-sshd-simple -Restrictions: allow-stderr +Restrictions: allow-stderr, needs-root Test-Command: set -e; for py in $(py3versions -i); do printf '\n\n=== %s\n\n' "$py"; env PYTHONPATH="$(pwd)/tests/python" "$py" -B -u -m run_sshd_test -v -t tests/run-test.sh /usr/bin/remrun; done Depends: @, openssh-client, openssh-server, python3-all, python3-cfg-diag, python3-utf8-locale Features: test-name=upstream-sshd-suite -Restrictions: allow-stderr +Restrictions: allow-stderr, needs-root
Bug#1018140: override: clutter-1.0:oldlibs/optional
On Thu, 25 Aug 2022 at 16:26:21 -0700, Sean Whitton wrote: > On Thu 25 Aug 2022 at 08:50PM +01, Simon McVittie wrote: > > clutter-1.0 is unmaintained upstream (#996690), but has too many > > reverse-dependencies to remove immediately. Please move all of its binary > > packages into oldlibs to make this more obvious. > > Done. Just for next time, please list the binary packages in the > request, as we have to feed the names of each of them to dak. Sorry, reportbug asked me for "either source of [sic] binary package" so I assumed either one was equally useful to the ftp team. Is there a syntax in which the ftp team would prefer to receive override requests for easiest review/copy/paste, so I can ask for reportbug to populate the bug report with that syntax, analogous to how it knows how to compose ben and wanna-build syntax for release team bugs? (Perhaps the ideal thing would be if I could tell reportbug that I want to override "src:clutter-1.0 src:cogl", and it would do the appropriate apt queries to expand that into a list of binary packages ready for the ftp team's use?) smcv
Bug#1018085: hplip fails to setup wired printer HP P 1102w
On Thu 25 Aug 2022 at 08:41:20 -0500, William Melgaard wrote: > Package: hplip > Version: 3.21.2+dfsg1-2 > Severity: normal > X-Debbugs-Cc: piob...@mindspring.com Thank you for your report, William. > Dear Maintainer, > > *** Reporter, please consider answering these questions, where appropriate *** > >* What led up to the situation? > print driver failed after upgrade to bullseye TBH, this issue gives the impression of being a user support issue. >* What exactly did you do (or not do) that was effective (or > ineffective)? > Instlled latest hplip; deleted existing driver and installed printer > HP Laserjet Pro P1102w It hoped by "latest hplip" the version for Debian 11 was installed? >* What was the outcome of this action > The install insists on the installation of a proprietary plugin. > However, attempts to install that plugin from HP CD fails because the > workstation does not have a WiFi port HPLIP does offer the option of > USB vs WiFi connection. However, chosing USB appears ineffectual. The > setup still insists that the plugin is missing. Upstream offen advise the following technique: * Download the plugin for your HPLIP version from https://www.openprinting.org/download/printdriver/auxfiles/HP/plugins/ * Install the plugin with 'sh DOWNLOADED_PLUGIN' >* What outcome did you expect instead? > Successful test print That should be possible with a correct setup. Please give lpstat -t lpinfo -v lpinfo -m | grep p1102w Regards, Brian.
Bug#1018046: libsocket6-perl FTCBFS: does not pass --host to configure
On Wed, 24 Aug 2022 15:20:37 +0200, Helmut Grohne wrote:
> I opted for $Config{archname},
> which happens to be x86_64-linux-gnu-thread-multi on amd64. This is not
> quite what we wanted x86_64-linux-gnu, but reasonably close. It also
> seems to work on armhf. Do you know a better way to acquire the
> architecture name?
I looked a bit at the %Config hash, and found
config_arg11: -Darchname=x86_64-linux-gnu
which comes from
config_args: … -Darchname=x86_64-linux-gnu …
but I have no idea about how to extract this value in a sane way.
I also note that the documentation for Config (3perl) says:
"archname"
From archname.U:
This variable is a short name to characterize the current
architecture. It is used mainly to construct the default
archlib.
but then:
archlib: /usr/lib/x86_64-linux-gnu/perl/5.34
I hope that Niko and Dom have more ideas :)
Cheers,
gregor
--
.''`. https://info.comodo.priv.at -- Debian Developer https://www.debian.org
: :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D 85FA BB3A 6801 8649 AA06
`. `' Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe
`-
signature.asc
Description: Digital Signature
Bug#1018130:
Looks like this is only for a mapping integration (?! Must have been after my time) using the old libchamplain, should just be able to disable that build option.
Bug#1018154: restic: New upstream version 0.14.0
Package: restic Version: 0.13.1-1+b1 Severity: wishlist X-Debbugs-Cc: a.t.chadw...@gmail.com Dear Maintainers, It would be lovely if v0.14.0 could be packaged for Debian. It introduces compression (with a new default repo format), and it adds a few nice performance and efficiency boosts generally: https://restic.net/blog/2022-08-25/restic-0.14.0-released/ > /tmp/restic-0.13.1$ uscan --no-download > uscan: Newest version of restic on remote site is 0.14.0, local version is > 0.13.1 > uscan: => Newer package available from: > => https://github.com/restic/restic/archive/refs/tags/v0.14.0.tar.gz Oddly, https://tracker.debian.org/pkg/restic has not picked it up yet, though. thanks, Andrew
Bug#1018153: nodejs-doc: Home link takes you to root
Package: nodejs-doc Version: 18.7.0+dfsg-1 Severity: normal X-Debbugs-Cc: jrub...@gmail.com Dear Maintainer, Clicking on the Node.js link at the top left of every page brings me to "file:///" rather than "file:///usr/share/doc/nodejs/api/index.html". This is a minor usability issue but seems easily resolvable with a quilt patch. Best Regards, Jonathan Rubenstein -- System Information: Debian Release: bookworm/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') merged-usr: no Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.18.0-4-amd64 (SMP w/12 CPU threads; PREEMPT) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=fi_FI.UTF-8, LC_CTYPE=fi_FI.UTF-8 (charmap=UTF-8), LANGUAGE=fi:en_US:en_GB Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled nodejs-doc depends on no packages. Versions of packages nodejs-doc recommends: ii nodejs 18.7.0+dfsg-1 nodejs-doc suggests no packages. -- debconf-show failed
Bug#967685: GTK 4 support now shipping
The promised librnd update to include GTK 4 support happened, and so when the time comes, we can fairly simply turn off GTK 2 and turn on GTK 4. I see no reason to do that until/unless GTK 2 removal from Debian is actually scheduled, however. Bdale
Bug#1017268: golang-go4: FTBFS
Control: tags -1 + confirmed Control: forwarded -1 https://github.com/go4org/go4/issues/55 This appears to be caused by golang v1.19's changing of its sorting algorithm [1], which isn't the first time that has caused this test to fail [2]. Mathias [1] -- https://go.dev/doc/go1.19#sort [2] -- https://github.com/go4org/go4/issues/22 signature.asc Description: This is a digitally signed message part
Bug#1018152: buster-pu: package pglogical/2.2.1-4+deb10u1
Package: release.debian.org
Severity: normal
Tags: buster
User: release.debian@packages.debian.org
Usertags: pu
X-Debbugs-Cc: Debian PostgreSQL Maintainers
* Add upstream hack to fix FTBFS with the export of AcquireDeletionLock.
(Closes: #962423)
diff -Nru pglogical-2.2.1/debian/changelog pglogical-2.2.1/debian/changelog
--- pglogical-2.2.1/debian/changelog2019-02-12 16:11:05.0 +0200
+++ pglogical-2.2.1/debian/changelog2022-08-26 01:01:19.0 +0300
@@ -1,3 +1,11 @@
+pglogical (2.2.1-4+deb10u1) buster; urgency=medium
+
+ * Non-maintainer upload.
+ * Add upstream hack to fix FTBFS with the export of AcquireDeletionLock.
+(Closes: #962423)
+
+ -- Adrian Bunk Fri, 26 Aug 2022 01:01:19 +0300
+
pglogical (2.2.1-4) unstable; urgency=medium
* Team upload.
diff -Nru
pglogical-2.2.1/debian/patches/0001-Quick-hack-to-compile-with-recent-export-of-AcquireD.patch
pglogical-2.2.1/debian/patches/0001-Quick-hack-to-compile-with-recent-export-of-AcquireD.patch
---
pglogical-2.2.1/debian/patches/0001-Quick-hack-to-compile-with-recent-export-of-AcquireD.patch
1970-01-01 02:00:00.0 +0200
+++
pglogical-2.2.1/debian/patches/0001-Quick-hack-to-compile-with-recent-export-of-AcquireD.patch
2022-08-26 01:00:29.0 +0300
@@ -0,0 +1,108 @@
+From efe3e983a0a17b57da5386550037d809754bda55 Mon Sep 17 00:00:00 2001
+From: Petr Jelinek
+Date: Thu, 7 May 2020 18:15:14 +0200
+Subject: Quick hack to compile with recent export of AcquireDeletionLock
+
+And ReleaseDeletionLock which we implement statically.
+
+Later we'll want to move them to compat, or better, rething the
+pglogical_depedency module completely.
+---
+ pglogical_dependency.c | 24
+ 1 file changed, 12 insertions(+), 12 deletions(-)
+
+diff --git a/pglogical_dependency.c b/pglogical_dependency.c
+index 2dbf616..7c325ae 100644
+--- a/pglogical_dependency.c
b/pglogical_dependency.c
+@@ -227,8 +227,8 @@ static void reportDependentObjects(const ObjectAddresses
*targetObjects,
+ DropBehavior behavior,
+ int msglevel,
+ const ObjectAddress *origObject);
+-static void AcquireDeletionLock(const ObjectAddress *object, int flags);
+-static void ReleaseDeletionLock(const ObjectAddress *object);
++static void PGLAcquireDeletionLock(const ObjectAddress *object, int flags);
++static void PGLReleaseDeletionLock(const ObjectAddress *object);
+ static bool find_expr_references_walker(Node *node,
+
find_expr_references_context *context);
+ static void eliminate_duplicate_dependencies(ObjectAddresses *addrs);
+@@ -492,7 +492,7 @@ findDependentObjects(const ObjectAddress *object,
+ {
+ systable_endscan(scan);
+ /* need to release caller's
lock; see notes below */
+- ReleaseDeletionLock(object);
++ PGLReleaseDeletionLock(object);
+ return;
+ }
+
+@@ -556,8 +556,8 @@ findDependentObjects(const ObjectAddress *object,
+* caller's lock to avoid deadlock against a
concurrent
+* deletion of the owning object.)
+*/
+- ReleaseDeletionLock(object);
+- AcquireDeletionLock(, 0);
++ PGLReleaseDeletionLock(object);
++ PGLAcquireDeletionLock(, 0);
+
+ /*
+* The owning object might have been deleted
while we waited
+@@ -568,7 +568,7 @@ findDependentObjects(const ObjectAddress *object,
+ if (!systable_recheck_tuple(scan, tup))
+ {
+ systable_endscan(scan);
+- ReleaseDeletionLock();
++ PGLReleaseDeletionLock();
+ return;
+ }
+
+@@ -653,7 +653,7 @@ findDependentObjects(const ObjectAddress *object,
+ /*
+* Must lock the dependent object before recursing to it.
+*/
+- AcquireDeletionLock(, 0);
++ PGLAcquireDeletionLock(, 0);
+
+ /*
+* The dependent object might have been deleted while we waited
to
+@@ -665,7 +665,7 @@ findDependentObjects(const ObjectAddress *object,
+ if (!systable_recheck_tuple(scan, tup))
+ {
+ /* release the now-useless lock */
+-
Bug#1018151: buster-pu: package ruby-http-parser.rb/0.6.0-4+deb10u1
Package: release.debian.org
Severity: normal
Tags: buster
User: release.debian@packages.debian.org
Usertags: pu
X-Debbugs-Cc: Debian Ruby Extras Maintainers
* Relax "post identity body world" test to fix FTBFS with the
CVE-2019-15605 fix in http-parser. (Closes: #977750)
diff -Nru ruby-http-parser.rb-0.6.0/debian/changelog
ruby-http-parser.rb-0.6.0/debian/changelog
--- ruby-http-parser.rb-0.6.0/debian/changelog 2017-11-16 00:15:54.0
+0200
+++ ruby-http-parser.rb-0.6.0/debian/changelog 2022-08-25 21:52:11.0
+0300
@@ -1,3 +1,11 @@
+ruby-http-parser.rb (0.6.0-4+deb10u1) buster; urgency=medium
+
+ * Non-maintainer upload.
+ * Relax "post identity body world" test to fix FTBFS with the
+CVE-2019-15605 fix in http-parser. (Closes: #977750)
+
+ -- Adrian Bunk Thu, 25 Aug 2022 21:52:11 +0300
+
ruby-http-parser.rb (0.6.0-4) unstable; urgency=medium
* Team upload
diff -Nru
ruby-http-parser.rb-0.6.0/debian/patches/0007-disable-identity-transfer-encoding-test.patch
ruby-http-parser.rb-0.6.0/debian/patches/0007-disable-identity-transfer-encoding-test.patch
---
ruby-http-parser.rb-0.6.0/debian/patches/0007-disable-identity-transfer-encoding-test.patch
1970-01-01 02:00:00.0 +0200
+++
ruby-http-parser.rb-0.6.0/debian/patches/0007-disable-identity-transfer-encoding-test.patch
2022-08-25 21:51:48.0 +0300
@@ -0,0 +1,21 @@
+Subject: Relax "post identity body world" test
+Author: Christoph Biedl
+Date: 2020-12-20
+Bug: https://github.com/tmm1/http_parser.rb/issues/68
+Bug-Debian: https://bugs.debian.org/977750
+
+Technically, disabling "strict" causes the entire test to be
+skipped. Perhaps some day upstream might implement the lenient
+mode.
+
+--- a/spec/support/requests.json
b/spec/support/requests.json
+@@ -162,7 +162,7 @@
+ "Content-Length": "5"
+ },
+ "body": "World",
+-"strict": true
++"strict": false
+ },
+ {
+ "name": "post - chunked body: all your base are belong to us",
diff -Nru ruby-http-parser.rb-0.6.0/debian/patches/series
ruby-http-parser.rb-0.6.0/debian/patches/series
--- ruby-http-parser.rb-0.6.0/debian/patches/series 2017-11-16
00:15:54.0 +0200
+++ ruby-http-parser.rb-0.6.0/debian/patches/series 2022-08-25
21:52:01.0 +0300
@@ -4,3 +4,4 @@
0004-Do-not-overload-loadpath.patch
0005-tweak-to-support-rspec3.patch
0006-disable-folding-header-test.patch
+0007-disable-identity-transfer-encoding-test.patch
Bug#1018004: qt6-tools: does not build and link with system litehtml
Control: block 1018004 by 1018006 Hi Rob! Thanks a lot for your patch! If possible, next time try to create a MR in https://salsa.debian.org/qt-kde-team/qt6/qt6-tools/ , that makes it much easier for us to review. Now looking at the code the real issue is on litehtml itself. By modifying src/assistant/qlitehtml/src/CMakeLists.txt to make a verbose find_package(): ``` CMake Warning at src/assistant/qlitehtml/src/CMakeLists.txt:15 (find_package): By not providing "Findlitehtml.cmake" in CMAKE_MODULE_PATH this project has asked CMake to find a package configuration file provided by "litehtml", but CMake did not find one. Could not find a package configuration file provided by "litehtml" with any of the following names: litehtmlConfig.cmake litehtml-config.cmake Add the installation prefix of "litehtml" to CMAKE_PREFIX_PATH or set "litehtml_DIR" to a directory containing one of the above files. If "litehtml" provides a separate development package or SDK, be sure it has been installed. ``` Looking at liblitehtml-dev: ``` $ dpkg -L liblitehtml-dev | grep -i cmake /usr/lib/x86_64-linux-gnu/cmake /usr/lib/x86_64-linux-gnu/cmake/litehtml /usr/lib/x86_64-linux-gnu/cmake/litehtml/litehtmlTargets-none.cmake /usr/lib/x86_64-linux-gnu/cmake/litehtml/litehtmlTargets.cmake ``` it is not providing the right CMake files. So the fix really lies on liblitehtml. qttools already has the right code in order to make it work, liblitehtml needs to ship the right cmake files. -- Lisandro Damián Nicanor Pérez Meyer https://perezmeyer.com.ar/
Bug#1018150: dh-python3 crashes on attempting to diff files that are not valid utf-8.
Package: dh python
Version: 5.20220819
I am curently in the process of trying to fix numpy in raspbian bookworm.
Which had become uninstallable due to a dependency on libpython3.9. To
avoid a build-dependency loop, the first step of that process was doing
a build of numpy with nodoc and nocheck
While doing so I ran into the following error.
W: dh_python3 fs:146: Paths differ:
debian/python3-numpy/usr/lib/python3.10/dist-packages/numpy/core/lib/libnpymath.a
and
debian/python3-numpy/usr/lib/python3/dist-packages/numpy/core/lib/libnpymath.a
Traceback (most recent call last):
File "/usr/bin/dh_python3", line 284, in
main()
File "/usr/bin/dh_python3", line 210, in main
fix_locations(package, interpreter, SUPPORTED, options)
File "/usr/share/dh-python/dhpython/fs.py", line 53, in fix_locations
share_files(srcdir, dstdir, interpreter, options)
File "/usr/share/dh-python/dhpython/fs.py", line 127, in share_files
share_files(fpath1, fpath2, interpreter, options)
File "/usr/share/dh-python/dhpython/fs.py", line 127, in share_files
share_files(fpath1, fpath2, interpreter, options)
File "/usr/share/dh-python/dhpython/fs.py", line 127, in share_files
share_files(fpath1, fpath2, interpreter, options)
File "/usr/share/dh-python/dhpython/fs.py", line 149, in share_files
fromlines = fp1.readlines()
File "/usr/lib/python3.10/codecs.py", line 322, in decode
(result, consumed) = self._buffer_decode(data, self.errors, final)
UnicodeDecodeError: 'utf-8' codec can't decode byte 0xd0 in position 75:
invalid continuation byte
Reading the code, this is clearly caused by applying diff code that
assumes text, presumablly in the encoding from the current locale
to arbitrary files, there is already code to exclude .so files from
the diff, but other files will be treated as text causing
dh-python
As a quick fix so I could proceed with what I'm doing I made it also
exclude .a files from the diffing, but throwing a text differ at arbitrary
files of arbitrary size does not seem a great idea to me.
Debdiff for the quick fix is attatched.
diff -Nru dh-python-5.20220819/debian/changelog
dh-python-5.20220819+rpi1/debian/changelog
--- dh-python-5.20220819/debian/changelog 2022-08-19 21:34:55.0
+0100
+++ dh-python-5.20220819+rpi1/debian/changelog 2022-08-25 21:47:15.0
+0100
@@ -1,3 +1,9 @@
+dh-python (5.20220819+rpi1) bookworm-staging; urgency=medium
+
+ * Don't attempt to diff .a files.
+
+ -- Peter Michael Green Thu, 25 Aug 2022 20:47:15
+
+
dh-python (5.20220819) unstable; urgency=medium
* flit plugin: Explicitly install using the "deb_system" sysconfig scheme.
diff -Nru dh-python-5.20220819/dhpython/fs.py
dh-python-5.20220819+rpi1/dhpython/fs.py
--- dh-python-5.20220819/dhpython/fs.py 2022-08-19 21:34:55.0 +0100
+++ dh-python-5.20220819+rpi1/dhpython/fs.py2022-08-25 21:46:56.0
+0100
@@ -144,7 +144,7 @@
else:
# The files differed so we cannot collapse them.
log.warn('Paths differ: %s and %s', fpath1, fpath2)
-if options.verbose and not i.endswith('.so'):
+if options.verbose and not i.endswith('.so') and not
i.endswith('.a'):
with open(fpath1) as fp1:
fromlines = fp1.readlines()
with open(fpath2) as fp2:
Bug#1018146: correct multiarch for blends stuff?
[Helmut Grohne] > debian-edu builds a pile of task packages. I am wondering, why are these > task architecture-dependent? If they were Architecture: all, they would > be irrelevant to cross building and this whole bug would become moot. So > this is a relevant question. I have no answer. The task pacakges started out as arch: all, but as the set of packages available are not identical across all architectures in Debian, this proved not to work well and made it imposible to keep the task packages in testing. -- Happy hacking Petter Reinholdtsen
Bug#1016803: [Pkg-utopia-maintainers] Bug#1016803: Bug#1016803: Generates unusable resolv.conf
Output of "nmcli" as well, please. Is /etc/resolv.conf a real file or a symlink pointing somewhere? Please also post the content of /run/NetworkManager/no-stub-resolv.conf Thanks, Michael OpenPGP_signature Description: OpenPGP digital signature
Bug#1010804: Thanks for the patch
Hello, I just tested your patch and it works. I will upload the new package shortly. Thanks for your work, Mt. signature.asc Description: This is a digitally signed message part
Bug#1018149: O: granite -- extension of GTK3 libraries
Package: wnpp Severity: normal I intend to orphan the granite package. The package is currently in good condition, please check out its status at https://tracker.debian.org/pkg/granite . Maintaining a package requires time and skills. Please only adopt this package if you will have enough time and attention to work on it. If you want to be the new maintainer, please see https://www.debian.org/devel/wnpp/#howto-o for detailed instructions how to adopt a package properly. If you are still uncertain about how to adopt the package, please feel free to let me know or seek help from other Debian Developers. You do not need anyone's permit to take over maintenance of this package. The package description is: Granite-7 is an extension of GTK. Among other things, it provides complex widgets and convenience functions designed for use in apps built for elementary OS. Thanks, Boyuan Yang signature.asc Description: This is a digitally signed message part
Bug#1018147: O: granite-7 -- extension of GTK4 libraries
Package: wnpp Severity: normal I intend to orphan the granite-7 package. The package is currently in good condition, please check out its condition at https://tracker.debian.org/pkg/granite-7 . As a project under elementaryOS umbrella, granite-7 is a GTK4 port of the original granite library. As of Aug 2022, it is not used by any package in Debian repository. Maintaining a package requires time and skills. Please only adopt this package if you will have enough time and attention to work on it. If you want to be the new maintainer, please see https://www.debian.org/devel/wnpp/#howto-o for detailed instructions how to adopt a package properly. If you are still uncertain about how to adopt the package, please feel free to let me know or seek help from other Debian Developers. You do not need anyone's permit to take over maintenance of this package. The package description is: Granite-7 is an extension of GTK4. Among other things, it provides complex widgets and convenience functions designed for use in apps built for elementary OS. Thanks, Boyuan Yang signature.asc Description: This is a digitally signed message part
Bug#1018075: [Tts-project] Bug#1018075: Bug#1018075: Default to espeak-ng-mbrola which has no voice?
Sebastien Bacher, le jeu. 25 août 2022 20:46:52 +0200, a ecrit: > Le 25/08/2022 à 20:38, Samuel Thibault a écrit : > > But when there is no voice available there, it > > won't be working so in that case speech-dispatcher shouldn't even enable > > it, and thus fallback to espeak-ng. I'll have a look at fixing that, > > thanks for the report that at last reached somebody who is actually in > > touch with speech-dispatcher! > > Thanks. Also I was unsure if there is really no voice available or is that > an issue with the mbrola-paths patch which made them not being found? The mbrola-paths actually follows the mbrola packages path, so that's really supposed to be so. Anyway, if anything is wrong with a speechd module, we don't want to let speechd enable it :) Samuel
Bug#1018146: correct multiarch for blends stuff?
Package: src:debian-edu,blends-dev User: debian-cr...@lists.debian.org Usertags: cross-satisfiability debian-edu presently cannot be cross-built from source, because its dependency on blends-dev is not cross-satisfiable. In general, Architecture: all packages cannot satisfy cross Build-Depends unless marked Multi-Arch: foreign (or annotated :native). Before doing the obvious thing, please let us step back. debian-edu builds a pile of task packages. I am wondering, why are these task architecture-dependent? If they were Architecture: all, they would be irrelevant to cross building and this whole bug would become moot. So this is a relevant question. I have no answer. So if the education-* tasks do have to be Arch: any, then they're relevant to cross building. In that case, understanding their architecture-dependence is important to understanding whether we can mark blends-dev Multi-Arch: foreign. Keep in mind that Multi-Arch: foreign is a promise to downstreams that essentially says: This package works the same way regardless which architecture you install it for. I hope you can shed some light on these questions rather than blindly changing some Multi-Arch fields without understanding what they do. Thanks in advance Helmut
Bug#1018145: gst-plugins-bad1.0: Default SoundFont patch is missing
Package: src:gst-plugins-bad1.0 Version: 1.20.3-2 Severity: normal Dear Maintainer, It seems that the patch to set a default SoundFont which was one of the results from bug #929185 [1] has gone missing without mention. Several changelog entries (1.16.0-2, 1.16.0-3, 1.16.1-1 which added the SoundFont patch, 1.16.2-1, 1.16.2-2.2, and 1.16.2-2.3) are also missing in the current package (1.20.3-2) and the changelog entry for 1.16.2-2 is different in the current package than the original. Looking at package versions 1.16.2-2.3 [2] and 1.17.2-1 [3] it appears the patch went missing in the 1.17.2-1 experimental upload, but then never came back again. The patch for a default SoundFont was added with commit 32dbf91 [4] but was no longer present after commit 5cec5ce [5] which was the merge of the experimental branch. Perhaps it would be good to restore this default SoundFont patch that was apparently accidentally dropped in the mentioned merge? Thank you for your work maintaining the GStreamer packages. [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=929185 [2] https://snapshot.debian.org/package/gst-plugins-bad1.0/1.16.2-2.3/ [3] https://snapshot.debian.org/package/gst-plugins-bad1.0/1.17.2-1/ [4] https://salsa.debian.org/gstreamer-team/gst-plugins-bad1.0/-/commit/32dbf91 [5] https://salsa.debian.org/gstreamer-team/gst-plugins-bad1.0/-/commit/5cec5ce
Bug#1018143: confusion regarding mode changes and patch formats
Package: dgit Version: 9.16 Prior to dgit 9.16, dgit would not tolerate (with 3.0 (quilt)) (a) treechanges involving the creation of executable files (b) treechanges involving file executability changes In #949675 it was reported that this made dgit unable to handle an actual package: a version of glibc, as it happens. In response I committed: a0ac573f8359 "dgit: tolerate making quilt patches creating +x files" I evidently at the time thought that the fact that this package actually existed and did this was sufficient to know that all would be well and I could relax the check. So I did so. There was a test case, testing that this was rejected. Foolishly, I just dropped the test. This was because I thought (and indeed I still think) that what is accepted by dpkg-source actually depends on whatever the installed version of diff does. For 1.0, dpkg-source carefully validates diffs to check they have nothing untoward; for 3.0 it delegates completely to diff - leading to uncontrolled introduction of source package features which don't work on older versions of Debian. I must have thought that the test failure was for this reason. However, there is a flaw in this reasoning. The fact that dpkg-source can extract these things (on at least some versions of Debian) does not mean that it can create them. Now that I investigate #995056, I find that it cannot. Empirically, dpkg-source claims that there are no changes to represent. I believe the situation with treechanges (a) (#949675) and (b) #995056 is the same. Looking at the patches in the glibc_2.32-4 source package, I find that debian/patches/git-updates.diff is like this: GIT update of https://sourceware.org/git/glibc.git/release/2.32/master from glibc-2.32 diff --git a/NEWS b/NEWS index 485b8ddffa..2afe250ccf 100644 --- a/NEWS +++ b/NEWS @@ -5,6 +5,25 @@ See the end for copying conditions. ... diff --git a/sysdeps/x86_64/configure b/sysdeps/x86_64/configure old mode 100644 new mode 100755 index 84f82c2406..fc1840e23f Whereas a dpkg-source-generated patch is like this: Description: TODO: Put a short summary on the line above and replace this paragraph ... Author: Ian Jackson --- The information above should follow the Patch Tagging Guidelines, please ... Origin: , Bug: ... Last-Update: 2022-08-25 --- /dev/null +++ example-1.1/newx @@ -0,0 +1 @@ +hi This is a mess. I think it means that dpkg-source cannot rely (solely or mostly) on dpkg-source for constructing debian/patches because the other tools people are using are strictly more powerful - and we need to match their feature set. Relaxing the check in dgit worked for Peter because he didn't need to actually manipulate any of the dpkg-source-unmanipulatable patches. My attempt to introduce a test case for this situation failed because it involved actually creating a new patch. I think the problem is in `quiltify_dpkg_commit`. Maybe the answer is to give up on dpkg-source --commit entirely. The only call sites are in quiltify whichruns in a playtree. Ian. -- Ian JacksonThese opinions are my own. Pronouns: they/he. If I emailed you from @fyvzl.net or @evade.org.uk, that is a private address which bypasses my fierce spamfilter.
Bug#1018144: sssd-ad: Active Directory dynamic DNS updates broken without bind9-dnsutils installed
Package: sssd-ad Version: 2.4.1-2 Severity: normal Dear Maintainer, sssd-ad supports dynamically updating DNS recource records on Active Directory-based authoritative DNS servers after the system has joined their AD domain. To use this feature, a number of dyndns-specific sssd options have to be configured in sssd.conf. I spent close to a day of work finding out what made this mechanism work on one of our hosts, but not another - the root cause was determined to be that the host which had this feature working right away had the bind9-dnsutils package installed, which happens to provide `/usr/bin/nsupdate`. Even if this executable is not present, sssd will willingly let itself be configured with AD-based dyndns updates, but cannot actually perform them. The dyndns update mechanism repeatedly execv()s `nsupdate` if it was found during initialization at src/providers/be_dyndns.c:1188 as per the source package of sssd-ad 2.4.1 in bullseye. I therefore think it's a sound idea to have bind9-dnsutils in either Suggests or Recommends of the sssd-ad package, as an arguably significant portion of its functionality depends on it having been installed. Thanks for your consideration, and the great work on sssd in Debian!
Bug#1018142: override: clutter-gst-3.0:oldlibs/optional
Package: ftp.debian.org Severity: normal User: ftp.debian@packages.debian.org Usertags: override clutter-gst-3.0 is unmaintained upstream, but has too many reverse-dependencies to remove immediately. Please move all of its binary packages into oldlibs to make this more obvious. Thanks, smcv
Bug#1018141: override: clutter-gtk:oldlibs/optional
Package: ftp.debian.org Severity: normal User: ftp.debian@packages.debian.org Usertags: override clutter-gtk is unmaintained upstream (#1018113), but has too many reverse-dependencies to remove immediately. Please move all of its binary packages into oldlibs to make this more obvious. Thanks, smcv
Bug#1018140: override: clutter-1.0:oldlibs/optional
Package: ftp.debian.org Severity: normal User: ftp.debian@packages.debian.org Usertags: override clutter-1.0 is unmaintained upstream (#996690), but has too many reverse-dependencies to remove immediately. Please move all of its binary packages into oldlibs to make this more obvious. Thanks, smcv
Bug#1018004: qt6-tools: does not build and link with system litehtml
For reference the bug filed against src:litehtml related to this is: #1018006 - litehtml: qt6-tools does not build/link with this version https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1018006
Bug#1018139: override: cogl:oldlibs/optional
Package: ftp.debian.org Severity: normal User: ftp.debian@packages.debian.org Usertags: override cogl is unmaintained upstream (#996691), but has too many reverse-dependencies to remove immediately. Please move all of its binary packages into oldlibs to make this more obvious. Thanks, smcv
Bug#1018137: ibus-clutter: depends on unmaintained clutter-1.0 and related libraries
Control: reassign -1 ibus-clutter On Thu, 25 Aug 2022 at 20:33:53 +0100, Simon McVittie wrote: > Source: ibus-clutter > Version: 0.0+git20090728.a936bacf-7 > Severity: important > Tags: bookworm sid upstream > User: pkg-gnome-maintain...@lists.alioth.debian.org > Usertags: oldlibs clutter > Control: block 996690 by -1 > > This package depends on and enhances clutter-1.0, which is no longer > maintained upstream (and has been effectively unmaintained for a while). > > It can stay in Debian as long as clutter does (assuming there are no RC > bugs), but will have to be removed when clutter is removed. Sorry, I got the package name wrong; reassigning. smcv
Bug#1018138: scim-clutter-immodule: depends on unmaintained clutter-1.0 and related libraries
Package: scim-clutter-immodule Version: 1.4.18+git20211204-0.1 Severity: normal Tags: bookworm sid upstream User: pkg-gnome-maintain...@lists.alioth.debian.org Usertags: oldlibs clutter Control: block 996690 by -1 This package depends on and enhances clutter-1.0, which is no longer maintained upstream (and has been effectively unmaintained for a while). It can stay in Debian as long as clutter does (assuming there are no RC bugs), but will have to be removed when clutter is removed. smcv
Bug#1018137: ibus-clutter: depends on unmaintained clutter-1.0 and related libraries
Source: ibus-clutter Version: 0.0+git20090728.a936bacf-7 Severity: important Tags: bookworm sid upstream User: pkg-gnome-maintain...@lists.alioth.debian.org Usertags: oldlibs clutter Control: block 996690 by -1 This package depends on and enhances clutter-1.0, which is no longer maintained upstream (and has been effectively unmaintained for a while). It can stay in Debian as long as clutter does (assuming there are no RC bugs), but will have to be removed when clutter is removed. smcv
Bug#1018136: swell-foop: depends on unmaintained clutter-1.0 and related libraries
Source: swell-foop Version: 1:41.1-1 Severity: important Tags: bookworm sid upstream User: pkg-gnome-maintain...@lists.alioth.debian.org Usertags: oldlibs clutter Control: block 996690 by -1 Forwarded: https://gitlab.gnome.org/GNOME/swell-foop/-/issues/24 This package depends on clutter-1.0, which is no longer maintained upstream (and has been effectively unmaintained for a while). smcv
Bug#1018132: lifeograph: depends on unmaintained clutter-1.0 and related libraries
Source: lifeograph Version: 2.0.3-1 Severity: important Tags: bookworm sid upstream User: pkg-gnome-maintain...@lists.alioth.debian.org Usertags: oldlibs clutter Control: block 996690 by -1 This package depends on clutter-1.0, which is no longer maintained upstream (and has been effectively unmaintained for a while). It looks like this might be via libchamplain rather than directly. https://gitlab.gnome.org/GNOME/Initiatives/-/issues/31 has some porting notes for projects that are part of GNOME, which might be useful inspiration for porting this package. In the case of libchamplain, the direct replacement is GTK 4 and libshumate. smcv
Bug#1018135: quadrapassel: depends on unmaintained clutter-1.0 and related libraries
Source: quadrapassel Version: 1:40.2-1 Severity: important Tags: bookworm sid upstream User: pkg-gnome-maintain...@lists.alioth.debian.org Usertags: oldlibs clutter Control: block 996690 by -1 Forwarded: https://gitlab.gnome.org/GNOME/quadrapassel/-/issues/40 This package depends on clutter-1.0, which is no longer maintained upstream (and has been effectively unmaintained for a while). smcv
Bug#1018134: chatty: Fails to build with evolution-data-server 3.45
Source: chatty Version: 0.6.7-2 Severity: important Tags: ftbfs sid bookworm upstream Forwarded: https://source.puri.sm/Librem5/chatty/-/issues/727 chatty fails to build with evolution-data-server 3.45 currently in Debian Experimental. Thank you, Jeremy Bicha
Bug#1018133: pinpoint: depends on unmaintained clutter-1.0 and related libraries
Source: pinpoint Version: 1:0.1.8-5 Severity: important Tags: bookworm sid upstream User: pkg-gnome-maintain...@lists.alioth.debian.org Usertags: oldlibs clutter Control: block 996690 by -1 This package depends on clutter-1.0, which is no longer maintained upstream (and has been effectively unmaintained for a while). https://gitlab.gnome.org/GNOME/Initiatives/-/issues/31 has some porting notes for projects that are part of GNOME, which might be useful inspiration for porting this package. smcv
Bug#1017493: feedreader: Switch to libsoup3
Control: severity -1 serious To provide more warning and time for the maintainer to take action, I'm bumping this bug's severity now. Thank you, Jeremy Bicha
Bug#1018130: abiword: depends on unmaintained clutter-1.0 and related libraries
Source: abiword Version: 3.0.5~dfsg-1 Severity: important Tags: bookworm sid upstream User: pkg-gnome-maintain...@lists.alioth.debian.org Usertags: oldlibs clutter Control: block 996690 by -1 This package depends on clutter-1.0, which is no longer maintained upstream (and has been effectively unmaintained for a while). It looks like this might be via libchamplain rather than directly. https://gitlab.gnome.org/GNOME/Initiatives/-/issues/31 has some porting notes for projects that are part of GNOME, which might be useful inspiration for porting this package. smcv
Bug#1018129: jami: depends on unmaintained clutter-1.0 and related libraries
Source: ring Version: 20210112.2.b757bac~ds1-1 Severity: important Tags: bookworm sid upstream User: pkg-gnome-maintain...@lists.alioth.debian.org Usertags: oldlibs clutter Control: block 996690 by -1 This package depends on clutter-1.0, which is no longer maintained upstream (and has been effectively unmaintained for a while). https://gitlab.gnome.org/GNOME/Initiatives/-/issues/31 has some porting notes for projects that are part of GNOME, which might be useful inspiration for porting this package. smcv
Bug#1018128: jami: depends on unmaintained clutter-1.0 and related libraries
Source: jami Version: 20210112.2.b757bac~ds1-1 Severity: important Tags: bookworm sid upstream User: pkg-gnome-maintain...@lists.alioth.debian.org Usertags: oldlibs clutter Control: block 996690 by -1 This package depends on clutter-1.0, which is no longer maintained upstream (and has been effectively unmaintained for a while). https://gitlab.gnome.org/GNOME/Initiatives/-/issues/31 has some porting notes for projects that are part of GNOME, which might be useful inspiration for porting this package. smcv
Bug#1018127: gtkpod: depends on unmaintained clutter-1.0 and related libraries
Source: gtkpod Version: 2.1.5-9 Severity: important Tags: bookworm sid upstream User: pkg-gnome-maintain...@lists.alioth.debian.org Usertags: oldlibs clutter Control: block 996690 by -1 This package depends on clutter-1.0, which is no longer maintained upstream (and has been effectively unmaintained for a while). https://gitlab.gnome.org/GNOME/Initiatives/-/issues/31 has some porting notes for projects that are part of GNOME, which might be useful inspiration for porting this package. smcv
Bug#1018126: gthumb: depends on unmaintained clutter-1.0 and related libraries
Source: gthumb Version: 3:3.12.2-1 Severity: important Tags: bookworm sid upstream User: pkg-gnome-maintain...@lists.alioth.debian.org Usertags: oldlibs clutter Control: block 996690 by -1 This package depends on clutter-1.0, which is no longer maintained upstream (and has been effectively unmaintained for a while). https://gitlab.gnome.org/GNOME/Initiatives/-/issues/31 has some porting notes for projects that are part of GNOME, which might be useful inspiration for porting this package. smcv
Bug#1018125: gnome-nibbles: depends on unmaintained clutter-1.0 and related libraries
Source: gnome-nibbles Version: 1:3.38.2-2 Severity: important Tags: bookworm sid upstream User: pkg-gnome-maintain...@lists.alioth.debian.org Usertags: oldlibs clutter Control: block 996690 by -1 Forwarded: https://gitlab.gnome.org/GNOME/gnome-nibbles/-/issues/53 This package depends on clutter-1.0, which is no longer maintained upstream (and has been effectively unmaintained for a while). smcv
Bug#1018124: gnome-2048: depends on unmaintained clutter-1.0 and related libraries
Source: gnome-2048 Version: 3.38.2-2 Severity: important Tags: bookworm sid upstream User: pkg-gnome-maintain...@lists.alioth.debian.org Usertags: oldlibs clutter Control: block 996690 by -1 Forwarded: https://gitlab.gnome.org/GNOME/gnome-2048/-/issues/26 This package depends on clutter-1.0, which is no longer maintained upstream (and has been effectively unmaintained for a while). smcv
Bug#1018123: geeqie: depends on unmaintained clutter-1.0 and related libraries
Source: geeqie Version: 1:2.0.1-1 Severity: important Tags: bookworm sid upstream User: pkg-gnome-maintain...@lists.alioth.debian.org Usertags: oldlibs clutter Control: block 996690 by -1 This package depends on clutter-1.0, which is no longer maintained upstream (and has been effectively unmaintained for a while). https://gitlab.gnome.org/GNOME/Initiatives/-/issues/31 has some porting notes for projects that are part of GNOME, which might be useful inspiration for porting this package. smcv
Bug#1018122: RM: empathy -- RoQA; unmaintained; incompatible with GNOME 43
Package: ftp.debian.org X-Debbugs-CC: empa...@packages.debian.org An app can't link against both libsoup2.4 and libsoup3 simultaneously. empathy depends on libsoup2.4 but it also depends on several libraries that will be switching to libsoup3 to finish packaging GNOME 43 for Debian 12. There is no longer an upstream for empathy. Empathy was archived more than a year ago which means bug reports, translation updates, and even bugfixes are no longer being accepted. [1] [1] https://gitlab.gnome.org/GNOME/empathy Thank you, Jeremy Bicha
Bug#1018121: fotoxx: depends on unmaintained clutter-1.0 and related libraries
Source: fotoxx Version: 20.08-2 Severity: important Tags: bookworm sid upstream User: pkg-gnome-maintain...@lists.alioth.debian.org Usertags: oldlibs clutter Control: block 996690 by -1 This package depends on clutter-1.0, which is no longer maintained upstream (and has been effectively unmaintained for a while). https://gitlab.gnome.org/GNOME/Initiatives/-/issues/31 has some porting notes for projects that are part of GNOME, which might be useful inspiration for porting this package. smcv
Bug#1018120: evolution: depends on unmaintained clutter-1.0 and related libraries
Source: evolution Version: 3.44.4-1 Severity: important Tags: bookworm sid upstream User: pkg-gnome-maintain...@lists.alioth.debian.org Usertags: oldlibs clutter Control: found -1 3.45.2-2 Control: block 996690 by -1 This package depends on clutter-1.0, which is no longer maintained upstream (and has been effectively unmaintained for a while). It looks as though disabling the "contact maps" option might resolve this. smcv
Bug#1016080: buster-pu: package libreoffice/:6.1.5-3+deb10u8
Hi, Am 25.08.22 um 21:05 schrieb Adam D. Barratt: To clarify here, are you suggesting that we should skip this change for buster? Yes, given that we'd need a further update even more tiny and the next release is the final one I don't think this warrants a full libreoffice build. Sorry for this unneeded request. > (and, as you say, assume people will want to use newer versions in any case.) Indeed. Just didn't want to close myself, but we could do so and ignore this for buster. Regards, Rene
Bug#1018118: transition: mutter & gnome-shell 43
Package: release.debian.org Tags: moreinfo User: release.debian@packages.debian.org Usertags: transition X-Debbugs-Cc: gnome-sh...@packages.debain.org Affected packages that all need sourceful uploads are below plus gnome-shell-extensions https://release.debian.org/transitions/html/auto-mutter.html All of those core packages are maintained by the Debian GNOME team except for Budgie which just needs a simple dependency change when the transition begins. This transition overlaps with the big evolution-data-server transition: https://launchpad.net/bugs/1016706 Either transition can go first, but it's best that they not happen simultaneously. This transition is blocked on someone going through all the packaged gnome-shell extensions to report bugs for them to either declare compatibility with GNOME Shell 43 (if compatible, the metadata file and debian/control need to be updated) or to let them be removed from Testing. We have completed this transition in Ubuntu but Ubuntu only has a very small number of packaged extensions compared to Debian. Thank you, Jeremy Bicha
Bug#1018119: eog-plugin-map: depends on unmaintained clutter-1.0 and related libraries
Package: eog-plugin-map Version: 42.1-1 Severity: important Tags: bookworm sid upstream User: pkg-gnome-maintain...@lists.alioth.debian.org Usertags: oldlibs clutter Control: block 996690 by -1 The map plugin depends on clutter-1.0, which is no longer maintained upstream (and has been effectively unmaintained for a while). https://gitlab.gnome.org/GNOME/Initiatives/-/issues/31 has some porting information for core GNOME apps which might be useful here. The map plugin will presumably have to be removed at some point. smcv
Bug#1018117: empathy: upstream project discontinued
Source: empathy Version: 3.25.90+really3.12.14-2 Severity: important Tags: bookworm sid upstream wontfix User: pkg-gnome-maintain...@lists.alioth.debian.org Usertags: oldlibs unmaintained-upstream Empathy has been moved to https://gitlab.gnome.org/Archive/empathy and archived. No new commits can be pushed, no new bugs can be reported and no new releases will be made unless someone starts a maintained fork. smcv
Bug#1018116: empathy: depends on unmaintained clutter-1.0 and related libraries
Source: empathy Version: 3.25.90+really3.12.14-2 Severity: important Tags: bookworm sid upstream wontfix User: pkg-gnome-maintain...@lists.alioth.debian.org Usertags: oldlibs clutter Control: block 996690 by -1 This package depends on clutter-1.0, which is no longer maintained upstream (and has been effectively unmaintained for a while). empathy is dead upstream and has been archived, so this is unlikely to be fixed unless someone forks it. smcv
Bug#1018073: asterisk: CVE-2019-15297 AST-2021-006 crash when receiving m=image 0 udptl t38 re-invite fixed in 16.16.2
Hi I'm not sure it make sense that the CVE-2019-15297 was used both for AST-2019-004 and AST-2021-006. I asked MITRE CNA to see if there is a reason not to assign a new CVE for AST-2021-006. I suspect many have missed otherwise the update through AST-2021-006 because did already tracked the CVE-2019-15297 / AST-2019-004 and updated packages accordingly (which happened in Debian with the 1:16.10.0~dfsg-1 and 1:16.2.1~dfsg-1+deb10u2 updates). Regards, Salvatore
Bug#1018114: buzztrax: depends on unmaintained clutter-1.0 and related libraries
Source: buzztrax Version: 0.10.2-7.1 Severity: important Tags: bookworm sid upstream User: pkg-gnome-maintain...@lists.alioth.debian.org Usertags: oldlibs clutter Control: block 996690 by -1 This package depends on clutter-1.0, which is no longer maintained upstream (and has been effectively unmaintained for a while). https://gitlab.gnome.org/GNOME/Initiatives/-/issues/31 has some porting notes for projects that are part of GNOME, which might be useful inspiration for porting this package. smcv
Bug#1018115: cheese: depends on unmaintained clutter-1.0 and related libraries
Source: cheese Version: 43~alpha-1 Severity: important Tags: bookworm sid upstream User: pkg-gnome-maintain...@lists.alioth.debian.org Usertags: oldlibs clutter Forwarded: https://gitlab.gnome.org/GNOME/cheese/-/merge_requests/55 Control: block 996690 by -1 This package depends on clutter-1.0, which is no longer maintained upstream (and has been effectively unmaintained for a while). There is a merge request upstream, but nobody seems to be reviewing it. smcv
Bug#1016080: buster-pu: package libreoffice/:6.1.5-3+deb10u8
Hi, On Thu, 2022-07-28 at 23:05 +0200, Rene Engelhard wrote: > Hi, > > Am 26.07.22 um 19:11 schrieb Rene Engelhard: > > actually this is quite a small update for a big package. Should we > > really do it (and the default change)? Or should we assume people > > don't > > use LO from oldstable anymore and either use bullseye or the > > bullseye > > version backported to buster? > > > > Filing for completeness' sake, though. > > I didn't have on radar that buster supports ends in a few days > anyway. > > And doing the default change in LTS then even makes less sense for a > effectively [small diff elided] > only... > > Hmm. > To clarify here, are you suggesting that we should skip this change for buster? (and, as you say, assume people will want to use newer versions in any case.) Regards, Adam
Bug#1018113: clutter-gtk: upstream project discontinued, should be removed
Source: clutter-gtk Version: 1.8.4-4 Severity: important Tags: bookworm sid upstream wontfix User: pkg-gnome-maintain...@lists.alioth.debian.org Usertags: oldlibs clutter Control: block 996690 by -1 clutter-gtk has now been moved to https://gitlab.gnome.org/Archive/clutter-gtk and archived. No new bugs can be reported, no new commits can be pushed, and no new releases will be made. https://gitlab.gnome.org/GNOME/Initiatives/-/issues/31 has some porting notes. smcv
Bug#1018112: clutter-gst-3.0: upstream project discontinued, should be removed
Source: clutter-gst-3.0 Version: 3.0.27-3 Severity: important Tags: bookworm sid upstream wontfix User: pkg-gnome-maintain...@lists.alioth.debian.org Usertags: oldlibs clutter Control: block 996690 by -1 clutter-gst has now been moved to https://gitlab.gnome.org/Archive/clutter-gst and archived. No new bugs can be reported, no new commits can be pushed, and no new releases will be made. https://gitlab.gnome.org/GNOME/Initiatives/-/issues/31 has some porting notes. The replacement appears to be GStreamer's gtkglsink. smcv
Bug#994014: dgit push-source unnecessarily fails if gpg updates its trustdb
Control: tags -1 + moreinfo
Colin Watson writes ("Bug#994014: dgit push-source unnecessarily fails if gpg
updates its trustdb"):
> dgit: failed command: git verify-tag
> 7fc8242a8eaa1da7e442993b6a300b8da9f34d5f
Firstly, thanks for diligently filing a report.
> dgit: error: subprocess failed with error exit status 1
> ! Push failed, *after* signing the tag.
> ! If you want to try again, you should use a new version number.
>
> I'm not sure why "git verify-tag" apparently returned non-zero here, but
> the trustdb junk in the output is suspicious. Perhaps dgit ought to run
> gpg with the "--no-auto-check-trustdb" option to suppress this?
Possibly. I think it's more likely to be random flakiness in gnupg2.
In principle dgit might have assembled an incorrect git tag (it
doesn't use git-tag to make tags which is one reason it verifies
them). But it doesn't seem very likely. There are some obvious
possible stochastic failure modes involving random strings of variable
length, but if dgit has one of those it has a very low probability.
Was the tag in fact correct, DYK?
I already knew that git-verify-tag sometimes has poor error handling -
it can fail to say what it tried to do to verify the tag and what the
results were. I don't think that's helping.
If the trustdb theory is right, then it's a bug in gnupg or maybe the
way git-verify-tag calls it. But I doubt it's worth attempting to
constructing a repro based on that theory.
Under the circumstances (particular, gnupg2's past history of low
probability random lossage) I don't think this bug is worth any
followup unless we have a repro. This is vexing, because I want dgit
to be reliable.
Sorry.
In any case, I don't think this is at all likely to be a bug in dgit.
I'm going to tag this moreinfo. Feel free to leave it open, or close
it, as you like.
Thanks,
Ian.
--
Ian JacksonThese opinions are my own.
Pronouns: they/he. If I emailed you from @fyvzl.net or @evade.org.uk,
that is a private address which bypasses my fierce spamfilter.
Bug#1018111: libchamplain: depends on discontinued library clutter-1.0
Source: libchamplain Version: 0.12.20-1 Severity: important Tags: bookworm sid upstream wontfix User: pkg-gnome-maintain...@lists.alioth.debian.org Usertags: oldlibs clutter Control: block 996690 by -1 libchamplain depends on clutter-1.0, which is no longer maintained upstream. libchamplain probably doesn't have a whole lot of future either. The recommended replacement for libchamplain is libshumate, a "friendly fork" of libchamplain that uses GTK 4 instead of GTK 3 and Clutter. Apps need to be ported from GTK 3 to GTK 4 and from libchamplain to libshumate at the same time. https://gitlab.gnome.org/GNOME/gnome-maps/-/issues/353 is an example of this process. smcv
Bug#996691: cogl: upstream project discontinued, should be removed
Control: retitle -1 cogl: upstream project discontinued, should be removed Control: block -1 by 996690 On Sun, 17 Oct 2021 at 13:48:11 +0100, Simon McVittie wrote: > The upstream README says: > > > Clutter is in deep maintenance mode; only micro releases addressing > > bug fixes are planned from now on. Additionally, the API and features > > are frozen. Cogl has now been moved to https://gitlab.gnome.org/Archive/cogl and archived. No new bugs can be reported, no new commits can be pushed, and no new releases will be made. smcv
Bug#996690: clutter-1.0: upstream project discontinued, should be removed
Control: retitle -1 clutter-1.0: upstream project discontinued, should be removed Control: forcemerge -1 1018109 Clutter has now been moved to https://gitlab.gnome.org/Archive/clutter and it's in the process of being archived. After that has happened, no new bugs can be reported, no new commits can be pushed, and no new releases will be made. smcv
Bug#1018110: RFS: hydrapaper/3.3.1-1 [RC] -- Utility that sets background independently for each monitor
Package: sponsorship-requests Severity: important Dear mentors, I am looking for a sponsor for my package "hydrapaper": * Package name: hydrapaper Version : 3.3.1-1 Upstream Author : Gabriele Musco * URL : https://gitlab.com/gabmus/HydraPaper * License : GPL-3+ * Vcs : https://salsa.debian.org/fmneto-guest/hydrapaper Section : graphics The source builds the following binary packages: hydrapaper - Utility that sets background independently for each monitor To access further information about this package, please visit the following URL: https://mentors.debian.net/package/hydrapaper/ Alternatively, you can download the package with 'dget' using this command: dget -x https://mentors.debian.net/debian/pool/main/h/hydrapaper/hydrapaper_3.3.1-1.dsc Changes since the last upload: hydrapaper (3.3.1-1) unstable; urgency=medium . * New upstream version 3.3.1. * Bumped Standards-Version to 4.6.1. * Reorganized dependencies (application now uses GTK 4) (Closes: #1010697). Regards, -- Francisco Mariano Neto signature.asc Description: This is a digitally signed message part
Bug#1018075: [Tts-project] Bug#1018075: Default to espeak-ng-mbrola which has no voice?
Le 25/08/2022 à 20:38, Samuel Thibault a écrit : But when there is no voice available there, it won't be working so in that case speech-dispatcher shouldn't even enable it, and thus fallback to espeak-ng. I'll have a look at fixing that, thanks for the report that at last reached somebody who is actually in touch with speech-dispatcher! Thanks. Also I was unsure if there is really no voice available or is that an issue with the mbrola-paths patch which made them not being found? Cheers, Sebastien Bacher
Bug#1018109: clutter-1.0: unmaintained upstream, should eventually be removed
Source: clutter-1.0 Version: 1.26.4+dfsg-4 Severity: important Tags: bookworm sid upstream wontfix User: pkg-gnome-maintain...@lists.alioth.debian.org Usertags: oldlibs clutter clutter is unmaintained upstream, and is in the process of being archived by the closest thing it has to an upstream maintainer. The most recent major release was in 2016. I am not aware of a porting guide. https://gitlab.gnome.org/GNOME/Initiatives/-/issues/31 has some examples of apps being ported away from Clutter/Cogl. smcv
Bug#1018075: [Tts-project] Bug#1018075: Default to espeak-ng-mbrola which has no voice?
Hello, Sebastien Bacher, le jeu. 25 août 2022 11:46:18 +0200, a ecrit: > but it seems the problem is that espeak-ng-mbrola is the > default output and that has no voice? > > $ spd-say -O > OUTPUT MODULES > espeak-ng-mbrola > espeak-ng > > $ spd-say -o espeak-ng-mbrola -L > NAME LANGUAGE VARIANT > $ > > Should espeak-ng be the default? No, we really want espeak-ng-mbrola to be the default when it's available and working. But when there is no voice available there, it won't be working so in that case speech-dispatcher shouldn't even enable it, and thus fallback to espeak-ng. I'll have a look at fixing that, thanks for the report that at last reached somebody who is actually in touch with speech-dispatcher! Samuel
Bug#1004471: Fwd: [Pkg-javascript-devel] node-terser_5.15.0-1_source.changes ACCEPTED into unstable
Hi, could you also push node-rollup-plugin-terser ? I fixed it for terser >= 5 (partial patch revert: 2001_*) and added a "Breaks node-rollup-plugin-terser (<< 7.0.2+~5.0.1-3~)" in node-terser. Cheers, Yadd Forwarded Message Subject: [Pkg-javascript-devel] node-terser_5.15.0-1_source.changes ACCEPTED into unstable Date: Thu, 25 Aug 2022 17:01:35 + From: Debian FTP Masters To: Debian Javascript Maintainers , Jonas Smedegaard Accepted: Format: 1.8 Date: Thu, 25 Aug 2022 18:32:01 +0200 Source: node-terser Architecture: source Version: 5.15.0-1 Distribution: unstable Urgency: medium Maintainer: Debian Javascript Maintainers Changed-By: Jonas Smedegaard Changes: node-terser (5.15.0-1) unstable; urgency=medium . [ upstream ] * new release . [ Jonas Smedegaard ] * unfuzz patches * fix use source-map during build; build-depend on node-source-map * skip tests likely caused by outdated source-map; add source helper tool tap-todo * update copyright info: update coverage Checksums-Sha1: 8d2d2f3f67960602e3ad7d8937eb60e68410f52b 2477 node-terser_5.15.0-1.dsc 3f37c472ecb1b6a922da2e455684b3b39aca3fe0 467601 node-terser_5.15.0.orig.tar.gz 548b8a8e3a5012d6ddc7ddd4d12969830b2c1dd5 14104 node-terser_5.15.0-1.debian.tar.xz c5671b20ebce9f22f6fef318e5d5ae3b4bca4036 14868 node-terser_5.15.0-1_amd64.buildinfo Checksums-Sha256: 075c771a34c144805ae0af31fbc518ff2357dee768cf6c8a9cf47bcf3608ff14 2477 node-terser_5.15.0-1.dsc 702131e06038d855f5ce9972fdb9cae6e68108aeb4239a7a15305ad9712f9b99 467601 node-terser_5.15.0.orig.tar.gz c4ad5ef05f27e3f2f9bac582211b55eff9271b6f56bb5af46d17167cdeb1f460 14104 node-terser_5.15.0-1.debian.tar.xz 22eed69a5a7b12a5912a53fae0cd4073da72be65dcfa6c976d81fb5d71b2e2b2 14868 node-terser_5.15.0-1_amd64.buildinfo Files: d47d39d1bc8d9efafc51233c23533597 2477 javascript optional node-terser_5.15.0-1.dsc 029ec3d70e57e0803e5fb3ca3df1bedc 467601 javascript optional node-terser_5.15.0.orig.tar.gz 4f580a1bb8348f932d6be329d6ead128 14104 javascript optional node-terser_5.15.0-1.debian.tar.xz 18e85108f8e19185c9ae106c7be73458 14868 javascript optional node-terser_5.15.0-1_amd64.buildinfo Thank you for your contribution to Debian. -- Pkg-javascript-devel mailing list pkg-javascript-de...@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
Bug#1018108: buster-pu: package ruby-hiredis/0.6.1-2+deb10u1
And here is the debdiff.
cu
Adrian
On Thu, Aug 25, 2022 at 09:27:20PM +0300, Adrian Bunk wrote:
> Package: release.debian.org
> Severity: normal
> Tags: buster
> User: release.debian@packages.debian.org
> Usertags: pu
> X-Debbugs-Cc: Debian Ruby Extras Maintainers
> ;
>
> * Skip more EAGAIN related tests. (Closes: #988023)
>
> debian/patches/disable-no-eagain-test.patch was updated to the
> version in 0.6.3-2, fixing the FTBFS.
diff -Nru ruby-hiredis-0.6.1/debian/changelog
ruby-hiredis-0.6.1/debian/changelog
--- ruby-hiredis-0.6.1/debian/changelog 2018-10-12 10:38:52.0 +0300
+++ ruby-hiredis-0.6.1/debian/changelog 2022-08-25 21:21:59.0 +0300
@@ -1,3 +1,10 @@
+ruby-hiredis (0.6.1-2+deb10u1) buster; urgency=medium
+
+ * Non-maintainer upload.
+ * Skip more EAGAIN related tests. (Closes: #988023)
+
+ -- Adrian Bunk Thu, 25 Aug 2022 21:21:59 +0300
+
ruby-hiredis (0.6.1-2) unstable; urgency=medium
[ Cédric Boutillier ]
diff -Nru ruby-hiredis-0.6.1/debian/patches/disable-no-eagain-test.patch
ruby-hiredis-0.6.1/debian/patches/disable-no-eagain-test.patch
--- ruby-hiredis-0.6.1/debian/patches/disable-no-eagain-test.patch
2016-02-09 16:07:46.0 +0200
+++ ruby-hiredis-0.6.1/debian/patches/disable-no-eagain-test.patch
2022-08-25 21:21:52.0 +0300
@@ -1,28 +1,107 @@
-Author: Apollon Oikonomopoulos
-Description: Disable test_no_eagain_after_cumulative_wait_exceeds_timeout
- This test is probably too time-sensitive and yields different results across
- different kernels (seems to work reliably only on Linux).
+From: Apollon Oikonomopoulos
+Date: Mon, 20 Jan 2020 09:28:45 -0300
+Subject: Disable EAGAIN related tests
+These tests are probably too time-sensitive and yields different results across
+different kernels (seems to work reliably only on Linux).
Forwarded: no
-Last-Update: 2014-04-14
+Last-Update: 2020-02-19
+
+test
+---
+ test/connection_test.rb | 105
+ 1 file changed, 105 deletions(-)
+
+diff --git a/test/connection_test.rb b/test/connection_test.rb
+index 513d520..bd94e80 100644
--- a/test/connection_test.rb
+++ b/test/connection_test.rb
-@@ -361,35 +361,37 @@
+@@ -281,111 +281,6 @@ module ConnectionTests
end
end
+- def test_recover_from_partial_write
+-listen do |server|
+- hiredis.connect("localhost", 6380)
+-
+- # Find out send buffer size
+- sndbuf = sockopt(hiredis.sock, Socket::SO_SNDBUF)
+-
+- # Make request that saturates the send buffer
+- hiredis.write(["x" * sndbuf])
+-
+- # Flush and disconnect to signal EOF
+- hiredis.flush
+- hiredis.disconnect
+-
+- # Compare to data received on the other end
+- formatted = "*1\r\n$#{sndbuf}\r\n#{"x" * sndbuf}\r\n"
+- assert formatted == server.read
+-end
+- end
+-
+- #
+- # This does not have consistent outcome for different operating systems...
+- #
+- # def test_eagain_on_write
+- # listen do |server|
+- # hiredis.connect("localhost", 6380)
+- # hiredis.timeout = 100_000
+-
+- # # Find out buffer sizes
+- # sndbuf = sockopt(hiredis.sock, Socket::SO_SNDBUF)
+- # rcvbuf = sockopt(hiredis.sock, Socket::SO_RCVBUF)
+-
+- # # Make request that fills both the remote receive buffer and the local
+- # # send buffer. This assumes that the size of the receive buffer on the
+- # # remote end is equal to our local receive buffer size.
+- # assert_raises Errno::EAGAIN do
+- # hiredis.write(["x" * rcvbuf * 2])
+- # hiredis.write(["x" * sndbuf * 2])
+- # hiredis.flush
+- # end
+- # end
+- # end
+-
+- def test_eagain_on_write_followed_by_remote_drain
+-listen do |server|
+- hiredis.connect("localhost", 6380)
+- hiredis.timeout = 100_000
+-
+- # Find out buffer sizes
+- sndbuf = sockopt(hiredis.sock, Socket::SO_SNDBUF)
+- rcvbuf = sockopt(hiredis.sock, Socket::SO_RCVBUF)
+-
+- # This thread starts reading the server buffer after 50ms. This will
+- # cause the local write to first return EAGAIN, wait for the socket to
+- # become writable with select(2) and retry.
+- begin
+-thread = Thread.new do
+- sleep(0.050)
+- loop do
+-server.read(1024)
+- end
+-end
+-
+-# Make request that fills both the remote receive buffer and the local
+-# send buffer. This assumes that the size of the receive buffer on the
+-# remote end is equal to our local receive buffer size.
+-hiredis.write(["x" * rcvbuf])
+-hiredis.write(["x" * sndbuf])
+-hiredis.flush
+-hiredis.disconnect
+- ensure
+-thread.kill
+- end
+-end
+- end
+-
- def test_no_eagain_after_cumulative_wait_exceeds_timeout
-listen do |server|
- hiredis.connect("localhost", 6380)
- hiredis.timeout = 10_000
-+ # The following test seems to be too sensitive wrt
Bug#1018108: buster-pu: package ruby-hiredis/0.6.1-2+deb10u1
Package: release.debian.org Severity: normal Tags: buster User: release.debian@packages.debian.org Usertags: pu X-Debbugs-Cc: Debian Ruby Extras Maintainers ; * Skip more EAGAIN related tests. (Closes: #988023) debian/patches/disable-no-eagain-test.patch was updated to the version in 0.6.3-2, fixing the FTBFS.
Bug#1018081: rust-atk-sys: autopkgtest failure with at-spi2-core 2.45.90+
Hello, Jeremy Bicha, le jeu. 25 août 2022 09:22:20 -0400, a ecrit: > rust-atk-sys's autopkgtests fail with at-spi2-core 2.45.90-1, > currently in Debian experimental. > > https://ci.debian.net/packages/r/rust-atk-sys/unstable/amd64/ > > test cross_validate_constants_with_c ... FAILED > cross_validate_constants_with_c stdout > Constant value mismatch for (gint) ATK_ROLE_LAST_DEFINED Thanks for having watched this. I guess this will want a patch like debian/patches/allow-increase-in-c-value-of-atk-state-last-defined.patch Actually, probably better introduce one for all the LAST_DEFINED macros ATK_KEY_EVENT_LAST_DEFINED ATK_RELATION_LAST_DEFINED ATK_ROLE_LAST_DEFINED ATK_STATE_LAST_DEFINED ATK_TEXT_ATTR_LAST_DEFINED ATK_VALUE_LAST_DEFINED because upstream will never bump the soname when adding new roles, state, etc. Samuel
Bug#1009643: Puppet: Fails to work with Ruby 3.0
On 2022-04-14 10:49:43, Antoine Beaupré wrote: > On 2022-04-13 17:26:27, Gabriel Filion wrote: >> Hi there, >> >> For what it's worth, upstream puppet does not yet suppport ruby 3.0. >> >> see: https://puppet.com/docs/puppet/7/release_notes_puppet.html >> >> puppet 7 added support for ruby 2.7 but 2.9 and 3.0 were never there >> upstream. I'm guessing they'll bump to 3.x for the puppet 8 cycle only. > > That's actually not quite correct: Puppet 7.8 added support for Ruby 3, > so we should be able to jump there. > > It is my hope that we can ship Puppet agent 6 and Puppet server 7 in > bookworm to fix all of those issues in one fell swoop. See: > > https://alioth-lists.debian.net/pipermail/pkg-puppet-devel/2022-April/012681.html > > I don't think it's worth fixing the Puppet 5.5 packages to be honest, > our energy is better spent updating to upstream packages. For what it's worth, I have tested lavamind's Puppet 7 package from experimental, on bookworm, and it works fine: https://tracker.debian.org/pkg/puppet-agent ... I am not sure how to express this in the BTS here, because it's a different source package, so I can't mark it as fixed there without first marking it as affecting that other package, but it never affected it. Anyways, just to say that this is fixed in experimental. :) -- A developed country is not a place where the poor have cars. It's where the rich use public transportation. - Gustavo Petro
Bug#1018076: transition: gjs and gnome-shell likely to be removed from armel
Simon McVittie dijo [Thu, Aug 25, 2022 at 11:19:30AM +0100]: > Obviously that's quite a bit of churn, mostly in packages that, in > practice, have never been useful to run on the 2009-2010 plug computers > that seem to be the main use-case for armel. > > Is armel a realistic candidate for being a Debian 12 release > architecture? It's already lacking other important packages like Firefox, > and if it ceased to be treated as a release architecture very soon, > then we wouldn't have to do all this work to coax GNOME into testing > despite armel. While I would never attempt to run a heavy desktop under such machines, I think there are still many users of Debian in armel machines -- me included! The Raspberry Pi families for models 0 and 1 are almost-but-not-quite-armhf (so they must run armel). There are several million such devices Out There™; while the RPi1 family does not make too much sense for buying nowadays (being at the same price as RPi3, which is vastly more powerful), hardware availability for the much smaller RPi0W (introduced in 2015/2017, according to Wikipedia) is much more than of the newer RPI0W-2 (oh, the naming for such machines...) I cannot provide hard numbers (I suppose mirror operators might?), but I do not feel armel systems are hard to come by, nor marginal in the amount of users they have. Yes, running a GNOME desktop on them might be a Very Bad Idea (if at all possible)... But they are very good non-interactive purposes.
Bug#1018107: buster-pu: package golang-github-docker-go-connections/0.3.0-3+deb10u1
Package: release.debian.org
Severity: normal
Tags: buster
User: release.debian@packages.debian.org
Usertags: pu
X-Debbugs-Cc: Debian Go Packaging Team
* Add patch to skip tests which use expired certificate. (Closes: #986306)
diff -Nru golang-github-docker-go-connections-0.3.0/debian/changelog
golang-github-docker-go-connections-0.3.0/debian/changelog
--- golang-github-docker-go-connections-0.3.0/debian/changelog 2018-02-16
10:55:09.0 +0200
+++ golang-github-docker-go-connections-0.3.0/debian/changelog 2022-08-25
21:05:07.0 +0300
@@ -1,3 +1,10 @@
+golang-github-docker-go-connections (0.3.0-3+deb10u1) buster; urgency=medium
+
+ * Non-maintainer upload.
+ * Add patch to skip tests which use expired certificate. (Closes: #986306)
+
+ -- Adrian Bunk Thu, 25 Aug 2022 21:05:07 +0300
+
golang-github-docker-go-connections (0.3.0-3) unstable; urgency=medium
* Team upload.
diff -Nru
golang-github-docker-go-connections-0.3.0/debian/patches/0001-Skip-tests-which-use-expiered-certificate.patch
golang-github-docker-go-connections-0.3.0/debian/patches/0001-Skip-tests-which-use-expiered-certificate.patch
---
golang-github-docker-go-connections-0.3.0/debian/patches/0001-Skip-tests-which-use-expiered-certificate.patch
1970-01-01 02:00:00.0 +0200
+++
golang-github-docker-go-connections-0.3.0/debian/patches/0001-Skip-tests-which-use-expiered-certificate.patch
2021-04-05 14:39:50.0 +0300
@@ -0,0 +1,28 @@
+From: Shengjing Zhu
+Date: Mon, 5 Apr 2021 19:38:47 +0800
+Subject: Skip tests which use expiered certificate
+
+---
+ tlsconfig/config_test.go | 2 ++
+ 1 file changed, 2 insertions(+)
+
+diff --git a/tlsconfig/config_test.go b/tlsconfig/config_test.go
+index 345cbe7..aa94f02 100644
+--- a/tlsconfig/config_test.go
b/tlsconfig/config_test.go
+@@ -202,6 +202,7 @@ func TestConfigServerTLSClientCASet(t *testing.T) {
+ // Exclusive root pools determines whether the CA pool will be a union of the
system
+ // certificate pool and custom certs, or an exclusive or of the custom certs
and system pool
+ func TestConfigServerExclusiveRootPools(t *testing.T) {
++ t.Skip("certificate is expired")
+ key, cert := getCertAndKey()
+ ca := getMultiCert()
+
+@@ -562,6 +563,7 @@ func TestConfigClientTLSNotSetWithInvalidPassphrase(t
*testing.T) {
+ // Exclusive root pools determines whether the CA pool will be a union of the
system
+ // certificate pool and custom certs, or an exclusive or of the custom certs
and system pool
+ func TestConfigClientExclusiveRootPools(t *testing.T) {
++ t.Skip("certificate is expired")
+ ca := getMultiCert()
+
+ caBytes, err := ioutil.ReadFile(ca)
diff -Nru golang-github-docker-go-connections-0.3.0/debian/patches/series
golang-github-docker-go-connections-0.3.0/debian/patches/series
--- golang-github-docker-go-connections-0.3.0/debian/patches/series
1970-01-01 02:00:00.0 +0200
+++ golang-github-docker-go-connections-0.3.0/debian/patches/series
2021-04-05 14:39:50.0 +0300
@@ -0,0 +1 @@
+0001-Skip-tests-which-use-expiered-certificate.patch
Bug#1018106: sshd: pam_env(sshd:session): deprecated reading of user environment enabled
Package: openssh-server Version: 1:9.0p1-1+b1 Severity: normal Dear Maintainer, Each time a ssh session begins I have in the log on the server : sshd: pam_env(sshd:session): deprecated reading of user environment enabled This arrive since to day after libpam-modules and libpam-runtime were upgraded to 1.5.2-2. I don't know how to solve this, perhaps a modification in /etc/pam.d/sshd but what to do. Regards François -- System Information: Debian Release: bookworm/sid APT prefers testing APT policy: (900, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.18.0-4-amd64 (SMP w/8 CPU threads; PREEMPT) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.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 openssh-server depends on: ii adduser3.123 ii debconf [debconf-2.0] 1.5.79 ii dpkg 1.21.9 ii init-system-helpers1.64 ii libaudit1 1:3.0.7-1+b1 ii libc6 2.34-4 ii libcom-err21.46.5-2 ii libcrypt1 1:4.4.28-2 ii libgssapi-krb5-2 1.20-1 ii libkrb5-3 1.20-1 ii libpam-modules 1.5.2-2 ii libpam-runtime 1.5.2-2 ii libpam0g 1.5.2-2 ii libselinux13.4-1+b1 ii libssl33.0.5-2 ii libsystemd0251.3-1 ii libwrap0 7.6.q-31 ii lsb-base 11.2 ii openssh-client 1:9.0p1-1+b1 ii openssh-sftp-server1:9.0p1-1+b1 ii procps 2:3.3.17-7+b1 ii runit-helper 2.14.1 ii ucf3.0043 ii zlib1g 1:1.2.11.dfsg-4.1 Versions of packages openssh-server recommends: ii libpam-systemd [logind] 251.3-1 ii ncurses-term 6.3+20220423-2 ii xauth1:1.1.1-1 Versions of packages openssh-server suggests: ii ksshaskpass [ssh-askpass] 4:5.25.4-1 pn molly-guard pn monkeysphere pn ufw -- debconf information: openssh-server/password-authentication: true openssh-server/permit-root-login: false
Bug#923345: Fixed?
Hello, The problem seems to be now fixed, at least in Sid with Firefox ESR. I didn't find which change fixed the problem. Philippe.
Bug#1018105: gimp: crashes when adding text to image
Package: gimp Version: 2.10.32-1+b1 Severity: important X-Debbugs-Cc: somethingsomethingg...@gmail.com Dear Maintainer, * What led up to the situation? adding text to an image after deleting part of the image * What was the outcome of this action? gimp crashed * What outcome did you expect instead? text to be added to image -- System Information: Debian Release: bookworm/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 5.18.0-4-amd64 (SMP w/12 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.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 gimp depends on: ii gimp-data2.10.32-1 ii graphviz 2.42.2-7 ii libaa1 1.4p5-50 ii libbabl-0.1-01:0.1.92-1 ii libbz2-1.0 1.0.8-5 ii libc62.34-5 ii libcairo21.16.0-6 ii libfontconfig1 2.13.1-4.4 ii libfreetype6 2.12.1+dfsg-3 ii libgcc-s112.2.0-1 ii libgdk-pixbuf-2.0-0 2.42.9+dfsg-1 ii libgegl-0.4-01:0.4.38-1+b1 ii libgexiv2-2 0.14.0-1 ii libgimp2.0 2.10.32-1+b1 ii libglib2.0-0 2.73.3-2 ii libgs9 9.56.1~dfsg-1 ii libgtk2.0-0 2.24.33-2 ii libgudev-1.0-0 237-2 ii libharfbuzz0b2.7.4-1+b1 ii libheif1 1.12.0-2+b4 ii libjpeg62-turbo 1:2.1.2-1 ii libjson-glib-1.0-0 1.6.6-1 ii liblcms2-2 2.13.1-1 ii liblzma5 5.2.5-2.1 ii libmng1 1.0.10+dfsg-3.1+b5 ii libmypaint-1.5-1 1.6.0-2 ii libopenexr-3-1-303.1.5-4 ii libopenjp2-7 2.5.0-1 ii libpango-1.0-0 1.50.9+ds-1 ii libpangocairo-1.0-0 1.50.9+ds-1 ii libpangoft2-1.0-01.50.9+ds-1 ii libpng16-16 1.6.37-5 ii libpoppler-glib8 22.08.0-2 ii librsvg2-2 2.54.4+dfsg-1 ii libstdc++6 12.2.0-1 ii libtiff5 4.4.0-4 ii libwebp7 1.2.2-2+b1 ii libwebpdemux21.2.2-2+b1 ii libwebpmux3 1.2.2-2+b1 ii libwmf-0.2-7 0.2.12-5 ii libwmflite-0.2-7 0.2.12-5 ii libx11-6 2:1.8.1-2 ii libxcursor1 1:1.2.1-1 ii libxext6 2:1.3.4-1 ii libxfixes3 1:6.0.0-1 ii libxmu6 2:1.1.3-3 ii libxpm4 1:3.5.12-1 ii xdg-utils1.1.3-4.1 ii zlib1g 1:1.2.11.dfsg-4.1 Versions of packages gimp recommends: ii ghostscript 9.56.1~dfsg-1 Versions of packages gimp suggests: ii gimp-data-extras 1:2.0.2-1.1 ii gimp-help-en [gimp-help] 2.10.0-1 ii gvfs-backends 1.50.2-1 ii libasound21.2.7.2-1 -- no debconf information
Bug#1018104: texworks-manual FTBFS with imagemagick with the #987504 change
Source: texworks-manual Version: 20150506-2 Severity: serious Tags: ftbfs Control: close -1 20200329-1 https://tests.reproducible-builds.org/debian/rb-pkg/buster/amd64/texworks-manual.html ... make[4]: Entering directory '/build/texworks-manual-20150506/src/en/html' convert-im6.q16: attempt to perform an operation not allowed by the security policy `PDF' @ error/constitute.c/IsCoderAuthorized/408. convert-im6.q16: no images defined `images/Linux.png' @ error/convert.c/ConvertImageCommand/3258. make[4]: *** [Makefile:39: images/Linux.png] Error 1
Bug#1018103: ERROR: Unknown command 'lock'
Package: xdg-utils
Version: 1.1.3-4.1
Severity: minor
File: /usr/bin/xdg-screensaver
The xdg-screensaver usage goes like this:
anarcat@curie:~$ xdg-screensaver --help
xdg-screensaver - command line tool for controlling the screensaver
Synopsis
xdg-screensaver suspend WindowID
xdg-screensaver resume WindowID
xdg-screensaver { activate | lock | reset | status }
xdg-screensaver { --help | --manual | --version }
Use 'man xdg-screensaver' or 'xdg-screensaver --manual' for additional info.
Yet the lock command does *not* actually work in bullseye:
anarcat@curie:~$ xdg-screensaver lock
ERROR: Unknown command 'lock'
anarcat@curie:~[4]$
I suspect this is because I fall out of the normal "desktop" scenario:
i use i3 as wm and xss-lock as a screensaver.
looking at the source, it looks like screensaver_xserver() is lacking
a lock() clause. it would suffice to merge it with the activate) case
to fix this bug, I believe. Something like this:
>From 6f2840821c376aa77904e9ee50e6d152186e4a4f Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Antoine=20Beaupr=C3=A9?=
Date: Thu, 25 Aug 2022 13:35:05 -0400
Subject: [PATCH] add lock support to generic desktop environments
---
scripts/xdg-screensaver.in | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/scripts/xdg-screensaver.in b/scripts/xdg-screensaver.in
index 06d6667..b412a00 100644
--- a/scripts/xdg-screensaver.in
+++ b/scripts/xdg-screensaver.in
@@ -402,7 +402,7 @@ screensaver_xserver()
result=$?
;;
-activate)
+activate|lock)
xset s activate > /dev/null
result=$?
;;
--
2.30.2
Cheers
-- Package-specific info:
Desktop environment: XDG_CURRENT_DESKTOP=
-- System Information:
Debian Release: 11.4
APT prefers stable-security
APT policy: (500, 'stable-security'), (500, 'stable-debug'), (500, 'stable'),
(1, 'unstable'), (1, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 5.10.0-16-amd64 (SMP w/4 CPU threads)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_FIRMWARE_WORKAROUND,
TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=fr_CA.UTF-8, LC_CTYPE=fr_CA.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
xdg-utils depends on no packages.
Versions of packages xdg-utils recommends:
ii libfile-mimeinfo-perl 0.30-1
ii libnet-dbus-perl 1.2.0-1+b1
ii libx11-protocol-perl 0.56-7.1
ii x11-utils 7.7+5
ii x11-xserver-utils 7.7+8
xdg-utils suggests no packages.
-- no debconf information
Bug#1018102: idle detection failure
Package: xss-lock
Version: 0.3.0-10+b1
Severity: important
I have xss-lock setup to start xsecurelock automatically after the
delay prescribed by my `xset` configuration.
Basically, I have this in my .config/systemd/user/xset.service:
[Unit]
Description=Miscellaneous settings for X11
PartOf=graphical-session.target
[Service]
# `b off` disables the audible bell
# http://netbuz.org/blog/2011/11/x-bells-and-urgency-hints/
# `s IDLE BLANK` is the screensaver setup
# start after 1 minute idle, then lock in 3 seconds
# the blank timeout corresponds to the dimmer delay
# (XSECURELOCK_BLANK_TIMEOUT) in ~/.xsecurelock.env
ExecStart=/usr/bin/xset b off s 60 3
Type=oneshot
RemainAfterExit=false
[Install]
WantedBy=graphical-session.target
... and this in my .config/systemd/user/xss-lock.service:
[Unit]
Description=xss-lock - use external locker as X screen saver
Documentation=man:xss-lock(1)
PartOf=graphical-session.target
Wants=xset.service
After=xset.service
[Service]
Type=simple
EnvironmentFile=/home/anarcat/.xsecurelock.env
ExecStart=/usr/bin/xss-lock --verbose --transfer-sleep-lock
--session=${XDG_SESSION_ID} --notifier /usr/libexec/xsecurelock/dimmer --
xsecurelock
[Install]
WantedBy=graphical-session.target
In general, this works: on my laptop, right now, the screen correctly
locked after 60 seconds. But on my desktop, right now, the screen does
*not* lock after 60 seconds.
Calling `xset s activate` *does* lock the screen though, so xss-lock
is correctly behaving on that part. I have tried lowering the delay as
well (`xset s 3 3`, wait 3 seconds), no effect: it's as if my session
is not seen as idle by Xorg.
I suspect this is hard to reproduce: I seem to recall this workstation
correctly locking itself, but I'm not sure.
I wonder if I'm missing a key service in my session, or how to debug
the screensaver in Xorg (or if I should just switch to wayland already
anyways... ;)
Thanks for any help you can give me!
-- System Information:
Debian Release: 11.4
APT prefers stable-security
APT policy: (500, 'stable-security'), (500, 'stable-debug'), (500, 'stable'),
(1, 'unstable'), (1, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 5.10.0-16-amd64 (SMP w/4 CPU threads)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_FIRMWARE_WORKAROUND,
TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=fr_CA.UTF-8, LC_CTYPE=fr_CA.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 xss-lock depends on:
ii libc62.31-13+deb11u3
ii libglib2.0-0 2.66.8-1
ii libxcb-screensaver0 1.14-3
ii libxcb-util1 0.4.0-1+b1
ii libxcb1 1.14-3
xss-lock recommends no packages.
xss-lock suggests no packages.
-- debconf-show failed
Bug#977765: [Pkg-fonts-devel] Bug#977765: src:gsfonts: package superseded by fonts-urw-base35
Hi!
On Do, 25 Aug 2022, I wrote:
> I also think about updating gsfonts-x11 to use fonts-urw-base35 (.t1
> files) instead of gsfonts (.pfb files), but I'm not fully sure how to
> map the fonts since the full names in the fonts files look quite
> different (but both contain 35 fonts, so a mapping should be
> possible). Maybe a job for some rainy day...
I was curious, whether this is possible and so I just tried to patch
gsfonts-x11 to use fonts-urw-base35 instead of gsfonts and it worked
for me. I kept all font names in fonts.scale and fonts.alias and only
changed the referenced file names.
You'll find an updated gsfonts-x11_0.29_all.deb ans well as the patch
over current GIT version attached.
I had to rename the symlinks from .t1 to .pfb, since X11 doesn't
accept the .t1 names, but this shouldn't be a problem.
What do you think about this change?
Greetings
Roland
gsfonts-x11_0.29_all.deb
Description: application/vnd.debian.binary-package
diff --git a/README b/README
index fb1e257..1e01c3c 100644
--- a/README
+++ b/README
@@ -1,9 +1,9 @@
gsfonts-x11 for Debian
==
-This packages makes the 35 Postscript fonts from the gsfonts package
-available to your X server under their "urw" names and via fonts.alias
-with the official "adobe" names, too.
+This packages makes the 35 Postscript fonts from the fonts-urw-base35
+package available to your X server under their "urw" names and via
+fonts.alias with the official "adobe" names, too.
This package does not contain any fonts itself but allows to reuse the
ghostscript fonts as X11 screen fonts.
diff --git a/debian/changelog b/debian/changelog
index 1c9987a..f70aec8 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,6 +1,7 @@
gsfonts-x11 (0.29) UNRELEASED; urgency=medium
* Update to Standards-Version 4.6.1 (no changes).
+ * Use fonts from fonts-urw-base35 instead of gsfonts as base.
-- Roland Rosenfeld Sat, 11 Jun 2022 11:10:00 +0200
diff --git a/debian/control b/debian/control
index a5b5230..5fe35c5 100644
--- a/debian/control
+++ b/debian/control
@@ -11,11 +11,11 @@ Vcs-Browser: https://salsa.debian.org/debian/gsfonts-x11
Package: gsfonts-x11
Architecture: all
Multi-Arch: foreign
-Depends: gsfonts, ${misc:Depends}
-Description: Make Ghostscript fonts available to X11
- This package makes the 35 PostScript fonts from the gsfonts package
- available to your X server under their "urw" names and via
+Depends: fonts-urw-base35, ${misc:Depends}
+Description: Make fonts-urw-base35 fonts available to X11
+ This package makes the 35 PostScript fonts from the fonts-urw-base35
+ package available to your X server under their "urw" names and via
fonts.alias with the official "adobe" names, too.
.
This package does not contain any fonts itself but allows one to
- reuse the ghostscript fonts as X11 screen fonts.
+ reuse the fonts-urw-base35 fonts as classic X11 screen fonts.
diff --git a/debian/copyright b/debian/copyright
index b2a4ccb..11cc372 100644
--- a/debian/copyright
+++ b/debian/copyright
@@ -1,7 +1,7 @@
Format: https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/
Files: *
-Copyright: Copyright (c) 1999-2018 Roland Rosenfeld
+Copyright: Copyright (c) 1999-2022 Roland Rosenfeld
License: GPL-2
This program is free software; you can redistribute it and/or modify it
under the terms of the GNU General Public License as published by the
diff --git a/debian/rules b/debian/rules
index 56f905d..f9d07a5 100755
--- a/debian/rules
+++ b/debian/rules
@@ -1,6 +1,6 @@
#!/usr/bin/make -f
#
-# (C) 1999-2015 Roland Rosenfeld , based on
+# (C) 1999-2022 Roland Rosenfeld
#
# Uncomment this to turn on verbose mode.
#export DH_VERBOSE=1
@@ -12,9 +12,9 @@ debroot=`pwd`/debian/gsfonts-x11
dh $@
override_dh_install-indep:
- for f in `sed -e '1d;s/ .*//' < fonts.scale`; do \
- ln -sf ../../type1/gsfonts/$$f \
- $(debroot)/usr/share/fonts/X11/Type1/$$f; \
+ for f in `sed -e '1d;s/.pfb.*//' < fonts.scale`; do \
+ ln -sf ../../type1/urw-base35/$$f.t1 \
+ $(debroot)/usr/share/fonts/X11/Type1/$$f.pfb; \
done
perl -e 'my $$lines=""; my $$count=0; '\
diff --git a/fonts.scale b/fonts.scale
index ce08be0..58c457e 100644
--- a/fonts.scale
+++ b/fonts.scale
@@ -1,36 +1,36 @@
35
-a010013l.pfb -urw-urw gothic l-book-r-normal--0-0-0-0-p-0-iso8859-1
-a010015l.pfb -urw-urw gothic l-demibold-r-normal--0-0-0-0-p-0-iso8859-1
-a010033l.pfb -urw-urw gothic l-book-o-normal--0-0-0-0-p-0-iso8859-1
-a010035l.pfb -urw-urw gothic l-demibold-o-normal--0-0-0-0-p-0-iso8859-1
-b018012l.pfb -urw-urw bookman l-light-r-normal--0-0-0-0-p-0-iso8859-1
-b018015l.pfb -urw-urw bookman l-demibold-r-normal--0-0-0-0-p-0-iso8859-1
-b018032l.pfb -urw-urw bookman l-light-i-normal--0-0-0-0-p-0-iso8859-1
-b018035l.pfb -urw-urw bookman l-demibold-i-normal--0-0-0-0-p-0-iso8859-1
-c059013l.pfb -urw-century schoolbook l-regular-r-normal--0-0-0-0-p-0-iso8859-1
-c059016l.pfb -urw-century schoolbook
Bug#1017247: golang-github-gatherstars-com-jwz: FTBFS: dh_auto_test: error: cd _build && go test -vet=off -v -p 8 github.com/gatherstars-com/jwz github.com/gatherstars-com/jwz/examples/visualize retur
Hey Nilesh, Nilesh Patra, Aug 25, 2022 at 14:20: > This bug is causing an autoremoval warning for aerc. There does not seem to > be a fix > upstream about this. I am not sure what exactly is triggering this, but my > hunch > is it might be related to change in sort function with golang 1.19. > (This works fine with go-1.18) > > Can I ask you to take a look at it? I pushed a fix on salsa: https://salsa.debian.org/go-team/packages/golang-github-gatherstars-com-jwz/-/commit/842c69125282bdfb2725325d91d8002ce8f86891 This patch was submitted upstream: https://github.com/gatherstars-com/jwz/pull/2 If you want I can upload but you'll need to give me permission for golang-github-gatherstars-com-jwz :-) Cheers,
Bug#962686: RFP: s2geometry -- Computational geometry and spatial indexing on the sphere http://s2geometry.io/
There is a working, up to date packaging of s2geometry by the Mobian team here: https://salsa.debian.org/Mobian-team/packages/puremaps/s2geometry-deb It looks like the only thing this package needs is a sponsor.
Bug#779969: .NET 6 is available in Ubuntu
dotnet6 recently got packaged in Ubuntu repositories. See the news here: https://ubuntu.com/blog/install-dotnet-on-ubuntu The source package can be found here https://packages.ubuntu.com/source/jammy-updates/dotnet6
Bug#1018101: buster-pu: package kannel/1.4.5-2+deb10u1
Package: release.debian.org Severity: normal Tags: buster User: release.debian@packages.debian.org Usertags: pu X-Debbugs-Cc: Chris Hofstaedtler * Disable PostScript documentation generation to fix the build now that ImageMagick PostScript conversion is no longer permitted. (Closes: #991058) After this change kannel-docs no longer contains PostScript documentation, but the same documentation is still available as PDF. diff -Nru kannel-1.4.5/debian/changelog kannel-1.4.5/debian/changelog --- kannel-1.4.5/debian/changelog 2018-10-08 02:12:01.0 +0300 +++ kannel-1.4.5/debian/changelog 2022-08-25 20:00:58.0 +0300 @@ -1,3 +1,14 @@ +kannel (1.4.5-2+deb10u1) buster; urgency=medium + + * Non-maintainer upload. + + [ Robie Basak ] + * Disable PostScript documentation generation to fix the build now +that ImageMagick PostScript conversion is no longer permitted. +(Closes: #991058) + + -- Adrian Bunk Thu, 25 Aug 2022 20:00:58 +0300 + kannel (1.4.5-2) unstable; urgency=medium * Fix have kannel-dev depend on libssl-dev (not libssl1.0-dev). diff -Nru kannel-1.4.5/debian/patches/50_disable-ps-docs.patch kannel-1.4.5/debian/patches/50_disable-ps-docs.patch --- kannel-1.4.5/debian/patches/50_disable-ps-docs.patch1970-01-01 02:00:00.0 +0200 +++ kannel-1.4.5/debian/patches/50_disable-ps-docs.patch2022-08-25 20:00:58.0 +0300 @@ -0,0 +1,38 @@ +Description: disable build of PostScript documentation + The ImageMagick package in Ubuntu (but not Debian) no longer permits + conversion to or from PostScript, so we can no longer generate working + PostScript documentation. See the bug for the discussion on this. +Author: Robie Basak +Bug-Ubuntu: https://launchpad.net/bugs/1838425 +Forwarded: not-needed +Last-Update: 2019-07-30 + +--- a/Makefile.in b/Makefile.in +@@ -161,7 +161,7 @@ + man8pages = gw/kannel.8 + + docsrcs = $(wildcard grep -l '
Bug#1018100: ITP: liblanguage-detector-java -- Language Detection Library for Java
Package: wnpp Severity: wishlist Owner: Markus Koschany X-Debbugs-Cc: debian-de...@lists.debian.org, a...@debian.org,debian-j...@lists.debian.org * Package name: liblanguage-detector-java Version : 0.6 Upstream Author : Nakatani Shuyo, Francois ROLAND, Fabian Kessler, Nicole Torres, Robert Theis * URL : https://github.com/optimaize/language-detector * License : Apache-2.0 Programming Lang: Java Description : Language Detection Library for Java This software uses language profiles which were created based on common text for each language. N-grams, a contiguous sequence of n items from a given sample of text, were then extracted from that text and stored in the profiles. When trying to figure out in what language a certain text is written, the program goes through the same process: It creates the same kind of n-grams of the input text. Then it compares the relative frequency of them, and finds the language that matches best. Currently 71 languages are supported.
Bug#1018099: kannel-docs no longer contains the docs
Package: kannel-docs Version: 1.4.5-7 Severity: serious X-Debbugs-Cc: Robie Basak * Disable PostScript documentation generation to fix the build now that ImageMagick PostScript conversion is no longer permitted (LP: #1838425). * Drop Build-Depends-Indep on imagemagick since it is no required following the above change. Disabling generating the archaic PostScript is not a big loss as long as the PDF is still present. But dropping the Build-Depends-Indep on imagemagick made the package useless since it also disabled pdf/rtf/html generation due to https://sources.debian.org/src/kannel/1.4.5-9/configure.in/#L578-L581
Bug#991057: gri: diff for NMU version 2.12.27-1.1
Control: tags 991057 + pending Dear maintainer, I've prepared an NMU for gri (versioned as 2.12.27-1.1) and uploaded it to DELAYED/1. Please feel free to tell me if I should cancel it. cu Adrian diff -Nru gri-2.12.27/debian/changelog gri-2.12.27/debian/changelog --- gri-2.12.27/debian/changelog 2020-06-26 03:41:17.0 +0300 +++ gri-2.12.27/debian/changelog 2022-08-25 19:33:47.0 +0300 @@ -1,3 +1,11 @@ +gri (2.12.27-1.1) unstable; urgency=medium + + * Non-maintainer upload. + * Use ps2pdf instead of convert for converting from ps to pdf. +(Closes: #991057) + + -- Adrian Bunk Thu, 25 Aug 2022 19:33:47 +0300 + gri (2.12.27-1) unstable; urgency=medium * New upstream release. diff -Nru gri-2.12.27/debian/patches/imagemagick.patch gri-2.12.27/debian/patches/imagemagick.patch --- gri-2.12.27/debian/patches/imagemagick.patch 1970-01-01 02:00:00.0 +0200 +++ gri-2.12.27/debian/patches/imagemagick.patch 2022-08-25 19:33:47.0 +0300 @@ -0,0 +1,30 @@ +Description: Use ps2pdf instead of convert for converting from ps to pdf +Author: Adrian Bunk +Bug-Debian: https://bugs.debian.org/991057 + +--- gri-2.12.27.orig/doc/examples/Makefile.am gri-2.12.27/doc/examples/Makefile.am +@@ -78,8 +78,8 @@ DISTCLEANFILES = $(png_files) $(eps_file + %-tiny.png : %.png + -convert -strip -background white -geometry 90x999 $< $@ + %.pdf : %.ps +- convert $< $@ +-# ps2pdf $< $@ ++# convert $< $@ ++ ps2pdf $< $@ + %.html : %.gri + perl $(srcdir)/../gri2html $< $@ + all: html png eps txt +--- gri-2.12.27.orig/doc/screenshots/Makefile.am gri-2.12.27/doc/screenshots/Makefile.am +@@ -26,8 +26,8 @@ pdf: $(the_pdf_files) + -convert $< $@ + + %.pdf : %.eps +- convert $< $@ +-# ps2pdf $< $@ ++# convert $< $@ ++ ps2pdf $< $@ + + # This was good for color; + # now let's put them in grayscale for the PostScript manual diff -Nru gri-2.12.27/debian/patches/series gri-2.12.27/debian/patches/series --- gri-2.12.27/debian/patches/series 1970-01-01 02:00:00.0 +0200 +++ gri-2.12.27/debian/patches/series 2022-08-25 19:33:47.0 +0300 @@ -0,0 +1 @@ +imagemagick.patch
Bug#1013933: Keep xsane out of Debian releases
On 2022-06-27 19:25:13, Jörg Frings-Fürst wrote: > This is a placeholder RC bug to prevent xsane from entering testing > and making it to a Debian release. Xsane has not been maintained by > the Upstream author since 2014. Even the current fork does not show > much further development. > > Because of the bugs in the GUI I don't think the current version > is suitable for a Debian release. > > Should the fork develop positively, I will close this bug. Good to know, thanks! Are you aware of an alternative SANE GUI that would be a good replacement for xsane? -- Brief is this existence, as a fleeting visit in a strange house. The path to be pursued is poorly lit by a flickering consciousness. - Albert Einstein
Bug#1013063: w1retap: diff for NMU version 1.4.6-1.1
On Fri, Aug 19, 2022 at 10:36:16AM +0100, Thomas Stewart wrote: > On 18 Aug 2022, at 16:39, Adrian Bunk wrote: > > I've prepared an NMU for w1retap (versioned as 1.4.6-1.1) and uploaded > > it to DELAYED/14. Please feel free to tell me if I should cancel it. > > Thanks for that Adrain, it's been on my TODO list for far too long. Thanks, rescheduled for immediate upload. > Kind Regards cu Adrian
Bug#1010842: Info received (fail2ban not starting proftpd and sshd jails correctly)
Hi, is it possible, that iptables chains are created only when needed (ie. only when some ip should be banned?) Libor On St, 2022-05-11 at 12:15 +, Debian Bug Tracking System wrote: > Thank you for the additional information you have supplied regarding > this Bug report. > > This is an automatically generated reply to let you know your message > has been received. > > Your message is being forwarded to the package maintainers and other > interested parties for their attention; they will reply in due > course. > > Your message has been sent to the package maintainer(s): > Debian Python Team > > If you wish to submit further information on this problem, please > send it to 1010...@bugs.debian.org. > > Please do not send mail to ow...@bugs.debian.org unless you wish > to report a problem with the Bug-tracking system. >
Bug#1017030: dictd: yields "client_read_status: Connection reset by peer" in the client
On Thu, Aug 25, 2022 at 03:57:53PM +0200, Vincent Lefevre wrote: > If dictd is expected to be restarted on major libc6 upgrade, > I suppose that this bug should be reassigned to libc6. I strongly suspect that it should be restarted on libc6 upgrades, and that this was the cause of the bug, but I'm not the maintainer. Robert, do you agree with the assessment / should we reassign? Best, Ryan -- |)|/ Ryan Kavanagh | 4E46 9519 ED67 7734 268F |\|\ https://rak.ac | BD95 8F7B F8FC 4A11 C97A signature.asc Description: PGP signature
Bug#1018098: bullseye-pu: package foxtrotgps/1.2.2+bzr331-1~deb11u1
Package: release.debian.org
Severity: normal
Tags: bullseye moreinfo
User: release.debian@packages.debian.org
Usertags: pu
X-Debbugs-Cc: Paul Wise
- Fixes crash due to not unreferencing threads (see LP#1876744)
https://bugs.launchpad.net/foxtrotgps/+bug/1876744
The only difference between the packages in bullseye and bookworm
is that bookworm contains a fix for a regression that was introduced
in bullseye.
Paul, please ACK/NAK whether you as maintainer consider this appropriate.
diff -Nru foxtrotgps-1.2.2+bzr330/changelog/ChangeLog
foxtrotgps-1.2.2+bzr331/changelog/ChangeLog
--- foxtrotgps-1.2.2+bzr330/changelog/ChangeLog 2021-07-14 02:44:15.0
+0300
+++ foxtrotgps-1.2.2+bzr331/changelog/ChangeLog 2021-08-17 15:19:23.0
+0300
@@ -1,4 +1,24 @@
+revno: 331
+fixes bug: https://launchpad.net/bugs/1876744
+author: Jesse Gardner
+committer: Paul Wise
+branch nick: foxtrotgps
+timestamp: Mon 2021-08-16 23:01:48 -0700
+message:
+ Added g_thread_unref wherever g_thead_new is used
+
+ Fixes:
+ https://bazaar.launchpad.net/~foxtrotgps-team/foxtrotgps/trunk/revision/315
+ Cleanup-by: Paul Wise
+modified:
+ src/friends.c
+ src/geo_photos.c
+ src/gps_functions.c
+ src/hrm_functions.c
+ src/tile_management.c
+ src/tracks.c
+
revno: 330
committer: Paul Wise
branch nick: bzr
diff -Nru foxtrotgps-1.2.2+bzr330/debian/changelog
foxtrotgps-1.2.2+bzr331/debian/changelog
--- foxtrotgps-1.2.2+bzr330/debian/changelog2021-07-14 02:58:30.0
+0300
+++ foxtrotgps-1.2.2+bzr331/debian/changelog2022-08-25 19:15:51.0
+0300
@@ -1,3 +1,17 @@
+foxtrotgps (1.2.2+bzr331-1~deb11u1) bullseye; urgency=medium
+
+ * Non-maintainer upload.
+ * Rebuild for bullseye.
+
+ -- Adrian Bunk Thu, 25 Aug 2022 19:15:51 +0300
+
+foxtrotgps (1.2.2+bzr331-1) unstable; urgency=medium
+
+ * New upstream snapshot.
+- Fixes crash due to not unreferencing threads (see LP#1876744)
+
+ -- Paul Wise Tue, 17 Aug 2021 20:24:50 +0800
+
foxtrotgps (1.2.2+bzr330-1) unstable; urgency=medium
* New upstream snapshot.
diff -Nru foxtrotgps-1.2.2+bzr330/src/friends.c
foxtrotgps-1.2.2+bzr331/src/friends.c
--- foxtrotgps-1.2.2+bzr330/src/friends.c 2021-04-26 07:33:42.0
+0300
+++ foxtrotgps-1.2.2+bzr331/src/friends.c 2021-08-17 09:01:48.0
+0300
@@ -104,7 +104,10 @@
gtk_label_set_label (label_msg, _("Connecting..."));
#if GLIB_CHECK_VERSION(2,34,0)
- if (!g_thread_new("friends thread", _position_thread, (gpointer)
NULL) != 0)
+ GThread *gt = g_thread_new("friends thread", _position_thread,
(gpointer) NULL);
+ if (gt != 0)
+ g_thread_unref(gt);
+ else
#else
if (!g_thread_create(_position_thread, NULL, FALSE, NULL) != 0)
#endif
@@ -473,7 +476,10 @@
gtk_label_set_text (label_msg, _("Connecting..."));
#if GLIB_CHECK_VERSION(2,34,0)
- if (!g_thread_new("register nick thread", _nick_thread,
(gpointer) NULL) != 0)
+ GThread *gt=g_thread_new("register nick thread", _nick_thread,
(gpointer) NULL);
+ if (gt != 0)
+ g_thread_unref(gt);
+ else
#else
if (!g_thread_create(_nick_thread, NULL, FALSE, NULL) != 0)
#endif
@@ -705,7 +711,10 @@
postdata = create_msg_postdata(m);
#if GLIB_CHECK_VERSION(2,34,0)
- if (!g_thread_new("Mission thread", _send_message, postdata) !=
0)
+ GThread *gt = g_thread_new("Mission thread", _send_message,
postdata);
+ if (gt != 0)
+ g_thread_unref(gt);
+ else
#else
if (!g_thread_create(_send_message, postdata, FALSE, NULL) != 0)
#endif
diff -Nru foxtrotgps-1.2.2+bzr330/src/geo_photos.c
foxtrotgps-1.2.2+bzr331/src/geo_photos.c
--- foxtrotgps-1.2.2+bzr330/src/geo_photos.c2021-04-26 07:33:42.0
+0300
+++ foxtrotgps-1.2.2+bzr331/src/geo_photos.c2021-08-17 09:01:48.0
+0300
@@ -687,7 +687,7 @@
gtk_widget_hide(dialog_photo_correlate);
#if GLIB_CHECK_VERSION(2,34,0)
- g_thread_new("geocode thread", geocode_thread, (gpointer) NULL);
+ g_thread_unref(g_thread_new("geocode thread", geocode_thread,
(gpointer) NULL));
#else
g_thread_create(geocode_thread, NULL, FALSE, NULL);
#endif
diff -Nru foxtrotgps-1.2.2+bzr330/src/gps_functions.c
foxtrotgps-1.2.2+bzr331/src/gps_functions.c
--- foxtrotgps-1.2.2+bzr330/src/gps_functions.c 2021-04-26 07:33:42.0
+0300
+++ foxtrotgps-1.2.2+bzr331/src/gps_functions.c 2021-08-17 09:01:48.0
+0300
@@ -849,7 +849,7 @@
}
#if GLIB_CHECK_VERSION(2,34,0)
- g_thread_new("gps thread", _gps_thread, (gpointer)NULL);
+ g_thread_unref(g_thread_new("gps thread", _gps_thread,
(gpointer)NULL));
#else
g_thread_create(_gps_thread, NULL, FALSE, NULL);
#endif
diff -Nru foxtrotgps-1.2.2+bzr330/src/hrm_functions.c
Bug#1018097: buster-pu: package foxtrotgps/1.2.1-1+deb10u1
Package: release.debian.org Severity: normal Tags: buster User: release.debian@packages.debian.org Usertags: pu X-Debbugs-Cc: Paul Wise * Add upstream fix for FTBFS with new imagemagick. (Closes: #991056) diff -Nru foxtrotgps-1.2.1/debian/changelog foxtrotgps-1.2.1/debian/changelog --- foxtrotgps-1.2.1/debian/changelog 2018-04-10 05:39:03.0 +0300 +++ foxtrotgps-1.2.1/debian/changelog 2022-08-25 19:09:09.0 +0300 @@ -1,3 +1,10 @@ +foxtrotgps (1.2.1-1+deb10u1) buster; urgency=medium + + * Non-maintainer upload. + * Add upstream fix for FTBFS with new imagemagick. (Closes: #991056) + + -- Adrian Bunk Thu, 25 Aug 2022 19:09:09 +0300 + foxtrotgps (1.2.1-1) unstable; urgency=medium * New upstream release diff -Nru foxtrotgps-1.2.1/debian/patches/imagemagick.patch foxtrotgps-1.2.1/debian/patches/imagemagick.patch --- foxtrotgps-1.2.1/debian/patches/imagemagick.patch 1970-01-01 02:00:00.0 +0200 +++ foxtrotgps-1.2.1/debian/patches/imagemagick.patch 2022-08-25 19:09:07.0 +0300 @@ -0,0 +1,14 @@ +=== modified file 'doc/Makefile.am' +--- a/doc/Makefile.am 2013-09-16 02:09:13 + b/doc/Makefile.am 2021-04-26 04:33:42 + +@@ -6,7 +6,8 @@ + + info_TEXINFOS = foxtrotgps.texi + +-foxtrotgps_TEXINFOS = $(images) $(images_eps) ++foxtrotgps_TEXINFOS = $(images) ++DVIS = $(images_eps) foxtrotgps.dvi + + images = \ + foxtrotgps-logo.png \ + diff -Nru foxtrotgps-1.2.1/debian/patches/series foxtrotgps-1.2.1/debian/patches/series --- foxtrotgps-1.2.1/debian/patches/series 1970-01-01 02:00:00.0 +0200 +++ foxtrotgps-1.2.1/debian/patches/series 2022-08-25 19:08:59.0 +0300 @@ -0,0 +1 @@ +imagemagick.patch
Bug#1017434: speedtest-cli: error message "Cannot retrieve speedtest configuration"
Control: severity -1 normal On 2022-08-24 17:15:20, Antoine Beaupré wrote: > Control: tags -1 +unreproducible > > It's funny, I had this exact same problem earlier, and now it's > gone. Maybe it's a transient issue with speedtest.net itself? I still can't reproduce this. I can only assume it was a glitch on the speedtest website, because things are back to normal now. Maybe the bug here is "there should be better feedback to the user when the site crashes", but that certainly doesn't warrant the current severity. a. -- Dr. King’s major assumption was that if you are nonviolent, if you suffer, your opponent will see your suffering and will be moved to change his heart. He only made one fallacious assumption: In order for nonviolence to work, your opponent must have a conscience. The United States has none.- Stokely Carmichael
Bug#1018096: buster-pu: package ftgl/2.4.0-2.1~deb10u1
Package: release.debian.org Severity: normal Tags: buster User: release.debian@packages.debian.org Usertags: pu * Don't try to convert PNG to EPS for latex, as our imagemagick has EPS disabled for security reasons and it seems to work without them. (Closes: #991053) diff -Nru ftgl-2.4.0/debian/changelog ftgl-2.4.0/debian/changelog --- ftgl-2.4.0/debian/changelog 2019-02-26 17:52:23.0 +0200 +++ ftgl-2.4.0/debian/changelog 2022-08-25 18:57:23.0 +0300 @@ -1,3 +1,21 @@ +ftgl (2.4.0-2.1~deb10u1) buster; urgency=medium + + * Non-maintainer upload. + * Rebuild for buster. + + -- Adrian Bunk Thu, 25 Aug 2022 18:57:23 +0300 + +ftgl (2.4.0-2.1) unstable; urgency=medium + + * Non-maintainer upload + + [ William Grant ] + * Don't try to convert PNG to EPS for latex, as our imagemagick has EPS +disabled for security reasons and it seems to work without them. (Closes: +#991053) + + -- Sebastian Ramacher Mon, 26 Jul 2021 22:41:23 +0200 + ftgl (2.4.0-2) unstable; urgency=medium * Install ftgl.pdf file again, the external problem generating PDF file diff -Nru ftgl-2.4.0/debian/patches/no-eps.patch ftgl-2.4.0/debian/patches/no-eps.patch --- ftgl-2.4.0/debian/patches/no-eps.patch 1970-01-01 02:00:00.0 +0200 +++ ftgl-2.4.0/debian/patches/no-eps.patch 2021-07-26 23:40:30.0 +0300 @@ -0,0 +1,13 @@ +Index: ftgl-2.4.0/docs/Makefile.am +=== +--- ftgl-2.4.0.orig/docs/Makefile.am ftgl-2.4.0/docs/Makefile.am +@@ -26,7 +26,7 @@ endif + touch $@ + + html/doxygen.css: stamp-doxygen +-stamp-doxygen: doxygen.cfg stamp-eps ++stamp-doxygen: doxygen.cfg + $(DOXYGEN) $^ + for file in html/*html; do \ + $(SED) -e 's/%FTGL/FTGL/' < $$file > $$file.tmp; \ diff -Nru ftgl-2.4.0/debian/patches/series ftgl-2.4.0/debian/patches/series --- ftgl-2.4.0/debian/patches/series2019-02-26 17:28:55.0 +0200 +++ ftgl-2.4.0/debian/patches/series2021-07-26 23:40:30.0 +0300 @@ -1 +1,2 @@ fix-doc-projects-eman2.patch +no-eps.patch
