Summary: | www-servers/tomcat-9.0.0_alpha6 : [javac] /.../ApplicationDispatcher.java:372: error: cannot find symbol | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Toralf Förster <toralf> |
Component: | Current packages | Assignee: | Java team <java> |
Status: | RESOLVED FIXED | ||
Severity: | normal | ||
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
emerge-history.txt
environment www-servers:tomcat-9.0.0_alpha6:20160517-133601.log |
Description
Toralf Förster
2016-05-17 13:45:01 UTC
Created attachment 434532 [details]
emerge-history.txt
Created attachment 434534 [details]
environment
Created attachment 434536 [details]
www-servers:tomcat-9.0.0_alpha6:20160517-133601.log
i did not check the source code yet but a quick guess. do you have tomcat-servlet-api-9.0.0_alpha6 installed? (In reply to Miroslav Šulc from comment #4) the already attached history mentions: Fri May 13 10:43:22 2016 >>> dev-java/tomcat-servlet-api-9.0.0_alpha4 (In reply to Toralf Förster from comment #5) > (In reply to Miroslav Šulc from comment #4) > the already attached history mentions: > > Fri May 13 10:43:22 2016 >>> dev-java/tomcat-servlet-api-9.0.0_alpha4 then it must be updated to alpha6 first. and only after that update tomcat to alpha6 too. closing the bug. if the problem persists, please reopen the isssue. (In reply to Miroslav Šulc from comment #6) > (In reply to Toralf Förster from comment #5) > > (In reply to Miroslav Šulc from comment #4) > > the already attached history mentions: > > > > Fri May 13 10:43:22 2016 >>> dev-java/tomcat-servlet-api-9.0.0_alpha4 > > then it must be updated to alpha6 first. and only after that update tomcat > to alpha6 too. Shouldn't the tomcat ebuild enforce this then? (In reply to James Le Cuirot from comment #8) > (In reply to Miroslav Šulc from comment #6) > > (In reply to Toralf Förster from comment #5) > > > (In reply to Miroslav Šulc from comment #4) > > > the already attached history mentions: > > > > > > Fri May 13 10:43:22 2016 >>> dev-java/tomcat-servlet-api-9.0.0_alpha4 > > > > then it must be updated to alpha6 first. and only after that update tomcat > > to alpha6 too. > > Shouldn't the tomcat ebuild enforce this then? it does for normal versions but not for _alpha, _beta etc. anyway, imo in this case the user did not update whole system but just tomcat ebuild (something like `emerge tomcat` instead of `emerge -uD tomcat` or @world) which caused the issue as otherwise tomcat-servlet-api would/should be updated aswell. also, there is no tomcat-servlet-api-9.0.0_alpha4 in the tree anymore as for these alphas i always rename the old version to the new one. i could change the ebuild so that for _alpha it requires strictly the same _alpha version but as i always remove the previous versions on bump, this issue occurs only when not updating the packages as it should be done. The tinderbox does an "emerge -u", no -D, right Why do alpha versions of tomcat rely on "-D" ? And why are alpha versions handled differently from non-alpha versions ? (FWIW @world is updated usually once a day with -uUDNU but that's not the point here). (In reply to Miroslav Šulc from comment #9) > (In reply to James Le Cuirot from comment #8) > > Shouldn't the tomcat ebuild enforce this then? > > it does for normal versions but not for _alpha, _beta etc. anyway, imo in > this case the user did not update whole system but just tomcat ebuild > (something like `emerge tomcat` instead of `emerge -uD tomcat` or @world) > which caused the issue as otherwise tomcat-servlet-api would/should be > updated aswell. also, there is no tomcat-servlet-api-9.0.0_alpha4 in the > tree anymore as for these alphas i always rename the old version to the new > one. i could change the ebuild so that for _alpha it requires strictly the > same _alpha version but as i always remove the previous versions on bump, > this issue occurs only when not updating the packages as it should be done. I partly agree in that I don't think you always need to specify a minimum version if you're reasonably confident that all the versions still in the tree will work. However, if a breaking version was only removed a very short time ago then I think you could be stricter. Not everyone updates their system in the same way. If anything, it probably should be stricter for pre-release versions because the API is more likely to change during this period. commit 2e69839ece70c6944eea30f352bfd53ef92f6047 Author: Miroslav Šulc <fordfrog@gentoo.org> Date: Thu May 19 08:02:28 2016 +0200 www-servers/tomcat: restricted dependency on tomcat-servlet-api to the exact version (bug #583292) Package-Manager: portage-2.3.0_rc1 |