ruro

No idea about how rpm packaging works. It looks like you need to declare the installed files explicitly in the `%files` directive? Regarding #3386, I have mentioned in the Disclaimer...

It seems this thread died? Can I help? I have the BW (classic) [without the Alternate]. The name is `Razer BlackWidow Classic`. The `capabilities` are {'name': True, 'type': True, 'firmware_version':...

> You can mount the non-legacy ones too with -o zfsutil. That is an internal flag that is not meant for end user use, although you will see initramfs archives...

You have convinced me that the current behaviour is correct. I guess, I'll just have to use `mountpoint=none` for the root dataset and then manually set `mountpoint=legacy` for all the...

I've seen that issue. Maybe I should have left a comment there instead of opening a new issue, but I think, that attempting to merge pre-generated `requirements.txt` from different environments...

> How about adding a `pip-combine` command that does receive a list of requirement files and produce a single one. With 5.2.0 we also include the python version used to...

> That is because you assumed the intermediate files do not have an implicit/invisible marker, but they would. No, that was not my point. Please, feel free to add the...

> just because I support an old version of Python that it does not? Yes. Exactly because you support a version of Python that doesn't have the newer package version....

> I don't want PyTest 4 on Python 3.10 if I happen to support Python 2.7. PyTest > and the previous contents of the compiled requirements.txt > > Why? Adding...

> The printed message, sure, but I believe the solve is unaffected by requirements.txt if requirements.in is supplied. ```sh > cat requirements.in pytest > cat requirements.txt # # This file...