Package: wnpp
Severity: wishlist
Owner: "ChangZhuo Chen (陳昌倬)"
* Package name: python-bitbucket-api
Version : 0.5.0
Upstream Author : Name
* URL : https://github.com/Sheeprider/BitBucket-api
* License : ISC
Programming Lang: Python
Description : librar
Hello,
since tha update on thursday I can't use GPG on Stretch.
There is gpg version 2.1.15-4.
Unter Jessie all things are fine with gpg 1.4.18
Unter Stretch I have no access to my private key and the public keyring.
I only see the keys which incomes with the mails after the update
What happen
On Sat, 15 Oct 2016, Mechtilde wrote:
> There is gpg version 2.1.15-4.
> Unter Jessie all things are fine with gpg 1.4.18
>
> Unter Stretch I have no access to my private key and the public keyring.
> I only see the keys which incomes with the mails after the update
>
> What happens? The files of
Lots of this discussion has been focusing on the test suite process
leak problem. But there are actually three separate use cases which
need something along the lines of my proposal; two of which are
regressions from gnupg1.
1. gnupg1-compatible authorisation lifetime:
Command line use of gpg b
... at least not for boost.
I downloaded the latest release manually by following the links from boost.org
to https://sourceforge.net/projects/boost/files/boost/1.62.0/
boost_1_62_0.tar.bz2/download
Then I remembered that Dimitri had written a watch file to use the Files-
Excluded facility. So
Howdy -devel,
It's that time of the year again - that's right, another paultag rant
with some grand ideas about the state of the world.
It seems like every month or so, someone pops into a channel and asks
why we aren't using https on our mirrors. This well-meaning question is
usually met with h
On 15 October 2016 at 18:47, Steve M. Robbins wrote:
> ... at least not for boost.
>
> I downloaded the latest release manually by following the links from boost.org
> to https://sourceforge.net/projects/boost/files/boost/1.62.0/
> boost_1_62_0.tar.bz2/download
>
Yes, this is known to me, but I d
On 15 October 2016 at 19:03, Paul Tagliamonte wrote:
>
> So, the real question:
>
> So, when are we going to push this? If not now, what criteria need to be
> met? Why can't we https-ify the default CDN mirror today?
>
It is my understanding that in 2016 there is a huge difference between
the fol
There's nothing stopping mirror operators from enabling HTTPS. Some of them
actually have done it already:
https://crt.sh/?q=ftp%25.%25.debian.org
(and there's more in non-*.debian.org domains)
We should have an official list of HTTPS mirrors, and encourage more operators
to enable it.
On a s
]] Paul Tagliamonte
> So, when are we going to push this? If not now, what criteria need to
> be met? Why can't we https-ify the default CDN mirror today?
The usual crypto answer: because key handling is hard.
Doing this for the per-country mirrors means that repointing mirrors
becomes a lot ha
Package: wnpp
Severity: wishlist
Owner: Evgeni Golov
* Package name: ansible-tower-cli
Version : 3.0.1
Upstream Author : Luke Sneeringer
* URL : https://github.com/ansible/tower-cli
* License : Apache 2.0
Programming Lang: Python
Description : command
On Sat, Oct 15, 2016 at 12:47:21PM -0500, Steve M. Robbins wrote:
> Notice the crucial difference: the reflector is using
> "boost/snapshots/master"
> whereas the correct URL uses "boost/1.62.0". The snapshots are pulled from
> the branch tip and are NOT actual releases. So the reflector is l
Package: general
Severity: normal
Hello,
I dusted off a notebook with hardware serial port which also happens to have a
Mach64 graphics card.
Accidentally during system upgrade an extra display manager was installed which
broke the text console. Running two X servers without KMS is problematic.
On Oct 15, Dimitri John Ledkov wrote:
> I believe the TLS overhead costs are negligible, especially if one
This is not about the TLS overhead: the real issue is not being able to
use sendfile(2).
> uses ECC keys. The further privacy it buys one, is IMHO, well worth
> the effort. I would be in f
On Sat, Oct 15, 2016 at 09:24:15PM +0200, Jakub Wilk wrote:
> Some of ftp*.*.d.o and cdimage.d.o mirrors serve random free (and sometimes
> non-free) software that is not Debian[*]. This may mislead inexperienced
> people into thinking that this software is endorsed or even produced by
> Debian. Sh
Marco d'Itri wrote:
> On Oct 15, Dimitri John Ledkov wrote:
> > I believe the TLS overhead costs are negligible, especially if one
> This is not about the TLS overhead: the real issue is not being able to
> use sendfile(2).
If you really want to use sendfile (or splice or vmsplice) for your TLS
c
On Sun, Oct 16, 2016 at 1:47 AM, Steve M. Robbins wrote:
> Who can I contact to get https://qa.debian.org/watch/sf.php/boost/ fixed?
These days the reflector is just a proxy for the sourceforge RSS feeds:
https://sourceforge.net/projects/boost/rss?limit=1000
So check if the issu
On Sun, Oct 16, 2016 at 2:03 AM, Paul Tagliamonte wrote:
> So, when are we going to push this? If not now, what criteria need to be
> met? Why can't we https-ify the default CDN mirror today?
Exactly what actions do you mean by this?
Debian does not control what mirror operators do, they are fre
On Sun, Oct 16, 2016 at 3:25 AM, Tollef Fog Heen wrote:
> Doing this for the per-country mirrors means that repointing mirrors
> becomes a lot harder than it currently is, and this is something we do
> on a daily basis. We'd need a solution for deploying the TLS cert for,
> say, ftp.de.d.o to ftp
On Sunday, October 16, 2016, Tollef Fog Heen wrote:
> ]] Paul Tagliamonte
>
> > So, when are we going to push this? If not now, what criteria need to
> > be met? Why can't we https-ify the default CDN mirror today?
>
> The usual crypto answer: because key handling is hard.
>
> Doing this for the
On Sunday, October 16, 2016, Paul Wise wrote:
> On Sun, Oct 16, 2016 at 3:25 AM, Tollef Fog Heen wrote:
>
> > Doing this for the per-country mirrors means that repointing mirrors
> > becomes a lot harder than it currently is, and this is something we do
> > on a daily basis. We'd need a solution
Package: wnpp
Severity: wishlist
Owner: Giovani Augusto Ferreira
* Package name: winregfs
Version : 0.6
Upstream Author : Jody Bruchon
* URL : https://github.com/jbruchon/winregfs
* License : GPL-2
Programming Lang: C
Description : Windows registry FUS
Howdy all,
I am preparing a new version of ‘dput’ that stops using ‘/usr/bin/gpg’,
and instead uses the GPGME library for GnuPG operations.
Currently, as of ‘dput’ version 0.10, GnuPG operations are done by
invoking the ‘/usr/bin/gpg’ command in a subprocess. This is fragile in
several ways, not
On Sunday, October 16, 2016, Aron Xu wrote:
>
>
> On Sunday, October 16, 2016, Paul Wise > wrote:
>
>> On Sun, Oct 16, 2016 at 3:25 AM, Tollef Fog Heen wrote:
>>
>> > Doing this for the per-country mirrors means that repointing mirrors
>> > becomes a lot harder than it currently is, and this is
On Sun, Oct 16, 2016 at 2:49 AM, Dimitri John Ledkov wrote:
> Yes, this is known to me, but I did not report. The redirector /
> sourceforge make it hard to distinct identically named files in
> different subfolders unfortunately.
This was a bug in the redirector, I've added additional links
cont
Package: wnpp
Severity: wishlist
Owner: "ChangZhuo Chen (陳昌倬)"
* Package name: python-github3.py
Version : 0.9.3
Upstream Author : Ian Cordasco (sigmavirus24)
* URL : https://github.com/sigmavirus24/github3.py
* License : BSD-3-clause
Programming Lang: Python
On 15 October 2016 at 20:25, Tollef Fog Heen wrote:
> ]] Paul Tagliamonte
>
>> So, when are we going to push this? If not now, what criteria need to
>> be met? Why can't we https-ify the default CDN mirror today?
>
> The usual crypto answer: because key handling is hard.
>
> Doing this for the per
Package: wnpp
Severity: wishlist
Owner: Sruthi Chandran
X-Debbugs-CC: debian-devel@lists.debian.org
* Package name: node-buffer-equal
Version : 1.0.0
Upstream Author : James Halliday (http://substack.net)
* URL : https://github.com/substack/node-buffer-equal
* License
Package: wnpp
Severity: wishlist
Owner: Daniel Silverstone
* Package name: tongue
Version : 0.8
Upstream Author : Daniel Silverstone
* URL : https://git.gitano.org.uk/tongue.git
* License : BSD
Programming Lang: Lua
Description : Lua I18N library 'Tong
Package: wnpp
Severity: wishlist
Owner: Sruthi Chandran
X-Debbugs-CC: debian-devel@lists.debian.org
* Package name: node-string-decoder
Version : 0.10.31
Upstream Author : FIX_ME upstream author
* URL : https://github.com/rvagg/string_decoder
* License : Expat
]] Dimitri John Ledkov
> I'm not a sysadmin. My naive approach would be to have cname specified
> on the certs that are subject to redirect. E.g. ftp.d.o should have
> cname's for all country codes, such that any country mirror can fall
> back to ftp.d.o.
This would restrict us to always point a
]] Aron Xu
> To make it clear, content delivery systems used by pypi and npm don't
> work for many people in China because:
>
> 1) Major global CDN providers don't have decent services in the
> country (except akamai and cloudflare but need special contract);
>
> 2) BGP based network topology d
32 matches
Mail list logo
