It's Sunday and I'm now sitting in the train from Brest to Paris where I will be changing to Germany, on the way back from the annual Debian conference. A full week of presentations, discussions, talks and socializing is laying behind me and my head is still spinning from the intensity.
Pollito and the gang of DebConf mascots wearing their conference badges (photo: Christoph Berg)
Table of Contents
Sunday, July 13th
It started last Sunday with traveling to the conference. I got on the Eurostar in Duisburg and we left on time, but even before reaching Cologne, the train was already one hour delayed for external reasons, collecting yet another hour between Aachen and Liege for its own technical problems. "The train driver is working on trying to fix the problem." My original schedule had well over two hours for changing train stations in Paris, but being that late, I missed the connection to Brest in Montparnasse. At least in the end, the total delay was only one hour when finally arriving at the destination. Due to the French julliet quatorze fireworks approaching, buses in Brest were rerouted, but I managed to catch the right bus to the conference venue, already meeting a few Debian people on the way.
The conference was hosted at the IMT Atlantique Brest campus, giving the event a nice university touch. I arrived shortly after 10 in the evening and after settling down a bit, got on one of the "magic" buses for transportation to the camping site where half of the attendees where stationed. I shared a mobile home with three other Debianites, where I got a small room for myself.
Monday, July 14th
Next morning, we took the bus back to the venue with a small breakfast and the opening session where Enrico Zini invited me to come to his and Nicolas Dandrimont's session about Debian community governance and curation, which I gladly did. Many ideas about conflict moderation and community steering were floated around. I hope some of that can be put into effect to make flamewars on the mailing lists less heated and more directed. After that, I attended Olly Betts' "Stemming with Snowball" session, which is the stemmer used also in PostgreSQL. Text search is one of the areas in PostgreSQL that I never really looked closely at, including the integration into the postgresql-common package, so it was nice to get more information about that.
In preparation for the conference, a few of us Ham radio operators in Debian had decided to bring some radio gear to DebConf this year in order to perhaps spark more interest for our hobby among the fellow geeks. In the afternoon after the talks, I found a quieter spot just outside of the main hall and set up a shortwave antenna by attaching a 10m mast to one of the park benches there. The 40m band was still pretty much closed, but I could work a few stations from England, just across the channel from Bretagne, answering questions from interested passing-by Debian people between the contacts. Over time, the band opened and more European stations got into the log.
F/DF7CB in Brest (photo: Evangelos Ribeiro Tzaras)
Tuesday, July 15th
Tuesday started with Helmut Grohne's session about "Reviving (un)schroot". The schroot program has been Debian's standard way of managing build chroots for a long time, but it is more and more being regarded as obsolete with all kinds of newer containerization and virtualization technologies taking over. Since many bits of Debian infrastructure depend on schroot, and its user interface is still very useful, Helmut reimplemented it using Linux namespaces and the "unshare" systemcall. I had already worked with him at the Hamburg Minidebconf to replace the apt.postgresql.org buildd machinery with the new system, but we were not quite there yet (network isolation is nice, but we still sometimes need proper networking), so it was nice to see the effort is still progressing and I will give his new scripts a try when I'm back home.
Next, Stefano Rivera and Colin Watson presented Debusine, a new package repository and workflow management system. It looks very promising for anyone running their own repository, so perhaps yet another bit of apt.postgresql.org infrastructure to replace in the future. After that, I went to the Debian LTS BoF session by Santiago Ruano Rinc n and Bastien Roucari s - Debian releases plus LTS is what we are covering with apt.postgresql.org. Then there were bits from the DPL (Debian Project Leader), and a session moderated by Stefano Rivera interesting to me as a member of the Debian Technical Committee on the future structure of the packages required for cross-building in Debian, a topic which had been brought to TC a while ago. I am happy that we could resolve the issue without having to issue a formal TC ruling as the involved parties (kernel, glibc, gcc and the cross-build people) found a promising way forward themselves. DebConf is really a good way to get such issues unstuck.
Ten years ago at the 2015 Heidelberg DebConf, Enrico had given a seminal "Semi-serious stand-up comedy" talk, drawing parallels between the Debian Open Source community and the BDSM community - "People doing things consensually together". (Back then, the talk was announced as "probably unsuitable for people of all ages".) With his unique presentation style and witty insights, the session made a lasting impression on everyone attending. Now, ten years later (and he and many in the audience being ten years older), he gave an updated version of it. We are now looking forward to the sequel in 2035. The evening closed with the famous DebConf tradition of the Cheese & Wine party in a old fort next to the coast, just below the conference venue. Even when he's a fellow Debian Developer, Ham and also TC member, I had never met Paul Tagliamonte in person before, but we spent most of the evening together geeking out on all things Debian and Ham radio.
The northern coast of Ushant (photo: Christoph Berg)
Wednesday, July 16th
Wednesday already marked the end of the first half of the week, the day of the day trips. I had chosen to go to Ouessant island (Ushant in English) which marks the Western end of French mainland and hosts one of the lighthouses yielding the way into the English channel. The ferry trip included surprisingly big waves which left some participants seasick, but everyone recovered fast. After around one and a half hours we arrived, picked up the bicycles, and spent the rest of the day roaming the island. The weather forecast was originally very cloudy and 18 C, but over noon this turned into sunny and warm, so many got an unplanned sunburn. I enjoyed the trip very much - it made up for not having time visiting the city during the week. After returning, we spent the rest of the evening playing DebConf's standard game, Mao (spoiler alert: don't follow the link if you ever intend to play).
Having a nice day (photo: Christoph Berg)
Thursday, July 17th
The next day started with the traditional "Meet the Technical Committee" session. This year, we trimmed the usual slide deck down to remove the boring boilerplate parts, so after a very short introduction to the work of the committee by our chairman Matthew Vernon, we opened up the discussion with the audience, with seven (out of 8) TC members on stage. I think the format worked very well, with good input from attendees. Next up was "Don't fear the TPM" by Jonathan McDowell. A common misconception in the Free Software community is that the TPM is evil DRM hardware working against the user, but while it could be used in theory that way, the necessary TPM attestations seem to impossible to attain in practice, so that wouldn't happen anyway. Instead, it is a crypto coprocessor present in almost all modern computers that can be used to hold keys, for example to be used for SSH. It will also be interesting to research if we can make use of it for holding the Transparent Data Encryption keys for CYBERTEC's PostgreSQL Enterprise Edition.
Aigars Mahinovs then directed everyone in place for the DebConf group picture, and Lucas Nussbaum started a discussion about archive-wide QA tasks in Debian, an area where I did a lot of work in the past and that still interests me. Antonio Terceiro and Paul Gevers followed up with techniques to track archive-wide rebuilding and testing of packages and in turn filing a lot of bugs to track the problems. The evening ended with the conference dinner, again in the fort close by the coast. DebConf is good for meeting new people, and I incidentally ran into another Chris, who happened to be one of the original maintainers of pgaccess, the pre-predecessor of today's pgadmin. I admit still missing this PostgreSQL frontend for its simplicity and ability to easily edit table data, but it disappeared around 2004.
Friday, July 18th
On Friday, I participated in discussion sessions around contributors.debian.org (PostgreSQL is planning to set up something similar) and the New Member process which I had helped to run and reform a decade or two ago. Agathe Porte (also a Ham radio operator, like so many others at the conference I had no idea of) then shared her work on rust-rewriting the slower parts of Lintian, the Debian package linter. Craig Small talked about "Free as in Bytes", the evolution of the Linux procps free command. Over the time and many kernel versions, the summary numbers printed became better and better, but there will probably never be a version that suits all use cases alike. Later over dinner, Craig (who is also a TC member) and I shared our experiences with these numbers and customers (not) understanding them. He pointed out that for PostgreSQL and looking at used memory in the presence of large shared memory buffers, USS (unique set size) and PSS (proportional set size) should be more realistic numbers than the standard RSS (resident set size) that the top utility is showing by default.
Antonio Terceiro and Paul Gevers again joined to lead a session, now on ci.debian.net and autopkgtest, the test driver used for running tests on packages after then have been installed on a system. The PostgreSQL packages are heavily using this to make sure no regressions creep in even after builds have successfully completed and test re-runs are rescheduled periodically. The day ended with Bdale Garbee's electronics team BoF and Paul Tagliamonte and me setting up the radio station in the courtyard, again answering countless questions about ionospheric conditions and operating practice.
Saturday, July 19th
Saturday was the last conference day. In the first session, Nikos Tsipinakis and Federico Vaga from CERN announced that the LHC will be moving to Debian for the accelerator's frontend computers in their next "long shutdown" maintenance period in the next year. CentOS broke compatibility too often, and Debian trixie together with the extended LTS support will cover the time until the next long shutdown window in 2035, until when the computers should have all been replaced with newer processors covering higher x86_64 baseline versions. The audience was very delighted to hear that Debian is now also being used in this prestige project.
Ben Hutchings then presented new Linux kernel features. Particularly interesting for me was the support for atomic writes spanning more than one filesystem block. When configured correctly, this would mean PostgreSQL didn't have to record full-page images in the WAL anymore, increasing throughput and performance. After that, the Debian ftp team discussed ways to improve review of new packages in the archive, and which of their processes could be relaxed with new US laws around Open Source and cryptography algorithms export. Emmanuel Arias led a session on Salsa CI, Debian's Gitlab instance and standard CI pipeline. (I think it's too slow, but the runners are not under their control.) Julian Klode then presented new features in APT, Debian's package manager. I like the new display format (and a tiny bit of that is also from me sending in wishlist bugs).
In the last round of sessions this week, I then led the Ham radio BoF with an introduction into the hobby and how Debian can be used. Bdale mentioned that the sBitx family of SDR radios is natively running Debian, so stock packages can be used from the radio's touch display. We also briefly discussed his involvement in ARDC and the possibility to get grants from them for Ham radio projects. Finally, DebConf wrapped up with everyone gathering in the main auditorium and cheering the organizers for making the conference possible and passing Pollito, the DebConf mascot, to the next organizer team.
Pollito on stage (photo: Christoph Berg)
Sunday, July 20th
Zoom back to the train: I made it through the Paris metro and I'm now on the Eurostar back to Germany. It has been an intense week with all the conference sessions and meeting all the people I had not seen so long. There are a lot of new ideas to follow up on both for my Debian and PostgreSQL work. Next year's DebConf will take place in Santa Fe, Argentina. I haven't yet decided if I will be going, but I can recommend the experience to everyone!
The post The Debian Conference 2025 in Brest appeared first on CYBERTEC PostgreSQL Services & Support.
I have been a bearded subject since I was 18, back in 1994. Yes,
during 1999-2000, I shaved for my military service, and I briefly tried the
goatee look in 2008 Few people nowadays can imagine my face without
a forest of hair.
But sometimes, life happens. And, unlike my good friend
Bdale, I didn t get Linus to do the
honors But, all in all, here I am:
Turns out, I have been suffering from quite bad skin infections for a
couple of years already. Last Friday, I checked in to the hospital,
with an ugly, swollen face (I won t put you through that), and the
hospital staff decided it was in my best interests to trim my
beard. And then some more. And then shave me. I sat in the hospital
for four days, getting soaked (medical term) with antibiotics and
otherstuff, got my recipes for the next few days, and well, I
really hope that s the end of the infections. We shall see!
So, this is the result of the loving and caring work of three
different nurses. Yes, not clean-shaven (I should not trim it
further, as shaving blades are a risk of reinfection).
Anyway I guess the bits of hair you see over the place will not
take too long to become a beard again, even get somewhat
respectable. But I thought some of you would like to see the real me
PS- Thanks to all who have reached out with good wishes. All is fine!
I joined the
Debian project in late 1994, well before the first
stable release was issued, and have been involved in various ways continuously
ever since. Over the years, I adopted a number of packages that are, or at
least were at one time, fundamental to the distribution.
But, not surprisingly, my interests have shifted over time. In the more than
quarter century I've contributed to Debian, I've adopted existing packages
that needed attention, packaged new software I wanted to use that wasn't yet
in Debian, offered packages up for others to adopt, and even sometimes
requested the removal of packages that became obsolete or replaced by
something better. That all felt completely healthy.
But over the last couple weeks, I realized I'm still "responsible" for some
packages I'd had for a very long time, that generally work well but over time
have accumulated bugs in functionality I just don't use, and frankly haven't
been able to find the motivation to chase down. As one example, I just
noticed that I first uploaded the gzip package 25 years ago today, on
2 December 1995. And while the package works fine for me and most other
folks, there are 30 outstanding bugs and 3 forwarded bugs that I just can't
muster up any energy to address.
So, I just added gzip to a short list of packages I've offered up for
adoption recently. I'm pleased that tar already has a new maintainer, and
hope that both sudo and gzip will get more attention soon.
It's not that I'm less interested in Debian. I've just been busy recently
packaging up more software I use or want to use in designing high
power model
rockets and the solid propellant motors I fly in them, and would rather spend
the time I have available for Debian maintaining those packages and all their
various build dependencies than continuing to be responsible for core
packages in the distribution that "work fine for me" but could use attention.
I'm writing about this partly to mark the passing of more than a quarter
century as a package maintainer for Debian, partly to encourage other Debian
package maintainers with the right skills and motivation to consider adopting
some of the packages I'm giving up, and finally to encourage other long-time
participants in Debian to spend a little time evaluating their own package
lists in a similar way.
DebConf4
This tshirt is 16 years old and from DebConf4. Again, I should probably wash it at 60 celcius for once...
DebConf4 was my 2nd DebConf and took place in Porto Alegre, Brasil.
Like many DebConfs, it was a great opportunity to meet people:
I remember sitting in the lobby of the venue and some guy asked me what I did in Debian and I told
him about my little involvements and then asked him what he was doing, and he told me he wanted to
become involved in Debian again, after getting distracted away. His name was Ian Murdock...
DebConf4 also had a very cool history session in the hallway track (IIRC, but see below) with
Bdale Garbee, Ian Jackson and Ian Murdock and with a young student named Biella Coleman busy writing notes.
That same hallway also saw the kickoff meeting of the Debian Women project, though sadly
today http://tinc.debian.net ("there's no cabal") only shows an apache placeholder page and not
a picture of that meeting.
DebCon4 was also the first time I got a bit involved in preparing DebConf, together with
Jonas Smedegaard I've set up some computers there, using FAI. I had no idea that this was
the start of me contributing to DebConfs for text ten years.
And of course I also saw some talks, including one which I really liked, which then in turn made
me notice there were no people doing video recordings, which then lead to something...
I missed the group picture of this one. I guess it's important to me to mention it because
I've met very wonderful people at this DebConf... (some mentioned in this post, some not. You know
who you are!)
Afterwards some people stayed in Porto Alegre for FISL,
where we saw Lawrence Lessing present Creative Commons to the world for the first time. On the flight
back I sat next to a very friendly guy from Poland and we talked almost the whole flight and then
we never saw each other again, until 15 years later in Asia...
Oh, and then, after DebConf4, I used IRC for the first time. And stayed in the #debconf4 IRC channel
for quite some years
Finally, DebConf4 and more importantly FISL, which was really big (5000 people?) and after that,
the wizard of OS conference in Berlin
(which had a very nice talk about Linux in different places in the world, illustrating the
different states of 'first they ignore you, then they laugh at you, then they fight you, then you win'),
made me quit my job at a company supporting Windows- and Linux-setups as I realized I'd better
start freelancing with Linux-only jobs. So, once again, my life would have been different
if I would not have attended these events!
Note: yesterdays post about DebConf3 was thankfully corrected twice. This might well happen
to this post too!
A few days ago I ordered a small batch of
the ChaosKey, a small
USB dongle for generating entropy created by Bdale Garbee and Keith
Packard. Yesterday it arrived, and I am very happy to report that it
work great! According to its designers, to get it to work out of the
box, you need the Linux kernel version 4.1 or later. I tested on a
Debian Stretch machine (kernel version 4.9), and there it worked just
fine, increasing the available entropy very quickly. I wrote a small
test oneliner to test. It first print the current entropy level,
drain /dev/random, and then print the entropy level for five seconds.
Here is the situation without the ChaosKey inserted:
% cat /proc/sys/kernel/random/entropy_avail; \
dd bs=1M if=/dev/random of=/dev/null count=1; \
for n in $(seq 1 5); do \
cat /proc/sys/kernel/random/entropy_avail; \
sleep 1; \
done
300
0+1 oppf ringer inn
0+1 oppf ringer ut
28 byte kopiert, 0,000264565 s, 106 kB/s
4
8
12
17
21
%
The entropy level increases by 3-4 every second. In such case any
application requiring random bits (like a HTTPS enabled web server)
will halt and wait for more entrpy. And here is the situation with
the ChaosKey inserted:
% cat /proc/sys/kernel/random/entropy_avail; \
dd bs=1M if=/dev/random of=/dev/null count=1; \
for n in $(seq 1 5); do \
cat /proc/sys/kernel/random/entropy_avail; \
sleep 1; \
done
1079
0+1 oppf ringer inn
0+1 oppf ringer ut
104 byte kopiert, 0,000487647 s, 213 kB/s
433
1028
1031
1035
1038
%
Quite the difference. :) I bought a few more than I need, in case
someone want to buy one here in Norway. :)
Update: The dongle was presented at Debconf last year. You might
find the talk
recording illuminating. It explains exactly what the source of
randomness is, if you are unable to spot it from the schema drawing
available from the ChaosKey web site linked at the start of this blog
post.
When I was younger, and worked in an "old HP" test and measurement division,
I sometimes sat at lunch in the cafeteria with a group of older co-workers
who I grew to have immense respect for. They told great stories. I learned
a lot of practical electronics from them... and other things too.
Each carried on their person a copy of the US Constitution and Bill of
Rights, and most also had a "concealed carry" permit, which they would refer
to as their "redneck license". I quickly learned that they weren't all gun
fanatics... at that time, the vetting process for such a permit was a bit
daunting, and having one was their way of "proving" that they were honest,
law-abiding citizens. Citizens who knew their rights. Who enjoyed debating
boundary conditions in those rights inspired by current events at the lunch
table. I miss those guys and those conversations.
I mention this because it's one of those things that I realize now had a
significant formative impact on my adult values and world view. Freedom
matters. That's why, despite my long-standing appreciation for and support
of the organization's activities, I'm embarrassed to admit that it wasn't
until this week that I personally joined the
American Civil Liberties Union
and sent them a donation.
At the end of August 2012, I announced my
Early Retirement
from HP. Two years later, my friend and former boss Martin Fink
successfully recruited me to return to what later became
Hewlett Packard Enterprise, as an
HPE Fellow
working on open source strategy in his Office of the CTO.
I'm proud of what I was was able to accomplish in the 25 months since then,
but recent efforts to "simplify" HPE actually made things complicated for
me. Between the announcement in late June that
Martin intended to retire himself,
and the two major spin-merger announcements involving
Enterprise Services
and
Software... well...
The bottom line is that today, 30 September 2016, is my last day at HPE.
My plan is to "return to retirement" and work on some fun projects with my wife
now that we are "empty nesters". I do intend to remain involved in the Free
Software and open hardware worlds, but whether that might eventually involve
further employment is something I'm going to try and avoid thinking about
for a while...
There is a rocket launch scheduled nearby this weekend, after all!
What happened in the Reproducible
Builds effort between Sunday August 14 and Saturday August 20 2016:
Fasten your seatbelts
Important note: we enabled build path variation for unstable now, so your package(s) might become unreproducible, while previously it was said to be reproducible given a specific build path it probably still is reproducible but read on for the details below in the tests.reproducible-builds.org section! As said many times: this is still research and we are working to make it reality.
Media coverage
Daniel Stender blogged about python
packaging and
explained some caveats regarding reproducible builds.
Toolchain developments
Thomas Schmitt uploaded
xorriso which now
obeysSOURCE_DATE_EPOCH. As
stated in its man pages:
ENVIRONMENT
[...]
SOURCE_DATE_EPOCH belongs to the specs of reproducible-builds.org. It
is supposed to be either undefined or to contain a decimal number which
tells the seconds since january 1st 1970. If it contains a number, then
it is used as time value to set the default of --modification-date=,
--gpt_disk_guid, and --set_all_file_dates. Startup files and program
options can override the effect of SOURCE_DATE_EPOCH.
Packages reviewed and fixed, and bugs filed
The following packages have become reproducible after being fixed:
The following updated packages appear to be reproducible now, for reasons we
were not able to figure out. (Relevant changelogs did not mention reproducible
builds.)
The following 2 packages were not changed, but have become reproducible due
to changes in their build-dependencies: tagsouptclx8.4.
Some uploads have addressed some reproducibility issues, but not all of them:
Chris Lamb pinged 164 bugs he filed more than 90 days ago which have a patch and had no maintainer reaction.
Reviews of unreproducible packages
55 package reviews have been added, 161 have been updated and 136 have been
removed in this week, adding to our knowledge about identified
issues.
2 issue types have been updated:
diffoscope development
Chris Lamb, Holger Levsen and Mattia Rizzolo worked on diffoscope this week.
Improvements were made to SquashFS and JSON comparison, the
https://try.diffoscope.org/ web service, documentation,
packaging, and general code quality.
diffoscope 57, 58, and 59 were uploaded to unstable by Chris Lamb. Versions 57
and 58 were both broken, so Holger set up a job on jenkins.debian.net to test
diffoscope on each git commit. He also wrote a CONTRIBUTING document to help
prevent this from happening in future.
From these efforts, we were also able to learn that diffoscope is now reproducible
even when built across multiple architectures:
< h01ger> https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/diffoscope.html shows these packages were built on amd64:
< h01ger> bd21db708fe91c01ba1c9cb35b9d41a7c9b0db2b 62288 diffoscope_59_all.deb
< h01ger> 366200bf2841136a4c8f8c30bdc87057d59a4cdd 20146 trydiffoscope_59_all.deb
< h01ger> and on i386:
< h01ger> bd21db708fe91c01ba1c9cb35b9d41a7c9b0db2b 62288 diffoscope_59_all.deb
< h01ger> 366200bf2841136a4c8f8c30bdc87057d59a4cdd 20146 trydiffoscope_59_all.deb
< h01ger> and on armhf:
< h01ger> bd21db708fe91c01ba1c9cb35b9d41a7c9b0db2b 62288 diffoscope_59_all.deb
< h01ger> 366200bf2841136a4c8f8c30bdc87057d59a4cdd 20146 trydiffoscope_59_all.deb
And those also match the binaries uploaded by Chris in his diffoscope 59 binary upload to ftp.debian.org, yay! Eating our own dogfood and enjoying it!
tests.reproducible-builds.org
Debian related:
show percentage of results in the last 24/48h (h01ger)
switch python database backend to SQLAlchemy (Valerie)
vary build path varitation for unstable and experimental for all architectures. (h01ger)
The last change probably will have an impact you will see: your package might become unreproducible in unstable and this will be shown on tracker.debian.org, while it will still be reproducible in testing.
We've done this, because we think reproducible builds are possible with arbitrary build paths. But: we don't think those are a realistic goal for stretch, where we still recommend to use .buildinfo to record the build patch and then do rebuilds using that path.
We are doing this, because besides doing theoretical groundwork we also have a practical goal: enable users to independently verify builds. And if they only can do this with a fixed path, so be it. For now
To be clear: for Stretch we recommend that reproducible builds are done in the same build path as the "original" build.
Finally, and just for our future references, when we enabled build path variation on Saturday, August 20th 2016, the numbers for unstable were:
suite
all
reproducible
unreproducible
ftbfs
depwait
not for this arch
blacklisted
unstable/amd64
24693
21794 (88.2%)
1753 (7.1%)
972 (3.9%)
65 (0.2%)
95 (0.3%)
10 (0.0%)
unstable/i386
24693
21182 (85.7%)
2349 (9.5%)
972 (3.9%)
76 (0.3%)
103 (0.4%)
10 (0.0%)
unstable/armhf
24693
20889 (84.6%)
2050 (8.3%)
1126 (4.5%)
199 (0.8%)
296 (1.1%)
129 (0.5%)
Misc.
Ximin Luo updated our git setup scripts to make it easier for people to write
proper descriptions for our repositories.
This week's edition was written by Ximin Luo and Holger Levsen and reviewed by
a bunch of Reproducible Builds folks on IRC.
Today was day one of the DebConf16 Open Festival and I attended
the open hardware panel,
part of the talk about Code For South Africa,
shirish's experiences
and the DebConf new folks session.
The open hardware panel was a wide ranging discussion between bdale, Andy and indiebio.
bdate talked about the experiences he has had with his rocketry hardware.
bdale said "Make concious decisions about what you are buying",
referencing a case where he investigated, found a GPL violation and didn't buy.
Various people care about openness of different layers of the hardware.
Off-the-shelf products are very strongly integrated, which is great for
makers but means that people who care about lower layers like CPU
micro-architecture aren't able to participate.
Andy said "We are just beginning to come out of the shareware stage [of open hardware]".
bdale mentioned the companies who do hardware production as a service from design files.
Later in the pub some folks mentioned j-core, an open re-implementation of SuperH processors.
I missed most of the code4sa talk unfortunately,
but it was about government services and open data.
shirish covered his journey through life to Debian.
His youth, how satellite TV and knowledge of the
outside world came to India around the time of the Iraq war.
His experience accessing the Internet for the first time,
uncensored vs the usual censorship in India's media.
His experiences of Windows 95 viruses and crashes.
He learned of PCTwist Linux through a magazine cover.
His initial install was not a success but eventually
managed to break through and install a desktop,
but experienced network and other issues.
Eventually he encountered Ubuntu and began contributing bug reports.
His experiences there led him to Debian.
He began blogging about Debian.
In the last few years he and others
have been going around the country doing
mini-DebConfs at institutes around India.
The first question was predictably about having a DebConf in India
and how shirish might like to get more involved.
DebConf in India sounds like a possibility some day
and shirish was thinking about getting involved in publicity,
marketting and the Debian installer.
The DebConf new folks session was a great intro to DebConf
for folks new to the community.
There were some quite excellent touches added to this
year's version of the event by indiebio and Rhonda.
I also got some things done.
Usual spam reporting.
Reviewed wiki RecentChanges.
Talked to the chromium-bsu/MacPorts maintainer about AX_CHECK_GL brokenness.
Filed Debian wishlist bug #829292 asking to update autoconf-archive.
Redirected a Hurd porterbox request to the exodar admin
and quickly found out I was wrong to do that, rectified.
Then we found out the LDAP sync to exodar was broken.
Replied to someone who intends to sell Debian pre-installs.
Thanked BunsenLabs folks for joining the derivatives list.
Applied reproducible builds patch for cats from Chris Lamb.
Heard about awesome new terminal-mode screensaver. Moo!
Prepared a blog post about check-all-the-things.
AltOS 1.6.3
Bdale and I are pleased to announce the release of
AltOS version 1.6.3.
AltOS is the core of the software
for all of the Altus Metrum products. It
consists of firmware for our cc1111, STM32L151, STMF042, LPC11U14 and ATtiny85
based electronics and Java-based ground station software.
Version 1.6.3 adds idle mode to AltosDroid and has bug fixes
for our host software on desktops, laptops an android devices
along with BlueTooth support for Windows.
1.6.3 is in Beta test for Android; if you want to use the beta
version, join the AltosDroid beta program
AltOS
AltOS fixes:
Fix hardware flow control on TeleBT v3.0. RTS/CTS is
wired backwards on this board, switch from using the
hardware to driving these pins with software.
AltosUI and TeleGPS Applications
AltosUI and TeleGPS New Features:
Add BlueTooth support for Windows operating system. This
supports connections to TeleBT over BlueTooth rather than
just USB.
AltosUI and TeleGPS Fixes:
Change Java detection and install on Windows. Detection is
now done by looking for the 'javaw.exe' program, and
installation by opening a browser on the java.com web site.
Delay polling while the Fire Igniters is visible to allow
for TeleMega to report back complete status over the radio.
Disallow changing RF calibration numbers in the
configuration UI. There's no good reason to change this from
the field, and recovering is really hard if you haven't
written down the right number.
Fix USB device discovery on Mac OS X El Capitan. This makes
the connected Altus Metrum USB devices appear again.
Fix acceleration data presented in MonitorIdle mode for
TeleMetrum v2.0 flight computers.
AltosDroid
AltosDroid new features:
Monitor Idle mode. Check state of flight computer while in
idle mode over the radio link
Fire Igniters. Remotely fire ignires for recovery system
ground tests.
Remote reboot. Cause the flight computer to reboot over the
radio link. This provides a method for switching the flight
computer from idle to flight mode without needing to reach
the power switch.
Configurable frequency menu. Change the set of available
frequencies and provide more descriptive names.
AltosDroid bug fixes:
Don't set target location if GPS hasn't locked yet.
Fix saving target states so they can be reloaded when the
application restarts. When the application is shut down and
restarted, all previous target state information will be
restored (including GPS position if available).
Fix crash on some Android devices for offline maps when
changing the map scale or location.
Don't require USB OTG support. This kept the latest
AltosDroid from being offered on devices without USB device
support, although it can work without that just fine using
BlueTooth.
Don't require bluetooth to be enabled. This allows the
application to operate with USB devices or just show old
data without turning on the bluetooth radio.
Recover old tracker positions when restarting
application. This finally allows you to safely stop and
restart the application without losing the last known
location of any tracker.
What happened in the reproducible
builds effort between March 13th and March 19th 2016:
Toolchain fixes
Petter Reinholdtsen uploaded naturaldocs/1.51-1.1 which makes the output reproducible. Original patch by Chris Lamb.
Damyan Ivanov uploaded libpdf-api2-perl/2.025-2 which will make internal font ID reproducible.
Christian Hofstaedtler uploaded ruby2.3/2.3.0-5 which sets gzip embedded mtime field to fixed value for rdoc-generated compressed javascript data.
Packages fixed
The following packages have become reproducible due to changes in their
build dependencies:
diction,
doublecmd,
ruby-hiredis,
vdr-plugin-epgsearch.
The following packages became reproducible after getting fixed:
Patches submitted which have not made their way to the archive yet:
#818128 on nethack by Reiner Herrmann: implement support for SOURCE_DATE_EPOCH, set LC_ALL to C, and ensure deterministic build order when running parallel builds.
AltOS 1.6.2 TeleMega v2.0 support, bug fixes and documentation updates
Bdale and I are pleased to announce the release of
AltOS version 1.6.2.
AltOS is the core of the software
for all of the Altus Metrum products. It
consists of firmware for our cc1111, STM32L151, STMF042, LPC11U14 and ATtiny85
based electronics and Java-based ground station software.
This is a minor release of AltOS, including support for our new
TeleMega v2.0 board, a small selection
of bug fixes and a major update of the documentation
AltOS Firmware TeleMega v2.0 added
The updated six-channel flight computer, TeleMega v2.0,
has a few changes from the v1.0 design:
CC1200 radio chip instead of the CC1120. Better receive performance
for packet mode, same transmit performance.
Serial external connector replaced with four PWM channels for
external servos.
Companion pins rewired to match EasyMega functionality.
None of these change the basic functionality of the device, but they
do change the firmware a bit so there's a new package.
AltOS Bug Fixes
We also worked around a ground station limitation in the firmware:
Slow down telemetry packets so receivers can keep up. With TeleMega
v2 offering a fast CPU and faster radio chip, it was overrunning
our receivers so a small gap was introduced between packets.
AltosUI and TeleGPS applications
A few minor new features are in this release
Post-flight TeleMega and EasyMega orientation computations were off
by a factor of two
Downloading eeprom data from flight hardware would
bail if there was an error in a data record. Now it keeps
going.
Documentation
I spent a good number of hours completely reformatting and
restructuring the Altus Metrum documentation.
I've changed the source format from raw docbook to asciidoc, which
has made it much easier to edit and to use docbook features like
links.
The css moves the table of contents out to a sidebar so you can
navigate the html format easily.
There's a separate EasyMini manual
now, constructed by taking sections from the larger manual.
I woke up this morning and realized that for the first time since
17 April 2001,
I am no longer a member of the Debian Technical Committee.
My departure from the committee is a consequence of the
Debian General Resolution
"limiting the term of the technical committee members" that was passed
amending the Debian Constitution nearly a year ago. As the two longest-serving
members, both over the term limit, Steve Langasek and I completed our service
yesterday.
In early March 2015, I
stepped down
from the role of chairman after serving in that role for the better part of
a decade, to help ensure a smooth transition. Don Armstrong is now serving
admirably in that role, I have the utmost respect for the remaining members
of the TC, and the process of nominating replacements for the two now-vacant
seats is already well underway.
So, for the Debian project as a whole, today is really a non-event... which
is exactly as it should be! Debian has been a part of my life since 1994,
and I sincerely hope to be able to remain involved for many years to come!
Long over due post
It s been a long time I haven t written here. And lots of things happened in the OpenStack planet. As a full time employee with the mission to package OpenStack in Debian, it feels like it is kind of my duty to tell everyone about what s going on.
Liberty is out, uploaded to Debian
Since my last post, OpenStack Liberty, the 12th release of OpenStack, was released. In late August, Debian was the first platform which included Liberty, as I proudly outran both RDO and Canonical. So I was the first to make the announcement that Liberty passed most of the Tempest tests with the beta 3 release of Liberty (the Beta 3 is always kind of the first pre-release, as this is when feature freeze happens). Though I never made the announcement that Liberty final was uploaded to Debian, it was done just a single day after the official release.
Before the release, all of Liberty was living in Debian Experimental. Following the upload of the final packages in Experimental, I uploaded all of it to Sid. This represented 102 packages, so it took me about 3 days to do it all.
Tokyo summit
I had the pleasure to be in Tokyo for the Mitaka summit. I was very pleased with the cross-project sessions during the first day. Lots of these sessions were very interesting for me. In fact, I wish I could have attended them all, but of course, I can t split myself in 3 to follow all of the 3 tracks.
Then there was the 2 sessions about Debian packaging on upstream OpenStack infra. The goal is to setup the OpenStack upstream infrastructure to allow packaging using Gerrit, and gating each git commit using the usual tools: building the package and checking there s no FTBFS, running checks like lintian, piuparts and such. I knew already the overview of what was needed to make it happen. What I didn t know was the implementation details, which I hoped we could figure out during the 1:30 slot. Unfortunately, this didn t happen as I expected, and we discussed more general things than I wished. I was told that just reading the docs from the infra team was enough, but in reality, it was not. What currently needs to happen is building a Debian based image, using disk-image-builder, which would include the usual tools to build packages: git-buildpackage, sbuild, and so on. I m still stuck at this stage, which would be trivial if I knew a bit more about how upstream infra works, since I already know how to setup all of that on a local machine.
I ve been told by Monty Tailor that he would help. Though he s always a very busy man, and to date, he still didn t find enough time to give me a hand. Nobody replied to my request for help in the openstack-dev list either. Hopefully, with a bit of insistence, someone will help.
Keystone migration to Testing (aka: Debian Stretch) blocked by python-repoze.who
Absolutely all of OpenStack Liberty, as of today, has migrated to Stretch. All? No. Keystone is blocked by a chain of dependency. Keystone depends on python-pysaml2, itself blocked by python-repoze.who. The later, I upgraded it to version 2.2. Though python-repoze.what depends on version <= 1.9, which is blocking the migration. Since python-repoze.who-plugins, python-repoze.what and python-repoze.what-plugins aren t used by any package anymore, I asked for them to be removed from Debian (see #805407). Until this request is processed by the FTP masters, Keystone, which is the most important piece of OpenStack (it does the authentication) will be blocked for migration to Stretch.
New OpenStack server packages available
On my presentation at Debconf 15, I quickly introduced new services which were released upstream. I have since packaged them all:
Barbican (Key management as a Service)
Congress (Policy as a Service)
Magnum (Container as a Service)
Manila (Filesystem share as a Service)
Mistral (Workflow as a Service)
Zaqar (Queuing as a Service)
Congress, unfortunately, was not accepted to Sid yet, because of some licensing issues, especially with the doc of python-pulp. I will correct this (remove the non-free files) and reattempt an upload.
I hope to make them all available in jessie-backports (see below). For the previous release of OpenStack (ie: Kilo), I skipped the uploads of services which I thought were not really critical (like Ironic, Designate and more). But from the feedback of users, they would really like to have them all available. So this time, I will upload them all to the official jessie-backports repository.
Keystone v3 support
For those who don t know about it, Keystone API v3 means that, on top of the users and tenant, there s a new entity called a domain . All of the Liberty is now coming with Keystone v3 support. This includes the automated Keystone catalog registration done using debconf for all *-api packages. As much as I could tell by running tempest on my CI, everything still works pretty well. In fact, Liberty is, to my experience, the first release of OpenStack to support Keystone API v3.
Uploading Liberty to jessie-backports
I have rebuilt all of Liberty for jessie-backports on my laptop using sbuild. This is more than 150 packages (166 packages currently). It took me about 3 days to rebuild them all, including unit tests run at build time. As soon as #805407 is closed by the FTP masters, all what s remaining will be available in Stretch (mostly Keystone), and the upload will be possible. As there will be a lot of NEW packages (from the point of view of backports), I do expect that the approval will take some time. Also, I have to warn the original maintainers of the packages that I don t maintain (for example, those maintained within the DPMT), that because of the big number of packages, I will not be able to process the usual communication to tell that I m uploading to backports. However, here s the list of package. If you see one that you maintain, and that you wish to upload the backport by yourself, please let me know. Here s the list of packages, hopefully, exhaustive, that I will upload to jessie-backports, and that I don t maintain myself:
alabaster contextlib2 kazoo python-cachetools python-cffi python-cliff python-crank python-ddt python-docker python-eventlet python-git python-gitdb python-hypothesis python-ldap3 python-mock python-mysqldb python-pathlib python-repoze.who python-setuptools python-smmap python-unicodecsv python-urllib3 requests routes ryu sphinx sqlalchemy turbogears2 unittest2 zzzeeksphinx.
More than ever, I wish I could just upload these to a PPA^W Bikeshed, to minimize the disruption for both the backports FTP masters, other maintainers, and our OpenStack users. Hopefully, Bikesheds will be available soon. I am sorry to give that much approval work to the backports FTP masters, however, using the latest stable system with the latest release, is what most OpenStack users really want to do. All other major distributions have specific repositories too (ie: RDO for CentOS / Red Hat, and cloud archive for Ubuntu), and stable-backports is currently the only place where I can upload support for the Stable release.
Debian listed as supported distribution on openstack.org
Good news! If you go at http://www.openstack.org/marketplace/distros/ you will see a list of supported distributions. I am proud to be able to tell that, after 6 months of lobbying from my side, Debian is also listed there. The process of having Debian there included talking with folks from the OpenStack foundation, and having Bdale to sign an agreement so that the Debian logo could be reproduced on openstack.org. Thanks to Bdale Garbee, Neil McGovern, Jonathan Brice, and Danny Carreno, without who this wouldn t have happen.
Patches submitted which have not made their way to the archive yet:
#797027 on zyne by Chris Lamb: switch to pybuild to get rid of .pyc files.
#797180 on python-doit by Chris Lamb: sort output when creating completion script for bash and zsh.
#797211 on apt-dater by Chris Lamb: fix implementation of SOURCE_DATE_EPOCH.
#797215 on getdns by Chris Lamb: fix call to dpkg-parsechangelog in debian/rules.
#797254 on splint by Chris Lamb: support SOURCE_DATE_EPOCH for version string.
#797296 on shiro by Chris Lamb: remove username from build string.
#797408 on splitpatch by Reiner Herrmann: use SOURCE_DATE_EPOCH to set manpage date.
#797410 on eigenbase-farrago by Reiner Herrmann: sets the comment style to scm-safe which tells ResourceGen that no timestamps should be included.
#797415 on apparmor by Reiner Herrmann: sorting with the locale set to C. CAPABILITIES
#797419 on resiprocate by Reiner Herrmann: set the embedded hostname to a static value.
#797427 on jam by Reiner Herrmann: sorting with the locale set to C.
#797430 on ii-esu by Reiner Herrmann: sort source list using C locale.
#797431 on tatan by Reiner Herrmann: sort source list using C locale.
Chris Lamb also noticed that binaries shipped with libsilo-bindid not work.
Documentation update
Chris Lamb and Ximin Luo assembled a proper specification for SOURCE_DATE_EPOCH in the hope to convince more upstreams to adopt it. Thanks to Holger it is published under a non-Debian domain name.
Lunar documented easiest way to solve issues with file ordering and timestamps in tarballs that came with tar/1.28-1.
Some examples on how to use SOURCE_DATE_EPOCH have been improved to support systems without GNU date.
reproducible.debian.net
armhf is finally being tested, which also means the remote building of Debian packages finally works! This paves the way to perform the tests on even more architectures and doing variations on CPU and date. Some packages even produce the same binary Arch:all packages on different architectures (1, 2). (h01ger)
Tests for FreeBSD are finally running. (h01ger)
As it seems the gcc5 transition has cooled off, we schedule sid more often than testing again on amd64. (h01ger)
disorderfs has been built and installed on all build nodes (amd64 and armhf). One issue related to permissions for root and unpriviliged users needs to be solved before disorderfs can be used on reproducible.debian.net. (h01ger)
strip-nondeterminism
Version 0.011-1 has been released on August 29th. The new version updates dh_strip_nondeterminism to match recent changes in debhelper. (Andrew Ayer)
disorderfs
disorderfs, the new FUSE filesystem to ease testing of filesystem-related variations, is now almost ready to be used. Version 0.2.0 adds support for extended attributes. Since then Andrew Ayer also added support to reverse directory entries instead of shuffling them, and arbitrary padding to the number of blocks used by files.
Package reviews
142 reviews have
been removed, 48 added and 259 updated this week.
Santiago Vila renamed the not_using_dh_builddeb issue into varying_mtimes_in_data_tar_gz_or_control_tar_gz to align better with other tag names.
New issue identified this week: random_order_in_python_doit_completion.
37 FTBFS issues have been reported by Chris West (Faux) and Chris Lamb.
Misc.
h01ger gave a talk at FrOSCon on August 23rd. Recordings are already online.
These reports are being reviewed and enhanced every week by many people hanging out on #debian-reproducible. Huge thanks!
I tried to start to write this blog entry like I usually do: Type along what goes through my mind and see where I'm heading. This won't work out right now for various reasons, mostly because there is so much going on that I don't have the time to finish that in a reasonable time and I want to publish this today still. So please excuse me for being way more brief than I usually am, and hopefully I'll find the time to expand some things when asked or come back to that later.
Part of the reason of me being short on time is different stuff going on in my private life which requires additional attention. A small part of this is also something that I hinted in a former blog entry: I switched my job in June. I really was looking forward to this. I made them aware of what the name Rhonda means to me and it's definitely extremely nice to be addressed with female pronouns at work. And also I'm back in a system administration job which means there is an interest overlap with my work on Debian, so a win-win situation on sooo many levels!
I'm at DebConf15 since almost two weeks now. On my way here I was complimented on my outfit by a security guard at the Vienna airport which surprised me but definitely made my day. I was wearing one of these baggy hippie pants (which was sent to me by a fine lady I met at MiniDebConf Bucharest) but pulled up the leg parts to the knees so it could be perceived as a skirt instead. Since I came here I was pretty busy with taking care of DCschedule bot adjustments (like, changing topic and twittering from @DebConf at the start of the talks), helping out with the video team when I noticed there was a lack of people (which is a hint for that you might want to help with the video team in the future too, it's important for remote people but also for yourself because you can't attend multiple sessions at the same time).
And I have to repeat myself, this is the place I feel home amongst my extended family, even though I it still is sometimes for me to get to speak up in certain groups. I though believe it's more an issue of certain individuals taking up a lot of space in discussions without giving (more shy) people in the round the space to also join in. I guess it might be the time that we need a session on dominant talking patterns for next year and how to work against them. I absolutely enjoyed such a session during last year's FemCamp in Vienna which set the tone for the rest of the conference, and it was simply great.
And then there was the DebConf Poetry Night. I'm kinda disappointed with the outcome this year. It wasn't able to attract as much people anticipated, which I to some degree account to me not making people aware of it well enough, overlapping with a really great band playing at the same time in competition, and even though the place where we did it sounded like a good idea at first, it didn't had enough light for someone to read something from a book (but that was solved through smartphone lights). I know that most people did enjoy it, so it was good to do it, but I'm still a fair bit disappointed with the outcome and will try to work on improving on that grounds for next year. :)
With all this going on there unfortunately wasn't as much time as I would have liked to spend with people I haven't seen for a long time, or new people I haven't met yet. Given that this year's DebConf had an height in attendees (526 being here at certain times during the two weeks, and just today someone new arrived too, so that doesn't even have to be the final number) it makes it a bit painful to have picked up so many tasks and thus lost some chances to socialize as much as I would have liked to.
So, if you are still here and have the feeling we should have talked more, please look for me. As Bdale pointed out correctly in the New to DebConf BoF (paraphrased): When you see us DebConf old timers speaking to someone else and you feel like you don't want to disturb, please do disturb and speak to us. I always enjoyed to get to know new people. This for me always is one of the important aspects of DebConf.
Also, I am very very happy to have received feedback from different people about both my tweets and my blog, thank you a lot of that. It is really motivating to keep going.
So, lets enjoy the last few hours of DebConf!
Another last side notice: While my old name in the Debian LDAP did manage to find some wrongly displayed names in the DebConf website, like for speakers, or volunteers, it was clear to me that having it exposed through SSO.debian.org isn't really something I appreciate. So I took the chance and spoke to Luca from the DSA team right here today, and ... got it fixed. I love it! Next step is getting my gpg key exchanged, RT ticket is coming up. :)
This year, on top of the many excellent contributed talks, BoFs, and other
events always part of DebConf (some of which have already been announced) we
are excited to have confirmed the following keynote speakers.
During the Open Weekend (Saturday, August 15th and Sunday, August 16th), we
will have keynotes delivered by:
Bradley M. Kuhn,
President, Software Freedom Conservancy / Board of Directors, Free Software Foundation
(Wikipedia page)
Werner Koch,
Creator and Lead Developer, GnuPG Project / g10 Code GmbH
(Wikipedia page)
Bdale Garbee,
Chief Technologist Open Source and Linux, HP / Debian Project
(Wikipedia page)
On the last day of DebConf, we look forward to the closing keynote by:
Jacob Appelbaum,
Security Researcher and Journalist / Tor Project
(Wikipedia page)
For more information about our invited speakers, please see
http://debconf15.debconf.org/invited_speakers.xhtml
Citizenfour Screening
Additionally, there will be a screening of the
Citizenfour movie,
winner of the Best Documentary Feature Academy Award on the evening of Friday,
August 21st.
You still have time to submit your talk
There are only a few days left before the end of the Call for Proposals on June
15th. Events submitted after that date might not be part of the official
DebConf schedule. So, please, hurry, check out the
proposal submission guide
and submit your event.
Regards from the DebConf Team
Notice: There were several requests for me to more elaborate on my path to Debian and impact on life so here it is. It's going to be a bit long so anyone who isn't interested in my personal Debian journey should skip it. :)
In 2007. I enrolled into Faculty of Mechanical Engineering (at first at Department of Industrial Management and later transfered to Department of Mechatronics - this was possible because first 3 semesters are same for both departments). By the end of same year I was finishing my tasks (consisting primarily of calculations, some small graphical designs and write-ups) when famous virus, called by users "RECYCLER", sent my Windows XP machine into oblivion. Not only it took control over machine and just spawned so many processes that system would crash itself, it actually deleted all from hard-disk before it killed the system entirely. I raged - my month old work, full of precise calculations and a lot of design details, was just gone. I started cursing which was always continued with weeping: "Why isn't there an OS that can whithstand all of viruses, even if it looks like old DOS!". At that time, my roommate was my cousin who had used Kubuntu in past and currently was having SUSE dual-booted on his laptop. He called me over, started talking about this thing called Linux and how it's different but de facto has no viruses. Well, show me this Linux and my thought was, it's probably so ancient and not used that it probably looks like from pre Windows 3.1 era, but when SUSE booted up it had so much more beautiful UI look (it was KDE, and compared to XP it looked like the most professional OS ever).
So I was thrilled, installed openSUSE, found some rough edges (I knew immediately that my work with professional CAD systems will not be possible on Linux machines) but overall I was bought. After that he even talked to me about distros. Wait, WTF distros?! So, he showed me distrowatch.com. I was amazed. There is not only a better OS then Windows - there where dozens, hundreds of them. After some poking around I installed Debian KDE - and it felt great, working better then openSUSE but now I was as most newbies, on fire to try more distros. So I was going around with Fedora, Mandriva, CentOS, Ubuntu, Mint, PCLinuxOS and in beginning of 2008 I stumbled upon Debian docs which where talking about GNU and GNU Manifesto. To be clear, I was always as a high-school kid very much attached to idea of freedom but started loosing faith by faculty time (Internet was still not taking too much of time here, youth still spent most of the day outside). So the GNU Manifesto was really a big thing for me and Debian is a social bastion of freedom. Debian (now with GNOME2) was being installed on my machine.
As all that hackerdom in Debian was around I started trying to dig up some code. I never ever read a book on coding (until this day I still didn't start and finish one) so after a few days I decided to code tetris in C++ with thought that I will finish it in two days at most (the feeling that you are powerful and very bright person) - I ended it after one month in much pain. So instead I learned about keeping Debian system going on, and exploring some new packages. I got thrilled over radiotray, slimvolley (even held a tournament in my dorm room), started helping on #debian, was very active in conversation with others about Debian and even installed it on few laptops (I became de facto technical support for users of those laptops :D ).
Then came 2010 which with negative flow that came in second half of 2009, started to crush me badly. I was promised to go to Norway, getting my studies on robotics and professor lied (that same professor is still on faculty even after he was caught in big corruption scandal over buying robots - he bought 15 years old robots from UK, although he got money from Norway to buy new ones). My relationship came to hard end and had big emotional impact on me. I fell a year on faculty. My father stopped financing me and stopped talking to me. My depression came back. Alcohol took over me. I was drunk every day just not to feel anything. Then came the end of 2010, I somehow got to the information that DebConf will be in Banja Luka. WHAT?! DebConf in city where I live. I got into #debconf and in December 2010/January 2011 I became part of the famous "local local organizers". I was still getting hammered by alcohol but at least I was getting out of depression. IIRC I met Holger and Moray in May, had a great day (a drop of rakia that was too much for all of us) and by their way of behaving there was something strange. Beatiful but strange. Both were sending unique energy of liberty although I am not sure they were aware of it. Later, during DebConf I felt that energy from almost all Debian people, which I can't explain. I don't feel it today - not because it's not there, it's because I think I integrated so much into Debian community that it's now a natural feeling which people here, that are close to me are saying that they feel it when I talk about Debian.
DebConf time in Banja Luka was awesome - firstly I met Phil Hands and Andrew McMillan which were a crazy team, local local team was working hard (I even threw up during the work in Banski Dvor because of all heat and probably not much of sleep due to excitement), met also crazy Mexican Gunnar (aren't all Mexicans crazy?), played Mao (never again, thank you), was hanging around smart but crazy people (love all) from which I must notice Nattie (a bastion of positive energy), Christian Perrier (which had coordinated our Serbian translation effort), Steve Langasek (which asked me to find physiotherapist for his co-worker Mathias Klose, IIRC), Zach (not at all important guy at that time), Luca Capello (who gifted me a swirl on my birthday) and so many others that this would be a post for itself just naming them. During DebConf it was also a bit of hard time - my grandfather died on 6th July and I couldn't attend the funeral so I was still having that sadness in my heart, and Darjan Prtic, a local team member that came from Vienna, committed suicide on my birthday (23 July). But DebConf as conference was great, but more importantly the Debian community felt like a family and Meike Reichle told me that it was. The night it finished, me and Vedran Novakovic cried. A lot. Even days after, I was getting up in the morning having the feeling I need something to do for DebConf. After a long time I felt alive. By the end of year, I adopted package from Clint Adams and Moray became my sponsor. In last quarter of 2011 and beginning of 2012, I (as part of LUG) held talks about Linux, had Linux installation in Computer Center for the first time ever, and installed Debian on more machines.
Now fast forwarding with some details - I was also on DebConf13 in Switzerland, met some great new friends such as Tincho and Santiago (and many many more), Santiago was also my roommate in Portland on the previous DebConf. In Switzerland I had really great and awesome time. Year 2014 - I was also at DebConf14, maintain a bit more packages and have applied for DD, met some new friends among which I must put out Apollon Oikonomopoulos and Costas Drogos which friendship is already deep for such a short time and I already know that they are life-long friends. Also thanks to Steve Langasek, because without his help I wouldn't be in Portland with my family and he also gave me Arduino. :) 2015. - I am currently at my village residence, have a 5 years of working experince as developer due to Debian and still a lot to go, learn and do but my love towards Debian community is by magnitude bigger then when I thought I love it at most. I am also going through my personal evolution and people from Debian showed me to fight for what you care, so I plan to do so.
I can't write all and name all the people that I met, and believe me when I say that I remember most and all of you impacted my life for which I am eternally grateful. Debian, and it's community effect literally saved my life, spring new energy into me and changed me for better. Debian social impact is far bigger then technical, and when you know that Debian is a bastion of technical excellence - you can maybe picture the greatness of Debian. Some of greatest minds are in Debian but most important isn't the sheer amount of knowledge but the enormous empathy. I just hope I can in future show to more people what Debian is and to find all lost souls as me to give them the hope, to show them that we can make world a better place and that everyone is capable to live and do what they love.
P.S. I am still hoping and waiting to see Bdale writing a book about Debian's history to this day - in which I think many of us would admire the work done by project members, laugh about many situations and have fun reading a book about project that was having nothing to do but fail and yet it stands stronger then ever with roots deep into our minds.
AltOS 1.6 TeleDongle v3.0 support and bug fixes
Bdale and I are pleased to announce the release of
AltOS version 1.6.
AltOS is the core of the software
for all of the Altus Metrum products. It
consists of firmware for our cc1111, STM32L151, STMF042, LPC11U14 and ATtiny85
based electronics and Java-based ground station software.
This is a major release of AltOS, including support for our new
TeleDongle v3.0 board and a selection
of bug fixes
AltOS Firmware TeleDongle v3.0 added along with some fixes
Our updated ground station, TeleDongle v3.0,
works just like the original TeleDongle, but is an all-new design:
CC1200 radio chip is about 5dB more sensitive than TeleDongle's CC1111.
LPC11U14 CPU can be reprogrammed over the USB link.
AltOS Bug Fixes
We also fixed a few bugs in the firmware:
Make sure the startup flight computer beeps are
consistent. Sometimes, it was taking long enough to beep out the
battery voltage that the flight computer state was changing in the
middle, causing a bit of confusion.
Change TeleDongle's LED indicators during telemetry
reception. The green LED blinks on successful packet
reception, and the red LED blinks when a packet with an invalid
checksum is received.
The SPI driver used in both TeleDongle v3 and TeleGPS has been
rewritten to avoid locking up under heavy CPU load. If you've got a
TeleGPS board, you'll want to reflash with new firmware.
AltosUI and TeleGPS applications
A few minor new features are in this release
AltosUI can now compute and display tilt angle when graphing eeprom
log data from TeleMega and EasyMega.
The AltosUI tool window is shown when starting with a data
file. This way, when you double-click on a file in the file
manager, you'll get the whole AltosUI interface, rather than just
the graphing window.
At the end of replaying an old log file, stick 'done' in the Age
field so you can tell the recording is over.
Bug Fixes
There are a bunch of minor bug fixes, including the usual collection
of attempts to make stuff behave better on Windows platforms.
Use a different Windows API to discover USB device ids. This works
better on my new HP Windows 7 machine. Maybe it will work better
for other people too?
Look in more places in the Windows registry to try and find the
installed Java version. It appears that the default Java download
from Oracle is a 32-bit version? In any case, that version sticks
its install information in a different spot in the registry.
Fix file associations on Windows when Java isn't installed in the
system root.
Make 'Scan Channels' work better with new AltOS firmware which only
reports device configuration information once ever five seconds.