Recent searches
Search options
Administered by:
With the update of @dino to 0.3.1 in #debian, the functionality on small screens such as #pinephone running #mobian ... did not work so great.
The version uploaded to debian experimental, allowed resizing the different parts of the window a little bit, but still often hid useful information...
So I refreshed the libhandy patches!
Packages available from:
https://people.debian.org/~vagrant/debian/pool/main/d/dino-im
The "UNRELEASED" repository is signed by my key in the debian-keyring.
Have not tested much, but works for me!
And for better and worse, I did all the initial patch updates, packaging, building, testing, etc. on the #pinephone itself using the #squeekboard on-screen keyboard, fish shell, sbuild and #emacs.
It was a little rough at times with the small screen and limited keyboard, but it felt like the right thing to do, at least in some bizarre sense. Kind of an ouroboros of a development workflow.
Though the packages I just published, I'll admit I used my laptop to polish it up a little cleaner!
@vagrantc mighty nice of you. I can't use it because my version of dino is only 3.0. Is there some place get 3.1?
@vagrantc sorry bone head moment for me. I see you are providing it in the repo. Is the deal to just install all of the arm64 stuff?
I put in /etc/apt/sources.list.d/people.debian.org.vagrant.sources
Uris: https://people.debian.org/~vagrant/debian
Components: main
Types: deb deb-src
Architectures: amd64 arm64 armhf
Suites: UNRELEASED
Signed-By: /etc/apt/vagrant.asc
And then dump the key where you need it:
gpg --locate-key vagrant@debian.org
gpg --export --armor vagrant@debian.org > vagrant.asc
sudo cp vagrant.asc /etc/apt/
You can also extract the key from the debian-keyring package...
@vagrantc I guess the thing I'm not getting is, that when I try to install this, it removes dino, and only install dino-im-common, but of course then Dino doesn't work anymore. I'm on a Librem 5, and pulling the adaptive version of Dino from their octarine repo.
@Phaserune it was built for debian unstable/testing, so maybe not fully compatible with what you are running?