Hello,
On Mon, 31 Mar 2025, Luca Boccassi wrote:
> Paul, could you please confirm whether resolved is a key package and
> thus cannot be removed anymore, or isn't and can? Thanks.
We don't care. Nobody wants to see systemd-resolved removed from Debian.
> So, just one simple question: why the ***
On Mar 31, Luca Boccassi wrote:
I am really sorry for the disruption, but unfortunately when features
need to be dropped, there's bound to be some of that. Let's keep in
mind though, that we are talking about an optional 2% popcon package.
Considering all the quality issues with systemd-resolve
Hi Luca (2025.04.01_18:06:38_+)
More generically, if you haven't seen on the MR, I had proposed several
alternatives to the submitter that are much safer and clearer, such as
a package conflict. The MR submitter's answer to the _mere suggestion_
was escalating to DAM.
Again, let me clarify:
On Tue, Apr 01, 2025 at 08:59:44PM +, Luca Boccassi wrote:
> > > Do the cloud images use avahi at all? Assuming I'm looking at the right
> > > manifest:
> > >
> > > https://cdimage.debian.org/images/cloud/trixie/daily/20250324-2061/debian-13-generic-amd64-daily-20250324-2061.json
> >
> > No, in
On Mon, Mar 31, 2025 at 10:30:41PM +0100, Luca Boccassi wrote:
> > Please try to find a less disruptive way to handle the resolved
> situation.
>
> I am really sorry for the disruption, but unfortunately when features
> need to be dropped, there's bound to be some of that. Let's keep in
> mind tho
Hi Josh (2025.04.02_17:56:48_+)
As you said, the TC or the project cannot *require* that a maintainer do
work they've objected to. However, I think it's reasonable for a
maintainer to say "OK, fine, this isn't the outcome I would prefer, but
I'll implement it, and I'd prefer to implement it m
On Tue, Apr 01, 2025 at 07:06:38PM +0100, Luca Boccassi wrote:
> Do the cloud images use avahi at all? Assuming I'm looking at the right
> manifest:
>
> https://cdimage.debian.org/images/cloud/trixie/daily/20250324-2061/debian-13-generic-amd64-daily-20250324-2061.json
No, in fact most cloud envir
On Wed, Apr 02, 2025 at 06:38:25PM +, Stefano Rivera wrote:
> Hi Josh (2025.04.02_17:56:48_+)
> > As you said, the TC or the project cannot *require* that a maintainer do
> > work they've objected to. However, I think it's reasonable for a
> > maintainer to say "OK, fine, this isn't the out
On Tue, 1 Apr 2025 23:42:26 + Stefano Rivera wrote:
> Hi Luca (2025.04.01_22:32:45_+)
> When you think about the TC rulings in that context, a refusal to accept
> an NMU to implement the TC ruling reads as an unwillingness to allow the
> TC to overrule the maintainer.
>
> How else are w
On Wed, 2 Apr 2025 20:01:19 + stefa...@debian.org wrote:
> Hi Josh (2025.04.02_19:27:34_+)
> >I think it's important to distinguish between "communication problem"
> >and "obstruction". "obstruction" is a problem that goes to DAM;
> >"communication problem" can potentially look like that, b
Hi Josh (2025.04.02_19:27:34_+)
I think it's important to distinguish between "communication problem"
and "obstruction". "obstruction" is a problem that goes to DAM;
"communication problem" can potentially look like that, but once it's
resolved as *not* being that, it should ideally be rapidl
On Wed, Apr 02, 2025 at 07:47:03AM +0200, Raphael Hertzog wrote:
On Wed, 2 Apr 2025 06:52:07 +0200 Marc Haber
wrote:
On Tue, Apr 01, 2025 at 10:32:45PM +, Luca Boccassi wrote:
>- Mar 24 13:59: first of several suggestions for implementation
>details and improvements on MR
Which MR are we
On Wed, 2 Apr 2025 06:52:07 +0200 Marc Haber
wrote:
> On Tue, Apr 01, 2025 at 10:32:45PM +, Luca Boccassi wrote:
> >- Mar 24 13:59: first of several suggestions for implementation
> >details and improvements on MR
>
> Which MR are we talking about here? I'd like to read up on that.
I assume
On Tue, Apr 01, 2025 at 10:32:45PM +, Luca Boccassi wrote:
- Mar 24 13:59: first of several suggestions for implementation
details and improvements on MR
Which MR are we talking about here? I'd like to read up on that.
Greetings
Marc
--
Hi Luca (2025.04.01_22:32:45_+)
I don't think getting into the timeline nitty gritty is the most
productive thing we can do, but let me give you the context that you're
missing. Skip over this part of my email, if you want to get onto
productive bits.
- Mar 4 11:58: TC is asked to open
On Tue, 1 Apr 2025 at 22:42, Noah Meyerhans wrote:
>
> On Tue, Apr 01, 2025 at 09:35:02PM +, Luca Boccassi wrote:
> > > > > Please let's not get ahead of ourselves. I think Stefano was simply
> > > > > pointing out something that had happned in the past, not any new DAM
> > > > > involvement.
On Tue, 1 Apr 2025 at 21:47, Stefano Rivera wrote:
>
> Hi Luca (2025.04.01_18:06:38_+)
> >More generically, if you haven't seen on the MR, I had proposed several
> >alternatives to the submitter that are much safer and clearer, such as
> >a package conflict. The MR submitter's answer to the _m
On Tue, Apr 01, 2025 at 09:35:02PM +, Luca Boccassi wrote:
> > > > Please let's not get ahead of ourselves. I think Stefano was simply
> > > > pointing out something that had happned in the past, not any new DAM
> > > > involvement.
> > >
> > > Sorry I should have been clearer: when I said war
Hi,
On Tue, 01 Apr 2025, Luca Boccassi wrote:
> > We don't care. Nobody wants to see systemd-resolved removed from Debian.
>
> Excuse me, but could you please clarify who is "we" in this statement?
> Are you speaking for the Release Team here?
No, I'm not part of the release team. But besides yo
On Tue, 1 Apr 2025 at 22:22, Noah Meyerhans wrote:
>
> On Tue, Apr 01, 2025 at 09:10:20PM +, Luca Boccassi wrote:
> > > Please let's not get ahead of ourselves. I think Stefano was simply
> > > pointing out something that had happned in the past, not any new DAM
> > > involvement.
> >
> > Sor
On Tue, Apr 01, 2025 at 09:10:20PM +, Luca Boccassi wrote:
> > Please let's not get ahead of ourselves. I think Stefano was simply
> > pointing out something that had happned in the past, not any new DAM
> > involvement.
>
> Sorry I should have been clearer: when I said warning, I literally
>
On Tue, 1 Apr 2025 at 22:07, Noah Meyerhans wrote:
>
> On Tue, Apr 01, 2025 at 08:59:44PM +, Luca Boccassi wrote:
> > > > Do the cloud images use avahi at all? Assuming I'm looking at the right
> > > > manifest:
> > > >
> > > > https://cdimage.debian.org/images/cloud/trixie/daily/20250324-2061
On Tue, Apr 01, 2025 at 08:47:25PM +, Stefano Rivera wrote:
> Hi Luca (2025.04.01_18:06:38_+)
> > More generically, if you haven't seen on the MR, I had proposed several
> > alternatives to the submitter that are much safer and clearer, such as
> > a package conflict. The MR submitter's ans
On Tue, 1 Apr 2025 at 19:50, Noah Meyerhans wrote:
>
> On Tue, Apr 01, 2025 at 07:06:38PM +0100, Luca Boccassi wrote:
> > Do the cloud images use avahi at all? Assuming I'm looking at the right
> > manifest:
> >
> > https://cdimage.debian.org/images/cloud/trixie/daily/20250324-2061/debian-13-gener
On Tue, 1 Apr 2025 10:59:57 +0200 Raphael Hertzog
wrote:
> Hello,
>
> On Mon, 31 Mar 2025, Luca Boccassi wrote:
> > Paul, could you please confirm whether resolved is a key package
and
> > thus cannot be removed anymore, or isn't and can? Thanks.
>
> We don't care. Nobody wants to see systemd-re
On Mon, 31 Mar 2025 19:31:10 -0400 Noah Meyerhans
wrote:
> On Mon, Mar 31, 2025 at 10:30:41PM +0100, Luca Boccassi wrote:
> > There are several issues. First and most importantly, the TC wants
half
> > of resolved (mdns) gone, but there seems to be some
misunderstanding
> > going around that it ca
On Tue, Apr 01, 2025 at 08:24:37AM +0200, Helmut Grohne wrote:
> > In the interest of trying to contribute potential solutions, one
> > possibility that comes to mind is to use a generator to avoid
> > conflicting with avahi. If the generator determines that avahi is
> > installed (I don't think i
Hi Noah,
Allow me to give background on the resolved matter without addressing
any other aspects of this. I've been managing the relevant ctte
discussion on that report.
On Mon, Mar 31, 2025 at 07:31:10PM -0400, Noah Meyerhans wrote:
> In the interest of trying to contribute potential solutions,
On Mon, 31 Mar 2025 22:30:41 +0100 Luca Boccassi wrote:
> Finally, and I understand you can't possibly care, but the only things
> I am getting out of working on this are burnout and grief, a constant
> barrage. Getting hate from random anonymous trolls is one thing and
> pretty much comes with t
On Mon, Mar 31, 2025 at 11:47:07PM +0200, Marco d'Itri wrote:
> > I am really sorry for the disruption, but unfortunately when features
> > need to be dropped, there's bound to be some of that. Let's keep in
> > mind though, that we are talking about an optional 2% popcon package.
> Considering all
Hi Luca (2025.03.31_21:30:41_+)
Speaking for myself, as a technical committee member, I haven't run any
of this by the rest of the committee.
There are several issues. First and most importantly, the TC wants half
of resolved (mdns) gone, but there seems to be some misunderstanding
going
Control: merge -1 1101762
On Fri, 28 Mar 2025 18:35:41 -0400 =?UTF-8?Q?Jeremy_B=C3=ADcha?=
wrote:
> Source: systemd
> Version: 257.4-5
> Severity: serious
> X-Debbugs-CC: debian-rele...@lists.debian.org
>
> systemd is unable to migrate to Testing because it abruptly dropped
> these packages:
> -
Source: systemd
Version: 257.4-5
Severity: serious
X-Debbugs-CC: debian-rele...@lists.debian.org
systemd is unable to migrate to Testing because it abruptly dropped
these packages:
- libnss-resolve
- systemd-resolved
which are dependencies of debian-cloud-images and openvpn-systemd-resolved.
See
33 matches
Mail list logo
