Bug#925533: libspring-java: stopped building libspring-jms-java and libspring-messaging-java

Source: libspring-java Version: 4.3.22-2 Severity: serious X-Debbugs-Cc: tony mancill Control: block 925390 924635 924634 by -1 Dear maintainer (and tony, whose upload 4.3.22-2 caused this bug), your package libspring-java suddenly stopped building two binaries that were actively used by other p

Bug#925533: libspring-java: stopped building libspring-jms-java and libspring-messaging-java

On Tue, 26 Mar 2019 14:46:35 +0100 Mattia Rizzolo wrote: > Dear maintainer (and tony, whose upload 4.3.22-2 caused this bug), > > your package libspring-java suddenly stopped building two binaries that > were actively used by other packages, like activemq. > > What's very worse, the changelog d

Bug#925533: libspring-java: stopped building libspring-jms-java and libspring-messaging-java

On Tue, Mar 26, 2019 at 02:46:35PM +0100, Mattia Rizzolo wrote: > Source: libspring-java > Version: 4.3.22-2 > Severity: serious > X-Debbugs-Cc: tony mancill > Control: block 925390 924635 924634 by -1 > > Dear maintainer (and tony, whose upload 4.3.22-2 caused this bug), > > your package libspr

Bug#925533: libspring-java: stopped building libspring-jms-java and libspring-messaging-java

On Tue, Mar 26, 2019 at 04:35:41PM -0700, tony mancill wrote: > Are you sure about the upload of 4.3.22-2 changing the number of binary > packages built? If that is the case, it was completely unintentional. Meh, apparently nope, I was tricked by that dpkg change in the Binary field... I had only

Bug#925533: libspring-java: stopped building libspring-jms-java and libspring-messaging-java

On Wed, 27 Mar 2019 12:01:40 +0100 Mattia Rizzolo wrote: > On Tue, Mar 26, 2019 at 04:35:41PM -0700, tony mancill wrote: > > Are you sure about the upload of 4.3.22-2 changing the number of binary > > packages built? If that is the case, it was completely unintentional. > > Meh, apparently nope,

Bug#925533: libspring-java: stopped building libspring-jms-java and libspring-messaging-java

On Tue, 26 Mar 2019 16:35:41 -0700 tony mancill wrote: > Regarding the OpenHFT, I tried to help the overall situation by > uploading new versions to experimental several months back but as was > discussed on the list (I'd have to find the link), was requested to > hold-off on transitioning them in

Bug#925533: libspring-java: stopped building libspring-jms-java and libspring-messaging-java

On Tue, 26 Mar 2019 15:27:38 +0100 Emmanuel Bourg wrote:> I think this was done to remove the openhft packages that are > incompatible with Java 11. But maybe the affected Spring modules could > be salvaged by disabling the code using openhft (if it's optional). I’m not entirely sure it is possib

Bug#925533: libspring-java: stopped building libspring-jms-java and libspring-messaging-java

On Wed, Mar 27, 2019 at 12:37:17PM +0100, Andrej Shadura wrote: > > (srly? Using dh -N instead of removing the packages from d/control?!…). > > Yes, so that it’s easier to bring them back when they’re unbroken. But that doesn't help anything. You removed two packages because a dependency of the

Bug#925533: libspring-java: stopped building libspring-jms-java and libspring-messaging-java

Le 27/03/2019 à 12:41, Andrej Shadura a écrit : > I’m not entirely sure it is possible. But maybe someone else is going to > have better luck removing openhft dependencies. I'll get a look during the Paris BSP on sunday. Emmanuel Bourg __ This is the maintainer address of Debian's Java team