Kari Pahula | 6 Jul 21:40 2015
Picon

Bug#791608: ITP: minizinc -- Constraint modelling language and tool chain

Package: wnpp
Severity: wishlist
Owner: Kari Pahula <kaol <at> debian.org>

* Package name    : minizinc
  Version         : 2.0.4
  Upstream Author : Guido Tack <guido.tack <at> monash.edu>
* URL             : http://www.minizinc.org/
* License         : MPL-2.0, MS-PL
  Programming Lang: C++
  Description     : constraint modelling language and tool chain

 MiniZinc is a medium-level constraint modelling language. It is
 high-level enough to express most constraint problems easily, but
 low-level enough that it can be mapped onto existing solvers easily
 and consistently. It is a subset of the higher-level language Zinc.
 .
 MiniZinc is designed to interface easily to different backend
 solvers.  It does this by transforming an input MiniZinc model and
 data file into a FlatZinc model. FlatZinc models consist of variable
 declaration and constraint definitions as well as a definition of the
 objective function if the problem is an optimization problem. The
 translation from MiniZinc to FlatZinc is specializable to individual
 backend solvers, so they can control what form constraints end up
 in. In particular, MiniZinc allows the specification of global
 constraints by decomposition.

I already maintain Gecode, which includes a FlatZinc interpreter.  I
intend to package minizinc and minizinc-ide to provide more use for
Gecode.
(Continue reading)

Colin Tuckley | 6 Jul 11:41 2015
Picon

Bug#791564: ITP: linpac -- A packet terminal program

Package: wnpp
Severity: wishlist
Owner: Colin Tuckley <colint <at> debian.org>

* Package name    : linpac
  Version         : 0.21
  Upstream Author : David Ranch <dranch <at> trinnet.net>
* URL             : https://sourceforge.net/projects/linpac/
* License         : GPL V2
  Description     : A packet terminal program

Linpac was previously in Debian but was removed due to bugs and lack of upstream support.

The project is now under new management and is being supported upstream.

lauren-blaine | 6 Jul 00:37 2015
Picon

Bug#791536: general: Debian 7.8 running EXTREMELY slow. Like chronic stop script error.

Package: general
Severity: important

Dear Maintainer,
*** Please consider answering these questions, where appropriate ***

   * What led up to the situation? Seems unrelated to any change
   * What exactly did you do (or not do) that was effective (or
     ineffective)? I thought that it was a stop script error with facebook but
it is constant, even when facebook is off. Restarting doesn't help. Within a
short time, it's back to turtle slow, long hesitations between typing letters,
extremely long time for web pages to load. etc. Wondering if it's a virus.
   * What was the outcome of this action?
   * What outcome did you expect instead?

*** End of the template - remove these lines ***

-- System Information:
Debian Release: 7.8
  APT prefers oldstable-updates
  APT policy: (500, 'oldstable-updates'), (500, 'oldstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.2.0-4-amd64 (SMP w/6 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Steve M. Robbins | 5 Jul 20:52 2015
Picon

GCC 5 / libstdc++ abi wiki: can FIXMEs be fixed?

Hi,

I've heard rumours that GCC 5 is coming :-)

I help maintain several C++ libraries and expect some work is required to get 
through this GCC transition.  I'd like to understand what I'm doing and do it 
right the first time.  I'm just an average C++ programmer, not an avid follower 
of GCC nor even of debian lists.  So below are lots of questions asked out of 
ignorance.  Please don't shoot the messenger/questioner.  :-)

Posts here and bug reports reference the wiki page 
https://wiki.debian.org/GCC5 .  I've read that page and there are a bunch of 
notes embedded within it that just confuse me:

1. "The good news is, that GCC 5 now provides a stable libcxx11 ABI, and 
stable support for C++11 (GCC version before 5 called this supported 
experimental). This required some changes in the libstdc++ ABI, and now 
libstdc++6 provides a dual ABI, the classic libcxx98 ABI, and the new libcxx11 
(FIXME: GCC 5 (<< 5.1.1-20) only provides the classic libcxx98 ABI)."

What does the FIXME refer to?  That the correct statement is "The good new is, 
that GCC 5 (post 5.1.1-20) now provides .."?  Or something else?

2. "libstdc++ doesn't change the soname, provides a dual ABI. Existing C++98 
binary packages will continue to work. Building these packages using g++-5 is 
expected to work after build failures are fixed. FIXME: Will they only work 
when built with _GLIBCXX_USE_CXX11_ABI set to 0? By default they will use the 
new libstdc++ ABI."

What's the answer to this FIXME?  What does the last sentence mean?  Does it 
(Continue reading)

Andreas Tille | 5 Jul 17:28 2015
Picon

Bug#791483: ITP: r-cran-r.oo -- GNU R object-oriented programming with or without references

Package: wnpp
Severity: wishlist
Owner: Andreas Tille <tille <at> debian.org>

* Package name    : r-cran-r.oo
  Version         : 1.19.0
  Upstream Author : Henrik Bengtsson <henrikb <at> braju.com>
* URL             : http://cran.r-project.org/web/packages/R.oo/
* License         : LGPL
  Programming Lang: R
  Description     : GNU R object-oriented programming with or without references
 Methods and classes for object-oriented programming in R with or
 without references. Large effort has been made on making definition of
 methods as simple as possible with a minimum of maintenance for package
 developers. The package has been developed since 2001 and is now
 considered very stable. This is a cross-platform package implemented in
 pure R that defines standard S3 classes without any tricks.

Remark: This package is another precondition of a Debian Med target
and maintained at
    svn://anonscm.debian.org/debian-med/trunk/packages/R/r-cran-r.oo/

lumin | 4 Jul 18:55 2015
Picon

The Spirit of Free Software, or The Reality

Hello Debian community,

I long for becoming a Debian member, always. However now I get into
trouble with the problem of "Spirit of Free software or Reality".
I wonder how Debian interprets it's "Spirit of Free Software".
(Certainly Social Contract and DFSG don't refer much detail)

As we know, getting into the stage where as the same as
Richard.M.Stallman (i.e. Resists any non-free stuff, thoroughly )
is very hard for an ordinary person, as well as me. Even though,
many people are trying their best to protect their software freedom,
with several careful compromises to non-free blobs.

Several years ago I was influenced by Debian's insist on Freesoftware,
and then trying to gradually block non-free matters away, and was
very happy doing that, because I protected my computer away from those
terrible non-free softwares and got myself stayed in a clean, pure
computer environment.

Blocking non-free blobs away, does it means partially blinding
one's eye for teenagers? In order to get touched with the world
outside of freesoftware, sometimes indeed we need to compromise with
non-free blobs, at least temporarily. After all freesoftware communities
and opensource software communities occupies only a tiny proportion
of human.

Hence my strategy was changed. I compromised with more and more 
non-free blobs when I want to experience what I haven't experienced,
when I want to gain what I don't possess, when I want to explore the 
outer world that I haven't seen.
(Continue reading)

Balasankar C | 4 Jul 14:39 2015

Bug#791406: ITP: ruby-unicorn-worker-killer -- library to kill unicorn workers by memory and request counts

Package: wnpp
Severity: wishlist
Owner: Balasankar C <balasankarc <at> autistici.org>

* Package name    : ruby-unicorn-worker-killer
  Version         : 0.4.2
  Upstream Author : Kazuki Ohta <kazuki.ohta <at> gmail.com>
* URL             : https://github.com/kzk/unicorn-worker-killer
* License         : GPL-2+ or Ruby
  Programming Lang: Ruby
  Description     : library to kill unicorn workers by memory and request counts

Sandro Tosi | 4 Jul 04:01 2015
Picon

Bug#791376: ITP: cycler -- composable style cycles

Package: wnpp
Severity: wishlist
Owner: Sandro Tosi <morph <at> debian.org>

* Package name    : cycler
  Version         : 0.9.0
  Upstream Author : Thomas A Caswell
* URL             : http://github.com/matplotlib/cycler
* License         : BSD
  Programming Lang: Python
  Description     : composable style cycles

it will be a dep for matplotlib in a future release

Balasankar C | 3 Jul 22:05 2015

Bug#791359: ITP: ruby-rqrcode-rails3 -- render QR codes with Rails 3

Package: wnpp
Severity: wishlist
Owner: Balasankar C <balasankarc <at> autistici.org>

* Package name    : ruby-rqrcode-rails3
  Version         : 0.1.5
  Upstream Author : Sam Vincent <sam.vincent <at> mac.com>
* URL             : https://github.com/samvincent/rqrcode-rails3
* License         : Expat
  Programming Lang: Ruby
  Description     : render QR codes with Rails 3

Balasankar C | 3 Jul 13:57 2015

Bug#790971: ITP: ruby-redis-actionpack -- Redis session store for ActionPack

Package: wnpp
Severity: wishlist
Owner: Balasankar C <balasankarc <at> autistici.org>

* Package name    : ruby-redis-actionpack
  Version         : 4.0.0
  Upstream Author : Luca Guidi <me <at> lucaguidi.com>
* URL             : https://github.com/redis-store/redis-actionpack
* License         : Expat
  Programming Lang: Ruby
  Description     : Redis session store for ActionPack

Daniel Pocock | 3 Jul 11:09 2015

server certificates/key pairs and CA directories


Hi all,

There has been some discussion in the past about CA certificates and
server certificate/key locations in /etc

I'd like to ensure that the RTC Quick Start Guide[1] is giving people
accurate instructions about where to create their private key and server
certificate files on a Debian host.

I couldn't find a specific policy on how it is currently supposed to be
managed, although there are a few proposals on the wiki:

  https://wiki.debian.org/X.509
  https://wiki.debian.org/SslCertificateHandling

I looked at the package ssl-cert to try and understand and there I found
that it is using /etc/ssl/certs for server certs while other packages
trust that directory as a store of root certs, I opened a bug[2] for that.

Can anybody refer me to any document that describes the current
situation, whether it is in a policy document, wiki or mailing list archive?

Is anybody currently working on improving this situation?

Regards,

Daniel

1. http://rtcquickstart.org/guide/multi/tls-install-certificate.html
(Continue reading)


Gmane