Bug#1013102: cmd/link: check CGO_CFLAGS for non -g/-I/-O options before,+ internal linking
On Mon, 20 Jun 2022 at 14:59, Shengjing Zhu wrote:
> On Mon, Jun 20, 2022 at 08:42:51AM +1200, Michael Hudson-Doyle wrote:
> > Ah yes but that patch doesn't actually work in practice. I've been slack
> on
> > this :(
> >
> > IIRC the problem with https://go-review.googlesource.com/c/go/+/339370
> is
> > that lto causes some of the references in the linked executable to
> > disappear, meaning cgo can't do the analysis it needs to do. It's a shame
> > because it's obviously a much cleaner patch...
> >
>
> However CL281314 has its own problem that causes several packages FTBFS
> (#982701, #982714, #982720, #982724, #982734)
>
I think that was a broken version of the patch -- the packages those bugs
affect build fine in Ubuntu now afaics -- but I haven't checked explicitly.
> If CL339370 has problem too, can we try another routine? Like disable lto
> in dh-golang?
>
> If I read doko's message right, we are only going to enable lto by default
> in dpkg-buildflags, not gcc itself. So hacking dh-golang looks more
> sensible to me.
>
> For example adding following line to dh-golang (I didn't test it though):
>
> diff --git a/lib/Debian/Debhelper/Buildsystem/golang.pm
> b/lib/Debian/Debhelper/Buildsystem/golang.pm
> index 60f725a..02f16fe 100644
> --- a/lib/Debian/Debhelper/Buildsystem/golang.pm
> +++ b/lib/Debian/Debhelper/Buildsystem/golang.pm
> @@ -369,6 +369,7 @@ sub _set_goproxy {
> sub _set_cgo_flags {
> my $bf = Dpkg::BuildFlags->new();
> $bf->load_config();
> +$bf->set_feature("optimize", "lto", 0)
>
> my @flags = ( "CFLAGS", "CPPFLAGS", "CXXFLAGS", "FFLAGS", "LDFLAGS" );
> foreach my $flag (@flags) {
>
If that works, it might be a better option for now indeed.
Cheers,
mwh
Bug#1012286: RFS: zig/0.9.1-1 [ITP] -- Programming language
Hi,
quick progress report.
* Nick Hastings [220615 14:20]:
>
> * Adam Borowski [220603 23:34]:
> > On Fri, Jun 03, 2022 at 09:38:37AM +0900, Nick Hastings wrote:
> >
> > Worst news first: the copyright file requires a lot more work. I see for
> > example unlisted Khronos stuff (lib/libc/include/any-windows-any/{GL,KHR}/),
> > NTP (lib/libc/include/any-linux-any/linux/timex.h), Zope (mingw), ISC,
> > Apache, APSL, ... And the list of copyright holders is even more
> > incomplete. This is a big honking waste of time but it's
> > required... :(
>
> I actually already put quite a bit of effort into the copyright file,
> but it has been a very long time since I last worked on it.
>
> Taking a quick look now I wonder if maybe I have overlooked include
> directories, perhaps assuming that anything in there would be covered by
> src directories. Or maybe I'd just become burned out with it and wanted
> to move on!
>
> Anyway I think I'm ready to dive back in.
The initial copyright file was generated by debmake, have since used
decopy which seems to have found a lot of things that were previously
missed. I'm slowly grinding though it, adding and fixing things. It's
very time consuming, but I'm making progress.
https://github.com/NickHastings/zig-debian/blob/decopy/copyright
> > The package includes a bunch of tests, and with the likelihood of code not
> > handling a particular arch, glibc, etc, I'd say it's a must to run
> > them.
>
> Ok, I'll investigate running the tests.
I've added the tests to debian/rules. However two of them fail. See
https://github.com/NickHastings/zig-debian/blob/tests/rules
It's unclear to me if they are important. Have asked on zig irc, but so
far, no response. Will try to chase it up soon.
> > Not a strict requirement, but a man page would be greatly appreciated.
>
> Will put it on the todo list, but hopefully I can get upstream to do
> something on that front.
This is still sitting untouched at the bottom of the todo list.
Cheers,
Nick.
Bug#1013102: cmd/link: check CGO_CFLAGS for non -g/-I/-O options before,+ internal linking
On Mon, Jun 20, 2022 at 08:42:51AM +1200, Michael Hudson-Doyle wrote:
> Ah yes but that patch doesn't actually work in practice. I've been slack on
> this :(
>
> IIRC the problem with https://go-review.googlesource.com/c/go/+/339370 is
> that lto causes some of the references in the linked executable to
> disappear, meaning cgo can't do the analysis it needs to do. It's a shame
> because it's obviously a much cleaner patch...
>
However CL281314 has its own problem that causes several packages FTBFS
(#982701, #982714, #982720, #982724, #982734)
If CL339370 has problem too, can we try another routine? Like disable lto
in dh-golang?
If I read doko's message right, we are only going to enable lto by default
in dpkg-buildflags, not gcc itself. So hacking dh-golang looks more
sensible to me.
For example adding following line to dh-golang (I didn't test it though):
diff --git a/lib/Debian/Debhelper/Buildsystem/golang.pm
b/lib/Debian/Debhelper/Buildsystem/golang.pm
index 60f725a..02f16fe 100644
--- a/lib/Debian/Debhelper/Buildsystem/golang.pm
+++ b/lib/Debian/Debhelper/Buildsystem/golang.pm
@@ -369,6 +369,7 @@ sub _set_goproxy {
sub _set_cgo_flags {
my $bf = Dpkg::BuildFlags->new();
$bf->load_config();
+$bf->set_feature("optimize", "lto", 0)
my @flags = ( "CFLAGS", "CPPFLAGS", "CXXFLAGS", "FFLAGS", "LDFLAGS" );
foreach my $flag (@flags) {
Bug#1013250: psi-plugins: OMEMO plugin not available
Package: psi-plugins Version: 1.5-2 Severity: minor Dear Maintainer, While OMEMO support is listed in the description of the psi package, it does not seem to be present in the psi-plugin package. $ apt-cache show psi [...] Version: 1.5+dfsg1-1+b1 [...] Description-en: Qt-based XMPP client [...] is also a major consideration, and Psi provides it for both client-to-server (TLS) and client-to-client (OpenPGP, OTR, OMEMO) via appropriate plugins. [...] $ apt-cache show psi-plugins | grep omemo $ It seems this plugin is not listed in psi-plugins debian/rules, while other plugins are: $ apt-get source psi-plugins [...] $ grep omemo psi-plugins-1.5/debian/rules $ Could you consider either enabling this plugin ? Alternatively, you could edit the package description to remove mention of OMEMO, although I would personally find such fix as underwhelming. Regards, Vincent Pelletier -- System Information: Debian Release: bookworm/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.17.0-2-amd64 (SMP w/8 CPU threads; PREEMPT) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE=fr:en_GB Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages psi-plugins depends on: ii libc6 2.33-7 ii libgcc-s1 12.1.0-2 ii libgcrypt20 1.10.1-2 ii libotr5 4.1.1-5 ii libqt5core5a5.15.2+dfsg-16+b2 ii libqt5dbus5 5.15.2+dfsg-16+b2 ii libqt5gui5 5.15.2+dfsg-16+b2 ii libqt5network5 5.15.2+dfsg-16+b2 ii libqt5widgets5 5.15.2+dfsg-16+b2 ii libqt5xml5 5.15.2+dfsg-16+b2 ii libstdc++6 12.1.0-2 ii libtidy5deb12:5.6.0-11 ii libx11-62:1.7.5-1 ii psi 1.5+dfsg1-1+b1 Versions of packages psi-plugins recommends: pn psi-l10n psi-plugins suggests no packages. -- no debconf information
Bug#1013249: virtio_ring: module verification failed: signature and/or required key missing - tainting kernel
Package: src:linux Version: 5.18.5-1 Severity: normal User: debian-ri...@lists.debian.org Usertags: riscv64 X-Debbugs-Cc: debian-ri...@lists.debian.org Dear Maintainer, I do not expect a kernel module in a genuine Debian kernel package taints a kernel. But I see the following message in dmesg on QEMU RISCV64 virt machine: [8.038025] virtio_ring: module verification failed: signature and/or required key missing - tainting kernel The QEMU is running on Debian/testing amd64 with the following version: $ dpkg-query -W | fgrep qemu-system-misc qemu-system-misc1:7.0+dfsg-7 The QEMU is started as follows: qemu-system-riscv64 -machine virt,aclint=on,aia=none -m 4G -smp 4 -bios /usr/lib/riscv64-linux-gnu/opensbi/generic/fw_jump.elf -kernel /usr/lib/u-boot/qemu-riscv64_smode/uboot.elf -append "console=ttyS0 rw root=/dev/vda1" -netdev user,id=net0 -device virtio-net-pci,netdev=net0 -object rng-random,filename=/dev/urandom,id=rng0 -device virtio-rng-pci,rng=rng0 -drive if=virtio,file=debian-sid-riscv64.qcow2,index=0,format=qcow2,discard=unmap,detect-zeroes=unmap -- Package-specific info: ** Version: Linux version 5.18.0-2-riscv64 (debian-ker...@lists.debian.org) (gcc-11 (Debian 11.2.0-20) 11.2.0, GNU ld (GNU Binutils for Debian) 2.38) #1 SMP Debian 5.18.5-1 (2022-06-16) ** Command line: root=UUID=031c42a9-74c5-4b38-8e78-87d5f1141c24 rw noquiet root=/dev/vda1 net.ifnames=0 consoleblank=0 rw ** Tainted: E (8192) * unsigned module was loaded ** Kernel log: [0.00] Linux version 5.18.0-2-riscv64 (debian-ker...@lists.debian.org) (gcc-11 (Debian 11.2.0-20) 11.2.0, GNU ld (GNU Binutils for Debian) 2.38) #1 SMP Debian 5.18.5-1 (2022-06-16) [0.00] OF: fdt: Ignoring memory range 0x8000 - 0x8020 [0.00] Machine model: riscv-virtio,qemu [0.00] efi: UEFI not found. [0.00] NUMA: No NUMA configuration found [0.00] NUMA: Faking a node at [mem 0x8020-0x00017fff] [0.00] NUMA: NODE_DATA [mem 0x17ffedbc0-0x17ffeefff] [0.00] Zone ranges: [0.00] DMA32[mem 0x8020-0x] [0.00] Normal [mem 0x0001-0x00017fff] [0.00] Movable zone start for each node [0.00] Early memory node ranges [0.00] node 0: [mem 0x8020-0x00017fff] [0.00] Initmem setup node 0 [mem 0x8020-0x00017fff] [0.00] On node 0, zone DMA32: 512 pages in unavailable ranges [0.00] SBI specification v0.3 detected [0.00] SBI implementation ID=0x1 Version=0x1 [0.00] SBI TIME extension detected [0.00] SBI IPI extension detected [0.00] SBI RFENCE extension detected [0.00] SBI SRST extension detected [0.00] SBI HSM extension detected [0.00] riscv: base ISA extensions acdfhim [0.00] riscv: ELF capabilities acdfim [0.00] percpu: cpu 0 has no node -1 or node-local memory [0.00] percpu: Embedded 27 pages/cpu s72744 r8192 d29656 u110592 [0.00] pcpu-alloc: s72744 r8192 d29656 u110592 alloc=27*4096 [0.00] pcpu-alloc: [0] 0 [0] 1 [0] 2 [0] 3 [0.00] Fallback order for Node 0: 0 [0.00] Built 1 zonelists, mobility grouping on. Total pages: 1031688 [0.00] Policy zone: Normal [0.00] Kernel command line: root=UUID=031c42a9-74c5-4b38-8e78-87d5f1141c24 rw noquiet root=/dev/vda1 net.ifnames=0 consoleblank=0 rw [0.00] Unknown kernel command line parameters "noquiet", will be passed to user space. [0.00] Dentry cache hash table entries: 524288 (order: 10, 4194304 bytes, linear) [0.00] Inode-cache hash table entries: 262144 (order: 9, 2097152 bytes, linear) [0.00] mem auto-init: stack:off, heap alloc:on, heap free:off [0.00] software IO TLB: mapped [mem 0xfb73a000-0xff73a000] (64MB) [0.00] Memory: 2079280K/4192256K available (7539K kernel code, 5095K rwdata, 4096K rodata, 2456K init, 426K bss, 252764K reserved, 0K cma-reserved) [0.00] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1 [0.00] ftrace: allocating 28720 entries in 113 pages [0.00] ftrace: allocated 113 pages with 4 groups [0.00] trace event string verifier disabled [0.00] rcu: Hierarchical RCU implementation. [0.00] rcu: RCU restricting CPUs from NR_CPUS=8 to nr_cpu_ids=4. [0.00] Rude variant of Tasks RCU enabled. [0.00] Tracing variant of Tasks RCU enabled. [0.00] rcu: RCU calculated value of scheduler-enlistment delay is 25 jiffies. [0.00] rcu: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=4 [0.00] NR_IRQS: 64, nr_irqs: 64, preallocated irqs: 0 [0.00] riscv-intc: 64 local interrupts mapped [0.00] plic: plic@c00: mapped 53 interrupts with 4 handlers for 8 contexts. [0.00] riscv_timer_init_dt: Registering clocksource cpuid
Bug#1013248: libseat-dev: Missing libseat-dev dependency on libsystemd-dev via pkg-config
Package: libseat-dev
Version: 0.7.0-4
Severity: grave
Justification: renders package unusable
Dear Maintainer,
Using pkg-config to find headers fails for libseat-dev with
the following output:
$ /usr/bin/pkg-config --cflags libseat
Package libsystemd was not found in the pkg-config search path.
Perhaps you should add the directory containing `libsystemd.pc'
to the PKG_CONFIG_PATH environment variable
Package 'libsystemd', required by 'libseat', not found
pkgconfig/libseat.pc includes dependency on libsystemd:
$ cat /usr/lib/x86_64-linux-gnu/pkgconfig/libseat.pc
prefix=/usr
includedir=${prefix}/include
libdir=${prefix}/lib/x86_64-linux-gnu
have_seatd=true
have_logind=true
have_builtin=true
Name: libseat
Description: Seat management library
Version: 0.7.0
Requires.private: libsystemd
Libs: -L${libdir} -lseat
Libs.private: -lrt
Cflags: -I${includedir}
Please include libsystemd-dev as a dependency of libseat-dev.
Also, if I'm not mistaken, seatd is trying not to have hard
dependencies on systemd, but couldn't find from where
the .pc file is generated.
-- System Information:
Debian Release: bookworm/sid
APT prefers testing
APT policy: (500, 'testing'), (50, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 5.17.0-1-amd64 (SMP w/12 CPU threads; PREEMPT)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
LANGUAGE=en_US:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages libseat-dev depends on:
ii libseat1 0.7.0-4
libseat-dev recommends no packages.
libseat-dev suggests no packages.
-- no debconf information
Bug#1003353: lintian: Cannot use brackets in suppression rules?
Control: tag -1 + pending patch
Hi Samuel,
Samuel Thibault wrote:
> Seeing that qa.debian.org is using version 2.114.123 of lintian, I
> upgraded my lintian from its git tree, only to find that it seems I
> cannot update my suppression rule according to the new output:
>
> W: libbrlapi-dev: bad-whatis-entry
> [usr/share/man/man3/brlapi_authClientPacket_t.3.gz]
> W: libbrlapi-dev: mismatched-override bad-whatis-entry
> [usr/share/man/man3/brlapi_*] [usr/share/lintian/overrides/libbrlapi-dev:2]
>
> I did have updated this rule to include brackets:
>
> bad-whatis-entry [usr/share/man/man3/brlapi_*]
>
> but that doesn't seem to be working. I also tried to use escaping (which
> had fixed things for the ${} case), but to no avail:
>
> bad-whatis-entry \[usr/share/man/man3/brlapi_*\]
Using * or ? in place of the brackets probably would have worked.
Cause was the switch of was this commit from 6 months ago:
commit 139009d5a54225ebff4509ec37b979cb898c17fe
Author: Felix Lechner
Date: Wed Dec 1 21:46:24 2021 -0800
Use Text::Glob to match hint contexts with override patterns.
Replaces a trusted homegrown routine.
Gbp-Dch: ignore
I neither understand why you would replace something "trusted" and
additionally not even plan to mention such a invasive commit in the
changelog.
And because Text::Glob also interprets brackets (and curly braces) and
you can't disable that, such issues were just waiting to happen.
And together with the brackets using "pointed hints" concept
introduced at around the same time, this caused really havoc.
> Lintian has recently been annoying enough that I'm unsure I'd continue
> monitoring its output any more.
*nod* JFYI, in case you didn't notice it (it happend months after your
bug report), but there was an "O: lintian" WNPP bug report in the
meantime: https://bugs.debian.org/1012289
So I'm now trying to clean up the shattered remains which the previous
(recent) Lintian maintainer(s) left behind.
For now I'm trying to get a current lintian version back into Testing,
i.e. I'm concentrating on RC and important bugs as well as bugs which
are annoying and easy to fix, e.g. those with a patch or MR.
At least the lintian internal test suite is no more failing. Although
it likely has some false negatives as it seems that the test suite is
no more able to run more than one check in one test. And running a
test against multiple checks at the same time seems critical to write
tests for issues like this one. Meh.
Anyway, my feature branch for this bug report is
https://salsa.debian.org/lintian/lintian/-/commits/brackets-in-overrides-rc-bug-1003353
but I will likely force-push that branch some more times, so the
commit message in
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1003353#50 might
become stale soon while I refine the commit before that (which
contains a test for this bug), but the patch will likely stay valid.
You also might get further such mails when I force-push new histories
in that feature branch. I hope you don't mind, but I wanted to publish
what I already have.
Regards, Axel
--
,''`. | Axel Beckert , https://people.debian.org/~abe/
: :' : | Debian Developer, ftp.ch.debian.org Admin
`. `' | 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5
`-| 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE
signature.asc
Description: PGP signature
Bug#1013247: telegram-desktop: Crashes on entering a chat if the window is too narrow (less wide than ca. 380 pixel) or resized to below ca. 380 pixel width while a chat is open
Package: telegram-desktop Version: 3.7.3+ds-2+b1 Severity: important Hi, telegram-desktop crashes for me if I make its window smaller than some specific window width or start it and it gets resized to such a width by i3 (tiling window manager) and then open e.g. a group chat. It basically happens once the speech bubbles don't become less wide than the available space anymore. If I first make the window too small and then enter the group chat, I only see the very last speech bubble before it crashes (probably during trying to display the remaining speech bubbles). A window size of 381x572 was fine, and a window size of 378x572 or less wide triggered the crash. The crash output ends as follows: DSvgRenderer::load: XML parse error: Input file is too short /usr/include/c++/11/bits/stl_algo.h:3658: constexpr const _Tp& std::clamp(const _Tp&, const _Tp&, const _Tp&) [with _Tp = int]: Assertion '!(__hi < __lo)' failed. [4] + 8736 IOT instruction (core dumped) This is reproducible for me: ~crash/1000 → ls -ltr *telegram* -rw--- 1 abe abe 2875678720 Jun 19 23:53 12097-1000-1000-6-1655675593-c6--usr-bin-telegram-desktop--deleted-.core -rw--- 1 abe abe 628158464 Jun 19 23:53 1764-1000-1000-6-1655675638-c6--usr-bin-telegram-desktop.core -rw--- 1 abe abe 538529792 Jun 19 23:54 2201-1000-1000-6-1655675651-c6--usr-bin-telegram-desktop.core -rw--- 1 abe abe 538755072 Jun 19 23:54 2932-1000-1000-6-1655675678-c6--usr-bin-telegram-desktop.core -rw--- 1 abe abe 538767360 Jun 19 23:56 4579-1000-1000-6-1655675773-c6--usr-bin-telegram-desktop.core -rw--- 1 abe abe 537563136 Jun 20 00:08 8736-1000-1000-6-1655676533-c6--usr-bin-telegram-desktop.core -rw--- 1 abe abe 535805952 Jun 20 00:19 10857-1000-1000-6-1655677151-c6--usr-bin-telegram-desktop.core -rw--- 1 abe abe 545185792 Jun 20 00:19 12650-1000-1000-6-1655677178-c6--usr-bin-telegram-desktop.core -rw--- 1 abe abe 523145216 Jun 20 00:34 15104-1000-1000-6-1655678091-c6--usr-bin-telegram-desktop.core -rw--- 1 abe abe 537464832 Jun 20 00:35 19830-1000-1000-6-1655678103-c6--usr-bin-telegram-desktop.core Backtraces available in private upon request. The one core dump containing the word "deleted" was from before the BinNMU for the Qt transistion. So I suspect that it is _NOT_ related to it. I just tried this for the first time (in a long time) after that transition by chance. -- Package-specific info: -- BEGIN ATTACHMENTS -- /home/abe/.local/share/TelegramDesktop/log.txt -- END ATTACHMENTS -- -- System Information: Debian Release: bookworm/sid APT prefers unstable APT policy: (990, 'unstable'), (600, 'testing'), (500, 'unstable-debug'), (500, 'buildd-unstable'), (110, 'experimental'), (1, 'experimental-debug'), (1, 'buildd-experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.16.0-6-amd64 (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: sysvinit (via /sbin/init) LSM: AppArmor: enabled Versions of packages telegram-desktop depends on: ii libabsl20210324 0~20210324.2-4 ii libavcodec-extra58 [libavcodec58] 7:4.4.2-1+b3 ii libavformat-extra58 [libavformat58] 7:4.4.2-1+b3 ii libavutil56 7:4.4.2-1+b3 ii libc6 2.33-7 ii libgcc-s1 12.1.0-4 ii libglib2.0-02.72.2-2 ii libglibmm-2.4-1v5 2.66.4-1 ii libhunspell-1.7-0 1.7.0-4 ii libjpeg62-turbo 1:2.1.2-1 ii libkf5waylandclient54:5.94.0-2 ii liblz4-11.9.3-2 ii libminizip1 1.1-8+b1 ii libopenal1 1:1.19.1-2 ii libopus01.3.1-1 ii libqrcodegencpp11.8.0-1.1 ii libqt5core5a [qtbase-abi-5-15-4]5.15.4+dfsg-3 ii libqt5gui5 5.15.4+dfsg-3 ii libqt5network5 5.15.4+dfsg-3 ii libqt5svg5 5.15.4-2 ii libqt5waylandclient5 [qtwayland-client-abi-5-15-4] 5.15.4-2 ii libqt5widgets5 5.15.4+dfsg-3 ii librlottie0-1 0.1+dfsg-2 ii libsigc++-2.0-0v5 2.10.8-1 ii libssl3 3.0.3-8 ii libstdc++6 12.1.0-4 ii libswresample3 7:4.4.2-1+b3 ii libswscale5 7:4.4.2-1+b3 ii
Bug#1012835: Summary
The random number generator has undergone a few important changes for [uptream] Linux 5.17 and 5.18, in an attempt to modernize both the code and the cryptography used. Details: https://www.zx2c4.com/projects/linux-rng-5.17-5.18/ The most visible aspect of this, and the likely reason for several bug reports, is that the size of the entropy pool went down from ~3000+ to 256. This is an intentional upstream change and NOT a bug in the Debian kernel. The 'wontfix' tag is therefor added to this bug (and therefor merged bugs). These changes have also been backported to other LTS kernels, including the 5.10 kernel used in Debian Bullseye. Almost the whole upstream 5.10.119 release consist of these changes. There have been extensive commit messages, so next to the above referenced document, ``git log v5.10.118..v5.10.119`` should give you (more) details. signature.asc Description: This is a digitally signed message part.
Bug#1013246: RFS: kmscon/9.0.0-1 [ITP] -- Simple terminal emulator based on Kernel Mode Setting
Package: sponsorship-requests Severity: wishlist -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 ear mentors, I am looking for a sponsor for my package "kmscon": * Package name: kmscon Version : 9.0.0-1 Upstream Author : Aetf * URL : https://github.com/Aetf/kmscon * License : LGPL-2.1+, public-domain, GPL-2 with Font exception, Expat and HPND, Expat * Vcs : https://salsa.debian.org/viccie30/kmscon Section : utils The source builds the following binary packages: kmscon - Simple terminal emulator based on Kernel Mode Setting To access further information about this package, please visit the following URL: https://mentors.debian.net/package/kmscon/ Alternatively, you can download the package with 'dget' using this command: dget -x https://mentors.debian.net/debian/pool/main/k/kmscon/kmscon_9.0.0-1.dsc Changes for the initial release: kmscon (9.0.0-1) unstable; urgency=medium . * Initial release (Closes: #1004919) Regards, - -- Victor Westerhuis -BEGIN PGP SIGNATURE- iQJHBAEBCAAxFiEE6OxII3T+o0Ujs6ECQz2Rq5dHQPsFAmKvjv4THHZpY3RvckB3 ZXN0ZXJodS5pcwAKCRBDPZGrl0dA+1DuEACoVZ3h4kLV+vGvRLwqs7C8BdzOl9F4 JIX3J0wKTUYp+y0x7phTDvoTCdEPVmYdaaF8UTMAJJBn0CSCxfL/VHoLWwG6HadI EU1ECy1u5TAuZrFxVeUUArzUzIuMulPPldXdoRh0xghdwTNDdF9HI0w9pSTkgDwW 3GwgLNnTfk3gidgC7K46oHc0grqma0m5fZ7TFAvRMyl7cU5WPxJ8Mzt9BcIvEx8Y vURyb/58/9wOsKOruchcsvQsXJpT6IBYA3F5csfVVdvY9tp20GDS9/dTdh2+bshM j4xm1ZwKnZOlSwkpzScHnY2/UhxUIROvemtXyPsnY0A+0PtDT7eUMR+5DJUjAKAe nPxSThsQqn3YVn4CkpDgVWH4VXsj2r9vM/LD+yOw/TO8Kg462GSk3Bw+398pU3mc w/wpCVFwflw6vgVN54T8zSM0glqpOCOzL6zszxOy0x4efH7dNUA8y2iJunexqEQC O6fG5sruRWSQYybo1dw8I1uRVPFw67J+NamsOLpD0tf8k9FtjdoVM44OpmATzXII IlNtY7Ah3P+pfnI5cwoJ81Y63ZYUnCC4jq/YW68pfOhhFG3ULG2INjdWCJBfM4+6 WSxduOdxj3sZF3gI4+5pymG1fN6Vk54Vrx1XcVyK6pyFR1i9feJjc5nCro5MIrEI UfG0EZEDrN90qw== =rOiZ -END PGP SIGNATURE-
Bug#1013241: upgrade-reports: kernel upgrade 5.10.0.9 to 5.10.0.15
Control: merge -1 1013192 On zondag 19 juni 2022 22:09:08 CEST Paul Gevers wrote: > On 19-06-2022 21:48, NormanMurray wrote: > > > With 5.10.0.9, randomsound worked well to keep > > /proc/sys/kernel/random/entropy_avail up at set point and > > /proc/sys/kernel/random/poolsize at 4096 > > With 5.10.0.15, randomsound did > > not work to keep /proc/sys/kernel/random/entropy_avail up at set point > > and /proc/sys/kernel/random/poolsize was set at 256 I down graded back to > > 5.10.0.9 > > I've seen the same drop in entropy_avail, but the changelog mentioned a > lot of changes to random, so I interpreted that as being intended. I've > reassigned to the linux source package, as they can confirm that this is > not a bug, or treat it appropriately. See the bug with which this one will be merged for details, especially https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013192#19 This is an intentional change in the upstream kernel. signature.asc Description: This is a digitally signed message part.
Bug#1011909: shellcheck: FTBFS: dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2
The build is now failing with another error, but both FTBFS are not caused by shellcheck, and can't be fixed by it. There's something weird going on with haskell packages, I believe the error will eventually be solved in the next few weeks, let's see... Regards, -- Samuel Henrique
Bug#1013245: RFS: flask-session/0.3.2-1 [ITP] -- Extension for Flask
Package: sponsorship-requests Severity: wishlist Dear mentors, I am looking for a sponsor for my package "flask-session": * Package name: flask-session Version : 0.3.2-1 Upstream Author : https://github.com/fengsp/flask-session/issues * URL : https://github.com/fengsp/flask-session * License : BSD-3-Clause * Vcs : https://salsa.debian.org/debian/flask-session Section : python The source builds the following binary packages: python3-flask-session - Extension for Flask To access further information about this package, please visit the following URL: https://mentors.debian.net/package/flask-session/ Alternatively, you can download the package with 'dget' using this command: dget -x https://mentors.debian.net/debian/pool/main/f/flask-session/flask-session_0.3.2-1.dsc git -x https://salsa.debian.org/nilsonfsilva/flask-session Changes for the initial release: flask-session (0.3.2-1) experimental; urgency=medium . * Initial release. (Closes: #928091) Regards, -- Nilson F. Silva
Bug#1012600: [Pkg-zfsonlinux-devel] Bug#1012600:
I think this is because it Depends: a kernel << 5.18 and not Conflicts/Breaks a kernel >= 5.18. Since you can install multiple kernel packages, your existing kernel package is satisfying the dependency. -- Richard OpenPGP_signature Description: OpenPGP digital signature
Bug#1013102: cmd/link: check CGO_CFLAGS for non -g/-I/-O options before,+ internal linking
Ah yes but that patch doesn't actually work in practice. I've been slack on this :( IIRC the problem with https://go-review.googlesource.com/c/go/+/339370 is that lto causes some of the references in the linked executable to disappear, meaning cgo can't do the analysis it needs to do. It's a shame because it's obviously a much cleaner patch... Cheers, mwh On Sat, 18 Jun 2022 at 02:51, Shengjing Zhu wrote: > On Fri, Jun 17, 2022 at 3:36 PM Matthias Klose wrote: > > > > Package: src:golang-1.18 > > Version: 1.18.3-1 > > Severity: wishlist > > Tags: patch > > > > lto support now landed in dpkg in unstable, now evaluation the > possibility to > > turn on link time optimizations by default. Currently builds fail like: > > > > [...] > > loadelf: $WORK/b101/_pkg_.a(_x001.o): 151068: sym#11 > (g_cgo_export.c.d01d1947): > > ignoring symbol in section 4 (type 0) > > loadelf: $WORK/b101/_pkg_.a(_x002.o): 151072: sym#11 > > (cgo_linux.cgo2.c.e1a05304): ignoring symbol in section 4 (type 0) > > loadelf: $WORK/b101/_pkg_.a(_x003.o): 151077: sym#13 > > (cgo_resnew.cgo2.c.1f334c1b): ignoring symbol in section 5 (type 0) > > loadelf: $WORK/b101/_pkg_.a(_x004.o): 151081: sym#11 > > (cgo_socknew.cgo2.c.00cb1c10): ignoring symbol in section 4 (type 0) > > loadelf: $WORK/b101/_pkg_.a(_x005.o): 151086: sym#13 > (cgo_unix.cgo2.c.81407354): > > ignoring symbol in section 5 (type 0) > > loadelf: $WORK/b108/_pkg_.a(_x001.o): 151068: sym#11 > (g_cgo_export.c.d01d1947): > > ignoring symbol in section 4 (type 0) > > loadelf: $WORK/b108/_pkg_.a(_x002.o): 151093: sym#11 > (cgo.cgo2.c.547524ab): > > ignoring symbol in section 4 (type 0) > > loadelf: $WORK/b108/_pkg_.a(_x003.o): 151098: sym#13 > (gcc_context.c.0c594a6b): > > ignoring symbol in section 5 (type 0) > > loadelf: $WORK/b108/_pkg_.a(_x004.o): 151105: sym#16 > (gcc_fatalf.c.104c99f5): > > ignoring symbol in section 5 (type 0) > > loadelf: $WORK/b108/_pkg_.a(_x005.o): 151116: sym#21 > (gcc_libinit.c.57049a80): > > ignoring symbol in section 5 (type 0) > > loadelf: $WORK/b108/_pkg_.a(_x006.o): 151126: sym#19 > > (gcc_linux_amd64.c.7bb88008): ignoring symbol in section 5 (type 0) > > loadelf: $WORK/b108/_pkg_.a(_x007.o): 151133: sym#16 > (gcc_mmap.c.58726c34): > > ignoring symbol in section 5 (type 0) > > loadelf: $WORK/b108/_pkg_.a(_x008.o): 151138: sym#13 > (gcc_setenv.c.58922dfc): > > ignoring symbol in section 5 (type 0) > > loadelf: $WORK/b108/_pkg_.a(_x009.o): 151143: sym#14 > (gcc_sigaction.c.8c3bca0d): > > ignoring symbol in section 5 (type 0) > > loadelf: $WORK/b108/_pkg_.a(_x010.o): 151148: sym#13 > (gcc_traceback.c.2a322f93): > > ignoring symbol in section 5 (type 0) > > loadelf: $WORK/b108/_pkg_.a(_x011.o): 151156: sym#16 > (gcc_util.c.9bbd18fc): > > ignoring symbol in section 5 (type 0) > > loadelf: $WORK/b108/_pkg_.a(_x012.o): 151161: sym#13 > (linux_syscall.c.96145c1f): > > ignoring symbol in section 5 (type 0) > > _cgo_callers: relocation target x_cgo_callers not defined > > _cgo_init: relocation target x_cgo_init not defined > > _cgo_mmap: relocation target x_cgo_mmap not defined > > _cgo_munmap: relocation target x_cgo_munmap not defined > > /usr/lib/go-1.18/pkg/tool/linux_amd64/link: too many errors > > [...] > > > > > https://patches.ubuntu.com/g/golang-1.18/golang-1.18_1.18.3-1ubuntu1.patch > > > > so please disable these for now and/or forward the issue upstream. > > The patch says it has been forwarded to > https://go-review.googlesource.com/c/go/+/281314 > And on https://go-review.googlesource.com/c/go/+/281314, the comment > says it has been obsoleted by > https://go-review.googlesource.com/c/go/+/339370 > > -- > Shengjing Zhu > >
Bug#988135: evince: zooming 100% ignores dpi as reported by xrandr
Control: tags -1 + upstream patch Control: severity -1 important On Thu, May 06, 2021 at 01:55:44PM +0200, Helmut Grohne wrote: > The logic there essentially says: If your screen is taller than 1080 > pixels in landscape, your dpi is 192 and otherwise it is 96. For a > typical 1900x1200 24" display that happens to have roughly a dpi of 96, > evince determines that it must be a HiDPI display at 192 dpi. As a > result, 100% actually presents more like 200%. > > That's quite unhelpful. This used to work correctly. It is really annoying. Every single document I open with evince comes out scaled unreadable. It also is trivial to fix: git revert c3ac0d3dc7bf05ebb219afcdf3d58f93d01e42cc Possibly, a middle ground could be found by clamping the computed DPI to the 96 to 192 range made in the guess, but I think that the 192 guess is so bad that revert is the initial way to go. Also keep in mind that working around the current behaviour is impossible, because evince has no setting to force a dpi or like that. On the other hand, working around a broken detection logic is as simple as xrandr --dpi 96. Would you mind a NMU? Helmut
Bug#1013243: RFP: hexbytes -- Python bytes subclass that decodes hex, with a readable console output
Package: wnpp Severity: wishlist * Package name: hexbytes Upstream Author : The Ethereum Foundation * URL : https://github.com/ethereum/hexbytes * License : Expat Programming Lang: Python Description : Python bytes subclass that decodes hex, with a readable console output This Python library is needed to update crossbar to a later upstream version. It should be maintained in the Python Team. HexBytes is a very thin wrapper around the python built-in bytes class. It has these three changes: 1. Accepts more initializing values, like hex strings, non-negative integers, and booleans 2. Returns hex with prefix ‘0x’ from HexBytes.hex() 3. The representation at console is in hex
Bug#1010286: please package new upstream release
On 2022-04-27 17:01:33, Antoine Beaupre wrote: > This is needed to ship the newer Trocla release (0.4.0) and possibly > other dependencies. > > I'll see if I can work on this myself shortly as part of the ruby > team. So I have tried that and failed. I pushed the results to salsa in a debian/experimental branch on salsa. Somehow the test suite is failing because it's trying to load the specs from `git ls-files`, which obviously can't work. Yet it *did* work in 1.0.0, currently in the archive, which *also* has that in its gemspec file. I have no idea wtf is going on with that and ran out of time today. Hopefully, what I pushed there can be useful for others. I have disabled a few patches that do not apply as well, those were there to disable tests as well, so maybe that's the problem? Anyways, it was a struggle enough just to get here. At least I pushed one patch upstream, here: https://github.com/moneta-rb/moneta/pull/228 ... which hopefully we'll be able to eventually drop. Attached: latest build log. a. -- We build our computer (systems) the way we build our cities: over time, without a plan, on top of ruins. - Ellen Ullman sbuild (Debian sbuild) 0.81.2 (31 January 2021) on angela.anarc.at +==+ | ruby-moneta 1.5.1-1 (amd64) Sun, 19 Jun 2022 19:56:58 + | +==+ Package: ruby-moneta Version: 1.5.1-1 Source Version: 1.5.1-1 Distribution: unstable Machine Architecture: amd64 Host Architecture: amd64 Build Architecture: amd64 Build Type: full I: NOTICE: Log filtering will replace 'autopkgtest-virt-dummy-location' with '<>' I: NOTICE: Log filtering will replace 'build/ruby-moneta-ljKTNZ/resolver-tH3gU2' with '<>' +--+ | Update chroot| +--+ Get:1 https://deb.debian.org/debian unstable InRelease [165 kB] Get:2 https://deb.debian.org/debian unstable/main Sources.diff/Index [63.6 kB] Get:3 https://deb.debian.org/debian unstable/main amd64 Packages.diff/Index [63.6 kB] Get:4 https://deb.debian.org/debian unstable/main Sources T-2022-06-19-1406.21-F-2022-06-19-1406.21.pdiff [10.7 kB] Get:4 https://deb.debian.org/debian unstable/main Sources T-2022-06-19-1406.21-F-2022-06-19-1406.21.pdiff [10.7 kB] Get:5 https://deb.debian.org/debian unstable/main amd64 Packages T-2022-06-19-1406.21-F-2022-06-19-1406.21.pdiff [9318 B] Get:5 https://deb.debian.org/debian unstable/main amd64 Packages T-2022-06-19-1406.21-F-2022-06-19-1406.21.pdiff [9318 B] Fetched 313 kB in 4s (80.4 kB/s) Reading package lists... Reading package lists... Building dependency tree... Reading state information... Calculating upgrade... The following packages were automatically installed and are no longer required: apparmor busybox dbus-user-session krb5-locales libldap-common libsasl2-modules os-prober zstd Use 'apt autoremove' to remove them. The following packages will be upgraded: libfreetype6 1 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. Need to get 420 kB of archives. After this operation, 0 B of additional disk space will be used. Get:1 https://deb.debian.org/debian unstable/main amd64 libfreetype6 amd64 2.12.1+dfsg-3 [420 kB] Fetched 420 kB in 0s (4982 kB/s) (Reading database ... (Reading database ... 5% (Reading database ... 10% (Reading database ... 15% (Reading database ... 20% (Reading database ... 25% (Reading database ... 30% (Reading database ... 35% (Reading database ... 40% (Reading database ... 45% (Reading database ... 50% (Reading database ... 55% (Reading database ... 60% (Reading database ... 65% (Reading database ... 70% (Reading database ... 75% (Reading database ... 80% (Reading database ... 85% (Reading database ... 90% (Reading database ... 95% (Reading database ... 100% (Reading database ... 24538 files and directories currently installed.) Preparing to unpack .../libfreetype6_2.12.1+dfsg-3_amd64.deb ... Unpacking libfreetype6:amd64 (2.12.1+dfsg-3) over (2.12.1+dfsg-2) ... Setting up libfreetype6:amd64 (2.12.1+dfsg-3) ... Processing triggers for libc-bin (2.33-7) ... +--+ | Fetch source files | +--+ Local sources - /home/anarcat/dist/build-area/ruby-moneta_1.5.1-1.dsc exists in /home/anarcat/dist/build-area; copying to chroot I: NOTICE: Log filtering will replace 'build/ruby-moneta-ljKTNZ/ruby-moneta-1.5.1' with '<>' I: NOTICE: Log filtering will replace 'build/ruby-moneta-ljKTNZ' with '<>'
Bug#1013241: upgrade-reports: kernel upgrade 5.10.0.9 to 5.10.0.15
Control: reassign -1 src:linux Hi Norman, On 19-06-2022 21:48, NormanMurray wrote: Package: upgrade-reports Severity: normal X-Debbugs-Cc: nmur...@telusplanet.net With 5.10.0.9, randomsound worked well to keep /proc/sys/kernel/random/entropy_avail up at set point and /proc/sys/kernel/random/poolsize at 4096 With 5.10.0.15, randomsound did not work to keep /proc/sys/kernel/random/entropy_avail up at set point and /proc/sys/kernel/random/poolsize was set at 256 I down graded back to 5.10.0.9 I've seen the same drop in entropy_avail, but the changelog mentioned a lot of changes to random, so I interpreted that as being intended. I've reassigned to the linux source package, as they can confirm that this is not a bug, or treat it appropriately. Paul OpenPGP_signature Description: OpenPGP digital signature
Bug#1013242: pulseaudio only plays back at default sample rate
Package: pulseaudio Version: 15.0+dfsg1-4+b1 Severity: normal Tags: upstream X-Debbugs-Cc: julianhug...@gmail.com Dear Maintainer, pulseaudio only plays back at default sample rate. The settings in /etc/pulse/daemon.conf "avoid-resampling = true" and "alternate-sample-rate = 48000" are ineffective, though when I run `pactl list modules` my alsa cards are shown with "avoid-resampling = true". For example: "Module #9 Name: module-alsa-card Argument: device_id="3" name="usb- XMOS_Clover_AUDIO_XMOS_Clover_AUDIO-00" card_name="alsa_card.usb- XMOS_Clover_AUDIO_XMOS_Clover_AUDIO-00" namereg_fail=false tsched=no fixed_latency_range=no ignore_dB=no deferred_volume=yes use_ucm=yes avoid_resampling=yes card_properties="module-udev-detect.discovered=1"" The above is a device which supports multiple sample rates and before I updated from Debian Bullseye to Bookworm pulseaudio did honour the "avoid_resampling=yes" option. Now it *only* plays audio at default sample rate set in daemon.conf I believe this is an upstream bug as I have seen users of Red Hat/Fedora and Arch making identical reports in their trackers. -- Package-specific info: File '/etc/default/pulseaudio' does not exist -- System Information: Debian Release: bookworm/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.18.0-1-amd64 (SMP w/12 CPU threads; PREEMPT) 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 pulseaudio depends on: ii adduser 3.121 ii init-system-helpers 1.63 ii libasound2 1.2.6.1-2+b1 ii libasound2-plugins 1:1.2.6-dmo1 ii libc6 2.33-7 ii libcap2 1:2.44-1 ii libdbus-1-3 1.14.0-1 ii libfftw3-single33.3.8-2 ii libgcc-s1 12.1.0-2 ii libglib2.0-02.72.2-2 ii libgstreamer-plugins-base1.0-0 1.20.2-dmo2 ii libgstreamer1.0-0 1.20.2-1 ii libice6 2:1.0.10-1 ii libltdl72.4.7-4 ii liborc-0.4-01:0.4.32-2 ii libpulse0 15.0+dfsg1-4+b1 ii libsm6 2:1.2.3-1 ii libsndfile1 1.0.31-2 ii libsoxr00.1.3-4 ii libspeexdsp11.2.0-1 ii libstdc++6 12.1.0-2 ii libsystemd0 250.4-1 ii libtdb1 1.4.6-3 ii libudev1250.4-1 ii libwebrtc-audio-processing1 0.3-1+b1 ii libx11-62:1.7.5-1 ii libx11-xcb1 2:1.7.5-1 ii libxcb1 1.14-3 ii libxtst62:1.2.3-1.1 ii lsb-base11.2 ii pulseaudio-utils15.0+dfsg1-4+b1 Versions of packages pulseaudio recommends: ii dbus-user-session1.14.0-1 ii libpam-systemd [logind] 250.4-1 ii rtkit0.13-4 Versions of packages pulseaudio suggests: ii paprefs 1.2-1 ii pavucontrol 5.0-2 ii pavumeter0.9.3-4+b4 ii udev 250.4-1 -- Configuration Files: /etc/pulse/daemon.conf changed: ; daemonize = no ; fail = yes ; allow-module-loading = yes ; allow-exit = yes ; use-pid-file = yes ; system-instance = no ; local-server-type = user ; enable-shm = yes ; enable-memfd = yes ; shm-size-bytes = 0 # setting this 0 will use the system-default, usually 64 MiB ; lock-memory = no ; cpu-limit = no ; high-priority = yes ; nice-level = -11 ; realtime-scheduling = yes ; realtime-priority = 5 ; exit-idle-time = 20 ; scache-idle-time = 20 ; dl-search-path = (depends on architecture) ; load-default-script-file = yes ; default-script-file = /etc/pulse/default.pa ; log-target = auto ; log-level = notice ; log-meta = no ; log-time = no ; log-backtrace = 0 ; resample-method = speex-float-1 resample-method = soxr-vhq ; avoid-resampling = false avoid-resampling = true ; enable-remixing = yes ; remixing-use-all-sink-channels = yes ; enable-lfe-remixing = no ; lfe-crossover-freq = 0 ; flat-volumes = yes ; rlimit-fsize = -1 ; rlimit-data = -1 ; rlimit-stack = -1 ; rlimit-core = -1 ; rlimit-as = -1 ; rlimit-rss = -1 ; rlimit-nproc = -1 ; rlimit-nofile = 256 ; rlimit-memlock = -1 ; rlimit-locks = -1 ; rlimit-sigpending = -1 ; rlimit-msgqueue = -1 ; rlimit-nice = 31 ; rlimit-rtprio = 9 ; rlimit-rttime = 20 ; default-sample-format = s16le default-sample-format = s24le ; default-sample-rate = 44100 ; alternate-sample-rate = 48000 ; default-sample-channels = 2 ; default-channel-map = front-left,front-right ; default-fragments = 4 ; default-fragment-size-msec = 25 ; enable-deferred-volume = yes ;
Bug#928091: ITP: flask-session -- Dependency needed for pagure
Control: owner -1 Nilson Silva On Sun, 19 Jun 2022 18:46:47 + Nilson Silva wrote: If you are not interested in packaging, can you change the title of the Bug? When the ITP has not been implemented for several years it is okay to just own the bug and go ahead. pagure does not seem to need this anymore because it exists in Debian without it. Please also block the reverse dependency's ITP by this ITP to show which program it is needed for.
Bug#1013241: upgrade-reports: kernel upgrade 5.10.0.9 to 5.10.0.15
Package: upgrade-reports Severity: normal X-Debbugs-Cc: nmur...@telusplanet.net (Please provide enough information to help the Debian maintainers evaluate the report efficiently - e.g., by filling in the sections below.) My previous release is: I am upgrading to: Archive date: Upgrade date: uname -a before upgrade: uname -a after upgrade: Method: Contents of /etc/apt/sources.list: - Were there any non-Debian packages installed before the upgrade? If so, what were they? - Was the system pre-update a pure sarge system? If not, which packages were not from sarge? - Did any packages fail to upgrade? - Were there any problems with the system after upgrading? Further Comments/Problems: Please attach the output of "COLUMNS=200 dpkg -l" (or "env COLUMNS ...", depending on your shell) from before and after the upgrade so that we know what packages were installed on your system. With 5.10.0.9, randomsound worked well to keep /proc/sys/kernel/random/entropy_avail up at set point and /proc/sys/kernel/random/poolsize at 4096 With 5.10.0.15, randomsound did not work to keep /proc/sys/kernel/random/entropy_avail up at set point and /proc/sys/kernel/random/poolsize was set at 256 I down graded back to 5.10.0.9
Bug#1013240: ITP: libinfluxdb-http-perl -- Perl way to interact with InfluxDB.
Package: wnpp Severity: wishlist Owner: Gabriel Filion X-Debbugs-Cc: debian-de...@lists.debian.org * Package name: libinfluxdb-http-perl Version : 0.04 Upstream Author : Raphael Seebacher * URL : https://metacpan.org/pod/InfluxDB::HTTP#LICENSE-AND-COPYRIGHT * License : Expat Programming Lang: Perl Description : Perl way to interact with InfluxDB. InfluxDB::HTTP allows you to interact with the InfluxDB HTTP API. The module essentially provides one method per InfluxDB HTTP API endpoint, that is ping, write and query. This package is a new dependency for the latest upstream release of Smokeping. I plan to manage this package through the perl team and I will ask for sponsoring from within the team.
Bug#1013239: ITP: python-gflanguages -- language-support categorization of the font families in the Google Fonts collection
Package: wnpp Severity: wishlist Owner: Agathe Porte X-Debbugs-Cc: debian-de...@lists.debian.org, deb...@microjoe.org * Package name: python-gflanguages Version : 0.4.0 Upstream Author : Felipe Corrêa da Silva Sanches * URL : https://github.com/googlefonts/lang * License : Apache-2.0 Programming Lang: Python Description : language-support categorization of the font families in the Google Fonts collection This python module provides an API with data about languages/regions/scripts for use in the language-support categorization of the font families in the Google Fonts collection. This is a new dependency of the gftools software that I am currently maintaining. I intent to maintain this package under the umbrella of both the Debian Python Team and the Debian Fonts Team.
Bug#1012874: lombok no longer ships lombok-utils.jar
On Thu, Jun 16, 2022 at 12:18:57PM +0200, Emmanuel Bourg wrote: > Le 2022-06-16 07:40, tony mancill a écrit : > > > Emmanuel, is there a reason it needed to be removed? > > If I remember well lombok-utils.jar is no longer built upstream, the last > version on Maven central is lombok-utils 1.18.12 (feb 2020). > > https://search.maven.org/artifact/org.projectlombok/lombok-utils > > > > Any concerns with me adding it back to the package? > > No objection but I'm not sure this will be enough to build lombok-ast. It > hasn't been updated since 2011, I guess it's obsolete now and we'll > increasingly struggle to keep it building. Ack that. Thanks for the response. I will close this and focus on porting lombok-ast.
Bug#928091: ITP: flask-session -- Dependency needed for pagure
Hello Alex! Are you still interested in packaging this module? I'm packaging a program that depends on it. He's ready. But when I went to open an ITP, I realized that you had already opened it. If you are not interested in packaging, can you change the title of the Bug? I'm on hold. Thanks! Nilson F. Silva
Bug#1013238: src:pyspread: fails to migrate to testing for too long: uploader built arch:all binary
Source: pyspread Version: 2.0.1-1 Severity: serious Control: close -1 2.1-2 Tags: sid bookworm pending User: release.debian@packages.debian.org Usertags: out-of-sync Dear maintainer(s), The Release Team considers packages that are out-of-sync between testing and unstable for more than 60 days as having a Release Critical bug in testing [1]. Your package src:pyspread has been trying to migrate for 61 days [2]. Hence, I am filing this bug. If a package is out of sync between unstable and testing for a longer period, this usually means that bugs in the package in testing cannot be fixed via unstable. Additionally, blocked packages can have impact on other packages, which makes preparing for the release more difficult. Finally, it often exposes issues with the package and/or its (reverse-)dependencies. We expect maintainers to fix issues that hamper the migration of their package in a timely manner. This bug will trigger auto-removal when appropriate. As with all new bugs, there will be at least 30 days before the package is auto-removed. I have immediately closed this bug with the version in unstable, so if that version or a later version migrates, this bug will no longer affect testing. I have also tagged this bug to only affect sid and bookworm, so it doesn't affect (old-)stable. Your package is only blocked because the arch:all binary package(s) aren't built on a buildd. Unfortunately the Debian infrastructure doesn't allow arch:all packages to be properly binNMU'ed. Hence, I will shortly do a no-changes source-only upload to DELAYED/15, closing this bug. Please let me know if I should delay or cancel that upload. Paul [1] https://lists.debian.org/debian-devel-announce/2020/02/msg5.html [2] https://qa.debian.org/excuses.php?package=pyspread OpenPGP_signature Description: OpenPGP digital signature
Bug#1000944: Business Proposal
-- Premier Oil Plc, 23 Lower Belgrave Street SW1W 0NR. London. Attention: Account/Finance manager Hello, My name is Mr Oliver Baruch, Account/Finance manager in (Premier Oil PLC). I have a business proposal that will be beneficial to you and me. please contact me for more details of the business to you. thanks. Forward your response to this email: oliverbaru...@gmail.com
Bug#1007022: podman: starting rootless container fails with: can't get final child's PID from pipe: EOF
Hi again, On 2022-06-19 03:28, Shengjing Zhu wrote: I used to be able to run rootless container on debian sid maybe 3 months ago (I'm sorry, I don't have much more precise information about versions when things used to work), but now that I try and start containers again I am consistently hitting errors of this form: $ podman run -d --name="draw" -p 8080:8080 -p 8443:8443 fjudith/draw.io Error: OCI runtime error: unable to start container "0f2eb8afb9ce6eebbede769dc288e228ea6cbae0e76936672e6673228ac6862c": runc create failed: unable to start container process: can't get final child's PID from pipe: EOF Can someone checks if you still fail to run rootless container with runc and podman 4.1? I think it's because https://github.com/containers/podman/issues/13731, which is fixed in podman 4.1. And it's caused by systemd 250 which changes OOMScoreAdjust inuser@.service For an added tidbit of information, I am under the impression that I need the "crun" package because of this configuration: $ podman info [...] ociRuntime: name: crun package: 'crun: /usr/bin/crun' path: /usr/bin/crun Although I tried changing that by creating a file ~/.config/containers/containers.conf with this: [engine] runtime = "runc" and then I had to remove currently existing containers to recreate them. and although "podman info" and "podman container inspect ..." show me that runc should now be used, I'm still getting the error above. So I don't know how to get containers to run with runc. Is it possible that podman has changed its default runtime to crun? In this case, would it make more sense for the podman debian package to depend on crun by default instead of runc?
Bug#1012613: nftables: upgrade stops but does not start service
On 2022-06-19, at 13:48:59 +0200, Arturo Borrero Gonzalez wrote:
> On Fri, 10 Jun 2022 12:21:37 +0200 Christian Göttsche wrote:
> > Package: nftables
> > Version: 1.0.4-1
> > Severity: serious
> >
> > Dear Maintainer,
> >
> > upgrades of nftables stop the service but do not start it (even if the
> > service is actually enabled).
> > This can lead to lockouts, e.g. when using special rules for ssh access.
> >
> >
> > nft.preinst:
> >
> > #!/bin/sh
> > set -e
> > # Automatically added by dh_installsystemd/13.7.1
> > if [ -z "${DPKG_ROOT:-}" ] && [ "$1" = upgrade ] && [ -d
> > /run/systemd/system ] ; then
> >deb-systemd-invoke stop 'nftables.service' >/dev/null || true
> > fi
> > # End automatically added section
> >
> >
> > nft.postinst:
> >
> > #!/bin/sh
> > set -e
> > # Automatically added by dh_installsystemd/13.7.1
> > if [ "$1" = "configure" ] || [ "$1" = "abort-upgrade" ] || [ "$1" =
> > "abort-deconfigure" ] || [ "$1" = "abort-remove" ] ; then
> >if deb-systemd-helper debian-installed 'nftables.service'; then
> ># This will only remove masks created by d-s-h on package
> > removal.
> >deb-systemd-helper unmask 'nftables.service' >/dev/null ||
> > true
> >
> >if deb-systemd-helper --quiet was-enabled
> > 'nftables.service'; then
> ># Create new symlinks, if any.
> >deb-systemd-helper enable 'nftables.service'
> > >/dev/null || true
> >fi
> >fi
> >
> ># Update the statefile to add new symlinks (if any), which need to
> > be cleaned
> ># up on purge. Also remove old symlinks.
> >deb-systemd-helper update-state 'nftables.service' >/dev/null || true
> > fi
> > # End automatically added section
>
> I confirmed this can be a problem:
>
> [...]
>
> @Alberto, @Jeremy,
>
> It seems to me like we need to play with the dh_installsystemd
> --no-restart-after-upgrade option, but don't have time to figure out the
> right logic.
>
> I'm currently unable to handle this. Could you please take a look?
Passing `--restart-after-upgrade` does the trick:
diff -u nftables_1.0.4-1/postinst nftables_1.0.4-2/postinst
--- nftables_1.0.4-1/postinst 2022-06-07 23:59:59.0 +0100
+++ nftables_1.0.4-2/postinst 2022-06-19 18:04:19.0 +0100
@@ -17,3 +17,13 @@
deb-systemd-helper update-state 'nftables.service' >/dev/null || true
fi
# End automatically added section
+# Automatically added by dh_installsystemd/13.7.1
+if [ "$1" = "configure" ] || [ "$1" = "abort-upgrade" ] || [ "$1" =
"abort-deconfigure" ] || [ "$1" = "abort-remove" ] ; then
+ if [ -z "${DPKG_ROOT:-}" ] && [ -d /run/systemd/system ]; then
+ systemctl --system daemon-reload >/dev/null || true
+ if [ -n "$2" ]; then
+ deb-systemd-invoke try-restart 'nftables.service'
>/dev/null || true
+ fi
+ fi
+fi
+# End automatically added section
I've pushed that and a few other changes to Salsa.
J.
signature.asc
Description: PGP signature
Bug#779364: pan: Crash when opening article with layered attachments
Hello Karl On Sun, 1 Mar 2015 10:31:13 -0800 (PST) Karl Kornel wrote: > I am having an issue with Pan, where it is crashing when I try to open certain > articles. In 2015, you reported a bug on Pan which crashed when opening some articles. The backtrace shows a problem with g_mime_multipart_encrypted_decrypt (). I guess that the crash was triggered by utf-8 encoded character that can be found in the article mentioned in the bug report [1]. A lot of related to utf-8 and gmime are now fixed in Pan which is now v.0150. Could you try again ? If not, if the leland group public ? We hope to be able to reproduce this bug. All the best [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=779364
Bug#1013236: atop should not listen on 0.0.0.0 by default
Package: atop
Version: 2.7.1-1
Severity: important
X-Debbugs-Cc: witold.bary...@gmail.com
$ sudo ss -lnp | awk '$5 ~ /\[::\]|0\.0\.0\.0:|\*:/ { print $0; }' | grep atop
??? UNCONN 0 0 0.0.0.0:255
0.0.0.0:*users:(("atop",pid=2185,fd=3))
$
That should not be a default. Please make it listen on "localhost" ([::1]
+ 127.0.0.1) only by default, or even disable this by default.
I belive this is a regression in last few months, as I didn't see atop
listening in the past.
Also I have no idea why atop listens on this port. It is not documented
in atop --help, or manpage.
-- System Information:
Debian Release: bookworm/sid
APT prefers testing-debug
APT policy: (500, 'testing-debug'), (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 5.18.5 (SMP w/32 CPU threads; PREEMPT)
Kernel taint flags: TAINT_WARN, 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)
Versions of packages atop depends on:
ii init-system-helpers 1.63
ii libc62.33-7
ii libncursesw6 6.3+20220423-2
ii libtinfo66.3+20220423-2
ii lsb-base 11.2
ii zlib1g 1:1.2.11.dfsg-4
Versions of packages atop recommends:
ii cron [cron-daemon] 3.0pl1-144
atop suggests no packages.
-- no debconf information
Bug#1011271: nvidia-graphics-drivers-legacy-390xx 390.151-1~deb11u1 flagged for acceptance
package release.debian.org tags 1011271 = bullseye pending thanks Hi, The upload referenced by this bug report has been flagged for acceptance into the proposed-updates queue for Debian bullseye. Thanks for your contribution! Upload details == Package: nvidia-graphics-drivers-legacy-390xx Version: 390.151-1~deb11u1 Explanation: new upstream release; fix out-of-bound write issues [CVE-2022-28181 CVE-2022-28185]
Bug#1011272: nvidia-graphics-drivers-legacy-390xx 390.151-1~deb10u1 flagged for acceptance
package release.debian.org tags 1011272 = 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: nvidia-graphics-drivers-legacy-390xx Version: 390.151-1~deb10u1 Explanation: new upstream release; fix out-of-bound write issues [CVE-2022-28181 CVE-2022-28185]
Bug#1013235: RM: fexoticoptions -- RoM: Retired upstream
Package: ftp.debian.org Severity: normal The fexoticoptions package (binary: r-cran-fexoticoptions) is no longer on CRAN and can be removed from unstable as well. If needed, old versions remain at https://cran.r-project.org/web/packages/fExoticOptions/index.html Dirk -- dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org
Bug#1013234: RM: fasionoptions -- RoM: Retired upstream
Package: ftp.debian.org Severity: normal The fasianoptions package (binary: r-cran-fasianoptions) is no longer on CRAN and can be removed from unstable as well. If needed, old versions remain at https://cran.r-project.org/web/packages/fAsianOptions/index.html Dirk -- dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org
Bug#1013233: RM: flask-script -- RoQA; dead upstream; incompatible with modern flask; FTBFS; no rdeps
Package: ftp.debian.org Severity: normal X-Debbugs-Cc: mo...@debian.org Hello, please process this removal of a dead leaf package. thanks!
Bug#1013227: qjackctl cannot be installed on a pipewire only system
Another option is to use the qpwgraph package On 19 June 2022 14:36:27 BST, Daniel Savi wrote: >Package: qjackctl >Severity: important >X-Debbugs-Cc: pub...@gaess.ch > >Dear Maintainer, > >I'm running a system on bookworm with pipewire only as sound server. According >to the pipewire documentation, qjackctl would be the best tool to manage sound >pipes also with pipewire. Because qjackctl depends on jackd only, it cannot be >installed without installing jackd as well. Please add an alternative >dependency for pipewire as well. >Kind regards and thanks for the good work. > > >-- System Information: >Debian Release: bookworm/sid > APT prefers testing > APT policy: (500, 'testing') >Architecture: amd64 (x86_64) > >Kernel: Linux 5.18.0-1-amd64 (SMP w/4 CPU threads; PREEMPT) >Locale: LANG=de_CH.UTF-8, LC_CTYPE=de_CH.UTF-8 (charmap=UTF-8), >LANGUAGE=de_CH:de >Shell: /bin/sh linked to /usr/bin/dash >Init: systemd (via /run/systemd/system) >LSM: AppArmor: enabled > >Versions of packages qjackctl depends on: >pn jackd >ii libasound21.2.6.1-2+b1 >ii libc6 2.33-7 >ii libgcc-s1 12.1.0-2 >ii libjack-jackd2-0 [libjack-0.125] 1.9.21~dfsg-1 >ii libqt5core5a 5.15.2+dfsg-16+b2 >ii libqt5dbus5 5.15.2+dfsg-16+b2 >ii libqt5gui55.15.2+dfsg-16+b2 >ii libqt5network55.15.2+dfsg-16+b2 >ii libqt5widgets55.15.2+dfsg-16+b2 >ii libqt5xml55.15.2+dfsg-16+b2 >ii libstdc++612.1.0-2 > >qjackctl recommends no packages. > >Versions of packages qjackctl suggests: >pn pulseaudio-utils >
Bug#820625: [wrap-and-sort] removes all comments from debian/control
Re: Niels Thykier > As of devscripts/2.22.2 (currently in unstable), we now have a temporary > option called "--experimental-rts-parser" that should solve this > problem. Please try it out and report your successes/problems back to > this bug. Hi, running on postgresql-common's debian/control, the new option preserves the comment present in the file, while omitting the option removes the comment. Thanks, Christoph
Bug#1013232: maxima: Incorrect remainder evaluation with unbound variables
Package: maxima Version: 5.46.0-2 Severity: normal Tags: upstream X-Debbugs-Cc: t.duehr...@gmx.net Dear Maintainer, entering 2 * remainder(45, 7); returns 6, as expected. But using an unbound variable, a in this case, 2 * remainder(45, a); returns 90, which is incorrect. The input should be returned unchanged. -- System Information: Debian Release: bookworm/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 5.18.0-1-amd64 (SMP w/1 CPU thread; PREEMPT) Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages maxima depends on: ii libc6 2.33-7 ii libedit2 3.1-20210910-1 ii libgmp10 2:6.2.1+dfsg1-1 ii libtirpc3 1.3.2-2 ii libx11-6 2:1.7.5-1 Versions of packages maxima recommends: pn gnuplot-x11 pn maxima-share Versions of packages maxima suggests: pn maxima-doc pn maxima-emacs pn texmacs pn wish pn xmaxima -- no debconf information
Bug#1013231: RFS: parsimonious/0.9.0-1 [ITP] -- fastest pure-Python PEG parser
Package: sponsorship-requests Severity: wishlist Dear mentors, I am looking for a sponsor for my package "parsimonious": * Package name: parsimonious Version : 0.9.0-1 Upstream Author : https://github.com/erikrose/parsimonious/issues * URL : https://github.com/erikrose/parsimonious/ * License : MIT * Vcs : https://salsa.debian.org/debian/python-parsimonious Section : python The source builds the following binary packages: python3-parsimonious - fastest pure-Python PEG parser To access further information about this package, please visit the following URL: https://mentors.debian.net/package/parsimonious/ Alternatively, you can download the package with 'dget' using this command: dget -x https://mentors.debian.net/debian/pool/main/p/parsimonious/parsimonious_0.9.0-1.dsc git -x https://salsa.debian.org/nilsonfsilva/python-parsimonious Changes for the initial release: parsimonious (0.9.0-1) experimental; urgency=medium . * Initial release. (Closes: #1009671) Regards, -- Josenilson Ferreira da SIlva Nilson F. Silva 81-3036-0200 81-991616348 81-98546-9553
Bug#1003353: tagging 1012326, tagging 1012690, tagging 1012464, tagging 1001317, tagging 1012221, tagging 1011807 ...
Control: notfound 1003353 2.114.0 Hi Andreas, Andreas Beckmann wrote: > found 1003353 2.114.0 please explain what makes you think that this issue is present in lintian 2.114.0 as currently in Debian Unstable. The submitter clearly said he ran into it when he bumped his lintian copy to git HEAD. And as far as I can see that problem is only present if Lintian uses Text::Glob for evaluating wildcards in overrides and that got introduced 32 commits _AFTER_ the 2.114.0 release: commit 139009d5a54225ebff4509ec37b979cb898c17fe Author: Felix Lechner Date: Wed Dec 1 21:46:24 2021 -0800 Use Text::Glob to match hint contexts with override patterns. Replaces a trusted homegrown routine. Gbp-Dch: ignore (No idea why this was marked "Gbp-Dch: Ignore" as it has quite some impact, also on dependencies and build-dependencies. *grrr*) And: ~/lintian/lintian → git describe 139009d5a54225ebff4509ec37b979cb898c17fe 2.114.0-32-g139009d5a ^^ Which is the reason why I marked this bug report as NOT being found in 2.114.0 a few days ago. (And now again.) So please refrain from marking this specific bug report as found in 2.114.0 again unless you have a really good reason to do so. Thanks in advance! Regards, Axel -- ,''`. | Axel Beckert , https://people.debian.org/~abe/ : :' : | Debian Developer, ftp.ch.debian.org Admin `. `' | 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5 `-| 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE signature.asc Description: PGP signature
Bug#1013230: qqwing: Improved random number generation to allow running multiple instances of the program in parallel.
Package: qqwing
Version: 1.3.4-1.1+b1
Severity: important
Tags: patch
X-Debbugs-Cc: krzpyrk...@gmail.com
Dear Maintainer,
Current version of qqwing uses srand(time(0)) and rand() as a way to
generate the board. It makes running multiple instances of the program
in parallel for faster sudoku generation impossible, because all are
started in the same second, generating exactly the same sequence of
numbers, and as a result, sequence of boards.
The solution is to replace the randomness based on time with one based on
a truly random seed, and rand() with a random generator that does not
rely on a global state like srand.
My patch makes use of several C++11 features such as std::random_device,
std::uniform_int_distribution and std::shuffle that are state of the art
solutions to the aforementioned issue.
diff --git a/main.cpp b/main.cpp
index 13a4355..ae1def7 100644
--- a/main.cpp
+++ b/main.cpp
@@ -200,9 +200,6 @@ int main(int argc, char *argv[]){
return 1;
}
- // Initialize the random number generator
- srand ( unsigned ( time(0) ) );
-
// If printing out CSV, print a header
if (printStyle == SudokuBoard::CSV){
if (printPuzzle) cout << "Puzzle,";
diff --git a/qqwing.cpp b/qqwing.cpp
index ed18ff0..a923398 100644
--- a/qqwing.cpp
+++ b/qqwing.cpp
@@ -23,6 +23,7 @@
#include
#include
+#include
#include "qqwing.hpp"
@@ -109,6 +110,7 @@ namespace qqwing {
* Create a new Sudoku board
*/
SudokuBoard::SudokuBoard() :
+ rand_generator(random_device{}()),
puzzle ( new int[BOARD_SIZE] ),
solution ( new int[BOARD_SIZE] ),
solutionRound ( new int[BOARD_SIZE] ),
@@ -1528,18 +1530,13 @@ namespace qqwing {
/**
* Shuffle the values in an array of integers.
*/
- void shuffleArray(int* array, int size){
- {for (int i=0; i dist(0, 3);
+ switch (dist(rand_generator)){
case 0: return SudokuBoard::ROTATE90;
case 1: return SudokuBoard::ROTATE180;
case 2: return SudokuBoard::MIRROR;
diff --git a/qqwing.hpp b/qqwing.hpp
index 54a7872..9a9c752 100644
--- a/qqwing.hpp
+++ b/qqwing.hpp
@@ -24,6 +24,7 @@
#include
#include
+ #include
namespace qqwing {
@@ -120,6 +121,13 @@
~SudokuBoard();
private:
+ /**
+* Random number generator seeded with true
randomness
+* in the constructor. Replacement for
srand(time(0)).
+* Now, multiple instances of the program
running
+* in parallel generate different boards.
+*/
+ std::mt19937 rand_generator;
/**
* The 81 integers that make up a sudoku puzzle.
* Givens are 1-9, unknowns are 0.
@@ -230,6 +238,8 @@
bool arePossibilitiesSame(int position1, int
position2);
void addHistoryItem(LogItem* l);
void shuffleRandomArrays();
+ void shuffleArray(int* array, int size);
+ SudokuBoard::Symmetry getRandomSymmetry();
void print(int* sudoku);
void rollbackNonGuesses();
void clearPuzzle();
Bug#1013229: wvdial: Verbose PPP debugging output cannot be enabled
Package: wvdial Version: 1.61-5 Severity: normal X-Debbugs-Cc: debbug.wvd...@sideload.33mail.com Connecting using a GSM mobile broadband USB modem succeeds but there are errors during the PPP handshake. When the “debug” option is uncommented in /etc/ppp/options as well as the “-detach” option, the ppp logging is no more verbose than without those options. They seem to take no effect. Is wvdial launching pppd in a way that interferes with parameters in /etc/ppp/options? This is the output both with and without debug info enabled: /var/log/messages: ===8<-- $timestamp $host pppd[84797]: pppd 2.4.9 started by $user, uid 0 $timestamp $host pppd[84797]: Using interface ppp0 $timestamp $host pppd[84797]: Connect: ppp0 <--> /dev/ttyUSB0 $timestamp $host pppd[84797]: LCP: timeout sending Config-Requests $timestamp $host pppd[84797]: Connection terminated. $timestamp $host pppd[84797]: Modem hangup $timestamp $host pppd[84797]: Exit. -->8=== /etc/wvdial.conf: ===8<-- [Dialer Defaults] StupidMode = 1 Modem Type = Analog Modem Baud = 460800 New PPPD = yes Modem = /dev/ttyUSB0 ISDN = 0 Init1 = ATZ Init2 = ATQ0 V1 E1 S0=0 +FCLASS=0 [Dialer Orange] Init3 = AT+CGDCONT=1,"IP","mworld.be",,0,0 Phone = *99# Mcc = 206 Mnc = 10 Username = '' Password = '' Carrier Check = off -->8=== /etc/ppp/options: ===8<-- asyncmap 0 auth crtscts lock hide-password modem debug -detach nodetach lcp-echo-interval 30 lcp-echo-failure 4 noipx -->8=== -- System Information: Debian Release: 11.0 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-8-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 wvdial depends on: ii debconf [debconf-2.0] 1.5.77 ii libc6 2.31-13 ii libgcc-s1 [libgcc1] 10.2.1-6 ii libstdc++6 10.2.1-6 ii libuniconf4.6 4.6.1-15 ii libwvstreams4.6-base4.6.1-15 ii libwvstreams4.6-extras 4.6.1-15 ii ppp 2.4.9-1+1 wvdial recommends no packages. wvdial suggests no packages. -- debconf information excluded
Bug#1013228: python-werkzeug: Please keep version < 2.1
Package: python-werkzeug Version: 2.0.2+dfsg1-1 Severity: wishlist Please keep the werkzeug version < 2.1 because that is currently needed for the crossbar package: https://github.com/labgrid-project/labgrid/commit/8c17101400cb2be587d104e1aa32acd592b4ea65 I will inform you via this bug when this limit is gone.
Bug#1013227: qjackctl cannot be installed on a pipewire only system
Package: qjackctl Severity: important X-Debbugs-Cc: pub...@gaess.ch Dear Maintainer, I'm running a system on bookworm with pipewire only as sound server. According to the pipewire documentation, qjackctl would be the best tool to manage sound pipes also with pipewire. Because qjackctl depends on jackd only, it cannot be installed without installing jackd as well. Please add an alternative dependency for pipewire as well. Kind regards and thanks for the good work. -- System Information: Debian Release: bookworm/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 5.18.0-1-amd64 (SMP w/4 CPU threads; PREEMPT) Locale: LANG=de_CH.UTF-8, LC_CTYPE=de_CH.UTF-8 (charmap=UTF-8), LANGUAGE=de_CH:de Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages qjackctl depends on: pn jackd ii libasound21.2.6.1-2+b1 ii libc6 2.33-7 ii libgcc-s1 12.1.0-2 ii libjack-jackd2-0 [libjack-0.125] 1.9.21~dfsg-1 ii libqt5core5a 5.15.2+dfsg-16+b2 ii libqt5dbus5 5.15.2+dfsg-16+b2 ii libqt5gui55.15.2+dfsg-16+b2 ii libqt5network55.15.2+dfsg-16+b2 ii libqt5widgets55.15.2+dfsg-16+b2 ii libqt5xml55.15.2+dfsg-16+b2 ii libstdc++612.1.0-2 qjackctl recommends no packages. Versions of packages qjackctl suggests: pn pulseaudio-utils
Bug#1008415: libnih: FTBFS: dh_auto_test: error: make -j8 check VERBOSE=1 returned exit code 2
Hi Marius, Marius Gripsgard wrote: > libnih has been removed as dependency for lomiri-donwload-manager > for a good while upstream [0] Ah, nice! > but has not had a release with this in it yet. So I make a new > released lomiri-download-manager 0.1.1 with libnih removed as dep, > and uploaded this to unstable. Yay! Thanks a lot. > So nih can be removed IMO. Done so now: https://bugs.debian.org/1013225 Regards, Axel -- ,''`. | Axel Beckert , https://people.debian.org/~abe/ : :' : | Debian Developer, ftp.ch.debian.org Admin `. `' | 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5 `-| 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE signature.asc Description: PGP signature
Bug#1013226: RFP: python-stringcase -- Convert strings between camel case, pascal case, snake case etc.
Package: wnpp Severity: wishlist * Package name: python-stringcase Version : 1.2.0 Upstream Author : Taka Okunishi * URL : https://github.com/okunishinishi/python-stringcase * License : Expat Programming Lang: Python Description : Convert strings between camel case, pascal case, snake case etc. This simple string conversion library is needed to update crossbar to a later upstream version. It should be maintained in the Python Team.
Bug#1009671:
Control: retitle -1 ITP: python-parsimonious -- fastest pure-Python PEG parser
Bug#1012613: nftables: upgrade stops but does not start service
On 2022-06-19, at 13:48:59 +0200, Arturo Borrero Gonzalez wrote:
> On Fri, 10 Jun 2022 12:21:37 +0200 Christian Göttsche wrote:
> > Package: nftables
> > Version: 1.0.4-1
> > Severity: serious
> >
> > Dear Maintainer,
> >
> > upgrades of nftables stop the service but do not start it (even if the
> > service is actually enabled).
> > This can lead to lockouts, e.g. when using special rules for ssh access.
> >
> >
> > nft.preinst:
> >
> > #!/bin/sh
> > set -e
> > # Automatically added by dh_installsystemd/13.7.1
> > if [ -z "${DPKG_ROOT:-}" ] && [ "$1" = upgrade ] && [ -d
> > /run/systemd/system ] ; then
> >deb-systemd-invoke stop 'nftables.service' >/dev/null || true
> > fi
> > # End automatically added section
> >
> >
> > nft.postinst:
> >
> > #!/bin/sh
> > set -e
> > # Automatically added by dh_installsystemd/13.7.1
> > if [ "$1" = "configure" ] || [ "$1" = "abort-upgrade" ] || [ "$1" =
> > "abort-deconfigure" ] || [ "$1" = "abort-remove" ] ; then
> >if deb-systemd-helper debian-installed 'nftables.service'; then
> ># This will only remove masks created by d-s-h on package
> > removal.
> >deb-systemd-helper unmask 'nftables.service' >/dev/null ||
> > true
> >
> >if deb-systemd-helper --quiet was-enabled
> > 'nftables.service'; then
> ># Create new symlinks, if any.
> >deb-systemd-helper enable 'nftables.service'
> > >/dev/null || true
> >fi
> >fi
> >
> ># Update the statefile to add new symlinks (if any), which need to
> > be cleaned
> ># up on purge. Also remove old symlinks.
> >deb-systemd-helper update-state 'nftables.service' >/dev/null || true
> > fi
> > # End automatically added section
>
> I confirmed this can be a problem:
>
> [...]
>
> @Alberto, @Jeremy,
>
> It seems to me like we need to play with the dh_installsystemd
> --no-restart-after-upgrade option, but don't have time to figure out the
> right logic.
>
> I'm currently unable to handle this. Could you please take a look?
Yup.
J.
signature.asc
Description: PGP signature
Bug#1009671: (ITP: python-parsimonious -- fastest pure-Python PEG parser)
Control: retitle -1 ITP: python-parsimonious -- fastest pure-Python PEG parser Am 19.06.22 um 15:07 schrieb Nilson Silva: Hello Bastian! Certainly
Bug#1013225: RM: libnih -- RoQA; RC buggy, orphaned, upstream dead, no more reverse deps
Package: ftp.debian.org Severity: normal X-Debbugs-Cc: Axel Beckert , Marius Gripsgard , Mike Gabriel Hi, libnih is: * orphaned since 2016: https://bugs.debian.org/826286 * RC buggy (FTBFS due to test suite failures) since March and nobody cares (except for getting rid of it): https://bugs.debian.org/1008415 * upstream dead since 2012-ish: https://code.launchpad.net/libnih * reverse-dependency-free as the last reverse dependency has dropped its dependency on libnih, see https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008415#20 and https://tracker.debian.org/news/1338387/accepted-lomiri-download-manager-011-1-source-into-unstable/ So please finally remove it from Unstable.
Bug#1009671: (ITP: python-parsimonious -- fastest pure-Python PEG parser)
Hi Nilson, I need parsimonious for a new crossbar version. Do you still want to package it? Thanks, Bastian
Bug#444714: wvdial: comments start with hash (“#”)
Package: wvdial Version: 1.61-5 Followup-For: Bug #444714 X-Debbugs-Cc: bug639...@sideload.33mail.com Indeed the README still shows semicolons to designate comments. So the README still needs to be updated. I find that the hash symbol works for comments so that’s the workaround. -- System Information: Debian Release: 11.0 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-8-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 wvdial depends on: ii debconf [debconf-2.0] 1.5.77 ii libc6 2.31-13 ii libgcc-s1 [libgcc1] 10.2.1-6 ii libstdc++6 10.2.1-6 ii libuniconf4.6 4.6.1-15 ii libwvstreams4.6-base4.6.1-15 ii libwvstreams4.6-extras 4.6.1-15 ii ppp 2.4.9-1+1 wvdial recommends no packages. wvdial suggests no packages. -- debconf information excluded
Bug#1013224: ITP: qt6-languageserver -- An implementation of the Language Server Protocol
Package: wnpp Severity: wishlist Owner: Patrick Franz X-Debbugs-Cc: debian-de...@lists.debian.org, delta...@debian.org, debian-qt-...@lists.debian.org * Package name: qt6-languageserver Version : 6.3.0 Upstream Author : The Qt Company Ltd. * URL : https://www.qt.io/developers/ * License : GPL, LGPL Programming Lang: C++ Description : An implementation of the Language Server Protocol Qt is a cross-platform C++ application framework. Qt's primary feature is its rich set of widgets that provide standard GUI functionality. This module implements the Language Server Protocol Specification and the JsonRpc 2.0 protocol.
Bug#1013223: bird2: FTBFS on arm64: make[1]: *** [Makefile:180: obj/lib/bitmap_test.ok] Error 1
Source: bird2 Version: 2.0.9-3 Severity: serious Tags: ftbfs sid bookworm Justification: fails to build from source (but built successfully in the past) X-Debbugs-Cc: sramac...@debian.org https://buildd.debian.org/status/fetch.php?pkg=bird2=arm64=2.0.9-3=1649868353=0 obj/lib/bitmap_test: t_hmap_set_clear_fill 5.023173111s [FAIL] obj/lib/bitmap_test 6.241085926s [FAIL] make[1]: *** [Makefile:180: obj/lib/bitmap_test.ok] Error 1 make[1]: *** Waiting for unfinished jobs In function ‘memcpy’, inlined from ‘nl_add_attr’ at sysdep/linux/netlink.c:598:5, inlined from ‘nl_add_attr_ip6’ at sysdep/linux/netlink.c:638:3, inlined from ‘nl_send_route’ at sysdep/linux/netlink.c:1381:7: /usr/include/aarch64-linux-gnu/bits/string_fortified.h:29:10: warning: writing 16 bytes into a region of size 12 [-Wstringop-overflow=] 29 | return __builtin___memcpy_chk (__dest, __src, __len, | ^ sysdep/linux/netlink.c: In function ‘nl_send_route’: sysdep/linux/netlink.c:1338:21: note: at offset [4, 16] into destination object ‘h’ of size 16 1338 | struct nlmsghdr h; | ^ In function ‘memcpy’, inlined from ‘nl_add_attr’ at sysdep/linux/netlink.c:598:5, inlined from ‘nl_add_attr_ip6’ at sysdep/linux/netlink.c:638:3, inlined from ‘nl_add_attr_ipa’ at sysdep/linux/netlink.c:647:5, inlined from ‘nl_send_route’ at sysdep/linux/netlink.c:1423:5: /usr/include/aarch64-linux-gnu/bits/string_fortified.h:29:10: warning: writing 16 bytes into a region of size 12 [-Wstringop-overflow=] 29 | return __builtin___memcpy_chk (__dest, __src, __len, | ^ sysdep/linux/netlink.c: In function ‘nl_send_route’: sysdep/linux/netlink.c:1338:21: note: at offset [4, 16] into destination object ‘h’ of size 16 1338 | struct nlmsghdr h; | ^ In function ‘memcpy’, inlined from ‘nl_add_attr’ at sysdep/linux/netlink.c:598:5, inlined from ‘nl_add_attr_ip6’ at sysdep/linux/netlink.c:638:3, inlined from ‘nl_send_route’ at sysdep/linux/netlink.c:1381:7: /usr/include/aarch64-linux-gnu/bits/string_fortified.h:29:10: warning: writing 16 bytes into a region of size 12 [-Wstringop-overflow=] 29 | return __builtin___memcpy_chk (__dest, __src, __len, | ^ sysdep/linux/netlink.c: In function ‘nl_send_route’: sysdep/linux/netlink.c:1338:21: note: at offset [4, 16] into destination object ‘h’ of size 16 1338 | struct nlmsghdr h; | ^ In function ‘memcpy’, inlined from ‘nl_add_attr’ at sysdep/linux/netlink.c:598:5, inlined from ‘nl_add_attr_ip6’ at sysdep/linux/netlink.c:638:3, inlined from ‘nl_add_attr_ipa’ at sysdep/linux/netlink.c:647:5, inlined from ‘nl_send_route’ at sysdep/linux/netlink.c:1423:5: /usr/include/aarch64-linux-gnu/bits/string_fortified.h:29:10: warning: writing 16 bytes into a region of size 12 [-Wstringop-overflow=] 29 | return __builtin___memcpy_chk (__dest, __src, __len, | ^ sysdep/linux/netlink.c: In function ‘nl_send_route’: sysdep/linux/netlink.c:1338:21: note: at offset [4, 16] into destination object ‘h’ of size 16 1338 | struct nlmsghdr h; | ^ In function ‘memcpy’, inlined from ‘nl_add_attr’ at sysdep/linux/netlink.c:598:5, inlined from ‘nl_add_attr_ip6’ at sysdep/linux/netlink.c:638:3, inlined from ‘nl_send_route’ at sysdep/linux/netlink.c:1381:7: /usr/include/aarch64-linux-gnu/bits/string_fortified.h:29:10: warning: writing 16 bytes into a region of size 12 [-Wstringop-overflow=] 29 | return __builtin___memcpy_chk (__dest, __src, __len, | ^ sysdep/linux/netlink.c: In function ‘nl_send_route’: sysdep/linux/netlink.c:1338:21: note: at offset [4, 16] into destination object ‘h’ of size 16 1338 | struct nlmsghdr h; | ^ In function ‘memcpy’, inlined from ‘nl_add_attr’ at sysdep/linux/netlink.c:598:5, inlined from ‘nl_add_attr_ip6’ at sysdep/linux/netlink.c:638:3, inlined from ‘nl_add_attr_ipa’ at sysdep/linux/netlink.c:647:5, inlined from ‘nl_send_route’ at sysdep/linux/netlink.c:1423:5: /usr/include/aarch64-linux-gnu/bits/string_fortified.h:29:10: warning: writing 16 bytes into a region of size 12 [-Wstringop-overflow=] 29 | return __builtin___memcpy_chk (__dest, __src, __len, | ^ sysdep/linux/netlink.c: In function ‘nl_send_route’: sysdep/linux/netlink.c:1338:21: note: at offset [4, 16] into destination object ‘h’ of size 16 1338 | struct nlmsghdr h; | ^ make[1]: Leaving directory '/<>' dh_auto_test: error: make -j8 test VERBOSE=1 returned exit code 2 Cheers -- Sebastian Ramacher
Bug#1013222: src:qt6-wayland: please package private headers
Source: qt6-wayland Severity: wishlist Dear Maintainer, Please package private QtWaylandClient headers and related CMake config. Telegram authors offer a forked plugin for XDG shell integration. In order to build the telegram-desktop package against Qt6 keeping all features with Wayland, the headers are necessary. signature.asc Description: This is a digitally signed message part.
Bug#1012447: coreutils: tr: tr.1 (and tr --help) falsely claims -t is only valid when translating
On 07/06/2022 13:41, наб wrote:
Package: coreutils
Version: 8.32-4.1
Severity: minor
File: /usr/bin/tr
Dear Maintainer,
The soup at the end of tr.1 (and tr --help) claims:
-t may be used only when translating.
This is a very obvious lie:
$ tr -tds abcd A
aabbccddAA
A
Of course, -t only changes anything when translating,
because heirloom tr uses separate tables for tr/-d/-s
and explicitly handles overlong set2 for squeezing,
but it can be specified whenever
(just doesn't do anything unless translating).
Fair point.
Will address this upstream in the attached.
thanks,
Pádraig
From 2616c03a616804e9832e6412474013cd2c6c339e Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?P=C3=A1draig=20Brady?=
Date: Sun, 19 Jun 2022 13:18:01 +0100
Subject: [PATCH] doc: tr: clarify that -t is ignored unless translating
* src/tr.c (usage): Don't say that -t is disallowed unless translating.
Reported in https://bugs.debian.org/1012447
---
src/tr.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/src/tr.c b/src/tr.c
index e2aa33e76..59b0969d2 100644
--- a/src/tr.c
+++ b/src/tr.c
@@ -340,7 +340,7 @@ Interpreted sequences are:\n\
fputs (_("\
\n\
Translation occurs if -d is not given and both STRING1 and STRING2 appear.\n\
--t may be used only when translating. ARRAY2 is extended to length of\n\
+-t is only significant when translating. ARRAY2 is extended to length of\n\
ARRAY1 by repeating its last character as necessary. Excess characters\n\
of ARRAY2 are ignored. Character classes expand in unspecified order;\n\
while translating, [:lower:] and [:upper:] may be used in pairs to\n\
--
2.26.2
Bug#639368: ppp: confirmed verbosity problem in v. 2.4.9-1+1
Package: ppp Version: 2.4.9-1+1 Followup-For: Bug #639368 X-Debbugs-Cc: bug639...@sideload.33mail.com When the following options are supplied in /etc/ppp/options prior to running wvdial: * debug * -detach * nodetach output is normal (non-verbose). It’s unclear if this is the same bug as the 11 year old bug (639368) because the OP reports no output after the “pppd 2.4.5 started by root” line. Whereas I’m seeing a little more output but certainly not verbose. So this report was filed upstream: https://github.com/ppp-project/ppp/issues/352 -- System Information: Debian Release: 11.0 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-8-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 ppp depends on: ii libc6 2.31-13 ii libcrypt1 1:4.4.18-4 ii libpam-modules 1.4.0-9 ii libpam-runtime 1.4.0-9 ii libpam0g1.4.0-9 ii libpcap0.8 1.10.0-2 ii libssl1.1 1.1.1k-1 ii libsystemd0 247.3-6 ii procps 2:3.3.17-5 ppp recommends no packages. ppp suggests no packages. -- Configuration Files: /etc/ppp/options changed [not included] -- no debconf information
Bug#1012613: nftables: upgrade stops but does not start service
On Fri, 10 Jun 2022 12:21:37 +0200 =?UTF-8?Q?Christian_G=C3=B6ttsche?=
wrote:
Package: nftables
Version: 1.0.4-1
Severity: serious
Dear Maintainer,
upgrades of nftables stop the service but do not start it (even if the
service is actually enabled).
This can lead to lockouts, e.g. when using special rules for ssh access.
nft.preinst:
#!/bin/sh
set -e
# Automatically added by dh_installsystemd/13.7.1
if [ -z "${DPKG_ROOT:-}" ] && [ "$1" = upgrade ] && [ -d
/run/systemd/system ] ; then
deb-systemd-invoke stop 'nftables.service' >/dev/null || true
fi
# End automatically added section
nft.postinst:
#!/bin/sh
set -e
# Automatically added by dh_installsystemd/13.7.1
if [ "$1" = "configure" ] || [ "$1" = "abort-upgrade" ] || [ "$1" =
"abort-deconfigure" ] || [ "$1" = "abort-remove" ] ; then
if deb-systemd-helper debian-installed 'nftables.service'; then
# This will only remove masks created by d-s-h on
package removal.
deb-systemd-helper unmask 'nftables.service' >/dev/null || true
if deb-systemd-helper --quiet was-enabled
'nftables.service'; then
# Create new symlinks, if any.
deb-systemd-helper enable 'nftables.service'
>/dev/null || true
fi
fi
# Update the statefile to add new symlinks (if any), which need
to be cleaned
# up on purge. Also remove old symlinks.
deb-systemd-helper update-state 'nftables.service' >/dev/null || true
fi
# End automatically added section
I confirmed this can be a problem:
=== 8< ===
⌂0.65 arturo@nostromo:~ $ apt-cache policy nftables
nftables:
Installed: 1.0.2-1
Candidate: 1.0.4-1
Version table:
1.0.4-1 500
500 http://deb.debian.org/debian sid/main amd64 Packages
*** 1.0.2-1 500
500 http://deb.debian.org/debian testing/main amd64 Packages
100 /var/lib/dpkg/status
⌂0.68 arturo@nostromo:~ $ sudo systemctl status nftables
● nftables.service - nftables
Loaded: loaded (/lib/systemd/system/nftables.service; disabled;
vendor preset: enabled)
Active: active (exited) since Sun 2022-06-19 13:38:11 CEST; 51s ago
Docs: man:nft(8)
http://wiki.nftables.org
Process: 5537 ExecStart=/usr/sbin/nft -f /etc/nftables.conf
(code=exited, status=0/SUCCESS)
Main PID: 5537 (code=exited, status=0/SUCCESS)
CPU: 13ms
Jun 19 13:38:11 nostromo systemd[1]: Starting nftables...
Jun 19 13:38:11 nostromo systemd[1]: Finished nftables.
⌂0.70 arturo@nostromo:~ $ sudo nft list ruleset
table inet filter {
chain input {
type filter hook input priority filter; policy accept;
iif "lo" accept
ct state established,related accept
tcp dport 22 ct state new accept
ip6 nexthdr ipv6-icmp icmpv6 type { nd-router-advert,
nd-neighbor-solicit, nd-neighbor-advert } accept
counter packets 6 bytes 898 drop
}
}
⌂0.65 arturo@nostromo:~ $ sudo aptitude install nftables
The following packages will be upgraded:
libnftables1 nftables
2 packages upgraded, 0 newly installed, 0 to remove and 754 not upgraded.
Need to get 365 kB of archives. After unpacking 27.6 kB will be used.
Do you want to continue? [Y/n/?] Y
Get: 1 http://deb.debian.org/debian sid/main amd64 nftables amd64
1.0.4-1 [71.9 kB]
Get: 2 http://deb.debian.org/debian sid/main amd64 libnftables1 amd64
1.0.4-1 [294 kB]
Fetched 365 kB in 0s (4,064 kB/s)
Reading changelogs... Done
(Reading database ... 273043 files and directories currently installed.)
Preparing to unpack .../nftables_1.0.4-1_amd64.deb ...
Unpacking nftables (1.0.4-1) over (1.0.2-1) ...
Preparing to unpack .../libnftables1_1.0.4-1_amd64.deb ...
Unpacking libnftables1:amd64 (1.0.4-1) over (1.0.2-1) ...
Setting up libnftables1:amd64 (1.0.4-1) ...
Setting up nftables (1.0.4-1) ...
Processing triggers for man-db (2.10.2-1) ...
Processing triggers for libc-bin (2.33-7) ...
Current status: 754 (-2) upgradable.
⌂0.78 arturo@nostromo:~ $ sudo nft list ruleset
⌂0.78 arturo@nostromo:~ $ sudo systemctl status nftables
○ nftables.service - nftables
Loaded: loaded (/lib/systemd/system/nftables.service; disabled;
vendor preset: enabled)
Active: inactive (dead)
Docs: man:nft(8)
http://wiki.nftables.org
Jun 19 13:38:11 nostromo systemd[1]: Starting nftables...
Jun 19 13:38:11 nostromo systemd[1]: Finished nftables.
Jun 19 13:39:13 nostromo systemd[1]: Stopping nftables...
Jun 19 13:39:13 nostromo systemd[1]: nftables.service: Deactivated
successfully.
Jun 19 13:39:13 nostromo systemd[1]: Stopped nftables.
=== 8< ===
@Alberto, @Jeremy,
It seems to me like we need to play with the dh_installsystemd
--no-restart-after-upgrade option, but don't have time to figure out the
right logic.
I'm currently unable to handle this. Could you please take a look?
regards.
Bug#1012663: paraview: FTBFS in unstable (error: expected identifier or ‘(’ before numeric constant)
Control: tags -1 upstream patch Control: forwarded -1 https://gitlab.kitware.com/paraview/paraview/-/issues/21442 The attached patch resolves the issue by renaming the conflicting variable. Kind Regards, Bas -- GPG Key ID: 4096R/6750F10AE88D4AF1 Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1Description: Fix FTBFS with NetCDF 4.9.0. Author: Bas Couwenberg Bug-Debian: https://bugs.debian.org/1012663 Forwarded: https://gitlab.kitware.com/paraview/paraview/-/issues/21442 --- a/VTK/ThirdParty/exodusII/vtkexodusII/src/ex_utils.c +++ b/VTK/ThirdParty/exodusII/vtkexodusII/src/ex_utils.c @@ -1770,11 +1770,11 @@ void ex__compress_variable(int exoid, in */ /* const int NC_SZIP_EC = 4; */ /* Selects entropy coding method for szip. */ -const int NC_SZIP_NN = 32; /* Selects nearest neighbor coding method for szip. */ +const int NC_SZIP_NN_ = 32; /* Selects nearest neighbor coding method for szip. */ /* Even and between 4 and 32; typical values are 8, 10, 16, 32 */ const int SZIP_PIXELS_PER_BLOCK = file->compression_level == 0 ? 32 : file->compression_level; -nc_def_var_szip(exoid, varid, NC_SZIP_NN, SZIP_PIXELS_PER_BLOCK); +nc_def_var_szip(exoid, varid, NC_SZIP_NN_, SZIP_PIXELS_PER_BLOCK); #else char errmsg[MAX_ERR_LENGTH]; snprintf(errmsg, MAX_ERR_LENGTH,
Bug#1013035: sgt-puzzles: ftbfs with GCC-12
On Thu, 2022-06-16 at 12:13 +, Matthias Klose wrote: [...] > In file included from /usr/include/string.h:519, > from mines.c:12: > In function ‘memset’, > inlined from ‘new_game’ at mines.c:2257:2: > /usr/include/x86_64-linux-gnu/bits/string_fortified.h:59:10: error: > ‘__builtin_memset’ specified size between 18446744071562067968 and > 18446744073709551615 exceeds maximum object size 9223372036854775807 > [-Werror=stringop-overflow=] >59 | return __builtin___memset_chk (__dest, __ch, __len, > | ^~~~ >60 | __glibc_objsize0 (__dest)); > | ~~ > mines.c: In function ‘new_game’: > mines.c:2257:29: note: destination object allocated here > 2257 | memset(state->layout->mines, 0, wh * sizeof(bool)); > |~^~~ [...] This warning is nonsense, isn't it? It's claiming that memset() is the allocation site. And the length (wh) is the result of multiplying two integers that have been range-checked (though not in this function). I should patch out the use of -Werror in this package though. Ben. -- Ben Hutchings The most exhausting thing in life is being insincere. - Anne Morrow Lindberg signature.asc Description: This is a digitally signed message part
Bug#1012703: vtk9: FTBFS with NetCDF 4.9.0 (error: expected identifier or '(' before numeric constant)
Control: tags -1 upstream patch Control: forwarded -1 https://gitlab.kitware.com/vtk/vtk/-/issues/18576 The attached patch resolves the issue by renaming the conflicting variable. Kind Regards, Bas -- GPG Key ID: 4096R/6750F10AE88D4AF1 Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1Description: Fix FTBFS with NetCDF 4.9.0. Author: Bas Couwenberg Bug-Debian: https://bugs.debian.org/1012703 Forwarded: https://gitlab.kitware.com/vtk/vtk/-/issues/18576 --- a/ThirdParty/exodusII/vtkexodusII/src/ex_utils.c +++ b/ThirdParty/exodusII/vtkexodusII/src/ex_utils.c @@ -1770,11 +1770,11 @@ void ex__compress_variable(int exoid, in */ /* const int NC_SZIP_EC = 4; */ /* Selects entropy coding method for szip. */ -const int NC_SZIP_NN = 32; /* Selects nearest neighbor coding method for szip. */ +const int NC_SZIP_NN_ = 32; /* Selects nearest neighbor coding method for szip. */ /* Even and between 4 and 32; typical values are 8, 10, 16, 32 */ const int SZIP_PIXELS_PER_BLOCK = file->compression_level == 0 ? 32 : file->compression_level; -nc_def_var_szip(exoid, varid, NC_SZIP_NN, SZIP_PIXELS_PER_BLOCK); +nc_def_var_szip(exoid, varid, NC_SZIP_NN_, SZIP_PIXELS_PER_BLOCK); #else char errmsg[MAX_ERR_LENGTH]; snprintf(errmsg, MAX_ERR_LENGTH,
Bug#1013219: texlive-lang-japanese: should downgrade fonts-ipa* to Recommends/Suggests
On 6/19/22 09:04, YOSHINO Yoshihito wrote: Hi, This package Depends on fonts-ipafont-* and fonts-ipaexfont-* packages, which are big and 42.7 MB in total. Since TexLive 2020 HaranoAji is the default font bundled in this package and it is preferred by kanji-config-updmap, I suppose those fonts can now be safely demoted to Recommends or even Suggests. I decided to use "suggests", b/c apt installs recommended packages in default installation. Fix will be in next upload. Hilmar -- Testmail
Bug#1012741: modprobe: ERROR: could not insert 'crc_itu_t': Key was rejected by service
On Sat, 2022-06-18 at 16:21 +0200, Ben Hutchings wrote: > On Thu, 2022-06-16 at 01:28 +0200, Ben Hutchings wrote: > [...] > > > linux-image-4.19.0-17-amd64 4.19.194-1 > > lib/modules/4.19.0-17-amd64/kernel/drivers/dma/dw/dw_dmac_core.ko > > linux-image-4.19.0-17-amd64 4.19.194-2 > > lib/modules/4.19.0-17-amd64/kernel/drivers/dma/dw/dw_dmac_core.ko > > linux-image-4.19.0-17-amd64 4.19.194-3 > > lib/modules/4.19.0-17-amd64/kernel/drivers/dma/dw/dw_dmac_core.ko > [...] > > A significant pattern visible here is a short signature for the same > > module in multiple consecutive versions, where the module may have > > identical contents. That implies that this is a reproducible issue for > > certain inputs that cannot be worked around by re-running the signing > > process. > > > > However, I have *not* yet verified that all short signatures really are > > invalid. > > These module files are indeed identical, and their signatures are > rejected by the kernel. > > I'm now looking at whether the missing bytes are recoverable (e.g. are > they always zeroes). [...] I wrote a script to try all possible byte values for 2 bytes before or after the short signature. For this particular file, none of them producd a valid signature. So the short signatures seem to be corrupted in a more complex way. In the mean time, we have another security update coming which might not hit this bug again. But there are 28,679 signed binaries across the three architectures, so the probability is only about 65%. Ben. -- Ben Hutchings The most exhausting thing in life is being insincere. - Anne Morrow Lindberg signature.asc Description: This is a digitally signed message part
Bug#1013172: redis: Failed at step EXEC spawning /usr/bin/redis-server: Permission denied
tags 1013172 + pending thanks Hi Christian, > The reason is not the symlink but the library path /usr/lib, as this > happened on a system not converted to usrmerge. Ah, but of course! I would not have reached that diagnosis quickly (if it all), so that's some good insight. How did you think of that? Am uploading a fix now as part of redis 5:7.0.2-2. Once this lands, can you run "systemctl revert redis-server.service" and confirm that the stock/default .service file works for you? Thanks in advance... Best wishes, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org chris-lamb.co.uk `-
Bug#1013221: sendfile: /etc/cron.weekly job complains about deprecated tempfile
Package: sendfile
Version: 2.1b.20080616-8
Severity: normal
I'm getting an email weekly:
/etc/cron.weekly/sendfile:
WARNING: tempfile is deprecated; consider using mktemp instead.
Replacing the recommended action seems to fix the issue.
-- System Information:
Debian Release: 11.3
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 5.10.0-15-amd64 (SMP w/2 CPU threads)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/bash
Init: sysvinit (via /sbin/init)
Versions of packages sendfile depends on:
ii libc6 2.31-13+deb11u3
ii libdpkg-perl 1.20.10
ii libreadline8 8.1-1
ii openbsd-inetd [inet-superserver] 0.20160825-5
ii perl 5.32.1-4+deb11u2
ii update-inetd 4.51
sendfile recommends no packages.
Versions of packages sendfile suggests:
pn pgp-i
-- Configuration Files:
/etc/cron.weekly/sendfile changed:
test -f /etc/sendfile.cf || exit 0
test -x /usr/bin/sendfile || exit 0
spooldir=$(sendfile -qW=spool)
cd $spooldir || exit 0
export LANG=C
maxage=$(grep '^deljunk' /etc/sendfile.cf)
test -n "$maxage" || exit 0
maxage=${maxage##*=}
maxage=${maxage//}
maxage=${maxage/ /}
pivot=$spooldir/pivot
touch -d now-${maxage}days $pivot
touch -d now-1day $pivot.yesterday
tmp=$(mktemp)
trap "rm -f $tmp $pivot $pivot.yesterday" INT EXIT
for i in *
do
if [ -z "$(getent passwd "$i")" ]
then
continue
fi
echo -n > $tmp
if [ -d "$i" ]
then
(
cd "$i"
for f in $(find -maxdepth 1 -name '*.h')
do
b=${f#./}
b=${b%.h}
FILE=
SIZE=
while read line
do
case $line in
FILE*) FILE=${line#FILE }
;;
SIZE*) SIZE=${line#SIZE }
SIZE=${SIZE#* }
;;
esac
done < $f
size=$(stat $b.d|grep Size)
size=${size#*Size: }
size=${size%% *}
if [ $SIZE -gt $size ]
then
if [ $b.d -ot $pivot ]
then
logger -i -p daemon.info -t sendfile "sf_cleanup: Expired
partial file $b for user $i"
rm -f ${b}.{dh}
else
if [ $b.d -ot $pivot.yesterday ]
then
echo "Partial file $b will expire after $maxage days"
>> $tmp
fi
fi
fi
done
)
if [ -s $tmp ]
then
(
echo "Subject: Weekly SAFT Report"
echo "From: SAFT Server "
echo
echo "The following incompletely received files have been found
in the SAFT"
echo "spool directory $spooldir:"
echo
cat $tmp
) | /usr/sbin/sendmail $i
fi
fi
done
/etc/logrotate.d/sendfile changed:
/var/spool/sendfile/*/log {
weekly
compress
rotate 7
missingok
nocreate
sharedscripts
}
/etc/profile.d/sendfile [Errno 2] No such file or directory:
'/etc/profile.d/sendfile'
-- no debconf information
Bug#820625: [wrap-and-sort] removes all comments from debian/control
On Sun, 10 Apr 2016 21:02:05 +0200 Christoph Berg wrote: > Package: devscripts > Version: 2.16.2 > Severity: normal > User: devscri...@packages.debian.org > Usertag: wrap-and-sort > > Hi, > > I've just had all comments removed from corosync's debian/control: > > [...] > > Christoph > > Already mentioned to Christoph via IRC, but posting here in case others come across the bug. As of devscripts/2.22.2 (currently in unstable), we now have a temporary option called "--experimental-rts-parser" that should solve this problem. Please try it out and report your successes/problems back to this bug. The goal is to remove the option again and have it be the new default behaviour once it has been properly tested. Thanks, ~Niels
Bug#1012600:
I'm no expert, but since these packages are in 'contrib' I suspect they don't have the ability to block package upgrades in 'main'. On Sun, Jun 19, 2022 at 5:51 AM Chris Putnam wrote: > > Apologies if this question is well-answered, but why isn't this package > holding back the kernel to 5.17? In my mind an "apt upgrade" should not have > pulled 5.18, especially when the net result may well be an unbootable system. > Surely there's some way to mark this package as broken in tandem with 5.18? > > I'm also quite surprised this wasn't caught in sid before it was pulled into > testing. Is there any form of testing for this package going on in sid?
Bug#1012600:
Apologies if this question is well-answered, but why isn't this package holding back the kernel to 5.17? In my mind an "apt upgrade" should not have pulled 5.18, especially when the net result may well be an unbootable system. Surely there's some way to mark this package as broken in tandem with 5.18? I'm also quite surprised this wasn't caught in sid before it was pulled into testing. Is there any form of testing for this package going on in sid?
Bug#1011343: WISHLIST: Offical ALL-IN-ONE images?
Hi, i tested merging of /firmware directories with barely sufficently complete debian-11.0.0-amd64-DLBD-[12].iso.tmp from aborted jigdo-lite runs. All files which are reported as being only in CUSTOM(all-in-one) by https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011343#115 are listed by xorriso as present in the emerging ISO, of which i suppressed the actual production out of storage space reasons. So if the next diff between self-made CUSTOM(all-in-one) and merged.iso shows again missing files in /firmware, i have to ask for full listings of the /firmware trees in DLBD-1, DLBD-2, CUSTOM(all-in-one), and merged.iso . --- About my shortcuts with download and ISO non-production: I waited with aborting jigdo-lite just long enough until the first downloaded packages caused the inflation of the .template file to .iso.tmp. The directory tree and the management files are then already present, whereas the packages' content is mostly waiting for being filled in. Further i modified the xorriso run to end by -find /firmware -- -rollback_end so that no ISO emerges but only the content of the planned /firmware directory is shown before the program ends. (I would go further. But the production of CUSTOM(all-in-one) via debian-cd is out of my reach, given the section "ABOUT MIRROR" in message #115. So the effort to complete the download and to produce a merged.iso would bring no benefit for now.) Have a nice day :) Thomas
Bug#1011726: switcheroo-control: FTBFS: AssertionError: 0 != 1
severity 1011726 important thanks On Thu, 26 May 2022 08:13:24 +0200 Lucas Nussbaum wrote: > > Hi, > > During a rebuild of all packages in sid, your package failed to build > on amd64. Hello, I cannot reproduce this on my laptop, not sure what happened I'll reduce the severity to important so the package is not removed from unstable for now Kind regards, Laurent Bigonville
Bug#1007022: podman: starting rootless container fails with: can't get final child's PID from pipe: EOF
On Fri, Mar 11, 2022 at 2:51 AM Gabriel Filion wrote: > > Package: podman > Version: 3.4.4+ds1-1 > Severity: normal > > Hello, > > I used to be able to run rootless container on debian sid maybe 3 months ago > (I'm sorry, I don't have much more precise information about versions when > things used to work), but now that I try and start containers again I am > consistently hitting errors of this form: > > $ podman run -d --name="draw" -p 8080:8080 -p 8443:8443 fjudith/draw.io > Error: OCI runtime error: unable to start container > "0f2eb8afb9ce6eebbede769dc288e228ea6cbae0e76936672e6673228ac6862c": runc > create failed: unable to start container process: can't get final child's PID > from pipe: EOF > Can someone checks if you still fail to run rootless container with runc and podman 4.1? I think it's because https://github.com/containers/podman/issues/13731, which is fixed in podman 4.1. And it's caused by systemd 250 which changes OOMScoreAdjust in user@.service -- Shengjing Zhu
Bug#1013219: texlive-lang-japanese: should downgrade fonts-ipa* to Recommends/Suggests
Package: texlive-lang-japanese Version: 2020.20210202-2 Severity: normal X-Debbugs-Cc: yy.y.ja...@gmail.com Dear Maintainer, This package Depends on fonts-ipafont-* and fonts-ipaexfont-* packages, which are big and 42.7 MB in total. Since TexLive 2020 HaranoAji is the default font bundled in this package and it is preferred by kanji-config-updmap, I suppose those fonts can now be safely demoted to Recommends or even Suggests. Thanks in advance, -- YOSHINO Yoshihito -- Package-specific info: IMPORTANT INFORMATION: We will only consider bug reports concerning the packaging of TeX Live as relevant. If you have problems with combination of packages in a LaTeX document, please consult your local TeX User Group, the comp.text.tex user group, the author of the original .sty file, or any other help resource. In particular, bugs that are related to up-upstream, i.e., neither Debian nor TeX Live (upstream), but the original package authors, will be closed immediately. *** The Debian TeX Team is *not* a LaTeX Help Desk *** If you report an error when running one of the TeX-related binaries (latex, pdftex, metafont,...), or if the bug is related to bad or wrong output, please include a MINIMAL example input file that produces the error in your report. Please run your example with (pdf)latex -recorder ... (or any other program that supports -recorder) and send us the generated file with the extension .fls, it lists all the files loaded during the run and can easily explain problems induced by outdated files in your home directory. Don't forget to also include minimal examples of other files that are needed, e.g. bibtex databases. Often it also helps to include the logfile. Please, never send included pictures! If your example file isn't short or produces more than one page of output (except when multiple pages are needed to show the problem), you can probably minimize it further. Instructions on how to do that can be found at http://www.minimalbeispiel.de/mini-en.html (english) or http://www.minimalbeispiel.de/mini.html (german) ## minimal input file ## other files ## List of ls-R files -rw-r--r-- 1 root root 1881 Dec 15 2021 /var/lib/texmf/ls-R lrwxrwxrwx 1 root root 29 Feb 13 2021 /usr/share/texmf/ls-R -> /var/lib/texmf/ls-R-TEXMFMAIN lrwxrwxrwx 1 root root 31 Feb 18 2021 /usr/share/texlive/texmf-dist/ls-R -> /var/lib/texmf/ls-R-TEXLIVEDIST lrwxrwxrwx 1 root root 31 Feb 18 2021 /usr/share/texlive/texmf-dist/ls-R -> /var/lib/texmf/ls-R-TEXLIVEDIST ## Config files -rw-r--r-- 1 root root 475 Dec 15 2021 /etc/texmf/web2c/texmf.cnf lrwxrwxrwx 1 root root 33 Feb 18 2021 /usr/share/texmf/web2c/fmtutil.cnf -> /var/lib/texmf/fmtutil.cnf-DEBIAN lrwxrwxrwx 1 root root 32 Feb 18 2021 /usr/share/texmf/web2c/updmap.cfg -> /var/lib/texmf/updmap.cfg-DEBIAN -rw-r--r-- 1 root root 2763 Dec 15 2021 /var/lib/texmf/tex/generic/config/language.dat ## Files in /etc/texmf/web2c/ total 8 -rw-r--r-- 1 root root 283 Feb 28 2019 mktex.cnf -rw-r--r-- 1 root root 475 Dec 15 2021 texmf.cnf ## md5sums of texmf.d ca40c66f144b4bafc3e59a2dd32ecb9c /etc/texmf/texmf.d/00debian.cnf -- System Information: Debian Release: 11.3 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable'), (100, 'bullseye-fasttrack') Architecture: amd64 (x86_64) Kernel: Linux 5.10.0-15-amd64 (SMP w/8 CPU threads) Locale: LANG=ja_JP.UTF-8, LC_CTYPE=ja_JP.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: sysvinit (via /sbin/init) LSM: AppArmor: enabled Versions of packages texlive-lang-japanese depends on: ii fonts-ipaexfont-gothic 00401-3 ii fonts-ipaexfont-mincho 00401-3 ii fonts-ipafont-gothic00303-21 ii fonts-ipafont-mincho00303-21 ii ruby1:2.7+2 ii tex-common 6.16 ii texlive-base2020.20210202-3 ii texlive-binaries2020.20200327.54578-7 ii texlive-lang-cjk2020.20210202-2 texlive-lang-japanese recommends no packages. texlive-lang-japanese suggests no packages. Versions of packages tex-common depends on: ii dpkg 1.20.10 ii ucf 3.0043 Versions of packages tex-common suggests: ii debhelper 13.3.4 Versions of packages texlive-lang-japanese is related to: ii tex-common6.16 ii texlive-binaries 2020.20200327.54578-7 -- no debconf information
Bug#1013189: [Pkg-javascript-devel] Bug#1013189: node-webpack: ftbfs Error: [BABEL]: Cannot find module '@babel/helper-define-polyfill-provider'
On 18/06/2022 20:21, Pirate Praveen wrote: Package: src:node-webpack Version: 5.65.0+dfsg+~cs9.20.9-13 severity: serious failed to build on buildd https://buildd.debian.org/status/fetch.php?pkg=node-webpack=all=5.65.0%2Bdfsg%2B%7Ecs9.20.9-13=1654591817=0 likely a missing build depends This build is old, bug is fixed since 2022-06-10 (in node-babel-polyfills dependencies)
Bug#1013205: [Pkg-samba-maint] Bug#1013205: samba-common: samba no longer installable on sparc64 due to impossible version conflict
19.06.2022 03:03, Rich Ercolani wrote: Package: samba-common Version: 2:4.13.5+dfsg-2 Severity: normal X-Debbugs-Cc: rincebr...@gmail.com Dear Maintainer, Pretty simple report - since samba-common is only offered at 2:4.16.2+dfsg-1 in sid currently, and all the binary samba packages for sparc64 are at 2:4.13.14+dfsg-1+b4, it's impossible to install right now without either reaching into the archive snapshots or building yourself. It would be nice if this wasn't breaking "apt upgrade". Samba upstream does not build on sparc. It would be nice it it did, that'd fix this issue. Meanwhile, in order not to break samba on all other architectures, I decided to build current version of samba-common on all other architectures, even if it breaks old version of samba on sparc. Thanks, /mjt
Bug#1013215: node-extract-text-webpack-plugin: error when validating schema
Package: node-extract-text-webpack-plugin
Version: 3.0.2-6
Severity: normal
This usage triggers a call to
(0, _schemaUtils.validate)(_path.default.resolve(__dirname,
'../schema/loader.json'), options, 'Extract Text Plugin (Loader)');
But validate (from ajv) expects an object, not a path string.
Usage:
ExtractTextPlugin.extract({
use: {
loader: 'css-loader',
options: {
url: false
}
}
})
-- System Information:
Debian Release: bookworm/sid
APT prefers unstable
APT policy: (500, 'unstable'), (101, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 5.18.0-1-amd64 (SMP w/4 CPU threads; PREEMPT)
Kernel taint flags: TAINT_WARN
Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages node-extract-text-webpack-plugin depends on:
ii node-loader-utils 2.0.2-1
ii node-neo-async2.6.2+~cs3.0.0-2
ii node-schema-utils 3.1.1~ds-1
ii node-webpack-sources 3.2.1-5
ii webpack 5.65.0+dfsg+~cs9.20.9-12
node-extract-text-webpack-plugin recommends no packages.
node-extract-text-webpack-plugin suggests no packages.
-- no debconf information
Bug#1013216: node-extract-text-webpack-plugin: abandonned upstream, please package mini-css-extract-plugin instead
Package: node-extract-text-webpack-plugin Version: 3.0.2-6 Severity: important mini-css-extract-plugin has replaced this module. It looks packageable (maybe some devDeps are missing, but only for running some tests). -- System Information: Debian Release: bookworm/sid APT prefers unstable APT policy: (500, 'unstable'), (101, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 5.18.0-1-amd64 (SMP w/4 CPU threads; PREEMPT) Kernel taint flags: TAINT_WARN Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages node-extract-text-webpack-plugin depends on: ii node-loader-utils 2.0.2-1 ii node-neo-async2.6.2+~cs3.0.0-2 ii node-schema-utils 3.1.1~ds-1 ii node-webpack-sources 3.2.1-5 ii webpack 5.65.0+dfsg+~cs9.20.9-12 node-extract-text-webpack-plugin recommends no packages. node-extract-text-webpack-plugin suggests no packages. -- no debconf information
