1 More detailed explanation:
3 http://lists.pld-linux.org/mailman/pipermail/pld-devel-en/2012-December/023356.html
5 On Dec 1, 2012, at 10:55 AM, Jeffrey Johnson <n3npq@me.com> wrote:
8 > I'm inclined atm to prefer the above actual behavior to "fudging" an
9 > extra +1 for "legacy compatible" behavior; I'm sure we disagree here.
11 > Short answer: patch in an extra +1 (there will be two code paths in need
12 > of patching, check for symmetry as above) if you wish "legacy compatible" behavior.
15 This is likely all that is needed (untested):
17 cvs diff rpm/lib/psm.c
19 ===================================================================
20 RCS file: /v/rpm/cvs/rpm/lib/psm.c,v
21 retrieving revision 2.399.2.5
22 diff -p -u -w -r2.399.2.5 rpm/lib/psm.c
23 --- rpm/lib/psm.c 19 Apr 2012 17:26:06 -0000 2.399.2.5
24 +++ rpm/lib/psm.c 1 Dec 2012 16:02:48 -0000
25 @@ -2755,7 +2755,7 @@ assert(psm->te != NULL);
26 psm->scriptTag = RPMTAG_POSTIN;
27 psm->progTag = RPMTAG_POSTINPROG;
28 psm->sense = RPMSENSE_TRIGGERIN;
29 - psm->countCorrection = 0;
30 + psm->countCorrection = 1;
32 if (!(rpmtsFlags(ts) & RPMTRANS_FLAG_NOPOST)) {
33 rc = (rpmRC) rpmpsmNext(psm, PSM_SCRIPT);
35 _______________________________________________
36 pld-devel-en mailing list
37 pld-devel-en@lists.pld-linux.org
38 http://lists.pld-linux.org/mailman/listinfo/pld-devel-en