[EPEL-devel] Re: Orphaned Packages in epel7 (2016-11-01)

[Christopher]

On Wed, Nov 2, 2016 at 3:23 PM Jason L Tibbitts III <tibbs(a)math.uh.edu&gt;
wrote:

>  >>>>> "C" == Christopher 
> <ctubbsii(a)fedoraproject.org&gt; writes:
>
>  C> Also, after taking a package, how does one check to see if all of its
>  C> dependencies are in a good state? (non-orphaned)
>
>  Get the list of dependencies (with repoquery or "dnf repoquery" or
>  inspection of the spec.  Then look them up in pkgdb.  You can do those
>  lookups from the command line if you like using pkdgb-cli:
>
>    pkgdb-cli acl python-keyring epel7
>
>  (the branch names are el5, el6 and epel7 for historical reasons)
>
>  Will show you the four current maintainers of python-keyring in EPEL7.
>  Or you can make an API call and handle the returned json as you wish, if
>  you want to write something.
>
>  C> Aside from these emails for passive notification, is there a way to
>  C> get a smaller, personalized report, like on pkgdb, about a specific
>  C> package's dependencies?
>
>  pkgdb doesn't track dependencies, so all you can do is ask it about the
>  status of a particular package.  You'll need to get the dependencies
>  from the package manager.
>
>  
That's unfortunate. These emails are a bit spammy, are not easily parsed,
and are hard to track. Not only is it hard to tell the difference between
notices sent directly to me, or sent to me via the mailing list, it also
seems impossible to get an immediate report of a newly acquired package.

It seems like it'd be useful for pkgdb (or some other system) to show the
active/orphan/retire status of a package and all its dependencies, on
demand, rather than wait for the next round of emails like this to see that
one of your critical dependencies just got retired.

Basically, I think we need a web UI for whatever system is currently
generating these emails.



>  C> Or a particular user's packages' dependencies?
>
>  That's just extracting from pkgdb the list of packages to which a user
>  has commit access (assuming commit access is what you want) and then
>  looking at that package in a loop.
>
>   - J<
>