Hi all,
javamail ursine is using version 1.5.2 while there are some module streams at 1.6.x
The upstream project also moved to the eclipse foundation and these 1.6.x releases have different exports for OSGi, making an update to them potentially breaking for users.
I'd like to update ursine to 1.6.x, but I understand packages depending on them should be notified or some such. However I realized I don't know what commands to run to get a list of such and then where to send it. Could anyone advise?
Also, upstream repo was renamed: https://github.com/eclipse-ee4j/mail so maybe a new package 'mail' can be introduced to use it? Any thoughts there?
Thanks, Jie Kang
On Mon, Jun 29, 2020 at 4:06 PM Jie Kang jkang@redhat.com wrote:
Hi all,
javamail ursine is using version 1.5.2 while there are some module streams at 1.6.x
The upstream project also moved to the eclipse foundation and these 1.6.x releases have different exports for OSGi, making an update to them potentially breaking for users.
I'd like to update ursine to 1.6.x, but I understand packages depending on them should be notified or some such. However I realized I don't know what commands to run to get a list of such and then where to send it. Could anyone advise?
Also, upstream repo was renamed: https://github.com/eclipse-ee4j/mail so maybe a new package 'mail' can be introduced to use it? Any thoughts there?
I use this command to check for dependent packages:
$ dnf --repo rawhide --repo rawhide-source --releasever rawhide repoquery --whatrequires javamail
Which is enough, since there are no other subpackages except -javadoc. The command yielded (on July 1):
ant-0:1.10.8-1.fc33.src ant-javamail-0:1.10.8-1.fc33.noarch bouncycastle-0:1.65-2.fc33.src httpunit-0:1.7-29.fc32.src log4j-0:2.13.1-1.fc33.src log4j12-0:1.2.17-26.fc32.src openas2-0:2.10.0-2.fc33.src openas2-lib-0:2.10.0-2.fc33.noarch
So the list of affected packages seems to be:
- ant (Stewardship / Java SIG will deal with this) - bouncycastle (?) - httpunit (?) - log4j (Stewardship / Java SIG will deal with this) - log4j12 (Stewardship / Java SIG will deal with this) - openas2 (?)
I already had to adapt ant to use the "legacy" coordinates of javamail, so those changes can be reverted once it's updated. I'm not sure whether the other packages are similarly affected (I assume they are, and will require some `%pom_change_dep` or sed magic).
I suggest notifying the maintainers of the three "(?)" packages directly.
Fabio
On Wed, 1 Jul 2020 at 15:05, Fabio Valentini decathorpe@gmail.com wrote:
On Mon, Jun 29, 2020 at 4:06 PM Jie Kang jkang@redhat.com wrote:
Hi all,
javamail ursine is using version 1.5.2 while there are some module streams at 1.6.x
The upstream project also moved to the eclipse foundation and these 1.6.x releases have different exports for OSGi, making an update to them potentially breaking for users.
I'd like to update ursine to 1.6.x, but I understand packages depending on them should be notified or some such. However I realized I don't know what commands to run to get a list of such and then where to send it. Could anyone advise?
Also, upstream repo was renamed: https://github.com/eclipse-ee4j/mail so maybe a new package 'mail' can be introduced to use it? Any thoughts there?
I use this command to check for dependent packages:
$ dnf --repo rawhide --repo rawhide-source --releasever rawhide repoquery --whatrequires javamail
Which is enough, since there are no other subpackages except -javadoc. The command yielded (on July 1):
ant-0:1.10.8-1.fc33.src ant-javamail-0:1.10.8-1.fc33.noarch bouncycastle-0:1.65-2.fc33.src httpunit-0:1.7-29.fc32.src log4j-0:2.13.1-1.fc33.src log4j12-0:1.2.17-26.fc32.src openas2-0:2.10.0-2.fc33.src openas2-lib-0:2.10.0-2.fc33.noarch
So the list of affected packages seems to be:
- ant (Stewardship / Java SIG will deal with this)
- bouncycastle (?)
Bouncycastle is me (it is a dep of jgit). From reading the javamail "compat" document: https://javaee.github.io/javamail/docs/COMPAT.txt it looks like I probably will need to take no action at all.
Thanks for the insight and link Fabio and Mat. I'll look into the compatibility and verify if any changes need to be made and if so, contact the maintainers. Following a week or two for responses, I'll submit an update for rawhide.
Regards, Jie Kang Senior Software Engineer, Red Hat Canada
On Thu, Jul 2, 2020 at 5:54 AM Mat Booth fedora@matbooth.co.uk wrote:
On Wed, 1 Jul 2020 at 15:05, Fabio Valentini decathorpe@gmail.com wrote:
On Mon, Jun 29, 2020 at 4:06 PM Jie Kang jkang@redhat.com wrote:
Hi all,
javamail ursine is using version 1.5.2 while there are some module streams at 1.6.x
The upstream project also moved to the eclipse foundation and these 1.6.x releases have different exports for OSGi, making an update to them potentially breaking for users.
I'd like to update ursine to 1.6.x, but I understand packages depending on them should be notified or some such. However I realized I don't know what commands to run to get a list of such and then where to send it. Could anyone advise?
Also, upstream repo was renamed: https://github.com/eclipse-ee4j/mail so maybe a new package 'mail' can be introduced to use it? Any thoughts there?
I use this command to check for dependent packages:
$ dnf --repo rawhide --repo rawhide-source --releasever rawhide repoquery --whatrequires javamail
Which is enough, since there are no other subpackages except -javadoc. The command yielded (on July 1):
ant-0:1.10.8-1.fc33.src ant-javamail-0:1.10.8-1.fc33.noarch bouncycastle-0:1.65-2.fc33.src httpunit-0:1.7-29.fc32.src log4j-0:2.13.1-1.fc33.src log4j12-0:1.2.17-26.fc32.src openas2-0:2.10.0-2.fc33.src openas2-lib-0:2.10.0-2.fc33.noarch
So the list of affected packages seems to be:
- ant (Stewardship / Java SIG will deal with this)
- bouncycastle (?)
Bouncycastle is me (it is a dep of jgit). From reading the javamail "compat" document: https://javaee.github.io/javamail/docs/COMPAT.txt it looks like I probably will need to take no action at all.
devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Hey Mat,
On further investigation, the compatibility changes that require attention are made in javamail 1.6.3 and later, see:
https://eclipse-ee4j.github.io/mail/docs/COMPAT.txt
The maven coordinates are changed, generally javax -> jakarta. This also affects the osgi provides.
Regards, Jie Kang
On Thu, Jul 2, 2020 at 5:54 AM Mat Booth fedora@matbooth.co.uk wrote:
On Wed, 1 Jul 2020 at 15:05, Fabio Valentini decathorpe@gmail.com wrote:
On Mon, Jun 29, 2020 at 4:06 PM Jie Kang jkang@redhat.com wrote:
Hi all,
javamail ursine is using version 1.5.2 while there are some module streams at 1.6.x
The upstream project also moved to the eclipse foundation and these 1.6.x releases have different exports for OSGi, making an update to them potentially breaking for users.
I'd like to update ursine to 1.6.x, but I understand packages depending on them should be notified or some such. However I realized I don't know what commands to run to get a list of such and then where to send it. Could anyone advise?
Also, upstream repo was renamed: https://github.com/eclipse-ee4j/mail so maybe a new package 'mail' can be introduced to use it? Any thoughts there?
I use this command to check for dependent packages:
$ dnf --repo rawhide --repo rawhide-source --releasever rawhide repoquery --whatrequires javamail
Which is enough, since there are no other subpackages except -javadoc. The command yielded (on July 1):
ant-0:1.10.8-1.fc33.src ant-javamail-0:1.10.8-1.fc33.noarch bouncycastle-0:1.65-2.fc33.src httpunit-0:1.7-29.fc32.src log4j-0:2.13.1-1.fc33.src log4j12-0:1.2.17-26.fc32.src openas2-0:2.10.0-2.fc33.src openas2-lib-0:2.10.0-2.fc33.noarch
So the list of affected packages seems to be:
- ant (Stewardship / Java SIG will deal with this)
- bouncycastle (?)
Bouncycastle is me (it is a dep of jgit). From reading the javamail "compat" document: https://javaee.github.io/javamail/docs/COMPAT.txt it looks like I probably will need to take no action at all.
devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Sure, but when updating the javamail package, you will be providing compatibility aliases for the old maven coordinates using %mvn_alias and compatibility symlinks for the old filename using %mvn_file in order to not break dependent packages, right? Right? ;-)
Unless a package somehow is not using the felix-bundle-plugin or aqute-bnd, a simple rebuild should fix OSGi metadata (i.e. the next mass rebuild should take care of it).
On Mon, 6 Jul 2020 at 19:59, Jie Kang jkang@redhat.com wrote:
Hey Mat,
On further investigation, the compatibility changes that require attention are made in javamail 1.6.3 and later, see:
https://eclipse-ee4j.github.io/mail/docs/COMPAT.txt
The maven coordinates are changed, generally javax -> jakarta. This also affects the osgi provides.
Regards, Jie Kang
On Thu, Jul 2, 2020 at 5:54 AM Mat Booth fedora@matbooth.co.uk wrote:
On Wed, 1 Jul 2020 at 15:05, Fabio Valentini decathorpe@gmail.com
wrote:
On Mon, Jun 29, 2020 at 4:06 PM Jie Kang jkang@redhat.com wrote:
Hi all,
javamail ursine is using version 1.5.2 while there are some module streams at 1.6.x
The upstream project also moved to the eclipse foundation and these 1.6.x releases have different exports for OSGi, making an update to them potentially breaking for users.
I'd like to update ursine to 1.6.x, but I understand packages depending on them should be notified or some such. However I realized I don't know what commands to run to get a list of such and then where to send it. Could anyone advise?
Also, upstream repo was renamed: https://github.com/eclipse-ee4j/mail so maybe a new package 'mail' can be introduced to use it? Any thoughts there?
I use this command to check for dependent packages:
$ dnf --repo rawhide --repo rawhide-source --releasever rawhide repoquery --whatrequires javamail
Which is enough, since there are no other subpackages except -javadoc. The command yielded (on July 1):
ant-0:1.10.8-1.fc33.src ant-javamail-0:1.10.8-1.fc33.noarch bouncycastle-0:1.65-2.fc33.src httpunit-0:1.7-29.fc32.src log4j-0:2.13.1-1.fc33.src log4j12-0:1.2.17-26.fc32.src openas2-0:2.10.0-2.fc33.src openas2-lib-0:2.10.0-2.fc33.noarch
So the list of affected packages seems to be:
- ant (Stewardship / Java SIG will deal with this)
- bouncycastle (?)
Bouncycastle is me (it is a dep of jgit). From reading the javamail
"compat" document: https://javaee.github.io/javamail/docs/COMPAT.txt it looks like I probably will need to take no action at all.
devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-leave@lists.fedoraproject.org Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives:
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org _______________________________________________ java-devel mailing list -- java-devel@lists.fedoraproject.org To unsubscribe send an email to java-devel-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/java-devel@lists.fedoraproject...
java-devel@lists.fedoraproject.org
-
Fabio Valentini -
Jie Kang -
Mat Booth