Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 192367 - sci-electronics/geda-1.2.0 request for version bump
Summary: sci-electronics/geda-1.2.0 request for version bump
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: New packages (show other bugs)
Hardware: All Linux
: High enhancement (vote)
Assignee: The Soldering-Iron Brotherhood
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-09-12 22:58 UTC by Stefan Salewski
Modified: 2007-09-18 10:04 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Stefan Salewski 2007-09-12 22:58:14 UTC
Stable geda release 1.2.0 is available at
http://www.seul.org/pipermail/geda-announce/2007-September/000052.html

The ebuild for the last stable 1.1 release was invisible/masked for most users!
I have seen it today for the first time after executing

cd /etc/portage/package.mask/
echo "=sci-electronics/libgeda-200*" > libgeda
echo "=sci-electronics/geda-200*" > geda

I have created my own 1.2 overlay for geda and libgeda as described at
http://gentoo-wiki.com/HOWTO_Create_an_Updated_Ebuild

It was only necessary to replace SUBDIR="v1.2" and to replace "devel" with "release" directory.



Reproducible: Always
Comment 1 Denis Dupeyron (RETIRED) gentoo-dev 2007-09-18 10:04:17 UTC
Done. Thanks for reporting it.

(In reply to comment #0)

> The ebuild for the last stable 1.1 release was invisible/masked for most users!
> I have seen it today for the first time after executing
> 
> cd /etc/portage/package.mask/
> echo "=sci-electronics/libgeda-200*" > libgeda
> echo "=sci-electronics/geda-200*" > geda

Yes, this was documented in the ChangeLog. Unfortunately there wasn't much that could be done. In order for the situation to be fixed we need to get rid of every single 200* versions, which can only be done when one of the new versions is stabilized. And this means we have to wait a reasonable time before we stabilize version 1.1.1. I've asked for stabilization today so this should be fixed soon.

Denis.