Package: wnpp
Severity: wishlist
Owner: Diane Trout
* Package name: pytest-expect
Version : 1.1.0
Upstream Author : Geoffrey Sneddon
* URL : https://github.com/gsnedders/pytest-expect
* License : Expat
Programming Lang: Python
Description : py.test plu
Package: wnpp
Severity: wishlist
Owner: Scott Kitterman
* Package name: django-simple-redis-admin
Version : 1.4.0
Upstream Author : Nicholas Serra
* URL : https://github.com/nicholasserra/django-simple-redis-admin
* License : BSD
Programming Lang: Python
D
Package: wnpp
Followup-For: Bug #838282
Owner: Robbie Harwood
Control: retitle -1 ITP: gssproxy -- A privilege separation daemon for GSSAPI
* Package name: gssproxy
Version : 0.5.1
Upstream Author : The GSS-PROXY contributors
* URL : https://fedorahosted.org/gss-proxy/
On Mon, Nov 14, 2016 at 07:10:00PM +, Niels Thykier wrote:
> Marco d'Itri:
> > On Nov 14, Lisandro Damián Nicanor Pérez Meyer wrote:
> >
> >> And yes, I would step back and switch libssl-dev to provide libssl1.0-dev
> >> and
> >> have libssl1.1-dev around for anyone who can really do the sw
Processing commands for cont...@bugs.debian.org:
> reassign 844315 general
Bug #844315 [tzdata] tzdata version breaks dist-upgrade leaving version from
oldstable security installed
Bug reassigned from package 'tzdata' to 'general'.
No longer marked as found in versions 2016i-0+deb7u1.
Ignoring re
On Mon, Nov 14, 2016 at 10:45:50AM -0300, Lisandro Damián Nicanor Pérez Meyer
wrote:
> And yes, I would step back and switch libssl-dev to provide libssl1.0-dev and
> have libssl1.1-dev around for anyone who can really do the switch.
That's the only viable alternative I see.
It looks like an in
Niels Thykier:
> Marco d'Itri:
>> On Nov 14, Lisandro Damián Nicanor Pérez Meyer wrote:
>>
>>> And yes, I would step back and switch libssl-dev to provide libssl1.0-dev
>>> and
>>> have libssl1.1-dev around for anyone who can really do the switch.
>> I would not: OpenSSL 1.0 does not support Cha
Package: wnpp
Severity: wishlist
Owner: Andreas Tille
* Package name: r-cran-rotl
Version : 3.0.1
Upstream Author : Francois Michonneau
* URL : https://cran.r-project.org/package=rotl
* License : BSD
Programming Lang: GNU R
Description : GNU R interfac
Marco d'Itri:
> On Nov 14, Lisandro Damián Nicanor Pérez Meyer wrote:
>
>> And yes, I would step back and switch libssl-dev to provide libssl1.0-dev
>> and
>> have libssl1.1-dev around for anyone who can really do the switch.
> I would not: OpenSSL 1.0 does not support ChaCha20 so it would be a
Ian Jackson wrote:
[...]
> I'm not a fan of the idea of merely adding 1 second per binnmu. That
> would mean that making a second binnmu correctly would involve looking
> in the archive to see what the previous binnmu timestamp was.
[...]
The reference point would be the last source change accor
There is a large number of packages currently build-depending on
openssl 1.0 explicitly.
Supporting dual-stack 1.0 & 1.1 openssl is a lot of work.
In Ubuntu, I have reverted the 1.1 migration, and forced 1.0 to be
used and provided by both libssl-dev & libssl1.0-dev packages.
This was done after a
Package: wnpp
Severity: wishlist
Owner: Lev Lamberov
* Package name: elpa-recursive-narrow
Version : 20140811.1546
Upstream Author : Nathaniel Flath
* URL : https://github.com/nflath/recursive-narrow
* License : GPL-3+
Programming Lang: Emacs Lisp
Descript
Hi,
thanks for having this discussion!
On Mon, Nov 14, 2016 at 06:10:57PM +0100, Johannes Schauer wrote:
> Quoting Ian Jackson (2016-11-14 17:33:55)
> > 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 s
Hi,
Quoting Ian Jackson (2016-11-14 17:33:55)
> Unless the timestamp is of the binnmu request, plumbing to try to get
> the same timestamp will be difficult.
>
> I'm not a fan of the idea of merely adding 1 second per binnmu. That
> would mean that making a second binnmu correctly would involve
Ondřej Surý writes:
> And this is happening all over places (apache2 vs php7.0) - I don't
> think we can have a partial transition. It's now all or nothing.
xml-security-c has not yet been ported to OpenSSL 1.1 upstream (which is
non-trivial), and we're now at an impasse in the Shibboleth suite
Johannes Schauer writes ("Re: [buildd-tools-devel] Bug#843773: Bug#843773:
misleading timestamps in binnmus"):
> I want to understand why passing the same timestamp to all
> architectures is an inferior solution to your proposal.
This is a sensible question. Thanks for helping to explore all the
On Nov 14, Lisandro Damián Nicanor Pérez Meyer wrote:
> And yes, I would step back and switch libssl-dev to provide libssl1.0-dev and
> have libssl1.1-dev around for anyone who can really do the switch.
I would not: OpenSSL 1.0 does not support ChaCha20 so it would be a very
bad default for nex
Hi,
Quoting Ian Jackson (2016-11-14 14:52:18)
>I don't think it is possible to make the binnmu timestamp the same
>across architectures. For example, a package might be rebuilt only
>on some architectures. I don't think we want to change that. In
>particular, even if we were pre
On Mon, Nov 14, 2016 at 10:45:50AM -0300, Lisandro Damián Nicanor Pérez Meyer
wrote:
> On lunes, 14 de noviembre de 2016 13:26:44 ART Ondřej Surý wrote:
> > And this is happening all over places (apache2 vs php7.0) - I don't
> > think we can have a partial transition. It's now all or nothing.
>
>
Package: wnpp
Severity: wishlist
Owner: Lev Lamberov
* Package name: elpa-iedit
Version : 0.9.9.9
Upstream Author : Victor Ren
* URL : https://github.com/victorhge/iedit
* License : GPL-3+
Programming Lang: Emacs Lisp
Description : edit multiple region
Johannes Schauer writes ("Re: [buildd-tools-devel] Bug#843773: Bug#843773:
misleading timestamps in binnmus"):
> Instead, file conflicts might be created from files with
> content that depends on SOURCE_DATE_EPOCH.
tl;dr:
Analysis. Revised proposal:
Introduce BUILD_DATE_EPOCH (= time of sb
On lunes, 14 de noviembre de 2016 13:26:44 ART Ondřej Surý wrote:
> And this is happening all over places (apache2 vs php7.0) - I don't
> think we can have a partial transition. It's now all or nothing.
I've said it before, I say it again: this transition should *not* have
happened at this point
On Sat, Nov 12, 2016 at 07:58:33PM +, Mattia Rizzolo wrote:
> On Sat, Nov 12, 2016 at 08:55:43PM +0100, Michael Biebl wrote:
> > Am 12.11.2016 um 19:17 schrieb Guillem Jover:
> > > Control: severity 843073 important
> >
> > > Ok, Mattia Rizzolo tells me (thanks!) that it's actually twice per
>
And this is happening all over places (apache2 vs php7.0) - I don't
think we can have a partial transition. It's now all or nothing.
Cheers,
--
Ondřej Surý
Knot DNS (https://www.knot-dns.cz/) – a high-performance DNS server
Knot Resolver (https://www.knot-resolver.cz/) – secure, privacy-aware,
f
Am 14.11.2016 um 12:22 schrieb Raphael Hertzog:
> Please find two patches attached.
>
> I checked that the command below was failing with the current dpkg-dev
> and it did no longer fail with the updated one.
>
> $ sbuild -d sid --add-depends=usrmerge --chroot-setup-commands="sed -i
> 's#^/usr#
Control: tag -1 + patch
Control: severity -1 serious
Hi Guillem,
On Sun, 13 Nov 2016, Guillem Jover wrote:
> > The /usr merge violates core assumptions in dpkg-shlibdeps. The reason
> > that amd64 isn't broken is sheer luck.
> > /etc/ld.so.conf.d/x86_64-linux-gnu.conf lists /lib before /usr/lib,
Package: wnpp
Severity: wishlist
Owner: Pirate Praveen
X-Debbugs-CC: debian-devel@lists.debian.org
* Package name: node-nodeunit
Version : 0.10.2
Upstream Author : Caolan McMahon
* URL : https://github.com/caolan/nodeunit#readme
* License : Expat
Programming
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
Am Sonntag, den 06.11.2016, 01:12 -0200 schrieb Henrique de Moraes
Holschuh:
>
>
>
> Unfortunately, when hardware lock elision support was added to glibc
> upstream, libpthreads was *not* changed to properly assert() this
> forbidden condition on the non-hardware-elision codepaths. Such an
> as
29 matches
Mail list logo