Otto Kekäläinen writes:
> Hi,
>
> The go-tuf version string 2.0.2+0.7.0-1 seems cryptic. How is the
> package lifecycle planned to go if it actually contains the same
> package twice?
If a new release on either branch happens, the package is updated.
> Would it not be much simpler to just have
Hi all!
I found out about Gophian[1, 2] yesterday and I had no clue it
existed. It seems new, from summer 2025. I wonder how many people are
using it? What do you think about it?
I noticed Nicolas is working on
https://github.com/Debian/dh-make-golang/pull/240 which seems to have
been one of the
Hi,
The go-tuf version string 2.0.2+0.7.0-1 seems cryptic. How is the
package lifecycle planned to go if it actually contains the same
package twice?
Would it not be much simpler to just have two source packages in
Debian, just like all other packages that have multiple versions?
> But there are packages (e.g.,
> cosign) that ultimately Build-Depends on both, so both has to be
> installed at the same time.
Ah, in that case it makes sense to have both in the same package as
the workaround.
Hi!
Five days later, the script and proposal to execute enabling Salsa
instance runners still has zero approvals..
While waiting to get approvals on my code suggestions, I will also
draft a workflow 2025 proposal at
https://salsa.debian.org/go-team/go-team.pages.debian.net like was
done in 2017 t
