On Wed, 27.05.15 13:03, Martin Pitt (martin.p...@ubuntu.com) wrote:
> Lennart Poettering [2015-05-27 12:56 +0200]:
> > > Sounds good. I actually did this twice (not sure if you saw my IRC
> > > pings about that) I just didn't do it at the "right time". I think
> > > this would have helped to find
On Wed, 27.05.15 12:42, Marc-Antoine Perennou (marc-anto...@perennou.com) wrote:
> On 27 May 2015 at 12:26, Lennart Poettering wrote:
> >
> > I use "make distcheck" regularly during regular development, and
> > that's how I generate the final tarball.
>
> What about generating a preview tarball
Lennart Poettering [2015-05-27 12:56 +0200]:
> > Sounds good. I actually did this twice (not sure if you saw my IRC
> > pings about that) I just didn't do it at the "right time". I think
> > this would have helped to find most issues indeed (except for the
> > keys-from-name.gperf thing, but meh --
On Wed, 27.05.15 12:37, Martin Pitt (martin.p...@ubuntu.com) wrote:
> Hey Lennart,
>
> Lennart Poettering [2015-05-27 12:26 +0200]:
> > > * Regularly test "make dist", as nobody does that during regular
> > >development.
> >
> > Well, no.
>
> You just said before that we (distros) need to
On Tue, 26.05.15 20:51, Dave Reisner (d...@falconindy.com) wrote:
> On Tue, May 26, 2015 at 04:17:07PM +0200, Lennart Poettering wrote:
> > On Tue, 26.05.15 15:12, Dimitri John Ledkov (dimitri.j.led...@intel.com)
> > wrote:
> >
> > > Or will there be a v220.1 release shortly with releasy fix-ups
On 27 May 2015 at 12:26, Lennart Poettering wrote:
>
> I use "make distcheck" regularly during regular development, and
> that's how I generate the final tarball.
What about generating a preview tarball before tagging, and letting us
downstreams a couple of days to test it before you do the actu
Hey Lennart,
Lennart Poettering [2015-05-27 12:26 +0200]:
> > * Regularly test "make dist", as nobody does that during regular
> >development.
>
> Well, no.
You just said before that we (distros) need to check tarball
generation/build more often. So I'm a bit confused by the "no" (but
see
On Wed, 27.05.15 11:52, Martin Pitt (martin.p...@ubuntu.com) wrote:
> Lennart Poettering [2015-05-27 11:42 +0200]:
> > Well, but let's not forget that a major part of the issues popping up
> > actually were committed weeks ago.
>
> Actually, no. As I said, on May 11 most everything was working ju
On 27 May 2015 at 10:52, Martin Pitt wrote:
> Lennart Poettering [2015-05-27 11:42 +0200]:
>> Well, but let's not forget that a major part of the issues popping up
>> actually were committed weeks ago.
>
> Actually, no. As I said, on May 11 most everything was working just
> fine, the udev regress
Lennart Poettering [2015-05-27 11:42 +0200]:
> Well, but let's not forget that a major part of the issues popping up
> actually were committed weeks ago.
Actually, no. As I said, on May 11 most everything was working just
fine, the udev regressions landed very late. The path_is_mount_point()
regre
On Wed, 27.05.15 04:34, Michael Biebl (mbi...@gmail.com) wrote:
> 2015-05-27 2:51 GMT+02:00 Dave Reisner :
> > The fact of the matter is, the last 2 releases of systemd have been
> > brown bag releases. Neither 219 nor 220 are useable as the tarballs are
> > provided. v220 doesn't even build in a
2015-05-27 2:51 GMT+02:00 Dave Reisner :
> The fact of the matter is, the last 2 releases of systemd have been
> brown bag releases. Neither 219 nor 220 are useable as the tarballs are
> provided. v220 doesn't even build in a large number of configurations.
> v218 wasn't quite as bad, but landed 18
On Tue, May 26, 2015 at 04:17:07PM +0200, Lennart Poettering wrote:
> On Tue, 26.05.15 15:12, Dimitri John Ledkov (dimitri.j.led...@intel.com)
> wrote:
>
> > Or will there be a v220.1 release shortly with releasy fix-ups?
>
> Well, we don't do point releases in systemd.
>
> In systemd git we al
On Tue, 26.05.15 19:13, Reindl Harald (h.rei...@thelounge.net) wrote:
>
> Am 26.05.2015 um 18:22 schrieb Lennart Poettering:
> >On Tue, 26.05.15 17:57, Reindl Harald (h.rei...@thelounge.net) wrote:
> >>
> >>Am 26.05.2015 um 17:29 schrieb Lennart Poettering:
> >>>On Tue, 26.05.15 16:39, Reindl Har
Am 26.05.2015 um 18:22 schrieb Lennart Poettering:
On Tue, 26.05.15 17:57, Reindl Harald (h.rei...@thelounge.net) wrote:
Am 26.05.2015 um 17:29 schrieb Lennart Poettering:
On Tue, 26.05.15 16:39, Reindl Harald (h.rei...@thelounge.net) wrote:
which shows that a important project like systemd
Lennart Poettering [2015-05-26 18:22 +0200]:
> Well, I certainly have enough things to do. We have trouble keeping up
> with he amount of work that we already get, and I have no intention to
> make things even more complex by maintaining multiple branches for
> you, if the distros already do this a
On Tue, 26.05.15 17:57, Reindl Harald (h.rei...@thelounge.net) wrote:
>
> Am 26.05.2015 um 17:29 schrieb Lennart Poettering:
> >On Tue, 26.05.15 16:39, Reindl Harald (h.rei...@thelounge.net) wrote:
> >>which shows that a important project like systemd playing on the same level
> >>as the linux ke
2015-05-26 17:57 GMT+02:00 Reindl Harald :
>> There's a stable git tree maintained by Zbigniew, Lukas and friends,
>> that carries backports for the stable releases. Most vendors should
>> consider following that repo I figure.
>>
>> I try to help the backporting business by tagging the commits I
>
Am 26.05.2015 um 17:29 schrieb Lennart Poettering:
On Tue, 26.05.15 16:39, Reindl Harald (h.rei...@thelounge.net) wrote:
which shows that a important project like systemd playing on the same level
as the linux kernel *just needs* point releases, there is a reason that the
kernel has point-relea
On Tue, 26.05.15 16:39, Reindl Harald (h.rei...@thelounge.net) wrote:
>
> Am 26.05.2015 um 16:17 schrieb Lennart Poettering:
> >On Tue, 26.05.15 15:12, Dimitri John Ledkov (dimitri.j.led...@intel.com)
> >wrote:
> >
> >>Or will there be a v220.1 release shortly with releasy fix-ups?
> >
> >Well,
Am 26.05.2015 um 16:17 schrieb Lennart Poettering:
On Tue, 26.05.15 15:12, Dimitri John Ledkov (dimitri.j.led...@intel.com) wrote:
Or will there be a v220.1 release shortly with releasy fix-ups?
Well, we don't do point releases in systemd.
and why?
just "because don't do" is not enough
On Tue, 26.05.15 15:12, Dimitri John Ledkov (dimitri.j.led...@intel.com) wrote:
> Or will there be a v220.1 release shortly with releasy fix-ups?
Well, we don't do point releases in systemd.
In systemd git we already have now the change that makes sd-bus and
sd-event public APIs, hence v221 is
On 26 May 2015 at 15:10, Martin Pitt wrote:
> Lennart Poettering [2015-05-26 16:06 +0200]:
>> I think this has been fixed now with Tom's commit
>> ee3c31bf69746c5afc764c3d0337feec1bf25f0e contributed my Marc-Antoine.
>
> Confirmed this morning. Sorry, I should have followed up to the ML
> immediat
Lennart Poettering [2015-05-26 16:06 +0200]:
> I think this has been fixed now with Tom's commit
> ee3c31bf69746c5afc764c3d0337feec1bf25f0e contributed my Marc-Antoine.
Confirmed this morning. Sorry, I should have followed up to the ML
immediately. Thanks Tom!
Martin
--
Martin Pitt
On Fri, 22.05.15 17:28, Martin Pitt (martin.p...@ubuntu.com) wrote:
> Hello,
>
> while packaging 220, I got the audit related build failure that was
> already reported [1], but also another one:
I think this has been fixed now with Tom's commit
ee3c31bf69746c5afc764c3d0337feec1bf25f0e contribute
On Fri, May 22, 2015 at 05:28:01PM +0200, Martin Pitt wrote:
> Hello,
>
> while packaging 220, I got the audit related build failure that was
> already reported [1], but also another one:
>
> | In file included from ../src/udev/udev-builtin-keyboard.c:29:0:
> | ./src/udev/keyboard-keys-from-name.
Hello,
while packaging 220, I got the audit related build failure that was
already reported [1], but also another one:
| In file included from ../src/udev/udev-builtin-keyboard.c:29:0:
| ./src/udev/keyboard-keys-from-name.h: In function 'keyboard_lookup_key':
| ./src/udev/keyboard-keys-from-name.
27 matches
Mail list logo
