Hi,
There is now a much easier way to download the daily Linaro images and hardware packs, the /latest link. Inside each build directory a /latest link will always point to the latest successful build. The following urls are currently setup:
http://snapshots.linaro.org/11.05-daily/linaro-alip/latest http://snapshots.linaro.org/11.05-daily/linaro-developer/latest http://snapshots.linaro.org/11.05-daily/linaro-headless/latest http://snapshots.linaro.org/11.05-daily/linaro-netbook-efl/latest
Please note that the headless and netbook-efl images will be replaced by the Nano and Evaluation Ubuntu Desktop builds soon.
The following hardware packs are also built:
http://snapshots.linaro.org/11.05-daily/linaro-hwpacks/igep/latest/ http://snapshots.linaro.org/11.05-daily/linaro-hwpacks/imx51/latest/ http://snapshots.linaro.org/11.05-daily/linaro-hwpacks/lt-s5pv310/latest http://snapshots.linaro.org/11.05-daily/linaro-hwpacks/omap3/latest/ http://snapshots.linaro.org/11.05-daily/linaro-hwpacks/omap3-x11-base/latest... http://snapshots.linaro.org/11.05-daily/linaro-hwpacks/overo/latest/ http://snapshots.linaro.org/11.05-daily/linaro-hwpacks/panda/latest/ http://snapshots.linaro.org/11.05-daily/linaro-hwpacks/vexpress/latest/
Regards, Jamie. -- Linaro Release Manager
On Tue, Feb 08, 2011, Jamie Bennett wrote:
There is now a much easier way to download the daily Linaro images and hardware packs, the /latest link. Inside each build directory a /latest link will always point to the latest successful build.
\o/
Except it seems to point to the last day where a (successful?) build happen rather than to the build itself? (IOW, it should point to the /0, /1, or /2 subdirectory)
Hi Jamie,
On Tue, Feb 08, 2011 at 01:10:46PM +0000, Jamie Bennett wrote:
There is now a much easier way to download the daily Linaro images and hardware packs, the /latest link. Inside each build directory a /latest link will always point to the latest successful build. The following urls are currently setup:
http://snapshots.linaro.org/11.05-daily/linaro-alip/latest http://snapshots.linaro.org/11.05-daily/linaro-developer/latest http://snapshots.linaro.org/11.05-daily/linaro-headless/latest http://snapshots.linaro.org/11.05-daily/linaro-netbook-efl/latest
Thanks for making this happen!
+1 to Loïc's comment that this should link directly to the latest build, not just the latest day.
On 11 Feb 08, Steve Langasek wrote:
Hi Jamie,
On Tue, Feb 08, 2011 at 01:10:46PM +0000, Jamie Bennett wrote:
There is now a much easier way to download the daily Linaro images and hardware packs, the /latest link. Inside each build directory a /latest link will always point to the latest successful build. The following urls are currently setup:
http://snapshots.linaro.org/11.05-daily/linaro-alip/latest http://snapshots.linaro.org/11.05-daily/linaro-developer/latest http://snapshots.linaro.org/11.05-daily/linaro-headless/latest http://snapshots.linaro.org/11.05-daily/linaro-netbook-efl/latest
Thanks for making this happen!
+1 to Loïc's comment that this should link directly to the latest build, not just the latest day.
The currently link needs the following navigation:
http://snapshots.linaro.org/11.05-daily/linaro-developer/latest/0/images/tar...
Perhaps it's also be possible to simply that to
http://snapshots.linaro.org/11.05-daily/linaro-developer/latest/linaro-n-dev... ?
(note change to filename)
/Amit
On Mon, Feb 14, 2011 at 10:39 AM, Amit Kucheria amit.kucheria@linaro.orgwrote:
The currently link needs the following navigation:
http://snapshots.linaro.org/11.05-daily/linaro-developer/latest/0/images/tar...
Perhaps it's also be possible to simply that to
http://snapshots.linaro.org/11.05-daily/linaro-developer/latest/linaro-n-dev...
Only if linaro-n-developer.tar.gz is a symlink to linrao-n-developer-tar-DATESTAMP-BUILDID.tar.gz. It is still useful to have some easy way to see which image we are pulling, even if it means pulling it out of the filename. Another alternative, would be if we could drop some buildstamp file in the image directory to pull this from.
Another thought too... if we are already going to this extent to make it easier for people to stay up to date with the latest image, does it make sense to go ahead and enable creation of .zsync files for the images? Granted, these aren't nearly the size of an iso, but some of our folks with slower connections might appreciate it.
Thanks, Paul Larson
On Mon, Feb 14, 2011, Paul Larson wrote:
Only if linaro-n-developer.tar.gz is a symlink to linrao-n-developer-tar-DATESTAMP-BUILDID.tar.gz. It is still useful to have some easy way to see which image we are pulling, even if it means pulling it out of the filename. Another alternative, would be if we could drop some buildstamp file in the image directory to pull this from.
I personally don't like DATESTAMP in the filename; it makes rsync-ing harder as a start, and it only helps with local tarballs, not installed images. I think you want some build-stamp information in the tarball itself, no matter what, so you can as well "tar vtf linaro-n-dev.tar.gz|grep build-stamp" or something. The date of the build is only one of the important pieces of information which we want to see at a glance about a build, so I'd rather not clutter filenames with it.
Another thought too... if we are already going to this extent to make it easier for people to stay up to date with the latest image, does it make sense to go ahead and enable creation of .zsync files for the images? Granted, these aren't nearly the size of an iso, but some of our folks with slower connections might appreciate it.
Good idea; there's also a request to consider .xz instead of .gz: https://bugs.launchpad.net/linaro-images/+bug/683849
On 02/14/11 at 06:39pm, Amit Kucheria wrote:
On 11 Feb 08, Steve Langasek wrote:
Hi Jamie,
On Tue, Feb 08, 2011 at 01:10:46PM +0000, Jamie Bennett wrote:
There is now a much easier way to download the daily Linaro images and hardware packs, the /latest link. Inside each build directory a /latest link will always point to the latest successful build. The following urls are currently setup:
http://snapshots.linaro.org/11.05-daily/linaro-alip/latest http://snapshots.linaro.org/11.05-daily/linaro-developer/latest http://snapshots.linaro.org/11.05-daily/linaro-headless/latest http://snapshots.linaro.org/11.05-daily/linaro-netbook-efl/latest
Thanks for making this happen!
+1 to Loïc's comment that this should link directly to the latest build, not just the latest day.
The currently link needs the following navigation:
http://snapshots.linaro.org/11.05-daily/linaro-developer/latest/0/images/tar...
Perhaps it's also be possible to simply that to
http://snapshots.linaro.org/11.05-daily/linaro-developer/latest/linaro-n-dev... ?
(note change to filename)
This is beyond the capabilities of the current scripts we have for syncing images from Offspring to the snapshots server. The Infrastructure team have this on their plate to investigate whether or not we can add this to Offspring itself. I'll keep you informed.
/Amit
Regards, Jamie. -- Linaro Release Manager
On Tue, Feb 8, 2011 at 1:10 PM, Jamie Bennett jamie.bennett@linaro.org wrote:
Hi,
There is now a much easier way to download the daily Linaro images and hardware packs, the /latest link. Inside each build directory a /latest link will always point to the latest successful build. The following urls are currently setup:
http://snapshots.linaro.org/11.05-daily/linaro-alip/latest http://snapshots.linaro.org/11.05-daily/linaro-developer/latest http://snapshots.linaro.org/11.05-daily/linaro-headless/latest http://snapshots.linaro.org/11.05-daily/linaro-netbook-efl/latest
Please note that the headless and netbook-efl images will be replaced by the Nano and Evaluation Ubuntu Desktop builds soon.
The following hardware packs are also built:
http://snapshots.linaro.org/11.05-daily/linaro-hwpacks/igep/latest/ http://snapshots.linaro.org/11.05-daily/linaro-hwpacks/imx51/latest/ http://snapshots.linaro.org/11.05-daily/linaro-hwpacks/lt-s5pv310/latest http://snapshots.linaro.org/11.05-daily/linaro-hwpacks/omap3/latest/ http://snapshots.linaro.org/11.05-daily/linaro-hwpacks/omap3-x11-base/latest... http://snapshots.linaro.org/11.05-daily/linaro-hwpacks/overo/latest/ http://snapshots.linaro.org/11.05-daily/linaro-hwpacks/panda/latest/ http://snapshots.linaro.org/11.05-daily/linaro-hwpacks/vexpress/latest/
So far, so good, but we still don't shapshort linaro-image-tools along with releases.
This will become a problem because l-i-t evolves over time -- I've already had to start explaining to people how to check out old versions of l-i-t in order to make use of the linaro-m release images. Installing the (unsupported) linaro-m release for panda doesn't work with current l-i-t, for example.
To be fair, this is more of an issue for releases.linaro.org (where people will tend to need a specific, old version of l-i-t) than for snapshots.linaro.org. But it's something we need to think about.
Cheers ---Dave
On Wed, Feb 16, 2011 at 12:55:31PM +0000, Dave Martin wrote:
So far, so good, but we still don't shapshort linaro-image-tools along with releases.
This will become a problem because l-i-t evolves over time -- I've already had to start explaining to people how to check out old versions of l-i-t in order to make use of the linaro-m release images. Installing the (unsupported) linaro-m release for panda doesn't work with current l-i-t, for example.
What error do you get in this case? The current version of l-i-t /is/ supposed to work for installing old linaro-m images, and if it doesn't that's something we should fix.
On Wed, 16 Feb 2011 12:55:31 +0000, Dave Martin dave.martin@linaro.org wrote:
So far, so good, but we still don't shapshort linaro-image-tools along with releases.
This will become a problem because l-i-t evolves over time -- I've already had to start explaining to people how to check out old versions of l-i-t in order to make use of the linaro-m release images. Installing the (unsupported) linaro-m release for panda doesn't work with current l-i-t, for example.
I would consider this a bug. I think it is impractical for us to ask everyone to use a different l-i-t for every release that they consume.
I also think it would be a massive headache for maintainence of l-i-t as well.
Please file bugs when you see these issues, and we will deal with them appropriately.
Thanks,
James
On Wed, Feb 16, 2011 at 2:53 PM, James Westby james.westby@canonical.com wrote:
On Wed, 16 Feb 2011 12:55:31 +0000, Dave Martin dave.martin@linaro.org wrote:
So far, so good, but we still don't shapshort linaro-image-tools along with releases.
This will become a problem because l-i-t evolves over time -- I've already had to start explaining to people how to check out old versions of l-i-t in order to make use of the linaro-m release images. Installing the (unsupported) linaro-m release for panda doesn't work with current l-i-t, for example.
I would consider this a bug. I think it is impractical for us to ask everyone to use a different l-i-t for every release that they consume.
I also think it would be a massive headache for maintainence of l-i-t as well.
Please file bugs when you see these issues, and we will deal with them appropriately.
OK I'll try to reproduce it--- but unless we test every l-m-c with all old releases, surely we're going to get regressions over time?
Cheers ---Dave
On Wed, Feb 16, 2011 at 2:56 PM, Dave Martin dave.martin@linaro.org wrote:
On Wed, Feb 16, 2011 at 2:53 PM, James Westby james.westby@canonical.com wrote:
On Wed, 16 Feb 2011 12:55:31 +0000, Dave Martin dave.martin@linaro.org wrote:
So far, so good, but we still don't shapshort linaro-image-tools along with releases.
This will become a problem because l-i-t evolves over time -- I've already had to start explaining to people how to check out old versions of l-i-t in order to make use of the linaro-m release images. Installing the (unsupported) linaro-m release for panda doesn't work with current l-i-t, for example.
I would consider this a bug. I think it is impractical for us to ask everyone to use a different l-i-t for every release that they consume.
I also think it would be a massive headache for maintainence of l-i-t as well.
Please file bugs when you see these issues, and we will deal with them appropriately.
OK I'll try to reproduce it--- but unless we test every l-m-c with all old releases, surely we're going to get regressions over time?
Seems to be reproducible. Bug raised here:
https://bugs.launchpad.net/linaro-image-tools/+bug/720114
---Dave
On 16 February 2011 14:56, Dave Martin dave.martin@linaro.org wrote:
OK I'll try to reproduce it--- but unless we test every l-m-c with all old releases, surely we're going to get regressions over time?
Sounds like something it would be worth automating in hudson...
-- PMM
On Wed, Feb 16, 2011 at 4:45 PM, Peter Maydell peter.maydell@linaro.org wrote:
On 16 February 2011 14:56, Dave Martin dave.martin@linaro.org wrote:
OK I'll try to reproduce it--- but unless we test every l-m-c with all old releases, surely we're going to get regressions over time?
Sounds like something it would be worth automating in hudson...
yes, validating tools like l-m-c will be covered at some point as part of our greater automated validation efforts ...
On Wed, Feb 16, 2011 at 11:58 PM, Alexander Sack asac@linaro.org wrote:
On Wed, Feb 16, 2011 at 4:45 PM, Peter Maydell peter.maydell@linaro.org wrote:
On 16 February 2011 14:56, Dave Martin dave.martin@linaro.org wrote:
OK I'll try to reproduce it--- but unless we test every l-m-c with all old releases, surely we're going to get regressions over time?
Sounds like something it would be worth automating in hudson...
yes, validating tools like l-m-c will be covered at some point as part of our greater automated validation efforts ...
Fair enough -- so long as we'll have some way to make sure old releases are still installable, that should be fine.
Cheers ---Dave
On 8 February 2011 13:10, Jamie Bennett jamie.bennett@linaro.org wrote:
There is now a much easier way to download the daily Linaro images and hardware packs, the /latest link. Inside each build directory a /latest link will always point to the latest successful build.
http://snapshots.linaro.org/11.05-daily/linaro-headless/latest
This currently points to 20110217 which is a failed build, not a successful one...
-- PMM
-
Alexander Sack -
Amit Kucheria -
Dave Martin -
James Westby -
Jamie Bennett -
Loïc Minier -
Paul Larson -
Peter Maydell -
Steve Langasek