Bug#915583: about html_static_path

[Holger Wansing]

Hi Sean,

Sean Whitton  wrote (Sat, 24 Feb 2024 11:58:59 +0800):
> Attached is the patch I prepared, which I couldn't get to work.  Maybe
> you can see what is wrong.  Thanks!

As I know it, the debian.css file has to reside in policy/_static.
And activate (un-comment) the path declaration for that in line 105 of 
conf.py.in.

Additionally, as I already wrote somewhere, for navigating it would be good
to have the Next/Previous buttons at the top of the page as well, not only
at the bottom.

And: do we want to have the 
"Built with Sphinx using a theme provided by Read the Docs."
in the footer? If not, that could be suppressed by
html_show_sphinx = False
in conf.py.in.


My diff for conf.py.in would be like this (with above suggestions):

diff --git a/policy/conf.py.in b/policy/conf.py.in
index d516d7b..4ea4df6 100755
--- a/policy/conf.py.in
+++ b/policy/conf.py.in
@@ -84,13 +84,19 @@ todo_include_todos = False
 # The theme to use for HTML and HTML Help pages.  See the documentation for
 # a list of builtin themes.
 #
-html_theme = 'nature'
+html_theme = 'sphinx_rtd_theme'
 
 # Theme options are theme-specific and customize the look and feel of a theme
 # further.  For a list of options available for each theme, see the
 # documentation.
 #
-# html_theme_options = {}
+html_theme_options = {
+   # To get previous/next buttons at the top and the bottom:
+   'prev_next_buttons_location': 'both'
+}
+
+# Overwrite theme to fit Debian colors
+html_css_files = ['debian.css']
 
 # Override the title to remove the unnecessary "documentation" suffix.
 html_title = "Debian Policy Manual v@VERSION@"
@@ -98,11 +104,14 @@ html_title = "Debian Policy Manual v@VERSION@"
 # Suppress the copyright notice.
 html_show_copyright = False
 
+# Hide “Created using Sphinx” in the HTML footer
+html_show_sphinx = False
+
 # Add any paths that contain custom static files (such as style sheets) here,
 # relative to this directory. They are copied after the builtin static files,
 # so a file named "default.css" will overwrite the builtin "default.css".
 #
-# html_static_path = ['_static']
+html_static_path = ['_static']
 
 
 # -- Options for HTMLHelp output --



Best regards
Holger



-- 
Holger Wansing 
PGP-Fingerprint: 496A C6E8 1442 4B34 8508  3529 59F1 87CA 156E B076

Bug#1062416: libmems: NMU diff for 64-bit time_t transition

[Steve Langasek]

Hello,

The package that was previously uploaded to experimental was unfortunately
broken because we did not notice that the package uses d-shlibs and
therefore needs additional changes.  (Most packages using d-shlibs simply
failed to build without additional changes; libbpp-seq-omics built but
produced an empty package.)

Please find a fixed patch attached.
-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developer   https://www.debian.org/
slanga...@ubuntu.com vor...@debian.org
diff -Nru libmems-1.6.0+4725/debian/changelog 
libmems-1.6.0+4725/debian/changelog
--- libmems-1.6.0+4725/debian/changelog 2020-11-17 08:12:35.0 +
+++ libmems-1.6.0+4725/debian/changelog 2024-02-24 07:52:53.0 +
@@ -1,3 +1,16 @@
+libmems (1.6.0+4725-9.1~exp2) experimental; urgency=medium
+
+  * Bump d-shlibs build-dependency for --t64 support.
+
+ -- Steve Langasek   Sat, 24 Feb 2024 07:52:53 +
+
+libmems (1.6.0+4725-9.1~exp1) experimental; urgency=medium
+
+  * Non-maintainer upload.
+  * Rename libraries for 64-bit time_t transition.
+
+ -- Steve Langasek   Thu, 01 Feb 2024 09:56:15 +
+
 libmems (1.6.0+4725-9) unstable; urgency=medium
 
   * Standards-Version: 4.5.1 (routine-update)
diff -Nru libmems-1.6.0+4725/debian/control libmems-1.6.0+4725/debian/control
--- libmems-1.6.0+4725/debian/control   2020-11-17 08:12:35.0 +
+++ libmems-1.6.0+4725/debian/control   2024-02-24 07:52:31.0 +
@@ -4,7 +4,7 @@
 Section: science
 Priority: optional
 Build-Depends: debhelper-compat (= 13),
-   d-shlibs,
+   d-shlibs (>= 0.106~),
pkg-config,
libgenome-dev,
libboost-filesystem-dev,
@@ -20,7 +20,7 @@
 Package: libmems-dev
 Architecture: any
 Section: libdevel
-Depends: libmems1 (= ${binary:Version}),
+Depends: libmems1t64 (= ${binary:Version}),
  ${misc:Depends},
  ${devlibs:Depends}
 Provides: libmems-1.6-dev
@@ -37,16 +37,18 @@
  This is the development package containing the statically linked
  library and the header files.
 
-Package: libmems1
+Package: libmems1t64
+Provides: ${t64:Provides}
 Architecture: any
 Multi-Arch: same
 Section: libs
 Depends: ${shlibs:Depends},
  ${misc:Depends}
 Pre-Depends: ${misc:Pre-Depends}
-Conflicts: libmems-1.6-1,
+Conflicts: libmems1 (<< ${source:Version}),
+   libmems-1.6-1,
libmems-1.6-1v5
-Replaces: libmems-1.6-1,
+Replaces: libmems1, libmems-1.6-1,
   libmems-1.6-1v5
 Description: library to support DNA string matching and comparative genomics
  libMems is a freely available software development library to support DNA
diff -Nru libmems-1.6.0+4725/debian/libmems1t64.lintian-overrides 
libmems-1.6.0+4725/debian/libmems1t64.lintian-overrides
--- libmems-1.6.0+4725/debian/libmems1t64.lintian-overrides 1970-01-01 
00:00:00.0 +
+++ libmems-1.6.0+4725/debian/libmems1t64.lintian-overrides 2024-02-01 
09:56:15.0 +
@@ -0,0 +1 @@
+libmems1t64: package-name-doesnt-match-sonames libmems1
diff -Nru libmems-1.6.0+4725/debian/rules libmems-1.6.0+4725/debian/rules
--- libmems-1.6.0+4725/debian/rules 2020-11-17 08:12:35.0 +
+++ libmems-1.6.0+4725/debian/rules 2024-02-24 07:51:56.0 +
@@ -8,6 +8,7 @@
 override_dh_install:
dh_install
d-shlibmove --commit \
+   --t64 \
--multiarch \
--devunversioned \
--exclude-la \


signature.asc
Description: PGP signature

Bug#1064554: jruby fails to build from source in unstable

[Vladimir Petko]

Source: jruby
Version: 9.4.5.0+ds-1
Severity: serious

Dear Maintainer,

When building jruby in unstable, the following error occurs:

[INFO] 
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-install-
plugin:3.1.1:install (default-install) on project jruby-parent: Failed to
install artifact org.jruby:jruby-parent:pom:9.4.5.0:
/<>/debian/maven-repo/org/jruby/jruby-parent/9.4.5.0/jruby-
parent-9.4.5.0.pom (Permission denied) -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e
switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please
read the following articles:
[ERROR] [Help 1]
http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
dh_auto_build: error: /usr/lib/jvm/default-java/bin/java -noverify -cp
/usr/share/maven/boot/plexus-classworlds-2.x.jar -Dmaven.home=/usr/share/maven
-Dmaven.multiModuleProjectDirectory=/<>/jruby-9.4.5.0\+ds
-Dclassworlds.conf=/etc/maven/m2-debian.conf
-Dproperties.file.manual=/<>/jruby-9.4.5.0\+ds/debian/maven.properties
org.codehaus.plexus.classworlds.launcher.Launcher -s/etc/maven/settings-
debian.xml -Ddebian.dir=/<>/jruby-9.4.5.0\+ds/debian
-Dmaven.repo.local=/<>/jruby-9.4.5.0\+ds/debian/maven-repo --batch-
mode -Djruby.revision=9.4.5.0\+ds-1build1\~ppa2 -Pmain,complete,dist
-DskipTests -Dnotimestamp=true -Dlocale=en_US returned exit code 1
make[1]: *** [debian/rules:43: override_dh_auto_build] Error 25
make[1]: Leaving directory '/<>'
make: *** [debian/rules:9: binary] Error 2
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2

Build finished at 2024-02-24T07:14:56Z

This is due to maven-repo-helper copying symlinks to jruby poms rather than
poms themselves.

One possible solution is to copy jruby poms manually in
execute_after_dh_auto_configure:
# copy jruby poms rather than links, because the build will try to
patch them
for p in jruby jruby-parent jruby-base jruby-core jruby-artifacts ; do
\
rm debian/maven-repo/org/jruby/$$p/* ;\
mkdir debian/maven-repo/org/jruby/$$p/debian ; \
cp /usr/share/maven-repo/org/jruby/$$p/debian/* debian/maven-
repo/org/jruby/$$p/debian/ ;\
done




-- System Information:
Debian Release: trixie/sid
  APT prefers mantic-updates
  APT policy: (500, 'mantic-updates'), (500, 'mantic-security'), (500, 
'mantic'), (100, 'mantic-backports')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.5.0-17-generic (SMP w/32 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_WARN, TAINT_OOT_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Bug#1062411: libmateweather: NMU diff for 64-bit time_t transition

[Steve Langasek]

Hello,

Please find attached an updated patch rebased on current unstable.

-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developer   https://www.debian.org/
slanga...@ubuntu.com vor...@debian.org
diff -Nru libmateweather-1.26.3/debian/changelog 
libmateweather-1.26.3/debian/changelog
--- libmateweather-1.26.3/debian/changelog  2024-02-06 14:26:16.0 
+
+++ libmateweather-1.26.3/debian/changelog  2024-02-24 07:49:53.0 
+
@@ -1,3 +1,10 @@
+libmateweather (1.26.3-3.1~exp1) experimental; urgency=medium
+
+  * Non-maintainer upload.
+  * Rename libraries for 64-bit time_t transition.
+
+ -- Steve Langasek   Sat, 24 Feb 2024 07:49:53 +
+
 libmateweather (1.26.3-3) unstable; urgency=medium
 
   * debian/control:
diff -Nru libmateweather-1.26.3/debian/control 
libmateweather-1.26.3/debian/control
--- libmateweather-1.26.3/debian/control2024-02-06 14:25:31.0 
+
+++ libmateweather-1.26.3/debian/control2024-02-24 07:49:42.0 
+
@@ -24,15 +24,16 @@
 Vcs-Browser: https://salsa.debian.org/debian-mate-team/libmateweather
 Vcs-Git: https://salsa.debian.org/debian-mate-team/libmateweather.git
 
-Package: libmateweather1
+Package: libmateweather1t64
+Provides: ${t64:Provides}
 Architecture: any
 Multi-Arch: same
 Pre-Depends: ${misc:Pre-Depends},
 Depends: libmateweather-common (= ${source:Version}),
  ${misc:Depends},
  ${shlibs:Depends},
-Breaks: libmateweather,
-Replaces: libmateweather,
+Breaks: libmateweather1 (<< ${source:Version}), libmateweather,
+Replaces: libmateweather1, libmateweather,
 Description: MateWeather shared library
  libmateweather is a library to access weather information from online
  services for numerous locations.
@@ -57,7 +58,7 @@
 Multi-Arch: same
 Depends: libglib2.0-dev,
  libgtk-3-dev,
- libmateweather1 (= ${binary:Version}),
+ libmateweather1t64 (= ${binary:Version}),
  libsoup2.4-dev,
  libxml2-dev,
  ${misc:Depends},
diff -Nru libmateweather-1.26.3/debian/libmateweather1.install 
libmateweather-1.26.3/debian/libmateweather1.install
--- libmateweather-1.26.3/debian/libmateweather1.install2014-12-11 
04:45:54.0 +
+++ libmateweather-1.26.3/debian/libmateweather1.install1970-01-01 
00:00:00.0 +
@@ -1 +0,0 @@
-usr/lib/*/*.so.*
diff -Nru libmateweather-1.26.3/debian/libmateweather1.symbols 
libmateweather-1.26.3/debian/libmateweather1.symbols
--- libmateweather-1.26.3/debian/libmateweather1.symbols2019-07-10 
11:59:00.0 +
+++ libmateweather-1.26.3/debian/libmateweather1.symbols1970-01-01 
00:00:00.0 +
@@ -1,125 +0,0 @@
-libmateweather.so.1 libmateweather1 #MINVER#
-* Build-Depends-Package: libmateweather-dev
- _weather_info_fill@Base 1.6.2
- bom_start_open@Base 1.6.2
- calc_moon@Base 1.6.2
- calc_moon_phases@Base 1.6.2
- calc_sun@Base 1.6.2
- calc_sun_time@Base 1.6.2
- ecl2equ@Base 1.6.2
- free_forecast_list@Base 1.6.2
- iwin_start_open@Base 1.6.2
- mateweather_dpgettext@Base 1.6.2
- mateweather_gettext@Base 1.6.2
- mateweather_location_entry_get_location@Base 1.6.2
- mateweather_location_entry_get_type@Base 1.6.2
- mateweather_location_entry_has_custom_text@Base 1.6.2
- mateweather_location_entry_new@Base 1.6.2
- mateweather_location_entry_set_city@Base 1.6.2
- mateweather_location_entry_set_location@Base 1.6.2
- mateweather_location_free_children@Base 1.6.2
- mateweather_location_free_timezones@Base 1.6.2
- mateweather_location_get_children@Base 1.6.2
- mateweather_location_get_city_name@Base 1.6.2
- mateweather_location_get_code@Base 1.6.2
- mateweather_location_get_coords@Base 1.6.2
- mateweather_location_get_country@Base 1.6.2
- mateweather_location_get_distance@Base 1.6.2
- mateweather_location_get_level@Base 1.6.2
- mateweather_location_get_name@Base 1.6.2
- mateweather_location_get_parent@Base 1.6.2
- mateweather_location_get_sort_name@Base 1.6.2
- mateweather_location_get_timezone@Base 1.6.2
- mateweather_location_get_timezones@Base 1.6.2
- mateweather_location_get_type@Base 1.6.2
- mateweather_location_get_weather@Base 1.6.2
- mateweather_location_has_coords@Base 1.6.2
- mateweather_location_level_get_type@Base 1.6.2
- mateweather_location_new_world@Base 1.6.2
- mateweather_location_ref@Base 1.6.2
- mateweather_location_to_weather_location@Base 1.6.2
- mateweather_location_unref@Base 1.6.2
- mateweather_parser_free@Base 1.6.2
- mateweather_parser_get_localized_value@Base 1.6.2
- mateweather_parser_get_value@Base 1.6.2
- mateweather_parser_new@Base 1.6.2
- mateweather_prefs_get_distance_display_name@Base 1.6.2
- mateweather_prefs_get_pressure_display_name@Base 1.6.2
- mateweather_prefs_get_speed_display_name@Base 1.6.2
- mateweather_prefs_get_temp_display_name@Base 1.6.2
- 

Bug#1064553: libgdiplus: build-error on current sid (all warnings being treated as errors)

[Andreas Metzler]

Source: libgdiplus
Version: 6.1+dfsg-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)

libgdiplus FTBFS on current sid:

make[7]: Entering directory '/dev/shm/x/libgdiplus-6.1+dfsg/gtest_build'
[ 12%] Building CXX object googletest/CMakeFiles/gtest.dir/src/gtest-all.cc.o
In file included from 
/tmp/x/libgdiplus-6.1+dfsg/external/googletest/googletest/src/gtest-all.cc:42:
/tmp/x/libgdiplus-6.1+dfsg/external/googletest/googletest/src/gtest-death-test.cc:
 In function 'bool testing::internal::StackGrowsDown()':
/tmp/x/libgdiplus-6.1+dfsg/external/googletest/googletest/src/gtest-death-test.cc:1301:24:
 error: 'dummy' may be used uninitialized [-Werror=maybe-uninitialized]
 1301 |   StackLowerThanAddress(, );
  |   ~^
/tmp/x/libgdiplus-6.1+dfsg/external/googletest/googletest/src/gtest-death-test.cc:1290:13:
 note: by argument 1 of type 'const void*' to 'void 
testing::internal::StackLowerThanAddress(const void*, bool*)' declared here
 1290 | static void StackLowerThanAddress(const void* ptr, bool* result) {
  | ^
/tmp/x/libgdiplus-6.1+dfsg/external/googletest/googletest/src/gtest-death-test.cc:1299:7:
 note: 'dummy' declared here
 1299 |   int dummy;
  |   ^
cc1plus: all warnings being treated as errors
make[7]: *** [googletest/CMakeFiles/gtest.dir/build.make:76: 
googletest/CMakeFiles/gtest.dir/src/gtest-all.cc.o] Error 1

cu Andreas

Bug#1062726: libident: NMU diff for 64-bit time_t transition

[Steve Langasek]

Hello,

An oversight with regards to the provides: handling support in debhelper
means the package in experimental does not correctly declare compatibility
on 64-bit archs with the prior ABI.  Please find an updated patch attached.

-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developer   https://www.debian.org/
slanga...@ubuntu.com vor...@debian.org
diff -Nru libident-0.32/debian/changelog libident-0.32/debian/changelog
--- libident-0.32/debian/changelog  2022-01-02 19:55:27.0 +
+++ libident-0.32/debian/changelog  2024-02-24 07:41:13.0 +
@@ -1,3 +1,17 @@
+libident (0.32-1.1~exp2) experimental; urgency=medium
+
+  * Fix doc link.
+  * Declare X-Time64-Compat to get proper Provides:
+
+ -- Steve Langasek   Sat, 24 Feb 2024 07:41:13 +
+
+libident (0.32-1.1~exp1) experimental; urgency=medium
+
+  * Non-maintainer upload.
+  * Rename libraries for 64-bit time_t transition.
+
+ -- Steve Langasek   Fri, 02 Feb 2024 23:03:30 +
+
 libident (0.32-1) unstable; urgency=medium
 
   * New upstream release. (Closes: #1002955)
diff -Nru libident-0.32/debian/control libident-0.32/debian/control
--- libident-0.32/debian/control2022-01-02 19:55:26.0 +
+++ libident-0.32/debian/control2024-02-24 07:40:47.0 +
@@ -10,7 +10,11 @@
 Vcs-Git: https://salsa.debian.org/debian/libident.git
 Vcs-Browser: https://salsa.debian.org/debian/libident
 
-Package: libident
+Package: libident0
+X-Time64-Compat: libident
+Provides: ${t64:Provides}
+Replaces: libident
+Breaks: libident (<< ${source:Version})
 Architecture: any
 Depends:
  ${misc:Depends},
@@ -31,7 +35,7 @@
 Section: libdevel
 Priority: optional
 Depends:
- libident (= ${binary:Version}),
+ libident0 (= ${binary:Version}),
  ${misc:Depends},
  ${shlibs:Depends},
 Description: simple RFC1413 client library - development
diff -Nru libident-0.32/debian/libident.install 
libident-0.32/debian/libident.install
--- libident-0.32/debian/libident.install   2022-01-02 19:35:23.0 
+
+++ libident-0.32/debian/libident.install   1970-01-01 00:00:00.0 
+
@@ -1,3 +0,0 @@
-usr/sbin/
-usr/lib/*/lib*.so.*
-usr/share/man/man8/
diff -Nru libident-0.32/debian/libident.shlibs 
libident-0.32/debian/libident.shlibs
--- libident-0.32/debian/libident.shlibs2022-01-01 18:15:57.0 
+
+++ libident-0.32/debian/libident.shlibs1970-01-01 00:00:00.0 
+
@@ -1 +0,0 @@
-libident 0 libident (>= 0.32)
diff -Nru libident-0.32/debian/libident0.install 
libident-0.32/debian/libident0.install
--- libident-0.32/debian/libident0.install  1970-01-01 00:00:00.0 
+
+++ libident-0.32/debian/libident0.install  2024-02-02 23:03:30.0 
+
@@ -0,0 +1,3 @@
+usr/sbin/
+usr/lib/*/lib*.so.*
+usr/share/man/man8/
diff -Nru libident-0.32/debian/libident0.lintian-overrides 
libident-0.32/debian/libident0.lintian-overrides
--- libident-0.32/debian/libident0.lintian-overrides1970-01-01 
00:00:00.0 +
+++ libident-0.32/debian/libident0.lintian-overrides2024-02-02 
23:03:30.0 +
@@ -0,0 +1 @@
+libident0: package-name-doesnt-match-sonames libident
diff -Nru libident-0.32/debian/libident0.shlibs 
libident-0.32/debian/libident0.shlibs
--- libident-0.32/debian/libident0.shlibs   1970-01-01 00:00:00.0 
+
+++ libident-0.32/debian/libident0.shlibs   2024-02-02 23:03:30.0 
+
@@ -0,0 +1 @@
+libident0 0 libident0 (>= 0.32)
diff -Nru libident-0.32/debian/rules libident-0.32/debian/rules
--- libident-0.32/debian/rules  2022-01-02 19:33:19.0 +
+++ libident-0.32/debian/rules  2024-02-24 07:40:28.0 +
@@ -20,4 +20,4 @@
--enable-testers
 
 override_dh_installdocs:
-   dh_installdocs --link-doc=libident
+   dh_installdocs --link-doc=libident0


signature.asc
Description: PGP signature

Bug#1062292: libfilezilla: NMU diff for 64-bit time_t transition

[Steve Langasek]

Please find attached an updated patch, rebased on current unstable.

-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developer   https://www.debian.org/
slanga...@ubuntu.com vor...@debian.org
diff -Nru libfilezilla-0.46.0/debian/changelog 
libfilezilla-0.46.0/debian/changelog
--- libfilezilla-0.46.0/debian/changelog2024-02-23 05:52:18.0 
+
+++ libfilezilla-0.46.0/debian/changelog2024-02-24 07:32:22.0 
+
@@ -1,3 +1,10 @@
+libfilezilla (0.46.0-3.1~exp1) experimental; urgency=medium
+
+  * Non-maintainer upload.
+  * Rename libraries for 64-bit time_t transition.
+
+ -- Steve Langasek   Sat, 24 Feb 2024 07:32:22 +
+
 libfilezilla (0.46.0-3) unstable; urgency=medium
 
   * 'd/copyright': Update year for copyright holders.
diff -Nru libfilezilla-0.46.0/debian/changelog.orig 
libfilezilla-0.46.0/debian/changelog.orig
--- libfilezilla-0.46.0/debian/changelog.orig   2024-02-23 05:52:18.0 
+
+++ libfilezilla-0.46.0/debian/changelog.orig   1970-01-01 00:00:00.0 
+
@@ -1,516 +0,0 @@
-libfilezilla (0.46.0-3) unstable; urgency=medium
-
-  * 'd/copyright': Update year for copyright holders.
-
- -- Phil Wyett   Fri, 23 Feb 2024 05:52:18 +
-
-libfilezilla (0.46.0-2) unstable; urgency=medium
-
-  * Source only upload to allow migration.
-
- -- Phil Wyett   Fri, 23 Feb 2024 05:28:26 +
-
-libfilezilla (0.46.0-1) unstable; urgency=medium
-
-  * New upstream version 0.46.0.
-  * Soname bump rename package to libfilezilla42.
-  * 'd/control'.
-- Update 'libgnutls28-dev' required version to minimum of 3.8.3.
-- Change 'Build-Depends' from  obsolete 'pkg-config' to 'pkgconf'.
-
- -- Phil Wyett   Thu, 08 Feb 2024 06:43:27 +
-
-libfilezilla (0.45.0-5) unstable; urgency=medium
-
-  [ Gianfranco Costamagna ]
-  * d/rules: Ignore 'GNUTLS_SYSTEM_PRIORITY_FILE'.
-  * Drop not required 'disable-ssl-tests.patch'.
-
- -- Phil Wyett   Tue, 28 Nov 2023 14:21:33 +
-
-libfilezilla (0.45.0-4) unstable; urgency=medium
-
-  [ Gianfranco Costamagna ]
-  * Disable tls1.0 and tls1.1 tests, deprecated. (Closes: #1055633).
-
- -- Phil Wyett   Thu, 09 Nov 2023 19:59:31 +
-
-libfilezilla (0.45.0-3) unstable; urgency=medium
-
-  * Update override to: debian-watch-does-not-check-openpgp-signature
-
- -- Phil Wyett   Wed, 08 Nov 2023 22:25:13 +
-
-libfilezilla (0.45.0-2) unstable; urgency=medium
-
-  * Source only upload for migration to testing.
-
- -- Phil Wyett   Thu, 02 Nov 2023 01:28:13 +
-
-libfilezilla (0.45.0-1) unstable; urgency=medium
-
-  * New upstream 0.45.0.
-  * Soname bump rename package to libfilezilla41.
-
- -- Phil Wyett   Wed, 25 Oct 2023 04:15:45 +0100
-
-libfilezilla (0.44.0-3) unstable; urgency=medium
-
-  * Change d/gbp.conf compression to xz.
-  * Add comment to d/rules for verbose.
-
- -- Phil Wyett   Fri, 28 Jul 2023 04:39:28 +0100
-
-libfilezilla (0.44.0-2) unstable; urgency=medium
-
-  * Source only upload for migration to testing
-
- -- Phil Wyett   Sat, 08 Jul 2023 12:58:06 +0100
-
-libfilezilla (0.44.0-1) unstable; urgency=medium
-
-  * New upstream version 0.44.0
-  * Soname bump rename package to libfilezilla40
-
- -- Phil Wyett   Thu, 06 Jul 2023 08:41:43 +0100
-
-libfilezilla (0.43.0-2) unstable; urgency=medium
-
-  * Source only upload for migration to testing
-
- -- Phil Wyett   Tue, 13 Jun 2023 08:18:14 +0100
-
-libfilezilla (0.43.0-1) unstable; urgency=medium
-
-  * New upstream version 0.43.0
-  * Soname bump rename package to libfilezilla39
-
- -- Phil Wyett   Sun, 11 Jun 2023 10:35:46 +0100
-
-libfilezilla (0.42.2-1) experimental; urgency=medium
-
-  * New upstream version 0.42.2
-  * Soname bump rename package to libfilezilla38
-
- -- Phil Wyett   Sat, 29 Apr 2023 08:24:14 +0100
-
-libfilezilla (0.42.0-1) experimental; urgency=medium
-
-  * New upstream version 0.42.0
-  * Soname bump rename package to libfilezilla36
-  * d/watch: Use upstream preferred tar.xz tarball
-
- -- Phil Wyett   Fri, 21 Apr 2023 07:24:25 +0100
-
-libfilezilla (0.41.1-1) experimental; urgency=medium
-
-  * New upstream version 0.41.1
-  * Soname bump rename package to libfilezilla35
-
- -- Phil Wyett   Fri, 24 Feb 2023 02:02:27 +
-
-libfilezilla (0.41.0-2) unstable; urgency=medium
-
-  * Source only upload for migration to testing
-
- -- Phil Wyett   Tue, 24 Jan 2023 06:53:01 +
-
-libfilezilla (0.41.0-1) unstable; urgency=medium
-
-  * New upstream version 0.41.0
-  * Soname bump rename package to libfilezilla34
-- Only additions to API in this release
-- Only consumed by filezilla, so low risk soname bump
-
- -- Phil Wyett   Thu, 12 Jan 2023 11:43:51 +
-
-libfilezilla (0.40.0-2) unstable; urgency=medium
-
-  * Source only upload for migration to testing
-
- -- Phil Wyett   Sun, 01 Jan 2023 19:25:34 +
-
-libfilezilla (0.40.0-1) 

Bug#1062243: libcapi20-3: NMU diff for 64-bit time_t transition

[Steve Langasek]

Hello,

The package that was previously uploaded to experimental was unfortunately
broken because of incorrect renaming of the .install.in file.

Please find a fixed patch attached.

-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developer   https://www.debian.org/
slanga...@ubuntu.com vor...@debian.org
diff -Nru libcapi20-3-3.27/debian/changelog libcapi20-3-3.27/debian/changelog
--- libcapi20-3-3.27/debian/changelog   2018-04-15 12:23:19.0 +
+++ libcapi20-3-3.27/debian/changelog   2024-02-24 07:21:21.0 +
@@ -1,3 +1,16 @@
+libcapi20-3 (1:3.27-3.1~exp2) experimental; urgency=medium
+
+  * Fix wrong renaming of .install.in file
+
+ -- Steve Langasek   Sat, 24 Feb 2024 07:21:21 +
+
+libcapi20-3 (1:3.27-3.1~exp1) experimental; urgency=medium
+
+  * Non-maintainer upload.
+  * Rename libraries for 64-bit time_t transition.
+
+ -- Steve Langasek   Wed, 31 Jan 2024 20:12:41 +
+
 libcapi20-3 (1:3.27-3) unstable; urgency=medium
 
   * control:
diff -Nru libcapi20-3-3.27/debian/control libcapi20-3-3.27/debian/control
--- libcapi20-3-3.27/debian/control 2018-04-15 12:22:25.0 +
+++ libcapi20-3-3.27/debian/control 2024-01-31 20:12:41.0 +
@@ -9,7 +9,10 @@
 Vcs-Browser: https://github.com/leggewie-DM/libcapi20
 Vcs-Git: g...@github.com:leggewie-DM/libcapi20.git
 
-Package: libcapi20-3
+Package: libcapi20-3t64
+Provides: ${t64:Provides}
+Replaces: libcapi20-3
+Breaks: libcapi20-3 (<< ${source:Version})
 Architecture: linux-any
 Section: libs
 Multi-Arch: same
@@ -23,9 +26,9 @@
 Architecture: linux-any
 Section: libdevel
 Multi-Arch: same
-Depends: libcapi20-3 (= ${binary:Version}), ${misc:Depends}
+Depends: libcapi20-3t64 (= ${binary:Version}), ${misc:Depends}
 Breaks: isdnutils-base (<< 1:3.22+dfsg1-4)
-Replaces: libcapi20-3 (<< 1:3.9.20060704+dfsg.3-4),
+Replaces: libcapi20-3t64 (<< 1:3.9.20060704+dfsg.3-4),
  isdnutils-base (<< 1:3.22+dfsg1-4)
 Description: ISDN utilities - CAPI development libraries
  This package provides files needed for development of CAPI-aware software.
diff -Nru libcapi20-3-3.27/debian/libcapi20-3.README.Debian 
libcapi20-3-3.27/debian/libcapi20-3.README.Debian
--- libcapi20-3-3.27/debian/libcapi20-3.README.Debian   2014-04-07 
04:29:08.0 +
+++ libcapi20-3-3.27/debian/libcapi20-3.README.Debian   1970-01-01 
00:00:00.0 +
@@ -1,21 +0,0 @@
-The libcapi20-3 package was carved out from the long-established isdnutils
-package for easier maintenance in March 2014.  Feel free to consult isdnutils
-history to learn more about how things evolved prior to that date.
-
-It may become necessary to debug libcapi20. Debian builds the package without
-debug information for performance reasons.  Below patch will compile the
-library with debug information.
-
-diff --git a/capi20/capi20.c b/capi20/capi20.c
-index ab8c1c6..81b5c5c 100644
 a/capi20/capi20.c
-+++ b/capi20/capi20.c
-@@ -61,7 +61,7 @@ static int tracelevel;
- static char *tracefile;
-
- /** debug level, for debugging purpose */
--static int nDebugLevel = 0;
-+static int nDebugLevel = 0x;
-
- /**
-  * \brief CapiDebug output functions
diff -Nru libcapi20-3-3.27/debian/libcapi20-3.docs 
libcapi20-3-3.27/debian/libcapi20-3.docs
--- libcapi20-3-3.27/debian/libcapi20-3.docs2011-11-10 01:35:09.0 
+
+++ libcapi20-3-3.27/debian/libcapi20-3.docs1970-01-01 00:00:00.0 
+
@@ -1 +0,0 @@
-README
diff -Nru libcapi20-3-3.27/debian/libcapi20-3.install.in 
libcapi20-3-3.27/debian/libcapi20-3.install.in
--- libcapi20-3-3.27/debian/libcapi20-3.install.in  2014-04-25 
06:50:57.0 +
+++ libcapi20-3-3.27/debian/libcapi20-3.install.in  1970-01-01 
00:00:00.0 +
@@ -1,2 +0,0 @@
-usr/lib/@DEB_HOST_MULTIARCH@/libcapi20.so.* usr/lib/@DEB_HOST_MULTIARCH@/
-usr/lib/@DEB_HOST_MULTIARCH@/capi/*.so* usr/lib/@DEB_HOST_MULTIARCH@/capi/
diff -Nru libcapi20-3-3.27/debian/libcapi20-3.shlibs 
libcapi20-3-3.27/debian/libcapi20-3.shlibs
--- libcapi20-3-3.27/debian/libcapi20-3.shlibs  2014-04-01 03:31:36.0 
+
+++ libcapi20-3-3.27/debian/libcapi20-3.shlibs  1970-01-01 00:00:00.0 
+
@@ -1 +0,0 @@
-libcapi20 3 libcapi20-3
diff -Nru libcapi20-3-3.27/debian/libcapi20-3t64.Debian 
libcapi20-3-3.27/debian/libcapi20-3t64.Debian
--- libcapi20-3-3.27/debian/libcapi20-3t64.Debian   1970-01-01 
00:00:00.0 +
+++ libcapi20-3-3.27/debian/libcapi20-3t64.Debian   2024-01-31 
20:12:41.0 +
@@ -0,0 +1,21 @@
+The libcapi20-3 package was carved out from the long-established isdnutils
+package for easier maintenance in March 2014.  Feel free to consult isdnutils
+history to learn more about how things evolved prior to that date.
+
+It may become necessary to debug libcapi20. Debian builds the package without
+debug 

Bug#1064490: closed by Debian FTP Masters (reply to Andrej Shadura ) (Bug#1064490: fixed in inputplug 0.4.0-3)

[Peter Green]

reopen 1064490
thanks

On 23/02/2024 10:21, Debian Bug Tracking System wrote:

This is an automatic notification regarding your Bug report
which was filed against the inputplug package:

#1064490: inputplug - upcoming rust-nix and rust-x11rb updates.

It has been closed by Debian FTP Masters  (reply to 
Andrej Shadura ).


Thanks for adopting the patches, however the package still build-depends on
librust-x11rb-0.8+default-dev, so it can't currently be built with the 
rust-x11rb
from experimental.

Bug#1064166: ldc: NMU diff for 64-bit time_t transition

[Steve Langasek]

On Sat, Feb 24, 2024 at 08:12:09AM +0100, Matthias Klumpp wrote:
> Am Sa., 24. Feb. 2024 um 08:00 Uhr schrieb Steve Langasek :

> > Hi Matthias,
> >
> > I see you've implemented this as:
> >
> > ifneq (,$(filter $(DEB_HOST_ARCH), armhf))
> > export DEB_BUILD_MAINT_OPTIONS += abi=+time64,+lfs
> > endif
> >
> > Please note that armhf is not the only architecture affected by this ABI
> > change: armel is also a release architecture affected, and there are a
> > number of other 32-bit ports architectures which are affected (hppa,
> > powerpc, ...)
> 
> I know, but LDC does not exist on these architectures ;-)

Ah, fair enough!

-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developer   https://www.debian.org/
slanga...@ubuntu.com vor...@debian.org


signature.asc
Description: PGP signature

Bug#1062232: libbpp-phyl-omics: NMU diff for 64-bit time_t transition

[Steve Langasek]

Ahem.

Really attached now.

On Fri, Feb 23, 2024 at 11:08:42PM -0800, Steve Langasek wrote:
> Hello,
> 
> The package that was previously uploaded to experimental was unfortunately
> broken because we did not notice that the package uses d-shlibs and
> therefore needs additional changes.  (Most packages using d-shlibs simply
> failed to build without additional changes; libbpp-phyl-omics built but
> produced an empty package.)
> 
> Please find a fixed patch attached.
> 
> -- 
> Steve Langasek   Give me a lever long enough and a Free OS
> Debian Developer   to set it on, and I can move the world.
> Ubuntu Developer   https://www.debian.org/
> slanga...@ubuntu.com vor...@debian.org

-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developer   https://www.debian.org/
slanga...@ubuntu.com vor...@debian.org
diff -Nru libbpp-phyl-omics-2.4.1/debian/changelog 
libbpp-phyl-omics-2.4.1/debian/changelog
--- libbpp-phyl-omics-2.4.1/debian/changelog2023-08-13 11:11:55.0 
+
+++ libbpp-phyl-omics-2.4.1/debian/changelog2024-02-24 07:11:14.0 
+
@@ -1,3 +1,16 @@
+libbpp-phyl-omics (2.4.1-5.1~exp2) experimental; urgency=medium
+
+  * Bump d-shlibs build-dependency for --t64 support.
+
+ -- Steve Langasek   Sat, 24 Feb 2024 07:11:14 +
+
+libbpp-phyl-omics (2.4.1-5.1~exp1) experimental; urgency=medium
+
+  * Non-maintainer upload.
+  * Rename libraries for 64-bit time_t transition.
+
+ -- Steve Langasek   Wed, 31 Jan 2024 19:55:07 +
+
 libbpp-phyl-omics (2.4.1-5) unstable; urgency=medium
 
   * Team upload.
diff -Nru libbpp-phyl-omics-2.4.1/debian/control 
libbpp-phyl-omics-2.4.1/debian/control
--- libbpp-phyl-omics-2.4.1/debian/control  2023-08-13 11:11:41.0 
+
+++ libbpp-phyl-omics-2.4.1/debian/control  2024-02-24 07:11:11.0 
+
@@ -6,7 +6,7 @@
 Priority: optional
 Build-Depends: debhelper-compat (= 13),
cmake,
-   d-shlibs,
+   d-shlibs (>= 0.106~),
libbpp-phyl-dev,
libbpp-seq-omics-dev
 Standards-Version: 4.6.2
@@ -18,7 +18,7 @@
 Package: libbpp-phyl-omics-dev
 Architecture: any
 Section: libdevel
-Depends: libbpp-phyl-omics3 (= ${binary:Version}),
+Depends: libbpp-phyl-omics3t64 (= ${binary:Version}),
  ${misc:Depends},
  ${devlibs:Depends}
 Multi-Arch: same
@@ -32,7 +32,10 @@
  This package contains the static library and the header files of the
  Bio++ classes dedicated to genomic phylogeny.
 
-Package: libbpp-phyl-omics3
+Package: libbpp-phyl-omics3t64
+Provides: ${t64:Provides}
+Replaces: libbpp-phyl-omics3
+Conflicts: libbpp-phyl-omics3 (<< ${source:Version})
 Architecture: any
 Multi-Arch: same
 Section: libs
diff -Nru libbpp-phyl-omics-2.4.1/debian/libbpp-phyl-omics3.symbols 
libbpp-phyl-omics-2.4.1/debian/libbpp-phyl-omics3.symbols
--- libbpp-phyl-omics-2.4.1/debian/libbpp-phyl-omics3.symbols   2023-08-13 
11:11:55.0 +
+++ libbpp-phyl-omics-2.4.1/debian/libbpp-phyl-omics3.symbols   1970-01-01 
00:00:00.0 +
@@ -1,543 +0,0 @@
-libbpp-phyl-omics.so.3 libbpp-phyl-omics3 #MINVER#
-* Build-Depends-Package: libbpp-phyl-omics-dev
- _ZN3bpp10BppIntegerD0Ev@Base 2.4.1
- _ZN3bpp10BppIntegerD1Ev@Base 2.4.1
- 
_ZN3bpp11MafSequence33splitNameIntoSpeciesAndChromosomeERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEERS6_S9_@Base
 2.4.1
- _ZN3bpp12TreeTemplateINS_4NodeEE11getRootNodeEv@Base 2.4.1
- _ZN3bpp12TreeTemplateINS_4NodeEE11newOutGroupEPS1_@Base 2.4.1
- _ZN3bpp12TreeTemplateINS_4NodeEE11newOutGroupEi@Base 2.4.1
- 
_ZN3bpp12TreeTemplateINS_4NodeEE11setNodeNameEiRKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE@Base
 2.4.1
- _ZN3bpp12TreeTemplateINS_4NodeEE11setRootNodeEPS1_@Base 2.4.1
- _ZN3bpp12TreeTemplateINS_4NodeEE12resetNodesIdEv@Base 2.4.1
- _ZN3bpp12TreeTemplateINS_4NodeEE13getInnerNodesEv@Base 2.4.1
- _ZN3bpp12TreeTemplateINS_4NodeEE14deleteNodeNameEi@Base 2.4.1
- _ZN3bpp12TreeTemplateINS_4NodeEE14getTotalLengthEv@Base 2.4.1
- 
_ZN3bpp12TreeTemplateINS_4NodeEE15getNodePropertyEiRKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE@Base
 2.4.1
- 
_ZN3bpp12TreeTemplateINS_4NodeEE15setNodePropertyEiRKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEERKNS_8ClonableE@Base
 2.4.1
- _ZN3bpp12TreeTemplateINS_4NodeEE16getBranchLengthsEv@Base 2.4.1
- _ZN3bpp12TreeTemplateINS_4NodeEE16setBranchLengthsEd@Base 2.4.1
- 
_ZN3bpp12TreeTemplateINS_4NodeEE17getBranchPropertyEiRKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE@Base
 2.4.1
- 
_ZN3bpp12TreeTemplateINS_4NodeEE17setBranchPropertyEiRKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEERKNS_8ClonableE@Base
 2.4.1
- 

Bug#1062238: libbpp-raa: NMU diff for 64-bit time_t transition

[Steve Langasek]

Hello,

The package that was previously uploaded to experimental was unfortunately
broken because we did not notice that the package uses d-shlibs and
therefore needs additional changes.  (Most packages using d-shlibs simply
failed to build without additional changes; libbpp-raa built but produced an
empty package.)

Please find a fixed patch attached.

-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developer   https://www.debian.org/
slanga...@ubuntu.com vor...@debian.org
diff -Nru libbpp-raa-2.4.1/debian/changelog libbpp-raa-2.4.1/debian/changelog
--- libbpp-raa-2.4.1/debian/changelog   2022-11-26 07:06:31.0 +
+++ libbpp-raa-2.4.1/debian/changelog   2024-02-24 07:14:09.0 +
@@ -1,3 +1,16 @@
+libbpp-raa (2.4.1-7.1~exp2) experimental; urgency=medium
+
+  * Bump d-shlibs build-dependency for --t64 support.
+
+ -- Steve Langasek   Sat, 24 Feb 2024 07:14:09 +
+
+libbpp-raa (2.4.1-7.1~exp1) experimental; urgency=medium
+
+  * Non-maintainer upload.
+  * Rename libraries for 64-bit time_t transition.
+
+ -- Steve Langasek   Wed, 31 Jan 2024 20:05:30 +
+
 libbpp-raa (2.4.1-7) unstable; urgency=medium
 
   * Fix watch file
diff -Nru libbpp-raa-2.4.1/debian/control libbpp-raa-2.4.1/debian/control
--- libbpp-raa-2.4.1/debian/control 2022-11-26 07:06:31.0 +
+++ libbpp-raa-2.4.1/debian/control 2024-02-24 07:14:08.0 +
@@ -6,7 +6,7 @@
 Priority: optional
 Build-Depends: debhelper-compat (= 13),
cmake,
-   d-shlibs,
+   d-shlibs (>= 0.106~),
zlib1g-dev,
libbpp-seq-dev
 Standards-Version: 4.6.1
@@ -18,7 +18,7 @@
 Package: libbpp-raa-dev
 Architecture: any
 Section: libdevel
-Depends: libbpp-raa4 (= ${binary:Version}),
+Depends: libbpp-raa4t64 (= ${binary:Version}),
  ${misc:Depends},
  libbpp-seq-dev
 Multi-Arch: same
@@ -29,7 +29,10 @@
  .
  This package contains header files and static library.
 
-Package: libbpp-raa4
+Package: libbpp-raa4t64
+Provides: ${t64:Provides}
+Replaces: libbpp-raa4
+Conflicts: libbpp-raa4 (<< ${source:Version})
 Architecture: any
 Section: libs
 Depends: ${shlibs:Depends},
diff -Nru libbpp-raa-2.4.1/debian/libbpp-raa4.symbols.amd64 
libbpp-raa-2.4.1/debian/libbpp-raa4.symbols.amd64
--- libbpp-raa-2.4.1/debian/libbpp-raa4.symbols.amd64   2022-11-26 
07:06:31.0 +
+++ libbpp-raa-2.4.1/debian/libbpp-raa4.symbols.amd64   1970-01-01 
00:00:00.0 +
@@ -1,186 +0,0 @@
-libbpp-raa.so.4 libbpp-raa4 #MINVER#
- _ZN3bpp14RaaSpeciesTree10firstChildEi@Base 2.4.1
- _ZN3bpp14RaaSpeciesTree11nextSynonymEi@Base 2.4.1
- _ZN3bpp14RaaSpeciesTree5countEi@Base 2.4.1
- _ZN3bpp14RaaSpeciesTree5labelB5cxx11Ei@Base 2.4.1
- _ZN3bpp14RaaSpeciesTree6getTidEi@Base 2.4.1
- _ZN3bpp14RaaSpeciesTree6parentEi@Base 2.4.1
- _ZN3bpp14RaaSpeciesTree7getNameB5cxx11Ei@Base 2.4.1
- _ZN3bpp14RaaSpeciesTree7isChildEii@Base 2.4.1
- 
_ZN3bpp14RaaSpeciesTree8findNodeERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEEb@Base
 2.4.1
- _ZN3bpp14RaaSpeciesTree8findNodeEi@Base 2.4.1
- _ZN3bpp14RaaSpeciesTree8getMajorEi@Base 2.4.1
- _ZN3bpp14RaaSpeciesTree9nextChildEii@Base 2.4.1
- _ZN3bpp16BadCharExceptionD0Ev@Base 2.4.1
- _ZN3bpp16BadCharExceptionD1Ev@Base 2.4.1
- _ZN3bpp16BadCharExceptionD2Ev@Base 2.4.1
- _ZN3bpp17AlphabetExceptionD0Ev@Base 2.4.1
- _ZN3bpp17AlphabetExceptionD1Ev@Base 2.4.1
- _ZN3bpp17AlphabetExceptionD2Ev@Base 2.4.1
- _ZN3bpp3RAA10deleteListEPNS_7RaaListE@Base 2.4.1
- 
_ZN3bpp3RAA10getSeqFragERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEEiiRS6_@Base
 2.4.1
- 
_ZN3bpp3RAA10getSeqFragEiiiRNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE@Base
 2.4.1
- 
_ZN3bpp3RAA11getSeq_bothERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEEii@Base
 2.4.1
- 
_ZN3bpp3RAA12openDatabaseERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEEPFPcPvESA_@Base
 2.4.1
- 
_ZN3bpp3RAA12processQueryERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEES8_@Base
 2.4.1
- 
_ZN3bpp3RAA12translateCDSERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE@Base
 2.4.1
- _ZN3bpp3RAA12translateCDSEi@Base 2.4.1
- _ZN3bpp3RAA13closeDatabaseEv@Base 2.4.1
- 
_ZN3bpp3RAA13getAttributesERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE@Base
 2.4.1
- _ZN3bpp3RAA13getAttributesEi@Base 2.4.1
- _ZN3bpp3RAA14getNextFeatureEPv@Base 2.4.1
- 
_ZN3bpp3RAA14keywordPatternERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE@Base
 2.4.1
- 
_ZN3bpp3RAA14knownDatabasesERSt6vectorINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESaIS7_EESA_@Base
 2.4.1
- 
_ZN3bpp3RAA15createEmptyListERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEES8_@Base
 2.4.1
- _ZN3bpp3RAA15freeSpeciesTreeEPNS_14RaaSpeciesTreeE@Base 2.4.1
- _ZN3bpp3RAA15loadSpeciesTreeEb@Base 2.4.1
- 

Bug#1062232: libbpp-phyl-omics: NMU diff for 64-bit time_t transition

[Steve Langasek]

Hello,

The package that was previously uploaded to experimental was unfortunately
broken because we did not notice that the package uses d-shlibs and
therefore needs additional changes.  (Most packages using d-shlibs simply
failed to build without additional changes; libbpp-phyl-omics built but
produced an empty package.)

Please find a fixed patch attached.

-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developer   https://www.debian.org/
slanga...@ubuntu.com vor...@debian.org


signature.asc
Description: PGP signature

Bug#1062237: libbpp-qt: NMU diff for 64-bit time_t transition

[Steve Langasek]

Hello,

The package that was previously uploaded to experimental was unfortunately
broken because we did not notice that the package uses d-shlibs and
therefore needs additional changes.  (Most packages using d-shlibs simply
failed to build without additional changes; libbpp-qt built but
produced an empty package.)

Please find a fixed patch attached.

-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developer   https://www.debian.org/
slanga...@ubuntu.com vor...@debian.org
diff -Nru libbpp-qt-2.4.1/debian/changelog libbpp-qt-2.4.1/debian/changelog
--- libbpp-qt-2.4.1/debian/changelog2023-08-13 18:33:06.0 +
+++ libbpp-qt-2.4.1/debian/changelog2024-02-24 07:12:40.0 +
@@ -1,3 +1,16 @@
+libbpp-qt (2.4.1-9.1~exp2) experimental; urgency=medium
+
+  * Bump d-shlibs build-dependency for --t64 support.
+
+ -- Steve Langasek   Sat, 24 Feb 2024 07:12:40 +
+
+libbpp-qt (2.4.1-9.1~exp1) experimental; urgency=medium
+
+  * Non-maintainer upload.
+  * Rename libraries for 64-bit time_t transition.
+
+ -- Steve Langasek   Wed, 31 Jan 2024 20:04:47 +
+
 libbpp-qt (2.4.1-9) unstable; urgency=medium
 
   * Team upload.
diff -Nru libbpp-qt-2.4.1/debian/control libbpp-qt-2.4.1/debian/control
--- libbpp-qt-2.4.1/debian/control  2023-08-13 18:32:54.0 +
+++ libbpp-qt-2.4.1/debian/control  2024-02-24 07:12:39.0 +
@@ -6,7 +6,7 @@
 Priority: optional
 Build-Depends: debhelper-compat (= 13),
cmake,
-   d-shlibs,
+   d-shlibs (>= 0.106~),
qt5-qmake,
qtdeclarative5-dev,
libbpp-phyl-dev
@@ -19,7 +19,7 @@
 Package: libbpp-qt-dev
 Architecture: any
 Section: libdevel
-Depends: libbpp-qt2 (= ${binary:Version}),
+Depends: libbpp-qt2t64 (= ${binary:Version}),
  ${misc:Depends},
  ${devlibs:Depends}
 Multi-Arch: same
@@ -33,7 +33,10 @@
  Contains development files of the Bio++ graphical classes developed
  with Qt.
 
-Package: libbpp-qt2
+Package: libbpp-qt2t64
+Provides: ${t64:Provides}
+Replaces: libbpp-qt2
+Conflicts: libbpp-qt2 (<< ${source:Version})
 Architecture: any
 Section: libs
 Depends: ${shlibs:Depends},
diff -Nru libbpp-qt-2.4.1/debian/libbpp-qt2.symbols.amd64 
libbpp-qt-2.4.1/debian/libbpp-qt2.symbols.amd64
--- libbpp-qt-2.4.1/debian/libbpp-qt2.symbols.amd64 2023-08-13 
18:15:22.0 +
+++ libbpp-qt-2.4.1/debian/libbpp-qt2.symbols.amd64 1970-01-01 
00:00:00.0 +
@@ -1,594 +0,0 @@
-libbpp-qt.so.2 libbpp-qt2 #MINVER#
-* Build-Depends-Package: libbpp-qt-dev
- _ZN3bpp10TreeCanvas10searchTextERK7QString@Base 2.4.1
- _ZN3bpp10TreeCanvas11qt_metacallEN11QMetaObject4CallEiPPv@Base 2.4.1
- _ZN3bpp10TreeCanvas11qt_metacastEPKc@Base 2.4.1
- _ZN3bpp10TreeCanvas14drawingChangedEv@Base 2.4.1
- _ZN3bpp10TreeCanvas14getTreeDrawingEv@Base 2.4.1
- _ZN3bpp10TreeCanvas14mouseMoveEventEP11QMouseEvent@Base 2.4.1
- _ZN3bpp10TreeCanvas14setDrawingSizeEjj@Base 2.4.1
- _ZN3bpp10TreeCanvas14setTreeDrawingERKNS_11TreeDrawingEb@Base 2.4.1
- _ZN3bpp10TreeCanvas15mousePressEventEP11QMouseEvent@Base 2.4.1
- _ZN3bpp10TreeCanvas16staticMetaObjectE@Base 2.4.1
- _ZN3bpp10TreeCanvas17mouseReleaseEventEP11QMouseEvent@Base 2.4.1
- _ZN3bpp10TreeCanvas21mouseDoubleClickEventEP11QMouseEvent@Base 2.4.1
- _ZN3bpp10TreeCanvas6redrawEv@Base 2.4.1
- _ZN3bpp10TreeCanvas7setTreeEPKNS_4TreeE@Base 2.4.1
- _ZN3bpp10TreeCanvas9getDeviceEv@Base 2.4.1
- _ZN3bpp10TreeCanvasC1EP7QWidget@Base 2.4.1
- _ZN3bpp10TreeCanvasC2EP7QWidget@Base 2.4.1
- _ZN3bpp10TreeCanvasD0Ev@Base 2.4.1
- _ZN3bpp10TreeCanvasD1Ev@Base 2.4.1
- _ZN3bpp10TreeCanvasD2Ev@Base 2.4.1
- _ZN3bpp12MouseAdapter14mouseMoveEventEP11QMouseEvent@Base 2.4.1
- _ZN3bpp12MouseAdapter15mousePressEventEP11QMouseEvent@Base 2.4.1
- _ZN3bpp12MouseAdapter17mouseReleaseEventEP11QMouseEvent@Base 2.4.1
- _ZN3bpp12MouseAdapter21mouseDoubleClickEventEP11QMouseEvent@Base 2.4.1
- _ZN3bpp12NodeTemplateINS_19TreeDrawingNodeInfoEE12removeFatherEv@Base 2.4.1
- _ZN3bpp12NodeTemplateINS_19TreeDrawingNodeInfoEE6getSonEm@Base 2.4.1
- _ZN3bpp12NodeTemplateINS_19TreeDrawingNodeInfoEE8getInfosEv@Base 2.4.1
- _ZN3bpp12NodeTemplateINS_19TreeDrawingNodeInfoEE8setInfosERKS1_@Base 2.4.1
- _ZN3bpp12NodeTemplateINS_19TreeDrawingNodeInfoEE9getFatherEv@Base 2.4.1
- _ZN3bpp12NodeTemplateINS_19TreeDrawingNodeInfoEED0Ev@Base 2.4.1
- _ZN3bpp12NodeTemplateINS_19TreeDrawingNodeInfoEED1Ev@Base 2.4.1
- _ZN3bpp12NodeTemplateINS_19TreeDrawingNodeInfoEED2Ev@Base 2.4.1
- 
_ZN3bpp12TreeTemplateINS_12NodeTemplateINS_19TreeDrawingNodeInfo11getRootNodeEv@Base
 2.4.1
- 
_ZN3bpp12TreeTemplateINS_12NodeTemplateINS_19TreeDrawingNodeInfo11newOutGroupEPS3_@Base
 2.4.1
- 
_ZN3bpp12TreeTemplateINS_12NodeTemplateINS_19TreeDrawingNodeInfo11newOutGroupEi@Base
 2.4.1
- 

Bug#1064166: ldc: NMU diff for 64-bit time_t transition

[Matthias Klumpp]

Am Sa., 24. Feb. 2024 um 08:00 Uhr schrieb Steve Langasek :
>
> Hi Matthias,
>
> I see you've implemented this as:
>
> ifneq (,$(filter $(DEB_HOST_ARCH), armhf))
> export DEB_BUILD_MAINT_OPTIONS += abi=+time64,+lfs
> endif
>
> Please note that armhf is not the only architecture affected by this ABI
> change: armel is also a release architecture affected, and there are a
> number of other 32-bit ports architectures which are affected (hppa,
> powerpc, ...)

I know, but LDC does not exist on these architectures ;-)

Cheers,
Matthias

-- 
I welcome VSRE emails. See http://vsre.info/

Bug#1062229: libbigwig: NMU diff for 64-bit time_t transition

[Steve Langasek]

Hello,

The package that was previously uploaded to experimental was unfortunately
broken because we did not notice that the package uses d-shlibs and
therefore needs additional changes.  (Most packages using d-shlibs simply
failed to build without additional changes; camp built but produced an empty
package.)

Please find a fixed patch attached.

-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developer   https://www.debian.org/
slanga...@ubuntu.com vor...@debian.org
diff -Nru libbigwig-0.4.7+dfsg/debian/changelog 
libbigwig-0.4.7+dfsg/debian/changelog
--- libbigwig-0.4.7+dfsg/debian/changelog   2022-09-10 07:33:51.0 
+
+++ libbigwig-0.4.7+dfsg/debian/changelog   2024-02-24 06:58:05.0 
+
@@ -1,3 +1,16 @@
+libbigwig (0.4.7+dfsg-3.1~exp2) experimental; urgency=medium
+
+  * Bump d-shlibs build-dependency for --t64 support
+
+ -- Steve Langasek   Sat, 24 Feb 2024 06:58:05 +
+
+libbigwig (0.4.7+dfsg-3.1~exp1) experimental; urgency=medium
+
+  * Non-maintainer upload.
+  * Rename libraries for 64-bit time_t transition.
+
+ -- Steve Langasek   Wed, 31 Jan 2024 19:51:41 +
+
 libbigwig (0.4.7+dfsg-3) unstable; urgency=medium
 
   * Team upload.
diff -Nru libbigwig-0.4.7+dfsg/debian/control 
libbigwig-0.4.7+dfsg/debian/control
--- libbigwig-0.4.7+dfsg/debian/control 2022-08-29 16:56:21.0 +
+++ libbigwig-0.4.7+dfsg/debian/control 2024-02-24 06:57:51.0 +
@@ -4,7 +4,7 @@
 Section: science
 Priority: optional
 Build-Depends: debhelper-compat (= 13),
-   d-shlibs,
+   d-shlibs (>= 0.106~),
libcurl4-gnutls-dev|libcurl-dev,
zlib1g-dev
 Build-Depends-Indep: doxygen
@@ -14,7 +14,10 @@
 Homepage: https://github.com/dpryan79/libBigWig/
 Rules-Requires-Root: no
 
-Package: libbigwig0
+Package: libbigwig0t64
+Provides: ${t64:Provides}
+Replaces: libbigwig0
+Conflicts: libbigwig0 (<< ${source:Version})
 Architecture: any
 Section: libs
 Multi-Arch: same
@@ -31,7 +34,7 @@
 Architecture: any
 Multi-Arch: same
 Section: libdevel
-Depends: libbigwig0 (= ${binary:Version}),
+Depends: libbigwig0t64 (= ${binary:Version}),
  ${misc:Depends}
 Description: C library for handling bigWig files - header files
  This package provides the files needed to develop with the libBigWig
diff -Nru libbigwig-0.4.7+dfsg/debian/libbigwig0.symbols 
libbigwig-0.4.7+dfsg/debian/libbigwig0.symbols
--- libbigwig-0.4.7+dfsg/debian/libbigwig0.symbols  2022-08-29 
16:52:07.0 +
+++ libbigwig-0.4.7+dfsg/debian/libbigwig0.symbols  1970-01-01 
00:00:00.0 +
@@ -1,66 +0,0 @@
-libBigWig.so.0 libbigwig0 #MINVER#
- GLOBAL_DEFAULTBUFFERSIZE@Base 0.4.6
- addIntervalValue@Base 0.4.6
- bbDestroyOverlappingEntries@Base 0.4.6
- bbGetOverlappingEntries@Base 0.4.6
- bbGetOverlappingEntriesCore@Base 0.4.6
- bbGetSQL@Base 0.4.6
- bbIsBigBed@Base 0.4.6
- bbOpen@Base 0.4.6
- bbOverlappingEntriesIterator@Base 0.4.6
- bwAddIntervalSpanSteps@Base 0.4.6
- bwAddIntervalSpans@Base 0.4.6
- bwAddIntervals@Base 0.4.6
- bwAppendIntervalSpanSteps@Base 0.4.6
- bwAppendIntervalSpans@Base 0.4.6
- bwAppendIntervals@Base 0.4.6
- bwCleanup@Base 0.4.6
- bwClose@Base 0.4.6
- bwCreateChromList@Base 0.4.6
- bwCreateHdr@Base 0.4.6
- bwDestroyIndex@Base 0.4.6
- bwDestroyIndexNode@Base 0.4.6
- bwDestroyOverlappingIntervals@Base 0.4.6
- bwFillBuffer@Base 0.4.6
- bwFillDataHdr@Base 0.4.6
- bwFinalize@Base 0.4.6
- bwGetOverlappingIntervals@Base 0.4.6
- bwGetOverlappingIntervalsCore@Base 0.4.6
- bwGetTid@Base 0.4.6
- bwGetValues@Base 0.4.6
- bwInit@Base 0.4.6
- bwIsBigWig@Base 0.4.6
- bwIteratorDestroy@Base 0.4.6
- bwIteratorNext@Base 0.4.6
- bwOpen@Base 0.4.6
- bwOverlappingIntervalsIterator@Base 0.4.6
- bwRead@Base 0.4.6
- bwReadIndex@Base 0.4.6
- bwSetPos@Base 0.4.6
- bwStats@Base 0.4.6
- bwStatsFromFull@Base 0.4.6
- bwStrdup@Base 0.4.7
- bwTell@Base 0.4.6
- bwWriteHdr@Base 0.4.6
- constructZoomLevels@Base 0.4.6
- destroyBWOverlapBlock@Base 0.4.6
- destroyVals_t@Base 0.4.6
- getContentLength@Base 0.4.6
- getScalar@Base 0.4.6
- makeZoomLevels@Base 0.4.6
- nextPos@Base 0.4.6
- overlapsInterval@Base 0.4.6
- updateInterval@Base 0.4.6
- urlClose@Base 0.4.6
- urlFetchData@Base 0.4.6
- urlOpen@Base 0.4.6
- urlRead@Base 0.4.6
- urlSeek@Base 0.4.6
- url_fread@Base 0.4.6
- walkRTreeNodes@Base 0.4.6
- writeIndex@Base 0.4.6
- writeIndexOffsets@Base 0.4.6
- writeIndexTree@Base 0.4.6
- writeIndexTreeNode@Base 0.4.6
- writeSummary@Base 0.4.6
- writeZoomLevels@Base 0.4.6
diff -Nru libbigwig-0.4.7+dfsg/debian/libbigwig0t64.lintian-overrides 
libbigwig-0.4.7+dfsg/debian/libbigwig0t64.lintian-overrides
--- libbigwig-0.4.7+dfsg/debian/libbigwig0t64.lintian-overrides 1970-01-01 
00:00:00.0 +
+++ libbigwig-0.4.7+dfsg/debian/libbigwig0t64.lintian-overrides 2024-01-31 

Bug#1064166: ldc: NMU diff for 64-bit time_t transition

[Steve Langasek]

Hi Matthias,

I see you've implemented this as:

ifneq (,$(filter $(DEB_HOST_ARCH), armhf))
export DEB_BUILD_MAINT_OPTIONS += abi=+time64,+lfs
endif

Please note that armhf is not the only architecture affected by this ABI
change: armel is also a release architecture affected, and there are a
number of other 32-bit ports architectures which are affected (hppa,
powerpc, ...)

Thanks,
-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developer   https://www.debian.org/
slanga...@ubuntu.com vor...@debian.org


signature.asc
Description: PGP signature

Bug#1060972: telepathy-farstream: diff for NMU version 0.6.2-1.2

[pino]

Control: tags 1060972 + patch
Control: tags 1060972 + pending


Dear maintainer,

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

Regards.

diff -Nru telepathy-farstream-0.6.2/debian/changelog 
telepathy-farstream-0.6.2/debian/changelog
--- telepathy-farstream-0.6.2/debian/changelog  2021-01-01 14:35:16.0 
+0100
+++ telepathy-farstream-0.6.2/debian/changelog  2024-02-24 07:37:17.0 
+0100
@@ -1,3 +1,11 @@
+telepathy-farstream (0.6.2-1.2) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Add the gir1.2-glib-2.0-dev build dependency, needed for GObject-2.0.gir.
+(Closes: #1060972)
+
+ -- Pino Toscano   Sat, 24 Feb 2024 07:37:17 +0100
+
 telepathy-farstream (0.6.2-1.1) unstable; urgency=medium
 
   * Non maintainer upload by the Reproducible Builds team.
diff -Nru telepathy-farstream-0.6.2/debian/control 
telepathy-farstream-0.6.2/debian/control
--- telepathy-farstream-0.6.2/debian/control2014-09-16 20:02:51.0 
+0200
+++ telepathy-farstream-0.6.2/debian/control2024-02-24 07:31:51.0 
+0100
@@ -12,6 +12,7 @@
libfarstream-0.2-dev (>= 0.2.0),
libtelepathy-glib-dev (>= 0.19.0),
gobject-introspection,
+   gir1.2-glib-2.0-dev,
gtk-doc-tools
 Standards-Version: 3.9.5
 Homepage: http://telepathy.freedesktop.org/

Bug#1062341: highwayhash: NMU diff for 64-bit time_t transition

[Steve Langasek]

The previous patch unfortunately resulted in a misbuild where the library
was not actually included in the package.  Please see attached a corrected
patch.

-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developer   https://www.debian.org/
slanga...@ubuntu.com vor...@debian.org
diff -Nru highwayhash-0~git20200803.9490b14/debian/changelog 
highwayhash-0~git20200803.9490b14/debian/changelog
--- highwayhash-0~git20200803.9490b14/debian/changelog  2023-12-10 
21:46:41.0 +
+++ highwayhash-0~git20200803.9490b14/debian/changelog  2024-02-24 
06:37:15.0 +
@@ -1,3 +1,16 @@
+highwayhash (0~git20200803.9490b14-4.1~exp2) experimental; urgency=medium
+
+  * debian/rules: install the library in the correct path.
+
+ -- Steve Langasek   Sat, 24 Feb 2024 06:37:15 +
+
+highwayhash (0~git20200803.9490b14-4.1~exp1) experimental; urgency=medium
+
+  * Non-maintainer upload.
+  * Rename libraries for 64-bit time_t transition.
+
+ -- Graham Inggs   Thu, 01 Feb 2024 05:55:48 +
+
 highwayhash (0~git20200803.9490b14-4) unstable; urgency=medium
 
   * Orphan this package. (See #1013208)
diff -Nru highwayhash-0~git20200803.9490b14/debian/control 
highwayhash-0~git20200803.9490b14/debian/control
--- highwayhash-0~git20200803.9490b14/debian/control2023-12-10 
21:46:17.0 +
+++ highwayhash-0~git20200803.9490b14/debian/control2024-02-01 
05:55:48.0 +
@@ -12,7 +12,7 @@
 Package: libhighwayhash-dev
 Section: libdevel
 Architecture: any
-Depends: ${misc:Depends}, libhighwayhash0 (= ${binary:Version})
+Depends: ${misc:Depends}, libhighwayhash0t64 (= ${binary:Version})
 Multi-Arch: same
 Description: Fast strong hash functions: SipHash/HighwayHash (development)
  Highwayhash provides three 'strong' (well-distributed and unpredictable)
@@ -33,7 +33,10 @@
  .
  This package ships the static library and development files.
 
-Package: libhighwayhash0
+Package: libhighwayhash0t64
+Provides: ${t64:Provides}
+Replaces: libhighwayhash0
+Breaks: libhighwayhash0 (<< ${source:Version})
 Section: libs
 Architecture: any
 Multi-Arch: same
diff -Nru 
highwayhash-0~git20200803.9490b14/debian/libhighwayhash0t64.lintian-overrides 
highwayhash-0~git20200803.9490b14/debian/libhighwayhash0t64.lintian-overrides
--- 
highwayhash-0~git20200803.9490b14/debian/libhighwayhash0t64.lintian-overrides   
1970-01-01 00:00:00.0 +
+++ 
highwayhash-0~git20200803.9490b14/debian/libhighwayhash0t64.lintian-overrides   
2024-02-01 05:55:48.0 +
@@ -0,0 +1 @@
+libhighwayhash0t64: package-name-doesnt-match-sonames libhighwayhash0
diff -Nru highwayhash-0~git20200803.9490b14/debian/rules 
highwayhash-0~git20200803.9490b14/debian/rules
--- highwayhash-0~git20200803.9490b14/debian/rules  2023-12-10 
21:36:43.0 +
+++ highwayhash-0~git20200803.9490b14/debian/rules  2024-02-24 
06:36:59.0 +
@@ -39,10 +39,10 @@
 
 override_dh_auto_install:
dh_auto_install
-   mkdir -p debian/libhighwayhash0/usr/lib/$(DEB_HOST_MULTIARCH)
+   mkdir -p debian/libhighwayhash0t64/usr/lib/$(DEB_HOST_MULTIARCH)
rename 's/.so/.so.0/' debian/tmp/usr/lib/$(DEB_HOST_MULTIARCH)/*.so
install -m0755 debian/tmp/usr/lib/$(DEB_HOST_MULTIARCH)/*.so.0 \
-   debian/libhighwayhash0/usr/lib/$(DEB_HOST_MULTIARCH)/
+   debian/libhighwayhash0t64/usr/lib/$(DEB_HOST_MULTIARCH)/
mkdir -p debian/libhighwayhash-dev/usr/lib/$(DEB_HOST_MULTIARCH)
install -m0755 debian/tmp/usr/lib/$(DEB_HOST_MULTIARCH)/*.a \
debian/libhighwayhash-dev/usr/lib/$(DEB_HOST_MULTIARCH)/


signature.asc
Description: PGP signature

Bug#1062183: gnuastro: NMU diff for 64-bit time_t transition

[Steve Langasek]

Please find attached an updated patch rebased against the current unstable
version.

-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developer   https://www.debian.org/
slanga...@ubuntu.com vor...@debian.org
diff -Nru gnuastro-0.22/debian/changelog gnuastro-0.22/debian/changelog
--- gnuastro-0.22/debian/changelog  2024-02-20 08:43:34.0 +
+++ gnuastro-0.22/debian/changelog  2024-02-24 06:20:51.0 +
@@ -1,3 +1,10 @@
+gnuastro (0.22-3.1~exp1) experimental; urgency=medium
+
+  * Non-maintainer upload.
+  * Rename libraries for 64-bit time_t transition.
+
+ -- Steve Langasek   Sat, 24 Feb 2024 06:20:51 +
+
 gnuastro (0.22-3) unstable; urgency=medium
 
   * 'd/control': Drop not required 'libtool-bin' Build-Depends.
diff -Nru gnuastro-0.22/debian/control gnuastro-0.22/debian/control
--- gnuastro-0.22/debian/control2024-02-20 08:43:34.0 +
+++ gnuastro-0.22/debian/control2024-02-24 06:20:36.0 +
@@ -19,11 +19,14 @@
 Vcs-Git: https://salsa.debian.org/debian-astro-team/gnuastro.git
 Vcs-Browser: https://salsa.debian.org/debian-astro-team/gnuastro
 
-Package: libgnuastro20
+Package: libgnuastro20t64
+Provides: ${t64:Provides}
 Replaces: libgnuastro17,
-  libgnuastro18
+  libgnuastro18,
+  libgnuastro20
 Breaks: libgnuastro17 (<< ${source:Version}),
-libgnuastro18 (<< ${source:Version})
+libgnuastro18 (<< ${source:Version}),
+libgnuastro20 (<< ${source:Version})
 Architecture: any
 Section: libs
 Multi-Arch: same
@@ -39,7 +42,7 @@
 Package: libgnuastro-dev
 Architecture: any
 Section: libdevel
-Depends: libgnuastro20 (= ${binary:Version}), ${misc:Depends}
+Depends: libgnuastro20t64 (= ${binary:Version}), ${misc:Depends}
 Description: GNU Astronomy Utilities development files
  GNU Astronomy Utilities (Gnuastro) is a collection of libraries and programs
  for astronomical data analysis and manipulation. The programs can be run on
@@ -50,7 +53,7 @@
 
 Package: gnuastro
 Architecture: any
-Depends: libgnuastro20 (= ${binary:Version}), ${misc:Depends}, 
${shlibs:Depends}
+Depends: libgnuastro20t64 (= ${binary:Version}), ${misc:Depends}, 
${shlibs:Depends}
 Description: GNU Astronomy Utilities programs
  GNU Astronomy Utilities (Gnuastro) is a collection of libraries and programs
  for astronomical data analysis and manipulation. The programs can be run on
diff -Nru gnuastro-0.22/debian/libgnuastro20.install 
gnuastro-0.22/debian/libgnuastro20.install
--- gnuastro-0.22/debian/libgnuastro20.install  2024-02-19 15:35:40.0 
+
+++ gnuastro-0.22/debian/libgnuastro20.install  1970-01-01 00:00:00.0 
+
@@ -1,7 +0,0 @@
-usr/lib/*/libgnuastro*.so.*
-
-# This is a GNU Make extension library for using Gnuastro's library directly
-# with Makefiles without having to use '$(shell ...)'. See:
-#   https://www.gnu.org/software/make/manual/html_node/Loading-Objects.html
-usr/lib/*/libgnuastro_make.so
-usr/lib/*/libgnuastro_make*.so.*
diff -Nru gnuastro-0.22/debian/libgnuastro20t64.install 
gnuastro-0.22/debian/libgnuastro20t64.install
--- gnuastro-0.22/debian/libgnuastro20t64.install   1970-01-01 
00:00:00.0 +
+++ gnuastro-0.22/debian/libgnuastro20t64.install   2024-02-19 
15:35:40.0 +
@@ -0,0 +1,7 @@
+usr/lib/*/libgnuastro*.so.*
+
+# This is a GNU Make extension library for using Gnuastro's library directly
+# with Makefiles without having to use '$(shell ...)'. See:
+#   https://www.gnu.org/software/make/manual/html_node/Loading-Objects.html
+usr/lib/*/libgnuastro_make.so
+usr/lib/*/libgnuastro_make*.so.*
diff -Nru gnuastro-0.22/debian/libgnuastro20t64.lintian-overrides 
gnuastro-0.22/debian/libgnuastro20t64.lintian-overrides
--- gnuastro-0.22/debian/libgnuastro20t64.lintian-overrides 1970-01-01 
00:00:00.0 +
+++ gnuastro-0.22/debian/libgnuastro20t64.lintian-overrides 2024-02-24 
06:19:22.0 +
@@ -0,0 +1 @@
+libgnuastro20t64: package-name-doesnt-match-sonames libgnuastro20


signature.asc
Description: PGP signature

Bug#1062141: globus-common: NMU diff for 64-bit time_t transition

[Steve Langasek]

Please find attached an updated patch rebased on the current unstable
version of globus-common.

-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developer   https://www.debian.org/
slanga...@ubuntu.com vor...@debian.org
diff -Nru globus-common-18.14/debian/changelog 
globus-common-18.14/debian/changelog
--- globus-common-18.14/debian/changelog2024-02-09 10:13:35.0 
+
+++ globus-common-18.14/debian/changelog2024-02-24 06:12:53.0 
+
@@ -1,3 +1,10 @@
+globus-common (18.14-1.1~exp1) experimental; urgency=medium
+
+  * Non-maintainer upload.
+  * Rename libraries for 64-bit time_t transition.
+
+ -- Steve Langasek   Sat, 24 Feb 2024 06:12:53 +
+
 globus-common (18.14-1) unstable; urgency=medium
 
   * New GCT release v6.2.20240202
diff -Nru globus-common-18.14/debian/control globus-common-18.14/debian/control
--- globus-common-18.14/debian/control  2024-02-09 10:13:35.0 +
+++ globus-common-18.14/debian/control  2024-02-24 06:11:51.0 +
@@ -13,7 +13,10 @@
 Vcs-Git: https://salsa.debian.org/ellert/globus-common.git
 Homepage: https://github.com/gridcf/gct/
 
-Package: libglobus-common0
+Package: libglobus-common0t64
+Provides: ${t64:Provides}
+Breaks: libglobus-common0 (<< ${source:Version})
+Replaces: libglobus-common0
 Section: libs
 Architecture: any
 Multi-Arch: same
@@ -30,7 +33,7 @@
  Community Forum (GridCF) that provides community-based support for core
  software packages in grid computing.
  .
- The libglobus-common0 package contains:
+ The libglobus-common0t64 package contains:
  Common Library
 
 Package: globus-common-progs
@@ -38,7 +41,7 @@
 Architecture: any
 Multi-Arch: foreign
 Depends:
- libglobus-common0 (= ${binary:Version}),
+ libglobus-common0t64 (= ${binary:Version}),
  ${shlibs:Depends},
  ${misc:Depends}
 Description: Grid Community Toolkit - Common Library Programs
@@ -56,7 +59,7 @@
 Architecture: any
 Multi-Arch: same
 Depends:
- libglobus-common0 (= ${binary:Version}),
+ libglobus-common0t64 (= ${binary:Version}),
  ${misc:Depends},
  ${perl:Depends},
  libltdl-dev
diff -Nru globus-common-18.14/debian/libglobus-common0.docs 
globus-common-18.14/debian/libglobus-common0.docs
--- globus-common-18.14/debian/libglobus-common0.docs   2019-07-11 
13:15:01.0 +
+++ globus-common-18.14/debian/libglobus-common0.docs   1970-01-01 
00:00:00.0 +
@@ -1 +0,0 @@
-debian/README
diff -Nru globus-common-18.14/debian/libglobus-common0.install 
globus-common-18.14/debian/libglobus-common0.install
--- globus-common-18.14/debian/libglobus-common0.install2020-12-12 
15:26:25.0 +
+++ globus-common-18.14/debian/libglobus-common0.install1970-01-01 
00:00:00.0 +
@@ -1,5 +0,0 @@
-/usr/lib/*/libglobus_common.so.*
-/usr/lib/*/libglobus_memory_debug.so.*
-/usr/lib/*/libglobus_thread_pthread.so
-/usr/share/perl5/Globus/Core/Config.pm
-/usr/share/perl5/Globus/Core/Paths.pm
diff -Nru globus-common-18.14/debian/libglobus-common0.lintian-overrides 
globus-common-18.14/debian/libglobus-common0.lintian-overrides
--- globus-common-18.14/debian/libglobus-common0.lintian-overrides  
2018-03-02 17:15:08.0 +
+++ globus-common-18.14/debian/libglobus-common0.lintian-overrides  
1970-01-01 00:00:00.0 +
@@ -1,3 +0,0 @@
-# This is a loadable plugin - unversioned soname expected
-dev-pkg-without-shlib-symlink */libglobus_thread_pthread.so *
-shlib-without-versioned-soname */libglobus_thread_pthread.so *
diff -Nru globus-common-18.14/debian/libglobus-common0.shlibs 
globus-common-18.14/debian/libglobus-common0.shlibs
--- globus-common-18.14/debian/libglobus-common0.shlibs 2018-03-02 
17:15:08.0 +
+++ globus-common-18.14/debian/libglobus-common0.shlibs 1970-01-01 
00:00:00.0 +
@@ -1,2 +0,0 @@
-libglobus_common 0 libglobus-common0 (>= 17)
-libglobus_memory_debug 0 libglobus-common0 (>= 17)
diff -Nru globus-common-18.14/debian/libglobus-common0t64.docs 
globus-common-18.14/debian/libglobus-common0t64.docs
--- globus-common-18.14/debian/libglobus-common0t64.docs1970-01-01 
00:00:00.0 +
+++ globus-common-18.14/debian/libglobus-common0t64.docs2024-02-24 
06:10:50.0 +
@@ -0,0 +1 @@
+debian/README
diff -Nru globus-common-18.14/debian/libglobus-common0t64.install 
globus-common-18.14/debian/libglobus-common0t64.install
--- globus-common-18.14/debian/libglobus-common0t64.install 1970-01-01 
00:00:00.0 +
+++ globus-common-18.14/debian/libglobus-common0t64.install 2024-02-24 
06:10:50.0 +
@@ -0,0 +1,5 @@
+/usr/lib/*/libglobus_common.so.*
+/usr/lib/*/libglobus_memory_debug.so.*
+/usr/lib/*/libglobus_thread_pthread.so
+/usr/share/perl5/Globus/Core/Config.pm
+/usr/share/perl5/Globus/Core/Paths.pm
diff -Nru 

Bug#1062097: gensio: NMU diff for 64-bit time_t transition

[Steve Langasek]

Please find attached an updated patch for the latest gensio in unstable.

-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developer   https://www.debian.org/
slanga...@ubuntu.com vor...@debian.org


signature.asc
Description: PGP signature

Bug#1064128: your mail

[Kyle Robbertze]

I'm working on upgrading with disabled gstreamer. Removing the optional 
dependency is not sufficient, which is how it used to work - it still fails at 
the same point. Either way, fixing this is not the only issue currently. 
ocaml-lastfm needs fixing first before liquidsoap can migrate to testing [1]. 
If upstream doesn't fix that soon, I'll just drop that and upload with a 
fixed/removed gstreamer

[1] https://github.com/savonet/ocaml-lastfm/pull/3


Cheers
Kyle

24 Feb 2024 06:27:27 Bo YU :

> Hi,
> On Fri, Feb 23, 2024 at 01:02:08PM -0300, Andreas Hasenack wrote:
>> ...and 2.2.4 also fails to build:
>> https://github.com/savonet/liquidsoap/issues/3752
> 
> Thanks.
>> 
>> $ make
>> : warning: "_FORTIFY_SOURCE" redefined
>> : note: this is the location of the previous definition
>> : warning: "_FORTIFY_SOURCE" redefined
>> : note: this is the location of the previous definition
>> : warning: "_FORTIFY_SOURCE" redefined
>> : note: this is the location of the previous definition
>> : warning: "_FORTIFY_SOURCE" redefined
>> : note: this is the location of the previous definition
>> File "src/core/decoder/gstreamer_decoder.ml", line 314, characters 37-51:
>> 314 | (Decoder.test_file ~log ~mimes:mime_types#get
>>   ^^
>> Error: This expression has type string list
>>   but an expression was expected of type string list option
>> make: *** [Makefile:4: build] Error 1
> 
> Yeah, I got this error after upgrading 2.2.4 also.
> And it seems upstream suggests to ship the package wihtout gstreamer:
> https://github.com/savonet/liquidsoap/discussions/3751#discussioncomment-8524446
> 
> It will cost more time for me how to disable this on Debian packaging.
> 
> 
> -- 
> Regards,
> -- 
>    Bo YU

Bug#1062066: gegl: NMU diff for 64-bit time_t transition

[Steve Langasek]

Updated patch against the current gegl in unstable.

-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developer   https://www.debian.org/
slanga...@ubuntu.com vor...@debian.org


signature.asc
Description: PGP signature

Bug#1062037: camp: NMU diff for 64-bit time_t transition

[Steve Langasek]

Hello,

The package that was previously uploaded to experimental was unfortunately
broken because we did not notice that the package uses d-shlibs and
therefore needs additional changes.  (Most packages using d-shlibs simply
failed to build without additional changes; camp built but produced an empty
package.)

Please find a fixed patch attached.

-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developer   https://www.debian.org/
slanga...@ubuntu.com vor...@debian.org
diff -Nru camp-0.8.4/debian/changelog camp-0.8.4/debian/changelog
--- camp-0.8.4/debian/changelog 2021-11-08 12:30:04.0 -0800
+++ camp-0.8.4/debian/changelog 2024-02-23 21:38:11.0 -0800
@@ -1,3 +1,16 @@
+camp (0.8.4-4.1~exp2) experimental; urgency=medium
+
+  * Bump d-shlibs build-dependency for --t64 support
+
+ -- Steve Langasek   Sat, 24 Feb 2024 05:38:11 +
+
+camp (0.8.4-4.1~exp1) experimental; urgency=medium
+
+  * Non-maintainer upload.
+  * Rename libraries for 64-bit time_t transition.
+
+ -- Steve Langasek   Wed, 31 Jan 2024 03:22:50 +
+
 camp (0.8.4-4) unstable; urgency=medium
 
   * Team upload.
diff -Nru camp-0.8.4/debian/control camp-0.8.4/debian/control
--- camp-0.8.4/debian/control   2021-11-08 12:30:04.0 -0800
+++ camp-0.8.4/debian/control   2024-02-23 21:38:11.0 -0800
@@ -5,7 +5,7 @@
 Priority: optional
 Build-Depends: cmake,
debhelper-compat (= 13),
-   d-shlibs,
+   d-shlibs (>= 0.106~),
libboost-dev,
libboost-test-dev,
qtbase5-dev
@@ -15,15 +15,15 @@
 Homepage: https://github.com/IRCAD/camp
 Rules-Requires-Root: no
 
-Package: libcamp0.8
+Package: libcamp0.8t64
 Architecture: any
 Multi-Arch: same
 Section: libs
 Depends: ${shlibs:Depends},
  ${misc:Depends}
-Conflicts: libcamp0.7
-Provides: libcamp0.7
-Replaces: libcamp0.7
+Conflicts: libcamp0.8 (<< ${source:Version}), libcamp0.7
+Provides: libcamp0.7, ${t64:Provides}
+Replaces: libcamp0.8, libcamp0.7
 Description: C++ multi-purpose reflection library
  CAMP is a multi-purpose reflection library developed by Technogerma Systems
  France (http://www.tegesoft.com).
@@ -50,7 +50,7 @@
 Package: libcamp-dev
 Architecture: any
 Section: libdevel
-Depends: libcamp0.8 (= ${binary:Version}),
+Depends: libcamp0.8t64 (= ${binary:Version}),
  ${shlibs:Depends},
  ${misc:Depends}
 Conflicts: libcamp0.7-dev
diff -Nru camp-0.8.4/debian/rules camp-0.8.4/debian/rules
--- camp-0.8.4/debian/rules 2021-11-08 12:30:04.0 -0800
+++ camp-0.8.4/debian/rules 2024-02-23 21:37:49.0 -0800
@@ -12,6 +12,7 @@
 override_dh_install:
dh_install
d-shlibmove \
+   --t64 \
--commit --multiarch --devunversioned --exclude-a --exclude-la \
--movedev debian/tmp/usr/include/camp usr/include \
--movedev debian/tmp/usr/include/camp-xml usr/include \


signature.asc
Description: PGP signature

Bug#1062211: android-platform-frameworks-native: NMU diff for 64-bit time_t transition

[Steve Langasek]

Hello,

An oversight with regards to the provides: handling support in debhelper
means the package in experimental does not correctly declare compatibility
on 64-bit archs with the prior ABI.  Please find an updated patch attached.

-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developer   https://www.debian.org/
slanga...@ubuntu.com vor...@debian.org
diff -Nru 
android-platform-frameworks-native-10.0.0+r36/debian/android-libetc1.docs 
android-platform-frameworks-native-10.0.0+r36/debian/android-libetc1.docs
--- android-platform-frameworks-native-10.0.0+r36/debian/android-libetc1.docs   
2020-11-22 15:26:31.0 +
+++ android-platform-frameworks-native-10.0.0+r36/debian/android-libetc1.docs   
1970-01-01 00:00:00.0 +
@@ -1 +0,0 @@
-NOTICE
diff -Nru 
android-platform-frameworks-native-10.0.0+r36/debian/android-libetc1.install 
android-platform-frameworks-native-10.0.0+r36/debian/android-libetc1.install
--- 
android-platform-frameworks-native-10.0.0+r36/debian/android-libetc1.install
2020-11-22 15:26:31.0 +
+++ 
android-platform-frameworks-native-10.0.0+r36/debian/android-libetc1.install
1970-01-01 00:00:00.0 +
@@ -1,3 +0,0 @@
-#!/usr/bin/dh-exec
-
-debian/out/libETC1.so.0   usr/lib/${DEB_HOST_MULTIARCH}/android
\ No newline at end of file
diff -Nru 
android-platform-frameworks-native-10.0.0+r36/debian/android-libetc1t64.docs 
android-platform-frameworks-native-10.0.0+r36/debian/android-libetc1t64.docs
--- 
android-platform-frameworks-native-10.0.0+r36/debian/android-libetc1t64.docs
1970-01-01 00:00:00.0 +
+++ 
android-platform-frameworks-native-10.0.0+r36/debian/android-libetc1t64.docs
2024-01-31 18:44:12.0 +
@@ -0,0 +1 @@
+NOTICE
diff -Nru 
android-platform-frameworks-native-10.0.0+r36/debian/android-libetc1t64.install 
android-platform-frameworks-native-10.0.0+r36/debian/android-libetc1t64.install
--- 
android-platform-frameworks-native-10.0.0+r36/debian/android-libetc1t64.install 
1970-01-01 00:00:00.0 +
+++ 
android-platform-frameworks-native-10.0.0+r36/debian/android-libetc1t64.install 
2024-01-31 18:44:12.0 +
@@ -0,0 +1,3 @@
+#!/usr/bin/dh-exec
+
+debian/out/libETC1.so.0   usr/lib/${DEB_HOST_MULTIARCH}/android
\ No newline at end of file
diff -Nru 
android-platform-frameworks-native-10.0.0+r36/debian/android-libetc1t64.lintian-overrides
 
android-platform-frameworks-native-10.0.0+r36/debian/android-libetc1t64.lintian-overrides
--- 
android-platform-frameworks-native-10.0.0+r36/debian/android-libetc1t64.lintian-overrides
   1970-01-01 00:00:00.0 +
+++ 
android-platform-frameworks-native-10.0.0+r36/debian/android-libetc1t64.lintian-overrides
   2024-01-31 18:44:12.0 +
@@ -0,0 +1 @@
+android-libetc1t64: package-name-doesnt-match-sonames android-libetc1
diff -Nru android-platform-frameworks-native-10.0.0+r36/debian/changelog 
android-platform-frameworks-native-10.0.0+r36/debian/changelog
--- android-platform-frameworks-native-10.0.0+r36/debian/changelog  
2020-11-22 15:40:12.0 +
+++ android-platform-frameworks-native-10.0.0+r36/debian/changelog  
2024-02-24 05:21:27.0 +
@@ -1,3 +1,16 @@
+android-platform-frameworks-native (1:10.0.0+r36-1.1~exp2) experimental; 
urgency=medium
+
+  * Set X-Time64-Compat explicitly for debhelper provides
+
+ -- Steve Langasek   Sat, 24 Feb 2024 05:21:27 +
+
+android-platform-frameworks-native (1:10.0.0+r36-1.1~exp1) experimental; 
urgency=medium
+
+  * Non-maintainer upload.
+  * Rename libraries for 64-bit time_t transition.
+
+ -- Steve Langasek   Wed, 31 Jan 2024 18:44:12 +
+
 android-platform-frameworks-native (1:10.0.0+r36-1) unstable; urgency=medium
 
   [ Roger Shimizu ]
diff -Nru android-platform-frameworks-native-10.0.0+r36/debian/control 
android-platform-frameworks-native-10.0.0+r36/debian/control
--- android-platform-frameworks-native-10.0.0+r36/debian/control
2020-11-22 15:40:12.0 +
+++ android-platform-frameworks-native-10.0.0+r36/debian/control
2024-02-24 05:21:10.0 +
@@ -24,7 +24,11 @@
  This package contains headers in include/android in platform/frameworks/native
  Consists of all the header files ranging from asset_manager.h to window.h.
 
-Package: android-libetc1
+Package: android-libetc1t64
+X-Time64-Compat: android-libetc1
+Provides: ${t64:Provides}
+Replaces: android-libetc1
+Breaks: android-libetc1 (<< ${source:Version})
 Section: libs
 Architecture: amd64 i386 armel armhf arm64 mips mipsel mips64el
 Depends: ${shlibs:Depends}, ${misc:Depends}
@@ -36,7 +40,7 @@
 Package: android-libetc1-dev
 Section: libdevel
 Architecture: amd64 i386 armel armhf arm64 mips mipsel mips64el
-Depends: android-libetc1 (= ${binary:Version}), ${misc:Depends}, 

Bug#1064128: your mail

[Bo YU]

Hi,
On Fri, Feb 23, 2024 at 01:02:08PM -0300, Andreas Hasenack wrote:

...and 2.2.4 also fails to build:
https://github.com/savonet/liquidsoap/issues/3752


Thanks.


$ make
: warning: "_FORTIFY_SOURCE" redefined
: note: this is the location of the previous definition
: warning: "_FORTIFY_SOURCE" redefined
: note: this is the location of the previous definition
: warning: "_FORTIFY_SOURCE" redefined
: note: this is the location of the previous definition
: warning: "_FORTIFY_SOURCE" redefined
: note: this is the location of the previous definition
File "src/core/decoder/gstreamer_decoder.ml", line 314, characters 37-51:
314 | (Decoder.test_file ~log ~mimes:mime_types#get
  ^^
Error: This expression has type string list
  but an expression was expected of type string list option
make: *** [Makefile:4: build] Error 1


Yeah, I got this error after upgrading 2.2.4 also.
And it seems upstream suggests to ship the package wihtout gstreamer:
https://github.com/savonet/liquidsoap/discussions/3751#discussioncomment-8524446

It will cost more time for me how to disable this on Debian packaging.


--
Regards,
--
  Bo YU



signature.asc
Description: PGP signature

Bug#915583: about html_static_path

[Sean Whitton]

Hello,

On Thu 15 Feb 2024 at 11:44pm +01, Holger Wansing wrote:

> Sean Whitton  wrote:
>> On Fri 29 Dec 2023 at 07:08am +01, Stéphane Blondon wrote:
>>
>> > Yes, html_static_path must be set but it's already the case in conf.py.in:
>> > https://sources.debian.org/src/debian-policy/4.6.2.0/policy/conf.py.in/#L105
>> >
>> > I guess conf.py is generated from conf.py.in so we only need to keep
>> > the current setup.
>>
>> That line is commented out, though.  Are you saying it takes on its
>> default value in that case?
>
> I think it would be good to un-comment such lines which are needed, so it's
> clear without doubt, what is used and active.
> Works fine here BTW.

Attached is the patch I prepared, which I couldn't get to work.  Maybe
you can see what is wrong.  Thanks!

-- >8 --
From: =?UTF-8?q?St=C3=A9phane=20Blondon?= 
Date: Mon, 27 Nov 2023 23:36:06 +0100
Subject: [PATCH] New Debian-specific Sphinx style

---
 debian/changelog  |   3 ++
 debian/control|   1 +
 policy/conf.py.in |   5 ++-
 policy/debian.css | 103 ++
 4 files changed, 111 insertions(+), 1 deletion(-)
 create mode 100644 policy/debian.css

diff --git a/debian/changelog b/debian/changelog
index ffa0f8b..6d04491 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -14,6 +14,9 @@ debian-policy (4.6.2.1) UNRELEASED; urgency=medium
   package metadata.
   * Update Installed-Size algorithm used by dpkg (Closes: #793499).
 
+  [ Stéphane Blondon ]
+  * New Debian-specific Sphinx style (Closes: #915583).
+
  -- Russ Allbery   Sat, 09 Sep 2023 15:27:27 -0700
 
 debian-policy (4.6.2.0) unstable; urgency=medium
diff --git a/debian/control b/debian/control
index a98b425..ebb3c3f 100644
--- a/debian/control
+++ b/debian/control
@@ -17,6 +17,7 @@ Build-Depends:
  libxml2-utils,
  links | elinks,
  python3-sphinx,
+ python3-sphinx-rtd-theme,
  sphinx-common (>= 1.6.5),
  sphinx-intl,
  texinfo,
diff --git a/policy/conf.py.in b/policy/conf.py.in
index d516d7b..86bc1ac 100755
--- a/policy/conf.py.in
+++ b/policy/conf.py.in
@@ -84,7 +84,7 @@ todo_include_todos = False
 # The theme to use for HTML and HTML Help pages.  See the documentation for
 # a list of builtin themes.
 #
-html_theme = 'nature'
+html_theme = 'sphinx_rtd_theme'
 
 # Theme options are theme-specific and customize the look and feel of a theme
 # further.  For a list of options available for each theme, see the
@@ -92,6 +92,9 @@ html_theme = 'nature'
 #
 # html_theme_options = {}
 
+# Overwrite theme to fit Debian colors
+html_css_files = ['debian.css']
+
 # Override the title to remove the unnecessary "documentation" suffix.
 html_title = "Debian Policy Manual v@VERSION@"
 
diff --git a/policy/debian.css b/policy/debian.css
new file mode 100644
index 000..7f0981b
--- /dev/null
+++ b/policy/debian.css
@@ -0,0 +1,103 @@
+/* Debian Cascading stylesheet for Sphinx */
+
+div.related {
+background-color: #C70036;
+}
+
+.rst-content h1, .rst-content h2, .rst-content h3, .rst-content h4, 
.rst-content h5, .rst-content h6 {
+color: #C70036;
+}
+
+.wy-nav-top {
+background-color: #C70036;
+}
+
+.wy-side-nav-search {
+background-color: #C70036;
+}
+
+.rst-content a:link {
+color: #0035C7;
+text-decoration: none;
+}
+.rst-content a:visited {
+color: #00207A;
+text-decoration: none;
+}
+.rst-content a:link:hover {
+color: #00207A;
+text-decoration: underline;
+}
+
+
+/* Table in content */
+
+.wy-table-responsive table td, .wy-table-responsive table th {
+white-space: normal;
+}
+
+.rst-content table.docutils, .wy-table-bordered-all {
+width: 100%;
+}
+
+.wy-table-responsive table.docutils thead tr {
+background-color: #C70036;
+border: 1px solid black;
+color: black;
+}
+
+.wy-table-responsive table.docutils thead tr:hover {
+color: #fcfcfc;
+}
+
+.wy-table-responsive table.docutils tbody tr:hover {
+background-color:#66;
+color: #FF;
+}
+
+.rst-content table.docutils:not(.field-list) tbody tr:hover:nth-child(2n-1), 
.wy-table-backed, .wy-table-odd td, .wy-table-striped tr:nth-child(2n-1) td {
+background-color:#66;
+}
+
+/* Previous and next buttons */
+
+.rst-footer-buttons .btn:hover {
+text-decoration: none !important;
+}
+
+/* Version release more readable */
+
+.wy-side-nav-search > div.version {
+color: #FCFCFC;
+}
+
+/* Infos blocks */
+
+div.warning {
+border: 1px dashed #EFF500;
+background-color: #eff50030;
+}
+
+div.note {
+border: 1px dashed blue;
+background-color: #ff30;
+
+}
+
+.warning, .note {
+margin-left: 1em;
+margin-right: 1em;
+}
+
+@media (max-width: 5in), (max-device-width: 5in){
+.warning, .note {
+margin-left: 0.5em;
+margin-right: 0.5em;
+}
+}
+
+/* Notes */
+
+html.writer-html5 .rst-content aside.citation, html.writer-html5 .rst-content 
aside.footnote, html.writer-html5 .rst-content div.citation {
+display: block;
+}
-- 
Sean Whitton


signature.asc
Description: 

Bug#1063270: xen: NMU diff for 64-bit time_t transition

[Steve Langasek]

Hello,

The previous NMU of xen failed to build in experimental because we did not
handle the file renames in debian/shuffle-binaries.  Please see the attached
corrected patch which has been uploaded to experimental.

-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developer   https://www.debian.org/
slanga...@ubuntu.com vor...@debian.org
diff -Nru xen-4.17.3+10-g091466ba55/debian/changelog 
xen-4.17.3+10-g091466ba55/debian/changelog
--- xen-4.17.3+10-g091466ba55/debian/changelog  2024-02-04 04:45:17.0 
-0800
+++ xen-4.17.3+10-g091466ba55/debian/changelog  2024-02-23 18:53:03.0 
-0800
@@ -1,3 +1,17 @@
+xen (4.17.3+10-g091466ba55-1.1~exp2) experimental; urgency=medium
+
+  * debian/shuffle-binaries: handle rename of
+debian/libxenmiscV.install.vsn-in
+
+ -- Steve Langasek   Sat, 24 Feb 2024 02:53:03 +
+
+xen (4.17.3+10-g091466ba55-1.1~exp1) experimental; urgency=medium
+
+  * Non-maintainer upload.
+  * Rename libraries for 64-bit time_t transition.
+
+ -- Steve Langasek   Mon, 05 Feb 2024 23:01:29 +
+
 xen (4.17.3+10-g091466ba55-1) unstable; urgency=medium
 
   * Update to new upstream version 4.17.3+10-g091466ba55, which also contains
diff -Nru xen-4.17.3+10-g091466ba55/debian/control 
xen-4.17.3+10-g091466ba55/debian/control
--- xen-4.17.3+10-g091466ba55/debian/control2024-02-04 04:45:17.0 
-0800
+++ xen-4.17.3+10-g091466ba55/debian/control2024-02-05 15:01:29.0 
-0800
@@ -212,16 +212,16 @@
 Section: libdevel
 Architecture: amd64 arm64 armhf
 Depends: ${shlibs:Depends}, ${misc:Depends},
-libxenmisc4.17 (= ${binary:Version}),
-libxencall1 (= ${binary:Version}),
-libxendevicemodel1 (= ${binary:Version}),
-libxenevtchn1 (= ${binary:Version}),
-libxenforeignmemory1 (= ${binary:Version}),
-libxengnttab1 (= ${binary:Version}),
-libxenstore4 (= ${binary:Version}),
-libxentoolcore1 (= ${binary:Version}),
-libxentoollog1 (= ${binary:Version}),
-libxenhypfs1 (= ${binary:Version}),
+libxenmisc4.17t64 (= ${binary:Version}),
+libxencall1t64 (= ${binary:Version}),
+libxendevicemodel1t64 (= ${binary:Version}),
+libxenevtchn1t64 (= ${binary:Version}),
+libxenforeignmemory1t64 (= ${binary:Version}),
+libxengnttab1t64 (= ${binary:Version}),
+libxenstore4t64 (= ${binary:Version}),
+libxentoolcore1t64 (= ${binary:Version}),
+libxentoollog1t64 (= ${binary:Version}),
+libxenhypfs1t64 (= ${binary:Version}),
 Description: Public headers and libs for Xen
  This package contains the public headers and static libraries for Xen.
  .
@@ -236,7 +236,10 @@
  Most of the other included libraries are internal, and intended for
  use by the Xen toolstack, rather than directly.
 
-Package: libxenmisc4.17
+Package: libxenmisc4.17t64
+Provides: ${t64:Provides}
+Replaces: libxenmisc4.17
+Breaks: libxenmisc4.17 (<< ${source:Version})
 Section: libs
 Architecture: amd64 arm64 armhf
 Depends: ${shlibs:Depends}, ${misc:Depends}
@@ -247,7 +250,10 @@
  knowledge of hypervisor-version-specific hypercall ABIs.
 Multi-Arch: same
 
-Package: libxencall1
+Package: libxencall1t64
+Provides: ${t64:Provides}
+Replaces: libxencall1
+Breaks: libxencall1 (<< ${source:Version})
 Section: libs
 Architecture: amd64 arm64 armhf
 Depends: ${shlibs:Depends}, ${misc:Depends}
@@ -255,7 +261,10 @@
  Shared library for Xen utilities.
 Multi-Arch: same
 
-Package: libxendevicemodel1
+Package: libxendevicemodel1t64
+Provides: ${t64:Provides}
+Replaces: libxendevicemodel1
+Breaks: libxendevicemodel1 (<< ${source:Version})
 Section: libs
 Architecture: amd64 arm64 armhf
 Depends: ${shlibs:Depends}, ${misc:Depends}
@@ -263,7 +272,10 @@
  Shared library for Xen utilities.
 Multi-Arch: same
 
-Package: libxenevtchn1
+Package: libxenevtchn1t64
+Provides: ${t64:Provides}
+Replaces: libxenevtchn1
+Breaks: libxenevtchn1 (<< ${source:Version})
 Section: libs
 Architecture: amd64 arm64 armhf
 Depends: ${shlibs:Depends}, ${misc:Depends}
@@ -271,7 +283,10 @@
  Shared library for Xen utilities.
 Multi-Arch: same
 
-Package: libxenforeignmemory1
+Package: libxenforeignmemory1t64
+Provides: ${t64:Provides}
+Replaces: libxenforeignmemory1
+Breaks: libxenforeignmemory1 (<< ${source:Version})
 Section: libs
 Architecture: amd64 arm64 armhf
 Depends: ${shlibs:Depends}, ${misc:Depends}
@@ -279,7 +294,10 @@
  Shared library for Xen utilities.
 Multi-Arch: same
 
-Package: libxengnttab1
+Package: libxengnttab1t64
+Provides: ${t64:Provides}
+Replaces: libxengnttab1
+Breaks: libxengnttab1 (<< ${source:Version})
 Section: libs
 Architecture: amd64 arm64 armhf
 Depends: ${shlibs:Depends}, ${misc:Depends}
@@ -287,7 +305,10 @@
  Shared library for Xen utilities.
 Multi-Arch: same
 
-Package: libxenstore4

Bug#945269: debian-policy: packages should use tmpfiles.d(5) to create directories below /var

[Sean Whitton]

Hello,

On Sun 17 Sep 2023 at 10:52am -07, Russ Allbery wrote:

> I don't see how shipping empty directories in a deb package affects this
> in any way.  You're going to have to be considerably more specific about
> what invariant is being violated or what error you're expecting.
>
> One of the key things that I'm stuck on, and which you haven't addressed
> that I've seen, is that you're talking here about a system managed with a
> normal package manager, and therefore running all maintainer scripts.  The
> maintainer scripts under this tmpfiles.d proposal will create directories
> and files in /var, because the whole point is that systemd-tmpfiles is run
> from postinst.  But you are saying that creating directories and files in
> /var with the package manager will break this configuration.  I'm missing
> something here.  There's nothing special about dpkg creating the directory
> versus postinst creating the directory.  So far as I can tell, the only
> important part is that the directory be registered in tmpfiles.d (or a
> service unit) so that it can be recreated when needed.

Something which I don't think has been mentioned yet is that we
explicitly permit the local administrator to nuke /usr/share/doc, even
though that is a similar sort of inconsistency between the dpkg db and
the filesystem as the ones that are bothering Luca.

> I understand that you are trying to do something new, and you are worried
> that this will interfere with it, but so far you have not been able to
> explain any way in which this *would* cause you problems.  You just don't
> like the vibes.  And I hear that, and sometimes that sort of bad feeling
> is a valuable architectural clue, but in this case you're really going to
> have to be more specific because I'm not seeing it.
>
> Also, we clearly cannot ship a system without /var *now* because oodles of
> other packages put things there, so a lot of work is left to do before
> this is a technical vision that Debian can implement, if we do indeed
> decide to implement it.  Policy can always change later; perhaps by the
> time that we're ready to implement this vision, dpkg will have a way of
> registering files managed by tmpfiles.d and there's no reason to ship the
> empty directories in the package.  So theoretical future problems are not
> very persuasive to me at this stage, particularly if you can't be specific
> about what those problems would be.
>
>> [...]
>
> I understand that you would like to finish this, but Debian so far has not
> even decided to *start* this, so while I'm willing to take this into
> account when writing Policy, it's not a controlling design principle.  If
> you get an agreement in Debian that this is something we're going to work
> towards, then it will become a significant factor in evaluating Policy
> changes.
>
> I'm really trying to meet you halfway here by adopting and fleshing out
> proposals that you're putting forward primarily for a project that Debian
> isn't currently doing, but which have clear other benefits regardless of
> whether we do the factory reset project.  I don't want to argue over end
> goals when we can agree on intermediate steps regardless of the end goal.
> But I really want to emphasize here that we are not *currently* writing
> Policy to support factory reset because there is no decision in Debian yet
> that we are supporting factory reset.
>
> This is not directly relevant to this bug, but for the record, if you want
> Debian to support factory reset, one good way to make that more likely is
> to write a DEP with the details of precisely what that would mean, roughly
> what sorts of things would need to change in packaging, and a list of what
> the benefits would be.  I personally think a lot of the benefits are
> rather compelling, but no one has yet made a proper case for it in Debian.
> You and Marco and a few other people just write email messages on other
> topics that treat the desirability of factory reset as a foregone
> conclusion, or mention a few benefits in passing and without specifics,
> which of course is fine for casual discussion but which is not a real
> attempt at persuasion and doesn't get us closer to making a real decision.
>
> In other words, this is advice that I constantly give myself because I am
> very bad at this and have to be reminded repeatedly: stop arguing with
> people about specifics and use that energy to write down a design with a
> justification.  It will make the arguments much less annoying and
> repetitive, because a lot of the repetition is because everyone else is
> sadly incapable of reading your mind and doesn't understand what you are
> assuming is well-known.

I very much agree.  It also seems worth mentioning that if we are able
to support factory-reset, we will also want to minimise how much it gets
in the way of people who have no interest in that sort of feature --
most of our classic Debian desktop power users, I suspect (which
includes most DDs).

Russ, I think 

Bug#1063066: wcstools: NMU diff for 64-bit time_t transition

[Steve Langasek]

Hello,

wcstools failed to build in experimental because the .install file had a
missing / in the shebang path for dh_exec.  I'm not sure how this ever
worked at all?  Anyway, attached is a debdiff for a fixed NMU that has been
uploaded.

Thanks,
-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developer   https://www.debian.org/
slanga...@ubuntu.com vor...@debian.org
diff -Nru wcstools-3.9.7/debian/changelog wcstools-3.9.7/debian/changelog
--- wcstools-3.9.7/debian/changelog 2022-04-30 13:18:07.0 +
+++ wcstools-3.9.7/debian/changelog 2024-02-24 02:43:31.0 +
@@ -1,3 +1,17 @@
+wcstools (3.9.7-1.1~exp2) experimental; urgency=medium
+
+  * Add missing leading / to the shebang path for .install; not clear how
+this ever worked without it?
+
+ -- Steve Langasek   Sat, 24 Feb 2024 02:43:31 +
+
+wcstools (3.9.7-1.1~exp1) experimental; urgency=medium
+
+  * Non-maintainer upload.
+  * Rename libraries for 64-bit time_t transition.
+
+ -- Steve Langasek   Sun, 04 Feb 2024 20:00:38 +
+
 wcstools (3.9.7-1) unstable; urgency=medium
 
   [ Debian Janitor ]
diff -Nru wcstools-3.9.7/debian/control wcstools-3.9.7/debian/control
--- wcstools-3.9.7/debian/control   2022-04-30 13:08:17.0 +
+++ wcstools-3.9.7/debian/control   2024-02-04 20:00:38.0 +
@@ -15,7 +15,7 @@
 
 Package: wcstools
 Architecture: any
-Depends: libwcstools1 (= ${binary:Version}),
+Depends: libwcstools1t64 (= ${binary:Version}),
  ${misc:Depends},
  ${shlibs:Depends}
 Description: Handle the WCS of a FITS image
@@ -31,7 +31,7 @@
 Architecture: any
 Multi-Arch: same
 Section: libdevel
-Depends: libwcstools1 (= ${binary:Version}),
+Depends: libwcstools1t64 (= ${binary:Version}),
  ${misc:Depends},
  ${shlibs:Depends}
 Description: Handle the WCS of a FITS image (development files)
@@ -43,7 +43,10 @@
  .
  This package contains the files needed for development.
 
-Package: libwcstools1
+Package: libwcstools1t64
+Provides: ${t64:Provides}
+Replaces: libwcstools1
+Breaks: libwcstools1 (<< ${source:Version})
 Architecture: any
 Multi-Arch: same
 Section: libs
diff -Nru wcstools-3.9.7/debian/libwcstools1.install 
wcstools-3.9.7/debian/libwcstools1.install
--- wcstools-3.9.7/debian/libwcstools1.install  2022-04-30 13:08:17.0 
+
+++ wcstools-3.9.7/debian/libwcstools1.install  1970-01-01 00:00:00.0 
+
@@ -1,3 +0,0 @@
-#! usr/bin/dh-exec
-libwcs/libwcstools.so.1 usr/lib/${DEB_HOST_MULTIARCH}/
-libwcs/libwcstools.so.1.0.0 usr/lib/${DEB_HOST_MULTIARCH}/
diff -Nru wcstools-3.9.7/debian/libwcstools1.lintian-overrides 
wcstools-3.9.7/debian/libwcstools1.lintian-overrides
--- wcstools-3.9.7/debian/libwcstools1.lintian-overrides2022-04-30 
13:08:17.0 +
+++ wcstools-3.9.7/debian/libwcstools1.lintian-overrides1970-01-01 
00:00:00.0 +
@@ -1,4 +0,0 @@
-# calling exit() is part of the wcstools API.
-exit-in-shared-library usr/lib/*/libwcstools.so*
-# False positive
-spelling-error-in-binary usr/lib/*/libwcstools.so* lengH length
diff -Nru wcstools-3.9.7/debian/libwcstools1.symbols 
wcstools-3.9.7/debian/libwcstools1.symbols
--- wcstools-3.9.7/debian/libwcstools1.symbols  2022-04-30 13:17:47.0 
+
+++ wcstools-3.9.7/debian/libwcstools1.symbols  1970-01-01 00:00:00.0 
+
@@ -1,902 +0,0 @@
-libwcstools.so.1 libwcstools1 #MINVER#
-* Build-Depends-Package: libwcstools-dev
- AIR@Base 3.8.4
- AIT@Base 3.8.4
- ARC@Base 3.8.4
- AZP@Base 3.8.4
- BON@Base 3.8.4
- CAR@Base 3.8.4
- CEA@Base 3.8.4
- COD@Base 3.8.4
- COE@Base 3.8.4
- COO@Base 3.8.4
- COP@Base 3.8.4
- CSC@Base 3.8.4
- CYP@Base 3.8.4
- CatCode@Base 3.8.4
- CatID@Base 3.8.4
- CatMagName@Base 3.8.4
- CatMagNum@Base 3.8.4
- CatName@Base 3.8.4
- CatNdec@Base 3.8.4
- CatNum@Base 3.8.4
- CatNumLen@Base 3.8.4
- CatRad@Base 3.8.4
- CatSource@Base 3.8.4
- CatTabHead@Base 3.8.4
- ChangeFITSWCS@Base 3.8.4
- DateString@Base 3.8.4
- DecSortStars@Base 3.8.4
- DelDistort@Base 3.8.4
- DelWCSFITS@Base 3.8.4
- FillFITS@Base 3.8.4
- FiltFITS@Base 3.8.4
- FindStars@Base 3.8.4
- FitMatch@Base 3.8.4
- FitPlate@Base 3.8.4
- FluxSortStars@Base 3.8.4
- GetFITSWCS@Base 3.8.4
- GetFITShead@Base 3.8.4
- GetPlate@Base 3.8.4
- GetWCSFITS@Base 3.8.4
- IDSortStars@Base 3.8.4
- MER@Base 3.8.4
- MOL@Base 3.8.4
- MagSortStars@Base 3.8.4
- MergeStars@Base 3.8.4
- NParamFit@Base 3.8.4
- NumNdec@Base 3.8.4
- PAR@Base 3.8.4
- PCO@Base 3.8.4
- ParamFit@Base 3.8.4
- PhotPix@Base 3.8.4
- PrintWCS@Base 3.8.4
- ProgCat@Base 3.8.4
- ProgName@Base 3.8.4
- QSC@Base 3.8.4
- RASortStars@Base 3.8.4
- RangeInit@Base 3.8.4
- ReadMatch@Base 3.8.4
- RefCat@Base 3.8.4
- RefLim@Base 3.8.4
- RotFITS@Base 3.8.4
- SFL@Base 3.8.4
- SIN@Base 3.8.4
- STG@Base 3.8.4
- SZP@Base 3.8.4
- SearchLim@Base 3.8.4
- 

Bug#968226: Move documentation of Build-Depends alternative selection out of footnote

[Sean Whitton]

control: tag -1 + pending

On Sun 10 Sep 2023 at 10:45am -07, Russ Allbery wrote:

> Russ Allbery  writes:
>
>> This patch from a while back is still waiting for one more second before
>> it can be merged for the next Policy release.  It previously got one
>> second from Wouter.  I revised the patch to mention the experimental
>> suite as well as the backports suites.
>
> Argh, wrong patch, sorry.  Here is the one that was actually updated to
> include experimental.

Seconded and applied.  I think the whole thing might be non-normative,
but certainly the mere addition of experimental is.

> --
> Russ Allbery (r...@debian.org)  
>
>>From 7ee49f6c892d6057b9a0d2f9eb84ff0f35d1d436 Mon Sep 17 00:00:00 2001
> From: Russ Allbery 
> Date: Tue, 20 Sep 2022 19:11:54 -0700
> Subject: [PATCH] Improve alternative build dependency discussion
>
> Alternatives in build dependencies are normally (except for
> backports) handled specially by autobuilders to try to maintain
> consistent builds.  This was documented in Policy, but in a
> footnote that people often didn't see.
>
> Move this text into the main body of the discussion of build
> dependencies and reword it for additional clarity.  Add a pointer
> to this discussion where alternative dependencies are introduced.
> ---
>  policy/ch-relationships.rst | 61 +++--
>  1 file changed, 45 insertions(+), 16 deletions(-)
>
> diff --git a/policy/ch-relationships.rst b/policy/ch-relationships.rst
> index 5074428..ffafbf1 100644
> --- a/policy/ch-relationships.rst
> +++ b/policy/ch-relationships.rst
> @@ -15,7 +15,10 @@ control fields of the package, which declare dependencies 
> on other
>  packages, the package names listed may also include lists of alternative
>  package names, separated by vertical bar (pipe) symbols ``|``. In such a
>  case, that part of the dependency can be satisfied by any one of the
> -alternative packages.  [#]_
> +alternative packages. (Alternative dependencies in ``Build-Depends``,
> +``Build-Depends-Indep``, and ``Build-Depends-Arch`` are interpreted
> +specially by Debian autobuilders. See :ref:`Relationships between source
> +and binary packages ` for more details.)
>  
>  All of the fields may restrict their applicability to particular versions
>  of each named package. This is done in parentheses after each individual
> @@ -620,6 +623,47 @@ earlier for binary packages) in order to invoke the 
> targets in
>  ``Build-Conflicts-Arch`` fields must be satisfied when these targets
>  are invoked.
>  
> +Alternative dependencies are allowed in the ``Build-Depends``,
> +``Build-Depends-Indep``, and ``Build-Depends-Arch`` fields, but Debian's
> +autobuilders normally discard the dependencies after the first. This is
> +done to give alternative dependencies a consistent interpretation that
> +reduces the risk of inconsistencies between repeated builds. If, for
> +example, the first-listed dependency would normally be available but is
> +temporarily not installable, the autobuilder fails rather than install a
> +subsequent dependency that may significantly change the behavior of the
> +package.
> +
> +More specifically, Debian autobuilders perform the following
> +transformation on alternative dependencies in the ``Build-Depends``,
> +``Build-Depends-Indep``, and ``Build-Depends-Arch`` fields:
> +
> +#. Discard any alternatives that are restricted to architectures that do
> +   not match the host architecture.
> +#. Discard any alternatives specifying different package names than the
> +   now-first alternative. (Alternatives specifying the same package name
> +   are kept to permit relationships such as ``foo (<= x) | foo (>= y)``.)
> +
> +For example, an autobuilder for the ``amd64`` architecture would treat the
> +following dependency::
> +
> +foo-special [armhf] | foo (<= 4) | foo (>= 4.2) | bar
> +
> +as if it were::
> +
> +foo (<= 4) | foo (>= 4.2)
> +
> +The normal effect is to use only the first alternative that is valid on
> +the relevant architecture and fail if that alternative is not installable.
> +
> +While this rule for build dependencies may limit the usefulness of
> +alternatives, they can still be used to provide flexibility when building
> +the package outside of Debian's autobuilders.
> +
> +The autobuilders for the Debian backports and experimental suites do not
> +perform this transformation and instead use the same dependency resolution
> +rules as normal package installations to choose which alternative
> +dependency to install.
> +
>  .. _s-built-using:
>  
>  Additional source packages used to build the binary - ``Built-Using``
> @@ -666,21 +710,6 @@ requirements to retain the referenced source packages.  
> It should not
>  be added solely as a way to locate packages that need to be rebuilt
>  against newer versions of their build dependencies.
>  
> -.. [#]
> -   While ``Build-Depends``, ``Build-Depends-Indep`` and
> -   

Bug#1062403: freecontact: NMU diff for 64-bit time_t transition

[Steve Langasek]

Hello,

The previous NMU of freecontact failed to build in experimental because
debian/rules still had a --v5 option passed to d-shlibs, which is mutually
incompatible with --t64.  Please see the attached corrected patch.

-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developer   https://www.debian.org/
slanga...@ubuntu.com vor...@debian.org
diff -Nru freecontact-1.0.21/debian/changelog 
freecontact-1.0.21/debian/changelog
--- freecontact-1.0.21/debian/changelog 2023-05-18 09:43:26.0 +
+++ freecontact-1.0.21/debian/changelog 2024-02-24 01:32:43.0 +
@@ -1,3 +1,17 @@
+freecontact (1.0.21-13.1~exp2) experimental; urgency=medium
+
+  * Non-maintainer upload.
+  * Drop --v5 argument to d-shlibs, should be mutually exclusive with --t64.
+
+ -- Steve Langasek   Sat, 24 Feb 2024 01:32:43 +
+
+freecontact (1.0.21-13.1~exp1) experimental; urgency=medium
+
+  * Non-maintainer upload.
+  * Rename libraries for 64-bit time_t transition.
+
+ -- Lukas Märdian   Thu, 01 Feb 2024 09:41:16 +
+
 freecontact (1.0.21-13) unstable; urgency=medium
 
   * Team upload.
diff -Nru freecontact-1.0.21/debian/control freecontact-1.0.21/debian/control
--- freecontact-1.0.21/debian/control   2022-04-09 20:20:33.0 +
+++ freecontact-1.0.21/debian/control   2024-02-01 09:41:16.0 +
@@ -5,7 +5,7 @@
 Priority: optional
 Build-Depends: debhelper-compat (= 13),
bash-completion,
-   d-shlibs,
+   d-shlibs (>= 0.106),
gfortran,
libblas-dev | libblas-3.so,
libboost-dev,
@@ -35,14 +35,17 @@
  .
  This package contains the command line tool freecontact(1).
 
-Package: libfreecontact0v5
+Package: libfreecontact0t64
+Provides: ${t64:Provides}
+X-Time64-Compat: libfreecontact0v5
+Breaks: libfreecontact0v5 (<< ${source:Version})
 Architecture: any
 Multi-Arch: same
 Section: libs
 Depends: ${shlibs:Depends},
  ${misc:Depends}
 Conflicts: libfreecontact0
-Replaces: libfreecontact0
+Replaces: libfreecontact0v5, libfreecontact0
 Description: fast protein contact predictor library
  ${Description}
  .
@@ -52,7 +55,7 @@
 Architecture: any
 Multi-Arch: same
 Section: libdevel
-Depends: libfreecontact0v5 (= ${binary:Version}),
+Depends: libfreecontact0t64 (= ${binary:Version}),
  ${misc:Depends}
 Suggests: libfreecontact-doc
 Conflicts: libfreecontact-dev
diff -Nru freecontact-1.0.21/debian/libfreecontact0t64.lintian-overrides 
freecontact-1.0.21/debian/libfreecontact0t64.lintian-overrides
--- freecontact-1.0.21/debian/libfreecontact0t64.lintian-overrides  
1970-01-01 00:00:00.0 +
+++ freecontact-1.0.21/debian/libfreecontact0t64.lintian-overrides  
2024-02-01 09:41:16.0 +
@@ -0,0 +1 @@
+libfreecontact0t64: package-name-doesnt-match-sonames libfreecontact0v5
diff -Nru freecontact-1.0.21/debian/rules freecontact-1.0.21/debian/rules
--- freecontact-1.0.21/debian/rules 2023-05-18 09:29:42.0 +
+++ freecontact-1.0.21/debian/rules 2024-02-24 01:32:14.0 +
@@ -27,10 +27,10 @@
 override_dh_install:
dh_install
d-shlibmove --commit \
+   --t64 \
--multiarch \
--exclude-la \
--devunversioned \
-   --v5 \
 --override s/libgfortran[345]-dev/libgfortran-12-dev/ \
--movedev debian/tmp/usr/include/* usr/include \
debian/tmp/usr/lib/*/*.so


signature.asc
Description: PGP signature

Bug#1064551: bookworm-pu: libjwt/1.10.2-1+deb11u1

[Thorsten Alteholz]

Package: release.debian.org
Severity: normal
Tags: bookworm
User: release.debian@packages.debian.org
Usertags: pu


The attached debdiff for libjwt fixes CVE-2024-25189 in Bookworm. It is 
marked as no-dsa by the security team.

The fix is straightfoward and should not make any problems.

  Thorsten
diff -Nru libjwt-1.10.2/debian/changelog libjwt-1.10.2/debian/changelog
--- libjwt-1.10.2/debian/changelog  2019-07-14 19:03:00.0 +0200
+++ libjwt-1.10.2/debian/changelog  2024-02-19 22:03:02.0 +0100
@@ -1,3 +1,10 @@
+libjwt (1.10.2-1+deb12u1) bookworm; urgency=medium
+
+  * CVE-2024-25189 (Closes: #1063534)
+fix a timing side channel via strcmp()
+
+ -- Thorsten Alteholz   Mon, 19 Feb 2024 22:03:02 +0100
+
 libjwt (1.10.2-1) unstable; urgency=medium
 
   * New upstream release
diff -Nru libjwt-1.10.2/debian/libjwt0.symbols 
libjwt-1.10.2/debian/libjwt0.symbols
--- libjwt-1.10.2/debian/libjwt0.symbols2019-01-13 15:13:51.0 
+0100
+++ libjwt-1.10.2/debian/libjwt0.symbols2024-02-19 22:03:02.0 
+0100
@@ -38,5 +38,6 @@
  jwt_sign_sha_hmac@Base 1.9.0
  jwt_sign_sha_pem@Base 1.9.0
  jwt_str_alg@Base 1.9.0
+ jwt_strcmp@Base 1.10.2
  jwt_verify_sha_hmac@Base 1.9.0
  jwt_verify_sha_pem@Base 1.9.0
diff -Nru libjwt-1.10.2/debian/libjwt-gnutls0.symbols 
libjwt-1.10.2/debian/libjwt-gnutls0.symbols
--- libjwt-1.10.2/debian/libjwt-gnutls0.symbols 2019-01-13 15:13:51.0 
+0100
+++ libjwt-1.10.2/debian/libjwt-gnutls0.symbols 2024-02-19 22:03:02.0 
+0100
@@ -38,5 +38,6 @@
  jwt_sign_sha_hmac@Base 1.9.0
  jwt_sign_sha_pem@Base 1.9.0
  jwt_str_alg@Base 1.9.0
+ jwt_strcmp@Base 1.10.2
  jwt_verify_sha_hmac@Base 1.9.0
  jwt_verify_sha_pem@Base 1.9.0
diff -Nru libjwt-1.10.2/debian/patches/CVE-2024-25189-1.patch 
libjwt-1.10.2/debian/patches/CVE-2024-25189-1.patch
--- libjwt-1.10.2/debian/patches/CVE-2024-25189-1.patch 1970-01-01 
01:00:00.0 +0100
+++ libjwt-1.10.2/debian/patches/CVE-2024-25189-1.patch 2024-02-19 
22:03:02.0 +0100
@@ -0,0 +1,130 @@
+commit f73bac57c5bece16ac24f1a70022aa34355fc1bf
+Author: Ben Collins 
+Date:   Fri Feb 9 09:03:35 2024 -0500
+
+Implement a safer strcmp() function
+
+As noted, the strcmp() function can be used for time-based side attacks.
+
+I tried to test this and could not find a reasonable way to implement
+this attack for several reasons:
+
+1) strcmp() is optimized to compare 4 and 8 bytes at a time when possible
+   on almost every modern system, making the attack almost impossible.
+2) Running 128 million iterations of strcmp() for a single byte attack
+   gave sub-nanosecond average differences (locally on same excution stack)
+   and almost as often as the comparison was correct, it was also wrong in
+   the reverse sense (i.e. two byte strcmp() took less time than single
+   byte).
+3) Adding noise from network, application stack, web server, etc. would
+   only add to the failure rate of guessing the differences above.
+
+Erwan noted that there are proofs out there showing that signal noise
+reduction can make this guessing more "accurate", but this proof also
+noted it would take up to 4 billion guesses to completely cover this
+attack surface. The claim was that 50k attempts per second would break
+a 256-bit hmac in 22 hours. While this isn't impossible, it's very
+implausible.
+
+However, for the sake of cryptographic correctness, I implemented
+jwt_strcmp() which always compares all bytes, and does so up to the
+longest string in the 2-string set, without passing string boundaries.
+
+This makes it time-consistent for len(max(a,b)) comparisons. I proofed
+this using a 128 million interation average for various scenarious.
+
+Reported-by: Erwan Legrand 
+Signed-off-by: Ben Collins 
+
+Index: libjwt-1.10.2/libjwt/jwt-gnutls.c
+===
+--- libjwt-1.10.2.orig/libjwt/jwt-gnutls.c 2024-02-19 22:38:58.575655983 
+0100
 libjwt-1.10.2/libjwt/jwt-gnutls.c  2024-02-19 22:38:58.571655984 +0100
+@@ -90,7 +90,7 @@
+   jwt_Base64encode(buf, sig_check, len);
+   jwt_base64uri_encode(buf);
+ 
+-  if (!strcmp(sig, buf))
++  if (!jwt_strcmp(sig, buf))
+   ret = 0;
+ 
+   free(sig_check);
+Index: libjwt-1.10.2/libjwt/jwt-openssl.c
+===
+--- libjwt-1.10.2.orig/libjwt/jwt-openssl.c2024-02-19 22:38:58.575655983 
+0100
 libjwt-1.10.2/libjwt/jwt-openssl.c 2024-02-19 22:38:58.571655984 +0100
+@@ -140,7 +140,7 @@
+   jwt_base64uri_encode(buf);
+ 
+   /* And now... */
+-  ret = strcmp(buf, sig) ? EINVAL : 0;
++  ret = jwt_strcmp(buf, sig) ? EINVAL : 0;
+ 
+ jwt_verify_hmac_done:
+   BIO_free_all(b64);
+Index: libjwt-1.10.2/libjwt/jwt-private.h

Bug#1064550: bullseye-pu: libjwt/1.10.2-1+deb11u1

[Thorsten Alteholz]

Package: release.debian.org
Severity: normal
Tags: bullseye
User: release.debian@packages.debian.org
Usertags: pu


The attached debdiff for libjwt fixes CVE-2024-25189 in Bullseye. It is 
marked as no-dsa by the security team.

The fix is straightfoward and should not make any problems.

  Thorsten
diff -Nru libjwt-1.10.2/debian/changelog libjwt-1.10.2/debian/changelog
--- libjwt-1.10.2/debian/changelog  2019-07-14 19:03:00.0 +0200
+++ libjwt-1.10.2/debian/changelog  2024-02-20 23:03:02.0 +0100
@@ -1,3 +1,10 @@
+libjwt (1.10.2-1+deb11u1) bullseye; urgency=medium
+
+  * CVE-2024-25189 (Closes: #1063534)
+fix a timing side channel via strcmp()
+
+ -- Thorsten Alteholz   Tue, 20 Feb 2024 23:03:02 +0100
+
 libjwt (1.10.2-1) unstable; urgency=medium
 
   * New upstream release
diff -Nru libjwt-1.10.2/debian/libjwt0.symbols 
libjwt-1.10.2/debian/libjwt0.symbols
--- libjwt-1.10.2/debian/libjwt0.symbols2019-01-13 15:13:51.0 
+0100
+++ libjwt-1.10.2/debian/libjwt0.symbols2024-02-20 23:03:02.0 
+0100
@@ -38,5 +38,6 @@
  jwt_sign_sha_hmac@Base 1.9.0
  jwt_sign_sha_pem@Base 1.9.0
  jwt_str_alg@Base 1.9.0
+ jwt_strcmp@Base 1.10.2
  jwt_verify_sha_hmac@Base 1.9.0
  jwt_verify_sha_pem@Base 1.9.0
diff -Nru libjwt-1.10.2/debian/libjwt-gnutls0.symbols 
libjwt-1.10.2/debian/libjwt-gnutls0.symbols
--- libjwt-1.10.2/debian/libjwt-gnutls0.symbols 2019-01-13 15:13:51.0 
+0100
+++ libjwt-1.10.2/debian/libjwt-gnutls0.symbols 2024-02-20 23:03:02.0 
+0100
@@ -38,5 +38,6 @@
  jwt_sign_sha_hmac@Base 1.9.0
  jwt_sign_sha_pem@Base 1.9.0
  jwt_str_alg@Base 1.9.0
+ jwt_strcmp@Base 1.10.2
  jwt_verify_sha_hmac@Base 1.9.0
  jwt_verify_sha_pem@Base 1.9.0
diff -Nru libjwt-1.10.2/debian/patches/CVE-2024-25189-1.patch 
libjwt-1.10.2/debian/patches/CVE-2024-25189-1.patch
--- libjwt-1.10.2/debian/patches/CVE-2024-25189-1.patch 1970-01-01 
01:00:00.0 +0100
+++ libjwt-1.10.2/debian/patches/CVE-2024-25189-1.patch 2024-02-20 
23:03:02.0 +0100
@@ -0,0 +1,130 @@
+commit f73bac57c5bece16ac24f1a70022aa34355fc1bf
+Author: Ben Collins 
+Date:   Fri Feb 9 09:03:35 2024 -0500
+
+Implement a safer strcmp() function
+
+As noted, the strcmp() function can be used for time-based side attacks.
+
+I tried to test this and could not find a reasonable way to implement
+this attack for several reasons:
+
+1) strcmp() is optimized to compare 4 and 8 bytes at a time when possible
+   on almost every modern system, making the attack almost impossible.
+2) Running 128 million iterations of strcmp() for a single byte attack
+   gave sub-nanosecond average differences (locally on same excution stack)
+   and almost as often as the comparison was correct, it was also wrong in
+   the reverse sense (i.e. two byte strcmp() took less time than single
+   byte).
+3) Adding noise from network, application stack, web server, etc. would
+   only add to the failure rate of guessing the differences above.
+
+Erwan noted that there are proofs out there showing that signal noise
+reduction can make this guessing more "accurate", but this proof also
+noted it would take up to 4 billion guesses to completely cover this
+attack surface. The claim was that 50k attempts per second would break
+a 256-bit hmac in 22 hours. While this isn't impossible, it's very
+implausible.
+
+However, for the sake of cryptographic correctness, I implemented
+jwt_strcmp() which always compares all bytes, and does so up to the
+longest string in the 2-string set, without passing string boundaries.
+
+This makes it time-consistent for len(max(a,b)) comparisons. I proofed
+this using a 128 million interation average for various scenarious.
+
+Reported-by: Erwan Legrand 
+Signed-off-by: Ben Collins 
+
+Index: libjwt-1.10.2/libjwt/jwt-gnutls.c
+===
+--- libjwt-1.10.2.orig/libjwt/jwt-gnutls.c 2024-02-19 22:38:58.575655983 
+0100
 libjwt-1.10.2/libjwt/jwt-gnutls.c  2024-02-19 22:38:58.571655984 +0100
+@@ -90,7 +90,7 @@
+   jwt_Base64encode(buf, sig_check, len);
+   jwt_base64uri_encode(buf);
+ 
+-  if (!strcmp(sig, buf))
++  if (!jwt_strcmp(sig, buf))
+   ret = 0;
+ 
+   free(sig_check);
+Index: libjwt-1.10.2/libjwt/jwt-openssl.c
+===
+--- libjwt-1.10.2.orig/libjwt/jwt-openssl.c2024-02-19 22:38:58.575655983 
+0100
 libjwt-1.10.2/libjwt/jwt-openssl.c 2024-02-19 22:38:58.571655984 +0100
+@@ -140,7 +140,7 @@
+   jwt_base64uri_encode(buf);
+ 
+   /* And now... */
+-  ret = strcmp(buf, sig) ? EINVAL : 0;
++  ret = jwt_strcmp(buf, sig) ? EINVAL : 0;
+ 
+ jwt_verify_hmac_done:
+   BIO_free_all(b64);
+Index: libjwt-1.10.2/libjwt/jwt-private.h

Bug#1064549: elpa-pdf-tools: 'Warning (comp): Cannot look-up eln file as no source file was found [...]' message after M-x pdf-tools-install

[iago]

Package: elpa-pdf-tools 
 Version: 1.0.0-1 
 Severity: normal 
 X-Debbugs-Cc: none, Iago Giné Vázquez  
 
Dear Maintainer, 
 
When I want to use pdf-tools in Debian, taking into account the bug 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=883598, to get it to 
work the first thing I do is 
 
M-x pdf-tools-install 
 
So, following the next steps: 
1. Open emacs (for example, through terminal 'emacs') 
2. Execute 'M-x pdf-tools-install' 
 
The outcome got is a new window with the next message repeated multiple 
times: 
 
Warning (comp): Cannot look-up eln file as no source file was found for 
/usr/share/emacs/site-lisp/elpa/pdf-tools-1.0/pdf-tools.elc Disable 
showing Disable logging 
 
I did not expect any warning. 
 
Thanks. 
Kind regards,
Iago 
 
-- System Information: 
Debian Release: 12.5 
 APT prefers stable-updates 
 APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable') 
Architecture: amd64 (x86_64) 
 
Kernel: Linux 6.1.0-18-amd64 (SMP w/8 CPU threads; PREEMPT) 
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE 
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_GB:en 
Shell: /bin/sh linked to /usr/bin/dash 
Init: systemd (via /run/systemd/system) 
LSM: AppArmor: enabled 
 
Versions of packages elpa-pdf-tools depends on: 
ii  dh-elpa-helper 2.0.16 
ii  elpa-let-alist 1.0.6-2 
ii  elpa-pdf-tools-server  1.0.0-1 
ii  elpa-tablist   1.0-2 
ii  emacs  1:28.2+1-15 
ii  emacs-gtk [emacs]  1:28.2+1-15 
ii  emacsen-common 3.0.5 
 
elpa-pdf-tools recommends no packages. 
 
elpa-pdf-tools suggests no packages. 
 
-- no debconf information

Bug#1064548: tracker-miners: bmp-basic-1 test fails on big-endian

[Jeremy Bícha]

Source: tracker-miners
Version: 3.5.0~beta-1
Severity: serious
Tags: ftbfs experimental help
X-Debbugs-CC: debian-s...@lists.debian.org
User: debian-s...@lists.debian.org
Usertags: s390x
Forwarded: https://gitlab.gnome.org/GNOME/tracker-miners/-/issues/309

tracker-miners added new tests in 3.5.0.beta including bmp-basic-1.
This test is failing on the big endian architectures s390x and ppc64.

In Debian, we could ignore this test failure since this issue was only
discovered via a brand new test. That function has likely been broken
on those architectures in Debian for a long time. But it would be much
nicer to see it fixed.

Thank you,
Jeremy Bícha

Bug#1063916: RFP: freenginx -- a fork of nginx maintained by Maxim Dounin and the development community

[Jeffrey Walton]

On Thu, Feb 15, 2024 at 4:57 PM Henrique de Moraes Holschuh
 wrote:
>
> Is there *any* point on packaging this nginx fork this early?
>
> We don't yet know the bus factor (i.e. uptake of the fork, size of core team, 
> etc) of this fork yet.  We don't know how the dynamics with the F5-controlled 
> ngnix project will play out re. cross-merges, security issues (which are very 
> likely to be the same for both projects for quite a while given the shared 
> code), etc.
>
> If nginx and freenginx diverge too much on functionality, it might make sense 
> to have both in Debian.  If they do not, we more likely should stick with 
> either one, but not both (and it is way too early to even guess which one 
> would make sense to stick to)...
>
> There are other potential issues as well, it is best to wait a couple months 
> at the very least.

Thank you sir!

And my apologies for selecting the wrong license. That was a
copy/paste error from the sample wnpp request.

Jeff

Bug#1063916:

[Jeffrey Walton]

X-Debbugs-CC: mdou...@mdounin.ru

Bug#1064547: glslang-dev: no longer shipping intermediate.h (among others)

[Timo Röhling]

Package: glslang-dev
Version: 14.0.0-2
Severity: important
Tags: affects -1 src:filament

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Dear maintainer,

glslang-dev stopped shipping a number of header files, which causes 
filament to FTBFS:

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063143


Cheers
Timo


-BEGIN PGP SIGNATURE-

iQGzBAEBCgAdFiEEJvtDgpxjkjCIVtam+C8H+466LVkFAmXZMBUACgkQ+C8H+466
LVkCxgwAiwL9uR0sHaC2DgQL48TWIgZ1cit00KkNdxoJ1BPyf2URSUhJ3usYudms
bdgbf3G8GerOouvMOMYpYljbISMCPV8oheptoc2vnr84uP4RckGYO+PPvmRCgxtJ
0+qohcrAG/1uSUw/aawl5Kp8PCuL8S3VFdSONbsocPyEOLbpaHj96uKaUoJ/RqnK
rCq4eZYO8PS4L4NNvnvbOX+ldNOkEMAOsYKRJqNEnRCWW8bQfuCmyZ8LO8Lugunv
z6o1XtIvWowg8X4v01auSB906jCFqDtkSAn+3i4LedDICumzjazjXXOtu9JSwkwb
ky2GP1xWeI5QrVJYqIOFPYjQEdpMAr9mrIMbfLP2d8kS4fKEqI8D7wPidIled2+m
grqrSsWptbY7XfySkhLpbCP/vSNuiJY4P6pTIPeQSnwkV8Scuzy0fdCt+0bTP0L/
KMoCRTZon5zjGYB/wkGUPGnSx8uBzRkoF9cG54JHzyJdp5ZP6H0WWi0oPYXALsPI
6NtbkpBG
=u2mR
-END PGP SIGNATURE-

Bug#1064546: kicad: Please package 8.0.0

[Sebastian Reichel]

Package: kicad
Version: 7.0.10+dfsg-1
Severity: wishlist

Dear Maintainer,

https://www.kicad.org/blog/2024/02/Version-8.0.0-Released/

Please update the package :)

Thanks for your work,

-- Sebastian

Bug#1061926: Bug#1061966 closed by Debian FTP Masters (reply to Steve Langasek ) (Bug#1061966: fixed in audit 1:3.1.2-2.1~exp2)

[Steve Langasek]

Thanks to discussion on debian-devel, it's become clear that a rename of
libaudit1 is not required, only of libauparse0.  Please find attached a
follow-on patch for yet another NMU to experimental, reverting the libaudit
package name change.

On Fri, Feb 02, 2024 at 09:56:51AM -0800, Steve Langasek wrote:
> Really-really-really
> 
> On Fri, Feb 02, 2024 at 09:36:27AM -0800, Steve Langasek wrote:
> > Helmut pointed out the preinst.in files didn't actually include the token to
> > be substituted, but instead still had the hard-coded architecture path :/
> > 
> > Attached is the really-really-fixed-this-time NMU patch.
> > 
> > 
> > On Fri, Feb 02, 2024 at 08:56:32AM -0800, Steve Langasek wrote:
> > > By happenstance I noticed that I had mindlessly hard-coded the
> > > amd64-specific multiarch path into the preinsts.
> > > 
> > > Please find a really-fixed-this-time NMU patch for experimental.
> > > 
> > > 
> > > On Wed, Jan 31, 2024 at 12:41:48PM -0800, Steve Langasek wrote:
> > > > Sorry, and thanks for bearing with me.  Uploaded to experimental again;
> > > > updated full NMU debdiff attached.
> > > > 
> > > > On Wed, Jan 31, 2024 at 09:31:25PM +0100, Helmut Grohne wrote:
> > > > > Control: reopen -1
> > > > > 
> > > > > On Wed, Jan 31, 2024 at 10:12:03AM +, Debian Bug Tracking System 
> > > > > wrote:
> > > > > > #1061966: file loss due to combining time64 + /usr-move
> > > > > > 
> > > > > > It has been closed by Debian FTP Masters 
> > > > > >  (reply to Steve Langasek 
> > > > > > ).
> > > > > 
> > > > > I fear this is not fixed.
> > > > > 
> > > > > > /usr/lib/x86_64-linux-gnu/libaudit.so.1 and
> > > > > 
> > > > > This is fixed.
> > > > > 
> > > > > > /usr/lib/x86_64-linux-gnu/libaudit.so.1.0.0 have been moved from
> > > > > 
> > > > > This not.
> > > > > 
> > > > > > libaudit1 to libaudit1t64 in this upload and these files have 
> > > > > > formerly
> > > > > > been installed below /lib in bookworm. Hence, we are creating 
> > > > > > exactly
> > > > > > the problem that the file move moratorium was meant to prevent.
> > > > > > 
> > > > > > /usr/lib/x86_64-linux-gnu/libauparse.so.0 and
> > > > > 
> > > > > This is fixed.
> > > > > 
> > > > > > /usr/lib/x86_64-linux-gnu/libauparse.so.0.0.0 likewise move from
> > > > > 
> > > > > This not.
> > > > > 
> > > > > > libauparse0 to libauparse0t64 and create the same problem.
> > > > > > 
> > > > > > DEP17 classifies this a P1 and proposed mitigations M7 and M8. In 
> > > > > > this
> > > > > > case, I recommend not exercising Conflicts (M7), because they are 
> > > > > > known
> > > > > > to be unreliable and libaudit1 is part of the the essential set 
> > > > > > (login
> > > > > > depends on it). Instead, their respective preinst script should 
> > > > > > create
> > > > > > protective diversions
> > > > > > 
> > > > > > dpkg-divert --package libaudit1t64 --no-rename --divert 
> > > > > > /lib/x86_64-linux-gnu/libaudit.so.1.usr-is-merged 
> > > > > > /lib/x86_64-linux-gnu/libaudit.so.1
> > > > > > 
> > > > > > for each of the affected files with their aliased location. In this 
> > > > > > case
> > > > > > - since we cannot use Conflicts - we cannot get rid of these 
> > > > > > diversions
> > > > > > in postinst. We already have Breaks: libaudit1 (<< ...), but that 
> > > > > > allows
> > > > > > concurrent unpack and hence still allows for the file loss 
> > > > > > scenario. The
> > > > > > diversions should be cleaned up in forky's postinst.
> > > > > > 
> > > > > > I appreciate another upload of audit to experimental to verify the
> > > > > > mitigation.
> > > > > 
> > > > > Helmut
> > > > > 
> > > > 
> > > > -- 
> > > > Steve Langasek   Give me a lever long enough and a Free 
> > > > OS
> > > > Debian Developer   to set it on, and I can move the 
> > > > world.
> > > > Ubuntu Developer   
> > > > https://www.debian.org/
> > > > slanga...@ubuntu.com 
> > > > vor...@debian.org
> > > 
> > > > diff -Nru audit-3.1.2/debian/changelog audit-3.1.2/debian/changelog
> > > > --- audit-3.1.2/debian/changelog2024-01-24 15:05:18.0 
> > > > +
> > > > +++ audit-3.1.2/debian/changelog2024-01-31 20:39:17.0 
> > > > +
> > > > @@ -1,3 +1,19 @@
> > > > +audit (1:3.1.2-2.1~exp3) experimental; urgency=medium
> > > > +
> > > > +  * Proper complete fix for usrmerge.  Closes: #1061966.
> > > > +
> > > > + -- Steve Langasek   Wed, 31 Jan 2024 20:39:17 +
> > > > +
> > > > +audit (1:3.1.2-2.1~exp2) experimental; urgency=medium
> > > > +
> > > > +  * Non-maintainer upload.
> > > > +  * Rename libraries for 64-bit time_t transition.
> > > > +  * Fix uninstallable packages from the previous upload.
> > > > +  * Add usrmerge diversions in preinst to protect against file deletion
> > > > +due to libraries moving between packages.  Closes: #1061966.
> > > > +
> > > > + -- Steve Langasek   Wed, 31 Jan 2024 08:49:07 +
> > 

Bug#1062995: tslib: NMU diff for 64-bit time_t transition

[Steve Langasek]

Hi Martin,

On Wed, Feb 21, 2024 at 06:56:09AM +, Martin Kepplinger wrote:
> in general, tslib only ever uses time_t differences, so apart from one
> glitch when wrapping around, the library will continue to work after
> 2038 as-is.

Sorry, but that's immaterial: per
,
the ts_read() family of functions take a pointer to a struct that contains a
struct timeval, which means that sizes and offsets of elements in that
struct will be interpreted incorrectly across the ABI horizon.  This is an
ABI break.  It's the last element of struct ts_sample so offsets are not an
issue, but depending on the endianness of the architecture, a caller that
doesn't know you've moved to 64-bit time_t will be reading the wrong word;
and anything caller-side that happens to allocate arrays of ts_sample will
get the wrong size of the element.  (I'm assuming by the description of the
functions in the header that ts_sample is always allocated by the library
and not by the caller.)  But for ts_sample_mt it's even worse, the tv is in
the middle of the struct and throws everything off.

> I'll look at what `__TIMESIZE` currently is on 32bit archs. But given
> the low-impact this has for tslib functionality-wise, I'd rather find
> the correct change (any help appreciated), and increment LT_CURRENT.

> So: where do I start in order to comply with your scripts? do I simply
> add `D__USE_TIME_BITS64` to CPPFLAGS?

Once gcc and dpkg have been uploaded to unstable, we will be batch NMUing
these patches to unstable as well.  There should be no need for you to
manually adjust CPPFLAGS in your package; simply incorporating the NMU
changes will be sufficient.

-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developer   https://www.debian.org/
slanga...@ubuntu.com vor...@debian.org


signature.asc
Description: PGP signature

Bug#1064545: RFS: golang-goptlib/1.5.0-1 -- library for Tor pluggable transports written in Go

[Danial Behzadi]

Package: sponsorship-requests
Severity: normal

Dear mentors,

I am looking for a sponsor for my package "golang-goptlib":

* Package name : golang-goptlib
  Version  : 1.5.0-1
  Upstream contact : Tor Project
* URL  :
https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/goptlib
* License  : CC0-1.0
* Vcs  :
https://salsa.debian.org/pkg-privacy-team/golang-goptlib/
  Section  : golang

The source builds the following binary packages:

 golang-goptlib-dev - library for Tor pluggable transports written in Go

To access further information about this package, please visit the
following URL:

 https://mentors.debian.net/package/golang-goptlib/

Alternatively, you can download the package with 'dget' using this
command:

 dget -x
https://mentors.debian.net/debian/pool/main/g/golang-goptlib/golang-goptlib_1.5.0-1.dsc

Changes since the last upload:

golang-goptlib (1.5.0-1) unstable; urgency=medium
.
  * Update source in d/watch.
  * Use '_build' as build root.
  * New upstream version 1.5.0

Regards,
--
Danial Behzadi

Bug#1052298: metafun broken?

[Karl Berry]

I noticed that there is now a package context-legacy.r69173.tar.xz in 
the TL/archive subdir . I contains a lot of stuff 
"tex/context/patterns/mkii". 

Yes, Siep created context-legacy to continue to support mkii.

I guess I have to package that and upload it into Debian.

Indeed. If you want to support that original context.

Please confirm.

Hans has prepared a new context(+luametatex) release for tl24, which I
will import into TL as soon as I have a chance. So I wouldn't spend your
time worrying about what is in TL now. (Although I don't expect the
structure of the packages to change, one never knows ...) --best, karl.

Bug#1064544: libwbclient-dev should provide more header files to be useful

[Michael Tokarev]

Package: src:samba
Version: 2:4.19.5+dfsg-1

 interface defines quite some structs and functions to
communicate with winbind.  However, it does not define WinNT status
codes, used, for example, in wbcAuthErrorInfo:nt_status.  Without
these, the code can not know actual reason of the error, and can't
handle it properly.

NT STATUS codes are declared in code/ntstatus.h.  However, this file
declares a few other functions which are internal to samba.  So it
isn't possible to just move that file to another package.

/mjt

Bug#1064542: please stop Build-Depending on samba-dev, use libwbclient-dev instead

[Michael Tokarev]

24.02.2024 01:21, Michael Tokarev:

Source: freeradius
Version: 3.2.3+dfsg-2
Severity: important
X-Debbugs-Cc: pkg-samba-de...@lists.alioth.debian.org

For a long time now, samba provides separate library libwbclient
(together with development package) which is actually public
(unlike the collection in samba-libs) and has stable API and ABI.
As far as I can see, freeradius only needs winbindd, not whole
samba.  samba-dev has too much private interfaces which should
not be used.


Actually this turns out not to be that simple.

src/modules/rlm_mschap/auth_wbclient.c includes core/ntstatus.h,
which defines core WinNR status codes.  Without that, 
is kind of useless.

It looks like we have to refine which headers are included in
which packages in samba.  Hmm..

/mjt

Bug#1052298: metafun broken?

[Hilmar Preuße]

On 27.10.23 22:31, Siep Kroonenberg wrote:

Hello,


The standalone context is mostly free from mkii, but cont-tmf.zip
still has most of the legacy stuff, which will mostly be added back
in, in the form of a context-legacy package for TL. I find sorting
things out and creating / modifying the .tlpsrc definitions for the
context packages a tricky business; it is going a lot slower than I
hoped and expected.



I noticed that there is now a package context-legacy.r69173.tar.xz in 
the TL/archive subdir . I contains a lot of stuff 
"tex/context/patterns/mkii". I guess I have to package that and upload 
it into Debian.


Please confirm.

Hilmar
--
Testmail



OpenPGP_signature.asc
Description: OpenPGP digital signature

Bug#1064543: python3-launchpadlib: Failed to start launchpadlib-cache-clean.service

[Kevin Locke]

Package: python3-launchpadlib
Version: 1.11.0-4
Severity: normal

Dear Maintainer,

After upgrading to 1.11.0-4, I have observed the following errors in
my system log:

2024-02-23T15:03:42-07:00 systemd[1538]: launchpadlib-cache-clean.service: 
Failed with result 'exit-code'.
2024-02-23T15:03:42-07:00 systemd[1538]: Failed to start 
launchpadlib-cache-clean.service - Clean up old files in the Launchpadlib cache.

After examining /usr/lib/systemd/user/launchpadlib-cache-clean.service
I suspect that this is because ~/.launchpadlib does not exist for my
user.  It would be nice if the unit only ran when required.  Perhaps

ConditionPathExists=%h/.launchpadlib/api.launchpad.net/cache

could be added to the [Unit] section of launchpadlib-cache-clean.service?

Thanks for considering,
Kevin


-- System Information:
Debian Release: trixie/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'oldstable-security'), (500, 'unstable'), 
(500, 'stable'), (101, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.8.0-rc5 (SMP w/4 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 python3-launchpadlib depends on:
ii  init-system-helpers 1.66
ii  python3 3.11.6-1
ii  python3-httplib20.20.4-3
ii  python3-lazr.restfulclient  0.14.6-1
ii  python3-lazr.uri1.0.6-3

python3-launchpadlib recommends no packages.

Versions of packages python3-launchpadlib suggests:
ii  python3-keyring24.3.0-1
ii  python3-pkg-resources  68.1.2-2
pn  python3-testresources  

-- no debconf information

Bug#1064542: please stop Build-Depending on samba-dev, use libwbclient-dev instead

[Michael Tokarev]

Source: freeradius
Version: 3.2.3+dfsg-2
Severity: important
X-Debbugs-Cc: pkg-samba-de...@lists.alioth.debian.org

For a long time now, samba provides separate library libwbclient
(together with development package) which is actually public
(unlike the collection in samba-libs) and has stable API and ABI.
As far as I can see, freeradius only needs winbindd, not whole
samba.  samba-dev has too much private interfaces which should
not be used.

Thanks,

/mjt

Bug#1064541: ITP: python-autoray -- Lightweight Python AUTOmatic-arRAY library for abstracting tensor operations

[Yogeswaran Umasankar]

Package: wnpp
Severity: wishlist
Owner: Yogeswaran Umasankar 
X-Debbugs-Cc: debian-de...@lists.debian.org, kd8...@gmail.com

* Package name: python-autoray
  Version : 0.6.8
  Upstream Contact: Johnnie Gray 
* URL : https://github.com/jcmgray/autoray
* License : Apache-2.0
  Programming Lang: Python
  Description : Lightweight Python AUTOmatic-arRAY library for abstracting 
tensor operations

Primarily it provides an automatic dispatch mechanism that
 means you can write backend agnostic code that works for
 numpy, pytorch, jax, cupy, dask, autograd, tensorflow,
 sparse, mars, etc., and indeed any library that provides a
 numpy-ish API, even if it knows nothing about autoray. This
 is a depend for other python and science packages. I planned
 to maintain it under DPT, and need sponsorship.

Bug#1064540: ITP: golang-github-makeworld-the-better-one-dither -- fast, correct image dithering library in Go

[Anthony Fok]

Package: wnpp
Severity: wishlist
Owner: Anthony Fok 

* Package name: golang-github-makeworld-the-better-one-dither
  Version : 2.4.0-1
  Upstream Author : makeworld
* URL : https://github.com/makeworld-the-better-one/dither
* License : MPL-2.0
  Programming Lang: Go
  Description : fast, correct image dithering library in Go

 dither is a library for dithering images in Go.  It has many dithering
 algorithms built-in, and allows you to specify your own.  Correctness
 is a top priority, as well as performance.  It is designed to work well
 on its own, but also implements interfaces from the standard library,
 so that it can be integrated easily in a wide variety of situtations.
 .
 This library is uniquely correct from a math and quality perspective.
 It linearizes the image, and color comparisons are done with human
 luminance perception in mind (channel weighting).  Few-to-no other
 libraries do this.
 .
 It supports images that make use of the alpha channel, AKA transparency.
 .
 Types of dithering supported:
 .
  * Random noise (in grayscale and RGB)
  * Ordered Dithering
- Bayer matrix of any size (as long as dimensions are powers of two)
- Clustered-dot - many different preprogrammed matrices
- Some unusual horizontal or vertical line matrices
- Yours?
  + Using PixelMapperFromMatrix, this library can dither using
any matrix
  + If you need more freedom, PixelMapper can be used to implement
any method of dithering that affects each pixel individually
 .
  * Error diffusion dithering
- Simple 2D
- Floyd-Steinberg, False Floyd-Steinberg
- Jarvis-Judice-Ninke
- Atkinson
- Stucki
- Burkes
- Sierra/Sierra3, Sierra2, Sierra2-4A/Sierra-Lite
- Steven Pigeon (https://hbfs.wordpress.com/2013/12/31/dithering/)
- Yours? Custom error diffusion matrices can be used by the library.
 .
 More methods of dithering are being worked on, such as Riemersma,
 Yuliluoma, and blue noise.

Reason for packaging: Needed by hugo (>= 0.123.0)

Bug#1064517: texlive-bin: CVE-2024-25262

[Moritz Muehlenhoff]

On Fri, Feb 23, 2024 at 10:13:53PM +0100, Hilmar Preuße wrote:
> On 23.02.24 16:31, Moritz Mühlenhoff wrote:
> 
> Hello Moritz,
> 
> > The following vulnerability was published for texlive-bin.
> > 
> > CVE-2024-25262[0]:
> > | texlive-bin commit c515e was discovered to contain heap buffer
> > | overflow via the function ttfLoadHDMX:ttfdump. This vulnerability
> > | allows attackers to cause a Denial of Service (DoS) via supplying a
> > | crafted TTF file.
> > 
> 
> I'll upload tl-bin -9 soon. Do we need a fix in Debian stable too?

It's rather harmless, I don't believe we need a DSA. If you make an
update for a forthcoming point release to fix other bugs it's worth
piggybacking this, though.

Cheers,
Moritz

Bug#1064539: systemd: DHCPPrefixDelegation does not allow zero value in Token=

[Fabian Müller]

Package: systemd
Version: 252.19-1~deb12u1
Severity: normal
Tags: ipv6
X-Debbugs-Cc: fmu+deb...@never-afk.de

Dear Maintainer,


   * What led up to the situation?

I wanted systemd-networkd to select the first address (zero) from the ipv6
prefix that was delegated to me. My provider (Vodafone Kabel / Germany) offers
me a /56 prefix via prefix delegation.

My .network file looks like this:

[Match]
Name=enp1s0

[Network]
IPv6AcceptRA=yes
DHCP=yes
DHCPPrefixDelegation=yes

[DHCPv6]
PrefixDelegationHint=::/56
UseDNS=no
UseAddress=no

[DHCPPrefixDelegation]
Token=static:::


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

I tried to set the "Token=" option in the [DHCPPrefixDelegation] section of my
.network file as follows:

[DHCPPrefixDelegation]
Token=static:::

   * What was the outcome of this action?

The resulting ipv6 address is selects via eui64 instead of static.
So i get a address like this 2001:db8::a60:6eff:feda:858a/64

   * What outcome did you expect instead?

I expected the address to be zero. More like this: 2001:db8::/64 (which is a
valid ipv6 address).

I also tried the following values:
Token=static:::0 # does not work
Token=:: # does not work
Token=static::: # does not work
Token=static:::1 # works as expected, but is not what i want, address would be
2001:db8::1/64


-- Package-specific info:

-- System Information:
Debian Release: 12.4
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: amd64 (x86_64)

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

Versions of packages systemd depends on:
ii  libacl12.3.1-3
ii  libaudit1  1:3.0.9-1
ii  libblkid1  2.38.1-5+b1
ii  libc6  2.36-9+deb12u3
ii  libcap21:2.66-4
ii  libcryptsetup122:2.6.1-4~deb12u1
ii  libfdisk1  2.38.1-5+b1
ii  libgcrypt201.10.1-3
ii  libkmod2   30+20221128-1
ii  liblz4-1   1.9.4-1
ii  liblzma5   5.4.1-0.2
ii  libmount1  2.38.1-5+b1
ii  libp11-kit00.24.1-2
ii  libseccomp22.5.4-1+b3
ii  libselinux13.4-1+b6
ii  libssl33.0.11-1~deb12u2
ii  libsystemd-shared  252.19-1~deb12u1
ii  libsystemd0252.19-1~deb12u1
ii  libzstd1   1.5.4+dfsg2-5
ii  mount  2.38.1-5+b1

Versions of packages systemd recommends:
ii  dbus [default-dbus-system-bus]   1.14.10-1~deb12u1
ii  systemd-timesyncd [time-daemon]  252.19-1~deb12u1

Versions of packages systemd suggests:
ii  libfido2-11.12.0-2+b1
ii  libqrencode4  4.1.1-1
pn  libtss2-esys-3.0.2-0  
pn  libtss2-mu0   
pn  libtss2-rc0   
ii  policykit-1   122-3
ii  polkitd   122-3
pn  systemd-boot  
ii  systemd-container 252.19-1~deb12u1
pn  systemd-homed 
ii  systemd-resolved  252.19-1~deb12u1
pn  systemd-userdbd   

Versions of packages systemd is related to:
ii  dbus-user-session  1.14.10-1~deb12u1
pn  dracut 
ii  initramfs-tools0.142
pn  libnss-systemd 
ii  libpam-systemd 252.19-1~deb12u1
ii  udev   252.19-1~deb12u1

-- no debconf information

Bug#1064538: perftest FTBFS on hppa: get_cycles not implemented

[John David Anglin]

Source: perftest
Version: 24.01.0+0.38-1
Severity: normal
Tags: ftbfs patch

Dear Maintainer,

See:
https://buildd.debian.org/status/fetch.php?pkg=perftest=hppa=24.01.0%2B0.38-1=1708389231=0

Attached patch fixes build.  Please install.

Regards,
Dave Anglin


-- System Information:
Debian Release: trixie/sid
  APT prefers buildd-unstable
  APT policy: (500, 'buildd-unstable'), (500, 'unstable')
Architecture: hppa (parisc64)

Kernel: Linux 6.1.77+ (SMP w/4 CPU threads)
Locale: LANG=C, 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)
--- ./src/get_clock.h.save  2024-02-23 21:28:08.358672860 +
+++ ./src/get_clock.h   2024-02-23 21:34:51.861653976 +
@@ -114,6 +114,14 @@
return perf_get_cycles();
 }
 
+#elif defined(__hppa__)
+typedef unsigned long long cycles_t;
+static inline cycles_t get_cycles(void)
+{
+   cycles_t clk;
+   asm volatile("mfctl %%cr16, %0" : "=r" (clk));
+   return clk;
+}
 #else
 #warning get_cycles not implemented for this architecture: attempt asm/timex.h
 #include 

Bug#1055067: isc-dhcp-client: network-manager 1.44.2-3 changed path to nm-dhcp-helper, apparmor need update

[Santiago Ruano Rincón]

El 30/10/23 a las 18:29, Sven-Haegar Koch escribió:
> Package: isc-dhcp-client
> Version: 4.4.3-P1-4
> Severity: normal
> 
> Dear Maintainer,
> 
> I am using network manager with /etc/NetworkManager/NetworkManager.conf
> 
>   [main]
>   dhcp=dhclient
> 
> and thus using isc-dhcp-client as my DHCP client.
> 
> With the update of network-manager 1.44.2-3 the nm-dhcp-helper moved
> from /usr/lib/NetworkManager/ to /usr/libexec/.
> 
> Without a fix to /etc/apparmor.d/sbin.dhclient the system now fails to
> activate interfaces using DHCP, logging
> 
> audit: type=1400 audit(1698680734.539:50): apparmor="DENIED" operation="exec" 
> class="file" profile="/{,usr/}sbin/dhclient" 
> name="/usr/libexec/nm-dhcp-helper" pid=7523 comm="dhclient" 
> requested_mask="x" denied_mask="x" fsuid=0 ouid=0
> 
> The following diff fixes it for me - just duplicating the existing
> rules to the new path:
> 
> diff --git a/etc/apparmor.d/sbin.dhclient b/etc/apparmor.d/sbin.dhclient
> index 1acc6b92..b219d688 100644
> --- a/etc/apparmor.d/sbin.dhclient
> +++ b/etc/apparmor.d/sbin.dhclient
> @@ -69,6 +69,8 @@
># Support the new executable helper from NetworkManager.
>/usr/lib/NetworkManager/nm-dhcp-helper  Pxrm,
>signal (receive) peer=/usr/lib/NetworkManager/nm-dhcp-helper,
> +  /usr/libexec/nm-dhcp-helper Pxrm,
> +  signal (receive) peer=/usr/libexec/nm-dhcp-helper,
>  
># Site-specific additions and overrides. See local/README for details.
>#include 
> @@ -101,6 +103,21 @@
>network inet6 dgram,
>  }
>  
> +/usr/libexec/nm-dhcp-helper {
> +  #include 
> +  #include 
> +  /usr/libexec/nm-dhcp-helper mr,
> +
> +  /run/NetworkManager/private-dhcp rw,
> +  signal (send) peer=/sbin/dhclient,
> +
> +  /var/lib/NetworkManager/*lease r,
> +  signal (receive) peer=/usr/sbin/NetworkManager,
> +  ptrace (readby) peer=/usr/sbin/NetworkManager,
> +  network inet dgram,
> +  network inet6 dgram,
> +}
> +
>  /usr/lib/connman/scripts/dhclient-script {
>#include 
>#include 
> 
> 
> Greetings,
> Sven

Hi!

Really sorry, this has fallen through the cracks.

Could you please confirm the version available in this repo fixes the
issue:

https://debian.pages.debian.net/-/isc-dhcp/-/jobs/5350735/artifacts/aptly/index.html

Cheers,

 -- Santiago


signature.asc
Description: PGP signature

Bug#1064537: ITP: golang-github-schollz-peerdiscovery -- Pure-Go library for cross-platform local peer discovery using UDP multicast :woman: :repeat: :woman:

[Guilherme Puida Moreira]

Package: wnpp
Severity: wishlist
Owner: Guilherme Puida Moreira 

* Package name: golang-github-schollz-peerdiscovery
  Version : 1.7.2-1
  Upstream Author : Zack
* URL : https://github.com/schollz/peerdiscovery
* License : Expat
  Programming Lang: Go
  Description : Pure-Go library for cross-platform local peer discovery 
using UDP multicast :woman: :repeat: :woman:

 Pure-go library for cross-platform thread-safe local peer discovery using
 UDP multicast.

This is a dependency of croc, which I'm also working on packaging

Bug#1064194: Info received (Bug#1064194: 535.86.05 breaks Xorg)

[Harald Dunkel]

For verification I have installed Bookworm on an external SSD (using
debootstrap), added Gnome and nvidia-graphics-drivers 525 and verified,
upgraded to Testing and verified, and upgraded to Unstable and verified
(still 525.147.05-7~deb12u1). X worked.

Next I cherry-picked nvidia 535.86.10-1 from experimental and tried
again: Now its broken.

Please note there is no xorg.conf

Regards
Harri

Bug#1059356: python3-poetry: No module named 'poetry_plugin_export'

[Emmanuel Arias]

Hi Tomas!

You are right the poetry-plugin-export was missed,
but now we have it in Debian. The reason about why
it did not fail before, because I deactivated the
tests until poetry-plugin-export be in Debian.

A good question is about why it has never been
reported before :-).

FYI, I'm working in the version 1.8.0.dev0. As it
was no released yet, I will go first to experimental.

-- 
cheers,
Emmanuel Arias

 ⢀⣴⠾⠻⢶⣦⠀
 ⣾⠁⢠⠒⠀⣿⡁  eam...@debian.org
 ⢿⡄⠘⠷⠚⠋⠀  OpenPGP: 13796755BBC72BB8ABE2AEB5 FA9DEC5DE11C63F1
 
 ⠈⠳⣄


signature.asc
Description: PGP signature

Bug#1064517: texlive-bin: CVE-2024-25262

[Hilmar Preuße]

On 23.02.24 16:31, Moritz Mühlenhoff wrote:

Hello Moritz,


The following vulnerability was published for texlive-bin.

CVE-2024-25262[0]:
| texlive-bin commit c515e was discovered to contain heap buffer
| overflow via the function ttfLoadHDMX:ttfdump. This vulnerability
| allows attackers to cause a Denial of Service (DoS) via supplying a
| crafted TTF file.



I'll upload tl-bin -9 soon. Do we need a fix in Debian stable too?

Hilmar
--
Testmail



OpenPGP_signature.asc
Description: OpenPGP digital signature

Bug#1064369: gobject-introspection dropped versioned dependency on python3

[Jeremy Bícha]

Matthias,

Since glib and gobject-introspection have migrated out of
noble-proposed, is there still a need to keep this bug open?

Thank you,
Jeremy Bícha

Bug#1064536: scribus: Please package 1.6.1

[Jeremy Bícha]

Source: scribus
Version: 1.5.8+dfsg-5
Severity: wishlist

Please package scribus 1.6.1. 1.5.x is technically a development series.

https://www.scribus.net/scribus-1-6-0-released/
https://scribus.net/scribus-1-6-1-released/

Thank you,
Jeremy Bícha

Bug#1064535: python-fudge: cleanup: Sphinx now supports SOURCE_DATE_EPOCH natively

[James Addison]

Source: python-fudge
Version: 1.1.1-2
Severity: wishlist
User: reproducible-bui...@lists.alioth.debian.org
Usertags: timestamps

Dear Maintainer,

I'm an occasional volunteer contributor with the Reproducible Builds[1]
project, and noticed that the python-fudge package failed an automated
reproducible build test[2] recently.

While investigating the cause, I found that the debian/rules file in the
python-fudge source package contains some SOURCE_DATE_EPOCH logic that is
now natively supported[3] by Sphinx itself.

I believe that removing the SPHINX_DATE_EPOCH-related logic from the
debian/rules file should be possible, and is likely to address the cause of
the reproducibility failure.

To assist with confirmation that your package is reproducible, you may
optionally enable Debian Salsa's Continuous Integration[4]; this includes a
utility called 'reprotest' that will test two maximally-varying builds of
your source package and indicate whether the binary packages remain identical
(as intended) despite build environment variance.

Thank you,
James

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

[2] - 
https://tests.reproducible-builds.org/debian/rb-pkg/trixie/arm64/diffoscope-results/python-fudge.html

[3] - https://github.com/sphinx-doc/sphinx/pull/1954

[4] - https://salsa.debian.org/salsa-ci-team/pipeline/

Bug#1064534: rofi as dmenu replacement

[Wesley Schwengle]

Package: rofi
Version: 1.7.5-0.1+b1
Severity: wishlist
X-Debbugs-Cc: wes...@schwengle.net

Dear Maintainer,

I saw a cool thing on /r/unixporn on reddit and it made me look at rofi. I want
to replace it for the dmenu call to dmenu of suckless-tools. However there is
an issue.

rofi states that it is a drop-in replacement for dmenu. If you call rofi as
dmenu, eg by linking it ln -s /usr/bin/rofi /usr/bin/dmenu you get to have all
the toys. This works pretty well as long as you have suckless-tools installed.

Without suckless-tools i3 for example doesn't work correctly. This is because
i3 calls dmenu_run, which is provided by suckless-tools. dmenu_run calls
/usr/bin/dmenu_path which is also provided by suckless-tools.

My question is as follows, is there a way that both suckless-tools and rofi
start providing dmenu (as an update-alternatives) and that both suckless-tools
and rofi depend on a package that is called dmenu-data which provides dmenu_run
and dmenu_path?

I filed this against rofi, because rofi is the one not providing some of the
crucial infra to be a replacement for dmenu.

$ apt-cache depends i3
i3
  Depends: i3-wm
  Recommends: i3lock
  Recommends: suckless-tools
  Recommends: dunst

By implementing the dmenu_path and dmenu_run scripts from suckless-tools the i3
recommends can be either suckless-tools or rofi.

Many thanks!
Wesley



-- System Information:
Debian Release: trixie/sid
  APT prefers unstable
  APT policy: (900, 'unstable'), (500, 'experimental'), (500, 'testing'), (10, 
'stable-updates'), (10, 'stable-security'), (10, 'oldstable-security'), (10, 
'oldoldstable'), (10, 'stable'), (10, 'oldstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.6.15-amd64 (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=C.UTF-8, LC_CTYPE=C.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 rofi depends on:
ii  libc6 2.37-15
ii  libcairo2 1.18.0-1+b1
ii  libgdk-pixbuf-2.0-0   2.42.10+dfsg-3+b1
ii  libglib2.0-0  2.78.4-1
ii  libpango-1.0-01.51.0+ds-4
ii  libpangocairo-1.0-0   1.51.0+ds-4
ii  libstartup-notification0  0.12-6+b1
ii  libxcb-cursor00.1.4-1+b1
ii  libxcb-ewmh2  0.4.1-1.1+b1
ii  libxcb-icccm4 0.4.1-1.1+b1
ii  libxcb-randr0 1.15-1
ii  libxcb-util1  0.4.0-1+b1
ii  libxcb-xinerama0  1.15-1
ii  libxcb-xkb1   1.15-1
ii  libxcb1   1.15-1
ii  libxkbcommon-x11-01.6.0-1
ii  libxkbcommon0 1.6.0-1

rofi recommends no packages.

rofi suggests no packages.

-- no debconf information

Bug#1063376: Add blockers

[Andreas Tille]

Control: block -1 by 1063377
Control: block -1 by 1063378
Control: block -1 by 1063379

Adding blockers.  Please remove the rdepends first.

Kind regards
Andreas.

-- 
http://fam-tille.de

Bug#1062371: Add blocking bugs

[Andreas Tille]

Control: block -1 by 1063060
Control: block -1 by 1063063

The bugs to remove reverse dependencies were filed.  For your
convenience I have added these as blocker.  It would be great if the
packages in question could be removed in the near future to stop
cluttering our developer mailing list with testing removal mails.

Thanks a lot
Andreas.

-- 
http://fam-tille.de

Bug#1064533: src:peony: fails to migrate to testing for too long: new Build-Depends not available everywhere

[Paul Gevers]

Source: peony
Version: 3.2.4-2
Severity: serious
Control: close -1 4.0.0.0-1
Tags: sid trixie
User: release.debian@packages.debian.org
Usertags: out-of-sync

Dear maintainer(s),

The Release Team considers packages that are out-of-sync between testing 
and unstable for more than 30 days as having a Release Critical bug in 
testing [1]. Your package src:peony has been trying to migrate for 31 
days [2]. Hence, I am filing this bug. The version in unstable 
apparently has a new Build-Depends. It's not available on armel, armhf, 
i386, mips64el and ppc64el. If the Build-Depends can't be worked around, 
you'll need to request binary removals from those architectures from 
unstable $(reportbug ftp.debian.org).


If a package is out of sync between unstable and testing for a longer 
period, this usually means that bugs in the package in testing cannot be 
fixed via unstable. Additionally, blocked packages can have impact on 
other packages, which makes preparing for the release more difficult. 
Finally, it often exposes issues with the package and/or
its (reverse-)dependencies. We expect maintainers to fix issues that 
hamper the migration of their package in a timely manner.


This bug will trigger auto-removal when appropriate. As with all new 
bugs, there will be at least 30 days before the package is auto-removed.


I have immediately closed this bug with the version in unstable, so if 
that version or a later version migrates, this bug will no longer affect 
testing. I have also tagged this bug to only affect sid and trixie, so 
it doesn't affect (old-)stable.


If you believe your package is unable to migrate to testing due to 
issues beyond your control, don't hesitate to contact the Release Team.


Paul

[1] https://lists.debian.org/debian-devel-announce/2023/06/msg1.html
[2] https://qa.debian.org/excuses.php?package=peony



OpenPGP_signature.asc
Description: OpenPGP digital signature

Bug#1064532: src:dt-schema: fails to migrate to testing for too long: autopkgtest failure

[Paul Gevers]

Source: dt-schema
Version: 2022.08.2-5
Severity: serious
Control: close -1 2023.11-3
Tags: sid trixie
User: release.debian@packages.debian.org
Usertags: out-of-sync

Dear maintainer(s),

The Release Team considers packages that are out-of-sync between testing 
and unstable for more than 30 days as having a Release Critical bug in 
testing [1]. Your package src:dt-schema has been trying to migrate for 
31 days [2]. Hence, I am filing this bug. The version in unstable fails 
its own autopkgtest.


If a package is out of sync between unstable and testing for a longer 
period, this usually means that bugs in the package in testing cannot be 
fixed via unstable. Additionally, blocked packages can have impact on 
other packages, which makes preparing for the release more difficult. 
Finally, it often exposes issues with the package and/or
its (reverse-)dependencies. We expect maintainers to fix issues that 
hamper the migration of their package in a timely manner.


This bug will trigger auto-removal when appropriate. As with all new 
bugs, there will be at least 30 days before the package is auto-removed.


I have immediately closed this bug with the version in unstable, so if 
that version or a later version migrates, this bug will no longer affect 
testing. I have also tagged this bug to only affect sid and trixie, so 
it doesn't affect (old-)stable.


If you believe your package is unable to migrate to testing due to 
issues beyond your control, don't hesitate to contact the Release Team.


Paul

[1] https://lists.debian.org/debian-devel-announce/2023/06/msg1.html
[2] https://qa.debian.org/excuses.php?package=dt-schema



OpenPGP_signature.asc
Description: OpenPGP digital signature

Bug#1061765: Help needed to fix python-coverage-test-runner

[Gunnar Wolf]

Andreas Tille dijo [Fri, Feb 23, 2024 at 03:22:27PM +0100]:
> HI Andrius,
> 
> Am Fri, Feb 23, 2024 at 09:29:27AM +0200 schrieb Andrius Merkys:
> > > ModuleNotFoundError: No module named 'imp'
> > 
> > I had a similar problem. I worked it around by depending on
> > python3-zombie-imp, the original code did not require any modifications.
> 
> Nice hint - implemented.

Thank you very much for your work, Andreas!

Bug#1064531: src:amberol: unsatisfied build dependency in testing: librust-lofty-0.17-dev

[Paul Gevers]

Source: amberol
Version: 0.10.3-2
Severity: serious
Tags: sid trixie
User: debian...@lists.debian.org
Usertags: edos-uninstallable

Dear maintainer(s),

Dose [1] is reporting a build issue with your package, it's missing a
build dependency. Obviously your build dependencies shouldn't be
removed from testing, but unfortunately there are multiple scenarios
where that can happen nevertheless. To uphold our social contract,
Debian requires that packages can be rebuild from source in the suite
we are shipping them, so currently this is a serious issue with your
package in testing.

Can you please investigate the situation and figure out how to resolve
it? Regularly, if the build dependency is available in unstable,
helping the maintainer of your Build-Depends to enable migration to
testing is a great way to solve the issue. If your build dependency is
gone from unstable and testing, you'll have to fix the build process
in some other way.

Paul

Note: this bug report was sent after some quick manual checks using a
template. Please reach out to me if you believe I made a mistake in my
process.

[1] https://qa.debian.org/dose/debcheck/src_testing_main/latest/amd64.html



OpenPGP_signature.asc
Description: OpenPGP digital signature

Bug#1064513: kea-dhcp4-server: Apparmor profile does not include /etc/apparmor.d/local/ file

[Andreas Hasenack]

PR at https://salsa.debian.org/debian/isc-kea/-/merge_requests/43

On Fri, Feb 23, 2024 at 12:27 PM Théophile Bastian
 wrote:
>
> Package: kea-dhcp4-server
> Version: 2.2.0-6
> Severity: normal
> X-Debbugs-Cc: theophile.bast...@echirolles.fr
>
> Dear Maintainer,
>
> The currently packaged apparmor profile for kea-dhcp4-server (and probably
> other kea-*, although I did not check) does not include the
> /etc/apparmor.d/local/usr.sbin.kea-dhcp4 local profile.
>
> I am currently trying to setup a Kea HA cluster, but the Apparmor profile
> prevents me from loading SSL certificates (under some non-kea directory in
> /etc/). Although I could override the shipped profile, I would rather edit the
> file under `local/` and leave the main file unchanged, so that packages 
> updates
> may deploy new versions of this file.
>
> Best regards,
> -- Théophile Bastian
>
> -- System Information:
> Debian Release: 12.5
>   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/1 CPU thread; 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 kea-dhcp4-server depends on:
> ii  init-system-helpers  1.65.2
> ii  kea-common   2.2.0-6
> ii  libc62.36-9+deb12u4
> ii  libgcc-s112.2.0-14
> ii  libstdc++6   12.2.0-14
>
> kea-dhcp4-server recommends no packages.
>
> Versions of packages kea-dhcp4-server suggests:
> pn  kea-doc  
>
> -- Configuration Files:
> /etc/kea/kea-dhcp4.conf changed [not included]
>
> -- no debconf information

Bug#1064513:

[Andreas Hasenack]

Oh, good one. dh_apparmor takes care of generating the local/* file,
but it of course won't change the main profile file to include it...

Bug#1056992: freerdp2 version 3

[Sylvain Archenault]

Hi Mike & team,

Is there something blocking you to start packaging v3 ?

Thanks
Sylvain

Bug#1057089: bookworm-pu: package usrmerge/37~deb12u1

[Andreas Beckmann]

On 30/11/2023 09.49, Marco d'Itri wrote:

On Nov 29, Andreas Beckmann  wrote:


Improve the usrmerge experience in bookworm.

Great idea, thank you for working on this!


The bookworm branch and a signed tag can be found in

https://salsa.debian.org/anbe/usrmerge.git

(IIRC merge requests don't handle tags, therefore I'm not creating one.)


Andreas

Bug#1056232: celery's autopkg tests fail with Python 3.12

[Colin Watson]

Control: reassign -1 python3-kombu
Control: forwarded -1 https://github.com/celery/kombu/issues/1804
Control: affects -1 src:celery
Control: fixed -1 kombu/5.3.4-1
Control: close -1

On Sun, Nov 19, 2023 at 12:08:09PM +0100, Matthias Klose wrote:
> celery's autopkg tests fail with Python 3.12. All failing like:
[...]
> 544s self = 
> 544s instance = 
> 544s value =  0x73c86780>
> 544s
> 544s def __set__(self, instance, value):
> 544s if instance is None:
> 544s return self
> 544s
> 544s >   with self.lock:
> 544s E   AttributeError: 'cached_property' object has no attribute
> 'lock'
> 544s
> 544s /usr/lib/python3/dist-packages/kombu/utils/objects.py:37:
> AttributeError

This was https://github.com/celery/kombu/issues/1804, fixed in kombu
5.3.3, which has been in Debian for a few months now.  (#1058317 is
still a problem, but is a separate bug.)

Thanks,

-- 
Colin Watson (he/him)  [cjwat...@debian.org]

Bug#1064530: pagure: (Build-)depend on celery rather than python-celery-common

[Colin Watson]

Source: pagure
Version: 5.11.3+dfsg-2.1
Severity: normal

https://bugs.debian.org/1038295 requests that the transitional package
python-celery-common be dropped from the archive.  However, pagure still
(build-)depends on it.  Please could you (build-)depend on its
replacement "celery" package instead, if that's still appropriate?

Thanks,

-- 
Colin Watson (he/him)  [cjwat...@debian.org]

Bug#1064276: python-channels-redis 4.0.0-1+deb12u1 flagged for acceptance

[Jonathan Wiltshire]

package release.debian.org
tags 1064276 = bookworm pending
thanks

Hi,

The upload referenced by this bug report has been flagged for acceptance into 
the proposed-updates queue for Debian bookworm.

Thanks for your contribution!

Upload details
==

Package: python-channels-redis
Version: 4.0.0-1+deb12u1

Explanation: 

Bug#1063823: nvidia-graphics-drivers 470.223.02-2 flagged for acceptance

[Jonathan Wiltshire]

package release.debian.org
tags 1063823 = bullseye pending
thanks

Hi,

The upload referenced by this bug report has been flagged for acceptance into 
the proposed-updates queue for Debian bullseye.

Thanks for your contribution!

Upload details
==

Package: nvidia-graphics-drivers
Version: 470.223.02-2

Explanation: end support for Tesla 450 drivers; build libnvidia-fbc1 for arm64

Bug#1055115: prometheus-node-exporter-collectors 0.0~git20230203.6f710f8-1+deb12u1 flagged for acceptance

[Jonathan Wiltshire]

package release.debian.org
tags 1055115 = bookworm pending
thanks

Hi,

The upload referenced by this bug report has been flagged for acceptance into 
the proposed-updates queue for Debian bookworm.

Thanks for your contribution!

Upload details
==

Package: prometheus-node-exporter-collectors
Version: 0.0~git20230203.6f710f8-1+deb12u1

Explanation: do not adversely affect mirror network; fix deadlock with other 
apt update runs

Bug#1064529: python3-hmmlearn: installed metadata wrong, `pip show hmmlearn` shows 0.0.0

[Michael R. Crusoe]

Package: python3-hmmlearn
Version: 0.3.0-4
Severity: normal
X-Debbugs-Cc: cru...@debian.org

# pip show hmmlearn
Name: hmmlearn
Version: 0.0.0
Summary: Hidden Markov Models in Python with scikit-learn like API
Home-page: https://github.com/hmmlearn/hmmlearn
Author:
Author-email:
License: new BSD
Location: /usr/lib/python3/dist-packages
Requires: numpy, scikit-learn, scipy
Required-by:

# dpkg -L python3-hmmlearn | grep dist-info
/usr/lib/python3/dist-packages/hmmlearn-0.0.0.dist-info
/usr/lib/python3/dist-packages/hmmlearn-0.0.0.dist-info/INSTALLER
/usr/lib/python3/dist-packages/hmmlearn-0.0.0.dist-info/METADATA
/usr/lib/python3/dist-packages/hmmlearn-0.0.0.dist-info/WHEEL
/usr/lib/python3/dist-packages/hmmlearn-0.0.0.dist-info/top_level.txt

--
Michael R. Crusoe



OpenPGP_signature.asc
Description: OpenPGP digital signature

Bug#1064528: fish: loss of rendering (color) difference between valid and broken symbolic links

[Patrice Duroux]

Package: fish
Version: 3.7.0-1
Severity: wishlist

Dear Maintainer,

Going back to 3.6.4-1 confirms me that it was due to the last upgrade.
Reading the fish release note, it is not clear that something is supposed to be
changed with 3.7.0 unless the section 'Deprecations and removed features', but
it is not exactly my point I think.


Regards,
Patrice



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

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

Versions of packages fish depends on:
ii  bsdextrautils  2.39.3-6
ii  fish-common3.7.0-1
ii  groff-base 1.23.0-3
ii  libc6  2.37-15
ii  libpcre2-32-0  10.42-4+b1
ii  libstdc++6 14-20240201-3
ii  libtinfo6  6.4+20240113-1
ii  man-db 2.12.0-3
ii  procps 2:4.0.4-4
ii  python33.11.6-1

Versions of packages fish recommends:
ii  firefox [www-browser]   123.0-1
ii  google-chrome-stable [www-browser]  122.0.6261.69-1
ii  lynx [www-browser]  2.9.0rel.0-2
ii  vivaldi-stable [www-browser]6.5.3206.63-1
ii  xsel1.2.1-1

Versions of packages fish suggests:
pn  doc-base  

-- no debconf information

Bug#1057447: broadcom-sta-dkms: module build fails for Linux 6.6: wl_linux.c:486:12: error: 'struct net_device' has no member named 'wireless_handlers'

[Andreas Beckmann]

Followup-For: Bug #1057447
Control: found -1 6.30.223.271-24~exp1
Control: tag -1 + patch

This issue is caused by
a) version parsing that expects three numeric components (6.6.1-foo) and
   fails if there are only two (6.7-rc1)
b) broken version comparison logic
which turn on APICHOICE=FORCE_WEXT on kernels without
CONFIG_WIRELESS_EXT

Attached patch fixes that.

Verified to be able to build a module for 6.7-cloud-amd64.


Andreas
Author: Andreas Beckmann 
Description: fix detection of LINUXVER_WEXT_ONLY
 - fix version parsing if there are only two numeric components (e.g. 6.7-rc1)
 - set SUBLEVEL to 0 if missing
 - fix version comparison logic
 - -a and -o don't have well defined precedence
Bug-Debian: https://bugs.debian.org/1057447

--- a/amd64/Makefile
+++ b/amd64/Makefile
@@ -20,20 +20,22 @@
 
 ifneq ($(KERNELRELEASE),)
 
-  VERSION := $(shell echo $(KERNELRELEASE) | sed -e 
's/\([0-9]*\)[.]\([0-9]*\)[.]\([0-9]*\)\(.*\)/\1/')
-  PATCHLEVEL := $(shell echo $(KERNELRELEASE) | sed -e 
's/\([0-9]*\)[.]\([0-9]*\)[.]\([0-9]*\)\(.*\)/\2/')
-  SUBLEVEL := $(shell echo $(KERNELRELEASE) | sed -e 
's/\([0-9]*\)[.]\([0-9]*\)[.]\([0-9]*\)\(.*\)/\3/')
+  VERSION := $(shell echo $(KERNELRELEASE) | sed -e 
's/\([0-9]*\)[.]\([0-9]*\)\(.*\)/\1/')
+  PATCHLEVEL := $(shell echo $(KERNELRELEASE) | sed -e 
's/\([0-9]*\)[.]\([0-9]*\)\(.*\)/\2/')
+  SUBLEVEL := $(shell echo $(KERNELRELEASE) | sed -e 
's/\([0-9]*\)[.]\([0-9]*\)[.]\([0-9]*\)\(.*\)/\3/; 
s/\([0-9]*\)[.]\([0-9]*\)\(.*\)/0/')
 
+  # >= 2.6.32
   LINUXVER_GOODFOR_CFG80211:=$(strip $(shell \
-if [ "$(VERSION)" -ge "2" -a "$(PATCHLEVEL)" -ge "6" -a "$(SUBLEVEL)" -ge 
"32" -o "$(VERSION)" -ge "3" ]; then \
+if [ "$(VERSION).$(PATCHLEVEL)" = "2.6" -a "$(SUBLEVEL)" -ge "32" ] || [ 
"$(VERSION)" -eq "2" -a "$(PATCHLEVEL)" -ge "7" ] || [ "$(VERSION)" -ge "3" ]; 
then \
   echo TRUE; \
 else \
   echo FALSE; \
 fi \
   ))
 
+  # < 2.6.17
 LINUXVER_WEXT_ONLY:=$(strip $(shell \
-if [ "$(VERSION)" -ge "2" -a "$(PATCHLEVEL)" -ge "6" -a "$(SUBLEVEL)" -ge 
"17" ]; then \
+if [ "$(VERSION).$(PATCHLEVEL)" = "2.6" -a "$(SUBLEVEL)" -ge "17" ] || [ 
"$(VERSION)" -eq "2" -a "$(PATCHLEVEL)" -ge "7" ] || [ "$(VERSION)" -ge "3" ]; 
then \
   echo FALSE; \
 else \
   echo TRUE; \

Bug#1064527: ITP: golang-github-schollz-logger -- Simplistic, opinionated logging for Golang

[Guilherme Puida Moreira]

Package: wnpp
Severity: wishlist
Owner: Guilherme Puida Moreira 

* Package name: golang-github-schollz-logger
  Version : 1.2.0-1
  Upstream Author : Zack
* URL : https://github.com/schollz/logger
* License : Expat
  Programming Lang: Go
  Description : Simplistic, opinionated logging for Golang

 Simplistic, opinionated logging for Golang
  * Zero dependencies
  * Global logger (with optional local logger)
  * Leveled
  * Useful defaults / i.e. zero-config
  * Simple API
  * Colors on Linux (Windows colors are horrible and unnecessary)
  * Set leveling via environmental variables
LOGGER=trace|debug|info|warn|error

This is a dependency of croc, which I'm also working on packaging.

Bug#1064526: Please package upstream release 3.9.0

[Thomas Goirand]

Source: prettytable
Version: 3.6.0-1
Severity: wishlist

Hi,

The next OpenStack release codename Caracal needs upstream version 3.9.0,
could you please upgrade your package to that version?

Cheers,

Thomas Goirand (zigo)

Bug#1064525: ITP: libtest-expander-perl -- collection of frequentely used test functionalities

[gregor herrmann]

Package: wnpp
Owner: gregor herrmann 
Severity: wishlist
X-Debbugs-CC: debian-de...@lists.debian.org, debian-p...@lists.debian.org

* Package name: libtest-expander-perl
  Version : 2.5.0
  Upstream Author : Jurij Fajnberg 
* URL : https://metacpan.org/release/Test-Expander
* License : Artistic or GPL-1+
  Programming Lang: Perl
  Description : collection of frequentely used test functionalities

The primary objective of Test::Expander is to provide additional convenience
functions for tests based on Test2::V0, considering boilerplate aspects that
seem to be important in a notable number of cases. These are among other
things:

Repeated application of class/module and/or method/function to be tested.

The frequent necessity of introduction of a temporary directory and/or file.

Another fuctionality frequently used in tests relates to the work with files
and directories: reading, writing, creation, etc.

Run tests in a clean environment, where only explicitly mentioned environment
variables are set and environment variables from the "outside world" cannot
affect the execution of tests.

The package will be maintained under the umbrella of the Debian Perl Group.

--
Generated with the help of dpt-gen-itp(1) from pkg-perl-tools.


signature.asc
Description: Digital Signature

Bug#1064523: ITP: golang-github-kalafut-imohash -- Fast hashing for large files

[Guilherme Puida Moreira]

Package: wnpp
Severity: wishlist
Owner: Guilherme Puida Moreira 

* Package name: golang-github-kalafut-imohash
  Version : 1.0.3-1
  Upstream Author : Jim Kalafut
* URL : https://github.com/kalafut/imohash
* License : Expat
  Programming Lang: Go
  Description : Fast hashing for large files

 imohash is a fast, constant-time hashing library for Go. It uses file
 size and sampling to calculate hashes quickly, regardless of file size.
 .
 Uses
 .
 Because imohash only reads a small portion of a file's data, it is very
 fast and well suited to file synchronization and deduplication,
 especially over a fairly slow network. A need to manage media (photos
 and video) over Wi-Fi between a NAS and multiple family computers is how
 the library was born.

This is a dependency of croc, which I'm also working on packaging.

Bug#1064522: RM: cpdb-backend-file -- RoQA; unused

[Jeremy Bícha]

Package: ftp.debian.org
User: cpdb-backend-f...@packages.debian.org
Usertags: remove
Control: affects -1 src:cpdb-backend-file
X-Debbugs-Cc: cpdb-backend-f...@packages.debian.org, till.kamppe...@gmail.com

Please remove cpdb-backend-file from Debian. It has no reverse
dependencies and it is not expected for anything to use it in the
future. This is because print dialogs already support printing to PDF
without needing an extra helper.

I have confirmed this with OpenPrinting maintainer Till Kamppeter today.

Thank you,
Jeremy Bícha

Bug#949436: firmware-iwlwifi: Got an HT rate (flags:0x88/mcs:15) for a non data frame

[Patrice Duroux]

Hi Diederik,
No more the case, everything is fine after many upgrades since this issue.
My system is still the same hardware but with a Debian sid.
So, on my side, you can close it.

Regards,
Patrice

Le ven. 23 févr. 2024 à 15:39, Diederik de Haas
 a écrit :
>
> Control: tag -1 moreinfo
>
> On 20 Jan 2020 22:32:26 +0100 Patrice Duroux  wrote:
> > Package: firmware-iwlwifi
> > Version: 20190717-2
> >
> > I am reporting this «exception» here without being sure this is the right
> > package or if it has been already reported (not easy to check).
> >
> > [   48.335755] [ cut here ]
> > [   48.335766] Got an HT rate (flags:0x88/mcs:15) for a non data frame
> > [   48.335839] WARNING: CPU: 7 PID: 543 at
> > drivers/net/wireless/intel/iwlwifi/mvm/tx.c:333
> > ...
> > [   48.336015] CPU: 7 PID: 543 Comm: irq/37-iwlwifi Tainted: G   OE
> > 5.4.0-3-amd64 #1 Debian 5.4.13-1
> > [   48.336018] Hardware name: Hewlett-Packard HP ZBook 15 G2/2253, BIOS M70
> > Ver. 01.25 08/29/2019
> > [   48.336039] RIP: 0010:iwl_mvm_get_tx_rate.isra.0+0xc0/0xd0 [iwlmvm]
> > ...
> > [   48.336079] Call Trace:
> > [   48.336105]  iwl_mvm_set_tx_cmd_rate+0x66/0xc0 [iwlmvm]
> > [   48.336125]  iwl_mvm_set_tx_params+0x337/0x4f0 [iwlmvm]
> > ...
> > [   48.336862] ---[ end trace c6ab05d82de48c15 ]---
>
> While firmware may be relevant, a kernel stack trace indicates it's more 
> likely
> to be a kernel problem.
> Can you reproduce this issue with more recent firmware and kernel?

Bug#1064521: ITP: libscalar-readonly-perl -- functions for controlling whether any scalar variable is read-only

[gregor herrmann]

Package: wnpp
Owner: gregor herrmann 
Severity: wishlist
X-Debbugs-CC: debian-de...@lists.debian.org, debian-p...@lists.debian.org

* Package name: libscalar-readonly-perl
  Version : 0.03
  Upstream Author : Philippe M. Chiasson 
* URL : https://metacpan.org/release/Scalar-Readonly
* License : Artistic or GPL-1+
  Programming Lang: Perl
  Description : functions for controlling whether any scalar variable is 
read-only

This simple module can make scalars read-only. This is useful to protect
configuration variables, for example.

Scalar::Readonly can also be used to subvert Perl's many read-only variables
to potential evil trickery.

The package will be maintained under the umbrella of the Debian Perl Group.

--
Generated with the help of dpt-gen-itp(1) from pkg-perl-tools.


signature.asc
Description: Digital Signature

Bug#1064520: Acknowledgement (felher fork, "culpa", is maintained)

[Ian Jackson]

I looked into this a bit more and have suggested to withoutboats
(author of fehler) that they might like to grant crate name ownership
to the "culpa" (fork) maintainers.

https://github.com/withoutboats/fehler/issues/70
-- 
Ian JacksonThese opinions are my own.  

Pronouns: they/he.  If I emailed you from @fyvzl.net or @evade.org.uk,
that is a private address which bypasses my fierce spamfilter.

Bug#1064520: felher fork, "culpa", is maintained

[Ian Jackson]

Package: rust-fehler
Version: 1.0.0-1+b1
Severity: wishlist

The fehler crate is not presently maintained.  (Rumours[1] point to
the maintainer's employer's policies preventing the maintainer from
contribnuting to FLOSS>0

The package has been picked up by the community as "culpa".
We should consider whether we want to import that.

I reviewed the MR titles of the open and closed MRs so far and looked
at the various summary pages.  I think culpa 1.0.x is compatible with
fehler 1.0.0.  (There are some new features in culpa 1.0.2, but they
are fairly minor.)

IMO it would be fine to have *just* the culpa source package in
Debian, and use it to supply a cargo package called "fehler" for those
dependencies that want that.  I have no idea how that would be done
with eg debcargo.  (One .deb that Provides both?)

Filing this as "wishlist" since the current situation is fine for now.

Ian.

[1] https://lib.rs/crates/culpa

-- 
Ian JacksonThese opinions are my own.  

Pronouns: they/he.  If I emailed you from @fyvzl.net or @evade.org.uk,
that is a private address which bypasses my fierce spamfilter.

Bug#1064494: libreoffice-calc: forcing "Wrap text automatically" when moving cells

[Rene Engelhard]

Hi,

Am 23.02.24 um 08:02 schrieb HIGUCHI Daisuke (VDR dai):

Sorry, resending to BTS, not to debian-openoffice.


No problem, that -1 redirects the bug reports to debian-openoffice is a bug.

(Fixed in later versions but those are stuck after the t64 transition.)


Regards,


Rene

Bug#1035880: radeon: radeon driver only partial support of pipelines/ #keypoint isuggest shifting rv530 into the acceptance/features sampling/s applying of r600‎ including the agp to pcie translator

[christianpeterkiss]

Hello,

i suspect itis precisely R300 vs R600 features precisely of the driver s 3d 
part.


if it consists of 2d with its exa emphasis

and glamor part emphasis on 3dfunctions in 2d


and one the api .. ithinkitwas... .. dri ?

#keypoint
thenthe relevant part is the R300 driver part 3d part vs its features likely in 
R600


#keypoint
 isuggest shifting rv530 into the acceptance/features sampling/ applying  of 
r600‎ including the agp to pcie translator chip 




allthebest
Christian KISS




  Original Message  
From: Diederik de Haas
Sent: Freitag, 23. Februar 2024 16:48
To: Christian Kiss; 1035...@bugs.debian.org
Subject: Re: Bug#1035880: radeon: radeon driver only partial support of 
pipelines

Control: reassign -1 src:linux 5.10.178-1

On Wednesday, 10 May 2023 15:41:44 CET Christian Kiss wrote:
> Package: firmware-amd-graphics
> Version: 20210315-3
> 
> kernel.log reports that radeon: 1 quad pipes, 2 z pipes initialized.
> the gpu an rv530 has atleast double to 4 of these each.
> 
> the rudimentary partial support of the hardware features includes oddity
> clock at 85.5Mhz instead 500 / 1100ram
> 
> while the bit width 128seems to becorrect
> 
> additionally to this the realtime kernel scheduling seems to break the gpu/
> non optimised coordination cpu gpu scheduling of cpucycles

This seems to be a kernel issue, reassigning accordingly.

Bug#1064512: python3-samba: Tests should not be packaged

[Michael Tokarev]

Control: severity -1 wishlist

23.02.2024 16:58, Gregor Riepl wrote:

Package: python3-samba
Version: 2:4.19.5+dfsg-1
Severity: normal
X-Debbugs-Cc: onit...@gmail.com

Dear Maintainer,

It looks like the python3-samba package installs some unit tests into
/usr/lib/python3/dist-packages/samba/tests

If this is the case, please exclude them from the package build. There is no
value in installing unit tests along with a runtime library (or, as in this
case, a Python module).


Lacking a way to exclude something from debian/install file,  I don't
have a good way to do that.  The tests should not be merely excluded,
it is part of samba-testsuite package.

samba-testsuite itself is a very questionable package, it has other
issues (like being non-reproducible as it embeds build paths in the
binary and has other problems in this area) and personally I don't see
a reason to ship this package in debian.  If it were removed, this an
other problems would just go away.  But some say it is useful. I dunno :)

/mjt

Bug#1064128:

[Andreas Hasenack]

...and 2.2.4 also fails to build:
https://github.com/savonet/liquidsoap/issues/3752

$ make
: warning: "_FORTIFY_SOURCE" redefined
: note: this is the location of the previous definition
: warning: "_FORTIFY_SOURCE" redefined
: note: this is the location of the previous definition
: warning: "_FORTIFY_SOURCE" redefined
: note: this is the location of the previous definition
: warning: "_FORTIFY_SOURCE" redefined
: note: this is the location of the previous definition
File "src/core/decoder/gstreamer_decoder.ml", line 314, characters 37-51:
314 | (Decoder.test_file ~log ~mimes:mime_types#get
   ^^
Error: This expression has type string list
   but an expression was expected of type string list option
make: *** [Makefile:4: build] Error 1

Bug#1064519: flask-limiter-docs: please make the build reproducible.

[James Addison]

Package: python-flask-limiter-doc
Followup-For: Bug #1064519
Control: forwarded -1 
https://salsa.debian.org/python-team/packages/flask-limiter/-/merge_requests/2

Bug#1035880: radeon: radeon driver only partial support of pipelines

[Diederik de Haas]

Control: reassign  -1 src:linux 5.10.178-1

On Wednesday, 10 May 2023 15:41:44 CET Christian Kiss wrote:
> Package: firmware-amd-graphics
> Version: 20210315-3
> 
> kernel.log reports that radeon: 1 quad pipes, 2 z pipes initialized.
> the gpu an rv530 has atleast double to 4 of these each.
> 
> the rudimentary partial support of the hardware features includes oddity
> clock at 85.5Mhz  instead 500 / 1100ram
> 
> while the bit width 128seems to becorrect
> 
> additionally to this the realtime kernel scheduling seems to break the gpu/
> non optimised coordination cpu gpu scheduling of cpucycles

This seems to be a kernel issue, reassigning accordingly.

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

Bug#1022043: apt-cacher-ng sometimes fails with several concurrent

[Andreas B. Mundt]

Control: tags -1 patch
Control: found -1 apt-cacher-ng/3.7.4-1

Hi Tim,

thanks for the provided patch!  We see the same issue here, so I
included it in a locally built package to give it a try on our
infrastructure.

So far it looks quite promising, no errors up to now .

Best regards,

  Andi

Bug#1064519: flask-limiter-docs: please make the build reproducible.

[James Addison]

Package: python-flask-limiter-doc
Version: 3.5.1-1
Severity: wishlist
Tags: patch

Dear Maintainer,

I'm an occasional volunteer contributor to the Reproducible Builds[1] project,
and recently noticed that python-flask-limiter-docs package failed to build
reproducibly during automated reproducible build testing[2] and also during a
reprotest build[3] on Salsa-CI.

The origin of the non-reproducibility demonstrated in both of those cases is
that a command[4] invoked by the Sphinx-based documentation project markup
produces nondeterministic output.

In particular, the output involves iteration over a set of HTTP methods
associated with a flask (Python web framework) view.  The methods are
placed[5] on the relevant Python object by the werkzeug Python library, and
are stored within an Python set object that is unordered[6].

Because the storage (and therefore retrieval) ordering of the elements in the
set is based on Python's object hashing, it is non-deterministic by default
and varies at build-time.

We can fix this within Debian's packaging by configuring the PYTHONHASHSEED[7]
to use a deterministic value.  The value of zero (0) appears to be most common
within existing debian/rules files, based on codesearch[8].

I'll open a merge request on Salsa to suggest that modification and will link
that to the bug here.

Regards,
James

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

[2] - 
https://tests.reproducible-builds.org/debian/rb-pkg/trixie/amd64/diffoscope-results/flask-limiter.html

[3] - https://salsa.debian.org/python-team/packages/flask-limiter/-/jobs/5335790

[4] - 
https://sources.debian.org/src/flask-limiter/3.5.1-1/doc/source/cli.rst/#L60-L61

[5] - 
https://sources.debian.org/src/python-werkzeug/3.0.1-2/src/werkzeug/routing/rules.py/#L477

[6] - https://docs.python.org/3.11/library/stdtypes.html#set-types-set-frozenset

[7] - https://docs.python.org/3/using/cmdline.html#envvar-PYTHONHASHSEED

[8] - 
https://codesearch.debian.net/search?q=path%3Adebian%2Frules+PYTHONHASHSEED

Bug#1064518: dnsmasq-base: missing depends on passwd, needed by postinst for useradd

[Aurelien Jarno]

Package: dnsmasq-base
Version: 2.90-2
Severity: important
User: debian-ri...@lists.debian.org
Usertags: riscv64
X-Debbugs-Cc: debian-ri...@lists.debian.org

Dear maintainer,

dnsmasq-base's postinst uses the useradd command, however it doesn't
depends on useradd, which is provided by the package passwd. While the
passwd package is required, starting with debootstrap from trixie [1],
it is not guaranteed to be installed on a system or a chroot. In turns
that causes other packages to FTBFS on architectures that have not been
yet released with stable:

| Setting up golang-github-go-playground-universal-translator-dev (0.17.0-2) ...
| Setting up liblxc-common (1:5.0.3-2+b1) ...
| Setting up golang-google-cloud-compute-metadata-dev (0.56.0-3) ...
| Setting up golang-golang-x-tools-dev (1:0.17.0+ds-1) ...
| Setting up dnsmasq-base (2.90-2) ...
| /var/lib/dpkg/info/dnsmasq-base.postinst: 9: useradd: not found
| dpkg: error processing package dnsmasq-base (--configure):
|  installed dnsmasq-base package post-installation script subprocess returned 
error exit status 127
| Setting up man-db (2.12.0-3) ...
| Not building database; man-db/auto-update is not 'true'.
| Setting up golang-github-gorilla-websocket-dev (1.5.1-1) ...

A full build log is available here:
https://buildd.debian.org/status/fetch.php?pkg=incus=riscv64=0.6-1=1708700144=0

Regards
Aurelien

[1] 
https://tracker.debian.org/news/1472578/accepted-debootstrap-10133-source-into-unstable/
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837060