Custom Query (894 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (100 - 102 of 894)

Ticket Owner Reporter Resolution Summary
#1022 rcuza rcuza fixed Can't build v1.2.0pre3 tag on OS X 10.6.8
Description

When trying to build the OS X package of Bcfg2 I run into a repeatable error (see attached text file for full make output) related to BCFGVER variable in the makefile:

...
<snip snip>
/bin/sh: -c: line 0: syntax error near unexpected token `('
/bin/sh: -c: line 0: `/bin/echo if sys.hexversion < 0x03000000 and os.path.exists(py3lib): 1.2.0pre3 | /usr/bin/cut -d"." -f1'
/bin/sh: -c: line 0: syntax error near unexpected token `('
/bin/sh: -c: line 0: `/bin/echo if sys.hexversion < 0x03000000 and os.path.exists(py3lib): 1.2.0pre3 | /usr/bin/cut -d"." -f2'
/bin/sh: -c: line 0: syntax error near unexpected token `('
/bin/sh: -c: line 0: `/bin/echo if sys.hexversion < 0x03000000 and os.path.exists(py3lib): 1.2.0pre3 | /usr/bin/cut -d"." -f3'
...
<snip snip>
...
rm -rf `pwd`/bcfg2-if sys.hexversion < 0x03000000 and os.path.exists(py3lib): 1.2.0pre3.pkg
/bin/sh: -c: line 0: syntax error near unexpected token `('
/bin/sh: -c: line 0: `rm -rf `pwd`/bcfg2-if sys.hexversion < 0x03000000 and os.path.exists(py3lib): 1.2.0pre3.pkg'
make: *** [server] Error 2

Here are the occurrences of the BCFGVER variable in the makefile:

$ grep BCFGVER Makefile 
BCFGVER = $(shell /usr/bin/grep version ../setup.py | cut -d\" -f2)
BCFGVER1 = $(shell /bin/echo ${BCFGVER} | /usr/bin/cut -d"." -f1)
BCFGVER2 = $(shell /bin/echo ${BCFGVER} | /usr/bin/cut -d"." -f2)
BCFGVER3 = $(shell /bin/echo ${BCFGVER} | /usr/bin/cut -d"." -f3)
BCFGVER3I = $(shell /usr/bin/python -c "import sys; print sys.argv[1][0:1]" ${BCFGVER3})
MAJOR = ${BCFGVER1}
MINOR = ${BCFGVER2}${BCFGVER3I}
        sed -i '' "s/{SHORTVERSION}/${BCFGVER}/g" "${PKGTMP}/${PROTO_PLIST}"
        rm -rf `pwd`/bcfg2-${BCFGVER}.pkg
                          --out `pwd`/bcfg2-${BCFGVER}.pkg
        rm -rf `pwd`/bcfg2-${BCFGVER}.pkg
                          --out `pwd`/bcfg2-${BCFGVER}.pkg

When run manually this is the output:

$ grep version ../setup.py | cut -d\" -f2
if sys.hexversion < 0x03000000 and os.path.exists(py3lib):
1.2.0pre3

The expected output is 1.2.0pre3.

#1023 rcuza rcuza fixed Fresh Install of bcfg2-1.2.0pre3 Fails on Mac OS X 10.6.8
Description

On a fresh install of Mac OS X 10.6 with only Apple patches applied (10.6.8, Build 10K540), /usr/local/bin/bcfg2-admin init fails with the following error:

Traceback (most recent call last):
  File "/usr/local/bin/bcfg2-admin", line 6, in <module>
    import Bcfg2.Server.Core
ImportError: No module named Bcfg2.Server.Core

The version of Bcfg2 is from commit 5c9f5c5052acf4107ecbf13d5ab63c1a7996c87e.

#1067 https://www.google.com/accounts/o8/id?id=AItOawnSjgovXZr-_V3vGkvMSR0pc5LDykRc1Nc rcuza fixed bcfg2-repo-validate throws up on missing aligator
Description

On the malformed attached Metadata/groups.xml file, bcfg2.repo.validate throws up the following error:

# bcfg2-repo-validate 
Traceback (most recent call last):
  File "/usr/sbin/bcfg2-repo-validate", line 40, in <module>
    xdata = lxml.etree.parse("%s/Metadata/groups.xml" % repo)
  File "lxml.etree.pyx", line 2706, in lxml.etree.parse (src/lxml/lxml.etree.c:49958)
  File "parser.pxi", line 1500, in lxml.etree._parseDocument (src/lxml/lxml.etree.c:71797)
  File "parser.pxi", line 1529, in lxml.etree._parseDocumentFromURL (src/lxml/lxml.etree.c:72080)
  File "parser.pxi", line 1429, in lxml.etree._parseDocFromFile (src/lxml/lxml.etree.c:71175)
  File "parser.pxi", line 975, in lxml.etree._BaseParser._parseDocFromFile (src/lxml/lxml.etree.c:68173)
  File "parser.pxi", line 539, in lxml.etree._ParserContext._handleParseResultDoc (src/lxml/lxml.etree.c:64257)
  File "parser.pxi", line 625, in lxml.etree._handleParseResult (src/lxml/lxml.etree.c:65178)
  File "parser.pxi", line 565, in lxml.etree._raiseParseError (src/lxml/lxml.etree.c:64521)
lxml.etree.XMLSyntaxError: expected '>', line 13, column 1

The expected behaviour is for bcfg2-repo-validate to say "Yo phat fingers, you are missing a '>' on line 12. What were you thinking?"

Note: See TracQuery for help on using queries.