Hi,
I've updated the package with the ITP bug.
Cheers,
francesco
Il giorno sab, 21/07/2007 alle 18.34 +0200, Francesco Namuri ha scritto:
Hi,
I've made a dictconv deb,
It builds these binary packages:
dictconv - Dictconv convert a dictionay file type in another dictionary file
The
Hi mentors,
eterm-themes is an orphaned package and because this I am interested in
adopting it, but i need a sponsor :)
Dear mentors,
I am looking for a sponsor for the new version 0.9.3.20060329-2
of my package eterm-themes.
It builds these binary packages:
eterm-themes - Themes for
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Russ Allbery wrote:
[...]
What I was trying to get at earlier is that I believe groff can't handle
UTF-8 input. So fixing B, if I'm correct, is certainly not local to
man-db. I believe that fixing groff to handle multibyte character sets
Dear mentors,
I am looking for a sponsor for the new version 1.4-1.1
of my package libgtkol.
It builds these binary packages:
libgtkol-docs - GTK C++ Object Layer - documentation
libgtkol1 - GTK C++ Object Layer - shared libraries
libgtkol1-dev - GTK C++ Object Layer - development files
The
On Sun, Aug 12, 2007 at 08:44:13PM -0700, Russ Allbery wrote:
Adam Borowski [EMAIL PROTECTED] writes:
Issues to fix
=
A. man output
B. groff processing
C. man input
Fixes for A. and B. are mostly local to man-db, fixing C. would be a
Debian-wide issue.
What I
David Given [EMAIL PROTECTED] writes:
The standard encoding for Japanese man pages is EUC-JP
That's no more true than the standard encoding for English text is
ASCII. The world is moving to Unicode encodings, though legacy
encodings will remain for some time.
They're also both equally
Recently I've had a bug filed against a few of my packages about
final binaries being stripped even though DEB_BUILD_OPTIONS=nostrip
is set (in an autobuild process). The bug goes on to say that it
could be that upstream is stripping the files.
Such is the case with my packages. Upstream does
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ben Finney wrote:
[...]
The standard encoding for Japanese man pages is EUC-JP
That's no more true than the standard encoding for English text is
ASCII. The world is moving to Unicode encodings, though legacy
encodings will remain for some time.
On Mon, Aug 13, 2007 at 01:24:34PM +0200, Francesco Aloe wrote:
Hi mentors,
eterm-themes is an orphaned package and because this I am interested in
adopting it, but i need a sponsor :)
Hello Francesco,
There are several issues:
1) eterm-themes is not orphaned but RFA'ed. This means I am still
Kevin Coyner [EMAIL PROTECTED] writes:
Recently I've had a bug filed against a few of my packages about
final binaries being stripped even though DEB_BUILD_OPTIONS=nostrip
is set (in an autobuild process). The bug goes on to say that it
could be that upstream is stripping the files.
Such is
Adam Borowski [EMAIL PROTECTED] writes:
The current Debian groff can produce UTF-8 output only for a narrow
range of characters, ones which happen to be present in 8 bit charsets.
It cannot handle UTF-8 input at all; on the other hand, Red Hat's
version seem to be working just fine.
Yeah, I
On Mon, 13 Aug 2007 10:14:23 -0400
Kevin Coyner [EMAIL PROTECTED] wrote:
Recently I've had a bug filed against a few of my packages about
final binaries being stripped even though DEB_BUILD_OPTIONS=nostrip
is set (in an autobuild process). The bug goes on to say that it
could be that
Kevin Coyner [EMAIL PROTECTED] writes:
Such is the case with my packages. Upstream does strip in the
Makefile. Aside from editing the Makefile using dpatch, is there
anything else that is easily done to correct this? I know this seems
straightforward, but I just wanted to ask before I start
Hi Bill,
i must apologize because i have done a mistake,a newbie error, i didn't
want hijack your package for asking a ransom. True is that this package
isn't orphaned but RFA'ed, I wrote on your Bug report logs - #313183 a
month ago without reciving an answer, so i supposed (and that was my big
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Russ Allbery wrote:
[...]
Okay, your analysis matches what I thought was going on. However, David
Given seems to be seeing something else where some man pages are already
encoded in UTF-8. So I guess I'm confused as to what's going on and what
On Monday 13 August 2007 19:38:35 Russ Allbery wrote:
Kevin Coyner [EMAIL PROTECTED] writes:
Such is the case with my packages. Upstream does strip in the
Makefile. Aside from editing the Makefile using dpatch, is there
anything else that is easily done to correct this? I know this seems
David Given [EMAIL PROTECTED] writes:
Wll... unfortunately man-db uses ISO-8859-1 for C and POSIX locales,
so transcoding would be required.
You do get lintian warnings if you try to use ISO 8859-1 characters in man
pages currently. Unfortunately, a lot of people just ignore those
Hello,
The description of your project has somehow piqued my curiosity. But, as Neil
Williams said, I think you need to explain to us how is it different from
(c)deboostrap.
What can you program do that I couldn't do with a trivial shell script? What
have you solved that would go beyond
On 10/08/07, Giovanni Mascellani [EMAIL PROTECTED] wrote:
All'incirca Thu, 9 Aug 2007 19:47:01 -0500, Raphael Geissert
[EMAIL PROTECTED] sembrerebbe aver scritto:
Hello everybody,
I've finally prepared the irrlicht package.
As I wrote many hacks to get dpkg-buildpackage successfully
Hello,
On Mon, 13 Aug 2007, Kevin Coyner wrote:
Such is the case with my packages. Upstream does strip in the
Makefile. Aside from editing the Makefile using dpatch, is there
anything else that is easily done to correct this?
Different strokes for different folks.
I got away with redefining
On 10/08/07, Brandon [EMAIL PROTECTED] wrote:
1) It appears that the irrlicht engine is incompatable with the libjpeg
engine that comes with debian. I have attached a log with errors. This
is from compiling, and then running, 02.Quake3Map.
However, after checking the versions, it seems
21 matches
Mail list logo
