Re: Switching packages to non-awaiting triggers

2013-05-16 Thread Charles Plessy
Hello everybody, For those interested in learning more about triggers, including the noawait forms, which Guillem reminded us that they should be the ones to use in most of the cases, I recommend to have a look to the patch in preparation for the Debian Policy.

Re: Switching packages to non-awaiting triggers

2013-05-08 Thread Raphael Hertzog
Hi Guillem, On Tue, 07 May 2013, Guillem Jover wrote: Examples of this are man pages (#707129) or info documents (#707133), others could be menu, desktop or dictionary triggers, but that depends on how the triggering packages make use of them. I'd be glad if people who know any package

Re: Switching packages to non-awaiting triggers

2013-05-08 Thread Julien Cristau
On Wed, May 8, 2013 at 10:37:00 +0200, Raphael Hertzog wrote: python-support (will go away anyway) Seems fairly unlikely that it will, actually, with 758 reverse build deps in sid as far as I can tell. Cheers, Julien signature.asc Description: Digital signature

Re: Switching packages to non-awaiting triggers

2013-05-08 Thread Jakub Wilk
* Raphael Hertzog hert...@debian.org, 2013-05-08, 10:37: python-support (will go away anyway) #629154 (don't pay attention to the current bug subject) -- Jakub Wilk -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact

Switching packages to non-awaiting triggers

2013-05-07 Thread Guillem Jover
Hi! To be able to fix dpkg bug #671711, we should first reduce or completely eliminate the possibilty for triggered packages needing its configured dependencies, not ending up being in triggers-awaited status awaiting on them. For packages installing triggers for things that are not necessary

Re: Switching packages to non-awaiting triggers

2013-05-07 Thread Игорь Пашев
Hi, I think I know one more issue related to this, correct me if it is not. This might be a problem for systemd, but I will talk about SMF [1] and concrete example - dbus. 1. dbus package includes SMF manifest 2. for dbus service to appear, its manifest should be imported 3. importing manifests

Re: Switching packages to non-awaiting triggers

2013-05-07 Thread Michael Biebl
Am 2013-05-07 21:09, schrieb Игорь Пашев: This might be a problem for systemd, but I will talk about SMF [1] and concrete example - dbus. 1. dbus package includes SMF manifest 2. for dbus service to appear, its manifest should be imported 3. importing manifests if done via triggers (AFAIK like

Re: Switching packages to non-awaiting triggers

2013-05-07 Thread Игорь Пашев
2013/5/7 Michael Biebl bi...@debian.org: We don't use dpkg triggers to start (systemd) services. Hm? http://anonscm.debian.org/gitweb/?p=pkg-systemd/systemd.git;a=blob;f=debian/systemd.triggers;h=f6c3c0ce0da08815f366868d3b3a3f9e5907875f;hb=refs/heads/debian -- To UNSUBSCRIBE, email to

Re: Switching packages to non-awaiting triggers

2013-05-07 Thread Michael Biebl
Am 2013-05-07 21:40, schrieb Игорь Пашев: 2013/5/7 Michael Biebl bi...@debian.org: We don't use dpkg triggers to start (systemd) services. Hm?

Re: Switching packages to non-awaiting triggers

2013-05-07 Thread Игорь Пашев
2013/5/7 Michael Biebl bi...@debian.org: If you actually looked at the package, you would have noticed that it has nothing to do with starting services. Maybe, systemctl enable does not start the service? Main question is: can triggers be activated before package is configured (namely