880806 - upload mozinfo, mozprocess, mozdevice, mozinstall versions to puppetagain for bug 877733

Status: RESOLVED FIXED

(Release Engineering :: General, defect)

Description

[Jeff Hammel]

Re https://bugzilla.mozilla.org/show_bug.cgi?id=877733#c26

The package versions bumped and mirrored to m-c (and possibly other)
should be uploaded to puppetagain.  While there's been discussion
about a script or modifying existing scripts to do so, ABICT the
manual file a bug and give URLs procedure is the process for the time being.

Comment 1

[Jeff Hammel]

https://pypi.python.org/packages/source/m/mozinfo/mozinfo-0.5.tar.gz#md5=1ad8ad87bf55ec90481f09e1b177e124
https://pypi.python.org/packages/source/m/mozprocess/mozprocess-0.11.tar.gz#md5=6430eef89ef458d9e2512e921ec6d37f
https://pypi.python.org/packages/source/m/mozInstall/mozInstall-1.6.tar.gz#md5=c36e8c1f4d4dd38531c079ce14a43d7e
https://pypi.python.org/packages/source/m/mozdevice/mozdevice-0.26.tar.gz#md5=1ab3e89277975dbbae2fe73afb00ed21

Comment 2

[Jeff Hammel]

Not sure how to find an owner for this bug; it blocks bug 877733 abict

Comment 3

[Armen [:armenzg]]

[[e-mail]3 packages]$ ls -l mozdevice-0.26.tar.gz 
-rw-r--r-- 1 armenzg armenzg 43652 Jun  6 11:14 mozdevice-0.26.tar.gz
[[e-mail]3 packages]$ ls -l mozinfo-0.5.tar.gz 
-rw-r--r-- 1 armenzg armenzg 3639 Jun  3 10:44 mozinfo-0.5.tar.gz
[[e-mail]3 packages]$ ls -l mozInstall-1.6.tar.gz 
-rw-r--r-- 1 armenzg armenzg 4618 Jun  3 10:44 mozInstall-1.6.tar.gz
[[e-mail]3 packages]$ ls -l mozprocess-0.11.tar.gz 
-rw-r--r-- 1 armenzg armenzg 17712 Jun  3 10:44 mozprocess-0.11.tar.gz

Comment 4

[Jeff Hammel]

Thanks, Armen!

Comment 5

[Ryan VanderMeulen [:RyanVM]]

I think this may be what broke the b2g18 branches. See bug 881216.

Comment 6

[Armen [:armenzg]]

Should I be backing out those packages? or would that break something on mozilla-central?


FYI, every time you request packages to be deployed, buildduty of the week will take care of it.

Comment 7

[Joel Maher ( :jmaher ) (UTC -8)]

why would the b2g18 branch be picking up a different version of the package?  We have specific versions for a reason.

Comment 8

[Jonathan Griffin (:jgriffin)]

I've commented on bug 881216; the problem is that mozInstall 1.6 has been uploaded to puppetagain, which depends on mozfile >= 0.4, but mozfile 0.3 is the most recent package available there.  The fix, I think, is uploading the latest mozfile to puppetgain, assuming that won't break something else.

We're moving away from puppetagain for B2G tests on m-c, but we can't do that easily for mozilla-b2g18, so we're going to stick with puppetagain on that tree until it becomes obsolete (hopefully sooner than later).

Comment 9

[Jonathan Griffin (:jgriffin)]

Er, mozInstall depends on mozinfo >= 0.4, which depends on mozfile >= 0.6  Same solution, though.

Comment 10

[Jeff Hammel]

(In reply to Armen Zambrano G. [:armenzg] (Release Enginerring) from comment #6)
> Should I be backing out those packages? or would that break something on
> mozilla-central?
> 
> 
> FYI, every time you request packages to be deployed, buildduty of the week
> will take care of it.

It looks like everything is sorted out, ABICT, unless I missed something.  Is this the case Armen et al.?