Account Options

  1. Sign in
The old Google Groups will be going away soon.
Switch to the new Google Groups.
Google Groups Home
« Groups Home
Message from discussion Refreshed UEC Images of 10.10 LTS (Lucid Lynx)
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
Scott Moser  
View profile  
 More options Aug 30 2010, 11:05 pm
From: Scott Moser <smo...@ubuntu.com>
Date: Mon, 30 Aug 2010 23:05:27 -0400 (EDT)
Local: Mon, Aug 30 2010 11:05 pm
Subject: Re: [ec2ubuntu] Re: Refreshed UEC Images of 10.10 LTS (Lucid Lynx)

On Mon, 30 Aug 2010, Thierry wrote:
> Scott,

> By the way, not that it impacted me, but I noticed some
> "irregularities" in the naming of beta and alpha releases. For
> example, for Lucid you used "alpha-1", "beta-1" in the path an "beta1"
> in the filename. Then, still in Lucid, you provided another path,
> "beta1". Now go to Maverick and you again have "alpha-1" path with no
> "alpha1" name. Is that supposed to be the logic from now on? I mean a

The practice of '-' in the directory name, but not in the filename comes
from the other code that I use in the publishing of images.  Ie, that is
(or at least should be) consistent with other ubuntu releases.

I'm not actually sure how the where the symlink for directory name
'beta1' -> beta-1 came from (ie, in the directory listing at
http://uec-images.ubuntu.com/server/releases/lucid/).

It appears to me that the query data consistently references files using
'beta-1' rather than 'beta1'.  One way or another, the query data gives
you a hassle free path into all of this.  You shouldn't have to worry
about a 'label' -> 'filename' or label -> path conversion as the data
provides it for you.

In query, there will not be hyphens in label names. (but I won't make
promises about path names).

> 'SUITE-server-uec-ARCH.tar.gz' generic name, whatever the release,
> specifics being given by the path?

I did change the file naming convention once, and that ticked some people
off.  I believe that we should be able to stick to
<suite>-<buildname>-uec-<arch>.tar.gz for a while.  Again, hopefully even
if I changed it, the query would provide you with the correct data.

One thing that I'm not terribly happy with is that for dailies, the
<suite>-<buildname>-uec-<arch>.tar.gz contains files named like
"<suite>-<buildname>-uec-<arch>", but for published builds, the contents
of the tarball are still '<suite>-<buildname>-uec-<arch>', but the tarfile
name has changed.

That is a side effect of the fact that "promote-daily" doesn't change
anything that was MD5SUMed.   Ie, the build that was a daily produced a
<suite>-<buildname>-uec-<arch>.tar.gz , and that was simply copied and
renamed to
ubuntu-<suite>-<version>-<label>-<arch>-<buildname>-<serial>.

The inconsistencies that you find are a result of happening as they went,
not purely designed from the beginning.

So, in summary, if you use data in /query, then you shouldn't have to
worry about this stuff.


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.