Hello Ming, I'm happy to hear that you're overall satisfied with the project, but I need to clarify the 'terms and conditions' of open source further: not only no one owes you a fix, no one owes you an investigation of a possible issue either, especially if the issue looks difficult or time-consuming to replicate (and in this case it is). So it's not likely there will be a definitive answer to the question of whether it's been fixed (or even whether it's a real issue in poky, or simply something specific to your configuration).
On the other hand, Yocto is open source. All development happens in the open, and obtaining the latest source tree is a single 'git clone' command. You're welcome to join the ongoing development rather than just use the release deliveries, and obtain the answers that way. What I'm specifically suggesting is: get the latest poky master revision, set up a minimal configuration where the issue can be observed, and then see if you, the team most affected by it, can first find out where things go wrong, and second how they could be fixed. It may also well be that the issue is indeed fixed in latest master. The community can assist in that investigation if you run into problems or are unsure how to proceed, but doing the investigation is on you. Once you establish those facts, we can help towards making fixes and backporting them to LTS. Alex On Thu, 21 Dec 2023 at 05:15, Ming Wen <m...@ambarella.com> wrote: > > Hi Alex: > > Nice to meet you and thanks for the comments. Fully understand! > > We're not trying to push you for the fix(definitely not). Instead, we always > appreciate your efforts on bringing Yocto to us. Really so many R&Ds love it. > It is even much more than our expectation when we tried to welcome Yocto to > our SDK years ago. > Here, we just seek for your help to see if this issue has been fixed in your > later LTS poky. If not, then to see if it can have a chance to be fixed in > future when you have enough resource. > > Thanks again for you and Yocto! > > Best Regards! > Ming Wen (闻明) > SDK Team | Ambarella Shanghai > > -----Original Message----- > From: Alexander Kanavin <alex.kana...@gmail.com> > Sent: Thursday, December 21, 2023 4:40 AM > To: yocto@lists.yoctoproject.org; Ming Wen <m...@ambarella.com> > Cc: ross.bur...@arm.com; Song-Jun Han <sj...@ambarella.com>; Jian Tang > <jt...@ambarella.com> > Subject: [EXT] Re: [yocto] do_populate_sdk_ext failed > > On Wed, 20 Dec 2023 at 01:51, Ming Wen <m...@ambarella.com> wrote: > > Song-Jun and myself are in the same team. We spent some efforts to > > make it happen for " do_populate_sdk_ext" finally by fixing some issue in > > Poky(we're using latest Kirkstone 4.0). But as you mentioned, when we tried > > the generated eSDK, we found that it still can't go with externalsrc > > enabled. :( We're wondering whether this limitation/issue will be resolved > > in your next LTS Scarthgap (5.0). Or it is still waiting to be fixed in > > future. If it is the later, we will file a bug for eSDK. > > Hello Ming, > > I have to stress that Yocto is a community open source project, and not your > commercial supplier. Nobody owes you a fix. If things do not work for you, it > is your responsibility to find out what solutions can be, and implement them > with code. You can of course file a bug as a way to document the problem, but > it doesn't mean the bug is going to be worked on by someone within reasonable > time. That only happens for high priority issues that affect many people, and > this one isn't such. > > Thanks, > Alex > > ###################################################################### > This EXTERNAL email has been scanned by Proofpoint Email Protect service. > > ********************************************************************** > This email and attachments contain Ambarella Proprietary and/or Confidential > Information and is intended solely for the use of the individual(s) to whom > it is addressed. Any unauthorized review, use, disclosure, distribute, copy, > or print is prohibited. If you are not an intended recipient, please contact > the sender by reply email and destroy all copies of the original message. > Thank you.
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#62015): https://lists.yoctoproject.org/g/yocto/message/62015 Mute This Topic: https://lists.yoctoproject.org/mt/103167520/21656 Group Owner: yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
