Can't open Transcode tarball or it doesn't exist
Hi Folks, I have been trying to get a tarball of transcode to compile on my SUSE 9.2 system. Every pkg I have d/l'd from the sites listed on the Transcode Wiki page: http://www.transcoding.org/cgi-bin/transcode are unopenable. Every one, including the beta versions. Have I made one of those embarrassing newby errors? Konqi Filemgr says : "The file does not exist" even tho it lists it. Is there a location for a transcode I can open and compile? PeterB p.s. The pkgs are unopenable on my SUSE 8.2 sys also -- -- Proud SUSE user since 5.2 Loving SUSE 9.2 My BLOG == http://vancampen.org/blog --
Peter B Van Campen wrote:
Is there a location for a transcode I can open and compile?
Not really an answer to your problem directly, but you can get both rpms and src.rpms from packman.link2linux.org. You can either use the rpm, rebuild the src.rpm, or you can use mc to extract the tarball from the src.rpm. HTH -- Joe Morris New Tribes Mission Email Address: Joe_Morris@ntm.org Registered Linux user 231871
On Sunday 13 March 2005 11:39 am, Peter B Van Campen wrote:
Hi Folks,
I have been trying to get a tarball of transcode to compile on my SUSE 9.2 system. Every pkg I have d/l'd from the sites listed on the Transcode Wiki page:
http://www.transcoding.org/cgi-bin/transcode
are unopenable. Every one, including the beta versions. Have I made one of those embarrassing newby errors? Konqi Filemgr says : "The file does not exist" even tho it lists it.
Is there a location for a transcode I can open and compile?
My guess is you downloaded it as root and are trying to open it as user. Happens to me all the time! Nother thing to look out for in the wonderful world of linux. Check its permissions and make sure it's readable and changeable by anyone. Or if you're paranoid, and doing it from the command line, su before you try to open it. ra ra
PeterB
p.s. The pkgs are unopenable on my SUSE 8.2 sys also -- --
Proud SUSE user since 5.2 Loving SUSE 9.2 My BLOG == http://vancampen.org/blog
--
-- Old age ain't for Sissies!
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 2005-03-13 12:39:20 -0500 Peter B Van Campen <peterb@vancampen.org> wrote:
I have been trying to get a tarball of transcode to compile on my SUSE 9.2 system. Every pkg I have d/l'd from the sites listed on the Transcode Wiki page:
http://www.transcoding.org/cgi-bin/transcode
are unopenable.
I tested it out for you (I usually compile transcode from CVS). It is really strange- the package wouldn't open is Ark or KArchiver but works fine with mc and "tar -xzvf". Charles -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (GNU/Linux) Comment: Using the GPG bundle for GNUMail iD8DBQFCNJvE3epPyyKbwPYRAkmuAJ9F7+I/QDSrVwaNMuWoD0vcW4YIYgCfYWaW jtxzny7EY1g69s1F0PVe/Fs= =leax -----END PGP SIGNATURE-----
On Sunday 13 March 2005 2:00 pm, Charles Philip Chan wrote:
On 2005-03-13 12:39:20 -0500 Peter B Van Campen <peterb@vancampen.org>
wrote:
I have been trying to get a tarball of transcode to compile on my SUSE 9.2 system. Every pkg I have d/l'd from the sites listed on the Transcode Wiki page:
http://www.transcoding.org/cgi-bin/transcode
are unopenable.
I tested it out for you (I usually compile transcode from CVS). It is really strange- the package wouldn't open is Ark or KArchiver but works fine with mc and "tar -xzvf".
Hi Charles, Thanks for the help. MC works here too. I agree very very weird indeed. Can anyone else shed any light on why a gzipped tarball is "non-existant" in Konqi running as FileManager (root)?? I d/l'd it in XP and got 'StuffIt' to open it, then I moved the extracted folder to SUSE 9.2. Considering how some people regard transcode I wonder if there is a tad of skulldugery going on; imagine if some particular zip files were unopenable in the M$ Windows world!!! Cry CONSPIRACY! PeterB -- -- Proud SUSE user since 5.2 Loving SUSE 9.2 My BLOG == http://vancampen.org/blog --
* Peter B Van Campen (peterb@vancampen.org) [20050313 18:40]:
are unopenable. Every one, including the beta versions. Have I made one of those embarrassing newby errors? Konqi Filemgr says : "The file does not exist" even tho it lists it.
Is there a location for a transcode I can open and compile?
The tarball has been created by a pre POSIX version of tar. POSIX tar files have a standardized header with the string 'ustar' at position 258, which makes it easy to identify them. Pre-POSIX tar files need additional logic to identify the file which seems to be lacking from whatever KDE component that handles/determines file types. You can try yourself: gunzip -c transcode-0.6.14.tar.gz|file - /dev/stdin: tar archive tar -xzf transcode-0.6.14.tar.gz tar -cf - transcode-0.6.14| file - /dev/stdin: POSIX tar archive Philipp -- Philipp Thomas <pth <at> suse.de> Research & Development SUSE LINUX Products GmbH, Maxfeldstr. 5, D-90409 Nuremberg, Germany
On 2005-03-13 12:39:20 -0500 Peter B Van Campen <peterb@vancampen.org> wrote:
http://www.transcoding.org/cgi-bin/transcode
are unopenable. Every one, including the beta versions. Have I made one of those embarrassing newby errors? Konqi Filemgr says : "The file does not exist" even tho it lists it.
No problem here. What happens when you run file against it, eg: file transcode-1.0.2.tar.gz ? Charles -- printk("??? No FDIV bug? Lucky you...\n"); linux-2.2.16/include/asm-i386/bugs.h
participants (5)
-
Charles Philip Chan -
Joe Morris (NTM) -
Peter B Van Campen -
Philipp Thomas -
Richard