In Portage tree since 30 days, no bugs reported. Only modification from stable -r5 is that a built_with_use test was replaced by a USE dependency, and therefore the ebuild was changed to EAPI 2. There should be no changes in the installed files. emacs-18.59-r5 may be removed when -r6 is stable. Thanks in advance.
x86 stable, closing
Please stabilise on amd64 too.
is this really necessary? # emerge -1av =app-editors/emacs-18.59-r6 These are the packages that would be merged, in order: Calculating dependencies... done! [ebuild UD] x11-libs/libX11-1.1.5 [1.2.2] USE="ipv6 -debug -xcb*" 0 kB [ebuild NS ] app-editors/emacs-18.59-r6 [22.3-r2, 23.1] USE="X" 2,926 kB Total: 2 packages (1 downgrade, 1 in new slot), Size of downloads: 2,926 kB
(In reply to comment #3) > is this really necessary? > [ebuild UD] x11-libs/libX11-1.1.5 [1.2.2] USE="ipv6 -debug -xcb*" 0 kB Is this on x86 or amd64? Generally, it needs libX11 with USE=-xcb. I don't know why it would downgrade, though.
> Is this on x86 or amd64? That was a stupid question, as only the amd64 keyword is missing. We could change RDEPEND to the following, since on amd64 it needs libX11 for the header files only: RDEPEND="sys-libs/ncurses >=app-admin/eselect-emacs-1.2 amd64? ( app-emulation/emul-linux-x86-baselibs X? ( x11-libs/libX11 app-emulation/emul-linux-x86-xlibs ) ) !amd64? ( X? ( x11-libs/libX11[-xcb] ) )"
bah, sorry for the noise. I was confused by this portage behaviour as I thought the ebuild wants an older libX11. it's okay like it is, as I just had to USE="-xcb" and no downgrade anymore.... sorry for the noise.
amd64 stable, all arches done.
