Le 22/08/2025 à 06:54, Maytham Alsudany a écrit :
On Wed, 2025-08-20 at 14:04 +0000, [email protected] wrote:
If another linux distro maintainer ask me to create a repo in their ecosystem,
I cannot imagine to maintain a repo for each linux distro myosotis will be
packaged for.
I understand you, you are both upstream and maintainer AFAIK. According
to my experience upstream doesn't
have to create a repo in each linux distro, that task for the distro
package maintainer (you in this case)
Some thoughts:
If upstream == downstream, then IMO a Debian branch on the upstream repo
is more suitable than a completely separate repo on Salsa. git-
buildpackage already supports this, and commands like "gbp import-ref"
can be used to import new releases' tags.
After reflection, I think you are right.
Then there are also advantages to placing packaging on Salsa, like
incorporating Salsa CI to test the package, tag2upload (if you use
that), and DDs being able to access your repo already if it is under the
"debian" group.
Indeed. I was seduced by the fact DDs an Tiny task team could contibute.
But now, finally, I will not create a Salsa repo in addition to my
upstream repo.
Thanks,
Maytham
Thank you for sharing your thougths,
Benoît
