Bug#893369: 893369

n you tell us if this works, and post the output? apt install systemd:amd64=238-2 -- Saludos, Felipe Sateler ___ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers

Bug#891836: systemd: systemctl start/stop/restart valid-template@invalid-instance doesn't cause errors

ecStart=-/usr/bin/pg_ctlcluster --skip-systemctl-redirect %i start If postgres would report the error back to systemd, it would at least tell you that. getty@.service suffers from the same issue. Other units do not: % sudo systemctl start systemd-nspawn@doe

Bug#890343: systemd: Debian could use the fq_codel network queuing algorithm by default

kernel policies, at least until it will become >the only supported init system. And it makes sense: why would some users get this but others don't? -- Saludos, Felipe Sateler ___ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers

Bug#887456: init-system-helpers: deb-systemd-helper does not honor the same package-relevant unit paths as systemd

symlink in such > a case and by prefering /usr/lib/systemd we'd avoid one indirection. > > Felipe, wdyt? I'm indifferent. I don't think there is much impact, but we still don't enable usrmerge by default... -- Saludos, Felipe Sateler __

Bug#887343: systemd-timesyncd does not start with DynamicUser=yes

Control: tags -1 patch fixed-upstream On Mon, Jan 15, 2018 at 10:42 AM, Felipe Sateler <fsate...@debian.org> wrote: > Control: forwarded -1 https://github.com/systemd/systemd/issues/7883 > > On Mon, Jan 15, 2018 at 8:57 AM, Martin Pitt <mp...@debian.org> wrote: >> >

Bug#887343: systemd-timesyncd does not start with DynamicUser=yes

hat either should be fixed, or systemd > needs > to raise libnss-systemd to a Depends: for that particular bug/reason. > It appears timesyncd wants to do this to support being run as root and then dropping privileges. However, this will fail in the DynamicUser=yes world because systemd-ti

Re: Bug#883407: libc6: getpwnam_r() leaks memory

gning the bug there. Normally this is not a problem since the mempool will live (and be reused) as long as the calling process. This is not true for nss modules, and thus I've forwarded this upstream. Unfortunately just defining VALGRIND also appears to disable some optimizations in the journal, so I don't think we can just enable it. -- Saludos, Felipe Sateler ___ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers

Bug#879771: init-system-helpers: update-rc.d falsly creates K-symlinks on installation which breaks switching init systems later

now. Next in the TODO: add some autopkgtests [1] https://anonscm.debian.org/git/collab-maint/init-system-helpers.git/commit/?id=7b4318cb2238c21dca86ab5e3bb4429309b4cf1b -- Saludos, Felipe Sateler ___ Pkg-systemd-maintainers mailing list Pkg-sys

Bug#802211: RFC: wip patch to force sulogin on locked root accounts

login will become necessary, then I think it makes more >sense to pass sulogin-shell's arguments to sulogin and use getenv() > to decide the label of the mode (rescue/emergency/potato), rather >than the other way around. > I don't have an opinion here. -- Saludos

Bug#878401: [systemd] Dependency on /tmp not correctly stated for some sound.target (or /tmp/pulse-* shows up underneath my /tmp mount)

/rules.d/90-alsa-restore.rules , and change the alsactl lines to add a new flag: /usr/sbin/alsactl -E HOME=/run/alsa -E PULSE_RUNTIME_PATH=/run/alsa/runtime restore $attr{device/number} (and the same for the nrestore command). -- Saludos, Felipe Sateler

Bug#878401: [systemd] Dependency on /tmp not correctly stated for some sound.target (or /tmp/pulse-* shows up underneath my /tmp mount)

upposed to be a systemd user service so this > doesn't really make sense. > > Is it possible that pulseaudio is started via other means which are not > under systemd's control? This might be caused by the alsa units. The pulse plugin might be attempting to connect to pulseaudio, but it

Bug#802211: RFC: wip patch to force sulogin on locked root accounts

usable in the (now default?) passwordless-root environments d-i generates is not very user friendly. So I think d-i should generate this snippet in /etc if the root account was not configured. -- Saludos, Felipe Sateler ___ Pkg-systemd-maintainers ma

Bug#878182: systemd: Should stop creating systemd-bus-proxy user

Package: systemd Version: 234-3 Severity: normal Systemd is still creating in postinst the systemd-bus-proxy user. That user is no longer used upstream as all kdbus code was removed. The user should no longer be created. It appears (but I haven't checked) that it is safe to remove the user on

Bug#857452: Steps towards a patch to document disabling a daemon upon installation

On Tue, Sep 12, 2017 at 9:49 AM, Ian Jackson <ijack...@chiark.greenend.org.uk> wrote: > Felipe Sateler writes ("Re: Steps towards a patch to document disabling a > daemon upon installation"): >> I suggest instead mentioning the real reasons its bad: > >

Bug#877414: systemd: please include a /var/log/README like Fedora has

le persistent journal by default either. Maybe these two defaults should be changed? I have no opinion on that. -- Saludos, Felipe Sateler ___ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.

Bug#873613: systemd gets confused at shutdown time

this patch affect the big problem (important services > being shut down too early)? > Which important service is being shutdown too early? portmap is stopped after nfs mounts are stopped (even though one failed to unmount). -- Saludos, Felipe Sateler ___

Bug#869719: udev-234 doesn't execute when udev architecture != systemd architecture

> I'm also not convinced if it's worth complicating the maintainers > scripts for such an exotic case. Well, udev can run arbitrary programs via RUN commands, is it right to assume that those will always be native? -- Saludos, Felipe Sateler ___ Pk

Bug#873613: systemd gets confused at shutdown time

On Fri, Sep 1, 2017 at 7:27 AM, Harald Dunkel <harald.dun...@aixigo.de> wrote: > On Wed, 30 Aug 2017 10:17:55 -0300 > Felipe Sateler <fsate...@debian.org> wrote: > >> On Wed, Aug 30, 2017 at 6:53 AM, Harald Dunkel <harald.dun...@aixigo.de> >> wrote: >

Bug#873789: init-system-helpers: autopkgtests broken in 1.49

On Thu, Aug 31, 2017 at 4:12 AM, Steve Langasek <steve.langa...@canonical.com> wrote: > Attached is a patch which fixes the tests to also correctly handle the > escape characters in the unit names. Thanks! Applied as b13d642. It will be part of the next upload. -- Saludos, Fe

Bug#873708: libsystemd-shared: symbol collisions

e a bug on heimdal for this issue? -- Saludos, Felipe Sateler ___ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers

Bug#873613: systemd gets confused at shutdown time

On Wed, Aug 30, 2017 at 6:53 AM, Harald Dunkel <harald.dun...@aixigo.de> wrote: > On Tue, 29 Aug 2017 11:17:03 -0300 > Felipe Sateler <fsate...@debian.org> wrote: > > > > Please attach the full configuration for your mount points. > > > > /proc/mounts

Bug#873628: systemd: Apparent regression on #825394, logind.conf accepts upstream default of KillUserProcesses=yes

making the change and rebooting my long running processes > are not terminated arbitrarily. TIA > This has already been fixed in git[1] but not yet uploaded. It should be part of the next upload. https://anonscm.debian.org/cgit/pkg-systemd/systemd.g

Bug#873613: systemd gets confused at shutdown time

rently it ignored NFS > completely. No wonder that it got stuck. > > Would you mind to check and fix for stretch? Could you attach full logs? Attaching the info generated by reportbug would be useful too. -- Saludos, Felipe Sateler

Bug#872598: udev-udeb: no input in graphical installer

e sure that new (and/or > deleted) files in the udev and libudev1 binaries are detected by > maintainers (esp. since udev.install uses wildcards for rules files, while > udev-udeb.rules uses a static list), so that the update can be propagated > to the udebs if relevant. --fail-missing is broke

Bug#872119: systemd: fdisk build-dependency needed (for tests)

that adding the dependency to that autopkgtest is enough. I have added this dependency in git. -- Saludos, Felipe Sateler ___ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers

Bug#870747: update-rc.d: enabling a default-disabled service fails: "foo Default-Start contains no runlevels, aborting."

codify policy, it should be a dumb mechanism to alter the symlink farm. I think the correct fix is #857452, plus changing your init script to have Default-start: 2 3 4 5. #857452: update-rc.d: please provide a defaults-disabled option -- Saludos, Felipe Sateler ___

Bug#870777: casync: Please migrate to openssl1.1 in Buster

On Sat, Aug 5, 2017 at 1:50 PM, Sebastian Andrzej Siewior <sebast...@breakpoint.cc> wrote: > On 2017-08-05 11:16:06 [-0400], Felipe Sateler wrote: >> Hi Sebastian, > Hi Felipe, > >> I still have the libssl1.0-dev fallback in order to be able to build >> in my

Bug#870777: casync: Please migrate to openssl1.1 in Buster

uilt in a fresh chroot. -- Saludos, Felipe Sateler ___ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers

Bug#869995: interface stays in "routable (configuring)", systemd-networkd-wait-online.service in failed state

an additional IPv6 address statically configured. > Does the problem go away if you remove all the static configuration? This may be related (but not the same as) upstream issue #6359 . https://github.com/systemd/systemd/issues/6359 -- Saludos, Felipe Sateler

Bug#869531: casync autopkgtest is broken in 1+65-2

blocker for > testing (which would be useful to help us improve the quality of the > release); but Ubuntu does, so FWIW this will block the new casync from > reaching the next Ubuntu release until fixed. Thanks, fixed in git. Will upload shortly. -- Saludos, Felipe Sateler

Bug#869140: casync FTBFS on mips64el: test-casync TIMEOUT

succeeded after 108.83 seconds, so this might > just require an increased timeout (untested). This test runs faster than test-camakebst on my amd64 machine, so there may be a real issue. -- Saludos, Felipe Sateler ___ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers

Bug#869134: casync: FTBFS: linux/magic.h: No such file or directory

wait until 869136 is fixed before uploading though. -- Saludos, Felipe Sateler ___ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers

Bug#869136: casync: FTBFS on sparc64: test suite bus error

on't have further details beyond what you can find at > https://buildd.debian.org/status/fetch.php?pkg=casync=sparc64=1%2B65-1=1500566201=0, > but perhaps you can reproduce the crash on a porterbox. > > Could you please take a look? Indeed, I have it on my todo list. -- Saludos, Fel

Bug#868980: ITP: casync -- content addressable data synchronizer

Package: wnpp Severity: wishlist Owner: Felipe Sateler <fsate...@debian.org> * Package name: casync Version : 1 Upstream Author : Lennart Poettering <lenn...@poettering.de> * URL : https://github.com/systemd/casync * License : LGPL-2.1 Program

Bug#868458: `systemctl status' output is ellipsised

sing: >udev > > It would be good to do what the hint in the output says, so we can see > what's going wrong from logs. Patch attached. > Thanks. I've applied your patch as 5836b30 . -- Saludos, Felipe Sateler ___ Pkg-systemd-main

Bug#867368: systemd-udevd: delays boot for 2+ minutes when LVM PV is inside a LV

nvenient > arrangement and I would hope it could be made to work without an excessive > boot delay. > Can you try booting with the old jessie kernel? This looks like a kernel regression. -- Saludos, Felipe Sateler ___ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers

Bug#860637: mkosi: FTBFS on i386: help2man: can't get `--help' info from ./mkosi

I'm downgrading to wishlist and retitling: it's probably a good idea to > keep a trace of this in the BTS to avoid additional bugs getting filed. This actually means mkosi is unusable in all but amd64 and arm64. Patching it to support creating non-image formats (directory and tar) is easy (just

Re: /usr/bin/dh_systemd_start: dh_systemd_start needs to start .socket before .service

the >.socket must be started before the .service. Otherwise it will cause >issues/confusion if an enduser starts the services manually. Yes, please add that. Otherwise the config is too brittle. -- Saludos, Felipe Sateler ___ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers

Bug#859855: systemd-container - machinectl fails to display list

t if one of the machines comes from > libvirt/qemu. This problem is fixed upstream. This was already filed as #849316 , where I posted a backported patch for testing. Could you test that please? -- Saludos, Felipe Sateler ___ Pkg-systemd-maintaine

Bug#859003: systemd-container: strange permissions on /dev/pts/ptmx

do that. In the host, /dev/ptmx has 0666 permissions. [1] https://www.kernel.org/doc/Documentation/filesystems/devpts.txt -- Saludos, Felipe Sateler ___ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers

Bug#858818: please consider implementing or at least documenting a headless-friendly emergency target

d to be the > case in the pre-systemd era, and I'd love to get this possibility back. I don't think this can work as long as ssh.service has `DefaultDependencies=yes`, because that implies `Requires=sysinit.target`, which is likely involved in the failure that resulted in the emergency target

Re: Bug#857132: console-setup: additional info needed ?

gt;/dev/null; then for i in /dev/vcs[0-9]*; do { : setfont '/etc/console-setup/cached_Lat15-Fixed16.psf.gz' } < /dev/tty${i#/dev/vcs} > /dev/tty${i#/dev/vcs} done fi Might it be that /dev/fb* do not exist during boot, and thus the font is not loaded in a

Re: piuparts.debian.org: jessie2bpo has >400 packages in dependency-failed-testing status

ersions. > > you cannot expect users to do the right thing by themselves ;-) There cannot be a dependency, as systemd can be used without udev (like on containers), and udev can be used without systemd. Since there are already Breaks/Replaces, and we can'

Bug#858335: systemd: should usr /run instead of /var/run

itself has moved over. I'm not familiar with SELinux, but this string you have reported is never used to create a file AFAICT. Systemd (sd-bus, actually) only uses this to attempt connecting to the system dbus daemon. Is it still a problem in this case? [1] https://bugs.debian.org/cgi-bin/b

Bug#857743: installation-report: Jessie stable ++ all Backports cause kernel-panic on HP EliteBook 8440p

On Tue, 14 Mar 2017 17:05:48 +0100 Andreas Glaeser wrote: > So the root-filesystem looks like this: > > > drwxr-xr-x 2 root root 4096 Mar 14 16:02 bin > > drwxr-xr-x 3 root root 4096 Mar 14 16:32 boot > > drwxr-xr-x 20 root root 3520 Mar 14 16:35 dev > >

Bug#857306: debhelper: merge dh_systemd_enable and dh_systemd_install

Package: debhelper Version: 10.2.5 Severity: wishlist Hi, >From what I can tell, dh_systemd_enable was a separate command that needed to run before dh_installinit because dh_installinit looked at .service and .tmpfiles. Since compat 11 this is no longer the case, so dh_systemd_{enable,start}

Bug#856985: systemd: Uninstalling systemd-cron hangs/crashes systemd

g commit here: https://github.com/systemd/systemd/commit/47fffb35 Unfortunately, that does not apply cleanly to 215, so some backporting will be needed. -- Saludos, Felipe Sateler ___ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@list

Bug#850855: [rtkit] rtkit daemon fails to start

On Sun, Mar 5, 2017 at 9:01 PM, Michael Biebl <bi...@debian.org> wrote: > On Fri, 20 Jan 2017 11:38:54 -0300 Felipe Sateler <fsate...@debian.org> > wrote: >> Control: tags -1 - unreproducible moreinfo >> Control: reassign -1 systemd >> Control: affects -

Bug#856924: systemd: on WorkingDirectory not existing, some weird log about CHROOT is generated

/sh is not found, when actually the issue is that > WorkingDirectory doesn't exist. > > Perhaps a log message related to the actual error would be of more use. This was improved in 233: test.service: Failed at step CHDIR spawning /bin/sh: No such

Re: [Install] for static systemd unit file?

On Wed, Mar 1, 2017 at 11:39 PM, Patrick Schleizer <patrick-mailingli...@whonix.org> wrote: > Felipe Sateler: >> On Wed, Mar 1, 2017 at 9:50 PM, Patrick Schleizer >> <patrick-mailingli...@whonix.org> wrote: >>> Felipe Sateler: >>>> On Wed, Mar 1,

Re: [Install] for static systemd unit file?

On Wed, Mar 1, 2017 at 9:50 PM, Patrick Schleizer <patrick-mailingli...@whonix.org> wrote: > Felipe Sateler: >> On Wed, Mar 1, 2017 at 5:51 PM, Patrick Schleizer >> <patrick-mailingli...@whonix.org> wrote: >>> Michael Biebl: >>>> Am 01.03.2

Re: [Install] for static systemd unit file?

On Wed, Mar 1, 2017 at 7:40 PM, Felipe Sateler <fsate...@debian.org> wrote: > On Wed, Mar 1, 2017 at 5:51 PM, Patrick Schleizer > <patrick-mailingli...@whonix.org> wrote: >> Michael Biebl: >>> Am 01.03.2017 um 21:35 schrieb Patrick Schleizer: >>>

Re: [Install] for static systemd unit file?

ositive, and can be safely ignored. If not, just add the install section. This warning was introduced in #832771. As I argued in that bug, there are plenty of reasons one wouldn't want to have a service enabled on its own. Some were fixed in #837057, but not all. -- Saludos, Felipe Sateler __

Bug#787028: systemd-cryptsetup@.service fails, although encrypted swap is enabled nevertheless

Control: forwarded -1 https://github.com/systemd/systemd/pull/5480 On Thu, 28 May 2015 00:25:49 +0200 Roland Hieber wrote: > Package: systemd > Version: 219-10 > Severity: normal > > Dear Maintainers, > > I have now the situation that sometimes /dev/mapper/cryptswap is

Bug#856265: systemd-journald: RuntimeMaxUse is not properly obeyed

ot refer to RSS, but rather to the "disk" space used in /run when the persistent journal is not active. So this flag does not control what you want. AFAIK, there is no way to control max memory usage. -- Saludos, Felipe Sateler ___ Pkg-systemd-mai

Bug#854041: getting past this issue

On Thu, Feb 16, 2017 at 8:42 AM, Daniel Pocock <dan...@pocock.pro> wrote: > > I tried: > > dpkg -i --force-breaks /var/cache/apt/archives/systemd_232-15_amd64.deb What breaks did dpkg tell you it had to ignore? -- Saludos, Felipe Sateler _

Bug#855209: systemd ignores configuration for getty when switching and autostarting a new vt

ing but not fixed yet. In the meantime, you should be able to fix the issue via `ln -s getty@tty6.service /etc/systemd/system/autovt@tty6.service` -- Saludos, Felipe Sateler ___ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debi

Re: schroot: please provide a systemd service file

is the last LSB initscript without equivalent that > requires the $network facility, in some situation, this makes the boot stall > for around 20s (as it waits for the network to come online). Could it still > be an option to add that for stretch? > As an interested user, thanks f

Bug#854102: systemd-logind fails to update session's Display property after `startx` from VT

settable at session creation time. I don't know if this is deliberate or not. -- Saludos, Felipe Sateler ___ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers

Bug#854041: systemd: dpkg fails for systemd package when upgrading from jessie to stretch

systemd while running under it is a bad idea[1]. Dear apt maintainers, any idea on what conditions could result in apt deciding to temporarily remove systemd? [1] https://sources.debian.net/src/systemd/232-15/debian/systemd.prerm/#L10 -- Saludos, Felipe Sateler

Bug#852811: marked as done (udev: Doesn't start after upgrade powerpc)

gt;> Still the same : > > The error code is different. > >> | Jan 27 15:38:52 fabian.marillat.net systemd[1]: systemd-udevd.service: >> Main process exited, code=exited, status=228/SECCOMP > > IIRC MemoryDenyWriteExecute= uses seccomp as

Bug#852811: udev: Doesn't start after upgrade powerpc

On Fri, 27 Jan 2017 15:16:57 +0100 m...@linux.it (Marco d'Itri) wrote: > On Jan 27, Christian Marillat wrote: > > > Maybe the problem is because / is a RAID0 ? > > > > Setting up udev (232-14) ... > No. This is the problem: > > > addgroup: The group `input' already exists as a

Re: Bug#850211: open-iscsi: Boot with systemd hangs for iSCSI+LUKS+LVM volume

le ago upstream, but it has not been fixed yet. -- Saludos, Felipe Sateler ___ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers

Re: Bug#850855: [rtkit] rtkit daemon fails to start

A related issue is https://github.com/systemd/systemd/issues/3867 , but that is supposedly fixed in 232. BogDan, do you have version 232 installed? It may be that the issue is not fully fixed yet. -- Saludos, Felipe Sateler ___ Pkg-systemd-maintainers

Re: Bug#851747: sysvinit-utils: unmaintained package should not be Essential

also has a pidof implementation, so we could switch to that. Andreas Henriksson + Craig Small have done some analysis at #810018 -- Saludos, Felipe Sateler ___ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org http://l

Bug#851730: init-system-helpers: update-rc.d fails to disable nbd-server

, both the systemd sysv-generator and insserv have such a relaxed parsing: https://sources.debian.net/src/systemd/232-10/src/sysv-generator/sysv-generator.c/#L495 https://sources.debian.net/src/insserv/1.14.0-5.4/insserv.c/#L1309 I'm inclined to make update-rc.d agree with insserv and systemd; opinio

Bug#851253: bootstrap build failure: install: cannot stat 'build-deb/.libs/test-udev': No such file or directory

he binary objects in .libs? Dear libtool maintainers, do you have any idea? > > Reverting systemd packaging commit > 943053a2c2fd8b153545eb410101e0e3616d4de9 makes the issue go away. https://anonscm.debian.org/cgit/pkg-systemd/systemd.git/commit/?id=943053a2c2fd8b153545eb410101e0e3616d4de9

Bug#846944: Installing libnss-resolve before libnss-mdns breaks mDNS name resolution

t, improve the man pages of the three NSS modules in other ways a bit. So I guess we just failed to update usage with upstream? -- Saludos, Felipe Sateler ___ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers

Bug#851253: bootstrap build failure: install: cannot stat 'build-deb/.libs/test-udev': No such file or directory

ot cause will be more fruitful. > This smells like a bug in libtool. Indeed. -- Saludos, Felipe Sateler ___ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers

Re: Migration from sysvinit to systemd: reboot fails to complete

Control: severity -1 serious Control: tags -1 - patch On 31 December 2016 at 08:30, Francesco Poli <invernom...@paranoici.org> wrote: > On Fri, 30 Dec 2016 22:21:32 +0100 Michael Biebl wrote: > >> Am 30.12.2016 um 22:16 schrieb Felipe Sateler: > [...] >> > But, your

Re: Migration from sysvinit to systemd: reboot fails to complete

On 30 December 2016 at 15:01, Francesco Poli <invernom...@paranoici.org> wrote: > On Fri, 30 Dec 2016 14:15:17 -0300 Felipe Sateler wrote: > >> Hi Francesco, > > Hello Felipe, > first off, thanks for your prompt reply! > >> >> On 30 December 2016 at 13:08,

Bug#849316: machinctl: fails to list anything if a libvirt qemu container is running

On 29 December 2016 at 14:54, Felipe Sateler <fsate...@debian.org> wrote: > On 26 December 2016 at 06:18, Michael Biebl <bi...@debian.org> wrote: >> >> Am 25.12.2016 um 22:32 schrieb Felipe Sateler: >> > PR 4978 was closed in favor of 4972. However, it has

Re: Migration from sysvinit to systemd: reboot fails to complete

ystem!) and no serious damage was apparently done. > > Nonetheless, the procedure does not seem to work cleanly. > > Is there a way to cleanly shutdown a box running sysvinit as PID 1, > immediately after the installation of package systemd-sysv, and > the mandatory simultaneous removal of sy

Bug#849316: machinctl: fails to list anything if a libvirt qemu container is running

On 26 December 2016 at 06:18, Michael Biebl <bi...@debian.org> wrote: > > Am 25.12.2016 um 22:32 schrieb Felipe Sateler: > > PR 4978 was closed in favor of 4972. However, it has not been merged > > yet. The patch is small so at least I don't have a problem with > > b

Bug#849316: machinctl: fails to list anything if a libvirt qemu container is running

es. > PR 4978 was closed in favor of 4972. However, it has not been merged yet. The patch is small so at least I don't have a problem with backporting. However, we prefer patches to be merged upstream, so we'll wait until the PR is merged. Feel free to ping again if the PR is merged and ther

Bug#801822: deb-systemd-helper does not support template units (e.g. foo@.service)

Control: tags -1 confirmed On Wed, 14 Oct 2015 19:28:25 -0300 Antonio Terceiro wrote: > Package: init-system-helpers > Version: 1.24 > Severity: normal > > `deb-systemd-helper enable foo@1.service` will not work even if the > corresponding foo@.service is correctly in place.

Bug#777125: sysvinit-utils: service cmd with systemd shows, but did not stop duplicate instances of nslcd

Control: reassign -1 nslcd 0.9.4-3 On Thu, 05 Feb 2015 11:15:32 +0100 Hermann Lauer wrote: > Package: sysvinit-utils > Version: 2.88dsf-58 > Severity: normal > > Dear Maintainer, > > during some "service {start,stop,restart,status} nslcd" usage > there are

Bug#780522: init-system-helpers: deb-systemd-helper doesn't handle drop-ins and is inconsistent w/ systemd w.r.t. lists

Control: tags -1 moreinfo Hi Christian, On Sun, 15 Mar 2015 15:23:38 +0100 Christian Seiler wrote: > Package: init-system-helpers > Version: 1.22 > Severity: important > Tags: patch > > Dear Maintainers, > > deb-systemd-helper doesn't handle drop-ins at all (only the main >

Bug#843761: invoke-rc.d: Kill 600 birds with one stone (a.k.a. automatic policy-rc.d for init-less chroots)

Control: tags -1 pending On 20 December 2016 at 21:52, Michael Biebl <bi...@debian.org> wrote: > Am 21.12.2016 um 01:29 schrieb Felipe Sateler: > >> Michael, from the discussion on IRC I did not end up entirely clear if >> you are OK with this change or not. Could you plea

Bug#780028: init: aptitude upgrade from wheezy to jessie does not install systemd-sysv

On 20 December 2016 at 23:13, Paul Wise <p...@debian.org> wrote: > Control: reopen -1 > > On Tue, 2016-12-20 at 19:55 -0300, Felipe Sateler wrote: > >> Unfortunately, I think the ship to fix this has sailed, as jessie was >> released a while ago already.

Bug#788253: gfsd: unowned files after purge (policy 6.8, 10.8): /var/lib/systemd/deb-systemd-helper-masked/gfsd.service

Control: reassign -1 gfsd 2.6.4.1+dfsg-1 On Wed, 24 Jun 2015 17:52:58 +1000 Dmitry Smirnov wrote: > Control: reassign -1 dh-systemd 1.23 > > On Fri, 12 Jun 2015 08:32:04 Dmitry Smirnov wrote: > > On Thu, 11 Jun 2015 15:56:20 Andreas Beckmann wrote: > > > maybe the manual rm

Bug#843761: invoke-rc.d: Kill 600 birds with one stone (a.k.a. automatic policy-rc.d for init-less chroots)

On Thu, 10 Nov 2016 09:15:40 +0100 Martin Pitt wrote: > Hello Andreas, > > Andreas Henriksson [2016-11-09 11:08 +0100]: > > As discussed on IRC we seem to agree that an init-less chroot which does > > not have a policy-rc.d blocking service actions isn't a sane > >

Bug#728682: Patch

Control: tags -1 pending On Sat, 10 Dec 2016 21:36:33 +0100 Christian Hofstaedtler wrote: > Control: tags -1 + patch > > Proposed patch attached. Thanks. I have applied the patch. I also find "just in case warnings" quite useless. Saludos,

Bug#845185: init-system-helpers: deb-system-invoke starts disabled systemd service on package install/upgrade (backport request)

Hi Yury On 1 December 2016 at 10:06, Felipe Sateler <fsate...@debian.org> wrote: > On 1 December 2016 at 09:17, Yury V. Zaytsev <y...@shurup.com> wrote: >> On Wed, 30 Nov 2016, Felipe Sateler wrote: >> >>>> I'm filing this bug as discussed on #debian-syst

Bug#832351: init-system-helpers: purging gdm3/lightdm/sddm/xdm leaves dangling /etc/systemd/system/display-manager.service symlink

Control: clone -1 -2 Control: reassign -1 xdm 1:1.1.11-3 Control: reassign -2 sddm 0.13.0-1 On Sun, 24 Jul 2016 15:54:55 +0200 Michael Biebl wrote: > Am 24.07.2016 um 15:49 schrieb Andreas Beckmann: > > Package: init-system-helpers > > Version: 1.22 > > Severity: important > >

Bug#769895: init-system-helpers: deb-systemd-helper should remove timestamps on timer unit purge

Control: forwarded -1 https://github.com/systemd/systemd/issues/4930 On Mon, 17 Nov 2014 12:46:38 +0100 Alexandre Detiste wrote: > Package: init-system-helpers > Version: 1.21 > Severity: minor > > Dear Maintainer, > > When a timer unit with flag "Persistant=true" is

Re: Bug#805878: dh-systemd: dh_systemd_start --no-start --restart-after-upgrade causes the service to be started on install

Hi, On 9 October 2016 at 17:26, Felipe Sateler <fsate...@debian.org> wrote: > Control: tags -1 patch > > On 23 November 2015 at 11:34, Felipe Sateler <fsate...@debian.org> wrote: >> Package: dh-systemd >> Version: 1.24 >> Severity: normal >> >>

Re: How to install and enable timer units in a package?

On 13 December 2016 at 15:16, Gioele Barabucci <gio...@svario.it> wrote: > On 13/12/2016 13:58, Felipe Sateler wrote: >> On 12 December 2016 at 17:40, Gioele Barabucci <gio...@svario.it> wrote: >>> My open question now is: how does one enable/start the installed ti

Re: How to install and enable timer units in a package?

I can use? You should just use dh_systemd_enable/dh_systemd_start. If you are using short-form dh, passing --with systemd will do the trick in compat <=9, compat >= 10 enables the systemd sequence by default. -- Saludos, Felipe Sateler ___ Pkg-s

Bug#847203: systemd: journalctl zsh completion fails with RC_QUOTES

On 7 December 2016 at 13:57, Vincent Lefevre <vinc...@vinc17.net> wrote: > > On 2016-12-07 10:28:45 -0300, Felipe Sateler wrote: > > Hi ZSH Maintainers, > > Not sure they are reading (or have they been Bcc'ed?), Ooops, I forgot to add the CC. > but I started > a thr

Bug#847203: systemd: journalctl zsh completion fails with RC_QUOTES

completions) worked. Yet it didn't. On 6 December 2016 at 12:02, Vincent Lefevre <vinc...@vinc17.net> wrote: > On 2016-12-06 11:40:35 -0300, Felipe Sateler wrote: >> I think the better fix is to somehow make zsh use default option >> values when evaluating the completion funct

Bug#847203: systemd: journalctl zsh completion fails with RC_QUOTES

e:_files' \ > > At least, this is equivalent without RC_QUOTES. > I've attached the corresponding patch. I think the better fix is to somehow make zsh use default option values when evaluating the completion functions. I see that some completions use `emulate -LR zsh

Re: Next stable upload for 8.7

fix exists), please let me know. > > The current list of issues is at [1]. I currently plan to address > #839607 > #774153 > #788050 > #833849 > and eventually > #818978 Not sure if it's worth looking fixing, but there is also #823577 - if not worth fixing, it shoul

Bug#845185: init-system-helpers: deb-system-invoke starts disabled systemd service on package install/upgrade (backport request)

On 1 December 2016 at 09:17, Yury V. Zaytsev <y...@shurup.com> wrote: > On Wed, 30 Nov 2016, Felipe Sateler wrote: > >>> I'm filing this bug as discussed on #debian-systemd, requesting to kindly >>> backport the relevant commit and push the new package

Bug#846377: [systemd] /lib/systemd/systemd --user starts dbus-daemon without AFS token

On 30 November 2016 at 20:39, Russ Allbery <r...@debian.org> wrote: > Felipe Sateler <fsate...@debian.org> writes: >> On 30 November 2016 at 19:20, Michael Biebl <bi...@debian.org> wrote: >>> Am 30.11.2016 um 23:12 schrieb Russ Allbery: > >&g

Bug#845185: init-system-helpers: deb-system-invoke starts disabled systemd service on package install/upgrade (backport request)

fix would be incomplete without addressing #768450 too. Unfortunately, this means also an update of src:sysvinit (as invoke-rc.d was moved to i-s-h post-jessie) is needed but I don't really want to touch that... -- Saludos, Felipe Sateler ___ Pkg-sy

Bug#846377: [systemd] /lib/systemd/systemd --user starts dbus-daemon without AFS token

e more appropriate if this variable should be copied from an already existing environment. -- Saludos, Felipe Sateler ___ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers

Bug#846377: [systemd] /lib/systemd/systemd --user starts dbus-daemon without AFS token

ibility to the Kerberos ticket cache). systemd --user does open a pam session (with the systemd-user name). Maybe the problem is that libpam-afs-session (is this the right module?) registers itself in the common-session include file but systemd-user loads only common-s

Bug#845302: systemd: 232-6:Failed to boot, makes kernel panic when starting /sbin/init.

re filesystems are a SSD and HDD.(Will replace HDD to > another SSD) > SSD: ADATA 240GiB (/dev/sde) > HDD: Toshiba 3TiB (/dev/sdd) > Partition type of both disks are GPT. > > Partition structure: > / : sdd3, #8300, EXT4, 30GiB > /boot : sde2, #8300, EXT4, 7.9Gib

Bug#844785: systemd prevents polkit from working properly

is not working for 232. I'm reassigning so that it can be fixed. -- Saludos, Felipe Sateler ___ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers

  1   2   3   >