After seven years of maintaining PPA with custom packages for Debian, I now decided to finally drop and close it. I no longer use Debian as my main Linux distribution hence I have no need nor interest in providing any builds for it.
That being said, I also decided to pack the whole repo as is for anyone willing to either pick it up or to simply have a look on how this was done for the last few years.
I also need to give the credit where the credit is due — Julien’s Valroff’s tutorial titled Build i386 packages on amd64 brought me into world of proper Debian package building. I’m not even sure how old it is, but it’s still valid today.
As far as it comes to the software stack, the only thing I changed not long ago was finally the switch git-buildpackage. All the rest is the same —
reprepro and simple
nginx in front.
Package with the repo contents can be found on the PPAs website. It was fun and useful for the time being, thanks for the ride!
It was about time to clean a little bit up my PPA. What was removed and briefly why:
- audacious: latest stable release available in deb-multimedia repositories
- deja-dup: newer version available in official repositories
- geary: newer version available in official repositories
- revelation: latest version available in official repositories
- vala-0.22: newer version available in official repositories
That’s it so far. If you have any suggestions or you want to report any bugs, catch me on twitter.
Snappy Ubuntu Core has been announced two days ago. I was counting that sooner or later there will be some alternative to Project Atomic and here we are. What I found a bit surprising was the immediate compatibility with Microsoft Azure. I also found this statement:
Microsoft loves Linux[…]
I wanted to have a small, “minimalistic” VMs on my hypervisor, so they would have very little footprint on resources. I decided to go with systemd and btrfs for system & service management and main/only filesystem respectively.
The only considered distributions up for that task (at least from my point of view) were Debian and Gentoo. I decided to start with the latter as I had less experience with it and wanted to learn my ways around.
Recently I’ve been migrating to new infrastructure — I will most definitely write about it more in separate post(s) — and I found myself in need of some centralized log server. I played a bit with different tools and eventually settled with graylog2. Current setup looks as follows:
Eventually I’d love to put Elasticsearch and MongoDB on separate machine(s) and add one more node for graylog2-radio and RabbitMQ (though preferably having both on separate boxes too), but this can wait and I needed working solution as fast as possible. Speaking of which, what seems to be the…
Awhile back I decided to finally publish my dotfiles. It turned out that it’s not necessarily such good idea to split config files into so many small chunks — it’s harder to maintain when they are split like that. Few days ago I stubmled upon GitHub ❤ ~/ where I learned about rcm.
Logical Volume Manager
- Repartitioning LUKS-crypted LVM on Debian
- Extending LVM & FS online with new disk
- Updating GRUB device.map file after adding a new disk
- Migrating to new Logical Volume
- Extend LV & FS on-line with one command
Stay tuned cause more is coming soon! (: