On 2016-06-24 23:01 -0700, Josh Triplett wrote:
> Some packages, if installed on any architecture, must be installed for
> every enabled architecture. Most notably, an NSS or PAM module package,
> if enabled in /etc/nsswitch.conf or /etc/pam.d respectively, must exist
> for every enabled architec
On Fri, 2016-06-24 at 23:01 -0700, Josh Triplett wrote:
> Some packages, if installed on any architecture, must be installed for
> every enabled architecture. Most notably, an NSS or PAM module package,
> if enabled in /etc/nsswitch.conf or /etc/pam.d respectively, must exist
> for every enabled a
On Sat, Jun 25, 2016 at 09:37:37AM +0200, Ben Hutchings wrote:
> On Fri, 2016-06-24 at 23:01 -0700, Josh Triplett wrote:
> > Some packages, if installed on any architecture, must be installed for
> > every enabled architecture. Most notably, an NSS or PAM module package,
> > if enabled in /etc/nss
Sven Joachim wrote:
> On 2016-06-24 23:01 -0700, Josh Triplett wrote:
> > Some packages, if installed on any architecture, must be installed for
> > every enabled architecture. Most notably, an NSS or PAM module package,
> > if enabled in /etc/nsswitch.conf or /etc/pam.d respectively, must exist
>
On Fri, 24 Jun 2016 at 23:01:21 -0700, Josh Triplett wrote:
> Some packages, if installed on any architecture, must be installed for
> every enabled architecture. Most notably, an NSS or PAM module package,
> if enabled in /etc/nsswitch.conf or /etc/pam.d respectively, must exist
> for every enabl
I have an interpreter name (say "Python") and an interval of versions (say
"2.5 - 2.6").
Based on this data I need to select the python executable among installed
files, if available.
The rule of the "game" is that I write a data file (preferably in RDF/Turtle
format) which describes all avail
On Sat, Jun 25, 2016 at 02:41:04PM +0300, Victor Porton wrote:
> I have an interpreter name (say "Python") and an interval of versions (say
> "2.5 - 2.6").
>
> Based on this data I need to select the python executable among installed
> files, if available.
That "problem" is solved by '#!/usr/bi
Control: retitle -1 ITP: lua-stdlib -- Standard Lua libraries
Control: owner -1 !
On Tuesday, October 22 2013, Axel Beckert wrote:
> * Package name: lua-stdlib
> Version : v35
> Upstream Author : Reuben Thomas et al.
> * URL or Web page : https://github.com/rrthomas/lua-stdlib
> *
On Fri, Jun 24, 2016 at 11:19:33PM +0200, Alexander Wirt wrote:
> On Fri, 24 Jun 2016, Elimar Riesebieter wrote:
> > * Jonathan Dowland [2016-06-24 09:24 +0100]:
> > > On Thu, Jun 23, 2016 at 09:10:50PM +0200, Elimar Riesebieter wrote:
> > > >
> > > > I've packaged neomutt for Debian. A Debian IT
On Sat, Jun 25, 2016 at 02:01:27AM -0700, Josh Triplett wrote:
> Sven Joachim wrote:
> > On 2016-06-24 23:01 -0700, Josh Triplett wrote:
> > > Some packages, if installed on any architecture, must be installed for
> > > every enabled architecture. Most notably, an NSS or PAM module package,
> > >
Geert Stappers, you have misunderstood my problem.
I want to support ALL interpreters available in Debian (Perl, Python, Ruby,
Java, etc.)
I need to make supporting all interpreters and all their versions
manageable. My question is how to support it all, specifically when a user
explicitly spe
On Sat, Jun 25, 2016 at 06:44:35PM +0300, Victor Porton wrote:
> Geert Stappers wrote:
> > On Sat, Jun 25, 2016 at 02:41:04PM +0300, Victor Porton wrote:
> > > I have an interpreter name (say "Python") and an interval of versions
... 28 lines from previous posting ( not previous discussion ) .
Josh Triplett writes ("Handling Multi-Arch packages that must be installed for
every enabled architecture?"):
> That would solve the problem for the couple of cases it has come up in,
> but it seems far from ideal; I'd welcome an cleaner alternative
> solution. Notably, this doesn't work well for
Victor Porton writes ("Re: How to select an interpretor version?"):
> Geert Stappers, you have misunderstood my problem.
>
> I want to support ALL interpreters available in Debian (Perl, Python, Ruby,
> Java, etc.)
>
> I need to make supporting all interpreters and all their versions
> manageab
On Sat, Jun 25, 2016 at 07:08:39PM +0100, Ian Jackson wrote:
> Josh Triplett writes ("Handling Multi-Arch packages that must be installed
> for every enabled architecture?"):
> > That would solve the problem for the couple of cases it has come up in,
> > but it seems far from ideal; I'd welcome an
Package: wnpp
Severity: wishlist
Owner: Debian Med team
* Package name: cnvkit
Version : 0.7.11
Upstream Author : Eric Talevich
* URL : http://cnvkit.readthedocs.io/
* License : Apache-2.0
Programming Lang: Python
Description : Copy number variant dete
Simon McVittie wrote:
> On Fri, 24 Jun 2016 at 23:01:21 -0700, Josh Triplett wrote:
> > Some packages, if installed on any architecture, must be installed for
> > every enabled architecture. Most notably, an NSS or PAM module package,
> > if enabled in /etc/nsswitch.conf or /etc/pam.d respectively
Josh Triplett writes ("Re: Handling Multi-Arch packages that must be installed
for every enabled architecture?"):
> On Sat, Jun 25, 2016 at 07:08:39PM +0100, Ian Jackson wrote:
> > * LD_PRELOAD hacks need their .so installing for all architecture "for
> > which they are going to be used" (whatev
David Kalnischkies wrote:
> On Sat, Jun 25, 2016 at 02:01:27AM -0700, Josh Triplett wrote:
> > Sven Joachim wrote:
> > > On 2016-06-24 23:01 -0700, Josh Triplett wrote:
> > > > Some packages, if installed on any architecture, must be installed for
> > > > every enabled architecture. Most notably,
Ian Jackson wrote:
> Victor Porton writes ("Re: How to select an interpretor version?"):
>> Geert Stappers, you have misunderstood my problem.
>>
>> I want to support ALL interpreters available in Debian (Perl, Python,
>> Ruby, Java, etc.)
>>
>> I need to make supporting all interpreters and all
Package: wnpp
Severity: wishlist
Owner: Debian Med team
* Package name: r-cran-r.cache
Version : 0.12.0
Upstream Author : Henrik Bengtsson
* URL : https://github.com/HenrikBengtsson/R.cache
* License : LGPL (>= 2.1)
Programming Lang: R
Description : R
Package: wnpp
Severity: wishlist
Owner: Debian Med team
* Package name: r-bioc-dnacopy
Version : 1.46.0
Upstream Author : Venkatraman E. Seshan
* URL :
http://www.bioconductor.org/packages/release/bioc/html/DNAcopy.html
* License : GPL-2.0+
Programming Lang
Victor Porton writes ("Re: How to select an interpretor version?"):
> I am going to write a program which automatically converts between XML
> formats using scripts described by RDF resources located at namespace URLs
> (not a precise description of my project, but you've got the taste).
>
> The
On Sat, 2016-06-25 at 23:54 +0100, Ian Jackson wrote:
> Victor Porton writes ("Re: How to select an interpretor version?"):
> > I am going to write a program which automatically converts between
> > XML
> > formats using scripts described by RDF resources located at
> > namespace URLs
> > (not a
Package: wnpp
Severity: wishlist
Owner: Debian Med team
* Package name: r-cran-listenv
Version : 0.6.0
Upstream Author : Henrik Bengtsson
* URL : https://github.com/HenrikBengtsson/listenv
* License : LGPL 2.1+
Programming Lang: R
Description : R packa
Package: wnpp
Severity: wishlist
Owner: Debian Med team
* Package name: r-cran-globals
Version : 0.6.1
Upstream Author : Henrik Bengtsson
* URL : https://github.com/HenrikBengtsson/globals
* License : LGPL-2.1+
Programming Lang: R
Description : R packa
Package: wnpp
Severity: wishlist
Owner: Debian Med team
* Package name: r-cran-future
Version : 1.0.0
Upstream Author : Henrik Bengtsson
* URL : https://github.com/HenrikBengtsson/future
* License : LGPL-2.1+
Programming Lang: R
Description : R package
]] Holger Levsen
> On Wed, Jun 22, 2016 at 08:13:40AM +, Eliran Mesika wrote:
> > As I wrote earlier, we're open to making certain features available upon
> > request. In the specific case of the feature that was discussed - could you
> > please elaborate what is missing and what functionalit
28 matches
Mail list logo
