At the risk of CC'ing too many people:
Quoting David Lloyd [EMAIL PROTECTED]:
Roger et al,
Again, I would reccomend using dpkg-buildpackage, even if you only
intend to generate the source upload. If you name the source tarball
(upstream source) pkg_version.orig.tar.gz and are in the
On Tue, Apr 15, 2003 at 10:43:12AM +0930, David Lloyd wrote:
Roger et al,
Again, I would reccomend using dpkg-buildpackage, even if you only
intend to generate the source upload. If you name the source tarball
(upstream source) pkg_version.orig.tar.gz and are in the source
tree (with
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Roger!
Am Montag, 14. April 2003 06:47 schrieb Roger Ward:
How are you generating the .diff.gz files? dpkg-buildpackage should name
them something like: pysol_4.81.orig.tar.gz and pysol_4.81-1.diff.gz. If
anyone knows a better way than
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tuesday 15 Apr 2003 12:54, Alexander Nofftz [EMAIL PROTECTED]
wrote:
However I got a warning from dpkg-source that the original source of
pysol-cardsets_4.40 will not be provided with pysol-cardsets_4.40-2.
Has this something to do with the -2,
Hi,
However I got a warning from dpkg-source that the original source of
pysol-cardsets_4.40 will not be provided with pysol-cardsets_4.40-2. Has this
something to do with the -2, the second Debian release?
Yes. See the manpage, which also documents the option to force generating
a tarball.
First (forgive me if you've stated it already) is this a native debian package?
I.e. are you developing it for debian, or are you packaging it?
How are you generating the .diff.gz files? dpkg-buildpackage should name them
something like: pysol_4.81.orig.tar.gz and pysol_4.81-1.diff.gz. If
Hi Roger!
Am Mon, Apr 14, 2003 at 12:47:43AM -0400 schrieb Roger Ward:
First (forgive me if you've stated it already) is this a native debian
package?
I.e. are you developing it for debian, or are you packaging it?
I'm packaging it, adopting the debianized version of Adam Klein. The
Alexander Nofftz wrote:
How are you generating the .diff.gz files? dpkg-buildpackage should name them
something like: pysol_4.81.orig.tar.gz and pysol_4.81-1.diff.gz. If anyone
knows a better way than dpkg-buildpackage to generate the diff let me know...
I generated them manually by using diff
Quoting Alexander Nofftz [EMAIL PROTECTED]:
I'm packaging it, adopting the debianized version of Adam Klein. The
upstream
sources can be found at: http://www.oberhumer.com/opensource/pysol/
How are you generating the .diff.gz files?
I generated them manually by using diff directy. I
Roger et al,
Again, I would reccomend using dpkg-buildpackage, even if you only
intend to generate the source upload. If you name the source tarball
(upstream source) pkg_version.orig.tar.gz and are in the source
tree (with /debian/ setup) it should generate the .diff.gz based on
the last
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Roger!
Am Dienstag, 8. April 2003 00:46 schrieb Roger Ward:
Please don't think I am suggesting your build process should involve three
source tarballs (i'm not the expert in Debian Ways To Do Things), but take
a look at Apache and how it is
Hi Folks!
I've still not found a sponsor for my adopted PySol packages. There are still
arriving new bug reports in the BTS for PySol that I've allready fixed in the
new version.
deb[-src] http://server.alexnofftz.de/~alex/pysol/ ./
I've signed my GPG key by a DD, but I want someone to
Why are you not uploading his source, with Debian patches in a .diff?
Is your package IMPOSSIBLE to deliver this way?
-Roger
Quoting Alexander Nofftz [EMAIL PROTECTED]:
Hi Folks!
I've still not found a sponsor for my adopted PySol packages. There are still
arriving new bug reports in
Hi!
Am Mon, Apr 07, 2003 at 06:46:08PM -0400 schrieb Roger Ward:
Please don't think I am suggesting your build process should involve three
source tarballs (i'm not the expert in Debian Ways To Do Things), but take a
look at Apache and how it is built. Many different patches, tars, etc are
14 matches
Mail list logo
