Le Fri, Aug 16, 2013 at 10:10:51AM +0900, Charles Plessy a écrit :
Le Sun, Aug 04, 2013 at 09:14:09AM +0900, Charles Plessy a écrit :
Le Sat, Aug 03, 2013 at 09:41:59AM -0700, Jonathan Nieder a écrit :
If I end up with time to work on it, what I would probably do is to
split the patch
Le Sun, Aug 04, 2013 at 09:14:09AM +0900, Charles Plessy a écrit :
Le Sat, Aug 03, 2013 at 09:41:59AM -0700, Jonathan Nieder a écrit :
If I end up with time to work on it, what I would probably do is to
split the patch into smaller changes that can be considered and
applied
Le Thu, Jul 25, 2013 at 08:00:55AM +0900, Charles Plessy a écrit :
does the current patch (attached) address your concerns ? If yes, would
you second it ?
Hi all,
I would like to make one more call for feedback.
Needless to say, I am annoyed that despite we had mutiple persons who
On Thu, Jul 25, 2013 at 08:00:55 +0900, Charles Plessy wrote:
does the current patch (attached) address your concerns ? If yes, would
you second it ?
Sorry, I don't feel confident to second anything trigger-related.
Cheers,
Julien
signature.asc
Description: Digital signature
Charles Plessy wrote:
Le Thu, Jul 25, 2013 at 08:00:55AM +0900, Charles Plessy a écrit :
does the current patch (attached) address your concerns ? If yes, would
you second it ?
Hi all,
I would like to make one more call for feedback.
Sorry for the long silence.
My feeling is that the
Le Sat, Aug 03, 2013 at 09:41:59AM -0700, Jonathan Nieder a écrit :
If I end up with time to work on it, what I would probably do is to
split the patch into smaller changes that can be considered and
applied independently, which would hopefully be less intimidating for
area experts to
On Wed, Jul 17, 2013 at 09:27:19 +0200, Raphael Hertzog wrote:
Hi,
On Wed, 17 Jul 2013, Charles Plessy wrote:
About the problem of triggers being called with Depends not satisfied, can
you
give more explanations or suggest some text for the warning ? Would it be
enough to add a
Le Wed, Jul 24, 2013 at 03:58:04PM +0200, Julien Cristau a écrit :
On Wed, Jul 17, 2013 at 09:27:19 +0200, Raphael Hertzog wrote:
On Wed, 17 Jul 2013, Charles Plessy wrote:
About the problem of triggers being called with Depends not satisfied,
can you
give more explanations or
On Mon, 22 Jul 2013, Charles Plessy wrote:
Nevertheless, please let me try to refocus on the question of whether
the Policy can be updated or not.
I believe we can update the policy whatever the status of this specific
bug.
Here is what is written in the Policy about postinst configure:
Le Mon, Jul 22, 2013 at 09:00:59AM +0200, Raphael Hertzog a écrit :
I believe we can update the policy whatever the status of this specific
bug.
You're missing the important sentence that follows: “If there are no
circular dependencies involved, all package dependencies will be
On Sat, 20 Jul 2013, Charles Plessy wrote:
Can you explain what the bug is and what the correction will be ? Because I
The bug is that triggers are run while the dependencies of the triggered
package are not satisfied. The fix is not to do that and wait until those
dependencies are satisfied
Le Sun, Jul 21, 2013 at 09:36:52PM +0200, Raphael Hertzog a écrit :
There are no restrictions for postinst configure (you can rely on
dependencies — except if you have a dependency cycle) and there should be
no restrictions for postinst triggered. But right now, dpkg doesn't
ensure anything.
Thanks again Raphaël for your prompt feedback.
Le Thu, Jul 18, 2013 at 09:00:44AM +0200, Raphael Hertzog a écrit :
On Thu, 18 Jul 2013, Charles Plessy wrote:
- postinst configure should do at least everything needed by
postinst triggers, since in the situations where triggers are
On Thu, 18 Jul 2013, Charles Plessy wrote:
Le Thu, Jul 18, 2013 at 08:55:20AM +0900, Charles Plessy a écrit :
regarding “noawait” triggers, the patch already contains the following,
which
is new and improved compared to the existing documentation.
The tt*-noawait/tt directives
Hi,
On Thu, 18 Jul 2013, Charles Plessy wrote:
After reading #671711 and /usr/share/doc/dpkg-dev/triggers.txt.gz, my
impression is that a package can not become Unpacked and keep a list of
pending triggers, because of the following statements in triggers.txt:
1) Pending triggers are marked
Le Wed, Jul 17, 2013 at 09:27:19AM +0200, Raphael Hertzog a écrit :
Julien is referring to this bug:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=671711
It might be fixed for jessie, at least I hope so, but he seems to doubt
it.
Also, if you think that triggers will give us
Le Thu, Jul 18, 2013 at 08:55:20AM +0900, Charles Plessy a écrit :
2) The section Details - triggered package mentions that packages in
‘config-failed’ or worse are never considered to have lists of pending
triggers. (Where config-failed means Half-Installed). In my
understanding
On Thu, Jul 4, 2013 at 11:26:01 +0900, Charles Plessy wrote:
Le Sun, May 12, 2013 at 10:09:17AM +0200, Raphael Hertzog a écrit :
On Sun, 12 May 2013, Charles Plessy wrote:
I also added through the ttinterst/tt or ttactivate/tt
directives
after When a configured package activates
Le Tue, Jul 16, 2013 at 05:09:08PM +0200, Julien Cristau a écrit :
On Thu, Jul 4, 2013 at 11:26:01 +0900, Charles Plessy wrote:
http://bugs.debian.org/cgi-bin/bugreport.cgi?msg=87;filename=policy-triggers.diff;att=1;bug=582109
That patch has a bunch of typos (I noticed a few in
tag 582109 patch
thanks
Le Thu, Jul 04, 2013 at 11:26:01AM +0900, Charles Plessy a écrit :
now that Wheezy is released, I hope that everybody has more time to review the
patch to integrate triggers in the Policy and confirm Raphaël's seconding or
propose extra corrections or improvements.
Processing commands for cont...@bugs.debian.org:
tag 582109 patch
Bug #582109 [debian-policy] debian-policy: document triggers where appropriate
Added tag(s) patch.
thanks
Stopping processing here.
Please contact me if you need assistance.
--
582109:
Le Sun, May 12, 2013 at 10:09:17AM +0200, Raphael Hertzog a écrit :
On Sun, 12 May 2013, Charles Plessy wrote:
I also added through the ttinterst/tt or ttactivate/tt directives
after When a configured package activates a trigger.
I applied the other changes you proposed as well, with
Hi,
On Thu, 16 May 2013, Charles Plessy wrote:
Guillem recently posted on debian-devel about noawait triggers, and I would
like to send a link to the patch to the Policy once it gets futher
proof-reading and seconds. Or if it takes time, shall I point to this bug log
on -devel ?
I don't see
Le Wed, Apr 10, 2013 at 12:07:19PM +0200, Raphael Hertzog a écrit :
Here are my comments. There's quite a bit of work left.
Thanks a lot Raphaël and everybody !
I think that I took care of all of your comments.
Here is an updated patch. Among the changes, it introduces
sub-section to make
Hi Charles,
On Sat, 11 May 2013, Charles Plessy wrote:
I think that I took care of all of your comments.
Here is an updated patch. Among the changes, it introduces
sub-section to make the information easier to digest.
Thank you for the work! I have a few fixes and suggestions but otherwise
Hi Raphaël,
thanks for the quick feedback.
In the list of directives, I have moved the noawait variant on top to
better show that they are the default choice. I also reworded your suggestion
to make it a positive recommenation: use interest and activate only
if you want to put the triggering
Hi Charles,
On Fri, 15 Mar 2013, Charles Plessy wrote:
I am still seeking comments for the attached patch, that describes Dpkg
triggers.
Here are my comments. There's quite a bit of work left.
From 6a7fd0e49cb8dbd025771feb95c2dcafb408c1b8 Mon Sep 17 00:00:00 2001
From: Charles Plessy
On 10-04-13 12:07, Raphael Hertzog wrote:
“prgndpkg/prgn triggers allows packages to monitor events caused by
It should be allow here, not allows, since the subject (triggers)
of this sentence is in plural form.
[...]
+ whitespace, everything after the first hash character (tt#/tt)
hat class=native-en_GB-speaker
On 10/04/13 11:24, Wouter Verhelst wrote:
On 10-04-13 12:07, Raphael Hertzog wrote:
+ whitespace, everything after the first hash character (tt#/tt)
whitespaces ? (with s)
No, absolutely not. The word whitespace does not have a plural form,
since it is
On 10-04-13 12:37, Simon McVittie wrote:
hat class=native-en_GB-speaker
On 10/04/13 11:24, Wouter Verhelst wrote:
On 10-04-13 12:07, Raphael Hertzog wrote:
+whitespace, everything after the first hash character (tt#/tt)
whitespaces ? (with s)
No, absolutely not. The word whitespace
On Wed, 10 Apr 2013, Simon McVittie wrote:
hat class=native-en_GB-speaker
I've mostly seen whitespace used as a mass noun, like water or
sand: you can say whitespace is ignored or a sequence of
whitespace, but not a whitespace or whitespaces, in the same
way that it's correct to say some
On 10-04-13 18:19, Don Armstrong wrote:
On Wed, 10 Apr 2013, Simon McVittie wrote:
hat class=native-en_GB-speaker
I've mostly seen whitespace used as a mass noun, like water or
sand: you can say whitespace is ignored or a sequence of
whitespace, but not a whitespace or whitespaces, in the
Raphael Hertzog hert...@debian.org writes:
On Fri, 15 Mar 2013, Charles Plessy wrote:
+ Dpkg defines the folowing states for the packages.
+ taglist
+tagNot-Installed/tag
I would use the precise states listed in dpkg(1), i.e. entirely in
lowercase. (same for all the
On Wed, 10 Apr 2013, Russ Allbery wrote:
Raphael Hertzog hert...@debian.org writes:
On Fri, 15 Mar 2013, Charles Plessy wrote:
+Dpkg defines the folowing states for the packages.
+taglist
+ tagNot-Installed/tag
I would use the precise states listed in dpkg(1), i.e.
On Fri, 15 Mar 2013, Charles Plessy wrote:
+ Dpkg defines the folowing states for the packages.
+ taglist
+tagNot-Installed/tag
s/folowing/following
Cheers,
--
Bill. ballo...@debian.org
Imagine a large red swirl here.
--
To UNSUBSCRIBE, email to
Le Fri, Mar 15, 2013 at 04:11:19AM +0100, Guillem Jover a écrit :
On Fri, 2013-03-15 at 08:37:25 +0900, Charles Plessy wrote:
I am still seeking comments for the attached patch, that describes Dpkg
triggers.
I've not yet allocated a chunk of time to take a look into this, will
try to do
Hello everybody,
I am still seeking comments for the attached patch, that describes Dpkg
triggers.
Have a nice day,
--
Charles
From 6a7fd0e49cb8dbd025771feb95c2dcafb408c1b8 Mon Sep 17 00:00:00 2001
From: Charles Plessy ple...@debian.org
Date: Sat, 2 Mar 2013 22:48:04 +0900
Subject: [PATCH]
Hi Guillem,
thank you for your comments (some quoted below).
Le Sat, Mar 02, 2013 at 03:37:36PM +0100, Guillem Jover a écrit :
This is documented in the dpkg man page (PACKAGE STATES), sorry for
not mentioning this before.
We unified the states in policy to be all capitalized some time
Le Sun, Feb 24, 2013 at 04:41:55PM +0900, Charles Plessy a écrit :
I am having a look at how to document triggers. In order to simplify the
explanation and re-use more easily material from the file above, I think
that we would benefit from documenting the dpkg states for a package.
How
Dear all,
pasting a lot from /usr/share/doc/dpkg-dev/triggers.txt.gz and deb-triggers(1),
I have drafted a patch to the Policy to document triggers.
Your comments are very welcome.
Have a nice week-end,
--
Charles
From 04f094a0bfa98643ccead594be9d880439eae0b8 Mon Sep 17 00:00:00 2001
From:
Hi!
On Sat, 2013-03-02 at 18:45:30 +0900, Charles Plessy wrote:
Le Sun, Feb 24, 2013 at 04:41:55PM +0900, Charles Plessy a écrit :
I am having a look at how to document triggers. In order to simplify the
explanation and re-use more easily material from the file above, I think
that we
Le Tue, May 18, 2010 at 02:50:02PM +0200, Raphaël Hertzog a écrit :
The policy needs to be updated to take into account the dpkg triggers. At
the very least it needs to document the new invocations of the postinst in
chapter 6 (postinst triggered ...) see
Package: debian-policy
Version: 3.8.4.0
Severity: normal
The policy needs to be updated to take into account the dpkg triggers. At
the very least it needs to document the new invocations of the postinst in
chapter 6 (postinst triggered ...) see
/usr/share/doc/dpkg-dev/triggers.txt.gz
-- System
On Tue, May 18, 2010 at 02:50:02PM +0200, Raphaël Hertzog wrote:
Package: debian-policy
Version: 3.8.4.0
Severity: normal
The policy needs to be updated to take into account the dpkg triggers. At
the very least it needs to document the new invocations of the postinst in
chapter 6 (postinst
44 matches
Mail list logo
