Search Results: "ag"

22 April 2007

Neil Williams: Mandatory -dbg packages for libraries

I'd like to see all library source packages having a minimum of 4 binary packages required by Policy: the SONAME, the -dev (without SONAME), the -dbg (with SONAME) and a -doc package (without SONAME). (Libraries for perl or other non-compiled languages would be exempt from -dbg packages but not -doc.)

Currently, only a -dev is mandated. I'm currently writing a GtkHTML extension for quicklist and writing code to use an undocumented library is PITA.

Libraries without a -dbg are worse because Debian doesn't need any upstream involvement to create -dbg packages. Things like that make Debian a nicer environment to be upstream, not just a nice environment to be a DD or user.

Are there libraries written in compiled languages that cannot provide a -dbg?

Masayuki Hatta: GNU a2ps 4.13c-rc4 released

GNU sysadmins gave me permission some days ago, so I uploaded my work to alpha.gnu.org for the first time. You can obtain it from:
ftp://alpha.gnu.org/gnu/a2ps/a2ps-4.13c-rc4.tar.gz
I uploaded new Debian a2ps package to ftp-master, too. Let's see what buildds are gonna say... BTW, it seems Gentoo people have already "released" 4.13c (for example, look here) somehow. Hmm...I might have to number the new one as 4.14.

Tag this post with del.icio.us!

Christian Perrier: Vote - 1st round

So, today is the first round of the French presidential election. I already explained where is my preference going, also who I fear the most and who I absolutely don't want ever (no link here: I will never give a link to this guy and his party's web site. You don't want to read the kind of crap they write, do you? This is of course Le Pen). For those reading this and not familiar with the French presidential eletion voting system, a few more hints: We have 12 candidates this year. on first round, a president may be elected if (s)he gets more than 50% of votes (not counting white and null votes). This is of course nearly impossible. The highest probability is thus for a second round. Here, the two best ranked candidates would stay and the president is elected among one of them two. That second round will happen on May 5th. Candidates are (non neutral comments!): Though choice, isn't it? Out of these 12, 4 have some chances to reach the second round: Bayrou, Royal, Le Pen and Sarkozy. It is pretty sure that Sarkozy will reach the second round (unfortunately, should I say). Bayrou and Royal have the best chances to be the second candidate (apparently the disaster of 2002 where Le Pen reached the second round will not happen, though still possible). So, let's vote and vote well...but, first of all, vote! See you at 20:01 +02:00.

Erich Schubert: DBus-Inspector

Interest in my DBus inspector has been increasing. I received a couple of interesting mails these days. Two people have suggested I could add a command line version, which would be similar to "dbus-send", but use introspection data to assist in finding the appropriate values. There was also a request when I'll add invocation support to the dbus-inspector GUI (that's the big thing on my wishlist, btw.)DBus-inspector was also packaged for Foresight linux, and I'll maybe upload a package to Debian these days.[Update: first parts of the 'invocation GUI' are committed. It has a column for 'in' parameters that you can edit, and an execute button that is only enabled when you've clicked on a method. But it doesn't do actual invocation yet when you click that button.]

Wichert Akkerman: Debian upgrade experience

With the recent release of Debian etch (usability note: why can't that URL be per-release? All the info on sarge suddenly is not reachable at the location people bookmarked anymore) I figured I would try upgrading some servers to it. Debian has always had excellent in-place migration handling, so this should be easy, right? If only.. I will stay with sarge for a while longer.

Christian Perrier: News from the debconf review project

Three weeks after I officially announced the launch of the Smith Review Project, it is time to send a status update. First of all, and again, this was not an April Fool's joke. Sent on April 1st, but mostly because that day was a Sunday, the day where I have enough time to work on such annoucements. The task of reviewing debconf templates (and debian/control files) began in March 2007, much before the project is officially launched. Up to now, 17 packages have been reviewed. Several others are under work (I have 15 of these for which I'm coordinating the various review steps). The traffic on debian-l10n-english is exploding. OK, up to now, more than half of this are messages from me, which I expect to slowly change. The process is very well accepted by package maintainers and it really seems there was a need for it. The challenge now is that there are many more texts to review in Debian such as man pages (for native packages), README.Debian files and many other documentation files. We really need help and not only from people whose native language is English. Yes, that means *you* who are still reading my logorrhea.

Michael Prokop: Booting from USB pen: troubleshooting and pitfalls

As grml supports booting from usb devices (harddisk installation via grml2hd as well as booting from usb pens via grml2usb) and I helped many people at debugging booting problems I think I stumbled upon every existing pitfall. 8-) There are several situations where booting might fail. So here we go with a summary of the most common pitfalls and possible solutions:
  1. The Bootsplash is displayed, the kernel loads but you very soon get a:
  2. ran out of input data
    System halted
    
    Reason: everything OK, except for the filesystem used on your usb device. So instead of fat16 you use for example fat32. Fix: use the appropriate filesystem (fat16 for usb pens usually).
  3. When trying to boot from USB you get something like:
  4. Invalid operating system
    
    Possible reason: the partition layout is not ok. Very probably there’s no primary partition or none has the flag ‘bootable’ set. (Read on for further details.)
  5. When trying to boot from USB you get something like:
  6. No operating system found.
    
    Possible reason: you forgot to set the boot-flag on the partition. Or you did not install an operating system at all. ;-)
  7. When trying to set up the partition(s) on the USB device cfdisk reports something like:
  8. FATAL ERROR: Bad primary partition 0: Partition ends in the final partial cylinder
    
    Reason: the partition layout is not ok. Either use fdisk (requires detailed knowledge about partition setup!) or better: use a fronted of libparted, like gparted. gparted does an excellent job at setting up an appropriate partition layout for booting from USB (read on for details about the correct setup). As long as cfdisk has problems with the layout - it will exit on errors - your usb pen very probably does not have a valid partition setup for booting. Please notice that fdisk very often uses defaults which are not OK, whereas gparted uses the appropriate heads, sectors/track and cylinders settings. So if you really want to use fdisk for setting up the appropriate partition layout you might have to enter the ‘extra functionality (experts only)’ menu of fdisk.
  9. The system never displays the bootsplash of the usb device at all? Checklist:
    • does your system support booting from USB at all? Check settings in BIOS.
    • do you use the correct USB mode in BIOS? Check BIOS again, usually you want to use USB-HDD mode. Not possible? See USB-ZIP mode.
    • is "booting from USB" in the appropriate order of the booting sequence? Check the "boot"-section in your BIOS.
    • is the bootable flag set on the boot-partition? Check for example with cfdisk.
    • is the partition used for booting the first partition and a primary one on your device? Check with cfdisk again.
    • is the partition layout ok? The first partition (the one used for booting) has to start at cylinder 1/sector 63, otherwise booting will fail on most (all?) x86 systems. Check with ‘cfdisk -P s /dev/..’ or ‘fdisk -l -u /dev/…’. Do *not* trust the output of ‘fdisk -l /dev/…’. Really.
  10. syslinux does not work on your system (b0rken BIOS for example)? Possible solution: use grub instead.
  11. Kernel boots but fails to find the root filesystem with something like:
  12. kernel-panic: unable to mount root-fs...
    
    Yes? Then the root= argument in your kernel commandline (specified in the bootloader, usually lilo, grub or isolinux/syslinux) is pointing to the wrong device. Solution: adjust the root=-option in your bootmanager’s configuration. Tip: use root=UUID instead of root=/dev/[hs]d…
  13. All of the above tips don’t work? Maybe your USB pen is even larger than 1GB?
  14. Possible reason: Some BIOSes offer different modes for USB booting. The proper mode to boot a USB stick is USB-HDD. If that doesn’t work or is not supported by your system, you need to format your USB-Stick as USB-ZIP. To do this, the syslinux source distribution contains an utility called mkdiskimage, which you can use to re-format your USB stick in USB-ZIP format. For more information refer to the USB-webpage in the grml-wiki and Bootable USB Key in the knoppix-wiki.
I mentioned the correct partition layout several times. Reminder: a first, primary partition with fat16 (as filesystem as well as partition’s system id!) with bootable-flag set. The partition should start behind MBR at 1st cylinder and 63rd sector (see www.ata-atapi.com/hiwmbr.htm and thestarman.pcministry.com/asm/mbr/index.html for more details about MBR). So how does a correct partition look like? Output in several formats as reference:
# fdisk -l -u /dev/sda
Disk /dev/sda: 1039 MB, 1039663104 bytes
255 heads, 63 sectors/track, 126 cylinders, total 2030592 sectors
Units = sectors of 1 * 512 = 512 bytes
   Device Boot      Start         End      Blocks   Id  System
/dev/sda1   *          63     2024189     1012063+   6  FAT16
# fdisk -l /dev/sda
Disk /dev/sda: 1039 MB, 1039663104 bytes
255 heads, 63 sectors/track, 126 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
   Device Boot      Start         End      Blocks   Id  System
/dev/sda1   *           1         126     1012063+   6  FAT16
# sfdisk -d /dev/sda
# partition table of /dev/sda
unit: sectors
/dev/sda1 : start=       63, size=  2024127, Id= 6, bootable
/dev/sda2 : start=        0, size=        0, Id= 0
/dev/sda3 : start=        0, size=        0, Id= 0
/dev/sda4 : start=        0, size=        0, Id= 0
Tip: if you have a working stick, store your partition layout using ’sfdisk -d /dev/sda > sfdisk.sda’ for later restore (via ’sfdisk /dev/sda < sfdisk.sda’). This is also very useful for cloning a working setup to other devices (though you might have to adjust cylinder/units later on). And of course you can use it as backup if you ran [sc]fdisk-commands on the wrong device. ;-)

Andrew Pollock: [life] Parental visitation

My Mum and Dad arrived today for a three week visit. We're hardly seeing them though. They fly out on Tuesday to the east coast, to see New York, Washington DC and I think the Niagara Falls for seven days. When they get back, we're all heading to Las Vegas to check out the Grand Canyon, then they're off to Vancouver and to see the Rocky's. After that, they're back for a few days, then they leave again. Their itinerary makes me feel tired.

21 April 2007

Christian Perrier: bzr rant

The time has come for me to rant again about the crazy world of VCS. I noticed today that a few things changed in apt l10n and I wanted to resync with Michael Vogt's bzr archive. I was first notified about some archive format change and was suggested to run some magic spell to bring my archive to the Wonderful World of bzr 0.whatever_new_version. Fortunately, it worked, which is good because I have no bloody idea of how I can reconstruct a broken archive. Then, unfortunately, when trying to push these changes to my public archive (the one used by maintainers for l10n changes):
bubulle@mykerinos:~/src/debian/apt/bzr/apt/main> bzr rspush
kheops.homeunix.org:/home/www/www.perrier.eu.org/debian/packages/d-i/level4/apt-main
Bzrtools is not up to date with installed bzr version 0.15.0.
There should be a newer version available, e.g. 0.15.
Unable to load plugin 'bzrtools' from
'/usr/lib/python2.4/site-packages/bzrlib/plugins'
bzr: ERROR: unknown command "rspush"
So, again, something changed in bzr stuff. bzrtools is then broken, the rspush command I'm using for a while now is broken and I can't publish my changes anymore. Of course, while I'm fighting with this, the good old SVN for D-I still works like a charm just like it's doing since December 2003 when Joeyh migrated from CVS to SVN. Joey, Frans, promise me you'll never ever switch to this distributed hype and keep our good old, crappy, limited but rock solid SVN. This was the rant of the day.

Erich Schubert: More AppArmor FUD^W PR:

I didn't intend to write (ok, rant...) on this topic again, but a few days ago, this "AppArmor FAQ", was posted to the Linux Kernel Mailing list. Again, this is a lot of 'marketing stuff', and doesn't have the facts quite right...Some quotes:
In the traditional UNIX model, files do have names but not labels, and applications only operate in terms of those names.
No. In the traditional UNIX model, filenames point to inodes, and the inodes contain data such as file modification dates and permissions. This is where SELinux stores the labels it uses for access control. In fact, the "unix owner" and "unix group" are pretty much the same thing as SELinux labels. And also work pretty much the same way.
Contrary to popular belief, AppArmor is *not* "Pathnames R Us", but rather "Use native abstractions to mediate stuff": when you mediate something, you should use the native syntax that users normally use to access the object.
Maybe the appropriate term would have been "naive abstractions"?And, no, security systems shouldn't be designed around what a user can easily grasp, because that might just not work... it should be designed around the way resources are handled and how you can successfully restrict access."Contrary to popular belief", SELinux *does* use path names. Actually in a very convenient way for the users. So I wouldn't claim SELinux is really harder to use than AppArmor because of its use of path names.The difference is that SELinux doesn't rely on the path names, but it still gives the user the possibility to use them. In fact, the only way I know to get a proplerly labeled filesystem is based on path names.If I'd for example keep my web stuff in /home/www, I can tell SELinux that the appropriate label is httpd_sys_content_t by doing
semanage fcontext -a -t httpd_sys_content_t /home/www
restorecon -R /home/www
In AppArmor, I'd need to modify the policy for several applications to achieve this, because of it's dependency on path names. SELinux also uses an abstraction. One that is very convenient for users actually. SELinux does access control on object classes. What I'm doing in above example is to put these files into the "Web site data files" class. So please stop scaring people of "labels". That is just the technical term for what is an "object class", a concept every developer will be familiar with. (SELinux policy development has a couple of OOP-like features, btw., for example it is possible to give an application access to 'all log files'.)There are, however, some true statements hidden in there:
We also acknowledge that pathname based access control requires a way to perform pathname matching in the kernel, and this comes at a cost higher than comparing object labels [...]
So by providing string matching in the kernel, AppArmor trades run-time performance to grant reduced administrative work. It is however not obvious how large the difference in "reduced administrative work" is between AppArmor testing the filename "run-time" compared to SELinux using filenames to relabel files "on demand" (or, with restorecond, even on creation by using inotify).What I still seriously dislike is the FUD spread by AppArmor people such as
Label-based security (exemplified by SELinux, and its predecessors in MLS systems) attaches security policy to the data. As the data flows through the system, the label sticks to the data, and so security policy with respect to this data stays intact. This is a good approach for ensuring secrecy, the kind of problem that intelligence agencies have.
Why should this only be useful to "intelligence agencies"? Some people live in countries with very strict privacy requirements, and we might want to use these techniques to lessen the risk of leaking data. In AppArmor, I can copy a file with private customer data to the web server directory, and it becomes readable by the web server. In SELinux, the file will still be unreadable by the web server. Does that really sound like "only useful to intelligence agencies" to you?Dear AppArmor people, please stop trying to invoke fear of the NSA, just to make people use AppArmor. That makes you look very untrustworthy, you know...The SELinux kernel code is part of the Linux kernel, AppArmor is not. So in theory, that code has been reviewed much better than yours, and is maybe even less likely to contain a "NSA backdoor" than yours. Changes to SELinux are openly discussed on a mailing list, and go through peer review there. They foolow a very strict coding style, which makes review easier; obfuscated code doesn't have a place there. It's not like we were running a binary blob from the NSA we can't have a look at.

Patrick Winnertz: Test Release 3 of Etch-based Debian-Edu/Skolelinux available!

Hey! Today (5 minutes ago) the third test release of Debian-Edu/Skolelinux 3.0 (Codename Terra) is released. Here the announce:
The Debian-Edu/Skolelinux project is pleased to announce that the next test release of “Debian-Edu/Skolelinux 3.0 codename terra” is ready. This is the third test release based on debian/etch. It is available from FTP, HTTP and rsync.

Highlights

  • Based on the recently released Debian/Etch.
  • Released as DVD image, with a lot more translations and applications available.
  • Includes ltspfs for local device access from thin clients.
  • Improved laptop support.
  • And a lot more…
The ISO image is 4.4 GiB. To download it, use either of these methods:

ftp://ftp.skolelinux.org/skolelinux-cd/debian-edu_etch-i386-test03.iso
http://ftp.skolelinux.org/skolelinux-cd/debian-edu_etch-i386-test03.iso
rsync ftp.skolelinux.org::skolelinux-cd/debian-edu_etch-i386-test03.iso

Nico Golde: Errm Mark Shuttleworth...

Today I read an interview on Golem and there was a question about Debian's relationship to Ubuntu.

Mark Shuttleworth answer includes the following statement:
"Wir wollen so effizient wie m glich mit Debian zusammenarbeiten und investieren daher auch, beispielsweise indem wir alle an Ubuntu-Paketen durchgef hrten nderungen an den jeweiligen Debian-Maintainer zur ckgeben."

Which says that they want to co-work with Debian as efficient as possible and that's why they also invest in Debian for example with sending all the changes on Ubuntu packages back to the Debian-maintainer.

I am sorry, I never really said my opinion about Ubuntu in public since I think this wouldn't be really productive for the problem but that is just a lie in my opinion.
I won't state any further here but I never ever received a patch for the fetchmail package from Ubuntu.

Daniel Burrows: Wikified aptitude TODO list.

I've been able to crib more time lately for Debian, so I'm hoping that I can stop just keeping my head above water (barely) and start on the pile of new work that I'd like to do. For a while I've been accumulating a mental list of stuff that sucks in aptitude, but mental lists have the drawbacks that no-one else knows about them and that they never seem to be available when I want them.

I've now got a nice page in the Debian wiki holding aptitude's current TODO list. The entries range from changes that are trivial but will improve the user experience, to deep and difficult changes that no-one will notice. Since I don't expect a team of magic pixies to do the coding for me, I figure I might have the majority of the design and coding done in a year or so.

Biella Coleman: Re-public: Re-imagining Democracy in our own (male) Image

The online journal re-public: re-imagining democracy has a handful of articles on collaboration and wikipedia, adding to two special issues on reimagining the commons. Many are good. But I am disturbed over the true paucity of diverse voices, including women. The recent slew of articles does not have even one authored by a woman and there are only 2 represented in the re-imagining the commons special issues. Given that there are many woman researchers and practitioners who do work on this material, I honestly don’t think this represents a lack but a problematic oversight. Problematic most especially because they are “re-imagining democracy,” and this does not look to imaginative to me.

Julien Blache: Call for help: SANE

I am currently going through the SANE bugs reported on bugs.d.o. There are quite a few of them, and verifying them already takes a long, long time; fixing them is another story entirely, given I own none of the affected scanners or platforms. I’ll be going through the bugs this week-end, re-reading the logs, tagging/retitling as needed so hopefully the list will be easier to read. If you have - or are affected by - an open bug against SANE, please try to reproduce the bug on an up-to-date unstable system. I’ll be uploading a CVS snapshot to unstable today for that purpose. SANE is a complex piece of software that is best maintained in a team, if only because there’s so much hardware involved that the more maintainers you have, the more different hardware you can have too. If you have a scanner, have some knowledge about USB, shared libraries, GTK among other things and want to help, mail me and tell me what you can/want to do. Some knowledge about SCSI can help too, though SCSI scanners aren’t exactly mainstream anymore. I currently own only 3 scanners, one old SCSI scanner and a pair of nearly identical USB scanners; so that really makes 2 scanners. If you have some scanners lying around that you don’t use anymore, I (and the SANE developers too) could probably use them. I’m primarily interested in any scanner that is involved in one of the bugs currently open against SANE. I’m also looking for a scanner supported by the epson backend (the Epson scanners I have are supported by the snapscan backend). Now, back to these damn bugs.

Masayuki Hatta: R.I.P. Andrew Hill

Jazz pianist/composer extraordinaire Andrew Hill died yesterday. He was 75 years old. I love his music. I even gave a lecture on his music several years ago. I have a great regard for someone who follows his own logic, challenges the mainstream mode AND achieve artistic excellence. In many cases, so-called "avan-garde" are hard trying to do things different, but their results are not impressive aesthetically. Hill achieved both. And boy, he swang hard when he wanted. I'll miss him.

Tag this post with del.icio.us!

Andrew Pollock: [life/americania] On the right to bear arms

Steven's blog post reminded me that I had to make a note about the two email responses I received to my own. I received one email from Pro Guns Person A quite quickly after my blog post went up. He was quite civil, and had things to say such as:
The truth is, if a few good citizens were armed and nearby, they would have had a chance to stop the killer before he could do any more harm.
and went on to say how if a person really wanted to, they'd break laws to get guns, so gun control doesn't achieve anything, except leaving the good guys unable to defend themselves. Sure, they'd break laws to get guns. You can't stop them if they really want to, but you can make it harder. And you have to make it harder universally. It's no good if one state cracks right down, if people can just pop over to the next state and pick up a firearm instead. I agree with Steven. Leave the gun toting to the people trained in their use (i.e. law enforcement). Frankly, it disturbs me that "defending yourself" equates to being able to shoot the attacker. I think it's Texas where you can legally shoot trespassers. Scary stuff. Pro Guns Person A went on to say:
To close, again without intending offense, please do not call for gun control if you aren't even a citizen of this country. The real problem is the societal issues that drive people to do these things. The truth is, fifty years ago in this country, people could leave loaded guns in their unlocked cars, even in high school parking lots...and nothing like this ever happened. But now, even though we have far more restrictive gun laws, things like this do happen, because of the societal problems.
I have the right to express my opinion, irrespective of my citizenship, as do you, Mr Pro Guns Person A. You don't have to like my opinion, just as I don't have to like yours, but I respect your right to have your opinion. No offense taken, either. You were very polite in putting across your point, I appreciate it. (By the way, I agree. Society's gone to pot.) Pro Guns Person B's email was along a similar theme: the bad people will always get their mitts on a gun, and the good people won't be able to defend themselves.
Think about these figures (I'll write about the US, since that's the nation you wrote about now): In the state of Arizona the gun per person ratio is 2,5 (on average 2,5 guns owned by 1 person, and these are the legally purchased ones). In the state of New York there is an official prohibition on guns. So why is it that New York has the higher armed crime rate among those two? (and one of the highest across the country)
I don't think reverting the entire US to a "wild wild west" scenario is really going to help matters at all. Sarah was saying that she'd found some statistic somewhere, probably saying something like what this page is saying. Now this was done at a Federal level, so that's why it worked, whereas anything done piecemeal, is going to cause a situation like what Pro Gun Person B was describing in his email.

Dirk Eddelbuettel: Boston Marathon 2007

So this Monday was the 111th running, as they call it, of the venerable Boston Marathon, and my first time there. After the fairly serious storm warnings -- and the corresponding health warnings, delivered through two emails from the race organizers and a handout at registration, we got very, very lucky as the rain more or less stopped shortly after the start. And there was relatively little wind, and mostly laterally, rather than the 'in your face' gusts at the projected 30 to 50 mph.
There were actually six of us running from our little informal group in River Forest / Oak Park, and fellow rookie Russ and I decided to 'take it easy' and just 'go for a long run'. I ended up with a fairly even pace between 7:45 and 8:10, averaging 7:57 for a total of 3:28:24, or a few seconds faster than my very first marathon in Chicago. Which is quite pleasant, given the conditions, and the hillier course. The race went pretty well for all six us, which is nice too. Given how we trained together, it is neat how we all ended up within seven minutes of each other. The race itself is quite stunning. With the required qualifying time comes a 'seeding' system for the start, so one tends to run most of the course with runners of fairly similar speed. That made for nice cameraderie on the course -- and for beautiful sights of nothing but runners rolling through the hills of Massachusetts. I think I'll be back next year.

20 April 2007

Romain Francoise: On SVK

Like Joerg, I use SVK to work offline with Subversion repositories, and I'm mostly happy with it. The only annoyance is that its memory usage can be quite insane on large repositories, which makes it very slow. I hear that SVK 2.0 is better in this area, but it's (still) not packaged for Debian (see bug #408306).

Romain Francoise: Read/write NTFS under Linux

While I wasn't looking, someone implemented a read/write NTFS driver for Linux, using FUSE. It's called ntfs-3g and appears to be working well!

NTFS is now a good choice for USB/Firewire hard drives:

Next.

Previous.