[gentoo-user] Re: listing portage/overlay packages by dev ?

2016-06-02 Thread James
Michael Orlitzky  gentoo.org> writes:


> You can script something smarter. I'm attaching a python script called
> maintainer.py. You can use find/xargs to search by maintainer email:

>   $ find $REPOS/gentoo.git/ -type f -name 'metadata.xml' | \
> xargs ./maintainer.py mjo  gentoo.org
>   mail-filter/pypolicyd-spf


OK, let me play with this a while...

> Attachment (maintainer.py): text/x-python, 587 bytes

James









Re: [gentoo-user] Re: listing portage/overlay packages by dev ?

2016-06-02 Thread Michael Orlitzky
On 06/02/2016 04:29 PM, James wrote:
> 
> Hm. I currently have to add about 6 lines manually for each overlay
> into repos.conf/overlays::
> 
> ...
> 
> So your saying do this for every overlay?
> 
> Surely there is just a way to concatenate metadata (or info) from overlays
> into a single file (periodically) to perform this parse? Or am I just being
> 'dense' here and not understanding what you suggest? 
> 
> I understand that what you are saying  will work, but installing every
> overlay to search out package listings and descriptions seems awkward;
> like there ought to be a better (lightweight) way to do this?
> 

I didn't say it was a good idea, just that it would work =)

You can script something smarter. I'm attaching a python script called
maintainer.py. You can use find/xargs to search by maintainer email:

  $ find $REPOS/gentoo.git/ -type f -name 'metadata.xml' | \
xargs ./maintainer.py m...@gentoo.org
  mail-filter/pypolicyd-spf
  dev-ruby/rbpdf
  dev-ruby/spreadsheet
  dev-ruby/vcard
  dev-ruby/ruby-ole
  sys-process/xjobs
  app-laptop/hdapsd
  app-text/XML-Schema-learner
  dev-perl/Net-IPv4Addr
  dev-perl/Monitoring-Plugin
  net-dns/djbdns
  net-dns/rbldnsd
  sys-apps/apply-default-acl
  www-apache/mpm_itk
  net-mail/amavis-logwatch
  net-mail/mailshears
  net-mail/postfix-logwatch
  dev-lang/coffee-script
  dev-php/php-redmine-api
  dev-php/PHPMailer
  dev-php/recaptcha
  net-analyzer/nagios-check_mysql_health
  net-analyzer/nagios
  net-analyzer/monitoring-plugins
  net-analyzer/nagios-core
  net-analyzer/nagios-check_openvpn-simple
  net-analyzer/nagios-plugins
  net-analyzer/nagios-check_rbl
  net-misc/haeredes
  net-misc/hath
  app-backup/untangle-https-backup
  app-emacs/multi-term
  sci-mathematics/rw
  app-antivirus/clamav-unofficial-sigs

Apparently I maintain all of those things.

> And then there is the problem::
> 
> Package net-analyzer/wpscan-2.9.1 is missing metadata.xml
> (when not installed)

metadata.xml is required for every package, somebody screwed up. In any
case, without it, you have no idea who the maintainer is, so you can
ignore that package.

#!/usr/bin/python3

from sys import argv

if len(argv) < 3:
print("Usage:", argv[0], "", "")
raise SystemExit

from os.path import abspath, dirname, split
import xml.etree.ElementTree as ET

for fileidx in range(2,len(argv)):
tree = ET.parse(argv[fileidx])
root = tree.getroot()

for maintainer in root.iter("maintainer"):
if maintainer[0].text == argv[1]:
# Found a winner.
d = dirname(abspath(argv[fileidx]))
(h1,t1) = split(d)
(_,t2) = split(h1)
print(t2 + "/" + t1)



[gentoo-user] Re: listing portage/overlay packages by dev ?

2016-06-02 Thread James
Michael Orlitzky  gentoo.org> writes:


> >> $ portageq --maintainer-email=idl0r  gentoo.org

> > Now I shall research how to code something up for non-installed
> > portage packages and the overlay collections those listings
> > are really what I'm after.

> It already works for non-installed packages, 

So it does... missed that, but now I see


> so "all" you should have to do is clone every overlay and put them 
> in /etc/portage/repos.conf before running portageq.


Hm. I currently have to add about 6 lines manually for each overlay
into repos.conf/overlays::

last entry::

[pentoo]
priority = 50
location = /var/lib/layman/pentoo
sync-type = git
sync-uri = git://anongit.gentoo.org/proj/pentoo.git
auto-sync = yes

So your saying do this for every overlay?

Surely there is just a way to concatenate metadata (or info) from overlays
into a single file (periodically) to perform this parse? Or am I just being
'dense' here and not understanding what you suggest? 

I understand that what you are saying  will work, but installing every
overlay to search out package listings and descriptions seems awkward;
like there ought to be a better (lightweight) way to do this?

And then there is the problem::

Package net-analyzer/wpscan-2.9.1 is missing metadata.xml
(when not installed)

But this (description) info is visable via zugania::
https://gpo.zugaina.org/Search?search=wpscan

After installing wpscan, metadata is still not available.
but the description is via 'eix wpscan' is available.

James







Re: [gentoo-user] Re: listing portage/overlay packages by dev ?

2016-06-02 Thread Michael Orlitzky
On 06/02/2016 02:48 PM, James wrote:
> Michael Orlitzky  gentoo.org> writes:
> 
> 
>> $ portageq --maintainer-email=idl0r  gentoo.org
> 
> VERY COOL!
> 
> Now I shall research how to code something up for non-installed
> portage packages and the overlay collections those listings
> are really what I'm after.
> 

It already works for non-installed packages, so "all" you should have to
do is clone every overlay and put them in /etc/portage/repos.conf before
running portageq.





[gentoo-user] Re: listing portage/overlay packages by dev ?

2016-06-02 Thread James
Michael Orlitzky  gentoo.org> writes:


> $ portageq --maintainer-email=idl0r  gentoo.org

VERY COOL!

Now I shall research how to code something up for non-installed
portage packages and the overlay collections those listings
are really what I'm after.

THX!

James









Re: [gentoo-user] Re: listing portage/overlay packages by dev ?

2016-06-02 Thread Michael Orlitzky
On 06/02/2016 02:12 PM, James wrote:
> Michael Orlitzky  gentoo.org> writes:
> 
> 
>> portageq --maintainer-email can do it, but it only checks your installed
>> overlays.
> 
> I have htop install, and 'idl0r' is the maintainer
> 
> 'portageq --maintainer-email   idl0r' 
> 
> comes back empty as with any number of dev-handles listed in metadata for
> installed packages. when ran as root. It throws errors when run as a user.
> 
> correct syntax ??
> 

maintainer-email, not maintainer-handle =P

$ portageq --maintainer-email=id...@gentoo.org
app-forensics/lynis-1.6.4
app-vim/gitolite-syntax-20111225
dev-db/maatkit-7540-r1
dev-db/percona-toolkit-2.2.11
dev-db/xtrabackup-bin-2.2.5
dev-vcs/colorsvn-0.3.2-r2
dev-vcs/gitolite-2.3.1-r1
dev-vcs/gitolite-3.6
dev-vcs/gitolite-3.6.3
dev-vcs/gitolite-gentoo-2.3.1-r1
dev-vcs/topgit-0.9
net-analyzer/nagios-check_ipmi_sensor-3.1
net-analyzer/nagios-check_ipmi_sensor-3.2
net-analyzer/nagstamon-1.0.1
net-dns/bind-9.10.3_p2
net-dns/bind-9.10.3_p4
net-dns/bind-tools-9.10.1_p1
net-dns/bind-tools-9.10.3_p2
net-dns/bind-tools-9.10.3_p4
net-misc/cfengine-2.2.10-r4
net-misc/cfengine-3.3.9
net-proxy/haproxy-1.5.14
sys-apps/flashrom-0.9.6.1
sys-apps/flashrom-0.9.7
sys-process/htop-1.0.3
sys-process/incron-0.5.10
sys-process/incron-0.5.10-r1
www-apache/mod_perl-2.0.8
www-apache/mod_perl-2.0.10_pre201601
www-servers/varnish-3.0.7
www-servers/varnish-4.0.3




[gentoo-user] Re: listing portage/overlay packages by dev ?

2016-06-02 Thread James
Michael Orlitzky  gentoo.org> writes:


> portageq --maintainer-email can do it, but it only checks your installed
> overlays.

I have htop install, and 'idl0r' is the maintainer

'portageq --maintainer-email   idl0r' 

comes back empty as with any number of dev-handles listed in metadata for
installed packages. when ran as root. It throws errors when run as a user.

correct syntax ??

portageq is not documented in the man page for portage ?
is portageq -h the extent of available docs? 

I did find this scant info in the wiki::
https://wiki.gentoo.org/wiki/Portage#portageq

and a listing of 'portageq -h' and a wee bit more here::
https://wiki.gentoo.org/wiki/Portageq


I was hoping for a separate code/script I could hack on.
I doubt seriously, (my) hacks to portage are going to be welcome...

Anyway that's a neat tool and close, but I'm not sure how to
wise patching portage is to extend the features. A non-core
package would be fine. I'll look at the portageq code on github
and see if I can make a stand alone script or q-applet to
extend this metadata query. Packages I already have installed
are not the issue. What I want is a quick and convenient tool
to 'periscope' into all the gentoo published work a dev might
have so as to better understand the focus(es) of their work
and common interests.


With blueness, it's dirt simple::

https://wiki.gentoo.org/wiki/User:Blueness && 
https://dev.gentoo.org/~blueness/


But this basic information would be very nice if a tool parsed out the
basics so each and every dev does not have to do this. I'm trying to
'not reinvent the wheel' but it is a great help, particularly for the
product devs that are into the same sorts of things as I am. (ultrabug) for
example.

thx,
James





Re: [gentoo-user] Re: listing portage/overlay packages by dev ?

2016-06-02 Thread Michael Orlitzky
On 06/02/2016 12:37 PM, James wrote:
> 
> I was actually hoping for something much simpler and always as current as the 
> last sync of protage and the corresponding overlays (layman syntax). Perhaps
> an option I missed in the 'q' applets (portage-utils) or gentoolkit ?
> 

portageq --maintainer-email can do it, but it only checks your installed
overlays.




Re: [gentoo-user] Re: listing portage/overlay packages by dev ?

2016-06-02 Thread ng0
On 2016-06-02(04:37:00+), James wrote:
> ng0  n0.is> writes:
>
> > > Is there a consistent semantic to at least list all of the portage tree
> > > packages there are listed on as maintainer?
> > > Is there a universal, slick way to list the overlay packages they are
> > > working on (github)?
>
> > What about checking out the portage repo and doing the native git search
> > in there via log?
>
> I was actually hoping for something much simpler and always as current as the
> last sync of protage and the corresponding overlays (layman syntax). Perhaps
> an option I missed in the 'q' applets (portage-utils) or gentoolkit ?
>
>
> If nothing exist, I'd consider writing some C (q applets) or python
> (gentoolkit) code to perform this searching task. It wont be comprehensive,
> but it should work on both the protage tree and the official overlays.
>
>
> Thoughts and ideas are welcome.
>
>
> James

I'm not sure if it works like this.
You have the metadata.xml files and Changelog files, as far as I know those
are the only name -> package relations you can get when not using git.

I might be wrong, so a tool like this could be useful if one needs it.

--
♥Ⓐ ng0
4096R/13212A27975AF07677A29F7002A296150C201823


signature.asc
Description: Digital signature


[gentoo-user] Re: listing portage/overlay packages by dev ?

2016-06-02 Thread James
ng0  n0.is> writes:

> > Is there a consistent semantic to at least list all of the portage tree 
> > packages there are listed on as maintainer?
> > Is there a universal, slick way to list the overlay packages they are
> > working on (github)?

> What about checking out the portage repo and doing the native git search 
> in there via log?

I was actually hoping for something much simpler and always as current as the 
last sync of protage and the corresponding overlays (layman syntax). Perhaps
an option I missed in the 'q' applets (portage-utils) or gentoolkit ?


If nothing exist, I'd consider writing some C (q applets) or python
(gentoolkit) code to perform this searching task. It wont be comprehensive,
but it should work on both the protage tree and the official overlays.


Thoughts and ideas are welcome.


James