Feel free to contact me at my username at foldling.org, or visit my homepage for more info.
ticketprocedure currently supports retrieving tickets, but not adding or modifying them. It should be extended to work with the
I've added a
dust disablecommand that turns off the active CHICKEN version. This is included in version 0.0.13. Please give it a try and reopen this ticket if it doesn't work for you.
Thanks again for the suggestion!
REPORTED RESOLVED IMPLEMENTED
Fixed by c0663958.
REPORTED RESOLVED FIXED
Thank you for testing, that information was helpful. I've found and fixed the issue, and version 0.0.12 should work for you now. Please make sure you run these commands when trying again:chicken-uninstall -force dust begin-syntax module-declarations chicken-install -purge dust begin-syntax module-declarations chicken-install -force dust:0.0.12
We can leave this open now, and close it when it's implemented.
We could do that. However, it's not a high priority since there you can already build CHICKEN with a PREFIX set like you have shown there, as a workaround. So, this may be added, but probably not soon.
I don't want to change the filenames, but a dust off feature would be useful, good idea! It could simply remove the active link. I will try to add this.
Hi, thanks for the report!
This is interesting, the problem doesn't occur on the latest stable release of CHICKEN, so something must be different between version 5.2.0 and master. This may be related to #1548, I'll need to investigate.
I've reproduced this, but can you please confirm the bug doesn't appear for you on CHICKEN 5.2.0?
When using the artifacts POST API endpoint to attach a file to a ref in a repository, one can currently reuse a single filename for multiple uploads to different refs. In this case, the older file is overwritten and the URL for any artifacts attached with the same name to other refs becomes incorrect.
There should be an error when this is attempted, to avoid naming conflicts and incorrect attachment URLs.
The API does currently signal an error when one attempts to reuse a filename within the same ref. But, because the refs are stored in a single per-repository namespace, the API should also signal an error when a duplicate filename is used with a different ref.
Here is a concrete example where one version of a file was uploaded to
refs/tags/0.2.0, then another to
refs/tags/0.3.0with the same filename.