Summary: | Update nxcomp-1.3.2-r1 ebuild with gcc34 patch. | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Clemmitt M. Sigler <cmsigler> |
Component: | Current packages | Assignee: | Gentoo NX Server project <nx> |
Status: | RESOLVED FIXED | ||
Severity: | major | CC: | bugs, me, rhill |
Priority: | High | ||
Version: | 2006.0 | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 140707 | ||
Attachments: | .tar.gz of changes to net-misc/nxcomp portage subtree |
Description
Clemmitt M. Sigler
2006-06-08 19:14:37 UTC
Created attachment 88734 [details]
.tar.gz of changes to net-misc/nxcomp portage subtree
This .tar.gz includes updated files for the net-misc/nxcomp portage subtree along with the originals.
alternatively, bumping nxcomp-1.5.0-r1 to stable would fix this bug as well as pave the way for GCC 4.1 going stable (bug #140707). Stabilise nxcomp-1.5.0-r2 please and cc arches if there are no obstacles (I see no bugs left to that version) Any word on this? GCC 4.1.1 should be going stable soon and this needs to be resolved first. If there's no word on this by August 25th/26th, then I'm just going to go ahead an mark the newer version stable on amd64/x86 after making sure it works. If you have any objections, speak them now. wolf31o2, so please go on stabilizing No go. You have to stabilise all nx*-1.5 packages as a group, or not at all. NX-1.5 is an old version; upstream are now on NX-2.0. I'm just the proxy maintainer for NX these days. I'll check with the guys who maintain the packages. If you don't hear from me by the 25th, the best thing to do would be to mask NX until we can get the NX-2.0 packages into Portage. Please don't stabilise NX-1.5 unless you're willing to provide support for NX-1.5 bugs. Best regards, Stu (In reply to comment #7) > I'm just the proxy maintainer for NX these days. I'll check with the guys who > maintain the packages. If you don't hear from me by the 25th, the best thing > to do would be to mask NX until we can get the NX-2.0 packages into Portage. > > Please don't stabilise NX-1.5 unless you're willing to provide support for > NX-1.5 bugs. So should we mask this then? x86, drop the stable keyword please, it doesn't compile. Stuart, any update about this? Should we simply drop the keyword at this point as 2.0 has not made it into the tree? *** Bug 152517 has been marked as a duplicate of this bug. *** I remove us, as nxcomp will vanish soon as I just read on Planet. |