Package: yosys
Version: 0.51-1
X-Debbugs-CC: Scott Ashcroft <scott.ashcr...@hotmail.com>, Steffen Möller 
<steffen_moel...@gmx.de>, Tarik Graba <tarik.gr...@telecom-paris.fr>, Philipp 
Klaus Krause <p...@spth.de>, "J. Neuschäfer" <j.neuschae...@gmx.net>, 
pkg-electronics-de...@alioth-lists.debian.net, Andrey Gursky 
<andrey.gursky...@gmail.com>, Larry Doolittle <la...@doolittle.boa.org>

(Sound of me praying the huge X-Debbugs-CC pseudoheader doesn't break)

On Tue, Mar 18, 2025 at 03:08:30PM +0000, Scott Ashcroft wrote:
> On Tue, 2025-03-18 at 15:02 +0100, Daniel Gröber wrote:
> > Last time it just needed a strategically placed (double) cast. Idk
> > why this would have started breaking again?
> 
> https://github.com/YosysHQ/yosys/commit/2edb9397c317cb3ef3e4d29741069e0cd900eadb
> 
> "Unclear if there are any changes lost that we need to patch back in."
> 
> That'll be a yes then. 

Ugh! What's even the point in sending stuff upstream sometimes xD. Keeping
this as our own patch would have made this obvious...

I'll leave the yosys RM request as-is for now. If the build starts working
again it'll just get reintroduced. Asking ftp-master not to remove i386
after all at this point would just add confusion and not save any work on
their side AFAIK.

I guess we should have sent the patch to gtkwave to begin with.

Looking at buildd logs for gtkwave I'm wondering why it's working on i386,
does the package just not test the fst code?

Thanks for digging this up,
--Daniel

Attachment: signature.asc
Description: PGP signature

Reply via email to