On 1/15/19 8:58 PM, Michael Biebl wrote:
What's going on is just too stupid/crazy.
This begs the question what you consider is too stupid/crazy?
Is it something here upstream ( which could be improved upon )?
Or is it something ( political? ) downstream in Debian?
Or both?
JBG
Am Di, 15. Jan 2019, um 22:21, schrieb Vito Caputo:
> On Tue, Jan 15, 2019 at 09:58:20PM +0100, Michael Biebl wrote:
> > Will stop maintaining systemd in debian for a while.
> >
> > What's going on is just too stupid/crazy.
> >
>
> Michael, as a long-time Debian user, I just wanted to say I
Hi,
I'm quite new to systemd-nspawn,
I configured a systemd container based on ubuntu bionic using debootstrap.
I can start the container from a bionic host (systemd 237) with a
command like this one
systemd-nspawn -b -D bionic-devel
--capability=CAP_SYS_TIME,CAP_SYS_RAWIO --bind=/dev/sda
Lennart Poettering on Tue, 2019/01/15 20:00:
> Note that we don't branch releases right now. Instead when we are
> getting closer to a release we simply don't merge PRs we don't
> consider appropriate for the release anymore until after the
> release. Or in other words: the master branch simply
On 1/15/19 6:49 PM, Lennart Poettering wrote:
On Di, 15.01.19 11:23, Eric DeVolder (eric.devol...@oracle.com) wrote:
Systemd-devel,
Below is a write-up I've done to explain a new service for archiving pstore
contents. I've attached the pstore.service files
(/lib/systemd/system/pstore.service
On Tue, Jan 15, 2019 at 09:58:20PM +0100, Michael Biebl wrote:
> Will stop maintaining systemd in debian for a while.
>
> What's going on is just too stupid/crazy.
>
Michael, as a long-time Debian user, I just wanted to say I appreciate
your work. I'm confident in saying it's no accident that
Will stop maintaining systemd in debian for a while.
What's going on is just too stupid/crazy.
--
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?
___
systemd-devel mailing list
On Di, 15.01.19 10:36, Filipe Brandenburger (filbran...@google.com) wrote:
> So I think all the bits already exist somewhere and perhaps a small
> change in naming would go a long way to make these pushes smoother.
>
> If when we cut v240 from the master branch, we had called it v240-rc1
>
On Di, 15.01.19 11:23, Eric DeVolder (eric.devol...@oracle.com) wrote:
> Systemd-devel,
>
> Below is a write-up I've done to explain a new service for archiving pstore
> contents. I've attached the pstore.service files
> (/lib/systemd/system/pstore.service and bin/pstore-tool). These are trivial
So I think all the bits already exist somewhere and perhaps a small
change in naming would go a long way to make these pushes smoother.
If when we cut v240 from the master branch, we had called it v240-rc1
instead, perhaps it was clear that it could take some more testing
before it was made
When you create a new organization you can choose "Team For Open
Source" plan. Here is the link
https://github.com/account/organizations/new
Though, I don't know if it's possible to upgrade the existing systemd
organization, sorry. Maybe it's possible to contact github support to
ask for this.
Systemd-devel,
Below is a write-up I've done to explain a new service for archiving
pstore contents. I've attached the pstore.service files
(/lib/systemd/system/pstore.service and bin/pstore-tool). These are
trivial right now, but easy to build upon if periodic, rather than just
on-boot,
Thank you for your explanation, Lenart. I tried different approach.
Everything is running on a single thread. I have a global
`sd_bus_message* test` variable. I do the following
int method_handler(sd_bus_message* m, void* /*userdata*/,
sd_bus_error* /*error*/) {
test = sd_bus_message_ref(m);
Hi everyone,
241 will be released soon. Current list of outstanding tickets [1]:
"23 wireguard peers hang systemd-networkd"
#11404 opened 3 days ago by darkk
network: wait for kernel to reply ipv6 peer address
#11428
(needs review)
"Bump numbers for v241"
#11387
(release mechanics)
"Add
On 1/14/19 3:48 PM, Lennart Poettering wrote:
On Mo, 14.01.19 08:43, Dave Reisner (d...@falconindy.com) wrote:
On Mon, Jan 14, 2019 at 10:59:06AM +0100, Jan Synacek wrote:
Hi,
since v240 didn't go too well, I would like to suggest that the next one
(preferably two) release(s) are bugfix
On Tue, Jan 15, 2019 at 01:09:16PM +0100, Lennart Poettering wrote:
> On Mo, 14.01.19 11:26, Dave Reisner (d...@falconindy.com) wrote:
> > >
> > > Well, that sounds as if you want to volunteer as release engineer? ;-)
> > >
> > > Thing is, we are understaffed. I too have a wishlist of things I'd
>
On Mo, 14.01.19 21:07, Jean Valjean (valjean.jean1...@gmail.com) wrote:
> I want to send a reply to a method call outside method_handler. Is it
> possible?
> In the method_handler I increase reference count of sd_bus_message and send
> it to the other thread. From there I want to call
>
On Di, 15.01.19 09:51, Michael Olbrich (m.olbr...@pengutronix.de) wrote:
> On Mon, Jan 14, 2019 at 04:36:49PM +0100, Lennart Poettering wrote:
> > I'd love to see some more CI hookup with Arch and Debian for example
> > (right now there is zero) or even just a git preview package set or so
> >
On Mo, 14.01.19 11:26, Dave Reisner (d...@falconindy.com) wrote:
> >
> > Well, that sounds as if you want to volunteer as release engineer? ;-)
> >
> > Thing is, we are understaffed. I too have a wishlist of things I'd
> > like to see done, but with only two paid full-time upstream engineers
> >
On Mon, Jan 14, 2019 at 04:36:49PM +0100, Lennart Poettering wrote:
> I'd love to see some more CI hookup with Arch and Debian for example
> (right now there is zero) or even just a git preview package set or so
> that interested people can test. Without either it's very likely that
> things break
20 matches
Mail list logo
