On Thu, Aug 18, 2016 at 12:17 PM, Marcin Kulisz wrote:
> On 2016-08-18 16:27:23, Luke W Faraone wrote:
>> Package: wnpp
>> Severity: wishlist
>> Owner: Luke W Faraone
>>
>> * Package name: powershell
>> Version : 6.0.0~alpha9
>> Upstream Author : Microsoft
>> * URL : h
Package: wnpp
Severity: wishlist
Owner: Sean Whitton
* Package name: keysafe
Version : 0.20160819
Upstream Author : Joey Hess
* URL : https://joeyh.name/code/keysafe/
* License : AGPL-3
Programming Lang: Haskell
Description : back up secret keys to clo
Package: wnpp
Severity: wishlist
Owner: Antonio Terceiro
* Package name: python-whitenoise
Version : 3.2.1
Upstream Author : David Evans
* URL : http://whitenoise.evans.io
* License : MIT/Expat
Programming Lang: Python
Description : static file serving
Package: wnpp
Severity: wishlist
Owner: Sergio Durigan Junior
* Package name: libjs-jquery-selectize.js
Version : 0.12.2
Upstream Author : Brian Reavis
* URL : https://github.com/selectize/selectize.js
* License : Apache-2.0 and Expat
Programming Lang: JavaS
On 08/19/2016 08:15 PM, Mario Lang wrote:
Christoph Egger writes:
Marcin Kulisz writes:
Most likely I'm missing something but what's the use case for Powershell on
I don't know, what's the usecase for tcsh or lua?
tcsh is to support legacy scripts, but, very good question: What *is*
the
Christoph Egger writes:
> Marcin Kulisz writes:
>> Most likely I'm missing something but what's the use case for Powershell on
>
> I don't know, what's the usecase for tcsh or lua?
tcsh is to support legacy scripts, but, very good question: What *is*
the use-case for Lua actually? :-)
--
CYa,
Package: wnpp
Severity: wishlist
X-Debbugs-CC: debian-devel@lists.debian.org
--- Please fill out the fields below. ---
Package name: ShogiGUI
Version: 0.0.6.1
Upstream Author: [shogix...@gmail.com] Can't figure out who the author is.
URL: [http://shogigui.siganus.com/]
On August 19, 2016 10:44:44 AM EDT, Marcin Kulisz wrote:
>Ha, so we're trying lure Windows admins to Debian under the pretence of
>'you
>can do the same from Debian' and then quietly make them drop
>proprietary
>platforms. Sounds like a good plan to me.
Embrace, extend, extinguish? ;-)
--
Harl
On 2016-08-19 15:34:14, Dimitri John Ledkov wrote:
> On 18 August 2016 at 18:17, Marcin Kulisz wrote:
> > Most likely I'm missing something but what's the use case for Powershell on
> > Debian?
>
> On more practical note - there is a bunch of tooling and cmdtets to
> manage remote service from po
On 18 August 2016 at 18:17, Marcin Kulisz wrote:
> On 2016-08-18 16:27:23, Luke W Faraone wrote:
>> Package: wnpp
>> Severity: wishlist
>> Owner: Luke W Faraone
>>
>> * Package name: powershell
>> Version : 6.0.0~alpha9
>> Upstream Author : Microsoft
>> * URL : https:/
Hi,
Quoting Ian Jackson (2016-08-19 14:25:52)
> (Would it not be possible to generate the key inside the chroot? I
> guess there are probably other problems with that.)
that would require lots of time and entropy - unless somebody knows how to
trick gpg to generate a private/public key pair from
Package: wnpp
Severity: wishlist
Owner: Ghislain Antony Vaillant
* Package name: glbinding
Version : 2.1.1
Upstream Author : CG Internals GmbH
* URL : https://github.com/cginternals/glbinding
* License : Expat
Programming Lang: C++
Description : cross-p
Package: wnpp
Severity: wishlist
Owner: Eugene Zhukov
*Package Name: openvpn-systemd-resolved
Version: 1.1.1
Upstream Author: Jonathan Wright
*URL: https://github.com/jonathanio/update-systemd-resolved
*License: GPL
Description: integrates OpenVPN with systemd-resolved
This is a helper script
Johannes Schauer writes ("Re: Does anybody plan to keep using sbuild with
Squeeze or older chroots?"):
> Old sbuild will not help you. The problem is mainly, that older
> chroots contain an apt installation that has no support for the
> [trusted=yes] option in sources.list. This in turn means that
Hi,
Quoting Ian Jackson (2016-08-19 14:04:40)
> And to those others who replied, I would like to point out that answers of
> the form "oh no surely they don't" to questions like Johannes's can be
> harmful.
I read their answers as: "I don't think it is necessary for sbuild to support a
distributi
Hello,
I accidentally called "dpkg-name" on some *.udeb files and they got
renamed to .deb.
Looking inside dpkg-name, it tries to evaluate "Package-Type" [1], but
that is not contained in the control file of the binary package, so
always evaluates to "deb":
> 123 my $type = $fields->{'Package
On Fri, Aug 19, 2016 at 01:01:23PM +0100, Ian Jackson wrote:
> > does anybody plan to use sbuild in Stretch with Debian Squeeze or older
> > chroots?
>
> Yes.
I'm actually not doing Debian packaging for it, but at work there still
are embedded machines running Lenny, where upgrading is simply no
Ian Jackson writes ("Re: Does anybody plan to keep using sbuild with Squeeze or
older chroots?"):
> Johannes Schauer writes ("Does anybody plan to keep using sbuild with Squeeze
> or older chroots?"):
> > does anybody plan to use sbuild in Stretch with Debian Squeeze or older
> > chroots?
>
> Ye
Johannes Schauer writes ("Does anybody plan to keep using sbuild with Squeeze
or older chroots?"):
> does anybody plan to use sbuild in Stretch with Debian Squeeze or older
> chroots?
Yes.
> I would like to remove some code from sbuild which is only useful
> for chroots with very old apt inside
19 matches
Mail list logo
