Cristian Le

> The library code is packaged into a cmake project, and consumed by others as a tarball (I use FetchContent for that). There is an infinite number of configurations, so...

> This error happens because we wrap the command as > > ``` > f"/bin/bash -c '{command}'" > ``` Should be documented with a `.. warning` Here's the gem I...

@igmar any progress on this? If we can get a Fedora+epel-9 it is already a major step. I can help guide some automation with packit if upstream wants to support...

I can disable the tag if you want. Just last time it was not uploaded to pypi

I think best way to design this is to read for `.mdformat.yaml` in each folder, and merge the options of the last given `.mdformat.yaml`. Then expose an option of a...

Consider #262 for a more complete implementation

In https://github.com/LecrisUT/atuin-rpmspec/tree/review/rust-dependencies, I am using: - `paths: [ atuin ]` - `specfile_path: atuin.spec` - `downstream_package_name: atuin` I want to get rid of the latter 2 (so that it looks like...

But that's the issue, the documentation indicates that it could be a supported design: > #### downstream_package_name > (string) Name of the RPM package in Fedora, defaults to the name...

> And have you any suggestion on what can be helpful to you to work more easily with the path and file_sync interaction? Have an option for `packit propose-downstream --dry-run...

Should note that the workaround described here is only for container runs