[MIR] taglibs-standard [demote to universe] jakarta-taglibs-standard

[Gianfranco Costamagna]

Availability:
- Already in universe and available on all archs (java).

Rationale:
- New tomcat8 needs it, and seems to be a better library instead of the old jakarta version
(I didn't investigate this, but Debian switched it and there should be a good reason, I completely trust Emmanuel here)

Security:
- No files installed suid, sgid.
- No binaries installed in sbin.
- Not a plugin to security sensitive software.
- Not a daemon or opening a sensitive port.

Quality assurance:
- Should work without configuration.
- No debconf questions.
- Never had a bug in Debian and Ubuntu.

 The status of important bugs in Debian's, Ubuntu's, and upstream's bug tracking systems must be evaluated. Links to these bug trackers need to be provided in the MIR report. Important bugs must be pointed out and discussed in the MIR report.
https://bugs.debian.org/cgi-bin/pkgreport.cgi?ordering=normal;archive=0;src=taglibs-standard;dist=unstable;repeatmerged=0 - No open bugs found.

UI standards:
Not applicable.

Dependencies:
I don't think we have issues, since there seems to be no runtime dependencies on universe packages.

Standards compliance:
Should meet standard, no lintian overrides or warnings.

Maintenance:
Simple package, low maintenance effort, and maintained well in Debian.

Background information:
New tomcat8 requires it.

[Gianfranco Costamagna (costamagnagianfranco)]

and AFAICS jakarta-taglibs-standard can move back to universe

[Iain Lane (laney)]

On Mon, Sep 26, 2016 at 08:23:21AM -0000, Launchpad Bug Tracker wrote:
> You have been subscribed to a public bug by LocutusOfBorg (costamagnagianfranco):
>
> Availability:
> - Already in universe and available on all archs (java).
>
> Rationale:
> - New tomcat8 needs it, and seems to be a better library instead of the old jakarta version
> (I didn't investigate this, but Debian switched it and there should be a good reason, I completely trust Emmanuel here)

I can't comment on the MIR (but maybe talk to the server team about that,
since you will be asking them to maintain taglibs-standard), but for the
new version it might be easier to revert the change for the first
upload - so you can decouple it from this request.

--
Iain Lane [ <email address hidden> ]
Debian Developer [ <email address hidden> ]
Ubuntu Developer [ <email address hidden> ]

[Gianfranco Costamagna (costamagnagianfranco)]

Hi Laney, I'm not sure where to forward the request to server team (maybe I suscribed the team correctly).

There is no real need to sync it right now, we can MIR and sync post-yakkety

[Matthias Klose (doko)]

now uploaded, fyi, the following packages can be demoted with this:

 o jakarta-taglibs-standard: libjakarta-taglibs-standard-java libjstl1.1-java
 o libjaxp1.3-java: libjaxp1.3-java libjaxp1.3-java-gcj
 o libxalan2-java: libxalan2-java libxalan2-java-doc
 o libxerces2-java: libxerces2-java libxerces2-java-doc libxerces2-java-gcj
 o libxml-commons-resolver1.1-java: libxml-commons-resolver1.1-java libxml-commons-resolver1.1-java-doc libxml-commons-resolver1.1-java-gcj
 o xml-commons-external: libxml-commons-external-java libxml-commons-external-java-doc

[Mathieu Trudel-Lapierre (cyphermox)]

This was already promoted as it seems to be a source renamed from jakarta-taglibs-standard; however it does also rename the provided binaries, which would force a transition for any packages (build-)depending on them:

* jetty8
* libspring-java
* tomcat7
* shiro

Fortunately jakarta-tagslibs-standard is still in the archive.

I see no other issues with this MIR; furthermore this was already reviewed in 2012 for the tomcat7/jakarta-taglibs-standard MIR.

[Matthias Klose (doko)]

closing, server team is subscribed.