[I was originally going to ask here if you had a UBports image or the original Canonical images installed, but after re-reading, I noticed that you had Canonical's image installed (since UBports is at OTA-3 now). So feel free to disregard this post, I'm not discarding it simply because it could be of use to other people further on.]
If you were using a UBports image, you shouldn't have needed to reinstall the libertine and xmir components, as they appear to come installed by default. Libertine itself also has very little in the way of dependencies. [Like above, this was before I re-read the OP]
@ctyler1984 Also, you should remove the libertine-scope package and install it from the Ubuntu Store. I'm not entirely sure if the scopes are the same version, but using the click is safer since it can receive upgrades. If you receive any OTAs from UBports or Canonical (I know, this one isn't happening), the OTA will overwrite dpkg's info files and cause the system to believe the libertine-scope package isn't actually installed, even though it is, which can cause issues when attempting to reinstall, remove or even upgrade it. (This isn't theoretical, it does actually happen, I've run into it multiple times while Canonical was still the development team since I use a modified kernel for the Nexus 7 so I can run QEMU-x86/WINE on the tablet.)
Also for future reference, you can remount without making the whole image fully writable by using sudo mount -o remount,rw / from the normal terminal. I know this is all a moot point now since you've solved your own issue, but hopefully it will help someone else in the future.
The TL;DR:
For new users to Ubuntu Touch: If you have installed from the UBports branch, libertine and it's components come installed and ready to use by default (except for the scope, you need to find that in the Ubuntu Store, or install libertine-scope using APT [Not recommended due to possible package management issues later on]
You shouldn't install packages if you're expecting to be able to OTA update, it WILL cause issues with dpkg after an OTA, they might not be visible immediately, but it will definitely show up if you attempt to upgrade, reinstall or remove packages installed before the OTA that aren't a part of the default system. I'm not telling you not to do it (that would be major hypocrisy on my part), I'm just genuinely recommending that you don't.
You don't need to permanently make the system writable (yes, it can be reversed by removing the .writable-image file under /userdata but that's more work than it needs to be, you can easily mount the rootfs read/write (and do it without rebooting, saving some time) by performing sudo mount -o remount,rw / from the terminal.
I know the post is long, that's why I did a TL;DR, sorry for the wall of text.