SpiralLinux / SpiralLinux-project

SpiralLinux project
https://spirallinux.github.io/
142 stars 5 forks source link

KDE desktop installation fails while installaing from synaptic package manager or tasksel #62

Closed samarkv closed 2 years ago

samarkv commented 2 years ago

KDE desktop installation fails while installing from synaptic package manager or tasksel. It is due to unresolved dependency caused by library packages installed from backports repository while the installer expects those packages from stable repository. I am giving a link to two videos from my channel where you will know exactly which unresolved dependency are causing failure of KDE desktop installation.

Video links - 1) https://youtu.be/IjtQj9oPXiU 2) https://youtu.be/C6GxmpItXR0

geckolinux commented 2 years ago

Hi there, thanks for the report and thanks for the Youtube coverage.

In general I can't offer support for the Builder edition since it's basically a blank slate and the possibilities and methods of customizing it are practically infinite. However, what you were trying to do will definitely work.

Regarding tasksel, the desired component for installation needs to be selected first with the spacebar before proceeding.

Regarding the Synaptic troubles, It can't be a matter of missing dependencies or problems with Backports, since the SpiralLinux Plasma ISO can be successfully generated using the exact same packages and Debian repository configuration. I think that maybe you just needed to refresh the package indexes.

In general, when you see broken packages, the solution is usually via refreshing the package indexes and/or removing conflicting packages, not installing additional ones. Broken packages will never be resolved by installing more packages, because if a resolution was possible via any other package in the available repositories then APT would install it automatically to satisfy the dependencies.

In my test it allowed me to proceed with the same selections you tried:

*All the packages selected in the KDE Desktop section (except one `gambas` package that was broken and was deselected):**

Screenshot from 2022-07-30 08-51-48

kde-full full KDE installation metapackage:

Screenshot from 2022-07-30 08-54-55

kde-standard metapackage:

Screenshot from 2022-07-30 08-55-34

samarkv commented 2 years ago

I have again made a video for KDE install using tasksel. I selected the KDE option using spacebar. But installation is failing due to unresolved package dependency.

Please watch my detailed video on this subject which will be released at 1am IST tomorrow.

samarkv commented 2 years ago

If you watch my both videos I always do apt update before installing new desktop. So package indexes are refreshed before installation.

geckolinux commented 2 years ago

It could always be a network error or a local Debian mirror that is out of sync. This is my attempt with tasksel to install KDE on a fresh installation: Screenshot from 2022-07-30 09-54-05

samarkv commented 2 years ago

check this out Screenshot_20220729_155812

samarkv commented 2 years ago

I changed the mirrors from main to India and back to main. But both installation attempts failed.

samarkv commented 2 years ago

I will give another try in next few days.

geckolinux commented 2 years ago

It appears that gdb and gdb-minimal conflict with each other. Please try installing just one of them.

samarkv commented 2 years ago

I finally found out the issue. It is with india server. Screenshot_20220801_142423 .

samarkv commented 2 years ago

APT does not install one of the two packages gdb or gdb-minimal as full packaging indexes are yet to downloaded and refreshed. This is because of repository download issue with India server shown in screenshot above.

samarkv commented 2 years ago

If I use main server, then I am able to install KDE desktop using any expert install method.

geckolinux commented 2 years ago

Thanks for testing and confirming that. The default package repository URLs that SpiralLinux uses point to deb.debian.org, which is actually a redirection service to a mirror network (reference). So you were probably being randomly redirected to the nearest server in India or a nearby country, which was temporarily out of date.