Bug List: (This bug is not in your last search results)   Show last search results      Search page      Enter new bug
Bug#: 192367
Alias:
Product:
Component:
Status: RESOLVED
Resolution: FIXED
Assigned To: The Soldering-Iron Brotherhood <sci-electronics@gentoo.org>
Hardware:
OS:
Version:
Priority:
Severity:
Reporter: Stefan Salewski <mail@ssalewski.de>
Add CC:
CC:
URL:
Summary:
Status Whiteboard:
Keywords:

Filename Description Type Creator Created Size Actions
Create a New Attachment (proposed patch, testcase, etc.) View All

Bug 192367 depends on: Show dependency tree
Bug 192367 blocks:
Votes: 0    Show votes for this bug    Vote for this bug

Additional Comments: (this is where you put emerge --info)


Not eligible to see or edit group visibility for this bug.






View Bug Activity   |   Format For Printing   |   XML   |   Clone This Bug

Description:   Opened: 2007-09-12 22:58 0000 
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 From Denis Dupeyron 2007-09-18 10:04:17 0000 ------- 
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.
Bug List: (This bug is not in your last search results)   Show last search results      Search page      Enter new bug