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.tar.gz + > .debian.tar.gz), this is wrong, isn't it? > Yeah, that was a mistake. I used to just dpkg-buildpackage -rfakeroot and it was doing it all for me, but when I retried lately, it was not doing the .orig.tar.gz for me (anymore?). In any case, I created a second "upstream" branch to my repository, identical to "master", so that git-buildpackage seems to be working. Le sigh.
Can you see if it works now? Problem is, cl-launch 3 depends on asdf 2, so it's not immediately helpful to upload cl-launch before asdf is updated. That said, cl-launch 2 is probably already broken by asdf 1.704, so you may as well upload it now and things will magically work when asdf 2 is finally uploaded. [ François-René ÐVB Rideau | Reflection&Cybernethics | http://fare.tunes.org ] The worst thing that can happen to a good cause is, not to be skillfully attacked, but to be ineptly defended. — F. Bastiat _______________________________________________ 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
