Package: wnpp
Severity: wishlist
Owner: Python Applications Packaging Team
* Package name: pylci
Version : 2017-03-10
Upstream Author : Pičugins Arsenijs
* URL : https://github.com/CRImier/pyLCI
* License : Apache 2.0
Programming Lang: Python
Description
Package: wnpp
Severity: wishlist
Owner: Sean Whitton
* Package name: message-templ
Version : 0.3.20161104
Upstream Author : ARISAWA Akihiro
* URL : git://pivot.cs.unb.ca/message-templ.git
* License : GPL-2+
Programming Lang: Emacs Lisp
Description : te
On 02/08/17 21:54, Guido Günther wrote:
>
> [...]
>
> We could also store it in the upstream tag message when importing the
> tarball but having it on pristine-tar looks nicer. Will you file
> wishlist bug against pristine-tar?
> Cheers,
> -- Guido
For those interested, the bug is https://bugs.de
Marco d'Itri writes:
> But as it has been noted there is more than HTTP, so totally removing
> support for 1.0/1.1 may still not be appropriate.
Adding a data point here, my employer (Dropbox) is reasonably aggressive
about SSL configuration, but based on the usage we see, we've not yet been
com
Package: wnpp
Severity: wishlist
Owner: Debian Gajim Maintainers
* Package name: gajim-rostertweaks
Version : 0.6.3
Upstream Author : Denis Fomin
* URL :
https://dev.gajim.org/gajim/gajim-plugins/wikis/RosterTweaksPlugin
* License : GPL3+
Programming Lang:
On Fri, 11 Aug 2017 18:20:22 +0200, Sven Hartge
wrote:
>Christian Seiler wrote:
>> Don't get me wrong: I do believe it's a huge problem that vendors of
>> said appliances don't provide updates for these kind of things, and I
>> wish that we could indeed drop everything except TLS 1.2, but the rea
/me just realized he made a stupid mistake by grep'ing Packages instead
of Sources.
Approximate data based on grep'ing Sources:
- 452 teams maintaining packages in unstable
- 3 is the median number of packages maintained by a team
- 155 teams maintaining a single package
On Mon, Aug 07, 2017 at
Hi,
I have done some work for sensible-utils but I am a little stuck due
to lack of documentation/policy.
I want first to create desktop file for
sensible-editor/sensible-pager/sensible-browser in order to open from
firefox text file (fixing #780742).
The main problem is to exec this in a termin
Christian Seiler wrote:
> Don't get me wrong: I do believe it's a huge problem that vendors of
> said appliances don't provide updates for these kind of things, and I
> wish that we could indeed drop everything except TLS 1.2, but the real
> world is unfortunately more complicated, and I think De
Kurt Roeckx wrote:
> On Fri, Aug 11, 2017 at 01:34:53PM +0200, Sven Hartge wrote:
>> Marco d'Itri wrote:
>>> On Aug 09, Sven Hartge wrote:
>> >> Looking at https://developer.android.com/about/dashboards/index.html
>> >> there is still a marketshare of ~25% of smartphones based on Android
>> >>
On Fri, Aug 11, 2017 at 04:24:03PM +0200, Kurt Roeckx wrote:
> On Fri, Aug 11, 2017 at 08:41:10AM -0400, Wouter Verhelst wrote:
> > On Mon, Aug 07, 2017 at 08:35:52PM +0200, Kurt Roeckx wrote:
> > > On Mon, Aug 07, 2017 at 05:22:51PM +0200, Joerg Jaspert wrote:
> > > > I wonder if there is a middle
On Thu, Aug 10, 2017 at 9:56 PM, Niels Thykier wrote:
> Stefan Fritsch:
>> Hi,
>>
>> [...]
>>
>
> Hi,
>
> Thanks for improving dbgsym integration. :)
>
>> BTW, in some discussions some other questions were raised:
>>
>> - Is it really a good idea that foo-dbgsym depends on "foo (==
>> foo-version)
On Fri, Aug 11, 2017 at 08:41:10AM -0400, Wouter Verhelst wrote:
> On Mon, Aug 07, 2017 at 08:35:52PM +0200, Kurt Roeckx wrote:
> > On Mon, Aug 07, 2017 at 05:22:51PM +0200, Joerg Jaspert wrote:
> > > I wonder if there is a middle way that ensures that all new stuff does
> > > go TLS1.2 (or later,
Hi,
Am 2017-08-11 15:09, schrieb Sven Hartge:
Unless it has been proven that TLS1.0 and TLS1.1 are as broken as SSL3,
please keep the support for them enabled in OpenSSL, and just change
the
defaults in the application to only use TLS1.2 (unless changed by the
administrator).
I remember a ta
On Fri, Aug 11, 2017 at 01:34:53PM +0200, Sven Hartge wrote:
> Marco d'Itri wrote:
> > On Aug 09, Sven Hartge wrote:
>
> >> Looking at https://developer.android.com/about/dashboards/index.html
> >> there is still a marketshare of ~25% of smartphones based on Android
> >> 5.0 and 5.1 and 16% base
Package: wnpp
Severity: wishlist
Owner: Tom Marble
* Package name: shimdandy
Version : 1.2.0
Upstream Author : Toby Crawley
* URL : https://github.com/projectodd/shimdandy
* License : EPL
Programming Lang: Java
Description : Shim wrapping multiple Cloju
Marco d'Itri wrote:
> On Aug 11, Marco d'Itri wrote:
>> but I see on your link that Android pre-5.x still has a ~25% market
>> share, so unless it will drop a lot in the next year I do not think
>> that we can cut them off from Debian-based web servers.
> OTOH if the PCI council says that TLS <
On Aug 11, Marco d'Itri wrote:
> but I see on your link that Android pre-5.x still has a ~25% market
> share, so unless it will drop a lot in the next year I do not think that
> we can cut them off from Debian-based web servers.
OTOH if the PCI council says that TLS < 1.2 has to go by june 2018
On Mon, Aug 07, 2017 at 08:35:52PM +0200, Kurt Roeckx wrote:
> On Mon, Aug 07, 2017 at 05:22:51PM +0200, Joerg Jaspert wrote:
> > I wonder if there is a middle way that ensures that all new stuff does
> > go TLS1.2 (or later, whenever), but does allow older stuff still to
> > work. Which isnt the c
On Sun, Aug 06, 2017 at 01:27:49PM +0500, Andrey Rahmatullin wrote:
> On Sun, Aug 06, 2017 at 07:28:08AM +, Dr. Bas Wijnen wrote:
> > I can't think of a situation where you would not want it
> The "I don't want yet another thing that can cause subtle breakages and
> doesn't give me anything" si
Marco d'Itri wrote:
> On Aug 09, Sven Hartge wrote:
>> Looking at https://developer.android.com/about/dashboards/index.html
>> there is still a marketshare of ~25% of smartphones based on Android
>> 5.0 and 5.1 and 16% based on 4.4. So this change would (at the
>> moment) block ~40% of Android s
On Aug 09, Sven Hartge wrote:
> Looking at https://developer.android.com/about/dashboards/index.html
> there is still a marketshare of ~25% of smartphones based on Android 5.0
> and 5.1 and 16% based on 4.4. So this change would (at the moment) block
> ~40% of Android smartphones from connecting
22 matches
Mail list logo
