Bug#787953: depends on obsolete libasm2-java library

2015-10-09 Thread Markus Koschany
Hello,

FTR: As already noted in the initial bug report, substance and its
dependency liblaf-widget-java are unmaintained. Last version was
released in 2010.

https://java.net/projects/substance

Last Github snapshot:

https://github.com/kirillcool/substance

substance was forked into insubstantial:

https://github.com/Insubstantial/insubstantial

and Felix Natter (CCed) intended to maintain it for Debian (#787953).

Unfortunately insubstantial is also unmaintained now and still depends
on asm2.

I think it only makes sense to replace substance and its libraries with
insubstantial when upstream development continues and asm2 is replaced
with a newer, Java 7+ compatible version.

I am going to file bug reports against Jajuk and bgfinancas which depend
on substance and ask that they either move away from substance or take
over maintenance.

I have opened an upstream bug report for Jajuk already:

https://github.com/jajuk-team/jajuk/issues/1994


Regards,

Markus



signature.asc
Description: OpenPGP digital signature


Bug#784986: Ubuntu package

2015-10-09 Thread Pietro Battiston
Just for the records, there is an Ubuntu package:
https://launchpad.net/~alessandro-strada/+archive/ubuntu/ppa
which I am using succesfully under Debian testing, and which might be a
starting point for a Debian package.

Pietro



Bug#799759: Bug#778650: freerdp-x11: Alt key gets "stuck" with -grab-keyboard option when using Alt-Tab to switch between local X windows

2015-10-09 Thread Mike Gabriel

Hi Petr,

On  Fr 09 Okt 2015 07:53:23 CEST, Petr Vorel wrote:


Hi Petr,




Thanks for preparing this patch. I had filed a request for help bug [1]
recently and Bernhard from upstream and Sriram will support maintenance of
freerdp in Debian.



As it seems that you have some hacking skills around freerdp, mayby you are
interested in supporting maintenance, as well.



We hang out on IRC channel #freerdp on Freenode, if you are interested in
continuously working on freerdp in Debian.



Sriram is currently going through all open issues in Debian's current
freerdp version as found in unstable (so we can push them to jessie, as
well), whereas Bernhard is working on the upstream side on prepping a major
upstream release 2.0 which we will then push to Debian experimental.



Greets,
Mike



[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=799759


Hi Mike,

great news there are some work to be done on Debian freerdp :-). I  
suppose you're also

going to address RC bug #785898 [2].

Unfortunately I don't know freerdp. I just spent some time with this  
bug as it annoyed me
enough and wanted to help fix it. And this bug also affects krdc  
(which uses /usr/bin/xfreerdp as RDP backend).


Thanks a lot for you offer to join packaging team. I might be  
interested on RC bugs,
unless anybody else is working on them as I rely on this package.   
But with very limited
time I can give to Debian in next months it wouldn't be responsible  
to make promis I'd be

continuously working on freerdp in Debian.

Kind regards,
Petr

[2] https://bugs.debian.org/785898


No problem at all. I thought, I'd just ask if you are interested.  
Thanks for that patch anyway, we will handle inclusion in Debian's  
freerdp and upstreaming.


Mike
--

DAS-NETZWERKTEAM
mike gabriel, herweg 7, 24357 fleckeby
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


pgpwE2BQsWr7f.pgp
Description: Digitale PGP-Signatur


Processed: reassign 738883 to ftp.debian.org ...

2015-10-09 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> reassign 738883 ftp.debian.org
Bug #738883 [wnpp] O: scribble -- Popular crossword game, similar to Scrabble(R)
Bug reassigned from package 'wnpp' to 'ftp.debian.org'.
Ignoring request to alter found versions of bug #738883 to the same values 
previously set
Ignoring request to alter fixed versions of bug #738883 to the same values 
previously set
> retitle 738883 RM: scribble -- RoQA: Unmaintained for a year, (will become) 
> RC buggy
Bug #738883 [ftp.debian.org] O: scribble -- Popular crossword game, similar to 
Scrabble(R)
Changed Bug title to 'RM: scribble -- RoQA: Unmaintained for a year, (will 
become) RC buggy' from 'O: scribble -- Popular crossword game, similar to 
Scrabble(R)'
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
738883: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=738883
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems



Bug#801366: ITP: notebook -- Jupyter interactive notebook

2015-10-09 Thread Julien Puydt

Package: wnpp
Owner: Julien Puydt 
Severity: wishlist
X-Debbugs-CC: debian-pyt...@lists.debian.org

* Package name: notebook
  Version : 4.0.5
  Upstream Author : Jupyter Development Team
* URL : https://github.com/jupyter/notebook
* License : BSD-3-clause
  Programming Lang: Python
  Description : Jupyter interactive notebook
 The Jupyter HTML notebook is a web-based notebook environment
 for interactive computing.

Snark on #debian-python



Bug#714973: google-drive-ocamlfuse

2015-10-09 Thread Pietro Battiston
Notice the RFP for the better maintained google-drive-ocamlfuse:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=784986

Pietro



Bug#801417: ITP: whichcraft -- cross-platform cross-python shutil.which functionality

2015-10-09 Thread Vincent Bernat
Package: wnpp
Severity: wishlist
Owner: Vincent Bernat 

* Package name: whichcraft
  Version : 0.1.1
  Upstream Author : Daniel Roy Greenfeld 
* URL : https://github.com/pydanny/whichcraft
* License : BSD
  Programming Lang: Python
  Description : cross-platform cross-python shutil.which functionality

Binary package names: python3-whichcraft python-whichcraft



Bug#787953: depends on obsolete libasm2-java library

2015-10-09 Thread Felix Natter
Markus Koschany  writes:

> Hi!

hello Markus,

> Am 09.10.2015 um 21:01 schrieb Felix Natter:
>> Markus Koschany  writes:
> [...]
>>> Unfortunately insubstantial is also unmaintained now and still depends
>>> on asm2.
>>>
>>> I think it only makes sense to replace substance and its libraries with
>>> insubstantial when upstream development continues and asm2 is replaced
>>> with a newer, Java 7+ compatible version.
>> 
>> Are you sure? I was able to build insubstantial (7.3) with asm2 and used
>> the resulting package in the r-deps jajuk/bgfinancas/triplea[2]/freeplane)
>> where it worked fine.
>
> My concerns are not about building insubstantial with asm2. That works.
> I query whether it makes sense to switch from one unmaintained project
> (substance, liblaf-widget-java, trident, etc) to another one
> (insubstantial).
>
> http://speling.shemnon.com/blog/2013/06/08/insubstantial-needs-a-new-maintainer/

I think it does, see below.

> If you really intend to maintain insubstantial you should be prepared to
> do development work as bug fixing or switching from asm2 to asm5 too.
> Otherwise we and you invest a lot of time for a switch but without a
> significant gain.

The significant gain is that we don't have to rewrite large parts of
freeplane 1.4 and triplea 1.8.

>> [2] triplea 1.8 will require insubstantial (7.3):
>> http://sourceforge.net/p/triplea/code/HEAD/tree/trunk/triplea/changelog.txt
>
> The Debian package of triplea currently recommends substance and I think
> this will remain when 1.8 is packaged. Making a LAF-theme optional is
> one of the solutions I can think of.

It's certainly easier to use insubstantial than to patch freeplane-1.4
and triplea-1.8.

>> A quick search in the history (http://asm.ow2.org/history.html) did not
>> reveal anything.  They claim that ASM4 will "full[y] support of Java 7"
>> and ASM5 will "Full[y] support of Java 8" but does that really mean that
>> it does not work with java7/java8?
>> 
>> But reading #801322/#801323, I guess you argue that libasm2 must be
>> removed from the archive.
>
> Careful. asm2 was released ten years ago and is currently packaged in
> libasm2-java. The latest version of asm is packaged in libasm4-java
> (actually asm5). I have only filed those bug reports because I would
> like to see modern packages use the latest version of asm and not
> something from the last decade. So libasm4-java is fully supported
> upstream. I just care and want to clean up a little and to remove (very)
> old packages. Maintaining several versions of the same library in Debian
> should be the exception, even for Java.
>
>>> I am going to file bug reports against Jajuk and bgfinancas which depend
>>> on substance and ask that they either move away from substance or take
>>> over maintenance.
>> 
>> Moving away from flamingo/substance/trident is _a lot_ of work. For
>> freeplane this would mean rewriting the user interface (ribbons).
>> The jajuk maintainers tell similar things [3]
>> (though it's easier for jajuk because they "only" use substance L)
>> 
>> [3] https://github.com/jajuk-team/jajuk/issues/1994
>
> I have to further discuss this with the upstream developer of Jajuk but
> he indicated that he could be willing to switch to Nimbus as the default
> theme. He might also be interested in helping you to port insubstantial
> to asm5 (libasm4-java). I will ask him.

+1 for porting, thanks!

Please also tell him/her that I have patches for converting jajuk to
insubstantial 7.3:
  
https://github.com/fnatter/insubstantial-debian/blob/rdeps/rdeps/jajuk/05_insubstantial_7.3.diff
  
https://github.com/fnatter/insubstantial-debian/blob/rdeps/rdeps/jajuk/MANIFEST.MF.diff

>>> I have opened an upstream bug report for Jajuk already:
>>>
>>> https://github.com/jajuk-team/jajuk/issues/1994
>> 
>> How about trying to add a Debian patch to make insubstantial (7.3) build
>> with asm4 (if that is necessary)? Shall I look into it?
>
> That would be definitely one of the preferred options to solve this issue.
>
> I see the following option:
>
> 1. Go ahead and package insubstantial as one source package that
> provides the old binary packages from substance, trident,
> liblaf-widget-java, etc. Maven poms should be provided as well. If you
> also provide a patch to build with libasm4-java we could easily replace
> the old dependencies for jajuk, bgfinancas, triplea and freeplane with
> your new version and remove libasm2-java from Debian. (only
> jasperreports would be an open issue but I would invest the time to fix
> this package myself)

Agreed, I will work on providing poms. Two questions:

- can you think of a role model package for installing maven artifacts?

- Do I have to generate poms via gradle or shall/can I use+modify the
  ones from maven.org?
  
(http://search.maven.org/#artifactdetails|com.github.insubstantial|flamingo|7.3|jar)

> Win-Win situation
>
> 2. Make substance an optional theme and use Nimbus or other standard 

Bug#801414: ITP: world -- WORLD is a high-quality speech analysis/synthesis system on the basis of Vocoder.

2015-10-09 Thread Tobias Platen

Package: wnpp
Owner: Tobias Platen 
Severity: wishlist

* Package name : world
  Version : 0.2.0_4
  Upstream Author : Masanori Morise
  Programming Lang: C++
  Description : WORLD is a high-quality speech analysis/synthesis 
system on the basis of Vocoder.


WORLD was proposed to synthesize high-quality speech as natural as the 
input speech. The purpose of WORLD is reducing the computational cost of 
TANDEM-STRAIGHT without deterioration. WORLD is superior to 
TANDEM-STRAIGHT in implementing the real-time singing synthesis, whereas 
it is inferior to TANDEM-STRAIGHT in manipulating consonant flexibly. 
Since the concept of WORLD differs from that of TANDEM-STRAIGHT, you 
should select them based on your purpose.


I'm using WORLD to build a free software replacement for both 
MBROLA(multilingual speech synthesizer) and VOCALOID/UTAU(Japanese 
singing synthesizer). I've found Paul Liu as a sponsor/maintainer and I 
ask the Debian Debian-Accessibility team for co-mainantainers.
The dsc is at 
http://mentors.debian.net/debian/pool/main/w/world/world_0.2.0~dfsg4-retry2.dsc


Tobias Platen


--
Sent from my Libreboot X200



Bug#801418: ITP: pytest-mock -- thin-wrapper around the mock package for easier use with py.test

2015-10-09 Thread Vincent Bernat
Package: wnpp
Severity: wishlist
Owner: Vincent Bernat 

* Package name: pytest-mock
  Version : 0.8.1
  Upstream Author : Bruno Oliveira 
* URL : https://github.com/pytest-dev/pytest-mock/
* License : LGPL-3
  Programming Lang: Python
  Description : thin-wrapper around the mock package for easier use with 
py.test

Binary package names: python3-pytest-mock python-pytest-mock

 This plugin installs a ``mocker`` fixture which is a thin-wrapper around the 
patching API
 provided by the excellent `mock `_ package,
 but with the benefit of not having to worry about undoing patches at the end
 of a test.



Bug#787953: depends on obsolete libasm2-java library

2015-10-09 Thread Markus Koschany
Hi Felix,

Am 09.10.2015 um 23:19 schrieb Felix Natter:
> Markus Koschany  writes:
[...]
> 
> Please also tell him/her that I have patches for converting jajuk to
> insubstantial 7.3:
>   
> https://github.com/fnatter/insubstantial-debian/blob/rdeps/rdeps/jajuk/05_insubstantial_7.3.diff
>   
> https://github.com/fnatter/insubstantial-debian/blob/rdeps/rdeps/jajuk/MANIFEST.MF.diff

I just did:

https://github.com/jajuk-team/jajuk/issues/1994

[...]
>>
>> 1. Go ahead and package insubstantial as one source package that
>> provides the old binary packages from substance, trident,
>> liblaf-widget-java, etc. Maven poms should be provided as well. If you
>> also provide a patch to build with libasm4-java we could easily replace
>> the old dependencies for jajuk, bgfinancas, triplea and freeplane with
>> your new version and remove libasm2-java from Debian. (only
>> jasperreports would be an open issue but I would invest the time to fix
>> this package myself)
> 
> Agreed, I will work on providing poms. Two questions:
> 
> - can you think of a role model package for installing maven artifacts?
> 
> - Do I have to generate poms via gradle or shall/can I use+modify the
>   ones from maven.org?
>   
> (http://search.maven.org/#artifactdetails|com.github.insubstantial|flamingo|7.3|jar)

You can usually reuse the poms from maven.org. You can either use
javahelper + jh_maven_repo_helper

https://packages.qa.debian.org/libj/libjide-oss-java.html

or you can also depend on maven-debian-helper in addition to your normal
build system and install them too.

I think we figure that out as soon insubstantial is ported to
libasm4-java. Just ask on debian-java for a review.

Cheers,

Markus






signature.asc
Description: OpenPGP digital signature


Bug#801420: ITP: mbedtls -- lightweight crypto and SSL/TLS library

2015-10-09 Thread James Cowgill
Package: wnpp
Owner: James Cowgill 
Severity: wishlist
X-Debbugs-CC: debian-de...@lists.debian.org

* Package name: mbedtls
  Version : 2.1.2
  Upstream Author : ARM Limited
* URL : http://tls.mbed.org/
* License : Apache-2.0 or GPL-2+
  Programming Lang: C
  Description : lightweight crypto and SSL/TLS library

mbed TLS (formerly known as PolarSSL) is a lean open source crypto library for
 providing SSL and TLS support in your programs. It offers an intuitive API and
 documented header files, so you can actually understand what the code does.
 It features:
  - Symmetric algorithms, like AES, Blowfish, Triple-DES, DES, ARC4, Camellia
and XTEA
  - Hash algorithms, like SHA-1, SHA-2, RIPEMD-160 and MD5
  - Entropy pool and random generators, like CTR-DRBG and HMAC-DRBG
  - Public key algorithms, like RSA, Elliptic Curves, Diffie-Hellman, ECDSA
and ECDH
  - TLS 1.0, 1.1 and 1.2
  - Abstraction layers for ciphers, hashes, public key operations, platform
abstraction and threading

Around a year ago control of PolarSSL was passed to ARM and the project
was later rebranded as mbed TLS. Version 2 made large changes to the
API (including renaming all the functions, include paths, etc) so it
makes sense to me to create an entirely separate source package. Due to
the number of API changes, even the -dev package does not conflict with
libpolarssl-dev.

signature.asc
Description: This is a digitally signed message part


Bug#801253: O: wicd -- wired and wireless network manager

2015-10-09 Thread Michael Lustfield
This is something I use heavily and it's found a nice little place in my
heart. If you'd be willing to help make sure I don't screw up, I'd be
interested in doing packing work for wicd.
On Oct 7, 2015 1:30 PM, "Axel Beckert"  wrote:

> Package: wnpp
> Severity: normal
>
> Hi,
>
> TL;DR: wicd is a lightweight alternative to GNOME's Network Manager.
> It is written in Python and offers commandline, curses and GTK user
> interfaces.
>
> David Paleino (Cc'ed), original developer and current Debian package
> maintainer of wicd stated multiple times[1][2] that he has no more
> time to work on wicd.
>
> Upstream development already has been passed[1] over to new
> developers. I asked in that thread if the new upstream developers
> would also take over the packaging of wicd for Debian, but it has been
> unanswered for more than one year now, though.
>
> wicd has seen two NMUs[3][4] in the past, both related to python-urwid
> API changes.
>
> According to Gianfranco (Cc'ed), David said that "he would avoid
> seeing the package die"[2]. And since the package received two NMUs
> since the last maintainer upload in 2012, I think it's the best to
> declare it as orphaned so that it's clear that someone who's
> interested can take over the package.
>
> There's already some work done on the package at [5]. Any future
> maintainer should base on that work.
>
> I'd be available for sponsoring wicd as I've done the first NMU and
> sponsored the second. I may also join a dedicated team in case wicd
> will be team-maintained in the future. That team would just need a
> more python-savvy lead than me.
>
> [1] https://answers.launchpad.net/wicd/+question/227789
> [2] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=800693#71
> [3] https://packages.qa.debian.org/w/wicd/news/20130609T173413Z.html
> [4] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=800693#56
> [5] https://anonscm.debian.org/cgit/collab-maint/wicd.git
>
> Some more details about the source and binary packages:
>
> Source: wicd
> Section: net
> Priority: optional
> Build-Depends:
>  debhelper (>= 7.2.3~)
>  , python (>= 2.6.6-3~)
> Build-Depends-Indep:
>  po-debconf
>  , python-babel
>  , gettext
> Standards-Version: 3.9.6
> Homepage: https://launchpad.net/wicd
> Vcs-Browser: https://anonscm.debian.org/cgit/collab-maint/wicd.git
> Vcs-Git: git://anonscm.debian.org/collab-maint/wicd.git
>
> Package: wicd
> Architecture: all
> Depends: ${misc:Depends}
>  , wicd-daemon (= ${source:Version})
>  , wicd-gtk (= ${source:Version}) | wicd-curses (= ${source:Version})
>  | wicd-cli (= ${source:Version}) | wicd-client
> Description: wired and wireless network manager - metapackage
>  Wicd is a general-purpose network configuration server which aims
>  to provide a simple but flexible interface for connecting to networks.
>  Its features include:
>   * wide variety of settings;
>   * ability to connect to (and maintain profiles for) both wired and
> wireless networks;
>   * support for many encryption schemes, including WEP, WPA, WPA2 and
> custom schemes;
>   * wireless-tools compatibility;
>   * tray icon showing network activity and signal strength;
>   * lack of GNOME dependencies (although it does require GTK+), making it
> easy to use in Xfce, Fluxbox, Openbox, Enlightenment, etc.
>  .
>  This is a metapackage, it allows installation of all the components of
>  Wicd, including one of the clients, which must be manually chosen.
>
> Package: wicd-daemon
> Architecture: all
> Depends:
>  ${misc:Depends}
>  , ${python:Depends}
>  , python-dbus
>  , python-gobject
>  , dbus
>  , wpasupplicant
>  , wireless-tools
>  , dhcpcd | isc-dhcp-client | pump | udhcpc
>  , net-tools | ethtool
>  , net-tools | iproute2
>  , adduser
>  , lsb-base (>= 3.2-13)
>  , psmisc
>  , iputils-ping | inetutils-ping
>  , python-wicd (= ${source:Version})
> Pre-Depends: debconf (>= 1.5.34)
> Recommends: wicd-gtk (= ${source:Version}) | wicd-curses (=
> ${source:Version}) | wicd-cli (= ${source:Version}) | wicd-client
>  , rfkill
> Suggests: pm-utils
> Breaks: wicd (<= 1.6.2.2-4)
> Replaces: wicd (<= 1.6.2.2-4)
> Description: wired and wireless network manager - daemon
>  Wicd is a general-purpose network configuration server which aims
>  to provide a simple but flexible interface for connecting to networks.
>  Its features include:
>   * wide variety of settings;
>   * ability to connect to (and maintain profiles for) both wired and
> wireless networks;
>   * support for many encryption schemes, including WEP, WPA, WPA2 and
> custom schemes;
>   * wireless-tools compatibility.
>  .
>  This package contains the daemon needed to run Wicd.
>
> Package: wicd-gtk
> Architecture: all
> Depends:
>  ${misc:Depends}
>  , ${python:Depends}
>  , python-gtk2
>  , python-glade2
>  , wicd-daemon (= ${source:Version})
> Recommends:
>  gksu
>  , python-notify
> Provides: wicd-client
> Breaks: wicd (<= 1.6.2.2-4)
> Replaces: wicd (<= 1.6.2.2-4)
> Description: wired and 

Bug#801397: marked as done (ITP: tuptime -- Report historical and statistical running time of the system, keeping it between restarts.)

2015-10-09 Thread Debian Bug Tracking System
Your message dated Fri, 09 Oct 2015 16:20:16 +
with message-id 
and subject line closing ITP: tuptime -- Report historical and statistical 
running time of the system, keeping it between restarts.
has caused the Debian Bug report #801397,
regarding ITP: tuptime -- Report historical and statistical running time of the 
system, keeping it between restarts.
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.)


-- 
801397: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=801397
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: wnpp
Severity: wishlist
Owner: Ricardo F 

* Package name: tuptime
  Version : 3.2.01
  Upstream Author : Name 
* URL : https://github.com/rfrail3/tuptime
* License : GPL
  Programming Lang: Python
  Description : Report historical and statistical running time of the 
system, keeping it between restarts.


Tuptime is a tool for report the historical and statistical running time of the 
system, keeping it between restarts. Indeed, it can:

  - Count system startups
  - Register first boot time (a.k.a. installation time)
  - Count nicely and accidentally shutdowns
  - Uptime and downtime percentage since first boot time
  - Accumulated system uptime, downtime and total
  - Largest, shortest and average uptime and downtime
  - Current uptime
  - Print formatted table or list with most of the previous values
  - Register used kernels
--- End Message ---
--- Begin Message ---
Please retitle bug 638422 from RFP to ITP and set yourself as the owner.--- End Message ---


Bug#516183: RFP: python-django-cms -- hierarchical Django content management system app

2015-10-09 Thread W. Martin Borgert

Hi, is anybody still working on this?
Upstream is now on github, it seems:
https://github.com/divio/django-cms



Bug#801062: Your mail

2015-10-09 Thread James Cowgill
Control: forcemerge -1 801063
Control: retitle -1 ITP: world -- high-quality speech analysis/synthesis system 
on the basis of Vocoder.

On Mon, 05 Oct 2015 21:39:35 +0200 Tobias Platen  
wrote:
> Package: wnpp
> Severity: wishlist
> Owner: Tobias Platen 
> 
> * Package name: world

Hi Tobias,

I have adjusted the title of this bug for you and merged it with the
other identical bug you filed (assuming this is what you meant).

Email 801...@bugs.debian.org if you want to add any extra comments to
the bug.

Thanks,
James

signature.asc
Description: This is a digitally signed message part


Processed: Re: Your mail

2015-10-09 Thread Debian Bug Tracking System
Processing control commands:

> forcemerge -1 801063
Bug #801062 [wnpp] (no subject)
Bug #801063 [wnpp] world -- high-quality speech analysis/synthesis system on 
the basis of Vocoder.
Owner recorded as Tobias Platen .
Merged 801062 801063
> retitle -1 ITP: world -- high-quality speech analysis/synthesis system on the 
> basis of Vocoder.
Bug #801062 [wnpp] (no subject)
Bug #801063 [wnpp] world -- high-quality speech analysis/synthesis system on 
the basis of Vocoder.
Changed Bug title to 'ITP: world -- high-quality speech analysis/synthesis 
system on the basis of Vocoder.' from '(no subject)'
Changed Bug title to 'ITP: world -- high-quality speech analysis/synthesis 
system on the basis of Vocoder.' from 'world -- high-quality speech 
analysis/synthesis system on the basis of Vocoder.'

-- 
801062: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=801062
801063: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=801063
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems



Processed: block 761914 with 798278

2015-10-09 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> block 761914 with 798278
Bug #761914 [wnpp] ITP: mapbox-studio -- Vector tile driven map design
761914 was not blocked by any bugs.
761914 was not blocking any bugs.
Added blocking bug(s) of 761914: 798278
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
761914: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=761914
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems



Bug#787953: depends on obsolete libasm2-java library

2015-10-09 Thread Felix Natter
Markus Koschany  writes:

> Hello,

hello Markus,

> FTR: As already noted in the initial bug report, substance and its
> dependency liblaf-widget-java are unmaintained. Last version was
> released in 2010.
>
> https://java.net/projects/substance
>
> Last Github snapshot:
>
> https://github.com/kirillcool/substance
>
> substance was forked into insubstantial:

(Not just substance, all 7 flamingo/substance/trident packages)

> https://github.com/Insubstantial/insubstantial
>
> and Felix Natter (CCed) intended to maintain it for Debian (#787953).

Yes, I need this for the upcoming freeplane 1.4 (I also have patches for
the r-deps) :-)

I will soon fix some copyright problems that Tony (CC) told be about.

I already argued in favor of the upgrade on debian-java:
  https://lists.debian.org/debian-java/2015/08/msg00043.html

> Unfortunately insubstantial is also unmaintained now and still depends
> on asm2.
>
> I think it only makes sense to replace substance and its libraries with
> insubstantial when upstream development continues and asm2 is replaced
> with a newer, Java 7+ compatible version.

Are you sure? I was able to build insubstantial (7.3) with asm2 and used
the resulting package in the r-deps jajuk/bgfinancas/triplea[2]/freeplane)
where it worked fine.

[2] triplea 1.8 will require insubstantial (7.3):
http://sourceforge.net/p/triplea/code/HEAD/tree/trunk/triplea/changelog.txt

A quick search in the history (http://asm.ow2.org/history.html) did not
reveal anything.  They claim that ASM4 will "full[y] support of Java 7"
and ASM5 will "Full[y] support of Java 8" but does that really mean that
it does not work with java7/java8?

But reading #801322/#801323, I guess you argue that libasm2 must be
removed from the archive.

> I am going to file bug reports against Jajuk and bgfinancas which depend
> on substance and ask that they either move away from substance or take
> over maintenance.

Moving away from flamingo/substance/trident is _a lot_ of work. For
freeplane this would mean rewriting the user interface (ribbons).
The jajuk maintainers tell similar things [3]
(though it's easier for jajuk because they "only" use substance L)

[3] https://github.com/jajuk-team/jajuk/issues/1994

> I have opened an upstream bug report for Jajuk already:
>
> https://github.com/jajuk-team/jajuk/issues/1994

How about trying to add a Debian patch to make insubstantial (7.3) build
with asm4 (if that is necessary)? Shall I look into it?

Cheers and Best Regards,
-- 
Felix Natter



Bug#801408: ITP: python-duckduckgo2 -- Library for querying the DuckDuckGo API

2015-10-09 Thread Iain R. Learmonth
Package: wnpp
Severity: wishlist
Owner: "Iain R. Learmonth" 

Hi,

* Package name: python-duckduckgo2
  Version : 0.242
  Upstream Author : Michael Smith 
* URL : https://pypi.python.org/pypi/duckduckgo2/
* License : BSD
  Programming Lang: Python
  Description : Library for querying the DuckDuckGo API

A Python library for querying the DuckDuckGo Instant Answer API. The
Instant Answer API gives you free access to many of DuckDuckGo's instant
answers like: topic summaries, categories, disambiguation, and !bang
redirects.

More information on the Instant Answer API can be found at:

  https://duckduckgo.com/api

Thanks,
Iain.

-- 
e: i...@fsfe.orgw: iain.learmonth.me
x: i...@jabber.fsfe.org t: EPVPN 2105
c: 2M0STB  g: IO87we
p: 1F72 607C 5FF2 CCD5 3F01 600D 56FF 9EA4 E984 6C49


pgp9hCsvSej1y.pgp
Description: PGP signature


Processed: Rename the source package

2015-10-09 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> retitle 801366 ITP: jupyter-notebook -- Jupyter interactive notebook
Bug #801366 [wnpp] ITP: notebook -- Jupyter interactive notebook
Changed Bug title to 'ITP: jupyter-notebook -- Jupyter interactive notebook' 
from 'ITP: notebook -- Jupyter interactive notebook'
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
801366: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=801366
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems



Bug#787953: depends on obsolete libasm2-java library

2015-10-09 Thread Markus Koschany
Hi!

Am 09.10.2015 um 21:01 schrieb Felix Natter:
> Markus Koschany  writes:
[...]
>> Unfortunately insubstantial is also unmaintained now and still depends
>> on asm2.
>>
>> I think it only makes sense to replace substance and its libraries with
>> insubstantial when upstream development continues and asm2 is replaced
>> with a newer, Java 7+ compatible version.
> 
> Are you sure? I was able to build insubstantial (7.3) with asm2 and used
> the resulting package in the r-deps jajuk/bgfinancas/triplea[2]/freeplane)
> where it worked fine.

My concerns are not about building insubstantial with asm2. That works.
I query whether it makes sense to switch from one unmaintained project
(substance, liblaf-widget-java, trident, etc) to another one
(insubstantial).

http://speling.shemnon.com/blog/2013/06/08/insubstantial-needs-a-new-maintainer/

If you really intend to maintain insubstantial you should be prepared to
do development work as bug fixing or switching from asm2 to asm5 too.
Otherwise we and you invest a lot of time for a switch but without a
significant gain.


> [2] triplea 1.8 will require insubstantial (7.3):
> http://sourceforge.net/p/triplea/code/HEAD/tree/trunk/triplea/changelog.txt

The Debian package of triplea currently recommends substance and I think
this will remain when 1.8 is packaged. Making a LAF-theme optional is
one of the solutions I can think of.

> 
> A quick search in the history (http://asm.ow2.org/history.html) did not
> reveal anything.  They claim that ASM4 will "full[y] support of Java 7"
> and ASM5 will "Full[y] support of Java 8" but does that really mean that
> it does not work with java7/java8?
> 
> But reading #801322/#801323, I guess you argue that libasm2 must be
> removed from the archive.

Careful. asm2 was released ten years ago and is currently packaged in
libasm2-java. The latest version of asm is packaged in libasm4-java
(actually asm5). I have only filed those bug reports because I would
like to see modern packages use the latest version of asm and not
something from the last decade. So libasm4-java is fully supported
upstream. I just care and want to clean up a little and to remove (very)
old packages. Maintaining several versions of the same library in Debian
should be the exception, even for Java.

>> I am going to file bug reports against Jajuk and bgfinancas which depend
>> on substance and ask that they either move away from substance or take
>> over maintenance.
> 
> Moving away from flamingo/substance/trident is _a lot_ of work. For
> freeplane this would mean rewriting the user interface (ribbons).
> The jajuk maintainers tell similar things [3]
> (though it's easier for jajuk because they "only" use substance L)
> 
> [3] https://github.com/jajuk-team/jajuk/issues/1994

I have to further discuss this with the upstream developer of Jajuk but
he indicated that he could be willing to switch to Nimbus as the default
theme. He might also be interested in helping you to port insubstantial
to asm5 (libasm4-java). I will ask him.

>> I have opened an upstream bug report for Jajuk already:
>>
>> https://github.com/jajuk-team/jajuk/issues/1994
> 
> How about trying to add a Debian patch to make insubstantial (7.3) build
> with asm4 (if that is necessary)? Shall I look into it?

That would be definitely one of the preferred options to solve this issue.

I see the following option:

1. Go ahead and package insubstantial as one source package that
provides the old binary packages from substance, trident,
liblaf-widget-java, etc. Maven poms should be provided as well. If you
also provide a patch to build with libasm4-java we could easily replace
the old dependencies for jajuk, bgfinancas, triplea and freeplane with
your new version and remove libasm2-java from Debian. (only
jasperreports would be an open issue but I would invest the time to fix
this package myself)

Win-Win situation

2. Make substance an optional theme and use Nimbus or other standard themes.

3. Do not depend on unmaintained software like substance at all. ;-)

Cheers,

Markus







signature.asc
Description: OpenPGP digital signature


Bug#801397: ITP: tuptime -- Report historical and statistical running time of the system, keeping it between restarts.

2015-10-09 Thread Ricardo F
Package: wnpp
Severity: wishlist
Owner: Ricardo F 

* Package name: tuptime
  Version : 3.2.01
  Upstream Author : Name 
* URL : https://github.com/rfrail3/tuptime
* License : GPL
  Programming Lang: Python
  Description : Report historical and statistical running time of the 
system, keeping it between restarts.


Tuptime is a tool for report the historical and statistical running time of the 
system, keeping it between restarts. Indeed, it can:

  - Count system startups
  - Register first boot time (a.k.a. installation time)
  - Count nicely and accidentally shutdowns
  - Uptime and downtime percentage since first boot time
  - Accumulated system uptime, downtime and total
  - Largest, shortest and average uptime and downtime
  - Current uptime
  - Print formatted table or list with most of the previous values
  - Register used kernels