coreos
Abandoned?
Is this project maintained? Has it been abandoned? I would love to take over maintenance.
@ananthb I am interested in a Go package to read journald and restart systemd services.
Do you maintain a fork or do you use a different package?
@guettli I might start maintaining a fork depending on whether I get sign-offs from $previous_employer. We had an internal fork with a few good changes, but I don't have the energy to rewrite those.
@ananthb I use exec.Command().CombinedOutput() now. This works for my use-case. I would prefer a package. But doing that is a lot of effort.
@Luap99 @cgwalters could you give us a status on this repo? We are wondering if we should keep using it in productive software projects.
I am not a maintainer of this project (never was). I just contributed one bug fix here.
Thus I cannot speak to the status of this project. I can try contacting some of the coreos folks to clarify though.
We depend on this project in podman so keeping this maintained is important to us and I would be happy to help here to keep things going. Is there anything critical that needs attention here or did you just raise that because there were no commits in a while?
@Luap99 We encountered a bug (assuming it is a bug) that was addressed by this MR in the fork, but it was never reviewed or merged. After discovering it, we noticed there have been no commits or responses from the maintainers in a while, which raised the question of whether the project is still alive
I have access to the repo now together with @kolyshkin, I will try go over some older PRs.
I merged the CI fixes from @kolyshkin so please rebase any open PRs you have to ensure they are passing tests.
Besides if like to help please review PRs and issues here.