Summary: | rpm -i fails to install some Mandriva source rpms (rpm5.org src.rpms?) | ||
---|---|---|---|
Product: | Sisyphus | Reporter: | viy <viy> |
Component: | rpm | Assignee: | placeholder <placeholder> |
Status: | NEW --- | QA Contact: | qa-sisyphus |
Severity: | normal | ||
Priority: | P3 | CC: | at, glebfm, imz, ldv, mike, n3npq, peroyvind, placeholder, vt |
Version: | unstable | ||
Hardware: | all | ||
OS: | Linux | ||
URL: | http://mirror.yandex.ru/mandriva/devel/2011/SRPMS/contrib/backports/abcm2ps-6.5.15-1.src.rpm |
Description
viy
2012-01-02 18:36:03 MSK
tracked at https://bugs.launchpad.net/rpm/+bug/911021 (In reply to comment #0) > $ wget -c > 'http://mirror.yandex.ru/mandriva/devel/2011/SRPMS/contrib/backports/abcm2ps-6.5.15-1.src.rpm' > $ rpm -i abcm2ps-6.5.15-1.src.rpm > ошибка: невозможно получить исключительную блокировку на /var/lib/rpm/Packages > ошибка: невозможно открыть индекс Packages используя db3 - (-1) > ошибка: не могу открыть базу данных Packages в /var/lib/rpm > $ rpm -q > rpm-4.0.4-alt100.43 > > Выглядит так, как будто rpm принимает их за бинарные пакеты. exactly, they _are_ binary packages: $ od -A n -N 16 -t x1 -- abcm2ps-7.0.3-1.src.rpm ed ab ee db 03 00 00 00 00 00 00 00 00 00 00 00 :( the whole dir http://mirror.yandex.ru/mandriva/devel/2011/SRPMS/contrib/backports/ contains those 'srpms' with RPMVERSION=5.3.12. What does it mean? is rpm 5.3 compatible with our rpm 4.0+ no more? or is it just local Mandriva bug? Relax: Per Oyvind added a tracking dependency, now reverted. The change totally screwed not only Mandriva's build system *twice* but also ROSA's. Packages produced by rpm-5.3.12 SHOULD be compatible in format almost everywhere. The issue is vendor divergence, not upstream incompatibilities. (В ответ на комментарий №4) > Relax: Per Oyvind added a tracking dependency, now reverted. > > The change totally screwed not only Mandriva's build system *twice* > but also ROSA's. > > Packages produced by rpm-5.3.12 SHOULD be compatible in > format almost everywhere. The issue is vendor divergence, not > upstream incompatibilities. thanks! that's good news. (In reply to comment #4) > Relax: Per Oyvind added a tracking dependency, now reverted. Not related at all (and it only affected a few packages in cooker for a few days).. Judging by Dmitry's comment, a better guess would be that the issue is that rpmlead is being used to determine whether src.rpm or not.. |