On Sun, 2019-12-08 at 15:55:45 -0800, Russ Allbery wrote:
> Guillem Jover writes:
> > But here you do have another option, but I'm not sure it might be
> > described as nicer TBH, :) something like this, or variations on this
> > theme:
>
> > [Service]
> > Type=simple
> >
Guillem Jover writes:
> But here you do have another option, but I'm not sure it might be
> described as nicer TBH, :) something like this, or variations on this
> theme:
> [Service]
> Type=simple
> EnvironmentFile=/etc/default/service-static-vars
>
On Sun, 2019-12-08 at 11:15:57 -0800, Russ Allbery wrote:
> > Sure, help fir that would be nice. Thanks for the offer. (Probably
> > should have an own bug for that.) Nethertheless, this is the line that
> > causes my problems and needs to be transferred:
> >
Tobias Frost writes:
> Am Samstag, den 07.12.2019, 17:12 -0800 schrieb Russ Allbery:
>> A Policy should means that if there is some stronger reason (such as
>> that adding a unit file would introduce new bugs), there is nothing
>> requiring you to do so. It indicates that not having a unit file
Hi,
On 08.12.19 09:54, Tobias Frost wrote:
> Well, I was responding to a mail that suggested to make unit files
> mandatory (which I read as then RC-buggy) and suggesting some lines
> later to drop support for the sysv-generator and in this case it is
> quite moot that policy can be ignored
On Sun, Dec 08, 2019 at 12:59:25PM -0400, David Bremner wrote:
> Bill Allombert writes:
> > In any case, this is an upstream choice, not a packaging choice, so we
> > have to use what upstream provide.
>
> Just to be clear using /etc/default is not an upstream choice, it's a
> Debian convention.
Bill Allombert writes:
>
> In any case, this is an upstream choice, not a packaging choice, so we
> have to use what upstream provide.
>
Just to be clear using /etc/default is not an upstream choice, it's a
Debian convention. I know you probably didn't mean to imply that, but
that's how it read
On Sun, Dec 08, 2019 at 02:25:41PM +0100, Bill Allombert wrote:
> > > Sure, help fir that would be nice. Thanks for the offer.
> > > (Probably should have an own bug for that.) Nethertheless, this is the
> > > line that causes my problems and needs to be transferred:
> > >
On Sun, Dec 08, 2019 at 03:02:10PM +0500, Andrey Rahmatullin wrote:
> On Sun, Dec 08, 2019 at 09:54:23AM +0100, Tobias Frost wrote:
> > Sure, help fir that would be nice. Thanks for the offer.
> > (Probably should have an own bug for that.) Nethertheless, this is the
> > line that causes my
On Sat, Dec 07, 2019 at 05:12:14PM -0800, Russ Allbery wrote:
> That said, if you'd like help with this, I or someone else following this
> thread may be willing to take a look and figure out a way to replicate the
> init script behavior. It's normally possible to handle /etc/default
> conffiles
On Sun, Dec 08, 2019 at 09:54:23AM +0100, Tobias Frost wrote:
> Sure, help fir that would be nice. Thanks for the offer.
> (Probably should have an own bug for that.) Nethertheless, this is the
> line that causes my problems and needs to be transferred:
>
Am Samstag, den 07.12.2019, 17:12 -0800 schrieb Russ Allbery:
> Tobias Frost writes:
>
> > JFTR, I maintain gmedia-resurrect and in this package I failed
> > despite
> > trying to create a systemd unit file with equal functinality as the
> > init.d script*. So for this package the proposoal
Tobias Frost writes:
> JFTR, I maintain gmedia-resurrect and in this package I failed despite
> trying to create a systemd unit file with equal functinality as the
> init.d script*. So for this package the proposoal would lead to
> regressions for the users.
A Policy should means that if there
On Wed, Dec 04, 2019 at 07:03:09PM +0100, Simon Richter wrote:
> Hi,
>
> chiming in as I've been pointed to this bug: I agree with Ansgar in that
> adding unit files does not hurt sysvinit support in the least, provided we
> still get to ignore them.
>
> I'd even be in favour of making them
Hi,
chiming in as I've been pointed to this bug: I agree with Ansgar in that
adding unit files does not hurt sysvinit support in the least, provided we
still get to ignore them.
I'd even be in favour of making them mandatory (i.e. upgrading the lintian
warning to an error), and I don't see how
15 matches
Mail list logo
