joining python team
Hi all, I think I once was member of this team and had some packages, but seemingly in some reorganization this was lost. Could you please add me (salsa: preining) to the Debian package team. I am currently updating python-zeroconf which is needed for newer calibre. I have read the python policy. Best Norbert -- PREINING Norbert https://www.preining.info Fujitsu Research + IFMGA Guide + TU Wien + TeX Live + Debian Dev GPG: 0x860CDC13 fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13 signature.asc Description: PGP signature
Re: FWD: [debian-python on Calibre] Non-migration of cssutils
Hi Nicholas, thanks for your email. On Thu, 06 Feb 2020, Nicholas D Steeves wrote: > It doesn't look like these test failures on non-x86 will go away by > themselves, though. Somebody will have to figure out what's wrong > and fix them eventually. Forwarded upstream https://bugs.launchpad.net/calibre/+bug/1862234 Best Norbert -- PREINING Norbert http://www.preining.info Accelia Inc. + IFMGA ProGuide + TU Wien + JAIST + TeX Live + Debian Dev GPG: 0x860CDC13 fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13
Re: updating mechanize - help concerning tests with pybuild
Dear Arnaud, thanks a lot for agreeing, and all your work on mechanize! All the best Norbert On Mon, 02 Sep 2019, Arnaud Fontaine wrote: > As I have no plan to work on it, I think it is better if someone else > maintains it, so please go ahead and thanks for taking over maintenance! -- PREINING Norbert http://www.preining.info Accelia Inc. + IFMGA ProGuide + TU Wien + JAIST + TeX Live + Debian Dev GPG: 0x860CDC13 fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13
Re: updating mechanize - help concerning tests with pybuild
Hi all, On Sun, 01 Sep 2019, Norbert Preining wrote: > Done that now, and removed the last lintian warning. And now also - fixed building in clean chroot (missing build deps for tests and run) - install docs made via sphinx - updated copyright file to match what is advertised in the package Package is uploaded to experimental as it needs to go through NEW queue ... oh holy , uploads that need the NEW queue need to include the binaries, right? Advertising source only uploads and then requiring NEW queue processing to include binaries is **really** ?#$(
Re: updating mechanize - help concerning tests with pybuild
Dear Raphael, > Maybe you could have bumped debhelper to 12 and standards-version to 4.4.0 Done that now, and removed the last lintian warning. Uploading later today. All the best Norbert -- PREINING Norbert http://www.preining.info Accelia Inc. + IFMGA ProGuide + TU Wien + JAIST + TeX Live + Debian Dev GPG: 0x860CDC13 fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13
Re: updating mechanize - help concerning tests with pybuild
Dear Matthias Thanks, I interpret this a go ahead with the adoption. Thanks for your and the teams work. At all: anything you want to see before I upload the new version? Best Norbert On September 1, 2019 9:43:33 AM GMT+09:00, Matthias Klose wrote: >On 01.09.19 01:59, Norbert Preining wrote: >> Hi Raphael, >> >> @Matthias, please read on. >> >> On Sat, 31 Aug 2019, Raphael Hertzog wrote: >>> https://salsa.debian.org/python-team/modules/python-mechanize >> >> Thanks, that is perfect. I pushed my work there, changed control VCS, >> maintainer, and uploader. >> >> ATM I only put me into the uploaders. Please, those who are >interested, >> put yourself in there, thanks! >> >>>> Do we go through package salvaging? >>>> https://wiki.debian.org/PackageSalvaging >>> >>> I don't think it's required here. The bugs have been open for long >enough >>> without any activity. >> >> Hmmm... I don't feel confident simply uploading someone's else >package. >> Best would probably be if Matthias Klose, one of the current >Uploaders, >> agrees to that and uploads the current package thus passing over >> maintainership. >> >> Matthias? > >did you see my comment in #936270? -- PREINING Norbert http://www.preining.info Accelia Inc. + JAIST + TeX Live + Debian Developer GPG: 0x860CDC13 fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13
Re: updating mechanize - help concerning tests with pybuild
Hi Raphael, @Matthias, please read on. On Sat, 31 Aug 2019, Raphael Hertzog wrote: > https://salsa.debian.org/python-team/modules/python-mechanize Thanks, that is perfect. I pushed my work there, changed control VCS, maintainer, and uploader. ATM I only put me into the uploaders. Please, those who are interested, put yourself in there, thanks! > > Do we go through package salvaging? > > https://wiki.debian.org/PackageSalvaging > > I don't think it's required here. The bugs have been open for long enough > without any activity. Hmmm... I don't feel confident simply uploading someone's else package. Best would probably be if Matthias Klose, one of the current Uploaders, agrees to that and uploads the current package thus passing over maintainership. Matthias? Best Norbert -- PREINING Norbert http://www.preining.info Accelia Inc. + IFMGA ProGuide + TU Wien + JAIST + TeX Live + Debian Dev GPG: 0x860CDC13 fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13
Re: updating mechanize - help concerning tests with pybuild
Hi Raphael, On Sat, 31 Aug 2019, Raphael Hertzog wrote: > Thus I would suggest to go ahead and take over the package in the DPMT > team. Fine with me. If you could give me DPMT membership on salsa I can push my current work there. Do we go through package salvaging? https://wiki.debian.org/PackageSalvaging Best Norbert -- PREINING Norbert http://www.preining.info Accelia Inc. + IFMGA ProGuide + TU Wien + JAIST + TeX Live + Debian Dev GPG: 0x860CDC13 fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13
Re: updating mechanize - help concerning tests with pybuild
On Sat, 31 Aug 2019, Dmitry Shachnev wrote:
> http_proxy= no_proxy= dh_auto_test -- --system custom --test-args "cd
> {build_dir}; {interpreter} run_tests.py"
Cool, thanks a big lot
BTW, why isn't that mentioned anywhere in the pybuild docs ...
Thanks
Norbert
--
PREINING Norbert http://www.preining.info
Accelia Inc. + IFMGA ProGuide + TU Wien + JAIST + TeX Live + Debian Dev
GPG: 0x860CDC13 fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13
Re: updating mechanize - help concerning tests with pybuild
Dear Dmitry
thanks for your email!
On Sat, 31 Aug 2019, Dmitry Shachnev wrote:
> - Add run_tests.py and the tests themselves to debian/pybuild.testfiles,
> to make pybuild copy them to the build directory.
>
> - Add override_dh_auto_test target with a command like this:
> dh_auto_test -- --system custom --test-args "{interpreter} run_tests.py"
Ok, I have done this and added the necessary files. Interestingly, I
*still* get errors:
Testing manually in the root:
$ pwd
.../mechanize.git
$ ls
... examples mechanize test test-tools ...
$ python2.7 run_tests.py
...
--
Ran 303 tests in 6.048s
OK
Testing manually in the build directory
$ pwd
.../mechanize.git/.pybuild/cpython2_2.7_mechanize/build
$ ls
... examples mechanize test test-tools ...
$ python2.7 run_tests.py
...
--
Ran 303 tests in 5.960s
OK
Finally doing dpkg-buildpackage or whatever
debian/rules override_dh_auto_test-indep
make[1]: Entering directory '/home/norbert/Development/calibre/mechanize.git'
dh_auto_test -- --system custom --test-args "{interpreter} run_tests.py"
pybuild --test -i python{version} -p 2.7 --system custom --test-args
"{interpreter} run_tests.py"
I: pybuild base:217: python2.7 run_tests.py
.E...EEE.EEF.E.EEE.EE.EE..FF...
Now, the interesting thing are the error messages. One of them is
ERROR: test_mozilla_cookiejar (test.test_functional.CookieJarTests)
--
Traceback (most recent call last):
File
"/home/norbert/Development/calibre/mechanize.git/test/test_functional.py", line
684, in test_mozilla_cookiejar
self._test_cookiejar(make_cookiejar, commit)
File
"/home/norbert/Development/calibre/mechanize.git/test/test_functional.py", line
654, in _test_cookiejar
html = br.open(url).read()
File
"/home/norbert/Development/calibre/mechanize.git/mechanize/_mechanize.py", line
253, in open
return self._mech_open(url_or_request, data, timeout=timeout)
File
"/home/norbert/Development/calibre/mechanize.git/mechanize/_mechanize.py", line
309, in _mech_open
raise response
httperror_seek_wrapper: HTTP Error 403: request disallowed by robots.txt
H? Why does it use the original file directly in mechanize.git???
run_tests.py does more or less
this_dir = os.path.dirname(__file__)
sys.path.insert(0, os.path.join(this_dir, "test"))
sys.path.insert(0, os.path.join(this_dir, "test-tools"))
sys.path.insert(0, os.path.join(this_dir, "mechanize"))
so **why** does it use the test/test-tools/mechanize from the ROOT
instead of the python test build?
It seems something is messed up in the pybuild test setup?
If you want to take a look, here is the git repo with the current
status:
https://github.com/norbusan/debian-mechanize.git
Thanks a lot and all the best
Norbert
--
PREINING Norbert http://www.preining.info
Accelia Inc. + IFMGA ProGuide + TU Wien + JAIST + TeX Live + Debian Dev
GPG: 0x860CDC13 fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13
updating mechanize - help concerning tests with pybuild
Dear all, here are two questions: one concerning adopting/updating mechanize and how to deal with rdepends, one concerning how to fix tests with special requirements in pybuild. For calibre and porting to python3, I need mechanize for python3. The current version of python-mechanize is from 2012 and version 0.2.5, while the latest version is 0.4.3 from a few days ago. The recent versions support python3, so I would like to update mechanize. I checked the rdepends of python-mechanize: python-twill zope2.13 python-zope.testbrowser calibre python-clientform zope2.13 is very old, removed from testing, unmaintained python-zope.testbrowser the same python-clientform is a transitional package build from mechanize python-twill has a last upload in 2016, but is lagging behind badly (current version 1.8 on pypi) calibre needs an updated mechanize. So I think it would be fine to simply update mechanize without too much troubles. The current maintainers/uploaders are Maintainer: Debian/Ubuntu Zope Team Uploaders: Brian Sutherland , Fabio Tranchitella , Jérémy Bobbio , Matthias Klose , Arnaud Fontaine (In CC, but Brian removed, he already declared he does not want to maintain the package anymore, see bug #869439) I would be interested in adopting mechanize if the current maintainers / uploaders are fine with it. Or we put it into the python modules team and I do the stuff there. All is fine for me. How could be proceed here? --- Now for the pybuild question: Current mechanize needs to set up a special environment for the tests. There is a dedicated script run_tests.py that would do the trick. I tried to use the pybuild before tests feature to export PYTHONPATH, but that didn't work. Is there a way to run a specific script instead of the built-in tests of pybuild? I thought about using PYTHON_DISABLE=tests and add a specific dh test target. WDYT? Thanks for any hints! All the best Norbert -- PREINING Norbert http://www.preining.info Accelia Inc. + IFMGA ProGuide + TU Wien + JAIST + TeX Live + Debian Dev GPG: 0x860CDC13 fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13
Re: packaging problems with python3.5 and python 3.6
Hi Steve, thanks for your answer, very much appreciated. > Ok, that was the first hit I got but I discounted it because it spoke of > packaging "libraries", not modules or extensions. Indeed, but I was choosing between "applications" and "libraries" and the later one sounded more appropriate. > I added python3-lxml because without it, build-time tests failed for > python3. If I also added python-lxml, that was purely a cut'n'paste error. No, my fault, it is python*3*-lxml. Thanks. > AFAIK you would need to get the ftpmasters to reject the existing -1 first. Ok, thanks a lot. All the best Norbert -- PREINING Norbert http://www.preining.info Accelia Inc. +JAIST +TeX Live +Debian Developer GPG: 0x860CDC13 fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13
Re: packaging problems with python3.5 and python 3.6
Hi Steve, Thanks for your answer and your fix! > Which "python packaging guide" do you refer to? A search for "debian python > packaging guide" does not return unambiguous results. https://wiki.debian.org/Python/LibraryStyleGuide where it states: You'll want to have at least the following build dependencies: ... python3-all but the python[,3]-all-dev are never mentioned. So sorry, I didn't know about them and searched for the required header files, and added the respective packages. > 'python-all-dev, python3-all-dev' - plus the python2 and python3 versions of Thanks, maybe one with proper knowledge should fix the wiki, though. > Since this package is in collab-maint, I've gone ahead and pushed fixed > python3 support to the repo. Thanks again. You added a dependency on python-lxml. I don't think this is necessary as libxml is only used at compile time. At least building in a clean chroot did work out without any problems. BTW, does it make sense to upload another -1 version to ftp-master to replace the one in the NEW queue? All the best Norbert -- PREINING Norbert http://www.preining.info Accelia Inc. +JAIST +TeX Live +Debian Developer GPG: 0x860CDC13 fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13
packaging problems with python3.5 and python 3.6
Dear all (please Cc) to satisfy a dependency of the next Calibre package I have packaged html5-parser https://github.com/kovidgoyal/html5-parser see Vcs-Browser: https://anonscm.debian.org/cgit/collab-maint/html5-parser.git Vcs-Git: git://anonscm.debian.org/collab-maint/html5-parser.git Unfortunately I have given up providing python3 modules, since it seems that either python3.5 or python3.6 breaks when adding the respective line as explained in the python packaging guide. For now I have uploaded the package with python2 support, only, as this also the only one needed for Calibre (which is python2 application). If you have any suggestion concerning the python3 packaging part, please let me know how this should be done. You can see what I have done wrt python3 in the following commit https://anonscm.debian.org/cgit/collab-maint/html5-parser.git/commit/?id=4a8e02b20698e35e577482f96efdeb17826d797f which I reverted afterwards. Thanks a lot and all the best Norbert -- PREINING Norbert http://www.preining.info Accelia Inc. +JAIST +TeX Live +Debian Developer GPG: 0x860CDC13 fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13
