Hi, considering SUSE employees are being motivated to help maintaining orphaned packages I'd like to help maintaining this package. Of course this package isn't orphaned but it looks like there's still help needed, e.g. last time I had to update quite a big gab (https://build.opensuse.org/request/show/999209) and now the package is again one major version behind.

Am I correct that I should first update to the latest minor/patch version within the currently packaged major version to submit this to Leap first (and only then update to the current major release)?

Marius Kittler (mkittler) - almost 2 years ago

maintainer

Looks like the last two 8.x releases (https://github.com/grafana/grafana/releases/tag/v8.5.16 and https://github.com/grafana/grafana/releases/tag/v8.5.20) were just updating the Go version. Is it necessary to take note of these at all (considering we're using out own version of Go)? Supposedly these tags could also be left out in grafana.changes as they are not relevant for our packaging (and grafana.changes will likely get cluttered enough).

Marius Kittler (mkittler) - almost 2 years ago

maintainer

I went ahead and created an updated package: https://build.opensuse.org/package/show/home:mkittler:branches:server:monitoring/grafana

I'm going to submit it after testing it locally.

I would update this package but for me the yarn build fails:

# This file contains the result of Yarn building a package (esbuild@npm:0.18.12)
# Script name: postinstall


node:internal/process/esm_loader:40
      internalBinding('errors').triggerUncaughtException(
                                ^
TypeError [Error]: [ERR_IMPORT_ASSERTION_TYPE_MISSING]: Module "file:///hdd/osc/home:mkittler:branches:server:monitoring/grafana/tmp.ZaCkiUwfW9/grafana-10.2.1/.yarn/unplugged/esbuild-npm-0.18.12-cca10dbb26/node_modules/esbuild/package.json" needs an import assertion of type "json"
    at load$1 (file:///hdd/osc/home:mkittler:branches:server:monitoring/grafana/tmp.ZaCkiUwfW9/grafana-10.2.1/.pnp.loader.mjs:1458:17)
    at nextLoad (node:internal/modules/esm/hooks:749:28)
    at Hooks.load (node:internal/modules/esm/hooks:382:26)
    at MessagePort.handleMessage (node:internal/modules/esm/worker:199:24)
    at [nodejs.internal.kHybridDispatch] (node:internal/event_target:810:20)
    at exports.emitMessage (node:internal/per_context/messageport:23:28) {
  code: 'ERR_IMPORT_ASSERTION_TYPE_MISSING'
}

Node.js v21.1.0

The yarn build no longer fails for me with the current version. However, now the Go build fails and updating to the latest version doesn't change that. I suppose we need to wait until https://github.com/grafana/grafana/pull/82114 has been released.

I tried to update this considering the current version is quite old. Unfortunately the current version tag is not a valid package version (at least my local osc build invocation complains about it). I tried to make the source services cope with that and produce a compatible version instead but haven't had success yet and spending more time on it is not reasonable. So I suppose we just wait for the next tag that will hopefully be supported again. Note that the current version is supposedly not affected by the recently revealed security venerability so there's no pressure to update this package now.

And I hope it will be acceptable to simply update this to the latest version and have a combined changelog based on the changelog diff that the source service produces. Otherwise it would be too much effort for me to update this package anyway.