public inbox for libabigail@sourceware.org
 help / color / mirror / Atom feed
From: "woodard at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: libabigail@sourceware.org
Subject: [Bug default/29332] fedabipkgdiff exits with 1 due to - "Could not find package"
Date: Mon, 03 Apr 2023 22:24:23 +0000	[thread overview]
Message-ID: <bug-29332-9487-CH1o4IJcql@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-29332-9487@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=29332

Ben Woodard <woodard at redhat dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
            Summary|fedabipkgdiff 3mux exits    |fedabipkgdiff exits with 1
                   |with an unexplained error   |due to - "Could not find
                   |                            |package"

--- Comment #5 from Ben Woodard <woodard at redhat dot com> ---
There are 4178 packages which seem to exhibit this problem.

The original problem with 3mux, absiel-cpp, and age seem to have gone away. The
fingerprint of this problem is:

$ sudo dnf info ziffy
[sudo] password for ben: 
Updating Subscription Management repositories.
Last metadata expiration check: 0:58:22 ago on Mon 03 Apr 2023 02:22:07 PM PDT.
Available Packages
Name         : ziffy
Version      : 0
Release      : 0.10.20220615git8413c32.fc37
Architecture : x86_64
Size         : 1.4 M
Source       :
golang-github-facebook-time-0-0.10.20220615git8413c32.fc37.src.rpm
Repository   : fedora
Summary      : CLI tool to triangulate switches that are not operating
correctly as PTP Transparent Clocks.
URL          : https://github.com/facebook/time
License      : ASL 2.0
Description  : CLI tool to triangulate datacenter switches that are not
operating correctly as PTP Transparent Clocks.
             : Ziffy sends PTP SYNC/DELAY_REQ packets between two hosts to get
data about the topology.
             : It supports sending packets from a range of source ports to
encourage hashing of
             : traffic over multiple paths. In case the hashing is done using
only destination IP and source IP, Ziffy can
             : target multiple IPs in the same /64 prefix as the destination.

$ fedabipkgdiff --self-compare -a --from fc37 ziffy
Cannot find package ziffy.
Command exited with non-zero status 1
0.12user 0.01system 0:00.58elapsed 23%CPU (0avgtext+0avgdata 38876maxresident)k
0inputs+0outputs (0major+6381minor)pagefaults 0swaps

so the problem seems to be with the interaction with the fedora build system.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

      parent reply	other threads:[~2023-04-03 22:24 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-07 18:14 [Bug default/29332] New: fedabipkgdiff 3mux exits with an error woodard at redhat dot com
2022-07-07 18:14 ` [Bug default/29332] " woodard at redhat dot com
2022-07-08 13:38 ` [Bug default/29332] fedabipkgdiff 3mux exits with an unexplained error woodard at redhat dot com
2022-07-09 18:58 ` woodard at redhat dot com
2022-07-09 19:16 ` woodard at redhat dot com
2022-07-09 19:35 ` woodard at redhat dot com
2022-07-09 20:11 ` woodard at redhat dot com
2023-04-03 22:24 ` woodard at redhat dot com [this message]

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=bug-29332-9487-CH1o4IJcql@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=libabigail@sourceware.org \
    /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).