Bug 1037609

Summary: libspiro is out of date
Product: [Fedora] Fedora Reporter: H.J. Lu <hongjiu.lu>
Component: libspiroAssignee: Kevin Fenzi <kevin>
Status: CLOSED RAWHIDE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: rawhideCC: i, kevin, nphilipp, pnemade
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-12-03 23:48:27 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description H.J. Lu 2013-12-03 13:28:09 UTC
libspiro seems to have moved to

https://github.com/fontforge/libspiro

Comment 1 Kevin Fenzi 2013-12-03 23:48:27 UTC
Updated in rawhide. Thanks.

Comment 2 Christopher Meng 2013-12-04 10:17:02 UTC
Thanks for your notification, I just changed libuninameslist's tag name strategy on github, also for libspiro.

Kevin, this should be verisoned like: 0.2.20130930, but not 20130930.

Comment 3 Kevin Fenzi 2013-12-04 16:11:50 UTC
I saw that they added a useless 0.2 there. I suppose we could reversion, but it will require us to use Epoch. 

Probibly we want to talk to upstream and see if how they are going to be doing versioning moving forward. I'm not sure what value the 0.2 adds there.

Comment 4 Christopher Meng 2013-12-05 04:34:29 UTC
(In reply to Kevin Fenzi from comment #3)
> I saw that they added a useless 0.2 there. I suppose we could reversion, but
> it will require us to use Epoch. 

Yes, I should told you about this more quickly... Then we can untag it... Inevitably, we are too late. ;)

> Probibly we want to talk to upstream and see if how they are going to be
> doing versioning moving forward. I'm not sure what value the 0.2 adds there.

Talk to me is OK ;)

I've dicussed with others to use majorver.minorver.date as release naming way. We don't have intention to change again from now on.

Just keep this versioned packaged there.