| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
revert part of commit r5052 (June 28 2012, "light speedups")
|
| |
|
|
|
|
| |
(that cause rpm to abort on assert while creating a new pool)
|
| |
|
|
|
|
|
| |
RPMFILE_UNPATCHED is no more used and RPMFILE_EXCLUDE only exists during
spec parse (see rpm commit 8d277bbb)
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
| |
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"
|
| |
|
| |
|
| |
|
|
|
|
| |
(it should have been named suggests_nosense in the first place, bad pixel...)
|
| |
|
| |
|
|
|
|
|
|
|
|
|
| |
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")
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
(...)
|
| |
|
|
|
|
|
|
| |
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)"
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
This avoids pushing more than 50k strings on the stack to check if texmf has a README.urpmi
|
| |
|
| |
|
|
|
|
|
|
|
| |
introduction introduced in commit r5031 on 012-06-25
("spec2srcheader) simplify using headerPutString()")
fixed by simplifying: our changes are no more needed...
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
thus fixing setting rflags on packages (mga#6532)
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
should have been done right away 9 years ago instead of reimplementing
older rpmRangesOverlap() in commit r11141 by fpons on Tue Apr 29 2003:
"first try of 4.2 compatible perl-URPM,
missing verify_signature,
new version 0.83"
francois I hate you!
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
fd leaks (mga#6453)
rationale:
commit 4c1f7e335de1724661ce63c53186d161ab71a63f changed rpm-4.10 so that
fdFree() always return NULL whereas previously it would return the
supposedly free'd fd back if the fd had remaining references.
This prevent us to call fdClose() thus to really close the fd
we should not close fdLink() which set ref counter to 2 anyway...
|
| |
|
| |
|