Hello,
We recently stumbled upon an issue with patch synchronization, which
turned out to be a bug in Hibernate handling of Package objects, which
in turn was caused by a strange definition of hashCode() in that class.
Steps to reproduce the problem and a proposed patch follow.
Reproducing the
Hello,
We recently stumbled upon an issue with patch synchronization, which
turned out to be a bug in Hibernate handling of Package objects, which
in turn was caused by a strange definition of hashCode() in that class.
Steps to reproduce the problem and a proposed patch follow.
Reproducing the
Hello Silvio,
what I did was:
1. I created a x86_64 channel, an erratum with a package
name-version-release.i686 and published the erratum into the channel
2. I cloned the channel with all errata
3. I added name-version-release.x86_64 package to the original erratum
4. I went to
On 08/21/2013 01:57 PM, Tomas Lestach wrote:
Does this mean the reproducer is wrong? Shall I take two packages of same
name, arch and evr? xulrunner-devel-17.0.5-1.el6_4-x86_64 and
xulrunner-devel-17.0.5-1.el6_4-x86_64 (let's say signed with another gpg key)?
Exactly - the problem arises when
