This bug was fixed in the package tomcat8 - 8.5.39-1ubuntu1~18.10
---
tomcat8 (8.5.39-1ubuntu1~18.10) cosmic; urgency=medium
[ Matthias Klose ]
* Backport for OpenJDK 11. LP: #1817567.
* tomcat8 now uses systemd service instead of init scripts. See
/usr/share/doc/tomcat8/NEW
This bug was fixed in the package tomcat8 - 8.5.39-1ubuntu1~18.04.1
---
tomcat8 (8.5.39-1ubuntu1~18.04.1) bionic; urgency=medium
[ Matthias Klose ]
* Backport for OpenJDK 11. LP: #1817567.
/usr/share/doc/tomcat8/NEWS.gz. LP: #1819721.
[ Tiago Stürmer Daitx ]
* debian/tomc
Hello Matthias, or anyone else affected,
Accepted tomcat8 into cosmic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/tomcat8/8.5.39-1ubuntu1~18.10 in a
few hours, and then in the -proposed repository.
Please help us by testing this new package. See
Steve, thank you, that sounds great from our perspective!
Dimitri, I would have no objections against a change like this in a new
version of Ubuntu. That said, I do understand that I'm not entitled to
set requirements for something I'm not paying for.
FWIW, the change we have to the Tomcat 8 init
based on discussion with Tiago this afternoon, I understand we have
agreement to revert the addition of the systemd unit in this SRU in
order to maximize compatibility with existing local configuration
changes.
** Changed in: tomcat8 (Ubuntu)
Status: Confirmed => Triaged
** Changed in: tom
That is for the future.
W.r.t. SRU, i don't know if it is ok to do init.d -> systemd switch in
an SRU. And if it's ok to do it without support existing (GA-time)
config files, or not.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
ht
@Sebastian (slovdahl)
Well, you have customized init.d scripts and added local features to it,
which is not something that Ubuntu can know about, nor has to support.
There are obvious ways how you can continue to support those things in
an automated manner. For example, you can dpkg-divert systemd
Tiago,
Thank you for helping out!
Unfortunately, that doesn't work out of the box in our case. The reason
is how our tomcat8.local currently is used. We have some sane defaults
in /etc/default/tomcat8 that Puppet manages, and use
/etc/default/tomcat8.local to make it possible to override it local
Sebastian,
thank you for taking the time to report this bug and helping to make
Ubuntu better.
For a systemd service you can easily override it and to modify/add
options. As an example, you should be able to achieve a similar result
to what you describe by using:
/etc/systemd/system/tomcat.servi
@Mathias - do you consider that a blocker that makes you re-modify the
ongoing SRU in bug 1817567 ?
I don't see a SRU Template or regression potential discussion here -
even thou being only released to -security would that be needed and
address these concerns?
I'm flagging as regression-proposed
This change has the potential to be a showstopper in some cases.
We're managing Tomcat on a lot of servers using Puppet. Puppet currently
installs slightly modified /etc/init.d/tomcat8 and /etc/default/tomcat8
files. The changed init.d file adds support for e.g. reading a
/etc/default/tomcat8.loca
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: tomcat8 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1819721
Title:
to
A community user reported a startup delay for tomcat8, guessing missing
entropy at the start?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1819721
Title:
tomcat8 SRU for bionic uses systemd service
13 matches
Mail list logo
