Your message dated Wed, 22 Jun 2016 06:36:30 +
with message-id
and subject line Bug#826512: fixed in systemd 230-3
has caused the Debian Bug report #826512,
regarding [systemd] automount hangs after first unmount
to be marked as done.
This means that you claim that the problem has been dealt
Your message dated Wed, 22 Jun 2016 06:36:30 +
with message-id
and subject line Bug#827756: fixed in systemd 230-3
has caused the Debian Bug report #827756,
regarding Cannot enable lingering without policykit-1
to be marked as done.
This means that you claim that the problem has been dealt wi
Your message dated Wed, 22 Jun 2016 06:36:30 +
with message-id
and subject line Bug#825981: fixed in systemd 230-3
has caused the Debian Bug report #825981,
regarding failure message upon install
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is
Your message dated Wed, 22 Jun 2016 06:36:30 +
with message-id
and subject line Bug#826512: fixed in systemd 230-3
has caused the Debian Bug report #826512,
regarding systemd: autofs mount hang in 230
to be marked as done.
This means that you claim that the problem has been dealt with.
If thi
Your message dated Wed, 22 Jun 2016 06:36:30 +
with message-id
and subject line Bug#826512: fixed in systemd 230-3
has caused the Debian Bug report #826512,
regarding systemd.automount fails to mount filesystem after unmount do to a
timeout, then crashes
to be marked as done.
This means that
Your message dated Wed, 22 Jun 2016 06:36:30 +
with message-id
and subject line Bug#825913: fixed in systemd 230-3
has caused the Debian Bug report #825913,
regarding systemd init script integration: needs manual systemctl daemon-reload
after installing initscript
to be marked as done.
This
Your message dated Wed, 22 Jun 2016 06:36:30 +
with message-id
and subject line Bug#823322: fixed in systemd 230-3
has caused the Debian Bug report #823322,
regarding please build "systemd-sysusers" binary
to be marked as done.
This means that you claim that the problem has been dealt with.
I
Your message dated Wed, 22 Jun 2016 06:36:29 +
with message-id
and subject line Bug#817210: fixed in systemd 230-3
has caused the Debian Bug report #817210,
regarding systemd-resolve: segfaults upon domain name resolution
to be marked as done.
This means that you claim that the problem has be
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Tue, 21 Jun 2016 23:51:07 +0200
Source: systemd
Binary: systemd systemd-sysv systemd-container systemd-journal-remote
systemd-coredump libpam-systemd libnss-myhostname libnss-mymachines
libnss-resolve libsystemd0 libs
systemd_230-3_amd64.changes uploaded successfully to localhost
along with the files:
systemd_230-3.dsc
systemd_230-3.debian.tar.xz
libnss-myhostname-dbgsym_230-3_amd64.deb
libnss-myhostname_230-3_amd64.deb
libnss-mymachines-dbgsym_230-3_amd64.deb
libnss-mymachines_230-3_amd64.deb
libn
Am 21.06.2016 um 23:29 schrieb Dmitry Smirnov:
> On Tuesday, 21 June 2016 10:39:25 PM AEST Martin Pitt wrote:
>> FTR, we just discussed this on IRC. I'm working on adding the
>> systemd-sysusers binary for now (no sysusers.d/ files and the unit yet, as
>> these need Debianization and an integration
Processing control commands:
> tags -1 + moreinfo
Bug #825850 [systemd] [systemd] Long time to load accounts-daemon.service and
issue with X
Added tag(s) moreinfo.
--
825850: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=825850
Debian Bug Tracking System
Contact ow...@bugs.debian.org with pr
Control: tags -1 + moreinfo
On Mon, 30 May 2016 20:56:57 +0200 Fenix wrote:
> Package: systemd
> Version: 230-1
> Severity: normal
>
> --- Please enter the report below this line. ---
>
>
> Dear maintainer:
>
>
> After 229.6 (I waited that 230-1 fix it, but it is the same) update I
> ha
On Fri, 29 Jan 2016 00:17:23 +0100 Michael Biebl wrote:
> Control: tags -1 + moreinfo
>
> Hi Laurent
>
> On Thu, 12 Nov 2015 13:02:40 +0100 Laurent Bigonville
> wrote:
> > I'm using libeatmydata in sbuild on my machine, and it FTBFS due to the
> > postbuild check that looks for libs in /usr
>
Control: tags -1 + moreinfo
On Sat, 2 Apr 2016 13:09:56 -0500 Stephen Crowley
wrote:
> Package: systemd
> Version: 229-3
> Severity: important
>
> Try changing a mac using method 1 at
>
> https://wiki.archlinux.org/index.php/MAC_address_spoofing#Method_1:_systemd-networkd
>
> it doesnt work
>
Processing control commands:
> tags -1 + moreinfo
Bug #819817 [systemd] systemd: mac addresss changing doesnt work as advertised
Added tag(s) moreinfo.
--
819817: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=819817
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
_
On Tuesday, 21 June 2016 10:39:25 PM AEST Martin Pitt wrote:
> FTR, we just discussed this on IRC. I'm working on adding the
> systemd-sysusers binary for now (no sysusers.d/ files and the unit yet, as
> these need Debianization and an integration test), and we'll upload -3
> RSN.
Excellent. Thank
Processing commands for cont...@bugs.debian.org:
> tags 825981 + pending
Bug #825981 [systemd] failure message upon install
Added tag(s) pending.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
825981: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=825981
Debian
Am 09.06.2016 um 14:47 schrieb Arturo Borrero Gonzalez:
> On 9 June 2016 at 14:18, Michael Biebl wrote:
>> So, I would suggest you make iptables-dev a transitional package which
>> pulls in the new -dev packages.
>> I would also move it to section oldlibs.
>> Then file bug reports to get those pa
Processing commands for cont...@bugs.debian.org:
> tags 823322 + pending
Bug #823322 [src:systemd] please build "systemd-sysusers" binary
Added tag(s) pending.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
823322: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug
Dmitry Smirnov [2016-06-16 0:26 +1000]:
> Please, pretty please address the issue ASAP or provide time frame for
> decision to be made... We shouldn't let packages to be broken for so long.
FTR, we just discussed this on IRC. I'm working on adding the
systemd-sysusers binary for now (no sysusers
Am 21.06.2016 um 18:28 schrieb Szilard Andai:
> I have an udev rule to automatically mount an USB device:
> ACTION=="add", KERNEL=="sd?1", ATTRS{idVendor}=="0781",
> ATTRS{idProduct}=="5150", RUN+="/bin/mount -v %N"
...
> Unfortunately the device doesn't get actually mounted: it doesn't appear
>
Hi, I am too experiencing the same behaviour described in this report on
two of my systems, but I it doesn't stop when I restart systemd-logind. It
also seems to randomly occur after restarts, the 300 logins earlier seem
like a good estimate. Commenting out the pam_systemd module in
/etc/pam.d/comm
23 matches
Mail list logo