Hi Randy,
Sent patch for this with below subject line: [meta-oe][PATCH] ltrace: added alternate source Thanks & Regards, Aditya Tayade ________________________________ From: Randy MacLeod <[email protected]> Sent: Saturday, July 28, 2018 1:27 AM To: Aditya Tayade; [email protected]; [email protected] Cc: [email protected]; Nisha Parrakat Subject: Re: [oe] [meta-openembedded] Original ltrace_git.bb SRCREV commit used is now unavailable in git tarball from ltrace.org On 07/27/2018 06:34 AM, Aditya Tayade wrote: > Hi, > > > Me too facing same issue. Any advice on this. Archived versions to fix previous releases may be here: https://apac01.safelinks.protection.outlook.com/?url=https%3A%2F%2Falioth-archive.debian.org%2Fgit%2Fcollab-maint%2F&data=02%7C01%7CAditya.Tayade%40kpit.com%7Ce77886ee683842dd047d08d5f3fb451f%7C3539451eb46e4a26a242ff61502855c7%7C0%7C0%7C636683182900149535&sdata=UB%2F4VAlY8JydqNvYwsy4%2BDQd5Yfbz%2FPnMmzL9xp8GrY%3D&reserved=0 for master, a commit to pull from ltrace.org makes sense to me but someone who follows debian development might be able to help locate the git repo. All I found was: https://apac01.safelinks.protection.outlook.com/?url=https%3A%2F%2Falioth-archive.debian.org%2Fgit%2Fcollab-maint%2F&data=02%7C01%7CAditya.Tayade%40kpit.com%7Ce77886ee683842dd047d08d5f3fb451f%7C3539451eb46e4a26a242ff61502855c7%7C0%7C0%7C636683182900149535&sdata=UB%2F4VAlY8JydqNvYwsy4%2BDQd5Yfbz%2FPnMmzL9xp8GrY%3D&reserved=0 and a maze of twisty little hyperlinks. Aditya, Nisha, Will you send a patch? See: https://apac01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.openembedded.org%2Fwiki%2FHow_to_submit_a_patch_to_OpenEmbedded&data=02%7C01%7CAditya.Tayade%40kpit.com%7Ce77886ee683842dd047d08d5f3fb451f%7C3539451eb46e4a26a242ff61502855c7%7C0%7C0%7C636683182900149535&sdata=gsSW5cWRMpdL%2F7TLEVcj5K1kYfDbWZstw22RiSSGA%2BY%3D&reserved=0 ../Randy > > > > Regards, > > Aditya Tayade > > ________________________________ > From: Nisha Parrakat > Sent: Tuesday, July 24, 2018 4:08:12 PM > To: [email protected]; > [email protected] > Cc: [email protected] > Subject: [meta-openembedded] Original ltrace_git.bb SRCREV commit used is now > unavailable in git tarball from ltrace.org > > > Hi all, > > > ltrace recipe is pointing to a fetch url > (git://anonscm.debian.org/collab-maint/ltrace.git;branch=master) that is > discontinued now. > > No ltrace found in alternate salsa.debian.org. > > Tarball for ltrace is present in ltrace.org but the SRCREV in the mentioned > in the original recipe is not found any more but we do see the same commit > with another sha but a different git history. > > > Please advice if we should modify the SRCREV to reflect the new git source > from ltrace.org? > > > original SRCREV in recipe c22d3594... > > corresponding SRCREV coming from the git tarball is ea8928da... > > > Please advice . > > > > > Regards, > Ms Nisha Parrakat > KPIT Technologies Ltd, Pune, INDIA > > > This message contains information that may be privileged or confidential and > is the property of the KPIT Technologies Ltd. It is intended only for the > person to whom it is addressed. If you are not the intended recipient, you > are not authorized to read, print, retain copy, disseminate, distribute, or > use this message or any part thereof. If you receive this message in error, > please notify the sender immediately and delete all copies of this message. > KPIT Technologies Ltd. does not accept any liability for virus infected mails. > -- # Randy MacLeod # Wind River Linux This message contains information that may be privileged or confidential and is the property of the KPIT Technologies Ltd. It is intended only for the person to whom it is addressed. If you are not the intended recipient, you are not authorized to read, print, retain copy, disseminate, distribute, or use this message or any part thereof. If you receive this message in error, please notify the sender immediately and delete all copies of this message. KPIT Technologies Ltd. does not accept any liability for virus infected mails.
-- _______________________________________________ yocto mailing list [email protected] https://lists.yoctoproject.org/listinfo/yocto
