December 2021 - asdf-devel - mailman3.common-lisp.net

Need to call asdf:load-system (or equivalent) from asdf:test-system
by Albus Matt Piroglu 29 Dec '21

29 Dec '21

Note I have opened an issue on gitlab, but I know it's an overkill to open issues for questions. I couldn't find an appropriate channel until I found this mailing list. I'll close the issue, and here is my question for your consideration: Hi, I'm trying to test a functionality that depends on loading systems. Thusly I ended up writing some tests that need to load a "test-system" during the tests, and I clear the system afterwards. A simplified code for the test in question is: (test check-the-system-is-loaded-as-expected () (asdf:load-system "my-test-system-under-test-folder") (is --check that the system loaded as expected--) (asdf:clear-system "my-test-system-under-test-folder") (delete-package "PACKAGE-FROM-TEST-SYSTEM")) and, to clarify, another test relies on the same system not being loaded, so I don't think a dependency would solve the issue, it is rather a dynamic decision to load or not. Now, I know that this feature is deprecated and may not work. What I'm wondering if there's a safer way to achieve this. Wouldn't some tests for asdf itself need loading some test systems for example? (hmm it actually might be a good idea to go check them now). OK, for example there's a hello-world-example.asd in test, which looks similar to my my-test-system-under-test-folder. So, instead of asdf:load-system in the above test code, should I be using a lower-level operation call? Thanks! Albus

3 4

:initform vs. :default-initargs
by Attila Lendvai 22 Dec '21

22 Dec '21

dear list, i wanted to set the default-component-class of our own system subclass using :default-initargs, but it's ignored because the slot has a :initform (as opposed to setting the default value using a :default-initargs entry). in the current ASDF setup, i need to override the slot (or the accessor method), which involves messing with internal symbols. if ASDF used :default-initargs then i could just override that using a :default-initargs entry on my own subclass (IIUC). https://lisptips.com/post/11728375873/initform-and-default-initargs i'm sending it for your consideration, it's not a pressing issue on my side. - attila PGP: 5D5F 45C7 DFCD 0A39

4 5

Re: ASDF tools/release.lisp and PGP keys
by Robert Goldman 22 Dec '21

22 Dec '21

Thanks for the note! I'm not sure what to do about this, since I don't use the "asdf/tools" myself. I never figured out how to debug the lisp scripts there, so I have stuck to the old code that is based on bash and make. That looks like code that is probably related to the creation of Debian packages for ASDF. No one has been doing that for years. I should probably prune the code for doing that.... Best, R On 22 Dec 2021, at 10:54, Attila Lendvai wrote: > Robert, > > i have this local diff: > > - (error "Please export variable DEBSIGN_KEYID to be the 8-hex hash of > your GnuPG secret key"))) > + (error "Please export variable DEBSIGN_KEYID to be the 16+ digit > hexadecimal hash of your GnuPG secret key"))) > > there's an ongoing attack against PGP keys where a white hat hacker is > brute-forcing the published keys to generate keys that have the same > hash/fingerprint, or at least the last 8 digits. > > luckily they also publish a revocation certificate for these fake > keys, but i recommend using longer than 8 digit fingerprints when > identifying PGP keys. > > just a head's up, probably not very urgent/relevant. > > - attila > PGP: 5D5F 45C7 DFCD 0A39

1 0