Bug#989229: grub-install: warning: Cannot read EFI Boot* variables.
id_sensor_hub i915 hid_generic mmc_block crct10dif_pclmul crct10dif_common crc32_pclmul crc32c_intel ghash_clmulni_intel i2c_algo_bit drm_kms_helper cec drm ahci xhci_pci sdhci_pci xhci_hcd libahci [Sun Jul 11 20:36:36 2021] aesni_intel cqhci sdhci usbcore libaes crypto_simd libata cryptd glue_helper mmc_core scsi_mod i2c_i801 i2c_smbus lpc_ich intel_lpss_pci intel_lpss idma64 usb_common i2c_hid hid fan button battery wmi video [Sun Jul 11 20:36:36 2021] CPU: 0 PID: 66728 Comm: kworker/u8:10 Not tainted 5.10.0-6-amd64 #1 Debian 5.10.28-1 [Sun Jul 11 20:36:36 2021] Hardware name: Acer Spin SP111-31N/Ironhide_AP, BIOS V1.02 01/04/2017 [Sun Jul 11 20:36:36 2021] Workqueue: efi_rts_wq efi_call_rts [Sun Jul 11 20:36:36 2021] RIP: 0010:efi_recover_from_page_fault+0x2a/0xc0 [Sun Jul 11 20:36:36 2021] Code: 0f 1f 44 00 00 8b 15 65 77 f7 01 85 d2 74 09 48 81 ff ff 0f 00 00 77 01 c3 53 48 89 fe 48 c7 c7 60 ca 8c b0 50 e8 e9 b0 7f 00 <0f> 0b 83 3d 3d 77 f7 01 0a 0f 84 13 ac 7f 00 48 8b 3d 18 bb e5 01 [Sun Jul 11 20:36:36 2021] RSP: 0018:abf1c1703b50 EFLAGS: 00010082 [Sun Jul 11 20:36:36 2021] RAX: RBX: 93b4eb6b8000 RCX: 93b53bc18a08 [Sun Jul 11 20:36:36 2021] RDX: ffd8 RSI: 0027 RDI: 93b53bc18a00 [Sun Jul 11 20:36:36 2021] RBP: abf1c1703bf8 R08: R09: abf1c1703970 [Sun Jul 11 20:36:36 2021] R10: abf1c1703968 R11: b0ecb368 R12: 66cd61d0 [Sun Jul 11 20:36:36 2021] R13: R14: 000b R15: 0001 [Sun Jul 11 20:36:36 2021] FS: () GS:93b53bc0() knlGS: [Sun Jul 11 20:36:36 2021] CS: 0010 DS: ES: CR0: 80050033 [Sun Jul 11 20:36:36 2021] CR2: 66cd61d0 CR3: 0001001a4000 CR4: 003506f0 [Sun Jul 11 20:36:36 2021] Call Trace: [Sun Jul 11 20:36:36 2021] no_context+0x16a/0x3a0 [Sun Jul 11 20:36:36 2021] exc_page_fault+0x7b/0x160 [Sun Jul 11 20:36:36 2021] asm_exc_page_fault+0x1e/0x30 [Sun Jul 11 20:36:36 2021] RIP: 0010:0xfffefb04fd44 [Sun Jul 11 20:36:36 2021] Code: d1 b9 04 00 00 00 e9 b7 ff ff ff cc cc cc 48 8b 05 f9 4a 00 00 48 ff 60 30 cc 48 83 ec 28 48 8b 05 e9 4a 00 00 4c 8d 44 24 40 50 40 48 8b 4c 24 40 33 d2 48 85 c0 48 0f 48 ca 48 8b c1 48 83 [Sun Jul 11 20:36:36 2021] RSP: 0018:abf1c1703ca0 EFLAGS: 00010086 [Sun Jul 11 20:36:36 2021] RAX: 66cd6190 RBX: 0002 RCX: 0004 [Sun Jul 11 20:36:36 2021] RDX: 0002 RSI: RDI: 0002 [Sun Jul 11 20:36:36 2021] RBP: abf1c1703d70 R08: abf1c1703ce0 R09: abf1c1703dd0 [Sun Jul 11 20:36:36 2021] R10: R11: 0018 R12: [Sun Jul 11 20:36:36 2021] R13: 00083fb0 R14: abf1c1703dd0 R15: abf1c1703dd8 [Sun Jul 11 20:36:36 2021] ? __clear_extent_bit+0x232/0x4a0 [btrfs] [Sun Jul 11 20:36:36 2021] ? endio_readpage_release_extent+0x52/0xb0 [btrfs] [Sun Jul 11 20:36:36 2021] ? psi_group_change+0x41/0x210 [Sun Jul 11 20:36:36 2021] ? __efi_call+0x28/0x30 [Sun Jul 11 20:36:36 2021] ? __schedule+0x28a/0x870 [Sun Jul 11 20:36:36 2021] ? efi_call_rts+0x424/0x760 [Sun Jul 11 20:36:36 2021] ? __schedule+0x28a/0x870 [Sun Jul 11 20:36:36 2021] ? process_one_work+0x1b6/0x350 [Sun Jul 11 20:36:36 2021] ? worker_thread+0x53/0x3e0 [Sun Jul 11 20:36:36 2021] ? process_one_work+0x350/0x350 [Sun Jul 11 20:36:36 2021] ? kthread+0x11b/0x140 [Sun Jul 11 20:36:36 2021] ? __kthread_bind_mask+0x60/0x60 [Sun Jul 11 20:36:36 2021] ? ret_from_fork+0x22/0x30 [Sun Jul 11 20:36:36 2021] ---[ end trace b7e2b9ad057169a2 ]--- [Sun Jul 11 20:36:36 2021] efi: Froze efi_rts_wq and disabled EFI Runtime Services [Sun Jul 11 20:36:36 2021] efi: EFI Runtime Services are disabled! [Sun Jul 11 20:36:42 2021] efi: EFI Runtime Services are disabled! The output from the other commands is fairly long, so I've left copies at the links below, but I assume they couldn't possibly run correctly as the kernel has disabled efi: # strace -f -s 1024 grub-install --target=x86_64-efi https://www.maher.org.uk/~joseph/20210711-strace-grub-install.log # strace -f -s 1024 efibootmgr https://www.maher.org.uk/~joseph/20210711-strace-efibootmgr.log Thanks! Joseph
Bug#990872: puppetdb.jar crashes out of the box with clojure classpath error
On Sat, 10 Jul 2021 14:08:00 -0400 =?UTF-8?Q?Louis-Philippe_V=c3=a9ronneau?= wrote: > On Fri, 09 Jul 2021 23:14:22 -0700 "Gabriel G. Rosa" > wrote: > > Package: puppetdb > > Version: 6.2.0-5 > > Severity: grave > > Justification: renders package unusable > > > > Dear Maintainer, > > > > When installing puppetdb and configuring it to listen on http port, the > > puppetdb.jar crashes with the following lines in syslog: > > > > Jul 9 23:01:46 puppet java[25194]: Syntax error (FileNotFoundException) > > compiling at (clojure/core/async/impl/ioc_macros.clj:1:1). > > Jul 9 23:01:46 puppet java[25194]: Could not locate > > clojure/tools/analyzer__init.class, clojure/tools/analyzer.clj or > > clojure/tools/analyzer.cljc on classpath. > > Jul 9 23:01:46 puppet java[25194]: Full report at: > > Jul 9 23:01:46 puppet java[25194]: /tmp/clojure-1064777479875377538.edn > > I've seen that error elsewhere while running clojure testsuites for > packages depending on libcore-async-clojure [1] and never got to debug it... > > I've just re-built libcore-async-clojure and libtools-analyzer-clojure > locally and their full testsuites passes though. > > I've also checked, and libtools-analyzer-clojure does ship the right jar > files: > > usr/ > └── share > ├── doc > │ └── libtools-analyzer-clojure > │ ├── changelog.Debian.gz > │ ├── changelog.gz > │ ├── CONTRIBUTING.md > │ ├── copyright > │ └── README.md.gz > ├── java > │ ├── tools.analyzer-1.0.0.jar > │ └── tools.analyzer.jar -> tools.analyzer-1.0.0.jar > └── maven-repo > └── org > └── clojure > └── tools.analyzer > ├── 1.0.0 > │ ├── tools.analyzer-1.0.0.jar > │ └── tools.analyzer-1.0.0.pom > └── debian > ├── tools.analyzer-debian.jar -> > ../1.0.0/tools.analyzer-1.0.0.jar > └── tools.analyzer-debian.pom > > Those jars do contain the right clojure files too... > > clojure/ > └── tools > ├── analyzer > │ ├── ast > │ │ └── query.clj > │ ├── ast.clj > │ ├── env.clj > │ ├── passes So if I include a few extra jars in the command line, it gets me a little further: grosa@puppet:~$ sudo /usr/bin/java -Xmx192m -Djava.security.egd=/dev/urandom -XX:OnOutOfMemoryError="kill -9 %p" -cp /usr/share/puppetdb/puppetdb.jar:/usr/share/java/tools.analyzer.jar:/usr/share/java/tools.analyzer.jvm.jar clojure.main -m puppetlabs.puppetdb.core services --config /etc/puppetdb/conf.d --bootstrap-config /etc/puppetdb/bootstrap.cfg --restart-file /run/puppetdb/restart Syntax error (ClassNotFoundException) compiling . at (puppetlabs/http/client/async.clj:60:5). org.apache.http.nio.protocol.HttpAsyncResponseConsumer Full report at: /tmp/clojure-11985391683440035019.edn clojure-11985391683440035019.edn Description: Binary data But still not at a working puppetdb http listener… Sorry I am fumbling in the dark a bit — I am not at all familiar with java and clojure. Should I be filing a bug report against a different package? Thanks, -G
Bug#801951: debian/copyright should mention BSD3 license, not PSF
Am 11.07.21 um 01:28 schrieb Colin Watson: Thanks for committing a fix for this to git. Do you need sponsorship help to upload this (if so, I'd be happy to do it), or is an upload already in progress? The change needs sponsorship. It is in the Python Team's RFS queue, so please go ahead.
Bug#988905:
I see there is a fix in the git repo now. Are you planning an upload any time soon, or only after the buster release?
Bug#990966: grub-efi-arm64: breaks upgrades when the efivarfs is mounted read-only
Control: severity -1 important Hey Andres, On Sun, Jul 11, 2021 at 04:19:19PM -0400, Andres Salomon wrote: >Package: grub-efi-arm64 >Version: 2.04-19 >Severity: serious > >I experienced the follow on multiple ARM64 systems (both a Rock64 >board and a Raspberry Pi 4b board) during an unattended-upgrades run: > >Unattended upgrade result: All upgrades installed > >Packages that attempted to upgrade: > shim-helpers-arm64-signed shim-signed shim-signed-common > shim-unsigned ... >Here's the relevant field in /proc/mounts: >efivarfs /sys/firmware/efi/efivars efivarfs ro,nosuid,nodev,noexec,relatime 0 0 > >I expect that the reason /sys/firmware/efi/efivars is mounted read-only is >due to bug reports such as the following: >https://github.com/systemd/systemd/issues/2402 But that was never agreed. I'm genuinely curious why you have efivarfs mounted read-only, and I don't think it's a supported/supportable option here. >It would be preferable for grub to either >a) continue the package postinstall despite efivars being read-only, or >b) remount efivars read-write, update efivars, and then remount ro. > >grub-install is being called from shim-helpers-arm64-signed's >postinst. You could argue that shim-helpers-arm64-signed could >remount efivars read-write, but since I can actually trigger the >same error in grub-efi-arm64's postinst, it seems like this should be >fixed in grub: The "issue" is definitely coming from grub-efi-$ARCH, but it's behaving as designed here. Continuing despite failing to update the EFI boot vars here will potentially leave you with an unbootable system. -- Steve McIntyre, Cambridge, UK.st...@einval.com "I've only once written 'SQL is my bitch' in a comment. But that code is in use on a military site..." -- Simon Booth
Processed: Re: Bug#990966: grub-efi-arm64: breaks upgrades when the efivarfs is mounted read-only
Processing control commands: > severity -1 important Bug #990966 [grub-efi-arm64] grub-efi-arm64: breaks upgrades when the efivarfs is mounted read-only Severity set to 'important' from 'serious' -- 990966: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=990966 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#990966: grub-efi-arm64: breaks upgrades when the efivarfs is mounted read-only
Package: grub-efi-arm64 Version: 2.04-19 Severity: serious I experienced the follow on multiple ARM64 systems (both a Rock64 board and a Raspberry Pi 4b board) during an unattended-upgrades run: Unattended upgrade result: All upgrades installed Packages that attempted to upgrade: shim-helpers-arm64-signed shim-signed shim-signed-common shim-unsigned Packages with upgradable origin but kept back: Debian testing: shim-signed shim-helpers-arm64-signed shim-signed-common Package installation log: Log started: 2021-07-10 06:16:45 Preparing to unpack .../shim-unsigned_15.4-6_arm64.deb ... Unpacking shim-unsigned (15.4-6) over (15.4-5) ... Setting up shim-unsigned (15.4-6) ... Log ended: 2021-07-10 06:16:50 Log started: 2021-07-10 06:16:51 Preconfiguring packages ... Preconfiguring packages ... Preparing to unpack .../shim-signed-common_1.37+15.4-6_all.deb ... Unpacking shim-signed-common (1.37+15.4-6) over (1.36+15.4-5) ... Preparing to unpack .../shim-signed_1.37+15.4-6_arm64.deb ... Unpacking shim-signed:arm64 (1.37+15.4-6) over (1.36+15.4-5) ... Setting up shim-signed-common (1.37+15.4-6) ... No DKMS packages installed: not changing Secure Boot validation state. Setting up shim-signed:arm64 (1.37+15.4-6) ... Installing for arm64-efi platform. grub-install: warning: Cannot set EFI variable Boot. grub-install: warning: efivarfs_set_variable: failed to create /sys/firmware/efi/efivars/Boot-8be4df61-93ca-11d2-aa0d-00e098032b8c for writing: Read-only file system. grub-install: warning: _efi_set_variable_mode: ops->set_variable() failed: Read-only file system. grub-install: error: failed to register the EFI boot entry: Read-only file system. dpkg: error processing package shim-signed:arm64 (--configure): installed shim-signed:arm64 package post-installation script subprocess returned error exit status 1 Errors were encountered while processing: shim-signed:arm64 E:Sub-process /usr/bin/dpkg returned an error code (1) Log ended: 2021-07-10 06:17:29 Unattended-upgrades log: Checking if system is running on battery is skipped. Please install powermgmt-base package to check power status and skip installing updates when the system is running on battery. Starting unattended upgrades script Allowed origins are: origin=Debian,codename=bullseye,label=Debian, origin=Debian,codename=bullseye,label=Debian-Security, origin=Debian,codename=bullseye-security,label=Debian-Security Initial blacklist: Initial whitelist (not strict): Packages that will be upgraded: shim-helpers-arm64-signed shim-signed shim-signed-common shim-unsigned Writing dpkg log to /var/log/unattended-upgrades/unattended-upgrades-dpkg.log Installing the upgrades failed! error message: installArchives() failed dpkg returned a error! See /var/log/unattended-upgrades/unattended-upgrades-dpkg.log for details Package shim-helpers-arm64-signed is kept back because a related package is kept back or due to local apt_preferences(5). Package shim-signed is kept back because a related package is kept back or due to local apt_preferences(5). Package shim-signed-common is kept back because a related package is kept back or due to local apt_preferences(5). Here's the relevant field in /proc/mounts: efivarfs /sys/firmware/efi/efivars efivarfs ro,nosuid,nodev,noexec,relatime 0 0 I expect that the reason /sys/firmware/efi/efivars is mounted read-only is due to bug reports such as the following: https://github.com/systemd/systemd/issues/2402 It would be preferable for grub to either a) continue the package postinstall despite efivars being read-only, or b) remount efivars read-write, update efivars, and then remount ro. grub-install is being called from shim-helpers-arm64-signed's postinst. You could argue that shim-helpers-arm64-signed could remount efivars read-write, but since I can actually trigger the same error in grub-efi-arm64's postinst, it seems like this should be fixed in grub: dilinger@wifi2:~$ sudo dpkg-reconfigure grub-efi-arm64 [sudo] password for dilinger: Installing for arm64-efi platform. grub-install: warning: Cannot set EFI variable Boot. grub-install: warning: efivarfs_set_variable: failed to create /sys/firmware/efi/efivars/Boot-8be4df61-93ca-11d2-aa0d-00e098032b8c for writing: Read-only file system. grub-install: warning: _efi_set_variable_mode: ops->set_variable() failed: Read-only file system. grub-install: error: failed to register the EFI boot entry: Read-only file system. Failed: grub-install --target=arm64-efi WARNING: Bootloader is not properly installed, system may not be bootable Generating grub configuration file ... Found linux image: /boot/vmlinuz-5.10.0-7-arm64 Found initrd image: /boot/initrd.img-5.10.0-7-arm64 done
Bug#990911: marked as done (liferea: Segfaults when selecting a news bin)
Your message dated Sun, 11 Jul 2021 20:17:00 +
with message-id
and subject line Bug#990911: fixed in liferea 1.13.5-3
has caused the Debian Bug report #990911,
regarding liferea: Segfaults when selecting a news bin
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
990911: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=990911
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: liferea
Version: 1.13.5-1
Severity: important
Tags: upstream, fixed-upstream, patch
liferea 1.13.5 will immediately segfault when selecting a news bin in
the left pane. (And if a news bin was the last selected item before
upgrading, it will then automatically crash on startup. I'd argue this
would justify a bump to serious; you be the judge.)
The bug is in feed_add_xml_attributes(), where node->subscription gets
dereferenced at the end, even if it was found to be NULL beforehand.
This was fixed upstream in 49cf235, by moving the last three lines
inside the if(), where they belong. That patch does not apply cleanly
to 1.13.5 (due to 9db267f), so I'm attaching a revised version.
-- System Information:
Debian Release: 11.0
APT prefers testing
APT policy: (990, 'testing'), (500, 'unstable-debug'), (500,
'testing-debug'), (100, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 5.10.0-5-amd64 (SMP w/4 CPU threads)
Kernel taint flags: TAINT_WARN, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
>From dd9ede21cd822989e9fafecadefb4fc410a7c0e7 Mon Sep 17 00:00:00 2001
From: Lars Windolf
Date: Fri, 2 Apr 2021 01:22:24 +0200
Subject: [PATCH] Fix crash on selecting news bins
---
src/feed.c | 11 ++-
1 file changed, 6 insertions(+), 5 deletions(-)
diff --git a/src/feed.c b/src/feed.c
index 585ed82a..97848f9f 100644
--- a/src/feed.c
+++ b/src/feed.c
@@ -165,9 +165,14 @@ feed_add_xml_attributes (nodePtr node, xmlNodePtr feedNode)
xmlNewTextChild (feedNode, NULL, "feedId", node_get_id (node));
xmlNewTextChild (feedNode, NULL, "feedTitle", node_get_title (node));
- if (node->subscription)
+ if (node->subscription) {
subscription_to_xml (node->subscription, feedNode);
+ tmp = g_strdup_printf("%d", node->subscription->error);
+ xmlNewTextChild(feedNode, NULL, "error", tmp);
+ g_free(tmp);
+ }
+
tmp = g_strdup_printf("%d", node->available?1:0);
xmlNewTextChild(feedNode, NULL, "feedStatus", tmp);
g_free(tmp);
@@ -178,10 +183,6 @@ feed_add_xml_attributes (nodePtr node, xmlNodePtr feedNode)
if(feed->parseErrors && (strlen(feed->parseErrors->str) > 0))
xmlNewTextChild(feedNode, NULL, "parseError",
feed->parseErrors->str);
-
- tmp = g_strdup_printf("%d", node->subscription->error);
- xmlNewTextChild(feedNode, NULL, "error", tmp);
- g_free(tmp);
}
xmlDocPtr
--
2.30.2
--- End Message ---
--- Begin Message ---
Source: liferea
Source-Version: 1.13.5-3
Done: Paul Gevers
We believe that the bug you reported is fixed in the latest version of
liferea, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 990...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Paul Gevers (supplier of updated liferea package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Sun, 11 Jul 2021 21:37:39 +0200
Source: liferea
Architecture: source
Version: 1.13.5-3
Distribution: unstable
Urgency: medium
Maintainer: David Michael Smith
Changed-By: Paul Gevers
Closes: 990911
Changes:
liferea (1.13.5-3) unstable; urgency=medium
.
[ Frédéric Brière ]
* Add 0001-Fix-crash-on-selecting-news-bins.patch (Closes: #990911)
Checksums-Sha1:
142fc0026be345fb6b632869e980ffadfa189a72 2075 liferea_1.13.5-3.dsc
8f7e71b691c9b94c8b01c6b9202efe9180f90c29 28192 liferea_1.13.5-3.debian.tar.xz
Checksums-Sha256:
d4e5de34641324ebd50c5828e8a0ab80c6875177a3dd87b6b303d46e9794fa3d 2075
liferea_1.13.5-3.dsc
Bug#990906: Xarchiver Debian bug 990906
Hi Ingo, I have received a bug report from David Harte (Debian bug #990906) and I can reproduce the behavior. https://bugs.debian.org/990906 It makes no difference if the linked directory is on a ntfs or ext4 file system though. If you follow all steps and open the archive with xarchiver and double click on the symlink, then xarchiver will move the files from the linked directory to the tmp directory. They are not lost yet but this is a surprising behavior. After a reboot they would be permanently lost though. If I right click on the symlink and try to extract it then the extraction works as intended. However the "Open with" feature (or a double click) produces an error message and moves the files inside the symlinked directory to the tmp directory. Could you comment on this issue please? Is there a quick fix which I could apply to address this problem because we are in a full freeze right now. Regards, Markus signature.asc Description: This is a digitally signed message part
Processed: Re: autopkgtest fails with rails 6 in experimental
Processing control commands: > severity -1 important Bug #966549 [ruby-markerb] ruby-markerb: autopkgtest fails with rails 6 in experimental Severity set to 'important' from 'serious' -- 966549: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966549 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#966549: autopkgtest fails with rails 6 in experimental
Control: severity -1 important On Thu, 30 Jul 2020 19:18:09 +0530 Kartik Kulkarni wrote: > Hi, > > This package's autopkgtest and rebuilds failed with rails 6 currently in > experimental. rails 6 will be uploaded to unstable in a weeks time, so > please make sure this package is ready for rails 6. The severity of > this bug will be raised to serious after rails 6 is uploaded to > unstable. Its only reverse dependency diaspora now embeds rails 5 and the test failures during build is ignored and autopkgtest is disabled in 1.1.0-4. I will keep the bug open in case someone is interested to fix the rails 6 support. Alternatively, if diaspora switches to another gem like premailer-rails we could remove this package.
Processed: Re: Bug#990911: liferea: Segfaults when selecting a news bin
Processing control commands: > tags -1 confirmed Bug #990911 [liferea] liferea: Segfaults when selecting a news bin Added tag(s) confirmed. > severity -1 serious Bug #990911 [liferea] liferea: Segfaults when selecting a news bin Severity set to 'serious' from 'important' -- 990911: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=990911 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#988909: Please make sure lintian-brush will migrate to testing (Was: routine-update is marked for autoremoval from testing)
Hi Andreas, Thanks for the pointer - I hadn't realized that this bug was still affecting testing. How hard would it be to drop support for lintian-brush in routine-update in testing? It looks like properly fixing this bug is going to be tricky if it involves going via unstable - it would mean rolling back several packages in unstable. Dropping lintian-brush is probably the safest option to avoid impact on routine-update, as I am not sure I'll be able to get all of that done properly in time. Sorry :-/ Cheers, Jelmer On Fri, Jul 09, 2021 at 08:53:27AM +0200, Andreas Tille wrote: > Hi Jelmer, > > its only four days left to get lintian-brush migrating. You definitely > need to do some action. > > Kind regards > Andreas. > > On Fri, Jul 09, 2021 at 04:39:03AM +, Debian testing autoremoval watch > wrote: > > routine-update 0.0.6 is marked for autoremoval from testing on 2021-07-13 > > > > It (build-)depends on packages with these RC bugs: > > 988909: lintian-brush: autopkgtest failure and FTBFS > > https://bugs.debian.org/988909 > > > > > > > > This mail is generated by: > > https://salsa.debian.org/release-team/release-tools/-/blob/master/mailer/mail_autoremovals.pl > > > > Autoremoval data is generated by: > > https://salsa.debian.org/qa/udd/-/blob/master/udd/testing_autoremovals_gatherer.pl > > > > ___ > > Debian-med-packaging mailing list > > debian-med-packag...@alioth-lists.debian.net > > https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-med-packaging > > > > -- > http://fam-tille.de > signature.asc Description: PGP signature
Processed: closing 868773
Processing commands for cont...@bugs.debian.org: > close 868773 Bug #868773 [src:khal] khal FTBFS: AssertionError: assert not OSError(6, 'No such device or address') Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 868773: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=868773 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: closing 908498
Processing commands for cont...@bugs.debian.org: > close 908498 Bug #908498 [src:python-icalendar] python-icalendar FTBFS with python-dateutil 2.7.3-1 Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 908498: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=908498 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#990927: ensmallen FTBFS: test not run
Control: tag -1 patch Hi Adrian, Thank you for your testings, and having caught this: > Unable to find executable: > /<>/obj-x86_64-linux-gnu/ensmallen_tests It looks like the binary ensmallen_tests driving the test suite does not get built by the default targets. The patch in attachment solves the problem on my end, and the build from source goes through. In hope this helps… Have a nice day, :) -- Étienne Mollier Fingerprint: 8f91 b227 c7d6 f2b1 948c 8236 793c f67e 8f0d 11da Sent from /dev/tty1, please excuse my verbosity. --- a/debian/rules +++ b/debian/rules @@ -7,6 +7,9 @@ %: dh $@ +execute_after_dh_auto_build: + dh_auto_build -- ensmallen_tests + # Number of times to run test suite. # (There was a heisenbug, and this was used to help track it down.) n_test = 1 signature.asc Description: PGP signature
Bug#990371: munin-node: Unit fails on startup - Runtime directory n/a
I've sent MR to fix this issue. https://salsa.debian.org/debian/munin/-/merge_requests/5 Regards,
Processed: munin-node: Unit fails on startup - Runtime directory n/a
Processing commands for cont...@bugs.debian.org: > tags 990371 patch Bug #990371 [munin-node] munin-node: Unit fails on startup - Runtime directory n/a Added tag(s) patch. > End of message, stopping processing here. Please contact me if you need assistance. -- 990371: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=990371 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#951647: marked as done (libmstch-dev: Library configuration is misplaced)
Your message dated Sun, 11 Jul 2021 12:48:31 + with message-id and subject line Bug#951647: fixed in mstch 1.0.2-3 has caused the Debian Bug report #951647, regarding libmstch-dev: Library configuration is misplaced to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 951647: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=951647 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libmstch-dev Version: 1.0.2-2 Severity: important Tags: patch Dear Maintainer, While trying to link up a CMake project with this library, an error occured: ``` CMake Error at /usr/lib/cmake/mstch/mstch-config.cmake:1 (include): include could not find load file: /usr/lib/cmake/mstch/mstch-targets.cmake ``` This is because the *mstch-targets.cmake* is being installed into multiarch location, which is introduced by the *fix-lib-dir* patch. -- System Information: Debian Release: 10.3 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.19.0-8-amd64 (SMP w/8 CPU cores) Kernel taint flags: TAINT_WARN Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8), LANGUAGE=ru_RU:ru (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages libmstch-dev depends on: ii libboost-dev 1.67.0.1 libmstch-dev recommends no packages. libmstch-dev suggests no packages. -- no debconf information fix-lib-dir Description: fix-lib-dir --- End Message --- --- Begin Message --- Source: mstch Source-Version: 1.0.2-3 Done: Guus Sliepen We believe that the bug you reported is fixed in the latest version of mstch, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 951...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Guus Sliepen (supplier of updated mstch package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sun, 11 Jul 2021 14:18:54 +0200 Source: mstch Architecture: source Version: 1.0.2-3 Distribution: unstable Urgency: medium Maintainer: Guus Sliepen Changed-By: Guus Sliepen Closes: 897342 951647 Changes: mstch (1.0.2-3) unstable; urgency=medium . * Bump Standards-Version. * Add Rules-Requires-Root: no. * Fix installation directory for the CMake configuration file. Closes: #951647, #897342 Checksums-Sha1: 62e99b2387e1eb86c3d62f1a2adddbb76d64fe83 1729 mstch_1.0.2-3.dsc 68f0878aec473b1b5853257f85ce4e831b6c7535 2648 mstch_1.0.2-3.debian.tar.xz 6e28e8b235993f969aef40ec9da3ee487b1add73 8137 mstch_1.0.2-3_source.buildinfo Checksums-Sha256: 764e0fb53707c3bc9f943156f431e6d3c598ccfec272c7062a47748f22e60364 1729 mstch_1.0.2-3.dsc 8fb429804cf09bc59096f43b50f3f73db29abe646dc64817dd242d55498cd857 2648 mstch_1.0.2-3.debian.tar.xz 494f26d269ef6851cb00a5a7c5b579b5d47bfd1cf4df7b94a87bccab1aec8b00 8137 mstch_1.0.2-3_source.buildinfo Files: 1dc6faa3cb04b71dfb6e39ccbe5ed7c9 1729 libs optional mstch_1.0.2-3.dsc 3511365968e28f51c6f670a04775a2cf 2648 libs optional mstch_1.0.2-3.debian.tar.xz 1616b5b2aa706395ff44e5a724738694 8137 libs optional mstch_1.0.2-3_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEETRt3lsA+CDGZG91CP0kN64ce+foFAmDq4fcACgkQP0kN64ce +fov/A/+Kd2Z2qtToxhctw4AK7NExnn3uq54QUbyP2X4sxdvfcE1sqU6Uveix/Z4 Tm6iLMZIu4eT4Qs4/0YmcpACXLx55neqkj9/hBlRTwwxZSi5pDlRMLr7WEbu6KZV 95ZQvY/+Tlsj19hv9/U5Eqsb8Emd55EbLr18w8CylhJmEhTPLOgu0bAoIvieNWAN MhYby2jVKPkSCpCSArmBNivcqNd+cE4FKJihbxpmcPfy/o4/uK0djhxwEErU20BM 0mqwBgApssUWbCmpZRHPo8spXbqfYwHxPXsMGsc9HTKNcDZkGQTnhkdsJZblce5p TnOx7O4U7M9kh87NTW1CEYSYKMLNM0jKV+qoKJ8bl/RbG3/kXjXtrUsl51Wp8+jt icDo6nEoyGj/dAwqbRTz1FVELmBJWkkvXvVjU8QacFPWvHX7cl73zp9kCYGa7afG QZK0ULw8skEiQC9dc5i7MbsnDgKTUG3LOlz1kgtUzSgPuoYiFTbhJDjoSjZS3Z1r d8jWHgUOy6mKF93DwJn6JWqDKZXeBIjb6hN62DfZ+cm/I5vl9OU/Lo7zaHqENjjO EsOetLlT6W8U0cvpWfqBSyp3NwL8oJsh3sqgRhlAnep+aKAqztmf5Ydt6vvp3pFl P+COYzVCJP9X2j5eHeXwQbGVN2RCW6AaSAKNIJB4r+H0axEoaag= =bE2Z -END PGP SIGNATURE End Message ---
Processed: severity of 986397 is serious
Processing commands for cont...@bugs.debian.org:
> severity 986397 serious
Bug #986397 {Done: Russell Stuart }
[nagios4-common] nagios4-common: fails to install nagios4 package in the fresh
debian testing installation
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
986397: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=986397
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#990927: ensmallen FTBFS: test not run
Processing control commands: > tag -1 patch Bug #990927 [src:ensmallen] ensmallen FTBFS: test not run Added tag(s) patch. -- 990927: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=990927 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: severity of 986697 is serious
Processing commands for cont...@bugs.debian.org:
> severity 986697 serious
Bug #986697 {Done: Chow Loong Jin } [qreator] qreator
crashes at startup
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
986697: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=986697
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#990863: marked as done (libserialport0: libserialport tries to use termiox on bullseye, and fails to open serial ports)
Your message dated Sun, 11 Jul 2021 09:18:22 +
with message-id
and subject line Bug#990863: fixed in libserialport 0.1.1-4
has caused the Debian Bug report #990863,
regarding libserialport0: libserialport tries to use termiox on bullseye, and
fails to open serial ports
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
990863: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=990863
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libserialport0
Version: 0.1.1-3+b1
Severity: important
Tags: upstream patch
X-Debbugs-Cc: t...@seoss.co.uk
Serial port open seems to fail on bullseye. Strace output follows:
1512868 openat(AT_FDCWD, "/dev/ttyACM0", O_RDWR|O_NOCTTY|O_NONBLOCK) = 9
1512868 ioctl(9, TCGETS, {B9600 opost isig icanon echo ...}) = 0
1512868 ioctl(9, TIOCMGET, [TIOCM_DTR|TIOCM_RTS|TIOCM_CTS]) = 0
1512868 ioctl(9, TCGETX, 0x55cd7cc80df0) = -1 ENOTTY (Inappropriate ioctl for
device)
1512868 close(9)= 0
1512868 write(2, "sr: ", 4) = 4
1512868 write(2, "serial-libsp: Error opening port"..., 71) = 71
1512868 write(2, "No devices found.\n", 18) = 18
Applying upstream commit 6f9b03e597ea fixes the issue. I tested this
with:
/usr/local/bin/sigrok-cli --driver=rdtech-tc:conn=/dev/ttyACM0 --continuous
Patch here:
https://github.com/sigrokproject/libserialport/commit/6f9b03e597ea7200eb616a4e410add3dd1690cb1
I suspect that libserialport0 will fail to open all serial ports on
bullseye without this fix, so this bug may unfortunately be RC?
Cheers,
Tim.
-- System Information:
Debian Release: 11.0
APT prefers testing-security
APT policy: (500, 'testing-security'), (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 5.10.0-7-amd64 (SMP w/4 CPU threads)
Kernel taint flags: TAINT_WARN, TAINT_CRAP
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 libserialport0 depends on:
ii libc6 2.31-12
libserialport0 recommends no packages.
libserialport0 suggests no packages.
-- no debconf information
>From 6f9b03e597ea7200eb616a4e410add3dd1690cb1 Mon Sep 17 00:00:00 2001
From: Karl Palsson
Date: Fri, 11 Jun 2021 17:07:09 +
Subject: [PATCH] HACK: don't even check for termiox
termiox was removed from linux in e0efb3168d34
Some more information available in
https://www.spinics.net/lists/linux-serial/msg41926.html
Attempting to use the termiox ioctls on more modern kernels results in
"Inappropriate IOCTL" errors.
While the "right" solution might be to remove the termiox code from the
linux path, simply not checking for termiox builds a libserialport that
functions on modern linux kernels.
Signed-off-by: Karl Palsson
---
configure.ac | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/configure.ac b/configure.ac
index b1af16f..a26b851 100644
--- a/configure.ac
+++ b/configure.ac
@@ -112,7 +112,7 @@ AC_SYS_LARGEFILE
AC_TYPE_SIZE_T
# Check for specific termios structures.
-AC_CHECK_TYPES([struct termios2, struct termiox],,,
+AC_CHECK_TYPES([struct termios2],,,
[[#include ]])
AC_CHECK_MEMBERS([struct termios.c_ispeed, struct termios.c_ospeed,
struct termios2.c_ispeed, struct termios2.c_ospeed],,,
--
2.30.2
--- End Message ---
--- Begin Message ---
Source: libserialport
Source-Version: 0.1.1-4
Done: Jonathan McDowell
We believe that the bug you reported is fixed in the latest version of
libserialport, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 990...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Jonathan McDowell (supplier of updated libserialport package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Sat, 10 Jul 2021 17:21:59 +0100
Source: libserialport
Architecture: source
Version: 0.1.1-4
Distribution: unstable
Urgency: high
Maintainer: Debian Electronics Packaging Team
Changed-By: Jonathan McDowell
Closes: 990863
Changes:
libserialport (0.1.1-4) unstable; urgency=high
.
* Avoid the use of
Bug#990927: ensmallen FTBFS: test not run
Source: ensmallen Version: 2.17.0-1 Severity: serious Tags: ftbfs https://buildd.debian.org/status/package.php?p=ensmallen ... Unable to find executable: /<>/obj-x86_64-linux-gnu/ensmallen_tests 1/1 Test #1: ensmallen_tests ..***Not Run 0.00 sec 0% tests passed, 1 tests failed out of 1 Total Test time (real) = 0.00 sec The following tests FAILED: 1 - ensmallen_tests (Not Run) Errors while running CTest make[2]: *** [Makefile:119: test] Error 8 The successful ports architectures are building with nocheck.
Bug#990708: [debian-mysql] Bug#990708: mariadb-server-10.5: upgrade problems due to galera-3 -> galera-4 switch
On Sat, Jul 10, 2021 at 12:37 AM Andreas Beckmann wrote: > > On 10/07/2021 09.16, Otto Kekäläinen wrote: > > Seems this issue only happens with apt – not when using apt-get. > > Yuck. Can you ask the apt developers whether this is intended? I always > expected apt-get and apt to be functionally equivalent (i.e. to always > take the same decisions when installing/upgrading/removing packages > since they use the same resolver in the background). > (If they are not, testing apt, too, means doubling the number of > piuparts tests...) Filed https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=990922 > Have you tried default-mysql-server + (roundcube-core (or roundcube) or > cacti)? This yields the unwanted behavior (removing default-mysql-server > + mariadb-server-10.3 without installing mariadb-server-10.5)) with > apt-get in my piuparts tests both with and without --install-recommends. > I can find more examples that only work with --install-recommends. Tested Roundcube + default-mysql-server upgrades with both apt and apt-get, and with and without --no-install-recommends in https://salsa.debian.org/mariadb-team/mariadb-10.5/-/commit/c3f53fe664517bbce7f8ae67244e018f9086534c All passed fine.
