Hi Edward,
The following procedure is from the point of view of a package mantainer.
Once you cloned the git repository, the branch by default will be the
master branch (in the most of the cases). Don't change this branch.
Checkout the gbp-master branch, instead of the master branch. It
inclu
I forgot to add the changes to debian/changelog, increasing
automatically from jessie2 to jessie3 (the upstream branch hasn't
changed, we only added a quilt patch to the debian branch):
$ git-dch --ignore-branch --auto --full
After that, you can do some minor refinements handly to debian/chang
Hi all,
Patching my latest post:
- grap
+ wrap
:)
On 12/08/2015 01:00 PM, aitor_czr wrote:
I forgot to add the changes to debian/changelog, increasing
automatically from jessie2 to jessie3 (the upstream branch hasn't
changed, we only added a quilt patch to the debian branch):
$ git-dch --
Edward Bartolo writes:
> On 07/12/2015, Edward Bartolo wrote:
>> Hi Aitor,
>>
>> Thanks for granting me permission. I will now start editing some files
>> under netman/debian so that dpkg-buildpackage works.
>>
>> I am getting this error:
>> dpkg-source: error: can't build with source format '3.0
:-)
Check those digest subjects ;-)
Steve
On Tue, 08 Dec 2015 16:00:00 +0100
aitor_czr wrote:
> Hi all,
>
> Patching my latest post:
>
> - grap
> + wrap
>
> :)
>
> On 12/08/2015 01:00 PM, aitor_czr wrote:
> > I forgot to add the changes to debian/changelog, increasing
> > automatically
Hi All,
I applied the patch suggested yesterday by Rainer *manually* by
editing files. I am lost here and I am hesitant to mess with git as it
can easily damage my sources.
Edward
On 08/12/2015, Rainer Weikusat wrote:
> Edward Bartolo writes:
>> On 07/12/2015, Edward Bartolo wrote:
>>> Hi Ai
On Tue, Dec 08, 2015 at 07:25:55PM +0100, Edward Bartolo wrote:
> Hi All,
>
> I applied the patch suggested yesterday by Rainer *manually* by
> editing files. I am lost here and I am hesitant to mess with git as it
> can easily damage my sources.
>
I belive that patch was meant to be applied usi
Edward Bartolo writes:
> I applied the patch suggested yesterday by Rainer *manually* by
> editing files. I am lost here and I am hesitant to mess with git as it
> can easily damage my sources.
While I have some "areas of disagreement" with git, it isn't that
bad. In particular, you can always us
Hi,
RunCommand is defined in the Process unit. As far as I can tell, it is
named Process.inc. This is part of the fpc-source package. Mine is
fpc-source-2.6.4 (Installed: 2.6.4+dfsg-4).
I tested again my local netman source tree with git status which
stated again that it is the same as the upload
Edward Bartolo writes:
> RunCommand is defined in the Process unit. As far as I can tell, it is
> named Process.inc. This is part of the fpc-source package. Mine is
> fpc-source-2.6.4 (Installed: 2.6.4+dfsg-4).
Judging from the fpc scm,
http://svn.freepascal.org/cgi-bin/viewvc.cgi/tags/release_2
Hi Aitor et al,
This seems to be a build dependency for the frontend. At least version
fpc-source 2.6.2 is needed to compile the frontend. Process.inc
exports RunCommand and this is used by the frontend.
Do you know where I should document this requirement?
Thanks
On 08/12/2015, Rainer Weikusat
On Tue, Dec 08, 2015 at 11:06:55PM +0100, Edward Bartolo wrote:
> Hi Aitor et al,
>
> This seems to be a build dependency for the frontend. At least version
> fpc-source 2.6.2 is needed to compile the frontend. Process.inc
> exports RunCommand and this is used by the frontend.
>
> Do you know whe
On Tue, 2015-12-08 at 23:06 +0100, Edward Bartolo wrote:
> Hi Aitor et al,
>
> This seems to be a build dependency for the frontend. At least version
> fpc-source 2.6.2 is needed to compile the frontend. Process.inc
> exports RunCommand and this is used by the frontend.
>
> Do you know where I sh
13 matches
Mail list logo
