On 2021-01-20 12:58, Lucas Nussbaum wrote:
Source: leiningen-clojure
Version: 2.9.1-3
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20210120 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant pa
Thanks for the report.
Looks like libcommons-io-java has been updated to 2.8.0.[1] We'll need
to patch both the Debian build and send a PR upstream to get it on the
newer version.
- e
[1]: https://packages.debian.org/sid/libcommons-io-java
signature.asc
Description: PGP signature
On Tue, Sep 22, 2020 at 08:56:25PM +1000, Dmitry Smirnov wrote:
>
> As discussed in debian-devel, Kubernetes package abuses Debian practices
> and Golang team policies by needlessly vendoring hundreds(!) of libraries,
> most of which are available in Debian.
>
> For a complex package like Kubern
On Sat, Feb 23, 2019 at 06:34:53PM -0500, Elana Hashman wrote:
> So this weekend I am going to look into changing the build to more
> closely match upstream, now that we've bootstrapped a working
> Leiningen into the archive. This would involve building Leiningen with
> a pr
On Sun, Feb 24, 2019 at 04:31:08PM +, Santiago Vila wrote:
>
> I tried to build this package in buster but it failed:
>
>
> [INFO] Scanning for projects...
> [INFO]
> [INFO] ---< leiningen-core:l
On Tue, Jan 22, 2019 at 05:39:46PM -0800, Phil Hagelberg wrote:
>
> It looks like it's been fixed in newer versions of Clojure, but we
> haven't bumped that in Leiningen yet.
Note that this has been fixed upstream in the 2.9.0 release. I've been
trying to upgrade Leiningen in Debian to this new r
On 2019-01-21 14:49, Moritz Mühlenhoff wrote:
We can only support one OpenJDK relase in a stable release and that
version
will be openjdk-11. I'm bumping the severity back to serious.
Cheers,
Moritz
So here's the issue with Leiningen and Java 11. We previously tracked
down some sor
The patch to fix this was already applied to clojure1.8. I just need to
do it for 1.9.
I've been sick all weekend or else this'd be done already. Now instead I
am drowning in AUTORM emails :'(
Cheers,
- e
signature.asc
Description: Digital signature
Hi Emilio,
Why was this bug filed as serious? Leiningen has a direct dependency on
Java 8 and upstream has not yet been updated to use a newer version of
Java, as the public Java 11 builds aren't really available yet. I had to
pin the build to Java 8 as it does not work properly with Java 9+ yet.
Thanks for reopening this! Not sure why the clojure1.8 changelog marked
it as done, as it specified the issues were only partially addressed. I
will be uploading all the bd fixes for leiningen and its multitude of
dependencies in the next day or two :)
- e
signature.asc
Description: Digital sign
Control: tags sid
Hi Adrian! Thanks for your report. The Clojure Team was aware of this
bug but has not yet fixed it.
Leiningen is not compatible with Clojure >1.8 as a build dependency.
This is why I blocked the new Clojure 1.9 alpha from migrating to
testing (#887382).
Hence, this bug doesn't
Package: clojure
Version: 1.9.0~alpha15-1
Severity: serious
This alpha version of Clojure 1.9.0 was uploaded to facilitate packaging
the official 1.9.0 release. As such, I need to prevent it from migrating
to testing for now.
signature.asc
Description: Digital signature
Package: libcore-cache-clojure
Version: 0.6.5-1
Severity: grave
Justification: renders package unusable
Control: block -1 by 855722
Hello!
While working on packaging libstencil-clojure, I noticed that the
dependency org.clojure/data.priority-map was missing, and traced it down
to this package:
On 2017-05-10 10:14, Adrian Bunk wrote:
Package: libpomegranate-clojure
Version: 0.3.1-1
Severity: serious
libpomegranate-clojure 0.2.0-1 has:
Depends: libaether-java, libdynapath-clojure, libwagon-java,
libwagon2-java, maven
libpomegranate-clojure 0.3.1-1 has no dependencies at all.
Hi Adria
Package: libpomegranate-clojure
Version: 0.3.1-1
Severity: grave
Justification: renders package unusable
Control: block 819811 by -1
libpomegranate-clojure 0.2.0 and 0.3.1 depend on Maven 3.0.4. However,
only 3.3.9 is available in stretch and sid. When I attempt to use the
package, I get a ClassN
15 matches
Mail list logo
