Re: RFS: libchart-php

[Daniel Lombraña González]

Dear Kilian,

Would you mind to check again the package ;) I hope this time is almost done
:)

Regards,

Daniel

2011/8/1 Kilian Krause 

> Hi Daniel,
>
> On Mon, Aug 01, 2011 at 05:36:36PM +0200, Daniel Lombraña González wrote:
> > 2011/7/30 Michael Tautschnig 
> > > > I have update the package with the latest available version 1.3.
> Please,
> > > can
> > > > you check if everything is OK?
> > > >
> > > [...]
> > >
> > > I just thought I'd briefly check whether your orig.tar.gz matches the
> > > upstream
> > > tar.gz, found different md5sums and then this:
> > >
> > > (omitting full diffstat output)
> > >  78 files changed, 3771 insertions(+), 4496 deletions(-)
> > >
> > > !?
> > >
> > > It seems you completely reorganized the source tree. That's not quite
> the
> > > point
> > > of a .orig.tar.gz file.
> > >
> >
> > I'm sorry, I thought I have to reorganized the source tree to create the
> > package. Now I have understood the problem, and a new version has been
> > uploaded. This one has the original tar.gz. I hope this time, at least
> this
> > issue is fixed.
>
> Thanks for the update. Your debian/watch however still doesn't work for me.
> A version that would work looks at least like this:
>
> version=3
> opts="downloadurlmangle=s#\/\/code.google.com##" \
> http://code.google.com/p/libchart/downloads/list \
>
> //libchart.googlecode.com/files/libchart-(.*)\.tar\.gz<http://libchart.googlecode.com/files/libchart-%28.*%29%5C.tar%5C.gz>
>
> -(snip)-
>
> Feel free to provide an even better one if you can. =)
>
> Apart from that you still ship the *.ttf files inside your orig.tar.gz
> source. You will want to modify this as DFSG-repack (removing the ttf files
> entirely from the tarball) and leave your patch in place which looks ok
> from
> a first glimpse. A get-orig-source target inside debian/rules is the
> correct
> place to put this.
>
> Your standards-version is still at 3.9.1 and should be bumped to latest
> 3.9.2 - shouldn't be much of a problem.
>
> The debian/copyright looks a bit weird with the URL you point to. Please
> use
> DEP-5 (which is the to-be-standard) with its correct URL instead - and put
> a
> full verbatim GPL-3 quote.
>
> The URL http://libchart.googlecode.com/svn/trunk doesn't work. Neither
> does
> http://naku.dohcrew.com/libchart/pages/introduction. At least with a
> regular
> browser. Should they? I guess at least the latter should.
>
> The upstream changelog at libchart/ChangeLog should be shipped also in the
> package.
>
> Ping me or Michael when the above is done as that should make the package
> good enough for an initial upload.
>
> Thanks!
>
> --
> Best regards,
> Kilian
>
> -BEGIN PGP SIGNATURE-
> Version: GnuPG v1.4.10 (GNU/Linux)
>
> iD4DBQFONxVmvdkzt4X+wX8RAsn2AJ9EBjCqq3LAVZXe4CHJJK7D3FXiSQCY5p/E
> vbUhfgw7RTTqQao6e06IhA==
> =AJyR
> -END PGP SIGNATURE-
>
>


-- 
··
http://github.com/teleyinex
http://www.flickr.com/photos/teleyinex
··
Por favor, NO utilice formatos de archivo propietarios para el
intercambio de documentos, como DOC y XLS, sino HTML, RTF, TXT, CSV
o cualquier otro que no obligue a utilizar un programa de un
fabricante concreto para tratar la información contenida en él.
··

Re: RFS: libchart-php

[Daniel Lombraña González]

Dear Michael,

2011/7/30 Michael Tautschnig 

> Hi Daniel,
>
> > I have update the package with the latest available version 1.3. Please,
> can
> > you check if everything is OK?
> >
> [...]
>
> I just thought I'd briefly check whether your orig.tar.gz matches the
> upstream
> tar.gz, found different md5sums and then this:
>
> (omitting full diffstat output)
>  78 files changed, 3771 insertions(+), 4496 deletions(-)
>
> !?
>
> It seems you completely reorganized the source tree. That's not quite the
> point
> of a .orig.tar.gz file.
>

I'm sorry, I thought I have to reorganized the source tree to create the
package. Now I have understood the problem, and a new version has been
uploaded. This one has the original tar.gz. I hope this time, at least this
issue is fixed.

Regards,

Daniel


>
> I didn't dig any deeper as copyright checks don't make sense if upstream
> source
> isn't actually upstream source.
>
> Sorry,
> Michael
>
>


-- 
··
http://github.com/teleyinex
http://www.flickr.com/photos/teleyinex
··
Por favor, NO utilice formatos de archivo propietarios para el
intercambio de documentos, como DOC y XLS, sino HTML, RTF, TXT, CSV
o cualquier otro que no obligue a utilizar un programa de un
fabricante concreto para tratar la información contenida en él.
··

Re: RFS: libchart-php

[Daniel Lombraña González]

Dear Michael,

I have update the package with the latest available version 1.3. Please, can
you check if everything is OK?

Regards,

Daniel

2011/5/3 Daniel Lombraña González 

> Dear Michael,
>
> Thanks for your advice. I will try to fix this problem, and upload a new
> version.
>
> Regards,
>
> Daniel
>
>
> 2011/5/1 Michael Tautschnig 
>
>> [...]
>> > > Well, it seems to me that this information is better suited for the
>> > > patch header and the changelog (I want to know about that when I'm
>> > > looking at the patch, but as an end-user reading the installed
>> > > README.Debian, I don't really care; it won't change how I use the
>> > > package).
>> >
>> > I have changed them to the changelog file. However, I don't know how
>> > to get the information in the debian patches folder, as those files
>> > are automatically created by dpkg. Can you help me? I'm using
>> > git-buildpackge for creating the package.
>> >
>> [...]
>>
>> They are created by dpkg *once*, but after that you can freely modify
>> them.
>>
>> Hope this helps,
>> Michael
>>
>>
>
>
> --
>
> ··
> http://github.com/teleyinex
> http://www.flickr.com/photos/teleyinex
>
> ··
> Por favor, NO utilice formatos de archivo propietarios para el
> intercambio de documentos, como DOC y XLS, sino HTML, RTF, TXT, CSV
> o cualquier otro que no obligue a utilizar un programa de un
> fabricante concreto para tratar la información contenida en él.
>
> ··
>



-- 
··
http://github.com/teleyinex
http://www.flickr.com/photos/teleyinex
··
Por favor, NO utilice formatos de archivo propietarios para el
intercambio de documentos, como DOC y XLS, sino HTML, RTF, TXT, CSV
o cualquier otro que no obligue a utilizar un programa de un
fabricante concreto para tratar la información contenida en él.
··

Re: RFS: libchart-php

[Daniel Lombraña González]

Dear Michael,

Thanks for your advice. I will try to fix this problem, and upload a new
version.

Regards,

Daniel

2011/5/1 Michael Tautschnig 

> [...]
> > > Well, it seems to me that this information is better suited for the
> > > patch header and the changelog (I want to know about that when I'm
> > > looking at the patch, but as an end-user reading the installed
> > > README.Debian, I don't really care; it won't change how I use the
> > > package).
> >
> > I have changed them to the changelog file. However, I don't know how
> > to get the information in the debian patches folder, as those files
> > are automatically created by dpkg. Can you help me? I'm using
> > git-buildpackge for creating the package.
> >
> [...]
>
> They are created by dpkg *once*, but after that you can freely modify them.
>
> Hope this helps,
> Michael
>
>


-- 
··
http://github.com/teleyinex
http://www.flickr.com/photos/teleyinex
··
Por favor, NO utilice formatos de archivo propietarios para el
intercambio de documentos, como DOC y XLS, sino HTML, RTF, TXT, CSV
o cualquier otro que no obligue a utilizar un programa de un
fabricante concreto para tratar la información contenida en él.
··

Re: RFS: libchart-php

[Daniel Lombraña González]

2011/2/10 Benoît Knecht :
> Daniel Lombraña González wrote:
>> > You should document the changes introduced by
>> > debian/patches/debian-changes-1.2.2-1, and avoid creating example files
>> > in that patch (simply put the files somewhere in debian/, and install
>> > them from there). Also, make sure you forward those changes upstream if
>> > relevant.
>>
>> That was my fault. I deleted from the original software the examples.
>> Those files are directly provided by the upstream author, so I have
>> rebuilt the package, removing those files as patches, and including
>> them in the orig.tar.gz package.
>
> Great, it's much better now.

Thanks ;)

>
>> I have documented those changes in the file README.Debian. I don't
>> know if I should include that information in other file. Please, let
>> me know if this is OK or not.
>
> Well, it seems to me that this information is better suited for the
> patch header and the changelog (I want to know about that when I'm
> looking at the patch, but as an end-user reading the installed
> README.Debian, I don't really care; it won't change how I use the
> package).

I have changed them to the changelog file. However, I don't know how
to get the information in the debian patches folder, as those files
are automatically created by dpkg. Can you help me? I'm using
git-buildpackge for creating the package.

Cheers,

Daniel
>
> Cheers,
>
> --
> Benoît Knecht
>
>
> --
> To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
> Archive: http://lists.debian.org/20110210225658.gb19...@debian.lan
>
>



-- 
··
http://github.com/teleyinex
http://www.flickr.com/photos/teleyinex
··
Por favor, NO utilice formatos de archivo propietarios para el
intercambio de documentos, como DOC y XLS, sino HTML, RTF, TXT, CSV
o cualquier otro que no obligue a utilizar un programa de un
fabricante concreto para tratar la información contenida en él.
··

Re: RFS: libchart-php

[Daniel Lombraña González]

Hi,

2011/2/10 Benoît Knecht :
> Daniel Lombraña González wrote:
>> 2011/2/8 Benoît Knecht :
>> > Lintian reports a few issues that you should address:
>> >
>> >  W: libchart-php source: out-of-date-standards-version 3.8.0 (current is 
>> > 3.9.1)
>> >  I: libchart-php: description-synopsis-might-not-be-phrased-properly
>> >  I: libchart-php: extended-description-is-probably-too-short
>>
>> I have fixed those lintian errors.
>
> Could you also add a working debian/watch file?

Added.

>
>> > And your debian/changelog entry is incomplete, you should have a bug
>> > number in the "(Closes: #)" part (submit a bug against wnpp if you
>> > didn't already, see http://www.debian.org/devel/wnpp/ ).
>>
>> I have created a bug
>> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=612615 for the
>> package. So now the changelog is corrected.
>
> You forgot to update the date in the changelog, so it looks like if the
> time continuum was broken (as if the bug number was put in the changelog
> before the bug even existed).

Fixed :)

>
>> Please, let me know if I need to fix something else of the package.
>
> You should document the changes introduced by
> debian/patches/debian-changes-1.2.2-1, and avoid creating example files
> in that patch (simply put the files somewhere in debian/, and install
> them from there). Also, make sure you forward those changes upstream if
> relevant.

That was my fault. I deleted from the original software the examples.
Those files are directly provided by the upstream author, so I have
rebuilt the package, removing those files as patches, and including
them in the orig.tar.gz package. I have documented those changes in
the file README.Debian. I don't know if I should include that
information in other file. Please, let me know if this is OK or not.

Regards,

Daniel
>
> Cheers,
>
> --
> Benoît Knecht
>
>
> --
> To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
> Archive: http://lists.debian.org/20110210110909.gc27...@debian.lan
>
>



-- 
··
http://github.com/teleyinex
http://www.flickr.com/photos/teleyinex
··
Por favor, NO utilice formatos de archivo propietarios para el
intercambio de documentos, como DOC y XLS, sino HTML, RTF, TXT, CSV
o cualquier otro que no obligue a utilizar un programa de un
fabricante concreto para tratar la información contenida en él.
··

Re: RFS: libchart-php

[Daniel Lombraña González]

Hi,

2011/2/8 Benoît Knecht :
> Hi Daniel,
>
> Daniel Lombraña González wrote:
>> I am looking for a sponsor for my package "libchart-php".
>>
>> * Package name    : libchart-php
>>   Version         : 1.2.2
>>   Upstream Author : [fill in name and email of upstream]
>> * URL             : http://code.google.com/p/libchart/
>> * License         : GPLv3
>>   Section         : web
>>
>> It builds these binary packages:
>> libchart-php - PHP library for creating charts.
>>
>> The package appears to be lintian clean.
>
> Lintian reports a few issues that you should address:
>
>  W: libchart-php source: out-of-date-standards-version 3.8.0 (current is 
> 3.9.1)
>  I: libchart-php: description-synopsis-might-not-be-phrased-properly
>  I: libchart-php: extended-description-is-probably-too-short

I have fixed those lintian errors.

>
> Also, you should use a version number in the form
> ${upstream_version}-${debian_version} (i.e. 1.2.2-1).

I have also fixed the version number.

>
> And your debian/changelog entry is incomplete, you should have a bug
> number in the "(Closes: #)" part (submit a bug against wnpp if you
> didn't already, see http://www.debian.org/devel/wnpp/ ).

I have created a bug
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=612615 for the
package. So now the changelog is corrected.

Please, let me know if I need to fix something else of the package.

Regards,

Daniel
>
> Cheers,
>
> --
> Benoît Knecht
>
>
> --
> To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
> Archive: http://lists.debian.org/20110208172036.gb6...@debian.lan
>
>



-- 
··
http://github.com/teleyinex
http://www.flickr.com/photos/teleyinex
··
Por favor, NO utilice formatos de archivo propietarios para el
intercambio de documentos, como DOC y XLS, sino HTML, RTF, TXT, CSV
o cualquier otro que no obligue a utilizar un programa de un
fabricante concreto para tratar la información contenida en él.
··

RFS: libchart-php

[Daniel Lombraña González]

Dear mentors,

I am looking for a sponsor for my package "libchart-php".

* Package name: libchart-php
  Version : 1.2.2
  Upstream Author : [fill in name and email of upstream]
* URL : http://code.google.com/p/libchart/
* License : GPLv3
  Section : web

It builds these binary packages:
libchart-php - PHP library for creating charts.

The package appears to be lintian clean.

My motivation for maintaining this package is: I'm using this
interesting library for creating charts for my software Jarifa. I'm
also creating a package for Jarifa, and the library was embed, so
sponsors told me that I should remove the library and create a
separate package for it. Thanks to this package, the library will be
able to be used by other developers and applications, not only Jarifa.

The package can be found on mentors.debian.net:
- URL: http://mentors.debian.net/debian/pool/main/l/libchart-php
- Source repository: deb-src http://mentors.debian.net/debian unstable
main contrib non-free
- dget 
http://mentors.debian.net/debian/pool/main/l/libchart-php/libchart-php_1.2.2.dsc

I would be glad if someone checks an uploaded this package for me.

Kind regards
 Daniel Lombraña González


-- 
··
http://jarifa.unex.es/
http://www.flickr.com/photos/teleyinex
··
Por favor, NO utilice formatos de archivo propietarios para el
intercambio de documentos, como DOC y XLS, sino HTML, RTF, TXT, CSV
o cualquier otro que no obligue a utilizar un programa de un
fabricante concreto para tratar la información contenida en él.
··

Re: RFS: jarifa

[Daniel Lombraña González]

Thanks for the comments. I will try to address all your points, and fix them!!!

On Sun, Dec 12, 2010 at 17:58, Paul Wise  wrote:
> 2010/12/9 Daniel Lombraña González :
>
>> I am looking for a sponsor for my package "jarifa".
>
> A review of the source package:
>
> Your upstream version should be 1.0~rc8 since that sorts before 1.0
> and rc usually means release candidate.
>
> debian/patches/debian-changes-1.0-rc8-1 looks like it can be removed
> or applied upstream.
>
> Please add a debian/watch file (see uscan manual page for details).
>
> You might want to wrap the Depends line in debian/control since it is
> very long. I like to split the line after every comma.
>
> Can jarifa not connect to a MySQL server over the network? If so you
> might want to demote mysql-server to recommends.
>
> README.source looks like it belongs in the upstream README since it is
> not Debian specific.
>
> You add a symlink to ttf-dejavu fonts but do not depend on it. At the
> very least I would say you need a Recommend.
>
> Please switch jarifa to a randomly generated password instead of a
> static easily guessable one when the user does not set a password.
>
> www-data is defined in base-passwd so I think you can set permissions
> on /usr/share/jarifa/img/stats at build time instead of in
> postinstall.
>
> Why does your prerm remove files from /usr? I think maybe your
> software should use /var/lib/jarifa instead for runtime-created data.
>
> I would replace your debian/rules file with
> /usr/share/doc/debhelper/examples/rules.tiny and add "conf/jarifa.sql
> usr/share/dbconfig-common/data/jarifa/install/mysql" to
> debian/jarifa.install.
>
> libchart-1.2 is an embedded code copy (with its own embedded font
> copy), please remove it from the tarball and package it separately.
> db_conn.inc is similar, but I'm wondering why I don't see that in the
> boinc package in Debian.
>
> These files look like they were created in Inkscape/GIMP but I don't
> see any SVG/XCF source for them: computer.png cpus.png credit.png
> supplier.png volunteer.png.
>
> I wonder what the license/source for vcss.png is, since it looks like
> an image from the W3C. Same for agplv3.png since it is an FSF image.
>
> Why is there a lang/es_ES.utf8/LC_MESSAGES/messages.mo but no
> lang/es_ES.utf8/LC_MESSAGES/messages.po?
>
> Have you had the PHP code audited for vulnerabilities or run any
> automated exploit finding tools against jarifa? Examples of such tools
> available in Debian include w3af wapiti sqlmap rats. owasp.org is a
> good place to go to learn about web application security.
>
> Your jarifa.apache.conf forces jarifa to be available at /jarifa on
> all apache vhosts. As a sysadmin I would expect to be either asked
> what vhost, URL path to configure jarifa at or expect me to configure
> it manually based on an example config.
>
> lintian complaints:
>
> I: jarifa source: no-complete-debconf-translation
> I: jarifa source: debian-watch-file-is-missing
>
> --
> bye,
> pabs
>
> http://wiki.debian.org/PaulWise
>
>
> --
> To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
> Archive: 
> http://lists.debian.org/aanlktintdrm5edez5g1+haeh_7kc-d-xoa8fxzvh...@mail.gmail.com
>
>



-- 
··
http://jarifa.unex.es/
http://www.flickr.com/photos/teleyinex
··
Por favor, NO utilice formatos de archivo propietarios para el
intercambio de documentos, como DOC y XLS, sino HTML, RTF, TXT, CSV
o cualquier otro que no obligue a utilizar un programa de un
fabricante concreto para tratar la información contenida en él.
··

RFS: jarifa

[Daniel Lombraña González]

Dear mentors,

I am looking for a sponsor for my package "jarifa".

* Package name: jarifa
  Version : 1.0-rc8-2
  Upstream Author : Daniel Lombraña González
* URL : http://jarifa.unex.es
* License : AGPLv3
  Section : web

It builds these binary packages:
jarifa - A system for grid computing on organizational resources using BOINC

The package appears to be lintian clean.

My motivation for maintaining this package is: that I'm the author of
the software, and I would like to see this software packaged for
Debian, making easier the installation process of the tool.

The package can be found on mentors.debian.net:
- URL: http://mentors.debian.net/debian/pool/main/j/jarifa
- Source repository: deb-src http://mentors.debian.net/debian unstable
main contrib non-free
- dget http://mentors.debian.net/debian/pool/main/j/jarifa/jarifa_1.0-rc8-2.dsc

I would be glad if someone uploaded this package for me.

Kind regards
 Daniel Lombraña González


--
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/aanlktim-9eanjsni7uu5vpidzspa+mhjbupptehdm...@mail.gmail.com

Re: Using Quilt with a new package

[Daniel Lombraña González]

Hi everyone,

Thanks for all your help. I think that right now the easiest way for
me is to handle the modifications by hand as they are not very
difficult to manage (just comment out one line in the SQL file).
Neverthless, what I wanted is to do this automatically for me :). I
will try it again with Quilt 3.0 and see if I can achieve what I want.

Thanks for your help,

Daniel

On Wed, Nov 3, 2010 at 16:45, Goswin von Brederlow  wrote:
> Scott Howard  writes:
>
>> On Wed, Nov 3, 2010 at 3:00 AM, Charles Plessy  wrote:
>>> Le Tue, Nov 02, 2010 at 01:02:25PM +0100, Daniel Lombrańa González a écrit :

 After that, I kept reading about git-buildpackage and it seems that it
 should be more easy to maintain those differences between the upstream
 version and the deb one using patches. However, I don't know how I
 have to do this, as I have been trying it out, and as far as I have
 get is to create the debian/patches folder (using gbp-pq) with a patch
 that removes that instruction. However, when building the package
 using git-buildpackage in the master branch (not in
 patch-queue/master) the resulting package does not have applied the
 patch, which is wrong. Is it possible to apply automatically those
 patches when building the package? (FYI I have tried the 3.0 version,
 and I don't get it working either, probably because I'm doing
 something wrong).
>>>
>>
>> Paul is right, it's best to get upstream to make a change so you don't
>> need patches, but in case they don't the easiest way is to use source
>> 3.0 (quilt) format [1]. That should automatically apply and keep track
>> of packages for you with no need to change rules files or add depends.
>>
>> I don't know what problem you're having, but the following command:
>> mkdir debian/source ; echo '3.0 (quilt)' > debian/source/format
>>
>> would create a file named "format" in debian/source in your package.
>> The content of the file should be '3.0 (quilt)'. Now you should just
>> use quilt normally.
>>
>> For example
>> quilt new my_new_patch.patch
>> quilt add src/file_i_want_to_change.c
>> [edit the file]
>> quilt refresh
>
> That won't work, at least not the verry first time. The verry first time
> you need to use 'QUILT_PATCHES=debian/patches quilt ...'. When you
> unpack a source with dpkg-source it does this for you.
>
>
> An alternative way to create a new patch and from my point of view
> easier is to
>
> - just edit files
>
> - debuild / dpkg-buildpackage till you are happy
>  + creates debian/patches/debian-changes-version
>
> - quilt rename [-P debian-changes-version] my-cool-new-feature.patch
>
> - $EDITOR debian/patches/my-cool-new-feature.patch
>  + add patch description to the premade header
>
>> you now should have your patch in debian/patches along with a file
>> named "series" in debian/patches that contains the name of your patch.
>>
>> You can find better how tos on the internet, but that should be it.
>>
>> [1] http://wiki.debian.org/Projects/DebSrc3.0
>
> And if you want to have patches unapplied add "unapply-patches" to
> debian/source/local-options.
>
> MfG
>        Goswin
>
>
> --
> To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
> Archive: http://lists.debian.org/87iq0eif7m@frosties.localdomain
>
>



-- 
··
http://jarifa.unex.es/
http://www.flickr.com/photos/teleyinex
··
Por favor, NO utilice formatos de archivo propietarios para el
intercambio de documentos, como DOC y XLS, sino HTML, RTF, TXT, CSV
o cualquier otro que no obligue a utilizar un programa de un
fabricante concreto para tratar la información contenida en él.
··

Using Quilt with a new package

[Daniel Lombraña González]

Dear all,

I'm creating a new deb package for the software Jarifa (
http://jarifa.unex.es), and  I'm wondering when I should use quilt and
git-buildpackage to modify
at least as possible the upstream version of Jarifa files. Let me
explain. Jarifa has a SQL file that by default creates the DB in
MySQL. Nevertheless, in the deb package this is managed by
dbconfig-common, so I have to remove the instruction of creating the
DB in the SQL file. Right now I have done this, by creating a new git
repository and modify the source code by hand.

After that, I kept reading about git-buildpackage and it seems that it
should be more easy to maintain those differences between the upstream
version and the deb one using patches. However, I don't know how I
have to do this, as I have been trying it out, and as far as I have
get is to create the debian/patches folder (using gbp-pq) with a patch
that removes that instruction. However, when building the package
using git-buildpackage in the master branch (not in
patch-queue/master) the resulting package does not have applied the
patch, which is wrong. Is it possible to apply automatically those
patches when building the package? (FYI I have tried the 3.0 version,
and I don't get it working either, probably because I'm doing
something wrong).

Thanks in advance,

Daniel

-- 
··
http://jarifa.unex.es/
http://www.flickr.com/photos/teleyinex
··
Por favor, NO utilice formatos de archivo propietarios para el
intercambio de documentos, como DOC y XLS, sino HTML, RTF, TXT, CSV
o cualquier otro que no obligue a utilizar un programa de un
fabricante concreto para tratar la información contenida en él.
··

Re: Using quilt for Jarifa

[Daniel Lombraña González]

Thanks a lot Fernando. I will send an e-mail to that list :)

Cheers,

Daniel

On Thu, Oct 28, 2010 at 05:15, Fernando C. Estrada
 wrote:
> Hi,
>
> El mié, 27-10-2010 a las 16:02 +0200, Daniel Lombraña González escribió:
>>
>> I do not an answer in a few days, so I was wondering where I should
>> ask for help in this matter. Thanks a lot :)
>
> Daniel: I'm unable to help you but maybe in the mentors list someone
> give you a proper advice about this ;-)
>
>> > I'm wondering when I should use quilt and git-buildpackage to modify
>> > at least as possible the upstream version of Jarifa files. Let me
>> > explain. Jarifa has a SQL file that by default creates the DB in
>> > MySQL. Nevertheless, in the deb package this is managed by
>> > dbconfig-common, so I have to remove the instruction of creating the
>> > DB in the SQL file. Right now I have done this, by creating a new git
>> > repository and modify the source code by hand.
>> >
>> > After that, I kept reading about git-buildpackage and it seems that it
>> > should be more easy to maintain those differences between the upstream
>> > version and the deb one using patches. However, I don't know how I
>> > have to do this, as I have been trying it out, and as far as I have
>> > get is to create the debian/patches folder (using gbp-pq) with a patch
>> > that removes that instruction. However, when building the package
>> > using git-buildpackage in the master branch (not in
>> > patch-queue/master) the resulting package does not have applied the
>> > patch, which is wrong. Is it possible to apply automatically those
>> > patches when building the package? (FYI I have tried the 3.0 version,
>> > and I don't get it working either, probably because I'm doing
>> > something wrong).
>
> Regards,
> --
> Fernando C. Estrada
>
>



-- 
··
http://jarifa.unex.es/
http://www.flickr.com/photos/teleyinex
··
Por favor, NO utilice formatos de archivo propietarios para el
intercambio de documentos, como DOC y XLS, sino HTML, RTF, TXT, CSV
o cualquier otro que no obligue a utilizar un programa de un
fabricante concreto para tratar la información contenida en él.
··