Vincent Bernat wrote...
> One of the package that I maintain (python-asyncssh) makes a DNS request
> during build and expects it to fail. Since Policy 4.9 forbids network
> access (in a rather confusing wording "may not"), I got this serious
> bug:
> https://bugs.debian.org/cgi-bin/bugreport.cgi?
On Wed, Sep 07, 2016 at 07:17:20AM +0200, Vincent Bernat wrote:
> The fix is easy: just disable the test.
>
> However, I have a hard time to find this useful for anyone. To sum up:
As a counterpoint, it's useful to prevent others from wondering why
the build attempts to access the network. In thi
On 09/07/2016 07:17 AM, Vincent Bernat wrote:
> One of the package that I maintain (python-asyncssh) makes a DNS request
> during build and expects it to fail. Since Policy 4.9 forbids network
> access (in a rather confusing wording "may not"), I got this serious
> bug:
> https://bugs.debian.org/c
Hey!
One of the package that I maintain (python-asyncssh) makes a DNS request
during build and expects it to fail. Since Policy 4.9 forbids network
access (in a rather confusing wording "may not"), I got this serious
bug:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=830568
The fix is easy:
> There's something I've been pondering for a while, along with some
> other folks - it might be useful to do a "jessie and a half" release,
> similarly to what we did in the etch days. That's *basically* just
> like a normal jessie release, but with a few key updates:
>
> * backports kernel
> *
On Tue, Sep 06, 2016 at 05:25:49PM -0400, Theodore Ts'o wrote:
> On Tue, Sep 06, 2016 at 02:29:56AM +0200, Zlatan Todorić wrote:
... and we're discussing all this on debian-devel because ... ?
--
Stefano Zacchiroli . z...@upsilon.cc . upsilon.cc/zack . . o . . . o . o
Computer Science Professor
On 06/09/2016 22:54, Thomas Pierson wrote:
> Should we create a collab account/project and start working from this?
Sorry I just read the message of Sean above. So Martin, keep me informed
when you see this with Alessio. And tell me if I need to contact him
directly too.
Regards,
Thomas Pierson
On Tue, Sep 06, 2016 at 02:29:56AM +0200, Zlatan Todorić wrote:
> You're just fueling myths you stand behind for some reason. You take
> data from one year (did you even verify it on your own?) and you don't
> look at historical development of situation.
The data was compiled primarily by Jon Corb
On 04/09/2016 12:57, Martin List-Petersen wrote:
> Seans suggestion to maybe maintain this in the collab git repository is
> a good idea. It makes sense, to have more than one maintainer working on
> this, so that we keep it updated more frequently and it doesn't end
> again, like it did right now.
Package: wnpp
Severity: wishlist
Owner: Julian Andres Klode
* Package name: sicherboot
Version : 0.1.0
Upstream Author : Julian Andres Klode
* URL : https://github.com/julian-klode/sicherboot
* License : MIT
Programming Lang: Shell
Description : Instal
Package: wnpp
Severity: wishlist
Owner: Boyuan Yang <073p...@gmail.com>
* Package name: qevercloud
Version : 3.0.2
Upstream Author : Dmitry Ivanov
* URL : https://github.com/d1vanov/QEverCloud
* License : MIT/X (Expat)
Programming Lang: C++
Description
Package: wnpp
Owner: Vincent Prat
Severity: wishlist
X-Debbugs-Cc:
debian-devel@lists.debian.org,debian-as...@lists.debian.org,debian-pyt...@lists.debian.org
* Package name: PyDL
Version : 0.5.2
Upstream Author : Benjamin Alan Weaver
* URL : https://github.com/weave
Package: wnpp
Severity: wishlist
* Package name: notepadqq
Version : 0.53.0
Upstream Author : Daniele Di Sarli
* URL : https://github.com/notepadqq/notepadqq
* License : GPL
Programming Lang: C++
Description : A lightweight text editor for developers
A
Robie,
there's exactly similar situation with libjpeg62. There's a default
libjpeg-dev package that depends on libjpeg62-turbo-dev
ondrej@yugen:~$ apt-file show libjpeg62-turbo
libjpeg62-turbo: /usr/lib/x86_64-linux-gnu/libjpeg.so.62
libjpeg62-turbo: /usr/lib/x86_64-linux-gnu/libjpeg.so.62.2.0
[.
14 matches
Mail list logo
