Re: [yocto] ROOTFS_RPM_DEBUG undocumented

On 05/08/2018 12:33 PM, Peter Kjellerstedt wrote: FYI, the already applied patch only solves half the problem. I have an updated version that solves all of it that I am preparing for publication. I only need to make some verifications first... I just found that out as well. Lua is not

Re: [yocto] ROOTFS_RPM_DEBUG undocumented

> -Original Message- > From: yocto-boun...@yoctoproject.org [mailto:yocto- > boun...@yoctoproject.org] On Behalf Of Alexander Kanavin > Sent: den 7 maj 2018 12:12 > To: Mirza Krak <mirza.k...@gmail.com> > Cc: Yocto list discussion <yocto@yoctoproject

Re: [yocto] ROOTFS_RPM_DEBUG undocumented

On 05/07/2018 12:03 PM, Mirza Krak wrote: I have also been bitten by rpm performance issues in docker and glad that I found this. I am in the process of verifying above (on pyro branch). Is this patch on its way to pyro and rocko branches? As far as I know, no. You are welcome to backport and

Re: [yocto] ROOTFS_RPM_DEBUG undocumented

On 4 May 2018 at 14:41, Alexander Kanavin wrote: > On 05/04/2018 03:42 PM, Paulo Neves wrote: >> >> I will propose a patch with a default bb.debug, and always have the >> verbose on dnf. Let's see how it affects the performance. I cannot >> test this in a docker

Re: [yocto] ROOTFS_RPM_DEBUG undocumented

Ouch you are right. Damn me for using pyro still? After applying this patch I will report on the remaining issues. On Fri, May 4, 2018 at 2:41 PM, Alexander Kanavin wrote: > On 05/04/2018 03:42 PM, Paulo Neves wrote: >> >> I will propose a patch with a default

Re: [yocto] ROOTFS_RPM_DEBUG undocumented

On 05/04/2018 03:50 PM, Scott Rifenbark wrote: If ROOTFS_RPM_DEBUG should be a documented variable in the Yocto Project Reference Manual, could someone please provide me with some base explanation of the variable and any usage specifics? No need, we're going to remove it. Alex --

Re: [yocto] ROOTFS_RPM_DEBUG undocumented

If ROOTFS_RPM_DEBUG should be a documented variable in the Yocto Project Reference Manual, could someone please provide me with some base explanation of the variable and any usage specifics? Thanks, Scott On Fri, May 4, 2018 at 5:41 AM, Alexander Kanavin < alexander.kana...@linux.intel.com>

Re: [yocto] ROOTFS_RPM_DEBUG undocumented

On 05/04/2018 03:41 PM, Alexander Kanavin wrote: https://bugzilla.redhat.com/show_bug.cgi?id=1537564 Obviously you and anyone else affected need to make noise in the redhat bugzilla, otherwise they're likely to keep this low priority. Alex -- ___

Re: [yocto] ROOTFS_RPM_DEBUG undocumented

On 05/04/2018 03:42 PM, Paulo Neves wrote: I will propose a patch with a default bb.debug, and always have the verbose on dnf. Let's see how it affects the performance. I cannot test this in a docker container because of the problems described below: In the mean time I found what was happening

Re: [yocto] ROOTFS_RPM_DEBUG undocumented

I will propose a patch with a default bb.debug, and always have the verbose on dnf. Let's see how it affects the performance. I cannot test this in a docker container because of the problems described below: In the mean time I found what was happening with my slow do_rootfs. I was running bitbake

Re: [yocto] ROOTFS_RPM_DEBUG undocumented

On 05/03/2018 04:37 PM, Peter Kjellerstedt wrote: # Have dnf always print in verbose mode and print the output to bb.debug instead of bb.note. I think this is the best solution actually. I disagree with changing bb.note to bb.debug for this. It is very good to be able to look in

Re: [yocto] ROOTFS_RPM_DEBUG undocumented

> -Original Message- > From: yocto-boun...@yoctoproject.org [mailto:yocto- > boun...@yoctoproject.org] On Behalf Of Alexander Kanavin > Sent: den 3 maj 2018 15:04 > To: Paulo Neves <ptsne...@gmail.com>; Yocto list discussion > <yocto@yoctoproject

Re: [yocto] ROOTFS_RPM_DEBUG undocumented

On 05/03/2018 01:42 PM, Paulo Neves wrote: # Add ROOTFS_RPM_DEBUG to the documentation; I'd rather get rid of it, the less variables the better :) # Detect if we are running with debug output and enable the debugging output. This is the most elegant solution but I do not know how to detect