Byzantium backports unofficial

What about libedataserver, libebook-contacts, ‘libgoa’?
Also evolution-data-server should be installed. Such package exist in backports but it seems that its version mismatched… In fact I have two version of libgoa-backend installed on my phone - 3.46 and 3.52. Have no idea why it happened.

3 Likes

All the packages you have mentioned are installed

1 Like

Ok, lets check keyring and gnome-setting related packages:

$ LANG=en apt list --installed | grep keyring
debian-archive-keyring/byzantium,now 2021.1.1+deb11u1 all [installed]
debian-keyring/byzantium,now 2021.07.26 all [installed,automatic]
gnome-keyring-pkcs11/unknown,now 42.1-1 arm64 [installed,automatic]
gnome-keyring/unknown,now 42.1-1 arm64 [installed,automatic]
libpam-gnome-keyring/unknown,now 42.1-1 arm64 [installed,automatic]
pureos-archive-keyring/byzantium,now 2021.11.0 all [installed]
$ LANG=en apt list --installed | grep setting
dconf-gsettings-backend/byzantium,now 0.38.0-2 arm64 [installed,automatic]
gnome-settings-daemon-common/unknown,now 47.1-2 all [installed,automatic]
gnome-settings-daemon/unknown,now 47.1-2 arm64 [installed,automatic]
gsettings-desktop-schemas/unknown,now 47.1-1 all [installed,automatic]
phosh-mobile-settings/unknown,now 0.43.0-1 arm64 [installed]
qml-module-qt-labs-settings/byzantium,now 5.15.2+dfsg-6 arm64 [installed,automatic]
1 Like

May be there is some option to control this behavior or the module/library responsible for the priority that is familiar for you?

Check

and

2 Likes

And this fixes the copy-paste error in the above commit: data: Really add gnome-clocks (!148) · Merge requests · Librem5 / feedbackd · GitLab to really use gnome-clocks app-id. But the idea remains the same.

2 Likes

This made the job!
Everything works as expected, thank you very much!
Backports are updated :slight_smile:

3 Likes

By the way, it looks like packages can be downloaded directly from codeberg. The next line should be added into /etc/apt/sources.list

deb  [allow-insecure=yes] https://codeberg.org/galilley/librem5-byzantium-backports/raw/branch/main ./
2 Likes
$ apt list --installed | grep keyring

WARNING: apt does not have a stable CLI interface. Use with caution in scripts.

debian-archive-keyring/byzantium,now 2021.1.1+deb11u1 all [installed]
gnome-keyring-pkcs11/now 42.1-1 arm64 [installed,local]
gnome-keyring/now 42.1-1 arm64 [installed,local]
libpam-gnome-keyring/now 42.1-1 arm64 [installed,local]
pureos-archive-keyring/byzantium,now 2021.11.0 all [installed]

$ apt list --installed | grep setting
dconf-gsettings-backend/byzantium,now 0.38.0-2 arm64 [installed,automatic]
gnome-settings-daemon-common/now 47.1-2 all [installed,local]
gnome-settings-daemon/now 47.1-2 arm64 [installed,local]
gsettings-desktop-schemas/now 47.1-1 all [installed,local]
phosh-mobile-settings/now 0.43.0-1 arm64 [installed,local]

I appear to be missing:

debian-keyring/byzantium,now 2021.07.26 all [installed,automatic]

but it did not help.

1 Like

since these aren’t signed there is an error but using ‘deb [allow-insecure=yes]’ also still generates the following errors running “sudo apt update”.

“Encountered a section with no Package: header”
“Problem with MergeList /var/lib/apt/lists/codeberg.org_galilley_librem5-byzantium-backports_src_branch_main_._Packages”
“The package lists or status file could not be parsed or opened”

1 Like

I fixed the url, looks like it works now, please check.

2 Likes

Worked like s charm!!

3 Likes

Turns put the issue here was far simpler…

My randomly generated passwords I was trying with both contained a \ char.

The error was something about parsing a string, so I figures I would try, and yes, changing my passwords to remove the \ got me connected again.

I will do a little digging and see if an Issue needs to be filed for Gnome Control Center or Libadwaita or whatever.

2 Likes

So, are you able to get the list of your contacts now?

2 Likes

Yup, all set!
I have very few issues now running your backports, and I’m not even sure they are attributable to your backports at this point.

4 Likes

@galilley
What are the steps involved if I wanted to get pipenv backported and available to install?

I’m not necessarily asking you to do it (you’ve done so much work already), but more curious about how it would be done.

When I try to install this now:

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:
 python3-pip-whl : Breaks: python-pip-whl (< 21.3.1+dfsg-2~) but 20.3.4-4+deb11u1 is to be installed
 python3-setuptools-whl : Breaks: python-pip-whl (< 21.3.1+dfsg-2~) but 20.3.4-4+deb11u1 is to be installed
E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages.
1 Like

Well… as far as some critical number of packages have already rebuilt and nobody should download the whole backports repo (just add the link to apt/sources.list) we could try to rebuild some stuff directly on the phone (the most easiest and a quite dirty way :wink:)!

Here are the steps on how to do it:

  1. Be sure that dpkg-dev is installed (sudo apt install dpkg-dev, byzantium version)
  2. Make a folder where you will build a package (mkdir /mnt/storage/pkgs) and go into.
  3. Download the sources for your package:
    3.1. Go to packages.debian.org to search the right version. You could also use snapshot.debian.org to find some intermediate version of the package. Sometimes it is really important as far as trixie-s version could be too new and bookworkm-s is too old.
    3.2. Prefer bookworm repo is it enough (pipenv).
    3.3. Use dget for .dsc file to download and unpack the sources:
    dget http://deb.debian.org/debian/pool/main/p/pipenv/pipenv_2022.12.19+ds-1.dsc
  4. Be careful about additional active cooling of your phone :hot_face:.
  5. Go to the package folder and run dpkg-buildpackage -b -rfakeroot -us -uc (link).
  6. If you’re lucky, you won’t need any additional dependencies. Me not :rofl: : Unmet build dependencies: build-essential:native dh-python python3-mock python3-pytest-xdist python3-virtualenv python3-virtualenv-clone. In fact this is the most difficult point - to satisfy build dependencies.
    6.1. Some of the packages in the list have been already rebuild by me and another one are available in byzantium, so at this step run apt update (to download updated list of backports) and install all of them.
    6.2. Run dpkg-buildpackage -b -rfakeroot -us -uc again. Fell free to use -nc flag to avoid some initialization steps and continue build.
  7. Install the fresh package: $ sudo apt install ../pipenv_2022.12.19+ds-1_all.deb
  8. Ooops, I’m accidentally rebuild pipenv for you! :grin: So, now you can just install it from backports but I believe that this small howto will be useful and fell free to ask me about -dev versions of the backported packages as far as I do not include them until today.
  9. And the last but not least. It will be much better do not install -dev packages into your system to not litter them and do not waist the space on your root. Just create a separate chroot environment where you will install everything that you need to build a new package (link):
    $ debootstrap --arch=arm64 byzantium ./byz https://repo.pureos.net/pureos
3 Likes

Flathub works fine

2 Likes

In the last few days I perform some investigations in gnome-calls. The memory consumption was extremely huge (about 2 Gb). It looks like due to connection with gmail.com (yes, I use google to store my contacts and sync them with other devices, including android phone, by historical reasons). Gmail creates a stub avatar (just the first letter on the colored background) for each contact (about 500 pieces in my case) with 1MPix resolution. So, all together they resulted in 1.5 Gb (1Mpix x 3 color) of raw images that gnome-calls trying to load and show me all time. The right solution is to scale each avatar down to 64x64 pix or something else which reduce the memory consumption a lot, but I have no time to do it in the right way. So, I just disable all avatars at al. As a result, gnome-calls takes less than 200 Mb (as it should be). Exactly this version of gnome-calls come to backports, so, you could save a little bit RAM for other apps :).

I’ve also added readme on my codeberg page with the address of my crypto wallet. So, if you are really like what I do you could send me some USDT to by a coffee :heart:.

4 Likes

Nice!
Minor question: Is there a way to make the list of packages collapse so that you can get to the ReadME faster?

2 Likes

No, not unless all of the packages are moved into its own directory, but you can access the README.md file itself: