Re: Bug#1002344: hy: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.10 3.9" returned exit code 13

2021-12-22 Thread Tianon Gravi 
On Wed, 22 Dec 2021 at 00:04, Lucas Nussbaum  wrote:
> Source: hy
> Version: 0.19.0-2
> Severity: serious
> Justification: FTBFS
> Tags: bookworm sid ftbfs
> User: lu...@debian.org
> Usertags: ftbfs-20211220 ftbfs-bookworm
>
> Hi,
>
> During a rebuild of all packages in sid, your package failed to build
> on amd64.
> ...
> If you fail to reproduce this, please provide a build log and diff it with 
> mine
> so that we can identify if something relevant changed in the meantime.

Ouch, thanks for the report.  I think the best fix for this is going
to be updating the package to the 1.0a3 upstream release (because I'm
fairly sure this is really about Hy 0.19 not actually supporting
Python 3.10 yet and the 1.0a3 release does), however that bump
includes the landmine of a complete documentation refactor that
creates a bit of a complex cycle with (the new)
https://github.com/hylang/sphinxcontrib-hydomain repository. 

I've played with building those together as a multiorig package (given
both the dependency cycle and that there aren't likely to be many/any
other consumers of "sphinxcontrib-hydomain" at this time), and ran
into a number of (hopefully minor?) problems, the first of which being
versioning (that repository has a tagged version, but it isn't
compatible with the latest Hy release nor the version of Sphinx in
Debian, but getting a commit that's good enough for the latter doesn't
fully resolve the former and requires further patching).

However, I'm definitely in a bit over my head here, so I'm adding
debian-python to CC hoping that perhaps someone there has some good
advice or ideas (maybe even a spare cycle or two). 

My (non-functional) WIP can be found at
https://salsa.debian.org/hy-team/hy/-/compare/master...1.0a3 

If I bypass the Sphinx bits, I run into "INTERNALERROR> IndexError:
list index out of range" (and the full backtrace appears to all be in
non-Hy codelike pytest and "pluggy"), which I *think* is related to
funcparserlib needing to be 1.0.0a0+
(https://github.com/hylang/hy/pull/2164), but I am not certain.

♥,
- Tianon
  4096R / B42F 6819 007F 00F8 8E36  4FD4 036A 9C25 BF35 7DD

Re: Bug#959631: hy: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.8 returned exit code 13

2020-05-15 Thread Tianon Gravi 
On Tue, 5 May 2020 at 10:55, Tianon Gravi  wrote:
> I was definitely over my head with this one, so I reached out to the
> Hy community and was pointed to https://bugs.python.org/issue39562,
> which does seem quite related from my own limited understanding, so
> this might technically be a bug in the Python package?
>
> I'm including the Debian Python list on CC to hopefully see if someone
> there can provide some assistance figuring out what's necessary here.
> O:)

Looking at results from ci.debian.net[1], our autopkgtests failed on
2020-05-07 and passed today (2020-05-15).  Comparing the logs, it
appears the difference is that the last failing build was against
python3.8 version 3.8.3~rc1-1, and the successful build from today was
against python3.8 version 3.8.3-1 (lending credence to the thought it
was probably a Python bug, and that it's now fixed).

[1]: https://ci.debian.net/packages/h/hy/

Can you re-test and verify that we no longer FTBFS in your testing? O:)

♥,
- Tianon
  4096R / B42F 6819 007F 00F8 8E36  4FD4 036A 9C25 BF35 7DD4

Re: Bug#959631: hy: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.8 returned exit code 13

2020-05-05 Thread Tianon Gravi 
On Sun, 3 May 2020 at 06:12, Lucas Nussbaum  wrote:
> > ...
> > === warnings summary 
> > ===
> > .pybuild/cpython3_3.8_hy/build/tests/native_tests/comprehensions.hy::test_fors[sfor]
> >   /<>/hy/models.py:133: RuntimeWarning: coroutine '' 
> > was never awaited
> > return super(HySymbol, cls).__new__(cls, s)
> >
> > .pybuild/cpython3_3.8_hy/build/tests/native_tests/comprehensions.hy::test_fors[gfor]
> >   /usr/lib/python3/dist-packages/funcparserlib/parser.py:232: 
> > RuntimeWarning: coroutine '' was never awaited
> > self.pos = pos
> >
> > .pybuild/cpython3_3.8_hy/build/tests/native_tests/comprehensions.hy::test_empty_for
> >   /usr/lib/python3/dist-packages/_pytest/nodes.py:192: RuntimeWarning: 
> > coroutine '' was never awaited
> > return (x[1] for x in self.iter_markers_with_node(name=name))
> >
> > .pybuild/cpython3_3.8_hy/build/tests/native_tests/core.hy::test_parse_args
> >   /usr/lib/python3/dist-packages/funcparserlib/parser.py:322: 
> > RuntimeWarning: coroutine '' was never awaited
> > raise NoParseError('got unexpected token', s)
> >
> > -- Docs: https://docs.pytest.org/en/latest/warnings.html
> > === 5 failed, 547 passed, 54 deselected, 4 warnings in 8.47 seconds 
> > 
> > E: pybuild pybuild:352: test: plugin distutils failed with: exit code=1: cd 
> > /<>/.pybuild/cpython3_3.8_hy/build; python3.8 -m pytest -k 
> > '-test_bin -test_hy2py'
> > dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.8 
> > returned exit code 13
>
> ...

Oh, fun times.

I was definitely over my head with this one, so I reached out to the
Hy community and was pointed to https://bugs.python.org/issue39562,
which does seem quite related from my own limited understanding, so
this might technically be a bug in the Python package?

I'm including the Debian Python list on CC to hopefully see if someone
there can provide some assistance figuring out what's necessary here.
O:)

♥,
- Tianon
  4096R / B42F 6819 007F 00F8 8E36  4FD4 036A 9C25 BF35 7DD4

Re: Request to Join

2016-01-22 Thread Tianon Gravi 
On 21 January 2016 at 07:10, Harlan Lieberman-Berg  wrote:
> I'd like to request to join this team to help maintain backports of the Let's 
> Encrypt dependencies, especially python-sphinx.
>
> I've read and agree to the Python Modules Team Policy. My Alioth username is 
> hlieberman-guest.

I can't accept your request (not a DPMT admin), but I think you'd be a
fine addition to the team (having worked with you previously). :)

♥,
- Tianon
  4096R / B42F 6819 007F 00F8 8E36  4FD4 036A 9C25 BF35 7DD4

Re: Question about private modules in /usr/share

2015-04-20 Thread Tianon Gravi 
On 20 April 2015 at 20:21, Potter, Tim (Cloud Services)
timothy.pot...@hp.com wrote:
 It looks pretty good, but I think I have messed up something as my binary 
 gives an import error since /usr/share/dwarf isn’t in the PYTHONPATH:

 # dwarf
 Traceback (most recent call last):
   File /usr/bin/dwarf, line 32, in module
 from dwarf import log   # pylint: disable=W0611
 ImportError: No module named dwarf

I'm not an expert by any means, but it's been my experience that the
more you trust Piotr's pybuild code to DTRT, the more it does. :)

I cloned your package locally and removed both override_dh_*
sections from debian/rules and deleted debian/links and it
successfully created a package with just pybuild, including installing
dwarf and dwarf-manage in /usr/bin.  Is there a specific reason to
override what pybuild is doing?

Here's what I get after removing those sections, building, installing,
and testing the result:

| # dwarf
| libvirt: XML-RPC error : Failed to connect socket to
'/var/run/libvirt/libvirt-sock': No such file or directory

This seems to be working properly (there's no ImportError), but I
admit I'm not at all familiar with upstream here. :)

♥,
- Tianon
  4096R / B42F 6819 007F 00F8 8E36  4FD4 036A 9C25 BF35 7DD4


--
To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
https://lists.debian.org/cahnknk11ikxumq2psaoyyufmuh8dkf6musepwveocwe+06u...@mail.gmail.com

Re: python3-aiohttp

2015-03-31 Thread Tianon Gravi 
On 31 March 2015 at 07:24, Daniel Lintott dan...@serverb.co.uk wrote:
 I can't find an ITP/RFP bug for the package, but see that there are some
 files already in SVN.

I was packaging it originally for something paultag was working on,
but he no longer needed it so I didn't finish (and it felt like a
waste to just purge it completely).

Piotr recently expressed some interest (on IRC), but I don't think he
took it any further after I offered it to him.  I'd reiterate what I
told him though; I'm happy to work on finishing it out more if there's
some interest in it, but I also won't be sad if someone wants to just
take over from me (either using my bits or scrapping them entirely and
starting fresh).  I'd point out that it's really close as-is, though.
:)

♥,
- Tianon
  4096R / B42F 6819 007F 00F8 8E36  4FD4 036A 9C25 BF35 7DD4


--
To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
https://lists.debian.org/cahnknk3foqzcyez5ogu86yogcthjqtprxxpm_ti-avokv-x...@mail.gmail.com

Re: PyPI and debian/watch

2015-02-04 Thread Tianon Gravi 
On 4 February 2015 at 06:08, Donald Stufft don...@stufft.io wrote:
 If it gets implemented it'll live at /uscan/ because it exists primarily to
 work around the deficiencies that exist in uscan (Particularly the dificulty
 in ignoring url fragments).

This seems like we're building a workaround to a tool we could
theoretically change. :(

debian/watch has a version=3, which is presumably so that there
can be a version=4 when deficiencies are discovered -- wouldn't it
be worthwhile to consider revbumping the watch format and updating
uscan to have some improved support for edge cases like this?  I know
uscan has some other open bugs too that could use some thought towards
a more flexible format to handle cases like this.

♥,
- Tianon
  4096R / B42F 6819 007F 00F8 8E36  4FD4 036A 9C25 BF35 7DD4


--
To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
https://lists.debian.org/cahnknk2j1huhddu49nqkzag9vf5opcsj49yuulnuterm3jg...@mail.gmail.com

Re: PyPI and debian/watch

2015-02-04 Thread Tianon Gravi 
On 4 February 2015 at 13:06, Donald Stufft don...@stufft.io wrote:
 We talked about this in #debian-python and there was concern that a new 
 version
 of uscan wouldn’t be in Jessie and then wouldn’t cover the people who need it
 the most.

Ah right, that makes sense -- I forgot that we were talking about this
specifically in the context of getting some kind of fix into Jessie.

♥,
- Tianon
  4096R / B42F 6819 007F 00F8 8E36  4FD4 036A 9C25 BF35 7DD4


--
To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
https://lists.debian.org/cahnknk3ccon84fffzhxdkgpsneym7dikaonwkorjnqzzuxa...@mail.gmail.com

Re: Debian uscan redirector for PyPI (was: PyPI and debian/watch)

2015-02-04 Thread Tianon Gravi 
On 4 February 2015 at 15:18, Ben Finney ben+deb...@benfinney.id.au wrote:
 Great! Can we please have (from you, or whoerver is best position to
 write it) a reference on how to use this redirector?

Checking out http://pypi.debian.net/hy, it looks pretty easy to use. :)

♥,
- Tianon
  4096R / B42F 6819 007F 00F8 8E36  4FD4 036A 9C25 BF35 7DD4


--
To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
https://lists.debian.org/cahnknk3wqcme_bwjpi8c-k469wzvnze3m3d_r2yalnrydd6...@mail.gmail.com

Re: About requests.packages.urllib3 in Debian

2014-11-13 Thread Tianon Gravi 
On 13 November 2014 10:25, Daniele Tricoli er...@mornie.org wrote:
 I'm working on this and I think I have already the proper fix. Sorry for this!
 :(

No worries from my end!  Thanks for your work! :D

♥,
- Tianon
  4096R / B42F 6819 007F 00F8 8E36  4FD4 036A 9C25 BF35 7DD4


--
To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
https://lists.debian.org/cahnknk1zxwt3ffr67wta29nyhck6sz1m3p-nfs9dgiewuu9...@mail.gmail.com

Re: About requests.packages.urllib3 in Debian

2014-11-12 Thread Tianon Gravi 
On 12 November 2014 15:15, Daniele Tricoli er...@mornie.org wrote:
 All done, including unblocking by RT (you rock! :). Many thanks to all!

I reverted the python-docker -1.1 patch (and I've pushed that up so
it's easier to test against), and now it works perfectly in python2
using the new requests 2.4.3-3, but python3 fails with the following:

| $ python3 basic-test.py
| Traceback (most recent call last):
|   File basic-test.py, line 1, in module
|import docker, os
|  File /usr/lib/python3/dist-packages/docker/__init__.py, line 20,
in module
|from .client import Client # flake8: noqa
|  File /usr/lib/python3/dist-packages/docker/client.py, line 28, in module
|from .unixconn import unixconn
|  File /usr/lib/python3/dist-packages/docker/unixconn/__init__.py,
line 1, in module
|from .unixconn import UnixAdapter  # flake8: noqa
|  File /usr/lib/python3/dist-packages/docker/unixconn/unixconn.py,
line 24, in module
|import requests.packages.urllib3.connectionpool as connectionpool
| AttributeError: 'module' object has no attribute 'packages'

Where the contents of my basic-test.py are:

| import docker, os
| c = docker.Client(base_url=os.getenv('DOCKER_HOST'))
| print(c.version())
| print(c.images())

Any ideas?  Do we need to include some kind of further patch in
python-docker, or was the patch to requests possibly not complete?

♥,
- Tianon
  4096R / B42F 6819 007F 00F8 8E36  4FD4 036A 9C25 BF35 7DD4


--
To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
https://lists.debian.org/CAHnKnK2PXUhaC7DCO2Quze7ZEbA=xjw3umsznocgdxzndfg...@mail.gmail.com

Re: About requests.packages.urllib3 in Debian

2014-11-12 Thread Tianon Gravi 
On 12 November 2014 23:43, Tianon Gravi admwig...@gmail.com wrote:
 I reverted the python-docker -1.1 patch (and I've pushed that up so
 it's easier to test against), ...

Of course, that's the moment where my local push decides to hang and
make a liar out of me...  O:)

♥,
- Tianon
  4096R / B42F 6819 007F 00F8 8E36  4FD4 036A 9C25 BF35 7DD4


--
To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
https://lists.debian.org/cahnknk2kxzc53eua6lbejxpkfbrz+6ffmwd-7rmj7g_zzgs...@mail.gmail.com

Re: Keeping upstream commits separate from Debian packaging commits (was: Fighting commit storm madness)

2014-10-10 Thread Tianon Gravi 
On 9 October 2014 22:59, Ben Finney ben+deb...@benfinney.id.au wrote:
 It's a good illustration of why I much prefer the workflow of a separate
 VCS for the ‘debian/’ directory, merged with upstream source only at
 build time. The results of the merge are in a separate location and are
 never checked into VCS, they're used only for the build.

At the BoF during DebConf, me and paultag discussed how we use exactly
this workflow for Docker stuff in Git, and we love it.  We don't ever
worry about any kind of upstream commits in the packaging, and only
deal with upstream tarballs/source at build time, which keeps things
simple.

Looking at the history of our repo is a direct look at the history of
debian/, which makes sense because it's a repo for the packaging, and
anything other than that really is a distraction.

During the BoF, we were kind of alone in recommending this workflow,
but it's certainly nice (for me anyhow) to see other people advocating
it as well! :)

TL;DR +1 for ditching upstream artifacts :

♥,
- Tianon


--
To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
https://lists.debian.org/cahnknk0gbmk6jeeidfqrtqupgpmw-_iyzajhab-yj+njamh...@mail.gmail.com

Re: When packaging a library, should I prevent its test suite from being packaged

2014-09-10 Thread Tianon Gravi 
On 9 September 2014 09:28, Piotr Ożarowski pi...@debian.org wrote:
 (I will remove all .../dist-packages/test{,s} by default in next
 dh_python{2,3} version).

Does this mean we'll get a nice warning too, so we know that we need
to report the bug upstream? :)

♥,
- Tianon


--
To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
https://lists.debian.org/cahnknk3dx4zbiwqflektrvkl_0j0_ktuj7cz-pcxnkqj5zs...@mail.gmail.com

Re: When packaging a library, should I prevent its test suite from being packaged

2014-09-10 Thread Tianon Gravi 
On 10 September 2014 11:11, Piotr Ożarowski pi...@debian.org wrote:
 yes (and I'm still wondering if failing with an error message that this
 module name is too generic is a better idea)

I'd personally love to see it hard fail (since warnings will be quite
often missed), especially if it included some hints about how to patch
it out or patch move it appropriately while waiting for upstream to
respond to the request to install it in the proper namespace.

♥,
- Tianon


--
To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
https://lists.debian.org/cahnknk3kxgazquj2atokt1wrcpvgqoufww8ntmq0crweh4e...@mail.gmail.com

Re: librabbitmq and git

2014-08-18 Thread Tianon Gravi 
On 18 August 2014 17:52, Brian May br...@microcomaustralia.com.au wrote:
 I take this to mean I should be downloading the orig.tag.gz from github.

Not that I'm involved in the packaging or the upstream here in any
way, but I just wanted to point out that this is exactly what
debian/watch[1] is for, which uscan(1) will read and use to find
upstream versions.

♥,
- Tianon

[1]: 
http://anonscm.debian.org/cgit/collab-maint/librabbitmq.git/tree/debian/watch


--
To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
https://lists.debian.org/CAHnKnK3HOvEzBvBa6uRZ8-+bnXYg7-G93z1pfB00Kcx6_CN7=w...@mail.gmail.com

Re: librabbitmq and git

2014-08-18 Thread Tianon Gravi 
On 18 August 2014 18:11, Brian May br...@microcomaustralia.com.au wrote:
 Unfortunately, debian/watch (AFAIK) doesn't include any details of any
 changes that were made to the tar.gz file by the package developer.

It's been my understanding that this is exactly one of the main uses of
the command argument in debian/watch.  See docker.io's debian/watch[1]
for example, where /bin/sh debian/repack.sh is what does the
DFSG-compliance repacking of the orig tarball so that they're cleanly
repeatable (which is an important property of orig tarballs).

Have you tried comparing the existing orig tarball from the archive to
the corresponding tarball downloaded via uscan?

  $ curl -sSL 
'http://http.debian.net/debian/pool/main/libr/librabbitmq/librabbitmq_0.5.0.orig.tar.gz'
| sha1sum
  826286c3f04695bdc231d8e7b0541f871975cdcc  -

  $ curl -sSL 'https://github.com/alanxz/rabbitmq-c/archive/v0.5.0.tar.gz'
| sha1sum
  826286c3f04695bdc231d8e7b0541f871975cdcc  -

Also, looking in Git, it would appear that Michael is currently working
on packaging 0.5.1. ;)

♥,
- Tianon

[1]: http://sources.debian.net/src/docker.io/1.0.0~dfsg1-1/debian/watch


--
To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
https://lists.debian.org/cahnknk0zsxxmsmhzmdwohhqnruam5b6+jhf12gzouga-php...@mail.gmail.com

python-docker

2014-05-05 Thread Tianon Gravi 
Hi! :)

I'm part of the docker-maint team (which is listed in Uploaders on
python-docker), and I'm interested in joining DPMT to help Paul maintain
and update python-docker, which is falling a little bit behind upstream.

♥,
- Tianon


-- 
To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20140505211857@gmail.com