Update hyrule, bolson, deku, ocarina and rito

[mikesol]

{
  "packages": {
    "hyrule": "v2.3.2",
    "bolson": "v0.3.1",
    "deku": "v0.8.1",
    "ocarina": "v1.5.1",
    "rito": "v0.3.1"
  }
}

[pacchettibotti]

The JSON input for this package update is malformed:

Expected value at key: 'payload'

You can try again by commenting on this issue with a corrected payload.

[thomashoneyman]

{ "packages": { "hyrule": "2.3.2", "bolson": "0.3.1", "deku": "0.8.1", "ocarina": "1.5.1", "rito": "0.3.1" } }

[thomashoneyman]

Sorry for the terrible error message. I suspect this JSON is not parsing because the registry does not use “v” prefixes for versions.

[pacchettibotti]

Processing package set update.

[pacchettibotti]

One or more packages in the suggested batch cannot be processed.

Cannot be added or updated:

• bolson@0.3.1: No manifest entry exists in the registry index.
• deku@0.8.1: No manifest entry exists in the registry index.
• hyrule@2.3.2: No manifest entry exists in the registry index.
• ocarina@1.5.1: No manifest entry exists in the registry index.
• rito@0.3.1: No manifest entry exists in the registry index.

[thomashoneyman]

@mikesol Looks like none of these packages are in the registry at the given versions.

[mikesol]

I think the most helpful thing would be for me to describe how I got here, as I'm outside of the project, hopefully it'll give you a sense of what I'm trying to do.

Step 1 - I read the README.

Modify the Package Set

Package sets are released once per day automatically. However, they sometimes need manual intervention (for example, to update a set of packages all together). The registry provides a batch package set update API for this purpose. You can add new packages or update package versions using the JSON specified below. The registry will update the package set to the indicated versions and recompile it. If successful, it will release a new package set with your changes.

Step 2 - I used the example payload

I read the example payload given in the documentation

{
 "packages": {
   "aff": "7.1.0",
   "argonaut": "9.1.0"
 }
}

And modified it using the versions of my packages:

{
  "packages": {
    "hyrule": "v2.3.2",
    "bolson": "v0.3.1",
    "deku": "v0.8.1",
    "ocarina": "v1.5.1",
    "rito": "v0.3.1"
  }
}

---

@mikesol Looks like none of these packages are in the registry at the given versions.

You're right that none of them are in the registry at the given versions, but my intention was for the package set to be updated to the indicated versions. I feel like I'm missing a step, though.

My expectation was that this would update the packages in the registry from the sentence in the README "The registry will update the package set to the indicated versions and recompile it".

I know this report is pedantic, but it traces how I'm finding information here and what my expectation is. Hopefully that's helpful!

[thomashoneyman]

You're right that none of them are in the registry at the given versions, but my intention was for the package set to be updated to the indicated versions. I feel like I'm missing a step, though.

I’m on mobile so I can give a better answer later, but in short what you’re missing is that the package sets only contain package versions that are in the registry. That means the packages you’ve listed here are ineligible because the indicated versions aren’t published to the registry. You’ll have to publish them first.

If you publish them all today then they will all be included in tonight’s package set update. Or you can submit a manual update if you’d like. But either way, the package sets are an artifact describing packages from the registry, and you can’t add a package version to the registry by adding it to the package sets — it’s gotta be the other way around.

[thomashoneyman]

Also I definitely hear you on the frustration of using the registry as someone outside the project. Really, most users aren’t meant to ever think about the registry because you should interact with it via a package manager like Spago. Unfortunately, there is no published version of Spago that yet works with the registry.

[mikesol]

{ "packages": { "hyrule": "2.3.2", "bolson": "0.3.1", "deku": "0.8.1", "ocarina": "1.5.2", "rito": "0.3.2" } }

[mikesol]

Also I definitely hear you on the frustration of using the registry as someone outside the project. Really, most users aren’t meant to ever think about the registry because you should interact with it via a package manager like Spago. Unfortunately, there is no published version of Spago that yet works with the registry.

Truly no worries - my intention here is to document the path I've followed in hopes that it's helpful, because once I figure things out, I'll forget what I struggled with and won't be able to provide good feedback.

[pacchettibotti]

Processing package set update.

[pacchettibotti]

One or more packages in the suggested batch cannot be processed.

Cannot be added or updated:

• bolson@0.3.1: No manifest entry exists in the registry index.
• deku@0.8.1: No manifest entry exists in the registry index.
• hyrule@2.3.2: No manifest entry exists in the registry index.
• ocarina@1.5.2: No manifest entry exists in the registry index.
• rito@0.3.2: No manifest entry exists in the registry index.

[mikesol]

{ "name": "hyrule", "ref": "v2.3.2", "compiler": "0.15.6" }

[pacchettibotti]

Publishing package hyrule at the ref v2.3.2.

[pacchettibotti]

Successfully uploaded package to the registry! 🎉 🚀

[pacchettibotti]

Skipping Pursuit publishing because this package failed to compile:

Compilation failed because the build plan compiler version 0.15.6 is not supported. Please try again with a different compiler.

[mikesol]

{ "name": "hyrule", "ref": "v2.3.2", "compiler": "0.15.4" }

[mikesol]

{ "name": "bolson", "ref": "v0.3.1", "compiler": "0.15.4" }

[mikesol]

{ "name": "deku", "ref": "v0.8.1", "compiler": "0.15.4" }

[mikesol]

{ "name": "ocarina", "ref": "v1.5.2", "compiler": "0.15.4" }

[mikesol]

{ "name": "rito", "ref": "v0.3.2", "compiler": "0.15.4" }

[pacchettibotti]

Publishing package deku at the ref v0.8.1.

[pacchettibotti]

Publishing package ocarina at the ref v1.5.2.

[pacchettibotti]

Successfully uploaded package to the registry! 🎉 🚀

[pacchettibotti]

Skipping Pursuit publishing because this package failed to compile:

Could not produce valid dependencies for manifest.

[Error 1] Package index contained no versions for bolson in the range >=0.3.1 <0.4.0 (existing versions: 0.0.0, 0.0.1, 0.0.2, 0.0.3, 0.0.4, 0.0.5, 0.0.6, 0.0.7, 0.0.8, 0.0.9, 0.1.0, 0.1.1)

[pacchettibotti]

Publishing package bolson at the ref v0.3.1.

[pacchettibotti]

Publishing package rito at the ref v0.3.2.

[pacchettibotti]

Successfully uploaded package to the registry! 🎉 🚀

[pacchettibotti]

Skipping Pursuit publishing because this package failed to compile:

Could not produce valid dependencies for manifest.

[Error 1] Package index contained no versions for bolson in the range >=0.3.1 <0.4.0 (existing versions: 0.0.0, 0.0.1, 0.0.2, 0.0.3, 0.0.4, 0.0.5, 0.0.6, 0.0.7, 0.0.8, 0.0.9, 0.1.0, 0.1.1)

[pacchettibotti]

Publishing package hyrule at the ref v2.3.2.

[pacchettibotti]

You tried to upload a version that already exists: 2.3.2 Its metadata is:

{ bytes: 14879.0, hash: sha256-oIZY8gRn6cU5UZiq89R4ewkSgi0O9d/tjyC0NUz/u1w=, publishedTime: (RFC3339String "2022-10-30T08:24:56.0Z"), ref: "v2.3.2" }

[pacchettibotti]

Successfully uploaded package to the registry! 🎉 🚀

[pacchettibotti]

Skipping Pursuit publishing because this package failed to compile:

Could not produce valid dependencies for manifest.

[Error 1] Package index contained no versions for bolson in the range >=0.3.1 <0.4.0 (existing versions: 0.0.0, 0.0.1, 0.0.2, 0.0.3, 0.0.4, 0.0.5, 0.0.6, 0.0.7, 0.0.8, 0.0.9, 0.1.0, 0.1.1)

[pacchettibotti]

Successfully uploaded package to the registry! 🎉 🚀

[pacchettibotti]

Successfully uploaded package docs to Pursuit! 🎉 🚀

[mikesol]

{ "packages": { "hyrule": "2.3.2", "bolson": "0.3.1", "deku": "0.8.1", "ocarina": "1.5.2", "rito": "0.3.2" } }

[pacchettibotti]

Processing package set update.

[pacchettibotti]

Built and released a new package set! Now mirroring to the package-sets repo...

[pacchettibotti]

Mirrored a new legacy package set.