[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: [atomic-devel] different package versions on similar machines

On Mon, Jun 11, 2018 at 2:36 PM arnaud gaboury <arnaud gaboury gmail com> wrote:
I set up two Fedora atomic machines recently absolutely the same way (same etc settings, same added packages...). They could have been rsync'ed.

For unknown reasons, some packages don't have same versions. Some examples:
cockpit-docker.x86_64                                     168-1.fc28     <>       169-1.fc28 
ca-certificates.noarch                                    2018.2.24-1.0.fc28    <>  2018.2.22-3.fc28

When running # rpm-ostree upgrade on the machines with older versions, I get : No upgrade available, with a general upgrade or by package.

# rpm-ostree upgrade cockpit-docker
1 metadata, 0 content objects fetched; 569 B transferred in 3 seconds                                     Checking out tree 291ea90... done
Importing metadata [=============] 100%dora                                                              
Resolving dependencies... done
No upgrade available.

# rpm-ostree status lists the same layered packages.

What is the reason behind this difference and how to solve? Maybe an hint, the two machines were not built on the same days (in case day 0 is important for upgrades)

Thank you for help.


after diff between the two output of "dnf list installed", among various different packages I found one machine has Fedora-release 28-1 and the other one 28-2.
The machine which is still in release 28-1 has two more packages than the other machine (release 28-2):
Skopeo-containers, oci-register-machine.

Can they prevent to upgrade to 28-2 because of some dependencies?

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]