Skip to content
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

phase1: remove kmods in target packages if archive is enabled #37

Closed
wants to merge 5 commits into from

Commits on Nov 13, 2024

  1. phase1: Implement custom step ShellCommandAndSetProperty

    Implement custom step ShellCommandAndSetProperty, as an extension of
    ShellCommand with the addition of setting a bool property that is set
    True or False if the shell command succeeded or not.
    
    Signed-off-by: Christian Marangi <[email protected]>
    Ansuel committed Nov 13, 2024
    Configuration menu
    Copy the full SHA
    7d7fb14 View commit details
    Browse the repository at this point in the history

Commits on Nov 15, 2024

  1. phase1: remove kmods in target packages if archive is enabled

    OPKG gets confused if kmod packages are present in both, target packages
    as well as kernel version specific folder.
    Remove them from target packages to make opkg pick the kmods from kmod
    archive folder only.
    
    This also affects APK that picks packages from the first entry in the
    repository file and doesn't support checking the same package from
    multiple entry.
    
    Signed-off-by: Daniel Golle <[email protected]>
    [ add --remove-source-files and improve implementation ]
    Signed-off-by: Christian Marangi <[email protected]>
    dangowrt authored and Ansuel committed Nov 15, 2024
    Configuration menu
    Copy the full SHA
    437dd6f View commit details
    Browse the repository at this point in the history

Commits on Nov 17, 2024

  1. pahse1: merge sha256sums with remote kmods entry if present

    Add additional logic to merge the sha256sums with the remote kmods entry
    (in remote sha256sums) already present.
    
    This is to produce a more consistent sha256sums that actually reflect
    what is present in the remote server by including also the sha of the
    kmods for each kernel version supported.
    
    Signed-off-by: Christian Marangi <[email protected]>
    Ansuel committed Nov 17, 2024
    Configuration menu
    Copy the full SHA
    ab85b44 View commit details
    Browse the repository at this point in the history
  2. phase1: correctly exclude kmods files from rsync target upload and prune

    There is currently a BUG in the --exclude pattern for the targetupload step.
    The /kmods/ directory is actually never excluded. This was never notice
    as the rsynclist never actually had kmods entry as make checksum step
    was done before moving the kmods to the dedicated directory.
    
    This is caused by the fact that with --files-from, not only the /kmods/
    directory needs to be excluded but also every content in it, hence the
    additional --exclude "/kmods/**" is required to correcly skip the entry
    present in rsynclist.
    
    Signed-off-by: Christian Marangi <[email protected]>
    Ansuel committed Nov 17, 2024
    Configuration menu
    Copy the full SHA
    db5d151 View commit details
    Browse the repository at this point in the history
  3. scripts: signall: skip updating hash of previous kmods/

    Handle case where a sha256sums might contain previous kmods/. In such
    case packages.adb for previous kmods/ needs to be skipped as not
    included in the sign tar and already signed by previous runs.
    
    Skip is limited to kmods/ entry as those are the only entry expected to
    be present in the sha256sums but not included in sign tar.
    
    Signed-off-by: Christian Marangi <[email protected]>
    Ansuel committed Nov 17, 2024
    Configuration menu
    Copy the full SHA
    174e7a1 View commit details
    Browse the repository at this point in the history