Groups > linux.debian.maint.python > #14096

Re: Updating jupyter-core to 4.10.0

Path	csiph.com!aioe.org!bofh.it!news.nic.it!robomod
From	Julian Gilbey <julian@d-and-j.net>
Newsgroups	linux.debian.maint.python
Subject	Re: Updating jupyter-core to 4.10.0
Date	Fri, 06 May 2022 09:10:01 +0200
Message-ID	<Ek0g9-dAa7-1@gated-at.bofh.it> (permalink)
References	<EjEyZ-dlJ1-9@gated-at.bofh.it> <EjFln-dmdJ-1@gated-at.bofh.it> <EjQTv-du3Q-7@gated-at.bofh.it>
X-Mailbox-Line	From debian-python-request@lists.debian.org Fri May 6 07:07:07 2022
Old-Return-Path	<julian@d-and-j.net>
X-Amavis-Spam-Status	No, score=-6.21 tagged_above=-10000 required=5.3 tests=[BAYES_00=-2, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, GMAIL=1, LDO_WHITELIST=-5, T_SCC_BODY_TEXT_LINE=-0.01] autolearn=ham autolearn_force=no
X-Policyd-Weight	using cached result; rate: -4.6
MIME-Version	1.0
Content-Type	text/plain; charset=iso-8859-1
Content-Disposition	inline
Content-Transfer-Encoding	8bit
X-Mailing-List	<debian-python@lists.debian.org> archive/latest/19921
List-ID	<debian-python.lists.debian.org>
List-URL	<https://lists.debian.org/debian-python/>
List-Archive	https://lists.debian.org/msgid-search/YnTJB82O8bYI40Sw@d-and-j.net
Approved	robomod@news.nic.it
Lines	35
Organization	linux.* mail to news gateway
Sender	robomod@news.nic.it
X-Original-Cc	Gordon Ball <gordon@chronitis.net>, debian-python@lists.debian.org
X-Original-Date	Fri, 6 May 2022 08:06:47 +0100
X-Original-Message-ID	<YnTJB82O8bYI40Sw@d-and-j.net>
X-Original-References	<ada8b747e54971b96961b06f414514ac70609ae8.camel@gmail.com> <YnOOK9ADWa98IYZF@d-and-j.net> <6dd1f4e98a65e9b95f7ad17654ce8a1559acd4f9.camel@gmail.com>
Xref	csiph.com linux.debian.maint.python:14096

Show key headers only | View raw

On Thu, May 05, 2022 at 11:07:31PM +0200, julien.puydt@gmail.com wrote:
> Le jeudi 05 mai 2022 à 09:43 +0100, Julian Gilbey a écrit :
> > 
> > I've had similar problems in the past.  It usually comes down to the
> > build requiring some package that happens to be present on your
> > system but not listed in the Build-Depends field, so dpkg-
> > buildpackage works, but sbuild doesn't.
> 
> That's indeed the usual suspect ; but here it turns out it wanted a
> writable home directory.
> 
> I'll check it doesn't break everything then upload... probably
> tomorrow...
> 
> Thanks!
> 
> J.Puydt

Ah, of course, that's the other thing I've hit in recent times with
ipython-related packages.  Note that writing to the home directory at
build-time is a contravention of Policy; see the thread starting at
https://lists.debian.org/debian-devel/2022/04/msg00345.html where I
ask about pretty much the same thing, and a clear distinction is made
between build time and autopkgtest time.  You mentioned earlier that
it's the tests that are failing; are these build-time tests or
autopkgtest tests?  If they're build-time tests, you could either
disable them or create a temporary home directory.  If they're
autopkgtest tests, then it depends on your test environment; see that
thread for recommendations and
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1010437 for a
discussion of how to set up lxc with autopkgtest.

Best wishes,

   Julian

Back to linux.debian.maint.python | Previous | Next — Previous in thread | Find similar | Unroll thread

Thread

Updating jupyter-core to 4.10.0 julien.puydt@gmail.com - 2022-05-05 10:00 +0200
  Re: Updating jupyter-core to 4.10.0 Julian Gilbey <julian@d-and-j.net> - 2022-05-05 10:50 +0200
    Re: Updating jupyter-core to 4.10.0 julien.puydt@gmail.com - 2022-05-05 23:10 +0200
      Re: Updating jupyter-core to 4.10.0 Julian Gilbey <julian@d-and-j.net> - 2022-05-06 09:10 +0200

csiph-web