{"@attributes":{"version":"2.0"},"channel":{"title":"Debian on Dhole's blog","link":"https:\/\/dhole.github.io\/categories\/debian\/","description":"Recent content in Debian on Dhole's blog","generator":"Hugo","language":"en-us","lastBuildDate":"Sat, 04 Jun 2016 00:13:28 +0200","item":[{"title":"No more unencrypted emails to gpg contacts","link":"https:\/\/dhole.github.io\/post\/check_mail_gpg\/","pubDate":"Sat, 04 Jun 2016 00:13:28 +0200","guid":"https:\/\/dhole.github.io\/post\/check_mail_gpg\/","description":"<p>I have been using mutt for about half a year already and I&rsquo;m very happy with it.\nThe previous email client I used was Thunderbird (with the Enigmail extension to\nhandle GPG).  There were two main reasons that made me switch.<\/p>\n<p>The first one was that I often would like to check my email while I&rsquo;m offline,\nand it seems that Thunderbird is not very good at this.  Sometimes not all my\nemail would have been downloaded (just the headers), and I also found it\nfrustrating that after marking more than 50 emails as read while offline, they\nwould be marked as unread again once I went back online.  With mutt I&rsquo;m using\nmbsync (which apparently is faster than offlineimap) to sync my email to a local\nfolder with a cron job.  I couldn&rsquo;t be happier.<\/p>"},{"title":"Reproducible builds on Debian for GSoC 2015, 1st update","link":"https:\/\/dhole.github.io\/post\/reproducible_builds_debian_gsoc2015_update_1\/","pubDate":"Thu, 06 Aug 2015 20:12:15 +0200","guid":"https:\/\/dhole.github.io\/post\/reproducible_builds_debian_gsoc2015_update_1\/","description":"<p>This is the second blog post I&rsquo;m writing about my experiences contributing to Debian for Google Summer of Code 2015 (check my <a href=\"https:\/\/dhole.github.io\/post\/reproducible_builds_debian_gsoc2015\/\">first post<\/a>)<\/p>\n<h1 id=\"status-update\">Status update<\/h1>\n<h2 id=\"first-month\">First month<\/h2>\n<p>It&rsquo;s been two months and a few days since the GSoC started. During the first month I worked on fixing specific packages, mainly concerning issues with timestamps, which is a very common source of unreproducibility. In many cases, during the build process files are compressed into gzip or zip archives, which store the creation time of files in the metadata. This can lead to unreproducible results when there is timezone variation between builds (easily fixed setting the timezone to UTC before the compression happens). In some cases the compressed files are generated during the build, and thus add build times in the metadata of compressed files (in this case the creation date of the files needs to be normalized somehow).<\/p>"},{"title":"Reproducible builds on Debian for GSoC 2015","link":"https:\/\/dhole.github.io\/post\/reproducible_builds_debian_gsoc2015\/","pubDate":"Sun, 10 May 2015 17:14:05 +0200","guid":"https:\/\/dhole.github.io\/post\/reproducible_builds_debian_gsoc2015\/","description":"<p>This is the first blog post of a series I will be writing about my experiences contributing to Debian for Google Summer of Code 2015.<\/p>\n<h1 id=\"a-bit-about-myself\">A bit about myself<\/h1>\n<p>I&rsquo;m a Spanish student doing a master&rsquo;s in Computer Science in Barcelona. I graduated on Electrical Engineering (we call it Telecommunications here). I&rsquo;ve always been interested in computing and programming and I have worked on several projects on my own using C, python and go. My main interests in the field are programming languages, security, cryptography, distributed and decentralized systems and embedded systems.<\/p>"}]}}