Le 7/09/2016 à 07:17, Vincent Bernat a écrit :
> Any thoughts?
I agree with you, if the network access has no impact on the build and
doesn't leak sensitive data it should be acceptable.
This rule appeared in the version 3.9.7 of the policy. Just declare in
debian/control that your package confo
On Wed, Sep 07, 2016 at 09:29:53AM +0200, Emmanuel Bourg wrote:
> This rule appeared in the version 3.9.7 of the policy. Just declare in
> debian/control that your package conforms to the version 3.9.6 and the
> issue will no longer be a RC policy violation ;)
That's not how policy compliance actu
Package: wnpp
Severity: wishlist
Owner: Andreas Tille
* Package name: rapmap
Version : 0.3.0
Upstream Author : COMputational BIology and Network Evolution lab
* URL : https://github.com/COMBINE-lab/RapMap
* License : GPL
Programming Lang: C
Description
On 09/07/2016 07:43 AM, Christian Seiler wrote:
> However, instead of disabling the test via a patch, [...]
Yet another solution would be to upstream a patch that adds the
@unittest.skipIf(os.getenv('TESTS_NO_NETWORK_ACCESS') == '1',
'No network access allowed in test suite')
de
On Wed, Sep 7, 2016 at 1:17 PM, 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.deb
* Christian Seiler , 2016-09-07, 07:43:
And, even better, IF there is a host name called 'fail' on the local
network
...or when your ISP hijacks all NXDOMAIN responses...
, using nss_wrapper the package build will still succeed.
--
Jakub Wilk
Hi!
On Wed, 2016-09-07 at 08:41:19 +0200, Christoph Biedl wrote:
> 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"),
On Tue, Sep 06, 2016 at 09:00:37AM +0200, Ondřej Surý wrote:
> So again I urge you to revert the decision to introduce yet another
> change in the Build-Depends for >= 300 packages and just use the
> libmysqlclient-dev package to be the "default".
Sorry, I disagree. The situation with MariaDB need
On Wed, Sep 7, 2016 at 6:06 PM, Guillem Jover wrote:
> On Wed, 2016-09-07 at 08:41:19 +0200, Christoph Biedl wrote:
>> Now the funny question: Does traffic on the loopback interface count
>> as network access? A daemon started during build to run tests is
>> certainly okay. What about traffic to ot
Robie,
I have no idea why are you talking about -compat packages and mariadb
shipping libmysqlclient.
The initial email stated:
> Packages built against default-mysqlclient-dev and link using
> "-lmysqlclient" will end up with a shared library dependency on either
> libmysqlclient.so.X or libmar
Package: wnpp
Severity: wishlist
Owner: Christos Trochalakis
* Package name: python-confluent-kafka
Version : 0.9.1.2
Upstream Author : Magnus Edenhill
* URL : https://github.com/confluentinc/confluent-kafka-python
* License : Apache-2.0
Programming Lang: Pyth
Vincent Bernat writes ("Network access during build"):
> The fix is easy: just disable the test.
>
> However, I have a hard time to find this useful for anyone. To sum up:
>
> - patching the test suite requires maintaining the patch forever
If it is hard to maintain such a trivial patch forever
On 09/07/2016 07:43 AM, Christian Seiler wrote:
> 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
On 09/07/2016 07:17 AM, Vincent Bernat wrote:
> 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.de
On 09/07/2016 01:14 PM, Christos Trochalakis wrote:
> Package: wnpp
> Severity: wishlist
> Owner: Christos Trochalakis
>
> * Package name: python-confluent-kafka
> Version : 0.9.1.2
> Upstream Author : Magnus Edenhill
> * URL : https://github.com/confluentinc/confluent-
On Wed, Sep 7, 2016 at 9:07 PM, Thomas Goirand wrote:
> This seem a pretty good solution to the problem. Could you show an
> example in a package that does that, or maybe a patch for this kind of
> bug that Lamby opened?
build-rdeps says that varnish-modules and sssd use nss-wrapper.
--
bye,
pa
Package: wnpp
Severity: wishlist
Owner: "Iain R. Learmonth"
* Package name: powerline-taskwarrior
Version : 0.1
Upstream Author : German Lashevich
* URL : https://github.com/Zebradil/powerline-taskwarrior
* License : MIT
Programming Lang: Python
Description
Hello Thomas,
On Wed, Sep 07, 2016 at 03:17:31PM +0200, Thomas Goirand wrote:
On 09/07/2016 01:14 PM, Christos Trochalakis wrote:
Package: wnpp
Severity: wishlist
Owner: Christos Trochalakis
* Package name: python-confluent-kafka
Version : 0.9.1.2
Upstream Author : Magnus Edenhi
On 08/30/2016 12:09 PM, Zlatan Todorić wrote:
> I don't know is it a time for GPLv4 which will explain to all
> corporations that THIS LICENSE mean you must participate with community
> and also make people aware that it is not only license but movement
> towards better humanity that cooperates all
Package: wnpp
Severity: wishlist
Owner: Andreas Tille
* Package name: metaphlan2-data
Version : 2.6.0
Upstream Author : Duy Tin Truong, Nicola Segata and Curtis Huttenhower
* URL : https://bitbucket.org/biobakery/metaphlan2/downloads
* License : expat
Program
Thomas Goirand writes:
> While I do agree that a package *must* be able to build without Internet
> access (for example, the test suite should never mandate access to a
> working DNS, or a query to a google search, both of which are real world
> cases...), I'm not sure about the severity: serious
* Vincent Bernat , 2016-09-07, 07:17:
both pbuilder and sbuild are using an isolated network namespace
I know about pbuilder, but [citation needed] for sbuild.
--
Jakub Wilk
* Russ Allbery , 2016-09-07, 09:26:
Now, that said, assuming that "fail" is not a valid host in the local
domain isn't a good assumption and makes the build fragile. My packages
that perform a similar test use the DNS name addrinfo-test.invalid to
force a failure, which is guaranteed by IANA re
Jakub Wilk writes:
> * Russ Allbery , 2016-09-07, 09:26:
>> Now, that said, assuming that "fail" is not a valid host in the local
>> domain isn't a good assumption and makes the build fragile. My packages
>> that perform a similar test use the DNS name addrinfo-test.invalid to
>> force a failure,
On Sat, Jul 9, 2016, at 07:59, Ben Hutchings wrote:
> Non-free is not part of Debian so those components would need to be
> explicitly installed.
>
> firmware-nonfree is up-to-date in backports (at least, it is in synch
> with testing and unstable).
And so are the microcode packages, which are
On Tue, Jul 12, 2016, at 10:28, Jeffrey Walton wrote:
> [38229.510127] mce: [Hardware Error]: Machine check events logged
>
> $ sudo mcelog
> mcelog: Family 6 Model 3d CPU: only decoding architectural errors
Update that bios/UEFI *and* install intel-microcode from
stable-proposed-updates or ba
* Christian Seiler , 2016-09-07, 07:43:
That way, you can force host name resolution to not use DNS for your
test suite (via just using a hosts file), then there will be no network
access during package build, and you don't have to keep rebasing a
patch. And, even better, IF there is a host nam
Henrique de Moraes Holschuh writes ("Re: Thinking about a "jessie and a half"
release"):
> And so are the microcode packages, which are absolutely required for
> stable operation of at least Skylake and Broadwell right now (or your
> data is toast due to TSX malfunction or one of the multiple unde
Chào bạn lista, mình thấy trang web của bạn đang bị mất khá nhiều từ khóa trên
google
Đó là do khách truy cập xem website của bạn nhưng đã thoát khỏi trang web quá
nhanh
Bạn có thể dùng hộp chat của uhchat .net gắn vào website và câu giờ cho họ ở
lại lâu hơn để chat với bạn thay vì
Hi,
Quoting Jakub Wilk (2016-09-07 19:29:05)
> * Vincent Bernat , 2016-09-07, 07:17:
> >both pbuilder and sbuild are using an isolated network namespace
>
> I know about pbuilder, but [citation needed] for sbuild.
there is no out-of-the-box functionality that provides this for sbuild. There
is a
On Wed, Sep 07, 2016 at 09:26:37AM -0700, Russ Allbery wrote:
> Thomas Goirand writes:
> > While I do agree that a package *must* be able to build without Internet
> > access (for example, the test suite should never mandate access to a
> > working DNS, or a query to a google search, both of whic
31 matches
Mail list logo
