Uploaded. BTW, it might be useful to add me to cl-asdf Uploaders.
___
pkg-common-lisp-devel mailing list
pkg-common-lisp-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/pkg-common-lisp-devel
Also, note that for cl-asdf, I'm currently not using the git repo on
alioth (that is slowly bitrotting), but directly the upstream git
repo, with tag RELEASE and branch release being used as respective
upstream and debian trees in make targets.
[ François-René ÐVB Rideau | Reflection&Cybernethics
On 19 August 2010 04:41, Milan Zamazal wrote:
>> "F" == Faré writes:
>
> F> Note that if you already uploaded anything to any official repo,
>
> Not yet.
>
> F> LICENSE is created by the Makefile, and I don't know the correct
> F> way to tell git-buildpackage to ignore it.
>
> Isn't
> "F" == Faré writes:
F> Note that if you already uploaded anything to any official repo,
Not yet.
F> LICENSE is created by the Makefile, and I don't know the correct
F> way to tell git-buildpackage to ignore it.
Isn't it possible to remove it in `clean' target?
On 18 August 2010 04:26, Milan Zamazal wrote:
>> "F" == Faré writes:
>
> F> I've just uploaded ASDF 2.005 and CL-Launch 3.001.
>
> Some comments:
>
> - You should always check current Standards version (and changes) and
> put it in debian/control.
>
> - You should switch to source format
> "F" == Faré writes:
F> I've just uploaded ASDF 2.005 and CL-Launch 3.001.
Some comments:
- You should always check current Standards version (and changes) and
put it in debian/control.
- You should switch to source format 3.0 (probably nothing more than
editing debian/source/f
On 28 July 2010 04:58, Milan Zamazal wrote:
>> "F" == Faré writes:
>
> F> Can you or someone please update cl-asdf and cl-launch while it's
> F> still time?
>
> Done.
>
I've just uploaded ASDF 2.005 and CL-Launch 3.001.
In addition to many minor upstream bug fixes and features, the
pac
> "F" == Faré writes:
F> Can you or someone please update cl-asdf and cl-launch while it's
F> still time?
Done.
___
pkg-common-lisp-devel mailing list
pkg-common-lisp-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/
Faré writes:
> Can you or someone please update cl-asdf and cl-launch while it's
> still time? It would be an embarrassment to have the broken and
> already obsolete asdf 1.704 in stable with the incompatible cl-launch
> 2.32 with it.
Hi!
If it's still open on August 3rd I can take a look (e
Can you or someone please update cl-asdf and cl-launch while it's
still time? It would be an embarrassment to have the broken and
already obsolete asdf 1.704 in stable with the incompatible cl-launch
2.32 with it.
[ François-René ÐVB Rideau | Reflection&Cybernethics | http://fare.tunes.org ]
And h
> "F" == Faré writes:
F> Problem is, cl-launch 3 depends on asdf 2, so it's not
F> immediately helpful to upload cl-launch before asdf is
F> updated. That said, cl-launch 2 is probably already broken by
F> asdf 1.704, so you may as well upload it now and things will
F> ma
Dear Milan,
> F> I uploaded packages for cl-asdf 2.004 and cl-launch 3.000 to
> F> mentors. Can someone with proper privileges give a look and
> F> bless them?
>
> I can handle cl-launch. However this has been uploaded to mentors as a
> native Debian package (.tar.gz instead of .orig.ta
> "F" == Faré writes:
F> I uploaded packages for cl-asdf 2.004 and cl-launch 3.000 to
F> mentors. Can someone with proper privileges give a look and
F> bless them?
I can handle cl-launch. However this has been uploaded to mentors as a
native Debian package (.tar.gz instead of
13 matches
Mail list logo
