Debian Bug report logs - #741143
ltsp: please consider supporting raspbian and/or supporting unknown derivatives

Toggle useless messages

Message #5 received at submit@bugs.debian.org (full text, mbox, reply):

From: peter green <peter.green@postgrad.manchester.ac.uk>

To: Debian Bug Tracking System <submit@bugs.debian.org>

Subject: ltsp: please consider supporting raspbian and/or supporting unknown derivatives

Date: Sun, 09 Mar 2014 02:12:34 +0000

Package: ltsp
Severity: wishlist

Since we started using our own vendor identifications on raspbian (as we 
were encouraged to do by various parties in debian) ltsp started failing 
to build for us 
http://buildd.raspbian.org/status/fetch.php?pkg=ltsp&arch=armhf&ver=5.4.2-6%2Bb2&stamp=1382790352 
. This appeared to be the result of the debian ltsp packages using the 
vendor name to locate certain files and failling on unknown vendors. We 
made a quick hack to work arround this 
http://debdiffs.raspbian.org/main/l/ltsp/ltsp_5.4.2-6%2brpi1.debdiff 
(which we have since pulled forward to each new ltsp version that hit 
jessie)

If all that is required is to distinguish between debian and ubuntu then 
I reccomend using "dpkg-vendor --derives-from ubuntu" to distinguish 
them (dpkg-vendor --derives-from debian can't be used to distinguish 
because ubuntu is a derivative of debian). If it's really critical to 
have different settings for every derivative then I guess you have 
little choice but to list them all. If it would be nice but not critical 
to have settings (e.g. mirror locations for each derivative) and more 
important to distiguish ubuntu-based from non ubuntu based then a hybrid 
approach may be possible to use distro specific settings first, then 
using "--derives-from ubuntu" as a fallback to detect ubuntu derivatives 
and finally fall back to treating the system as debian. I'm not a ltsp 
expert myself so I leave the details of which approach is best in this 
case to those who are.

I just had a chat with vagrantc about this on irc (freenode #raspbian) 
and the discussion is preserved below.

<plugwash> You maintain ltsp in debian right?
<vagrantc> yup
<vagrantc> in fact, that's what got me interested in the rpi ... looking 
at it's use as a thin client
<plugwash> I know some people have been doing stuff with ltsp and the Pi 
but i've no idea on the details. I've patched the ltsp in raspbian 
jessie to make it build but I've no idea if that is enough to actually 
make it usable
<vagrantc> oh, it failed to build?
<plugwash> and if it's appropriate to push anything upstream into debian
<vagrantc> if it's not too crazy complicated, i'd be happy to take patches
<plugwash> It started failling to build after we started using our own 
vendor name
* ColdKeyboard has quit ()
<plugwash> 
http://buildd.raspbian.org/status/fetch.php?pkg=ltsp&arch=armhf&ver=5.4.2-6%2Bb2&stamp=1382790352
<vagrantc> i recently switched the packaging to dpkg-vendor, it used to 
use lsb-release...
<vagrantc> probably not able to take patches for wheezy at this point, 
though
<plugwash> How exactly do you use dpkg-vendor?
<vagrantc> ah, got it.
<vagrantc> i see why it's failing.
<plugwash> Anyway I added a quick hack 
http://debdiffs.raspbian.org/main/l/ltsp/ltsp_5.5.0-1%2brpi1.debdiff but 
i've no idea what the best way to fix it is, nor if raspbian is likely 
to need different settings from debian to make ltsp actually usable
<vagrantc> the ltsp packages have some differences between ubuntu and 
debian, so we use dpkg-vendor/lsb_release to check
* dougl has quit (Remote host closed the connection)
<vagrantc> i haven't actually used raspbian as an LTSP server, though, 
i've only tested the client environment
<plugwash> In general to distinguish between debian and ubuntu it's best 
to use "dpkg-vendor --derives-from ubuntu"
<plugwash> That way downstreams of both will get appropriate treatment
<vagrantc> plugwash: my hunch is that raspbian can be treated 
identically to Debian for all the ltsp packaging
* vagrantc wonders ho wmany people are using raspbian as an LTSP server...
<vagrantc> at runtime, most stuff uses lsb_release, i'm guessing that's 
different too?
<plugwash> Yes it is
<plugwash> in general I would advise against using lsb_release because 
it lacks any understanding of the idea of derivative distributions
<vagrantc> that's used extensively upstream
<vagrantc> there isn't any distro-agnostic tool that does any better 
that i'm aware of
<plugwash> Well there is /etc/os-release though you have to parse it 
yourself
<plugwash> and it's relatively new
<plugwash> The problem is lsb_release has no concept of derivatives, so 
rather than saying "do x on debian like distros and y on redhat like 
distros" you have to say "do x on debian, ubuntu, mint ............ y on 
fedora, rhel, suse, mandrake..............."
<plugwash> Which means smaller distros get screwed because upstreams 
neglect to include them
<vagrantc> as far as the packaging is concerned...
<vagrantc> for ltsp
* DrShoggoth (~prakwtf@12.116.104.118) has joined #raspbian
<vagrantc> i just need additional checks for dpkg --derives-from debian 
&& VENDOR=Debian
<vagrantc> and dpkg --derives-from Ubuntu && VENDOR=Ubuntu ?
* DrShoggoth has quit (Client Quit)
<vagrantc> and then... probably need a symlink in 
/usr/share/ltsp/plugins/ltsp-build-client/Raspbian -> Debian
<vagrantc> although the mirror settings will be different. hrm.
<plugwash> In general don't use "--derives-from debian"
<vagrantc> ?
<plugwash> because pretty much every dpkg using distro will return true 
for that
<vagrantc> well, if VENDOR != Debian or Ubuntu ...
<plugwash> Remember ubuntu derives from debian
<plugwash> so in general you would check if derived from ubuntu, if so 
do ubuntu stuff, if not do debian stuff
<vagrantc> the --dervices-from checks would only be fallbacks if it's an 
"unknown" VENDOR
<plugwash> If you really insist on doing a --derives-from debian test 
you would need to do it AFTER the --derives-from ubuntu test
<vagrantc> right
<vagrantc> plugwash: would you file a wishlist bug on ltsp about this?
* themill sets ban on 
*!*@CPEc8d3a35a59fe-CM000f9fa607d2.cpe.net.cable.rogers.com
<themill> (that's the well known drive-by spammer)
<plugwash> (but in general I see doing a --derives-from debian test as 
pointless, you may as well just put the "debian" choice as the final 
fallback IMO)
<vagrantc> plugwash: yeah, that makes sense.

Message #10 received at 741143@bugs.debian.org (full text, mbox, reply):

From: Vagrant Cascadian <vagrant@debian.org>

To: peter green <peter.green@postgrad.manchester.ac.uk>

Cc: 741143@bugs.debian.org

Subject: Re: Bug#741143: ltsp: please consider supporting raspbian and/or supporting unknown derivatives

Date: Fri, 11 Apr 2014 09:29:50 -0700

[Message part 1 (text/plain, inline)]

Control: tags 741143 pending

On Sun, Mar 09, 2014 at 02:12:34AM +0000, peter green wrote:
> If all that is required is to distinguish between debian and ubuntu then I
> reccomend using "dpkg-vendor --derives-from ubuntu" to distinguish them

Implemented in bzr:

  	https://alioth.debian.org/scm/loggerhead/pkg-ltsp/ltsp-debian-packaging/revision/1207/rules

Should be committed with the next upload.

That should get the packages to build, although it will likely require
additional changes upstream to get ltsp-build-client to work out-of-the box,
though they can be worked around by manually setting --mirror,
--security-mirror, --updates-mirror, --kernel-package, etc.

live well,
  vagrant

[signature.asc (application/pgp-signature, inline)]

Message #17 received at 741143-close@bugs.debian.org (full text, mbox, reply):

From: Vagrant Cascadian <vagrant@debian.org>

To: 741143-close@bugs.debian.org

Subject: Bug#741143: fixed in ltsp 5.5.2-1

Date: Wed, 06 Aug 2014 00:04:39 +0000

Source: ltsp
Source-Version: 5.5.2-1

We believe that the bug you reported is fixed in the latest version of
ltsp, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 741143@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Vagrant Cascadian <vagrant@debian.org> (supplier of updated ltsp package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster@ftp-master.debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Format: 1.8
Date: Tue, 05 Aug 2014 16:19:36 -0700
Source: ltsp
Binary: ltsp-server ltsp-server-standalone ltsp-client-core ltsp-client ltsp-client-builder
Architecture: all source
Version: 5.5.2-1
Distribution: unstable
Urgency: medium
Maintainer: LTSP Debian Maintainers <pkg-ltsp-devel@lists.alioth.debian.org>
Changed-By: Vagrant Cascadian <vagrant@debian.org>
Closes: 606313 741143 743867 753746 753749
Description: 
 ltsp-client-builder - build an LTSP environment in the installer target (udeb)
 ltsp-client - complete LTSP client environment
 ltsp-client-core - basic LTSP client environment
 ltsp-server - basic LTSP server environment
 ltsp-server-standalone - complete LTSP server environment
Changes:
 ltsp (5.5.2-1) unstable; urgency=medium
 .
   * New upstream version:
     - Add support for newer versions of syslinux/pxelinux.
     - Support LDM feature to hash passwords for use with
       localapps and fat clients.
     - ltsp-build-client: Allow setting --locale as simply the locale,
       rather than requiring also specifying the encoding.
     - initramfs udhcp hooks:
       + bring up NICs that become available progressively.
       + timeout for ip link up from 4 seconds to 10.
     - Fix ltsp-update-image --revert.
     - screen.d/kiosk: Pass KIOSK_OPTIONS as an environment variable.
       (Closes: #743867)
 .
   * ltsp-client-core: Update syslinux/pxelinux dependencies:
     - Add syslinux-common
     - Remove syslinux
     - Add pxelinux, with fallback for older versions of syslinux-common.
 .
   * ltsp-server/ltsp-client-core:
     - Prefer iproute2 over iproute transitional package.
       (Closes: #753746, #753749)
 .
   * debian/rules:
     - Use dpkg-vendor --derives-from Ubuntu to set VENDOR, to better handle
       Debian/Ubuntu derivatives (Closes: #741143). Thanks to Peter Green.
 .
   * ltsp-client-builder:
     - Add "--updates-mirror none", which is needed when CD/USB sticks do not
       contain an updates-mirror.
     - Drop --mount-cdrom option, as it is no longer needed (Closes: #606313).
Checksums-Sha1: 
 241e424cfd7cbc862a6543678c2b0fb28ee218f1 2285 ltsp_5.5.2-1.dsc
 d13e7b50cf43522656c386235ec3e8ae6c8e7bb5 432074 ltsp_5.5.2.orig.tar.gz
 d341d45e74a19021b1a8829d572028ff3885735e 73140 ltsp_5.5.2-1.debian.tar.xz
 dcc0361925282f385ea459c9af04247d01a59d8f 262198 ltsp-server_5.5.2-1_all.deb
 f73369fa13c40a99316c50a9f54b18c3a3fda4d3 143820 ltsp-server-standalone_5.5.2-1_all.deb
 581556f56472703e20adffbd0eb2ea6416220091 11094 ltsp-client-builder_5.5.2-1_all.udeb
Checksums-Sha256: 
 7550933f12ded7cd24a0d214ac3a797d25ab4c53bd4e116f7b2a66ce76fc5cf0 2285 ltsp_5.5.2-1.dsc
 375d3bfc84f26680a7bf37ae5a09d52015dfcb62a58d621902fc0860860b701e 432074 ltsp_5.5.2.orig.tar.gz
 9eac6dbed624b68e64efae63b4798a4626480be9774bb167043d6ee0087e778e 73140 ltsp_5.5.2-1.debian.tar.xz
 78a39877ad58a927724e925d7e39e3b5bde4507c1b168329452b76bae6473fe4 262198 ltsp-server_5.5.2-1_all.deb
 68cea31f1ae12f6a5a1f66d39fa5b62806ea87faa4d1bd6244816c217ab8d1e5 143820 ltsp-server-standalone_5.5.2-1_all.deb
 3d40ee8e46ee910a36fee5d0d24045b3eefec2018652dd73435447d6c353a65b 11094 ltsp-client-builder_5.5.2-1_all.udeb
Files: 
 dc2f9aa5c59f574be9cc8a1de9062436 2285 misc extra ltsp_5.5.2-1.dsc
 541348afaec1289e36108b60818b4ecd 432074 misc extra ltsp_5.5.2.orig.tar.gz
 468a3b1e7e07a3838087521684c9173f 73140 misc extra ltsp_5.5.2-1.debian.tar.xz
 a6616d6bd01cbe04c4fd50ca44efa1cd 262198 misc extra ltsp-server_5.5.2-1_all.deb
 44833d922eb89b94e5652db48f9db6ad 143820 misc extra ltsp-server-standalone_5.5.2-1_all.deb
 45f576e82b024e3a7cbcf0776c321b14 11094 debian-installer extra ltsp-client-builder_5.5.2-1_all.udeb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQIcBAEBCgAGBQJT4W+WAAoJELeLgtSBS5G2kucP/Rb9RVAjBwYVPF7UzdB6EYhu
Hbuwedd1aatu58lscdBiPETIa/wRLqoqCYY88BCpJY9okS8gCkAy5DcXp8Dvizd6
4YmskutJyBGWyNbuaVgi51fs+M1XXErOJCrky7rlh3OKXxgq9Jcvmx16YsD08MrO
Io+2Za5s3VV0iBKsT2GLd8kIxhP57pqDoGjH6EXWpCbBxy0NWnxLOe8Me3Yxtq2x
nNj/5fPQeKDioMb9Oa1GejCv0VeCNdfqZRWRF9BIri95Iqdfiax3g6EZQyc9zm5s
FbiGAc8tTgvoKOodIYKa7B5uyJHb3LKHQUywY8NYLeXRVAJJdNjN1IGQJt+aZmVa
1d8f9KHQ+zxJ2MTjfrWBlFW32KX8X7IPkxloD6qf74effJu3V7xsdm+X4cxVVZbj
pER45m9hpsaMFBwXJlIQfQTiFY/i9dc9YhP75ccI+KBtqYy5K9bNyG0NywFEXR8/
6FPbpqlHVGAZzt4lBIUGxFeVrgvmmf6NdDSn8/GWHw5BOXvPPbleANuTqEYP6w8b
CH12JIu58pQEmgEH7fefyBpzDAD9e2sL5HFiQZKAn83dPw5JAdl4ve/BoVpFkhO/
fZf8GS5F0Lua9DSna39nTJJ/V7DjHusf9+Yuo6K1fOmhbKRe3iyu+XqBIZO/hCuG
QNgVY+vlKEx0vLEfKpZm
=vwM4
-----END PGP SIGNATURE-----

Send a report that this bug log contains spam.