Bug#202593: eSNACC public licence still missing from v1.7 + Debian contributions

2004-07-12 Thread Martin Quinson
[please keep the debian bug in CC for logging purposes]

Hello,

In http://www.imc.org/imc-snacc/mail-archive/msg00282.html that it would be
a good idea to include the eSNACC public licence within the archive. As
version 1.7, it is still not done.

Could you please schedule that for the next release (ie do in your CVS?) ?


That being said, I wanted to signal that there is snacc is part of the
Debian distribution. It resulted in small changes to the program. You can
find a compressed patch containing all those changes at:
http://http.us.debian.org/debian/pool/main/s/snacc/snacc_1.3bbn-5.1.diff.gz
(ignore anything within the debian/ directory, of course).

Moreover, a patch was provided by a debian user (even if not included yet).
More about that here: 
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=202593


I would love it you could review those patches, and integrate them in your
tree if they seem relevant or explain why if not (so that I can forward this
information to the patch authors).


Thanks for your time, and for taking over the maintainership of this software.
Mt.

PS: Please note that I'm not even member of Debian, but a simple user.

-- 
Those are my principles, and if you don't like them... well, I have others.
  -- Groucho Marx
  



Bug#202593: eSNACC public licence still missing from v1.7 + Debian contributions

2004-07-12 Thread Martin Quinson
[please keep the debian bug in CC for logging purposes]

Hello,

In http://www.imc.org/imc-snacc/mail-archive/msg00282.html that it would be
a good idea to include the eSNACC public licence within the archive. As
version 1.7, it is still not done.

Could you please schedule that for the next release (ie do in your CVS?) ?


That being said, I wanted to signal that there is snacc is part of the
Debian distribution. It resulted in small changes to the program. You can
find a compressed patch containing all those changes at:
http://http.us.debian.org/debian/pool/main/s/snacc/snacc_1.3bbn-5.1.diff.gz
(ignore anything within the debian/ directory, of course).

Moreover, a patch was provided by a debian user (even if not included yet).
More about that here: 
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=202593


I would love it you could review those patches, and integrate them in your
tree if they seem relevant or explain why if not (so that I can forward this
information to the patch authors). That would allow me to propose cleanups
to the debian package "maintainer".


Thanks for your time, and for taking over the maintainership of this software.
Mt.

PS: Please note that I'm not even member of Debian, but a simple user.

PS to reader of the Debian bug log: this is dupplicated because I was stupid
enough to send the previous mail to the majordomo istead of the imc mailling
list...

-- 
Those are my principles, and if you don't like them... well, I have others.
  -- Groucho Marx
  




Bug#249740: More info

2004-07-16 Thread Martin Quinson
People interrested in snacc in Debian may be find this link interesting:
http://lists.debian.org/debian-qa/2004/07/msg00012.html

Thanks, Mt.

-- 
Everything should be made as simple as possible but not simpler.
  -- Albert Einstein



Bug#202593: [Joseph.Grone@DigitalNet.com: RE: eSNACC public licence still missing from v1.7 + Debian contributions]

2004-07-29 Thread Martin Quinson
Received privately.
Mt.

- Forwarded message from "Grone, Joseph" <[EMAIL PROTECTED]> -

Subject: RE: eSNACC public licence still missing from v1.7 + Debian 
contributions
Date: Fri, 16 Jul 2004 12:10:22 -0400
From: "Grone, Joseph" <[EMAIL PROTECTED]>
To: Martin Quinson <[EMAIL PROTECTED]>
Cc: "Joseph, Susan" <[EMAIL PROTECTED]>

Martin,
 
I am not sure why it didn't post to the mailing list.  I will look into the 
licensing issue.  I think the public license resides in the ./SNACC/docs 
directory in the zip file in our documentation.  If not, that is something that 
I will add for the next release.  I will also take a look at your changes, and 
contact you back.  We have recently moved to using CMMI in our development 
process, so any changes we want to make will have to be approved before a board 
before they can be incorporated into a release.  We have already set our 
requirements for the next release before the board, so I am unsure as to wether 
any of your changes will be able to be made for our next release.  Thank you.
 
--Joseph

    -Original Message- 
From: Martin Quinson [mailto:[EMAIL PROTECTED] 
Sent: Fri 7/16/2004 12:58 AM 
To: Grone, Joseph 
Cc: 
Subject: eSNACC public licence still missing from v1.7 + Debian 
contributions



After 3 days, the archive does not show my message, and I've got no 
answer.
I thus send it to you directly to workaround any technical issue with 
the
mailing list.

Thanks for your time,
Mt.

- Forwarded message from mquinson -

Date: Mon, 12 Jul 2004 18:12:44 -0700
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Subject: eSNACC public licence still missing from v1.7 + Debian 
contributions

[please keep the debian bug in CC for logging purposes]

Hello,

In http://www.imc.org/imc-snacc/mail-archive/msg00282.html that it 
would be
a good idea to include the eSNACC public licence within the archive. As
version 1.7, it is still not done.

Could you please schedule that for the next release (ie do in your 
CVS?) ?


That being said, I wanted to signal that there is snacc is part of the
Debian distribution. It resulted in small changes to the program. You 
can
find a compressed patch containing all those changes at:

http://http.us.debian.org/debian/pool/main/s/snacc/snacc_1.3bbn-5.1.diff.gz
(ignore anything within the debian/ directory, of course).

Moreover, a patch was provided by a debian user (even if not included 
yet).
More about that here:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=202593


I would love it you could review those patches, and integrate them in 
your
tree if they seem relevant or explain why if not (so that I can forward 
this
information to the patch authors). That would allow me to propose 
cleanups
to the debian package "maintainer".


Thanks for your time, and for taking over the maintainership of this 
software.
Mt.

PS: Please note that I'm not even member of Debian, but a simple user.

PS to reader of the Debian bug log: this is dupplicated because I was 
stupid
enough to send the previous mail to the majordomo istead of the imc 
mailling
list...

--
Those are my principles, and if you don't like them... well, I have 
others.
  -- Groucho Marx
 


- End forwarded message -



- End forwarded message -

-- 
Computers make very fast, very accurate mistakes.



Bug#196073: gtk-doc-tools and #196073

2003-06-26 Thread Martin Quinson
On Wed, Jun 25, 2003 at 05:08:32PM +0200, J.H.M. Dassen (Ray) wrote:
> On Wed, Jun 25, 2003 at 10:53:58 +0200, Martin Quinson wrote:
> > you uploaded a new version of gtk-doc the 2003-06-19 (maintainer:
> > debian-qa) to fix a few bugs, but you forgot the #196073 one, which were
> > marked pending by the maintainer before orphaning, and not fixed.
> 
> I didn't forget it. I was concerned only about the issues effecting the
> libgsf package which I maintain.

Ok, I'll have to find another DD interested in qa to upload this then.

> > Could you please reupload this package with the needed dependency ?
> 
> No. Reading #196073 it talks about packages that use both gtk-doc-tools and
> automake at build time and don't declare their build dependencies properly.
> IMO that's a bug in those packages, not in gtk-doc-tools.

Not exactly. gtk-doc-tools is unusable in projects (not [only] package, user
projects) when gnome-common isn't installed because you have to put
GNOME_GTKDOC_CHECK in your configure.{ac,in}. And this macro is declared in
files from gnome-common.

So, gtk-doc-tools is unusable if installed as is without gnome-common if you
do what is documented in this package. Of course, you can avoid using this
AC macro, and do it manually, but how ?

Moreover, your argument saying that each package depending on gtk-doc-tools
have to put the dependency on gnome-common themselves seems quite suporious
to me. It could be used to argument that each program willing to use
gnome-canvas have to declare the dependency on gnome-canvas's dependencies
by itself. :)

And last point, as said in the BR, I would be ok with a 'suggest'. I only
think that when stuff fails because of missing extra package, the first
package should give an hint to the user on how to fix this.

Bye, Mt.

-- 
Moi, Adam et Ève, j'y crois plus tu vois, parce que je suis pas un
idiot : la pomme, ça peut pas être mauvais, c'est plein de pectine...
  -- Jean Claude Van Damme



Bug#235831: cdtool: Please switch to gettext-based debconf templates

2004-03-02 Thread Martin Quinson
Package: cdtool
Version: n/a
Severity: wishlist
Tags: patch l10n

Using the "new" gettext format for debconf templates helps for templates
translations. For instance, detecting outdated or untranslated strings 
becomes considerably easier. It also keeps track of who did which
translation.

The attached patch does the required modifications :
- debian/control modification for dependencies (see below)
- execute "debconf-gettextize debian/*templates*" 
- mark the right strings as translatable in the templates (see below)
- update the style to the best current practice (see below)


If you want to reproduce this by yourself instead of applying the
patch, you have to do:

- install po-debconf on your system
- go to the debian directory
- read man po-debconf..:-)
- run "debconf-gettextize *.templates"
- read the output
- change Build-Depends or Build-Depends-Indep (see below)
  They should list "po-debconf"
- update the templates file to mark as translatable only the fields
  which should (ie, not the one containing stuff which cannot be
  translated such as kernel module name, and neither the one not
  shown to the users), and improve the style to follow the dstg.

For more details, see po-debconf documentation, especially "man 7
po-debconf"

Read this if you're concerned with backports :


Please note that the suggested modifications will make your
package a little bit harder to backport to earlier Debian releases. If
this is a concern to you, you may try to adopt the method used by the
openssh package and detailed by Colin Watson in
http://lists.debian.org/debian-i18n/2003/debian-i18n-200307/msg00026.html

This patch does not includes this method as this would make it too
invasive, IMHO. So, preserving backportability is up to you...

The rest of the story :
-
While I was working on the convertion to po-debconf, I noticed that the
templates of your package may be easily improved by applying the advices
contained at the following address:

http://people.debian.org/~bubulle/dtsg.txt

I applied the advices from this document concerning the short descriptions,
and I think that no extra work is needed on the templates. But feel free to
improve them further, if you want... Don't get me wrong, I don't want to
criticize, I just want the template to reach a translatable state (ie quite
stable) rather soon.

Once the switch is achieved, and the style improvement are done, I 
guess that you will receive translations of your templates rather soon. You
may consider asking on the debian-i18n@lists.debian.org mailing list for
translations once you think that your templates are in a sort of final state
where they won't be modified in the near future.


Thanks for helping the translators, and thus your non english speaker
end-users. 

Bye, Mt.

PS: I know that this package is orphaned, but according to my stats, that
the most important package (wrt popcon) not having a po-debconf switch bug
report. So here you are..
http://graal.ens-lyon.fr/~mquinson/debian/switch/popcon.html

-- System Information:
Debian Release: testing/unstable
Architecture: i386
Kernel: Linux galadriel 2.4.22 #1 ven nov 21 16:02:19 CET 2003 i686
Locale: LANG=fr_FR.ISO-8859-1, LC_CTYPE=fr_FR.ISO-8859-1

diff -ruN cdtool-2.1.5.ori/debian/control cdtool-2.1.5/debian/control
--- cdtool-2.1.5.ori/debian/control 2004-03-02 10:09:45.0 -0800
+++ cdtool-2.1.5/debian/control 2004-03-02 10:11:01.0 -0800
@@ -2,11 +2,12 @@
 Section: sound
 Priority: optional
 Maintainer: Debian QA Group <[EMAIL PROTECTED]>
+Build-Depends: po-debconf
 Standards-Version: 3.6.1
 
 Package: cdtool
 Architecture: any
-Depends: ${shlibs:Depends}, debconf (>= 0.5.00)
+Depends: ${shlibs:Depends}, debconf (>= 1.2.0)
 Description: some text-based commands for managing a CD
  cdtool contains cdplay, cdeject, cdstop, cdpause, and several other
  utilities that let you control your CD-ROM drive from a command
diff -ruN cdtool-2.1.5.ori/debian/po/POTFILES.in 
cdtool-2.1.5/debian/po/POTFILES.in
--- cdtool-2.1.5.ori/debian/po/POTFILES.in  1969-12-31 16:00:00.0 
-0800
+++ cdtool-2.1.5/debian/po/POTFILES.in  2004-03-02 10:11:30.0 -0800
@@ -0,0 +1 @@
+[type: gettext/rfc822deb] templates
diff -ruN cdtool-2.1.5.ori/debian/po/templates.pot 
cdtool-2.1.5/debian/po/templates.pot
--- cdtool-2.1.5.ori/debian/po/templates.pot1969-12-31 16:00:00.0 
-0800
+++ cdtool-2.1.5/debian/po/templates.pot2004-03-02 10:12:40.0 
-0800
@@ -0,0 +1,40 @@
+#
+#Translators, if you are not familiar with the PO format, gettext
+#documentation is worth reading, especially sections dedicated to
+#this format, e.g. by running:
+# info -n '(gettext)PO Files'
+# info -n '(gettext)Header Entry'
+#
+#Some information specific to po-debconf are available at
+#/usr/share/doc/po-debconf/README-trans
+# or http://www.debian.org/intl/l10n/po-debconf/README-trans

Bug#235834: multi-gnome-terminal: Please switch to gettext-based debconf templates

2004-03-02 Thread Martin Quinson
Package: multi-gnome-terminal
Version: n/a
Severity: wishlist
Tags: patch l10n


Using the "new" gettext format for debconf templates helps for templates
translations. For instance, detecting outdated or untranslated strings 
becomes considerably easier. It also keeps track of who did which
translation.

The attached patch does the required modifications :
- debian/control modification for dependencies (see below)
- execute "debconf-gettextize debian/*templates*" 
- mark the right strings as translatable in the templates (see below)
- update the style to the best current practice (see below)



If you want to reproduce this by yourself instead of applying the
patch, you have to do:

- install po-debconf on your system
- go to the debian directory
- read man po-debconf..:-)
- run "debconf-gettextize *.templates"
- read the output
- change Build-Depends or Build-Depends-Indep (see below)
  They should list "debhelper (>= 4.1.16)" (debhelper depends upon 
  po-debconf) since you use debhelper.
- update the templates file to mark as translatable only the fields
  which should (ie, not the one containing stuff which cannot be
  translated such as kernel module name, and neither the one not
  shown to the users), and improve the style to follow the dstg.

For more details, see po-debconf documentation, especially "man 7
po-debconf"

Read this if you're concerned with backports :


Please note that the suggested modifications will make your
package a little bit harder to backport to earlier Debian releases. If
this is a concern to you, you may try to adopt the method used by the
openssh package and detailed by Colin Watson in
http://lists.debian.org/debian-i18n/2003/debian-i18n-200307/msg00026.html

This patch does not includes this method as this would make it too
invasive, IMHO. So, preserving backportability is up to you...

The rest of the story :
-
While I was working on the convertion to po-debconf, I noticed that the
templates of your package may be easily improved by applying the advices
contained at the following address:

http://people.debian.org/~bubulle/dtsg.txt

Please read this document, and improve your templates. For example, the
first one smells like a debconf abuse, even if I'm not completely sure of
it. The second one may be placed in NEWS.Debian, where it really belongs.

You should also explain the kind of problem preventing you from doing so
automatically. I mean, if that's dangerous, do not ask your user to do so
blindly. If not, do so automatically ;)

Don't get me wrong, I don't want to criticize, I just want the template to
reach a translatable state (ie quite stable) rather soon.

Once the switch is achieved, and the style improvement are done, I 
guess that you will receive translations of your templates rather soon. You
may consider asking on the debian-i18n@lists.debian.org mailing list for
translations once you think that your templates are in a sort of final state
where they won't be modified in the near future.


Thanks for helping the translators, and thus your non english speaker
end-users. 

Bye, Mt.



-- System Information:
Debian Release: testing/unstable
Architecture: i386
Kernel: Linux galadriel 2.4.22 #1 ven nov 21 16:02:19 CET 2003 i686
Locale: LANG=fr_FR.ISO-8859-1, LC_CTYPE=fr_FR.ISO-8859-1

diff -ruN multi-gnome-terminal-1.6.2.ori/debian/control 
multi-gnome-terminal-1.6.2/debian/control
--- multi-gnome-terminal-1.6.2.ori/debian/control   2004-03-02 
10:21:30.0 -0800
+++ multi-gnome-terminal-1.6.2/debian/control   2004-03-02 10:21:47.0 
-0800
@@ -2,14 +2,14 @@
 Section: x11
 Priority: optional
 Maintainer: Debian QA Group <[EMAIL PROTECTED]>
-Build-Depends: debhelper (>> 4.0.0), gettext, libgnome-dev (>= 1.4.2-3), 
liborbit-dev, flex, bison, libgtk1.2-dev, xlibs-dev, libxml-dev, 
libgdk-pixbuf-gnome-dev (>= 0.18.0-3), libglade-gnome0-dev, intltool, 
libbz2-dev, libgtkxmhtml-dev, zlib1g-dev, scrollkeeper, jade, docbook-dsssl
+Build-Depends: debhelper (>= 4.1.16), gettext, libgnome-dev (>= 1.4.2-3), 
liborbit-dev, flex, bison, libgtk1.2-dev, xlibs-dev, libxml-dev, 
libgdk-pixbuf-gnome-dev (>= 0.18.0-3), libglade-gnome0-dev, intltool, 
libbz2-dev, libgtkxmhtml-dev, zlib1g-dev, scrollkeeper, jade, docbook-dsssl
 Build-Depends-Indep: gtk-doc-tools
 Standards-Version: 3.6.1
 
 Package: multi-gnome-terminal
 Section: gnome
 Architecture: any
-Pre-Depends: debconf (>= 0.2.17)
+Pre-Depends: debconf (>= 1.2.0)
 Depends: ${shlibs:Depends}
 Provides: x-terminal-emulator
 Recommends: multi-gnome-terminal-doc
diff -ruN multi-gnome-terminal-1.6.2.ori/debian/multi-gnome-terminal.templates 
multi-gnome-terminal-1.6.2/debian/multi-gnome-terminal.templates
--- multi-gnome-terminal-1.6.2.ori/debian/multi-gnome-terminal.templates
2004-03-02 10:21:31.0 -0800
+++ multi-gnome-terminal-1.6.2/debian/multi-gnome-terminal.templates
2004-03-02 10:22:09.0 -0800
@@ -1,6 +1,6 @@
 Template:

Bug#245186: hunglish: Please switch to gettext-based debconf templates

2004-04-21 Thread Martin Quinson
Package: hunglish
Version: n/a
Severity: wishlist
Tags: patch l10n

Using the "new" gettext format for debconf templates helps for templates
translations. For instance, detecting outdated or untranslated strings 
becomes considerably easier. It also keeps track of who did which
translation.

The attached patch does the required modifications :
- debian/control modification for dependencies (see below)
- execute "debconf-gettextize debian/*templates*" 
- mark the right strings as translatable in the templates (see below)
- removed files left by debconf-gettextize (*.templates.XX which are the
  old-style translations and now live in debian/po/XX.po)

The previously existing translation were not lost in the process, but
automatically converted to po files. You may however want to ask your
previous translator to review them and update them if needed. Also ask
them to add their name in the header of the po files, to ease future
maintainance and update of the file.

If you want to reproduce this by yourself instead of applying the
patch, you have to do:

- install po-debconf on your system
- run "debconf-gettextize *.templates"
- remove files left by debconf-gettextize (*templates.*)
- Modify Build-Depends or Build-Depends-Indep to add "debhelper (>= 4.1.16)"
  (debhelper depends upon po-debconf) since you use debhelper.
- Modify depends to add "debconf (>= 1.2.0)" since older version have issues
  with templates specifying the encoding of their content.
- Add 'debconf-updatepo' to the clean target of your debian/rules
- update the templates file to mark as translatable only the fields
  which should (ie, not the one containing stuff which cannot be
  translated such as kernel module name, and neither the one not
  shown to the users), and improve the style to follow the dstg.

For more details, see po-debconf documentation, especially "man 7
po-debconf"

Read this if you're concerned with backports :


Please note that the suggested modifications will make your
package a little bit harder to backport to earlier Debian releases. If
this is a concern to you, you may try to adopt the method used by the
openssh package and detailed by Colin Watson in
http://lists.debian.org/debian-i18n/2003/debian-i18n-200307/msg00026.html

This patch does not includes this method as this would make it too
invasive, IMHO. So, preserving backportability is up to you...

The rest of the story :
-
While I was working on the convertion to po-debconf, I noticed that the
templates of your package are in a rather good shape. I did provide such
a conversion for a bunch of packages, and I saw a bunch of broken
templates very hard to understand for newbies. Yours are not that way,
and I wanted to congratulate you for that. However, you may want to
check the current best practices concerning templates, available from:

http://people.debian.org/~bubulle/dtsg.txt
   
Once the switch is achieved, and the style improvement are done (if any), I
guess that you will receive translations of your templates rather soon. They
will consist in XX.po files where XX is the code of the language they
contain. Simply put them to debian/po, add a changelog entry, and your
package is ready for rebuilding and uploading after the usual checks.

If you modify your templates in the future, no action is absolutely
mandatory from you to take care of the translations (outdated translations
will be automatically discarded). But it is nicer to your translators and
your not english speaking users to include the updated translations in the
same upload. For that, run debconf-updatepo, and mail each translator the
XX.po file they provided you. Their adress can be found in the headers of
the po file. Wait a few days so that they can do their work, and put the new
version of the po file back in position in debian/po.



Thanks for helping the translators, and thus your non english speaker
end-users. 

Bye, Mt.



-- System Information:
Debian Release: testing/unstable
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: i386 (i686)
Kernel: Linux 2.6.3
Locale: [EMAIL PROTECTED], [EMAIL PROTECTED]
diff -ruN hunglish-1.12.ori/debian/control hunglish-1.12/debian/control
--- hunglish-1.12.ori/debian/control2004-04-20 17:12:33.0 -0700
+++ hunglish-1.12/debian/control2004-04-20 17:13:14.0 -0700
@@ -2,12 +2,12 @@
 Section: misc
 Priority: optional
 Maintainer: Debian QA Group <[EMAIL PROTECTED]>
-Build-Depends-Indep: debhelper (>> 2.0.0)
+Build-Depends-Indep: debhelper (>= 4.1.16)
 Standards-Version: 3.5.8.0
 
 Package: hunglish
 Architecture: all
-Depends: debconf (>= 0.2.70)
+Depends: debconf (>= 1.2.0)
 Conflicts: xbase-clients (<< 4.0.3), hunglish-x3
 Replaces: hunglish-x3
 Recommends: console-tools, xbase-clients
diff -ruN hunglish-1.12.ori/debian/hunglish.templates 
hunglish-1.12/debian/hunglish.templates
--- hungl

Bug#246439: x-ttcidfont-conf: Failure to install

2004-04-29 Thread Martin Quinson
This looks like a missing dependency in defoma, but I'm not sure and the
maintainer of defoma is in CC.

Thanks for the report, Mt.

On Thu, Apr 29, 2004 at 03:06:00AM +0100, Noel Torres wrote:
> Package: x-ttcidfont-conf
> Version: 17
> Severity: grave
> Justification: renders package unusable
> 
> Maybe related to #245297
> 
> Exactly the same happens installing msttcorefonts .
> 
> Installing x-ttcidfont-conf I got this (sorry, I'm spanish so some lines
> are in spanish):
> 
> Configurando x-ttcidfont-conf (17) ...
> Can't locate File/Copy.pm in @INC (@INC contains: /etc/perl
> /usr/local/lib/perl/5.8.3 /usr/local/share/perl/5.8.3 /usr/lib/perl5
> /usr/share/perl5 /usr/lib/perl/5.8 /usr/share/perl/5.8
> /usr/local/lib/site_perl .) at /usr/bin/defoma-app line 7.
> BEGIN failed--compilation aborted at /usr/bin/defoma-app line 7.
> dpkg: error al procesar x-ttcidfont-conf (--install):
>  el subproceso post-installation script devolvi? el c?digo de salida de
>  error 2
>  
> 
> -- System Information
> Debian Release: 3.0
> Architecture: i386
> Kernel: Linux TacoronteX 2.4.18 #2 mar feb 24 21:05:49 WET 2004 i686
> Locale: [EMAIL PROTECTED], LC_CTYPE=es_ES
> 
> Versions of packages x-ttcidfont-conf depends on:
> ii  debconf   1.4.22 Debian configuration management 
> sy
> ii  defoma0.11.0 Debian Font Manager -- automatic 
> f
> ii  xutils4.1.0-16woody3 X Window System utility programs
> 
> 
> 
> 

-- 
Le monde est dangereux à vivre! Non pas tant à cause de ceux qui font le
mal, mais à cause de ceux qui regardent et laissent faire.
  -- Albert Einstein


signature.asc
Description: Digital signature


Bug#245297: x-ttcidfont-conf: install/upgrade fails - template parse error

2004-06-04 Thread Martin Quinson
On Thu, Apr 22, 2004 at 01:39:00PM +0100, Lee Braiden wrote:
> Package: x-ttcidfont-conf
> Version: 17
> Severity: important
> Tags: sid l10n
> 
> x-ttcidfont-conf fails to install/upgrade for me.  I get the following:
> 
> Setting up x-ttcidfont-conf (17) ...
> Template parse error near `BM8
>  (followed by lines of binary)
> 
> And the apt then fails, of course.
> 
> I marked this as a l10n bug, since the template file seems to hold
> translations.  But I'm not sure about it; sorry if it's inappropriate.

Erm, I'm quite puzzled. I tried to reproduce this bug in vain. Could you
still reproduce this? Would it be possible that it just comes from a broken
download or something?

Did you also run the installation under locale C, as the bug report seems to
imply, or did you use another one?

Thanks for any detail, Mt.

-- 
This message has been made up using recycled ideas and language constructs.
No tree has been cut nor animal harmed in process of making it.


signature.asc
Description: Digital signature