Hi, Could Koji provide all the available versions of packages in a repository? Even http://koji.fedoraproject.org/static-repos/ indexes only the latest package versions there. Also f14 is not available there. ------------------------------------------------------------------------------ Otherwise could someone with the Koji filesystem access run there from cron / after each rpm build: find -name "*.rpm"|xargs rpm -q --qf '%{sourcerpm}.%{arch}\n' -lp|perl -lne '$s="$1$2" if m{^(.*)\.src\.rpm(.*)$};print "$s:$1$2" if m{^/usr/lib/debug/\.build-id/(..)/(.{38})$};' >databasefile producing gdb-7.0.1-50.fc12.i686:4f5aa8186d76a9799aece9a9b068af0d936ef5e3 gdb-7.0.1-50.fc12.i686:a7e7e5aaf6afddb1896ef43c84145c6eeb9d1df6 glibc-2.11-2.rm2.x86_64:00a915570060ddc72b453a3494e76acbe8645089 [...] and make that textfile available at Koji? ------------------------------------------------------------------------------ Use case: As a real world example I got a Bug with core file https://bugzilla.redhat.com/show_bug.cgi?id=631575#c3 but the crash is not reproducible for me. I do not have the right set of packages / debuginfos as the reporter. GDB even says: Missing separate debuginfo for /usr/lib64/libgconf-2.so.4 Try: yum --disablerepo='*' --enablerepo='*-debuginfo' install /usr/lib/debug/.build-id/6b/07bd9a969c858a548f9ca099afbe0eee9efbc0 but nothing can be installed by that command. It is due to: $ repoquery -qf /usr/lib/debug/.build-id/6b/07bd9a969c858a548f9ca099afbe0eee9efbc0 <nothing> Google for 07bd9a969c858a548f9ca099afbe0eee9efbc0 says GConf2-debuginfo-2.31.91-1.fc14.x86_64 so great. The problem is the repository still containing an older package because no Bodhi update has been submitted for it. $ repoquery -qf /usr/lib64/libgconf-2.so.4 GConf2-0:2.31.7-1.fc14.x86_64 In other cases the repository contains already a newer package. So I should Google all the build-id strings? Anyway even Google does not work: Missing separate debuginfo for /lib64/librt.so.1 Try: yum --disablerepo='*' --enablerepo='*-debuginfo' install /usr/lib/debug/.build-id/dd/84c09c78810df5dab541a469bf0e4fcf2cee97 -> Your search - 84c09c78810df5dab541a469bf0e4fcf2cee97 - did not match any documents. OK, I could ask the reported for `rpm -qa' but why to require human interaction when that information is in fact already available there. Thanks, Jan -- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/devel
