Rob Taylor: PackageKit Stop Energy
This should be a reply on Hughsies blog, but I don’t want to create a livejournal account. Richard, please move to blogs.gnome.org!
In response to Jason’s comments:
Hey. I’m a Debian/Ubuntu kinda guy and I think PackageKit is a hell of a lot better than Ubuntu making ubuntu-only solutions like gnome-app-install. It’s DEFINITELY not a NIH, there was nothing that gave us this kind of capability at all before PackageKit started. Everyone knew what was needed to be written and Richard was the guy that jumped in and got it started.
Also Richard wasn’t working at Red Hat when he started PackageKit and has worked with every distro he can on this.
Jason, stop the Stop Energy.
Update:
I though I might jump in and say a bit more on this problem: It really comes down to the question of whether a backend should ask questions of the user. Richard thinks that they shouldn’t, mainly because every time he’s seen backends ask questions they aren’t ones he knows the answer to and so, by inference, most people don’t know the answer to. These questions shouldn’t be asked in a user-friendly system.
However ‘These questions’ are actually multiple classes of problems and simplistically dismissing these is really just asking for failure in solving the problems correctly. Before I go any further, let me note that debconf has multiple levels of verbosity that it can ask questions at. Most Debian based distros just ask the highest priority questions. It should be noted that a PackageKit backend should allow a central administrator to set default values for any of these setting however. Lets break down some of the kind of questions asked though debconf:
So the question really comes down to asking the user sensible questions that they a) know how to answer and b) care about.
The point I made to Richard on IRC is that this is actually a difficult and multi-faceted problem and just hiding these problems won’t help in solving them well, so my take is that PackageKit should allow asking of questions, probably via a dbus interface, have a debconf frontend that channels questions by this channel, and then let the Ubuntu and Debian guys get on the case of forming projects and policy to help fix the problem at source.
Update 2:Richard pointed me to this FAQ entry which explains why even handling debconf questions is hard.
I though I might jump in and say a bit more on this problem: It really comes down to the question of whether a backend should ask questions of the user. Richard thinks that they shouldn’t, mainly because every time he’s seen backends ask questions they aren’t ones he knows the answer to and so, by inference, most people don’t know the answer to. These questions shouldn’t be asked in a user-friendly system.
However ‘These questions’ are actually multiple classes of problems and simplistically dismissing these is really just asking for failure in solving the problems correctly. Before I go any further, let me note that debconf has multiple levels of verbosity that it can ask questions at. Most Debian based distros just ask the highest priority questions. It should be noted that a PackageKit backend should allow a central administrator to set default values for any of these setting however. Lets break down some of the kind of questions asked though debconf:
- Configuration file overwrites
- License agreements (cf suns jdk packages, flashplugin-nonfree, etc)
- Technical questions, like whether to start a daemon or not
- Lots of other things?…


Of course, this post is about the results for the recent 

These graphs can help give some idea of how the shortened DPL voting period
this year changed voting patterns.
Each vote starts on a Sunday (except 2005 which was a day late). Calls for
votes are posted again each weekend during the vote, and a final call two
days before the end of the vote. These are responsible for most of the
spikes on the graph, and the trail off after each CFV is probably due to
some people seeing it the next day.
Shortening the voting period seems to have made more people respond to
the second and third CFV (both in percentage and absolute number of
voters). It's also interesting that a smaller percent than usual of votes
were recieved on the last day this year. There seems to not have been a
rush to vote on the last day despite the shortened period.
I wonder if posting CFVs more frequently would result in more voters, or
if it would just level off the graph?
(Graph produced using
There have been a number of discussions on sane-devel in the past months revolving around the SANE2 standard (still in development) and/or extensions to the current SANE1 standard. SANE2 is an effort that has been “ongoing” (on and off, mostly off, unfortunately) for a number of years already.
This led to a number of questions being raised, most notably this one: do we need SANE2, or can we get away only with extensions to SANE1? Or should we just redesign the whole stack from the ground up?
First of all, congratulations Steve!
It's a bit strange. Still. Writing this personal part of my blog, opening some of my most inner thoughts to the wild public. Though, so wild it doesn't seem to be. To be honest I can't remember having received any bad feedback on my personal stuff, only positive, supportive ones. (Or, there was one. Though, it wasn't related to the core of the personal section but someone thinking it would be "cool" to misinterpret some statement therein and try to hurt me with it. It only made me laugh at them, trying to "use" it as an argument.)
I'm pretty impressed with the new 
Steve Kemp holds the opinion that "
If you upload a new package to the Debian archive which contains a setuid or setgid binary please please ask for a security audit, or carry out one yourself.
I certainly accept that the
We escorted Sarge to its last home. 3.1r8 is done, thanks to all the
people who made it possible. A big thanks goes to James Troup, our
ftpmaster of the day doing all the grunt work of getting a new point
release out of the door.
To bring in a more personal feeling of who makes this all possible,
here is a list of people contributing uploads to 3.1r8 (mostly
people from our fabulous Security Team):
