-
Notifications
You must be signed in to change notification settings - Fork 280
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Packages are not reproducible #1831
Comments
My only other thought is that we should map the |
Summary of IRC discussion: Pkg
Poudriere
|
That would be very nice, how's it coming along? I just made a patch that adds a flag to ignore these versions: valpackett@884c2e3 and only then found this issue with the plan to remove them. |
|
When I run |
Well, this is a very long way to go. As a Maven PMC member I was involved to make all Maven-generated builds fully reproducible with the same JDK and system type (Windows xor POSIX-like). It took us years to address all components. (do not feel discouraged)
Use I'd be happy to consult. |
We know how to make reproducible builds, I have been involved in the 2 first reproducible builds summit long ago. pkg per se is able to create reproducible package for around 5 years, the problem which is pointed out here is freebsd specific. (and thanks for pointing out at diffoscope, I am an early contributor of it, in particular porting it to freebsd, so I am well aware of it). |
So this s a lack of resources rather than tooling? PS: Thanks for diffoscope, I love it. |
pkg can make reproducible packages just fine, pkg cannot make reproducible packages without breaking many existing tooling available in freebsd, so the issue is deal with the legacy |
#1829 got me thinking about this.
For Poudriere to not rebuild packages when there's no PORTREVISION bump to change the
deps{version}
means the naive way of repackaging them will always change the hash.Stepping back from Poudriere the problem is that building the same port twice without any changes to the port can produce a different package metadata/deps and hash due to dep versions. I think framing the issue as a reproducibility problem might be clearer.
I would prefer to find a way to do what we need with Poudriere without changing hashes.
Things that care about the version:
pkg rquery %v
pkg add
deps (ports depends on this)My only idea currently is to make both assume the latest version which isn't great considering actually supporting multiple versions of packages in 1 repository with proper dependencies.
The text was updated successfully, but these errors were encountered: