Bug 1154

Summary:	Yocto 1.1 quickstart points to the 1.0 downloads directory which includes poky-bernard-5.0
Product:	[Documentation] Quick Start	Reporter:	Joshua Lock - Disabled <josh>
Component:	quick-start	Assignee:	Scott Rifenbark <srifenbark>
Status:	VERIFIED FIXED	QA Contact:
Severity:	normal
Priority:	Medium	CC:	dvhart, Infras.watcher, infras.web.watcher, liezhi.yang, poky.doc.watcher, poky.watcher
Version:	unspecified
Target Milestone:	1.1
Hardware:	x86
OS:	Multiple
URL:	http://git.yoctoproject.org/cgit.cgi/poky/commit/?id=a27fbe5e25a5aee956d2a43a2e2bf671c6d985f2
Whiteboard:	23 aug 2011 - changed status to resolved/fixed
OS type for building Yocto:	---	Type of Regression:	---
Verified:		Documentation change:	---

Description Joshua Lock - Disabled 2011-06-09 15:58:09 UTC

Per the title, the Yocto 1.1 quickstart points to the 1.0 downloads directory which includes poky-bernard-5.0

This isn't too much of an issue once we fix the QS to reference the 5.0.1 tarball in the wget line but I feel it would make sense also to have a copy-of/symlink-to the 5.0.1 tarball in the 1.0 downloads directory since we explicitly point people at it in the QS.

Thoughts?

Comment 1 Scott Rifenbark 2011-06-14 16:32:18 UTC

I talked with Beth about this and pointed out the fact that only the 1.0 tarball is in the yocto-1.0 area of the index of downloads.  She said that everything was going to be in the 'poky' area now.  

Also, i fixed the QS to point the user to the download page on the website now and instruct them to pick their release from there.  The only exposure to the index of downloads area is the wget example.

Comment 2 Scott Rifenbark 2011-08-23 17:16:17 UTC

I changed the status to resolved/fixed.

http://git.yoctoproject.org/cgit.cgi/poky/commit/?id=a27fbe5e25a5aee956d2a43a2e2bf671c6d985f2

Comment 3 Joshua Lock - Disabled 2012-04-18 00:18:21 UTC

poky.ent saves us

Comment 4 Scott Rifenbark 2012-04-18 12:03:07 UTC

Yes - poky.ent is a much better way to go.

Comment 5 Robert Yang 2017-04-13 09:51:13 UTC

*** Bug 11353 has been marked as a duplicate of this bug. ***