Pavel Raiskup

FWIW, tito project itself has the problem now: ``` $ sudo dnf copr enable @rpm-software-management/tito $ sudo dnf update tito ...nothing happens... ``` the version in Copr is 0.6.24-1.fc39 compared...

For me, this is hard to predict. Can we simply try that? Seems like a nice experiment.

Just tried to chain build the client Copr packages from git-head: mock --chain \ /tmp/tito/python-copr-1.132-1.git.75.658230d.fc41.src.rpm \ /tmp/tito/copr-cli-1.112-1.git.78.658230d.fc41.src.rpm But for the `copr-cli` package it always installs: python3-copr noarch 1.132-3.fc41 fedora 241.8...

Note that `pyproject.toml` file is a standard file, something like `setup.py` and templating it is quite complicated task (you most probably need to copy-paste the content and maintain both the...

Example: https://github.com/fedora-copr/resalloc-ibm-cloud/blob/main/pyproject.toml

~~Note the inconvenience -- this may lead to a non-reproducible release tarball generator (the changelog file is usually baked into the tarball). The feature should be documented with appropriate warnings.~~...

The problem is that `setup.py` is added to the `git archive` tarball. And we don't want to modify it on the fly - or maybe, do we? But that would...

Applied ```diff From 4f41eec5e0cf6fa2f8bbf0fdc902a035c35496c3 Mon Sep 17 00:00:00 2001 From: Pavel Raiskup Date: Fri, 19 May 2023 15:36:39 +0200 Subject: [PATCH] Initialized to use tito. --- .tito/packages/.readme | 3 +++...

The `tito build --srpm --test` works: `Wrote: /tmp/tito/crush-v2023.2.alpha1-1.git.435.4f41eec.fc38.src.rpm`

Is this a duplicate to #208 ?