Dashboards and editors for Graphite, InfluxDB, OpenTSDB
http://grafana.org/
A graph and dashboard builder for visualizing time series metrics.
Grafana provides ways to create, explore, and share
dashboards and data with teams.
- Sources inherited from project server:monitoring
- Devel package for openSUSE:Factory
-
7
derived packages
- Links to openSUSE:Factory / grafana
- Download package
-
Checkout Package
osc -A https://api.opensuse.org checkout home:ioguix:check_pgactivity/grafana && cd $_ - Create Badge
Refresh
Refresh
Source Files
| Filename | Size | Changed |
|---|---|---|
| Makefile | 0000000965 965 Bytes | |
| README | 0000001076 1.05 KB | |
| _service | 0000000457 457 Bytes | |
| _servicedata | 0000000224 224 Bytes | |
| grafana-5.0.0.tar.xz | 0030139268 28.7 MB | |
| grafana-rpmlintrc | 0000000121 121 Bytes | |
| grafana.changes | 0000009119 8.91 KB | |
| grafana.spec | 0000006206 6.06 KB |
Revision 6 (latest revision is 133)
Jan Fajerski (jfajerski)
accepted
request 604489
from
Dirk Mueller (dirkmueller)
(revision 6)
- fix build for older distributions
Comments 5
Hi, considering SUSE employees are 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)?
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).
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.0The 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.