Hi,
On 7/11/24 9:55 PM, Jonas Smedegaard wrote:
Quoting Philipp Kern (2024-07-11 21:13:42)
I'd - at the very least - would like to see a statement why a fork is
necessary. Innovation can happen in forks. But they don't necessarily
need to be in the archive to make a point.
dh-cargo is desig
On Fri, 2024-07-12 at 10:44 +0500, Andrey Rakhmatullin wrote:
> On Fri, Jul 12, 2024 at 05:54:59AM +0100, Phil Wyett wrote:
> > Morning all,
> >
> > As we embark on a new process where packages submitted to mentors are
> > reviewed
> > and brought to a "Ready" stage for then busy DDs who are grac
On Fri, Jul 12, 2024 at 05:54:59AM +0100, Phil Wyett wrote:
> Morning all,
>
> As we embark on a new process where packages submitted to mentors are reviewed
> and brought to a "Ready" stage for then busy DDs who are gracious enough to
> give
> their time to review and possibly sponsor into Debia
Morning all,
As we embark on a new process where packages submitted to mentors are reviewed
and brought to a "Ready" stage for then busy DDs who are gracious enough to give
their time to review and possibly sponsor into Debian. We have a unique problem
(one which is now a nice one to have to be ho
Quoting Philipp Kern (2024-07-11 21:13:42)
> On 11.07.24 18:06, Jonas Smedegaard wrote:
> > * Package name: dh-rust
> >Version : 0.0.1
> >Upstream Contact: build-common team
> >
> > * URL : https://salsa.debian.org/build-common-team/dh-rust
>
> This ("build-common
Hi,
On 11.07.24 18:06, Jonas Smedegaard wrote:
* Package name: dh-rust
Version : 0.0.1
Upstream Contact: build-common team
* URL : https://salsa.debian.org/build-common-team/dh-rust
This ("build-common") reminded me of cdbs. Can we not have another
schism and ac
Hi Nilesh,
Quoting Nilesh Patra (2024-07-11 19:57:56)
> On Thu, Jul 11, 2024 at 06:06:21PM +0200, Jonas Smedegaard wrote:
> > * Package name: dh-rust
>
> I would be happy if this makes it to the archive, though. Would be
> easier to have a dh for rust which would be specifically useful to
> b
On July 11, 2024 7:57:56 PM GMT+02:00, Nilesh Patra wrote:
>On Thu, Jul 11, 2024 at 06:06:21PM +0200, Jonas Smedegaard wrote:
>> Package: wnpp
>> Severity: wishlist
>> Owner: Jonas Smedegaard
>> X-Debbugs-Cc: debian-devel@lists.debian.org, build-common team
>>
>>
>> -BEGIN PGP SIGNED ME
On Thu, Jul 11, 2024 at 06:06:21PM +0200, Jonas Smedegaard wrote:
> Package: wnpp
> Severity: wishlist
> Owner: Jonas Smedegaard
> X-Debbugs-Cc: debian-devel@lists.debian.org, build-common team
>
>
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA512
>
> * Package name: dh-rust
I would be
On Thu, Jul 11, 2024 at 06:06:21PM GMT, Jonas Smedegaard wrote:
> Package: wnpp
> Severity: wishlist
> Owner: Jonas Smedegaard
> X-Debbugs-Cc: debian-devel@lists.debian.org, build-common team
>
Hi!
(all of what follows is my personal opinion and not coordinated with
other members of the Rust p
Package: wnpp
Severity: wishlist
Owner: Jonas Smedegaard
X-Debbugs-Cc: debian-devel@lists.debian.org, build-common team
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
* Package name: dh-rust
Version : 0.0.1
Upstream Contact: build-common team
* URL : https://salsa
Jumping in in the middle of the conversation, but couldn't resist
On 11/7/24 10:23, Martin-Éric Racine wrote:
Claiming to offer a drop-in substitute all while nudging people
towards a new paradigm is not welcome.
If ifupdown's paradigm were working for people we wouldn't be having this
con
On 11/7/24 8:16, Marc Haber wrote:
On Wed, 10 Jul 2024 23:15:24 +0200, Ansgar ? wrote:
While there are numerous alternative implementations of DHCP client,
the Linux world seems to be without a working DHCP relay
implementation in those days. That's REALLY bad for an installation
with Linux rout
On 10.07.24 22:14, Simon Richter wrote:
It is supported *now*, but the roadmap is unclear -- that support
could be discontinued at any moment, and it would not be the first
time a feature Debian relied on was removed.
I don't think that the systemd people have *any* intention to
substantiall
El 09/07/24 a las 11:45, Simon McVittie escribió:
> On Tue, 09 Jul 2024 at 10:57:39 +0200, Matthias Urlichs wrote:
> > Agreed: either it's drop-in compatible or we may as well switch the
> > default to NM and/or systemd-networkd.
> >
> > Well, here's a heretical thought: why don't we do th
Package: wnpp
Severity: wishlist
Owner: Michael Fladischer
X-Debbugs-Cc: debian-devel@lists.debian.org
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
* Package name: python-jq
Version : 1.7.0
Upstream Contact: Michael Williamson
* URL : https://github.com/mwilliamso
On Thu, 11 Jul 2024 13:48:06 +0200, Marco d'Itri wrote:
>On Jul 11, Matthias Urlichs wrote:
>
>> On 11.07.24 08:13, Marc Haber wrote:
>> > Therefore, you could change
>> > configuration while the Interfacce was up and then just say "ifdown ;
>> > ifup" and be fine. No network configuration softwa
El 09/07/24 a las 11:25, Daniel Gröber escribió:
> Hi Santiago,
>
> On Mon, Jul 08, 2024 at 12:23:16PM -0300, Santiago Ruano Rincón wrote:
> > > > Santiago, how do you feel about ifupdown's future maintainability and
> > > > feature development? I honestly never looked into why people started
> >
On Jul 11, Matthias Urlichs wrote:
> On 11.07.24 08:13, Marc Haber wrote:
> > Therefore, you could change
> > configuration while the Interfacce was up and then just say "ifdown ;
> > ifup" and be fine. No network configuration software up to today has
> > THAT feature.
> Shouldn't "systemctl rel
On 11.07.24 11:13, Marco d'Itri wrote:
On Jul 11, Philip Hands wrote:
I've only seen netplan mentioned in passing in this thread so far.
Because I believe that Netplan is the answer to a question that nobody
asked here.
It has all the disadvantages of switching to a new configuration format,
Package: wnpp
Severity: wishlist
Owner: Edward Betts
X-Debbugs-Cc: debian-devel@lists.debian.org, debian-pyt...@lists.debian.org
* Package name: korean-lunar-calendar
Version : 0.3.1
Upstream Author : Jinil Lee
* URL : https://github.com/usingsky/korean_lunar_calendar
to 11. heinäk. 2024 klo 12.34 Daniel Gröber (d...@darkboxed.org) kirjoitti:
> On Thu, Jul 11, 2024 at 11:23:38AM +0300, Martin-Éric Racine wrote:
> > > > Claiming to offer a drop-in substitute all while nudging people
> > > > towards a new paradigm is not welcome.
> > >
> > > If ifupdown's paradigm
On 11.07.24 08:13, Marc Haber wrote:
Therefore, you could change
configuration while the Interfacce was up and then just say "ifdown ;
ifup" and be fine. No network configuration software up to today has
THAT feature.
Shouldn't "systemctl reload systemd-networkd" do exactly that?
--
-- regards
Am Di, Jul 09, 2024 at 20:03:52 +0200 schrieb Matthias Urlichs:
Well, I've been apt-purging ifupdown for almost a decade by now and
didn't yet miss any of it.
I would never purge ifupdown. I like the nice configuration in one file
that you can find no matter if it is an old or new Debian insta
Hi Vincent, Martin,
On Thu, Jul 11, 2024 at 07:54:50AM +0200, Vincent Bernat wrote:
> > From where I'm sitting ifupdown2 is completely out of the question as *the*
> > Debian ifupdown since it doesn't even support *basic* IPv6 use-cases like
> > DHCPv6. Upstream community seems nonexistant since
On Jul 10, Simon Richter wrote:
> It is supported *now*, but the roadmap is unclear -- that support could be
> discontinued at any moment, and it would not be the first time a feature
> Debian relied on was removed.
You have manufactured a non-existing issue and then decided to get
anxious about
On 11.07.24 02:18, Thomas Goirand wrote:
On 7/10/24 20:03, Michael Biebl wrote:
Since there is a lot of support for this idea, the next logical step as smcv
said, would be to make d-i/netcfg networkd aware. At the beginning, this could
be opt-in (for testing purposes) and we could make it the
On Jul 11, Vincent Bernat wrote:
> This is quite unfair. Cumulus tried very hard to make ifupdown2 a community
> projects, with notably a presentation at Debconf 14 and Debconf 16. One of
> its killer feature is the ability to go from the running state to the target
> state with one command (ifre
On Jul 11, Philip Hands wrote:
> I've only seen netplan mentioned in passing in this thread so far.
Because I believe that Netplan is the answer to a question that nobody
asked here.
It has all the disadvantages of switching to a new configuration format,
but then it limits you to the features
On 11.07.24 09:16, Philip Hands wrote:
Simon McVittie writes:
On Tue, 09 Jul 2024 at 16:21:16 +0200, Ansgar 🙀 wrote:
On Tue, 2024-07-09 at 22:44 +0900, Simon Richter wrote:
I believe NM does not have a fixed configuration format, but only a dbus
API.
It's perfectly fine to edit configurati
ti 9. heinäk. 2024 klo 15.13 Daniel Gröber (d...@darkboxed.org) kirjoitti:
> Users may choose to opt-in to the more declarative "use" stanzas if they
> wish and I'd expect any new upstream executors like vrf will need them
> (haven't tried) but not traditional stanzas or if-*.d based extensions.
>
Simon McVittie writes:
> On Tue, 09 Jul 2024 at 16:21:16 +0200, Ansgar 🙀 wrote:
>> On Tue, 2024-07-09 at 22:44 +0900, Simon Richter wrote:
>> > I believe NM does not have a fixed configuration format, but only a dbus
>> > API.
>>
>> It's perfectly fine to edit configuration files for NM manuall
32 matches
Mail list logo
