Search Results: "ag"

2 October 2007

Neil Williams: 2038 overflows

Adrian (also sent by email):
Re: 2038 issues on mobile platforms.

It is possible to handle 64bit time on 32bit systems. I got disillusioned with the libglib2.0-0 support (GDate) and I already had a library capable of 64bit mathematics (libqof1) so I wrote QofDate and QofTime that can handle true 64bit date and time calculations, formatting and scanning on 32bit or 64bit installations. I estimate that this gives us enough capacity to handle time for a couple of dozen times the age of the universe to nanosecond precision. The maths can also go backwards as far as it can go forwards so it could handle the date of the Big Bang with nanosecond precision too - if anybody actually works that out.
:-)
I'll be using this library in Emdebian to provide support for 64bit maths for gpe-expenses and the pre-alpha gpe-cash (stripped out gnucash for embedded devices) so at least your financial records will be safe.
http://cashutil.sourceforge.net/gpecash.php
http://gpe-expenses.sourceforge.net/

"QofTime is a lot like the unix 'struct timespec' except that it uses a
64-bit signed int to store the seconds. This should adequately cover
dates in the distant future as well as the distant past, as long as
these are not more than a couple of dozen times the age of the
universe. Values of this type can range from -9,223,372,036,854,775,808
to 9,223,372,036,854,775,807."


http://qof.sourceforge.net/doxy/group__QOFTIME.html#gb93e930907d0e2eba07b1fa7496e7822

http://qof.sourceforge.net/doxy/group__QOFTIME.html

QofTime is defined as 64bit on all systems and will not overflow until
the year 292,471,208,679 (not counting leap years). i.e. approx.
9223372036854775808 / (60*60*24*365). This also means that some values
of QofTime cannot be converted to a time_t on systems where time_t is
defined as 32bit.

http://qof.sourceforge.net/doxy/group__Date.html

A QofDate is theoretically able to go forward to the year
292,471,206,707 AD and back to the year 292,471,206,708 BC. Whether
such dates actually exist is outside the scope of this documentation.

http://packages.debian.org/sid/libqof-doc
http://packages.debian.org/sid/libqof1

Matthew Palmer: That ain't no *disco* inferno

We're a third of the way through spring, and already we're hitting temperatures that would be a respectable mid-summer day. Tomorrow has also been declared a Total Fire Ban day in our area. That's probably nearly unheard of, especially given the large amount of rain that we've had over winter. I think I'm going to be a busy boy this summer. The bush around our town last had a bushfire through it seven years ago, and there's a regular seven year cycle of major bushfires. We're due for it. As this is my first summer as a qualified bush firefighter, I'm a bit twitchy about what the continued hot, dry weather may bring. Here's hoping it's not too horrific.

Simon Richter: The CEO has really earned his bonus

The German train drivers are going on strike again on Friday, asking for 30% more money. So far, they've been offered 4% and two extra hours of work per week. At least DB had the decency not to sink millions of Euros into an advertising campaign denouncing the union's demands as unreasonable. Which they aren't.

Michal Čihař: Too much spam in Ukolovnik demo

Looking at the web stats, I noticed, that quite a lot of people find something relevant to "environmental" on my pages. As I was not aware of anything related here, I tried that in Google. To my surprise all results are in demo for Ukolovnik. Well I do not want to add any anti spam technique to this simple tool as it will be usually password protected. And this is exactly what I did with demo for now. So if you want to use it, you need to login with user demo and password demo. I hope this will prevent spammers from using this demo, otherwise I would probably have to close it.

1 October 2007

Randall Donald: for those of you following along at home...

96.43.01 and 71.86.01 legacy packages have been started but I didn't get them done in time for a weekend release. Sorry about that. The plan is for the next two days.

Steve McIntyre: Debian T-shirts popping up everywhere...!

Phil and I managed to catch up with Linus when he was at the kernel summit in Cambridge last month. We gave him a Debian T-shirt at the time, as Phil blogged at the time. Barton George was one of a number of Sun people who came along to Debconf, and he picked up an Etch T-shirt while he was there too. Apparently he's quite keen to wear it in public too... :-) Any more action shots out there?

Lior Kaplan: Firefox bug triage

Today, I started doing the Firefox bug triage. A request to reproduce or close bugs was sent to 324 bugs’ owners. Most of the bugs were reported against Firefox version 1.5 (or lower). As some people responded quite quickly, about 10 bugs were closed and another 10 were reproduced (or confirmed to still be relevant). The latter got reassigned to Iceweasel for further handling by the maintainer. I hope people will continue to be responsive… If someone wishes to follow this triage, simply look at the Firefox bugs list.

Joey Hess: pristine-tar followup

Madduck wondered why a package using revision control needed pristine tarballs at all. Firstly, the example he gave of tagging an upstream release and creating a tarball of it to build the package against is exactly what pristine-tar does. Except it preserves permissions and timestamps and other tar cruft. Sometimes timestamp or permissions issues do cause issues with package builds, so being able to build against the original files from the pristine tarball is potentially useful to catch and fix such problems. As to other uses of pristine tarballs... It's hard to list the advantages to using pristine tarballs, since Debian (rpm too) has had them forever, and lots of people may depend on them in ways that we don't anticipate. For example, I've seen FreeBSD point at ftp.debian.org to get tarballs for their packages, since they don't archive tarballs on their own, and sometimes the tarball isn't available upstream (or ftp,debian.org is the upstream). That's a wacky example, but I've seen it more often than I've seen pristine tarballs used for the often-cited md5sum comparison case. Rather than try to enumerate all the possible reasons for pristine tarballs, and then try to whittle the list down to reasons that actually make sense, and cost-benefit analise those, it seemed better to just try to write a solution to the problem. (Or at least, to most of it -- a hopefully small subset of the set of reasons for pristine tarballs are not satisfied by pristine-tar.) I've also been theoretically interested in this problem of generating pristine tarballs from version controlled source ever since Scott Remnant mentioned at a meeting (140 mb video of meeting here) that he had a tool to do it -- and AFAIK never shared the tool! So the challange factor was another reason to write it. However, pristine-tar has already saved me hundreds of megabytes of disk space, sped up my release process (avoiding bug #225483) and simplified the way I work, so it's already a net win for me, even if it turns out we don't need pristine tarballs for anything at all!

John Goerzen: Spineless Democrats

The Democrats ran in 2008 on the platform of ending the Iraq war, and won largely on that platform. Now they are failing to deliver upon it.

It is true that they have a thin majority in the Senate and a not much wider one in the House. It is also true that it takes 60 votes to pass legislation in the Senate, which they don't have.

But here's the thing. It takes 60 votes to pass legislation. That means that they can easily defeat any massive Republican war spending bill.

I think they are worried about the Republicans painting them as being against the troops. So what? If the Republicans vote against a Democratic funding bill that provides adequate funds for an orderly withdrawal, aren't they doing the same? "No" votes on both are votes to prevent the funding from passing.

They easily have the votes to defeat massive Republican spending bills. So why not advance a spending bill like they campaigned for, and watch all the Republicans vote against it? If no funding at all passes, they achieve their objective, just not as cleanly, and the Republicans would be the ones voting against funding. Make the Republicans take some heat for a change, and give them no choice but to compromise.

Martin F. Krafft: Pristine tarballs and VCS

Joey writes about the difficulty of dealing with the need of pristine tarballs and version control systems. He concludes that it's best to save the tarballs in the repository and has written a tool to store binary differences to save space to achieve his goal. This being another piece of software by Joey, it's probably worth checking out. But I wonder why we actually bother about pristine tarballs. Sure, our Debian archive scripts require a tarball, but why does that have to be the pristine upstream tarball? As Debian maintainer, I use git to keep track of the software that I package, and if possible, I track the upstream repository directly (Git makes it very easy to track repositories of the other, popular version control systems). When I decide to upload a new upstream version to the Debian archive, I tag the upstream tree, sign the tag, and generate a tarball from it:
git tag -s -m'preparing release of upstream 1.2.3' upstream/1.2.3
git archive --prefix=foo-1.2.3/ upstream/1.2.3   gzip -9 \
  > ../foo_1.2.3.orig.tar.gz
Then I merge the tag into my Debian branch and prepare a Debian release, which I also tag (debian/1.2.3-1) just before uploading the package to our archive. This is very flexible and allows me to release packages based on software snapshots, as I just did with mdadm. Now, a filename of mdadm_2.6.3+200709292116+4450e59.orig.tar.gz pretty clearly states that this is not mdadm-2.6.3.tar.gz, so people would be aware that this tarball is not "upstream-official". But what about official releases, like mdadm-2.6.3.tar.gz? When preparing the Debian package, it's only slightly more effort for me to download the official tarball and store it as ../mdadm_2.6.3.orig.tar.gz, but why do I need to keep it around after I uploaded Debian package 2.6.3-1? I know I need the orig tarball to prepare the diff.gz for 2.6.3-2, but for that purpose, I can really just git-archive the appropriate tag. The result won't produce the same hash (because the tar format stores timestamps and is thus not really appropriate for the cause), but it provides the same contents. In fact, what I (or someone else) should finally implement is a tool to create the diff.gz directly from the version control data or even better, we should finally get rid of source packages as I've previously suggested, long before Ubuntu came around to propose and blueprint the concept. I am aware of some people's preference to be able to "independently verify Debian's orig tarball using e.g. a detached GPG signature provided by upstream," but I dare to question the point of this verification. Those who care enough to verify that the Debian-provided orig tarball is pristine are hopefully building their own binary packages instead of trusting mine (another beef I've raised in the past), and then they might just as well download the source directly from upstream. I'd say most people (rightfully) don't do this and just use the Debian-provided content, which can be assumed to be pristine if you trust me and Debian: my GPG signature authenticates uploads to the Debian servers, and APT provides authenticity checks downstream up until the installation on an end-user system. and if you trust the version control system, and this actually raises an interesting point for me: how feasible would a man-in-the-middle attack between Neil's (the mdadm upstream) repository and mine be, given that I use the plain-text git transport protocol to fetch new commits. If you have any comments on that, please let me know. I'll leave this issue for another discussion or post. NP: The Beatles: Abbey Road Update: Matej Cepl pointed me to this thread on the fedora-devel mailing list, where they discuss switching from CVS to Git and talk a lot about their needs and how the end result is much the same as what I am proposing. Thanks!

Simon Richter: Self-censorship

A lot of people treat their blog basically as an extension to their CV, and don't write anything that could be used against them in any way, and even if it is just to suggest that they are not invincible superhumans who work 36 hours every day. I often find myself thinking about what people could read into a posting while still writing it, thus censoring myself; I even do so now. Some of the commercial blog hosters offer "private" categories where friends have to log in to see some of the entries. What is your take on the situation? Do you feel limited in what you can write into your blog by what other people might think?

Kartik Mistry: Freed.in/07

* One of the best ever event Freed.in is over (although, some people are enjoying at Manali right now!). I came back on last night. * I reached Delhi on Thursday night. Grepping JNU was easy due to pre-paid taxi from airport. Got my room at Aravali Hostel and found none of the known person at first site. Oldmonk’s reply to my call, ‘where are you?’ was hilarious one. Finally, I found Karunakar and we enjoyed ‘Maggie’ at 12 AM. * Both days were entirely full of fun. I talked about ‘Debian-IN‘ project. Unfortunately, my talk got last place on schedule (I think due to track allocation etc) and so, number of people was less. The fun thing was that whole #linux-india channel (almost, except famous Lap_64) was there. And channel was so quite during 2 days.. * With very limited time in our hand, we (me and tuxmaniac) visited Qutub Minar, India Gate and famous Delhi Metro (by traveling to/from random station!). Flickr photos are up.

Russell Coker: live.com - Useless Search

I’ve just started getting a lot of traffic referred by live.com. It seems that my post Porn for Children [1] is the second link returned from a live.com search for “porn” and my post Porn vs Rape [2] is the third link. These results occur in two of the three settings for “safe search” (the most safe one doesn’t return any matches for a query about “porn”). A query for “porn” and “research” (which would reasonably be expected to match a blog post concerning scientific research made my page the 8th listing (behind http://www.news.com.au/404, http://www.news.com.au/couriermail/404, and http://www.theaustralian.news.com.au/404). It seems strange that a query which should match my page gives it a lower ranking than three 404 error pages while a query which shouldn’t match my page (no-one who searches for “porn” on it’s own wants to read about scientific research) gives it a high ranking. One very interesting thing about the live.com search is that it doesn’t filter out some of the least effective ways of gaming search engines. For example the URL http://gra.sdsu.edu/research.php has a huge number of links to porn pages and pages that apparently sell illegal pharmecuticals) that are not visible (view page source to see them). The links that I tested were all broken so it seems that the other sites (including http://www.hcs.harvard.edu/~hraaa, http://base.rutgers.edu/pgforms, http://www.wccs.edu/employees, http://base.rutgers.edu/mirna, http://www.calstatela.edu/faculty/jperezc/students/oalamra, and http://institute.beacon.edu/), were cleaned up long ago. There is probably some money to be made in running a service that downloads all content from a web site and/or has a firewall device that sniffs all content that is sent out and makes sure that it seems to be what is intended (about half the URLs in question appear to relate to content that is illegal under US law). As an aside, I did a few other live.com searches for various sites and the word “porn” and found one Australian university running a forum with somewhat broken HTTP authentication that has some interesting posts about porn etc. I’m not going to provide a link because the content didn’t appear to violate Australian law and you expect some off-topic content on a forum. But to be fair, live.com have significantly improved their service since last time I tested it [3]. Now a search for “bonnie” or “bonnie++” will give me the top two spots which is far better than the previous situation. Although I have to admit that the Google result of not giving me a high ranking for “bonnie” is probably better.

Mike O'Connor: A Driver for the PCDJ DAC-2

I had one of these devices collecting dust in my basement. I finally got around to reverse engineering a userspace driver for it, which was much easier than I expected. It just shows up as a usb->serial device, and it was mostly a matter of of watching the serial line while hitting buttons. I have started to figure out some of what I need to know to communicate with it in the other direction in order to do stuff like turn on the lights and manipulate the lcd displays. That stuff is not yet, however, functional, but in the spirit of "release early, release often", I've uploaded a 0.0.1 release to the project page on sourceforge. Also included is a python extension which allows you to register callbacks for the various controls on the device. After I get the leds and lcds working, I think the next step will be to write a program to generate synthetic MIDI events when the device is manipulated so I can hook the thing up to something like mixxx. Hopefully someone else has one of these kicking around and might also find this work useful!

Mike O'Connor: A Driver for the PCDJ DAC-2

I had one of these devices collecting dust in my basement. I finally got around to reverse engineering a userspace driver for it, which was much easier than I expected. It just shows up as a usb->serial device, and it was mostly a matter of of watching the serial line while hitting buttons. I have started to figure out some of what I need to know to communicate with it in the other direction in order to do stuff like turn on the lights and manipulate the lcd displays. That stuff is not yet, however, functional, but in the spirit of "release early, release often", I've uploaded a 0.0.1 release to the project page on sourceforge. Also included is a python extension which allows you to register callbacks for the various controls on the device. After I get the leds and lcds working, I think the next step will be to write a program to generate synthetic MIDI events when the device is manipulated so I can hook the thing up to something like mixxx. Hopefully someone else has one of these kicking around and might also find this work useful!

Michal Čihař: Nokia cables

What does cryptic shortcut for different cables for different Nokia phones mean? This was always a bit confusing to me. Now I finally found some document which writes quite clearly, what all they do. Unfortunately for most readers of this blog, it is only in Czech language - Ovl d n mobiln ho telefonu jedno ipov m mikroprocesorem. However here is quick summary if somebody is interested: MBUS Single wire (+ ground) connection, usually used for servicing phone, but sometimes also exposes some functionality. Fixed baud rate at 9600. DTR and RTS usually used as power source, DTR should be low and RTS high. FBUS Two wire (+ ground) connection, used for user data. Variable baud rate (but usually 115200). DTR and RTS usually used as power source, DTR should be low and RTS high. DAU-9 / DLR-3 Cables for both FBUS and MBUS, switching is usually done by toggling RTS or DTR signals (for DAU-9) or special AT command (for DLR-3). DLR-3 also additionally supports AT commands over FBUS lines. DKU-5 This is basically DLR-3 cable with USB/RS232 converter, so it is first step of getting USB into phones. DKU-2 This is for recent phones which directly support USB, it contains no logic, just wires for USB.

Joey Hess: pristine tarball generator

Keeping pristine upstream tarballs around is a pain. Wouldn't it be nice to be able to keep them in revision control? Except, it would use far too much disk... Here's a solution. It generates an binary delta between the pristine upstream tarball and a tarball created using files checked out of the repository. The delta should be quite small, and any checkout of the repository that has the same file contents as that used to create the delta can be used to regenerate the pristine tarball. Example (which would presumably be more fun and faster if I used git):
joey@kodama:~package/uqm-voice>svn switch svn+ssh://uqm.debian.net/srv/svn/uqm/tags/uqm-voice/upstream_version_0.3
D    debian
A    comm/blackur/black041.ogg
U    comm/shofixt/shofi040.ogg
U    comm/starbas/starb182.ogg
D    comm/slyland/slyla030.ogg
U    comm/chmmr/chmmr035.ogg
U    comm/supox/supox031.ogg
Updated to revision 223.
joey@kodama:~package/uqm-voice> pristine-tar extract ~/uqm-voice.delta ../uqm-voice_0.3.orig.tar.gz
The generated tarball is bit-identical to the 19 MB upstream tarball, though you have to gunzip them both to check this, since the gzip compression differs. The delta file is all of 41k large. The uqm-voice.delta file was created earlier as follows:
joey@kodama:~> pristine-tar stash lib/debian/unstable/uqm-voice_0.3.orig.tar.gz uqm-voice.delta
I've uploaded pristine-tar to incoming.

Joey Hess: git archive as distro package format

The tricky part of using a git (or other rcs) archive as distribution source package format is handling pristine upstream tarballs. One approach would be to try to create a git archive that didn't include objects present in the upstream tarball. Then, to unpack the source package, you'd unpack the upstream tarball, convert the files in it into git objects and add them into the .git directory. This way a pristine upstream tarball is available for verification, and it also has the same properties of not needing to re-upload the source for every package release as the current Debian source format. This seems like it might be possible to implement, but you'd need to know quite a lot about git internals to remove the redundant objects from the git repo and regenerate them from the tarball.
Another approach would be to keep the pristine upstream tarball in the git archive, and then the source package would consist entirely of the git archive. This doesn't have the same nice minimal bandwidth upload behavior -- unless you can git push your changes to do the upload. Storing a lot of upstream tarballs in git wouldn't be efficient, but I've written pristine-tar to take care of that. :-)

30 September 2007

DebConf team: DebConf maintenance (Posted by Joerg Jaspert)

In the last few days we (as in DebConf admins Steve Gran, Mark Hymers and myself) have been doing some DebConf maintenance work. Some time ago one of DebConf’s permanent sponsors, ByteMark sponsored a new machine, krabappel, which we use as a replacement for the older machine we have from them, cmburns. It was neccessary, as good old cmburns had a lot of stuff running and so was always pretty loaded. Imagine it running most of our websites, main mail and dns server and then also having 4 vserver instances on it. Those vserver itself where also running things that do use some resources, like our wiki and the main DebConf7 site, the PentaBarf test-host and our LedgerSMB instance. While it was long decided to move stuff our - we just had to find time to do it. This weekend seems to be it, everything is migrated except cmburns itself, as that needs a fix in the reverse dns entries for the new /28 we got. We are using xen-tools to make installation of new images easy. For that I wrote a script that is used as a role script, automating all that various setup tasks that one can automate easily. Which means that it takes about 5 minutes to get a complete new XEN domain up and running. (Add some minutes to add it to nagios2, munin, our mail setup and to sync the userdatabase.) Mark and Steve also did another migration: gallery.debconf.org is now using gallery2. Still needs a nice layout designed looking similar to our normal DebConf website, but that shouldn’t be too hard to get. While they have been on it they also integrated gallery.debian.net, so that it is back up again. Feel free to use both of them! gallery.debconf.org offers space for all DebConf related pictures, be it the main yearly DebConf (and related) or regional DebConfs, like the one planned for Panama soon. gallery.debian.net is a place where pictures from all Debian related events/parties/whatever can be put. Basically - whenever people working on Debian meet (like a BSP, a work meeting, etc) - feel free to put pictures up there. Just put them into a folder matching the year it happened in… Basic goal is to get a huge set of pictures from people involved in Debian.

Marc 'Zugschlus' Haber: Booting from USB stick on older hardware

I spent the better part of the weekend with trying to get an older Athlon XP mainboard to boot grub from an USB stick. Unfortunately, without success. Since a few months, my notebook boots Windows XP when it is booted naively. Only if the correct USB stick is plugged in on boot, the Debian system that I work with comes up. The USB stick has grub, a kernel and an initrd which is used to boot and unlock the crypto file systems (crypted LVs) on the disk and can be removed once the system has booted. I wanted to use the same scheme for a “newly built” new desktop from old parts. Unfortunately, this was much harder than I expected. Since a few years, I use the USB-ZIP format for USB sticks that need to boot. It has shown that this format has the best chance to successfully boot. For more information about this format and about how to build it, see /usr/share/syslinux/README.usbkey on any recent Debian system with syslinux installed. My grml USB stick that I always have on me is formatted like this, and the “new” desktop boots it just fine. The boot stick for my notebook is an USB-ZIP as well, only that its primary partition is not FAT, but ext3. Unfortunately, the BIOS of the “new” desktop seems to refuse booting grub. Neither my notebook’s stick nor the new stick even come to the “loading stage x” output of grub, let alone to the menu. syslinux works fine, and both sticks boot just fine on my notebook and on a qemu on the “new” desktop. Since the grub command line has saved me multiple times in the past, I didn’t really like the idea of having to use syslinux, and decided to boot the “new” desktop conventionally from hard disk without the use of an USB boot stick. Until I got this far, the complete saturday and the better part of sunday was wasted. Darn. This reminds me of a mainboard from 2002 (incidentally from the same vendor), which checked whether the first hard disk had an active primary partition on it before it even tried to execute the MBR code. If no primary partition was found (which was common case with the partitioning scheme that I used back then which only had logical drives - this was before I discovered LVM), the BIOS gave the error message “Not found active primary partition” (sic!) and refused to boot. Stupid programmers trying to outsmart the sysadmins of their products. But at least, the error message was reasonably clear back then.

Next.

Previous.