-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
[sonic_debian_extension.j2] fix systemd version not from buster-backp… #7322
Conversation
…orts Signed-off-by: Stepan Blyschak <[email protected]>
/azp run |
Azure Pipelines successfully started running 1 pipeline(s). |
/Azp run |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run |
Azure Pipelines successfully started running 1 pipeline(s). |
/azpw run |
Hello! The latest build seems to fail to boot Docker on my Arista platform. See #7372 for details. Could this PR be related given that it touches systemd? The diff is pretty small of potential culprits and I think this might be the biggest related change. EDIT: I reverted this commit in my own master branch and that solved the issue for me. Would appreciate if you could comment on the issue #7372. |
…er-backports (sonic-net#7322)" This reverts commit 4369361.
…orts (sonic-net#7322) Install systemd explicitelly from backports and install libsystemd* packages from backports. Signed-off-by: Stepan Blyschak <[email protected]>
…orts (sonic-net#7322) Install systemd explicitelly from backports and install libsystemd* packages from backports. Signed-off-by: Stepan Blyschak <[email protected]>
…orts
Signed-off-by: Stepan Blyschak [email protected]
Why I did it
To fix systemd is not the right version
How I did it
Install systemd explicitelly from backports and install libsystemd* packages from backports.
How to verify it
systemd --version
Which release branch to backport (provide reason below if selected)
Description for the changelog
A picture of a cute animal (not mandatory but encouraged)