On 2022-11-23 17:59:41, Riccardo Coccioli wrote:
> On Wed, Nov 23, 2022 at 5:15 PM Moritz Mühlenhoff <mmuhlenh...@wikimedia.org>
> wrote:
>
>> Hi Antoine,
>>
>> [Adding Riccardo Coccioli, my colleague at Wikimedia and the primary
>> author of Cumin to CC]
>>
>> > which makes me wonder: should we drop the debian branch on github and
>> > gerrit? or should we (say, debian sponsors) pull changes from you and
>> > sync them to salsa?
>> >
>> > how should we play this long term?
>>
>> My proposal would be to discard the debian branch on gerrit/github and
>> make salsa.debian.org the authoritative repository for Cumin debs (and
>> just build backports for apt.wikimedia.org based on the latest version
>> on salsa/unstable).
>>
>> But let's hear from Riccardo on this as well.
>>
>> Cheers,
>> Moritz
>>
>
> I'd like to better understand why it would be better/easier to move the
> debian branch into salsa instead of leaving it attached to the upstream
> project. I'm not that familiar with the whole debian process, so correct me
> if I'm missing something obvious.
Sure. It really depends on how you want to manage this package. So far
I've been assuming I'd be doing some of the work at least, which means
I'd need access to the git repo, hence salsa, where I can also grant
*you* access. I suspect the reverse is not possible, and I wouldn't be
able to contribute back to the wikimedia repositories myself...
> It would seem to me that leaving the debian branch into the upstream
> repository would also allow other distro/users to build their own deb
> package using the same config without importing a separate repository.
I don't think you need write access to the repository to build your own
deb, that's the thing. If you just add a pointer in the wikimedia repo
to salsa, people will know where to find the repo.
Heck, you shouldn't even need to build your own debs if we do this
right; this will trickle down to bookworm and, from there, backports,
ubuntu, etc.
> As for the debian/watch file if you don't mind I would like to upload a
> slightly different one that I use for another project as the tags are all
> signed and it does work with the new GitHub APIs (see also the recent "Q:
> uscan with GitHub" thread in debian-devel).
Oh, yes of course, I'd be happy to see that.
Let me know if you want access to the salsa repo. I'm fine either way.
a.
--
For every complex problem, there is an answer that is clear, simple -
and wrong.
- H.L. Mencken
