Summary: | =net-libs/wt-3.3.4: please rapid stabilize since the current stable version is broken wrt boost. | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Toralf Förster <toralf> |
Component: | [OLD] Library | Assignee: | Matthew Marlowe (RETIRED) <mattm> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | amd64, blueness, jouni.kosonen, qa, x86 |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Toralf Förster
2015-01-24 22:20:52 UTC
This should likely be blocking bug 522474 . From upstream http://redmine.webtoolkit.eu/issues/3561 "This is a problem with boost 1.56 on the last Wt release. Boost rearranged some of its header files. This is fixed in the latest git version of Wt. So you options are to either use an older version of boost, or to use the git version of Wt." Just for information, it also affects the stable wt 3.2.2_p1-r1, which installed fine in the past, but is now getting the listed error when doing "emerge @preserved-rebuild", presumably due to the updated boost. I just copied wt-3.3.1.ebuild into wt-3.3.4.ebuild and this version built fine (In reply to Egor Y. Egorov from comment #3) > I just copied wt-3.3.1.ebuild into wt-3.3.4.ebuild and this version built > fine I just hit this. @mattm, can we get this bumped? (In reply to Anthony Basile from comment #4) > (In reply to Egor Y. Egorov from comment #3) > > I just copied wt-3.3.1.ebuild into wt-3.3.4.ebuild and this version built > > fine > > I just hit this. > > @mattm, can we get this bumped? Okay i removed 3.3.1 which is unstable and bumped it to 3.3.4. I also bumped to EAPI="5" and added slot selection := to dev-db/postgresql and dev-libs/openssl. I've made sense of the entire ebuild, I'm just not sure if we should have := or :* on dev-db/postgresql so I went with the safer choice. I'm not 100% familiar with this package. @mattm feel free to correct anything I did, but I had to move on this because all net-libs/wt ebuilds were broken, including the stable verison. @QA. You're cc-ed because of the current breakage. Feel free to put in your 2 cents. (In reply to Anthony Basile from comment #5) > (In reply to Anthony Basile from comment #4) > > (In reply to Egor Y. Egorov from comment #3) > > > I just copied wt-3.3.1.ebuild into wt-3.3.4.ebuild and this version built > > > fine > > > > I just hit this. > > > > @mattm, can we get this bumped? > > Okay i removed 3.3.1 which is unstable and bumped it to 3.3.4. I also > bumped to EAPI="5" and added slot selection := to dev-db/postgresql and > dev-libs/openssl. I've made sense of the entire ebuild, I'm just not sure > if we should have := or :* on dev-db/postgresql so I went with the safer > choice. I'm not 100% familiar with this package. > > @mattm feel free to correct anything I did, but I had to move on this > because all net-libs/wt ebuilds were broken, including the stable verison. > > @QA. You're cc-ed because of the current breakage. Feel free to put in your > 2 cents. Okay it looks like I'm the only person who cares, so I went ahead and stabilized 3.3.4 on amd64 and x86. The older version is simply broken so this has to be an improvement on things. Its still on the tree and I'll remove it in a few days if there are no further issues with this bug. I removed the broken version. We're done here. |