Joey Hess: website backup RFC
So, I'm considering a backup system that has as its goal to let you
backup all your data from third party
websites, easily.
The idea I have for its UI is you enter in the urls for all the sites you
use, or feed it a bookmark file. By examining the URLs, it determines if it
knows how to export data from each site, and prompts for any necessary
login info. The result would be a list of sites, and their backup status. I
think it's important that you be able to enter websites that the system
doesn't know how to handle yet; backup of such sites will show as failed,
which is accurate. It seems to almost be appropriate to have a web
interface, although command-line setup and cron should also be supported.
For the actual data collection, there would be a plugin system. Some
plugins could handle fairly generic things, like any site with an RSS feed.
Other plugins would have site-specific logic, or would run third-party
programs that already exist for specific sites. There are some subtle
issues: Just because a plugin manages to suck an RSS feed or FOAF file off
a site does not mean all the relevant info for that site is being backed
up. More than one plugin might be able to back up parts of a site using
different methods. Some methods will be much too expensive to run often.
As far as storing the backup, dumping it to a directory as files in
whatever formats are provided might seem cheap, but then you can check it
into git, or let your regular backup system (which you have, right?)
handle it.
Thoughts, comments, prior art, cute program idea names (my idea is "?unsilo"), or am I wasting my time thinking about this?
When starting with Python or just when you haven t read
It would appear that debian.org rejected mail for maybe up to twelve hours
from late yesterday afternoon (Central timezone) to some time shortly after I
got up this morning. Things appear to be back to normal, so a big
Thanks to the mail admins.
If you happened to have sent me mail to my debian.org address during that time
period, you may have gotten a hard reject ('550 Administrative prohibition')
as did a test mail of mine. In this case mail may not be respooled, so please
do send it again.
My alternate address, formed by my first name followed by the family name and
the commercial top-level domain, remained functional as a fallback.
Lenny well supported
We re pleased that Lenny released with good support for the Eee PC and are now turning our efforts to make Squeeze even better, while continuing to provide support for our Lenny user base. The standard Lenny installer can install Debian on all models of Eee and our
If you deal with

Here are a few hints if you want your reports to be treated more promptly.
When testing fails, try unstable
If you are running testing, not all bug reports are interesting. More specifically, the relevant ones are about insufficient dependencies that let slip into testing a non-working combination of packages. Think of the I upgraded foo, then bar broke category.
Otherwise, the reason why reportbug looks for newer versions of a package in unstable is that, in most cases, the bug is fixed in unstable. If you can, always try the unstable version before reporting the bug.
Report bugs against the failing package
This is related to printing in a GNOME program, so I report this against libgnomeprint.
Always file reports against the failing program. If there is a library involved, reportbug will include the necessary information so that the maintainer can easily reassign. If you re not sure of the affected package, use a metapackage (for example, gnome for GNOME-related packages).
Do not second-guess the origin of the bug
After upgrading libfoo, bar starts crashing, so I m reporting it against libfoo.
Unless you can tell which function is at fault and how this is ABI breakage, you should report the bug against the program that crashes. The program s maintainer will reassign if needed, and will hit the library s maintainer with a hammer if needed.
Don t forget to explain what s wrong
The frobniz in libfrob is broken, you should change /usr/share/libfrob/blah line 13 to something else. I don t know what libfrob is about, but I have some problems that look frobniz-related.
Do not second-guess, always start explaining what bug you are seeing first. Your attempts at investigating it can be interesting, but don t forget to explain what bug lead you on investigating.
What is the use case we should cover?
I m trying to do that with your package and it looks extremely complicated/doesn t work as expected/fails miserably. Your package is clearly broken!
If your attempts to do something that should be trivial, given the purpose of the package, fail, then you are probably looking at the problem at the wrong angle. There may be a much simpler, though radically different, way to do what you are trying to achieve.
In these situations, always include in your report what you are trying to do and why you want to do it.
strace is not a general-purpose debugging tool
Whether you observe a crash, a deadlock or a livelock, strace is not the tool that will give us information. The only thing you do by adding a strace log to the bug report is making it unreadable with its thousands of lines of output.
For the specific cases that require strace for debugging, these traces are welcome but if you re not sure, don t attach them. The developers will ask them for you. Otherwise, the general-purpose debugging tool is
Wow!
Ever since I bought