Search Results: "ag"

15 February 2009

Norbert Tretkowski: Help with Debian MySQL packages required

During the last few months I was the only person working on the MySQL packages in Debian, and I could really need some help. Currently there is MySQL 5.0.32 in etch, 5.0.51a in lenny, 5.0.75 in unstable and 5.1.31 in experimental, and I am also trying to get MySQL Cluster and MySQL Workbench into Debian. All in all it is way too much work for only one developer.

If you are an interested Debian developer/maintainer with a good knowledge in MySQL and shared library packaging, drop me a mail.

Ben Hutchings: Going to PyCon

I'm going to PyCon 2009: Chicago Carl Karsten of the PyCon organisers recruited three of us from the DebConf video team to lead and train the video team at PyCon.

Daniel Kahn Gillmor: Stricter GnuTLS rejects outmoded X.509 certs

Recently, several people noticed that GnuTLS behavior did not match its documentation with respect to two significant security concerns, both regarding X.509 certificate validation: GnuTLS has been fixed upstream, and a fix to at least the latter problem has already propagated into etch via a security upload. The lenny packages should already behave as documented (no MD5 digests accepted in cert validation, v1 certificates not explicitly acceptable as authorities). However, this means that if you use GnuTLS-linked tools to connect to systems whose certificate chains rely on either MD5 digests (in anything but the root certificate) or on v1 certificates for any of the certificate authorities, your connections may fail due to this stricter validation. There are already several bug reports about broken LDAP connections and broken mail connections due to these problems, and there have been reasonable concerns raised on debian-release about this. So what can you do to make sure that the infrastructure you rely on or maintain does not depend on these outmoded and insecure features of X.509? Read on for concrete steps for administrators, developers/maintainers, and end users... This entry has been truncated read the full entry.Tags: gnutls, security, x.509

Holger Levsen: FOSDEM videos released

In a nice coincedence with the release of Lenny (cheers!!1), the low-quality versions of the videos from the Debian DevRoom at FOSDEM 2009 are available now!

Better quality versions will be encoded and uploaded by Ben over the next days. I'd also like to collect the slides from the talks there, so if you had a talk there, please send them to Wouter and/or me, and Wouter, please send me the slides you collected on the presetation computer ;-)

Basically I'm very happy with our results, excpet for two things: sadly the computer running dvswitch wasn't powerful enough to do picture in picture (and due to time constraints we weren't able to switch to a more powerful one), so we'll have to plan this better next year. And second, I have no real clue how useful our streaming efforts are, I believe the recordings are useful, but in both cases feedback from people who find them useful is appreciated! Covering FOSDEM is certainly a lot of fun, but it's also a lot of work and leaves not much room for seeing other parts of the conference. So a short reply (I'll post this to d-d-a with reply-to set to -project) will be very much appreciated! :)

Big thanks go to Womble2, edrz, xerrako, Q_, danielsan, DaCa, tokkee, luca, Yoe, Ganneff, franklin, huhn, luk, CarlFK, daven and some more volunteers I cannot remember right now! Also not to be forgotten the FOSDEM crew & volunteers for an awesome event and the people from CCC Hamburg who came by car and took a lot of audio/video/computer equipment for us (and left 90min later than planned! Thanks again!)! And also Debian (via the DPL) for some 120 Euros to rent equiqment and for buying batteries and the always needed duct-tape!

Julien Valroff: Lenny

lennybanner_indexedWell, I am sure all of you have already read the announcement: Lenny (aka Debian 5.0) is out! I have been using Debian on all my machines since at least mid 2003, when Woody was stable. Sarge was then released in 2005, then Etch the year after. I have updated my personal repository of unofficial packages for this new stable release. I have let etch packages available (under oldstable), but will remove them in a while. This repository is mainly mainly composed of backported or patched packages for my own use, but can be used by anyone (but I do not guarantee anything ;-)).

Michael Prokop: Debian GNU/Linux 5.0 codename Lenny - News for sysadmins

Alright, Debian GNU/Linux 5.0 AKA as Lenny has been released. Time for a Debian unstable unfreeze party! 8-) What does the new stable release bring for system administrators? I ll give an overview what news you might expect when upgrading from Debian GNU/Linux 4.0, codename Etch (released on 8th April 2007) to the current version Debian GNU/Linux 5.0, codename Lenny (released on 14th February 2009). I try to avoid duplicated information so make sure to read the release announcement and the official release notes for Lenny beforehand. Noteworthy Changes Virtualisation Virtualisation related new tools: Desktop oriented packages like virtualbox and qemu are available as well of course. Noteworthy Updates This is a (selective) list of some noteworthy updates: New packages Lenny ships over 7000 new packages. Lists of new/removed/replaced packages are available online. I ll name 238 sysadmin related packages that might be worth a look. (Note: I don t list addon stuff like optional server-modules, docs-only and kernel-source related packages. I plan to present some of the following packages in more detail in separate blog entries.) Further Ressources

Mike Hommey: Testing small upgrades with namespaces and unionfs

If you are following this blog, you probably remember per-process namespaces. Today, I m going to tell you how I did use them in the process of preparing this server to be upgraded to Lenny. I must say I was not using the most recent stuff on this server, and this is why I needed such preparation. First, this server is still running with php4. And well, the following line in the apt-get dist-upgrade output got my full attention (emphasis mine):
The following packages will be REMOVED:
cacti libapache2-mod-php4 libarchive-tar-perl libcurl3-openssl-dev
libgssapi2 libpci2 librpm4 libssp0 linux-kernel-headers modutils php4-mysql
While this server is not important enough not to be broken for a couple hours, I do like to test procedures that could help on servers that are. The first thing I needed to do on this server was obviously to upgrade php. But we all know how php applications are not fully compatible with all versions of php, so I also needed to test the upgrade was not breaking anything. On a server you don t care much about, you can just upgrade, test if all is okay, and be done with it. Obviously, if all is not okay, your visitors will see it, and you may also have a bad time downgrading. Another way to perform the upgrade is to have a similarly installed server on the side, test and validate the upgrade there, and replicate the upgrade on the production server if everything is fine. However, that does require additional resources, and possibly to setup them if they don t already exist. A cheaper way to do the above is to do it on the production server, both in-place and on the side (you ll see what I mean), using unionfs and per-process namespaces. Full containers could be used instead of per-process namespaces (such as openvz, vserver or lxc), but they still require much more setup, especially when you don t use them in the first place. Chroots could work just as well as per-process namespaces, but one of the ideas here is to expose the per-process namespaces feature, and allow for improvement of this procedure with pid and network namespaces, which are not available in Etch (where I m starting from), but are in Lenny. Unionfs allows to merge several directories into a single one, accessing some read-only, and others read-write. Installing unionfs is as easy as running the following command:
apt-get install unionfs-modules- uname -r
I won t describe all the kinds of setups that are possible with unionfs, but only one typical use case, which is what we will be using here:
# mkdir /tmp/root-cow
# mount -t unionfs -o dirs=/tmp/root-cow:/=ro none /mnt
The first thing we do here is to create an empty directory. Next, we merge it with the root filesystem (/), that we will keep read-only (meaning unionfs won t allow itself to write there), and mount the merged filesystem under /mnt. none could just be anything, as there is no device to be mounted. The result, in /mnt, is just something that looks like the root filesystem:
# ls /
bin boot dev etc home initrd lib media mnt opt proc root sbin srv sys tmp usr var
# ls /mnt
bin boot dev etc home initrd lib media mnt opt proc root sbin srv sys tmp usr var
But creating or modifying a file will do so in /tmp/root-cow:
# echo a > /mnt/a
# cat /a
cat: /a: No such file or directory
# cat /tmp/root-cow/a
a
# echo foo.com > /mnt/etc/mailname
# cat /etc/mailname
glandium.org
# cat /tmp/root-cow/etc/mailname
foo.com
# find /tmp/root-cow
/tmp/root-cow
/tmp/root-cow/etc
/tmp/root-cow/etc/mailname
/tmp/root-cow/a
Keep in mind that it doesn t include submounts, though:
# ls /var
backups cache lib local lock log mail opt run spool tmp www
# ls /mnt/var
This means we ll have to also mount /var, /proc, /dev, and /sys. That s enough testing for now, and we ll first do some cleanup before going after the real job:
# umount /mnt
# rm -rf /tmp/root-cow
Using the newns utility from my first post on per-process namespaces, let s create a new namespace to keep our testing private, and populate it with the necessary mount points:
# newns
# umount /tmp
# mount -t tmpfs tmpfs /tmp
# mkdir /tmp/root-cow /tmp/var-cow
# mount -t unionfs -o dirs=/tmp/root-cow:/=ro none /mnt
# mount -t unionfs -o dirs=/tmp/var-cow:/var=ro none /mnt/var
# cd /mnt
# pivot_root . mnt
# mount --move /mnt/proc /proc
# mount --move /mnt/sys /sys
# mount --move /mnt/lib/init/rw /lib/init/rw
# mount --move /mnt/tmp /tmp
# mount --move /mnt/dev /dev
The second and third statements are useful to avoid sharing /tmp with the main namespace, which means the directories we create in the fourth statement won t be visible in /tmp outside this namespace. The fifth and sixth statements put the union filesystems in place. As my system only has a separate /var filesystem (no /usr, and I don t care about /home here), I only need to setup these two. Feel free to add more union filesystems as necessary. The pivot_root call allows to switch to the unionfs ed root: everything under /mnt (/mnt and /mnt/var in our case) will be remounted under /, while what was under / is remounter under /mnt under the new root.
This means, in our case, that we have / and /var as union filesystems, while the old / and /var are respectively in /mnt and /mnt/var. It also means /dev, /proc, /sys and other filesystems are remounted as /mnt/dev, /mnt/proc, /mnt/sys, etc., which is why we next mount --move all of them to a better place in our namespace. Once all this setup is done, we are ready to do our php upgrade test. As Etch doesn t have support for neither PID namespaces nor network namespaces, we ll still have some conflicts with the main namespace for TCP port binding and process handling, so we need to be a little careful:
# rm /var/run/apache2.pid
# echo Listen 8080 > /etc/apache2/ports.conf
With these changes, we can now safely start apache2 in this namespace, at the same time the main apache2 runs in the main namespace:
# /etc/init.d/apache2 start
Now, there are actually 2 problems showing up in apache in this setup. The first one is that displaying static files doesn t work. At all. It appears unionfs doesn t support sendfile(). Which is fine. But apache doesn t check for sendfile() s error cases and doesn t fallback to a working solution when sendfile() doesn t work. So we have to manually disable it:
# echo EnableSendfile off > /etc/apache2/conf.d/sendfile.conf
The second one is that access to the mysql socket doesn t work properly under the unionfs. I didn t want to investigate further, so I only worked around the issue by forcing to use the socket outside the unionfs:
# mount --bind /mnt/var/run/mysqld /var/run/mysqld
Finally, we can test and validate our php upgrade:
# apt-get install php5-mysql php5-cli php5-snmp libapache2-mod-php5
# /etc/init.d/apache2 restart
# apt-get remove --purge php4-common
Note that installing libapache2-mod-php5 will remove libapache2-mod-php4, and apache2 gets restarted, taking into account this change. But the php modules (php5-mysql and php5-snmp) install is only going to happen after that, and no apache2 restart is triggered then, which leaves a half working php setup
Also note that the cacti setup in etch supposes php4 is installed, using a IfModule statement against mod_php4.c and none for mod_php5.c, which means a part of its setup doesn t work out of the box (most notably, the DirectoryIndex). Once all is validated, all we need to do is to stop apache2 and exit from the namespace. The union filesystems and temporary filesystems are then automagically cleaned-up and the namespace disappears as well as all modifications we just did, since all processes using the namespace ended. We are now free to upgrade on the production server, as we know all the side effects. I ll now be able to upgrade to Lenny without php getting removed.

Bastian Venthur: Lenny

Today Lenny was finally released. According to this page with roughly 120 open release critical bugs. That s quite a big number according to our standards, but still a good and necessary compromise. Thanks for everyone involved, good work everyone! I m very happy that the release didn t take quite as long as I predicted. Three or four more months of Sid being frozen would probably have meant more people playing with semi-supported mixtures of unstable and experimental packages and more migration towards other distributions with more current software packages. So I m very happy to see over a hundred new packages uploaded to unstable already and roughly 700 new release critical bugs opened :)

David Pashley: MySQL silently truncating your data: Update

After my entry yesterday about MySQL truncating data, several people have pointed out that MySQL 4.1 or later gives you a warning. Yes, this is true. You can even see it in the example I gave:
Query OK, 1 row affected, 1 warning (0.00 sec)
I ignored mentioning this, but perhaps should have said something about it. I reason I didn't mention it was because I didn't feel that a warning really helped anyone. Developers have enough problems remembering to check for errors, let along remembering to check in case there was a warning as well. Plus, they'd then have to work out if the warning was something serious or something they could ignore. There's also the question of how well the language bindings present this information. Take for example, PHP. The mysqli extension gained support for checking for warnings in PHP5 and gives the following code as an example of getting warnings:
mysqli_query($link, $query);
if (mysqli_warning_count($link))  
   if ($result = mysqli_query($link, "SHOW WARNINGS"))  
      $row = mysqli_fetch_row($result);
      printf("%s (%d): %s\n", $row[0], $row[1], $row[2]);
      mysqli_free_result($result);
    
 
Hardly concise code. As of 5.1.0, there is also mysqli_get_warnings(), but is undocumented beyond noting its existence. The MySQL extension does not support getting warning information. The PDO wrapper doesn't provide any way to get this information. In perl, DBD::mysql has a mysql_warning_count() function, but presumably would have to call "SHOW WARNINGS" like in the PHP example. Seems Python's MYSQLdb module will raise an exception on warnings in certain cases. Mostly using the Cursor object. In java, you can set the jdbcCompliantTruncation connection parameter to make the driver throw java.sql.DataTruncation exceptions, as per the JDBC spec, which makes you wonder why this isn't set by default. Unfortunately this setting is usually outside the programmer's control. There is also the java.sql.Statement.getWarnings(), but once again, you need to check this after every statement. Not sure if ORM tools like Hibernate check this or not. So, yes MySQL does give you a warning, but in practice is useless.
Read Comments (0)

Ingo Juergensmann: Lenny released, next to come: Squeeze

Congrats and thanks to all people involved into releasing Lenny! Keep on the good work!

Now everyone can concentrate on the next release of Debian called Squeeze. My wishlist for the new, upcoming release:

  1. no political, show-stopping discussions or GRs anymore.

  2. more members in core teams such as ftpmaster, DAM, debian-admin, ... - don't wait until someone will eventually join, but look actively for new members and train them, so that the workload for everyone involved will be less at the end.

  3. please forget your personal dislike when working with other people. You don't need to be friends, but you should be able to work together like professionals and concentrate on the topics.

  4. please introduce sub-releases for desktop, multimedia, kernel stuff while having a base of core packages for a longer term for servers. Release desktop related stuff more often than the base core packages.

  5. acknowledge the work of contributors and find a way to let them some part of Debian without following the long and often unnecessary, unwanted and boring path of NM.

  6. and finally: have fun! :-)



So, now it's up to upgrade my machines to Lenny in the next days... I hope everything will be as smooth as everyone is expecting it. :-)

Sune Vuorela: This time of year again

/me++ Or in a bit longer words, today is my birthday and I got a nice present from Debian - a release sent from Samoa. For all the KDE/Debian users, this is also the beginning of something special: Pushing KDE4 slowly to unstable and testing/squeeze.
If you are in the group of KDE-users-against-change, then please stay with the just released version of Debian, Debian Lenny, as this is where KDE3 desktop will be. From Debian unstable, it will dissapear soon.

Jan Wagner: Oh happy day

What a happy day on the wedding anniversary of our civil marriage we got a great gift. Our favorite distribution released a new major version.
Like every time it s the best distribution our project released so far. Many thanks to all those people who did make that happen. If you not married today, maybe you have the possibility to dedicate Lenny to your valentine. :)

Paul van Tilburg: Lenny Released

The long-awaited, big and stable Debian GNU/Linux Lenny 5.0 has been released! Great job everyone and congratulations! In this release the Debian/Ruby Extra team has an ever greater presence. We were able to increase the number of mainted libraries and applications to over 95 packages. Also quite a lot of issues were resolved and I am proud that we obtained this quality level. For Squeeze we plan to deal with the transition to Ruby 1.9 and with possible multiple interpreter-support (still Ruby 1.8, JRuby?). We might also deal with the gems, who knows? :) P.S. Indeed, did I just started posting without explaining why I was away for over 7 months?

Kartik Mistry: Lenny


* Lenny is the future now! Lenny on Kavin's Hand Now ;)

David Pashley: MySQL silently truncating your data

MySQL in its standard configuration has this wonderful "feature" of truncating your data if it can't fit in the field.
mysql> create table foo (bar varchar(4));
Query OK, 0 rows affected (0.00 sec)
mysql> insert into foo (bar) values ("12345");
Query OK, 1 row affected, 1 warning (0.00 sec)
In comparison, PostgeSQL does:
psql=> create table foo (bar varchar(4));
CREATE TABLE
psql=> insert into foo (bar) values ('12345');
ERROR:  value too long for type character varying(4)
You can make MySQL do the right thing by setting the SQL Mode option to include STRICT_TRANS_TABLES or STRICT_ALL_TABLES. The difference is that the former will only enable it for transactional data storage engines. As much as I'm loathed to say it, I don't recommend using STRICT_ALL_TABLES, as an error during updating a non-transational table will result in a partial update, which is probably worse than a truncated field. Setting the mode to TRADITIONAL includes both these and a couple of related issues (NO_ZERO_IN_DATE, NO_ZERO_DATE, ERROR_FOR_DIVISION_BY_ZERO) You can set the mode using: Just say no to databases that happily throw away your data
Read Comments (4)

Mark Brown: Upgrading crm114

When upgrading from older crm114 releases and trying to retain your existing configuration it is important to check that all the configuration options that the new version expects to be set have been set. While some will cause errors if they re omitted others will appear to work but will cause unwanted behaviour at runtime. For example, omitting good_threshold and spam_threshold will cause everything to be flagged as spam in X-CRM114-Status even though the classifier is working well. In practice there are relatively few configuration options that users are expected to configure so it may be easier to redo the configuration based on the example provided. For safety it s best to delete your existing CSS files too in case they ve been invalidated by a configuration or format change. It s all a bit manual but it s worth it for what it does for my inbox.

14 February 2009

Biella Coleman: Joe Reagle on Wikipedia

In this age of bits and bytes, there are many virtual organizations and networks which produce all sorts of stuff we use on a daily basis. My two favorite institutions are Debian (not a surprise) and Wikipedia, not just because they oh-so-useful to me and many others, which they are, but because the social organizations behind these two entities are so (at times maddeningly) complex and full of nuance, they provide for endless analytical fascination. One of my friends, Joe Reagle, who has recently graduated from my home department, is presenting is work on Wikipedia and I thought some local New York geeks might be interested. Information below:
All welcome 4:30 - 6:00 PM, Tuesday February 17
206 Vanderbilt Hall, 40 Wash. Sq. So. Wikipedia: Nazis and Norms Joseph Reagle, NYU Department of Media, Culture, and Communication Abstract: In 1990 Mike Godwin coined his Law of Nazi Analogies to capture the common devolution of Usenet discourse into insulting comparisons with Nazis or Hitler. Eleven years later, Jimmy Wales wrote that it was important that the Wikipedia community preserve and extend our culture of co-operation, with all of us standing as firmly as possible against the culture of conflict embodied in Usenet. I argue Wikipedia is a realization even if flawed of a long-held vision for a universal encyclopedia: a technology inspired vision seeking to wed increased access to information with greater human accord. And I claim Wikipedia s collaborative culture is a big factor for this success: the norms of Neutral Point of View ensures that the scattered pieces of what we think we know can be joined and good faith facilitates the actual practice of fitting them together.

Biella Coleman: Joe Reagle on Wikipedia

In this age of bits and bytes, there are many virtual organizations and networks which produce all sorts of stuff we use on a daily basis. My two favorite institutions are Debian (not a surprise) and Wikipedia, not just because they oh-so-useful to me and many others, which they are, but because the social organizations behind these two entities are so (at times maddeningly) complex and full of nuance, they provide for endless analytical fascination. One of my friends, Joe Reagle, who has recently graduated from my home department, is presenting is work on Wikipedia and I thought some local New York geeks might be interested. Information below:
All welcome 4:30 - 6:00 PM, Tuesday February 17
206 Vanderbilt Hall, 40 Wash. Sq. So. Wikipedia: Nazis and Norms Joseph Reagle, NYU Department of Media, Culture, and Communication Abstract: In 1990 Mike Godwin coined his Law of Nazi Analogies to capture the common devolution of Usenet discourse into insulting comparisons with Nazis or Hitler. Eleven years later, Jimmy Wales wrote that it was important that the Wikipedia community preserve and extend our culture of co-operation, with all of us standing as firmly as possible against the culture of conflict embodied in Usenet. I argue Wikipedia is a realization even if flawed of a long-held vision for a universal encyclopedia: a technology inspired vision seeking to wed increased access to information with greater human accord. And I claim Wikipedia s collaborative culture is a big factor for this success: the norms of Neutral Point of View ensures that the scattered pieces of what we think we know can be joined and good faith facilitates the actual practice of fitting them together.

Joerg Jaspert: Lenny Release

I just finished most of my jobs for the Lenny release. I started, together with Mark Hymers, at 10:23 UTC. This was ahead schedule, which said 12:00 UTC, but better early than late. After disabling all our ftpmaster cronjobs, setting up our work environment and whatever else we needed and at 10:43 UTC we got the Release Teams GO. All of what we did got logged from screen, as we intend to write a dak tool doing such releases. Anyway, I won t bore you with a detailed set of actions we had to took, way too much for now, just some few moments (All times in UTC): While writing this entry people are still doing work for the release. For example the cd building will take time, after all there are well over 500 images (and 36 live cds). Current plan seems to be that we ftpmaster push the archive mirrors around 23:00 UTC, so it has time to sync everywhere. Some while later the cd mirror will get a push, and then the official announcement will happen. Thanks go out to everyone involved in preparing this release, be it in the past by fixing bugs, uploading packages, doing whatever was needed, as well as doing the work today.

Brandon Holtsclaw: Managing Social Media Accounts

So in 2009 I've started using Social Media Accounts alot more like Facebook, Twitter,Wordpress ( self hosted ), and plan to use more as time goes on and I discover new services and new services are introduced. <rant> One of the issues I've noticed is most "tweet flows" want you to update your status across multiple services, like your IM status would be the same as your Twitter status and again the same as your Facebook status and so on. See the problem with this is not all "status" messages on Social Media sites are used for the same purpose , e.g. the Facebook status allows comments and the Tweet allows replies and RT's ( Re-Tweets ) and IM status doesn't allow any feedback at all, at least not publicly. An posting to both identi.ca and twitter causes replies and such to be checked on both. Where is our "Digital Convergence" / Digital Universe for Social Media ? How do any of you keep all the different forms of social media updated ( an relevant ) to the media its self, e.g. not posting the wrong status to the wrong service and not using 100000(.5) web interfaces constantly. </rant>

Next.

Previous.