Bug#422162: powerprefs sponsoring
First of all, sorry for being late. On Saturday 23 May 2009, Rogério Brito wrote: Hi, Riku. On May 22 2009, Riku Voipio wrote: On Fri, May 22, 2009 at 12:16:56AM +0100, Marco Rodrigues wrote: I've saw that a new version of powerprefs is at mentors, but anyone had sponsored it yet. http://mentors.debian.net/cgi-bin/sponsor-pkglist?action=details; package=powerprefs perhaps it's a good idea to ask users and the person who prepared the upload to mentors forts. Well, i've uploaded that version ages ago and didn't get a vaste audience... I intend to adopt powerprefs, pbbuttonsd, gtkpbbuttons etc. I have already contacted upstream (Matthias Grimm) and he told me that he is supportive of my maintenance. Please go on. I'm not really motivated to do any real contribution to Debian, and i've recently tried pommed on my ibook and it's working quite well (and I think that powersave does a better job with the powermanagement stuff), so I don't use pbbuttonsd and it's fellow programs anymore. So you're going to do a better jobs than mine... Now, the question is only to ask the person that prepared the update (already contacted by e-mail and with a CC sent to the bug 422162. Please take care of the packages... They were in a decent state, but probably you'll need to polish some rough edges ;) Regards, Rogério. Friendly, Francesco -- :wq -- To UNSUBSCRIBE, email to debian-wnpp-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#530615: ITP: libfile-temp-perl -- return name and handle of a temporary file safely
Package: wnpp Severity: wishlist Owner: Brian Cassidy brian.cass...@gmail.com * Package name: libfile-temp-perl Version : 0.21 Upstream Author : Tim Jenness tjenn...@cpan.org * URL : http://search.cpan.org/dist/File-Temp/ * License : Artistic | GPL-1+ Programming Lang: Perl Description : return name and handle of a temporary file safely File::Temp can be used to create and open temporary files in a safe way. There is both a function interface and an object-oriented interface. The File::Temp constructor or the tempfile() function can be used to return the name and the open filehandle of a temporary file. The tempdir() function can be used to create a temporary directory. The security aspect of temporary file creation is emphasized such that a filehandle and filename are returned together. This helps guarantee that a race condition can not occur where the temporary file is created by another process between checking for the existence of the file and its opening. Additional security levels are provided to check, for example, that the sticky bit is set on world writable directories. See safe_level for more information. -- To UNSUBSCRIBE, email to debian-wnpp-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#530621: RFA: php-imagick -- ImageMagick module for php5
Package: wnpp Severity: normal Description below: Description: ImageMagick module for php5 This package provides a wrapper for ImageMagick library directly from PHP scripts. . PHP5 is an HTML-embedded scripting language. Much of its syntax is borrowed from C, Java and Perl with a couple of unique PHP-specific features thrown in. The goal of the language is to allow web developers to write dynamically generated pages quickly. Homepage: http://pecl.php.net/package/imagick -- To UNSUBSCRIBE, email to debian-wnpp-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#530615: ITP: libfile-temp-perl -- return name and handle of a temporary file safely
On Tue May 26, 2009 at 08:11:06 -0300, Brian Cassidy wrote: * Package name: libfile-temp-perl Version : 0.21 Upstream Author : Tim Jenness tjenn...@cpan.org * URL : http://search.cpan.org/dist/File-Temp/ * License : Artistic | GPL-1+ Programming Lang: Perl Description : return name and handle of a temporary file safely File::Temp can be used to create and open temporary files in a safe way. This module is already packaged: sh-3.2$ ls /usr/share/perl/5.10.0/File/Temp.pm /usr/share/perl/5.10.0/File/Temp.pm sh-3.2$ dpkg --search /usr/share/perl/5.10.0/File/Temp.pm perl-modules: /usr/share/perl/5.10.0/File/Temp.pm Did you miss this, or is it being removed from perl-modules? Steve -- Managed Anti-Spam Service http://mail-scanning.com/ -- To UNSUBSCRIBE, email to debian-wnpp-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#530615: ITP: libfile-temp-perl -- return name and handle of a temporary file safely
On Tue, May 26, 2009 at 9:24 AM, Steve Kemp s...@debian.org wrote: This module is already packaged: sh-3.2$ ls /usr/share/perl/5.10.0/File/Temp.pm /usr/share/perl/5.10.0/File/Temp.pm sh-3.2$ dpkg --search /usr/share/perl/5.10.0/File/Temp.pm perl-modules: /usr/share/perl/5.10.0/File/Temp.pm Did you miss this, or is it being removed from perl-modules? File::Temp is dual-lived (Core+CPAN). This package is meant for users and other packages that require more recent versions of the module that get shipped to CPAN. -Brian -- To UNSUBSCRIBE, email to debian-wnpp-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#527180: ITP: libio-async-perl -- Perl module for implementing asynchronous filehandle I/O
On Mon, 18 May 2009 08:53:23 -0400 Jonathan Yu jonathan.i...@gmail.com wrote: Paul: On Mon, May 18, 2009 at 5:44 AM, Paul LeoNerd Evans leon...@leonerd.org.uk wrote: * Package name : libio-async-perl Version : 0.20 Upstream Author : Paul Evans leon...@leonerd.org.uk * URL : CPAN * License : Perl (Artistic/GPL) Programming Lang: Perl Description : Perl module for implementing asynchronous filehandle I/O Actually, I am shortly about to release 0.21, which makes quite a few updates and changes on 0.20, and fixes some of the suprious testing failures in it (mostly to do with imprecise timings on busy build/testing boxes). Excellent. I've currently done most of the work of packaging that and was just waiting for its dependencies to finish packaging prior to release. However, I'll wait on your new upstream update before doing so. Thanks for letting us know! Is now up on CPAN: http://search.cpan.org/~pevans/IO-Async-0.21/ -- Paul LeoNerd Evans leon...@leonerd.org.uk ICQ# 4135350 | Registered Linux# 179460 http://www.leonerd.org.uk/ signature.asc Description: PGP signature
Bug#530615: ITP: libfile-temp-perl -- return name and handle of a temporary file safely
On Tue, May 26, 2009 at 09:41:53AM -0300, Brian Cassidy wrote: On Tue, May 26, 2009 at 9:24 AM, Steve Kemp s...@debian.org wrote: This module is already packaged: sh-3.2$ ls /usr/share/perl/5.10.0/File/Temp.pm /usr/share/perl/5.10.0/File/Temp.pm sh-3.2$ dpkg --search /usr/share/perl/5.10.0/File/Temp.pm perl-modules: /usr/share/perl/5.10.0/File/Temp.pm Did you miss this, or is it being removed from perl-modules? File::Temp is dual-lived (Core+CPAN). This package is meant for users and other packages that require more recent versions of the module that get shipped to CPAN. Please mention this in the package description. For instance, this is what I put in podlators-perl: Note that the Perl core distribution (supplied in the perl package) already includes older versions of these modules and scripts. Please depend on this package only if you specifically need the newer features, for instance the improved UTF-8 support. Also see #497130, which led to the removal of the previous incarnation of libfile-temp-perl (at version 0.20). -- Niko Tyni nt...@debian.org -- To UNSUBSCRIBE, email to debian-wnpp-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#530615: ITP: libfile-temp-perl -- return name and handle of a temporary file safely
Oh, another note: In this case, yes, File::Temp has changed a lot. (See: http://search.cpan.org/diff?from=File-Temp-0.18to=File-Temp-0.21) However, a lot of the changes are bug fixes and small feature additions, which I think are difficult to mention in a description. A more appropriate place might be debian/changelog, as a sublist under the New upstream release point. But really, I don't think upstream changelog really belongs there - if the user wants to check what has happened between 0.18 and 0.21, they can check the changelog or the diff (see above) themselves. Let's say a CPAN module author has written something which uses File::Temp, but that knows it depends on a bug fix (this happens often in practice). Then they'd just depend on the new File::Temp version, which is no longer core, and it'd need to be packaged. I think that given the large number of bug fixes, the new package makes sense. Otherwise, the other option is to apply a horrendous set of patches to perl-modules for little gain, since modules really depending on the fixes that have been made can depend on them explicitly (and if they are broken, this is something likely to cause test failures which we will notice when building via pbuilder and correct. Or the module author will notice the CPAN Test reports and fix it themselves). Cheers, Jonathan On Tue, May 26, 2009 at 11:05 AM, Jonathan Yu jonathan.i...@gmail.com wrote: I believe this package is already done and sitting in our repository... It's under Tagged but not in the archive yet which means it's heading out to the archive at large. However, I think within the Perl community, this is something that is already widely understood -- that is, dual-lived modules. As an example, this is what apt-cache shows me for libmodule-build-perl (which is part of perl-modules 5.10 and up): Package: libmodule-build-perl Priority: optional Section: perl Installed-Size: 680 Maintainer: Debian Perl Group pkg-perl-maintain...@lists.alioth.debian.org Architecture: all Version: 0.3300-1 Depends: perl (= 5.6.0-16), libarchive-tar-perl, libyaml-perl, libextutils-parsexs-perl Recommends: libextutils-cbuilder-perl, libversion-perl, libpod-readme-perl Suggests: libpar-dist-perl (= 0.17) Filename: pool/main/libm/libmodule-build-perl/libmodule-build-perl_0.3300-1_all.deb Size: 259330 MD5sum: a4d8e1f1b9fa09e66f6e3f7c9c0174d9 SHA1: d7bac6e297e4b66e517a79c4df7f7a6644134a97 SHA256: 9b68211cb027f3054fa028440311cd2f5c0285cce113af52b19077929e096649 Description: Subclassable and make-independent perl module builder alternative Module::Build is a system for building, testing, and installing Perl modules. It is meant to be a replacement for ExtUtils::MakeMaker. Developers may alter the behavior of the module through subclassing in a much more straightforward way than with MakeMaker. Homepage: http://search.cpan.org/dist/Module-Build/ Tag: devel::lang:perl, implemented-in::perl, role::shared-lib There is absolutely no mention of this being a dual-lived module. However, anything that goes through the pkg-perl group is first checked by our main sponsor, gregoa. And he always makes sure we do something like: Build-Depends: perl-modules (= 5.10) | libmodule-build-perl (Assuming both can be used. On the other hand, libmodule-build-perl is only 0.28 or so in the perl-modules core package; if a newer version is necessary then that version will need to be depended upon, as mentioned). Anyway, this is the good thing about having a team that can manage Perl packages (or any similar set of packages) to review them all and make sure they meet some sort of standard. It's more difficult to do this on the wider Debian archive with various people contributing things and various other people (many of whom do not have much experience with packaging Perl) reviewing things. This is particularly why I'd encourage people to consider packaging something under the umbrella of pkg-perl. All in all, I think this package is useful even if there is no real difference between the core package and this one. Why? The same reason we say to prefer EITHER perl-modules = 5.10 OR libmodule-build-perl. We can install on a system (say oldstable) that does not have Perl 5.10 installed; however, it might be able to trivially backport libmodule-build-perl. All with the added advantage of being able to keep a newer version of libmodule-build-perl up to date, which might come out of sync with the core version (and is likely to do so over the life cycle of the Perl release). I can definitely see why there might not be merit to uploading it if there are no changes as compared to the current version. We obviously don't want something made totally unnecessary by the Perl core modules to pollute the Debian archives. Still, I think the benefits outweigh the downsides of such an arrangement. Niko's suggestion of using a description to alert users and other maintainers about the
Bug#530615: ITP: libfile-temp-perl -- return name and handle of a temporary file safely
On Tue, May 26, 2009 at 11:16 AM, Guy Hulbert gwhulb...@eol.ca wrote: On Tue, 2009-26-05 at 11:05 -0400, Jonathan Yu wrote: However, I think within the Perl community, this is something that is already widely understood -- that is, dual-lived modules. This is a 'debian' list ... This is a debian-perl list. :-) The entirety of the list name is important. It is my hope that any people packaging Perl modules for Debian are also a part of the Perl community, as well as the Debian community. Which means they should ideally understand dual-lived modules. If not, I hope they will upload their modules via pkg-perl so we can review them and make sure they're Debian quality before pushing them out, which ultimately benefits our users. -- --gh -- To UNSUBSCRIBE, email to debian-wnpp-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#530615: ITP: libfile-temp-perl -- return name and handle of a temporary file safely
On Tue, 2009-26-05 at 11:05 -0400, Jonathan Yu wrote: However, I think within the Perl community, this is something that is already widely understood -- that is, dual-lived modules. This is a 'debian' list ... -- --gh -- To UNSUBSCRIBE, email to debian-wnpp-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#530615: ITP: libfile-temp-perl -- return name and handle of a temporary file safely
I believe this package is already done and sitting in our repository... It's under Tagged but not in the archive yet which means it's heading out to the archive at large. However, I think within the Perl community, this is something that is already widely understood -- that is, dual-lived modules. As an example, this is what apt-cache shows me for libmodule-build-perl (which is part of perl-modules 5.10 and up): Package: libmodule-build-perl Priority: optional Section: perl Installed-Size: 680 Maintainer: Debian Perl Group pkg-perl-maintain...@lists.alioth.debian.org Architecture: all Version: 0.3300-1 Depends: perl (= 5.6.0-16), libarchive-tar-perl, libyaml-perl, libextutils-parsexs-perl Recommends: libextutils-cbuilder-perl, libversion-perl, libpod-readme-perl Suggests: libpar-dist-perl (= 0.17) Filename: pool/main/libm/libmodule-build-perl/libmodule-build-perl_0.3300-1_all.deb Size: 259330 MD5sum: a4d8e1f1b9fa09e66f6e3f7c9c0174d9 SHA1: d7bac6e297e4b66e517a79c4df7f7a6644134a97 SHA256: 9b68211cb027f3054fa028440311cd2f5c0285cce113af52b19077929e096649 Description: Subclassable and make-independent perl module builder alternative Module::Build is a system for building, testing, and installing Perl modules. It is meant to be a replacement for ExtUtils::MakeMaker. Developers may alter the behavior of the module through subclassing in a much more straightforward way than with MakeMaker. Homepage: http://search.cpan.org/dist/Module-Build/ Tag: devel::lang:perl, implemented-in::perl, role::shared-lib There is absolutely no mention of this being a dual-lived module. However, anything that goes through the pkg-perl group is first checked by our main sponsor, gregoa. And he always makes sure we do something like: Build-Depends: perl-modules (= 5.10) | libmodule-build-perl (Assuming both can be used. On the other hand, libmodule-build-perl is only 0.28 or so in the perl-modules core package; if a newer version is necessary then that version will need to be depended upon, as mentioned). Anyway, this is the good thing about having a team that can manage Perl packages (or any similar set of packages) to review them all and make sure they meet some sort of standard. It's more difficult to do this on the wider Debian archive with various people contributing things and various other people (many of whom do not have much experience with packaging Perl) reviewing things. This is particularly why I'd encourage people to consider packaging something under the umbrella of pkg-perl. All in all, I think this package is useful even if there is no real difference between the core package and this one. Why? The same reason we say to prefer EITHER perl-modules = 5.10 OR libmodule-build-perl. We can install on a system (say oldstable) that does not have Perl 5.10 installed; however, it might be able to trivially backport libmodule-build-perl. All with the added advantage of being able to keep a newer version of libmodule-build-perl up to date, which might come out of sync with the core version (and is likely to do so over the life cycle of the Perl release). I can definitely see why there might not be merit to uploading it if there are no changes as compared to the current version. We obviously don't want something made totally unnecessary by the Perl core modules to pollute the Debian archives. Still, I think the benefits outweigh the downsides of such an arrangement. Niko's suggestion of using a description to alert users and other maintainers about the purpose for such a module is great, and I have no objection to that. Perhaps this is something we can consider in a broader sense to help our users decide. We have to keep in mind though that newer releases of perl-modules may mean that we'd have to remove that particular section, and isn't this essentially what debian/changelog is supposed to be for? Another question is.. If there is a bug with Module::Build that we need to fix, should a bug be filed against perl-modules (= 5.10) or under libmodule-build-perl? We could upgrade our own version and apply our own patches, and just require that in B-D for modules where a bug in M::B is problematic. It's more difficult to get it fixed in perl-modules and subsequently require perl-modules (= 5.10-11) or what-have-you. Cheers, Jonathan On Tue, May 26, 2009 at 9:59 AM, Niko Tyni nt...@debian.org wrote: On Tue, May 26, 2009 at 09:41:53AM -0300, Brian Cassidy wrote: On Tue, May 26, 2009 at 9:24 AM, Steve Kemp s...@debian.org wrote: This module is already packaged: sh-3.2$ ls /usr/share/perl/5.10.0/File/Temp.pm /usr/share/perl/5.10.0/File/Temp.pm sh-3.2$ dpkg --search /usr/share/perl/5.10.0/File/Temp.pm perl-modules: /usr/share/perl/5.10.0/File/Temp.pm Did you miss this, or is it being removed from perl-modules? File::Temp is dual-lived (Core+CPAN). This package is meant for users and other packages that require more recent versions of the module that get shipped to CPAN. Please mention
Bug#512360: RFH: openldap -- OpenLDAP server, libraries, and utilities
Still looking for help? Matt
Bug#530660: ITP: agedu -- a Unix utility for tracking down wasted disk space
Package: wnpp Severity: wishlist Owner: Alexander Prinsier aphe...@mailhaven.com * Package name: agedu Version : N/A Upstream Author : Simon Tatham ana...@pobox.com * URL : http://www.chiark.greenend.org.uk/~sgtatham/agedu/ * License : MIT Programming Lang: C Description : a Unix utility for tracking down wasted disk space Unix provides the standard du utility, which scans your disk and tells you which directories contain the largest amounts of data. That can help you narrow your search to the things most worth deleting. However, that only tells you what's big. What you really want to know is what's too big. By itself, du won't let you distinguish between data that's big because you're doing something that needs it to be big, and data that's big because you unpacked it once and forgot about it. -- System Information: Debian Release: 5.0.1 APT prefers stable APT policy: (990, 'stable'), (800, 'unstable'), (800, 'testing') Architecture: i386 (i686) -- To UNSUBSCRIBE, email to debian-wnpp-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#530660: ITP: agedu -- a Unix utility for tracking down wasted disk space
Samuel Thibault wrote: Alexander Prinsier, le Tue 26 May 2009 20:21:14 +0200, a écrit : However, that only tells you what's big. What you really want to know is what's too big. By itself, du won't let you distinguish between data that's big because you're doing something that needs it to be big, and data that's big because you unpacked it once and forgot about it. And how does agedu do that? It looks at the atime of the files :) Alexander -- To UNSUBSCRIBE, email to debian-wnpp-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#530660: ITP: agedu -- a Unix utility for tracking down wasted disk space
Alexander Prinsier, le Tue 26 May 2009 20:32:37 +0200, a écrit : Samuel Thibault wrote: Alexander Prinsier, le Tue 26 May 2009 20:21:14 +0200, a écrit : However, that only tells you what's big. What you really want to know is what's too big. By itself, du won't let you distinguish between data that's big because you're doing something that needs it to be big, and data that's big because you unpacked it once and forgot about it. And how does agedu do that? It looks at the atime of the files :) Ok, please mention it in the description, it's not necessarily obvious :) Samuel -- To UNSUBSCRIBE, email to debian-wnpp-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#530660: ITP: agedu -- a Unix utility for tracking down wasted disk space
Samuel Thibault wrote: Alexander Prinsier, le Tue 26 May 2009 20:32:37 +0200, a écrit : Samuel Thibault wrote: Alexander Prinsier, le Tue 26 May 2009 20:21:14 +0200, a écrit : However, that only tells you what's big. What you really want to know is what's too big. By itself, du won't let you distinguish between data that's big because you're doing something that needs it to be big, and data that's big because you unpacked it once and forgot about it. And how does agedu do that? It looks at the atime of the files :) Ok, please mention it in the description, it's not necessarily obvious :) You mean, mention it in the description of the package once it's packaged? Or change the description of this ITP? On the first one, agreed, but I wouldn't know how to do the second one. Alexander -- To UNSUBSCRIBE, email to debian-wnpp-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#530660: ITP: agedu -- a Unix utility for tracking down wasted disk space
Alexander Prinsier, le Tue 26 May 2009 20:21:14 +0200, a écrit : However, that only tells you what's big. What you really want to know is what's too big. By itself, du won't let you distinguish between data that's big because you're doing something that needs it to be big, and data that's big because you unpacked it once and forgot about it. And how does agedu do that? Samuel -- To UNSUBSCRIBE, email to debian-wnpp-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#530660: ITP: agedu -- a Unix utility for tracking down wasted disk space
Alexander Prinsier, le Tue 26 May 2009 20:43:52 +0200, a écrit : Samuel Thibault wrote: Alexander Prinsier, le Tue 26 May 2009 20:32:37 +0200, a écrit : Samuel Thibault wrote: Alexander Prinsier, le Tue 26 May 2009 20:21:14 +0200, a écrit : However, that only tells you what's big. What you really want to know is what's too big. By itself, du won't let you distinguish between data that's big because you're doing something that needs it to be big, and data that's big because you unpacked it once and forgot about it. And how does agedu do that? It looks at the atime of the files :) Ok, please mention it in the description, it's not necessarily obvious :) You mean, mention it in the description of the package once it's packaged? Or change the description of this ITP? The former. -- To UNSUBSCRIBE, email to debian-wnpp-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: tagging as pending bugs that are closed by packages in NEW
Processing commands for cont...@bugs.debian.org: # Tue May 26 20:03:09 UTC 2009 # Tagging as pending bugs that are closed by packages in NEW # http://ftp-master.debian.org/new.html # # Source package in NEW: libticonv tags 503103 + pending Bug#503103: ITP: libticonv -- Texas Instruments calculators charsets library There were no tags set. Tags added: pending # Source package in NEW: libtifiles tags 505818 + pending Bug#505818: ITP: libtifiles2 -- Texas Instruments calculator files library There were no tags set. Tags added: pending # Source package in NEW: libfile-temp-perl tags 530615 + pending Bug#530615: ITP: libfile-temp-perl -- return name and handle of a temporary file safely There were no tags set. Tags added: pending # Source package in NEW: libticables tags 505824 + pending Bug#505824: ITP: libticables2 -- Texas Instruments link cables library There were no tags set. Tags added: pending # Source package in NEW: libticalcs tags 505822 + pending Bug#505822: ITP: libticalcs2 -- provides functions to communicate with TI calculators There were no tags set. Tags added: pending # Source package in NEW: libgtk2-unique-perl tags 530578 + pending Bug#530578: ITP: libgtk2-unique-perl -- Perl module for single instance applications There were no tags set. Tags added: pending # Source package in NEW: libcue tags 529729 + pending Bug#529729: ITP: libcue - CUE Sheet Parser Library There were no tags set. Tags added: pending # Source package in NEW: remuco-server tags 416379 + pending Bug#416379: ITP: remuco -- mobile phone remote music control There were no tags set. Tags added: pending End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to debian-wnpp-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#530666: ITP: imagevis3d -- desktop volume rendering application for large data
Package: wnpp Severity: wishlist Owner: Tom Fogal tempor...@sogetthis.com * Package name: imagevis3d Version : 1.0rc1 Upstream Author : ImageVis3D developers iv3d-us...@sci.utah.edu * URL : http://www.imagevis3d.org/ * License : MIT/X Programming Lang: C++ Description : desktop volume rendering application for large data ImageVis3D is a volume rendering application specifically designed to render large data. This is achieved by splitting the dataset multiple levels of detail (LoD), which each level itself decomposed into multiple bricks (atomic rendering primitive). Interaction occurs at the coarsest LoD, which can be rendered instantaneously on almost all modern systems. After a configurable delay, ImageVis3D will successively render finer levels of detail, until the data are visible at their native resolution. -- System Information: Debian Release: 5.0.1 APT prefers stable APT policy: (500, 'stable') 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
Processed: retitle 446003 to O: xar -- eXtensible ARchiver, bug 446003 has no owner
Processing commands for cont...@bugs.debian.org: retitle 446003 O: xar -- eXtensible ARchiver Bug#446003: ITA: xar -- eXtensible ARchive Changed Bug title to `O: xar -- eXtensible ARchiver' from `ITA: xar -- eXtensible ARchive'. noowner 446003 Bug 446003 [wnpp] O: xar -- eXtensible ARchiver Removed annotation that Bug was owned by Julio Cesar Hernandez Garcia julio...@gmail.com. End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to debian-wnpp-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: retitle 487474 to O: xbl -- 3-D tetris like game, bug 487474 has no owner
Processing commands for cont...@bugs.debian.org: retitle 487474 O: xbl -- 3-D tetris like game Bug#487474: ITA: xbl -- 3-D tetris like game Changed Bug title to `O: xbl -- 3-D tetris like game' from `ITA: xbl -- 3-D tetris like game'. noowner 487474 Bug 487474 [wnpp] O: xbl -- 3-D tetris like game Removed annotation that Bug was owned by Julio Cesar Hernandez Garcia julio...@gmail.com. End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to debian-wnpp-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#530679: ITP: kobby -- Collaborative text editor for KDE
Package: wnpp Severity: wishlist Owner: Ryan Kavanagh ryana...@kubuntu.org * Package name: kobby Version : 1.0b2 Upstream Author : Gregory Haynes g...@greghaynes.net * URL : http://kobby.greghaynes.net * License : GPLv2 or later Programming Lang: C++, Qt Description : Collaborative text editor for KDE Kobby is an editor which allows to edit text documents and source files collaboratively over a network. All users could work on the file simultaneously without the need to lock it. -- System Information: Debian Release: 5.0 APT prefers jaunty-updates APT policy: (500, 'jaunty-updates'), (500, 'jaunty-security'), (500, 'jaunty-backports'), (500, 'jaunty') 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#488679: A recommendation from a friend
Attn: Interested Candidate, My name is Mark Jones, A representative of Smart Concepts Inc, This is an awareness to let the public know that we have a vacant position of a mystery shopper in our company and we would like to know your interest in working for Smart Concepts Inc. As a mystery shopper you work and shop together for pleasure and the pay is between $200 - $400 weekly for part time basis you only work 2-3 hours twice in a week. Kindly provide the Information requested below for assessment and registration by the company, you can contact me by sending me an e-mail to the e-mail address below smart.concept1...@gmail.com or by calling 917-285-9182 or e-mail Full Legal Name, Address, City, State, Zip code and Home and Cell # Thanks Mark Jones. 24 hours by email:
