Le 16/07/2019 à 16:52, Paul Tagliamonte a écrit :
> I lost some of this thread - should we request a transition
> from the release team? I was looking for the list of blockers
> to dropping Python 2 and couldn't find anything except this
> thread (where we're still figuring out what to do, of cours
Le 16/07/2019 à 17:21, Andrey Rahmatullin a écrit :
> Python 2 is included in buster and so will be supported for several
> years.
>
The starting point of the thread was :
1. Ok, buster has Python 2 so even if upstream drops it, we will still
support it for the years to come for our users ;
2. bu
Hi,
Le mardi 10 décembre 2019 à 21:08 +0100, Patrice Duroux a écrit :
> Two tiny remarks related to the recent python3-testpath upgrade to
> 0.4.4+dfsg-1.
Oops! I did it again?
> 1. Two open bugs were almost the same (or at least to me):
>
> #945214 assigned to python3-pip and reassigned to pyt
Hi,
Le mercredi 11 décembre 2019 à 20:10 +0100, Patrice Duroux a écrit :
> For the PKG-INFO file I just found it inside the .tar.gz available
> here where I
> am checking Python module:
> https://pypi.org/project/testpath/#files
> but may be I am wrong to check such a source. This repository is ma
Le samedi 18 janvier 2020 à 02:38 +, peter green a écrit :
> I just took a look at the "add python3.8 transition tracker", and
> split the remaining "bad" packages into categories.
There's another kind of issue ; here is an example :
- sagemath builds only for Python 3.7, so some of this subp
Le dimanche 19 janvier 2020 à 00:54 +, peter green a écrit :
> > There's another kind of issue
> Yeah, sadly the transition tracker only looks at unstable, so
> packages that are fixed in unstable but haven't migrated to testing
> for some reason won't show up.
> > ; here is an example :
> >
Hi,
I'm trying to solve this bug on python3-setuptools-scm :
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=928156
where the problem is :
- python3-setuptools-scm depends on python3-distutils
- python3-distutils is not a separate package in stretch-backports.
I think the solution of the prob
Le mercredi 22 janvier 2020 à 21:04 +0500, Andrey Rahmatullin a écrit :
> On Wed, Jan 22, 2020 at 04:53:22PM +0100, Julien Puydt wrote:
> > Hi,
> >
> > I'm trying to solve this bug on python3-setuptools-scm :
> >
> > https://bugs.debian.org/cgi-bin/bugre
Hi,
I saw python3-itsdangerous was far behind upstream, and decided to if
it was easy to update : but it's not on salsa.
Should I import the last known package version (recent upload to remove
the Python 2 package) to a new salsa repository and start from here?
Cheers,
JP
Le jeudi 27 février 2020 à 15:49 +0500, Andrey Rahmatullin a écrit :
> On Thu, Feb 27, 2020 at 11:33:00AM +0100, Julien Puydt wrote:
> > Hi,
> >
> > I saw python3-itsdangerous was far behind upstream, and decided to
> > if
> > it was easy to update : but it&
Le jeudi 27 février 2020 à 19:14 +0500, Andrey Rahmatullin a écrit :
> https://alioth-archive.debian.org/git/collab-maint/python-itsdangerous.git.tar.xz
>
I must be going through a very bad day, but trying to follow
https://wiki.debian.org/Salsa/AliothMigration#By_hand doesn't work ;
the two gi
Package: ftp.debian.org
Severity: normal
X-Debbugs-CC: debian-python@lists.debian.org
The src:ipykernel-py2 package provides python-ipykernel, which is to be
removed for the Python 2 removal transition.
Notice that for most packages, a single src:foo package provides both
python-foo and python3-f
Hi,
I know about the SETUPTOOLS_SCM_PRETEND_VERSION trick when it is used
in d/rules :
include /usr/share/dpkg/pkg-info.mk
export SETUPTOOLS_SCM_PRETEND_VERSION=$(DEB_VERSION_UPSTREAM)
so setuptools-scm won't have trouble finding the correct version
outside of a git repository. But the situation
Hi,
Le mardi 09 juin 2020 à 10:35 +0200, Ondrej Novy a écrit :
> po 8. 6. 2020 v 17:22 odesílatel Julien Puydt > napsal:
> > I know about the SETUPTOOLS_SCM_PRETEND_VERSION trick when it is
> > used
> > in d/rules :
> >
> > include /u
Le dimanche 05 juillet 2020 à 00:52 -0400, Sandro Tosi a écrit :
> Tbh, i think it's time to just rip the bandaid and upload mercurial
> python3 to unstable, and deal with the consequences there (i
> volunteer to do so);
>
> What do people think about this?
Against band-aid ripping :
- breaking
Hi,
Le mardi 04 août 2020 à 07:49 -0500, Dirk Eddelbuettel a écrit :
> Hi doko and Python folks,
>
> I am lost.
>
I suggest to check the shebangs.
Cheers,
JP
Package: wnpp
Severity: wishlist
X-Debbugs-CC: debian-python@lists.debian.org
* Package name : python-jupyterlab-pygments
Version: 0.1.2
Upstream author: Project Jupyter Contributors
* URL : https://github.com/jupyterlab/jupyterlab_pygments
* License : BSD-3-clause
Descriptio
Hi,
there are two repositories which claim they package src:ipython : one
is named dpt:ipython, and the other is dpt:ipython4.
The dpt:ipython repository hasn't seen serious use in years : every
packaging work has been done in the dpt:ipython4 one.
The two usual uploaders, Gordon Ball and myself
Package: wnpp
Severity: wishlist
X-Debbugs-CC: debian-python@lists.debian.org
* Package name: jupyter-server
Version: 1.0.5
Upstream author: Jupyter Development Team
* URL: https://github.com/jupyter/jupyter_server
License: BSD-3-clause
Description: Jupyter protocol server backend
It's a step to
Hi,
my first goal was to update nbconvert -- but it needs a more recent
nbsphinx.
So I have a look at nbsphinx. Ah, it requires a more recent ipywidgets.
Now ipywidgets gets interesting : that package suffers from a lack of
love, for reasons made obvious below.
The purely Python part is ok, but
Package: wnpp
Severity: wishlist
X-Debbugs-CC: debian-python@lists.debian.org
* Package name: jupyterlab-server
Version: 1.2.0
Upstream author: Project Jupyter contributors
* URL: https://github.com/jupyterlab/jupyterlab_server
* License: BSD-3-clause and Expat
Programming lang: Python
Des
Package: wnpp
Severity: wishlist
X-Debbugs-CC: debian-python@lists.debian.org
* Package name: python-anyio
Version: 2.0.2
Upstream author: Alex Grönholm
* URL: https://github.com/agronholm/anyio
* License: Expat
Programming lang: Python
Description: Asynchronous compatibility layer
This i
Hi,
I have worked on jupyterlab last year.
Le mardi 18 mai 2021 à 08:06 +, Gordon Ball a écrit :
> On Mon, May 17, 2021 at 06:20:19PM +0200, Roland Mas wrote:
> > Hi everyone,
> >
> > I've been contracted by Synchrotron Soleil to work on the packaging
> > of
> > Jupyterhub and its dependenci
Hi,
I don't get why python-anyio is stuck ; I certainly didn't upload it
without trying to build it, and I just tried again and there was no
issue :
https://buildd.debian.org/status/package.php?p=python-anyio
Does someone have a clue what is happening?
Cheers,
J.Puydt
Hi,
I tried to update ipython to latest upstream. I fixed some things here
and there but there's still :
1) Building the doc, some files don't get found (several no such file
or directory docs/source/whatever/file) and a few syntax errors,
perhaps due to the previous issues -- strangely, that doe
Package: wnpp
Owner: Julien Puydt
X-Debbugs-Cc: Debian Python
Severity: wishlist
* Package name: nbclassic
Version : 0.3.2
Upstream Author : Jupyterlab Project contributors
* URL : https://github.com/jupyterlab-nbclassic
* License : BSD-3-clause
Programming
Hi,
I check my packages in a schroot on my computer before uploading ; that
way I detect problems like missing deps or network access, and I'm
pretty confident things will go well on the buildd network.
But today's upload of python-anyio is broken... and I'm clueless as to
why. From the repeated
Hi,
I tried to update jupyter-core to 4.10.0, but didn't manage to run the
upstream test suite reliably.
I first disabled it, so the package was building with both dpkg-
buildpackage and sbuild. A bad solution.
Then I re-enabled it ; it passes with dpkg-buildpackage (there's a
catch, see [1]), b
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
Le jeudi 02 juin 2022 à 10:28 -0400, Sandro Tosi a écrit :
> > I would suggest ratt-rebuilding all reverse dependencies. Could
> > that be
> > done?
>
> there order of thousands rdeps, i dont think it's fair to ask any
> individual contributor the time and resources to check that via ratt.
Agreed
Le lundi 11 juillet 2022 à 18:37 +0100, Julian Gilbey a écrit :
> [Explanation: britney (?) tries each
> package on its own when testing for migration: pytest can't migrate
> as that would break pygments in testing, and pygments can't migrate
> as it depends on the newer pytest. So we're stuck and
Hi,
I decided to fix the jupyter-notebook packages ; on salsa I:
- updated to a more recent upstream (but still in the same series to
avoid breaking things) ;
- unbroke the build by hand ;
- unbroke the build in chroot.
So far, so good, but I didn't unbreak the autopkg tests. Here is the
rele
Le jeudi 11 août 2022 à 11:34 +0100, Carles Pina i Estany a écrit :
>
> Hi,
>
> On Aug/11/2022, julien.pu...@gmail.com wrote:
>
> > So far, so good, but I didn't unbreak the autopkg tests. Here is
> > the
> > relevant part of the log:
>
> do you have a link to the full log on salsa and the repo
Package: ftp.debian.org
X-Debbugs-CC: debian-python@lists.debian.org
I packaged this years ago when nice features of Python 3 needed a
backport to Python 2 ; those days are gone and we're moving away from
Python 2 with the next release of Debian, so this package should be
removed.
I checked with
Package: wnpp
Severity: wishlist
X-Debbugs-Cc: jpu...@debian.org, debian-python@lists.debian.org
* Package name: python-hatch-nodejs-version
Version : 0.3.0
Upstream Author : Angus Hollands
* URL : https://github.com/agoose77/hatch-nodejs-version
* License : Exp
Hi,
Le samedi 25 novembre 2023 à 16:23 +, Stefano Rivera a écrit :
>
> Julien Puydt
> fpylll (U)
> pplpy (U)
>
I had a look.
For fpylll: it has a newer upstream which works with more recent cython
versions, so I'm actually eager to see the move.
For pplpy, I&
Hi,
Le samedi 25 novembre 2023 à 16:23 +, Stefano Rivera a écrit :
>
> Julien Puydt
> fpylll (U)
> pplpy (U)
For pplpy, I found the package was pointing to an archived repo, but
the author had a newer one with a version which is supposed to be okay
(to be confirmed).
Le jeudi 30 novembre 2023 à 08:25 +0100, julien.pu...@gmail.com a
écrit :
> Hi,
>
> Le samedi 25 novembre 2023 à 16:23 +, Stefano Rivera a écrit :
> >
> > Julien Puydt
> > fpylll (U)
> > pplpy (U)
>
>
> For pplpy, I found the package w
bug #1052826 (broken tests)
Author: Julien Puydt
Forwarded: not needed
--- entrypoints.orig/tests/test_entrypoints.py
+++ entrypoints/tests/test_entrypoints.py
@@ -19,31 +19,31 @@
def test_iter_files_distros():
result = entrypoints.iter_files_distros(path=sample_path)
-# the sample_path h
101 - 139 of 139 matches
Mail list logo
