Bug#188153: Hiya hottie. Would you like to nail me through the night?.,,.,.,. diction
So what do you think? Your profile showed up as just the type Im looking for. Would you like to be my bootey call? So do you think you're interested? Send a message too hardfuck48. http://tama9x.com/dpw/ Rich must leadsman if marksman bryan if nov.-ely9j.com/notonlist/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#256283: [pylucene-dev] Re: PyLucence Debian Package
Hi, I did a little digging. Package gcj-3.4 was removed from Debian Unstable on Aug 14, 2005 because it was Not Built by Source http://ftp-master.debian.org/removals.txt Since gcj is the critical path, this suggests to me that maybe gcj-4.x is the better place to put effort. Andi, do you and OSAF already have all the communication and clout you need with gcj devs? I suppose we could try getting Debian maintainers to lean on upstream a little bit - not that they responded to my initial inquiry. And Ubuntu might also care. On the other hand, gcj is so high profile they may be immune to a little extra persuasion. Are the bugs rocket sciencish, or can a random C programmer like me dive in and help? Any other way we can help? Other possible TODO items: * Swig sounds like it is progressing just fine. * Figure out Java Lucene / Free Software build issues. Barry told me today on IM that he is interested in this, but he is totally swamped. I'm also willing to look, I'm just very slow. FYI, Java Lucene 1.4.3 only builds via a Free Software toolchain in Debian Testing (etch) and Debian Unstable (sid). Debian Stable (sarge) doesn't have a powerful enough free software toolchain for Java. * Andi, think about - eventually - having a future PyLucene source release that is more sourcetastic. For example, maybe include a tarball of the SVN snapshot and a new build target that untars, patches, and rebuilds the .jar files. The precompiled .jar files can still be included. If that's a real pain, then defer because it is not on the critical path. But this or something like it will eventually be helpful, especially since it sounds like the gcj-3.4 package got kicked out of Debian for similar reasons. PyLucene only works with Python 2.4 so to make use of it ensure you are using /usr/bin/python2.4 and not /usr/bin/python. * Mathew, the PyLucene module will not be found if one tries to import it from python 2.3 right? I don't have the PyLucene package in front of me to double check this. http://www.debian.org/doc/packaging-manuals/python-policy/ch-python.html#s-paths * I guess backports.org is still an open question. Anyway, great job on getting this far with the sarge packages. Matthew, you've already made a significant positive difference, and I'm already hearing positive comments. Most recently from a hacker at PARC (my employer) who is actively migrating an internal application called UpLib from Java Lucene towards PyLucene. -Jeff
Bug#351656: [Utnubu-discuss] Bug#351656: RFH: libapache2-mod-annodex -- Provides server-side support for Annodex media
On 2/6/06, Jeff Waugh [EMAIL PROTECTED] wrote: Package: wnpp Severity: normal I've created a mod_annodex package for Ubuntu, and I would love to see it in Debian. Anyone want to lend a hand? :-) deb http://people.ubuntu.com/~jdub/dapper/ ./ deb-src http://people.ubuntu.com/~jdub/dapper/ ./ I would like to review this package and package it for Debian under utnubu group. I'll retitle #351656 and upload it this weekend, if nobody disagree. Thanks, Gustavo Franco -- [EMAIL PROTECTED]
Bug#256283: [pylucene-dev] Re: PyLucence Debian Package
Jeff Breidenbach [EMAIL PROTECTED] said: Hi, I did a little digging. Package gcj-3.4 was removed from Debian Unstable on Aug 14, 2005 because it was Not Built by Source I also did some digging. I found the same removal message and then tracked down a gcj maintainer IRC. He simply said: doko moconnor: we only want to have one gcj version So, that's that. Also, all the gcj-3.4 bugs were reassigned to gcj-4.0. * Swig sounds like it is progressing just fine. I was able to build PyLucene with what will be SWIG 1.3.28. However, PyLucene failed to load. So work is needed there but at least it's not generating bad stuff, that's a plus. PyLucene only works with Python 2.4 so to make use of it ensure you are using /usr/bin/python2.4 and not /usr/bin/python. * Mathew, the PyLucene module will not be found if one tries to import it from python 2.3 right? I don't have the PyLucene package in front of me to double check this. Correct. It goes in /usr/lib/python2.4/site-packages/. I figured this was a fine place b/c it is where python2.4-elementtree puts itself. * I guess backports.org is still an open question. Anyway, great job on getting this far with the sarge packages. Matthew, you've already made a significant positive difference, and I'm already hearing positive comments. Most recently from a hacker at PARC (my employer) who is actively migrating an internal application called UpLib from Java Lucene towards PyLucene. Cool. I submitted the repository to http://www.apt-get.org as well. As asked around and it looks like the backports.org path is as you describe: unstable or testing packages which get backported. -matthew -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#351794: RFP: taxbird -- Client to create and submit your tax declaration to the german ELSTER system
Package: wnpp Severity: wishlist * Package name: taxbird Version : 0.6.0 Upstream Author : Jürgen Stuber [EMAIL PROTECTED], Stefan Siegl [EMAIL PROTECTED] * URL : http://www.taxbird.de/ * License : GPL Description : Client for the German ELSTER system to electronically submit your tax declaration This program helps you to create your tax declaration. When finished it can act as a client to the ELSTER system and submit your forms electronically. Since 2005 you must submit your tax declaration this way in Germany. If you pay your taxes in another country, this software is probably not useful for you. -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable'), (9, 'experimental') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/dash Kernel: Linux 2.6.15-1-k7 Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#351821: RFA: freetype -- FreeType 2 font engine, shared library files
Package: wnpp Severity: normal I request an adopter for the freetype package. Due to a new job I haven't had any time to work on FreeType in the last few months. As such I would like someone to adopt it. A team would probably be best, there's lots of difficult issues with this package and it requires plenty of testing with different fonts and displays. There's a new upstream version likely in the not so distant future. The package description is: The FreeType project is a team of volunteers who develop free, portable and high-quality software solutions for digital typography. They specifically target embedded systems and focus on bringing small, efficient and ubiquitous products. . The FreeType 2 library is their new software font engine. It has been designed to provide the following important features: * A universal and simple API to manage font files * Support for several font formats through loadable modules * High-quality anti-aliasing * High portability performance . Supported font formats include: * TrueType files (.ttf) and collections (.ttc) * Type 1 font files both in ASCII (.pfa) or binary (.pfb) format * Type 1 Multiple Master fonts. The FreeType 2 API also provides routines to manage design instances easily * Type 1 CID-keyed fonts * OpenType/CFF (.otf) fonts * CFF/Type 2 fonts * Adobe CEF fonts (.cef), used to embed fonts in SVG documents with the Adobe SVG viewer plugin. * Windows FNT/FON bitmap fonts . This package contains the files needed to run programs that use the FreeType 2 library. . Home Page: http://www.freetype.org/ Authors: David Turner [EMAIL PROTECTED] Robert Wilhelm [EMAIL PROTECTED] Werner Lemberg [EMAIL PROTECTED] -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.12-1-686 Locale: LANG=en_GB, LC_CTYPE=en_GB (charmap=ISO-8859-1) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#256283: [pylucene-dev] Re: PyLucence Debian Package
On Tue, 7 Feb 2006, Jeff Breidenbach wrote: Hi, I did a little digging. Package gcj-3.4 was removed from Debian Unstable on Aug 14, 2005 because it was Not Built by Source http://ftp-master.debian.org/removals.txt Since gcj is the critical path, this suggests to me that maybe gcj-4.x is the better place to put effort. Andi, do you and OSAF already have all the communication and clout you need with gcj devs? I tried gcj 4.x and have had little luck with it. For the longest time, I wasn't even able to build it. I should try it again... gcj 3.4.x is the safe and stable route for the time being. With the arrival of Intel Macs and no Intel OS X gcj available until probably gcj 4.2, this may change sometime in the next 12 months. As for 'clout' with the gcj devs, well, that word would be inappropriate. I suppose we could try getting Debian maintainers to lean on upstream a little bit - not that they responded to my initial inquiry. And Ubuntu might also care. On the other hand, gcj is so high profile they may be immune to a little extra persuasion. Are the bugs rocket sciencish, or can a random C programmer like me dive in and help? Any other way we can help? Definitely not a random C programmer. gcj is actually at least 3 projects put together, with their own interests and schedules: gcc + classpath + boehm-gc. I've had very little luck in getting any issue resolved, most of them are hard to isolate and reproduce or not on the gcj devs' agenda (static linking, for example). The [EMAIL PROTECTED] mailing list is quite active and very responsive and can be very helpful if you're willing to do most of the work since there is a lot more work than gcj devs can handle. I've had better luck working around issues on my own. * Swig sounds like it is progressing just fine. In a way, it is, but distros are very quick to upgrade to the latest swig in spite of the fact that swig keeps making incompatible changes that make it unlikely for a new swig release to work out of the box for pre-existing software packages. * Andi, think about - eventually - having a future PyLucene source release that is more sourcetastic. For example, maybe include a tarball of the SVN snapshot and a new build target that untars, patches, and rebuilds the .jar files. This is how PyLucene is built from scratch. The source release includes the pre-compiled jars because the audience for PyLucene is Python programmers and I didn't want to impose a JDK requirement on them. GCJ is difficult enough to get right - on the Mac, you have to build gcj yourself since Apple doesn't ship it - adding a JDK requirement on top of it (+ ant) would be gratuitous. The precompiled .jar files can still be included. If that's a real pain, then defer because it is not on the critical path. But this or something like it will eventually be helpful, especially since it sounds like the gcj-3.4 package got kicked out of Debian for similar reasons. I have no problems with making a source-only package, it'd add a java compiler requirement to this exercise. Whichever works best in the world of Debian is fine by me. * Mathew, the PyLucene module will not be found if one tries to import it from python 2.3 right? I don't have the PyLucene package in front of me to double check this. It'll be found if it is in the right place to be found. If PyLucene is built against Python 2.4 headers it may very well crash the process when imported from Python 2.3. Anyway, great job on getting this far with the sarge packages. Matthew, you've already made a significant positive difference, and I'm already hearing positive comments. Most recently from a hacker at PARC (my employer) who is actively migrating an internal application called UpLib from Java Lucene towards PyLucene. Excellent ! Andi.. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#251885: ITP: cgal -- C++ library for computational geometry
Hi Toni, How does upstream release version 3.1 of CGAL, actually fixes these issues? The license of some files was changed such that all files in the Kernel and Support Library are licensed under LGPL, the files in the Basic Library are licensed under QPL. In particlar, all *.C files that end up in libCGAL.so are licensed under LGPL. I don't see any changes in the license since lgpl/qpl dual licensing. Previously, LGPL and QPL licenses were mixed for files in the Kernel and Support Library. This has been changed. BTW, there is no dual licensing, each file is either under LGPL or QPL. Unfortunately, no all license problems were resolved with the 3.1 release. Contrary to the statement in the top-level LICENSE file, there are many files without any copyright notice (and there is no default license clause). 1) Source files in include/CGAL/ and src/. No big deal, the appropriate copyright headers just need to be added. 2) Many, many files in demo/ and examples/ (source as well as images, data, ...) 3) The license situation for the documentation is unclear. Currently, the documentation is not part of the tarball, but there are plans to include the source for the documentation. [Part 3) is a minor problem; if 1) and 2) are solved, one could also remove the documentation from the Debian tarball and point users to the PDF on the CGAL website.] I'm in contact with the CGAL developers. I hope that these license issues are fixed in 3.2 which is scheduled for late spring. Regards, Joachim -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: tagging 284189
Processing commands for [EMAIL PROTECTED]: # Automatically generated email from bts, devscripts version 2.9.11 tags 284189 pending Bug#284189: ITP: xul-runner -- XUL/XPCOM application runner 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 [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#251885: ITP: cgal -- C++ library for computational geometry
On Tue, Feb 07, 2006 at 08:04:40PM +0100, Joachim Reichel wrote:
How does upstream release version 3.1 of CGAL, actually fixes these
issues?
The license of some files was changed such that all files in the Kernel
and Support Library are licensed under LGPL, the files in the Basic
Library are licensed under QPL. In particlar, all *.C files that end up
in libCGAL.so are licensed under LGPL.
ok. I got a different impression at first about the libCGAL.so.
After doing QPL-cleanup:
$ rm `grep -lr LICENSE.QPL .`
Build do fails. There seems to be some debug headers that the core
uses.
Fortunately it is rather easy to fix (either fixing the license of the
debug headers or the use of the debug header with an attached patch).
--
Toni Timonen toni dot timonen at iki dot fi
NP Solutions Ltd
Helsinki University of Technology
Department of Engineering Physics and Mathematicsdiff -rub CGAL-3.1-orig/include/CGAL/Nef_2/Polynomial.h
CGAL-3.1/include/CGAL/Nef_2/Polynomial.h
--- CGAL-3.1-orig/include/CGAL/Nef_2/Polynomial.h 2006-02-07
00:21:27.0 +0200
+++ CGAL-3.1/include/CGAL/Nef_2/Polynomial.h2006-02-07 23:29:44.0
+0200
@@ -35,7 +35,6 @@
#include cstddef
#undef _DEBUG
#define _DEBUG 3
-#include CGAL/Nef_2/debug.h
#include vector
diff -rub CGAL-3.1-orig/src/Polynomial.C CGAL-3.1/src/Polynomial.C
--- CGAL-3.1-orig/src/Polynomial.C 2006-02-07 00:21:26.0 +0200
+++ CGAL-3.1/src/Polynomial.C 2006-02-07 07:27:24.0 +0200
@@ -24,6 +24,9 @@
#include CGAL/Nef_2/Polynomial.h
+#define CGAL_NEF_TRACEN(foo)
+#define CGAL_NEF_TRACEV(foo)
+
namespace CGAL{
signature.asc
Description: Digital signature
Bug#78687: Hi cutestuff. Want to be my fuck buddy?... chronography
How does that sound too you? I checked out your profile and you are just what Im looking for. Will you be the one who fucks me at night? Does that sound like fun too you? Leave me a message at hotfuck83. http://tori5x.com/dpw/ Courtney is southbound or kidnap mine but emerson.-gorifobi.com/notonlist/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#349746: marked as done (ITA(Hijack): synergy -- Share mouse and keyboard over the network)
Your message dated Tue, 07 Feb 2006 15:02:14 -0800 with message-id [EMAIL PROTECTED] and subject line Bug#349746: fixed in synergy 1.2.8-1 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) ---BeginMessage--- Package: wnpp Severity: normal I intend to hijack this package, the current maintainer Daniel Lutz doesn't respond (the second time that he went into MIA), the MIA-Process is triggered. I just made an NMU for xlib-dev-Transition and intend to take over the package completely in february. The package description is: Synergy lets you easily share a single mouse and keyboard between multiple computers with different operating systems, each with its own display, without special hardware. It's intended for users with multiple computers on their desk since each system uses its own display. Cord -- BOFH excuse #231: We had to turn off that service to comply with the CDA Bill. ---End Message--- ---BeginMessage--- Source: synergy Source-Version: 1.2.8-1 We believe that the bug you reported is fixed in the latest version of synergy, which is due to be installed in the Debian FTP archive: synergy_1.2.8-1.diff.gz to pool/main/s/synergy/synergy_1.2.8-1.diff.gz synergy_1.2.8-1.dsc to pool/main/s/synergy/synergy_1.2.8-1.dsc synergy_1.2.8-1_i386.deb to pool/main/s/synergy/synergy_1.2.8-1_i386.deb synergy_1.2.8.orig.tar.gz to pool/main/s/synergy/synergy_1.2.8.orig.tar.gz A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to [EMAIL PROTECTED], and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Cord Beermann [EMAIL PROTECTED] (supplier of updated synergy package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing [EMAIL PROTECTED]) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sat, 4 Feb 2006 22:48:34 +0100 Source: synergy Binary: synergy Architecture: source i386 Version: 1.2.8-1 Distribution: unstable Urgency: low Maintainer: Cord Beermann [EMAIL PROTECTED] Changed-By: Cord Beermann [EMAIL PROTECTED] Description: synergy- Share mouse, keyboard and clipboard over the network Closes: 349746 Changes: synergy (1.2.8-1) unstable; urgency=low . * Hijack the package (closes: #349746) * Rebuild the package from scratch. * moved package from 'net' to 'x11'. Files: cd47f112de236817a02d341c82e774e3 664 x11 optional synergy_1.2.8-1.dsc 7815b1673bd16e0ba155c715428205a5 692068 x11 optional synergy_1.2.8.orig.tar.gz 90191dacd8c3c6057c0a489e6ce40950 30840 x11 optional synergy_1.2.8-1.diff.gz 8eed2acef59e372d1d4f502e9e6d5c40 555712 x11 optional synergy_1.2.8-1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2 (GNU/Linux) iD8DBQFD6SNv72U+jVr0xGIRAl9dAKCBVNef5C53nvt5ylKpLFE0wrtQkgCcCmil IKB7j3ftg3B1X9XM/UPovXc= =fvoe -END PGP SIGNATURE- ---End Message---
Bug#279757: Removed from Debian - unmaintained
I'm taking over full maintenance of FreeWRL. It's the only available VRML browser/plugin for Linux. I already packaged the latest version http://mentors.debian.net/debian/pool/main/f/freewrl/ I'll upload it as soon as I find a sponsor. Stan Vasilyev -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: your mail
Processing commands for [EMAIL PROTECTED]: reopen 279757 Bug#279757: O: freewrl -- VRML browser and netscape plugin Bug reopened, originator not changed. retitle 279757 ITA: freewrl -- VRML browser and netscape plugin Bug#279757: O: freewrl -- VRML browser and netscape plugin Changed Bug title. owner 279757 ! Bug#279757: ITA: freewrl -- VRML browser and netscape plugin Owner recorded as Stan Vasilyev [EMAIL PROTECTED]. thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
