Bug 153308 - stabilize net-news/blam-1.8.4_pre2 for mozilla removal
|
Bug#:
153308
|
Product: Gentoo Linux
|
Version: unspecified
|
Platform: All
|
|
OS/Version: Linux
|
Status: RESOLVED
|
Severity: major
|
Priority: P2
|
|
Resolution: FIXED
|
Assigned To: amd64@gentoo.org
|
Reported By: latexer@gentoo.org
|
|
Component: Ebuilds
|
|
|
URL:
|
|
Summary: stabilize net-news/blam-1.8.4_pre2 for mozilla removal
|
|
Keywords:
|
|
Status Whiteboard:
|
|
Opened: 2006-10-29 08:46 0000
|
blam-1.8.2 has been in the tree nearly a year now. Last night I commited one
last fix for issues with mono-1.1.17 and higher, but otherwise this has had
almost no bugs. I need this stabalized as part of my work to rid gecko-sharp of
the mozilla dependancy (see bug #137665).
Thanks in advance arch teams.
looks like gecko-sharp-0.11-r1 needs to go stable first if you don't want
mozilla.
# emerge -ptv =blam-1.8.2-r2
[ebuild N ] net-news/blam-1.8.2-r2 583 kB
[ebuild N ] dev-dotnet/gecko-sharp-0.6 108 kB
[ebuild N ] www-client/mozilla-1.7.13 USE="crypt gnome ipv6 java ldap
ssl truetype xprint -debug -mozcalendar -mozdevelop -moznocompose -moznoirc
-moznomail -moznoxft -mozsvg -postgres -xinerama" 29,912 kB
[ebuild NS ] dev-dotnet/gconf-sharp-1.0.10 0 kB
[ebuild NS ] dev-dotnet/gnome-sharp-1.0.10 0 kB
[ebuild NS ] dev-dotnet/art-sharp-1.0.10 0 kB
[ebuild NS ] dev-dotnet/glade-sharp-1.0.10 0 kB
[ebuild NS ] dev-dotnet/gtk-sharp-1.0.10 0 kB
(In reply to comment #1)
> looks like gecko-sharp-0.11-r1 needs to go stable first if you don't want
> mozilla.
That has been added on 29th October 2006, so I won't stable it right away. I
come again on 29th of November to stable both together.
(In reply to comment #4)
> (In reply to comment #1)
> > looks like gecko-sharp-0.11-r1 needs to go stable first if you don't want
> > mozilla.
>
> That has been added on 29th October 2006, so I won't stable it right away. I
> come again on 29th of November to stable both together.
blam harddepends on gecko-sharp-0.6 (and that is needed). So it will always
pull in mozilla, if it is not fixed in the ebuild. Stable on x86
(In reply to comment #5)
> blam harddepends on gecko-sharp-0.6 (and that is needed). So it will always
> pull in mozilla, if it is not fixed in the ebuild. Stable on x86
Reopen, this doesn't solve the mozilla removal issue in any way...
Yeah, totally my bad, I'd forgotten blam was still so far in the dark ages and
was actually using the old gtk# 1.0.x stuff. Someone else has taken up blam
development, found at (http://www.cmartin.tk/blam.html), which among other
things finally updates to the new gecko-sharp/gtk-sharp. I will try to find
time this week to bump, which should resolve this dep issue.
Fixed in 1.8.4_pre2; needs to be stabilized.
Re-adding the arch teams, please stabalise the new 1.8.4_pre2 for us, so the
mozilla herd can stop harassing me. (:
!!! All ebuilds that could satisfy ">=dev-dotnet/glade-sharp-2.8.2" have been
masked.
!!! One of the following masked packages is required to complete your request:
- dev-dotnet/glade-sharp-2.8.2 (masked by: ~x86 keyword)
- dev-dotnet/glade-sharp-2.10.0 (masked by: ~x86 keyword)
Which one do you want stabilized for blam?
checking for BLAM... configure: error: Package requirements (gtk-sharp-2.0 >=
2.8.2
gecko-sharp-2.0 >= 0.11
gconf-sharp-2.0 >= 2.8.2
glade-sharp-2.0 >= 2.8.2) were not met:
Requested 'gconf-sharp-2.0 >= 2.8.2' but version of GConf is 2.8.0
So please add it.
(In reply to comment #10)
> !!! All ebuilds that could satisfy ">=dev-dotnet/glade-sharp-2.8.2" have been
> masked.
> !!! One of the following masked packages is required to complete your request:
> - dev-dotnet/glade-sharp-2.8.2 (masked by: ~x86 keyword)
> - dev-dotnet/glade-sharp-2.10.0 (masked by: ~x86 keyword)
>
> Which one do you want stabilized for blam?
>
Go ahead with 2.8.2 which amd64 has already done so themselves.
when I run blam 1.8.4_pre2, the theme images do not show up for themes blam and
pimped, but they do appear in the planet theme.. The only difference I can find
is that the planet theme loads the images using css while the 2 others have
them in the html file. Do you want to stabilize anyways (for amd64) ?
ok, the image bug is an upstream bug..
They set <base href="${url}" /> ... but that means that all files loaded from
the html will be relative to that URL... so the images dont get loaded.. quick
fix is to have an absolute path (with file:///) or load the images using CSS.
Anyways, I've emailed upstream.
Also blam 1.8.4 is out if you care.
I adjusted the dependency of gconf-sharp to 2.8.2, as dotnet team did not react
to my request. x86 stable