Your message dated Fri, 13 Oct 2017 19:21:00 +0200
with message-id <[email protected]>
and subject line Re: RFS: cl-asdf/3.3.0 - Another System Definition Facility
has caused the Debian Bug report #878167,
regarding RFS: cl-asdf/2:3.3.0-1 - Another System Definition Facility
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
878167: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=878167
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: sponsorship-requests
Severity: normal
Dear mentors,
I have packaged the new upstream release 3.3.0 of the Common Lisp ASDF
software:
Package name : cl-asdf
Version : 2:3.3.0-1
Upstream Author : Robert P. Goldman <[email protected]>
URL : https://common-lisp.net/project/asdf/
License : Expat
Section : lisp
The cl-asdf source package builds this binary package:
cl-asdf - Another System Definition Facility
The package appears to be lintian clean apart from a
orig-tarball-missing-upstream-signature
warning which I cannot fix due to building the package from git with gbp.
To access further information about this package, please visit the following
URL:
http://mentors.debian.net/package/cl-asdf
Alternatively, one can download the package with dget using this command:
dget -x
http://mentors.debian.net/debian/pool/main/c/cl-asdf/cl-asdf_3.3.0-1.dsc
Changes since the last upload:
cl-asdf (2:3.3.0-1) unstable; urgency=medium
Package changes:
* Update Standards-Version to 4.1.1
New upstream milestone:
* Build-plan: Extensively revised the build plan process so that
:DEFSYSTEM-DEPENDS-ON would work correctly, even when depended on systems
change (which didn't work before). See our ELS demonstration about it:
"Delivering Common Lisp Applications with ASDF 3.3"
< https://github.com/fare/asdf2017 >
* Internals: to support the above, many ASDF internals have changed.
ASDF now has the notion of multiple build phases to a common build session
(which generalizes the previous build cache). ASDF considers loading a .asd
file as an operation DEFINE-OP, and tracks as dependencies files mentioned
during in :LOAD-FILE-FORM statements, etc. Some code has moved to new
files or among old files, and between packages. Actions are now
uniformly represented as a CONS of an OPERATION and a COMPONENT, where
in some cases previously only the class of the operation was
preserved. Forcing is constrained to be uniform across all phases of a
top level ASDF operation invocation. Fixed the protocol for
resetting systems being (re)defined, allowing subclasses to define
default slot values. Remove *LOAD-SYSTEM-OPERATION*, as the current
maintainer of ECL, for which it was originally designed, decided
that it could never be made to work properly, after all.
* ASDF&UIOP: Tweak dependencies between ASDF and UIOP. To avoid DEFINE-OP
circularity, asdf.asd with no longer causes uiop.asd to be loaded.
A standalone UIOP won't be loaded at all unless it's strictly more recent
than ASDF.
* Tests: tests for new capabilities and bugs. Test backtraces can be disabled.
* Documentation: a number of improvements and clarifications.
* Feature: a new feature :asdf3.3
* ECL: restored the deprecated function MAKE-BUILD, removed in 3.2.0,
in a way that works on top of supported APIs (we still recommend you migrate
to these supported APIs). Also stop using the deprecated COMPUTE-INIT-NAME.
* Deprecation: starting to emit STYLE-WARNINGs for deprecated
functions. Will gradually escalate to true WARNINGs and then ERRORs.
Thank you
Kambiz Darabi
--
m-creations gmbh
Acker 2
55116 Mainz
Germany
--- End Message ---
--- Begin Message ---
On Fri, Oct 13, 2017 at 05:40:48PM +0200, Kambiz Darabi wrote:
>
> > Thanks. However it looks like you forgot to push the upstream branch
> > and the tags. Could you please do so?
>
> Done.
I have uploaded the package (with a few modifications that you can see in the
changelog; I also deleted the changelog entry for 2:3.2.0-1, since that version
never existed, and merged its content with the new entry).
A few more questions (to be addressed in future versions, at your convenience):
- documenting upstream changes in debian/changelog is not common practice.
Normally that file documents packaging changes, and upstream changelog
documents upstream changes. I see that upstream changelog (in doc/ChangeLog)
looks like a debian changelog, which is rather confusing, so I understand
that you prefer not to ship it. In any case, do as you see fit.
- there are many people listed in the Uploaders field, but you seem to be the
only one active. The others should probably be removed, unless you think some
of them could contribute again to the maintenance?
- in the future, as said before, just push your changes to the git, and send a
mail to [email protected]. Hopefully someone will
upload the package (I personally intend to be active in the team for some
time).
Thanks for your contribution to Debian.
Best,
--
⢀⣴⠾⠻⢶⣦⠀ Sébastien Villemot
⣾⠁⢠⠒⠀⣿⡁ Debian Developer
⢿⡄⠘⠷⠚⠋⠀ http://sebastien.villemot.name
⠈⠳⣄⠀⠀⠀⠀ http://www.debian.org
signature.asc
Description: PGP signature
--- End Message ---
