* [yocto-patches] [meta-java] QA Issue: Missing Upstream-Status in patch @ 2025-02-21 3:26 Mingyu Wang (Fujitsu) 2025-02-21 3:40 ` Khem Raj 0 siblings, 1 reply; 11+ messages in thread From: Mingyu Wang (Fujitsu) @ 2025-02-21 3:26 UTC (permalink / raw) To: yocto-patches@lists.yoctoproject.org There're many patches that have the following error when build them: do_patch: QA Issue: Missing Upstream-Status in patch Should I fix them by adding "Upstrem-Status" to the patch file, or add " ERROR_QA:remove = "patch-status" " to conf/layer.conf to ignore the error. -- Best Regards --------------------------------------------------- Wang Mingyu FUJITSU NANJING SOFTWARE TECHNOLOGY CO., LTD. (FNST) No.6 Wenzhu Road, Nanjing, 210012, China TEL：+86+25-86630566--8568 COINS: 79988548 FAX: +86+25-83317685 MAIL: wangmy@fujitsu.com ^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: [yocto-patches] [meta-java] QA Issue: Missing Upstream-Status in patch 2025-02-21 3:26 [yocto-patches] [meta-java] QA Issue: Missing Upstream-Status in patch Mingyu Wang (Fujitsu) @ 2025-02-21 3:40 ` Khem Raj 2025-02-21 8:27 ` Mingyu Wang (Fujitsu) 0 siblings, 1 reply; 11+ messages in thread From: Khem Raj @ 2025-02-21 3:40 UTC (permalink / raw) To: yocto-patches On Thu, Feb 20, 2025 at 7:26 PM wangmy via lists.yoctoproject.org <wangmy=fujitsu.com@lists.yoctoproject.org> wrote: > > There're many patches that have the following error when build them: > do_patch: QA Issue: Missing Upstream-Status in patch > > Should I fix them by adding "Upstrem-Status" to the patch file, > or add " ERROR_QA:remove = "patch-status" " to conf/layer.conf to ignore the error. > Good uplift would be to add Upstream-Status as appropriate > > -- > Best Regards > --------------------------------------------------- > Wang Mingyu > FUJITSU NANJING SOFTWARE TECHNOLOGY CO., LTD. (FNST) > No.6 Wenzhu Road, Nanjing, 210012, China > TEL：+86+25-86630566--8568 > COINS: 79988548 > FAX: +86+25-83317685 > MAIL: wangmy@fujitsu.com > > > > -=-=-=-=-=-=-=-=-=-=-=- > Links: You receive all messages sent to this group. > View/Reply Online (#1108): https://lists.yoctoproject.org/g/yocto-patches/message/1108 > Mute This Topic: https://lists.yoctoproject.org/mt/111302715/1997914 > Group Owner: yocto-patches+owner@lists.yoctoproject.org > Unsubscribe: https://lists.yoctoproject.org/g/yocto-patches/leave/13340786/1997914/645821814/xyzzy [raj.khem@gmail.com] > -=-=-=-=-=-=-=-=-=-=-=- > > ^ permalink raw reply [flat|nested] 11+ messages in thread
* RE: [yocto-patches] [meta-java] QA Issue: Missing Upstream-Status in patch 2025-02-21 3:40 ` Khem Raj @ 2025-02-21 8:27 ` Mingyu Wang (Fujitsu) 2025-02-21 9:12 ` Richard Purdie 0 siblings, 1 reply; 11+ messages in thread From: Mingyu Wang (Fujitsu) @ 2025-02-21 8:27 UTC (permalink / raw) To: yocto-patches@lists.yoctoproject.org It's definitely the best thing to be able to do this But there are many patches with this problem, and it is uncertain what the purpose of the patch was at that time (many patches do not have commit information). In addition, most upstream have not been maintained or updated for a long time, so the feasibility of modifying them all seems not very high. It is best for the author of the patch to make the modifications. -- Best Regards --------------------------------------------------- Wang Mingyu FUJITSU NANJING SOFTWARE TECHNOLOGY CO., LTD. (FNST) No.6 Wenzhu Road, Nanjing, 210012, China TEL：+86+25-86630566--8568 COINS: 79988548 FAX: +86+25-83317685 MAIL: wangmy@fujitsu.com > -----Original Message----- > From: yocto-patches@lists.yoctoproject.org > <yocto-patches@lists.yoctoproject.org> On Behalf Of Khem Raj via > lists.yoctoproject.org > Sent: Friday, February 21, 2025 11:40 AM > To: yocto-patches@lists.yoctoproject.org > Subject: Re: [yocto-patches] [meta-java] QA Issue: Missing Upstream-Status in > patch > > On Thu, Feb 20, 2025 at 7:26 PM wangmy via lists.yoctoproject.org > <wangmy=fujitsu.com@lists.yoctoproject.org> wrote: > > > > There're many patches that have the following error when build them: > > do_patch: QA Issue: Missing Upstream-Status in patch > > > > Should I fix them by adding "Upstrem-Status" to the patch file, or add > > " ERROR_QA:remove = "patch-status" " to conf/layer.conf to ignore the error. > > > > Good uplift would be to add Upstream-Status as appropriate > > > > > -- > > Best Regards > > --------------------------------------------------- > > Wang Mingyu > > FUJITSU NANJING SOFTWARE TECHNOLOGY CO., LTD. (FNST) > > No.6 Wenzhu Road, Nanjing, 210012, China > > TEL：+86+25-86630566--8568 > > COINS: 79988548 > > FAX: +86+25-83317685 > > MAIL: wangmy@fujitsu.com > > > > > > > > > > > > > > > -=-=-=-=-=-=-=-=-=-=-=- > Links: You receive all messages sent to this group. > View/Reply Online (#1109): > https://lists.yoctoproject.org/g/yocto-patches/message/1109 > Mute This Topic: https://lists.yoctoproject.org/mt/111302715/5974946 > Group Owner: yocto-patches+owner@lists.yoctoproject.org > Unsubscribe: > https://lists.yoctoproject.org/g/yocto-patches/leave/13614271/5974946/19028 > 31066/xyzzy [wangmy@fujitsu.com] > -=-=-=-=-=-=-=-=-=-=-=- > ^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: [yocto-patches] [meta-java] QA Issue: Missing Upstream-Status in patch 2025-02-21 8:27 ` Mingyu Wang (Fujitsu) @ 2025-02-21 9:12 ` Richard Purdie 2025-02-21 9:20 ` Alexander Kanavin 0 siblings, 1 reply; 11+ messages in thread From: Richard Purdie @ 2025-02-21 9:12 UTC (permalink / raw) To: yocto-patches On Fri, 2025-02-21 at 08:27 +0000, wangmy via lists.yoctoproject.org wrote: > It's definitely the best thing to be able to do this > > But there are many patches with this problem, and it is uncertain > what the purpose of the patch was at that time (many patches do not > have commit information). > In addition, most upstream have not been maintained or updated for a > long time, so the feasibility of modifying them all seems not very > high. > > It is best for the author of the patch to make the modifications. That layer is struggling for maintainer time and the authors of the patches have moved on to other things a long time ago. I therefore don't think it will happen by the author or the layer maintainer. We do really need to work out that information but it isn't an easy job. This is why we now require it but these patches date from before we did that. It will need someone to spend time on it. Cheers, Richard ^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: [yocto-patches] [meta-java] QA Issue: Missing Upstream-Status in patch 2025-02-21 9:12 ` Richard Purdie @ 2025-02-21 9:20 ` Alexander Kanavin 2025-02-25 0:07 ` FW: " Mingyu Wang (Fujitsu) 2025-02-25 0:21 ` Mingyu Wang (Fujitsu) 0 siblings, 2 replies; 11+ messages in thread From: Alexander Kanavin @ 2025-02-21 9:20 UTC (permalink / raw) To: yocto-patches, wangmy On Fri, 21 Feb 2025 at 10:12, Richard Purdie via lists.yoctoproject.org <richard.purdie=linuxfoundation.org@lists.yoctoproject.org> wrote: > > It's definitely the best thing to be able to do this > > > > But there are many patches with this problem, and it is uncertain > > what the purpose of the patch was at that time (many patches do not > > have commit information). > > In addition, most upstream have not been maintained or updated for a > > long time, so the feasibility of modifying them all seems not very > > high. > > > > It is best for the author of the patch to make the modifications. > > That layer is struggling for maintainer time and the authors of the > patches have moved on to other things a long time ago. I therefore > don't think it will happen by the author or the layer maintainer. > > We do really need to work out that information but it isn't an easy > job. This is why we now require it but these patches date from before > we did that. It will need someone to spend time on it. This is the situation with meta-java: https://lists.openembedded.org/g/openembedded-devel/message/114958 I'd say you Wang need to commit to maintaining that layer if you want to keep it in some kind of working state. There's just no one else who has an interest in it anymore. Alex ^ permalink raw reply [flat|nested] 11+ messages in thread
* FW: [yocto-patches] [meta-java] QA Issue: Missing Upstream-Status in patch 2025-02-21 9:20 ` Alexander Kanavin @ 2025-02-25 0:07 ` Mingyu Wang (Fujitsu) 2025-02-25 0:21 ` Mingyu Wang (Fujitsu) 1 sibling, 0 replies; 11+ messages in thread From: Mingyu Wang (Fujitsu) @ 2025-02-25 0:07 UTC (permalink / raw) To: yocto-patches@lists.yoctoproject.org Cc: douglas.royds=taitcommunications.com@lists.yoctoproject.org There're many patches that have the following error when build them: do_patch: QA Issue: Missing Upstream-Status in patch Do you have any suggestions regarding the Upstream-Status error? Should I fix them by adding "Upstrem-Status" to the patch file, or add " ERROR_QA:remove = "patch-status" " to conf/layer.conf to ignore the error. Of course, the latter requires a lot of time to figure out the reasons for the existence of these patches and their latest status, and progress may be slow -- Best Regards --------------------------------------------------- Wang Mingyu FUJITSU NANJING SOFTWARE TECHNOLOGY CO., LTD. (FNST) No.6 Wenzhu Road, Nanjing, 210012, China TEL：+86+25-86630566--8568 COINS: 79988548 FAX: +86+25-83317685 MAIL: wangmy@fujitsu.com -----Original Message----- From: yocto-patches@lists.yoctoproject.org <yocto-patches@lists.yoctoproject.org> On Behalf Of Alexander Kanavin via lists.yoctoproject.org Sent: Friday, February 21, 2025 5:21 PM To: yocto-patches@lists.yoctoproject.org; Wang, Mingyu/王 鸣瑜 <wangmy@fujitsu.com> Subject: Re: [yocto-patches] [meta-java] QA Issue: Missing Upstream-Status in patch On Fri, 21 Feb 2025 at 10:12, Richard Purdie via lists.yoctoproject.org <richard.purdie=linuxfoundation.org@lists.yoctoproject.org> wrote: > > It's definitely the best thing to be able to do this > > > > But there are many patches with this problem, and it is uncertain > > what the purpose of the patch was at that time (many patches do not > > have commit information). > > In addition, most upstream have not been maintained or updated for a > > long time, so the feasibility of modifying them all seems not very > > high. > > > > It is best for the author of the patch to make the modifications. > > That layer is struggling for maintainer time and the authors of the > patches have moved on to other things a long time ago. I therefore > don't think it will happen by the author or the layer maintainer. > > We do really need to work out that information but it isn't an easy > job. This is why we now require it but these patches date from before > we did that. It will need someone to spend time on it. This is the situation with meta-java: https://lists.openembedded.org/g/openembedded-devel/message/114958 I'd say you Wang need to commit to maintaining that layer if you want to keep it in some kind of working state. There's just no one else who has an interest in it anymore. Alex -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#1113): https://lists.yoctoproject.org/g/yocto-patches/message/1113 Mute This Topic: https://lists.yoctoproject.org/mt/111302715/5974946 Group Owner: yocto-patches+owner@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/yocto-patches/leave/13614271/5974946/1902831066/xyzzy [wangmy@fujitsu.com] -=-=-=-=-=-=-=-=-=-=-=- ^ permalink raw reply [flat|nested] 11+ messages in thread
* FW: [yocto-patches] [meta-java] QA Issue: Missing Upstream-Status in patch 2025-02-21 9:20 ` Alexander Kanavin 2025-02-25 0:07 ` FW: " Mingyu Wang (Fujitsu) @ 2025-02-25 0:21 ` Mingyu Wang (Fujitsu) 2025-02-25 7:55 ` Alexander Kanavin 1 sibling, 1 reply; 11+ messages in thread From: Mingyu Wang (Fujitsu) @ 2025-02-25 0:21 UTC (permalink / raw) To: yocto-patches@lists.yoctoproject.org; +Cc: Tim Orling There're many patches that have the following error when build them: do_patch: QA Issue: Missing Upstream-Status in patch Do you have any suggestions regarding the Upstream-Status error? Should I fix them by adding "Upstrem-Status" to the patch file, or add " ERROR_QA:remove = "patch-status" " to conf/layer.conf to ignore the error. Of course, the latter requires a lot of time to figure out the reasons for the existence of these patches and their latest status, and progress may be slow -- Best Regards --------------------------------------------------- Wang Mingyu FUJITSU NANJING SOFTWARE TECHNOLOGY CO., LTD. (FNST) No.6 Wenzhu Road, Nanjing, 210012, China TEL：+86+25-86630566--8568 COINS: 79988548 FAX: +86+25-83317685 MAIL: wangmy@fujitsu.com -----Original Message----- From: yocto-patches@lists.yoctoproject.org <yocto-patches@lists.yoctoproject.org> On Behalf Of Alexander Kanavin via lists.yoctoproject.org Sent: Friday, February 21, 2025 5:21 PM To: yocto-patches@lists.yoctoproject.org; Wang, Mingyu/王 鸣瑜 <wangmy@fujitsu.com> Subject: Re: [yocto-patches] [meta-java] QA Issue: Missing Upstream-Status in patch On Fri, 21 Feb 2025 at 10:12, Richard Purdie via lists.yoctoproject.org <richard.purdie=linuxfoundation.org@lists.yoctoproject.org> wrote: > > It's definitely the best thing to be able to do this > > > > But there are many patches with this problem, and it is uncertain > > what the purpose of the patch was at that time (many patches do not > > have commit information). > > In addition, most upstream have not been maintained or updated for a > > long time, so the feasibility of modifying them all seems not very > > high. > > > > It is best for the author of the patch to make the modifications. > > That layer is struggling for maintainer time and the authors of the > patches have moved on to other things a long time ago. I therefore > don't think it will happen by the author or the layer maintainer. > > We do really need to work out that information but it isn't an easy > job. This is why we now require it but these patches date from before > we did that. It will need someone to spend time on it. This is the situation with meta-java: https://lists.openembedded.org/g/openembedded-devel/message/114958 I'd say you Wang need to commit to maintaining that layer if you want to keep it in some kind of working state. There's just no one else who has an interest in it anymore. Alex -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#1113): https://lists.yoctoproject.org/g/yocto-patches/message/1113 Mute This Topic: https://lists.yoctoproject.org/mt/111302715/5974946 Group Owner: yocto-patches+owner@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/yocto-patches/leave/13614271/5974946/1902831066/xyzzy [wangmy@fujitsu.com] -=-=-=-=-=-=-=-=-=-=-=- ^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: FW: [yocto-patches] [meta-java] QA Issue: Missing Upstream-Status in patch 2025-02-25 0:21 ` Mingyu Wang (Fujitsu) @ 2025-02-25 7:55 ` Alexander Kanavin 2025-02-26 0:34 ` Mingyu Wang (Fujitsu) 0 siblings, 1 reply; 11+ messages in thread From: Alexander Kanavin @ 2025-02-25 7:55 UTC (permalink / raw) To: yocto-patches, wangmy; +Cc: Tim Orling On Tue, 25 Feb 2025 at 01:21, wangmy via lists.yoctoproject.org <wangmy=fujitsu.com@lists.yoctoproject.org> wrote: > There're many patches that have the following error when build them: > do_patch: QA Issue: Missing Upstream-Status in patch > > Do you have any suggestions regarding the Upstream-Status error? > Should I fix them by adding "Upstrem-Status" to the patch file, or add " ERROR_QA:remove = "patch-status" " to conf/layer.conf to ignore the error. > Of course, the latter requires a lot of time to figure out the reasons for the existence of these patches and their latest status, and progress may be slow You are asking the same thing again and again. Please do not do this. The only answer is: meta-java has no maintainer, and Tim, or anyone else, is unable to help you. You need to become the maintainer first. Alex ^ permalink raw reply [flat|nested] 11+ messages in thread
* RE: FW: [yocto-patches] [meta-java] QA Issue: Missing Upstream-Status in patch 2025-02-25 7:55 ` Alexander Kanavin @ 2025-02-26 0:34 ` Mingyu Wang (Fujitsu) 2025-02-26 10:03 ` Alexander Kanavin 0 siblings, 1 reply; 11+ messages in thread From: Mingyu Wang (Fujitsu) @ 2025-02-26 0:34 UTC (permalink / raw) To: Alexander Kanavin, yocto-patches@lists.yoctoproject.org To Alex, I'm sorry. I have read Tim's message. As the following he said, it seems that he will merge patches to meta-java. So, I just wanted to get some suggestions from him. > My requirements for the current state of meta-java are that any patches MUST apply to "master" (meaning the development "walnascar" 5.2 release at this time, > but we've been in this state since scarthgap at least and probably more like since kirkstone). If patches apply cleanly, including building and run-time testing, then I am willing to apply them. >The only answer is: meta-java has no maintainer, and Tim, or anyone >else, is unable to help you. You need to become the maintainer first. I wonder if it means that I or somebody else can become the maintainer of meta-java? -- Best Regards --------------------------------------------------- Wang Mingyu FUJITSU NANJING SOFTWARE TECHNOLOGY CO., LTD. (FNST) No.6 Wenzhu Road, Nanjing, 210012, China TEL：+86+25-86630566--8568 COINS: 79988548 FAX: +86+25-83317685 MAIL: wangmy@fujitsu.com > -----Original Message----- > From: Alexander Kanavin <alex.kanavin@gmail.com> > Sent: Tuesday, February 25, 2025 3:56 PM > To: yocto-patches@lists.yoctoproject.org; Wang, Mingyu/王 鸣瑜 > <wangmy@fujitsu.com> > Cc: Tim Orling <tim.orling@konsulko.com> > Subject: Re: FW: [yocto-patches] [meta-java] QA Issue: Missing Upstream-Status > in patch > > On Tue, 25 Feb 2025 at 01:21, wangmy via lists.yoctoproject.org > <wangmy=fujitsu.com@lists.yoctoproject.org> wrote: > > There're many patches that have the following error when build them: > > do_patch: QA Issue: Missing Upstream-Status in patch > > > > Do you have any suggestions regarding the Upstream-Status error? > > Should I fix them by adding "Upstrem-Status" to the patch file, or add " > ERROR_QA:remove = "patch-status" " to conf/layer.conf to ignore the error. > > Of course, the latter requires a lot of time to figure out the reasons > > for the existence of these patches and their latest status, and > > progress may be slow > > You are asking the same thing again and again. Please do not do this. > > The only answer is: meta-java has no maintainer, and Tim, or anyone else, is > unable to help you. You need to become the maintainer first. > > Alex ^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: FW: [yocto-patches] [meta-java] QA Issue: Missing Upstream-Status in patch 2025-02-26 0:34 ` Mingyu Wang (Fujitsu) @ 2025-02-26 10:03 ` Alexander Kanavin 2025-02-26 11:35 ` Richard Purdie 0 siblings, 1 reply; 11+ messages in thread From: Alexander Kanavin @ 2025-02-26 10:03 UTC (permalink / raw) To: Mingyu Wang (Fujitsu); +Cc: yocto-patches@lists.yoctoproject.org On Wed, 26 Feb 2025 at 01:34, Mingyu Wang (Fujitsu) <wangmy@fujitsu.com> wrote: > >The only answer is: meta-java has no maintainer, and Tim, or anyone > >else, is unable to help you. You need to become the maintainer first. > > I wonder if it means that I or somebody else can become the maintainer of meta-java? What you can do is make a fork of meta-java somewhere public (typically we suggest github, but that might be difficult for you to access from PRC). Then you can add your patches and fixes in it, and send announcements here when there are significant enhancements. If there's a good track record and commitment to making it work according to official yocto layer standards, then we can make it official. Alex ^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: FW: [yocto-patches] [meta-java] QA Issue: Missing Upstream-Status in patch 2025-02-26 10:03 ` Alexander Kanavin @ 2025-02-26 11:35 ` Richard Purdie 0 siblings, 0 replies; 11+ messages in thread From: Richard Purdie @ 2025-02-26 11:35 UTC (permalink / raw) To: yocto-patches, Mingyu Wang (Fujitsu) On Wed, 2025-02-26 at 11:03 +0100, Alexander Kanavin via lists.yoctoproject.org wrote: > On Wed, 26 Feb 2025 at 01:34, Mingyu Wang (Fujitsu) > <wangmy@fujitsu.com> wrote: > > > The only answer is: meta-java has no maintainer, and Tim, or > > > anyone > > > else, is unable to help you. You need to become the maintainer > > > first. > > > > I wonder if it means that I or somebody else can become the > > maintainer of meta-java? > > What you can do is make a fork of meta-java somewhere public > (typically we suggest github, but that might be difficult for you to > access from PRC). Then you can add your patches and fixes in it, and > send announcements here when there are significant enhancements. If > there's a good track record and commitment to making it work > according > to official yocto layer standards, then we can make it official. We could also provide a contrib/ branch in the repo which you could push your changes too as a staging area. Cheers, Richard ^ permalink raw reply [flat|nested] 11+ messages in thread
end of thread, other threads:[~2025-02-26 11:36 UTC | newest] Thread overview: 11+ messages (download: mbox.gz follow: Atom feed -- links below jump to the message on this page -- 2025-02-21 3:26 [yocto-patches] [meta-java] QA Issue: Missing Upstream-Status in patch Mingyu Wang (Fujitsu) 2025-02-21 3:40 ` Khem Raj 2025-02-21 8:27 ` Mingyu Wang (Fujitsu) 2025-02-21 9:12 ` Richard Purdie 2025-02-21 9:20 ` Alexander Kanavin 2025-02-25 0:07 ` FW: " Mingyu Wang (Fujitsu) 2025-02-25 0:21 ` Mingyu Wang (Fujitsu) 2025-02-25 7:55 ` Alexander Kanavin 2025-02-26 0:34 ` Mingyu Wang (Fujitsu) 2025-02-26 10:03 ` Alexander Kanavin 2025-02-26 11:35 ` Richard Purdie
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.