-
-
Notifications
You must be signed in to change notification settings - Fork 49
config/hooks/GRMLBASE/updatebase: fix duplicate Check-Valid-Until #425
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
base: master
Are you sure you want to change the base?
Conversation
crpb
commented
Aug 23, 2025
- If the class RELEASE is enabled (which is now default) and we use the waybackmachine the sources.list(5) entry 'Check-Valid-Until' will be taken care by config/scripts/GRMLBASE/33-aptsetup
|
pretty sure ifclass ! RELEASE doesn't do what you want there. if ! ifclass RELEASE should work. and we dont need quotes around RELEASE :) |
DOCH!
i know that it isn't necessary with this simple query but i think it is cleaner to write it like that. someone also did put a space between |
Remember this is not FAI's ifclass :) |
|
isn't this too simple? if you build an image without RELEASE, and then rebuild it with |
To clarify, IMO a test should be: and then |
@zeha is that expected?
|
* If the class RELEASE is enabled (which is now default) and we use the waybackmachine the sources.list(5) entry 'Check-Valid-Until' will be taken care by config/scripts/GRMLBASE/33-aptsetup
|
same result with a current merge... anything else i could test or do we want a workflow test for this? ¯\_(ツ)_/¯ |
I mean obviously, if you pick an older date than what you built with, some packages will not be available. |
|
General questions I have about
|
yeah i know that but maybe it would be prefferred to 'reinstall' those with the currently available version. |