Nikolaus Rath writes:
> On Aug 28 2016, Bart Schouten wrote:
>> But that's not the relevance. The idea that systemd is clearly superior
>> to sysvinit is just something you concoct up because you don't know how
>> to write a service file or script and you want to let systemd do the
>> hard work.
On Aug 28 2016, Bart Schouten wrote:
> But that's not the relevance. The idea that systemd is clearly
> superior to sysvinit is just something you concoct up because you
> don't know how to write a service file or script and you want to let
> systemd do the hard work.
How is that concoted? Yes, s
On Tue, Aug 30, 2016 at 1:56 AM, Niels Thykier wrote:
> Frankly, I do not think that the source package is the correct place for
> the Maintainer / Uploaders data. There are plenty of cases where it
> would make sense to update it "retroactively" after the package has been
> uploaded (E.g. orphan
Hi,
On 28.08.2016 14:29, Jonathan de Boyne Pollard wrote:
> especially in light of the fact
> that the systemd developers have had a list of "Oddball things that you
> can actually do with rc scripts that systemd isn't going to support."
The crux of the matter is that what the majority thinks of
Dmitry Bogatov writes:
> Socket is not bad thing. Inventing daemon for no reason is complicating
> things for no reason => bad. Thanks history, we have pid files, not
> `libpid' to talk to `pidd'.
Uh, the daemon in question is the init daemon? Which has been there since
the beginning of UNIX?
> > I can understand this need, although never needed it myself.
>
> > But implementation makes me sad. Instead of creating UNIX-way solution
> > (create /var/run/foo.ready, when you are ready?), it does the worst
> > thing I can imagine.
>
> If communicating with another local daemon via a UNIX d
Package: wnpp
Owner: Hilko Bengen
Severity: wishlist
* Package name: libscca
Version : 20160108
Upstream Author : Joachim Metz
* URL or Web page : https://github.com/libyal/libscca
* License : LGPL-3.0+
Description : library to access the Windows Prefetch File (SCCA)
Package: wnpp
Owner: Hilko Bengen
Severity: wishlist
* Package name: dfwinreg
Version : 20160428
Upstream Author : The dfWinReg development team
* URL or Web page : https://github.com/log2timeline/dfwinreg
* License : Apache 2.0
Description : Digital Forensics Window
Hi,
On 28.08.2016 22:11, Bart Schouten wrote:
> That "very serious race condition" is nothing more than one daemon
> having to wait for the other while starting up. THAT'S IT. Oh and
> knowing when something has died so you can restart it or something.
That is also something the init system can
Ian Jackson:
> Holger Levsen writes ("Re: removal instead of orphaning?"):
>> Maybe a solution would be a third kind of maintainer/uploader, so
>> people could indicate that they are happy to do house-cleaning work on
>> this package, even though they are not apt to maintain it properly.
>>
>>
Vincent Bernat writes:
> ❦ 29 août 2016 05:00 CEST, Russ Allbery :
>> upstart supports a similar mechanism via the -Z flag, but it's (IMO) a
>> little less clean: the process sends itself a SIGSTOP when it's ready,
>> and then lets the init system send it a SIGCONT. This does work, but I
>> do
Jonathan de Boyne Pollard
writes:
> Russ Allbery:
>> All other init systems except upstart [...]
> Psst!
> * https://jdebp.eu./FGA/unix-daemon-readiness-protocol-problems.html#Choice
I think that... says the same thing I said? At least the only ones I see
there are systemd and a proposal for
Dmitry Bogatov writes:
> I can understand this need, although never needed it myself.
> But implementation makes me sad. Instead of creating UNIX-way solution
> (create /var/run/foo.ready, when you are ready?), it does the worst
> thing I can imagine.
If communicating with another local daemon
Ian Jackson wrote:
> Jay Berkenbilt writes ("orphaning psutils"):
>> retitle 777699 O: psutils -- PostScript document handling utilities
>> thanks
>>
>> I'm going to go ahead and orphan these. The RFA has been open for a long
>> time, and the package has not been adopted yet. I didn't actually no
The fun thing is that if the original poster had just shipped an
half-broken script nobody would have ever noticed, and in a couple of
years it would have been another data point about the irrelevance of
sysvinit nowadays.
As long as the package builds, don't bother... :-)
--
ciao,
Marco
si
In https://lists.debian.org/debian-devel/2016/08/msg00554.html, Simon
McVittie:
Please contact the D-Bus upstream mailing list if you are interested
in implementing a user bus without systemd. You will need something
resembling pam_xdg_support (which is what Ubuntu used before they
switched t
"Adam D. Barratt" writes:
> No. Policy is not a user-focused tool, it's the documentation of how
> developers / maintainers are expected to build packages. It documents
> how things are and the current conventions, not how they will or might
> be at some hypothetical point in the future.
Okay, i
Package: wnpp
Severity: wishlist
Owner: Andreas Tille
* Package name: pirs
Version : 2.0.2
Upstream Author : BGI
* URL : https://github.com/galaxy001/pirs
* License : BSD
Programming Lang: C++
Description : Profile based Illumina pair-end Reads Simulat
Jay Berkenbilt writes ("orphaning psutils"):
> retitle 777699 O: psutils -- PostScript document handling utilities
> thanks
>
> I'm going to go ahead and orphan these. The RFA has been open for a long
> time, and the package has not been adopted yet. I didn't actually notice
> that someone else ha
Holger Levsen writes ("Re: removal instead of orphaning?"):
> Maybe a solution would be a third kind of maintainer/uploader, so
> people could indicate that they are happy to do house-cleaning work on
> this package, even though they are not apt to maintain it properly.
>
> Maintainers: debian
On Mon, 2016-08-29 at 13:12 +0300, Dmitrii Kashin wrote:
> Don Armstrong writes:
[...]
> > Policy is not a tool to beat developers with; it's a method of
> > documenting convention so that we can build a distribution of packages
> > which interact. Like most documentation of convention, it tends t
Didier 'OdyX' Raboud writes:
> Le lundi, 29 août 2016, 12.07:23 h CEST Dmitrii Kashin a écrit :
>> But I know a lot of them. And not only in Debian community. And they
>> don't agree that migrating will give them greater control over their
>> systems.
>
> This is not a popularity contest, in whic
Package: wnpp
Owner: intrigeri
Severity: wishlist
X-Debbugs-CC: debian-devel@lists.debian.org, debian-p...@lists.debian.org
* Package name: libgtk3-simplelist-perl
Version : 0.15
Upstream Author : Thierry Vignaud
* URL : https://metacpan.org/release/Gtk3-SimpleList
*
Le lundi, 29 août 2016, 12.07:23 h CEST Dmitrii Kashin a écrit :
> But I know a lot of them. And not only in Debian community. And they
> don't agree that migrating will give them greater control over their
> systems.
This is not a popularity contest, in which we'd count points either way. We,
as
Don Armstrong writes:
> On Mon, 29 Aug 2016, Dmitrii Kashin wrote:
>> If we assume that this precedent allow a maintainer to violate policy,
>> so we don't need the Policy anymore.
>
> Violating policy is still a bug; it may be a bug in policy, or a bug in
> the package.
>
>> they still continue
On Mon, 29 Aug 2016, Dmitrii Kashin wrote:
> If we assume that this precedent allow a maintainer to violate policy,
> so we don't need the Policy anymore.
Violating policy is still a bug; it may be a bug in policy, or a bug in
the package.
> they still continue to rely on Policy to be sure that s
But I know a lot of them. And not only in Debian community. And they
don't agree that migrating will give them greater control over their
systems.
If you want I'll ask them to write here too.
Attila Kinali writes:
> On Thu, 25 Aug 2016 19:47:55 -0400
> Robert Edmonds wrote:
>
>> I would guess
Philipp Kern writes:
> On 2016-08-26 19:53, Wookey wrote:
>> After Stretch there may not be that many sysvinit users, but I think
>> that 2 releases is the minimum sensible period to maintain support for
>> such a siginificant change.
>
> But it seems that this discussion does not consider if sys
[2016-08-28 20:00] Russ Allbery
>
> part text/plain3207
> Dmitry Bogatov writes:
>
> > Not to start flame or to advertize anything/anyone, but why to integrate
> > with 'runit' init system, your program should support foreground
> > operation and logging on stdout, and to in
29 matches
Mail list logo
