Byzantium backports unofficial

Never type Yes, do as I say! (In the context of this thread) It ends badly

3 Likes

I hope didn’t reply twice, I reached daily reply limits as an new user and the browser starts acting weird. I didn’t do the ‘do as I say!’ part, ha. I found out that the package requires gnome-desktop3-data < 3.39 but this backports gnome-desktop3-data is 0.44. everytime when I got the 3.39 installed, and then if I upgrade from the backports, it will be 0.44 again when I install phosh. Has anyone install phosh 0.44 successfully? and steps that needs to be in order to install? I read above that there are similar problems as mine, but the chatty install alone with the tracker-miner-fs didn’t work for me. I am playing around the crimson now. Thanks for the help.

2 Likes

Ok, in the case if you will decide to try again please provide the full output of the apt install and/or apt dist-upgrade. I know that at least two people were able to apply backports, but the process is quite complicated due to really old age of Byzantium.

2 Likes

I don’t know if they can provide the process. I tried install librem5-gnome, gnome-shell first, it is not working due to the dependencies issue. Most of the gnome related part I got the desktop3-data 0.44 unmet dependency error. The only time that it went through all the way, is when I install Geary, it updates a lot!! But after that, some apps start to break.

I first copy the backports repo into the source.list, so alone with 3 original repos in the source list file. Then I did the sudo apt update, and then I did sudo apt install . I tried to install chatty and tracker-miner-fs, it failed due the the dependency. I would love to try again :smiley: ha.

1 Like

The problem that some packages should be replaced (not upgraded) during the process and apt can not resolve all dependencies by itself. That is why you should give a hint to explain what exactly you want :).

One way, if you see that some conflicted package exists in backports, is to install it manually together with the first one (e.g. chatty). Finally more clear error message must appears.

What exactly?

Also the full output will be helpfull for me as I might miss something. I hope that together we will able to make the upgrading process much easier! :slight_smile:

By the way, what version of Phosh offered in Crimson?

2 Likes
1 Like

I will try to get the output when I first install the chatty and tracker.miner.fs again. One thing I would like to ask, in the source list when I try, should I leave the original apt repo lists together with the back ports apt repo or comment the original ones out and only use the back ports apt repo in the source.list file? Thanks.

1 Like

Leave the originals there.
The best way I have found to install these is from the command-line:

This installs everything in the backports, hence you may want to remove the unwanted packages.

3 Likes

sudo apt install chatty tracker-miner-fs
Reading package lists… Done
Building dependency tree… Done
Reading state information… Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
libgnome-desktop-3-19 : Depends: gnome-desktop3-data (< 3.39) but 44.0-5 is to be installed
E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages

i tried again, the desktop3-data issue

if i directly run dist-upgrade, i got that do as i say warning.

1 Like

Could you specify is it a clean Buzantium installation? Which image exactly?

1 Like

I use the latest image from purism Byzantium since librem 5 flash script doesn’t fetch the latest image if I don’t provide a local one. So I just download the image and use the librem 5 flash script to flash the local image. I did use the–stable and end–debug flags though.

Here is the location that I found from one of the links that provided by franklyflawless, ha

https://storage.puri.sm/librem5/images/byzantium/latest/librem5r4/luks/artifact/

2 Likes

I would try cloning the repo,
add it to the apt/sources.list
cd into the directory
sudo apt install ./PACKAGENAME.deb
and then you could change the source list back to the codeberg repo and delete the clone

2 Likes

I only know add the repo link to the source.list. Not fully understand(my limited knowledge,ha) and by Cloning the repo and add it to the source.list? Let me see.

1 Like

Read the beginning of the thread

1 Like

So I have not been able to install 0.44

The following information may help to resolve the situation:

The following packages have unmet dependencies:
phosh : Depends: phoc (>= 0.44~) but 0.43.0-1 is to be installed
E: Broken packages
1 Like

I got this too when I try to install phosh. Again, if I install geary in the first place, and then install systemd(with other 2 packages), I was able to upgrade a lot from the system without having the do as I say message. After that, left 22 packages not able to install due to the libgnome-desktop-3-19 package is depending on the gnome-desktop3-data 0.39 but all the backport gnome packages needs gnome-desktop3-data 0.44.

By removing ibgnome-desktop-3-19(and other dependancies), I will endup in the terminal only gui after reboot(lost phosh ui), then I was able to install gnome-desktop3-data, but to install phosh ui, I have to use the original repo, but then, everything will go back again. Ha. May the image that I am using is not fit for this? I don’t know.

1 Like

No your image is fine, it is the way you are going about it that is the problem.
Try downloading those 22 files from the repo,
cd into your downloads folder,
sudo apt install ./*.deb

1 Like

Success!
I manually downloaded and installed phoc, and then phosh installed

4 Likes

I will try it. Still messing around in the terminal only pureos ha. When you install the deb file, you don’t need the source.list to be added with that git repo, right?

1 Like

No, you just need the ./ in front

1 Like