Re: Seeking a small group to package Apache Arrow (was: Bug#970021: RFP: apache-arrow -- cross-language development platform for in-memory analytics)

2024-04-04 Thread Richard Duivenvoorde

On 3/25/24 7:17 PM, Julian Gilbey wrote:

So this is a plea for anyone looking for something really helpful to
do: it would be great to have a group of developers finally package
this!  There was some initial work done (see the RFP bug report for
details: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=970021),
but that is fairly old now.  As Apache Arrow supports numerous
languages, it may well benefit from having a group of developers with
different areas of expertise to build it.  (Or perhaps it would make
more sense to split the upstream source into a collection of different
Debian source packages for the different supported languages.  I don't
know.)  Unfortunately I don't have the capacity to devote any time to
it myself.

Thanks in advance for anyone who can step forward for this!


As someone from the Debian-GIS community, I would also be very interested in 
this!

The Apache Arrow C++ library is one of the dependencies to make GDAL/OGR able 
to read/write (geo)parquet files, a data format with a lot traction in the geo 
community [0]. Thereby making it possible for QGIS to handle those (on Debian).

[0] 
https://cloudnativegeo.org/blog/2023/09/duckdb-the-indispensable-geospatial-tool-you-didnt-know-you-were-missing/

Regards,

Richard Duivenvoorde



Re: [Python-modules-team] python-docker issue?

2015-11-22 Thread Richard Duivenvoorde

Ah, thanks for your help Brian.

I fixed my problem thanks to your hints:
- removed docker, docker-dompose, python-docker, python-dockerpty
- updatedb;locate docker
- and found there was still a docker egg/package in
/usr/local/lib/python2.7/site-packages
- apparently I installed docker python stuff using pip some time ago...
- after removing that stuff and reinstalling all is working again.

Sorry for the noise. Me bad for using non-packaged modules :>(

Regards,

Richard Duivenvoorde

On 21-11-15 23:31, Brian May wrote:
> Hello,
> 
> Just for reference, you should perhaps send emails like this to
> debian-python@lists.debian.org - the
> python-modules-t...@lists.alioth.debian.org is intended for
> automatically generated emails. I have CCed
> debian-python@lists.debian.org.
> 
> 
> Richard Duivenvoorde <rich...@duif.net> writes:
> 
>> Hi,
>>
>> not sure how to add an issue for packaging.
>>
>> but I'm directed via
>>
>> https://github.com/docker/compose/issues/2433#issuecomment-158448859
>>
>> to the Debian packaging team
>>
>> Please guide me to another issue tracker system if needed.
> 
> Please see the following page on reporting bugs in Debian:
> https://www.debian.org/Bugs/Reporting
> 
> 
>> In short:
>>
>> docker-compose
>>
>> Traceback (most recent call last):
>>   File "/usr/bin/docker-compose", line 9, in
>> load_entry_point('docker-compose==1.5.1', 'console_scripts',
>> 'docker-compose')()
>>   File "/usr/lib/python2.7/dist-packages/pkg_resources/__init__.py",
>> line 558, in load_entry_point
>> return get_distribution(dist).load_entry_point(group, name)
>>   File "/usr/lib/python2.7/dist-packages/pkg_resources/__init__.py",
>> line 2682, in load_entry_point
>> return ep.load()
>>   File "/usr/lib/python2.7/dist-packages/pkg_resources/__init__.py",
>> line 2355, in load
>> return self.resolve()
>>   File "/usr/lib/python2.7/dist-packages/pkg_resources/__init__.py",
>> line 2361, in resolve
>> module = __import__(self.module_name, fromlist=['__name__'], level=0)
>>   File "/usr/lib/python2.7/dist-packages/compose/cli/main.py", line 16, in
>> from ..config import ConfigurationError
>>   File "/usr/lib/python2.7/dist-packages/compose/config/__init__.py",
>> line 2, in
>> from .config import ConfigurationError
>>   File "/usr/lib/python2.7/dist-packages/compose/config/config.py", line
>> 14, in
>> from .validation import validate_against_fields_schema
>>   File "/usr/lib/python2.7/dist-packages/compose/config/validation.py",
>> line 7, in
>> from docker.utils.ports import split_port
>> ImportError: No module named ports
> 
> This works for me...
> 
> (sid-amd64)root@prune:/home/brian/tree/spud/spud# python
> Python 2.7.10+ (default, Oct 10 2015, 09:11:24) 
> [GCC 5.2.1 20151028] on linux2
> Type "help", "copyright", "credits" or "license" for more information.
>>>> from docker.utils.ports import split_port
> 
> 
> Are you sure you do have 1.5.0-1 of python-docker installed?
> 
> (sid-amd64)root@prune:/home/brian/tree/spud/spud# dpkg -l python-docker
> Desired=Unknown/Install/Remove/Purge/Hold
> | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
> |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
> ||/ Name  Version Architecture
> Description
> +++-=-=======-===-===
> ii  python-docker 1.5.0-1 all 
> Python wrapper to access docker.io's control socket
> 
> 
> The "apt-cache show python-docker" shows what version of python-docker
> is available, it doesn't say what version is installed.
> 
> docker-compose has a dependancy on "python-docker (>= 1.3.0)" so maybe
> you have an old version of python-docker?
> 
> 
>> Regards,
>>
>> Richard Duivenvoorde