Custom Query (159 matches)
Results (25 - 27 of 159)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #35 | fixed | First build with pb doesn't create the correct tree | ||
| Description |
When using pb for the first time on a system without previous pb, the checkout done use the version passed in param. However, you may want to refer to the whole tree instead in pburl. Which may create a problem. pb should detect that and propose the right thing. Checking out svn+ssh://svn.project-builder.org/mondo/svn/pb to /home/pb/pb//0.9.4 ... Executing svn co svn+ssh://svn.project-builder.org/mondo/svn/pb /home/pb/pb//0.9.4 Where pburl is pburl pb = svn+ssh://bryang@svn.project-builder.org/mondo/svn/pb In that case the co creates twice a 0.9.4 dir in which it exports the content. |
|||
| #37 | worksforme | cms anonymous access | ||
| Description |
It appears that I can't correctly specify anonymous access for CVS (and I suspect for svn) for the project to be packaged itself (eg. for pburl) . This is a must to have, since I can't be expected to have authenticated access to a project's CMS at the early stages. This is also likely true for the pbconfurl as well, so that once the necessary configurations are established, packages could be build by automated means. Hence the same defect and requirement here. |
|||
| #38 | fixed | debian packages for CVS based projects and (HEAD) versions | ||
| Description |
Currently, when a revision is not specified for a CVS based project, PB attempts to use cvs-1 as a versioning string. This is a problem for debian packaging guidelines and the typical tools used resulting is this type of error: dh_builddeb -v
dpkg-deb - error: (upstream) version (`cvs') doesn't contain any digits dpkg-deb: 1 errors in control file dh_builddeb: command returned error code 512 make: * [binary-arch] Error 1 dpkg-buildpackage: failure: fakeroot debian/rules binary gave error exit status 2 I'd suggest we modify this approach to use one similar to the svn behaviour of using a date stamp format (YYYYMMDD), and this also matches what Debian Policy states: http://www.debian.org/doc/debian-policy/ch-binary.html#s3.2.1 |
|||
