Bug 199546 - dev-cpp/glibmm-2.14.2 do not need anymore the fbsd patchset
|
Bug#:
199546
|
Product: Gentoo/Alt
|
Version: unspecified
|
Platform: All
|
|
OS/Version: FreeBSD
|
Status: RESOLVED
|
Severity: normal
|
Priority: P2
|
|
Resolution: FIXED
|
Assigned To: bsd@gentoo.org
|
Reported By: toffanin.mauro@gmail.com
|
|
Component: FreeBSD
|
|
|
URL:
|
|
Summary: dev-cpp/glibmm-2.14.2 do not need anymore the fbsd patchset
|
|
Keywords:
|
|
Status Whiteboard:
|
|
Opened: 2007-11-18 15:41 0000
|
dev-cpp/glibmm-2.14.2 fail unpack phase because do not found the patch
"glibmm-2.14.2-date.patch":
* Running elibtoolize in: glibmm-2.14.2/scripts
* Applying portage-1.5.10.patch ...
* Applying max_cmd_len-1.5.20.patch ...
* Applying sed-1.5.6.patch ...
* Applying fbsd-conf-1.5.20b.patch ...
* Applying glibmm-2.14.2-date.patch ...
* Failed Patch: glibmm-2.14.2-date.patch !
* ( /usr/portage/dev-cpp/glibmm/files/glibmm-2.14.2-date.patch )
*
* Include in your bugreport the contents of:
*
*
/var/tmp/portage/dev-cpp/glibmm-2.14.2/temp/glibmm-2.14.2-date.patch-10075.out
dev-cpp/glibmm-2.14.2 do not need the patch made by Roy Marple about GTime and
time_t (as done in glibmm-2.14.0-date.patch) because the problem has been fixed
upstream for the 2.14.2 release; indeed glibmm-2.14.2 now compile and run fine
on g/fbsd.
Reproducible: Always
*** Bug 201533 has been marked as a duplicate of this bug. ***
gnome-mm team: what's the status of 2.14.2? It's still here because of slacking
arches, right ? I can't build it, most likely because of too recent glib. I
think I could just remove fbsd keyword from 2.14.2 and drop the patch, no time
to waste in supporting old libs. Opinions?
I want to stabilize glibmm 2.16.4. But as you've noted, we're stuck with
slacking arches (I won't name them...)
I'm currently preparing the stable list for gnome-mm packages. You're allowed
to whip me if I don't get it out today :)
Thanks
(In reply to comment #4)
> I'm currently preparing the stable list for gnome-mm packages. You're allowed
> to whip me if I don't get it out today :)
As we don't have stable keywords for bsd, that's not really our problem ;)
I've removed the broken patch, dropped the x86-fbsd keyword for 2.14.2 as
2.16.4 seems fine.
Therefore, bug "fixed"