tagging_pkg_debug_dump

> Updates:
>
> Trying to add pkg to our tag
>
>   $ brew add-pkg --owner=dfarrell rhos-10.0-odl-rhel-7-maven-imports
org.eclipse.jdt-org.eclipse.jdt.core-3.10.0-1
>   Adding 1 packages to tag rhos-10.0-odl-rhel-7-maven-imports
>   $ brew tag-build rhos-10.0-odl-rhel-7-maven-imports
org.eclipse.jdt-org.eclipse.jdt.core-3.10.0-1
>   TagError: Package org.eclipse.jdt-org.eclipse.jdt.core not in list for
rhos-10.0-odl-rhel-7-maven-imports

Not sure about this error, haven't encountered this stuff previously..
Best bet is ping Russell or Lon Hohberger (lon) on IRC and ask them for
help with this.

>
> Also trying without the -1 part
>
>   $ brew add-pkg --owner=dfarrell rhos-10.0-odl-rhel-7-maven-imports
org.eclipse.jdt-org.eclipse.jdt.core-3.10.0
>   Adding 1 packages to tag rhos-10.0-odl-rhel-7-maven-imports
>   $ brew tag-build rhos-10.0-odl-rhel-7-maven-imports
org.eclipse.jdt-org.eclipse.jdt.core-3.10.0-1
>   TagError: Package org.eclipse.jdt-org.eclipse.jdt.core not in list for
rhos-10.0-odl-rhel-7-maven-imports
>
> The package for the missing artifact shows when looking at the packages
on our tag
>
>   $ brew list-pkgs --tag=rhos-10.0-odl-rhel-7-maven-imports|grep jdt
>   org.eclipse.jdt-org.eclipse.jdt.core-3.10.0-1
rhos-10.0-odl-rhel-7-maven-imports                  dfarrell
>   org.eclipse.jdt-org.eclipse.jdt.core-3.10.0
rhos-10.0-odl-rhel-7-maven-imports                  dfarrell
>
> Tagging still fails in the same way
>
>   $ brew tag-build rhos-10.0-odl-rhel-7-maven-imports
org.eclipse.jdt-org.eclipse.jdt.core-3.10.0-1
>   TagError: Package org.eclipse.jdt-org.eclipse.jdt.core not in list for
rhos-10.0-odl-rhel-7-maven-imports
>
> Mead download and import script still fails in the same way
>
>   $ ./mead-download-and-import --owner dfarrell --tag
rhos-10.0-odl-rhel-7-maven-imports
org.eclipse.jdt:org.eclipse.jdt.core:jar:3.10.0
>   brew import-archive --create-build --type maven --type-info
/tmp/tmps1IuGn/org.eclipse.jdt.core-3.10.0.pom
org.eclipse.jdt-org.eclipse.jdt.core-3.10.0-1
/tmp/tmps1IuGn/org.eclipse.jdt.core-3.10.0-sources.jar
/tmp/tmps1IuGn/org.eclipse.jdt.core-3.10.0-javadoc.jar
>
> Wondering if a job needs to run to update something? Or maybe it's okay,
since it shows in list-pkgs?
> Will a new build detect it automagically or do we need a newRepo job to
get triggered somehow?
>
> Trying a new build
>
> https://brewweb.engineering.redhat.com/brew/taskinfo?taskID=12186803
>
>
> Daniel Farrell
> Software Engineer, Red Hat SDN Team
> https://wiki.opendaylight.org/view/user:dfarrell07
>
> ----- Original Message -----
> > On Thu, Dec 1, 2016 at 6:51 PM, Daniel Farrell <dfarrell@redhat.com>
wrote:
> >
> > > Trying to catch you before it's late, sorry for quick dump.
> > >
> > > Looking at a failing build and importing the resulting GAV is failing,
> > > just spitting out a command and exiting 1.
> > >
> > >   DEBUG util.py:257:  [ERROR] Failed to execute goal
> > > org.eclipse.xtend:xtend-maven-plugin:2.9.2:compile (default) on
project
> > > testutils: Execution default of goal
> > > org.eclipse.xtend:xtend-maven-plugin:2.9.2:compile
> > > failed: Plugin org.eclipse.xtend:xtend-maven-plugin:2.9.2 or one of
its
> > > dependencies could not be resolved: Could not find artifact
> > > org.eclipse.jdt:org.eclipse.jdt.core:jar:3.10.0 in
> > > koji-task-12184506-repo (
http://download.eng.bos.redhat.com/brewroot/work/
> > > tasks/4506/12184506)
> > >
> > > http://download-node-02.eng.bos.redhat.com/brewroot/work/
> > > tasks/4533/12184533/root.log
> > >
> > >   $ ./mead-download-and-import --owner dfarrell --tag
> > > rhos-10.0-odl-rhel-7-maven-imports org.eclipse.jdt:org.eclipse.
> > > jdt.core:jar:3.10.0
> > >   brew import-archive --create-build --type maven --type-info
> > > /tmp/tmpfex9Ws/org.eclipse.jdt.core-3.10.0.pom
> > > org.eclipse.jdt-org.eclipse.jdt.core-3.10.0-1
> > > /tmp/tmpfex9Ws/org.eclipse.jdt.core-3.10.0-sources.jar
> > > /tmp/tmpfex9Ws/org.eclipse.jdt.core-3.10.0-javadoc.jar
> > >   # Exit status 1
> > >
> >
> > I never came across this,
> >
> > but basically that script is downloading and importing the artifacts so
> > you could generally download them manually and import them with another
> > script that it's calling.
> > I;m not sure of the exact call to make but the information is
available in
> > mojo.
> >
> >
> > > Nothing is imported:
> > >
> > >   $ brew list-tagged
> > >
> > > rhos-10.0-odl-rhel-7-maven-imports|grep jdt
> > >   # Nothing
> > >
> > > Trying some other similar commands, still fails for jdt.core
> > >
> > >   $ ./mead-download-and-import --owner dfarrell --tag
> > > rhos-10.0-odl-rhel-7-maven-imports org.eclipse.jdt:org.eclipse.
> > > jdt.core:javadoc:3.10.0
> > >   brew import-archive --create-build --type maven --type-info
> > > /tmp/tmpmelsO7/org.eclipse.jdt.core-3.10.0.pom
> > > org.eclipse.jdt-org.eclipse.jdt.core-3.10.0-1
> > > /tmp/tmpmelsO7/org.eclipse.jdt.core-3.10.0-sources.jar
> > > /tmp/tmpmelsO7/org.eclipse.jdt.core-3.10.0-javadoc.jar
> > >
> > > But can import other artifacts (although this was already imported, so
> > > maybe not exactly the same)
> > >
> > >   $ ./mead-download-and-import --owner dfarrell --tag
> > > rhos-10.0-odl-rhel-7-maven-imports org.eclipse.xtext:org.eclipse.
> > > xtext:jar:2.9.2
> > >   Imported and tagged org.eclipse.xtext-org.eclipse.xtext-2.9.2-1
> > >
> > > I see the artifact in the catch-all MEAD tag
> > >
> > >   [~/rh-mead-scripts]$ brew list-tagged mead-import-maven-all|grep
> > > org.eclipse.jdt.core
> > >
> > >
> > > org.eclipse.jdt-org.eclipse.jdt.core-3.10.0-1  mead-import-maven-all
> > > pgallagh
> > >
> >
> > In this case it's not actually necessary to download nor import it,
what
> > the script would do (if it had worked) is just tag it to your tag.
> > Prehaps you can utilize that and try do a 'brew tag-build
> > org.eclipse.jdt-org.eclipse.jdt.core-3.10.0-1 --tag
> > rhos-10.0-odl-rhel-7-maven-imports'
> >
> > or something of this sort?
> >
> >
> > >
> > > Daniel Farrell
> > > Software Engineer, Red Hat SDN Team
> > > https://wiki.opendaylight.org/view/user:dfarrell07