Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.bugs.dist > #1150824 > unrolled thread

Bug#1037306: ITP: apycula -- Tools to generate Gowin FPGA bitstreams

Back to article view | Back to linux.debian.bugs.dist

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.

Contents

  Bug#1037306: ITP: apycula -- Tools to generate Gowin FPGA bitstreams Daniel Gröber <dxld@darkboxed.org> - 2023-06-21 18:40 +0200
    Bug#1037306: ITP: apycula -- Tools to generate Gowin FPGA bitstreams Daniel Gröber <dxld@darkboxed.org> - 2023-06-24 23:00 +0200
      Bug#1037306: ITP: apycula -- Tools to generate Gowin FPGA bitstreams Daniel Gröber <dxld@darkboxed.org> - 2023-07-25 16:00 +0200
        Bug#1037306: ITP: apycula -- Tools to generate Gowin FPGA bitstreams Simon Richter <sjr@debian.org> - 2023-07-26 05:00 +0200
          Bug#1037306: ITP: apycula -- Tools to generate Gowin FPGA bitstreams Daniel Gröber <dxld@darkboxed.org> - 2023-07-26 14:40 +0200

#1150824 — Bug#1037306: ITP: apycula -- Tools to generate Gowin FPGA bitstreams

Hi Simon,

I still haven't heard back since last week. Are you still interested in
sponsoring nextpnr related packages?

Since my last mail I've finished the prjtrellis integration so everything
should be ready for the first upload.

    https://salsa.debian.org/electronics-team/apycula
    https://salsa.debian.org/electronics-team/prjtrellis

Thanks,
--Daniel

[toc] | [next] | [standalone]

#1151261

Hi Simon,

On Sat, Jun 24, 2023 at 10:00:39PM +0900, Simon Richter wrote:
> I'm looking at trellis first:
> 
>  - the bit_to_svf.py script is not installed

It's not installed by the `make install` target. If upstream wants it
installed, they probably shoud do so :)

I can install it into docs if you like but the generic name prevents
installation into /usr/bin IMO.

>  - Rachel suggests https://prjtrellis.readthedocs.io/en/latest/ as the
> homepage link, any opinion on whether that is a better choice than the
> github page?

I prefer upstream source repos as Homepage TBH. The docs are linked to from
the README so I think they should be easy enough to discover.

Debian policy has this to say on the matter:

| 5.6.23. Homepage
| 
| The URL of the web site for this package, preferably (when applicable)
| __the site from which the original source can be obtained__ and any
| additional upstream documentation or information may be found.

So I think my intuition is correct here.

>  - dh_auto_configure and dh_auto_install are overridden with the default
> behaviour.

Yeah I forgot to do a final cleanup pass after getting nextpnr working :)

Will rectify with the next upload.

I also got a review from Jonathan Neuschäfer saying that trellis chipdbs
are installed into the wrong path and nextpnr barfs so we'll have to upload
a fixed version anyway.

Do you know if we have to wait to clear the NEW queue or can we just upload
another revision right away?

>  - the "Unlicense" is, very strictly speaking, a crayon license, although
> the intention is clear. The FTP team might object here, or just shrug, so
> not a blocker to uploading IMO.

Indeed in some countries giving up copyright as such is simply not
possible. My home country (Austria) doesn't allow this either for
example. Aber "wo kein kläger da kein richter" ;)

> Other than that, the package is very good, and ready for upload.
> 
> Will look at apycula now.

I see you already uploaded it now. Great!

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?

Also I see the debian/* tags are still missing please don't forget to push
them.

If you forgot to run gbp-buildpackage with --git-tag it's best to use `gbp
import-dsc` to import the source package you just uploaded and push
that. IIRC this will create the debian/* tag too.

You can push everything using `gbp push origin` and if that doesn't work
(it fails sometimes for me):

    git push --tags && git push origin master upstream

Thanks,
--Daniel

[toc] | [prev] | [next] | [standalone]

#1155838

Hi Simon,

On Sat, Jun 24, 2023 at 10:50:24PM +0200, Daniel Gröber wrote:
> > Will look at apycula now.
> 
> I see you already uploaded it now. Great!

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.

Also a reminder on pushing the tags if you could:

> 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?
> 
> Also I see the debian/* tags are still missing please don't forget to push
> them.
> 
> If you forgot to run gbp-buildpackage with --git-tag it's best to use `gbp
> import-dsc` to import the source package you just uploaded and push
> that. IIRC this will create the debian/* tag too.
> 
> You can push everything using `gbp push origin` and if that doesn't work
> (it fails sometimes for me):
> 
>     git push --tags && git push origin master upstream

Thanks,
--Daniel

[toc] | [prev] | [next] | [standalone]

#1155951

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.

> 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.

Hopefully I can get around to that tonight when I get home.

>> 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.

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.

    Simon

[toc] | [prev] | [next] | [standalone]

#1155986

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

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.bugs.dist

csiph-web