tags/debianbloghttp://blog.spang.cc/tags/debian/blogikiwiki2011-03-18T22:45:03Zon transparencyhttp://blog.spang.cc/posts/on_transparency/2011-03-18T22:45:03Z2011-03-18T22:45:03Z
<p>I found the following quote from Stefano's <acronym title="Debian
Project Leader">DPL</acronym>
<a href="http://www.debian.org/vote/2011/platforms/zack">platform</a> interesting:</p>
<blockquote><p>When faced with the dilemma, I've favored ditching some DPL tasks
and communicating or taking notes about the others, instead of the
other way around.</p></blockquote>
<p>It takes someone who really knows Debian to realize that sometimes
communicating about what's being done is more important than doing more.</p>
RC bug squashinghttp://blog.spang.cc/posts/RC_bug_squashing/Christine Spang2010-06-27T04:11:55Z2010-06-27T04:01:39Z
<p>Inspired by various Planet Debian postings, I've spent some time
recently looking into a few RC bugs to help with the Squeeze release.</p>
<p><strong><a href="http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=581227">mpg123-el #581227</a></strong> A
previous commenter on this bug suggested a proposed fix, which I tested
and uploaded. I think the bug's severity was inflated to begin with, so
I downgraded the bug as well.</p>
<p><strong><a href="http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=580246">doclifter #580246</a></strong> This
one had to do with the python2.6 transition. I
pointed out a patch against Ubuntu's version of the package that fixes
this problem, and someone else made an NMU based on that. (Seemed like a
good idea to look in the PTS for Ubuntu patches since Ubuntu always
transitions to newer Python before Debian proper.)</p>
<p><strong><a href="http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=580110">gnuvd #580110</a></strong> I
checked upstream and a new version that's supposed to fix this bug was
released <em>today</em>, so I updated the bug report to make note of this and
give the maintainer a chance to look at it.</p>
<p><strong><a href="http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=583820">libtommath #583820</a></strong> This
FTBFS bug was caused by a previous NMU that fixed a different FTBFS and
also made some unrelated changes. I sent a message to the previous NMUer
noting this fact and made a new upload fixing the new FTBFS.</p>
<p><strong><a href="http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=580820">fceu #580820</a></strong> Needs
new upstream packaged to fix. The maintainer seems pseudo-MIA but has
shown some signs of returning to activity; I sent an email inquiring as
to whether he intends to fix the critical issue in this package.</p>
<p><strong><a href="http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=571427">op-panel #582377 and #571427</a></strong>
These were not merged when I started out, so I merged them after
noticing they were the same. I spent some poking at the bug itself and
made a simple patch, only to find out that there was a pending patch in
pkg-voip's subversion repo. I hopped onto #debian-voip to prod the
person who'd prepared the patch in subversion about the importance of
updating the BTS when working on bugs. These bugs are currently blocking
on testing the patch.</p>
<p>Most all of these bugs I've subscribed to in case of follow-up. (Geez,
challenge-response subscription via email is kind of a pain.)</p>
is your keysigning offer up to date?http://blog.spang.cc/posts/is_your_keysigning_offer_up_to_date__63__/Christine Spang2010-04-03T02:48:23Z2010-04-03T02:48:23Z
<p>I occasionally get emails from people looking for GPG keysigning around
the Boston area, addressed to all the local Debian Developers on the
<a href="http://wiki.debian.org/Keysigning/Offers">keysigning offers list</a>.
Generally, I'm the only one who replies to them, despite there being
four or so other people addressed. I wonder if this problem pervades
other locations as well.</p>
<p>Keysigning is one of the hurdles every person interested in becoming a
full Debian Developer must overcome. The New Maintainer process is a
hurdle enough in itself! Let's try not to discourage excited newcomers
who are <em>already convinced that they want to help Debian</em>
by leaving them hanging for long periods of time trying to get their key
signed.</p>
<p>Have you moved? Are you no longer interested in filling keysigning
requests? (I suspect many of those who would answer "yes" to that
question are actually inactive, and so are unlikely to actually see
this.) Are you interested in filling keysigning requests but didn't know
about the offers list? Go to the
<a href="http://wiki.debian.org/Keysigning/Offers">keysigning offers list on the Debian wiki</a>
and update, add, or remove your information. There's also the
<a href="http://wiki.debian.org/Keysigning/Need">list of people requesting keysigning</a>—you
can subscribe to this page to see updates.</p>