Regarding bugzilla, you can close your bug report and mark it as a duplicate of the earlier bug report (you provide the number). This will also add a note to the the original bug report about the duplicate.
Hth. On Sep 2, 2011 11:19 AM, "Barry Fishman" <barry_fish...@acm.org> wrote: > Recently while running Fedora 16, my attempt at: > > yum update --skip-broken > > failed with: > > warning: rpmts_HdrFromFdno: Header V3 RSA/SHA256 Signature, key ID 069c8460: NOKEY > Retrieving key from file:///etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-x86_64 > > > The GPG keys listed for the "Fedora 16 - x86_64" repository are already installed but they are not correct for this package. > Check that the correct key URLs are configured for this repository. > > Looking at bug #735037, It seems that there was a problem with package > btrfs-progs. > > Couldn't yum refers to 'this package' but does not say which package was > the problems. If it at least said which package was involved, I could > have uninstalled that package and updated everything else. > > Better yet 'yum --skip-broken' could have removed that package from > consideration, redid the dependencies and updated the remaining > packages. > > As a side note, I checked bugzilla for problems with yum and finding > none submitted bug #735235. It takes a while for bug reports to show up > in the bugzilla search, so a day or so later when I got a confirmation I > found the earlier bug report. > > I found no way in bugzilla to close my bug report by merging it into the > earlier bug report. I think such an ability by the original submitter > would help the people working on fixing bug, (and bug submitters,) by > prefiltering the individual bug reports to which they needed to look at. > > -- > Barry Fishman > > -- > devel mailing list > devel@lists.fedoraproject.org > https://admin.fedoraproject.org/mailman/listinfo/devel
-- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
