urpmi/t, branch 7.28

add 2 other possible transaction orders

2013-10-04T07:26:33+00:00

needed due to perl-5.18 random keys order

it could alternatively be workarounded by sorting packages in genhdlist2

factorize possible transaction sets definition

2013-10-04T07:26:31+00:00

(needed for next commit)

simplify: use member()

2013-10-04T07:25:34+00:00

(needed for next commit)

adapt to perl-5.18's random hash keys ordering

2013-10-04T07:25:34+00:00

(translate_why_removed_one) ensure we got the right reason

(testsuite) adapt to new URPM predictible behaviour

it was previously relying on the following fixed hash order:

$ perl -MData::Dumper -e 'warn Dumper [ keys {'rr1', 'rr1', 'rr2',
'rr2'} ]; \
warn Dumper [ keys {'bb1', 'bb1', 'bb2', 'bb2-1'} ]'
$VAR1 = [
          'rr2',
          'rr1'
        ];
$VAR1 = [
          'bb1',
          'bb2'
        ];

(install_logger) keep a separate counter for erasures

2013-02-09T12:20:39+00:00

only initialize $total_pkg:
- when starting a new transaction
- or on first erasure in transaction

(_compute_pkg_total) kill it (no more needed)

adjust testsuite accordingly

(install_logger) unify with callback_uninst(), thus fixing counting for

2013-02-05T14:31:05+00:00

erasures

(callback_uninst) restore quiet behavior when not in verbose mode

(install) temporary set $urpm->{trans}

adapt testsuite

(callback_uninst) display erasure progress

2013-02-03T22:18:23+00:00

inspirated from install_logger()

adjust testsuite accordingly

wrap comment

2013-02-03T22:18:19+00:00

fix that test when prelink is installed

2013-01-31T20:14:02+00:00

revert my previous commits, this was a bad anyway

2012-12-10T18:19:07+00:00