libcgroup: update to 2.0

[wibed]

General

• [ x] This is a new package and it conforms to the quality requirements

Have the results of the proposed changes been tested?

• I use the packages affected by the proposed changes on a regular basis and confirm this PR works for me
• [x ] I generally don't use the affected packages but briefly tested this PR

[paper42]

continuation of #32231

the commit message is wrong, it should be libcgroup: update to 2.0

[paper42]

No, run git commit --amend and fix the commit message there.

The build is failing now, did you test it on your machine? I think we removed the failing patch in the previous PR, didn't we?

[wibed]

git commit --amend is what i run

i have adjusted the patches to be compatible with git patches

[paper42]

No, run git commit --amend and fix the commit message there.

git commit --amend is what i run

but for some reason you are not editing the commit message

• did an editor open for you?
• did you edit the message in it?
• did you save the file in the editor?

git show will tell you the commit message.

If you are not able to edit the commit message interactively, this command should work:

git commit --amend --no-edit -m "message"

i have adjusted the patches to be compatible with git patches

👍

The build is failing now, did you test it on your machine? I think we removed the failing patch in the previous PR, didn't we?

CVE-2018-14348 affects only versions up to (and including) 0.41, so we don't need the patch for 2.0. Didn't we already discuss this? Could you build it on your machine before pushing here to make sure simple mistakes like this don't happen?

[paper42]

fix the commit message

[wibed]

does the commit message has to contain something special i am currently not aware of?

[paper42]

does the commit message has to contain something special i am currently not aware of?

The commit message is correct now, thanks.

[paper42]

@wibed could you test if qomui and mininet still work with this version of libcgroup?

[wibed]

ill have a look tomorrow if i get to it

[github-actions]

Pull Requests become stale 90 days after last activity and are closed 14 days after that. If this pull request is still relevant bump it or assign it.