Andrew Lee <[email protected]> writes:

> Hi Simon,
>
> On Tue, Jul 14, 2026 at 8:29 PM Andrew Lee <[email protected]> wrote:
>> Once we have all these identical with `go import path`, it would make
>> dependency handling much easier under module-aware builds.
>>
>> I will update these into the document on wiki page for the phase 1.
>> When you work on the source package, please check the `go import path`
>> from go.mod file.
>> And then update it to debian/copyright and debian/control and also the
>> package name. I will talk to awm from DFSG team here in DebCamp for
>> these renamed packages.
>
> I made an update on this as example package:
>   
> https://salsa.debian.org/go-team/packages/golang-github-spiffe-go-spiffe/-/commits/debian/sid?ref_type=HEADS
>
> I haven't uploaded it. Since you are the maintainer, it would be nice
> if you can do a quick review for the changes.

Don't block on me if it passes normal QA testing, and you think it is
the right thing.

I'm not sure I follow, you are changing the Source package name, so this
would go into NEW and effectively be a new package, doesn't it?  What do
you think about just forking this repository into a new Salsa project
for that new name instead?  The old package won't magically go away, and
having two packages in the PTS that points to the same Salsa project
seems confusing.  It will mean the PTS will complain it is out of sync
with git for the old package.

-Upstream-Name: go-spiffe
+Upstream-Name: github.com/spiffe/go-spiffe/v2

This looks weird.  Do that really match the intention behind
debian/copyright Upstream-Name?

https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/#upstream-name-field

It looks more like you are using this for something Go-related?  The
upstream project name seems to be 'go-spiffe', not the entire namespace.

/Simon

>
> I didn't put a transitional package due to we are switching to
> module-aware builds. We expected a lot of package would receive source
> level update. So that it's also a good time to clean up and resolve
> the dependency cleanly manually(expected a lot of patches that tirm
> out /v? folders can be drop).
>
> Best regards,

Attachment: signature.asc
Description: PGP signature

Reply via email to