Re: pdf files in upstream tarball and -doc package

2005-02-11 Thread Frank Küster
Miriam Ruiz [EMAIL PROTECTED] schrieb: --- Justin Pryzby [EMAIL PROTECTED] escribió: PDF can be trojaned, so you should at least *provide* a way to generate them from their sources, even if that makefile rule is not called by default, and the additional build-dependencies are just a

Re: pdf files in upstream tarball and -doc package

2005-02-11 Thread martin f krafft
also sprach Frank Küster [EMAIL PROTECTED] [2005.02.11.1332 +0100]: But you cannot include pdf files for which no source is included, or only Micro$oft .doc files, in a Debian package: We need the source code, and pdf, even if not compressed, cannot be taken as source code. This is

Re: pdf files in upstream tarball and -doc package

2005-02-11 Thread Samuel Mimram
martin f krafft wrote: also sprach Frank Küster [EMAIL PROTECTED] [2005.02.11.1332 +0100]: But you cannot include pdf files for which no source is included, or only Micro$oft .doc files, in a Debian package: We need the source code, and pdf, even if not compressed, cannot be taken as source code.

Re: pdf files in upstream tarball and -doc package

2005-02-11 Thread Miriam Ruiz
There are two problems with this: Security and DFSG-freeness. I wouldn't put too much weight in the security thing. If you don't understand postscript or pdf, you won't detect the exploit - it doesn't matter if it is in the ps/pdf file, or in a \special command in the LaTeX/Lyx

RFS: schedtool -- cpu schedule policy tool (fwd)

2005-02-11 Thread Janne Kujanpää
* Package name: schedtool Version : 1.2.4 Upstream Author : Freek * URL : http://freequaos.host.sk/schedtool/ * License : GPL2 Description : cpu schedule policy tool It can be used to avoid skipping for A/V-applications, to lock processes onto certain

Re: pdf files in upstream tarball and -doc package

2005-02-11 Thread Jay Berkenbilt
martin f krafft [EMAIL PROTECTED] wrote: also sprach Frank Kster [EMAIL PROTECTED] [2005.02.11.1332 +0100]: But you cannot include pdf files for which no source is included, or only Micro$oft .doc files, in a Debian package: We need the source code, and pdf, even if not compressed, cannot be

RFS: php-services-weather

2005-02-11 Thread Jose Carlos
Package Name: php-services-weather Licence : PHP License 2.02 Description: services_Weather module for PEAR Services_Weather searches for given locations and retrieves current weather data and, dependent on the used service, also forecasts. Up to now, GlobalWeather from CapeScience, Weather XML

Re: RFS: nxtvepg

2005-02-11 Thread Philipp Kern
On 11 Feb 2005, at 21:33, Martin Theiss wrote: I am also looking for a Debian Developer near Stuttgart/Germany to have my gpg key signed and complete the first step in the new maintainer process. Look at http://nm.debian.org/gpg_offer.php#de for a Debian developer near you. Regards, Philipp

Re: pdf files in upstream tarball and -doc package

2005-02-11 Thread Alejandro Exojo
El Viernes, 11 de Febrero de 2005 17:21, Jay Berkenbilt escribi: That isn't to say that it is impossible to create a security hole through a PDF file, but it's more comparable to html in that respect than to PostScript. In other words, you could include a malicious link or put invalid PDF data