First Last Prev Next    No search results available      Search page      Enter new bug
Bug#: 133386
Alias:
Product:
Component:
Status: RESOLVED
Resolution: FIXED
Assigned To: ppc64 architecture team <ppc64@gentoo.org>
Hardware:
OS:
Version:
Priority:
Severity:
Reporter: Jon Mason <jdmason@gmail.com>
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 133386 depends on: Show dependency tree
Bug 133386 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: 2006-05-15 08:39 0000
dev-util/mercurial-0.8.1 works on ppc64.
I emerged it and everything appears to be in working order.  Since there is no
version of mercurial marked stable on ppc64, this would be a good candidate. 


# emerge info
Portage 2.0.54 (default-linux/ppc/ppc64/2006.0/64bit-userland, gcc-3.4.6,
glibc-2.3.4.20041102-r2, 2.6.17-rc4 ppc64)
=================================================================
System uname: 2.6.17-rc4 ppc64 POWER3 (630)
Gentoo Base System version 1.6.14
dev-lang/python:     2.4.2
dev-util/ccache:     [Not Present]
dev-util/confcache:  [Not Present]
sys-apps/sandbox:    1.2.12
sys-devel/autoconf:  2.13, 2.59-r7
sys-devel/automake:  1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.6-r1
sys-devel/binutils:  2.16.1
sys-devel/libtool:   1.5.22
virtual/os-headers:  2.6.11-r4
ACCEPT_KEYWORDS="ppc64"
AUTOCLEAN="yes"
CBUILD="powerpc64-unknown-linux-gnu"
CFLAGS="-O2 -pipe -mcpu=power3"
CHOST="powerpc64-unknown-linux-gnu"
CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3/share/config
/usr/share/config /var/qmail/control"
CONFIG_PROTECT_MASK="/etc/eselect/compiler /etc/gconf /etc/terminfo /etc/env.d"
CXXFLAGS="-O2 -pipe -mcpu=power3"
DISTDIR="/usr/portage/distfiles"
FEATURES="autoconfig distlocks sandbox sfperms strict"
GENTOO_MIRRORS="http://distfiles.gentoo.org
http://distro.ibiblio.org/pub/linux/distributions/gentoo"
MAKEOPTS="-j3"
PKGDIR="/usr/portage/packages"
PORTAGE_TMPDIR="/var/tmp"
PORTDIR="/usr/portage"
SYNC="rsync://rsync.gentoo.org/gentoo-portage"
USE="ppc64 X alsa apache2 apm arts berkdb bitmap-fonts bzip2 cli cups dri eds
emboss encode esd expat foomaticdb fortran gdbm gif gnome gpm gstreamer gtk
gtk2 ibm imlib ipv6 jpeg kde libg++ libwww mad mikmod motif mp3 mpeg ncurses
nls nptl ogg opengl oss pam pcre pdflib perl png python qt quicktime readline
reflection sdl session spell spl ssl tcpd truetype truetype-fonts type1-fonts
udev unicode vorbis xml xml2 xmms xorg xv zlib userland_GNU kernel_linux
elibc_glibc"
Unset:  ASFLAGS, CTARGET, INSTALL_MASK, LANG, LC_ALL, LDFLAGS, LINGUAS,
PORTDIR_OVERLAY

------- Comment #1 From Markus Rothe 2006-05-16 12:53:07 0000 -------
added ~ppc64 to mercurial >0.8

------- Comment #2 From Jon Mason 2006-05-17 06:16:29 0000 -------
Sorry, I don't think I was clear.  Currently all mercurial packages are masked
as unstable (i.e., ~ppc64).  I have tested dev-util/mercurial-0.8.1 on my
power3 system and it works.  Please mark this ebuild as stable (i.e., ppc64).

Note:  mercurial-0.7.ebuild has no ppc64 flag at all.  You might want to add
one.

------- Comment #3 From Markus Rothe 2006-05-17 13:52:24 0000 -------
hmm.. I'm pretty sure that I've added ~ppc64 yesterday and the diff from cvs
shows me the same: no ~ppc64 in mercurial ebuilds untill yesterday... mercurial
will go stable in 30 days, if no bugs are opened for it.

Or am I missunderstanding the situation?

------- Comment #4 From Jon Mason 2006-05-18 06:29:49 0000 -------
Alright, if the precedure is to wait 30 days, then I will wait and keep it
unmasked in my tree until then.  Thanks

First Last Prev Next    No search results available      Search page      Enter new bug