Hello,
systemd is a replacement for the standard init command, which normally
runs as process id 1 on initialisation of a UNIX bootup. There has been
a movement, especially around the Red Hat-related developers to copy
Microsoft Windows and all of its features. Now this interpretation of
how
free...@tango.lu writes:
> If Debian drops sysVinit support I will drop Debian
[...]
> This is your last chance to do the right thing and announce the
> removal of this fucking piece of shit malware(D) from Debian and go
> back to sysVinit or openrc!
So dropping sysvinit support will make you go a
On 17.10.2018 06:52, Russ Allbery wrote:
> I think a package of a daemon that does not inherently require any
> systemd-specific features and would work straightforwardly with sysvinit,
> but has only a systemd unit file and no init script, is not only buggy but
> RC-buggy. That's what Policy curr
On Wed, Oct 17, 2018 at 10:19:31AM +0200, Ansgar Burchardt wrote:
So dropping sysvinit support will make you go away? That sounds like a
positive effect to me, but for some reason you seem to try and use it as
a threat?
Please don't feed the trolls. I enjoy mail from you, and it's a shame
when
Package: wnpp
Severity: wishlist
Owner: Andreas Tille
* Package name: r-cran-plumber
Version : 0.4.6
Upstream Author : Trestle Technology, LLC,
* URL : https://cran.r-project.org/package=plumber
* License : MIT
Programming Lang: GNU R
Description : API
Hi,
> Is it possible to support these versions properly for our
> users as long as there is security/LTS support for our releases?
the PHP 7.0 will be supported like any other package in Debian - the security
fixes will be cherrypicked and applied for the lifetime of Debian stretch. Then
the L
On Wed, Oct 17, 2018 at 11:04:00AM +0200, OndÅ?ej Surý wrote:
> > I know that there is
> > https://deb.sury.org - but prefer to trust stuff that was
> > built on Debian machines and is distributed/signed with a
> > key we trust.
> Shrug, all the packages that I upload to Debian and to the DPA are
On Oct 17, Holger Levsen wrote:
> yes, but when using your repo one has to add your key to the keys apt
> trusts, and this is something completly different than using proper
> backports.
Well... I trust much more Ondrej's archive since over the years it has
proven its quality and scope, while ne
* Kamil Jońca [181017 01:27]:
>
> Recently I tried to upgrade my freeradius package to 3.0.16+dfsg-4.1+b1
> And after that my laptop with wpa_supplicant stops authenticate:
>
> with version 3.0.16+dfsg-3+b1 everything works ok.
> Any hints what to check in logs?
Please ask user questions on deb
On 16.10.2018 15:40, Xavier wrote:
Hello,
you must install upstream key in debian/upstream/signing-key.asc: uscan
should verify key with its own keystore, not yours.
Cheers,
Xavier
I have installed the key to both debian/upstream/signing-key.pgp and
debian/upstream/signing-key.asc. It stil
Hi,
On 18-10-17 15:11:00, Tommi Höynälänmaa wrote:
> I have installed the key to both debian/upstream/signing-key.pgp and
> debian/upstream/signing-key.asc. It still doesn't work.
Run uscan with increased verbosity (-v), it might give you a hint what
is going wrong.
Cheers,
Georg
signature.asc
Package: wnpp
Severity: wishlist
X-Debbugs-CC: debian-devel@lists.debian.org
--- Please fill out the fields below. ---
Package name: multiblend
Version: 0.6.2
Upstream Author: David Horman
URL: http://horman.net/multiblend/
License: GPL-2+
Description:
*multiblend* is a multi-level image bl
Am 17.10.18 um 12:00 schrieb Marco d'Itri:
> On Oct 17, Holger Levsen wrote:
>
>> yes, but when using your repo one has to add your key to the keys apt
>> trusts, and this is something completly different than using proper
>> backports.
> Well... I trust much more Ondrej's archive since over the
(previously sent to debian-devel by mistake)
Recently I tried to upgrade my freeradius package to 3.0.16+dfsg-4.1+b1
And after that my laptop with wpa_supplicant stops authenticate:
excerpt from wpa_supplicant
network={
ssid=<<...>
proto=RSN
key_mgmt=WPA-EAP
pa
On Wed, Oct 17, 2018 at 04:04:15PM +0200, Kamil Jońca wrote:
> (previously sent to debian-devel by mistake)
You've repeated that mistake.
--
WBR, wRAR
signature.asc
Description: PGP signature
Package: wnpp
Severity: wishlist
Owner: Talat Batheesh
* Package name: sockperf
Version : 3.5.0
Upstream Author : Liran Oz
* URL : https://github.com/Mellanox/sockperf
* License : BSD
Programming Lang: C, C++
Description : Network benchmarking utility
Package: wnpp
Severity: wishlist
Owner: Talat Batheesh
* Package name: libvma
Version : 8.7.1
Upstream Author : Liran Oz
* URL : https://github.com/Mellanox/libvma
* License : GPLv2 and BSD
Programming Lang: C, C++
Description : libvma is a LD_PRELOAD-
Philipp Kern writes:
> On 17.10.2018 06:52, Russ Allbery wrote:
>> I think a package of a daemon that does not inherently require any
>> systemd-specific features and would work straightforwardly with
>> sysvinit, but has only a systemd unit file and no init script, is not
>> only buggy but RC-bu
On Thu, Oct 18, 2018 at 5:24 AM Russ Allbery wrote:
> Timer units are also a more complicated problem since they're not a
> superset of cron behavior. They do some things better than cron jobs;
> they do other things much *worse* than cron jobs. I have cron jobs that I
> wanted to convert to tim
Paul Wise writes:
> On Thu, Oct 18, 2018 at 5:24 AM Russ Allbery wrote:
>> Timer units are also a more complicated problem since they're not a
>> superset of cron behavior. They do some things better than cron jobs;
>> they do other things much *worse* than cron jobs. I have cron jobs
>> that I
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 weren't aware of it.
Define a ser
21 matches
Mail list logo
