[asdf-devel] Please test before releasing ASDF 3.0.0 - Also, resigning again

Faré fahree at gmail.com
Tue Apr 30 14:45:19 UTC 2013


This is bug worthy. Dunno that I have the courage to fix it before
3.0.0. Maybe a good target for procrastination, though.

—♯ƒ • François-René ÐVB Rideau •Reflection&Cybernethics• http://fare.tunes.org
You can tell whether a man is clever by his answers.
You can tell whether a man is wise by his questions. — Naguib Mahfouz


On Tue, Apr 30, 2013 at 10:40 AM, Stas Boukarev <stassats at gmail.com> wrote:
> Faré <fahree at gmail.com> writes:
>
>> On Tue, Apr 30, 2013 at 10:30 AM, Stas Boukarev <stassats at gmail.com> wrote:
>>>
>>> I also have a file /foo, if that m
>>
>> Yes, that probably matters. I don't remember exactly how things go,
>> but I believe that what's going on is that ASDF by default gets
>> truenames at every step, which causes this behaviour. I suppose it
>> should rather error out, expecting a directory pathname, than give
>> this answer.
>>
>> Also, this particular test should probably disable the truename resolution.
> Removing that file results in successful execution of tests.
>
> --
> With best regards, Stas.



More information about the asdf-devel mailing list