Bug#452264: ITP: libid3-ruby -- Ruby interface to the id3lib library for editing ID3 tags
Package: wnpp Severity: wishlist Owner: Reto Schuettel <[EMAIL PROTECTED]> * Package name: libid3-ruby Version : 0.5.0 Upstream Author : Robin Stocker <[EMAIL PROTECTED]> * URL : http://id3lib-ruby.rubyforge.org/ * License : Ruby's Programming Lang: Ruby, C++ Description : Ruby interface to the id3lib library for editing ID3 tags libid3-ruby provides a Ruby interface to the id3lib C++ library for easily editing ID3 tags (v1 and v2) of MP3 audio files. Features: - Read and write ID3v1 and ID3v2 tags - Simple interface for adding, changing and removing frames - Quick access to common text frames like title and performer - Custom data frames like attached picture (APIC) - Pretty complete coverage of id3lib's features - UTF-16 support -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#294990: ITP: bontmia -- backup over network to multiple incremental archives
Hi On Mon, Feb 14, 2005 at 09:53:12AM +1100, Matthew Palmer wrote: > On Sun, Feb 13, 2005 at 03:49:45PM +0100, Reto Schuettel wrote: > > On Sun, Feb 13, 2005 at 09:25:15AM +1100, Matthew Palmer wrote: > > > > bontmia creates incremental snapshots of a list of given directories > > > > over the network by using rsync over ssh and hard links. Every snapshot > > > > looks for the user like a complete copy of all the files, but as a > > > > result > > > > of using hard links every unchanged copy of a file is stored only once > > > > on > > > > the hard disk. > > > > > > What advantages does this package have over, say, dirvish or backuppc? > > > > I never used dirvish nor backuppc, so I can't really say what the > > difference are. But it seems like bontmia is simpler than both > > (especially backuppc). > > Simpler in terms of features available, or simpler in terms of configuration > for the same level of features? Fewer features, shorter script and easier configuration... but it isn't a big difference. > > I can't really say if that's a reason for creating a new package, I > > personally would like it, because it's already running on several of my > > machines, but beside of that, it wouldn't be a big problem for me to close > > my ITP. > > > > What do you think? > > It's a tricky one. I'm a firm believer in not duplicating effort, and with > the existence of at least two other packages which appear to do a similar > job, I'm just worried that we'll end up with a lot of packages doing the > same thing, which does nothing except dissipate effort and fragment the user > base of all of the alternatives. However, at the end of the day, you're the > one expending the effort, so if you think it's worthwhile, I've got no > reason to stop you. I made a mistake, I asked the author, created a package and AFTER that I filed an ITP. So, my effort isn't the problem anymore. Splitting up the user base is one... Hmm... I'll try to find a sponsor, with a pointer to this discussion here. The sponsor should decide if it's worth to upload the package. Do you agree with this procedure? Regards, Reto Schüttel -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#294990: ITP: bontmia -- backup over network to multiple incremental archives
Hi Matthew On Wed, Feb 16, 2005 at 10:40:36AM +1100, Matthew Palmer wrote: > On Tue, Feb 15, 2005 at 10:49:44PM +0100, Reto Schuettel wrote: > > I made a mistake, I asked the author, created a package and AFTER that I > > filed an ITP. > > Oooh. Did you check wnpp before you started, in case someone else was > working on the package? Of course :). But I didn't expect a 'hey, we already have that'-problem :). Next time... > > Hmm... I'll try to find a sponsor, with a pointer to this discussion > > here. The sponsor should decide if it's worth to upload the package. Do > > you agree with this procedure? > > I think that's a good idea. A potential sponsor will hopefully look > at bontmia with reference to the other alternatives available, and > make a judgment call on whether it's sufficiently different. Okay! Thanks for your advices! Regards Reto Schüttel -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#286764: bmon-2.0.1 released
close 286764 stop bmon 2.0.1 was released in unstable a few days ago: http://packages.debian.org/unstable/net/bmon Thanks! Reto Schuettel -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#286764: ITP: bmon -- Portable bandwidth monitor and rate estimator
Package: wnpp Severity: wishlist * Package name: bmon Version : 2.0.1 Upstream Author : Thomas Graf <[EMAIL PROTECTED]> * URL : http://suug.ch/~tgr/bmon/ * License : MIT/X Description : Portable bandwidth monitor and rate estimator bmon is a portable bandwidth monitor and rate estimator running on various operating systems. It supports various input methods for different architectures. Variout output modes exist including an interactive curses interface, lightweight HTML output but also simple ASCII output. Statistics may be distributed over a network using multicast or unicast and collected at some point to generate a summary of statistics for a set of node -- System Information: Debian Release: 3.1 APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.9-1-k7 Locale: LANG=C, LC_CTYPE=de_CH (charmap=ISO-8859-1)
Bug#286847: ITP: libnl -- library for applications dealing with netlink socket
Package: wnpp Severity: wishlist * Package name: libnl Version : 0.4.2 Upstream Author : Thomas Graf <[EMAIL PROTECTED]> * URL : http://www.suug.ch/~tgr/libnl/ * License : LGPL Description : library for applications dealing with netlink socket libnl is a library for applications dealing with netlink socket. It provides an easy to use interface for raw netlink message but also netlink family specific APIs. * Sending/Receiving of netlink messages with support for sequence numbers and callbacks to adjust behaviour of parser and help debugging. * Generic cache interface holding items for all netlink users. * Message parsers for all supported netlink users that store into caches * Static structs exporting netlink user data to the application * Dumping routines for all supported netlink users to allow easy dumping of whole caches or single entries * Character string from/to type number transformation routines * Netlink user specific APIs (i.e. change link attributes, add/delete/change neighbour, etc.) -- System Information: Debian Release: 3.1 APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.9-1-k7 Locale: LANG=C, LC_CTYPE=de_CH (charmap=ISO-8859-1)
Bug#286847: Request for package
Hi This library would be mainly useful for a bandwidth monitor tool called bmon[1]. I hoped I could package it by myself, but encountered a problem which I wasn't able solve with my current skills. libnl is at the moment heavily under development (0.x branch) and the upstream author doesn't want to increase the soname after breaking the binary compatibility[2] until the ABI gets stable (IMHO comprehensible). Usually one would link the application statically against the library, but according to the author that isn't possible either. Perhaps somebody with more experience is able to solve this problem... Anyway, I'll change my ITP into an RFP and I'll re-evaluate the situation in a few months. Thanks! Reto Schuettel 1] http://www.suug.ch/~tgr/bmon 2] http://www.netfort.gr.jp/~dancer/column/libpkg-guide/libpkg-guide.html#BINARYCOMPAT
Bug#286847: Request for package
Hi This library would be mainly useful for a bandwidth monitor tool called bmon[1]. I hoped I could package it by myself, but encountered a problem which I wasn't able solve with my current skills. libnl is at the moment heavily under development (0.x branch) and the upstream author doesn't want to increase the soname after breaking the binary compatibility[2] until the ABI gets stable (IMHO comprehensible). Usually one would link the application statically against the library, but according to the author that isn't possible either. Perhaps somebody with more experience is able to solve this problem... Anyway, I'll change my ITP into an RFP and I'll re-evaluate the situation in a few months. Thanks! Reto Schuettel 1] http://www.suug.ch/~tgr/bmon 2] http://www.netfort.gr.jp/~dancer/column/libpkg-guide/libpkg-guide.html#BINARYCOMPAT -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#294990: ITP: bontmia -- backup over network to multiple incremental archives
Package: wnpp Severity: wishlist Owner: Reto Schuettel <[EMAIL PROTECTED]> * Package name: bontmia Version : 0.14 Upstream Author : John Enok Vollestad <[EMAIL PROTECTED]> * URL : http://folk.uio.no/johnen/bontmia/ * License : GPL Description : backup over network to multiple incremental archives bontmia creates incremental snapshots of a list of given directories over the network by using rsync over ssh and hard links. Every snapshot looks for the user like a complete copy of all the files, but as a result of using hard links every unchanged copy of a file is stored only once on the hard disk. The user can specify how old backups should be stored/kept. For example it's possible to keep the daily snapshots of the last 14 days, but also keep one snapshot per month of the last 12 months. The used network bandwidth can also be limited to avoid affecting production systems. -- System Information: Debian Release: 3.1 APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.9-1-k7 Locale: LANG=C, LC_CTYPE=de_CH (charmap=ISO-8859-1) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#294990: ITP: bontmia -- backup over network to multiple incremental archives
Hi Matthew On Sun, Feb 13, 2005 at 09:25:15AM +1100, Matthew Palmer wrote: > > bontmia creates incremental snapshots of a list of given directories > > over the network by using rsync over ssh and hard links. Every snapshot > > looks for the user like a complete copy of all the files, but as a result > > of using hard links every unchanged copy of a file is stored only once on > > the hard disk. > > What advantages does this package have over, say, dirvish or backuppc? I never used dirvish nor backuppc, so I can't really say what the difference are. But it seems like bontmia is simpler than both (especially backuppc). I can't really say if that's a reason for creating a new package, I personally would like it, because it's already running on several of my machines, but beside of that, it wouldn't be a big problem for me to close my ITP. What do you think? Regards, Reto Schüttel -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
