Here s my (ninth) monthly update about the activities I ve done in the F/L/OSS world.
Debian
This was my 16th month of contributing to Debian.
I became a DM in late March last year and a DD last Christmas! \o/
This month was a little intense. I did a lot of different kinds of things in Debian this month. Whilst most of my time went on doing security stuff, I also sponsored a bunch of packages.
Here are the following things I did this month:
Uploads and bug fixes:
rails (2:5.2.4.3+dfsg-1) - fix a bunch of CVEs in Sid and Bullseye.
Sponsored ruby-ast for Abraham, libexif for Hugh, djangorestframework-gis and karlseguin-ccache for Nilesh, and twig-extensions, twig-i18n-extension, and mariadb-mysql-kbs for William.
GSoC Phase 1, Part 2!
Last month, I got selected as a Google Summer of Code student for Debian again! \o/
I am working on the Upstream-Downstream Cooperation in Ruby project.
The first half of the first month is blogged here, titled, GSoC Phase 1.
Also, I log daily updates at gsocwithutkarsh2102.tk.
Whilst the daily updates are available at the above site^, I ll breakdown the important parts of the later half of the first month here:
Spread the word/usage about this tool/library via adding them in the official RuboCop docs.
We had our third weekly meeting where we discussed the next steps and the things that are supposed to be done for the next set of cops.
Wrote more tests so as to cover different aspects of the GemspecGit cop.
Opened PR #4 for the next Cop, RequireRelativeToLib.
Introduced rubocop-packaging to the outer world and requested other upstream projects to use it! It is being used by 6 other projects already
Had our fourth weekly meeting where we pair-programmed (and I sucked :P) and figured out a way to make the second cop work.
Found a bug, reported at issue #5 and raised PR #6 to fix it.
And finally, people loved the library/tool (and it s outcome):
(for those who don t know, @bbatsov is the author of RuboCop, @lienvdsteen is an amazing fullstack engineer at GitLab, and @pboling is the author of some awesome Ruby tools and libraries!)
Continuation of GSoC for other Ruby related stuff!
Whilst I have already mentioned it multiple times but it s still not enough to stress how amazing Antonio Terceiro and David Rodr guez are!
They re more than just mentors to me!
Well, only they know how much I trouble them with different things, which are not only related to my GSoC project but also extends to the projects they maintain! :P
David maintains rubygems and bundler and Antonio maintains debci.
So on days when I decide to hack on rubygems or debci, only I know how kind and nice David and Anotonio are to me!
They very patiently walk me through with whatever I am stuck on, no matter what and no matter when.
Thus, with them around, I contributed to these two projects and more, with regards to working on rubocop-packaging.
Following are a few things that I raised:
Debian LTS
Debian Long Term Support (LTS) is a project to extend the lifetime of all Debian stable releases
to (at least) 5 years. Debian LTS is not handled by the Debian security team, but by a separate group
of volunteers and companies interested in making it a success.
This was my ninth month as a Debian LTS paid contributor. I was assigned 30.00 hours and worked on
the following things:
Uploaded a fix for CVE-2020-11082, for ruby-kaminari.
This upload was for Sid and Bullseye and this CVE was fixed in version 1.0.1-6.
Uploaded a fix for CVE-2020-10663, for ruby-json, ruby2.1, and ruby2.5.
These uploads were for Stretch and Buster and were fixed in the version 2.3.3-1+deb9u8, 2.1.0+dfsg-2+deb10u1, 2.3.3-1+deb9u8, and 2.5.5-3+deb10u2.
Other(s)
Sometimes it gets hard to categorize work/things into a particular category.
That s why I am writing all of those things inside this category.
This includes two sub-categories and they are as follows.
Personal:
This month I did the following things:
Wrote and published v0.1.0 of rubocop-packaging on RubyGems!
It s open-sourced and the repository is here.
Bug reports and pull requests are welcomed!
Integrated a tiny (yet a powerful) hack to align images in markdown for my blog.
Commit here.
Well, this time, my project is basically to write a linter (an extension to RuboCop).
This tool is mostly to help the Debian Ruby team.
And that is the best part, I love working in/for/with the Ruby team!
(I ve been an active part of the team for 18 months now :))
More details about the project can be found here, on the wiki.
And also, I have got the best mentors I could ve possibly asked for: Antonio Terceiro
and David Rodr guez
So, the program began on 1st June and I ve been working since then. I log my daily updates at
gsocwithutkarsh2102.tk.
Whilst the daily updates are available at the above site^, I ll breakdown the important
parts here:
During the first three days, I looked for a potential solution to the usage of
git ls-files in the gemspec files. This has been the most problematic thing for us.
Apart from the option of using Dir or Dir.glob, the best (closest) possible solution
(right now) is to use Rake::FileList which tries to respects the .gitignore file.
I stumbled upon this interesting gem, fast_ignore.
It is the exact thing which we want to use but unfortunately, to use it inside other
gemspec files, it should be vendored inside bundler s
code.
We had our first meeting on the
fourth day and we decided to hold meetings every Thursday for the next 12 weeks.
For the next five days, I learned more of Ruby and figured out what to do and how to do it.
If you d like to know what exactly I did in these 5 days, I d suggest you to read the daily
logs for those respective days.
During the next to two days, the first part of the project, the GemspecGit Cop, was
implemented.
This cop will correctly determine the usage of git in the gemspec files and would tell
the developers and the maintainers to replace them with pure Ruby alternatives with giving
them a proper reason to do so. Much thanks to Dana for her
help she took out time to pair-program with me!
We had our second weekly meeting
where I finally told Antonio and David that the first part is already done (\o/) and we
discussed some things and even pair-programmed :D
I took the weekend off (and something terrible happened) but anyways, I managed to get
together some time and energy to document the source code and raised this
PR #2.
And here I am on the 15th day :)
It has been a lot of fun so far! Though I am little worried on how to implement the next part
of the project as I am not sure how to check only a particalar directory for some relative
require calls.
But I think, that s okay, somehow, something will work out. And I can always ask around
others and check other cops to see how it s done! \( )/
Until next time. :wq for today.
Here s my (eighth) monthly update about the activities I ve done in the F/L/OSS world.
Debian
This month marks my 15 months of contributing to Debian.
And 6th month as a DD! \o/
Whilst I love doing Debian stuff, I have started spending more time on the programming
side now. And I hope to keep it this for some time now.
Of course, I ll keep doing the Debian stuff, but just lesser in amount.
Anyway, the following are the things I did in May.
Experimenting and improving Ruby libraries FTW!
I have been very heavily involved with the Debian Ruby team for over an year now.
Thanks to Antonio Terceiro (and GSoC), I ve started experimenting and taking more
interest in upstream development and improvement of these libraries.
This has the sole purpose of learning. It has gotten fun since I ve started doing Ruby.
And I hope it stays this way.
This month, I opened some issues and proposed a few pull requests. They are:
Issue #802 against whenever for Ruby2.7 test failures.
Issue #8 against aggregate asking upstream for a release on rubygems.
Issue #104 against irb for asking more about Array.join("\n").
Issue #1391 against mail asking upstream to cut a new release.
Issue #1655 against rack reporting test failures in the CVE fix.
Debian LTS
Debian Long Term Support (LTS) is a project to extend the lifetime of all Debian stable releases
to (at least) 5 years. Debian LTS is not handled by the Debian security team, but by a separate group
of volunteers and companies interested in making it a success.
This was my eighth month as a Debian LTS paid contributor. I was assigned 17.25 hours and worked on
the following things:
CVE Fixes and Announcements:
Issued DLA 2191-1, fixing CVE-2020-10683, for dom4j.
For Debian 8 Jessie , this problem has been fixed in version 1.6.1+dfsg.3-2+deb8u2.
Issued DLA 2192-1, fixing CVE-2020-10663, for ruby2.1.
For Debian 8 Jessie , this problem has been fixed in version 2.1.5-2+deb8u10.
Issued DLA 2210-1, fixing CVE-2020-3810, for apt.
This update was prepared by the maintainer, Julian. I just took care of the paperwork.
For Debian 8 Jessie , this problem has been fixed in version 1.0.9.8.6.
Other(s)
Sometimes it gets hard to categorize work/things into a particular category.
That s why I am writing all of those things inside this category.
This includes two sub-categories and they are as follows.
Personal:
This month I could get the following things done:
Wrote and published my first Ruby gem/library/tool on RubyGems!
It s open-sourced and the repository is here.
Bug reports and pull requests are welcomed!
Wrote a small Ruby script (available here) to install Ruby gems from Gemfile(.lock).
Needed this when I hit a bug while using ruby-standalone, which Antonio fixed pretty quickly!
As a technologist, I've been wondering how I can help people with the
rapidly spreading coronavirus pandemic. With the world entering
the "exponential stage" (e.g. Canada, the USA and basically
all of Europe), everyone should take precautions and limit
practice Social Distancing (and not dumbfuckery). But this
doesn't mean we should dig ourselves in a hole in our basement: we can
still talk to each other on the internet, and there are great, and
free, tools available to do this. As part of my work as a sysadmin,
I've had to answer questions about this a few times and I figured it
was useful to share this more publicly.
Just say hi using whatever
First off, feel free to use the normal tools you normally use:
Signal, Facetime, Skype, Zoom, and Discord can
be fine to connect with your folks, and since it doesn't take much to
make someone's day please do use those tools to call your close
ones and say "hi". People, especially your older folks, will feel
alone and maybe scared in those crazy times. Every little bit you can
do will help, even if it's just a normal phone call, an impromptu
balcony fanfare, a remote workout class, or just a
sing-along from your balcony, anything goes.
But if those tools don't work well for some reason, or you want to try
something new, or someone doesn't have an iPad, or it's too dang cold
to go on your balcony, you should know there are other alternatives
that you can use.
Jitsi
We've been suggesting our folks use a tool called "Jitsi". Jitsi
is a free software platform to host audio/video conferences. It has a
web app which means anyone with a web browser can join a session. It
can also do "screen sharing" if you need to work together on a
project.
There are many "instances", but here's a subset I know about:
You can connect to those with your web browser directly. If your web
browser doesn't work, try switching to another (e.g. if Firefox
doesn't work, try Chrome and vice-versa). There are also apps for
desktop and mobile apps (F-Droid, Google Play, Apple
Store) that will work better than just using your browser.
Jitsi should scale for small meetings up to a dozen people.
Mumble
... but beyond that, you might have trouble doing a full
video-conference with a lot of people anyways. If you need to have a
large conference with a lot of people, or if you have bandwidth and
reliability problems with Jitsi, you can also try Mumble.
Mumble is an audio-only conferencing service, similar to Discord or
Teamspeak, but made with free software. It requires users to install
an app but there are clients for every platform out there
(F-Droid, Google Play, Apple Store). Mumble is harder
to setup, but is much more efficient in terms of bandwidth and
latency. In other words, it will just scale and sound better.
Mumble ships with a list of known servers, but you can also connect to
those trusted ones:
mumble.riseup.net - Riseup, an autonomous collective, hosted in Seattle
(ask me if you need their password) not a public service
talk.systemli.org - systemli, a
left-wing network and technics-collective, hosted in Berlin
Live streaming
If for some reason those tools still don't scale, you might have a
bigger problem on your hands. If your audience is over 100 people, you
will not be able to all join in the same conference together. And
besides, maybe you just want to broadcast some news and do not need
audio or video feedback from the audience. In this case, you need
"live streaming".
Here, proprietary services are Twitch, Livestream.com and Youtube. But
the community also provides alternatives to those. This is more
complicated to setup, but just to get you started, I'll link to:
For either of those tools, you need an app on your desktop. The
Mayfirst instructions use OBS Studio for this, but it might
be possible to hotwire VLC to stream video from your computer as
well.
Text chat
When all else fails, text should go through. Slack, Twitter and
Facebook are the best known alternatives here, obviously. I would warn
against spending too much time on those, as they can foment harmful
rumors and can spread bullshit like a virus on any given day. The
situation does not make that any better. But it can be a good way to
keep in touch with your loved ones.
But if you want to have a large meetings with a crazy number of
people, text can actually accomplish wonders. Internet Relay Chat
also known as "IRC" (and which oldies might have experienced for a bit
as mIRC) is, incredibly, still alive at the venerable age of 30
years old. It is mainly used by free software projects, but can be
used by anyone. Here are some networks you can try:
Those are all web interface to the IRC networks, but there are also a
plenitude of IRC apps you can install on your desktop if you want the
full experience.
Whiteboards and screensharing
I decided to add this section later on because it's a frequently
mentioned "oh but you forgot..." comment I get from this post.
Big Blue Button - seems to check all the boxes: free software,
VoIP integration, whiteboarding and screen sharing, works from a
web browser
CodiMD: collaborative text editor with UML and diagrams support
Excalidraw: (collaborative) whiteboard tool that lets you
easily sketch diagrams that have a hand-drawn feel
I'll also mention that collaborative editors, in general, like
Etherpad are just great for taking minutes because you don't have
that single person with the load of writing down what people are
saying and is too busy to talk. Google Docs and Nextcloud have similar
functionality, of course.
Update, public Big Blue Button instances:
BBB requires one user to register to start the conference, but once
that's done, anyone with the secret URL can join.
Common recommendations
Regardless of the tools you pick, audio and video streaming is a
technical challenge. A lot of things happen under the hood when
you pick up your phone and dial a number, and sometimes using a
desktop, it can be difficult to get everything "just right".
Some advice:
get a good microphone and headset: good audio really makes a
difference in how pleasing the experience will be, both for you
and your peers. good hardware will reduce echo, feedback and other
audio problems. (see also my audio docs)
check your audio/video setup before joining the meeting, ideally
with another participant on the same platform you will use
find a quiet place to meet: even a good microphone will pick up
noises from the environment, if you reduce this up front,
everything will sound better. if you do live streaming and want
high quality recording, considering setting up a smaller room to
do recording. (tip: i heard of at least one journalist hiding in a
closer full of clothes to make recordings, as it dampens the
sound!)
mute your microphone when you are not speaking (spacebar
in Jitsi, follow the "audio wizard" in Mumble)
If you have questions or need help, feel free to ask! Comment on this
blog or just drop me an email (see contact), I'd be happy to
answer your questions.
Other ideas
Inevitably, when I write a post like this, someone writes
something like "I can't believe you did not mention APL!" Here's a
list of tools I have not mentioned here, deliberately or because I
forgot:
Nextcloud Talk - needs access to a special server, but can be
used for small meetings (less than 5, or so i heard)
Jabber/XMPP - yes, I know, XMPP can do everything and
it's magic. but I've given up a while back, and I don't think
setting up audio conferences with multiple enough is easy enough to
make the cut here
Signal - signal is great. i use it every day. it's the primary
way I do long distance, international voice calls for free, and the
only way I do video-conferencing with family and friends at
all. but it's one to one only, and the group (text) chat kind of
sucks
Also, all the tools I recommend above are made of free software, which
means they can be self-hosted. If things go bad and all those services
stop existing, it should be possible for you to run your own
instance.
Let me know if I forgot anything, but in a friendly way. And stay safe
out there.
Update: a similar article from the good folks at systemli also
recommends Mastodon, Ticker, Wikis and Etherpad.
Update 2: same, at SFC, which also mentions Firefox Send
and Etherpad (and now I wish I did).
First day of the videoteam autumn sprint! Well, I say first day, but
in reality it's more day 0. Even though most of us have arrived in Cambridge
already, we are still missing a few people.
Last year we decided to sprint in Paris because most of our video gear
is stocked there. This year, we instead chose to sprint a few days before the
Cambridge Mini-Debconf to help record the conference afterwards.
Since some of us arrived very late and the ones who did arrive early are still
mostly jet lagged (that includes me), I'll use this post to introduce the space
we'll be working from this week and our general plan for the sprint.
House Party
After some deliberations, we decided to rent a house for a week in Cambridge:
finding a work space to accommodate us and all our gear proved difficult and we
decided mixing accommodation and work would be a good idea.
I've only been here for a few hours, but I have to say I'm pretty impressed by
the airbnb we got. Last time I checked (it seems every time I do, some new room
magically appears), I counted 5 bedrooms, 6 beds, 5 toilets and 3 shower rooms.
Heck, there's even a solarium and a training room with weights and a punching
bag on the first floor.
Having a whole house to ourselves also means we have access to a functional
kitchen. I'd really like to cook at least a few meals during the week.
There's also a cat!
It's not the house's cat per say, but it's been hanging out around the house
for most of the day and makes cute faces trying to convince us to let it come
inside. Nice try cat. Nice try.
Here are some glamour professional photos of what the place looks like on a
perfect summer day, just for the kick of it:
Of course, reality has trouble matching all the post-processing filters.
Plan for the week
Now on a more serious note; apart from enjoying the beautiful city of Cambridge,
here's what the team plans to do this week:
tumbleweed
Stefano wants to continue refactoring our ansible setup. A lot of things have
been added in the last year, but some of it are hacks we should remove and
implement correctly.
highvoltage
Jonathan won't be able to come to Cambridge, but plans to work remotely, mainly
on our desktop/xfce session implementation. Another pile of hacks waiting to be
cleaned!
ivodd
Ivo has been working a lot of the pre-ansible part of our installation and plans
to continue working on that. At the moment, creating an installation USB key is
pretty complicated and he wants to make that simpler.
olasd
Nicolas completely reimplemented our streaming setup for DC17 and wants to
continue working on that.
More specifically, he wants to write scripts to automatically setup and teardown
- via API calls - the distributed streaming network we now use.
Finding a way to push TLS certificates to those mirrors, adding a live stream
viewer on video.debconf.org and adding a viewer to our archive are also
things he wants to look at.
pollo
For my part, I plan to catch up with all the commits in our ansible repository I
missed since last year's sprint and work on documentation.
It would be very nice if we could have a static website describing our work so
that others (at mini-debconfs for examples) could replicate it easily.
If I have time, I'll also try to document all the ansible roles we have written.
Stay tuned for more daily reports!
After too much time lying to myself, telling myself things like "I'll just add
this neat feature I want on my blog next week", I've finally made the big jump,
ditched django and migrated my website to Pelican.
I'm going to the Cambridge Mini-Debconf at the end of the month for
the Debconf Videoteam Autumn sprint and I've taken the task of making
daily sprint reports for the team. That in return means I have to publish my
blog on Planet Debian. My old website not having
feeds made this a little hard and this perfect storm gave me the energy to make
the migration happen.
Anyway, django was fun. Building a (crappy) custom blogging engine with it
taught me some rough basics, but honestly I don't know why I ever thought it was
a good idea.
Don't get me wrong: django is great and should
definitely be used for large and complicated websites. My blog just ain't one.
Migrating to Pelican was pretty easy since it also uses Jinja2 templates and
generates content from Mardown. The hardest part was actually bending it to
replicate the weird and specific behavior I wanted it to have.
So yeah, woooo, I migrated to Pelican. Who cares, right? Well, if you are
amongst the very, very few people who read the blog posts I mainly write for
myself, you'll be please to know that:
One of the reasons which made me switch my old 17" BenQ monitor for a Dell U2413 three years ago was it had an integrated SD card reader. I find very convenient to take camera's card out, plug the card into the monitor and click on KDE device monitor's option Open with digiKam to download the photos or videos.
But last week, when trying to reconnect the USB cable to the new board just didn't work and the kernel log messages were not very hopeful:
[190231.770349] usb 2-2.3.3: new SuperSpeed USB device number 15 using xhci_hcd
[190231.890439] usb 2-2.3.3: New USB device found, idVendor=0bda, idProduct=0307
[190231.890444] usb 2-2.3.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[190231.890446] usb 2-2.3.3: Product: USB3.0 Card Reader
[190231.890449] usb 2-2.3.3: Manufacturer: Realtek
[190231.890451] usb 2-2.3.3: SerialNumber: F141000037E1
[190231.896592] usb-storage 2-2.3.3:1.0: USB Mass Storage device detected
[190231.896764] scsi host8: usb-storage 2-2.3.3:1.0
[190232.931861] scsi 8:0:0:0: Direct-Access Generic- SD/MMC/MS/MSPRO 1.00 PQ: 0 ANSI: 6
[190232.933902] sd 8:0:0:0: Attached scsi generic sg5 type 0
[190232.937989] sd 8:0:0:0: [sde] Attached SCSI removable disk
[190243.069680] hub 2-2.3:1.0: hub_ext_port_status failed (err = -71)
[190243.070037] usb 2-2.3-port3: cannot reset (err = -71)
[190243.070410] usb 2-2.3-port3: cannot reset (err = -71)
[190243.070660] usb 2-2.3-port3: cannot reset (err = -71)
[190243.071035] usb 2-2.3-port3: cannot reset (err = -71)
[190243.071409] usb 2-2.3-port3: cannot reset (err = -71)
[190243.071413] usb 2-2.3-port3: Cannot enable. Maybe the USB cable is bad?
...
I was sure USB 3.0 ports were working, because I've already used them with a USB 3.0 drive, so first thought was the monitor USB hub had failed. It seemed unlikely that a cable which has not been moved in 3 years was suddenly failing, is that even possible?
But a few moments later the same cable plugged into a USB 2.0 worked flawlessly and all photos could be downloaded, just noticeably slower.
A bit confused, and thinking that, since everything else was working maybe the cable had to be replaced, it happened I upgraded the system in the meantime. And luck came into rescue, because now it works again in 4.9.30-2+deb9u5 kernel. Looking at the package changelog it seems the fix was this usb:xhci:Fix regression when ATI chipsets detected . So, not a bad cable but a little kernel bug ;-)
Thanks to all involved, specially Ben for the package update!
A new and much enhanced version of RcppMsgPack arrived on CRAN a couple of days ago. It came together following this email to the r-package-devel list which made it apparent that Travers Ching had been working on MessagePack converters for R which required the very headers I had for use from, inter alia, the RcppRedis package.
So we joined our packages. I updated the headers in RcppMsgPack to the current upstream version 2.1.5 of MessagePack, and Travers added his helper functions allow direct packing / unpacking of MessagePack objects at the R level, as well as tests and a draft vignette. Very exciting, and great to have a coauthor!
So now RcppMspPack provides R with both MessagePack header files for use via C++ (or C, if you must) packages such as RcppRedis --- and direct conversion routines at the R prompt.
MessagePack itself is an efficient binary serialization format. It lets you exchange data among multiple languages like JSON. But it is faster and smaller. Small integers are encoded into a single byte, and typical short strings require only one extra byte in addition to the strings themselves.
Welcome to gambaru.de. Here is my monthly report that covers what I have been doing for Debian. If you re interested in Java, Games and LTS topics, this might be interesting for you.
Debian Games
The bug fix (#866378) for 3dchess also landed in Stretch and Jessie.
I sponsored Lugaru for Vincent Prat and Martin Erik Werner, a really cool 3D fighting game featuring a rabbit. The game is dfsg-free now and will replace openlugaru.
I uploaded a new revision of clanlib and teg fixing Perl transition bugs. The patches were provided by gregor herrmann. I added myself to Uploaders in case of teg because the package was missing a human maintainer.
I adopted trackballs after I discovered #868983 where Henrique de Moraes Holschuh called attention to a new fork of Trackballs. The current version was broken and unplayable and it was only a matter of time before the game was removed from Debian. I could fix a couple of bugs, forwarded some issues upstream and I believe a nice game was saved.
I uploaded Bullet 2.86.1 to unstable and completed another Bullet transition.
Debian Java
Almost all PDFsam dependencies were accepted into the archive this month. I had to update some of them and removed patches that were needed for the initial bootstrapping. I also uploaded libmetadata-extractor-java to unstable. Now only fontawesomefx is missing to complete the PDFsam update.
Debian LTS
This was my seventeenth month as a paid contributor and I have been paid to work 23,5 hours on Debian LTS, a project started by Rapha l Hertzog. In that time I did the following:
From 24. July until 31. July I was in charge of our LTS frontdesk. I triaged bugs in tinyproxy, varnish, freerdp, ghostscript, gcc-4.6, gcc-4.7, fontforge, teamspeak-server, teamspeak-client, qpdf, nvidia-graphics-drivers and sipcrack. I also pinged Diego Biurrun for more information about the next libav update and replied to questions on the debian-lts mailing list and LTS IRC channel.
DLA 1034-1. Issued a security update for php5 fixing 5 CVE. I discussed CVE-2017-11362 with the security team. We came to the conclusion that it was no security issue but just a normal bug.
DLA 1036-1. Issued a security update for gsoap fixing 1 CVE.
DLA 1037-1. Issued a security update for catdoc fixing 1 CVE.
DLA 613-2. Issued a regression update for roundcube.
DLA 1045-1. Issued a security update for graphicsmagick fixing 10 CVE.
DLA 1047-1. Issued a security update for supervisor fixing 1 CVE.
DLA-1048-1. Issued a security update for ghostscript fixing 8 CVE.
Non-maintainer upload
I uploaded the security fix for spice to unstable which was already fixed in Stretch and earlier versions.
A new package! Or at least new on CRAN as the very initial version 0.1.0 had been available via the ghrr drat for over a year. But now we have version 0.1.1 to announce as a CRAN package.
RcppMspPack provides R with MessagePack header files for use via C++ (or C, if you must) packages such as RcppRedis.
MessagePack itself is an efficient binary serialization format. It lets you exchange data among multiple languages like JSON. But it is faster and smaller. Small integers are encoded into a single byte, and typical short strings require only one extra byte in addition to the strings themselves.
MessagePack is used by Redis and many other projects, and has bindings to just about any language.
To use this package, simply add it to the LinkingTo: field in the DESCRIPTION field of your R package---and the R package infrastructure tools will then know how to set include flags correctly on all architectures supported by R.
More information may be on the RcppMsgPack page. Issues and bugreports should go to the GitHub issue tracker.
Here's what happened in the Reproducible Builds effort between Sunday April 30 and Saturday May 6 2017:
Past and upcoming events
Between May 5th-7th the Reproducible Builds Hackathon
2017 took
place in Hamburg, Germany.
On May 6th Mattia Rizzolo gave a talk on Reproducible Builds at
DUCC-IT 17 in Vicenza, Italy.
On May 13th Chris Lamb will give a talk on Reproducible Builds at OSCAL 2017 in Tirana, Albania.
Media coverage
Ximin updated his R patch to fix a few FTBFS and now we have 463/478 reproducible R packages. For more details, see his detailed write-up on this blog.
Holger rebuilt dpkg, gcc-6 and r-base for our experimental toolchain for unstable on arm64, i386 and armhf.
Packages reviewed and fixed, and bugs filed
Chris Lamb:
Reviews of unreproducible packages
93 package reviews have been added, 12 have been updated and 98 have been removed in this week,
adding to our knowledge about identified issues.
The following issues have been added:
This week's edition was written by Chris Lamb, Holger Levsen and Ximin Luo & reviewed by a bunch of Reproducible Builds folks on IRC & the mailing lists.
Here is my monthly update covering what I have been doing in the free software world (previous month):
I was elected Debian Project Leader for 2017. I'd like to sincerely thank everyone who voted for me as well as everyone who took part in the election in general especially Mehdi Dogguy for being a worthy opponent. The result was covered on LWN, Phoronix, DistroWatch, iTWire, etc.
Added support for the Monzo banking API in social-core, a Python library to allow web applications to authenticate using third-parties. (#68)
Updated systemd's documentation to explain why we suggest explicitly calling make all despite the Makefile's "check" target calling it. (#5830)
Updated the documentation of a breadth-first version of find(1) called bfs to refer to the newly-uploaded Debian package. (#23)
Updated the configuration for the ticketbot IRC bot (zwiebelbot on OFTC) to identify #reproducible-builds as a Debian-related channel. This is so that bug Debian bug numbers are automatically expanded by the bot. (#7)
Reproducible builds
Whilst anyone can inspect the source code of free software for malicious flaws, most software is distributed pre-compiled to end users.
The motivation behind the Reproducible Builds effort is to permit verification that no flaws have been introduced either maliciously or accidentally during this compilation process by promising identical results are always generated from a given source, thus allowing multiple third-parties to come to a consensus on whether a build was compromised.
I have generously been awarded a grant from the Core Infrastructure Initiative to fund my work in this area.
This month I:
Presented at foss-north.se 2017 in Gothenburg, Sweden on Reproducible Builds.
Sent a patch for poti a library to generate paje traces to ensure the build is reproducible when Git is not available. (#7)
Submitted a pull request to patat (a tool to make terminal-based presentations using Pandoc) to make the build reproducible. (#36)
Fixed miniupnp's build system to make the build reproducible. (#237)
Updated sunpinyin, a "statistical model" based Chinese input method, to make the .pc file output reproducible. (#73)
taskflow (an OpenStack library) to ensure the generated documentation is reproducible. (#4)
Issued DLA 882-1 for the tryton-server general application platform to fix a path suffix injection attack.
Issued DLA 883-1 for curl preventing a buffer read overrun vulnerability.
Issued DLA 884-1 for collectd (a statistics collection daemon) to close a potential infinite loop vulnerability.
Issued DLA 885-1 for the python-django web development framework patching two open redirect & XSS attack issues.
Issued DLA 890-1 for ming, a library to create Flash files, closing multiple heap-based buffer overflows.
Issued DLA 892-1 and DLA 891-1 for the libnl3/libnl Netlink protocol libraries, fixing integer overflow issues which could have allowed arbitrary code execution.
Here's what happened in the Reproducible
Builds effort between Sunday April 9 and
Saturday April 15 2017:
Upcoming events
On April 26th Chris Lamb will give a talk at foss-north
2017 in Gothenburg, Sweden on Reproducible Builds.
Media coverage
Jake Edge wrote a
summary of Vagrant
Cascadian's talk on Reproducible Builds at LibrePlanet.
Toolchain development and fixes
Ximin Luo forwarded patches to
GCC for
BUILD_PATH_PREFIX_MAP support.
With this patch to backported to GCC-6, as well as a patched dpkg to set the
environment variable, he scheduled ~3,300 packages that are unreproducible in
unstable-amd64 but reproducible in testing-amd64 - because we vary the build
path in the former but not latter case. Our infrastructure ran these in just
under 3 days, and we reproduced ~1,700 extra packages.
This is about 6.5% of ~26,100 Debian source
packages,
and about 1/2 of the ones whose irreproducibility is due to build-path issues.
Most of the rest are not related to GCC, such as things built by R, OCaml,
Erlang, LLVM, PDF IDs, etc.
(The dip afterwards, in the graph linked above, is due to reverting back to an
unpatched GCC-6, but we'll be rebasing the patch continually over the next few
weeks so the graph should stay up.)
Packages reviewed and fixed, and bugs filed
Chris Lamb:
Reviews of unreproducible packages
38 package reviews have been added, 111 have been updated and 85 have been
removed in this week, adding to our knowledge about identified
issues.
6 issue types have been updated:
Added:
records_build_flags, captures_build_path: we temporarily
consider these non-deterministic, to better track the issue - the patches are
still pending and statuses will keep changing as we upload patched packages.
compiler version need to be identical and recorded
build options and their order needs to be identical and recorder
build path needs to be identical and recorded
(otherwise debug symbols - and BuildIDs - change)
diffoscope helps checking for differences in build output
We stopped when compiling a PE .exe produced a varying output.
It turns out that PE carries a build date timestamp.
The spec says that bound DLLs timestamps are refered to in the "Delay-Load Directory Table". Maybe that's also the date Windows displays when a system-wide DLL is about to be replaced, too.
Build timestamps looks unused in .exe files though.
Anyway, Stephen Kitt pointed out (thanks!) that Debian's MinGW linker binutils-mingw-w64 has an upstream-pending patch that sets the timestamp to SOURCE_DATE_EPOCH if set.
Alternatively, one can pass -Wl,--no-insert-timestamp to set it to 0 (though see caveats below):
$ cd/usr/srx/mxe
$ make sdl2
$ md5sum usr/i686-w64-mingw32.static/lib/libSDL2.a /tmp/libSDL2.a
c6c368323927e2ae7adab7ee2a7223e9 usr/i686-w64-mingw32.static/lib/libSDL2.a
68909ab13181b1283bd1970a56d41482 /tmp/libSDL2.a
$ ls-l ./usr/i686-w64-mingw32.static/lib/libSDL2.a /tmp/libSDL2.a
-rw-r--r-- 1 me me 5861536 mars 23 21:04/tmp/libSDL2.a
-rw-r--r-- 1 me me 5862488 mars 25 19:46 ./usr/i686-w64-mingw32.static/lib/libSDL2.a
Well that was expected.
But what about the filesystem order?
With such an automated build, could potential variations in the order of files go undetected?
Would the output be different on another filesystem format (ext4 vs. btrfs...)?
It was a good opportunity to test the disorderfs fuse-based tool.
And while I'm at it, check if reprotest is easy enough to use (the manpage is scary).
Let's redo our basic tests with it - basic usage is actually very simple:
$ apt-get install reprotest disorderfs faketime
$ reprotest 'make hello''hello'
...
will vary: environment
will vary: fileordering
will vary: home
will vary: kernel
will vary: locales
will vary: exec_path
will vary:time
will vary: timezone
will vary:umask
...
--- /tmp/tmpk5uipdle/control_artifact/+++ /tmp/tmpk5uipdle/experiment_artifact/--- /tmp/tmpk5uipdle/control_artifact/hello
+++ /tmp/tmpk5uipdle/experiment_artifact/hello
stat
@@ -1,8+1,8 @@
Size:8632 Blocks:24 IO Block:4096 regular file
Links:1-Access: (0755/-rwxr-xr-x) Uid: (1000/ me) Gid: (1000/ me)+Access: (0775/-rwxrwxr-x) Uid: (1000/ me) Gid: (1000/ me)
Modify:1970-01-01 00:00:00.000000000+0000
Birth: -# => OK except for permissions
$ reprotest 'make hello && chmod 755 hello''hello'=======================
Reproduction successful
=======================
No differences in hello
c8f63b73265e69ab3b9d44dcee0ef1d2815cdf71df3c59635a2770e21cf462ec hello
$ reprotest 'make hello CFLAGS="-g -O2"''hello'# => lots of differences, as expected
Now let's apply to the MXE build.
We keep the same build path, and also avoid using linux32 (because MXE would then recompile all the host compiler tools for 32-bit):
$ reprotest --dont-vary build_path,kernel 'touch src/sdl2.mk && make sdl2 && cp -a usr/i686-w64-mingw32.static/lib/libSDL2.a .''libSDL2.a'=======================
Reproduction successful
=======================
No differences in libSDL2.a
d9a39785fbeee5a3ac278be489ac7bf3b99b5f1f7f3e27ebf3f8c60fe25086b5 libSDL2.a
That checks!
What about a full MXE environment?
$ reprotest --dont-vary build_path,kernel 'make clean && make sdl2 sdl2_gfx sdl2_image sdl2_mixer sdl2_ttf libzip gettext nsis''usr'# => changes in installation dates# => timestamps in .exe files (dbus, ...)# => libicu doesn't look reproducible (derb.exe, genbrk.exe, genccode.exe...)# => apparently ar timestamp variations in libaclui
Most libraries look reproducible enough. ar differences may go away at FreeDink link time since I'm aiming at a static build.
Let's try!
First let's see how FreeDink behaves with stable dependencies.
We can compile with -Wl,--no-insert-timestamp and strip the binaries in a first step.
There are various issues (timestamps, permissions) but first let's check the executables themselves:
Gah...
AFAIU there is something random in the linking phase, and sometimes the timestamp is removed, sometimes it's not.
Not very easy to track but I believe I reproduced it with the "hello" example:
# With MXE:
$ reprotest 'i686-w64-mingw32.static-gcc hello.c -I /opt/mxe/usr/i686-w64-mingw32.static/include -I/opt/mxe/usr/i686-w64-mingw32.static/include/SDL2 -L/opt/mxe/usr/i686-w64-mingw32.static/lib -lmingw32 -Dmain=SDL_main -lSDL2main -lSDL2 -lSDL2main -Wl,--no-insert-timestamp -luser32 -lgdi32 -lwinmm -limm32 -lole32 -loleaut32 -lshell32 -lversion -o hello && chmod 700 hello''hello'# => different# => maybe because it imports the build timestamp from -lSDL2main# With Debian's MinGW (but without SOURCE_DATE_EPOCH):
$ reprotest 'i686-w64-mingw32-gcc hello.c -I /opt/mxe/usr/i686-w64-mingw32.static/include -I/opt/mxe/usr/i686-w64-mingw32.static/include/SDL2 -L/opt/mxe/usr/i686-w64-mingw32.static/lib -lmingw32 -Dmain=SDL_main -lSDL2main -lSDL2 -lSDL2main -Wl,--no-insert-timestamp -luser32 -lgdi32 -lwinmm -limm32 -lole32 -loleaut32 -lshell32 -lversion -o hello && chmod 700 hello''hello'=======================
Reproduction successful
=======================
No differences in hello
0b2d99dc51e2ad68ad040d90405ed953a006c6e58599beb304f0c2164c7b83a2 hello
# Let's remove -Dmain=SDL_main and let our main() have precedence over the one in -lSDL2main:
$ reprotest 'i686-w64-mingw32.static-gcc hello.c -I /opt/mxe/usr/i686-w64-mingw32.static/include -I/opt/mxe/usr/i686-w64-mingw32.static/include/SDL2 -L/opt/mxe/usr/i686-w64-mingw32.static/lib -lmingw32 -lSDL2main -lSDL2 -lSDL2main -Wl,--no-insert-timestamp -luser32 -lgdi32 -lwinmm -limm32 -lole32 -loleaut32 -lshell32 -lversion -o hello && chmod 700 hello''hello'=======================
Reproduction successful
=======================
No differences in hello
6c05f75eec1904d58be222cc83055d078b4c3be8b7f185c7d3a08b9a83a2ef8d hello
$ LANG=C i686-w64-mingw32.static-ld --version # MXE
GNU ld (GNU Binutils)2.25.1
Copyright (C)2014 Free Software Foundation, Inc.
$ LANG=C i686-w64-mingw32-ld --version # Debian
GNU ld (GNU Binutils)2.27.90.20161231
Copyright (C)2016 Free Software Foundation, Inc.
It looks like there is a random behavior in binutils 2.25, coupled with SDL2's wrapping of my main().
So FreeDink is nearly reproducible, except for this build timestamp issue that pops up in all kind of situations.
In the worse case I can zero it out, or patch MXE's binutils until they upgrade.
More importantly, what if I recompile FreeDink and the dependencies twice?
Yay!
I could not reproduce the build timestamp issue in the stripped binaries, though it was still varying in the unstripped src/freedinkedit.exe.
I mentioned there was other changes noticed by diffoscope.
Changes in file timestamps.
That one is interesting.
Could be ignored, but we want to generate an identical binary package/archive too, right?
That's where archive meta-data matters. make INSTALL="$(which install) install -p" could help for static files, but not generated ones.
The doc suggests clamping all files to SOURCE_DATE_EPOCH - i.e. all generated files will have their date set at that timestamp:
Caused by varying umask.
I attempted to mitigate the issue by playing with make install MKDIR_P="mkdir -p -m 755"(1).
However even mkdir -p -m ... does not set permissions for intermediate directories.
Maybe it's better to set and record the umask...
So, aside from minor issues such as BuildIDs and build timestamps, the toolchain is pretty stable as of now.
The issue is more about fixing and recording the build environment.
Which is probably the next challenge
As some of the world knows full well by now, I've been noodling with Go
for a few years, working through its pros, its cons, and thinking a lot
about how humans use code to express thoughts and ideas. Go's got a lot of
neat use cases, suited to particular problems, and used in the right place,
you can see some clear massive wins.
I've started writing Debian tooling in Go, because it's a pretty natural fit.
Go's fairly tight, and overhead shouldn't be taken up by your operating system.
After a while, I wound up hitting the usual blockers, and started to build up
abstractions. They became pretty darn useful, so, this blog post is announcing
(a still incomplete, year old and perhaps API changing) Debian package for Go.
The Go importable name is pault.ag/go/debian. This contains a lot of utilities
for dealing with Debian packages, and will become an edited down "toolbelt"
for working with or on Debian packages.
Module Overview
Currently, the package contains 4 major sub packages. They're a changelog
parser, a control file parser, deb file format parser, dependency parser
and a version parser. Together, these are a set of powerful building blocks
which can be used together to create higher order systems with reliable
understandings of the world.
changelog
The first (and perhaps most incomplete and least tested) is a changelog file
parser.. This provides the
programmer with the ability to pull out the suite being targeted in the
changelog, when each upload was, and the version for each. For example, let's
look at how we can pull when all the uploads of Docker to sid took place:
funcmain()resp,err:=http.Get("http://metadata.ftp-master.debian.org/changelogs/main/d/docker.io/unstable_changelog")iferr!=nilpanic(err)allEntries,err:=changelog.Parse(resp.Body)iferr!=nilpanic(err)for_,entry:=rangeallEntriesfmt.Printf("Version %s was uploaded on %s\n",entry.Version,entry.When)
The output of which looks like:
Version 1.8.3~ds1-2 was uploaded on 2015-11-04 00:09:02 -0800 -0800
Version 1.8.3~ds1-1 was uploaded on 2015-10-29 19:40:51 -0700 -0700
Version 1.8.2~ds1-2 was uploaded on 2015-10-29 07:23:10 -0700 -0700
Version 1.8.2~ds1-1 was uploaded on 2015-10-28 14:21:00 -0700 -0700
Version 1.7.1~dfsg1-1 was uploaded on 2015-08-26 10:13:48 -0700 -0700
Version 1.6.2~dfsg1-2 was uploaded on 2015-07-01 07:45:19 -0600 -0600
Version 1.6.2~dfsg1-1 was uploaded on 2015-05-21 00:47:43 -0600 -0600
Version 1.6.1+dfsg1-2 was uploaded on 2015-05-10 13:02:54 -0400 EDT
Version 1.6.1+dfsg1-1 was uploaded on 2015-05-08 17:57:10 -0600 -0600
Version 1.6.0+dfsg1-1 was uploaded on 2015-05-05 15:10:49 -0600 -0600
Version 1.6.0+dfsg1-1~exp1 was uploaded on 2015-04-16 18:00:21 -0600 -0600
Version 1.6.0~rc7~dfsg1-1~exp1 was uploaded on 2015-04-15 19:35:46 -0600 -0600
Version 1.6.0~rc4~dfsg1-1 was uploaded on 2015-04-06 17:11:33 -0600 -0600
Version 1.5.0~dfsg1-1 was uploaded on 2015-03-10 22:58:49 -0600 -0600
Version 1.3.3~dfsg1-2 was uploaded on 2015-01-03 00:11:47 -0700 -0700
Version 1.3.3~dfsg1-1 was uploaded on 2014-12-18 21:54:12 -0700 -0700
Version 1.3.2~dfsg1-1 was uploaded on 2014-11-24 19:14:28 -0500 EST
Version 1.3.1~dfsg1-2 was uploaded on 2014-11-07 13:11:34 -0700 -0700
Version 1.3.1~dfsg1-1 was uploaded on 2014-11-03 08:26:29 -0700 -0700
Version 1.3.0~dfsg1-1 was uploaded on 2014-10-17 00:56:07 -0600 -0600
Version 1.2.0~dfsg1-2 was uploaded on 2014-10-09 00:08:11 +0000 +0000
Version 1.2.0~dfsg1-1 was uploaded on 2014-09-13 11:43:17 -0600 -0600
Version 1.0.0~dfsg1-1 was uploaded on 2014-06-13 21:04:53 -0400 EDT
Version 0.11.1~dfsg1-1 was uploaded on 2014-05-09 17:30:45 -0400 EDT
Version 0.9.1~dfsg1-2 was uploaded on 2014-04-08 23:19:08 -0400 EDT
Version 0.9.1~dfsg1-1 was uploaded on 2014-04-03 21:38:30 -0400 EDT
Version 0.9.0+dfsg1-1 was uploaded on 2014-03-11 22:24:31 -0400 EDT
Version 0.8.1+dfsg1-1 was uploaded on 2014-02-25 20:56:31 -0500 EST
Version 0.8.0+dfsg1-2 was uploaded on 2014-02-15 17:51:58 -0500 EST
Version 0.8.0+dfsg1-1 was uploaded on 2014-02-10 20:41:10 -0500 EST
Version 0.7.6+dfsg1-1 was uploaded on 2014-01-22 22:50:47 -0500 EST
Version 0.7.1+dfsg1-1 was uploaded on 2014-01-15 20:22:34 -0500 EST
Version 0.6.7+dfsg1-3 was uploaded on 2014-01-09 20:10:20 -0500 EST
Version 0.6.7+dfsg1-2 was uploaded on 2014-01-08 19:14:02 -0500 EST
Version 0.6.7+dfsg1-1 was uploaded on 2014-01-07 21:06:10 -0500 EST
control
Next is one of the most complex, and one of the oldest parts of go-debian,
which is the control file parser
(otherwise sometimes known as deb822). This module was inspired by the way
that the json module works in Go, allowing for files to be defined in code
with a struct. This tends to be a bit more declarative, but also winds up
putting logic into struct tags, which can be a nasty anti-pattern if used too
much.
The first primitive in this module is the concept of a Paragraph, a struct
containing two values, the order of keys seen, and a map of string to string.
All higher order functions dealing with control files will go through this
type, which is a helpful interchange format to be aware of. All parsing of
meaning from the Control file happens when the Paragraph is unpacked into
a struct using reflection.
The idea behind this strategy that you define your struct, and let the Control
parser handle unpacking the data from the IO into your container, letting you
maintain type safety, since you never have to read and cast, the conversion
will handle this, and return an Unmarshaling error in the event of failure.
Additionally, Structs that define an anonymous member of control.Paragraph
will have the raw Paragraph struct of the underlying file, allowing the
programmer to handle dynamic tags (such as X-Foo), or at least, letting
them survive the round-trip through go.
The default decoder
contains an argument, the ability to verify the input control file using an
OpenPGP keyring, which is exposed to the programmer through the
(*Decoder).Signer() function. If the passed argument is nil, it will not
check the input file signature (at all!), and if it has been passed, any
signed data must be found or an error will fall out of the NewDecoder call.
On the way out, the opposite happens, where the struct is introspected,
turned into a control.Paragraph, and then written out to the io.Writer.
Here's a quick (and VERY dirty) example showing the basics of reading and
writing Debian Control files with go-debian.
packagemainimport("fmt""io""net/http""strings""pault.ag/go/debian/control")typeAllowedPackagestructPackagestringFingerprintstringfunc(a*AllowedPackage)UnmarshalControl(instring)errorin=strings.TrimSpace(in)chunks:=strings.SplitN(in," ",2)iflen(chunks)!=2returnfmt.Errorf("Syntax sucks: '%s'",in)a.Package=chunks[0]a.Fingerprint=chunks[1][1:len(chunks[1])-1]returnniltypeDMUAstructFingerprintstringUidstringAllowedPackages[]AllowedPackage control:"Allow" delim:"," funcmain()resp,err:=http.Get("http://metadata.ftp-master.debian.org/dm.txt")iferr!=nilpanic(err)decoder,err:=control.NewDecoder(resp.Body,nil)iferr!=nilpanic(err)fordmua:=DMUAiferr:=decoder.Decode(&dmua);err!=niliferr==io.EOFbreakpanic(err)fmt.Printf("The DM %s is allowed to upload:\n",dmua.Uid)for_,allowedPackage:=rangedmua.AllowedPackagesfmt.Printf(" %s [granted by %s]\n",allowedPackage.Package,allowedPackage.Fingerprint)
Output (truncated!) looks a bit like:
...
The DM Allison Randal <allison@lohutok.net> is allowed to upload:
parrot [granted by A4F455C3414B10563FCC9244AFA51BD6CDE573CB]
...
The DM Benjamin Barenblat <bbaren@mit.edu> is allowed to upload:
boogie [granted by 3224C4469D7DF8F3D6F41A02BBC756DDBE595F6B]
dafny [granted by 3224C4469D7DF8F3D6F41A02BBC756DDBE595F6B]
transmission-remote-gtk [granted by 3224C4469D7DF8F3D6F41A02BBC756DDBE595F6B]
urweb [granted by 3224C4469D7DF8F3D6F41A02BBC756DDBE595F6B]
...
The DM <aelmahmoudy@sabily.org> is allowed to upload:
covered [granted by 41352A3B4726ACC590940097F0A98A4C4CD6E3D2]
dico [granted by 6ADD5093AC6D1072C9129000B1CCD97290267086]
drawtiming [granted by 41352A3B4726ACC590940097F0A98A4C4CD6E3D2]
fonts-hosny-amiri [granted by BD838A2BAAF9E3408BD9646833BE1A0A8C2ED8FF]
...
...
deb
Next up, we've got the deb module. This contains code to handle reading
Debian 2.0 .deb files. It contains a wrapper that will parse the control
member, and provide the data member through the
archive/tar interface.
Here's an example of how to read a .deb file, access some metadata, and
iterate over the tar archive, and print the filenames of each of the
entries.
dependency
The dependency package provides an interface to parse and compute
dependencies. This package is a bit odd in that, well, there's no other
library that does this. The issue is that there are actually two different
parsers that compute our Dependency lines, one in Perl (as part of dpkg-dev)
and another in C (in dpkg).
To date, this has resulted in me filing
threedifferentbugs.
I also found a broken package in the
archive,
which actually resulted in another bug being (totally accidentally)
already fixed.
I hope to continue to run the archive through my parser in hopes of finding
more bugs! This package is a bit complex, but it basically just returns what
amounts to be an AST
for our Dependency lines. I'm positive there are bugs, so file them!
funcmain()dep,err:=dependency.Parse("foo bar, baz, foobar [amd64] bazfoo [!sparc], fnord:armhf [gnu-linux-sparc]")iferr!=nilpanic(err)anySparc,err:=dependency.ParseArch("sparc")iferr!=nilpanic(err)for_,possi:=rangedep.GetPossibilities(*anySparc)fmt.Printf("%s (%s)\n",possi.Name,possi.Arch)
Gives the output:
foo (<nil>)
baz (<nil>)
fnord (armhf)
version
Right off the bat, I'd like to thank
Michael Stapelberg for letting me graft this
out of dcs and into the go-debian package.
This was nearly entirely his work (with a one or two line function I added
later), and was amazingly helpful to have. Thank you!
This module implements Debian version comparisons and parsing, allowing for
sorting in lists, checking to see if it's native or not, and letting the
programmer to implement smart(er!) logic based on upstream (or Debian)
version numbers.
This module is extremely easy to use and very straightforward, and not worth
writing an example for.
Final thoughts
This is more of a "Yeah, OK, this has been useful enough to me at this point
that I'm going to support this" rather than a "It's stable!" or even
"It's alive!" post. Hopefully folks can report bugs and help iterate on
this module until we have some really clean building blocks to build
solid higher level systems on top of. Being able to have multiple libraries
interoperate by relying on go-debian will be a massive ease.
I'm in need of more documentation, and to finalize some parts of the older
sub package APIs, but I'm hoping to be at a "1.0" real soon now.
A longish blog post, please bear, a second part of the blog post would be published in few days from now. My fixed visa finally arrived, yeah But this story doesn t start here, it starts about a year back. While I have been contributing to Debian in my free time over the years, and sometimes paid time as well, I had never thought of going overseas as the experiences I knew from friends and relatives, it isn t easy to get all the permissions and paperwork done to say the least (bureaucracy @ work). But last year, when Debconf 15 was being launched, there are/were 2-3 friends of mine who are studying, doing their Ph.D. in some computer/web stuff, living in Germany currently that they goaded me to apply. The first few times I gave some standard excuses, but when they kept on for a while, just to shut them up I applied to the debconf team applying for food, accommodation and travel sponsorship.
I didn t have high hopes as there obviously are many more talented peers around me who understand FOSS and Debian at a much more fundamental, philosophical as well as technical level than me. Much to my surprise though, about a month (and around two or three weeks just before the event was about to take place) I got the bursary/sponsorships for food, accommodation as well as travel. I was unsure that the remaining time was enough to get a visa hence declined that time around.
That whole episode gave me the confidence that perhaps my application would be accepted if I applied again. Using my previous years understanding, decided to give it a shot again as this would also enable me to get a feel of visa bureaucracy as well as gain a bit of novice understanding about what factors go in choosing a flight and believe me the latter part proved to be pretty confusing. While the visa business seems easy, the form at least is easy and what they ask, it can be troublesome as far as visa-processing process is concerned. It took a better part of the month to get the visa which I needed. The in-between time is and can be a bit stressful as you have committed funds for travel i.e. the airline tickets and are in a limbo as you didn t know that if the visa is cancelled for some reason, your tickets would be refunded or not. A little history is needed and hopefully is helpful for anybody who s applying for a short-stay Visa in South Africa.
Exactly, A month and day back I had applied for visa. The visa I had applied for is 17 days as the flights within my budget was for those days only. The visa I got was for 10 days only which was ending in the middle of the conference. I tried many avenues to get information and was told that I needed to write a correction letter telling/sharing the information about the correct time period and dates in BOLD with a heavier weight/point which is what I did and gave to VFS office without any further payment on my part. It took a bit more time than the first time around but the consulate co-operated. While I can understand the oversight as they probably get more visas requests along with special and urgent requests so such occurrences can happen. I am and was happy that there was a recourse rather than starting from scratch which probably would have made me more anxious due to the first experience .
Apparently I was lucky that I had done with Qatar Airways as later came to know that there are other airways which don t refund money even after visa rejection . This information I got to know pretty late in the game otherwise I wouldn t have been much stressed. As had committed knew had to go the whole hog and whatever barriers are there, have overcome at least as far as the visa part/process is concerned.
Now after few days, will probably start to worry about the actual travel, part nervousness, part excitement, nervousness as it will be an alien land, am obese so traveling economy on 787-8 and 777-300 ER will be tricky. The 787-8 will probably be a rough ride as it s a 9 hr. journey and the seat are a mere 18 , the cattle class as shared by one of our esteemed politicians. This blame has to do with Boeing 787 rather than anybody else. Hopefully, if there is a next time, would make better choices.
Anyways,have selected an aisle seat so that will be able to walk every hr. or so to get the circulation in legs going as leg room in economy is not much from my domestic air travel experiences. If I do survive the travel, then will see South Africa and try to get some free time and explore South Africa and try to figure out how are they able to get one and half time tourists while we get around half figure for a whole year even though we are bigger (area-wise) to South Africa. I did find something positive for us as well, it s not all doldrums all around.
Now, I had been thinking about if I know any South African music and movies. I had explored djembe while growing up in teens but other than that, not much. The only music I have heard is Harry Belafonte . So I hope to bring some Indian movies and music with me so that people if they have not explored Bollywood as well as Indian classical music could explore some of it, of course it will be pale imitation of what Sawai Gandharva Music Festival for instance gives. I also hope to hear and get some music and movies to learn more about South Africa. Filed under: Miscellenous Tagged: #bollywood, #Debconf Germany 2015, #Debconf South Africa 2016, #Debconf15, #Debconf16, #djembe, #South-African consulate, music, tourism, visa
What happened in the reproducible
builds effort between February 28th and March 5th:
Toolchain fixes
Antonio Terceiro uploaded gem2deb/0.27 that forces generated gemspecs to use the date from debian/changelog.
Antonio Terceiro uploaded gem2deb/0.28 that forces generated gemspecs to have their contains file lists sorted.
Robert Luberda uploaded ispell/3.4.00-5 which make builds of hashes reproducible.
C dric Boutillier uploaded ruby-ronn/0.7.3-4 which will make the output locale agnostic. Original patch by Chris Lamb.
Markus Koschany uploaded spring/101.0+dfsg-1. Fixed by Alexandre Detiste.
Ximin Luo resubmitted the patch adding the --clamp-mtime option to Tar on Savannah's bug tracker.
Lunar rebased our experimental dpkg on top of the current master branch. Changes in the test infrastructure are required before uploading a new version to our experimental repository.
Reiner Herrmann rebased our custom texlive-bin against the latest uploaded version.
Patches submitted which have not made their way to the archive yet:
#816209 on elog by Reiner Herrmann: use printf instead of echo which is shell-independent.
#816214 on python-pip by Reiner Herrmann: removes timestamp from generated Python scripts.
#816230 on rows by Reiner Herrmann: tell grep to always treat the input as text.
#816232 on eficas by Reiner Herrmann: use printf instead of echo which is shell-independent.
Florent Daigniere and bancfc reported that linux-grsec was currently built with GRKERNSEC_RANDSTRUCT which will prevent reproducible builds with the current packaging.
tests.reproducible-builds.org
pbuilder has been updated to the last version to be able to support Build-Depends-Arch and Build-Conflicts-Arch. (Mattia Rizzolo, h01ger)
New package sets have been added for Subgraph OS, which is based on Debian Stretch: packages and build dependencies. (h01ger)
Two new armhf build nodes have been added (thanks Vagrant Cascadian) and integrated in our Jenkins setup with 8 new armhf builder jobs. (h01ger)
strip-nondeterminism development
strip-nondeterminism version 0.016-1 was released on Sunday 28th. It will now normalize the POT-Creation-Date field in GNU Gettext .mo files. (Reiner Herrmann) Several improvements to the packages metadata have also been made. (h01ger, Ben Finney)
Package reviews
185 reviews have been removed, 91 added and 33 updated in the previous week.
New issue: fileorder_in_gemspec_files_list.
43 FTBFS bugs were reported by Chris Lamb, Martin Michlmayr, and gregor herrmann.