On Tue, Oct 11, 2016 at 11:30:04AM -0300, Felipe Sateler wrote:
> > If your intention is that "debian/rules build" builds everything from
> > scratch again if you do it a second time, you can't even do that
> > with dh because of dh's own stamping system.
> >
> > For example, try "debian/rules bui
On Tue, Oct 11, 2016 at 11:07:13AM -0300, Felipe Sateler wrote:
> > I suggest the patch below to fix this. It makes debian/rules a little bit
> > shorter
> > and maybe a little bit more dh-style.
>
> The build target is there because otherwise make does not consider it
> phony (the build system
Package: src:mkosi
Version: 0~20161004-1
Severity: serious
Tags: patch
Dear maintainer:
I tried to build this package in stretch with "dpkg-buildpackage -A"
(which is what the "Arch: all" autobuilder would do to build it)
but it failed:
---
On Tue, May 31, 2016 at 07:20:28PM +0200, Michael Biebl wrote:
> Which version of login and libpam-systemd?
Current ones in stretch as of today:
login 1:4.2-3.1
libpam-systemd 230-1
___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@list
Package: libpam-systemd,login
Dear maintainers:
Since I upgraded to stretch, logcheck sends me messages like this each
time I do "su -" to become root:
Security Events for su
=-=-=-=-=-=-=-=-=-=-=-
[...] mymachine su[4887]: pam_systemd(su:session): Cannot create session:
Already running in a se
affects 823530 ruby2.3
affects 823530 openexr
thanks
On Fri, 6 May 2016, Antonio Terceiro wrote:
> Will every package need to start declaring higher limits explicitly?
I also would like to know the answer for that question.
How does a package which needs a higher limit to build is supposed to
o
On Wed, Mar 30, 2016 at 06:57:39AM +1300, beagleburt wrote:
> Package: general
> Severity: normal
>
> Dear Maintainer,
>
> * CLI command "shutdown -r now" USUALLY does not work, since systemd replaced
> sysvinit in Debian 8 "jessie".
> Posted problem on http://www.linuxquestions.org/questions/deb
On Wed, 8 Apr 2015, Michael Biebl wrote:
> Can you boot with systemd.log_level=debug on the kernel command line and
> attach the output of journalctl -alb.
Attached.
journalctl-alb.txt.gz
Description: application/gzip
___
Pkg-systemd-maintainers mailin
On Wed, 8 Apr 2015, Michael Biebl wrote:
> Am 08.04.2015 um 13:33 schrieb Santiago Vila:
> > Package: systemd
> > Version: 215-14
> >
> > After a recent upgrade in a lab where I use NFS, I see messages like this:
> >
> > ifup[370]: mount.nfs: /home/nfs
On a computer which is a little bit faster than the others I see this
instead:
ifup[429]: /sbin/ifup: interface eth0 already configured
I can even reproduce it after *every* reboot:
* One computer (faster than the others) says "eth0 already configured".
* The others (older, slower) say "/home/nf
Package: systemd
Version: 215-14
After a recent upgrade in a lab where I use NFS, I see messages like this:
ifup[370]: mount.nfs: /home/nfs is busy or already mounted
but this didn't happen before. I suspect of recent changes in systemd.
It's not grave as it seems harmless, but if it's a regres
On Sun, 30 Nov 2014, Ben Hutchings wrote:
> Control: notfound -1 204-8
>
> Nils Dagsson Moskopp wrote:
> > See also bug #770876, where udev device enumeration in Xorg does not work
> > with Linux kernel 3.2, but does work with Linux kernel 3.16. Introducing
> > a versioned dependency of systemd o
Package: systemd
Version: 215-5+b1
Tags: patch
The output of journalctl --help says this:
--since=DATE Start showing entries on or newer than the specified date
--until=DATE Stop showing entries on or older than the specified date
This is a little bit confusing. In fact, beca
Package: systemd
Version: 215-5+b1
I modified /etc/systemd/journald.conf by adding these two lines:
MaxRetentionSec=7day
MaxFileSec=1day
Before the change, journalctl says:
-- Logs begin at vie 2014-10-10 14:33:54 CEST, [...]
After the change, journalctl says:
-- Logs begin at mié 2014-10-15
reassign 765622 systemd,dracut
retitle 765622 Please support /usr being in a separate partition.
severity 765622 normal
thanks
On Thu, 16 Oct 2014, Krzysztof Sobiecki wrote:
> Package: base-files
> Version: 7.6
> Severity: minor
>
> Dear Maintainer,
>
> After switching to dracut from initramfs-
For people who look for error messages in search engines.
This bug seems to be the reason for log lines like this one:
systemd-tmpfiles[N]: Two or more conflicting lines for /var/cache/man
configured, ignoring.
The following command shows those conflicting lines:
$ grep /var/cache/man /usr
16 matches
Mail list logo
