Le 21/08/2022 à 00:41, Luca Boccassi a écrit :
Yes I noticed the same thing when building images, this cross-device
check is a true annoyance and can't seem to find a workaround :-/
I can't find a solution, so unfortunately it looks like we have to
resort to maintainer scripts, which is awful b
On Sat, 20 Aug 2022 20:30:43 +0100 Luca Boccassi
wrote:
> On Fri, 19 Aug 2022 08:58:03 +0200 Michael Prokop
> wrote:
> > Hi,
> >
> > * Luca Boccassi [Thu Aug 18, 2022 at 03:20:22PM +0100]:
> > > On Thu, 2022-08-18 at 16:07 +0200, Raphaël Halimi wrote:
> >
> > > > And, last but not the least, I
On Fri, 19 Aug 2022 08:58:03 +0200 Michael Prokop
wrote:
> Hi,
>
> * Luca Boccassi [Thu Aug 18, 2022 at 03:20:22PM +0100]:
> > On Thu, 2022-08-18 at 16:07 +0200, Raphaël Halimi wrote:
>
> > > And, last but not the least, I see that /etc/resolv.conf is now
part of
> > > systemd-resolved files, w
Le 18/08/2022 à 21:29, Luca Boccassi a écrit :
Going for a custom setup means sometimes there is, sometimes there's
not. It's always a tradeoff. This breaking change means there's now a
supported way to run resolved, and it's the easiest possible way for
all those that weren't using it before, wh
Hi,
* Luca Boccassi [Thu Aug 18, 2022 at 03:20:22PM +0100]:
> On Thu, 2022-08-18 at 16:07 +0200, Raphaël Halimi wrote:
> > And, last but not the least, I see that /etc/resolv.conf is now part of
> > systemd-resolved files, which means that it would be deleted when the
> > systemd-resolved packa
On Thu, 2022-08-18 at 18:07 +0200, Raphaël Halimi wrote:
> Le 18/08/2022 à 16:59, Luca Boccassi a écrit :
> > No, custom and unsupported setups are unsupported. Compatibility is
> > provided for default environments, anything outside of it can and will
> > break at any given time, and it's not real
Le 18/08/2022 à 16:59, Luca Boccassi a écrit :
No, custom and unsupported setups are unsupported. Compatibility is
provided for default environments, anything outside of it can and will
break at any given time, and it's not really feasible to do otherwise
given the uncountable amount of possible
On Thu, 2022-08-18 at 16:46 +0200, Raphaël Halimi wrote:
> Le 18/08/2022 à 16:20, Luca Boccassi a écrit :
> > No, it is not, because no integration nor support was provided before.
> > It was an inhert and disabled service and binary.
> > The NEWS file covers the change adequately for custom setups
Le 18/08/2022 à 16:20, Luca Boccassi a écrit :
No, it is not, because no integration nor support was provided before.
It was an inhert and disabled service and binary.
The NEWS file covers the change adequately for custom setups. Custom
setups are always at risk of breakage.
I agree that it was
On Thu, 2022-08-18 at 16:07 +0200, Raphaël Halimi wrote:
> Le 17/08/2022 à 00:36, Luca Boccassi a écrit :
> > > Personally I see this as a regression, since resolved used to be part of
> > > systemd and thus readily available without installing additional packages.
> >
> > No support was provided
Le 17/08/2022 à 00:36, Luca Boccassi a écrit :
Personally I see this as a regression, since resolved used to be part of
systemd and thus readily available without installing additional packages.
No support was provided before for resolved, it was completely inhert,
hence it is not a regression.
On Tue, 2022-08-16 at 23:17 +0200, Raphaël Halimi wrote:
> Le 16/08/2022 à 22:59, Luca Boccassi a écrit :
> > You want resolved? Install the resolved package. Don't want resolved?
> > Don't install the package.
>
> Personally I see this as a regression, since resolved used to be part of
> systemd
Le 16/08/2022 à 22:59, Luca Boccassi a écrit :
You want resolved? Install the resolved package. Don't want resolved?
Don't install the package.
Personally I see this as a regression, since resolved used to be part of
systemd and thus readily available without installing additional packages.
On Sun, 14 Aug 2022 19:08:14 +0200 "Andrej Shadura"
wrote:
> Hi,
>
> On Sun, 14 Aug 2022, at 19:04, Michael Biebl wrote:
> >> I agree that the decision should be revisited, but for a different
> >> reason. I see no reason why resolvconf cannot be used with
resolved;
> >> OTOH the current split p
Hi,
On Sun, 14 Aug 2022, at 19:04, Michael Biebl wrote:
>> I agree that the decision should be revisited, but for a different
>> reason. I see no reason why resolvconf cannot be used with resolved;
>> OTOH the current split prevents that, which I find very undesirable.
>>
>> I was very surprise
Am 14.08.22 um 18:43 schrieb Andrej Shadura:
Hi,
On Sun, 14 Aug 2022 04:29:52 +0200 Raphaël Halimi
wrote:
And finally, my opinion:
After reading the mail thread in this bug report, I thought the plan
was to separate systemd-resolvconf (as Arch did, IIUC), not the entire
systemd-resolved se
Hi,
On Sun, 14 Aug 2022 04:29:52 +0200 Raphaël Halimi
wrote:
And finally, my opinion:
After reading the mail thread in this bug report, I thought the plan was
to separate systemd-resolvconf (as Arch did, IIUC), not the entire
systemd-resolved service.
IMHO this is a **very** bad idea, and
Dear developers,
I just upgraded a sid system and I noticed that the network was broken
on this machine.
I suppose the reason is that I had systemd-resolved enabled and
/etc/resolv.conf was symlinked to the stub resolver
(/run/systemd/resolve/stub-resolv.conf), and since the systemd-resolved
18 matches
Mail list logo
