On Fri, Oct 25, 2024 at 6:00 AM Reinhard Tartler wrote:
>
> On Fri, Oct 25, 2024 at 5:57 AM Simon Josefsson
> wrote:
>
>> Status update:
>>
>> - I've canceled the TUF *-v2 NEW package, prefering your advice to
>> upgrade the existing package from v0.
>>
>> - Upstream for rekor + sigstore-sigst
On Fri, Oct 25, 2024 at 5:57 AM Simon Josefsson wrote:
> Status update:
>
> - I've canceled the TUF *-v2 NEW package, prefering your advice to
> upgrade the existing package from v0.
>
> - Upstream for rekor + sigstore-sigstore replied quickly that TUF v0 is
> deprecated for those projects, s
Status update:
- I've canceled the TUF *-v2 NEW package, prefering your advice to
upgrade the existing package from v0.
- Upstream for rekor + sigstore-sigstore replied quickly that TUF v0 is
deprecated for those projects, so we can patch it out.
- I've uploaded sigstore-sigstore 1.8.10-2 to
On Wed, Oct 23, 2024 at 4:59 PM Simon Josefsson wrote:
> Status update:
>
> - I've canceled the TUF *-v2 NEW package, prefering your advice to
> upgrade the existing package from v0.
>
> - TUF 2.0.2 is uploaded into experimental:
> https://tracker.debian.org/pkg/golang-github-theupdateframewo
Status update:
- I've canceled the TUF *-v2 NEW package, prefering your advice to
upgrade the existing package from v0.
- TUF 2.0.2 is uploaded into experimental:
https://tracker.debian.org/pkg/golang-github-theupdateframework-go-tuf
- Upstream for rekor + sigstore-sigstore replied quickly t
Thanks for feedback! I'll try to cancel the -v2 NEW upload, and will do
a v2 upload to experimental to allow others to help test. I did upgrade
the old package and did a reverse rebuild, see pipeline here:
https://salsa.debian.org/jas/golang-github-theupdateframework-go-tuf/-/pipelines/751423
T
Hey Simon, thanks for taking a look at the tuf package in Debian,
On Wed, Oct 23, 2024 at 5:01 AM Simon Josefsson wrote:
> All,
>
> I've uploaded the v2 package to NEW and it builds fine and seems to
> work.
>
> But how do we handle migrations for packages that use the same
> namespace? Now bot
All,
I've uploaded the v2 package to NEW and it builds fine and seems to
work.
But how do we handle migrations for packages that use the same
namespace? Now both golang-github-theupdateframework-go-tuf and
golang-github-theupdateframework-go-tuf-v2 will provide some overlapping
files, so cannot
