Feeds

Debian components breach terms of GPLv2

You want source code with that?

Intelligent flash storage arrays

A top Debian contributor has been left "pretty disappointed" by elements of the Debian community for failing to comply with the conditions of the GNU GPLv2 license.

Daniel Baumann, who maintains the Debian Syslinux bootloader package, has said Debian components were being released only in binary form without source code - resulting in problems for Apple Macintosh users.

"I don't want to blame individual persons," Baumann said. "This is just a note of how disappointed I'm about some parts of Debian that are not complying to licenses when it comes to distributing software."

One problem concerns Debian CD - the toolkit used to build new versions of Debian for public release. Baumann found the toolkit was using an embedded binary version of Syslinux rather than taking a full version with source code from the official Debian archive. Another instance involved the Sarge release of Debian that shipped with Syslinux 2.04 in binary and Syslinux 2.11 in source.

Baumann also found that source code for some components was missing from last November's beta version of KDE 4 - although this has now been removed from the Debian Live CDs distribution list.

The problem of synchronizing source and binary versions of Debian packages affected some Apple users last week when they tried to install the first beta release of the Lenny, the latest version Debian. Some users found their keyboard freezing up as a result of the wrong binary-only version of Syslinux being included in the package. In this case the current archive version of Syslinux (3.71) did not work - while an earlier version (3.63) embedded in Debian Installer worked fine.

Baumann has acknowledged that the problem is most likely the result of the increasingly heavy workload faced by the Debian community and the growing popularity of Debian-based Linux distros.

"It appears that as good as our package checks are, we spend little to no time to check our resulting products made from these packages," Baumann said.®

Beginner's guide to SSL certificates

More from The Register

next story
Microsoft to bake Skype into IE, without plugins
Redmond thinks the Object Real-Time Communications API for WebRTC is ready to roll
Microsoft promises Windows 10 will mean two-factor auth for all
Sneak peek at security features Redmond's baking into new OS
Mozilla: Spidermonkey ATE Apple's JavaScriptCore, THRASHED Google V8
Moz man claims the win on rivals' own benchmarks
FTDI yanks chip-bricking driver from Windows Update, vows to fight on
Next driver to battle fake chips with 'non-invasive' methods
DEATH by PowerPoint: Microsoft warns of 0-day attack hidden in slides
Might put out patch in update, might chuck it out sooner
Ubuntu 14.10 tries pulling a Steve Ballmer on cloudy offerings
Oi, Windows, centOS and openSUSE – behave, we're all friends here
Was ist das? Eine neue Suse Linux Enterprise? Ausgezeichnet!
Version 12 first major-number Suse release since 2009
Redmond top man Satya Nadella: 'Microsoft LOVES Linux'
Open-source 'love' fairly runneth over at cloud event
prev story

Whitepapers

Why cloud backup?
Combining the latest advancements in disk-based backup with secure, integrated, cloud technologies offer organizations fast and assured recovery of their critical enterprise data.
A strategic approach to identity relationship management
ForgeRock commissioned Forrester to evaluate companies’ IAM practices and requirements when it comes to customer-facing scenarios versus employee-facing ones.
Reg Reader Research: SaaS based Email and Office Productivity Tools
Read this Reg reader report which provides advice and guidance for SMBs towards the use of SaaS based email and Office productivity tools.
Storage capacity and performance optimization at Mizuno USA
Mizuno USA turn to Tegile storage technology to solve both their SAN and backup issues.
The hidden costs of self-signed SSL certificates
Exploring the true TCO for self-signed SSL certificates, including a side-by-side comparison of a self-signed architecture versus working with a third-party SSL vendor.