On Tue, 2022-10-25 at 07:47 +0700, Arnaud Rebillout wrote:
> On 24/10/2022 21:55, Christopher Obbard wrote:
> > I'm more leaning on just adding it as a direct Dependency to the
> > Debos
> > package and seeing if anyone moans...
> Works for me.
Seems installing systemd-resolved breaks the autopkgt
On 24/10/2022 21:55, Christopher Obbard wrote:
I'm more leaning on just adding it as a direct Dependency to the Debos
package and seeing if anyone moans...
Works for me.
On Mon, 2022-10-24 at 20:00 +0700, Arnaud Rebillout wrote:
>
> On 24/10/2022 17:34, Christopher Obbard wrote:
>
> > I have proposed[1] to check if systemd-resolved is available at
> > runtime, to at least let users know *why* name resolution doesn't
> > work
> > inside their fakemachine over let
On 24/10/2022 17:34, Christopher Obbard wrote:
I have proposed[1] to check if systemd-resolved is available at
runtime, to at least let users know *why* name resolution doesn't work
inside their fakemachine over letting the user debugging it themselves.
[1]:https://github.com/go-debos/fakemachin
On Thu, 2022-10-06 at 10:11 +0700, Arnaud Rebillout wrote:
>
> On 05/10/2022 22:06, Michael Biebl wrote:
> > I think if you want to assemble a root/usr fs where you don't want
> > do
> > "disturb" the host system, I'd use a debootstrapped chroot but not
> > the
> > host fs.
>
> I think the orig
On 05/10/2022 22:06, Michael Biebl wrote:
I think if you want to assemble a root/usr fs where you don't want do
"disturb" the host system, I'd use a debootstrapped chroot but not the
host fs.
I think the original reason for fakemachine to exist was to build OS
images from within containers.
Hi,
> > So far, the package fakemachine Depends on systemd, and that was enough.
> > Now with the split, and since we need systemd-resolved, we should make
> > fakemachine Depend on systemd-resolved as well. However, and if I
> > understand properly, installing systemd-resolved also *enables* i
On Wed, 5 Oct 2022 at 17:06, Michael Biebl wrote:
>
> Am 05.10.22 um 16:08 schrieb Arnaud Rebillout:
> > On 05/10/2022 16:58, Christopher Obbard wrote:
> >> Hi Arnaud,
> >>
> >> Thanks for shedding the extra light. This is not a nice bug !
> >>
> >> I think we should ask the systemd maintainer if
Am 05.10.22 um 16:08 schrieb Arnaud Rebillout:
On 05/10/2022 16:58, Christopher Obbard wrote:
Hi Arnaud,
Thanks for shedding the extra light. This is not a nice bug !
I think we should ask the systemd maintainer if they'd accept a patch
to make the enabling of systemd-resolved service a manual
On 05/10/2022 16:58, Christopher Obbard wrote:
Hi Arnaud,
Thanks for shedding the extra light. This is not a nice bug !
I think we should ask the systemd maintainer if they'd accept a patch
to make the enabling of systemd-resolved service a manual operation, or
at least to split the binary into
merge 1020288 1020691
On Wed, 2022-10-05 at 14:36 +0700, Arnaud Rebillout wrote:
>
> > On Sun, 25 Sep 2022 12:28:19 +0100 Christopher Obbard
> > wrote:
> > > Because of this, on a machine which does not have
> > > systemd-resolved installed, debos no longer works as
> > > intended.
> > >
>
> On Sun, 25 Sep 2022 12:28:19 +0100 Christopher Obbard
> wrote:
> > Because of this, on a machine which does not have
> > systemd-resolved installed, debos no longer works as
> > intended.
> >
> > Please add systemd-resolved as a runtime dependency to debos.
>
> It will fix debos but might bre
Hello Christopher!
On Sun, 25 Sep 2022 12:28:19 +0100 Christopher Obbard
wrote:
> Because of this, on a machine which does not have systemd-resolved
installed,
> debos no longer works as intended.
>
> Please add systemd-resolved as a runtime dependency to debos.
It will fix debos but might b
Package: debos
Version: 1.0.0+git20210707.c66a48d-2+b2
Severity: important
Dear Maintainer,
The latest systemd packages do not include systemd-resolved; it was split out
into a seperate package.
Because of this, on a machine which does not have systemd-resolved installed,
debos no longer works a
14 matches
Mail list logo
