public inbox for cygwin-apps@cygwin.com
 help / color / mirror / Atom feed
From: Jon Turney <jon.turney@dronecode.org.uk>
To: "cygwin-apps@cygwin.com" <cygwin-apps@cygwin.com>
Subject: Re: [PATCH] setup spews too many messages
Date: Sat, 04 Aug 2018 14:32:00 -0000	[thread overview]
Message-ID: <e20367f9-c6ee-3fc8-9e66-ffaa42987047@dronecode.org.uk> (raw)
In-Reply-To: <87h8kfb3wh.fsf@Rainer.invalid>

[-- Attachment #1: Type: text/plain, Size: 807 bytes --]

On 31/07/2018 20:29, Achim Gratz wrote:
> fix excessive message spewage when package vendor is something other than "cygwin"
> 
> Installed packages are getting coerced to vendor "cygwin", so there will
> be warnings if the vendor string of the single repo is something other
> than that.  Use "@System" like zypper for these and suppress the warning
> if it would concern an installed package.

Yeah, this is a bit unfortunate.

Ideally we'd be remembering the vendor (along with other information we 
currently guess) for installed packages.

I'm not sure about fixing it this way, though, as it will mean that 
normally (when the repo label is 'cygwin') all upgraded packages will be 
shown as vendorchanged in the full log (or when using -v)

How about the attached, which should have the same effect?


[-- Attachment #2: 0001-Fix-message-spam-when-package-vendor-is-something-ot.patch --]
[-- Type: text/plain, Size: 1681 bytes --]

From 3103d94026056f0ba07548dab8ff9f04f4dccb70 Mon Sep 17 00:00:00 2001
From: Achim Gratz <Stromeko@Stromeko.DE>
Date: Tue, 31 Jul 2018 21:29:02 +0200
Subject: [PATCH setup] Fix message spam when package vendor is something other
 than "cygwin"

Installed packages are getting coerced to vendor "cygwin", so there will be
warnings if the vendor string of the single repo is something other than
that.
---
 package_meta.cc | 15 +++++++++++----
 1 file changed, 11 insertions(+), 4 deletions(-)

diff --git a/package_meta.cc b/package_meta.cc
index f765baf..a7f4cfd 100644
--- a/package_meta.cc
+++ b/package_meta.cc
@@ -183,10 +183,17 @@ packagemeta::add_version (const SolverPool::addPackageData &inpkgdata)
           /* Otherwise... if we had a way to set repo priorities, that could be
              used to control which packageversion the solver picks. For the
              moment, just warn that you might not be getting what you think you
-             should... */
-          Log (LOG_PLAIN) << "Version " << pkgdata.version << " of package " <<
-            name << " is present in releases labelled " << pkgdata.vendor <<
-            " and " << i->Vendor() << endLog;
+             should...
+
+             (suppress this for installed packages, as we are only guessing the
+             vendor, currently)
+          */
+          if (pkgdata.reponame != "_installed")
+            {
+              Log (LOG_PLAIN) << "Version " << pkgdata.version << " of package " <<
+                name << " is present in releases labelled " << pkgdata.vendor <<
+                " and " << i->Vendor() << endLog;
+            }
         }
 
       versions.erase(i);
-- 
2.17.0


  reply	other threads:[~2018-08-04 14:32 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-31 19:29 Achim Gratz
2018-08-04 14:32 ` Jon Turney [this message]
2018-08-04 18:55   ` Achim Gratz

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=e20367f9-c6ee-3fc8-9e66-ffaa42987047@dronecode.org.uk \
    --to=jon.turney@dronecode.org.uk \
    --cc=cygwin-apps@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).