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

directory is not a distro (packages) or advisories repository (but it actually is) #1380

Open
dustinkirkland opened this issue Dec 29, 2024 · 1 comment
Labels
bug Something isn't working needs-triage applied to all new customer/user issues. Removed after triage occurs.

Comments

@dustinkirkland
Copy link
Member

I can't get the wolfictl command to operate. @jamie-albert helped me get started, but he was also unable to figure out what's wrong.

$ git clone [email protected]:wolfi-dev/os.git
$ cd os
$ pwd
/home/kirkland/src/wolfi/os
$ wolfictl advisory update
2024/12/29 16:02:57 ERRO distro repo dir and/or advisories repo dir was left unspecified, and distro auto-detection failed: unable to find advisories dir: unable to find repo dir
$ wolfictl advisory update

I'm in a clean clone of the wolfi-dev/os code. On a related note, I've tried running with "--log-level debug" per the in line instruction, but that doesn't work either:

$ wolfictl --log-level DEBUG advisory update
2024/12/29 16:09:42 ERROR log level out of range: -4

Here's my version info:

$ wolfictl version
 __        __   ___    _       _____   ___    ____   _____   _
 \ \      / /  / _ \  | |     |  ___| |_ _|  / ___| |_   _| | |
  \ \ /\ / /  | | | | | |     | |_     | |  | |       | |   | |
   \ V  V /   | |_| | | |___  |  _|    | |  | |___    | |   | |___
    \_/\_/     \___/  |_____| |_|     |___|  \____|   |_|   |_____|
wolfictl: A CLI helper for developing Wolfi

GitVersion:    devel
GitCommit:     797586bae957cee7ced398558290ccf5a6fc32c5
GitTreeState:  clean
BuildDate:     2024-09-17T12:17:20
GoVersion:     go1.23.1
Compiler:      gc
Platform:      linux/amd64
@dustinkirkland dustinkirkland added bug Something isn't working needs-triage applied to all new customer/user issues. Removed after triage occurs. labels Dec 29, 2024
@luhring
Copy link
Member

luhring commented Dec 30, 2024

Just curious, the build date from the version output looks old, do you know if this happens with the current code, too?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working needs-triage applied to all new customer/user issues. Removed after triage occurs.
Projects
None yet
Development

No branches or pull requests

2 participants