Bug#1037306: ITP: apycula -- Tools to generate Gowin FPGA bitstreams
Hi Simon,
On Wed, Jul 26, 2023 at 11:45:32AM +0900, Simon Richter wrote:
> Hi Daniel,
>
> On 7/25/23 22:53, Daniel Gröber wrote:
>
> > FYI: It seems you didn't do a source-only upload for apycula so it's
> > BLOCKED from migrating to testing now. We have to do another source-only
> > upload to get it unstuck.
>
> Yes, known problem. I dimly remember that NEW uploads require binaries for
> some reason.
Ah yes, you're right, https://wiki.debian.org/SourceOnlyUpload says:
NEW uploads and uploads with NEW binary packages currently cannot be
source-only. This is also true for backports-NEW.
This means you need to upload a source+binary package in these
situations. After your package has passed the checks and is in the
archive, you need to do a source-only upload to allow the package to
migrate to testing. The source+binary package you did initially will NOT
be allowed to migrate.
> > > Did you make any changes either of the the packages? If so don't forget to
> > > commit and push to salsa please. You should have push access to
> > > electronics-team, right?
>
> No changes, IIRC. I'm not sure if I have push access, I will have to check
> at home.
If you didn't make any changes it's not necessary. I can probably
reconstruct the tags myself then. Don't worry about it.
> > Also a reminder on pushing the tags if you could:
>
> Right, I'll have to learn how to do that, I seldom use git-buildpackage, and
> I verify packages by building them in pbuilder.
You should be able to have gbp use pbuilder for building, see
--git-builder= or --git-pbuilder=.
> BTW, I have ghdl 3.0.0 packages at https://deb.simonrichter.eu/ and am
> successfully using the ghdl yosys plugin with those, this might be another
> goal for the next months.
Neat, now we just have to get Andreas to upload it. Can you submit a BTS
patch / salsa PR or something?
I'm still wating for prjtrellis to clear NEW before the updated nextpnr can
go in, is there anyone we can poke to accellerate things? It's been sitting
around a good while now :)
yosys_0.30 on the other hand is giving me a hard time since I started
trying to package it's testsuite as an autopkgtest. I had to take a break
from that but I'll get back to that soon and then it'll (hopefully) have
migration blocked if a berkeley-abc upload breaks it.
Upstream yosys has also been kind enough to tag releases on yosys-abc so we
could package that to make breakage due to mismatch between their fork and
bekeley-abc less likely (https://github.com/YosysHQ/yosys/issues/3827)
--Daniel
Reply to: