Bug 197124

Summary:	Hermes: broken upgrade paths
Product:	[Fedora] Fedora	Reporter:	Ville Skyttä <scop>
Component:	Hermes	Assignee:	Thomas Vander Stichele <thomas>
Status:	CLOSED NEXTRELEASE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	5	CC:	extras-qa, hdegoede
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2006-07-02 11:50:07 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Ville Skyttä 2006-06-28 17:57:20 UTC

Hermes' upgrade paths are broken:

  4: 0:1.3.3-9.fc4 (FE4)
  5: 0:1.3.3-7 (FE5)
  6: 0:1.3.3-7 (FE6)

See https://www.redhat.com/archives/fedora-extras-list/2006-May/msg00083.html

Comment 1 Thomas Vander Stichele 2006-07-02 11:50:07 UTC

pushed a .10 release for fe5 and fe6

Comment 2 Thomas Vander Stichele 2006-07-02 12:03:38 UTC

actually, they just don't even build.  the packages should be removed.

Comment 3 Hans de Goede 2006-07-23 08:16:52 UTC

Hmm,

Reopening, you say the package didn't build and should be removed, but as is
they are not removed and thus the broken upgrade paths are still there.

Also in bug 184109 you write that Hermes is orphaned, but you didn't change
owners.list to reflect that. Is Hermes orphaned?  I've just submitted a package
(CLanLib06) for review which needs Hermes (and seems to work fine with the
current versions in FE) so if its orphaned I would like to pick it up as I need it.

Comment 4 Thomas Vander Stichele 2006-07-23 15:47:36 UTC

it's yours for the taking

Comment 5 Hans de Goede 2006-07-23 20:57:47 UTC

Ok,

I've been working hard on a new release 1.3.3-11 which should show up on a
mirror near you soon, with the following changes:
* Sun Jul 23 2006 Hans de Goede <j.w.r.degoede> 1.3.3-11
- Taking over as new maintainer
- Add a patch from Debian fixing some 64 bit issues and more importantly
  fix building with a recent toolchain.
- Fix some further 64 bit issues
- Remove static lib
- Add --disable-dependency-tracking, touch config.h.in to fix the timestamp
  instead of BR: automake, autoconf
- Mark asm files as NOT needing execstack, making us OK with new default
  SELinux targeted policy settings.

Which should really fix the problem reported in this bug, so I'm leaving it closed.