published on Sun Feb 22 05:00:28 2009 in packages-news
Article submitted by Donn Ingle. We’ve run out of articles! If you like Debian Package of the Day please submit good articles about software you like!
Fonty Python is available from the
fontypython package in both Debian and Ubuntu in Universe. Fonty is a wxPython app so will work in any desktop environment. It also has a command-line interface which avoids the gui.
What the font?
As a graphic designer, one is called-upon to create artwork for many things. Fonts change from one client to another, from one job to another. If busy enough, then one can soon amass a vast pile of font files. Some are downloaded from the net as freeware, others are purchased, others are supplied by the clients for their work.
These font-files are stored somewhere, independently of the system fonts managed by the Debian package manager, possibly sorted in whatever fashion you prefer. It’s crazy to have these fonts all installed at the same time. Besides whatever that may do to your computer’s speed, it has one gigantic drawback: it clutters up font-selection boxes. Have you ever tried to find a font in a list of 500 fonts? Bleh.
What you need is a way to herd fonts and that’s what Fonty does.
Bring out yer fonts!
Think of Pogs as “groups”, “bags”, “cases”, “boxes” —that kind of thing. It’s an oddball word invented to describe a bunch of font files.
Ye olde basic idea
You visually gather fonts into Pogs. You then install a Pog and all the fonts within it are active on the system. You finish your work and then uninstall the Pog.
Your fonts never move from where they live (so don’t worry). Neither are copies of your fonts made; only links to the original files are used to install the fonts into your home
For example, you might have a Pog called
logoZoo into which you place all the TTFs you need to design a logo for a Zoo. After that, when you need to work with them, you simply install the
logoZoo Pog and start your design app. All those fonts will now appear in Inkscape or The Gimp, and other apps. Do your work as normal, and forget about fonts.
When you are done designing, you uninstall
logoZoo and all those fonts go away. The links to the original files are removed from your home .fonts
directory, effectively uninstalling each font.
Fonty is also great for just looking at fonts wherever they are on your computer, without having to install them first. Fonty also has a command-line, allowing very quick use. You can install or remove pogs without having to start the entire gui, which is neat.
The layout of Fonty is supposed to be as simple as possible. I stayed away from context-menus and drag and drop because I find them hard to use. The flow is left-to-right with the sources of fonts on the left and their
targets on the right.
- Point 1: You choose a Source Folder (or Source Pog) on the left.
- Point 2 & 3: You then see the fonts in the middle. You can page or Point or search around (Points 5,7). You click the fonts you want to use.
- Point 4: On the right, you choose a Pog, or make a new one.
- Point 6: Once you have a Target Pog selected, you can place fonts that you ticked into it.
- Point 8: On the bottom-right you then Install or Uninstall Pogs as you need them.
- There is a settings box (ctrl+s) where you can change the sample text and sizes.
- Check the help too — it’s full of tips and quite short.
Some fonts are simply bad to the bone. Fonty relies on freetype and PIL to open and draw the glyphs, and when this fails so does Fonty. I have put a lot of effort into catching this, but it does not always work. When a font crashes Fonty, you should get a popup box telling you which one did the deed. You really ought to remove that font! Some fonts cannot be displayed, and Fonty will show that by using coloured bars in the display area.
There is also a menu item (File > Check Fonts) that you can point at a given directory and scan it for fonts that will crash Fonty. Use this when you want to cull all the fonts that are bad.
Originally, Fonty could only show TTF files. Since then I have expanded it to include OTF, Type1 and TTC files. As far as I can tell, being only seminiscient, this all works.
Fonty speaks your language; or it will if you translate it. There are a few translations available and you can join the project to contribute others.
Fonty needs help
With Python heading for version 3 and all kinds of other changes, Fonty is falling behind. She still works quite well, but I cannot spend the time I want to on her. If there’s anyone out there who wants to stick a fork in her and run —please do.
I hope to find some time this year to have another go; fix some bugs and include a few translations I have been sent, but I can’t be relied upon.
published on Sun Feb 15 05:00:48 2009 in packages-news
Article submitted by Geoffroy Youri Berret. We’ve run out of articles! If you like Debian Package of the Day please submit good articles about software you like!
localepurge allows you to remove unnecessary locale data you have on your system and prevents installing unneeded locales when installing new packages.
During the initial installation of localepurge you’ll be asked which languages you want in your system. The installation process will ask you if you want to purge also manpages for unwanted locales. Once installed, localepurge will be launched each time you install a new package on your system and will inform you of the amount of space you saved.
On a regular desktop installation you may save up to one hundred or more MiB. Even though space is no longer that expensive, this kind of tool might still be useful on netbooks, laptops and, in general, mobile technology with limited disk space.
nota bene: You have to be aware that localepurge is considered a hack of the package system, this is not a feature (localepurge(8)). localepurge is independent and not a part of dpkg/apt. Consider using it at your own risk. This warning sounds worrying but my personal experience of localepurge for the past 5 years tells me there is no reason to be afraid of —I never identified a problem on my system I could blame on localepurge. It’s nonetheless important to keep that in mind.
Let’s see of efficient it is with a mplayer installation on Debian Lenny for instance:
Preconfiguring packages …
Selecting previously deselected package libopenal1.
(Reading database … 95241 files and directories currently installed.)
Unpacking libopenal1 (from …/libopenal1_1%3a1.4.272-2_i386.deb) …
Selecting previously deselected package mplayer-skin-blue.
Unpacking mplayer-skin-blue (from …/mplayer-skin-blue_1.6-2_all.deb) …
Selecting previously deselected package mplayer.
Unpacking mplayer (from …/mplayer_1.0~rc2-17+lenny3_i386.deb) …
Processing triggers for man-db …
Processing triggers for menu …
Setting up libopenal1 (1:1.4.272-2) …
Setting up mplayer-skin-blue (1.6-2) …
Setting up mplayer (1.0~rc2-17+lenny3) …
Configuring mplayer …done
Processing triggers for menu …
localepurge: Disk space freed in /usr/share/man: 780K
published on Mon Feb 9 00:00:00 2009 in weekly-news
Welcome to this year's second issue of DPN, the newsletter for the Debian community. Topics covered in this issue include:
published on Sun Feb 8 05:00:06 2009 in packages-news
There are many command-line utilities in the Unix / Linux world that collect network traffic statistics for a chosen interface.
vnstat is different because statistics are collected permanently. It keeps the data in files so traffic monitoring is resumed at reboot. vnstat can be useful in situations when you need to know the exact amount of traffic that goes through the interface for a period longer than the computer is on. For example when you have a mobile 3G internet connection or an xDSL connection that has traffic limit per month, then you can easily check how much traffic you generated.
vnstat can be run without root privileges because it collects data from the kernel’s proc filesystem. It doesn’t have a daemon service, it is simply run by cron periodically. In Debian, the installation creates a cron job where a vnstat -u command is run every 5 minutes:
# /etc/cron.d/vnstat: crontab entries for the vnstat package 0-55/5 * * * * root if [ -x /usr/bin/vnstat ] && [ `ls /var/lib/vnstat/ | wc -l` -ge 1 ]; then /usr/bin/vnstat -u; fi
Initially, you have to create the database with this command:
vnstat -u -i wlan1
After creating the database, the statistics can be viewed by running vnstat without any further parameters. Thanks to the cron job, the statistic is updated every 5 minutes. It even remembers the interface name to list:
$ vnstat Database updated: Tue Jan 27 15:40:01 2009 wlan1 received: 2.18 GB (81.3%) transmitted: 512.85 MB (18.7%) total: 2.68 GB rx | tx | total -----------------------+------------+----------- yesterday 95.14 MB | 12.19 MB | 107.32 MB today 11.33 MB | 4.47 MB | 15.80 MB -----------------------+------------+----------- estimated 16 MB | 6 MB | 22 MB
Some command line options allow you to view statistics for specific periods of time. For example:
$ vnstat --days wlan1 / daily day rx | tx | total ------------------------+-------------+---------------------------------------- 18.01. 231 kB | 115 kB | 346 kB 19.01. 611.72 MB | 58.16 MB | 669.88 MB %%%%%%%%%%%%%%%%%:: 20.01. 400.53 MB | 200.70 MB | 601.23 MB %%%%%%%%%%%%%%::::: 21.01. 5.87 MB | 1.56 MB | 7.43 MB 22.01. 417.97 MB | 108.94 MB | 526.91 MB %%%%%%%%%%%%%%:::: 23.01. 365.24 MB | 41.78 MB | 407.02 MB %%%%%%%%%%%%:: 24.01. 150.00 MB | 13.42 MB | 163.43 MB %%%%%% 25.01. 170.17 MB | 71.52 MB | 241.70 MB %%%%%%::: 26.01. 95.14 MB | 12.19 MB | 107.32 MB %%%% 27.01. 11.36 MB | 4.51 MB | 15.87 MB ------------------------+-------------+---------------------------------------- estimated 16 MB | 6 MB | 22 MB
$ vnstat --weeks wlan1 / weekly rx | tx | total ----------------------------+---------------+-------------- last 7 days 1.19 GB | 253.93 MB | 1.44 GB last week 2.07 GB | 496.08 MB | 2.56 GB current week 106.52 MB | 16.71 MB | 123.23 MB ----------------------------+---------------+-------------- estimated 456 MB | 68 MB | 524 MB
$ vnstat --months wlan1 / monthly month rx | tx | total -------------------------+--------------+-------------------------------------- Jan '09 2.18 GB | 512.90 MB | 2.68 GB %%%%%%%%%%%%%::: -------------------------+--------------+-------------------------------------- estimated 2.53 GB | 596 MB | 3.12 GB
$ vnstat --top10 wlan1 / top 10 # day rx | tx | total -------------------------------+-------------+--------------------------------- 1 19.01.09 611.72 MB | 58.16 MB | 669.88 MB %%%%%%%%%%%%%%%%:: 2 20.01.09 400.53 MB | 200.70 MB | 601.23 MB %%%%%%%%%%%::::: 3 22.01.09 417.97 MB | 108.94 MB | 526.91 MB %%%%%%%%%%%::: 4 23.01.09 365.24 MB | 41.78 MB | 407.02 MB %%%%%%%%%: 5 25.01.09 170.17 MB | 71.52 MB | 241.70 MB %%%%:: 6 24.01.09 150.00 MB | 13.42 MB | 163.43 MB %%%% 7 26.01.09 95.14 MB | 12.19 MB | 107.32 MB %% 8 21.01.09 5.87 MB | 1.56 MB | 7.43 MB 9 18.01.09 231 kB | 115 kB | 346 kB -------------------------------+-------------+---------------------------------
--livegives real-time statistics about the packets currently going through the interface:
$ vnstat --live -i wlan1 Monitoring wlan1... (press CTRL-C to stop) rx: 113.40 kB/s 99 p/s tx: 28.42 kB/s 96 p/s
Pros and cons
- Permanent network traffic statistic that is not forgotten.
- Very lightweight solution, no daemon service is running in the background (automatically run from cron periodically).
- Easy to install and use. In vnstat, everything can be done from the command line and it clearly shows how many megabytes have you send/receive in a given day or month.
- Internet or remote traffic cannot be separated from local network traffic if it all goes through the interface being monitored.
- It works for a single host, but it doesn’t scale very well. If you need to monitor a lot of hosts and need detailed graphs, there are better alternatives, such as munin or ganglia.
contributed by andremachado, published on Wed Feb 4 00:25:45 2009 in news
Debian 5.0 Lenny is coming: target release date
With the Debian Installer RC2 announcement (and following the plan outlined in the previous release update) we are now in deep freeze, which means that we will only be migrating to testing those packages which fix RC bugs.
The weekend of February 14th is going to be our tentative target for release. We've checked with all the involved teams (which are many!) and the date works for all of them.
The intention is to only lift that date if either something really critical pops up which could not possibly be handled as an errata, or if we end up technically unable to release that weekend (e.g., a needed machine crashes). Every other fix that doesn't make it in time will be r1 material.
We also intend for there to be a "Lenny and a half" release half-way through the Squeeze release cycle, as was done for Etch. If necessary, during the "Lenny and a half" release additional hardware support will be considered.
Read the full announcement.
About the Debian Project
Debian GNU/Linux is one of the free libre operating systems, with a broad list of officially maintained packages on 15 hardware platforms, from cell phones to mainframes, developed by more than two thousand volunteers from all over the world who collaborate on the Debian Project.
The Debian Project's key strengths are its volunteer base, its dedication to Free Libre Open Source Software, to the Debian Social Contract and the non-profit nature Debian Constitution, its open and meritocratic development model, its organization and social governance and its commitment to provide the best operating systems attainable, following a strict quality policy, working with an established QA Team and helpful users reporting bugs, suggestions, exchanging ideas, solutions, and registering experiences during its history.
One can help Debian Project joining it or even not being a programmer, or being a development and or service partner company or institution at the Debian Partner Program, or simply making various donations to the Debian Project.
published on Mon Feb 2 20:42:03 2009 in interviews
A Few Questions For Gustavo Noronha
(english only content here.)
How did you end up using Debian and becoming a DD?
Somewhat of a long story: I started using GNU/Linux because I wanted to learn how to program and I got to know that C compilers were easily available in GNU/Linux distributions. I started with Conectiva Marumbi, in late 1998, and when I bought a Debian CD in early 1999 I was instantly in love.
I felt dpkg was so much better than rpm, at the time, and got to know apt, which made me wonder how something of such high quality was so unknown (a very small number of people even knew Debian existed in Brazil, at the time.)
By reading the Debian foundation documents and its pages about what Free Software means I fell in love with the idea of software freedom, and by getting to know the Debian community I was deeply impressed at the very possibility of such a large body of people voluntarily associating to achieve a common goal. Then I started to make small contributions, and signed up for NM in the last half of 2000; in January 2001 I got my account!
How are you currently involved in the Debian project?
I'm involved mostly in helping on GNOME and Python-related packaging. I maintain some small projects upstream (such as gksu), which I also consider to be “for Debian” (though others do use them). I've been involved in the translation and writing of documents (I used to be the main author of APT Howto), early on, as well as in the translation of DWN, package descriptions, debconf messages and the Debian web page, back in the day.
Though I consider myself quite involved with Debian and its surroundings, these days I am spending more time contributing upstream in projects such as WebKit and Epiphany than in Debian packages themselves. I would say I spend like 20 hours a month in Debian proper.
How do you currently use Debian?
I use Debian as my main desktop operating system. I also use Debian as the operating system of choice for servers I maintain in the company I work at, and in my sister's and mother's computers. These days I am doing lots of development work: python web development as a job, and GNOME-related development for fun.
What do you do when you're not working on Debian?
I enjoy playing FreeCraft with my girlfriend and friends, (and other not-so-free games I'm not going to advertise =P) =). I also enjoy music, and going to the movies. I moderately enjoy traveling, and I do enjoy going out with friends for beer and fun. Recently my girlfriend convinced me to start on some dancing classes, which I am really enjoying. Anyone for some samba, or tango? =)
published on Sun Feb 1 05:00:47 2009 in packages-news
Article submitted by Dmitry E. Oboukhov. Guess what? We still need you to submit good articles about software you like!
Many people use a wonderful bittorrent client: rtorrent. It is an extremely easy and convenient program for servers. However, its Command-Line Interface may scare some.
If you’re already using apache then you may use an external GUI for rtorrent. rtpg-www (RTorrent Perl GUI) is a package package that quite recently appeared in Debian (Sid) and Ubuntu (Jaunty). It will please your nearest and dearest with a nice web interface, as they will be able to run rtorrent without having to touch the dreaded terminal :)
The package comes with an already configured virtual server. In its simplest variant all you need to do is:
- Answer “yes” on debconf’s question about adding a line to
/etc/hosts(only if dpkg asks you medium priority questions)
- Switch on the scgi module with a2enmod scgi
- Enable the virtual server in apache: a2ensite rtpg.apache.conf
- Reload apache to activate the new configuration: invoke-rc.d apache2 reload
- Add “scgi_port = localhost:5000″ to your
Now, you can go to
http://rtpg/ and start using it! With it you can:
- add/delete/view the list of torrents.
- Control torrents’ download priorities, start, and stop them.
- Control torrents’ file-by-file download priorities.
- View the statistics: rating, number of peers, download/upload rate, etc.
- Control the overall download/upload rates (for all torrents).
So install and enjoy! Good luck!