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

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 prop

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 sour

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:

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 Yo

-----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

You were both already in the CC list. You should receive copies when the next release candidate is built. Michael Halstead Yocto Project / System Administrator

The QA_MAIL_CC value in ./config/autobuilder.conf needed to be comma separated. I think it is fixed now. Thanks for the report. Michael Halstead Yocto Project / SysAdmin

-----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 bugzil

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

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 ma

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

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/fe

I recently updated git to version 1.9.0 which caused the problem. With 1.9.0 additional permissions to the are required to write temporary files in the working directory. I've rolled back the upgrade

#yocto

Good idea. I've prepended '-- ' to the footers of all Yocto Project and OE lists. Michael Halstead Yocto Project / Sys Admin

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

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 loca

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 a

The trend graphs for work week 40 have been updated automatically at https://wiki.yoctoproject.org/wiki/Yocto_Bug_Trend. The weighted defect density increased from last week's 1603 to 1633, the report

The trend graphs for work week 40 have been updated automatically at https://wiki.yoctoproject.org/wiki/Yocto_Bug_Trend. The weighted defect density decreased from last week's 1604 to 1603, the report