On Thursday, 28 November 2019 9:19:14 PM AEDT Arnaud Rebillout wrote:
> how do I make use of it? For example, I look at
> https://tracker.debian.org/pkg/golang-github-azure-go-autorest, I don't
> see any mention of the "affects" that you set with the bts.
Just click bugs like (which is showing '0' at the moment) and you will see
the following:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?src=golang-github-azure-go-autorest
and the ITP of the affecting package is there.
> Is there another place I should look at?
I'm not sure. Maybe. To me it was always enough to have relationships
in the bug tracker. For example when I look at ITP I see which packages
are affected and the affected packages have links to related ITP bugs.
> Thanks for pointing that out. I think I fixed everything in salsa master.
Thanks. I can't check right now but I should be able to get to it
either tomorrow or in few days.
> Regarding generated files, I compared the new package with the old one,
> and I saw a only one difference, in the two .pb.gw.go files:
Having any differences is good - it means that re-generation does what's
expected. Size of the differences is not too important but now you know
that re-building will be meaningful in case of any changes (e.g. in other
packages) that have potential to affect generated files.
--
All the best,
Dmitry Smirnov.
---
The world is a dangerous place to live, not because of the people who are
evil, but because of the people who don't do anything about it.
-- Albert Einstein
Attachment:
signature.asc
Description: This is a digitally signed message part.