Distributions
New online man pages for Debian
The announcement of a modernized version of the online Debian man pages was met with well-deserved acclaim, but also with some concerns about the development tools being used. The man pages themselves are handy and are organized by Debian release; each page provides navigation links to pages for each release and in languages other than what is set in the browser. But the use of GitHub for development and bug tracking was questioned by some.
Michael Stapelberg posted the announcement of the updated service in
mid-January to the
debian-devel mailing list. Instead of a CGI script, the man pages are
statically generated "and therefore
blazingly fast
". Stapelberg implemented the debiman tool that is used to
create the static web pages from the man pages in Debian packages. He
also worked with the Debian system administrators to deploy the service.
As described on the About
page, others were instrumental in getting the service up and running as
well.
The CGI-based version ran aground in August 2016 due to excessive load that was at least partly caused by traffic from robots and web spiders. Default Apache installs on Debian linked to manpages.debian.org, which apparently exacerbated the problem. That led to the creation of debiman and the new site, which can withstand much more traffic because of its static nature.
The debiman program runs regularly to pick up new packages or changes to the man pages. It takes less than ten minutes for debiman to create the whole set of pages for Debian unstable and less than fifteen seconds to do an incremental update, according to the project page. It tracks multiple Debian repositories; as Stapelberg put it:
![crontab(5) [crontab(5)]](https://static.lwn.net/images/2017/debian-manpages-sm.png)
The debiman page notes that the crontab(5)
man page (seen at right) is a particularly good test case because it
"is present in multiple Debian versions, multiple languages, multiple
sections and multiple conflicting packages
". The page for the
"Jessie" (Debian 8.x) version has links to man pages for three different
packages (cron, bcron-run, and systemd-cron), several different versions
("Wheezy", testing, unstable, and experimental), the crontab(1) man page,
and the page in five different languages.
The response was generally quite positive. Various folks replied to offer congratulations and thanks. There were, of course, some bug reports and feature requests as well. Henrique de Moraes Holschuh asked that man pages from the contrib repository be added, since those are all freely licensed (unlike non-free). Stapelberg added an issue to the GitHub tracker, which was closed as fixed shortly thereafter.
Paul Wise posted a laundry list of suggestions and bugs, most of which were either already addressed or had new GitHub issues opened for them. But Debian has its own bug tracker, of course. Ian Jackson was concerned about the use of GitHub both for hosting the code and for bug tracking. He suggested creating a pseudopackage in the Debian bug tracker so that users can report bugs that way. He also would like to see a way to automatically get the source code from the debiman program:
Would you accept a patch to make debiman copy its own source code, including git history, to its output ?
Stapelberg pointed out that each of the
pages has the Git revision used to generate it in the page footer
("debiman c17f615, see github.com/Debian/debiman
").
That should allow anyone to check out the exact code that was run to create
the page. There are some other ancillary files that need to be checked
into Git, but that was already on his to-do list. He said that while he
agreed with Jackson's concerns about using a proprietary service like
GitHub, he was being pragmatic about it:
In my personal experience, I can say that I would not be able to spend _nearly_ as much of my time on FOSS if it weren't for GitHub's convenient web interface.
Even though the commit ID is available on each page, Jackson said, he would "like to be able to check out
the running version without interacting with a proprietary online
service
". To that end, Stapelberg created a mirror
of the GitHub repository for debiman and a repository
for the Debian-specific pieces on Debian's infrastructure. That way,
anyone who wants the source, but doesn't want to deal with GitHub, can get it.
Creating a pseudopackage for the Debian bug tracker would allow users to report bugs in debiman using that system. Stapelberg is not entirely happy with that plan, but is willing to go along:
The underlying problem is that there is no free alternative to GitHub that is as full-featured. Various posters in the thread noted that problem (including Jackson in his original response). The ease of use of GitHub, along with its widespread adoption, simply makes it far easier for new contributors to get involved. It is not at all surprising that Debian developers, in particular, would be disinclined toward GitHub, but alternatives need to arise. As Alec Leamas put it:
But, we cannot just say "our tools are as good as github". Because they are not. We need to understand it, and see what can be done. It's an uphill battle, but also uphill battles can be won.
There was a suggestion to look at using a free version of GitLab for hosting Debian projects. The fact that there is a free version may be a sticking point, however. GitLab the company has two separate versions of its code, a community edition and closed-source enterprise edition, which is the classic "open core" model. Lars Wirzenius was not particularly interested in using GitLab because of that:
So it would seem that things have worked out amicably at this point, though it is unlikely that the GitHub question has gone away. But there are much nicer, faster man pages online and Debian users can get the source and file bugs using Debian infrastructure. The "move" to GitHub is one we are seeing recur with some frequency (e.g. for Python) and will likely see more of in the coming years. A free alternative that eventually attracts a large following is what is needed, but nothing has really reared its head at this point.
Brief items
Distribution quote of the week
Release for CentOS AltArch 7 (1611) on i386 Architecture
The CentOS AltArch SIG has released the latest CentOS version 7 (1611) for the i386 architecture. This release includes all packages that build on x86 32-bit processors.LEDE v17.01.0-rc1 released
The LEDE project, working on a fork of the OpenWrt router distribution, has announced its first release candidate. "With this release, the LEDE development team closes out an intense effort to modernize many parts of OpenWrt and incorporate many new modules, packages, and technologies." Click below for a terse list of changes; they include the significant WiFi performance improvements described in this article.
Scientific Linux 7.3
Scientific Linux 7.3 has been released. "SL 7.3 includes updated support for Scientific Linux Contexts which should allow for ease of creating local customization for specific computing needs. Anaconda integration should be less intrusive for non-context users For more information on Scientific Linux Contexts: http://ftp.scientificlinux.org/linux/scientific/7/conte..." See the release notes for details.
Distribution News
Debian GNU/Linux
Debian BSP in Berlin
There will be a Bug Squashing Party at Endocode AG in Berlin, Germany February 25-26.
Ubuntu family
Ubuntu Zesty Zapus Alpha 2 Released
Several flavors of Ubuntu have released an alpha version of Zesty Zapus (17.04), including Lubuntu, Kubuntu, Ubuntu MATE, Ubuntu Kylin, Ubuntu GNOME, and Ubuntu Budgie.
Newsletters and articles of interest
Distribution newsletters
- DistroWatch Weekly (January 30)
- Lunar Linux weekly news (January 27)
- openSUSE news (January 26)
- openSUSE news (February 1)
- openSUSE Tumbleweed β Review of the Week (January 27)
- Puppy Linux Newsletter (February)
- Sparky news (January 30)
- Ubuntu Weekly Newsletter (January 29)
Best Lightweight Linux Distros for 2017 (Linux.com)
Swapnil Bhartiya picks a few lightweight distributions for a mini-review. He includes Knoppix, Lubuntu, PIXEL, Arch Linux, Remix OS, Debian, and Puppy Linux. "Debian, the mother of many popular distributions is by default a lightweight distro, as itβs system requirements are relatively low and you still get the most stable distribution on the planet. Debian uses Gnome as the default desktop environment, which can be resource hungry on some machines, but I suggest the LXDE version of Debian which brings the best of both worlds: lightweight, without compromising on quality and stability." Knoppix, Lubuntu and PIXEL are based on Debian.
Page editor: Rebecca Sobol
Next page:
Development>>