Bug#1050867: marked as pending in jekyll

[Sébastien Villemot]

Le mardi 05 septembre 2023 à 21:02 -0300, Antonio Terceiro a écrit :
> yes. I just submitted a stable update bug about it (#1051302)

This is great, thanks!

-- 
⢀⣴⠾⠻⢶⣦⠀  Sébastien Villemot
⣾⠁⢠⠒⠀⣿⡁  Debian Developer
⢿⡄⠘⠷⠚⠋⠀  https://sebastien.villemot.name
⠈⠳⣄  https://www.debian.org




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

Bug#1051353: freecad: Can't create window in arch workbench

[Petter Reinholdtsen]

Control: tags -1 + patch

For the record, I was mistaken about the problem also being present in
FreeCAD 0.21.  I was comparing against the wrong file locally to come to
this incorrect conclusion.  The follow change to the problematic
getargspec() calls are lifted from upstream.  Can you test to see if it
solve your problem?  There are other changes in 0.21 to this file, and I
am unsure if any of them are needed.  It might be a better idea to
upgrade FreeCAD in Debian to 0.21 instead of backporting this fix.

--- a/src/Mod/Draft/draftguitools/gui_snapper.py
+++ b/src/Mod/Draft/draftguitools/gui_snapper.py
@@ -1426,7 +1426,7 @@ class Snapper:
 Gui.Snapper.off()
 self.ui.offUi()
 if callback:
-if len(inspect.getargspec(callback).args) > 1:
+if len(inspect.getfullargspec(callback).args) > 1:
 obj = None
 if self.snapInfo and ("Object" in self.snapInfo) and 
self.snapInfo["Object"]:
 obj = 
App.ActiveDocument.getObject(self.snapInfo["Object"])
@@ -1445,7 +1445,7 @@ class Snapper:
 Gui.Snapper.off()
 self.ui.offUi()
 if callback:
-if len(inspect.getargspec(callback).args) > 1:
+if len(inspect.getfullargspec(callback).args) > 1:
 callback(None, None)
 else:
 callback(None)


-- 
Happy hacking
Petter Reinholdtsen

Bug#1034668: Please update to new upstream release 3.22.3 in experimental

[GCS]

Hi Nilesh, Benjamin,

On Sat, Jul 22, 2023 at 5:06 AM Nilesh Patra  wrote:
> On Thu, 27 Apr 2023 19:59:38 +0530 Pirate Praveen  
> wrote:
> >  Target "tests" links to:
> >
> >absl::scoped_mock_log
> >
> >  but the target was not found. Possible reasons include:
 The reason is that it and protobuf 3.24.2 need abseil 20230125.0 or
newer. While it is available in experimental, it doesn't export
scoped_mock_log targets for cmake. Hence it is not found, I don't know
if newer versions like 20230802.0 fix this issue or not. Can you
comment on this Benjamin and if you are going to package it soon
and/or accept someone as a co-maintainer for abseil? It seems abseil
20230802.0 became available and should be packaged.

> Now, the release of abseil in experimental seems to be doing that, but
> only for the static library and not the shared library, because it needs
> googltest for the same, and googletest does not vendor any shared
> library because the SO lib is not maintained properly upstream[2] [...]
[...]
> This was straightforward was to add "-Dprotobuf_BUILD_TESTS=OFF" to
> configure options.
 Building without tests are always a bad idea.

> PS: Sponsor me a party/dinner when?
 If you are at DebConf, we may talk and eat together.

Regards,
Laszlo/GCS

Bug#1051238: ITP: biome -- formatter and linter for web languages

[Jonas Smedegaard]

Quoting Edward Little (2023-09-06 23:03:30)
> Please remove this email address from list.  Thanks.  e.little...@gmail.com

I cannot remove you, you will need to do that yourself.

Most likely (but check the email headers of the previous email) you
received it through a subscription to the Debian JavaScript team
mailinglist.

Kind regards,

 - Jonas

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

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

signature.asc
Description: signature

Bug#1050547:

[Hor Jiun Shyong]

Hi,

After updating Debian today with below packages,  Gnome still starts with
white screen.  Error as below.  Thanks.

gnome-shell:amd64 (44.3-5, 44.4-1),
mutter:amd64 (44.3-7, 44.4-2)
linux-image-6.4.0-4-amd64:amd64 (6.4.13-1, automatic),
linux-image-amd64:amd64 (6.4.11-1, 6.4.13-1),

  Start-Date: 2023-09-07  12:17:22
  Commandline: apt-get dist-upgrade -V
  Install: linux-image-6.4.0-4-amd64:amd64 (6.4.13-1, automatic),
linux-kbuild-6.4.0-4:amd64 (6.4.13-1, automatic),
linux-headers-6.4.0-4-amd64:amd64 (6.4.13-1, automatic), linux-headers-6.4.
 0-4-common:amd64 (6.4.13-1, automatic)
  Upgrade: libnghttp2-14:amd64 (1.55.1-1, 1.56.0-1), python3-brlapi:amd64
(6.6-2, 6.6-4), mutter-common-bin:amd64 (44.3-7, 44.4-2), xbrlapi:amd64
(6.6-2, 6.6-4), libldb2:amd64 (2:2.7.2+samba4  .18.6+dfsg-1,
2:2.8.0+samba4.19.0+dfsg-1), libbrlapi0.8:amd64 (6.6-2, 6.6-4),
libmutter-12-0:amd64 (44.3-7, 44.4-2), virtinst:amd64 (1:4.1.0-2,
1:4.1.0-3), linux-compiler-gcc-13-x86:amd64 (  6.4.11-1, 6.4.13-1),
libwbclient0:amd64 (2:4.18.6+dfsg-1, 2:4.19.0+dfsg-1),
linux-headers-amd64:amd64 (6.4.11-1, 6.4.13-1), libsmbclient:amd64
(2:4.18.6+dfsg-1, 2:4.19.0+dfsg-1), mutter-com  mon:amd64 (44.3-7, 44.4-2),
gnome-shell:amd64 (44.3-5, 44.4-1), linux-image-amd64:amd64 (6.4.11-1,
6.4.13-1), libnet-http-perl:amd64 (6.22-1, 6.23-1), gir1.2-mutter-12:amd64
(44.3-7, 44.4-2  ), gnome-shell-common:amd64 (44.3-5, 44.4-1),
libmozjs-102-0:amd64 (102.14.0-1, 102.15.0-1), mutter:amd64 (44.3-7,
44.4-2), python3-ldb:amd64 (2:2.7.2+samba4.18.6+dfsg-1, 2:2.8.0+samba4.19.
 0+dfsg-1), libsdl2-2.0-0:amd64 (2.28.2+dfsg-1, 2.28.3+dfsg-1),
samba-libs:amd64 (2:4.18.6+dfsg-1, 2:4.19.0+dfsg-1), virt-viewer:amd64
(11.0-2, 11.0-3), gnome-shell-extension-prefs:amd64 (44  .3-5, 44.4-1),
linux-libc-dev:amd64 (6.4.11-1, 6.4.13-1)
  End-Date: 2023-09-07  12:19:30


   17.787657] gnome-shell[1684]: segfault at 18 ip 7f62cfcced54 sp
7ffcfcdeff98 error 4 in libmutter-12.so.0.0.0[7f62cfc4e000+156000]
likely on CPU 2 (core 1, socket 0)
[   17.787670] Code: c7 e8 10 44 f8 ff e9 6f fe ff ff 0f 1f 00 c7 43 60 00
00 00 00 e8 cc 9a f8 ff e9 3a fe ff ff 0f 1f 80 00 00 00 00 f3 0f 1e fa
<48> 8b 47 18 c3 0f 1f 80 00 00 00 00 f3 0f 1e fa 55 48 89 f5 53 48
[   18.415736] gnome-shell[1715]: segfault at 18 ip 7f9f416ced54 sp
7ffc3a4e58a8 error 4 in libmutter-12.so.0.0.0[7f9f4164e000+156000]
likely on CPU 4 (core 2, socket 0)
[   18.415750] Code: c7 e8 10 44 f8 ff e9 6f fe ff ff 0f 1f 00 c7 43 60 00
00 00 00 e8 cc 9a f8 ff e9 3a fe ff ff 0f 1f 80 00 00 00 00 f3 0f 1e fa
<48> 8b 47 18 c3 0f 1f 80 00 00 00 00 f3 0f 1e fa 55 48 89 f5 53 48

Regards,
Hor Jiun Shyong 何俊雄

Bug#1051304: error: out of memory

[Daniel Richard G.]

Hi Julian,

On Wed, 2023 Sep  6 04:17-04:00, Julian Andres Klode wrote:
>
> Yes, so please just try the 2.12~rc1-9 in unstable and see if it
> fixes your issue.

I've confirmed that this version no longer gives the "out of memory"
error, and can load and boot the ISO images that previously failed.

Is this a long way from making it into stable? Or at least -backports?

-- 
Daniel Richard G. || sk...@iskunk.org
My ASCII-art .sig got a bad case of Times New Roman.

Bug#1051380: transition: rocksdb

[GCS]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: transition
Control: affects -1 + src:rocksdb

Hi RMs,

Small transition of rocksdb as only two packages are affected: balboa
and sortmerna. Both build fine with the 8.5.3 version of rocksdb
already in experimental.
Only thing to mention is that the testing version of sortmerna doesn't
build with the new rocksdb version - but as I know it doesn't cause
any issue as binNMUs happen in unstable.

Thanks for considering,
Laszlo/GCS

Bug#1051379: ITP: usbrip -- USB device artifacts tracker

[Josenilson Ferreira da Silva]

Package: wnpp
Severity: wishlist
Owner: Josenilson Ferreira da Silva 
X-Debbugs-Cc: debian-de...@lists.debian.org, nilsonfsi...@hotmail.com

* Package name: usbrip
  Version : 0.14.2
  Upstream Contact: Sam Freeside
* URL : snovvcr...@protonmail.ch
* License : (GPL-3
  Programming Lang: Python
  Description : USB device artifacts tracker
 
 USB device forensic analysis tool for Linux systems.
 It is designed to assist in the investigation of activities related
 to USB devices such as USB sticks and USB storage devices.
 usbrip runs from the command line, which allows its integration
 in automated scripts and workflows

Bug#1051378: ruby-ffi:Add types.conf for loongarch64-linux

[Zang Ruochen]

Package: ruby-ffi
Version: 1.15.5+dfsg-1
Severity: wishlist
Tags: patch
User:debian-de...@lists.debian.org
Usertags: loongarch64

Dear ruby-ffi maintainers,

The ruby-ffi master already supports loongarch64, but the latest release has 
not yet added support for loongarch64. we have added patch for ruby-ffi package.

[1]:
Add types.conf for loongarch64-linux · ffi/ffi@5153384 · GitHub 



thanks,
Zang Ruochen
From 5153384b330ccf1ecf07a98cbc5ea1a291f6059c Mon Sep 17 00:00:00 2001
From: wangluwei 
Date: Thu, 3 Mar 2022 16:13:54 +0800
Subject: [PATCH] Add types.conf for loongarch64-linux

---
 lib/ffi/platform/loongarch64-linux/types.conf | 141 ++
 1 file changed, 141 insertions(+)
 create mode 100644 lib/ffi/platform/loongarch64-linux/types.conf

diff --git a/lib/ffi/platform/loongarch64-linux/types.conf 
b/lib/ffi/platform/loongarch64-linux/types.conf
new file mode 100644
index 0..aa8716d8c
--- /dev/null
+++ b/lib/ffi/platform/loongarch64-linux/types.conf
@@ -0,0 +1,141 @@
+rbx.platform.typedef.*__caddr_t = char
+rbx.platform.typedef.__blkcnt64_t = long
+rbx.platform.typedef.__blkcnt_t = long
+rbx.platform.typedef.__blksize_t = int
+rbx.platform.typedef.__clock_t = long
+rbx.platform.typedef.__clockid_t = int
+rbx.platform.typedef.__daddr_t = int
+rbx.platform.typedef.__dev_t = ulong
+rbx.platform.typedef.__fd_mask = long
+rbx.platform.typedef.__fsblkcnt64_t = ulong
+rbx.platform.typedef.__fsblkcnt_t = ulong
+rbx.platform.typedef.__fsfilcnt64_t = ulong
+rbx.platform.typedef.__fsfilcnt_t = ulong
+rbx.platform.typedef.__fsword_t = long
+rbx.platform.typedef.__gid_t = uint
+rbx.platform.typedef.__id_t = uint
+rbx.platform.typedef.__ino64_t = ulong
+rbx.platform.typedef.__ino_t = ulong
+rbx.platform.typedef.__int16_t = short
+rbx.platform.typedef.__int32_t = int
+rbx.platform.typedef.__int64_t = long
+rbx.platform.typedef.__int8_t = char
+rbx.platform.typedef.__int_least16_t = short
+rbx.platform.typedef.__int_least32_t = int
+rbx.platform.typedef.__int_least64_t = long
+rbx.platform.typedef.__int_least8_t = char
+rbx.platform.typedef.__intmax_t = long
+rbx.platform.typedef.__intptr_t = long
+rbx.platform.typedef.__key_t = int
+rbx.platform.typedef.__loff_t = long
+rbx.platform.typedef.__mode_t = uint
+rbx.platform.typedef.__nlink_t = uint
+rbx.platform.typedef.__off64_t = long
+rbx.platform.typedef.__off_t = long
+rbx.platform.typedef.__pid_t = int
+rbx.platform.typedef.__priority_which_t = int
+rbx.platform.typedef.__quad_t = long
+rbx.platform.typedef.__rlim64_t = ulong
+rbx.platform.typedef.__rlim_t = ulong
+rbx.platform.typedef.__rlimit_resource_t = int
+rbx.platform.typedef.__rusage_who_t = int
+rbx.platform.typedef.__sig_atomic_t = int
+rbx.platform.typedef.__socklen_t = uint
+rbx.platform.typedef.__ssize_t = long
+rbx.platform.typedef.__suseconds_t = long
+rbx.platform.typedef.__syscall_slong_t = long
+rbx.platform.typedef.__syscall_ulong_t = ulong
+rbx.platform.typedef.__time_t = long
+rbx.platform.typedef.__timer_t = pointer
+rbx.platform.typedef.__u_char = uchar
+rbx.platform.typedef.__u_int = uint
+rbx.platform.typedef.__u_long = ulong
+rbx.platform.typedef.__u_quad_t = ulong
+rbx.platform.typedef.__u_short = ushort
+rbx.platform.typedef.__uid_t = uint
+rbx.platform.typedef.__uint16_t = ushort
+rbx.platform.typedef.__uint32_t = uint
+rbx.platform.typedef.__uint64_t = ulong
+rbx.platform.typedef.__uint8_t = uchar
+rbx.platform.typedef.__uint_least16_t = ushort
+rbx.platform.typedef.__uint_least32_t = uint
+rbx.platform.typedef.__uint_least64_t = ulong
+rbx.platform.typedef.__uint_least8_t = uchar
+rbx.platform.typedef.__uintmax_t = ulong
+rbx.platform.typedef.__useconds_t = uint
+rbx.platform.typedef.blkcnt_t = long
+rbx.platform.typedef.blksize_t = int
+rbx.platform.typedef.clock_t = long
+rbx.platform.typedef.clockid_t = int
+rbx.platform.typedef.daddr_t = int
+rbx.platform.typedef.dev_t = ulong
+rbx.platform.typedef.fd_mask = long
+rbx.platform.typedef.fsblkcnt_t = ulong
+rbx.platform.typedef.fsfilcnt_t = ulong
+rbx.platform.typedef.gid_t = uint
+rbx.platform.typedef.id_t = uint
+rbx.platform.typedef.in_addr_t = uint
+rbx.platform.typedef.in_port_t = ushort
+rbx.platform.typedef.ino_t = ulong
+rbx.platform.typedef.int16_t = short
+rbx.platform.typedef.int32_t = int
+rbx.platform.typedef.int64_t = long
+rbx.platform.typedef.int8_t = char
+rbx.platform.typedef.int_fast16_t = long
+rbx.platform.typedef.int_fast32_t = long
+rbx.platform.typedef.int_fast64_t = long
+rbx.platform.typedef.int_fast8_t = char
+rbx.platform.typedef.int_least16_t = short
+rbx.platform.typedef.int_least32_t = int
+rbx.platform.typedef.int_least64_t = long
+rbx.platform.typedef.int_least8_t = char
+rbx.platform.typedef.intmax_t = long
+rbx.platform.typedef.intptr_t = long
+rbx.platform.typedef.key_t = int
+rbx.platform.typedef.loff_t = long
+rbx.platform.typedef.mode_t = uint
+rbx.platform.typedef.nlink_t = uint

Bug#1037840: Fwd: regina-normal: ftbfs with GCC-13

[Jonathan Bergh]

Control: tags 1037840 + patch

Resending with corrected control tag


patch.debdiff
Description: Binary data

Bug#1037907: yrmcds: ftbfs with GCC-13

[Jonathan Bergh]

Control: tags 1037907 + patch

Fix FTBFS for 1037907


patch.debdiff
Description: Binary data

Bug#1037882: vart: ftbfs with GCC-13

[Jonathan Bergh]

Control: tags 1037882 + patch

patch attached to deal with change to gcc-13


patch.debdiff
Description: Binary data

Bug#1029238: export PATH=$PATH:/usr/libexec/imv

[肖盛文]

Hi

    You may add the following line to your ~/.bashrc file:

export PATH=$PATH:/usr/libexec/imv

If you don't install renameutils package in your system, you may run 
this imv now.


As renameutils package already ship /usr/bin/imv command before,
so the imv package must to avoid a file name clash with the renameutils 
package.



Regards,

--
肖盛文 xiao sheng wen
https://www.atzlinux.com 《铜豌豆 Linux》基于 Debian 的 Linux 中文 桌面 操作系统
Debian QA page: https://qa.debian.org/developer.php?login=atzlinux%40sina.com
Debian salsa: https://salsa.debian.org/atzlinux-guest
GnuPG Public Key: 0x00186602339240CB



OpenPGP_signature
Description: OpenPGP digital signature

Bug#1051377: RM: ulex0.8 -- ROM; no more rdeps; FTBFS

[Stéphane Glondu]

Package: ftp.debian.org
Severity: normal
User: ftp.debian@packages.debian.org
Usertags: remove
X-Debbugs-Cc: ulex...@packages.debian.org, debian-ocaml-ma...@lists.debian.org
Control: affects -1 + src:ulex0.8

Dear FTP team,

ulex0.8 was kind of a transitional package (cf #436982) that has no
more reverse dependencies. Moreover, it fails to build from source
with camlp5 8.02.x. I think it's time to remove it.

Note that it is known as ulex-camlp5 in opam, and it has no reverse
dependencies there.


Cheers,

-- 
Stéphane

Bug#1050854: python-xarray: autopkgtest failures

[Gianfranco Costamagna]

Hello, due to tzdata split, we need an additional patch:

https://github.com/pydata/xarray/pull/8153

From cadeae171e882736e7e6b0dc79150627faf37f58 Mon Sep 17 00:00:00 2001
From: Gianfranco Costamagna 
Date: Thu, 7 Sep 2023 03:35:49 +0200
Subject: [PATCH 1/2] tests: Update US/Eastern timezone to America/New_York

Reason is that US/Eastern symlink moved from tzdata to tzdata-legacy package,
causing FTBFS. Since America/New_York is better supported by tzdata,
the switch makes the package stronger against future failures
---
 xarray/tests/test_dataset.py  |  2 +-
 xarray/tests/test_variable.py | 18 +-
 2 files changed, 10 insertions(+), 10 deletions(-)

diff --git a/xarray/tests/test_dataset.py b/xarray/tests/test_dataset.py
index e119cfe9bc..19fd78daf0 100644
--- a/xarray/tests/test_dataset.py
+++ b/xarray/tests/test_dataset.py
@@ -4698,7 +4698,7 @@ def 
test_convert_dataframe_with_many_types_and_multiindex(self) -> None:
 "e": [True, False, True],
 "f": pd.Categorical(list("abc")),
 "g": pd.date_range("20130101", periods=3),
-"h": pd.date_range("20130101", periods=3, tz="US/Eastern"),
+"h": pd.date_range("20130101", periods=3, 
tz="America/New_York"),
 }
 )
 df.index = pd.MultiIndex.from_product([["a"], range(3)], names=["one", 
"two"])
diff --git a/xarray/tests/test_variable.py b/xarray/tests/test_variable.py
index f30cdcf3f7..b09426c5d3 100644
--- a/xarray/tests/test_variable.py
+++ b/xarray/tests/test_variable.py
@@ -2604,7 +2604,7 @@ def test_datetime(self):
 
 @requires_pandas_version_two

 def test_tz_datetime(self) -> None:
-tz = pytz.timezone("US/Eastern")
+tz = pytz.timezone("America/New_York")
 times_ns = pd.date_range("2000", periods=1, tz=tz)
 
 times_s = times_ns.astype(pd.DatetimeTZDtype("s", tz))

@@ -2904,9 +2904,9 @@ def test_from_pint_wrapping_dask(self, Var):
 (pd.date_range("2000", periods=1), False),
 (datetime(2000, 1, 1), False),
 (np.array([datetime(2000, 1, 1)]), False),
-(pd.date_range("2000", periods=1, tz=pytz.timezone("US/Eastern")), 
False),
+(pd.date_range("2000", periods=1, 
tz=pytz.timezone("America/New_York")), False),
 (
-pd.Series(pd.date_range("2000", periods=1, 
tz=pytz.timezone("US/Eastern"))),
+pd.Series(pd.date_range("2000", periods=1, 
tz=pytz.timezone("America/New_York"))),
 False,
 ),
 ],
@@ -2929,7 +2929,7 @@ def test_datetime_conversion_warning(values, 
warns_under_pandas_version_two) ->
 # the case that the variable is backed by a timezone-aware
 # DatetimeIndex, and thus is hidden within the PandasIndexingAdapter 
class.
 assert var._data.array.dtype == pd.DatetimeTZDtype(
-"ns", pytz.timezone("US/Eastern")
+"ns", pytz.timezone("America/New_York")
 )
 
 
@@ -2941,12 +2941,12 @@ def test_pandas_two_only_datetime_conversion_warnings() -> None:

 (pd.date_range("2000", periods=1), "datetime64[s]"),
 (pd.Series(pd.date_range("2000", periods=1)), "datetime64[s]"),
 (
-pd.date_range("2000", periods=1, tz=pytz.timezone("US/Eastern")),
-pd.DatetimeTZDtype("s", pytz.timezone("US/Eastern")),
+pd.date_range("2000", periods=1, 
tz=pytz.timezone("America/New_York")),
+pd.DatetimeTZDtype("s", pytz.timezone("America/New_York")),
 ),
 (
-pd.Series(pd.date_range("2000", periods=1, 
tz=pytz.timezone("US/Eastern"))),
-pd.DatetimeTZDtype("s", pytz.timezone("US/Eastern")),
+pd.Series(pd.date_range("2000", periods=1, 
tz=pytz.timezone("America/New_York"))),
+pd.DatetimeTZDtype("s", pytz.timezone("America/New_York")),
 ),
 ]
 for data, dtype in cases:
@@ -2960,7 +2960,7 @@ def test_pandas_two_only_datetime_conversion_warnings() 
-> None:
 # the case that the variable is backed by a timezone-aware
 # DatetimeIndex, and thus is hidden within the PandasIndexingAdapter 
class.
 assert var._data.array.dtype == pd.DatetimeTZDtype(
-"ns", pytz.timezone("US/Eastern")
+"ns", pytz.timezone("America/New_York")
 )
 
 


From 8b5a187d12294a40c21701fcea3ef1b78de65f11 Mon Sep 17 00:00:00 2001
From: "pre-commit-ci[bot]"
 <66853113+pre-commit-ci[bot]@users.noreply.github.com>
Date: Thu, 7 Sep 2023 01:43:49 +
Subject: [PATCH 2/2] [pre-commit.ci] auto fixes from pre-commit.com hooks

for more information, see https://pre-commit.ci
---
 xarray/tests/test_variable.py | 8 ++--
 1 file changed, 6 insertions(+), 2 deletions(-)

diff --git a/xarray/tests/test_variable.py b/xarray/tests/test_variable.py
index b09426c5d3..9ecc3ace3c 100644
--- a/xarray/tests/test_variable.py
+++ b/xarray/tests/test_variable.py
@@ -2906,7 +2906,9 @@ def test_from_pint_wrapping_dask(self, Var):
 

Bug#1051376: lftp: Please update the outdated config.guess and config.sub to recognize the LoongArch

[zhangdandan]

Source: lftp
Version: 4.9.2-2
Severity: wishlist
Tags: patch
User: debian-de...@lists.debian.org
Usertags: loongarch64

   Dear maintainers,

When compiling the package lftp for loong64 in the Debian Package 
Auto-Building environment [1], The error message is as follows:

..omit
checking build system type... Invalid configuration 
`loongarch64-linux-gnu': machine `loongarch64' not recognized
configure: error: /bin/bash build-aux/config.sub loongarch64-linux-gnu 
failed

make: *** [debian/rules:24: configure-stamp] Error 1
..omit

The full compilation log can be found at [2].
The version of config.guess and config.sub in the lftp source package 
are too old for the LoongArch architecture.


The LoongArch architecture has been supported in config upstream [3] and 
autotools-dev source package [4].


Please consider the patch (modify debian/rules) I have attached.
Alternatively, update the config.guess and config.sub files, see the 
merge request for lftp [5].

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


[1]:https://buildd.debian.org/status/package.php?p=lftp=sid
[2]:https://buildd.debian.org/status/fetch.php?pkg=lftp=loong64=4.9.2-2%2Bb1=1693579710=0
[3]:https://git.savannah.gnu.org/cgit/config.git/commit/?id=20403c5701973a4cbd7e0b4bbeb627fcd424a0f1
[4]:https://packages.debian.org/bookworm/autotools-dev
[5]:https://salsa.debian.org/debian/lftp/-/merge_requests/2

thanks,
Dandan Zhang

diff -Nru lftp-4.9.2/debian/rules lftp-4.9.2/debian/rules
--- lftp-4.9.2/debian/rules 2018-09-17 07:33:33.0 +
+++ lftp-4.9.2/debian/rules 2022-07-16 10:24:04.0 +
@@ -20,6 +20,7 @@
 #configure: configure-stamp
 configure-stamp:
dh_testdir
+   dh_update_autotools_config
# Add here commands to configure the package.
CFLAGS="$(CFLAGS)" CXXFLAGS="$(CXXFLAGS)" CPPFLAGS="$(CPPFLAGS)" 
LDFLAGS="$(LDFLAGS)" ./configure \
--prefix=/usr \

Bug#1050688: poetry: needs internet access during build?

[Emmanuel Arias]

Hi again,

OK, now I have a theory. In all the tests (or at least the tests that I
looked) intervene a egg-info folder. But now this folder is removed by
dh-python.

Cheers,
Emmanuel


signature.asc
Description: PGP signature

Bug#1051375: libcairo2-dev: missing-pkgconfig-dependency cairo-script-interpreter => lzo2

[Paul Wise]

Package: libcairo2-dev
Version: 1.17.8-3
Severity: normal

The libcairo2-dev package is missing some sort of relationship with the
liblzo2-dev package because the cairo-script-interpreter.pc file
references the lzo2.pc file in Requires.private. Most uses of the
cairo-script-interpreter.pc file probably aren't for static linking
in Debian so probably Recommends or Suggests would be enough.

This bug report brought to you by adequate:

https://bonedaddy.net/pabs3/log/2013/02/23/inadequate-software/

$ pkg1=libcairo2-dev

$ adequate libcairo2-dev
libcairo2-dev:amd64: missing-pkgconfig-dependency cairo-script-interpreter => 
lzo2

$dpkg -L libcairo2-dev | grep -F cairo-script-interpreter.pc
/usr/lib/x86_64-linux-gnu/pkgconfig/cairo-script-interpreter.pc

$ grep lzo2 /usr/lib/x86_64-linux-gnu/pkgconfig/cairo-script-interpreter.pc
Requires.private: zlib, libpng, fontconfig >=  2.2.95, freetype2 >=  9.7.3, 
x11, xext, xrender >=  0.6, xcb >=  1.6, xcb-render >=  1.6, xcb-shm, pixman-1 
>=  0.36.0, lzo2

$ apt-file search lzo2.pc
liblzo2-dev: /usr/lib/x86_64-linux-gnu/pkgconfig/lzo2.pc

$ apt-cache show libcairo2-dev | grep liblzo2-dev

$ COLUMNS=80 man adequate | grep -A5 pkgconfig
   missing-pkgconfig-dependency
   Dependency of a pkg-config (.pc) file shipped by this package
   couldn't be satisfied.

   References: Debian Policy §8.4.

-- System Information:
Debian Release: trixie/sid
  APT prefers testing-debug
  APT policy: (900, 'testing-debug'), (900, 'testing'), (800, 
'unstable-debug'), (800, 'unstable'), (790, 'buildd-unstable'), (700, 
'experimental-debug'), (700, 'experimental'), (690, 'buildd-experimental')
Architecture: amd64 (x86_64)

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

Versions of packages libcairo2-dev depends on:
ii  libcairo-gobject2 1.17.8-3
ii  libcairo-script-interpreter2  1.17.8-3
ii  libcairo2 1.17.8-3
ii  libfontconfig-dev 2.14.2-4
ii  libfreetype-dev   2.13.2+dfsg-1
ii  libglib2.0-dev2.77.2-1
ii  libpixman-1-dev   0.42.2-1
ii  libpng-dev1.6.40-1
ii  libsm-dev 2:1.2.3-1
ii  libx11-dev2:1.8.6-1
ii  libxcb-render0-dev1.15-1
ii  libxcb-shm0-dev   1.15-1
ii  libxcb1-dev   1.15-1
ii  libxext-dev   2:1.3.4-1+b1
ii  libxrender-dev1:0.9.10-1.1

libcairo2-dev recommends no packages.

Versions of packages libcairo2-dev suggests:
pn  libcairo2-doc  

-- no debconf information

-- 
bye,
pabs

https://wiki.debian.org/PaulWise


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

Bug#1050688: poetry: needs internet access during build?

[Emmanuel Arias]

Hi Gianfranco,

Thanks for you report, and sorry for the delay. I'm investigating the
issues. I can not says that they need internet connection but I did not
finish to check all tests.

This error seems strange to me because they run successfully some days
ago.

Cheers,
Emmanuel


signature.asc
Description: PGP signature

Bug#1051371: debian-policy: stop referring to legacy filesystem paths for script interpreters

[Luca Boccassi]

On Thu, 7 Sept 2023 at 00:45, Sam Hartman  wrote:
>
> > "Luca" == Luca Boccassi  writes:
> Luca> How would such a change look like?
>
> I looked at your patch.
>
> In most of the cases you are changing non-normative language.
> That is, parts of policy that do not create a requirement.
> For example:
> >Scripts may assume that "/bin/sh" implements the POSIX.1-2017 Shell
> >Command Language  [7] plus the following additional features not
> >mandated by POSIX.1-2017.. [8]
>
> That creates no requirement on a package.
>
> >* The term *may* and the adjective *optional* are used to clarify
> >  cases where it may otherwise appear that Policy is specifying a
> >  requirement or recommendation. In those cases, these words describe
>
> I.E. in the cases you adjust, I think it is already
> not a bug, and it would be inappropriate to use existing policy language
> to complain about which interpreter path people use.

In practice though they are used as normative, for example Lintian
raises an error (not even a warning, an actual error). So given they
are not literally normative, wouldn't it be fine to change them, or
alternatively drop any specific path mention? That way there is no
doubt that we can change Lintian and close such bugs. Right now it's
not that clear at all, as evidenced by Lintian and these bugs.

> There is one case however where I think your patch adjusts normative
> language.
>
> I propose the following adjustment to your patch.  Rather than mandating
> a particular path for a csh interpreter, make it clear that the policy
> requirement is that the csh script start with a #! line rather than
> simply assuming csh will interpret the script as was all too common back
> in the days of csh:
>
> @@ -266,7 +266,7 @@ including ``open``, ``print``, ``close``, ``rename`` and 
> ``system``.
>  Programming Considered Harmful*, one of the ``comp.unix.*`` FAQs, which
>  can be found at http://www.faqs.org/faqs/unix-faq/shell/csh-whynot/. If
>  an upstream package comes with ``csh`` scripts then you must make sure
> -that they start with ``#!/bin/csh`` and make your package depend on the
> +that they start with the path of a csh interpreter such as ``#!/bin/csh`` 
> and make your package depend on the
>  ``c-shell`` virtual package.
>
>  Any scripts which create files in world-writeable directories (e.g., in

How about:

+that they start with the path of a csh interpreter such as
``#!/bin/csh`` or other valid paths, and make your package depend on
the

Bug#1051371: debian-policy: stop referring to legacy filesystem paths for script interpreters

[Sam Hartman]

> "Luca" == Luca Boccassi  writes:
Luca> How would such a change look like?

I looked at your patch.

In most of the cases you are changing non-normative language.
That is, parts of policy that do not create a requirement.
For example:
>Scripts may assume that "/bin/sh" implements the POSIX.1-2017 Shell
>Command Language  [7] plus the following additional features not
>mandated by POSIX.1-2017.. [8]

That creates no requirement on a package.

>* The term *may* and the adjective *optional* are used to clarify
>  cases where it may otherwise appear that Policy is specifying a
>  requirement or recommendation. In those cases, these words describe

I.E. in the cases you adjust, I think it is already
not a bug, and it would be inappropriate to use existing policy language
to complain about which interpreter path people use.

There is one case however where I think your patch adjusts normative
language.

I propose the following adjustment to your patch.  Rather than mandating
a particular path for a csh interpreter, make it clear that the policy
requirement is that the csh script start with a #! line rather than
simply assuming csh will interpret the script as was all too common back
in the days of csh:

@@ -266,7 +266,7 @@ including ``open``, ``print``, ``close``, ``rename`` and 
``system``.
 Programming Considered Harmful*, one of the ``comp.unix.*`` FAQs, which
 can be found at http://www.faqs.org/faqs/unix-faq/shell/csh-whynot/. If
 an upstream package comes with ``csh`` scripts then you must make sure
-that they start with ``#!/bin/csh`` and make your package depend on the
+that they start with the path of a csh interpreter such as ``#!/bin/csh`` and 
make your package depend on the
 ``c-shell`` virtual package.

 Any scripts which create files in world-writeable directories (e.g., in

I think the other hunks of your patch are unnecessary to avoid policy be
used to create bugs in this space.

Bug#998408: "good password" advice in installer is still bad two years after this was reported

[Philip Hands]

Jonathan Kamens  writes:

> Oh, I see now that the fact that the installer shouldn't recommend 
> changing one's password regularly was also reported previously, in bug 
> #868869.

Also, in #656509 (in which Cyril states that the effort of translating a
new message outweighs the importance of the change).

I've no idea if that justification for inaction still stands, but I
thought this would make a nice little example for the use of the
salsa-CI pipeline (and my branch2repo variant of that), so here's an MR:

  https://salsa.debian.org/installer-team/user-setup/-/merge_requests/7

and here's a screenshot of what the change looks like:

  https://openqa.debian.net/tests/185853#step/passwords/1

I'm not 100% happy with the wording (and the underlines around 'should'
need to go) so I'm very likely to tweak it tomorrow.

Suggestions for improvement welcome, although be aware that given the
resistance to fixing this in the past, it's always possible such a
change will also be deemed unjustified now.

I think it's probably about time we fixed it, since even the civil
servants in the UK have stopped recommending password changes by now,
and they tend to make such changes at least a decade late. ;-)

Cheers, Phil.
-- 
Philip Hands -- https://hands.com/~phil


signature.asc
Description: PGP signature

Bug#1051373: libglib2.0-0: 2.77.3-1 breaks Midnight Commander extension file

[Philip Withnall]

See upstream report
https://gitlab.gnome.org/GNOME/glib/-/issues/3095#note_1839091, which
will be fixed upstream for 2.78.0, which is due to be released in the
next couple of days.

Philip

On Wed, 2023-09-06 at 22:49 +, Michael Gold wrote:
> Package: libglib2.0-0
> Version: 2.77.3-1
> Severity: important
> 
> Dear Maintainer,
> 
> After upgrading libglib2.0-0 from 2.77.2-1 to 2.77.3-1, I'm no longer
> able to open files by selecting them in Midnight Commander and
> pressing
> Enter.  A change in the behaviour of g_key_file_get_string() appears
> to
> be the cause.  For example, one section of the mc.ext.ini file
> contains:
> [pdf]
> Regex=\.(pdf|PDF|ps|djvu)$
> Open=pdf %f &
> 
> With the new package, a call to g_key_file_get_string() for the
> "Regex"
> value returns NULL.  If I pre-load the old library version, it
> returns
> the string, and mc executes the specified command if I press Enter
> with
> a PDF file selected.
> 
> The package version of "mc" is "3:4.8.29-2".
> 
> - Michael
> 
> 
> -- System Information:
> Debian Release: trixie/sid
>   APT prefers unstable-debug
>   APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1,
> 'experimental')
> Architecture: amd64 (x86_64)
> 
> Kernel: Linux 6.4.0-4-amd64 (SMP w/32 CPU threads; PREEMPT)
> Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8),
> LANGUAGE=en_CA:en
> Shell: /bin/sh linked to /usr/bin/dash
> Init: systemd (via /run/systemd/system)
> LSM: AppArmor: enabled
> 
> Versions of packages libglib2.0-0 depends on:
> ii  libc6 2.37-7
> ii  libffi8   3.4.4-1
> ii  libmount1 2.39.2-1
> ii  libpcre2-8-0  10.42-4
> ii  libselinux1   3.5-1
> ii  zlib1g    1:1.2.13.dfsg-3
> 
> Versions of packages libglib2.0-0 recommends:
> ii  libglib2.0-data   2.77.3-1
> ii  shared-mime-info  2.2-1
> ii  xdg-user-dirs 0.18-1
> 
> Versions of packages libglib2.0-0 suggests:
> pn  low-memory-monitor  
> 
> -- no debconf information

Bug#1051373: libglib2.0-0: 2.77.3-1 breaks Midnight Commander extension file

[Michael Gold]

Package: libglib2.0-0
Version: 2.77.3-1
Severity: important

Dear Maintainer,

After upgrading libglib2.0-0 from 2.77.2-1 to 2.77.3-1, I'm no longer
able to open files by selecting them in Midnight Commander and pressing
Enter.  A change in the behaviour of g_key_file_get_string() appears to
be the cause.  For example, one section of the mc.ext.ini file contains:
[pdf]
Regex=\.(pdf|PDF|ps|djvu)$
Open=pdf %f &

With the new package, a call to g_key_file_get_string() for the "Regex"
value returns NULL.  If I pre-load the old library version, it returns
the string, and mc executes the specified command if I press Enter with
a PDF file selected.

The package version of "mc" is "3:4.8.29-2".

- Michael


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

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

Versions of packages libglib2.0-0 depends on:
ii  libc6 2.37-7
ii  libffi8   3.4.4-1
ii  libmount1 2.39.2-1
ii  libpcre2-8-0  10.42-4
ii  libselinux1   3.5-1
ii  zlib1g1:1.2.13.dfsg-3

Versions of packages libglib2.0-0 recommends:
ii  libglib2.0-data   2.77.3-1
ii  shared-mime-info  2.2-1
ii  xdg-user-dirs 0.18-1

Versions of packages libglib2.0-0 suggests:
pn  low-memory-monitor  

-- no debconf information


signature.asc
Description: PGP signature

Bug#1051371: debian-policy: stop referring to legacy filesystem paths for script interpreters

[Luca Boccassi]

On Wed, 6 Sept 2023 at 23:51, Sam Hartman  wrote:
>
> > "Luca" == Luca Boccassi  writes:
> Luca> /bin/sh is not universally compatible with non-Linux OSes.
>
> I claim it is more compatible.
>
> Luca> Also I thought that policy should not be used to beat other
> Luca> developers (it is because of this) and it should reflect the
> Luca> common practices adopted in Debian (it does not because of
> Luca> this). Is that no longer the case?
>
> I'd consider it a non-RC bug if someone were manually writing
> #!/usr/bin/sh
>
> We can debate about normal vs minor.
>
> I do not think it should be a bug if some automated build process found
> /usr/bin/sh and stuck that into a script.
> I'd support a policy change to make that clear.

How would such a change look like?

Bug#1051314: fonts-recommended: recognise noto-core as alternative to dejavu-core

[Adam Borowski]

On Wed, Sep 06, 2023 at 07:22:36AM +0100, Justin B Rye wrote:
> Package: fonts-recommended
> Version: 1
> Severity: wishlist

> Various major desktops now default to fonts-noto-core instead of
> fonts-dejavu-core.   During a conversation with a fontconfig-config
> maintainer on debian-l10n-english about the knock-on effects
> ("https://lists.debian.org/debian-l10n-english/2023/09/msg1.html;)
> I noticed that the dependency chains ensuring that fonts-noto-core is
> actually installed at all are surprisingly weak.
> 
> This font package used to be very nearly the only one I needed to have
> manually installed to ensure I got everything I was likely to want

Alas, noto has the downside of making font pickers next to useless, as
it declares every single of languages it supports as a separate font family.
So instead off just "Noto Sans" "Noto Mono" "Noto Slightly Serifed", you
have "Noto Western Klingon" "Noto Eastern Klingon" and so on, making the
list of available fonts one big noto fest.

Given that you can install Noto yourself if that is your choice, removing
any need for this metapackage, I don't quite see the point of declaring
an alternative.  On the other hand, Dejavu has the technical quirk of
having been taken for granted for so long by random pieces of software,
I'd rather not skip it.  Somehow despite Noto's ubiquity in the Android
world this is not the case for it, as software doesn't get ported (at least,
not without significant changes) between Android and regular OSes much.

I thus consider removing all (or most) alternatives here, and make this
metapackage a single opinionated set.  Alternatives are good for tasks/etc
where there's a serious downside to having them not installed -- for a
set of fonts, not so much.


Meow!
-- 
⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁
⢿⡄⠘⠷⠚⠋⠀ ᛊᚨᚾᛁᛏᚣ᛫ᛁᛊ᛫ᚠᛟᚱ᛫ᚦᛖ᛫ᚹᛖᚨᚲ
⠈⠳⣄

Bug#1051374: breaks existing setups using /etc/default/mini-httpd

[Johannes Schauer Marin Rodrigues]

Package: mini-httpd
Version: 1.30-4
Severity: serious

Hi,

after an upgrade to mini-httpd 1.30-4 my setup stopped working. It seems
that this new version changed the init script for a systemd unit where
the latter ignores the contents of /etc/default/mini-httpd.

If that is intentional and not an oversight, there should at least be a
NEWS entry so that users upgrading to 1.30-4 learn about this breaking
change and are also told how to convert their existing configuration to
the new style.

If possible it would of course be nice if the systemd service would not
break user's setups and would continue to consume /etc/default/mini-httpd.

Thanks!

cheers, josch

Bug#1051371: debian-policy: stop referring to legacy filesystem paths for script interpreters

[Sam Hartman]

> "Luca" == Luca Boccassi  writes:
Luca> /bin/sh is not universally compatible with non-Linux OSes.

I claim it is more compatible.


Luca> Also I thought that policy should not be used to beat other
Luca> developers (it is because of this) and it should reflect the
Luca> common practices adopted in Debian (it does not because of
Luca> this). Is that no longer the case?

I'd consider it a non-RC bug if someone were manually writing
#!/usr/bin/sh

We can debate about normal vs minor.

I do not think it should be a bug if some automated build process found
/usr/bin/sh and stuck that into a script.
I'd support a policy change to make that clear.

Bug#1051353: freecad: Can't create window in arch workbench

[Petter Reinholdtsen]

[philippe]
> It seems to be a conflict with phyton version (getargspec seems to be
> depracted)

Thank you for discovering this problem. :)

While I doubt 'grave' is the correct severity for this, as it do not
render FreeCAD completely useless that one of the workbenches do not
work, and I personally is using the Part Design and Part
workbenches with success, I can reproduce the issue and the problem seem
to be due to python version incompatibility.

The method is present in Python 3.8[1], but not in 3.11[2] used in Debian
at the moment.  Only the recommended replacement getfullargspec() is
present in 3.11.  This issue need to be fixed upstream, as it is also
present in version 0.21.

[1] https://docs.python.org/3.8/library/inspect.html#inspect.getargspec >
[2] https://docs.python.org/3.11/library/inspect.html#inspect.getfullargspec >
-- 
Happy hacking
Petter Reinholdtsen

Bug#1051371: debian-policy: stop referring to legacy filesystem paths for script interpreters

[Luca Boccassi]

On Wed, 6 Sept 2023 at 23:34, Sam Hartman  wrote:
>
> > "Luca" == Luca Boccassi  writes:
>
> Luca> Debian only supports merged-usr since Bookworm. We should
> Luca> update policy to reference /usr/bin/sh and similar paths to
> Luca> describe recommended shebangs for scripts.
>
> I do not support this change.  /bin/sh should still be the recommended
> interface path for the posix shell.  Among other reasons, it promotes
> compatibility between Linux and other posix architectures.  Besides
> that, I suspect there are cases where tools look for /bin/sh in a #!
> line and do not accept /usr/bin/sh.

/bin/sh is not universally compatible with non-Linux OSes.

Also I thought that policy should not be used to beat other developers
(it is because of this) and it should reflect the common practices
adopted in Debian (it does not because of this). Is that no longer the
case?

Bug#1035312: minetest: New upstream version available (5.7.0)

[tuxayo]

On Sun, 23 Jul 2023 10:10:17 +0200 Tobias Frost  wrote:

--> we will need to use the bundled lua.


As a blanket solution yes. But IIUC it seems running the tests can tell 
if a given Debian version is affected:


https://github.com/minetest/minetest/issues/12778#issuecomment-1250255332
> Effects you can expect if the test fails: Minetest continues to work 
mostly normally, but memory leaks can happen and error handling might 
not work correctly in edge cases.


Cheers,

--
tuxayo

Bug#1049902: raspi-firmware on non-rpi arm64

[Adam Borowski]

gwolf wrote:
> The only risk I can think of is that the bug might still impact users of
> non-Raspberry ARM systems. However, the likelihood of having it installed is
> minor (due to the available hardware being different).

Given that the laptop I use on the DebConf right now has 100% likelihood of
having this firmware installed (because of no network otherwise), you might
want to test stuff on it.

On the other hand, while the package can't be removed nor upgraded without
manually messing with both the hook and the postinst, it couldn't be
installed in the first place without doing so as well, thus people are at
least aware.  Thus, my priority is in getting rid of raspi-only bits...

In any case, I'd be glad helping test -- and you can put your hands on
this box if you fancy so.


Meow!
-- 
⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁
⢿⡄⠘⠷⠚⠋⠀ ᛊᚨᚾᛁᛏᚣ᛫ᛁᛊ᛫ᚠᛟᚱ᛫ᚦᛖ᛫ᚹᛖᚨᚲ
⠈⠳⣄

Bug#1051371: debian-policy: stop referring to legacy filesystem paths for script interpreters

[Sam Hartman]

> "Luca" == Luca Boccassi  writes:

Luca> Debian only supports merged-usr since Bookworm. We should
Luca> update policy to reference /usr/bin/sh and similar paths to
Luca> describe recommended shebangs for scripts.

I do not support this change.  /bin/sh should still be the recommended
interface path for the posix shell.  Among other reasons, it promotes
compatibility between Linux and other posix architectures.  Besides
that, I suspect there are cases where tools look for /bin/sh in a #!
line and do not accept /usr/bin/sh.

I absolutely agree that the physical path of the posix shell should be
/usr/bin/sh.
I disagree that we should be changing interface paths for items
traditionally found in /bin.


signature.asc
Description: PGP signature

Bug#1038911: goldencheetah: diff for NMU version 1:3.5-1.2

[Gianfranco Costamagna]

Control: tags 1038911 + patch
Control: tags 1038911 + pending

Dear maintainer,

I've prepared an NMU for goldencheetah (versioned as 1:3.5-1.2) and
uploaded it.

Regards.

diff -Nru goldencheetah-3.5/debian/changelog goldencheetah-3.5/debian/changelog
--- goldencheetah-3.5/debian/changelog  2021-02-07 13:29:13.0 +0100
+++ goldencheetah-3.5/debian/changelog  2023-09-07 00:14:26.0 +0200
@@ -1,3 +1,10 @@
+goldencheetah (1:3.5-1.2) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * switch from libcurl4-nss-dev to libcurl4-openssl-dev (Closes: #1038911)
+
+ -- Gianfranco Costamagna   Thu, 07 Sep 2023 
00:14:26 +0200
+
 goldencheetah (1:3.5-1.1) unstable; urgency=medium

   * Non-maintainer upload.
diff -Nru goldencheetah-3.5/debian/control goldencheetah-3.5/debian/control
--- goldencheetah-3.5/debian/control2020-07-25 02:03:49.0 +0200
+++ goldencheetah-3.5/debian/control2023-09-07 00:14:24.0 +0200
@@ -7,7 +7,7 @@
  , bison
  , flex
  , libboost-dev
- , libcurl4-nss-dev
+ , libcurl4-openssl-dev
  , zlib1g-dev
  , libgcrypt-dev
  , libnss3



OpenPGP_signature
Description: OpenPGP digital signature

Bug#967716: qiv: depends on deprecated GTK 2

[Bastian Germann]

With pqiv, there is a gtk3 version of qiv already in the archive.
Maybe, qiv should be a made a transitional package to that one?

Bug#1051372: Ctrl-F crashes thunderbird in nl_NL.UTF-8 locale

[David Mandelberg]

Package: thunderbird-l10n-nl
Version: 1:115.2.0-1

If I run `env -u LOCPATH -u LANGUAGE LANG=nl_NL.UTF-8 thunderbird` and 
hit Ctrl-F to find text within an email, thunderbird crashes. If I do 
the same thing with `env -u LOCPATH -u LANGUAGE LANG=en_US.UTF-8 
thunderbird` instead, it doesn't crash. Using `/` instead of Ctrl-F 
works in either locale.

Bug#1051031: libvmime: diff for NMU version 0.9.2-8.1

[Gianfranco Costamagna]

Control: tags 1051031 + patch
Control: tags 1051031 + pending


Dear maintainer,

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

Regards.

diff -Nru libvmime-0.9.2/debian/changelog libvmime-0.9.2/debian/changelog
--- libvmime-0.9.2/debian/changelog 2022-01-22 12:20:47.0 +0100
+++ libvmime-0.9.2/debian/changelog 2023-09-07 00:08:37.0 +0200
@@ -1,3 +1,11 @@
+libvmime (0.9.2-8.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Change libgsasl7-dev into libgsasl-dev following Debian
+package renaming (Closes: #1051031)
+
+ -- Gianfranco Costamagna   Thu, 07 Sep 2023 
00:08:37 +0200
+
 libvmime (0.9.2-8) unstable; urgency=medium

   * [4fe0f91] Rebuild patch queue from patch-queue branch
diff -Nru libvmime-0.9.2/debian/control libvmime-0.9.2/debian/control
--- libvmime-0.9.2/debian/control   2022-01-22 12:11:27.0 +0100
+++ libvmime-0.9.2/debian/control   2023-09-07 00:08:31.0 +0200
@@ -7,7 +7,7 @@
   debhelper-compat (= 13),
   libgtk-3-dev,
   libgnutls28-dev (>= 3.4.0),
-  libgsasl7-dev,
+  libgsasl-dev,
   sendmail,
 Build-Depends-Indep:
   asciidoc-base,
@@ -25,7 +25,7 @@
 Architecture: any
 Depends:
   libgnutls28-dev (>= 3.4.0~),
-  libgsasl7-dev,
+  libgsasl-dev,
   libvmime1 (= ${binary:Version}),
   ${misc:Depends},
 Description: C++ mail library (development files)



OpenPGP_signature
Description: OpenPGP digital signature

Bug#1051371: debian-policy: stop referring to legacy filesystem paths for script interpreters

[Edward Little]

Unsubscribe:

 e.little...@gmail.com

On Wed, Sep 6, 2023 at 5:54 PM Luca Boccassi  wrote:

> Package: debian-policy
> X-Debbugs-Cc: j...@debian.org hel...@subdivi.de
>
> Debian only supports merged-usr since Bookworm. We should update policy
> to reference /usr/bin/sh and similar paths to describe recommended
> shebangs for scripts.
>
> I heard many times the policy maintainers mention something along the
> lines of 'policy should not be a hammer to beat other maintainers
> with'. Today I saw policy being used to force a maintainer to re-add
> support for the deprecated and unsupported split-usr filesystem layout,
> as 'policy only mentions /bin/sh, not /usr/bin/sh'.
>
> So let's update the policy to refer to modern and supported filesystem
> paths as adopted by Debian de-facto and de-jure, and stop other
> maintainers from getting beaten with it.
>
> Patch attached and also pushed to
> https://salsa.debian.org/bluca/policy/-/tree/bin_sh
>
> --
> Kind regards,
> Luca Boccassi
>

Bug#1041866: Package: geeqie

[Andreas Rönnquist]

On Mon, 24 Jul 2023 18:07:03 +0200
Florian Cramer  wrote:

>Package: geeqie
>
>geeqie (version 1:2.0.1-8+b2, Trixie package) depends on the
>package liblua5.1-0 . However, liblua5.1-0 is not included in the
>dependencies of Trixie's geeqie package and needs to be manually installed.
>Without an installed liblua5.1-0, geeqie quit upon launch with an
>error message about liblua5.1.so.0 missing.
>
>I am using Debian Trixie with kernel 6.3.0-1-amd64 #1 SMP PREEMPT_DYNAMIC
>Debian 6.3.7-1 (2023-06-12) x86_64 GNU/Linux.

Are you on amd64? The geeqie package should depend on
liblua5.3-0 (and according to https://packages.debian.org/sid/geeqie it
claims to do just that on all architectures except m68k, sh4 and x32).

I just tested on unstable, removed liblua5.1-0 and liblua5.1-0-dev, and
started geeqie - which worked just fine, with only Lua 5.3 installed.

/Andreas Rönnquist
gus...@debian.org

Bug#1051371: debian-policy: stop referring to legacy filesystem paths for script interpreters

[Luca Boccassi]

Package: debian-policy
X-Debbugs-Cc: j...@debian.org hel...@subdivi.de

Debian only supports merged-usr since Bookworm. We should update policy
to reference /usr/bin/sh and similar paths to describe recommended
shebangs for scripts.

I heard many times the policy maintainers mention something along the
lines of 'policy should not be a hammer to beat other maintainers
with'. Today I saw policy being used to force a maintainer to re-add
support for the deprecated and unsupported split-usr filesystem layout,
as 'policy only mentions /bin/sh, not /usr/bin/sh'.

So let's update the policy to refer to modern and supported filesystem
paths as adopted by Debian de-facto and de-jure, and stop other
maintainers from getting beaten with it.

Patch attached and also pushed to
https://salsa.debian.org/bluca/policy/-/tree/bin_sh

-- 
Kind regards,
Luca Boccassi
From  Mon Sep 17 00:00:00 2001
From: Luca Boccassi 
Date: Wed, 6 Sep 2023 22:41:58 +0100
Subject: [PATCH] Stop referring to legacy filesystem paths for shebangs

Debian only supports merged-usr since bookworm. Use /usr/bin/sh and
similar paths to describe recommended shebangs for scripts.
---
 policy/ch-files.rst | 14 +++---
 1 file changed, 7 insertions(+), 7 deletions(-)

diff --git a/policy/ch-files.rst b/policy/ch-files.rst
index b34c183..ff9b2f6 100644
--- a/policy/ch-files.rst
+++ b/policy/ch-files.rst
@@ -211,8 +211,8 @@ may instead be easier to check the exit status of commands directly. See
 Every script should use ``set -e`` or check the exit status of *every*
 command.
 
-Scripts may assume that ``/bin/sh`` implements the POSIX.1-2017 Shell Command
-Language  [#]_ plus the following additional features not mandated by
+Scripts may assume that ``/usr/bin/sh`` implements the POSIX.1-2017 Shell
+Command Language  [#]_ plus the following additional features not mandated by
 POSIX.1-2017.. [#]_
 
 -  ``echo -n``, if implemented as a shell built-in, must not generate a
@@ -248,16 +248,16 @@ POSIX.1-2017.. [#]_
 
 If a shell script requires non-POSIX.1-2017 features from the shell interpreter
 other than those listed above, the appropriate shell must be specified
-in the first line of the script (e.g., ``#!/bin/bash``) and the package
+in the first line of the script (e.g., ``#!/usr/bin/bash``) and the package
 must depend on the package providing the shell (unless the shell package
 is marked "Essential", as in the case of ``bash``).
 
 You may wish to restrict your script to POSIX.1-2017 features plus the above
-set when possible so that it may use ``/bin/sh`` as its interpreter.
+set when possible so that it may use ``/usr/bin/sh`` as its interpreter.
 Checking your script with ``checkbashisms`` from the devscripts package
 or running your script with an alternate shell such as ``posh`` may help
 uncover violations of the above requirements. If in doubt whether a
-script complies with these requirements, use ``/bin/bash``.
+script complies with these requirements, use ``/usr/bin/bash``.
 
 Perl scripts should check for errors when making any system calls,
 including ``open``, ``print``, ``close``, ``rename`` and ``system``.
@@ -266,7 +266,7 @@ including ``open``, ``print``, ``close``, ``rename`` and ``system``.
 Programming Considered Harmful*, one of the ``comp.unix.*`` FAQs, which
 can be found at http://www.faqs.org/faqs/unix-faq/shell/csh-whynot/. If
 an upstream package comes with ``csh`` scripts then you must make sure
-that they start with ``#!/bin/csh`` and make your package depend on the
+that they start with ``#!/usr/bin/csh`` and make your package depend on the
 ``c-shell`` virtual package.
 
 Any scripts which create files in world-writeable directories (e.g., in
@@ -780,7 +780,7 @@ restricted to ASCII when it is possible to do so.
 .. [#]
These features are in widespread use in the Linux community and are
implemented in all of bash, dash, and ksh, the most common shells
-   users may wish to use as ``/bin/sh``.
+   users may wish to use as ``/usr/bin/sh``.
 
 .. [#]
This is necessary to allow top-level directories to be symlinks. If


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

Bug#1051370: howdoi: Fails to find help on any topic

[Pelle]

Package: howdoi
Version: 1.1.9-1.1
Severity: grave
Justification: renders package unusable

Dear maintainer of howdoi,

I can't seem to get howdoi to find any help:

$ howdoi format date bash
Sorry, couldn't find any help with that topic

$ howdoi print stack trace python
Sorry, couldn't find any help with that topic

$ howdoi howdoi
Sorry, couldn't find any help with that topic

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

Kernel: Linux 6.4.0-3-amd64 (SMP w/4 CPU threads; PREEMPT)
Kernel taint flags: TAINT_FIRMWARE_WORKAROUND
Locale: LANG=en_DK.UTF-8, LC_CTYPE=en_DK.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 howdoi depends on:
ii  python3 3.11.4-5+b1
ii  python3-cssselect   1.2.0-2
ii  python3-lxml4.9.3-1
ii  python3-pygments2.15.1+dfsg-1
ii  python3-pyquery 1.4.3-1
ii  python3-requests2.31.0+dfsg-1
ii  python3-requests-cache  0.9.8-1

howdoi recommends no packages.

howdoi suggests no packages.

-- no debconf information

Bug#1051238: ITP: biome -- formatter and linter for web languages

[Edward Little]

Please remove this email address from list.  Thanks.  e.little...@gmail.com

On Mon, Sep 4, 2023 at 4:39 PM Jonas Smedegaard  wrote:

> Package: wnpp
> Severity: wishlist
> Owner: Jonas Smedegaard 
> X-Debbugs-Cc: debian-de...@lists.debian.org, Debian Javascript
> Maintainers 
>
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA512
>
> * Package name: biome
>   Version : 1.0.0
>   Upstream Contact: Rome Tools is Rome Tools, Inc.
> * URL : https://biomejs.dev/
> * License : Expat
>   Programming Lang: Rust, Node.js
>   Description : formatter and linter for web languages
>
>  Biome formats and lints your code in a fraction of a second.
>  .
>  Biome supports JavaScript, TypeScript, JSON, and CSS.
>  It aims to support all main languages of modern web development.
>  .
>  Biome has sane defaults and requires minimal configuration.
>  Biome helps you as much as possible
>  by displaying detailed and contextualized diagnostics.
>  .
>  Biome unifies functionality that has previously been separate tools.
>  Building upon a shared base allows us to provide a cohesive experience
>  for processing code, displaying errors, parallelizing work,
>  caching, and configuration.
>  .
>  Biome is designed to eventually replace Babel, ESLint, webpack,
>  Prettier, Jest, and others.
>
> This package will be maintained in the collaborative debian section of
> salsa, at https://salsa.debian.org/debian/biome
> -BEGIN PGP SIGNATURE-
>
> iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmT2P20ACgkQLHwxRsGg
> ASEZWg//TeQDd1oBh1KOyQvlEQkq6aducgElCNp/fas9oXJt+wIbw2E5o62c74Iw
> 4fqYiHJp7+hwA9Ld87G0llqdokhAPsq4+bwH21x4EDoNSaWBlcBjc1V6q8g22g/b
> xm0cI2cQKC15MhVls+WuDKpdHeGZHqxp4F3dWoCXbmJtFK82nMkWJkXZOh3UiJ+P
> /dPV5mI1Y/uexZZZmww+LKdt51ma100kZbAf+P4XgQOo43zKiiguE3RSVYd5CKgv
> 3i5i0V5OCFeoYr1vsXL2G1G0vrNZHDygJ6V88F2VpMe/AxHShLpnhL5PaQgAEFeq
> scKmLpV7blYU4qDXp3im3OP9mJsetovNLhvr0b9HuLn8U3QhmJoOZ4CoydmMAoNJ
> Kj8crKndk+ioZa3ct15SdUjOmQCrrQ5w47VjDvlyIpx7BrKeA7jquVLC367/LcZQ
> H0MyMu4Gy6YvHYKXB6OvWO8GJPJo/63vVz/AJYYuR7NT3Q0C3eBKr/VW1p555Yyd
> k/12Qv5p+QmlN0u0vniLX3i4Ftr3sGNhcjxCVAgYqsRZyTUR1rtdRgY9Bf9qTkFC
> jbdUrxrUfiyuunQimUlTDbsAIykZQac5f4cHViDWiGdCv6niAJaVQOatwFHslM4B
> SffnPOG3kdMjZpgIwlpGhVhxLEjETlPKcfE22EsOKmPiKtkzCaE=
> =fldg
> -END PGP SIGNATURE-
>
>

Bug#1043551: llvm-toolchain-(14|15): links against libcurl3-nss which will be dropped in August 2023

[Sylvestre Ledru]

merci :)

merged


Le 06/09/2023 à 22:26, Samuel Henrique a écrit :

Argh, I think the links got merged together, here are the proper ones:

llvm-toolchain-14
https://salsa.debian.org/pkg-llvm-team/llvm-toolchain/-/merge_requests/117

llvm-toolchain-15
https://salsa.debian.org/pkg-llvm-team/llvm-toolchain/-/merge_requests/118

llvm-toolchain-17
https://salsa.debian.org/pkg-llvm-team/llvm-toolchain/-/merge_requests/119

Cheers,

Bug#1051331: mmm-mode: warnings in comp when starting Emacs 29 for the first time

[Vincent Lefevre]

Control: tags -1 fixed-upstream

This was actually fixed upstream almost one year ago!

https://github.com/dgutov/mmm-mode/commit/869d5ef62896f95e52c33aea8267e986bdb7d2c3
https://github.com/dgutov/mmm-mode/commit/d5af05a4a95b4e29663b0d7815a79d3ae1793453

and these fixes should be included in 0.5.9.

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Bug#1051369: mmm-mode: please update to new upstream version 0.5.9

[Vincent Lefevre]

Package: mmm-mode
Version: 0.5.8-4
Severity: normal

Version 0.5.9 has been available since October 2022.
Please update to this version.

This should at least fix bug 1051331.

-- System Information:
Debian Release: trixie/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'stable-updates'), (500, 
'stable-security'), (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 
'experimental')
merged-usr: no
Architecture: amd64 (x86_64)

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

Versions of packages mmm-mode depends on:
ii  emacs-gtk [emacsen]  1:29.1+1-5
ii  emacsen-common   3.0.5

mmm-mode recommends no packages.

mmm-mode suggests no packages.

-- no debconf information

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Bug#1051368: python3-selenium: Selenium Python still can't find chromedriver

[Jonathan Kamens]

Package: python3-selenium
Version: 4.12.0+dfsg-1
Severity: grave
Justification: renders package unusable

Opening a new ticket since bug 1050378 is resolved and I don't know
how to reopen a resolved ticket (nor do I know if it is even possible
for me to reopen a resolved ticket).

python3-selenium 4.12.0+dfsg-1 still doesn't work.

I get this when I try to create a selenium.webdriver.Chrome object:

selenium.common.exceptions.NoSuchDriverException: Message: Unable to obtain 
driver for chrome using Selenium Manager.; For documentation on this error, 
please visit: 
https://www.selenium.dev/documentation/webdriver/troubleshooting/errors/driver_location

The ChangeLog for this release claims:

  * [5b22b76] d/README.Debian: Add section about the Selenium Manager
  * [25b0d5f] d/NEWS moved to d/python-selenium.NEWS
(Closes: #1050378)

But neither of those files exists in the python3-selenium package. Was
there an intention to add them to the package that wasn't followed
through on?

Incidentally, I took a look at README.Debian in the source package and
there are some issues with the text that may be worth fixing as well.
In particular:

>While writing it's not packaged for Debian. In order to make python3-selenium

I suggest changing "While writing" (which is not really an idiom that
is used in English) to "At this time".

>usable with this new circumstance you will need to adjust your source in a
>way to choose the used driver directly and skip the calling of the manager
>code in Selenium. Please have a look at the following example how to archive

I think you mean to say "achieve" here rather than "archive".

>this.

In any case I do not believe that documenting this deficiency in
README.Debian, even if/when it is included in the package, is a
sufficient fix for the issue. The issue IMO should remain unresolved
until Selenium Manager is properly packaged for Debian.

Thank you,

Jonathan Kamens

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

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

Versions of packages python3-selenium depends on:
ii  python3 3.11.4-5+b1
ii  python3-certifi 2022.9.24-1
ii  python3-trio0.22.2-1
ii  python3-trio-websocket  0.10.3-1
ii  python3-urllib3 1.26.16-1

Versions of packages python3-selenium recommends:
ii  chromium-driver  116.0.5845.140-1

python3-selenium suggests no packages.

-- no debconf information

Bug#1043550: llvm-toolchain-(14|15): links against libcurl3-nss which will be dropped in August 2023

[Samuel Henrique]

Argh, I think the links got merged together, here are the proper ones:

llvm-toolchain-14
https://salsa.debian.org/pkg-llvm-team/llvm-toolchain/-/merge_requests/117

llvm-toolchain-15
https://salsa.debian.org/pkg-llvm-team/llvm-toolchain/-/merge_requests/118

llvm-toolchain-17
https://salsa.debian.org/pkg-llvm-team/llvm-toolchain/-/merge_requests/119

Cheers,


-- 
Samuel Henrique 

Bug#1046738: libgmime-3.0-0: Invalid RFC 2047 token decoding logic for base64 encodings

[John Fistikis]

On Sun, 13 Aug 2023 23:59:18 +0300 Bogdan Ruslanovich Drozd 
 wrote:

Package: libgmime-3.0-0
Version: 3.2.13+dfsg-2
Severity: normal

Dear Maintainer, include the 

patch, please.

What does it fix?  This patch fix invalid decoding what leads
to distortion of the text (e.g. I use emacs+notmuch, and subjects
of some titles are cut off).




The recently released version 3.2.14 
(https://github.com/jstedfast/gmime/releases/tag/3.2.14) also fixes 
this.

Bug#1050897: updating metadata

[Helmut Grohne]

user helm...@debian.org
usertags -1 + dep17p6
thanks

Thanks to Timothy for handling all of this. He also filed a MR
https://salsa.debian.org/debian/openrc/-/merge_requests/2 to incorporate
the necessary change into the Debian package.

This bug will become release-critical once openrc moves its files from /
to /usr. Other than that, there is no particular urgency with applying
the change, because no other packages interact with the relevant
directory.

Helmut

Bug#1051367: regression: powersave screen blank causes system freeze after upgrade to Debian 12

[Marcin Owsiany]

Package: gnome
Version: 1:43+1
Severity: normal

Dear Maintainer,

After upgrading from Debian 11 to Debian 12, my system freezes hard at
the moment GNOME blanks the screen (the second setting in power saving
options in GNOME settings). Sometimes, additionally, after 10-15 more
seconds - the system hard reboots. Otherwise, I need to powercycle
manually. Either way, there is no clean shutdown.

This happens on AC power, and I confirmed this is the screen blanking,
and NOT suspend that causes this.

I also confirmed that if I switch to a text VT and leave the system
idle, the freeze does not happen.

I tried running `journalctl --follow` through an SSH connection to this
machine, but nothing appears before the connection freezes.

The system information about the computer that suffers from this problem
is below. Another laptop that I have (different hardware) running the
same software, does not exhibit this issue.

I'd be happy to try and isolate/debug this issue further, but I don't
know where to start. Hints most welcome.

regards,
Marcin

-- System Information:
Lenovo laptop: "ideapad FLEX 5-1570"
Graphics: Mesa Intel® UHD Graphics 620 (KBL GT2)
CPU: Intel® Core™ i5-8250U × 8
Using GNOME with Wayland

Debian Release: 12.1
  APT prefers stable-security
  APT policy: (500, 'stable-security'), (500, 'stable-debug'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.1.0-11-amd64 (SMP w/8 CPU threads; PREEMPT)
Locale: LANG=pl_PL.UTF-8, LC_CTYPE=pl_PL.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 gnome depends on:
ii  avahi-daemon 0.8-10
ii  cheese   43.0-1
ii  cups-pk-helper   0.2.6-1+b1
ii  desktop-base 12.0.6+nmu1~deb12u1
ii  evolution3.46.4-2
ii  evolution-plugins3.46.4-2
ii  file-roller  43.0-1
ii  gnome-calendar   43.1-2
ii  gnome-clocks 43.0-1
ii  gnome-color-manager  3.36.0-1+b1
ii  gnome-core   1:43+1
ii  gnome-maps   43.5-2~deb12u1
ii  gnome-music  42.1-1
ii  gnome-sound-recorder 43~beta-1
ii  gnome-tweaks 42~beta-4
ii  gnome-weather43.0-1
ii  gstreamer1.0-libav   1.22.0-2
ii  gstreamer1.0-plugins-ugly1.22.0-2+deb12u1
ii  libgsf-bin   1.14.50-1
ii  libproxy1-plugin-networkmanager  0.4.18-1.2
ii  libreoffice-calc 4:7.4.7-1
ii  libreoffice-gnome4:7.4.7-1
ii  libreoffice-impress  4:7.4.7-1
ii  libreoffice-writer   4:7.4.7-1
ii  network-manager-gnome1.30.0-2
ii  orca 43.1-1
ii  rhythmbox3.4.6-2+b1
ii  rhythmbox-plugin-cdrecorder  3.4.6-2+b1
ii  rhythmbox-plugins3.4.6-2+b1
ii  rygel-playbin0.42.1-1
ii  rygel-tracker0.42.1-1
ii  seahorse 43.0-1
ii  shotwell 0.30.17-1+b1
ii  simple-scan  42.5-2
ii  totem-plugins43.0-2
ii  xdg-user-dirs-gtk0.11-1

Versions of packages gnome recommends:
ii  gnome-games   1:43+1
ii  gnome-initial-setup   43.2-6
ii  gnome-remote-desktop  43.3-1
ii  transmission-gtk  3.00-2.1+b1

Versions of packages gnome suggests:
pn  alacarte  
pn  empathy   
pn  firefox-esr-l10n-all | firefox-l10n-all   
pn  goobox | sound-juicer 
pn  polari
ii  vinagre   3.22.0-8.1
pn  webext-ublock-origin-firefox | webext-ublock-origin-chromium  

Versions of packages gnome-core depends on:
ii  adwaita-icon-theme43-1
ii  at-spi2-core  2.46.0-5
ii  baobab43.0-1
ii  dconf-cli 0.40.0-4
ii  dconf-gsettings-backend   0.40.0-4
ii  eog   43.2-1
ii  evince43.1-2+b1
ii  evolution-data-server 3.46.4-2
ii  fonts-cantarell   0.303.1-1
ii  gdm3  43.0-3
ii  gkbd-capplet  3.28.1-1
ii  glib-networking   2.74.0-4
ii  gnome-backgrounds 43.1-1
ii  gnome-bluetooth-sendto42.5-3
ii  gnome-calculator  1:43.0.1-2
ii  gnome-characters  43.1-1
ii  gnome-contacts43.1-1
ii  gnome-control-center  1:43.6-2~deb12u1
ii  gnome-disk-utility43.0-1
ii  gnome-font-viewer 43.0-1
ii  gnome-keyring 

Bug#1043550: llvm-toolchain-(14|15): links against libcurl3-nss which will be dropped in August 2023

[Samuel Henrique]

Control: tags -1 patch

I've opened MRs on salsa:
llvm-toolchain-14
https://salsa.debian.org/pkg-llvm-team/llvm-toolchain/-/merge_requests/117
llvm-toolchain-15
https://salsa.debian.org/pkg-llvm-team/llvm-toolchain/-/merge_requests/118
llvm-toolchain-17
https://salsa.debian.org/pkg-llvm-team/llvm-toolchain/-/merge_requests/119

I would really appreciate it if this could be uploaded to unstable in
the next couple of days, my wish is for these fixes to get to testing
before ~15th September.

Cheers,


-- 
Samuel Henrique 

Bug#1051366: liblouisutdml FTCBFS: passes host cflags to native build

[Helmut Grohne]

Source: liblouisutdml
Version: 2.11.0-3
Tags: patch
User: debian-cr...@lists.debian.org
Usertags: ftcbfs

liblouisutdml started failing to cross build from source as dpkg
introduced arm64-specific compiler flags. The packaging passes the
host's cflags to the native build, which may not understand them. This
can easily avoided by asking debhelper to recompute the flags after
changing the architecture. I'm attaching a patch for your convenience.

Helmut
diff --minimal -Nru liblouisutdml-2.11.0/debian/changelog 
liblouisutdml-2.11.0/debian/changelog
--- liblouisutdml-2.11.0/debian/changelog   2023-06-21 10:04:56.0 
+0200
+++ liblouisutdml-2.11.0/debian/changelog   2023-09-06 10:07:26.0 
+0200
@@ -1,3 +1,10 @@
+liblouisutdml (2.11.0-3.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix FTCBFS: Do not pass host cflags to native build. (Closes: #-1)
+
+ -- Helmut Grohne   Wed, 06 Sep 2023 10:07:26 +0200
+
 liblouisutdml (2.11.0-3) unstable; urgency=medium
 
   * control, rules: Support hurd-amd64.
diff --minimal -Nru liblouisutdml-2.11.0/debian/rules 
liblouisutdml-2.11.0/debian/rules
--- liblouisutdml-2.11.0/debian/rules   2023-05-06 17:51:50.0 +0200
+++ liblouisutdml-2.11.0/debian/rules   2023-09-06 10:07:25.0 +0200
@@ -19,7 +19,7 @@
 
 override_dh_auto_configure:
 ifneq ($(DEB_BUILD_ARCH),$(DEB_HOST_ARCH))
-   dpkg-architecture -f -a$(DEB_BUILD_ARCH) -c dh_auto_configure -- 
--disable-java-bindings
+   dpkg-architecture -f -a$(DEB_BUILD_ARCH) -c dh_auto_configure 
--reload-all-buildenv-variables -- --disable-java-bindings
dpkg-architecture -f -a$(DEB_BUILD_ARCH) -c dh_auto_build
dh_auto_clean
 endif

Bug#1051365: linux: drop stage1 profile?

[Helmut Grohne]

Source: linux
Severity: wishlist
User: helm...@debian.org
Usertags: rebootstrap

Hi,

I recently captured a conversation involving Bastain saying that the
stage1 build profile was deprecated. He's right!

So I went searching for users of this profile. The most obvious user to
me is rebootstrap. It turns out that stage1 is sufficiently similar to
pkg.linux.nokernel,pkg.linux.nosource,pkg.linux.notools that I can just
use that profile combination instead and changed rebootstrap.

Another obvious candidate is cross-toolchain-base as it also produces
packages that resemble a linux-libc-dev. Looking into it, I found that
it doesn't use linux' packaging at all and just does make
headers_install, so it does not use stage1 either.

And with that I'm lost locating users of linux' stage1 profile.

Is it time to delete it?

If your answer is "no", please close this bug without further action.

Helmut

Bug#1051364: nvi uses Conflicts in violation of policy 10.1

[Helmut Grohne]

Package: nvi
Version: 1.81.6-18
Severity: serious
Justification: policy 10.1

nvi has declared Conflicts with nex due to the duplicated use of
/usr/bin/nex. Since nvi has come first, this purely is a bug in the nex
package and it is tracked as #1022957. On the nvi side, such a conflict
is harmful, because a fixed nex (one that no longer contains
/usr/bin/nex) cannot be coinstalled. The conflict is declared in direct
violation of policy section 10.1 and should therefore be removed.

Helmut

Bug#1051363: RM: g3data -- RoQA; dead upstream; orphaned; depends on gtk2

[Bastian Germann]

Package: ftp.debian.org
Severity: normal
User: ftp.debian@packages.debian.org
Usertags: remove
Control: affects -1 + src:g3data

g3data is dead upstream and orphaned. Please remove it.

Bug#1042713: wireplumber: High cpu usage

[Jonathan Kamens]

I just encountered this again, and sound (both input and output) weren't 
working while it was going on. I did `systemctl --user restart pipewire 
pipewire-pulse` and wireplumber stopped spinning and sound started 
working again. Just posting this update in case somebody else stumbles 
across this bug report and is looking for a workaround.

Bug#1051362: goldencheetah: Crashes during initial data import

[Alexey G. Petrov]

Package: goldencheetah
Version: 1:3.5-1.1
Followup-For: Bug #981223


Dear Maintainer,

I have same problem. The  Golden Cheetah crashed repeatedly at the point just 
before it would
complete the import and switch to the main window.

I think that GDB backtrace can be useful

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

Kernel: Linux 6.4.0-1-amd64 (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_UNSIGNED_MODULE
Locale: LANG=ru_RU.utf8, LC_CTYPE=ru_RU.utf8 (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 goldencheetah depends on:
ii  libc6  2.37-7
ii  libgcc-s1  13.2.0-3
ii  libical3   3.0.16-1+b1
ii  libkmlbase11.3.0-10
ii  libkmldom1 1.3.0-10
ii  libqt5bluetooth5   5.15.10-2
ii  libqt5charts5  5.15.10-2
ii  libqt5concurrent5  5.15.10+dfsg-3
ii  libqt5core5a   5.15.10+dfsg-3
ii  libqt5gui5 5.15.10+dfsg-3
ii  libqt5multimedia5  5.15.10-2
ii  libqt5network5 5.15.10+dfsg-3
ii  libqt5opengl5  5.15.10+dfsg-3
ii  libqt5serialport5  5.15.10-2
ii  libqt5sql5 5.15.10+dfsg-3
ii  libqt5sql5-sqlite  5.15.10+dfsg-3
ii  libqt5svg5 5.15.10-2
ii  libqt5webkit5  5.212.0~alpha4-33
ii  libqt5widgets5 5.15.10+dfsg-3
ii  libqt5xml5 5.15.10+dfsg-3
ii  libstdc++6 13.2.0-3
ii  libusb-0.1-4   2:0.1.12-32
ii  libvlc51:3.0.18-dmo9
ii  zlib1g 1:1.2.13.dfsg-3

goldencheetah recommends no packages.

goldencheetah suggests no packages.

-- no debconf information

GDB bt

Thread 1 "GoldenCheetah" received signal SIGSEGV, Segmentation fault.
QColor::operator= (this=this@entry=0x57545a08, color=...) at 
painting/qcolor.cpp:2932
Download failed: Недопустимый аргумент.  Continuing without source file 
./src/gui/painting/qcolor.cpp.  


   
2932painting/qcolor.cpp: Нет такого файла или каталога.
(gdb) bt
#0  QColor::operator=(QColor const&) (this=this@entry=0x57545a08, 
color=...) at painting/qcolor.cpp:2932
#1  0x557b191d in Card::setData(RideItem*) 
(this=this@entry=0x575458e0, item=0x0) at Charts/OverviewWindow.cpp:562
#2  0x557b3850 in OverviewWindow::rideSelected() (this=0x56bdaf20) 
at Charts/OverviewWindow.cpp:305
#3  0x736fb74d in doActivate(QObject*, int, void**) 
(sender=0x56bdaf20, signal_index=10, argv=0x7fffc510) at 
kernel/qobject.cpp:3937
#4  0x736f454f in QMetaObject::activate(QObject*, QMetaObject const*, 
int, void**) (sender=, m=m@entry=0x56711da0 
, local_signal_index=local_signal_index@entry=3, 
argv=argv@entry=0x7fffc510) at kernel/qobject.cpp:3985
#5  0x55d39262 in GcWindow::rideItemChanged(RideItem*) (this=, _t1=) at moc_GoldenCheetah.cpp:492
#6  0x55d3a9bb in GcWindow::qt_metacall(QMetaObject::Call, int, void**) 
(this=this@entry=0x56bdaf20, _c=_c@entry=QMetaObject::WriteProperty, _id=4, 
_a=_a@entry=0x7fffc610) at moc_GoldenCheetah.cpp:450
#7  0x55d3aa35 in GcChartWindow::qt_metacall(QMetaObject::Call, int, 
void**) (this=this@entry=0x56bdaf20, 
_c=_c@entry=QMetaObject::WriteProperty, _id=, 
_a=_a@entry=0x7fffc610) at moc_GoldenCheetah.cpp:662
#8  0x55d2e8c6 in OverviewWindow::qt_metacall(QMetaObject::Call, int, 
void**) (this=0x56bdaf20, _c=QMetaObject::WriteProperty, _id=, _a=0x7fffc610) at moc_OverviewWindow.cpp:578
#9  0x736d12ba in QMetaProperty::write(QObject*, QVariant const&) const 
(this=this@entry=0x7fffc6a0, object=object@entry=0x56bdaf20, value=...) 
at kernel/qmetaobject.cpp:3287
#10 0x736f9de8 in QObject::setProperty(char const*, QVariant const&) 
(this=this@entry=0x56bdaf20, name=name@entry=0x55e08041 "ride", 
value=...) at kernel/qobject.cpp:4109
#11 0x55867b82 in HomeWindow::tabSelected(int) 
(this=this@entry=0x56f4d2e0, index=index@entry=0) at 
Charts/HomeWindow.cpp:401
#12 0x55871422 in HomeWindow::restoreState(bool) 
(this=this@entry=0x56f4d2e0, useDefault=, 
useDefault@entry=false) at Charts/HomeWindow.cpp:1467
#13 0x55872042 in HomeWindow::selected() (this=0x56f4d2e0) at 
Charts/HomeWindow.cpp:301
#14 0x55b9833a in TabView::selectionChanged() (this=0x57635950) at 
Gui/TabView.h:57
#15 0x736fb74d in doActivate(QObject*, int, void**) 
(sender=0x577bd4b0, signal_index=20, argv=0x7fffcc40) at 
kernel/qobject.cpp:3937
#16 0x736f454f in QMetaObject::activate(QObject*, QMetaObject const*, 
int, void**) (sender=, m=m@entry=0x5671bd80 
, 

Bug#631078: docbook2x produces manpages which don't pass "hyphen-used-as-minus-sign" lintian check

[Samuel Thibault]

Hello,

Gabriele Giacone, le lun. 20 juin 2011 01:09:38 +0200, a ecrit:
> Gnash manpages are built with docbook2x (xslt -> Man-XML -> man)
> 
> e.g. Input is findmicrophones.man-xml file [1]
> 
>  $ db2x_xsltproc -s man findmicrophones.man-xml -o findmicrophones.mxml
>  $ db2x_manxml --solinks findmicrophones.mxml
> 
> Resulting findmicrophones.1 manpage has unescaped dashes which trigger
> "hyphen-used-as-minus-sign" lintian tag [2].
> 
> [1] http://deb.li/iQ6Wd
> [2] http://lintian.debian.org/tags/hyphen-used-as-minus-sign.html

This is also posing problem in e.g. git buildpackage manpages, making
copying/pasting long option names problematic:

$ man gbp-import-orig
[... copy/paste ‐‐upstream‐vcs‐tag]
$ gbp import-orig ‐‐upstream‐vcs‐tag=foo --uscan
gbp:error: you can't pass both --uscan and a filename.

The attached patch at least fixes this for the commands and options
appearing in the synopsis. I have also submitted it on
https://salsa.debian.org/xml-sgml-team/docbook2x/-/merge_requests/2

The hyphen-used-as-minus-sign lintian tag is getting resurrected, see
Bug#1051357

Samuel
diff --git a/xslt/man/synop.xsl b/xslt/man/synop.xsl
index 9713a1b..e535b75 100644
--- a/xslt/man/synop.xsl
+++ b/xslt/man/synop.xsl
@@ -107,9 +107,9 @@
 
   
 
-  
+  
 
-  
+  
 
 
 

Bug#1051285: scap-security-guide: build dependency missing in testing

[Paul Gevers]

Hi,

On 06-09-2023 19:57, Håvard F. Aasen wrote:

For how we ended up in the situation where scap-security-guide is in
testing without the necessary dependencies I cannot tell, it was
removed, then after a day, migrated back.


I think this is a glitch in the migration software. It'sn not a 
dependency (that wouldn't be allowed), but a build dependency. The 
migration software tries to prevent migration without build 
dependencies, but it's doesn't enforce that (yet).


Paul


OpenPGP_signature.asc
Description: OpenPGP digital signature

Bug#1051361: ITP: golang-github-fsmiamoto-git-todo-parser -- Small parser for git todo files

[Jongmin Kim]

Package: wnpp
Severity: wishlist
Owner: Jongmin Kim 
X-Debbugs-Cc: debian-de...@lists.debian.org, debian...@lists.debian.org

* Package name: golang-github-fsmiamoto-git-todo-parser
  Version : 0.0.5
  Upstream Contact: Flavio Miamoto 
* URL : https://github.com/fsmiamoto/git-todo-parser
* License : Expat
  Programming Lang: Go
  Description : Small parser for git todo files

 A small parser for git todo files.
 .
 This package provides the library for parsing the git todo files.

This package is in the dependency tree of lazygit (#908894)[1].

[1] https://github.com/jesseduffield/lazygit-debian/wiki/Dependency-graph

Bug#1044070: python-pauvre: FTBFS with pandas 2.0

[Étienne Mollier]

Control: tags -1 confirmed

There is a build failure reproducible by pulling python3-pandas
and python3-pandas-lib from experimental specifically.  Relevant
log that went missing from Launchpad would probably have looked
like:

   debian/rules override_dh_auto_test
make[1]: Entering directory '/<>'
PYBUILDDIR="$(echo "/<>"/.pybuild/cpython3_3.*/build)" \
&& mkdir -p "${PYBUILDDIR}/pauvre/tests/testdata/alignments" \
"${PYBUILDDIR}/pauvre/tests/testresults" \
&& cp -r "/<>/debian/tests/gff_files" \
"${PYBUILDDIR}/pauvre/tests/testdata" \
&& BUILDDIR="${PYBUILDDIR}" PATH="/<>/debian/bin:$PATH" \
dh_auto_test \
&& rm "${PYBUILDDIR}/input" \
&& rm -r "${PYBUILDDIR}/pauvre/tests/testdata" \
"${PYBUILDDIR}/pauvre/tests/testresults"
I: pybuild base:291: cd 
/<>/.pybuild/cpython3_3.11_pauvre/build; python3.11 -m unittest 
discover -v 
test_normal_plotting_scenario 
(pauvre.tests.test_synplot.libSeq_test_case.test_normal_plotting_scenario)
This verifies that the LibSeq class is constructed with all of the ... 
+ export PYTHONPATH=/<>/.pybuild/cpython3_3.11_pauvre/build
+ PYTHONPATH=/<>/.pybuild/cpython3_3.11_pauvre/build
+ exec python3 
/<>/.pybuild/cpython3_3.11_pauvre/build/pauvre/pauvre_main.py 
synplot --aln_dir 
/<>/.pybuild/cpython3_3.11_pauvre/build/pauvre/tests/testdata/alignments/
 --fileform pdf --gff_paths 
/<>/.pybuild/cpython3_3.11_pauvre/build/pauvre/tests/testdata/gff_files/Bf201706.gff
 
/<>/.pybuild/cpython3_3.11_pauvre/build/pauvre/tests/testdata/gff_files/JN392469.gff
 
/<>/.pybuild/cpython3_3.11_pauvre/build/pauvre/tests/testdata/gff_files/NC016117.gff
 --center_on COX1 --gff_labels 'B. forskalii' 'P. bachei' 'M. leidyi'
Traceback (most recent call last):
  File 
"/<>/.pybuild/cpython3_3.11_pauvre/build/pauvre/pauvre_main.py", 
line 636, in 
main()
  File 
"/<>/.pybuild/cpython3_3.11_pauvre/build/pauvre/pauvre_main.py", 
line 630, in main
args.func(parser, args)
  File 
"/<>/.pybuild/cpython3_3.11_pauvre/build/pauvre/pauvre_main.py", 
line 64, in run_subtool
submodule.run(args)
  File 
"/<>/.pybuild/cpython3_3.11_pauvre/build/pauvre/synplot.py", line 
581, in run
synplot(args)
  File 
"/<>/.pybuild/cpython3_3.11_pauvre/build/pauvre/synplot.py", line 
402, in synplot
GFFs.append(GFFParse(gffpath, args.stop_codons, species))

  File 
"/<>/.pybuild/cpython3_3.11_pauvre/build/pauvre/functions.py", 
line 75, in __init__
self.features.drop('dunno1', 1, inplace=True)
TypeError: DataFrame.drop() takes from 1 to 2 positional arguments but 
3 positional arguments (and 1 keyword-only argument) were given
FAIL

==
FAIL: test_normal_plotting_scenario 
(pauvre.tests.test_synplot.libSeq_test_case.test_normal_plotting_scenario)
This verifies that the LibSeq class is constructed with all of the
--
Traceback (most recent call last):
  File 
"/<>/.pybuild/cpython3_3.11_pauvre/build/pauvre/tests/test_synplot.py",
 line 66, in test_normal_plotting_scenario
self.assertEqual(0, int(data.returncode))
AssertionError: 0 != 1

In hope this helps (including future self),
-- 
  .''`.  Étienne Mollier 
 : :' :  gpg: 8f91 b227 c7d6 f2b1 948c  8236 793c f67e 8f0d 11da
 `. `'   sent from /dev/pts/0, please excuse my verbosity
   `-on air: Pink Floyd - One Of These Days


signature.asc
Description: PGP signature

Bug#1051360: coreutils: Mention the Users and Groups Debian document in SEE ALSO of the groups(1) man page

[Karl O. Pinc]

Package: coreutils
Version: 8.32-4+b1
Severity: wishlist

Hi,

It'd be nice if the groups(1) man page mentioned the "Users and Groups
in the Debian System" document in the SEE ALSO section.  The document
describes the users and groups which come with the system.

Perhaps a file URL would be best:

file:///usr/share/doc/base-passwd/users-and-groups.html

(The file is in base-passwd, which is Priority:required so always
present.)


-- System Information:
Debian Release: 11.7
  APT prefers oldstable-security
  APT policy: (500, 'oldstable-security'), (500, 'oldstable')
Architecture: amd64 (x86_64)

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

Versions of packages coreutils depends on:
ii  libacl1  2.2.53-10
ii  libattr1 1:2.4.48-6
ii  libc62.31-13+deb11u6
ii  libgmp10 2:6.2.1+dfsg-1+deb11u1
ii  libselinux1  3.1-3

coreutils recommends no packages.

coreutils suggests no packages.

-- no debconf information

Bug#1051359: passwd: Mention the Users and Groups Debian document in SEE ALSO for passwd man pages

[Karl O. Pinc]

Package: passwd
Version: 1:4.8.1-1
Severity: wishlist

Hi,

It'd be nice if the passwd(1) and passwd(5) man pages mentioned the
"Users and Groups in the Debian System" document in the SEE ALSO
section of their man pages.  The document describes the users and
groups which come with the system.

Perhaps a file URL would be best:

file:///usr/share/doc/base-passwd/users-and-groups.html

(The file is in base-passwd, which is Priority:required so always
present.)

-- System Information:
Debian Release: 11.7
  APT prefers oldstable-security
  APT policy: (500, 'oldstable-security'), (500, 'oldstable')
Architecture: amd64 (x86_64)

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

Versions of packages passwd depends on:
ii  libaudit1   1:3.0-2
ii  libc6   2.31-13+deb11u6
ii  libcrypt1   1:4.4.18-4
ii  libpam-modules  1.4.0-9+deb11u1
ii  libpam0g1.4.0-9+deb11u1
ii  libselinux1 3.1-3
ii  libsemanage13.1-1+b2

passwd recommends no packages.

passwd suggests no packages.

-- no debconf information

Bug#1051358: manpages: Mention the Users and Groups Debian document in SEE ALSO for the group(5) man page

[Karl O. Pinc]

Package: manpages
Version: 5.10-1
Severity: wishlist

Hi,

It'd be nice if the groups(5) man page mentioned the "Users and Groups
in the Debian System" document in the SEE ALSO section.  The document
describes the users and groups which come with the system.

Perhaps a file URL would be best:

file:///usr/share/doc/base-passwd/users-and-groups.html

(The file is in base-passwd, which is Priority:required so always
present.)


-- System Information:
Debian Release: 11.7
  APT prefers oldstable-security
  APT policy: (500, 'oldstable-security'), (500, 'oldstable')
Architecture: amd64 (x86_64)

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

manpages depends on no packages.

manpages recommends no packages.

Versions of packages manpages suggests:
ii  man-db [man-browser]  2.9.4-2

-- no debconf information

Bug#1051357: lintian: RfC: resurrect hyphen-used-as-minus-sign

[G. Branden Robinson]

Package: lintian
Version: 2.116.3
Severity: wishlist
X-Debbugs-Cc: cjwat...@debian.org, sthiba...@debian.org

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

Samuel Thibault and Colin Watson have suggested resurrecting this
lintian tag now that groff 1.23.0 handles the underlying issue a bit
differently.  (Mainly, the new groff makes it easier for sites to opt-in
and -out of this behavior by putting things in man.local and mdoc.local
instead of in the macro packages themselves, which are not conffiles.)

Debian's groff package is presently _not_ remapping input hyphens to
U+002D, to try and attract package maintainer attention and shake these
issues out, but it is also carrying a serious-severity ticket to prevent
itself from shipping that way in the next stable release.

See https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1041731#57 .

Regards,
Branden


signature.asc
Description: PGP signature

Bug#1051356: adduser: Mention the Users and Groups Debian document in SEE ALSO for the adduser(8) man page

[Karl O. Pinc]

Package: adduser
Version: 3.118
Severity: wishlist

Hi,

It'd be nice if the adduser(8) man page mentioned the "Users and
Groups in the Debian System" document in the SEE ALSO section.  The
document describes the users and groups which come with the system.

Perhaps a file URL would be best:

file:///usr/share/doc/base-passwd/users-and-groups.html

(The file is in base-passwd, which is Priority:required so always
present.)


-- System Information:
Debian Release: 11.7
  APT prefers oldstable-security
  APT policy: (500, 'oldstable-security'), (500, 'oldstable')
Architecture: amd64 (x86_64)

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

Versions of packages adduser depends on:
ii  debconf [debconf-2.0]  1.5.77
ii  passwd 1:4.8.1-1

adduser recommends no packages.

Versions of packages adduser suggests:
ii  liblocale-gettext-perl  1.07-4+b1
ii  perl5.32.1-4+deb11u2

-- debconf information excluded

Bug#1051355: chromium: Segmentation fault

[Leandro Cunha]

Package: chromium
Version: 116.0.5845.180-1
Severity: grave
Justification: Renders package unusable

Dear Maintainer,

Your package is currently unusable, making it impossible to use it.
Please consider fixing this so other users can use it normally.
Thanks.
Just reiterating that the browser doesn't even open in Gnome 44 with Wayland.
The output in the terminal is as follows:
[4562:4562:0906/161027.517475:ERROR:chrome_browser_cloud_management_controller.cc(163)]
Cloud management controller initialization aborted as CBCM is not
enabled.
[4562:4590:0906/161028.019651:ERROR:nss_util.cc(357)] After loading
Root Certs, loaded==false: NSS error code: -8018
[0906/161028.521029:ERROR:elf_dynamic_array_reader.h(64)] tag not found
Falha de segmentação

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

Kernel: Linux 6.4.0-3-amd64 (SMP w/4 CPU threads; PREEMPT)
Kernel taint flags: TAINT_WARN, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=pt_BR.UTF-8, LC_CTYPE=pt_BR.UTF-8 (charmap=UTF-8),
LANGUAGE=pt_BR:pt:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages chromium depends on:
ii  chromium-common116.0.5845.180-1
ii  libasound2 1.2.9-2
ii  libatk-bridge2.0-0 2.49.91-2
ii  libatk1.0-02.49.91-2
ii  libatomic1 13.2.0-2
ii  libatspi2.0-0  2.49.91-2
ii  libbrotli1 1.0.9-2+b6
ii  libc6  2.37-7
ii  libcairo2  1.16.0-7
ii  libcups2   2.4.2-5
ii  libdbus-1-31.14.10-1
ii  libdouble-conversion3  3.3.0-1
ii  libdrm22.4.115-1
ii  libevent-2.1-7 2.1.12-stable-8
ii  libexpat1  2.5.0-2
ii  libflac12  1.4.3+ds-2
ii  libfontconfig1 2.14.2-4
ii  libfreetype6   2.13.2+dfsg-1
ii  libgbm123.1.6-1
ii  libgcc-s1  13.2.0-2
ii  libglib2.0-0   2.77.2-1
ii  libgtk-3-0 3.24.38-4
ii  libjpeg62-turbo1:2.1.5-2
ii  libjsoncpp25   1.9.5-6
ii  liblcms2-2 2.14-2
ii  libminizip11:1.2.13.dfsg-3
ii  libnspr4   2:4.35-1.1
ii  libnss32:3.92-1
ii  libopenh264-7  2.3.1+dfsg-3
ii  libopenjp2-7   2.5.0-2
ii  libopus0   1.4-1
ii  libpango-1.0-0 1.51.0+ds-2
ii  libpng16-161.6.40-1
ii  libpulse0  16.1+dfsg1-2+b1
ii  libsnappy1v5   1.1.10-1
ii  libstdc++6 13.2.0-2
ii  libwebp7   1.2.4-0.2
ii  libwebpdemux2  1.2.4-0.2
ii  libwebpmux31.2.4-0.2
ii  libwoff1   1.0.2-2
ii  libx11-6   2:1.8.6-1
ii  libxcb11.15-1
ii  libxcomposite1 1:0.4.5-1
ii  libxdamage11:1.1.6-1
ii  libxext6   2:1.3.4-1+b1
ii  libxfixes3 1:6.0.0-2
ii  libxkbcommon0  1.5.0-1
ii  libxml22.9.14+dfsg-1.3
ii  libxnvctrl0525.125.06-1
ii  libxrandr2 2:1.5.2-2+b1
ii  libxslt1.1 1.1.35-1
ii  xdg-desktop-portal-gnome [xdg-desktop-portal-backend]  43.1-2
ii  xdg-desktop-portal-gtk [xdg-desktop-portal-backend]1.14.1-1
ii  zlib1g 

Bug#1051354: squashfs-tools: man page claims mksquashfs DIRECTORY IMAGE.SQFS creates IMAGE.SQSH

[David Starner]

Package: squashfs-tools
Version: 1:4.6.1-1
Severity: minor
X-Debbugs-Cc: prosfil...@gmail.com

mksquashfs.1 says

   mksquashfs DIRECTORY IMAGE.SQFS
  Create a Squashfs filesystem from the contents of DIRECTORY, 
writing the output to IMAGE.SQSH.  Mksquashfs will use the default compressor 
(normally gzip), and block size of 128 Kbytes.

But it doesn't; instead of writing the output to IMAGE.SQSH, it writes it to 
IMAGE.SQFS, the filename given on the command line. It seems that the manpage 
changed the normal extension from SQFS to SQSH, and the mangpage uses the two 
extensions inconsistently, but this is the only case that's actually erroneous, 
as far as I can see.


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

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

Versions of packages squashfs-tools depends on:
ii  libc6  2.37-7
ii  liblz4-1   1.9.4-1
ii  liblzma5   5.4.4-0.1
ii  liblzo2-2  2.10-2
ii  libzstd1   1.5.5+dfsg2-1
ii  zlib1g 1:1.2.13.dfsg-3

squashfs-tools recommends no packages.

squashfs-tools suggests no packages.

-- no debconf information

Bug#1044079: augur: FTBFS with pandas 2.0

[Étienne Mollier]

Control: tags -1 + help

It looks like there are no plans upstream to fix the issue for
now, and the item was closed on that ground.  I would welcome
help, as the code makes use of a pandas' internal to make
something smart with dates, and I didn't make sense of what
happens despite some digging before filing the issue upstream.

Thanks,
-- 
  .''`.  Étienne Mollier 
 : :' :  gpg: 8f91 b227 c7d6 f2b1 948c  8236 793c f67e 8f0d 11da
 `. `'   sent from /dev/pts/2, please excuse my verbosity
   `-on air: Cirrus Bay - Song Of The Wind


signature.asc
Description: PGP signature

Bug#1050970: open-vm-tools: CVE-2023-20900

[Moritz Muehlenhoff]

On Wed, Sep 06, 2023 at 08:11:17PM +0200, Bernd Zeimetz wrote:
> Hi security team,
> 
> I'm preparing security uploads for bookworm-security and buster-security
> for
> 
> > CVE-2023-20900[0]:
> > | VMware Tools contains a SAML token signature bypass vulnerability. A
> > | malicious actor with man-in-the-middle (MITM) network positioning
> > | between vCenter server and the virtual machine may be able to bypass
> > | SAML token signature verification, to perform VMware Tools Guest
> > | Operations.
> > 
> 
> any objections against fixing CVE-2023-20867 at the same time?
> Its a minor issue so we did not fix it, but I think it doesn't hurt
> to include it in stable/oldstable uploads while we are at it.

Ack, that's perfectly fine!

> Current (untested) diff would be:
> 
> https://salsa.debian.org/vmware-packaging-team/pkg-open-vm-tools/-/commit/3812674370c07c708744c0d1d497583dffa3d665

I'll have a look tomorrow.

Cheers,
Moritz

Bug#1051353: freecad: Can't create window in arch workbench

[philippe]

Package: freecad
Version: 0.20.2+dfsg1-4
Severity: grave
Justification: renders package unusable

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?

   * What exactly did you do (or not do) that was effective (or
 ineffective)?
I try to create an house with the arch workbench.
When I want to add a window, this is not created

   * What was the outcome of this action?
I get this error :
20:54:51  
20:54:51  Traceback (most recent call last):
20:54:51File "/usr/share/freecad/Mod/Draft/draftguitools/gui_snapper.py",
line 1417, in click
20:54:51  accept()
20:54:51File "/usr/share/freecad/Mod/Draft/draftguitools/gui_snapper.py",
line 1429, in accept
20:54:51  if len(inspect.getargspec(callback).args) > 1:
20:54:51 ^^
20:54:51  AttributeError: module 'inspect' has no attribute 'getargspec'. Did
you mean: 'getargs'?

It seems to be a conflict with phyton version (getargspec seems to be
depracted)

   * What outcome did you expect instead?

*** End of the template - remove these template lines ***


-- System Information:
Debian Release: 12.1
  APT prefers stable-security
  APT policy: (960, 'stable-security'), (950, 'stable-updates'), (910, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

Versions of packages freecad depends on:
ii  freecad-python3  0.20.2+dfsg1-4

Versions of packages freecad recommends:
ii  calculix-ccx  2.20-1
ii  graphviz  2.42.2-7+b3

Versions of packages freecad suggests:
ii  povray  1:3.7.0.10-2+b2

-- no debconf information

Bug#1000008: openscap: depends on obsolete pcre3 library

[Håvard F . Aasen]

On 06.09.2023 20:09, Bastian Germann wrote:
> Control: tags -1 fixed-upstream
> 
> The new openscap release builds with pcre2.


Thanks for the heads-up, I'll see if I can have it uploaded by tonight or
tomorrow.

Håvard

Bug#1037901: xir: ftbfs with GCC-13

[Jonathan Bergh]

Control: tags 1037901 + patch

Patch for the above bug attached.
Regards
Jonathan


patch.debdiff
Description: Binary data

Bug#1051326: systemsettings: A lot of icons are just black squares

[Lisandro Damián Nicanor Pérez Meyer]

Hi!

El miércoles, 6 de septiembre de 2023 07:15:26 -03 j...@mailb.org escribió:
> Tags: fixed
> 
> turns out the issue was libqt5quick5-gles everything looks correct after 
> installing libqt5quick5
> is there any way to avoid libqt5quick5-gles getting installed on desktops?


The question is: did you manually install any *-gles package yourself? They 
shouldn't be automatically installed, but we had issues like that before. If 
you have any dpkg/apt logs, the better.

Thanks

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

Bug#1050970: open-vm-tools: CVE-2023-20900

[Bernd Zeimetz]

On 2023-09-06 20:11, Bernd Zeimetz wrote:

Hi security team,

I'm preparing security uploads for bookworm-security and 
buster-security


(bullseye-security of course... - we clearly have too many relases with 
bu)


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

Bug#1050970: open-vm-tools: CVE-2023-20900

[Bernd Zeimetz]

Hi security team,

I'm preparing security uploads for bookworm-security and buster-security
for


CVE-2023-20900[0]:
| VMware Tools contains a SAML token signature bypass vulnerability. A
| malicious actor with man-in-the-middle (MITM) network positioning
| between vCenter server and the virtual machine may be able to bypass
| SAML token signature verification, to perform VMware Tools Guest
| Operations.



any objections against fixing CVE-2023-20867 at the same time?
Its a minor issue so we did not fix it, but I think it doesn't hurt
to include it in stable/oldstable uploads while we are at it.

Current (untested) diff would be:

https://salsa.debian.org/vmware-packaging-team/pkg-open-vm-tools/-/commit/3812674370c07c708744c0d1d497583dffa3d665


Thanks,

Bernd

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

Bug#1039958: autopkgtest-build-podman: Image creation fails with "sd-bus call: Permission denied"

[Simon McVittie]

On Wed, 06 Sep 2023 at 19:35:46 +0200, Gioele Barabucci wrote:
> If there is consensus, I volunteer to create a MR to move
> autopkgtest-build-podman and related files to a separate package that can
> then Depends: on podman, dbus-user-session and all other packages required
> to make it work out of the box.

I don't think this is a good idea: this design would mean autopkgtest
needing to go through the NEW queue and be arbitrarily delayed by ftp
team review every time it gains a new optional backend with non-trivial
dependencies. (Currently that's: docker/podman, lxc, lxd, qemu, schroot,
plus perhaps some of the autopkgtest-build* tools have requirements that
are not the same as their corresponding autopkgtest-virt- backends.)

Also, autopkgtest-virt-docker and -virt-podman are the same script,
running in a different mode, with different dependencies, and the same
is true for their autopkgtest-build-* equivalents. Should the package
containing them depend on Docker, or Podman, or both, or use an "|"-group?
None of those possible answers really seems right to me.

The ftp team also seems unlikely to be impressed by a new binary
package for around 20K of scripts (plus man pages).

If you want to help with this, I think a better MR would be one to make
a-b-podman and a-v-podman log a user-comprehensible warning mentioning
dbus-user-session, if they are started in podman mode while the socket
$XDG_RUNTIME_DIR/bus doesn't exist.

(Or if you can figure out exactly what circumstances require
dbus-user-session, maybe even exit early with an error under those
circumstances - but I wouldn't want to get that wrong and prevent people
from using podman in a situation where actually it would have worked fine,
so please be conservative, or at least have some sort of --force option.)

smcv

Bug#1000008: openscap: depends on obsolete pcre3 library

[Bastian Germann]

Control: tags -1 fixed-upstream

The new openscap release builds with pcre2.

Bug#1049456: update

[Terrance Hendrik]

after upgrading bluez bundle to
```
Package: bluez

Version: 5.69-1
...
```

now **MX Anywhere 3** disconnect immediately then reconnected for dozens of
times every several seconds.

While other mice (e.g.UGreen MU002 ) working fine.

Bug#1037840: regina-normal: ftbfs with GCC-13

[Jonathan Bergh]

tags: control -1 + patch

Hi, please find a patch intended to resolve the above FTBFS.


patch.debdiff
Description: Binary data

Bug#1002996: maturin

[Jeffrey Cliff]

maturin ITP is finished fyi


Jeff Cliff
-- 

End the campaign to Cancel Richard Stallman - go to stallmansupport.org !

Bug#1051325: [Debian-med-packaging] Bug#1051325: sortmerna: FTBFS: concurrentqueue.h: No such file or directory

[Étienne Mollier]

Control: tags -1 + confirmed

Hi László,

László Böszörményi, on 2023-09-06:
> /build/sortmerna-4.3.6/include/readsqueue.hpp:49:12: fatal error:
> concurrentqueue/concurrentqueue.h: No such file or directory
>49 | #  include 
>   |^~~
[…]
> It seems the mentioned header moved to
> /usr/include/concurrentqueue/moodycamel/concurrentqueue.h ; please
> update your package.

Thanks for the report and the hint, I'm looking at this.

Have a nice day,  :)
-- 
  .''`.  Étienne Mollier 
 : :' :  gpg: 8f91 b227 c7d6 f2b1 948c  8236 793c f67e 8f0d 11da
 `. `'   sent from /dev/pts/2, please excuse my verbosity
   `-on air: Marillion - Angelina


signature.asc
Description: PGP signature

Bug#1051305: Request to Add 'loong64' to java-common's debian/java_defaults.mk

[tony mancill]

Hi Meng Sang,

On Wed, Sep 06, 2023 at 09:19:49AM +0800, 桑猛 wrote:
> Source: java-common
> X-Debbugs-Cc: sangm...@loongson.cn
> Version: 0.74
> Tags: patch
> Severity: wishlist
> Usertags: loongarch64
> User: debian-de...@lists.debian.org
> 
> I am writing to request a modification to the `java17_architectures` variable 
> in the `debian/java_defaults.mk` file of the `java-common` package.
> 
> Specifically, I would like to request the addition of the 'loong64' 
> architecture to the `java17_architectures` variable.

Since this impacts the openjdk packages, which are maintained by the
OpenJDK Team (distinct from the Debian Java Team), I'll wait to hear
from that team before uploading.

However, I believe your patch may also need to add an entry to the
jvm_archdir_map. [0]  Is the mapping loong64=loong64?

Cheers,
tony

[0] 
https://salsa.debian.org/java-team/java-common/-/blob/master/debian/java_defaults.mk#L35-39


signature.asc
Description: PGP signature

Bug#1039958: autopkgtest-build-podman: Image creation fails with "sd-bus call: Permission denied"

[Gioele Barabucci]

On 06/09/23 15:27, Faidon Liambotis wrote:

On Fri, Jun 30, 2023 at 12:52:31PM +0200, Gioele Barabucci wrote:

autopkgtest-build-podman's failure is due to the issue reported in [1], i.e.
the Debian setup of podman requires `dbus-user-session`, but none of the
podman-related packages Depends on it.


podman may not Depend on dbus-user-session, but it Recommends it.


Indeed this is not a `podman` issue, but a `autopkgtest-build-podman` one.

To rephrase it: autopkgtest-build-podman does not work without 
dbus-user-session. Why doesn't the package that contains 
autopkgtest-build-podman Depends: on dbus-user-session?


The answer is (I presume) that the package containing 
autopkgtest-build-podman (autopkgtest) is a bit too generic to have an 
hard Depend on dbus-user-session. This is why I was suggesting splitting 
it into a separate package.


If there is consensus, I volunteer to create a MR to move 
autopkgtest-build-podman and related files to a separate package that 
can then Depends: on podman, dbus-user-session and all other packages 
required to make it work out of the box.


Regards,

--
Gioele Barabucci

Bug#1009259: nvidia-legacy-340xx-driver: Crash at start with linux 5.10

[Mike Mironov]

Hello!

I confirm this bug. Try to start module from package 340.108-19 get 
kernel panic.


Module from 340.108-10~bpo10+1 start without problem

Bug#885426: typo?

[Jeffrey Cliff]

is this a typo?  Shouldn't this be electrum-cash ?

Jeff Cliff
-- 

End the campaign to Cancel Richard Stallman - go to stallmansupport.org !

Bug#1051292: grub-efi-amd64 post install script 10_linux.orig fails with locally compiled kernel

[tv.debian]

Le 06/09/2023 à 16:01, Marc Haber a écrit :

On Wed, Sep 06, 2023 at 10:23:31AM +0200, tv.debian wrote:

You can close this bug, I'll deal with it locally since it only affects
systems with out of repository kernels. It is not worse your time.
Sorry for the noise.


It is an incompatible change in the script and function files and you
tricked dpkg into not updating the 10_linux file.

I left my 10_linux unchanged and put a patched 08_linux in front of it,
of course my 08_linux failed as well since the sorting function was
removed in grub. But that was easy to fix.

It does not have to do with out-of-repository kernels.

Greetings
Marc

P.S.: Yes, my method doubles all kernel entries, but the ones created by
the local scripts are first.



Hello, thank you for the diagnosis, the system is a test bed for new 
features upgraded in place since Etch, and always running some kind of 
unstable, so occasional weirdness and cruft are expected.
I am only sorry I wasted time for everyone involved before digging 
deeper and fixing it myself :-( .


Once the old stuff pruned and reverted to clean grub-* packages with an 
"install --reinstall" incantation it is all up and working.


Again sorry for the noise.

Thanks to all.

Bug#1050730: cyrus-imapd 3.6.1-4+deb12u1 flagged for acceptance

[Jonathan Wiltshire]

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

Hi,

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

Thanks for your contribution!

Upload details
==

Package: cyrus-imapd
Version: 3.6.1-4+deb12u1

Explanation: ensure mailboxes are not lost on upgrades from bullseye

Bug#1051084: kernelshark 2.2.1-1~deb12u1 flagged for acceptance

[Jonathan Wiltshire]

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

Hi,

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

Thanks for your contribution!

Upload details
==

Package: kernelshark
Version: 2.2.1-1~deb12u1

Explanation: fix segfault in libshark-tepdata; fix capturing when target 
directory contains a space

Bug#1051338: lintian: Downgrade wrong-path-for-interpreter from error to pedantic, merged-usr is mandatory now

[Luca Boccassi]

Control: tags -1 patch
Control: severity -1 important
Control: retitle -1 Lintian raises wrong-path-for-interpreter for valid aliased 
paths

On Wed, 6 Sep 2023 12:36:50 +0200 Julian Andres Klode 
wrote:
> Package: lintian
> Severity: normal
> 
> Merged-usr has been mandatory since bookworm, so use of /usr/bin/sh
> and such can no longer constitute an error, it's just for pedantic
> people who want to stay behind the times and annoy everyone.

These tags flag more things than just /bin vs /usr/bin, so rather than
downgrading I think it's better to adjust the check to accept both /usr
and legacy paths.

I have opened a MR on Salsa to do just that:

https://salsa.debian.org/lintian/lintian/-/merge_requests/478

-- 
Kind regards,
Luca Boccassi


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

Bug#1051352: ITP: shedskin -- Python-to-C++ compiler designed to speed up Python programs

[Paul Boddie]

Package: wnpp
Severity: wishlist
Owner: Paul Boddie 

* Package name: shedskin
  Version : 0.9.7
  Upstream Author : Mark Dufour 
* URL : https://shedskin.github.io/
* License : GPL-3+
  Programming Lang: Python
  Description : Python-to-C++ compiler designed to speed up Python programs

Shed Skin converts programs written in a static subset of Python to C++.
The C++ code can be compiled to executable code, which can be run either
as a standalone program or as a module imported from Python.

This package was previously included in Debian but was discarded when Python
2 ceased to be supported for most areas of distribution functionality. This
software has since been updated to run using Python 3.

Previously, I found a sponsor for the package via the Debian Mentors
service. It might make sense to maintain this new package within the Debian
Python team, and much of the packaging has been done according to their
packaging standards.

Bug#1050777: The surf autopkgtests are failing with webkitgtk 2.41

[Sebastien Bacher]

Checking a strace output it's loading libEGL.so.1 on my machine and not 
libGLES.so.2


Le 06/09/2023 à 17:46, Sebastien Bacher a écrit :

Yes

ii  libgles2:amd64 1.6.0-1 amd64    Vendor neutral GL dispatch 
library -- GLESv2 support


Le 06/09/2023 à 13:43, Alberto Garcia a écrit :

On Tue, Aug 29, 2023 at 09:47:01AM +0200, Sebastien Bacher wrote:

The issue seems to be there in Debian as well
https://ci.debian.net/packages/s/surf/unstable/amd64/

This is due to a missing dependency on libgles2 (which is loaded at
runtime via libepoxy), so I will add that to the package.

Do you have that package installed?

Berto

Bug#1050777: The surf autopkgtests are failing with webkitgtk 2.41

[Sebastien Bacher]

Yes

ii  libgles2:amd64 1.6.0-1 amd64    Vendor neutral GL dispatch 
library -- GLESv2 support


Le 06/09/2023 à 13:43, Alberto Garcia a écrit :

On Tue, Aug 29, 2023 at 09:47:01AM +0200, Sebastien Bacher wrote:

The issue seems to be there in Debian as well
https://ci.debian.net/packages/s/surf/unstable/amd64/

This is due to a missing dependency on libgles2 (which is loaded at
runtime via libepoxy), so I will add that to the package.

Do you have that package installed?

Berto

Bug#921526: geany crashes when deleting files in Tree Browser

[Lee Garrett]

This seems to be fixed in the bookworm release.

On Wed, 06 Feb 2019 15:19:24 +0100 Lee Garrett  wrote:

Package: geany
Version: 1.33-1
Severity: important

Hi,

geany crashes when deleting files in Tree Browser. Steps to reproduce:

1) Open a geany project
2) Enable the side bar with View -> Show Sidebar
3) Switch to the "Tree Browser" tab
4) Double-click on a file to open it
5) Right-click on the file in the Tree Browser
6) Select "delete"

At this point geany with crash with following shell output:

--->8-->8-->8-->8-->8-->8-->8-->8-->8-->8---

(geany:7652): Gtk-WARNING **: 15:16:21.819: Theme parsing error: 
gtk-widgets.css:186:14: not a number

(geany:7652): Gtk-WARNING **: 15:16:21.819: Theme parsing error: 
gtk-widgets.css:186:14: Expected a string.

(geany:7652): Gtk-WARNING **: 15:16:21.824: Theme parsing error: 
gtk-widgets.css:2749:24: not a number

(geany:7652): Gtk-WARNING **: 15:16:21.824: Theme parsing error: 
gtk-widgets.css:2749:24: Expected a string.

(geany:7652): Gtk-WARNING **: 15:16:21.824: Theme parsing error: 
gtk-widgets.css:2940:14: not a number

(geany:7652): Gtk-WARNING **: 15:16:21.824: Theme parsing error: 
gtk-widgets.css:2940:14: Expected a string.

(geany:7652): Gtk-WARNING **: 15:16:21.824: Theme parsing error: 
gtk-widgets.css:2946:17: Expected a string.

(geany:7652): Gtk-WARNING **: 15:16:21.827: Theme parsing error: 
gtk-widgets.css:4083:14: not a number

(geany:7652): Gtk-WARNING **: 15:16:21.827: Theme parsing error: 
gtk-widgets.css:4083:14: Expected a string.

(geany:7652): Gtk-WARNING **: 15:16:21.827: Theme parsing error: 
gtk-widgets.css:4088:17: Expected a string.

(geany:7652): Gtk-WARNING **: 15:16:21.828: Theme parsing error: 
gtk-widgets.css:4729:14: not a number

(geany:7652): Gtk-WARNING **: 15:16:21.828: Theme parsing error: 
gtk-widgets.css:4729:14: Expected a string.

(geany:7652): Gtk-WARNING **: 15:16:21.829: Theme parsing error: 
xfce.css:47:16: not a number

(geany:7652): Gtk-WARNING **: 15:16:21.829: Theme parsing error: 
xfce.css:47:16: Expected a string.

(geany:7652): Gtk-WARNING **: 15:16:21.829: Theme parsing error: 
lightdm-gtk-greeter.css:16:14: not a number

(geany:7652): Gtk-WARNING **: 15:16:21.829: Theme parsing error: 
lightdm-gtk-greeter.css:16:14: Expected a string.

(geany:7652): Gtk-WARNING **: 15:16:21.829: Theme parsing error: 
lightdm-gtk-greeter.css:26:14: not a number

(geany:7652): Gtk-WARNING **: 15:16:21.829: Theme parsing error: 
lightdm-gtk-greeter.css:26:14: Expected a string.

(geany:7652): Gtk-WARNING **: 15:16:21.830: Theme parsing error: 
lightdm-gtk-greeter.css:40:16: not a number

(geany:7652): Gtk-WARNING **: 15:16:21.830: Theme parsing error: 
lightdm-gtk-greeter.css:40:16: Expected a string.

(geany:7652): Gtk-WARNING **: 15:16:21.830: Theme parsing error: 
lightdm-gtk-greeter.css:96:14: Expected a string.

Bug#1051351: graphviz: Please package a new upstream version

[Eugene Toder]

Package: graphviz

Version: 2.42.2-7+b3

Severity: normal

X-Debbugs-Cc: elto...@gmail.com


Dear maintainer,

It appears that the upstream version of graphviz was last updated in

September 2019, i.e. almost 4 years ago. Several new versions were

released since then with many bug fixes. Please package a new version.

Some other distributions (Fedora, Arch, Alpine, Gentoo) have the latest

version.

Regards,

Eugene


-- System Information:

Debian Release: bookworm/sid

Architecture: amd64 (x86_64)



Kernel: Linux 5.15.112-ts1-amd64 (SMP w/6 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 graphviz depends on:

ii  libann01.1.2+doc-9+b1

ii  libc6  2.36-7

ii  libcdt52.42.2-7+b3

ii  libcgraph6 2.42.2-7+b3

ii  libexpat1  2.5.0-1

ii  libgcc-s1  12.2.0-13

ii  libgd3 2.3.3-9

ii  libglib2.0-0   2.74.6-2

ii  libgts-0.7-5   0.7.6+darcs121130-5+b1

ii  libgvc62.42.2-7+b3

ii  libgvpr2   2.42.2-7+b3

ii  liblab-gamut1  2.42.2-7+b3

ii  libstdc++6 12.2.0-13

ii  libx11-6   2:1.8.4-2+deb12u1

ii  libxaw72:1.0.14-1

ii  libxmu62:1.1.3-3

ii  libxt6 1:1.2.1-1.1



Versions of packages graphviz recommends:

ii  fonts-liberation2  2.1.5-1



Versions of packages graphviz suggests:

pn  graphviz-doc  

pn  gsfonts   



-- no debconf information

Bug#1051342: Issue with the genx software

[PICCA Frederic-Emmanuel]

Hello, here you should find the informations.

platform: Debina unstable

python: ~$ python3
Python 3.11.5 (main, Aug 29 2023, 15:31:31) [GCC 13.2.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> 

$ dpkg -l | grep wx

ii  libwxbase3.2-1:amd64   3.2.2+dfsg-4 
amd64wxBase library (runtime) - non-GUI support classes 
of wxWidgets toolkit
ii  libwxgtk-gl3.2-1:amd64 3.2.2+dfsg-4 
amd64wxWidgets Cross-platform C++ GUI toolkit (GTK 3 gl 
library runtime)
ii  libwxgtk3.2-1:amd643.2.2+dfsg-4 
amd64wxWidgets Cross-platform C++ GUI toolkit (GTK 3 
runtime)
ii  python3-wxgtk4.0   4.2.1+dfsg-1 
amd64Python 3 interface to the wxWidgets Cross-platform 
C++ GUI toolkit
ii  python3-wxutils0.3.0-1  
all  wxPython utilities and convenience functions 
(Python 3)

> I suspect that something changed in the WX API causing this issue. I don't 
> think
> this should prevent you from packaging, as this part of the code only gets
> called upon user request to exit. (There might be no request to save or 
> missing
> storage of window state, but no big impact on the functionality).

I already uploaded the version into Debian and you can see that there is issues 
with numba...

https://buildd.debian.org/status/package.php?p=genx

 one probleme at a time :))

Cheers

Bug#1051349: slapd: DoS after some 'Too many open files'?

[Quanah Gibson-Mount]

--On Wednesday, September 6, 2023 5:43 PM +0200 Patrice Duroux 
 wrote:



Package: slapd
Version: 2.5.13+dfsg-5
Severity: normal

Dear Maintainer,

This happens on one physical machine using a Debian Bookworm and only
dedicated to NFS/LDAP services.
I never faced this before for years with Bulleyes before upgrading to
Bookworm.

Looking into log files there are the following messages:


You need to increase the number of file descriptors available to slapd. 
You're hitting this issue because Debian compiles with the 
--enable-wrappers flag for tcp wrappers.


With systemd, you can change the number of file descriptors available with 
the

"LimitNOFILE" option.

For example:

[Service]
...
LimitNOFILE=8192

To increase the limit to 8,192 available file descriptors to the slapd 
process.  I don't know what defaults Debian allows in regards to file 
descriptors for slapd in their default package.


Regards,
Quanah

Bug#1042853: docknot: FTBFS with Perl 5.38: t/spin/errors.t failure

[Russ Allbery]

gregor herrmann  writes:
> On Tue, 01 Aug 2023 23:06:54 +0300, Niko Tyni wrote:

>> This package fails to build from source with Perl 5.38 (currently in
>> experimental.)
>> 
>> This looks like just a test-only diagnostics change, but
>> please file a bug against perl to add a Breaks entry if
>> there's actual runtime breakage after all.

> According to https://github.com/rra/docknot/issues/6 fixed upstream
> (in git, not released yet).

Yeah, I'm sorry about the delay here.  I'm trying to get a new release out
shortly and if I fail at that I'll patch this in the Debian package.
Please feel free to move forward with Perl and don't block on this
package; this is totally my own (known) problem.

-- 
Russ Allbery (r...@debian.org)  

Bug#1051342: Issue with the genx software

[Glavic Artur Gregor]

Hi Frédéric,

Can you send me details of your configuration?
- platform
- python version
- wxPython version

I suspect that something changed in the WX API causing this issue. I don't 
think this should prevent you from packaging, as this part of the code only 
gets called upon user request to exit. (There might be no request to save or 
missing storage of window state, but no big impact on the functionality).

Cheers,
Artur

-Original Message-
From: PICCA Frederic-Emmanuel  
Sent: Wednesday, September 6, 2023 3:25 PM
To: Glavic Artur Gregor 
Cc: debian-pan-maintainers ; 
1051...@bugs.debian.org
Subject: Issue with the genx software

Hello, I am preparing the packaging of genx 3.6.22.

When I try to quit the application I have this error message

CRITICAL: uncought python error
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/genx/gui/main_window.py", line 1418, in 
eh_mb_quit
if event.CanVeto() and not self.model_control.saved:
   ^
AttributeError: 'CommandEvent' object has no attribute 'CanVeto'
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/genx/gui/main_window.py", line 1418, in 
eh_mb_quit
if event.CanVeto() and not self.model_control.saved:
   ^

So I would like your help in order to solve this issue.

thanks for considering.

Frédéric

Bug#967790: urfkill: depends on deprecated GTK 2

[Bastian Germann]

I am uploading a NMU (DELAYED/10) with the attached debdiff.diff -Nru urfkill-0.5.0/debian/changelog urfkill-0.5.0/debian/changelog
--- urfkill-0.5.0/debian/changelog  2019-07-09 06:21:18.0 +
+++ urfkill-0.5.0/debian/changelog  2023-09-06 13:48:31.0 +
@@ -1,3 +1,10 @@
+urfkill (0.5.0-7.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Drop Build-Depends: gir1.2-gtk-2.0. (Closes: #967790)
+
+ -- Bastian Germann   Wed, 06 Sep 2023 13:48:31 +
+
 urfkill (0.5.0-7) unstable; urgency=low
 
   [Mark Hindley]
diff -Nru urfkill-0.5.0/debian/control urfkill-0.5.0/debian/control
--- urfkill-0.5.0/debian/control2019-07-09 06:21:18.0 +
+++ urfkill-0.5.0/debian/control2023-09-06 13:47:18.0 +
@@ -2,7 +2,7 @@
 Section: net
 Priority: optional
 Maintainer: Keng-Yu Lin 
-Build-Depends: debhelper (>= 9.20160709), dh-autoreconf (>=2), dh-exec 
(>=0.3), autotools-dev, libglib2.0-dev, libdbus-1-dev, libdbus-glib-1-dev, 
libudev-dev, libpolkit-gobject-1-dev, libexpat1-dev, intltool (>=0.40.0), 
gobject-introspection (>= 0.6.7), libgirepository1.0-dev (>= 0.6.7), 
gir1.2-gtk-2.0, gir1.2-gtk-3.0, autopoint, gtk-doc-tools
+Build-Depends: debhelper (>= 9.20160709), dh-autoreconf (>=2), dh-exec 
(>=0.3), autotools-dev, libglib2.0-dev, libdbus-1-dev, libdbus-glib-1-dev, 
libudev-dev, libpolkit-gobject-1-dev, libexpat1-dev, intltool (>=0.40.0), 
gobject-introspection (>= 0.6.7), libgirepository1.0-dev (>= 0.6.7), 
gir1.2-gtk-3.0, autopoint, gtk-doc-tools
 Standards-Version: 4.0.0
 Homepage: http://www.freedesktop.org/wiki/Software/urfkill