Bug 483549 - New upstream release 3.7
Summary: New upstream release 3.7
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: joe
Version: rawhide
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Ivana Varekova
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-02-02 12:02 UTC by Hans de Goede
Modified: 2009-02-14 22:01 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2009-02-03 11:47:00 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Hans de Goede 2009-02-02 12:02:53 UTC
Hi,

I'm a fervent joe user and I was having some problems with joe (segfaulting regulary) so I looked upstream to see if there might be any fixes, and then I noticed that our version is a bit stale.

I've prepared a rebase to 3.7 (including rebasing our patches). Just say the word and I'll commit (I'm in the proven packager group) and build it for rawhide.

Also as I use joe on a daily basis I would like to co-maintain it with you, if that is ok with you then I'll request the necessary rights in pkgdb.

Comment 1 Ivana Varekova 2009-02-03 11:47:00 UTC
Thanks. Fixed.

Comment 2 Hans de Goede 2009-02-14 22:01:46 UTC
<sigh>

Half fixed, why is reading so hard? I offered to co-maintain, it would be nice if you responded to that. Also I said I already had a new package ready to commit to CVS, this bz was just a courtesy thing, you didn't need to spend any time on this other then to type: Go ahead commit the new version.

Instead you've duplicated some of my work, and did a bad job at it. Yes joe does not put translations in a standard place, that is something which would be nice to fix, but by removing them completely you've broken translations in joe, as they do work when left where joe puts them.

Even worse, you've now got a non - applying patch in the package which needed rebasing which you did not rebase. This should have broken the build, but it did note this is an rpm bug, see: bug 485584. But still something which you should have noticed (I did and it was fixed in the version I had al ready to commit).

I'm doing a new fixed build now. And I'm still interested in co-maintaining if you want a co-maintainer.


Note You need to log in before you can comment on or make changes to this bug.