On Tue, Jan 04, 2005 at 05:31:26PM +0100, Thomas Jollans wrote:
> stuff. If I needed something more production-ready, I'd use testing
> because you have (almost) garantee that the software will work and you
> will have security updates, too. (But not in the same quality as
Unfortunately, testin
On Thu, Jan 06, 2005 at 09:51:21AM +0100, Marc Haber wrote:
> That would leave testing users who happen to have such a package
> installed alone because they wouldn't notice their package vanishing
> from the mirrors, continuing to use a potentially vulnerable package.
Good point. But that problem
On Tue, Mar 15, 2005 at 05:39:37PM +0100, Frank Lichtenheld wrote:
> So where is the lack of communication you detected?
Well, at least to me it's completely unclear why it took so long to
address the points you mentioned (t-s, d-i). There are probably very good
reasons, and people did work hard t
On Thu, Mar 24, 2005 at 12:59:19AM -0800, Blars Blarson wrote:
> Release candidate architecture:
>
> * testing managed by port release manager(s)
> * testing consists of packages that built on the candidate and
> are in release architecture testing with the same version
Please specify what appl
On Thu, Dec 18, 2008 at 04:45:02PM +1100, Russell Coker wrote:
> It seems that the grass-roots support for doing something quite different to
> the current vote includes me, Brian, and quite a few bloggers on Planet
> Debian.
I don't like the current vote either and wouldn't mind if it was
cance
Package: wnpp
Severity: wishlist
Owner: Jan Niehusmann <[EMAIL PROTECTED]>
* Package name: qca2-plugin-ossl
Version : 0.1~20070706
Upstream Author : Justin Karneges <[EMAIL PROTECTED]>, Brad Hards <[EMAIL
PROTECTED]>
* URL : http://del
Package: wnpp
Severity: wishlist
* Package name: qca
Version : not yet released, currently CVS only
Upstream Author : Justin Karneges <[EMAIL PROTECTED]>
* URL : http://psi.affinix.com/
* License : LGPL
Description : The Qt Cryptographic Architecture (QCA)
On Fri, Oct 22, 2004 at 10:20:51AM +0200, Jérôme Marant wrote:
> Debian developers, on the contrary, run unstable and rarely run
> testing, which means that they don't really know about the shape
> of what they release.
I would immediately upgrade at least one, probably more, woody machines
to sar
On Sun, Dec 01, 2002 at 08:43:06PM +0100, Russell Coker wrote:
> When you have a very small number of people doing something totally contrary
> to what everyone else on the Internet is doing, and expecting that everyone
> else should go out of their way to accomodate them, then you don't need to
On Mon, Dec 02, 2002 at 04:58:48PM +0100, Russell Coker wrote:
> On Mon, 2 Dec 2002 16:39, Jan Niehusmann wrote:
> > Time will tell. I fear that some day, the only way to use email
> > productively is to block all email with invalid sender adresses. And I
> If an auto-respond
On Mon, Dec 02, 2002 at 08:18:46AM -0800, Stephen Zander wrote:
> The above is based on the false premise that those who send spam are
> incapable of sending it with (forged) real email addresses. They
> already have lots of them to choose from.
But if they send the spam with a forged email addre
On Wed, Dec 04, 2002 at 02:25:43PM +0100, Joerg Friedrich wrote:
> and the other htb-based. cbq is no longer developped, but tc from
> iproute does not support htb.
Well, according to the changelog, tc does support htb, but it's probably
based on htb2 and 2.4.20 contains htb3, which seems to be in
I'd say a package wich only works with a recent kernel version is not a
problem. Add a note to the description, and let the program detect
availability of the necessary features at runtime, with a meaningfull
error message if the feature is missing.
By the way, the iproute package just got updated
On Sun, Apr 20, 2003 at 06:19:28PM -0400, Glenn Maynard wrote:
> Remember, the issue here isn't whether there's good reason to remove the
> Reiser message, but whether we're allowed to (apparently not) and
> whether not being allowed to do so is DFSG-free. Even if we were happy
> with simply putti
Is there a mixer available that supports the advanced mixing features
of the emu10k1 chip (found on Soundblaster Live) ?
The only one I know is 'dm', a little but very usefull command line
tool. As it's not yet in debian, I will ITP it if there are no
alternatives.
There is another point I'm not
On Wed, Jan 02, 2002 at 11:00:58AM -0900, Christopher S. Swingley wrote:
> > A quick search of the debian-devel archive didn't turn up
> > anything about this, but I might have goofed the search.
> > Anyway, mutt-1.3.24-2 works well enough for me, but 1.3.24-3
> > won't let me modify /var/mail/foo.
Hi!
Is there a reason why the Release.gpg files for testing and unstable are
empty?
I'm using the Wichert's script to check the integrity of the local
mirror, but at the moment this is not possible because auf the missing
signature.
Jan
On Mon, Jan 14, 2002 at 03:30:45PM +0100, Jan Niehusmann wrote:
> I'm using the Wichert's script to check the integrity of the local
Sorry, wrong attribution - of course, the script is written by Anthony
Towns.
On Mon, Jan 14, 2002 at 05:51:39PM +0100, Martin Schulze wrote:
> Jan Niehusmann wrote:
> > Is there a reason why the Release.gpg files for testing and unstable are
> > empty?
>
> A bug on your end of the pipe?
>
> auric!joey(pts/0):/org/ftp.debian.org/inco
Hi!
Can anybody tell me why the psi package in queue/new doesn't get
processed? I made an upload which only changed 'non-US' to 'net' nearly
three weeks ago. (I added another upload with new features last week)
If there is anything wrong with this package, please tell me, so I can
correct it.
Ja
On Mon, Apr 15, 2002 at 09:29:10PM +1000, Anthony Towns wrote:
> ] Build-Depends: debhelper (>> 3.0.0), tmake, libqt3-mt-dev, libssl-dev
> ^^
> OpenSSL can't be used with GPL licensed software.
The psi binary package doesn't cont
Hi,
due to bug #736066, encfs was removed from jessie.
I'd think it would be better to allow encfs into jessie for the
following reasons:
The bug report is about security issues, but these are not security
issues of the software (as in: you can somehow hack into the computer
wich is running the
Hi Holger,
On Thu, Sep 11, 2014 at 06:42:32PM +0200, Holger Levsen wrote:
> I (probably too briefly) skimmed though the bug report, but couldn't find a
> usecase where an encrypted filestem container with broken crypto could be
> useful. Could you elaborate, please?
As far as I understand the E
Package: wnpp
Severity: wishlist
Owner: Jan Niehusmann
* Package name: condure
Version : 1.1.0
Upstream Author : Justin Karneges
* URL : https://github.com/fanout/condure/
* License : Apache-2.0
Programming Lang: Rust
Description : HTTP/WebSocket
Hi,
On Fri, Nov 04, 2016 at 11:58:44PM +0200, Adrian Bunk wrote:
> You could enforce that no Qt-using package uses the wrong OpenSSL by
> adding libssl1.0-dev dependencies to libqt4-dev and qtbase5-dev.
How can I handle the case of a package which uses both qt and curl? The
latter already switch
Hi,
(Cc to Alessandro because this causes issues with libcurl)
On Wed, Nov 02, 2016 at 09:15:13PM +0100, Kurt Roeckx wrote:
> I don't think having libssl1-1-dev vs libssl1.0-dev is going to
> make much differences in the end. The build conflicts will always
> have to be sorted out.
Well I think
On Fri, Nov 11, 2016 at 03:15:09PM +0100, Kurt Roeckx wrote:
> At least something like that also came up with xmltooling.
> It's probably caused by this:
> curl_easy_setopt(easy, CURLOPT_SSL_CTX_FUNCTION, &sslCtxFunction_cb);
>
> You get an SSL_CTX from OpenSSL 1.1 and you call an OpenSSL 1.0
> fu
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
On Tue, Nov 15, 2016 at 10:43:07AM -0300, Lisandro Damián Nicanor Pérez Meyer
wrote:
> On lunes, 14 de noviembre de 2016 22:16:25 ART Jan Niehusmann wrote:
> [snip]
> > (It's fine if packages which depend on libssl-dev get an RC-bug if they
> > can't be compiled with
Hi,
On Mon, Nov 21, 2016 at 11:11:09AM +0100, Tino Mettler wrote:
> At the end I noticed that Qt will stay at 1.0 (by glancing into the
> changelog of the relevant upload) which means that my package also has
> to to stay at 1.0 and the whole excitement resulted in just a changed
> build-dep.
I'm
On Thu, Nov 24, 2016 at 03:59:10PM +0200, Adrian Bunk wrote:
> If inspection is not easily possible, then adding a dependency on
> libssl1.0-dev to qtbase5-private-dev should be sufficient to
> ensure that this is not leaked to a different OpenSSL version.
I see two disadvantages:
1) doesn't cat
On Thu, Nov 24, 2016 at 07:23:22PM +0200, Adrian Bunk wrote:
> If both b-dev and c-dev would depend on the libssl*-dev they use,
Which is not always the case, now.
qtbase5-private-dev exposes lots of internal OpenSSL structures, but
doesn't depend on any OpenSSL package.
libcurl4-openssl-dev onl
On Fri, Nov 25, 2016 at 01:56:19AM +0400, Stepan Golosunov wrote:
> qsslsocket_openssl_symbols.cpp also tries to load any libssl.* it can
> find (in directories gathered from dl_iterate_phdr) when it cannot
> find libssl.so.. This asks for trouble when
> libssl1.0.2 is not installed and probably n
Package: wnpp
Severity: wishlist
Owner: Jan Niehusmann
* Package name: tnetstring3
Version : 0.3.1
Upstream Author : Carlo Pires
* URL : https://pypi.python.org/pypi/tnetstring3
* License : MIT
Programming Lang: Python / C
Description : python3
34 matches
Mail list logo
