Re: [yocto-announce] Mailing list platform change November 21st
The window for the mailing list move has shifted forward to November 21st from 4pm to 8pm Pacific Standard Time. (2019-11-22 00:00-04:00 UTC) Moderators please tend to all pending requests today. Thank you, -- Michael Halstead Linux Foundation / Yocto Project Systems Operations Engineer On Fri, Nov 15, 2019 at 4:25 PM Michael Halstead < mhalst...@linuxfoundation.org> wrote: > After backing out of the first attempt to migrate we are again moving > our lists from Mailman to Groups.io. E-mail to lists will be delayed > during the move window on November 21st between 17:00 and 23:00 UTC. > > A new account will be created for you on the Groups.io platform and most > users will only need to update their list mailing address from the > @yoctoproject.org to @lists.yoctoproject.org. > > Moderators please attend to all pending requests next Wednesday November > 20th. > > Please read more about the change on the wiki: > > https://wiki.yoctoproject.org/wiki/index.php?title=GroupsMigration > > If there are serious issues we will rollback the changes. We will e-mail > all lists when work is complete. > > -- > Michael Halstead > Linux Foundation / Yocto Project > Systems Operations Engineer > -- ___ yocto-announce mailing list yocto-announce@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto-announce
Re: [yocto] Mailing list platform change November 21st
The window for the mailing list move has shifted forward to November 21st from 4pm to 8pm Pacific Standard Time. (2019-11-22 00:00-04:00 UTC) Moderators please tend to all pending requests today. Thank you, -- Michael Halstead Linux Foundation / Yocto Project Systems Operations Engineer On Fri, Nov 15, 2019 at 4:25 PM Michael Halstead < mhalst...@linuxfoundation.org> wrote: > After backing out of the first attempt to migrate we are again moving > our lists from Mailman to Groups.io. E-mail to lists will be delayed > during the move window on November 21st between 17:00 and 23:00 UTC. > > A new account will be created for you on the Groups.io platform and most > users will only need to update their list mailing address from the > @yoctoproject.org to @lists.yoctoproject.org. > > Moderators please attend to all pending requests next Wednesday November > 20th. > > Please read more about the change on the wiki: > > https://wiki.yoctoproject.org/wiki/index.php?title=GroupsMigration > > If there are serious issues we will rollback the changes. We will e-mail > all lists when work is complete. > > -- > Michael Halstead > Linux Foundation / Yocto Project > Systems Operations Engineer > -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto-announce] Mailing list platform change November 21st
After backing out of the first attempt to migrate we are again moving our lists from Mailman to Groups.io. E-mail to lists will be delayed during the move window on November 21st between 17:00 and 23:00 UTC. A new account will be created for you on the Groups.io platform and most users will only need to update their list mailing address from the @yoctoproject.org to @lists.yoctoproject.org. Moderators please attend to all pending requests next Wednesday November 20th. Please read more about the change on the wiki: https://wiki.yoctoproject.org/wiki/index.php?title=GroupsMigration If there are serious issues we will rollback the changes. We will e-mail all lists when work is complete. -- Michael Halstead Linux Foundation / Yocto Project Systems Operations Engineer pEpkey.asc Description: application/pgp-keys -- ___ yocto-announce mailing list yocto-announce@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto-announce
[yocto] [yocto-autobuilder2][PATCH][v2] scheduler: make the default choice an option
The default choice on the force build form will select a random worker.
builder_to_workers dictionary values can no longer be strings.
Signed-off-by: Michael Halstead
---
config.py | 4 ++--
schedulers.py | 2 +-
2 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/config.py b/config.py
index e9d6d98..1577bcf 100644
--- a/config.py
+++ b/config.py
@@ -127,7 +127,7 @@ builder_to_workers = {
"oe-selftest-opensuse": workers_opensuse,
"oe-selftest-centos": workers_centos,
"meta-mingw": workers_wine,
-"buildperf-ubuntu1604": "perf-ubuntu1604",
-"buildperf-centos7": "perf-centos7",
+"buildperf-ubuntu1604": ["perf-ubuntu1604"],
+"buildperf-centos7": ["perf-centos7"],
"default": workers
}
diff --git a/schedulers.py b/schedulers.py
index b22f18f..671baae 100644
--- a/schedulers.py
+++ b/schedulers.py
@@ -81,7 +81,7 @@ def props_for_builder(builder):
default="*",
multiple=False,
strict=True,
- choices=worker_list))
+ choices=worker_list + ["*"]))
return props
--
2.21.0
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] [yocto-autobuilder2][PATCH] scheduler: make the default choice an option
The default choice on the force build form will select a random worker.
Updating to the corrent config. Note builder_to_workers dictionary values can
no longer be strings.
Signed-off-by: Michael Halstead
---
config.py | 40 +++-
schedulers.py | 2 +-
2 files changed, 24 insertions(+), 18 deletions(-)
diff --git a/config.py b/config.py
index e9d6d98..54977cd 100644
--- a/config.py
+++ b/config.py
@@ -61,26 +61,26 @@ trigger_builders_wait_shared = [
"non-gpl3", "wic",
"poky-tiny", "musl-qemux86", "musl-qemux86-64", "no-x11",
"qa-extras", "qa-extras2",
-"check-layer", "meta-mingw"
+"check-layer", "meta-mingw",
+"qemuarm64-armhost"
]
trigger_builders_wait_quick = trigger_builders_wait_shared + [
-"oe-selftest", "qemux86-64-ptest-fast"
+"oe-selftest", "qemux86-64-ptest-fast", "qemuarm64-ptest-fast"
]
trigger_builders_wait_full = trigger_builders_wait_shared + [
"qemumips-alt", "edgerouter-alt", "mpc8315e-rdb-alt", "qemuppc-alt",
"qemux86-world-alt",
"oe-selftest-ubuntu", "oe-selftest-debian", "oe-selftest-fedora",
"oe-selftest-centos",
-"qemux86-64-ptest", "buildperf-ubuntu1604", "buildperf-centos7",
"qemux86-64-ltp"
+"qemux86-64-ptest", "buildperf-ubuntu1604", "buildperf-centos7",
"qemux86-64-ltp",
+"qemuarm64-ptest", "qemuarm64-ltp"
]
# Builders which are individually triggered
builders_others = [
"meta-oe", "meta-virt", "meta-intel",
"bringup",
-"qemuarm64-ptest",
-"qemuarm64-ptest-fast",
-"qemuarm64-ltp"
+"qemuarm-armhost"
]
subbuilders = list(set(trigger_builders_wait_quick +
trigger_builders_wait_full + builders_others))
@@ -88,32 +88,33 @@ builders = ["a-quick", "a-full"] + subbuilders
# ## Cluster configuration
# Publishing settings
-sharedrepodir = "/srv/www/vhosts/repos.yoctoproject.org"
-publish_dest = "/srv/www/vhosts/autobuilder.yoctoproject.org/pub"
+sharedrepodir = "/srv/autobuilder/repos"
+publish_dest = "/srv/autobuilder/autobuilder.yoctoproject.org/pub"
# Web UI settings
web_port = 8010
# List of workers in the cluster
-workers_ubuntu = ["ubuntu1804-ty-1", "ubuntu1804-ty-2", "ubuntu1804-ty-3",
"ubuntu1604-ty-1"]
+workers_ubuntu = ["ubuntu1904-ty-1", "ubuntu1804-ty-1", "ubuntu1804-ty-2",
"ubuntu1804-ty-3", "ubuntu1604-ty-1"]
workers_centos = ["centos7-ty-1", "centos7-ty-2", "centos7-ty-3",
"centos7-ty-4"]
-workers_fedora = ["fedora28-ty-1", "fedora29-ty-1"]
-workers_debian = ["debian9-ty-1", "debian8-ty-1", "debian9-ty-2"]
-workers_opensuse = ["opensuse423-ty-1", "opensuse150-ty-1"]
+workers_fedora = ["fedora29-ty-1", "fedora30-ty-1", "fedora30-ty-2"]
+workers_debian = ["debian8-ty-1", "debian9-ty-2", "debian10-ty-1",
"debian10-ty-2", "debian10-ty-3"]
+workers_opensuse = ["tumbleweed-ty-1", "tumbleweed-ty-2", "tumbleweed-ty-3",
"opensuse151-ty-1", "opensuse150-ty-1"]
workers = workers_ubuntu + workers_centos + workers_fedora + workers_debian +
workers_opensuse
-workers_bringup = ["rhel8-ty-1", "tumbleweed-ty-1", "ubuntu1804-arm-1"]
+workers_bringup = []
# workers with wine on them for meta-mingw
workers_wine = ["ubuntu1804-ty-1", "ubuntu1804-ty-2", "ubuntu1804-ty-3"]
workers_buildperf = ["perf-ubuntu1604", "perf-centos7"]
+workers_arm = ["ubuntu1804-arm-1"]
-all_workers = workers + workers_bringup + workers_buildperf
+all_workers = workers + workers_bringup + workers_buildperf + workers_arm
# Worker configuration, all workers configured the same...
# TODO: support per-worker config
worker_password = "pass"
-worker_max_builds = None
+worker_max_builds = 3
notify_on_missing = None
# Some builders should only run on specific workers (host OS dependent)
@@ -127,7 +128,12 @@ builder_to_workers = {
"oe-selftest-opensuse": workers_opensuse,
"oe-selftest-centos": workers_centos,
"meta-mingw": workers_wine,
-"buildperf-ubuntu1604": "perf-ubuntu1604",
-"buildperf-centos7": "perf-centos7",
+"buildperf-ubuntu1604": ["perf-ubuntu1604"],
+"buildperf-centos7": ["perf-centos7"],
+"qemuarm-armhost": workers_arm,
+"qemuarm64-ptest": workers_arm,
+"qemuarm64-ptest-fast": workers_arm,
+"qemuarm64-ltp": workers_arm,
+"qemuarm64-armhost": workers_arm,
"default": workers
}
diff --git a/schedulers.py b/schedulers.py
index da87c1b..a014fbf 100644
--- a/schedulers.py
+++ b/schedulers.py
@@ -81,7 +81,7 @@ def props_for_builder(builder):
default="*",
multiple=False,
strict=True,
- choices=worker_list))
+ choices=worker_list + ["*"]))
return props
--
2.21.0
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[linux-yocto] Mailing list update September 15th - platform change delayed
This Sunday I will take the Mailman mailing lists offline for updates in preparation for the platform change. As part of the update I plan to change the list addresses to their new dedicated domain @lists.yoctoproject.org so we can start changing addresses in the MAINTAINERS files and elsewhere. Moderators, thanks for helping by clearing out the queues in advance. If you have outstanding moderation or trouble clearing your queue please reach out to me. I will send a follow up e-mail with a new time line for the platform change after these updates are in place. -- Michael Halstead Linux Foundation / Yocto Project Systems Operations Engineer pEpkey.asc Description: application/pgp-keys -- ___ linux-yocto mailing list linux-yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/linux-yocto
[Yocto-bsp] Mailing list update September 15th - platform change delayed
This Sunday I will take the Mailman mailing lists offline for updates in preparation for the platform change. As part of the update I plan to change the list addresses to their new dedicated domain @lists.yoctoproject.org so we can start changing addresses in the MAINTAINERS files and elsewhere. Moderators, thanks for helping by clearing out the queues in advance. If you have outstanding moderation or trouble clearing your queue please reach out to me. I will send a follow up e-mail with a new time line for the platform change after these updates are in place. -- Michael Halstead Linux Foundation / Yocto Project Systems Operations Engineer pEpkey.asc Description: application/pgp-keys -- ___ yocto-bsp mailing list yocto-bsp@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto-bsp
[yocto-announce] Mailing list update September 15th - platform change delayed
This Sunday I will take the Mailman mailing lists offline for updates in preparation for the platform change. As part of the update I plan to change the list addresses to their new dedicated domain @lists.yoctoproject.org so we can start changing addresses in the MAINTAINERS files and elsewhere. Moderators, thanks for helping by clearing out the queues in advance. If you have outstanding moderation or trouble clearing your queue please reach out to me. I will send a follow up e-mail with a new time line for the platform change after these updates are in place. -- Michael Halstead Linux Foundation / Yocto Project Systems Operations Engineer pEpkey.asc Description: application/pgp-keys -- ___ yocto-announce mailing list yocto-announce@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto-announce
[yocto] Mailing list update September 15th - platform change delayed
This Sunday I will take the Mailman mailing lists offline for updates in preparation for the platform change. As part of the update I plan to change the list addresses to their new dedicated domain @lists.yoctoproject.org so we can start changing addresses in the MAINTAINERS files and elsewhere. Moderators, thanks for helping by clearing out the queues in advance. If you have outstanding moderation or trouble clearing your queue please reach out to me. I will send a follow up e-mail with a new time line for the platform change after these updates are in place. -- Michael Halstead Linux Foundation / Yocto Project Systems Operations Engineer pEpkey.asc Description: application/pgp-keys -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto-announce] Mailing list platform change September 15th
We are moving our lists from Mailman to Groups.io. E-mail to lists will be delayed during the move window on September 15th between 9:00 and 17:00 UTC. A new account will be created for you on the Groups.io platform and most users will only need to update their list mailing address from the @yoctoproject.org to @lists.yoctoproject.org. Moderators please attend to all pending requests next Friday Sept. 13th before beginning your weekend. Please read more about the change on the wiki: https://wiki.yoctoproject.org/wiki/index.php?title=GroupsMigration If there are serious issues we will rollback the changes. We will e-mail all lists when work is complete. -- Michael Halstead Linux Foundation / SysAdmin -- ___ yocto-announce mailing list yocto-announce@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto-announce
[yocto] Mailing list platform change September 15th
We are moving our lists from Mailman to Groups.io. E-mail to lists will be delayed during the move window on September 15th between 9:00 and 17:00 UTC. A new account will be created for you on the Groups.io platform and most users will only need to update their list mailing address from the @yoctoproject.org to @lists.yoctoproject.org. Moderators please attend to all pending requests next Friday Sept. 13th before beginning your weekend. Please read more about the change on the wiki: https://wiki.yoctoproject.org/wiki/index.php?title=GroupsMigration If there are serious issues we will rollback the changes. We will e-mail all lists when work is complete. -- Michael Halstead Linux Foundation / SysAdmin -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[Yocto-bsp] Mailing list platform change September 15th
We are moving our lists from Mailman to Groups.io. E-mail to lists will be delayed during the move window on September 15th between 9:00 and 17:00 UTC. A new account will be created for you on the Groups.io platform and most users will only need to update their list mailing address from the @yoctoproject.org to @lists.yoctoproject.org. Moderators please attend to all pending requests next Friday Sept. 13th before beginning your weekend. Please read more about the change on the wiki: https://wiki.yoctoproject.org/wiki/index.php?title=GroupsMigration If there are serious issues we will rollback the changes. We will e-mail all lists when work is complete. -- Michael Halstead Linux Foundation / SysAdmin -- ___ yocto-bsp mailing list yocto-bsp@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto-bsp
Re: [yocto] [PATCH][yocto-docs] ref-manual: Corrected openSUSE essential packages
On Thu, Jun 6, 2019 at 5:07 PM akuster808 wrote: > > > On 6/6/19 4:46 PM, Michael Halstead wrote: > > Some packages were bumped onto the pip3 install line. Install them with > zypper as before. > with backport? ie is Warrior or Thud affected, I suspect so > Yes for Warrior. Thud is fine. Is there anything I need to do for the Warrior backport? > > - armin > > > > Signed-off-by: Michael Halstead > > --- > > documentation/poky.ent | 4 ++-- > > 1 file changed, 2 insertions(+), 2 deletions(-) > > > > diff --git a/documentation/poky.ent b/documentation/poky.ent > > index b5f600969..a436d9027 100644 > > --- a/documentation/poky.ent > > +++ b/documentation/poky.ent > > @@ -68,8 +68,8 @@ > > python3-jinja2 SDL-devel xterm"> > > chrpath make wget python-xml \ > > diffstat makeinfo python-curses patch socat python3 python3-curses > tar python3-pip \ > > - python3-pexpect xz which python3-Jinja2 Mesa-libEGL1 > > - $ sudo pip3 install GitPython libSDL-devel xterm"> > > + python3-pexpect xz which python3-Jinja2 Mesa-libEGL1 libSDL-devel > xterm > > + $ sudo pip3 install GitPython"> > > > $ sudo yum makecache > > $ sudo yum install gawk make wget tar bzip2 gzip python unzip perl > patch \ > > -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] [PATCH][yocto-docs] ref-manual: Corrected openSUSE essential packages
Some packages were bumped onto the pip3 install line. Install them with zypper as before. Signed-off-by: Michael Halstead --- documentation/poky.ent | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/documentation/poky.ent b/documentation/poky.ent index b5f600969..a436d9027 100644 --- a/documentation/poky.ent +++ b/documentation/poky.ent @@ -68,8 +68,8 @@ python3-jinja2 SDL-devel xterm"> + python3-pexpect xz which python3-Jinja2 Mesa-libEGL1 libSDL-devel xterm + $ sudo pip3 install GitPython"> https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [yocto-infrastructure] Upcoming network outage: Fri, May 17 starting 10PM PDT (Sat, 5:00Z)
On 5/11/19 1:59 PM, akuster808 wrote: > > > On 5/10/19 4:21 PM, Michael Halstead wrote: >> What: 30-minute network outage to Portland-hosted services >> When: Fri, May 17, between 10PM-3AM PDT (Sat, 05:00-10:00 UTC) >> Why : Network equipment replacement by our service provider >> >> Services Impacted: autobuilder.yoctoproject.org >> <http://autobuilder.yoctoproject.org>, downloads.yoctoproject.org >> <http://downloads.yoctoproject.org>, sstate.yoctoproject.org >> <http://sstate.yoctoproject.org> >> >> Our Portland hosting provider needs to replace some of their main >> network equipment, which will require rerunning some cables. They are >> asking us to prepare for up to a 30-minute network outage between the >> hours listed above in order to complete this work. > > Thanks for the heads up. > > Is there a time on Sat that if things are not back to normal that we > should contact you? I hope and don't expect you to be working @ 3am. Please ping if services are un-available after 7am on Saturday. That's when I'm planning to check in on my alerts. > > regards, > Armin >> >> -- >> Michael Halstead >> Linux Foundation / SysAdmin >> >> > -- Michael Halstead Linux Foundation / SysAdmin -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] Upcoming network outage: Fri, May 17 starting 10PM PDT (Sat, 5:00Z)
What: 30-minute network outage to Portland-hosted services When: Fri, May 17, between 10PM-3AM PDT (Sat, 05:00-10:00 UTC) Why : Network equipment replacement by our service provider Services Impacted: autobuilder.yoctoproject.org, downloads.yoctoproject.org, sstate.yoctoproject.org Our Portland hosting provider needs to replace some of their main network equipment, which will require rerunning some cables. They are asking us to prepare for up to a 30-minute network outage between the hours listed above in order to complete this work. -- Michael Halstead Linux Foundation / SysAdmin -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] git.yoctoproject.org TLS certificate expired
On 5/4/19 9:19 AM, Adrian Bunk wrote: > $ git pull > fatal: unable to access 'https://git.yoctoproject.org/git/poky/': server > certificate verification failed. CAfile: none CRLfile: none > $ > > > Firefox says: > git.yoctoproject.org uses an invalid security certificate. The > certificate expired on May 4, 2019, 7:53 AM. The current time is May 4, > 2019, 7:16 PM. > > > cu > Adrian I've renewed the certificate manually for now. I will review the automated process and monitoring to make sure this doesn't happen again. -- Michael Halstead Yocto Project / SysAdmin -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [OE-core] Yocto Project Status WW07'19
The regular 3 hour update wasn't installed on the new server. I have repaired that and added the RRS updates as well.. The update has been run several times in testing and I'm curious if RRS has caught up as expected. On 2/12/19 5:57 PM, Paul Eggleton wrote: Hi Alex On Wednesday, 13 February 2019 6:22:23 AM NZDT Alexander Kanavin wrote: On Tue, 12 Feb 2019 at 17:10, wrote: The recipe reporting system integration with the layer index is available at: https://layers.openembedded.org/rrs/recipes/OE-Core/2.7/M3/ and the historical data has now been imported. Sadly the new RRS still seems to be suffering from the 'outdated info' problem. For example glibc, or python3 recipes have been updated to latest versions, yet RRS still shows that they haven't been. We're reliant upon the layer index updating and it appears that's not working at the moment. I have asked Michael to look into it. Thanks for the report, I'll reply back here when things are sorted out. Cheers, Paul -- Michael Halstead Linux Foundation / SysAdmin -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [Recipe reporting system] Upgradable recipe name list
3.5 Robert Yang git 2.18.1 2.20.1Robert Yang mklibs-native 0.1.43 0.1.44Robert Yang piglit1.0+gitrX1.0-new-commits-a... Ross Burton acpid 2.0.30 2.0.31Ross Burton libinput 1.12.3 1.12.4Ross Burton vulkan-demos git git-new-commits-a... Ross Burton perl 5.24.4 5.28.1Ross Burton gtk-icon-utils-na... 3.22.30 3.24.2Ross Burton ofono 1.25 1.26 Ross Burton libical 2.0.03.0.4 Ross Burton vulkan1.1.73.0 1.1.92.1 Ross Burton lsbinitscripts9.79 10.01 Ross Burton sysvinit 2.88dsf 2.93 Ross Burton adwaita-icon-theme3.28.0 3.30.1Ross Burton fontconfig2.12.6 2.13.1Ross Burton gdk-pixbuf2.36.11 2.38.0Ross Burton gtk+3 3.24.1 3.24.2Ross Burton pkgconf 1.5.31.5.4 Ross Burton perl-native 5.24.4 5.28.1Ross Burton alsa-tools1.1.61.1.7 Tanu Kaskinen alsa-plugins 1.1.61.1.7 Tanu Kaskinen alsa-utils-scripts1.1.61.1.7 Tanu Kaskinen alsa-lib 1.1.61.1.7 Tanu Kaskinen alsa-utils1.1.61.1.7 Tanu Kaskinen gnu-efi 3.0.83.0.9 Yi Zhao libcap2.25 2.26 Yi Zhao chkconfig 1.3.58 1.8 Yi Zhao Version 1.5 requires selinux logrotate 3.14.0 3.15.0Yi Zhao file 5.34 5.35 Yi Zhao wget 1.19.5 1.20 Yi Zhao json-glib 1.4.21.4.4 Yi Zhao libsdl2 2.0.82.0.9 Yi Zhao Upgradable count: 147 Upgradable total count: 151 The based commit is: commit 9908b7955e75e10d6a1384e4c08417ef534464af Author: Richard Purdie Date: Sun Jan 20 12:18:52 2019 + scripts/contrib/build-perf-test.sh: Remove it This is the older script which the code in lib/oeqa/buildperf replaces so delete the obsolete script to avoid confusion. Signed-off-by: Richard Purdie Any problem, please contact Jose Lamego -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto -- Michael Halstead Linux Foundation / SysAdmin -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [patchtest][PATCH] scripts: Reset working repository to match origin during clean up
On 1/11/19 1:53 PM, Khem Raj wrote:
OK then I need to understand how this will be invoked for
meta-openembedded repos
I think that is beyond the scope of this patch. Can you clarify a bit
more? Or perhaps this topic deserves its own thread on an OE list.
On Fri, Jan 11, 2019 at 1:47 PM Michael Halstead
wrote:
Since these commands run in $REPODIR and $path I think they will apply to any
repository under test.
On 1/11/19 12:25 PM, Khem Raj wrote:
Hi Michael
Can we enable these checks for meta-openembedded repo as well
On Fri, Jan 11, 2019 at 11:03 AM Michael Halstead
wrote:
If the local HEAD is a patchtest generated merge commit patchtest may be unable
to apply new patches. This should prevent patchtest from becoming stuck
in that state.
Signed-off-by: Michael Halstead
---
scripts/create-share-folder | 2 +-
scripts/host| 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/scripts/create-share-folder b/scripts/create-share-folder
index 861da4b..9432cb1 100755
--- a/scripts/create-share-folder
+++ b/scripts/create-share-folder
@@ -122,7 +122,7 @@ function update_repository() {
(
cd $REPODIR
git am --abort --quiet
- git reset --hard --quiet
+ git reset --hard --quiet FETCH_HEAD
git clean -f -e ".git-pw*" --quiet
)
diff --git a/scripts/host b/scripts/host
index 85f0e4a..893ce63 100755
--- a/scripts/host
+++ b/scripts/host
@@ -83,7 +83,7 @@ function clean() {
(
cd $path
git am --abort
- git reset --hard
+ git reset --hard FETCH_HEAD
git clean -f -e ".git-pw*"
)
}
--
2.17.2
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
--
Michael Halstead
Linux Foundation / SysAdmin
--
Michael Halstead
Linux Foundation / SysAdmin
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [patchtest][PATCH] scripts: Reset working repository to match origin during clean up
Since these commands run in $REPODIR and $path I think they will apply
to any repository under test.
On 1/11/19 12:25 PM, Khem Raj wrote:
Hi Michael
Can we enable these checks for meta-openembedded repo as well
On Fri, Jan 11, 2019 at 11:03 AM Michael Halstead
mailto:mhalst...@linuxfoundation.org>>
wrote:
If the local HEAD is a patchtest generated merge commit patchtest
may be unable
to apply new patches. This should prevent patchtest from becoming
stuck
in that state.
Signed-off-by: Michael Halstead mailto:mhalst...@linuxfoundation.org>>
---
scripts/create-share-folder | 2 +-
scripts/host | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/scripts/create-share-folder b/scripts/create-share-folder
index 861da4b..9432cb1 100755
--- a/scripts/create-share-folder
+++ b/scripts/create-share-folder
@@ -122,7 +122,7 @@ function update_repository() {
(
cd $REPODIR
git am --abort --quiet
- git reset --hard --quiet
+ git reset --hard --quiet FETCH_HEAD
git clean -f -e ".git-pw*" --quiet
)
diff --git a/scripts/host b/scripts/host
index 85f0e4a..893ce63 100755
--- a/scripts/host
+++ b/scripts/host
@@ -83,7 +83,7 @@ function clean() {
(
cd $path
git am --abort
- git reset --hard
+ git reset --hard FETCH_HEAD
git clean -f -e ".git-pw*"
)
}
--
2.17.2
--
___
yocto mailing list
yocto@yoctoproject.org <mailto:yocto@yoctoproject.org>
https://lists.yoctoproject.org/listinfo/yocto
--
Michael Halstead
Linux Foundation / SysAdmin
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] [patchtest][PATCH] scripts: Reset working repository to match origin during clean up
If the local HEAD is a patchtest generated merge commit patchtest may be unable
to apply new patches. This should prevent patchtest from becoming stuck
in that state.
Signed-off-by: Michael Halstead
---
scripts/create-share-folder | 2 +-
scripts/host| 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/scripts/create-share-folder b/scripts/create-share-folder
index 861da4b..9432cb1 100755
--- a/scripts/create-share-folder
+++ b/scripts/create-share-folder
@@ -122,7 +122,7 @@ function update_repository() {
(
cd $REPODIR
git am --abort --quiet
- git reset --hard --quiet
+ git reset --hard --quiet FETCH_HEAD
git clean -f -e ".git-pw*" --quiet
)
diff --git a/scripts/host b/scripts/host
index 85f0e4a..893ce63 100755
--- a/scripts/host
+++ b/scripts/host
@@ -83,7 +83,7 @@ function clean() {
(
cd $path
git am --abort
- git reset --hard
+ git reset --hard FETCH_HEAD
git clean -f -e ".git-pw*"
)
}
--
2.17.2
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [Recipe reporting system] Upgradable recipe name list
Pascal Bach cmake-native 3.12.2 3.13.2Pascal Bach build-compare 2015.02.10+gitX 2015.02.10-new-co... Paul Eggleton build-appliance-i... 15.0.0 20.0.0Richard Purdie gnu-config20180713+gitX20180713-new-comm... Robert Yang squashfs-tools4.3+gitrX4.3-new-commits-a... Robert Yang e2fsprogs 1.44.3 1.44.5Robert Yang ccache3.4.23.5 Robert Yang git 2.18.1 2.20.1Robert Yang mklibs-native 0.1.43 0.1.44Robert Yang piglit1.0+gitrX1.0-new-commits-a... Ross Burton acpid 2.0.30 2.0.31Ross Burton libinput 1.12.3 1.12.4Ross Burton vulkan-demos git git-new-commits-a... Ross Burton perl 5.24.4 5.28.1Ross Burton gtk-icon-utils-na... 3.22.30 3.24.2Ross Burton ofono 1.25 1.26 Ross Burton libical 2.0.03.0.4 Ross Burton vulkan1.1.73.0 1.1.92.1 Ross Burton lsbinitscripts9.79 10.01 Ross Burton sysvinit 2.88dsf 2.93 Ross Burton adwaita-icon-theme3.28.0 3.30.1Ross Burton fontconfig2.12.6 2.13.1Ross Burton gdk-pixbuf2.36.11 2.38.0Ross Burton gtk+3 3.24.1 3.24.2Ross Burton pkgconf 1.5.31.5.4 Ross Burton perl-native 5.24.4 5.28.1Ross Burton alsa-tools1.1.61.1.7 Tanu Kaskinen alsa-plugins 1.1.61.1.7 Tanu Kaskinen alsa-utils-scripts1.1.61.1.7 Tanu Kaskinen alsa-lib 1.1.61.1.7 Tanu Kaskinen alsa-utils1.1.61.1.7 Tanu Kaskinen gnu-efi 3.0.83.0.9 Yi Zhao libcap2.25 2.26 Yi Zhao chkconfig 1.3.58 1.8 Yi Zhao Version 1.5 requires selinux logrotate 3.14.0 3.15.0Yi Zhao file 5.34 5.35 Yi Zhao wget 1.19.5 1.20 Yi Zhao json-glib 1.4.21.4.4 Yi Zhao libsdl2 2.0.82.0.9 Yi Zhao Upgradable count: 147 Upgradable total count: 151 The based commit is: commit c22b0bf66a28324da66caf0660f171cc279a1f2b Author: Robert Yang Date: Tue Dec 18 17:48:22 2018 +0800 cmake-native: Set --parallel for configure This can save do_configure's time from 330s to 60s on my host. Signed-off-by: Robert Yang Signed-off-by: Richard Purdie Any problem, please contact Jose Lamego -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto -- Michael Halstead Linux Foundation / SysAdmin -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] [yocto-autobuilder-helper][PATCH] config.json: Enable dedicated sstate during build and remove after
Without any sstate available oe-selftest cannot run in parallel. Set sstate to a
location used only by these builds and remove it as the last step.
Signed-off-by: Michael Halstead
---
config.json | 5 -
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/config.json b/config.json
index 8a694d7..d898bf3 100644
--- a/config.json
+++ b/config.json
@@ -147,7 +147,7 @@
},
"nightly-bringup" : {
"TEMPLATE" : "nightly-arch",
-"SSTATEDIR" : [],
+"SSTATEDIR" : ["${BUILDDIR}/../sstate"],
"MACHINE" : "qemuarm64",
"step2" : {
"MACHINE" : "qemux86-64"
@@ -168,6 +168,9 @@
],
"EXTRACMDS" : ["${SCRIPTSDIR}/checkvnc; DISPLAY=:1 oe-selftest
--skip-tests distrodata.Distrodata.test_checkpkg -j 15"],
"ADDLAYER" : ["${BUILDDIR}/../meta-selftest"]
+},
+"step7" : {
+ "EXTRACMDS" : ["rm -rf ${BUILDDIR}/../sstate"]
}
},
"nightly-mips" : {
--
2.17.2
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [patchtest-oe][PATCH] test_patch_cve.py: fix cve tag checking logic
When updating patchtest-oe to include the CVE fixes I also cleaned up repositories in the share directory removing the patchwork credentials in the process. I've restored the patchwork credentials and posted the test results from local backups. I've opened a bug to collect ideas for testing patchtest upgrades at https://bugzilla.yoctoproject.org/show_bug.cgi?id=13002. On 11/8/18 11:38 PM, Mittal, Anuj wrote: > On Wed, 2018-11-07 at 09:01 +, Richard Purdie wrote: >> On Fri, 2018-11-02 at 14:03 +0800, Chen Qi wrote: >>> The current logic for checking cve tag is not correct. It errors >>> out if and only if the patch contains a line which begins with >>> CVE-- and contains nothing else. >>> >>> It will not error out if the patch contains no CVE information, nor >>> will it error out if the patch contains line like below. >>> >>> 'Fix CVE--' >>> >>> I can see that the cve tag checking logic tries to ensure the patch >>> contains something like 'CVE: CVE--'. So fix to implement >>> such >>> logic. >>> >>> Signed-off-by: Chen Qi >>> --- >>> tests/test_patch_cve.py | 15 --- >>> 1 file changed, 8 insertions(+), 7 deletions(-) >> Thanks, good find. >> >> I've merged this and I believe the instance should have it applied >> now >> too. >> > Not sure if this is related but it looks like the tests aren't running > at all now ... > > > https://patchwork.openembedded.org/project/oe-core/series/?ordering=-last_updated > > Thanks, > > Anuj -- Michael Halstead Linux Foundation / SysAdmin -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] [yocto-autobuilder-helper][PATCH] config.json: Disable BUILDINFO for oe-selftest
Currently the containerimage.ContainerImageTests.test_expected_files test
doesn't expect a file at /etc/build so BUILDINFO must be false for the test to
pass.
Signed-off-by: Michael Halstead
---
config.json | 1 +
1 file changed, 1 insertion(+)
diff --git a/config.json b/config.json
index 6288e4b..8a694d7 100644
--- a/config.json
+++ b/config.json
@@ -158,6 +158,7 @@
"BBTARGETS" : "core-image-minimal:do_populate_sdk_ext
core-image-sato:do_populate_sdk"
},
"step6" : {
+"BUILDINFO" : false,
"MACHINE" : "qemux86-64",
"SDKMACHINE" : "x86_64",
"PACKAGE_CLASSES" : "package_rpm",
--
2.17.2
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] [yocto-autobuilder-helper][PATCH] config.json: Remove sstate, add oe-selftest, and replace beaglebone
We want to build everything without sstate during bringup testing.
Adding oe-selftest will catch errors other targets wouldn't. We just want to
test on qemuarm64 and qemux86-64 architectures so remove beaglebone as an
unneeded third. This takes advantage of the template as well.
Signed-off-by: Michael Halstead
---
config.json | 17 ++---
1 file changed, 14 insertions(+), 3 deletions(-)
diff --git a/config.json b/config.json
index 2945155..abc5928 100644
--- a/config.json
+++ b/config.json
@@ -146,16 +146,27 @@
}
},
"nightly-bringup" : {
-"MACHINE" : "qemuarm",
"TEMPLATE" : "nightly-arch",
+"SSTATEDIR" : [],
+"MACHINE" : "qemuarm64",
"step2" : {
-"MACHINE" : "beaglebone-yocto",
-"BBTARGETS" : "core-image-sato core-image-sato-dev
core-image-sato-sdk core-image-minimal core-image-minimal-dev
core-image-sato-sdk-ptest core-image-sato:do_populate_sdk"
+"MACHINE" : "qemux86-64"
},
"step5" : {
"MACHINE" : "qemux86-64",
"SDKMACHINE" : "x86_64",
"BBTARGETS" : "core-image-minimal:do_populate_sdk_ext
core-image-sato:do_populate_sdk"
+},
+"step6" : {
+"MACHINE" : "qemux86-64",
+"SDKMACHINE" : "x86_64",
+"PACKAGE_CLASSES" : "package_rpm",
+"PRSERV" : false,
+"extravars" : [
+"RPM_GPG_SIGN_CHUNK = '1'"
+],
+"EXTRACMDS" : ["checkvnc; DISPLAY=:1 oe-selftest --skip-tests
distrodata.Distrodata.test_checkpkg -j 15"],
+"ADDLAYER" : ["${BUILDDIR}/../meta-selftest"]
}
},
"nightly-mips" : {
--
2.17.2
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] [yocto-autobuilder-helper][PATCH] config.json: Add steps to test new workers before adding to the main pool
We add workers to the nightly-bringup pool to test them in a production like
enviroment. Include one completely emulated target and one to test
virtualization extentions.
Signed-off-by: Michael Halstead
---
config.json | 13 +
1 file changed, 13 insertions(+)
diff --git a/config.json b/config.json
index f912abf..2945155 100644
--- a/config.json
+++ b/config.json
@@ -145,6 +145,19 @@
"SANITYTARGETS" : "core-image-minimal:do_testsdkext"
}
},
+ "nightly-bringup" : {
+"MACHINE" : "qemuarm",
+"TEMPLATE" : "nightly-arch",
+"step2" : {
+"MACHINE" : "beaglebone-yocto",
+"BBTARGETS" : "core-image-sato core-image-sato-dev
core-image-sato-sdk core-image-minimal core-image-minimal-dev
core-image-sato-sdk-ptest core-image-sato:do_populate_sdk"
+},
+"step5" : {
+"MACHINE" : "qemux86-64",
+"SDKMACHINE" : "x86_64",
+"BBTARGETS" : "core-image-minimal:do_populate_sdk_ext
core-image-sato:do_populate_sdk"
+}
+},
"nightly-mips" : {
"MACHINE" : "qemumips",
"TEMPLATE" : "nightly-arch",
--
2.17.2
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] [error-report-web][PATCH] Allow autobuilder filter string to match anywhere
Multiple build clusters use the same prefix so we match a more distinctive
string anywhere in the submitter name.
Signed-off-by: Michael Halstead
---
Post/feed.py | 2 +-
Post/views.py | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/Post/feed.py b/Post/feed.py
index 745ee23..45c5327 100644
--- a/Post/feed.py
+++ b/Post/feed.py
@@ -25,7 +25,7 @@ class LatestEntriesFeed(Feed):
if self.mode == results_mode.SPECIAL_SUBMITTER and
hasattr(settings,"SPECIAL_SUBMITTER"):
#Special submitter mode see settings.py to enable
name = settings.SPECIAL_SUBMITTER['name']
-queryset =
BuildFailure.objects.order_by('-BUILD__DATE').filter(BUILD__NAME__istartswith=name)[:self.limit]
+queryset =
BuildFailure.objects.order_by('-BUILD__DATE').filter(BUILD__NAME__icontains=name)[:self.limit]
else:
queryset =
BuildFailure.objects.order_by('-BUILD__DATE')[:self.limit]
diff --git a/Post/views.py b/Post/views.py
index 7f2cffb..cabd29b 100644
--- a/Post/views.py
+++ b/Post/views.py
@@ -205,7 +205,7 @@ def search(request, mode=results_mode.LATEST, **kwargs):
if mode == results_mode.SPECIAL_SUBMITTER and
hasattr(settings,"SPECIAL_SUBMITTER"):
#Special submitter mode see settings.py to enable
name = settings.SPECIAL_SUBMITTER['name']
-items = items.filter(BUILD__NAME__istartswith=name)
+items = items.filter(BUILD__NAME__icontains=name)
elif mode == results_mode.SEARCH and request.GET.has_key("query"):
query = request.GET["query"]
--
2.17.2
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] QA notification for completed autobuilder build (yocto-2.6_M3.rc1)
A build flagged for QA (yocto-2.6_M3.rc1) was completed on the autobuilder and is available at: https://autobuilder.yocto.io/pub/releases/yocto-2.6_M3.rc1 Build hash information: bitbake: e72be96cfa9f05fda5f420c7cfa8bcfa9304b884 eclipse-poky-neon: 303e46a6848f1937d12541a7fd58e61aa1361225 eclipse-poky-oxygen: f1a20dc6a5a252a4ed4484b618d579cbbc7d146e meta-gplv2: 813b7d2b5573d8591c6cd8087b326f0a0703d6b9 meta-intel: ba19605153725d66dc55e0a16962ae684e66c9e4 meta-mingw: 17887019257143f649a0f2e9caa9f814f7fb0b2a meta-qt3: 02f273cba6c25f5cf20cb66d8a417a83772c3179 meta-qt4: 8e791c40140460825956430ba86b6266fdec0a93 oecore: e3f5ceec690379d64bd38330111a32f6c8fc6353 poky: c6edf2f8bc5778b267e3a7f4e8875d22f359fb8d This is an automated message from the Yocto Project Autobuilder Git: git://git.yoctoproject.org/yocto-autobuilder2 Email: richard.pur...@linuxfoundation.org -- Michael Halstead Linux Foundation / SysAdmin -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Error Report Tool Purge
Currently the database is 26GB. I'm going to start purging un-visited reports older than 180 days today. I see some good suggestions in this thread. Khem, would you open an enhancement request describing the counts you are interested in preserving? On Thu, Jul 19, 2018 at 11:08 PM Martin Jansa wrote: > OK, so it's only visited links, not linked from ML or wiki or whatever, > right? > > How huge the database is? I've checked our internal instance and on > relatively slow VM we have: > 47 472 724 Post_buildstatstask > 2 715 091 Post_build > 559 655 Post_buildfailure > > we use postgresql, the db currently has 20GB, which is quite big for VM > with 10GB RAM and 12 E5-2699 cores so it's slow as well, but not terribly > slow, individual builds or build-failures are really fast, there are some > bad queries in django which are terrible, but we're not using those usually. > > Cheers, > > > On Thu, Jul 19, 2018 at 9:01 PM Brindle, Amanda R < > amanda.r.brin...@intel.com> wrote: > >> Every time a specific report is visited (with the end of the URL being >> /Errors/Details/), we are tracking if the referrer is another website, >> the reporting tool itself, or unknown. If the referrer is another website >> or unknown, then we won’t delete it. >> >> >> >> The purge script does not look at links to whole builds, so as it is >> right now, those would get deleted. If it’s common to link to whole builds, >> though, I can add something to the script to save reports from a visited or >> linked build. >> >> >> >> -Amanda Brindle >> >> >> >> *From:* Martin Jansa [mailto:martin.ja...@gmail.com] >> *Sent:* Thursday, July 19, 2018 11:38 AM >> *To:* Brindle, Amanda R >> *Cc:* Yocto Project >> *Subject:* Re: [yocto] Error Report Tool Purge >> >> >> >> I'm just curious, how are you tracking which reports were viewed or >> linked to (and linked from where)? I often use a link to >> http://errors.yoctoproject.org in the mailing list or the recipes/commit >> message instead of copy pasting whole build error, because it already >> shortens the build paths and shows useful additional information about the >> error. >> >> >> >> The links to whole builds on http://errors.yoctoproject.org were also >> often linked from "bitbake world status" e-mails and wiki like: >> >> https://www.openembedded.org/wiki/Bitbake_World_Status_Rocko >> >> and on many of them nobody clicked yet - should I expect that these will >> mostly get broken? >> >> >> >> Regards >> >> >> >> >> >> >> >> On Thu, Jul 19, 2018 at 8:30 PM Brindle, Amanda R < >> amanda.r.brin...@intel.com> wrote: >> >> Hello, >> >> >> >> The Error Reporting Tool’s database ( >> http://errors.yoctoproject.org/Errors/Latest/Autobuilder/) has grown to >> a huge size, and this is affecting the performance of the application. We >> are planning to run a purge to get rid of reports that we don’t need. We >> will keep reports from the last thirty days, as well as reports that have >> been viewed or linked to. If you have a specific report that you don’t want >> purged, please let me know by the end of the month. >> >> >> >> Amanda Brindle, Software Engineer >> >> 503-264-3970 >> >> amanda.r.brin...@intel.com >> >> >> >> -- >> ___ >> yocto mailing list >> yocto@yoctoproject.org >> https://lists.yoctoproject.org/listinfo/yocto >> >> -- > ___ > yocto mailing list > yocto@yoctoproject.org > https://lists.yoctoproject.org/listinfo/yocto > -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [Call to Action] Yocto Project Bug Triage
The meeting page is https://www.yoctoproject.org/public-virtual-meetings/ for anyone interested. On Tue, May 29, 2018 at 8:39 AM, Osier-mixon, Jeffrey < jeffrey.osier-mi...@intel.com> wrote: > Stephen and I put together a meetings page. I'll work with him on a > shareable calendar this week. > > > Original message ---- > From: Michael Halstead > Date: 5/29/18 8:37 AM (GMT-08:00) > To: Stephano Cetola , Trevor Woerner < > twoer...@gmail.com> > Cc: yocto@yoctoproject.org, "Jolley, Stephen K" < > stephen.k.jol...@intel.com>, "Osier-mixon, Jeffrey" < > jeffrey.osier-mi...@intel.com> > Subject: Re: [yocto] [Call to Action] Yocto Project Bug Triage > > > > On 05/29/2018 08:16 AM, Stephano Cetola wrote: > > On 5/29/18 8:00 AM, Trevor Woerner wrote: > >> Is someone working on putting together a (google?) calendar of the > >> various project (OE Yocto) meetings? > > Great question. > > > > Michael, do we have access to a Yocto Project google account? > > > > --S > > > I don't but I think this is being worked on currently. It appears new > meetings are being scheduled by theyoctoproj...@gmail.com. Whoever > controls that account should be able to make the calendar public. > > -- > Michael Halstead > Linux Foundation / SysAdmin > > -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [Call to Action] Yocto Project Bug Triage
On 05/29/2018 08:16 AM, Stephano Cetola wrote: > On 5/29/18 8:00 AM, Trevor Woerner wrote: >> Is someone working on putting together a (google?) calendar of the >> various project (OE Yocto) meetings? > Great question. > > Michael, do we have access to a Yocto Project google account? > > --S > I don't but I think this is being worked on currently. It appears new meetings are being scheduled by theyoctoproj...@gmail.com. Whoever controls that account should be able to make the calendar public. -- Michael Halstead Linux Foundation / SysAdmin -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] Pruning poky-contrib Oct 1st
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hello poky-contrib users, We are going to start regularly moving branches from poky-contrib to poky-contrib-archive that haven't been active for 1 year. The next move will happen on October 1st. Please prune any branch that should not be archived before the 1st. If you have branches that need to stay in place but are no longer receiving updates please update the list at https://wiki.yoctoproject.org/wiki/Poky_Contrib or e-mail me. For example, you might need a branch to stay where it is because it is referenced in documentation. - -- Michael Halstead Linux Foundation / SysAdmin -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEzowQ2UYmQerfiW8/amSWNbpCWpUFAlnKaMcACgkQamSWNbpC WpWw8hAAm+FTba/EK1NYz4CQJbTG08iiOPiqHm9oO8wlmAswigL6HrBJ5TDsgIVh FdkKcEpGhvHVlGfWZsUFAEUKayd4+5oCKg9zOST9/4lDc9SHbyAtf587POmVYVz2 P3r+423CJY2vkH8Xp3xl1zJAmRIUGpwWQqJu2ERcLxfjGWgQy5fhgFo7zX8vMPOa 8ONzbpF5lWO86DtAzErCeerS6ZTkC0lOzMyhARXE6XPFh+nb+AvMY5ewCPVbCRQK ilK0YfjKIGv1tJ4g4zfsa2Lbexp6lsI3lWvPGjwFYZvWXB/OKAE0iSUtuWimepDQ 8mm633tVEk5tuksCYU7CRox2xiU9oYlCV2pFp3HKBnIxkxOyhoFYYiE7PdTC8Tp5 dRpOGzyiEU38en2UlDiq+Uc26kW8GGIHnp0ku0FCAWxPI0ioPusTpV2iZm1lwGnl ydweOAyNPOo9cD5kjo19dnWjUYtxty1vjtz4F2iTobJgenmxFjDrmUmCYnNYZmQu Ayt+s5n9/kr/CXOzfCHQO+Xal9kPXI1bhKapFhk4rWg0/5hSypm5J24BT1jSTjgw amGMeZgbn3jOEBMehpPHvJ0OMXfBJfstTgD5UUCIwtc1tpbPxAbKKZz2GK/yqLeL j8ztjW8TmSfmnuBWGeDM9ObotRIYz8M+E+tsl+VHzfCmTXusPVk= =TNB2 -END PGP SIGNATURE- -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [infra] git domain name updates
On 09/25/2017 06:17 PM, akuster808 wrote: > > > On 09/25/2017 05:17 PM, Michael Halstead wrote: >> Hello, >> >> As Yocto Project continues to grow load on our git server does as >> well. We are going to make a few changes to our git infrastructure to >> allow for more growth. >> >> All read-only git operations should point at git.yoctoproject.org. For >> example poky can be cloned from the following URLs: >> >> git://git.yoctoproject.org/poky >> https://git.yoctoproject.org/git/poky >> >> If you have repositories pointed at www.yoctoproject.org, >> git.pokylinux.org, or any other domain name please update their remotes >> to git.yoctoproject.org. >> >> Read-write operations via ssh will use a new domain specifically for >> that purpose. I've added push.yoctoproject.org and ra.yoctoproject.org >> (like ra.kernel.org). >> > Read-write URLs should be updated to the new domain names. I've >> changed mine like so: >> >> >> git remote set-url origin ssh://g...@push.yoctoproject.org/poky-contrib >> >> > will this apply to the other contrib repos hosted by Yocto? This will apply to all repos hosted at git.yoctoproject.org. I used poky-contrib as the push example since it has the most users. > > Is there a policy on pruning old branches in the contrib repos? > There hasn't been a policy but we need to create one. I've checked with Richard and we will move branches to poky-contrib-archive that haven't been touched in a year. I'll send out a notice about that. > >> This is all ready to go right now. Please update your remotes. >> >> We will have to make these changes required before we can start to get >> performance benefits from them. I suggest November 1st 2017 but I need >> more feedback before we can set a cut off date. > sounds good to me. Thanks for working on this. > > - armin >> >> Thank you, >> > > -- Michael Halstead Linux Foundation / SysAdmin -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [infra] git domain name updates
On 09/26/2017 03:27 AM, Burton, Ross wrote: > On 26 September 2017 at 01:17, Michael Halstead > <mhalst...@linuxfoundation.org <mailto:mhalst...@linuxfoundation.org>> > wrote: > > This is all ready to go right now. Please update your remotes. > Read-write users: While updating your git remotes you may also need to update configuration in ~/.ssh/config or /etc/ssh/ssh_config with the new domain name. If you use several ssh keys or work behind a proxy you probably have configuration to update. grep yoctoproject ~/.ssh/config /etc/ssh/ssh_config /etc/ssh/ssh_config.d/*.conf If you see git.yoctoproject.org change it to push.yoctoproject.org. Remember to check for any build accounts you've created as well as your main account. -- Michael Halstead Linux Foundation / SysAdmin -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] [infra] git domain name updates
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hello, As Yocto Project continues to grow load on our git server does as well. We are going to make a few changes to our git infrastructure to allow for more growth. All read-only git operations should point at git.yoctoproject.org. For example poky can be cloned from the following URLs: git://git.yoctoproject.org/poky https://git.yoctoproject.org/git/poky If you have repositories pointed at www.yoctoproject.org, git.pokylinux.org, or any other domain name please update their remotes to git.yoctoproject.org. Read-write operations via ssh will use a new domain specifically for that purpose. I've added push.yoctoproject.org and ra.yoctoproject.org (like ra.kernel.org). Read-write URLs should be updated to the new domain names. I've changed mine like so: git remote set-url origin ssh://g...@push.yoctoproject.org/poky-contrib This is all ready to go right now. Please update your remotes. We will have to make these changes required before we can start to get performance benefits from them. I suggest November 1st 2017 but I need more feedback before we can set a cut off date. Thank you, - -- Michael Halstead Yocto Project / SysAdmin -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEzowQ2UYmQerfiW8/amSWNbpCWpUFAlnJnKsACgkQamSWNbpC WpVwphAAkRfTKy64rClsiB2lijbi2Z7o/NJIEbkDgbYf92aeAAJw4KQHLMxbrOS+ lZi6MtUSEGtFGdcxqOZ3RCNagfjA9peiDpcxf0A/Jnax02yQz5njHQco12n7IuYl Q92CW2wMWfqVHJ+0NZe2THb72OUd6cepjHOeNBUb4L3TFOK6NAc63zaFD24vXqq0 VAx+x3s8DPIyzttS7s3lA1IXlLS1S3jGdhLM/0G0E48QJM3Y/I3ntUJ3G02mVMYc wJ1a8E1/YTTgcL0Xwioa+EoGXeuAPmbrirlp+e9QXwBzYw/2EjNTt3stEpGCK+xK Pf7+TNGgky/OMzX9pr51jHl1XwgtZJzmumyyIDA3UewVxxvkkOwsFjICN0keWM3W GGlkOn+Sn+V7Nnw5MVchX9cexojgebgbaDuyFmlpr+nXin9YKO7ELPnOaENTQouk lq72nvlfllHDGa0yx6ZbhP/UV5E03Q0g+aDLvoYvY+HWFZGyMFP5cyumEI4H2puQ mqTjg9aWE3NExA5/gseihxjW/UvGhApfkV5OWXcxv03FmCfLIGNBKdFYJYTtC4gm WUGZbV8yyw13/F0gwPe/538BEsL+4oJxhk4AqNtGYjbb3m0XpjIxVP/Gbf7WASJi 2r3NDP8SE0ehQE79gqxQIX07+s1smCPJ3EkHvvKY/Bk8QCa2iBg= =TfzM -END PGP SIGNATURE- -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] downloads.yoctoproject.org timeouts and service interruptions
Dedicated hardware is now in place. This should resolve these issues. Please report any new timeouts in #yocto if possible. On 08/15/2017 10:27 AM, Michael Halstead wrote: > On Wednesday August 9th we upgraded the backend storage for > downloads.yoctoproject.org and related sites. The new hardware is much > faster but it is also depended on by more systems. > > August 12th connections began timing out due to contention. I'm working > on tuning to keep downloads available right now. Over the next day we > will work to provision new decided resources for these important services. > > Expect timeouts and service interruptions for the next 24 hours. > > I will update the lists or you can follow the incident at > https://status.linuxfoundation.org/incidents/hxz2f2kvbn88. > -- Michael Halstead Linux Foundation / SysAdmin signature.asc Description: OpenPGP digital signature -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] downloads.yoctoproject.org timeouts and service interruptions
On Wednesday August 9th we upgraded the backend storage for downloads.yoctoproject.org and related sites. The new hardware is much faster but it is also depended on by more systems. August 12th connections began timing out due to contention. I'm working on tuning to keep downloads available right now. Over the next day we will work to provision new decided resources for these important services. Expect timeouts and service interruptions for the next 24 hours. I will update the lists or you can follow the incident at https://status.linuxfoundation.org/incidents/hxz2f2kvbn88. -- Michael Halstead Linux Foundation / SysAdmin -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Release Candidate Build for yocto-2.3.1.rc1 now available
The RC2 e-mail should arrive shortly. It was sent the normal way, directly
by the autobuilder.
On Wed, Jul 12, 2017 at 10:03 AM, Perez Carranza, Jose <
jose.perez.carra...@intel.com> wrote:
> Hi Michael
>
> You sent the mail for rc1 and there is an rc2 available, according to RP
> rc2 is the one that will be used for QA.
>
> Regards,
> José
>
>
> -Original Message-
> From: Michael Halstead [mailto:mhalst...@linuxfoundation.org]
> Sent: Wednesday, July 12, 2017 11:38 AM
> To: pi...@toganlabs.com; Perez Carranza, Jose <
> jose.perez.carra...@intel.com>; Cruz, Libertad <libertad.c...@intel.com>;
> ota...@ossystems.com.br; Zhao, Yi (Wind River) <yi.z...@windriver.com>;
> Graydon, Tracy <tracy.gray...@intel.com>; Lock, Joshua G <
> joshua.g.l...@intel.com>; yocto@yoctoproject.org
> Subject: Release Candidate Build for yocto-2.3.1.rc1 now available
>
> A release candidate build for yocto-2.3.1.rc1 is now available at:
>
>
> https://autobuilder.yocto.io/pub/releases/yocto-2.3.1.rc1
>
>
> Please begin QA on this build as soon as possible.
>
>
> Build hash information:
> meta-intel : 16aea09d224f3ed2021623d17c3e807f4b8ff18d
> meta-qt4 : e120a2193be3982d55741fb9e51472db6ab9a5cd
> refkit : d86ed372d83a930e9fe2ef22e8a4b98a269d33e6
> meta-mingw : 4bdb99650a053f254ccd158a6d0c25c80e79f6ee
> meta-qt3 : f33b73a9563f2dfdfd0ee37b61d65d90197a456f
> meta-gplv2 : de001bd6bfcec943d274b649c62be6848cc9c3e6
> poky : c2ef32ae58737463cf19aab7446d6a30ad81754f
>
> \nThis is an automated message from\nThe Yocto Project Autobuilder\nGit:
> git://git.yoctoproject.org/yocto-autobuilder\nEmail: pi...@toganlabs.com
> " | sendmail -t in dir /home/pokybuild/yocto-autobuilder/yocto-worker/
> nightly/build
> (timeout 10 secs)
> watching logfiles {}
> argv: echo "To: yocto@yoctoproject.org
> Cc: pi...@toganlabs.com, jose.perez.carra...@intel.com,
> libertad.c...@intel.com, ota...@ossystems.com.br, yi.z...@windriver.com,
> tracy.gray...@intel.com, joshua.g.l...@intel.com
> Subject: Release Candidate Build for yocto-2.3.1.rc1 now available.
>
>
> A release candidate build for yocto-2.3.1.rc1 is now available at:
>
>
> https://autobuilder.yocto.io/pub/releases/yocto-2.3.1.rc1
>
>
> Please begin QA on this build as soon as possible.
>
>
> Build hash information:
> meta-intel : 16aea09d224f3ed2021623d17c3e807f4b8ff18d
> meta-qt4 : e120a2193be3982d55741fb9e51472db6ab9a5cd
> refkit : d86ed372d83a930e9fe2ef22e8a4b98a269d33e6
> meta-mingw : 4bdb99650a053f254ccd158a6d0c25c80e79f6ee
> meta-qt3 : f33b73a9563f2dfdfd0ee37b61d65d90197a456f
> meta-gplv2 : de001bd6bfcec943d274b649c62be6848cc9c3e6
> poky : c2ef32ae58737463cf19aab7446d6a30ad81754f
>
>
> --
> Michael Halstead
> Linux Foundation / SysAdmin
>
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] Release Candidate Build for yocto-2.3.1.rc1 now available
A release candidate build for yocto-2.3.1.rc1 is now available at:
https://autobuilder.yocto.io/pub/releases/yocto-2.3.1.rc1
Please begin QA on this build as soon as possible.
Build hash information:
meta-intel : 16aea09d224f3ed2021623d17c3e807f4b8ff18d
meta-qt4 : e120a2193be3982d55741fb9e51472db6ab9a5cd
refkit : d86ed372d83a930e9fe2ef22e8a4b98a269d33e6
meta-mingw : 4bdb99650a053f254ccd158a6d0c25c80e79f6ee
meta-qt3 : f33b73a9563f2dfdfd0ee37b61d65d90197a456f
meta-gplv2 : de001bd6bfcec943d274b649c62be6848cc9c3e6
poky : c2ef32ae58737463cf19aab7446d6a30ad81754f
\nThis is an automated message from\nThe Yocto Project Autobuilder\nGit:
git://git.yoctoproject.org/yocto-autobuilder\nEmail: pi...@toganlabs.com
" | sendmail -t
in dir /home/pokybuild/yocto-autobuilder/yocto-worker/nightly/build
(timeout 10 secs)
watching logfiles {}
argv: echo "To: yocto@yoctoproject.org
Cc: pi...@toganlabs.com, jose.perez.carra...@intel.com,
libertad.c...@intel.com, ota...@ossystems.com.br, yi.z...@windriver.com,
tracy.gray...@intel.com, joshua.g.l...@intel.com
Subject: Release Candidate Build for yocto-2.3.1.rc1 now available.
A release candidate build for yocto-2.3.1.rc1 is now available at:
https://autobuilder.yocto.io/pub/releases/yocto-2.3.1.rc1
Please begin QA on this build as soon as possible.
Build hash information:
meta-intel : 16aea09d224f3ed2021623d17c3e807f4b8ff18d
meta-qt4 : e120a2193be3982d55741fb9e51472db6ab9a5cd
refkit : d86ed372d83a930e9fe2ef22e8a4b98a269d33e6
meta-mingw : 4bdb99650a053f254ccd158a6d0c25c80e79f6ee
meta-qt3 : f33b73a9563f2dfdfd0ee37b61d65d90197a456f
meta-gplv2 : de001bd6bfcec943d274b649c62be6848cc9c3e6
poky : c2ef32ae58737463cf19aab7446d6a30ad81754f
--
Michael Halstead
Linux Foundation / SysAdmin
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] [infra] Intermittent outages for Yocto Project services starting soon
Maintenance of our ISP's connectivity at the Internet Exchange at Portland, will cause service interruptions for some users. Most services including git, mail, autobuilder, wiki, and website will be affected. Planned Start: May 18, 2017 12:00AM PDT / 07:00 UTC Expected End: May 18, 2017 6:00AM PDT / 13:00 UTC Apologies for the short notice. -- Michael Halstead Linux Foundation / SysAdmin -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [bitbake-devel] [oe] Infra Full Stop 12/26-12/29
On 12/25/2016 11:43 PM, Martin Jansa wrote: > On Sun, Dec 25, 2016 at 08:06:50PM -0800, Michael Halstead wrote: >> In preparation for the scheduled maintenance I have moved >> git.openembedded.org to a new server temporarily. E-mail and Patchwork >> hooks may not work correctly. All other git operations as well as >> listings at http://git.openembedded.org/ should continue working. >> >> If you have a git remote pointed directly at openembedded.org it will >> fail. Please update your remote to point at git.openembedded.org and try >> again. > It doesn't seem to be working here: > > error: Could not fetch origin > fatal: unable to connect to git.openembedded.org: > git.openembedded.org[0: 104.236.212.160]: errno=Connection refused > git.openembedded.org[1: 2604:a880:800:10::2127:2001]: errno=Network is > unreachable > > But that's OK for me, I was prepared to do some holiday celebrations > thanks to planned downtime :). And I have some local mirrors in case > I got tired of celebrations before the downtime is over. This is fixed now. I fulled tested push access but not normal anonymous clones. Sorry about that. > >> Other services that will stay up during the maintenance are: >> >> Layerindex https://layers.openembedded.org/ >> Mailman http://lists.openembedded.org/ >> Patchwork https://patchwork.openembedded.org/ >> >> I'd like the share my appreciation for the OpenEmbedded volunteer >> sysadmins who are taking time away from their holiday celebrations to >> make this downtime as convenient for the rest of us as possible. >> >> >> On 12/22/2016 09:19 AM, Tom King wrote: >>> Schedule is 06:00UTC 27DEC16 for the full stop. Things will start coming >>> back (estimated) about 48hrs later. >>> >>> Tom >>> >>> On Tue, Dec 20, 2016 at 11:16 AM, Khem Raj <raj.k...@gmail.com> wrote: >>> >>>>> On Dec 20, 2016, at 10:50 AM, Tom King <ka6...@gmail.com> wrote: >>>>> >>>>> Hi All, >>>>> >>>>> We have been looking for a time when we could do a full stop of the infra >>>>> to upgrade some bits and clear out some faults. >>>>> >>>>> This will involve shutting down the main machine that we use for *most* >>>> of >>>>> the OE infra. >>>>> >>>>> Our goal is to put up a backup git master but other services such as: >>>> wiki, >>>>> patches, etc will be offline for some or all of that period. >>>>> >>>>> We have delayed doing this much needed maintenance to try to work around >>>>> Yocto and OE release schedules and it is necessary that we take this time >>>>> to do the work. >>>>> >>>> I guess, you need to come up with a tentative down-time schedule. >>>> >>>>> Tom >>>>> (for the OE Infra Team) >>>>> -- >>>>> ___ >>>>> Openembedded-devel mailing list >>>>> openembedded-de...@lists.openembedded.org >>>>> http://lists.openembedded.org/mailman/listinfo/openembedded-devel >>>> -- >>>> ___ >>>> Openembedded-devel mailing list >>>> openembedded-de...@lists.openembedded.org >>>> http://lists.openembedded.org/mailman/listinfo/openembedded-devel >>>> >> -- >> Michael Halstead >> Linux Foundation / SysAdmin >> >> > > > >> -- >> ___ >> bitbake-devel mailing list >> bitbake-de...@lists.openembedded.org >> http://lists.openembedded.org/mailman/listinfo/bitbake-devel > -- Michael Halstead Linux Foundation / SysAdmin -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [oe] Infra Full Stop 12/26-12/29
In preparation for the scheduled maintenance I have moved git.openembedded.org to a new server temporarily. E-mail and Patchwork hooks may not work correctly. All other git operations as well as listings at http://git.openembedded.org/ should continue working. If you have a git remote pointed directly at openembedded.org it will fail. Please update your remote to point at git.openembedded.org and try again. Other services that will stay up during the maintenance are: Layerindex https://layers.openembedded.org/ Mailman http://lists.openembedded.org/ Patchwork https://patchwork.openembedded.org/ I'd like the share my appreciation for the OpenEmbedded volunteer sysadmins who are taking time away from their holiday celebrations to make this downtime as convenient for the rest of us as possible. On 12/22/2016 09:19 AM, Tom King wrote: > Schedule is 06:00UTC 27DEC16 for the full stop. Things will start coming > back (estimated) about 48hrs later. > > Tom > > On Tue, Dec 20, 2016 at 11:16 AM, Khem Raj <raj.k...@gmail.com> wrote: > >>> On Dec 20, 2016, at 10:50 AM, Tom King <ka6...@gmail.com> wrote: >>> >>> Hi All, >>> >>> We have been looking for a time when we could do a full stop of the infra >>> to upgrade some bits and clear out some faults. >>> >>> This will involve shutting down the main machine that we use for *most* >> of >>> the OE infra. >>> >>> Our goal is to put up a backup git master but other services such as: >> wiki, >>> patches, etc will be offline for some or all of that period. >>> >>> We have delayed doing this much needed maintenance to try to work around >>> Yocto and OE release schedules and it is necessary that we take this time >>> to do the work. >>> >> I guess, you need to come up with a tentative down-time schedule. >> >>> Tom >>> (for the OE Infra Team) >>> -- >>> ___ >>> Openembedded-devel mailing list >>> openembedded-de...@lists.openembedded.org >>> http://lists.openembedded.org/mailman/listinfo/openembedded-devel >> -- >> ___ >> Openembedded-devel mailing list >> openembedded-de...@lists.openembedded.org >> http://lists.openembedded.org/mailman/listinfo/openembedded-devel >> -- Michael Halstead Linux Foundation / SysAdmin signature.asc Description: OpenPGP digital signature -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] Patchwork upgrade tonight
After 2 weeks of testing and some performance tuning we are going to proceed with the Patchwork upgrade. Data entered into the current version in the next few hours may need to be re-entered after the upgrade. All features of the current Patchwork install work in the new version. So while there are still issues surrounding detection of patch series there are no known regressions. Series detection can be addressed after the upgrade. The rollback plan can be executed very quickly if needed. Please reach out if you have concerns. -- Michael Halstead Linux Foundation / SysAdmin -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] Patchwork users: Help test new version
Hello, OpenEmbedded is nearly ready to upgrade to a new version of Patchwork. The new version offers several new features that will allow OpenEmbedded to improve developer workflow and automated checks on incoming patches. If you are a Patchwork user please visit https://patchwork-next.openembedded.org/ and take a look. If you find anything amiss please e-mail me directly and include patchwork in the subject line. Thank you for your help upgrading this important system! -- Michael Halstead Linux Foundation / SysAdmin -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] 1.7.1 ADT-installer errors
The sync is complete and broken symlinks are restored. I've also taken the opportunity to clean up absolute symlinks at the source so this issue cannot happen again even if the chroots aren't set properly. Michael Halstead Yocto Project / SysAdmin On 04/15/2015 05:20 AM, Michael Halstead wrote: A change in the rsync configuration caused all symlinks to break during the most recent sync to the mirror front ends. The error has been corrected and the adtrepo links will be restored from the source shortly. Michael Halstead Yocto Project / SysAdmin On 04/15/2015 04:50 AM, Flanagan, Elizabeth wrote: On 15 April 2015 at 04:33, Yi Zhao yi.z...@windriver.com wrote: Hi, I can confirm it is an issue. I got a 404 not found error when I tried to download the core-image-sato-sdk-qemux86.tar.bz2 from http://adtrepo.yoctoproject.org/1.7.1/rootfs/qemux86/. Looks like the symbolic link is broken. Beth, Would you please have a look at this and fix it ? Sure, it'll take me a bit to get access to the infrastructure but I'll get to it when I have access. -b Thanks, Yi 在 2015年04月14日 16:24, heli Atck 写道: Hi, I'm new to Yocto (and embedded Linux for that matter). I was following the ADT manual to get started with application development. I tried using the ADT-installer script, but ran into some errors. Here's the relevant part of the installer log file: Creating directory /home/spe/test-yocto/qemux86... Extracting rootfs: core-image-sato-sdk-qemux86.tar.bz2, using pseudo... tar (child): ./download_image/core-image-sato-sdk-qemux86.tar.bz2: Cannot open: No such file or directory tar (child): Error is not recoverable: exiting now tar: Child returned status 2 tar: Error is not recoverable: exiting now There are no files in my /download_image directory so I guess they have not been properly retrieved from the repository. I looked at the repository for 1.7.1 at http://adtrepo.yoctoproject.org/1.7.1/rootfs/qemux86/ and some of the relevant files seem to be missing. Or did I mis a step somewhere? Sammy signature.asc Description: OpenPGP digital signature -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] adtrepo clean-up
After examining download logs it appears we could safely delete versions 1.0-1.3.x from http://adtrepo.yoctoproject.org/. They are only accessed by web crawlers at this point. Removing them would make room for more releases and save on hardware budget. Are there any reasons to keep versions 1.0-1.3.x in http://adtrepo.yoctoproject.org/? -- Michael Halstead Yocto Project / SysAdmin -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] http://adtrepo.yoctoproject.org Not Found
Just an update. This was also posted to the yocto-infrastructure list and handled there. ADT repos are all online again. Michael Halstead Yocto Project / SysAdmin On 02/03/2015 05:15 AM, Gabo wrote: Hallo, it seems the server http://adtrepo.yoctoproject.org does not respond correcty (Page Not Found 404) this is the output of adt-installer script --2015-02-03 10:12:11-- http://adtrepo.yoctoproject.org/1.6.1 Resolving adtrepo.yoctoproject.org http://adtrepo.yoctoproject.org (adtrepo.yoctoproject.org http://adtrepo.yoctoproject.org)... 140.211.169.59 Connecting to adtrepo.yoctoproject.org http://adtrepo.yoctoproject.org (adtrepo.yoctoproject.org http://adtrepo.yoctoproject.org)|140.211.169.59|:80... connected. HTTP request sent, awaiting response... 404 Not Found 2015-02-03 10:12:11 ERROR 404: Not Found. Is there any problem? thank you Gabriele -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] can't pull any sources anymore
On 01/09/2015 08:08 AM, Saul Wold wrote: On 01/09/2015 06:10 AM, matthias.he...@atlas-elektronik.com wrote: Hi, I'm not able to pull any sources for a little time now. As test I re-tried an already working setup by again following some tutorial and trying to setup a fresh repo. The repo init works but the sync fails. I should mention that due to network limitations I replace git:// urls with https:// . Is it possible that this doesn't work anymore (I mean it is replaced but maybe the online repos don't support it anymore seamlessly)? Mat, Please note that the git:// and http:// URLs have a different structure. For example, git://git.yoctoproject.org/poky http://git.yoctoproject.org/git/poky https://git.yoctoproject.org/git/poky You can find these URLs at the bottom of any project page in cgit http://git.yoctoproject.org/cgit/cgit.cgi/poky/ Please try running git clone https://git.yoctoproject.org/git/poky; and if it fails send me the output. Thank you, Michael Halstead Yocto Project / SysAdmin Can you be more specific, are you talking about the git repos at git.yoctoproject.org or some other git source? You say a repo init works, does that mean an initial clone or ? What commands are you running? I think a little more information is needed here. Sau! Thanks Mat signature.asc Description: OpenPGP digital signature -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto-announce] [ANNOUNCEMENT] Yocto Project 1.7 (dizzy 12.0.0) Released
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hello, The latest release of the Yocto Project 1.7 (dizzy-12.0.0) is now available for download at: http://downloads.yoctoproject.org/releases/yocto/yocto-1.7/poky-dizzy-12.0.0.tar.bz2 http://mirrors.kernel.org/yocto/yocto/yocto-1.7/poky-dizzy-12.0.0.tar.bz2 A gpg signed version of these release notes is available at: http://downloads.yoctoproject.org/releases/yocto/yocto-1.7/RELEASENOTES We have rotated our release signing key with this release. The new key has been signed by the previous key and the old key has been retired. The new key is at http://downloads.yoctoproject.org/releases/yocto/keys/yocto-release-key.asc Full pass test report is available at: https://wiki.yoctoproject.org/wiki/WW43_-_2014-10-18_-_Full_Pass_-_1.7_M4.rc5 Thanks go out to everyone for all their hard work during this release! Sincerely, Michael Halstead Yocto Systems Administrator mich...@yoctoproject.org - - yocto-1.7 Errata - - Release Name: poky-dizzy-12.0.0 Branch: dizzy Tag: dizzy-12.0.0 Hash: 9aff3a4ec058a1a1149d026ebedcc6251089fffb md5: 5d04120e09bbc0933a3eb53c94cd8daa Download Locations: http://downloads.yoctoproject.org/releases/yocto/yocto-1.7/poky-dizzy-12.0.0.tar.bz2 http://mirrors.kernel.org/yocto/yocto/yocto-1.7/poky-dizzy-12.0.0.tar.bz2 Release Name: eclipse-poky-juno-dizzy-12.0.0 Branch: dizzy Tag: dizzy-12.0.0 Hash: 26bfc407781aa185f244a47ba63120343cee4a37 md5: f147c7938731f616fdcac49c8f1dfb0c Download Locations: http://downloads.yoctoproject.org/releases/yocto/yocto-1.7/eclipse-poky-juno-dizzy-12.0.0.tar.bz2 http://mirrors.kernel.org/yocto/yocto/yocto-1.7/eclipse-poky-juno-dizzy-12.0.0.tar.bz2 Release Name: eclipse-poky-kepler-dizzy-12.0.0 Branch: dizzy Tag: dizzy-12.0.0 Hash: 4a167fd662262ebdaa3cf0d332ac0debb52d7904 md5: 8f26189fd223a1025fa319687a15bc28 Download Locations: http://downloads.yoctoproject.org/releases/yocto/yocto-1.7/eclipse-poky-kepler-dizzy-12.0.0.tar.bz2 http://mirrors.kernel.org/yocto/yocto/yocto-1.7/eclipse-poky-kepler-dizzy-12.0.0.tar.bz2 Release Name: meta-qt3-dizzy-12.0.0 Branch: dizzy Tag: dizzy-12.0.0 Hash: 3016129d90b7ac8517a5227d819f10ad417b5b45 md5: afbfbb2c4a7c7a648071fa503d41ffe6 Download Locations: http://downloads.yoctoproject.org/releases/yocto/yocto-1.7/meta-qt3-dizzy-12.0.0.tar.bz2 http://mirrors.kernel.org/yocto/yocto/yocto-1.7/meta-qt3-dizzy-12.0.0.tar.bz2 - New Features - * gcc 4.9 * glibc (version 2.20) is now used in place of eglibc * Significant enhancement of systemd support: - Upgraded systemd to 216 - Other packages that overlap in functionality are now masked out when systemd is used - Added support for using systemd with uclibc - Added support for read-only rootfs when using systemd - Added os-release recipe to deploy /etc/os-release - Added systemd service files to acpid, bind, cronie, cups, dhcp, portmap, ppp, tcf-agent (some from meta-systemd) * Core support for musl libc (requires additional meta-musl support layer) * Improvements to BitBake termination, error handling and responsiveness * wic image creator 2.0 - Major code cleanup - Added bootimg-partition plugin - Added sdimage-bootpart kickstart file for SD card support - Added vfat support - Added squashfs partition support - Added gummiboot support to bootimg-efi - Added support to find plugins and kickstart (.wks) files in all configured layers * Cleanup of bashisms and addition of missing bash/perl dependencies (with split packages where possible) * Added bootchart2 and cleaned up bootchart support * Additional recipes: i2c-tools, patchelf, serf, nettle, liberror-perl, libxshmfence, dri3proto, libunwind, pinentry * RPM4 support (in addition to RPM5) * Added support for locked shared state * Extended hardware runtime testing support - Added base class for hardware runtime testing - Added support for runtime testing on edgerouter, beaglebone and generic GRUB-based machines - Added test-remote-image script to download an image and automatically test it on a specified machine * Added runtime test for error messages in kernel and Xorg logs * Added runtime test for running installed ptests * Added runtime testing for SDKs * Added ptest support to gdbm, openssh, openssl, oprofile, pango, sed * Package QA check improvements: - Added build-deps QA check - Added file-rdeps QA check - Show QA check name in warning / error messages - Overlapping files deployed into the sysroot will now trigger an error instead of a warning * autotools class now uses a separate build directory by default (B != S) * mkefidisk: added gummiboot support * Added devpyshell interactive python shell * package_ipk: Support hierarchical package feeds * package_deb: Added support for multilib * bitbake: added bb.utils.contains and bb.utils.contains_any, and replaced instances of base_contains * Add buildstats-summary class to provide sstate re-use summary
[yocto] [ANNOUNCEMENT] Yocto Project 1.7 (dizzy 12.0.0) Released
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hello, The latest release of the Yocto Project 1.7 (dizzy-12.0.0) is now available for download at: http://downloads.yoctoproject.org/releases/yocto/yocto-1.7/poky-dizzy-12.0.0.tar.bz2 http://mirrors.kernel.org/yocto/yocto/yocto-1.7/poky-dizzy-12.0.0.tar.bz2 A gpg signed version of these release notes is available at: http://downloads.yoctoproject.org/releases/yocto/yocto-1.7/RELEASENOTES We have rotated our release signing key with this release. The new key has been signed by the previous key and the old key has been retired. The new key is at http://downloads.yoctoproject.org/releases/yocto/keys/yocto-release-key.asc Full pass test report is available at: https://wiki.yoctoproject.org/wiki/WW43_-_2014-10-18_-_Full_Pass_-_1.7_M4.rc5 Thanks go out to everyone for all their hard work during this release! Sincerely, Michael Halstead Yocto Systems Administrator mich...@yoctoproject.org - - yocto-1.7 Errata - - Release Name: poky-dizzy-12.0.0 Branch: dizzy Tag: dizzy-12.0.0 Hash: 9aff3a4ec058a1a1149d026ebedcc6251089fffb md5: 5d04120e09bbc0933a3eb53c94cd8daa Download Locations: http://downloads.yoctoproject.org/releases/yocto/yocto-1.7/poky-dizzy-12.0.0.tar.bz2 http://mirrors.kernel.org/yocto/yocto/yocto-1.7/poky-dizzy-12.0.0.tar.bz2 Release Name: eclipse-poky-juno-dizzy-12.0.0 Branch: dizzy Tag: dizzy-12.0.0 Hash: 26bfc407781aa185f244a47ba63120343cee4a37 md5: f147c7938731f616fdcac49c8f1dfb0c Download Locations: http://downloads.yoctoproject.org/releases/yocto/yocto-1.7/eclipse-poky-juno-dizzy-12.0.0.tar.bz2 http://mirrors.kernel.org/yocto/yocto/yocto-1.7/eclipse-poky-juno-dizzy-12.0.0.tar.bz2 Release Name: eclipse-poky-kepler-dizzy-12.0.0 Branch: dizzy Tag: dizzy-12.0.0 Hash: 4a167fd662262ebdaa3cf0d332ac0debb52d7904 md5: 8f26189fd223a1025fa319687a15bc28 Download Locations: http://downloads.yoctoproject.org/releases/yocto/yocto-1.7/eclipse-poky-kepler-dizzy-12.0.0.tar.bz2 http://mirrors.kernel.org/yocto/yocto/yocto-1.7/eclipse-poky-kepler-dizzy-12.0.0.tar.bz2 Release Name: meta-qt3-dizzy-12.0.0 Branch: dizzy Tag: dizzy-12.0.0 Hash: 3016129d90b7ac8517a5227d819f10ad417b5b45 md5: afbfbb2c4a7c7a648071fa503d41ffe6 Download Locations: http://downloads.yoctoproject.org/releases/yocto/yocto-1.7/meta-qt3-dizzy-12.0.0.tar.bz2 http://mirrors.kernel.org/yocto/yocto/yocto-1.7/meta-qt3-dizzy-12.0.0.tar.bz2 - New Features - * gcc 4.9 * glibc (version 2.20) is now used in place of eglibc * Significant enhancement of systemd support: - Upgraded systemd to 216 - Other packages that overlap in functionality are now masked out when systemd is used - Added support for using systemd with uclibc - Added support for read-only rootfs when using systemd - Added os-release recipe to deploy /etc/os-release - Added systemd service files to acpid, bind, cronie, cups, dhcp, portmap, ppp, tcf-agent (some from meta-systemd) * Core support for musl libc (requires additional meta-musl support layer) * Improvements to BitBake termination, error handling and responsiveness * wic image creator 2.0 - Major code cleanup - Added bootimg-partition plugin - Added sdimage-bootpart kickstart file for SD card support - Added vfat support - Added squashfs partition support - Added gummiboot support to bootimg-efi - Added support to find plugins and kickstart (.wks) files in all configured layers * Cleanup of bashisms and addition of missing bash/perl dependencies (with split packages where possible) * Added bootchart2 and cleaned up bootchart support * Additional recipes: i2c-tools, patchelf, serf, nettle, liberror-perl, libxshmfence, dri3proto, libunwind, pinentry * RPM4 support (in addition to RPM5) * Added support for locked shared state * Extended hardware runtime testing support - Added base class for hardware runtime testing - Added support for runtime testing on edgerouter, beaglebone and generic GRUB-based machines - Added test-remote-image script to download an image and automatically test it on a specified machine * Added runtime test for error messages in kernel and Xorg logs * Added runtime test for running installed ptests * Added runtime testing for SDKs * Added ptest support to gdbm, openssh, openssl, oprofile, pango, sed * Package QA check improvements: - Added build-deps QA check - Added file-rdeps QA check - Show QA check name in warning / error messages - Overlapping files deployed into the sysroot will now trigger an error instead of a warning * autotools class now uses a separate build directory by default (B != S) * mkefidisk: added gummiboot support * Added devpyshell interactive python shell * package_ipk: Support hierarchical package feeds * package_deb: Added support for multilib * bitbake: added bb.utils.contains and bb.utils.contains_any, and replaced instances of base_contains * Add buildstats-summary class to provide sstate re-use summary
[yocto] Error while reverting changes to Bugzilla database [June 27th 17:15 UTC - June 29th 15:00 UTC]
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Summary: If you entered data into bugzilla.yoctoproject.org during the last 3 days, please double check your entries are correct. Data entered into bugzilla.yoctoproject.org after June 27th 17:15 UTC and before June 29th 15:00 UTC was lost from the production database. One lost bug was re-entered by hand. Details: While restoring Testopia data from a test plan that was deleted last Thursday I made a mistake regarding the format of the database backup files I was using. The bugzilla database was reverted to its state as of June 26th 08:30 UTC. It continued in this state until June 29th 15:00 UTC when I restored the database as it was on June 27th 17:15 UTC. The only changes made during this odd state were to temporary bug id 6483 which I have recreated as https://bugzilla.yoctoproject.org/show_bug.cgi?id=6488. I believe no bug data was lost. Daily stats data for June 27th were lost. Weekly stats are not affected. Testopia data remains in the June 26th 08:30 UTC state. - -- Michael Halstead Yocto Project / SysAdmin -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.22 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEcBAEBAgAGBQJTsD3IAAoJEH9hAclg9EfIf6oH/2cXZzKdyX2C/RzHjBo+u5be PAiSJ84M97yeqx17bgz52ZrNUcZanoipTfgAs0Gh8u3J5e1XDMEORTYxU9uuS7EH lsjg9XXKgSGxAe2xXuxoQZ6nk7bH2p9b2aMCj9r0HST3fpLiaBurSO2AmSRRFc3v c9MMyIEK0gQ/Odct7/5zf5Iigx5BTZoWlotmKkK5ONOzYe4qwa+izmxHtNbCppos AmlrMgKAI6Sw4m0xxqmcSZqruqFX5JnfeNUuCr+jXZrzdmVCeZmv7+wS3uRFwJ8y /e9VDwaY88ge/GQJHdpylLEZ1AQMlEpkalaEZZeWr5ISO/zv0h6m5GUDar+UCI0= =2DIT -END PGP SIGNATURE- -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [meta-mono] Git push fails. No space left
Thanks for the heads up Alex! I've added 1.8TB of extra space so we should be set for awhile. Sorry that you weren't able to push. I've also fixed the obvious style problems with the headers on the markdown the meta-mono /about page. Please tell me if you have any other style suggestions. Michael Halstead Yocto Project / SysAdmin On 05/18/2014 01:48 AM, Alex J Lennon wrote: Hi, I'm trying to push a commit to meta-mono and it's failing due to lack of space, it says, Counting objects: 12, done. Delta compression using up to 2 threads. Compressing objects: 100% (5/5), done. Writing objects: 100% (5/5), 477 bytes | 0 bytes/s, done. Total 5 (delta 4), reused 0 (delta 0) error: file write error (No space left on device) fatal: unable to write sha1 file error: unpack failed: unpack-objects abnormal exit To g...@git.yoctoproject.org:meta-mono ! [remote rejected] master - master (n/a (unpacker error)) error: failed to push some refs to 'g...@git.yoctoproject.org:meta-mono' Cheers, Alex smime.p7s Description: S/MIME Cryptographic Signature -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Ni, please add me to your LinkedIn network
I've made an effort to ban any posts from Linkedin from ever reaching the lists using sender filters. Hopefully we won't see any messages like this again. Michael Halstead Yocto Project / SysAdmin On 05/18/2014 08:41 PM, Ridish R A via LinkedIn wrote: LinkedIn http://www.linkedin.com/e/nd2fjz-hvd883pn-1o/hom/?hs=falsetok=3dVAq0GbBZa6g1 http://www.linkedin.com/e/nd2fjz-hvd883pn-1o/rso/40028291/WC4Q/name/125977031_I592211285_125/eml-comm_invm-b-photo-newinvite/?hs=falsetok=0Z7J5eLtxZa6g1 Hi Ni, I'd like to connect with you on LinkedIn. Ridish R A http://www.linkedin.com/e/nd2fjz-hvd883pn-1o/rso/40028291/WC4Q/name/125977031_I592211285_125/eml-comm_invm-b-name-newinvite/?hs=falsetok=0q1OXmboZZa6g1 Senior Design Engineer at GE Heathcare Accept http://www.linkedin.com/e/nd2fjz-hvd883pn-1o/vGbzErNZNH9pQ6uemd-zK7w298WpQgsb6vy/blk/I592211285_125/6lQqnpKqntBryRQs6lzoS4JoyRJtCVFnSRJrScJr6RBfnhv9ClRsDgZp6lQs6lzoQ5AomZIpn8_dj8NnPkUcz4Ncz8VdkALgllGqRpBh5ALczwPdzwMczgQej4LrCBxbOYWrSlI/eml-comm_invm-b-accept-newinvite/?hs=falsetok=2VMPjIOh9Za6g1 View Profile http://www.linkedin.com/e/nd2fjz-hvd883pn-1o/rso/40028291/WC4Q/name/125977031_I592211285_125/eml-comm_invm-b-profile-newinvite/?hs=falsetok=2P7B9OFgRZa6g1 You are receiving Invitation emails. Unsubscribe https://www.linkedin.com/e/nd2fjz-hvd883pn-1o/vGbzErNZNH9pQ6uemd-zK7w298WpQgsb6vy/eus/AQGkymXCjd331gAAAUYSklDScGZpGE0Ek63dRBQzpb3Ud0lNh8rQ_3Tj4vsIctqf6DEqr03_eQO-9bu8LDg/nd2fjz-hvd883pn-1o/eml-comm_invm-f-unsub-inv28/?hs=falsetok=2sESB5P_hZa6g1. This email was intended for Ni Qingliang (Software Engineer at Insigma). Learn why we included this http://www.linkedin.com/e/nd2fjz-hvd883pn-1o/plh/http%3A%2F%2Flinkedin%2Ecusthelp%2Ecom%2Fapp%2Fanswers%2Fdetail%2Fa_id%2F4788/2t30/?hs=falsetok=13gOWofnxZa6g1. © 2014, LinkedIn Corporation. 2029 Stierlin Ct. Mountain View, CA 94043, USA smime.p7s Description: S/MIME Cryptographic Signature -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Git fetch with user/pass in a recipe
On 04/16/2014 02:15 PM, Ronaldo Nunez wrote: Hi all! I'm trying to create a custom recipe to a proprietary software from my company. The code should be fetched from a git server, with username and password authentication through a http connection (port 8080). From the terminal I use the following command line to clone the project: $ git clone http://username:pass@server:8080/project.git well in the bitbake recipe, I tried the following in SRC_URI variable, with no success: SRC_URI = git://username:pass@server:8080/project.git;protocol=http I also tried: SRC_URI = git://server:8080/project.git;protocol=http;user=username It isn't mentioned at http://www.yoctoproject.org/docs/1.6/bitbake-user-manual/bitbake-user-manual.html#git-fetcher but looking at http://git.yoctoproject.org/cgit/cgit.cgi/poky/tree/bitbake/lib/bb/fetch2/git.py?h=dora it seems that including the password as part of the user parameter should work. For example, SRC_URI = git://server:8080/project.git;protocol=http;user=username:password Michael Halstead Yocto Project / Sys Admin Again, with no success. Well, any help is welcome. Thanks in advance. -- Ronaldo Nunez -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] openssl and heartbleed
On 04/14/2014 07:41 AM, Martin Jansa wrote: On Mon, Apr 14, 2014 at 02:37:52PM +, Richard Schmitt wrote: Does the Yocto project plan to have some response to the heartbleed exploit in openssl in the near term? Has this already been addressed? It was already addressed for master, daisy, dora and dylan. It's a separate issue but as far as the yoctoproject.org infrastructure is concerned our primary SSL termination server runs OpenSSL 0.9.8k and was not vulnerable to heartbleed. Other servers were not publicly accessible and were patched quickly after the announcement. On the build hosts the only running service linked linked against OpenSSL was NTP. We discussed this on the https://www.yoctoproject.org/tools-resources/community/weekly-technical-call the day after heartbleed was announced. Michael Halstead Yocto Project / Sys Admin -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Slightly OT: Administrivia (add -- to footers)
On 03/07/2014 02:46 PM, Khem Raj wrote: On Fri, Mar 7, 2014 at 9:55 AM, Ben Kamen b...@benjammin.net wrote: If I could make a small suggestion for the Yocto list owners. I also run MailMan and have set all the footers to be preceded by the -- (dash dash space). For the mailers that understand it (like Thunderbird), everything past the -- is excluded in replies. This would cut down a lot on needed trim of appended footers on the list. I think its a very good suggestion. I am sure Michael H would be interested. Good idea. I've prepended '-- \r\n' to the footers of all Yocto Project and OE lists. Michael Halstead Yocto Project / Sys Admin Just an item for the suggestion box. Cheers, -Ben ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto smime.p7s Description: S/MIME Cryptographic Signature -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Git clone over http broken on git.yoctoproject.org
On 11/25/2013 01:32 PM, michael_e_br...@dell.com wrote: Several repositories have broken git pulls over http on git.yoctoproject.org. Working: $ git clone --mirror http://git.yoctoproject.org/git/yocto-kernel-tools Initialized empty Git repository in /home/michael_e_brown/f10/sources/f/yocto-kernel-tools.git/ remote: Counting objects: 1067, done. remote: Compressing objects: 100% (462/462), done. remote: Total 1067 (delta 711), reused 958 (delta 603) Receiving objects: 100% (1067/1067), 273.41 KiB | 251 KiB/s, done. Resolving deltas: 100% (711/711), done. Broken: $ git clone --mirror http://git.yoctoproject.org/git/linux-yocto-3.10 Initialized empty Git repository in /home/michael_e_brown/f10/sources/f/linux-yocto-3.10.git/ error: RPC failed; result=52, HTTP code = 100 Failing with an HTTP continue code is sort of odd. I wonder if you are going through a proxy which could be causing this issue only for larger repos like the kernels. I think the content length header might be wrong or undefined for large objects at the moment which could give certain proxy software trouble. I've tried to correct those headers. Can you test again? I tested with git version 1.7.9.5 and no proxy and was able to clone all the kernels. Michael Halstead Yocto Project / System Administrator All of the kernel pulls appear to be broken in the same way (3.10, 3.8, etc) URLs taken directly from the cgit HTTP url listed. -- Michael ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto smime.p7s Description: S/MIME Cryptographic Signature ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] RFC Autobuilder Naming
On 11/25/2013 07:01 AM, Paul Eggleton wrote: Hi Michael, On Friday 22 November 2013 15:43:58 Michael Halstead wrote: Currently all builders are simply named ab00-ab13 based on when we acquired them. The name doesn't change except for ab01 which has been reused on new hardware. As we increase the number of builders and make the build process more flexible this becomes inconvenient. I'd like to switch to embedding useful information in the name. Going forward as I refresh builders I'd like to name them with their distro and location. For example at OSL: fedora19.osl.yoctoproject.org fedora20.osl.yoctoproject.org opensuse131.osl.yoctoproject.org ubuntu1310.osl.yoctoproject.org etc. And if we added a build clusters in the EasyStreet datacenter in Portland: centos64.pdx.yoctoproject.org debian7.pdx.yoctoproject.org etc. This allows for additional build clusters to be added and makes the distro clear to anyone viewing the logs. The current available build slaves can be found on the relevant cluster's buildbot interface (http://autobuilder.yoctoproject.org/main/buildslaves) so as names change there is an easy place to look them up. Comments? I guess this works fine until you want to have two builders with the same distro. Maybe we plan not to do that anymore...? I've been asked to run many different distros in order to find distro specific incompatibilities and bugs. So ideally we wouldn't have two builders running the same distro and version in the same location. Sometimes when refreshing all of the builders at once we will install the same software on all of them to speed up the process. They were all openSUSE for awhile 2 years ago and they are all Fedora at the moment. In these cases, should they arise again, I would append a letter to distinguish the hostname. fedora20.osl.yoctoproject.org fedora20-a.osl.yoctoproject.org fedora20-b.osl.yoctoproject.org fedora20-c.osl.yoctoproject.org Cheers, Paul smime.p7s Description: S/MIME Cryptographic Signature ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] RFC Autobuilder Naming
Currently all builders are simply named ab00-ab13 based on when we acquired them. The name doesn't change except for ab01 which has been reused on new hardware. As we increase the number of builders and make the build process more flexible this becomes inconvenient. I'd like to switch to embedding useful information in the name. Going forward as I refresh builders I'd like to name them with their distro and location. For example at OSL: fedora19.osl.yoctoproject.org fedora20.osl.yoctoproject.org opensuse131.osl.yoctoproject.org ubuntu1310.osl.yoctoproject.org etc. And if we added a build clusters in the EasyStreet datacenter in Portland: centos64.pdx.yoctoproject.org debian7.pdx.yoctoproject.org etc. This allows for additional build clusters to be added and makes the distro clear to anyone viewing the logs. The current available build slaves can be found on the relevant cluster's buildbot interface (http://autobuilder.yoctoproject.org/main/buildslaves) so as names change there is an easy place to look them up. Comments? -- Michael Halstead Yocto Project / System Administrator smime.p7s Description: S/MIME Cryptographic Signature ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Yocto Project 1.5_M2.rc1 build status
Thank you. The final steps of http://autobuilder.yoctoproject.org/pub/nightly/20130703-3/ were blocked and never completed so there may be other things missing as well. We probably need to do another build before releasing but it will hopefully be from the same commit as well. Michael Halstead Yocto Project / Sys Admin On 07/05/2013 01:05 AM, Georgescu, Alexandru C wrote: Hi Michael, The adt-installer is missing from the http://autobuilder.yoctoproject.org/pub/nightly/20130703-3/ build. But since it is using the same commit for as http://autobuilder.yoctoproject.org/pub/nightly/20130703-2 build, we will use the one there instead for testing. Regards, *--* *Alexandru Georgescu* *From:*Michael Halstead [mailto:mhalst...@linuxfoundation.org] *On Behalf Of *Michael Halstead *Sent:* Thursday, July 04, 2013 03:36 *To:* yocto@yoctoproject.org *Subject:* Re: Yocto Project 1.5_M2.rc1 build status Adidtional autobuilder configuration errors were corrected and a third spin of 1.5_M2.rc1 started. Please find the build at the new location: http://autobuilder.yoctoproject.org/pub/nightly/20130703-3 poky eaa5df34af42b6a37f6506847d0f3ef6ba0d298a https://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=eaa5df34af42b6a37f6506847d0f3ef6ba0d298a meta-fsl-arm daf582c93a7283fb0af3b25fe2ada48f4c9985c4 https://git.yoctoproject.org/cgit/cgit.cgi/meta-fsl-arm/commit/?id=daf582c93a7283fb0af3b25fe2ada48f4c9985c4 meta-fsl-ppc a2bcb25c53f935ae9a423c57ca5e2f7a2f7b1a69 (Changed since last build) meta-intel e0d6134ed2e2687ff9f2ee77701666447842bf33 https://git.yoctoproject.org/cgit/cgit.cgi/meta-intel/commit/?id=e0d6134ed2e2687ff9f2ee77701666447842bf33 meta-minnow286a72ba3f5e29432be1dd77127de5bdc2d988c3 https://git.yoctoproject.org/cgit/cgit.cgi/meta-minnow/commit/?id=286a72ba3f5e29432be1dd77127de5bdc2d988c3 meta-qt3 b73552fb998fd30a01dbee5a172e432a16078222 https://git.yoctoproject.org/cgit/cgit.cgi/meta-qt3/commit/?id=b73552fb998fd30a01dbee5a172e432a16078222 eclipse-poky e35dfd79e3970f88a8273125890a54f75f108b97 https://git.yoctoproject.org/cgit/cgit.cgi/eclipse-poky/commit/?id=e35dfd79e3970f88a8273125890a54f75f108b97 Please begin QA as soon as possible. Thank you. smime.p7s Description: S/MIME Cryptographic Signature ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Yocto Project 1.5_M2.rc1 build status
Adidtional autobuilder configuration errors were corrected and a third spin of 1.5_M2.rc1 started. Please find the build at the new location: http://autobuilder.yoctoproject.org/pub/nightly/20130703-3 pokyeaa5df34af42b6a37f6506847d0f3ef6ba0d298a https://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=eaa5df34af42b6a37f6506847d0f3ef6ba0d298a meta-fsl-armdaf582c93a7283fb0af3b25fe2ada48f4c9985c4 https://git.yoctoproject.org/cgit/cgit.cgi/meta-fsl-arm/commit/?id=daf582c93a7283fb0af3b25fe2ada48f4c9985c4 meta-fsl-ppca2bcb25c53f935ae9a423c57ca5e2f7a2f7b1a69 (Changed since last build) meta-intel e0d6134ed2e2687ff9f2ee77701666447842bf33 https://git.yoctoproject.org/cgit/cgit.cgi/meta-intel/commit/?id=e0d6134ed2e2687ff9f2ee77701666447842bf33 meta-minnow 286a72ba3f5e29432be1dd77127de5bdc2d988c3 https://git.yoctoproject.org/cgit/cgit.cgi/meta-minnow/commit/?id=286a72ba3f5e29432be1dd77127de5bdc2d988c3 meta-qt3b73552fb998fd30a01dbee5a172e432a16078222 https://git.yoctoproject.org/cgit/cgit.cgi/meta-qt3/commit/?id=b73552fb998fd30a01dbee5a172e432a16078222 eclipse-pokye35dfd79e3970f88a8273125890a54f75f108b97 https://git.yoctoproject.org/cgit/cgit.cgi/eclipse-poky/commit/?id=e35dfd79e3970f88a8273125890a54f75f108b97 Please begin QA as soon as possible. Thank you. smime.p7s Description: S/MIME Cryptographic Signature ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] Yocto Project 1.5_M2.rc1 build underway
The Yocto Project 1.5_M2.rc1 build is underway. As tasks complete artifacts will start appearing at: http://autobuilder.yoctoproject.org/pub/nightly/20130703-1 pokyeaa5df34af42b6a37f6506847d0f3ef6ba0d298a https://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=eaa5df34af42b6a37f6506847d0f3ef6ba0d298a meta-fsl-armdaf582c93a7283fb0af3b25fe2ada48f4c9985c4 https://git.yoctoproject.org/cgit/cgit.cgi/meta-fsl-arm/commit/?id=daf582c93a7283fb0af3b25fe2ada48f4c9985c4 meta-fsl-ppcb889029dca03fcb7e55c671aa5006fe8be1eefb0 https://git.yoctoproject.org/cgit/cgit.cgi/meta-fsl-ppc/commit/?id=b889029dca03fcb7e55c671aa5006fe8be1eefb0 meta-intel e0d6134ed2e2687ff9f2ee77701666447842bf33 https://git.yoctoproject.org/cgit/cgit.cgi/meta-intel/commit/?id=e0d6134ed2e2687ff9f2ee77701666447842bf33 meta-minnow 286a72ba3f5e29432be1dd77127de5bdc2d988c3 https://git.yoctoproject.org/cgit/cgit.cgi/meta-minnow/commit/?id=286a72ba3f5e29432be1dd77127de5bdc2d988c3 meta-qt3b73552fb998fd30a01dbee5a172e432a16078222 https://git.yoctoproject.org/cgit/cgit.cgi/meta-qt3/commit/?id=b73552fb998fd30a01dbee5a172e432a16078222 eclipse-pokye35dfd79e3970f88a8273125890a54f75f108b97 https://git.yoctoproject.org/cgit/cgit.cgi/eclipse-poky/commit/?id=e35dfd79e3970f88a8273125890a54f75f108b97 Please begin QA as soon as possible. Thank you. -- Michael Halstead Yocto Project / Sys Admin smime.p7s Description: S/MIME Cryptographic Signature ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Yocto Project 1.5_M2.rc1 build underway, again
After correcting some configuration errors the Yocto Project 1.5_M2.rc1 build is underway again. As tasks complete artifacts will start appearing at their new location: http://autobuilder.yoctoproject.org/pub/nightly/20130703-2 pokyeaa5df34af42b6a37f6506847d0f3ef6ba0d298a https://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=eaa5df34af42b6a37f6506847d0f3ef6ba0d298a meta-fsl-armdaf582c93a7283fb0af3b25fe2ada48f4c9985c4 https://git.yoctoproject.org/cgit/cgit.cgi/meta-fsl-arm/commit/?id=daf582c93a7283fb0af3b25fe2ada48f4c9985c4 meta-fsl-ppcb889029dca03fcb7e55c671aa5006fe8be1eefb0 https://git.yoctoproject.org/cgit/cgit.cgi/meta-fsl-ppc/commit/?id=b889029dca03fcb7e55c671aa5006fe8be1eefb0 meta-intel e0d6134ed2e2687ff9f2ee77701666447842bf33 https://git.yoctoproject.org/cgit/cgit.cgi/meta-intel/commit/?id=e0d6134ed2e2687ff9f2ee77701666447842bf33 meta-minnow 286a72ba3f5e29432be1dd77127de5bdc2d988c3 https://git.yoctoproject.org/cgit/cgit.cgi/meta-minnow/commit/?id=286a72ba3f5e29432be1dd77127de5bdc2d988c3 meta-qt3b73552fb998fd30a01dbee5a172e432a16078222 https://git.yoctoproject.org/cgit/cgit.cgi/meta-qt3/commit/?id=b73552fb998fd30a01dbee5a172e432a16078222 eclipse-pokye35dfd79e3970f88a8273125890a54f75f108b97 https://git.yoctoproject.org/cgit/cgit.cgi/eclipse-poky/commit/?id=e35dfd79e3970f88a8273125890a54f75f108b97 Please begin QA as soon as possible. Thank you. -- Michael Halstead Yocto Project / Sys Admin smime.p7s Description: S/MIME Cryptographic Signature ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] poky-extras
On 06/30/2013 10:44 PM, Darren Hart wrote: On Sun, 2013-06-30 at 22:33 -0700, Michael Halstead wrote: I can change the name shortly. Is there any reason to keep a read-only copy available at the current location temporarily? Not really. Unless Bruce is using it in some automated scripts that need to be updated. -- Darren The name has been changed. Shall we update the description or is Supplementary metadata layers to extend the Poky core https://git.yoctoproject.org/cgit/cgit.cgi/meta-yocto-kernel-extras/ still appropriate? Thanks, Michael Halstead Yocto Project / Sys Admin Michael Halstead Yocto Project / Sys Admin On 06/30/2013 10:19 PM, Rifenbark, Scott M wrote: Hi, I updated the dev-manual section that tells the user what is in this repo and shows an example of cloning it. Nothing changes except for the name, which I switched to 'meta-yocto-kernel-extras'. To me, it appears that the contents of the repo still contain the kernel BitBake append files that you edit to point to your locally modified kernel source files as described in the text. Within the entire YP documentation set, this little area is the only reference to the old 'poky-extras' repo. Here is the link to see the changes - http://www.yoctoproject.org/docs/1.5/dev-manual/dev-manual.html#meta-yocto-kernel-extras-repo. I am assuming that the name of the repo will indeed be changed to 'meta-yocto-kernel-extras'. If I don't hear from anyone, I will assume everything is good. Thanks, Scott -Original Message- From: Hart, Darren Sent: Friday, June 28, 2013 10:08 PM To: Richard Purdie Cc: Bruce Ashfield; Rifenbark, Scott M; yocto; Michael Halstead Subject: Re: poky-extras On Fri, 2013-06-28 at 14:56 +0100, Richard Purdie wrote: On Fri, 2013-06-28 at 09:40 -0400, Bruce Ashfield wrote: On 13-06-28 09:22 AM, Rifenbark, Scott M wrote: All I need is the name to make some initial changes. Personally, I'm fine with 'meta-yocto-kernel'. Naming things is never easy, so I won't agonize over whether or not an extras should be on the end. But the name should be clear that it isn't the main yocto kernel, it's just a few crappy bbappends that make working with it locally easier for some :) So my only counter proposal is: meta-yocto-kernel-extras I'm going to de-crapify the bbappends so they are more useful, and have started on that work, but haven't finished it yet. No strong feelings here. I just wiped out meta-linaro from there (hoping Darren won't mind) and that checksums.ini file. That's fine, I was just thinking about that last week when I saw Linaro has a meta-linaro. That's where it belongs, so buh-bye. :-) -- Darren Hart Intel Open Source Technology Center Yocto Project - Technical Lead - Linux Kernel smime.p7s Description: S/MIME Cryptographic Signature ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] poky-extras
I can change the name shortly. Is there any reason to keep a read-only copy available at the current location temporarily? Michael Halstead Yocto Project / Sys Admin On 06/30/2013 10:19 PM, Rifenbark, Scott M wrote: Hi, I updated the dev-manual section that tells the user what is in this repo and shows an example of cloning it. Nothing changes except for the name, which I switched to 'meta-yocto-kernel-extras'. To me, it appears that the contents of the repo still contain the kernel BitBake append files that you edit to point to your locally modified kernel source files as described in the text. Within the entire YP documentation set, this little area is the only reference to the old 'poky-extras' repo. Here is the link to see the changes - http://www.yoctoproject.org/docs/1.5/dev-manual/dev-manual.html#meta-yocto-kernel-extras-repo. I am assuming that the name of the repo will indeed be changed to 'meta-yocto-kernel-extras'. If I don't hear from anyone, I will assume everything is good. Thanks, Scott -Original Message- From: Hart, Darren Sent: Friday, June 28, 2013 10:08 PM To: Richard Purdie Cc: Bruce Ashfield; Rifenbark, Scott M; yocto; Michael Halstead Subject: Re: poky-extras On Fri, 2013-06-28 at 14:56 +0100, Richard Purdie wrote: On Fri, 2013-06-28 at 09:40 -0400, Bruce Ashfield wrote: On 13-06-28 09:22 AM, Rifenbark, Scott M wrote: All I need is the name to make some initial changes. Personally, I'm fine with 'meta-yocto-kernel'. Naming things is never easy, so I won't agonize over whether or not an extras should be on the end. But the name should be clear that it isn't the main yocto kernel, it's just a few crappy bbappends that make working with it locally easier for some :) So my only counter proposal is: meta-yocto-kernel-extras I'm going to de-crapify the bbappends so they are more useful, and have started on that work, but haven't finished it yet. No strong feelings here. I just wiped out meta-linaro from there (hoping Darren won't mind) and that checksums.ini file. That's fine, I was just thinking about that last week when I saw Linaro has a meta-linaro. That's where it belongs, so buh-bye. :-) -- Darren Hart Intel Open Source Technology Center Yocto Project - Technical Lead - Linux Kernel smime.p7s Description: S/MIME Cryptographic Signature ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] Additional spam filtering added for *@yoctoproject.org lists
Due to a recent increase in the amount of spam, list moderation has become very time consuming. In order to keep the lists running smoothly without overloading our hardworking moderators we have enabled several more layers of spam filtering. We are also now using real-time blacklists (http://en.wikipedia.org/wiki/DNSBL). If you find your e-mail isn't getting through to the lists please contact halstead on IRC (chat.freenode.net) or e-mail mhalst...@linuxfoundation.org for assistance. -- Michael Halstead Yocto Project / System Administrator smime.p7s Description: S/MIME Cryptographic Signature ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] Bug Trend for WW18 - new automated charts
Bug trend data is now gathered automatically and displayed using detailed interactive charts. Hover your mouse over various parts of the charts for more detail. The dynamic axis labels will sometimes omit text for readability but the relevant data is displayed in the chart. Data for each week is taken from 23:59:59 UTC on the Sunday ending the week. Daily data is collected during the last second of that day in UTC. Numbers from previous periods have been regenerated using these times for consistency. The charts are currently displayed on their own pages but in the future will be embedded into either the main Yocto Project website or the wiki. Find the new style trend charts links at https://wiki.yoctoproject.org/wiki/Yocto_Bug_Trend Or view them all at once at https://wiki.yoctoproject.org/charts/combo.html -- Michael Halstead Yocto Project / System Administrator signature.asc Description: OpenPGP digital signature ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] Improper 1.4_M5.rc1 tags pushed to git.yoctoproject.org
Less than 16 hours ago I improperly tagged 1.4_M5.rc1. If you have recently fetched updates from poky https://git.yoctoproject.org/cgit/cgit.cgi/poky/, eclipse-poky https://git.yoctoproject.org/cgit/cgit.cgi/eclipse-poky/, meta-intel https://git.yoctoproject.org/cgit/cgit.cgi/meta-intel/, or meta-qt3 https://git.yoctoproject.org/cgit/cgit.cgi/meta-qt3/ you will need to delete the bad tags. From inside your poky repository run: git tag -d 1.4_M5.rc1 If you see Deleted tag '1.4_M5.rc1' (was c459a89) then the tag has been correctly deleted. If you see error: tag '1.4_M5.rc1' not found. then your repository didn't have the bad tag and there is nothing else you need to do. Repeat the steps for eclipse-poky https://git.yoctoproject.org/cgit/cgit.cgi/eclipse-poky/, meta-intel https://git.yoctoproject.org/cgit/cgit.cgi/meta-intel/, and meta-qt3 https://git.yoctoproject.org/cgit/cgit.cgi/meta-qt3/ repositories if needed. From inside of each repository run: git tag -d 1.4_M5.rc1 Thank you, -- Michael Halstead Yocto Project / Sys Admin smime.p7s Description: S/MIME Cryptographic Signature ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] Yocto Project 1.4 milestone 4 released
Yocto Project 1.4 milestone 4 is ready. Kernel.org mirrors will be present shortly. -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 The fourth milestone for the upcoming Yocto Project 1.4 release is now available at: http://downloads.yoctoproject.org/releases/yocto/milestones/yocto-1.4-m4/poky-yocto-1.4-m4.tar.bz2 Thanks to everyone for all their hard work. Michael Halstead Yocto Project / System Administrator mich...@yoctoproject.org - yocto-1.4-m4 Errata - Release Name: eclipse-poky-yocto-1.4-m4 Branch: 1.4_M4 Tag: 1.4_M4.final Hash: d18c45e0f5367979f7402380ee123242da2b57d5 md5: f0ba42c65fbb53d456eb4c81a8e20672 eclipse-poky-yocto-1.4-m4.tar.bz2 Download Locations: http://downloads.yoctoproject.org/releases/yocto/milestones/yocto-1.4-m4/eclipse-poky-yocto-1.4-m4.tar.bz2 http://mirrors.kernel.org/yocto/yocto/milestones/yocto-1.4-m4/eclipse-poky-yocto-1.4-m4.tar.bz2 Release Name: meta-intel-yocto-1.4-m4 Branch: 1.4_M4 Tag: 1.4_M4.final Hash: 150be7c8fb97ac88737f6017fdf9dd47b273bb3e md5: eae235635e155f544a94cf46d90ed30e meta-intel-yocto-1.4-m4.tar.bz2 Download Locations: http://downloads.yoctoproject.org/releases/yocto/milestones/yocto-1.4-m4/meta-intel-yocto-1.4-m4.tar.bz2 http://mirrors.kernel.org/yocto/yocto/milestones/yocto-1.4-m4/meta-intel-yocto-1.4-m4.tar.bz2 Release Name: meta-qt3-yocto-1.4-m4 Branch: 1.4_M4 Tag: 1.4_M4.final Hash: 06e2fe600de962cdba53c23de1207501439a9c9f md5: 504f01a15fd52daffde64561bed6e689 meta-qt3-yocto-1.4-m4.tar.bz2 Download Locations: http://downloads.yoctoproject.org/releases/yocto/milestones/yocto-1.4-m4/meta-qt3-yocto-1.4-m4.tar.bz2 http://mirrors.kernel.org/yocto/yocto/milestones/yocto-1.4-m4/meta-qt3-yocto-1.4-m4.tar.bz2 Release Name: poky-yocto-1.4-m4 Branch: 1.4_M4 Tag: 1.4_M4.final Hash: 7d22ef28e64de06b6238d0ef9b664c0bee6efa46 md5: aa9c6703d41087859d38cf9920f47950 poky-yocto-1.4-m4.tar.bz2 Download Locations: http://downloads.yoctoproject.org/releases/yocto/milestones/yocto-1.4-m4/poky-yocto-1.4-m4.tar.bz2 http://mirrors.kernel.org/yocto/yocto/milestones/yocto-1.4-m4/poky-yocto-1.4-m4.tar.bz2 - Features - Performance enhancement in places such as the packaging process, pseudo, etc., which leads to more than 10% improvement of the total build time for core-image-sato. The build time for rootfs with sstate cache enabled has also been reduced in half. Various improvements to HOB, bitbake, systemd support, buildhistory tool, yocto-kernel tool, multi-lib, etc. Zypper updater cleanup. New comprehensive git proxy script (oe-git-proxy) with improvements suggested by the community. Regular package updates including gtk+, qemu, pseudo, net-tools, qmmp, perl, etc. and various bug fixes. - Known Issues - Bug 3908: Kernel panic on qemux86-64 when using runqemu kvm and cpu host Bug 3930: [Test Case 146 Failure] Check if AUTOPR could be export/lockdown for package build Bug 3804: connman offline mode doesn't work on qemu images Bug 3921: Hob in Build Appliance doesn't start. Bug 3338: iptables-1.4.15: autoreconf run failed on gmae-toolchain -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.14 (GNU/Linux) iQEcBAEBAgAGBQJROMTAAAoJEEyK+E/MEkQPv78IANIO3/LF4suz3L3v2ZLZ4XJE 5EVSvmlHeUJGbhJU+mYsgdr/xBiYiKdn+4SPOYaJqzp8zcI/4l3WUBaBrHHK3w5k VDogNdMQpd+hTF5QFL832KPeL27tjbQFbhZpI7/vg4dnQfzGn14YFNKEXG52pmMB hjJf4sGYsuGFZOOk46Po7dZf8hM45dqb9zRGoithyQ6mVbVSb63bOJnOXSgDhwOz b0Jjp4zlgljGN+RWz+DGWGPnRS07xEICkpZrgJedE8A9SDQuORuiBB+rNcsdN+ln ZgkreHuQD3XZR9F/5s+XuO0QqHC3+T+BpKbp6SUaB4spsc6mwZLHSIWH+5S3kKA= =FaOw -END PGP SIGNATURE- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] Yocto Project 1.4 milestone 3 released
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 The third milestone for the upcoming Yocto Project 1.4 release is now available at: http://downloads.yoctoproject.org/releases/yocto/milestones/yocto-1.4-m3/poky-yocto-1.4-m3.tar.bz2 Due to holiday scheduling the Yocto Project CCB approved merging the second and third milestones together. There is no separate 1.4_M2 release. Thanks to everyone for all their hard work. Michael Halstead Yocto Project / System Administrator mich...@yoctoproject.org - - yocto-1.4-m3 Errata - - Release Name: eclipse-poky-yocto-1.4-m3 Branch: 1.4_M3 Tag: 1.4_M3.rc2 Hash: 65f1b736b719ad5284281ccd88a33a5a92724da2 md5: 7869868e366c4df96a0fbc08e815881a eclipse-poky-yocto-1.4-m3.tar.bz2 Download Locations: http://downloads.yoctoproject.org/releases/yocto/milestones/yocto-1.4-m3/eclipse-poky-yocto-1.4-m3.tar.bz2 http://mirrors.kernel.org/yocto/yocto/milestones/yocto-1.4-m3/eclipse-poky-yocto-1.4-m3.tar.bz2 Release Name: meta-intel-yocto-1.4-m3 Branch: 1.4_M3 Tag: 1.4_M3.rc2 Hash: 4f676959c35cbd0ed9ac6a1817993d38611859e1 md5: 12db3fe2246a023778fdfdae4537495b meta-intel-yocto-1.4-m3.tar.bz2 Download Locations: http://downloads.yoctoproject.org/releases/yocto/milestones/yocto-1.4-m3/meta-intel-yocto-1.4-m3.tar.bz2 http://mirrors.kernel.org/yocto/yocto/milestones/yocto-1.4-m3/meta-intel-yocto-1.4-m3.tar.bz2 Release Name: meta-qt3-yocto-1.4-m3 Branch: 1.4_M3 Tag: 1.4_M3.rc2 Hash: 06e2fe600de962cdba53c23de1207501439a9c9f md5: 30ee9daddfb1720112f6b69d2b315482 meta-qt3-yocto-1.4-m3.tar.bz2 Download Locations: http://downloads.yoctoproject.org/releases/yocto/milestones/yocto-1.4-m3/meta-qt3-yocto-1.4-m3.tar.bz2 http://mirrors.kernel.org/yocto/yocto/milestones/yocto-1.4-m3/meta-qt3-yocto-1.4-m3.tar.bz2 Release Name: poky-yocto-1.4-m3 Branch: 1.4_M3 Tag: 1.4_M3.rc2 Hash: 3ae1a4ba972cfc17ff3f2fda632da8ecc3414885 md5: cec6355a03d5a48408d1f96f3b3c8f9e poky-yocto-1.4-m3.tar.bz2 Download Locations: http://downloads.yoctoproject.org/releases/yocto/milestones/yocto-1.4-m3/poky-yocto-1.4-m3.tar.bz2 http://mirrors.kernel.org/yocto/yocto/milestones/yocto-1.4-m3/poky-yocto-1.4-m3.tar.bz2 - - Features - - -- Integrated Wayland support. - - -- Update to LTSI 3.4 Linux kernel. - - -- 'ptest' feature to create packages containing the test suite of packages for running on the target, which enables more automated package testing. - - -- Track and display variable setting history in the build process to greatly enhance debugging/analyzing capability. - - -- Systemd support for core-image-minimal. - - -- Run postinstalls at do_rootfs time for pango, update-modules, matchbox-keyboard, busybox-syslog, etc. - - -- yocto-bsp improvement to support customized kernel via linux-yocto-custom - - -- New yocto-layer tool to create generic layers and list their input properties. - - -- HOB improvements and fixes including parser warning message display, UI fixes, etc. - - -- Package updates including boost, gtk+, dbus, iptables, eglibc, mesa, etc. and bug fixes. - - Known Issues Bug 3745 Bitbake remake/remake-native check error Bug 2918 lib64 sato and sato-sdk do_rootfs fails Bug 3756 Crosstap script fails Bug 3338 iptables-1.4.15: autoreconf run failed on gmae-toolchain Bug 3758 Package gtk+-2.0 missing from the userbuilt toolchain Bug 3805 PAM support: missing pam_systemd.so Bug 3804 connman offline mode doesn't work on qemu images Bug 3768 smart: --yaml option doesn't work Bug 3656 rpm2cpio: Segmentation fault -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.14 (GNU/Linux) iQEcBAEBAgAGBQJRF3bIAAoJEEyK+E/MEkQPmxYH/1J5u2Ur/cAgoNEnl7quN1CE q0bL8bPTPkMu/WJSybhCktg+S0boXUU/da4kUrEzz7Zon5t5OByRk0jOBbCQLPX/ Q0+S0WXvnLta6dvew7RzF4Aw3/tL6agnvZ/FIt1KmidQ19NnuVWQXXAU10uKkagF J1m47HuFk/xW14AWk4IpXb7iIz0nbDbkXfYXA0dC70JZktLP+hbkCX4icdtY6Pp5 LBZZOr/XRkUh+LkZT4cBddMyDLqSrr4Jf7ZesF4tOiA68LskOrreXt6YwVOS8F9Y 4YOfpUTt+U8v/Pv3uWbH34on7wC0ypxNdECjRATcmjYcadhtjaOz8tBQyJBr3EU= =1Qwy -END PGP SIGNATURE- -- Michael Halstead Yocto Project / System Administrator smime.p7s Description: S/MIME Cryptographic Signature ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Fwd: GMA3600 VGA Driver
On 02/01/2013 11:22 AM, Fábio Laureano Antônio wrote: Dear kindly ask for help to solve the demand mentioned above. After re-reading your e-mail it seems you are trying to find GMA3600 drivers for Ubuntu 12.10, not trying to build an embedded OS with GMA3600 support. Is that correct? If so this is probably not the right place to ask for assistance. If you are building an OS with Yocto Project can you please share what board you are working with? Michael Halstead Yocto Project / Sys Admin Since I am already grateful for the attention. -- Forwarded message -- From: *Fábio Laureano Antônio* fabiolaure...@bsd.com.br mailto:fabiolaure...@bsd.com.br Date: 2012/12/11 Subject: Re: GMA3600 VGA Driver To: Michael Halstead mich...@yoctoproject.org mailto:mich...@yoctoproject.org Dear Michael, I can not perform any of downloading dependencies mentioned on the page that you sent me. Attached hereto presented with error. And I'm a little confused on how this process could please illustrate how to install and configure the driver GMA3600? I have over 40 computers waiting for this solution to be able to open a supermarket. Since I am already grateful for the attention. 2012/12/10 Michael Halstead mich...@yoctoproject.org mailto:mich...@yoctoproject.org Hello, Have you looked at the sources from the Cedartrail BSP https://www.yoctoproject.org/download/intel%C2%AE-atom%E2%84%A2-processor-n2000-and-d2000-series-based-platform-cedar-trail-powervr-graphics-0? I think this contains the driver you are interested in. Please tell me if this helped you. Best regards, -- Michael Halstead Yocto Project / Sys Admin ask about link so I can download the driver for the card GMA 3600. For I have the OS Ubuntu 12.10 and need for running this adapter. Thank you for your attention. -- Fábio Laureano - Consultor de TI Ribeirão Vermelho - MG - BRAZIL 35 9803-3428 tel:35%209803-3428 -- Fábio Laureano - Consultor de TI Ribeirão Vermelho - MG - BRAZIL 35 9803-3428 ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto smime.p7s Description: S/MIME Cryptographic Signature ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] 1.4_M3.rc2 ready for QA
The 1.4_M3.rc2 is available at: http://autobuilder.yoctoproject.org/pub/nightly/20130131-4/ Built from: poky: 3ae1a4ba972cfc17ff3f2fda632da8ecc3414885 eclipse-poky: 65f1b736b719ad5284281ccd88a33a5a92724da2 meta-qt3: 06e2fe600de962cdba53c23de1207501439a9c9f Please begin testing against this RC. Please note that tag and branch names for this milestone will be named as if it was M3. Branches have already been created since some commits needed to be cherry-picked for the build. I will tag, sign and release the milestone if/when given the all clear. -- Michael Halstead Yocto Project / Sys Admin smime.p7s Description: S/MIME Cryptographic Signature ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] [Infrastructure] Yocto Project Downtime Jan 29th 17:00-21:00 UTC
The downtime window is: Tuesday, January 29, 2013 at 9:00 AM - 1:00 PMPST Tuesday, January 29, 2013 at 5:00 PM - 9:00 PMUTC The downtime should go unnoticed by most users. Servers at OSU-OSL will be brought down for important firmware and software upgrades. We will make every effort to keep web services accessible during this time. Git services should remain up. Mail delivery will be delayed. Downloads will be temporarily redirected to our mirrors at kernel.org. Autobuilders will not be accessible during the upgrades. -- Michael Halstead Yocto Project / Sys Admin smime.p7s Description: S/MIME Cryptographic Signature ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] experimental/meta-tpm replaced by experimental/meta-trusted
The public git repository experimental/meta-tpm has been replaced with experimental/meta-trusted which will include libraries and tools that are not necessarily TCG/TPM destined as well as the work that was already in place. Find the new repository at http://git.yoctoproject.org/cgit/cgit.cgi/experimental/meta-trusted/ -- Michael Halstead Yocto Project / Sys Admin smime.p7s Description: S/MIME Cryptographic Signature ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [PATCH 1/1] meta-intel: update MAINTAINERS with meta-intel mailing list info
On 11/11/2012 03:27 PM, Tom Zanussi wrote: On Sun, 2012-11-11 at 18:22 -0500, Philip Balister wrote: On 11/11/2012 06:18 PM, tom.zanu...@intel.com wrote: From: Tom Zanussi tom.zanu...@intel.com The newly created meta-intel mailing list is where meta-intel-specific e-mail and patches should now go. Update MAINTAINERS with that information. Signed-off-by: Tom Zanussi tom.zanu...@intel.com --- MAINTAINERS | 32 ++-- 1 file changed, 18 insertions(+), 14 deletions(-) diff --git a/MAINTAINERS b/MAINTAINERS index a2231d0..d5f521b 100644 --- a/MAINTAINERS +++ b/MAINTAINERS @@ -1,26 +1,30 @@ This file contains a list of BSP maintainers for the BSPs contained in the meta-intel repository. -Please submit any patches against meta-intel BSPs to the Yocto mailing -list (yocto@yoctoproject.org) and preface them with [meta-intel] in -the Subject: line of your e-mail(s). The latter makes it obvious that -your patches are intended for inclusion into meta-intel and also makes -it easier for maintainers to notice patches intended for meta-intel -amongst all the other traffic on the Yocto mailing list. Also, if -your patches are available via a public git repository, please also -include a URL to the repo and branch containing your patches as that -makes it easier for maintainers to grab and test your patches. +Please submit any patches against meta-intel BSPs to the meta-intel +mailing list (meta-in...@yoctoproject.org). Also, if your patches are +available via a public git repository, please include a URL to the +repo and branch containing your patches as that makes it easier for +maintainers to grab and test your patches. + +The web page for users of the meta-intel mailing list is +https://lists.yoctoproject.org/listinfo/meta-intel, where you can +subscribe to the list (please do, especially if you intend on +submitting patches). If you have problems with or questions about a particular BSP, feel -free to contact the maintainer directly (cc:ing the Yocto mailing list -puts it in the archive and helps other people who might have the same -questions in the future), but please try to do the following first: +free to contact the maintainer directly (cc:ing the meta-intel mailing +list puts it in the archive and helps other people who might have the +same questions in the future), but please try to do the following +first: - look in the Yocto Project Bugzilla (http://bugzilla.yoctoproject.org/) to see if a problem has -already been reported +already been reported. - - look through recent entries of the Yocto mailing list archives + - look through recent entries of the meta-intel mailing list +archives (https://lists.yoctoproject.org/pipermail/meta-intel/) +and the Yocto mailing list archives (https://lists.yoctoproject.org/pipermail/yocto/) to see if other people have run into similar problems or had similar questions answered. Can you setup gmane to archive the list also? Then people can follow the list using NNTP. I've requested this list be added to Gmane. It should be picked up shortly. Michael Halstead Yocto Project / Sys Admin Sounds like a good idea to me, but I'll have to defer to Michael (added to CC: Tom Philip smime.p7s Description: S/MIME Cryptographic Signature ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] HTTP read only access to git repositories available
All of the Yocto Project hosted git repositories can be accessed via the http protocol on port 80. This method uses the smart http backend and it is as fast as access via the git protocol. Connecting via http will help users behind a proxy clone and update repositories with minimal configuration. Configure git to use your http proxy by setting the http_proxy environment variable or by running 'git config http.proxy [proxy_url]'. URLs are listed at the bottom of cgit project pages after the clone heading. Visit http://git.yoctoproject.org/cgit/cgit.cgi/poky/ for an example. They follow the pattern http://git.yoctoproject.org/git/[repo_path]. -- Michael Halstead Yocto Project / Sys Admin smime.p7s Description: S/MIME Cryptographic Signature ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Cloning yocto repos over https
On 10/16/2012 09:44 AM, Evade Flow wrote: Is there a way to clone yocto repositories (say, poky) over https? I just announced that repositories are available from git.yoctoproject.org via http. I didn't mention it but clones via https will work equally well if that is preferable. As Paul mentioned, there is work in progress to make it possible to clone yocto repos over http. This should be finished in the very near future, but in the meantime, I've created some (very) unofficial mirrors here: http://github.com/yoctoproject-mirrors I have a script running that syncs all of these every 15 minutes or so. Perhaps this will help you until the official HTTP access is available. (Just be advised: I plan to delete these mirrors when they are no longer necessary...) The github mirrors shouldn't be needed any longer. Please tell me if there is anything more needed on this front. Michael Halstead Yocto Project / Sys Admin On Tue, Oct 16, 2012 at 6:50 AM, Paul Eggleton paul.eggle...@linux.intel.com wrote: On Friday 11 May 2012 09:35:30 Chin Huat Ang wrote: Is there a way to clone yocto repositories (say, poky) over https? I'm behind a firewall where git port is blocked, getting it opened is a bureaucracy nightmare. Sorry, it's taken us a while to look into this but we have opened a bug to track it - you may wish to add yourself to the CC list: http://bugzilla.yoctoproject.org/show_bug.cgi?id=3263 Cheers, Paul -- Paul Eggleton Intel Open Source Technology Centre ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto smime.p7s Description: S/MIME Cryptographic Signature ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] [ANNOUNCEMENT] Yocto 1.3 Milestone 4 Released
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hello, We are pleased to announce the fourth milestone of the coming release of Yocto 1.3. This milestone release is available at: http://downloads.yoctoproject.org/releases/yocto/milestones/yocto-1.3-m4/poky-yocto-1.3-m4.tar.bz2 or http://mirrors.kernel.org/yocto/yocto/milestones/yocto-1.3-m4/poky-yocto-1.3-m4.tar.bz2 Additional tarballs for meta-qt3 and the eclipse plugin are available at: http://downloads.yoctoproject.org/releases/yocto/milestones/yocto-1.3-m4/eclipse-poky-yocto-1.3-m4.tar.bz2 http://downloads.yoctoproject.org/releases/yocto/milestones/yocto-1.3-m4/meta-qt3-yocto-1.3-m4.tar.bz2 with mirror locations at: http://mirrors.kernel.org/yocto/yocto/milestones/yocto-1.3-m4/eclipse-poky-yocto-1.3-m4.tar.bz2 http://mirrors.kernel.org/yocto/yocto/milestones/yocto-1.3-m4/meta-qt3-yocto-1.3-m4.tar.bz2 For information on 1.3 M4 test results see: https://wiki.yoctoproject.org/wiki/Yocto_1.3_Milestone_Test_Report Thank you everyone for all your hard work. Michael Halstead Yocto Project / Sys Admin mich...@yoctoproject.org - yocto-1.3-m4 Errata - Release Name: eclipse-poky-yocto-1.3-m4 Branch: 1.3_M4 Tag: 1.3_M4.final Hash: cd7e7664dc342b6f52fbdc797845c1c19408f895 md5: 8631dd8988a217b8be1026e5862eb1fb eclipse-poky-yocto-1.3-m4.tar.bz2 Download Locations: http://downloads.yoctoproject.org/releases/yocto/milestones/yocto-1.3-m4/eclipse-poky-yocto-1.3-m4.tar.bz2 http://mirrors.kernel.org/yocto/yocto/milestones/yocto-1.3-m4/eclipse-poky-yocto-1.3-m4.tar.bz2 Release Name: meta-qt3-yocto-1.3-m4 Branch: 1.3_M4 Tag: 1.3_M4.final Hash: 8730326c902e6fb256b5dea77a6dde28d813c424 md5: de551c0781b418827f366b156dfd49a7 meta-qt3-yocto-1.3-m4.tar.bz2 Download Locations: http://downloads.yoctoproject.org/releases/yocto/milestones/yocto-1.3-m4/meta-qt3-yocto-1.3-m4.tar.bz2 http://mirrors.kernel.org/yocto/yocto/milestones/yocto-1.3-m4/meta-qt3-yocto-1.3-m4.tar.bz2 Release Name: poky-yocto-1.3-m4 Branch: 1.3_M4 Tag: 1.3_M4.final Hash: e5c3513ca8abb21eb5e9b8c19d1b9199b14ae07c md5: 94c63c3f437b182c9754984fa32f2758 poky-yocto-1.3-m4.tar.bz2 Download Locations: http://downloads.yoctoproject.org/releases/yocto/milestones/yocto-1.3-m4/poky-yocto-1.3-m4.tar.bz2 http://mirrors.kernel.org/yocto/yocto/milestones/yocto-1.3-m4/poky-yocto-1.3-m4.tar.bz2 - Features - * Complete kernel upgrade to 3.4.9 and real time kernel support and upgrade to kernel 3.4.9-rt17. * Bring meta-yocto to conform with the Yocto Project compliance criteria by separating out the hardware support components into meta-yocto-bsp and leaving policy configuration in meta-yocto. * Rename ‘task’ to ‘packagegroup’. Evaluate, refactor and clean up existing packagegroup (task) recipes including naming, description, structure, etc. * Switch to using ‘nativesdk’ as a prefix instead of a suffix to make scaling nativesdk and others easier. * Bitbake: fold Knotty2 into knotty and make it default, which handles bitbake console output in a much nicer way. * Re-locatable SDK: now SDK can be installed into user specified location. * Remove xserver-kdrive, and switch to X.org xserver for some BSPs. * Drop qemu GL passthrough support to improve stability and reduce maintenance issues. * Various update to Yocto Project documents including the quick start guide, development manual, BSP developer’s guide, etc. * Various fixes, cleanup and improvements to the yocto-bsp tool, bitbake, HOB, shared state cache, eglibc, uclibc, etc. * Various package upgrade including webkit-gtk, wget, dhcp, subversion, etc. - Known Issues - Bug 2878 pkgconfig is missing from sato-sdk image - installing and then trying to removing it leads to rpm crashes/assertions Bug 2399 gdk-pixbuf: hundreds of warnings on boot Bug 2415 connman doesn't provide a 3g configuration utility Bug 2694 [QEMU-X86_64]zypper refresh fail Bug 3047 do_rootfs: ERROR: tried running useradd command 10 times Bug 3116 sstate-cache-management.sh prints some error message when running Bug 2590 [multilib]do_rootfs failed for lib32-connman-gnome with ipk Bug 2918 lib64-core-image-sato-sdk fails due to do_rootfs issue Bug 3100 autoreconf run failed on x86-64 gmae-toolchain Bug 2577 Segmentation fault on qemuarm from /usr/lib/libust.so.0 Bug 2695 [HOB]toolchain arch in settings is not saved Please see https://wiki.yoctoproject.org/wiki/Yocto_1.3_Milestone_Test_Report for detail. -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.14 (GNU/Linux) iQEcBAEBAgAGBQJQZ1R/AAoJEEyK+E/MEkQPA4wIALe8rSbopGL0zAaOqLR6z6+8 J1XjvzQzY3qk5iWB6CeDK28/ZrhjaeI3sOwiB8CovFAYX9nFlr5vBQ3S3Zm56zad Etn2O2g5HQMORxeudDfNwJpRaTWSDz859ZOtgaSLDqh15UCmslCAtuYlDhG2lS9L cGarU9PDNo6vQRuO2KBc7oKnrUQyTscjfx4WhyiHyhYSBYAzXYQno3OXx4eSLYGs tR+pd60vXuRDfXdHsMOl+dlZxU6ukslvpDF4Z5lyVqKtqrvUzXDXymS7iN5qZvZn ieGVC0fpGSxKqN6ZGpWeeyH4teUmJj3BdtLwBgkcdLnv0qxideZrkglIjMrzl6U
[yocto] [ANNOUNCEMENT] Yocto 1.3 Milestone 3 Released
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hello, We are pleased to announce the third milestone of the coming release of Yocto 1.3. This milestone release is available at: http://downloads.yoctoproject.org/releases/yocto/milestones/yocto-1.3-m3/poky-yocto-1.3-m3.tar.bz2 or http://mirrors.kernel.org/yocto/yocto/milestones/yocto-1.3-m3/poky-yocto-1.3-m3.tar.bz2 Additional tarballs for meta-qt3 and the eclipse plugin are available at: http://downloads.yoctoproject.org/releases/yocto/milestones/yocto-1.3-m3/eclipse-poky-yocto-1.3-m3.tar.bz2 http://downloads.yoctoproject.org/releases/yocto/milestones/yocto-1.3-m3/meta-qt3-yocto-1.3-m3.tar.bz2 with mirror locations at: http://mirrors.kernel.org/yocto/yocto/milestones/yocto-1.3-m3/eclipse-poky-yocto-1.3-m3.tar.bz2 http://mirrors.kernel.org/yocto/yocto/milestones/yocto-1.3-m3/meta-qt3-yocto-1.3-m3.tar.bz2 For information on 1.3 M3 test results see: https://wiki.yoctoproject.org/wiki/Yocto_1.3_Milestone_Test_Report Thank you everyone for all the hard work. Michael Halstead Yocto Project / Sys Admin mich...@yoctoproject.org - yocto-1.3-m3 Errata - Release Name: eclipse-poky-yocto-1.3-m3 Branch: 1.3_M3 Tag: 1.3_M3.final Hash: db06ec9ffe7558107502599918db298abee160cd md5: a75e8e18d1029180803239a72a549ebb eclipse-poky-yocto-1.3-m3.tar.bz2 Download Locations: http://downloads.yoctoproject.org/releases/yocto/milestones/yocto-1.3-m3/eclipse-poky-yocto-1.3-m3.tar.bz2 http://mirrors.kernel.org/yocto/yocto/milestones/yocto-1.3-m3/eclipse-poky-yocto-1.3-m3.tar.bz2 Release Name: meta-qt3-yocto-1.3-m3 Branch: 1.3_M3 Tag: 1.3_M3.final Hash: f8475d5c5935695d4d1dfff1d7be30f49e162094 md5: 4231e853d33ab3eaccc97020704c2f16 meta-qt3-yocto-1.3-m3.tar.bz2 Download Locations: http://downloads.yoctoproject.org/releases/yocto/milestones/yocto-1.3-m3/meta-qt3-yocto-1.3-m3.tar.bz2 http://mirrors.kernel.org/yocto/yocto/milestones/yocto-1.3-m3/meta-qt3-yocto-1.3-m3.tar.bz2 Release Name: poky-yocto-1.3-m3 Branch: 1.3_M3 Tag: 1.3_M3.final Hash: 8b8748c8f963900b83dc0fdd7757556f917fe4fd md5: c1c662f38b281d771784b2e02385309e poky-yocto-1.3-m3.tar.bz2 Download Locations: http://downloads.yoctoproject.org/releases/yocto/milestones/yocto-1.3-m3/poky-yocto-1.3-m3.tar.bz2 http://mirrors.kernel.org/yocto/yocto/milestones/yocto-1.3-m3/poky-yocto-1.3-m3.tar.bz2 - Features - * eglibc upgrade to 2.16, mesa upgrade to 8.0.4 * Build history improvements such as tracking runtime package name and version changes when there is meta data changes. * Various bitbake usability improvement including adding search path to debug log, cleaning up runqueue exception catching in normal task failure case, handling broken symlinks in local mirror handling, etc. * The combo-layer tool usability improvement including improving patch list handling and output, allowing component pull to be done separately, etc. * The installer now supports EFI with a new basic EFI installer script in the initramfs-live-install-efi recipe. * Various bug fixes and improvement in areas such as connman, kern-tool, disabling gtk-doc, etc. - Known Issues - 2577 Segmentation fault on qemuarm from /usr/lib/libust.so.0 2775 [mpc8315e-rdb] kernel crashes when booting with 1.3 M2 RC1 20120712 build 2888 x32 build fails at gcc cross-initial do_compile 2969 Incremental RPM image generation is not working as expected 2980 toolchain issue - segmentation fault while configuring packages 3005 1.3 M3 build-appliance comes with old poky tree and m4-native compile fails Please see https://wiki.yoctoproject.org/wiki/Yocto_1.3_Milestone_Test_Report for detail. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iQEcBAEBAgAGBQJQP/+pAAoJEEyK+E/MEkQPsfoH/ic4Cy7jOO+A7M2aGE4U52xB KgvnGAIHMwWOVG9HV/rKRwCZMr5VsRNpXbzTwq6ff0Yy9DMkwbkNaDVAeaeG/Ywq 20otTtlnmEamv15TjuWK54euKhTdE8oBqJMsdSDxyWoIto6t3NXEcpGmJvTe3VGG VkUqB1cBLFP6o3W6TwJiXlQYKXXpyQnMIp9P5CuY6yJn7INH5ulYdjKIbC445GO5 jruCuvQYLme6ygcrONva3kgEngE5f+yjGiGF7xs5A4ASy/xgHdlrv90pVbMRBE86 W2aqVkXoGLD6MD4nUU20RuRXSKqvv7nFw7BrrT5+SY0w3GU0pW4dTl+HfwyzxJk= =iSgO -END PGP SIGNATURE- smime.p7s Description: S/MIME Cryptographic Signature ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] [infrastructure] Power interruption at OSL
There was an unintended power interruption during UPS electrical work at the OSU Open Source Lab today. Power to the Yocto Project racks was not impacted but the core router was briefly offline. This event doesn't appear to have impacted us but please report any network trouble that may be related. Michael Halstead Yocto Project / Sys Admin ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] [Infrastructure] ISP network maintenance August 20 between 3:00am and 6:00am PDT
This maintenance effects our main website, access to git repositories, mailing list traffic, bugzilla, and access to the autobuilders. NERO will be upgrading the firmware on all NERO Core routers during the next regularly scheduled maintenance window on Monday, August 20, 2012, between 0300-0600. This upgrade is expected to cause some disruption to all customer traffic. All efforts will be made to minimize the impact. Michael Halstead Yocto Project / Sys Admin smime.p7s Description: S/MIME Cryptographic Signature ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [Infrastructure] ISP network maintenance August 20 between 3:00am and 6:00am PDT
Just a clarification, the outage times are 10:00 - 13:00 UTC. (Our ISP, NERO, operates exclusively in Oregon USA). On 08/17/2012 12:41 PM, Michael Halstead wrote: This maintenance effects our main website, access to git repositories, mailing list traffic, bugzilla, and access to the autobuilders. NERO will be upgrading the firmware on all NERO Core routers during the next regularly scheduled maintenance window on Monday, August 20, 2012, between 0300-0600. This upgrade is expected to cause some disruption to all customer traffic. All efforts will be made to minimize the impact. Michael Halstead Yocto Project / Sys Admin smime.p7s Description: S/MIME Cryptographic Signature ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] [ANNOUNCEMENT] Yocto 1.1.2 Released
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hello, We are pleased to announce the new Yocto Project Edison point release 1.1.2. The full test report for this release is available at https://wiki.yoctoproject.org/wiki/Yocto_1.1.2_Test_Report You can download this release from either the main Yocto Project download site: http://downloads.yoctoproject.org/releases/yocto/yocto-1.1.2/poky-edison-6.0.2.tar.bz2 or the kernel.org mirror: http://mirrors.kernel.org/yocto/yocto/yocto-1.1.2/poky-edison-6.0.2.tar.bz2 Git tags gpg key information is available at: http://pgp.mit.edu:11371/pks/lookup?op=vindexsearch=0x4C8AF84FCC12440F Thank you everyone, especially the 1.1.2 maintainer Joshua Lock, for all their hard work! Michael Halstead Yocto Project Systems Administrator mich...@yoctoproject.org - edison-6.0.2 Errata - Release Name: eclipse-poky-edison-6.0.2 Branch: edison Tag: edison-6.0.2 Hash: 826e8b3bd14d945fafef3073884524a04bfa7f7c md5: f462da45012d59d2e2948e2e6a6906e2 eclipse-poky-edison-6.0.2.tar.bz2 Download Locations: http://downloads.yoctoproject.org/releases/yocto/yocto-1.1.2/eclipse-poky-edison-6.0.2.tar.bz2 http://mirrors.kernel.org/yocto/yocto/yocto-1.1.2/eclipse-poky-edison-6.0.2.tar.bz2 Release Name: meta-qt3-edison-6.0.2 Branch: edison Tag: edison-6.0.2 Hash: 0c3153242344e5113a50002939d36a2b739cc497 md5: 3a6dd4f556db5ca3ff55be09d4937b46 meta-qt3-edison-6.0.2.tar.bz2 Download Locations: http://downloads.yoctoproject.org/releases/yocto/yocto-1.1.2/meta-qt3-edison-6.0.2.tar.bz2 http://mirrors.kernel.org/yocto/yocto/yocto-1.1.2/meta-qt3-edison-6.0.2.tar.bz2 Release Name: poky-edison-6.0.2 Branch: edison Tag: edison-6.0.2 Hash: 8886aee5b9741c05886994967d9ecf420331c600 md5: 9974cb0751268b2fc14b6a27461c7d15 poky-edison-6.0.2.tar.bz2 Download Locations: http://downloads.yoctoproject.org/releases/yocto/yocto-1.1.2/poky-edison-6.0.2.tar.bz2 http://mirrors.kernel.org/yocto/yocto/yocto-1.1.2/poky-edison-6.0.2.tar.bz2 - Features - * Enhanced useradd class including fixes for the following issues: - Ensure -native recipes don't depend on target recipes - Fixes for useradd recipes when using shared state - Retry commands to avoid races around lock contention * Improved download reliability by adding checksums to several recipes * More robust image creation include: - Fixed creation of large (1GB) live images [YOCTO #2138] - Account for FAT fs overhead in image size [YOCTO #1852] - Ensure rootfs generation dependencies are built for live images [YOCTO #2246] * Several fixes for running on new distributions, inc: - Support building on 3.3 and newer kernel version [YOCTO #2236] - Handle new location of sys/time.h on Debian based systems - Support building apt-native with modern toolchains for deb based systems - Distributions with GCC 4.7 or newer will not be supported for Poky Edison - Known Issues - Bug 2015 - [emenlow]X is black when resume from S3 standby mode Bug 2742 - ioatdma error happened on jasperforest platform with edison branch Bug 2748 - launch qemu failed due to can not find GLIBC_2.14 with edison branch Bug 2694 - [QEMU-X86_64]zypper refresh fail Bug 2746 - mklibs-native failed to compile fedora17-X86_64 ** In general host OS's with GCC 4.7 won't be able to build Edison -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.14 (GNU/Linux) iQEcBAEBAgAGBQJQEbk9AAoJEEyK+E/MEkQPV3UIAJb4JQQ4ckPqFgNpyHzpBiGX vgGHU/5CgH8O+lAFaMp32E2Mw6hspo4w8qhKeh0bn6U+isDIR3+eO/qiRZmGizT7 e8Qw49oZmyTwj8n9tvLbDnQAM8469FmukYiq2ML/JUxHdbCjRpSVRXDqJGhSZNDF BpTtVgccNO8H5UGRjz0LW8TyCTbes3KFtEQ4cQZNtoHi6dBNOLFwGncCyDW+MW9+ uIqCNDCdRvoDCOYbfNzQkgRe3TNyhrxfZofBZkLRATlS8mMSk09lkbR39XsHHjPl /AqWwWTFQU8mEHo2lLPqduTkbKB8xg1ma3xQguA4V8TVyhjrefEj5wJCmMPU4KQ= =CqgW -END PGP SIGNATURE- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Manually fetching files (and disabling the sanity-checker)
On 07/18/2012 04:50 PM, Tim Bird wrote: Hi all, I've given up trying to work around Sony's firewall. After repeated attempts I still can't get any 'git:'-based URLS to work through the firewall. I vaguely recall the last time I worked on this (about 5.0 timeframe) there was a mirror where tarballs could be downloaded, if the git fetch didn't work. Sources the autobuilder uses are made available via http at http://downloads.yoctoproject.org/mirror/sources/ and can be used as a premirror. The directions in the following post should help you with set up, https://lists.yoctoproject.org/pipermail/yocto/2012-May/008966.html Michael Halstead Yocto Project / Sys Admin Is this mirror still available? If not, is there any way to disable the sanity-checker, and have bitbake tell me what repositories it's looking for, so I can manually construct a local mirror for yoctoproject to work off of? Is there any way to extract the tarballs from a build appliance image? Any advice or pointers would be appreciated. -- Tim = Tim Bird Architecture Group Chair, CE Workgroup of the Linux Foundation Senior Staff Engineer, Sony Network Entertainment = ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto smime.p7s Description: S/MIME Cryptographic Signature ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] Bugzilla Reorganization
The reorganization of bugzilla has been refined and the new layout is available for preview at https://bugzilla.yoctodev.org/. After a quick review I plan to make this change live on production. Expect a short 5 to 10 minute downtime while the changes go live later today. I've attached the new layout and mapping file for reference. -- Michael Halstead Yocto Project / Sys Admin +--+---+---++ | Classification | Product | Component | CompID | +--+---+---++ | Build System Metadata | BitBake | bitbake |107 | | Build System Metadata | Hob | hob |127 | | Build System Metadata | Hob | image creator |118 | | Build System Metadata | Layers| demoapps |116 | | Build System Metadata | Layers| dlna |122 | | Build System Metadata | Layers| layers |109 | | Build System Metadata | Layers| linaro |124 | | Build System Metadata | Meta-yocto| configuration |108 | | Build System Metadata | Meta-yocto| meta-yocto |110 | | Build System Metadata | OE-Core | configuration |135 | | Build System Metadata | OE-Core | connectivity |111 | | Build System Metadata | OE-Core | core |112 | | Build System Metadata | OE-Core | devtools / tool chain |113 | | Build System Metadata | OE-Core | graphics |114 | | Build System Metadata | OE-Core | kernel |129 | | Build System Metadata | OE-Core | multimedia |115 | | Build System Metadata | OE-Core | virtual machines |136 | | Build System Metadata | Web - Hob | web-hob |137 | | Documentation| ADT Docs | SDK | 87 | | Documentation| BSP Docs | bsp-docs |138 | | Documentation| Development | development |139 | | Documentation| Kernel Development| kernel-development |140 | | Documentation| Quick Start | quick-start |126 | | Documentation| Reference | handbook | 88 | | Documentation| Reference | PRD | 85 | | Infrastructure | AutoBuilder | autobuilder | 78 | | Infrastructure | Bugzilla | bugzilla | 91 | | Infrastructure | Website | website | 92 | | Infrastructure | Wiki | wiki |141 | | QA/Testing | Automated Build Testing | automated-build-testing |142 | | QA/Testing | Automated Runtime Testing | automated-runtime-testing |143 | | QA/Testing | Manual Testing| manual-testing |144 | | QA/Testing | Test Plans/Suite | test-plans/suite | 79 | | Runtime | Build Appliance | build-appliance |145 | | Runtime | Installation | Installation | 81 | | Runtime | Package Management Issues | package-management-issues |146 | | Runtime | Runtime | runtime |147 | | Runtime | Security | security | 83 | | Runtime | System Startup| system-startup | 82 | | Yocto Project Components | ADT | adt |119 | | Yocto Project Components | ADT | kernel analysis |120 | | Yocto Project Components | Anjuta Plugin | anjuta-plugin |100 | | Yocto Project Components | BSPs | bsps-configuration |105 | | Yocto Project Components | BSPs | bsps-meta-fsl-ppc |131 | | Yocto Project Components | BSPs | bsps-meta-intel |128 | | Yocto Project Components | BSPs | bsps-meta-ti
Re: [yocto] Bugzilla Reorganization
The reorganization at https://bugzilla.yoctoproject.org/ is complete. Total time offline was 7 minutes. Please report any errors to me via e-mail or to halstead in #yocto on freenode. Michael Halstead Yocto Project / Sys Admin On 06/15/2012 05:03 AM, Michael Halstead wrote: The reorganization of bugzilla has been refined and the new layout is available for preview at https://bugzilla.yoctodev.org/. After a quick review I plan to make this change live on production. Expect a short 5 to 10 minute downtime while the changes go live later today. I've attached the new layout and mapping file for reference. smime.p7s Description: S/MIME Cryptographic Signature ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Bugzilla Re-organization
On 05/30/2012 07:51 AM, Rifenbark, Scott M wrote: For documentation there should be six things. We are missing the ADT Manual and the BSP manual. The reclassification step is incomplete. ADT didn't reclassify as expected and has remained in Build System Metadata. BSPs is still in Yocto Project Components. I'll correct these in the script and import fresh data to test. Thank you Scott for reporting this. Michael Halstead ScottR -Original Message- From: yocto-boun...@yoctoproject.org [mailto:yocto-boun...@yoctoproject.org] On Behalf Of Michael Halstead Sent: Friday, May 25, 2012 3:38 PM To: yocto-infrastruct...@yoctoproject.org; Yocto Project Discussion Subject: [yocto] Bugzilla Re-organization The first draft of the reorganized bugzilla is available for feedback now at https://bugzilla.yoctodev.org/. Outgoing e-mail is currently disabled on this preview copy. Please feel free to take a look and see if you spot any errors. Additional refinement of product or component descriptions will be helpful as well. -- Michael Halstead Yocto Project / Sys Admin smime.p7s Description: S/MIME Cryptographic Signature ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Download mirror instability
The new download mirror is now active. Fetching from downloads.yoctoproject.org should be reliable once again. Michael Halstead Yocto Project / Sys Admin On 05/14/2012 08:21 PM, Michael Halstead wrote: We are experiencing download mirror instability that began with a DDOS on Friday. Since then the network configuration attached to the mirror server has been in flux. This caused several outages. Fetcher failures during the last 36 hours are probably caused by these issues. I am in the process of building a new download server which will help with stability. I will post to the list when the build is complete. Michael Halstead Yocto Project / Sys Admin smime.p7s Description: S/MIME Cryptographic Signature ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] [Infra] Network home directories
Problems: Moving files between builders requires copying them to localhost and back (slow) or forwarding your ssh-agent around (poor security). Different amounts of free local storage mean pokybuild has different size constraints on different builders which isn't helpful. Solution: Beth and I propose that we mount user home directories from the NAS on the autobuilder stack so that user files are shared across the build infrastructure. We will keep a copy of bare home directories with ssh keys on the filesystem below the network mount so that logins will continue to function even during a NAS outage. Interruption: Setting this up requires moving user home directories from /srv and consolidating the data. This wouldn't interrupt the builders but would keep some users from logging in for several minutes. What we gain: This offers the benefit of shared files across the builders as well as keeping the local disk free for poky builds. It allows easy tear-down and rebuilding of slave hosts because unique data is separated from local storage. Does this break anyone's existing workflow? Any other concerns? Michael Halstead Yocto Project / Sys Admin smime.p7s Description: S/MIME Cryptographic Signature ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] Download mirror instability
We are experiencing download mirror instability that began with a DDOS on Friday. Since then the network configuration attached to the mirror server has been in flux. This caused several outages. Fetcher failures during the last 36 hours are probably caused by these issues. I am in the process of building a new download server which will help with stability. I will post to the list when the build is complete. Michael Halstead Yocto Project / Sys Admin ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] Bugzilla Upgrade Complete
The upgrade to Bugzilla 4.2.1 is complete. The upgrade completed with 0 errors and 0 warnings. Total downtime was 6 minutes. I am still working on smoothly re-categorizing and renaming classifications, products, and components. Here are a list of new features from bugzilla.org http://www.bugzilla.org/releases/4.2.1/release-notes.html#v42_feat_email. Michael Halstead Yocto Project / Sys Admin smime.p7s Description: S/MIME Cryptographic Signature ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] 48 hour delay: Bugzilla Downtime for Upgrades
There was a possible error during the Bugzilla upgrade today. We have rolled back to the current version out of caution. Total downtime was 9 minutes. No data was affected. We are rescheduling to run the upgrade again in 48 hours. Bugzilla will temporarily go offline on Sunday April 29th 2012 at 19:00 UTC (12 noon PDT) for 10 minutes to 1 hour. During this time we will update to the newest version of Bugzilla. We will also rename classifications and products to reflect changes in Yocto Project. The new names will make labeling and finding bugs easier in the future. I will e-mail the list once the upgrade is complete. Michael Halstead Yocto Project / Sys Admin smime.p7s Description: S/MIME Cryptographic Signature ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] Bugzilla Downtime for Upgrades
Bugzilla will temporarily go offline on Friday April 27th 2012 at 19:00 UTC (12 noon PDT) for 10 minutes to 1 hour. During this time we will update to the newest version of Bugzilla. We will also rename classifications and products to reflect changes in Yocto Project. The new names will make labeling and finding bugs easier in the future. I will e-mail the list once the upgrade is complete. Michael Halstead Yocto Project / Sys Admin smime.p7s Description: S/MIME Cryptographic Signature ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] Bugzilla downtime begins in 30 minutes
We are starting the bug tracker upgrade in 30 minutes. There will be some downtime during the transition because we are both upgrading and moving to new servers. I will send another list mail went the process is complete. Michael Halstead Sys Admin / Yocto Project smime.p7s Description: S/MIME Cryptographic Signature ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] Bugzilla 4.0.3 online
Bugzilla is updated and live on the new server at https://bugzilla.yoctoproject.org/. SSL is now required to connect and all page loads will use the yoctoproject.org domain. Old bookmarks should be redirected properly. If you find issues with the new version please e-mail me at mich...@yoctoproject.org or open a bug at https://bugzilla.yoctoproject.org/enter_bug.cgi?product=Bugzilla Michael Halstead Sys Admin / Yocto Project smime.p7s Description: S/MIME Cryptographic Signature ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] Reminder Bugzilla Upgrade Tomorrow
This is just a quick reminder that bugzilla.yoctoproject.org and bugzilla.pokylinux.org will be offline starting at 3:00pm PST tomorrow. We hope to have the new version up and running within 30 minutes but the upgrade may take until 6:00pm. Michael Halstead Sys Admin / Yocto Project smime.p7s Description: S/MIME Cryptographic Signature ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] Bugzilla Downtime and Upgrade February 24th
We will be upgrading Bugzilla and moving servers on Friday February 24th. Traditionally Friday after 3pm PST is a low usage time and ideal for an upgrade. The Saturday after gives ample time for recovery in case of exceptional problems. Here is the timeline, I'm setting aside a 3 hour window but only 30 minutes should be needed. 3:00pm Current Bugzilla goes down and DNS is changed. 3:30pm Bugzilla is back up and available for use. I will update the list with any new information. 4:00pm bring up a read only copy of Bugzilla 3.x for comparison and troubleshooting. 4:00-6:00pm repair any issues found in real time. 6:00pm Fall back point, if 4.x is having problems this is when we will revert to version 3.6. Michael Halstead Sys Admin / Yocto Project smime.p7s Description: S/MIME Cryptographic Signature ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] Downtime for network configuration update 3pm PST (23:00 UTC) today
All Yocto services except for bugzilla will experience a 10-20 minute outage while we update network configuration at the OSU Open Source Lab. The downtime will begin at 3pm PST today. At the conclusion of the update routing between linuxfoundation.org and yoctoproject.org will be restored. Michael Halstead Sys Admin / Yocto Project smime.p7s Description: S/MIME Cryptographic Signature ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
