RFS: QTM - Qt4 blogging client

Package name: QTM Version: 0.5.8.2 Upstream author: M.J. Smith < Home page: http://qtm.blogistan.co.uk License: GPLv2 or later Section: x11 Location of the package: http://kadu.net/~patryk/qtm/qtm_0.5.8.2-1.dsc http://kadu.net/~patryk/qtm/qtm_0.5.8.2-1.diff.gz http://kadu.net/~patryk/qtm/qtm_0.5.8.

Re: RFS: QTM - Qt4 blogging client

now here's a corrected version: http://kadu.net/~patryk/qtm/qtm_0.5.8.2-1.dsc http://kadu.net/~patryk/qtm/qtm_0.5.8.2-1.diff.gz http://kadu.net/~patryk/qtm/qtm_0.5.8.2.orig.tar.gz -- Patryk Cisek signature.asc Description: This is a digitally signed message part.

RFS: xmms-musepack - input plugin for playing mpc music files.

ces from: http://poczta.prezu.one.pl/xmms-musepack -- Regards, Patryk Cisek pgphZu3oolwyf.pgp Description: PGP signature

Re: RFS: xmms-musepack - input plugin for playing mpc music files.

, and the "©" copyright symbol > are all interchangeable; but the sequence '(C)' is legally null, so > use the proper symbol instead. I've used the template from: /usr/share/common-licenses/BSD or: http://www.opensource.org/licenses/bsd-license.php like meny other packages. -- Regards, Patryk Cisek pgpwHqIcbD2os.pgp Description: PGP signature

Re: RFS: xmms-musepack - input plugin for playing mpc music files.

not touching the code, so no new version), Because it can take a while before next release. Of course I'll update the source package when it happens. I've also submitted the package to sponsors.debian.net: http://sponsors.debian.net/viewpkg.php?id=65 -- Regards Patryk Cisek pgp

RFS: doorman -- Port knocking daemon for SSH and other servers.

urrently doorman can only protect TCP services. The project's home page is at: http://doorman.sourceforge.net/ You can get the source and i386 binary packages from: http://poczta.prezu.one.pl/doorman/ -- Regards, Patryk Cisek pgpj8mvBCOVZR.pgp Description: PGP signature

RFS: Kadu

://kadu.net * Source package: http://kadu.net/~patryk/debian * License: Gnu/GPL -- Patryk Cisek pgpkZ6WPvlsgD.pgp Description: PGP signature

Re: RFS: Kadu

ot; dialog) reads directly from AUTHORS, THANKS, LICENSE and about-changes-tab.txt files. Contents of these are put in "About..." dialogs tabs. So we need these files uncompressed. Since it's not obvious, I've also added this explanation to debian/changelog -- ftp-masters might also want to ask this question. :) Package is in the same place as before: http://kadu.net/~patryk/debian/ -- Patryk Cisek pgpyRnx3jvfRr.pgp Description: PGP signature

Re: RFS: Kadu

gt;= 0.5.0-1)" It's now "Recommends: kadu" > * /usr/share/kadu/themes/icons/kadu.xpm - why not install it into > /usr/share/pixmaps/ ? Yeah, Good idea, since this directory holds other applications icons. > * please add info about your packaging copyrights to debian

Re: stripping by upstream

ols project. For example in kadu package configure checks if it was run with "--enable-debug". If not, it adds "-s" to $CFLAGS/$CXXFLAGS. This of course results in stripping when g++ links kadu binary. So I patched configure. -- Patryk Cisek pgpwmgiBifO6f.pgp Description: PGP signature

RFS: I'm looking for a sponsor for xlogmaster (an orphaned kackage).

Hello all. I've ITAd it (see #192676) and looking for a sponsor. I have fixed some warnings and bugs that lintian reported. The errors were: E: xlogmaster binary:E: xlogmaster binary:   file-in-etc-not-marked-as-conffile /etc/xlogmaster/entries/README E: xlogmaster binary: file-in-etc-not-mark

Re: RFS: I'm looking for a sponsor for xlogmaster (an orphaned kackage).

> * Why don't you want these files to be conffiles ? Because they're not a configuration files and I think they definitly shouldn't be listed in conffiles. If for example the READMEs change in the future, dpkg will ask the user if he/she wants the newer version of them, but that shouldn't be que

Re: RFS: I'm looking for a sponsor for xlogmaster (an orphaned kackage).

> I thought the user would only be prompted if the file changed *and* they > had made local modifications to the old file. The last is fairly unlikely > for READMEs. Yes that's true. I've included these READMEs to conffiles now. Changed package files are at: http://poczta.prezu.one.pl/xlogmaster/

Re: RFS: I'm looking for a sponsor for xlogmaster (an orphaned kackage).

> What's the point of this? For example, why would one want the README to > stick around after the package has been removed? (c.f. 10.7.3) Unless > the README is actually a configuration file, it should be > in /usr/share/doc, perhaps named as README.configuration if there's a > different README al

Re: RFS: I'm looking for a sponsor for xlogmaster (an orphaned kackage).

Anibal Monsalve Salazar agreed to sponsor the package. -- Regards. pgp0IkNARuqdw.pgp Description: PGP signature

Re: RFS: I'm looking for a sponsor for xlogmaster (an orphaned kackage).

> Anibal Monsalve Salazar agreed to sponsor the package. Certainly if he decides the package is all right. :) -- Regards. pgpm5rGUpZSw4.pgp Description: PGP signature