Bug#793911: groovy should not release with stretch
Hi Markus, On Fri, Dec 11, 2015 at 09:23:42PM +0100, Markus Koschany wrote: > > we can always consider to fix red5 with a NMU. We just should raise the > severity accordingly before we do that. Sure, that's a valid option. An NMU to DELAYED/7 or something is OK with me. > I hope I can lend you a hand with an update of libspring-java after I > have packaged the latest netbeans release. Perhaps you can write a short > TODO list and push it to the libspring-java repo, which upstream should > be packaged, if we have to package new dependencies and where you need > help. OK, unfortunately I don't have too much time lately but I think I can review latest Spring upstream releases to document if/which new dependencies are needed and push that to the repo. Cheers, -- Miguel Landaeta, nomadium at debian.org secure email with PGP 0x6E608B637D8967E9 available at http://miguel.cc/key. "Faith means not wanting to know what is true." -- Nietzsche signature.asc Description: Digital signature
Bug#793911: groovy should not release with stretch
Le 11/12/2015 21:16, Miguel Landaeta a écrit : > To package libspring-java new upstream releases is a task that would > be very appreciated although is not easy but with the recent progress > in Maven and Gradle helpers (thanks to Emmanuel again!) maybe this is > something more feasible nowadays. I should have mentioned that I'm working on upgrading libspring-java to the version 4.0.9, I'm almost done. I confirm that gradle-debian-helper renders the task much easier! Emmanuel
Bug#793911: groovy should not release with stretch
Le 11/12/2015 22:49, Miguel Landaeta a écrit : > OK, unfortunately I don't have too much time lately but I think I can > review latest Spring upstream releases to document if/which new > dependencies are needed and push that to the repo. I've packaged most the new dependencies required by Spring 4.0.x except: - com.jayway.jsonpath:json-path:0.9.1 - org.apache.taglibs:taglibs-standard-jstlel:1.2.1 I haven't checked the new dependencies for Spring 4.1 yet. Emmanuel Bourg
Bug#793911: groovy should not release with stretch
Am 11.12.2015 um 22:49 schrieb Miguel Landaeta: > Hi Markus, > > On Fri, Dec 11, 2015 at 09:23:42PM +0100, Markus Koschany wrote: >> >> we can always consider to fix red5 with a NMU. We just should raise the >> severity accordingly before we do that. > > Sure, that's a valid option. An NMU to DELAYED/7 or something is OK > with me. I suggest to raise the severity of red5 to serious as soon as we have fixed libspring-java and it remains the only package left. Then we should give the maintainer at least ten days to fix the issue (according to the NMU guide lines) and after that it is fire at will. >> I hope I can lend you a hand with an update of libspring-java after I >> have packaged the latest netbeans release. Perhaps you can write a short >> TODO list and push it to the libspring-java repo, which upstream should >> be packaged, if we have to package new dependencies and where you need >> help. > > OK, unfortunately I don't have too much time lately but I think I can > review latest Spring upstream releases to document if/which new > dependencies are needed and push that to the repo. No problem. I just read Emmanuel's comment. If you need some help with the packaging, just ping me. Like I said I intend to work on Netbeans, maven-repo-helper (#805228) and Eclipse in the near future but there is hopefully always some time to package a new dependency. :E Markus signature.asc Description: OpenPGP digital signature
Bug#793911: groovy should not release with stretch
Hi Markus, On Sat, Nov 28, 2015 at 01:53:03PM +0100, Markus Koschany wrote: > > [...] > > These are the current reverse dependencies in unstable: > > libspring-java -> must be updated to a newer version I already pushed some trivial changes to the repo to migrate libspring-java to groovy2. > jenkins -> unmaintainable, can be ignored > > It bothers me jenkins package status but I'm not in a position to > help at this moment. > > red5 -> must be updated to a newer version Emmanuel sent a patch for this. Please see #805627. > If you want to update either libspring-java or red5, that would be a big > help. To package libspring-java new upstream releases is a task that would be very appreciated although is not easy but with the recent progress in Maven and Gradle helpers (thanks to Emmanuel again!) maybe this is something more feasible nowadays. Regarding red5, I'm not quite sure how much is used in Debian nowadays. Maybe we should contact Damien to check if he agrees to transfer its maintenance to pkg-java. I'm ccing him just in case. Cheers, -- Miguel Landaeta, nomadium at debian.org secure email with PGP 0x6E608B637D8967E9 available at http://miguel.cc/key. "Faith means not wanting to know what is true." -- Nietzsche signature.asc Description: Digital signature
Bug#793911: groovy should not release with stretch
Am 11.12.2015 um 21:16 schrieb Miguel Landaeta: [...] >> red5 -> must be updated to a newer version > > Emmanuel sent a patch for this. Please see #805627. > >> If you want to update either libspring-java or red5, that would be a big >> help. > > To package libspring-java new upstream releases is a task that would > be very appreciated although is not easy but with the recent progress > in Maven and Gradle helpers (thanks to Emmanuel again!) maybe this is > something more feasible nowadays. > > Regarding red5, I'm not quite sure how much is used in Debian > nowadays. Maybe we should contact Damien to check if he agrees to > transfer its maintenance to pkg-java. I'm ccing him just in case. Hi, we can always consider to fix red5 with a NMU. We just should raise the severity accordingly before we do that. I hope I can lend you a hand with an update of libspring-java after I have packaged the latest netbeans release. Perhaps you can write a short TODO list and push it to the libspring-java repo, which upstream should be packaged, if we have to package new dependencies and where you need help. Cheers, Markus signature.asc Description: OpenPGP digital signature
Bug#793911: groovy should not release with stretch
On Thu, 1 Oct 2015 23:38:11 +0800 =?UTF-8?B?5q635ZWf6IGw?=wrote: > On Tue, 28 Jul 2015 22:38:40 +0200 Moritz Muehlenhoff wrote: > > Package: groovy > > Severity: serious > > > > A separate source package groovy2 was uploaded, so reverse dependencies > > need to be migrated to that one and groovy removed. > > > > Cheers, > > Moritz > > > > > > Hi Moritz and all pkg-java members, > > I am wondering if it is better to upgrade groovy to the latest version > (2.4.5 as of now) and drop groovy2, and migrate all build-rdeps of old > Groovy 1.x to using a separate groovy-1.8 or groovy-1.9 package if > necessary. In the end that we get rid of groovy and remain a groovy2 > package seems odd. Anyway BND, Maven are under the similar transition. > Since GSoC I have been maintaining Gradle in Debian so I am happy and > willing to do the transition. Hi Kai-Chung, I think upgrading src:groovy to version 2.x is a good idea. Though it is more important that we upgrade all reverse dependencies of groovy 1.x to to groovy 2.x first, so that we can drop one source package before the Stretch release. These are the current reverse dependencies in unstable: freemind -> will be removed from Debian soon because we have a very similar package already (freeplane) libspring-java -> must be updated to a newer version jenkins -> unmaintainable, can be ignored red5 -> must be updated to a newer version If you want to update either libspring-java or red5, that would be a big help. Regards, Markus signature.asc Description: OpenPGP digital signature
Bug#793911: groovy should not release with stretch
On Tue, 28 Jul 2015 22:38:40 +0200 Moritz Muehlenhoffwrote: > Package: groovy > Severity: serious > > A separate source package groovy2 was uploaded, so reverse dependencies > need to be migrated to that one and groovy removed. > > Cheers, > Moritz > > Hi Moritz and all pkg-java members, I am wondering if it is better to upgrade groovy to the latest version (2.4.5 as of now) and drop groovy2, and migrate all build-rdeps of old Groovy 1.x to using a separate groovy-1.8 or groovy-1.9 package if necessary. In the end that we get rid of groovy and remain a groovy2 package seems odd. Anyway BND, Maven are under the similar transition. Since GSoC I have been maintaining Gradle in Debian so I am happy and willing to do the transition. Cheers, Kai-Chung Yan
Bug#793911: groovy should not release with stretch
Package: groovy Severity: serious A separate source package groovy2 was uploaded, so reverse dependencies need to be migrated to that one and groovy removed. Cheers, Moritz -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org