Re: Moving package with quilt to new upstream version

2010-09-19 Thread Guido Günther
On Wed, Sep 15, 2010 at 10:12:29PM +0200, Bernd Zeimetz wrote: On 09/15/2010 06:33 PM, Henrique de Moraes Holschuh wrote: On Wed, 15 Sep 2010, Giuseppe Sacco wrote: IMO, you should try to get yourself better acquinted with quilt before using it, or you can end up with a mess. Right.

Re: Moving package with quilt to new upstream version

2010-09-17 Thread Raphael Hertzog
On Wed, 15 Sep 2010, Henrique de Moraes Holschuh wrote: On Wed, 15 Sep 2010, Goswin von Brederlow wrote: QUILT_PATCHES=debian/patches quilt push will do the same. You only need QUILT_PATCHES for the first quilt call. Is that so? That would be good news, but it doesn't match my

Moving package with quilt to new upstream version

2010-09-15 Thread Giuseppe Sacco
Hi all, I have recently packaged hylafax 6.0.4-10 using quilt. Now I am moving to a new upstream release 6.0.5 and I am trying to update my package following http://www.debian.org/doc/maint-guide/ch-update.en.html#s-newupstream but I failed to it properly. What I do: 1. untar new upstream release

Re: Moving package with quilt to new upstream version

2010-09-15 Thread Henrique de Moraes Holschuh
On Wed, 15 Sep 2010, Giuseppe Sacco wrote: here it fails with message No patches in series because it doesn't look for debian/patches/series but only for patches/series. You have to set the QUILT_PATCHES environment variable or tell quilt where to find the patches through its config file. man

Re: Moving package with quilt to new upstream version

2010-09-15 Thread Jordan Metzmeier
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 09/15/2010 11:58 AM, Giuseppe Sacco wrote: here it fails with message No patches in series because it doesn't look for debian/patches/series but only for patches/series. See section 3.1 of the New Maintainers Guide. Regards, - --

Re: Moving package with quilt to new upstream version

2010-09-15 Thread Giuseppe Sacco
Il giorno mer, 15/09/2010 alle 13.14 -0300, Henrique de Moraes Holschuh ha scritto: [...] man quilt explains it all. thanks IMO, you should try to get yourself better acquinted with quilt before using it, or you can end up with a mess. Right. That's why I am testing this process while

Re: Moving package with quilt to new upstream version

2010-09-15 Thread Henrique de Moraes Holschuh
On Wed, 15 Sep 2010, Giuseppe Sacco wrote: IMO, you should try to get yourself better acquinted with quilt before using it, or you can end up with a mess. Right. That's why I am testing this process while upstream only produced and rc version. I've found that using dpkg-source format

Re: Moving package with quilt to new upstream version

2010-09-15 Thread Christoph Egger
Giuseppe Sacco giuse...@eppesuigoccas.homedns.org writes: here it fails with message No patches in series because it doesn't look for debian/patches/series but only for patches/series. export QUILT_PATCHES=debian/patches -- 9FED 5C6C E206 B70A 5857 70CA 9655 22B9 D49A E731 Debian Developer |

Re: Moving package with quilt to new upstream version

2010-09-15 Thread Goswin von Brederlow
Christoph Egger christ...@debian.org writes: Giuseppe Sacco giuse...@eppesuigoccas.homedns.org writes: here it fails with message No patches in series because it doesn't look for debian/patches/series but only for patches/series. export QUILT_PATCHES=debian/patches Actually not needed.

Re: Moving package with quilt to new upstream version

2010-09-15 Thread Henrique de Moraes Holschuh
On Wed, 15 Sep 2010, Goswin von Brederlow wrote: QUILT_PATCHES=debian/patches quilt push will do the same. You only need QUILT_PATCHES for the first quilt call. Is that so? That would be good news, but it doesn't match my experience... although the last time I tried that was some months

Re: Moving package with quilt to new upstream version

2010-09-15 Thread Bernd Zeimetz
On 09/15/2010 06:33 PM, Henrique de Moraes Holschuh wrote: On Wed, 15 Sep 2010, Giuseppe Sacco wrote: IMO, you should try to get yourself better acquinted with quilt before using it, or you can end up with a mess. Right. That's why I am testing this process while upstream only produced and