Re: [Discuss-gnuradio] Errors using PyBombs recipe for RFNoC setup

[Ethan Trewhitt]

I can take the blame for this one. On apt-based machines that have python-apt installed, the new cache (that I added in #391) handles requests from PyBOMBS concerning the installation state of apt-based packages. Whenever a package is installed, the cache was not updated (bug). As a result, any time PyBOMBS installed a new package, it would assume failure (because the cache said the package was still not installed) and transition to the next installation method. In some cases, this revealed issues in the alternative installation methods; in others, it meant you'd end up with both the package version and the source version, etc. at the same time.

The reason the workaround worked is because it forced the cache to be reloaded. PyBOMBS would move onto the next actually-missing package and fail again, or succeed in installing two copies, etc.

I committed a fix. I apologize for the goofup. https://github.com/gnuradio/pybombs/pull/399

Ethan

On Fri, Sep 23, 2016 at 5:44 PM, Martin Braun <address@hidden> wrote:

Hey Andrew,

sorry for the miserable experience -- not sure why apt-get would be
acting up so badly. Clearly, the point of pybombs is for new users not
to have this kind of trouble.

I'm still a bit surprised that this is happening on 14.04, which is
probably the most popular distro around here at this point in time, and
many people run pybombs on there without issues.

Cheers,
M

On 09/23/2016 12:17 PM, Andrew Lanez wrote:
> I finally got everything installed successfully after doing 30+ attempts
> (this is no exaggeration) of rm -rf rfnoc and pybombs prefix init
> ~/rfnoc -R rfnoc -a alias. I was getting wildly varying errors from
> packages not being found (though I could manually hit those websites and
> download the files) to compiling errors with make scripts. This was over
> my wired home network and my work's wireless enterprise network but not
> sure if I should blame those networks or the servers where these
> packages live.
>
> On Fri, Sep 23, 2016 at 8:47 AM, Anon Lister <address@hidden
> <mailto:address@hidden>> wrote:
>
>     It was WX that was mentioned as being deprecated. Sorry I don't have
>     much to offer for your issue tho, except that you should run the
>     pybombs command with -v (pybombs -v <whatever>. -vv works too for
>     very verbose output. At some point it's trying to fetch a QT
>     installer, but failing. I would try grabbing that URL by hand as a
>     start go make sure it's not an issue on your network. Then someone
>     here can try to reproduce, Incase QT changed something.
>
>
>     On Sep 23, 2016 11:29 AM, "Andrew Lanez" <address@hidden

>     <mailto:address@hidden>> wrote:
>
>         Here is that output again with more relevant info that I forgot
>         to copy over:
>
>         make[2]: Entering directory
>         `/home/switchlanez/rfnoc/src/pyqt4/qpy/QtCore'
>         g++ -c -m64 -pipe -fno-strict-aliasing -O2 -fPIC -Wall -W
>         -D_REENTRANT -DQT_NO_DEBUG -DQT_GUI_LIB -DQT_CORE_LIB
>         -DQT_SHARED -I/usr/share/qt4/mkspecs/linux-g++-64 -I.
>         -I/usr/include/qt4/QtCore -I/usr/include/qt4/QtGui
>         -I/usr/include/qt4 -I/usr/include/python2.7 -I../../QtCore -I.
>         -I. -o qpycore_chimera.o qpycore_chimera.cpp
>         qpycore_chimera.cpp: In member function ‘void Chimera::set_flag()’:
>         qpycore_chimera.cpp:376:50: error: ‘pyqt4ClassTypeDef’ has no
>         member named ‘qt4_flags’
>                  _is_flag = ((pyqt4ClassTypeDef *)_type)->qt4_flags & 0x01;
>                                                           ^
>         make[2]: *** [qpycore_chimera.o] Error 1
>         make[2]: Leaving directory
>         `/home/switchlanez/rfnoc/src/pyqt4/qpy/QtCore'
>         make[1]: *** [all] Error 2
>         make[1]: Leaving directory `/home/switchlanez/rfnoc/src/pyqt4/qpy'
>         make: *** [all] Error 2
>         PyBOMBS.Packager.source - ERROR - Build failed. See output above
>         for error messages.
>         PyBOMBS.Packager.source - ERROR - Problem occurred while
>         building package pyqt4:
>         Build failed.
>         PyBOMBS.install_manager - ERROR - Error installing package
>         pyqt4. Aborting.
>
>
>         I was at GNU Radio Conference last week and remember mention of
>         qt being deprecated. Could this be why?
>
>         On Fri, Sep 23, 2016 at 8:20 AM, Andrew Lanez

>         <address@hidden <mailto:address@hidden>> wrote:
>
>             Well, I wiped everything clearn and started from a fresh
>             image of Linux to remove any doubt (3rd time doing this).
>             This time I made sure to do sudo apt-get update liberally
>             before running pybombs prefix init ~/rfnoc -R rfnoc -a alias
>
>             The first time it showed boost failed to install even though
>             the Installation progress bar showed 100%.
>
>             I discovered that if I delete the ~/rfnoc directory I can
>             rerun pybombs prefix init ~/rfnoc -R rfnoc -a alias without
>             errors. So everytime I do that now I persistently get:
>
>             Processing triggers for libc-bin (2.19-0ubuntu6.9) ...
>             PyBOMBS.Fetcher.wget - ERROR - hostname 'download.qt.io
>             <http://download.qt.io>' doesn't match either of
>             '*.qt-project.org <http://qt-project.org>', 'qt-project.org
>             <http://qt-project.org>', 'www.qt-project.org
>             <http://www.qt-project.org>'
>             PyBOMBS.Packager.source - ERROR - Problem occurred while
>             building package qt4:
>             Unable to fetch recipe qt4
>             PyBOMBS.install_manager - ERROR - Error installing package
>             qt4. Aborting.
>
>
>             What can I do about this?
>
>
>             On Thu, Sep 22, 2016 at 9:16 PM, Andrew Lanez

>             <address@hidden <mailto:address@hidden>> wrote:
>
>                 New Linux user here, I don't mean to anger anyone with
>                 my naivete.
>
>                 I just ran sudo apt-get. That might fix the other
>                 non-showstopper errors earlier. But I am not sure where
>                 to start to address that last error which is the show
>                 stopper:
>
>                 checking for BASE_DEPENDENCIES... no
>                 configure: error: Package requirements (glib-2.0 >=
>                 2.25.10    atk >= 1.29.2    pango >= 1.20    cairo >=
>                 1.6    gdk-pixbuf-2.0 >= 2.21.0) were not met:
>
>                 No package 'atk' found
>                 No package 'pango' found
>                 No package 'cairo' found
>
>                 Consider adjusting the PKG_CONFIG_PATH environment
>                 variable if you
>                 installed software in a non-standard prefix.
>
>                 Alternatively, you may set the environment variables
>                 BASE_DEPENDENCIES_CFLAGS
>                 and BASE_DEPENDENCIES_LIBS to avoid the need to call
>                 pkg-config.
>                 See the pkg-config man page for more details.
>                 PyBOMBS.Packager.source - ERROR - Configuration failed
>                 after running at least twice.
>                 PyBOMBS.Packager.source - ERROR - Problem occurred while
>                 building package gtk2:
>                 Configuration failed
>                 PyBOMBS.install_manager - ERROR - Error installing
>                 package gtk2. Aborting.
>
>
>                 I tried running the same pybombs command and got:
>                 $ pybombs prefix init ~/rfnoc -R rfnoc -a alias
>                 PyBOMBS - INFO - PyBOMBS Version 2.2.0
>                 PyBOMBS.prefix - ERROR - Ignoring. A prefix already
>                 exists in `/home/switchlanez/rfnoc'
>
>                 So I took out what might be prefix-related stuff but
>                 these didn't work:
>                 $ pybombs -R rfnoc -a alias
>                 $ pybombs rfnoc -a alias
>                 $ pybombs rfnoc
>
>                 How do I properly rerun the pybombs script?
>
>
>
>
>         _______________________________________________
>         Discuss-gnuradio mailing list

>         address@hidden <mailto:address@hiddenorg>
>         https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
>         <https://lists.gnu.org/mailman/listinfo/discuss-gnuradio>

>
>
>
>
>
> _______________________________________________
> Discuss-gnuradio mailing list
> address@hidden
> https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
>


_______________________________________________
Discuss-gnuradio mailing list
address@hidden
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio