Michael Biebl [2017-03-31 3:08 +0200]:
> Imo the only clean solution is to split out the tests into a separate
> package systemd-tests, which then can have a strictly versioned
> dependency on systemd (= ${binary:Version})
The systemd dependency is a good reason indeed, so I suppose let's do
Hello,
I am Barr Kong Khemara, I humbly ask if you are related to my client who died
couple of
years ago in a car accident here in my country Cambodia. I wish to also inquire
if
it is possible to have different families with the same last name as yours by
coincidence
who do not share the same
Am 31.03.2017 um 01:16 schrieb Arthur Gautier:
> Package: libsystemd-dev
> Version: 232-22
> Severity: normal
>
> Dear maintainer,
>
> One should be able to install libsystemd and libsystemd-dev without having
> systemd.
>
> When using a build machine with sysvinit instead of systemd, we can't
On Fri, Mar 31, 2017 at 12:51:08AM +0200, Michael Biebl wrote:
> Maybe I'm overly paranoid here, but maybe that helps to better
> understand my concerns.
No, your concerns sound reasonable to me, and I agree that demanding
a username from group sudo, along with its password sounds like it
could
Package: libsystemd-dev
Version: 232-22
Severity: normal
Dear maintainer,
One should be able to install libsystemd and libsystemd-dev without having
systemd.
When using a build machine with sysvinit instead of systemd, we can't build
packages depending on libsystemd-dev without installing first
Am 31.03.2017 um 00:27 schrieb Nathan Dorfman:
> Hi, this is still an issue with the default stretch install, if the
> option to not set a root password is taken at installation.
>
> It is quite severe IMO, especially considering how likely it is to be
> discovered only when the rescue shell is
Hi, this is still an issue with the default stretch install, if the
option to not set a root password is taken at installation.
It is quite severe IMO, especially considering how likely it is to be
discovered only when the rescue shell is actually needed.
If this really can't be fixed before
Am 30.03.2017 um 23:07 schrieb Emmanuel DECAEN:
> Hi,
>
> I have the same of problem on multiple servers with systemd/232-19.
>
> You will find journalctl -alb et udevadm info in attachments.
Your journal shows problems with /var, /tmp, /home and swap.
Makes me wonder if your /etc/fstab is
Processing commands for cont...@bugs.debian.org:
> #
> # bts-link upstream status pull for source package systemd
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> #
> user bts-link-upstr...@lists.alioth.debian.org
Setting user to
#
# bts-link upstream status pull for source package systemd
# see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
#
user bts-link-upstr...@lists.alioth.debian.org
# remote status report for #837893 (http://bugs.debian.org/837893)
# Bug title: systemd: Logging from gnome
Package: systemd
Version: 233-5
Dear maintainer,
here are 2 DNS queries that illustrate the problem:
- when I query a "real" DNS server (bind) I get the expected answer
"irancy.iut2.upmf-grenoble.fr"
- when I query systemd-resolved I get the short answer "irancy"
root@irancy:~# host
11 matches
Mail list logo
