Re: [arch-dev-public] switching to systemd-stable

Hi, On 07/06/17 at 09:44am, NicoHood wrote: > On 07/06/2017 09:12 AM, Bartłomiej Piotrowski wrote: > > On 2017-07-06 02:11, NicoHood wrote: > >> On 07/05/2017 12:10 AM, Christian Hesse wrote: > >>> Dave Reisner on Sat, 2017/07/01 13:22: > Hey all, > > This

Re: [arch-dev-public] switching to systemd-stable

On 2017-07-06 09:44, NicoHood wrote: > On 07/06/2017 09:12 AM, Bartłomiej Piotrowski wrote: >> On 2017-07-06 02:11, NicoHood wrote: >>> On 07/05/2017 12:10 AM, Christian Hesse wrote: Dave Reisner on Sat, 2017/07/01 13:22: > Hey all, > > This should be pretty

Re: [arch-dev-public] switching to systemd-stable

On 06/07/17 17:44, NicoHood wrote: > ArchLinux At least spell the name of the distro correctly. It is the simple addition of one space character between "Arch" and "Linux". But I see it is easy for people to forget about silly one character issues. A

Re: [arch-dev-public] switching to systemd-stable

On 07/06/2017 09:44 AM, NicoHood wrote: > And yes, I am doing stuff in the background. I wrote a guide and a tool > that simplifies source code signing[1] and I am doing a detailed > security analysis on all ArchLinux packages. And once it is ready I will > request gpg signatures from every

Re: [arch-dev-public] switching to systemd-stable

On 07/06/2017 09:12 AM, Bartłomiej Piotrowski wrote: > On 2017-07-06 02:11, NicoHood wrote: >> On 07/05/2017 12:10 AM, Christian Hesse wrote: >>> Dave Reisner on Sat, 2017/07/01 13:22: Hey all, This should be pretty much a no-brainer, but wanted to be sure I

Re: [arch-dev-public] switching to systemd-stable

On 2017-07-06 02:11, NicoHood wrote: > On 07/05/2017 12:10 AM, Christian Hesse wrote: >> Dave Reisner on Sat, 2017/07/01 13:22: >>> Hey all, >>> >>> This should be pretty much a no-brainer, but wanted to be sure I wasn't >>> missing anything. Systemd upstream publishes a

Re: [arch-dev-public] switching to systemd-stable

On 07/05/2017 12:10 AM, Christian Hesse wrote: > Dave Reisner on Sat, 2017/07/01 13:22: >> Hey all, >> >> This should be pretty much a no-brainer, but wanted to be sure I wasn't >> missing anything. Systemd upstream publishes a "systemd-stable" repo [1] >> which branches at

Re: [arch-dev-public] switching to systemd-stable

Dave Reisner on Sat, 2017/07/01 13:22: > Hey all, > > This should be pretty much a no-brainer, but wanted to be sure I wasn't > missing anything. Systemd upstream publishes a "systemd-stable" repo [1] > which branches at each tag and cherry-picks backports. I'd like to >

Re: [arch-dev-public] switching to systemd-stable

Le 01/07/2017 à 20:15, Laurent Carlier via arch-dev-public a écrit : > Le samedi 1 juillet 2017, 19:59:49 CEST Christian Hesse a écrit : >> Dave Reisner on Sat, 2017/07/01 13:22: >>> One potentially bikeshed-worthy question is versioning. Do we count >>> commits and modify

Re: [arch-dev-public] switching to systemd-stable

Le samedi 1 juillet 2017, 19:59:49 CEST Christian Hesse a écrit : > Dave Reisner on Sat, 2017/07/01 13:22: > > One potentially bikeshed-worthy question is versioning. Do we count > > commits and modify the pkgver every time we build from the repo, e.g. > > 233.23-1 (meaning

Re: [arch-dev-public] switching to systemd-stable

Dave Reisner on Sat, 2017/07/01 13:22: > Hey all, > > This should be pretty much a no-brainer, but wanted to be sure I wasn't > missing anything. Systemd upstream publishes a "systemd-stable" repo [1] > which branches at each tag and cherry-picks backports. I'd like to >

[arch-dev-public] switching to systemd-stable

Hey all, This should be pretty much a no-brainer, but wanted to be sure I wasn't missing anything. Systemd upstream publishes a "systemd-stable" repo [1] which branches at each tag and cherry-picks backports. I'd like to switch our systemd package to this repo to avoid some of the duplication of