Debian repositories?

Oct 27, 2012 at 8:30 AM

Hello fellas.

Have you given any thoughts to adding your library to the Debian repositories? If you're interested, I'd volunteer to do it myself. I've been looking for a project to get into Debian maintaining for a while, already have a sponsor that'd help me in, and your project is certainly worth it.


Oct 27, 2012 at 9:03 AM

I think this is a great idea. We haven't had the resources and the expertise to do it so far, so if you want to give it a try, this will be an outstanding contribution. I will try do add the missing "For Developers" wiki page soon; please let me know about anything else you will need to support your effort! 

Oct 27, 2012 at 10:35 AM

Excellent! I'll start working on it and I'll get back to you soon.

Oct 29, 2012 at 2:17 PM

Just a quick update: I've been accepted into the "Mentoring of the Month" program, as you can see in [1], and will be starting right away. Hopefully by the end of November we should have CSB into the unstable repositories.



Oct 29, 2012 at 2:28 PM

Great, and here is a new "For Developers" wiki page:

Oct 29, 2012 at 2:33 PM

Excellent, that'll come in handy.


Nov 5, 2012 at 1:33 PM

Alright, the package is coming along nicely, and it's been approved by my mentor for upload, pending input from the Debian Python team.

One thing that they've asked me to find out is whether it would be possible to have better access to the source tarball of each release. The way Codeplex handles the downloading, with no clear reference to a .tar.gz file at any point, makes it impossible for me to write a "watch" file that contains a regular expression that will allow the Debian "uscan" utility to automatically find the sources file.

Any chance you could provide an easier way to download the source tarball? Please take into account that it should be kept in sync with any releases.


Nov 5, 2012 at 4:20 PM

There is a small difference between a "release package" and a "source tarball". Release packages are something that can be installed with "python install". Source tarballs do not contain HTML docs, do not have properly set csb.__version__ number and basically need to be built first with "csb/". This produces a release package.

If a release package would be sufficient for you, then it is very simple: we upload every release to PyPi. Just query the PyPi stats for package "csb". One way to do it is to parse this XML:

and then search for "csb-n.n.n.tar.gz", where "n" is a digit (\d+). Another option is to use a PyPi API, such as:


But in case you really need the source tarball, it is a bit more work:

1) use a mercurial client to get the changeset id of the latest stable release (releases are tagged with labels) -- you basically need the ID of the newest label

2) then download the tarball from here:

where ChangesetID is the changeset ID.

Nov 5, 2012 at 7:54 PM

That's great, the pypi tarball will do just fine.


Jan 16, 2013 at 4:52 PM

Greeting, friends.

Just a quick update about the Debian packaging effort: the package has been uploaded to the debian FTP a couple of weeks ago, and should be making its way into unstable shortly. Unfortunately Debian is in the middle of a freeze, and the approval of new packages gets a lower priority during this time. In any case, you can check the FTP link for the package [1] to take a sneak peek ;)