Re: finish retirement of sysvinit-only packages Re: Schedule for Friday's FESCo Meeting (2016-07-29)

2016-08-02 Thread Jóhann B . Guðmundsson
On 07/31/2016 06:29 AM, Parag Nemade wrote: Kevin has already given a detailed information how longer it took to retire these packages. Also see this https://fedoramagazine.org/systemd-converting-sysvinit-scripts/ Take that article with a grain of salt since it's written by somebody that has

Re: finish retirement of sysvinit-only packages Re: Schedule for Friday's FESCo Meeting (2016-07-29)

2016-08-02 Thread Simo Sorce
On Tue, 2016-08-02 at 09:11 +, Jóhann B. Guðmundsson wrote: > On 07/31/2016 06:29 AM, Parag Nemade wrote: > > > Kevin has already given a detailed information how longer it took to > > retire these packages. Also see this > > https://fedoramagazine.org/systemd-converting-sysvinit-scripts/ > >

Re: finish retirement of sysvinit-only packages Re: Schedule for Friday's FESCo Meeting (2016-07-29)

2016-08-02 Thread Jóhann B . Guðmundsson
On 07/31/2016 03:18 AM, Sérgio Basto wrote: why such hurry ? There has been a more than enough time for this migration to happen already and now it's existence has started to hinder other changes and adoptions in the distribution. The initial target was for the feature completion was F20 o

Re: finish retirement of sysvinit-only packages Re: Schedule for Friday's FESCo Meeting (2016-07-29)

2016-08-02 Thread Jóhann B . Guðmundsson
On 08/02/2016 09:24 AM, Simo Sorce wrote: On Tue, 2016-08-02 at 09:11 +, Jóhann B. Guðmundsson wrote: On 07/31/2016 06:29 AM, Parag Nemade wrote: Kevin has already given a detailed information how longer it took to retire these packages. Also see this https://fedoramagazine.org/systemd-c

Re: finish retirement of sysvinit-only packages Re: Schedule for Friday's FESCo Meeting (2016-07-29)

2016-08-02 Thread Jóhann B . Guðmundsson
On 08/02/2016 12:25 AM, Nico Kadel-Garcia wrote: It's a burden, usually solved by ignoring one or the other. Since systemd is always incompatible and always will be incompatible with anything but relatively modern Linux distrubitutions, guess which packages never get ported to non-Linux systems.

Re: finish retirement of sysvinit-only packages Re: Schedule for Friday's FESCo Meeting (2016-07-29)

2016-08-02 Thread Simo Sorce
On Tue, 2016-08-02 at 10:09 +, Jóhann B. Guðmundsson wrote: > > On 08/02/2016 09:24 AM, Simo Sorce wrote: > > On Tue, 2016-08-02 at 09:11 +, Jóhann B. Guðmundsson wrote: > >> On 07/31/2016 06:29 AM, Parag Nemade wrote: > >> > >>> Kevin has already given a detailed information how longer it

Re: finish retirement of sysvinit-only packages Re: Schedule for Friday's FESCo Meeting (2016-07-29)

2016-08-02 Thread Jóhann B . Guðmundsson
On 08/02/2016 10:23 AM, Simo Sorce wrote: I do not actually have to prove anything, in a welcoming community you give the beneit of the doubt that people researched and know what they are talking about and you stick to actual fact in whatever they produce, not to some badge of credentials that

Re: finish retirement of sysvinit-only packages Re: Schedule for Friday's FESCo Meeting (2016-07-29)

2016-08-02 Thread Simo Sorce
On Tue, 2016-08-02 at 10:37 +, Jóhann B. Guðmundsson wrote: > > On 08/02/2016 10:23 AM, Simo Sorce wrote: > > > > I do not actually have to prove anything, in a welcoming community you > > give the beneit of the doubt that people researched and know what they > > are talking about and you stic

Fedora 25-20160802.n.0 compose check report

2016-08-02 Thread Fedora compose checker
Missing expected images: Workstation live i386 Cloud_base raw-xz x86_64 Xfce raw-xz armhfp Cloud_base raw-xz i386 Atomic raw-xz x86_64 Minimal raw-xz armhfp Workstation live x86_64 Failed openQA tests: 61/79 (x86_64), 14/16 (i386) ID: 26954 Test: x86_64 Everything-boot-iso install_default@

Fedora Rawhide-20160802.n.0 compose check report

2016-08-02 Thread Fedora compose checker
Missing expected images: Kde live i386 Workstation live i386 Kde live x86_64 Cloud_base raw-xz x86_64 Cloud_base raw-xz i386 Atomic raw-xz x86_64 Kde raw-xz armhfp Minimal raw-xz armhfp Workstation live x86_64 Failed openQA tests: 58/74 (x86_64), 13/15 (i386) ID: 26865 Test: x86_64 Everyth

Re: finish retirement of sysvinit-only packages Re: Schedule for Friday's FESCo Meeting (2016-07-29)

2016-08-02 Thread Nico Kadel-Garcia
On Tue, Aug 2, 2016 at 6:15 AM, Jóhann B. Guðmundsson wrote: > On 08/02/2016 12:25 AM, Nico Kadel-Garcia wrote: > >> It's a burden, usually solved by ignoring one or the other. Since >> systemd is always incompatible and always will be incompatible with >> anything but relatively modern Linux dist

Re: finish retirement of sysvinit-only packages Re: Schedule for Friday's FESCo Meeting (2016-07-29)

2016-08-02 Thread Nico Kadel-Garcia
On Wed, Aug 3, 2016 at 12:11 AM, Nico Kadel-Garcia wrote: > On Tue, Aug 2, 2016 at 6:15 AM, Jóhann B. Guðmundsson > wrote: >> On 08/02/2016 12:25 AM, Nico Kadel-Garcia wrote: >> >>> It's a burden, usually solved by ignoring one or the other. Since >>> systemd is always incompatible and always wil

Re: finish retirement of sysvinit-only packages Re: Schedule for Friday's FESCo Meeting (2016-07-29)

2016-08-02 Thread Sérgio Basto
On Qua, 2016-08-03 at 00:11 -0400, Nico Kadel-Garcia wrote: > On Tue, Aug 2, 2016 at 6:15 AM, Jóhann B. Guðmundsson > wrote: > > > > On 08/02/2016 12:25 AM, Nico Kadel-Garcia wrote: > > > > > > > > It's a burden, usually solved by ignoring one or the other. Since > > > systemd is always incompa

hfsplus-tools executables renamed

2016-08-02 Thread Mattia Verga
Hi, it seems that the hfsplus-tools package arbitrary renames its executables. This prevents kde-partitionmanager to fully support HFS+. I've opened a bug [1] for this, but I received no answer. Anyone knows why those executables are renamed? Thanks Mattia [1] https://bugzilla.redhat.com/sho

Re: hfsplus-tools executables renamed

2016-08-02 Thread Ville Skyttä
On Wed, Aug 3, 2016 at 9:00 AM, Mattia Verga wrote: > it seems that the hfsplus-tools package arbitrary renames its executables. > This prevents kde-partitionmanager to fully support HFS+. > I've opened a bug [1] for this, but I received no answer. > > Anyone knows why those executables are renam