-
Notifications
You must be signed in to change notification settings - Fork 27
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
use apt-get with --error-on=any option #266
base: master
Are you sure you want to change the base?
Conversation
for better error handling
A simple and non-controversial change? |
The problem I have with this change is, that this feature seems to be available as of apt v2.1.16, which is available "only" as of bullseye (v11) and newer Debian releases, while we still supported Debian releases back until jessie (v8). The So I'm afraid while the change looks simple and non-controversial, it's not as simple as that. :-/ (Furthermore in line 182 of |
I guess feature detection could be added, then ok? |
ACK! :) |
Uff, the option isn't mentioned in
Any ideas how to properly detect |
Would probably need to set or not set the option based on the Debian version. |
Simple but good idea, thanks! :) |
for better error handling
Otherwise if 1 repository fails (such as the security repository) apt would by default silently ignore this can continue the build. Therefore for consistent builds and towards reproducible builds, this option is required.
I am using this in all my build scripts for years, though injected through DPKG_OPTIONS but I think the case is strong enough to hardcode this as default.