Bug#1063361: nvidia-graphics-drivers-tesla-470: autopkgtest needs update for new version of linux

[Florian Ernst]

Control: tag 1063361 + bookworm

On Sat, Feb 10, 2024 at 03:49:45PM +0100,  wrote:
> Control: found 1063361 470.223.02-2~deb12u1
> [...]
> Thus now marking this bug accordingly.

Not quite, but hopefully now.

FWIW, manually adding 0035-fix-build-w-kernel-6.1.76-6.6.15-6.7.3.patch[0]
fixes the build for me on bookworm as well.

Cheers,
Flo

[0] 
https://sources.debian.org/src/nvidia-graphics-drivers-tesla-470/470.223.02-4/debian/module/debian/patches/0035-fix-build-w-kernel-6.1.76-6.6.15-6.7.3.patch/


signature.asc
Description: PGP signature

Bug#1063361: nvidia-graphics-drivers-tesla-470: autopkgtest needs update for new version of linux

[Florian Ernst]

Control: found 1063361 470.223.02-2~deb12u1

On Tue, Feb 06, 2024 at 09:18:15PM +0100, Paul Gevers wrote:
> Source: nvidia-graphics-drivers-tesla-470
> Version: 470.223.02-3
> Severity: serious
> X-Debbugs-CC: li...@packages.debian.org
> Tags: sid trixie
> User: debian...@lists.debian.org
> Usertags: needs-update
> Control: affects -1 src:linux
> [...]
> 320s # MODPOST
> /var/lib/dkms/nvidia-tesla-470/470.223.02/build/Module.symvers
> 320sscripts/mod/modpost -M -m   -o
> /var/lib/dkms/nvidia-tesla-470/470.223.02/build/Module.symvers -T
> /var/lib/dkms/nvidia-tesla-470/470.223.02/build/modules.order -i
> Module.symvers -e
> 320s ERROR: modpost: GPL-incompatible module nvidia.ko uses GPL-only symbol
> '__rcu_read_unlock'
> 320s ERROR: modpost: GPL-incompatible module nvidia.ko uses GPL-only symbol
> '__rcu_read_lock'
> 320s make[4]: ***
> [/usr/src/linux-headers-6.6.15-common/scripts/Makefile.modpost:145:
> /var/lib/dkms/nvidia-tesla-470/470.223.02/build/Module.symvers] Error 1

Well, now that Linux 6.1.76 has entered Bookworm as part of today's
point release[0] this bug eccurs there as well. Here the end of my
/var/lib/dkms/nvidia-tesla-470/470.223.02/build/make.log:

| sh /usr/src/linux-headers-6.1.0-18-common/scripts/modules-check.sh 
/var/lib/dkms/nvidia-tesla-470/470.223.02/build/modules.order
| make -f /usr/src/linux-headers-6.1.0-18-common/scripts/Makefile.modpost
|sed 's/ko$/o/'  
/var/lib/dkms/nvidia-tesla-470/470.223.02/build/modules.order | 
scripts/mod/modpost -m -o 
/var/lib/dkms/nvidia-tesla-470/470.223.02/build/Module.symvers -e -i 
Module.symvers -T -
| ERROR: modpost: GPL-incompatible module nvidia.ko uses GPL-only symbol 
'__rcu_read_lock'
| ERROR: modpost: GPL-incompatible module nvidia.ko uses GPL-only symbol 
'__rcu_read_unlock'
| make[3]: *** 
[/usr/src/linux-headers-6.1.0-18-common/scripts/Makefile.modpost:126: 
/var/lib/dkms/nvidia-tesla-470/470.223.02/build/Module.symvers] Error 1
| make[2]: *** [/usr/src/linux-headers-6.1.0-18-common/Makefile:1991: modpost] 
Error 2
| make[2]: Leaving directory '/usr/src/linux-headers-6.1.0-18-amd64'
| make[1]: *** [Makefile:250: __sub-make] Error 2
| make[1]: Leaving directory '/usr/src/linux-headers-6.1.0-18-common'
| make: *** [Makefile:80: modules] Error 2

Thus now marking this bug accordingly.

Cheers,
Flo


[0] 
https://tracker.debian.org/news/1499745/accepted-linux-6176-1-source-into-proposed-updates/


signature.asc
Description: PGP signature

Bug#1031291: uchardet: New upstream release (0.0.8, 2022-12-08)

[Florian Ernst]

Hello James,

On Sun, Jul 09, 2023 at 03:54:18PM +0200, Florian Ernst wrote:
> [...]
> However, I was wondering what your plans with respect to this package
> are, for I didn't notice much Debian activity from your side recently.
> Maybe I simply failed to look at the correct places, and if so I
> apologize for the notion. But maybe you are indeed busy with other
> things, and if so, I'd like to offer to help out and/or take over,
> depending on your preferences. Please just let me know.

Could you please comment on this. Thank you.

Cheers,
Flo


signature.asc
Description: PGP signature

Bug#1009232: libxslt: New upstream release (v1.1.35, 2022 Feb 16), not detected by debian/watch

[Florian Ernst]

Control: retitle -1 libxslt: New upstream release (v1.1.38, 2023-May-08)

On Sat, Apr 09, 2022 at 02:41:44PM +0200, Mattia Rizzolo wrote:
> On Sat, Apr 09, 2022 at 01:05:20PM +0200, Florian Ernst wrote:
> > there is a new upstream release available, cf.
> > <https://gitlab.gnome.org/GNOME/libxslt/-/tags>.
> 
> Thank you, I had indeed missed this release…

Apparently this version was also uploaded soon after, cf.
<https://tracker.debian.org/news/1346162/accepted-libxslt-1135-1-source-into-unstable/>,
including an updated debian/watch.

However, the latter now indicates the availability of 1.1.38, hence
just updating this bug's title accordingly.

Cheers,
Flo


signature.asc
Description: PGP signature

Bug#1040993: libcbor: New upstream release (0.10.2, 2023-01-31)

[Florian Ernst]

Source: libcbor
Version: 0.8.0-2
Severity: wishlist

Dear maintainer,

there are several new upstream releases available at
, their changes read

| 0.10.2 (2023-01-31)
| - Fixed minor test bug causing failures for x86 Linux (discovered by
|   trofi)
|   - Actual libcbor functionality not affected, bug was in the test suite
| - Made tests platform-independent
| 
| 0.10.1 (2022-12-30)
| - Fix a regression in cbor_serialize_alloc that caused serialization of
|   zero-length strings and bytestrings or byte/strings with zero-length
|   chunks to fail (discovered by martelletto)
| 
| 0.10.0 (2022-12-29)
| - Make the buffer_size optional in cbor_serialize_alloc [#205] (by
|   hughsie)
| - BREAKING: Improved half-float encoding for denormalized numbers.
|   [#208] (by ranvis)
|   - Denormalized half-floats will now preserve data in the mantissa
|   - Note: Half-float NaNs still lose data (#215)
| - BUILD BREAKING: Minimum CMake version is 3.0 [#201] (by thewtex@)
|   - See https://repology.org/project/cmake/versions for support; the
| vast majority of users should not be affected.
| - Fix a potential memory leak when the allocator fails during array or
|   map decoding [#224] (by James-ZHANG)
| - Fix a memory leak when the allocator fails when adding chunks to
|   indefinite bytestrings. (discovered by James-ZHANG)
| - Fix a memory leak when the allocator fails when adding chunks to
|   indefinite strings
| - Potentially BUILD BREAKING: Add nodiscard attributes to most functions
|   - Warning: This may cause new build warnings and (in rare cases,
| depending on your configuration) errors
| - BREAKING: Fix cbor_copy leaking memory and creating invalid items when
|   the allocator fails.
|   - Previously, the failures were not handled in the interface. Now,
| cbor_copy may return NULL upon failure; clients should check the
| return value
| - Fix cbor_build_tag illegal memory behavior when the allocator fails
| - Add a new cbor_serialized_size API
| - Reworked cbor_serialize_alloc to allocate the exact amount of memory
|   necessary upfront
|   - This should significantly speed up cbor_serialize_alloc for large
| items by avoiding multiple reallocation iterations
|   - Clients should not use the return value of cbor_serialize_alloc. It
| may be removed in the future.
| - BUILD BREAKING: Deprecate CBOR_CUSTOM_ALLOC
|   - cbor_set_allocs will always be enabled from now on
|   - Note: The flag will be kept as a no-op triggering a warning when
| used for one version and then removed completely
| 
| 0.9.0 (2021-11-14)
| - Improved pkg-config paths handling [#164] (by jtojnar@)
| - Use explicit math.h linkage [#170]
| - BREAKING: Fixed handling of items that exceed the host size_t range
|   [#186]
|   - Callbacks for bytestrings, strings, arrays, and maps use uint64_t
| instead of size_t to allow handling of large items that exceed
| size_t even if size_t < uint64_t
|   - cbor_decode explicitly checks size to avoid overflows (previously
| broken, potentially resulting in erroneous decoding on affected
| systems)
|   - The change should be a noop for 64b systems
| - Added a Bazel build example [#196] (by andyjgf@)

Well, those contain quite some changes marked as BREAKING which might
complicate things.

Please update the package when you think it is due time.

Cheers,
Flo


signature.asc
Description: PGP signature

Bug#1040989: libcdr: New upstream release (0.1.7, 26-Mar-2021)

[Florian Ernst]

Source: libcdr
Version: 0.1.6-2
Severity: wishlist

Dear maintainer,

there is a new upstream release available at
, containing various fixes.

Please update the package when you think it is due time.

Cheers,
Flo


signature.asc
Description: PGP signature

Bug#1040987: cabextract: New upstream release (1.11, 24 February 2023)

[Florian Ernst]

Source: cabextract
Version: 1.9-3
Severity: wishlist

Dear maintainer,

there is a two new upstream releases available at
, their changes include

| Changes in cabextract 1.11
| - A bug introduced in cabextract 1.10 was fixed: it did not create
|   directory paths when extracting files
| Changes in cabextract 1.10
| - Multiple --filter options can be given. cabextract will extract files
|   matching any of the filters
| - cabextract now overwrites symlinks by default, both directories and
|   files. This is to be consistent with other archive tools. This does
|   not affect symlinks that are part of the --directory option
| - New --keep-symlinks option for the old behaviour of keeping symlinks
|   and following them when extracting files
| - New --interactive option to prompt you whether to overwrite existing
|   files
| - New --no-overwrite option to never overwrite existing files. The
|   default behaviour remains that existing files are overwritten
|   automatically

Please update the package when you think it is due time.

Cheers,
Flo


signature.asc
Description: PGP signature

Bug#1040986: ipcalc: New upstream release (0.51, 2021 Nov 3)

[Florian Ernst]

Source: ipcalc
Version: 0.42-2
Severity: wishlist

Dear maintainer,

there is a new upstream release available at
 (as linked to from
), apparently consolidating many patches
(including some from you) and applying some further changes.

Please update the package when you think it is due time.

Cheers,
Flo


signature.asc
Description: PGP signature

Bug#1040985: metis: New upstream release (v5.2.1, 2022 Dec 5)

[Florian Ernst]

Source: metis
Version: 5.1.0.dfsg-7
Severity: wishlist

Dear maintainer,

there is a new upstream release available at
 provided by one of the
original authors, cf. .

Please update the package when you think it is due time.

Cheers,
Flo


signature.asc
Description: PGP signature

Bug#1040984: lsyncd: New upstream release (2.3.1, 2022 Nov 17)

[Florian Ernst]

Source: lsyncd
Version: 2.2.3-1
Severity: wishlist

Dear maintainer,

there are two new upstream releases available at
, their changes include

| 2.3.1 - Squeaker Latest
| - multiple bugfixes
| - code cleanup
| 
| 2.3.0 - Spell of Resurrection
| This is the first release since quite a while and under new the new 
maintainer @poelzi
| Not only does the release fix many outstanding issues, it also contains quite 
a few additions.
| 
| Whats new
| - nix flake support
| - support for tunnel commands
| - support for batchSizeLimit
| - -onepass option
| - crontab support
| - support relative executable paths
| What's Changed
| - Fix typo: width => with by @msabramo in #380
| - default.collect: Print target by @msabramo in #379
| - Fix typo: Exlcusions => Exclusions by @msabramo in #378
| - Updated lbash.lua and lrsync.lau to remove the equals (=) by @mralexjuarez 
in #398
| - fix: direct mode allows injecting unauthorized filesystem operations by 
@wodny in #349
| - config file url by @gsouf in #459
| - Add example config for syncing with an AWS S3 bucket by @danielkza in #463
| - Fix for non-versioned lua not being searched in Cmake by @yokogawa-k in #500
| - Enable ssh._extra args by @taylor-s-dean in #583
| - Remove /System/Volumes/Data from fsevent paths on macOS by @ajdavis in #615
| - version format in lua.h changed by @j1cken in #568
| - add -onepass option, allowing exit after initial sync by @cleary in #541
| - Expose rsync's copy_unsafe_links by @rotu in #567
| - Fixed typo at readme.md by @schneiderl in #538
| - allow deleting excluded files with rsync by @tomjnixon in #595
| - fix error - bad binary format (version mismatch) by @CoolTuxNet in #656

Please update the package when you think it is due time.

Cheers,
Flo


signature.asc
Description: PGP signature

Bug#1040982: libexttextcat: New upstream release (3.4.6, 08-Nov-2021)

[Florian Ernst]

Source: libexttextcat
Version: 3.4.5-1
Severity: wishlist

Dear maintainer,

there is a new upstream release available at
, adding support for
some more languages / variants.

Please update the package when you think it is due time.

Cheers,
Flo


signature.asc
Description: PGP signature

Bug#1040695: libvidstab: New upstream release (v1.1.1, 2022 May 30)

[Florian Ernst]

Source: libvidstab
Version: 1.1.0-2
Severity: wishlist

Dear maintainer,

there is a new upstream release available, cf.

(as referenced from
).

Please update the packaging when you think it is due time.

Cheers,
Flo


signature.asc
Description: PGP signature

Bug#1036456: unblock: libfastjson/1.2304.0-1

[Florian Ernst]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
X-Debbugs-Cc: libfastj...@packages.debian.org, bi...@debian.org
Control: affects -1 + libfastjson

Please unblock package libfastjson

A new upstream version of libfastjson fixes a security bug
(CVE-2020-12762, #1035302). They also changed the release numbering,
hence the seemingly huge jump, but the actual diff is quite small.

[ Reason ]
"Prevent signed integer overflows with large buffers", as upstream
states inline, cf.
.
.

[ Impact ]
Without this change the above vulnerability remains. However, according
to upstream rsyslog - the main and almost sole user of this library -
was not affected anyways due to size limits.

[ Tests ]
There is some coverage via upstream's tests/test_printbuf.c that is run
during build time. The code in question is also tested in json-c, cf.
.

[ Risks ]
Via rsyslog this library is a key package. However, the new code merely
adds some straightforward checks against signed integer overflows, which
are already part of json-c in buster, bullseye, bookworm, and sid, cf.
.
The new libfastjson release has entered unstable 18 days ago, and so far
no bugs seem to have surfaced due to this change.

[ Checklist ]
  [x] all changes are documented in the d/changelog
  [x] I reviewed all changes and I approve them (disclaimer below)
  [x] attach debdiff against the package in testing

I am not the package maintainer but merely the bug submitter. However,
Michael expressed he wouldn't object if I want to pursue this, cf.
.

unblock libfastjson/1.2304.0-1
diff -Nru libfastjson-0.99.9/ChangeLog libfastjson-1.2304.0/ChangeLog
--- libfastjson-0.99.9/ChangeLog2021-01-25 13:52:55.0 +0100
+++ libfastjson-1.2304.0/ChangeLog  2023-04-17 15:51:20.0 +0200
@@ -1,3 +1,8 @@
+1.2304.0, 2023-04-18
+- change of release number scheme, now like rsyslog
+- fix Fix CVE-2020-12762
+  Note: the CVE did not affect rsyslog use due to size limits
+  Thanks to Wang Haitao for the patch.
 0.99.9 2021-01-26
 - add API fjson_object_get_uint()
   Thanks to Janmejay Singh for contributing the patch.
diff -Nru libfastjson-0.99.9/configure libfastjson-1.2304.0/configure
--- libfastjson-0.99.9/configure2021-01-25 13:53:09.0 +0100
+++ libfastjson-1.2304.0/configure  2023-04-17 15:54:00.0 +0200
@@ -1,6 +1,6 @@
 #! /bin/sh
 # Guess values for system-dependent variables and create Makefiles.
-# Generated by GNU Autoconf 2.69 for libfastjson 0.99.9.
+# Generated by GNU Autoconf 2.69 for libfastjson 1.2304.0.
 #
 # Report bugs to .
 #
@@ -590,8 +590,8 @@
 # Identity of this package.
 PACKAGE_NAME='libfastjson'
 PACKAGE_TARNAME='libfastjson'
-PACKAGE_VERSION='0.99.9'
-PACKAGE_STRING='libfastjson 0.99.9'
+PACKAGE_VERSION='1.2304.0'
+PACKAGE_STRING='libfastjson 1.2304.0'
 PACKAGE_BUGREPORT='rsys...@lists.adiscon.com'
 PACKAGE_URL=''
 
@@ -1336,7 +1336,7 @@
   # Omit some internal or obsolete options to make the list less imposing.
   # This message is too long to be a string in the A/UX 3.1 sh.
   cat <<_ACEOF
-\`configure' configures libfastjson 0.99.9 to adapt to many kinds of systems.
+\`configure' configures libfastjson 1.2304.0 to adapt to many kinds of systems.
 
 Usage: $0 [OPTION]... [VAR=VALUE]...
 
@@ -1407,7 +1407,7 @@
 
 if test -n "$ac_init_help"; then
   case $ac_init_help in
- short | recursive ) echo "Configuration of libfastjson 0.99.9:";;
+ short | recursive ) echo "Configuration of libfastjson 1.2304.0:";;
esac
   cat <<\_ACEOF
 
@@ -1525,7 +1525,7 @@
 test -n "$ac_init_help" && exit $ac_status
 if $ac_init_version; then
   cat <<\_ACEOF
-libfastjson configure 0.99.9
+libfastjson configure 1.2304.0
 generated by GNU Autoconf 2.69
 
 Copyright (C) 2012 Free Software Foundation, Inc.
@@ -1948,7 +1948,7 @@
 This file contains any messages produced by compilers while
 running configure, to aid debugging if configure makes a mistake.
 
-It was created by libfastjson $as_me 0.99.9, which was
+It was created by libfastjson $as_me 1.2304.0, which was
 generated by GNU Autoconf 2.69.  Invocation command line was
 
   $ $0 $@
@@ -2838,7 +2838,7 @@
 
 # Define the identity of the package.
  PACKAGE='libfastjson'
- VERSION='0.99.9'
+ VERSION='1.2304.0'
 
 
 cat >>confdefs.h <<_ACEOF
@@ -15280,7 +15280,7 @@
 # report actual input values of CONFIG_FILES etc. instead of their
 # values after options handling.
 ac_log="
-This file was extended by libfastjson $as_me 0.99.9, which was
+This file was extended by libfastjson $as_me 1.2304.0, which was
 generated by GNU Autoconf 2.69.  Invocation command line was
 
   CONFIG_FILES= $CONFIG_FILES
@@ -15346,7 

Bug#1031359: mjpegtools: New upstream release (2.2.1, 2021-09-05)

[Florian Ernst]

Source: mjpegtools
Version: 1:2.1.0+debian-7
Severity: wishlist

Dear maintainer,

there is a new upstream release available, cf.
,
containing "a lot of fixes and a lot of cleanup since the last (2.1.0)
release".

Please update the package when you think it is due time.

Cheers,
Flo


signature.asc
Description: PGP signature

Bug#1004588: libzip: New upstream release (1.8.0, 2021 Jun 18)

[Florian Ernst]

Control: retitle -1 libzip: New upstream release (1.9.2, 2022 Jun 28)

Dear maintainer,

by now there are several new upstream releases available, cf.
.

The additional changes contain

| libzip 1.9.2
| June 28, 2022
| Fix version number in header file.
| 
| libzip 1.9.1
| June 28, 2022
| Fix zip_file_is_seekable().
| 
| libzip 1.9.0
| June 13, 2022
| Add zip_file_is_seekable().
| Improve compatibility with WinAES.
| Fix encoding handling in zip_name_locate().
| Add option to zipcmp to output summary of changes.
| Various bug fixes and documentation improvements.

which seem nice enough to eventually have in Debian.

Please update the package when you think it is due time.

Cheers,
Flo


signature.asc
Description: PGP signature

Bug#1031291: uchardet: New upstream release (0.0.8, 2022-12-08)

[Florian Ernst]

Source: uchardet
Version: 0.0.7-1
Severity: wishlist

Dear maintainer,

there is a new upstream release available, cf.
:

| - New supports:
|   * Norwegian: IBM865, ISO-8859-1, ISO-8859-15 and WINDOWS-1252.
|   * Danish: IBM865.
| - Minimum CMake version bumped to 3.1 (requirement was 2.8.5 before) to
|   have CMake exported targets:
|   * The executable uchardet::uchardet
|   * The library uchardet::libuchardet
|   * The static library uchardet::libuchardet_static
| - Fix build issues for UWP on Windows.
| - Add uchardet CLI tool building support for MSVC.
| - Various bug fixes and docs/README tweaks.

Please update the package when you think it is due time.

Cheers,
Flo


signature.asc
Description: PGP signature

Bug#1031226: librabbitmq: New upstream release (0.13.0, 2023 Feb 06)

[Florian Ernst]

Source: librabbitmq
Version: 0.11.0-1
Severity: wishlist

Dear maintainer,

there is a new upstream release available which uscan did not detect,
cf. .

The changes contain

| rabbitmq-c v0.13.0 Latest
|  Fixed
|   Fixed missing option to not install static library (#665)
|   Missing pkgconfig version in v0.12.0 output (#755, #751)
|   Correct return value from amqp_ssl_socket_set_key_buffer (#723)
|  Changed
|   Remove OpenSSL code no longer needed when used with OpenSSL >= 1.1.0.
|   (Fixed: #715, #737)
|  Added
|   Integration with OSS-Fuzz (#736)
| 
| rabbitmq-c v0.12.0
|  Changed
|   rabbitmq-c now compiles as C99
|   CMake 3.12 is new minimum required version
|   CMake -DBUILD_TESTS renamed to -DBUILD_TESTING
|   CMake -DBUILD_EXAMPLES now defaults to OFF
|   CMake -DBUILD_TOOLS now defaults to OFF
|   Unix library version now matches the release version, SONAME remains the
|   same.
|   Modernized CMake scripts to better adopt modern standards
|   Public headers have moved to rabbitmq-c/ directory
|   Dropped support for MSVC older than VS 2010
|   Dropped support for OpenSSL v1.1.0 and older
|   Minimum SSL version set to TLSv1.2
|   Updated to RabbitMQ framing to v3.8.19

Please update the package when you think it is due time.

Cheers,
Flo


signature.asc
Description: PGP signature

Bug#1027970: lcms2: New upstream release (2.14, 2022-11-01)

[Florian Ernst]

Dear Maintainer,

thank you for updating the package.

On Thu, Jan 05, 2023 at 12:31:24PM +0100, Florian Ernst wrote:
> there is a new upstream release available, cf.
> <https://github.com/mm2/Little-CMS/releases>. Its Changes include
> | - lcms2 now implements ICC specification 4.4
> | - New multi-threaded plug-in
> | [...]
> | ICC Version 4.4 and the multithreaded plug-in are important milestones.

Please note that debian/copyright now states that this new
multi-threaded plug-in is licensed under the MIT license whereas it
should be GPL-3. Please find attached a revised patch
"2.14-copyright.diff" fixing this (and in another chunk also updating
the copyright year of your packaging, just because I still had this in a
local branch and it thus showed up in the diff).

Cheers,
Flo
diff --git a/debian/copyright b/debian/copyright
index c76cdfc..cb36b91 100644
--- a/debian/copyright
+++ b/debian/copyright
@@ -23,7 +23,7 @@ License: MIT
  OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
  SOFTWARE.
 
-Files: plugins/fast_float/*
+Files: plugins/fast_float/* plugins/threaded/*
 Copyright: 1998-2022 Marti Maria Saguer 
 License: GPL-3
  This package is free software: you can redistribute it and/or modify
@@ -92,7 +92,7 @@ License: IJG
 
 Files: debian/*
 Copyright: 2011 Oleksandr Moskalenko 
-   2013-2022 Thomas Weber 
+   2013-2023 Thomas Weber 
 License: GPL-2+
  This package is free software; you can redistribute it and/or modify
  it under the terms of the GNU General Public License as published by


signature.asc
Description: PGP signature

Bug#1027970: lcms2: New upstream release (2.14, 2022-11-01)

[Florian Ernst]

ug reports etc. send mail to
-i...@littlecms.com.
-.SH SEE ALSO
-.BR jpgicc (1),
-.BR tificc (1),
-.BR psicc (1),
-.BR transicc (1),
-.SH AUTHOR
-This manual page was written by Shiju p. Nair ,
-for the Debian project.
diff --git a/debian/man/psicc.1 b/debian/man/psicc.1
deleted file mode 100644
index 269b856..000
--- a/debian/man/psicc.1
+++ /dev/null
@@ -1,40 +0,0 @@
-.\"Shiju P. Nair September 30, 2004
-.TH PSICC 1 "September 30, 2004"
-.SH NAME
-psicc - little cms PostScript converter.
-.SH SYNOPSIS
-.B psicc
-.RI [ options ]
-.SH DESCRIPTION
-lcms is a standalone CMM engine, which deals with the color management.
-It implements a fast transformation between ICC profiles.
-.B psicc 
-is little cms PostScript converter.
-.SH OPTIONS
-.TP
-.B \-b 
-Black point compensation (CRD only).
-.TP
-.BI \-i\  profile
-Input profile: Generates Color Space Array (CSA).
-.TP
-.BI \-o\  profile
-.TP
-Output profile: Generates Color Rendering Dictionary(CRD).
-.TP
-.B \-t <0,1,2,3>
-Intent (0=Perceptual, 1=Colorimetric, 2=Saturation, 3=Absolute).
-.TP
-.B \-u 
-Do NOT generate resource name on CRD.
-.SH NOTES
-For suggestions, comments, bug reports etc. send mail to
-i...@littlecms.com.
-.SH SEE ALSO
-.BR jpgicc (1),
-.BR tificc (1),
-.BR linkicc (1),
-.BR transicc (1),
-.SH AUTHOR
-This manual page was written by Shiju p. Nair ,
-for the Debian project.
diff --git a/debian/man/transicc.1 b/debian/man/transicc.1
deleted file mode 100644
index 7e2952a..000
--- a/debian/man/transicc.1
+++ /dev/null
@@ -1,60 +0,0 @@
-.\"Shiju P. Nair September 30, 2004
-.TH TRANSICC 1 "September 30, 2004"
-.SH NAME
-transicc - little cms ColorSpace conversion calculator.
-.SH SYNOPSIS
-.B transicc
-.RI [ options ]
-.SH DESCRIPTION
-lcms is a standalone CMM engine, which deals with the color management.
-It implements a fast transformation between ICC profiles.
-.B transicc 
-is lcms ColorSpace conversion calculator.
-.SH OPTIONS
-.TP
-.B \-%
-use percent % of ink.
-.TP
-.B \-b 
-Black point compensation.
-.TP
-.B \-c <0,1,2,3>
-Precalculates transform. (0=Off, 1=Normal, 2=Hi-res, 3=LoRes) [defaults to 1]
-.TP
-.BI \-i\  profile
-Input profile (defaults to sRGB).
-.TP
-.B \-l
-Transform by device-link profile.
-.TP
-.B \-n
-Terse output, intended for pipe usage.
-.TP
-.BI \-o\  profile
-.TP
-Output profile (defaults to sRGB).
-.TP
-.B \-t <0,1,2,3>
-Intent (0=Perceptual, 1=Colorimetric, 2=Saturation, 3=Absolute).
-.TP
-.B \-v
-Verbose.
-.TP
-.B \-w
-Use 16 bits.
-.TP
-.B \-x
-Hexadecimal.
-.TP
-You can use '*Lab' and '*xyz' as built-in profiles.
-.SH NOTES
-For suggestions, comments, bug reports etc. send mail to
-i...@littlecms.com.
-.SH SEE ALSO
-.BR jpgicc (1),
-.BR tificc (1),
-.BR psicc (1),
-.BR linkicc (1),
-.SH AUTHOR
-This manual page was written by Shiju p. Nair ,
-for the Debian project.
diff --git a/debian/patches/manpages-cleanup.patch b/debian/patches/manpages-cleanup.patch
new file mode 100644
index 000..6b09d18
--- /dev/null
+++ b/debian/patches/manpages-cleanup.patch
@@ -0,0 +1,28 @@
+Description: clean up manpages
+ In particular, "warning: macro 'p' not defined" can be fixed just by dropping
+ that.
+Author: Florian Ernst 
+Index: lcms2/utils/psicc/psicc.1
+===
+--- lcms2.orig/utils/psicc/psicc.1
 lcms2/utils/psicc/psicc.1
+@@ -26,7 +26,6 @@ Input profile: Generates Color Space Arr
+ Alternate way to set precision, number of CLUT points (CRD only).
+ .TP
+ .BI \-o\  profile
+-.p
+ Output profile: Generates Color Rendering Dictionary(CRD).
+ .TP
+ .BI \-t\  intent
+Index: lcms2/utils/transicc/transicc.1
+===
+--- lcms2.orig/utils/transicc/transicc.1
 lcms2/utils/transicc/transicc.1
+@@ -41,7 +41,6 @@ SoftProof intent (0,1,2,3) [defaults to
+ Terse output, intended for pipe usage.
+ .TP
+ .BI \-o\  profile
+-.p
+ Output profile (defaults to sRGB).
+ .TP
+ .B \-q
diff --git a/debian/patches/series b/debian/patches/series
index ed0970a..6308b2d 100644
--- a/debian/patches/series
+++ b/debian/patches/series
@@ -1 +1,2 @@
 prepare-for-libtoolizing.patch
+manpages-cleanup.patch
diff --git a/debian/upstream/metadata b/debian/upstream/metadata
new file mode 100644
index 000..bd23dd1
--- /dev/null
+++ b/debian/upstream/metadata
@@ -0,0 +1,5 @@
+---
+Bug-Database: https://github.com/mm2/Little-CMS/issues
+Bug-Submit: https://github.com/mm2/Little-CMS/issues/new
+Repository: https://github.com/mm2/Little-CMS.git
+Repository-Browse: https://github.com/mm2/Little-CMS


signature.asc
Description: PGP signature

Bug#1022825: libyaml-dev: Include yamlConfig.cmake

[Florian Ernst]

Hello Bastian,

On Wed, Oct 26, 2022 at 04:10:33PM +0200, Bastian Germann wrote:
> Please include yamlConfig.cmake as part of the -dev package.

That yamlConfig.cmake file currently will only be generated when using
CMake to build libyaml. Upstream's standard build scheme does not build
it, though.

However, the yamlConfig.cmake.in appears simple enough as it is. Is
there an easy way to generate a fully compliant yamlConfig.cmake from it
without changing build systems?

Cheers,
Flo


signature.asc
Description: PGP signature

Bug#933098: Which skills needed for a maintainer for xskat?

[Florian Ernst]

Hello Marco,

On Sat, Oct 08, 2022 at 10:42:59AM +, Marco wrote:
> which skills are exactly needed for package maintainers?

That is a rather broad question given the wide variety of packages and
their respective build systems and further implementation details. As
such, I'd have a hard time to pinpoint the "exactly" from your question.

But now on a more serious note, there are many resources available for
dealing with the technical and/or organizational aspects of packaging,
e.g.

https://www.debian.org/doc/manuals/debmake-doc/
https://www.debian.org/doc/manuals/maint-guide/
https://www.debian.org/doc/manuals/developers-reference/
https://wiki.debian.org/DebianMaintainer

that will also link to further resources. And of course there is quite
some overlap among these documents, and often not all details will be
needed.

As for the xskat package in particular, there most probably won't be all
too many exciting changes required (or much glory to be earned, to be
honest): no new upstream release for over 18 years, most of the
packaging already done with a rather simple structure (just as you
stated: it compiles easily and just works), so mostly keeping up with
the latest Debian standards and recommendations, as e.g. pointed out as
"action needed" on , which so far
I had done a whopping 6 times over the past 16 years.

> Are there people out there who can help newcomers if they encounter
> problems?

That would be the Debian Mentors with some more documentation at
 and a mailing list at
 (with a FAQ at
).

JFTR, I personally most probably won't be available for any such help.

HTH,
Flo


signature.asc
Description: PGP signature

Bug#1015276: ITS: lcms2

[Florian Ernst]

Greetings,

On Sat, Jul 23, 2022 at 01:06:06PM +0200, Florian Ernst wrote:
> [...]
> As of now I do not see any pressing issues left that would require
> direct action. Lintian points to some low-hanging fruit, and one could
> add autopkgtests and a Salsa pipeline to extend test coverage, so I
> guess I will keep a view on this package and eventually file some MR.

FWIW, I now started with those low-hanging fruit as pointed out by
lintian, cf. <https://salsa.debian.org/debian/lcms2/-/merge_requests/4>.
Please review once you find the spare time, and I will eventually
investigate autopkgtests next. And then we could just enable a Salsa
CI/CD pipeline to see it all in motion.

Cheers,
Flo


signature.asc
Description: PGP signature

Bug#1007752: NMU in DELAYED/7

[Florian Ernst]

Greetings,

On Mon, Jul 18, 2022 at 09:34:22AM +0200, Adam Borowski wrote:
> On Mon, Jul 18, 2022 at 07:56:14AM +0200, Florian Ernst wrote:
> > [...]
> > As such I really wouldn't like to see this uploaded in its current form.
> 
> Ok, cancelled.

Thanks.

> > Still, given the apparent lack of public respone I was considering
> > starting the salvaging process for lcms2
> 
> Sounds good.  Of course, I have no interest in lcms2 itself.

On Mon, Jul 18, 2022 at 09:43:31AM +0200, Mathieu Malaterre wrote:
> On Mon, Jul 18, 2022 at 8:00 AM Florian Ernst  wrote:
> > Still, given the apparent lack of public respone I was considering
> > starting the salvaging process for lcms2 as described in the Developer's
> > Reference (5.12) and the Debian Wiki
> > <https://wiki.debian.org/PackageSalvaging>. Of course, this would result
> > in some more delay until the new version could get uploaded. Unless
> > Thomas does it himself, of course.
> 
> Excellent, thanks for volunteering.

JFTR, an ITS has now been filed in <https://bugs.debian.org/1015276>,
with both of you also X-Debbugs-Cc'd.

Cheers,
Flo


signature.asc
Description: PGP signature

Bug#1015276: ITS: lcms2

[Florian Ernst]

Source: lcms2
Version: 2.12~rc1-2
Severity: important
X-Debbugs-Cc: Thomas Weber , lc...@packages.debian.org, 
Mathieu Malaterre , Adam Borowski 

Greetings,

hereby I declare my intention to salvage the "lcms2" package using the
procedure described in the Developer's Reference (5.12) and the Debian
Wiki .

Criteria are met as follows:

* The package is in clear need of some love and care:
  * There are three upstream releases missing (2.12, 2.13, 2.13.1), cf.
, filed 16 Mar 2022.
  * There is work needed from a quality-assurance perspective as the
packaging uses outdated / deprecated standards, cf.


AND

* An upload is needed to fix this.

AND

* At least one to the following applies (non-applicable omitted):
  * There is no visible activity regarding the package for six months.
Attempting to elicit a maintainer response failed, cf.
 ff.

My objective is to have this package in Debian, and in good shape. So
if you (maintainer) want to resume taking care of it, please do. And in
case you object or already have other plans, just let me know.

I am well aware that filing this ITS is a stretch as the criteria are
hardly met. I'm filing it nonetheless already due to demand for an
updated package for matching upstream requirements. Given these
circumstances I plan to wait a bit longer with the ITS waiting phase.

Kind regards,
Flo


signature.asc
Description: PGP signature

Bug#1007752: NMU in DELAYED/7

[Florian Ernst]

Hello Adam,

On Sun, Jul 17, 2022 at 10:52:32PM +0200, Adam Borowski wrote:
> As jpeg-xl needs the new version, and we haven't heard from you for quite
> a while, I've uploaded Florian's NMU to DELAYED/7.
> 
> If you have anything against it, please holler.

Thanks for the upload. However, this upload was prepared as an NMU not
for the purposes to upload it as-is, but merely to silence lintian
somewhat on local runs. If I were to NMU, I'd really like to apply some
further adjustments. And also upload by myself, while at it. ;-)

As such I really wouldn't like to see this uploaded in its current form.

Still, given the apparent lack of public respone I was considering
starting the salvaging process for lcms2 as described in the Developer's
Reference (5.12) and the Debian Wiki
. Of course, this would result
in some more delay until the new version could get uploaded. Unless
Thomas does it himself, of course.

Adam, would that possible additional delay be acceptable for you / for
jpeg-xl? If not, please feel free to take my patch as basis for an
upload, but then don't attribute it to me but rather maybe just mention
me.
However, either way, please remove the current DELAYED/7 upload.

Cheers,
Flo


signature.asc
Description: PGP signature

Bug#1014506: slurm-wlm: flaky autopkgtest: sbatch fails without

[Florian Ernst]

Control: affects 1014506 src:libyaml

On Thu, Jul 07, 2022 at 11:22:44AM +0200, Paul Gevers wrote:
> [...]
> I looked at the results of the autopkgtest of you package on armhf because
> it was showing up as a regression for the upload of perl. I noticed that the
> test regularly fails and I saw failures on other architectures too.
> 
> Because the unstable-to-testing migration software now blocks on
> regressions in testing, flaky tests, i.e. tests that flip between
> passing and failing without changes to the list of installed packages,
> are causing people unrelated to your package to spend time on these
> tests.

JFTR, this now also affects the unstable-to-testing migration of libyaml,
cf. https://tracker.debian.org/pkg/libyaml. Thus marking this issue here
as such.

Cheers,
Flo


signature.asc
Description: PGP signature

Bug#1014621: tree: --timefmt doesn't imply -D, manual says it should

[Florian Ernst]

Control: severity 1014621 minor

Hello Steve,

this came in to the Debian BTS, cf.  as
well as the full list of reported issues at
.

Oh, I just noticed https://gitlab.com/OldManProgrammer/unix-tree. I
could just file new issues there matching those filed at the Debian BTS,
for easier tracking, if so desired.

JFYI and for your consideration. The issue that наб illustrates seems to
stem from the early "break" when parsing "--timefmt" with a "="
separator (line 428 as of tree 2.0.2). When calling tree without the
"=", e.g. "tree --timefmt %s aac/a", it works as expected. @наб, JFYI,
and with thanks for the report.

One could argue that tree works just as the manpage describes, as there
is no mention of the "=" separator therein, but that would IMHO be
rather nitpicky and distracting, and tree would still violate the
principle of least surprise in this. ;-)

Cheers,
Flo

On Sat, Jul 09, 2022 at 02:48:43AM +0200, наб wrote:
> Package: tree
> Version: 2.0.2-1
> Version: 1.8.0-1+b1
> Severity: normal
> 
> Dear Maintainer,
> 
> Quoth tree(1):
>--timefmt format
>   Prints (implies -D) and formats the date according to the 
> format string which uses the strftime(3) syntax.
> 
> However:
> -- >8 --
> nabijaczleweli@tarta:~/code/voreutils$ tree --timefmt=%s aac/a
> aac/a
> └── b
> ├── c
> │   └── d
> │   └── e
> └── q
> 
> 4 directories, 1 file
> nabijaczleweli@tarta:~/code/voreutils$ tree --timefmt=%s aac/a -D
> aac/a
> └── [1631887206]  b
> ├── [1631887206]  c
> │   └── [1631887206]  d
> │   └── [1631887206]  e
> └── [1631885430]  q
> 
> 4 directories, 1 file
> -- >8 --
> 
> (Also, the -D in the quoted paragraph is unbolded but should be.)
> 
> Affects bullseye (1.8.0-1+b1) and sid (2.0.2-1).
> 
> Best,
> наб
> 
> 
> -- System Information:
> Debian Release: 11.3
>   APT prefers stable-updates
>   APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 
> 'stable-debug'), (500, 'stable')
> Architecture: amd64 (x86_64)
> Foreign Architectures: i386
> 
> Kernel: Linux 5.10.0-15-amd64 (SMP w/24 CPU threads)
> Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_FIRMWARE_WORKAROUND, 
> TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
> Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), 
> LANGUAGE=en_GB:en
> Shell: /bin/sh linked to /usr/bin/dash
> Init: systemd (via /run/systemd/system)
> LSM: AppArmor: enabled
> 
> Versions of packages tree depends on:
> ii  libc6  2.31-13+deb11u3
> 
> tree recommends no packages.
> 
> tree suggests no packages.
> 
> -- no debconf information




signature.asc
Description: PGP signature

Bug#1013670: transition: srt

[Florian Ernst]

On Thu, Jun 30, 2022 at 07:53:50AM +0200, Florian Ernst wrote:
> On Wed, Jun 29, 2022 at 10:37:12PM +0200, Sebastian Ramacher wrote:
> > On 2022-06-25 13:46:45 +0200, Sebastian Ramacher wrote:
> > > On 2022-06-24 17:32:43, Florian Ernst wrote:
> > > > please grant a transition slot for the srt transition.
> > > > [...]
> > > 
> > > Let's wait until ffmpeg migrated and then we should be good to go ahead
> > > with this one.
> > 
> > Please go ahead
> 
> Thanks. I'm planning to add some finetuning to the current packaging and
> then to upload on Saturday.

srt 1.5.0-2 has just been uploaded to unstable, thanks for taking care.

Cheers,
Flo


signature.asc
Description: PGP signature

Bug#1013670: transition: srt

[Florian Ernst]

On Wed, Jun 29, 2022 at 10:37:12PM +0200, Sebastian Ramacher wrote:
> On 2022-06-25 13:46:45 +0200, Sebastian Ramacher wrote:
> > On 2022-06-24 17:32:43, Florian Ernst wrote:
> > > please grant a transition slot for the srt transition.
> > > [...]
> > 
> > Let's wait until ffmpeg migrated and then we should be good to go ahead
> > with this one.
> 
> Please go ahead

Thanks. I'm planning to add some finetuning to the current packaging and
then to upload on Saturday.

Cheers,
Flo


signature.asc
Description: PGP signature

Bug#1013670: transition: srt

[Florian Ernst]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: transition

Dear Release Team,

please grant a transition slot for the srt transition.

Upstream has changed the soname from 1.4 to 1.5, and the srt packaging
has been adjusted to reflect this. The following source package have
been build-depending on srt:

ffmpeg
gst-plugins-bad1.0
nageru
vlc

I have successfully rebuilt all of them on amd64 against srt as present
in experimental, where srt itself has successfully built on all release
architectures..

The information on
https://release.debian.org/transitions/html/auto-srt.html looks correct
to me.

Ben file:

title = "srt";
is_affected = .depends ~ "libsrt1.4-gnutls" | .depends ~ "libsrt1.4-openssl" | 
.depends ~ "libsrt1.5-gnutls" | .depends ~ "libsrt1.5-openssl";
is_good = .depends ~ "libsrt1.5-gnutls" | .depends ~ "libsrt1.5-openssl";
is_bad = .depends ~ "libsrt1.4-gnutls" | .depends ~ "libsrt1.4-openssl";

Cheers,
Flo


signature.asc
Description: PGP signature

Bug#1009356: kubernetes-client: config use-context command segfaults since version 1.20.5+really1.20.2-1.1

[Florian Ernst]

Greetings,

On Sat, Apr 23, 2022 at 11:21:02PM -0700, David Tomaschik wrote:
> It appears as though the underlying bug is this:
> https://github.com/golang/go/issues/48238
> 
> Bumping the vendored versions of modern-go/reflect2 and json-iterator/go
> look to fix the issue.

Thanks, David, for the pointer. It seems this is what upstream did, i.e.
both vendored modules have been updated in recent versions, and when I
take current upstream v1.24.1 and apply the current Debian packaging it
manages to create a kubernetes-client...deb whose kubectl binary doesn't
suffer from this particular segfault anymore. The other tests which I
conducted in #1000980 still succeed as well, so apparently packaging the
current upstream "simply" fixes this issue here.

Cheers,
Flo


signature.asc
Description: PGP signature

Bug#987895: libyaml: 0.2.5 released upstream, not detected by watch file

[Florian Ernst]

Greetings,

On Sun, May 01, 2022 at 03:06:12PM +0200, Florian Ernst wrote:
> Could you please comment on <https://bugs.debian.org/987895>?
> 
> To me it feels like the libyaml package might be in need of salvaging as
> per Developer's Reference (5.12) and the Debian Wiki
> <https://wiki.debian.org/PackageSalvaging>, so please speak up.

JFTR, I now started the salvaging process in
<https://bugs.debian.org/1012344>.

Kind regards,
Flo


signature.asc
Description: PGP signature

Bug#1012344: ITS: libyaml

[Florian Ernst]

Source: libyaml
Version: 0.2.2-1
Severity: important
X-Debbugs-Cc: Anders Kaseorg , liby...@packages.debian.org

Greetings,

hereby I declare my intention to salvage the "libyaml" package using the
procedure described in the Developer's Reference (5.12) and the Debian
Wiki .

Criteria are met as follows:

* The package is in clear need of some love and care:
  * There are three upstream releases missing, cf.
, filed 01 May 2021.
  * There is work needed from a quality-assurance perspective as the
packaging uses outdated / deprecated standards, cf.


AND

* An upload is needed to fix this.

AND

* At least one to the following applies (non-applicable omitted):
  * There is no visible activity regarding the package for six months.
Attempting to elicit a maintainer response failed, cf.
 ff.

My objective is to have this package in Debian, and in good shape. So
if you (maintainer) want to resume taking care of it, please do. And in
case you object or already have other plans, just let me know.

Kind regards,
Flo


signature.asc
Description: PGP signature

Bug#1010050: bullseye-pu: package clementine/1.4.0~rc1+git347-gfc4cb6fc7+dfsg-1+deb11u1

[Florian Ernst]

On Sat, May 28, 2022 at 08:17:47PM +0100, Adam D. Barratt wrote:
> On Sat, 2022-04-23 at 10:25 +0200, Florian Ernst wrote:
> > Clementine fails to start if the package libqt5sql5-sqlite is not
> > installed, i.e. clementine is missing a Depends. This was reported in
> > #1008312, an identical fix has already been uploaded to Unstable.
> > 
> > [ Impact ]
> > Users need to realize that a Depends is missing that they need to
> > install manually. As it is, clementine might simply fail to start.
> > Clementine's error messages indicate that something is missing, but
> > finding the relevant missing package is hard for end users.
> > 
> 
> Please go ahead.

Thanks, just uploaded.

Cheers,
Flo


signature.asc
Description: PGP signature

Bug#1010435: harfbuzz: Several new upstream releases

[Florian Ernst]

Source: harfbuzz
Version: 2.7.4-1
Severity: wishlist

Dear maintainers,

as your are undoubtedly aware there are several new upstream releases
available, cf. .

Among other things those stabilize the subset API as required for
#988781, contain various build fixes that might help with #956646 and/or
#944212, provide Unicode 14.0 support, extend the public API, support
more than 65535 (the OpenType limit) glyph shapes and metrics, and much
much more.

Are there any reasons preventing to package any of those 19 new releases
since the currently-packaged 2.7.4? Posing this admittedly rather loaded
question here as I am wondering what is going on, and if there are
indeed any such reasons please document them here ...

Cheers,
Flo


signature.asc
Description: PGP signature

Bug#987895: libyaml: 0.2.5 released upstream, not detected by watch file

[Florian Ernst]

Hello Anders,

On Wed, Mar 30, 2022 at 05:54:52PM +0200, Florian Ernst wrote:
> I saw that you had been active in Debian recently, which is a relief as
> I was wondering whether the libyaml package might be in need of
> salvaging, given the apparent lack of activity over the last years.

Could you please comment on <https://bugs.debian.org/987895>?

To me it feels like the libyaml package might be in need of salvaging as
per Developer's Reference (5.12) and the Debian Wiki
<https://wiki.debian.org/PackageSalvaging>, so please speak up.

Kind regards,
Flo


signature.asc
Description: PGP signature

Bug#1010433: ITS: liblognorm

[Florian Ernst]

Source: liblognorm
Version: 2.0.5-1.1
Severity: important
X-Debbugs-Cc: Pierre Chifflier , Michael Biebl 


Greetings,

hereby I declare my intention to salvage the "liblognorm" package using
the procedure described in the Developer's Reference (5.12) and the
Debian Wiki .

Criteria are met as follows:

* The package is in clear need of some love and care:
  * There is an upstream release missing, cf.
, filed 28 Apr 2020.
  * There is work needed from a quality-assurance perspective as the
packaging uses outdated / deprecated standards, cf.
, and it FTCBFS, cf.


AND

* An upload is needed to fix this.

AND

* At least one to the following applies (non-applicable omitted):
  * There is no visible activity regarding the package for six months.
Attempting to elicit a maintainer response failed, cf.
 ff.
  * The last upload was an NMU and there was no maintainer upload within
one year.
Last maintainer upload was on 2018-04-29, last NMU (and package
update) on 2020-03-15.

My objective is to have this package in Debian, and in good shape. So
if you (maintainer) want to resume taking care of it, please do. And in
case you object or already have other plans, just let me know.

As this package is a direct dependency of rsyslog and is also coming
from the same upstream I'm CC'ing the rsyslog maintainer who might have
something to say on this.

Kind regards,
Flo


signature.asc
Description: PGP signature

Bug#1010434: ITS: libestr

[Florian Ernst]

Source: libestr
Version: 0.1.10-2.1
Severity: important
X-Debbugs-Cc: Pierre Chifflier , Michael Biebl 


Greetings,

hereby I declare my intention to salvage the "libestr" package using the
procedure described in the Developer's Reference (5.12) and the Debian
Wiki .

Criteria are met as follows:

* The package is in clear need of some love and care:
  * There is a (recommended) upstream release missing, cf.
, filed 31 Oct 2018.
  * There is work needed from a quality-assurance perspective as the
packaging uses outdated / deprecated standards, cf.


AND

* An upload is needed to fix this.

AND

* At least one to the following applies (non-applicable omitted):
  * There is no visible activity regarding the package for six months.
Attempting to elicit a maintainer response failed, cf.
 ff.
  * The last upload was an NMU and there was no maintainer upload within
one year.
Last maintainer upload was on 2016-04-18, last NMU (and package
update) on 2017-10-09.

My objective is to have this package in Debian, and in good shape. So
if you (maintainer) want to resume taking care of it, please do. And in
case you object or already have other plans, just let me know.

As this package is a direct dependency of rsyslog and is also coming
from the same upstream I'm CC'ing the rsyslog maintainer who might have
something to say on this (and who, incidentally, had also filed the bug
mentioned above).

Kind regards,
Flo


signature.asc
Description: PGP signature

Bug#865846: src:xpuzzles: New upstream release (8.0.5)

[Florian Ernst]

Control: retitle -1 xpuzzles: New upstream release (8.4.0)

Hello Varun,

On Sun, Jun 25, 2017 at 09:19:27AM +0200, Florian Ernst wrote:
> there is a new upstream release on a new homepage, cf.
> <http://www.sillycycle.com/puzzles.html#X>, thus not noticed by uscan.

By now upstream is at 8.4.0. However, considering that the last
maintainer upload for xpuzzles dates back to 2013(!), despite several
upstream releases and an unacknowledged NMU since then and a removal
from testing due to RC-bugginess, I assume you are not working on this
package anymore.

Please let me know whether you have any plans for xpuzzles. As a former
maintainer of this package I'd very much wish to see it in better shape.

Cheers,
Flo


signature.asc
Description: PGP signature

Bug#1008312: clementine: diff for NMU version 1.4.0~rc1+git347-gfc4cb6fc7+dfsg-2.1

[Florian Ernst]

On Thu, Apr 14, 2022 at 06:23:53PM +0200, Florian Ernst wrote:
> Please note that this bug also affects current stable, i.e. bullseye, and
> should be fixed there as well, as per
> <https://www.debian.org/doc/manuals/developers-reference/pkgs.html#upload-stable>.

JFTR, this will now be tracked in <https://bugs.debian.org/1010050>.

Cheers,
Flo


signature.asc
Description: PGP signature

Bug#1010050: bullseye-pu: package clementine/1.4.0~rc1+git347-gfc4cb6fc7+dfsg-1+deb11u1

[Florian Ernst]

Package: release.debian.org
Severity: normal
Tags: bullseye
User: release.debian@packages.debian.org
Usertags: pu
X-Debbugs-Cc: Thomas Pierson 

[ Reason ]
Clementine fails to start if the package libqt5sql5-sqlite is not
installed, i.e. clementine is missing a Depends. This was reported in
#1008312, an identical fix has already been uploaded to Unstable.

[ Impact ]
Users need to realize that a Depends is missing that they need to
install manually. As it is, clementine might simply fail to start.
Clementine's error messages indicate that something is missing, but
finding the relevant missing package is hard for end users.

[ Tests ]
There are no code changes at all, clementine just gains an explicit
Depends on a package that most QT users will already have installed
anyways. I'm running the updated package on my local Bullseye just fine.

[ Risks ]
No code changes at all, a trivial fix, and the newly added Depends on
libqt5sql5-sqlite can be fulfilled on all release archs. There had been
a binNMU in Stable that had me worrying whether the versioning of the
proposed upload was correct, but according to apt/dpkg it all works as
intended, cf.
| ~/debian/temp/clementine $ apt policy clementine
| clementine:
|   Installed: 1.4.0~rc1+git347-gfc4cb6fc7+dfsg-1+deb11u1
|   Candidate: 1.4.0~rc1+git347-gfc4cb6fc7+dfsg-1+deb11u1
|   Version table:
|  1.4.0~rc1+git347-gfc4cb6fc7+dfsg-2.1 50
|  50 http://deb.debian.org/debian unstable/main amd64 Packages
|  1.4.0~rc1+git347-gfc4cb6fc7+dfsg-2 50
|  50 http://deb.debian.org/debian testing/main amd64 Packages
|  *** 1.4.0~rc1+git347-gfc4cb6fc7+dfsg-1+deb11u1 100
| 100 /var/lib/dpkg/status
|  1.4.0~rc1+git347-gfc4cb6fc7+dfsg-1+b1 990
| 990 http://deb.debian.org/debian bullseye/main amd64 Packages
|  1.3.1+git609-g623a53681+dfsg-1 990
| 990 http://deb.debian.org/debian buster/main amd64 Packages
| ~/debian/temp/clementine $ dpkg --compare-versions 
'1.4.0~rc1+git347-gfc4cb6fc7+dfsg-1+deb11u1' gt 
'1.4.0~rc1+git347-gfc4cb6fc7+dfsg-1+b1' && echo true
| true

[ Checklist ]
  [X] *all* changes are documented in the d/changelog
  [X] I reviewed all changes and I approve them
  [X] attach debdiff against the package in (old)stable
  [X] the issue is verified as fixed in unstable

[ Changes ]
Add explicit Depends on libqt5sql5-sqlite.

[ Other info ]
In the past other packages were impacted similarly and also fixed this
by adding an explicit Depends, e.g.
- kaffeine 1.0~pre3-1 (updated in kaffeine 2.0.3-1)
- kstars 4:16.08.3-2, #854516
- ktouch 4:19.08.3-2, LP#1790955

I'll upload once I receive your approval.

Cheers,
Flo
diff -Nru clementine-1.4.0~rc1+git347-gfc4cb6fc7+dfsg/debian/changelog 
clementine-1.4.0~rc1+git347-gfc4cb6fc7+dfsg/debian/changelog
--- clementine-1.4.0~rc1+git347-gfc4cb6fc7+dfsg/debian/changelog
2020-10-27 11:30:27.0 +0100
+++ clementine-1.4.0~rc1+git347-gfc4cb6fc7+dfsg/debian/changelog
2022-04-23 09:29:26.0 +0200
@@ -1,3 +1,10 @@
+clementine (1.4.0~rc1+git347-gfc4cb6fc7+dfsg-1+deb11u1) bullseye; 
urgency=medium
+
+  * Non-maintainer upload.
+  * Add explicit Depends on libqt5sql5-sqlite (Closes: #1008312)
+
+ -- Florian Ernst   Sat, 23 Apr 2022 09:29:26 +0200
+
 clementine (1.4.0~rc1+git347-gfc4cb6fc7+dfsg-1) unstable; urgency=medium
 
   * New upstream snapshot.
diff -Nru clementine-1.4.0~rc1+git347-gfc4cb6fc7+dfsg/debian/control 
clementine-1.4.0~rc1+git347-gfc4cb6fc7+dfsg/debian/control
--- clementine-1.4.0~rc1+git347-gfc4cb6fc7+dfsg/debian/control  2020-10-27 
11:30:27.0 +0100
+++ clementine-1.4.0~rc1+git347-gfc4cb6fc7+dfsg/debian/control  2022-04-23 
09:12:37.0 +0200
@@ -38,6 +38,7 @@
 Package: clementine
 Architecture: any
 Depends: ${shlibs:Depends}, ${misc:Depends},
+ libqt5sql5-sqlite,
  gstreamer1.0-plugins-base,
  gstreamer1.0-plugins-good,
  gstreamer1.0-plugins-ugly


signature.asc
Description: PGP signature

Bug#747196: cstream: new upstream release (3.1.1 18-Feb-2013)

[Florian Ernst]

Control: retitle -1 cstream: new upstream release (3.2.1, 2022-03-13)

On Tue, May 06, 2014 at 11:25:23AM +0200, Florian Ernst wrote:
> there is a new upstream release of cstream, the changelog reads as
> follows:

Well, 3.1.1 had entered the archives over three years ago, cf.
<https://tracker.debian.org/news/1032355/accepted-cstream-311-1-source-into-unstable/>.

However, by now there are new upstream releases available, cf.
<https://www.cons.org/cracauer/download/>. The newest CHANGES read

| 3.2.1:
| --
| 
| print throughput after fsync, if requested.
| 
| 3.2.0:
| --
| 
| -O F option (do an fsync at the end of the output file).
| 
| When closing files fails, exit with an error code.

Please update the package when you think it is due time.

Cheers,
Flo


signature.asc
Description: PGP signature

Bug#1004588: libzip: New upstream release (1.8.0, 2021 Jun 18)

[Florian Ernst]

Following up to myself:

On Sun, Jan 30, 2022 at 08:52:17PM +0100, Florian Ernst wrote:
> there is a new upstream release available, cf.
> <https://github.com/nih-at/libzip/releases>.
> 
> The changes contain
> 
> | Add support for zstd (Zstandard) compression.
> | Add support for lzma (ID 14) compression.
> | Add zip_source_window_create().
> | Add zip_source_zip_create() variant to zip_source_zip().
> | Allow method specific comp_flags in zip_set_file_compression().
> | Allow zip_source_tell() on sources that don't support seeking and 
> zip_ftell() on compressed data.
> | Provide more details for consistency check errors.
> | Improve output of zipcmp.
> | In zipcmp, don’t ignore empty directories when comparing directory listing.
> | Treat empty string as no password given in zip_file_set_encryption(), 
> zip_fopen_encrypted(), and zip_set_default_password().
> 
> which seem nice enough to eventually have in Debian.

I confirmed that the current packaging can still be used for
libzip-1.8.0 when dropping the SOVERSION patch which does not apply
anymore. Well, maybe it's finally time to do the transition anyways.

Of course, the resulting build is not clean then, and further changes
could (most possibly should) be applied. But this just as a heads-up.

Cheers,
Flo


signature.asc
Description: PGP signature

Bug#881910: ITA: libcdio-paranoia -- library to read and control digital audio CDs (was: Bug#881910: O: libcdio and libcdio-paranoia)

[Florian Ernst]

Hello Gabriel,

On Mon, Oct 18, 2021 at 08:37:10PM +0200, Bastian Germann wrote:
> On Tue, 4 Feb 2020 23:10:06 -0300 "Gabriel F. T. Gomes" wrote:
> > I maintain pragha, which depends on this package, so I'll adopt it.
> It is now 1.5 years since you filed the ITA. There is a new upstream version
> that is unpackaged. Do you still want to take over maintainership?

Could you please comment on this, thanks.

Cheers,
Flo


signature.asc
Description: PGP signature

Bug#1008312: clementine: diff for NMU version 1.4.0~rc1+git347-gfc4cb6fc7+dfsg-2.1

[Florian Ernst]

Control: tags 1008312 + patch
Control: tags 1008312 + pending

Dear maintainer,

I've prepared an NMU for clementine (versioned as
1.4.0~rc1+git347-gfc4cb6fc7+dfsg-2.1) and uploaded it to DELAYED/7.
Please feel free to tell me if I should delay it longer.

I have verified that adding an explicit Depends on libqt5sql5-sqlite
allows clementine to start again and play some stuff as follows:
- create minimal chroot and enter
- install clementine via "apt install --no-install-recommends clementine"
- start clementine -> fails as reported
- install libqt5sql5-sqlite
- start clementine -> starts and allows to play music

Please note that this bug also affects current stable, i.e. bullseye, and
should be fixed there as well, as per
<https://www.debian.org/doc/manuals/developers-reference/pkgs.html#upload-stable>.

Best regards,
Flo
diff -Nru clementine-1.4.0~rc1+git347-gfc4cb6fc7+dfsg/debian/changelog clementine-1.4.0~rc1+git347-gfc4cb6fc7+dfsg/debian/changelog
--- clementine-1.4.0~rc1+git347-gfc4cb6fc7+dfsg/debian/changelog	2022-02-12 18:15:45.0 +0100
+++ clementine-1.4.0~rc1+git347-gfc4cb6fc7+dfsg/debian/changelog	2022-04-14 18:00:57.0 +0200
@@ -1,3 +1,10 @@
+clementine (1.4.0~rc1+git347-gfc4cb6fc7+dfsg-2.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Add explicit Depends on libqt5sql5-sqlite (Closes: #1008312)
+
+ -- Florian Ernst   Thu, 14 Apr 2022 18:00:57 +0200
+
 clementine (1.4.0~rc1+git347-gfc4cb6fc7+dfsg-2) unstable; urgency=medium
 
   [ Pino Toscano ]
diff -Nru clementine-1.4.0~rc1+git347-gfc4cb6fc7+dfsg/debian/control clementine-1.4.0~rc1+git347-gfc4cb6fc7+dfsg/debian/control
--- clementine-1.4.0~rc1+git347-gfc4cb6fc7+dfsg/debian/control	2020-10-27 11:47:50.0 +0100
+++ clementine-1.4.0~rc1+git347-gfc4cb6fc7+dfsg/debian/control	2022-04-14 17:26:41.0 +0200
@@ -38,6 +38,7 @@
 Package: clementine
 Architecture: any
 Depends: ${shlibs:Depends}, ${misc:Depends},
+ libqt5sql5-sqlite,
  gstreamer1.0-plugins-base,
  gstreamer1.0-plugins-good,
  gstreamer1.0-plugins-ugly


signature.asc
Description: PGP signature

Bug#1009356: kubernetes-client: config use-context command segfaults since version 1.20.5+really1.20.2-1.1

[Florian Ernst]

Hello Janos,

thank you for your reply. I just saw it after my previous message, so
commenting here now.

On Tue, Apr 12, 2022 at 01:15:11PM +0200, Janos LENART wrote:
> Thanks for your report. I will look into this one. There was a reason I was
> reluctant to "upgrade" golang

I understand your reluctancy, especially given how the situation
developed. And I'm glad to have you on board.

Still, not upgrading had already led to kubernetes being removed from
Bookworm, cf.
,
so one might argue we are still slightly better off now.

Please feel free to communicate how you'd prefer to proceed, and I - for
one - will not interfer any further if so desired. :-)

Cheers,
Flo


signature.asc
Description: PGP signature

Bug#1009356: kubernetes-client: config use-context command segfaults since version 1.20.5+really1.20.2-1.1

[Florian Ernst]

Control: severity -1 important

Hello Nicolas,

thanks for the pointer.

On Tue, Apr 12, 2022 at 11:35:01AM +0200, Nicolas Noirbent wrote:
> Since the upgrade to version 1.20.5+really1.20.2-1.1, using "kubernetes 
> config use-context" to
> switch context systematically triggers SIGSEGV:
> 
> % kubectl config use-context dev-go-cell-001
> unexpected fault address 0x0
> fatal error: fault
> [signal SIGSEGV: segmentation violation code=0x80 addr=0x0 pc=0x46421f]
> […]
> 
> This also obviously affects kubectx and kubens (which uses kubectl config 
> use-context); however it
> does not preclude from manually setting a context / namespace when running 
> regular kubectl
> commands, e.g.:
> 
> % kubectl --context dev-go-cell-001 --namespace hello-world get pods
> NAME  READY   STATUS RESTARTS   AGE
> […]
> 
> Downgrading to 1.20.5+really1.20.2-1 fixes the issue, so I suspect this has 
> something to do with
> the switch to golang 1.18 done to fix 
> #https://bugs.debian.org/cgi-bin/bugreport.cgi?1000980

Commenting here as I did the NMU to fix #1000980:

Confirmed, and for me the segfault looks exactly the same. I'm raising
the severity due to the segfault, but I'm not raising to RC-level as
most(?) functionality remains available, at the cost of ease of use. Or
at least that is what I tedn to believe at the moment.

Shengjing Zhu do you maybe have more insights into this issue?

Cheers,
Flo


signature.asc
Description: PGP signature

Bug#1008687: FTBFS: as-test_pool FAIL killed by signal 6 SIGABRT

[Florian Ernst]

Hello Matthias,

On Mon, Apr 11, 2022 at 11:14:41AM +0200, Matthias Klumpp wrote:
> I'll likely downgrade this bug, but this is fairly odd! If the tests
> fail on some building machines, there is a chance that the actual
> application also doesn't work everywhere. I can say though that this
> works on the buildds, on my local machine and on GitLab. Is there
> anything that's different in the reproducible build machines compared
> to the buildds? Is there anything special about your local machine?

Well, apperently there is, and I'd love to know what exactly it is, but
I'm afraid I don't know. I am using sbuild just like the buildd do, but
reproducible-builds is using pbuilder (cowbuilder?), and all in all I
don't see any common factor.

That being said I take some strange consolation now from the weird fact
that appstream 0.15.3-1 seems to FTBFS on reproducible-builds as well,
or at least on amd64, arm64, and armhf so far, right in the same manner
as initially reported. Yeah, I know, that is not really helpful ...

Cheers,
Flo


signature.asc
Description: PGP signature

Bug#1008687: FTBFS: as-test_pool FAIL killed by signal 6 SIGABRT

[Florian Ernst]

Hello Matthias,

thank you for your reply and for the appstream update.

On Sun, Apr 10, 2022 at 11:08:40PM +0200, Matthias Klumpp wrote:
> Am Mi., 30. März 2022 um 20:21 Uhr schrieb Florian Ernst 
> :
> > during a rebuild of the reverse b-d of libyaml I found that this package
> > failed to build on my amd64.
> >
> > In addition, the build also failed on amd64, i386, arm64, and armhf,
> > each both in unstable and in bookworm, cf.
> > <https://tests.reproducible-builds.org/debian/rb-pkg/appstream.html>
> > where you will also find full logs.
> 
> I can't reproduce this issue at all, and a recent upload of AppStream
> is building fine on all architectures...
> Does this issue still exist? Maybe it was a fluke or fixed in some
> other component meanwhile...

I agree that the new upload appears to be building just fine on the
official buildd, so thanks for that.

Unfortunately, for me both the previous version and the current version
still FTBFS on my local setup, with exactly the same error message. Of
course, that by itself could all too easily be a local fluke that I'd
have to investigate and that you could safely ignore, if it weren't for
reproducible-builds indicating the very same FTBFS as well.

Looking at the reproducible-builds history of appstream it seems it has
been FTBFS'ing in their setup for quite a while, cf.

https://tests.reproducible-builds.org/debian/history/appstream.html

as well as the individual logs at

https://tests.reproducible-builds.org/debian/rbuild/unstable/amd64/appstream_0.15.2-2.rbuild.log.gz
https://tests.reproducible-builds.org/debian/rbuild/unstable/i386/appstream_0.15.2-2.rbuild.log.gz
https://tests.reproducible-builds.org/debian/rbuild/unstable/arm64/appstream_0.15.2-2.rbuild.log.gz
https://tests.reproducible-builds.org/debian/rbuild/unstable/armhf/appstream_0.15.2-2.rbuild.log.gz
https://tests.reproducible-builds.org/debian/rbuild/bookworm/amd64/appstream_0.15.2-2.rbuild.log.gz
https://tests.reproducible-builds.org/debian/rbuild/bookworm/i386/appstream_0.15.2-2.rbuild.log.gz
https://tests.reproducible-builds.org/debian/rbuild/bookworm/arm64/appstream_0.15.2-2.rbuild.log.gz
https://tests.reproducible-builds.org/debian/rbuild/bookworm/armhf/appstream_0.15.2-2.rbuild.log.gz

All in all this hints at some issue still lingering around, but I cannot
exactly pinpoint what it might be.

I'd say let's wait until reproducible-builds attempts to build 0.15.3-1
and see what the results are. Or feel free to downgrade this issue here
as you deem fit, for on the official buildd and on your machine
everything seems to be working juts fine.

Cheers,
Flo


signature.asc
Description: PGP signature

Bug#1009232: libxslt: New upstream release (v1.1.35, 2022 Feb 16), not detected by debian/watch

[Florian Ernst]

Source: libxslt
Version: 1.1.34-4
Severity: wishlist

Dear maintainer,

there is a new upstream release available, cf.
.

Its NEWS read
| v1.1.35: Feb 16 2022:
|- Security:
|   [CVE-2021-30560] Fix use-after-free in xsltApplyTemplates
|   Fix memory leak in xsltDocumentElem (David King)
|   Fix memory leak in xsltCompileIdKeyPattern (David King)
|   Fix double-free with stylesheets containing entity nodes
| 
|- Fixed regressions:
|   Fix performance regression with predicates in patterns
|   Fix regression in xsltComputeSortResult
| 
|- Bug fixes:
|   Fix conflict resolution for templates with same priority
|   Fix xsl:number generating invalid UTF-8
|   Support attribute value templates in xsl:sort lang attributes
|   Don't pass first  in  twice
|   Fix quadratic runtime with text and 
|   Don't allow empty EXSLT durations
| 
|- Improvements:
|   Add xsltproc --huge Argument via libxml XML_PARSE_HUGE (William N. 
Braswell, Jr.)
| 
|- Tests, code quality, fuzzing:
|   Remove .travis.yml
|   Fix some misleading indentation (David King)
|   Use actual types for templates in struct _xsltStylesheet
|   Add CI for CMake on MSVC (Markus Rickert)
|   Check for null pointer before calling freelocale
|   Add CI test for Python 3
|   Don't set maxDepth in XPath contexts
|   Transfer XPath limits to XPtr context
|   Stop using maxParserDepth XPath limit
|   Make long-to-double cast explicit in date.c
|   Disable LeakSanitizer
|   Run clang CI tests with -Wimplicit-int-conversion
|   Fix implicit-int-conversion warning in exslt/crypto.c
|   Fix clang -Wimplicit-int-conversion warning (David Kilzer)
|   Fix clang -Wconditional-uninitialized warning in libxslt/numbers.c (David 
Kilzer)
|   Fix -Wshadow warnings in libexslt/dynamic.c (David Kilzer)
|   Also search parent dir for source XML when fuzzing
| 
|- Build system, portability:
|   Add CMake build files (Markus Rickert)
|   Initial support for Python 3 (Suleyman Poyraz)
|   Call ANSI versions of WinAPI functions explicitly
|   Remove redundant flags from pkg-config files
|   Suppress automake warning in tests/XSLTMark
|   Fix linking libexslt dynamic library when using MinGW (Vadim Zeitlin)
|   Added platform specific path separators (Dmitriy Korovkin)
|   win32: allow passing *FLAGS on command line
|   Fix export of xsltExtMarker on Windows (David Kilzer)
|   Fix redundant includes already in libexslt.h (David Kilzer)
|   Minor fixes to configure.js
|   Fix variable syntax in Python configuration
|   Add new EXSLT string tests to EXTRA_DIST
|   Fix xml2-config check in configure script
|   win32: Add configuration for profiler (Chun-wei Fan)
|   Check whether 'xml2-config --dynamic' is supported
| 
|- Documentation:
|   Add Makefile rule to regenerate xsltproc.html
|   Update links
|   Remove MAINTAINERS
|   Upload documentation to GitLab Pages
|   Add documentation in devhelp format
|   Add --enable-rebuild-docs configure option
|   Fix libexslt header summaries
|   Fix validity of tutorial XML (David King)
|   Use DocBook URL for tutorial DTD (David King)
|   Update libxslt.doap
|   Add missing options to xsltproc man page

The security fixes, the fixed regressions, and the misc bug fixes make
this worthwile, it seems. Please update the package when you think it is
due time.

Please find attached a patch fixing the Homepage (the former now
redirects to the latter) and allowing debian/watch to detect new
releases at GNOME's gitlab instance.

Cheers,
Flo
diff -Nru libxslt-1.1.34/debian/control libxslt-1.1.34/debian/control
--- libxslt-1.1.34/debian/control	2020-03-04 13:43:18.0 +0100
+++ libxslt-1.1.34/debian/control	2022-04-09 12:53:15.0 +0200
@@ -15,7 +15,7 @@
  rename,
 Standards-Version: 4.5.0
 Rules-Requires-Root: no
-Homepage: http://xmlsoft.org/xslt/
+Homepage: https://gitlab.gnome.org/GNOME/libxslt/-/wikis/home
 Vcs-Browser: https://salsa.debian.org/xml-sgml-team/libxslt
 Vcs-Git: https://salsa.debian.org/xml-sgml-team/libxslt.git
 
diff -Nru libxslt-1.1.34/debian/watch libxslt-1.1.34/debian/watch
--- libxslt-1.1.34/debian/watch	2019-11-25 17:17:02.0 +0100
+++ libxslt-1.1.34/debian/watch	2022-04-09 12:53:24.0 +0200
@@ -1,3 +1,4 @@
 version=4
 opts="pgpmode=auto" \
-ftp://xmlsoft.org/libxslt/libxslt-([\d\.]+)\.tar\.gz
+https://gitlab.gnome.org/GNOME/@PACKAGE@/-/tags \
+.*/@PACKAGE@-v?@ANY_VERSION@@ARCHIVE_EXT@$


signature.asc
Description: PGP signature

Bug#1009229: ndisc6: New upstream release (1.0.5, 2021 Sep 21), not detected by debian/watch

[Florian Ernst]

Source: ndisc6
Version: 1.0.4-2
Severity: wishlist

Dear maintainer,

there is a new upstream release available, cf.
.

The NEWS read
| STABLE RELEASE 1.0.5 :
| 
| # Add --no-solicit option to skip sending the discovery packet.
| # Ignore multicast advertisements when discovery was sent as unicast.

debian/watch looks in the directory where all the old releases except
the current one are kept and thus is off by one. The attached patch
fixes this and makes the file more future-proof (and also fixes
lintian's older-debian-watch-file-standard).

Please update the package when you think it is due time.

Cheers,
Flo
diff -Nru ndisc6-1.0.4/debian/watch ndisc6-1.0.4/debian/watch
--- ndisc6-1.0.4/debian/watch	2020-12-11 10:32:44.0 +0100
+++ ndisc6-1.0.4/debian/watch	2022-04-09 10:46:00.0 +0200
@@ -1,6 +1,6 @@
-# Compulsory line, this is a version 3 file
-version=3
+# Compulsory line, this is a version 4 file
+version=4
 
 #  
-http://www.remlab.net/files/ndisc6/archive/ ndisc6-(.*).tar.bz2
+http://www.remlab.net/files/@PACKAGE@/ @PACKAGE@-(.*)@ARCHIVE_EXT@
 


signature.asc
Description: PGP signature

Bug#1009153: tomsfastmath: New upstream release (v0.13.1, 2017 Apr 04), not detected by debian/watch

[Florian Ernst]

Source: tomsfastmath
Version: 0.13-4
Severity: wishlist

Dear maintainer,

there is a new upstream release available, cf.
:

| Bugfix release 0.13.1
| 
|  -- Fix missing fp_rand symbol in shared library
|  -- Fix some parameters in API signatures that should've been const
|  -- Bugfixes and improvements contributed by Sebastian Siewior, Reiner 
Herrmann and Mathias Tausig

Please update the package when you think it is due time.

Please find attached a patch that allows debian/watch to detect new
upstream releases no matter which compression they might use.

Cheers,
Flo
diff -Nru tomsfastmath-0.13/debian/watch tomsfastmath-0.13/debian/watch
--- tomsfastmath-0.13/debian/watch	2016-07-03 21:48:51.0 +0200
+++ tomsfastmath-0.13/debian/watch	2022-04-07 20:49:05.0 +0200
@@ -1,3 +1,3 @@
-version=3
+version=4
 opts=pgpsigurlmangle=s/$/.asc/ \
-  https://github.com/libtom/tomsfastmath/releases .*/tfm-(\d\S*)\.tar\.bz2
+  https://github.com/libtom/@PACKAGE@/releases .*/tfm-(\d\S*)@ARCHIVE_EXT@


signature.asc
Description: PGP signature

Bug#1009151: nghttp2: New upstream release (v1.47.0, 2022 Feb 23)

[Florian Ernst]

Source: nghttp2
Version: 1.43.0-1
Severity: wishlist

Dear maintainer,

there are new upstream releases available, cf.
:

| nghttp2 v1.47.0 Latest
| - lib: Fix decoder table size update (GH-1667)
| - lib: chore: fix -Wunreachable-code-return (GH-1625)
| - build: Make Docker speak HTTP/3 (GH-1657)
| - build: Remove SPDY option for CMake (GH-1665)
| - build: cmake: Disable libbpf build by default
| - doc: Fix typos (GH-1668)
| - doc: Update nghttp2.pyx (GH-1666)
| - h2load: Handle EAGAIN/EWOULDBLOCK from sendmsg
| - h2load: allow setting max frame size for h2load (GH-1640)
| - nghttpx: Add --require-http-scheme option
| - nghttpx: Add support QUIC BBR2
| - nghttpx: Bump libbpf to v0.7.0 and turn on all strict features
| - nghttpx: Change qlog file extension to .sqlog
| - nghttpx: Fix bug that h3 stream ends prematurely
| - nghttpx: Fix the issue that forwarded h3 GET request always has chunked TE
| - nghttpx: Handle EAGAIN/EWOULDBLOCK from sendmsg
| - nghttpx: Send and receive ECN in QUIC packets
| - nghttpx: Set IP_PMTUDISC_DO explicitly
| - nghttpx: Support h3 trailer fields
| - nghttpx: fix quotes in --altsvc example (GH-1643)
| - nghttpx: shrpx: make nghttpx -v show ngtcp2 and nghttp3 version as well 
(GH-1636)
| - third-party: Bump llhttp to v6.0.6
| 
| nghttp2 v1.46.0
| - build: Workaround broken version check in AX_PYTHON_DEVEL (GH-1622)
| - build: Remove check for UDP_SEGMENT (GH-1619)
| - build: Fix issue that libev cannot be found with autotools under mac osx
| - build: Fix compile error with libressl
| - build: Always include optional files to EXTRA_DIST
| - build: Add missing cmake files to EXTRA_DIST
| - src: Enable HTTP/3 with boringssl
| - src: Compile with boringssl for non-http3 build
| - src: Guard msghdr_get_local_addr with ENABLE_HTTP3 macro (GH-1620)
| - nghttpx: Reduce dgram size if sendmsg fails with EINVAL or EMSGSIZE
| - nghttpx: Set SCT data when built with boringssl
| - nghttpx: Fix wrong SSL_CTX object usage
| - nghttpx: Respect !tls-no-postpone-early-data with boringssl
| - nghttpx: Send session ticket after handshake with boringssl
| - nghttpx: Add --frontend-quic-initial-rtt option
| - nghttpx: Unload BPF program after setting up all QUIC listeners
| - nghttpx: Add --worker-process-grace-shutdown-period option
| - nghttpx: Add --max-worker-processes option
| - nghttpx: Unload BPF objects on reload to avoid running out of memlock
| - nghttpx: Support h3-29
| - nghttpx: Fail h3 connection attempt if no ALPN is negotiated
| - nghttpx: Add --rlimit-memlock option
| - nghttpx: Read QUIC keying materials from file
| - nghttpx: Allocate server id in Connection ID (see --quic-server-id option)
| 
| nghttp2 v1.45.1
| - build: Fix compile error with libressl
| - build: Always include optional files to EXTRA_DIST
| - build: Add missing cmake files to EXTRA_DIST
| 
| nghttp2 v1.45.0
| - lib: Stricter checks for pseudo-headers :method and :path (Patch from 
Michael Kaufmann) (GH-1613)
| - doc: Rename sphinxcontrib to rubydomain to avoid module loading error
| - doc: Allow SPHINXBUILD to be overridden by environment variable
| - doc: Fix reference to non-existing 
nghttp2_option_set_max_send_header_block_size() in comment (Patch from Amir 
Livneh) (GH-1610)
| - doc: update document for nghttp2_session_mem_recv (Patch from Jacky_Yin) 
(GH-1603)
| - build: Build with OpenSSL v3.0.0
| - build: Fix cmake Systemd warning
| - nghttpx: Check that HTTP response message finished safely
| - nghttpx: Use secure random to create websocket nonce
| - nghttpx: Fix heap-use-after-free on initialization failure
| - nghttpx: Add experimental HTTP/3 support
| - nghttpx: Add "dnf" (= "do not forward") parameter to backend option 
(GH-1607)
| - h2load: Add qlog output support (Patch from Hajime Fujita) (GH-1569)
| - h2load: Add SSLKEYLOGFILE support (Patch from Lucas Pardue) (GH-1399)
| - h2load: Add experimental HTTP/3 support
| - nghttpd: Fix prototype mismatch for function 'file_read_callback' (Patch 
from lhuang04) (GH-1602)
| 
| nghttp2 v1.44.0
| - lib: Port new ngtcp2 map implementation
| - doc: Replace master with main
| - build: Add precious variables for libev and jemalloc and use JEMALLOC_CFLAGS
| - build: Add more --with-* configure flags
| - build: Add LIBTOOL_LDFLAGS configure variable
| - third-party: Bump llhttp to 6.0.2
| - src: Replace black-list with block-list
| - nghttpx: Fix max distance in weight group/address cycle comparison
| - nghttpx: Set connect_blocker and live_check after shuffling addresses
| - nghttpx: Replace master with main
| - nghttpx: Remove trailing white space after $method log variable (GH-1553)
| - h2load: Add --rps option (GH-1559)
| - h2load: Allow unit in -D option
| - asio: fix some typos (Patch from Jan Kundrát) (GH-1550)

Apart from the various bugfixes the addition of HTTP/3 support and
building with OpenSSL v3.0.0 sound interesting to me.

Please update the package when you think it is due time.

Cheers,
Flo

Bug#1008312: clementine doesn't start

[Florian Ernst]

Hello scorpion2185,

thanks for your report. Please bear with me, as I am not the package
maintainer but just stumbled over this report.

On Sat, Mar 26, 2022 at 05:55:26PM +0100, realroot wrote:
> clementine doesn't start:
> 
> -
> clementine
> 17:53:14.456 WARN  unknown  QSqlDatabase: QSQLITE 
> driver not loaded
> 17:53:14.456 WARN  unknown  QSqlDatabase: available 
> drivers:
> [...]

Do you have the package "libqt5sql5-sqlite" installed? If not please
install it and retry.

This package normally is installed on KDE-based systems, but it seems
clementine is not explicitly forcing its installation via declaring a
Depends, so it could happen that this package is missing even though
clementine needs it.

@Thomas, I confirmed that clementine in current Bullseye behaves just
like reported if that package is missing, and the reported empty list of
available drivers indicates this is indeed the culprit. Once confirmed
by the submitter clementine will need to add an explicit Depends on that
package, both in Sid and in Bullseye (in Buster, too? I haven't checked
...).

Best regards,
Flo


signature.asc
Description: PGP signature

Bug#907174: New version available

[Florian Ernst]

Hello Andrew,

On Sat, Apr 02, 2022 at 02:32:07PM -0400, Andrew Ayer wrote:
> On Thu, 31 Mar 2022 17:42:37 +0200
> Florian Ernst  wrote:
> > [...]
> > On Wed, Mar 30, 2022 at 07:47:52PM -0400, Andrew Ayer wrote:
> > > [...]
> > > I am thinking of putting libndp up for adoption - might you be
> > > willing to take over?
> > 
> > Well, I am willing to help, and if that means I take over that'd be
> > fine with me, thanks for considering. No need to file an RFA in that
> > case, I could just refer to this bugreport here if you approve.
> 
> I approve.  Thanks again!

Thank you, and also thanks for all the work you have invested in
introducing and maintaining libndp. All the best for your future
endeavors!

I have now populated https://salsa.debian.org/debian/libndp with my
latest changes, an upload will follow as soon as the Salsa pipeline
finishes successfully.

Best regards,
Flo


signature.asc
Description: PGP signature

Bug#1000980: kubernetes: diff for NMU version 1.20.5+really1.20.2-1.1

[Florian Ernst]

Dear maintainer,

I've prepared an NMU for kubernetes (versioned as 1.20.5+really1.20.2-1.1)
and uploaded it to DELAYED/7. Please feel free to tell me if I should
delay it longer.
(Note: the previous upload as per
<https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000980#41> has been
canceled, this one here will replace it.)

The diff is based on what I previously sent to this bugreport in
<https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000980#31>, but now
updated to use "golang-go" as per Shengjing Zhu's hint in
<https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000980#50> (and yes,
we could have saved a roundtrip here ...).

The binary package debdiff just lists
| $ debdiff kubernetes-client_1.20.5+really1.20.2-1_amd64.deb 
kubernetes-client_1.20.5+really1.20.2-1.1_amd64.deb
| File lists identical (after any substitutions)
| 
| Control files: lines which differ (wdiff format)
| 
| Installed-Size: [-40405-] {+37547+}
| Version: [-1.20.5+really1.20.2-1-] {+1.20.5+really1.20.2-1.1+}

I tested the kubectl binary against a local KinD cluster and found no
issues. Basic testing as follows:
| [ ... same (successful) results as before snipped ...]
| $ ./kubectl version
| Client Version: version.Info{Major:"1", Minor:"20", GitVersion:"v1.20.2", 
GitCommit:"faecb196815e248d3ecfb03c680a4507229c2a56", GitTreeState:"archive", 
BuildDate:"2022-04-02T14:49:13Z", GoVersion:"go1.18", Compiler:"gc", 
Platform:"linux/amd64"}
| Server Version: version.Info{Major:"1", Minor:"21", GitVersion:"v1.21.1", 
GitCommit:"5e58841cce77d4bc13713ad2b91fa0d961e69192", GitTreeState:"clean", 
BuildDate:"2021-05-21T23:01:33Z", GoVersion:"go1.16.4", Compiler:"gc", 
Platform:"linux/amd64"}

Please also find attached the local build log.

Best regards,
Flo
diff -Nru kubernetes-1.20.5+really1.20.2/debian/changelog kubernetes-1.20.5+really1.20.2/debian/changelog
--- kubernetes-1.20.5+really1.20.2/debian/changelog	2021-06-13 09:08:18.0 +0200
+++ kubernetes-1.20.5+really1.20.2/debian/changelog	2022-04-02 16:49:13.0 +0200
@@ -1,3 +1,10 @@
+kubernetes (1.20.5+really1.20.2-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Build using golang-go (Closes: #1000980)
+
+ -- Florian Ernst   Sat, 02 Apr 2022 16:49:13 +0200
+
 kubernetes (1.20.5+really1.20.2-1) unstable; urgency=medium
 
   * This is actually still 1.20.2
diff -Nru kubernetes-1.20.5+really1.20.2/debian/control kubernetes-1.20.5+really1.20.2/debian/control
--- kubernetes-1.20.5+really1.20.2/debian/control	2021-06-13 09:08:18.0 +0200
+++ kubernetes-1.20.5+really1.20.2/debian/control	2022-04-02 16:49:00.0 +0200
@@ -2,7 +2,7 @@
 Section: admin
 Priority: optional
 Maintainer: Janos Lenart 
-Build-Depends: debhelper (>= 12~), bash-completion, golang-1.15-go, jq, rsync
+Build-Depends: debhelper (>= 12~), bash-completion, golang-go, jq, rsync
 Standards-Version: 4.5.0
 Homepage: http://kubernetes.io/
 
diff -Nru kubernetes-1.20.5+really1.20.2/debian/rules kubernetes-1.20.5+really1.20.2/debian/rules
--- kubernetes-1.20.5+really1.20.2/debian/rules	2020-10-21 13:29:24.0 +0200
+++ kubernetes-1.20.5+really1.20.2/debian/rules	2022-04-02 16:49:00.0 +0200
@@ -2,7 +2,7 @@
 
 export DH_VERBOSE = 1
 export GOPATH = $(CURDIR)/.go
-export PATH := /usr/lib/go-1.15/bin:$(PATH)
+export PATH := /usr/lib/go/bin:$(PATH)
 export CGO_ENABLED = 0
 
 %:
sbuild (Debian sbuild) 0.81.2 (31 January 2021) on fernst.no-ip.org

+==+
| kubernetes 1.20.5+really1.20.2-1.1 (amd64)   Sat, 02 Apr 2022 14:51:12 + |
+==+

Package: kubernetes
Version: 1.20.5+really1.20.2-1.1
Source Version: 1.20.5+really1.20.2-1.1
Distribution: unstable
Machine Architecture: amd64
Host Architecture: amd64
Build Architecture: amd64
Build Type: full

I: NOTICE: Log filtering will replace 
'var/run/schroot/mount/unstable-amd64-sbuild-84aad74e-1348-46a6-8c5c-123eb8e424d9'
 with '<>'
I: NOTICE: Log filtering will replace 'build/kubernetes-6AFsTn/resolver-UBQyvV' 
with '<>'

+--+
| Update chroot|
+--+

Get:1 http://127.0.0.1:3142/deb.debian.org/debian unstable InRelease [165 kB]
Get:2 http://127.0.0.1:3142/deb.debian.org/debian unstable/main 
Sources.diff/Index [63.6 kB]
Get:3 http://127.0.0.1:3142/deb.debian.org/debian unstable/main amd64 
Packages.diff/Index [63.6 kB]
Get:4 http://127.0.0.1:3142/deb.debian.org/debian unstable/main Sources 
T-2022-04-02

Bug#1000980: kubernetes: diff for NMU version 1.20.5+really1.20.2-1.1

[Florian Ernst]

Control: tags 1000980 + patch
Control: tags 1000980 + pending

Dear maintainer,

I've prepared an NMU for kubernetes (versioned as 1.20.5+really1.20.2-1.1)
and uploaded it to DELAYED/7. Please feel free to tell me if I should
delay it longer.

The diff is based on what I previously sent to this bugreport in
<https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000980#31>.
The binary package debdiff just lists
| $ debdiff kubernetes-client_1.20.5+really1.20.2-1_amd64.deb 
kubernetes-client_1.20.5+really1.20.2-1.1_amd64.deb
| File lists identical (after any substitutions)
| 
| Control files: lines which differ (wdiff format)
| 
| Installed-Size: [-40405-] {+38907+}
| Version: [-1.20.5+really1.20.2-1-] {+1.20.5+really1.20.2-1.1+}

I tested the kubectl binary against a local KinD cluster and found no
issues. Basic testing as follows:
| 15:47:27 ⌁0% 1d :~/debian/temp/kubernetes $ ./kubectl create deployment nginx 
--image=nginx
| deployment.apps/nginx created
| 15:47:57 ⌁0% 1d :~/debian/temp/kubernetes $ ./kubectl expose deployment nginx 
--type LoadBalancer --port 80
| service/nginx exposed
| 15:48:04 ⌁0% 1d :~/debian/temp/kubernetes $ kubectl get svc nginx
| NAMETYPE   CLUSTER-IP EXTERNAL-IPPORT(S)AGE
| nginx   LoadBalancer   10.96.54.121   172.19.255.1   80:30032/TCP   14s
| 15:48:18 ⌁0% 1d :~/debian/temp/kubernetes $ curl 172.19.255.1
| 
| 
| 
| Welcome to nginx!
| 
| html { color-scheme: light dark; }
| body { width: 35em; margin: 0 auto;
| font-family: Tahoma, Verdana, Arial, sans-serif; }
| 
| 
| 
| Welcome to nginx!
| If you see this page, the nginx web server is successfully installed and
| working. Further configuration is required.
| 
| For online documentation and support please refer to
| http://nginx.org/;>nginx.org.
| Commercial support is available at
| http://nginx.com/;>nginx.com.
| 
| Thank you for using nginx.
| 
| 
| 15:48:25 ⌁0% 1d :~/debian/temp/kubernetes $ ./kubectl get po
| NAME READY   STATUSRESTARTS   AGE
| nginx-6799fc88d8-v5ms9   1/1 Running   0  77s
| 15:48:59 ⌁0% 1d :~/debian/temp/kubernetes $ ./kubectl exec -it 
nginx-6799fc88d8-v5ms9 -- hostname
| nginx-6799fc88d8-v5ms9
| 15:49:20 ⌁0% 1d :~/debian/temp/kubernetes $ ./kubectl delete deploy,svc nginx
| deployment.apps "nginx" deleted
| service "nginx" deleted
| 15:49:36 ⌁0% 1d :~/debian/temp/kubernetes $ ./kubectl get po
| No resources found in default namespace.
| 15:49:41 ⌁0% 1d :~/debian/temp/kubernetes $ ./kubectl version
| Client Version: version.Info{Major:"1", Minor:"20", GitVersion:"v1.20.2", 
GitCommit:"faecb196815e248d3ecfb03c680a4507229c2a56", GitTreeState:"archive", 
BuildDate:"2022-04-02T13:36:06Z", GoVersion:"go1.17.8", Compiler:"gc", 
Platform:"linux/amd64"}
| Server Version: version.Info{Major:"1", Minor:"21", GitVersion:"v1.21.1", 
GitCommit:"5e58841cce77d4bc13713ad2b91fa0d961e69192", GitTreeState:"clean", 
BuildDate:"2021-05-21T23:01:33Z", GoVersion:"go1.16.4", Compiler:"gc", 
Platform:"linux/amd64"}

Please also find attached the local build log.

Best regards,
Flo
diff -Nru kubernetes-1.20.5+really1.20.2/debian/changelog kubernetes-1.20.5+really1.20.2/debian/changelog
--- kubernetes-1.20.5+really1.20.2/debian/changelog	2021-06-13 09:08:18.0 +0200
+++ kubernetes-1.20.5+really1.20.2/debian/changelog	2022-04-02 15:36:06.0 +0200
@@ -1,3 +1,10 @@
+kubernetes (1.20.5+really1.20.2-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Build using golang-1.17-go (Closes: #1000980)
+
+ -- Florian Ernst   Sat, 02 Apr 2022 15:36:06 +0200
+
 kubernetes (1.20.5+really1.20.2-1) unstable; urgency=medium
 
   * This is actually still 1.20.2
diff -Nru kubernetes-1.20.5+really1.20.2/debian/control kubernetes-1.20.5+really1.20.2/debian/control
--- kubernetes-1.20.5+really1.20.2/debian/control	2021-06-13 09:08:18.0 +0200
+++ kubernetes-1.20.5+really1.20.2/debian/control	2022-02-27 13:55:20.0 +0100
@@ -2,7 +2,7 @@
 Section: admin
 Priority: optional
 Maintainer: Janos Lenart 
-Build-Depends: debhelper (>= 12~), bash-completion, golang-1.15-go, jq, rsync
+Build-Depends: debhelper (>= 12~), bash-completion, golang-1.17-go, jq, rsync
 Standards-Version: 4.5.0
 Homepage: http://kubernetes.io/
 
diff -Nru kubernetes-1.20.5+really1.20.2/debian/rules kubernetes-1.20.5+really1.20.2/debian/rules
--- kubernetes-1.20.5+really1.20.2/debian/rules	2020-10-21 13:29:24.0 +0200
+++ kubernetes-1.20.5+really1.20.2/debian/rules	2022-02-27 13:55:20.0 +0100
@@ -2,7 +2,7 @@
 
 export DH_VERBOSE = 1
 export GOPATH = $(CURDIR)/.go
-export PATH := /usr/lib/go-1.15/bin:$(PATH)
+export PATH := /usr/lib/go-1.17/bin:$(PATH)
 export CGO_ENABLED = 0
 
 %:
sbuild (De

Bug#907174: New version available

[Florian Ernst]

Hello Andrew,

thank you for your feedback.

On Wed, Mar 30, 2022 at 07:47:52PM -0400, Andrew Ayer wrote:
> [...]
> I am thinking of putting libndp up for adoption - might you be willing
> to take over?

Well, I am willing to help, and if that means I take over that'd be fine
with me, thanks for considering. No need to file an RFA in that case, I
could just refer to this bugreport here if you approve.

Of course other work models are available, like co-maintenance or just
one-shot NMU'ing. But generally I prefer to get more directly involved.

Best regards,
Flo


signature.asc
Description: PGP signature

Bug#1008698: libprelude-dev: Depends on unavailable package libltdl3-dev

[Florian Ernst]

JFTR:

On Wed, Mar 30, 2022 at 10:00:26PM +0200, Florian Ernst wrote:
> libtool 2.4.7-2 started to not provide the virtual package libltdl3-dev
> anymore, and as such this package here is now uninstallable due to a
> Depends on it. [...]

Some more background can be found in
<https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008470>.

Best regards,
Flo


signature.asc
Description: PGP signature

Bug#1008698: libprelude-dev: Depends on unavailable package libltdl3-dev

[Florian Ernst]

Package: libprelude-dev
Version: 5.2.0-5+b2
Severity: grave
Justification: renders package unusable

Hello there,

libtool 2.4.7-2 started to not provide the virtual package libltdl3-dev
anymore, and as such this package here is now uninstallable due to a
Depends on it.

For reference, libtool migrated to just providing libltdl3-dev from
libltdl-dev starting with 2.2.6a-2 from 30 Mar 2009, but now libltdl-dev
does not provide any such compatibility provides anymore.

Best regards,
Flo


signature.asc
Description: PGP signature

Bug#912419: Please package the latest upstream version 0.1.11

[Florian Ernst]

Hello Pierre,

could you please comment on this, as I am wondering by now whether
libestr might be in need of salvaging.

Best regards,
Flo


signature.asc
Description: PGP signature

Bug#959007: liblognorm: Please provide new upstream release (2.0.6)

[Florian Ernst]

Hello Pierre,

could you please comment on this, as I am wondering by now whether
liblognorm might be in need of salvaging.

Best regards,
Flo


signature.asc
Description: PGP signature

Bug#907174: New version available

[Florian Ernst]

Hello Andrew,

could you please comment on this, as I am wondering by now whether
libndp might be in need of salvaging.

Best regards,
Flo


signature.asc
Description: PGP signature

Bug#987895: libyaml: 0.2.5 released upstream, not detected by watch file

[Florian Ernst]

Hello Anders,

I saw that you had been active in Debian recently, which is a relief as
I was wondering whether the libyaml package might be in need of
salvaging, given the apparent lack of activity over the last years.

Please share your thoughts on the topics below.

On Sat, Mar 05, 2022 at 05:45:59PM +0100, Florian Ernst wrote:
> On Sat, Feb 19, 2022 at 10:48:37AM +0100, Florian Ernst wrote:
> > [...]
> > Just as a heads-up, with the new upstream source the current packaging
> > still manages to build new packages, even though there seems to be some
> > doc-base weirdness now. The debdiff looks OK, and lintian has some old
> > and some new qualms that could/should be investigated. Please also find
> > attached the sbuild output.
> 
> Could you please comment on whether you have any plans for libyaml
> packaging? Thanks.
> 
> As written before there are updates available, and I am willing to help.

So I just took some time and prepared a more exhaustive update. Feel
free to pick up the parts you like - if any - for any eventual libyaml
update.

The changelog currently reads
| libyaml (0.2.5-0.1) UNRELEASED; urgency=medium
| 
|   [ Debian Janitor ]
|   * Use secure copyright file specification URI.
|   * Set debhelper-compat version in Build-Depends.
|   * Set upstream metadata fields: Bug-Database, Bug-Submit (from ./configure),
| Repository, Repository-Browse.
|   * Drop transition for old debug package migration.
|   * Update standards version to 4.6.0, no changes needed.
| 
|   [ Florian Ernst ]
|   * Non-maintainer upload.
|   * [de63dcd] debian/watch: update as per latest uscan recommendations.
| This allows detecting new upstream releases again and also migrates
| to the actual upstream source tarballs not containing any pre-built
| stuff like documentation, saving a bunch of lintian errors/warnings.
|   * [1b08058] New upstream version 0.2.5 (Closes: #987895)
|   * [dfbe297] debian/copyright: update years according to most recent changes
|   * [183f9d4] upgrade to recommended debhelper-compat (= 13)
| But ignore libtool library during installation and simplify debian/rules
|   * [982974f] debian/rules: enable hardening=+all
|   * [1f7cabe] debian/libyaml-0-2.symbols: add Build-Depends-Package
| meta-information
|   * [1104826] debian/control: declare Rules-Requires-Root: no
|   * [8f2e2e6] debian/tests/: add upstream tests as autopkgtest

i.e. it incorporates the Janitor MR from
<https://salsa.debian.org/andersk/libyaml/-/merge_requests/1>,
changes the upstream tarball and brings the packaging up-to-speed with
respect to recent best practices.

All packaging, including the autopkgtest, has been checked: the Salsa
pipeline at
<https://salsa.debian.org/florian/libyaml/-/pipelines/363041> for
building and static checks, and I successfully rebuilt all direct
reverse build-depends against the updated package (well, all that are
currently able to build, that is, as some are rather broken at the
moment). Full logs are available, of course.

You can find my state of packaging in a fork of your repo at
<https://salsa.debian.org/florian/libyaml>.

Cheers,
Flo


signature.asc
Description: PGP signature

Bug#990334: sbuild: Make usage of zfs snapshot/rollback and clone

[Florian Ernst]

Hello there,

On Sat, Jun 26, 2021 at 06:54:16AM +0200, Johannes Schauer Marin Rodrigues 
wrote:
> Quoting Juri Grabowski (2021-06-25 23:00:39)
> > overlayfs doesn't work with ZFS right now.  I mean, that through zfs
> > snapshot/rollback and clone features we can achieve better performance in
> > spawning and destroying new schroots.
> 
> Possibly. But if so, then that's something that schroot has to offer. Not
> sbuild.

JFTR, schroot already supports ZFS datasets with snapshotting and
cloning to create new sessions. For reference, I put a description of my
personal setup into
.

Cheers,
Flo


signature.asc
Description: PGP signature

Bug#988354: schroot: fails to enter zfs source chroots

[Florian Ernst]

Hello there,

On Tue, May 11, 2021 at 10:48:00AM +0200, Sebastian Ramacher wrote:
> Thanks for adding zfs support to schroot. While entering a zfs-backed
> chroot works fine, i.e., schroot -c unstable-amd64-sbuild, trying to
> enter the source chroot fails:
> [...]

FWIW, this works for me, so it might simply be that some additional
configuration is required. Thus the following just for reference:

My bash history tells me that I actually applied

# zfs set mountpoint=legacy zfspool/SYSTEM/srv/chroot/unstable-amd64-sbuild

when migrating to a ZFS-based schroot setup as per

# cat /etc/schroot/chroot.d/unstable-amd64-sbuild-*
[unstable-amd64-sbuild]
description=Debian unstable/amd64 autobuilder
groups=root,sbuild
root-groups=root,sbuild
profile=sbuild
type=zfs-snapshot
zfs-dataset=zfspool/SYSTEM/srv/chroot/unstable-amd64-sbuild
mount-options=-o relatime,async
command-prefix=/var/cache/pbuilder/ccache/sbuild-setup,eatmydata
aliases=UNRELEASED,sid,rc-buggy,experimental

and indeed it just works for me, cf. for illustration

$ schroot -c unstable-amd64-sbuild # normal access
(unstable-amd64-sbuild)fernst@fernst:~$ df -hT
Filesystem  
   Type   Size  Used Avail Use% Mounted on
zfspool/SYSTEM/srv/chroot/unstable-amd64-sbuild/schroot-unstable-amd64-sbuild-caeca563-8016-4209-a022-77f59f5d4058
 zfs 65G  359M   64G   1% /
tmpfs   
   tmpfs   16G 0   16G   0% /dev/shm
zfspool/SYSTEM/var  
   zfs 50G   33G   18G  65% /build
zfspool/SYSTEM/home/fernst  
   zfs264G  201G   64G  76% 
/home/fernst/debian
/dev/mapper/lvmpool-root
   ext415G   11G  4.0G  73% 
/etc/sudoers.d/local-reprotest
(unstable-amd64-sbuild)fernst@fernst:~$ # CTRL+D here
exit
$ schroot -c source:unstable-amd64-sbuild # accessing the source chroot as a 
normal user
E: Access not authorised
I: You do not have permission to access the schroot service.
I: This failure will be reported.
$ sudo schroot -c source:unstable-amd64-sbuil # accessing the source chroot via 
sudo
(unstable-amd64-sbuild)root@fernst:/home/fernst# touch /blubber # apply some 
change
(unstable-amd64-sbuild)root@fernst:/home/fernst# # CTRL+D here
exit
$ schroot -c unstable-amd64-sbuild
(unstable-amd64-sbuild)fernst@fernst:~$ ls -al /blubber # check whether the 
above change persisted
-rw-r--r-- 1 root root 0 Mar 29 16:09 /blubber
(unstable-amd64-sbuild)fernst@fernst:~$ # CTRL+D here
exit

The only glitch I had so far with ZFS-based schroot I just reported in
, and there is a simple fix available.

Cheers,
Flo


signature.asc
Description: PGP signature

Bug#1008616: /etc/schroot/setup.d/05zfs: make ZFS snapshot removal more robust

[Florian Ernst]

Package: schroot
Version: 1.6.10-12
Severity: minor
File: /etc/schroot/setup.d/05zfs
Tags: patch

Dear maintainer,

thank you for enabling ZFS usage.

Please consider the following patch to make clone removal a little more
robust:

| diff --git a/schroot/setup.d/05zfs b/schroot/setup.d/05zfs
| index 6ecc0196..785aee5f 100755
| --- a/schroot/setup.d/05zfs
| +++ b/schroot/setup.d/05zfs
| @@ -49,10 +49,10 @@ if [ "$CHROOT_TYPE" = "zfs-snapshot" ] && [ -n 
"$CHROOT_ZFS_CLONE_NAME" ]; then
|  if zfs list "$CHROOT_ZFS_CLONE_NAME" >/dev/null 2>&1
|  then
|  if [ "$VERBOSE" = "verbose" ]; then
| -zfs destroy "$CHROOT_ZFS_CLONE_NAME"
| +zfs destroy -r "$CHROOT_ZFS_CLONE_NAME"
|  zfs destroy "$CHROOT_ZFS_SNAPSHOT_NAME"
|  else
| -zfs destroy "$CHROOT_ZFS_CLONE_NAME" > /dev/null
| +zfs destroy -r "$CHROOT_ZFS_CLONE_NAME" > /dev/null
|  zfs destroy "$CHROOT_ZFS_SNAPSHOT_NAME" > /dev/null
|  fi
|  else

I.e. recursively destroy all children of that clone via the "-r" option.
Otherwise I can all too easily happen that such children exist in the
form of snapshots, e.g. when using zfsnap or any such tool that might
automatically create a snapshot of a ZFS dataset while it is in use.

For illustration, let's consider the following sequence of actions:

1. a user enters a ZFS-based chroot via
   $ schroot -c unstable-amd64-sbuild
2. schroot creates a snapshot of the base dataset and then a clone of
   that snapshot, e.g.
   $ zfs list -t all
   [...]
   
zfspool/SYSTEM/srv/chroot/unstable-amd64-sbuild@unstable-amd64-sbuild-44e762df-cab6-4cf3-99dd-15f0fd018d18
 0B  -  359M  -
   
zfspool/SYSTEM/srv/chroot/unstable-amd64-sbuild/schroot-unstable-amd64-sbuild-44e762df-cab6-4cf3-99dd-15f0fd018d18
 8K  62.2G  359M  legacy
3. some tool - here done manually - creates a snapshot of that clone
   $ sudo zfs snapshot 
zfspool/SYSTEM/srv/chroot/unstable-amd64-sbuild/schroot-unstable-amd64-sbuild-44e762df-cab6-4cf3-99dd-15f0fd018d18@test
4. the user exits their schroot session and schroot complains
   E: 05zfs: cannot destroy 
'zfspool/SYSTEM/srv/chroot/unstable-amd64-sbuild/schroot-unstable-amd64-sbuild-44e762df-cab6-4cf3-99dd-15f0fd018d18':
 filesystem has children
   E: 05zfs: use '-r' to destroy the following datasets:
   E: 05zfs: 
zfspool/SYSTEM/srv/chroot/unstable-amd64-sbuild/schroot-unstable-amd64-sbuild-44e762df-cab6-4cf3-99dd-15f0fd018d18@test
   E: unstable-amd64-sbuild-44e762df-cab6-4cf3-99dd-15f0fd018d18: Chroot setup 
failed: stage=setup-stop
5. $CHROOT_ZFS_CLONE_NAME and $CHROOT_ZFS_SNAPSHOT_NAME must be cleaned
   up manually

Cheers,
Flo


signature.asc
Description: PGP signature

Bug#1008172: ffmpeg: Please enable librist

[Florian Ernst]

Source: ffmpeg
Version: 7:4.4.1-3
Severity: wishlist
Tags: patch

Dear maintainers,

now that  is available (thanks
to really quick NEW processing) please enable librist in ffmpeg as per
the attached patch.

For reference, quoting from the package description
| Reliable Internet Stream Transport (RIST) is a transport protocol
| designed for reliable transmission of video over lossy networks
| (including the Internet) with low latency and high quality.
| .
| RIST is intended as a more reliable successor to Secure Reliable
| Transport (SRT), and as an open alternative to proprietary commercial
| options such as Zixi, VideoFlow, QVidium, and DVEO (Dozer).

And for further elaborating my motivation please see the ITP at
.
I just confirmed that with the attached patch ffmpeg still builds fine,
resulting in the same debdiff as presented in that ITP.

Cheers,
Flo
diff -Nru ffmpeg-4.4.1/debian/control ffmpeg-4.4.1/debian/control
--- ffmpeg-4.4.1/debian/control 2022-01-15 16:31:36.0 +0100
+++ ffmpeg-4.4.1/debian/control 2022-03-19 09:49:07.0 +0100
@@ -109,6 +109,8 @@
  libpulse-dev,
 # --enable-librabbitmq
  librabbitmq-dev,
+# --enable-librist
+ librist-dev,
 # --enable-librubberband
  librubberband-dev,
 # --enable-librsvg
diff -Nru ffmpeg-4.4.1/debian/rules ffmpeg-4.4.1/debian/rules
--- ffmpeg-4.4.1/debian/rules   2021-11-21 18:30:36.0 +0100
+++ ffmpeg-4.4.1/debian/rules   2022-03-19 09:49:07.0 +0100
@@ -52,6 +52,7 @@
--enable-libopus \
--enable-libpulse \
--enable-librabbitmq \
+   --enable-librist \
--enable-librubberband \
--enable-libshine \
--enable-libsnappy \


signature.asc
Description: PGP signature

Bug#971827: New upstream release (1.8.0)

[Florian Ernst]

retitle 971827 New upstream release (1.10.0)
thanks

On Thu, Oct 08, 2020 at 09:21:25AM +0200, Laurent Bigonville wrote:
> Would it be possible to package the new upstream release?
> 
> 1.8.0 - May 29, 2020
> 
> [...]

Well, JFTR, 1.8.0 entered the archives last year and is by now part of
Bullseye, cf.

and .

However, in the meantime two new versions have been released:

| 1.10.0 - Feb 14, 2022
| =
| - Add API for resolving multiple tree matches
| - Add API for resolving multiple media matches
| - Add API to match between two OsinfoTree
| - Add API to match between two OsinfoMedia
| - Add API to get a complete list of firmwares
| - Add missing documentation of osinfo_os_add_firmware()
| - Add release status to osinfo-query
| - Add --all flag to all tools to report all matches
| - Fix hiding database entries
| - Adapt to libsoup3 which is now preferred over libsoup2
| - Several CI improvements
| - Several translations improvements
| 1.9.0 - Feb 02, 2021
| 
| - Improve on the osinfo-tools' and osinfo-detect's help
| - Several CI improvements
| - Several translations improvements
| - Improve on debuggability of the loader code
| - Fix build when using clang
Cf. 

Please update the package when you think it is due time.

Cheers,
Flo


signature.asc
Description: PGP signature

Bug#1008073: lp-solve: New upstream release (5.5.2.11, 2020-12-31)

[Florian Ernst]

Package: lp-solve
Version: 5.5.2.5-2
Severity: wishlist

Dear maintainer,

there are two new upstream releases available, cf.
.

The attached debian/watch provides a start to allow uscan to detect them
and to download the new upstream tarballs.

Please update the package when you think it is due time.

Cheers,
Flo
version=4
https://sf.net/lpsolve/ \
lp_solve_@ANY_VERSION@_source@ARCHIVE_EXT@ debian
opts="component=doc" https://sf.net/lpsolve/ \
lp_solve_@ANY_VERSION@_doc@ARCHIVE_EXT@ same uupdate


signature.asc
Description: PGP signature

Bug#1008003: jansson: New upstream release (2.14, 2021 Sep 9), not detected by debian/watch

[Florian Ernst]

On Sun, Mar 20, 2022 at 01:56:10PM +0100, Florian Ernst wrote:
> The attached diff to debian/watch allows uscan to detect this version.

Yeah, right, a classic. So, now attached.

Cheers,
Flo
diff -Nru jansson-2.13.1/debian/watch jansson-2.13.1/debian/watch
--- jansson-2.13.1/debian/watch 2021-02-04 22:45:00.0 +0100
+++ jansson-2.13.1/debian/watch 2022-03-20 13:40:58.0 +0100
@@ -1,2 +1,4 @@
-version=3
-https://www.digip.org/jansson/releases/jansson-([\d+\.]*).tar.gz
+version=4
+opts="filenamemangle=s%(?:.*?)?v?(\d[\d.]*)\.tar\.gz%@PACKAGE@-$1.tar.gz%" \
+https://github.com/akheron/@PACKAGE@/tags \
+(?:.*?/)?v?(\d[\d.]*)\.tar\.gz


signature.asc
Description: PGP signature

Bug#1008003: jansson: New upstream release (2.14, 2021 Sep 9), not detected by debian/watch

[Florian Ernst]

Source: jansson
Version: 2.13.1-1.1
Severity: wishlist

Dear maintainer,

there is a new upstream release available, cf.
.

(For reference, the Homepage  now
redirects to .)

The attached diff to debian/watch allows uscan to detect this version.

The actual upstream differences contain some interesting items, cf.
, and of
these

looks like it would help with
 and/or .

Please update the package when you think it is due time.

Cheers,
Flo


signature.asc
Description: PGP signature

Bug#1007198: ITP: librist -- Reliable Internet Stream Transport for reliable transmission of video over lossy networks

[Florian Ernst]

tags 1007198 pending
thanks

On Sun, Mar 13, 2022 at 02:15:20PM +0100, Florian Ernst wrote:
> * Package name: librist
>   Version : v0.2.6
>   Upstream Author : VideoLAN and librist authors
> * URL : https://code.videolan.org/rist/librist
> * License : BSD 2-Clause "Simplified"
>   Programming Lang: C (+ asm)
>   Description : Reliable Internet Stream Transport for reliable 
> transmission of video over lossy networks
> [...]
> FFmpeg as present in Bookworm or newer already allows building against
> librist, hence a heads-up to the Debian Multimedia Maintainers. I will
> send a patch for evaluating librist linking once the package hits the
> archives.

FWIW, I was able to build FFmpeg against my local librist package using
the attached patch, the relevant part of the debdiff indicating success:

| Control files of package libavformat-extra58: lines which differ (wdiff 
format)
| 
---
| Depends: libavcodec58 (= [-7:4.4.1-3),-] {+7:4.4.1-3.1),+} libavutil56 (= 
[-7:4.4.1-3),-] {+7:4.4.1-3.1),+} libbluray2 (>= 1:0.2.2), libbz2-1.0, libc6 
(>= 2.33), libchromaprint1 (>= 1.3.2), libgme0 (>= 0.5.5), libgnutls30 (>= 
3.7.2), libopenmpt0 (>= 0.3.0), librabbitmq4 (>= 0.6.0), {+librist4 (>= 
0.2.6+dfsg),+} libsmbclient (>= 2:4.0.3+dfsg1), libsrt1.4-gnutls (>= 1.4.4), 
libssh-gcrypt-4 (>= 0.8.0), libxml2 (>= 2.7.4), libzmq5 (>= 4.0.1+dfsg), zlib1g 
(>= 1:1.2.0.2)
| Installed-Size: [-2741-] {+2749+}
| Provides: libavformat58 (= [-7:4.4.1-3)-] {+7:4.4.1-3.1)+}
| Version: [-7:4.4.1-3-] {+7:4.4.1-3.1+}
| [...]
| Control files of package libavformat58: lines which differ (wdiff format)
| -
| Depends: libavcodec58 (= [-7:4.4.1-3),-] {+7:4.4.1-3.1),+} libavutil56 (= 
[-7:4.4.1-3),-] {+7:4.4.1-3.1),+} libbluray2 (>= 1:0.2.2), libbz2-1.0, libc6 
(>= 2.33), libchromaprint1 (>= 1.3.2), libgme0 (>= 0.5.5), libgnutls30 (>= 
3.7.2), libopenmpt0 (>= 0.3.0), librabbitmq4 (>= 0.6.0), {+librist4 (>= 
0.2.6+dfsg),+} libsrt1.4-gnutls (>= 1.4.4), libssh-gcrypt-4 (>= 0.8.0), libxml2 
(>= 2.7.4), libzmq5 (>= 4.0.1+dfsg), zlib1g (>= 1:1.2.0.2)
| Version: [-7:4.4.1-3-] {+7:4.4.1-3.1+}

I will recheck that patch once librist hits the archive and then file a
corresponding wishlist but against FFmpeg for librist inclusion.

My packaging has just been uploaded to NEW, the current packaging can be
found at <https://salsa.debian.org/debian/librist>.

Cheers,
Flo
diff -Nru ffmpeg-4.4.1/debian/control ffmpeg-4.4.1/debian/control
--- ffmpeg-4.4.1/debian/control 2022-01-15 16:31:36.0 +0100
+++ ffmpeg-4.4.1/debian/control 2022-03-19 09:49:07.0 +0100
@@ -109,6 +109,8 @@
  libpulse-dev,
 # --enable-librabbitmq
  librabbitmq-dev,
+# --enable-librist
+ librist-dev,
 # --enable-librubberband
  librubberband-dev,
 # --enable-librsvg
diff -Nru ffmpeg-4.4.1/debian/rules ffmpeg-4.4.1/debian/rules
--- ffmpeg-4.4.1/debian/rules   2021-11-21 18:30:36.0 +0100
+++ ffmpeg-4.4.1/debian/rules   2022-03-19 09:49:07.0 +0100
@@ -52,6 +52,7 @@
--enable-libopus \
--enable-libpulse \
--enable-librabbitmq \
+   --enable-librist \
--enable-librubberband \
--enable-libshine \
--enable-libsnappy \


signature.asc
Description: PGP signature

Bug#1007198: ITP: librist -- Reliable Internet Stream Transport for reliable transmission of video over lossy networks

[Florian Ernst]

Package: wnpp
Severity: wishlist
Owner: Florian Ernst 
X-Debbugs-Cc: debian-de...@lists.debian.org, Debian Multimedia Maintainers 


* Package name: librist
  Version : v0.2.6
  Upstream Author : VideoLAN and librist authors
* URL : https://code.videolan.org/rist/librist
* License : BSD 2-Clause "Simplified"
  Programming Lang: C (+ asm)
  Description : Reliable Internet Stream Transport for reliable 
transmission of video over lossy networks

Reliable Internet Stream Transport (RIST) is a transport protocol
designed for reliable transmission of video over lossy networks
(including the Internet) with low latency and high quality.
.
RIST is intended as a more reliable successor to Secure Reliable
Transport (SRT), and as an open alternative to proprietary commercial
options such as Zixi, VideoFlow, QVidium, and DVEO (Dozer).


The second paragraph also describes my motivation for packaging this,
with my newly-acquired SRT maintainer hat on. Further information about
RIST (and most of the description above) can be found at
<https://en.wikipedia.org/wiki/Reliable_Internet_Stream_Transport>, and
further language wrappers and application integration can be found at
<https://code.videolan.org/rist>.

FFmpeg as present in Bookworm or newer already allows building against
librist, hence a heads-up to the Debian Multimedia Maintainers. I will
send a patch for evaluating librist linking once the package hits the
archives.

Cheers,
Flo


signature.asc
Description: PGP signature

Bug#983109: Build vlc with srt support

[Florian Ernst]

(>= 5.2.4), libmad0 (>= 0.15.1b-3), libmatroska7 
(>= 1.6.3), libmpcdec6 (>= 1:0.1~r435), libmpeg2-4 (>= 0.5.1), libmpg123-0 (>= 
1.28.0), libmtp9 (>= 1.1.0), libncursesw6 (>= 6), libnfs13 (>= 1.9.7), libogg0 
(>= 1.1.0), libopenmpt-modplug1 (>= 0.2.7386~beta20.3), libopus0 (>= 1.1), 
libpng16-16 (>= 1.6.2-1), libpostproc55 (>= 7:4.4), libprotobuf-lite23 (>= 
3.12.4), libpulse0 (>= 1.0), libraw1394-11 (>= 2.1.2), libresid-builder0c2a, 
librsvg2-2 (>= 2.14.4), libsamplerate0 (>= 0.1.7), libsdl-image1.2 (>= 1.2.10), 
libsdl1.2debian (>= 1.2.11), libsecret-1-0 (>= 0.7), libshine3 (>= 3.1.0), 
libshout3 (>= 2.2.2), libsidplay2, libsndio7.0 (>= [-1.1.0),-] {+1.8.1),+} 
libsoxr0 (>= 0.1.2), libspatialaudio0 (>= 0.3.0+git20180730+dfsg1), libspeex1 
(>= 1.2~beta3-1), libspeexdsp1 (>= 1.2~beta3.2-1), {+libsrt1.4-gnutls (>= 
1.4.4),+} libssh2-1 (>= 1.2.3), libstdc++6 (>= 11), libswscale5 (>= 7:4.4), 
libsystemd0, libtag1v5 (>= 1.9.1-2.2~), libtheora0 (>= 1.0), libtinfo6 (>= 6), 
libtwolame0 (>= 0.3.6), libudev1 (>= 183), libupnp13 (>= 1:1.8.3), libva-drm2 
(>= 1.1.0), libva2 (>= 2.2.0), libvlccore9 (>= [-3.0.16),-] {+3.0.17.3),+} 
libvorbis0a (>= 1.1.2), libvorbisenc2 (>= 1.1.2), libx264-163 (>= 
2:0.163.3060+git5db6aa6), libx265-199 (>= 3.5), libxcb-keysyms1 (>= 0.4.0), 
libxcb1, libxml2 (>= 2.7.4), libzvbi0 (>= 0.2.35), zlib1g (>= 1:1.1.4), 
vlc-plugin-abi-3-0-0f

So, all in all please consider enabling SRT again in VLC, thanks.

Some final notes: Yes, there were some warning around SRT parts during
compilations, but apparently nothing fatal. Yes, I simply shied away
from adjusting patch 0003 to apply cleanly, so I simply disabled it as
it didn't matter to my build environment. And yes, I now saw that there
were updates in the packaging repo on Salsa, but I had already started
my work based on the released source package from the archives.

Cheers,
Flo
diff -Nru vlc-3.0.16/debian/changelog vlc-3.0.17.3/debian/changelog
--- vlc-3.0.16/debian/changelog 2021-06-21 21:07:16.0 +0200
+++ vlc-3.0.17.3/debian/changelog   2022-03-12 14:38:28.0 +0100
@@ -1,3 +1,11 @@
+vlc (3.0.17.3-0.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * debian/:
+- Reenable srt (Closes: #983109)
+
+ -- Florian Ernst   Sat, 12 Mar 2022 14:38:28 +0100
+
 vlc (3.0.16-1) unstable; urgency=medium
 
   * Upload to unstable
diff -Nru vlc-3.0.16/debian/control vlc-3.0.17.3/debian/control
--- vlc-3.0.16/debian/control   2021-06-17 23:52:00.0 +0200
+++ vlc-3.0.17.3/debian/control 2022-03-12 14:38:28.0 +0100
@@ -91,6 +91,7 @@
libspatialaudio-dev,
libspeex-dev (>= 1.0.5),
libspeexdsp-dev (>= 1.0.5),
+   libsrt-gnutls-dev,
libssh2-1-dev,
libswscale-dev (>= 7:3.0),
libsystemd-dev [linux-any],
diff -Nru vlc-3.0.16/debian/patches/series vlc-3.0.17.3/debian/patches/series
--- vlc-3.0.16/debian/patches/series2021-06-17 23:52:00.0 +0200
+++ vlc-3.0.17.3/debian/patches/series  2022-03-12 14:38:10.0 +0100
@@ -1,3 +1,3 @@
 0001-configure-fix-linking-on-RISC-V-ISA.patch
 0002-Revert-configure-Require-libmodplug-0.8.9.patch
-0003-Do-not-generate-cache-during-build.patch
+#0003-Do-not-generate-cache-during-build.patch
diff -Nru vlc-3.0.16/debian/rules vlc-3.0.17.3/debian/rules
--- vlc-3.0.16/debian/rules 2021-06-17 23:52:00.0 +0200
+++ vlc-3.0.17.3/debian/rules   2022-03-12 14:38:28.0 +0100
@@ -76,6 +76,7 @@
--enable-soxr \
--enable-spatialaudio \
--enable-speex \
+   --enable-srt \
--enable-svg \
--enable-svgdec \
--enable-taglib \
@@ -112,7 +113,6 @@
 # projectm: broken
 # schroedinger: removed from Debian (#845037)
 # sparkle: MacOS X only
-# srt: broken package (#962624)
 # telx: incompatible with zvbi
 # vpx: not needed when having libavcodec
 # vsxu: not in Debian
@@ -141,7 +141,6 @@
--disable-projectm \
--disable-schroedinger \
--disable-sparkle \
-   --disable-srt \
--disable-telx \
--disable-vpx \
--disable-vsxu \
diff -Nru vlc-3.0.16/debian/vlc-plugin-access-extra.install 
vlc-3.0.17.3/debian/vlc-plugin-access-extra.install
--- vlc-3.0.16/debian/vlc-plugin-access-extra.install   2021-06-11 
20:56:47.0 +0200
+++ vlc-3.0.17.3/debian/vlc-plugin-access-extra.install 2022-03-12 
14:38:28.0 +0100
@@ -1,2 +1,3 @@
 usr/lib/*/vlc/plugins/access/libvnc_plugin.so
 usr/lib/*/vlc/plugins/access/libxcb_screen_plugin.so
+usr/lib/*/vlc/plugins/access/libaccess_srt_plugin.so


signature.asc
Description: PGP signature

Bug#987895: libyaml: 0.2.5 released upstream, not detected by watch file

[Florian Ernst]

Hello Anders,

On Sat, Feb 19, 2022 at 10:48:37AM +0100, Florian Ernst wrote:
> [...]
> Just as a heads-up, with the new upstream source the current packaging
> still manages to build new packages, even though there seems to be some
> doc-base weirdness now. The debdiff looks OK, and lintian has some old
> and some new qualms that could/should be investigated. Please also find
> attached the sbuild output.

Could you please comment on whether you have any plans for libyaml
packaging? Thanks.

As written before there are updates available, and I am willing to help.

Cheers,
Flo


signature.asc
Description: PGP signature

Bug#959007: liblognorm: Please provide new upstream release (2.0.6)

[Florian Ernst]

Hello Pierre,

On Fri, Feb 18, 2022 at 10:20:20PM +0100, Florian Ernst wrote:
> FWIW, I can confirm that when you apply the current packaging to upstream
> 2.0.6 it still manages to build its packages (albeit not entirely
> lintian clean and missing two new symbols "ln_constructCheckpointLEA"
> and "ln_destructCheckpointLEA").

Could you please comment on whether you have any plans for liblognorm
packaging? Thanks.

As written before there are updates available, and I am willing to help.

Cheers,
Flo


signature.asc
Description: PGP signature

Bug#907174: New version available

[Florian Ernst]

Hello Andrew,

On Wed, Feb 16, 2022 at 10:42:23PM +0100, Florian Ernst wrote:
> [...]
> Please find attached the changes to debian/ to ease review.

Could you please comment on whether you have any plans for libndp
packaging? Thanks.

As written before there are updates available, and I am willing to help.

Cheers,
Flo


signature.asc
Description: PGP signature

Bug#912419: Please package the latest upstream version 0.1.11

[Florian Ernst]

Hello Pierre,

On Fri, Feb 18, 2022 at 10:06:04PM +0100, Florian Ernst wrote:
> [...]
> FWIW, this is the relevant part of this bugfix:
> [...]

Could you please comment on whether you have any plans for libestr
packaging? Thanks.

As written before there are updates available, and I am willing to help.

Cheers,
Flo


signature.asc
Description: PGP signature

Bug#1006785: sagan: Please consider compiling with libdumbnet in order to enable Unified2 output support

[Florian Ernst]

Package: sagan
Version: 1.2.0-1.2
Severity: wishlist
Tags: patch

Dear maintainer,

sagan's configure script contains

| echo "   The libdnet headers cannot be found.  This library is used for 
Sagan's"
| echo "   Unified2 output support.  Please see:"
| echo "   https://wiki.quadrantsec.com/bin/view/Main/Unified2Output;

and etc/sagan.yaml further elaborates

|   # The 'unified2' output allows Sagan to write in Snort's unified2 format.
|   # This allows events/alerts generates by Sagan to be read and queued for
|   # external programs like Barnyard2 (http://www.securixlive.com/barnyard2/).
|   # Barnyard2 can then record events to various formats (Sguil, PostgreSQL,
|   # MySQL, MS-SQL, Oracle, etc).  Sagan must be compiled with libdnet support
|   # to use this function.


However, the current packaging explicitly disables libdnet support, but
the following small patch could be used to enable it:

| diff -Nru sagan-1.2.0/debian/control sagan-1.2.0/debian/control
| --- sagan-1.2.0/debian/control  2021-01-26 16:33:17.0 +0100
| +++ sagan-1.2.0/debian/control  2022-03-04 22:26:33.0 +0100
| @@ -14,7 +14,8 @@
|  libpq-dev,
|  libprelude-dev,
|  liblognorm-dev,
| -libyaml-dev
| +libyaml-dev,
| +libdumbnet-dev
|  Standards-Version: 4.1.4
|  Homepage: http://sagan.softwink.com/
|  #Vcs-Git: git://git.debian.org/collab-maint/sagan.git
| diff -Nru sagan-1.2.0/debian/rules sagan-1.2.0/debian/rules
| --- sagan-1.2.0/debian/rules2021-01-26 16:35:40.0 +0100
| +++ sagan-1.2.0/debian/rules2022-03-04 22:26:36.0 +0100
| @@ -17,7 +17,7 @@
| 
|  override_dh_auto_configure:
| dh_testdir
| -   dh_auto_configure -- 
--with-postgresql-includes=/usr/include/postgresql --disable-libdnet LIBS="-lm 
-lestr -lee"
| +   dh_auto_configure -- 
--with-postgresql-includes=/usr/include/postgresql --enable-libdnet LIBS="-lm 
-lestr -lee"
| 
|  override_dh_auto_install:
| dh_auto_install

The resulting binary package debdiff then merely indicates the
additional dependency on libdumbnet1:

| Control files of package sagan: lines which differ (wdiff format)
| -
| Depends: libc6 (>= 2.33), {+libdumbnet1 (>= 1.8),+} libfastjson4 (>= 0.99.3), 
liblognorm5 (>= 0.3.0), libpcre3, libyaml-0-2, adduser, sagan-rules, lsb-base 
(>= 3.0-6)
| Installed-Size: [-592-] {+608+}
| Version: [-1.2.0-1.2-] {+1.2.0-1.3+}

Please consider whether it's worthwhile to include libdumbnet support
into sagan, thanks.


Oh, JFTR, libdnet was renamed in Debian to libdumbnet due to a naming
conflict with a DECnet library, but luckily sagan knows how to deal with
that, see above. The project lay dormant for quite some time but now
found a new upstream.
Disclaimer: I am the new libdumbnet maintainer, so of course I am biased
on whether libdumbnet should be used.

Cheers,
Flo


signature.asc
Description: PGP signature

Bug#1006783: tcpreplay: Please consider compiling with libdumbnet in order to enable the fragroute feature

[Florian Ernst]

Package: tcpreplay
Version: 4.4.0-1
Severity: wishlist
Tags: patch

Dear maintainer,

when configuring tcpreplay the configure script provides the following
warning:

| checking for libdnet... no
| configure: WARNING: libdnet not found, disabling fragroute feature

and then the following configuration results:

| ##
|  TCPREPLAY Suite Configuration Results (4.4.0)
| ##
| libpcap:/usr (>= 0.9.6)
| PF_RING libpcap no
| libdnet:no
  ^^
| autogen:/usr/bin/autogen (5.18.16)
| Use libopts tearoff:yes
| 64bit counter support:  yes
| tcpdump binary path:/usr/bin/tcpdump
| fragroute support:  no
| tcpbridge support:  yes
| tcpliveplay support:yes
| 
| Supported Packet Injection Methods (*):
| Linux TX_RING:  no
| Linux PF_PACKET:yes
| BSD BPF:no
| libdnet:no
  ^^
| pcap_inject:yes
| pcap_sendpacket:yes **
| pcap_netmap no
| Linux/BSD netmap:   no
| Tuntap device support:  yes

(cf. e.g. 
)


However, merely adding libdumbnet-dev to B-D like this here

| diff -Nru tcpreplay-4.4.0/debian/control tcpreplay-4.4.0/debian/control
| --- tcpreplay-4.4.0/debian/control  2022-01-31 23:39:12.0 +0100
| +++ tcpreplay-4.4.0/debian/control  2022-03-04 21:55:20.0 +0100
| @@ -8,6 +8,7 @@
|  autogen,
|  libpcap0.8-dev,
|  tcpdump,
| +libdumbnet-dev,
|  Priority: optional
|  Rules-Requires-Root: no
|  Section: net

and then rebuilding results in

| checking for libdnet... /usr
| checking for dumbnet.h... yes

and then

| ##
|  TCPREPLAY Suite Configuration Results (4.4.0)
| ##
| libpcap:/usr (>= 0.9.6)
| PF_RING libpcap no
| libdnet:/usr   1.14 (libdumbnet)
  
| autogen:/usr/bin/autogen (5.18.16)
| Use libopts tearoff:yes
| 64bit counter support:  yes
| tcpdump binary path:/usr/bin/tcpdump
| fragroute support:  yes
| tcpbridge support:  yes
| tcpliveplay support:yes
| 
| Supported Packet Injection Methods (*):
| Linux TX_RING:  no
| Linux PF_PACKET:yes
| BSD BPF:no
| libdnet:yes
  ^^^
| pcap_inject:yes
| pcap_sendpacket:yes **
| pcap_netmap no
| Linux/BSD netmap:   no
| Tuntap device support:  yes

i.e. enabling fragroute support and the libdnet injection method.

The binary package debdiff then merely indicates the additional
dependency on libdumbnet1:

| Control files of package tcpreplay: lines which differ (wdiff format)
| -
| Depends: libc6 (>= 2.33), {+libdumbnet1 (>= 1.8),+} libpcap0.8 (>= 0.9.8)
| Installed-Size: [-1900-] {+1950+}
| Version: [-4.4.0-1-] {+4.4.0-1.1+}


Please consider whether it's worthwhile to include libdumbnet support
into tcpreplay, thanks.


Oh, JFTR, libdnet was renamed in Debian to libdumbnet due to a naming
conflict with a DECnet library, but luckily tcpreplay knows how to deal
with that, see above. The project lay dormant for quite some time but
now found a new upstream.
Disclaimer: I am the new libdumbnet maintainer, so of course I am biased
on whether libdumbnet should be used.

Cheers,
Flo


signature.asc
Description: PGP signature

Bug#990887: tig: Please update to 2.5.4

[Florian Ernst]

Following up to myself ...

On Mon, Jan 17, 2022 at 08:56:41PM +0100, Florian Ernst wrote:
> Now there is https://github.com/jonas/tig/releases/tag/tig-2.5.5, and I
> can confirm that the current packaging still allows to build a .deb from
> it.

The new releases cover many bugfixes (including some for segfaults) and
many nice improvements, see below.

Sebastian, in light of this, do you have any plans for updating the
package? Personally I'd very much like to have the new version available
in Debian (as opposed to just locally as mentioned above), and I
wouldn't mind doing the work myself. If you agree, of course.

However, I can also offer further assistance by taking a (co-)maintainer
role. Just let me know what you'd prefer.

FWIW, here is the list of bugfixes and improvements as applied by
upstream, cf. <https://github.com/jonas/tig/releases>:

| tig-2.5.5 Latest
| Improvements:
| - Make word-diff a toggleable option. (#1119, #1125)
| - Add Linux installation instructions. (#1121, #1126)
| - Allow :back to work across separate blame views. (#1123, #1127)
| - Add auto-refresh to log view. (#1128)
| - Expose %(file_old), useful for deleted and renamed files. (#1132)
| - Enable jumping back in main view. (#628, #1138)
| - Add PCRE (Perl Compatible Regular Expressions) support. (#1137, #1143)
| - Pass command line args through to diff-files in status view. (#1152, #1155)
| - Remove quotes from TIG_LS_REMOTE to allow inline shell commands. (#1160, 
#1161)
| - Avoid pushing identical history state in main view.
| - Replace useless strncpy to avoid compilation warning with GCC 8.
| - Update utf8proc to v2.7.0.
| - Update distclean rule to preserve tarball contents. (#1167, #1169)
| - Add reference types stash and other. (#1160, #1172)
| - Auto refresh view upon option change.
| - Allow to toggle revision filtering. (#1173)
| Bug fixes:
| - Fix null dereferences on unset format strings. (#1136, #1159)
| - Fix invalid read in log_read. (#1128)
| - Restore support for tig log --graph. (#1128)
| - Further fix to fullscreen navigation.
| - Fix blame when opened from an initial diff view. (#1135)
| - Fix stash view when using tig --all or tig revs. (#1146, #1147)
| - Avoiding null pointer dereference. (#1096)
| - Fix navigation between chunks after splitting chunk. (#1101, #1162)
| - Fix status line when toggling general options. (#1163, #1164)
| - Honor reference-format = hide:tag in diff view. (#1168, #1170)
| - Fix crash on :toggle file-args.
| 
| tig-2.5.4
| Improvements:
| - Add FreeBSD installation instructions. (#1093)
| - Add TIG_EDITOR environment variable to configure editor. (#889, #1098)
| - Enable mailmap by default to match git log's behaviour. (#1104, #1105)
| - Enable tilde expansion for diff-highlight. (#1107)
| Bug fixes:
| - Escape variables with %% in external commands. (#1091, #1095)
| - Fix parsing of -L argument. (#1100)
| - Bugfix: smart-case does not work when search term contains a space. (#1108)
| - Use ncursesw by default on Linux. (#920)
| - Replace obsolete macro `AC_CONFIG_HEADER' in configure.ac.
| 
| tig-2.5.3
| Bug fixes:
| - Fix autoconf checking for readline. (#1072)
| - Fix segfault when saving a view with no column.
| - Reset view->parent when main view is promoted.
| - Fix segfault when pressing Enter in a child main view.
| - Restore lazy navigation.
| - Format time_t values portably and fix other values too. (#1084, #1085)
| - Fix loop when wrapping line with ISO-8859-1 character. (#1087, #1088)
| 
| tig-2.5.2
| Incompatibilities:
| - Change directory from the next argument, from now use tig -C /path/to/repo. 
(#1079)
| Improvements:
| - Jump from blame to commit. (#355)
| - Start blame of an uncommitted deleted line from HEAD so the line's origin 
can be traced. (#1008, #1009)
| - Add line-graphics = auto. (#834, #1019)
| - Allow maxwidth to be expressed in % of the view width. (#1021)
| - Pass stash args through. (#1022, #1030)
| - Make build work on IBM i. (#1051, #1052)
| - Restore fullscreen navigation. (#1053)
| - Update utf8proc to v2.6.1.
| - Add some range so control chars ^^ and ^_ are also supported. (#1041, #1058)
| - Disable ncurses extended key values so that esc-codes can be used. (#1046, 
#1049)
| - Use id column for commit id only. (#1025, #1056)
| - Some minor updates for scrolling and for a double-click in diff. (#1060)
| - Add scroll-half-page-up and scroll-half-page-down actions. (#531, #1075)
| - Allow to generate a compilation database. (#1064)
| - New command stage-update-part.
| - The line number before a diff was applied is exposed as %(lineno_old). 
(#1081)
| Bug fixes:
| - Fix wrapping of lines with multibyte characters. (#988)
| - Improve highlighting of search with $ regex. (#1000)
| - Update tracking branch when refreshing status view. (#1015)
| - Fix vertical lines in Putty with UTF-8 graphics. (#981, #983)
| - Fix parsing of three-way chunk headers with extra dashes.
| - Update tracking branch when refreshing status v

Bug#1001529: libsrt-openssl-dev: pkg-config file applies to GnuTLS lib version

[Florian Ernst]

tags 1001529 patch
thanks

On Sat, Dec 11, 2021 at 04:55:07PM +0100, Stefan Pöschel wrote:
> Package: libsrt-openssl-dev
> Version: 1.4.2-1.3
> Severity: normal
> 
> The pkg-config files of this package (srt.pc and haisrt.pc) apply to the
> GnuTLS version (libsrt-gnutls-dev) of this library, as they refer to
> its lib name ("srt-gnutls") and to GnuTLS as dependancy. Therefore the
> files cannot be used to aid using the OpenSSL flavour of this library.

After building first the OpenSSL flavor and then the GnuTLS flavor
debian/rules installed both in that order into debian/tmp, claiming
this "Does not overwrite anything". Then, libsrt-openssl-dev.install
caused the *.pc files of the GnuTLS flavor to be installed for OpenSSL.

The intention then was to copy the *.pc files from their flavor-specific
build directories into their respective install tree, overwriting what
might already be there, but that unfortunately did not include the
correct path for OpenSSL.

The following patch fixes this:

| diff -Nru srt-1.4.2/debian/rules srt-1.4.2/debian/rules
| --- srt-1.4.2/debian/rules  2021-01-19 15:12:44.0 +0100
| +++ srt-1.4.2/debian/rules  2022-02-21 21:34:30.0 +0100
| @@ -60,8 +60,8 @@
| 
|  override_dh_install:
| dh_install
| -   install -d debian/libsrt-dev/usr/lib/$(DEB_HOST_MULTIARCH)/pkgconfig/
| -   install -m 0644 build-openssl/*.pc 
debian/libsrt-dev/usr/lib/$(DEB_HOST_MULTIARCH)/pkgconfig/
| +   install -d 
debian/libsrt-openssl-dev/usr/lib/$(DEB_HOST_MULTIARCH)/pkgconfig/
| +   install -m 0644 build-openssl/*.pc 
debian/libsrt-openssl-dev/usr/lib/$(DEB_HOST_MULTIARCH)/pkgconfig/
| install -d 
debian/libsrt-gnutls-dev/usr/lib/$(DEB_HOST_MULTIARCH)/pkgconfig/
| install -m 0644 build-gnutls/*.pc 
debian/libsrt-gnutls-dev/usr/lib/$(DEB_HOST_MULTIARCH)/pkgconfig/
| 

With this patch applied (and also with Steve's patch from #984352
applied to fix the FTBFS with GCC-11) the pkg-config files of
libsrt-openssl-dev turn out like this:

| prefix=/usr
| exec_prefix=${prefix}
| libdir=${exec_prefix}/lib/x86_64-linux-gnu
| includedir=${prefix}/include
| 
| Name: srt
| Description: SRT library set
| Version: 1.4.2
| Libs: -L${libdir} -lsrt
| Libs.private:  -lpthread -lstdc++ -lm -lgcc_s -lgcc -lc -lgcc_s -lgcc
| Cflags: -I${includedir} -I${includedir}/srt
| Requires.private: openssl libcrypto

Cheers,
Flo


signature.asc
Description: PGP signature

Bug#995230: [Pkg-rust-maintainers] Bug#995230: ripgrep: add autocompletion for bash

[Florian Ernst]

On Sun, Feb 20, 2022 at 06:42:54PM +0100, Sylvestre Ledru wrote:
> Le 20/02/2022 à 14:25, Florian Ernst a écrit :
> > In commit 7f0d6ae of rust-team/debcargo-conf the corresponding "--with
> > bash-completion" was dropped, most presumably by accident. As such bash
> > autocompletion was missing ever since 13.0.0-1. Readding that part
> > brings back the missing file:
> > [...]
> It seems. Would you like to provide a MR ?

Truth be told, I actively avoided the formal overhead of a MR for such a
tiny change. Feel free to just fix it in git.

However, if some policy of sorts requires a MR I will file one. If it's
just for attribution, though, I personally see no need.

Cheers,
Flo


signature.asc
Description: PGP signature

Bug#995230: ripgrep: add autocompletion for bash

[Florian Ernst]

On Tue, Sep 28, 2021 at 10:43:53AM +0200, Laurent Cheylus wrote:
> during build of ripgrep, a script (rg.bash) is generated via clap tool
> for autocompletion (see [...]
> This script is not included in Debian package v13.0.0-2. Please add it
> to be installed as /usr/share/bash-completion/completions/rg.

In commit 7f0d6ae of rust-team/debcargo-conf the corresponding "--with
bash-completion" was dropped, most presumably by accident. As such bash
autocompletion was missing ever since 13.0.0-1. Readding that part
brings back the missing file:

| diff -Nru rust-ripgrep-13.0.0/debian/rules rust-ripgrep-13.0.0/debian/rules
| --- rust-ripgrep-13.0.0/debian/rules2021-08-31 22:06:04.0 +0200
| +++ rust-ripgrep-13.0.0/debian/rules2022-02-20 13:48:27.0 +0100
| @@ -1,6 +1,6 @@
|  #!/usr/bin/make -f
|  %:
| -   dh $@ --buildsystem cargo
| +   dh $@ --buildsystem cargo --with bash-completion
| 
|  execute_after_dh_testdir:
| find . ! -newermt "jan 01, 2000" -exec touch {} +

and then after rebuilding the binary package

| $ debdiff ripgrep_13.0.0-2_amd64.deb ripgrep_13.0.0-2.1_amd64.deb
| [The following lists of changes regard files as different if they have
| different names, permissions or owners.]
| 
| Files in second .deb but not in first
| -
| -rw-r--r--  root/root   /usr/share/bash-completion/completions/rg
| drwxr-xr-x  root/root   /usr/share/bash-completion/
| drwxr-xr-x  root/root   /usr/share/bash-completion/completions/
| 
| Control files: lines which differ (wdiff format)
| [...]

Cheers,
Flo


signature.asc
Description: PGP signature

Bug#1000185: minidlna: diff for NMU version 1.3.0+dfsg-2.1

[Florian Ernst]

On Sun, Feb 13, 2022 at 11:15:12AM +0100, Florian Ernst wrote:
> diff -Nru minidlna-1.3.0+dfsg/debian/changelog 
> minidlna-1.3.0+dfsg/debian/changelog
> --- minidlna-1.3.0+dfsg/debian/changelog  2021-01-31 16:56:14.0 
> +0100
> +++ minidlna-1.3.0+dfsg/debian/changelog  2022-02-13 11:08:56.0 
> +0100
> @@ -1,3 +1,13 @@
> +minidlna (1.3.0+dfsg-2.1) unstable; urgency=medium
> +[...]
> +  * specify autofs.service dependency correctly, thanks to Mathieu Malaterre
> +and наб (Closes: #1000185)

Also thanks to Ross Vandegrift. Only just now when importing my NMU to
https://salsa.debian.org/debian/minidlna I saw that you had already
opened https://salsa.debian.org/debian/minidlna/-/merge_requests/3 two
months ago. I apologize for not noticing this any earlier and giving you
credit in debian/changelog.

Cheers,
Flo


signature.asc
Description: PGP signature

Bug#933098: RFA: xskat -- 3-player card game "Skat"

[Florian Ernst]

On Thu, Feb 17, 2022 at 09:34:57PM +0100, Florian Ernst wrote:
> Just by chance I now saw your mail while checking old bug reports. The
> package is still up for adoption, so if anyone's interested just go
> ahead.

JFTR, I received a bounce for Lars' mail address, so in my view this RFA
is unclaimed and thus still up for takers.

Apologies to Lars - if he ever sees this - for missing a chance when I
didn't see his mail in time.

Cheers,
Flo


signature.asc
Description: PGP signature

Bug#959007: liblognorm: Please provide new upstream release (2.0.6)

[Florian Ernst]

On Sat, Jan 29, 2022 at 08:54:16PM +0100, Florian Ernst wrote:
> JFTR, the Changelog at
> <https://www.liblognorm.com/news/liblognorm-2-0-6-released/> reads as
> follows:

FWIW, I can confirm that when you apply the current packaging to upstream
2.0.6 it still manages to build its packages (albeit not entirely
lintian clean and missing two new symbols "ln_constructCheckpointLEA"
and "ln_destructCheckpointLEA").

Cheers,
Flo


signature.asc
Description: PGP signature

Bug#912419: Please package the latest upstream version 0.1.11

[Florian Ernst]

On Sat, Jan 29, 2022 at 08:59:39PM +0100, Florian Ernst wrote:
> [...]
> | Version 0.1.11 2018-10-30
> [...]
> | - bugfix: es_str2num mishandling empty strings
> |   If es_str2num() receives an empty string, misadressing happens.
> |   Under extreme conditions, this theoretically can lead to a segfault.
> |   Thanks to Jan Gerhards for the patch.
> |   closes https://github.com/rsyslog/libestr/issues/10
> [...]

FWIW, this is the relevant part of this bugfix:

| diff -Nru libestr-0.1.10/src/string.c libestr-0.1.11/src/string.c
| --- libestr-0.1.10/src/string.c 2014-12-09 11:32:32.0 +0100
| +++ libestr-0.1.11/src/string.c 2018-10-18 18:38:39.0 +0200
| @@ -607,10 +607,10 @@
|  {
| long long num;
| unsigned char *c;
| -
| if(s->lenStr == 0) {
| num = 0;
| -   *bSuccess = 0;
| +   if(bSuccess != NULL)
| +   *bSuccess = 0;
| goto done;
| }
| 

And I can confirm that when you apply the current packaging to upstream
0.1.11 it still manages to build its packages (albeit not entirely
lintian clean).

Cheers,
Flo


signature.asc
Description: PGP signature

Bug#933098: RFA: xskat -- 3-player card game "Skat"

[Florian Ernst]

Hello there,

On Sat, Dec 07, 2019 at 12:32:57AM +, Barmettler Lars wrote:
> I'm a newcomer in the Debian development community and would like to ask 
> if I'm allowed to take over your game?

FWIW, thank you for asking. Generally, no asking for permission is
required. On the contrary, by filing an RFA bug I'm indeed asking for
someone to take over. Just for reference,
 provides all the
details.

That being said, why am I posting this now, over two years later? Well,
I simply haven't seen your mail any earlier, as it was sent solely to
the bug address, and this address by default does not forward to the bug
submitter, i.e. me. It does forward to the maintainer of the 'wnpp'
pseudo package, but this won't do much good. Just for reference,
 contains further
info.

Just by chance I now saw your mail while checking old bug reports. The
package is still up for adoption, so if anyone's interested just go
ahead. Not much has happened with the package over the years, but I did
take the chance to apply some minor updates, including salvaging the git
repo and putting it on salsa, as now linked from the package page, cf.
.

Cheers,
Flo


signature.asc
Description: PGP signature

Bug#907174: New version available

[Florian Ernst]

On Tue, Jan 18, 2022 at 05:15:39PM +0100, Florian Ernst wrote:
> On Fri, Aug 24, 2018 at 03:14:18PM +0200, Sebastien Bacher wrote:
> > There is a new upstream version available, it would be nice to get the
> > update in Debian
> > https://github.com/jpirko/libndp/commits/v1.7
> 
> FWIW, by now there already is v1.8 available, with commits dealing with
> some leaks and a buffer overflow and adding options to ndptool.

I have prepared a rather minimal update for this at
<https://salsa.debian.org/florian/libndp> (i.e. in a fork of the latest
<https://salsa.debian.org/debian/libndp>). Of course further changes are
possible, as e.g. suggested by lintian.

Upstream v1.8 seems to build sanely from this, and I also tested
building the reverse dependencies of libndp-dev, i.e. network-manager,
which succeeded as well showing no differences.

Please find attached the changes to debian/ to ease review.

Cheers,
Flo
diff --git a/debian/changelog b/debian/changelog
index 173649e..cab4437 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,38 @@
+libndp (1.8-0.1) UNRELEASED; urgency=medium
+
+  [ Michael Biebl ]
+  * Drop --disable-silent-rules from debian/rules. This is now handled by dh
+directly depending on whether the DH_QUIET environment variable is set.
+
+  [ Ondřej Nový ]
+  * d/copyright: Use https protocol in Format field
+  * d/control: Deprecating priority extra as per policy 4.0.1
+  * d/control: Set Vcs-* to salsa.debian.org
+
+  [ Debian Janitor ]
+  * [07f0e48] Transition to automatic debug package (from: libndp-dbg).
+Changes-By: lintian-brush
+Fixes: lintian: debian-control-has-obsolete-dbg-package
+See-also: https://lintian.debian.org/tags/debian-control-has-obsolete-dbg-package.html
+  * [0e8a255] Bump debhelper from deprecated 9 to 10.
+Changes-By: lintian-brush
+Fixes: lintian: package-uses-deprecated-debhelper-compat-version
+See-also: https://lintian.debian.org/tags/package-uses-deprecated-debhelper-compat-version.html
+  * [3ef06fb] Set upstream metadata fields: Bug-Database, Bug-Submit, Repository, Repository-Browse.
+Changes-By: lintian-brush
+Fixes: lintian: upstream-metadata-file-is-missing
+See-also: https://lintian.debian.org/tags/upstream-metadata-file-is-missing.html
+Fixes: lintian: upstream-metadata-missing-bug-tracking
+See-also: https://lintian.debian.org/tags/upstream-metadata-missing-bug-tracking.html
+Fixes: lintian: upstream-metadata-missing-repository
+See-also: https://lintian.debian.org/tags/upstream-metadata-missing-repository.html
+
+  [ Florian Ernst ]
+  * [2f15507] New upstream version 1.8 (Closes: #907174)
+  * [79a30ff] update symbols for upstream 1.8
+
+ -- Florian Ernst   Wed, 16 Feb 2022 22:24:38 +0100
+
 libndp (1.6-1) unstable; urgency=high
 
   * New upstream release. Fixes CVE-2016-3698. (Closes: #824545, #781755)
@@ -65,4 +100,3 @@ libndp (1.2-1) unstable; urgency=low
   * Initial release (Closes: #742973)
 
  -- Andrew Ayer   Sat, 29 Mar 2014 10:40:30 -0700
-
diff --git a/debian/compat b/debian/compat
index ec63514..f599e28 100644
--- a/debian/compat
+++ b/debian/compat
@@ -1 +1 @@
-9
+10
diff --git a/debian/control b/debian/control
index 3df0519..d68b3e9 100644
--- a/debian/control
+++ b/debian/control
@@ -1,26 +1,12 @@
 Source: libndp
 Priority: optional
 Maintainer: Andrew Ayer 
-Build-Depends: debhelper (>= 9)
+Build-Depends: debhelper (>= 10~)
 Standards-Version: 3.9.8
 Section: net
 Homepage: http://libndp.org
-Vcs-Git: https://anonscm.debian.org/git/collab-maint/libndp.git
-Vcs-Browser: https://anonscm.debian.org/gitweb/?p=collab-maint/libndp.git
-
-Package: libndp-dbg
-Section: debug
-Priority: extra
-Architecture: linux-any kfreebsd-any
-Multi-Arch: same
-Depends: libndp0 (= ${binary:Version}), ${misc:Depends}
-Description: Library for Neighbor Discovery Protocol (debug symbols)
- libndp is a library for the IPv6 Neighbor Discovery Protocol (NDP).  It
- contains functions for building and parsing NDP messages, and provides
- a high-level interface for sending and receiving NDP messages on a
- network interface.
- .
- This package provides debug symbols.
+Vcs-Git: https://salsa.debian.org/debian/libndp.git
+Vcs-Browser: https://salsa.debian.org/debian/libndp
 
 Package: libndp-dev
 Section: libdevel
diff --git a/debian/copyright b/debian/copyright
index abae717..2036d75 100644
--- a/debian/copyright
+++ b/debian/copyright
@@ -1,4 +1,4 @@
-Format: http://www.debian.org/doc/packaging-manuals/copyright-format/1.0/
+Format: https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/
 Upstream-Name: libndp
 Source: https://github.com/jpirko/libndp
 
diff --git a/debian/libndp0.symbols b/debian/libndp0.symbols
index 72f91b4..556f385 100644
--- a/debian/libndp0.symbols
+++ b/debian/libndp0.symbols
@@ -5,6 +5,7 @@ libndp.so.0 libndp0 #MINVER#
  ndp_get_eventfd@Base 1.2
  ndp_get_log_priority@Base 1.2
  ndp_msg_addrto@Base 1.2
+ ndp_

Bug#984114: liblastfm: diff for NMU version 1.0.9-1.2

[Florian Ernst]

Hello Stefan,

On Sun, Feb 13, 2022 at 11:30:07AM +, Stefan Ahlers wrote:
> I apologize for the very long delay. Thank you for preparing an NMU. Due to
> my private situation I'm unable to continue maintaining this package.
> Therefore, where is no reason to delay the upload any longer.

Thanks for the feedback! I have thus just rescheduled the upload from
DELAYED/7 to DELAYED/0.

Also thank you for your contributions, and all the best from my side.
I see that you have orphaned your remaining packages, and I'm sorry to
see you go.  Perhaps some other time again ...

Cheers,
Flo


signature.asc
Description: PGP signature

Bug#1000185: minidlna: diff for NMU version 1.3.0+dfsg-2.1

[Florian Ernst]

Dear maintainer,

I've prepared an NMU for minidlna (versioned as 1.3.0+dfsg-2.1) and
uploaded it to DELAYED/7. Please feel free to tell me if I
should delay it longer.

Cheers,
Flo
diff -Nru minidlna-1.3.0+dfsg/debian/changelog minidlna-1.3.0+dfsg/debian/changelog
--- minidlna-1.3.0+dfsg/debian/changelog	2021-01-31 16:56:14.0 +0100
+++ minidlna-1.3.0+dfsg/debian/changelog	2022-02-13 11:08:56.0 +0100
@@ -1,3 +1,13 @@
+minidlna (1.3.0+dfsg-2.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * fix FTBFS with newer autoconf by patching configure.ac.
+(Closes: #993241)
+  * specify autofs.service dependency correctly, thanks to Mathieu Malaterre
+and наб (Closes: #1000185)
+
+ -- Florian Ernst   Sun, 13 Feb 2022 11:08:56 +0100
+
 minidlna (1.3.0+dfsg-2) unstable; urgency=medium
 
   [ Debian Janitor ]
diff -Nru minidlna-1.3.0+dfsg/debian/minidlna.service minidlna-1.3.0+dfsg/debian/minidlna.service
--- minidlna-1.3.0+dfsg/debian/minidlna.service	2021-01-31 14:16:48.0 +0100
+++ minidlna-1.3.0+dfsg/debian/minidlna.service	2022-02-13 10:58:08.0 +0100
@@ -1,7 +1,7 @@
 [Unit]
 Description=MiniDLNA lightweight DLNA/UPnP-AV server
 Documentation=man:minidlnad(1) man:minidlna.conf(5)
-After=local-fs.target remote-fs.target autofs
+After=local-fs.target remote-fs.target autofs.service
 
 [Service]
 User=minidlna
diff -Nru minidlna-1.3.0+dfsg/debian/patches/fix_FTBFS_configure_error.patch minidlna-1.3.0+dfsg/debian/patches/fix_FTBFS_configure_error.patch
--- minidlna-1.3.0+dfsg/debian/patches/fix_FTBFS_configure_error.patch	1970-01-01 01:00:00.0 +0100
+++ minidlna-1.3.0+dfsg/debian/patches/fix_FTBFS_configure_error.patch	2022-02-13 11:08:11.0 +0100
@@ -0,0 +1,27 @@
+Description: Fix build issue with newer autoconf
+Bug-Debian: https://bugs.debian.org/993241
+Bug-Upstream: https://sourceforge.net/p/minidlna/bugs/341/
+Index: minidlna-1.3.0+dfsg/configure.ac
+===
+--- minidlna-1.3.0+dfsg.orig/configure.ac
 minidlna-1.3.0+dfsg/configure.ac
+@@ -414,7 +414,7 @@ for dir in "" /usr/local $SEARCH_DIR; do
+ AC_CHECK_LIB([id3tag -lz], [id3_file_open], [LIBID3TAG_LIBS="-lid3tag -lz"], [unset ac_cv_lib_id3tag_id3_file_open; LDFLAGS="$LDFLAGS_SAVE"; continue])
+ break
+ done
+-test x"$ac_cv_lib_id3tag__lz___id3_file_open" = x"yes" || AC_MSG_ERROR([Could not find libid3tag])
++test x"$ac_cv_lib_id3tag__lz_id3_file_open" = x"yes" || AC_MSG_ERROR([Could not find libid3tag])
+ AC_SUBST(LIBID3TAG_LIBS)
+ 
+ LDFLAGS_SAVE="$LDFLAGS"
+@@ -440,8 +440,8 @@ for dir in "" /usr/local $SEARCH_DIR; do
+ 		  [unset ac_cv_lib_avformat_av_open_input_file; unset ac_cv_lib_avformat_avformat_open_input; LDFLAGS="$LDFLAGS_SAVE"; continue])])
+ break
+ done
+-if test x"$ac_cv_lib_avformat__lavcodec__lavutil__lz___av_open_input_file" != x"yes" &&
+-   test x"$ac_cv_lib_avformat__lavcodec__lavutil__lz___avformat_open_input" != x"yes"; then
++if test x"$ac_cv_lib_avformat__lavcodec__lavutil__lz_av_open_input_file" != x"yes" &&
++   test x"$ac_cv_lib_avformat__lavcodec__lavutil__lz_avformat_open_input" != x"yes"; then
+AC_MSG_ERROR([Could not find libavformat - part of ffmpeg])
+ fi
+ AC_SUBST(LIBAVFORMAT_LIBS)
diff -Nru minidlna-1.3.0+dfsg/debian/patches/series minidlna-1.3.0+dfsg/debian/patches/series
--- minidlna-1.3.0+dfsg/debian/patches/series	2021-01-31 16:53:51.0 +0100
+++ minidlna-1.3.0+dfsg/debian/patches/series	2022-01-16 11:57:06.0 +0100
@@ -5,3 +5,4 @@
 08-Fix-testupnpdescgen-build.patch
 09-do-not-disable-logs-with-systemd.patch
 10-do-not-close-socket-on-sighup.patch
+fix_FTBFS_configure_error.patch


signature.asc
Description: PGP signature

Bug#984114: liblastfm: diff for NMU version 1.0.9-1.2

[Florian Ernst]

Dear maintainer,

I've prepared an NMU for liblastfm (versioned as 1.0.9-1.2) and
uploaded it to DELAYED/7. Please feel free to tell me if I
should delay it longer.

Cheers,
Flo
diff -Nru liblastfm-1.0.9/debian/changelog liblastfm-1.0.9/debian/changelog
--- liblastfm-1.0.9/debian/changelog	2019-08-23 23:37:23.0 +0200
+++ liblastfm-1.0.9/debian/changelog	2022-02-13 08:04:58.0 +0100
@@ -1,3 +1,11 @@
+liblastfm (1.0.9-1.2) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix FTBFS with GCC-11 by removing dynamic exception specifications,
+patch taken from upstream PR. (Closes: #984114)
+
+ -- Florian Ernst   Sun, 13 Feb 2022 08:04:58 +0100
+
 liblastfm (1.0.9-1.1) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -Nru liblastfm-1.0.9/debian/patches/fix_gcc11_ftbfs.patch liblastfm-1.0.9/debian/patches/fix_gcc11_ftbfs.patch
--- liblastfm-1.0.9/debian/patches/fix_gcc11_ftbfs.patch	1970-01-01 01:00:00.0 +0100
+++ liblastfm-1.0.9/debian/patches/fix_gcc11_ftbfs.patch	2022-02-13 08:03:57.0 +0100
@@ -0,0 +1,49 @@
+Description: Fix GCC-11 build issue
+Author: Xeonacid
+Bug-Debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984114
+Bug-Upstream: https://github.com/lastfm/liblastfm/issues/39
+Origin: upstream, https://github.com/lastfm/liblastfm/pull/41/commits/d51ad3e759331d7d79c6675c5d22541280bf9a70
+Index: liblastfm-1.0.9/src/fingerprint/Fingerprint.cpp
+===
+--- liblastfm-1.0.9.orig/src/fingerprint/Fingerprint.cpp
 liblastfm-1.0.9/src/fingerprint/Fingerprint.cpp
+@@ -94,7 +94,7 @@ lastfm::Fingerprint::data() const
+ 
+ 
+ void
+-lastfm::Fingerprint::generate( FingerprintableSource* ms ) throw( Error )
++lastfm::Fingerprint::generate( FingerprintableSource* ms )
+ {
+ //TODO throw if we can't get required metadata from the track object
+ 
+@@ -306,7 +306,7 @@ lastfm::Fingerprint::submit() const
+ 
+ 
+ void
+-lastfm::Fingerprint::decode( QNetworkReply* reply, bool* complete_fingerprint_requested ) throw( Error )
++lastfm::Fingerprint::decode( QNetworkReply* reply, bool* complete_fingerprint_requested )
+ {
+ // The response data will consist of a number and a string.
+ // The number is the fpid and the string is either FOUND or NEW
+Index: liblastfm-1.0.9/src/fingerprint/Fingerprint.h
+===
+--- liblastfm-1.0.9.orig/src/fingerprint/Fingerprint.h
 liblastfm-1.0.9/src/fingerprint/Fingerprint.h
+@@ -71,7 +71,7 @@ namespace lastfm
+ };
+ 
+ /** This is CPU intensive, do it in a thread in your GUI application */
+-void generate( FingerprintableSource* ) throw( Error );
++void generate( FingerprintableSource* );
+ 
+ /** Submits the fingerprint data to Last.fm in order to get a FingerprintId
+   * back. You need to wait for the QNetworkReply to finish before you can
+@@ -82,7 +82,7 @@ namespace lastfm
+   * will be valid. Otherwise we will throw. You always get a valid id
+   * or a throw.
+   */
+-void decode( QNetworkReply*, bool* lastfm_needs_a_complete_fingerprint = 0 ) throw( Error );
++void decode( QNetworkReply*, bool* lastfm_needs_a_complete_fingerprint = 0 );
+ };
+ 
+ 
diff -Nru liblastfm-1.0.9/debian/patches/series liblastfm-1.0.9/debian/patches/series
--- liblastfm-1.0.9/debian/patches/series	2015-11-20 16:42:23.0 +0100
+++ liblastfm-1.0.9/debian/patches/series	2022-01-14 22:27:26.0 +0100
@@ -1,2 +1,3 @@
 change_target-name.patch
 strip_README.patch
+fix_gcc11_ftbfs.patch


signature.asc
Description: PGP signature

Bug#996240: ncdu: new stable upstream version 1.16

[Florian Ernst]

On Tue, Oct 12, 2021 at 03:02:35PM +0200, Christian Göttsche wrote:
> Please package the latest (stable) upstream version 1.16.

FWIW, the ChangeLog reads

| 1.16 - 2021-07-02
|- Increase width of size bar depending on terminal size (Christian 
Göttsche)
|- Set/increment $NCDU_LEVEL variable when spawning a shell
|- Indicate whether apparent size or disk usage is being displayed
|- Display setuid, setgid and sticky bits in file flags in extended mode
|- Fix error handling while reading --exclude-from file
|- Improve JSON import to allow for several future extensions to the 
format
|- Export link count in JSON dumps
|- Don't export inode in JSON dumps for non-hardlinks

and I can confirm that the current packaging still manages to produce a
sensible-looking .deb when applied to upstream's 1.16.

Upstream's 2.x will be an entirely different matter, though, due to the
rewrite in Zig. JFTR,  is the ITP for Zig.

Cheers,
Flo


signature.asc
Description: PGP signature

Bug#1004590: librabbitmq: New upstream release (0.11.0, 2021 Apr 01)

[Florian Ernst]

Source: librabbitmq
Version: 0.10.0-1
Severity: wishlist

Dear maintainer,

there is a new upstream release available which uscan did not detect,
cf. .

The changes contain

| Added:
| - rabbitmq-c-config.cmake is now generated (#611)
| - rabbitmq-c can be compiled on Win32 using pthreads (#613)
| - Add amqp_set_ssl_engine API to allow setting OpenSSL engine (#618)
| - Add amqp_ssl_socket_set_key_engine API to allow setting OpenSSL engine 
(#618)
| - Add support use of password-protected SSL keys (#661)
| Changed
| - Update OpenSSL library initialization to current best practices (#603)
| - Updates to OpenSSL to support v3.0.0 (#654, 627)
| Fixed:
| - OpenSSL symbol clash when compiling on Win32 (#583)
| - Restore correct non-blocking behavior using OpenSSL v1.1.1 (#586)
| - Disable harmless secure CRT compile warnings on Win32 (#588)
| - Fix unused parameter warnings on Win32 (#591)
| - Fix invalid format in generated pkg-config file (#599)
| - Fix invalid AMQP_STATUS_HEARTBEAT_TIMEOUT (#557)
| - Fix incorrect port when using --server flag in CLI tools

Please update the package when you think it is due time.

Cheers,
Flo


signature.asc
Description: PGP signature

Bug#1004582: htop: New upstream release (3.1.2, 2021 Nov 30)

[Florian Ernst]

On Sun, Jan 30, 2022 at 08:26:27PM +0100, Daniel Lange wrote:
> https://github.com/htop-dev/htop/issues/806
> and
> https://github.com/htop-dev/htop/issues/863
> are the reasons I have not updated htop in sid yet.
> Waiting for these to get fixed.

Thanks for the feedback and thanks for taking care.

I trust you know best. :-)

Cheers,
Flo


signature.asc
Description: PGP signature

Bug#1004588: libzip: New upstream release (1.8.0, 2021 Jun 18)

[Florian Ernst]

Source: libzip
Version: 1.7.3-1
Severity: wishlist

Dear maintainer,

there is a new upstream release available, cf.
.

The changes contain

| Add support for zstd (Zstandard) compression.
| Add support for lzma (ID 14) compression.
| Add zip_source_window_create().
| Add zip_source_zip_create() variant to zip_source_zip().
| Allow method specific comp_flags in zip_set_file_compression().
| Allow zip_source_tell() on sources that don't support seeking and zip_ftell() 
on compressed data.
| Provide more details for consistency check errors.
| Improve output of zipcmp.
| In zipcmp, don’t ignore empty directories when comparing directory listing.
| Treat empty string as no password given in zip_file_set_encryption(), 
zip_fopen_encrypted(), and zip_set_default_password().

which seem nice enough to eventually have in Debian.

Please update the package when you think it is due time.

Cheers,
Flo


signature.asc
Description: PGP signature

Bug#705913: Choosing -ize/-ise has no effect

[Florian Ernst]

Package: aspell-en
Followup-For: Bug #705913

Hello all,

FWIW, for me the same invocation now yields

| enen-variant_0  en-variant_1  en-variant_2  en-w_accents  
en-wo_accents  en_AU  organization
| en_AU-variant_0   organization
| en_AU-variant_1   organization
| en_AU-w_accents   organization
| en_AU-wo_accents  organization
| en_CA analysed
| en_CA-variant_0   analysed
| en_CA-variant_1   analysed
| en_CA-w_accents   analysed
| en_CA-wo_accents  analysed
| en_GB organization
| en_GB-ise organization
| en_GB-ise-w_accents   organization
| en_GB-ise-wo_accents  organization
| en_GB-ize organization
| en_GB-ize-w_accents   organization
| en_GB-ize-wo_accents  organization
| en_GB-variant_0   organization
| en_GB-variant_1   organization
| en_GB-w_accents   organization
| en_GB-wo_accents  organization
| en_US analysed  labour
| en_US-variant_0   analysed  labour
| en_US-variant_1   analysed  labour
| en_US-w_accents   analysed  labour
| en_US-wo_accents  analysed  labour

which to me (yes, I not a native speaker) looks OK.

Maybe I'm missing something here, though ...

Cheers,
Flo

-- System Information:
Debian Release: 11.2
  APT prefers stable-updates
  APT policy: (990, 'stable-updates'), (990, 'stable-security'), (990, 
'stable'), (50, 'testing-proposed-updates'), (50, 'proposed-updates'), (50, 
'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.10.0-10-amd64 (SMP w/8 CPU threads)
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=en_US
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages aspell-en depends on:
ii  aspell   0.60.8-3
ii  dictionaries-common  1.28.4

aspell-en recommends no packages.

aspell-en suggests no packages.

-- no debconf information


signature.asc
Description: PGP signature

Bug#1004582: htop: New upstream release (3.1.2, 2021 Nov 30)

[Florian Ernst]

Package: htop
Version: 3.0.5-7
Severity: wishlist

Dear maintainer,

there are new upstream releases available, cf.
.

The ChangeLog lists

| What's new in version 3.1.2
| 
| * Bugfix for crash when storing modified settings at exit
| * Generate xz-compressed source tarball (with configure) using github actions
| * Allow -u UID with numerical value as argument
| * Added documentation for obsolete/state libraries/program files highlighting
| * Some obsolete/stale library highlighting refinements
| * Column width issues resolved
| * Dynamic UID column sizing improved
| * Discard stale information from Disk and Network I/O meters
| * Refined Linux kernel thread detection
| * Reworked process state handling
| * New CCGROUP column showing abbreviated cgroup name
| * New OFFSET column in the list of open files screen
| 
| What's new in version 3.1.1
| 
| * Update license headers to explicitly say GPLv2+
| * Document minimum version for libcap (thanks to James Brown)
| * Fix mouse wheel collision with autogroups nice adjustment
| * Adjust Makefile.am macro definitions for older automake versions
| * Ensure consistent reporting of MemoryMeter 'used' memory
| * Report hugepage memory as real and used memory (as before)
| * Handle procExeDeleted, usesDeletedLib without mergedCommandline mode
| * Validate meter configuration before proceeding beyond htoprc parsing
| * Properly release memory on partially read configuration
| * Handle interrupted sampling from within libpcp PDU transfers
| * On Linux, provide O_PATH value if not defined
| * On Linux, always compute procExeDeleted if already set
| * Workaround for Rosetta 2 on Darwin (thanks to Alexander Momchilov)
| * Fix FreeBSD cmdline memory leak in Process_updateCmdline, and
| * Plug a Disk I/O meter memory leak on FreeBSD (thanks to Ximalas)
| 
| What's new in version 3.1.0
| 
| * Updated COPYING file to remove the PLPA exemption (appendix 2)
|   With this change the license is now GPLv2 without any additional wording.
| * Improved default sort ordering
|   Note for users: This may lead to an inverted sort order on startup of
|   htop 3.1.0 compared to previous versions.
|   This is due to what is stored in your htoprc file. Solution: Press I
|   (to invert sort order).
|   This changed setting will be saved by htop on exit as long as it can
|   write to your htoprc file.
| * The compile-time option to cater specifically for running htop as
|   setuid has been removed
| * Add read-only option
|   This allows htop to be run in an non-intrusive fashion where it acts only
|   as a process viewer disabling all functions to manipulate system state.
|   Note: This is not a security feature!
| * Move the code for handling the command line formatting related tasks
|   to be shared across all platforms
|   This means important features like stale binary/library highlighting
|   can now be available on all supported platforms.
| * Make the EXE and COMM columns available on all platforms
|   All supported platforms have the name of the executable (EXE) and a
|   self-chosen thread/command name (COMM) available one way or the other.
|   Moving this column to be handled as a platform-independently available
|   information simplifies the markup of the command line.
| * Introduce configuration file versioning and config_reader_min_version
|   Starting with this version the configuration file contains a version
|   identifying the minimum version of the configuration parser needed to
|   fully understand the configuration file format.
|   Old configuration file formats are automatically upgraded when
|   saving the config file (htoprc).
| * Make the configuration parser friendlier to users (thanks to Bart Bakker)
|   With this change only settings that cannot be parsed properly are
|   reset to their defaults.
| * Improve default display for systems with many CPUs
| * Add the process ELAPSED time column
| * Improve the process STATE column sorting
| * Reworked handling resize and redrawing of the UI
| * Fixed an issue where the LED meter mode could overflow allotted space
| * Allow text mode Meters to span empty neighbors to the right
| * Rescale graph meters when value of total changes
|   (thanks to Michael Schönitzer)
| * Update generic process field display
|   Usually "uninteresting" values in columns like 1 thread, nice value
|   of 0, CPU and memory of 0%, idle/sleeping state, etc. are shown with
|   reduced intensity (dark grey)
| * Option and key ("*") to collapse / expand all branches under PID 1
|   (and PID 2 if kernel threads are shown) (thanks to Krishna Chaitanya)
| * Keep following a process when inverting the sort order, displaying
|   the help screen or hiding/unhiding userland threads.
|   If a thread is currently selected the selection is updated to point
|   to the thread's parent process. (thanks to Gonzalo, et.al.)
| * Reorder process scanning to be performed before updating the display
|   of the meters in the