Bug#1017113: glibc FTBFS on Alpha: segfault in setlocale
Source: glibc
Version: 2.34
Severity: important
User: debian-al...@lists.debian.org
Usertags: ftbfs
Justification: Fails to build from source but built in the past.
glibc 2.34 FTBFS on Alpha with a segfault occuring during building
locales. From the build log:
Generating locale en_US.UTF-8: this might take a while...
../localedata/gen-locale.sh: line 29: 12551 Segmentation fault
${localedef_before_env} ${run_program_env} I18NPATH=../localedata
${localedef_after_env} $flags -f $charmap -i $input
${common_objpfx}localedata/$out
Charmap: "UTF-8" Inputfile: "en_US" Outputdir: "en_US.UTF-8" failed
/bin/bash: line 4:
/<>/build-tree/alpha-libc/localedata/en_US.UTF-8/LC_CTYPE.test-result:
No such file or directory
make[3]: *** [../gen-locales.mk:17:
/<>/build-tree/alpha-libc/localedata/en_US.UTF-8/LC_CTYPE] Error 1
make[3]: Leaving directory '/<>/iconv'
In the build directory I reran ./debian/rule build-arch to get a
coredump. Debugging reports:
(sid)mjc@alpha:glibc-2.34$ gdb build-tree/alpha-libc/elf/ld.so
iconv/core-23033-\!build\!glibc-hXmOs0\!glibc-2.34\!build-tree\!alpha-libc\!elf\!ld.so
GNU gdb (Debian 12.1-3) 12.1
Copyright (C) 2022 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Type "show copying" and "show warranty" for details.
This GDB was configured as "alpha-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
Bug#939904: Temporary network disruption during upgrade
Dear developers, I just upgraded a sid system and I noticed that the network was broken on this machine. I suppose the reason is that I had systemd-resolved enabled and /etc/resolv.conf was symlinked to the stub resolver (/run/systemd/resolve/stub-resolv.conf), and since the systemd-resolved service had disappeared and didn't respond anymore on 127.0.0.53, the system was left with a broken DNS resolution. On a side note, the changelog says that an entry was added in NEWS.Debian to warn user of the change, but it wasn't displayed during the upgrade (this is weird, I know). I had to read the changelog to understand what was going on. And finally, my opinion: After reading the mail thread in this bug report, I thought the plan was to separate systemd-resolvconf (as Arch did, IIUC), not the entire systemd-resolved service. IMHO this is a **very** bad idea, and not only because of the broken DNS resolution broken after the upgrade in some cases... The whole point of systemd-resolved is that it's included in systemd (so basically in every Linux system nowadays) and, alongside systemd-networkd, provides an entire network configuration/management stack, without the need to install optional packages, but most importantly, standard across all distributions (no need to learn and/or master ifupdown, sysconfig, netplan, whatever, etc). If it's not too late, I strongly suggest to reintegrate systemd-resolved in the main systemd package (as it was before), and split only systemd-resolvconf. Best regards, -- Raphaël Halimi
Bug#1017103: [Pkg-electronics-devel] Bug#1017103: Provide transition package for geda-gaf
Moritz Muehlenhoff writes: > Source: lepton-eda > Version: 1.9.18-1 > Severity: wishlist > > geda-gaf has been removed from the archive. In #1008700 it was mentioned > that lepton-eda is a sufficient replacement, so it could provide a > transition package to help existing geda-gaf users. How do you think we should implement that? I'm happy to patch the Debian packaging of lepton-eda to make something useful happen, just not sure what makes sense? Bdale signature.asc Description: PGP signature
Bug#1001214: Getting EFI Boot Guard into Debian
Am 01.08.22 um 16:34 schrieb Gylstorff Quirin: After an internal discuss I would step up as the Maintainer for efibootguard. Thanks. I have invited you to the git repo. Please change 0.12-1's changelog signature line to your Name and email and the current date so I can sponsor the package for you.
Bug#1016877: org-mode-doc: The info documentation doesn't override the version shipped with emacs
On Mon, 2022-08-08 at 18:54 -0300, David Bremner wrote: > Diane Trout writes: > > > > > Though debian-el might be a better example to follow where the info > > file > > and its dir file are added to the elpa-src directory. > > > > Although that's my doing (I think) I have to note that it makes the > info > files inaccessible to /usr/bin/info, so might not be an ideal > solution. Hmm... I think ultimately the problem was caused for me by ending up with this value for Info-directory-list "/usr/share/info/emacs" "/usr/share/info/" "/usr/share/info/") If it looked like this it probably would work correctly "/usr/share/info/" "/usr/share/info/emacs" "/usr/share/info/") I just couldn't figure out where the /usr/share/info/emacs was getting added. Diane
Bug#1017071: RFS: psi-notify/1.3.1-1 -- Alert when your machine is becoming oversaturated
On Fri, 2022-08-12 at 23:35 -0500, Michel Alexandre Salim wrote: > -O2 is baked into the Makefile. The last option should win so -O0 takes > precedence, I suppose? I can probably convince upstream to implement a > simple ./configure. Sounds right, so probably not an issue, just seemed a bit weird. > Likely, assuming things continue to work. I'll look into that. I don't know what happens when someone uses BSD make instead, that is unlikely on Linux distros but you never know :) > Right. The Debian patch is actually to disable sanitization -- upstream > enabled it for testing only in 1.3.1 which broke CI builds. Current > hypothesis is because eatmydata changes some LD_PRELOAD settings. The patch headers made it sound like you might enable it globally. eatmydata definitely sounds like it would cause this issue. -- bye, pabs https://wiki.debian.org/PaulWise signature.asc Description: This is a digitally signed message part
Bug#1017112: buster-pu: package libdatetime-timezone-perl/1:2.23-1+2022b
Package: release.debian.org
Severity: normal
Tags: buster
User: release.debian@packages.debian.org
Usertags: pu
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
After being reminded by
https://lists.debian.org/debian-project/2022/08/msg6.html
that buster is still a thing, I've now uploaded
libdatetime-timezone-perl/1:2.23-1+2022b there as well.
Copying from #1017054 (bullseye):
… updating the data to the new tzdata 2022b release via a quilt patch.
Changes (from tzdata package):
- Chile's 2022 DST start is delayed from September 4 to September 11.
- Iran plans to stop observing DST permanently, after it falls back
on 2022-09-21.
Manually stripped down debdiff attached.
Cheers,
gregor
-BEGIN PGP SIGNATURE-
iQKTBAEBCgB9FiEE0eExbpOnYKgQTYX6uzpoAYZJqgYFAmL4TulfFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEQx
RTEzMTZFOTNBNzYwQTgxMDREODVGQUJCM0E2ODAxODY0OUFBMDYACgkQuzpoAYZJ
qgZFYg/+JoPHtnhXnhpQpCe1J6npYHIaViNDHVfLqynl1uWSdrblgO0y9fzYQHnE
/bvEoTCCeoTpBA2GPnoj6umu+SJyQ+nmaA8D2gfJ4LSoAMcCDdmZj4nkPxQfyde6
rDVROqrIRQ5eHa8fJQM7EzEhYDIYe12g2BeAAoJAXDKRgW17/GdgmM7xftResGJn
FwIGt6LXqxav7aiF9G23CwRjwHsbQL+fTstJPTWaYhOtcoYfzrXYP9SPPVuxHsvK
eifhBqgbrf4ZG3Q1GVRWtRrm382la2Q7X9DZgUNzRJlWj9qRK54slzler5cI8VY4
v+9VHPaWcALpLuQ+iIpAsysRcyFLrRm71Q8iJujHTElwl2rorkYAJO3CQdikSArY
qbBXvX17kh51ZSjAf6fjEGJBWoz1uLKUFo2AvfXL/Bn8scRQSWt7u7Yl9NRuwGs9
ro/6hvDVx+E03vwPZBd9B6LWOxlECLCcacf0IwtCaA/6k9pM1QDEKnb2krXTSD4l
w6nvBg2GVL7KgQLZHh9BLaqk9a+epDeYPq6HI1O8aUJqZPOE/IRyBjSLC6KuBG/5
hsqE9GyHOZXxoGrYC9u/UasFMYKt4hp6qjTynLxOavx0G0Rnf6YScMtI7Zvq7+a+
v8RK4QTdmYBTuL228hT7tvdDMeBXrTr/9JdptHfBgyl4gaBxKMM=
=A3Jb
-END PGP SIGNATURE-
diff -Nru libdatetime-timezone-perl-2.23/debian/changelog
libdatetime-timezone-perl-2.23/debian/changelog
--- libdatetime-timezone-perl-2.23/debian/changelog 2022-03-19
15:58:02.0 +0100
+++ libdatetime-timezone-perl-2.23/debian/changelog 2022-08-14
03:15:00.0 +0200
@@ -1,3 +1,10 @@
+libdatetime-timezone-perl (1:2.23-1+2022b) buster; urgency=medium
+
+ * Update to Olson database version 2022b.
+This update includes contemporary changes for Chile and Iran.
+
+ -- gregor herrmann Sun, 14 Aug 2022 03:15:00 +0200
+
libdatetime-timezone-perl (1:2.23-1+2022a) buster; urgency=medium
* Update to Olson database version 2022a.
diff -Nru libdatetime-timezone-perl-2.23/debian/patches/olson-2022b
libdatetime-timezone-perl-2.23/debian/patches/olson-2022b
--- libdatetime-timezone-perl-2.23/debian/patches/olson-2022b 1970-01-01
01:00:00.0 +0100
+++ libdatetime-timezone-perl-2.23/debian/patches/olson-2022b 2022-08-14
03:15:00.0 +0200
@@ -0,0 +1,21549 @@
+Description: Update to Olson DB 2022b
+Origin: vendor
+Author: gregor herrmann
+Last-Update: 2022-08-14
+
+--- a/lib/DateTime/TimeZone/Africa/Abidjan.pm
b/lib/DateTime/TimeZone/Africa/Abidjan.pm
+@@ -3,7 +3,7 @@
+ # DateTime::TimeZone module distribution in the tools/ directory
+
+ #
+-# Generated from debian/tzdata/africa. Olson data version 2022a
++# Generated from debian/tzdata/africa. Olson data version 2022b
+ #
+ # Do not edit this file directly.
+ #
+@@ -43,7 +43,7 @@
+ ],
+ ];
+
+-sub olson_version {'2022a'}
++sub olson_version {'2022b'}
+
+ sub has_dst_changes {0}
+
+--- a/lib/DateTime/TimeZone/America/Santiago.pm
b/lib/DateTime/TimeZone/America/Santiago.pm
+@@ -3,7 +3,7 @@
+ # DateTime::TimeZone module distribution in the tools/ directory
+
+ #
+-# Generated from debian/tzdata/southamerica. Olson data version 2022a
++# Generated from debian/tzdata/southamerica. Olson data version 2022b
+ #
+ # Do not edit this file directly.
+ #
+@@ -196,20 +196,20 @@
+ ],
+ [
+ 61395163200, #utc_start 1946-07-15 04:00:00 (Mon)
+-61399306800, # utc_end 1946-09-01 03:00:00 (Sun)
++61399047600, # utc_end 1946-08-29 03:00:00 (Thu)
+ 61395152400, # local_start 1946-07-15 01:00:00 (Mon)
+-61399296000, #local_end 1946-09-01 00:00:00 (Sun)
++61399036800, #local_end 1946-08-29 00:00:00 (Thu)
+ -10800,
+ 1,
+ '-03',
+ ],
+ [
+-61399306800, #utc_start 1946-09-01 03:00:00 (Sun)
++61399047600, #utc_start 1946-08-29 03:00:00 (Thu)
+ 61417627200, # utc_end 1947-04-01 04:00:00 (Tue)
+-61399292400, # local_start 1946-08-31 23:00:00 (Sat)
++61399033200, # local_start 1946-08-28 23:00:00 (Wed)
+ 61417612800, #local_end 1947-04-01 00:00:00 (Tue)
+ -14400,
+-0,
++1,
+ '-04',
+ ],
+ [
+@@ -1177,17 +1177,17 @@
+ ],
+ [
+ 63784638000, #utc_start 2022-04-03 03:00:00 (Sun)
+-63797947200, # utc_end 2022-09-04 04:00:00 (Sun)
++63798552000, # utc_end 2022-09-11 04:00:00 (Sun)
+ 63784623600, # local_start 2022-04-02 23:00:00 (Sat)
+-63797932800, #local_end 2022-09-04 00:00:00 (Sun)
++63798537600, #local_end 2022-09-11 00:00:00 (Sun)
+ -14400,
+ 0,
+ '-04',
+ ],
+ [
+-63797947200, #utc_start 2022-09-04 04:00:00 (Sun)
++63798552000, #utc_start 2022-09-11
Bug#1017111: opencolorio-tools: manual page issues: errors, duplicate text
Package: opencolorio-tools Version: 2.1.2+dfsg1-1 Severity: minor Usertags: doc Several of the manual pages in opencolorio-tools 2 duplicate their documentation about usage and options. Several of the manual pages in opencolorio-tools 2 reference an "Invalid" info manual, presumably this is a mistake. $ for f in /usr/share/man/man1/ocio* ; do if man $f | grep -C2 Invalid ; then echo ; echo $f ; line ; fi ; done SEE ALSO The full documentation for Invalid is maintained as a Texinfo manual. If the info and Invalid programs are properly installed at your site, the command info Invalid should give you access to the complete manual. /usr/share/man/man1/ociobakelut.1.gz SEE ALSO The full documentation for Invalid is maintained as a Texinfo manual. If the info and Invalid programs are properly installed at your site, the command info Invalid should give you access to the complete manual. /usr/share/man/man1/ociocheck.1.gz SEE ALSO The full documentation for Invalid is maintained as a Texinfo manual. If the info and Invalid programs are properly installed at your site, the command info Invalid should give you access to the complete manual. /usr/share/man/man1/ociochecklut.1.gz SEE ALSO The full documentation for Invalid is maintained as a Texinfo manual. If the info and Invalid programs are properly installed at your site, the command info Invalid should give you access to the complete manual. /usr/share/man/man1/ociolutimage.1.gz -- bye, pabs https://wiki.debian.org/PaulWise signature.asc Description: This is a digitally signed message part
Bug#1017110: coreutils: printf 'X takes X to be a byte, not a character (and missing in manual)?
Package: coreutils Version: 8.32-4+b1 Severity: normal Dear Maintainer, Consider: -- >8 -- $ /bin/printf %d\\n \'ą /bin/printf: warning: �: character(s) following character constant have been ignored 196 $ /bin/printf %d\\n \'я /bin/printf: warning: �: character(s) following character constant have been ignored 209 -- >8 -- Compare bash: -- >8 -- $ printf %d\\n \'ą 261 $ printf %d\\n \'я 1103 -- >8 -- Compare POSIX (Issue 7): > If the leading character is a single-quote or double-quote, the value > shall be the numeric value in the underlying codeset of the character > following the single-quote or double-quote. Compare printf.1: [no data (??)] Best, наб -- System Information: Debian Release: 11.4 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable-debug'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.10.0-16-amd64 (SMP w/24 CPU threads) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_FIRMWARE_WORKAROUND, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages coreutils depends on: ii libacl1 2.2.53-10 ii libattr1 1:2.4.48-6 ii libc62.31-13+deb11u3 ii libgmp10 2:6.2.1+dfsg-1+deb11u1 ii libselinux1 3.1-3 coreutils recommends no packages. coreutils suggests no packages. -- no debconf information signature.asc Description: PGP signature
Bug#1017109: issue building the /*/devel/website/stats/*.wml files with Debian 11's wml version
Package: www.debian.org
User: www.debian@packages.debian.org
Usertag: scripts
Severity: normal
X-Debbugs-CC: a...@debian.org
Hello all
After upgrading www-master from Debian 10 buster (wml 2.12.2) to Debian
11 bullseye (wml 2.32.0), we're experiencing an issue when building the
stats files for the website:
make[4]: Entering directory
'/srv/www.debian.org/webwml/english/devel/website/stats'
wml -q -D CUR_YEAR=2022 -o UNDEFuEN:ar.en.html@g+w -D CUR_LANG=English
-D CUR_ISO_LANG=en -D CUR_LOCALE=en_US.UTF-8 -D CHARSET=utf-8 \
../../../../english/devel/website/stats/ar.wml
ePerl:Error: Perl runtime error (interpreter rc=2)
Contents of STDERR channel: -
couldn't open ./../../../../index.wml or
/srv/www.debian.org/webwml/english/devel/website/stats/../../../../index.wml:
No such file or directory
Died at /tmp/kZRxwsy3aN/wml.tmp1 line 747.
--
** WML:Break: Error in Pass 3 (rc=1).
Died at /usr/share/wml/TheWML/Frontends/Wml/Runner.pm line 402.
TheWML::Frontends::Wml::Runner::_run_pass(TheWML::Frontends::Wml::Runner=HASH(0x55c872bf8850),
3, SCALAR(0x55c8731471c8), REF(0x55c873147198), REF(0x55c8731471b0)) called at
/usr/share/wml/TheWML/Frontends/Wml/Runner.pm line 440
TheWML::Frontends::Wml::Runner::_passes_loop(TheWML::Frontends::Wml::Runner=HASH(0x55c872bf8850))
called at /usr/share/wml/TheWML/Frontends/Wml/Runner.pm line 727
TheWML::Frontends::Wml::Runner::_output_and_cleanup(TheWML::Frontends::Wml::Runner=HASH(0x55c872bf8850))
called at /usr/share/wml/TheWML/Frontends/Wml/Runner.pm line 932
TheWML::Frontends::Wml::Runner::run_with_ARGV(TheWML::Frontends::Wml::Runner=HASH(0x55c872bf8850),
HASH(0x55c872df9390)) called at /usr/bin/wml line 47
make[4]: *** [Makefile:33: ar.en.html] Error 2
make[4]: Leaving directory
'/srv/www.debian.org/webwml/english/devel/website/stats'
make[3]: [../../../Makefile.common:84: stats-install] Error 2 (ignored)
make[3]: Leaving directory
'/srv/www.debian.org/webwml/english/devel/website'
The error happens with all the files in the "stats" folder, in all the
languages.
I have checked that the source wml files (created with the script
stattrans.pl) are similar with buster and bullseye. It seems the problem
is in how the file is referenced when passed to wml: if I try to build
the file like this:
wml -q -D CUR_YEAR=2022 -o UNDEFuEN:ar.en.html@g+w -D CUR_LANG=English
-D CUR_ISO_LANG=en -D CUR_LOCALE=en_US.UTF-8 -D CHARSET=utf-8 ar.wml
then it builds fine. If I try
wml -q -D CUR_YEAR=2022 -o UNDEFuEN:ar.en.html@g+w -D CUR_LANG=English
-D CUR_ISO_LANG=en -D CUR_LOCALE=en_US.UTF-8 -D CHARSET=utf-8
../stats/ar.wml
again it builds fine, the same with
../../../devel/website/stats/ar.wml but it fails when the file is
referenced as "../../../../english/devel/website/stats/ar.wml"
I am not sure if this happens because with that path are two .wmlrc
files involved, or because the new wml version is buggy about how it
handles long relative paths.
For now, I suggest to workaround the issue changing the corresponding
line in the english/devel/website/stats/Makefile:
-%.$(LANGUAGE).html: $(ENGLISHDIR)/$(CUR_DIR)/%.wml
$(LOCALEDIR)/stats.mo | $(VCSREVCACHE)
+%.$(LANGUAGE).html: %.wml $(LOCALEDIR)/stats.mo | $(VCSREVCACHE)
then the English folders builds fine, but we would need to create
symbolic links in the other languages /devel/website/stats, in a similar
way as it was done with the sitemap.wml in bug #924172, so they can be
built too. I don't know how to do this, though, I've added this code to
/english/devel/website/stats/Makefile:
ifneq "$(LANGUAGE)" "en"
%.wml:
$(shell ln -s $(ENGLISHDIR)/$(CUR_DIR)/*.wml .)
endif
prior to the %.$(LANGUAGE).html recipe, and it seems it works for all
languages except Chinese (variants):
wml -q -D CUR_YEAR=2022 -O1 -o
UNDEFuZH@uCNuCNHKuCNTW:ar.zh-cn.html.tmp@g+w -o
UNDEFuZH@uHKuCNHKuHKTWuTWHK:ar.zh-hk.html.tmp@g+w -o
UNDEFuZH@uTWuCNTWuHKTWuTWHK:ar.zh-t
w.html.tmp@g+w --prolog=../../../bin/format_zh.pl
--epilog=../../../bin/strip_initial_blank_line.sh -D CUR_LANG=Chinese -D
CUR_ISO_LANG=zh -D CUR_LOCALE=zh_CN.UTF-8 -D
CHARSET=UTF-8 \
ar.wml
Can't call method "Clone" on an undefined value at
/usr/share/wml/SliceTermParser.pm line 285.
SliceTermParser::__ANON__(TheWML::Backends::Slice::Main=HASH(0x564e54d0cec8),
HASH(0x564e54d0cf88)) called at /usr/share/wml/TheWML/Backends/Slice/Main.pm
line
600
TheWML::Backends::Slice::Main::pass3(TheWML::Backends::Slice::Main=HASH(0x564e54d0cec8))
called at /usr/share/wml/TheWML/Backends/Slice/Main.pm line 650
TheWML::Backends::Slice::Main::main(TheWML::Backends::Slice::Main=HASH(0x564e54d0cec8))
called at /usr/share/wml/TheWML/Frontends/Wml/PassesManager.pm line 291
TheWML::Frontends::Wml::PassesManager::__ANON__("-o",
"UNDEFuZH\@uCNuCNHKuCNTW:ar.zh-cn.html.tmp\@g+w", "-o",
"UNDEFuZH\@uHKuCNHKuHKTWuTWHK:ar.zh-hk.html.tmp\@
g+w", "-o",
Bug#1016524: openjdk-11 does not recognize cgroups2 in docker containers
Hello Karol, On Tue, Aug 02, 2022 at 09:29:36AM +, Swiderski, Karol wrote: > Package: openjdk-11 > Version: 11.0.15+10-1~deb11u1 > Severity: important > Tags: upstream > > Dear Maintainer, > > Openjdk 11 does not recognize cgroups2, which is the default for debian > bullseye. This is fixed in openjdk 11.0.16, see > https://bugs.openjdk.org/browse/JDK-8230305 11.0.16+8-1~deb11u1 has been uploaded to stable-proposed-updates [1]. You can enable proposed-updates following these instructions [2]. Does that address your use case with cgroups2? Cheers, tony [1] https://tracker.debian.org/news/1349552/accepted-openjdk-11-110168-1deb11u1-source-into-proposed-updates-stable-new-proposed-updates/ [2] https://www.debian.org/releases/proposed-updates signature.asc Description: PGP signature
Bug#1017108: ffmpeg: FTBFS on !linux-any
Package: ffmpeg Version: 7:5.0.1-3+b1 Severity: important Tags: patch Hello, ffmpeg currently fails to build on non-linux because vulkan and placebo are basically linux-only atm. The attached patch fixes this, could you apply it? Thanks, Samuel -- System Information: Debian Release: bookworm/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable-debug'), (500, 'testing-debug'), (500, 'stable-security'), (500, 'stable-debug'), (500, 'proposed-updates-debug'), (500, 'proposed-updates'), (500, 'oldstable-proposed-updates-debug'), (500, 'oldstable-proposed-updates'), (500, 'oldoldstable'), (500, 'buildd-unstable'), (500, 'unstable'), (500, 'stable'), (500, 'oldstable'), (1, 'experimental-debug'), (1, 'buildd-experimental'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386, arm64 Kernel: Linux 5.19.0 (SMP w/8 CPU threads; PREEMPT) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages ffmpeg depends on: ii libavcodec597:5.0.1-3+b1 ii libavdevice59 7:5.0.1-3+b1 ii libavfilter87:5.0.1-3+b1 ii libavformat59 7:5.0.1-3+b1 ii libavutil57 7:5.0.1-3+b1 ii libc6 2.33-8 ii libpostproc56 7:5.0.1-3+b1 ii libsdl2-2.0-0 2.0.22+dfsg-6 ii libswresample4 7:5.0.1-3+b1 ii libswscale6 7:5.0.1-3+b1 ffmpeg recommends no packages. Versions of packages ffmpeg suggests: pn ffmpeg-doc -- no debconf information -- Samuel --- Pour une évaluation indépendante, transparente et rigoureuse ! Je soutiens la Commission d'Évaluation de l'Inria. --- debian/control.original 2022-08-13 20:05:10.0 + +++ debian/control 2022-08-13 20:13:21.0 + @@ -106,7 +106,7 @@ # --enable-libopus libopus-dev, # --enable-libplacebo - libplacebo-dev (>= 4.192) , + libplacebo-dev (>= 4.192) [linux-any] , # --enable-pocketsphinx libpocketsphinx-dev (>= 0.8+5prealpha+1-7~) [!alpha !hppa !ia64 !m68k !mipsel !mips64el !powerpc !ppc64 !s390x !sparc64], # --enable-libpulse @@ -161,7 +161,7 @@ # --enable-libvpx libvpx-dev, # autodetected: vulkan - libvulkan-dev, + libvulkan-dev [linux-any], # --enable-libwebp libwebp-dev, # --enable-libx264 --- debian/rules.original 2022-08-13 20:07:11.0 + +++ debian/rules2022-08-13 20:07:32.0 + @@ -155,8 +155,12 @@ CONFIG += \ --enable-chromaprint \ --enable-frei0r \ - --enable-libplacebo \ --enable-libx264 + ifeq (linux,$(DEB_HOST_ARCH_OS)) + CONFIG += --enable-libplacebo + else + CONFIG += --disable-libplacebo + endif endif # Disable altivec optimizations on powerpc, because they are not always available on this architecture.
Bug#1015167: CPU stall while running fwupdmgr
On Aug 13, Salvatore Bonaccorso wrote: > Do you still experience this problem with the latest kernel in > unstable or experimental? No, but IIRC the bug was not deterministic and a later update with the same kernel did not actually trigger it. -- ciao, Marco signature.asc Description: PGP signature
Bug#1014310: src:openjfx: fails to migrate to testing for too long: FTBFS on arm64 and armhf
Hi Paul, On Sat, Aug 13, 2022 at 09:51:03PM +0200, Paul Gevers wrote: > Hi, > > On Sun, 3 Jul 2022 21:25:49 +0200 Paul Gevers wrote: > > Your package failed to build from source on arm64 and armhf while it > > built there successfully in the past. > > I just checked to see if there would be a commit upstream to fix the FTBFS, > but it seems that upstream is active and is at release 20+1 (from 16 days > ago), but in a new place (so the debian/watch file isn't working). > > https://github.com/openjdk/jfx For JDK 11, I believe we want https://github.com/openjdk/jfx11u For JDK 17, it would be https://github.com/openjdk/jfx17u > You may want to look into this. Agreed. Java Team, should we be targeting OpenJFX 17 for bookworm, or is an updated build of OpenJFX 11 of use? signature.asc Description: PGP signature
Bug#1017107: libpmix2: dangling /usr/lib/x86_64-linux-gnu/libpmix.so.2 symlink
Package: libpmix2 Version: 4.2.0~rc1-1 Severity: critical Justification: breaks unrelated software Hi, The upload of pmix version 4.2.0~rc1-1 introduced a dangling symlink, /usr/lib/x86_64-linux-gnu/libpmix.so.2 points to pmix2/lib/libpmix.so.2.5.2 which doesn't exist anymore as it has been renamed into pmix2/lib/libpmix.so.2.6.0. This breaks unrelated software: https://buildd.debian.org/status/fetch.php?pkg=dolfin=amd64=2019.2.0%7Egit20220407.d29e24d-5%2Bnmu1=1660402579=0 https://ci.debian.net/data/autopkgtest/testing/amd64/m/mpi4py/24742525/log.gz https://ci.debian.net/data/autopkgtest/testing/amd64/o/openmpi/24742526/log.gz Regards Aurelien
Bug#1012900: fixed in bctoolbox 5.0.37-2
Hi, On Sun, 24 Jul 2022 16:04:07 + Debian FTP Masters wrote: bctoolbox (5.0.37-2) experimental; urgency=medium . * Cherry-pick upstream patch e142436 (Closes: #1012900) Can we have this fix in unstable too please? bctoolbox is a key package. Please fix RC bugs in unstable/bookworm too. Paul OpenPGP_signature Description: OpenPGP digital signature
Bug#1017106: vkd3d: build depends on strictly versioned arch:all binary of itself
Source: vkd3d Version: 1.2-13 Severity: serious Justification: ftbfs Dear maintainer, Your package currently doesn't get build on ppc64el because it build-depends on the to-be-build version of libvkd3d-headers, but the version available on ppc64el is the previously built version. Your trick seems to have worked on other architectures, but it's a race condition (and doesn't work elsewhere). I just discussed this on #debian-ftp does anybody have a clue where to look why libvkd3d-headers (arch:all) isn't available on ppc64el causing ppc64el to not build vkd3d -*- elbrus stares at https://buildd.debian.org/status/package.php?p=vkd3d because -13 is the current version on ppc64el, but it wants -14 how can this work?= it can't of course but it's an interesting idea: build-depending on itself, just another architecture sorry, I should have spotted that -*- elbrus will file a bug thx worked elsewhere dak is supposed to export only arch-all packages of the matching version. maybe this does not work always or what aka if a source got arch-any with version 1 and arch-all with version 1 and 2, only the version 1 should be available in the Packages files maybe that doesn't extend to incoming? ie there's a ~6h window where you *can* pull in the arch:all version the header dependency is !i386 !amd64 and the arm64 build picked it up from incoming right, incoming. yes that makes sense then Paul
Bug#1016937: atop: autopkgtest regression on arm64 and armhf and times out on s390x
Hi, On 13-08-2022 21:34, Marc Haber wrote: running atop from unstable also hangs: root@elbrus:~# atop ^C on zelenka, running the atop binary just works fine. Installing atop 2.7.1-2 in a DD chroot on zelenka also works fine, and the binary is ok as well. However, the chroots dont start the services though. Progress. Now, instead of killing it, I sent it to the background and when I then take it to the foreground, it works as expected. root@ci-worker-s390x-01:~# atop ^Z [1]+ Stopped atop root@ci-worker-s390x-01:~# fg atop root@ci-worker-s390x-01:~# Same with your command in the test: root@ci-worker-s390x-01:~# atop -P cpu 5 1 ^Z [1]+ Stopped atop -P cpu 5 1 root@ci-worker-s390x-01:~# fg atop -P cpu 5 1 RESET cpu ci-worker-s390x-01 1660421134 2022/08/13 16:05:34 1936023 100 0 12314475 57940088 197207 116525509 1229493 133423 982033 4278583 0 0 100 0 0 cpu ci-worker-s390x-01 1660421134 2022/08/13 16:05:34 1936023 100 1 13096470 56792358 204646 118023945 1290960 133142 321874 3737087 0 0 100 0 0 cpu ci-worker-s390x-01 1660421134 2022/08/13 16:05:34 1936023 100 2 12982530 56925413 209005 117993872 1288573 131703 322564 3746751 0 0 100 0 0 cpu ci-worker-s390x-01 1660421134 2022/08/13 16:05:34 1936023 100 3 13465982 56697100 208873 117747350 1287548 131114 322660 3739777 0 0 100 0 0 cpu ci-worker-s390x-01 1660421134 2022/08/13 16:05:34 1936023 100 4 13639265 56795653 213211 117476209 1276394 130964 321365 3747339 0 0 100 0 0 cpu ci-worker-s390x-01 1660421134 2022/08/13 16:05:34 1936023 100 5 13326756 56460169 202500 118173964 1261805 129906 322232 3723116 0 0 100 0 0 cpu ci-worker-s390x-01 1660421134 2022/08/13 16:05:34 1936023 100 6 12968736 56176871 207863 118788707 1265701 130806 329336 3732416 0 0 100 0 0 cpu ci-worker-s390x-01 1660421134 2022/08/13 16:05:34 1936023 100 7 13026985 56068710 211225 118856524 1248204 130943 321583 3736213 0 0 100 0 0 cpu ci-worker-s390x-01 1660421134 2022/08/13 16:05:34 1936023 100 8 14194105 56997563 204065 116748001 1264309 130682 320834 3740854 0 0 100 0 0 cpu ci-worker-s390x-01 1660421134 2022/08/13 16:05:34 1936023 100 9 13285438 56060337 205755 118583081 1279057 130206 323123 3733407 0 0 100 0 0 SEP Anybody any clue? Paul OpenPGP_signature Description: OpenPGP digital signature
Bug#1014310: src:openjfx: fails to migrate to testing for too long: FTBFS on arm64 and armhf
Hi, On Sun, 3 Jul 2022 21:25:49 +0200 Paul Gevers wrote: Your package failed to build from source on arm64 and armhf while it built there successfully in the past. I just checked to see if there would be a commit upstream to fix the FTBFS, but it seems that upstream is active and is at release 20+1 (from 16 days ago), but in a new place (so the debian/watch file isn't working). https://github.com/openjdk/jfx You may want to look into this. Paul OpenPGP_signature Description: OpenPGP digital signature
Bug#1013939: fixed in python-xarray 2022.06.0-3
Control: reopen -1
Hi,
On Fri, 12 Aug 2022 11:33:53 + Debian FTP Masters
wrote:
python-xarray (2022.06.0-3) unstable; urgency=medium
.
* Depend on scipy >= 1.8.1-8 for fixes. Closes: #1004869, #1013939
But the log [1] that was generated by the migration trial run has the
output below and the runs in unstable fail too (so no missing
*versioned* items).
=== FAILURES
===
___ test_weighted_operations_nonequal_coords
___
def test_weighted_operations_nonequal_coords():
# There are no weights for a == 4, so that data point is ignored.
weights = DataArray(np.random.randn(4), dims=("a",),
coords=dict(a=[0, 1, 2, 3]))
data = DataArray(np.random.randn(4), dims=("a",),
coords=dict(a=[1, 2, 3, 4]))
check_weighted_operations(data, weights, dim="a", skipna=None)
q = 0.5
result = data.weighted(weights).quantile(q, dim="a")
# Expected value computed using code from
https://aakinshin.net/posts/weighted-quantiles/ with values at a=1,2,3
expected = DataArray([0.9308707], coords={"quantile":
[q]}).squeeze()
> assert_allclose(result, expected)
E AssertionError: Left and right DataArray objects are not close
E
E Differing values:
E L
E array(0.058928)
E R
E array(0.930871)
Paul
[1]
https://ci.debian.net/data/autopkgtest/testing/amd64/p/python-xarray/24742527/log.gz
OpenPGP_signature
Description: OpenPGP digital signature
Bug#1016937: atop: autopkgtest regression on arm64 and armhf and times out on s390x
On Fri, Aug 12, 2022 at 03:02:36PM +0200, Paul Gevers wrote: > On 12-08-2022 12:23, Marc Haber wrote: > > On Thu, Aug 11, 2022 at 10:51:32PM +0200, Paul Gevers wrote: > > > On 10-08-2022 12:03, Marc Haber wrote: > > > > I tried the (dead simple)d autopkgtest on the s390s and arm64 > > > > porterboxes > > > > and it succeeded in a second's time. I have sharpened the expression > > > > that counts the CPUs in lscpu's output and hope this will fix the issue. > > > > > > ooo, CPU count. Yes, some of those archs run on hosts with lots of CPU's. > > > armhf has 160, s390x has 10. > > > > I am testing locally on amd64 with a machine with 12 CPUs. The armhf > > tests succeed (see > > https://ci.debian.net/data/autopkgtest/testing/armhf/a/atop/24578667/log.gz). > > Great, same on arm64. s390x still times out though. And I would love to know which of the two pipes hang. On zelenka, everything is just fine. > > The complete test is: > > #!/bin/bash > > > > # atop reports number of CPU and two extra lines > > ATOPSOPINION="$(atop -P cpu 5 1 | grep -vE '^(RESET|SEP)' | wc -l)" > > When I run `atop` manually (on stable), it doesn't do anything... > root@ci-worker-s390x-01:~# atop > ^C > > I started up a clean unstable lxc container and installing atop takes quite > some time between: > Created symlink /etc/systemd/system/timers.target.wants/atop-rotate.timer -> > /lib/systemd/system/atop-rotate.timer. > Created symlink /etc/systemd/system/multi-user.target.wants/atop.service -> > /lib/systemd/system/atop.service. > Created symlink /etc/systemd/system/multi-user.target.wants/atopacct.service > -> /lib/systemd/system/atopacct.service. > and > Could not execute systemctl: at /usr/bin/deb-systemd-invoke line 145. > > running atop from unstable also hangs: > root@elbrus:~# atop > ^C on zelenka, running the atop binary just works fine. Installing atop 2.7.1-2 in a DD chroot on zelenka also works fine, and the binary is ok as well. However, the chroots dont start the services though. > > There is no loop, and nothing that could fail on a big number. In my > > understanding, this could run on a box with 2000 cores and still work. > > Except, it doesn't. Seems like atop is seriously broken on s390x on the > hosts that we have. Except zelenka, the only machine that is easily accessible to me. Everything is just fine there. > > Also, the test does not time out on zelenka when manually invoked in an > > schroot (setting PATH to point to an executable atop is necessary, as it > > does not seem to be possible to install an abitrary package that is not > > in the archive. Also, the test is successful if invoked after installing > > atop 2.7.1-2 from the archive. > > Maybe we need to involve the s390x porters? I put them in CC to already draw > their attention. That's what I did yesterday. Their mailing list seems to be a cozy quiet place though. Greetings Marc -- - Marc Haber | "I don't trust Computers. They | Mailadresse im Header Leimen, Germany| lose things."Winona Ryder | Fon: *49 6224 1600402 Nordisch by Nature | How to make an American Quilt | Fax: *49 6224 1600421
Bug#1017105: virt-viewer: FTBFS on hppa - error: ‘-fstack-protector’ not supported for this target [-Werror]
Source: virt-viewer Version: 11.0-2 Severity: normal Tags: patch Dear Maintainer, Build fails here: cc -Itests/test-version-compare.p -Itests -I../tests -I. -I.. -Isrc -I../src -I/usr/include/glib-2.0 -I/usr/lib/hppa-linux-gnu/glib-2.0/include -I/usr/include/gtk-3.0 -I/usr/include/at-spi2-atk/2.0 -I/usr/include/at-spi-2.0 -I/usr/include/dbus-1.0 -I/usr/lib/hppa-linux-gnu/dbus-1.0/include -I/usr/include/gio-unix-2.0 -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/harfbuzz -I/usr/include/fribidi -I/usr/include/atk-1.0 -I/usr/include/pixman-1 -I/usr/include/uuid -I/usr/include/freetype2 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libpng16 -I/usr/include/hppa-linux-gnu -I/usr/include/libmount -I/usr/include/blkid -fdiagnostics-color=always -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -std=gnu99 -O0 -Werror -fno-common -W -Wabsolute-value -Waddress -Waddress-of-packed-member -Waggressive-loop-optimizations -Wall -Wattribute-warning -Wattributes -Wbool-compare -Wbool-operation -Wbuiltin-declaration-mismatch -Wbuiltin-macro-redefined -Wcannot-profile -Wcast-align -Wcast-align=strict -Wcast-function-type -Wchar-subscripts -Wclobbered -Wcomment -Wcomments -Wcoverage-mismatch -Wcpp -Wdangling-else -Wdate-time -Wdeprecated-declarations -Wdesignated-init -Wdouble-promotion -Wdiscarded-array-qualifiers -Wdiscarded-qualifiers -Wdiv-by-zero -Wduplicated-cond -Wduplicate-decl-specifier -Wempty-body -Wendif-labels -Wexpansion-to-defined -Wextra -Wformat-contains-nul -Wformat-extra-args -Wformat-nonliteral -Wformat-security -Wformat-y2k -Wformat-zero-length -Wframe-address -Wfree-nonheap-object -Whsa -Wif-not-aligned -Wignored-attributes -Wignored-qualifiers -Wimplicit -Wimplicit-function-declaration -Wimplicit-int -Wincompatible-pointer-types -Winit-self -Winline -Wint-conversion -Wint-in-bool-context -Wint-to-pointer-cast -Winvalid-memory-model -Winvalid-pch -Wlogical-not-parentheses -Wlogical-op -Wmain -Wmaybe-uninitialized -Wmemset-elt-size -Wmemset-transposed-args -Wmisleading-indentation -Wmissing-attributes -Wmissing-braces -Wmissing-declarations -Wmissing-field-initializers -Wmissing-include-dirs -Wmissing-parameter-type -Wmissing-profile -Wmissing-prototypes -Wmultichar -Wmultistatement-macros -Wnarrowing -Wnested-externs -Wnonnull -Wnonnull-compare -Wnull-dereference -Wodr -Wold-style-declaration -Wold-style-definition -Wopenmp-simd -Woverflow -Woverride-init -Wpacked-bitfield-compat -Wpacked-not-aligned -Wparentheses -Wpointer-arith -Wpointer-compare -Wpointer-sign -Wpointer-to-int-cast -Wpragmas -Wpsabi -Wrestrict -Wreturn-local-addr -Wreturn-type -Wscalar-storage-order -Wsequence-point -Wshadow -Wshift-count-negative -Wshift-count-overflow -Wshift-negative-value -Wsizeof-array-argument -Wsizeof-pointer-div -Wsizeof-pointer-memaccess -Wstrict-aliasing -Wstrict-prototypes -Wstringop-truncation -Wsuggest-attribute=cold -Wsuggest-attribute=const -Wsuggest-attribute=format -Wsuggest-attribute=noreturn -Wsuggest-attribute=pure -Wsuggest-final-methods -Wsuggest-final-types -Wswitch -Wswitch-bool -Wswitch-unreachable -Wsync-nand -Wtautological-compare -Wtrampolines -Wtrigraphs -Wtype-limits -Wuninitialized -Wunknown-pragmas -Wunused -Wunused-but-set-parameter -Wunused-but-set-variable -Wunused-function -Wunused-label -Wunused-local-typedefs -Wunused-parameter -Wunused-result -Wunused-value -Wunused-variable -Wvarargs -Wvariadic-macros -Wvector-operation-performance -Wvla -Wvolatile-register-var -Wwrite-strings -Walloc-size-larger-than=2147483647 -Warray-bounds=2 -Wattribute-alias=2 -Wformat-overflow=2 -Wformat-truncation=2 -Wimplicit-fallthrough=5 -Wnormalized=nfc -Wshift-overflow=2 -Wstringop-overflow=2 -Wunused-const-variable=2 -Wno-sign-compare -Wno-cast-function-type -Wjump-misses-init -Wswitch-enum -Wno-format-nonliteral -Wno-format-truncation -Wframe-larger-than=4096 -fexceptions -fasynchronous-unwind-tables -fipa-pure-const -Wno-suggest-attribute=pure -Wno-suggest-attribute=const -fstack-protector-strong -DGLIB_VERSION_MIN_REQUIRED=GLIB_VERSION_2_48 -DGLIB_VERSION_MAX_ALLOWED=GLIB_VERSION_2_48 -DGDK_VERSION_MIN_REQUIRED=GDK_VERSION_3_18 -DGDK_VERSION_MAX_ALLOWED=GDK_VERSION_3_18 '-DLOCALE_DIR="/usr/share/locale"' -g -O2 -ffile-prefix-map=/<>=. -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIE -pthread -MD -MQ tests/test-version-compare.p/test-version-compare.c.o -MF tests/test-version-compare.p/test-version-compare.c.o.d -o tests/test-version-compare.p/test-version-compare.c.o -c ../tests/test-version-compare.c cc1: error: ‘-fstack-protector’ not supported for this target [-Werror] cc1: all warnings being treated as errors [49/83] cc -Isrc/libvirt-viewer-common.a.p -Isrc -I../src -I. -I.. -I/usr/include/libxml2 -I/usr/include/glib-2.0 -I/usr/lib/hppa-linux-gnu/glib-2.0/include -I/usr/include/gtk-3.0 -I/usr/include/at-spi2-atk/2.0 -I/usr/include/at-spi-2.0 -I/usr/include/dbus-1.0
Bug#1012774: src:git: fails to migrate to testing for too long: piuparts reports issue
Control: clone -1 -2 Control: retitle -2 during removal fails to remove /var/log/git-daemon Control: notfound -2 1:2.35.1-1 Control: reopen -2 Control: found -2 1:2.36.1-1 Hi, On Mon, 13 Jun 2022 21:22:09 +0200 Paul Gevers wrote: The excuses pages tells us that piuparts is reporting an issue with bin:git-daemon-run during removal: rmdir: failed to remove '/var/log/git-daemon': No such file or directory Unknown option: f deluser USER After the recent upload, this is still there. Paul OpenPGP_signature Description: OpenPGP digital signature
Bug#1017039: 90overlay-root vs 90dmsquash-live
> On Fri, 12 Aug 2022 00:25:27 -0400, Laszlo said: > I wanted to reach out to open a discussion about the maintenance of 90overlay-root. Nice idea, yes let;s discuss this here. > I believe that the functionality of 90overlay-root can be achieved with the 90dmsquash-live module which is available upstream - > https://github.com/dracutdevs/dracut/tree/master/modules.d/90dmsquash-live I do not know the excat function of dmsquash-live but 90overlay-root can mount a flat remote directory via NFS. Can dmsquash-live do this? Or does it only support squash file systems? -- regards Thomas
Bug#1005473: gcc-11-cross-ports: FTBFS: s-tsmona.adb:160: undefined reference to `dladdr'
Hi, On Sun, 13 Feb 2022 08:00:39 +0100 Lucas Nussbaum wrote: Source: gcc-11-cross-ports During a rebuild of all packages in sid, your package failed to build on amd64. Ping. gcc-11-cross-ports hasn't built since 1 February 2022. Paul OpenPGP_signature Description: OpenPGP digital signature
Bug#1017103: Provide transition package for geda-gaf
Source: lepton-eda Version: 1.9.18-1 Severity: wishlist geda-gaf has been removed from the archive. In #1008700 it was mentioned that lepton-eda is a sufficient replacement, so it could provide a transition package to help existing geda-gaf users. Cheers, Moritz
Bug#1010814: Re 1010814 src:faketime: fails to migrate to testing for too long: FTBFS on 32 bit architectures
Control: tag -1 pending patch Hi, I have submitted a MR: https://salsa.debian.org/debian/faketime/-/merge_requests/2 I'll upload that fix shortly to DELAYED/2. Please let me know if I should cancel or delay longer. Paul OpenPGP_signature Description: OpenPGP digital signature
Bug#1017102: ITS: libwebcam
Source: libwebcam Version: 0.2.4-1.1 Severity: important X-Debbugs-CC: pj.as...@gmail.com Tags: sid bookworm Dear package libwebcam maintainer in Debian, After looking into the package you maintain (libwebcam, https://tracker.debian.org/pkg/libwebcam), I found that this package received no maintainer updates in the past 8 years and was not in good shape. As a result, I am filing an ITS (Intent to Salvage) request against your package according to section 5.12 in Debian's Developers' Reference [1] to take over package maintenance. My current plan is to package the latest upstream release (0.2.5), fix the RC bug, clean up packaging and co-maintain this package in Debian Multimedia Team to allow possible external contribution. Please let me know whether you are still willing to maintain this package. According to the criteria listed at [2], I will upload a Non- maintainer Upload (NMU) of this package onto DELAYED/7 after 21 days (Sep. 03, 2022) to continue with the package salvaging. If you find it necessary to pause the ITS process, please let me know immediately by replying this bug report. [1] https://www.debian.org/doc/manuals/developers-reference/pkgs.en.html#package-salvaging [2] https://wiki.debian.org/PackageSalvaging -- Best Regards, Boyuan Yang signature.asc Description: This is a digitally signed message part
Bug#1016672: grub-efi-ia32-signed 1+2.06+3~deb11u1 flagged for acceptance
package release.debian.org tags 1016672 = bullseye pending thanks Hi, The upload referenced by this bug report has been flagged for acceptance into the proposed-updates queue for Debian bullseye. Thanks for your contribution! Upload details == Package: grub-efi-ia32-signed Version: 1+2.06+3~deb11u1 Explanation: new upstream release
Bug#1016672: grub-efi-amd64-signed 1+2.06+3~deb11u1 flagged for acceptance
package release.debian.org tags 1016672 = bullseye pending thanks Hi, The upload referenced by this bug report has been flagged for acceptance into the proposed-updates queue for Debian bullseye. Thanks for your contribution! Upload details == Package: grub-efi-amd64-signed Version: 1+2.06+3~deb11u1 Explanation: new upstream release
Bug#1016672: grub-efi-arm64-signed 1+2.06+3~deb11u1 flagged for acceptance
package release.debian.org tags 1016672 = bullseye pending thanks Hi, The upload referenced by this bug report has been flagged for acceptance into the proposed-updates queue for Debian bullseye. Thanks for your contribution! Upload details == Package: grub-efi-arm64-signed Version: 1+2.06+3~deb11u1 Explanation: new upstream release
Bug#981009: charybdis abandoned upstream, do not ship in bullseye
On 2022-08-02 13:46:44, Chris Hofstaedtler wrote: > * Antoine Beaupre : >> After a somewhat long period of uncertainty, Charybdis has been >> finally abandoned upstream. The official git repository here: >> >> https://github.com/charybdis-ircd/charybdis >> >> .. is marked as "archived by the owner [and] read-only". > > Is it time to file an RM bug, given that its probably going to be > solanum? Sure, feel free. -- Be yourself. Everyone else is already taken! - Oscar Wilde
Bug#1017096: libnss-systemd: postinst script creates duplicates in the /etc/nsswitch.conf
Control: clone -1 -2
Control: reassign -2 dh-nss
Control: found -2 1.4
Control: block -1 by -2
Am 13.08.22 um 17:00 schrieb Patrice Duroux:
Package: libnss-systemd
Version: 251.3-2
Severity: normal
Dear Maintainer,
After the upgrade I got:
passwd: files systemd systemd
group: files systemd systemd
shadow: files systemd
gshadow:files systemd
After clean-up, this is easy to reproduce:
dpkg-reconfigure libnss-systemd
and get:
passwd: files systemd systemd
group: files systemd systemd
shadow: files systemd systemd
gshadow:files systemd systemd
The maintainer scripts code is generated by dh-nss, thus cloning the bug
report for dh-nss.
if ! grep -q -E '^[^#:]+:.*\s(systemd|systemd|systemd|systemd)\s'
"${DPKG_ROOT}/etc/nsswitch.conf" ; then
looks suspicious.
I guess there should be separate checks for each passwd, group, shadow
and gshadow
OpenPGP_signature
Description: OpenPGP digital signature
Bug#1017100: ITP: libdatetime-format-datemanip-perl -- module to convert between Date::Manip and DateTime dates and durations
Package: wnpp Owner: gregor herrmann Severity: wishlist X-Debbugs-CC: debian-de...@lists.debian.org, debian-p...@lists.debian.org * Package name: libdatetime-format-datemanip-perl Version : 0.04 Upstream Author : Ben Bennett * URL : https://metacpan.org/release/DateTime-Format-DateManip * License : Artistic or GPL-1+ Programming Lang: Perl Description : module to convert between Date::Manip and DateTime dates and durations DateTime::Format::DateManip is a class that knows how to convert between Date::Manip dates and durations and DateTime and DateTime::Duration objects. The package will be maintained under the umbrella of the Debian Perl Group. -- Generated with the help of dpt-gen-itp(1) from pkg-perl-tools. signature.asc Description: Digital Signature
Bug#1017099: vboot-utils: Missing dependency on shflags and flashrom
Package: vboot-utils Version: 0~R99-14469.B-2 Severity: normal X-Debbugs-Cc: leon...@lausen.nl Dear Maintainer, thank you for packaging vboot-utils. It is very useful for running Debian on Chromebook hardware. Unfortunately, there are missing dependencies for the /usr/share/vboot/bin/get_gbb_flags.sh and /usr/share/vboot/bin/set_gbb_flags.sh scripts. Running either of them as currently packaged, errors out as "ERROR: Cannot find the required shflags library." To fix the problem, please package shflags from https://github.com/kward/shflags/blob/master/shflags at /usr/share/vboot/bin/lib/shflags/shflags or create a new shflags package which installs shflags to /usr/share/misc/shflags and declare a dependency. Upon locally installing shflags to /usr/share/vboot/bin/lib/shflags/shflags, running the scripts still fails "/usr/share/vboot/bin/get_gbb_flags.sh: 54: flashrom: not found". To resolve this issue, please declare a dependency on flashrom. Thank you -- System Information: Debian Release: bookworm/sid APT prefers testing-debug APT policy: (500, 'testing-debug'), (500, 'testing'), (1, 'unstable-debug'), (1, 'unstable') Architecture: arm64 (aarch64) Kernel: Linux 5.19.0-stb-cbq+ (SMP w/8 CPU threads; PREEMPT) Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages vboot-utils depends on: ii libc6 2.34-3 ii libssl3 3.0.4-2 ii vboot-kernel-utils 0~R99-14469.B-2 Versions of packages vboot-utils recommends: ii cgpt 0~R99-14469.B-2 vboot-utils suggests no packages. -- no debconf information
Bug#990372: feature-check 0.2.2-3+deb10u1 flagged for acceptance
package release.debian.org tags 990372 = buster pending thanks Hi, The upload referenced by this bug report has been flagged for acceptance into the proposed-updates queue for Debian buster. Thanks for your contribution! Upload details == Package: feature-check Version: 0.2.2-3+deb10u1 Explanation: fix some version comparisons
Bug#987538: node-end-of-stream 1.4.1-1+deb10u1 flagged for acceptance
package release.debian.org tags 987538 = buster pending thanks Hi, The upload referenced by this bug report has been flagged for acceptance into the proposed-updates queue for Debian buster. Thanks for your contribution! Upload details == Package: node-end-of-stream Version: 1.4.1-1+deb10u1 Explanation: work around test bug
Bug#987941: pacemaker 2.0.1-5+deb10u2 flagged for acceptance
package release.debian.org tags 987941 = buster pending thanks Hi, The upload referenced by this bug report has been flagged for acceptance into the proposed-updates queue for Debian buster. Thanks for your contribution! Upload details == Package: pacemaker Version: 2.0.1-5+deb10u2 Explanation: update relationship versions to fix upgrades from stretch LTS
Bug#945578: libapache2-mod-auth-openidc 2.3.10.2-1+deb10u1 flagged for acceptance
package release.debian.org tags 945578 = buster pending thanks Hi, The upload referenced by this bug report has been flagged for acceptance into the proposed-updates queue for Debian buster. Thanks for your contribution! Upload details == Package: libapache2-mod-auth-openidc Version: 2.3.10.2-1+deb10u1 Explanation: improve validation of the post-logout URL parameter on logout [CVE-2019-14857]
Bug#960396: adminer 4.7.1-1+deb10u1 flagged for acceptance
package release.debian.org tags 960396 = buster pending thanks Hi, The upload referenced by this bug report has been flagged for acceptance into the proposed-updates queue for Debian buster. Thanks for your contribution! Upload details == Package: adminer Version: 4.7.1-1+deb10u1 Explanation: fix open redirect issue, cross-site scripting issues [CVE-2020-35572 CVE-2021-29625]; elasticsearch: Do not print response if HTTP code is not 200 [CVE-2021-21311]; provide a compiled version and configuration files
Bug#1016671: grub-efi-ia32-signed 1+2.06+3~deb10u1 flagged for acceptance
package release.debian.org tags 1016671 = buster pending thanks Hi, The upload referenced by this bug report has been flagged for acceptance into the proposed-updates queue for Debian buster. Thanks for your contribution! Upload details == Package: grub-efi-ia32-signed Version: 1+2.06+3~deb10u1 Explanation: new upstream release
Bug#1016671: grub-efi-arm64-signed 1+2.06+3~deb10u1 flagged for acceptance
package release.debian.org tags 1016671 = buster pending thanks Hi, The upload referenced by this bug report has been flagged for acceptance into the proposed-updates queue for Debian buster. Thanks for your contribution! Upload details == Package: grub-efi-arm64-signed Version: 1+2.06+3~deb10u1 Explanation: new upstream release
Bug#1016671: grub-efi-amd64-signed 1+2.06+3~deb10u1 flagged for acceptance
package release.debian.org tags 1016671 = buster pending thanks Hi, The upload referenced by this bug report has been flagged for acceptance into the proposed-updates queue for Debian buster. Thanks for your contribution! Upload details == Package: grub-efi-amd64-signed Version: 1+2.06+3~deb10u1 Explanation: new upstream release
Bug#1016198: gif2apng 1.9+srconly-2+deb10u1 flagged for acceptance
package release.debian.org tags 1016198 = buster pending thanks Hi, The upload referenced by this bug report has been flagged for acceptance into the proposed-updates queue for Debian buster. Thanks for your contribution! Upload details == Package: gif2apng Version: 1.9+srconly-2+deb10u1 Explanation: fix heap-based buffer overflows [CVE-2021-45909 CVE-2021-45910 CVE-2021-45911]
Bug#1008163: node-minimist 1.2.0-1+deb10u2 flagged for acceptance
package release.debian.org tags 1008163 = buster pending thanks Hi, The upload referenced by this bug report has been flagged for acceptance into the proposed-updates queue for Debian buster. Thanks for your contribution! Upload details == Package: node-minimist Version: 1.2.0-1+deb10u2 Explanation: fix prototype pollution issue [CVE-2021-44906]
Bug#1010388: node-ejs 2.5.7-1+deb10u1 flagged for acceptance
package release.debian.org tags 1010388 = buster pending thanks Hi, The upload referenced by this bug report has been flagged for acceptance into the proposed-updates queue for Debian buster. Thanks for your contribution! Upload details == Package: node-ejs Version: 2.5.7-1+deb10u1 Explanation: sanitize options and new objects [CVE-2022-29078]
Bug#1008154: node-node-forge 0.8.1~dfsg-1+deb10u1 flagged for acceptance
package release.debian.org tags 1008154 = buster pending thanks Hi, The upload referenced by this bug report has been flagged for acceptance into the proposed-updates queue for Debian buster. Thanks for your contribution! Upload details == Package: node-node-forge Version: 0.8.1~dfsg-1+deb10u1 Explanation: fix signature verification issues [CVE-2022-24771 CVE-2022-24772 CVE-2022-24773]
Bug#1006182: qtbase-opensource-src 5.11.3+dfsg1-1+deb10u5 flagged for acceptance
package release.debian.org tags 1006182 = buster pending thanks Hi, The upload referenced by this bug report has been flagged for acceptance into the proposed-updates queue for Debian buster. Thanks for your contribution! Upload details == Package: qtbase-opensource-src Version: 5.11.3+dfsg1-1+deb10u5 Explanation: fix setTabOrder for compound widgets; add an expansion limit for XML entities [CVE-2015-9541]
Bug#1017097: debhelper: Possibility to officially support brace-expansion in config fragments?
Source: debhelper Source-Version: 13.8 Severity: wishlist Hi! In dpkg, there are the original man pages and the translated ones, which can appear and disappear on each version depending on their translation percentage. Supporting this with debhelper has been a bit of a pain over the years. Before recently, the last incarnation was using manual make rules to install these conditionally, but that started to fail with dh_missing. So, I misrecalled that this was due to a bug now fixed in debhelper and switched that to use brace expansion: dpkg commit 01e66a1a8f2d7d8023073d88b4d2b3135d7a4668 Then during the release process noticed and recalled, that while debhelper "supports" it (as in it currently works), it is not a supported feature as per the docs, see #642129. And debhelper(7): When appropriate, in cases like these, you can use standard shell wildcard characters (? and * and [..] character classes) in the files. So, while officially supporting this could be just a matter of updating that paragraph (and the lintian warning), I'm not sure you agree with that. If you do I'm happy to provide a patch, otherwise of course feel free to close the report. While I guess I could switch to use executable .manpages files (which has always seemed a bit meh to me), or try to find some other way to drive these, somehow. (I guess ideally, it would be nice for debhelper to support marking pathnames as optionally present, which could also solve this by not using brace expansion but some other means. Perhaps that would be something you might entertain instead? Again, if not please close. :) Thanks, Guillem
Bug#1017084: rust-chrono: please update to v0.4.21
Quoting Peter Green (2022-08-13 17:10:15) > On 13/08/2022 14:51, Jonas Smedegaard wrote: > > Quoting Peter Green (2022-08-13 15:33:21) > >> The new upstream version depends on the iana-time-zone crate, if/when > >> someone packages that crate and it passes trough NEW, I am happy to > >> update chrono. > > Thanks for your input, Peter. > > > > I don't really understand your last comment, however: I would expect > > that the maintainer of a package considers packaging dependencies as > > needed for maintaining the package - not just waiting idly for other to > > do so. > > Sadly there are a lot of under-maintained rust packages in Debian. > I got involved with the rust team, because the situation had > degraded to the point it was causing issues for my downstream > distribution. I fixed (and continue to fix) many issues that were > blocking up testing migration, and recently I have also been > looking at any bug reports that come in requesting new versions > of packages, or requesting that broken packages be fixed. If > said bug reports can be fixed easily I fix them, otherwise > I document what the blockers are. > > I'm reluctant to introduce new packages, because I see that > as taking long-term responsibility which I would rather > not take unless the package in question is meaningful to > me personally. Makes good sense. Thanks for your work! - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: signature
Bug#1017096: libnss-systemd: postinst script creates duplicates in the /etc/nsswitch.conf
Package: libnss-systemd Version: 251.3-2 Severity: normal Dear Maintainer, After the upgrade I got: passwd: files systemd systemd group: files systemd systemd shadow: files systemd gshadow:files systemd After clean-up, this is easy to reproduce: dpkg-reconfigure libnss-systemd and get: passwd: files systemd systemd group: files systemd systemd shadow: files systemd systemd gshadow:files systemd systemd Thanks! Patrice -- System Information: Debian Release: bookworm/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental-debug'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.18.0-4-amd64 (SMP w/12 CPU threads; PREEMPT) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages libnss-systemd depends on: ii libc62.34-3 ii systemd 251.3-2 libnss-systemd recommends no packages. libnss-systemd suggests no packages. -- no debconf information
Bug#1017084: rust-chrono: please update to v0.4.21
On 13/08/2022 14:51, Jonas Smedegaard wrote: Quoting Peter Green (2022-08-13 15:33:21) The new upstream version depends on the iana-time-zone crate, if/when someone packages that crate and it passes trough NEW, I am happy to update chrono. Thanks for your input, Peter. I don't really understand your last comment, however: I would expect that the maintainer of a package considers packaging dependencies as needed for maintaining the package - not just waiting idly for other to do so. Sadly there are a lot of under-maintained rust packages in Debian. I got involved with the rust team, because the situation had degraded to the point it was causing issues for my downstream distribution. I fixed (and continue to fix) many issues that were blocking up testing migration, and recently I have also been looking at any bug reports that come in requesting new versions of packages, or requesting that broken packages be fixed. If said bug reports can be fixed easily I fix them, otherwise I document what the blockers are. I'm reluctant to introduce new packages, because I see that as taking long-term responsibility which I would rather not take unless the package in question is meaningful to me personally.
Bug#1017095: debian-policy: Upgrade check list for 4.5.1 should use the same wording then 2.3
Package: debian-policy Version: 4.6.1.0 Severity: minor Control: tags -1 + patch Dear Maintainer, The wording of upgrade list 4.5.1 about copyright is not clear >The copyright information for files in a package must be copied verbatim into /usr/share/doc/PACKAGE/copyright when Whereas the 2.3 is clearer: >The copyright information for files in a package must be copied verbatim into /usr/share/doc/PACKAGE/copyright, *when all of the following hold*: Could you add the "all of the following hold" part ? Thanks Bastien -- System Information: Debian Release: bookworm/sid APT prefers testing APT policy: (900, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.18.0-2-rt-amd64 (SMP w/4 CPU threads; PREEMPT) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled debian-policy depends on no packages. Versions of packages debian-policy recommends: ii libjs-sphinxdoc 4.5.0-4 Versions of packages debian-policy suggests: pn doc-base -- no debconf information
Bug#1017094: false positive source-is-missing for gtk-doc generated html documentation
Package: lintian Version: 2.115.2 Severity: important lintian issues the following error for network-manager E: network-manager source: source-is-missing [docs/api/html/gdbus-org.freedesktop.NetworkManager.SecretAgent.html] E: network-manager source: source-is-missing [docs/api/html/gdbus-org.freedesktop.NetworkManager.html] E: network-manager source: source-is-missing [docs/api/html/index.html] E: network-manager source: source-is-missing [docs/api/html/ix01.html] E: network-manager source: source-is-missing [docs/api/html/nm-dbus-types.html] E: network-manager source: source-is-missing [docs/api/html/nm-settings-dbus.html] E: network-manager source: source-is-missing [docs/api/html/nm-settings-nmcli.html] E: network-manager source: source-is-missing [docs/api/html/nmcli.html] E: network-manager source: source-is-missing [docs/api/html/settings-802-11-wireless-security.html] E: network-manager source: source-is-missing [docs/api/html/settings-802-11-wireless.html] E: network-manager source: source-is-missing [docs/api/html/settings-802-1x.html] E: network-manager source: source-is-missing [docs/api/html/settings-802-3-ethernet.html] E: network-manager source: source-is-missing [docs/api/html/settings-connection.html] E: network-manager source: source-is-missing [docs/api/html/settings-hostname.html] E: network-manager source: source-is-missing [docs/api/html/settings-ipv4.html] E: network-manager source: source-is-missing [docs/api/html/settings-ipv6.html] E: network-manager source: source-is-missing [docs/api/html/settings-match.html] E: network-manager source: source-is-missing [docs/api/html/settings-sriov.html] E: network-manager source: source-is-missing [docs/api/html/settings-team-port.html] E: network-manager source: source-is-missing [docs/api/html/settings-team.html] E: network-manager source: source-is-missing [docs/api/html/settings-vlan.html] E: network-manager source: source-is-missing [docs/api/html/settings-wireguard.html] E: network-manager source: source-is-missing [docs/libnm/html/NMClient.html] E: network-manager source: source-is-missing [docs/libnm/html/NMConnection.html] While the package does ship pre-generated html files, the build is done with --enable-gtk-doc to regenerate the html. And the source files are right there: $ ls docs/api/ dbus-org.freedesktop.NetworkManager.AccessPoint.xml dbus-org.freedesktop.NetworkManager.Device.xml dbus-org.freedesktop.NetworkManager.AgentManager.xml dbus-org.freedesktop.NetworkManager.DHCP4Config.xml dbus-org.freedesktop.NetworkManager.Connection.Active.xml dbus-org.freedesktop.NetworkManager.DHCP6Config.xml dbus-org.freedesktop.NetworkManager.Device.Adsl.xml dbus-org.freedesktop.NetworkManager.DnsManager.xml dbus-org.freedesktop.NetworkManager.Device.Bluetooth.xml dbus-org.freedesktop.NetworkManager.IP4Config.xml dbus-org.freedesktop.NetworkManager.Device.Bond.xml dbus-org.freedesktop.NetworkManager.IP6Config.xml dbus-org.freedesktop.NetworkManager.Device.Bridge.xml dbus-org.freedesktop.NetworkManager.PPP.xml dbus-org.freedesktop.NetworkManager.Device.Dummy.xml dbus-org.freedesktop.NetworkManager.SecretAgent.xml dbus-org.freedesktop.NetworkManager.Device.Generic.xml dbus-org.freedesktop.NetworkManager.Settings.Connection.xml dbus-org.freedesktop.NetworkManager.Device.Infiniband.xml dbus-org.freedesktop.NetworkManager.Settings.xml dbus-org.freedesktop.NetworkManager.Device.IPTunnel.xml dbus-org.freedesktop.NetworkManager.VPN.Connection.xml dbus-org.freedesktop.NetworkManager.Device.Macsec.xml dbus-org.freedesktop.NetworkManager.VPN.Plugin.xml dbus-org.freedesktop.NetworkManager.Device.Macvlan.xml dbus-org.freedesktop.NetworkManager.xml dbus-org.freedesktop.NetworkManager.Device.Modem.xml html dbus-org.freedesktop.NetworkManager.Device.OlpcMesh.xmlMakefile.am dbus-org.freedesktop.NetworkManager.Device.Statistics.xml Makefile.in dbus-org.freedesktop.NetworkManager.Device.Team.xmlmeson.build dbus-org.freedesktop.NetworkManager.Device.Tun.xml network-manager-docs.xml dbus-org.freedesktop.NetworkManager.Device.Veth.xml NetworkManager-overrides.txt dbus-org.freedesktop.NetworkManager.Device.Vlan.xml NetworkManager-sections.txt dbus-org.freedesktop.NetworkManager.Device.Vxlan.xml settings-spec.xml dbus-org.freedesktop.NetworkManager.Device.WifiP2P.xml settings-spec.xsl dbus-org.freedesktop.NetworkManager.Device.Wired.xml version.xml dbus-org.freedesktop.NetworkManager.Device.WireGuard.xml version.xml.in dbus-org.freedesktop.NetworkManager.Device.Wireless.xml -- System Information: Debian Release: bookworm/sid APT prefers unstable APT policy: (500, 'unstable'), (200, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.18.0-4-amd64 (SMP w/4 CPU threads; PREEMPT) Kernel taint flags: TAINT_FIRMWARE_WORKAROUND Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8
Bug#1017093: nautilus-extension-gnome-console: Gets removed when upgrading gnome-console to 43~beta-1
Package: nautilus-extension-gnome-console Version: 42~beta-2 Severity: important X-Debbugs-Cc: chandru...@gmail.com Dear Maintainer, apt attempts to remove nautilus-extension-gnome-console when upgrading gnome-console pakcage to 43~beta-1. Please update this package's dependency on gnome-console. $ sudo apt upgrade gnome-console Reading package lists... Done Building dependency tree... Done Reading state information... Done Calculating upgrade... Done The following packages will be REMOVED: nautilus-extension-gnome-console The following NEW packages will be installed: libvte-2.91-gtk4-0 The following packages will be upgraded: gnome-console 1 upgraded, 1 newly installed, 1 to remove and 0 not upgraded. Need to get 927 kB of archives. After this operation, 1,250 kB of additional disk space will be used. Do you want to continue? [Y/n] n Abort. -- System Information: Debian Release: bookworm/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 5.18.0-4-amd64 (SMP w/12 CPU threads; PREEMPT) Locale: LANG=en_IN, LC_CTYPE=en_IN (charmap=UTF-8), LANGUAGE=en_IN:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages nautilus-extension-gnome-console depends on: ii gnome-console42~beta-2 ii libc62.34-3 ii libglib2.0-0 2.72.3-1+b1 ii libgtk-3-0 3.24.34-1 ii libnautilus-extension1a 42.2-1 nautilus-extension-gnome-console recommends no packages. nautilus-extension-gnome-console suggests no packages. -- no debconf information
Bug#1017092: ITP: libprometheus-tiny-shared-perl -- tiny Prometheus client with a shared database behind it
Package: wnpp Owner: Niko Tyni Severity: wishlist X-Debbugs-CC: debian-de...@lists.debian.org, debian-p...@lists.debian.org * Package name: libprometheus-tiny-shared-perl Version : 0.026 Upstream Author : Rob N ★ * URL : https://metacpan.org/release/Prometheus-Tiny-Shared * License : Artistic or GPL-1+ Programming Lang: Perl Description : tiny Prometheus client with a shared database behind it Prometheus::Tiny::Shared is a wrapper around Prometheus::Tiny that instead of storing metrics data in a hashtable, stores them in a shared datastore (provided by Hash::SharedMem, though this may change in the future). This lets you keep a single set of metrics in a multithreaded app. The package will be maintained under the umbrella of the Debian Perl Group. -- Generated with the help of dpt-gen-itp(1) from pkg-perl-tools.
Bug#1017084: rust-chrono: please update to v0.4.21
Quoting Peter Green (2022-08-13 15:33:21) > > > > ome reverse dependencies tightens dependency on chrono to v0.4.20 or > > v0.4.21, apparently related to RUSTSEC advisory 2020-0159 (bug#996913). > > As I discussed in that bug report, while I understand why rustsec > consider this a security issue (they treat all soundness bugs as security > issues) I don't think it's particularly useful to characterise it as one > downstream. > > > Please update to latest upstream release 0.4.21 to allow this security > > tightening to take effect in Debian-packaged code. > > The new upstream version depends on the iana-time-zone crate, if/when > someone packages that crate and it passes trough NEW, I am happy to > update chrono. Thanks for your input, Peter. I don't really understand your last comment, however: I would expect that the maintainer of a package considers packaging dependencies as needed for maintaining the package - not just waiting idly for other to do so. - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: signature
Bug#1017091: ITP: libhash-sharedmem-perl -- efficient shared mutable hash
Package: wnpp Owner: Niko Tyni Severity: wishlist X-Debbugs-CC: debian-de...@lists.debian.org, debian-p...@lists.debian.org * Package name: libhash-sharedmem-perl Version : 0.005 Upstream Author : Andrew Main (Zefram) * URL : https://metacpan.org/release/Hash-SharedMem * License : Artistic or GPL-1+ Programming Lang: Perl Description : efficient shared mutable hash Hash::SharedMem provides a facility for efficiently sharing mutable data between processes on one host. Data is organised as a key/value store, resembling a Perl hash. The keys and values are restricted to octet (Latin-1) strings. Structured objects may be stored by serialising them using a mechanism such as Sereal. The package will be maintained under the umbrella of the Debian Perl Group. -- Generated with the help of dpt-gen-itp(1) from pkg-perl-tools.
Bug#1015556: [Pkg-utopia-maintainers] Bug#1015556: network-manager: ftbfs with LTO (link time optimization) enabled
Control: tags -1 - moreinfo unreproducible
I looked into this a bit more and the relevant failure message appears to be
linker script "./src/libnm-client-impl/libnm.ver" contains symbols that are not exported
by library "./src/libnm-client-impl/.libs/libnm.so":
1 nm_access_point_get_last_seen@libnm_1_0_6
2 nm_device_get_metered@libnm_1_0_6
3 nm_device_wifi_request_scan_options@libnm_1_0_6
4 nm_device_wifi_request_scan_options_async@libnm_1_0_6
5 nm_ip_address_dup@libnm_1_30_8
6 nm_ip_route_dup@libnm_1_30_8
7 nm_metered_get_type@libnm_1_0_6
8 nm_setting_connection_autoconnect_slaves_get_type@libnm_1_0_4
9 nm_setting_connection_get_autoconnect_slaves@libnm_1_0_4
10 nm_setting_connection_get_mdns@libnm_1_10_14
11 nm_setting_connection_get_metered@libnm_1_0_6
12 nm_setting_connection_mdns_get_type@libnm_1_10_14
13 nm_setting_ip_config_get_dns_priority@libnm_1_2_4
14 nm_setting_ip_config_get_required_timeout@libnm_1_30_8
15 nm_setting_wired_get_wake_on_lan@libnm_1_0_6
16 nm_setting_wired_get_wake_on_lan_password@libnm_1_0_6
17 nm_setting_wired_wake_on_lan_get_type@libnm_1_0_6
18 nm_utils_enum_from_str@libnm_1_0_6
19 nm_utils_enum_to_str@libnm_1_0_6
20 nm_utils_wifi_2ghz_freqs@libnm_1_0_6
21 nm_utils_wifi_5ghz_freqs@libnm_1_0_6
make[4]: *** [Makefile:21307: check-local-exports-libnm] Error 1
Looking at the version script src/libnm-client-impl/libnm.ver [1], the
symbols not being exported in the LTO build are the following:
libnm_1_0_4 {
#nm_setting_connection_autoconnect_slaves_get_type@libnm_1_0_4;
#nm_setting_connection_get_autoconnect_slaves@libnm_1_0_4;
} libnm_1_0_0;
libnm_1_0_6 {
#nm_access_point_get_last_seen@libnm_1_0_6;
#nm_device_get_metered@libnm_1_0_6;
#nm_device_wifi_request_scan_options@libnm_1_0_6;
#nm_device_wifi_request_scan_options_async@libnm_1_0_6;
#nm_metered_get_type@libnm_1_0_6;
#nm_setting_connection_get_metered@libnm_1_0_6;
#nm_setting_wired_get_wake_on_lan@libnm_1_0_6;
#nm_setting_wired_get_wake_on_lan_password@libnm_1_0_6;
#nm_setting_wired_wake_on_lan_get_type@libnm_1_0_6;
#nm_utils_enum_from_str@libnm_1_0_6;
#nm_utils_enum_to_str@libnm_1_0_6;
#nm_utils_wifi_2ghz_freqs@libnm_1_0_6;
#nm_utils_wifi_5ghz_freqs@libnm_1_0_6;
} libnm_1_0_4;
libnm_1_2_4 {
#nm_setting_ip_config_get_dns_priority@libnm_1_2_4;
} libnm_1_2_0;
libnm_1_10_14 {
#nm_setting_connection_get_mdns@libnm_1_10_14;
#nm_setting_connection_mdns_get_type@libnm_1_10_14;
} libnm_1_10_2;
libnm_1_30_8 {
#nm_ip_address_dup@libnm_1_30_8;
#nm_ip_route_dup@libnm_1_30_8;
#nm_setting_ip_config_get_required_timeout@libnm_1_30_8;
} libnm_1_30_0;
They all have a preceeding '#'.
I've never seen this syntax before. Is this a linker/compiler bug in LTO
mode?
[1]
https://salsa.debian.org/utopia-team/network-manager/-/blob/debian/master/src/libnm-client-impl/libnm.ver
OpenPGP_signature
Description: OpenPGP digital signature
Bug#1017084: rust-chrono: please update to v0.4.21
ome reverse dependencies tightens dependency on chrono to v0.4.20 or v0.4.21, apparently related to RUSTSEC advisory 2020-0159 (bug#996913). As I discussed in that bug report, while I understand why rustsec consider this a security issue (they treat all soundness bugs as security issues) I don't think it's particularly useful to characterise it as one downstream. Please update to latest upstream release 0.4.21 to allow this security tightening to take effect in Debian-packaged code. The new upstream version depends on the iana-time-zone crate, if/when someone packages that crate and it passes trough NEW, I am happy to update chrono.
Bug#1017090: g++-12-i686-linux-gnu: Install of g++-12-i686-linux-gnu (12.1.0-7cross1) causes removal of libc6-dev:i386 (2.34-3)
Package: g++-12-i686-linux-gnu Version: 12.1.0-7cross1 Severity: important X-Debbugs-Cc: witold.bary...@gmail.com For few days now (maybe a week): On sid. $ apt install g++-12-i686-linux-gnu The following additional packages will be installed: libc6-dev-i386-cross (2.33-1cross1) libstdc++-12-dev-i386-cross (12.1.0-7cross1) Suggested packages: g++-12-multilib-i686-linux-gnu (12.1.0-7cross1) gcc-12-doc (12.1.0-1) The following packages will be REMOVED: libc6-dev:i386 (2.34-3) The following NEW packages will be installed: g++-12-i686-linux-gnu (12.1.0-7cross1) libc6-dev-i386-cross (2.33-1cross1) libstdc++-12-dev-i386-cross (12.1.0-7cross1) ... Trying to install both: $ apt install g++-12-i686-linux-gnu libc6-dev:i386 The following packages have unmet dependencies: libc6-dev:i386 : Breaks: libc6-dev-i386-cross (< 2.34~) but 2.33-1cross1 is to be installed It was working fine for years (previously with gcc 11 cross compiler), but something broke recently. Also gcc-12-i686-linux-gnu (but not g++) installs fine with libc6-dev:i386. Maybe related: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1016829 Dump of gcc stuff: $ dpkg -l | egrep 'gcc|g\+\+|libc6' ii g++ 4:12.1.0-3 amd64GNU C++ compiler ii g++-11 11.3.0-5 amd64GNU C++ compiler ii g++-11-aarch64-linux-gnu11.3.0-3cross1 amd64GNU C++ compiler (cross compiler for arm64 architecture) ii g++-11-arm-linux-gnueabihf 11.3.0-3cross1 amd64GNU C++ compiler (cross compiler for armhf architecture) ii g++-12 12.1.0-8 amd64GNU C++ compiler ii g++-12-aarch64-linux-gnu12.1.0-7cross1 amd64GNU C++ compiler (cross compiler for arm64 architecture) ii g++-12-arm-linux-gnueabihf 12.1.0-7cross1 amd64GNU C++ compiler (cross compiler for armhf architecture) ii g++-aarch64-linux-gnu 4:12.1.0-3 amd64GNU C++ compiler for the arm64 architecture ii g++-arm-linux-gnueabihf 4:12.1.0-3 amd64GNU C++ compiler for the armhf architecture ii g++-mingw-w64 10.3.0-15+24.4 all GNU C++ compiler for MinGW-w64 ii g++-mingw-w64-i686 10.3.0-15+24.4 all GNU C++ compiler for MinGW-w64 targeting Win32 ii g++-mingw-w64-i686-posix10.3.0-15+24.4 amd64GNU C++ compiler for MinGW-w64, Win32/POSIX ii g++-mingw-w64-i686-win3210.3.0-15+24.4 amd64GNU C++ compiler for MinGW-w64, Win32/Win32 ii g++-mingw-w64-x86-6410.3.0-15+24.4 all GNU C++ compiler for MinGW-w64 targeting Win64 ii g++-mingw-w64-x86-64-posix 10.3.0-15+24.4 amd64GNU C++ compiler for MinGW-w64, Win64/POSIX ii g++-mingw-w64-x86-64-win32 10.3.0-15+24.4 amd64GNU C++ compiler for MinGW-w64, Win64/Win32 ii gcc 4:12.1.0-3 amd64GNU C compiler ii gcc-10-base:amd64 10.4.0-4 amd64GCC, the GNU Compiler Collection (base package) ii gcc-11 11.3.0-5 amd64GNU C compiler ii gcc-11-aarch64-linux-gnu11.3.0-3cross1 amd64GNU C compiler (cross compiler for arm64 architecture) ii gcc-11-aarch64-linux-gnu-base:amd64 11.3.0-3cross1 amd64GCC, the GNU Compiler Collection (base package) ii gcc-11-arm-linux-gnueabihf 11.3.0-3cross1 amd64GNU C compiler (cross compiler for armhf architecture) ii gcc-11-arm-linux-gnueabihf-base:amd64 11.3.0-3cross1 amd64GCC, the GNU Compiler Collection (base package) ii gcc-11-base:amd64 11.3.0-5 amd64GCC, the GNU
Bug#1016317: linux-image-5.10.0-16-armmp: insecure W+X mapping
Control: tags -1 + moreinfo
On Fri, Jul 29, 2022 at 08:04:56PM +0200, Rainer Dorsch wrote:
> Package: src:linux
> Version: 5.10.127-2
> Severity: normal
>
> Dear Maintainer,
>
> I just noticed after booting into the kernel 5.10.0-16-armmp #1 SMP Debian
> 5.10.127-2 (2022-07-23) armv7l GNU/Linux (on a SolidRun Cubox-i with an NXP
> iMX6) that I get an
>
> insecure W+X mapping at address 0xf0879000
>
> on a serial console and a backtrace during the boot process:
>
> [5.377591] Registering SWP/SWPB emulation handler
> [5.382640] registered taskstats version 1
> [5.386784] Loading compiled-in X.509 certificates
> [5.787454] Loaded X.509 cert 'Debian Secure Boot CA:
> 6ccece7e4c6c0d1f6149f3dd27dfcc5cbb419ea1'
> [5.796311] Loaded X.509 cert 'Debian Secure Boot Signer 2021 - linux:
> 4b6ef5abca669825178e052c84667ccbc0531f8c'
> [5.806849] zswap: loaded using pool lzo/zbud
> [5.812253] Key type ._fscrypt registered
> [5.816352] Key type .fscrypt registered
> [5.820314] Key type fscrypt-provisioning registered
> [5.825722] AppArmor: AppArmor sha1 policy hashing enabled
> [5.865627] vcc_3v3: supplied by v_5v0
> [5.895845] Freeing unused kernel memory: 2048K
> [5.913843] [ cut here ]
> [5.918527] WARNING: CPU: 0 PID: 1 at arch/arm/mm/dump.c:248
> note_page+0x3d0/0x3dc
> [5.926143] arm/mm: Found insecure W+X mapping at address 0xf0879000
> [5.932529] Modules linked in:
> [5.935629] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 5.10.0-16-armmp #1
> Debian 5.10.127-2
> [5.943912] Hardware name: Freescale i.MX6 Quad/DualLite (Device Tree)
> [5.950457] Backtrace:
> [5.952938] [] (dump_backtrace) from []
> (show_stack+0x20/0x24)
> [5.960532] r7:00f8 r6:6013 r5: r4:c14cdda8
> [5.966215] [] (show_stack) from []
> (dump_stack+0xc8/0xdc)
> [5.973469] [] (dump_stack) from [] (__warn+0xfc/0x158)
> [5.980449] r7:00f8 r6:0009 r5:c031fa38 r4:c0fbe5c8
> [5.986130] [] (__warn) from []
> (warn_slowpath_fmt+0xa4/0xe4)
> [5.993633] r7:c031fa38 r6:00f8 r5:c0fbe5c8 r4:c0fbe594
> [5.999311] [] (warn_slowpath_fmt) from []
> (note_page+0x3d0/0x3dc)
> [6.007251] r8: r7: r6:0005 r5:c140c4e0 r4:c197ff28
> [6.013971] [] (note_page) from []
> (walk_pmd+0xe8/0x1a4)
> [6.021042] r10:c197ff28 r9:c0207c20 r8:c1900800 r7: r6:c0fbe610
> r5:f087b000
> [6.02] r4:c19001ec
> [6.031437] [] (walk_pmd) from []
> (ptdump_check_wx+0x88/0x104)
> [6.039030] r10: r9: r8: r7: r6:c0208000
> r5:f080
> [6.046878] r4:c0207c28
> [6.049435] [] (ptdump_check_wx) from []
> (mark_rodata_ro+0x3c/0x40)
> [6.057459] r6: r5:c0d092cc r4:
> [6.062103] [] (mark_rodata_ro) from []
> (kernel_init+0x44/0x130)
> [6.069873] [] (kernel_init) from []
> (ret_from_fork+0x14/0x2c)
> [6.077459] Exception stack(0xc197ffb0 to 0xc197fff8)
> [6.082528] ffa0:
>
> [6.090726] ffc0:
>
> [6.098924] ffe0: 0013
> [6.105553] r5:c0d092cc r4:
> [6.109187] ---[ end trace 36d095f56a800b3c ]---
> [6.114076] Checked W+X mappings: FAILED, 1 W+X pages found
> [6.119751] Run /init as init process
> [6.847313] gpio_mxc: module verification failed: signature and/or
> required
> key missing - tainting kernel
> [6.859257] vdd1p1: supplied by regulator-dummy
> [6.871900] v_usb2: supplied by v_5v0
> [6.876972] vdd3p0: supplied by regulator-dummy
> [6.882630] vdd2p5: supplied by regulator-dummy
> [6.887949] vddarm: supplied by regulator-dummy
> [6.893661] vddpu: supplied by regulator-dummy
> [6.898847] vddsoc: supplied by regulator-dummy
>
> I do not observe any functional issue so far though.
>
> Since I have not checked the output of the serial console for a while, I
> cannot tell when
> the issue started to appear.
>
> There is a similar report for the same hardware platform, but is reported on
> a 5.13 kernel:
> https://lore.kernel.org/all/yun2qpc5ibaiv...@shell.armlinux.org.uk/T/
>
> I am not sure if it was already present in 5.10, if it got backported or if
> it is
> entirely unrelated.
>
> Many thanks for the great support of many hardware platforms
Would it be possible that you try to cherry-pick upstream 4aede550f104
("ARM: imx6: mark OCRAM mapping read-only") to see if it solves the
issue?
Can you alternatively test the package from bullseye-backports which
would have the fix included and see if the issue goes away?
Regards,
Salvatore
Bug#1017089: RFP: PDF4QT -- An all in one PDF reader and editor tool.
Package: wnpp Severity: wishlist * Package name: PDF4QT Version : 1.2.1 Upstream Author : Jakub Melka * URL : https://github.com/JakubMelka/PDF4QT * License : LGPL Programming Lang: C++ Description : All in one PDF reader and editor for Qt. PDF4QT consists of a PDF rendering library, and several applications, such as advanced document viewer, command line tool, and document page manipulator application. Software is implementing PDF functionality based on PDF Reference 2.0. It is written and maintained by Jakub Melka. This one aims to do everything a PDF reader and editor should be able to do and even can read basic XFA forms unlike poppler based PDF readers. It would be wonderful to see this package in debian because now you could do anything PDF related in just one program and not have to juggle 3-4 of them to do what 1 can do. The PDF rendering is part of the program itself, so that means that you don't have to worry about poppler being updated to read a PDF better or even properly.
Bug#1003397:
Hi Iwamatsu-san,
> First, This is emedded with C4CORE.
> Do you have any plans to package this?
> https://github.com/biojppm/c4core
I filed an ITP for c4core. For details, take a look at the following.
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017088
Let's continue discussion about packaging c4core there.
Best,
Fukui
On Mon, 25 Jul 2022 06:58:22 +0900 Nobuhiro Iwamatsu
wrote:
> Hi Daichi,
>
> I reviewed your package.
>
> First, This is emedded with C4CORE.
> Do you have any plans to package this?
> https://github.com/biojppm/c4core
>
> debain/control:
> development package is required., because this is a library.
>
> debian/patches:
> Currently, this package does not have any patches. so this can delete.
>
> Best regards,
> Nobuhiro
>
> 2022年7月20日(水) 23:09 Daichi Fukui :
>
> >
> > Hello Iwamatsu-san,
> >
> > I have drafted a source package of rapidyaml and put it onto my private
repository in salsa:
> >
> > https://salsa.debian.org/dfukui/rapidyaml/-/tree/debian/0.4.1-1
> >
> > When you have time, can you review the source package and help me
upload it to the archive?
> >
> > Best regards,
> > Fukui
>
>
>
> --
> Nobuhiro Iwamatsu
>iwamatsu at {nigauri.org / debian.org}
>GPG ID: 40AD1FA6
>
>
Bug#1017088: ITP: c4core -- library of low-level C++ utilities, written with low-latency projects in mind
Package: wnpp Severity: wishlist Owner: Fukui Daichi X-Debbugs-Cc: debian-de...@lists.debian.org, a.dog.will.t...@akane.waseda.jp * Package name: c4core Version : 0.1.9 Upstream Author : Joao Paulo Magalhaes * URL : https://github.com/biojppm/c4core * License : MIT Programming Lang: C++ Description : library of low-level C++ utilities, written with low-latency projects in mind Rationale: rapidyaml [0] depends on this utility. Moreover, jsonnet [1] depends on rapidyaml. [0] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1003397 [1] https://tracker.debian.org/pkg/jsonnet Maintenance plan: Because I am a novice in debian packaging, I would like to ask for someone who can review my upload. I need a sponsor too.
Bug#1017077: sets compiler and flags wrong for armhf
Hi! I haven't looked deeply into this, bit for armhf using GDC is the intended choice - it has way fewer bugs than LDC, which generally seems to work better on 64bit architectures. That's why this was changed in the past (so at least of stuff compiles with gdc, the resulting binary will work). I'm currently traveling, so I'll look at this issue properly later. Cheers, Matthias Nilesh Patra schrieb am Sa., 13. Aug. 2022, 08:42: > Package: dh-dlang > Version: 0.6.5 > Severity: important > X-Debbugs-Cc: m...@debian.org > > Hi, > > dh-dlang seems to export flags for armhf incorrectly. ldc is > supported on armhf and hence this should be exported if available > however dh-dlang does not seem to honor that[1] > > Furthermore, it has a snippet in the same condition to set > extra DFLAGS for armhf[2] which makes it a no-op. > Similar modifications should probably be done on default-d-compiler > metapkg too. > > This was making diet-ng FTBFS for a while, so I added a workaround for > it there. > > [1]: https://sources.debian.org/src/dh-dlang/0.6.5/dlang-flags.mk/#L27 > [2]: https://sources.debian.org/src/dh-dlang/0.6.5/dlang-flags.mk/#L32 > > -- System Information: > Debian Release: bookworm/sid > APT prefers testing > APT policy: (990, 'testing'), (500, 'unstable') > Architecture: amd64 (x86_64) > > Kernel: Linux 5.18.0-3-amd64 (SMP w/8 CPU threads; PREEMPT) > Kernel taint flags: TAINT_WARN, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE > Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE > not set > Shell: /bin/sh linked to /usr/bin/dash > Init: systemd (via /run/systemd/system) > LSM: AppArmor: enabled > > Versions of packages dh-dlang depends on: > ii debhelper 13.8 > pn default-d-compiler > ii python3 3.10.5-3 > > dh-dlang recommends no packages. > > dh-dlang suggests no packages. >
Bug#1015295: linux-image-5.10.0-16-arm64: Unbootable system due to F2FS sanity_check_inode errors after upgrading kernel
Control: tags -1 + moreinfo On Tue, Jul 19, 2022 at 05:50:13AM +0200, Lukasz K. wrote: > Package: linux-image-5.10.0-16-arm64 > Severity: critical > Justification: breaks the whole system > X-Debbugs-Cc: mov...@cryptolab.net > > Dear Maintainer, > > After upgrading kernel from linux-image-5.10.0-14-arm64 to > linux-image-5.10.0-16-arm64 my system became unbootable due to F2FS > sanity_check_inode errors. > > Going back to previous kernel fixed the issue. > > This does not appear to be limited only to Debian, as could be seen in this > thread: > https://github.com/raspberrypi/linux/issues/5068 > > Error messages are (aside from different device) the same as in the linked > thread above: > [ 10.395372] F2FS-fs (mmcblk0p2): sanity_check_inode: inode (ino=85f5, > mode=33188) should not have inline_data, run fsck to fix > [...] > > I am using F2FS for my root partition with zstd compression enabled. > > Partition was created with: > mkfs.f2fs -f -O > extra_attr,inode_checksum,sb_checksum,compression,quota,encrypt DEVICE > > And is mounted with: > flush_merge,data_flush,compress_algorithm=zstd > > Compression was explicitly enabled for entire root partition during > installation > with: > mount -t f2fs -o flush_merge,data_flush,compress_algorithm=zstd DEVICE /target > chattr -R -V +c /target > > Linked thread also mentions that this was fixed upstream. The referenced commit seems to have actually landed in 5.10.127 upstream. So this probably needs more investigation. Can you for your device test upstrema kernels and test if 5.10.136 upstream fixes the issue? Can you bisect the breaking commit upstream between the two versions working in Debian and breaking? Regards, Salvatore
Bug#1014254: lintian: Please use slidding windows
Package: lintian Version: 2.115.2 Followup-For: Bug #1014254 Control: severity -1 serious Control: tags -1 security Dear Maintainer, This bug was fixed in old version of lintian (before rewrite by lechner) by using a slidding windows algorithm... Nthyhier and myself are the main author of the slidding windows and could give you some pointer. Moreover infinite recursion for regex is a security bug. Slidding windows close it by guaranted that the string parsed by the regex is limited in size. Thanks Bastien -- System Information: Debian Release: bookworm/sid APT prefers testing APT policy: (900, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.18.0-2-rt-amd64 (SMP w/4 CPU threads; PREEMPT) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages lintian depends on: ii binutils2.38.90.20220713-2 ii bzip2 1.0.8-5 ii diffstat1.64-1 ii dpkg1.21.9 ii dpkg-dev1.21.9 ii file1:5.41-4 ii gettext 0.21-6 ii gpg 2.2.35-3 ii intltool-debian 0.35.0+20060710.5 ii iso-codes 4.11.0-1 ii libapt-pkg-perl 0.1.40+b1 ii libarchive-zip-perl 1.68-1 ii libberkeleydb-perl 0.64-1+b2 ii libcapture-tiny-perl0.48-1 ii libclass-xsaccessor-perl1.19-4 ii libclone-perl 0.45-1+b2 ii libconfig-tiny-perl 2.28-1 ii libconst-fast-perl 0.014-2 ii libcpanel-json-xs-perl 4.30-1 ii libdata-dpath-perl 0.58-1 ii libdata-validate-domain-perl0.10-1.1 ii libdata-validate-uri-perl 0.07-2 ii libdevel-size-perl 0.83-2 pn libdigest-sha-perl ii libdpkg-perl1.21.9 ii libemail-address-xs-perl1.05-1 ii libencode-perl 3.19-1 ii libfile-basedir-perl0.09-1 ii libfile-find-rule-perl 0.34-2 ii libfont-ttf-perl1.06-2 ii libhtml-html5-entities-perl 0.004-2 ii libhtml-tokeparser-simple-perl 3.16-4 ii libio-interactive-perl 1.023-1 ii libipc-run3-perl0.048-2 ii libjson-maybexs-perl1.004003-1 ii liblist-compare-perl0.55-1 ii liblist-someutils-perl 0.58-1 ii liblist-utilsby-perl0.12-1 ii libmldbm-perl 2.05-3 ii libmoo-perl 2.005004-3 ii libmoox-aliases-perl0.001006-2 ii libnamespace-clean-perl 0.27-2 ii libpath-tiny-perl 0.122-1 ii libperlio-gzip-perl 0.20-1 ii libperlio-utf8-strict-perl 0.009-1+b1 ii libproc-processtable-perl 0.634-1+b1 ii libregexp-wildcards-perl1.05-3 ii libsereal-decoder-perl 4.025+ds-1 ii libsereal-encoder-perl 4.025+ds-1 ii libsort-versions-perl 1.62-2 ii libsyntax-keyword-try-perl 0.27-1 ii libterm-readkey-perl2.38-1+b3 ii libtext-levenshteinxs-perl 0.03-5 ii libtext-markdown-discount-perl 0.13-1+b1 ii libtext-xslate-perl 3.5.9-1+b1 ii libtime-duration-perl 1.21-1 ii libtime-moment-perl 0.44-1+b4 ii libtimedate-perl2.3300-2 ii libunicode-utf8-perl0.62-1+b3 ii liburi-perl 5.12-1 ii libwww-mechanize-perl 2.13-1 ii libwww-perl 6.67-1 ii libxml-libxml-perl 2.0207+dfsg+really+2.0134-1 ii libyaml-libyaml-perl0.83+ds-1+b1 ii lzip [lzip-decompressor]1.23-4 ii lzop1.04-2 ii man-db 2.10.2-1 ii patchutils 0.4.2-1 ii perl [libencode-perl] 5.34.0-5 ii t1utils 1.41-4 ii unzip 6.0-27 ii xz-utils5.2.5-2.1 lintian recommends no packages. Versions of packages lintian suggests: ii binutils-multiarch 2.38.90.20220713-2 ii libtext-template-perl 1.61-1 -- no debconf information
Bug#1017087: meson: All ldc related packages FTBFS with 0.63.1-1
Package: meson Version: 0.63.1-1 Severity: serious X-Debbugs-Cc: jpakk...@gmail.com Hi, On building any d-lang package (which uses ldc in build) with new meson, it goes FTBFS with errors similar to the one pasted below. This was working fine just minutes before (with meson 0.63.0) Tried with packages: gir-to-d, diet-ng, sambamba Seems meson is enforcing some flags? | cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 meson .. --wrap-mode=nodownload --buildtype=plain --prefix=/usr --sysconfdir=/etc --localstatedir=/var --libdir=lib/x86_64-linux-gnu | The Meson build system | Version: 0.63.1 | Source dir: /<> | Build dir: /<>/obj-x86_64-linux-gnu | Build type: native build | Project name: GIR-to-D | Project version: 0.19.1 | | ../meson.build:1:0: ERROR: Unable to detect linker for compiler `ldc2 -L=--version /tmp/tmp9o4k_f0e.d -Wl,-z,relro -O -g -release -wi --allinst` | stdout: | stderr: ldc2: Unknown command line argument '-Wl,-z,relro'. Try: 'ldc2 --help' | ldc2: Did you mean '--icp-lto'? -- System Information: Debian Release: bookworm/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 5.18.0-3-amd64 (SMP w/8 CPU threads; PREEMPT) Kernel taint flags: TAINT_WARN, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages meson depends on: pn ninja-build ii python33.10.5-3 ii python3-pkg-resources 59.6.0-1.2 ii python3-setuptools 59.6.0-1.2 Versions of packages meson recommends: ii dpkg-dev 1.21.9 meson suggests no packages.
Bug#1015167: CPU stall while running fwupdmgr
Control: tags -1 + moreinfo Hi Marco, On Sun, Jul 17, 2022 at 01:49:12AM +0200, Marco d'Itri wrote: > On Jul 17, Diederik de Haas wrote: > > > On Sunday, 17 July 2022 01:34:08 CEST Marco d'Itri wrote: > > > Source: linux > > > Version: 5.10.127-1 > > > Severity: normal > ... > > > Kernel: Linux 5.18.0-2-amd64 (SMP w/4 CPU threads; PREEMPT) > > > > Why is this bug filed against kernel version 5.10.127-1 and not 5.18.5-1? > I wondered myself, but I do not know why reportbug choose the version of > the stable package. > > ii linux-image-5.18.0-2-amd64 5.18.5-1 amd64Linux 5.18 for > 64-bit > > > 5.18.0-2-amd64 #1 SMP PREEMPT_DYNAMIC Debian 5.18.5-1 (2022-06-16) x86_64 > GNU/Linux Do you still experience this problem with the latest kernel in unstable or experimental? Regards, Salvatore
Bug#1017086: ledger: no longer reads gnucash files (regression → undead bug #740757)
Package: ledger Version: 3.2.1-7+b2 Followup-For: Bug #740757 X-Debbugs-Cc: debbug.740...@sideload.33mail.com X-Debbugs-Cc: hel...@subdivi.de Control: unarchive 740757 Control: reopen 740757 Control: found 740757 3.2.1-7+b2 Control: affects 740757 gnucash For the past ~7 or so years I have been using my own manually compiled version of ledger to escape bug# 740757: ===8<-- $ /usr/local/bin/ledger -v Ledger 2.6.2, the command-line accounting tool Copyright (c) 2003-2009, John Wiegley. All rights reserved. This program is made available under the terms of the BSD Public License. See LICENSE file included with the distribution for details and disclaimer. (modules: gmp, pcre, xml) ===8<-- This old version of ledger still works on the current stable version of gnucash (ver.4.4): ===8<-- $ /usr/local/bin/ledger --file "$datafile" --register-format '%D!!%P!!%t\n' --begin 2020/12/31 --end 2022/01/01 --sort date --display 't>0' register exp.\*cycl 2021/03/17!! derailleur + chain pliers!!$27.93 2021/04/04!! trigger shifters!!$24.99 ===8<-- But the current version of ledger (3.2.1-7+b2) does NOT operate on gnucash data: ===8<-- /usr/bin/ledger --file "$datafile" --register-format '%D!!%P!!%t\n' --begin 2020/12/31 --end 2022/01/01 --sort date --display 't>0' register exp.\*cycl While parsing file "$datafile", line 2: Error: Directive '' requires an argument While parsing file "$datafile", line 66: Error: Directive '' requires an argument … ===8<-- I don’t know if this is a regression, or if it was never actually fixed. But the current status is that it’s broken. (BTS issue) This bug is a recurrance of bug# 740757. I tried to unarchive that bug but messages to do so were sent to cont...@bugs.debian.org and they were ignored. It’s unclear why because control messages get no ack. So I was forced to open this new bug report, which is the same bug. -- System Information: Debian Release: 11.4 APT prefers stable-updates APT policy: (990, 'stable-updates'), (990, 'stable-security'), (990, 'testing'), (990, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.10.0-16-amd64 (SMP w/2 CPU threads) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages ledger depends on: ii libboost-filesystem1.74.0 1.74.0-9 ii libboost-iostreams1.74.01.74.0-9 ii libboost-python1.74.0 [libboost-python1.74.0-py39] 1.74.0-9 ii libboost-regex1.74.0 [libboost-regex1.74.0-icu67] 1.74.0-9 ii libc6 2.31-13+deb11u3 ii libgcc-s1 10.2.1-6 ii libgmp102:6.2.1+dfsg-1+deb11u1 ii libicu6767.1-7 ii libmpfr64.1.0-3 ii libpython3.93.9.2-1 ii libstdc++6 10.2.1-6 ledger recommends no packages. Versions of packages ledger suggests: pn elpa-ledger pn python3-ledger -- no debconf information
Bug#1017085: lintian: Documentation should give example for regex on overrides
Package: lintian Version: 2.115.2 Severity: minor Dear Maintainer, It will be nice if documentation give example for regex filtering. For instance I do not know if regex syntax is pcre or shell and if only * is considered as a regex -- System Information: Debian Release: bookworm/sid APT prefers testing APT policy: (900, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.18.0-2-rt-amd64 (SMP w/4 CPU threads; PREEMPT) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages lintian depends on: ii binutils2.38.90.20220713-2 ii bzip2 1.0.8-5 ii diffstat1.64-1 ii dpkg1.21.9 ii dpkg-dev1.21.9 ii file1:5.41-4 ii gettext 0.21-6 ii gpg 2.2.35-3 ii intltool-debian 0.35.0+20060710.5 ii iso-codes 4.11.0-1 ii libapt-pkg-perl 0.1.40+b1 ii libarchive-zip-perl 1.68-1 ii libberkeleydb-perl 0.64-1+b2 ii libcapture-tiny-perl0.48-1 ii libclass-xsaccessor-perl1.19-4 ii libclone-perl 0.45-1+b2 ii libconfig-tiny-perl 2.28-1 ii libconst-fast-perl 0.014-2 ii libcpanel-json-xs-perl 4.30-1 ii libdata-dpath-perl 0.58-1 ii libdata-validate-domain-perl0.10-1.1 ii libdata-validate-uri-perl 0.07-2 ii libdevel-size-perl 0.83-2 pn libdigest-sha-perl ii libdpkg-perl1.21.9 ii libemail-address-xs-perl1.05-1 ii libencode-perl 3.19-1 ii libfile-basedir-perl0.09-1 ii libfile-find-rule-perl 0.34-2 ii libfont-ttf-perl1.06-2 ii libhtml-html5-entities-perl 0.004-2 ii libhtml-tokeparser-simple-perl 3.16-4 ii libio-interactive-perl 1.023-1 ii libipc-run3-perl0.048-2 ii libjson-maybexs-perl1.004003-1 ii liblist-compare-perl0.55-1 ii liblist-someutils-perl 0.58-1 ii liblist-utilsby-perl0.12-1 ii libmldbm-perl 2.05-3 ii libmoo-perl 2.005004-3 ii libmoox-aliases-perl0.001006-2 ii libnamespace-clean-perl 0.27-2 ii libpath-tiny-perl 0.122-1 ii libperlio-gzip-perl 0.20-1 ii libperlio-utf8-strict-perl 0.009-1+b1 ii libproc-processtable-perl 0.634-1+b1 ii libregexp-wildcards-perl1.05-3 ii libsereal-decoder-perl 4.025+ds-1 ii libsereal-encoder-perl 4.025+ds-1 ii libsort-versions-perl 1.62-2 ii libsyntax-keyword-try-perl 0.27-1 ii libterm-readkey-perl2.38-1+b3 ii libtext-levenshteinxs-perl 0.03-5 ii libtext-markdown-discount-perl 0.13-1+b1 ii libtext-xslate-perl 3.5.9-1+b1 ii libtime-duration-perl 1.21-1 ii libtime-moment-perl 0.44-1+b4 ii libtimedate-perl2.3300-2 ii libunicode-utf8-perl0.62-1+b3 ii liburi-perl 5.12-1 ii libwww-mechanize-perl 2.13-1 ii libwww-perl 6.67-1 ii libxml-libxml-perl 2.0207+dfsg+really+2.0134-1 ii libyaml-libyaml-perl0.83+ds-1+b1 ii lzip [lzip-decompressor]1.23-4 ii lzop1.04-2 ii man-db 2.10.2-1 ii patchutils 0.4.2-1 ii perl [libencode-perl] 5.34.0-5 ii t1utils 1.41-4 ii unzip 6.0-27 ii xz-utils5.2.5-2.1 lintian recommends no packages. Versions of packages lintian suggests: ii binutils-multiarch 2.38.90.20220713-2 ii libtext-template-perl 1.61-1 -- no debconf information
Bug#1014793: linux-image-5.10.0-16-amd64: Kernel crashes while serving NFS
Hi Arne,
On Fri, Jul 22, 2022 at 10:18:56AM +0200, Arne Nordmark wrote:
> Den 2022-07-15 kl. 21:58, skrev Salvatore Bonaccorso:
> > I would be interested to either pinpoint the regressing commit
> > upstream beween 5.10.120 and 5.10.127 or conversely the fixing commit
> > beween 5.10.127 upstream and 5.10.130 where you are not able anymore
> > to reproduce the error. What I can say, I have already imported
> > 5.10.130 for furture upload (cf.
> > https://salsa.debian.org/kernel-team/linux/-/merge_requests/506).
>
> Bisection for the regression proved too hard.
>
> Bisection for the fix went better, I can get a crash with 5.10.128-00010 but
> not yet with 5.10.128-00011. This indicates that the fixing commit was
> probably:
>
> commit 6a0b9512a6aa7b7835d8138f5ffdcb4789c093d4
> Author: Chuck Lever
> Date: Thu Jun 30 16:48:18 2022 -0400
>
> SUNRPC: Fix READ_PLUS crasher
>
> which indeed seems to touch code involved in NFS service.
>
> Consequently, the breaking commit was probably:
>
> 6c254bf3b637 ("SUNRPC: Fix the calculation of xdr->end in
> xdr_get_next_encode_buffer()")
Thank you and apologies for the delay! The next upload for
bullseye(-security) will contain that fix and will close the bug with
that upload.
Thanks a lot for your investigtive work and bisection to the fix!
Regards,
Salvatore
Bug#1017074: ITP: libpysal -- "Core components of PySAL A library of spatial analysis functions".
Hi Nilson, [ replying via debbugs, to maintain transparency ] Quoting Nilson Silva (2022-08-13 11:53:41) > It was carelessness. I will pay more attention. No problem :-) > By the way, could you sponsor this package after it's done? Sorry, I lack the time¹ to sponsor packages. Also, I encourage you to join a team and maintain the package together with others (instead of seeking sponsorship for maintaining on your own). Looks like relevant teams include Python team or Science team. More info here: https://wiki.debian.org/Teams/#Packaging_teams Enjoy! - Jonas ¹ I have gone back to school, so homework steals a lot of my time now. -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: signature
Bug#1016974: sofia-sip: CVE-2022-31001 CVE-2022-31002 CVE-2022-31003
control -1 tags patch
Hi,
I'm not quite sure which is the preferred form to supply a patch,
so I'll attach a `git format-patch` based on my `wip/cve` branch on salsa [0].
If for further discussions should be needed before this can be uploaded
or the patch in a different form is preffered, please give me a shout.
[0] https://salsa.debian.org/devrtz/sofia-sip/-/tree/wip/cve
--
Cheers,
Evangelos
PGP: B938 6554 B7DD 266B CB8E 29A9 90F0 C9B1 8A6B 4A19
From 3687228cab738c9819bd82f6e171180e19b50c19 Mon Sep 17 00:00:00 2001
From: Evangelos Ribeiro Tzaras
Date: Sat, 13 Aug 2022 04:24:34 +0200
Subject: [PATCH 1/2] Add patches to fix reported CVEs; add copyright of
patches
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
closes: bug#1016974, thanks Moritz Mühlenhoff!
For further information see:
- CVE-2022-31001[0]:
- CVE-2022-31002[1]:
- CVE-2022-31003[2]:
[0] https://security-tracker.debian.org/tracker/CVE-2022-31001
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-31001
[1] https://security-tracker.debian.org/tracker/CVE-2022-31002
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-31002
[2] https://security-tracker.debian.org/tracker/CVE-2022-31003
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-31003
---
debian/copyright | 18
.../1003-cve-fix-oob-read-sip_method_d.patch | 28
.../1004-cve-fix-oob-read-url_canonize.patch | 45 +++
.../1005-cve-fix-heap-overflow-by-two.patch | 39
debian/patches/series | 3 ++
5 files changed, 133 insertions(+)
create mode 100644 debian/patches/1003-cve-fix-oob-read-sip_method_d.patch
create mode 100644 debian/patches/1004-cve-fix-oob-read-url_canonize.patch
create mode 100644 debian/patches/1005-cve-fix-heap-overflow-by-two.patch
diff --git a/debian/copyright b/debian/copyright
index e9c3efcf..a6b1642e 100644
--- a/debian/copyright
+++ b/debian/copyright
@@ -245,6 +245,24 @@ License-Grant:
License: GPL-3+
Reference: debian/copyright
+Files:
+ debian/patches/1003*
+ debian/patches/1004*
+ debian/patches/1005*
+Copyright:
+ 2022 Andrey Volk
+License-Grant:
+ This library is free software;
+ you can redistribute it and/or modify it
+ under the terms of the GNU Lesser General Public License
+ as published by the Free Software Foundation;
+ either version 2.1 of the License,
+ or (at your option) any later version.
+License-Grant:
+ Licensed under LGPL.
+ See file COPYING.
+License: LGPL-2.1+
+
License: BSD-3-clause
Redistribution and use in source and binary forms,
with or without modification,
diff --git a/debian/patches/1003-cve-fix-oob-read-sip_method_d.patch b/debian/patches/1003-cve-fix-oob-read-sip_method_d.patch
new file mode 100644
index ..d6e12d1d
--- /dev/null
+++ b/debian/patches/1003-cve-fix-oob-read-sip_method_d.patch
@@ -0,0 +1,28 @@
+From: Andrey Volk
+Commit: e96b4b89fc37a074bc95fc8fc24bb4b5297048ad
+Date: Mon, 18 Apr 2022 17:11:26 +0300
+Subject: Fix Out-of-bound read in sip_method_d
+
+Bug: https://security-tracker.debian.org/tracker/CVE-2022-31001
+Bug-Debian: https://bugs.debian.org/1016974
+
+Last-Update: 2022-08-13
+---
+ libsofia-sip-ua/sip/sip_parser.c | 4
+ 1 file changed, 4 insertions(+)
+
+diff --git a/libsofia-sip-ua/sip/sip_parser.c b/libsofia-sip-ua/sip/sip_parser.c
+index 3a4593d..b94be9b 100644
+--- a/libsofia-sip-ua/sip/sip_parser.c
b/libsofia-sip-ua/sip/sip_parser.c
+@@ -413,6 +413,10 @@ sip_method_t sip_method_d(char **ss, char const **return_name)
+
+ #undef MATCH
+
++ if (strlen(s) < n) {
++return sip_method_invalid;
++ }
++
+ if (IS_NON_WS(s[n]))
+ /* Unknown method */
+ code = sip_method_unknown;
diff --git a/debian/patches/1004-cve-fix-oob-read-url_canonize.patch b/debian/patches/1004-cve-fix-oob-read-url_canonize.patch
new file mode 100644
index ..46a3b030
--- /dev/null
+++ b/debian/patches/1004-cve-fix-oob-read-url_canonize.patch
@@ -0,0 +1,45 @@
+From: Andrey Volk
+Commit: 32a209f00763d4e506ed68ab68ffea3ead9cc8de
+Date: Mon, 18 Apr 2022 17:22:55 +0300
+Subject: Fix Out-of-bound read in url_canonize2 and url_canonize3
+
+Bug: https://security-tracker.debian.org/tracker/CVE-2022-31002
+Bug-Debian: https://bugs.debian.org/1016974
+
+Last-Update: 2022-08-13
+---
+ libsofia-sip-ua/url/url.c | 14 --
+ 1 file changed, 12 insertions(+), 2 deletions(-)
+
+diff --git a/libsofia-sip-ua/url/url.c b/libsofia-sip-ua/url/url.c
+index 7df6ab0..b379562 100644
+--- a/libsofia-sip-ua/url/url.c
b/libsofia-sip-ua/url/url.c
+@@ -364,7 +364,12 @@ char *url_canonize2(char *d, char const * const s, size_t n,
+ continue;
+ }
+
+-h1 = s[i + 1], h2 = s[i + 2];
++h1 = s[i + 1];
++if (!h1) {
++*d = '\0';
++return NULL;
++}
++h2 = s[i + 2];
+
+ if (!IS_HEX(h1) || !IS_HEX(h2)) {
+ *d = '\0';
+@@ -422,7 +427,12 @@ char *url_canonize3(char
Bug#1017084: rust-chrono: please update to v0.4.21
Source: rust-chrono Version: 0.4.19-3 Severity: important Tags: security upstream X-Debbugs-Cc: Debian Security Team -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 ome reverse dependencies tightens dependency on chrono to v0.4.20 or v0.4.21, apparently related to RUSTSEC advisory 2020-0159 (bug#996913). Please update to latest upstream release 0.4.21 to allow this security tightening to take effect in Debian-packaged code. - Jonas -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmL3in0ACgkQLHwxRsGg ASG4Kg//RTY+60aGPxbrlHflLrX/sBntR9QyLhuAlHJJZR4+XG1cXdEOz+Ot+Nyt di96ckZTtcrKCl6/xZI4T8hwhtm6xqF6y6vmwDfxbZnXejUPRoso+fl+Y+u1cCgj sCvZWoEDMpoI0WkY28skldBHszcPoyoichbC4IN66cmkgu6NV9IEx2tiQLsWNc3x 26BYNYAb/KypFI8XwJhZjuWPkwYVVS0wh8V0/qKGGqCoywVDzzVWkTyc4dzk2MBh /uK5XTU0WsGXU9DOjxDoaEs63L9wwQ9h49jUiRmBUyTsmkkCZB7z5kTuVrVBOzsM fEqy6V9XU7j/WdWigtHm6FZ1f23oQBWYSnppvR9xhYQRoZ4RS7Wt8CJYXyrYefVJ Ijka91l0L4LbMuyqqlgI6BbbpzrWj3EVamNOMC/qewRLbU3qWcsc/yC/jz2MzMDh LiwvVCH19c3rZKSTskt4jOQRDH1ty6MENC0VjFm+dqXuI1lQL+EUOo07o948AYdG unVhoWECvGgyFZPinKMLZJhFmcJWJUTyRr7WuOb+9ivMIf6l+yum+Kqbf74yPizM 28s2Gm0wlGl9DVhtCtNlutzvqGoMOPXLFDLvY4KbduKCE3T/jSaklCJOnNd7vZ6f bbN/E9Nw211KTMWaI/bxlW7ONw/f/RnlRSG48QpacrjS6WILd+4= =aJjV -END PGP SIGNATURE-
Bug#1017083: bibledit: Some sources are not included in your package
Source: bibledit Version: 5.0.983-1 Severity: serious Tags: upstream ftbfs security Justification: DFSG #2 X-Debbugs-Cc: Debian Security Team , debian...@lists.debian.org Dear Maintainer, Your package includes some files that seem to lack sources in preferred forms of modification: # Several minified Javascript objects are included. Upstream did this intentionally. There is several minifiers, like YUI, Uglify.JS, and others. Each of them employs their own algorithms to makes the source smaller. Upstream included the minified versions provided by the developers. This way they are more sure to have well-tested and reliable minified objects. [jquery/jquery-3.5.1.min.js] # Several minified Javascript objects are included. Upstream did this intentionally. There is several minifiers, like YUI, Uglify.JS, and others. Each of them employs their own algorithms to makes the source smaller. Upstream included the minified versions provided by the developers. This way they are more sure to have well-tested and reliable minified objects. [jquery/jquery.touchSwipe.min.js] # Several minified Javascript objects are included. Upstream did this intentionally. There is several minifiers, like YUI, Uglify.JS, and others. Each of them employs their own algorithms to makes the source smaller. Upstream included the minified versions provided by the developers. This way they are more sure to have well-tested and reliable minified objects. [nicedit/nicedit.min.js] # Several minified Javascript objects are included. Upstream did this intentionally. There is several minifiers, like YUI, Uglify.JS, and others. Each of them employs their own algorithms to makes the source smaller. Upstream included the minified versions provided by the developers. This way they are more sure to have well-tested and reliable minified objects. [notifit/notifit.min.js] # Several minified Javascript objects are included. Upstream did this intentionally. There is several minifiers, like YUI, Uglify.JS, and others. Each of them employs their own algorithms to makes the source smaller. Upstream included the minified versions provided by the developers. This way they are more sure to have well-tested and reliable minified objects. [quill/1.1.5/quill.core.js] # Several minified Javascript objects are included. Upstream did this intentionally. There is several minifiers, like YUI, Uglify.JS, and others. Each of them employs their own algorithms to makes the source smaller. Upstream included the minified versions provided by the developers. This way they are more sure to have well-tested and reliable minified objects. [quill/1.1.5/quill.js] # Several minified Javascript objects are included. Upstream did this intentionally. There is several minifiers, like YUI, Uglify.JS, and others. Each of them employs their own algorithms to makes the source smaller. Upstream included the minified versions provided by the developers. This way they are more sure to have well-tested and reliable minified objects. [quill/1.1.5/quill.min.js] # Several minified Javascript objects are included. Upstream did this intentionally. There is several minifiers, like YUI, Uglify.JS, and others. Each of them employs their own algorithms to makes the source smaller. Upstream included the minified versions provided by the developers. This way they are more sure to have well-tested and reliable minified objects. [quill/1.3.6/quill.core.js] # Several minified Javascript objects are included. Upstream did this intentionally. There is several minifiers, like YUI, Uglify.JS, and others. Each of them employs their own algorithms to makes the source smaller. Upstream included the minified versions provided by the developers. This way they are more sure to have well-tested and reliable minified objects. [quill/1.3.6/quill.js] # Several minified Javascript objects are included. Upstream did this intentionally. There is several minifiers, like YUI, Uglify.JS, and others. Each of them employs their own algorithms to makes the source smaller. Upstream included the minified versions provided by the developers. This way they are more sure to have well-tested and reliable minified objects. [quill/1.3.6/quill.min.js] # Several minified Javascript objects are included. Upstream did this intentionally. There is several minifiers, like YUI, Uglify.JS, and others. Each of them employs their own algorithms to makes the source smaller. Upstream included the minified versions provided by the developers. This way they are more sure to have well-tested and reliable minified objects. [quill/quill.core.js] # Several minified Javascript objects are included. Upstream did this intentionally. There is several minifiers, like YUI, Uglify.JS, and others. Each of them employs their own algorithms to makes the source smaller. Upstream included the minified versions provided by the
Bug#1016668: kicad-packages3d - Unreachable maintainer
Well, Am 13.08.22 um 10:56 schrieb Bastian Blank: On Sat, Aug 13, 2022 at 10:41:09AM +0200, Carsten Schoenert wrote: | Action: failed | Final-Recipient: rfc822;c.schoen...@t-online.de | Status: 5.0.0 | Remote-MTA: dns; mx02.t-online.de | Diagnostic-Code: smtp; 554 IP=194.177.211.212 - A problem occurred. (Ask your postmaster for help or to contact t...@rx.t-online.de to clarify.) this can only be some temporary problem I think. While working on various uploads for the kicad-* packagas I did receive all related information emails from DAK, except this one. Also I haven't noticed any similar problems with other uploads that did happen after the kicad-* packages. No, this is a ongoing problem. We see reject messages at the ftp-master alias quite regularly. you see more here as I'm ever possible to see. It is a known problem with your selected e-mail provider. They block at least on of the debian.org mail relays. T-Online isn't a niche provider in Germany as you for sure know. I had only few problems in the past were I was needed to go in contact with the T-Online. And maybe I had always luck then, I was getting support well and quick enough. So far my experience is quite good with T-Online. I only know of one specific email provider in France which has regularly issues delivering emails to T-Online due rejects. And only one to two times a year I hear from some own hosted foreign email domain which gets similar problems you have seen. There isn't much I can do about this, I normally don't even get noticed about such problems. It should be somehow possible for Debian to get in contact with T-Online, I can try to ask our mail systems administrators which do also encounter rejects from various other email domains and the systems they run on. Maybe they have a personal contact person. -- Regards Carsten
Bug#1015654: sambamba: ftbfs with LTO (link time optimization) enabled
Hi Matthias, On Tue, 19 Jul 2022 17:00:38 + Matthias Klose wrote: > Package: src:sambamba > > ldc2: for the --flto option: Cannot find option named 'auto'! > ldc2: Unknown command line argument '-ffat-lto-objects'. Try: 'ldc2 --help' > ldc2: Did you mean '--enable-asserts'? > ninja: build stopped: subcommand failed. I suppose this fails because ldc does not recognize 'auto' as a valid option with flto. It instead needs `full' or `thin'. It also does not seem to recognize the `-ffat-lto-objects' flag either. So probably flags should be properly passed and these bug reports should be either updated or closed for time being. There are a few more ldc-related bugs (like for mir-core) Let me know what you'd think? -- Best, Nilesh signature.asc Description: PGP signature
Bug#1004770: octave-video: Use this patch instead
Complementing my message below, the unit test in inst/VideWriter.m passed successfully when the sources were compiled against ffmpeg 4, for instance in this build: https://buildd.debian.org/status/fetch.php?pkg=octave-video=amd64=2.0.2-1%2Bb2=1650535691=0 * Rafael Laboissière [2022-08-13 10:49]: * William 'jawn-smith' Wilson [2022-08-02 17:35]: Package: octave-video Followup-For: Bug #1004770 User: ubuntu-de...@lists.ubuntu.com Usertags: origin-ubuntu kinetic ubuntu-patch Control: tags -1 patch Dear Maintainer, The first patch I submitted was a bit messy and failed to build with older versions of ffmpeg. A version with this patch has built successfully for me in Ubuntu kinetic and Debian sid. In Ubuntu, the attached patch was applied to achieve the following: * d/patches/ffmpeg5.patch: Update to FFMPEG 5 API. Thanks for considering the patch. Thank you for your patch. The package builds fine on my amd64 Debian sid system against ffmpeg 5. However, one of the unit test is failing: $ echo 'pkg load video; test VideoWriter' | octave-cli -q fatal: caught signal Segmentation fault -- stopping myself... Segmentation fault Further investigation, when running the code of the unit test by hand, shows that the problem happens in the method writeVideo of the VideoWriter class: $ octave-cli -q octave:1> pkg load video octave:2> fn = fullfile (tempdir(), "rainbow.mp4"); octave:3> width = 200; octave:4> height = 150; octave:5> nframes = 120; octave:6> p = permute (rainbow (width), [3 1 2]); octave:7> raw_video = zeros (height, width, 3, nframes); octave:8> w = VideoWriter (fn); octave:9> for k=1:nframes disp (k) ps = circshift (p, k * 6); img = uint8 (255 * repmat (ps, height, 1)); raw_video (:, :, :, k) = img; writeVideo (w, img); endfor 1 fatal: caught signal Segmentation fault -- stopping myself... Segmentation fault Ultimately, I noticed that the problem arises in the call of the function __writer_open__, defined in src/cap_ffmpeg_wrapper.cc. Do you experience the same problem in your system? Best, Rafael Laboissière
Bug#1017074: ITP: libpysal -- "Core components of PySAL A library of spatial analysis functions".
Package: wnpp Severity: wishlist Owner: Josenilson Ferreira da Silva X-Debbugs-Cc: debian-de...@lists.debian.org, nilsonfsi...@hotmail.com * Package name: libpysal Version : 4.6.2 Upstream Author : Name PySAL Developers * URL : https://github.com/pysal/libpysal/ * License : BSD 3-Clause Programming Lang: Python Description : "PySAL Core Components A library of spatial analysis functions" libpysal offers four modules that form the building blocks in many upstream packages in the PySAL family: * Spatial Weights: libpysal.weights * Input-and output: libpysal.io * Computational geometry: libpysal.cg * Built-in example datasets libpysal.examples Note: package depends in https://github.com/pysal/pysal Nilson F. Silva
Bug#1017082: neomutt: (security) The sender’s timezone is exposed in the Date: header
Package: neomutt
Version: 20201127+dfsg.1-1.2
Severity: normal
Tags: upstream
X-Debbugs-Cc: debbug.neom...@sideload.33mail.com
The “Date:” field is added after the user instructs neomutt to send
their message, so there is no opportunity for the user to edit the
timestamp of the message. Perhaps rightly so, for RFC-compliance. But
the timestamp that mutt generates exposes the timezone of the
author. It’s too much information. E.g. this reveals to the recipient
and all mail servers enroute that the sender is physically in the
central Europe timezone:
Date: Fri, 12 Aug 2022 13:21:24 +0200
This exposes the presence of senders in the eastern US timezone:
Date: Fri, 12 Aug 2022 13:21:24 -0400
It would be surprising if Google or Microsoft did not exploit that
information in some way. For privacy, users need control over the
format of that date. The RFC likely dictates the format, but the time
should be expressed in UTC. And UTC should in fact be the *default*
timezone as well.
If a user really wants to reveal the timezone they are in for some
reason (i.e. the status quo), perhaps there should be a new config
parameter for that case. The parameter could be an enum that enables
you to name a timezone, or perhaps it could be a simple boolean like
“compose_timezone_local” or “compose_timezone_zulu”.
FWIW, it’s perhaps also worth mentioning that it might be useful to be
able to dynamically select the timezone of the /recipient/, as a
courtesy to them in cases where the recipient’s timezone is known by
the sender. Of course that brings in a bit of complexity.
But in any case, the current behavior is a security issue because
confidentiality is compromized.
-- Package-specific info:
NeoMutt 20201127
Copyright (C) 1996-2020 Michael R. Elkins and others.
NeoMutt comes with ABSOLUTELY NO WARRANTY; for details type 'neomutt -vv'.
NeoMutt is free software, and you are welcome to redistribute it
under certain conditions; type 'neomutt -vv' for details.
System: Linux 5.10.0-16-amd64 (x86_64)
ncurses: ncurses 6.2.20201114 (compiled with 6.2.20201114)
libidn: 1.33 (compiled with 1.33)
GPGME: 1.14.0-unknown
GnuTLS: 3.7.1
libnotmuch: 5.3.0
storage: tokyocabinet
Configure options: --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}
{--libexecdir=${prefix}/lib/x86_64-linux-gnu} --disable-maintainer-mode
--disable-dependency-tracking --mandir=/usr/share/man --libexecdir=/usr/libexec
--with-mailpath=/var/mail --gpgme --lua --notmuch --with-ui --gnutls --gss
--idn --mixmaster --sasl --tokyocabinet --sqlite --autocrypt
Compilation CFLAGS: -g -O2
-ffile-prefix-map=/build/neomutt-aFsTyZ/neomutt-20201127+dfsg.1=.
-fstack-protector-strong -Wformat -Werror=format-security -std=c99
-D_ALL_SOURCE=1 -D_GNU_SOURCE=1 -D__EXTENSIONS__ -I/usr/include
-I/usr/include/lua5.4 -DNCURSES_WIDECHAR -isystem /usr/include/mit-krb5
Default options:
+attach_headers_color +compose_to_sender +compress +cond_date +debug
+encrypt_to_self +forgotten_attachments +forwref +ifdef +imap +index_color
+initials +limit_current_thread +multiple_fcc +nested_if +new_mail +nntp +pop
+progress +quasi_delete +regcomp +reply_with_xorig +sensible_browser +sidebar
+skip_quoted +smtp +status_color +timeout +tls_sni +trash
Compile options:
+autocrypt +bkgdset +color +curs_set +fcntl -flock -fmemopen +futimens
+getaddrinfo +gnutls +gpgme +gss +hcache -homespool +idn +inotify
-locales_hack +lua +meta +mixmaster +nls +notmuch -openssl +pgp +regex +sasl
+smime +sqlite +start_color +sun_attachment +typeahead
MAILPATH="/var/mail"
MIXMASTER="mixmaster"
PKGDATADIR="/usr/share/neomutt"
SENDMAIL="/usr/sbin/sendmail"
SYSCONFDIR="/etc"
To learn more about NeoMutt, visit: https://neomutt.org
If you find a bug in NeoMutt, please raise an issue at:
https://github.com/neomutt/neomutt/issues
or send an email to:
-- System Information:
Debian Release: 11.4
APT prefers stable-updates
APT policy: (990, 'stable-updates'), (990, 'stable-security'), (990,
'testing'), (990, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 5.10.0-16-amd64 (SMP w/2 CPU threads)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages neomutt depends on:
ii libc6 2.31-13+deb11u3
ii libgnutls30 3.7.1-5+deb11u1
ii libgpg-error0 1.38-2
ii libgpgme111.14.0-1+b2
ii libgssapi-krb5-2 1.18.3-6+deb11u1
ii libidn11 1.33-3
ii liblua5.4-0 5.4.2-2
ii libncursesw6 6.2+20201114-2
ii libnotmuch5 0.31.4-2
ii libsasl2-22.1.27+dfsg-2.1+deb11u1
ii
Bug#1016367: gnome-shell: trouble with dual VGA devices
Hi,
Just for info in case.
The story about the dual VGA devices is independent from this issue.
See a recent post at debian-user:
https://lists.debian.org/debian-user/2022/08/msg00211.html
But even after the recent update of gjs (1.73.1-2) and libmozjs91 (91.12.0-1),
the issue is still there.
Thanks,
Patrice
PID: 2005 (gnome-shell)
UID: 1001 (patrice)
GID: 1001 (patrice)
Signal: 6 (ABRT)
Timestamp: Sat 2022-08-13 11:12:50 CEST (6min ago)
Command Line: /usr/bin/gnome-shell
Executable: /usr/bin/gnome-shell
Control Group:
/user.slice/user-1001.slice/user@1001.service/session.slice/org.gnome.Shell@wayland.service
Unit: user@1001.service
User Unit: org.gnome.Shell@wayland.service
Slice: user-1001.slice
Owner UID: 1001 (patrice)
Boot ID: 5f5fc1fe0e384c72b519d76f380089b7
Machine ID: be351e757dc049ffa300ddbaf0f4856a
Hostname: kos-moceratops
Storage:
/var/lib/systemd/coredump/core.gnome-shell.1001.5f5fc1fe0e384c72b519d76f380089b7.2005.166038197000.zst
(present)
Disk Size: 13.8M
Message: Process 2005 (gnome-shell) of user 1001 dumped core.
Module linux-vdso.so.1 with build-id
c9e3a861ce407cfd2ce8f09d76cd130128ae1352
Module libpixbufloader-xpm.so with build-id
2814bfc3ede07521e51496cf7d00c9992f0022e0
Module libnss_resolve.so.2 with build-id
05797a3f932e0872bfaf0ec85a933a7a57810c93
Metadata for module libnss_resolve.so.2 owned by FDO found: {
"type" : "deb",
"os" : "debian",
"name" : "systemd",
"architecture" : "amd64",
"version" : "251.3-1",
"debugInfoUrl" : "https://debuginfod.debian.net;
}
Module libnss_mdns4_minimal.so.2 with build-id
e3453c70da826e01a6499c633b45e4bcc4984edd
Module libgiognutls.so with build-id
765823d6efb9289bd9ea23ec09d1f41027ae7dea
Module libgiognomeproxy.so with build-id
db1de6e743cc5db457df8dd9945b84ea741dc5d8
Module libgioremote-volume-monitor.so with build-id
d29c2515d256451d46705652707fb4b9b82e4b34
Module libtelepathy-logger.so.3 with build-id
9c5ee58594405138f1c5907cf075afe223f9e93b
Module libdbus-glib-1.so.2 with build-id
90430c691f4ef85d90b05889fe88a181f2fdc767
Module libtelepathy-glib.so.0 with build-id
4ceaa49f6deb2a182923892c950b3a45b152ae03
Module libcrypt.so.1 with build-id
2442239fad26c8122cf7dd8e54af2b15c7a17fa6
Module libaccountsservice.so.0 with build-id
39cf83accf4e52a9de65a52077e30f8bc0afe618
Module libtirpc.so.3 with build-id
89d6760d8f004a33b2ad80e7277842ef8f3c4a43
Module libnsl.so.2 with build-id
d7e4e187c5d3d36dc8386646d8d02910f2664a85
Module libopus.so.0 with build-id
c660cf724fd7835d53a33b5f2d494471104cb556
Module libvorbisenc.so.2 with build-id
15116f34e1cc88f88c13d4e6ce5aab9a05c2ad55
Module libFLAC.so.8 with build-id
d002f9c229612cbb6ac63c0e833401a3b63bb1fa
Module libwrap.so.0 with build-id
7d8e1fb1fcb296405159bce34a01e39141261f4e
Module libasyncns.so.0 with build-id
2f138035552f4b777ccafb65b22b5da8983ea7ac
Module libsndfile.so.1 with build-id
d9c760d5e9fb778f7b03a199d024ab496e9771a1
Module libpulsecommon-15.0.so with build-id
e4c9eb2d667fdde3e41e2c1e0e19f8ae498f16e5
Module libpulse-mainloop-glib.so.0 with build-id
613cb2b99b5cb6e2c9790f6f8e5852edfe863d5f
Module libpulse.so.0 with build-id
fcc8cf20a45efd1ceae1aeb4d9d85d4005af9417
Module libgvc.so with build-id
563078344ca491bd0567749fff122395898d487f
Module libupower-glib.so.3 with build-id
f20d66477d0eb02b5e191d2b5e465d05a8b5575b
Module libgnome-bluetooth-3.0.so.13 with build-id
39eb5f1c05f9a9da4b4de7eb8247a4824b34291b
Module libgeocode-glib.so.0 with build-id
44338f2e6b60da39428ad7d3afd9cbbbaf060670
Module libgweather-4.so.0 with build-id
b3d4b6ae225968aab7c349857c6417224d9f449e
Module librsvg-2.so.2 with build-id
b07fc77a1604a7e4083885c5cfc33e00e8b9b3ec
Module libpixbufloader-svg.so with build-id
c04d0545dd5559fc7fb1ea29dab1a6b4828fe4ab
Module libgdm.so.1 with build-id
ac70f813d47ffb1f73398a71bcac79b55d53b1f0
Module libgeoclue-2.so.0 with build-id
be26128a7113a2d4727083a3f4066c8b16686bd3
Module libmalcontent-0.so.0 with build-id
9a0afb9c624e93974f8c2162c381a98ab8a8dfae
Module libibus-1.0.so.5 with build-id
e5420e073b9ebd978422078c73d4d6812ecf53ed
Module libresolv.so.2 with build-id
Bug#987619: ITP: golang-github-dgryski-go-rendezvous -- Go implementation of rendezvous hashing
Package: wnpp Followup-For: Bug #987619 Hi, Any plans to upload this package? I am interested in this package maintenance. Best regards, Nobuhiro
Bug#1016668: kicad-packages3d - Unreachable maintainer
On Sat, Aug 13, 2022 at 10:41:09AM +0200, Carsten Schoenert wrote: > > | Action: failed > > | Final-Recipient: rfc822;c.schoen...@t-online.de > > | Status: 5.0.0 > > | Remote-MTA: dns; mx02.t-online.de > > | Diagnostic-Code: smtp; 554 IP=194.177.211.212 - A problem occurred. (Ask > > your postmaster for help or to contact t...@rx.t-online.de to clarify.) > > this can only be some temporary problem I think. > While working on various uploads for the kicad-* packagas I did receive > all related information emails from DAK, except this one. > Also I haven't noticed any similar problems with other uploads that did > happen after the kicad-* packages. No, this is a ongoing problem. We see reject messages at the ftp-master alias quite regularly. It is a known problem with your selected e-mail provider. They block at least on of the debian.org mail relays. Bastian -- We Klingons believe as you do -- the sick should die. Only the strong should live. -- Kras, "Friday's Child", stardate 3497.2
Bug#1004770: octave-video: Use this patch instead
* William 'jawn-smith' Wilson [2022-08-02 17:35]: Package: octave-video Followup-For: Bug #1004770 User: ubuntu-de...@lists.ubuntu.com Usertags: origin-ubuntu kinetic ubuntu-patch Control: tags -1 patch Dear Maintainer, The first patch I submitted was a bit messy and failed to build with older versions of ffmpeg. A version with this patch has built successfully for me in Ubuntu kinetic and Debian sid. In Ubuntu, the attached patch was applied to achieve the following: * d/patches/ffmpeg5.patch: Update to FFMPEG 5 API. Thanks for considering the patch. Thank you for your patch. The package builds fine on my amd64 Debian sid system against ffmpeg 5. However, one of the unit test is failing: $ echo 'pkg load video; test VideoWriter' | octave-cli -q fatal: caught signal Segmentation fault -- stopping myself... Segmentation fault Further investigation, when running the code of the unit test by hand, shows that the problem happens in the method writeVideo of the VideoWriter class: $ octave-cli -q octave:1> pkg load video octave:2> fn = fullfile (tempdir(), "rainbow.mp4"); octave:3> width = 200; octave:4> height = 150; octave:5> nframes = 120; octave:6> p = permute (rainbow (width), [3 1 2]); octave:7> raw_video = zeros (height, width, 3, nframes); octave:8> w = VideoWriter (fn); octave:9> for k=1:nframes disp (k) ps = circshift (p, k * 6); img = uint8 (255 * repmat (ps, height, 1)); raw_video (:, :, :, k) = img; writeVideo (w, img); endfor 1 fatal: caught signal Segmentation fault -- stopping myself... Segmentation fault Ultimately, I noticed that the problem arises in the call of the function __writer_open__, defined in src/cap_ffmpeg_wrapper.cc. Do you experience the same problem in your system? Best, Rafael Laboissière
Bug#1003165: scikit-learn testing migration
On 8/13/22 13:34, Andreas Tille wrote: The drawback of this solution is that we will not get any warning for new *potentially more important* issues since all test failures will be ignored now. For me this is outweighted by the advantage that we can present upstream a full log of all issues in certain architectures and can open according issues. I admit I'm not really enthusiastic that upstream will care much about this - but at least we have the logs at hand and can do something in case someone wants to invest time into this. Considering long term maintainance this does not seem to be nice especially keeping in mind the fact that sklearn is a key package. I think it is OK to do it _for the moment_ to allow the dust to settle a bit, and rm'ed packages to get to their destination once again but I'd suggest ``incrementally'' enabling the tests once everything is in place. I agree that upstream is probably not very enthusiastic about fixing those, but if we get fixes, we should keep propagating them. In a nutshell, IMO the sklearn revision that enters bookworm _should_ have tests enabled, without hacks and the tests that do not pass can be disabled (after all, it does not come from our end) I do not plan to close bugs #1003165 and #1008369 but I think it is appropriate to reduce its severity to important and thus enable the package and its dependencies to migrate to testing (I have not checked debci yet). Sounds good, and thanks for caring for it. [1] https://salsa.debian.org/science-team/scikit-learn/-/blob/master/debian/rules#L227 -- Best, Nilesh
Bug#1003165: scikit-learn testing migration
Hi again, Am Thu, Aug 04, 2022 at 01:25:42PM +0200 schrieb Andreas Tille: > Am Fri, Jul 29, 2022 at 06:09:26AM +0200 schrieb Andreas Tille: > Before we fall into another "do nothing" period: I will upload > scikit-learn restricted to those architectures only which have all tests > passing and will ask ftpmaster for removal of the others. If you think > this is a bad idea please give good reasons not to do so or even better > fix the package for the problematic architectures. When looking at the rules file I noticed that we currently exclude (more or less randomly) certain tests for certain architectures. So I had two options: 1. Simply add the other failing tests 2. Ignore all failures but print the failures into the build logs I decided for the latter now in scikit-learn_1.1.2+dfsg-3 and you see that the package is building now. I've added according README.Debian which are *architecture specific*[1] to inform our users about poptential issues. The drawback of this solution is that we will not get any warning for new *potentially more important* issues since all test failures will be ignored now. For me this is outweighted by the advantage that we can present upstream a full log of all issues in certain architectures and can open according issues. I admit I'm not really enthusiastic that upstream will care much about this - but at least we have the logs at hand and can do something in case someone wants to invest time into this. I do not plan to close bugs #1003165 and #1008369 but I think it is appropriate to reduce its severity to important and thus enable the package and its dependencies to migrate to testing (I have not checked debci yet). Any comments about this strategy? Kind regards Andreas. [1] https://salsa.debian.org/science-team/scikit-learn/-/blob/master/debian/rules#L227 -- http://fam-tille.de
Bug#1017081: lintian: warn about paths in /usr/share/applications/ not named *.desktop or *-mimeapps.list
Package: lintian Version: 2.115.2 Severity: wishlist There are a couple of packages shipping files in the directory /usr/share/applications/ that are not applications or MIME lists. $ apt-file search /usr/share/applications/ | grep -vE ': /usr/share/applications/[^/]+(\.desktop|-mimeapps\.list)$' fte-xwindow: /usr/share/applications/fte32x32.xpm spread-phy: /usr/share/applications/desktop The icon should be in /usr/share/pixmaps/ or /usr/share/icons/ dirs, since its filename and contents both indicate it is an image. The desktop file should be renamed to spread-phy.desktop or similar, since its file contents indicate it is actually a .desktop file. Please add a warning to lintian suggesting that these files be moved elsewhere or renamed. Probably lintian should detect the type of file and suggest the correct location for it to be moved or renamed to. -- bye, pabs https://wiki.debian.org/PaulWise signature.asc Description: This is a digitally signed message part
Bug#1017079: ITP: netbox -- WebUI based tool designed to manage and document computer networks
Package: wnpp Severity: wishlist Owner: Carsten Schoenert X-Debbugs-Cc: debian-de...@lists.debian.org * Package name: netbox Version : 3.2.8 Upstream Author : Jeremy Stretch * URL : https://github.com/netbox-community/netbox * License : Apache-2.0 and MIT/X Programming Lang: Python Description : WebUI based tool designed to manage and document computer networks NetBox is a Django based web application, initially conceived by the network engineering team at DigitalOcean, NetBox was developed specifically to address the needs of network and infrastructure engineers. It encompasses the following aspects of network management: . * Hierarchical regions, site groups, sites, and locations * Racks, devices, and device components * Cables and wireless connections * Power distribution * Data circuits and providers * Virtual machines and clusters * IP prefixes, ranges, and addresses * VRFs and route targets * FHRP groups (VRRP, HSRP, etc.) * AS numbers * VLANs and scoped VLAN groups * Organizational tenants and contacts . In addition to its extensive built-in models and functionality, NetBox can be customized and extended through the use of: . * Custom fields * Custom links * Configuration contexts * Custom model validation rules * Reports * Custom scripts * Export templates * Conditional webhooks * Plugins * Single sign-on (SSO) authentication * NAPALM integration * Detailed change logging . NetBox also features a complete REST API as well as a GraphQL API for easily integrating with other tools and systems. . While NetBox strives to cover many areas of network management, the scope of its feature set is necessarily limited. This ensures that development focuses on core functionality and that scope creep is reasonably contained. To that end, it might help to provide some examples of functionality that NetBox does not provide: . * Network monitoring * DNS server * RADIUS server * Configuration management * Facilities management I plan to maintain netbox within the Debian Python Team ideally together with some more interested people in managing the maintenance. Right now all needed build and binary package dependencies are fulfilled, as NetBox is getting actively developed it constantly bugfixes and new added features which might need new dependencies in the near future which are not packed yet. I'd like to see (if possible) the netbox package within the bookworm release. The NetBox UI is using some comprehensive JS files which are shipped as minimized files. Currently I'm unable to drop the shipped minimized code and rebuild all the needed files from scratch. If possible I'd like to get some help on this, currently netbox will need to go into non-free due the non rebuild-able minimized files. OTOH netbox can't go into main as it requires at least one package from non-free, it requires drf-yasg-nonfree for some Swagger functionality. Regards Carsten
Bug#1017074: ITP: libpysal -- "Core components of PySAL A library of spatial analysis functions".
Quoting Josenilson Ferreira da Silva (2022-08-13 05:19:55) > > * Package name: libpysal [...] > Description : "Componentes principais do PySAL Uma biblioteca de > funções de análise espacial. Please use english also for short description (not only long desscription) - i.e. translate to english if upstream project primary language is another. Thanks, - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: signature
Bug#1017077: sets compiler and flags wrong for armhf
Package: dh-dlang Version: 0.6.5 Severity: important X-Debbugs-Cc: m...@debian.org Hi, dh-dlang seems to export flags for armhf incorrectly. ldc is supported on armhf and hence this should be exported if available however dh-dlang does not seem to honor that[1] Furthermore, it has a snippet in the same condition to set extra DFLAGS for armhf[2] which makes it a no-op. Similar modifications should probably be done on default-d-compiler metapkg too. This was making diet-ng FTBFS for a while, so I added a workaround for it there. [1]: https://sources.debian.org/src/dh-dlang/0.6.5/dlang-flags.mk/#L27 [2]: https://sources.debian.org/src/dh-dlang/0.6.5/dlang-flags.mk/#L32 -- System Information: Debian Release: bookworm/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 5.18.0-3-amd64 (SMP w/8 CPU threads; PREEMPT) Kernel taint flags: TAINT_WARN, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages dh-dlang depends on: ii debhelper 13.8 pn default-d-compiler ii python3 3.10.5-3 dh-dlang recommends no packages. dh-dlang suggests no packages.
