date:20240401


Package: chatty
Version: 0.8.2-1
Severity: serious
User: debian-...@lists.debian.org
Usertag: time-t

After being rebuilt for the time64 transition, chatty depends
on both libpurple0 and libpurple0t64. As a
result it is uninstallable on architectures that are undergoing
the time64 transition (armel, armhf and some debian-ports
archictures).

Processed: re: librnd: FTBFS: ../src/librnd/plugins/hid_lesstif/main.c:261:25: error: implicit declaration of function ‘lesstif_attr_sub_update_hidlib’ [-Werror=implicit-function-declaration]

Processing commands for cont...@bugs.debian.org:

> tags 1066248 +patch
Bug #1066248 [src:librnd] librnd: FTBFS: 
../src/librnd/plugins/hid_lesstif/main.c:261:25: error: implicit declaration of 
function ‘lesstif_attr_sub_update_hidlib’ 
[-Werror=implicit-function-declaration]
Added tag(s) patch.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1066248: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066248
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1066248: librnd: FTBFS: ../src/librnd/plugins/hid_lesstif/main.c:261:25: error: implicit declaration of function ‘lesstif_attr_sub_update_hidlib’ [-Werror=implicit-function-declaration]


tags 1066248 +patch
thanks

The functions in question are defined in 
src/librnd/plugins/hid_lesstif/dialogs.c

and used in src/librnd/plugins/hid_lesstif/main.c

My first attempt at fixing the issue was to declare the functions in 
dialogs.h

and include dialogs.h in main.c, however doing so caused errors with
conflicting type definitions, so I just defined them directly in main.c 
instead.


while working on this issue I discovered that the clean target was not
cleaning up properly, so I fixed that too.

A debdiff is attatched.

Review and upload would be appreciated since this blocks the time_t
transition
diff -Nru librnd-4.1.1/debian/changelog librnd-4.1.1/debian/changelog
--- librnd-4.1.1/debian/changelog   2024-02-28 17:20:34.0 +
+++ librnd-4.1.1/debian/changelog   2024-04-02 04:43:46.0 +
@@ -1,3 +1,11 @@
+librnd (4.1.1-1.2) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Add missing function declarations.
+  * Fix clean target.
+
+ -- Peter Michael Green   Tue, 02 Apr 2024 04:43:46 +
+
 librnd (4.1.1-1.1) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -Nru librnd-4.1.1/debian/patches/add-missing-function-declaration.patch 
librnd-4.1.1/debian/patches/add-missing-function-declaration.patch
--- librnd-4.1.1/debian/patches/add-missing-function-declaration.patch  
1970-01-01 00:00:00.0 +
+++ librnd-4.1.1/debian/patches/add-missing-function-declaration.patch  
2024-04-02 04:42:54.0 +
@@ -0,0 +1,14 @@
+Index: librnd-4.1.1/src/librnd/plugins/hid_lesstif/main.c
+===
+--- librnd-4.1.1.orig/src/librnd/plugins/hid_lesstif/main.c
 librnd-4.1.1/src/librnd/plugins/hid_lesstif/main.c
+@@ -51,6 +51,9 @@
+ 
+ #include 
+ 
++void lesstif_attr_dlg_free_all(void);
++void lesstif_attr_sub_update_hidlib(void *hid_ctx, rnd_design_t *new_dsg);
++
+ const char *lesstif_cookie = "lesstif HID";
+ 
+ rnd_design_t *ltf_hidlib;
diff -Nru librnd-4.1.1/debian/patches/series librnd-4.1.1/debian/patches/series
--- librnd-4.1.1/debian/patches/series  2024-01-13 09:12:54.0 +
+++ librnd-4.1.1/debian/patches/series  2024-04-02 04:21:58.0 +
@@ -0,0 +1 @@
+add-missing-function-declaration.patch
diff -Nru librnd-4.1.1/debian/rules librnd-4.1.1/debian/rules
--- librnd-4.1.1/debian/rules   2024-01-13 09:12:54.0 +
+++ librnd-4.1.1/debian/rules   2024-04-02 04:43:46.0 +
@@ -21,6 +21,10 @@
 override_dh_auto_clean:
# only try to run dh_auto_clean if configure has been run
test -f Makefile.conf && dh_auto_clean || true
+   find . -name *.o -delete
+   find . -name *.so.* -delete
+   rm -f scconfig/aru
+   rm -f doc/conf/tree/editor_global_grid.html 
doc/conf/tree/editor_local_grid.html src/librnd/plugins/lib_hid_gl/draw_INIT.h 
src/librnd/poly/polyconf.h src/librnd/polybool/polyconf.h
 
 override_dh_auto_configure:
./configure \

Bug#1068189: debhelper: --link-doc checking for known packages makes linux-signed build FTBFS

2024-04-01 Thread Salvatore Bonaccorso

Control: reassign -1 src:linux 6.7.9-2

Hi Niels,

On Mon, Apr 01, 2024 at 05:19:43PM +0200, Niels Thykier wrote:
> Salvatore Bonaccorso:
> > Source: debhelper
> > Version: 13.15
> > Severity: serious
> > Tags: ftbfs
> > Justification: Regression for other package builds, FTBFS
> > X-Debbugs-Cc: car...@debian.org,debian-ker...@lists.debian.org
> > Control: affects -1 + 
> > src:linux,src:linux-signed-amd64,src:linux-signed-arm64
> > 
> > Hi Niels,
> > 
> > Not fully investigated, but starting to fill a bugreport. I noticed
> > that the src:linux pipeline on salsa started to fail for the
> > jobs in th build-signed stage (in the build-signed job).
> > 
> > https://salsa.debian.org/carnil/linux/-/jobs/5527774
> > 
> > (and for saving the output):
> > 
> > [...]
> > 
> > (attached as well the raw log)
> > 
> > I'm not 100% sure yet, this might be a problem in our packaging in
> > which case we can re-eassign. But it only got triggered with the
> > change recently in debhelper:
> > 
> > https://salsa.debian.org/debian/debhelper/-/commit/dec5cfad00e2abd9ee3594f90c93f3fa42bb73ff
> > 
> > Regards,
> > Salvatore
> 
> Hi Salvatore
> 
> It was a suggestion raised (I think on IRC) to have debhelper explicitly
> check these parameters, because a lot of t64 breakage was "unnoticed" by
> debhelper. That is, when people forgot to update --link-doc parameters
> (etc.).
> 
> The code for `--link-doc` uses `${binary:Version}` for the dependency, so
> the package should really be from the same source[1]. In my view, it was
> never a case that was expected to work between source packages.
> 
> I think `linux` with `linux-signed` is doing something really special here
> (especially considering it has worked so far), and I think the question is
> whether `linux`/`linux-signed` should get a special-case or concluding that
> the `--link-doc` is not suitable for the `linux`/`linux-signed` case.
> 
> I would like to hear your case for what makes `--link-doc` sensible for the
> `linux-signed` case. I know of `linux-signed`, but I have no idea what you
> are dealing with in practice, so it is hard for me to make a judgement call
> on this (other than my biased gut feeling of wanting to minimize
> special-cases).

Thanks for your very quick reply, this is much appreicated.

I understand the reason and src:linux should not get really to be
exceptionally handled. So for now I will re-assign it to src:linux
and we can search for a solution in our package.

Thanks a lot for your work on debhelper!

Regards,
Salvatore

Processed: Re: Bug#1068189: debhelper: --link-doc checking for known packages makes linux-signed build FTBFS

Processing control commands:

> reassign -1 src:linux 6.7.9-2
Bug #1068189 [src:debhelper] debhelper: --link-doc checking for known packages 
makes linux-signed build FTBFS
Bug reassigned from package 'src:debhelper' to 'src:linux'.
No longer marked as found in versions debhelper/13.15.
Ignoring request to alter fixed versions of bug #1068189 to the same values 
previously set
Bug #1068189 [src:linux] debhelper: --link-doc checking for known packages 
makes linux-signed build FTBFS
Marked as found in versions linux/6.7.9-2.

-- 
1068189: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068189
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1064598: [3dprinter-general] Bug#1064598: yagv: crashes with "module 'pyglet.graphics' has no attribute 'vertex_list'"

2024-04-01 Thread Chow Loong Jin

On Thu, Mar 28, 2024 at 09:37:18AM +0100, Petter Reinholdtsen wrote:
> [Gregor Riepl 2024-02-26]
> > Unfortunately, it appears that upstream project is dead.
> > The last commit was in 2017, and any requests by @pere on their bug tracker
> > fell on deaf ears: [2]
> > 
> > It's regrettable, but I don't think yagv can be kept with the current
> > situation.
> 
> I agree.  Someone need to take over yagl upstream development for it to
> be sustainable in Debian.  Time to file for removal?
> 
> See https://bugs.debian.org/877377 > for my tries to find a new
> upstream.

Agreed. It's been a while and there are superior alternatives to yagv
now.

-- 
Kind regards,
Loong Jin


signature.asc
Description: PGP signature

Bug#1066602: marked as done (ukui-biometric-auth: FTBFS: pam_biometric.c:333:8: error: implicit declaration of function ‘enable_biometric_auth_double’; did you mean ‘enable_biometric_authentication’?

Your message dated Tue, 02 Apr 2024 04:05:29 +
with message-id 
and subject line Bug#1066602: fixed in ukui-biometric-auth 1.2.2.2-1
has caused the Debian Bug report #1066602,
regarding ukui-biometric-auth: FTBFS: pam_biometric.c:333:8: error: implicit 
declaration of function ‘enable_biometric_auth_double’; did you mean 
‘enable_biometric_authentication’? [-Werror=implicit-function-declaration]
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1066602: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066602
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ukui-biometric-auth
Version: 1.2.2.1-2
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240313 ftbfs-trixie ftbfs-impfuncdef

Hi,

During a rebuild of all packages in sid, your package failed to build
on amd64.

This is most likely caused by a change in dpkg 1.22.6, that enabled
-Werror=implicit-function-declaration. For more information, see
https://wiki.debian.org/qa.debian.org/FTBFS#A2024-03-13_-Werror.3Dimplicit-function-declaration

Relevant part (hopefully):
> make[3]: Entering directory '/<>/obj-x86_64-linux-gnu'
> Updating '/<>/obj-x86_64-linux-gnu/polkit-agent/ru.qm'...
> Generated 17 translation(s) (17 finished and 0 unfinished)
> Ignored 3 untranslated source text(s)
> cd /<>/obj-x86_64-linux-gnu/polkit-agent && 
> /usr/lib/qt5/bin/lrelease /<>/polkit-agent/i18n_ts/zh_CN.ts -qm 
> /<>/obj-x86_64-linux-gnu/polkit-agent/zh_CN.qm
> Updating '/<>/obj-x86_64-linux-gnu/bioauth-bin/pt.qm'...
> Generated 18 translation(s) (18 finished and 0 unfinished)
> Ignored 1 untranslated source text(s)
> Updating '/<>/obj-x86_64-linux-gnu/polkit-agent/tr.qm'...
> Generated 17 translation(s) (16 finished and 1 unfinished)
> Ignored 3 untranslated source text(s)
> Updating '/<>/obj-x86_64-linux-gnu/bioauth-bin/fr.qm'...
> Generated 18 translation(s) (18 finished and 0 unfinished)
> Ignored 1 untranslated source text(s)
> Updating '/<>/obj-x86_64-linux-gnu/polkit-agent/zh_CN.qm'...
> Generated 26 translation(s) (26 finished and 0 unfinished)
> make[3]: Leaving directory '/<>/obj-x86_64-linux-gnu'
> [ 33%] Generating include/moc_bioauth.cpp
> [ 34%] Generating ru.qm
> cd /<>/obj-x86_64-linux-gnu/bioauth-bin && 
> /usr/lib/qt5/bin/lrelease /<>/bioauth-bin/i18n_ts/ru.ts -qm 
> /<>/obj-x86_64-linux-gnu/bioauth-bin/ru.qm
> cd /<>/obj-x86_64-linux-gnu/bioauth/include && 
> /usr/lib/qt5/bin/moc 
> @/<>/obj-x86_64-linux-gnu/bioauth/include/moc_bioauth.cpp_parameters
> [ 36%] Generating include/moc_biodevices.cpp
> cd /<>/obj-x86_64-linux-gnu/bioauth/include && 
> /usr/lib/qt5/bin/moc 
> @/<>/obj-x86_64-linux-gnu/bioauth/include/moc_biodevices.cpp_parameters
> [ 38%] Generating zh_CN.qm
> Updating '/<>/obj-x86_64-linux-gnu/bioauth-bin/ru.qm'...
> cd /<>/obj-x86_64-linux-gnu/bioauth-bin && 
> /usr/lib/qt5/bin/lrelease /<>/bioauth-bin/i18n_ts/zh_CN.ts -qm 
> /<>/obj-x86_64-linux-gnu/bioauth-bin/zh_CN.qm
> Generated 18 translation(s) (18 finished and 0 unfinished)
> Ignored 1 untranslated source text(s)
> [ 39%] Generating tr.qm
> cd /<>/obj-x86_64-linux-gnu && /usr/bin/cmake -E cmake_depends 
> "Unix Makefiles" /<> /<>/bioauth 
> /<>/obj-x86_64-linux-gnu 
> /<>/obj-x86_64-linux-gnu/bioauth 
> /<>/obj-x86_64-linux-gnu/bioauth/CMakeFiles/BioAuth.dir/DependInfo.cmake
>  "--color="
> cd /<>/obj-x86_64-linux-gnu/bioauth-bin && 
> /usr/lib/qt5/bin/lrelease /<>/bioauth-bin/i18n_ts/tr.ts -qm 
> /<>/obj-x86_64-linux-gnu/bioauth-bin/tr.qm
> Updating '/<>/obj-x86_64-linux-gnu/bioauth-bin/zh_CN.qm'...
> Generated 17 translation(s) (17 finished and 0 unfinished)
> Ignored 2 untranslated source text(s)
> [ 39%] Built target polkit_i18n
> Updating '/<>/obj-x86_64-linux-gnu/bioauth-bin/tr.qm'...
> Generated 18 translation(s) (16 finished and 2 unfinished)
> Ignored 1 untranslated source text(s)
> make[3]: Leaving directory '/<>/obj-x86_64-linux-gnu'
> /<>/pam-biometric/pam_biometric.c: In function 
> ‘biometric_auth_embeded’:
> /<>/pam-biometric/pam_biometric.c:333:8: error: implicit 
> declaration of function ‘enable_biometric_auth_double’; did you mean 
> ‘enable_biometric_authentication’? [-Werror=implicit-function-declaration]
>   333 | if(enable_biometric_auth_double())
>   |^~~~
>   |enable_biometric_authentication
> make[3]: Leaving directory '/<>/obj-x86_64-linux-gnu'
> make  -f bioauth/CMakeFiles/BioAuth.dir/build.make 
> bioauth/CMakeFiles/BioAuth.dir/build
> make[3]: Entering directory

Processed: re: bitlbee-facebook: redundant dependency on libglib2.0-0

Processing commands for cont...@bugs.debian.org:

> severity 1067391 serious
Bug #1067391 [bitlbee-facebook] bitlbee-facebook: redundant dependency on 
libglib2.0-0
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1067391: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067391
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: Re: Bug#1068204: pdl: FTBFS on i386: Failed 1/45 test programs. 2/2262 subtests failed.

Processing control commands:

> tags -1 upstream
Bug #1068204 [src:pdl] pdl: FTBFS on i386: Failed 1/45 test programs. 2/2262 
subtests failed.
Added tag(s) upstream.
> forwarded -1 https://github.com/PDLPorters/pdl/issues/469
Bug #1068204 [src:pdl] pdl: FTBFS on i386: Failed 1/45 test programs. 2/2262 
subtests failed.
Set Bug forwarded-to-address to 'https://github.com/PDLPorters/pdl/issues/469'.

-- 
1068204: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068204
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1068204: pdl: FTBFS on i386: Failed 1/45 test programs. 2/2262 subtests failed.

2024-04-01 Thread Sebastiaan Couwenberg


Control: tags -1 upstream
Control: forwarded -1 https://github.com/PDLPorters/pdl/issues/469

On 4/1/24 10:47 PM, Sebastian Ramacher wrote:

https://buildd.debian.org/status/fetch.php?pkg=pdl=i386=1%3A2.086-1=1712002199=0


Salsa CI also caught that which triggered the upstream issue.

Kind Regards,

Bas

--
 GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146  50D1 6750 F10A E88D 4AF1

Bug#1068217: atomes, dependencies unsatisfiable on 32-bit non-i386 architectures.


Package: atomes
Version: 1.1.12+repack-2
Severity: grave
User: debian-...@lists.debian.org
Usertag: time-t

After being rebuilt for the time64 transition, atomes depends
on both libgtk-3-0t64 and .libgtk-3-0t64 As a
result it is uninstallable on architectures that are undergoing
the time64 transition (armel, armhf and some debian-ports
archictures).

This applies to both versions 1.1.12+repack-2 and 1.1.14-1

Bug#1066392: gtk2-engines-murrine: FTBFS: ./src/murrine_style.c:133:30: error: implicit declaration of function ‘murrine_widget_is_ltr’; did you mean ‘murrine_widget_is_rgba’? [-Werror=implicit-functi


tags 1066392 +patch
thanks

I've whipped up a patch that adds the missing function declarations to
the headers.

Review and upload would be appreciated as this is needed for the
time64 transition (and is a key package, so can't simply be autoremoved).
diff -Nru gtk2-engines-murrine-0.98.2/debian/changelog 
gtk2-engines-murrine-0.98.2/debian/changelog
--- gtk2-engines-murrine-0.98.2/debian/changelog2019-11-18 
08:32:18.0 +
+++ gtk2-engines-murrine-0.98.2/debian/changelog2024-04-02 
02:51:30.0 +
@@ -1,3 +1,11 @@
+gtk2-engines-murrine (0.98.2-3.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Add declarations for functions to fix implicit function declaration
+errors.
+
+ -- Peter Michael Green   Tue, 02 Apr 2024 02:51:30 +
+
 gtk2-engines-murrine (0.98.2-3) unstable; urgency=medium
 
   [ Mike Gabriel ]
diff -Nru 
gtk2-engines-murrine-0.98.2/debian/patches/add-missing-function-declarations.patch
 
gtk2-engines-murrine-0.98.2/debian/patches/add-missing-function-declarations.patch
--- 
gtk2-engines-murrine-0.98.2/debian/patches/add-missing-function-declarations.patch
  1970-01-01 00:00:00.0 +
+++ 
gtk2-engines-murrine-0.98.2/debian/patches/add-missing-function-declarations.patch
  2024-04-02 02:51:30.0 +
@@ -0,0 +1,31 @@
+Description: Add declarations for functions to fix implicit function 
declaration errors.
+Author: Peter Michael Green 
+
+--- gtk2-engines-murrine-0.98.2.orig/src/murrine_rc_style.h
 gtk2-engines-murrine-0.98.2/src/murrine_rc_style.h
+@@ -155,4 +155,6 @@ struct _MurrineRcStyleClass
+ 
+ GType murrine_rc_style_get_type   (void);
+ 
++void murrine_rc_style_register_types (GTypeModule *module);
++
+ #endif /* MURRINE_RC_STYLE_H */
+--- gtk2-engines-murrine-0.98.2.orig/src/murrine_style.h
 gtk2-engines-murrine-0.98.2/src/murrine_style.h
+@@ -102,5 +102,6 @@ struct _MurrineStyleClass
+ };
+ 
+ GType murrine_style_get_type (void);
++void murrine_style_register_types (GTypeModule *module);
+ 
+ #endif /* MURRINE_STYLE_H */
+--- gtk2-engines-murrine-0.98.2.orig/src/support.h
 gtk2-engines-murrine-0.98.2/src/support.h
+@@ -149,4 +149,7 @@ G_GNUC_INTERNAL void murrine_get_noteboo
+ gboolean  *start,
+ gboolean  *end);
+ 
++gboolean murrine_object_is_a (const GObject * object, const gchar * 
type_name);
++gboolean murrine_widget_is_ltr (GtkWidget *widget);
++
+ #endif /* SUPPORT_H */
diff -Nru gtk2-engines-murrine-0.98.2/debian/patches/series 
gtk2-engines-murrine-0.98.2/debian/patches/series
--- gtk2-engines-murrine-0.98.2/debian/patches/series   2019-11-12 
09:31:57.0 +
+++ gtk2-engines-murrine-0.98.2/debian/patches/series   2024-04-02 
02:51:30.0 +
@@ -1,2 +1,3 @@
 02_fix-linking-lm.patch
 pango_cairo_update_layout.patch
+add-missing-function-declarations.patch

Processed: re: gtk2-engines-murrine: FTBFS: ./src/murrine_style.c:133:30: error: implicit declaration of function ‘murrine_widget_is_ltr’; did you mean ‘murrine_widget_is_rgba’? [-Werror=implicit-func

Processing commands for cont...@bugs.debian.org:

> tags 1066392 +patch
Bug #1066392 [src:gtk2-engines-murrine] gtk2-engines-murrine: FTBFS: 
./src/murrine_style.c:133:30: error: implicit declaration of function 
‘murrine_widget_is_ltr’; did you mean ‘murrine_widget_is_rgba’? 
[-Werror=implicit-function-declaration]
Added tag(s) patch.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1066392: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066392
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1068216: aqemu, dependencies unsatisfiable on 32-bit non-i386 architectures.


Package: aqemu
Version: 0.9.2-3
Severity: serious
User: debian-...@lists.debian.org
Usertag: time-t

After being rebuilt for the time64 transition, aqemu still
depends on libqt5dbus5. As a result it is uninstallable on
architectures that are undergoing the time64 transition
(armel, armhf and some debian-ports archictures).

Bug#1052943: marked as done (closql-el: FTBFS: make[2]: *** No rule to make target '/usr/share/emacs/site-lisp/elpa-src/emacsql-3.1.1'. Stop.)

Your message dated Tue, 02 Apr 2024 01:58:52 +0200
with message-id <8734s4eitf.fsf@X570GP>
and subject line closql-el: FTBFS
has caused the Debian Bug report #1052943,
regarding closql-el: FTBFS: make[2]: *** No rule to make target 
'/usr/share/emacs/site-lisp/elpa-src/emacsql-3.1.1'.  Stop.
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1052943: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052943
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: closql-el
Version: 1.2.1-3
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230925 ftbfs-trixie

Hi,

During a rebuild of all packages in sid, your package failed to build
on amd64.


Relevant part (hopefully):
>  debian/rules binary
> dh binary --with elpa
>dh_update_autotools_config
>dh_autoreconf
>dh_auto_configure
>debian/rules override_dh_auto_build
> make[1]: Entering directory '/<>'
> make LOAD_PATH=-L /usr/share/emacs/site-lisp/elpa-src/emacsql-3.1.1 -L 
> /usr/share/emacs/site-lisp/elpa-src/emacsql-sqlite-3.1.1
> make[2]: Entering directory '/<>'
> make[2]: *** No rule to make target 
> '/usr/share/emacs/site-lisp/elpa-src/emacsql-3.1.1'.  Stop.
> make[2]: Leaving directory '/<>'
> make[1]: *** [debian/rules:13: override_dh_auto_build] Error 2


The full build log is available from:
http://qa-logs.debian.net/2023/09/25/closql-el_1.2.1-3_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20230925;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20230925=lu...@debian.org=1=1=1=1#results

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

If you reassign this bug to another package, please mark it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---


The upload of 1.2.1+git20231217.1.1b2ee60-1 should solve the 
issue.


Best,

Aymeric Agon-Rambosson--- End Message ---

Bug#1068213: gnome-remote-desktop: hard-coded dependency on pre-t64 library

Source: gnome-remote-desktop
Version: 44.2-7
Severity: serious
X-Debbugs-Cc: sramac...@debian.org

gnome-remote-desktop builds a binary pckage with a hard-coded dependy on
libmutter-12-0. This library was renamed as part of the time_t 64
transition. Please update the dependencies accordingly.

Cheers
-- 
Sebastian Ramacher

Bug#1066227: marked as done (armci-mpi: FTBFS: tests/contrib/non-blocking/overlap.c:660:17: error: implicit declaration of function ‘time’ [-Werror=implicit-function-declaration])

Your message dated Mon, 01 Apr 2024 23:04:30 +
with message-id 
and subject line Bug#1066227: fixed in armci-mpi 0.3.1~beta-7.1
has caused the Debian Bug report #1066227,
regarding armci-mpi: FTBFS: tests/contrib/non-blocking/overlap.c:660:17: error: 
implicit declaration of function ‘time’ [-Werror=implicit-function-declaration]
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1066227: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066227
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: armci-mpi
Version: 0.3.1~beta-7
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240313 ftbfs-trixie ftbfs-impfuncdef

Hi,

During a rebuild of all packages in sid, your package failed to build
on amd64.

This is most likely caused by a change in dpkg 1.22.6, that enabled
-Werror=implicit-function-declaration. For more information, see
https://wiki.debian.org/qa.debian.org/FTBFS#A2024-03-13_-Werror.3Dimplicit-function-declaration

Relevant part (hopefully):
> /bin/bash ./libtool  --tag=CC   --mode=link mpicc.mpich  -g -O2 
> -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. 
> -fstack-protector-strong -fstack-clash-protection -Wformat 
> -Werror=format-security -fcf-protection-Wl,-z,relro -o 
> tests/contrib/transp1D/transp1D-c tests/contrib/transp1D/transp1D-c.o 
> libarmci-mpich.la 
> libtool: link: mpicc.mpich -g -O2 -Werror=implicit-function-declaration 
> "-ffile-prefix-map=/<>=." -fstack-protector-strong 
> -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection 
> -Wl,-z -Wl,relro -o tests/contrib/transp1D/transp1D-c 
> tests/contrib/transp1D/transp1D-c.o  ./.libs/libarmci-mpich.a
> mpicc.mpich -DHAVE_CONFIG_H -I. -I./src  -I./src -Wdate-time 
> -D_FORTIFY_SOURCE=2  -g -O2 -Werror=implicit-function-declaration 
> -ffile-prefix-map=/<>=. -fstack-protector-strong 
> -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection   
> -c -o tests/contrib/non-blocking/overlap.o 
> tests/contrib/non-blocking/overlap.c
> tests/contrib/non-blocking/overlap.c: In function ‘main’:
> tests/contrib/non-blocking/overlap.c:660:17: error: implicit declaration of 
> function ‘time’ [-Werror=implicit-function-declaration]
>   660 | time_seed = time(NULL);
>   | ^~~~
> tests/contrib/non-blocking/overlap.c:45:1: note: ‘time’ is defined in header 
> ‘’; did you forget to ‘#include ’?
>44 | #include 
>   +++ |+#include 
>45 | 
> cc1: some warnings being treated as errors
> make[3]: *** [Makefile:1778: tests/contrib/non-blocking/overlap.o] Error 1


The full build log is available from:
http://qa-logs.debian.net/2024/03/13/armci-mpi_0.3.1~beta-7_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240313;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20240313=lu...@debian.org=1=1=1=1#results

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

If you reassign this bug to another package, please mark it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Source: armci-mpi
Source-Version: 0.3.1~beta-7.1
Done: Samuel Thibault 

We believe that the bug you reported is fixed in the latest version of
armci-mpi, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1066...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Samuel Thibault  (supplier of updated armci-mpi package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 30 Mar 2024 23:17:18 +0100
Source: armci-mpi
Architecture: source
Version: 0.3.1~beta-7.1
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Samuel Thibault 
Closes: 1066227
Changes:
 armci-mpi

Bug#1067055: openmpi: error: implicit declaration of function 'OPAL_THREAD_ADD_FETCH64'

On 2024-04-01 12:05:30 +0100, Alastair McKinstry wrote:
> 
> On 23/03/2024 01:58, Thorsten Glaser wrote:
> > Andrey Rakhmatullin dixit:
> > 
> > > OPAL_THREAD_ADD_FETCH64 is defined under #if OPAL_HAVE_ATOMIC_MATH_64
> > > And I assume this arch doesn't have 64-bit atomics.
> > No native ones, yes.
> > 
> > I *think* either libatomic or libatomic_ops(?) make them
> > available, but very slowly, using a syscall to guarantee
> > atomicity (those systems are normally uniprocessor) on
> > m68k.
> > 
> > If possible, avoiding them would be preferrable. (For
> > example, in some cases, like reading a 64-bit timestamp,
> > if the writing direction is known and stable, reading
> > twice then comparing is a possible alternative at least
> > for some architectures (e.g. I know BSD code for sparc
> > does it that way).
> > 
> > I guess you’ll have to ask the porters of 32-bit arches
> > with no native 64-bit atomics for details.
> > 
> > Though I had thought GCC’s builtin atomics use the
> > aforementioned kernel-based workaround from that library
> > these days?
> 
> There is a transition to openmpi-5 / mpi-defaults which is stalled by the
> t64 transition.
> 
> It drops 32-bit support from OpenMPI.
> 
> Because of this, I don't think the solution is to  port 32-bit atomics for
> armel/armhf, as it will be removed in a few weeks/months.
> 
> While we didn't want the transitions to be done simultaneously, it might be
> the best answer.
> 
> 
> What does the release team think?

Adding another transition on top will just delay the time_t transition
even more. So if we can avoid that, I'd prefer to not do this transition
now. Unfortunately, uploads such as the one of pmix that no dropped
support for 32 bit architectures (#1068211) are not really helpful.

Also, #1064810 has no information on test builds with the new
mpi-defaults on a 32 bit architecture. So has this transition been
tested?

Cheers
-- 
Sebastian Ramacher

Bug#1068211: pmix: FTBFS on 32 bit architectures: configure: WARNING: PMIx does not support 32 bit builds.

Source: pmix
Version: 5.0.2-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: sramac...@debian.org

https://buildd.debian.org/status/fetch.php?pkg=pmix=armel=5.0.2-1=1711406265=0

checking size of _Bool... 1
checking size of short... 2
checking size of int... 4
checking size of long... 4
checking size of void *... 4
configure: WARNING: PMIx does not support 32 bit builds.
configure: error: Cannot continue
-- 
Sebastian Ramacher

Bug#1068210: fricas: FTBFS on arm{el,hf}: /<>/src/lisp/fricas-lisp.c:1750:10: error: implicit declaration of function ‘sock_get_string_buf’; did you mean ‘sock_send_string_len’? [-Werror=

Source: fricas
Version: 1.3.10-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: sramac...@debian.org

https://buildd.debian.org/status/fetch.php?pkg=fricas=armhf=1.3.10-1%2Bb2=1711729211=0

/<>/src/lisp/fricas-lisp.c: In function 
‘sock_get_string_buf_wrapper’:
/<>/src/lisp/fricas-lisp.c:1750:10: error: implicit declaration of 
function ‘sock_get_string_buf’; did you mean ‘sock_send_string_len’? 
[-Werror=implicit-function-declaration]
 1750 |   return sock_get_string_buf(i, x->st.st_self, j); }
  |  ^~~
  |  sock_send_string_len
cc1: some warnings being treated as errors

Correctable error: 
Fast links are on: do (si::use-fast-links nil) for debugging
Signalled by COMPILE-FILE.
If continued: Continues anyway.SIMPLE-ERROR: (SYSTEM "/usr/bin/gcc  -c -g 
-Werror=implicit-function-declaration 
-ffile-prefix-map=/<>/gcl-2.6.14=. -fstack-protector-strong 
-fstack-clash-protection -Wformat -Werror=format-security -fsigned-char -pipe 
-fcommon -fno-builtin-malloc -fno-builtin-free -fno-PIE -fno-pie -fno-PIC 
-fno-pic -Wall -Wno-empty-body -Wno-unused-but-set-variable 
-fdollars-in-identifiers -g -I/usr/include/tirpc -D_TIME_BITS=64 
-D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 
-D_TIME_BITS=64 -Wdate-time -D_FORTIFY_SOURCE=2  
-I/usr/lib/gcl-2.6.14/unixport/../h  -O2  -c 
/<>/src/lisp/fricas-lisp.c -o 
/<>/src/lisp/fricas-lisp.o ") returned a non-zero value 1 0.

Broken at COMPILE-FILE.  Type :H for Help.
1 (continue) Continues anyway. 
2  Return to top level. 
BOOTTRAN>>
The compiler was called recursively.
Cannot compile primitives.lisp.
NIL
NIL
NIL
BOOTTRAN>>make[3]: *** [Makefile:249: do_it.gcl] Error 255

Cheers
-- 
Sebastian Ramacher

Bug#1054820: marked as done (xcffib: FTBFS: make[2]: *** [Makefile:16: xcffib] Error 1)

Your message dated Mon, 01 Apr 2024 22:07:17 +
with message-id 
and subject line Bug#1054820: fixed in xcffib 1.5.0-1
has caused the Debian Bug report #1054820,
regarding xcffib: FTBFS: make[2]: *** [Makefile:16: xcffib] Error 1
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1054820: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054820
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: xcffib
Version: 0.11.1-4
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20231027 ftbfs-trixie

Hi,

During a rebuild of all packages in sid, your package failed to build
on amd64.


Relevant part (hopefully):
> make[2]: Entering directory '/<>'
> cabal --config-file=/dev/null new-run -j8 exe:xcffibgen -- --input 
> //usr/share/xcb --output ./xcffib
> Warning: No remote package servers have been specified. Usually you would have
> one specified in the config file.
> Resolving dependencies...
> Build profile: -w ghc-9.4.7 -O1
> In order, the following will be built (use -v for more details):
>  - xcffib-0.11.1 (lib) (first run)
>  - xcffib-0.11.1 (exe:xcffibgen) (first run)
> Configuring library for xcffib-0.11.1..
> Preprocessing library for xcffib-0.11.1..
> Building library for xcffib-0.11.1..
> [1 of 2] Compiling Data.XCB.Python.PyHelpers ( 
> generator/Data/XCB/Python/PyHelpers.hs, 
> /<>/dist-newstyle/build/x86_64-linux/ghc-9.4.7/xcffib-0.11.1/build/Data/XCB/Python/PyHelpers.o,
>  
> /<>/dist-newstyle/build/x86_64-linux/ghc-9.4.7/xcffib-0.11.1/build/Data/XCB/Python/PyHelpers.dyn_o
>  )
> [2 of 2] Compiling Data.XCB.Python.Parse ( 
> generator/Data/XCB/Python/Parse.hs, 
> /<>/dist-newstyle/build/x86_64-linux/ghc-9.4.7/xcffib-0.11.1/build/Data/XCB/Python/Parse.o,
>  
> /<>/dist-newstyle/build/x86_64-linux/ghc-9.4.7/xcffib-0.11.1/build/Data/XCB/Python/Parse.dyn_o
>  )
> 
> generator/Data/XCB/Python/Parse.hs:291:29: error:
> • The constructor ‘Pad’ should have 2 arguments, but has been given 1
> • In the pattern: Pad i
>   In an equation for ‘structElemToPyUnpack’:
>   structElemToPyUnpack _ _ _ (Pad i) = Left (Nothing, mkPad i)
> |
> 291 | structElemToPyUnpack _ _ _ (Pad i) = Left (Nothing, mkPad i)
> | ^
> 
> generator/Data/XCB/Python/Parse.hs:355:27: error:
> • The constructor ‘Pad’ should have 2 arguments, but has been given 1
> • In the pattern: Pad i
>   In an equation for ‘structElemToPyPack’:
>   structElemToPyPack _ _ _ (Pad i) = Left (Nothing, mkPad i)
> |
> 355 | structElemToPyPack _ _ _ (Pad i) = Left (Nothing, mkPad i)
> |   ^
> 
> generator/Data/XCB/Python/Parse.hs:643:16: error:
> • The constructor ‘Pad’ should have 2 arguments, but has been given 1
> • In the pattern: Pad _
>   In an equation for ‘getName’: getName (Pad _) = Nothing
>   In an equation for ‘mkSyntheticMethod’:
>   mkSyntheticMethod membs
> = do let names = ...
>  
>  if null names then [] else [...]
> where
> getName :: GenStructElem Type -> Maybe String
> getName (Pad _) = Nothing
> getName (X.List n _ _ _) = Just n
> getName (SField n _ _ _) = Just n
> getName (ExprField n _ _) = Just n
> getName (ValueParam _ n _ _) = Just n
> getName (Switch n _ _ _) = Just n
> getName (Doc _ _ _) = Nothing
> getName (Fd n) = Just n
> getName (Length _ _) = Nothing
> assign :: String -> Statement ()
> assign n = mkAssign (mkDot "self" n) $ mkName n
> |
> 643 |   getName (Pad _) = Nothing
> |^
> 
> generator/Data/XCB/Python/Parse.hs:681:19: error:
> • The constructor ‘XEvent’ should have 6 arguments, but has been given 5
> • In the pattern: XEvent name opcode _ membs noSequence
>   In an equation for ‘processXDecl’:
>   processXDecl ext (XEvent name opcode _ membs noSequence)
> = do m <- get
>  let cname = ...
>  
>  return
>$ Declaration
>[mkXClass cname "xcffib.Event" statements (pack : 
> synthetic), ]
> |
> 681 | processXDecl ext (XEvent name opcode _ membs noSequence) = do
> |   ^
> Error: cabal: Failed to build xcffib-0.11.1 (which is required by
>

Processed: notfound 1068166 in 6.07-1

Processing commands for cont...@bugs.debian.org:

> notfound 1068166 6.07-1
Bug #1068166 [manpages-dev] manpages-dev: Fails to upgrade due to file conflict
Bug #1068167 [manpages-dev] manpages-dev: Update to 6.7-1 fails
There is no source info for the package 'manpages-dev' at version '6.07-1' with 
architecture ''
Unable to make a source version for version '6.07-1'
No longer marked as found in versions 6.07-1.
No longer marked as found in versions 6.07-1.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1068166: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068166
1068167: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068167
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1068209: libgtkada: FTBFS on all: dh_ada_library: error: debian/tmp/usr/lib/x86_64-linux-gnu/ada/adalib/gtkada/*.ali are missing

Source: libgtkada
Version: 24.0.0-2
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: sramac...@debian.org

mkdir -p debian/tmp/usr/share/doc/gtkada/gtkada_ug
cp --reflink=auto -aftdebian/tmp/usr/share/doc/gtkada/gtkada_ug \
  docs/gtkada_ug/_build/html/* \
  docs/gtkada_ug/_build/latex/GtkAda.pdf
make[1]: Leaving directory '/<>'
   dh_install -i
   dh_installdocs -i
   dh_sphinxdoc -i
   dh_installchangelogs -i
   dh_installexamples -i
   dh_installman -i
   dh_ada_library -i
dh_ada_library: error: 
debian/tmp/usr/lib/x86_64-linux-gnu/ada/adalib/gtkada/*.ali are missing

Cheers
-- 
Sebastian Ramacher

Bug#1067364: Probably bug is elsewhere

2024-04-01 Thread Ervin Hegedüs

I made an investigation and maybe the problem is in another package:
libnginx-mod-http-ndk-dev 1:0.3.3-1.

The report is here:

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

I'll inform you here about the result of the investigation.

Regards,


a.

Bug#1068203: spectrwm: hard-coded dependency on pre-t64 library

Hi

On 2024-04-01 23:39:37 +0200, Andrea Bolognani wrote:
> On Mon, Apr 01, 2024 at 10:37:03PM +0200, Sebastian Ramacher wrote:
> > Source: spectrwm
> > Version: 3.5.1-1
> > Severity: serious
> > X-Debbugs-Cc: sramac...@debian.org
> > 
> > spectrwm builds a packages with a hard-coded dependency on a library
> > package involved in the time_t 64 transition. This dependency needs to
> > be updated.
> 
> It would be useful if you could be more specific. I guess you're
> talking about the dependency on libxt6?

Yes.

> 
> The problem with it, and the reason why a manual dependency is used
> in that case, is that ${shlib:Depends} will not pick it up, since
> it's dlopen()ed rather than linked against.
> 
> Do you have any suggestions on how to handle this in a way that plays
> well with the 64-bit time_t transition?

You could derive it from the the dependencies of libxt-dev during the
build or for the time being simply change the dependency based on the
rename of the libxt6 -- provided that spectrwm is compatible with the
new ABI.

Cheers
-- 
Sebastian Ramacher

Processed (with 1 error): Re: manpages-dev: Fails to upgrade due to file conflict

Processing control commands:

> notfoud -1 6.07-1
Unknown command or malformed arguments to command.

> found -1 6.7-1
Bug #1068166 [manpages-dev] manpages-dev: Fails to upgrade due to file conflict
Bug #1068167 [manpages-dev] manpages-dev: Update to 6.7-1 fails
Marked as found in versions manpages/6.7-1.
Marked as found in versions manpages/6.7-1.

-- 
1068166: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068166
1068167: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068167
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1068166: manpages-dev: Fails to upgrade due to file conflict

2024-04-01 Thread Andreas Beckmann

Followup-For: Bug #1068166
Control: notfoud -1 6.07-1
Control: found -1 6.7-1

There are also a few manpages that moved from manpages (6.05.01-1) to 
manpages-dev (6.7-1):

usr/share/man/man3/sigevent.3type.gz
usr/share/man/man3/sigval.3type.gz
usr/share/man/man7/sigevent.7.gz

resulting in another file conflict:

  Preparing to unpack .../manpages-dev_6.7-1_all.deb ...
  Unpacking manpages-dev (6.7-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/manpages-dev_6.7-1_all.deb (--unpack):
   trying to overwrite '/usr/share/man/man3/sigevent.3type.gz', which is also 
in package manpages 6.05.01-1
  Errors were encountered while processing:
   /var/cache/apt/archives/manpages-dev_6.7-1_all.deb

Therefore manpages-dev needs to add/bump
  Breaks+Replaces: manpages (<< 6.7)
too.


Andreas

Bug#1000003: marked as done (pdfgrep: depends on obsolete pcre3 library)

Your message dated Mon, 01 Apr 2024 21:52:09 +
with message-id 
and subject line Bug#103: fixed in pdfgrep 2.2.0-0.1
has caused the Debian Bug report #103,
regarding pdfgrep: depends on obsolete pcre3 library
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
103: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=103
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pdfgrep
Severity: important
User: matthew-pcre...@debian.org
Usertags: obsolete-pcre3

Dear maintainer,

Your package still depends on the old, obsolete PCRE3[0] libraries
(i.e. libpcre3-dev). This has been end of life for a while now, and
upstream do not intend to fix any further bugs in it. Accordingly, I
would like to remove the pcre3 libraries from Debian, preferably in
time for the release of Bookworm.

The newer PCRE2 library was first released in 2015, and has been in
Debian since stretch. Upstream's documentation for PCRE2 is available
here: https://pcre.org/current/doc/html/

Many large projects that use PCRE have made the switch now (e.g. git,
php); it does involve some work, but we are now at the stage where
PCRE3 should not be used, particularly if it might ever be exposed to
untrusted input.

This mass bug filing was discussed on debian-devel@ in
https://lists.debian.org/debian-devel/2021/11/msg00176.html

Regards,

Matthew [0] Historical reasons mean that old PCRE is packaged as
pcre3 in Debian 
--- End Message ---
--- Begin Message ---
Source: pdfgrep
Source-Version: 2.2.0-0.1
Done: Raul Cheleguini 

We believe that the bug you reported is fixed in the latest version of
pdfgrep, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1000...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Raul Cheleguini  (supplier of updated pdfgrep 
package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 26 Mar 2024 11:57:16 -0300
Source: pdfgrep
Architecture: source
Version: 2.2.0-0.1
Distribution: unstable
Urgency: medium
Maintainer: Christoph Egger 
Changed-By: Raul Cheleguini 
Closes: 103
Changes:
 pdfgrep (2.2.0-0.1) unstable; urgency=medium
 .
   [ Raul Cheleguini ]
   * Non-maintainer upload.
   * New upstream release.
   * d/control: Update Build-Depends to include pcre2, pkgconf and others.
 (Closes: #103).
Checksums-Sha1:
 833b57dcc55dafcb054dafc766847e5f49ebc6fc 2170 pdfgrep_2.2.0-0.1.dsc
 753e071c464bea4921d2eea3c9154c00c7e9dd09 213237 pdfgrep_2.2.0.orig.tar.gz
 0f92e624d30281f646eea5c01b918420395b0f59 228 pdfgrep_2.2.0.orig.tar.gz.asc
 92a0737de69439ab6b2357c90662aac227e5bea1 6384 pdfgrep_2.2.0-0.1.debian.tar.xz
 541e2620ac85e1f5ecdd415789621949c9a40b5f 8150 pdfgrep_2.2.0-0.1_amd64.buildinfo
Checksums-Sha256:
 ca4daf009bc7171f10338e183f375deab1d32bda59bf2350cbda58d7ce73edf0 2170 
pdfgrep_2.2.0-0.1.dsc
 0661e531e4c0ef097959aa1c9773796585db39c72c84a02ff87d2c3637c620cb 213237 
pdfgrep_2.2.0.orig.tar.gz
 897d6d58d67847d116d8461e95ea6ae632f06da36c6d4c5a6715a1fc77882af6 228 
pdfgrep_2.2.0.orig.tar.gz.asc
 544f07dd70909f4faec3520b86edebdb035a659d85fb5b625612912e04e6ea5c 6384 
pdfgrep_2.2.0-0.1.debian.tar.xz
 41779364c13ff286a8237aee66e65ab38ab8b14bd2bd0820cb7f0049ed597b61 8150 
pdfgrep_2.2.0-0.1_amd64.buildinfo
Files:
 42f843006accd5e7cb31916f83377076 2170 utils optional pdfgrep_2.2.0-0.1.dsc
 f74b5505e71e8bad576285c6bd1790d9 213237 utils optional 
pdfgrep_2.2.0.orig.tar.gz
 c05893f601923ee8da581cd1ee7bc2bd 228 utils optional 
pdfgrep_2.2.0.orig.tar.gz.asc
 631a5377d74d5f6dd817cfa90dd15219 6384 utils optional 
pdfgrep_2.2.0-0.1.debian.tar.xz
 d80700a52763edcc5b7c69d4ffdbed45 8150 utils optional 
pdfgrep_2.2.0-0.1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJIBAEBCgAyFiEEI3pUsQKHKL8A7zH00Ot2KGX8XjYFAmYEjr0UHHNlcmdpb2Rq
QGRlYmlhbi5vcmcACgkQ0Ot2KGX8XjZnARAApF5xmEJUgtWP98+RFe3XTLle5ztM
Iu9MaQlwwDndX6Av7BX4CGHPiWmijMfg374FX3+JL68uO4Yksuvttgpo1s6o51QB
a8vtPmoenoh1Gqr6dcPOZX09Y1yKOLczQrohZO0JPXn+3NmHoQb7iLcF9PgGHorM
bwoZE/nmbGitW48ZTNGu/Eatn7pg0ph//Ee1jyAyjZ+uAMe6EeT8ADTdA8O7ZeFG
Mgxe4G97RWGSnoVMKP9E5pzCLU3eXhd1ZaZfUSKSyDDGLpwCqb2NADAqcjxsdnDP

Bug#1068203: spectrwm: hard-coded dependency on pre-t64 library

2024-04-01 Thread Andrea Bolognani

On Mon, Apr 01, 2024 at 10:37:03PM +0200, Sebastian Ramacher wrote:
> Source: spectrwm
> Version: 3.5.1-1
> Severity: serious
> X-Debbugs-Cc: sramac...@debian.org
> 
> spectrwm builds a packages with a hard-coded dependency on a library
> package involved in the time_t 64 transition. This dependency needs to
> be updated.

It would be useful if you could be more specific. I guess you're
talking about the dependency on libxt6?

The problem with it, and the reason why a manual dependency is used
in that case, is that ${shlib:Depends} will not pick it up, since
it's dlopen()ed rather than linked against.

Do you have any suggestions on how to handle this in a way that plays
well with the 64-bit time_t transition?

Thanks.

-- 
Andrea Bolognani 
Resistance is futile, you will be garbage collected.

signature.asc
Description: PGP signature

Bug#1068104: pandas: FTBFS on 32-bit architectures with -D_TIME_BITS=64

2024-04-01 Thread Rebecca N. Palmer


Thanks - I plan to look at this tomorrow.

Bug#1067603: marked as done (contextfree: FTBFS on armhf: test failure with missing codec)

Your message dated Tue, 2 Apr 2024 00:24:05 +0300
with message-id 
and subject line Re: Bug#1067603: contextfree: FTBFS on armhf: test failure 
with missing codec
has caused the Debian Bug report #1067603,
regarding contextfree: FTBFS on armhf: test failure with missing codec
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)

-- 
1067603: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067603
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: contextfree
Version: 3.4+dfsg-1.1
Severity: important
Tags: ftbfs
X-Debbugs-Cc: ken...@xdump.org

Dear Maintainer,

   * What led up to the situation?

   contextfree can't build on armel,armhf.

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

apt-get source contextfree
cd contextfree-3.4+dfsg
debuild -us -uc

   * What was the outcome of this action?

See
https://buildd.debian.org/status/fetch.php?pkg=contextfree=armhf=3.4%2Bdfsg-1.1=1711207519=0

input/ziggy_v2.cfdg   pass Reading rules file input/mtree.cfdg
Restarting as a version 3 design
8 rules loaded
Generating 8bit gray-scale Quicktime movie, variation FFGH...
Failed to create movie file: codec not found
make[1]: *** [Makefile:188: test] Error 8
make[1]: Leaving directory '/home/kenhys/work/contextfree-3.4+dfsg'
dh_auto_test: error: make -j8 test returned exit code 2
make: *** [debian/rules:6: build] Error 25
dpkg-buildpackage: error: debian/rules build subprocess returned exit
status 2 debuild: fatal error at line 1184:
dpkg-buildpackage -us -uc -ui failed

   * What outcome did you expect instead?

contextfree can build on armel/armhf.

-- System Information:
Debian Release: trixie/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'unstable')
Architecture: armhf (armv8l)

Kernel: Linux 6.1.0-18-arm64 (SMP w/8 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: unable to detect

Versions of packages contextfree depends on:
pn  libagg2
ii  libavcodec60   7:6.1.1-3
ii  libavformat60  7:6.1.1-3
ii  libavutil587:6.1.1-3
ii  libc6  2.37-15.1
ii  libgcc-s1  14-20240315-1
ii  libicu72   72.1-4+b1
pn  libpng16-16
ii  libstdc++6 14-20240315-1
ii  libswscale77:6.1.1-3
--- End Message ---
--- Begin Message ---
On Sun, Mar 24, 2024 at 09:04:49PM +0900, Kentaro HAYASHI wrote:
> Package: contextfree
> Version: 3.4+dfsg-1.1
> Severity: important
> Tags: ftbfs
> X-Debbugs-Cc: ken...@xdump.org
> 
> Dear Maintainer,
> 
> 
>* What led up to the situation?
> 
>contextfree can't build on armel,armhf.
> 
>* What exactly did you do (or not do) that was effective (or
>  ineffective)?
> 
> apt-get source contextfree
> cd contextfree-3.4+dfsg
> debuild -us -uc
> 
>* What was the outcome of this action?
> 
> See
> https://buildd.debian.org/status/fetch.php?pkg=contextfree=armhf=3.4%2Bdfsg-1.1=1711207519=0
> 
> input/ziggy_v2.cfdg   pass Reading rules file input/mtree.cfdg
> Restarting as a version 3 design
> 8 rules loaded
> Generating 8bit gray-scale Quicktime movie, variation FFGH...
> Failed to create movie file: codec not found
> make[1]: *** [Makefile:188: test] Error 8
> make[1]: Leaving directory '/home/kenhys/work/contextfree-3.4+dfsg'
> dh_auto_test: error: make -j8 test returned exit code 2
> make: *** [debian/rules:6: build] Error 25
> dpkg-buildpackage: error: debian/rules build subprocess returned exit
> status 2 debuild: fatal error at line 1184:
> dpkg-buildpackage -us -uc -ui failed
> 
>* What outcome did you expect instead?
> 
> contextfree can build on armel/armhf.
>...

Whatever the problem was (likely related to the ongoing transition to 
64bit time_t on armel/armhf) seems to be fixed now:
https://buildd.debian.org/status/logs.php?pkg=contextfree=3.4%2Bdfsg-1.1

cu
Adrian--- End Message ---

Bug#1053196: marked as done (Please remove librados-dev build-depends on all 32 bits arch)

Your message dated Mon, 01 Apr 2024 21:16:55 +
with message-id 
and subject line Bug#1053196: fixed in uwsgi 2.0.24-3
has caused the Debian Bug report #1053196,
regarding Please remove librados-dev build-depends on all 32 bits arch
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1053196: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1053196
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: uwsgi
Severity: important

Hi,

I'd like to remove 32 bits support from Ceph, because upstream makes some
64 bits assumptions a bit everywhere, because it's not tested in upstream
CI, and because it is increasingly difficult to build Ceph on a smaller
addressing footprint (we used to have many tricks to reduce the build footprint
that isn't sustainable in the long run).

So please remove librados-dev in build-depends of your package for all 32
bits arch, and remove Ceph support in all 32 bits binaries. I'll upload
Ceph with Build-Depends: architecture-is-64-bit as soon as this is done
for the affected packages:
- fio
- libvirt
- tcmu
- qemu
- eckit
- fdb
- nfs-ganesha
- uwsgi
- xrootd

Cheers,

Thomas Goirand (zigo)
--- End Message ---
--- Begin Message ---
Source: uwsgi
Source-Version: 2.0.24-3
Done: Jonas Smedegaard 

We believe that the bug you reported is fixed in the latest version of
uwsgi, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1053...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Jonas Smedegaard  (supplier of updated uwsgi package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 01 Apr 2024 22:01:33 +0200
Source: uwsgi
Architecture: source
Version: 2.0.24-3
Distribution: unstable
Urgency: medium
Maintainer: uWSGI packaging team 
Changed-By: Jonas Smedegaard 
Closes: 772386 1053196 1065996
Changes:
 uwsgi (2.0.24-3) unstable; urgency=medium
 .
   [ Alexandre Rossi ]
   * disable rados plugin on 32 bits archs;
 closes: #1053196, thanks to Thomas Goirand
   * drop useless dep on python3-distutils;
 closes: #1065996, thanks to Graham Inggs
   * fix bashism in initscript;
 closes: #772386, thanks to Raphael Geissert
Checksums-Sha1:
 ce6e052a5e3548e568f7c257dba3181195ff87b2 6916 uwsgi_2.0.24-3.dsc
 cd8acf0ec2443f52d2f822e1ee194d02ef0cac6d 73208 uwsgi_2.0.24-3.debian.tar.xz
 6d451974bf4ef72b14b0ac97367f8ec9fe2b775a 38756 uwsgi_2.0.24-3_amd64.buildinfo
Checksums-Sha256:
 c778ae67c80ba5d25f76b58051ee3f151ae558db9958602efdeeffbcdca9fea0 6916 
uwsgi_2.0.24-3.dsc
 e57155a57fd967a074599e6938e1c4ebb35a98970a03c52af2a32211bb152923 73208 
uwsgi_2.0.24-3.debian.tar.xz
 79328c2463c12d8452e2b26ae489670c80d59bcb9dba467a0356c80ed68c8643 38756 
uwsgi_2.0.24-3_amd64.buildinfo
Files:
 8f14b36b3b612de59ddbda191d33cdfe 6916 httpd optional uwsgi_2.0.24-3.dsc
 e1fea2e9e5007cc18f0662f217d05ce5 73208 httpd optional 
uwsgi_2.0.24-3.debian.tar.xz
 feeefe374a138539e5e99025db8e0acb 38756 httpd optional 
uwsgi_2.0.24-3_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmYLFegACgkQLHwxRsGg
ASHzSxAAikOJtYGY9b2di9xN7wCNzp86iTCrs0z0bCjMfhsEpREMIBNVyqXWc2w0
fxX7qe4mOx79Eypm8aRtjlJZjgw8wVui9skTPdG80MzFJLsmPjp2frcLWBixx8XF
fHhU45jzBteRQLWgroUCLFbUrS4/IjwBs2vqYFwjqNHUvMihHvN58j1/CcC3NF3k
JxKgk+g9JI3mAecKw9YzrK7AhGQ+2hFnwJKWNOgGTPXeoGm6U5h41PEInQQHDUH/
aPne9XYl7d5ks+YEvuRjF6WxiFfaKw9kaYF7w24zvxo+MHoJNjH/xzMuw2H/ENzj
xvlXa9dP4o8jvM634vEvGLtzrKoQirCGthiyIsTeUQSOslSBo+nrDqISvnLDaZzK
k3/OkFjMYjXreHdaIYEjhuwrtTyoQmrHvrLEnjHc8Poji01AKWVl+sYiuFJ/hAK0
9aTC8IoeF/k7EKTmGT5OqwhuwLRzbNjznIzGgZE1hLFCf9eOHMvfp45NNYK+tcIu
lyhP1wCb4AYB+FYpPeG+HRY9aTbkfOpHSJsiM21UehQrPEDmqc/A49oxy33m4hXO
pvKS/Di7qQL9KKQ5b8EH09CdA8j+tN0t1zH7Ep30xQxx/3i2gZU77yRJArSpkmWk
SOq9d/dB3xpA9CL2g6AxTwSqC7t++fE61OR2rbZpWD7SO5UGwTQ=
=Z35V
-END PGP SIGNATURE-



pgpSs_kIHXpXS.pgp
Description: PGP signature
--- End Message ---

Processed: squashfuse: diff for NMU version 0.5.2-0.1

Processing control commands:

> tags 1067010 + patch
Bug #1067010 [libsquashfuse-dev] libsquashfuse-dev: Incompatible pointer types 
on 32-bit architectures
Added tag(s) patch.
> tags 1067010 + pending
Bug #1067010 [libsquashfuse-dev] libsquashfuse-dev: Incompatible pointer types 
on 32-bit architectures
Added tag(s) pending.

-- 
1067010: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067010
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1067010: squashfuse: diff for NMU version 0.5.2-0.1

Control: tags 1067010 + patch
Control: tags 1067010 + pending

Dear maintainer,

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

Cheers
-- 
Sebastian Ramacher
diff -Nru squashfuse-0.5.0/.cirrus.yml squashfuse-0.5.2/.cirrus.yml
--- squashfuse-0.5.0/.cirrus.yml	2023-09-13 16:50:21.0 +0200
+++ squashfuse-0.5.2/.cirrus.yml	2024-02-22 16:19:33.0 +0100
@@ -3,12 +3,12 @@
 
 freebsd_task:
   freebsd_instance:
-image_family: freebsd-12-3
+image_family: freebsd-14-0
   setup_script:
 - pkg install -y autoconf automake libtool pkgconf fusefs-libs
 - pkg install -y lzo2 liblz4 zstd
 - pkg install -y squashfs-tools coreutils
-- kldload fuse
+- kldload fusefs
 - sysctl vfs.usermount=1
   build_script:
 - ./autogen.sh
diff -Nru squashfuse-0.5.0/configure.ac squashfuse-0.5.2/configure.ac
--- squashfuse-0.5.0/configure.ac	2023-09-13 16:50:21.0 +0200
+++ squashfuse-0.5.2/configure.ac	2024-02-22 16:19:33.0 +0100
@@ -1,4 +1,4 @@
-AC_INIT([squashfuse], [0.5.0], [d...@vasilevsky.ca])
+AC_INIT([squashfuse], [0.5.2], [d...@vasilevsky.ca])
 AC_CONFIG_MACRO_DIR([m4])
 AC_CONFIG_AUX_DIR([build-aux])
 AC_CONFIG_HEADERS([config.h])
@@ -91,6 +91,7 @@
 
 AC_SUBST([sq_mksquashfs_compressors])
 AC_CONFIG_FILES([tests/ll-smoke.sh],[chmod +x tests/ll-smoke.sh])
+AC_CONFIG_FILES([tests/ll-smoke-singlethreaded.sh],[chmod +x tests/ll-smoke-singlethreaded.sh])
 AC_CONFIG_FILES([tests/umount-test.sh],[chmod +x tests/umount-test.sh])
 
 
diff -Nru squashfuse-0.5.0/debian/changelog squashfuse-0.5.2/debian/changelog
--- squashfuse-0.5.0/debian/changelog	2023-11-02 09:42:28.0 +0100
+++ squashfuse-0.5.2/debian/changelog	2024-04-01 23:02:32.0 +0200
@@ -1,3 +1,11 @@
+squashfuse (0.5.2-0.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload
+  * New upstream release
+- Fix pointer types on 32 bit architectures (Closes: #1067010)
+
+ -- Sebastian Ramacher   Mon, 01 Apr 2024 23:02:32 +0200
+
 squashfuse (0.5.0-2) unstable; urgency=medium
 
   * Fix "needed headers (e.g. config.h) are not shipped"
diff -Nru squashfuse-0.5.0/.github/workflows/ci.yml squashfuse-0.5.2/.github/workflows/ci.yml
--- squashfuse-0.5.0/.github/workflows/ci.yml	2023-09-13 16:50:21.0 +0200
+++ squashfuse-0.5.2/.github/workflows/ci.yml	2024-02-22 16:19:33.0 +0100
@@ -17,6 +17,8 @@
 os: ubuntu-latest
 disable_fuse: "--disable-fuse"
 check_features: demo
+  - name: distcheck
+os: ubuntu-latest
   - name: Old distro
 os: ubuntu-20.04
   - name: Mac
@@ -29,6 +31,7 @@
 uses: actions/checkout@v2
   - name: apt dependencies
 run: > 
+  sudo apt-get update &&
   sudo apt-get install -y automake autoconf libtool pkg-config
   zlib1g-dev liblzo2-dev liblzma-dev liblz4-dev libzstd-dev
   fio
@@ -46,17 +49,20 @@
   brew install autoconf automake libtool pkgconfig squashfs coreutils
   brew install --cask macfuse
 if: runner.os == 'macOS'
-  - name: build
+  - name: configure
 run: |
   ./autogen.sh
   CPPFLAGS="-Werror" ./configure $DISABLE_FUSE
+  - name: build
+run: |
   make -j2 V=1
+if: matrix.name != 'distcheck'
   - name: test
 run: |
   make check
   diff -u ci/expected-features/${CHECK_FEATURES:-all} ci/features
-if: runner.os != 'macOS'
-  - name: test
+if: runner.os != 'macOS' && matrix.name != 'distcheck'
+  - name: test mac
 run: |
   # On macOS loading the macfuse extension is needed.  This
   # command should load it without rebooting, except System
@@ -68,8 +74,13 @@
 diff -u ci/expected-features/${CHECK_FEATURES:-all} ci/features
   fi
 if: runner.os == 'macOS'
+  - name: distcheck
+run: |
+  make distcheck
+if: matrix.name == 'distcheck'
   - name: install
 run: sudo make install
+if: matrix.name != 'distcheck'
   - name: output
 run: |
 cp /tmp/*.log . || true
diff -Nru squashfuse-0.5.0/.gitignore squashfuse-0.5.2/.gitignore
--- squashfuse-0.5.0/.gitignore	2023-09-13 16:50:21.0 +0200
+++ squashfuse-0.5.2/.gitignore	2024-02-22 16:19:33.0 +0100
@@ -33,4 +33,5 @@
 ci/features
 tests/lib.sh
 tests/ll-smoke.sh
+tests/ll-smoke-singlethreaded.sh
 tests/umount-test.sh
diff -Nru squashfuse-0.5.0/ll.c squashfuse-0.5.2/ll.c
--- squashfuse-0.5.0/ll.c	2023-09-13 16:50:21.0 +0200
+++ squashfuse-0.5.2/ll.c	2024-02-22 16:19:33.0 +0100
@@ -410,7 +410,12 @@
 }
 
 void sqfs_ll_op_forget(fuse_req_t req, fuse_ino_t ino,
-		unsigned long nlookup) {
+#ifdef HAVE_FUSE_LL_FORGET_OP_64T
+		uint64_t nlookup
+#else
+		unsigned long nlookup
+#endif
+		) {
 	sqfs_ll_i lli;

Bug#1068205: gauche: FTBFS on arm{el,hf}: "list.c", line 827 (Scm__GetExtendedPairDescriptor): Assertion failed: (z->hiddenTag&0x7) == 0x7

Source: gauche
Version: 0.9.14-2
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: sramac...@debian.org

https://buildd.debian.org/status/fetch.php?pkg=gauche=armhf=0.9.14-2=1711974534=0

gcc -DHAVE_CONFIG_H -I. -I. -I./../gc/include -I../gc/include 
`./get-atomic-ops-flags.sh .. .. --cflags`  -D_LARGEFILE_SOURCE 
-D_FILE_OFFSET_BITS=64 -D_TIME_BITS=64 -Wdate-time -D_FORTIFY_SOURCE=2  -g -O2 
-Werror=implicit-function-declaration -ffile-prefix-map=/<>=. 
-fstack-protector-strong -fstack-clash-protection -Wformat 
-Werror=format-security -Wall -Wextra -Wno-unused-label -fPIC 
-fomit-frame-pointer  -c test-extra.c
gcc -DHAVE_CONFIG_H -I. -I. -I./../gc/include -I../gc/include 
`./get-atomic-ops-flags.sh .. .. --cflags`  -D_LARGEFILE_SOURCE 
-D_FILE_OFFSET_BITS=64 -D_TIME_BITS=64 -Wdate-time -D_FORTIFY_SOURCE=2  -g -O2 
-Werror=implicit-function-declaration -ffile-prefix-map=/<>=. 
-fstack-protector-strong -fstack-clash-protection -Wformat 
-Werror=format-security -Wall -Wextra -Wno-unused-label -fPIC 
-fomit-frame-pointer  -c libextra.c
TARGETLIB="`pwd`"  gcc -g -O2 -Werror=implicit-function-declaration 
-ffile-prefix-map=/<>=. -fstack-protector-strong 
-fstack-clash-protection -Wformat -Werror=format-security -Wall -Wextra 
-Wno-unused-label -fPIC -Wl,--rpath="`pwd`" -L. -Wl,-z,relro  -rdynamic -o 
test-extra test-extra.o libextra.o -lgauche-0.98 -lmbedtls -lcrypt -lrt -lm  
-lpthread
make[3]: Leaving directory '/<>/src'
make[3]: Entering directory '/<>/lib'
make[3]: Nothing to be done for 'all'.
make[3]: Leaving directory '/<>/lib'
make[3]: Entering directory '/<>/ext'
(cd util; make default)
make[4]: Entering directory '/<>/ext/util'
"../../src/gosh" -ftest "../../lib/tools/precomp" -e -P -o util--match 
../../libsrc/util/match.scm
"list.c", line 827 (Scm__GetExtendedPairDescriptor): Assertion failed: 
(z->hiddenTag&0x7) == 0x7
make[4]: *** [Makefile:26: util--match.c] Error 1
make[4]: Leaving directory '/<>/ext/util'
make[3]: *** [Makefile:38: util] Error 2
make[3]: Leaving directory '/<>/ext'
make[2]: *** [Makefile:47: all] Error 1
make[2]: Leaving directory '/<>'
dh_auto_build: error: make -j1 returned exit code 2
make[1]: *** [debian/rules:23: override_dh_auto_build] Error 255

Cheers
-- 
Sebastian Ramacher

Processed: tagging 1061076

Processing commands for cont...@bugs.debian.org:

> tags 1061076 + ftbfs
Bug #1061076 [src:kbtin] kbtin: FTBFS with stack-clash-protection on armhf due 
to valgrind segfault
Added tag(s) ftbfs.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1061076: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061076
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1068204: pdl: FTBFS on i386: Failed 1/45 test programs. 2/2262 subtests failed.

Source: pdl
Version: 1:2.086-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: sramac...@debian.org

https://buildd.debian.org/status/fetch.php?pkg=pdl=i386=1%3A2.086-1=1712002199=0

not ok 569 - col=0
not ok 570 - col=1

...

Test Summary Report
---
t/pdl_from_string.t  (Wstat: 0 Tests: 144 Failed: 0)
  TODO passed:   60-62
t/primitive-random.t (Wstat: 0 Tests: 3 Failed: 0)
  TODO passed:   1
t/slice.t(Wstat: 512 (exited 2) Tests: 602 Failed: 2)
  Failed tests:  569-570
  Non-zero exit status: 2
Files=45, Tests=2262, 56 wallclock secs ( 0.48 usr  0.12 sys + 54.74 cusr  5.00 
csys = 60.34 CPU)
Result: FAIL
Failed 1/45 test programs. 2/2262 subtests failed.
make[2]: *** [Makefile:1077: test_dynamic] Error 255


Cheers
-- 
Sebastian Ramacher

Bug#1068203: spectrwm: hard-coded dependency on pre-t64 library

Source: spectrwm
Version: 3.5.1-1
Severity: serious
X-Debbugs-Cc: sramac...@debian.org

spectrwm builds a packages with a hard-coded dependency on a library
package involved in the time_t 64 transition. This dependency needs to
be updated.

Cheers
-- 
Sebastian Ramacher

Bug#1068202: bazel-bootstrap: FTBFS: /usr/include/absl/base/policy_checks.h:79:2: error: #error "C++ versions less than C++14 are not supported."

Source: bazel-bootstrap
Version: 4.2.3+ds-9
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: sramac...@debian.org

https://buildd.debian.org/status/fetch.php?pkg=bazel-bootstrap=amd64=4.2.3%2Bds-9%2Bb2=1711976723=0

  /usr/bin/gcc -U_FORTIFY_SOURCE -fstack-protector -Wall 
-Wunused-but-set-parameter -Wno-free-nonheap-object -fno-omit-frame-pointer -g 
'-std=c++0x' -Wdate-time '-D_FORTIFY_SOURCE=2' -g -O2 
'-ffile-prefix-map=/<>=.' -fstack-protector-strong 
-fstack-clash-protection -Wformat '-Werror=format-security' -fcf-protection -MD 
-MF 
bazel-out/k8-dbg/bin/src/main/protobuf/_objs/command_server_cc_grpc/command_server.grpc.pb.pic.d
 
'-frandom-seed=bazel-out/k8-dbg/bin/src/main/protobuf/_objs/command_server_cc_grpc/command_server.grpc.pb.pic.o'
 -fPIC '-DGRPC_USE_PROTO_LITE=ON' -iquote . -iquote bazel-out/k8-dbg/bin 
-iquote external/debian_cc_deps -iquote 
bazel-out/k8-dbg/bin/external/debian_cc_deps -iquote external/debian_proto_deps 
-iquote bazel-out/k8-dbg/bin/external/debian_proto_deps 
-fno-canonical-system-headers -Wno-builtin-macro-redefined 
'-D__DATE__="redacted"' '-D__TIMESTAMP__="redacted"' '-D__TIME__="redacted"' -c 
bazel-out/k8-dbg/bin/src/main/protobuf/command_server.grpc.pb.cc -o 
bazel-out/k8-dbg/bin/src/main/protobuf/_objs/command_server_cc_grpc/command_server.grpc.pb.pic.o)
Execution platform: //:default_host_platform
␛[32m[256 / 1,677]␛[0m 5 actions running
JavacBootstrap .../devtools/build/buildjar/libstarlark-deps.jar; 18s local
Compiling src/main/cpp/blaze.cc; 3s local
@debian_proto_deps//:descriptor_proto; 3s local
Compiling src/main/protobuf/command_server.pb.cc; 3s local
Compiling src/main/cpp/option_processor.cc; 1s local

␛[1A␛[K
␛[1A␛[K
␛[1A␛[K
␛[1A␛[K
␛[1A␛[K
␛[1A␛[KIn file included from /usr/include/absl/base/config.h:86,
 from /usr/include/absl/base/const_init.h:25,
 from /usr/include/absl/synchronization/mutex.h:67,
 from /usr/include/grpcpp/impl/codegen/sync.h:32,
 from /usr/include/grpcpp/client_context.h:46,
 from /usr/include/grpcpp/impl/call_op_set.h:29,
 from /usr/include/grpcpp/support/server_callback.h:27,
 from /usr/include/grpcpp/impl/codegen/server_callback.h:24,
 from 
/usr/include/grpcpp/impl/codegen/server_callback_handlers.h:25,
 from /usr/include/grpcpp/generic/async_generic_service.h:24,
 from 
bazel-out/k8-dbg/bin/src/main/protobuf/command_server.grpc.pb.h:31,
 from 
bazel-out/k8-dbg/bin/src/main/protobuf/command_server.grpc.pb.cc:6:
/usr/include/absl/base/policy_checks.h:79:2: error: #error "C++ versions less 
than C++14 are not supported."
   79 | #error "C++ versions less than C++14 are not supported."
  |  ^

Cheers
-- 
Sebastian Ramacher

Bug#1067827: marked as done (nheko: FTBFS on armhf: virtual memory exhausted: Cannot allocate memory)

Your message dated Mon, 01 Apr 2024 22:15:09 +0200
with message-id <171200250919.781844.8760648054923102...@auryn.jones.dk>
and subject line Re: Bug#1067827: nheko: FTBFS on armhf: virtual memory 
exhausted: Cannot allocate memory
has caused the Debian Bug report #1067827,
regarding nheko: FTBFS on armhf: virtual memory exhausted: Cannot allocate 
memory
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1067827: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067827
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: nheko
Version: 0.11.3+~0.9.2+~1.0.0+~0.3.0-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: sramac...@debian.org

https://buildd.debian.org/status/fetch.php?pkg=nheko=armhf=0.11.3%2B%7E0.9.2%2B%7E1.0.0%2B%7E0.3.0-1=1711340621=0

In static member function ‘static constexpr _Up* std::__copy_move<_IsMove, 
true, std::random_access_iterator_tag>::__copy_m(_Tp*, _Tp*, _Up*) [with _Tp = 
unsigned int; _Up = unsigned int; bool _IsMove = false]’,
inlined from ‘constexpr _OI std::__copy_move_a2(_II, _II, _OI) [with bool 
_IsMove = false; _II = unsigned int*; _OI = unsigned int*]’ at 
/usr/include/c++/13/bits/stl_algobase.h:506:30,
inlined from ‘constexpr _OI std::__copy_move_a1(_II, _II, _OI) [with bool 
_IsMove = false; _II = unsigned int*; _OI = unsigned int*]’ at 
/usr/include/c++/13/bits/stl_algobase.h:533:42,
inlined from ‘constexpr _OI std::__copy_move_a(_II, _II, _OI) [with bool 
_IsMove = false; _II = unsigned int*; _OI = unsigned int*]’ at 
/usr/include/c++/13/bits/stl_algobase.h:540:31,
inlined from ‘constexpr _OI std::copy(_II, _II, _OI) [with _II = unsigned 
int*; _OI = unsigned int*]’ at /usr/include/c++/13/bits/stl_algobase.h:633:7,
inlined from ‘static _ForwardIterator 
std::__uninitialized_copy::__uninit_copy(_InputIterator, _InputIterator, 
_ForwardIterator) [with _InputIterator = unsigned int*; _ForwardIterator = 
unsigned int*]’ at /usr/include/c++/13/bits/stl_uninitialized.h:147:27,
inlined from ‘_ForwardIterator std::uninitialized_copy(_InputIterator, 
_InputIterator, _ForwardIterator) [with _InputIterator = unsigned int*; 
_ForwardIterator = unsigned int*]’ at 
/usr/include/c++/13/bits/stl_uninitialized.h:185:15,
inlined from ‘constexpr void fmt::v9::basic_memory_buffer::grow(size_t) [with T = unsigned int; unsigned int SIZE = 32; 
Allocator = std::allocator]’ at /usr/include/fmt/format.h:925:26,
inlined from ‘constexpr void 
fmt::v9::detail::buffer::try_reserve(size_t) [with T = unsigned int]’ at 
/usr/include/fmt/core.h:928:39,
inlined from ‘constexpr void 
fmt::v9::detail::buffer::try_reserve(size_t) [with T = unsigned int]’ at 
/usr/include/fmt/core.h:927:24,
inlined from ‘constexpr void fmt::v9::detail::buffer::try_resize(size_t) 
[with T = unsigned int]’ at /usr/include/fmt/core.h:919:16,
inlined from ‘constexpr void fmt::v9::basic_memory_buffer::resize(size_t) [with T = unsigned int; unsigned int SIZE = 32; 
Allocator = std::allocator]’ at /usr/include/fmt/format.h:897:63,
inlined from ‘constexpr void fmt::v9::detail::bigint::assign(UInt) [with 
UInt = long long unsigned int; typename std::enable_if<(std::is_same::value || std::is_same::value), int>::type  = 0]’ at 
/usr/include/fmt/format.h:2792:19,
inlined from ‘constexpr void fmt::v9::detail::bigint::operator=(Int) [with 
Int = int]’ at /usr/include/fmt/format.h:2813:11,
inlined from ‘constexpr void 
fmt::v9::detail::format_dragon(basic_fp, unsigned int, int, 
buffer&, int&)’ at /usr/include/fmt/format.h:3013:11,
inlined from ‘constexpr int fmt::v9::detail::format_float(Float, int, 
float_specs, buffer&) [with Float = double]’ at 
/usr/include/fmt/format.h:3171:18:
/usr/include/c++/13/bits/stl_algobase.h:437:30: warning: ‘void* 
__builtin_memmove(void*, const void*, unsigned int)’ forming offset 4 is out of 
the bounds [0, 4] [-Warray-bounds=]
  437 | __builtin_memmove(__result, __first, sizeof(_Tp) * _Num);
  | ~^~~
[ 45%] Building CXX object CMakeFiles/nheko.dir/src/ui/UIA.cpp.o
/usr/bin/c++ -DFMT_SHARED -DGSTREAMER_AVAILABLE -DNHEKO_DBUS_SYS 
-DQAPPLICATION_CLASS=QApplication -DQT_CONCURRENT_LIB -DQT_CORE_LIB 
-DQT_DBUS_LIB -DQT_GUI_LIB -DQT_MULTIMEDIA_LIB -DQT_NETWORK_LIB -DQT_NO_DEBUG 
-DQT_QMLMODELS_LIB -DQT_QML_LIB -DQT_QUICKCONTROLS2_LIB -DQT_QUICKWIDGETS_LIB 
-DQT_QUICK_LIB -DQT_SVG_LIB -DQT_WIDGETS_LIB -DSPDLOG_COMPILED_LIB 
-DSPDLOG_FMT_EXTERNAL -DSPDLOG_SHARED_LIB

Bug#1067829: Additional information

2024-04-01 Thread Vladimir Petko

Hi,

I have submitted the bug upstream[1] here, and the patch contains
(long long int) cast as it would not be compiled otherwise.
The Ubuntu patch also contains a cast[2].
I apologise for not forwarding the patch correctly. I have attached
the patch forwarded upstream.

Best Regards,
 Vladimir.

[1] https://bugzilla.kernel.org/show_bug.cgi?id=218540
[2] 
https://launchpad.net/ubuntu/+archive/primary/+sourcefiles/nfs-utils/1:2.6.4-3ubuntu4/nfs-utils_2.6.4-3ubuntu4.debian.tar.xz
Description: cast to a type with a known size to ensure sprintf works
Author: Vladimir Petko 
Bug: https://bugzilla.kernel.org/show_bug.cgi?id=218540
Bug-Ubuntu:  https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/2055349
Last-Update: 2024-02-29
--- a/support/junction/export-cache.c
+++ b/support/junction/export-cache.c
@@ -107,7 +107,7 @@
 		xlog(D_GENERAL, "%s: time(3) failed", __func__);
 		return FEDFS_ERR_SVRFAULT;
 	}
-	snprintf(flushtime, sizeof(flushtime), "%ld\n", now);
+	snprintf(flushtime, sizeof(flushtime), "%lld\n", (long long int)now);
 
 	for (i = 0; junction_proc_files[i] != NULL; i++) {
 		retval = junction_write_time(junction_proc_files[i], flushtime);

Processed: closing 1065940

Processing commands for cont...@bugs.debian.org:

> close 1065940 2.5.0-1+1
Bug #1065940 [src:ppp] ppp: FTBFS on arm{el,hf}: sys-linux.c:357:9: error: 
implicit declaration of function ‘sif6down’; did you mean ‘sifdown’? 
[-Werror=implicit-function-declaration]
Bug #1066134 [src:ppp] FTBFS due -Werror=implicit-function-declaration
Marked as fixed in versions ppp/2.5.0-1+1.
Marked as fixed in versions ppp/2.5.0-1+1.
Bug #1065940 [src:ppp] ppp: FTBFS on arm{el,hf}: sys-linux.c:357:9: error: 
implicit declaration of function ‘sif6down’; did you mean ‘sifdown’? 
[-Werror=implicit-function-declaration]
Bug #1066134 [src:ppp] FTBFS due -Werror=implicit-function-declaration
Marked Bug as done
Marked Bug as done
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1065940: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065940
1066134: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066134
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1063096: marked as done (python3-webview: proxy_tools dependency not found)

Your message dated Mon, 01 Apr 2024 19:22:04 +
with message-id 
and subject line Bug#1063096: fixed in python-pywebview 5.0.5+dfsg-1
has caused the Debian Bug report #1063096,
regarding python3-webview: proxy_tools dependency not found
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1063096: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063096
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python3-webview
Version: 4.4.1+dfsg-1
Severity: important

Dear Maintainer,

With the upgrade to python3-webview from 3.3.5 to 4.4.1, the package is
no longer usable.

The package is unable to find the module proxy_tools.

For example, a simple script using webview fails:

---
#!/bin/python3
import webview
webview.create_window(title = 'Captive Portal Login', 
  url = 'http://network-test.debian.org/nm',
  width = 1024,
  height = 768,
  min_size = (1024, 768),
  resizable = False)
webview.start()
---

The error is:

---
Traceback (most recent call last):
  File "/home/user/bin/captiveportal.py", line 3, in 
import webview
  File "/usr/lib/python3/dist-packages/webview/__init__.py", line 23, in 

from proxy_tools import module_property
ModuleNotFoundError: No module named 'proxy_tools'
---

Presumably, python3-proxy_tools needs to be packaged and added to the
dependencies of python3-webview.

Thanks!

David

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

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

Versions of packages python3-webview depends on:
ii  gir1.2-webkit2-4.1   2.42.4-1
ii  python3 [python3-supported-min]  3.11.6-1
ii  python3-bottle   0.12.25-1
ii  python3-gi   3.46.0-3
ii  python3-gi-cairo 3.46.0-3
ii  python3-typing-extensions4.7.1-2

python3-webview recommends no packages.

python3-webview suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: python-pywebview
Source-Version: 5.0.5+dfsg-1
Done: Jeremy Bícha 

We believe that the bug you reported is fixed in the latest version of
python-pywebview, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1063...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Jeremy Bícha  (supplier of updated python-pywebview package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 01 Apr 2024 14:51:18 -0400
Source: python-pywebview
Built-For-Profiles: noudeb
Architecture: source
Version: 5.0.5+dfsg-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team 
Changed-By: Jeremy Bícha 
Closes: 1063096
Changes:
 python-pywebview (5.0.5+dfsg-1) unstable; urgency=medium
 .
   * Team upload
   * New upstream release
   * Add patch to avoid dependency on proxy_tools which is not in Debian
 (Closes: #1063096)
Checksums-Sha1:
 3e21f3b12461cc7530c7c3f39d628113074290f7 2154 python-pywebview_5.0.5+dfsg-1.dsc
 04a16011df01ba4846e93c1b6cbf9529cbcdb61b 27085016 
python-pywebview_5.0.5+dfsg.orig.tar.xz
 d8e94b58fd8d5efaf8aee7fde3186149cabded5f 5068 
python-pywebview_5.0.5+dfsg-1.debian.tar.xz
 f2356028538c2da50121508e0e81fa9dd13c4a43 8096 
python-pywebview_5.0.5+dfsg-1_source.buildinfo
Checksums-Sha256:
 e6640b6f4e94a0b0757829af4cf4570c1dd3329178e22abf7694e5948cf1e27f 2154 
python-pywebview_5.0.5+dfsg-1.dsc
 2e88147125912b54a890f5728ea2fa15096ed8b884794bad28428f61bb80ff1f 27085016 
python-pywebview_5.0.5+dfsg.orig.tar.xz
 3426e616b7de2a9c1bfcd71c1ef42e1bba001f65172791d70d91dcd90548f4b5 5068 
python-pywebview_5.0.5+dfsg-1.debian.tar.xz
 083d707f0336ad99e7fa80935240e7e0495b30b5311ec4082658e00ca23eb8a5 8096 
python-pywebview_5.0.5+dfsg-1_source.buildinfo
Files:

Bug#1061264: marked as done (ocrmypdf: Uses deprecated/to be removed pypdf2 in autopkgtest)

Your message dated Mon, 01 Apr 2024 19:21:46 +
with message-id 
and subject line Bug#1061264: fixed in ocrmypdf 16.1.2+dfsg1-1
has caused the Debian Bug report #1061264,
regarding ocrmypdf: Uses deprecated/to be removed pypdf2 in autopkgtest
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1061264: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061264
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ocrmypdf
Version: 15.2.0+dfsg1-1
Severity: wishlist

I've recently adopted pypdf and pypdf2 into the Debian Python Team in response 
to an RFA for both packages.  As these are somewhat security sensitive packages 
(among my first acts after adopting the packages was to upload proposed updates 
for both to address minor security issues in Bookworm in the next point release 
- same bug in both), I do not think we should release pypdf2 in Trixie and have 
filed an RC bug to that effect.

ocrmypdf uses the package in debian/tests/control.  Please update to use
python3-pypdf insteadm.
--- End Message ---
--- Begin Message ---
Source: ocrmypdf
Source-Version: 16.1.2+dfsg1-1
Done: Anton Gladky 

We believe that the bug you reported is fixed in the latest version of
ocrmypdf, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1061...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Anton Gladky  (supplier of updated ocrmypdf package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 31 Mar 2024 15:25:33 +0200
Source: ocrmypdf
Architecture: source
Version: 16.1.2+dfsg1-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team 
Changed-By: Anton Gladky 
Closes: 1054243 1061264
Changes:
 ocrmypdf (16.1.2+dfsg1-1) unstable; urgency=medium
 .
   * [ab69dd4] New upstream version 16.1.2+dfsg1
   * [023612d] Update patch
   * [31332ef] Replace jbig2dec by jbig2. (Closes: #1054243)
   * [945b537] Remove python3-pypdf2 from d/t/control. (Closes: #1061264)
   * [26285ea] Set minimal pikepdf version to 8.14.0
Checksums-Sha1:
 df3d7cd52f51ca1a04459fa0914e3ba755a02d95 2523 ocrmypdf_16.1.2+dfsg1-1.dsc
 c24ed3cb13530769f9695a9571412ad9192f15d5 4835928 
ocrmypdf_16.1.2+dfsg1.orig.tar.xz
 ace84b4ec647927dd902db2500c8eff18e6ff5e2 38568 
ocrmypdf_16.1.2+dfsg1-1.debian.tar.xz
 6b15610c1fd69d0bb77d9b5a37b7bece47b21262 11602 
ocrmypdf_16.1.2+dfsg1-1_source.buildinfo
Checksums-Sha256:
 19ad9afe9028f6686c2ddefac8c4292c5645147b078d185bf97eb05e3da5df58 2523 
ocrmypdf_16.1.2+dfsg1-1.dsc
 999b8c9ccfc2b3c07087ba6bde78ae622d9774218d006677f9ae470269b7a1e9 4835928 
ocrmypdf_16.1.2+dfsg1.orig.tar.xz
 30d77469c9fbd14250422f49a0837167cdfc764cbfc571d2c68f90033ccca9a0 38568 
ocrmypdf_16.1.2+dfsg1-1.debian.tar.xz
 5d8585af27f62d23104292dd6acb13f7964b44ed2472bf6aa4425e6dbb5a536e 11602 
ocrmypdf_16.1.2+dfsg1-1_source.buildinfo
Files:
 f09cf6789998a8eb6d84bffb5e7e4a4c 2523 graphics optional 
ocrmypdf_16.1.2+dfsg1-1.dsc
 abf2806bd5c89c0ef2d61f8073743eed 4835928 graphics optional 
ocrmypdf_16.1.2+dfsg1.orig.tar.xz
 e910619fd1149ad95424a358795b3581 38568 graphics optional 
ocrmypdf_16.1.2+dfsg1-1.debian.tar.xz
 58b9678497f93b7f249dbcb35187b50c 11602 graphics optional 
ocrmypdf_16.1.2+dfsg1-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEu71F6oGKuG/2fnKF0+Fzg8+n/wYFAmYJZKEACgkQ0+Fzg8+n
/wYaNQ//QvpGtwm8rjLwgCiYoUuI2n6/DgYxIiuf3zRfUncd+AoFr//zR2YF/VIH
VXUYabU/2ngXmXxH9lUm14v8vCbKiIhQzQUkmTMOD8Pptb5DatD//LMX5H8Sjh+3
ih77Mq3uAKDieuVFFKNGYwAoklPefdMO8iWES6XlAe77NChsKIK4NzYfv5huvSQi
GAjBuXK1wetu1Q8gTbo6tcDObZbS3gAzuw10P8Ys1VfjDIY8jOFRLUtdN6mc3qEo
54fZ0MKNl0NFmJG54jippaEP8Iwr3zavJF6cAG/cYra7+yZEV0y3qerMkPL2sh+p
JOWn2RFoAyv3+l6pH0k9Z7ms6tP0mz25AKkPg8/YFJcUSfmgyk1dAEd1rD713G9f
g53jSwwEqcaoMB8INtF6m2njufwVm0NAAevkNIrx3bqPXRp/EqW9rok2IXRPXAiZ
yI65Q0SDKauUYl6A6b890ozd41+FeLFQfu2h9Oha5cN5O/BIe5O59pmO+DTw3s37
Ug79TbLS1W1yCO4T5reqCv3MTRJxcWsk65FQLoh0ih8ATVls8lv5hMv2BJbkbcy4
FvCPJGlRgciAP+0RbNW70ca7pjIuiqNp/FGlfvyoA8b13HLwfwz8keIMDg/dls0v
54mpcQkTCnf3SecwFvWL/W9Y/lhvcCipLcQfWVez6RKqa95c5fM=
=TNvs
-END PGP SIGNATURE-



pgp8KZjL7qTnf.pgp
Description: PGP signature
--- End Message ---

Bug#1067849: marked as done (util-linux: CVE-2024-28085: wall: escape sequence injection)

Your message dated Mon, 01 Apr 2024 19:17:11 +
with message-id 
and subject line Bug#1067849: fixed in util-linux 2.38.1-5+deb12u1
has caused the Debian Bug report #1067849,
regarding util-linux: CVE-2024-28085: wall: escape sequence injection
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1067849: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067849
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: util-linux
Version: 2.39.3-11
Severity: grave
Tags: security upstream
Justification: user security hole
X-Debbugs-Cc: car...@debian.org, Debian Security Team 
Control: found -1 2.38.1-5 
Control: found -1 2.36.1-8+deb11u1
Control: found -1 2.36.1-8
Control: found -1 2.33.1-0.1

Hi,

The following vulnerability was published for util-linux.

CVE-2024-28085[0]:
| escape sequence injection in wall


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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2024-28085
https://www.cve.org/CVERecord?id=CVE-2024-28085
[1] https://www.openwall.com/lists/oss-security/2024/03/27/5
[2] https://people.rit.edu/sjf5462/6831711781/wall_2_27_2024.txt
[3] https://github.com/skyler-ferrante/CVE-2024-28085

Regards,
Salvatore

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

Kernel: Linux 6.1.0-18-amd64 (SMP w/16 CPU threads; PREEMPT)
Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: sysvinit (via /sbin/init)
--- End Message ---
--- Begin Message ---
Source: util-linux
Source-Version: 2.38.1-5+deb12u1
Done: Chris Hofstaedtler 

We believe that the bug you reported is fixed in the latest version of
util-linux, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1067...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Chris Hofstaedtler  (supplier of updated util-linux package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 28 Mar 2024 10:52:12 +0100
Source: util-linux
Architecture: source
Version: 2.38.1-5+deb12u1
Distribution: bookworm-security
Urgency: medium
Maintainer: util-linux packagers 
Changed-By: Chris Hofstaedtler 
Closes: 1067849
Changes:
 util-linux (2.38.1-5+deb12u1) bookworm-security; urgency=medium
 .
   * Add upstream patches to fix CVE-2024-28085 (Closes: #1067849)
   * No longer install wall, write setgid tty to address CVE-2024-28085
   * d/gbp.conf: update for stable release
Checksums-Sha1:
 54ddd5493323ae44404aba68c2ddf78a69c91f93 4579 util-linux_2.38.1-5+deb12u1.dsc
 f62a7b6fe64ce7f4569b57d7d2d0875b39f79836 7495904 util-linux_2.38.1.orig.tar.xz
 297967a6bfa48f0c8c8b8dac7d12760922f532eb 118748 
util-linux_2.38.1-5+deb12u1.debian.tar.xz
 fd3119a6d9e2ad19b9c839dd655327a176436b66 7736 
util-linux_2.38.1-5+deb12u1_source.buildinfo
Checksums-Sha256:
 980d9d9d9e56c12c067c281d8e4e6b1314537d8dac408b9f933e033da535d455 4579 
util-linux_2.38.1-5+deb12u1.dsc
 60492a19b44e6cf9a3ddff68325b333b8b52b6c59ce3ebd6a0ecaa4c5117e84f 7495904 
util-linux_2.38.1.orig.tar.xz
 751272cc0bbf1ed84a5a3378798aac17164de12f449575cc979b5b294f27d305 118748 
util-linux_2.38.1-5+deb12u1.debian.tar.xz
 013688753f75751c11ab72360d5bedf856ff91915053e531a65165b2e842d8ec 7736 
util-linux_2.38.1-5+deb12u1_source.buildinfo
Files:
 a1a361170185e7c126b380931c290701 4579 base required 
util-linux_2.38.1-5+deb12u1.dsc
 cd11456f4ddd31f7fbfdd9488c0c0d02 7495904 base required 
util-linux_2.38.1.orig.tar.xz
 20ad3c99e9f82bbb81f27f44117869a7 118748 base required 
util-linux_2.38.1-5+deb12u1.debian.tar.xz
 b9da2223bdb388076b68c4573ee5d528 7736 base required 
util-linux_2.38.1-5+deb12u1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEfRrP+tnggGycTNOSXBPW25MFLgMFAmYFREwACgkQXBPW25MF
LgPG+Q/9HBcjLpOMMqJitTr2BuYh6Y4jnVBv3cHj+/e47MLp4+v6ZaPnKUfTRIM5
966xbNpDH6TPoX187Uwc9Ai74Xw2nsYMAJSy+UaRCINlld5wK9gcWPuZL8mKTB1+
4qOxegDLdFaBRX02rainA569p2hGJP1zpswb3uJFbGECDWzdnylHkvmLsQcR/c2W

Processed: Re: Bug#1067288: pulseaudio: FTBFS on x86: cpu-volume-test fails, segfault in svolume_orc_test

Processing control commands:

> reassign -1 src:pulseaudio 16.1+dfsg1-3
Bug #1067288 [src:orc] pulseaudio: FTBFS on x86: cpu-volume-test fails, 
segfault in svolume_orc_test
Bug #1067458 [src:orc] pulseaudio: FTBFS cpu-volume-test fails
Bug reassigned from package 'src:orc' to 'src:pulseaudio'.
Bug reassigned from package 'src:orc' to 'src:pulseaudio'.
No longer marked as found in versions orc/1:0.4.38-1.
No longer marked as found in versions orc/1:0.4.38-1.
Ignoring request to alter fixed versions of bug #1067288 to the same values 
previously set
Ignoring request to alter fixed versions of bug #1067458 to the same values 
previously set
Bug #1067288 [src:pulseaudio] pulseaudio: FTBFS on x86: cpu-volume-test fails, 
segfault in svolume_orc_test
Bug #1067458 [src:pulseaudio] pulseaudio: FTBFS cpu-volume-test fails
Marked as found in versions pulseaudio/16.1+dfsg1-3.
Marked as found in versions pulseaudio/16.1+dfsg1-3.
> forwarded -1 
> https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues/3803
Bug #1067288 [src:pulseaudio] pulseaudio: FTBFS on x86: cpu-volume-test fails, 
segfault in svolume_orc_test
Bug #1067458 [src:pulseaudio] pulseaudio: FTBFS cpu-volume-test fails
Changed Bug forwarded-to-address to 
'https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues/3803' from 
'https://gitlab.freedesktop.org/gstreamer/orc/-/issues/66'.
Changed Bug forwarded-to-address to 
'https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues/3803' from 
'https://gitlab.freedesktop.org/gstreamer/orc/-/issues/66'.

-- 
1067288: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067288
1067458: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067458
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1067288: pulseaudio: FTBFS on x86: cpu-volume-test fails, segfault in svolume_orc_test

2024-04-01 Thread Adrian Bunk

Control: reassign -1 src:pulseaudio 16.1+dfsg1-3
Control: forwarded -1 
https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues/3803

On Fri, Mar 22, 2024 at 10:29:23AM +, Simon McVittie wrote:
> Control: retitle -1 pulseaudio: FTBFS on x86: cpu-volume-test fails, segfault 
> in svolume_orc_test
> Control: reassign -1 src:orc 1:0.4.38-1
> Control: forwarded -1 https://gitlab.freedesktop.org/gstreamer/orc/-/issues/66
> Control: tags 1067458 + ftbfs sid trixie
> Control: merge 1067458 -1
> Control: affects 1067458 + src:pulseaudio
> 
> On Wed, 20 Mar 2024 at 21:48:23 +0100, Lucas Nussbaum wrote:
> > > === 47/53 
> > > 
> > > test: cpu-volume-test
> > > start time:   06:46:56
> > > duration: 2.82s
> > > result:   exit status 1
> > > command:  
> > > UBSAN_OPTIONS=halt_on_error=1:abort_on_error=1:print_summary=1:print_stacktrace=1
> > >  
> > > LD_LIBRARY_PATH=/<>/obj-x86_64-linux-gnu/src/pulse:/<>/obj-x86_64-linux-gnu/src/pulsecore:/<>/obj-x86_64-linux-gnu/src
> > >  MALLOC_PERTURB_=255 MAKE_CHECK=1 
> > > ASAN_OPTIONS=halt_on_error=1:abort_on_error=1:print_summary=1 
> > > /<>/obj-x86_64-linux-gnu/src/tests/cpu-volume-test
> > > --- stdout 
> > > ---
> > > Running suite(s): CPU
> > > 66%: Checks: 3, Failures: 0, Errors: 1
> > > ../src/tests/cpu-volume-test.c:188:E:svolume:svolume_orc_test:0: (after 
> > > this point) Received signal 11 (Segmentation fault)
> > > ==
> 
> This seems to be the same issue as #1067458.
> 
> If a fix isn't obvious, could we perhaps roll back orc to 0.4.34
> (presumably versioned as 1:0.4.38+really0.4.34), or disable its use
> in PulseAudio for now?

According to the information in the upstream bug, PulseAudio has fixed 
the test now.

> Thanks,
> smcv

cu
Adrian

Processed: Bug#1063096 marked as pending in python-pywebview

Processing control commands:

> tag -1 pending
Bug #1063096 [python3-webview] python3-webview: proxy_tools dependency not found
Added tag(s) pending.

-- 
1063096: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063096
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1063096: marked as pending in python-pywebview

2024-04-01 Thread Jeremy Bicha

Control: tag -1 pending

Hello,

Bug #1063096 in python-pywebview reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:

https://salsa.debian.org/python-team/packages/python-pywebview/-/commit/d1575dbdace0ea512353b55911daae774e450f0e


Add patch to avoid dependency on proxy_tools which is not in Debian

Closes: #1063096


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1063096

Processed: Re: python3-webview: proxy_tools dependency not found

Processing commands for cont...@bugs.debian.org:

> severity 1063096 serious
Bug #1063096 [python3-webview] python3-webview: proxy_tools dependency not found
Severity set to 'serious' from 'important'
>
End of message, stopping processing here.

Please contact me if you need assistance.
-- 
1063096: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063096
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1068178: marked as done (aegean, dependencies unsatisfiable on 32-bit non-i386 architectures.)

Your message dated Mon, 01 Apr 2024 18:34:14 +
with message-id 
and subject line Bug#1068178: fixed in aegean 0.16.0+dfsg-4
has caused the Debian Bug report #1068178,
regarding aegean, dependencies unsatisfiable on 32-bit non-i386 architectures.
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1068178: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068178
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---

Package: aegean
Version: 0.16.0+dfsg-3
Severity: serious
User: debian-...@lists.debian.org
Usertag: time-t

After being rebuilt for the time64 transition, aegen depends
on both libgenometools0t64 and libgenometools0. As a
result it is uninstallable on architectures that are undergoing
the time64 transition (armel, armhf and some debian-ports
archictures).
--- End Message ---
--- Begin Message ---
Source: aegean
Source-Version: 0.16.0+dfsg-4
Done: Sascha Steinbiss 

We believe that the bug you reported is fixed in the latest version of
aegean, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1068...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Sascha Steinbiss  (supplier of updated aegean package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 01 Apr 2024 19:49:51 +0200
Source: aegean
Architecture: source
Version: 0.16.0+dfsg-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Sascha Steinbiss 
Closes: 1068178
Changes:
 aegean (0.16.0+dfsg-4) unstable; urgency=medium
 .
   * Remove explicit runtime dependency on libgenometools0.
 Closes: #1068178
   * Add d/copyright information for debian/ directory.
   * Bump Standards-Version.
   * Add Rules-Requires-Root: no.
   * Update debhelper compat level to 13.
   * Only list files not installed.
   * Adjust renamed lintian tag overrides.
   * Bump watchfile version to 4.
Checksums-Sha1:
 d2ea1a806ae5e9eeb7c6c3a01870d305c516432d 2235 aegean_0.16.0+dfsg-4.dsc
 00691a8e3c55341d06cb35f66476e5f4b0a23426 9628 
aegean_0.16.0+dfsg-4.debian.tar.xz
 b23985289243e9d24af136a993fdff02ff93c37e 9177 
aegean_0.16.0+dfsg-4_amd64.buildinfo
Checksums-Sha256:
 710d89ddf5e359e827a0504644fcd7d7ed36bcdf3d8c79335033deb80dfbd090 2235 
aegean_0.16.0+dfsg-4.dsc
 18eaae267e4af9c076ea1679286b71f8a242d7e2124d09eb2457acd07b8e1f93 9628 
aegean_0.16.0+dfsg-4.debian.tar.xz
 da063b74db294fefd3ef59b77227ccf699a69733c2ac78b49aa543553f84e60a 9177 
aegean_0.16.0+dfsg-4_amd64.buildinfo
Files:
 e2fcd5125f2c256eff81fb8af1ccfa17 2235 science optional aegean_0.16.0+dfsg-4.dsc
 e15b076adebc76512ba2fa37111644de 9628 science optional 
aegean_0.16.0+dfsg-4.debian.tar.xz
 2fc0f304d5cb0c3ef7964fa9f0590bcd 9177 science optional 
aegean_0.16.0+dfsg-4_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEWzS6WqtVB+kDQm6F6NN64vCfSHIFAmYK+dgACgkQ6NN64vCf
SHILeA//coNh6nDC0Zgn+ch4paV8NXYfYNvbiwflkAWC+l5dEshpNg6UCYjDnfqX
GhMl0eDhRrkU04tIpv0ENRkmh6Gxnk1z3M/mfgvX2nfzgcjD73F0wdq4GAZxKgkn
+YwWy+Dbr98eFtXO68S522t9ODrHr7qT+navhG7ZaysrWw+v4YEVTSgQ9mP54qvG
ptXnM8qwq5M6Xp5qrfPOcyEWIzO+7XjQ2Jm6niBC0/afw5r73yxlaEVYN+Rvg+ZF
F21JAfSOfj5nNQ7nGAsyTbQrUp2WgabYI+K8/Fupp3SHvJbK3dfsiIgjofc9nJf6
sA1Q7HNpibbJGGOF1ApUU+fEV7rbYFHFriC5X6vUF/e5Fzyj10KbPS273F6OsPtZ
B3L2cQfLrhaXC/hXz/rbdLE7g5Vdo8gvxjPPrChybpnIE1aXurjazKXE2G13XYOs
zh81DqEhUBGXJhqk4z1Sbvmmy/LW/hHY6SytIQYTUweNGP1rpO+G3cGLcy/59gky
EVCSjj9kp73TV+8YwWthpYzUgsNGRjRxGSt8mdNfz4+5HZURQnpnR2iVbjtH89h1
sK7W0KsRQqkIVbVnBHnCF18mAGGshkSpS5FrX+y5Ye4XZyWRMci+6G3RsmEp172h
BgDvrCzb/0/kz52Fb0TAnVcjNkUHTQBLQUtubX+nvAAqFEUwq4M=
=KOiA
-END PGP SIGNATURE-



pgpRgxjPE4eHf.pgp
Description: PGP signature
--- End Message ---

Bug#1068197: debian-installer: accesses the internet during build

2024-04-01 Thread Cyril Brulebois

[ Switching from ML to bug. ]

Hi Jonathan,

Jonathan Carter  (2024-04-01):
> On 2024/04/01 18:55, Aurelien Jarno wrote:
> > debian-installer attemps network access during build, although only to
> > the mirrors listed in /etc/apt/sources.list and in a secure way. This is
> > forbidden by Policy 4.9:
> > 
> >For packages in the main archive, required targets must not attempt
> >network access, except, via the loopback interface, to services on the
> >build host that have been started by the build.
> > 
> > In addition this brings constraints to the build daemons infrastructure.
> 
> As far as I know, this doesn't happen until after d-i asked the question "Do
> you want to use a network mirror?" and the user answered "Yes", in which
> case I think that would count as informed consent.

This isn't about d-i runtime, this is about src:debian-installer's
*build* requiring network access, which is a very well known problem
(even though there are no obvious solutions, at least that I'm aware
of), and that's now getting in the way of changes being considered 
regarding the buildd network.


Cheers,
-- 
Cyril Brulebois (k...@debian.org)
D-I release manager -- Release team member -- Freelance Consultant


signature.asc
Description: PGP signature

Bug#1066266: marked as done (bsdgames: FTBFS: hunt/hunt/otto.c:181:9: error: implicit declaration of function ‘sigpause’; did you mean ‘pause’? [-Werror=implicit-function-declaration])

Your message dated Mon, 01 Apr 2024 18:19:50 +
with message-id 
and subject line Bug#1066266: fixed in bsdgames 2.17-31
has caused the Debian Bug report #1066266,
regarding bsdgames: FTBFS: hunt/hunt/otto.c:181:9: error: implicit declaration 
of function ‘sigpause’; did you mean ‘pause’? 
[-Werror=implicit-function-declaration]
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1066266: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066266
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: bsdgames
Version: 2.17-30
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240313 ftbfs-trixie ftbfs-impfuncdef

Hi,

During a rebuild of all packages in sid, your package failed to build
on amd64.

This is most likely caused by a change in dpkg 1.22.6, that enabled
-Werror=implicit-function-declaration. For more information, see
https://wiki.debian.org/qa.debian.org/FTBFS#A2024-03-13_-Werror.3Dimplicit-function-declaration

Relevant part (hopefully):
> x86_64-linux-gnu-gcc -g -O2 -Wall -W -Wstrict-prototypes -Wmissing-prototypes 
> -Wpointer-arith -Wcast-align -Wcast-qual -Wwrite-strings -g -O2 
> -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. 
> -fstack-protector-strong -fstack-clash-protection -Wformat 
> -Werror=format-security -fcf-protection -Wdate-time -D_FORTIFY_SOURCE=2   
> -Iinclude   -Imille  -c mille/extern.c -o mille/extern.o
> hunt/hunt/otto.c: In function ‘otto’:
> hunt/hunt/otto.c:179:9: warning: ‘sigblock’ is deprecated 
> [-Wdeprecated-declarations]
>   179 | old_mask = sigblock(sigmask(SIGALRM));
>   | ^~~~
> In file included from include/signal.h:40,
>  from hunt/hunt/otto.c:54:
> /usr/include/signal.h:173:12: note: declared here
>   173 | extern int sigblock (int __mask) __THROW __attribute_deprecated__;
>   |^~~~
> hunt/hunt/otto.c:179:20: warning: sigmask is deprecated
>   179 | old_mask = sigblock(sigmask(SIGALRM));
>   |^~~
> hunt/hunt/hunt.c: In function ‘main’:
> hunt/hunt/hunt.c:141:9: warning: ignoring return value of ‘setregid’ declared 
> with attribute ‘warn_unused_result’ [-Wunused-result]
>   141 | setregid(getgid(), getgid());
>   | ^~~~
> hunt/hunt/otto.c:181:9: error: implicit declaration of function ‘sigpause’; 
> did you mean ‘pause’? [-Werror=implicit-function-declaration]
>   181 | sigpause(old_mask);
>   | ^~~~
>   | pause
> hunt/hunt/otto.c:182:9: warning: ‘sigsetmask’ is deprecated 
> [-Wdeprecated-declarations]
>   182 | sigsetmask(old_mask);
>   | ^~
> /usr/include/signal.h:176:12: note: declared here
>   176 | extern int sigsetmask (int __mask) __THROW __attribute_deprecated__;
>   |^~
> hunt/hunt/hunt.c: In function ‘dump_scores’:
> hunt/hunt/hunt.c:678:17: warning: ignoring return value of ‘write’ declared 
> with attribute ‘warn_unused_result’ [-Wunused-result]
>   678 | write(fileno(stdout), buf, cnt);
>   | ^~~
> hunt/hunt/hunt.c: In function ‘intr’:
> hunt/hunt/hunt.c:852:40: warning: ignoring return value of ‘write’ declared 
> with attribute ‘warn_unused_result’ [-Wunused-result]
>   852 | (void) write(Socket, "q", 1);
>   |^
> hunt/hunt/otto.c:225:16: warning: ignoring return value of ‘write’ declared 
> with attribute ‘warn_unused_result’ [-Wunused-result]
>   225 | (void) write(Socket, command, comlen);
>   |^~
> mille/comp.c: In function ‘calcmove’:
> mille/comp.c:98:33: warning: increment of a boolean expression 
> [-Wbool-operation]
>98 | ++cango;
>   | ^~
> mille/comp.c:199:45: warning: decrement of a boolean expression 
> [-Wbool-operation]
>   199 | if (--cango <= 0)
>   | ^~
> hunt/hunt/playit.c: In function ‘send_stuff’:
> hunt/hunt/playit.c:292:24: warning: ignoring return value of ‘write’ declared 
> with attribute ‘warn_unused_result’ [-Wunused-result]
>   292 | (void) write(1, "\7", 1);   /* CTRL('G') */
>   |^
> hunt/hunt/playit.c:316:24: warning: ignoring return value of ‘write’

Bug#1028356: marked as done (procmail: Variable set with stdin pipe action fails leaving empty variable)

Your message dated Mon, 01 Apr 2024 18:04:18 +
with message-id 
and subject line Bug#1028356: fixed in procmail 3.24+really3.22-1
has caused the Debian Bug report #1028356,
regarding procmail: Variable set with stdin pipe action fails leaving empty 
variable
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1028356: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028356
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: procmail
Version: 3.24-1
Severity: normal

I am very happy to see procmail upstream is now active again!
Excellent news!  I am a long time user and have quite a few mail
filtering rules.

The recent upgrade to 3.24 broke using a pipe action to set a variable
using stdin.  Reverting to 3.22 restores correct functioning.

For example due to UTF-8 subject encoding one might find a subject
with this contrived and constructed example.

Subject: =?utf-8?q?test-list_post_from_rwp=40proulx=2Ecom_require?=
 =?utf-8?q?s_approval?=

I use the following idiomatic procmail expression to decode that
subject and place it into a SUBJECT variable.  This following from my
.procmailrc file.

# If the subject is encoded and needs decoding then...
#   extract the subject, decode it, store in the SUBJECT variable.
:0h
* ^Subject:.*=\?
SUBJECT=|formail -cXSubject: | perl -MEncode -pe 
'Encode::from_to($_,"MIME-Header","UTF-8");'

# Store all remaining cases of Subject: into $SUBJECT.
# E - only execute this recipe if previous recipe was not executed.
:0hE
SUBJECT=|formail -cXSubject:

# Here forward SUBJECT contains the decoded text.
# Match it using the variable ?? syntax.
# * SUBJECT ?? ^Subject: blah blah blah

Then I use it like this following to handle Mailman messages.

:0
* ^X-BeenThere:
* SUBJECT ?? ^Subject: .*mailing list memberships reminder$
mailman-reminders/

:0
* ^X-List-Administrivia: yes
{
  :0
  * 1^0 SUBJECT ?? ^Subject: Auto-discard notification
  * 1^0 SUBJECT ?? ^Subject: El envio a [-a-zA-Z0-9]+ 
de.*precisa.*de.*aprobacion
  * 1^0 SUBJECT ?? ^Subject: Uncaught bounce notification
  * 1^0 SUBJECT ?? ^Subject: [-a-zA-Z0-9]+ post from
  * 1^0 SUBJECT ?? ^Subject: [-a-zA-Z0-9]+ subscription notification
  * 1^0 SUBJECT ?? ^Subject: [-a-zA-Z0-9]+ unsubscribe notification
  list-administrivia/
}

Unfortunately in 3.24 this functionality is broken.  I see in the
Testing migration "excuses" this "Too young, only 4 of 5 days old".
Should severity be "important" in order to keep Testing from breaking?

Some experiments show to try to bound the condition.  It's around the
use of stdin to the sub-process.  This following works.  This does not
use stdin.

SUBJECT=|echo hello
SUBJECT=|echo hello | tee /tmp/pt.rwp.debug
SUBJECT=|sh -c "echo hello | tee /tmp/pt.rwp.debug"

But this fails.  (Using a cat| pipe to ensure $SHELLMETAS are seen.)
This fails to process stdin.

SUBJECT=|tee /tmp/pt.rwp.debug
SUBJECT=|cat | tee /tmp/pt.rwp.debug
SUBJECT=|sh -c "tee /tmp/pt.rwp.debug"
SUBJECT=|sh -c "cat | tee /tmp/pt.rwp.debug"

Thank you for maintaining procmail! :-)

Bob


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

Kernel: Linux 6.1.0-1-amd64 (SMP w/2 CPU threads; PREEMPT)
Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages procmail depends on:
ii  libc6  2.36-8

Versions of packages procmail recommends:
ii  postfix [mail-transport-agent]  3.7.3-2+b1

procmail suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: procmail
Source-Version: 3.24+really3.22-1
Done: Santiago Vila 

We believe that the bug you reported is fixed in the latest version of
procmail, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1028...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Santiago Vila  (supplier of updated procmail package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)

Bug#1028356: procmail: Variable set with stdin pipe action fails leaving empty variable

2024-04-01 Thread Santiago Vila


Hi.

I have just reuploaded version 3.22.

This is certainly not the ideal state for this ancient
package, but I believe it's slightly better than keeping
an important regression forever.

If upstream decides to maintain procmail again (which means
addressing regressions, not merely making a new release),
it could make sense to consider the switch again.

I was about to write all this in the Debian changelog, but this
place is probably more appropriate.

Thanks a lot.

Bug#1062170: marked as done (glw: NMU diff for 64-bit time_t transition)

Your message dated Mon, 01 Apr 2024 18:00:11 +
with message-id 
and subject line Bug#1062170: fixed in glw 8.0.0-3
has caused the Debian Bug report #1062170,
regarding glw: NMU diff for 64-bit time_t transition
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1062170: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1062170
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: glw
Version: 8.0.0-1.1
Severity: serious
Tags: patch pending
Justification: library ABI skew on upgrade
User: debian-...@lists.debian.org
Usertags: time-t

Dear maintainer,

As part of the 64-bit time_t transition required to support 32-bit
architectures in 2038 and beyond
(https://wiki.debian.org/ReleaseGoals/64bit-time), we have identified
glw as a source package shipping runtime libraries whose ABI
either is affected by the change in size of time_t, or could not be
analyzed via abi-compliance-checker (and therefore to be on the safe
side we assume is affected).

To ensure that inconsistent combinations of libraries with their
reverse-dependencies are never installed together, it is necessary to
have a library transition, which is most easily done by renaming the
runtime library package.

Since turning on 64-bit time_t is being handled centrally through a change
to the default dpkg-buildflags (https://bugs.debian.org/1037136), it is
important that libraries affected by this ABI change all be uploaded close
together in time.  Therefore I have prepared a 0-day NMU for glw
which will initially be uploaded to experimental if possible, then to
unstable after packages have cleared binary NEW.

Please find the patch for this NMU attached.

If you have any concerns about this patch, please reach out ASAP.  Although
this package will be uploaded to experimental immediately, there will be a
period of several days before we begin uploads to unstable; so if information
becomes available that your package should not be included in the transition,
there is time for us to amend the planned uploads.



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

Kernel: Linux 6.5.0-14-generic (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
diff -u glw-8.0.0/debian/changelog glw-8.0.0/debian/changelog
--- glw-8.0.0/debian/changelog
+++ glw-8.0.0/debian/changelog
@@ -1,3 +1,10 @@
+glw (8.0.0-1.2) experimental; urgency=medium
+
+  * Non-maintainer upload.
+  * Rename libraries for 64-bit time_t transition.
+
+ -- Lukas Märdian   Wed, 31 Jan 2024 14:53:50 +
+
 glw (8.0.0-1.1) unstable; urgency=low
 
   [ Paul Gevers ]
diff -u glw-8.0.0/debian/control glw-8.0.0/debian/control
--- glw-8.0.0/debian/control
+++ glw-8.0.0/debian/control
@@ -19,11 +19,13 @@
 Homepage: http://mesa3d.sourceforge.net/
 
 Package: libglw1-mesa
+Replaces: libglw1-mesa
+Breaks: libglw1-mesa (<< ${source:Version})
 Architecture: any
 Depends:
  ${shlibs:Depends},
  ${misc:Depends},
-Provides: libglw1
+Provides: libglw1, ${t64:Provides}
 Pre-Depends: ${misc:Pre-Depends}
 Multi-Arch: same
 Description: GL widget library for Athena and Motif -- runtime
--- End Message ---
--- Begin Message ---
Source: glw
Source-Version: 8.0.0-3
Done: Julien Cristau 

We believe that the bug you reported is fixed in the latest version of
glw, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1062...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Julien Cristau  (supplier of updated glw package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 31 Mar 2024 13:00:14 +0200
Source: glw
Binary: libglw1-mesa-dev libglw1t64-mesa libglw1t64-mesa-dbgsym
Architecture: source amd64
Version: 8.0.0-3
Distribution: unstable
Urgency: medium
Maintainer: Debian X Strike Force 
Changed-By: Julien Cristau 
Description:
 libglw1-mesa-dev - GL widget library for Athena and Motif -- development files
 libglw1t64-mesa - GL widget

Bug#1068198: debian-installer-netboot-images: accesses the internet during build

2024-04-01 Thread Aurelien Jarno

Source: debian-installer-netboot-images
Severity: serious
Justification: Policy 4.9
X-Debbugs-Cc: d...@debian.org, wb-t...@buildd.debian.org
Control: affects -1 buildd.debian.org

Hi,

debian-installer-netboot-images attemps network access during build,
although only to the mirrors listed in /etc/apt/sources.list and in a
secure way. This is forbidden by Policy 4.9:

  For packages in the main archive, required targets must not attempt
  network access, except, via the loopback interface, to services on the
  build host that have been started by the build.

In addition this brings constraints to the build daemons infrastructure.

Regards,
Aurelien

Processed: debian-installer-netboot-images: accesses the internet during build

Processing control commands:

> affects -1 buildd.debian.org
Bug #1068198 [src:debian-installer-netboot-images] 
debian-installer-netboot-images: accesses the internet during build
Added indication that 1068198 affects buildd.debian.org

-- 
1068198: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068198
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1068140: polymake: FTBFS: dpkg-shlibdeps: error: no dependency information found for /lib/x86_64-linux-gnu/libflint.so.19 (used by debian/libpolymake4.11/usr/lib/libpolymake.so.4.11)

2024-04-01 Thread David Bremner

Sebastian Ramacher  writes:

> Control: affects -1 src:polymake
>
[...]
> Let's make sure that it is visible for polymake then. Otherwise I'll
> file it a third time ;)

Thanks, I thought to myself at some point this morning it should have
affects, and then, well, I didn't do it.

many hands make light-er work, I guess

David

Bug#1068188: pthread_cond_init.3.gz: conflict with manpages-dev 6.7-1

2024-04-01 Thread Sven Joachim

On 2024-04-01 19:02 +0200, Alejandro Colomar wrote:

> Hi Sven,
>
> On Mon, Apr 01, 2024 at 06:38:52PM +0200, Sven Joachim wrote:
>> Makes perfect sense, but at the moment it can only be uploaded to
>> experimental.
>>
>> > We're not in a freeze, so I guess that's fair game.
>>
>> We're not in a freeze but in the middle of the largest transition in
>> Debian history[1], and during that a new major glibc version in unstable is
>> out of the question.
>>
>> >> files for now and re-include either when glibc 2.38 is in unstable or
>> >> when it is in testing.
>> >
>> > Why do we need to wait to ask for a glibc-doc_2.38-7 with the patch
>> > dropped?  Does 2.38 have any freeze at the moment?
>>
>> Yes.  Every new major glibc version requires a transition (requiring
>> rebuilds of all packages which use @GLIBC_PRIVATE symbols, among other
>> things), and the one for glibc 2.38[2] has been pending for three
>> months[3].
>
> Hmmm, I understand.  If you want to temporarily drop these pages from
> manpages-dev, go ahead.  Please undrop them when glibc-doc can make a
> new release.  BTW, I guess glibc-doc must match libc6 version?

It is built from the same source package, so yes.

Cheers,
   Sven

Bug#1068188: pthread_cond_init.3.gz: conflict with manpages-dev 6.7-1

Hi Sven,

On Mon, Apr 01, 2024 at 06:38:52PM +0200, Sven Joachim wrote:
> Makes perfect sense, but at the moment it can only be uploaded to
> experimental.
> 
> > We're not in a freeze, so I guess that's fair game.
> 
> We're not in a freeze but in the middle of the largest transition in
> Debian history[1], and during that a new major glibc version in unstable is
> out of the question.
> 
> >> files for now and re-include either when glibc 2.38 is in unstable or
> >> when it is in testing.
> >
> > Why do we need to wait to ask for a glibc-doc_2.38-7 with the patch
> > dropped?  Does 2.38 have any freeze at the moment?
> 
> Yes.  Every new major glibc version requires a transition (requiring
> rebuilds of all packages which use @GLIBC_PRIVATE symbols, among other
> things), and the one for glibc 2.38[2] has been pending for three
> months[3].

Hmmm, I understand.  If you want to temporarily drop these pages from
manpages-dev, go ahead.  Please undrop them when glibc-doc can make a
new release.  BTW, I guess glibc-doc must match libc6 version?
Otherwise, you could have a more recent glibc-doc that drops these pages
without upgrading libc6.  Are documentation changes frozen in such a
transition?

> 
> >> There is also the problem that some derivatives (most notably Ubuntu)
> >> are already shipping glibc 2.39 and will have to adjust Breaks/Replaces
> >> versions in manpages-dev accordingly.
> >
> > Hmmm.  I suggest they patch glibc-doc to remove those manual pages.
> > They have been unsupported for a long time.  The last change in
> > glibc-doc is from 2013.
> 
> I guess Ubuntu can then drop the glibc-doc package entirely, as they do
> not ship the upstream changelogs in it, and after dropping the pthread_*
> manpages the package would be empty.  TBH, I do not see much value in
> these changelogs and will probably uninstall glibc-doc from my systems.

Good.

Have a lovely day!
Alex

> 
> Cheers,
>Sven
> 
> 
> 1. https://lists.debian.org/debian-devel-announce/2024/02/msg5.html
> 2. https://release.debian.org/transitions/html/glibc-2.38.html
> 3. https://bugs.debian.org/1059852

-- 

Looking for a remote C programming job at the moment.


signature.asc
Description: PGP signature

Processed: debian-installer: accesses the internet during build

Processing control commands:

> affects -1 buildd.debian.org
Bug #1068197 [src:debian-installer] debian-installer: accesses the internet 
during build
Added indication that 1068197 affects buildd.debian.org

-- 
1068197: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068197
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1068197: debian-installer: accesses the internet during build

2024-04-01 Thread Aurelien Jarno

Source: debian-installer
Severity: serious
Justification: Policy 4.9
X-Debbugs-Cc: d...@debian.org, wb-t...@buildd.debian.org
Control: affects -1 buildd.debian.org

Hi,

debian-installer attemps network access during build, although only to
the mirrors listed in /etc/apt/sources.list and in a secure way. This is
forbidden by Policy 4.9:

  For packages in the main archive, required targets must not attempt
  network access, except, via the loopback interface, to services on the
  build host that have been started by the build.

In addition this brings constraints to the build daemons infrastructure.

Regards,
Aurelien

Bug#1068188: pthread_cond_init.3.gz: conflict with manpages-dev 6.7-1

2024-04-01 Thread Sven Joachim

On 2024-04-01 18:00 +0200, Alejandro Colomar wrote:

> Hi Sven,
>
> On Mon, Apr 01, 2024 at 05:35:18PM +0200, Sven Joachim wrote:
>> Obviously the manpages-dev package should not have shipped these files
>> as long as there are in glibc-doc; this is tracked in #1068166.
>
> I CCed back in 2023-10 the debian-glibc@ list notifying that these pages
> were absorbed into the Linux man-pages project.  They didn't respond.

Thanks.  That might have fallen through the cracks.

>> Adding a Breaks on glibc-doc (<= 2.38-6) to manpages-dev is no good,
>> because that version is only in experimental and will remain there for
>> several weeks if not months.  I think manpages-dev should drop these
>
> Why not add glibc-doc 2.38-7 dropping the patch that adds these pages?

Makes perfect sense, but at the moment it can only be uploaded to
experimental.

> We're not in a freeze, so I guess that's fair game.

We're not in a freeze but in the middle of the largest transition in
Debian history[1], and during that a new major glibc version in unstable is
out of the question.

>> files for now and re-include either when glibc 2.38 is in unstable or
>> when it is in testing.
>
> Why do we need to wait to ask for a glibc-doc_2.38-7 with the patch
> dropped?  Does 2.38 have any freeze at the moment?

Yes.  Every new major glibc version requires a transition (requiring
rebuilds of all packages which use @GLIBC_PRIVATE symbols, among other
things), and the one for glibc 2.38[2] has been pending for three
months[3].

>> There is also the problem that some derivatives (most notably Ubuntu)
>> are already shipping glibc 2.39 and will have to adjust Breaks/Replaces
>> versions in manpages-dev accordingly.
>
> Hmmm.  I suggest they patch glibc-doc to remove those manual pages.
> They have been unsupported for a long time.  The last change in
> glibc-doc is from 2013.

I guess Ubuntu can then drop the glibc-doc package entirely, as they do
not ship the upstream changelogs in it, and after dropping the pthread_*
manpages the package would be empty.  TBH, I do not see much value in
these changelogs and will probably uninstall glibc-doc from my systems.

Cheers,
   Sven

1. https://lists.debian.org/debian-devel-announce/2024/02/msg5.html
2. https://release.debian.org/transitions/html/glibc-2.38.html
3. https://bugs.debian.org/1059852

Bug#1054484: marked as done (varnish: installs varnish.service twice once dh_installsystemd installs to /usr)

Your message dated Mon, 01 Apr 2024 16:25:46 +
with message-id 
and subject line Bug#1054484: fixed in varnish 7.1.1-1.2
has caused the Debian Bug report #1054484,
regarding varnish: installs varnish.service twice once dh_installsystemd 
installs to /usr
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1054484: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054484
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: varnish
Version: 7.1.1-1.1
Severity: normal
Tags: patch
User: helm...@debian.org
Usertags: dep17m2

We want to modify dh_installsystemd such that it installs units below
/usr in order to finalize the /usr-merge transition via DEP17. When
doing so, varnish.service is being installed to both /lib (via
dh_install) and /usr/lib (via dh_installsystemd). Such behaviour
constitutes a policy violation and therefore this bug will become
release-critical once I upload debhelper. In the attached patch, I also
change the way varnishncsa.service is installed to allow
dh_installsystemd to choose its location. Therefore, varnish will
hopefully not need any other changes for the /usr-merge.

Helmut
diff -Nru varnish-7.1.1/debian/changelog varnish-7.1.1/debian/changelog
--- varnish-7.1.1/debian/changelog  2023-01-09 22:09:31.0 +0100
+++ varnish-7.1.1/debian/changelog  2023-10-24 12:33:34.0 +0200
@@ -1,3 +1,10 @@
+varnish (7.1.1-1.2) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Install systemd units using dh_installsystemd only. (Closes: #-1)
+
+ -- Helmut Grohne   Tue, 24 Oct 2023 12:33:34 +0200
+
 varnish (7.1.1-1.1) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -Nru varnish-7.1.1/debian/rules varnish-7.1.1/debian/rules
--- varnish-7.1.1/debian/rules  2023-01-09 21:59:22.0 +0100
+++ varnish-7.1.1/debian/rules  2023-10-24 12:32:17.0 +0200
@@ -105,6 +105,9 @@
dh_installinit --name=varnishlog
dh_installinit --name=varnishncsa
 
+execute_after_dh_installsystemd:
+   dh_installsystemd --package=varnish --name=varnishncsa
+
 override_dh_makeshlibs:
dh_makeshlibs -VUpstream-Version
 
diff -Nru varnish-7.1.1/debian/varnish.install 
varnish-7.1.1/debian/varnish.install
--- varnish-7.1.1/debian/varnish.install2023-01-09 21:59:22.0 
+0100
+++ varnish-7.1.1/debian/varnish.install2023-10-24 12:33:28.0 
+0200
@@ -4,4 +4,3 @@
 usr/lib/*/varnish
 usr/share/man
 usr/share/varnish/vcl
-debian/*.service lib/systemd/system/
diff -Nru varnish-7.1.1/debian/varnish.varnishncsa.service 
varnish-7.1.1/debian/varnish.varnishncsa.service
--- varnish-7.1.1/debian/varnish.varnishncsa.service1970-01-01 
01:00:00.0 +0100
+++ varnish-7.1.1/debian/varnish.varnishncsa.service2023-01-09 
21:59:22.0 +0100
@@ -0,0 +1,20 @@
+[Unit]
+Description=Varnish HTTP accelerator log daemon
+Documentation=https://www.varnish-cache.org/docs/6.1/ man:varnishncsa
+After=varnish.service
+
+[Service]
+Type=forking
+PIDFile=/run/varnishncsa/varnishncsa.pid
+RuntimeDirectory=varnishncsa
+User=varnishlog
+Group=varnish
+ExecStart=/usr/bin/varnishncsa -a -w /var/log/varnish/varnishncsa.log -D -P 
/run/varnishncsa/varnishncsa.pid
+ExecReload=/bin/kill -HUP $MAINPID
+PrivateDevices=true
+PrivateTmp=true
+ProtectHome=true
+ProtectSystem=full
+
+[Install]
+WantedBy=multi-user.target
diff -Nru varnish-7.1.1/debian/varnishncsa.service 
varnish-7.1.1/debian/varnishncsa.service
--- varnish-7.1.1/debian/varnishncsa.service2023-01-09 21:59:22.0 
+0100
+++ varnish-7.1.1/debian/varnishncsa.service1970-01-01 01:00:00.0 
+0100
@@ -1,20 +0,0 @@
-[Unit]
-Description=Varnish HTTP accelerator log daemon
-Documentation=https://www.varnish-cache.org/docs/6.1/ man:varnishncsa
-After=varnish.service
-
-[Service]
-Type=forking
-PIDFile=/run/varnishncsa/varnishncsa.pid
-RuntimeDirectory=varnishncsa
-User=varnishlog
-Group=varnish
-ExecStart=/usr/bin/varnishncsa -a -w /var/log/varnish/varnishncsa.log -D -P 
/run/varnishncsa/varnishncsa.pid
-ExecReload=/bin/kill -HUP $MAINPID
-PrivateDevices=true
-PrivateTmp=true
-ProtectHome=true
-ProtectSystem=full
-
-[Install]
-WantedBy=multi-user.target
--- End Message ---
--- Begin Message ---
Source: varnish
Source-Version: 7.1.1-1.2
Done: Marco d'Itri 

We believe that the bug you reported is fixed in the latest version of
varnish, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have

Bug#1067293: marked as done (singular: FTBFS: cfModGcd.cc:1809:37: error: cannot convert ‘fq_nmod_ctx_struct’ to ‘const fq_nmod_mat_struct’)

Your message dated Mon, 01 Apr 2024 16:07:24 +
with message-id 
and subject line Bug#1067293: fixed in singular 1:4.3.2-p16+ds-1~exp1
has caused the Debian Bug report #1067293,
regarding singular: FTBFS: cfModGcd.cc:1809:37: error: cannot convert 
‘fq_nmod_ctx_struct*’ to ‘const fq_nmod_mat_struct*’
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1067293: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067293
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: singular
Version: 1:4.3.2-p10+ds-1.1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240319 ftbfs-trixie

Hi,

During a rebuild of all packages in sid, your package failed to build
on amd64.


Relevant part (hopefully):
> /bin/bash ./libtool  --tag=CXX   --mode=compile g++ -DHAVE_CONFIG_H -I.  
> -I./include -I./include -I. -DFACTORY_BUILDING_DLL -I/<> 
> -I/<>  -DSING_NDEBUG -DOM_NDEBUG -Wdate-time 
> -D_FORTIFY_SOURCE=2  -g -O2 -ffile-prefix-map=/<>=. 
> -fstack-protector-strong -fstack-clash-protection -Wformat 
> -Werror=format-security -fcf-protection -pipe -fno-common -O3 
> -Wno-unused-function -Wno-trigraphs -Wno-unused-parameter -Wunknown-pragmas 
> -Wno-unused-variable -fomit-frame-pointer -fwrapv -fvisibility=default 
> -finline-functions -fno-exceptions -fno-threadsafe-statics 
> -fno-enforce-eh-specs -fconserve-space -funroll-loops -fno-rtti -c -o 
> cf_ops.lo cf_ops.cc
> cfModGcd.cc: In function ‘long int gaussianElimFq(CFMatrix&, CFArray&, const 
> Variable&)’:
> cfModGcd.cc:1809:37: error: cannot convert ‘fq_nmod_ctx_struct*’ to ‘const 
> fq_nmod_mat_struct*’
>  1809 |   long rk= fq_nmod_mat_rref (FLINTN,ctx);
>   | ^~~
>   | |
>   | fq_nmod_ctx_struct*
> In file included from /usr/include/flint/fq_nmod_mat.h:36,
>  from FLINTconvert.h:42,
>  from cfModGcd.cc:53:
> /usr/include/flint/fq_mat_templates.h:247:76: note:   initializing argument 2 
> of ‘mp_limb_signed_t fq_nmod_mat_rref(fq_nmod_mat_struct*, const 
> fq_nmod_mat_struct*, const fq_nmod_ctx_struct*)’
>   247 | slong TEMPLATE(T, mat_rref)(TEMPLATE(T, mat_t) B, const TEMPLATE(T, 
> mat_t) A, const TEMPLATE(T, ctx_t) ctx);
>   |   
> ~^
> cfModGcd.cc: In function ‘CFArray solveSystemFq(const CFMatrix&, const 
> CFArray&, const Variable&)’:
> cfModGcd.cc:1916:37: error: cannot convert ‘fq_nmod_ctx_struct*’ to ‘const 
> fq_nmod_mat_struct*’
>  1916 |   long rk= fq_nmod_mat_rref (FLINTN,ctx);
>   | ^~~
>   | |
>   | fq_nmod_ctx_struct*
> /usr/include/flint/fq_mat_templates.h:247:76: note:   initializing argument 2 
> of ‘mp_limb_signed_t fq_nmod_mat_rref(fq_nmod_mat_struct*, const 
> fq_nmod_mat_struct*, const fq_nmod_ctx_struct*)’
>   247 | slong TEMPLATE(T, mat_rref)(TEMPLATE(T, mat_t) B, const TEMPLATE(T, 
> mat_t) A, const TEMPLATE(T, ctx_t) ctx);
>   |   
> ~^
> libtool: compile:  g++ -DHAVE_CONFIG_H -I. -I./include -I./include -I. 
> -DFACTORY_BUILDING_DLL -I/<> -I/<> -DSING_NDEBUG 
> -DOM_NDEBUG -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 
> -ffile-prefix-map=/<>=. -fstack-protector-strong 
> -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection 
> -pipe -fno-common -O3 -Wno-unused-function -Wno-trigraphs 
> -Wno-unused-parameter -Wunknown-pragmas -Wno-unused-variable 
> -fomit-frame-pointer -fwrapv -fvisibility=default -finline-functions 
> -fno-exceptions -fno-threadsafe-statics -fno-enforce-eh-specs 
> -fconserve-space -funroll-loops -fno-rtti -c cf_ops.cc  -fPIC -DPIC -o 
> .libs/cf_ops.o
> /bin/bash ./libtool  --tag=CXX   --mode=compile g++ -DHAVE_CONFIG_H -I.  
> -I./include -I./include -I. -DFACTORY_BUILDING_DLL -I/<> 
> -I/<>  -DSING_NDEBUG -DOM_NDEBUG -Wdate-time 
> -D_FORTIFY_SOURCE=2  -g -O2 -ffile-prefix-map=/<>=. 
> -fstack-protector-strong -fstack-clash-protection -Wformat 
> -Werror=format-security -fcf-protection -pipe -fno-common -O3 
> -Wno-unused-function -Wno-trigraphs -Wno-unused-parameter -Wunknown-pragmas 
> -Wno-unused-variable -fomit-frame-pointer -fwrapv -fvisibility=default 
> -finline-functions -fno-exceptions -fno-threadsafe-statics 
> -fno-enforce-eh-specs -fconserve-space -funroll-loops -fno-rtti -c -o 
> cf_primes.lo

Bug#1067450: Not a bug, can be closed

2024-04-01 Thread Daniel Huhardeaux

The encoured error is due to a mix of ttyd from unstable with 
libwebsockets17 from bookworm.


--
Daniel

Bug#1068188: pthread_cond_init.3.gz: conflict with manpages-dev 6.7-1

Hi Sven,

On Mon, Apr 01, 2024 at 05:35:18PM +0200, Sven Joachim wrote:
> Obviously the manpages-dev package should not have shipped these files
> as long as there are in glibc-doc; this is tracked in #1068166.

I CCed back in 2023-10 the debian-glibc@ list notifying that these pages
were absorbed into the Linux man-pages project.  They didn't respond.

However, the original author of the pages talked to me, agreeing to
that.  Other glibc upstream maintainers also participated in the thread.

> 
> > Please, remove from glibc-doc those manual pages that conflict with
> > manpages-dev.
> 
> Considering that the manpages in glibc-doc are not included upstream and

The history is a bit more complex than that.  They were originally
written upstream.  Then glibc removed them.  A decade later, Debian
added them back via a patch, with some modifications.  I noted down the
history in the discussion linked above.

> created via a Debian patch, that makes a lot of sense.  I was not aware
> of that fact.
> 
> > Marcos, you'll also need to specify a breaks with glibc-doc versions
> > up to (and including) 6.38-6 in the next revision of manpages-dev, and
> > drop 6.7-1.
> 
> Adding a Breaks on glibc-doc (<= 2.38-6) to manpages-dev is no good,
> because that version is only in experimental and will remain there for
> several weeks if not months.  I think manpages-dev should drop these

Why not add glibc-doc 2.38-7 dropping the patch that adds these pages?
We're not in a freeze, so I guess that's fair game.

> files for now and re-include either when glibc 2.38 is in unstable or
> when it is in testing.

Why do we need to wait to ask for a glibc-doc_2.38-7 with the patch
dropped?  Does 2.38 have any freeze at the moment?

> There is also the problem that some derivatives (most notably Ubuntu)
> are already shipping glibc 2.39 and will have to adjust Breaks/Replaces
> versions in manpages-dev accordingly.

Hmmm.  I suggest they patch glibc-doc to remove those manual pages.
They have been unsupported for a long time.  The last change in
glibc-doc is from 2013.

> Thoughts?
> 
> Cheers,
>Sven

Have a lovely day!
Alex

-- 

Looking for a remote C programming job at the moment.

signature.asc
Description: PGP signature

Bug#1068194: pcsx2: FTBFS: /<>/plugins/cdvdGigaherz/src/CDVD.cpp:143:19: error: ‘system_error’ in namespace ‘std’ does not name a type

Source: pcsx2
Version: 1.6.0+dfsg-2
Severity: serious
Tags: ftbfs
Justification: fails to build from source
X-Debbugs-Cc: sramac...@debian.org

https://buildd.debian.org/status/fetch.php?pkg=pcsx2=i386=1.6.0%2Bdfsg-2%2Bb10=1711729892=0

[  7%] Generating ../tr_TR__pcsx2_Main.gmo
cd /<>/obj-i686-linux-gnu/locales && /usr/bin/msgmerge --quiet 
--update --backup=none -s /<>/locales/tr_TR/pcsx2_Main.po 
/<>/locales/templates/pcsx2_Main.pot
/<>/plugins/cdvdGigaherz/src/CDVD.cpp: In function ‘bool 
StartKeepAliveThread()’:
/<>/plugins/cdvdGigaherz/src/CDVD.cpp:143:19: error: 
‘system_error’ in namespace ‘std’ does not name a type
  143 | } catch (std::system_error &) {
  |   ^~~~
/<>/plugins/cdvdGigaherz/src/CDVD.cpp: In function ‘s32 
CDVDopen(const char*)’:
/<>/plugins/cdvdGigaherz/src/CDVD.cpp:188:19: error: 
‘runtime_error’ in namespace ‘std’ does not name a type
  188 | } catch (std::runtime_error ) {
  |   ^
/<>/plugins/cdvdGigaherz/src/CDVD.cpp:22:1: note: 
‘std::runtime_error’ is defined in header ‘’; did you forget to 
‘#include ’?
   21 | #include "svnrev.h"
  +++ |+#include 
   22 | 
cd /<>/obj-i686-linux-gnu/locales && /usr/bin/msgfmt -o 
/<>/obj-i686-linux-gnu/tr_TR__pcsx2_Main.gmo 
/<>/locales/tr_TR/pcsx2_Main.po
/<>/plugins/cdvdGigaherz/src/CDVD.cpp:189:15: error: ‘ex’ was not 
declared in this scope
  189 | fputs(ex.what(), stdout);
  |   ^~
[  8%] Generating ../zh_CN__pcsx2_Main.gmo
cd /<>/obj-i686-linux-gnu/locales && /usr/bin/msgmerge --quiet 
--update --backup=none -s /<>/locales/zh_CN/pcsx2_Main.po 
/<>/locales/templates/pcsx2_Main.pot
cd /<>/obj-i686-linux-gnu/locales && /usr/bin/msgfmt -o 
/<>/obj-i686-linux-gnu/zh_CN__pcsx2_Main.gmo 
/<>/locales/zh_CN/pcsx2_Main.po
[  8%] Generating ../zh_TW__pcsx2_Main.gmo
cd /<>/obj-i686-linux-gnu/locales && /usr/bin/msgmerge --quiet 
--update --backup=none -s /<>/locales/zh_TW/pcsx2_Main.po 
/<>/locales/templates/pcsx2_Main.pot
make[3]: *** 
[plugins/cdvdGigaherz/src/CMakeFiles/cdvdGigaherz.dir/build.make:79: 
plugins/cdvdGigaherz/src/CMakeFiles/cdvdGigaherz.dir/CDVD.cpp.o] Error 1

Cheers
-- 
Sebastian Ramacher

Bug#1068188: pthread_cond_init.3.gz: conflict with manpages-dev 6.7-1

2024-04-01 Thread Sven Joachim

On 2024-04-01 16:23 +0200, Alejandro Colomar wrote:

> Package: glibc-doc
> Version: 2.38-6
> Severity: serious
> Justification: Policy 7.4
> X-Debbugs-Cc: a...@kernel.org, mar...@debian.org
>
> Dear Maintainer,
>
> The Linux man-pages project has recently added the pthread_*(3) manual
> pages that were provided by glibc-doc.  The first upstream version of
> the Linux man-pages that includes these pages is man-pages-6.06.  Here's
> what was added:
>
>   $ git diff --stat b06cd070f..128a3ae35
>man3/pthread_cond_init.3| 264 
>man3/pthread_condattr_init.3|  48 
>man3/pthread_key_create.3   | 178 +
>man3/pthread_mutex_init.3   | 241 ++
>man3/pthread_mutexattr_setkind_np.3 |  52 
>man3/pthread_once.3 |  44 
>6 files changed, 827 insertions(+)
>
> Debian's manpages-dev_6.7-1_all.deb has been the first package since
> that happened, and I've noticed that dpkg(1) (via apt-get(8)) refuses to
> upgrade manpages-dev due to a conflict with glibc-doc.

>   $ sudo apt-get upgrade -V;
>   [...]
>   Do you want to continue? [Y/n] y
>   Reading changelogs... Done
>   (Reading database ... 404853 files and directories currently installed.)
>   Preparing to unpack .../manpages-dev_6.7-1_all.deb ...
>   Unpacking manpages-dev (6.7-1) over (6.05.01-1) ...
>   dpkg: error processing archive 
> /var/cache/apt/archives/manpages-dev_6.7-1_all.deb (--unpack):
>trying to overwrite '/usr/share/man/man3/pthread_cond_init.3.gz', 
> which is also in package glibc-doc 2.38-6
>   Errors were encountered while processing:
>/var/cache/apt/archives/manpages-dev_6.7-1_all.deb
>   needrestart is being skipped since dpkg has failed
>   E: Sub-process /usr/bin/dpkg returned an error code (1)

Obviously the manpages-dev package should not have shipped these files
as long as there are in glibc-doc; this is tracked in #1068166.

> Please, remove from glibc-doc those manual pages that conflict with
> manpages-dev.

Considering that the manpages in glibc-doc are not included upstream and
created via a Debian patch, that makes a lot of sense.  I was not aware
of that fact.

> Marcos, you'll also need to specify a breaks with glibc-doc versions
> up to (and including) 6.38-6 in the next revision of manpages-dev, and
> drop 6.7-1.

Adding a Breaks on glibc-doc (<= 2.38-6) to manpages-dev is no good,
because that version is only in experimental and will remain there for
several weeks if not months.  I think manpages-dev should drop these
files for now and re-include either when glibc 2.38 is in unstable or
when it is in testing.

There is also the problem that some derivatives (most notably Ubuntu)
are already shipping glibc 2.39 and will have to adjust Breaks/Replaces
versions in manpages-dev accordingly.  Thoughts?

Cheers,
   Sven

Bug#1068189: debhelper: --link-doc checking for known packages makes linux-signed build FTBFS

2024-04-01 Thread Niels Thykier

Salvatore Bonaccorso:

Source: debhelper
Version: 13.15
Severity: serious
Tags: ftbfs
Justification: Regression for other package builds, FTBFS
X-Debbugs-Cc: car...@debian.org,debian-ker...@lists.debian.org
Control: affects -1 + src:linux,src:linux-signed-amd64,src:linux-signed-arm64

Hi Niels,

Not fully investigated, but starting to fill a bugreport. I noticed
that the src:linux pipeline on salsa started to fail for the
jobs in th build-signed stage (in the build-signed job).

https://salsa.debian.org/carnil/linux/-/jobs/5527774

(and for saving the output):

[...]

(attached as well the raw log)

I'm not 100% sure yet, this might be a problem in our packaging in
which case we can re-eassign. But it only got triggered with the
change recently in debhelper:

https://salsa.debian.org/debian/debhelper/-/commit/dec5cfad00e2abd9ee3594f90c93f3fa42bb73ff

Regards,
Salvatore

Hi Salvatore

It was a suggestion raised (I think on IRC) to have debhelper explicitly
check these parameters, because a lot of t64 breakage was "unnoticed" by
debhelper. That is, when people forgot to update --link-doc parameters
(etc.).

The code for `--link-doc` uses `${binary:Version}` for the dependency,
so the package should really be from the same source[1]. In my view, it
was never a case that was expected to work between source packages.

I think `linux` with `linux-signed` is doing something really special
here (especially considering it has worked so far), and I think the
question is whether `linux`/`linux-signed` should get a special-case or
concluding that the `--link-doc` is not suitable for the
`linux`/`linux-signed` case.

I would like to hear your case for what makes `--link-doc` sensible for
the `linux-signed` case. I know of `linux-signed`, but I have no idea
what you are dealing with in practice, so it is hard for me to make a
judgement call on this (other than my biased gut feeling of wanting to
minimize special-cases).

Best regards,
Niels

[1]: Policy also documents the "same source" requirement.

https://www.debian.org/doc/debian-policy/ch-docs.html#copyright-information

Processed: your mail

Processing commands for cont...@bugs.debian.org:

> forwarded 1068146 https://github.com/dipy/dipy/issues/3165
Bug #1068146 [src:dipy] FTBFS: tests failed
Set Bug forwarded-to-address to 'https://github.com/dipy/dipy/issues/3165'.
>
End of message, stopping processing here.

Please contact me if you need assistance.
-- 
1068146: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068146
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: Re: Bug#1056156: varnish: CVE-2023-44487: VSV00013 Varnish HTTP/2 Rapid Reset Attack

Processing control commands:

> found -1 5.0.0-1
Bug #1056156 [src:varnish] varnish: CVE-2023-44487: VSV00013 Varnish HTTP/2 
Rapid Reset Attack
Marked as found in versions varnish/5.0.0-1.
> fixed -1 7.4.2
Bug #1056156 [src:varnish] varnish: CVE-2023-44487: VSV00013 Varnish HTTP/2 
Rapid Reset Attack
The source 'varnish' and version '7.4.2' do not appear to match any binary 
packages
Marked as fixed in versions varnish/7.4.2.

-- 
1056156: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056156
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1056156: varnish: CVE-2023-44487: VSV00013 Varnish HTTP/2 Rapid Reset Attack

2024-04-01 Thread Marco d'Itri

Control: found -1 5.0.0-1
Control: fixed -1 7.4.2

On Nov 17, Salvatore Bonaccorso  wrote:

> CVE-2023-44487[0]:
> | The HTTP/2 protocol allows a denial of service (server resource
> | consumption) because request cancellation can reset many streams
> | quickly, as exploited in the wild in August through October 2023.
Fixing this issue would require backporting a significant amount of 
new features in varnish and I do not believe that it would be practical.

I am inclined to downgrade this bug because:
- this is just a DoS attack
- it only concerns people using hitch for TLS termination instead of 
  a full web server like nginx or haproxy

nginx in stable is also vulnerable, BTW.

-- 
ciao,
Marco


signature.asc
Description: PGP signature

Processed: fixed 1068187 in 0.37.0-2

Processing commands for cont...@bugs.debian.org:

> fixed 1068187 0.37.0-2
Bug #1068187 [phosh] Session fails to start with gnome-session >= 46
Marked as fixed in versions phosh/0.37.0-2.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1068187: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068187
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: found 1068187 in 0.37.0-1

Processing commands for cont...@bugs.debian.org:

> found 1068187 0.37.0-1
Bug #1068187 {Done: Guido Günther } [phosh] Session fails to 
start with gnome-session >= 46
Marked as found in versions phosh/0.37.0-1 and reopened.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1068187: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068187
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: fixed 1068187 in 0.37.1

Processing commands for cont...@bugs.debian.org:

> fixed 1068187 0.37.1
Bug #1068187 [phosh] Session fails to start with gnome-session >= 46
There is no source info for the package 'phosh' at version '0.37.1' with 
architecture ''
Unable to make a source version for version '0.37.1'
Marked as fixed in versions 0.37.1.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1068187: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068187
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1068188: glibc-doc: pthread_cond_init.3.gz: conflict with manpages-dev 6.7-1

On Mon, Apr 01, 2024 at 04:23:08PM +0200, Alejandro Colomar wrote:
> The Linux man-pages project has recently added the pthread_*(3) manual
> pages that were provided by glibc-doc.  The first upstream version of
> the Linux man-pages that includes these pages is man-pages-6.06.  Here's
> what was added:
> 
>   $ git diff --stat b06cd070f..128a3ae35
>man3/pthread_cond_init.3| 264 
>man3/pthread_condattr_init.3|  48 
>man3/pthread_key_create.3   | 178 +
>man3/pthread_mutex_init.3   | 241 ++
>man3/pthread_mutexattr_setkind_np.3 |  52 
>man3/pthread_once.3 |  44 
>6 files changed, 827 insertions(+)

Here's the relevant excerpt of the git-log(1):

* 128a3ae35 pthread_key_create.3: Mention glibc instead of LinuxThreads
* 8a00cac75 pthread_*.3: ffix (semantic newlines)
* 74235f157 pthread_*.3: ffix (paragraphing)
* 13151ec52 pthread_*.3: Remove AUTHOR section; add copyright; adapt TH
* c1c253d0e pthread_cond_init.3, pthread_condattr_init.3, 
pthread_key_create.3, pthread_mutex_init.3, pthread_mutexattr_setkind_np.3, 
pthread_once.3: Update the glibc pages with the debian/glibc version of them
*   87183bb8e Import debian/local/manpages/pthread_*.3 git history from 
debian/glibc
|\  
| * 02d79c7d9   * Remove linuxthreads from the tarball: - 
rules.d/tarball.mk: don't fetech linuxthreads and linuxthreads_db. - 
rules.d/build.mk: don't build linuxthreads manpages. - rules: don't run 
make clean in linuxthreads directory. - patches/any/local-sysctl.diff: drop 
the linuxthreads part. - patches/all/local-pthread-manpages.diff: remove.   
  - local/manpages/pthread_*.3: import the few remaining linuxthreads   
manpages. - debhelper.in/glibc-doc.manpages: update manpage locations.
|/  
* a254db8b3 pthread_cond_init.3, pthread_condattr_init.3, 
pthread_key_create.3, pthread_mutex_init.3, pthread_mutexattr_setkind_np.3, 
pthread_once.3: Import pages from glibc
* 87d09778d Revert "linuxthreads, linuxthreads_db: Directories removed 
(preserved in ports repository)."
*   281f670a4 Import linuxthreads/man/ git history from glibc
|\  
| * a3db24d46 linuxthreads, linuxthreads_db: Directories removed 
(preserved in ports repository).
| * 2988d2724 (CFLAGS-tst-align.c): Add -mpreferred-stack-boundary=4.
| * f7f73b1ca 2.5-18.1
| * 67eceac09 Update.
| * 7ffaa96aa Update.
| * 869af9b6a Correct example.
| * 31b1e42d5 LinuxThreads library.
|/  

-- 

Looking for a remote C programming job at the moment.


signature.asc
Description: PGP signature

Bug#1068190: telegram-desktop: FTBFS with abseil 20230802: (.text+0x270): undefined reference to `absl::debian3::base_internal::ThrowStdOutOfRange(char const*)'

Source: telegram-desktop
Version: 4.14.9+ds-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: sramac...@debian.org

https://buildd.debian.org/status/fetch.php?pkg=telegram-desktop=arm64=4.14.9%2Bds-1%2Bb2=1711978921=0

cd /<>/obj-aarch64-linux-gnu/Telegram && /usr/bin/cmake -E 
cmake_link_script CMakeFiles/Telegram.dir/link.txt --verbose=1
/usr/bin/c++ -g -O2 -ffile-prefix-map=/<>=. 
-fstack-protector-strong -fstack-clash-protection -Wformat 
-Werror=format-security -mbranch-protection=standard 
-ftemplate-backtrace-limit=0 -Wdate-time -D_FORTIFY_SOURCE=2 
-Werror=invalid-pch -Wl,-z,relro -Wl,-z,now -Wno-alloc-size-larger-than 
-Wno-stringop-overflow -Wno-odr -Wno-inline -pthread -Wl,--as-needed 
@CMakeFiles/Telegram.dir/objects1.rsp -o ../telegram-desktop  
liblib_tgcalls_legacy.a liblib_tgcalls.a lib_base/liblib_base.a 
lib_ui/liblib_ui.a lib_spellcheck/liblib_spellcheck.a 
lib_webview/liblib_webview.a liblib_tgvoip_bundled.a 
/usr/lib/aarch64-linux-gnu/libminizip.so liblib_tgcalls.a 
/usr/lib/aarch64-linux-gnu/libopenal.so /usr/lib/aarch64-linux-gnu/libtg_owt.a 
/usr/lib/aarch64-linux-gnu/libsrtp2.so 
/usr/lib/aarch64-linux-gnu/libprotobuf.so /usr/lib/aarch64-linux-gnu/libssl.so 
/usr/lib/aarch64-linux-gnu/libcrypto.so /usr/lib/aarch64-linux-gnu/libopus.so 
/usr/lib/aarch64-linux-gnu/libabsl_flags_parse.so.20230802.0.1 
/usr/lib/aarch64-linux-gnu/libabsl_flags_usage.so.20230802.0.1 
/usr/lib/aarch64-linux-gnu/libabsl_flags_usage_internal.so.20230802.0.1 
/usr/lib/aarch64-linux-gnu/libabsl_flags_internal.so.20230802.0.1 
/usr/lib/aarch64-linux-gnu/libabsl_flags_marshalling.so.20230802.0.1 
/usr/lib/aarch64-linux-gnu/libabsl_flags_reflection.so.20230802.0.1 
/usr/lib/aarch64-linux-gnu/libabsl_cord.so.20230802.0.1 
/usr/lib/aarch64-linux-gnu/libabsl_cordz_info.so.20230802.0.1 
/usr/lib/aarch64-linux-gnu/libabsl_cord_internal.so.20230802.0.1 
/usr/lib/aarch64-linux-gnu/libabsl_cordz_functions.so.20230802.0.1 
/usr/lib/aarch64-linux-gnu/libabsl_cordz_handle.so.20230802.0.1 
/usr/lib/aarch64-linux-gnu/libabsl_crc_cord_state.so.20230802.0.1 
/usr/lib/aarch64-linux-gnu/libabsl_crc32c.so.20230802.0.1 
/usr/lib/aarch64-linux-gnu/libabsl_str_format_internal.so.20230802.0.1 
/usr/lib/aarch64-linux-gnu/libabsl_crc_internal.so.20230802.0.1 
/usr/lib/aarch64-linux-gnu/libabsl_crc_cpu_detect.so.20230802.0.1 
/usr/lib/aarch64-linux-gnu/libabsl_raw_hash_set.so.20230802.0.1 
/usr/lib/aarch64-linux-gnu/libabsl_hash.so.20230802.0.1 
/usr/lib/aarch64-linux-gnu/libabsl_city.so.20230802.0.1 
/usr/lib/aarch64-linux-gnu/libabsl_low_level_hash.so.20230802.0.1 
/usr/lib/aarch64-linux-gnu/libabsl_hashtablez_sampler.so.20230802.0.1 
/usr/lib/aarch64-linux-gnu/libabsl_exponential_biased.so.20230802.0.1 
/usr/lib/aarch64-linux-gnu/libabsl_flags_config.so.20230802.0.1 
/usr/lib/aarch64-linux-gnu/libabsl_flags_private_handle_accessor.so.20230802.0.1
 /usr/lib/aarch64-linux-gnu/libabsl_flags_commandlineflag.so.20230802.0.1 
/usr/lib/aarch64-linux-gnu/libabsl_flags_commandlineflag_internal.so.20230802.0.1
 /usr/lib/aarch64-linux-gnu/libabsl_flags_program_name.so.20230802.0.1 
/usr/lib/aarch64-linux-gnu/libabsl_bad_optional_access.so.20230802.0.1 
/usr/lib/aarch64-linux-gnu/libabsl_synchronization.so.20230802.0.1 
/usr/lib/aarch64-linux-gnu/libabsl_graphcycles_internal.so.20230802.0.1 
/usr/lib/aarch64-linux-gnu/libabsl_kernel_timeout_internal.so.20230802.0.1 
/usr/lib/aarch64-linux-gnu/libabsl_stacktrace.so.20230802.0.1 
/usr/lib/aarch64-linux-gnu/libabsl_symbolize.so.20230802.0.1 
/usr/lib/aarch64-linux-gnu/libabsl_malloc_internal.so.20230802.0.1 
/usr/lib/aarch64-linux-gnu/libabsl_debugging_internal.so.20230802.0.1 
/usr/lib/aarch64-linux-gnu/libabsl_demangle_internal.so.20230802.0.1 
/usr/lib/aarch64-linux-gnu/libabsl_time.so.20230802.0.1 
/usr/lib/aarch64-linux-gnu/libabsl_strings.so.20230802.0.1 
/usr/lib/aarch64-linux-gnu/libabsl_string_view.so.20230802.0.1 
/usr/lib/aarch64-linux-gnu/libabsl_throw_delegate.so.20230802.0.1 
/usr/lib/aarch64-linux-gnu/libabsl_strings_internal.so.20230802.0.1 
/usr/lib/aarch64-linux-gnu/libabsl_base.so.20230802.0.1 
/usr/lib/aarch64-linux-gnu/libabsl_spinlock_wait.so.20230802.0.1 
/usr/lib/aarch64-linux-gnu/libabsl_int128.so.20230802.0.1 
/usr/lib/aarch64-linux-gnu/libabsl_civil_time.so.20230802.0.1 
/usr/lib/aarch64-linux-gnu/libabsl_time_zone.so.20230802.0.1 
/usr/lib/aarch64-linux-gnu/libabsl_bad_variant_access.so.20230802.0.1 
/usr/lib/aarch64-linux-gnu/libabsl_raw_logging_internal.so.20230802.0.1 
/usr/lib/aarch64-linux-gnu/libabsl_log_severity.so.20230802.0.1 
-Wl,--push-state,--as-needed -latomic -Wl,--pop-state 
/usr/lib/aarch64-linux-gnu/libvpx.so /usr/lib/aarch64-linux-gnu/libm.so 
/usr/lib/aarch64-linux-gnu/libyuv.so /usr/lib/aarch64-linux-gnu/libX11.so 
/usr/lib/aarch64-linux-gnu/libXcomposite.so 
/usr/lib/aarch64-linux-gnu/libXdamage.so /usr/lib/aarch64-linux-gnu/libXext.so 
/usr/lib/aarch64-linux-gnu/libXfixes.so

Bug#1068187: marked as done (Session fails to start with gnome-session >= 46)

Your message dated Mon, 1 Apr 2024 16:28:09 +0200
with message-id 
and subject line Re: Bug#1068187: Session fails to start with gnome-session >= 
46
has caused the Debian Bug report #1068187,
regarding Session fails to start with gnome-session >= 46
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1068187: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068187
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: phosh
Version: 0.37.1
Severity: grave

gnome-session no longer accepts the --systemd or --builtin arguments
which restults in the session failing to start.

This is already fixed in 0.37.0-2. Mostly filing this to get the version
tracking right.


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

Kernel: Linux 6.6.15-amd64 (SMP w/12 CPU threads; PREEMPT)
Kernel taint flags: TAINT_WARN, 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 phosh depends on:
ii  dconf-gsettings-backend [gsettings-bac  0.40.0-4+b1
kend]
ii  fonts-lato  2.015-1
ii  gnome-shell-common  44.9-1
ii  gsettings-desktop-schemas   46.0-1
ii  libc6   2.37-15
ii  libcairo2   1.18.0-1+b1
ii  libcallaudio-0-10.1.9-1+b1
ii  libcap2-bin 1:2.66-5
ii  libecal-2.0-2t643.50.3-2.2
ii  libedataserver-1.2-27t643.50.3-2.2
ii  libfeedback-0.0-0   0.2.1-1+b1
ii  libfribidi0 1.0.13-3+b1
ii  libgcr-base-3-1 3.41.2-1
ii  libgcr-ui-3-1   3.41.2-1
ii  libgdk-pixbuf-2.0-0 2.42.10+dfsg-3+b1
ii  libglib2.0-0t64 2.78.4-6
ii  libgnome-desktop-3-20t6444.0-5
ii  libgtk-3-0t64   3.24.41-4
ii  libgudev-1.0-0  238-3
ii  libhandy-1-01.8.3-1
ii  libical3t64 3.0.17-1.1
ii  libjson-glib-1.0-0  1.8.0-2
ii  libnm0  1.46.0-1
ii  libpam0g1.5.2-9.1+b1
ii  libpango-1.0-0  1.52.0+ds-1
ii  libpolkit-agent-1-0 124-1
ii  libpolkit-gobject-1-0   124-1
ii  libpulse-mainloop-glib0 16.1+dfsg1-3
ii  libpulse0   16.1+dfsg1-3
ii  libsecret-1-0   0.21.4-1
ii  libsystemd0 255.4-1
ii  libupower-glib3 1.90.2-8
ii  libwayland-client0  1.22.0-2.1+b1
ii  phoc0.37.0+next20240325.1905.b42258fa.1

Versions of packages phosh recommends:
ii  feedbackd  0.2.1-1+b1
ii  fonts-cantarell0.303.1-1
ii  gnome-session-bin  46.0-1
ii  gnome-session-common   46.0-1
ii  gnome-settings-daemon  46~beta-2
ii  iio-sensor-proxy   3.5-1+b1
ii  librsvg2-common2.54.7+dfsg-2
ii  phosh-mobile-tweaks0.37.0-1
hi  phosh-osk-stub 0.35.0
ii  slurp  1.5.0-1
ii  squeekboard1.24.0-1

phosh suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---

Version: phosh/0.37.0-2

On Mon, Apr 01, 2024 at 03:51:29PM +0200, Guido Günther wrote:
> Package: phosh
> Version: 0.37.1
> Severity: grave
> 
> gnome-session no longer accepts the --systemd or --builtin arguments
> which restults in the session failing to start.
> 
> This is already fixed in 0.37.0-2. Mostly filing this to get the version
> tracking right.

Closing with the aforementioned version.
Cheers,
 -- Guido

> 
> 
> -- System Information:
> Debian Release: trixie/sid
>   APT prefers testing
>   APT policy: (990, 'testing'), (500, 'unstable-debug'), (500, 
> 'testing-debug'), (500, 'unstable'), (1, 'experimental-debug'), (1, 
> 'experimental')
> Architecture: amd64 (x86_64)
> Foreign Architectures: arm64
> 
> Kernel: Linux 6.6.15-amd64 (SMP w/12 CPU threads; PREEMPT)
> Kernel taint flags: TAINT_WARN, TAINT_OOT_MODULE,

Processed: debhelper: --link-doc checking for known packages makes linux-signed build FTBFS

Processing control commands:

> affects -1 + src:linux,src:linux-signed-amd64,src:linux-signed-arm64
Bug #1068189 [src:debhelper] debhelper: --link-doc checking for known packages 
makes linux-signed build FTBFS
Added indication that 1068189 affects src:linux, src:linux-signed-amd64, and 
src:linux-signed-arm64

-- 
1068189: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068189
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1068189: debhelper: --link-doc checking for known packages makes linux-signed build FTBFS

2024-04-01 Thread Salvatore Bonaccorso

Source: debhelper
Version: 13.15
Severity: serious
Tags: ftbfs
Justification: Regression for other package builds, FTBFS
X-Debbugs-Cc: car...@debian.org,debian-ker...@lists.debian.org
Control: affects -1 + src:linux,src:linux-signed-amd64,src:linux-signed-arm64

Hi Niels,

Not fully investigated, but starting to fill a bugreport. I noticed
that the src:linux pipeline on salsa started to fail for the
jobs in th build-signed stage (in the build-signed job).

https://salsa.debian.org/carnil/linux/-/jobs/5527774

(and for saving the output):

dh_installdocs --link-doc=linux-headers-6.7+unreleased-cloud-amd64
dh_installdocs: error: Requested unknown package 
linux-headers-6.7+unreleased-cloud-amd64 via --link-doc, expected one of: 
linux-image-6.7+unreleased-amd64 linux-image-amd64 linux-headers-amd64 
linux-image-6.7+unreleased-cloud-amd64 linux-image-cloud-amd64 
linux-headers-cloud-amd64 linux-image-6.7+unreleased-rt-amd64 
linux-image-rt-amd64 linux-headers-rt-amd64
make[2]: *** [debian/rules.real:81: binary_meta] Error 25
make[1]: *** [debian/rules.gen:21: binary-arch_amd64_none_cloud-amd64_meta] 
Error 2
make: *** [debian/rules:19: binary-arch] Error 2
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2

(attached as well the raw log)

I'm not 100% sure yet, this might be a problem in our packaging in
which case we can re-eassign. But it only got triggered with the
change recently in debhelper:

https://salsa.debian.org/debian/debhelper/-/commit/dec5cfad00e2abd9ee3594f90c93f3fa42bb73ff

Regards,
Salvatore


5527774.log.gz
Description: application/gzip

Bug#1068188: pthread_cond_init.3.gz: conflict with manpages-dev 6.7-1

Package: glibc-doc
Version: 2.38-6
Severity: serious
Justification: Policy 7.4
X-Debbugs-Cc: a...@kernel.org, mar...@debian.org

Dear Maintainer,

The Linux man-pages project has recently added the pthread_*(3) manual
pages that were provided by glibc-doc.  The first upstream version of
the Linux man-pages that includes these pages is man-pages-6.06.  Here's
what was added:

$ git diff --stat b06cd070f..128a3ae35
 man3/pthread_cond_init.3| 264 
 man3/pthread_condattr_init.3|  48 
 man3/pthread_key_create.3   | 178 +
 man3/pthread_mutex_init.3   | 241 ++
 man3/pthread_mutexattr_setkind_np.3 |  52 
 man3/pthread_once.3 |  44 
 6 files changed, 827 insertions(+)

Debian's manpages-dev_6.7-1_all.deb has been the first package since
that happened, and I've noticed that dpkg(1) (via apt-get(8)) refuses to
upgrade manpages-dev due to a conflict with glibc-doc.

$ sudo apt-get upgrade -V;
[...]
Do you want to continue? [Y/n] y
Reading changelogs... Done
(Reading database ... 404853 files and directories currently installed.)
Preparing to unpack .../manpages-dev_6.7-1_all.deb ...
Unpacking manpages-dev (6.7-1) over (6.05.01-1) ...
dpkg: error processing archive 
/var/cache/apt/archives/manpages-dev_6.7-1_all.deb (--unpack):
 trying to overwrite '/usr/share/man/man3/pthread_cond_init.3.gz', 
which is also in package glibc-doc 2.38-6
Errors were encountered while processing:
 /var/cache/apt/archives/manpages-dev_6.7-1_all.deb
needrestart is being skipped since dpkg has failed
E: Sub-process /usr/bin/dpkg returned an error code (1)

Please, remove from glibc-doc those manual pages that conflict with
manpages-dev.

Marcos, you'll also need to specify a breaks with glibc-doc versions
up to (and including) 6.38-6 in the next revision of manpages-dev, and
drop 6.7-1.


Have a lovely day!
Alex


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

Kernel: Linux 6.8.0-rc7-alx-dirty (SMP w/24 CPU threads; PREEMPT)
Locale: LANG=C.utf8, LC_CTYPE=C.utf8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

glibc-doc depends on no packages.

glibc-doc recommends no packages.

Versions of packages glibc-doc suggests:
ii  glibc-doc-reference  2.38-1

-- no debconf information

Bug#1068180: marked as done (FTBFS: C++ versions less than C++14 are not supported.)

Your message dated Mon, 01 Apr 2024 13:51:15 +
with message-id 
and subject line Bug#1068180: fixed in libgav1 0.19.0-2
has caused the Debian Bug report #1068180,
regarding FTBFS: C++ versions less than C++14 are not supported.
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1068180: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068180
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libgav1
Version: 0.18.0-1
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/fetch.php?pkg=libgav1=armel=0.18.0-1%2Bb2=1711940873=0

In file included from /usr/include/absl/base/config.h:86,
 from /usr/include/absl/base/attributes.h:37,
 from /usr/include/absl/base/thread_annotations.h:37,
 from /<>/src/utils/threadpool.h:42,
 from /<>/src/threading_strategy.h:24,
 from /<>/src/frame_scratch_buffer.h:31,
 from /<>/src/decoder_impl.h:30,
 from /<>/src/decoder_impl.cc:15:
/usr/include/absl/base/policy_checks.h:79:2: error: #error "C++ versions less
than C++14 are not supported."
   79 | #error "C++ versions less than C++14 are not supported."
  |  ^


/usr/bin/c++ -DLIBGAV1_CMAKE=1 -DLIBGAV1_ENABLE_AVX2=0 -DLIBGAV1_ENABLE_NEON=0
-DLIBGAV1_ENABLE_SSE4_1=0 -DLIBGAV1_FLAGS_SRCDIR=\"/<>\"
-DLIBGAV1_FLAGS_TMPDIR=\"/tmp\" -DLIBGAV1_MAX_BITDEPTH=10 -I/<>
-I/<>/src -I/<>/obj-arm-linux-gnueabi
-I/<>/third_party/abseil-cpp
-I/<>/third_party/googletest/googlemock/include
-I/<>/third_party/googletest/googletest/include
-I/<>/third_party/googletest/googletest -g -O2 -ffile-prefix-
map=/<>=. -flto=auto -ffat-lto-objects -fstack-protector-strong
-fstack-clash-protection -Wformat -Werror=format-security -D_LARGEFILE_SOURCE
-D_FILE_OFFSET_BITS=64 -D_TIME_BITS=64 -Wdate-time -D_FORTIFY_SOURCE=2
-D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -D_TIME_BITS=64 -Wdate-time
-D_FORTIFY_SOURCE=2 -std=gnu++11 -fPIC -Wall -Wextra -Wmissing-declarations
-Wno-sign-compare -fvisibility=hidden -fvisibility-inlines-hidden -Wno-format-
truncation -MD -MT CMakeFiles/libgav1_utils.dir/src/utils/segmentation.cc.o -MF
CMakeFiles/libgav1_utils.dir/src/utils/segmentation.cc.o.d -o
CMakeFiles/libgav1_utils.dir/src/utils/segmentation.cc.o -c
/<>/src/utils/segmentation.cc
In file included from /usr/include/absl/time/time.h:89,
 from /usr/include/absl/time/clock.h:26,
 from
/usr/include/absl/synchronization/internal/kernel_timeout.h:30,
 from /usr/include/absl/synchronization/mutex.h:74,
 from /<>/src/utils/threadpool.h:43:
/usr/include/absl/strings/string_view.h: In member function ‘constexpr void
absl::debian5::string_view::remove_prefix(size_type) const’:
/usr/include/absl/strings/string_view.h:340:10: error: assignment of member
‘absl::debian5::string_view::ptr_’ in read-only object
  340 | ptr_ += n;
  | ~^~~~
/usr/include/absl/strings/string_view.h:341:13: error: assignment of member
‘absl::debian5::string_view::length_’ in read-only object
  341 | length_ -= n;
  | ^~~~
/usr/include/absl/strings/string_view.h: In member function ‘constexpr void
absl::debian5::string_view::remove_suffix(size_type) const’:
/usr/include/absl/strings/string_view.h:350:13: error: assignment of member
‘absl::debian5::string_view::length_’ in read-only object
  350 | length_ -= n;
  | ^~~~
/usr/include/absl/strings/string_view.h: In member function ‘constexpr void
absl::debian5::string_view::swap(absl::debian5::string_view&) const’:
/usr/include/absl/strings/string_view.h:358:13: error: passing ‘const
absl::debian5::string_view’ as ‘this’ argument discards qualifiers
[-fpermissive]
  358 | *this = s;
  | ^
/usr/include/absl/strings/string_view.h:161:7: note:   in call to
‘absl::debian5::string_view& absl::debian5::string_view::operator=(const
absl::debian5::string_view&)’
  161 | class string_view {
  |   ^~~
make[3]: Leaving directory '/<>/obj-arm-linux-gnueabi'
[ 15%] Built target libgav1_file_writer
/usr/include/absl/time/time.h: In constructor
‘absl::debian5::Duration::HiRep::HiRep(int64_t)’:
/usr/include/absl/time/time.h:256:5: error: ‘constexpr’ constructor does not
have empty body
  256 | }
  | ^
/usr/include/absl/time/time.h: In member function ‘constexpr int64_t
absl::debian5::Duration::HiRep::Get() const’:
/usr/include/absl/time/time.h:276:5: error: body of ‘constexpr’ function
‘constexpr int64_t absl::debian5::Duration::HiRep::Get() const’ not a

Bug#1068187: Session fails to start with gnome-session >= 46

2024-04-01 Thread Guido Günther

Package: phosh
Version: 0.37.1
Severity: grave

gnome-session no longer accepts the --systemd or --builtin arguments
which restults in the session failing to start.

This is already fixed in 0.37.0-2. Mostly filing this to get the version
tracking right.


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

Kernel: Linux 6.6.15-amd64 (SMP w/12 CPU threads; PREEMPT)
Kernel taint flags: TAINT_WARN, 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 phosh depends on:
ii  dconf-gsettings-backend [gsettings-bac  0.40.0-4+b1
kend]
ii  fonts-lato  2.015-1
ii  gnome-shell-common  44.9-1
ii  gsettings-desktop-schemas   46.0-1
ii  libc6   2.37-15
ii  libcairo2   1.18.0-1+b1
ii  libcallaudio-0-10.1.9-1+b1
ii  libcap2-bin 1:2.66-5
ii  libecal-2.0-2t643.50.3-2.2
ii  libedataserver-1.2-27t643.50.3-2.2
ii  libfeedback-0.0-0   0.2.1-1+b1
ii  libfribidi0 1.0.13-3+b1
ii  libgcr-base-3-1 3.41.2-1
ii  libgcr-ui-3-1   3.41.2-1
ii  libgdk-pixbuf-2.0-0 2.42.10+dfsg-3+b1
ii  libglib2.0-0t64 2.78.4-6
ii  libgnome-desktop-3-20t6444.0-5
ii  libgtk-3-0t64   3.24.41-4
ii  libgudev-1.0-0  238-3
ii  libhandy-1-01.8.3-1
ii  libical3t64 3.0.17-1.1
ii  libjson-glib-1.0-0  1.8.0-2
ii  libnm0  1.46.0-1
ii  libpam0g1.5.2-9.1+b1
ii  libpango-1.0-0  1.52.0+ds-1
ii  libpolkit-agent-1-0 124-1
ii  libpolkit-gobject-1-0   124-1
ii  libpulse-mainloop-glib0 16.1+dfsg1-3
ii  libpulse0   16.1+dfsg1-3
ii  libsecret-1-0   0.21.4-1
ii  libsystemd0 255.4-1
ii  libupower-glib3 1.90.2-8
ii  libwayland-client0  1.22.0-2.1+b1
ii  phoc0.37.0+next20240325.1905.b42258fa.1

Versions of packages phosh recommends:
ii  feedbackd  0.2.1-1+b1
ii  fonts-cantarell0.303.1-1
ii  gnome-session-bin  46.0-1
ii  gnome-session-common   46.0-1
ii  gnome-settings-daemon  46~beta-2
ii  iio-sensor-proxy   3.5-1+b1
ii  librsvg2-common2.54.7+dfsg-2
ii  phosh-mobile-tweaks0.37.0-1
hi  phosh-osk-stub 0.35.0
ii  slurp  1.5.0-1
ii  squeekboard1.24.0-1

phosh suggests no packages.

-- no debconf information

Processed: severity of 1059228 is serious, tagging 1059228

Processing commands for cont...@bugs.debian.org:

> # 
> https://buildd.debian.org/status/fetch.php?pkg=s2geometry=amd64=0.10.0-6.1%2Bb2=1711976885=0
> severity 1059228 serious
Bug #1059228 [src:s2geometry] build system hard-codes -std=c++11
Severity set to 'serious' from 'normal'
> tags 1059228 + sid trixie
Bug #1059228 [src:s2geometry] build system hard-codes -std=c++11
Added tag(s) trixie and sid.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1059228: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1059228
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1063976: marked as done (javaproperties: autopkgtest regression with pytest 8)

Your message dated Mon, 01 Apr 2024 13:35:04 +
with message-id 
and subject line Bug#1063976: fixed in javaproperties 0.8.1-2
has caused the Debian Bug report #1063976,
regarding javaproperties: autopkgtest regression with pytest 8
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1063976: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063976
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: javaproperties
Version: 0.8.1-1.1
Severity: important
User: debian-pyt...@lists.debian.org
Usertags: pytest-8

Dear maintainer,

your package has a autopkgtest regression with pytest 8.

Typically, packages will start failing if they

- have deprecation warnings of type PytestRemovedIn8Warning, or

- assume a particular pytest stdout/stderr output which might have
changed, or

- rely on implementation details of the pytest test collector, in
particular the pytest.Package class, which has been redesigned for
pytest 8.

Please refer to the upstream changelog [1] for a complete list of
breaking changes and the pytest (pseudo-)excuses [2] related to your
package for details of the regression.

It is possible that the autopkgtest regression is not directly caused
by javaproperties, but by one of its dependencies. In that case, feel
free to reassign the bug and mark your package as affected, but do
not close the bug until the autopkgtest passes.

Cheers Timo

[1]
https://docs.pytest.org/en/8.0.x/changelog.html#pytest-8-0-0rc1-2023-
12-30 [2]
https://qa.debian.org/excuses.php?experimental=1=pytest
--- End Message ---
--- Begin Message ---
Source: javaproperties
Source-Version: 0.8.1-2
Done: Luca Boccassi 

We believe that the bug you reported is fixed in the latest version of
javaproperties, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1063...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Luca Boccassi  (supplier of updated javaproperties package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 01 Apr 2024 14:04:52 +0100
Source: javaproperties
Architecture: source
Version: 0.8.1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team 
Changed-By: Luca Boccassi 
Closes: 1063976
Changes:
 javaproperties (0.8.1-2) unstable; urgency=medium
 .
   [ Alexandre Detiste ]
   * remove extraneous python3-six dependencies
 .
   [ Luca Boccassi ]
   * Bump Standards-Version to 4.6.2, no changes
   * Disable tests due to API breakage in pytest 8 (Closes: #1063976)
Checksums-Sha1:
 cf7a65a39335b9170b728de9f54a3cb32dc987c5 2139 javaproperties_0.8.1-2.dsc
 ca080af147f839a70332f300a21da93718cc668e 2776 
javaproperties_0.8.1-2.debian.tar.xz
 acbe36505b439f6ca1cb6517fdfaae83c678923a 7934 
javaproperties_0.8.1-2_source.buildinfo
Checksums-Sha256:
 3c9c8a79a222d97fa54b710bfd86e9898025eaa505cf73d127c09632aa8ce6b1 2139 
javaproperties_0.8.1-2.dsc
 e16855f68777844c5f267a8a16c0bc1d740a91935e58f9931ed472a1a6de93f3 2776 
javaproperties_0.8.1-2.debian.tar.xz
 28a088961293a245ae60bdf910cf406d760c9f6b66b8ed4953e6340ec22583a5 7934 
javaproperties_0.8.1-2_source.buildinfo
Files:
 03948e9b3dd4078fd9cba2bc48623a95 2139 python optional 
javaproperties_0.8.1-2.dsc
 2e919ac84c893c55a146be6b7506f1fe 2776 python optional 
javaproperties_0.8.1-2.debian.tar.xz
 4cd289a9b85957844b21c7ce5be6c629 7934 python optional 
javaproperties_0.8.1-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJFBAEBCgAvFiEErCSqx93EIPGOymuRKGv37813JB4FAmYKs4oRHGJsdWNhQGRl
Ymlhbi5vcmcACgkQKGv37813JB6APQ/9GvNyfsGaNLXJVSmPuhuVN3TLMcJjpMtk
MBN6dyyUREP/qTj48QS1QHuEs1zo3Cnen6UI0CQaUOwyH1Wr0EdRhyUSiwED3zuN
r70hw6gZ8LBnVcQBqtuEHCWCuLjUY90ScYA1YmDaaYGmUmCi10AMBXJAxZcmZqJY
vSiVtpwNUm8Hy13ogyvbbJU7np0NLrAUbAdqOPb5vRedVg/cTPOgXV38fCFYZw1X
KPnhaAS9NE68ju6Cy1iBPc3pby+KavGaJ+MTIFHflBQ1COwzHKDDP8ZARnw9aKnN
sadQR1N5CO671PKKNraDjo47Ohr/JdDgn9JFsHjWlxXxwsCZCkBB7olE7AhdJXdL
NXnGBVCnGftFtYQhVsHfPaMUPjyHHue8hhEOk16t/wGf5BfYvOBUirvp89Zp/3o/
ILPevmuAkOk6wo0kab/wrTIMX0wKB1JGwfWY3ks5mlzg9OQEoMhbcLLr0/8rNE9B
UlolULD8fqtljt0wJMcgBKbOyN99NQlo9DRdGi4oO6QByToTUZgdT6FyDRfvvXna
1/Tg6UgxEl/frlOnekQLfo+Wo54lClQgJ6V5S4C4cj4OQQ8+pGcuq7p+hbZvRK6H

Bug#1068186: mozc: FTBFS with abseil 20230802: ../../base/init_mozc.cc:90:29: error: ‘absl::debian5::flags_internal::ArgvListAction’ has not been declared

Source: mozc
Version: 2.28.4715.102+dfsg-2.2
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: sramac...@debian.org

https://buildd.debian.org/status/fetch.php?pkg=mozc=amd64=2.28.4715.102%2Bdfsg-2.2%2Bb5=1711976888=0

[57/144] /usr/bin/g++ -MMD -MF obj/base/base_core.init_mozc.o.d -DOS_LINUX 
-DMOZC_BUILD -DCHANNEL_DEV -DENABLE_GTK_RENDERER 
'-DMOZC_SERVER_DIR="/usr/lib/mozc"' 
'-DMOZC_DOCUMENT_DIR="/usr/lib/mozc/documents"' -DNDEBUG -DQT_NO_DEBUG 
-DMOZC_NO_LOGGING -DIGNORE_HELP_FLAG -DIGNORE_INVALID_FLAG 
'-I/<>/src' -Igen -I../../third_party/abseil-cpp -Igen/proto_out 
-fmessage-length=0 -fno-strict-aliasing -funsigned-char -pipe -pthread 
-fno-omit-frame-pointer -fstack-protector --param=ssp-buffer-size=4 -Wall 
-Wno-char-subscripts -Wno-sign-compare -Wno-deprecated-declarations 
-Wwrite-strings -Wno-unknown-warning-option -Wno-inconsistent-missing-override 
-fPIC -fno-exceptions -O2 -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong 
-fstack-clash-protection -Wformat -Werror=format-security -fcf-protection 
-Wdate-time -D_FORTIFY_SOURCE=2 -Wno-deprecated  -c ../../base/init_mozc.cc -o 
obj/base/base_core.init_mozc.o
FAILED: obj/base/base_core.init_mozc.o 
/usr/bin/g++ -MMD -MF obj/base/base_core.init_mozc.o.d -DOS_LINUX -DMOZC_BUILD 
-DCHANNEL_DEV -DENABLE_GTK_RENDERER '-DMOZC_SERVER_DIR="/usr/lib/mozc"' 
'-DMOZC_DOCUMENT_DIR="/usr/lib/mozc/documents"' -DNDEBUG -DQT_NO_DEBUG 
-DMOZC_NO_LOGGING -DIGNORE_HELP_FLAG -DIGNORE_INVALID_FLAG 
'-I/<>/src' -Igen -I../../third_party/abseil-cpp -Igen/proto_out 
-fmessage-length=0 -fno-strict-aliasing -funsigned-char -pipe -pthread 
-fno-omit-frame-pointer -fstack-protector --param=ssp-buffer-size=4 -Wall 
-Wno-char-subscripts -Wno-sign-compare -Wno-deprecated-declarations 
-Wwrite-strings -Wno-unknown-warning-option -Wno-inconsistent-missing-override 
-fPIC -fno-exceptions -O2 -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong 
-fstack-clash-protection -Wformat -Werror=format-security -fcf-protection 
-Wdate-time -D_FORTIFY_SOURCE=2 -Wno-deprecated  -c ../../base/init_mozc.cc -o 
obj/base/base_core.init_mozc.o
../../base/init_mozc.cc: In function ‘void 
mozc::{anonymous}::ParseCommandLineFlags(int, char**)’:
../../base/init_mozc.cc:90:29: error: 
‘absl::debian5::flags_internal::ArgvListAction’ has not been declared
   90 |   absl::flags_internal::ArgvListAction::kRemoveParsedArgs,
  | ^~

Cheers
-- 
Sebastian Ramacher

Bug#1068185: llvm-toolchain-16: FTBFS on armel: cxa_guard.cpp:(.text.unlikely.__cxa_guard_acquire+0xc): undefined reference to `__atomic_load_1'

Source: llvm-toolchain-16
Version: 1:16.0.6-24
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: sramac...@debian.org

https://buildd.debian.org/status/fetch.php?pkg=llvm-toolchain-16=armel=1%3A16.0.6-24=1711530825=0

FAILED: /<>/build-llvm/lib/libc++abi.so.1.0 
: && /<>/build-llvm/./bin/clang++ --target=arm-linux-gnueabi -fPIC 
-fstack-protector-strong -fstack-clash-protection -Wformat 
-Werror=format-security -Wno-unused-command-line-argument -march=armv5t 
-D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -D_TIME_BITS=64 -Wdate-time 
-D_FORTIFY_SOURCE=2 -fPIC -fno-semantic-interposition 
-fvisibility-inlines-hidden -Werror=date-time 
-Werror=unguarded-availability-new -Wall -Wextra -Wno-unused-parameter 
-Wwrite-strings -Wcast-qual -Wmissing-field-initializers -Wimplicit-fallthrough 
-Wcovered-switch-default -Wno-noexcept-type -Wnon-virtual-dtor 
-Wdelete-non-virtual-dtor -Wsuggest-override -Wstring-conversion 
-Wmisleading-indentation -Wctad-maybe-unsupported -fdiagnostics-color 
-ffunction-sections -fdata-sections 
-fdebug-prefix-map=/<>/build-llvm/runtimes/runtimes-bins=build-llvm/runtimes/runtimes-bins
 -fdebug-prefix-map=/<>/= -no-canonical-prefixes 
-ffile-prefix-map=/<>/build-llvm/runtimes/runtimes-bins=build-llvm/runtimes/runtimes-bins
 -ffile-prefix-map=/<>/= -no-canonical-prefixes  -O3 -DNDEBUG  
-Wl,-z,relro -Wl,--build-id,--as-needed -latomic -Wl,-z,defs -Wl,-z,nodelete  
-nostdlib++ -shared -Wl,-soname,libc++abi.so.1 -o 
/<>/build-llvm/lib/libc++abi.so.1.0 
libcxxabi/src/CMakeFiles/cxxabi_shared_objects.dir/cxa_aux_runtime.cpp.o 
libcxxabi/src/CMakeFiles/cxxabi_shared_objects.dir/cxa_default_handlers.cpp.o 
libcxxabi/src/CMakeFiles/cxxabi_shared_objects.dir/cxa_demangle.cpp.o 
libcxxabi/src/CMakeFiles/cxxabi_shared_objects.dir/cxa_exception_storage.cpp.o 
libcxxabi/src/CMakeFiles/cxxabi_shared_objects.dir/cxa_guard.cpp.o 
libcxxabi/src/CMakeFiles/cxxabi_shared_objects.dir/cxa_handlers.cpp.o 
libcxxabi/src/CMakeFiles/cxxabi_shared_objects.dir/cxa_vector.cpp.o 
libcxxabi/src/CMakeFiles/cxxabi_shared_objects.dir/cxa_virtual.cpp.o 
libcxxabi/src/CMakeFiles/cxxabi_shared_objects.dir/stdlib_exception.cpp.o 
libcxxabi/src/CMakeFiles/cxxabi_shared_objects.dir/stdlib_stdexcept.cpp.o 
libcxxabi/src/CMakeFiles/cxxabi_shared_objects.dir/stdlib_typeinfo.cpp.o 
libcxxabi/src/CMakeFiles/cxxabi_shared_objects.dir/abort_message.cpp.o 
libcxxabi/src/CMakeFiles/cxxabi_shared_objects.dir/fallback_malloc.cpp.o 
libcxxabi/src/CMakeFiles/cxxabi_shared_objects.dir/private_typeinfo.cpp.o 
libcxxabi/src/CMakeFiles/cxxabi_shared_objects.dir/stdlib_new_delete.cpp.o 
libcxxabi/src/CMakeFiles/cxxabi_shared_objects.dir/cxa_exception.cpp.o 
libcxxabi/src/CMakeFiles/cxxabi_shared_objects.dir/cxa_personality.cpp.o 
libcxxabi/src/CMakeFiles/cxxabi_shared_objects.dir/cxa_thread_atexit.cpp.o  
-lpthread  -lc  -lgcc  -lgcc_s && :
/usr/bin/arm-linux-gnueabi-ld: 
libcxxabi/src/CMakeFiles/cxxabi_shared_objects.dir/cxa_guard.cpp.o: in function 
`__cxa_guard_acquire':
cxa_guard.cpp:(.text.unlikely.__cxa_guard_acquire+0xc): undefined reference to 
`__atomic_load_1'
/usr/bin/arm-linux-gnueabi-ld: 
libcxxabi/src/CMakeFiles/cxxabi_shared_objects.dir/cxa_guard.cpp.o: in function 
`__cxa_guard_release':
cxa_guard.cpp:(.text.unlikely.__cxa_guard_release+0x14): undefined reference to 
`__atomic_store_1'
/usr/bin/arm-linux-gnueabi-ld: 
libcxxabi/src/CMakeFiles/cxxabi_shared_objects.dir/cxa_default_handlers.cpp.o: 
in function `std::set_unexpected(void (*)())':
cxa_default_handlers.cpp:(.text._ZSt14set_unexpectedPFvvE+0x1c): undefined 
reference to `__atomic_exchange_4'
/usr/bin/arm-linux-gnueabi-ld: 
libcxxabi/src/CMakeFiles/cxxabi_shared_objects.dir/cxa_default_handlers.cpp.o: 
in function `std::set_terminate(void (*)())':
cxa_default_handlers.cpp:(.text._ZSt13set_terminatePFvvE+0x1c): undefined 
reference to `__atomic_exchange_4'
/usr/bin/arm-linux-gnueabi-ld: 
libcxxabi/src/CMakeFiles/cxxabi_shared_objects.dir/cxa_default_handlers.cpp.o: 
in function `std::set_new_handler(void (*)())':
cxa_default_handlers.cpp:(.text._ZSt15set_new_handlerPFvvE+0x10): undefined 
reference to `__atomic_exchange_4'
/usr/bin/arm-linux-gnueabi-ld: 
libcxxabi/src/CMakeFiles/cxxabi_shared_objects.dir/cxa_handlers.cpp.o: in 
function `std::get_unexpected()':
cxa_handlers.cpp:(.text._ZSt14get_unexpectedv+0xc): undefined reference to 
`__atomic_load_4'
/usr/bin/arm-linux-gnueabi-ld: 
libcxxabi/src/CMakeFiles/cxxabi_shared_objects.dir/cxa_handlers.cpp.o: in 
function `std::get_terminate()':
cxa_handlers.cpp:(.text._ZSt13get_terminatev+0xc): undefined reference to 
`__atomic_load_4'
/usr/bin/arm-linux-gnueabi-ld: 
libcxxabi/src/CMakeFiles/cxxabi_shared_objects.dir/cxa_handlers.cpp.o: in 
function `std::get_new_handler()':
cxa_handlers.cpp:(.text._ZSt15get_new_handlerv+0xc): undefined reference to 
`__atomic_load_4'
/usr/bin/arm-linux-gnueabi-ld:

Processed: Bug#1063976 marked as pending in javaproperties

Processing control commands:

> tag -1 pending
Bug #1063976 [javaproperties] javaproperties: autopkgtest regression with 
pytest 8
Added tag(s) pending.

-- 
1063976: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063976
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1063976: marked as pending in javaproperties

2024-04-01 Thread Luca Boccassi

Control: tag -1 pending

Hello,

Bug #1063976 in javaproperties reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:

https://salsa.debian.org/python-team/packages/javaproperties/-/commit/644c92fa170fe0ac6f0dceb9b02e4de9747f3f96


Disable tests due to API breakage in pytest 8

Closes: #1063976


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1063976

Processed: your mail

Processing commands for cont...@bugs.debian.org:

> reassign 1068140 src:flint
Bug #1068140 [flint] polymake: FTBFS: dpkg-shlibdeps: error: no dependency 
information found for /lib/x86_64-linux-gnu/libflint.so.19 (used by 
debian/libpolymake4.11/usr/lib/libpolymake.so.4.11)
Bug reassigned from package 'flint' to 'src:flint'.
Ignoring request to alter found versions of bug #1068140 to the same values 
previously set
Ignoring request to alter fixed versions of bug #1068140 to the same values 
previously set
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1068140: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068140
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: tagging 1067568

Processing commands for cont...@bugs.debian.org:

> tags 1067568 + sid
Bug #1067568 {Done: Jeremy Sowden } [emacs-pdf-tools] 
emacs-pdf-tools: [time_t] Remove hardcoded dependency on libpoppler-glib8
Added tag(s) sid.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1067568: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067568
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1067274: marked as done (normaliz: FTBFS: ld: /usr/lib/gcc/x86_64-linux-gnu/13/../../../x86_64-linux-gnu/libeantic.so: undefined reference to `_fmpq_canonicalise')

Your message dated Mon, 01 Apr 2024 12:21:45 +
with message-id 
and subject line Bug#1067274: fixed in normaliz 3.10.2+ds-2~exp1
has caused the Debian Bug report #1067274,
regarding normaliz: FTBFS: ld: 
/usr/lib/gcc/x86_64-linux-gnu/13/../../../x86_64-linux-gnu/libeantic.so: 
undefined reference to `_fmpq_canonicalise'
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1067274: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067274
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: normaliz
Version: 3.10.2+ds-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240319 ftbfs-trixie

Hi,

During a rebuild of all packages in sid, your package failed to build
on amd64.


Relevant part (hopefully):
> /usr/bin/ld: warning: libflint.so.18, needed by 
> /usr/lib/gcc/x86_64-linux-gnu/13/../../../x86_64-linux-gnu/libeanticxx.so, 
> not found (try using -rpath or -rpath-link)
> /usr/bin/ld: 
> /usr/lib/gcc/x86_64-linux-gnu/13/../../../x86_64-linux-gnu/libeantic.so: 
> undefined reference to `_fmpq_canonicalise'
> /usr/bin/ld: 
> /usr/lib/gcc/x86_64-linux-gnu/13/../../../x86_64-linux-gnu/libeantic.so: 
> undefined reference to `arb_get_lbound_arf'
> /usr/bin/ld: 
> /usr/lib/gcc/x86_64-linux-gnu/13/../../../x86_64-linux-gnu/libeantic.so: 
> undefined reference to `nf_elem_equal_si'
> /usr/bin/ld: 
> /usr/lib/gcc/x86_64-linux-gnu/13/../../../x86_64-linux-gnu/libeantic.so: 
> undefined reference to `fmpz_poly_fit_length'
> /usr/bin/ld: 
> /usr/lib/gcc/x86_64-linux-gnu/13/../../../x86_64-linux-gnu/libeantic.so: 
> undefined reference to `fmpq_mul_2exp'
> /usr/bin/ld: 
> /usr/lib/gcc/x86_64-linux-gnu/13/../../../x86_64-linux-gnu/libeantic.so: 
> undefined reference to `nf_elem_sub_si'
> /usr/bin/ld: 
> /usr/lib/gcc/x86_64-linux-gnu/13/../../../x86_64-linux-gnu/libeantic.so: 
> undefined reference to `arf_get_fmpq'
> /usr/bin/ld: 
> /usr/lib/gcc/x86_64-linux-gnu/13/../../../x86_64-linux-gnu/libeantic.so: 
> undefined reference to `fmpz_sub'
> /usr/bin/ld: 
> /usr/lib/gcc/x86_64-linux-gnu/13/../../../x86_64-linux-gnu/libeantic.so: 
> undefined reference to `arb_mul_fmpz'
> /usr/bin/ld: 
> /usr/lib/gcc/x86_64-linux-gnu/13/../../../x86_64-linux-gnu/libeantic.so: 
> undefined reference to `arb_sub_fmpz'
> /usr/bin/ld: 
> /usr/lib/gcc/x86_64-linux-gnu/13/../../../x86_64-linux-gnu/libeanticxx.so: 
> undefined reference to `fmpq_init_set_readonly'
> /usr/bin/ld: 
> /usr/lib/gcc/x86_64-linux-gnu/13/../../../x86_64-linux-gnu/libeantic.so: 
> undefined reference to `arb_is_positive'
> /usr/bin/ld: 
> /usr/lib/gcc/x86_64-linux-gnu/13/../../../x86_64-linux-gnu/libeantic.so: 
> undefined reference to `nf_elem_scalar_div_si'
> /usr/bin/ld: 
> /usr/lib/gcc/x86_64-linux-gnu/13/../../../x86_64-linux-gnu/libeantic.so: 
> undefined reference to `fmpq_poly_is_one'
> /usr/bin/ld: 
> /usr/lib/gcc/x86_64-linux-gnu/13/../../../x86_64-linux-gnu/libeantic.so: 
> undefined reference to `arb_sub'
> /usr/bin/ld: 
> /usr/lib/gcc/x86_64-linux-gnu/13/../../../x86_64-linux-gnu/libeantic.so: 
> undefined reference to `fmpz_poly_set'
> /usr/bin/ld: 
> /usr/lib/gcc/x86_64-linux-gnu/13/../../../x86_64-linux-gnu/libeantic.so: 
> undefined reference to `nf_elem_add'
> /usr/bin/ld: 
> /usr/lib/gcc/x86_64-linux-gnu/13/../../../x86_64-linux-gnu/libeantic.so: 
> undefined reference to `fmpq_poly_print_pretty'
> /usr/bin/ld: 
> /usr/lib/gcc/x86_64-linux-gnu/13/../../../x86_64-linux-gnu/libeantic.so: 
> undefined reference to `arb_lt'
> /usr/bin/ld: 
> /usr/lib/gcc/x86_64-linux-gnu/13/../../../x86_64-linux-gnu/libeantic.so: 
> undefined reference to `fmpz_divexact'
> /usr/bin/ld: 
> /usr/lib/gcc/x86_64-linux-gnu/13/../../../x86_64-linux-gnu/libeantic.so: 
> undefined reference to `nf_elem_sub'
> /usr/bin/ld: 
> /usr/lib/gcc/x86_64-linux-gnu/13/../../../x86_64-linux-gnu/libeantic.so: 
> undefined reference to `fmpz_poly_set_coeff_fmpz'
> /usr/bin/ld: 
> /usr/lib/gcc/x86_64-linux-gnu/13/../../../x86_64-linux-gnu/libeantic.so: 
> undefined reference to `arb_gt'
> /usr/bin/ld: 
> /usr/lib/gcc/x86_64-linux-gnu/13/../../../x86_64-linux-gnu/libeanticxx.so: 
> undefined reference to `_fmpz_poly_content'
> /usr/bin/ld: 
> /usr/lib/gcc/x86_64-linux-gnu/13/../../../x86_64-linux-gnu/libeantic.so: 
> undefined reference to `fmpz_mul_2exp'
> /usr/bin/ld: 
> /usr/lib/gcc/x86_64-linux-gnu/13/../../../x86_64-linux-gnu/libeantic.so: 
> undefined reference to `fmpz_add'
> /usr/bin/ld: 
> /usr/lib/gcc/x86_64-linux-gnu/13/../../../x86_64-linux-gnu/libeantic.so: 
> undefined reference to

Processed: Re: Bug#1068140: polymake: FTBFS: dpkg-shlibdeps: error: no dependency information found for /lib/x86_64-linux-gnu/libflint.so.19 (used by debian/libpolymake4.11/usr/lib/libpolymake.so.4.11

Processing control commands:

> affects -1 src:polymake
Bug #1068140 [flint] polymake: FTBFS: dpkg-shlibdeps: error: no dependency 
information found for /lib/x86_64-linux-gnu/libflint.so.19 (used by 
debian/libpolymake4.11/usr/lib/libpolymake.so.4.11)
Added indication that 1068140 affects src:polymake

-- 
1068140: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068140
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1068140: polymake: FTBFS: dpkg-shlibdeps: error: no dependency information found for /lib/x86_64-linux-gnu/libflint.so.19 (used by debian/libpolymake4.11/usr/lib/libpolymake.so.4.11)

Control: affects -1 src:polymake

On 2024-04-01 08:46:44 -0300, David Bremner wrote:
> Control: reassign -1 flint
> 
> Sebastian Ramacher  writes:
> 
> > Source: polymake
> > Version: 4.11-2
> > Severity: serious
> > Tags: ftbfs
> > Justification: fails to build from source (but built successfully in the 
> > past)
> > X-Debbugs-Cc: sramac...@debian.org
> >
> > https://buildd.debian.org/status/fetch.php?pkg=polymake=amd64=4.11-2%2Bb4=1711743555=0
> 
> As I said the previous two times this bug was reported, as far as I know
> this has to be a bug (uncoordinated transition) in flint.

Let's make sure that it is visible for polymake then. Otherwise I'll
file it a third time ;)

Cheers
-- 
Sebastian Ramacher

Processed: Re: Bug#1068140: polymake: FTBFS: dpkg-shlibdeps: error: no dependency information found for /lib/x86_64-linux-gnu/libflint.so.19 (used by debian/libpolymake4.11/usr/lib/libpolymake.so.4.11

Processing control commands:

> reassign -1 flint
Bug #1068140 [src:polymake] polymake: FTBFS: dpkg-shlibdeps: error: no 
dependency information found for /lib/x86_64-linux-gnu/libflint.so.19 (used by 
debian/libpolymake4.11/usr/lib/libpolymake.so.4.11)
Bug reassigned from package 'src:polymake' to 'flint'.
No longer marked as found in versions polymake/4.11-2.
Ignoring request to alter fixed versions of bug #1068140 to the same values 
previously set

-- 
1068140: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068140
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1068140: polymake: FTBFS: dpkg-shlibdeps: error: no dependency information found for /lib/x86_64-linux-gnu/libflint.so.19 (used by debian/libpolymake4.11/usr/lib/libpolymake.so.4.11)

2024-04-01 Thread David Bremner

Control: reassign -1 flint

Sebastian Ramacher  writes:

> Source: polymake
> Version: 4.11-2
> Severity: serious
> Tags: ftbfs
> Justification: fails to build from source (but built successfully in the past)
> X-Debbugs-Cc: sramac...@debian.org
>
> https://buildd.debian.org/status/fetch.php?pkg=polymake=amd64=4.11-2%2Bb4=1711743555=0

As I said the previous two times this bug was reported, as far as I know
this has to be a bug (uncoordinated transition) in flint.

I guess I can stop building polymake against flint, but really
someone(TM) should fix flint. The fact that it uses a hardcoded shlibs
file instead of symbols is a bit worrying for me.

Bug#1067115: marked as done (gross: CVE-2023-52159)

Your message dated Mon, 01 Apr 2024 11:47:08 +
with message-id 
and subject line Bug#1067115: fixed in gross 1.0.2-4.1~deb12u1
has caused the Debian Bug report #1067115,
regarding gross: CVE-2023-52159
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1067115: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067115
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gross
Version: 1.0.2-4
Severity: grave
Tags: security upstream
Justification: user security hole
X-Debbugs-Cc: car...@debian.org, Debian Security Team 

Hi,

The following vulnerability was published for gross.

CVE-2023-52159[0]:
| A stack-based buffer overflow vulnerability in gross 0.9.3 through
| 1.x before 1.0.4 allows remote attackers to trigger a denial of
| service (grossd daemon crash) or potentially execute arbitrary code
| in grossd via crafted SMTP transaction parameters that cause an
| incorrect strncat for a log entry.


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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2023-52159
https://www.cve.org/CVERecord?id=CVE-2023-52159
[1] 
https://codeberg.org/bizdelnick/gross/wiki/Known-vulnerabilities#cve-2023-52159

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: gross
Source-Version: 1.0.2-4.1~deb12u1
Done: Adrian Bunk 

We believe that the bug you reported is fixed in the latest version of
gross, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1067...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Adrian Bunk  (supplier of updated gross package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 29 Mar 2024 22:52:55 +0200
Source: gross
Architecture: source
Version: 1.0.2-4.1~deb12u1
Distribution: bookworm
Urgency: high
Maintainer: Antonio Radici 
Changed-By: Adrian Bunk 
Closes: 1067115
Changes:
 gross (1.0.2-4.1~deb12u1) bookworm; urgency=medium
 .
   * Non-maintainer upload.
   * Rebuild for bookworm.
 .
 gross (1.0.2-4.1) unstable; urgency=high
 .
   * Non-maintainer upload.
   * CVE-2023-52159: Stack-based buffer overflow (Closes: #1067115)
Checksums-Sha1:
 bae100e2f26a5a73e74b5856aec709072dd25696 1869 gross_1.0.2-4.1~deb12u1.dsc
 00961feb7b9c8330bb6db2a33b8d5c378c1eaee2 317461 gross_1.0.2.orig.tar.gz
 9e4a6b15539d88a8d575eda307c164596fc49e07 7036 
gross_1.0.2-4.1~deb12u1.debian.tar.xz
Checksums-Sha256:
 4aeb80cc898ba43fa203e38fdd37fdf5668f4d3b6c9877f4330fd93d5b176ed8 1869 
gross_1.0.2-4.1~deb12u1.dsc
 8443b9ba46537ed6470bda60109df68d40d3dd11b9f5a07c9180cb01af7147f9 317461 
gross_1.0.2.orig.tar.gz
 f939750976aaa43c21061869b1d94ee677c7e138f8cd473d5f153f833e2e6264 7036 
gross_1.0.2-4.1~deb12u1.debian.tar.xz
Files:
 92992bb50c38e4aa96f2374a78e876aa 1869 mail extra gross_1.0.2-4.1~deb12u1.dsc
 cb88d88553161c01e9bed7a74c3e9263 317461 mail extra gross_1.0.2.orig.tar.gz
 e4b6aa33fa6b2caab03018e75c1cac22 7036 mail extra 
gross_1.0.2-4.1~deb12u1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAmYHLBoACgkQiNJCh6LY
mLGjcxAAliyTQjMcFCzTDsd0vHwLcNuby0r+bYHciFv3b7ybAGX69Pzqw9Dk7qAK
PqvINaRI6GRW1xlnGB4r30FbgeokTD7COVkfyeII8CojgaEkqWRWvH4mwj+7kliS
jS1BZcw7iyXBEQHxYHAiv5t/H5mUEW0Rb26LgrFrVPdBdprWoUvjNfzoFBWPhj+l
uN3YHRbfI/G1Y4o4aumia70OA7ToGbotRM3DYe20LTi5RlbMbqwwKtaTf1fMT8mF
VbOnwtGVu+MvtWOp6nKvY3KJ3Vdr3jjeJur73F71eD3GzPb4n/rR+2VoTTQ5m5Bz
tnJEU80JX1XjU1JVhttgyxeUcOrjf9hvSdom1nr5B5CIPNKb9LtLoH782bvif3H1
2wM85p65cZXqDDx35Fyk/kjYCFB2OUHCaWoa4DXiDKzWF2zEIilDDtOuWD6qod3q
22Onc+ZqWxxJYTQ8jjDjrOggoQQW9kqnPpsKvxFgMW/YD5FP04cUmMaDx1RxWRlr
h1xTaNAQocqcY50wrRDU6gpmnbfPBfK+9leN4/MuLvWKJ8so4KvQAur+reJJir3x
M5nR6ZF2x4AMKCc3kKEfzjLE05J5Ma6NnlsoPRBXIQkVsfWciGGLuuNvzziSvfY8
iHsvOkQ09UovJx/6jR77E7s1PvsiDsojprwbHKR/2qtm3kDTRDo=
=OXb5
-END PGP SIGNATURE-



pgpAi7PruHb8O.pgp
Description: PGP signature
--- End Message ---

Processed: forcibly merging 1067070 1067219