Lorenz Leutgeb

I would like to pick this up again, since I have a use-case for it. However, please @jhalterman re-read the changeset and proposals, and reformulate what should be done/how these...

@jhalterman you might want to consider closing this since #46 was merged, or is there something that I missed?

What's the status on this? It's the only thing that keeps me from rolling it out. Have you checked [this](https://blog.flo.cx/2012/09/cryptsetup-and-the-yubikey/) and respectively [flowolf/initramfs_ykfde](/flowolf/initramfs_ykfde)?

```diff --- cover2cover.py.old 2020-07-13 10:50:27.602377479 +0200 +++ cover2cover.new 2020-07-13 10:50:18.786395875 +0200 @@ -142,12 +143,12 @@ into = ET.Element('coverage') convert_root(root, into, source_roots) - print '' - print ET.tostring(into) + print('') +...

I also ran into this just now, assume `{a,b}.json` exist and are valid JSON, then consider the following snippet: ```jq import "./a" as $a; import "./b" as $b; def a:...

Please refer to [the diff I linked in the original post](https://github.com/composer/composer/compare/master...lorenzleutgeb:extsat#diff-57acde011ed9b5a18bb373af9d616bf1R232). I used what was already there :)

Unfortunately I cannot share the original `composer.json` with you, [just the formulas](https://github.com/composer/composer/files/1306507/composer-cnf.zip). We use Packagist and a self-hosted repository. Indeed, encoding these rules is not straightforward. By using policies to...

No need to, I think I'll manage. However, assuming that this will indeed lead to a performance gain, it would be nice get it upstream, provided that the changes will...

True, this should be tested for.

Some notes: 1. The [Common Upgradeability Description Format (CUDF)](http://www.mancoosi.org/cudf/) defines a format for package upgrade problems that is used to interface with some solvers. One issue with the format is...