Well, libtomcat7-java conflicts with libtomcat6-java. So, the update of this dependency in libjetty-extra-java will remove libtomcat6-java and any packages that depend on it. That's the only regression I could think of.
But then I've checked the dependencies with aptitude:
monsta@mint17 ~ $ aptitude why libtomcat6-java
i anacron Recommends rsyslog | system-log-daemon
p syslog-ng-core Provides system-log-daemon
p syslog-ng-core Suggests syslog-ng-mod-stomp
p syslog-ng-mod-stomp Suggests activemq
p activemq Depends libactivemq-java (= 5.6.0+dfsg-1)
p libactivemq-java Depends libspring-context-java
p libspring-context-java Recommends libtomcat6-java
So, it shows no packages that directly depend on libtomcat6-java.
I don't mind :)
Well, libtomcat7-java conflicts with libtomcat6-java. So, the update of this dependency in libjetty-extra-java will remove libtomcat6-java and any packages that depend on it. That's the only regression I could think of.
But then I've checked the dependencies with aptitude:
monsta@mint17 ~ $ aptitude why libtomcat6-java context- java context- java Recommends libtomcat6-java
i anacron Recommends rsyslog | system-log-daemon
p syslog-ng-core Provides system-log-daemon
p syslog-ng-core Suggests syslog-ng-mod-stomp
p syslog-ng-mod-stomp Suggests activemq
p activemq Depends libactivemq-java (= 5.6.0+dfsg-1)
p libactivemq-java Depends libspring-
p libspring-
So, it shows no packages that directly depend on libtomcat6-java.