Sponsor for linkchecker package
Hello, I packaged linkchecker and need someone to sponsor it. Package: linkchecker Version: 1.2.10 URL: http://linkchecker.sourceforge.net/ License: GPL LinkChecker can check HTML documents for broken links. thanks, Bastian Kleineidam -8<- original ITP 8<-- Package: wnpp Severity: wishlist Hello Debian developers. LinkChecker is a tool I wrote some time ago to check my HTML pages. It has grown into a program that can check whole web structures for broken links. Its licensed under the GPL. Features: o recursive checking o multithreading o output in colored or normal text, HTML, SQL, CSV or a sitemap graph in GML or XML. o HTTP/1.1, HTTPS, FTP, mailto:, news:, nntp:, Gopher, Telnet and local file links support o restriction of link checking with regular expression filters for URLs o proxy support o username/password authorization for HTTP and FTP o robots.txt exclusion protocol support o i18n support o a command line interface o a (Fast)CGI web interface (requires HTTP server) At the Homepage on http://linkchecker.sourceforge.net/ you can find the Debian package as well as the source tarball. It is also apt-able: deb ftp://linkchecker.sourceforge.net/pub/linkchecker ./ Because I do not have a Debian account yet I need a sponsor to upload this package. Greetings Bastian Kleineidam
ITP: linkchecker (needs sponsor)
Hello, I filed an ITP some days ago for LinkChecker and I need a sponsor to upload this package. Here is the description: LinkChecker -- check HTML pages for broken links Current version: 1.2.12 License: GPL URL: http://linkchecker.sourceforge.net/ Download: ftp://linkchecker.sourceforge.net/pub/linkchecker sources.list: deb ftp://linkchecker.sourceforge.net/pub/linkchecker ./ LinkChecker features: o recursive checking o multithreading o output in colored or normal text, HTML, SQL, CSV or a sitemap graph in GML or XML. o HTTP/1.1, HTTPS, FTP, mailto:, news:, nntp:, Gopher, Telnet and local file links support o restriction of link checking with regular expression filters for URLs o proxy support o username/password authorization for HTTP and FTP o robots.txt exclusion protocol support o i18n support o a command line interface o a (Fast)CGI web interface (requires HTTP server) Greetings, Bastian Kleineidam
linkchecker lintian warnings
Hi, if you test my linkchecker .deb package: I just noticed that lintian gives the following warnings on my 1.2.12 package of LinkChecker: W: linkchecker: postinst-does-not-set-usr-doc-link W: linkchecker: prerm-does-not-remove-usr-doc-link This is a lintian (or debconf) bug because I see the following lines in the postinst script: # Automatically added by dh_installdocs if [ "$1" = "configure" ]; then if [ -d /usr/doc -a ! -e /usr/doc/linkchecker -a -d /usr/share/doc/linkc hecker ]; then ln -sf ../share/doc/linkchecker /usr/doc/linkchecker fi fi # End automatically added section And the same applies for prerm My installed version: ii debhelper 2.2.8 helper programs for debian/rules ii lintian1.11.12Debian package checker Greetings, Bastian
Re: getting a python module accepted by python?
Sean, On Tue, 26 Dec 2000, Sean 'Shaleh' Perry wrote: > Is there a way to make a site-packages/foo/foo.py without requiring a change > in programs calling foo? No, and I dont think its wise to create an own subdirectory for a single file. Just leave the file in site-packages/. > Also, sorry to get off topic, but should the postinst compile the module? Yes, see the postinst for python-base. > Won't this happen the first time the module is imported? Yes and no, it depends on the write permissions of the user. If I have write permission to /usr/lib/python1.5/site-packages then the .pyc (or .pyo) file is created. If not, then no compiled file will be created. Thats the reason you should compile .py files with the postinst script. Note: .pyc files are not binary compatible, so if you are working with Python 2.0 and distribute .pyc files for Python 1.5 (or vice versa) they might not work. Thats another reason to compile with postinst. Bastian
How popular is the sponsor page?
Hello, I subscribed to the sponsorship program at http://www.internatif.org/bortzmeyer/debian/sponsor/ How popular is this web page? It is linked from http://www.debian.de/devel/join/ but I think that very few potential sponsors are reading this. Bastian Kleineidam
Re: Compiled pyton files for all arch?
Mikael, > I think I ought to produce an architecture:any package instead, am I > right? Anyone want to confirm, or test it? Use 'all' if you - have only .py files - use only platform independent Python modules - have no C extension modules Use 'any' if you - use only platform independent Python modules (this allows that you have some C extension modules, but they must be platform independent) Use the appropriate arch if you are not platform independent. You should compile the Python modules in your postinst script, because .pyc or .pyo files are not version-compatible. Look at python-base postinst (and prerm) scripts for an example! Bastian pgpcd33WwX9IW.pgp Description: PGP signature
Re: ITP: wmmenu -- button bar dockapp
Hi,
rob caSSon wrote:
deb http://styro.dyndns.org/debian/ ./
deb-src http://styro.dyndns.org/debian/ ./
everything seems lintian clean and such, but all comments are
welcome...application details below...
Usage of /usr/X11R6/{man,bin}/ is deprecated (see policy 12.8.7).
You should use /usr/bin and /usr/share/man.
Bastian
Re: RFS: python-elementtree and python-celementtree
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Moin Torsten, I can sponsor you. Here are the things that I think should be corrected before uploading: - - Both packages use dh_python so they must build-depend on "python". - - python-elementtree and python-celementtree are only dummy packages which should be noted in the descriptions. For example python-metakit has this paragraph in the description: . This package depends on the python bindings' package for the default python version, currently 2.3. Apart from that the packages are very good. Regards, Bastian - -- ,''`. Bastian Kleineidam : :' :GnuPG SchlÃssel `. `'gpg --keyserver wwwkeys.pgp.net --recv-keys 32EC6F3E `- -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.5 (GNU/Linux) iD8DBQFB/3hxeBwlBDLsbz4RAm7ZAKCZWV1dcwPXNkDVRmh8uBDFOoc9gACgkDBD GNPMjDSedGlO11iIeOxaMS4= =jA8i -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Sponsor for linkchecker package
Hello, I packaged linkchecker and need someone to sponsor it. Package: linkchecker Version: 1.2.10 URL: http://linkchecker.sourceforge.net/ License: GPL LinkChecker can check HTML documents for broken links. thanks, Bastian Kleineidam -8<- original ITP 8<-- Package: wnpp Severity: wishlist Hello Debian developers. LinkChecker is a tool I wrote some time ago to check my HTML pages. It has grown into a program that can check whole web structures for broken links. Its licensed under the GPL. Features: o recursive checking o multithreading o output in colored or normal text, HTML, SQL, CSV or a sitemap graph in GML or XML. o HTTP/1.1, HTTPS, FTP, mailto:, news:, nntp:, Gopher, Telnet and local file links support o restriction of link checking with regular expression filters for URLs o proxy support o username/password authorization for HTTP and FTP o robots.txt exclusion protocol support o i18n support o a command line interface o a (Fast)CGI web interface (requires HTTP server) At the Homepage on http://linkchecker.sourceforge.net/ you can find the Debian package as well as the source tarball. It is also apt-able: deb ftp://linkchecker.sourceforge.net/pub/linkchecker ./ Because I do not have a Debian account yet I need a sponsor to upload this package. Greetings Bastian Kleineidam -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
ITP: linkchecker (needs sponsor)
Hello, I filed an ITP some days ago for LinkChecker and I need a sponsor to upload this package. Here is the description: LinkChecker -- check HTML pages for broken links Current version: 1.2.12 License: GPL URL: http://linkchecker.sourceforge.net/ Download: ftp://linkchecker.sourceforge.net/pub/linkchecker sources.list: deb ftp://linkchecker.sourceforge.net/pub/linkchecker ./ LinkChecker features: o recursive checking o multithreading o output in colored or normal text, HTML, SQL, CSV or a sitemap graph in GML or XML. o HTTP/1.1, HTTPS, FTP, mailto:, news:, nntp:, Gopher, Telnet and local file links support o restriction of link checking with regular expression filters for URLs o proxy support o username/password authorization for HTTP and FTP o robots.txt exclusion protocol support o i18n support o a command line interface o a (Fast)CGI web interface (requires HTTP server) Greetings, Bastian Kleineidam -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
linkchecker lintian warnings
Hi, if you test my linkchecker .deb package: I just noticed that lintian gives the following warnings on my 1.2.12 package of LinkChecker: W: linkchecker: postinst-does-not-set-usr-doc-link W: linkchecker: prerm-does-not-remove-usr-doc-link This is a lintian (or debconf) bug because I see the following lines in the postinst script: # Automatically added by dh_installdocs if [ "$1" = "configure" ]; then if [ -d /usr/doc -a ! -e /usr/doc/linkchecker -a -d /usr/share/doc/linkc hecker ]; then ln -sf ../share/doc/linkchecker /usr/doc/linkchecker fi fi # End automatically added section And the same applies for prerm My installed version: ii debhelper 2.2.8 helper programs for debian/rules ii lintian1.11.12Debian package checker Greetings, Bastian -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: getting a python module accepted by python?
Sean, On Tue, 26 Dec 2000, Sean 'Shaleh' Perry wrote: > Is there a way to make a site-packages/foo/foo.py without requiring a change > in programs calling foo? No, and I dont think its wise to create an own subdirectory for a single file. Just leave the file in site-packages/. > Also, sorry to get off topic, but should the postinst compile the module? Yes, see the postinst for python-base. > Won't this happen the first time the module is imported? Yes and no, it depends on the write permissions of the user. If I have write permission to /usr/lib/python1.5/site-packages then the .pyc (or .pyo) file is created. If not, then no compiled file will be created. Thats the reason you should compile .py files with the postinst script. Note: .pyc files are not binary compatible, so if you are working with Python 2.0 and distribute .pyc files for Python 1.5 (or vice versa) they might not work. Thats another reason to compile with postinst. Bastian -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
How popular is the sponsor page?
Hello, I subscribed to the sponsorship program at http://www.internatif.org/bortzmeyer/debian/sponsor/ How popular is this web page? It is linked from http://www.debian.de/devel/join/ but I think that very few potential sponsors are reading this. Bastian Kleineidam -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Compiled pyton files for all arch?
Mikael, > I think I ought to produce an architecture:any package instead, am I > right? Anyone want to confirm, or test it? Use 'all' if you - have only .py files - use only platform independent Python modules - have no C extension modules Use 'any' if you - use only platform independent Python modules (this allows that you have some C extension modules, but they must be platform independent) Use the appropriate arch if you are not platform independent. You should compile the Python modules in your postinst script, because .pyc or .pyo files are not version-compatible. Look at python-base postinst (and prerm) scripts for an example! Bastian PGP signature
Re: ITP: wmmenu -- button bar dockapp
Hi,
rob caSSon wrote:
> deb http://styro.dyndns.org/debian/ ./
> deb-src http://styro.dyndns.org/debian/ ./
>
> everything seems lintian clean and such, but all comments are
> welcome...application details below...
Usage of /usr/X11R6/{man,bin}/ is deprecated (see policy 12.8.7).
You should use /usr/bin and /usr/share/man.
Bastian
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: new version number needed to repair broken download?
Marc, simply re-upload. Marc Haber wrote: > I recently goofed and invoked debsign twice on a package. This > resulted in a Signature on a Signature on my .dsc file, causing katie > (?) to reject my upload. > > Can I simply re-upload a correctly signed package, or do I need do > bump the version number for katie (?) to pick the upload up again? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Open Motif
Hi, On Fri, Jan 11, 2002 at 12:10:55PM +0100, Stefan Schwandter wrote: > But I don't understand why I also have to make both a statically and a > dynamically linked version of the package, as reqested by 12.8. Some people might not want to install the non-free libmotif, but want to have your package. > I also don't understand why a statically linked version is necessary at > all, since libmotif is in the debian distribution. Non-free is not included in official Debian CD's, as its not part of the main distribution. Greetings, Bastian msg05218/pgp0.pgp Description: PGP signature
Procedure for new GPG key?
Hello, what is the correct procedure to get a new GPG key into the Debian keyring? My old one expired unnoticed by me :(. I mailed [EMAIL PROTECTED], but my three mails seem to be dropped silently. My key Infos: Old key ID 959C340F New key ID 32EC6F3E (signed by [EMAIL PROTECTED]) URL: http://blackhole.pca.dfn.de:11371/pks/lookup?op=get&search=0x32EC6F3E I would be very thankful if anyone can help me on this because I want to upload package updates and bugfixes. Greetings, Bastian msg05501/pgp0.pgp Description: PGP signature
Re: Uncertainty regarding kernel module and /etc/modutils/*
Tore, On Tue, Apr 23, 2002 at 10:46:45PM +0200, Tore Anderson wrote: > So, should I accept the redundancy and let dh_installmodules do its job, > or should I use the postinst/rm approach? Or the insanely clever solution > one of you are going to suggest? :-) If you have identical files in your packages, you could make a new package -common and depend on it. Several packages have done this (apache-common, fetchmail-common, ...). Greetings, Bastian msg06041/pgp0.pgp Description: PGP signature
Re: Multiple configure-make cycles
Hi, On Fri, Apr 26, 2002 at 07:08:26PM -0700, David Caldwell wrote: > Instead of building in the source dir, create 2 build directories, cd to > each and ../configure with different options. Then in the make section, cd > into each build dir and make. So essentially you are building the different > versions in parallel, rather than repeating them in a serial fashion. Look at the FOX library, it uses exactly this approach to build a default libfox0.99 and one with debugging libfox0.99-dbg. Greetings, Bastian msg06085/pgp0.pgp Description: PGP signature
Sponsor search for linkchecker
Hi folks, some people may have noticed that my linkchecker package [1] is very out of date. Well, this is mainly because my GPG key expired and I am waiting now a long time to get the new key [2] into the keyring. In the meantime, would someone please sponsor an upload of the current version 1.4.2 [3]. This version fixes all bugs in the DBS [4]. The package source is signed with my new key. [1] http://packages.debian.org/linkchecker [2] http://blackhole.pca.dfn.de:11371/pks/lookup?op=get&search=0x32EC6F3E [3] http://people.debian.org/~calvin/debian/ [4] http://bugs.debian.org/linkchecker Thanks, Bastian msg06088/pgp0.pgp Description: PGP signature
Re: Multiple configure-make cycles
Hi,
On Sat, Apr 27, 2002 at 11:06:59AM -0400, Joey Hess wrote:
> That sounds redundant, what's wrong with building once with -g, linking
> shared, stripping, calling that one package, and then linking w/o
> stripping for the -dbg package?
The configure.in has different -D defines for debugging, so you have to
compile twice, one with --enable-release, the other with --enable-debug.
FOX has internal tracing (FXTRACE) and asserts (FXASSERT) macros that
are enabled when DEBUG is defined, disabled otherwise.
Greetings, Bastian
[configure.in snippet]
dnl Debugging turned on
AC_MSG_CHECKING(for debugging)
AC_ARG_ENABLE(debug,[ --enable-debug compile for debugging])
AC_MSG_RESULT([$enable_debug])
if test "x$enable_debug" = "xyes" ; then
CXXFLAGS="${CXXFLAGS} -g -DDEBUG"
fi
dnl Building for release
AC_MSG_CHECKING(for release build)
AC_ARG_ENABLE(release,[ --enable-releasecompile for release])
AC_MSG_RESULT([$enable_release])
if test "x$enable_release" = "xyes" ; then
CXXFLAGS="${CXXFLAGS} -O2 -DNDEBUG"
if test "${GXX}" = "yes" ; then
CXXFLAGS="${CXXFLAGS} -Wuninitialized -ffast-math -finline-functions
-fomit-frame-pointer -fexpensive-optimizations"
fi
fi
msg06094/pgp0.pgp
Description: PGP signature
Re: Sponsor search for linkchecker
On Sat, Apr 27, 2002 at 01:22:58PM -0500, Luis Bustamante wrote: > On Sat, Apr 27, 2002 at 04:44:29PM +0200, Bastian Kleineidam wrote: > > Hi folks, > > > > some people may have noticed that my linkchecker package [1] is very > > out of date. > > Well, this is mainly because my GPG key expired and I am waiting now > > a long time to get the new key [2] into the keyring. > > > > In the meantime, would someone please sponsor an upload of the current > > version 1.4.2 [3]. This version fixes all bugs in the DBS [4]. > > If nobody else have done it yet, I'll take care of it, I'll upload it in > a couple of hours. Cool, thanks. Bastian msg06104/pgp0.pgp Description: PGP signature
Help fixing non-i386 bugs
Hi, On Fri, May 24, 2002 at 06:00:02AM -0500, BugScan reporter wrote: > Bug stamp-out list for May 24 00:03 (CST) > > Total number of release-critical bugs: 112 Some bugs in this list affect architectures I dont have (have only i386) How am I supposed to use Debian machines to test/fix these bugs? How can I install build-depends on those machines? Should I use a chroot (imagine dozens of users install their own chroot on a single machine...)? Any suggestions appreciated. Greetings, Bastian msg06294/pgp0.pgp Description: PGP signature
Re: Files in /usr/sbin
On Fri, May 24, 2002 at 02:10:18PM +0100, [EMAIL PROTECTED] wrote: > I have a package which installs a programme in /usr/sbin but lintian gives > the following warning on the package: > W: libpam-mount: file-in-unusual-dir usr/sbin > > There are plenty of other Debian packages which put a file in /usr/sbin and > lintian doesn't complain about them; why does it do this for my package? Perhaps its not executable? Try chmod +x. Greetings, Bastian msg06296/pgp0.pgp Description: PGP signature
Re: Checking for installed package-alternative in a wrapper-skript
On Sat, Jun 22, 2002 at 07:08:00PM +0200, Andreas Metzler wrote:
> Hello,
> Is there some canonical fast way to check in a script whether inn,
> inn2 or cnews is installed on the system?
What dpkg does is parsing /var/lib/dpkg/status.
I recommend using dpkg - its error prone to rely on an implicit data
format of the status file.
If you look in the file, there is a paragraph for each package. What you
want is searching the Packages: line, then search its Status: line and
see if its last entry is "installed".
You could use awk to do this (replace with your package name).
Greetings, Bastian
test.sh
if awk -f test.awk /var/lib/dpkg/status; then
echo "installed";
else
echo "not installed";
fi
test.awk
/^Package: / { found = ($2==""); }
/^Status: / {
if (found) exit ($4!="installed");
}
END { if (!found) exit 1; }
msg06465/pgp0.pgp
Description: PGP signature
Re: postinst question
On Thu, Jun 27, 2002 at 02:29:44PM +0200, Marc Leeman wrote: > > I must be missing something here, I want the package to show a not when > installing to indicate that custom builds _are_ very useful for the time > being, but guess what, it's not asking :( > > Any help? Try this in config: > db_input high nvrec/nvrec_build_optimised db_input high nvrec/nvrec_build_optimised || true db_go || true Greetings, -- .~. /V\ Bastian Kleineidam · Unleash the power. Use Linux. /( )\ ^^-^^ msg06511/pgp0.pgp Description: PGP signature
Re: KDE3 package
Hi, On Sat, Aug 03, 2002 at 10:25:42PM +0200, Marc Leeman wrote: > btw, k3b is a full fledged graphical frontend for burning, composing, > copying CDs (data and audio) and even some tools for burning video to > CDs. btw, some graphics for k3b are from Ayo (http://www.73lab.com/), which is one of the best Tux art I've seen. Greetings, -- .~. /V\ Bastian Kleineidam · Unleash the power. Use Linux. /( )\ ^^-^^ msg06800/pgp0.pgp Description: PGP signature
Re: name collisions
On Mon, Aug 19, 2002 at 10:49:09AM +0200, Marc Leeman wrote: > Also, is renaming of binaries for debian at the discresion of the debian > maintainer (me) or should it be upstream (possibly interactive)? You should only rename binaries if its necessary for the Debian package (eg. a name clash, or multiple versions of this package have to coexist). Otherwise leave the name alone. Users, developers and the documentation normally refer to the original name and a rename would confuse things. Of course there is nothing against asking for renaming at the upstream author. Tschööö, Bastian -- Bastian Kleineidam · [EMAIL PROTECTED] · GPG key ID 32EC6F3E msg06914/pgp0.pgp Description: PGP signature
Re: How much redundancy?
On Tue, Aug 20, 2002 at 09:11:13AM -0700, Sean 'Shaleh' Perry wrote: > In the end I believe that as long as a package in Debian is being used by more > than 1 person it has value. Let's fight the urge to just package something > because it is interesting. However if there is a user base out there then > Debian should support them. Our users should not have to compile software on > their own. I agree. The only thing to be careful when packaging things is keeping the dependency list small. I remember those days where the gettext package suddenly depended on some emacs package (*shudder*). So this leads sometimes to packages split into "foo-common", "foo-gnome", "foo-gtk" or sometimes just compiled without gome/kde support. Cheers, Bastian -- Bastian Kleineidam · [EMAIL PROTECTED] · GPG key ID 32EC6F3E msg06933/pgp0.pgp Description: PGP signature
Re: chained dependencies handling in debian/control
On Mon, Sep 02, 2002 at 01:46:53PM +0200, Alexandre wrote: > Hello, > > Let package A depend on package B and C. > Let package B depend on package C. > I maintain A, someone else maintains B and C. > > Should I explicitely let A depend on B and C in debian/control, or is it > OK -- or better -- to let it depend only on B? You should depend on that what you are using. So if you have for example #!/usr/bin/python in one of your script, depend on the "python" package. Trusting on implicit dependencies is not a guarantee for your package to work in the future. cu, -- Bastian Kleineidam reflexionsniveau AT web.de calvin AT users.sf.net calvin AT debian.org msg07060/pgp0.pgp Description: PGP signature
Re: Check over doclifter package
On Fri, Sep 06, 2002 at 01:23:38PM +0100, Ross Burton wrote: > I have packaged ESR's doclifter package for Debian, and would like > someone to have a look at the packaging for me. Someone who has > packaged Python before would be good, as it depends on Python 2.2. When > I run lintian I get one message I am worried about -- "strange > interpreter" -- it appears that lintian doesn't know that python2.2 is a > valid interpreter. Yes, see bug #114164. cu, -- Bastian Kleineidam reflexionsniveau AT web.de calvin AT users.sf.net calvin AT debian.org msg07095/pgp0.pgp Description: PGP signature
Re: problem replacing package
On Mon, Sep 09, 2002 at 06:19:08PM +0200, Matus fantomas Uhlar wrote:
> Hello,
>
> I would like to compile some packages optimised for my processor. I have k6
> at home and pentiumII at work, and would like to speed up some programs
> running on those.
How about installing pentiumbuilder, configure it for k6 and do
apt-get source --build
If you are satisfied, you can put on hold and it does not get
updated automatically.
> I thought that if my package provides libogg0, it could be installed and
> replace libogg0 without any problems. What do I wrong?
The problem is you are providing a virtual package libogg0, which does
not work in all situations.
cu,
--
Bastian Kleineidam
reflexionsniveau AT web.de
calvin AT users.sf.net
calvin AT debian.org
msg07129/pgp0.pgp
Description: PGP signature
Re: Multiple compile of source (ie, different configure lines for each package)
> > On Wed, Sep 18, 2002 at 08:33:04AM +0200, Turbo Fredriksson wrote: > > > I'm packaging Nagios. It builds tree packages from one source: > > > 'nagios-text', 'nagios-pgsql' and 'nagios-mysql'. The differences > > > is quite obvious: Compile the source three times, each time with > > > different ./configure options. > > > > > > The problem I'm facing is that I want to 'scratch' the source > > > after each build. Actually: build first package, move it aside, > > > build second package - move it aside etc. The ./configure as well as the make can be done in a target subdir, so there is no need to scratch or clean the source tree. You'll find a beautiful example of this at the fox package (libfox1.0 et al.) Tschöö, Bastian -- Bastian Kleineidam reflexionsniveau AT web.de calvin AT users.sf.net calvin AT debian.org msg07176/pgp0.pgp Description: PGP signature
Re: inclusion of a debian dir in upstream src
On Tue, Sep 24, 2002 at 04:34:29PM -0700, Sam Powers wrote: > Is it a good idea to keep a debian directory upstream? I have CVS access, > so I think it'd make it easier for me, and also for others who want to > build custom debs, if the debian files were in CVS. Having an upstream debian/ is good. A minute saved is a minute earned. cu, -- Bastian Kleineidam reflexionsniveau AT web.de calvin AT users.sf.net calvin AT debian.org msg07289/pgp0.pgp Description: PGP signature
Re: Python scrips and deps
On Thu, Sep 26, 2002 at 12:38:08PM +0100, Ross Burton wrote: > I am the maintainer for doclifter, a Python 2.2 script. Upstream (RMS) > claims that it requires Python 2.2, so the script calls "/usr/bin/env > python2.2" and the package Requires: python2.2. > > However, lintian now moans as "python2.2" isn't a valid Python > interpreter. I'd say this is a bug (and I intend to report it in a > minute) but this does bring up an interesting issue. You should not use the env trick. Use #!/usr/bin/python2.2 for python2.2 scripts and #!/usr/bin/python for python scripts. > The default Python release in Debian Sid (and testing?) is now 2.2, so > should I change the package to call "python" and change the requirements > to Depends: python? It is always good to support the default python version. You must have Depends: python (>=2.2), python (<<2.3) You can also join the debian-python mailing list if you need more sophisticated answers :) Hope this helps, Bastian -- Bastian Kleineidam reflexionsniveau AT web.de calvin AT users.sf.net calvin AT debian.org msg07300/pgp0.pgp Description: PGP signature
Re: Python scrips and deps
On Thu, Sep 26, 2002 at 01:52:56PM +0200, Jérôme Marant wrote: > Why shouldn't env be used? Its nothing that policy forbids, but its good for people like me who keeps forgetting that I have local python versions for testing installed :) > > It is always good to support the default python version. You must have > > Depends: python (>=2.2), python (<<2.3) > > But I guess that if upstream absolutely want to use a specific Python, > there isn't any reason not to leave Depends: python2.2. > I don't see any problem here. Sure, its not a problem. cu, Bastian -- Bastian Kleineidam reflexionsniveau AT web.de calvin AT users.sf.net calvin AT debian.org msg07305/pgp0.pgp Description: PGP signature
Re: linker failure -- debuild fails -- please help
On Thu, Oct 10, 2002 at 12:23:00PM -0700, justin cunningham wrote: > I'm trying to compile a program from debian src and have gcc 2.95 and > related libraries installed so why does gcc die on this line? > > gcc -g -O2 -Wall -o .libs/vchkpw vchkpw.o vconfig.o > ./.libs/libvpopmail.so -lfreecdb -lfreecdbmake -ldl > /usr/lib/libmysqlclient.so -lz -lm -lnsl -lcrypt > /usr/bin/ld: cannot find -lz libz.so is missing. You should install zlib1g-dev. Hope this helps, Bastian -- Bastian Kleineidam reflexionsniveau AT web.de calvin AT users.sf.net calvin AT debian.org msg07462/pgp0.pgp Description: PGP signature
Re: Misc questions: add image to package, man page for cgi script, etc
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Frédéric, On Mon, Nov 25, 2002 at 11:35:26PM +1100, Frederic Schutz wrote: > 1) I'd like to add a binary file to the upstream source (an image, so that > all images are available locally and no Internet connection is needed). > Obviously, the diff file doesn't like binaries, so what is the best way to > do it ? [Currently, I added the image as a uuencoded file, with a > "Build-Depends: sharutils" (sharutils contains uudecode) and a line in > debian/rules that decodes it at build time] You have to use uuencode/uudecode. There is also a Perl script for this. This should answer your question: http://lists.debian.org/debian-mentors/2002/debian-mentors-200203/msg00027.html IIRC, theres development to enable binary diffs for the debian package utils, but I dont remember the thread anymore. > 2) Should I write a man page for a CGI script ? If yes, could someone > point me to an example of such a page ? No, there is no rule that one must have a man page for CGI scripts. Usually I make a note in the package description, in README or in README.Debian (whatever seems appropriate) that theres a CGI script available. > 3) The package contains a Perl script that can be used either as a cgi-bin > and on the command line [it is not the same script than in 2) and I > already wrote a man page for the command line version]. I can install it > in either /usr/lib/cgi-bin or /usr/bin and put a symbolic link in the > other directory. What is the best way to do it ? I would think that I > should put it in the cgi-bin directory, since the web server (Apache) will > probably not follow a symlink, while this is not a problem for a command. > Any other thought on the question ? As you said, you should not have symlinks pointing outside of /usr/lib/cgi-bin. I think there are two options: a) symlink from /usr/bin/foo to /usr/lib/cgi-bin/foo b) Make a cgi-only version and a commandline-only version of the script and put them in the proper dir. Because I'm lazy, I'd prefer a). Cheers, Bastian -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQE94iXceBwlBDLsbz4RAjEOAKC1pFcMFhj+Pvag8tRHYKEgbagssQCeNh2s YaxPrleHItp/r6AuDx2F+nk= =gu+8 -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
why is linkchecker gone?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, I noticed that my linkchecker package is gone[0] from unstable, but the last upload was ok[1]. There are strange debcheck errors on the package tracking page[2] which I dont understand, all buildd logs are successful. Can someone point me to whats wrong? [0] http://packages.debian.org/linkchecker [1] http://packages.qa.debian.org/l/linkchecker.html [2] http://qa.debian.org/debcheck.php?dist=unstable&package=linkchecker Cheers, Bastian -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQE961iDeBwlBDLsbz4RAgBzAJ9Bf4ZqxCTk2XczaDF55O/SfEnl5gCfRc5l C7ZurCbIjjUiVLERp6rqiOw= =OEV1 -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: RFS (2nd call): tsclient-0.56
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Fri, Dec 06, 2002 at 01:51:14AM +1100, Andrew Lau wrote: > Hey everyone, > Robster still hasn't uploaded tsclient 0.56 since promising to > sponsor/upload it on Sunday, so my RFS still stands, and is repeated > below. Thanks in advanced to anyone who picks it up. Let him have a little more time, you know the deal: free volunteer, real life, getting cinema tickets for LotR II... all this is more important! I would wait another 1-2 weeks for Robster to check your package and upload it. Cheers, Bastian -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQE973LceBwlBDLsbz4RAru0AJ9/y41Yzc8gvem5/oBTmFGujiSCaACfYe29 pk7oDGEN3mtPrPnbaaKF7ao= =BVl8 -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: ifeq( PACKAGE, "mypackage")
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Thu, Dec 19, 2002 at 10:50:18AM +, Mark Howard wrote: > Hi, > is it possible to determine the name of the current package at the > build stage of debian/rules (multi-binary source), so that only the > parts required for the current package are built? (and also so that they > aren't build twice). How about the FOX solution (apt-get source libfox1.0): define build-deb dh_testdir dh_testroot dh_installdocs -p$@ dh_installexampless -p$@ ... endif package1: build build-deb package2: build build-deb ... Ciao, Bastian -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQE+AauxeBwlBDLsbz4RAjsNAKCCSXVks7RJOjAAQPssO0SMdBM2ugCeOL3a LCRfPEd6ysHMDtL3x6IUZWQ= =adxd -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: postinst and debconf again
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Thu, Dec 19, 2002 at 02:58:11PM +0100, pp wrote: > I posted my problem some time ago. > > > postinst script: Hmm, this looks like a debian/config script, not a postinst script. But the debconf docs are fading already in my minds, so it might be ok. > #! /bin/sh -ex > > . /usr/share/debconf/confmodule > db_version 2.0 > db_title "Midgard library package." > > if $mysqlcmd -D mysql -e 'use midgard;' >/dev/null 2>&1 ; then > > db_input "high" midgard/error > db_go > db_stop > else > db_input high midgard/do_setup || true > db_go db_go || true ? Ciao, Bastian -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQE+AdPKeBwlBDLsbz4RAtMUAJ98ENQoBRlpwjCK1RbDt6IrVUC5OwCgl4h+ x1RUPuhJ2DwaOXXtMcZVhUY= =cb1V -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: postinst and debconf again
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Thu, Dec 19, 2002 at 04:21:13PM +0100, pp wrote: > so my question is : > how to display message without db_input?? db_input ... || true Same is for other db_ commands which might fail: db_go || true db_stop || true Cheers, Bastian -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQE+Ae80eBwlBDLsbz4RArd1AJ0aE+IAPrze/hjEzQIuTi0aGVtUGQCgiU2S inlb91VuP9ZGGsPgXtyTXJU= =L67A -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: sponsor für selflinux gesucht.
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Mon, Jan 20, 2003 at 08:41:03PM +0100, Andreas Rottmann wrote: > "Nik" <[EMAIL PROTECTED]> writes: > > > hallo! > > > > ich bin einer der maintainer des selflinux projekts. wir würden gerne mit > > unserem .deb file auf den offiziellen debian mirrors vertreten sein. > > > > > To get an actual audience on debian-mentors, you should be posting in > English. Yup, I contacted him in private mail and we discussed some ways to get his package into Debian. He will have to decide either to become a Debian Developer or to file an RFP. Tschöö, Bastian - -- Bastian Kleineidam Atombombe · Plutonium · Fat Man · Do it Yourself · Tim Taylor -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQE+LFiCeBwlBDLsbz4RApevAKCy6n5R5UXJGVRRjcQtseA+u1kkXACfVtPC gPC+mRMjLVSaPsnRHhK48cc= =NS65 -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: In search of mentor...
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thu, Jan 23, 2003 at 08:55:36AM -0800, deFreese, Barry wrote:
> Is anyone out there looking for a fairly newbie to Linux and a total
> greenhorn to C to do some grunt work? Bug fixes, documentation, small
> coding??
Yup, we need a lot of man pages[1].
Then, you can try to test unreproducible bugs[2].
If you happen to speak other languages besides English, we need a
lot of package descriptions and documentation translated[3].
Hope this answers your question.
[1] http://qa.debian.org/man-pages.html
[2] http://qa.debian.org/bts-unreproducible.html
[3] http://ddtp.debian.org/how_it_works/get_involved.en.html
Cheers, Bastian
- --
Bastian Kleineidam
Atombombe · Plutonium · Fat Man · Do it Yourself · Tim Taylor
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.1 (GNU/Linux)
iD8DBQE+MC79eBwlBDLsbz4RAkzYAKCv+VuSANTRGgS1DgnHk3THPz+ypwCZARk1
+GFjBkrMJyaIJ+xKQjdReo8=
=hEIr
-END PGP SIGNATURE-
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: How to be a great Debian Developer
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Mon, Jan 27, 2003 at 10:37:29PM +0100, Russell Coker wrote: > On Mon, 27 Jan 2003 21:37, Matej Cepl wrote: > > What's so wrong with maintaing just one package? > > It's like salted peanuts. Once you have one you can't stop. ;) I second that emotion .) - -- Bastian Kleineidam Atombombe · Plutonium · Fat Man · Do it Yourself · Tim Taylor -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQE+NcFpeBwlBDLsbz4RAofyAJ9otkjgLPXXBbT+X8uaUQCuAG3aoQCeKmdL 53eKu5o50SKarAFiVCpJdfY= =h/V9 -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Question about lintian's shell-script-fails-syntax-check
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Marco, On Tue, Jan 28, 2003 at 09:39:15PM +0100, Marco Kuhlmann wrote: > The scripts seem to work fine in spite of their syntax > errors, but I am not sure how to convince lintian about that. Read file:///usr/share/doc/lintian/lintian.html/ch2.html#s2.4 for lintian overrides. Cheers, Bastian - -- Bastian Kleineidam Atombombe · Plutonium · Fat Man · Do it Yourself · Tim Taylor -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQE+Nvt4eBwlBDLsbz4RAh2jAJ0QSg3DHTDfTR+jcpPU4bWhm1wQ9QCZAbiI H2vDo/WygF0alSZcfGhBdas= =mWrO -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: In search of mentor...
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Fri, Jan 31, 2003 at 08:48:04AM -0600, Graham Wilson wrote: > On Fri, Jan 24, 2003 at 08:51:04AM -0800, deFreese, Barry wrote: > > B. How do I select something that isn't going to be way over my head > > from the start? (Remember I'm pretty much still a newbie). Any > > pointers? Barry, I don't know exactly your programming experience, but to develop something useful in Unix/Linux, and especially developing packages for Debian you must at least be familiar with the following tools: - - the 'bash' shell - - the 'man' program to read documentation (lots of documentation) - - the 'make' utility for Makefiles (for example the debian/rules file is a Makefile) - - the programming language (Perl, C, etc) in which the package is written If you dont know one of the above points, start learning them. There are numerous tutorials about these tools on the web, and it is always good to ask a local (ie. in your office) Linux guru for help. > this might be difficult to do. id say just try something, and if it is > too difficult, ask for help, or move on to something else. I am suggesting the xtraceroute package 'xt'. It is written in C and has some bugs to fix, notably catching error conditions. Cheers, - -- Bastian Kleineidam Atombombe · Plutonium · Fat Man · Do it Yourself · Tim Taylor -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQE+Op8IeBwlBDLsbz4RAiyeAKC2kYkUxs4DkEZuv4e7NVG+YP01OwCcDChC ClF+jBFpcvkzsaoTLMAhayg= =3+nZ -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: debmake and dh-make
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mon, Feb 03, 2003 at 01:15:57PM +0100, Gergely Nagy wrote:
> lintian will not catch everything.
In case you want to run lintian *and* linda on debuild, see my patch at
http://bugs.debian.org/178456
There are some things in linda which lintian is not checking (and vice
versa of course).
Cheers,
- --
Bastian Kleineidam
Atombombe · Plutonium · Fat Man · Do it Yourself · Tim Taylor
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.1 (GNU/Linux)
iD8DBQE+PnLmeBwlBDLsbz4RAg90AJwKjzO8yFcqbP4v4k6WbEPapHVriQCdHIBP
TvQcycpPS43IqK0hGncMBTE=
=r2W4
-END PGP SIGNATURE-
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: PythonCard packaging advice?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Mon, Feb 03, 2003 at 03:38:11PM -0600, Kenneth Pronovici wrote: > I've now noticed that this doesn't conform to policy and I'm a little > confused about what packages I should provide. Only the name of the module package is against policy - it should be python-pythoncard. > Should I provide the package python-pythoncard that depends on on python > (>=2.2), python (<<2.3), or should I instead provide python2.2-pythoncard > that depends on python2.2 and also python2.3-pythoncard that depends on > python2.3? See below. > This is getting a bit more complicated than I expected it to be. I'd > appreciate any advice you can give me. I don't know why you split docs and samples, I'd put them in one package, the samples go into /usr/share/doc//examples/. The doc package depending on either of the library packages. The user can decide which pythoncard version to use for the samples. python2.2-pythoncard Depends: python2.2 python2.3-pythoncard Depends: python2.3 pythoncard-doc Depends: python2.2-pythoncard | python2.3-pythoncard Greetings, - -- Bastian Kleineidam Atombombe · Plutonium · Fat Man · Do it Yourself · Tim Taylor -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQE+P6gJeBwlBDLsbz4RAiuIAJ9JnatTa0a8+KFCbbG7W6bMAA8cNwCfUtxy 80MB+Mw9N6GDtsjxd0sGn6k= =hNRy -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: k3b test package
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sat, Feb 15, 2003 at 03:08:49PM +0100, Henning Moll wrote:
> deb http://www.planet-moll.de/debian woody main
Hm,
# HEAD http://www.planet-moll.de/debian
403 Forbidden
Could you provide source packages? See dpkg-source(1) or debuild(1)
for more info.
Cheers,
Bastian
- --
Bastian Kleineidam
Atombombe · Plutonium · Fat Man · Do it Yourself · Tim Taylor
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.1 (GNU/Linux)
iD8DBQE+TmqZeBwlBDLsbz4RAlehAKC3E9R6h7xJwYSa7gaSI22Pwv8yHwCfQB5n
Aydfj28mE/2BdH3xj2G+qm4=
=Oc8+
-END PGP SIGNATURE-
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: plugger
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thu, Feb 20, 2003 at 02:32:18PM +0800, Bernard Blackham wrote:
> Seems you beat me to ITP'ing it. I can't seem to reach your site
> though.
Being at least the third one who has packaged mozplugger[1] for
private use: please also support the not-yet-in-debian phoenix
browser[2] which I am using right now. I symlinked the mozplugger.so
from /usr/lib/{mozilla,phoenix}/plugins/ to make it work for both
browsers.
[1] http://people.debian.org/~calvin/debian/
[2] http://people.debian.org/~eric/debian/
Cheers, Bastian
- --
Bastian Kleineidam
Atombombe · Plutonium · Fat Man · Do it Yourself · Tim Taylor
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.1 (GNU/Linux)
iD8DBQE+VIhqeBwlBDLsbz4RAo4rAKCRijIiw08dzAlxVDy36MKtqd6h2ACfS1dO
hkdfUswLeXmCbxSule8y/T4=
=efXR
-END PGP SIGNATURE-
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: plugger
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Fri, Feb 21, 2003 at 06:44:15PM +0800, Bernard Blackham wrote: > Taking a deeper look at phoenix, it seems that it does check > $HOME/.mozilla/plugins, but not /usr/lib/mozilla/plugins. I feel > this is a bug with phoenix which doesn't really warrant a workaround > to be implemented in mozplugger and other plugins. > > There are several other browsers based on Mozilla that may or may > not check /usr/lib/mozilla for plugins. Should every plugin for > Mozilla have to check for the existence of each Mozilla-based > browser? It seems slightly ludicrous, IMHO. Also, the postinst/prerm > idea fails if mozplugger is installed before phoenix :( > > Just some random thoughts. Comments? :) Can you install every Mozilla plugin automatically and without changes in Phoenix? I am not sure that this is the case, especially on those with additional interface files (googlebar?). I have nothing against a shared /usr/lib/mozilla/plugins directory, but I think there is not much sense in if the plugins are not always compatible. Anyway, you are free to package things your own way, my symlink strategy is short-sighted (private package, I needed it, not much time, you know the deal ;) cheers, - -- Bastian Kleineidam Atombombe · Plutonium · Fat Man · Do it Yourself · Tim Taylor -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQE+V6keeBwlBDLsbz4RAppSAJ9/d86T+mnpyue9hjuWl3gLcOT9vgCfXmHI HxVt1dpBCXwvSuxMFQDGtWI= =GKmc -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: lintian warning: debconf-is-not-a-registry
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Sat, Feb 22, 2003 at 04:05:06PM +, Martin Orr wrote: > I am packaging the MCBSAM package, for managing a squid proxy server. This > package uses configuration files which must be set up at install time, so I > have a script /usr/sbin/mcbsam-configure which is run by my postinst to do > the setting up. When I run lintian on the .deb, I get the following warning: > W: mcbsam: debconf-is-not-a-registry ./usr/sbin/mcbsam-configure > Should I simply ignore it? If you run lintian -i, you can read some explanation of the warning. It says you should not use debconf calls outside of post/preinst scripts. Info: In the Unix tradition, Debian packages should have human-readable and human-editable configuration files. This package uses debconf commands outside its maintainer scripts, which often indicates that it is taking configuration information directly from the debconf database. Typically, packages should use debconf-supplied information to generate configuration files, and - to avoid losing configuration information on upgrades - should parse these configuration files in the `config' script if it is necessary to ask the user for changes. . Some standalone programs may legitimately use debconf to prompt the user for questions. If you maintain a package containing such a program, please contact &maint; so that the exception would be recognized in future versions of Lintian. Other exceptions to this check include configuration scripts called from the package's post-installation script. Cheers, - -- Bastian Kleineidam Atombombe · Plutonium · Fat Man · Do it Yourself · Tim Taylor -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQE+V6mveBwlBDLsbz4RAlbDAKC4B0QAemkEjbxNTitpcouV35jUkgCdFXy+ yNgOnCyipxG1bnfprI4ILEo= =rBxy -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: files in .deb
On Fri, Feb 28, 2003 at 07:57:02PM +1100, Matthew Palmer wrote:
> * Add your file to the package somewhere
You should put it in the debian/ directory. If its a binary file, you
have to uuencode it (to make diff happy) and on install uudecode it.
There is a perl script attached for this.
Cheers, Bastian
--
Bastian Kleineidam
Atombombe · Plutonium · Fat Man · Do it Yourself · Tim Taylor
#!/usr/bin/perl
$_ = <> until ($mode,$file) = /^begin\s*(\d*)\s*(\S*)/;
open(OUT,"> $file") if $file ne "";
while (<>) {
last if /^end/;
next if /[a-z]/;
next unless intord() - 32) & 077) + 2) / 3) ==
int(length() / 4);
print OUT unpack "u", $_;
}
chmod oct $mode, $file;
pgp0.pgp
Description: PGP signature
Unofficial package tips
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, here are some of my tips when packaging unofficial software as .debs. Perhaps its useful for someone :) Packaging tips for unofficial packages == Maintainer email - You can set the DEBEMAIL environment variable if you like to have a different email address for Debian packaging. Example: export [EMAIL PROTECTED] Native Package or not? - -- Short answer: don't make a native package. Be sure to provide a .orig.tar.gz before calling $(DEBUILD). a) Download the original mypackage-1.0.tar.gz b) Rename it to an original upstream file (notice the underscore instead of a dash): mv mypackage-1.0.tar.gz mypackage_1.0.orig.tar.gz c) Untar it and run dh_make, answer its questions: tar xzvf mypackage_1.0.orig.tar.gz cd mypackage-1.0 && dh_make; cd .. d) As we have already the orig.tar.gz, delete the .orig tree: rm -rf mypackage-1.0.orig e) edit mypackage-1.0/debian/* and build your debian package (see below for the $(DEBUILD) variable): cd mypackage-1.0 && $(DEBUILD) Package version - --- The Debian package version number is parsed from the top entry of debian/changelog, eg. "mypackage (1.1-0.1) unstable; urgency=low". Notice here the "-0.1", this is the debian internal number, and it must be lower than "-1" for unofficial packages. Subsequent releases must have "-0.2", "-0.3", etc. An official package will have "1.1-1". If there is already an official package eg with version "1.1-4", then use "1.1-4.1", "1.1-4.2", ... Package description - --- If you already maintain official Debian packages, your package description can note that this is not an official one. I usually add these two lines in front of the package description to remind users that even if this package is signed by my GPG key, its not an official one: File debian/control: Description: this is mypackage *** Unofficial package from [EMAIL PROTECTED] *** . Bug reports - --- The standard tool for reporting bugs is "reportbug". Your package should have: File /usr/share/bug/mypackage/control: Send-To: [EMAIL PROTECTED] See /usr/share/doc/reportbug/README.developers for more info. Building the package - You should sign your packages with your GPG key. Run "gpg --gen-key" to generate one. You can also use my patch at http://bugs.debian.org/178456 to add --linda option to debuild. Here is the debuild line I am using right now (you have to replace 32EC6F3E with your own GPG key id): File Makefile: # run debuild, log everything to [EMAIL PROTECTED] define DEBUILD (debuild -pgpg -sgpg -k32EC6F3E -tc -L -i 2>/dev/stdout && echo "built ok" > ../$@) | tee ../[EMAIL PROTECTED] endef mypackage: cd mypackage-1.1 && $(DEBUILD) Making it apt-get'able - -- a) Configure dput: File /home/joe/.dput.cf: [local] fqdn = localhost incoming = /home/joe/myarchive allow_unsigned_uploads = 0 b) Copy all mypackage files into your archive: dput local mypackage_1.1-0.1.changes c) Change into the myarchive directory and call: apt-ftparchive sources . | gzip -9 > Sources.gz apt-ftparchive packages . | gzip -9 > Packages.gz d) As root, add the deb and deb-src line: File /etc/apt/sources.list: # ... more deb lines above deb file:/home/joe/myarchive ./ deb-src file:/home/joe/myarchive ./ e) make it available for others by putting myarchive on a webserver. Then others can have File /etc/apt/sources.list: # my http repository deb http://www.joesdomain.org/~joe/myarchive ./ deb-src http://www.joesdomain.org/~joe/myarchive ./ Cheers, Bastian - -- Bastian Kleineidam Atombombe · Plutonium · Fat Man · Do it Yourself · Tim Taylor -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQE+X4FbeBwlBDLsbz4RAml6AKDFvK2jPyZvGR0ceE30MtlQ7t++DwCbBTSU IDTwzU66KSeQD1b2MjNg+HY= =qYHC -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Unofficial package tips
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Fri, Feb 28, 2003 at 07:02:05PM +0100, Michel Dänzer wrote: > I have found pbuilder to be a great way to avoid this as well as other > build time side effects. I tested it several weeks ago and it did not work for me. Perhaps I should give it another try. Cheers, Bastian - -- Bastian Kleineidam Atombombe · Plutonium · Fat Man · Do it Yourself · Tim Taylor -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQE+X78deBwlBDLsbz4RAs9qAJ487FxPBfMMsFGsnaRgW6nWzzD+pgCeLviv 6S8xEvoxxvQlvbLSMMHXgL0= =pLbb -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Unofficial package tips
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Fri, Feb 28, 2003 at 08:19:51PM +0100, Henning Moll wrote:
> Thanks for you tips! But still some questions remain:
>
> On Friday 28 February 2003 16:33, Bastian Kleineidam wrote:
> > Native Package or not?
> > --
> > Short answer: don't make a native package.
>
> Can you explain 'native package'? Did you mean 'binary-only' package by that?
A native package is one without a .orig.tar.gz (see dh_make(1)).
Everytime you upgrade a native package, you'll upload the complete
source code (.deb, .diff.gz, .changes, .dsc, .tar.gz).
Upgrading a non-native package usually uploads (.deb, .diff.gz, .changes,
.dsc) and only once .orig.tar.gz.
> > Be sure to provide a
> > .orig.tar.gz before calling $(DEBUILD).
>
> Hmm, dh_make is trying to do a similar approach. Why not use that way?
I like to have the original .tar.gz exactly as I downloaded it. dh_make
unpacks the source and repacks it to a new .orig.tar.gz.
> In addition i have some questions to the Depends section in debian/control:
> ${shlibs:Depends} is a nice feature, but i think for many packages/libraries
> it is way to strict, because it's always using the versions of installed
> packages which may not be necessary. So what's the best/common way to handle
> this?
The library version number is there for some reason: binary compatibility.
If you drop the version number from library depends, your package may
break when a new library is there.
> It is possible to let ${shlibs:Depends} do its job and then lower that
> requirements?
Its possible, but its not recommended.
> To be somewhat concret:
> Currently i am building an inoffical package for k3b (for woody/sarge). I have
> KDE3.1 installed and am building against that. But k3b only requires KDE
> higher 3.x. So i wonder if i could lower the corresponding entry in the
> Depends section?
I am not sure that all kde libraries are binary compatible between 3.1
and 3.0 versions. Just leave the depends as they are.
Cheers,
Bastian
- --
Bastian Kleineidam
Atombombe · Plutonium · Fat Man · Do it Yourself · Tim Taylor
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.1 (GNU/Linux)
iD8DBQE+X8TCeBwlBDLsbz4RAuvbAJ0fgLFcBWL4HEH+1jQ0T/ZWErJKswCfZinH
/0CPr8KzI37tdhzbpcA3dI4=
=a0te
-END PGP SIGNATURE-
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Unofficial package tips
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Fri, Feb 28, 2003 at 11:38:33PM -0500, Joey Hess wrote: > Bastian Kleineidam wrote: > > > Hmm, dh_make is trying to do a similar approach. Why not use that way? > > I like to have the original .tar.gz exactly as I downloaded it. dh_make > > unpacks the source and repacks it to a new .orig.tar.gz. > > Why would dh_make go out of its way to violate best practices like that? Correct me if I'm wrong, but I thought the preferred way was to use an existing original tarball, not generate a new one with dh_make. And I don't know if dh_make restores the original user, mode and timestamps of the files in the original tar. I remember dimly having problems with that and gpg-signed upstream tarballs. Cheers, Bastian - -- Bastian Kleineidam Atombombe · Plutonium · Fat Man · Do it Yourself · Tim Taylor -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQE+Y54OeBwlBDLsbz4RAgtxAJ4zlIHDkxQxt7JOgsYa6Ws7xvK1MwCguD4F 4VFw+UGG6Wuv+LFyRBfj+BQ= =ba2s -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: How to obtain current package version number?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Tue, Mar 04, 2003 at 01:41:58PM +0100, Marc Haber wrote: > how can a package learn about its current version number? Package information is stored in /var/lib/dpkg/available. There is already a package parsing this information: grep-dctrl You can do it yourself with awk/sed/whatever though. > Does a maintainer script know the package version, so that it can > write the version number to a file? # example: current bash version number BASH_VERSION=`grep-available -P -s Version -n -r '^bash$'` Ciao, Bastian - -- Bastian Kleineidam Atombombe · Plutonium · Fat Man · Do it Yourself · Tim Taylor -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQE+ZKbTeBwlBDLsbz4RAuFCAJ4uxWK3kOv5Cx/xZDgbsgYkf9ITXQCfV8r2 wrH9mafOinGUDrnin0SnMoA= =uew3 -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Unofficial packaging tips [update]
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, I updated my previously posted tips for building and maintaining unofficial packages. Url is http://people.debian.org/~calvin/unofficial/ Changes are (thanks to some of your suggestions): * mention the official packaging guide, the Developers Reference. * use dh_make -f switch instead of manual renaming * describe a versioning scheme that does not clash with NMUs * use the dput `local' method * use mini-dinstall Tschöö, - -- Bastian -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQE+ahwGeBwlBDLsbz4RAoDrAJsEyr4bfoHHXiEj6cB23rE5a8HKvACeIfZM fp2J5H4Apnd2oRrik5nz4ac= =YSyu -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: closing bugs in changelog
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Tue, Apr 01, 2003 at 02:26:30PM +0200, Frank Küster wrote: > Hi all, > > is there any automatic behind the (Closes: #12345) in the changelog? Yes. > Is this parsed after upload to close bugs? Yes. ciao, - -- F: Warum heist ein Löwe eigentlich Löwe? A: Weil er durch die Wüste löft. -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQE+iY94eBwlBDLsbz4RAr+BAKDVgIAsCqGmZs5JIKV/fUyOMI8shQCfYivP FQJCz0NsW5ZPM4v5LC7Yq2g= =4G0X -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Sponsor for TWiki package
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, On Tue, Apr 01, 2003 at 02:29:28PM +0200, Francesco P. Lovergine wrote: > On Tue, Apr 01, 2003 at 08:36:15AM +1000, Sven Dowideit wrote: > > Hello, > > I made some updates the twiki package to the latest upstream release > > (01Jan2003) about 2 months ago, and have since been trying to get the > > current maintainer to upload the changes. > > > > Unfortuanatly I get the feeling that Mark is unavailable (due to time > > constraints) so I would like to 'borrow' a debian developer as a > > sponsor. > > > > Did you ask Mark explicitely for adoption? Hijacking packages without > notices is not a good practice. Martin promised to do something about inactive developers. At least we should have a guiding document (or a formal process) on how to determine inactivity, eg. initial contact, waiting phase, hijacking. Cheers, Bastian - -- Panischer Anruf bei der Bahndirektion: "AUF DEM BAHNDAMM LIEGT EIN GLEIS!" Sagt der Bahnbeamte: "Das ist auch gut so!" und hängt wieder auf. 5 Minuten der gleiche Anrufer: "Jetzt haben sie den almen alten Mann übelfahlen" -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQE+iZCreBwlBDLsbz4RAszRAJ9OqFEEchnSN8Omy4jei2knH2TLbACghli4 hK0m1uR2NmG7uizbSy0Fexc= =qTsk -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: bug reports
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Neil, On Wed, May 28, 2003 at 06:49:50AM -0400, Neil Roeth wrote: > I'd like to download the web page of bugs by maintainer, > http://bugs.debian.org/cgi-bin/[EMAIL PROTECTED], and all > the bug reports linked to on that page, so that I can refer to them offline. > But, wget doesn't work, What's the error message? At least it works for me: # wget "http://bugs.debian.org/cgi-bin/[EMAIL PROTECTED]" - --13:53:00-- http://bugs.debian.org/cgi-bin/[EMAIL PROTECTED] => [EMAIL PROTECTED]' Resolving bugs.debian.org... done. Connecting to bugs.debian.org[146.82.138.7]:80... connected. HTTP request sent, awaiting response... 200 OK Length: unspecified [text/html] [<=> ] 22,52724.89K/s 13:53:02 (24.89 KB/s) - [EMAIL PROTECTED]' saved [22527] > I think because they are not static pages, they are > created on the fly by scripts. Only Content-Length is missing (thats why the length above is unspecified). > Before I spend time figuring this out, does > anyone know of an already existing means to do this? Some tips: - - put " quotes around the url - - check if you use a proxy ($http_proxy is set) - - check if you are blocked by a firewall Ciao, Bastian - -- .~.Bastian Kleineidam . calvin (at) debian.org /V\ /( )\ GnuPG Schlüssel http://kampfwurst.net/gpgkey.txt ^^-^^ Stehen zwei Pilze im Wald, und langweilen sich. Sagt der eine: "Da kommt der bekloppte Hase. dem hauen wir jetzt ein paar auf's Maul!" Ruft der andere: "Hey, Hase, komm doch mal zu uns rüber!" Hase: "Moin, was geht ab? Pilze: "Du hast keinen Hut auf!" und, uutz, auf's Maul! Am nächsten Tag langweilen sich die Pilze wieder. Der eine: "Den Hasen kriegen wir so bestimmt nicht nochmal!" Der andere: "Ne, aber ich habe eine Idee: wir fragen ihn nach Kippen, wenn er Filter hat, hauen wir ihm auf's Maul, weil wir nur ohne Filter rauchen, und wenn er ohne Filter hat, gibt's auf die Klötze, weil wi nur mit Filter rauchen!" Pilze: "Hey, Hase, komm doch mal her!" Hase: "Ne, ihr wollt mir ja doch nur wieder auf's Maul hauen!" Pilze: "Nein, ehrlich nicht! Das von gestern tut uns leid, kommt nicht wieder vor. wir wollen nur 'ne Kippe von dir!" Hase: "Okay, was wollt ihr denn, mit oder ohne Filter?" Pilze: uutz, auf die Klötze: "Du hast keinen Hut auf!" -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.2 (GNU/Linux) iD8DBQE+1KR9eBwlBDLsbz4RAsQYAKCuaWkerpmtiuakvu5EsK/z4oDq6gCfWiY+ gNexeVkYI0cuLba3qO9NYos= =SAN4 -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: ncurses
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Mon, Jun 02, 2003 at 08:40:11AM -0400, Barry Pollock wrote: > I am doin some ncurses stuff for ed [...] > This would speed up editing a great amount. Kudos to you using ed as your daily favourite editor :) I remember my first time with a Unix system: I asked about an editor and my neigbour said "vi". After many beeps I got frustrated and asked if there was something else. He said "yeah, there's ed". Thank god this did not drive me mad... Ciao, Bastian - -- .~.Bastian Kleineidam . calvin (at) debian.org /V\ /( )\ GnuPG Schlüssel http://kampfwurst.net/gpgkey.txt ^^-^^ Zwei Hochhäuser sitzen im Keller und bügeln Marmelade. Kommt ein Schraubenschlüssel rein, läuft die Wand hoch, die Decke entlang, die Wand wieder runter, macht das ganze nochmal, und läuft wieder raus. Sagt das eine Hochhaus zum andern: "Hast du das gesehen? Das ist ja wirklich kaum zu glauben, daß es sowas gibt!" Antwortet das andere: "Ja, ich weiss, der grüßt nie, wenn er wo reinkommt." -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.2 (GNU/Linux) iD8DBQE+22fleBwlBDLsbz4RAgKUAJ9H32qnwUWlAUDfe7SwOjbh8qYxXQCgqr7C MX5T58CWUfoDO7agqI5ZL5c= =YlYE -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Howto revive the old Debian get-changelog cgi script?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Howdy, some time ago there was a script at http://cgi.debian.org/cgi-bin/get-changelog to fetch changelogs of debian packages (in [1] there is some info about it) [1] http://kt.zork.net/debian/dd20010105_17.html#5 It is not available any more, and I want to have its functionality revived. I'd like to have something like apt-listchanges, but before I download a .deb, not afterwards. It is very helpful when you are on a dialup connection and want to know what has changed in a package before downloading it. So, before tinkering with the debian machines and searching for files, is there any suggestion on how to make this feasable? And on what is the best Debian machine to run such cgi scripts? Here are some possibilities I can think of: 1) Follow and parse one of the -changes lists, archive the changelogs in a machine-readable format, indexed by source/binary package. 2) Have an archive of all the changelog.Debian.gz files. This way I can reuse apt-listchanges functionality. 3) Have an archive of all the .deb files (ie an FTP mirror). Same as 2), only I have to extract the changelogs. Ciao, Bastian - -- .~.Bastian Kleineidam . calvin (at) debian.org /V\ /( )\ GnuPG Schlüssel http://kampfwurst.net/gpgkey.txt ^^-^^ F: Was hat vier Beine und einen Arm? A: Ein glücklicher Pitbull-Terrier -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.2 (GNU/Linux) iD8DBQE+5y6jeBwlBDLsbz4RAv63AJ9rZ5w4fZtrtQaC9L2HOPQjiDLpTwCeOmi7 kDd0H7Wq8QDREqlThb5FPLc= =7slY -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: new version number needed to repair broken download?
Marc, simply re-upload. Marc Haber wrote: I recently goofed and invoked debsign twice on a package. This resulted in a Signature on a Signature on my .dsc file, causing katie (?) to reject my upload. Can I simply re-upload a correctly signed package, or do I need do bump the version number for katie (?) to pick the upload up again?
Re: Open Motif
Hi, On Fri, Jan 11, 2002 at 12:10:55PM +0100, Stefan Schwandter wrote: > But I don't understand why I also have to make both a statically and a > dynamically linked version of the package, as reqested by 12.8. Some people might not want to install the non-free libmotif, but want to have your package. > I also don't understand why a statically linked version is necessary at > all, since libmotif is in the debian distribution. Non-free is not included in official Debian CD's, as its not part of the main distribution. Greetings, Bastian pgpUjnGl0vPq3.pgp Description: PGP signature
Procedure for new GPG key?
Hello, what is the correct procedure to get a new GPG key into the Debian keyring? My old one expired unnoticed by me :(. I mailed [EMAIL PROTECTED], but my three mails seem to be dropped silently. My key Infos: Old key ID 959C340F New key ID 32EC6F3E (signed by [EMAIL PROTECTED]) URL: http://blackhole.pca.dfn.de:11371/pks/lookup?op=get&search=0x32EC6F3E I would be very thankful if anyone can help me on this because I want to upload package updates and bugfixes. Greetings, Bastian pgpVNe0rOq8vC.pgp Description: PGP signature
Re: Uncertainty regarding kernel module and /etc/modutils/*
Tore, On Tue, Apr 23, 2002 at 10:46:45PM +0200, Tore Anderson wrote: > So, should I accept the redundancy and let dh_installmodules do its job, > or should I use the postinst/rm approach? Or the insanely clever solution > one of you are going to suggest? :-) If you have identical files in your packages, you could make a new package -common and depend on it. Several packages have done this (apache-common, fetchmail-common, ...). Greetings, Bastian pgpDEKqMge0oj.pgp Description: PGP signature
Re: Multiple configure-make cycles
Hi, On Fri, Apr 26, 2002 at 07:08:26PM -0700, David Caldwell wrote: > Instead of building in the source dir, create 2 build directories, cd to > each and ../configure with different options. Then in the make section, cd > into each build dir and make. So essentially you are building the different > versions in parallel, rather than repeating them in a serial fashion. Look at the FOX library, it uses exactly this approach to build a default libfox0.99 and one with debugging libfox0.99-dbg. Greetings, Bastian pgp3Nm6ULCzsw.pgp Description: PGP signature
Sponsor search for linkchecker
Hi folks, some people may have noticed that my linkchecker package [1] is very out of date. Well, this is mainly because my GPG key expired and I am waiting now a long time to get the new key [2] into the keyring. In the meantime, would someone please sponsor an upload of the current version 1.4.2 [3]. This version fixes all bugs in the DBS [4]. The package source is signed with my new key. [1] http://packages.debian.org/linkchecker [2] http://blackhole.pca.dfn.de:11371/pks/lookup?op=get&search=0x32EC6F3E [3] http://people.debian.org/~calvin/debian/ [4] http://bugs.debian.org/linkchecker Thanks, Bastian pgp3v3rvgviFL.pgp Description: PGP signature
Re: Multiple configure-make cycles
Hi,
On Sat, Apr 27, 2002 at 11:06:59AM -0400, Joey Hess wrote:
> That sounds redundant, what's wrong with building once with -g, linking
> shared, stripping, calling that one package, and then linking w/o
> stripping for the -dbg package?
The configure.in has different -D defines for debugging, so you have to
compile twice, one with --enable-release, the other with --enable-debug.
FOX has internal tracing (FXTRACE) and asserts (FXASSERT) macros that
are enabled when DEBUG is defined, disabled otherwise.
Greetings, Bastian
[configure.in snippet]
dnl Debugging turned on
AC_MSG_CHECKING(for debugging)
AC_ARG_ENABLE(debug,[ --enable-debug compile for debugging])
AC_MSG_RESULT([$enable_debug])
if test "x$enable_debug" = "xyes" ; then
CXXFLAGS="${CXXFLAGS} -g -DDEBUG"
fi
dnl Building for release
AC_MSG_CHECKING(for release build)
AC_ARG_ENABLE(release,[ --enable-releasecompile for release])
AC_MSG_RESULT([$enable_release])
if test "x$enable_release" = "xyes" ; then
CXXFLAGS="${CXXFLAGS} -O2 -DNDEBUG"
if test "${GXX}" = "yes" ; then
CXXFLAGS="${CXXFLAGS} -Wuninitialized -ffast-math -finline-functions
-fomit-frame-pointer -fexpensive-optimizations"
fi
fi
pgpJBFXzj0snF.pgp
Description: PGP signature
Re: Sponsor search for linkchecker
On Sat, Apr 27, 2002 at 01:22:58PM -0500, Luis Bustamante wrote: > On Sat, Apr 27, 2002 at 04:44:29PM +0200, Bastian Kleineidam wrote: > > Hi folks, > > > > some people may have noticed that my linkchecker package [1] is very > > out of date. > > Well, this is mainly because my GPG key expired and I am waiting now > > a long time to get the new key [2] into the keyring. > > > > In the meantime, would someone please sponsor an upload of the current > > version 1.4.2 [3]. This version fixes all bugs in the DBS [4]. > > If nobody else have done it yet, I'll take care of it, I'll upload it in > a couple of hours. Cool, thanks. Bastian pgpfAFApC3iCB.pgp Description: PGP signature
Re: Checking for installed package-alternative in a wrapper-skript
On Sat, Jun 22, 2002 at 07:08:00PM +0200, Andreas Metzler wrote:
> Hello,
> Is there some canonical fast way to check in a script whether inn,
> inn2 or cnews is installed on the system?
What dpkg does is parsing /var/lib/dpkg/status.
I recommend using dpkg - its error prone to rely on an implicit data
format of the status file.
If you look in the file, there is a paragraph for each package. What you
want is searching the Packages: line, then search its Status: line and
see if its last entry is "installed".
You could use awk to do this (replace with your package name).
Greetings, Bastian
test.sh
if awk -f test.awk /var/lib/dpkg/status; then
echo "installed";
else
echo "not installed";
fi
test.awk
/^Package: / { found = ($2==""); }
/^Status: / {
if (found) exit ($4!="installed");
}
END { if (!found) exit 1; }
pgpUvhwQAYTLy.pgp
Description: PGP signature
Re: postinst question
On Thu, Jun 27, 2002 at 02:29:44PM +0200, Marc Leeman wrote: > > I must be missing something here, I want the package to show a not when > installing to indicate that custom builds _are_ very useful for the time > being, but guess what, it's not asking :( > > Any help? Try this in config: > db_input high nvrec/nvrec_build_optimised db_input high nvrec/nvrec_build_optimised || true db_go || true Greetings, -- .~. /V\ Bastian Kleineidam · Unleash the power. Use Linux. /( )\ ^^-^^ pgpRFW7ChpQBI.pgp Description: PGP signature
Re: KDE3 package
Hi, On Sat, Aug 03, 2002 at 10:25:42PM +0200, Marc Leeman wrote: > btw, k3b is a full fledged graphical frontend for burning, composing, > copying CDs (data and audio) and even some tools for burning video to > CDs. btw, some graphics for k3b are from Ayo (http://www.73lab.com/), which is one of the best Tux art I've seen. Greetings, -- .~. /V\ Bastian Kleineidam · Unleash the power. Use Linux. /( )\ ^^-^^ pgpk55cbWeF5p.pgp Description: PGP signature
Re: name collisions
On Mon, Aug 19, 2002 at 10:49:09AM +0200, Marc Leeman wrote: > Also, is renaming of binaries for debian at the discresion of the debian > maintainer (me) or should it be upstream (possibly interactive)? You should only rename binaries if its necessary for the Debian package (eg. a name clash, or multiple versions of this package have to coexist). Otherwise leave the name alone. Users, developers and the documentation normally refer to the original name and a rename would confuse things. Of course there is nothing against asking for renaming at the upstream author. Tschööö, Bastian -- Bastian Kleineidam · [EMAIL PROTECTED] · GPG key ID 32EC6F3E pgpijsBiRLzdK.pgp Description: PGP signature
Re: How much redundancy?
On Tue, Aug 20, 2002 at 09:11:13AM -0700, Sean 'Shaleh' Perry wrote: > In the end I believe that as long as a package in Debian is being used by more > than 1 person it has value. Let's fight the urge to just package something > because it is interesting. However if there is a user base out there then > Debian should support them. Our users should not have to compile software on > their own. I agree. The only thing to be careful when packaging things is keeping the dependency list small. I remember those days where the gettext package suddenly depended on some emacs package (*shudder*). So this leads sometimes to packages split into "foo-common", "foo-gnome", "foo-gtk" or sometimes just compiled without gome/kde support. Cheers, Bastian -- Bastian Kleineidam · [EMAIL PROTECTED] · GPG key ID 32EC6F3E pgp6Nmc2RPmfm.pgp Description: PGP signature
Re: chained dependencies handling in debian/control
On Mon, Sep 02, 2002 at 01:46:53PM +0200, Alexandre wrote: > Hello, > > Let package A depend on package B and C. > Let package B depend on package C. > I maintain A, someone else maintains B and C. > > Should I explicitely let A depend on B and C in debian/control, or is it > OK -- or better -- to let it depend only on B? You should depend on that what you are using. So if you have for example #!/usr/bin/python in one of your script, depend on the "python" package. Trusting on implicit dependencies is not a guarantee for your package to work in the future. cu, -- Bastian Kleineidam reflexionsniveau AT web.de calvin AT users.sf.net calvin AT debian.org pgpnu7xYuQYrA.pgp Description: PGP signature
Re: Check over doclifter package
On Fri, Sep 06, 2002 at 01:23:38PM +0100, Ross Burton wrote: > I have packaged ESR's doclifter package for Debian, and would like > someone to have a look at the packaging for me. Someone who has > packaged Python before would be good, as it depends on Python 2.2. When > I run lintian I get one message I am worried about -- "strange > interpreter" -- it appears that lintian doesn't know that python2.2 is a > valid interpreter. Yes, see bug #114164. cu, -- Bastian Kleineidam reflexionsniveau AT web.de calvin AT users.sf.net calvin AT debian.org pgpNiUcIYuj7A.pgp Description: PGP signature
Re: problem replacing package
On Mon, Sep 09, 2002 at 06:19:08PM +0200, Matus fantomas Uhlar wrote:
> Hello,
>
> I would like to compile some packages optimised for my processor. I have k6
> at home and pentiumII at work, and would like to speed up some programs
> running on those.
How about installing pentiumbuilder, configure it for k6 and do
apt-get source --build
If you are satisfied, you can put on hold and it does not get
updated automatically.
> I thought that if my package provides libogg0, it could be installed and
> replace libogg0 without any problems. What do I wrong?
The problem is you are providing a virtual package libogg0, which does
not work in all situations.
cu,
--
Bastian Kleineidam
reflexionsniveau AT web.de
calvin AT users.sf.net
calvin AT debian.org
pgpD6xPXhhtRR.pgp
Description: PGP signature
Re: Kernel module package depending on kernel-headers.
Sven,
On Fri, Sep 13, 2002 at 05:05:27PM +0200, Sven LUTHER wrote:
> Ideally, i would build depend on kernel-headers-2.4, and have a option
> that i can pass to debian/rules which would detect what kernel-headers
> package provide this and set the kernel version accordyingly.
>
> Is this a better solution ?
Why not makeing a unicorn-src package, providing the upstream tarball?
Its always a major hassle to compile kernel-binaries (or module-binaries)
for all available platforms/processors. So a source package is the
preferred way to distribute kernel addons.
> How do other module packages handle this, do someone know at a good such
> package i could use as example ?
The current ALSA packages (apt-cache show alsa-source) are doing it
this way.
cu, Bastian
--
Bastian Kleineidam
reflexionsniveau AT web.de
calvin AT users.sf.net
calvin AT debian.org
pgpsaip89bJ4T.pgp
Description: PGP signature
Re: Kernel module package depending on kernel-headers.
On Fri, Sep 13, 2002 at 06:01:05PM +0200, Sven LUTHER wrote: > On Fri, Sep 13, 2002 at 05:15:59PM +0200, Bastian Kleineidam wrote: > > > How do other module packages handle this, do someone know at a good such > > > package i could use as example ? > > The current ALSA packages (apt-cache show alsa-source) are doing it > > this way. > > Ok, i will look at it ... > > Mmm is there not a smaller example to look at ? I only have a slow modem > line. Here are some more: nvidia-kernel-src, cryptoapi-core-source, cryptoloop-source, i2c-source, lm-sensors-source > My idea was that people would do : > > apt-get source unicorn > cd unicorn-0.3.4 > edit debian/rules and modify the KERNEL_VERSION variable > dpkg-buildpackage ... With the above packages, it would be like this: apt-get install unicorn-source cd /usr/src && tar xzvf unicorn-x.y.tar.gz cd /usr/src/kernel-source-2.4.18 && make-kpkg modules_image insmod unicorn Cheers, Bastian -- Bastian Kleineidam reflexionsniveau AT web.de calvin AT users.sf.net calvin AT debian.org pgpR4XJp2ckCg.pgp Description: PGP signature
Re: Multiple compile of source (ie, different configure lines for each package)
> > On Wed, Sep 18, 2002 at 08:33:04AM +0200, Turbo Fredriksson wrote: > > > I'm packaging Nagios. It builds tree packages from one source: > > > 'nagios-text', 'nagios-pgsql' and 'nagios-mysql'. The differences > > > is quite obvious: Compile the source three times, each time with > > > different ./configure options. > > > > > > The problem I'm facing is that I want to 'scratch' the source > > > after each build. Actually: build first package, move it aside, > > > build second package - move it aside etc. The ./configure as well as the make can be done in a target subdir, so there is no need to scratch or clean the source tree. You'll find a beautiful example of this at the fox package (libfox1.0 et al.) Tschöö, Bastian -- Bastian Kleineidam reflexionsniveau AT web.de calvin AT users.sf.net calvin AT debian.org pgp5F1fshdlDo.pgp Description: PGP signature
Re: inclusion of a debian dir in upstream src
On Tue, Sep 24, 2002 at 04:34:29PM -0700, Sam Powers wrote: > Is it a good idea to keep a debian directory upstream? I have CVS access, > so I think it'd make it easier for me, and also for others who want to > build custom debs, if the debian files were in CVS. Having an upstream debian/ is good. A minute saved is a minute earned. cu, -- Bastian Kleineidam reflexionsniveau AT web.de calvin AT users.sf.net calvin AT debian.org pgpDHnKOsK5RT.pgp Description: PGP signature
Re: Python scrips and deps
On Thu, Sep 26, 2002 at 12:38:08PM +0100, Ross Burton wrote: > I am the maintainer for doclifter, a Python 2.2 script. Upstream (RMS) > claims that it requires Python 2.2, so the script calls "/usr/bin/env > python2.2" and the package Requires: python2.2. > > However, lintian now moans as "python2.2" isn't a valid Python > interpreter. I'd say this is a bug (and I intend to report it in a > minute) but this does bring up an interesting issue. You should not use the env trick. Use #!/usr/bin/python2.2 for python2.2 scripts and #!/usr/bin/python for python scripts. > The default Python release in Debian Sid (and testing?) is now 2.2, so > should I change the package to call "python" and change the requirements > to Depends: python? It is always good to support the default python version. You must have Depends: python (>=2.2), python (<<2.3) You can also join the debian-python mailing list if you need more sophisticated answers :) Hope this helps, Bastian -- Bastian Kleineidam reflexionsniveau AT web.de calvin AT users.sf.net calvin AT debian.org pgpvU7dUjBj01.pgp Description: PGP signature
Re: Python scrips and deps
On Thu, Sep 26, 2002 at 01:52:56PM +0200, Jérôme Marant wrote: > Why shouldn't env be used? Its nothing that policy forbids, but its good for people like me who keeps forgetting that I have local python versions for testing installed :) > > It is always good to support the default python version. You must have > > Depends: python (>=2.2), python (<<2.3) > > But I guess that if upstream absolutely want to use a specific Python, > there isn't any reason not to leave Depends: python2.2. > I don't see any problem here. Sure, its not a problem. cu, Bastian -- Bastian Kleineidam reflexionsniveau AT web.de calvin AT users.sf.net calvin AT debian.org pgpJhFDwGeaXv.pgp Description: PGP signature
Re: linker failure -- debuild fails -- please help
On Thu, Oct 10, 2002 at 12:23:00PM -0700, justin cunningham wrote: > I'm trying to compile a program from debian src and have gcc 2.95 and > related libraries installed so why does gcc die on this line? > > gcc -g -O2 -Wall -o .libs/vchkpw vchkpw.o vconfig.o > ./.libs/libvpopmail.so -lfreecdb -lfreecdbmake -ldl > /usr/lib/libmysqlclient.so -lz -lm -lnsl -lcrypt > /usr/bin/ld: cannot find -lz libz.so is missing. You should install zlib1g-dev. Hope this helps, Bastian -- Bastian Kleineidam reflexionsniveau AT web.de calvin AT users.sf.net calvin AT debian.org pgpz8BPdfWnGN.pgp Description: PGP signature
Re: Misc questions: add image to package, man page for cgi script, etc
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Frédéric, On Mon, Nov 25, 2002 at 11:35:26PM +1100, Frederic Schutz wrote: > 1) I'd like to add a binary file to the upstream source (an image, so that > all images are available locally and no Internet connection is needed). > Obviously, the diff file doesn't like binaries, so what is the best way to > do it ? [Currently, I added the image as a uuencoded file, with a > "Build-Depends: sharutils" (sharutils contains uudecode) and a line in > debian/rules that decodes it at build time] You have to use uuencode/uudecode. There is also a Perl script for this. This should answer your question: http://lists.debian.org/debian-mentors/2002/debian-mentors-200203/msg00027.html IIRC, theres development to enable binary diffs for the debian package utils, but I dont remember the thread anymore. > 2) Should I write a man page for a CGI script ? If yes, could someone > point me to an example of such a page ? No, there is no rule that one must have a man page for CGI scripts. Usually I make a note in the package description, in README or in README.Debian (whatever seems appropriate) that theres a CGI script available. > 3) The package contains a Perl script that can be used either as a cgi-bin > and on the command line [it is not the same script than in 2) and I > already wrote a man page for the command line version]. I can install it > in either /usr/lib/cgi-bin or /usr/bin and put a symbolic link in the > other directory. What is the best way to do it ? I would think that I > should put it in the cgi-bin directory, since the web server (Apache) will > probably not follow a symlink, while this is not a problem for a command. > Any other thought on the question ? As you said, you should not have symlinks pointing outside of /usr/lib/cgi-bin. I think there are two options: a) symlink from /usr/bin/foo to /usr/lib/cgi-bin/foo b) Make a cgi-only version and a commandline-only version of the script and put them in the proper dir. Because I'm lazy, I'd prefer a). Cheers, Bastian -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQE94iXceBwlBDLsbz4RAjEOAKC1pFcMFhj+Pvag8tRHYKEgbagssQCeNh2s YaxPrleHItp/r6AuDx2F+nk= =gu+8 -END PGP SIGNATURE-
why is linkchecker gone?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, I noticed that my linkchecker package is gone[0] from unstable, but the last upload was ok[1]. There are strange debcheck errors on the package tracking page[2] which I dont understand, all buildd logs are successful. Can someone point me to whats wrong? [0] http://packages.debian.org/linkchecker [1] http://packages.qa.debian.org/l/linkchecker.html [2] http://qa.debian.org/debcheck.php?dist=unstable&package=linkchecker Cheers, Bastian -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQE961iDeBwlBDLsbz4RAgBzAJ9Bf4ZqxCTk2XczaDF55O/SfEnl5gCfRc5l C7ZurCbIjjUiVLERp6rqiOw= =OEV1 -END PGP SIGNATURE-
Re: RFS (2nd call): tsclient-0.56
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Fri, Dec 06, 2002 at 01:51:14AM +1100, Andrew Lau wrote: > Hey everyone, > Robster still hasn't uploaded tsclient 0.56 since promising to > sponsor/upload it on Sunday, so my RFS still stands, and is repeated > below. Thanks in advanced to anyone who picks it up. Let him have a little more time, you know the deal: free volunteer, real life, getting cinema tickets for LotR II... all this is more important! I would wait another 1-2 weeks for Robster to check your package and upload it. Cheers, Bastian -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQE973LceBwlBDLsbz4RAru0AJ9/y41Yzc8gvem5/oBTmFGujiSCaACfYe29 pk7oDGEN3mtPrPnbaaKF7ao= =BVl8 -END PGP SIGNATURE-
Re: ifeq( PACKAGE, "mypackage")
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Thu, Dec 19, 2002 at 10:50:18AM +, Mark Howard wrote: > Hi, > is it possible to determine the name of the current package at the > build stage of debian/rules (multi-binary source), so that only the > parts required for the current package are built? (and also so that they > aren't build twice). How about the FOX solution (apt-get source libfox1.0): define build-deb dh_testdir dh_testroot dh_installdocs -p$@ dh_installexampless -p$@ ... endif package1: build build-deb package2: build build-deb ... Ciao, Bastian -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQE+AauxeBwlBDLsbz4RAjsNAKCCSXVks7RJOjAAQPssO0SMdBM2ugCeOL3a LCRfPEd6ysHMDtL3x6IUZWQ= =adxd -END PGP SIGNATURE-
Re: postinst and debconf again
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Thu, Dec 19, 2002 at 02:58:11PM +0100, pp wrote: > I posted my problem some time ago. > > > postinst script: Hmm, this looks like a debian/config script, not a postinst script. But the debconf docs are fading already in my minds, so it might be ok. > #! /bin/sh -ex > > . /usr/share/debconf/confmodule > db_version 2.0 > db_title "Midgard library package." > > if $mysqlcmd -D mysql -e 'use midgard;' >/dev/null 2>&1 ; then > > db_input "high" midgard/error > db_go > db_stop > else > db_input high midgard/do_setup || true > db_go db_go || true ? Ciao, Bastian -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQE+AdPKeBwlBDLsbz4RAtMUAJ98ENQoBRlpwjCK1RbDt6IrVUC5OwCgl4h+ x1RUPuhJ2DwaOXXtMcZVhUY= =cb1V -END PGP SIGNATURE-
Re: postinst and debconf again
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Thu, Dec 19, 2002 at 04:21:13PM +0100, pp wrote: > so my question is : > how to display message without db_input?? db_input ... || true Same is for other db_ commands which might fail: db_go || true db_stop || true Cheers, Bastian -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQE+Ae80eBwlBDLsbz4RArd1AJ0aE+IAPrze/hjEzQIuTi0aGVtUGQCgiU2S inlb91VuP9ZGGsPgXtyTXJU= =L67A -END PGP SIGNATURE-
Re: sponsor fü r selflinux gesucht.
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Mon, Jan 20, 2003 at 08:41:03PM +0100, Andreas Rottmann wrote: > "Nik" <[EMAIL PROTECTED]> writes: > > > hallo! > > > > ich bin einer der maintainer des selflinux projekts. wir würden gerne mit > > unserem .deb file auf den offiziellen debian mirrors vertreten sein. > > > > > To get an actual audience on debian-mentors, you should be posting in > English. Yup, I contacted him in private mail and we discussed some ways to get his package into Debian. He will have to decide either to become a Debian Developer or to file an RFP. Tschöö, Bastian - -- Bastian Kleineidam Atombombe · Plutonium · Fat Man · Do it Yourself · Tim Taylor -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQE+LFiCeBwlBDLsbz4RApevAKCy6n5R5UXJGVRRjcQtseA+u1kkXACfVtPC gPC+mRMjLVSaPsnRHhK48cc= =NS65 -END PGP SIGNATURE-
Re: In search of mentor...
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thu, Jan 23, 2003 at 08:55:36AM -0800, deFreese, Barry wrote:
> Is anyone out there looking for a fairly newbie to Linux and a total
> greenhorn to C to do some grunt work? Bug fixes, documentation, small
> coding??
Yup, we need a lot of man pages[1].
Then, you can try to test unreproducible bugs[2].
If you happen to speak other languages besides English, we need a
lot of package descriptions and documentation translated[3].
Hope this answers your question.
[1] http://qa.debian.org/man-pages.html
[2] http://qa.debian.org/bts-unreproducible.html
[3] http://ddtp.debian.org/how_it_works/get_involved.en.html
Cheers, Bastian
- --
Bastian Kleineidam
Atombombe · Plutonium · Fat Man · Do it Yourself · Tim Taylor
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.1 (GNU/Linux)
iD8DBQE+MC79eBwlBDLsbz4RAkzYAKCv+VuSANTRGgS1DgnHk3THPz+ypwCZARk1
+GFjBkrMJyaIJ+xKQjdReo8=
=hEIr
-END PGP SIGNATURE-
Re: How to be a great Debian Developer
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Mon, Jan 27, 2003 at 10:37:29PM +0100, Russell Coker wrote: > On Mon, 27 Jan 2003 21:37, Matej Cepl wrote: > > What's so wrong with maintaing just one package? > > It's like salted peanuts. Once you have one you can't stop. ;) I second that emotion .) - -- Bastian Kleineidam Atombombe · Plutonium · Fat Man · Do it Yourself · Tim Taylor -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQE+NcFpeBwlBDLsbz4RAofyAJ9otkjgLPXXBbT+X8uaUQCuAG3aoQCeKmdL 53eKu5o50SKarAFiVCpJdfY= =h/V9 -END PGP SIGNATURE-
Re: Question about lintian's shell-script-fails-syntax-check
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Marco, On Tue, Jan 28, 2003 at 09:39:15PM +0100, Marco Kuhlmann wrote: > The scripts seem to work fine in spite of their syntax > errors, but I am not sure how to convince lintian about that. Read file:///usr/share/doc/lintian/lintian.html/ch2.html#s2.4 for lintian overrides. Cheers, Bastian - -- Bastian Kleineidam Atombombe · Plutonium · Fat Man · Do it Yourself · Tim Taylor -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQE+Nvt4eBwlBDLsbz4RAh2jAJ0QSg3DHTDfTR+jcpPU4bWhm1wQ9QCZAbiI H2vDo/WygF0alSZcfGhBdas= =mWrO -END PGP SIGNATURE-
