| Re: [proaudio] ebuilds for new versions of ardour 2.7 |
[ Thread Index |
Date Index
| More lists.tuxfamily.org/proaudio Archives
]
Hi Marc,
I had the same problem some weeks ago but don't remember how I solved
this issue finally. I had something like gtkmm or gtk+ or libgnomecanvas
in /etc/portage/packages.keywords and had to remove it from the keywords
file. MAybe you can identify the package using $ equery d gail
Then I did an emerge -C gnome-base/gail and emerge gail.
Be prepared that wget doesn't work anymore after removing gail.
I solved this by downloading the necessary packages using a browser and
placed them in /usr/portage/distfiles until the latest version of gail
was compiled.
Then I could go on update the usual way.
Here a list of package depending on gail:
~ $ equery d gail
[ Searching for packages depending on gail... ]
gnome-base/eel-2.22.2 (>=gnome-base/gail-0.16)
gnome-base/gnome-2.22.3 (accessibility? >=gnome-base/gail-1.22.3)
gnome-base/gnome-applets-2.22.3 (>=gnome-base/gail-1.1)
gnome-base/libgnomecanvas-2.20.1.1 (>=gnome-base/gail-1.19.6)
gnome-extra/gnome-media-2.22.0 (gnomecd? >=gnome-base/gail-0.0.3)
gnome-extra/gtkhtml-3.18.3 (>=gnome-base/gail-1.1)
~ $
I used the latest testing version of portage due to the EAPI2
dependency.
Hope this helps
Martin
On Di, 2008-11-25 at 05:25 -0800, Mark Knecht wrote:
> I am unable to build it. It seems to require a masked version of
> portage, which I managed to build, but then requires about 10 other
> ~amd64 package that havw blocks, one being something called gail-1000
> which I couldn't figure out how to fix.
>
> Not a happy camper.
>
> Cheers,
> Mark
>
> On Mon, Nov 24, 2008 at 10:24 PM, Arve Barsnes <arve.barsnes@xxxxxxxxx> wrote:
> > 2.7 is in portage, and 2.6 has been for a long time
> >
> > On Tue, Nov 25, 2008 at 7:00 AM, sonofzev@xxxxxxxxxxxx
> > <sonofzev@xxxxxxxxxxxx> wrote:
> >> Hi
> >>
> >> Is anybody working on ebuilds for the new versions of Ardour... (2.6.x or
> >> 2.7).
> >> I tried just building 2.6.1 from source the scons way.. but it was epic fail
> >> for me as I'm in tracking mode with some new tracks and it woudn't respond
> >> to MMC from my MPC 2000, which is critical....
> >>
> >> if not, let me know I may have a crack... but probably not for another week
> >> or so. ....
> >>
> >> cheers
> >>
> >> Allan
> >>
> >>
> >
> >
> >
>