Re: plan to update F27 to systemd-235 cancelled

2017-10-27 Thread James Hogarth
On 26 Oct 2017 22:37, "Zbigniew Jędrzejewski-Szmek" wrote: Hi, two weeks ago I signalled a plan to update systemd to v235 in F27. I have now given up on this. Reasons: there were some issues in the implementation of the DynamicUser feature. Handling this took some time and F27 entered the final

plan to update F27 to systemd-235 cancelled

2017-10-26 Thread Zbigniew Jędrzejewski-Szmek
Hi, two weeks ago I signalled a plan to update systemd to v235 in F27. I have now given up on this. Reasons: there were some issues in the implementation of the DynamicUser feature. Handling this took some time and F27 entered the final freeze, and it seems to late to do update the version now.

Re: Giving us the ability to go backwards [was Re: plan to update F27 to systemd-235]

2017-10-12 Thread nicolas . mailhot
- Mail original - De: "Pierre-Yves Chibon" >Ok, another random/crazy/likely stupid idea for the same outcome: the >possibility to go backwards in our packaging. >What if we inverted version and release? > So -2.1-1 become -1-2.1? Same problem than with epoch. Does not work with third-

Re: Giving us the ability to go backwards [was Re: plan to update F27 to systemd-235]

2017-10-12 Thread Pierre-Yves Chibon
On Sat, Oct 07, 2017 at 12:31:04PM -0400, Matthew Miller wrote: > On Sat, Oct 07, 2017 at 10:33:38AM -0400, Colin Walters wrote: > > I'm personally very in favor of this; of course my usual refrain > > here is that we should *try* new things and have the ability > > to back them out if they don't w

Re: plan to update F27 to systemd-235

2017-10-09 Thread Solomon Peachy
On Mon, Oct 09, 2017 at 04:38:07PM +0200, Reindl Harald wrote: > oh yeah, your mysqld tests surely include "and now me make the 800 > connections allowed in my.cnf"? i doubt! As an end-user testing my [organization's] applications on a new/beta distro release? This is something I'll absolutely t

Re: Giving us the ability to go backwards [was Re: plan to update F27 to systemd-235]

2017-10-09 Thread Colin Walters
On Sat, Oct 7, 2017, at 01:26 PM, Stephen John Smoogen wrote: > At a certain point, if you want/need to do these things, it is better > to burn it from the ground and come up with a new packaging system > (and relearn all the second system problems involved with that). I actually put code behind

Re: plan to update F27 to systemd-235

2017-10-09 Thread Solomon Peachy
On Mon, Oct 09, 2017 at 01:04:55PM +0200, Reindl Harald wrote: > maybe you did not understand that he is talking about "DefaultTasksMax=512" > which is systemd, affects all services and was *in the meantime* raised Surely this is one of the things a system administrator is expected to tune based

Re: plan to update F27 to systemd-235

2017-10-09 Thread James Hogarth
On 9 October 2017 at 11:30, Solomon Peachy wrote: > On Sat, Oct 07, 2017 at 10:17:31PM -0400, Nico Kadel-Garcia wrote: > > The killing of logged out user processes, without record and with > > no option to disable it after compilation in release 230 was another > > one. > > Oh, that's utter, unff

Re: plan to update F27 to systemd-235

2017-10-09 Thread Solomon Peachy
On Sat, Oct 07, 2017 at 10:17:31PM -0400, Nico Kadel-Garcia wrote: > The killing of logged out user processes, without record and with > no option to disable it after compilation in release 230 was another > one. Oh, that's utter, unffettered BS. That feature was there from the beginning. v230

Re: Giving us the ability to go backwards [was Re: plan to update F27 to systemd-235]

2017-10-09 Thread nicolas . mailhot
- Mail original - De: "Vít Ondruch" > This does not necessarily work in case when subpackages are using > different versions from main package. But if we always increased > release, it would not hurt ... OTOH, it would not solve the typical > issues with 1.0.0.rc1 updated to 1.0.0 T

Re: Giving us the ability to go backwards [was Re: plan to update F27 to systemd-235]

2017-10-09 Thread Vít Ondruch
Dne 7.10.2017 v 18:45 Neal Gompa napsal(a): > On Sat, Oct 7, 2017 at 12:31 PM, Matthew Miller > wrote: >> On Sat, Oct 07, 2017 at 10:33:38AM -0400, Colin Walters wrote: >>> I'm personally very in favor of this; of course my usual refrain >>> here is that we should *try* new things and have the a

Re: Giving us the ability to go backwards [was Re: plan to update F27 to systemd-235]

2017-10-08 Thread Nico Kadel-Garcia
On Sat, Oct 7, 2017 at 1:26 PM, Stephen John Smoogen wrote: > If there is one thing I have learned in 20 years of dealing with > RPMS... DON'T PLAY AROUND WITH EPOCH. It is a hack which should only > be used as a last resort and a lot of tools are built around that > assumption.. even if they don

Re: plan to update F27 to systemd-235

2017-10-08 Thread Neal Gompa
On Sun, Oct 8, 2017 at 8:19 AM, Zbigniew Jędrzejewski-Szmek wrote: > On Sat, Oct 07, 2017 at 10:33:38AM -0400, Colin Walters wrote: >> On Sat, Oct 7, 2017, at 08:14 AM, Zbigniew Jędrzejewski-Szmek wrote: >> >> > Well, my point is that in this case there aren't any big changes, only> >> > some rel

Re: plan to update F27 to systemd-235

2017-10-08 Thread Zbigniew Jędrzejewski-Szmek
On Sat, Oct 07, 2017 at 10:33:38AM -0400, Colin Walters wrote: > On Sat, Oct 7, 2017, at 08:14 AM, Zbigniew Jędrzejewski-Szmek wrote: > > > Well, my point is that in this case there aren't any big changes, only> > > some relatively minor feature additions. According to the policy, > > "minor" upg

Re: plan to update F27 to systemd-235

2017-10-08 Thread Zbigniew Jędrzejewski-Szmek
On Sat, Oct 07, 2017 at 10:17:31PM -0400, Nico Kadel-Garcia wrote: > On Fri, Oct 6, 2017 at 11:04 AM, Zbigniew Jędrzejewski-Szmek > wrote: > > Hi, > > > > systemd 235 was released today. A large number of issues was closed > > upstream, including many bug fixes, documentation updates, and > > long

Re: plan to update F27 to systemd-235

2017-10-08 Thread Zbigniew Jędrzejewski-Szmek
On Sat, Oct 07, 2017 at 12:17:15PM -0400, Neal Gompa wrote: > On Sat, Oct 7, 2017 at 12:02 PM, Richard W.M. Jones wrote: > > On Fri, Oct 06, 2017 at 03:04:12PM +, Zbigniew Jędrzejewski-Szmek wrote: > >> Hi, > >> > >> systemd 235 was released today. A large number of issues was closed > >> upst

Re: plan to update F27 to systemd-235

2017-10-07 Thread Nico Kadel-Garcia
On Fri, Oct 6, 2017 at 11:04 AM, Zbigniew Jędrzejewski-Szmek wrote: > Hi, > > systemd 235 was released today. A large number of issues was closed > upstream, including many bug fixes, documentation updates, and > long-standing RFEs. There are some new features, but relatively few > entirely new fe

Re: Giving us the ability to go backwards [was Re: plan to update F27 to systemd-235]

2017-10-07 Thread Stephen John Smoogen
On 7 October 2017 at 12:31, Matthew Miller wrote: > On Sat, Oct 07, 2017 at 10:33:38AM -0400, Colin Walters wrote: >> I'm personally very in favor of this; of course my usual refrain >> here is that we should *try* new things and have the ability >> to back them out if they don't work (the latter

Re: Giving us the ability to go backwards [was Re: plan to update F27 to systemd-235]

2017-10-07 Thread Neal Gompa
On Sat, Oct 7, 2017 at 1:10 PM, Pierre-Yves Chibon wrote: > On Sat, Oct 07, 2017 at 12:45:14PM -0400, Neal Gompa wrote: >> On Sat, Oct 7, 2017 at 12:31 PM, Matthew Miller >> wrote: >> > On Sat, Oct 07, 2017 at 10:33:38AM -0400, Colin Walters wrote: >> >> I'm personally very in favor of this; of c

Re: Giving us the ability to go backwards [was Re: plan to update F27 to systemd-235]

2017-10-07 Thread Pierre-Yves Chibon
On Sat, Oct 07, 2017 at 12:45:14PM -0400, Neal Gompa wrote: > On Sat, Oct 7, 2017 at 12:31 PM, Matthew Miller > wrote: > > On Sat, Oct 07, 2017 at 10:33:38AM -0400, Colin Walters wrote: > >> I'm personally very in favor of this; of course my usual refrain > >> here is that we should *try* new thin

Re: Giving us the ability to go backwards [was Re: plan to update F27 to systemd-235]

2017-10-07 Thread Neal Gompa
On Sat, Oct 7, 2017 at 12:47 PM, Igor Gnatenko wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA256 > > On Sat, 2017-10-07 at 12:31 -0400, Matthew Miller wrote: >> On Sat, Oct 07, 2017 at 10:33:38AM -0400, Colin Walters wrote: >> > I'm personally very in favor of this; of course my usual ref

Re: Giving us the ability to go backwards [was Re: plan to update F27 to systemd-235]

2017-10-07 Thread Igor Gnatenko
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Sat, 2017-10-07 at 12:31 -0400, Matthew Miller wrote: > On Sat, Oct 07, 2017 at 10:33:38AM -0400, Colin Walters wrote: > > I'm personally very in favor of this; of course my usual refrain > > here is that we should *try* new things and have the ab

Re: Giving us the ability to go backwards [was Re: plan to update F27 to systemd-235]

2017-10-07 Thread Neal Gompa
On Sat, Oct 7, 2017 at 12:31 PM, Matthew Miller wrote: > On Sat, Oct 07, 2017 at 10:33:38AM -0400, Colin Walters wrote: >> I'm personally very in favor of this; of course my usual refrain >> here is that we should *try* new things and have the ability >> to back them out if they don't work (the la

Re: Giving us the ability to go backwards [was Re: plan to update F27 to systemd-235]

2017-10-07 Thread Florian Weimer
On 10/07/2017 06:31 PM, Matthew Miller wrote: On Sat, Oct 07, 2017 at 10:33:38AM -0400, Colin Walters wrote: I'm personally very in favor of this; of course my usual refrain here is that we should *try* new things and have the ability to back them out if they don't work (the latter bit is what t

Giving us the ability to go backwards [was Re: plan to update F27 to systemd-235]

2017-10-07 Thread Matthew Miller
On Sat, Oct 07, 2017 at 10:33:38AM -0400, Colin Walters wrote: > I'm personally very in favor of this; of course my usual refrain > here is that we should *try* new things and have the ability > to back them out if they don't work (the latter bit is what the > current system doesn't support). You

Re: plan to update F27 to systemd-235

2017-10-07 Thread Neal Gompa
On Sat, Oct 7, 2017 at 12:02 PM, Richard W.M. Jones wrote: > On Fri, Oct 06, 2017 at 03:04:12PM +, Zbigniew Jędrzejewski-Szmek wrote: >> Hi, >> >> systemd 235 was released today. A large number of issues was closed >> upstream, including many bug fixes, documentation updates, and >> long-stand

Re: plan to update F27 to systemd-235

2017-10-07 Thread Richard W.M. Jones
On Fri, Oct 06, 2017 at 03:04:12PM +, Zbigniew Jędrzejewski-Szmek wrote: > Hi, > > systemd 235 was released today. A large number of issues was closed > upstream, including many bug fixes, documentation updates, and > long-standing RFEs. There are some new features, but relatively few > entire

Re: plan to update F27 to systemd-235

2017-10-07 Thread Colin Walters
On Sat, Oct 7, 2017, at 08:14 AM, Zbigniew Jędrzejewski-Szmek wrote: > Well, my point is that in this case there aren't any big changes, only> some > relatively minor feature additions. According to the policy, > "minor" upgrades are OK after beta. The only difference for critical > path packages

Re: plan to update F27 to systemd-235

2017-10-07 Thread James Hogarth
On 7 October 2017 at 13:14, Zbigniew Jędrzejewski-Szmek wrote: > On Sat, Oct 07, 2017 at 09:19:17AM +0100, James Hogarth wrote: > > Although personally I have no specific objections and indeed plan to use > > the IP accounting stuff on a bunch of units... since we're already past > > beta, this i

Re: plan to update F27 to systemd-235

2017-10-07 Thread Zbigniew Jędrzejewski-Szmek
On Sat, Oct 07, 2017 at 09:19:17AM +0100, James Hogarth wrote: > Although personally I have no specific objections and indeed plan to use > the IP accounting stuff on a bunch of units... since we're already past > beta, this is a critical component of the system and it's not got a Change > on the w

Re: plan to update F27 to systemd-235

2017-10-07 Thread James Hogarth
On 6 Oct 2017 16:08, "Zbigniew Jędrzejewski-Szmek" wrote: Hi, systemd 235 was released today. A large number of issues was closed upstream, including many bug fixes, documentation updates, and long-standing RFEs. There are some new features, but relatively few entirely new features or changes in

plan to update F27 to systemd-235

2017-10-06 Thread Zbigniew Jędrzejewski-Szmek
Hi, systemd 235 was released today. A large number of issues was closed upstream, including many bug fixes, documentation updates, and long-standing RFEs. There are some new features, but relatively few entirely new features or changes in behaviour that impact other services. There also are no (in