On 13 September 2017 at 05:50, Alexandre Detiste
wrote:
> Hi,
>
> Please also sprinkle these maintainers scripts with some
>
> rmdir /etc/init --ignore-fail-on-non-empty
>
> to avoid ending up with a stale, unowned, empty /etc/init.
> (ad: the "cruft" tool found out about this)
>
I think this
]] Simon McVittie
> On Thu, 05 Oct 2017 at 21:43:20 +0200, Tollef Fog Heen wrote:
> > However, if you just do the IMO more common sudo $command, you get a lot
> > more:
> >
> > $ sudo env | wc -l
> > 87
>
> Is that under default configuration? My /etc/sudoers{,.d/*} don't mention
> env_reset, a
Hi!
On Tue, 2017-09-26 at 21:03:00 +0200, Ansgar Burchardt wrote:
> While it doesn't hurt here, I think people are on their own if they set
> POSIX_CORRECTLY or so (or include another incompatible `rmdir` in
> $PATH).
> Arguably `dpkg` could also run maintainer scripts in a more controlled
> envi
On Thu, 05 Oct 2017 at 21:43:20 +0200, Tollef Fog Heen wrote:
> However, if you just do the IMO more common sudo $command, you get a lot
> more:
>
> $ sudo env | wc -l
> 87
Is that under default configuration? My /etc/sudoers{,.d/*} don't mention
env_reset, and "sudo env" clears most of the envir
]] Ian Jackson
> However, I think that such arrangements are already made. The
> majority of people use "sudo", which AIUI already launders the
> environment.
That depends.
If you do sudo -i you get a mostly clean env:
$ sudo -i env
LANG=nb_NO.UTF-8
TZ=CET
SUDO_GID=1000
DISPLAY=:0
HOSTNAME=xo
Michael Stone writes ("Re: Removal of upstart integration"):
> On Thu, Oct 05, 2017 at 06:08:15PM +0100, Colin Watson wrote:
> >The frontend is often started via the confmodule sourced by a maintainer
> >script (and then the maintscript re-execed under the frontend), so f
On Thu, Oct 05, 2017 at 06:08:15PM +0100, Colin Watson wrote:
On Tue, Sep 26, 2017 at 09:13:46PM +0200, Christian Seiler wrote:
On 09/26/2017 09:03 PM, Ansgar Burchardt wrote:
> Arguably `dpkg` could also run maintainer scripts in a more controlled
> environment so less random variables affect t
On Tue, Sep 26, 2017 at 09:13:46PM +0200, Christian Seiler wrote:
> On 09/26/2017 09:03 PM, Ansgar Burchardt wrote:
> > Arguably `dpkg` could also run maintainer scripts in a more controlled
> > environment so less random variables affect the maintainer scripts.
>
> Full ACK. IMHO it should be spe
On Tue, Sep 26, 2017 at 09:23:50PM +0200, Paul Gevers wrote:
> Hi,
>
> On 26-09-17 21:13, Christian Seiler wrote:
> > Maybe there are cases for others, but I don't think the list
> > should be much longer than that.
>
> Not sure about other helpers or scripts, but dbconfig-common and debconf
> ha
Hi,
On 26-09-17 21:13, Christian Seiler wrote:
> Maybe there are cases for others, but I don't think the list
> should be much longer than that.
Not sure about other helpers or scripts, but dbconfig-common and debconf
have debug variables:
dbc_debug and DEBCONF_DEBUG
Paul
signature.asc
Descri
On 09/26/2017 09:03 PM, Ansgar Burchardt wrote:
> Arguably `dpkg` could also run maintainer scripts in a more controlled
> environment so less random variables affect the maintainer scripts.
Full ACK. IMHO it should be specified which environment
variables are passed to the maintainer scripts from
Ian Jackson writes:
> Alexandre Detiste writes ("Re: Removal of upstart integration"):
>> Please also sprinkle these maintainers scripts with some
>>
>> rmdir /etc/init --ignore-fail-on-non-empty
>
> That should be
>
> rmdir --ignore-fail-on-non
On 09/24/2017 01:32 AM, Thomas Goirand wrote:
> On 09/13/2017 02:56 PM, Ian Jackson wrote:
>> Alexandre Detiste writes ("Re: Removal of upstart integration"):
>>> Please also sprinkle these maintainers scripts with some
>>>
>>> rmdir /etc/init -
On 09/13/2017 02:56 PM, Ian Jackson wrote:
> Alexandre Detiste writes ("Re: Removal of upstart integration"):
>> Please also sprinkle these maintainers scripts with some
>>
>> rmdir /etc/init --ignore-fail-on-non-empty
>
> That should be
>
>
On 13 September 2017 at 13:56, Ian Jackson
wrote:
> Alexandre Detiste writes ("Re: Removal of upstart integration"):
>> Please also sprinkle these maintainers scripts with some
>>
>> rmdir /etc/init --ignore-fail-on-non-empty
>
> That should be
>
>
Alexandre Detiste writes ("Re: Removal of upstart integration"):
> Please also sprinkle these maintainers scripts with some
>
> rmdir /etc/init --ignore-fail-on-non-empty
That should be
rmdir --ignore-fail-on-non-empty /etc/init
in case an environment variabl
Hi,
Please also sprinkle these maintainers scripts with some
rmdir /etc/init --ignore-fail-on-non-empty
to avoid ending up with a stale, unowned, empty /etc/init.
(ad: the "cruft" tool found out about this)
--- /var/spool/cruft/report_20170907.log2017-09-07
06:18:45.571974263 +0200
On Wed, 2017-08-30 at 15:58 +0200, Luca Falavigna wrote:
> 2017-08-30 15:54 GMT+02:00 Dimitri John Ledkov :
> > I hope that this email alone is enough for at least some maintainers
> > to integrate/schedule this change without the bug overhead
>
> I think this could be a good candidates for a lint
On Wed, Aug 30, 2017 at 06:58:51PM +0500, Andrey Rahmatullin wrote:
> > I hope that this email alone is enough for at least some maintainers
> > to integrate/schedule this change without the bug overhead, as this is
> > low priority.
> Can you please publish a dd-list?
Actually I should just scrol
On Wed, Aug 30, 2017 at 02:54:59PM +0100, Dimitri John Ledkov wrote:
> I hope that this email alone is enough for at least some maintainers
> to integrate/schedule this change without the bug overhead, as this is
> low priority.
Can you please publish a dd-list?
--
WBR, wRAR
signature.asc
Desc
2017-08-30 15:54 GMT+02:00 Dimitri John Ledkov :
> I hope that this email alone is enough for at least some maintainers
> to integrate/schedule this change without the bug overhead
I think this could be a good candidates for a lintian tag to inform
maintainers about the change and to keep track of
On 30 August 2017 at 14:44, Holger Levsen wrote:
> On Wed, Aug 30, 2017 at 02:39:16PM +0100, Dimitri John Ledkov wrote:
>> upstart - event-based init daemon has been removed from debian and is
>> currently only present in oldstable.
>>
>> Many packages however still ship upstart integration. Pleas
On Wed, Aug 30, 2017 at 02:39:16PM +0100, Dimitri John Ledkov wrote:
> upstart - event-based init daemon has been removed from debian and is
> currently only present in oldstable.
>
> Many packages however still ship upstart integration. Please consider
> removing /etc/init/* conffiles from your p
upstart - event-based init daemon has been removed from debian and is
currently only present in oldstable.
Many packages however still ship upstart integration. Please consider
removing /etc/init/* conffiles from your packages. Do note, that
typically this will require a debian/pkg.maintscript sni
24 matches
Mail list logo
