Problems, problems, self-induced #sewingPersonProblems.
I've done the last machine seam on the flannel shirt¹, but I want to use the same blue thread to sew a pair of linen trousers for my SO. He's not going to wear them for a few months, of course, but I want to see if the pattern is correct, so they are high priority.
However, my mother has just finished a filet crochet yoke for a nightgown that I'm going to make in linen for myself. Again, not something that is going to be worn any time soon², but it's a quick sew and it will allow me to know how much leftover linen I have for another project. But it needs a different colour of thread in the machine.
The sensible thing would be to sew the trousers during the next week, and then sew the nightgown. Luckily it's also the lazy thing, so that's probably what I'm going to do.
Can you guess how much I'd want to change plans and start with the nightgown? :D
(there will be pictures of everything mentioned. one day. :D )
@sewing group #sewing
¹ lots of handsewing remains, but that takes a different time slot.
² unless I decide to wear it as a chemise, but even then in winter I don't really need a linen one.
Vagrant Cascadian
in reply to Vagrant Cascadian • • •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!
BoosterFive 🚀
in reply to Vagrant Cascadian • • •BoosterFive 🚀
in reply to BoosterFive 🚀 • • •Vagrant Cascadian
in reply to BoosterFive 🚀 • • •@Phaserune
I put in /etc/apt/sources.list.d/people.debian.org.vagrant.sources
Uris: people.debian.org/~vagrant/deb…
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...
Index of /~vagrant/debian
people.debian.orgBoosterFive 🚀
in reply to Vagrant Cascadian • • •Vagrant Cascadian
in reply to BoosterFive 🚀 • • •Vagrant Cascadian
Unknown parent • • •@tom
Yes, that's where the patches originally came from.
I don't currently have a git repo with the patches applied, but should be able to "git am debian/patches/handy/*.patch" from the unpacked .dsc
Or... I'll just push a branch somewhere.
Vagrant Cascadian
in reply to Vagrant Cascadian • • •@tom
Pushed a couple branches to:
salsa.debian.org/vagrant/dino-…
The handy-v0.3.1 branch is based on the upstream v0.3.1 tag with the handy patches applied
There is also the debian/handy-0.3.x branch, based on of the debian/0.3.1 tag with the handy patches applied.
The patches are only slightly modified from the feature-handy branch in dino upstream, and not all are applied.
Really need to get small screen support working upstream sooner or later, as I do not like maintaining forks!
Vagrant Cascadian / dino-im · GitLab
GitLab