Dependency on old domain name #67

Closed
opened 2024-04-02 03:30:45 +00:00 by fez1 · 2 comments

I get this failure when trying to run go get after cloning itd:

go: go.elara.ws/infinitime@v0.0.0-20230421025334-f2640203e9e9 requires
        go.arsenm.dev/logger@v0.0.0-20230104225304-d706171ea6df: unrecognized import path "go.arsenm.dev/logger": parse https://go.arsenm.dev/logger?go-get=1: no go-import meta tags (meta tag go.elara.ws/logger did not match import path go.arsenm.dev/logger)

I saw in some of the commits to itd that arsenm might be an old name. Does this need to be updated?

I get this failure when trying to run `go get` after cloning itd: ``` go: go.elara.ws/infinitime@v0.0.0-20230421025334-f2640203e9e9 requires go.arsenm.dev/logger@v0.0.0-20230104225304-d706171ea6df: unrecognized import path "go.arsenm.dev/logger": parse https://go.arsenm.dev/logger?go-get=1: no go-import meta tags (meta tag go.elara.ws/logger did not match import path go.arsenm.dev/logger) ``` I saw in some of the commits to itd that arsenm might be an old name. Does this need to be updated?
Owner

Yeah, it does need to be updated. I'm working on replacing go.elara.ws/infinitime entirely, but in the meantime, I've just updated the domain.

Yeah, it does need to be updated. I'm working on replacing `go.elara.ws/infinitime` entirely, but in the meantime, I've just updated the domain.
Author

Sounds good, I hadn't seen your response when I filed the other issue (Elara6331/infinitime#28) since it's not exactly an itd issue. I'll close this one so it can be tracked there if that's alright with you.

Sounds good, I hadn't seen your response when I filed the other issue (https://gitea.elara.ws/Elara6331/infinitime/issues/28) since it's not exactly an itd issue. I'll close this one so it can be tracked there if that's alright with you.
fez1 closed this issue 2024-04-02 04:25:13 +00:00
Sign in to join this conversation.
No description provided.