Re: Default network configuration system (was Re: proposal: dhcpcd-base as standard DHCP client starting with Trixie)
On Thu, Jun 22, 2023 at 01:39:02PM +0800, Paul Wise wrote: > On Tue, 2023-06-20 at 11:19 +0200, Lukas Maerdian wrote: > > > Netplan allows to configure both of those tools and is already being > > used across Ubuntu and in Debian cloud-images for this purpose. All > > while keeping full flexibility to use the underlying tool's native > > config files, should Netplan's simple YAML settings not be enough for > > a given complex usecase. > > Is Netplan able to parse an existing native config for each of the > tools and then output either Netplan configs or native configs for each > of the other network config tools? For example could you use Netplan to > auto-migrate from ifupdown to systemd-networkd or NetworkManager etc? Netplan is implemented as a systemd-generator [1] and primarily intended to be used as a one-directional genreator from Netplan YAML -> native config. We've been making some moves in adding bidirectional parsing capabilities for NetworkManager's keyfiles, though, e.g.: NM keyfile <-> Netplan YAML And there's also an ifupdown migration prototype, but that is pretty limited, didn't see much love in the recent years and might not live up to expectations, e.g.: ENABLE_TEST_COMMANDS=1 netplan migrate Cheers, Lukas [1] https://manpages.debian.org/testing/systemd/systemd.generator.7.en.html signature.asc Description: PGP signature
Bug#1038880: ITP: settle -- CLI tool for managing a digital Zettelkasten
Package: wnpp Severity: wishlist Owner: Jonas Smedegaard X-Debbugs-Cc: debian-devel@lists.debian.org -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 * Package name: settle Version : 0.39.9 Upstream Contact: xylous * URL : https://github.com/xylous/settle * License : Expat Programming Lang: Rust Description : CLI tool for managing a digital Zettelkasten Settle is a command-line tool that helps you manage your digital Zettelkasten. . A Zettelkasten (German for "slip box") or card file consists of small items of information stored on paper slips or cards. It is used metaphorically for hypertext knowledge applications using plaintext notes. This package will be maintained in the collaborative section of Salsa, at https://salsa.debian.org/debian/settle - Jonas -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmSUQjwACgkQLHwxRsGg ASGLBRAAqRfPXobrKccbLvCRyl6w/4Emqnrf4mLDJGbTlL0eKiRpxa9gaKlhvePZ B1mCqKo/3hQpyFope/vR1Qw7aSOKqSOn7ONWNoyzHOAg4fZEdqxp3LKNN1py1oXS GA069u0OnqNVDG38CCviD2+xS2//nlF/9bybzCZNcP0CrfWoPr2ubdJC4XGe8aIq YNL+jKC7JyG7wEGtvqgYSVfIsw4crmijufsGyZe9DSUbTDPfZyv0AQ1+SPfJPGVZ 4lTnYc7N3EZQ2wKcGiJfWqvuVJ08azo7xKzOpdzcsu0MX3C9EN5TAPQhnZu8jPuo 1wDz+W3O1Ucijgu0ThKoIjZbZCAJU8uZbL/tTPLxUREl3195cBKQ+KvqlnHhu2ic XqWzgDm16eDUEDS27BXqDZzUVeWBwOx3KBBwS8xW3fidM1vWFoH74+P6SzT0YJkb 0Pq7XnOK6sT0d6qHbeMWecB8aJrTznlpL/40+w1R427ZkeJ6MJfql2BQq2yjUsMl GJfwSOjH0FkUlG+SU+fViKw9lERca4gFyh/faVps/4PKKFKKIC/wC7qQyyoteSjY FgYHZ+O+zIXl8xFnREHJUklpylWjXn4Fi5oNIjcaZ+XqW/ySkBCgp6gi/1W3QnMG a8Gx1Q3wlfYLvW99Zpfqq8ukXWhbyoKhIE3VG1a1N4uLWJSrKio= =0Pcu -END PGP SIGNATURE-
Re: proposal: dhcpcd-base as standard DHCP client starting with Trixie
El 20/06/23 a las 08:29, Martin-Éric Racine escribió: > On Mon, Jun 19, 2023 at 9:11 PM Santiago Ruano Rincón > wrote: > > El 19/06/23 a las 13:54, Martin-Éric Racine escribió: > > > Greetings, > > > > > > Seeing how the ISC DHCP suite has reached EOL upstream, now might be a > > > good time to re-visit Debian's choice of standard DHCP client shipping > > > with priority:important. > > > > > > I hereby propose bin:dhcpcd-base: > > > > > > 1) already supported by ifupdown. > > > 2) dual stack (DHCPv4, Bonjour, RA, DHCPv6 with PD) with privilege > > > separation. > > > 3) writes both IPv4 and IPv6 name servers to /etc/resolv.conf > > > 4) supports /etc/resolv.conf.head and /etc/resolv.conf.tail > > > 5) a mere inet line in /etc/network/interfaces is sufficient to > > > configure both stacks. > > ... > > > > I agree that dhcpcd seems the best alternative to isc-dhcp-client for > > the moment, and I'll make the relevant changes in ifupdown as soon as I > > can. Josué, any thoughts? > > 1) As someone pointed out in the thread, the reason why > isc-dhcp-client had priority:important probably was to ensure that > debootstrap would pull it, since debootstrap ignores Recommends and > packages with a priority lower than standard. > > 2) However, as long as ifupdown explictly depends on a package, it can > also pull dependencies with a lower priority. Right now ifupdown > Recommends "isc-dhcp-client | dhcp-client" which debootstrap would > ignore. It would have to Depends "dhcpcd-base | dhcp-client" instead. > > 3) At that point, swapping the priority of isc-dhcp-client and > dhcpcd-base merely becomes "nice to have". Heck, the priority of both > could, in principle, be optional, just as long as ifupdown explicitly > Depends on a DHCP client, and the first alternative is a real package. I was about to bump dhcpcd-base as ifupdown dependency, but... if isc-client-dhcp is a Recommends, is because not all users want a dhcp client installed, where all the ipv4 is handled statically, and ipv6 is done via SLAAC. As a user, I don't want/need to pull in dhcpcd-base the next upgrade. So I'd prefer to go forward with the steps proposed by Simon, and s/isc-dhcp-client/dhcpcd-base in ifupdown's Recommends: Unless there is a strong objection, I'll file the override bug report. Cheers, -- Santiago signature.asc Description: PGP signature
Re: proposal: dhcpcd-base as standard DHCP client starting with Trixie
On Thu, Jun 22, 2023 at 3:58 PM Santiago Ruano Rincón wrote: > El 20/06/23 a las 08:29, Martin-Éric Racine escribió: > > On Mon, Jun 19, 2023 at 9:11 PM Santiago Ruano Rincón > > wrote: > > > El 19/06/23 a las 13:54, Martin-Éric Racine escribió: > > > > Greetings, > > > > > > > > Seeing how the ISC DHCP suite has reached EOL upstream, now might be a > > > > good time to re-visit Debian's choice of standard DHCP client shipping > > > > with priority:important. > > > > > > > > I hereby propose bin:dhcpcd-base: > > > > > > > > 1) already supported by ifupdown. > > > > 2) dual stack (DHCPv4, Bonjour, RA, DHCPv6 with PD) with privilege > > > > separation. > > > > 3) writes both IPv4 and IPv6 name servers to /etc/resolv.conf > > > > 4) supports /etc/resolv.conf.head and /etc/resolv.conf.tail > > > > 5) a mere inet line in /etc/network/interfaces is sufficient to > > > > configure both stacks. > > > ... > > > > > > I agree that dhcpcd seems the best alternative to isc-dhcp-client for > > > the moment, and I'll make the relevant changes in ifupdown as soon as I > > > can. Josué, any thoughts? > > > > 1) As someone pointed out in the thread, the reason why > > isc-dhcp-client had priority:important probably was to ensure that > > debootstrap would pull it, since debootstrap ignores Recommends and > > packages with a priority lower than standard. > > > > 2) However, as long as ifupdown explictly depends on a package, it can > > also pull dependencies with a lower priority. Right now ifupdown > > Recommends "isc-dhcp-client | dhcp-client" which debootstrap would > > ignore. It would have to Depends "dhcpcd-base | dhcp-client" instead. > > > > 3) At that point, swapping the priority of isc-dhcp-client and > > dhcpcd-base merely becomes "nice to have". Heck, the priority of both > > could, in principle, be optional, just as long as ifupdown explicitly > > Depends on a DHCP client, and the first alternative is a real package. > > I was about to bump dhcpcd-base as ifupdown dependency, but... if > isc-client-dhcp is a Recommends, is because not all users want a dhcp > client installed, where all the ipv4 is handled statically, and ipv6 is > done via SLAAC. As a user, I don't want/need to pull in dhcpcd-base the > next upgrade. > > So I'd prefer to go forward with the steps proposed by Simon, and > s/isc-dhcp-client/dhcpcd-base in ifupdown's Recommends: > Unless there is a strong objection, I'll file the override bug report. The point has always been to ship some ifupdown-supported DHCP client by default. This can be done either by keeping the default client's priority to important or by making ifupdown Depends on one. I prefer the later. Martin-Éric
Re: proposal: dhcpcd-base as standard DHCP client starting with Trixie
On Jun 22, Martin-Éric Racine wrote: > The point has always been to ship some ifupdown-supported DHCP client > by default. This can be done either by keeping the default client's > priority to important or by making ifupdown Depends on one. I prefer > the later. It would be totally unacceptable to make ifupdown Depend on a DHCP client, because this would bloat most server installations. But I would be happy with a Recommends. It's not like the people whose server needs a DHCP client do not know that they need to install one. -- ciao, Marco signature.asc Description: PGP signature
Re: proposal: dhcpcd-base as standard DHCP client starting with Trixie
Marco d'Itri writes: > On Jun 22, Martin-Éric Racine wrote: > >> The point has always been to ship some ifupdown-supported DHCP client >> by default. This can be done either by keeping the default client's >> priority to important or by making ifupdown Depends on one. I prefer >> the later. > It would be totally unacceptable to make ifupdown Depend on a DHCP > client, because this would bloat most server installations. > But I would be happy with a Recommends. It's not like the people whose > server needs a DHCP client do not know that they need to install one. The DHCP client I have to hand says: Installed-Size: 686 ...so while I can see an argument about bloating a server install, I'm not sure it's strong enough to warrant "totally unacceptable"? Regards, Matthew -- "At least you know where you are with Microsoft." "True. I just wish I'd brought a paddle." http://www.debian.org
Re: FTBFS on all recent uploads
Hi, 在 2023-06-20星期二的 06:31 +0200，Joachim Zobel写道： > Hi. > > I have a FTBFS on all uploads after the end of the freeze. Example: > https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/gap-aclib.html > > All these packages had been changed to compat 13. Unfortunately I have > no idea why I get these. I can see two logs of successful builds and a > diff for them. At the end of each log I find reproducible ➤ FTBFS, so > this probably is because my build fails to be reproducible. However the > only diff I see is the diff between the build logs. > > Any hints on what to do about these would be helpful. In the link above, when clicking "build2" under amd64 1.3.2-3--build2, the log shows that the build machine raised an error before your source code actually got built. It might be a machine configuration error. Forwarding your email to Debian reproducible-builds mailing list since they may know more about it. Thanks, Boyuan Yang signature.asc Description: This is a digitally signed message part
Re: Bug#1038812: ITP: sexp -- S-expressions parser and generator C++ library and command-line tool
Hi, On Wed, Jun 21, 2023 at 12:20:52PM -0400, Daniel Kahn Gillmor wrote: > * URL : https://github.com/rnp/sexp this URL is 404, maybe you meant https://github.com/rnpgp/sexp ? Thanks, Alex
Re: FTBFS on all recent uploads
On 2023-06-22, Boyuan Yang wrote: > 在 2023-06-20星期二的 06:31 +0200，Joachim Zobel写道： >> I have a FTBFS on all uploads after the end of the freeze. Example: >> https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/gap-aclib.html >> >> All these packages had been changed to compat 13. Unfortunately I have >> no idea why I get these. I can see two logs of successful builds and a >> diff for them. At the end of each log I find reproducible ➤ FTBFS, so >> this probably is because my build fails to be reproducible. However the >> only diff I see is the diff between the build logs. >> >> Any hints on what to do about these would be helpful. > > In the link above, when clicking "build2" under amd64 1.3.2-3--build2, the log > shows that the build machine raised an error before your source code > actually got built. It might be a machine configuration error. Forwarding > your email to Debian reproducible-builds mailing list since they may know > more about it. We had a few glitches after the bookworm released, but I *think* they should be sorted out by now... FTBFS do get rescheduled fairly often, and if you really need, they can be manually rescheduled (if you are a debian developer, you should be able to click on the triangle of arrows to reschedule). live well, vagrant signature.asc Description: PGP signature
Googletest 1.13 requires at least C++14
Hi, Please CC me in any reply. A new googletest package for 1.13.0 just hit unstable and I now realise it requires at least C++14. From autopkgtests, I noted at least one build failure because of this. I'm hoping most code can simply opt to build at C++14 or later. However, I'm willing to re-introduce a googletest 1.12 if need be. Please get in touch if you have a package that cannot be made to build with googletest 1.13. Thanks, -Steve signature.asc Description: This is a digitally signed message part.
Re: proposal: dhcpcd-base as standard DHCP client starting with Trixie
On 22.06.23 16:03, Marco d'Itri wrote: On Jun 22, Martin-Éric Racine wrote: The point has always been to ship some ifupdown-supported DHCP client by default. This can be done either by keeping the default client's priority to important or by making ifupdown Depends on one. I prefer the later. It would be totally unacceptable to make ifupdown Depend on a DHCP client, because this would bloat most server installations. But I would be happy with a Recommends. It's not like the people whose server needs a DHCP client do not know that they need to install one. TBH time is too short to manually provision IP addresses on servers. Kind regards Philipp Kern
Re: proposal: dhcpcd-base as standard DHCP client starting with Trixie
On Thu, Jun 22, 2023 at 08:51:01PM +0200, Philipp Kern wrote: > TBH time is too short to manually provision IP addresses on servers. And DHCP is gladly enough entirely optional since SLAAC exists. But for that you need systemd-networkd/systemd-resolved or a whole bunch of other software. Bastian -- "... freedom ... is a worship word..." "It is our worship word too." -- Cloud William and Kirk, "The Omega Glory", stardate unknown
Re: proposal: dhcpcd-base as standard DHCP client starting with Trixie
On Thu, 2023-06-22 at 20:51 +0200, Philipp Kern wrote: > On 22.06.23 16:03, Marco d'Itri wrote: > > > TBH time is too short to manually provision IP addresses on servers. > IP addresses are just one of many things that can be instantiated by /etc/network/interfaces, /etc/network/interfaces.d/, and /etc/netplan/whatever.yaml. Will dhcpcd-base provision an IP address for a one interface and not interfere with any existing interfaces or routes (e.g. bridged interfaces, static VPN routes, containers, etc.) -Jim P.
Work-needing packages report for Jun 23, 2023
The following is a listing of packages for which help has been requested through the WNPP (Work-Needing and Prospective Packages) system in the last week. Total number of orphaned packages: 1200 (new: 5) Total number of packages offered up for adoption: 151 (new: 1) Total number of packages requested help for: 58 (new: 0) Please refer to https://www.debian.org/devel/wnpp/ for more information. The following packages have been orphaned: acr (#1038633), orphaned 3 days ago Description: autoconf like tool Installations reported by Popcon: 22 Bug Report URL: https://bugs.debian.org/1038633 gpac (#1038784), orphaned yesterday Description: GPAC Project on Advanced Content - utilities Reverse Depends: ccextractor gpac gpac-modules-base libgpac-dev ogmrip Installations reported by Popcon: 1065 Bug Report URL: https://bugs.debian.org/1038784 labgrid (#1038666), orphaned 3 days ago Description: Embedded board control programs Reverse Depends: labgrid Installations reported by Popcon: 12 Bug Report URL: https://bugs.debian.org/1038666 tudu (#1038634), orphaned 3 days ago Description: Command line hierarchical ToDo list Installations reported by Popcon: 34 Bug Report URL: https://bugs.debian.org/1038634 zlmdb (#1038667), orphaned 3 days ago Description: Object-relational in-memory database layer based on LMDB Reverse Depends: python3-crossbar Installations reported by Popcon: 1 Bug Report URL: https://bugs.debian.org/1038667 1195 older packages have been omitted from this listing, see https://www.debian.org/devel/wnpp/orphaned for a complete list. The following packages have been given up for adoption: arbtt (#1038397), offered 5 days ago Description: Automatic Rule-Based Time Tracker Installations reported by Popcon: 62 Bug Report URL: https://bugs.debian.org/1038397 150 older packages have been omitted from this listing, see https://www.debian.org/devel/wnpp/rfa_bypackage for a complete list. For the following packages help is requested: apache2 (#910917), requested 1713 days ago Description: Apache HTTP Server Reverse Depends: apache2 apache2-ssl-dev apache2-suexec-custom apache2-suexec-pristine backuppc bfh-container-server courier-webadmin cvsweb debbugs-web debian-edu-router-deployserver (126 more omitted) Installations reported by Popcon: 102043 Bug Report URL: https://bugs.debian.org/910917 apparmor (#1006872), requested 472 days ago Description: user-space parser utility for AppArmor Reverse Depends: apparmor-notify apparmor-profiles apparmor-profiles-extra apparmor-utils content-hub-testability dbus-broker dbus-daemon dbus-tests debian-cloud-images-packages dovecot-core (24 more omitted) Installations reported by Popcon: 202627 Bug Report URL: https://bugs.debian.org/1006872 autopkgtest (#846328), requested 2395 days ago Description: automatic as-installed testing for Debian packages Reverse Depends: debci-worker sbuild-qemu Installations reported by Popcon: 1156 Bug Report URL: https://bugs.debian.org/846328 balsa (#642906), requested 4288 days ago Description: An e-mail client for GNOME Reverse Depends: balsa Installations reported by Popcon: 605 Bug Report URL: https://bugs.debian.org/642906 cargo (#860116), requested 2263 days ago Description: Rust package manager Reverse Depends: dh-cargo python3-setuptools-rust rust-all Installations reported by Popcon: 2916 Bug Report URL: https://bugs.debian.org/860116 chromium (#1016047), requested 331 days ago Description: web browser Reverse Depends: chromium chromium-driver chromium-l10n chromium-shell node-puppeteer qunit-selenium x2gothinclient-minidesktop Installations reported by Popcon: 24823 Bug Report URL: https://bugs.debian.org/1016047 courier (#978755), requested 903 days ago Description: Courier mail server Reverse Depends: courier-faxmail courier-filter-perl courier-imap courier-ldap courier-mlm courier-mta courier-pcp courier-pop courier-webadmin couriergrey (3 more omitted) Installations reported by Popcon: 742 Bug Report URL: https://bugs.debian.org/978755 cron (#984736), requested 837 days ago Description: new maintainer need Reverse Depends: apticron autolog backintime-common bcron btrfsmaintenance buildd checksecurity clamtk cricket cron (25 more omitted) Installations reported by Popcon: 217752 Bug Report URL: https://bugs.debian.org/984736 cyrus-imapd (#921717), requested 1595 days ago Description:
