LP #1034818: Percona Toolkit 2.1.3 requires RPM dependencies that don't exist

**Comment from Launchpad by: Daniel Nichter on: 11-08-2012 16:28:03

Thanks, glad it worked. Third time really is the charm, I guess.

**Comment from Launchpad by: nathan hruby on: 11-08-2012 03:09:31

Hi,

reposync succeeded with the -2. Thank you for the respin! A+, would sync again!

-n

**Comment from Launchpad by: Daniel Nichter on: 10-08-2012 21:49:26

Upon further discussion with Ignacio, we decided to re-re-release the .rpm, this time with build/release number 2. The choice boiled down to who to upset: on the one hand, there are probably a lot of people who got the package later and so have already installed the 2nd, good 1 release. Re-re-releasing means we can trigger another upgrade for them that's not needed. But on the other hand, obviously some people got the 1st, bad -1 release and are now having problems with it and the 2nd, good -1 release. So, with no way to please everyone, we decided to punt, do a re-re-release (-2)the technically correct thing-and be done with it.

Lessons learned, and 2.1.4 will be better.

**Comment from Launchpad by: Ignacio Nin on: 10-08-2012 21:25:14

Hello Nathan,

Thanks for your report – agreed that increasing the buildnumber may avoid these problems, we'll try to use this approach for future cases.

In your particular problem, it'd seem that yum is not updating its local metadata for some reason. In any case, I've double checked the repodata and it seems fine – even more I reposync(1)ed the repo without problems.

Could you try yum clean metadata in your host? I'm hoping this will allow it to resync it to our repo. Let us know how it goes, and please excuse the inconveniences!

N.

**Comment from Launchpad by: nathan hruby on: 10-08-2012 19:50:58

Hi,

buldnum's must always be incremented a) for sanity, b) so things like yum can tell there's an update c) so caching doesn't bite you

I belive c is still affecting me. My specific issue is that it appears the package and the repodata are not in sync so when I try to remirror the centos 5 repo, I get this from reposync:

> [Percona-EL-5-x86_64: 30 of 40 ] Downloading percona-toolkit-2.1.3-1.noarch.rpm
> Could not retrieve package percona-toolkit-2.1.3-1.noarch. Error was failure: percona-toolkit-2.1.3-1.noarch.rpm from Percona-EL-5-x86_64: [Errno 256] No more mirrors to try.

The re-issuance of the package with same build number may have caused createrepo and/or other tooling to do the wrong thing. If you don't want to respin the package with a bumped buildnum, that's fine, but can you look at the repo metadata to ensure that it's kosher and mirrorable?

Thanks,

-n