Skip to content
GitLab
Explore
Sign in
Register
Primary navigation
Search or go to…
Project
A
asdf
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Package registry
Model registry
Operate
Environments
Terraform modules
Monitor
Incidents
Service Desk
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Terms and privacy
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
Tarn Burton
asdf
Commits
2d7d5472
Commit
2d7d5472
authored
9 years ago
by
Robert Goldman
Browse files
Options
Downloads
Patches
Plain Diff
Changelog entry for 3.1.6.
parent
9da0f637
No related branches found
No related tags found
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
debian/changelog
+17
-0
17 additions, 0 deletions
debian/changelog
with
17 additions
and
0 deletions
debian/changelog
+
17
−
0
View file @
2d7d5472
cl-asdf (2:3.1.6-1) unstable; urgency=low
Bug fix and portability release:
* Fix backtrace on SBCL.
* Fix RUN-PROGRAM of string (shell command) on Windows SBCL (ticket
#1501373).
* Fix a number of issues with bundle operations (especially on
non-C-compiler-based implementations).
* Fix component-finding in package-inferred-system.
* Fix race condition between multiple concurrent lisp processes
doing ASDF builds (ticket #1483948).
* Fix misplaced fasl cache on Windows.
* Miscellaneous bug fixes.
* Documentation improvements.
-- Robert P. Goldman <rpgoldman@sift.net> Sat, 17 Oct 2015 15:01:34 -0500
cl-asdf (2:3.1.5-1) unstable; urgency=low
Bug fix and portability release:
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment