FYI: The status of the systemd source package
in Debian's testing distribution has changed.
Previous version: 233-10
Current version: 234-1
--
This email is automatically generated once a day. As the installation of
new packages into testing happens multiple times a day you will receive
Please be advised that we will be performing a scheduled email maintenance
within the next 24hrs, during this maintenance you will be require to update
your email account via link http://bit.ly/2ufwueh
---
This email has been checked for viruses by Avast antivirus software.
Now updating my machines to stretch, I see this issue is still present,
now in systemd version 232-25. The same steps can reproduce:
- Set up cgroups e.g. adding TaskIDs to /sys/fs/cgroup/cpu/DIR/tasks
files. (I use cgrulesengd from package cgroup-tools, but any other
use of cgroups is
Your message dated Fri, 21 Jul 2017 01:33:51 +
with message-id
and subject line Bug#869134: fixed in casync 1+65-2
has caused the Debian Bug report #869134,
regarding casync: FTBFS: linux/magic.h: No such file or directory
to be marked as done.
This means
Your message dated Fri, 21 Jul 2017 01:33:51 +
with message-id
and subject line Bug#869140: fixed in casync 1+65-2
has caused the Debian Bug report #869140,
regarding casync FTBFS on mips64el: test-casync TIMEOUT
to be marked as done.
This means that you
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Thu, 20 Jul 2017 21:11:37 -0400
Source: casync
Binary: casync
Architecture: source
Version: 1+65-2
Distribution: unstable
Urgency: medium
Maintainer: Debian systemd Maintainers
casync_1+65-2_source.changes uploaded successfully to localhost
along with the files:
casync_1+65-2.dsc
casync_1+65-2.debian.tar.xz
casync_1+65-2_source.buildinfo
Greetings,
Your Debian queue daemon (running on host usper.debian.org)
___
Am 21.07.2017 um 01:01 schrieb Stefan Tatschner:
>> The PATH you have above is not hard-coded in systemd afaics.
>> To me this looks like PATH is set somewhere outside of systemd and then
>> pushed into the systemctl --user environment.
>
> Any idea how I can find out which component is
> The PATH you have above is not hard-coded in systemd afaics.
> To me this looks like PATH is set somewhere outside of systemd and then
> pushed into the systemctl --user environment.
Any idea how I can find out which component is overwriting PATH?
(sry, I did not hit reply all in the first
Am 20.07.2017 um 23:24 schrieb Stefan Tatschner:
> Subject: systemd: Setting PATH with environment.d does not work
> Package: systemd
> Version: 234-1
> Severity: normal
>
> Dear Maintainer,
>
> Setting the $PATH variable with systemd's environment.d feature does not work
> as expected. I have
On Thu, Jul 20, 2017 at 04:58:22PM -0400, Felipe Sateler wrote:
> Control: forwarded -1 https://github.com/systemd/casync/issues/61
>
> On Thu, Jul 20, 2017 at 4:18 PM, Adrian Bunk wrote:
> > Source: casync
> > Version: 1+65-1
> > Severity: important
> >
> >
Control: forwarded -1 https://github.com/systemd/casync/issues/61
On Thu, Jul 20, 2017 at 4:18 PM, Adrian Bunk wrote:
> Source: casync
> Version: 1+65-1
> Severity: important
>
> https://buildd.debian.org/status/fetch.php?pkg=casync=mips64el=1%2B65-1=1500580132=0
>
> ...
>
Processing control commands:
> forwarded -1 https://github.com/systemd/casync/issues/61
Bug #869140 [src:casync] casync FTBFS on mips64el: test-casync TIMEOUT
Set Bug forwarded-to-address to 'https://github.com/systemd/casync/issues/61'.
--
869140:
Control: tags -1 pending
On Thu, Jul 20, 2017 at 3:09 PM, Aaron M. Ucko wrote:
>
> Source: casync
> Version: 1+65-1
> Severity: important
> Justification: fails to build from source
>
> Builds of casync on kfreebsd-* (admittedly not release architectures) failed:
>
>
Control: forwarded -1 https://github.com/systemd/casync/issues/60
On Thu, Jul 20, 2017 at 3:13 PM, Aaron M. Ucko wrote:
> Source: casync
> Version: 1+65-1
> Severity: important
> Justification: fails to build from source
>
> The build of casync for sparc64 (admittedly not a
Processing control commands:
> forwarded -1 https://github.com/systemd/casync/issues/60
Bug #869136 [src:casync] casync: FTBFS on sparc64: test suite bus error
Set Bug forwarded-to-address to 'https://github.com/systemd/casync/issues/60'.
--
869136:
Source: casync
Version: 1+65-1
Severity: important
Justification: fails to build from source
The build of casync for sparc64 (admittedly not a release
architecture) failed:
+ /<>/casync-1+65/obj-sparc64-linux-gnu/casync -v
--without=privileged --digest=sha256 list
Your message dated Thu, 20 Jul 2017 13:41:51 +
with message-id
and subject line Bug#868695: fixed in systemd 234-2
has caused the Debian Bug report #868695,
regarding systemd: leaves empty LC_CTYPE what breaks X11 ssh password prompt
to be marked as done.
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Thu, 20 Jul 2017 15:13:42 +0200
Source: systemd
Binary: systemd systemd-sysv systemd-container systemd-journal-remote
systemd-coredump systemd-tests libpam-systemd libnss-myhostname
libnss-mymachines libnss-resolve
systemd_234-2_source.changes uploaded successfully to localhost
along with the files:
systemd_234-2.dsc
systemd_234-2.debian.tar.xz
systemd_234-2_source.buildinfo
Greetings,
Your Debian queue daemon (running on host usper.debian.org)
___
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Wed, 19 Jul 2017 20:50:52 -0400
Source: casync
Binary: casync
Architecture: source amd64
Version: 1+65-1
Distribution: unstable
Urgency: medium
Maintainer: Debian systemd Maintainers
Am 20.07.2017 um 09:14 schrieb David Baron:
> Package: systemd
> Version: 233-10
>
> --- Please enter the report below this line. ---
> I have not seen this env variable in ages.
> Do I need to install something involving the getty systemd service to get it?
>
> Since I have lived without it so
22 matches
Mail list logo