Package: wnpp
Severity: wishlist
Owner: Scott Kitterman
* Package name: python-sparkpost
Version : 1.3.2
Upstream Author : SparkPost
* URL : https://github.com/SparkPost/python-sparkpost
* License : Apache 2.0
Programming Lang: Python
Description : Spa
On Wednesday, November 16, 2016 10:04:00 PM Lisandro Damián Nicanor Pérez
Meyer wrote:
> On jueves, 17 de noviembre de 2016 00:40:42 ART Kurt Roeckx wrote:
> > On Mon, Nov 14, 2016 at 07:10:00PM +, Niels Thykier wrote:
> > > The alternative for ChaCha20 would be to adopt Cloudflare's patches[1
On jueves, 17 de noviembre de 2016 00:40:42 ART Kurt Roeckx wrote:
> On Mon, Nov 14, 2016 at 07:10:00PM +, Niels Thykier wrote:
> > The alternative for ChaCha20 would be to adopt Cloudflare's patches[1],
> > but that sort of assumes that you are only interested in openssl 1.1 for
> > ChaCha20 (
On Mon, Nov 14, 2016 at 07:10:00PM +, Niels Thykier wrote:
>
> The alternative for ChaCha20 would be to adopt Cloudflare's patches[1],
> but that sort of assumes that you are only interested in openssl 1.1 for
> ChaCha20 (and not the other changes).
I'm not willing to maintain such a patch.
On 2016-11-16 12:26:55 [+], Ian Jackson wrote:
> If we decide to wind back the transition and the openssl maintainers
> continue not to be available (within the short timeframes required),
> we have a lot of people who could competently prepare an NMU.
NMU openssl back to 1.0.2 or its rdeps to
On 2016-11-16 19:49:44 [+0200], Adrian Bunk wrote:
> The problem are not specific bugs, the problem is the whole size of the
> problem:
>
> 1. Sorting out what packages have to stay at 1.0.2
> The majority of OpenSSL-using packages in stretch might end up
> using 1.0.2 - sorting this out is part
Adam D. Barratt wrote...
> britney has never considered build-dependencies (that's #145257). This
> is one of several reasons for periodic rebuilds of testing.
Oy. While this is rather unfortunate, I bet there's a reason why
this never got fixed in all the years.
Thanks for sharing the wisdom of
On Wed, Nov 16, 2016 at 07:57:18PM +, Adam D. Barratt wrote:
> On Wed, 2016-11-16 at 20:49 +0100, Christoph Biedl wrote:
> > Hello,
> >
> > two days ago, syslog-ng 3.8.1-5 migrated to testing. However, as this
> > package build-depends on libssl1.0-dev which is available in unstable
> > only a
On Wed, 2016-11-16 at 20:49 +0100, Christoph Biedl wrote:
> Hello,
>
> two days ago, syslog-ng 3.8.1-5 migrated to testing. However, as this
> package build-depends on libssl1.0-dev which is available in unstable
> only at the moment, it cannot be rebuild in testing.
[...]
> So, does anybody else
Ofertas Pague Menos
body {
margin-left: 0px;
margin-top: 0px;
margin-right: 0px;
margin-bottom: 0px;
text-align: center;
font-family: Arial, Helvetica, sans-serif;
font-size: 12px;
}
Hello,
two days ago, syslog-ng 3.8.1-5 migrated to testing. However, as this
package build-depends on libssl1.0-dev which is available in unstable
only at the moment, it cannot be rebuild in testing.
Please note my only interested in understanding this from a general
point, not about the particul
Ian Jackson:
> Ian Jackson writes ("Re: OpenSSL 1.1.0"):
> [...]
>
> I was not able to find the message where the release team gave
> permission for the upload of openssl 1.1.x (in particular, the new
> version of libssl-dev) to unstable, that started the transition. [...]
>
> [...]
>
> Ian.
>
On Wed, Nov 16, 2016 at 12:15:39AM +0100, Sebastian Andrzej Siewior wrote:
> On 2016-11-15 00:16:14 [+0200], Adrian Bunk wrote:
> > And since 80% of all OpenSSL-using packages in unstable are still
> > using libssl1.0.2 (binNMUs have not yet happened), all runtime
> > issues observed so far are onl
Jonathan Wiltshire writes ("Re: OpenSSL 1.1.0"):
> On 2016-11-16 12:26, Ian Jackson wrote:
> > If we are going to wind back on this change we should do it ASAP. We
> > should not allow ourselves to make the decision to press on, simply by
> > failing to decide otherwise.
>
> Indeed it's been unde
Ian Jackson writes:
> Reading that bug I think it's a shame that we didn't manage to
> effectively identify the issues we've now discussed here on -devel
> earlier, despite Kurt's several messages to d-d-a.
Concerns were already raised in June, in the subthread starting here:
https://lists.debia
On Mon, Nov 14, 2016 at 03:37:00PM +0100, Adam Borowski wrote:
> Another issue: 1.0.2 is a LTS, supported until 2019-12-31, while 1.1.0 a
> short-lived release with upstream support only until 2018-08-31.
Hmm... a different interpretation of these two data points:
Stretch's EOL is projected for M
On 2016-11-16 12:26, Ian Jackson wrote:
In the absence of input from the openssl maintainers, I would like to
ask the Release Team's opinion.
If we are going to wind back on this change we should do it ASAP. We
should not allow ourselves to make the decision to press on, simply by
failing to de
Ian Jackson writes ("Re: OpenSSL 1.1.0"):
> Ian Jackson writes ("Re: OpenSSL 1.1.0"):
> > Lots of people have posted in this thread that they see problems with
> > our current approach to the openssl transition.
> >
> > Do the openssl maintainers have an response ?
...
> In the absence of input fr
Stephan Seitz wrote:
> And there is still the problem that 1.1.0 is not supported as long as the
> available LTS version.
That's not a decisive factor, Debian security support has been extended
over the upstream support time frame many times before.
Cheers,
Moritz
Package: wnpp
Severity: wishlist
Owner: Mike Gabriel
* Package name: curry-base
Version : 0.4.1
Upstream Author : Michael Hanus
* URL : https://git.ps.informatik.uni-kiel.de/curry/curry-base/
* License : BSD-3-clause
Programming Lang: Haskell
Description
On Mi, Nov 16, 2016 at 02:31:28 +0100, Marco d'Itri wrote:
ChaCha20 is hardly obscure: if it is to you then I fear that your
opinion on this issue is not informed enough to be useful.
It doesn’t matter in the end.
If no one wants to delay the next release until all applications support
OpenSS
On Nov 16, Pau Garcia i Quiles wrote:
> * Some obscure feature (e. g. BlaBla20) may be missing or be difficult
> to support on a limited number of packages (e. g. apache2)
ChaCha20 is hardly obscure: if it is to you then I fear that your
opinion on this issue is not informed enough to be useful.
On Wed, Nov 16, 2016 at 1:58 PM, Pau Garcia i Quiles
wrote:
[...]
> OpenSSL 1.0 only
> =
[...]
> * Some obscure feature (e. g. BlaBla20) may be missing or be difficult
> to support on a limited number of packages (e. g. apache2)
[...]
Sorry, it's ChaCha20, not BlaBla20. My bad.
--
On Wed, Nov 16, 2016 at 1:26 PM, Ian Jackson
wrote:
> A maintainer should be ready to explain, and if necessary change,
> decisions they have taken. (Ideally wider consultation before taking
> such a decision would be better.)
>
> In the absence of input from the openssl maintainers, I would lik
Ian Jackson writes ("Re: OpenSSL 1.1.0"):
> Lots of people have posted in this thread that they see problems with
> our current approach to the openssl transition.
>
> Do the openssl maintainers have an response ?
I count the following people who expressed concern[1] about this some
time before t
Hi,
Quoting Holger Levsen (2016-11-14 18:25:34)
> To me it seems a binNMU should change SOURCE_DATE_EPOCH, as debian/changelog
> gets modified by changelog.$arch, so it's actually a different source which
> is being build.
debian/changelog doesn't get modified by changelog.$arch. The latter is
ge
Package: wnpp
Severity: wishlist
Owner: Martin Kratochvil
* Package name: python-geoip2
Version : 2.4.0
Upstream Author : MaxMind, Inc.
* URL : https://github.com/maxmind/GeoIP2-python
* License : Apache-2
Programming Lang: Python
Description : Python
Am Dienstag, den 15.11.2016, 18:06 +0200 schrieb Adrian Bunk:
>
> > Unfortunately, in current unstable with thread sanitizer one might
> > get #796246 (at least I had this).
>
> Does "-fsanitize=thread -no-pie" work for you?
Indeed, that fixed the problem with g++-6.2 (g++-5.4 doesn't has this
p
Hi,
On Mon, 14 Nov 2016, Johannes Schauer wrote:
> > Can I ask you the converse question: what same-timestamp proposal do
> > you think is best and why ?
>
> I found Guillem's suggestion the most sensible and as far as I understand the
> matter also the easiest to implement:
>
> Quoting Guillem
html {width: 100%}
body {background-color: #ff; margin: 0px; padding: 0px; font-family: Arial,
Helvetica, sans-serif;}
Caso não esteja visualizando as imagens, acesse aqui
Package: wnpp
Severity: wishlist
Owner: Martin Kratochvil
* Package name: python-maxminddb
Version : 1.2.1
Upstream Author : MaxMind, Inc.
* URL : https://github.com/maxmind/MaxMind-DB-Reader-python
* License : Apache-2
Programming Lang: Python
Description
31 matches
Mail list logo
