[Pkg-electronics-devel] Fix for KLayout watch file

[Carsten Schoenert]

Hello Thomas,

Am 05.11.22 um 04:50 schrieb Thomas Dorch:
> The watch file is not currently working due to changes in the GitHub 
> Releases page (https://lists.debian.org/debian-devel/2022/09/msg00224.html).
> To fix this, we can just replace "releases" with "tags" for now,
> since the releases are all tagged.

initiated by another project which is using Klayout I've looked again at 
Klayout within Debian and also looked into d/watch to figure out why 
it's not working anymore. I've modified the file so it's using the git 
mode if the uscan tool is called.

...
> Should I run the |"gbp dch"command and push the generated changelog as 
> well or just leave it as is?

Well, this depends (to me) on the quality of the package preparation. I 
personally like a mostly "clean" straight forward git commit history 
there I can see the reason for a commit because it can be a strenuous 
thing to figure out why a file was modified three times by different not 
atomic commits.
That's happily so far not a real problem within Debian and the work of 
contributors, but I see this often within some upstream work.

And I personally don't see much a reason to do running gbp dch if it's 
not really clear the work is finished. gbp will honor anyway the author 
of the commits if it's called by another person.
There is no policy about this topic within the Electronic Team so far I 
know, so it's best to talk to the potential sponsor.

> Also, there is a new release of KLayout (0.27.12) that it would be nice 
> to get into the archive if someone (Carsten?) is able to help me with that.
As written above, I've seen this new version also a few days ago and did 
start importing that. I'm mostly done with the packaging and was trying 
to get the Salsa CI working again, but this is taking some effort 
because Klayout is a bit of a monster. It takes about 3.5h to build on 
the GitLab runner! Due this I needed to set the timeout for pipelines to 
4h, but it still fails for another reason.

https://salsa.debian.org/tijuca/klayout
https://salsa.debian.org/tijuca/klayout/-/pipelines/449977

I'm biased if having a working CI is that much gain...

I'll probably just let the CI turned of for the repository in the 
Electronic Teams group for now.

-- 
Regards
Carsten