Bug 171141 - app-office/gnotime-2.2.2 patch to compile w/ guile-1.8 without deprecated flag
|
Bug#:
171141
|
Product: Gentoo Linux
|
Version: unspecified
|
Platform: All
|
|
OS/Version: Linux
|
Status: RESOLVED
|
Severity: enhancement
|
Priority: P2
|
|
Resolution: FIXED
|
Assigned To: gnome-office@gentoo.org
|
Reported By: stas@onlineua.net
|
|
Component: Ebuilds
|
|
|
URL:
|
|
Summary: app-office/gnotime-2.2.2 patch to compile w/ guile-1.8 without deprecated flag
|
|
Keywords:
|
|
Status Whiteboard:
|
|
Opened: 2007-03-16 10:22 0000
|
This is ebuild for gnotime-2.2.2 with patches for build with new guile without
deprecated features and parallel build. Works for me on x86 and x86_64
Reproducible: Always
Steps to Reproduce:
Maybe this bug should be posted into bug #136372 (app-office/gnotime-2.1.6
emerge failed) or #163908 (gnome-extra/gnome-games and app-office/gnotime fail
to compile because of guile-1.8.1-r1) but they seems not to be directly
related, also it is new ebuild.
I'm seeing the same issue here. 2.2.2 works - maybe it should be stabilized,
it's out since September 2005 (!)
(In reply to comment #5)
> I'm seeing the same issue here. 2.2.2 works - maybe it should be stabilized,
> it's out since September 2005 (!)
So the patch is not needed, or???
Marijn, maybe you can tell us more...I am not really into Guile, so I can't
tell if this patch is still needed.
gnotime-2.2.2 seems to build fine with guile-1.8.2 with deprecated flag. I
imgine this patch here is to make it compile against 1.8* even without
deprecated flag (as the zeroth comment says).
So I suggest the patch is sent upstream and the ebuild made to depend on guile
being built with the deprecated flag until upstream accepts the patch.
(In reply to comment #9)
> gnotime-2.2.2 seems to build fine with guile-1.8.2 with deprecated flag. I
> imgine this patch here is to make it compile against 1.8* even without
> deprecated flag (as the zeroth comment says).
> So I suggest the patch is sent upstream and the ebuild made to depend on guile
> being built with the deprecated flag until upstream accepts the patch.
So I will add a check to 2.2.2 for that, stable that, will create a -r1 with
the patch applied and send it upstream. Honestly I don't think there will be
too much movement on upstream side. Give me some time to do it properly.
(In reply to comment #10)
> So I will add a check to 2.2.2 for that, stable that, will create a -r1 with
> the patch applied
Done. Closing, thanks for the patience.