Bug#683840: RFS: razorqt/0.4.1-1~exp1 [ITP]
Package: sponsorship-requests
Severity: wishlist
Dear mentors,
I am looking for a sponsor for my package "razorqt".
I am a DM and I already take care of a few widely used packages, I
intend to keep this one in good shape as well. Initially I decided to
put this one into experimental, since it's not very stable upstream
and there are new versions coming soon.
Related RFP/ITP bug:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=652745
Package name: razorqt
Version: 0.4.1-1~exp1
Upstream Author: Razor-qt team
URL: http://razor-qt.org/
License: LGPL2.1+
Section: x11
It builds those binary packages:
libqtxdg0 - Implementation of the XDG Specifications for Qt, libs
libqtxdg0-dev - Implementation of the XDG Specifications for Qt,
development pack
librazorqt0 - Shared libraries for Razor-qt desktop environment
librazorqt0-dev - Shared libraries for Razor-qt desktop environment,
development pa
razorqt - Lightweight desktop environment, all components
razorqt-appswitcher - Application switcher component for Razor-qt
desktop environment
razorqt-config - Configuration component for Razor-qt desktop environment
razorqt-data - Shared data files for Razor-qt desktop environment
razorqt-desktop - Desktop component for Razor-qt desktop environment
razorqt-panel - Panel component for Razor-qt desktop environment
razorqt-policykit-agent - PolicyKit agent component for Razor-qt
desktop environment
razorqt-power - Power manager component for Razor-qt desktop environment
razorqt-runner - Application launcher component for Razor-qt desktop
environment
razorqt-session - Session manager component for Razor-qt desktop environment
To access further information about this package, please visit the
following URL:
http://mentors.debian.net/package/razorqt
Alternatively, one can download the package with dget using this command:
dget -x http://mentors.debian.net/debian/pool/main/r/razorqt/razorqt_0.4.1-1~exp1.dsc
There is a lintian warning related with shared libraries file, I don't
know if it causes harm but the package should work all right. I would
appreciate if somebody advises on how to get rid of it, never
experienced it before, and it's happening only in one of the binary
packages when in fact the structure for most of them is the same.
Cheers.
--
Manuel A. Fernandez Montecelo <manuel.montezelo@gmail.com>
Reply to: