Downgrade Rpm Package Yum
Gaby Zenz
If you have the version number, or the target release, apt-get supports choosing a particular version or target release. More details can be found on manual page of apt-get. It can also be accessed from terminal by typing man apt-get
Remark that when using a target release (option -t), the release priority must greater than 1000 to allow downgrades (see man 5 apt_preferences) otherwise the currently installed version will be kept.
Then, you may download the version you would like to install and keep it in a folder, say abc.deb in Downloads. Open terminal, move to the folder using cd command and install the previous version using dpkg:
Update: I am still getting warnings mentioned above. My web projects warn about the Microsoft.NETCore.App package (see screenshot below) and my lib projects warn about NETStandard.Library (see screenshot above)
I opened the YourAwesomeApp.csproj file and went through the "Detected package downgrade" errors one-by-one and manually changed the version of that line item from the existing version to the specified version that was shown in the error itself.
The downside to this that I only had 5 errors this time but what if another person's project contained say 50 such errors. Then that person's task of manually editing those lines would be very tedious and time-consuming.
This is because Visual studio won't automatically upgrade this dependency as you've specified an explicit version for your project. You can either upgrade the dependency in your project to the minimum required version or remove it from your project, and let the package you're installing handle it.
To resolve this, in our example above, this would mean finding 'Newtonsoft.Json 8.0.0' and upgrading it to version '9.0.0' or simply removing it from your project prior to installing your package.
Go to Manage NuGet Packages for the project and search for"System.Diagonistics.DiagonsticSource" andupdate. Bear in mind that this may also cause another "Detectedpackage downgrade" error (you should go back to step one if thishappens)
A dependency package specified a version constraint on a higher version of a package than restore ultimately resolved. That is, because of the "nearest wins" rule when resolving packages, a nearer package in the graph may have overridden a distant package.
I had two libraries A, and B. Library A depended on some nuget package X, and library B depended on A. Once I upgraded X to a new version, somehow it started depending on a new version of NETStandard.Library nuget package (from 2.0.2 to 2.0.3), which broke the build of B with the error Detected package downgrade: NETStandard.Library from 2.0.3 to 2.0.2. Reference the package directly from the project to select a different version.
The issue for me was that I had packages installed locally that were of higher versions than my projects referenced. If you go to Tools > NuGet Package Manager > Package Manager Settings > General > Clear All NuGet Cache(s) then rebuild your solution it'll install the packages referenced and the errors will go.
Note: no line was present for this package, I copied the name and the version from the error. afterwards, do a clean and build and the error should be gone and you should be able to add whatever package you were trying to add. if error still doesn't go away, try "dotnet restore" in package manager console window.
I could solve the problem by downloading earlier version of the package causing the problem, that seems to be caused by depending on a .NET Standard version that's not installed, this also should be solved by updating Visual Studio.
When deploying the newest Electric Utility Network Enterprise v1 asset package it appears that it was created in Pro 2.7 which puts it at V5 and only compatible with Enterprise 10.9. I have Enterprise 10.8.1 and running Pro 2.6 so my utility networks are in V4 for the 10.8.1 Enterprise compatibility.
Is there a way to downgrade or drop the asset package to V4 that Pro 2.6 can recognize to be able to apply to the Enterprise 10.8.1 server environment? If not that any user not on Enterprise 10.9 can not utilize the Electric Utility Network Enterprise package and are forced to use the Electric Network Foundation packages which have already been moved to mature support.
In Electrical I had to delete Object ID 15, 16, and 17. Once I did this the tool ran just fine and downgraded the EnterpriseV1 to a utility network v4 to be able to work on Pro 2.6 and Enterprise 10.8.1
Lindsey, we are in the same boat as well with another project but with Water and Sewer. While we were planning for a water deployment a new sewer solution was released with Pro 2.7 which will only work with 10.9. We are thinking we may just build a UN from scratch with Pro 2.6 to put it at V4. We will then copy the guts out of the new data model and move forward from there. A lot of the dependencies seem to lie with the attribute rules which we've started deleting anyway from the asset package as they can slow down load times and usability times drastically. We then add in what we need depending on the need. If you can get this figured out please let me know. We've tried every approach less the total build out of a UN from scratch. I hope it doesn't come to that...
How can I manually downgrade one or a handful of packages ? Ideally without wrecking my system ? And how would I go about that ? This would allow me to test DNF Automatic without having to wait for new available updates.
In Fedora you can add the following repo
dnf install fedora-repos-archive
this allows the downgrade, or reversal of any single package or even a whole dnf update.
whole updates are done with dnf history.
I think all RPM distributions should offer this, its not that hard to do, just archive all prior versions
of packages to the archive repo before replacing the current main update repo with new.
why kill off one of the best features of rpm based distributions by not offering this.
people often find that an rpm package update has introduced a conflict or issue with there single workstation, and want to prove its the update that caused it, and then file a bug report.
of course if the distribution ie rocky in this case does not offer this, it is possible to create your own
repo localy on your network, that prior to reposync , copies all old versions to an archive repo , and runs createrpo on it, then make all your servers and workstations use the local repos instead of pulling from rockys repos, this will also lighten the load on the mirrors, essential to do if you are a company with many rocky instances.
regards peter
Thanks for all your input, guys. I found a very simple solution to my problem. Remember that the main objective here was to test DNF Automatic, so I needed to downgrade any random package from my server installation to create the need for an update. I simply chose a package from a third-party repository whose policy it is to keep older versions, and I chose Lynis for this:
One way to do this, as you found out, is to specify each version manually in the install command. If you want to make sure the dependencies will be removed when pigpio is removed, you can mark them as auto with apt-mark after installation.
This normally should work, but for some reason it doesn't for pigpio, probably because there's only one package in the default release. What does work with pigpio is the -t release option, and you can find out what release a package belongs to with apt-cache or apt policy:
If autoremove doesn't remove all the dependencies, it means that something else in your system is depending on those packages. You'll need to either uninstall that something, or downgrade it along with pigpio. Note that specifying old package versions manually wouldn't work in such a case either.
But there is one catch: The release must be configured to allow downgrades. This means its preference must be greater than 1000 because otherwise apt will keep the currently installed version. For more details see -tips.com/t/downgrade-a-package-with-its-dependencies/261
it prompts me for y/n and either way the package doesn't install. Ok so I go ahead and downgrade gcc and gcc-lib to version 11. I still get the same prompt on trying to downgrade cuda. I also tried using the downgrade package from the AUR, hoping there was a recursive downgrade feature. How can I resolve this issue?
If you are installing a package that depends on aur packages, you need to handle those dependencies yourself first. Downgrading is irrelevant (and a very bad idea). If you need to install the package in your first post, you need to install the package named gcc11 which is currently in the AUR.
I've never tried to enter an URL after the -U, so I'm not sure that would work. However, as you were already told, you need to list all the dependencies. But you don't have to use pacman to downgrade a package. You can simply use the package named "downgrade" (trizen -S downgrade) and then use it like this:
Or, if you still insist on using pacman for the downgrade, then visit the Arch's archive here (this is the address from which Downgrade gets the packages you have requested to be downgraded): and manually download each package and its dependencies, then put them in a separate directory which doesn't contain any other files and simply do
No, you do not need to list all dependencies. You can't, really, or you're going to destroy the system. None of that, nor the downgrade package, have anything to do with the OP's issue of not having gcc11.
Has anyone been able to get the opkg --force-downgrade option to work? I've tried all sorts of variations without success. The only way I can revert a package to a previous version is by uninstalling it, restricting access to the only the specific version I want (either by removing the package from the repo or directing the sbRIO to another repo that doesn't have the updated version), and reinstalling the package. I'm hoping somebody has a better way.
c80f0f1006