Re: Debian Buster release to partially drop non-systemd support

Jonathan Dowland writes: > On Wed, Oct 17, 2018 at 08:33:47PM -0700, Russ Allbery wrote: >>MAILTO was the main thing that I remember missing in terms of pure >>functionality. > > This is not a complete substitute for all uses of MAILTO, but I found > the following useful so I share it in case you

Re: Debian Buster release to partially drop non-systemd support

On Thu, Oct 18, 2018 at 08:46:10AM +0200, Kamil Jońca wrote: But this not play well with exim4. See: https://lists.freedesktop.org/archives/systemd-devel/2018-September/041417.html (and thread as a whole) Thanks for passing that along: I'm using it with Exim and haven't noticed this particular

Re: Debian Buster release to partially drop non-systemd support

On Thu, Oct 18, 2018 at 08:46:10AM +0200, Kamil Jońca wrote: > > Put an OnFailure= line in systemd units that you want to mail you if > > they go wrong > > > >> [Unit] > >> OnFailure=status-email-user@%n.service > > But this not play well with exim4. > See: > https://lists.freedesktop.org/archives

Re: Debian Buster release to partially drop non-systemd support

On Thu, Oct 18, 2018 at 09:09:38AM +0100, Jonathan Dowland wrote: Thanks for passing that along: I'm using it with Exim and haven't noticed this particular problem, but it's useful to know it could happen. Ah, because I have User=nobody, and so the systemd sub-process can't reap the privileged

Re: Debian Buster release to partially drop non-systemd support

Adam Borowski writes: [..] > > Ouch. This is downright terrifying. It should be quite obvious why things > other than exim can break when called from there. > > And there's no good way for a random tool you may use to know it might get > suddenly SIGKILLed out of the blue. The only workaround

Re: Debian Buster release to partially drop non-systemd support

Jonathan Dowland writes: > On Thu, Oct 18, 2018 at 09:09:38AM +0100, Jonathan Dowland wrote: >>Thanks for passing that along: I'm using it with Exim and haven't >>noticed this particular problem, but it's useful to know it could >>happen. > > Ah, because I have User=nobody, and so the systemd sub

"debian.pool.ntp.org" for Debian derivatives?

Hello, our business model is to we sell support for our own Debian based distribution "Univention Corporate Server": I recently had a discussion about NTP and their pool concept per vendor:

Bug#911293: ITP: libre-engine-re2-perl -- RE2 regex engine

Package: wnpp Severity: wishlist Owner: Jonas Smedegaard -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 * Package name: libre-engine-re2-perl Version : 0.13 Upstream Author : David Leadbeater * URL : https://metacpan.org/release/re-engine-RE2 * License : Art

Re: OpenRC is there (was: Debian Buster release to partially drop non-systemd support)

On 10/13/18 12:58 PM, Holger Levsen wrote: > On Sat, Oct 13, 2018 at 06:01:43AM +0100, Ben Hutchings wrote: >>> Has policy changed regarding support for multiple inits, or is it just that >>> no one is maintaining the shim and sysvinit-core? >> >> The latter. systemd-shim has been orphaned for ove

Re: "debian.pool.ntp.org" for Debian derivatives?

Philipp Hahn writes (""debian.pool.ntp.org" for Debian derivatives?"): > Are we (as a Debian derivate) allowed to hard-code and use the > "debian.pool.ntp.org" or must we apply for our own pool? The NTP pool folks would like you to use your own pool. So would Debian, I'm pretty sure. > PS: Payin

Re: "debian.pool.ntp.org" for Debian derivatives?

On 10/18/2018 11:22 AM, Philipp Hahn wrote: > Are we (as a Debian derivate) allowed to hard-code and use the > "debian.pool.ntp.org" or must we apply for our own pool? the idea between the different pool CNAMEs is that when one vendor does something bad/wrong, the queries of devices running that v

Re: "debian.pool.ntp.org" for Debian derivatives?

Hello Ian et al., Am 18.10.18 um 12:40 schrieb Ian Jackson: > Philipp Hahn writes (""debian.pool.ntp.org" for Debian derivatives?"): >> Are we (as a Debian derivate) allowed to hard-code and use the >> "debian.pool.ntp.org" or must we apply for our own pool? > > The NTP pool folks would like you

Re: "debian.pool.ntp.org" for Debian derivatives?

On Thu, 2018-10-18 at 13:57 +0200, Philipp Hahn wrote: > So my question is more like "is it okay to not change Debians default > NTP server selection", so the initial setup and those lazy enough to > not change the default get a sane time? I don't think Debian can answer that question and suggest

Re: Debian Buster release to partially drop non-systemd support

On Thu, 18 Oct 2018 06:58:14 +0100, Jonathan Dowland wrote: > On Wed, Oct 17, 2018 at 08:33:47PM -0700, Russ Allbery wrote: >>MAILTO was the main thing that I remember missing in terms of pure >>functionality. > > This is not a complete substitute for all uses of MAILTO, but I found > the followi

Bug#911335: ITP: cpdb-libs -- Common Print Dialog Backends - Interface Library for Backends

Package: wnpp Severity: wishlist Owner: Till Kamppeter * Package name: cpdb-libs Version : 1.1.2 Upstream Author : Nilanjana Lodh * URL : https://github.com/OpenPrinting/cpdb-libs * License : MIT Programming Lang: C Description : Common Print Dialog Ba

Bug#911340: ITP: cpdb-backend-cups -- Common Print Dialog Backends - CUPS/IPP Backend

Package: wnpp Severity: wishlist Owner: Till Kamppeter * Package name: cpdb-backend-cups Version : 1.1.0 Upstream Author : Nilanjana Lodh * URL : https://github.com/OpenPrinting/cpdb-backend-cups * License : MIT Programming Lang: C Description : Common

Bug#911342: ITP: cpdb-backend-gcp -- Common Print Dialog Backends - Google Cloud Print Backend

Package: wnpp Severity: wishlist Owner: Till Kamppeter * Package name: cpdb-backend-gcp Version : 1.1.0 Upstream Author : Abhijeet Dubey * URL : https://github.com/OpenPrinting/cpdb-backend-gcp * License : MIT Programming Lang: C Description : Common P

Re: Debian Buster release to partially drop non-systemd support

On 10/13/18 12:58 PM, Holger Levsen wrote: > On Sat, Oct 13, 2018 at 06:01:43AM +0100, Ben Hutchings wrote: >>> Has policy changed regarding support for multiple inits, or is it just that >>> no one is maintaining the shim and sysvinit-core? >> >> The latter. systemd-shim has been orphaned for o

Bug#911345: ITP: cpdb-backend-file -- Common Print Dialog Backends - Print-to-File Backend

Package: wnpp Severity: wishlist Owner: Till Kamppeter * Package name: cpdb-backend-file Version : 1.0.1 Upstream Author : Ayush Bansal * URL : https://github.com/OpenPrinting/cpdb-backend-file * License : MIT Programming Lang: C Description : Common P

Re: "debian.pool.ntp.org" for Debian derivatives?

We are probably accepting their TOS without reading them first: https://www.ntppool.org/tos.html Yao Wei (This email is sent from a phone; sorry for HTML email if it happens.) > On Oct 18, 2018, at 20:51, Ansgar Burchardt wrote: > >> On Thu, 2018-10-18 at 13:57 +0200, Philipp Hahn wrote: >> S

Work-needing packages report for Oct 19, 2018

The following is a listing of packages for which help has been requested through the WNPP (Work-Needing and Prospective Packages) system in the last week. Total number of orphaned packages: 1323 (new: 6) Total number of packages offered up for adoption: 165 (new: 2) Total number of packages reques

Re: Debian Buster release to partially drop non-systemd support

__ I'm using this express-made address because personal addresses aren't masked enough at this mail public archive. Public archive administrator should fix this against automated addresses collectors. El 18/10/18 a les 22:07, Bernd Zeimetz ha escrit: > For my packages I can state that I do