On Wed, 2026-11-11 at 10:09 +0200, Edmund Lodewijks wrote: > > in fact, it got uploaed to NEW, where it was (correctly) shot down by > ftpmasters due to missed vendored code (of which there was a tremendous > amount; i don't know if this has changed). > > If you still have it, could you please share the (gist of the) > ftpmasters rejection? Might be useful!
It was pretty much that d/copyright was completely wrong, and they gave a few examples to demonstrate. Note this happened before the DFSG team was a thing. > I don't think the amount of vendored code has changed very much. There's > some work to do, and some choices to be made. > > > you mention debian/copyright is "barely started"; we've got over 1100 > lines of it. i'd definitely try to leverage what you can from there > > d/copyright: Yes, very happy to continue on your work. Unvendoring first > would help a ton, so that's where I'd start. I'm sure ftpmasters or DFSG > use tools for quickly checking for licensen vs d/copyright. Would be > great to be able to use that. They do, but ultimately everything is (supposed to be) reviewed by hand. As you mention later here, this is probably something to do after it gets fully repacked and everything unnecessary is removed. [...] > > I have not been able to build zig0.14 [...] on my own machine, on > debusine.debian.net, and on barriere.debian.org (the amd64 porterbox) > > Thank you for trying to build this, and I am sorry about the many hours > without success. Happy to have a look at build logs if you feel like > running it again. I've uploaded to debusine again to get a build log, but the TLDR is that it segfaults every time after/during stage 2. Will send a message when the build log is ready. > Some things from my notes on the build failures I encountered when going > from 0.16 to 0.17.1 (different versions from the one you were trying to > build): > > - Do not use upstream's cmake path. cmake is good for generating > config.h and building zigcpp (libzigcpp.a) and nothing else; the > compiler itself has to be built by an existing zig via `zig build`. > - Pass -Dversion-string= and -DZIG_VERSION= explicitly. Both paths > otherwise run `git describe`, which fails in a release tarball. > - Have ZIG_GLOBAL_CACHE_DIR inside the build tree. A stale > ~/.cache/zig silently produces a miscompiled compiler that segfaults, > with nothing in the output pointing anywhere near the cache. That > cost me most of a day... :( > - -Dcpu=baseline, or the result varies per builder. > - I looked quite a bit at Fedora's spec file for ideas as well. [...] > On guix and buildds: > You are right, and I think that option (c) isn't very viable currently, > also because guix is currently still blocked. > None of it affects what I am proposing, where the chain runs once > outside the archive, and only its output (seed / blob) is shipped. Have you considered using snapshot.debian.org to produce a set of Debian packages that can be built sequentially from each other using different archive snapshots, which contain older versions of LLVM etc? -- Maytham
signature.asc
Description: This is a digitally signed message part

