Bug#818880: marked as done (dhcpcd5: sometimes removes route to local network on wakeup)
Your message dated Mon, 27 Jun 2022 18:23:34 +0300 with message-id and subject line no answer from submitter in 2 years, closing has caused the Debian Bug report #818880, regarding dhcpcd5: sometimes removes route to local network on wakeup 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.) -- 818880: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=818880 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: dhcpcd5 Version: 6.9.3-1 Severity: important Hi, I've a couple of systems that spend a lot of time in suspend and should ideally use DHCP for network configuration. isc-dhcp client doesn't work in that scenario because it'll never renew the lease (#812186), so I switched to dhcpcd5. This package will renew the lease on wakeup, but sometimes screw up routing in the process. When it fails, the routing table, usually Kernel IP routing table Destination Gateway Genmask Flags Metric RefUse Iface 0.0.0.0 192.168.0.1 0.0.0.0 UG20200 enp2s0 192.168.0.0 0.0.0.0 255.255.255.0 U 20200 enp2s0 will be missing the second line. Since my firewall doesn't route packets with source and destination on the LAN, that means no local connectivity at all. ifdown enp2s0 && ifup enp2s0 helps. It doesn't *always* happen and I haven't discerned a pattern yet. Anyway, a journal excerpt from a failed attempt is attached, the DHCP server is jessie's dnsmasq, in case it matters. Regards, Christian -- System Information: Debian Release: stretch/sid APT prefers testing-updates APT policy: (500, 'testing-updates'), (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 4.3.0-1-amd64 (SMP w/2 CPU cores) Locale: LANG=de_AT.UTF-8, LC_CTYPE=de_AT.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages dhcpcd5 depends on: ii libc6 2.22-3 Versions of packages dhcpcd5 recommends: pn openresolv | resolvconf Versions of packages dhcpcd5 suggests: pn dhcpcd-gtk -- no debconf information -- Logs begin at Fre 2016-03-11 20:32:15 CET, end at Mon 2016-03-21 11:31:58 CET. -- Mär 21 11:15:53 fatbeard kernel: (NULL device *): firmware: direct-loading firmware amd-ucode/microcode_amd.bin Mär 21 11:15:53 fatbeard kernel: Freezing user space processes ... (elapsed 0.001 seconds) done. Mär 21 11:15:53 fatbeard kernel: Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done. Mär 21 11:15:53 fatbeard kernel: PM: Suspending system (mem) Mär 21 11:15:53 fatbeard kernel: Suspending console(s) (use no_console_suspend to debug) Mär 21 11:15:53 fatbeard kernel: sd 2:0:0:0: [sdb] Synchronizing SCSI cache Mär 21 11:15:53 fatbeard kernel: sd 0:0:0:0: [sda] Synchronizing SCSI cache Mär 21 11:15:53 fatbeard kernel: sd 2:0:0:0: [sdb] Stopping disk Mär 21 11:15:53 fatbeard kernel: sd 0:0:0:0: [sda] Stopping disk Mär 21 11:15:53 fatbeard kernel: PM: suspend of devices complete after 800.390 msecs Mär 21 11:15:53 fatbeard kernel: PM: late suspend of devices complete after 0.522 msecs Mär 21 11:15:53 fatbeard kernel: pcieport :00:0a.0: System wakeup enabled by ACPI Mär 21 11:15:53 fatbeard kernel: ohci-pci :00:14.5: System wakeup enabled by ACPI Mär 21 11:15:53 fatbeard kernel: ehci-pci :00:13.2: System wakeup enabled by ACPI Mär 21 11:15:53 fatbeard kernel: ohci-pci :00:13.1: System wakeup enabled by ACPI Mär 21 11:15:53 fatbeard kernel: ohci-pci :00:13.0: System wakeup enabled by ACPI Mär 21 11:15:53 fatbeard kernel: ehci-pci :00:12.2: System wakeup enabled by ACPI Mär 21 11:15:53 fatbeard kernel: ohci-pci :00:12.1: System wakeup enabled by ACPI Mär 21 11:15:53 fatbeard kernel: ohci-pci :00:12.0: System wakeup enabled by ACPI Mär 21 11:15:53 fatbeard kernel: PM: noirq suspend of devices complete after 15.580 msecs Mär 21 11:15:53 fatbeard kernel: ACPI: Preparing to enter system sleep state S3 Mär 21 11:15:53 fatbeard kernel: PM: Saving platform NVS memory Mär 21 11:15:53 fatbeard kernel: Disabling non-boot CPUs ... Mär 21 11:15:53 fatbeard kernel: Broke affinity for irq 1 Mär 21 11:15:53 fatbeard kernel: Broke affinity for irq 12 Mär 21 11:15:53 fatbeard kernel: Broke affinity for irq 14 Mär 21 11:15:53 fatbeard kernel: Broke affinity for irq 16 Mär 21 11:15:53 fatbeard kernel: Broke affinity for irq 18 Mär 21 11:15:53 fatbeard kernel: Broke affinity for irq 19 Mär 21 11:15:53 fatbeard kernel: Broke affinity for irq 22 Mär 21 11:15:53 fatbeard kernel: Broke affinity for irq 25 Mär 21 11:15:53 fatbeard kernel: sm
Bug#820069: dhcpcd5: pending
I'm adopting this package. This issue will be resolved by splitting the binaries, exit hooks and manual pages into dhcpcd-base (provides: dhcp-client) and leaving only the init.d script and systemd unit in dhcpcd5. This way, those who only need the binaries as a backend for /etc/network/interfaces (ifupdown) can install dhcpcd-base, while those who also need the daemonized automation can install dhcpcd5. Martin-Éric
Bug#821405: marked as done (dhcpcd no longer starts wpa_supplicant)
Your message dated Mon, 27 Jun 2022 18:30:03 +0300 with message-id and subject line no answer from submitter in 2 years has caused the Debian Bug report #821405, regarding dhcpcd no longer starts wpa_supplicant 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.) -- 821405: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=821405 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: dhcpcd5 Version: 6.10.1-1 Since upgrading to 6.10.1-1, wpa_supplicant is no longer automatically started when I run dhcpcd. Everything works fine if I start wpa_supplicant by hand. I'm starting dhcpcd by hand, not from an init script, and the version of wpa_supplicant is 2.3-2.3. --- End Message --- --- Begin Message --- No answer from submitter in 2 years. Closing. Martin-Éric--- End Message ---
Bug#1013329: razor 2.85 is really 2.84
Hi vagrant, thanks for pushing this to bdo. On 21/06/2022 23:41, Vagrant Cascadian wrote: On 2022-06-20, Malte S. Stretz wrote: TL;DR: It looks like the Debian 2.85 razor package you've been recently working on according to https://salsa.debian.org/debian/razor/-/commits/debian/latest is really 2.84 >> […] The current "upstream" version was uploaded to debian in 2008 currently present in old-old-stable (e.g. two releases prior to the current stable release): https://tracker.debian.org/news/303771/accepted-razor-1285-1-source-amd64/ The best thing might be to actually update to the newest upstream release, if there is indeed one newer than 2.85... and kind of ignore that unfortunate problem... ... though there might be security issues that are not correctly tracked that are fixed in the upstream 2.85, but not in the debian packages because of the version discrepancy; that might be worth confirming and possibly notifying the security team. The good news: There doesn't seem to be any security relevant changes in https://github.com/toddr/Razor2-Client-Agent/compare/v2.84...v2.85 There even don't seem to be many functional changes, most of the changes are cleanup/build related things. v2.86 also was just a build related thing. The bad news: All the current Debian patches won't apply anymore since there was some excessive reformatting applied upstream. OTOH will some of them not be needed anymore since it looks they were partially incorporated upstream. All that said, not sure I have the energy to tackle this kind of tangled problem at the moment... Would you like help with that? My Debian packaging know how is a bit rusty but I could create a PR on Salsa which * Merges the Upstream repo into the current Salsa repo (ie. switching it over to https://wiki.debian.org/PackagingWithGit#Using_the_upstream_repo without losing any history) at upstream v2.84 * Fixes up the Quilt patches and merge that state with upstream v2.85 * Bump the whole stuff to v2.86 What do I get out of that? I'd like to include my IPv6 patch on top of all of this. Regards, Malte
Bug#1013948: zfs-fuse: Homepage in Metadata points to porn site
Package: zfs-fuse Version: 0.7.0-21 Severity: minor Dear Maintainer, at least the following package versions list the following homepage in the package metadata (possibly somehwhere else, too?): Version: 0.7.0-22+b1 Homepage: http://zfs-fuse.net Version: 0.7.0-21 Homepage: http://zfs-fuse.net The domain currently points to a porn site. I don't know if this is a domain hijack, or a hacked homepage ... but maybe someone can check with upstream? Best wishes, Julia -- System Information: Debian Release: 11.3 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable'), (95, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 5.18.0-0.bpo.1-amd64 (SMP w/4 CPU threads; PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages zfs-fuse depends on: ii fuse 2.9.9-5 ii libaio10.3.112-9 ii libc6 2.31-13+deb11u3 ii libfuse2 2.9.9-5 ii libssl1.1 1.1.1n-0+deb11u3 ii lsb-base 11.1.0 ii zlib1g 1:1.2.11.dfsg-2+deb11u1 zfs-fuse recommends no packages. Versions of packages zfs-fuse suggests: pn kpartx pn nfs-kernel-server -- no debconf information
mcu8051ide is marked for autoremoval from testing
mcu8051ide 1.4.9-2 is marked for autoremoval from testing on 2022-07-28 It (build-)depends on packages with these RC bugs: 1013877: libtk-img: add _TIFFsetString to its internal tiff library https://bugs.debian.org/1013877 1013878: libtk-img: add _TIFFsetString to its internal tiff library https://bugs.debian.org/1013878 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
Bug#1012624: Update golang-github-blevesearch-bleve dependency to bbolt
Source: golang-github-blevesearch-bleve Version: 0.5.0+git20170912.278.6eea5b78-5 Followup-For: Bug #1012624 Hi, The golang-github-blevesearch-bleve package seems to be orphaned from Debian go team view. BTW, the golang-github-blevesearch-bleve upstream had switched to bbolt from here [0] I think. [0]: https://github.com/blevesearch/bleve/blob/master/go.mod#L28 -- Best Regards, signature.asc Description: PGP signature
