Ubuntu
ltsp package

installing ltsp-server-standalone fails cant find xubuntu-artwork-usplash

Bug #221894 reported by J ME J
26
Affects Status Importance Assigned to Milestone
ltsp (Ubuntu)
Fix Released
Undecided
Unassigned
Hardy
Fix Released
Low
Unassigned
Ubuntu ubuntu-8.04.1
Intrepid
Fix Released
Undecided
Unassigned

Bug Description

When trying to install ltsp-server-standalone from and upgraded gutsy but a clean install of ltsp-server-standalone it fails saying LTSP client installation ended abnormally due to the package xubuntu-artwork-usplash either being missing or as a guess it maybe miss labeled.

I tried the main server and several mirrors and go the same result.

I also tried the exclude option ltsp-build-client --exclude xubuntu-artwork-usplash. But got the same result. Is the exclude option working correctly?

due to not working on any of the mirrors I have a strong feeling is due to an incorrect package name being supplied in ltsp-server-stanalone.

Any one fixed this or had the same problem please.

Revision history for this message
Oliver Grawert (ogra) wrote :

xubuntu moved to universe, ltsp builds the client by default from main packages only. you need to use the --components option with main,restricted,universe as parameters for that, someone in the xubuntu community should document that change.

Changed in ltsp:
status: New → Invalid
Revision history for this message
Nick_Hill (nick-nickhill) wrote :

I have tested and found the same problem.

Given that nobody without knowledge of undocumented parameters can use ltsp-build-client for it's intended purpose, I believe this to be a bug, and I believe it should remain a bug until either:
1) ltsp-build-client scripts no longer depend on universe packages
or
2) ltsp-build-client gives informational warning telling users the build will fail without the parameter, and why
or
3) The package the ltsp-build-client scripts are a member of moves to universe and, by default, enables the universe component in the client environment

Changed in ltsp:
status: Invalid → Confirmed
Revision history for this message
mbabcock (babcockm) wrote :

Please clarify the options you suggested with the proper syntax. What you posted helped me understand the problem but without the syntax and since it's not documented to make sure I was doing it right, the problem persisted until I edited the install scripts to point to more than just main.

Thank you

Revision history for this message
Oliver Grawert (ogra) wrote :

the --help option of ltsp-build-client documents it ....
but for the lazy ones:

sudo ltsp-build-client --components main,restricted,universe

Oliver Grawert (ogra)
Changed in ltsp:
importance: Undecided → Low
milestone: none → ubuntu-8.04.1
status: New → Fix Committed
Revision history for this message
Martin Pitt (pitti) wrote :

Accepted into -proposed, please test and give feedback here

Revision history for this message
Oliver Grawert (ogra) wrote :

tested and verified several times, fix should be fine

Revision history for this message
Martin Pitt (pitti) wrote :

Copied to hardy-updates.

Changed in ltsp:
status: Fix Committed → Fix Released
Revision history for this message
Nick_Hill (nick-nickhill) wrote :

I can confirm this bug has been fixed in 8.04.1.

Revision history for this message
Nick_Hill (nick-nickhill) wrote :

I haven't seen any reports that this bug actually exists in intrepid, and I have tested intrepid and not managed to repeat bug so also marking intrepid Fix Released.

Changed in ltsp:
status: Confirmed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.