Custom Query (894 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (52 - 54 of 894)

Ticket Resolution Summary Owner Reporter
#1105 fixed Ubuntu PPA packages for 10.04 are breaked desai https://www.google.com/accounts/o8/id?id=AItOawnFfCcdne2GWePPC4xyCfq5d-kFOs_qfYM
Description

New Ubuntu install:

apt-get install python-software-properties
add-apt-repository ppa:bcfg2/ppa
apt-get update
apt-get install bcfg2-server

It returns the following:
Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:

bcfg2-server: Depends: bcfg2 (= 1.2.0-3~lucid3) but it is not going to be installed

E: Broken packages

#1103 fixed RFE: Better logging from YUMng https://www.google.com/accounts/o8/id?id=AItOawnSjgovXZr-_V3vGkvMSR0pc5LDykRc1Nc https://www.google.com/accounts/o8/id?id=AItOawnSjgovXZr-_V3vGkvMSR0pc5LDykRc1Nc
Description

It appears that yum only logs to yum.log when called from the CLI, so operations performed by the Yum API (e.g., in YUMng) do not get logged to yum.log. Add stuff to YUMng.py to write to the yum logs when packages are updated/erased/installed/etc. It'd be really nice if we could use the code in yum in callback.py, but I'm not sure that'd be possible.

#1102 fixed Solaris build-chain broken desai Dan Foster <dan.foster@…>
Description

Hi,

There are are number of problems with the Makefile provided in solaris/ that prevents bcfg2 building on Solaris 10:

  • setup.py expects lib/<python-version>/site-packages/ to exist

No such file or directory: '/export/home/df3804/bcfg2-1.2.1/solaris/lib/python2.6/site-packages/test-easy-install-9272.pth'

The installation directory you specified (via --install-dir, --prefix, or
the distutils default setting) was:

    /export/home/df3804/bcfg2-1.2.1/solaris/lib/python2.6/site-packages/

This directory does not currently exist.  Please create it and try again, or
choose a different installation directory (using the -d or --install-dir
option).

  • setup.py expects lib/<python-version>/site-packages/ to be in $PYTHON_PATH
/usr/local/bin/python -E -c pass
TEST FAILED: /export/home/df3804/bcfg2-1.2.1/solaris/lib/python2.6/site-packages/ does NOT support .pth files
error: bad install directory or PYTHONPATH

You are attempting to install a package to a directory that is not
on PYTHONPATH and which Python does not read ".pth" files from.  The
installation directory you specified (via --install-dir, --prefix, or
the distutils default setting) was:

    /export/home/df3804/bcfg2-1.2.1/solaris/lib/python2.6/site-packages/

and your PYTHONPATH environment variable currently contains:

    ''

Here are some of your options for correcting the problem:

* You can choose a different installation directory, i.e., one that is
  on PYTHONPATH or supports .pth files

* You can add the installation directory to the PYTHONPATH environment
  variable.  (It must then also be on PYTHONPATH whenever you run
  Python and want to use the package(s) you are installing.)

* You can set up the installation directory to support ".pth" files by
  using one of the approaches described here:

  http://peak.telecommunity.com/EasyInstall.html#custom-installation-locations

Please make the appropriate changes for your system and try again.
  • setup.py generates an "extracted egg". i.e. lib/python2.6/site-packages/Bcfg2-1.2.1-py2.6.egg/{Bcfg2,share} instead of the more traditional lib/python2.6/site-packages/Bcfg2/ & share/
  • prototype.* contains an out-of-date list files to include in the package (e.g. lib/python2.6/site-packages/Bcfg2/Server/Plugins/Packages.py does not exist anymore).

It is unclear to me if an updated prototype.bcfg2 and prototype.bcfg2-server should be provided or if these should be generated dynamically. As a first attempt, I have produced gen-prototypes.sh that produces these dynamically. Although, this could be considered more dirty than updating the prototypes manually every release.

Attached to this ticket is the following:

  • Makefile - A replacement solaris/Makefile that solves the issues above and also changes the build prefix from $(PWD) to $(PWD)/build.
  • gen-prototypes.sh - A script to generate suitable prototype.* files.
Note: See TracQuery for help on using queries.