You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomcat.apache.org by bu...@apache.org on 2021/01/25 13:48:03 UTC
[Bug 65102] New: Build fails due to a lacking component
https://bz.apache.org/bugzilla/show_bug.cgi?id=65102
Bug ID: 65102
Summary: Build fails due to a lacking component
Product: Tomcat 9
Version: 9.0.41
Hardware: PC
Status: NEW
Severity: major
Priority: P2
Component: Catalina
Assignee: dev@tomcat.apache.org
Reporter: piotr.wyderski@aptitudesoftware.com
Target Milestone: -----
Hi,
I have just downloaded Tomcat sources for the version 9.0.41. The build fails
-- the build.properties refer to commons-daemon-1.2.3, but your server and the
mirrors host only commons-daemon-1.2.4. Please restore the old commons file or
update the dependencies, whichever fits you best.
Best regards, Piotr
testexist:
[echo] Testing for
/root/tomcat-build-libs/commons-daemon-1.2.3/commons-daemon-1.2.3.jar
downloadgz-2:
setproxy:
trydownload.check:
trydownload:
[get] Getting:
http://www.apache.org/dyn/closer.lua?action=download&filename=/commons/daemon/binaries/commons-daemon-1.2.3-bin.tar.gz
[get] To: /root/tomcat-build-libs/download-1961091249.tar.gz
[get]
http://www.apache.org/dyn/closer.lua?action=download&filename=/commons/daemon/binaries/commons-daemon-1.2.3-bin.tar.gz
moved to
https://apache.mirrors.tworzy.net//commons/daemon/binaries/commons-daemon-1.2.3-bin.tar.gz
[get] Error opening connection java.io.FileNotFoundException:
https://apache.mirrors.tworzy.net//commons/daemon/binaries/commons-daemon-1.2.3-bin.tar.gz
[get] Error opening connection java.io.FileNotFoundException:
https://apache.mirrors.tworzy.net//commons/daemon/binaries/commons-daemon-1.2.3-bin.tar.gz
[get] Error opening connection java.io.FileNotFoundException:
https://apache.mirrors.tworzy.net//commons/daemon/binaries/commons-daemon-1.2.3-bin.tar.gz
--
You are receiving this mail because:
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org
[Bug 65102] Build fails due to a lacking component
Posted by bu...@apache.org.
https://bz.apache.org/bugzilla/show_bug.cgi?id=65102
--- Comment #10 from mgrigorov <mg...@apache.org> ---
Would it be a good idea to download the dependencies from Maven Central instead
of the Apache download site ?
https://repo1.maven.org/maven2/commons-daemon/commons-daemon/
I am not suggesting to switch to Ant+Ivy!
--
You are receiving this mail because:
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org
[Bug 65102] Build fails due to a lacking component
Posted by bu...@apache.org.
https://bz.apache.org/bugzilla/show_bug.cgi?id=65102
--- Comment #5 from Mark Thomas <ma...@apache.org> ---
Looks like the http test in Ant's condition task (at least in 1.9.15) doesn't
behave they way the Tomcat build script expects it to when a URL first returns
a 302 and then a 404.
--
You are receiving this mail because:
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org
[Bug 65102] Build fails due to a lacking component
Posted by bu...@apache.org.
https://bz.apache.org/bugzilla/show_bug.cgi?id=65102
Mark Thomas <ma...@apache.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |INVALID
Status|NEW |RESOLVED
--- Comment #2 from Mark Thomas <ma...@apache.org> ---
9.0.41 depends on 1.2.3. Since that has been replaced by 1.2.4 you need to
either:
- configure the build, in build.properties, to point to the 1.2.3 release
(available from the ASF archives or Maven Central)
- configure the build, in build.properties to use 1.2.4
--
You are receiving this mail because:
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org
[Bug 65102] Build fails due to a lacking component
Posted by bu...@apache.org.
https://bz.apache.org/bugzilla/show_bug.cgi?id=65102
--- Comment #9 from Mark Thomas <ma...@apache.org> ---
ASF policy requires that the primary download site only contains the latest
version to reduce the space requirements for mirrors (they sync from the
primary download site).
All ASF releases will always be available from the ASF archive site.
--
You are receiving this mail because:
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org
[Bug 65102] Build fails due to a lacking component
Posted by bu...@apache.org.
https://bz.apache.org/bugzilla/show_bug.cgi?id=65102
--- Comment #3 from piotrw <pi...@aptitudesoftware.com> ---
I took the source package from your official website:
https://downloads.apache.org/tomcat/tomcat-9/v9.0.41/src/apache-tomcat-9.0.41-src.tar.gz
together with the signature file:
https://downloads.apache.org/tomcat/tomcat-9/v9.0.41/src/apache-tomcat-9.0.41-src.tar.gz.sha512
I have independently verified earlier that the fix you suggested (1.2.4 bump +
signature hash update) is sufficient to restore compilability. However, to me
the problem is not a minor issue, as it derails my automated build pipelines.
Using my modified source package is technically possible, but it adds a lot of
security-related paperwork. I need to formally explain why we are not using the
official package issued by the vendor etc. So if you could please issue a fixed
source package, it would help me a lot.
--
You are receiving this mail because:
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org
[Bug 65102] Build fails due to a lacking component
Posted by bu...@apache.org.
https://bz.apache.org/bugzilla/show_bug.cgi?id=65102
--- Comment #4 from Mark Thomas <ma...@apache.org> ---
Sorry, not going to happen. ASF releases are immutable.
The release of Commons Daemon 1.2.4 (which removed 1.2.3 from the mirrors)
should have triggered the build process to download the file from archive. I'm
currently not sure why that isn't happening.
--
You are receiving this mail because:
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org
[Bug 65102] Build fails due to a lacking component
Posted by bu...@apache.org.
https://bz.apache.org/bugzilla/show_bug.cgi?id=65102
Christopher Schultz <ch...@christopherschultz.net> changed:
What |Removed |Added
----------------------------------------------------------------------------
OS| |All
Component|Catalina |Packaging
--- Comment #1 from Christopher Schultz <ch...@christopherschultz.net> ---
Where did you get your source distro?
If you edit build.properties.default and change the following line, you should
be able to build:
- commons-daemon.version=1.2.3
+ commons-daemon.version=1.2.4
If your build is validating the signatures, you will have to update those or
disable the signing.
The current git main branch looks good to me.
--
You are receiving this mail because:
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org
[Bug 65102] Build fails due to a lacking component
Posted by bu...@apache.org.
https://bz.apache.org/bugzilla/show_bug.cgi?id=65102
--- Comment #8 from piotrw <pi...@aptitudesoftware.com> ---
So why don't you just restore the 1.2.3 on your mirrors and leave the source
bundle as it is? Why can't you host it together with 1.2.4 for one month
longer?
--
You are receiving this mail because:
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org
[Bug 65102] Build fails due to a lacking component
Posted by bu...@apache.org.
https://bz.apache.org/bugzilla/show_bug.cgi?id=65102
--- Comment #6 from Mark Thomas <ma...@apache.org> ---
An alternative work-around appears to be changing base-apache.loc.1 to use
https rather than http. You can probably argue that as a security improvement.
Still looking into the root cause of this difference in behaviour.
--
You are receiving this mail because:
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org
[Bug 65102] Build fails due to a lacking component
Posted by bu...@apache.org.
https://bz.apache.org/bugzilla/show_bug.cgi?id=65102
--- Comment #7 from Mark Thomas <ma...@apache.org> ---
https://bz.apache.org/bugzilla/show_bug.cgi?id=65105
The latest Tomcat source has already worked around this problem.
--
You are receiving this mail because:
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org
[Bug 65102] Build fails due to a lacking component
Posted by bu...@apache.org.
https://bz.apache.org/bugzilla/show_bug.cgi?id=65102
--- Comment #11 from Christopher Schultz <ch...@christopherschultz.net> ---
There's always the "ASF releases are immutable" problem. This is not a release
fro distant history, so it would be good to find a way to allow 9.0.41 source
distribution to build if at all possible.
Switching download sites can't be done because the URLs are already baked-into
the source release.
Is it at all possible to fix this on the server-side? I think probably not, as
the problem is with a failure to redirect properly. How about a fix in the ant
side (cf bug #65105).
--
You are receiving this mail because:
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org