Hey folks
I'd like to mirror and test the latest build of http://snapshots.linaro.org/10.11-daily/linaro-headless/
but I have two issues with this: * having some kind of direct link to the latest image so that I don't need to parse the HTML to get the latest build; something like /latest/ or /current/ would help here * having a constant name for the data as to be rsync friendly; that is, if the image is named linaro-m-headless-tar-20100923-0.tar.gz and linaro-m-headless-tar-20100924-0.tar.gz the next day, it's hard to convince rsync that the data file from the 24th can be mostly inferred from the contents of the 23th; if it was named linaro-m-headless-tar.tar.gz, I would have no problem
Where should I be filing bugs to track these requests, and who should I harass to get these resolved? :-)
Thanks!
On Fri, 24 Sep 2010 19:49:51 +0200, Loïc Minier loic.minier@linaro.org wrote:
Hey folksI'd like to mirror and test the latest build of http://snapshots.linaro.org/10.11-daily/linaro-headless/
but I have two issues with this:
- having some kind of direct link to the latest image so that I don't need to parse the HTML to get the latest build; something like /latest/ or /current/ would help here
- having a constant name for the data as to be rsync friendly; that is, if the image is named linaro-m-headless-tar-20100923-0.tar.gz and linaro-m-headless-tar-20100924-0.tar.gz the next day, it's hard to convince rsync that the data file from the 24th can be mostly inferred from the contents of the 23th; if it was named linaro-m-headless-tar.tar.gz, I would have no problem
Where should I be filing bugs to track these requests, and who should I harass to get these resolved? :-)
These sound like lexbuilder requests to me, though there may be another component that does the publishing, I'm not sure.
Please file the bugs against lexbuilder, and assign them to the linaro-infrastructure team for further investigation.
Thanks,
James
On Fri, Sep 24, 2010 at 7:49 PM, Loïc Minier loic.minier@linaro.org wrote:
Hey folks
I'd like to mirror and test the latest build of http://snapshots.linaro.org/10.11-daily/linaro-headless/
but I have two issues with this: * having some kind of direct link to the latest image so that I don't need to parse the HTML to get the latest build; something like /latest/ or /current/ would help here * having a constant name for the data as to be rsync friendly; that is, if the image is named linaro-m-headless-tar-20100923-0.tar.gz and linaro-m-headless-tar-20100924-0.tar.gz the next day, it's hard to convince rsync that the data file from the 24th can be mostly inferred from the contents of the 23th; if it was named linaro-m-headless-tar.tar.gz, I would have no problem
Where should I be filing bugs to track these requests, and who should I harass to get these resolved? :-)
I agree with James that lexbuilder should get this feature in the end. For now we could do a smart cronjob that creates the latest etc. directory with stable links .... md5sum .txt etc. might be a bit problematic though.
On Fri, 24 Sep 2010 14:35:54 -0400, James Westby james.westby@canonical.com wrote:
Please file the bugs against lexbuilder, and assign them to the linaro-infrastructure team for further investigation.
Hi,
Did you file these bugs?
Thanks,
James
On Mon, Sep 27, 2010, James Westby wrote:
Did you file these bugs?
I wasn't quite sure where to file it, so I just filed it under bugsy at: https://bugs.launchpad.net/bugsy/+bug/649277 and subscribed you
Thanks
On Mon, 27 Sep 2010 22:26:17 +0200, Loïc Minier loic.minier@linaro.org wrote:
On Mon, Sep 27, 2010, James Westby wrote:
Did you file these bugs?
I wasn't quite sure where to file it, so I just filed it under bugsy at: https://bugs.launchpad.net/bugsy/+bug/649277 and subscribed you
Thanks, I'll take a look.
James
On 27 September 2010 21:26, Loïc Minier loic.minier@linaro.org wrote: [about having snapshots.linaro.org have symlinks to 'latest' images and stable filenames to help rsync]
On Mon, Sep 27, 2010, James Westby wrote:
Did you file these bugs?
I wasn't quite sure where to file it, so I just filed it under bugsy at: https://bugs.launchpad.net/bugsy/+bug/649277 and subscribed you
Can somebody give an update on the status of this, please? Launchpad says I don't have permission to access that bug... (Looking at snapshots.linaro.org suggests the answer is "not fixed yet".)
thanks -- PMM
On Thu, 2 Dec 2010 11:34:55 +0000, Peter Maydell peter.maydell@linaro.org wrote:
On 27 September 2010 21:26, Loïc Minier loic.minier@linaro.org wrote: [about having snapshots.linaro.org have symlinks to 'latest' images and stable filenames to help rsync]
On Mon, Sep 27, 2010, James Westby wrote:
Did you file these bugs?
I wasn't quite sure where to file it, so I just filed it under bugsy at: https://bugs.launchpad.net/bugsy/+bug/649277 and subscribed you
Can somebody give an update on the status of this, please? Launchpad says I don't have permission to access that bug... (Looking at snapshots.linaro.org suggests the answer is "not fixed yet".)
Correct, it is unfixed.
I have filed https://bugs.launchpad.net/offspring/+bug/684229 on the new public project.
Thanks,
James
Recapping on an old discussion here...
On Fri, Sep 24, 2010 at 6:49 PM, Loïc Minier loic.minier@linaro.org wrote:
Hey folks
I'd like to mirror and test the latest build of http://snapshots.linaro.org/10.11-daily/linaro-headless/
but I have two issues with this: * having some kind of direct link to the latest image so that I don't need to parse the HTML to get the latest build; something like /latest/ or /current/ would help here
Having "latest" or "current" aliases can cause traceability problems if having mirrored the files, you can't determine which actual build/release it was.
Is it possible to have an easily-parsed file /LATEST or /CURRENT which just contains the URL(s) of the latest image(s)? -- tools or scripts can trivially download those files to get the right canonical URLs for the newest images at any particular time, without having to guess.
Of course, there's no reason why you can't have alises in addition to this, for casual use.
Cheers ---Dave
On Fri, Dec 03, 2010, Dave Martin wrote:
Having "latest" or "current" aliases can cause traceability problems if having mirrored the files, you can't determine which actual build/release it was.
We can include a build id in the image itself to help with this; we can also keep a map of MD5SUMs for past images to help with this as well
Is it possible to have an easily-parsed file /LATEST or /CURRENT which just contains the URL(s) of the latest image(s)? -- tools or scripts can trivially download those files to get the right canonical URLs for the newest images at any particular time, without having to guess.
A script could use this, but it means you always have to use a wrapper; you can't e.g. use rsync directly
Hi,
On Fri, Dec 3, 2010 at 4:51 PM, Loïc Minier loic.minier@linaro.org wrote:
On Fri, Dec 03, 2010, Dave Martin wrote:
Having "latest" or "current" aliases can cause traceability problems if having mirrored the files, you can't determine which actual build/release it was.
We can include a build id in the image itself to help with this; we can also keep a map of MD5SUMs for past images to help with this as well
Is it possible to have an easily-parsed file /LATEST or /CURRENT which just contains the URL(s) of the latest image(s)? -- tools or scripts can trivially download those files to get the right canonical URLs for the newest images at any particular time, without having to guess.
A script could use this, but it means you always have to use a wrapper; you can't e.g. use rsync directly
True--- as long as we have some way to provide the traceability / reproducability, I'm happy.
Cheers ---Dave
-
Alexander Sack -
Dave Martin -
James Westby -
Loïc Minier -
Peter Maydell