Since this package wasn't updated in a long time, I though it wouldn't be rude to request its version bump just after it was released upstream. The sourceforge.net SRC_URI doesn't work (at least right now), but it can be pointed to the Gentoo mirror.
I have had a working new ebuild ready in my CVS checkout since 3 hours after the tarballs appeared on the GNOME FTP servers (some of us track uploads to gnome ftp servers, and maintain status pages). However, I have not committed it to the tree due to the desktop file being completely broken, and therefore a menu entry not appearing, with the changes to that stuff. The changes between 1.1.6 and 1.1.7 are essentially the following: * Update desktop file to have bug-buddy integration -> this is completely broken and would need patching in the ebuild * Add MAINTAINERS file (which we traditionally usually don't install in Gentoo GNOME stuff anyway, so no change for us) * Changes to autotools stuff that has no difference to us if we don't autoregen * Some fixes to gtkspell CFLAGS usage at configure level - no change but for a few systems where it didn't work - there have been no failure reports by Gentoo users * Make gtkspell optional - but this is based on autodetection, so we can't use it for a USE flag introduction until we patch configure for it to be able to force the usage off (not have it on as soon as gtkspell libraries are found) * Remove some unused code for a slightly smaller footprint Given only trivial improvements for Gentoo usage and a serious regression, I decided to file bugs and wait a few days for responses and see what to do from there - if to bother with fixing the desktop stuff myself or just wait for a new release. I would really expect a new release to happen soon at upstream, given this rather big regression with the desktop entry. The bugs I filed are: http://bugzilla.gnome.org/show_bug.cgi?id=380021 http://bugzilla.gnome.org/show_bug.cgi?id=380022 Sorry that I got carried away and babbled way too much :p PS: As the tarball lives in GNOME FTP now, the SRC_URI is fixed by simply removing it from the ebuild - gnome2.eclass will take care of it now automatically.
Both bugs are closed as fixed by upstream in svn. If anyone feels like gently reminding upstream to make a new release, that'd be great.
Ok, I've just pinged upstream about a new release in one of Mart's bugs and I pushed 1.1.7 to portage although under p.mask.
Created attachment 155813 [details] gtranslator 1.1.7 ebuild with patchs for upstream bugs #380021 and #380022 This is 1.1.7 ebuild with patches for these two bugs (attached below).
Created attachment 155819 [details, diff] Patch for upstream bug #380021 I wasn't able to apply upstream patch for bug #380021 (see http://svn.gnome.org/viewvc/gtranslator?view=revision&revision=3138), so I applied my own quick & dirty patch that avoids the bug without fixing it.
Created attachment 155821 [details, diff] Patch for upstream bug #380022 Upstream patch for bug #380022
*** Bug 270084 has been marked as a duplicate of this bug. ***
What's going on here, there's 1.9.6 out there, what should we do about it ? lastrite ?
Last rite with a 60 day period. Obviously, no one cares enough to do the bump :)
Fro some reason I can not attach file :( Now GTranslator depends on GDL library. Patches can be removed???
Created attachment 205409 [details] gtranslator-1.9.6.ebuild
As stated in comment #1, 1.1.7 had nothing important to be had, and p.masking 1.1.6 because of a botched upstream release that adds nothing noteworthy (besides build issues) compared to 1.1.6 is just wrong.
As talked with leio this won't be removed
1.9.8 was commited to the tree. Closing.
