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

sailfishos:chum repository lacks 4.6 #287

Closed
Olf0 opened this issue May 26, 2024 · 8 comments
Closed

sailfishos:chum repository lacks 4.6 #287

Olf0 opened this issue May 26, 2024 · 8 comments
Labels
bug Something isn't working

Comments

@Olf0
Copy link
Collaborator

Olf0 commented May 26, 2024

@rinigus / @piggz, the sailfishos:chum and sailfishos:chum:testing repositories at Sailfish-OBS lack the final release number for SailfishOS 4.5.0 4.5.0.25 (and sailfishos:chum lacks 4.6). IMO that means:

  1. In the "meta" configuration of sailfishos:chum:testing the entries for 4.5.0.24 should be overwritten with:
      <repository name="4.5.0.25_i486">
        <path project="sailfishos:4.5.0.18" repository="latest_i486"/>
        <arch>i586</arch>
      </repository>
      <repository name="4.5.0.25_armv7hl">
        <path project="sailfishos:4.5.0.18" repository="latest_armv7hl"/>
        <path project="nemo:testing:hw:common" repository="sailfishos_4.5.0.25_armv7hl"/>
        <arch>armv8el</arch>
      </repository>
      <repository name="4.5.0.25_aarch64">
        <path project="sailfishos:4.5.0.18" repository="latest_aarch64"/>
        <path project="nemo:testing:hw:common" repository="sailfishos_4.5.0.25_aarch64"/>
        <arch>aarch64</arch>
      </repository>
    
  2. In the "meta" configuration of sailfishos:chum the entries for 4.5.0.25 and 4.6 should be added atop those for 4.5.0.24:
      <repository name="4.6_i486">
        <path project="sailfishos:4.6" repository="latest_i486"/>
        <arch>i586</arch>
      </repository>
      <repository name="4.6_armv7hl">
        <path project="sailfishos:4.6:hw-common" repository="latest_armv7hl"/>
        <path project="sailfishos:4.6" repository="latest_armv7hl"/>
        <arch>armv8el</arch>
      </repository>
      <repository name="4.6_aarch64">
        <path project="sailfishos:4.6:hw-common" repository="latest_aarch64"/>
        <path project="sailfishos:4.6" repository="latest_aarch64"/>
        <arch>aarch64</arch>
      </repository>
      <repository name="4.5.0.24_i486">
        <path project="sailfishos:4.5.0.18" repository="latest_i486"/>
        <arch>i586</arch>
      </repository>
      <repository name="4.5.0.25_armv7hl">
        <path project="sailfishos:4.5.0.18" repository="latest_armv7hl"/>
        <path project="nemo:testing:hw:common" repository="sailfishos_4.5.0.25_armv7hl"/>
        <arch>armv8el</arch>
      </repository>
      <repository name="4.5.0.25_aarch64">
        <path project="sailfishos:4.5.0.18" repository="latest_aarch64"/>
        <path project="nemo:testing:hw:common" repository="sailfishos_4.5.0.25_aarch64"/>
        <arch>aarch64</arch>
      </repository>
    

Thank you!

@Olf0 Olf0 added the bug Something isn't working label May 26, 2024
@piggz
Copy link
Contributor

piggz commented May 26, 2024

Keto from Jolla created a symlink for the download repository to save space. This means that although the projects doesnt display in OBS, the actual downloads continue to work.

@Olf0
Copy link
Collaborator Author

Olf0 commented May 26, 2024

Keto from Jolla created a symlink for the download repository to save space.

How is this symlink traceable / checkable? I.e. from where to where does it exactly point?

This means that although the projects doesnt display in OBS, the actual downloads continue to work.

Mmmh, what does this quite generic statement address specifically: Only 4.5.0.25, or also 4.6 for sailfishos:chum?

@piggz
Copy link
Contributor

piggz commented May 26, 2024

Visit the repo url fro 4.5.0.24 eg https://repo.sailfishos.org/obs/sailfishos:/chum/4.5.0.25_aarch64/
Change 24 to 25, see the timestamps are the same.

@Olf0
Copy link
Collaborator Author

Olf0 commented May 27, 2024

Visit the repo url fro 4.5.0.24 eg https://repo.sailfishos.org/obs/sailfishos:/chum/4.5.0.25_aarch64/ Change 24 to 25,

Thank you, now I see:

  1. For sailfishos:chum
  2. For sailfishos:chum:testing

see the timestamps are the same.

Or better: Descend into repodata and see that the hashes are the same.



Unfortunately this is nothing I can utilise for Storeman, but as this is a single package, the waste of space is much less significant. For 4.6, I will switch to a single repo for all SailfishOS 4.6.0.x releases, too.



What seems to remain of this issue are the missing 4.6 entries for sailfishos:chum proper:

  1. In the "meta" configuration of sailfishos:chum the entries for […] 4.6 shall be added atop those for 4.5.0.24:
  <repository name="4.6_i486">
    <path project="sailfishos:4.6" repository="latest_i486"/>
    <arch>i586</arch>
  </repository>
  <repository name="4.6_armv7hl">
    <path project="sailfishos:4.6:hw-common" repository="latest_armv7hl"/>
    <path project="sailfishos:4.6" repository="latest_armv7hl"/>
    <arch>armv8el</arch>
  </repository>
  <repository name="4.6_aarch64">
    <path project="sailfishos:4.6:hw-common" repository="latest_aarch64"/>
    <path project="sailfishos:4.6" repository="latest_aarch64"/>
    <arch>aarch64</arch>
  </repository>

@Olf0 Olf0 changed the title [Bug] sailfishos:chum and sailfishos:chum:testing repos lack 4.5.0.25 sailfishos:chum repository lacks 4.6 May 27, 2024
@rinigus
Copy link
Contributor

rinigus commented May 27, 2024

One more aspect: in addition to saving space, it avoids rebuilding Chum/ChumTesting for minor version changes. This rebuilds could easily take days in the current setup. Hopefully, this approach will work well in practice and get a leaner OBS as a result.

@piggz
Copy link
Contributor

piggz commented May 27, 2024

RE 4.6 ... we're still trying to get all of testing to build. Quite a lot of packages are held up by changes to the opt-qt5/kf5 stuff which is having an issue. Im away on holiday for a week, hopefully @rinigus will figure it out :)

@Olf0
Copy link
Collaborator Author

Olf0 commented May 31, 2024

BTW, sailfishoschum-gui-installer versions ≥ 0.6.4 should handle the new naming scheme <major>.<minor>_<arch> as implemented in sailfishos:chum:testing for SailfishOS 4.6, when implemented in sailfishos:chum proper.

@Olf0
Copy link
Collaborator Author

Olf0 commented Jun 13, 2024

What seems to remain of this issue are the missing 4.6 entries for sailfishos:chum proper:

This is looking good to me now, hence closing this issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants