Why won't you stop building dev-libs/protobuf-2.3.0-r4?

[Chris Sosa]

So I'm working on update_engine which depends on protobuf -- but ever
since the Python 2.7 upgrade, build_packages won't stop trying to
re-build protobuf every time I run build_packages. Am I doing
something wrong?

-Sosa

[Mike Frysinger]

show the output from:
ls -d /usr/local/lib64/python*/*
qfile -v /usr/local/lib64/python*
-mike

> --
> --
> Chromium OS Developers mailing list: chromiu...@chromium.org
> View archives, change email options, or unsubscribe:
> http://groups.google.com/a/chromium.org/group/chromium-os-dev?hl=en
>
>
>

[Chris Sosa]

sosa@sosa ~/trunk/src/scripts $ ls -d /usr/local/lib64/python*/*
/usr/local/lib64/python2.6/site-packages
/usr/local/lib64/python2.7/site-packages

sosa@sosa ~/trunk/src/scripts $ qfile -v /usr/local/lib64/python*
dev-libs/protobuf-2.3.0-r4 (/usr/local/lib64/python2.7)

[Mike Frysinger]

what all is in /usr/local/lib64/python2.6/site-packages ?
ls -R /usr/local/lib64/python2.6/site-packages

most likely you can `rm -rf` it
-mike

[Chris Sosa]

Argh, yeah I had some leftover pyc files in there that weren't
removed. However, build_packages is still rebuilding that package:

sosa@sosa ~/trunk/src/scripts $ ls -d /usr/local/lib64/python*/*

/usr/local/lib64/python2.7/site-packages

sosa@sosa ~/trunk/src/scripts $ qfile -v /usr/local/lib64/python*
dev-libs/protobuf-2.3.0-r4 (/usr/local/lib64/python2.7)

Log:
* Starting Python Updater...
* Main active version of Python: 2.7
* Active version of Python 2: 2.7
* Active version of Python 3: (None)
* Globally supported Python ABIs in installed repositories:
* chromiumos: 2.4 2.5 2.6 2.7 3.1 3.2
2.5-jython 2.7-pypy-1.5
* portage-stable: 2.4 2.5 2.6 2.7 3.1 3.2
2.5-jython 2.7-pypy-1.5
* x-crossdev: 2.4 2.5 2.6 2.7 3.1 3.2
2.5-jython 2.7-pypy-1.5
* No packages need to be reinstalled.
Starting fast-emerge.
Building package dev-libs/protobuf on root
Calculating deps...
Deps calculated in 0m0.6s
[ebuild R ] dev-libs/protobuf-2.3.0-r4
Pending 0/1, Fetching 1/1, [Time 0m1.0s Load 0.16 0.25 0.24]

[Mike Frysinger]

i can't explain why it keeps retrying protobuf. try running:
python-updater -p -v -v -v -v
-mike

[Hung-Te Lin]

Any luck? I'm seeing exactly the same issue.

 * Starting Python Updater...

 * Main active version of Python:    2.7

 * Active version of Python 2:       2.7

 * Active version of Python 3:       (None)

 * Globally supported Python ABIs in installed repositories:

 *   chromeos-overlay:               2.4 2.5 2.6 2.7 3.1 3.2 2.5-jython 2.7-pypy-1.5

 *   chromiumos:                     2.4 2.5 2.6 2.7 3.1 3.2 2.5-jython 2.7-pypy-1.5

 *   portage-stable:                 2.4 2.5 2.6 2.7 3.1 3.2 2.5-jython 2.7-pypy-1.5

 *   x-crossdev:                     2.4 2.5 2.6 2.7 3.1 3.2 2.5-jython 2.7-pypy-1.5

 * Check "manual" enabled.

 * Check "need_rebuild" enabled.

 * Check "pylibdir" enabled.

 * Check "PYTHON_ABIS" enabled.

 * Check "shared_linking" enabled.

 * Check "static_linking" enabled.

 * Checking app-admin/eselect-1.3.1:0

...

 * Checking dev-cpp/gflags-1.2:0

 *     Requested ABIs:          "2.7"

 *     Restricted ABIs:         "3.*"

 *     Previously enabled ABIs: "2.7"

 *     Newly enabled ABIs:      "2.7"

... 

 * Checking x11-proto/xproto-7.0.23-r1:0

 * No packages need to be reinstalled.

[1]+  Done                    sudo python-updater -p -v -v -v -v > py.log 2>&1

But every time I start build_packages it will still stuck in Python updater for a long time...

[Mike Frysinger]

/me looks for the py.log attachment

-mike

[Hung-Te Lin]

py.log attached.

BTW, here's the output when I do build_packages:

 * Starting Python Updater...

 * Main active version of Python:    2.7

 * Active version of Python 2:       2.7

 * Active version of Python 3:       (None)

 * Globally supported Python ABIs in installed repositories:

 *   chromeos-overlay:               2.4 2.5 2.6 2.7 3.1 3.2 2.5-jython 2.7-pypy-1.5

 *   chromiumos:                     2.4 2.5 2.6 2.7 3.1 3.2 2.5-jython 2.7-pypy-1.5

 *   portage-stable:                 2.4 2.5 2.6 2.7 3.1 3.2 2.5-jython 2.7-pypy-1.5

 *   x-crossdev:                     2.4 2.5 2.6 2.7 3.1 3.2 2.5-jython 2.7-pypy-1.5

 * No packages need to be reinstalled.

Starting fast-emerge.

 Building package dev-libs/protobuf on root

Calculating deps...

Deps calculated in 0m0.6s

[ebuild   R    ] dev-libs/protobuf-2.3.0-r4 

And it takes 110 seconds from "Starting Python Updater" to "No packages need to be reinstalled".

If I try to use top/pstree, I can see "python-updater" instances running.

[Mike Frysinger]

ok, you most likely have stale stuff in /usr/lib64/python2.6/.  that is what triggers python-updater to get run, and the protobuf runs due to other logic (but is contingent upon the earlier check).

what does this show:

ls -R /usr/lib64/python2.6/

-mike

[Chris Sosa]

That's likely totally it:

/usr/lib64/python2.6/:
site-packages

/usr/lib64/python2.6/site-packages:
update_payload

/usr/lib64/python2.6/site-packages/update_payload:
applier.pyc block_tracer.pyc checker.pyc common.pyc error.pyc
format_utils.pyc histogram.pyc __init__.pyc payload.pyc
update_metadata_pb2.pyc

Let me rm -rf these things.

[Chris Sosa]

Worked like a charm. I am happy again.

[Mike Frysinger]

you are easy to please ;)

i'm going to guess that local testing generated those .pyc files.  i'll post a CL that trims .pyc and empty dirs.

-mike

[Hung-Te Lin]

Mine: caused by servo, and the python updater goes away after python2.6 folder being removed :)

P.S: Maybe we can print something on screen like "/usr/lib64/python2.6 detected, running python-updater to upgrade - if you keep seeing this message, try to do 

 find /usr/lib64/python2.6  -name "*.pyc" -delete && find /usr/lib64/python2.6 -type d -exec rmdir {} \;"

/usr/lib64/python2.6:

site-packages

/usr/lib64/python2.6/site-packages:

servo 

/usr/lib64/python2.6/site-packages/servo:

drv              ftdi_common.pyc  ftdii2c.pyc   ftdi_utils.pyc  servod.pyc            servo_server.pyc

dut_control.pyc  ftdigpio.pyc     ftdiuart.pyc  __init__.pyc    servo_interfaces.pyc  system_config.pyc

/usr/lib64/python2.6/site-packages/servo/drv:

daisy_ec.pyc  gpio.pyc       i2c_reg.pyc  __init__.pyc  parrot_ec.pyc  pca9537.pyc  pty_driver.pyc  uart.pyc

ec.pyc        hw_driver.pyc  ina219.pyc   ltc1663.pyc   pca9500.pyc    pca9546.pyc  tca6416.pyc

[Mike Frysinger]

the latest tree already deletes all pyc files and then delete all empty dirs. so if that's all your system had, then things should just work now.
-mike