Bug#1027828: [Debichem-devel] Bug#1027828: macromoleculebuilder: FTBFS in bullseye (a2x: ERROR: "xsltproc" [...] returned non-zero exit status 5)

[Santiago Vila]

El 4/1/23 a las 8:40, Andrius Merkys escribió:


I can reproduce the issue. Should I propose a bullseye-pu upload fixing it?


Yes, please. Packages in stable must build in stable, that's the idea.

Thanks.

Bug#1027859: Uninstallable on bullseye-backports because of nodejs security upgrade

[Julian Gilbey]

Package: pkg-js-tools
Version: 0.15.9~bpo11+1
Severity: normal

On bullseye, there has been a security update of nodejs to version
12.22.12~dfsg-1~deb11u1, but the bullseye-backports version depends on
nodejs:any | nodejs (<< 12.22.5~dfsg-4~).  Aptitude complains that it
cannot install pkg-js-tools (or dh-nodejs) from bullseye-backports
together with nodejs, so I guess that this backport needs to be
updated.

Best wishes,

   Julian

Bug#1027832: debian-policy: Please clarify that priority required packages are not automatically build essential

[Santiago Vila]

El 4/1/23 a las 2:32, Sam Hartman escribió:

"Santiago" == Santiago Vila  writes:


 Santiago> As an example, packages tzdata, mount or e2fsprogs are not
 Santiago> build-essential and afaik have not been for a long time,
 Santiago> but there are still people who believe that they are
 Santiago> build-essential for the mere fact that they are
 Santiago> priority:required.

Why not just make all required packages build-essential?
I agree we should fix the class of bugs you are talking about, but it
seems like in some cases it might be easier to fix them by declaring
them not buggy.


Because required to build != required in a _running_ system

The idea of declaring something not a bug to avoid fixing it is not very 
appealing
to me. I believe we can do better than that. The proposal made in bug #837060
(namely, that debootstrap stops installing packages not build essential when
using the buildd profile) is IMO the optimal way to fix the problem at its root,
because once that packages with missing build-depends start failing in the 
buildds,
then it will be clear for everybody that there is a missing build-depends.

(The initial email in such bug by Johannes Schauer describes the problem
very well).

Thanks.

Bug#1027828: [Debichem-devel] Bug#1027828: macromoleculebuilder: FTBFS in bullseye (a2x: ERROR: "xsltproc" [...] returned non-zero exit status 5)

[Andrius Merkys]

Hi Santiago,

On 2023-01-03 22:35, Santiago Vila wrote:

Package: src:macromoleculebuilder
Version: 3.2+dfsg-2
Severity: serious
Tags: ftbfs
Control: fixed -1 4.0.0+dfsg-2

Dear maintainer:

During a rebuild of all packages in bullseye, your package failed to build


I can reproduce the issue. Should I propose a bullseye-pu upload fixing it?

Best,
Andrius

Bug#1027858: RFS: python-ebooklib/0.18-2 [QA] -- E-book library for handling EPUB2/EPUB3/Kindle formats - documentation

[Håvard F . Aasen]

Package: sponsorship-requests
Severity: normal

Dear mentors,

I am looking for a sponsor for my package "python-ebooklib":

 * Package name : python-ebooklib
   Version  : 0.18-2
   Upstream contact : Aleksandar Erkalović 
 * URL  : https://github.com/aerkalov/ebooklib
 * License  : AGPL-3
 * Vcs  :
   Section  : python

The source builds the following binary packages:

  python3-ebooklib - Python 3 E-book library for handling EPUB2/EPUB3/Kindle 
formats
  python-ebooklib-doc - E-book library for handling EPUB2/EPUB3/Kindle formats 
- documentation

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

  https://mentors.debian.net/package/python-ebooklib/

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

  dget -x 
https://mentors.debian.net/debian/pool/main/p/python-ebooklib/python-ebooklib_0.18-2.dsc

Changes since the last upload:

 python-ebooklib (0.18-2) unstable; urgency=medium
 .
   * QA upload.
   * Source-only upload.

Regards,
Håvard

Bug#1027811: libcifpp-data: uninstallable

[Nilesh Patra]

Hi Maarten/Patrice,

On Tue, 03 Jan 2023 17:23:19 +0100 Patrice DUROUX  
wrote:
> Package: libcifpp-data
> Version: 5.0.5-5
> Severity: normal
> 
> Dear Maintainer,
> 
> Here is the output:
> 
> Setting up libcifpp-data (5.0.5-5) ...
> /etc/cron.weekly/update-libcifpp-data: 9: Syntax error: "then" unexpected
> dpkg: error processing package libcifpp-data (--configure):
>  installed libcifpp-data package post-installation script subprocess returned 
> error exit status 2
> 
> 
> This script contains a duplicated 'then' directive:
> 
>  8if [ "${euid}" -ne 0 ] ; then
>  9then echo "Please run as root"
> 10exit
> 11fi

This is fixed in the latest upload right - could you check?
If so, could you close this bug report?
 

-- 
Best,
Nilesh


signature.asc
Description: PGP signature

Bug#1026513: patch seems incorrect, here's a better one

[FC Stegerman]

Hi!

The package description for python3-nose-random says:

  * uses a fixed seed so that each test run is identical
  * lets you to run the test only on a specific scenario to facilitate
debugging

I'm not very familiar with this package, but the removal of rseed in
the patch seems to me to break those properties, since it no longer
uses a fixed seed.

The real problem seems to be that config.scenario can be _missing,
which is an object() instead of a supported seed type.

I've attached a patch that fixes the original problem -- jsondiff's
tests no longer fail -- without removing the use of rseed.

- FC
--- a/nose_random/__init__.py	2023-01-04 07:38:06.340805543 +0100
+++ b/nose_random/__init__.py	2016-10-19 11:17:54.0 +0200
@@ -51,7 +51,7 @@
 def randomize(n, scenario_generator, seed=12038728732):
 def decorator(test):
 def randomized_test(self):
-if config.scenario is not None and config.scenario is not _missing:
+if config.scenario is not None:
 nseeds = 1
 seeds = [config.scenario]
 else:
@@ -70,4 +70,4 @@
 else:
 raise (type(e), type(e)('%s with scenario %s (%i of %i)' % (e.message, rseed, i+1, nseeds)), sys.exc_info()[2])
 return randomized_test
-return decorator
+return decorator
\ No newline at end of file

Bug#1027857: Debian12 Testing - SpellFix: Programming error in itcl 3.4.4-1

[abcd 567]

Package: itcl
Version: 3.4.4-1

Debian testing recently updated itcl from 3.4.3 to 3.4.4 and it appears 
SpellFix is now broken for abbreviations, eg. [info exist foo] vs [info exists 
foo].

Repro:

#!/usr/bin/env tclsh

package require Itcl

itcl::class TestClass {
method test {}
}

itcl::body TestClass::test {} {
set foo "bar"
if {[info exist foo]} {
puts "foo exists"
}
}

TestClass testClass
testClass test


$ ./test.tcl
SpellFix: programming error
[1]315606 IOT instruction  ./test.tcl

Bug#1027856: RM: wesnoth-1.14/1:1.14.17-2

[Vincent Cheng]

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

src:wesnoth-1.14 has been superseded by wesnoth-1.16; please remove the former
from the archive. Thanks!

Bug#1010244: Started packaging refresh

[William Desportes]

Hi, 

I started refreshing the packaging at 
https://salsa.debian.org/php-team/pear/phpsysinfo

You can expect this bug to get fixed some time soon

--
William Desportes

Bug#1024216: mkchromecast: please change dependency from youtube-dl to yt-dlp

[Andres Salomon]

On Wed, 16 Nov 2022 00:58:30 -0500 Andres Salomon  
wrote:

> Package: src:mkchromecast
> Version: 0.3.9~git20200902+db2964a-2
> Severity: normal
>
> We are planning to remove the youtube-dl package in the next Debian
> release, as upstream development had issues and has stagnated (see
>  ). The upstream package was forked, 
and

> active development now happens in yt-dlp (which is an almost* drop-in
> replacement for youtube-dl). Since your package depends on it, please
> test your package with yt-dlp and update the dependency to replace
> "youtube-dl" with "yt-dlp" once you've verified that it works 
correctly

> with your package.
>
> This bug is filed as normal for now, but will likely become
> release-critical once the new youtube-dl dummy package is uploaded to
> unstable.
>

The new youtube-dl dummy package has now been uploaded to unstable. 
However, I'm not raising the severity on this bug because youtube-dl is 
only used if mkchromecast is called with '-y '. So that will now 
be broken until you switch to yt-dlp, but mkchromecast appears usable 
without that functionality.


It looks like it calls "youtube-dl -o - ", which should work with 
a simple replacement to "yt-dlp -o - ".

Bug#1020391: mesa: Updates to 22.2 RCs cause blank screen on some VirtIO graphics

[Ben Westover]

Hello Fabio,

On 1/3/23 06:35, Fabio Pedretti wrote:
> You don't provide many details, but at a quick search your issue may
> be this one:
> https://gitlab.freedesktop.org/virgl/virglrenderer/-/issues/291
> https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/19655
I don't see how that issue is related to mine. It supposedly only occurs
when XWayland is being used, while mine is happening on pure X11.

Thanks,
--
Ben Westover


OpenPGP_signature
Description: PGP signature

Bug#1024752: (no subject)

[Patrick Franz]

Control: tag -1 pending

Fixed with
https://salsa.debian.org/qt-kde-team/qt6/qt6-websockets/-/commit/d2942bad0311f86137cbe284a3280ea5f785ee35
and will be part of the next upload once the transition is completed
and 6.4.2 final is available.


-- 
Med vänliga hälsningar

Patrick Franz

Bug#1000594: #1000594 / Re: Bug#1027404: RFS: sfeed/1.6-1 [ITP] -- simple RSS and Atom parser

[Joost van Baal-Ilić]

Hi,

FYI: Just uploaded Hiltjo's new sfeed_1.6-1.

Bye,

Joost

Bug#1027855: RM: boost1.80/experimental -- ROM; Package is replaced by a newer 1.80 version

[Anton Gladky]

Package: ftp.debian.org
Severity: normal
User: ftp.debian@packages.debian.org
Usertags: remove

Please remove 1.80 in experimental.

Thanks

Anton

Bug#1023345: spamassassin: plugin eval failed with unknown encoding 'MIME-Header'

[Noah Meyerhans]

On Wed, Nov 02, 2022 at 05:31:33PM +0100, Francesco Potortì wrote:
> Starting few days ago, I get many of these in syslog:
> 
> plugin: eval failed: Unknown encoding 'MIME-Header' at 
> /usr/share/perl5/Mail/SpamAssassin/Message.pm line 1090,  line 8342.
> plugin: eval failed: Unknown encoding 'MIME-Header' at 
> /usr/share/perl5/Mail/SpamAssassin/Message.pm line 1090,  line 248.
> plugin: eval failed: Unknown encoding 'MIME-Header' at 
> /usr/share/perl5/Mail/SpamAssassin/Message.pm line 1090,  line 2683.

Hi Francesco.  Are these issues still happening for you?  I haven't
encountered this myself, and don't see anything that could cause it on
first glance.  If it's still happening with spamassassin 4.0.0-1, please
provide additional debug output as generated when running spamd with the
--debug flag.

noah

Bug#1027854: kismet-plugins: uninstallable due to dependency on libssl1.1

[Christoph Anton Mitterer]

Package: kismet-plugins
Version: 2016.07.R1-1+b1
Severity: grave
Justification: renders package unusable


Hey.

libssl1.1 has been removed from unstable and thus kismet-plugins is no
longer installable.

Cheers,
Chris.

Bug#1027772: (bullseye-pu: package e2tools/0.1.0-3+deb11u1) update debdiff

[肖盛文]

Hi,

    The debdiff had updated in attachment 
e2tools.debdiff_0.1.0-1+deb11u1.txt.

The changes is *minimum* to fix the bug now, Thanks Santiago Vila.

Thanks!

--
肖盛文 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

diff -Nru e2tools-0.1.0/debian/changelog e2tools-0.1.0/debian/changelog
--- e2tools-0.1.0/debian/changelog  2020-12-15 09:50:50.0 +0800
+++ e2tools-0.1.0/debian/changelog  2023-01-04 10:46:06.0 +0800
@@ -1,3 +1,9 @@
+e2tools (0.1.0-1+deb11u1) bullseye; urgency=medium
+
+  * Add e2fsprogs to Build-Depends. Closes: #1027361.
+
+ -- xiao sheng wen   Wed, 04 Jan 2023 10:46:06 +0800
+
 e2tools (0.1.0-1) unstable; urgency=medium
 
   * change Vcs-Git to https://salsa.debian.org/debian/e2tools.git
diff -Nru e2tools-0.1.0/debian/control e2tools-0.1.0/debian/control
--- e2tools-0.1.0/debian/control2020-12-14 14:55:35.0 +0800
+++ e2tools-0.1.0/debian/control2023-01-04 10:46:06.0 +0800
@@ -3,6 +3,7 @@
 Priority: optional
 Maintainer: xiao sheng wen 
 Build-Depends: debhelper-compat (= 13), e2fslibs-dev, uuid-dev, ss-dev,
+ e2fsprogs,
  pkgconf,
 Standards-Version: 4.5.1
 Rules-Requires-Root: no


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1027853: transition: muparserx

[Andreas Bombe]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: transition
X-Debbugs-Cc: mupars...@packages.debian.org
Control: affects -1 + src:muparserx

This is still a package with a soname coupled to its release number, so
there isn't really anything significantly changed.

It has genomicsdb, otb and qiskit-aer as rdepds and I successfully built
all three against the new version. For both genomicsdb and qiskit-aer
the build time testsuite completed without failures. otb does not appear
to have a testsuite.

The auto-muparserx ben tracker appears correct.

Ben file:

title = "muparserx";
is_affected = .depends ~ "libmuparserx4.0.8" | .depends ~ "libmuparserx4.0.11";
is_good = .depends ~ "libmuparserx4.0.11";
is_bad = .depends ~ "libmuparserx4.0.8";

Bug#501456: dpkg: parallel compression and decompression

[Paul Wise]

On Sat, 2022-12-31 at 13:33 +0100, Sebastian Andrzej Siewior wrote:

> What about now given that #956452 has been closed?

That bug/patch seems to have added parallel xz decompression, which is
a good start, but this bug requests parallel compression and parallel
decompression for other compression formats too.

-- 
bye,
pabs

https://wiki.debian.org/PaulWise


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

Bug#310442: rdiff-backup: no way to recover from full filesystem

[Paul Wise]

Control: reopen -1

On Tue, 2023-01-03 at 17:56 -0300, Pablo Mestre wrote:

> Several months have passed since the last check regarding the bug and no
> response has been issued.

Looks like you didn't CC any of the people who were affected,
the Debian bug tracker does not subscribe anyone by default.

> We will proceed to close this bug and then archived if any discrepancy
> arises.

I no longer use rdiff-backup, but the issue seems trivial to test, so
I tested rdiff-backup 2.0.5-4 for this issue and saw it is unfixed.

-- 
bye,
pabs

https://wiki.debian.org/PaulWise


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

Bug#993012: zxing-cpp: please build the example programs into a package

[Paul Wise]

On Tue, 2023-01-03 at 13:54 +0100, Johannes Schauer Marin Rodrigues wrote:

> upstream advises against including the Qt and OpenCV examples in the produced
> binaries. Could you give some context why you think they are useful?

The reason I requested ZXingQtReader and ZXingOpenCV be packaged
is that zxing-cpp isn't well integrated into Linux desktops (at least
not GNOME, but I see there is some KDE integration) so there aren't
many GUI tools that provide its functionality to users and the Qt and
OpenCV zxing-cpp tools, while minimal, do provide useful functionality
to a subset of the potential users. Even if GNOME integration existed,
the tools would be useful in bare-bones window managers like i3 or
sway, or on Linux based mobile devices like the PinePhone, which often
run bare-bones desktops.

-- 
bye,
pabs

https://wiki.debian.org/PaulWise


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

Bug#1027852: sssd not compatible with current python

[Peter Chubb]

Package: python3-sss
Version: 2.8.1-1

A routine apt-get upgrade removed python3-sss because it installed
python3 version 3.11.1-1 and python3-sss has
   Depends:  python3 (<< 3.11)




-- 
Dr Peter Chubbhttps://trustworthy.systems/
Trustworthy Systems GroupCSE, UNSW
Core hours: Mon 8am-3pm; Wed: 8am-5pm; Fri 8am-12pm.

Bug#1026490: sssd: FTBFS: make[1]: *** [debian/rules:102: override_dh_missing] Error 25

[Sergio Durigan Junior]

Control: tags -1 + patch

On Tuesday, December 20 2022, Lucas Nussbaum wrote:

> Source: sssd
> Version: 2.8.1-1
> Severity: serious
> Justification: FTBFS
> Tags: bookworm sid ftbfs
> User: lu...@debian.org
> Usertags: ftbfs-20221220 ftbfs-bookworm
>
> Hi,
>
> During a rebuild of all packages in sid, your package failed to build
> on amd64.
>
>
> Relevant part (hopefully):
>> make[1]: Entering directory '/<>'
>> dh_missing --fail-missing
>> dh_missing: warning: 
>> usr/lib/python3/dist-packages/SSSDConfig-2.8.1.egg-info/PKG-INFO exists in 
>> debian/tmp but is not installed to anywhere 
>> dh_missing: warning: 
>> usr/lib/python3/dist-packages/SSSDConfig-2.8.1.egg-info/dependency_links.txt 
>> exists in debian/tmp but is not installed to anywhere 
>> dh_missing: warning: 
>> usr/lib/python3/dist-packages/SSSDConfig-2.8.1.egg-info/top_level.txt exists 
>> in debian/tmp but is not installed to anywhere 
>> dh_missing: error: missing files, aborting
>>  The following debhelper tools have reported what they installed (with 
>> files per package)
>>   * dh_install: libipa-hbac-dev (3), libipa-hbac0 (2), libnss-sss (1), 
>> libpam-sss (4), libsss-certmap-dev (3), libsss-certmap0 (3), 
>> libsss-idmap-dev (3), libsss-idmap0 (2), libsss-nss-idmap-dev (3), 
>> libsss-nss-idmap0 (2), libsss-simpleifp-dev (4), libsss-simpleifp0 (2), 
>> libsss-sudo (1), python3-libipa-hbac (1), python3-libsss-nss-idmap (1), 
>> python3-sss (5), sssd (0), sssd-ad (3), sssd-ad-common (3), sssd-common 
>> (96), sssd-dbus (5), sssd-idp (4), sssd-ipa (3), sssd-kcm (6), sssd-krb5 
>> (4), sssd-krb5-common (2), sssd-ldap (3), sssd-proxy (2), sssd-tools (14)
>>   * dh_installdocs: libipa-hbac-dev (0), libipa-hbac0 (0), libnss-sss 
>> (0), libpam-sss (0), libsss-certmap-dev (0), libsss-certmap0 (0), 
>> libsss-idmap-dev (0), libsss-idmap0 (0), libsss-nss-idmap-dev (0), 
>> libsss-nss-idmap0 (0), libsss-simpleifp-dev (0), libsss-simpleifp0 (0), 
>> libsss-sudo (0), python3-libipa-hbac (0), python3-libsss-nss-idmap (0), 
>> python3-sss (0), sssd (0), sssd-ad (0), sssd-ad-common (0), sssd-common (1), 
>> sssd-dbus (0), sssd-idp (0), sssd-ipa (0), sssd-kcm (0), sssd-krb5 (0), 
>> sssd-krb5-common (0), sssd-ldap (0), sssd-proxy (0), sssd-tools (0)
>>   * dh_installexamples: libipa-hbac-dev (0), libipa-hbac0 (0), 
>> libnss-sss (0), libpam-sss (0), libsss-certmap-dev (0), libsss-certmap0 (0), 
>> libsss-idmap-dev (0), libsss-idmap0 (0), libsss-nss-idmap-dev (0), 
>> libsss-nss-idmap0 (0), libsss-simpleifp-dev (0), libsss-simpleifp0 (0), 
>> libsss-sudo (0), python3-libipa-hbac (0), python3-libsss-nss-idmap (0), 
>> python3-sss (0), sssd (0), sssd-ad (0), sssd-ad-common (0), sssd-common (1), 
>> sssd-dbus (0), sssd-idp (0), sssd-ipa (0), sssd-kcm (0), sssd-krb5 (0), 
>> sssd-krb5-common (0), sssd-ldap (0), sssd-proxy (0), sssd-tools (0)
>>  If the missing files are installed by another tool, please file a bug 
>> against it.
>>  When filing the report, if the tool is not part of debhelper itself, 
>> please reference the
>>  "Logging helpers and dh_missing" section from the "PROGRAMMING" guide 
>> for debhelper (10.6.3+).
>>(in the debhelper package: /usr/share/doc/debhelper/PROGRAMMING.gz)
>>  Be sure to test with dpkg-buildpackage -A/-B as the results may vary 
>> when only a subset is built
>>  If the omission is intentional or no other helper can take care of this 
>> consider adding the
>>  paths to debian/not-installed.
>> make[1]: *** [debian/rules:102: override_dh_missing] Error 25
>
>
> The full build log is available from:
> http://qa-logs.debian.net/2022/12/20/sssd_2.8.1-1_unstable.log

The following MR should be fix this:

  https://salsa.debian.org/sssd-team/sssd/-/merge_requests/20

Cheers,

-- 
Sergio
GPG key ID: 237A 54B1 0287 28BF 00EF  31F4 D0EB 7628 65FC 5E36
Please send encrypted e-mail if possible
https://sergiodj.net/


signature.asc
Description: PGP signature

Bug#1027851: pytorch FTBFS with Python 3.11 as default version

[Adrian Bunk]

Source: pytorch
Version: 1.12.1-1
Severity: serious
Forwarded: https://github.com/pytorch/pytorch/pull/81242

https://buildd.debian.org/status/fetch.php?pkg=pytorch=amd64=1.12.1-1%2Bb2=1672759960=0

...
FAILED: caffe2/torch/CMakeFiles/torch_python.dir/csrc/Stream.cpp.o 
/usr/bin/c++ -DAT_PER_OPERATOR_HEADERS -DBUILDING_TESTS -DGFLAGS_IS_A_DLL=0 
-DGLOG_CUSTOM_PREFIX_SUPPORT -DHAVE_MALLOC_USABLE_SIZE=1 -DHAVE_MMAP=1 
-DHAVE_SHM_OPEN=1 -DHAVE_SHM_UNLINK=1 -DMINIZ_DISABLE_ZIP_READER_CRC32_CHECKS 
-DONNXIFI_ENABLE_EXT=1 -DONNX_ML=1 -DONNX_NAMESPACE=onnx -DTHP_BUILD_MAIN_LIB 
-DUSE_C10D -DUSE_C10D_GLOO -DUSE_DISTRIBUTED -DUSE_EXTERNAL_MZCRC -DUSE_NUMPY 
-DUSE_RPC -DUSE_TENSORPIPE -DUSE_VALGRIND -D_FILE_OFFSET_BITS=64 
-Dtorch_python_EXPORTS -I/<>/build/aten/src 
-I/<>/aten/src -I/<>/build -I/<> 
-I/<>/cmake/../third_party/benchmark/include 
-I/<>/debian/foxi -I/<>/build/debian/foxi 
-I/<>/torch/.. -I/<>/torch/../aten/src 
-I/<>/torch/../aten/src/TH 
-I/<>/build/caffe2/aten/src -I/<>/build/third_party 
-I/<>/build/third_party/onnx 
-I/<>/torch/../third_party/valgrind-headers 
-I/<>/torch/../third_party/gloo 
-I/<>/torch/../third_party/onnx 
-I/<>/torch/../third_party/flatbuffers/include 
-I/<>/torch/csrc -I/<>/torch/csrc/api/include 
-I/<>/torch/lib -I/<>/torch/lib/libshm 
-I/<>/torch/csrc/distributed -I/<>/torch/csrc/api 
-I/<>/c10/.. 
-I/<>/torch/lib/libshm/../../../torch/lib -isystem 
/<>/build/third_party/gloo -isystem 
/<>/cmake/../third_party/gloo -isystem 
/<>/cmake/../third_party/googletest/googlemock/include -isystem 
/<>/cmake/../third_party/googletest/googletest/include -isystem 
/usr/include/opencv4 -isystem /usr/include/eigen3 -isystem 
/usr/include/python3.11 -isystem 
/usr/lib/python3/dist-packages/numpy/core/include -Wdate-time 
-D_FORTIFY_SOURCE=2 -g -O2 -ffile-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -gsplit-dwarf 
-fvisibility-inlines-hidden -DUSE_PTHREADPOOL -fopenmp -DUSE_PYTORCH_QNNPACK 
-DUSE_XNNPACK -DSYMBOLICATE_MOBILE_DEBUG_HANDLE -DEDGE_PROFILER_USE_KINETO -O2 
-fPIC -Wno-narrowing -Wall -Wextra -Werror=return-type 
-Wno-missing-field-initializers -Wno-type-limits -Wno-array-bounds 
-Wno-unknown-pragmas -Wno-unused-parameter -Wno-unused-function 
-Wno-unused-result -Wno-unused-local-typedefs -Wno-strict-overflow 
-Wno-strict-aliasing -Wno-error=deprecated-declarations -Wno-stringop-overflow 
-Wno-psabi -Wno-error=pedantic -Wno-error=redundant-decls 
-Wno-error=old-style-cast -fdiagnostics-color=always -faligned-new 
-Wno-unused-but-set-variable -Wno-maybe-uninitialized -fno-math-errno 
-fno-trapping-math -Werror=format -Werror=cast-function-type 
-Wno-stringop-overflow -DHAVE_AVX512_CPU_DEFINITION -DHAVE_AVX2_CPU_DEFINITION 
-O2 -g -DNDEBUG -fPIC -DCAFFE2_USE_GLOO -DTH_HAVE_THREAD -Wno-unused-variable 
-fno-strict-aliasing -Wno-write-strings -Wno-strict-aliasing -std=gnu++14 -MD 
-MT caffe2/torch/CMakeFiles/torch_python.dir/csrc/Stream.cpp.o -MF 
caffe2/torch/CMakeFiles/torch_python.dir/csrc/Stream.cpp.o.d -o 
caffe2/torch/CMakeFiles/torch_python.dir/csrc/Stream.cpp.o -c 
/<>/torch/csrc/Stream.cpp
In file included from /usr/include/python3.11/Python.h:44,
 from /usr/include/pybind11/detail/common.h:266,
 from /usr/include/pybind11/attr.h:13,
 from /usr/include/pybind11/detail/class.h:12,
 from /usr/include/pybind11/pybind11.h:13,
 from /<>/torch/csrc/Stream.cpp:1:
/<>/torch/csrc/Stream.cpp: In function ‘void 
THPStream_init(PyObject*)’:
/<>/torch/csrc/Stream.cpp:112:3: error: lvalue required as left 
operand of assignment
  112 |   Py_TYPE() = _Type;
  |   ^~~
...

Bug#1027850: graph-tool FTBFS with Python 3.11 as default version

[Adrian Bunk]

Source: graph-tool
Version: 2.45+ds-9
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/fetch.php?pkg=graph-tool=amd64=2.45%2Bds-9%2Bb1=1672782255=0

...
TEST STARTED Tue Jan 3 21:43:53 UTC 2023
rm -f _BUILD/test.png
PYTHONPATH=/<>/debian/tmp//usr/lib/python3.11/dist-packages \
python3 -c "\
from graph_tool.all import *; \
show_config(); \
g = random_graph(10, lambda: 5, directed=False); \
graph_draw(g, output='_BUILD/test.png'); \
"
Matplotlib created a temporary config/cache directory at 
/tmp/matplotlib-vsfk88vs because the default path 
(/sbuild-nonexistent/.config/matplotlib) is not a writable directory; it is 
highly recommended to set the MPLCONFIGDIR environment variable to a writable 
directory, in particular to speed up the import of Matplotlib and to better 
support multiprocessing.
Traceback (most recent call last):
  File "", line 1, in 
  File 
"/<>/debian/tmp/usr/lib/python3.11/dist-packages/graph_tool/generation/__init__.py",
 line 370, in random_graph
if len(inspect.getargspec(deg_sampler)[0]) > 0:
   ^^
AttributeError: module 'inspect' has no attribute 'getargspec'. Did you mean: 
'getargs'?
version: 2.45
gcc version: 12.2.0
compilation flags: -DNDEBUG -Wdate-time -D_FORTIFY_SOURCE=2 -fopenmp -O3 
-fvisibility=default -fvisibility-inlines-hidden -Wno-deprecated -Wall -Wextra 
-ftemplate-backtrace-limit=0 -g -O2 -ffile-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wl,-z,relro 
-Wl,-z,now
install prefix: /usr
python dir: /usr/lib/python3.11/dist-packages
graph filtering: True
openmp: True
uname: Linux x86-csail-01 5.10.0-20-amd64 #1 SMP Debian 5.10.158-2 (2022-12-13) 
x86_64
make[1]: *** [debian/rules:43: override_dh_auto_install] Error 1



https://docs.python.org/3/whatsnew/3.11.html

...
Removed from the inspect module:

The getargspec() function, deprecated since Python 3.0; use 
inspect.signature() or inspect.getfullargspec() instead.
https://docs.python.org/3/whatsnew/3.11.html

...

Bug#1027849: zeroc-ice FTBFS with Python 3.11 as default version

[Adrian Bunk]

Source: zeroc-ice
Version: 3.7.8-1
Severity: serious
Tags: ftbfs patch
Forwarded: https://github.com/zeroc-ice/ice/pull/1394

https://buildd.debian.org/status/fetch.php?pkg=zeroc-ice=amd64=3.7.8-1%2Bb2=1672771157=0

...
modules/IcePy/Slice.cpp:17:10: fatal error: eval.h: No such file or directory
   17 | #include 
  |  ^~~~
compilation terminated.
make[3]: *** [Makefile:32: 
modules/IcePy/build/x86_64-linux-gnu/shared/pic/Slice.o] Error 1

Bug#1027832: debian-policy: Please clarify that priority required packages are not automatically build essential

[Sam Hartman]

> "Santiago" == Santiago Vila  writes:


Santiago> As an example, packages tzdata, mount or e2fsprogs are not
Santiago> build-essential and afaik have not been for a long time,
Santiago> but there are still people who believe that they are
Santiago> build-essential for the mere fact that they are
Santiago> priority:required.

Why not just make all required packages build-essential?
I agree we should fix the class of bugs you are talking about, but it
seems like in some cases it might be easier to fix them by declaring
them not buggy.

Bug#1027848: On Tyan TN71-BP012 (POWER8) bookworm-DI-alpha1 shutdown is not working.

[oliviosu_ppc64el]

Package: installation-reports

Boot method: USB stick
Image version: 
https://cdimage.debian.org/cdimage/bookworm_di_alpha1/ppc64el/iso-dvd/debian-bookworm-DI-alpha1-ppc64el-DVD-1.iso
Date: 2022-01-03

Machine: Tyan TN71-BP012
Processor: ppc64el POWER8 (raw), altivec supported
Memory: 133598MB
Partitions:
Filesystem Type 1K-blocks    Used Available Use% Mounted on
udev   devtmpfs  63413824   0  63413824   0% /dev
tmpfs  tmpfs 13358656   16960  13341696   1% /run
/dev/sda2  ext4 238263032 4465168 221621944   2% /
tmpfs  tmpfs 66793024   0  66793024   0% /dev/shm
tmpfs  tmpfs 5120   0  5120   0% /run/lock
tmpfs  tmpfs 13358592 832  13357760   1% /run/user/1000


Output of lspci -knn (or lspci -nn):
:00:00.0 PCI bridge [0604]: IBM POWER8 Host Bridge (PHB3) [1014:03dc]
0001:00:00.0 PCI bridge [0604]: IBM POWER8 Host Bridge (PHB3) [1014:03dc]
0001:01:00.0 PCI bridge [0604]: PLX Technology, Inc. PEX 8748 48-Lane, 12-Port 
PCI Express Gen 3 (8 GT/s) Switch, 27 x 27mm FCBGA [10b5:8748] (rev ca)
Subsystem: PLX Technology, Inc. PEX 8748 48-Lane, 12-Port PCI Express Gen 3 (8 
GT/s) Switch, 27 x 27mm FCBGA [10b5:8748]
0001:02:01.0 PCI bridge [0604]: PLX Technology, Inc. PEX 8748 48-Lane, 12-Port 
PCI Express Gen 3 (8 GT/s) Switch, 27 x 27mm FCBGA [10b5:8748] (rev ca)
Subsystem: PLX Technology, Inc. PEX 8748 48-Lane, 12-Port PCI Express Gen 3 (8 
GT/s) Switch, 27 x 27mm FCBGA [10b5:8748]
0001:02:02.0 PCI bridge [0604]: PLX Technology, Inc. PEX 8748 48-Lane, 12-Port 
PCI Express Gen 3 (8 GT/s) Switch, 27 x 27mm FCBGA [10b5:8748] (rev ca)
Subsystem: PLX Technology, Inc. PEX 8748 48-Lane, 12-Port PCI Express Gen 3 (8 
GT/s) Switch, 27 x 27mm FCBGA [10b5:8748]
0001:02:08.0 PCI bridge [0604]: PLX Technology, Inc. PEX 8748 48-Lane, 12-Port 
PCI Express Gen 3 (8 GT/s) Switch, 27 x 27mm FCBGA [10b5:8748] (rev ca)
Subsystem: PLX Technology, Inc. PEX 8748 48-Lane, 12-Port PCI Express Gen 3 (8 
GT/s) Switch, 27 x 27mm FCBGA [10b5:8748]
0001:02:09.0 PCI bridge [0604]: PLX Technology, Inc. PEX 8748 48-Lane, 12-Port 
PCI Express Gen 3 (8 GT/s) Switch, 27 x 27mm FCBGA [10b5:8748] (rev ca)
Subsystem: PLX Technology, Inc. PEX 8748 48-Lane, 12-Port PCI Express Gen 3 (8 
GT/s) Switch, 27 x 27mm FCBGA [10b5:8748]
0001:02:0a.0 PCI bridge [0604]: PLX Technology, Inc. PEX 8748 48-Lane, 12-Port 
PCI Express Gen 3 (8 GT/s) Switch, 27 x 27mm FCBGA [10b5:8748] (rev ca)
Subsystem: PLX Technology, Inc. PEX 8748 48-Lane, 12-Port PCI Express Gen 3 (8 
GT/s) Switch, 27 x 27mm FCBGA [10b5:8748]
0001:02:10.0 PCI bridge [0604]: PLX Technology, Inc. PEX 8748 48-Lane, 12-Port 
PCI Express Gen 3 (8 GT/s) Switch, 27 x 27mm FCBGA [10b5:8748] (rev ca)
Subsystem: PLX Technology, Inc. PEX 8748 48-Lane, 12-Port PCI Express Gen 3 (8 
GT/s) Switch, 27 x 27mm FCBGA [10b5:8748]
0001:02:11.0 PCI bridge [0604]: PLX Technology, Inc. PEX 8748 48-Lane, 12-Port 
PCI Express Gen 3 (8 GT/s) Switch, 27 x 27mm FCBGA [10b5:8748] (rev ca)
Subsystem: PLX Technology, Inc. PEX 8748 48-Lane, 12-Port PCI Express Gen 3 (8 
GT/s) Switch, 27 x 27mm FCBGA [10b5:8748]
0001:03:00.0 Ethernet controller [0200]: Mellanox Technologies MT27520 Family 
[ConnectX-3 Pro] [15b3:1007]
Subsystem: Mellanox Technologies MT27520 Family [ConnectX-3 Pro] [15b3:0050]
Kernel driver in use: mlx4_core
Kernel modules: mlx4_core
0001:04:00.0 Ethernet controller [0200]: Mellanox Technologies MT27520 Family 
[ConnectX-3 Pro] [15b3:1007]
Subsystem: Mellanox Technologies MT27520 Family [ConnectX-3 Pro] [15b3:0050]
Kernel driver in use: mlx4_core
Kernel modules: mlx4_core
0001:05:00.0 SATA controller [0106]: Marvell Technology Group Ltd. 88SE9235 
PCIe 2.0 x2 4-port SATA 6 Gb/s Controller [1b4b:9235] (rev 11)
Subsystem: Marvell Technology Group Ltd. 88SE9235 PCIe 2.0 x2 4-port SATA 6 
Gb/s Controller [1b4b:9235]
Kernel driver in use: ahci
Kernel modules: ahci
0001:06:00.0 USB controller [0c03]: Texas Instruments TUSB73x0 SuperSpeed USB 
3.0 xHCI Host Controller [104c:8241] (rev 02)
Kernel driver in use: xhci_hcd
Kernel modules: xhci_pci
0001:07:00.0 PCI bridge [0604]: ASPEED Technology, Inc. AST1150 PCI-to-PCI 
Bridge [1a03:1150] (rev 03)
Subsystem: ASPEED Technology, Inc. AST1150 PCI-to-PCI Bridge [1a03:1150]
0001:08:00.0 VGA compatible controller [0300]: ASPEED Technology, Inc. ASPEED 
Graphics Family [1a03:2000] (rev 30)
Subsystem: ASPEED Technology, Inc. ASPEED Graphics Family [1a03:2000]
Kernel driver in use: ast
Kernel modules: ast
0002:00:00.0 PCI bridge [0604]: IBM POWER8 Host Bridge (PHB3) [1014:03dc]



Base System Installation Checklist:
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it

Initial boot:   [O] *no grub menu for boot media (USB stick) have to 
create menu entry in Petitboot
Detect network card:    [O] *firmware non free 
needed.(firmware-misc-nonfree_20221214-3_all.deb) mlx4_core
Configure network:  [O]
Detect media:   [O]
Load installer modules: [O]

Bug#1027831: libpackagekitqt5-1: Discover does not notify about pending updates

[Matthias Klumpp]

Hi!
Can you please report this against PackageKit-Qt so we have a reference there?
It's an odd bug for sure, the amount of changes for the new QPK was
quite small and overall the library seems to be working fine. I wonder
whether this is a case of Discover not having adjusted to handle
plural signals from PK properly.

Cheers,
Matthias

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

Bug#1026062: kded5: kded crashes with signal 11

[Bernhard Übelacker]

Dear Maintainer,
I was able to reproduce this issue inside a minimal
amd64 qemu VM running Bookworm/testing.

By editing the kded service unit [1] I could get valgrind have a look
at this issue and it produced a matching use-after-free [2].

By further editing the service unit I was also able to record
such a crash with rr-debugger, that allows debugging in
reverse execution direction.


So I guess these are the relevant events:

- A object of PackageKit::Transaction gets created [3] (0x562777928e00)

- Inside its constructor also a QDeferredDeleteEvent
  gets created [4] (0x562777885690)

- The PackageKit::Transaction object gets stored in the
  m_transactions container [5]

- Qt reaches its event loop and processes the QDeferredDeleteEvent
  and deletes the PackageKit::Transaction [6]

- In TransactionWatcher::watchTransaction the member m_transactions
  still holds a reference to the already deleted object and gets
  found because a matching "tid" gets processed.
  "Unfortunately" the memory of the PackageKit::Transaction was
  already modified therefore the segmentation fault follows. [7]


For comparision the matching systemd-coredump
report with mangled symbols in [8].

There are some reports in bugs.kde.org [9].
But in 462706 it is mentioned that this is an issue
in packagekit-qt, unfortunately could not yet
find a report there.


Kind regards,
Bernhard






[1]
/usr/lib/systemd/user/plasma-kded.service
-ExecStart=/usr/bin/kded5
+ExecStart=/usr/bin/valgrind /usr/bin/kded5
or
+ExecStart=/usr/bin/rr record /usr/bin/kded5

systemctl --user daemon-reload
systemctl --user start plasma-kded

Then trigger in Discover a package list update.




[2]
==12351== Invalid read of size 8
==12351==at 0x27458BA0: PackageKit::Transaction::role() const 
(transaction.cpp:297)
==12351==by 0x273B6AAD: TransactionWatcher::watchTransaction(QDBusObjectPath 
const&, bool) (TransactionWatcher.cpp:104)
==12351==by 0x273B6B98: TransactionWatcher::transactionListChanged(QStringList 
const&) (TransactionWatcher.cpp:85)
==12351==by 0x5B59FCE: ??? (in 
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5.15.7)
==12351==by 0x2744C094: PackageKit::Daemon::transactionListChanged(QStringList 
const&) (moc_daemon.cpp:419)
==12351==by 0x5B59FFB: ??? (in 
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5.15.7)
==12351==by 0x27464B37: TransactionListChanged (daemonproxy.moc:331)
==12351==by 0x27464B37: 
OrgFreedesktopPackageKitInterface::qt_static_metacall(QObject*, 
QMetaObject::Call, int, void**) (daemonproxy.moc:178)
==12351==by 0x27465D72: 
OrgFreedesktopPackageKitInterface::qt_metacall(QMetaObject::Call, int, void**) 
(daemonproxy.moc:288)
==12351==by 0x580361A: ??? (in 
/usr/lib/x86_64-linux-gnu/libQt5DBus.so.5.15.7)
==12351==by 0x5B4E76F: QObject::event(QEvent*) (in 
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5.15.7)
==12351==by 0x49CAF5D: QApplicationPrivate::notify_helper(QObject*, 
QEvent*) (in /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5.15.7)
==12351==by 0x5B227C7: QCoreApplication::notifyInternal2(QObject*, QEvent*) 
(in /usr/lib/x86_64-linux-gnu/libQt5Core.so.5.15.7)
==12351==  Address 0x1a6a2a10 is 16 bytes inside a block of size 24 free'd
==12351==at 0x484371B: operator delete(void*) (vg_replace_malloc.c:923)
==12351==by 0x5B4E53E: QObject::event(QEvent*) (in 
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5.15.7)
==12351==by 0x49CAF5D: QApplicationPrivate::notify_helper(QObject*, 
QEvent*) (in /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5.15.7)
==12351==by 0x5B227C7: QCoreApplication::notifyInternal2(QObject*, QEvent*) 
(in /usr/lib/x86_64-linux-gnu/libQt5Core.so.5.15.7)
==12351==by 0x5B25760: QCoreApplicationPrivate::sendPostedEvents(QObject*, 
int, QThreadData*) (in /usr/lib/x86_64-linux-gnu/libQt5Core.so.5.15.7)
==12351==by 0x5B7B1D2: ??? (in 
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5.15.7)
==12351==by 0x6E1B7A8: g_main_context_dispatch (in 
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.7400.4)
==12351==by 0x6E1BA37: ??? (in 
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.7400.4)
==12351==by 0x6E1BACB: g_main_context_iteration (in 
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.7400.4)
==12351==by 0x5B7A8B5: 
QEventDispatcherGlib::processEvents(QFlags) (in 
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5.15.7)
==12351==by 0x5B2124A: 
QEventLoop::exec(QFlags) (in 
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5.15.7)
==12351==by 0x5B293B5: QCoreApplication::exec() (in 
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5.15.7)
==12351==  Block was alloc'd at
==12351==at 0x4840F2F: operator new(unsigned long) (vg_replace_malloc.c:422)
==12351==by 0x273B693B: TransactionWatcher::watchTransaction(QDBusObjectPath 
const&, bool) (TransactionWatcher.cpp:95)
==12351==by 0x273B6B98: TransactionWatcher::transactionListChanged(QStringList 
const&) (TransactionWatcher.cpp:85)
==12351==by 0x5B59FCE: ??? (in 
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5.15.7)
==12351==by 

Bug#1027418: autopkgtest failure - iconv issue?

[Changwoo Ryu]

Control: severity -1 normal
Control: notfound -1 0.7.92-1

This bug appears to occur only in an incomplete chroot environment.

Please check your chroot again. You can reopen if it still occurs in a
general environment.

Bug#1027176: u-boot-amlogic: broken non-EFI boot on odroid-c2

[Vagrant Cascadian]

On 2023-01-03, Vagrant Cascadian wrote:
> On 2023-01-03, Vagrant Cascadian wrote:
>> On 2023-01-02, Vagrant Cascadian wrote:
>>> On 2023-01-02, Vagrant Cascadian wrote:
 On 2022-12-28, Vagrant Cascadian wrote:
> The odroid-c2 fails to boot syslinux/extlinux style menus (e.g. those
> produced by u-boot-menu) or boot.scr as of upstream 2022.07-rc1. The
> commit triggering the issue has been identified as:
>
>   a9bf024b2933bba0e23038892970a18b72dfaeb4
>   efi_loader: disk: a helper function to create efi_disk objects from
>   udevice
>
> Workarounds I've heard are to disable EFI support for that board
>>> ...
 Obviously, it breaks EFI booting...

 Worst case, I suppose we could create two variants, one with EFI, one
 without...
>>>
>>> I have pushed a patch to git implementing an odroid-c2-noefi variant:
>>>
>>>   
>>> https://salsa.debian.org/debian/u-boot/-/commit/711ca985af1cab6f11e33fcf5e30dcc40dc7e64d
>>>
>>> This would not close the bug, but at least downgrade the severity...
>>
>> I can confirm that 2023.01-rc4+dfsg-1 does boot successfully with EFI on
>> the odroid-c2, so ... the two variant solution is a viable one if a
>> proper fix cannot be figured out in time for bookworm.
>
> From irc.libera.chat #u-boot:
>
>  < xypron> Tartarus: Loading Ramdisk to 7a896000, end 7bf3eb78
>overwrites internal memory structures of the EFI subsystem
>which leads to the crash on the Odroid C2. Why do we copy
>initrd to high memory at all?
> 
>  < xypron> vagrantc: Tartarus: setenv initrd_high 0x;
>setenv fdt_high 0x solves the problem on the
>Odroid C2
>
> I can confirm this works around the issue, although it may also cause
> other problems and should not be the default...

Another possible workaround...

  < Tartarus> A less dangerous work-around would be to us bootm_low or
  bootm_size (See
  https://u-boot.readthedocs.io/en/latest/usage/environment.html)
  to limit where relocations can be

live well,
  vagrant


signature.asc
Description: PGP signature

Bug#1027176: u-boot-amlogic: broken non-EFI boot on odroid-c2

[Vagrant Cascadian]

On 2023-01-03, Vagrant Cascadian wrote:
> On 2023-01-02, Vagrant Cascadian wrote:
>> On 2023-01-02, Vagrant Cascadian wrote:
>>> On 2022-12-28, Vagrant Cascadian wrote:
 The odroid-c2 fails to boot syslinux/extlinux style menus (e.g. those
 produced by u-boot-menu) or boot.scr as of upstream 2022.07-rc1. The
 commit triggering the issue has been identified as:

   a9bf024b2933bba0e23038892970a18b72dfaeb4
   efi_loader: disk: a helper function to create efi_disk objects from
   udevice

 Workarounds I've heard are to disable EFI support for that board
>> ...
>>> Obviously, it breaks EFI booting...
>>>
>>> Worst case, I suppose we could create two variants, one with EFI, one
>>> without...
>>
>> I have pushed a patch to git implementing an odroid-c2-noefi variant:
>>
>>   
>> https://salsa.debian.org/debian/u-boot/-/commit/711ca985af1cab6f11e33fcf5e30dcc40dc7e64d
>>
>> This would not close the bug, but at least downgrade the severity...
>
> I can confirm that 2023.01-rc4+dfsg-1 does boot successfully with EFI on
> the odroid-c2, so ... the two variant solution is a viable one if a
> proper fix cannot be figured out in time for bookworm.

From irc.libera.chat #u-boot:

 < xypron> Tartarus: Loading Ramdisk to 7a896000, end 7bf3eb78
   overwrites internal memory structures of the EFI subsystem
   which leads to the crash on the Odroid C2. Why do we copy
   initrd to high memory at all?

 < xypron> vagrantc: Tartarus: setenv initrd_high 0x;
   setenv fdt_high 0x solves the problem on the
   Odroid C2

I can confirm this works around the issue, although it may also cause
other problems and should not be the default...

live well,
  vagrant


signature.asc
Description: PGP signature

Bug#1027176: u-boot-amlogic: broken non-EFI boot on odroid-c2

[Heinrich Schuchardt]

Hello Vagrant,

copying initrd to high memory overwrites internal EFI structures.

setenv initrd_high 0x
setenv fdt_high 0x

solves the problem on the Odroid C2.

Best regards

Heinrich

Bug#1027793: closed by Debian FTP Masters (reply to James McCoy ) (Bug#1027766: fixed in vim 2:9.0.1000-3)

[James McCoy]

On Tue, Jan 03, 2023 at 09:15:36PM +0100, Alejandro Colomar wrote:
> Hi,
> 
> On 1/3/23 17:09, Debian Bug Tracking System wrote:
> > This is an automatic notification regarding your Bug report
> > which was filed against the vim-common package:
> > 
> > #1027793: vim: insert mode: Backspace doesn't do anything
> > 
> > It has been closed by Debian FTP Masters  
> > (reply to James McCoy ).
> > 
> > Their explanation is attached below along with your original report.
> > If this explanation is unsatisfactory and you have not received a
> > better one in a separate message then please contact Debian FTP Masters 
> >  (reply to James McCoy 
> > ) by
> > replying to this email.
> > 
> 
> For my own curiosity, would you mind pointing to the specific change that
> fixed this bug?

https://salsa.debian.org/vim-team/vim/-/commit/7bdf6feff01b77304c2d1a8af335bd57689b4c66

Cheers,
-- 
James
GPG Key: 4096R/91BF BF4D 6956 BD5D F7B7  2D23 DFE6 91AE 331B A3DB

Bug#1027847: libsigrokdecode FTBFS with Python 3.11 as default version

[Adrian Bunk]

Source: libsigrokdecode
Version: 0.5.3-3
Severity: serious

https://buildd.debian.org/status/fetch.php?pkg=libsigrokdecode=amd64=0.5.3-3%2Bb1=1672741924=0

...
Detected libraries (required):
 - glib-2.0 >= 2.34 2.74.4
 - python-3.10-embed... no
 - python-3.9-embed no
 - python-3.8-embed no
...
/bin/bash ./libtool  --tag=CC   --mode=link gcc -std=c99 -fvisibility=hidden 
-Wall -Wextra -Wmissing-prototypes -Wshadow -Wformat=2 -Wno-format-nonliteral 
-Wfloat-equal -pthread -I/usr/include/glib-2.0 
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/python3.11 
-I/usr/include/x86_64-linux-gnu/python3.11  -g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security  -Wl,-z,relro -Wl,--as-needed -o tests/main 
tests/main-main.o tests/main-core.o tests/main-decoder.o tests/main-inst.o 
tests/main-session.o libsigrokdecode.la -lm -lcheck_pic -lrt -lm -lsubunit 
-lglib-2.0  
libtool: link: gcc -std=c99 -fvisibility=hidden -Wall -Wextra 
-Wmissing-prototypes -Wshadow -Wformat=2 -Wno-format-nonliteral -Wfloat-equal 
-I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include 
-I/usr/include/python3.11 -I/usr/include/x86_64-linux-gnu/python3.11 -g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wl,-z -Wl,relro -Wl,--as-needed -o tests/.libs/main 
tests/main-main.o tests/main-core.o tests/main-decoder.o tests/main-inst.o 
tests/main-session.o  ./.libs/libsigrokdecode.so -lcheck_pic -lrt -lm -lsubunit 
-lglib-2.0 -pthread
/usr/bin/ld: ./.libs/libsigrokdecode.so: undefined reference to `PyList_Insert'
/usr/bin/ld: ./.libs/libsigrokdecode.so: undefined reference to 
`PyModule_AddObject'
/usr/bin/ld: ./.libs/libsigrokdecode.so: undefined reference to 
`PySys_GetObject'
/usr/bin/ld: ./.libs/libsigrokdecode.so: undefined reference to 
`PyDict_SetItemString'
/usr/bin/ld: ./.libs/libsigrokdecode.so: undefined reference to 
`PyType_GenericNew'
/usr/bin/ld: ./.libs/libsigrokdecode.so: undefined reference to 
`PyImport_Import'
/usr/bin/ld: ./.libs/libsigrokdecode.so: undefined reference to `PyList_GetItem'
/usr/bin/ld: ./.libs/libsigrokdecode.so: undefined reference to 
`PyBytes_AsStringAndSize'
/usr/bin/ld: ./.libs/libsigrokdecode.so: undefined reference to 
`PyObject_CallMethod'
/usr/bin/ld: ./.libs/libsigrokdecode.so: undefined reference to 
`PyGILState_Release'
/usr/bin/ld: ./.libs/libsigrokdecode.so: undefined reference to `PyBytes_Size'
/usr/bin/ld: ./.libs/libsigrokdecode.so: undefined reference to 
`PyBool_FromLong'
/usr/bin/ld: ./.libs/libsigrokdecode.so: undefined reference to 
`PyUnicode_FromString'
/usr/bin/ld: ./.libs/libsigrokdecode.so: undefined reference to 
`PyObject_CallFunctionObjArgs'
/usr/bin/ld: ./.libs/libsigrokdecode.so: undefined reference to 
`PyExc_TypeError'
/usr/bin/ld: ./.libs/libsigrokdecode.so: undefined reference to 
`Py_InitializeEx'
/usr/bin/ld: ./.libs/libsigrokdecode.so: undefined reference to 
`PyExc_Exception'
/usr/bin/ld: ./.libs/libsigrokdecode.so: undefined reference to `PyObject_Str'
/usr/bin/ld: ./.libs/libsigrokdecode.so: undefined reference to `PyDict_Next'
/usr/bin/ld: ./.libs/libsigrokdecode.so: undefined reference to `PyLong_AsLong'
/usr/bin/ld: ./.libs/libsigrokdecode.so: undefined reference to 
`PyModule_AddIntConstant'
/usr/bin/ld: ./.libs/libsigrokdecode.so: undefined reference to `PyErr_Format'
/usr/bin/ld: ./.libs/libsigrokdecode.so: undefined reference to 
`PyFloat_FromDouble'
/usr/bin/ld: ./.libs/libsigrokdecode.so: undefined reference to 
`PyArg_ParseTuple'
/usr/bin/ld: ./.libs/libsigrokdecode.so: undefined reference to `PyErr_Occurred'
/usr/bin/ld: ./.libs/libsigrokdecode.so: undefined reference to `PySet_Pop'
/usr/bin/ld: ./.libs/libsigrokdecode.so: undefined reference to 
`PyObject_IsSubclass'
/usr/bin/ld: ./.libs/libsigrokdecode.so: undefined reference to 
`PyArg_ParseTupleAndKeywords'
/usr/bin/ld: ./.libs/libsigrokdecode.so: undefined reference to `PyFloat_Type'
/usr/bin/ld: ./.libs/libsigrokdecode.so: undefined reference to 
`PyExc_IndexError'
/usr/bin/ld: ./.libs/libsigrokdecode.so: undefined reference to 
`PyEval_InitThreads'
/usr/bin/ld: ./.libs/libsigrokdecode.so: undefined reference to 
`_Py_FalseStruct'
/usr/bin/ld: ./.libs/libsigrokdecode.so: undefined reference to 
`PyEval_RestoreThread'
/usr/bin/ld: ./.libs/libsigrokdecode.so: undefined reference to 
`PyBytes_AsString'
/usr/bin/ld: ./.libs/libsigrokdecode.so: undefined reference to 
`PyType_FromSpec'
/usr/bin/ld: ./.libs/libsigrokdecode.so: undefined reference to `_Py_TrueStruct'
/usr/bin/ld: ./.libs/libsigrokdecode.so: undefined reference to 
`PyEval_SaveThread'
/usr/bin/ld: ./.libs/libsigrokdecode.so: undefined reference to `PyDict_Size'
/usr/bin/ld: ./.libs/libsigrokdecode.so: undefined reference to 
`PySequence_GetItem'
/usr/bin/ld: ./.libs/libsigrokdecode.so: undefined reference to `PyDict_GetItem'
/usr/bin/ld: ./.libs/libsigrokdecode.so: undefined 

Bug#1026388: [Pkg-utopia-maintainers] Bug#1026388: network-manager: Please use upstream default paths for NM libexec binaries in /usr/libexec

[Michael Biebl]

Am 03.01.23 um 16:20 schrieb Neal Gompa:

On Mon, Dec 19, 2022 at 11:52 AM Michael Biebl  wrote:


Am 19.12.22 um 15:44 schrieb Neal Gompa:


It does, though if all these packages are group-maintained by Utopia,
wouldn't it be possible to do the path migration for Bookworm through
NMUs?


They aren't unfortunately. Only three of the above 10 VPN plugins are
maintained within the utopia. Otherwise I agree it would have been
rather easy.


Maybe something to also fix is getting team co-maintainer privileges
for those packages so transitions like this are easy. Or maybe just
email them and ask? They might just go ahead and do it.

The status quo is pretty painful for upstream development on Debian. :(




I'm sorry to hear that.

Not sure if there is much I can do about that, though.
NetworkManager-$VPN packages that want to move under the pkg-utopia 
umbrella are certainly welcome.

I can't force those maintainers though.

Michael


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1027846: btrfsmaintenance: changing BTRFS_BALANCE_PERIOD, BTRFS_SCRUB_PERIOD etc. via systemd timer doesn't work

[andrew bezella]

Package: btrfsmaintenance
Version: 0.5-1
Severity: normal
Tags: patch upstream

Dear Maintainer,

when changing BTRFS_BALANCE_PERIOD, BTRFS_SCRUB_PERIOD etc. via systemd timer
the existing OnCalender entry needs to be emptied first as systemd timers are 
cumulative.

i had updated /etc/default/btrfsmaintenance to include:
BTRFS_SCRUB_PERIOD="quarterly"

and ran `sudo systemctl restart btrfsmaintenance-refresh.service` 
but noticed that this change was not reflected in the systemctl output:
NEXTLEFTLAST
PASSED UNITACTIVATES
Wed 2023-02-01 00:00:00 PST 4 weeks 0 days left Sun 2023-01-01 00:00:00 PST 2 
days ago btrfs-scrub.timer   btrfs-scrub.service

1 timers listed.
Pass --all to see loaded but inactive timers, too.

when i updated the generated 
/etc/systemd/system/btrfs-scrub.timer.d/schedule.conf
file to empty the existing OnCalendar value:
[Timer]
OnCalendar=
OnCalendar=quarterly

and reran `sudo systemctl restart btrfsmaintenance-refresh.service`
it was successfully updated:
NEXTLEFT  LAST
PASSED UNIT  ACTIVATES
Sat 2023-04-01 00:00:00 PDT 2 months 26 days left Sun 2023-01-01 00:00:00 PST 2 
days ago btrfs-scrub.timer btrfs-scrub.service

1 timers listed.
Pass --all to see loaded but inactive timers, too.

i have included a brief patch to address this.

thanks in advance.

andy

-- System Information:
Debian Release: 11.6
  APT prefers stable-updates
  APT policy: (990, 'stable-updates'), (990, 'stable-security'), (990, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 5.10.0-20-amd64 (SMP w/6 CPU threads)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages btrfsmaintenance depends on:
ii  btrfs-progs  5.10.1-2
ii  cron 3.0pl1-137
ii  systemd  247.3-7+deb11u1

btrfsmaintenance recommends no packages.

btrfsmaintenance suggests no packages.

-- Configuration Files:
/etc/default/btrfsmaintenance changed:
BTRFS_LOG_OUTPUT="stdout"
BTRFS_DEFRAG_PATHS=""
BTRFS_DEFRAG_PERIOD="none"
BTRFS_DEFRAG_MIN_SIZE="+1M"
BTRFS_BALANCE_MOUNTPOINTS="auto"
BTRFS_BALANCE_PERIOD="monthly"
BTRFS_BALANCE_DUSAGE="5 10"
BTRFS_BALANCE_MUSAGE="5"
BTRFS_SCRUB_MOUNTPOINTS="auto"
BTRFS_SCRUB_PERIOD="quarterly"
BTRFS_SCRUB_PRIORITY="idle"
BTRFS_SCRUB_READ_ONLY="false"
BTRFS_TRIM_PERIOD="none"
BTRFS_TRIM_MOUNTPOINTS="/"
BTRFS_ALLOW_CONCURRENCY="false"


-- no debconf information
--- 
/var/tmp/user/1000/andrew@gondolin:_usr_share_btrfsmaintenance_btrfsmaintenance-refresh-cron.sh.2023-01-03T14:32:38-0800.3233449
2020-10-02 18:47:48.0 -0700
+++ /usr/share/btrfsmaintenance/btrfsmaintenance-refresh-cron.sh
2023-01-03 14:32:49.533881598 -0800
@@ -74,6 +74,7 @@
mkdir -p /etc/systemd/system/"$SERVICE".timer.d/
cat << EOF > 
/etc/systemd/system/"$SERVICE".timer.d/schedule.conf
 [Timer]
+OnCalendar=
 OnCalendar=$PERIOD
 EOF
systemctl enable "$SERVICE".timer &> /dev/null

Bug#930953: Intent to NMU byobu to fix longstanding l10n bugs

[Dustin Kirkland]

Hi there!

Frankly, I'm delighted for the help!   Life and work and a bunch of other
things have consumed my time and I'm grateful for the NMU!

Cheers,
Dustin


On Tue, Jan 3, 2023 at 1:56 PM Helge Kreutzmann 
wrote:

> Hello Dustion,
> I intend to NMU byobu end of next week to fix longstanding l10n
> bugs[1]. The changelog would be something like the following:
>
>  byobu (5.133-1.1) UNRELEASED; urgency=medium
>  .
>* Non-maintainer upload.
>* Add/Update debconf template translation
>  - Add French translation.
>Thanks to Grégoire Scano (Closes: #930953)
>  - Update Russion translation.
>Thanks Lev Lamberov (Closes: #942636)
>  - Add Dutch translation.
>Thanks Frans Spiesschaert (Closes: #945360)
>  - Add Brazilian Portuguese translation.
>Thanks Adriano Rafael Gomes (Closes: #972450)
>
> Please tell me if you are currently preparing a new release yourself
> and would like me to skip the NMU.
>
> Greetings
>
>  Helge
>
> [1] https://i18n.debian.org/nmu-radar/nmu_bypackage.html
>
> --
>   Dr. Helge Kreutzmann deb...@helgefjell.de
>Dipl.-Phys.
> http://www.helgefjell.de/debian.php
> 64bit GNU powered gpg signed mail preferred
>Help keep free software "libre": http://www.ffii.de/
>

Bug#1027845: kdevelop-python: Plugin crashes on encountering Python code

[Jan Kriho]

Package: kdevelop-python
X-Debbugs-Cc: erbur...@gmail.com
Version: 22.12.0-2
Severity: important

Dear Maintainer,

after the Python 3.11 transition, the Python plugin for KDevelop crashes on
on my setup after loading a Python code. I have filed an upstream
bugreport https://bugs.kde.org/show_bug.cgi?id=463802 which contains the
full backtrace.

Regards,
Jan Kriho


-- System Information:
Debian Release: bookworm/sid
 APT prefers testing
 APT policy: (950, 'testing'), (900, 'unstable'), (850,
'experimental'), (800, 'stable'), (500, 'testing-debug'), (500,
'stable-security')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

Versions of packages kdevelop-python depends on:
ii  kdevelop-python-data  22.12.0-2
ii  kdevelop510-libs  4:22.12.0-2
ii  libc6 2.36-7
ii  libkf5configcore5 5.101.0-1
ii  libkf5coreaddons5 5.101.0-1
ii  libkf5i18n5   5.101.0-1+b1
ii  libkf5parts5  5.101.0-1
ii  libkf5texteditor5 5.101.0-2
ii  libkf5threadweaver5   5.101.0-1
ii  libkf5widgetsaddons5  5.101.0-1
ii  libkf5xmlgui5 5.101.0-1+b1
ii  libpython3.11 3.11.1-2
ii  libqt5core5a  5.15.7+dfsg-2
ii  libqt5gui55.15.7+dfsg-2
ii  libqt5widgets55.15.7+dfsg-2
ii  libstdc++612.2.0-13
ii  python3.113.11.1-2

Versions of packages kdevelop-python recommends:
ii  kdevelop  4:22.12.0-2
ii  pycodestyle   2.10.0-1
ii  python3-autopep8  2.0.0-1

Versions of packages kdevelop-python suggests:
pn  kdevelop-python-l10n  

-- no debconf information

Bug#1027844: btrfsmaintenance: noted BTRFS_BALANCE_PERIOD default in /etc/default/btrfsmaintenance is inconsistent w/systemd timer

[andrew bezella]

Package: btrfsmaintenance
Version: 0.5-1
Severity: minor

Dear Maintainer,

as distributed, /etc/default/btrfsmaintenance has the following information:
## Path:   System/File systems/btrfs
## Type:   string(none,daily,weekly,monthly)
## Default:"weekly"
## ServiceRestart: btrfsmaintenance-refresh
#
# Frequency of periodic balance.
#
# The frequency may be specified using one of the listed values or
# in the format documented in the "Calendar Events" section of systemd.time(7),
# if available.
BTRFS_BALANCE_PERIOD="weekly"

however /lib/systemd/system/btrfs-balance.timer has:
[Timer]
OnCalendar=monthly

it would seem that either the value/note in /etc/default/btrfsmaintenance
or the OnCalendar value in btrfs-balance.timer should be updated to match
the other.

thanks in advance.

andy

-- System Information:
Debian Release: 11.6
  APT prefers stable-updates
  APT policy: (990, 'stable-updates'), (990, 'stable-security'), (990, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 5.10.0-20-amd64 (SMP w/6 CPU threads)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages btrfsmaintenance depends on:
ii  btrfs-progs  5.10.1-2
ii  cron 3.0pl1-137
ii  systemd  247.3-7+deb11u1

btrfsmaintenance recommends no packages.

btrfsmaintenance suggests no packages.

-- Configuration Files:
/etc/default/btrfsmaintenance changed:
BTRFS_LOG_OUTPUT="stdout"
BTRFS_DEFRAG_PATHS=""
BTRFS_DEFRAG_PERIOD="none"
BTRFS_DEFRAG_MIN_SIZE="+1M"
BTRFS_BALANCE_MOUNTPOINTS="auto"
BTRFS_BALANCE_PERIOD="monthly"
BTRFS_BALANCE_DUSAGE="5 10"
BTRFS_BALANCE_MUSAGE="5"
BTRFS_SCRUB_MOUNTPOINTS="auto"
BTRFS_SCRUB_PERIOD="quarterly"
BTRFS_SCRUB_PRIORITY="idle"
BTRFS_SCRUB_READ_ONLY="false"
BTRFS_TRIM_PERIOD="none"
BTRFS_TRIM_MOUNTPOINTS="/"
BTRFS_ALLOW_CONCURRENCY="false"


-- no debconf information

Bug#1026934: Package colortbl does not work with dinbrief anymore

[Hilmar Preuße]

Control: tags -1 + wontfix

Am 24.12.2022 um 10:27 teilte Joey Schulze mit:

Hi,


I have found an incompatibility between the package colortbl and the
dinbrief documentclass.

The problem sneaked into bullseye and did not exist in buster.  It
seems to be still present in bookwork unfortunately (for verification
i copied both colortbl.sty and dinbrief.cls into the directory
containing the sample LaTeX file).

Please see this minimal LaTeX files to reproduce the problem


As you probably are able to speak German I refer this thread from dctt
[1]. The issue is probably in dinbrief, but I have little hope that
we'll get a fix for this. Tagging.

Hilmar

[1]
https://de.comp.text.tex.narkive.com/pPx7YIaB/problem-mit-xcolor-bzw-pdftex-def-und-dinbrief
--
--
sigfault

Bug#1026539: theano FTBFS

[Rebecca N. Palmer]

Please do *not* upload theano 1.12 to unstable - it's the Aesara 
version, which may seriously break backward compatibility.


I haven't had time to properly look at this bug yet.

Bug#1027843: libgnatcoll-bindings FTBFS with Python 3.11 as default version

[Adrian Bunk]

Source: libgnatcoll-bindings
Version: 23.0.0-3
Severity: serious

https://buildd.debian.org/status/fetch.php?pkg=libgnatcoll-bindings=ppc64el=23.0.0-3%2Bb1=1672725764=0

...
/<>/python3/python_support.c: In function ‘ada_pyframe_get_code’:
/<>/python3/python_support.c:817:14: error: invalid use of 
incomplete typedef ‘PyFrameObject’ {aka ‘struct _frame’}
  817 |return obj->f_code;
  |  ^~
/<>/python3/python_support.c: In function ‘ada_pyframe_get_back’:
/<>/python3/python_support.c:823:14: error: invalid use of 
incomplete typedef ‘PyFrameObject’ {aka ‘struct _frame’}
  823 |return obj->f_back;
  |  ^~

   compilation of python_support.c failed

gprbuild: *** compilation phase failed

Bug#1027702: plocate: "Try `ulimit -n 262144' or similar (current limit is 0)."

[Steinar H. Gunderson]

tags 1027702 + pending
thanks

On Mon, Jan 02, 2023 at 10:13:59AM +0100, Jakub Wilk wrote:
> I saw this in an error message sent by cron:
> 
> Hint: Try `ulimit -n 262144' or similar (current limit is 0).
> 
> The number in parentheses in wrong of course.

Fixed in upstream git, so this will be fixed whenever 1.1.18 is released.
Thanks!

/* Steinar */
-- 
Homepage: https://www.sesse.net/

Bug#1016963: Please test u-boot for rpi_4 rpi_4_32b

[Andreas Henriksson]

On Tue, Jan 03, 2023 at 11:46:31PM +0100, Andreas Henriksson wrote:
> On Wed, Dec 28, 2022 at 04:11:04PM -0800, Vagrant Cascadian wrote:
> > rpi_4
> > rpi_4_32b
> 
> I dug up my old dusty rpi4 which I probably haven't touched
> since last time we spoke about u-boot on it.
> 
> 
> I've tested only the 64bit (arm64) version so far.
[...]
> I upgraded only u-boot.bin from bookworm/sid/experimental
[...]
> The unstable and experimental versions both caused a reset
> after run bootcmd and before "Starting Linux...".
[...]


After upgrading rpi firmware files to latest release/tag
also the unstable and experimental u-boot seemed to boot
fine (no reset, garbage on console after linux started).


### unstable u-boot with rpi firmware-1.20221104.tar.gz

U-Boot 2022.10+dfsg-2 (Dec 23 2022 - 23:18:44 +)

DRAM:  3.9 GiB
RPI 4 Model B (0xc03111)
Core:  209 devices, 16 uclasses, devicetree: board
MMC:   mmcnr@7e30: 1, mmc@7e34: 0
Loading Environment from FAT... Unable to read "uboot.env" from mmc0:1... 
In:serial
Out:   serial
Err:   serial
Net:   eth0: ethernet@7d58
PCIe BRCM: link up, 5.0 Gbps x1 (SSC)
starting USB...
Bus xhci_pci: Register 5000420 NbrPorts 5
Starting the controller
USB XHCI 1.00
scanning bus xhci_pci for devices... 2 USB Device(s) found
   scanning usb for storage devices... 0 Storage Device(s) found
Hit any key to stop autoboot:  0 
U-Boot> 
U-Boot> 
U-Boot> 
U-Boot> 
U-Boot> 
U-Boot> 
U-Boot> 
U-Boot> run bootcmd
switch to partitions #0, OK
mmc0 is current device
Scanning mmc 0:2...
Found /boot/extlinux/extlinux.conf
Retrieving file: /boot/extlinux/extlinux.conf
U-Boot menu
1:  Debian GNU/Linux 5.7.0-1-arm64
2:  Debian GNU/Linux 5.7.0-1-arm64 (rescue target)
Enter choice: 1:Debian GNU/Linux 5.7.0-1-arm64
Retrieving file: /boot/initrd.img-5.7.0-1-arm64   
Retrieving file: /boot/vmlinuz-5.7.0-1-arm64
append: root=LABEL=root ro rootwait console=ttyS1,115200
Retrieving file: /usr/lib/linux-image-5.7.0-1-arm64/broadcom/bcm2711-rpi-4-b.dtb
## Flattened Device Tree blob at 0260
   Booting using the fdt blob at 0x260
   Using Device Tree in place at 0260, end 0260896e

Starting kernel ...

[... garbage characters...]


### experimental u-boot with rpi firmware-1.20221104.tar.gz

U-Boot 2023.01-rc4+dfsg-1 (Dec 24 2022 - 03:13:23 +)

DRAM:  948 MiB (effective 3.9 GiB)
RPI 4 Model B (0xc03111)
Core:  209 devices, 16 uclasses, devicetree: board
MMC:   mmcnr@7e30: 1, mmc@7e34: 0
Loading Environment from FAT... Unable to read "uboot.env" from mmc0:1...
In:serial  
Out:   serial  
Err:   serial  
Net:   eth0: ethernet@7d58
PCIe BRCM: link up, 5.0 Gbps x1 (SSC)
starting USB...
Bus xhci_pci: Register 5000420 NbrPorts 5
Starting the controller
USB XHCI 1.00  
scanning bus xhci_pci for devices... 2 USB Device(s) found
   scanning usb for storage devices... 0 Storage Device(s) found
Hit any key to stop autoboot:  0
U-Boot>
U-Boot>
U-Boot>
U-Boot> run bootcmd
switch to partitions #0, OK
mmc0 is current device
Scanning mmc 0:2...
Found /boot/extlinux/extlinux.conf
Retrieving file: /boot/extlinux/extlinux.conf
U-Boot menu
1:  Debian GNU/Linux 5.7.0-1-arm64
2:  Debian GNU/Linux 5.7.0-1-arm64 (rescue target)
Enter choice: 1:Debian GNU/Linux 5.7.0-1-arm64
Retrieving file: /boot/initrd.img-5.7.0-1-arm64
Retrieving file: /boot/vmlinuz-5.7.0-1-arm64
append: root=LABEL=root ro rootwait console=ttyS1,115200
Retrieving file: 
/usr/lib/linux-image-5.7.0-1-arm64/broadcom/bcm2711-rpi-4-b.dtb  
## Flattened Device Tree blob at 0260
   Booting using the fdt blob at 0x260
Working FDT set to 260
   Using Device Tree in place at 0260, end 0260896e
Working FDT set to 260

Starting kernel ...

[...garbage characters...]


Regards,
Andreas Henriksson

Bug#986152: Offer of help

[Jeremy Sowden]

On 2023-01-03, at 22:06:03 +, Jeremy Sowden wrote:
> On 2023-01-02, at 18:08:57 +0100, Romain Francoise wrote:
> > [Cc'ing Roberto directly to make sure he's aware of this
> > discussion.]
> > 
> > I'm also a Shorewall[6] user and while the state of the package
> > isn't really alarming right now, I need it to be properly maintained
> > going forward.
> > 
> > We could set up a pkg-shorewall team on Salsa and co-maintain the
> > packages there. Jeremy, would that work for you?
> 
> Absolutely.

I've imported my fork of Roberto's SF repo to Salsa:

  https://salsa.debian.org/azazel/shorewall

I haven't touched it in 18 months, so I'll give it a polish when I have
some time, and perhaps we can use it as a starting point.

J.



signature.asc
Description: PGP signature

Bug#1027842: displaycal-py3 FTBFS with Python 3.11 as default version

[Adrian Bunk]

Source: displaycal-py3
Version: 3.9.10-1
Severity: serious
Forwarded: https://github.com/eoyilmaz/displaycal-py3/issues/218

https://buildd.debian.org/status/fetch.php?pkg=displaycal-py3=ppc64el=3.9.10-1%2Bb1=1672726079=0

...
dh clean -Spybuild --with quilt
   dh_auto_clean -O-Spybuild
I: pybuild base:240: python3.11 setup.py clean 
/<>/setup.py:13: DeprecationWarning: The distutils package is 
deprecated and slated for removal in Python 3.12. Use setuptools or check PEP 
632 for potential alternatives
  from distutils.util import get_platform
['clean']
Traceback (most recent call last):
  File "/<>/DisplayCAL/defaultpaths.py", line 234, in 
set_translation
obj.translation = gettext.translation(
  
TypeError: translation() got an unexpected keyword argument 'codeset'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/<>/setup.py", line 1583, in 
setup()
  File "/<>/setup.py", line 991, in setup
from DisplayCAL.setup import setup
  File "/<>/DisplayCAL/setup.py", line 70, in 
from DisplayCAL.defaultpaths import autostart, autostart_home
  File "/<>/DisplayCAL/defaultpaths.py", line 399, in 
if isinstance(attr, (str, list)):
   ^
  File "/<>/DisplayCAL/defaultpaths.py", line 303, in 
__getattribute__
object.__getattribute__(self, "init")()
  File "/<>/DisplayCAL/defaultpaths.py", line 380, in init
XDG.set_translation(self)
  File "/<>/DisplayCAL/defaultpaths.py", line 238, in 
set_translation
obj.translation = gettext.translation(
  
  File "/usr/lib/python3.11/gettext.py", line 531, in translation
raise FileNotFoundError(ENOENT,
FileNotFoundError: [Errno 2] No translation file found for domain: 
'xdg-user-dirs'
E: pybuild pybuild:388: clean: plugin distutils failed with: exit code=1: 
python3.11 setup.py clean 
dh_auto_clean: error: pybuild --clean -i python{version} -p 3.11 returned exit 
code 13
make: *** [debian/rules:4: clean] Error 25

Bug#986583: btrfs-progs: "Received UUID" not cleared on "btrfs set property ... ro false"

[Leszek Dubiel]

I can't test new versions, because I work only on Debian Stable.

Here is similar case:

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



W dniu 3.01.2023 o 22:59, Nicholas D Steeves pisze:

Dear Leszek,

I agree that it seems inconsistent that "Received UUID" is not cleared,
and I'm surprised no one replied to your bug!

Leszek Dubiel  writes:


Package: btrfs-progs
Version: 4.20.1-2
Severity: minor



When one imports subvolume through   btrfs send ... | btrfs receive ...
then snapshot gets "Received UUID" from remote system.

When you   "btrfs sub snap -r ...", create readonly snapshot of received
snapshot, then "Received UUID" is copied.

When you   "btrfs sub snap ...", create read-write snapshot, then
"Received UUID" of new snapshot is cleared. That is GOOD.

But if you "btrfs set prop ... ro false" then "Received UUID" is not
cleared. I think this should be cleared -- in the same style when
you snapshot without "readonly" flag.

Testing script:


[snip]

Thank you for steps to reproduce as well as the script!

Do you know if this bug is still present in newer releases?  If it's
still present with either linux and btrfs-progs 6.x then this issue should
immediately be forwarded upstream.  If I remember correctly 5.10.x is
also still supported, and if it's fixed in 6.x but not in 5.10.x then
the fix might need to be backported--to my eyes the regression risk is
low.

Regards,
Nicholas

Bug#1016963: Please test u-boot for rpi_4 rpi_4_32b

[Andreas Henriksson]

On Wed, Dec 28, 2022 at 04:11:04PM -0800, Vagrant Cascadian wrote:
> rpi_4
> rpi_4_32b

I dug up my old dusty rpi4 which I probably haven't touched
since last time we spoke about u-boot on it.


I've tested only the 64bit (arm64) version so far.

The version that was on the sd-card since last time:
U-Boot> ver
U-Boot 2020.07+dfsg-1 (Jul 08 2020 - 23:29:02 +)

gcc (Debian 9.3.0-14) 9.3.0
GNU ld (GNU Binutils for Debian) 2.34.90.20200706
U-Boot> 


I upgraded only u-boot.bin from bookworm/sid/experimental
on the firmware partition (nothing else touched, and I'm not
really sure what state it was in since last time but probably
a bootable system atleast).

Testing/bookworm u-boot.bin seems to boot fine (although
serial console became garbage after Linux started, but
it seemed to run but I didn't investigate much).

The unstable and experimental versions both caused a reset
after run bootcmd and before "Starting Linux...".
U-Boot itself seemed to run fine though, it was running bootcmd
that caused the reset. Maybe I need to upgrade the rpi firmware,
or maybe it's related to what else is on the old sd-card that
was in the box.


# testing u-boot

U-Boot> ver
U-Boot 2022.04+dfsg-2+b1 (May 14 2022 - 19:14:13 +)

gcc (Debian 11.3.0-1) 11.3.0
GNU ld (GNU Binutils for Debian) 2.38
U-Boot> 

# unstable u-boot

U-Boot> ver
U-Boot 2022.10+dfsg-2 (Dec 23 2022 - 23:18:44 +)

gcc (Debian 12.2.0-10) 12.2.0
GNU ld (GNU Binutils for Debian) 2.39.50.20221208
U-Boot> 




U-Boot 2022.10+dfsg-2 (Dec 23 2022 - 23:18:44 +)

DRAM:  3.9 GiB
RPI 4 Model B (0xc03111)
Core:  135 devices, 14 uclasses, devicetree: board
MMC:   mmcnr@7e30: 1, emmc2@7e34: 0
Loading Environment from FAT... Unable to read "uboot.env" from
mmc0:1...
In:serial
Out:   serial
Err:   serial
Net:   eth0: genet@7d58
PCIe BRCM: link up, 5.0 Gbps x1 (!SSC)
starting USB...
Bus xhci_pci: Register 5000420 NbrPorts 5
Starting the controller
Port not available.
Hit any key to stop autoboot:  0
"Synchronous Abort" handler, esr 0x9644
elr: 0009f3a8 lr : 0009572c (reloc)
elr: 3b36c3a8 lr : 3b36272c
x0 : 3af52610 x1 : 3af52680
x2 : 0051 x3 : 6964003b6963765f
x4 : 3b3d0890 x5 : 3b3d0890
x6 : 005b x7 : 3b3d0e30
x8 : 3b3d0820 x9 : 0008
x10: fff0 x11: 0006
x12: 0001869f x13: 3af3e708
x14: 3af3e810 x15: 
x16: 3b36d548 x17: 596fcb0297bbddff
x18: 3af48d70 x19: 0071
x20: 3b3d0880 x21: 
x22: 0005 x23: 000a
x24: 0001 x25: 3b3e4cd8
x26:  x27: 3b3c4851
x28: 006d x29: 3af3d9e0

Code: a9410803 8b130001 b2400273 f9000413 (f9000c62)
Resetting CPU ...

resetting ...










# experimental u-boot


U-Boot> ver
U-Boot 2023.01-rc4+dfsg-1 (Dec 24 2022 - 03:13:23 +)

gcc (Debian 12.2.0-10) 12.2.0
GNU ld (GNU Binutils for Debian) 2.39.50.20221208
U-Boot> 

U-Boot> run bootcmd
"Synchronous Abort" handler, esr 0x9644
elr: 0009f7e0 lr : 00095e0c (reloc)
elr: 3b36c7e0 lr : 3b362e0c
x0 : 3af59470 x1 : 3af59490
x2 : 30636d6d x3 : 5f646d63746f6f00
x4 : 0070 x5 : 3b3d0e08
x6 : 005b x7 : 3b3d13a8
x8 : 0050 x9 : 0008
x10: fff0 x11: 0006
x12: 0001869f x13: 3af3e708
x14: 3af3e810 x15: 
x16: 3b36d994 x17: d9ff4b22fffbdcff
x18: 3af48d70 x19: 0021
x20: 3b3d0df8 x21: 3af59d80
x22: 3af59b20 x23: 0010
x24: 0008 x25: 3b3e5258
x26: 0002 x27: 3b3c4e54
x28: 0073 x29: 3af3da10

Code: a9410803 8b130001 b2400273 f9000413 (f9000c62) 
Resetting CPU ...

resetting ...


U-Boot 2023.01-rc4+dfsg-1 (Dec 24 2022 - 03:13:23 +)
[...]

Bug#1027841: desktop-base: Please provide UHD images for Debian 12 (emerald theme)

[Matthew Gabeler-Lee]

Package: desktop-base
Version: 12.0.2
Severity: wishlist

Updating some systems to Bookworm to try things out, I noticed the new
desktop theme is blurry on many systems compared to Bullseye, becaues the
Bullseye default "Homeworld" theme came with images (esp. SVGs) targeting
several resolutions above 1080p-ish, while Emerald tops out at
1920x1080/1200.

It feels especially sad to have _vector_ images do blurry pixel-oriented
upscaling -- GNOME at least seems to render the SVG at its target resolution
and then do a raster scaling to the screen resolution. That's not this
package's fault, but it can certainly provide copies of the SVGs that target
the higher res with very minimal editing.

For example, this tiny edit is enough to make the 1920x1080 render crisply
at 3840x2160, when combined with corresponding changes to the metadata
file(s):

--- 
/usr/share/desktop-base/emerald-theme/wallpaper/contents/images/1920x1080.svg   
2022-12-23 12:31:20.0 -0500
+++ 
/usr/share/desktop-base/emerald-theme/wallpaper/contents/images/3840x2160.svg   
2023-01-03 17:18:55.791977381 -0500
@@ -1,6 +1,7 @@
 
 
 http://www.w3.org/2000/svg; 
xmlns:xlink="http://www.w3.org/1999/xlink; x="0px" y="0px"
+   scale-x="0.5" width="3840" height="2160"
 viewBox="0 0 1920 1080" style="enable-background:new 0 0 1920 1080;" 
xml:space="preserve">
 

Bug#1027840: gcc-11: FTBFS on hurd-i386

[Svante Signell]

Source: gcc-11
Version: 11.3.0-10
Severity: important
Tags: patch
User: debian-h...@lists.debian.org
Usertags: hurd
Affects: gcc-11, gcc-snapshot
X-Debbugs-CC: debian-h...@lists.debian.org

Hi,

gcc-11-11.3.0-10 in sid FTBFS on hurd-i386 due to failing linkage of
pthread_once (same error already fixed in gcc-12 and gcc-13):
/<>/build/i686-gnu/libstdc++-v3/include/i686-gnu/bits/gthr-
default.h:700: undefined reference to `pthread_once'
and more.

The patch at hand is: libstdc++-hurd.diff, attached here for convenience.

Thanks!

This is notably needed because in glibc 2.34, the move of pthread functions
into libc.so happened for Linux only, not GNU/Hurd.

The pthread_self() function can also always be used fine as it is on
GNU/Hurd.

libstdc++-v3/ChangeLog:

* config/os/gnu-linux/os_defines.h [!__linux__]
  (_GLIBCXX_NATIVE_THREAD_ID, _GLIBCXX_GTHREAD_USE_WEAK): Do not define.

--- a/libstdc++-v3/config/os/gnu-linux/os_defines.h
+++ b/libstdc++-v3/config/os/gnu-linux/os_defines.h
@@ -49,22 +49,24 @@
 // version dynamically in case it has changed since libstdc++ was configured.
 #define _GLIBCXX_NO_OBSOLETE_ISINF_ISNAN_DYNAMIC __GLIBC_PREREQ(2,23)
 
-#if __GLIBC_PREREQ(2, 27)
-// Since glibc 2.27 pthread_self() is usable without linking to libpthread.
-# define _GLIBCXX_NATIVE_THREAD_ID pthread_self()
-#else
+#ifdef __linux__
+# if __GLIBC_PREREQ(2, 27)
+// Since glibc 2.27 Linux' pthread_self() is usable without linking to libpthread.
+#  define _GLIBCXX_NATIVE_THREAD_ID pthread_self()
+# else
 // Before then it was in libc.so.6 but not libc.a, and always returns 0,
 // which breaks the invariant this_thread::get_id() != thread::id{}.
 // So only use it if we know the libpthread version is available.
 // Otherwise use (__gthread_t)1 as the ID of the main (and only) thread.
-# define _GLIBCXX_NATIVE_THREAD_ID \
-  (__gthread_active_p() ? __gthread_self() : (__gthread_t)1)
-#endif
+#  define _GLIBCXX_NATIVE_THREAD_ID \
+   (__gthread_active_p() ? __gthread_self() : (__gthread_t)1)
+# endif
 
-#if __GLIBC_PREREQ(2, 34)
-// Since glibc 2.34 all pthreads functions are usable without linking to
+# if __GLIBC_PREREQ(2, 34)
+// Since glibc 2.34 all Linux pthreads functions are usable without linking to
 // libpthread.
-# define _GLIBCXX_GTHREAD_USE_WEAK 0
+#  define _GLIBCXX_GTHREAD_USE_WEAK 0
+# endif
 #endif
 
 #endif

Bug#1027839: createrepo-c FTBFS with Python 3.11 as default version

[Adrian Bunk]

Source: createrepo-c
Version: 0.17.3-1
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/fetch.php?pkg=createrepo-c=ppc64el=0.17.3-1%2Bb1=1672726045=0

...
-- Found PythonInterp: /usr/bin/python3 (found suitable version "3.11.1", 
minimum required is "3") 
-- Found PythonLibs: /usr/lib/powerpc64le-linux-gnu/libpython3.11.so (found 
suitable version "3.11.1", minimum required is "3") 
-- Python install dir is /usr/lib/python3/dist-packages
:1: DeprecationWarning: path is deprecated. Use files() instead. Refer 
to 
https://importlib-resources.readthedocs.io/en/latest/using.html#migrating-from-legacy
 for migration advice.
Traceback (most recent call last):
  File "", line 1, in 
TypeError: unsupported operand type(s) for /: '_GeneratorContextManager' and 
'str'
-- Python skbuild CMake dir is 
CMake Error at src/python/CMakeLists.txt:65 (find_package):
  By not providing "FindPythonExtensions.cmake" in CMAKE_MODULE_PATH this
  project has asked CMake to find a package configuration file provided by
  "PythonExtensions", but CMake did not find one.

  Could not find a package configuration file provided by "PythonExtensions"
  with any of the following names:

PythonExtensionsConfig.cmake
pythonextensions-config.cmake

  Add the installation prefix of "PythonExtensions" to CMAKE_PREFIX_PATH or
  set "PythonExtensions_DIR" to a directory containing one of the above
  files.  If "PythonExtensions" provides a separate development package or
  SDK, be sure it has been installed.


-- Configuring incomplete, errors occurred!




The problem seems to come from debian/patches/python-skbuild-path.patch

Bug#1027838: installation-reports: Odroid C2 install mostly successful

[Vagrant Cascadian]

Package: installation-reports
Severity: normal
X-Debbugs-Cc: vagr...@debian.org

Boot method: microSD/USB
Image version: 
https://d-i.debian.org/daily-images/arm64/20230103-02:24/netboot/mini.iso
Date: 2022-01-03 ~21:00 UTC

Machine: Hardkernel Odroid C2
Partitions: 
FilesystemType 1K-blocksUsed Available Use% Mounted 
on
udev  devtmpfs826416   0826416   0% /dev
tmpfs tmpfs   197476 552196924   1% /run
/dev/mapper/odc2a-odc2x--root ext4   5676852 1530324   3837280  29% /
tmpfs tmpfs   987360   0987360   0% /dev/shm
tmpfs tmpfs 5120   0  5120   0% 
/run/lock
/dev/mmcblk1p4vfat487160   41952445208   9% 
/boot/efi
tmpfs tmpfs   197472   0197472   0% 
/run/user/1000

Base System Installation Checklist:
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it

Initial boot:   [O]
Detect network card:[O]
Configure network:  [O]
Detect media:   [ ]
Load installer modules: [O]
Clock/timezone setup:   [O]
User/password setup:[O]
Detect hard drives: [O]
Partition hard drives:  [O]
Install base system:[O]
Install tasks:  [O]
Install boot loader:[E]
Overall install:[O]

Comments/Problems:

Using u-boot-amlogic 2023.01~rc4+dfsg-1 on microSD as the EFI
implementation, I loaded the mini.iso onto a USB stick and booted
debian-installer from that.

Failed installing grub, as the u-boot EFI implementation did not have
a place to save variables. Worked around by selecting "continue
without a bootloader" and manually running:

  chroot grub-install --force /dev/mmcblk1
  chroot update-grub

Grub did not display on the serial console at first boot, fixed by
adding "GRUB_TERMINAL=serial" to /etc/default/grub.d/serial.cfg and
re-running update-grub.

Ethernet worked from debian-installer just fine, but not reliably from
the booted system. Copied the /dtb/ directory from the EFI partition
on the debian-installer media to /boot/efi/dtb/ (which matches the
installed kernel), and then ethernet worked on the next boot. Could
have also copied the dtb files from /usr/lib/linux-image-VERSION too,
probably.

Would also be possible to install using SD card images once
https://bugs.debian.org/1027176 is fixed or worked around.


live well,
  vagrant

-- Package-specific info:

==
Installer lsb-release:
==
DISTRIB_ID=Debian
DISTRIB_DESCRIPTION="Debian GNU/Linux installer"
DISTRIB_RELEASE="12 (bookworm) - installer build 20230103-02:04:48"
X_INSTALLATION_MEDIUM=netboot

==
Installer hardware-summary:
==
uname -a: Linux odc2x 6.0.0-6-arm64 #1 SMP Debian 6.0.12-1 (2022-12-09) aarch64 
GNU/Linux
usb-list: 
usb-list: Bus 01 Device 01: DWC OTG Controller [1d6b:0002]
usb-list:Level 00 Parent 00 Port 00  Class 09(hub  ) Subclass 00 Protocol 01
usb-list:Manufacturer: Linux 6.0.0-6-arm64 dwc2_hsotg
usb-list:Interface 00: Class 09(hub  ) Subclass 00 Protocol 00 Driver hub
usb-list: 
usb-list: Bus 01 Device 02: USB2.0 Hub [05e3:0610]
usb-list:Level 01 Parent 01 Port 00  Class 09(hub  ) Subclass 00 Protocol 02
usb-list:Interface 00: Class 09(hub  ) Subclass 00 Protocol 02 Driver hub
lsmod: Module  Size  Used by
lsmod: fuse  135168  0
lsmod: nls_ascii  16384  1
lsmod: nls_cp437  20480  1
lsmod: efivarfs   20480  1
lsmod: dm_mod143360  14
lsmod: dax32768  1 dm_mod
lsmod: md_mod167936  0
lsmod: xfs  1392640  0
lsmod: jfs   196608  0
lsmod: btrfs1486848  0
lsmod: xor20480  1 btrfs
lsmod: xor_neon   20480  1 xor
lsmod: raid6_pq  106496  1 btrfs
lsmod: zstd_compress 258048  1 btrfs
lsmod: libcrc32c  16384  2 btrfs,xfs
lsmod: vfat   28672  1
lsmod: fat81920  1 vfat
lsmod: ext4  778240  1
lsmod: crc16  16384  1 ext4
lsmod: mbcache24576  1 ext4
lsmod: jbd2  143360  1 ext4
lsmod: crc32c_generic 16384  3
lsmod: sd_mod 57344  0
lsmod: t10_pi 16384  1 sd_mod
lsmod: crc64_rocksoft 20480  1 t10_pi
lsmod: crc64  20480  1 crc64_rocksoft
lsmod: crc_t10dif 20480  1 t10_pi
lsmod: crct10dif_common   16384  1 crc_t10dif
lsmod: uas28672  0
lsmod: usb_storage73728  1 uas
lsmod: scsi_mod  229376  3 sd_mod,usb_storage,uas
lsmod: scsi_common16384  3 scsi_mod,usb_storage,uas
lsmo

Bug#986152: Offer of help

[Jeremy Sowden]

On 2023-01-02, at 18:08:57 +0100, Romain Francoise wrote:
> [Cc'ing Roberto directly to make sure he's aware of this discussion.]
> 
> I'm also a Shorewall[6] user and while the state of the package isn't
> really alarming right now, I need it to be properly maintained going
> forward.
> 
> We could set up a pkg-shorewall team on Salsa and co-maintain the
> packages there. Jeremy, would that work for you?

Absolutely.

J.


signature.asc
Description: PGP signature

Bug#1027837: offlineimap3: "AssertionError: Your sqlite is not multithreading safe" with python3.11

[Simon McVittie]

Package: offlineimap3
Version: 0.0~git20211018.e64c254+dfsg-1
Severity: grave
Tags: fixed-upstream patch
Justification: renders package unusable
Forwarded: https://github.com/OfflineIMAP/offlineimap3/issues/136
Control: block 1026825 by -1

After upgrading to python3 (>= 3.11) I get lots of these errors:

> ERROR: ERROR in syncfolder for REDACTED folder .REDACTED: Traceback (most 
> recent call last):
>   File "/usr/share/offlineimap3/offlineimap/accounts.py", line 610, in 
> syncfolder
> statusfolder.openfiles()
>   File "/usr/share/offlineimap3/offlineimap/folder/LocalStatusSQLite.py", 
> line 107, in openfiles
> assert sqlite.threadsafety == 1, 'Your sqlite is not multithreading safe.'
>
> AssertionError: Your sqlite is not multithreading safe

and as far as I can tell, no mail is synchronized.
https://github.com/OfflineIMAP/offlineimap3/pull/139 appears to be the
upstream solution for this, and seems to be a suitable patch for the
version currently in Debian. Please see attached or the upstream PR.

smcv

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

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

Versions of packages offlineimap3 depends on:
ii  ca-certificates   20211016
ii  python3   3.11.1-1
ii  python3-distro1.8.0-1
ii  python3-imaplib2  2.57-5.2

offlineimap3 recommends no packages.

Versions of packages offlineimap3 suggests:
pn  python3-gssapi  

-- no debconf information

-- debsums errors found:
debsums: changed file 
/usr/share/offlineimap3/offlineimap/folder/LocalStatusSQLite.py (from 
offlineimap3 package)
>From 7cd32cf834b34a3d4675b29bebcd32dc1e5ef128 Mon Sep 17 00:00:00 2001
From: 0pointerexception 
Date: Thu, 17 Nov 2022 19:43:58 +0100
Subject: [PATCH] LocalStatusSQLite.py: Python 3.11 compatible threadsafety
 check

Signed-off-by: 0pointerexception 
---
 offlineimap/folder/LocalStatusSQLite.py | 10 --
 1 file changed, 8 insertions(+), 2 deletions(-)

diff --git a/offlineimap/folder/LocalStatusSQLite.py b/offlineimap/folder/LocalStatusSQLite.py
index a576b9ca..3c44643f 100644
--- a/offlineimap/folder/LocalStatusSQLite.py
+++ b/offlineimap/folder/LocalStatusSQLite.py
@@ -17,7 +17,7 @@
 
 import os
 import sqlite3 as sqlite
-from sys import exc_info
+from sys import exc_info,version_info
 from threading import Lock
 from .Base import BaseFolder
 
@@ -75,6 +75,11 @@ def __init__(self, name, repository):
 self.filename = os.path.join(self.getroot(), self.getfolderbasename())
 
 self._newfolder = False  # Flag if the folder is new.
+"""
+sqlite threading mode must be 3 as of Python 3.11, checking against
+1 for versions below Python 3.11 to sustain backwards compatibility.
+"""
+self._threading_mode_const = 3 if version_info.minor >=11 else 1
 
 dirname = os.path.dirname(self.filename)
 if not os.path.exists(dirname):
@@ -102,9 +107,10 @@ def __exit__(self, exc_type, exc_val, exc_tb):
 if self._in_transactions < 1:
 self.connection.commit()
 
+
 def openfiles(self):
 # Make sure sqlite is in multithreading SERIALIZE mode.
-assert sqlite.threadsafety == 1, 'Your sqlite is not multithreading safe.'
+assert sqlite.threadsafety == self._threading_mode_const, 'Your sqlite is not multithreading safe.'
 
 with self._databaseFileLock.getLock():
 # Try to establish connection, no need for threadsafety in __init__.

Bug#986583: btrfs-progs: "Received UUID" not cleared on "btrfs set property ... ro false"

[Nicholas D Steeves]

Dear Leszek,

I agree that it seems inconsistent that "Received UUID" is not cleared,
and I'm surprised no one replied to your bug!

Leszek Dubiel  writes:

> Package: btrfs-progs
> Version: 4.20.1-2
> Severity: minor
>
>
>
> When one imports subvolume through   btrfs send ... | btrfs receive ...
> then snapshot gets "Received UUID" from remote system.
>
> When you   "btrfs sub snap -r ...", create readonly snapshot of received
> snapshot, then "Received UUID" is copied.
>
> When you   "btrfs sub snap ...", create read-write snapshot, then
> "Received UUID" of new snapshot is cleared. That is GOOD.
>
> But if you "btrfs set prop ... ro false" then "Received UUID" is not
> cleared. I think this should be cleared -- in the same style when
> you snapshot without "readonly" flag.
>
> Testing script:
>
[snip]

Thank you for steps to reproduce as well as the script!

Do you know if this bug is still present in newer releases?  If it's
still present with either linux and btrfs-progs 6.x then this issue should
immediately be forwarded upstream.  If I remember correctly 5.10.x is
also still supported, and if it's fixed in 6.x but not in 5.10.x then
the fix might need to be backported--to my eyes the regression risk is
low.

Regards,
Nicholas


signature.asc
Description: PGP signature

Bug#1027836: planner,planner-data: both ship /usr/share/planner/images/gnome-planner.png

[Andreas Beckmann]

Package: planner,planner-data
Version: 0.14.91-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your packages failed to install
because they tries to overwrite each others files.

>From the attached log (scroll to the bottom...):

  Selecting previously unselected package planner.
  Preparing to unpack .../101-planner_0.14.91-1_amd64.deb ...
  Unpacking planner (0.14.91-1) ...
  dpkg: error processing archive 
/tmp/apt-dpkg-install-9JdNac/101-planner_0.14.91-1_amd64.deb (--unpack):
   trying to overwrite '/usr/share/planner/images/gnome-planner.png', which is 
also in package planner-data 0.14.91-1
  Errors were encountered while processing:
   /tmp/apt-dpkg-install-9JdNac/101-planner_0.14.91-1_amd64.deb


cheers,

Andreas


planner=0.14.91-1_planner-data=0.14.91-1.log.gz
Description: application/gzip

Bug#1027835: seahorse-adventures: SyntaxWarning with python3.11: invalid decimal literal "if x >=0and x

[Simon McVittie]

Package: seahorse-adventures
Version: 1.1+dfsg-5
Severity: minor

> Setting up python3 (3.11.1-1) ...
> running python rtupdate hooks for python3.11...
> /usr/share/games/seahorse-adventures/lib/pgu/tilevid.py:39: SyntaxWarning: 
> invalid decimal literal
>   if x >=0and x= 0 and x < w" is preferred due to being
less ambiguous. Digits immediately followed by a keyword are deprecated
since 3.10 and will eventually become a syntax error, according to
.

smcv

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

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

Versions of packages seahorse-adventures depends on:
ii  fonts-aenigma  0.0.20080511+dfsg-4
ii  fonts-dejavu-core  2.37-2
ii  python33.11.1-1
ii  python3-pygame 2.1.2+dfsg-5

seahorse-adventures recommends no packages.

seahorse-adventures suggests no packages.

-- no debconf information

Bug#1027789: libc-bin: zic should not be installed in /sbin/

[Jérémy Lal]

Le mar. 3 janv. 2023 à 21:23, Aurelien Jarno  a écrit :

> Hi,
>
> On 2023-01-03 12:18, Jérémy Lal wrote:
> > Package: libc-bin
> > Version: 2.36-7
> > Severity: normal
> >
> > It seems very odd that zic is installed in /sbin/zic.
>
> Could you please elaborate? zic is primarily used for administration
> tasks and requires write access to /usr/share/zoneinfo in its default
> invocation.
>

I was just looking at https://bugs.debian.org/1003044
and found out that it will call zic at some point, to be fixed.
I had no idea it was in /sbin, because it didn't look like a root-only
command to me.
And when looking at other commands in /sbin, zic seems a bit to be a
special case.
But if you don't want to change that, that's okay for me.

>
> Also please note that the debian package uses the same path than
> upstream (as in glibc, tzdata, Linux man-pages), and matches what is
> done on other SysV or BSD systems.
>

Ok, I suppose it's for historical reasons, then.

Jérémy

Bug#1027834: hplip: unable to print with hp laserjet P1006 (debian/sid)

[K.D]

Package: hplip
Severity: normal
X-Debbugs-Cc: drazi...@gmail.com

Dear Maintainer,

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

   * What led up to the situation?
I use debian/sid. I had a working printer (hplip 3.22.10 was installed from 
source).
However, the hplip version from the repos never worked for my printer. After 
the last update, again everything was messed up, and I "lost" somehow the 
ability to print. hplip again cannot be installed from the repos (it needs 
python <11). Anyway, something went very wrong after the update.

   * What exactly did you do (or not do) that was effective (or
 ineffective)?
   * What was the outcome of this action?
   * What outcome did you expect instead?

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


-- System Information:
Debian Release: bookworm/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)

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

Versions of packages hplip depends on:
ii  adduser3.130
ii  cups   2.4.2-1+b2
pn  hplip-data 
ii  libc6  2.36-7
ii  libcups2   2.4.2-1+b2
ii  libdbus-1-31.14.4-1
pn  libhpmud0  
ii  libpython3.10  3.10.9-1
pn  libsane-hpaio  
ii  libsane1   1.1.1-6+b1
ii  lsb-base   11.5
pn  printer-driver-hpcups  
ii  python33.11.1-1
ii  python3-dbus   1.3.2-3
ii  python3-gi 3.42.2-3
pn  python3-pexpect
ii  python3-pil9.3.0-1
ii  python3-reportlab  3.6.12-1
ii  sysvinit-utils [lsb-base]  3.06-2
ii  wget   1.21.3-1+b1
ii  xz-utils   5.4.0-0.1

Versions of packages hplip recommends:
ii  avahi-daemon  0.8-6+b1
ii  policykit-1   122-1
ii  printer-driver-postscript-hp  3.22.6+dfsg0-1
ii  sane-utils1.1.1-6+b1

Versions of packages hplip suggests:
pn  hplip-doc  
pn  hplip-gui  
ii  python3-notify20.3-5
pn  system-config-printer  

Bug#1027833: user-mode-linux: hostfs directory traversal

[Jakub Wilk]

Package: user-mode-linux
Version: 6.0um1+b1
Tags: security

The man page says that hostfs kernel param is "used to confine all 
hostfs mounts to within the specified directory tree on the host". But 
it's trivial to escape this confinements with ../ sequences:


  # mount none -t hostfs -o ../../../../../../../../home/bob/secrets /mnt


-- System Information:
Architecture: i386

--
Jakub Wilk

Bug#1027785: btrfs-progs: Version 6.1 breaks btrbk

[Nicholas D Steeves]

Control: tag -1 fixed-upstream

Yannick Roehlly  writes:

> Package: btrfs-progs
> Version: 6.1-1+b1
> Severity: important
> Tags: upstream
>
> Hi,
>
> Version 6.1 of btrfs-progs has a bug that makes the UUID empty in the 
> subvolume
> list:
>
> https://github.com/kdave/btrfs-progs/issues/562
>
> This breaks btrbk that stops making snapshots and backups:
>
> https://github.com/digint/btrbk/issues/519
>

Here is how to fix btrbk today: 
https://salsa.debian.org/go-team/packages/golang-github-containers-storage/-/commit/a4b6809d1b9f4a3854f5f852d355ca9a17c93404

> Apparently a hotfix 6.1.1 release is planned in a few days.
>

It's been released, and it's worth noting that that
golang-github-containers-storage commit will need to be reverted.

Regards,
Nicholas


signature.asc
Description: PGP signature

Bug#1019526: gnome-control-center: color management broken after update, segfault

[Mike Gerow]

tags 1019526 patch
thanks

Looks like the issue has been addressed upstream
https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/1640 with
2893f8e3f9cc94f969a7f2062585aef4161df235 which I'm guessing should
show up when 44 is released.

That said, the patch applies cleanly to 43, so this could be pulled
forward early to address the segfault. Patch attached.
From 2893f8e3f9cc94f969a7f2062585aef4161df235 Mon Sep 17 00:00:00 2001
From: Mohammed Sadiq 
Date: Tue, 15 Nov 2022 16:01:43 +0530
Subject: [PATCH] color: Select first device row only if non-NULL

Otherwise we might read some invalid memory resulting in a crash
---
 panels/color/cc-color-panel.c | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/panels/color/cc-color-panel.c b/panels/color/cc-color-panel.c
index f55fcf93b..42820c798 100644
--- a/panels/color/cc-color-panel.c
+++ b/panels/color/cc-color-panel.c
@@ -1642,7 +1642,8 @@ gcm_prefs_update_device_list_extra_entry (CcColorPanel *prefs)
   gtk_widget_set_visible (prefs->box_devices, first_row != NULL);
 
   /* if we have only one device expand it by default */
-  if (gtk_list_box_get_row_at_index (prefs->list_box, 1) == NULL)
+  if (first_row != NULL &&
+  gtk_list_box_get_row_at_index (prefs->list_box, 1) == NULL)
 cc_color_device_set_expanded (CC_COLOR_DEVICE (first_row), TRUE);
 }
 
-- 
2.39.0.314.g84b9a713c41-goog

Bug#1027176: u-boot-amlogic: broken non-EFI boot on odroid-c2

[Vagrant Cascadian]

On 2023-01-03, Frédéric Danis wrote:
> On 03/01/2023 18:55, Vagrant Cascadian wrote:
>> On 2023-01-03, Frédéric Danis wrote:
>>> Afaiu, the bug is not reproducible with unstable and experimental
>>> versions, but boot crash before starting the kernel, see
>>> lepotato-unstable.txt and lepotato-experimental.txt.
>> Sounds like the bug *is* reproducible with unstable and experiemental
>> versions, from reading the logs; looks like the same issue with
>> odroid-c2.
>>
>> Could you try building a "noefi" variant, like done with odroid-c2, and
>> test for the lepotato (libretech-cc?):
>>
>>
>> https://salsa.debian.org/debian/u-boot/-/commit/711ca985af1cab6f11e33fcf5e30dcc40dc7e64d
>
> I will try to build and test this
>
>> Could you also test EFI booting with the versions from unstable and
>> experimental to see if they can load a kernel? If EFI does work, that
>> justifies building two variants with and without EFI... it is a bit ugly
>> to produce two variants, but it's the easiest known workaround for
>> now...
>
> I will need your help on this as I don't know how to test EFI boot, for 
> me EFI was specific to Intel platforms.
> Can you point me to a doc explaining how to do this on LePotato/Arm board?

What I did for the odroid-c2 was download the debian-installer mini.iso:

  https://d-i.debian.org/daily-images/arm64/daily/netboot/

And dump it onto a USB stick. Then at boot, I interrupted the boot
process, and at the u-boot prompt:

  setenv boot_targets usb0
  boot

This of course presumes usb works for your platform.

You might be able to do a dance with microSD or whatever by booting from
microSD, yanking the microSD card, inserting a microSD card with the
mini.iso installed, rescanning the mmc bus, etc. but that is obviously a
lot tricker!

live well,
  vagrant


signature.asc
Description: PGP signature

Bug#1027832: debian-policy: Please clarify that priority required packages are not automatically build essential

[Santiago Vila]

Package: debian-policy
Version: 4.6.2.0
Severity: wishlist

Hello. This is an attempt to put the basis for fixing this bug:

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

As an example, packages tzdata, mount or e2fsprogs are not build-essential
and afaik have not been for a long time, but there are still people who
believe that they are build-essential for the mere fact that they are
priority:required.

Therefore I think a clarification would be useful to clear those kind
of misconceptions.

Proposed text, to be added after the paragraph which defines build essential
based on the Hello World example:

--
From this definition it follows that packages of required priority are not
necessarily build essential, as it is possible for some them not to be
needed at all to compile, link and put in a Debian package a Hello World
program written in C or C++.
--

Next step would be to add a paragraph saying tools like debootstrap when used
to create chroots for building (i.e. "buildd" profile in deboostrap) should try
to keep the list of installed packages as minimal as possible, as far as
doing so does not become disruptive (for example, apt is technically not
build-essential but it is required to install the build-dependencies).

Thanks.

Bug#1027831: libpackagekitqt5-1: Discover does not notify about pending updates

[luca]

Package: libpackagekitqt5-1
Version: 1.1.0-1
Severity: normal
X-Debbugs-Cc: ago...@gmail.com

after latest update of libpackagekitqt5-1 DiscoverNotifier in plasma-kde stops
notify about pending updates

revert to previous version 1.0.2-1 it works

https://bugs.kde.org/show_bug.cgi?id=462170#c12


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

Kernel: Linux 6.0.0-4-amd64 (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.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 libpackagekitqt5-1 depends on:
ii  libc6 2.36-7
ii  libgcc-s1 12.2.0-11
ii  libqt5core5a  5.15.7+dfsg-2
ii  libqt5dbus5   5.15.7+dfsg-2
ii  libstdc++612.2.0-11

libpackagekitqt5-1 recommends no packages.

Versions of packages libpackagekitqt5-1 suggests:
ii  packagekit  1.2.6-1

-- no debconf information

Bug#1027830: openssl: starttls fails on our LDAP server on bullseye, but it works on buster

[Jonathan]

Package: openssl
Version: 1.1.1k-1
Severity: normal

Dear Maintainer,

   * What led up to the situation?

After trying to update to bullseye, connecting to our LDAP server no longer 
works, both with pam_ldap package as well as using ldapsearch from ldap-utils.


   * What exactly did you do (or not do) that was effective (or
 ineffective)?
On Debian 9 or 10, or on Ubuntu 22.04, our configuration works and ldapsearch 
with the -ZZ flag works. 
On Debian 11, it does not. I've tried installing the version of the openssl 
package that Debian 10 uses on a Debian 11 system, but still it didn't work. 
Querying the server with the following command works perfectly:

openssl s_client -starttls ldap -connect :

The output of this command says amongst other things "SSL handshake has read 
4692 bytes and written 436 bytes. Verification: OK" and lists the full 
certificate chain. 
If adding the -showcerts flag, all certificates in the chain are shown 
succesfully.


   * What was the outcome of this action?
ldapsearch gives the following output: 

ldap_start_tls: Connect error (-11)
additional info: (unknown error code)


   * What outcome did you expect instead?

It should query the LDAP server and successfully return data.


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

Kernel: Linux 5.15.83-1-pve (SMP w/1 CPU thread)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE
Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages openssl depends on:
ii  libc6  2.31-13
ii  libssl1.1  1.1.1k-1

openssl recommends no packages.

Versions of packages openssl suggests:
ii  ca-certificates  20210119

-- no debconf information

Bug#1027176: u-boot-amlogic: broken non-EFI boot on odroid-c2

[Vagrant Cascadian]

On 2023-01-02, Vagrant Cascadian wrote:
> On 2023-01-02, Vagrant Cascadian wrote:
>> On 2022-12-28, Vagrant Cascadian wrote:
>>> The odroid-c2 fails to boot syslinux/extlinux style menus (e.g. those
>>> produced by u-boot-menu) or boot.scr as of upstream 2022.07-rc1. The
>>> commit triggering the issue has been identified as:
>>>
>>>   a9bf024b2933bba0e23038892970a18b72dfaeb4
>>>   efi_loader: disk: a helper function to create efi_disk objects from
>>>   udevice
>>>
>>> Workarounds I've heard are to disable EFI support for that board
> ...
>> Obviously, it breaks EFI booting...
>>
>> Worst case, I suppose we could create two variants, one with EFI, one
>> without...
>
> I have pushed a patch to git implementing an odroid-c2-noefi variant:
>
>   
> https://salsa.debian.org/debian/u-boot/-/commit/711ca985af1cab6f11e33fcf5e30dcc40dc7e64d
>
> This would not close the bug, but at least downgrade the severity...

I can confirm that 2023.01-rc4+dfsg-1 does boot successfully with EFI on
the odroid-c2, so ... the two variant solution is a viable one if a
proper fix cannot be figured out in time for bookworm.


live well,
  vagrant


signature.asc
Description: PGP signature

Bug#1022952: pam-auth-update ignores --root for /usr/share/pam-configs

[Johannes Schauer Marin Rodrigues]

Quoting Sam Hartman (2023-01-03 21:29:10)
> I'm committing this.

Perfect! Since gcc-defaults 1.202 was also uploaded two days ago, this will
mean that no patches are required anymore to create a chrootless essential
chroot plus apt. Thank you!! :)

> For reasons entirely unclear to me, pam is not listed in
> https://release.debian.org/testing/essential-and-build-essential.txt
> 
> so we haven't missed the train for bookworm.

Huh, that's indeed odd!

Bug#1023686: readline: Inaccurate copyright file

[Bastian Germann]

I am uploading a NMU with the attached debdiff to DELAYED/10 in order to 
address this.diff -Nru readline-8.2/debian/changelog readline-8.2/debian/changelog
--- readline-8.2/debian/changelog   2022-11-11 07:37:10.0 +0100
+++ readline-8.2/debian/changelog   2023-01-03 21:49:45.0 +0100
@@ -1,3 +1,11 @@
+readline (8.2-1.3) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Convert d/copyright to machine-readable format, adding missing info.
+(Closes: #1023686)
+
+ -- Bastian Germann   Tue, 03 Jan 2023 21:49:45 +0100
+
 readline (8.2-1.2) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -Nru readline-8.2/debian/copyright readline-8.2/debian/copyright
--- readline-8.2/debian/copyright   2016-02-06 12:26:16.0 +0100
+++ readline-8.2/debian/copyright   2023-01-03 21:49:00.0 +0100
@@ -1,68 +1,99 @@
-This is Debian GNU/Linux's prepackaged version of the FSF's GNU
-Readline library.
-
-This package was put together by Matthias Klose , derived
-from the bash package by Guy Maor , from the GNU sources at
-
-   ftp.gnu.org:/pub/gnu/readline/readline-6.0.tar.gz.
-
-Upstream Authors:
-
+Format: https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/
+Comment:
+This is Debian GNU/Linux's prepackaged version of the FSF's GNU
+Readline library.
+ .
+This package was put together by Matthias Klose ,
+derived from the bash package by Guy Maor .
+Upstream-Name: Readline
+Upstream-Contact: 
 Chet Ramey 
 Jeff Solomon  (examples/excallback.c)
 Harold Levy  (examples/rl-fgets.c)
-Juergen Weigert  (examples/rlfe)
-Michael Schroeder  
(examples/rlfe)
-Oliver Laumann (examples/rlfe)
+Source: http://ftp.gnu.org/gnu/readline/
 
+Files: *
 Copyright:
-
-Copyright (C) 1987-2009 Free Software Foundation, Inc.
-Copyright (C) 1999 Jeff Solomon (examples/excallback.c)
-Copyright (C) 2003-2004 Harold Levy (examples/rl-fgets.c)
-Copyright (C) 1993-2002 Juergen Weigert (examples/rlfe)
-Copyright (C) 1993-2002 Michael Schroeder (examples/rlfe)
-Copyright (C) 1987 Oliver Laumann (examples/rlfe)
-
-License:
-
+Copyright (C) 1987-2022 Free Software Foundation, Inc.
+License: GPL-3+
 Readline is free software: you can redistribute it and/or modify
 it under the terms of the GNU General Public License as published by
 the Free Software Foundation, either version 3 of the License, or
 (at your option) any later version.
-
+ .
 This package is distributed in the hope that it will be useful,
 but WITHOUT ANY WARRANTY; without even the implied warranty of
 MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
 GNU General Public License for more details.
-
+ .
 You should have received a copy of the GNU General Public License
 along with Readline.  If not, see .
+Comment:
+ On Debian systems, the complete text of the GNU General Public License
+ version 3 can be found in `/usr/share/common-licenses/GPL-3'.
+
+Files: examples/readlinebuf.h
+   examples/rl-fgets.c
+   examples/rlfe/*
+   examples/rlwrap-*.tar.gz
+Copyright:
+Copyright (C) 1987-2022 Free Software Foundation, Inc.
+Copyright (c) 2001 by Dimitris Vyzovitis [v...@media.mit.edu]
+Copyright (C) 1999 Jeff Solomon (examples/excallback.c)
+Copyright (C) 2003-2004 Harold Levy (examples/rl-fgets.c)
+Copyright (c) 1993-2002 Juergen Weigert 
(jnwei...@immd4.informatik.uni-erlangen.de)
+Copyright (c) 1993-2002 Michael Schroeder 
(mlsch...@immd4.informatik.uni-erlangen.de)
+Copyright (C) 1987 Oliver Laumann (examples/rlfe)
+Copyright (C) 2004, 1999 Per Bothner
+Copyright (C) 2000-2007 Hans Lub
+Copyright (C) 1999-2001 Geoff Wing
+Copyright (C) Damian Ivereigh 2000
+License: GPL-2+
+This program is free software; you can redistribute it and/or modify
+it under the terms of the GNU General Public License as published by
+the Free Software Foundation; either version 2, or (at your option)
+any later version.
+ .
+This program is distributed in the hope that it will be useful,
+but WITHOUT ANY WARRANTY; without even the implied warranty of
+MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
+GNU General Public License for more details.
+ .
+You should have received a copy of the GNU General Public License
+along with this program (see the file COPYING); if not, write to the
+Free Software Foundation, Inc.,
+59 Temple Place - Suite 330, Boston, MA  02111-1307, USA
+Comment:
+ On Debian systems, the complete text of the GNU General Public License
+ version 2 can be found in `/usr/share/common-licenses/GPL-2'.
+ .
+ The rlwrap example is also available in its own Debian package.
+ The code copyrighted by Damian Ivereigh is licensed under LGPL-2.1+.
 
-examples/rl-fgets.c: GPL v2 or later.
-examples/rlfe: GPL v2 or later.
-
-On Debian systems, the complete text 

Bug#1027829: pflogsumm ignores header filter rejects in postfix logs

[Andreas Jaggi]

Package: pflogsumm
Version: 1.1.5-7
Severity: normal
Tags: patch

pflogsumm ignores emails rejected by non-milter cleanup mechanisms such
as header filtering. This because of a bug/typo in the milter-rejects
patch which was added in #743570: 
https://sources.debian.org/patches/pflogsumm/1.1.5-7/milter-rejects/

With the milter-rejects patch, plain 'reject:' loglines are ignored and only
'milter-reject:' loglines are counted.

Example of an ignored logline:

Dec 29 08:01:23 server postfix/cleanup[12345]: AEGIM3EE9EID: reject: header 
Received: from example.com (example.com [192.0.2.1])??by 
KooR3roh2ooxuk.server.example.org.example.com (x) with ESMTP ID: Eu_h4do??Thu, 
29 Dec 2022 08:01:23 +0100 from out.example.net[203.0.113.1]; 
from= to= proto=ESMTP 
helo=: 5.7.1 Forged Received header


How to reproduce:
- echo 'Dec 29 08:01:23 server postfix/cleanup[12345]: AEGIM3EE9EID: reject: 
header Received: from example.com (example.com [192.0.2.1])??by 
KooR3roh2ooxuk.server.example.org.example.com (x) with ESMTP ID: Eu_h4do??Thu, 
29 Dec 2022 08:01:23 +0100 from out.example.net[203.0.113.1]; 
from= to= proto=ESMTP 
helo=: 5.7.1 Forged Received header' > testlog
- pflogsumm testlog
- observe that 0 messages are reported


How to fix:
The regex in the milter-rejects patch has a bug/typo which causes it to
only match 'milter-reject:' but no longer match plain 'reject:'

+   /\/cleanup\[\d+\]: .*?\b((?:milter-)reject|warning|hold|discard): 
(header|body|END-OF-MESSAGE) (.*)$/) == 3)

The 'milter-' part should be optional to match both:

+   /\/cleanup\[\d+\]: .*?\b((?:milter-)?reject|warning|hold|discard): 
(header|body|END-OF-MESSAGE) (.*)$/) == 3)







-- System Information:
Debian Release: 11.6
  APT prefers stable
  APT policy: (990, 'stable'), (500, 'stable-updates'), (500, 'stable-security')
Architecture: amd64 (x86_64)

Kernel: Linux 5.10.0-20-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 pflogsumm depends on:
ii  libdate-calc-perl  6.4-1.1
ii  perl   5.32.1-4+deb11u2

pflogsumm recommends no packages.

pflogsumm suggests no packages.

-- no debconf information

Bug#995239: pam: please use debian/patches/ for patch series

[Sam Hartman]

> "Sam" == Sam Hartman  writes:

> "Simon" == Simon McVittie  writes:
Simon> It would be great if the pam source package used
Simon> debian/patches/ instead of debian/patches-applied/ for the
Simon> patch series. That would make configuration transferrable
Simon> between pam and other source packages, and would enable use
Simon> of more powerful tools like git-buildpackage's gbp-pq.

Sam> Steve, I'd like to make this change.  What are your thoughts?

I just noticed that pam is being dgit pushed.
Having a dgit view with patches unapplied is shall we say very counter
intuitive.
I think we should make this change when merging the next upstream.
Unless I hear an objection from Steve I will make the change if I'm ever
the one doing an upstream import.

Bug#1027824: FTBFS: hanging testsuite: build killed after time of inactivity on buildds

[Adrian Bunk]

Control: found -1 2:8.2.4793-1
ontrol: retitle -1 vim FTBFS on IPV6-only buildds

On Tue, Jan 03, 2023 at 09:15:03PM +0100, Salvatore Bonaccorso wrote:
> Hi,
> 
> On Tue, Jan 03, 2023 at 09:03:27PM +0100, Salvatore Bonaccorso wrote:
> > Source: vim
> > Version: 2:9.0.1000-2
> > Severity: serious
> > Tags: ftbfs
> > Justification: ftbfs
> > X-Debbugs-Cc: car...@debian.org
> > 
> > Hi James,
> > 
> > Severity might not be warranted, please downgrade if you think it's
> > needed.
> > 
> > I noticed on the last two vim builds that the amd64 build failed,
> > giving it back helped most of the times. The last upload failed as
> > well:
> > 
> > https://buildd.debian.org/status/fetch.php?pkg=vim=amd64=2%3A9.0.1000-3=1672773526=0
> 
> Looking at the older build failures from
> https://buildd.debian.org/status/logs.php?pkg=vim=amd64 it looks
> it was always on x86-conova-01 when it failed.

The test seems to fail on IPV6-only buildds, I suspect something might 
go wrong with the usage of "localhost" in this test without IPV4?

> Regards,
> Salvatore

cu
Adrian

Bug#1026328: libbpp-core breaks bppsuite autopkgtest

[Andreas Tille]

Hi,

when looking at

  https://ci.debian.net/packages/b/bppsuite/unstable/arm64/

I'm wondering why you assume that libbpp-core/2.4.1-9 is responsible
for the failure.  IMHO it is rather gcc-13 where the failure is
happening.  The change


libbpp-core (2.4.1-9) unstable; urgency=medium

  * Fix watch file

 -- Andreas Tille   Tue, 06 Dec 2022 19:54:08 +0100


is hardly responsible for the observed failure.

Kind regards
   Andreas.


-- 
http://fam-tille.de

Bug#1027828: macromoleculebuilder: FTBFS in bullseye (a2x: ERROR: "xsltproc" [...] returned non-zero exit status 5)

[Santiago Vila]

Package: src:macromoleculebuilder
Version: 3.2+dfsg-2
Severity: serious
Tags: ftbfs
Control: fixed -1 4.0.0+dfsg-2

Dear maintainer:

During a rebuild of all packages in bullseye, your package failed to build:


[...]
 debian/rules binary-indep
dh binary-indep
   dh_update_autotools_config -i
   dh_autoreconf -i
   debian/rules override_dh_auto_configure
make[1]: Entering directory '/<>'
rm -rf parameterization/build
dh_auto_configure -- \
-DOpenMM_INCLUDE_DIR=/usr/include \
-DCMAKE_CXX_FLAGS="-D BuildNtC -D USE_OPENMM -g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -O0"
cd obj-x86_64-linux-gnu && cmake -DCMAKE_INSTALL_PREFIX=/usr -DCMAKE_BUILD_TYPE=None 
-DCMAKE_INSTALL_SYSCONFDIR=/etc -DCMAKE_INSTALL_LOCALSTATEDIR=/var -DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON 
-DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON -DCMAKE_INSTALL_RUNSTATEDIR=/run "-GUnix Makefiles" 
-DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_INSTALL_LIBDIR=lib/x86_64-linux-gnu -DOpenMM_INCLUDE_DIR=/usr/include 
"-DCMAKE_CXX_FLAGS=-D BuildNtC -D USE_OPENMM -g -O2 -ffile-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -O0" ..
-- The C compiler identification is GNU 10.2.1
-- The CXX compiler identification is GNU 10.2.1
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Check for working C compiler: /usr/bin/cc - skipped
-- Detecting C compile features
-- Detecting C compile features - done
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Check for working CXX compiler: /usr/bin/c++ - skipped
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- Configuring done
-- Generating done
CMake Warning:
  Manually-specified variables were not used by the project:

CMAKE_EXPORT_NO_PACKAGE_REGISTRY
CMAKE_INSTALL_LIBDIR
CMAKE_INSTALL_LOCALSTATEDIR
CMAKE_INSTALL_RUNSTATEDIR
CMAKE_INSTALL_SYSCONFDIR


-- Build files have been written to: /<>/obj-x86_64-linux-gnu
make[1]: Leaving directory '/<>'
   dh_auto_build -i
cd obj-x86_64-linux-gnu && make -j1 "INSTALL=install 
--strip-program=true" VERBOSE=1
make[1]: Entering directory '/<>/obj-x86_64-linux-gnu'
/usr/bin/cmake -S/<> -B/<>/obj-x86_64-linux-gnu 
--check-build-system CMakeFiles/Makefile.cmake 0
/usr/bin/cmake -E cmake_progress_start /<>/obj-x86_64-linux-gnu/CMakeFiles 
/<>/obj-x86_64-linux-gnu//CMakeFiles/progress.marks
make  -f CMakeFiles/Makefile2 all
make[2]: Entering directory '/<>/obj-x86_64-linux-gnu'
make  -f CMakeFiles/MMBlib.dir/build.make CMakeFiles/MMBlib.dir/depend
make[3]: Entering directory '/<>/obj-x86_64-linux-gnu'
cd /<>/obj-x86_64-linux-gnu && /usr/bin/cmake -E cmake_depends "Unix Makefiles" /<> 
/<> /<>/obj-x86_64-linux-gnu /<>/obj-x86_64-linux-gnu 
/<>/obj-x86_64-linux-gnu/CMakeFiles/MMBlib.dir/DependInfo.cmake --color=
Dependee "/<>/obj-x86_64-linux-gnu/CMakeFiles/MMBlib.dir/DependInfo.cmake" is newer than 
depender "/<>/obj-x86_64-linux-gnu/CMakeFiles/MMBlib.dir/depend.internal".
Dependee "/<>/obj-x86_64-linux-gnu/CMakeFiles/CMakeDirectoryInformation.cmake" is newer 
than depender "/<>/obj-x86_64-linux-gnu/CMakeFiles/MMBlib.dir/depend.internal".
Scanning dependencies of target MMBlib
make[3]: Leaving directory '/<>/obj-x86_64-linux-gnu'
make  -f CMakeFiles/MMBlib.dir/build.make CMakeFiles/MMBlib.dir/build
make[3]: Entering directory '/<>/obj-x86_64-linux-gnu'
[  3%] Building CXX object CMakeFiles/MMBlib.dir/src/Utils.cpp.o
/usr/bin/c++ -DMMBlib_EXPORTS -I/<>/include -I/usr/include/openmm 
-I/usr/include/openmm/reference -isystem /usr/include/simbody -D BuildNtC -D USE_OPENMM -g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -O0 
-fPIC -DMMB_BUILDING_SHARED_LIBRARY -o CMakeFiles/MMBlib.dir/src/Utils.cpp.o -c 
/<>/src/Utils.cpp
In file included from /<>/src/Utils.cpp:11:
/<>/include/Utils.h:33:70: note: ‘#pragma message: using 
OpenMM::Vec3: USE_OPENMM_REALVEC NOT defined’
   33 | #pragma message ("using OpenMM::Vec3: USE_OPENMM_REALVEC NOT defined")
  |  ^
/<>/src/Utils.cpp: In function ‘int ValidateNonNegativeInt(int)’:
/<>/src/Utils.cpp:526:1: warning: control reaches end of non-void 
function [-Wreturn-type]
  526 | }
  | ^
[  6%] Building CXX object CMakeFiles/MMBlib.dir/src/BiopolymerClass.cpp.o
/usr/bin/c++ -DMMBlib_EXPORTS -I/<>/include -I/usr/include/openmm 
-I/usr/include/openmm/reference -isystem /usr/include/simbody -D BuildNtC -D USE_OPENMM -g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -O0 
-fPIC -DMMB_BUILDING_SHARED_LIBRARY -o CMakeFiles/MMBlib.dir/src/BiopolymerClass.cpp.o -c 
/<>/src/BiopolymerClass.cpp
In file included from /<>/include/Mutation.h:4,
 from /<>/include/BiopolymerClass.h:18,
 from 

Bug#989301: Intent to NMU prometheus-nextcloud-exporter to fix longstanding l10n bugs

[Helge Kreutzmann]

Hello Jonas,
I intend to NMU prometheus-nextcloud-exporter end of next week to fix 
longstanding l10n
bugs[1]. The changelog would be something like the following:

 prometheus-nextcloud-exporter (0.4.0-2.1) UNRELEASED; urgency=medium
 .
   * Non-maintainer upload.
   * Add debconf template translation
 - French translation.
   Thanks Lucien Gentis (Closes: #989301)
 - Dutch translation.
   Thanks to Frans Spiesschaert (Closes: #989698)
 - German translation.
   Thanks Helge Kreutzmann (Closes: #991488)
 - Portuguese translation.
   Thanks Américo Monteiro (Closes: #1000765)
 - Spanish translation.
   Thanks Camaleón (Closes: #1003519)
 - Brazilian Portuguese translation.
   Thanks Paulo Henrique de Lima Santana (Closes: #1026396)

Please tell me if you are currently preparing a new release yourself
and would like me to skip the NMU.

Greetings

 Helge

[1] https://i18n.debian.org/nmu-radar/nmu_bypackage.html

-- 
  Dr. Helge Kreutzmann deb...@helgefjell.de
   Dipl.-Phys.   http://www.helgefjell.de/debian.php
64bit GNU powered gpg signed mail preferred
   Help keep free software "libre": http://www.ffii.de/


signature.asc
Description: PGP signature

Bug#1027827: litecoin: FTBFS in bullseye (expired certificates in test suite)

[Santiago Vila]

Package: src:litecoin
Version: 0.18.1-1.1
Severity: serious
Tags: ftbfs
Control: fixed -1 0.21.2.1-1

Dear maintainer:

During a rebuild of all packages in bullseye, your package failed to build:


[...]
 debian/rules build-arch
dh build-arch
   dh_update_autotools_config -a
   dh_autoreconf -a

[...]

Config: Using QtTest library 5.15.2, Qt 5.15.2 (x86_64-little_endian-lp64 
shared (dynamic) release build; by GCC 10.2.1 20210110), debian 11
PASS   : PaymentServerTests::initTestCase()
QDEBUG : PaymentServerTests::paymentServerTests() 
PaymentServer::initNetManager: No active proxy server found.
QWARN  : PaymentServerTests::paymentServerTests() PaymentRequestPlus::getMerchant: Payment request: certificate expired or not 
yet active:  QSslCertificate("3", "01", "Ipbt+DxK8RDQd25/5ueXqw==", "PaymentRequest Test 
CA", "testmerchant.org", QMap(), QDateTime(2012-12-10 16:37:24.000 UTC Qt::UTC), QDateTime(2022-12-08 16:37:24.000 
UTC Qt::UTC))
QDEBUG : PaymentServerTests::paymentServerTests() PaymentServer::processPaymentRequest: 
Insecure payment request to  "LYqnbT8oyiEbNFmZeFQe8JJAVDQLPTbhkp"
QWARN  : PaymentServerTests::paymentServerTests() PaymentRequestPlus::getMerchant: Payment request: certificate expired or not 
yet active:  QSslCertificate("3", "01", "Ipbt+DxK8RDQd25/5ueXqw==", "PaymentRequest Test 
CA", "testmerchant.org", QMap(), QDateTime(2012-12-10 16:37:24.000 UTC Qt::UTC), QDateTime(2022-12-08 16:37:24.000 
UTC Qt::UTC))
FAIL!  : PaymentServerTests::paymentServerTests() Compared values are not the 
same
   Actual   (merchant)   : ""
   Expected (QString("testmerchant.org")): "testmerchant.org"
   Loc: [qt/test/paymentservertests.cpp(90)]
PASS   : PaymentServerTests::cleanupTestCase()
Totals: 2 passed, 1 failed, 0 skipped, 0 blacklisted, 10ms
* Finished testing of PaymentServerTests *
* Start testing of RPCNestedTests *
Config: Using QtTest library 5.15.2, Qt 5.15.2 (x86_64-little_endian-lp64 
shared (dynamic) release build; by GCC 10.2.1 20210110), debian 11
PASS   : RPCNestedTests::initTestCase()
PASS   : RPCNestedTests::rpcNestedTests()
PASS   : RPCNestedTests::cleanupTestCase()
Totals: 3 passed, 0 failed, 0 skipped, 0 blacklisted, 18ms
* Finished testing of RPCNestedTests *
* Start testing of CompatTests *
Config: Using QtTest library 5.15.2, Qt 5.15.2 (x86_64-little_endian-lp64 
shared (dynamic) release build; by GCC 10.2.1 20210110), debian 11
PASS   : CompatTests::initTestCase()
PASS   : CompatTests::bswapTests()
PASS   : CompatTests::cleanupTestCase()
Totals: 3 passed, 0 failed, 0 skipped, 0 blacklisted, 0ms
* Finished testing of CompatTests *
* Start testing of WalletTests *
Config: Using QtTest library 5.15.2, Qt 5.15.2 (x86_64-little_endian-lp64 
shared (dynamic) release build; by GCC 10.2.1 20210110), debian 11
PASS   : WalletTests::initTestCase()
QDEBUG : WalletTests::walletTests() TransactionTablePriv::refreshWallet
QWARN  : WalletTests::walletTests() This plugin does not support 
propagateSizeHints()
QDEBUG : WalletTests::walletTests() "NotifyTransactionChanged: 
5327c0db6132d9e2a5cf91333bb03cac71cf34df8a6f503c55a86a04cabd1760 status= 0"
QDEBUG : WalletTests::walletTests() "NotifyTransactionChanged: 
a97abfdbbcfeca9532f4b70a6975d1ac0ce4ec50cb0de1c6038c594f999d2403 status= 1"
QDEBUG : WalletTests::walletTests() "NotifyAddressBookChanged: 
mfWxJ45yp2SFn7UciZyNpvDKrzbhyfKrY8  isMine=0 purpose=send status=0"
QDEBUG : WalletTests::walletTests() "TransactionTablePriv::updateWallet: 
5327c0db6132d9e2a5cf91333bb03cac71cf34df8a6f503c55a86a04cabd1760 0"
QDEBUG : WalletTests::walletTests() "inModel=0 Index=34-34 showTransaction=1 
derivedStatus=0"
QDEBUG : WalletTests::walletTests() "TransactionTablePriv::updateWallet: 
a97abfdbbcfeca9532f4b70a6975d1ac0ce4ec50cb0de1c6038c594f999d2403 1"
QDEBUG : WalletTests::walletTests() "inModel=1 Index=1-2 showTransaction=1 
derivedStatus=1"
QWARN  : WalletTests::walletTests() This plugin does not support 
propagateSizeHints()
QDEBUG : WalletTests::walletTests() "NotifyTransactionChanged: 
ae662ffa76ce22fb14e44bd1b73c836ee881fe91669c290dbe273c5b95caa6bd status= 0"
QDEBUG : WalletTests::walletTests() "NotifyTransactionChanged: 
e5b3f3e89ed68be15e4860589591f3cf06eef7c453e441dc18a08f34d9c35940 status= 1"
QDEBUG : WalletTests::walletTests() "TransactionTablePriv::updateWallet: 
ae662ffa76ce22fb14e44bd1b73c836ee881fe91669c290dbe273c5b95caa6bd 0"
QDEBUG : WalletTests::walletTests() "inModel=0 Index=75-75 showTransaction=1 
derivedStatus=0"
QDEBUG : WalletTests::walletTests() "TransactionTablePriv::updateWallet: 
e5b3f3e89ed68be15e4860589591f3cf06eef7c453e441dc18a08f34d9c35940 1"
QDEBUG : WalletTests::walletTests() "inModel=1 Index=20-21 showTransaction=1 
derivedStatus=1"
QDEBUG : WalletTests::walletTests() "NotifyAddressBookChanged: 

Bug#1027826: python-skbio: don't Build Depend on python-matplotlib-doc (it no longer exist in bookworm)

[Paul Gevers]

Source: python-skbio
Version: 0.5.6-7
Severity: serious
Tag: ftbfs
User: debian...@lists.debian.org
Usertag: edos-uninstallable

Dear maintainer(s),

Dose [1] is reporting issues with your packages. Normally your build 
dependencies shouldn't be removed from testing without removal all 
reverse build dependencies too, nor should a package be allowed to 
migrate unless all build dependencies are candidate for migration too. 
However, somehow we ended up in the current state and your source 
package is missing a Build-Depends now. Not being able to build from 
source in a suite is an RC bug in that suite.


matplotlib stopped building python-matplotlib-doc.

Paul

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


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1027825: bind-dyndb-ldap: FTBFS in bullseye (‘dns_dyndbctx_t’ has no member named ‘refvar’)

[Santiago Vila]

Package: src:bind-dyndb-ldap
Version: 11.6-3
Severity: serious
Tags: ftbfs
Control: fixed -1 11.10-1

Dear maintainer:

During a rebuild of all packages in bullseye, your package failed to build:


[...]
 debian/rules build-arch
dh build-arch --builddirectory=build
   dh_update_autotools_config -a -O--builddirectory=build
   dh_autoreconf -a -O--builddirectory=build
libtoolize: putting auxiliary files in '.'.
libtoolize: copying file './ltmain.sh'
libtoolize: putting macros in AC_CONFIG_MACRO_DIRS, 'm4'.
libtoolize: copying file 'm4/libtool.m4'
libtoolize: copying file 'm4/ltoptions.m4'
libtoolize: copying file 'm4/ltsugar.m4'
libtoolize: copying file 'm4/ltversion.m4'
libtoolize: copying file 'm4/lt~obsolete.m4'
configure.ac:14: installing './compile'
configure.ac:4: installing './missing'
src/Makefile.am: installing './depcomp'
   debian/rules override_dh_auto_configure
make[1]: Entering directory '/<>'
dh_auto_configure -- \
--libdir=/usr/lib \
--docdir=/usr/share/doc/bind9-dyndb-ldap
cd build && ../configure --build=x86_64-linux-gnu --prefix=/usr 
--includedir=\${prefix}/include --mandir=\${prefix}/share/man 
--infodir=\${prefix}/share/info --sysconfdir=/etc --localstatedir=/var 
--disable-option-checking --disable-silent-rules 
--libdir=\${prefix}/lib/x86_64-linux-gnu --runstatedir=/run --disable-maintainer-mode 
--disable-dependency-tracking --libdir=/usr/lib --docdir=/usr/share/doc/bind9-dyndb-ldap
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /bin/mkdir -p
checking for gawk... no
checking for mawk... mawk
checking whether make sets $(MAKE)... yes
checking whether make supports nested variables... yes
checking whether make supports the include directive... yes (GNU style)
checking for gcc... gcc
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables...
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking whether gcc understands -c and -o together... yes
checking dependency style of gcc... none
checking for ar... ar
checking the archiver (ar) interface... ar
checking for gcc... (cached) gcc
checking whether we are using the GNU C compiler... (cached) yes
checking whether gcc accepts -g... (cached) yes
checking for gcc option to accept ISO C89... (cached) none needed
checking whether gcc understands -c and -o together... (cached) yes
checking dependency style of gcc... (cached) none
checking build system type... x86_64-pc-linux-gnu
checking host system type... x86_64-pc-linux-gnu
checking how to print strings... printf
checking for a sed that does not truncate output... /bin/sed
checking for grep that handles long lines and -e... /bin/grep
checking for egrep... /bin/grep -E
checking for fgrep... /bin/grep -F
checking for ld used by gcc... /usr/bin/ld
checking if the linker (/usr/bin/ld) is GNU ld... yes
checking for BSD- or MS-compatible name lister (nm)... /usr/bin/nm -B
checking the name lister (/usr/bin/nm -B) interface... BSD nm
checking whether ln -s works... yes
checking the maximum length of command line arguments... 1572864
checking how to convert x86_64-pc-linux-gnu file names to x86_64-pc-linux-gnu 
format... func_convert_file_noop
checking how to convert x86_64-pc-linux-gnu file names to toolchain format... 
func_convert_file_noop
checking for /usr/bin/ld option to reload object files... -r
checking for objdump... objdump
checking how to recognize dependent libraries... pass_all
checking for dlltool... no
checking how to associate runtime and link libraries... printf %s\n
checking for archiver @FILE support... @
checking for strip... strip
checking for ranlib... ranlib
checking command to parse /usr/bin/nm -B output from gcc object... ok
checking for sysroot... no
checking for a working dd... /bin/dd
checking how to truncate binary pipes... /bin/dd bs=4096 count=1
checking for mt... no
checking if : is a manifest tool... no
checking how to run the C preprocessor... gcc -E
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking for dlfcn.h... yes
checking for objdir... .libs
checking if gcc supports -fno-rtti -fno-exceptions... no
checking for gcc option to produce PIC... -fPIC -DPIC
checking if gcc PIC flag -fPIC -DPIC works... yes
checking if gcc static flag -static works... yes
checking if gcc supports -c -o file.o... yes
checking if gcc supports -c -o 

Bug#1022952: pam-auth-update ignores --root for /usr/share/pam-configs

[Sam Hartman]

I'm committing this.

For reasons entirely unclear to me, pam is not listed in
https://release.debian.org/testing/essential-and-build-essential.txt

so we haven't missed the train for bookworm.


--Sam

Bug#1027789: libc-bin: zic should not be installed in /sbin/

[Aurelien Jarno]

Hi,

On 2023-01-03 12:18, Jérémy Lal wrote:
> Package: libc-bin
> Version: 2.36-7
> Severity: normal
> 
> It seems very odd that zic is installed in /sbin/zic.

Could you please elaborate? zic is primarily used for administration
tasks and requires write access to /usr/share/zoneinfo in its default
invocation.

Also please note that the debian package uses the same path than
upstream (as in glibc, tzdata, Linux man-pages), and matches what is
done on other SysV or BSD systems.

Regards
Aurelien

-- 
Aurelien Jarno  GPG: 4096R/1DDD8C9B
aurel...@aurel32.net http://www.aurel32.net

Bug#1001920: Intent to NMU elfutils to fix longstanding l10n bugs

[Helge Kreutzmann]

Hello Matthias,
hello Sergio,
I intend to NMU elfutils end of next week to fix longstanding l10n
bugs[1]. The changelog would be something like the following:

 elfutils (0.188-2.1) UNRELEASED; urgency=medium
 .
   * Non-maintainer upload.
   * Add debconf template translation
 - Dutch translation.
   Thanks to Frans Spiesschaert (Closes: #930953)
 - French translation.
   Thanks Jean-Pierre Giraud (Closes: #994667)
 - German translation.
   Thanks Helge Kreutzmann (Closes: #997891)
 - Portuguese translation.
   Thanks Américo Monteiro (Closes: #1001920)
 - Spanish translation.
   Thanks Camaleón (Closes: #1003517)
 - Brazilian Portuguese translation.
   Thanks Paulo Henrique de Lima Santana (Closes: #1025512)

Please tell me if you are currently preparing a new release yourself
and would like me to skip the NMU.

Greetings

 Helge

[1] https://i18n.debian.org/nmu-radar/nmu_bypackage.html

-- 
  Dr. Helge Kreutzmann deb...@helgefjell.de
   Dipl.-Phys.   http://www.helgefjell.de/debian.php
64bit GNU powered gpg signed mail preferred
   Help keep free software "libre": http://www.ffii.de/


signature.asc
Description: PGP signature

Bug#983804: ITA ucspi-tcp and ucspi-unix

[Joost van Baal-Ilić]

*ping*

Any news?

Bye,

Joost

Bug#460232: Please clarify license

[Sam Hartman]

> "Bastian" == Bastian Germann  writes:

Bastian> The main license does not have a GPL version. However,
Bastian> there are several files licensed under specific (L)GPL
Bastian> versions and also other licenses included.  Debian Policy
Bastian> requires to document every contained license.

Bastian> I have attached a machine-readable copyright file that
Bastian> should have most licenses.

I've reviewed your machine readable copyright file and agree that it
 is  a significant improvement over the previous copyright file.
 I will commit.
 We can continue to improve going forward.
 

Bug#1027824: FTBFS: hanging testsuite: build killed after time of inactivity on buildds

[Salvatore Bonaccorso]

Hi,

On Tue, Jan 03, 2023 at 09:03:27PM +0100, Salvatore Bonaccorso wrote:
> Source: vim
> Version: 2:9.0.1000-2
> Severity: serious
> Tags: ftbfs
> Justification: ftbfs
> X-Debbugs-Cc: car...@debian.org
> 
> Hi James,
> 
> Severity might not be warranted, please downgrade if you think it's
> needed.
> 
> I noticed on the last two vim builds that the amd64 build failed,
> giving it back helped most of the times. The last upload failed as
> well:
> 
> https://buildd.debian.org/status/fetch.php?pkg=vim=amd64=2%3A9.0.1000-3=1672773526=0

Looking at the older build failures from
https://buildd.debian.org/status/logs.php?pkg=vim=amd64 it looks
it was always on x86-conova-01 when it failed.

Regards,
Salvatore

Bug#1027793: closed by Debian FTP Masters (reply to James McCoy ) (Bug#1027766: fixed in vim 2:9.0.1000-3)

[Alejandro Colomar]

Hi,

On 1/3/23 17:09, Debian Bug Tracking System wrote:

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

#1027793: vim: insert mode: Backspace doesn't do anything

It has been closed by Debian FTP Masters  (reply to 
James McCoy ).

Their explanation is attached below along with your original report.
If this explanation is unsatisfactory and you have not received a
better one in a separate message then please contact Debian FTP Masters 
 (reply to James McCoy ) 
by
replying to this email.



For my own curiosity, would you mind pointing to the specific change that fixed 
this bug?


Thanks,

Alex





--



OpenPGP_signature
Description: OpenPGP digital signature

Bug#1027824: FTBFS: hanging testsuite: build killed after time of inactivity on buildds

[Salvatore Bonaccorso]

Source: vim
Version: 2:9.0.1000-2
Severity: serious
Tags: ftbfs
Justification: ftbfs
X-Debbugs-Cc: car...@debian.org

Hi James,

Severity might not be warranted, please downgrade if you think it's
needed.

I noticed on the last two vim builds that the amd64 build failed,
giving it back helped most of the times. The last upload failed as
well:

https://buildd.debian.org/status/fetch.php?pkg=vim=amd64=2%3A9.0.1000-3=1672773526=0

Regards,
Salvatore

Bug#930953: Intent to NMU byobu to fix longstanding l10n bugs

[Helge Kreutzmann]

Hello Dustion,
I intend to NMU byobu end of next week to fix longstanding l10n
bugs[1]. The changelog would be something like the following:

 byobu (5.133-1.1) UNRELEASED; urgency=medium
 .
   * Non-maintainer upload.
   * Add/Update debconf template translation
 - Add French translation.
   Thanks to Grégoire Scano (Closes: #930953)
 - Update Russion translation.
   Thanks Lev Lamberov (Closes: #942636)
 - Add Dutch translation.
   Thanks Frans Spiesschaert (Closes: #945360)
 - Add Brazilian Portuguese translation.
   Thanks Adriano Rafael Gomes (Closes: #972450)

Please tell me if you are currently preparing a new release yourself
and would like me to skip the NMU.

Greetings

 Helge

[1] https://i18n.debian.org/nmu-radar/nmu_bypackage.html

-- 
  Dr. Helge Kreutzmann deb...@helgefjell.de
   Dipl.-Phys.   http://www.helgefjell.de/debian.php
64bit GNU powered gpg signed mail preferred
   Help keep free software "libre": http://www.ffii.de/


signature.asc
Description: PGP signature

Bug#1027823: backintime-common: New upstream release 1.3.3

[Christian Buhtz]

Package: backintime-common
Severity: wishlist
Tags: upstream

Hello,

I'm part of the upstream maintainer team. We released a new version (1.3.3) and
would like to see it in the next Debian Release.

We have a heavy bug in the previous 1.3.2 version. It isn't reported at Debian
but at upstream (https://github.com/bit-team/backintime/issues/1247).
It happens with rsync 3.2.4 or newer and is related to its way to handle
"argument protection".

The bug is fixed in backintime 1.3.3 and the solution was heavily tested and
also reviewed and approved by the rsync maintainer himself.

Thanks in advance
Christian Buhtz

-- System Information:
Debian Release: 11.6
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500,
'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

Versions of packages backintime-common depends on:
ii  cron [cron-daemon]  3.0pl1-137
ii  openssh-client  1:8.4p1-5+deb11u1
ii  python3 3.9.2-3
ii  python3-dbus1.2.16-5
pn  python3-keyring 
ii  rsync   3.2.3-4+deb11u1

Versions of packages backintime-common recommends:
pn  backintime-qt  

Versions of packages backintime-common suggests:
ii  encfs   1.9.5-1+b2
ii  powermgmt-base  1.36

Bug#807646: Intent to NMU xsp to fix longstanding l10n bugs

[Helge Kreutzmann]

Hello Jo,
I intend to NMU xsp end of next week to fix longstanding l10n
bugs[1]. The changelog would be something like the following:

 xsp (4.2-2.2) UNRELEASED; urgency=medium
 .
   * Non-maintainer upload.
   * Obvious lintian fixes:
 init.d-script-needs-depends-on-lsb-base
   * Add/Update debconf template translation
 - Update Italian translation.
   Thanks to Beatrice Torracca (Closes: #807646)
 - Update French translation.
   Thanks jean-pierre giraud (Closes: #808328)
 - Add Japanese translation.
   Thanks Takuma Yamada (Closes: #815854)
 - Add Brazilian Portuguese translation.
   Thanks Paulo Henrique de Lima Santana (Closes: #1026412)

Please tell me if you are currently preparing a new release yourself
and would like me to skip the NMU.

Greetings

 Helge

[1] https://i18n.debian.org/nmu-radar/nmu_bypackage.html

-- 
  Dr. Helge Kreutzmann deb...@helgefjell.de
   Dipl.-Phys.   http://www.helgefjell.de/debian.php
64bit GNU powered gpg signed mail preferred
   Help keep free software "libre": http://www.ffii.de/


signature.asc
Description: PGP signature

Bug#1026114: RFS: ruby-mdl/0.12.0-1 [ITP] -- Markdown lint tool

[Jakub Wilk]

* Norwid Behrnd , 2022-12-31 13:06:

Package: sponsorship-requests
Severity: wishlist


As far as I can see, this RFS hasn't been filed as a new bug, but 
instead it was delivered to the ITP bug, where it's unlikely to been 
seen.


I think it's because your mail had the bug number in the subject, so BTS 
treated it a bug reply (even though it was sent to the submit@ address).


--
Jakub Wilk

Bug#1023312: fixed in ipmitool 1.8.19-4

[Elimar Riesebieter]

* Jörg Frings-Fürst  [2023-01-03 19:17 +0100]:

> 
> tag 1023312 + moreinfo
> thanks
> 
> Hi,
> 
> Am Montag, dem 02.01.2023 um 14:07 +0100 schrieb Elimar Riesebieter:
> > Control: found -1 1.8.19-4
> > 
> > * Debian Bug Tracking System  [2022-12-31
> > 04:39 +]:
> > 
> > > Source: ipmitool
> > > Source-Version: 1.8.19-4
> > > Done: Jörg Frings-Fürst 
> > > 
> > > We believe that the bug you reported is fixed in the latest version
> > > of
> > > ipmitool, which is due to be installed in the Debian FTP archive.
> > 
> > Bug is still present.
> > 
> Please can you send the output of 
> 
> ls -l /usr/share/misc/


insgesamt 1444
-rwxr-xr-x 1 root root   49482 Jan 31  2022 config.guess
-rwxr-xr-x 1 root root   35406 Jan 31  2022 config.sub
-rw-r--r-- 1 root root   29255 Dec 26  2021 keymap.syms
-rw-r--r-- 1 root root 497 Dec 26  2021 keymap.xkeys
-rw-r--r-- 1 root root2064 Dec 26  2021 keysym.equiv
lrwxrwxrwx 1 root root  13 Nov 19  2020 magic -> ../file/magic
lrwxrwxrwx 1 root root  24 Apr 24  2022 magic.mgc -> 
../../lib/file/magic.mgc
-rw-r--r-- 1 root root 1344776 Dec 24 17:19 pci.ids
lrwxrwxrwx 1 root root  25 Dec 22 13:06 usb.ids -> /var/lib/usbutils/usb.ids

Elimar
-- 
  "Talking much about oneself can also
   be a means to conceal oneself."
 -Friedrich Nietzsche

Bug#1027820: nctetris man page: bad description in NAME section

[nick black]

https://github.com/dankamongmen/notcurses/issues/2693

thanks! i'll fix this upstream and report here.

Bug#1024752: closed by Debian FTP Masters (reply to Patrick Franz ) (Bug#1024752: fixed in qt6-websockets 6.4.1-2)

[Helmut Grohne]

Control: reopen -1

Hi Patrick,

On Sun, Dec 11, 2022 at 12:57:05AM +, Debian Bug Tracking System wrote:
> It has been closed by Debian FTP Masters  
> (reply to Patrick Franz ).

I think the patch got broken during application. extra_cmake_args vs
cmake_extra_args. Could you fix that up?

Helmut

Bug#1027822: graphviz FTCBFS: issues with language bindings

[Helmut Grohne]

Source: graphviz
Version: 2.42.2-7
Tags: patch
User: debian-cr...@lists.debian.org
Usertags: cross-satisfiability ftcbfs

graphviz fails to cross build from source. The host Python cannot be
installed, rather the build architecture Python interpreter and the host
architecture development files are needed here. Also perl uses the build
architecture development files rather than the host's one. I'm attaching
a patch to fix both for your convenience.

Helmut
diff --minimal -Nru graphviz-2.42.2/debian/changelog 
graphviz-2.42.2/debian/changelog
--- graphviz-2.42.2/debian/changelog2022-06-15 19:55:30.0 +0200
+++ graphviz-2.42.2/debian/changelog2023-01-03 11:02:29.0 +0100
@@ -1,3 +1,12 @@
+graphviz (2.42.2-7.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix FTCBFS: (Closes: #-1)
++ Multiarchify python build dependencies.
++ Tell perl about the host development files.
+
+ -- Helmut Grohne   Tue, 03 Jan 2023 11:02:29 +0100
+
 graphviz (2.42.2-7) unstable; urgency=medium
 
   * Recommend fonts-liberation2 (closes: #1003006).
diff --minimal -Nru graphviz-2.42.2/debian/control 
graphviz-2.42.2/debian/control
--- graphviz-2.42.2/debian/control  2022-06-15 19:55:30.0 +0200
+++ graphviz-2.42.2/debian/control  2023-01-03 11:02:29.0 +0100
@@ -29,7 +29,8 @@
  libargon2-dev,
  libsodium-dev,
  libxml2-dev,
- python3-dev,
+ libpython3-dev,
+ python3-dev:any,
  libcairo2-dev,
  libpango1.0-dev,
  d-shlibs,
diff --minimal -Nru graphviz-2.42.2/debian/rules graphviz-2.42.2/debian/rules
--- graphviz-2.42.2/debian/rules2022-06-15 19:55:30.0 +0200
+++ graphviz-2.42.2/debian/rules2023-01-03 11:02:28.0 +0100
@@ -4,6 +4,7 @@
 # Uncomment this to turn on verbose mode.
 #export DH_VERBOSE=1
 
+include /usr/share/dpkg/architecture.mk
 DPKG_EXPORT_BUILDFLAGS = 1
 include /usr/share/dpkg/buildflags.mk
 
@@ -26,6 +27,12 @@
 RUBY = --enable-ruby
 endif
 
+ifneq ($(DEB_BUILD_ARCH),$(DEB_HOST_ARCH))
+PERLVER := $(shell perl -MConfig -e 'print $$Config{version}')
+export PERL5LIB := /usr/lib/$(DEB_HOST_MULTIARCH)/perl/cross-config-$(PERLVER)
+endif
+
+
 PYTHON_VERSIONS  = $(shell pyversions -r)
 PYTHON3_VERSIONS = $(shell py3versions -r)
 

Bug#1027821: neovim FTBFS with nocheck profile: missing Build-Depends: lua-mpack

[Helmut Grohne]

Source: neovim
Version: 0.7.2-4
Severity: important
Justification: will be serious after bookworm
Tags: ftbfs

neovim fails to build from source when built with the nocheck build
profile, because it misses a build dependency on lua-mpack. This
dependency is implied in one of the  annotated dependencies,
and therefore must be listed explicitly. This bug will become
release-critical after bookworm has been released.

Helmut

Bug#1027176: u-boot-amlogic: broken non-EFI boot on odroid-c2

[Frédéric Danis]

On 03/01/2023 18:55, Vagrant Cascadian wrote:

On 2023-01-03, Frédéric Danis wrote:

On 29/12/2022 00:07, Vagrant Cascadian wrote:

On 2022-12-28, Vagrant Cascadian wrote:

The odroid-c2 fails to boot syslinux/extlinux style menus (e.g. those
produced by u-boot-menu) or boot.scr as of upstream 2022.07-rc1. The
commit triggering the issue has been identified as:

a9bf024b2933bba0e23038892970a18b72dfaeb4
efi_loader: disk: a helper function to create efi_disk objects from
udevice

Workarounds I've heard are to disable EFI support for that board, or to
boot using EFI rather than boot scripts or syslinux/extlinux style
menus.

I will also want to get confirmation if other amlogic boards are
affected...

The currently supported amlogic platforms are:

# Neil Armstrong 
u-boot-amlogic_platforms += khadas-vim

# Neil Armstrong 
u-boot-amlogic_platforms += khadas-vim2

# Frederic Danis 
u-boot-amlogic_platforms += libretech-cc

# Neil Armstrong 
u-boot-amlogic_platforms += nanopi-k2

# Vagrant Cascadian 
u-boot-amlogic_platforms += odroid-c2

# Reco 
u-boot-amlogic_platforms += odroid-n2

Please test if the current versions from Debian unstable (2022.10*) and
experimental (2023.01-rc*) are affected by this issue... and if there
are other issues for Debian bookworm/testing (2022.04*).

This is part of what has been blocking u-boot from migrating to testing.


I do not see (m)any records of tests for most of these platforms at:

https://wiki.debian.org/U-boot/Status


live well,
vagrant

u-boot bookworm version works fine with LePotato board (libretech-cc),
see attached lepotato-bookworm.txt.

Thanks!


Afaiu, the bug is not reproducible with unstable and experimental
versions, but boot crash before starting the kernel, see
lepotato-unstable.txt and lepotato-experimental.txt.

Sounds like the bug *is* reproducible with unstable and experiemental
versions, from reading the logs; looks like the same issue with
odroid-c2.

Could you try building a "noefi" variant, like done with odroid-c2, and
test for the lepotato (libretech-cc?):

   
https://salsa.debian.org/debian/u-boot/-/commit/711ca985af1cab6f11e33fcf5e30dcc40dc7e64d


I will try to build and test this


Could you also test EFI booting with the versions from unstable and
experimental to see if they can load a kernel? If EFI does work, that
justifies building two variants with and without EFI... it is a bit ugly
to produce two variants, but it's the easiest known workaround for
now...


I will need your help on this as I don't know how to test EFI boot, for 
me EFI was specific to Intel platforms.

Can you point me to a doc explaining how to do this on LePotato/Arm board?

Regards,

Fred

--
Frédéric Danis
Senior Software Engineer

Collabora Ltd.
Platinum Building, St John's Innovation Park, Cambridge CB4 0DS, United Kingdom
Registered in England & Wales, no. 5513718

Bug#1026779: closed by Debian FTP Masters (reply to Matthias Klose ) (Bug#1026779: fixed in binutils 2.39.50.20221224-1)

[Antonio Terceiro]

Control: reopen -1

On Sat, Dec 24, 2022 at 02:45:07PM +, Debian Bug Tracking System wrote:
> This is an automatic notification regarding your Bug report
> which was filed against the src:binutils package:
> 
> #1026779: binutils: cross binutils and foreign libbinutils not coinstallable, 
> breaking upgrades
> 
> It has been closed by Debian FTP Masters  
> (reply to Matthias Klose ).
> 
> Their explanation is attached below along with your original report.
> If this explanation is unsatisfactory and you have not received a
> better one in a separate message then please contact Debian FTP Masters 
>  (reply to Matthias Klose ) 
> by
> replying to this email.
> 
> 
> -- 
> 1026779: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026779
> Debian Bug Tracking System
> Contact ow...@bugs.debian.org with problems

> Date: Sat, 24 Dec 2022 14:40:11 +
> From: Debian FTP Masters 
> To: 1026779-cl...@bugs.debian.org
> Subject: Bug#1026779: fixed in binutils 2.39.50.20221224-1
> Reply-To: Matthias Klose 
> Message-Id: 
> 

> Date: Tue, 20 Dec 2022 21:04:46 -0300
> From: Antonio Terceiro 
> To: Debian Bug Tracking System 
> Subject: binutils: cross binutils and foreign libbinutils not
>  coinstallable, breaking upgrades
> Message-ID: 
> 
> Source: binutils
> Version: 2.39.50.20221208-5
> Severity: serious
> 
> Dear Maintainer,
> 
> Up to src:binutils 2.39-8, binutils-${DEB_HOST_MULTIARCH} and
> libbinutils:${DEB_HOST_ARCH} were coinstallable. Upgrading a system
> where both are installed (e.g. binutils-aarch64-linux-gnu and
> libbinutils:arm64) fails like this:
> 
> 8<8<8<-
> Unpacking libbinutils:arm64 (2.39.50.20221208-5) over (2.39-8) ...
> Preparing to unpack 
> .../3-binutils-aarch64-linux-gnu_2.39.50.20221208-5_amd64.deb ...
> Unpacking binutils-aarch64-linux-gnu (2.39.50.20221208-5) over (2.39-8) ...
> dpkg: error processing archive 
> /tmp/apt-dpkg-install-maU0ym/3-binutils-aarch64-linux-gnu_2.39.50.20221208-5_amd64.deb
>  (--unpack):
>  trying to overwrite '/usr/lib/aarch64-linux-gnu/libsframe.so.0.0.0', which 
> is also in package libbinutils:arm64 2.39.50.20221208-5
> dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
> Preparing to unpack .../4-binutils-common_2.39.50.20221208-5_amd64.deb ...
> De-configuring binutils-common:arm64 (2.39-8), to allow configuration of 
> binutils-common:amd64 (2.39.50.20221208-5) ...
> Unpacking binutils-common:amd64 (2.39.50.20221208-5) over (2.39-8) ...
> Preparing to unpack .../5-binutils-common_2.39.50.20221208-5_arm64.deb ...
> Unpacking binutils-common:arm64 (2.39.50.20221208-5) over (2.39-8) ...
> Selecting previously unselected package libbinutils:amd64.
> Preparing to unpack .../6-libbinutils_2.39.50.20221208-5_amd64.deb ...
> Unpacking libbinutils:amd64 (2.39.50.20221208-5) ...
> Selecting previously unselected package libjansson4:amd64.
> Preparing to unpack .../7-libjansson4_2.14-2_amd64.deb ...
> Unpacking libjansson4:amd64 (2.14-2) ...
> Errors were encountered while processing:
>  
> /tmp/apt-dpkg-install-maU0ym/3-binutils-aarch64-linux-gnu_2.39.50.20221208-5_amd64.deb
> E: Sub-process /usr/bin/dpkg returned an error code (1)
> 8<8<8<-

i386 is still affected by this on 2.39.50.20221224-1 (testing):

Unpacking binutils-i686-linux-gnu (2.39.50.20221224-1) ...
dpkg: error processing archive 
/tmp/apt-dpkg-install-X01H6O/8-binutils-i686-linux-gnu_2.39.50.20221224-1_amd64.deb
 (--unpack):
 trying to overwrite '/usr/lib/i386-linux-gnu/libsframe.so.0.0.0', which is 
also in package libbinutils:i386 2.39.50.20221224-1
Errors were encountered while processing:
 
/tmp/apt-dpkg-install-X01H6O/8-binutils-i686-linux-gnu_2.39.50.20221224-1_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)

and also on 2.39.90.20221231-1 (unstable)

Unpacking binutils-i686-linux-gnu (2.39.90.20221231-1) ...
dpkg: error processing archive 
/var/cache/apt/archives/binutils-i686-linux-gnu_2.39.90.20221231-1_amd64.deb 
(--unpack):
 trying to overwrite '/usr/lib/i386-linux-gnu/libsframe.so.0.0.0', which is 
also in package libbinutils:i386 2.39.90.20221231-1
Errors were encountered while processing:
 /var/cache/apt/archives/binutils-i686-linux-gnu_2.39.90.20221231-1_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)



signature.asc
Description: PGP signature