| Summary: | www-servers/tomcat-7.0.32 and www-servers/tomcat-6.0.36 should install init scripts and configuration files | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Mark H. Wood <mwood> |
| Component: | [OLD] Java | Assignee: | Java team <java> |
| Status: | RESOLVED INVALID | ||
| Severity: | normal | ||
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
|
Description
Mark H. Wood
2012-12-07 16:48:04 UTC
this is expected behavior. you are supposed to follow the after-merge information: * Messages for package www-servers/tomcat-7.0.33: * For how to deploy a server instance run: * /usr/share/tomcat-7/gentoo/tomcat-instance-manager.bash --help * tomcat-dbcp.jar is not built at this time. Please fetch jar * from upstream binary if you need it. Gentoo Bug # 144276 you can also find helpful information at https://wiki.gentoo.org/wiki/Apache_Tomcat Do you mean to say that upgrading an existing Tomcat installation is expected to render it unusable? what do you mean by "unusable"? "Unusable" as in the initscript is gone, no way to start Tomcat. I think I caused confusion by writing unclearly about two different situations (of which I have both): o I have several Tomcat 7 installs which were already in place and functioning, and after today's 'emerge -u world' their initscripts and some JARs and configuration (such as the logging) are missing. o I had one host which had not yet been moved to Tomcat 7. When I remembered this, I tried to set it up (using the way many packages do, instead of reading the post-install note carefully). The response to that looked like useful information about the other problem, but apparently it isn't. the way to start tomcat is to create new tomcat instance and migrate your existing instance there. i have added https://wiki.gentoo.org/wiki/Apache_Tomcat#Migrating_Old_Tomcat_Instance to the wiki to ease the migration process. it is pretty easy i suppose. you will be able to run tomcat using the init script once you finish the instance migration process. So 'emerge -u tomcat' is *expected* to destroy my working instance of Tomcat 7? Was this announced somewhere? I do not want to -remove my existing, working Tomcat instance. I do not want to invent more instances. There's nothing to migrate; it's only a point release. I want my existing single non-suffixed instance working again. How can I do that? if the suffix is problem for you, you can run the instance manager without suffix, but it will complain about already existing directories/files so you'd have to resolve that (rename) first. using suffix is much easier if you have tomcat instance from previous tomcat version. another option is to create new instance using suffix and then adjust your non-suffixed instance so that it has the same config/init files. I should have noted on the bug that there should be a news item accompanying the stabilization as this would have been the only means to do it. Miroslav was pushed by security and so I take the blame for not being careful enough back in July. I want to apologize for the hassle this has caused. There are two paths to get things working, downgrading to a version still installing the old init script or to do the migration. The migration should be rather painless but needs some user intervention. Several months in unstable didn't brought up any user questions or complaints as far as I'm aware. The migration should be well worth it, dozens of bugs fixed and maybe one or two introduced ;). The migration is not because of upstream but how Gentoo builds and installs Tomcat. It was shear luck that things still worked somewhat before. Though this doesn't excuse an insufficient warning, so I'd like to apologize once more for how things entered stable. |
