Bug#524403: ITP: iguanair -- IguanaWorks Infrared Tranceiver support tools
Hello Max, (Yes, two months for a reply is a long time :-) On Saturday 31 of July 2010, Max Vozeler wrote: I recently got a iguanaIR USB and would like to have it supported without the need to rebuild lirc. Stefanos, are you still interested? Let me know if you need review and/or sponsorship. I'm happy to help but lack the time to maintain it properly myself. After your mail I tried to package iguanaIR but I failed. While everything else seems OK, I can't package the python bindings. Is there any documentation on how python bindings are supposed to be packaged? I've looked some other packages and they seem to do some hocus pocus for this. I understand that there should be one package (with the bindings) per python version but I don't know which python versions I'm supposed to package for and how to incorporate this to CDBS (iguanaIR isn't using distutils). While I'm not as inderested as before and I somehow lack the time, I'm willing to complete the packaging and maintain the package. I've found the creators of iguanaIR to be helpfull and they look forward for a debian package so any bugs etc will most probably be handled by them. Since the releases of iguanaIR software are not frequent this will not be very time consiming. So, if you can help me with the python bindings packaging we can upload this soon. I'm currently using CDBS for the packaging. -- To UNSUBSCRIBE, email to debian-wnpp-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/201009141455.46979@v13.gr
Bug#529955: ITP: iguanair -- IguanaWorks Infrared Tranceiver support tools
Package: wnpp Severity: wishlist Owner: Stefanos Harhalakis v...@v13.gr * Package name: iguanair Version : 0.99 Upstream Author : IguanaWorks Inc. * URL : http://iguanaworks.net/ * License : GPLv2 and LGPLv2 Programming Lang: C and Python Description : IguanaWorks Infrared Tranceiver support tools This is a package for iguanaworks support tools and development files. It adds the required tools to manage IgianaWorks IR transceivers and the appropriate development files (library and headers) for adding iguaunaIR support to lirc (see bug #524403) -- To UNSUBSCRIBE, email to debian-wnpp-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#524421: ITP: katimon -- KDE ATI Graphics Card Monitor
Package: wnpp Severity: wishlist Owner: Stefanos Harhalakis v...@v13.gr * Package name: katimon Version : 1.0.2 Upstream Author : Stefanos Harhalakis v...@v13.gr * URL : http://www.v13.gr/proj/katimon/ * License : GPLv2 Programming Lang: Python Description : KDE ATI Graphics Card Monitor A KDE program for monitoring ATI graphics cards. This program can: * Display graphics card temperature * Display and modify graphics card fans * Automatically adjust fan speed * Display GPU usage * Display core GPU speed and memory speed * Overclock the graphics card It is written in Python and uses the aticonfig tool. -- To UNSUBSCRIBE, email to debian-wnpp-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#516222: RFS: libnet - orphaning libnet
Hello, On Friday 27 March 2009, David Paleino wrote: retitle 516222 O: libnet -- library for the construction and handling of network packets thanks Hello, libnet has been in RFA (Request for Adoption) for more than a month now, and I'm hereby orphaning it. Someone please pick it up, as it's an important piece of software in Debian. Sam Roberts (CCed) is taking over upstream development, please contact him when adopting libnet. I'm willing to maintain it. I'm not familiar with libnet source code but I'm with its subject and I can package it whenever a new version becomes available or when a new package is needed. From what you say, I guess that the homepage[1] will change in the near future. Is there another one ? I see that you use git. Is it madantory to use git? (I'm not familiar with it). Also, I'm somehow new in this maintaining thing, so if there is someone else interested, please do it... ... but if not, I'd appreciate any information I can have. [1] http://www.packetfactory.net/libnet/ -- To UNSUBSCRIBE, email to debian-wnpp-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#516222: RFS: libnet - orphaning libnet
On Friday 27 March 2009, David Paleino wrote: F/up set, please respect it (I forgot setting it in my first mail, sorry.) Being a user of kmail I don't really know if it is possible to easily handle it. Also, I'm not suer I completely understand what you mean. You want to only send replies to the debian-devel list? (If yes, excuse this reply :-) I see that you use git. Is it madantory to use git? (I'm not familiar with it). No. You (or whoever is going to maintain it) may use whichever $VCS you want. There's some old-ish SVN repository for libnet (I migrated it to git recently, so the history there is not that old -- if you meant to use SVN, that is) http://svn.debian.org/viewsvn/collab-maint/deb-maint/libnet But please note that the SVN repo is quite broken [0] -- you may want to remove it and start it all over again (maybe re-importing it from git?) I have to have this stored in an VCS? For some other packages i packaged (only 1 in debian), i used a local copy (at least to begin with). If yes: Do I have to have the whole package in the VCS or just the debian/ directory? From what I've read I assumed that I only need to have local copies (or a versioning system) of debian/. signature.asc Description: This is a digitally signed message part.
Bug#516222: RFS: libnet - orphaning libnet
Hello, On Friday 27 March 2009, Jan Christoph Nordholz wrote: Hi Stefanos, if you need help, I could lend a hand now and then. I don't have the time to maintain the package on my own, but I have a faible for old and/or undocumented C code and some experience in delving through networking code in particular, so I could e.g. help hunting bugs. Thank you for your offer. I'm also quite familiar with C and networking code and I hope that there will be no problems. If there are any I'll annoy you :-) -- To UNSUBSCRIBE, email to debian-wnpp-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#520765: ITP: fsprotect -- Make filesystems immutable
Package: wnpp Severity: wishlist Owner: Stefanos Harhalakis v...@v13.gr * Package name: fsprotect Version : 1.0.0 Upstream Author : Stefanos Harhalakis v...@v13.gr * URL : http://www.v13.gr/ (not available yet) * License : GPL Programming Lang: Shell Description : Make filesystems immutable fsprotect ease the pain of protecting a system. By using an init script and a initramfs script it can make the root and other filesystems immutable. It uses aufs and tmpfs. A typical admin only has to install fsprotect and add the 'fsprotect' parameter to kernel to make the / immutable. She can also add a list of filesystems to be protected in /etc/default/fsprotect. This is a 'must' for all public computers like those in labs, libraries, etc. -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) -- To UNSUBSCRIBE, email to debian-wnpp-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#510275: krypt
On Friday 02 January 2009, Ana Guerrero wrote: Anyway, without beeing a DD, as a debian user, I'd like to have this program available as a package. So, to conclude, just take a moment to reply with at least a simple go-on or don't-go-on. I won't argue any more. You are free to package it and ask people to sponsor it. Nobody can forbid you of uploading a proper package to Debian if you find a sponsor, but think in the work that this will carry to the distro for maybe little gain. Your package will be some time in unstable, yeah, but its final target won't be being in a debian release given that squeeze (next release after lenny) will have KDE 4. I believe that I cannot take such a decision myself. From my POV (as a debian user) I want this program to be in debian and that's why i packaged it (as expected, I'm also using it). Fotis offered to sponsor it but I don't want to introduce problems to debian, so I'll follow your advice. As for KDE4, krypt will be usable for squeeze too and when the author ports it to KDE4 it will be ported for debian too. Having this in debian may increase the interrest of other/new users for it and they may offer to do the porting themeselves. As I see it, its main/only problem is that it will be replaced by built-in support in KDE4 sometime in the future (perhaps in KDE 4.3) but until then (1 year from now?) it is an essential tool for all encrypted-USB-stick, encrypted-USB-disk and laptop-with-encrypted-data-partition KDE3/4 users. p.s. Should I stop CCing you? -- To UNSUBSCRIBE, email to debian-wnpp-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#510275: ITP: krypt -- KDE GUI for managing volumes encrypted with LUKS
Hello Scott, On Wednesday 31 December 2008, Scott Kitterman wrote: Since it's too late for Lenny and Squeeze will be a KDE4 release, I think there is no point in packaging this until it's ported for KDE4. Krypt only depends on kdelibs. Everything else is HAL and DBUS related, so it should be working with kde4 too. If I understand it correctly, lenny will have kdelibs4 (that's kde3 libs) so it will be usable there too. In fact, krypt only needs libkdeui and libkdecore from the kde libraries (that's what ldd shows). -- To UNSUBSCRIBE, email to debian-wnpp-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#510275: krypt
Thanks for the answer, On Wednesday 31 December 2008, Ana Guerrero wrote: Hi, On Wed, Dec 31, 2008 at 09:54:32PM +0200, Stefanos Harhalakis wrote: Hello there, I've prepared a debian package for krypt [1] (KDE GUI for managing volumes encrypted with LUKS) and while looking for a sponsor, Faidon Liambotis suggested that I should contact you (pkg-kde) too. Is there any special procedure for creating a debian package for a kde program? Krypt only depends on kdelibs4 so it should be able to be used with kde4 too (right?). Is it OK to go-on and look for a sponsor? [1] http://krypt.berlios.de/ I have seen the ITP and marked to answer to the bug number, doing it now (bug Cc'ed). As you might know already, after Lenny, we are replacing KDE 3 with KDE 4, this transition will be quick but replacing all kde 3 apps for kde 4 apps, will take sime (surely too much time). So in the meantime we'll need to keep kdelibs (and part of kdebase), but the ultimate goal is getting ride of that too (and Qt3 too!) Even if you app only needs kdelibs, it is an app that is *integrated* with kde 3.5... I really think it is best wait until it is ported to KDE 4 then package it. I believe that there are some arguments for including it in debian too: a) It is not integrated. It just integrates with the desktop environment. It is a single executable binary that interracts with hal and dbus. After opening a luks device, the device is handled by KDE as a normal mapper device. It should work for gnome and KDE4 too b) From what I've seen, up to KDE 4.2, there is no good support for crypted volumes (correct me me if I'm wrong). This little program fills the gap. c) It's the only way (?) to have easily accessible encrypted removable devices. d) As you said, sime. Why not have this available for that time? e) It is a program that exists today and solves a today's problem. Isn't it better to have this available for the next year (or more), until it is ported to KDE4 or KDE4 gets support for encrypted devices? f) Are there any drawbaks for including this in debian? g) Isn't this what happens with all other packages? AFAIK, the KDE3-KDE4 transition of programs is not a debian's issue but the program's developers. Why not distribute this with debian too? Anyway, without beeing a DD, as a debian user, I'd like to have this program available as a package. So, to conclude, just take a moment to reply with at least a simple go-on or don't-go-on. I won't argue any more. Thanks in advance and have a happy new year. p.s. Please CC me. -- To UNSUBSCRIBE, email to debian-wnpp-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#510275: ITP: krypt -- KDE GUI for managing volumes encrypted with LUKS
Package: wnpp Severity: wishlist Owner: Stefanos Harhalakis v...@it.teithe.gr * Package name: krypt Version : 0.2 Upstream Author : Jakub Schmidtke sja...@users.berlios.de * URL : http://krypt.berlios.de/ * License : GPL Programming Lang: C++ Description : KDE GUI for managing volumes encrypted with LUKS I'm willing to maintain this package for debian. It is also requested with RFP #507655. To my knowledge (and to wnpp lists) noone else is working on it. It seems an easy to package program that should not be hard to maintain. Krypt is a nice gui, very nicely integraded in KDE 3.5, for easy mounting of LUKS encrypted volumes (like USB sticks). -- System Information: Debian Release: 5.0 APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) -- To UNSUBSCRIBE, email to debian-wnpp-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#458340: ITP: vbackup -- A modular backup program
Package: wnpp Severity: wishlist Owner: Stefanos Harhalakis [EMAIL PROTECTED] * Package name: vbackup Version : 0.1.4 Upstream Author : Stefanos Harhalakis [EMAIL PROTECTED] * URL : http://www.it.teithe.gr/~v13/vbackup/ * License : GPLv2, may be changed to GPLv3 Programming Lang: Shell Description : A modular backup program vbackup is a modular backup program. It is a set of scripts that can perform full or incremental system backups. Currently it supports: * Filesystem backups using tar * XFS backups using xfsdump * PostgreSQL backups * MySQL backups * dpkg package list backups -- System Information: Debian Release: lenny/sid APT prefers testing APT policy: (990, 'testing'), (500, 'stable'), (150, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.23.11-v2-v (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
