Search Results: "ag"

29 January 2008

David Welton: Munich Android Mobile Meeting Report

I'm a bit tired after driving up to Munich for the Android developer meeting, hosted by Google, and being "on" all day, but it was worth it. I was a bit apprehensive that it might be too 'introductory' in the sense of the Google guys telling you in person things that you could have easily looked up on the web, without spending a bunch of time driving around Austria and Bavaria. Fortunately, that wasn't the case. There was some of that, but also plenty of unstructured time to chat with Dan Morrill and Jason Chen, the two Google "Developer Advocates", who are both very friendly, informative and informed, approachable and put a lot of energy into what they do, despite being a bit tired from flying over from the US. It was nice to get a chance to talk with them, and considering that the platform is still changing, useful as well, because they were definitely listening to what people had to say to them. My thanks to them for a job well done. Here are some "impressions" I took away - note that they're not what anyone said, just ideas I got about what they said: There's still really a sense of Android continuing to evolve, in a true spirit of openness. I liked that, as it means there is space for people to tell Google what they want, rather than simply being given a finished product and told that that's that... but then again, I would, being the open source guy that I am. I didn't get to show off Hecl quite as much as I would have liked to, but I did get to mention it a few times, so I guess I did ok.

Christian Perrier: Want people to stop at your Debian booth?

...install a Babelbox, de-activate the "db_info babelbox/info" line in preseed_early and put the following in big capitals on a sheet of paper attached to the monitor:
BABELBOX CONTEST
Guess what language is used to install
that Debian system.
...and wait for the crowd to slowly gather around the box and start guessing. If you can offer stickers pins CDs to winners, that's even better. Hint: do not activate easy to guess languages. Good candidates (apart from all non Latin ones which are all *very* hard to recognize for the regular French geek, except maybe Japanese) are Hungarian, Basque, Slovenian. Arabic is too easy to recognize and so is Greek. Indic languages are a great success but Dzongkha is generally the winner. Hint 2: do not sort languages alphabetically by locales. Geeks are too smart and the geeks manning the booth will learn too quickly. Watch also people trying to switch to a console during the D-I runs and typing "cat /proc/cmdline". Hint 3: train yourself to recognize the languages before the contest so that you look clever... That worked pretty well during 1st day of Solutions Linux.

Norbert Tretkowski: No need to hurry for MySQL 5.0.51a in Debian

MySQL 5.0.51a was released today, which is a security hotfix release without any new features compared with 5.0.51. It fixes CVE-2007-6303, CVE-2007-6304, CVE-2008-0226 and CVE-2008-0227. These problems are already fixed in Debian with 5.0.32-7etch4 and 5.0.32-7etch5 for stable and 5.0.45-5 and 5.0.51-3 for unstable using the patches from MySQL, hence no need to write bugreports against the MySQL packages asking for an update to 5.0.51a.

We will update to 5.0.51a anyway with the next upload, but there's no need to hurry.

Maximilian Attems: 2.6.24 in Sid

2.6.24 has been uploaded on Saturday and passed NEW on Monday. It will be soonest available for all archs. If we don't get enough test coverage or things go bad 2.6.22 will be the fallback for Etch+half. The images install in Lenny/testing just fine. So please give it a spin. Known Issues are still missing VServer and Xen images, bnx2 + snd-cs46xx disabled due to firmware issue and ACPI userland still relying on old interfaces (for example #462305). For more adventurous souls the kernel buildserver will continue to track latest Linus git daily snapshot (enhanced ext4 should land soon). 2.6.24 will also soon be pushed to Testing. I repeat this is not the real Etch+half kernel yet as there will be some config changes for it, but it is pretty close. Thanks for your 2.6.24-rc7 feedback.

Simon Richter: Milestone 0.9

The not-yet-so-mighty project build tool I'm writing (codenamed "dammit") just compiled itself for the first time (took 40 seconds :-P ). It is probably not that usable yet, as it lacks dependency checking and thus always recompiles everything -- fixing that is the plan for tonight. So far, all it does is compile everything it can find and recognise in a directory and link it to a program; the plan for the future is not to add too much to that, mainly new project types like libraries and new input languages.

Kartik Mistry: KDE-gu is ~there~

* Thanks to Albert (aacid) for committing first Gujarati (gu) translation file for KDE. Time for hard and quick work now! Also, feel free to join me!! * I am at Ahemdabad for at least week from today. If LUG here is alive then, there is plan for a meet, but before that I need to fix bugs in my teeth :(

Stefano Zacchiroli: pts dehs integration

PTS now sports DEHS information During the last week I've started again doing some PTS hacking. Mostly it has been bug triaging and squashing ... I'll probably blog a summary of that sooner or later. In the meantime however an interesting mini-announcement is due: the PTS is now integrated with DEHS to help maintainers in knowing where a newer upstream version of their packages is available. The integration is twofold:
  1. if you are subscribed (via the PTS mail interface) to the "summary" keyword for a given package you will be notified of the availability of newer upstream versions. Kudos to Raphael Geissert for the work on the DEHS side of this
  2. in the PTS page related to a given source package you can now see a TODO item about the need to package a newer upstream version and a problem item if the last uscan attempt on your package failed
There is an entry about that in the forthcoming DeveloperNews, it will eventually flow to d-d-a.

28 January 2008

Martin F. Krafft: Consolidating packaging workflows across distros

I speculate that most of what we do for Debian squares with what others do for their respective distro. Thus, it should be possible to identify a conceptual workflow applicable to all distros, consolidate individual workflows on a per-package basis, and profit from each other. Jonathan let me have the after-afternoon-coffee slot of the Distro Summit for an impromptu discussion on the various workflows used by distros for packaging. The discussion round was very short-notice and despite the announcement sent to the conference mailing list, only ten people showed up: two people familiar with Fedora, and ( versus ) eight Debianites. Regardless, I think the discussion was success- and fruitful. We were able to identify a one-to-one mapping between the Fedora and Debian workflows, even though we use different techniques: Many Debian package maintainers use version control systems to maintain the ./debian directory, and if patch files are stored in ./debian/patches/, then Debian and Fedora both store patch files in a version control repository, which seems awful. Just as I am only one of many who are experimenting with VCS-based workflows for Debian packaging, the Fedora people are also considering the use of version control for packaging. Unlike Fedora, who seem to try to standardise on bzr, I try to cater for the plethora of version control systems in use in Debian, anticipating the impossibility of standardising/converging on a single tool across the entire project. It seems that our two projects are both at the start of a new phase in packaging, a paradigm shift . What better time could there be for us to listen to each other and come up with a workflow that works for both projects? My suggestion currently centres around a common repository for each package across all (participating) distros, and feature branches. Specifically, given an upstream source tree, modifications made during packaging for a given distro fall into four categories: Given a version control system with sufficient branching support, I imagine having different namespaces for branches: upstream-patches/*, distro/*, rpm/* or debian/*. Now, when building the Debian package, I d apply upstream-patches/*, distro/*, deb/* and debian/* in order, while my colleague from the Fedora project would apply upstream-patches/*, distro/*, rpm/* and fedora/*, before calling the build tools and uploading the package. There are surely problems to be overcome. Pascal Hakim mentioned patch dependencies, and I can t necessarily say with a clear conscience that my workflow isn t too complicated to be unleashed into the public yet. But if we find a conceptual workflow applicable to more than one distro, it should be possible to implement a higher-level tool to implement it. Also, the above is basically patch maintenance, not the entire workflow. Bug tracking system integration is going to play a role, as well as other aspects of daily distro packaging. I ll leave those for future time. For me, this is the start of a potentially fruitful cooperation and I hope that interested parties from other distros jump on. For now, I suggest my mailing list for discussion. You can also find some links on the Debian wiki.

Ian Wienand: A cool laptop

Or, a modern guide to CPU frequency scaling with Linux. Having setup my laptop long ago, I had a strange hybrid of daemons running all trying to scale the frequency of my laptop periodically based on a myriad of different situations. Having decided to fix this, it appears the simplest approach is, as usual, the best. The way of the future appears to be to let the kernel do all the work with the ondemand govener. The cpufrequtils Debian package will arrange this for you on boot and by default should just work, although you can of course tweak parameters like minimum speed to decrease to and so forth. You can use the cpufreq-set utility to fiddle with settings, or just go into /sys/devices/system/cpu/cpuN/cpufreq/ to tweak them by hand. The many available daemons (cpufreqd, powernowd, etc.) appear to be largely redundant and are probably best removed. This dropped the temperature of my laptop about 10 degrees C and, apart from a much cooler lap, is so far imperceptible.

Colin Watson: UTF-8 manual pages

See Encodings in man-db for context. Yesterday, I uploaded man-db 2.5.1-1 to unstable. With this version, not only is it possible to install manual pages in UTF-8 (as with 2.5.0, although with fewer bugs), but it's also possible to ask man to produce a version of an arbitrary page in the encoding of your choice, and have it guess the source encoding for you fairly reliably. This finally provides enough support to have debhelper automatically recode manual pages to UTF-8. It'll probably take a little while to shake out the corner-case bugs, but I'm generally pretty happy with this. Once the new man-db and debhelper land in testing, I'll send a note to debian-devel-announce and push harder on my policy amendment. Considering the historical state of man-db when it comes to localisation, and all of the dependencies and general yak-shaving that had to be tackled to get here, this represents the end of probably several hundred hours of work, so I'm pretty happy that this is out the door. The only remaining step is to add UTF-8 input support to groff, which fortunately Brian M. Carlson is working on. After that, we can reasonably claim to have dragged manual pages kicking and screaming into the 21st century.

Benjamin Mako Hill: Computing in the Cloud Recordings

As I mentioned I would a month or so ago, I attended a workshop on Computing in the Cloud organized by Ed Felton's Center for Information Technology Policy at Princeton University. The conference aimed to discuss the policy issues that are raised by the shift from computing on machines we own and have direct control over to computing on servers owned by others. Think Google, Facebook, MySpace, and that lot. I talked about what all this might mean for free software and for open source and our communities, a bit about the AGPL, and discussed some ideas of how might proceed as a community. Princeton has been organized enough to post audio and video of the whole conference, including recordings of my talk, in a variety of formats and qualities (although unfortunately not in Vorbis and Theora). As I said in my FSF membership appeal last month, I think complications raised by "cloud computing" are one of the most important sets of challenges facing free software this year.

Axel Beckert: I finally ordered

After a three and a half week test drive during my last year’s summer holidays and much consideration about the configuration, I finally ordered a Brompton folding bike at Velofix. Since the apple green was much nicer in the catalogue than in real life, I decided that I need a bike in colours that clearly mark it as my bike: Orange frame and black front and rear swinging fork. ;-) It will have 6 gears (a 3-gear internal hub and a 2-gear dérailleur, both at the rear axle), a lowered transmission ratio for hilly Zurich and sprints in the city, a SON axle dynamo, Kevlar reinforced, reflecting tyres, and a bicycle luggage rack which also serves as kick stand when (partially) folded. Options I thought about but then dismissed for miscellaneous reasons: Schlumpf MountainDrive (can’t say if will be really worthwile) and Rohloff Speedhub (not available although I already saw a Brompton with a red Speedhub — funnily just in front of the place I live, and probably also more expensive than I remembered).

Axel Beckert: Segmentation faulty tree

aptitude on Etch just gave me a funny error message:
1/0/0 root@c2:pts/2 21:14:24 [~] # aptitude upgrade 
Reading package lists... Done
Segmentation faulty tree... 87%
2/139/0 root@c2:pts/2 21:14:43 [~] # 
Ctrl-Ms can be nice sometimes…

Wouter Verhelst: FOSDEM schedule for the Debian Devroom

I spent a good few hours today on creating a preliminary schedule for the Debian Developer's room at FOSDEM 2008. Just as I had finished it and sent it to the speakers to get their feedback before declaring it final, I received a reminder from the FOSDEM organizers that the schedule is due by the end of this week. My timing is impeccable :-) Having said that, the schedule is full. If you wanted to do a talk at FOSDEM, you're probably too late by now. Try again next year. Time to start focusing on the booth now, I guess...

Simon Richter: Building software II: now with more evil

As written earlier, I'm switching build system for one of my projects. In the end, I decided to roll my own. Yes, another build system out there. The general idea is to combine the strengths of automake and MSBuild, and take them to new extremes by not compromising where they have (that makes my build system a tad inflexible though). Automake's biggest strength is that it is descriptive, rather than imperative, and while it allows for rules to be entered directly to allow for some flexibility, this is usually the point where the Makefiles that are produced become unportable. But in general, the idea of having a tool deduce what exactly should be done to transform a set of input files into a set of output files is a good one, I think. From MSBuild, I stole the idea of making an explicit distinction between higher-level integration projects ("solutions" in their lingo) and actual build projects. Build projects only have one (main) output, which usually is a program or a library, and several auxiliary outputs (development files, translation templates, ...), while integration projects coordinate the build process (for example, if one of the build projects builds a tool, all projects using that need to be re-run if the tool is rebuilt, but only then. Automake's biggest downfall is stuff that is not explicitly supported. One of my projects uses IDL extensively, which leads to quite a lot of explicit rules supporting different ORBs. If I wanted to teach automake about that, I'd have to understand lots of perl code that emits code fragments that, when combined, will do the right thing. In a way, automake is a compiler, but based around the idea that since we start out from a Makefile compatible syntax, just adding things will magically work. Where it doesn't, special cases are invented, such as for libtool support, but stacking special cases is really difficult. MSBuild, on the other hand, leaves a lot to be desired when it comes to project-to-project integration. There is no way to tell it "publish these include files under the such-and-such directory for use by other projects", rather, you are expected to have the project using them explicitly reference your project in the include directories. If a project uses includes that reference includes from yet another project, it gets worse. Milestone 1 is going to be when the main binary can build itself on Windows and Linux.

Stefano Zacchiroli: adsense powered ikiwiki

AdSense patch for ikiwiki's embed pluging Today I've started playing with AdSense, mainly to check whether a typical homepage+blog web site (read: mine) can survive its hosting costs by the means of this kind of revenue or not. However I don't want the ads to be visible on all pages, but only in some of them, mainly the main blog page (which scores high in search engine results and is also not prone to the risk of bothering usual readers, thanks to---$DEITY bless them---RSS/Atom feeds) and some selected pet software project homepages. With ikiwiki implementing this appeared trickier than I expected. The main difficulty is of course the wiki-wide htmlscrubber plugin which I do not want to switch off because of discussion pages and a part of my website which is actually used as a world-editable wiki. Googling around it seems that there is an adsense.pm plugin for ikiwiki, but it is not registered in the ikiwiki plugins page; as such I was not particularly envy to try it out. Besides, the right place to add such a feature to me seems the embed plugin. ... so I've minimally patched it: see bug #462970. If you're willing to use AdSense with ikiwiki please try out the patch: since I'm an AdSense newbie it might well be I've underestimated the possible script snippets it can generate. Post comments to bug #462970.

David Welton: Munich Android Mobile Meeting

Tomorrow (January 28th), I'll be in Munich for this: http://www.mobile-monday.de/web/guest/android Unfortunately, the event filled up super fast and I barely managed to squeeze in, so there are probably no spaces left. Still, if anyone would like to meet up afterwards, send me an email soonish. If you managed to get in, and would like to see a demo of Hecl, let me know, because I'd like to have the chance to show that off some too! Hopefully it will be a valuable experience. Android is a pretty convincing system in many ways, but of course has yet to fully come into contact with reality, so I'm curious to meet some of the people involved and hear about it from them. I really hope it doesn't end up being a rehash of information that's available on the web, as it's a two hour drive from Innsbruck.

Mohammed Sameer: Of GNOME and fonts.

Thanks to those 2 comments. Although placing Xft.dpi: 96 in my ~/.Xdefaults did not help, but I managed to do it through the appearance control center applet. I had to purge the gtk-qt theme engine because it was freezing the dialog and setting it via gconf-editor didn't work as expected.

I had to fight with my fonts this morning but here's my configuration. Maybe it'll be useful to anyone:
DejaVu sans book 12
96 DPI
greyscale smoothing, subpixel slight RGB.

I'm not yet satisfied but it's more usable now.

Thanks Phaeronix for the help too. read more

Rob Taylor: Language runtime independance

Colin, you might want to check out PyPy, especially it’s translation framework, which (as I read it) allows the separation of language definition, optimisation techniques and machine backends (virtual or not). It looks like right now you can translate Python to C, CLR, JVM, LLVM or even JavaScript and there seem to be people working on different language definitions also, with JavaScript, Prolog, Scheme and Smalltalk in the tree.

Russell Coker: LCA 2008 Security Miniconf

Today I gave a talk about Debian security at the security mini-conf of LCA. Before I started the talk I asked for suggestions as to how to get more entries in my security blogging contest [0]. During the talk I asked for suggestions as to how to get more people involved in security development. One suggestion was to offer incentives. I’m experimenting with that with my blogging contest and may do future variations of the same thing. I started with describing some of the history of security in Debian (primarily things that involved me in some way): In 2003 I suggested that exec-shield be a standard feature in Debian kernel images [1]. I created a kernel-patch-exec-shield package in 2003 and Marcus Better took it over in 2004. We are hoping to get it included in Lenny. AMD64 architecture doesn’t need exec-shield as the CPU has separate write and execute bits in the page table, but it would be nice to get exec-shield included before the last P4 machine gets decommissioned. A presentation at the security miniconf at LCA 2005 on the topic of stack smashing is interesting [2]. At the time Adamantix was a distribution based on Debian which used PaX (similar to exec-shield). Adamantix has gone away. Hardened Gentoo has been available with Pax for all this time (but is not widely used). RHEL and Fedora have been available for all this time with exec-shield… In mid 2002 I demonstrated the first SE Linux Play machine at a conference in Germany. It was fully operational with root as the guest user. At that time SE Linux support in Debian was essentially complete. Since that time the scope of the SE Linuc project has increased slightly (EG controlling DBUS access) so the amount of work required for full support is greater. Most of that support is in Debian and Etch is basically working with SE Linux (although not quite as well as it was in 2002 due to lack of support for the strict policy). The aim is to have Lenny SE Linux become as functional as SE Linux in Fedora Core 5. While FC5 has more SE Linux features than the SE Linux project supported in 2002 it’s still a great disappointment that it’s taken so long. FC5 had pam_namespace to polyinstantiate directories such as /tmp. Lenny will hopefully have it. I described the current status: The hardening-wrapper package in unstable allows environment variables starting with DEB_BUILD_HARDENING_ to be used to control execution of GCC. Documented on the Debian Hardening Wikipedia page [3]. It’s still a little experimental and may change in the near future, but it works. Lucas Nussbaum is working on automatically building Debian packages with warnings for security related issues. The aim is to build all packages and maintain a central location for the logs to allow DDs to find and fix the problems in their packages. The Alioth Hardening project [4] will hopefully get some action soon (the people involved are busy doing work but not updating the project). The current plan is to base the Debian Hardening work around it. SE Linux in Debian is something that I want to get working correctly. There are still some significant issues that make strict policy unusable (such as correct labelling of /etc/passwd) as of last time I tested it. Finally I described the future plans. There were many questions about usability features for SE Linux, I mentioned in concept the features that Red Hat and Tresys people are developing (which I often don’t use as I prefer vi for policy editing). There were some questions about how SE Linux works. More than half the audience indicated that they had used it so I assumed some basic knowledge of SE Linux when describing how SE Linux works in regard to minimum privilege and the benefits of MAC in terms of limiting the scope of attack. I noted that every program has bugs and every program which performs security related tasks (which includes serving data to the net without being owned) should be assumed to inevitably have security related bugs (see the The Inevitability of Failure paper []). Based on the Twilight of the Books [5] article I decided to give this talk with no slides as an experiment. I talked from notes that I wrote and advised the delegates to read my blog for the details. Not presenting any slides meant that the room lights were all left on, which made things much easier when answering the many questions (I prefer an interactive format to my talks and have more questions than most speakers). It will be interesting to get some feedback from delegates about how they regarded this.

Next.

Previous.