Re: Odd bug with pinning repository
Stephen Clouse <[email protected]> Fri, 8 Apr 2005 15:20:38 -0500
| Newsgroups | gmane.linux.conectiva.apt-rpm |
|---|---|
| Message-ID | <[email protected]> |
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Fri, Apr 08, 2005 at 11:30:57AM +0300, Panu Matilainen wrote:
> cpan2rpm is a real downgrade-case but the rest ... do the packages you
> have built yourself have a different release number than the ones coming
> from distro? I would guess not - or at least I could imagine something
> like this happening in that scenario.
Most of them are upgrades, but some (perl-CPAN as a quick example) aren't Fedora
packages at all.
perl-CPAN:
Installed: 0:1.76_01-0
Candidate: 0:1.76_01-0
Version Table:
*** 0:1.76_01-0 0
100 RPM Database
0:1.76_01-0 0
500 http://apt-internal.theiqgroup.com IQGroup/os-stable pkglist
0:1.76_01-0 0
1001 http://apt-internal.theiqgroup.com IQGroup/os-devel pkglist
In any case, I have the exact same packages as the repository. The repository
is actually built from packages I've built locally. I made the repository to
ease deployment in our development and production environments, and I want to
keep it pinned because our Perl is completely different from Fedora's, so none
of the distro packages will work anyway.
I just don't get why it thinks they're different when they're exactly the same.
Obviously it's a bug.
- --
Stephen Clouse <[email protected]>
Senior Programmer/DBE, Core Technology Developer
The IQ Group, Inc. <http://www.theiqgroup.com/>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.6 (GNU/Linux)
iD8DBQFCVueWy3uolkRT3A0RAgm+AJ9qJ+icvqxAbd1rjfJVY5sCS9dsugCfX3AT
XnqDo5eaFBb57IhktAZF2Qs=
=C8sa
-----END PGP SIGNATURE-----