Oops! You guys forgot to QA openSUSE-11.0-DVD-x86_64.iso

ZOMG Seriously.
Did anyone notice how this is in the openSUSE-11.0-DVD-x86_64.iso ISO:

\suse\x86_64\xorg-x11-driver-video-radeonhd-1.2.1_080522_566ba69-6.1.x86_64.r

\suse\x86_64\libakonadiprotocolinternals-devel-0.81.0+svn809880-5.1.x86_64.rp

Notice how the file extensions look nothing like .rpm but .r and .rp respectively.

Now look at the online repo for opensuse11:

http://download.opensuse.org/distribution/11.0/repo/oss/suse/x86_64/xorg-x11-driver-video-radeonhd-1.2.1_080522_566ba69-6.1.x86_64.rpm

wow these are the right file extensions… now it looks like I cant install this package from the installation media because somebody didn’t build it properly or copy the build directory to the ISO image right.

Yes that is right, the last 2 openSUSE-11.0-DVD-x86_64.iso I have downloaded has this messup on the dvd image.

This makes me wary there arent other missing or incomplete files on the DVD image!

Whats going to happen next?

Oh btw I just wanted to tell you guys that everyone makes these kinds of mistakes - this will always be my fav distro!!! :nerd:

Opensuse FTW! lol!

No problems here. You should view the DVD with a decent OS like Linux.

$ lsiso openSUSE-11.0-DVD-x86_64.iso | egrep '(radeon|libakona)'
-r--r--r--   6    0    0           34758 Jun  7 2008 [1621843 00]  libakonadiprotocolinternals0-0.81.0+svn809880-5.1.x86_64.rpm
-r--r--r--   6    0    0           13514 Jun  7 2008 [1621900 00]  libakonadiprotocolinternals-devel-0.81.0+svn809880-5.1.x86_64.rpm
-r--r--r--   6    0    0          245041 Jun  7 2008 [1621915 00]  libakonadi4-4.0.72-14.1.x86_64.rpm
-r--r--r--   6    0    0          136106 Jun  7 2008 [2027421 00]  xorg-x11-driver-video-radeonhd-1.2.1_080522_566ba69-6.1.x86_64.rpm

I dont think the issue is the OS I used to view the ISO.

If that were the case then I would have to inform you that the UDF filesystem is supposed to work in any OS.

Maybe you should test the same ISO in windows. If you still see the right filenames I’ll chalk it up to some caching webserver out in the cloud giving me a bad version of this ISO file.

This isnt the slashdot forums so next time you want to answer a posting try and not make it troll party via OS religious war because my 2 ISO images I downloded from this site from separate machines (via Linuks and via Windoze) have the same defect.

Not to mention the fact I was using linux to install Linux when I came across this bug.

so in short: thanks for your non-answer >:)

On Mon, 2008-10-06 at 18:46 +0000, c hill wrote:
>
> If that were the case then I would have to inform you that the UDF
> filesystem is supposed to work in any OS.
>

> Not to mention the fact I was using linux to install Linux when I came
> across this bug.

Not sure what the issue is. I checked the pressed CD… doesn’t have
the problem you mention:

ls xorg566 libakonadidevelsvn809*

libakonadiprotocolinternals-devel-0.81.0+svn809880-5.1.x86_64.rpm
xorg-x11-driver-video-radeonhd-1.2.1_080522_566ba69-6.1.x86_64.rpm

Now on the downloadable 64bit one:

ls xorg566 libakonadidevelsvn809*

libakonadiprotocolinternals-devel-0.81.0+svn809880-5.1.x86_64.rpm
xorg-x11-driver-video-radeonhd-1.2.1_080522_566ba69-6.1.x86_64.rpm

I’m guessing that the problem may actually be in how the DVD
was burnt (?)

But I’m just guessing. If I can say anything encouraging, it’s
that there doesn’t appear to be a problem with the iso images.
At least, not with the filenames anyhow.

It’s not a UDF filesystem, it’s just plain ISO-9660.

Maybe you should test the same ISO in windows. If you still see the right filenames I’ll chalk it up to some caching webserver out in the cloud giving me a bad version of this ISO file.

Why should I? When the DVD is installed, you are running Linux.

Not to mention the fact I was using linux to install Linux when I came across this bug.

So why the Windows-like backslashes?

so in short: thanks for your non-answer >:)

Well, it was a non-question. Obviously you seem to be the only one having this problem with truncated filenames. Nobody is having problems installing these packages.

So why did you post anyway? Just to show that you think that you found a mistake? If you think there is a problem the bug tracker is the place to report them. We’re users here, not developers, though the odd developer might view these forums.

I’ve looked on a burnt DVD and now 3 separately downloaded images. Your right, the file names look good in Linux - but not via POWERISO or normally opening the burnt DVD in Windows explorer.

Still from my perspective as someone who has to use BOTH of the OSes constantly it looks like the DVD image was made only for Linux users. Honestly this is the first time I’ve seen a DVD/CD image with filesystems incompatible between Winblows/Linukz.

So smart guy your right, my better, more common OS (Windows XP) cant read the disc made by your OpenSores™ OS.

Cool eh?

Yes, jump to conclusions at your own peril.

The probable reason why you had filename truncation in Windows is because the Linux and other open systems use Rock Ridge extensions to store the full filename, whereas Windows uses Joliet (a Microsoft extension). Those two names in question are 65 and 66 characters respectively which probably hit some limit of 64 somewhere in Windows or the Joliet standard.

Arguably it’s a shortcoming that you cannot see the full name in Windows, but since the DVD is for installation using a Linux boot anyway, it only affects people who want to view the DVD in Windows. If you feel this is a showstopper, feel free to file a bug at the bugzilla.

Not to mention the fact I was using linux to install Linux when I came across this bug.
WTF is this supposed to mean?:\

my better, more common OS (Windows XP)
Quite clearly far, far from true.

This thread needs moving guys. It’s more of a rant than anything.