Here is how I resolved it:
1) Keep [EMAIL PROTECTED] (ISO-8859-15) as a locale.
2) Uncommented charset utf-8 in .gnupg/gpg.conf
3) Convert all files in debian/* to UTF-8.
4) Build package using favorite tools (e.g. debuild, etc.).
Odd fonts will show, but debsign will still work OK.
Thanks
On Fri, Apr 02, 2004 at 01:29:31AM +0200, Goswin von Brederlow wrote:
Jeroen van Wolffelaar [EMAIL PROTECTED] writes:
In a .dsc, there is a 'Source:' entry (only if source pkg != bin pkg,
and/or source versionnr != bin versionnr), which points to the source.
So no need to fiddle with the
Hello,
I'm looking for a sponsor for my package gkrellshoot.
---
Package: wnpp
Severity: wishlist
* Package name: gkrellshoot
Version : 0.4.1
Upstream Author : M.R.Muthu Kumar [EMAIL PROTECTED]
* URL : http://gkrellshoot.sourceforge.net/
* License : GPL
On Thu, Apr 01, 2004 at 11:30:54PM +0200, Goswin von Brederlow wrote:
Jeroen van Wolffelaar [EMAIL PROTECTED] writes:
On Thu, Apr 01, 2004 at 05:09:09AM +0200, Goswin von Brederlow wrote:
Andreas Barth [EMAIL PROTECTED] writes:
The version number has no effect at all whether katie
Jeroen van Wolffelaar [EMAIL PROTECTED] writes:
On Fri, Apr 02, 2004 at 01:29:31AM +0200, Goswin von Brederlow wrote:
Jeroen van Wolffelaar [EMAIL PROTECTED] writes:
In a .dsc, there is a 'Source:' entry (only if source pkg != bin pkg,
and/or source versionnr != bin versionnr), which
Jeroen van Wolffelaar [EMAIL PROTECTED] writes:
On Thu, Apr 01, 2004 at 11:30:54PM +0200, Goswin von Brederlow wrote:
Jeroen van Wolffelaar [EMAIL PROTECTED] writes:
...
Katie ensures that the initial upload does in fact contain
source, or rather it checks if source for an upload are
On Fri, Apr 02, 2004 at 12:42:01PM +0200, Jeroen van Wolffelaar wrote:
On Thu, Apr 01, 2004 at 11:30:54PM +0200, Goswin von Brederlow wrote:
Jeroen van Wolffelaar [EMAIL PROTECTED] writes:
Err, why should katie do that based on the version number? That's very
unlikely, katie can simply
(moved to d-d)
On Fri, Apr 02, 2004 at 12:28:32PM +0100, Colin Watson wrote:
On Fri, Apr 02, 2004 at 11:53:43AM +0200, Jeroen van Wolffelaar wrote:
Any .deb indicates its source, including binary-only NMU's,
I'm afraid you're wrong there; I have some binNMUed packages here and
they do
On Fri, Apr 02, 2004 at 04:29:54PM +0200, Jeroen van Wolffelaar wrote:
IMHO, this is a suboptimal solution. In theory, with source header you
can always track the source.
See Bug#62529.
Cheers,
aj
--
Anthony Towns [EMAIL PROTECTED] http://azure.humbug.org.au/~aj/
I don't speak for anyone
On Fri, Apr 02, 2004 at 04:29:54PM +0200, Jeroen van Wolffelaar wrote:
On Fri, Apr 02, 2004 at 12:28:32PM +0100, Colin Watson wrote:
On Fri, Apr 02, 2004 at 11:53:43AM +0200, Jeroen van Wolffelaar wrote:
Any .deb indicates its source, including binary-only NMU's,
I'm afraid you're wrong
On Fri, Apr 02, 2004 at 04:35:13PM +0100, Colin Watson wrote:
On Fri, Apr 02, 2004 at 04:29:54PM +0200, Jeroen van Wolffelaar wrote:
On Fri, Apr 02, 2004 at 12:28:32PM +0100, Colin Watson wrote:
On Fri, Apr 02, 2004 at 11:53:43AM +0200, Jeroen van Wolffelaar wrote:
Any .deb indicates its
On Fri, Apr 02, 2004 at 07:09:51PM +0200, Jeroen van Wolffelaar wrote:
Pro the non-changelog thing is, that one can order a buildd to recompile
with correct version number, while currently manual changelog editing is
needed.
Actually, sbuild already has a --make-binNMU switch which does the
hello
I'm looking for sponsers
intresse??
contact me on dereymaekermats
@hotmail.com
On Fri, Apr 02, 2004 at 07:20:23PM +0400, Al Nikolov wrote:
Hi, all
Point me to sources describing the Debian way of backporting pls
Mmm, that is indeed not finished yet at www.backports.org
( http://www.backports.org/not_finished.yet )
--
Regards,
Al Nikolov
Cheers
Geert
On 2004-04-02 Bartosz Fenski aka fEnIo [EMAIL PROTECTED] wrote:
I would like to package some very useful set of utilities[1].
It depends on library of the same author[2].
Unfortunatelly SONAME of this library changes with every new version.
And to make this problem more annoying, new
On Fri, Apr 02, 2004 at 10:29:47PM +0200, Andreas Metzler wrote:
I would like to package some very useful set of utilities[1].
It depends on library of the same author[2].
Unfortunatelly SONAME of this library changes with every new version.
And to make this problem more annoying, new
Colin Watson [EMAIL PROTECTED] writes:
On Fri, Apr 02, 2004 at 07:09:51PM +0200, Jeroen van Wolffelaar wrote:
Pro the non-changelog thing is, that one can order a buildd to recompile
with correct version number, while currently manual changelog editing is
needed.
Actually, sbuild
Bartosz Fenski aka fEnIo [EMAIL PROTECTED] writes:
Hello.
I would like to package some very useful set of utilities[1].
It depends on library of the same author[2].
Unfortunatelly SONAME of this library changes with every new version.
And to make this problem more annoying, new releases
On Fri, Apr 02, 2004 at 11:18:11PM +0200, Goswin von Brederlow wrote:
Please give me some hints/suggestions what should be done in such
situation? Are there any packages with that situation in our archive?
Since you are the only one using I would say link it in
static. Problem solved.
First off I'll admit I only gave a quick glance at the Debian New
Maintainters' Corner, but from what I saw, it looked like the first
step wasn't an automated thing. It sounds like the first thing I need to
do it get to know some of the current developers...
In summary the reason I want to
First off I'll admit I only gave a quick glance at the Debian New
Maintainters' Corner, but from what I saw, it looked like the first
step wasn't an automated thing. It sounds like the first thing I need to
do it get to know some of the current developers...
In summary the reason I want to
Ok, would just like to apologize for that little snafu. Not the best
start on a mailing list. Ugh.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
On 2004-04-02 Benjamin Cutler [EMAIL PROTECTED] wrote:
First off I'll admit I only gave a quick glance at the Debian New
Maintainters' Corner, but from what I saw, it looked like the first
step wasn't an automated thing. It sounds like the first thing I need to
do it get to know some of the
I need some assistance with my bootsplash packages. It seems that the
bootsplash-theme* templates are not getting installed correctly and cannot
be seen by the bootsplash package. I don't know how to fix this.
--
Matthew A. Nicholson
Matt-Land.com
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
On Fri, Mar 26, 2004 at 01:30:37AM -0400, Rodrigo Henriquez M. wrote:
Package: wnpp
Severity: normal
I used atftp a lot and I would like to be the
new mantainer for this package.
-- System Information:
Debian Release: testing/unstable
APT prefers testing
APT policy: (500, 'testing')
Hi,
I have started work on packaging the Bouncy Castle Crypto libraries
for Java (bug #234048). I think I have most everything in place for a
first stab, but I can't figure out where to put the signed jar so that
dpkg-buildpackage won't complain.
Basically, the source of the Bouncy Castle Crypto
Here is how I resolved it:
1) Keep [EMAIL PROTECTED] (ISO-8859-15) as a locale.
2) Uncommented charset utf-8 in .gnupg/gpg.conf
3) Convert all files in debian/* to UTF-8.
4) Build package using favorite tools (e.g. debuild, etc.).
Odd fonts will show, but debsign will still work OK.
Thanks
On Fri, Apr 02, 2004 at 01:29:31AM +0200, Goswin von Brederlow wrote:
Jeroen van Wolffelaar [EMAIL PROTECTED] writes:
In a .dsc, there is a 'Source:' entry (only if source pkg != bin pkg,
and/or source versionnr != bin versionnr), which points to the source.
So no need to fiddle with the
Hello,
I'm looking for a sponsor for my package gkrellshoot.
---
Package: wnpp
Severity: wishlist
* Package name: gkrellshoot
Version : 0.4.1
Upstream Author : M.R.Muthu Kumar [EMAIL PROTECTED]
* URL : http://gkrellshoot.sourceforge.net/
* License : GPL
On Thu, Apr 01, 2004 at 11:30:54PM +0200, Goswin von Brederlow wrote:
Jeroen van Wolffelaar [EMAIL PROTECTED] writes:
On Thu, Apr 01, 2004 at 05:09:09AM +0200, Goswin von Brederlow wrote:
Andreas Barth [EMAIL PROTECTED] writes:
The version number has no effect at all whether katie
Jeroen van Wolffelaar [EMAIL PROTECTED] writes:
On Fri, Apr 02, 2004 at 01:29:31AM +0200, Goswin von Brederlow wrote:
Jeroen van Wolffelaar [EMAIL PROTECTED] writes:
In a .dsc, there is a 'Source:' entry (only if source pkg != bin pkg,
and/or source versionnr != bin versionnr), which
Jeroen van Wolffelaar [EMAIL PROTECTED] writes:
On Thu, Apr 01, 2004 at 11:30:54PM +0200, Goswin von Brederlow wrote:
Jeroen van Wolffelaar [EMAIL PROTECTED] writes:
...
Katie ensures that the initial upload does in fact contain
source, or rather it checks if source for an upload are
On Fri, Apr 02, 2004 at 11:53:43AM +0200, Jeroen van Wolffelaar wrote:
On Fri, Apr 02, 2004 at 01:29:31AM +0200, Goswin von Brederlow wrote:
Jeroen van Wolffelaar [EMAIL PROTECTED] writes:
In a .dsc, there is a 'Source:' entry (only if source pkg != bin pkg,
and/or source versionnr != bin
On Fri, Apr 02, 2004 at 12:42:01PM +0200, Jeroen van Wolffelaar wrote:
On Thu, Apr 01, 2004 at 11:30:54PM +0200, Goswin von Brederlow wrote:
Jeroen van Wolffelaar [EMAIL PROTECTED] writes:
Err, why should katie do that based on the version number? That's very
unlikely, katie can simply
(moved to d-d)
On Fri, Apr 02, 2004 at 12:28:32PM +0100, Colin Watson wrote:
On Fri, Apr 02, 2004 at 11:53:43AM +0200, Jeroen van Wolffelaar wrote:
Any .deb indicates its source, including binary-only NMU's,
I'm afraid you're wrong there; I have some binNMUed packages here and
they do
On Fri, Apr 02, 2004 at 04:29:54PM +0200, Jeroen van Wolffelaar wrote:
IMHO, this is a suboptimal solution. In theory, with source header you
can always track the source.
See Bug#62529.
Cheers,
aj
--
Anthony Towns [EMAIL PROTECTED] http://azure.humbug.org.au/~aj/
I don't speak for anyone
Hi, all
Point me to sources describing the Debian way of backporting pls
--
Regards,
Al Nikolov
On Fri, Apr 02, 2004 at 04:29:54PM +0200, Jeroen van Wolffelaar wrote:
On Fri, Apr 02, 2004 at 12:28:32PM +0100, Colin Watson wrote:
On Fri, Apr 02, 2004 at 11:53:43AM +0200, Jeroen van Wolffelaar wrote:
Any .deb indicates its source, including binary-only NMU's,
I'm afraid you're wrong
On Fri, Apr 02, 2004 at 04:35:13PM +0100, Colin Watson wrote:
On Fri, Apr 02, 2004 at 04:29:54PM +0200, Jeroen van Wolffelaar wrote:
On Fri, Apr 02, 2004 at 12:28:32PM +0100, Colin Watson wrote:
On Fri, Apr 02, 2004 at 11:53:43AM +0200, Jeroen van Wolffelaar wrote:
Any .deb indicates its
On Fri, Apr 02, 2004 at 07:09:51PM +0200, Jeroen van Wolffelaar wrote:
Pro the non-changelog thing is, that one can order a buildd to recompile
with correct version number, while currently manual changelog editing is
needed.
Actually, sbuild already has a --make-binNMU switch which does the
Hello.
I would like to package some very useful set of utilities[1].
It depends on library of the same author[2].
Unfortunatelly SONAME of this library changes with every new version.
And to make this problem more annoying, new releases shows very often
(about one version per two weeks).
And
hello
I'm looking for sponsers
intresse??
contact me on dereymaekermats
@hotmail.com
On Fri, Apr 02, 2004 at 07:20:23PM +0400, Al Nikolov wrote:
Hi, all
Point me to sources describing the Debian way of backporting pls
Mmm, that is indeed not finished yet at www.backports.org
( http://www.backports.org/not_finished.yet )
--
Regards,
Al Nikolov
Cheers
Geert
On 2004-04-02 Bartosz Fenski aka fEnIo [EMAIL PROTECTED] wrote:
I would like to package some very useful set of utilities[1].
It depends on library of the same author[2].
Unfortunatelly SONAME of this library changes with every new version.
And to make this problem more annoying, new
On Fri, Apr 02, 2004 at 10:29:47PM +0200, Andreas Metzler wrote:
I would like to package some very useful set of utilities[1].
It depends on library of the same author[2].
Unfortunatelly SONAME of this library changes with every new version.
And to make this problem more annoying, new
Colin Watson [EMAIL PROTECTED] writes:
On Fri, Apr 02, 2004 at 07:09:51PM +0200, Jeroen van Wolffelaar wrote:
Pro the non-changelog thing is, that one can order a buildd to recompile
with correct version number, while currently manual changelog editing is
needed.
Actually, sbuild
Bartosz Fenski aka fEnIo [EMAIL PROTECTED] writes:
Hello.
I would like to package some very useful set of utilities[1].
It depends on library of the same author[2].
Unfortunatelly SONAME of this library changes with every new version.
And to make this problem more annoying, new releases
On Fri, Apr 02, 2004 at 11:18:11PM +0200, Goswin von Brederlow wrote:
Please give me some hints/suggestions what should be done in such
situation? Are there any packages with that situation in our archive?
Since you are the only one using I would say link it in
static. Problem solved.
First off I'll admit I only gave a quick glance at the Debian New
Maintainters' Corner, but from what I saw, it looked like the first
step wasn't an automated thing. It sounds like the first thing I need to
do it get to know some of the current developers...
In summary the reason I want to
Ok, would just like to apologize for that little snafu. Not the best
start on a mailing list. Ugh.
On 2004-04-02 Benjamin Cutler [EMAIL PROTECTED] wrote:
First off I'll admit I only gave a quick glance at the Debian New
Maintainters' Corner, but from what I saw, it looked like the first
step wasn't an automated thing. It sounds like the first thing I need to
do it get to know some of the
I need some assistance with my bootsplash packages. It seems that the
bootsplash-theme* templates are not getting installed correctly and cannot
be seen by the bootsplash package. I don't know how to fix this.
--
Matthew A. Nicholson
Matt-Land.com
On Fri, Mar 26, 2004 at 01:30:37AM -0400, Rodrigo Henriquez M. wrote:
Package: wnpp
Severity: normal
I used atftp a lot and I would like to be the
new mantainer for this package.
-- System Information:
Debian Release: testing/unstable
APT prefers testing
APT policy: (500, 'testing')
Hi,
I have started work on packaging the Bouncy Castle Crypto libraries
for Java (bug #234048). I think I have most everything in place for a
first stab, but I can't figure out where to put the signed jar so that
dpkg-buildpackage won't complain.
Basically, the source of the Bouncy Castle Crypto
54 matches
Mail list logo
