From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by finch.gentoo.org (Postfix) with ESMTPS id 9D339158041 for ; Fri, 8 Mar 2024 08:24:02 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 796D32BC013; Fri, 8 Mar 2024 08:23:58 +0000 (UTC) Received: from smtp.gentoo.org (dev.gentoo.org [IPv6:2001:470:ea4a:1:5054:ff:fec7:86e4]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 24C34E29DD for ; Fri, 8 Mar 2024 08:23:58 +0000 (UTC) From: Agostino Sarubbo To: gentoo-dev@lists.gentoo.org Subject: [gentoo-dev] unprefixed eqawarn Date: Fri, 08 Mar 2024 09:23:53 +0100 Message-ID: <65790472.3F2A3RajZp@fcf> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@lists.gentoo.org Reply-to: gentoo-dev@lists.gentoo.org X-Auto-Response-Suppress: DR, RN, NRN, OOF, AutoReply MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="nextPart17473435.5WZRyvrzyv" Content-Transfer-Encoding: 7Bit X-Archives-Salt: 03648bcf-edce-48e1-9be8-642e69a7cfd1 X-Archives-Hash: c72c1622094dcbf8e7a13c7bbd637794 This is a multi-part message in MIME format. --nextPart17473435.5WZRyvrzyv Content-Type: multipart/alternative; boundary="nextPart10143287.L8ug28u51p" Content-Transfer-Encoding: 7Bit This is a multi-part message in MIME format. --nextPart10143287.L8ug28u51p Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="UTF-8" Hello all, the truth is that I should have separated this email into two threads. However they have a relation, so let's discuss them in one place. The first: While is not mandatory begin an eqawarn with "QA Notice" and thus there are no rules about that I think it helps while grepping on build logs. All of us agree that is should be fixed in the eqawarn function, but it won't happen soon. So, if you are interested to get bug reports (at least from me) about unprefixed eqawarn, please add the usual "QA Notice:" prefix as we did in https://bugs.gentoo.org/728046[1] If you think that add "QA Notice:" will break existing scripts or so, please let us know. I'm adding as attachment the list of eqawarn that miss the 'QA Notice' prefix. The second: By filing bugs for eqawarn/qa notice, I have been pointed out, for some class of issues, that a bugreport is not needed. At this point, since bugs can be filed by everyone, I think is better introduce something that make clear that we do not expect a bugreport about a particular issue. An example is here: eqawarn "QA (Dev) Notice: ........" eqawarn "......" eqawarn "......" eqawarn "Please remember that QA (Dev) Notice do not deserve a bugreport" In other words a "QA (Dev) Notice:" is supposed to be one or more of the following: - something useful for maintainer at the bump time - something that is not worth for a bugreport - something that is not worth for an immediate fix - something that will disappear soon with a new version of a package Two side notes: 1) I have tried to introduce that on irc in #gentoo-qa to get a feedback about that, but I have not received a response, so this should be the proper place. So this is NOT to point the finger to people that did not answer, but it's just to say that I'm not expecting something like: "why you didn't discuss this with us first" from qa ;) 2) @ionen already pointed out to me that configure.in qa notice in autotools.eclass no dot deserve a qa notice. What do you think? Agostino -------- [1] https://bugs.gentoo.org/728046 --nextPart10143287.L8ug28u51p Content-Transfer-Encoding: 7Bit Content-Type: text/html; charset="UTF-8"

Hello all,


the truth is that I should have separated this email into two threads. However they have a relation, so let's discuss them in one place.



The first:


While is not mandatory begin an eqawarn with "QA Notice" and thus there are no rules about that I think it helps while grepping on build logs.

All of us agree that is should be fixed in the eqawarn function, but it won't happen soon.

So, if you are interested to get bug reports (at least from me) about unprefixed eqawarn, please add the usual "QA Notice:" prefix as we did in https://bugs.gentoo.org/728046

If you think that add "QA Notice:" will break existing scripts or so, please let us know.


I'm adding as attachment the list of eqawarn that miss the 'QA Notice' prefix.



The second:


By filing bugs for eqawarn/qa notice, I have been pointed out, for some class of issues, that a bugreport is not needed.


At this point, since bugs can be filed by everyone, I think is better introduce something that make clear that we do not expect a bugreport about a particular issue.


An example is here:


eqawarn "QA (Dev) Notice: ........"

eqawarn "......"

eqawarn "......"

eqawarn "Please remember that QA (Dev) Notice do not deserve a bugreport"


In other words a "QA (Dev) Notice:" is supposed to be one or more of the following:

- something useful for maintainer at the bump time

- something that is not worth for a bugreport

- something that is not worth for an immediate fix

- something that will disappear soon with a new version of a package



Two side notes:

1)

I have tried to introduce that on irc in #gentoo-qa to get a feedback about that, but I have not received a response, so this should be the proper place.

So this is NOT to point the finger to people that did not answer, but it's just to say that I'm not expecting something like: "why you didn't discuss this with us first" from qa ;)



2)

@ionen already pointed out to me that configure.in qa notice in autotools.eclass no dot deserve a qa notice.



What do you think?


Agostino

--nextPart10143287.L8ug28u51p-- --nextPart17473435.5WZRyvrzyv Content-Disposition: attachment; filename="eqawarn.txt" Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="x-UTF_8J"; name="eqawarn.txt" autotools.eclass: eqawarn "This package has a configure.in file which has long been deprecated. Please" eqawarn "Running '${1}' in ${EBUILD_PHASE_FUNC} phase" chromium-2.eclass: eqawarn "L10N warning: no .pak file for ${lang} (${lang}.pak not found)" eqawarn "L10N warning: no ${lang} in LANGS" distutils-r1.eclass: eqawarn "Non-PEP517 builds are deprecated for ebuilds using plain distutils." eqawarn "${build_backend} backend is deprecated. Please see:" eqawarn "Python extension modules (*$(get_modname)) found installed. Please set:" ecm.eclass: eqawarn "Build system was modified by ECM_TEST=forceoptional-recursive." flag-o-matic.eclass: eqawarn "Appending an empty argument to LIBS is invalid! Skipping." eqawarn "Appending non-library to LIBS (${flag}); Other linker flags should be passed via LDFLAGS" go-module.eclass: eqawarn "This ebuild uses EGO_SUM which is deprecated" gstreamer-meson.eclass: eqawarn "QA: IUSE=orc is missing while plugin supports it" eqawarn "QA: IUSE=orc is present while plugin does not support it" eqawarn "QA: IUSE=introspection is missing while plugin supports it" eqawarn "QA: IUSE=introspection is present while plugin does not support it" haskell-cabal.eclass: eqawarn "No Setup.lhs or Setup.hs found. Either add Setup.hs to package or call cabal-mksetup from ebuild" java-pkg-simple.eclass: eqawarn "Need at least JDK 9 to compile module-info.java in src_compile." java-utils-2.eclass: eqawarn "java-pkg_ensure-dep: ${dev_error}" eqawarn "java-pkg_ensure-dep: ${dev_error}" python-r1.eclass: eqawarn "python_foreach_impl has been called directly while using distutils-r1." python-utils-r1.eclass: eqawarn "The directory ${fn} occludes package installed for ${EPYTHON}." eqawarn " ${l}" eqawarn "For more information on occluded packages, please see:" rpm.eclass: eqawarn 'do not use ${DISTDIR} with rpm_unpack -- it is added for you' eqawarn 'do not use full paths with rpm_unpack -- use ./ paths instead' ruby-fakegem.eclass: eqawarn "${CATEGORY}/${PF}: Unknown test recipe '${RUBY_FAKEGEM_RECIPE_TEST}' specified, using 'none'" eqawarn "Generating generic fallback gemspec *without* dependencies" ruby-ng.eclass: eqawarn "RUBY_PATCHES is no longer supported, use PATCHES instead" eqawarn "Missing test dependency dev-ruby/rspec" toolchain.eclass: eqawarn "Snapshot release with pre-generated info pages found!" wxwidgets.eclass: eqawarn "This package relies on the deprecated GTK 2 slot, which will go away soon (https://bugs.gentoo.org/618642)" --nextPart17473435.5WZRyvrzyv--