[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#283932: O: ksetisaver -- Seti screensaver for KDE



Package: wnpp
Severity: normal

The current maintainer of ksetisaver, Filippo Panessa <kalem@linux.it>,
is apparently not active anymore.  Therefore, I orphan this package
now.  If you want to be the new maintainer, please take it -- see
http://www.debian.org/devel/wnpp/index.html#howto-o for detailed
instructions how to adopt a package properly.

Some information about this package:

Package: ksetisaver
Binary: ksetisaver
Version: 0.3.3-0.1
Priority: optional
Section: contrib/kde
Maintainer: Filippo Panessa <kalem@linux.it>
Build-Depends: debhelper (>= 4.0.0), kdelibs4-dev, libqt3-compat-headers
Architecture: any
Standards-Version: 3.5.9
Format: 1.0
Directory: pool/contrib/k/ksetisaver
Files: e49ffeb665940db52557247a36edf6a8 613 ksetisaver_0.3.3-0.1.dsc
 4b3c69865c2d6c28341df42b28e9f552 631649 ksetisaver_0.3.3.orig.tar.gz
 5e07bc5b722724b34facc701f65f8d22 4082 ksetisaver_0.3.3-0.1.diff.gz

Package: ksetisaver
Priority: optional
Section: contrib/kde
Installed-Size: 808
Maintainer: Filippo Panessa <kalem@linux.it>
Architecture: i386
Version: 0.3.3-0.1
Depends: kdelibs4 (>= 4:3.1.1), libart-2.0-2 (>= 2.3.8), libc6 (>= 2.3.1-1), libfam0c102, libgcc1 (>= 1:3.3-0pre5), libpng12-0, libqt3c102-mt (>= 3:3.1.1), libstdc++5 (>= 1:3.3-0pre6), xlibs (>> 4.1.0), xlibs (>> 4.2.0), zlib1g (>= 1:1.1.4), setiathome (>= 3.0-1)
Filename: pool/contrib/k/ksetisaver/ksetisaver_0.3.3-0.1_i386.deb
Size: 141450
MD5sum: 0b9c13bbf20b8c45b8b8fe1b353baad7
Description: Seti screensaver for KDE
 The seti@home project offers two binaries: a command-line version and a
 graphical frontend (xsetiathome). KSetiSaver acts as a normal screensaver
 for KDE replacing seti@home frontend.
 When it is launched it starts monitoring a seti@home client. KSetiSaver
 is also able to launch setiathome. That means seti@home is only active,
 when the screensaver is.

Justification: Mail bounces, no reply on alternative address, rejected from
NM as unresponsive



Reply to: