Hello,
I am packaging tikiwiki, and want to use dbconfig-common for the
database configuration. I followed the instructions in the documentation
and looked at the examples, but it still yelling rude things at me.
First I installed my package and said NO to the first question, about
whether dbconf
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Rogério Brito wrote:
> there's actually no Computer Algebra System available in etch,
Right, although sid has "axiom" (for most architectures).
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.2 (GNU/Linux)
iD8DBQFDgcutXjXn6TzcAQkRAlGWAJ9WvQ5zhmAVGA
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello,
I am packaging some software and would like testers to try out my
packages. What is the best way to choose version numbers for the package
under development so that:
(1) Testers can use "apt-get upgrade" to download the next test versions
from
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello,
I am packaging TikiWiki. It includes pdf-php, a PDF generator written in
PHP:
http://www.ros.co.nz/pdf/
This contains font metric files (afm) for Adobe's standard fonts
(Courier, Times, Helvetica etc). These are, to my knowledge, not freely
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Marcus Better wrote:
> This contains font metric files (afm) for Adobe's standard fonts
> (Courier, Times, Helvetica etc). These are, to my knowledge, not freely
> distributable (?),
My mistake, they seem to be freely distribu
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Marcus Better wrote:
> Now I would like to know if there is a mechanism that can locate font
> files (both afm and pfb) based on a name like "Courier" or "Helvetica"?
Ok, so I think that defoma might help here, right?
If I
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Marcus Better wrote:
> My next question is: When my application is first installed, how will it
> find out about the fonts that are already installed on the system?
Ah, I see, defoma is more clever than that, so it should work... I
appreci
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Russ Allbery wrote:
>>(Couldn't it have used shishi-0.0.23.tar.gz?
> The packaging tools require that the upstream source have a very specific
> name, namely _.orig.tar.gz
But note (for the record) that it is enough to make this a symlink to
the ori
My application needs to locate font files for Type 1 fonts on the
system. Specifically, given a name which the user chooses, say "Courier"
or "Helvetica", the app needs to find a suitable pfb _and_ afm files for
these fonts. How do I do this?
Can I do this with either defoma or fontconfig?
I beli
I am looking for a sponsor for this package.
Package name: tikiwiki
Version : 1.9.2
Upstream Author : Luis Argerich, Garland Foster, Eduardo Polidor, et. al.
URL or Web page : http://tikiwiki.org
License : LGPL
Description : groupware and content management syst
Moritz Muehlenhoff wrote:
> http://moritz-naumann.com/adv/0003/tikiw/0003.txt
> Is this fixed in your package, the advisory says that 1.9.2 is affected
> as well?
The developers claim that 1.9.2 is not vulnerable, contrary to what was
stated in the advisory. See
http://www.derkeiler.com/Mailing-L
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello,
I am renewing my request for a sponsor for Tikiwiki. I would like to
upload it to experimental for easier access, so that I can get it more
widely tested.
> Package name: tikiwiki
> Version : 1.9.2
> Upstream Author : Luis Ar
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I use a few packages, such as kernel-patch-exec-shield, which are
neglected by the maintainer. What can I do to help if the maintainer is
not responding to bug reports or e-mail?
I have prepared patches fixing some bugs (even RC) and sent them to the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Justin Pryzby wrote:
> You can mail [EMAIL PROTECTED] asking if the maintainer is MIA.
Ah, I just noticed section "7.4 Dealing with inactive and/or unreachable
maintainers" in the Developer's Reference...
Thanks,
Marcus
-BEGIN PGP SIGNATURE-
Marco Nenciarini wrote:
> Description: A free SIP-based VoIP softphone with Video and Chat features.
No need to say that it's free, this is Debian after all :-) Perhaps the
short description should be something like:
Description: softphone with video and chat features
Marcus
--
To UNSUBSCR
://mentors.debian.net/debian/pool/main/t/tikiwiki
Kind regards
Marcus Better
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Alec Berryman wrote:
> The version in experimental is probably vulnerable to CVE-2006-3048,
> CVE-2006-3047, and CVE-2006-2635.
These are resolved in 1.9.4 according to information here:
http://tikiwiki.org/tiki-read_article.php?articleId=131
http://www.securityfocus.com/bid/18143
http://www.sec
Hi,
> All the source code was licenced under GPL in which
> case I decided to make a front-end for GNU/Linux using GTK2.
Just a little tip: tptest for Windows also runs very well under Wine. (Of
course a native version would be even better.)
Any plans to package the server also? That could be u
Hello,
I am looking for a sponsor for my package "nekohtml".
-
* Package name: nekohtml
Version : 0.9.5
Upstream Author : Andy Clark
* URL or Web page : http://people.apache.org/~andyc/neko/doc/html/
* License : CyberNeko Software License, V
Second attempt: anyone willing to sponsor this please?
Marcus Better wrote:
> Hello,
>
> I am looking for a sponsor for my package "nekohtml".
>
> -
> * Package name: nekohtml
> Version : 0.9.5
> Upstream Autho
Hello,
I am looking for a sponsor for my package "xml-im-exporter". This is
part of the JBoss packaging effort.
* Package name: xml-im-exporter
Version : 1.1
Upstream Author : Oliver Zeigermann
* URL or Web page : http://xml-im-exporter.sourceforge.net
* License : custom B
Marc Haber wrote:
> Which component of the build process is supposed to handle the control
> file generation
module-assistant. You will see that debian/rules includes some files
from /usr/share/modass. The documentation for module-assistant has the
details.
> as I suppose that the module build pr
Arnaud Vandyck wrote:
> Are you still looking for a sponsor to upload xml-im-exporter?
No, it's in the NEW queue.
> Did you put it in pkg-java Alioth's subversion?
Yes.
Marcus
pgpBUSbzcwkc6.pgp
Description: PGP signature
Hi!
> 3) Comments in changelog expanded, to explain about the man page patch.
No, it should only include the one line with "Initial release...". The
changes from upstream are considered packaging work, and do not need to be
recorded in the changelog. If you subsequently change things in the
packa
Paul Cager wrote:
>> I don't think the repackaging of the upstream zip file into a tarball
>> warrants a README.Debian-source file, so I would remove that.
>
> I put this in because of section 6.7.8.2 in the Developers' Reference
> seemed to require it. Is this right?
Yes, it seems you were right
Neil Williams wrote:
> Have there been *actual* incidences when a CDBS package has failed on
> the buildd's for reasons that can be clearly attributed to CDBS itself?
I have seen bugs that could have lead to FTBFS, due to the fact that people
mixed up their build-depends and build-depends-indep be
Carlo Segre wrote:
> If a new version of a package drops a dependency on a previously required
> package, should an install-time reminder be given to the user?
Certainly not as a general rule, that would be horrible given the frequency
of packages dropping dependencies. A note in the changelog see
Jens Peter Secher wrote:
> As others have mentioned,
> some of the nitpicking is really your personal preferences, and not
> really something that makes a new Developer much better at the tasks
> involved in maintaining a package.
I disagree. While a superfluous dh_* command or blank line here an
Magnus Holmgren wrote:
> I maintain a package where the upstream author has two changelog files: A
> brief one called Changes, summarizing the changes, and a detailed one
> called ChangeLog, which contains a detailed list of changes made to the
> various source files.
This is common with Java pack
Magnus Holmgren wrote:
>> This is common with Java packages built with Maven, where a detailed
>> commit log is automatically generated and included in the sources. In
>> that case I prefer to leave out the commit log altogether
> But what if Changes says "see ChangeLog for details"?
Mention of t
Jordi Gutierrez Hermoso wrote:
> mathematical pieces of software for Debian, beginning with surf,
> Singular's plotting engine, followed by Singular itself,
IIRC Singular has licensing restrictions (requires citing the authors) so I
don't think it can go in main.
Marcus
--
To UNSUBSCRIBE, ema
Bernhard R. Link wrote:
>> IIRC Singular has licensing restrictions (requires citing the authors) so
>> I don't think it can go in main.
>
> I don't think that is part of the license.
I don't know, but I think that at least a clarification from the authors is
needed. Citing the license [1]:
"Thi
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ludovic Claude wrote:
> Thanks for your suggestions. I have uploaded a new version of jetty into
> mentors.d.o, plus a new version of tomcat6 which contains a little
> packaging change used by jetty.
Great (but someone else will have to sponsor since
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
I am looking for a sponsor for the new version 5.11+dfsg-2 of my package
"testng".
It builds these binary packages:
testng - testing framework for Java
testng-doc - documentation for TestNG
The upload would fix this RC bug: 593040
The pack
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Asheesh Laroia wrote:
>> I am looking for a sponsor for the new version 5.11+dfsg-2 of my package
>> "testng".
(Still looking BTW...)
> Have you talked with the Debian Java team about this? If not, take a look
> at http://wiki.debian.org/Teams/JavaPa
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Varun,
> I can upload the package,
Great, thanks!
> but I see some easy-to-fix lintian warnings:
> Would you like to fix any of these? If this minimal-change RC fix
> upload is intended for squeeze,
Exactly, I'll fix those later.
Cheers,
Marc
36 matches
Mail list logo
