Package: wnpp
Severity: wishlist
Description:
A simple command-line password manager that keeps passwords inside a
gpg encrypted tgz archive. The content of the archive is a directory tree
with a file for each password entry. The first line of the file is the
password, and the rest can opt
RedisLabs have changed the license of various modules to be
incompatible with DFSG guideline 6: the 'Common Clause' rider.
https://redislabs.com/community/commons-clause/
Some examples - redis-timeseries, redisearch, rejson, rebloom, eredis,
redis-ml, at least some of which are in Debian
-Rob
Package: wnpp
Severity: wishlist
Owner: Michael Fladischer
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
* Package name: python-django-csp
Version : 3.4
Upstream Author : James Socol
* URL : https://github.com/mozilla/django-csp/
* License : BSD-3-clause
Package: wnpp
Severity: wishlist
Owner: Xavier Guimard
* Package name: libdbd-mariadb-perl
Version : 1.00
Upstream Author : Pali Rohár
* URL : https://metacpan.org/release/DBD-MariaDB
* License : Artistic or GPL-1+
Programming Lang: Perl
Description :
Package: wnpp
Severity: wishlist
Owner: Mike Gabriel
* Package name: cmake-vala
Version : 1
Upstream Author : Konstantin Pugin
* URL : https://gitlab.com/vala-panel-project/cmake-vala/
* License : BSD-2, BSD-3, BSL-1.0, LGPL-2.1+
Programming Lang: cmake
De
Package: wnpp
Severity: wishlist
Owner: Mechtilde
* Package name: tbsync
Version : 0.7.12
Upstream Author : Name john.biel...@gmx.de
* URL : https://github.com/jobisoft/TbSync
* License : GPL v3
Programming Lang: Javascript
Description : [Thunderbird Ad
On 21/08/18 14:05, Tobias Frost wrote:
> Dear fellow Debinites,
>
> many of you know already that there is currently a discussion about
> establishing a package salvaging process within Debian. The discussion
> is taking place at debian-devel, but I'd like make people aware which
> are not subs
On Tue, Aug 21, 2018 at 05:07:21PM +0300, Adrian Bunk wrote:
> This also opens the general question whether 3rd party repositories
> should become strongly discouraged in general, and flatpak/snap/...
> recommended instead.
The very mention of "flatpak/snap" answers your question, with an emphatic
On Tue, Aug 21, 2018 at 03:41:20PM +0200, Wouter Verhelst wrote:
>...
> I agree that having a key fingerprint on a valid TLS website is less
> good than having a trust anchor in Debian,
>...
The problem is that this is a trust anchor provided by Debian.
If a user installs the Emdebian or leap.se
On Tue, Aug 21, 2018 at 01:15:03PM +0200, Adam Borowski wrote:
> On Tue, Aug 21, 2018 at 01:39:29PM +0800, Paul Wise wrote:
> > On Tue, Aug 21, 2018 at 1:21 PM, Kentaro Hayashi wrote:
> >
> > > I want to make 3rd party keyring package (ITP). In the advance, I
> > > want to know a best practice abo
On Tue, Aug 21, 2018 at 01:39:29PM +0800, Paul Wise wrote:
> On Tue, Aug 21, 2018 at 1:21 PM, Kentaro Hayashi wrote:
>...
> > So, I plan to make one more 3rd party keryring into Debian.
>
> That seems like a reasonable way to provide a secure mechanism to install it.
This would actually compromis
On Tue, Aug 21, 2018 at 08:13:24PM +0900, Roger Shimizu wrote:
> And emdebian's keyring [3] didn't hit archive, either.
Wrong:
https://tracker.debian.org/pkg/emdebian-archive-keyring
"As of July 2014, updates to the Emdebian distributions ceased." though.
--
WBR, wRAR
signature.asc
Descriptio
On Tue, Aug 21, 2018 at 01:39:29PM +0800, Paul Wise wrote:
> On Tue, Aug 21, 2018 at 1:21 PM, Kentaro Hayashi wrote:
>
> > I want to make 3rd party keyring package (ITP). In the advance, I
> > want to know a best practice about *keyring* packaging. Any hints?
>
> > sudo apt install -y -V --allo
On Tue, Aug 21, 2018 at 2:39 PM, Paul Wise wrote:
> On Tue, Aug 21, 2018 at 1:21 PM, Kentaro Hayashi wrote:
>
>> I want to make 3rd party keyring package (ITP). In the advance, I
>> want to know a best practice about *keyring* packaging. Any hints?
>
> There are some best practices for using 3rd p
On Tue, 21 Aug 2018, Kentaro Hayashi wrote:
> I want to make 3rd party keyring package (ITP). In the advance, I
> want to know a best practice about *keyring* packaging. Any hints?
I'm not convinced that 3rd party keyring packages belong in the Debian
archive.
If the software itself is good and
15 matches
Mail list logo
