Bug#1057765: atril: Blured in fullscreen mode if I have used GDK_DPI_SCALE & GDK_SCALE

[張效維]

Edited: Press F5, not F11.

From ZXW 

Bug#1057765: atril: Blured in fullscreen mode if I have used GDK_DPI_SCALE & GDK_SCALE

[Zhang Xiaowei]

Package: atril
Version: 1.26.0-2+b1
Severity: normal

   * What led up to the situation?

If I
$ GDK_DPI_SCALE=0.8 GDK_SCALE=2 atril xxx.pdf

And press F11 to enter fullscreen mode. It's blured.

   * What exactly did you do (or not do) that was effective (or
 ineffective)?

$ GDK_DPI_SCALE=0.8 GDK_SCALE=2 atril xxx.pdf

Press F11 to enter fullscreen.

   * What was the outcome of this action?

It's blured.

   * What outcome did you expect instead?

$ GDK_DPI_SCALE=1 GDK_SCALE=1 atril xxx.pdf

It's clear.


-- System Information:
Debian Release: trixie/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.5.13 (SMP w/8 CPU threads)
Kernel taint flags: TAINT_USER
Locale: LANG=zh_TW.UTF-8, LC_CTYPE=zh_TW.UTF-8 (charmap=UTF-8), 
LANGUAGE=zh_TW:zh
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages atril depends on:
ii  atril-common 1.26.0-2
ii  dconf-gsettings-backend [gsettings-backend]  0.40.0-4
hi  libatk1.0-0  2.50.0-1
ii  libatrildocument31.26.0-2+b1
ii  libatrilview31.26.0-2+b1
hi  libc62.37-12
ii  libcaja-extension1   1.26.1-1
hi  libgdk-pixbuf-2.0-0  2.42.10+dfsg-3
hi  libglib2.0-0 2.78.1-4
hi  libgtk-3-0   3.24.38-6
ii  libice6  2:1.0.10-1
ii  libsecret-1-00.21.1-1
ii  libsm6   2:1.2.3-1
ii  libxml2  2.9.14+dfsg-1.3+b1
ii  shared-mime-info 2.4-1

Versions of packages atril recommends:
hi  dbus-user-session [default-dbus-session-bus]  1.14.10-3
hi  dbus-x11 [dbus-session-bus]   1.14.10-3
ii  gvfs  1.52.1-1

Versions of packages atril suggests:
ii  caja  1.26.1-1
ii  poppler-data  0.4.12-1
ii  unrar 1:7.0.4-1

-- no debconf information

Bug#1047612: Pending upload: macs: Fails to build source after successful build

[Andreas Tille]

Control: tags -1 pending

Due to some unrelated bugs (mainly #1055692 macs ftbfs with Python 3.12)
this package can't be uploaded currently but the issue is fixed in Git.

Kind regards
 Andreas.

-- 
http://fam-tille.de

Bug#1032358: Pending upload: btllib: Depends on libsdsl-dev, breaking installability when not needed

[Andreas Tille]

Control: tags -1 pending

Hi Steve,

sorry for not responding for this simple bug for so long.  Thanks to the
Debian Med Advent bug squashing party I spotted it and applied your
patch in Git.  I'd like to wait for some package in new which enables
uploading the new version of the package before uploading thus it is
marked pending.

Kind regards and thanks for your patience
  Andreas.

-- 
http://fam-tille.de

Bug#1057686: groovy: The package fails to build from source due to the missing file

[tony mancill]

On Thu, Dec 07, 2023 at 05:34:01PM +1300, Vladimir Petko wrote:
> Source: groovy
> Version: 2.4.21-8
> Severity: important
> Tags: ftbfs
> 
> Dear Maintainer,
> 
> The package fails to build from source due to the missing AntBuilder path:

Hi Vladimir,

I was seeing a slightly different (but reproducible) build failure with
Java 21 related to javadoc generation that was occurring just after the
AntBuilder check in this bug report.

I added a patch and the package is building successfully on both Java 17
and 21 for me now, so I went ahead and marked this bug is closed.  If
this was a distinct issue and you're still seeing FTBFS, please let me
know and I will reopen the bug.

Thank you,
tony

Bug#1057764: RFP: golang-github-go-webauthn-webauthn -- Webauthn/FIDO2 library in golang

[Maytham Alsudany]

Package: wnpp
Severity: wishlist
X-Debbugs-Cc: debian...@lists.debian.org

* Package name: golang-github-go-webauthn-webauthn
  Version : 0.9.4
  Upstream Contact: https://github.com/go-webauthn/webauthn/issues
* URL : https://github.com/go-webauthn/webauthn
* License : BSD-3-clause
  Programming Lang: Go
  Description : Webauthn/FIDO2 library in golang

 This library is meant to handle Web Authentication for Go apps that wish
 to implement a passwordless solution for users. This library conforms as
 much as possible to the guidelines and implementation procedures
 outlined by the document. Fork
 .
 This library is a hard fork of github.com/duo-labs/webauthn and is the
 natural successor to that library.

This package is a dependency of miniflux, and
golang-github-canonical-candid may switch to it in the future,
seeing this is the "natural successor" to
golang-github-duo-labs-webauthn.

I may pursue packaging this later on, but at the moment I don't have the
time to tackle the complexity of its dependency tree.

Kind regards,
Maytham

Bug#1057763: qt5-style-kvantum: add Qt 6 build

[James Lu]

Source: qt5-style-kvantum
Version: 1.0.10-1
Severity: wishlist
Tags: patch

Dear maintainers,

As apps inside Debian migrate from Qt 5 to Qt 6, I noticed that my theme 
configuration stopped working due to missing theme engines on Qt 6.


Kvantum already supports Qt 6, though it's currently a compile time 
option (ENABLE_QT5) that enables one or the other. I've created a merge 
request[1] that adapts the package to run two separate package builds, 
one against Qt 5, and another against Qt 6. As far as I can tell, the 
Arch package[2] uses a similar approach.


I've built and tested the package locally, and it seems to work - tested 
against audacious and wireshark in unstable with the materia-kde theme. 
Changing the active theme in Kvantum Manager updates both Qt 5 and 6 
simultaneously, so it's more or less transparent.


[1]: https://salsa.debian.org/lxqt-team/qt5-style-kvantum/-/merge_requests/7
[2]: 
https://gitlab.archlinux.org/archlinux/packaging/packages/kvantum/-/blob/main/PKGBUILD#L28


Best,
James


OpenPGP_0x2EC3F60DE71C0B9D.asc
Description: OpenPGP public key


OpenPGP_signature.asc
Description: OpenPGP digital signature

Bug#908204: git-buildpackage: cannot use gbp push without tagging a release

[Carlos Henrique Lima Melara]

Hi,

I'm working with a lot of newcommers in the Debian Brasília community
and learning packaging (and a myriad of tools that come with it) is
quite overwhelming. So we try to streamline things to make packaging a
little easier. gbp is a awesome tool (thanks!) because it simplifies
working with git, but the problem comes with the combination of working
with forks+mr (remember, newcommers) and importing new upstream
releases. gpb push fails because there is no tag in the debian branch
(but we want an unreleased and untagged push to the fork so an MR can be
opened). The alternative is to teach them pushing with plain old git,
but they always forget to push the upstream/pristine-tar branches.

Also, I too work with multiple computers and with the fork+mr workflow
so being able to just gbp push would be wonderful. git push --all is not
ok because often I have a patch-queue branch that I don't want on salsa
and also upstream branches sometimes coexist.

S, it would be really nice to at least have a flag --tips or --head
in gbp to do all the work for me.

Cheers,
Charles


signature.asc
Description: PGP signature

Bug#1055622: rust-gdk-pixbuf-sys: FTBFS with nocheck build profile: cp: cannot stat '/usr/share/gir-1.0/GLib-2.0.gir': No such file or directory

[Matthias Geiger]

On Wed, 8 Nov 2023 23:07:54 + Simon McVittie  wrote:
> Source: rust-gdk-pixbuf-sys
> Version: 0.18.0-2
> Severity: important
>
> While testing a proposed update for gobject-introspection I found that
> rust-gdk-pixbuf-sys FTBFS when built in sbuild with the nocheck build
> profile:
>
> > Command: dpkg-buildpackage --sanitize-env -Pnocheck -us -uc -B 
-rfakeroot

> ...
> > debian/rules execute_before_dh_auto_build
> > make[1]: Entering directory '/<>'
> > cp /usr/share/gir-1.0/GLib-2.0.gir /<>
> > cp: cannot stat '/usr/share/gir-1.0/GLib-2.0.gir': No such file or 
directory

>
> Either libgirepository1.0-dev should not be , or that cp 
command

> needs to be skipped when built with nocheck.
>
> (Other GObject-Introspection-adjacent Rust libraries might have the same
> issue, I haven't attempted to rebuild all of them.)
>

Hi Simon,


thanks for this. This makes sense; I did in fact not set nocheck.

The build must/should fail if libgirepository1.0-dev is not present. I 
opted to regenerate all gtk-rs code in debian.


This needs the .gir file(s) to be present as that's how the regeneration 
works (and emulates upstreams' workflow in debian).


Quoting the wiki on nocheck: "No test suite should be run, and build 
dependencies used only for that purpose should be ignored".


So I don't think we can set nocheck as it is a hard dependency rather 
than a test-dependency. The source code in the package gets created by 
the rules file


where depending on the package a specific set of the .gir files **must** 
be present. I introduced this to comply with ftpmasters so we can ship 
the newer ones.


best,

--
Matthias Geiger 
Debian Maintainer
"Freiheit ist immer Freiheit des anders Denkenden" -- Rosa Luxemburg



OpenPGP_0x18BD106B3B6C5475.asc
Description: OpenPGP public key


OpenPGP_signature.asc
Description: OpenPGP digital signature

Bug#1057761: papi: add support for loongarch64

[zhangdandan]

Source: papi
Version: 7.0.1-1
Severity: wishlist
Tags: patch
User: debian-loonga...@lists.debian.org
Usertags: loong64

Dear maintainers,

Compiling the papi failed for loong64 in the Debian Package 
Auto-Building environment.
The full compilation log can be found at 
https://buildd.debian.org/status/logs.php?pkg=papi=7.0.1-1=loong64


Please consider the patch I have attached.
And the papi source package was compiled successfully on my local 
loong64 rootfs environment.

If you have any questions, you can contact me at any time.

thanks,
Dandan Zhang

Description: Add support for loongarch64 
Author: Dandan Zhang  
Last-Update: 2023-12-06

--- papi-7.0.1.orig/src/linux-context.h
+++ papi-7.0.1/src/linux-context.h
@@ -35,6 +35,8 @@ typedef ucontext_t hwd_ucontext_t;
 #define OVERFLOW_ADDRESS(ctx) ctx.ucontext->uc_mcontext.arm_pc
 #elif defined(__aarch64__)
 #define OVERFLOW_ADDRESS(ctx) ctx.ucontext->uc_mcontext.pc
+#elif defined(__loongarch64)
+#define OVERFLOW_ADDRESS(ctx) ctx.ucontext->uc_mcontext.__pc
 #elif defined(__mips__)
 #define OVERFLOW_ADDRESS(ctx) ctx.ucontext->uc_mcontext.pc
 #elif defined(__hppa__)
--- papi-7.0.1.orig/src/linux-timer.c
+++ papi-7.0.1/src/linux-timer.c
@@ -246,6 +246,22 @@ get_cycles( void )
 }
 
 //
+/* loongarch64 get_cycles() */
+//
+
+#elif defined(__loongarch64)
+static inline long long
+get_cycles( void )
+{
+	int rid = 0;
+	unsigned long ret;
+
+	__asm__ __volatile__ ( "rdtime.d %0, %1" : "=r" (ret), "=r" (rid) );
+
+	return ret;
+}
+
+//
 /* POWER get_cycles()   */
 //
 
--- papi-7.0.1.orig/src/mb.h
+++ papi-7.0.1/src/mb.h
@@ -39,6 +39,9 @@
 #elif defined(__aarch64__)
 #define rmb()   asm volatile("dmb ld" ::: "memory")
 
+#elif defined(__loongarch64)
+#define rmb()   __asm__ __volatile__("dbar 0" : : : "memory") 
+
 #elif defined(__mips__)
 #define rmb()   asm volatile(   \
 ".set   mips2\n\t"  \

Bug#1057760: settle - upcoming rust-rusqlite update.

[Peter Green]

Package: settle
Version: 0.40.1-1

I intend to update rust-rusqlite in unstable to 0.29 soon.
The cargo dependencies for settle already allow 0.29 but
the Debian dependencies will need updating.

I don't expect any issues as 0.29 is what upstream asks
for and I already tested this a while ago but I'm filing
this bug report to give you a heads up if you want to
do any further testing.

Bug#1057759: libdbd-oracle-perl: Package cannot be installed

[a . kozhemyakin]

Package: libdbd-oracle-perl
Severity: important

Dear Maintainer,


When installing the package:
apt-get install libdbd-oracle-perl
...
The following packages have unmet dependencies:
  libdbd-oracle-perl : Depends: oracle-instantclient-basic but it is not 
installable or
oracle-instantclient-basiclite but it is 
not installable

E: Unable to correct problems, you have held broken packages.

package oracle-instantclient-basic installed via alien
dpkg-query -l | grep oracle
ii oracle-instantclient12.1-basic 12.1.0.2.0-2 amd64 Oracle Instant 
Client Basic package


On previous versions of debian, installation succeeds

I resolved the situation by correcting the package name in the INFO 
file,
oracle-instantclient12.1-basic replaced oracle-instantclient-basic, 
after which libdbd-oracle-perl was able to install



-- System Information:
Debian Release: 12.2
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 
'stable')

Architecture: amd64 (x86_64)

Kernel: Linux 6.1.0-13-amd64 (SMP w/8 CPU threads; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE 
not set

Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages libdbd-oracle-perl depends on:
ii  libaio1  
0.3.113-4
ii  libc6
2.36-9+deb12u3

pn  libdbi-perl  
pn  oracle-instantclient-basic | oracle-instantclient-basiclite  
ii  perl 
5.36.0-7
ii  perl-base [perlapi-5.36.0]   
5.36.0-7

pn  perl-dbdabi-94   

libdbd-oracle-perl recommends no packages.

Versions of packages libdbd-oracle-perl suggests:
pn  perl-tk  

Bug#1057707: [Pkg-javascript-devel] Bug#1057707: eslint is incompatible with node-ajv >= 8

[Yadd]

On 12/8/23 03:59, Jonas Smedegaard wrote:

Quoting Yadd (2023-12-07 14:37:31)

Control: tags -1 + patch

On 12/7/23 15:52, Jérémy Lal wrote:



Le jeu. 7 déc. 2023 à 12:45, Yadd mailto:y...@debian.org>> a écrit :

 Package: eslint
 Version: 6.4.0~dfsg+~6.1.9-7
 Severity: important
 Tags: ftbfs upstream

 Hi,

 eslint depends on node-ajv 6 and is incompatible with node-ajv 8
 (available in exeprimental branch). All is in lib/shared/ajv.js:

   - eslint requires 'ajv/lib/refs/json-schema-draft-04.json' which is no
     more available
   - eslint tries to set `ajv._opts.defaultMeta` which is
     `ajv.opts.defaultMeta` in node-ajv 8.

 Changing "ajv/lib/refs/json-schema-draft-04.json" to
 "ajv/lib/refs/json-schema-draft-06.json" doesn't work. I tried this
 patch which looks to work but 27 tests fail (not the good error string).
 It uses default ajv schemas.

 Help needed here ;-)


I suppose you tried
https://github.com/eslint/eslint/pull/13911/commits

?


Thanks a lot Jérémy! Based on your suggestion, I succeed to build a patch.

@Jonas, do you agree if I push this to experimental ?


If it succeeds the testsuite then by all means, go for it.


Hi,

sure, all test passed now. Only error strings had to be updated

Cheers,
Yadd

Bug#1057758: kmail: Plain text emails truncated at 60 lines if HTML section is included

[Soren Stoutner]

Package: kmail
Version: 4:22.12.3-1
Severity: normal
Tags: upstream

Control: forwarded -1 https://bugs.kde.org/show_bug.cgi?id=477443

When composing an email in both plain text and HTML, the plain text is 
truncated at 60 lines when the email is sent.  The HTML contains the entire 
message.

Bug#1057757: qbs: FTBFS on loong64 for dh_makeshlibs

[JiaLing Zhang]

Package: qbs
Version: 2.1.2-1
Severity: normal
Tags: FTBFS loong64
X-Debbugs-Cc: zhangjial...@loongson.cn

Dear Maintainer,

  Hi, I found qbs build failed on loong64 for symbols file less loong64 arch, 
Please looks 
https://buildd.debian.org/status/fetch.php?pkg=qbs=loong64=2.1.2-1=1697186185=0

Thanks,
JiaLing

Bug#1057756: git-filter-repo: the package fails to build from source due to git help changes

[Vladimir Petko]

Dear Maintainers,

  Would it be possible to consider a merge request[1] that addresses this
issue?

Best Regards,
 Vladimir.

 [1]
https://salsa.debian.org/python-team/packages/git-filter-repo/-/merge_requests/1

Bug#1057756: git-filter-repo: the package fails to build from source due to git help changes

[Vladimir Petko]

Package: git-filter-repo
Version: 2.38.0-1
Severity: important
Tags: ftbfs

Dear Maintainer,

The package fails to build from source in sid chroot due to the help strings
changes in git 2.43

The relevant parts of the build log
---
make[1]: Entering directory '/<>'
t/run_tests


== t9390-filter-repo.sh ==
ok 1 - check: basic -> basic-filename using '--path filename'
ok 2 - check: basic -> basic-twenty using '--path twenty'
ok 3 - check: basic -> basic-ten using '--path ten'
ok 4 - check: basic -> basic-numbers using '--path ten --path twenty'
ok 5 - check: basic -> basic-filename using '--invert-paths --path-glob t*en*'
ok 6 - check: basic -> basic-numbers using '--invert-paths --path-regex
f.*e.*e'
ok 7 - check: basic -> basic-mailmap using '--mailmap ../t9390/sample-mailmap'
ok 8 - check: basic -> basic-replace using '--replace-text ../t9390/sample-
replace'
ok 9 - check: basic -> basic-message using '--replace-message ../t9390/sample-
message'
ok 10 - check: empty -> empty-keepme using '--path keepme'
ok 11 - check: empty -> more-empty-keepme using '--path keepme --prune-
empty=always --prune-degenerate=always'
ok 12 - check: empty -> less-empty-keepme using '--path keepme --prune-
empty=never --prune-degenerate=never'
ok 13 - check: degenerate -> degenerate-keepme using '--path moduleA/keepme'
ok 14 - check: degenerate -> degenerate-moduleA using '--path moduleA'
ok 15 - check: degenerate -> degenerate-globme using '--path-glob *me'
ok 16 - check: degenerate -> degenerate-keepme-noff using '--path
moduleA/keepme --no-ff'
ok 17 - check: unusual -> unusual-filtered using '--path '
ok 18 - check: unusual -> unusual-mailmap using '--mailmap ../t9390/sample-
mailmap'
ok 19 - --path-rename sequences/tiny:sequences/small
ok 20 - --path-rename sequences:numbers
ok 21 - --path-rename-prefix values:numbers
ok 22 - --path-rename squashing
ok 23 - --path-rename inability to squash
ok 24 - --paths-from-file
ok 25 - Mixing filtering and renaming paths, not enough filters
ok 26 - Mixing filtering and renaming paths, enough filters
ok 27 - Mixing filtering and to-subdirectory-filter
ok 28 - --tag-rename
not ok 29 - tag of tag before relevant portion of history
#
#   test_create_repo filtered_tag_of_tag &&
#   (
#   cd filtered_tag_of_tag &&
#   echo contents >file &&
#   git add file &&
#   git commit -m "Initial" &&
#
#   git tag -a -m "Inner Tag" inner_tag HEAD &&
#   git tag -a -m "Outer Tag" outer_tag inner_tag &&
#
#   mkdir subdir &&
#   echo stuff >subdir/whatever &&
#   git add subdir &&
#   git commit -m "Add file in subdir" &&
#
#   git filter-repo --force --subdirectory-filter subdir &&
#
#   git show-ref >refs &&
#   ! grep refs/tags refs &&
#   git log --all --oneline >commits &&
#   test_line_count = 1 commits
#   )
#
ok 30 - --subdirectory-filter
ok 31 - --subdirectory-filter with trailing slash
ok 32 - --to-subdirectory-filter
ok 33 - --use-base-name
ok 34 - refs/replace/ to skip a parent
ok 35 - refs/replace/ to add more initial history
ok 36 - creation/deletion/updating of replace refs
ok 37 - --debug
ok 38 - --dry-run
ok 39 - --dry-run --debug
ok 40 - --dry-run --stdin
ok 41 - --analyze
ok 42 - --analyze --report-dir
ok 43 - --replace-text all options
ok 44 - --replace-text binary zero_byte-0_char
ok 45 - --replace-text binary zero_byte-no_0_char
ok 46 - --replace-text text-file no_zero_byte-zero_char
ok 47 - --strip-blobs-bigger-than
ok 48 - --strip-blobs-with-ids
ok 49 - commit message rewrite
ok 50 - commit hash unchanged if requested
not ok 51 - commit message encoding preserved if requested
#
#   (
#   git init commit_message_encoding &&
#   cd commit_message_encoding &&
#
#   cat >input <<-\EOF &&
#   feature done
#   commit refs/heads/develop
#   mark :1
#   original-oid deadbeefdeadbeefdeadbeefdeadbeefdeadbeef
#   author Just Me  1234567890 -0200
#   committer Just Me  1234567890 -0200
#   encoding iso-8859-7
#   data 5
#   EOF
#
#   printf "Pi: \360\n\ndone\n" >>input &&
#
#   cat input | git fast-import --quiet &&
#   git rev-parse develop >expect &&
#
#   git filter-repo --preserve-commit-encoding --force &&
#   git rev-parse develop >actual &&
#   test_cmp expect actual
#   )
#
ok 52 - commit message rewrite unsuccessful
ok 53 - startup sanity checks
ok 54 - other 

Bug#1057179: Acknowledgement (bookworm-pu: package mariadb-10.6 1:10.11.6-0+deb12u1)

[Otto Kekäläinen]

Uploading 10.11.6 to Bookworm should be done today but since autopkgtests
(mostly misc unrelated fails in LibreOffice) have been blocking the
migration from unstable to testing for past 10 days, uploading latest to
Bookworm would lead to a situation where Trixie has and older version
(10.11.5) than Bookworm (10.11.6).

I will assess the impact and consider proceeding despite this as it is
likely to get resolved by itself give more time for autopkgtests to re-run.

Bug#1057755: qt6-webengine: Support security updates in stable

[Soren Stoutner]

Source: qt6-webengine
Version: 6.4.2-final+dfsg-12
Severity: normal

Currently security patches to Qt WebEngine are not uploaded to Debian stable.
The purpose of this bug report is to track efforts to change that.

Bug#1057754: rust-typed-builder: please upgrade to v0.18

[Jonas Smedegaard]

Source: rust-typed-builder
Version: 0.14.0-1
Severity: normal
Tags: upstream

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Please upgrade to, or separately provide, branch v0.18.
-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmVyYZ4ACgkQLHwxRsGg
ASFsJRAAjUs4JiPEojR578mNAPiYhMzelmaJ2jAE3qxdt4zOC2RFg5ZU4CDNG82j
aJf0+GKSWJHP6/1f94l55NwMNiyorVI4I8zsVYRKDRm+/nesl2FaV3Sz95bDvzaA
twxzPsorGmCGuleThkku9B/XRzeG+tYsRCvxBC65mpUC/fKl6+BLLjbSFh8erHGp
WsMXKHf7ozp4cb6FYhOJQD/TXHrHVw/EzAh2F2ET3PkygpWsyJFCfdrzpEX7fbYk
aTbFRAl4meYWhVN+xLPR2lJ8U7DnvOlhC5scLsQTk+NIoPyDlMOG0ptZeDNJVlxh
GQ4u53PBIs15M0iObMTM5d3Qx0mU5f4VRrZGZ91C1aVK80KwZah3CEuw0M0c1WL9
Q1F55eREjzVa+2VIJ4z7xz4uFidZVli0KbiVm0tf/xCl7gF+Mh7/9K/9Z9ot4a6/
37cdjFQNBavPi5aBmRdtq+xVuCzStsm/CS4PIIpWuoRgG9d2FhF06+SBoBikCmEJ
tCNNjd5X/MDg2kP0656eQJPaTTlWCq8sbwE7D5mnvF4kd9Oit2AfXbm750plornr
83v7ex58eRkSX1n2RLLnQw1tlcWMw7odNlFUU4V5XUCkdv3TnWsuZkLGi0aTx7g7
Q2Tfx1c9kTvOA0bYA0/UrLm2Zm2aAdq26xxr6bC/8GW38JhsM4Q=
=hHYE
-END PGP SIGNATURE-

Bug#874030: Anyenv

[陳昌倬]

On Thu, Dec 07, 2023 at 12:59:06AM +0100, Mikko Johannes Koivunalho wrote:
> Has there been any interest? I am a permanent Anyenv user and contributor
> and I'd very much like to see it packaged for Debian.
> 
> I'm also willing to help, if needed, but I know very little about Debian
> packaging.

Sorry, I don't have time for this. If you are interested in packaing, I
can help to sponsor.

-- 
ChangZhuo Chen (陳昌倬) czchen@{czchen,debian}.org
Key fingerprint = BA04 346D C2E1 FE63 C790  8793 CC65 B0CD EC27 5D5B


signature.asc
Description: PGP signature

Bug#1057707: [Pkg-javascript-devel] Bug#1057707: eslint is incompatible with node-ajv >= 8

[Jonas Smedegaard]

Quoting Yadd (2023-12-07 14:37:31)
> Control: tags -1 + patch
> 
> On 12/7/23 15:52, Jérémy Lal wrote:
> > 
> > 
> > Le jeu. 7 déc. 2023 à 12:45, Yadd  > > a écrit :
> > 
> > Package: eslint
> > Version: 6.4.0~dfsg+~6.1.9-7
> > Severity: important
> > Tags: ftbfs upstream
> > 
> > Hi,
> > 
> > eslint depends on node-ajv 6 and is incompatible with node-ajv 8
> > (available in exeprimental branch). All is in lib/shared/ajv.js:
> > 
> >   - eslint requires 'ajv/lib/refs/json-schema-draft-04.json' which is no
> >     more available
> >   - eslint tries to set `ajv._opts.defaultMeta` which is
> >     `ajv.opts.defaultMeta` in node-ajv 8.
> > 
> > Changing "ajv/lib/refs/json-schema-draft-04.json" to
> > "ajv/lib/refs/json-schema-draft-06.json" doesn't work. I tried this
> > patch which looks to work but 27 tests fail (not the good error string).
> > It uses default ajv schemas.
> > 
> > Help needed here ;-)
> > 
> > 
> > I suppose you tried
> > https://github.com/eslint/eslint/pull/13911/commits 
> > 
> > ?
> 
> Thanks a lot Jérémy! Based on your suggestion, I succeed to build a patch.
> 
> @Jonas, do you agree if I push this to experimental ?

If it succeeds the testsuite then by all means, go for it.

But if not, then instead please let's look in more detail at the
options, to avoid complicating matters for this delicate beast.

 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/
 * Sponsorship: https://ko-fi.com/drjones

 [x] quote me freely  [ ] ask before reusing  [ ] keep private

signature.asc
Description: signature

Bug#1057753: gfs2-utils: delegate placement of udev files to pkg-config data

[Chris Hofstaedtler]

Source: gfs2-utils
Version: 3.5.1-1
Severity: normal
Tags: patch
User: helm...@debian.org
Usertags: dep17m2

Dear Maintainer,

your package installs files related to udev, into /lib. These
files need to be moved to /usr/lib as part of Debian's usr-merge
effort [1].

Attached you will find a patch to delegate the exact placement of
the udev files to udev.pc (using pkg-config). This should work today
in unstable and, if necessary, for bookworm. Once udev.pc in
unstable points to /usr/lib your package will benefit automatically
after a binNMU or any other upload.

Later during the trixie cycle I expect this bug class to raise in
priority.

Per the wiki, it is advisable to upload to experimental first, and
wait a few days for the dumat tool to check your package. The same
is advisable when any structural changes are done in the trixie
cycle.

Thank you for considering,
Chris

[1] https://wiki.debian.org/UsrMerge
diff -Nru gfs2-utils-3.5.1/debian/changelog gfs2-utils-3.5.1/debian/changelog
--- gfs2-utils-3.5.1/debian/changelog	2023-06-22 23:37:36.0 +0200
+++ gfs2-utils-3.5.1/debian/changelog	2023-12-08 00:56:31.0 +0100
@@ -1,3 +1,10 @@
+gfs2-utils (3.5.1-1.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Delegate placement of udev files to pkg-config data
+
+ -- Chris Hofstaedtler   Fri, 08 Dec 2023 00:56:31 +0100
+
 gfs2-utils (3.5.1-1) unstable; urgency=medium
 
   * New upstream version 3.5.1
diff -Nru gfs2-utils-3.5.1/debian/control gfs2-utils-3.5.1/debian/control
--- gfs2-utils-3.5.1/debian/control	2023-02-11 15:04:22.0 +0100
+++ gfs2-utils-3.5.1/debian/control	2023-12-08 00:55:40.0 +0100
@@ -16,6 +16,7 @@
  libncurses-dev,
  libtool,
  pkg-config,
+ systemd-dev,
  zlib1g-dev
 Standards-Version: 4.6.2
 Rules-Requires-Root: no
diff -Nru gfs2-utils-3.5.1/debian/rules gfs2-utils-3.5.1/debian/rules
--- gfs2-utils-3.5.1/debian/rules	2022-11-20 14:28:09.0 +0100
+++ gfs2-utils-3.5.1/debian/rules	2023-12-08 00:56:16.0 +0100
@@ -1,5 +1,7 @@
 #!/usr/bin/make -f
 
+udevdir = $(shell pkg-config --variable=udevdir udev)
+
 # build fails when format hardening is on
 export DEB_BUILD_MAINT_OPTIONS=hardening=+all
 
@@ -12,8 +14,8 @@
 		bzip2_CFLAGS=' ' \
 		bzip2_LIBS=-lbz2 \
 		bzip2_VERSION=' ' \
-		--libexecdir=/lib/udev \
-		--with-udevdir=/lib/udev
+		--libexecdir=$(udevdir) \
+		--with-udevdir=$(udevdir)
 
 override_dh_auto_install:
 	dh_auto_install

Bug#1057752: fpga-icestorm: delegate placement of udev files to pkg-config data

[Chris Hofstaedtler]

Source: fpga-icestorm
Version: 0~20230218gitd20a5e9-1
Severity: normal
Tags: patch
User: helm...@debian.org
Usertags: dep17m2

Dear Maintainer,

your package installs files related to udev, into /lib. These
files need to be moved to /usr/lib as part of Debian's usr-merge
effort [1].

Attached you will find a patch to delegate the exact placement of
the udev files to udev.pc (using pkg-config). This should work today
in unstable and, if necessary, for bookworm. Once udev.pc in
unstable points to /usr/lib your package will benefit automatically
after a binNMU or any other upload.

Later during the trixie cycle I expect this bug class to raise in
priority.

Per the wiki, it is advisable to upload to experimental first, and
wait a few days for the dumat tool to check your package. The same
is advisable when any structural changes are done in the trixie
cycle.

Thank you for considering,
Chris

[1] https://wiki.debian.org/UsrMerge
diff -Nru fpga-icestorm-0~20230218gitd20a5e9/debian/changelog fpga-icestorm-0~20230218gitd20a5e9/debian/changelog
--- fpga-icestorm-0~20230218gitd20a5e9/debian/changelog	2023-06-13 14:52:48.0 +0200
+++ fpga-icestorm-0~20230218gitd20a5e9/debian/changelog	2023-12-08 00:39:06.0 +0100
@@ -1,3 +1,11 @@
+fpga-icestorm (0~20230218gitd20a5e9-1.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Delegate placement of udev files to pkg-config data (Closes: #-1)
+  * Use debhelper compat 13 for substitutions in .install files
+
+ -- Chris Hofstaedtler   Fri, 08 Dec 2023 00:39:06 +0100
+
 fpga-icestorm (0~20230218gitd20a5e9-1) unstable; urgency=medium
 
   * New upstream version 0~20230218gitd20a5e9
diff -Nru fpga-icestorm-0~20230218gitd20a5e9/debian/control fpga-icestorm-0~20230218gitd20a5e9/debian/control
--- fpga-icestorm-0~20230218gitd20a5e9/debian/control	2023-05-17 21:08:04.0 +0200
+++ fpga-icestorm-0~20230218gitd20a5e9/debian/control	2023-12-08 00:39:06.0 +0100
@@ -4,11 +4,12 @@
Daniel Gröber 
 Section: electronics
 Priority: optional
-Build-Depends: debhelper-compat (= 12),
+Build-Depends: debhelper-compat (= 13),
libftdi-dev,
python3,
txt2man,
-   pkg-config
+   pkg-config,
+   systemd-dev
 Standards-Version: 4.6.0
 Vcs-Browser: https://salsa.debian.org/electronics-team/fpga-icestorm
 Vcs-Git: https://salsa.debian.org/electronics-team/fpga-icestorm.git
diff -Nru fpga-icestorm-0~20230218gitd20a5e9/debian/fpga-icestorm.install fpga-icestorm-0~20230218gitd20a5e9/debian/fpga-icestorm.install
--- fpga-icestorm-0~20230218gitd20a5e9/debian/fpga-icestorm.install	2023-05-17 21:08:17.0 +0200
+++ fpga-icestorm-0~20230218gitd20a5e9/debian/fpga-icestorm.install	2023-12-08 00:39:06.0 +0100
@@ -5,5 +5,5 @@
 docs/*.svg usr/share/doc/fpga-icestorm/html
 docs/*.html usr/share/doc/fpga-icestorm/html
 docs/*.png usr/share/doc/fpga-icestorm/html
-debian/40-fpga-icestorm.rules lib/udev/rules.d
+debian/40-fpga-icestorm.rules ${env:deb_udevdir}/rules.d/
 debian/at.clifford.icestorm.metainfo.xml usr/share/metainfo
diff -Nru fpga-icestorm-0~20230218gitd20a5e9/debian/rules fpga-icestorm-0~20230218gitd20a5e9/debian/rules
--- fpga-icestorm-0~20230218gitd20a5e9/debian/rules	2023-05-17 21:08:17.0 +0200
+++ fpga-icestorm-0~20230218gitd20a5e9/debian/rules	2023-12-08 00:39:06.0 +0100
@@ -11,6 +11,8 @@
 
 export CHIPDB_SUBDIR=fpga-icestorm/chipdb
 
+export deb_udevdir = $(shell pkg-config --variable=udevdir udev | sed s,^/,,)
+
 %:
 	dh $@
 

Bug#1057750: ciso: Please update to ciso 1.0.2

[Aaron Rainbolt]

Debdiff prepared and attached. Please review this whenever you get a 
chance and tell me if there's anything I can do better. Thanks!


--
Aaron Rainbolt
Lubuntu Developer
Matrix: @arraybolt3:matrix.org
IRC: arraybolt3 on irc.libera.chat
GitHub: https://github.com/ArrayBolt3
diff -Nru ciso-1.0.0/README.markdown ciso-1.0.2/README.markdown
--- ciso-1.0.0/README.markdown	1970-01-01 00:00:00.0 +
+++ ciso-1.0.2/README.markdown	2015-07-07 18:05:38.0 +
@@ -0,0 +1,24 @@
+ciso is a simple commandline utility to compress PSP iso files.
+
+This package is an OSX port of a package provided by Ubuntu: http://packages.ubuntu.com/search?keywords=ciso
+
+# Installation
+
+Now available via homebrew:
+
+brew install ciso
+
+To build yourself, it's a very straightforward `make` (and optional `make install`).
+
+# Usage
+
+To decompress a cso file:
+
+ciso 0 infile.cso outfile.iso
+
+To compress an iso file:
+
+ciso level infile.iso outfile.cso
+
+where level ranges from 1 (fast, poor compression) to 9 (slow, high
+compression).
diff -Nru ciso-1.0.0/ciso.c ciso-1.0.2/ciso.c
--- ciso-1.0.0/ciso.c	2006-11-03 20:53:29.0 +
+++ ciso-1.0.2/ciso.c	2015-07-07 18:05:38.0 +
@@ -22,6 +22,7 @@
 
 #include 
 #include 
+#include 
 #include/* /usr(/local)/include/zlib.h */
 #include 
 
@@ -31,10 +32,10 @@
 FILE *fin,*fout;
 z_stream z;
 
-unsigned int *index_buf = NULL;
-unsigned int *crc_buf = NULL;
-unsigned char *block_buf1 = NULL;
-unsigned char *block_buf2 = NULL;
+uint32_t *index_buf = NULL;
+uint32_t *crc_buf = NULL;
+uint8_t *block_buf1 = NULL;
+uint8_t *block_buf2 = NULL;
 
 /
 	compress ISO to CSO
@@ -43,9 +44,9 @@
 CISO_H ciso;
 int ciso_total_block;
 
-unsigned long long check_file_size(FILE *fp)
+uint64_t check_file_size(FILE *fp)
 {
-	unsigned long long pos;
+	uint64_t pos;
 
 	if( fseek(fp,0,SEEK_END) < 0)
 		return -1;
@@ -80,9 +81,9 @@
 /
 int decomp_ciso(void)
 {
-	unsigned long long file_size;
-	unsigned int index , index2;
-	unsigned long long read_pos , read_size;
+	uint64_t file_size;
+	uint32_t index , index2;
+	uint64_t read_pos , read_size;
 	int total_sectors;
 	int index_size;
 	int block;
@@ -117,7 +118,7 @@
 	ciso_total_block = ciso.total_bytes / ciso.block_size;
 
 	/* allocate index block */
-	index_size = (ciso_total_block + 1 ) * sizeof(unsigned long);
+	index_size = (ciso_total_block + 1 ) * sizeof(uint32_t);
 	index_buf  = malloc(index_size);
 	block_buf1 = malloc(ciso.block_size);
 	block_buf2 = malloc(ciso.block_size*2);
@@ -138,7 +139,7 @@
 
 	/* show info */
 	printf("Decompress '%s' to '%s'\n",fname_in,fname_out);
-	printf("Total File Size %ld bytes\n",ciso.total_bytes);
+	printf("Total File Size %lld bytes\n",ciso.total_bytes);
 	printf("block size  %d  bytes\n",ciso.block_size);
 	printf("total blocks%d  blocks\n",ciso_total_block);
 	printf("index align %d\n",1<
+
+#ifndef __CISO_H__
+#define __CISO_H__
+/*
+	complessed ISO(9660) header format
+*/
+typedef struct ciso_header
+{
+	uint8_t magic[4];			/* +00 : 'C','I','S','O' */
+	uint32_t header_size;		/* +04 : header size (==0x18)*/
+	uint64_t total_bytes;	/* +08 : number of original data size*/
+	uint32_t block_size;		/* +10 : number of compressed block size */
+	uint8_t ver;/* +14 : version 01  */
+	uint8_t align;			/* +15 : align of index value*/
+	uint8_t rsv_06[2];		/* +16 : reserved*/
+#if 0
+// INDEX BLOCK
+	uint32_t index[0];			/* +18 : block[0] index  */
+	uint32_t index[1];			/* +1C : block[1] index  */
+ :
+ :
+	uint32_t index[last];		/* +?? : block[last] */
+	uint32_t index[last+1];		/* +?? : end of last data point  */
+// DATA BLOCK
+	uint8_t data[];			/* +?? : compressed or plain sector data */
+#endif
+}CISO_H;
+
+/*
+note:
+
+file_pos_sector[n]  = (index[n]&0x7fff) << CISO_H.align
+file_size_sector[n] = ( (index[n+1]&0x7fff) << CISO_H.align) - file_pos_sector[n]
+
+if(index[n]&0x8000)
+  // read 0x800 without compress
+else
+  // read file_size_sector[n] bytes and decompress data
+*/
+
+#endif
 
-#ifndef __CISO_H__
-#define __CISO_H__
-/*
-	complessed ISO(9660) header format
-*/
-typedef struct ciso_header
-{
-	unsigned char magic[4];			/* +00 : 'C','I','S','O' */
-	unsigned long header_size;		/* +04 : header size (==0x18)*/
-	unsigned long long total_bytes;	/* +08 : number of original data size*/
-	unsigned long block_size;		/* +10 : number of compressed block size */
-	unsigned char ver;/* +14 : version 01  */
-	unsigned char align;			/* +15 : align of index value*/
-	unsigned char rsv_06[2];		/* +16 : reserved*/
-#if 

Bug#1057732: Acknowledgement (utfcpp: please update to 4.0.1)

[David Bremner]

In case it is not clear, later versions are fine also.

d

Bug#1057751: dlm: delegate placement of systemd/udev files to pkg-config data

[Chris Hofstaedtler]

Source: dlm
Version: 4.2.0-3
Severity: normal
Tags: patch
User: helm...@debian.org
Usertags: dep17m2

Dear Maintainer,

your package installs files related to systemd and udev, into /lib.
These files need to be moved to /usr/lib as part of Debian's
usr-merge effort [1].

Attached you will find a patch to delegate the exact placement to
systemd.pc/udev.pc (using pkg-config). This should work today in
unstable and, if necessary, for bookworm. Once udev.pc in unstable
points to /usr/lib your package will benefit automatically after a
binNMU or any other upload. systemd.pc in unstable already points to
/usr/lib.

Later during the trixie cycle I expect this bug class to raise in
priority.

Per the wiki, it is advisable to upload to experimental first, and
wait a few days for the dumat tool to check your package. The same
is advisable when any structural changes are done in the trixie
cycle.

Thank you for considering,
Chris

[1] https://wiki.debian.org/UsrMerge
diff -Nru dlm-4.2.0/debian/changelog dlm-4.2.0/debian/changelog
--- dlm-4.2.0/debian/changelog	2023-07-27 21:05:33.0 +0200
+++ dlm-4.2.0/debian/changelog	2023-12-08 00:06:33.0 +0100
@@ -1,3 +1,10 @@
+dlm (4.2.0-3.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Delegate placement of udev files to pkg-config data
+
+ -- Chris Hofstaedtler   Fri, 08 Dec 2023 00:06:33 +0100
+
 dlm (4.2.0-3) unstable; urgency=medium
 
   * [d012be6] Update Standards-Version to 4.6.2 (no changes required)
diff -Nru dlm-4.2.0/debian/control dlm-4.2.0/debian/control
--- dlm-4.2.0/debian/control	2023-07-27 21:03:02.0 +0200
+++ dlm-4.2.0/debian/control	2023-12-08 00:06:31.0 +0100
@@ -16,6 +16,7 @@
  libxml2-dev,
  pacemaker-dev,
  pkg-config,
+ systemd-dev,
  uuid-dev,
 Homepage: https://pagure.io/dlm
 Vcs-Browser: https://salsa.debian.org/ha-team/dlm
diff -Nru dlm-4.2.0/debian/dlm-controld.install dlm-4.2.0/debian/dlm-controld.install
--- dlm-4.2.0/debian/dlm-controld.install	2022-11-15 23:30:59.0 +0100
+++ dlm-4.2.0/debian/dlm-controld.install	2023-12-08 00:06:33.0 +0100
@@ -1,5 +1,5 @@
 debian/configfs.conf usr/lib/modules-load.d
-usr/lib/udev/rules.d/51-dlm.rules lib/udev/rules.d
+usr/lib/udev/rules.d/51-dlm.rules ${env:deb_udevdir}/rules.d
 usr/sbin
 usr/share/man/man5
 usr/share/man/man8
diff -Nru dlm-4.2.0/debian/rules dlm-4.2.0/debian/rules
--- dlm-4.2.0/debian/rules	2022-11-16 00:03:38.0 +0100
+++ dlm-4.2.0/debian/rules	2023-12-08 00:06:33.0 +0100
@@ -11,6 +11,9 @@
 DPKG_EXPORT_BUILDTOOLS=1
 include /usr/share/dpkg/buildtools.mk
 
+export deb_systemdsystemunitdir = $(shell pkg-config --variable=systemdsystemunitdir systemd | sed s,^/,,)
+export deb_udevdir = $(shell pkg-config --variable=udevdir udev | sed s,^/,,)
+
 %:
 	dh $@
 
@@ -18,7 +21,7 @@
 	dh_auto_install -- LIBNUM=/lib/$(DEB_HOST_MULTIARCH)
 
 DEFDIR=debian/dlm-controld/etc/default
-SDDIR= debian/dlm-controld/lib/systemd/system
+SDDIR=debian/dlm-controld/$(deb_systemdsystemunitdir)
 override_dh_install:
 	dh_install
 	mkdir -p "$(DEFDIR)" "$(SDDIR)"

Bug#1057750: ciso: Please update to ciso 1.0.2

[Aaron Rainbolt]

Package: ciso
Version: 1.0.0-1
Severity: normal
X-Debbugs-Cc: arraybo...@ubuntu.com

ciso 1.0.0 has numerous coding issues resulting in a ton of compile-time
warnings (mostly related to the fact that the author apparently forgot
to include string.h). Version 1.0.2 fixes many of these issues, and also
significantly improves code quality.

I am preparing a debdiff that updates the package, and adds some packaging
enhancements.


-- System Information:
Debian Release: trixie/sid
  APT prefers noble
  APT policy: (500, 'noble')
Architecture: amd64 (x86_64)

Kernel: Linux 6.5.0-9-generic (SMP w/8 CPU threads; PREEMPT)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages ciso depends on:
ii  libc6   2.38-3ubuntu1
ii  zlib1g  1:1.2.13.dfsg-1ubuntu5

ciso recommends no packages.

ciso suggests no packages.

Bug#1057749: spamc --headers corrupts body with NUL char in body

[Eric Wong]

Package: spamc
Version: 3.4.6-1
Severity: normal
Tags: upstream

Dear Maintainer,

I'm able to reproduce this bug on 4.0.0-8 on a sid machine, too.

My use of `spamc -E --headers' causes body corruption if a NUL
('\0') character appears in the body when talking to spamd.

The bug appears to be in the `_append_original_body' function of
spamc/libspamc.c stemming from the use of the strncpy(3) function.

I suggest using open_memstream(3) for all buffer management
needs, but I'm not sure if POSIX.1-2008 is too new for SA
upstream.  The use of strcat/strcpy/strncpy makes me seriously
uncomfortable (they're all banned from git itself and any
C codebase I work on due to safety problems).

The bug doesn't happen when spamd is unreachable and spamc falls
back to working entirely in-process.

Bug#998002: proposal to split mupdf binary package to mupdf,mupdf-gl (was Re: Bug#998002: mupdf: What is the purpose of /usr/bin/mupdf-gl?)

[Kan-Ru Chen]

Hi,

On Thu, Dec 7, 2023, at 7:48 PM, Jonathan Dowland wrote:
> Hi Davide,
>
> Thanks for the additional information.
>
> In my limited testing, mupdf-gl does not appear to function as well as
> mupdf. I can understand different people having a preference for one or
> the other.

I support that we do something to reduce the package size.
According to upstream website[1] the mupdf-gl viewer is the recommended one.
Although personally I also prefer the x11 version.

> On Tue, Nov 21, 2023 at 06:22:55PM +0100, Davide Prina wrote:
>> 2) a man page for mupdf-gl
>
> Yes, this is required by Debian policy.

Sure.

>> 1) a selection of which you want use at installing and
>>upgrading time
>
> One way of addressing this would be to have mupdf-gl be a separate
> binary package. Another argument for that would be to reduce the
> binary package size. I myself have found myself in a situation where
> I wanted to install mupdf but the binary was too large for the my
> bandwidth at the time (I was on a train, using tethered, metered
> Internet)
>
> I would like to hear from the package maintainers as to what their
> feelings are on splitting the binary package.  I am prepared to do
> some of the work.  If I don't hear from the maintainers one way or
> the other, I will prepare an NMU.

Another option is to enable building libmupdf and sharing it between
mupdf-x11 and mupdf-gl.

This will not fix #719351 because upstream still do not intend to distribute
mupdf as shared library. The libmupdf.so binary won't have soname. This is
confirmed with them.

> [ Maintainers: please consider marking yourself as supporting low
>   threshold NMUs:  ]

I support this initiative however I don't understand how this wiki is used.
Do everyone just search the wiki to find what's the NMU threshold? The comments
looks pretty arbitrary. IMO the delay queue NMU process works well, file a bug 
and
upload to delay queue so I have sometime to check. Or send a patch to salsa.d.o.

Cheers,
Kan-Ru

> Best wishes,
>
> -- 
> Jonathan Dowland

-- 
Kan-Ru Chen
Debian Developer

Bug#1057748: digimend-dkms: delegate placement of udev files to pkg-config data

[Chris Hofstaedtler]

Source: digimend-dkms
Version: 11-3
Severity: normal
Tags: patch
User: helm...@debian.org
Usertags: dep17m2

Dear Maintainer,

your package installs files related to udev, into /lib. These
files need to be moved to /usr/lib as part of Debian's usr-merge
effort [1].

Attached you will find a patch to delegate the exact placement of
the udev files to udev.pc (using pkg-config). This should work today
in unstable and, if necessary, for bookworm. Once udev.pc in
unstable points to /usr/lib your package will benefit automatically
after a binNMU or any other upload.

Later during the trixie cycle I expect this bug class to raise in
priority.

Per the wiki, it is advisable to upload to experimental first, and
wait a few days for the dumat tool to check your package. The same
is advisable when any structural changes are done in the trixie
cycle.

Thank you for considering,
Chris

[1] https://wiki.debian.org/UsrMerge
diff -Nru digimend-dkms-11/debian/changelog digimend-dkms-11/debian/changelog
--- digimend-dkms-11/debian/changelog	2023-06-16 05:52:28.0 +0200
+++ digimend-dkms-11/debian/changelog	2023-12-08 00:03:31.0 +0100
@@ -1,3 +1,10 @@
+digimend-dkms (11-3.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Delegate placement of udev files to pkg-config data
+
+ -- Chris Hofstaedtler   Fri, 08 Dec 2023 00:03:31 +0100
+
 digimend-dkms (11-3) unstable; urgency=medium
 
   * debian/control
diff -Nru digimend-dkms-11/debian/control digimend-dkms-11/debian/control
--- digimend-dkms-11/debian/control	2023-06-16 05:52:28.0 +0200
+++ digimend-dkms-11/debian/control	2023-12-08 00:01:47.0 +0100
@@ -5,6 +5,8 @@
 Build-Depends:
  debhelper-compat (= 13),
  dh-sequence-dkms,
+ pkgconf,
+ systemd-dev,
 Standards-Version: 4.6.2
 Homepage: https://github.com/DIGImend/digimend-kernel-drivers
 Vcs-Git: https://salsa.debian.org/debian/digimend-dkms.git
diff -Nru digimend-dkms-11/debian/patches/series digimend-dkms-11/debian/patches/series
--- digimend-dkms-11/debian/patches/series	2023-06-16 05:52:28.0 +0200
+++ digimend-dkms-11/debian/patches/series	2023-12-08 00:00:53.0 +0100
@@ -1,2 +1,3 @@
 skip-without-CONFIG_USB_HID.patch
 support-kernel-6.3.patch
+udev-udevdir.patch
diff -Nru digimend-dkms-11/debian/patches/udev-udevdir.patch digimend-dkms-11/debian/patches/udev-udevdir.patch
--- digimend-dkms-11/debian/patches/udev-udevdir.patch	1970-01-01 01:00:00.0 +0100
+++ digimend-dkms-11/debian/patches/udev-udevdir.patch	2023-12-08 00:01:36.0 +0100
@@ -0,0 +1,19 @@
+Index: digimend-dkms-11/Makefile
+===
+--- digimend-dkms-11.orig/Makefile
 digimend-dkms-11/Makefile
+@@ -7,11 +7,12 @@ KVERSION := $(shell uname -r)
+ KDIR := /lib/modules/$(KVERSION)/build
+ PWD := $(shell pwd)
+ DESTDIR =
+-UDEV_RULES = $(DESTDIR)/lib/udev/rules.d/90-digimend.rules
++UDEVDIR = $(shell pkg-config --variable=udevdir udev)
++UDEV_RULES = $(DESTDIR)$(UDEVDIR)/rules.d/90-digimend.rules
+ DEPMOD_CONF = $(DESTDIR)/etc/depmod.d/digimend.conf
+ DRACUT_CONF_DIR = $(DESTDIR)/usr/lib/dracut/dracut.conf.d
+ DRACUT_CONF = $(DRACUT_CONF_DIR)/90-digimend.conf
+-HID_REBIND = $(DESTDIR)/lib/udev/hid-rebind
++HID_REBIND = $(DESTDIR)$(UDEVDIR)/hid-rebind
+ DIGIMEND_DEBUG = $(DESTDIR)/usr/sbin/digimend-debug
+ XORG_CONF := $(DESTDIR)/usr/share/X11/xorg.conf.d/50-digimend.conf
+ PACKAGE_NAME = digimend-kernel-drivers

Bug#1057688: [Aptitude-devel] Bug#1057688: aptitude: Stray input on window click when running under tmux

[Thomas Dickey]

On Thu, Dec 07, 2023 at 06:06:49PM +0100, Axel Beckert wrote:
> Hi Sven,
> 
> Sven Joachim via Aptitude-devel wrote:
> > Debian ncurses maintainer here, bringing the ncurses upstream developer
> > into the loop.
> 
> Thanks for that!
> 
> > In addition to aptitude, mouse support is also broken in dialog(1) under
> > tmux.
> >
> > > Maybe this bug should instead be assigned to ncurses?
> > 
> > Probably should be reassigned to ncurses-base, but let's first see what
> > Thomas has to say about it.

It's probaby the same issue as this;

20231028
+ move xterm focus mode 1004 from xterm+sm+1006 into xterm+focus as
  fe/fd capabilities, like vim (vim-pr #13440).

(a change to the terminal description to help vim turned out to expose one
of the VTE bugs - fixed by making it less likely for other applications
to trigger the bug)

-- 
Thomas E. Dickey 
https://invisible-island.net


signature.asc
Description: PGP signature

Bug#1057559: emacs-wgrep: FTBFS: Error: error ("Test ‘wgrep-normal’ redefined")

[Xiyue Deng]

Nicholas D Steeves  writes:

> Xiyue Deng  writes:
>
>> Done.  Also reuploaded to mentors just in case.
>>
>
> Thanks, I've sponsored your upload.  Please push the release tag to git
> at your earliest convenience.
>

Thanks Nicholas!  Just pushed the tag 'debian/3.0.0-2' to team repo.
-- 
Xiyue Deng


signature.asc
Description: PGP signature

Bug#1057747: bumblebee: delegate placement of udev/systemd files to pkg-config data

[Chris Hofstaedtler]

Source: bumblebee
Version: 3.2.1-1
Severity: normal
Tags: patch
User: helm...@debian.org
Usertags: dep17m2

Dear Maintainer,

your package installs files related to udev and systemd, into /lib.
These files need to be moved to /usr/lib as part of Debian's
usr-merge effort [1].

Attached you will find a patch to delegate the exact placement of
the udev/systemd files to udev.pc/systemd.pc (using pkg-config).
This should work today
in unstable and, if necessary, for bookworm. Once udev.pc in
unstable points to /usr/lib your package will benefit automatically
after a binNMU or any other upload. systemd.pc was already updated
in unstable.

Later during the trixie cycle I expect this bug class to raise in
priority.

Per the wiki, it is advisable to upload to experimental first, and
wait a few days for the dumat tool to check your package. The same
is advisable when any structural changes are done in the trixie
cycle.

Thank you for considering,
Chris

[1] https://wiki.debian.org/UsrMerge
diff -Nru bumblebee-3.2.1/debian/bumblebee.install bumblebee-3.2.1/debian/bumblebee.install
--- bumblebee-3.2.1/debian/bumblebee.install	2023-01-05 01:53:42.0 +0100
+++ bumblebee-3.2.1/debian/bumblebee.install	2023-12-07 23:44:03.0 +0100
@@ -1,10 +1,10 @@
 etc/bumblebee/bumblebee.conf
 etc/bumblebee/xorg.conf.nvidia
 etc/bumblebee/xorg.conf.nouveau
-lib/udev/rules.d/99-bumblebee-nvidia-dev.rules
+${env:deb_udevdir}/rules.d/99-bumblebee-nvidia-dev.rules
 usr/bin/optirun
 usr/bin/bumblebee-bugreport
 usr/sbin/bumblebeed
 etc/bumblebee/*   usr/share/bumblebee/default-conf/
 debian/bumblebee.conf usr/share/bumblebee/modprobe.d/
-scripts/systemd/bumblebeed.servicelib/systemd/system/
+scripts/systemd/bumblebeed.service${env:deb_systemdsystemunitdir}/
diff -Nru bumblebee-3.2.1/debian/changelog bumblebee-3.2.1/debian/changelog
--- bumblebee-3.2.1/debian/changelog	2023-01-05 01:53:42.0 +0100
+++ bumblebee-3.2.1/debian/changelog	2023-12-07 23:44:03.0 +0100
@@ -1,3 +1,10 @@
+bumblebee (3.2.1-29.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Delegate placement of udev and systemd files to pkg-config data
+
+ -- Chris Hofstaedtler   Thu, 07 Dec 2023 23:44:03 +0100
+
 bumblebee (3.2.1-29) unstable; urgency=medium
 
   * Switch to dh-sequence-bash-completion.
diff -Nru bumblebee-3.2.1/debian/control bumblebee-3.2.1/debian/control
--- bumblebee-3.2.1/debian/control	2023-01-05 01:53:42.0 +0100
+++ bumblebee-3.2.1/debian/control	2023-12-07 23:41:44.0 +0100
@@ -16,6 +16,7 @@
  libx11-dev,
  pkg-config,
  libkmod-dev,
+ systemd-dev,
 Rules-Requires-Root: no
 Standards-Version: 4.6.2
 Homepage: https://launchpad.net/~bumblebee
diff -Nru bumblebee-3.2.1/debian/rules bumblebee-3.2.1/debian/rules
--- bumblebee-3.2.1/debian/rules	2023-01-05 01:53:42.0 +0100
+++ bumblebee-3.2.1/debian/rules	2023-12-07 23:44:03.0 +0100
@@ -57,12 +57,16 @@
 export DEB_BUILD_MAINT_OPTIONS = hardening=+all
 include /usr/share/dpkg/default.mk
 
+export deb_systemdsystemunitdir = $(shell pkg-config --variable=systemdsystemunitdir systemd | sed s,^/,,)
+export deb_udevdir = $(shell pkg-config --variable=udevdir udev | sed s,^/,,)
+
 %:
 	dh $@
 
 override_dh_auto_configure: $(MAINTSCRIPTS_GENERATED)
 ifeq ($(VENDOR),Ubuntu)
 	dh_auto_configure -- \
+		--with-udev-rules=/$(deb_udevdir)/rules.d
 		CONF_DRIVER_MODULE_NVIDIA=nvidia \
 		CONF_LDPATH_NVIDIA=/usr/lib/nvidia-current:/usr/lib32/nvidia-current:/usr/lib/x86_64-linux-gnu:/usr/lib/i386-linux-gnu \
 		CONF_MODPATH_NVIDIA=/usr/lib/nvidia-current/xorg,/usr/lib/xorg/modules \
@@ -70,6 +74,7 @@
 		CONF_XORG_BINARY=/usr/lib/xorg/Xorg
 else
 	dh_auto_configure -- \
+		--with-udev-rules=/$(deb_udevdir)/rules.d
 		CONF_DRIVER_MODULE_NVIDIA=nvidia \
 		CONF_LDPATH_NVIDIA=/usr/lib/x86_64-linux-gnu/nvidia:/usr/lib/i386-linux-gnu/nvidia:/usr/lib/x86_64-linux-gnu:/usr/lib/i386-linux-gnu \
 		CONF_MODPATH_NVIDIA=/usr/lib/nvidia,/usr/lib/xorg/modules \

Bug#1057559: emacs-wgrep: FTBFS: Error: error ("Test ‘wgrep-normal’ redefined")

[Nicholas D Steeves]

Xiyue Deng  writes:

> Done.  Also reuploaded to mentors just in case.
>

Thanks, I've sponsored your upload.  Please push the release tag to git
at your earliest convenience.


signature.asc
Description: PGP signature

Bug#1057746: beep: delegate placement of udev files to udev.pc

[Chris Hofstaedtler]

Source: beep
Version: 1.4.9-1
Severity: normal
Tags: patch
User: helm...@debian.org
Usertags: dep17m2

Dear Maintainer,

your package installs files related to udev, into /lib/udev. These
files need to be moved to /usr/lib as part of Debian's usr-merge
effort [1].

Attached you will find a patch to delegate the exact placement of
the udev files to udev.pc (using pkg-config). This should work today
in unstable and, if necessary, for bookworm. Once udev.pc in
unstable points to /usr/lib your package will benefit automatically
after a binNMU or any other upload.

Later during the trixie cycle I expect this bug class to raise in
priority.

Per the wiki, it is advisable to upload to experimental first, and
wait a few days for the dumat tool to check your package. The same
is advisable when any structural changes are done in the trixie
cycle.

Thank you for considering,
Chris

[1] https://wiki.debian.org/UsrMerge
diff -Nru beep-1.4.9/debian/beep.install beep-1.4.9/debian/beep.install
--- beep-1.4.9/debian/beep.install	2020-05-16 22:34:14.0 +0200
+++ beep-1.4.9/debian/beep.install	2023-12-07 23:33:18.0 +0100
@@ -1,4 +1,4 @@
 usr/bin
 usr/share/doc/beep
 usr/share/man
-debian/70-pcspkr-beep.rules lib/udev/rules.d/
+debian/70-pcspkr-beep.rules ${env:deb_udevdir}/rules.d/
diff -Nru beep-1.4.9/debian/beep-udeb.install beep-1.4.9/debian/beep-udeb.install
--- beep-1.4.9/debian/beep-udeb.install	2020-05-16 22:34:14.0 +0200
+++ beep-1.4.9/debian/beep-udeb.install	2023-12-07 23:33:13.0 +0100
@@ -1,2 +1,2 @@
 usr/bin
-debian/70-pcspkr-beep.rules lib/udev/rules.d/
+debian/70-pcspkr-beep.rules ${env:deb_udevdir}/rules.d/
diff -Nru beep-1.4.9/debian/changelog beep-1.4.9/debian/changelog
--- beep-1.4.9/debian/changelog	2020-05-16 22:53:59.0 +0200
+++ beep-1.4.9/debian/changelog	2023-12-07 23:34:12.0 +0100
@@ -1,3 +1,10 @@
+beep (1.4.9-1.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Delegate placement of udev files to pkg-config data
+
+ -- Chris Hofstaedtler   Thu, 07 Dec 2023 23:34:12 +0100
+
 beep (1.4.9-1) unstable; urgency=medium
 
   [ Rhonda D'Vine ]
diff -Nru beep-1.4.9/debian/control beep-1.4.9/debian/control
--- beep-1.4.9/debian/control	2020-05-16 22:46:17.0 +0200
+++ beep-1.4.9/debian/control	2023-12-07 23:34:12.0 +0100
@@ -2,7 +2,7 @@
 Section: sound
 Priority: optional
 Maintainer: Rhonda D'Vine 
-Build-Depends: debhelper-compat (= 13)
+Build-Depends: debhelper-compat (= 13), pkgconf, systemd-dev
 Standards-Version: 4.5.0
 Homepage: https://github.com/spkr-beep/beep
 Vcs-Browser: https://salsa.debian.org/rhonda/beep
diff -Nru beep-1.4.9/debian/rules beep-1.4.9/debian/rules
--- beep-1.4.9/debian/rules	2020-05-16 22:34:14.0 +0200
+++ beep-1.4.9/debian/rules	2023-12-07 23:34:12.0 +0100
@@ -4,6 +4,8 @@
 export DEB_BUILD_MAINT_OPTIONS=hardening=+all
 -include /usr/share/dpkg/buildtools.mk
 
+export deb_udevdir = $(shell pkg-config --variable=udevdir udev | sed s,^/,,)
+
 %:
 	dh $@
 

Bug#786453: New version 20180515 cannot be downloaded

[Alexandre Detiste]

https://web.archive.org/web/20220529104942/http://www.hoicher.de/hoichess/download/

-> tourney_manager-20180515.tar.gz

Bug#1057745: awesfx: delegate placement of udev files to udev.pc

[Chris Hofstaedtler]

Source: awesfx
Version: 0.5.2-1
Severity: normal
Tags: patch
User: helm...@debian.org
Usertags: dep17m2

Dear Maintainer,

your package installs files related to udev, into /lib/udev. These
files need to be moved to /usr/lib as part of Debian's usr-merge
effort [1].

Attached you will find a patch to delegate the exact placement of
the udev files to udev.pc (using pkg-config). This should work today
in unstable and, if necessary, for bookworm. Once udev.pc in
unstable points to /usr/lib your package will benefit automatically
after a binNMU or any other upload.

Note: the udev rule installed by dh_installudev will move when
dh_installudev is updated.

Later during the trixie cycle I expect this bug class to raise in
priority.

Per the wiki, it is advisable to upload to experimental first, and
wait a few days for the dumat tool to check your package. The same
is advisable when any structural changes are done in the trixie
cycle.

Thank you for considering,
Chris

[1] https://wiki.debian.org/UsrMerge
diff -Nru awesfx-0.5.2/debian/awesfx.install awesfx-0.5.2/debian/awesfx.install
--- awesfx-0.5.2/debian/awesfx.install	2019-08-05 22:11:00.0 +0200
+++ awesfx-0.5.2/debian/awesfx.install	2023-12-07 22:57:26.0 +0100
@@ -1,4 +1,4 @@
 debian/sfxloadrc etc
 debian/*.html usr/share/doc/awesfx
-debian/awesfx.sh lib/udev
+debian/awesfx.sh ${env:deb_udevdir}
 debian/awesfx.conf etc/modprobe.d
diff -Nru awesfx-0.5.2/debian/changelog awesfx-0.5.2/debian/changelog
--- awesfx-0.5.2/debian/changelog	2019-08-05 22:11:00.0 +0200
+++ awesfx-0.5.2/debian/changelog	2023-12-07 22:57:26.0 +0100
@@ -1,3 +1,10 @@
+awesfx (0.5.2-1.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Delegate placement of udev files to udev.pc
+
+ -- Chris Hofstaedtler   Thu, 07 Dec 2023 22:57:26 +0100
+
 awesfx (0.5.2-1) unstable; urgency=medium
 
   * New upstream version 0.5.2
diff -Nru awesfx-0.5.2/debian/compat awesfx-0.5.2/debian/compat
--- awesfx-0.5.2/debian/compat	2019-08-05 22:11:00.0 +0200
+++ awesfx-0.5.2/debian/compat	1970-01-01 01:00:00.0 +0100
@@ -1 +0,0 @@
-9
diff -Nru awesfx-0.5.2/debian/control awesfx-0.5.2/debian/control
--- awesfx-0.5.2/debian/control	2019-08-05 22:11:00.0 +0200
+++ awesfx-0.5.2/debian/control	2023-12-07 22:57:26.0 +0100
@@ -3,7 +3,7 @@
 Priority: optional
 Maintainer: Debian Multimedia Maintainers 
 Uploaders: Dmitry Eremin-Solenikov 
-Build-Depends: debhelper (>> 9.0.0), libasound2-dev, dh-autoreconf
+Build-Depends: debhelper-compat (= 13), libasound2-dev, dh-autoreconf, pkgconf, systemd-dev
 Homepage: https://github.com/tiwai/awesfx
 Standards-Version: 4.4.0
 Vcs-Git: https://salsa.debian.org/multimedia-team/awesfx.git
diff -Nru awesfx-0.5.2/debian/rules awesfx-0.5.2/debian/rules
--- awesfx-0.5.2/debian/rules	2019-08-05 22:11:00.0 +0200
+++ awesfx-0.5.2/debian/rules	2023-12-07 22:57:26.0 +0100
@@ -1,6 +1,7 @@
 #!/usr/bin/make -f
 
 export DEB_BUILD_MAINT_OPTIONS = hardening=+all
+export deb_udevdir = $(shell pkg-config --variable=udevdir udev | sed s,^/,,)
 
 %:
 	dh $@ --with autoreconf

Bug#1057567: libconfig-model-lcdproc-perl: FTBFS: Cannot determine local time zone

[gregor herrmann]

Control: forcemerge -1 1057566 1057568 1057569 1057571 1057572 1057592
Control: reassign -1 libdatetime-timezone-perl 1:2.60-1+2023c
Control: tags -1 = trixie sid
Control: retitle -1 libdatetime-timezone-perl: needs a dependency on tzdata 
(causes FTBFS in other package)
Control: affects -1 = libconfig-model-lcdproc-perl libapi-gitforge-perl 
libconfig-model-openssh-perl libconfig-model-systemd-perl libical-parser-perl 
libsoftware-copyright-perl pinto

On Wed, 06 Dec 2023 16:41:56 +0100, gregor herrmann wrote:

> "Cannot determine local time zone" is an exception thrown by
> DateTime::TimeZone::Local 
…
> I think the point
> for making libdatetime-timezone-perl depend on tzdata by itself gets
> stronger, which would en passant fix the test failures in the other
> packages.

Alright, no disagreement so far, I guess we can take this route.
Let's start with adjusting the bug metadata :)


Cheers,
gregor

-- 
 .''`.  https://info.comodo.priv.at -- Debian Developer https://www.debian.org
 : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D  85FA BB3A 6801 8649 AA06
 `. `'  Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe
   `-   


signature.asc
Description: Digital Signature

Bug#1057744: nmap: bring back zenmap

[Matthew Gabeler-Lee]

Package: nmap
Version: 7.93+dfsg1-1
Severity: wishlist

Some time ago, zenmap was removed due to being stuck back on python 2, but
as of nmap 0.94 [1] it has been brought up to date to use python 3 and
gobject, so hopefully it can now be brought back to Debian?

[1] 
https://github.com/nmap/nmap/blob/e47b742669e6aadcab8aaa16d123d8fa4832fe5d/CHANGELOG#L13

Bug#1057743: android-sdk-meta: delegate placement of udev files to udev.pc

[Chris Hofstaedtler]

Source: android-sdk-meta
Version: 28.0.2+9
Severity: normal
Tags: patch
User: helm...@debian.org
Usertags: dep17m2

Dear Maintainer,

your package installs files related to udev, into /lib/udev. These
files need to be moved to /usr/lib as part of Debian's usr-merge
effort [1].

Attached you will find a patch to delegate the exact placement of
the udev files to udev.pc (using pkg-config). This should work today
in unstable and, if necessary, for bookworm. Once udev.pc in
unstable points to /usr/lib your package will benefit automatically
after a binNMU or any other upload.

Later during the trixie cycle I expect this bug class to raise in
priority.

Per the wiki, it is advisable to upload to experimental first, and
wait a few days for the dumat tool to check your package. The same
is advisable when any structural changes are done in the trixie
cycle.

Thank you for considering,
Chris

[1] https://wiki.debian.org/UsrMerge
diff -Nru android-sdk-meta-28.0.2+9/debian/android-sdk-platform-tools-common.install android-sdk-meta-28.0.2+9+nmu1/debian/android-sdk-platform-tools-common.install
--- android-sdk-meta-28.0.2+9/debian/android-sdk-platform-tools-common.install	2023-01-24 07:07:40.0 +0100
+++ android-sdk-meta-28.0.2+9+nmu1/debian/android-sdk-platform-tools-common.install	2023-12-07 22:41:14.0 +0100
@@ -1,3 +1,3 @@
-51-android.rules lib/udev/rules.d
+51-android.rules ${env:deb_udevdir}/rules.d
 debian/android-sdk.metainfo.xml  usr/share/metainfo
 platform-tools/* usr/lib/android-sdk/platform-tools
diff -Nru android-sdk-meta-28.0.2+9/debian/changelog android-sdk-meta-28.0.2+9+nmu1/debian/changelog
--- android-sdk-meta-28.0.2+9/debian/changelog	2023-01-24 07:07:40.0 +0100
+++ android-sdk-meta-28.0.2+9+nmu1/debian/changelog	2023-12-07 22:41:14.0 +0100
@@ -1,3 +1,10 @@
+android-sdk-meta (28.0.2+9+nmu1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Delegate placement of udev files to udev.pc
+
+ -- Chris Hofstaedtler   Thu, 07 Dec 2023 22:41:14 +0100
+
 android-sdk-meta (28.0.2+9) unstable; urgency=medium
 
   * Team upload.
diff -Nru android-sdk-meta-28.0.2+9/debian/control android-sdk-meta-28.0.2+9+nmu1/debian/control
--- android-sdk-meta-28.0.2+9/debian/control	2023-01-24 07:07:40.0 +0100
+++ android-sdk-meta-28.0.2+9+nmu1/debian/control	2023-12-07 22:41:14.0 +0100
@@ -3,7 +3,7 @@
 Priority: optional
 Maintainer: Android Tools Maintainers 
 Uploaders: Chirayu Desai ,
-Build-Depends: debhelper-compat (= 12), dh-exec
+Build-Depends: debhelper-compat (= 13), dh-exec, pkg-config, systemd-dev
 Standards-Version: 4.5.0
 Vcs-Git: https://salsa.debian.org/android-tools-team/android-sdk-meta.git
 Vcs-Browser: https://salsa.debian.org/android-tools-team/android-sdk-meta
diff -Nru android-sdk-meta-28.0.2+9/debian/rules android-sdk-meta-28.0.2+9+nmu1/debian/rules
--- android-sdk-meta-28.0.2+9/debian/rules	2023-01-24 07:07:40.0 +0100
+++ android-sdk-meta-28.0.2+9+nmu1/debian/rules	2023-12-07 22:41:14.0 +0100
@@ -2,6 +2,8 @@
 
 include /usr/share/dpkg/pkg-info.mk
 
+export deb_udevdir = $(shell pkg-config --variable=udevdir udev | sed s,^/,,)
+
 export BUILD_TOOLS_VERSION = 29.0.3
 PLATFORM_TOOLS_VERSION = 28.0.2
 # this needs to also support updates and ubuntu versions, e.g.:
diff -Nru android-sdk-meta-28.0.2+9/debian/tests/control android-sdk-meta-28.0.2+9+nmu1/debian/tests/control
--- android-sdk-meta-28.0.2+9/debian/tests/control	2023-01-24 07:07:40.0 +0100
+++ android-sdk-meta-28.0.2+9+nmu1/debian/tests/control	2023-12-07 22:41:10.0 +0100
@@ -2,9 +2,9 @@
 
 Tests: test-deb-revision-parsing
 
-Test-Command: test -e /lib/udev/rules.d/51-android.rules
+Test-Command: test -e /usr/lib/udev/rules.d/51-android.rules
 Architecture: amd64 i386 armel armhf arm64 mipsel mips64el ppc64el
 Depends: adb, android-sdk-platform-tools-common
 
-Test-Command: test -e /lib/udev/rules.d/51-android.rules
+Test-Command: test -e /usr/lib/udev/rules.d/51-android.rules
 Depends: android-sdk-platform-tools-common

Bug#1057742: amazon-ec2-utils: delegate placement of udev files to udev.pc

[Chris Hofstaedtler]

> Attached you will find a patch to delegate the exact placement of
> the udev files to udev.pc (using pkg-config). 

Please find a corrected patch attached.

Chris

diff -Nru amazon-ec2-utils-2.1.0/debian/amazon-ec2-utils.install amazon-ec2-utils-2.1.0/debian/amazon-ec2-utils.install
--- amazon-ec2-utils-2.1.0/debian/amazon-ec2-utils.install	2023-09-30 00:40:28.0 +0200
+++ amazon-ec2-utils-2.1.0/debian/amazon-ec2-utils.install	2023-12-07 22:35:46.0 +0100
@@ -1,4 +1,4 @@
 ebsnvme-id /usr/sbin/
 ec2-metadata /usr/bin/
-ec2nvme-nsid /lib/udev/
-70-ec2-nvme-devices.rules /lib/udev/rules.d/
+ec2nvme-nsid ${env:deb_udevdir}/
+70-ec2-nvme-devices.rules ${env:deb_udevdir}/rules.d/
diff -Nru amazon-ec2-utils-2.1.0/debian/changelog amazon-ec2-utils-2.1.0/debian/changelog
--- amazon-ec2-utils-2.1.0/debian/changelog	2023-09-30 01:18:53.0 +0200
+++ amazon-ec2-utils-2.1.0/debian/changelog	2023-12-07 22:35:46.0 +0100
@@ -1,3 +1,10 @@
+amazon-ec2-utils (2.1.0-1.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Delegate placement of udev files to udev.pc
+
+ -- Chris Hofstaedtler   Thu, 07 Dec 2023 22:35:46 +0100
+
 amazon-ec2-utils (2.1.0-1) unstable; urgency=medium
 
   * New upstream release 2.1.0
diff -Nru amazon-ec2-utils-2.1.0/debian/control amazon-ec2-utils-2.1.0/debian/control
--- amazon-ec2-utils-2.1.0/debian/control	2023-09-30 00:40:28.0 +0200
+++ amazon-ec2-utils-2.1.0/debian/control	2023-12-07 22:35:46.0 +0100
@@ -3,7 +3,7 @@
 Priority: optional
 Maintainer: Debian Cloud Team 
 Uploaders: Noah Meyerhans 
-Build-Depends: debhelper-compat (= 12)
+Build-Depends: debhelper-compat (= 13), pkgconf, systemd-dev
 Standards-Version: 4.5.0
 Homepage: https://github.com/aws/amazon-ec2-utils
 Vcs-Browser: https://salsa.debian.org/cloud-team/amazon-ec2-utils
diff -Nru amazon-ec2-utils-2.1.0/debian/rules amazon-ec2-utils-2.1.0/debian/rules
--- amazon-ec2-utils-2.1.0/debian/rules	2023-09-30 00:40:28.0 +0200
+++ amazon-ec2-utils-2.1.0/debian/rules	2023-12-07 22:35:46.0 +0100
@@ -3,5 +3,7 @@
 # output every command that modifies files on the build system.
 #export DH_VERBOSE = 1
 
+export deb_udevdir = $(shell pkg-config --variable=udevdir udev)
+
 %:
 	dh $@

Bug#1057279: xtrlock option to verify password via a subprocess

[Simon Tatham]

Matthew Vernon  wrote:
> I think both docs and making the hourglass optional would be good, 
> please;

Revised patches attached.

The runtime usage message was starting to get large, so I've appended a
third patch that sets up standard --help and --version options, in case
that's also useful to you.

Cheers,
Simon

-- 
import hashlib; print((lambda p,q,g,y,r,s,m: (lambda w:(pow(g,int(hashlib.sha1(
m.encode('ascii')).hexdigest(),16)*w%q,p)*pow(y,r*w%q,p)%p)%q)(pow(s,q-2,q))==r
and s%q!=0 and m)(12342649995480866419, 2278082317364501, 1670428356600652640,
5398151833726432125, 645223105888478, 1916678356240619, ""))


0001-Add-check-option-to-specify-a-password-checking-subp.patch
Description: Binary data


0002-Display-a-wait-cursor-while-password-is-being-valida.patch
Description: Binary data


0003-Reorganise-help-output-into-help-and-version.patch
Description: Binary data

Bug#1057742: amazon-ec2-utils: delegate placement of udev files to udev.pc

[Chris Hofstaedtler]

Source: amazon-ec2-utils
Version: 2.1.0-1
Severity: normal
Tags: patch
User: helm...@debian.org
Usertags: dep17m2

Dear Maintainer,

your package installs files related to udev, into /lib/udev. These
files need to be moved to /usr/lib as part of Debian's usr-merge
effort [1].

Attached you will find a patch to delegate the exact placement of
the udev files to udev.pc (using pkg-config). This should work today
in unstable and, if necessary, for bookworm. Once udev.pc in
unstable points to /usr/lib your package will benefit automatically
after a binNMU or any other upload.

Later during the trixie cycle I expect this bug class to raise in
priority.

Per the wiki, it is advisable to upload to experimental first, and
wait a few days for the dumat tool to check your package. The same
is advisable when any structural changes are done in the trixie
cycle.

Thank you for considering,
Chris

[1] https://wiki.debian.org/UsrMerge
diff -Nru amazon-ec2-utils-2.1.0/debian/amazon-ec2-utils.install amazon-ec2-utils-2.1.0/debian/amazon-ec2-utils.install
--- amazon-ec2-utils-2.1.0/debian/amazon-ec2-utils.install	2023-09-30 00:40:28.0 +0200
+++ amazon-ec2-utils-2.1.0/debian/amazon-ec2-utils.install	2023-12-07 22:35:46.0 +0100
@@ -1,4 +1,4 @@
 ebsnvme-id /usr/sbin/
 ec2-metadata /usr/bin/
-ec2nvme-nsid /lib/udev/
-70-ec2-nvme-devices.rules /lib/udev/rules.d/
+ec2nvme-nsid ${env:deb_udevdir}
+70-ec2-nvme-devices.rules ${env:deb_udevdir}
diff -Nru amazon-ec2-utils-2.1.0/debian/changelog amazon-ec2-utils-2.1.0/debian/changelog
--- amazon-ec2-utils-2.1.0/debian/changelog	2023-09-30 01:18:53.0 +0200
+++ amazon-ec2-utils-2.1.0/debian/changelog	2023-12-07 22:35:46.0 +0100
@@ -1,3 +1,10 @@
+amazon-ec2-utils (2.1.0-1.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Delegate placement of udev files to udev.pc
+
+ -- Chris Hofstaedtler   Thu, 07 Dec 2023 22:35:46 +0100
+
 amazon-ec2-utils (2.1.0-1) unstable; urgency=medium
 
   * New upstream release 2.1.0
diff -Nru amazon-ec2-utils-2.1.0/debian/control amazon-ec2-utils-2.1.0/debian/control
--- amazon-ec2-utils-2.1.0/debian/control	2023-09-30 00:40:28.0 +0200
+++ amazon-ec2-utils-2.1.0/debian/control	2023-12-07 22:35:46.0 +0100
@@ -3,7 +3,7 @@
 Priority: optional
 Maintainer: Debian Cloud Team 
 Uploaders: Noah Meyerhans 
-Build-Depends: debhelper-compat (= 12)
+Build-Depends: debhelper-compat (= 13), pkgconf, systemd-dev
 Standards-Version: 4.5.0
 Homepage: https://github.com/aws/amazon-ec2-utils
 Vcs-Browser: https://salsa.debian.org/cloud-team/amazon-ec2-utils
diff -Nru amazon-ec2-utils-2.1.0/debian/rules amazon-ec2-utils-2.1.0/debian/rules
--- amazon-ec2-utils-2.1.0/debian/rules	2023-09-30 00:40:28.0 +0200
+++ amazon-ec2-utils-2.1.0/debian/rules	2023-12-07 22:35:46.0 +0100
@@ -3,5 +3,7 @@
 # output every command that modifies files on the build system.
 #export DH_VERBOSE = 1
 
+export deb_udevdir = $(shell pkg-config --variable=udevdir udev)
+
 %:
 	dh $@

Bug#1027069: waybar: improve its .service file?

[Vladimir K]

One can repurpose sysetmd XDG Autostart filter:

Either exlusive method:

ExecCondition=/lib/systemd/systemd-xdg-autostart-condition "" "GNOME:KDE"

Or inclusive:

ExecCondition=/lib/systemd/systemd-xdg-autostart-condition 
"wlroots:sway:Wayfire:labwc" ""

Bug#1057741: nvidia-support: delegate placement of udev files to udev.pc

[Chris Hofstaedtler]

Source: nvidia-support
Version: 20220217+3
Severity: normal
Tags: patch
User: helm...@debian.org
Usertags: dep17m2

Dear Maintainer,

your package installs files related to udev, into /lib/udev. These
files need to be moved to /usr/lib as part of Debian's usr-merge
effort [1].

Attached you will find a patch to delegate the exact placement of
the udev files to udev.pc (using pkg-config). This should work today
in unstable and, if necessary, for bookworm. Once udev.pc in
unstable points to /usr/lib your package will benefit automatically
after a binNMU or any other upload.

Note: the udev rule installed by dh_installudev will move when
dh_installudev is updated.

Later during the trixie cycle I expect this bug class to raise in
priority.

Per the wiki, it is advisable to upload to experimental first, and
wait a few days for the dumat tool to check your package. The same
is advisable when any structural changes are done in the trixie
cycle.

Thank you for considering,
Chris

[1] https://wiki.debian.org/UsrMerge
diff -Nru nvidia-support-20220217+3/debian/changelog nvidia-support-20220217+3+nmu1/debian/changelog
--- nvidia-support-20220217+3/debian/changelog	2023-06-12 16:55:42.0 +0200
+++ nvidia-support-20220217+3+nmu1/debian/changelog	2023-12-07 22:28:54.0 +0100
@@ -1,3 +1,9 @@
+nvidia-support (20220217+3+nmu1) UNRELEASED; urgency=medium
+
+  * Delegate placement of udev files to udev.pc. (Closes: #-1)
+
+ -- Chris Hofstaedtler   Thu, 07 Dec 2023 22:28:54 +0100
+
 nvidia-support (20220217+3) unstable; urgency=medium
 
   * nvidia-installer-cleanup: Add Breaks against obsolete nvidia-*-dkms
diff -Nru nvidia-support-20220217+3/debian/control nvidia-support-20220217+3+nmu1/debian/control
--- nvidia-support-20220217+3/debian/control	2023-06-12 16:55:42.0 +0200
+++ nvidia-support-20220217+3+nmu1/debian/control	2023-12-07 22:27:02.0 +0100
@@ -7,7 +7,9 @@
  Luca Boccassi ,
 Build-Depends:
  debhelper-compat (= 13),
+ pkgconf,
  po-debconf,
+ systemd-dev,
 Rules-Requires-Root: no
 Standards-Version: 4.6.2
 Vcs-Browser: https://salsa.debian.org/nvidia-team/nvidia-support
diff -Nru nvidia-support-20220217+3/debian/nvidia-kernel-common.install nvidia-support-20220217+3+nmu1/debian/nvidia-kernel-common.install
--- nvidia-support-20220217+3/debian/nvidia-kernel-common.install	2023-06-12 16:55:42.0 +0200
+++ nvidia-support-20220217+3+nmu1/debian/nvidia-kernel-common.install	2023-12-07 22:28:46.0 +0100
@@ -1,2 +1,2 @@
 nvidia_helper.ck /usr/lib/ConsoleKit/run-seat.d/
-nvidia_helper /lib/udev/
+nvidia_helper ${env:deb_udevdir}
diff -Nru nvidia-support-20220217+3/debian/rules nvidia-support-20220217+3+nmu1/debian/rules
--- nvidia-support-20220217+3/debian/rules	2023-06-12 16:55:42.0 +0200
+++ nvidia-support-20220217+3+nmu1/debian/rules	2023-12-07 22:28:37.0 +0100
@@ -1,4 +1,6 @@
 #!/usr/bin/make -f
+export deb_udevdir = $(shell pkg-config --variable=udevdir udev)
+
 %:
 	dh $@
 

Bug#1057740: gobi-loader: delegate placement of udev files to udev.pc

[Chris Hofstaedtler]

Source: gobi-loader
Version: 0.6-1
Severity: normal
Tags: patch
User: helm...@debian.org
Usertags: dep17m2

Dear Maintainer,

your package installs files related to udev, into /lib/udev. These
files need to be moved to /usr/lib as part of Debian's usr-merge
effort.

Attached you will find a patch to delegate the exact placement of
the udev files to udev.pc (using pkg-config). This should work today
in unstable and, if necessary, for bookworm. Once udev.pc in
unstable points to /usr/lib your package will benefit automatically
after a binNMU or any other upload.

Later during the trixie cycle I expect this bug class to raise in
priority.

Thank you for considering,
Chris
diff -u gobi-loader-0.6/debian/control gobi-loader-0.6/debian/control
--- gobi-loader-0.6/debian/control
+++ gobi-loader-0.6/debian/control
@@ -2,7 +2,7 @@
 Section: contrib/admin
 Priority: extra
 Maintainer: Mark Hymers 
-Build-Depends: debhelper (>= 7.0.50~)
+Build-Depends: debhelper (>= 7.0.50~), pkgconf, systemd-dev
 Standards-Version: 3.8.4
 Homepage: http://www.codon.org.uk/~mjg59/gobi_loader/
 Vcs-Git: git://git.debian.org/users/mhy/gobi-loader.git
diff -u gobi-loader-0.6/debian/rules gobi-loader-0.6/debian/rules
--- gobi-loader-0.6/debian/rules
+++ gobi-loader-0.6/debian/rules
@@ -10,14 +10,15 @@
 #export DH_VERBOSE=1
 
 PKGDIR=$(CURDIR)/debian/gobi-loader
+UDEVDIR=$(shell pkg-config --variable=udevdir udev)
 
 %:
 	dh $@ 
 
 override_dh_auto_install:
-	mkdir -p $(PKGDIR)/lib/udev
-	install -m0755 gobi_loader $(PKGDIR)/lib/udev/gobi_loader
-	sed s@gobi_loader@/lib/udev/gobi_loader@ 60-gobi.rules > debian/gobi-loader.udev
+	mkdir -p $(PKGDIR)$(UDEVDIR)
+	install -m0755 gobi_loader $(PKGDIR)$(UDEVDIR)/gobi_loader
+	sed s@gobi_loader@$(UDEVDIR)/gobi_loader@ 60-gobi.rules > debian/gobi-loader.udev
 
 override_dh_auto_clean:
 	make clean
diff -u gobi-loader-0.6/debian/changelog gobi-loader-0.6/debian/changelog
--- gobi-loader-0.6/debian/changelog
+++ gobi-loader-0.6/debian/changelog
@@ -1,3 +1,10 @@
+gobi-loader (0.6-1.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Delegate placement of udev files to udev.pc's udevdir.
+
+ -- Chris Hofstaedtler   Thu, 07 Dec 2023 22:01:08 +0100
+
 gobi-loader (0.6-1) unstable; urgency=low
 
   * Initial release (Closes: #585567).

Bug#1055987: ITP: virt-firmware -- Tools for manipulating edk2 (ovmf/qemu-efi) firmware images

[Luca Boccassi]

On Wed, 15 Nov 2023 05:54:23 -0700 dann frazier 
wrote:
> Package: wnpp
> Severity: wishlist
> Owner: dann frazier 
> X-Debbugs-Cc: debian-de...@lists.debian.org
> 
> * Package name    : virt-firmware
>   Version : 23.10
>   Upstream Contact: Gerd Hoffmann 
> * URL : https://gitlab.com/kraxel/virt-firmware
> * License : GPL-2+
>   Programming Lang: Python
>   Description : Tools for manipulating edk2 (ovmf/qemu-efi)
firmware images
> 
> This is a collection of tools for edk2 firmware images. They support
> decoding and printing the content of firmware volumes. Variable
stores
> (e.g. OVMF_VARS.fd) can be modified, for example to enroll secure
boot
> certificates. Tools included:
> 
>  virt-fw-dump - Decodes and prints the content of firmware volumes.
> 
>  virt-fw-vars - Print and edit variable store volumes. Currently
focused on
> enrolling certificates and enabling secure boot.
> 
>  virt-fw-sigdb - Print and edit EFI signature database files.
> 
>  host-efi-vars - Read efi variables from linux efivarfs and
decode/print them.
> 
>  kernel-bootcfg - Manage efi boot configuration for UKIs (unified
kernel
>   images) when using direct boot (without boot loader
like
> grub or systemd-boot).
> 
>  pe-dumpinfo - Information dump for pe (the format used by EFI)
binaries.
> 
>  pe-listsigs - List signatures and certificate chain for pe binaries.
Can also
>    extract certificates & signatures.
> 
> 
> My immediate motivation for packaging this is that, as the maintainer
of
> the edk2 package, I need to remove some deprecated image types -
specifically
> the OVMF 2M images. These utilities can help users migrate their VMs
to
> supported types by dumping/loading the variable stores.
> 
> In the future, I expect edk2 packaging to evolve into using these
tools
> to modify images out-of-band, instead of launching QEMU instances to
> modify them in-band as part of the build.
> 

Hello Dann,

I find myself in need of this package for some CI usage as well, are
you planning to work on this soon? Do you need any help?

Thanks!

-- 
Kind regards,
Luca Boccassi


signature.asc
Description: This is a digitally signed message part

Bug#1057421: sysstat: FTBFS: dh_install: warning: Cannot find (any matches for) "debian/tmp/lib/systemd/" (tried in ., debian/tmp)

[Chris Hofstaedtler]

Control: tags -1 + patch

* Chris Hofstaedtler :
> systemd.pc changed systemd_system_unit_dir to point to /usr. As a
> consequence, your package now FTBFS in unstable.

Please find a patch fixing this attached. It should also work if
sysstat is backported without additional changes.

Best,
Chris
diff -Nru sysstat-12.6.1/debian/changelog sysstat-12.6.1/debian/changelog
--- sysstat-12.6.1/debian/changelog	2022-12-04 22:23:25.0 +0100
+++ sysstat-12.6.1/debian/changelog	2023-12-07 21:50:19.0 +0100
@@ -1,3 +1,11 @@
+sysstat (12.6.1-1.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix FBTS when systemdsystemunitdir changes in systemd.pc. (Closes:
+#1057421)
+
+ -- Chris Hofstaedtler   Thu, 07 Dec 2023 21:50:19 +0100
+
 sysstat (12.6.1-1) unstable; urgency=medium
 
   * New upstream stable version: fixes size_t overflow in sa_common.c
diff -Nru sysstat-12.6.1/debian/control sysstat-12.6.1/debian/control
--- sysstat-12.6.1/debian/control	2022-12-04 22:23:25.0 +0100
+++ sysstat-12.6.1/debian/control	2023-12-07 21:48:26.0 +0100
@@ -6,7 +6,8 @@
gettext,
libsensors-dev,
pkg-config,
-   systemd
+   systemd,
+   systemd-dev
 Standards-Version: 4.6.1
 Rules-Requires-Root: no
 Homepage: http://sebastien.godard.pagesperso-orange.fr/
diff -Nru sysstat-12.6.1/debian/rules sysstat-12.6.1/debian/rules
--- sysstat-12.6.1/debian/rules	2022-12-04 22:23:25.0 +0100
+++ sysstat-12.6.1/debian/rules	2023-12-07 21:50:09.0 +0100
@@ -19,6 +19,8 @@
 
 DFLAGS :=
 
+export deb_systemdsystemunitdir=$(shell pkgconf --variable=systemdsystemunitdir systemd | sed s,^/,,)
+
 %:
 	dh ${@}
 
diff -Nru sysstat-12.6.1/debian/sysstat.install sysstat-12.6.1/debian/sysstat.install
--- sysstat-12.6.1/debian/sysstat.install	2022-12-04 22:23:25.0 +0100
+++ sysstat-12.6.1/debian/sysstat.install	2023-12-07 21:50:17.0 +0100
@@ -1,5 +1,5 @@
 debian/debian-sa1 usr/lib/sysstat
 debian/tmp/etc/
-debian/tmp/lib/systemd/
+debian/tmp/${env:deb_systemdsystemunitdir}
 debian/tmp/usr/
 debian/tmp/var/

Bug#1057229: brightness-udev: installs file into /lib/udev/rules.d

[Chris Hofstaedtler]

Control: tags -1 + patch

* Chris Hofstaedtler :
> your package installs the file /lib/udev/rules.d/90-brightnessctl.rules.
> Apparently this path is hard-coded, either in the upstream build system
> or the packaging.

Please find attached a patch, which delegates placement of the udev
files to udev.pc's udevdir.

Please consider applying it soon.

Thanks,
Chris

diff -Nru brightnessctl-0.5.1/debian/brightness-udev.install brightnessctl-0.5.1/debian/brightness-udev.install
--- brightnessctl-0.5.1/debian/brightness-udev.install	2020-11-30 16:06:43.0 +0100
+++ brightnessctl-0.5.1/debian/brightness-udev.install	2023-12-07 21:20:23.0 +0100
@@ -1,2 +1,2 @@
-/lib/udev/rules.d/90-brightnessctl.rules
-debian/bright-helper /lib/udev
+${env:UDEVDIR}/90-brightnessctl.rules
+debian/bright-helper ${env:deb_udevdir}
diff -Nru brightnessctl-0.5.1/debian/changelog brightnessctl-0.5.1/debian/changelog
--- brightnessctl-0.5.1/debian/changelog	2020-11-30 16:06:43.0 +0100
+++ brightnessctl-0.5.1/debian/changelog	2023-12-07 21:20:23.0 +0100
@@ -1,3 +1,9 @@
+brightnessctl (0.5.1-3.1) UNRELEASED; urgency=medium
+
+  * Delegate placement of udev files to udev.pc (Closes: #-1)
+
+ -- Chris Hofstaedtler   Thu, 07 Dec 2023 21:20:23 +0100
+
 brightnessctl (0.5.1-3) unstable; urgency=low
 
   * brightness-udev
diff -Nru brightnessctl-0.5.1/debian/control brightnessctl-0.5.1/debian/control
--- brightnessctl-0.5.1/debian/control	2020-11-30 16:06:43.0 +0100
+++ brightnessctl-0.5.1/debian/control	2023-12-07 21:20:23.0 +0100
@@ -2,7 +2,7 @@
 Maintainer: nicoo 
 Section: misc
 Priority: optional
-Build-Depends: debhelper-compat (= 13)
+Build-Depends: debhelper-compat (= 13), systemd-dev, pkgconf
 Standards-Version: 4.5.1
 Homepage:https://github.com/Hummer12007/brightnessctl
 Vcs-Browser: https://salsa.debian.org/debian/brightnessctl
diff -Nru brightnessctl-0.5.1/debian/rules brightnessctl-0.5.1/debian/rules
--- brightnessctl-0.5.1/debian/rules	2020-11-30 16:06:43.0 +0100
+++ brightnessctl-0.5.1/debian/rules	2023-12-07 21:20:23.0 +0100
@@ -2,5 +2,9 @@
 
 export DEB_BUILD_MAINT_OPTIONS = hardening=+all
 
+export deb_udevdir = $(shell pkg-config --variable=udevdir udev)
+# for Makefile
+export UDEVDIR = ${deb_udevdir}/rules.d
+
 %:
 	dh $@

Bug#1057739: jupyter-server: CVE-2023-39968

[Salvatore Bonaccorso]

Source: jupyter-server
Version: 1.23.3-1
Severity: important
Tags: security upstream
X-Debbugs-Cc: car...@debian.org, Debian Security Team 
Control: fixed -1 2.9.1-1

Hi,

The following vulnerability was published for jupyter-server.

CVE-2023-39968[0]:
| jupyter-server is the backend for Jupyter web applications. Open
| Redirect Vulnerability. Maliciously crafted login links to known
| Jupyter Servers can cause successful login or an already logged-in
| session to be redirected to arbitrary sites, which should be
| restricted to Jupyter Server-served URLs. This issue has been
| addressed in commit `29036259` which is included in release 2.7.2.
| Users are advised to upgrade. There are no known workarounds for
| this vulnerability.


If you fix the vulnerability please also make sure to include the
CVE (Common Vulnerabilities & Exposures) id in your changelog entry.

The issue is already fixed in experimental.

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2023-39968
https://www.cve.org/CVERecord?id=CVE-2023-39968
[1] 
https://github.com/jupyter-server/jupyter_server/security/advisories/GHSA-r726-vmfq-j9j3

Regards,
Salvatore

Bug#1057714: htop: newlines in cmdline rendered as U+FFFD

[наб]

Oddly, I cannot reproduce this on bookworm (htop 3.2.2-2 as well)
by running the same cmdline (
-- >8 --
sh -c 'make -C /lib/modules/6.5.0-5-amd64/build CC=gcc-13 \
  \
M="$PWD"  O=/lib/modules/6.5.0-5-amd64/build CONFIG_ZFS=m modules; 
sleep 100'
-- >8 --
) explicitly.


signature.asc
Description: PGP signature

Bug#1057738: chrony: use cached or "fallback" IP addresses on DNS failure

[Michael Gold]

Package: chrony
Version: 4.5-1
Severity: wishlist

Dear Maintainer,

I saw this change in the 4.4 release notes:
* Refresh address of NTP sources periodically

That made me think it could also be useful to support some "pre-seeding"
and/or caching of DNS results.  I usually configure a few sources via IP
addresses, just in case DNS is slow or unavailable at boot time (perhaps
DNSSEC is failing due to a terribly inaccurate clock).  But IP addresses
could change without me noticing, and some server operators request that
DNS be used whenever possible.

Maybe it should be possible to specify fallback addresses, to be used in
the case of a temporary lookup failure; for example,
  server ntp.example.net ip=2001:db8::7b ip=192.0.2.123

And I've already got .nts files in /var/lib/chrony for serveral sources,
which makes me think there could also be files caching the last-known IP
addresses for each server (possibly with expiry times and enabled via an
option such as "cacheaddr").  For servers with NTS, that data appears to
already be available.

- Michael


-- System Information:
Debian Release: trixie/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 6.5.0-5-amd64 (SMP w/32 CPU threads; PREEMPT)
Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_CA:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages chrony depends on:
ii  adduser  3.137
ii  init-system-helpers  1.66
ii  iproute2 6.6.0-1
ii  libc62.37-13
ii  libcap2  1:2.66-4
ii  libedit2 3.1-20230828-1
ii  libgnutls30  3.8.2-1
ii  libnettle8   3.9.1-2
ii  libseccomp2  2.5.4-2+b1
ii  tzdata-legacy2023c-11
ii  ucf  3.0043+nmu1

chrony recommends no packages.

Versions of packages chrony suggests:
ii  bind9-dnsutils [dnsutils]  1:9.19.17-1
pn  networkd-dispatcher

-- no debconf information


signature.asc
Description: PGP signature

Bug#1057050: qt6-multimedia: Please build with EIGEN_DONT_VECTORIZE on powerpc to fix FTBFS

[Patrick Franz]

Hej,

Am Donnerstag, 7. Dezember 2023, 08:09:50 CET schrieb Christian 
Marillat:
> On 02 déc. 2023 10:10, John Paul Adrian Glaubitz  wrote:
> > Hi!
> > 
> > On Sat, 2023-12-02 at 00:46 +0100, Patrick Franz wrote:
> >> We're in the middle of packaging Qt 6.6 and I had not planned to do
> >> any more 6.4.2 updates unless absolutely necessary.
> >> 
> >> Do you know whether this patch will also work on Qt 6.6.1 ?
> > 
> > Yes, absolutely. And since it only adds some powerpc-specific lines
> > to debian/rules, there is nothing really that would need to be
> > rebased when updating to a newer Qt version.
> > 
> > It's always safe to apply this patch.
> 
> It is possible to see this bug fixed ?

I'll include the fix in 6.6.1 which is being worked on.


-- 
Med vänliga hälsningar

Patrick Franz

Bug#1057737: python-cartopy: FTBFS with Python 3.12

[Bas Couwenberg]

Source: python-cartopy
Version: 0.22.0+dfsg-1
Severity: serious
Tags: ftbfs upstream
Justification: makes the package in question unusable or mostly so
Control: forwarded -1 https://github.com/SciTools/cartopy/issues/2301

Dear Maintainer,

Your package FTBFS with Python 3.12:

 aarch64-linux-gnu-gcc -fno-strict-overflow -Wsign-compare -DNDEBUG -g -O2 
-Wall -g -fstack-protector-strong -fstack-clash-protection -Wformat 
-Werror=format-security -mbranch-protection=standard -g -fwrapv -O2 -g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong 
-fstack-clash-protection -Wformat -Werror=format-security 
-mbranch-protection=standard -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC 
-I/usr/lib/python3/dist-packages/numpy/core/include -I/usr/include/python3.12 
-c lib/cartopy/trace.cpp -o 
build/temp.linux-aarch64-cpython-312/lib/cartopy/trace.o
 lib/cartopy/trace.cpp: In function ‘bool 
__pyx_f_7cartopy_5trace_degenerate_line(const __pyx_t_7cartopy_5trace_Line&)’:
 lib/cartopy/trace.cpp:1623:34: error: ‘_PyCFrame’ {aka ‘struct _PyCFrame’} has 
no member named ‘use_tracing’
  1623 |  (unlikely((tstate)->cframe->use_tracing) &&\
   |  ^

https://buildd.debian.org/status/fetch.php?pkg=python-cartopy=arm64=0.22.0%2Bdfsg-1%2Bb1=1701974552=0

Bug#1057736: rust-src: Ship Cargo.lock to enable "cargo -Z build-std" usecase

[Jonathan Neuschäfer]

Package: cargo
Version: 0.66.0+ds1-1
Severity: wishlist

Cargo has a new (nightly) feature, build-std[1], which rebuilds the
standard library along with the target crate. This is especially useful
when cross-compiling, as Debian doesn't ship the standard library
pre-built for other architectures.

This requires Cargo.lock, not just Cargo.toml in the rust source
directory, but the rust-src Debian package only contains Cargo.toml
right now[2].


## Potential downsides of shipping Cargo.toml

- cargo -Z build-std is currently a nightly feature, and the rust
  toolchain in Debian is not nightly, so build-std is only usable with
  some tricks[3].
- However, I think it wouldn't do harm to include Cargo.lock in the
  package.


[1]: https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#build-std
[2]: 
https://salsa.debian.org/rust-team/rust/-/blob/debian/sid/debian/rust-src.install?ref_type=heads
[3]: RUSTC_BOOTSTRAP=1 tricks cargo into allowing nightly features,
 RUSTFLAGS=-Clinker=arm-linux-gnueabi-gcc appears to be necessary as well

-- System Information:
Debian Release: trixie/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.5.0-4-amd64 (SMP w/12 CPU threads; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages cargo depends on:
ii  binutils   2.41.50.20231202-1
ii  clang  1:16.0-57
ii  clang-14 [c-compiler]  1:14.0.6-16
ii  clang-16 [c-compiler]  1:16.0.6-19
ii  gcc [c-compiler]   4:13.2.0-2
ii  gcc-11 [c-compiler]11.4.0-5
ii  gcc-12 [c-compiler]12.3.0-11
ii  gcc-13 [c-compiler]13.2.0-7
ii  libc6  2.37-12
ii  libcurl3-gnutls8.4.0-2
ii  libgcc-s1  13.2.0-7
ii  libgit2-1.51.5.1+ds-1
ii  libssh2-1  1.11.0-3
ii  libssl33.0.11-1
ii  rustc  1.70.0+dfsg1-1
ii  zlib1g 1:1.2.13.dfsg-3

cargo recommends no packages.

Versions of packages cargo suggests:
pn  cargo-doc  
ii  python33.11.4-5+b1

-- no debconf information

Bug#1032659: ITP: golang-github-go-task-slim-sprig -- Useful template functions for Go templates.

[Christopher Obbard]

Hi Mark,

I will be willing to sponsor this package (mainly as I am looking to using it
in Debos). Your packaging looks generally good, but I have noticed a few minor
issues with the Git repo / packaging, let me know if you can fix these or if
you'd like me to do so.

- d/copyright: "Copyright: 2019 Task" seems.. wrong? Also, for the record
there is no explicit licence file in the upstream repository, but the GitHub
page says MIT.

- The package's commit history seems to modify the original source, e.g.
908e6bca ("Ignore _build and quilt .pc dirs via .gitignore") which is then
reverted by af533953 ("Import Debian changes 2.20.0-1"). It would be far
cleaner to drop these commits.

- 6ef11ba6 ("fixup: unstable build submission") seems to be wrong. As you're
not uploading into unstable, you should leave it as UNRELEASED.

- v3.0.0 has been released upstream. What would the plan be for importing
that?

- The TestShuffle function seems to fail (heh, is this test even deterministic
?):

> $ gbp buildpackage --git-pbuilder
> === RUN   TestShuffle
> functions_test.go:82: 
>   Error Trace:/build/golang-github-go-task-slim-sprig-
> 2.20.0/_build/src/github.com/go-task/slim-sprig/functions_test.go:82
>   Error:  Received unexpected error:
>   Expected 'rldo HWlloe', got 'olldolr WeH'
>   Test:   TestShuffle
> --- FAIL: TestShuffle (0.00s)
> 
> dh_auto_test: error: cd _build && go test -vet=off -v -p 16 github.com/go-
> task/slim-sprig returned exit code 1



Thanks!

Chris

Bug#938929: Dependency problem with iptables and libvirt-daemon-system

[Diederik de Haas]

On 26 Jul 2023 12:24:00 + Patrick Schleizer  wrote:
> libvirt upstream no longer depends on iptables for years.
> 
> source:
> https://gitlab.com/libvirt/libvirt/-/issues/406#note_1176654618
> 
> Should be trivial and safe to switch to nftables?

Next to the Build-Depends on iptables, there's also an explicit Depends added 
to the libvirt-daemon-system binary package.

I think it would be good to switch both to nftables, especially now that we're 
(still) in the middle of the Trixie development cycle. Or at least add 
nftables as (preferred) optional dependency to iptables.
*If* any issues pop up, there's plenty of time to fix it.

Now almost 5 years ago, the iptables package added the following to its 
Description: "The iptables/xtables framework has been replaced by nftables. 
You should consider migrating now."

signature.asc
Description: This is a digitally signed message part.

Bug#1057735: RM: r-cran-parsetools -- ROM; Unmaintained upstream, not needed in Debian

[Andreas Tille]

Package: ftp.debian.org
Severity: normal
User: ftp.debian@packages.debian.org
Usertags: remove
X-Debbugs-Cc: r-cran-parseto...@packages.debian.org, 994...@bugs.debian.org, 
debia...@lists.debian.org
Control: affects -1 + src:r-cran-parsetools

Hi ftpmasters,

since you have closed #1057658 by removing r-cran-testextra (thank you
for this) we can now remove r-cran-parsetools which would close bug
#994847 requesting the removal of this package which is unmaintained and
not needed in Debian any more.

Kind regards and thanks for working as ftpmaster
Andreas.

Bug#1054657: Transition seems to be blocked (Was: Bug#1054657: transition: r-bioc-biocgenerics)

[Adrian Bunk]

On Thu, Dec 07, 2023 at 04:09:28PM +0100, Andreas Tille wrote:
>...
> Am Thu, Dec 07, 2023 at 01:37:02PM -0100 schrieb Graham Inggs:
>...
> > Also, why do r-bioc-netsam and r-bioc-org.hs.eg.db not even appear on
> > the tracker?
> 
> I was always wondering about this but I have no clue.  r-bioc-go.db is
> the third example in this row.  I was updating these in past transitions
> manually which is IMHO no big harm - but I simply don't understand.

Finding the root cause would be investigating the question why no 
dependency on r-api-bioc-* is generated for them.

Either that's not required and the packages are technically not part of 
the transition, or there is an (RC) bug that should be fixed.

> Kind regards
> Andreas.
>...

cu
Adrian

Bug#1049459: reverse dependencies

[Thorsten Alteholz]

Hi Charles,

On 07.12.23 12:17, Charles Plessy wrote:

I just submitted bugs against courier and jool.  Can I ask you to fix
node-mime-types?  You are Uploader of it…


oh, my last upload was years ago. But I will try to fix it this weekend ...


Looking at the source code, it seems that node-mime-types does not need
mime-support at all.  But if it does please build depend on media-types
instead.


Ok, thanks, this info helps.

  Thorsten

Bug#1057734: dahdi-dkms: Update to v3.3.0 and re-enable wctdm for TDM400P hardware

[Russ Dill]

Package: dahdi-dkms
Version: 1:3.1.0+git20230717~dfsg-5
Severity: wishlist

Dear Maintainer,

I lost support for my TDM400P when updating to v3.1.0 as upstream had removed
the wctdm module. v3.3.0 brings it back, so an update to that version along
with re-enabling the module in dkms.conf.in would be greatly appreciated.

-- System Information:
Debian Release: trixie/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.5.0-5-amd64 (SMP w/2 CPU threads; PREEMPT)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages dahdi-dkms depends on:
ii  dkms   3.0.12-1
ii  dpkg-dev   1.22.1
ii  gawk   1:5.2.1-2
ii  gcc4:13.2.0-2
ii  libc6-dev  2.37-13
ii  make   4.3-4.1

Versions of packages dahdi-dkms recommends:
ii  dahdi-linux  1:3.1.0+git20230717~dfsg-5

dahdi-dkms suggests no packages.

-- no debconf information

Bug#1057679: lvm2: LVM cache gets marked completely dirty on every boot when used for filesystem root

[Bastian Blank]

On Thu, Dec 07, 2023 at 12:30:20PM +1000, progserega wrote:
>* I create logical volume 'root_deb' on hdd and its writeback cache on ssd 
> (nvme). And also I create logical volume 'home' and its cache on nvme. 
>* All works. But after reboot PC - I get big value CacheDirtyBlocks for 
> root_deb logical volume. After some tome (~30 minutes) cache synced - and it 
> work again propertly. But next reboot - get big dirty value for root_deb 
> again. For 'home' no such bug. Only for root logical volume.
>* I think that dirty value after reboot do not big (~12 Gb) - as in my 
> situation.

I assume this happens because the blockdevice is not cleanly unmounted
during shutdown.  Please test "dracut" as initramfs generator.  This
should support a shutdown mode that does not have that problem.

Bastian

-- 
No one wants war.
-- Kirk, "Errand of Mercy", stardate 3201.7

Bug#1025830: beauti2 fails to start

[Andreas Tille]

Hi,

Am Sun, Dec 18, 2022 at 03:15:28PM +0100 schrieb Pierre Gruet:
> Control: tags -1 help
> 
> Hello,
> 
> I tried to investigate further, I feel a window should appear and the action
> of the user is expected, yet I don't see anything except the initial
> "Initializing BEAUti..." GUI.
> My knowledge of jdb did not allow me to understand further what is going on.

I tried to verify the issue with the latest uploaded beast2-mcmc and get:

$ beauti2
Loading package BEAST.base v2.7.6

as well as the very small "Initializing BEAUti..." window.

So this issue persists and some help to track this down would be really
appreciated.

Kind regards
Andreas.

-- 
http://fam-tille.de

Bug#1057688: [Aptitude-devel] Bug#1057688: aptitude: Stray input on window click when running under tmux

[Axel Beckert]

Hi Sven,

Sven Joachim via Aptitude-devel wrote:
> Debian ncurses maintainer here, bringing the ncurses upstream developer
> into the loop.

Thanks for that!

> In addition to aptitude, mouse support is also broken in dialog(1) under
> tmux.
>
> > Maybe this bug should instead be assigned to ncurses?
> 
> Probably should be reassigned to ncurses-base, but let's first see what
> Thomas has to say about it.

JFTR: If it turns out as a bug which indeed needs not (only) to be
fixed in ncurses, it's likely not in aptitude but in libcwidget4. (The
separation stems from times where aptitude still also had a GUI
frontend.)

P.S.: Thanks to Thomas for fixing the recent ncurses issues (htop,
etc.) so quickly at upstream!

Regards, Axel
-- 
 ,''`.  |  Axel Beckert , https://people.debian.org/~abe/
: :' :  |  Debian Developer, ftp.ch.debian.org Admin
`. `'   |  4096R: 2517 B724 C5F6 CA99 5329  6E61 2FF9 CD59 6126 16B5
  `-|  1024D: F067 EA27 26B9 C3FC 1486  202E C09E 1D89 9593 0EDE

Bug#1057651: ncurses-doc: cross references in manpages are broken

[Sven Joachim]

On 2023-12-06 20:21 -0500, Thomas Dickey wrote:

> On Wed, Dec 06, 2023 at 07:18:55PM -0500, Thomas Dickey wrote:
>> On Wed, Dec 06, 2023 at 05:26:35PM +0100, Sven Joachim wrote:
>> > Package: ncurses-doc
>> > Version: 6.4+20231121-1
>> >
>> > References to other manpages, e.g. in the "SEE ALSO" section, do no
>> > longer work correctly.
>> >
>> > ,
>> > | $ man terminfo_variables | grep -A1 "SEE ALSO"
>> > | SEE ALSO
>> > |curses(3X), curs_terminfo(3X), curs_threads(3X), terminfo(5)
>> > `
>> >
>> > Compare that with the correct references in ncurses-doc 6.4-4 (bookworm):
>> >
>> > ,
>> > | $ man terminfo_variables | grep -A1 "SEE ALSO"
>> > | SEE ALSO
>> > |ncurses(3NCURSES), terminfo(3NCURSES), threads(3NCURSES), 
>> > terminfo(5).
>> > `
>>
>> I hadn't noticed that (I had to make other fixes to get the filenames
>> to work after Branden's changes in the NAME section, but overlooked this 
>> part).
>>
>> > Bisection revealed that (at least for the manpage in question) the
>> > formatting changes in the 20231001 patchlevel triggered the problem.
>> > The man/make_sed.sh script most likely needs to be adjusted, it has not
>> > seen any changes since the 20230625 patchlevel.
>>
>> yes... it's that "\%" pair (will fix)
>
> something like this:
>
> --- man/make_sed.sh   2023/11/25 14:31:18 1.18
> +++ man/make_sed.sh   2023/12/07 01:16:43
> @@ -76,9 +76,10 @@
>   $UPPER
>
>  echo "# Do the embedded references"
> -sed  -e 's/ +sed  -e 's/ + -e 's/\\%   -e 's/  /fP(/' \
> - -e 's/  /)\/fB/' \
> + -e 's/  /)\/fB%/' \
>   -e 's/  /fP(/' \
>   -e 's/\/$/)\//' \
>   $UPPER

Thanks, that seems to work.  I'll wait for this weekend's patchlevel
before taking action.

Cheers,
   Sven

Bug#1057688: aptitude: Stray input on window click when running under tmux

[Sven Joachim]

Hi,

Debian ncurses maintainer here, bringing the ncurses upstream developer
into the loop.

On 2023-12-06 22:28 -0700, Antonio Russo wrote:

> Package: aptitude
> Version: 0.8.13-5
> Severity: normal
> X-Debbugs-Cc: aeru...@aerusso.net
>
> Dear maintainer,
>
> If I run aptitude inside xterm, and click on an aptitude TUI element (say, a 
> particular
> package), that package will be selected.  If, instead, I am running aptitude 
> inside tmux,
> and I click on said element, it appears many garbage characters are sent to 
> aptitude,
> including probably m and M, (the symptom is the automatic install state of 
> packages changes).
>
> If I manually set TERM=xterm inside the tmux window, everything works.  
> Alternatively, outside
> of tmux, if I set TERM=tmux-256color I get the same bad behavior in aptitude.
>
> If I downgrade all ncurses packages to 6.4+20231016, I don't get this
> behavior.

The culprit is the addition of xterm+sm+1006 (xterm SGR-mouse) to the
tmux/tmux-256color terminfo entries in the ncurses 20231028 patchlevel.
In addition to aptitude, mouse support is also broken in dialog(1) under
tmux.

> Maybe this bug should instead be assigned to ncurses?

Probably should be reassigned to ncurses-base, but let's first see what
Thomas has to say about it.

Cheers,
   Sven

Bug#1042129: jruby: FTBFS: [ERROR] /<>/core/src/main/java/org/jruby/ext/strscan/RubyStringScanner.java:[653,34] error: cannot find symbol

[Miguel Landaeta]

On Thu, Dec 7, 2023 at 3:46 PM Jérôme Charaoui  wrote:
>
> For the record, the upload is ready to go. I'm now only waiting for a
> new build-dependency to pass through NEW, jruby-mavengem.
>

Sounds great, I'll take a look at the new package. Thanks for working
on the 9.4 release.

On my side in the meantime, I recently have been refreshing and
updating several jruby build-dependencies like jnr-* package and a few
other related packages.

Bug#1057733: libprelude FTCBFS: confuses build and host compiler flags

[Helmut Grohne]

Source: libprelude
Version: 5.2.0-5.2
User: debian-cr...@lists.debian.org
Usertags: ftcbfs

libprelude started failing to cross build again. This time around it is
caused by PAC/BTI as that's adding architecture specific compiler flags.
Confusion of compiler flags earlier was harmless and now causes a build
failure. I'm attaching a patch for your convenience.

Helmut
--- libprelude-5.2.0.orig/configure.ac
+++ libprelude-5.2.0/configure.ac
@@ -755,12 +755,18 @@
 fi
 
 
+if test "$cross_compiling" = "yes"; then
+  CFLAGS_FOR_BUILD="${CFLAGS_FOR_BUILD-}"
+else
+  CFLAGS_FOR_BUILD="${CFLAGS_FOR_BUILD-$CFLAGS}"
+fi
 
 dnl **
 dnl * Setup build variable   *
 dnl **
 
 AC_SUBST(CFLAGS)
+AC_SUBST(CFLAGS_FOR_BUILD)
 AC_SUBST(PCFLAGS)
 AC_SUBST(CPPFLAGS)
 AC_SUBST(LDFLAGS)
--- libprelude-5.2.0.orig/src/libprelude-error/Makefile.am
+++ libprelude-5.2.0/src/libprelude-error/Makefile.am
@@ -46,7 +46,7 @@
 # It is correct to use $(CC_FOR_BUILD) here.  We want to run the
 # program at build time.
 mkerrcodes: mkerrcodes.c mkerrcodes.h Makefile
-	$(CC_FOR_BUILD) $(CFLAGS) -I. -I$(srcdir) -o $@ $(srcdir)/mkerrcodes.c
+	$(CC_FOR_BUILD) $(CFLAGS_FOR_BUILD) -I. -I$(srcdir) -o $@ $(srcdir)/mkerrcodes.c
 
 code-from-errno.h: mkerrcodes Makefile
 	./mkerrcodes | LANG="" $(AWK) -f $(srcdir)/mkerrcodes2.awk >$@

Bug#1057732: utfcpp: please update to 4.0.1

[David Bremner]

Source: utfcpp
Version: 3.2.5-1
Severity: important

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Apologies for the inflated severity, but it looks like utfcpp 3.2.5 is what is 
breaking
the ledger build [1]

[1]: https://github.com/ledger/ledger/issues/2302


- -- System Information:
Debian Release: trixie/sid
  APT prefers testing-debug
  APT policy: (500, 'testing-debug'), (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 6.5.0-4-amd64 (SMP w/20 CPU threads; PREEMPT)
Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_CA:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEkiyHYXwaY0SiY6fqA0U5G1WqFSEFAmVx7vIACgkQA0U5G1Wq
FSHbTA/9HZVMDpb1wvFmzVVnfK1Jm21KAwZUqA8pH8ZhwmbfcDx1NRG0HY2ey9hT
Cf5qDOewnYhfVyifkuFxrQbhrAmuoPzlMWWNAFtw7ngGorwPPl2ApZk1OD0SjTbn
0Lz1hO7gg2nEuKuVrSLr36NYh3JvsMVE8sKOtvq1GX0h8pojDI3BIZp1+XmmFMDS
LQQOnt+5/bWhFerd5sedhLvcl0PTqa8rLWUROYtlIDfTH2o29l7IopL3+Cw76ruy
bIBe4M8mjwkDQfH9INB2Fq+tD+ToGPk2asCk2rx7B0OtZZ4HleXstHdi6urQBaUL
URtyAaHujzPPTPkWrsZg2rG7FUHXL3b0nvRAdVv7rTUP8ErXrBEwnCY1bSBXktTp
hV8OxklLctrpfqIi5oDkajeiaa3I94lEVmIBvRY8bjUn7vx1ZWud0Qd/FVt1BBjB
92Tos0vG0vx+tM5vjN/NDwNueIjiuxS+M5wzzhq5s8h5p9Mgwr5cl5WcgKpFjHEl
wuvr7e6d4WhDj4+MgahBzWOXuYmOcppUkRrINFlxbFuZ50CTBrQ//UeiEL0jBrik
nqV0cnT4qmA5qNZOksOgxIA1obo+bhGUHZu15g+qaaNvXWdpRUbELqiJc363pw7s
u6f32URKUtQrdxhFAV/k8x6LkrdyT7qVz0R4Ow71C5eAu1xMc+s=
=p2HZ
-END PGP SIGNATURE-

Bug#1055758: opensmtpd: OpenSMTPD release in stable (bookworm) is useless due to #1037359

[Ryan Kavanagh]

On Thu, Nov 16, 2023 at 12:36:16PM -0500, Ryan Kavanagh wrote:
> I plan on uploading OpenSMTPD 7.4.0p2 to Debian backports in the near
> future

7.4.0p1 is now available from stable-backports.

Best,
Ryan

-- 
|)|/  Ryan Kavanagh  | 4E46 9519 ED67 7734 268F
|\|\  https://rak.ac | BD95 8F7B F8FC 4A11 C97A


signature.asc
Description: PGP signature

Bug#1057260: iwlwifi: `N' invalid for parameter `enable_ini'

[Salvatore Bonaccorso]

Hi Rémi,

On Thu, Dec 07, 2023 at 03:29:15PM +0100, Rémi Letot wrote:
> Salvatore Bonaccorso  writes:
> 
> > On Thu, Dec 07, 2023 at 10:36:58AM +0100, Rémi Letot wrote:
> >> 
> >> Hello,
> >> 
> >> /etc/modprobe.d/iwlwifi.conf contains one line:
> >> 
> >> options iwlwifi enable_ini=N
> >> 
> >> 
> >> ~ $ LANG=C dpkg -S iwlwifi.conf
> >> dpkg-query: no path found matching pattern *iwlwifi.conf*
> >> 
> >> I can't remember creating that file myself, but it's from two years ago,
> >> so it's possible...
> >> 
> >> ~ $ ls -l /etc/modprobe.d/iwlwifi.conf
> >> -rw-r--r--   1 root   root   29 2021-08-02  2021 
> >> /etc/modprobe.d/iwlwifi.conf
> >
> > I guess so it was created manually some time ago then. No package
> > provides it, and I found via short search that some forumposts or
> > articles suggest the enable_ini=N value for people having instability
> > with iwlwifi.
> 
> Indeed, I found my installation notes for that laptop, and I manually
> created the file.
> 
> I removed it, rebooted, and iwlwifi now works fine on 6.5.0-5

Thanks for the confirmation!

Regards,
Salvatore

Bug#1057729: pam FTCBFS: passes host flags to build compiler

[Sam Hartman]

> "Helmut" == Helmut Grohne  writes:
Helmut> Can I leave this up to you? To verify the cross build
Helmut> failure, please use amd64 or arm64 as host
Helmut> architecture. These are the only ones with
Helmut> architecture-specific compiler flags.

Up to who?  Andreas?  If so, I will let him speak for himself.  If you
are asking me to take this on, I'd love to but realistically I do not
have the time.

Bug#1042129: jruby: FTBFS: [ERROR] /<>/core/src/main/java/org/jruby/ext/strscan/RubyStringScanner.java:[653,34] error: cannot find symbol

[Jérôme Charaoui]

Le 2023-11-25 à 06 h 30, Miguel Landaeta a écrit :

On Sat, Nov 25, 2023 at 12:29 AM Jérôme Charaoui  wrote:


[...]

I've been working on a 9.4 release, you can see the progress here:
https://salsa.debian.org/lavamind/jruby

I plan to upload this version to experimental within a few days, I still
have some minor issues with the testsuite to iron out before.


Excellent, that's good to hear.
There is no point then just backporting the fix if you are close to
finishing preparing an upload.

Let me know if there is something else I can help with.
I think I'll take a look at some jnr-* dependencies packages that
could use a new upstream release and/or bugfixes.


For the record, the upload is ready to go. I'm now only waiting for a 
new build-dependency to pass through NEW, jruby-mavengem.

Bug#1054657: Transition seems to be blocked (Was: Bug#1054657: transition: r-bioc-biocgenerics)

[Andreas Tille]

Am Thu, Dec 07, 2023 at 04:09:28PM +0100 schrieb Andreas Tille:
> I'll take this
> occurence as a reason to fail with an error in dh-r to avoid such cases
> in future.

Done in

   
https://salsa.debian.org/r-pkg-team/dh-r/-/commit/e4c348832b3d99ba7bc8f7670085b9b21323f7b6

The check could be even more strict but should be sufficient for those
practical cases that occured in the past.

Thanks for Graham for spotting the issue

   Andreas.

-- 
http://fam-tille.de

Bug#1057730: python-jellyfish ftbfs in unstable (dpkg-buildpackage -B)

[Matthias Klose]

Package: src:python-jellyfish
Version: 0.10.0-2
Severity: serious
Tags: sid trixie

python-jellyfish ftbfs in unstable


[...]
   debian/rules override_dh_installdocs
make[1]: Entering directory '/<>'
dh_installdocs -ppython-jellyfish-doc --doc-main-package=python3-jellyfish
dh_installdocs: warning: All requested packages have been excluded (e.g. 
via a Build-Profile or due to architecture restrictions).

dh_installdocs --remaining-packages
mv debian/python-jellyfish-doc/usr/share/doc/python3-jellyfish/site 
debian/python-jellyfish-doc/usr/share/doc/python3-jellyfish/html
mv: cannot stat 
'debian/python-jellyfish-doc/usr/share/doc/python3-jellyfish/site': No 
such file or directory

make[1]: *** [debian/rules:28: override_dh_installdocs] Error 1

Bug#1057706: transition: dpdk

[Luca Boccassi]

On Thu, 07 Dec 2023 13:05:25 + Luca Boccassi 
wrote:
> On Thu, 07 Dec 2023 11:41:04 + Luca Boccassi 
> wrote:
> > Package: release.debian.org
> > Severity: normal
> > User: release.debian@packages.debian.org
> > Usertags: transition
> > X-Debbugs-CC:
pkg-dpdk-de...@lists.alioth.debian.org z...@debian.org
> > 
> > Hello Release Team,
> > 
> > We have prepared the src:dpdk 23.11 ABI transition.
> > 
> > src:dpdk reverse dependencies are collectd, uhd, openvswitch.
> > openvswitch needs to changes, uhd needed a patch but it has already
> > been uploaded in unstable and on its way to testing, and collectd
has
> > an NMU in the delayed/3 queue as of now.
> > 
> > With this version we are dropping i386 builds. openvswitch already
> > dropped i386, uhd never used it, and collectd is fixed by the nmu.
> > We will file an rm bug once the package is in unstable.
> > 
> > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057146
> > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057200
> 
> Collectd is only a Recommends, not a dependency, and it currently
FTBFS
> for unrelated reasons:
> 
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057712
> 
> The dependency is dropped in git main, so whenever that is fixed, it
> will be dropped too, so I'd suggest to ignore it for the transition
> purpose, as it won't stop anything from being migrated/removed.

collectd was just uploaded to fix the FTBFS and drop the i386 dep:

https://tracker.debian.org/news/1483817/accepted-collectd-5120-15-source-into-unstable/

so even that can be binNMU'ed to get the new Recommends.

-- 
Kind regards,
Luca Boccassi


signature.asc
Description: This is a digitally signed message part

Bug#1057146: collectd: drop build-dependency on libdpdk-dev on i386

[Luca Boccassi]

On Thu, 7 Dec 2023 at 14:44, Bernd Zeimetz  wrote:
>
> On Thu, 2023-12-07 at 12:58 +, Luca Boccassi wrote:
> > On Thu, 7 Dec 2023 at 12:49, Luca Boccassi  wrote:
> > >
> > > On Thu, 7 Dec 2023 at 12:34, Bernd Zeimetz  wrote:
> > > >
> > > > On 2023-12-07 13:22, Luca Boccassi wrote:
> > > >
> > > > > That's a pre-existing issue that happens before any of my
> > > > > changes as
> > > > > you can see in the previous Salsa commit, which was made by
> > > > > somebody
> > > > > else:
> > > > >
> > > > > https://salsa.debian.org/debian/pkg-collectd/-/jobs/4917853
> > > >
> > > > yes. It still fails to build due to that, so your upload is
> > > > broken.
> > > > Again, please either remove or fix it.
> > >
> > > Actually, it fails to build even before that, at your last commit:
> > >
> > > https://salsa.debian.org/bluca/pkg-collectd/-/commit/b8563518a02bc841fb93c778e553f09e8f6ac659
> >
> > I've filed #1057712 for the FTBFS, cancelled the NMU and unblocked
> > the
> > transition. It's just a Recommends: anyway, so it will be solved
> > whenever it will be solved.
> >
>
> I've just uploaded collectd with the java plugin disabled on i386,
> libjvm has a missing symbol there and fails to link because of that.
>
> So your transition should be happy.

That's great, thank you very much

Bug#1054657: Transition seems to be blocked (Was: Bug#1054657: transition: r-bioc-biocgenerics)

[Andreas Tille]

Hi Graham,

Am Thu, Dec 07, 2023 at 01:37:02PM -0100 schrieb Graham Inggs:
> On Sun, 3 Dec 2023 at 07:21, Andreas Tille  wrote:
> > I have no idea how to work around this.
> 
> I found a workaround; demote pandoc from a Depends to a Recommends in
> the r-cran-rmarkdown package.  It seems that pandoc is not used for
> building, at least for r-bioc-biovizbase, -degnorm, -ioniser, scrnaseq
> and -tximeta, which I tried.

Thanks for the patch - applied and uploaded.
 
> Do you know why r-bioc-metagenomeseq is considered neither good nor
> bad in the tracker?

Argh, upstream has messed up DESCRIPTION/git_branch which we trust to
detect r-bioc-api.  This is fixed[1] and uploaded.  I'll take this
occurence as a reason to fail with an error in dh-r to avoid such cases
in future.

> Also, why do r-bioc-netsam and r-bioc-org.hs.eg.db not even appear on
> the tracker?

I was always wondering about this but I have no clue.  r-bioc-go.db is
the third example in this row.  I was updating these in past transitions
manually which is IMHO no big harm - but I simply don't understand.

Kind regards
Andreas.

[1] 
https://salsa.debian.org/r-pkg-team/r-bioc-metagenomeseq/-/blob/master/debian/patches/fix_git_branch.patch

-- 
http://fam-tille.de

Bug#1057729: pam FTCBFS: passes host flags to build compiler

[Helmut Grohne]

Source: pam
Version: 1.3.1-1
Severity: important
Justification: bootstrap set
User: debian-cr...@lists.debian.org
Usertags: ftcbfs
X-Debbugs-Cc: Andreas Henriksson 

Hi,

since we now enabled PAC/BTI flags, distinguishing build flags and host
flags has become important. pam already does this, but about four years
ago Andreas added a fix-autoreconf.patch that breaks this distinction.

In essence, I think Andreas meant to ensure that CFLAGS passed by a user
are not discarded but passed to actual build invocations and that's what
his patch does in effect.

Cross compilation poses the opposite requirement: Flags passed via
CFLAGS must not propagate to some of the compiler invocations, because
the compiler may be unable to understand them as is the case with e.g.
-mbranch-protection=standard.

I note that in a native build, configure.ac already sets
BUILD_CFLAGS=${CFLAGS}, so this assignment should be harmless for native
builds. If it really was, Andreas probably wouldn't have patched it, so
rather than simply reverting the patch, we should understand the problem
he was trying to solve and I quite obviously miss something important.

Can I leave this up to you? To verify the cross build failure, please
use amd64 or arm64 as host architecture. These are the only ones with
architecture-specific compiler flags.

Helmut

Bug#1057728: binutils-mingw-w64 FTBFS: test failures

[Helmut Grohne]

Source: binutils-mingw-w64
Version: 11+nmu1
Severity: serious
Tags: ftbfs

binutils-mingw-w64 fails to build from source in unstable on amd64. A
build ends as follows:

| Running target unix
| Using /usr/share/dejagnu/baseboards/unix.exp as board description file for 
target.
| Using /usr/share/dejagnu/config/unix.exp as generic interface file for target.
| Using /<>/upstream/binutils/testsuite/config/default.exp as 
tool-and-target-specific interface file.
| WARNING: Assuming target board is the local machine (which is probably wrong).
| You may need to set your DEJAGNU environment variable.
| Running 
/<>/upstream/binutils/testsuite/binutils-all/aarch64/aarch64.exp 
...
| Running 
/<>/upstream/binutils/testsuite/binutils-all/addr2line.exp ...
| Running /<>/upstream/binutils/testsuite/binutils-all/ar.exp ...
| FAIL: replacing non-deterministic member: (failed to replace file)
| FAIL: replacing SOURCE_DATE_EPOCH deterministic member: (failed to replace 
file)
| Running 
/<>/upstream/binutils/testsuite/binutils-all/arc/objdump.exp ...
| Running 
/<>/upstream/binutils/testsuite/binutils-all/arm/objdump.exp ...
| Running 
/<>/upstream/binutils/testsuite/binutils-all/bfin/objdump.exp ...
| Running 
/<>/upstream/binutils/testsuite/binutils-all/compress.exp ...
| Running /<>/upstream/binutils/testsuite/binutils-all/cxxfilt.exp 
...
| Running 
/<>/upstream/binutils/testsuite/binutils-all/debuginfod.exp ...
| Running /<>/upstream/binutils/testsuite/binutils-all/dlltool.exp 
...
| Running /<>/upstream/binutils/testsuite/binutils-all/elfedit.exp 
...
| Running 
/<>/upstream/binutils/testsuite/binutils-all/hppa/objdump.exp ...
| Running 
/<>/upstream/binutils/testsuite/binutils-all/i386/i386.exp ...
| Running /<>/upstream/binutils/testsuite/binutils-all/kvx/kvx.exp 
...
| Running 
/<>/upstream/binutils/testsuite/binutils-all/loongarch64/loongarch64.exp
 ...
| Running 
/<>/upstream/binutils/testsuite/binutils-all/m68k/objdump.exp ...
| Running 
/<>/upstream/binutils/testsuite/binutils-all/mips/mips.exp ...
| Running 
/<>/upstream/binutils/testsuite/binutils-all/nfp/objdump.exp ...
| Running /<>/upstream/binutils/testsuite/binutils-all/nm.exp ...
| Version /<>/build/i686-w64-mingw32/binutils/nm-new 
2.41.50.20231206
| Running /<>/upstream/binutils/testsuite/binutils-all/objcopy.exp 
...
| Version /<>/build/i686-w64-mingw32/binutils/objcopy 
2.41.50.20231206
| Running /<>/upstream/binutils/testsuite/binutils-all/objdump.exp 
...
| Version /<>/build/i686-w64-mingw32/binutils/objdump 
2.41.50.20231206
| Running /<>/upstream/binutils/testsuite/binutils-all/readelf.exp 
...
| Running 
/<>/upstream/binutils/testsuite/binutils-all/riscv/riscv.exp ...
| Running /<>/upstream/binutils/testsuite/binutils-all/size.exp ...
| Version /<>/build/i686-w64-mingw32/binutils/size 2.41.50.20231206
| Running /<>/upstream/binutils/testsuite/binutils-all/strings.exp 
...
| Running 
/<>/upstream/binutils/testsuite/binutils-all/update-section.exp ...
| Running 
/<>/upstream/binutils/testsuite/binutils-all/vax/objdump.exp ...
| Running 
/<>/upstream/binutils/testsuite/binutils-all/wasm32/wasm32.exp ...
| Running 
/<>/upstream/binutils/testsuite/binutils-all/windres/windres.exp 
...
| Running 
/<>/upstream/binutils/testsuite/binutils-all/x86-64/objects.exp ...
| Running 
/<>/upstream/binutils/testsuite/binutils-all/x86-64/x86-64.exp ...
| 
| === binutils Summary ===
| 
| # of expected passes133
| # of unexpected failures2
| # of untested testcases 12
| # of unsupported tests  22
| make[7]: *** [Makefile:1838: check-DEJAGNU] Error 1
| make[7]: Leaving directory '/<>/build/i686-w64-mingw32/binutils'
| make[6]: *** [Makefile:1577: check-am] Error 2
| make[6]: Leaving directory '/<>/build/i686-w64-mingw32/binutils'
| make[5]: *** [Makefile:1446: check-recursive] Error 1
| make[5]: Leaving directory '/<>/build/i686-w64-mingw32/binutils'
| make[4]: *** [Makefile:1579: check] Error 2
| make[4]: Leaving directory '/<>/build/i686-w64-mingw32/binutils'
| make[3]: *** [Makefile:4127: check-binutils] Error 2
| make[3]: Leaving directory '/<>/build/i686-w64-mingw32'
| make[2]: *** [Makefile:2524: do-check] Error 2
| make[2]: Leaving directory '/<>/build/i686-w64-mingw32'
| dh_auto_test: error: cd build/i686-w64-mingw32 && make -j1 check returned 
exit code 2
| make[1]: *** [debian/rules:117: override_dh_auto_test-arch] Error 25
| make[1]: Leaving directory '/<>'
| make: *** [debian/rules:61: binary] Error 2
| dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 
2

This is also observed by reproducible builds.
https://tests.reproducible-builds.org/debian/rbuild/unstable/amd64/binutils-mingw-w64_11+nmu1.rbuild.log.gz

Helmut

Bug#1057724: imvirt FTCBFS: confuses build and host

[Helmut Grohne]

Source: imvirt
Version: 0.9.6-11
Tags: patch
User: debian-cr...@lists.debian.org
Usertags: ftcbfs

imvirt fails to cross build from source, because it confuses build and
host in a number of occasions:
 * configure is run without the --host parameter thus defaulting to
   build.
 * debian/rules matches on host rather than build.
 * configure examines uname, which is host, while it should be examining
   host_alias and things derived from that.

I'm attaching a patch fixing all of that. Consider applying it.

Helmut
diff --minimal -Nru imvirt-0.9.6/debian/changelog imvirt-0.9.6/debian/changelog
--- imvirt-0.9.6/debian/changelog   2023-01-12 11:08:10.0 +0100
+++ imvirt-0.9.6/debian/changelog   2023-12-07 12:43:12.0 +0100
@@ -1,3 +1,10 @@
+imvirt (0.9.6-11.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix FTCBFS: Fix host versus build confusions. (Closes: #-1)
+
+ -- Helmut Grohne   Thu, 07 Dec 2023 12:43:12 +0100
+
 imvirt (0.9.6-11) unstable; urgency=medium
 
   * Adjust debian/watch to work again with GitHub.
diff --minimal -Nru imvirt-0.9.6/debian/patches/cross.patch 
imvirt-0.9.6/debian/patches/cross.patch
--- imvirt-0.9.6/debian/patches/cross.patch 1970-01-01 01:00:00.0 
+0100
+++ imvirt-0.9.6/debian/patches/cross.patch 2023-12-07 11:06:55.0 
+0100
@@ -0,0 +1,19 @@
+--- imvirt-0.9.6.orig/configure.in
 imvirt-0.9.6/configure.in
+@@ -6,6 +6,7 @@
+ AC_PREREQ(2.61)
+ AC_INIT(imvirt, 0.9.6, li...@ibh.de)
+ AM_INIT_AUTOMAKE
++AC_CANONICAL_HOST
+ AC_CONFIG_SRCDIR([helper/detect.c])
+ AC_CONFIG_HEADER([helper/config.h])
+ 
+@@ -30,7 +31,7 @@
+ 
+ # Check architecture
+ AC_MSG_CHECKING(x86 platform)
+-case `uname -m` in
++case $host_cpu in
+ x86_64) x86arch=true ;;
+ i686) x86arch=true ;;
+ *) x86arch=false ;;
diff --minimal -Nru imvirt-0.9.6/debian/patches/series 
imvirt-0.9.6/debian/patches/series
--- imvirt-0.9.6/debian/patches/series  2023-01-12 11:08:10.0 +0100
+++ imvirt-0.9.6/debian/patches/series  2023-12-07 11:02:59.0 +0100
@@ -1,3 +1,4 @@
 01-spelling-error.diff
 02-broken-sort.diff
 03-escaped-quotes.diff
+cross.patch
diff --minimal -Nru imvirt-0.9.6/debian/rules imvirt-0.9.6/debian/rules
--- imvirt-0.9.6/debian/rules   2023-01-12 11:08:10.0 +0100
+++ imvirt-0.9.6/debian/rules   2023-12-07 12:30:48.0 +0100
@@ -5,18 +5,15 @@
 %:
dh $@
 
-override_dh_auto_configure:
-   ./configure --prefix=/usr --libexec=/usr/lib
-
 override_dh_auto_test:
 
 override_dh_install:
dh_install
-ifneq (,$(findstring linux,$(DEB_BUILD_ARCH_OS)))
-ifneq (,$(findstring i386,$(DEB_BUILD_ARCH)))
+ifneq (,$(findstring linux,$(DEB_HOST_ARCH_OS)))
+ifneq (,$(findstring i386,$(DEB_HOST_ARCH)))
dh_install -pimvirt-helper "debian/tmp/usr/lib/imvirt/" "usr/lib/"
 endif
-ifneq (,$(findstring amd64,$(DEB_BUILD_ARCH)))
+ifneq (,$(findstring amd64,$(DEB_HOST_ARCH)))
dh_install -pimvirt-helper "debian/tmp/usr/lib/imvirt/" "usr/lib/"
 endif
 endif

Bug#1057726: icu FTCBFS: host compiler flags leak into build compiler invocation

[Helmut Grohne]

Source: icu
Version: 72.1-4
Tags: patch
User: debian-cr...@lists.debian.org
Usertags: ftcbfs

icu fails to cross build from source due to architecture-specific
compiler flags such as PAC/BTI having been added recently. It currently
passes host compiler flags to its native pass and that doesn't go well.
I'm attaching a patch for your convenience.

Helmut
diff --minimal -Nru icu-72.1/debian/changelog icu-72.1/debian/changelog
--- icu-72.1/debian/changelog   2023-10-20 17:44:53.0 +0200
+++ icu-72.1/debian/changelog   2023-12-07 09:16:20.0 +0100
@@ -1,3 +1,10 @@
+icu (72.1-4.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix FTCBFS: Differentiate build and host compiler flags. (Closes: #-1)
+
+ -- Helmut Grohne   Thu, 07 Dec 2023 09:16:20 +0100
+
 icu (72.1-4) unstable; urgency=medium
 
   [ Adrian Bunk  ]
diff --minimal -Nru icu-72.1/debian/rules icu-72.1/debian/rules
--- icu-72.1/debian/rules   2023-10-20 17:44:53.0 +0200
+++ icu-72.1/debian/rules   2023-12-07 09:16:19.0 +0100
@@ -35,7 +35,7 @@
 ifeq ($(DEB_BUILD_ARCH),$(DEB_HOST_ARCH))
dh_auto_configure -- --enable-static --disable-layoutex 
--disable-icu-config
 else
-   dh_auto_configure -B $(CURDIR)/build-native -- 
--host=$(DEB_BUILD_GNU_TYPE) --disable-layoutex --disable-icu-config
+   dpkg-architecture -a$(DEB_BUILD_ARCH) -f -c dh_auto_configure 
--reload-all-buildenv-variables -B $(CURDIR)/build-native -- --disable-layoutex 
--disable-icu-config
dh_auto_build -B $(CURDIR)/build-native
dh_auto_configure -- --enable-static 
--with-cross-build=$(CURDIR)/build-native
 endif

Bug#1057727: openmpi-bin is wrongly marked Multi-Arch: foreign

[Helmut Grohne]

Package: openmpi-bin
Version: 3.1.3-1
Severity: important
User: debian-cr...@lists.debian.org
Usertags: ftcbfs
Control: affects -1 + src:combblas

openmpi-bin is currently marked Multi-Arch: foreign as a result of
#901874. I note that none of the solutions for that that I offered
involved marking a package containing mpicc Multi-Arch: foreign. The fix
to that bug was an error and is now causing further problems.

More specifically, cmake's FindMPI.cmake is now finding that mpicc
"works" (except that it gets us wrong include directories) and since
mpicc works, it skips over the working detection using pkg-config thus
failing to find a working MPI implementation. If openmpi-bin were not
Multi-Arch: foreign, mpicc would fail (rather than produce broken
results) and cause FindMPI to successfully detect MPI using pkg-config.

My last mail to that earlier bug said:

| So you have a choice here:
| 
| A. Ship -mpicc and make everyone use AC_PATH_TOOL over
|AC_PATH_PROG.
| 
| B. Make libopenmpi-dev Multi-Arch: no and let mpicc operate for whatever
|architecture it was installed for.
| 
| C. Ignore the problem and move to pkg-config directly.

I think we're effectively moving towards option C now, but there is a
complication. How do we decide whether try mpicc or pkg-config first? If
we try mpicc first, we end up risking to use the broken version of
openmpi-bin that doesn't work but looks like it works. So we either need
to convince everyone to try pkg-config before mpicc (which cmake's
FindMPI doesn't do at present) or we need to ensure that mpicc fails
reliably when it does not work. I'm effectively asking for the latter
here.

Helmut

Bug#1057725: android-platform-system-extras FTCBFS: uses the build architecture pkg-config

[Helmut Grohne]

Source: android-platform-system-extras
Version: 10.0.0+r36+ds-2.1
Tags: patch
User: debian-cr...@lists.debian.org
Usertags: ftcbfs

android-platform-system-extras fails to cross build from source, because
debian/rules hard codes the build architecture pkg-config. I'm attaching
a patch for your convenience.

Helmut
diff --minimal -Nru 
android-platform-system-extras-10.0.0+r36+ds/debian/changelog 
android-platform-system-extras-10.0.0+r36+ds/debian/changelog
--- android-platform-system-extras-10.0.0+r36+ds/debian/changelog   
2023-01-18 16:40:05.0 +0100
+++ android-platform-system-extras-10.0.0+r36+ds/debian/changelog   
2023-12-07 14:46:11.0 +0100
@@ -1,3 +1,10 @@
+android-platform-system-extras (10.0.0+r36+ds-2.2) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix FTCBFS: Use the host pkg-config. (Closes: #-1)
+
+ -- Helmut Grohne   Thu, 07 Dec 2023 14:46:11 +0100
+
 android-platform-system-extras (10.0.0+r36+ds-2.1) unstable; urgency=medium
 
   * Non-maintainer upload.
diff --minimal -Nru android-platform-system-extras-10.0.0+r36+ds/debian/rules 
android-platform-system-extras-10.0.0+r36+ds/debian/rules
--- android-platform-system-extras-10.0.0+r36+ds/debian/rules   2023-01-18 
16:39:59.0 +0100
+++ android-platform-system-extras-10.0.0+r36+ds/debian/rules   2023-12-07 
14:46:09.0 +0100
@@ -2,11 +2,13 @@
 
 include /usr/share/dpkg/architecture.mk
 include /usr/share/dpkg/pkg-info.mk
+-include /usr/share/dpkg/buildtools.mk
+PKG_CONFIG ?= pkg-config
 
 # Security Hardening
 export DEB_BUILD_MAINT_OPTIONS = hardening=+all
 export DEB_LDFLAGS_MAINT_APPEND = -fPIC
-export DEB_CPPFLAGS_MAINT_APPEND = -I/usr/include/android -DNDEBUG `pkg-config 
--cflags squashfuse`
+export DEB_CPPFLAGS_MAINT_APPEND = -I/usr/include/android -DNDEBUG 
`$(PKG_CONFIG) --cflags squashfuse`
 export OUT_DIR = debian/out
 
 lib%.so: debian/lib%.mk

Bug#1057279: xtrlock option to verify password via a subprocess

[Matthew Vernon]

Hi,

On 02/12/2023 15:23, Simon Tatham wrote:


I run xtrlock on a machine which doesn't store all its passwd/shadow
entries locally. So xtrlock is unable to verify my password by the usual
method.

To get around this, I added a feature which replaces the passwd/shadow
based check with a user-provided subprogram. xtrlock pipes the password
into the subprogram's standard input, and unlocks the screen if the
program exits with a success status.


Thanks for this and the attached patches; I think it's a useful addition 
to xtrlock.



Both patches are attached. At the moment, they lack documentation, and
also the hourglass-pointer patch is unconditional rather than
configurable. I'm prepared to do extra polishing effort if it's useful!


I think both docs and making the hourglass optional would be good, 
please; I'm sorry I've not done anything more useful in terms of review 
yet, but I'm currently a bit swamped, and I thought at least some reply 
would be better than continued silence!


Regards,

Matthew

Bug#1057146: collectd: drop build-dependency on libdpdk-dev on i386

[Bernd Zeimetz]

On Thu, 2023-12-07 at 12:58 +, Luca Boccassi wrote:
> On Thu, 7 Dec 2023 at 12:49, Luca Boccassi  wrote:
> > 
> > On Thu, 7 Dec 2023 at 12:34, Bernd Zeimetz  wrote:
> > > 
> > > On 2023-12-07 13:22, Luca Boccassi wrote:
> > > 
> > > > That's a pre-existing issue that happens before any of my
> > > > changes as
> > > > you can see in the previous Salsa commit, which was made by
> > > > somebody
> > > > else:
> > > > 
> > > > https://salsa.debian.org/debian/pkg-collectd/-/jobs/4917853
> > > 
> > > yes. It still fails to build due to that, so your upload is
> > > broken.
> > > Again, please either remove or fix it.
> > 
> > Actually, it fails to build even before that, at your last commit:
> > 
> > https://salsa.debian.org/bluca/pkg-collectd/-/commit/b8563518a02bc841fb93c778e553f09e8f6ac659
> 
> I've filed #1057712 for the FTBFS, cancelled the NMU and unblocked
> the
> transition. It's just a Recommends: anyway, so it will be solved
> whenever it will be solved.
> 

I've just uploaded collectd with the java plugin disabled on i386,
libjvm has a missing symbol there and fails to link because of that.

So your transition should be happy.


Bernd


-- 
 Bernd ZeimetzDebian GNU/Linux Developer
 http://bzed.dehttp://www.debian.org
 GPG Fingerprint: ECA1 E3F2 8E11 2432 D485  DD95 EB36 171A 6FF9 435F

Bug#1054353: Removal notice: obsolete

[Ilias Tsitsimpis]

Control: clone -1 -2
Control: reassign -2 ftp.debian.org
Control: retitle -2 RM: haskell-tree-monad -- ROM; obsolete
Control: severity -2 normal

On Sun, Oct 22, 2023 at 04:25PM, Ilias Tsitsimpis wrote:
> I intend to remove this package:
> 
>   * The current version FTBFS
>   * It's not part of the latest Stackage LTS

Dear FTP masters, please remove haskell-tree-monad from unstable.

-- 
Ilias

Bug#1057260: iwlwifi: `N' invalid for parameter `enable_ini'

[Rémi Letot]

Salvatore Bonaccorso  writes:

> On Thu, Dec 07, 2023 at 10:36:58AM +0100, Rémi Letot wrote:
>> 
>> Hello,
>> 
>> /etc/modprobe.d/iwlwifi.conf contains one line:
>> 
>> options iwlwifi enable_ini=N
>> 
>> 
>> ~ $ LANG=C dpkg -S iwlwifi.conf
>> dpkg-query: no path found matching pattern *iwlwifi.conf*
>> 
>> I can't remember creating that file myself, but it's from two years ago,
>> so it's possible...
>> 
>> ~ $ ls -l /etc/modprobe.d/iwlwifi.conf
>> -rw-r--r--   1 root   root   29 2021-08-02  2021 
>> /etc/modprobe.d/iwlwifi.conf
>
> I guess so it was created manually some time ago then. No package
> provides it, and I found via short search that some forumposts or
> articles suggest the enable_ini=N value for people having instability
> with iwlwifi.

Indeed, I found my installation notes for that laptop, and I manually
created the file.

I removed it, rebooted, and iwlwifi now works fine on 6.5.0-5

Thanks a lot,
-- 
Rémi

Bug#1054657: Transition seems to be blocked (Was: Bug#1054657: transition: r-bioc-biocgenerics)

[Graham Inggs]

Hi Andreas

On Sun, 3 Dec 2023 at 07:21, Andreas Tille  wrote:
> I have no idea how to work around this.

I found a workaround; demote pandoc from a Depends to a Recommends in
the r-cran-rmarkdown package.  It seems that pandoc is not used for
building, at least for r-bioc-biovizbase, -degnorm, -ioniser, scrnaseq
and -tximeta, which I tried.

Do you know why r-bioc-metagenomeseq is considered neither good nor
bad in the tracker?
Also, why do r-bioc-netsam and r-bioc-org.hs.eg.db not even appear on
the tracker?

Regards
Graham


--- r-cran-rmarkdown-2.25+dfsg/debian/control
+++ r-cran-rmarkdown-2.25+dfsg/debian/control
@@ -37,10 +37,9 @@
  libjs-prettify,
  r-cran-jquerylib,
  fonts-font-awesome,
- pandoc,
  r-cran-shiny,
  node-html5shiv
-Recommends: ${R:Recommends}
+Recommends: ${R:Recommends}, pandoc
 Suggests: ${R:Suggests}
 Description: convert R markdown documents into a variety of formats
  R Markdown is a framework for creating documents that mix R code with

Bug#1057722: Removal notice: obsolete

[Ilias Tsitsimpis]

Source: haskell-tidal
Version: 1.7.10-1
Severity: serious

I intend to remove this package:

  * It has no rev dependencies
  * Newer versions depend on libraries not available in Debian (tidal-link)

If you believe we should keep this package in Debian, please close this
bug report.

-- 
Ilias

Bug#1057721: openpyxl: please make the build reproducible

[Chris Lamb]

Source: openpyxl
Version: 3.1.2+dfsg-4
Severity: wishlist
Tags: patch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: timestamps
X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org

Hi,

Whilst working on the Reproducible Builds effort [0], we noticed that
openpyxl could not be built reproducibly.

This is because the documentation embedded the current build year in
its documentation.

However, a patch is attached that seeds this date from SOURCE_DATE_EPOCH
if available.

 [0] https://reproducible-builds.org/


Best wishes,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-
--- a/debian/patches/reproducibility_docs.patch 1970-01-01 01:00:00.0 
+0100
--- b/debian/patches/reproducibility_docs.patch 2023-12-07 14:25:29.745194613 
+
@@ -0,0 +1,23 @@
+Description: Make the docs reproducible
+Author: Chris Lamb 
+Last-Update: 2023-12-07
+
+--- openpyxl-3.1.2+dfsg.orig/doc/conf.py
 openpyxl-3.1.2+dfsg/doc/conf.py
+@@ -68,9 +68,14 @@ master_doc = 'index'
+ 
+ # General information about the project.
+ project = u'openpyxl'
+-from datetime import date
++import os
++import time
++import datetime
++build_date = datetime.datetime.utcfromtimestamp(
++int(os.environ.get('SOURCE_DATE_EPOCH', time.time()))
++)
+ 
+-copyright = u'2010 - {0}, {1}'.format(date.today().year, openpyxl.__author__)
++copyright = u'2010 - {0}, {1}'.format(build_date.year, openpyxl.__author__)
+ 
+ # The version info for the project you're documenting, acts as replacement for
+ # |version| and |release|, also used in various other places throughout the
--- a/debian/patches/series 2023-12-07 14:07:11.622651360 +
--- b/debian/patches/series 2023-12-07 14:24:37.929086483 +
@@ -2,3 +2,4 @@
 python3p12_compat.patch
 privacy.patch
 reproducibility.patch
+reproducibility_docs.patch

Bug#1057697: [Pkg-javascript-devel] Bug#1057697: Bug#1057697: nodejs:please enable loong64

[Jérémy Lal]

Le jeu. 7 déc. 2023 à 12:27, Jérémy Lal  a écrit :

> Le jeu. 7 déc. 2023 à 09:54, Shi Pujin  a écrit :
>
>> On Thu, 7 Dec 2023 08:30:09 +0800 Shi Pujin  wrote:
>>  > Package: nodejs
>>  > Version: 18.19.0
>>  > Severity: wishlist
>>  > Tags: patch
>>  > User: debian-loonga...@lists.debian.org
>>  > X-Debbugs-Cc: shipu...@loongson.cn
>>  > Usertags: loong64
>>  >
>>  > Hi,
>>  >
>>  > Nodejs upstream supports loong64 starting from nodejs-17.5.0 version,
>>  >
>>  > it'd be nice to have loong64 enabled，nodejs is in the Build-Depend
>> chain
>>  > for many packages.
>>
>
> Thanks, applied to
> https://salsa.debian.org/js-team/nodejs/-/commits/master-18.x
>
> Will be uploaded after current unstable nodejs has moved to testing.
>
>
>>  > I test compile nodejs locally, ignoring the build dependency
>>  > he(--no-check-builddeps), close the test phase,debian-nodejs was
>>  > successfully compiled.
>>  >
>>  > ```
>>  > debootstrap --no-check-gpg --arch=loong64 --variant=buildd
>>  > --extra-suites=unreleased unstable sid-loong64-rootfs
>>  > http://ftp.ports.debian.org/debian-ports
>
>
> The "correct" way to build nodejs on a new arch is documented in
>
> https://salsa.debian.org/js-team/nodejs/-/blob/master-18.x/debian/README.source
>


Also if you can give me access to a loong64 porterbox, I'll do that step
for you.

Bug#1057720: Removal notice: obsolete

[Ilias Tsitsimpis]

Source: haskell-ircbot
Version: 0.6.6.1-1
Severity: serious

I intend to remove this package:

  * It has no rev dependencies
  * The current version FTBFS (depends on optparse-applicative <0.17),
  * It's not part of the latest Stackage LTS

If you believe we should keep this package in Debian, please close this
bug report.

-- 
Ilias

Bug#1057718: Removal notice: obsolete

[Ilias Tsitsimpis]

Source: haskell-userid
Version: 0.1.3.7-1
Severity: serious

I intend to remove this package:

  * It has only one rev dependency (happstack-authenticate, which I
intend to remove as well)
  * The current version FTBFS (depends on base <4.17), 
  * Seems unmaintained; Doesn't build with GHC 9.4
  * It's not part of the latest Stackage LTS

If you believe we should keep this package in Debian, please close this
bug report.

-- 
Ilias

Bug#1057719: Removal notice: obsolete

[Ilias Tsitsimpis]

Source: haskell-happstack-authenticate
Version: 2.6.1-1
Severity: serious

I intend to remove this package:

  * It has no rev dependencies
  * The current version FTBFS (depends on broken haskell-userid)
  * It's not part of the latest Stackage LTS

If you believe we should keep this package in Debian, please close this
bug report.

-- 
Ilias

Bug#1057698: bugs.debian.org: The proposed kernel for Debian 12.3 breaks wlan

[Salvatore Bonaccorso]

Hi

On Thu, Dec 07, 2023 at 01:41:19PM +0100, Marc wrote:
> Indeed! So thank you so much Salvatore!
> 
> ---
> uname -a;dmesg | grep iwlw
> Linux t490 6.1.0-14-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.64-1
> (2023-11-30) x86_64 GNU/Linux
> [   16.115308] iwlwifi :00:14.3: enabling device ( -> 0002)
> [   16.136583] iwlwifi :00:14.3: firmware: direct-loading firmware
> iwlwifi-9000-pu-b0-jf-b0-46.ucode
> [   16.136607] iwlwifi :00:14.3: WRT: Overriding region id 0
> [   16.136610] iwlwifi :00:14.3: WRT: Overriding region id 1
> [   16.136611] iwlwifi :00:14.3: WRT: Overriding region id 2
> [   16.136612] iwlwifi :00:14.3: WRT: Overriding region id 3
> [   16.136613] iwlwifi :00:14.3: WRT: Overriding region id 4
> [   16.136613] iwlwifi :00:14.3: WRT: Overriding region id 6
> [   16.136614] iwlwifi :00:14.3: WRT: Overriding region id 8
> [   16.136615] iwlwifi :00:14.3: WRT: Overriding region id 9
> [   16.136616] iwlwifi :00:14.3: WRT: Overriding region id 10
> [   16.136617] iwlwifi :00:14.3: WRT: Overriding region id 11
> [   16.136618] iwlwifi :00:14.3: WRT: Overriding region id 15
> [   16.136619] iwlwifi :00:14.3: WRT: Overriding region id 16
> [   16.136619] iwlwifi :00:14.3: WRT: Overriding region id 18
> [   16.136620] iwlwifi :00:14.3: WRT: Overriding region id 19
> [   16.136621] iwlwifi :00:14.3: WRT: Overriding region id 20
> [   16.136622] iwlwifi :00:14.3: WRT: Overriding region id 21
> [   16.136623] iwlwifi :00:14.3: WRT: Overriding region id 28
> [   16.136626] iwlwifi :00:14.3: WRT: Overriding region id 29
> [   16.136934] iwlwifi :00:14.3: firmware: failed to load
> iwl-debug-yoyo.bin (-2)
> [   16.136944] iwlwifi :00:14.3: firmware: failed to load
> iwl-debug-yoyo.bin (-2)
> [   16.136946] iwlwifi :00:14.3: loaded firmware version 46.ea3728ee.0
> 9000-pu-b0-jf-b0-46.ucode op_mode iwlmvm
> [   16.317499] iwlwifi :00:14.3: BIOS contains WGDS but no WRDS
> [   16.319451] iwlwifi :00:14.3: Detected Intel(R) Wireless-AC 9560
> 160MHz, REV=0x312
> [   16.377004] iwlwifi :00:14.3: base HW address: 50:eb:71:1d:88:cd, OTP
> minor version: 0x4
> [   16.550372] iwlwifi :00:14.3 wlp0s20f3: renamed from wlan0
> --

Perfect, thanks for reporting back!

Note there was a missinformation in the previous reply. The values for
enable_ini would be:

parm:   enable_ini:0:disable, 1-15:FW_DBG_PRESET Values, 16:enabled 
without preset value defined,Debug INI TLV FW debug infrastructure (default: 16)

But if you do not need the setting just drop it.

Regards,
Salvatore

Bug#1057717: cmake ftbfs on ppc64el (and ppc64)

[Matthias Klose]

Package: src:cmake
Version: 3.28.0-1
Severity: serious
Tags: sid trixie

cmake ftbfs on ppc64el (and ppc64):

[...]
99% tests passed, 5 tests failed out of 697

Label Time Summary:
CMake  = 1205.59 sec*proc (290 tests)
CUDA   =  90.91 sec*proc (11 tests)
HIP=  17.89 sec*proc (6 tests)
ISPC   =  60.92 sec*proc (6 tests)
Label1 =   0.06 sec*proc (1 test)
Label2 =   0.06 sec*proc (1 test)
Qt5= 678.18 sec*proc (49 tests)
command=   6.93 sec*proc (23 tests)
policy =  81.42 sec*proc (42 tests)
run= 1198.66 sec*proc (267 tests)

Total Test time (real) = 436.62 sec

The following tests FAILED:
108 - LibName (SEGFAULT)
241 - CMakeCommands.add_link_options (SEGFAULT)
264 - CTestTestDepends (Failed)
393 - RunCMake.FPHSA (SEGFAULT)
467 - RunCMake.cmake_path (SEGFAULT)
Errors while running CTest
make[2]: *** [Makefile:94: test] Error 8
make[2]: Leaving directory '/<>/Build'

Bug#1057716: Removal notice: obsolete

[Ilias Tsitsimpis]

Source: haskell-diagrams
Version: 1.4.0.1-1
Severity: serious

I intend to remove this package:

  * It has no rev dependencies
  * It is a meta-package that installs diagrams-core, diagrams-lib, and
diagrams-cairo packages.

If you believe we should keep this package in Debian, please close this
bug report.

-- 
Ilias

Bug#1022772: Reduce severity, add wontfix

[Andreas Tille]

Control: tag -1 wontfix
Control: severity -1 minor

This bug is ranking amongst a lot of bugs that need attention while
this one is rather wontfix.  Thus also reducing severity.

Kind regards, Andreas.


-- 
http://fam-tille.de