Luca Bruno

This may be obvious to everybody reading this except me, but the update strategy message is not part of MOTD. It is instead generated for every login shell as as...

> If we really want to avoid sourcing it, we could suitably constrain it to be parseable by awk/sed. > Did you have anything particular in mind? No, I like...

Thanks for the report. It would be good to pinpoint where that error is being generated. I think this may be coming from the underlying go-dbus, possibly by some methods...

It sounds like you have pinpointed some faulty logic in `go-dbus`, so I'd suggest taking this discussion there and try to enhance that code. I'm not really keen on trying...

Gentle ping for @eklitzke. Any status update on this?

Thanks for the report. I fear you are hitting intrinsic UX issues with the whole Go module machinery, and I don't think there is much I can do as a...

@theory to the best of my understanding, the "versionless replace" hack should work as long as the versioned and non-versioned releases of this library have no API-breaking changes.

For casual readers landing here, Go modules require semver-imports as explained in the official docs: https://github.com/golang/go/wiki/Modules#semantic-import-versioning. This means that the proper way to consume this library is via versioned imports...

@theory to the best of my understanding, the `import "github.com/coreos/go-systemd/journal"` above is buggy and not valid under Go module importing rules, as stated by the official [documentation](https://github.com/golang/go/wiki/Modules#semantic-import-versioning) (emphasis mine): >...

~~@dalu please note that your comment tone is overly aggressive, and your reply doesn't bring any new/relevant content to this ticket.~~ EDIT: it looks like the user got banned from...