Bug#602034: jpeg8 vs jpeg-turbo
On Thu, Apr 25, 2013 at 6:17 AM, Riku Voipio riku.voi...@iki.fi wrote: On Wed, Apr 24, 2013 at 03:19:59PM +0200, Bill Allombert wrote: As IJG libjpeg maintainer, my plan is to move to libjpeg9 which has more feature. Only the applications that actually want to experiment with libjpeg8/9 ABI should be using it - The 100% of current applications that work just libjpeg-turbo should be using libjpeg-turbo for better performance and compatibility with rest of the linux distributions. Which feature in libjpeg9 does anyone want? The ability to make jpeg's images that nobody else can view? Chicken egg issue, until everyone follow debian and uses libjpeg9, there may be surprise. I do not see libjpeg-turbo as a suitable replacement. It has 1) an different license Be specific, what do you not like about libjpeg-turbo license? As far as I see, it is under the exact same license? 2) much more security issues in a much smaller timeframe. Which translates to.. a single CVE in libjpeg-turbo since it's inception! 3) do not implement the full libjpeg8 ABI, nor the upcoming libjpeg9. This would be a relevant if some application actually used the full libjpeg8 ABI . In fact, 100% of debian works fine with libjpeg-turbo, or even the original libjpeg6b (if the would be recompiled against it again). I find the reason that IJG libjpeg8 fork is so triggerhappy to repeatedly break the API and ABI (and image format!) rather a reason to make libjpeg8 the non-default. You should not deprive debian users from high performance jpeg rendering for a few ABI features that nobody uses - or anyone is asking for. I do not believe in debian life-span, a package manager ever switch an implementation of a package. So libjpeg9 and libjpeg-turbo will have to co-live. I understand your point that libjpeg9 offers experimental feature not needed for everyone, but at least from my point of view libjpeg-turbo by only implementing portion of ITU-T T.81, ISO/IEC IS 10918-1 (namely lossy 8bits progressive sequential) is a no-go for my applications. Have a look at ITK, DCMTK and/or GDCM which provide a patched libjpeg to provide support for lossy 8 12 bits and lossless 16bits. This is a burden to maintain those side implementations. This goes without saying that JPEG commitee is now working on a full implementation of ITU 81: https://github.com/thorfdbg/libjpeg Which also has a different license, may be slower, but *at last* provide a complete implementation of JPEG. It is said to provide an ABI compatible with the original IJG implementation in the near future. So debian may have to provide three JPEG implementations This bug will be really messy to read, but I wished the team from libjpeg-turbo and whoever is running IJG found a compromise to either integrate optimization from -turbo into jpeg9, or the other way around, -turbo provides empty body function for the new API. oh well... -M -- 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/ca+7wuszqjfo+ma94e2s_mkzbjduvmvcg+wsbgzhrfghjb5+...@mail.gmail.com
Bug#673637: marked as done (ITA: tcpflow -- TCP flow recorder)
Your message dated Thu, 25 Apr 2013 09:00:05 + with message-id e1uvi29-0007sb...@franck.debian.org and subject line Bug#673637: fixed in tcpflow 1.3.0+dfsg-1 has caused the Debian Bug report #673637, regarding ITA: tcpflow -- TCP flow recorder 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 this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 673637: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=673637 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: wnpp Severity: normal I intend to orphan the tcpflow package. Note: the upstream author is no longer active, the project was taken over by a new upstream who rewrote the program in C++: https://github.com/simsong/tcpflow/ The package description is: tcpflow is a program that captures data transmitted as part of TCP connections (flows), and stores the data in a way that is convenient for protocol analysis or debugging. A program like 'tcpdump' shows a summary of packets seen on the wire, but usually doesn't store the data that's actually being transmitted. In contrast, tcpflow reconstructs the actual data streams and stores each flow in a separate file for later analysis. . tcpflow understands sequence numbers and will correctly reconstruct data streams regardless of retransmissions or out-of-order delivery. However, it currently does not understand IP fragments; flows containing IP fragments will not be recorded properly. . tcpflow is based on the LBL Packet Capture Library and therefore supports the same rich filtering expressions that programs like 'tcpdump' support. tcpflow can also rebuild flows from data captured with 'tcpdump -w'. ---End Message--- ---BeginMessage--- Source: tcpflow Source-Version: 1.3.0+dfsg-1 We believe that the bug you reported is fixed in the latest version of tcpflow, which is due to be installed in the Debian FTP archive. 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 673...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Dima Kogan d...@secretsauce.net (supplier of updated tcpflow 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 ftpmas...@debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Sat, 02 Feb 2013 02:16:53 -0800 Source: tcpflow Binary: tcpflow tcpflow-dbg Architecture: source amd64 Version: 1.3.0+dfsg-1 Distribution: experimental Urgency: low Maintainer: Dima Kogan d...@secretsauce.net Changed-By: Dima Kogan d...@secretsauce.net Description: tcpflow- TCP flow recorder tcpflow-dbg - TCP flow recorder - debug symbols Closes: 536792 611047 636212 636922 673637 Changes: tcpflow (1.3.0+dfsg-1) experimental; urgency=low . * New Maintainer (Closes: #673637) * Package now follows new upstream: http://www.afflib.org/software/tcpflow/ . This fixes several bugs: (Closes: #636922, #536792, #611047, #636212) * Updated debianization - moved to debhelper v9, so debian/rules is now much simpler - added watch files - expanded debian/copyright - now building a tcpflow-dbg package Checksums-Sha1: 23f888af4ce739cdb20686e22e5aade0baf4e736 1955 tcpflow_1.3.0+dfsg-1.dsc 5e9738da87660cc41b93efe542e0e5948459da5b 128514 tcpflow_1.3.0+dfsg.orig.tar.gz 6d21b5fa979dbef006427d84e5b53733a999bd23 6293 tcpflow_1.3.0+dfsg-1.debian.tar.gz f93f7849e6e4abebd733b3c14942e408ca685f7b 70100 tcpflow_1.3.0+dfsg-1_amd64.deb c148f3efd19778653150580963713f1876ab3211 362688 tcpflow-dbg_1.3.0+dfsg-1_amd64.deb Checksums-Sha256: 8b36a98916101bfee282bd2fbb6a894f7f1fc454152ca32760a69e242ef2b709 1955 tcpflow_1.3.0+dfsg-1.dsc f90749e358755c30f84cc5202cbca1a83019f39ec8141d8d877aa71e479e412f 128514 tcpflow_1.3.0+dfsg.orig.tar.gz bab0649f6e250f163b817cdb18e0c5c2b881598e5f05a3612158557ab22c5e73 6293 tcpflow_1.3.0+dfsg-1.debian.tar.gz ac4e5bbecfe1e01430df44937c50beed93522633d88d19a42599757837c437e7 70100 tcpflow_1.3.0+dfsg-1_amd64.deb 384526676fb73fa4b45e6330e1ece578e702e1627269cfe8e26cc95ebc24340a 362688 tcpflow-dbg_1.3.0+dfsg-1_amd64.deb Files: a3892d07de1da9fb92014b8167595cbd 1955 net optional tcpflow_1.3.0+dfsg-1.dsc 1c34e2693c90d1faf781bd1aa6791266 128514 net optional tcpflow_1.3.0+dfsg.orig.tar.gz 20504a5adf4884519e8e5b78e1eab3e2 6293 net optional tcpflow_1.3.0+dfsg-1.debian.tar.gz 85f2d2b23d309938daaea85d6aa4ac1b 70100 net
Bug#706133: ITP: ompl -- Set of sampling-based motion planning algorithms.
Package: wnpp Severity: wishlist Owner: Leopold Palomo-Avellaneda l...@alaxarxa.net * Package name: ompl Version : 0.12.2 Upstream Author : Ioan A. Șucan, Mark Moll, Lydia E. Kavraki * URL : http://ompl.kavrakilab.org * License : The 3-clause BSD License Programming Lang: (C++, Python) Description : Consists of a set of sampling-based motion planning algorithms. The content of the library is limited to these algorithms, which means there is no environment specification, no collision detection or visualization. The library is designed so it can be easily integrated into systems that provide the additional needed components. -- 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/20130425091452.6013.39653.report...@soho.upc.es
Bug#705972: package qupzilla: bugs ITP 657791 and ITP 705972 have different owners
Hello Mònica, thank you for your scrutiny! Hello Mohamed, thanks to Mònica, I was alerted about your previous ITP over qupzilla some months ago. I made an ITP most recently and uploaded a working package yesterday. Do you want to abandon this package, or would you prefer to co-maintain it? When you decide, we can merge both ITP bugreports and define their owner. Best regards, Georges. Mònica Ramírez Arceda a écrit : Hi, There was already another ITP for qupzilla (#657791), although it's an old one and may be abandoned. Could you contact Mohammed Sameer msam...@foolab.org and ask him/her if he/she wants to abandon or co-maintain this package with you? Once you've done this, you should set the right owner in both bugs and merge them. Thanks for your work! -- Georges KHAZNADAR et Jocelyne FOURNIER 22 rue des mouettes, 59240 Dunkerque France. Téléphone +33 (0)3 28 29 17 70 signature.asc Description: Digital signature
Bug#602034: jpeg8 vs jpeg-turbo
[Mathieu Malaterre] I do not believe in debian life-span, a package manager ever switch an implementation of a package. So libjpeg9 and libjpeg-turbo will have to co-live. It happens. Look at the source for 'libc6'. It used to be glibc, these days it is a fork called eglibc. Likewise the source for the 'ssh' package was once SSH by Tatu Ylonen, these days it is a fork called OpenSSH maintained by some OpenBSD hackers. -- 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/20130425152859.ga4...@p12n.org
Bug#706014: ITP: re-name -- mass rename tool using regular expression
[Joao Eriberto Mota Filho] Re-name [...] is a small and quick tool written in C so it's quicker than most rename tools written in shell scripts. [citation needed] I'm suspicious of this claim for two reasons. - The obvious tool to compare with is 'prename' (mentioned up-thread), which we already ship, and that's not shell but Perl. In terms of efficiency, this may be quite significant, as it uses the rename() system call, whereas a shell implementation would have to fork 'mv' for each file. - In my experience and belief, the efficiency of a mass rename operation is dominated by the filesystem overhead. -- 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/20130425154929.gb4...@p12n.org
Bug#706159: ITP: libzmq-libzmq2-perl -- Perl bindings to the libzmq 2.x library
Package: wnpp Owner: Alessandro Ghedini gh...@debian.org Severity: wishlist X-Debbugs-CC: debian-de...@lists.debian.org,debian-p...@lists.debian.org * Package name: libzmq-libzmq2-perl Version : 1.07 Upstream Author : Daisuke Maki dais...@endeworks.jp * URL : https://metacpan.org/release/ZMQ-LibZMQ2/ * License : Artistic or GPL-1+ Programming Lang: Perl Description : Perl bindings to the libzmq 2.x library ÃMQ is a library which extends the standard socket interfaces with features traditionally provided by specialised messaging middleware products. ÃMQ sockets provide an abstraction of asynchronous message queues, multiple messaging patterns, message filtering (subscriptions), seamless access to multiple transport protocols and more. ZMQ::LibZMQ2 is a thin Perl wrapper around the libzmq 2.x C API. -- 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/debian-wnpp
Bug#706159: ITP: libzmq-libzmq2-perl -- Perl bindings to the libzmq 2.x library
On 25.04.2013 18:01, Alessandro Ghedini wrote: Package: wnpp Owner: Alessandro Ghedini gh...@debian.org Severity: wishlist X-Debbugs-CC: debian-de...@lists.debian.org,debian-p...@lists.debian.org * Package name: libzmq-libzmq2-perl Version : 1.07 Upstream Author : Daisuke Maki dais...@endeworks.jp * URL : https://metacpan.org/release/ZMQ-LibZMQ2/ * License : Artistic or GPL-1+ Programming Lang: Perl Description : Perl bindings to the libzmq 2.x library ØMQ is a library which extends the standard socket interfaces with features traditionally provided by specialised messaging middleware products. ØMQ sockets provide an abstraction of asynchronous message queues, multiple messaging patterns, message filtering (subscriptions), seamless access to multiple transport protocols and more. ZMQ::LibZMQ2 is a thin Perl wrapper around the libzmq 2.x C API. what is the difference to libzeromq-perl that we already have in unstable? -- 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/51795b97.7070...@googlemail.com
Bug#602034: jpeg8 vs jpeg-turbo
On Wed, Apr 24, 2013 at 3:19 PM, Bill Allombert bill.allomb...@math.u-bordeaux1.fr wrote: On Wed, Apr 24, 2013 at 11:23:04AM +0200, Ondřej Surý wrote: Hi Bill and Debian Developers, My proposal is: A. Add libjpeg-turbo to Debian archive (that's easy) B. Add required provides/alternatives for libjpeg62-dev and libjpeg8-dev (where API/ABI match) C. Decide which package should provide default libjpeg-dev library 1. https://bitbucket.org/libgd/gd-libgd/issue/50/tests-jpeg-jpeg_readc-fails-on-debian 2. http://lists.fedoraproject.org/pipermail/devel/2013-January/176299.html 3. http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=602034 As IJG libjpeg maintainer, my plan is to move to libjpeg9 which has more feature. I do not see libjpeg-turbo as a suitable replacement. It has 1) an different license. 2) much more security issues in a much smaller timeframe. 3) do not implement the full libjpeg8 ABI, nor the upcoming libjpeg9. Bill, sorry to barge in, but as a maintainer of the most prominent rev-deps of libjpeg (libgd2 php5-gd), I would like to have some questions answered, and I cannot find the answer neither on http://www.ijg.org/ nor http://www.infai.org/jpeg/. 1. Who is behind IJG? Is it just Guido Vollbeding or there are more people? 2. What's the legal status of IJG? 3. What is the relation of IJG and InfAI (http://www.infai.org/jpeg/)? 4. Is there a (public) bug tracker? 5. Is there a source repository? 6. Is there a mailing list for libjpeg development/users? 7. How do I contribute code to IJG libjpeg? 8. There are new features incorporated to libjpeg? Is that a community process? Or how are the changes driven? IJG (and the features they implement in libjpeg) is independent from jpeg.org (the standards committee). 9. Is there a documentation for new features of libjpeg (DCT, SmartScale), so independent implementations can be done? 10. And what is JPEGClub (http://jpegclub.org/)? (Just found it in the comment rant under: http://blog.kaourantin.net/?p=116) I haven't been able to find answers at IJG or any linked sites, so as you are so far the only one taking stand for IJG jpeg implementation, I would like to to help me to answer those questions. I wouldn't bother to care about libjpeg in Debian, but it's one of the core graphics libraries, and I think we should strive for good compatibility with the rest of the distros, applications and our users. And the 'new features' of libjpeg seems to contradict this. Ondrej -- Ondřej Surý ond...@sury.org -- 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/caljhhg-6u1y0v50zxuzn-2zcgomxy0dg5qb7cqsyc2m1zlz...@mail.gmail.com
Bug#706159: ITP: libzmq-libzmq2-perl -- Perl bindings to the libzmq 2.x library
On gio, apr 25, 2013 at 06:36:39 +0200, Julian Taylor wrote:
On 25.04.2013 18:01, Alessandro Ghedini wrote:
* Package name: libzmq-libzmq2-perl
Version : 1.07
Upstream Author : Daisuke Maki dais...@endeworks.jp
* URL : https://metacpan.org/release/ZMQ-LibZMQ2/
* License : Artistic or GPL-1+
Programming Lang: Perl
Description : Perl bindings to the libzmq 2.x library
[...]
what is the difference to libzeromq-perl that we already have in unstable?
The ZeroMQ module (libzeromq-perl) is deprecated in favour of ZMQ::LibZMQ2
(libzmq-libzmq2-perl), ZMQ::LibZMQ3 and ZMQ. My intention would be to have
libzeromq-perl removed at some point soon (this is why it's not in wheezy, also
see #690680) but it's been taking me a long time (mostly because of a lack of
free time from my part).
Cheers
--
perl -E '$_=q;$/= @{[@_]};and s;\S+;inidehG ordnasselA;eg;say~~reverse'
signature.asc
Description: Digital signature
Bug#502305: ulogd2 packaging effort
Hi all, I've been semi-packaging ulogd-2.x for some time for my own personal use, and after some input from a colleague of mine have been persuaded to tidy up my package and post it to mentors.debian.net. I'm just getting started and setting up my account on the above, but in the meantime my effort can be found at: http://apt.bootc.net/debian/pool/main/u/ulogd2/ulogd2_2.0.2-3.dsc https://github.com/bootc/ulogd2 I'd love to have some comments, positive or negative, about my package. If you'd rather I teamed up with some of the existing efforts, then please do say so too, as I'd be happy to help. Cheers, Chris -- Chris Boot bo...@bootc.net signature.asc Description: OpenPGP digital signature
Bug#706162: ITP: luxio -- Posix bindings for Lua
Package: wnpp Severity: wishlist Owner: Lars Wirzenius l...@liw.fi * Package name: luxio Version : 1.0 Upstream Author : Rob Kendrick rjek+lu...@rjek.com * URL : http://www.rjek.com/software.html * License : MIT (Same as Lua) Programming Lang: Lua Description : Posix bindings for Lua Lightweight UNIX I/O and POSIX binding for Lua 1. Reasonably good coverage of POSIX and BSD Sockets, including IPv6, and some GNU extensions. 2. Meant to be buildable anywhere that is POSIX.1-1996. If it's not, there's a bug. These are likely, as I have nowhere other than Linux to test. 3. Low-level. You get the return values and the errno for the bound functions where possible. Others take a table to fill in, or may return tables. 4. High-level wrapper library providing nice IO access and to misc. utility functions. Generates useful errors in assert()able form, and provides meaningful __tostring metamethods to aid debugging. 5. A high-level poll()-based event dispatch library. 6. Sub-process handling library (read/write io.popen with job control). 7. A prototype POSIX Message Queue-based IPC scheme that can serialise most simple Lua values. (No closures, userdata, etc) This package is needed as a dependency for Gitano, for which an ITP will be filed later. I will be co-maintaining this package with Daniel Silverstone. -- 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/20130425182657.411.13242.report...@havelock.liw.fi
Bug#706014: marked as done (ITP: re-name -- mass rename tool using regular expression)
Your message dated Thu, 25 Apr 2013 15:34:40 -0300 with message-id CAP+dXJeYWJPCNH6a6Z3JukmFfey=29sgkpg_5x5751mh5qx...@mail.gmail.com and subject line Re: ITP: re-name -- mass rename tool using regular expression has caused the Debian Bug report #706014, regarding ITP: re-name -- mass rename tool using regular expression 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 this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 706014: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=706014 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: wnpp Severity: wishlist Owner: Joao Eriberto Mota Filho eribe...@eriberto.pro.br * Package name: re-name Version : 1.99.2 Upstream Author : Andy Xuming xum...@users.sourceforge.net * URL : http://rename.sf.net * License : GPL3 Programming Lang: C Description : mass rename tool using regular expression Re-name (regular expression (re)name) is a tool to rename files. It can change, lowercase and uppercase a batch of files, or modify their ownership. It is a small and quick tool written in C so it's quicker than most rename tools written in shell scripts. . Rename is powered by the extended regular expression for searching and substituting string patterns in the file names. . The main features of rename are: . * Substitue strings in filenames. * Search and substitue strings in filenames by POSIX regular expressions. * Uppercase or lowercase filenames. * Support batch mode rename. * Recursively processing directories and subdirectories. * Support to read the filename list from a file. * Change ownership of files. * Safe mode: test before you go. ---End Message--- ---BeginMessage--- After several discussions on debian-devel and others, I am declining to maintain this package. Thus I am closing the ITP. Thanks a lot to all DDs that sent me suggestions and orientations. Best regards, Eriberto ---End Message---
Bug#602034: jpeg8 vs jpeg-turbo
Hi all, On Do 25 Apr 2013 18:41:40 CEST Ondřej Surý wrote: On Wed, Apr 24, 2013 at 3:19 PM, Bill Allombert bill.allomb...@math.u-bordeaux1.fr wrote: On Wed, Apr 24, 2013 at 11:23:04AM +0200, Ondřej Surý wrote: Hi Bill and Debian Developers, My proposal is: A. Add libjpeg-turbo to Debian archive (that's easy) B. Add required provides/alternatives for libjpeg62-dev and libjpeg8-dev (where API/ABI match) C. Decide which package should provide default libjpeg-dev library 1. https://bitbucket.org/libgd/gd-libgd/issue/50/tests-jpeg-jpeg_readc-fails-on-debian 2. http://lists.fedoraproject.org/pipermail/devel/2013-January/176299.html 3. http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=602034 As IJG libjpeg maintainer, my plan is to move to libjpeg9 which has more feature. I do not see libjpeg-turbo as a suitable replacement. It has 1) an different license. 2) much more security issues in a much smaller timeframe. 3) do not implement the full libjpeg8 ABI, nor the upcoming libjpeg9. Bill, sorry to barge in, but as a maintainer of the most prominent rev-deps of libjpeg (libgd2 php5-gd), I would like to have some questions answered, and I cannot find the answer neither on http://www.ijg.org/ nor http://www.infai.org/jpeg/. 1. Who is behind IJG? Is it just Guido Vollbeding or there are more people? 2. What's the legal status of IJG? 3. What is the relation of IJG and InfAI (http://www.infai.org/jpeg/)? 4. Is there a (public) bug tracker? 5. Is there a source repository? 6. Is there a mailing list for libjpeg development/users? 7. How do I contribute code to IJG libjpeg? 8. There are new features incorporated to libjpeg? Is that a community process? Or how are the changes driven? IJG (and the features they implement in libjpeg) is independent from jpeg.org (the standards committee). 9. Is there a documentation for new features of libjpeg (DCT, SmartScale), so independent implementations can be done? 10. And what is JPEGClub (http://jpegclub.org/)? (Just found it in the comment rant under: http://blog.kaourantin.net/?p=116) All questions are really good questions. Some of them have already been answered in the backlogs of #602034 [1] and the-merged-with bug #612341 [2]. Reading through both of them is probably a good idea for all who are interested in the complete story. Esp. some statements from Guido Vollbeding [3] make me ask myself: hey, what kind of guy is that and what is the stand of the IJG in the free software ecosystem. His arguing tends to be somehow aggressive and inbalanced. One quote that shows what I mean (taken from [3]): It seems that Bill Allombert is still one of the few sane people out there, many others have apparently gone mad. I don't care for the ignorant people. @Bill: Unfortunately, I am not an expert with image processing, but most of what I have read in this thread speaks for re-thinking the current strategy of staying with libjpeg IJG. Can this be a proposal? Package libjpeg and libjpeg-turbo using an alternatives setup and thus, making both libs installable in parallel. Packagers can then build-depend on one or the other libjpeg implementations. Greets, Mike [1] http://bugs.debian.org/602034 [2] http://bugs.debian.org/612341 [3] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=612341#116 -- DAS-NETZWERKTEAM mike gabriel, rothenstein 5, 24214 neudorf-bornstein fon: +49 (1520) 1976 148 GnuPG Key ID 0x25771B31 mail: mike.gabr...@das-netzwerkteam.de, http://das-netzwerkteam.de freeBusy: https://mail.das-netzwerkteam.de/freebusy/m.gabriel%40das-netzwerkteam.de.xfb pgpxbedkwcBYb.pgp Description: Digitale PGP-Unterschrift
Bug#602034: jpeg8 vs jpeg-turbo
Hello, The KDE maintainer in Fedora started an interesting discussion some time ago in Digikam's mailing list. There was input from the very IJG: http://mail.kde.org/pipermail/digikam-devel/2013-January/066206.html It boils down to jpeg6-2 is the only important thing. Forget about jpeg8 and jpeg9, which bring incompatible changes. http://mail.kde.org/pipermail/digikam-devel/2013-January/066256.html FWIW, Arch and Gentoo also follow the policy that jpeg6-2 (and jpeg-turbo with 6-2 API/ABI) is the real deal. On Wed, Apr 24, 2013 at 1:48 PM, Mike Gabriel mike.gabr...@das-netzwerkteam.de wrote: Hi Ondřej, I have just uploaded libjpeg-turbo to Debian and it still hovers in NEW [1]. On Mi 24 Apr 2013 11:23:04 CEST Ondřej Surý wrote: Debian has already open ITP[3] #602034 for libjpeg-turbo, which support libjpeg62 API/ABI and also some important bits of libjpeg8. As libjpeg is one of the base libraries of the system, I think it might be a good idea to discuss this project wide. Also although I have an opinion (as you might have guessed from this email) that we should try to be aligned with other distributions and the reasoning for not going for , I will be happy with whatever result will end-up. In an IRC discussion in #debian-devel several weeks ago the consensus was: the RT team (represented Julien) will probably not want two libjpeg implementations in Debian. My first packaging approach aimed at having the compat mode libraries available [2] and allow the user to install them as a drop-in replacement for libjpeg8. The IRC discussion lead to the result that the compat packages are not wanted in Debian, only the native TURBOjpeg ABI. I was asked to ping Bill Allombert about his opinion to transition from libjpeg8 fully to libjpeg8-turbo. @Bill: can you repeat your disposition here again? I guess our earlier mailing was a private mail exchange. A. Add libjpeg-turbo to Debian archive (that's easy) Done. Waiting in NEW. Only containing libturbojpeg.so.1 B. Add required provides/alternatives for libjpeg62-dev and libjpeg8-dev (where API/ABI match) A packaging example can be seen in [1]. If the packages disappears from the NEW queue, you can also obtain a libjpeg-turbo version with compat packages provided here [3]. C. Decide which package should provide default libjpeg-dev library Last statement from Bill: libjpeg by IJG Greets, Mike [1] http://ftp-master.debian.org/**new/libjpeg-turbo_1.2.90-2.**htmlhttp://ftp-master.debian.org/new/libjpeg-turbo_1.2.90-2.html [2] http://ftp-master.debian.org/**new/libjpeg-turbo_1.2.90-1.**htmlhttp://ftp-master.debian.org/new/libjpeg-turbo_1.2.90-1.html [3] http://packages.x2go.org/**debian/pool/main/libj/libjpeg-**turbo/http://packages.x2go.org/debian/pool/main/libj/libjpeg-turbo/ -- DAS-NETZWERKTEAM mike gabriel, rothenstein 5, 24214 neudorf-bornstein fon: +49 (1520) 1976 148 GnuPG Key ID 0x25771B31 mail: mike.gabriel@das-netzwerkteam.**demike.gabr...@das-netzwerkteam.de, http://das-netzwerkteam.de freeBusy: https://mail.das-netzwerkteam.**de/freebusy/m.gabriel%40das-** netzwerkteam.de.xfbhttps://mail.das-netzwerkteam.de/freebusy/m.gabriel%40das-netzwerkteam.de.xfb -- Pau Garcia i Quiles http://www.elpauer.org (Due to my workload, I may need 10 days to answer)
Processed: tagging as pending bugs that are closed by packages in NEW
Processing commands for cont...@bugs.debian.org: # Thursday 25 April 20:03:08 UTC 2013 # Tagging as pending bugs that are closed by packages in NEW # http://ftp-master.debian.org/new.html # # Source package in NEW: corekeeper tags 602946 + pending Bug #602946 [corekeeper] corekeeper: Fails to start/configure/install on kfreebsd Warning: Unknown package 'corekeeper' Added tag(s) pending. Warning: Unknown package 'corekeeper' # Source package in NEW: corekeeper tags 603360 + pending Bug #603360 [corekeeper] cronjob produces output after package removal Warning: Unknown package 'corekeeper' Added tag(s) pending. Warning: Unknown package 'corekeeper' # Source package in NEW: corekeeper tags 695901 + pending Bug #695901 [wnpp] ITP: corekeeper -- Core file centralizer and reaper Bug #695896 [wnpp] ITP: corekeeper -- Core file centralizer and reaper Bug #695897 [wnpp] ITP: corekeeper -- Core file centralizer and reaper Added tag(s) pending. Added tag(s) pending. Added tag(s) pending. # Source package in NEW: libzmq-libzmq2-perl tags 706159 + pending Bug #706159 [wnpp] ITP: libzmq-libzmq2-perl -- Perl bindings to the libzmq 2.x library Added tag(s) pending. End of message, stopping processing here. Please contact me if you need assistance. -- 602946: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=602946 603360: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=603360 695896: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=695896 695897: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=695897 695901: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=695901 706159: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=706159 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- 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/handler.s.c.13669202047896.transcr...@bugs.debian.org
Bug#706179: ITP: r-cran-rsclient -- R client for the headless Rserve R server
Package: wnpp Owner: Dirk Eddelbuettel e...@debian.org Severity: wishlist * Package name: r-cran-rsclient Version : 0.7-2 Upstream Author : Simon Urbanek * URL or Web page : http://www.rforge.net/RSclient/index.html * License : GPL-2 plus OpenSSL exception Description : R client for the headless Rserve R server This package extend the 'rserve' package we have had in Debian since 2007. 'rserve' already includes several reference clients, but this package provides a more extensive version. The package uses OpenSSL, and at my urging, Simon added the following to his top-level LICENSE file: [Summary: GPL-2 with OpenSSL linking exception] RSclient Copyright (C) 2002-2013 Simon Urbanek This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; version 2 of the License. This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details. You should have received a copy of the GNU General Public License along with this program; if not, write to the Free Software Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA. In addition, as a special exception, the copyright holders give permission to link the code of portions of this program with the OpenSSL project's OpenSSL library (or with modified versions of it that use the same license as the OpenSSL library - see http://www.openssl.org/), and distribute linked combinations including the two. You must obey the GNU General Public License in all respects for all of the code used other than OpenSSL. If you modify file(s) with this exception, you may extend this exception to your version of the file(s), but you are not obligated to do so. If you do not wish to do so, delete this exception statement from your version. If you delete this exception statement from all source files in the program, then also delete it here. which is followed by a full copy of the GPL-2. I believe that this meets our standards. Dirk -- Dirk Eddelbuettel | e...@debian.org | http://dirk.eddelbuettel.com -- 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/87zjwmxpkb@max.nulle.part
Bug#706180: ITP: node-once -- Run a function only once with this module for Node.js
Package: wnpp Severity: wishlist Owner: Jérémy Lal kapo...@melix.org * Package name: node-once Version : 1.1.1 Upstream Author : Isaac Z. Schlueter i...@izs.me * URL : https://github.com/isaacs/once * License : BSD-2-clause Programming Lang: JavaScript Description : Run a function only once with this module for Node.js node-once is useful to make sure a listener for multiple events is only run once. . Node.js is an event-based server-side javascript engine. -- 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/20130425215929.19037.25318.reportbug@imac.chaumes
Bug#706078: ITP: base91 -- base91 encoder/decoder
On Wed, Apr 24, 2013 at 03:40:57PM +0200, Franck wrote: basE91 is an advanced method for encoding binary data as ASCII characters. It is similar to UUencode or base64, but is more efficient. The overhead produced by basE91 depends on the input data. It amounts at most to 23% (versus 33% for base64) and can range down to 14%, which typically occurs on 0-byte blocks. This makes basE91 very useful for transferring larger files over binary insecure connections like e-mail or terminal lines. That word should be safety, not security. Safety here means the message does not get mangled, security on the other hand would mean things like encryption. -- 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/20130425214222.gb8...@amos.fritz.box
Bug#706184: ITP: freedv -- Digital Voice for HF
Package: wnpp Severity: wishlist Owner: A. Maitland Bottoms bott...@debian.org * Package name: freedv Version : 0.96r1235 Upstream Author : David Rowe VK5DGR da...@rowetel.com, Dave Witten witt...@wwrinc.com * URL : http://freedv.org * License : LGPL-2.1 Programming Lang: C++ Description : Digital Voice for HF FreeDV is a GUI application that allows any SSB radio to be used for low bit rate digital voice. Speech is compressed down to 1400 bit/s then modulated onto a 1100 Hz wide QPSK signal which is sent to the Mic input of a SSB radio. On receive, the signal is received by the SSB radio, then demodulated and decoded by FreeDV. FreeDV was built by an international team of Radio Amateurs working together on coding, design, user interface and testing. FreeDV is open source software, released under the GNU Public License version 2.1. The FDMDV modem and Codec 2 Speech codec used in FreeDV are also open source. Why FreeDV? Amateur Radio is transitioning from analog to digital, much as it transitioned from AM to SSB in the 1950's and 1960's. How would you feel if one or two companies owned the patents for SSB, then forced you to use their technology, made it illegal to experiment with or even understand the technology, and insisted you stay locked to it for the next 100 years? That's exactly what was happening with digital voice. But now, hams are in control of their technology again! FreeDV is unique as it uses 100% Open Source Software, including the audio codec. No secrets, nothing proprietary! FreeDV represents a path for 21st century Amateur Radio where Hams are free to experiment and innovate, rather than a future locked into a single manufacturers closed technology. I've been builing packages while trying to keep up with active development, and it is time for better availability of packaged versions to facilitate testing by early adopters. Expect the initial series of uploads to go into Debian experimental. The Lintian warning count is low, but the upstream developers expect some incompatible protocol changes between versions for the near future. -Maitland -- 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/20857.51522.980372.606...@airborne.nrl.navy.mil
Bug#705339: RFP: python-pyephem -- scientific-grade astronomical computations for Python
Hello Paul, [CCing Andreas to get his opinion] On Saturday 13 April 2013 18:13:36 you wrote: I would like to schedule some cron jobs relative to the time of sunset and sunrise at my current location, having this package in Debian would allow me to do that. I will package it! I want to do something similar to you. :) I have only one doubt: I'm a member of the DPMT, but this package maybe is more suitable under the umbrella of the Debian Science Team. If it's so, I will be happy to join the Debian Science Team and maintain python-pyephem under the umbrella of Debian Science Team. Andreas what do you suggest? Kind regards, -- Daniele Tricoli 'Eriol' http://mornie.org signature.asc Description: This is a digitally signed message part.
