Martin, I noticed this issue with devmem2 as well. I did some digging and I found this post on the mailing list from Dec 2106
http://lists.openembedded.org/pipermail/openembedded-devel/2 016-December/110568.html. Its possible that lartmarker domain has been down for some time. It looks like the version of devmem2 on sources.openembedded.org has changed and is now identical to the the updated devmem2.c on free-electrons mirror, AND it is the same as the updated version in http://sources.openembedded.org/devmem2-new.c. This means the checksum on the open embedded mirror doesn't match the checksum called out in the devmem2 recipes older than pyro. What is the recommendation for developers who need to stay on older branches such as Jethro for development cycle reasons? Is it as easy as contacting the maintainer of the open embedded source mirror to check if devmem2.c has been modified lately? Greg On Wed, May 31, 2017 at 11:17 AM, Leonardo Sandoval < [email protected]> wrote: > On Tue, 2017-05-30 at 20:10 +0000, Martin Siegumfeldt wrote: > > Hi, > > > > > > Is there any chance that http://git.openembedded.org/ > meta-openembedded/commit/?id=fc801961457fe2fbb24973bb43b302ad46044cb8 and > http://git.openembedded.org/meta-openembedded/commit/?id= > 6c584374a599f6f8d3607f20ecfc13a67ccf1da1 will be backported to release > branches? lartmaker domain seems no longer available - AFAICS all branches > older than pyro is affected. > > > > without much contexts on these two patches, send the backported patches > with proper stable releases names as prefixes to the mailing list. > > > > > Thanks, > > > > Martin > > > -- > _______________________________________________ > Openembedded-devel mailing list > [email protected] > http://lists.openembedded.org/mailman/listinfo/openembedded-devel > -- _______________________________________________ Openembedded-devel mailing list [email protected] http://lists.openembedded.org/mailman/listinfo/openembedded-devel
