You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the below, I would expect to see both the source-release property, the build-release property and the repository origin of the listed entities (it might also be nice to point out which of the candidates is installed if any):
ermo@snekhtpc:~/repos/serpent-os/recipes/g/golang [fix-golang* +4 ~2 -0 !]
$ moss info golang
Name golang
Version 1.22.6
Homepage https://golang.org
Summary
Description Dependencies soname(libc.so.6(x86_64))
Providers binary(go)
binary(gofmt)
name(golang)
soname(libstd.so(x86_64))
Name golang
Version 1.22.6
Homepage https://golang.org
Summary
Description Dependencies soname(libc.so.6(x86_64))
Providers binary(go)
binary(gofmt)
name(golang)
soname(libstd.so(x86_64))
The text was updated successfully, but these errors were encountered:
ermo
changed the title
moss info does not show source-release nor origin
moss info does not show source-release, build-releae nor repository origin properties
Aug 18, 2024
ermo
changed the title
moss info does not show source-release, build-releae nor repository origin properties
moss info does not show source-release, build-release nor repository origin properties
Aug 18, 2024
We now use a nice formatted list for deps/providers, visually
breaking up some of the noise. We also munch through potentially
crappy descriptions to emit as an aligned paragraph in the CLI
output.
As part of issue #333 we unique the input set to not print the same
remote version that is installed locally, and add missing build and
source release fields.
Signed-off-by: Ikey Doherty <[email protected]>
In the below, I would expect to see both the source-release property, the build-release property and the repository origin of the listed entities (it might also be nice to point out which of the candidates is installed if any):
The text was updated successfully, but these errors were encountered: