| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
| |
RPMFILE_UNPATCHED is no more used and RPMFILE_EXCLUDE only exists during
spec parse (see rpm commit 8d277bbb)
|
| |
|
| |
|
| |
|
|
|
|
| |
packages_providing()
|
|
|
|
|
|
|
|
|
| |
this mean prefering package from first medium when same NEVR exists in
several media, thus prefering 64bit media over 32 bit ones (mga#7524)
complement commit r2909 on Feb 7 2012:
" (find_required_package) really prefer packages from first media, thus
fixing downloading noarch packages from 32 bit repository (mga#1603)"
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
found accidently
could be triggered by the following (calling enough times either
requires() or provides() while traversing rpm db) which resulting in
an "Invalid read of size 8":
use URPM;
my $db = URPM::DB::open()->traverse_tag_find('whatprovides', 'kernel',
sub {
my ($p) = @_;
warn $p->requires, $p->requires, $p->requires, $p->requires, $p->requires,
$p->requires, $p->requires, $p->requires, $p->requires, $p->requires, $p->requires,
$p->requires, $p->requires, $p->requires, $p->requires, $p->requires, $p->requires;
return 1;
});
bug introduced in commit r4947 on June 14 2012:
"(_run_cb_while_traversing) introduce this helper"
|
| |
|
| |
|
|
|
|
| |
functions, then simplify
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
(it should have been named suggests_nosense in the first place, bad pixel...)
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
rationale:
it was passing RPMTAG_REQUIREFLAGS as flags instead of since commit
r225637 from pixel on 2007-08-09 that added initial suggests support
by that time, suggests were basically RPMTAG_REQUIRENAME + RPMSENSE_MISSINGOK.
in mdv2008.1, they were re-implemented the SuSe way with RPMTAG_SUGGESTSNAME.
since we no more support old mdv2008.0 suggests since commit r4974 on
2012-06-17 ("drop support for old mdv2008.0 suggests"), we no longer
try to distinct requires from suggests by looking at tag flags
so don't need to pass RPMTAG_REQUIREFLAGS anymore
(needed for next commit)
|
| |
|
| |
|
|
|
|
|
|
|
|
|
| |
calling ->provides or ->requires in traverse_tag_find() results in an
invalid read if provides/requires list is big (or if called several
times)
basically reverting commit r6476 on 2012-11-16
("(unsatisfied_requires) (slightly) optimize")
|
|
|
|
| |
callback_list_str_xpush()
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
some packages are broken
alternatively, we could try detecting if diff_provides doesn't change
for
a couple loops or not going over already rejected packages
(selecting/promoting/rejecting the same package forever)
eg: gtk+3.0-3.6.1-3.mga3.x86_64 is on the mirrors but not
lib64gtk+3_0-3.6.1-3.mga3.x86_64
we will then loop forever:
set_rejected: gtk+3.0-3.6.1-2.mga3.x86_64
installed lib64gtk+3_0-3.6.1-2.mga3.x86_64 is conflicting because of
unsatisfied gtk+3.0[== 3.6.1-2.mga3] gtk+3.0[*][== 3.6.1-2.mga3]
set_rejected: lib64gtk+3_0-3.6.1-2.mga3.x86_64
installed lib64gtk+3.0-devel-3.6.1-2.mga3.x86_64 is conflicting because
of unsatisfied lib64gtk+3_0[== 3.6.1]
set_rejected: lib64gtk+3.0-devel-3.6.1-2.mga3.x86_64
installed lib64gtk-gir3.0-3.6.1-2.mga3.x86_64 is conflicting because of
unsatisfied lib64gtk+3_0[== 3.6.1-2.mga3]
set_rejected: lib64gtk-gir3.0-3.6.1-2.mga3.x86_64
installed gtk+3.0-3.6.1-2.mga3.x86_64 is conflicting because of
unsatisfied lib64gtk+3_0[== 3.6.1]
promoting gtk+3.0-3.6.1-3.mga3.x86_64 because of conflict above
unselecting gtk+3.0-3.6.1-3.mga3.x86_64
set_rejected: gtk+3.0-3.6.1-2.mga3.x86_64
(...)
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
(Db_traverse,Db_traverse_tag) discard callback results prior to
introducing _run_cb_while_traversing() in commit r4947 on Jun 14 2012:
"(_run_cb_while_traversing) introduce this helper"
|
| |
|
| |
|
| |
|
|
|
|
|
| |
(should have been dropped along commit r6166 on 2012-10-05:
"(Trans_run) drop support for repackage (non working since rpm-4.6 in 2009)")
|
| |
|
| |
|
|
|
|
|
|
| |
should have been done right after commit r251061 by pixel on Tue Jan
2009: "- drop urpmi.recover
(no more possible with rpm 4.6 which doesn't handle --repackage)"
|
| |
|
| |
|