09-01-2024, 05:29 AM
Hello,
I'm not going to be able to help you with the modem, as i don't use it. On the other hand, here are a few explanations for the update problems that should definitely solve your current and future problems.
The regular ‘core’ and ‘extra’ repositories (‘community’ is now deprecated) contain packages that are sometimes removed to be replaced by their equivalents from further development, but renamed differently. And there have been a lot of these over the last few months, I myself have encountered the same difficulties updating my Manjaro with Plasma mobile system. These problems also occur when changing from the regular branch to the test branch. I'm going to be fairly precise in my explanations, as I've noticed that these problems recur on several forums.
OK, let's go!
The packages that cause conflict problems are ‘foreign’ packages, which are therefore not present in the regular repositories, as opposed to the packages that exist in these regular repositories, which are ‘native’ packages. It should also be noted that packages installed from the AUR are also ‘foreign’ packages. The list of ‘foreign’ packages can be obtained as follows:
You should recognize in this list the names of packages that have caused you problems, in principle.
All foreign packages can be safely removed, as they are not necessary for the regular operation of the system. And if one of them is nevertheless necessary (as a dependency, for example) pacman will give you a warning. But don't confuse a warning related to a conflict with other ‘foreign’ packages that you're going to remove anyway (some depend on each other), with warnings related to a conflict with ‘native’ packages. That's why you need to remove the whole list of ‘foreign’ packages at once. To avoid wasting time recopying the names of all the packages on a very long line, here's how to use an intermediary file :
(the lower-case ‘q’ is used to create the list without the package version number, as this would cause problems)
and then :
If required, the list of files (list.txt) produced by the ‘sudo pacman -Qmq > list.txt’ command can then be edited with a text editor, for example to remove packages installed by the user from the AUR, otherwise they will have to be reinstalled. (This have to be done before using the command ‘sudo pacman -R - < list.txt’, of course).
Finally, you need to clean up the system by removing all orphaned dependencies that are no longer required by other packages. To do this, the list can be obtained using the following command:
You can in the same way use a file list.txt to make things easier:
These last two commands should be repeated several times, until pacman returns an error because the entry is mute (because the list is empty). Deleting a dependency does not delete the dependency of the dependency, this is the reason (other methods exist, I like this one because I can see how my system is evolving).
And one last piece of advice: for dbus, ‘dbus-broker-units’ is the recommended choice in archlinux and it's also the one I've made, everything works fine on my pinephone.
I hope I've been able to help you as much as possible.
Best regards.
I'm not going to be able to help you with the modem, as i don't use it. On the other hand, here are a few explanations for the update problems that should definitely solve your current and future problems.
The regular ‘core’ and ‘extra’ repositories (‘community’ is now deprecated) contain packages that are sometimes removed to be replaced by their equivalents from further development, but renamed differently. And there have been a lot of these over the last few months, I myself have encountered the same difficulties updating my Manjaro with Plasma mobile system. These problems also occur when changing from the regular branch to the test branch. I'm going to be fairly precise in my explanations, as I've noticed that these problems recur on several forums.
OK, let's go!
The packages that cause conflict problems are ‘foreign’ packages, which are therefore not present in the regular repositories, as opposed to the packages that exist in these regular repositories, which are ‘native’ packages. It should also be noted that packages installed from the AUR are also ‘foreign’ packages. The list of ‘foreign’ packages can be obtained as follows:
Code:
sudo pacman -QmYou should recognize in this list the names of packages that have caused you problems, in principle.
All foreign packages can be safely removed, as they are not necessary for the regular operation of the system. And if one of them is nevertheless necessary (as a dependency, for example) pacman will give you a warning. But don't confuse a warning related to a conflict with other ‘foreign’ packages that you're going to remove anyway (some depend on each other), with warnings related to a conflict with ‘native’ packages. That's why you need to remove the whole list of ‘foreign’ packages at once. To avoid wasting time recopying the names of all the packages on a very long line, here's how to use an intermediary file :
Code:
sudo pacman -Qmq > list.txt(the lower-case ‘q’ is used to create the list without the package version number, as this would cause problems)
and then :
Code:
sudo pacman -R - < list.txtIf required, the list of files (list.txt) produced by the ‘sudo pacman -Qmq > list.txt’ command can then be edited with a text editor, for example to remove packages installed by the user from the AUR, otherwise they will have to be reinstalled. (This have to be done before using the command ‘sudo pacman -R - < list.txt’, of course).
Finally, you need to clean up the system by removing all orphaned dependencies that are no longer required by other packages. To do this, the list can be obtained using the following command:
Code:
sudo pacman -QdtYou can in the same way use a file list.txt to make things easier:
Code:
sudo pacman -Qqtq > list.txt
sudo pacman -R - < list.txtThese last two commands should be repeated several times, until pacman returns an error because the entry is mute (because the list is empty). Deleting a dependency does not delete the dependency of the dependency, this is the reason (other methods exist, I like this one because I can see how my system is evolving).
And one last piece of advice: for dbus, ‘dbus-broker-units’ is the recommended choice in archlinux and it's also the one I've made, everything works fine on my pinephone.
I hope I've been able to help you as much as possible.
Best regards.