Finally a Patch that works!
Male sexual enhancement formula http://www.asdokm.com/ss/ The moment we choose to love we begin to move towards freedom... The drug that heals our sorrows forgetfulness. Law is mind without reason. As a matter of principle, I never attend the first annual anything. America, why are your libraries full of tears? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Ihanot received any response in regards the funds transfer Re urgently
¡Tengo nueva dirección de correo!Ahora puedes escribirme a: [EMAIL PROTECTED] - RICHARD OPENE
Re: RFS: nautilus-clamscan
Clement Lorteau wrote: .. Your GPG key is not signed by anyone. You should try to meet someone that can sign it, preferably a DD or someone whose key is signed by a DD. Look at this page: https://nm.debian.org/gpg.php If you live in Paris or near Paris, I can sign your key. I do live near Paris. I'll contact you in private. However, is the key signing needed for uploading the package? I had 2 versions of another package uploaded without having to have my key signed. If I were intimately familiar with a package and had looked at EVERYTHING, I would be comfortable uploading a package signed with an unverified key. But that is a lot of work (and I am basically asking everyone to hold me accountable for any problems ;-). It is much more likely that I would not duplicate someone else's effort. When I decide to accept what someone else has done, then it become much more important to be able to identify that person. At the point where I might want to say I got code from someone else, the signed key becomes critical. I could upload a package that was sent with an unverified key, but that would speak volumes about my judgement. When I sign a package (or another key for that matter), a person can rely on my judgement as input. I do not promote worthless input. It should be easy to understand why a person would hesitate to accept an unverified key since it could make their judgement worthless. Richard -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Request to join PMPT and add python-lzma
Hello, I'd like to join the DPMT. My alioth username is mrbeige-guest. This is in response to #556451, an ITP I just filed for python-lzma (https://launchpad.net/pyliblzma). Thanks to the help of Kumar Appaiah, Clint Adams, and others in #debian-nyc, I have a package ready here: http://rkd.zgib.net/debian/ They've gone over it fairly thoroughly, but please let me know any other comments on the package. I'd like to add this to group maintenance, with maintainer set to DPMT (but I will still take responsibility for keeping it up to date). I know, at the least, that the copyright file needs the special form added. Thank you, - Richard -- | Richard Darst - rkd@ - boltzmann: up 118 days, 11:22 |http://rkd.zgib.net - pgp 0xBD356740 | "Ye shall know the truth and -- the truth shall make you free" signature.asc Description: Digital signature
Request for review/sponsorship of python-lzma
Hello, I worked with kmap last night to get my package of python-lzma (in DPMT svn) in shape. We think it's good, and he suggested I email here for further review and possibly sponsorship (to experimental since it depends on 2.6). If there's anything else I can/should do, please let me know. Thank you, - Richard -- | Richard Darst - rkd@ - boltzmann: up 123 days, 10:18 |http://rkd.zgib.net - pgp 0xBD356740 | "Ye shall know the truth and -- the truth shall make you free" -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: Request for review/sponsorship of python-lzma
On Sat, Nov 21, 2009 at 10:02:23AM -0600, Kumar Appaiah wrote:
> Dear Richard,
>
> On Sat, Nov 21, 2009 at 08:26:00AM -0500, Richard Darst wrote:
> > I worked with kmap last night to get my package of python-lzma (in
> > DPMT svn) in shape. We think it's good, and he suggested I email here
> > for further review and possibly sponsorship (to experimental since it
> > depends on 2.6).
Thanks for the review. I've fixed these things in the svn. Some of
them were caused by me not understanding the debhelper system just
yet.
> debian/copyright:
> * Licensed under LGPLv3+
> * Please add license headers too.
Is license headers the DEP5 things? I have them at the bottom of
debian/copyright, but I didn't see anything that said if or how they
have to be separated...
> debian/rules:
> * debhelper >= 7.3.5 has automatic support for building extensions for
> every supported Python version, so overriding dh_auto_* should be
> omitted.
I removed the overrides. However, I left in the dh_auto_test
override, since the python_distutils debhelper system doesn't seem to
support it.
> In addition, I observed that the package, when built, is currently
> uninstallable, even with the Python from experimental. The reason is
> that ${python:Depends} expands to python (>= 2.6), which is currently
> unsatisfiable, as the version of the "python" package in experimental
> is 2.5.4-3:
Hm. When it build for me, it expanded to "python (>= 2.6) |
python2.6" which does work because of the or operation. Is this
expected?
Thanks for the reviews,
- Richard
--
| Richard Darst - rkd@ - boltzmann: up 125 days, 3:05
|http://rkd.zgib.net - pgp 0xBD356740
| "Ye shall know the truth and -- the truth shall make you free"
--
To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: Request for review/sponsorship of python-lzma
On Mon, Nov 23, 2009 at 06:58:07PM +1100, Ben Finney wrote: > Richard Darst writes: > > > On Sat, Nov 21, 2009 at 10:02:23AM -0600, Kumar Appaiah wrote: > > > debian/copyright: > > > * Licensed under LGPLv3+ > > > * Please add license headers too. > > The header of a DEP 5 copyright file doesn't discuss licenses. What > Kumar seems to be referring to here is the fields in the body stanzas of > that file; you should write enough Files stanzas to cover all the > copyright terms of the work. I thought I had this, since it says the first license stanza defaults to "Files: *". I made it explicit now. Also, the source files with a copyright notice also include the authors of liblzma and the LZMA SDK, even though (as far as I can tell) it doesn't use any source from these things, so I left them out of the debian/copyright file. > > I have them at the bottom of debian/copyright, but I didn't see > > anything that said if or how they have to be separated... > > Have a closer read of DEP 5; it describes a header (describing the > package as a whole), and then a body with multiple stanzas. The header > is separated from the body by a blank line, and each stanza in the body > is separated from then next by a blank line. > > DEP 5 also forbids anything in that file which *isn't* the header or the > body stanzas; if you're going to conform with DEP 5, put all the > information into the structured format described there. I removed the extra non-DEP5 stuff at the top, and tried to tighten it up to strictly match what it says. There were some quirks, such as the required "Format-Specification" field not being present in any examples... I think that I've interpreted it strictly enough now that it should be correct. Here is the latest: http://svn.debian.org/wsvn/python-modules/packages/python-lzma/trunk/debian/copyright Anything else I can do to the package? Thanks, - Richard -- | Richard Darst - rkd@ - boltzmann: up 125 days, 9:19 |http://rkd.zgib.net - pgp 0xBD356740 | "Ye shall know the truth and -- the truth shall make you free" -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#566905: ITP: python-ctypeslib -- code generator to convert header files into ctypes interfaces
Package: wnpp Severity: wishlist Owner: Richard Darst * Package name: python-ctypeslib Version : 0.0.cvs20100125 Upstream Author : Thomas Heller * URL : http://starship.python.net/crew/theller/ctypes/ * License : MIT Programming Lang: Python Description : code generator to convert header files into ctypes interfaces ctypeslib is a code generator capable of converting C header files into xml files (using gccxml), and then converting the xmlfiles into Python modules which define a ctypes interface to the corresponding C library. -- System Information: Debian Release: 5.0.3 APT prefers stable APT policy: (500, 'stable') Architecture: i386 (i686) -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Requesting review of python-ctypeslib
Hello, I would like to request a review of my new packages python-ctypeslib: http://hcoop.net/~rkd/debian/python-ctypeslib_0.0.0+svn20100125-1.dsc or via PMPT: svn+ssh://svn.debian.org/svn/python-modules/packages/python-ctypeslib/trunk There are two executables which need manual pages still, otherwise it is lintian clean. Note: ctypeslib is not ctypes. Ctypeslib is an add on for ctypes which automatically generates ctypes interfaces from C header files. If you are interested in how this works, the examples.Debian is here: http://paste.debian.net/58466 . Thanks, - Richard (MrBeige @ oftc) -- | Richard Darst - rkd@ - boltzmann: up 196 days, 13:12 |http://rkd.zgib.net - pgp 0xBD356740 | "Ye shall know the truth and -- the truth shall make you free" -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Python talks at DebConf
Hello, I was looking through the talks submitted to DebConf, and noticed there weren't very many Python related talks. Given the amount there is to discuss related to Python in Debian, it would be great to see some more submissions. Perhaps the list can suggest some talks and we can nominate some people to lead them? At least we should have a talk on Python packaging and one on packaging helpers. Perhaps there could be talks on the DPMT or PAPT. Any more ideas? Also, the DebConf talks team (which I'm not especially a part of) recently made a call for "tracks" of related talks. The idea behind a track is to have a track coordinator, who works with the DebConf talks and scheduling teams to produce a coordinated series of talks. It would be great if there was a Python track. For the informational mail on this, please see http://lists.debconf.org/lurker/message/20100430.191031.1c01ddf4.en.html (Unfortunately, I'm too busy with the conference itself to help with these talks, but can answer any questions on submission and selection and so on.) - Richard -- | Richard Darst - rkd@ - boltzmann: up 286 days, 16:37 |http://rkd.zgib.net - pgp 0xBD356740 | "Ye shall know the truth and -- the truth shall make you free" -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100504202016.gd10...@boltzmann.zgib.net
Re: [Python-modules-team] python-docker issue?
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 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
Joining
Hi, I would like to join the team, in order to maintain my current packages within the team. My alioth login is : ulrichard-guest I have read the policy and accept it. Rgds Richard -- Meine Kontaktdetails sind immer aktuell in der NameCoin blockchain mit der Kennung: id/ulrichard Teile davon sieht man mit folgendem Link: https://nameid.org/?name=ulrichard Bitte schicken Sie mir wenn möglich PGP/GPG verschlüsselte Nachrichten. signature.asc Description: This is a digitally signed message part
Re: Seeking a small group to package Apache Arrow (was: Bug#970021: RFP: apache-arrow -- cross-language development platform for in-memory analytics)
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
pysnmp should follow lextudio/pysnmp?
At $DAYJOB, I ended up going down a long rabbit hole starting with python3-pysnmp4 not being updated for the importlib changes in Python 3.11. This was an issue for me on Ubuntu 24.04. It seems to NOT be an issue on sid (for reasons I do not fully understand), even in a fresh chroot, so I'm not filing a Debian bug about it. So at this point, I'm just writing to point out the PyPI points "pysnmp" to: https://github.com/lextudio/pysnmp The last change on that project is from a month ago, and it has a fix for this bug. In other words, it appears to be actively maintained. I looked on Salsa: https://salsa.debian.org/python-team/packages/python-pysnmp4/ I see some unreleased changes that reference: https://github.com/pysnmp/pysnmp The last change there is from over a year ago, and it does not have a fix for this bug. So, at a glance, it seems like you should follow lextudio/pysnmp like PyPI does. Of course, I've only looked at this for an hour, so you might have more information. I just wanted to mention lextudio/pysnmp (and PyPI referencing it) in case you were not aware. -- Richard OpenPGP_signature.asc Description: OpenPGP digital signature
Re: Bug#936613: ginac: Python2 removal in sid/bullseye
On 10.09.19 20:40, Matthias Klose wrote: >> If the python command isn't going to be python3, then I'll update the >> build-dependencies ASAP. And then this fact ought to be prominently >> documented and explained in the instructions so to support this >> transition. > > please do. and feel free to clarify the wiki page. Done. -richy.
