Opened 16 years ago

Closed 13 years ago

#22 closed defect (fixed)

ChangeLog not created if svn2cl not installed

Reported by: Bruno Cornec Owned by: Bruno Cornec
Priority: major Milestone: 0.10.1
Component: pb Version: 0.8.12
Keywords: Cc:

Description

ChangeLog not created if svn2cl not installed => rpm build fails later on

Change History (13)

comment:1 by Bruno Cornec, 16 years ago

Milestone: 0.9.00.9.1

comment:2 by Bruno Cornec, 16 years ago

Milestone: 0.9.10.9.2
Owner: set to Bruno Cornec
Status: newassigned

comment:3 by Bruno Cornec, 16 years ago

Milestone: 0.9.20.9.3

comment:4 by Bruno Cornec, 16 years ago

Milestone: 0.9.30.9.4

We should import svn2cl/cvs2cl code into pb to be independent

comment:5 by Bruno Cornec, 16 years ago

Milestone: 0.9.40.9.5

comment:6 by Bruno Cornec, 15 years ago

Milestone: 0.9.50.9.6

comment:7 by Bruno Cornec, 15 years ago

Milestone: 0.9.60.9.7

comment:8 by Bruno Cornec, 15 years ago

Milestone: 0.9.70.9.8

in reply to:  description comment:9 by Benoit Mortier, 15 years ago

Replying to bruno:

ChangeLog not created if svn2cl not installed => rpm build fails later on

This create a bug and stop the program

Unable to create /home/benoit/develop/project-builder/gosa/delivery/gosa-trunk/ChangeLog at /usr/share/perl/5.10/ProjectBuilder/CMS.pm line 761.

I think that a depency to svn2cl or cvs2cl is not that bad

or remove the die and create a basic changelog

cheers

comment:10 by Bruno Cornec, 15 years ago

As I just use a small portion of those tools, I was even considering including the code in pb directly. What is your take on this ?

A dependency is probably what is needed if we resort to keep an external call.

comment:11 by Bruno Cornec, 14 years ago

Milestone: 0.9.90.9.10

comment:12 by Bruno Cornec, 14 years ago

Milestone: 0.9.100.9.11

comment:13 by Bruno Cornec, 13 years ago

Resolution: fixed
Status: assignedclosed

I think this bug is since a long time fixed in fact as the call to svn2cl or cvs2cl is checked, and anyway an empty log file is created. Please reopen if you think there is still an issue.

Note: See TracTickets for help on using tickets.