On Mon, Jun 20, 2022 at 05:31:16PM -0700, Sean Whitton wrote:
> Hello,
>
> I hereby call for votes on the following resolution:
>
> BEGIN BALLOT
>
> Using its powers under constitution 6.1.5, the Technical Committee
> issues the following advice:
>
> 1. It is not a bug of any severity for a p
Package: wnpp
X-Debbugs-Cc: ehash...@debian.org
Severity: wishlist
* Package name: test-generative-clojure
Version : 1.0.0
Upstream Author : Rich Hickey
* URL : https://github.com/clojure/test.generative
* License : EPL-1.0
Programming Lang: Clojure
Descript
nue in the role if the committee agrees.
>
> The ballot:
>
> ===BEGIN
>
> A: Christoph Berg
> B: Helmut Grohne
> C: Elana Hashman
> D: Simon McVittie
> E: Niko Tyni
> F: Matthew Vernon
> G: Sean Whitton
> H: Gunnar Wolf
>
> ===END
My apolog
On Fri, Jan 14, 2022 at 11:56:20AM -0700, Sean Whitton wrote:
>
> ===BEGIN
> The Technical Committee recommends that Matthew Vernon be
> appointed by the Debian Project Leader to the Technical Committee.
>
> H: Recommend to Appoint Matthew Vernon
> F: Further Discussion
> ===END
I vote:
H > F
On Fri, Jan 14, 2022 at 11:55:17AM -0700, Sean Whitton wrote:
>
> ===BEGIN
> The Technical Committee recommends that Helmut Grohne be
> appointed by the Debian Project Leader to the Technical Committee.
>
> H: Recommend to Appoint Helmut Grohne
> F: Further Discussion
> ===END
I vote:
H > F
On Wed, Oct 13, 2021 at 08:13:08PM +0100, Simon McVittie wrote:
> I'm calling for votes on the following resolution as formal advice from
> the Technical Committee (Constitution §6.1.5). There are no non-accepted
> amendments, so the options to vote on are "yes" or "further discussion".
I vote (be
On Wed, Oct 20, 2021 at 12:30:54PM -0700, Sean Whitton wrote:
> Hello,
>
> I hereby call for votes on the following ballot to resolve #994275. The
> voting period starts immediately and lasts for up to one week, or until
> the outcome is no longer in doubt (Constitution 6.3.1).
>
> === Resolutio
Control: reassign -1 wnpp
Control: retitle -1 RFP: docker-buildx -- docker CLI plugin for BuildKit
* Package name: docker-buildx
Version: 0.5.1
Upstream Author: https://github.com/docker/buildx/blob/master/AUTHORS
* URL: https://github.com/docker/buildx
* License: Apache 2.0
Description: Doc
Package: docker.io
X-Debbugs-Cc: ehash...@debian.org
Version: 20.10.5+dfsg1-1+b3
Severity: important
When I try to run the `docker buildx build` command, even with experimental
features enabled, it fails:
ehashman@fedora:~$ docker buildx build
docker: 'buildx' is not a docker command.
See 'docker
takes effect.
>
> The ballot is the following:
>
> ===BEGIN===
>
> The chair of the Debian Technical Committee will be:
>
> A : Margarita Manterola
> B : David Bremner
> C : Niko Tyni
> D : Gunnar Wolf
> E : Simon McVittie
> F : Sean Whitton
> G
On 2021-03-10 11:34, Alexander Wirt wrote:
On Tue, Sep 22, 2020 at 10:04:39AM -0700, Elana Hashman wrote:
On Tue, Sep 22, 2020 at 02:02:40PM +0200, Alexander Wirt wrote:
>
> ehm, but you asked on the list if subscribers should get subscribed to
> the new list?
I did upon initial lis
On 2021-03-06 11:11, Jakub Wilk wrote:
* Elana Hashman , 2021-02-17, 11:06:
Would you be able to research some representative slice of popular
packages that would be affected by the policy change (at least 10) and
share the on-disk sizes with compression vs. without?
Not exactly what you
On Thu, 25 Feb 2021 09:58:36 +0100 Paul Gevers wrote:
>
> On 25-02-2021 07:17, Stefano Rivera wrote:
> > TL;DR: Debian heard of some upstream Python grumpyness about our
> > standard library splits, recently.
>
> We have more upstreams being grumpy how we handle things in Debian.
>
> > This is a
On Wed, Feb 17, 2021 at 12:45:05PM -0600, Gunnar Wolf wrote:
> ===BEGIN
>
> The Technical Committee recommends that Christoph Berg be
> appointed by the Debian Project Leader to the Technical Committee.
>
> A: Recommend to appoint Christoph Berg
> B: Further Discussion
>
> ===END
I have not w
Hi Niels,
Most of the arguments in this and previous bugs are anecdotal. It would
be helpful to provide a concrete analysis of the disk space savings that
compression provides, and whether it is a reasonable default.
There is a discussion about KDE debug symbols requiring 10Gi of disk
space a dec
On Mon, Jan 25, 2021 at 11:45:55AM -0700, Sean Whitton wrote:
> Dear Technical Committee members,
>
> I call for votes on the following ballot to resolve #978636. The voting
> period starts immediately and lasts for up to one week, or until the
> outcome is no longer in doubt (§6.3.1).
>
> ===BE
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
On Thu, Nov 19, 2020 at 09:04:00PM -0800, Elana Hashman wrote:
>
> I caution folks from speculating too much on the maintainer's
> motivations and reasoning while they haven't yet had a chance to share
> their perspective on the bug. :)
>
> From what I can see read
On Wed, Nov 18, 2020 at 11:36:09AM -0600, Gunnar Wolf wrote:
> ...
> I'm pasting here a bit of the discussion that happened later during
> the meeting: having this discussion K8S-specific, Elana mentioned that
> "that is a big part of the tension. sometimes, you have an upstream
> where the authors
On Thu, Nov 19, 2020 at 04:20:46PM -0800, Tianon Gravi wrote:
>
> On Wed, 18 Nov 2020 at 23:33, Josh Triplett wrote:
> > Any inclusion of work into a package necessitates *some* amount of
> > development and packaging resources by the maintainer of that package.
> > Even if someone else offers to
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 Tue, Sep 22, 2020 at 02:02:40PM +0200, Alexander Wirt wrote:
>
> ehm, but you asked on the list if subscribers should get subscribed to
> the new list?
I did upon initial list request but it's been over a year. Would you
like me to ask again? (The list should be CC'd so this is pretty
transpa
On Thu, Sep 10, 2020 at 09:52:40PM +0200, Alexander Wirt wrote:
>
> Sorry for joining late. Could you please upgrade the list of subscribers
> and provide me with the archive of the old alioth list?
No problem. I'm attaching another encrypted dump of the subscriber list.
The archives are publicl
> The ballot is the following:
>
> ===BEGIN===
>
> The chair of the Debian Technical Committee will be:
>
> A : Philip Hands
> B : Margarita Manterola
> C : David Bremner
> D : Niko Tyni
> E : Gunnar Wolf
> F : Simon McVittie
> G : Sean Whitton
Okay, latest version is now 0.8.677. Let's reevaluate what's required for
packaging.
`lein deps :tree` now says:
[org.clojure/tools.deps.alpha "0.8.677"]
;; I'm going to ignore these for now
[com.cognitect.aws/api "0.8.408"]
[com.cognitect/http-client "0.1.101"]
[org.eclipse.
Latest upstream version is now 1.10.1.536 with a dependency on
clojure.deps.alpha 0.8.677.
signature.asc
Description: PGP signature
On Thu, Apr 18, 2019 at 12:12:58PM +0200, Paul Gevers wrote:
>
> I think you want the whole package to disappear from Debian (well,
> unstable *and* testing I mean), right?
Yes, that's right.
> The issue in this case is the version of tools-nrepl-clojure package
> in testing, so I have added an
Source: pomegranate-clojure
Version: 1.1.0+really-1
Severity: normal
Current pomegranate-clojure autopkgtests depend on clojure1.8 which is
being RM'd. This has caused an autopkgtest regression in testing where
clojure1.8 has been removed.
Tests have no particular dependency on a Clojure version
Package: release.debian.org
User: release.debian@packages.debian.org
Usertags: rm
Severity: normal
This package was initially uploaded because leiningen-clojure was pinned
to Clojure 1.8 while the clojure package was updated to 1.9 and onward.
clojure/1.10 is currently in testing and leiningen
Package: libpomegranate-clojure
Version: 1.1.0-1
Severity: normal
Control: block 900299 by -1
Apparently I got the wrong upstream commit when tagging the release
because this is what's showing up in the maven repo for
libpomegranate-clojure_1.1.0-1:
ehashman@corn-syrup:~$ ls /usr/share/maven-repo
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 Thu, Feb 14, 2019 at 04:45:48PM +0100, Paul Gevers wrote:
> autopkgtest [12:11:27]: test hello-nrepl: [---
> WARNING: requiring-resolve already refers to:
> #'clojure.core/requiring-resolve in namespace: user, being replaced by:
> #'nrepl.misc/requiring-resolve
> "e7d1e44b-65
On Sun, Feb 10, 2019 at 08:15:27PM -0600, Alex Miller wrote:
>
> It's also easy to fix in the code in question by excluding the `cat`
> name from clojure.core to avoid the shadowing, but it's not required.
>
> Would just add cat to the list of excluded symbols here:
> https://github.com/cgrand/re
Package: libregex-clojure
Version: 1.1.0-2
Severity: minor
When libregex-clojure is loaded, the following warning is printed:
WARNING: cat already refers to: #'clojure.core/cat in namespace:
net.cgrand.regex, being replaced by: #'net.cgrand.regex/cat
I believe this behaviour is also present in
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
Package: wnpp
Owner: Elana Hashman
Severity: wishlist
* Package name: nrepl-clojure
Version : 0.5.3
Upstream Author : 2010-2018 Chas Emerick, Bozhidar Batsov and
contributors
* URL : https://nrepl.org/
* License : EPL-1.0
Programming Lang: Clojure
Package: wnpp
Owner: Elana Hashman
Severity: wishlist
* Package name: lua-fennel
Version : 0.2.0
Upstream Author : Calvin Rose
* URL : https://fennel-lang.org/
* License : MIT
Programming Lang: Lua
Description : a lisp that compiles to Lua
Fennel is
Just wanted to check in on this, it's been a few months :)
signature.asc
Description: PGP signature
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
On 2018-06-04 10:19, Emilio Pozuelo Monfort wrote:
OpenJDK 8 will be EOL sometime in 2020 (Red Hat will drop support for
it in
October 2020). With a buster release in mid 2019, that would only be a
little
over one year into buster's release. With 3 years of main support, that
won't be
enough.
Apologies for the slightly delayed reply, this got sent to my spam...
On Wed, Sep 05, 2018 at 11:34:40PM +, Santiago Vila wrote:
>
> The failure happens randomly, approximately half of the time, but it also
> happened here on armhf:
>
> https://tests.reproducible-builds.org/debian/rb-pkg/bus
On Mon, Aug 20, 2018 at 08:33:46AM +0100, Chris Lamb wrote:
>
> This is because you disabled the running of strip-nondeterminism
Ehhh this is not exactly true. At the time we turned this off due to
#877418. However, Clojure itself does not actually produce reproducible
bytecode[*] most of the tim
On Sun, Aug 05, 2018 at 04:21:53PM -0400, Elana Hashman wrote:
> Please upgrade data-xml-clojure to 0.2.0-alpha5.
Currently, Leiningen depends on 0.0.8 directly. I don't think that
0.2.0-alpha5 would break any 0.0.8 APIs (Clojure is notorious for
their backwards-compatible guarantees)
Source: jgit
Severity: wishlist
Control: block 891136 by -1
Please upgrade jgit to 4.10.0. This version is required for packaging
tools-deps-alpha-clojure, the new upstream dependency resolver that is
required to package the new upstream Clojure CLI.
Upgrading to this version would also appear to
Source: jsch-agent-proxy
Severity: wishlist
Control: block 891136 by -1
Please upgrade jsch-agent-proxy to 0.0.9. This version is required for
packaging tools-deps-alpha-clojure, the new upstream dependency
resolver that is required to package the new upstream Clojure CLI.
signature.asc
Descript
Source: data-xml-clojure
Severity: wishlist
Control: block 891136 by -1
Please upgrade data-xml-clojure to 0.2.0-alpha5. This version is
required for packaging tools-deps-alpha-clojure, the new upstream
dependency resolver that is required to package the new upstream
Clojure CLI.
signature.asc
D
Package: wnpp
Owner: Elana Hashman
Severity: wishlist
Control: block 891136 by -1
* Package name: tools-gitlibs-clojure
Version : 0.2.64
Upstream Author : Rich Hickey
* URL : https://github.com/clojure/tools.gitlibs
* License : EPL-1.0
Programming Lang
So I was thinking about this, because the vast majority of the work
consists of new uploads for S3 support... namely:
> - s3-wagon-private "1.3.1"
> - com.amazonaws/aws-java-sdk-core "1.11.184"
> - com.amazonaws/aws-java-sdk-kms "1.11.184"
> - com.amazonaws/aws-java-sdk-s3 "1.11.184"
> - software.
Okay, since I got a bug report about this, let's take a look at this
again for the latest tools.deps.alpha release 0.5.422. From deps.edn:
org.clojure/clojure {:mvn/version "1.9.0"}
* Good here: https://tracker.debian.org/pkg/clojure
org.apache.maven.resolver/maven-resolver-api {:mvn/version "1.
Hi Daniel,
Thanks for the report! My apologies for not getting back to you
sooner; the maintainer email for Clojure was incorrect so I didn't
receive a copy of this bug. I just uploaded a fix for that today.
I would like to package the new Clojure CLI scripts, and have an ITP
open here: https://
Package: lists.debian.org
Severity: wishlist
Hello!
I realize that alioth-lists.debian.net is only a temporary service and
will be going away within the next couple of years[1]. It would be
better to move the Clojure packaging list
sooner versus later.
I'm currently the admin of that list.
This
Package: debian-policy
Version: 4.2.0.0
Severity: normal
NEWS.Debian files are listed in the "unofficial policy"[1] but not in
the official policy.
It seems this was proposed in 2002[2], but in 2003, folks were
hesitant to "[get] this into policy until enough stuff uses it that we
can tell it wor
On 2018-07-22 16:29, Jérémy Lal wrote:
You lost me a little here.
From what i understand, there are only two general solutions:
1.a build from source at install time
Yup, by building from source, you typically avoid any ABI compatibility
issues by surfacing them at build time.
1.b build fro
On 2018-07-22 13:35, Jérémy Lal wrote:
Forwarded: https://github.com/nodejs/node/issues/21897
Yup, I've read through this as well.
I agree there is a problem. I disagree the problem is only on the
distributor side.
I also agree that the problem isn't only on the distributor side, *but*
I
Package: nodejs
Version: 8.10.0~dfsg-2
Severity: important
This bug was initially reported downstream against Ubuntu in
https://bugs.launchpad.net/ubuntu/+source/nodejs/+bug/1779863 by the
upstream GRPC maintainer.
Summary of the issue: upstream nodejs vendors its openssl dependency and
expo
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.
Package: dput-ng
Version: 1.18
Severity: minor
When I run `dcut upload`, the output returned makes me unsure if my
commands file actually got uploaded:
ehashman@corn-syrup:~/debian$ dcut upload -f do-a-thing.commands
Uploading commands file to ftp.upload.debian.org (incoming: /pub/UploadQueue/)
Okay, this dependency tree is a lot hairier than I initially expected.
`lein deps :tree` says:
[org.clojure/tools.deps.alpha "0.5.398"]
[org.apache.maven.resolver/maven-resolver-api "1.1.1"]
[org.apache.maven.resolver/maven-resolver-connector-basic "1.1.1"]
[org.apache.maven.resolver/ma
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
This ITP is currently blocked on
https://dev.clojure.org/jira/browse/TDEPS-44
Upstream depends on a version of Maven that is unavailable in the
archive. Because of significant API changes between Maven 3.3.9
(currently required) and Maven 3.5 (in Debian), it doesn't make sense
for me to attempt a
Package: wnpp
Severity: wishlist
Owner: Elana Hashman
Control: block -1 by 891136
* Package name: clojure-cli
Version : 1.9.0.341
Upstream Author : Rich Hickey
* URL : https://github.com/clojure/brew-install
* License : EPL-1.0
Description : upstream CLI
Package: wnpp
Owner: Elana Hashman
Severity: wishlist
* Package name: tools-deps-alpha-clojure
Version : 0.5.393
Upstream Author : Rich Hickey
* URL : https://github.com/clojure/tools.deps.alpha
* License : EPL-1.0
Programming Lang: Clojure
Description
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: clojure
Version: 1.8.0-3
Severity: wishlist
Owner: Elana Hashman
Control: block -1 by 886561 886562
Now that Clojure 1.9 is available, we should package it.
Clojure 1.9 is the first Clojure release that consists of more than one
jar. Before we can package this version, we must also
Package: wnpp
Severity: wishlist
Owner: Elana Hashman
* Package name: core-specs-alpha-clojure
Version : 0.1.24
Upstream Author : Rich Hickey
* URL : https://github.com/clojure/core.specs.alpha
* License : EPL-1.0
Programming Lang: Clojure
Description
Package: wnpp
Owner: Elana Hashman
Severity: wishlist
* Package name: spec-alpha-clojure
Version : 0.1.143
Upstream Author : Rich Hickey
* URL : https://github.com/clojure/spec.alpha
* License : EPL-1.0
Programming Lang: Clojure
Description : library
For those that have been waiting for updates on this, I realize I have
mostly been sending updates to pkg-clojure-maintainers, so let me also
comment directly on the bug!
I have preliminary packaging that builds up at
https://anonscm.debian.org/git/pkg-clojure/leiningen-clojure.git/
Hopefully wil
Package: libplexus-utils-java
Version: 1:1.5.15-4
Severity: wishlist
Control: block 819811 by -1
To facilitate packaging leiningen2, this package needs an upgrade to
version 3.0.24. This turns out to be a dependency of
libpomegranate-clojure via libmaven-resolver-java, which has a suggested
de
Hi all, just catching up on this thread.
FWIW I agree with Apollon; as rlb pointed out on IRC, we introduce a
potential race condition when we don't recompile when the timestamps are
equal. Quoting him...
The scenario I was thinking of is "clock ticks over to 1001s, I
compile foo.clj -
Package: libwagon2-java
Version: 2.12-3
It appears that the package ".poms" file explicitly excludes building
wagon-ssh for libwagon2-java:
https://anonscm.debian.org/cgit/pkg-java/wagon2.git/tree/debian/libwagon2-java.poms#n37
However, libpomegranate-clojure has a(n optional) dependency on t
All,
We are getting very close!
I have completed packaging for the three outstanding blocking bugs:
- #862233: use maven 3.5.0 and upgrade to pomegranate 0.4.0-alpha1
https://anonscm.debian.org/cgit/pkg-clojure/pomegranate-clojure.git/
-- this
one is complicated, wanted a few more eyes bef
On Mon, May 15, 2017 at 09:13:43AM +0200, Emmanuel Bourg wrote:
>
> Hi Elana,
>
> I plan to start working on Maven 3.5 after the Stretch release.
>
> Did you try building pomegranate with libaether-java? If it works we can
> keep it in Debian even if it is abandoned upstream.
>
> Emmanuel Bourg
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:
Package: libmaven3-core-java
Version: 3.3.9-4
Severity: wishlist
Control: block 862233 by -1
To facilitate packaging leiningen2, this package needs an upgrade to
version 3.5.0.
This is because its dependency libpomegranate-clojure currently depends
on a version of maven much older than availa
Finished packaging...
https://anonscm.debian.org/cgit/pkg-clojure/parsley-clojure.git/
https://csclub.uwaterloo.ca/~ehashman/debian/libparsley-clojure/
Just need someone to check this over and sponsor,
- e
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
I mentioned this on IRC, but also wanted to send a message out to the bug list
for posterity...
I've hit a bit of a snag with the libpomegranate-clojure packaging (#852246).
While I did get the package to build, it doesn't actually work. I realized it
relies on maven 3.0.4, which is only packag
Owner: Elana Hashman
Hi all,
Phil has done a bunch of great work significantly reducing the
dependency profile of leiningen, so I have updated all the blocking
issues and we are down to 8.
Of those, two are addressed by packages sitting in NEW and I will have
more to follow. I wrote a
Package: libwagon2-java
Version: 2.10-6
Severity: wishlist
Control: block 819811 by -1
To facilitate packaging leiningen2, this package needs an upgrade to
version 2.12. Phil Hagelberg says this version is needed to fix a bug
with self-signed certificates.
Hello package maintainers!
I've taken a look at the packaging of the current version and it appears
to use maven. I'd like to help upgrade it, but I've never made a maven
package before.
This looks a bit more complicated than using just javahelper, so I'm
wondering if you would accept a pack
I have built a working package for version 0.2.0:
https://github.com/ehashman/pedantic
https://csclub.uwaterloo.ca/~ehashman/debian/libpedantic-clojure/
You can test it by installing the package and attempting an import in
the REPL:
$ clojure -cp /usr/share/java/pedantic.jar
Clojure 1.8.0
use
On 2017-02-28 23:37, Elana Hashman wrote:
Hi,
I took a stab at packaging this. This is my first package submitted to
Debian so I don't know what I'm doing.
All the debian/ stuff can be found here:
https://github.com/ehashman/classlojure
Let me know what you think!
- e
Oh,
Control: retitle -1 ITP: libclasslojure-clojure -- Clojure library to
create a classloader with an alternate classpath
Hi,
I took a stab at packaging this. This is my first package submitted to
Debian so I don't know what I'm doing.
All the debian/ stuff can be found here:
https://github.co
All the first-degree dependencies should now be marked as blocking. Now
for some packaging...
There are a lot of deps and granddeps so if you're interested in helping
out, please feel free to claim one (or many)!
- e
Package: wnpp
Severity: wishlist
Control: block 819811 by -1
* Package name: libreply-clojure
Version : 0.3.7
Upstream Author : Colin Jones
* URL : https://github.com/trptcolin/reply
* License : EPL 1.0
Programming Lang: Clojure
Description : A fitter,
On 2017-01-19 16:12, Tom Marble wrote:
I've created a new page on the Debian wiki for this purpose:
https://wiki.debian.org/Clojure/Leiningen
Thanks for the great work on the wiki page, Tom, Phil!
I've gone ahead and filed version upgrade requests as blocking this bug
for all the packages id
Package: libjline2-java
Version: 2.11-4
Severity: wishlist
Control: block 819811 by -1
To facilitate packaging leiningen2, this package needs an upgrade to
version 2.12.1.
Package: libregex-clojure
Version: 0.0~git20130321.1.433265f-3
Severity: wishlist
Control: block 819811 by -1
To facilitate packaging leiningen2, this package needs an upgrade to
version 1.1.0.
Package: libtools-cli-clojure
Version: 0.2.4-3
Severity: wishlist
Control: block 819811 by -1
To facilitate packaging leiningen2, this package needs an upgrade to
version 0.3.1.
Package: libclj-stacktrace-clojure
Version: 0.2.6-3
Severity: wishlist
Control: block 819811 by -1
To facilitate packaging leiningen2, this package needs an upgrade to
version 0.2.7.
Package: libpomegranate-clojure
Version: 0.2.0-1
Severity: wishlist
Control: block 819811 by -1
To facilitate packaging leiningen2, this package needs an upgrade to
version 0.3.1.
Package: libbultitude-clojure
Version: 0.2.7-1
Severity: wishlist
Control: block 819811 by -1
To facilitate packaging leiningen2, this package needs an upgrade to
version 0.2.8.
Package: libslingshot-clojure
Version: 0.10.3-4
Severity: wishlist
Control: block 819811 by -1
To facilitate packaging leiningen2, this package needs an upgrade to
version 0.12.2.
Hello!
Finally following up with some conversations I had at Clojure/conj, I'd
like to help get the ball rolling on this again. Based on leiningen
2.7.1's dependencies, here's what we'll need to package/upgrade to make
this happen.
Packages that have a higher version in Debian unstable than
Package: krb5-kdc
Version: 1.12.1+dfsg-19+deb8u1
Severity: normal
Hi again!
I configured Kerberos to log to some specific locations:
(from /etc/krb5.conf:)
...
[logging]
kdc = FILE:/var/log/krb5kdc.log
admin_server = FILE:/var/log/kadmin.log
default = FILE:/var/log/krb5.log
However
1 - 100 of 103 matches
Mail list logo
