The previous section indicated that new PBI modules are uploaded to the PBI build server. There are actually several build locations, according to PC-BSD version and architecture:

+

'''Figure 11.6a: Viewing the Status of PBIs on the Build Server'''

−

* [http://pbibuild.pcbsd.org PC-BSD 7.x - i386]

+

[[File:Build1a.png|border]]

−

* [http://pbibuild64.pcbsd.org PC-BSD 7.x - amd64]

+

−

* [http://pbibuild.pcbsd.org/index.php?ver=8 PC-BSD 8.x - i386]

+

−

* [http://pbibuild64.pcbsd.org/index.php?ver=8 PC-BSD 8.x - amd64]

+

−

* [http://pbibuild.pcbsd.org/index.php?ver=9 PC-BSD 9.x - i386]

+

−

* [http://pbibuild64.pcbsd.org/index.php?ver=9 PC-BSD 9.x - amd64]

+

−

+

−

Figure X-XX shows a sample from the PC-BSD 8.x 32 bit location:

+

−

+

−

'''Figure X-XX:'''

+

−

+

−

[[File:Build.png]]

+

There are two ways you can assist in testing PBIs.

There are two ways you can assist in testing PBIs.

−

First, if you wish to help test a PBI before it has been approved, go to the build location for your version and architecture. Find the name of the PBI you wish to test in the Module column and click its hyperlink. You can then download the file with the .pbi extension. If you double-click the downloaded PBI in Dolphin, it will install the PBI for you. If you find any problems with the PBI, send an email to the [http://lists.pcbsd.org/mailman/listinfo/pbi-dev PBI-dev] mailing list describing how to recreate the problem. Include the text of any error messages you receive.

+

First, if you wish to help test a PBI before it has been approved, go to the build location for your version and architecture. Find the name of the PBI you wish to test in the "Module" column and click its hyperlink. You can then download the file with the ''.pbi'' extension. Once downloaded, run '''pbi_add /path/to/pbi''' to install the PBI. If you find any problems with the PBI, send an email to the {{citelink|url=http://lists.pcbsd.org/mailman/listinfo/pbi-dev|txt=PBI-dev}} mailing list describing how to recreate the problem. Include the text of any error messages you receive.

−

+

−

Second, you can try to resolve PBI modules that have a Build Status of FAILED. If you click on the name of a failed module, you can download the build.log.bz2 for that module. To access this file, you can either:

+

−

+

−

'''bunzip2 build.log.bz2''' to unzip the file so you can send it to a text processor to read it.

+

−

+

−

or

+

−

+

−

'''bzcat build.log.bz2''' to read the file without unzipping it. It will scroll down to the end, where the error occurred. Use '''bzcat build.log.bz2 | more''' if you prefer to scroll through the file.

+

−

If you think you know the cause of the problem after reading the error messages, you will need the module itself to try to resolve the problem. Modules are located in the PC-BSD [http://svn.pcbsd.org/browser/pbibuild/modules/ subversion repository]. To download the module, you can use the svn command. To give an example, the math/scilab PBI was flagged as FAILED in Figure X-XX. To download that module, cd to a suitable directory and issue the command:

+

Second, you can try to resolve PBI modules that have a "Build Status" of "FAILED". If you click on the name of a failed module, you can download the ''build.log'' for that module. This file is in ASCII text so it can be viewed in any text editor.

−

'''svn co svn://svn.pcbsd.org/pbibuild/modules/math/scilab'''

+

If the file ends in a ''.bz2'' extension, it has been compressed. To uncompress the file, type '''bunzip2 build.log.bz2'''. Or, you can read the compressed file directly using the command '''bzcat build.log.bz2'''. This command will scroll down to the end, where the error occurred. Use '''bzcat build.log.bz2 | more''' if you prefer to scroll through the file.

−

Note that the command uses the svn:// URI and does not include the /browser/ section in the URL.

+

If you think you know the cause of the problem after reading the error messages, you can review the PBI's module by clicking its "svn" hyperlink. If you decide to download a file to edit it, look for the "Plain Text" link in the "Download in other formats" section at the bottom of the page.

+

+

If you make an edit to correct the problem, send the modified file (or a diff) to the {{citelink|url=http://lists.pcbsd.org/mailman/listinfo/pbi-dev|txt=PBI-dev}} mailing list so the changes can be uploaded to the build server.

−

This command will create a directory called scilab and place the module's files in that directory. If you make changes to these files to correct the problem, create a tar.gz of the directory and send the tarball to the [http://lists.pcbsd.org/mailman/listinfo/pbi-dev PBI-dev] mailing list so the changes can be uploaded to the build server.

+

<noinclude>{{refheading}}</noinclude>

+

<noinclude>

+

[[category:handbook]]

+

[[category:Supporting PC-BSD®]]

+

[[category:Test PBIs]]

+

</noinclude>

Revision as of 12:33, 19 November 2012

(Sorry for the inconvenience)

Editor: please update template:UseTOC/9.2

Translator: please use {{UseTOC{{putVers}}|TOC}}

Protection (edit): sysopEdited by: Drulavigne

The previous section indicated that new PBI modules are uploaded to the PBI build server so that they can be built and tested. There are two build locations, one for each PC-BSD® architecture:

First, if you wish to help test a PBI before it has been approved, go to the build location for your version and architecture. Find the name of the PBI you wish to test in the "Module" column and click its hyperlink. You can then download the file with the .pbi extension. Once downloaded, run pbi_add /path/to/pbi to install the PBI. If you find any problems with the PBI, send an email to the PBI-dev[3] mailing list describing how to recreate the problem. Include the text of any error messages you receive.

Second, you can try to resolve PBI modules that have a "Build Status" of "FAILED". If you click on the name of a failed module, you can download the build.log for that module. This file is in ASCII text so it can be viewed in any text editor.

If the file ends in a .bz2 extension, it has been compressed. To uncompress the file, type bunzip2 build.log.bz2. Or, you can read the compressed file directly using the command bzcat build.log.bz2. This command will scroll down to the end, where the error occurred. Use bzcat build.log.bz2 | more if you prefer to scroll through the file.

If you think you know the cause of the problem after reading the error messages, you can review the PBI's module by clicking its "svn" hyperlink. If you decide to download a file to edit it, look for the "Plain Text" link in the "Download in other formats" section at the bottom of the page.

If you make an edit to correct the problem, send the modified file (or a diff) to the PBI-dev[3] mailing list so the changes can be uploaded to the build server.