Re: Help wanted to convert Archmage to Python 3
On Fri, May 3, 2019 at 11:36 PM Robert-André Mauchin wrote: > Hello, > > patool FTBFS depends on Archmage, which is Python 2 only. > I'm trying to convert it to Python 3. > > So far I have the dependency pychm converted: > https://copr.fedorainfracloud.org/coprs/eclipseo/pythontests/build/903162/ > > Here's my Py3 port with 2to3 and minor fixes: > https://github.com/eclipseo/archmage/tree/python3_port > > The problem is it doesn't work as expected: > > $ archmage -x t.chm > > Traceback (most recent call last): > File "/usr/bin/archmage", line 11, in > load_entry_point('archmage==0.3.1', 'console_scripts', 'archmage')() > File "/usr/lib/python3.7/site-packages/archmod/cli.py", line 161, in main > CHMFile(options.chmfile) or CHMDir(options.chmfile) > File "/usr/lib/python3.7/site-packages/archmod/Cached.py", line 34, in > __new__ > __instance = object.__new__(classtype, *args, **kwargs) > TypeError: object.__new__() takes exactly one argument (the type to > instantiate) > > I haven't touched archmod/Cached.py code, and as far as I know the > object.__new__() > method has not changed from Python 2 to Python 3 so I don't get why it's > not > working anymore. > Can anyone with more Python chops help me? > I took a quick look: - You'll probably have to update to beautifullsoup4 (shouldn't be too hard). - Depends on python2-chm, we don't have a python3-chm in Fedora (Haven't checked if it is supported). Piotr ___ python-devel mailing list -- python-devel@lists.fedoraproject.org To unsubscribe send an email to python-devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/python-devel@lists.fedoraproject.org
Orphaning nodejs packages
I've orphaned the following nodejs packages. I do not have time to maintain them any more. nodejs-onetime nodejs-oop nodejs-opn nodejs-pac-proxy-agent nodejs-pac-resolver nodejs-param-case nodejs-parserlib nodejs-pascal-case nodejs-path-case nodejs-path-exists nodejs-pend nodejs-pify nodejs-portscanner nodejs-private nodejs-proxy nodejs-recast nodejs-regenerator nodejs-relateurl nodejs-requestretry nodejs-require-directory nodejs-run-parallel-limit nodejs-safe-buffer nodejs-samsam nodejs-saucelabs nodejs-sauce-tunnel nodejs-sentence-case nodejs-set-immediate-shim nodejs-should-promised nodejs-sinon nodejs-smart-buffer nodejs-snake-case nodejs-socks-client nodejs-socks-proxy-agent nodejs-st nodejs-std-mocks nodejs-stream-equal nodejs-streamsink nodejs-stream-to-array nodejs-string nodejs-stringstream nodejs-strip-indent nodejs-supports-color nodejs-swap-case nodejs-tar-stream nodejs-title-case nodejs-tough-cookie nodejs-upper-case nodejs-upper-case-first nodejs-util nodejs-vary nodejs-verror nodejs-xregexp nodejs-yargs nodejs-zip-stream nodejs-after nodejs-alter nodejs-ansidiff nodejs-ansi-font nodejs-archiver nodejs-archiver-utils nodejs-array-union nodejs-array-uniq nodejs-arrify nodejs-astral nodejs-astral-angular-annotate nodejs-astral-pass nodejs-ast-traverse nodejs-ast-types nodejs-async-cache nodejs-async-each nodejs-aws-sign2 nodejs-base64-js nodejs-basic-auth-parser nodejs-bl nodejs-bluebird nodejs-breakable nodejs-camel-case nodejs-caniuse-db nodejs-change-case nodejs-clean-css nodejs-clone nodejs-cls nodejs-co nodejs-commoner nodejs-compress-commons nodejs-console-browserify nodejs-constant-case nodejs-crc32-stream nodejs-dashdash nodejs-date-now nodejs-deferred nodejs-defs nodejs-degenerator nodejs-domelementtype nodejs-domhandler nodejs-dom-serializer nodejs-domutils nodejs-dot-case nodejs-dreamopt nodejs-each-async nodejs-entities nodejs-etag nodejs-extend nodejs-extsprintf nodejs-far nodejs-fd nodejs-fg-lodash nodejs-file-uri-to-path nodejs-fn-name nodejs-forever-agent nodejs-formatio nodejs-fs2 nodejs-ftp nodejs-generate-function nodejs-generate-object-property nodejs-get-stdin nodejs-get-uri nodejs-grunt-angular-templates nodejs-grunt-contrib-connect nodejs-grunt-contrib-cssmin nodejs-grunt-contrib-htmlmin nodejs-grunt-contrib-less nodejs-grunt-contrib-requirejs nodejs-grunt-known-options nodejs-grunt-saucelabs nodejs-grunt-util-args nodejs-grunt-util-options nodejs-grunt-util-process nodejs-grunt-util-property nodejs-har-validator nodejs-hash_file nodejs-hock nodejs-html-minifier nodejs-https-proxy-agent nodejs-install nodejs-is-lower-case nodejs-is-my-json-valid nodejs-is-property nodejs-isstream nodejs-istanbul nodejs-is-typedarray nodejs-is-upper-case nodejs-jison nodejs-jsonpointer nodejs-lazystream nodejs-log-symbols nodejs-lolex nodejs-lower-case nodejs-lower-case-first nodejs-mkfiletree nodejs-multiline nodejs-next nodejs-node-int64 nodejs-npmlog ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: Need help on kickstarting my Open Source Contribution
On Sat, Jan 26, 2019 at 6:02 PM Rajeshkumar Pothiappan < rajeshkuma...@fedoraproject.org> wrote: > Hi Fedora Python Team, I am a developer, I can code in Python. I am > interested in contributing to Fedora as a Developer. I have read few > guides/wiki. Still I need someone to guide atleast till I make my first > contribution. > Can some one please guide me.. ,With minimal guidance on > 1. what to do > 2. where to refer > 3. Is any specific procedure to do that task, > It really depends on what you want to do, what your interests are, etc. Fedora infrastructure uses a lot of Python software which you could contribute to. There is a list of "easy fixes" [1]. Most projects are hosted on github, so you basically just need a github account, clone/fork the repo, fix the issue and create a PR. [1] https://fedoraproject.org/easyfix/ Piotr ___ python-devel mailing list -- python-devel@lists.fedoraproject.org To unsubscribe send an email to python-devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/python-devel@lists.fedoraproject.org
Orphaning Node.js module packages
I'm orphaning: nodejs-proxy-agent nodejs-superagent-proxy nodejs-grunt-html-validation nodejs-fd-slicer nodejs-test nodejs-agent-base nodejs-colors They FTBFS and I don't have time to fix them and don't use them any more. Piotr ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/UBRFCMGOY3WIYMB4QSIBGZ2GZUREGVEY/
Re: Django 2.0 released, and what it means to you
On Wed, Dec 6, 2017 at 12:36 PM, Nicolas Chauvetwrote: > 2017-12-06 10:26 GMT+01:00 Matthias Runge : > > On Wed, Dec 06, 2017 at 09:56:28AM +0100, Lumir Balhar wrote: > >> On 12/05/2017 04:27 PM, Miro Hrončok wrote: > >> > Maybe a Fedora Change coordinating this would be nice? > > > > probably a good idea. > > > >> > Those are packages that require python(2)-django and are themselves > not > >> > prefixed with python(2)-django: > >> > > >> > graphite-web > Last week a patch got merged to Graphite-web to support Python 3. Not sure when Django 2 will be supported. ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Re: Missing executables in Python 3 subpackages
On Thu, Mar 2, 2017 at 6:06 PM, Iryna Shcherbinawrote: > Hi all, > > According to the Fedora Packaging guidelines for Python [0], if a Python > package that supports Python 3 installs executables into */usr/bin*, then > either both Python versions of the executables should be packaged, or only > the Python 3 version, depending on the functionality they provide. > > However, after going through all Python 3-compatible packages for Fedora, > we have identified up to ~30 packages which provide both python2- and > python3- subpackages with executables available only in the Python 2 > version. For more information about obtaining the list refer to the > GitHub issue [1]. The list of the affected packages is available here [3]. > > Before doing mass bug filing, I would like to post the list of packages > here, to get feedback or ideas on how this can be fixed in a better way and > encourage packagers to do the changes. If you are in Cc, then you are > owing at least one of the affected packages. The guide for porting > Python-based RPMs is available here [2] and you may refer to it for more > instructions. > > python-whisper > whisper as library is python3 compatible, the executables not yet (AFAIK). Piotr ___ python-devel mailing list -- python-devel@lists.fedoraproject.org To unsubscribe send an email to python-devel-le...@lists.fedoraproject.org
Re: Missing executables in Python 3 subpackages
On Thu, Mar 2, 2017 at 6:06 PM, Iryna Shcherbinawrote: > Hi all, > > According to the Fedora Packaging guidelines for Python [0], if a Python > package that supports Python 3 installs executables into */usr/bin*, then > either both Python versions of the executables should be packaged, or only > the Python 3 version, depending on the functionality they provide. > > However, after going through all Python 3-compatible packages for Fedora, > we have identified up to ~30 packages which provide both python2- and > python3- subpackages with executables available only in the Python 2 > version. For more information about obtaining the list refer to the > GitHub issue [1]. The list of the affected packages is available here [3]. > > Before doing mass bug filing, I would like to post the list of packages > here, to get feedback or ideas on how this can be fixed in a better way and > encourage packagers to do the changes. If you are in Cc, then you are > owing at least one of the affected packages. The guide for porting > Python-based RPMs is available here [2] and you may refer to it for more > instructions. > > python-whisper > whisper as library is python3 compatible, the executables not yet (AFAIK). Piotr ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Re: Touchpad pointer accel - testers required, scratch build available
On Fri, Feb 24, 2017 at 12:35 AM, Peter Huttererwrote: > I've been playing with touchpad pointer acceleration in libinput again and > finally found something I'm happy with. Most notably it has a wide range of > configurable speed settings, from "tar" to "speed-skating ring". Please > give > this scratch build a test and let me know how you go: > https://koji.fedoraproject.org/koji/taskinfo?taskID=17546245 > > After installing it feels more accurate with small movements, which is an improvement. On both versions the acceleration could be larger for me, I cannot move the pointer from one corner of the screen to the opposite one with one finger movement. The touchpad speed slider in mouse and touchpad settings is on max already. This is on a Dell XPS 13 9360 with HiDPI screen. Piotr ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Re: Some of my packages are looking for new (co-)maintainers
On 09/01/2016 09:59 PM, Raphael Groner wrote: > HI, > > I'll orphan some of my packages due to lack of available time to properly > maintain them: > - rpms/bats -- Bash Automated Testing System ( master f25 f24 f23 epel7 el6 ) I'll take bats piotr -- devel mailing list devel@lists.fedoraproject.org https://lists.fedoraproject.org/admin/lists/devel@lists.fedoraproject.org
Re: Orphaned packages seeking new point of contact
On 07/29/2016 07:21 PM, Kevin Fenzi wrote: > Greetings. > #topic #1607 Orphan package for "patches" > .fesco 1607 > https://fedorahosted.org/fesco/ticket/1607 I've assigned nodejs packages which have dependencies to group::nodejs-sig. > compat-libuv010 (f23) > compat-libuv010 (f24) > compat-libuv010 (f25) > compat-libuv010 (master) Needed in f23 for nodejs 0.10 f23, f24: assigned to group::nodejs-sig retired in f25 and rawhide > node-gyp (el6) > node-gyp (epel7) > node-gyp (f23) > node-gyp (f24) > node-gyp (f25) > node-gyp (master) Assigned to group::nodejs-sig I'm not sure if we still need this. > npm (el6) > npm (epel7) > npm (f23) > npm (f24) Was already retired, assigned active branches to nodejs-sig. > uglify-js1 (el6) > uglify-js1 (epel7) > uglify-js1 (f23) > uglify-js1 (f24) > uglify-js1 (f25) > uglify-js1 (master) Assigned to nodejs-sig, some modules still use this. > web-assets (el5) > web-assets (el6) > web-assets (epel7) > web-assets (f23) > web-assets (f24) > web-assets (f25) > web-assets (master) Assigned to nodejs-sig web-assets-filesystem is used by many modules as buildrequires. > ycssmin (el6) > ycssmin (epel7) > ycssmin (f23) > ycssmin (f24) > ycssmin (f25) > ycssmin (master) assigned to nodejs-sig Piotr signature.asc Description: OpenPGP digital signature -- devel mailing list devel@lists.fedoraproject.org https://lists.fedoraproject.org/admin/lists/devel@lists.fedoraproject.org
[EPEL-devel] Re: Python 2 macros on EL 6
On 04/19/2016 06:37 AM, Sérgio Basto wrote: > Hi, > %{python2_sitelib} doesn't exist on epel6 ? This needs to be defined in epel6, see: https://fedoraproject.org/wiki/Packaging:Python_Old#Macros Piotr ___ epel-devel mailing list epel-devel@lists.fedoraproject.org http://lists.fedoraproject.org/admin/lists/epel-devel@lists.fedoraproject.org
Re: stalled package review
On Mon, Dec 7, 2015 at 9:40 PM, Jos de Kloewrote: > This package review: https://bugzilla.redhat.com/show_bug.cgi?id=751749 > has been stalled for several years now since the original submitter > (Karel Klíč) never got back to it, even though the review was approved. > > Since it is not packaged yet, the nonresponsive package maintainers > policy does not apply I think. So can someone else just step in and > package it, or should the review be redone in this case? > https://fedoraproject.org/wiki/Policy_for_stalled_package_reviews > > Jos. > -- > devel mailing list > devel@lists.fedoraproject.org > http://lists.fedoraproject.org/admin/lists/devel@lists.fedoraproject.org -- devel mailing list devel@lists.fedoraproject.org http://lists.fedoraproject.org/admin/lists/devel@lists.fedoraproject.org
Re: Mod_selinux for EPEL
On 08/04/2015 12:56 AM, William Brown wrote: I'm not a package maintainer at this point. This would be my first package, which is also why I'm asking for help with this process. Sincerely, You will need to be sponsored to the packager group first. You can start with a new package or try to co-maintain one, see [1]. It seems that Kaigai is not a sponsor so you will need to find another sponsor. You could also create a bug in bugzilla to request the epel package. [1]: https://fedoraproject.org/wiki/How_to_get_sponsored_into_the_packager_group -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Mod_selinux for EPEL
On 08/03/2015 05:25 AM, William Brown wrote: Hi, I have attempted to contact Kaigai about doing the work to get mod_selinux into EPEL. Sadly, he hasn't responded to me in a few months about this topic. Would someone be able to help guide me through the process of getting this package into EPEL? I'm happy to co-maintain it if that's what's required. If you already are a package maintainer you can request a new branch in pkgdb. Branches are created after about 7 days with no objection from other maintainters. Piotr -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
carbon-c-relay review swap
I am looking for a review for carbon-c-relay and offering a review swap, I really want to get this in. https://bugzilla.redhat.com/show_bug.cgi?id=1190390 I've also got some nodejs module review requests pending, also doing a review swap for any of them: https://tinyurl.com/oeyju9l (this has lower priority than carbon-c-relay) regards, Piotr -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Self Introduction: Piotr Popieluch
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi All, My name is Piotr Popieluch and live in the Hague in the Netherlands. I work as a Unix sysadmin with focus on monitoring. I manage rhel boxes professionally and use Fedora on my laptop. Because of this I want to give back and want to become a Fedora package maintainer. I've packaged two packages, python-structlog and graphite-api which depends on the former. I need a sponsor. python-structlog: https://bugzilla.redhat.com/show_bug.cgi?id=1154213 graphite-api: https://bugzilla.redhat.com/show_bug.cgi?id=1154218 I've done one unofficial review: https://bugzilla.redhat.com/show_bug.cgi?id=1151759 Kind regards, Piotr -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQIcBAEBAgAGBQJUQZr6AAoJEPHEApzE46n5CHwQAJVmvPbXE3ha0Z+ksc65znBE 2+Q4aAoPkoiQQvfkG6svSqSeMm4qgwHlLjx2qKqZa8mwYfbUdJTb82xzyQL46nyn iocPlaml3n9wHWBWV2dqhKCHsOfckpoyYHlnKDT+9veHVD0GPZR6zqoF1lFhGgwf kLWIvBmPQrXIRT/iQoxxmV/SByivHVbXuwlouBDaeeTAsFojvinHwboTA9dHyMra hzvu67BpqtWHA+bfg47J0ITzqk747uDKzbESfgBxgTd2ZaipWI7918h/HhVhxaCp 0gHdqDwmp09Tbz04Fnuo/ttM25Cbg+Jo2G9phXy6wGhu+A8e/9iPwvMbBQP4oX+A u1eSV5m9szar8UMAuE6brZj4iafLRdUu7ANjIgYU6k12c7Vlo97YthWoIv9YBSoH W57aXelqYlikXlPGjt3tkFQcC/yqYBjkdmdnHtcLFKedqy3KyDzlGIWM+09ED8wF pl+O5KJjEZxVzS+bmicEa+9XqMhhsbmEB6xO7tf6XgeDyy3hcUECyu7PKOgYjTDf VbeVC2uHOKQ7IDnW8fVBmPXIChSnYFkmELtxXWe0vKOEwK5xhI5ff2g13wcUc6id 4AswWnZVVIb5jtqZ62xAe4ZyVX2BoWWSi52oMkpGzx4wfm4Hc2WKDD3j2FiWPSbs tkSpG/EFwh5STP0mfxX/ =m6KS -END PGP SIGNATURE- -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct