Bug 1911 - ltsp-pam-1.0-0-i386.tgz from LTSP-4.1 is bad packed
Summary: ltsp-pam-1.0-0-i386.tgz from LTSP-4.1 is bad packed
Status: ASSIGNED
Alias: None
Product: LTSP
Classification: Unclassified
Component: LTSP Core (show other bugs)
Version: unspecified
Hardware: x86 (IA32) All
: high normal
Assignee: Jim McQuillan
QA Contact:
URL: http://www.ltsp.org/ltsp-4.1/ltsp-pam...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-11-23 03:31 UTC by Andrés Gómez García
Modified: 2013-03-19 09:36 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments
Repackaged ltsp-pam-1.0-0-i386.tgz file to solve the problem. (122.26 KB, text/plain)
2013-03-19 09:36 UTC, Andrés Gómez García
Details

Description Andrés Gómez García 2004-11-23 03:31:42 UTC
When it's untarred it creates 2 dirs:

i386/etc/
i386/opt/ltsp/i386/

It seems this is wrong and that which is situated under 

i386/opt/ltsp/i386/

should be directly under

i386/

Ciao.
Comment 1 chemtech 2013-03-15 14:08:49 UTC
Andrés Gómez García
Do you still experience this issue with newer drivers ?
Please check the status of your issue.
Comment 2 Andrés Gómez García 2013-03-19 09:36:31 UTC
Created attachment 76747 [details]
Repackaged ltsp-pam-1.0-0-i386.tgz file to solve the problem.

(In reply to comment #1)
> Andrés Gómez García
> Do you still experience this issue with newer drivers ?
> Please check the status of your issue.
...

Checked with:
http://ltsp.mirrors.tds.net/pub/ltsp/ltsp-4.1-old/ltsp-pam-1.0-0-i386.tgz

From:
http://ltsp.mirrors.tds.net/pub/ltsp/ltsp-4.1-old/

This is still happening.

Also checked with newer version:
http://ltsp.mirrors.tds.net/pub/ltsp/ltsp-4.1/ltsp-pam-1.1-0-i386.tgz

From:
http://ltsp.mirrors.tds.net/pub/ltsp/ltsp-4.1/

And in this new version seems to be fixed.

---

However, for compatibility reasons I'm providing as an attachment the same content the incorrect file correctly packaged.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.