Going from using local-rpm to upstream version of a specific package.

[postmannen]

We want to ditch a custom package and replace it with the same but newer version upstream.

I've tried searching for info about this and also asking on the IRC but so far it seems it is not possible based on the answers I've got.

In my mixer an earlier version of NetworkManager v1.20.4 was installed with local packages in local-rpms. I try to remove the files in the local-rpms, and keep the include(NetworkManager) entry in the local-bundles, do a version update --upstream-version latest, and rebuild. But it still continues to keep the 1.20.4 version and do not pick the latest upstream.

1. Is this possible, and in case how, and preferably with a detailed routine of how to do it ?
2. Could this be built into the mixer-tools ? We got mixer add-rpms today, could there also be a remove-rpm which let us go back to using the default upstream bundles/packages ?

[postmannen]

Seems like deleting the package rpm files both under local-rpms and local-yum removes all the traces of the custom package, and then after a new build it switches to using the latest upstream version.

If anyone can confirm that this is the right procedure it would be really great.

[postmannen]

A little odd..
Did the first testing in a lab environment where the deletion seemed to work ok.
But when testing on my prod server building the mix after deleting the NetworkManager-* from both local-rpms and local-yum, then building the bundles give the following error
Error: Error building bundles: rpm not found for pkg: NetworkManager-config-1.20.4-61.x86_64

Any help or advice would be highly appreciated.

[postmannen]

Seem like the trick was to do a mixer add-rpms after deleting the files in the local-rpms and local-yum directories. Then the build worked, and the latest upstream version of NetworkManager was used.