how to deal with py-file-not-bytecompiled
Hello, I am preparing the new silx package and I got these error messages from adequate This package produce the silx python module but install also a bunch of files for qtdesigner in the rules file with this command. # install the qtdesigner files only for the python3 package dh_install -p python3-silx qtdesigner_plugins/*.py /usr/lib/qt4/plugins/designer/python So I would like to know what is the proper way to deal with this. thanks for your help. Frederic 1m30.3s DEBUG: Starting command: ['adequate', '--root', '/var/run/schroot/mount/unstable-amd64-sbuild-0a8521f2-961d-11e8-8726-a0369f838f54-piuparts', 'python-silx-dbg', 'python-silx-dbgsym', 'python-silx-doc', 'python-silx', 'python3-silx-dbg', 'python3-silx-dbgsym', 'python3-silx', 'silx'] 1m30.6s DUMP: python3-silx: py-file-not-bytecompiled /usr/lib/qt4/plugins/designer/python/plot1dplugin.py python3-silx: py-file-not-bytecompiled /usr/lib/qt4/plugins/designer/python/plot2dplugin.py python3-silx: py-file-not-bytecompiled /usr/lib/qt4/plugins/designer/python/plotwidgetplugin.py python3-silx: py-file-not-bytecompiled /usr/lib/qt4/plugins/designer/python/plotwindowplugin.py 1m30.6s DEBUG: Command ok: ['adequate', '--root', '/var/run/schroot/mount/unstable-amd64-sbuild-0a8521f2-961d-11e8-8726-a0369f838f54-piuparts', 'python-silx-dbg', 'python-silx-dbgsym', 'python-silx-doc', 'python-silx', 'python3-silx-dbg', 'python3-silx-dbgsym', 'python3-silx', 'silx'] 1m30.6s ERROR: FAIL: Inadequate results from running adequate! python3-silx: py-file-not-bytecompiled /usr/lib/qt4/plugins/designer/python/plot1dplugin.py python3-silx: py-file-not-bytecompiled /usr/lib/qt4/plugins/designer/python/plot2dplugin.py python3-silx: py-file-not-bytecompiled /usr/lib/qt4/plugins/designer/python/plotwidgetplugin.py python3-silx: py-file-not-bytecompiled /usr/lib/qt4/plugins/designer/python/plotwindowplugin.py 1m30.6s ERROR: FAIL: Running adequate resulted in inadequate tags found: py-file-not-bytecompiled
Re: how to deal with py-file-not-bytecompiled
[PICCA Frederic-Emmanuel, 2018-08-02] > Hello, I am preparing the new silx package and I got these error messages > from adequate > > This package produce the silx python module but install also a bunch of files > for qtdesigner > in the rules file with this command. > > # install the qtdesigner files only for the python3 package > dh_install -p python3-silx qtdesigner_plugins/*.py > /usr/lib/qt4/plugins/designer/python > > > So I would like to know what is the proper way to deal with this. override_dh_python3: dh_python3 # if you have files installed in standard directories or in other binary packages dh_python3 -p python3-silx /usr/lib/qt4/plugins/designer/python/ see "private dirs" in dh_python3's manpage -- GPG: 1D2F A898 58DA AF62 1786 2DF7 AEF6 F1A2 A745 7645
RE:how to deal with py-file-not-bytecompiled
thanks a lot
Report from the Python BoF @ DebConf18
Hey folks, Today, we've had a productive BoF session at DebConf18, with around 12 people in attendance (unfortunately, this was not held in a recorded room). Here are the raw notes: https://gobby.debian.org/export/debconf18/bof/python There are two team-wide items that would be of general interest: 1/ We agreed that we would like Python 3.7 as default Python3 in Buster. As this needs a lot of work still, we set ourselves an internal deadline of October 2018 to assess whether releasing with 3.7 as default is feasible, leaving us 2.5 months to do any followup transitions that would be needed before the start of the transition freeze. Matthias will talk to the Release Team with this plan to "pre-book" a transition slot and make sure this would fit within their freeze plans Of course, in the meantime, we need to keep pushingupstreams to fix the async and generator-related issues that arise in 3.7. This also means finding solutions for edge-cases such as astroid, whose 2.0 branch is the only to support Py3.7, but also drops 2.x support. We may have to consider removing some leaf packages as well. 2/ Ondrej Novy will do a mass-change from git-dpm to gbp on team packages. Related to this, Piotr will review and amend the team policy if necessary, as well as work on the pipeline to make sure the policy gets published from salsa. 3/ Finally, there was some conversation about looking into debhelper's automatic detection of documentation packages (dh_installdocs in compat 11, policy §12.3 / 3.9.7), to actualy move documentation to the python-$foo-doc package if it exists. Stuart has taken this action item. Cheers, -- Nicolas Dandrimont BOFH excuse #149: Dew on the telephone lines. signature.asc Description: PGP signature
Re: how to deal with py-file-not-bytecompiled
On Thu, Aug 02, 2018 at 06:50:59AM +, PICCA Frederic-Emmanuel wrote: > Hello, I am preparing the new silx package and I got these error messages > from adequate > > This package produce the silx python module but install also a bunch of files > for qtdesigner > in the rules file with this command. > > # install the qtdesigner files only for the python3 package > dh_install -p python3-silx qtdesigner_plugins/*.py > /usr/lib/qt4/plugins/designer/python A bit off-topic, but you should not use Qt 4 in new packages. See https://lists.debian.org/debian-devel-announce/2017/08/msg6.html. -- Dmitry Shachnev signature.asc Description: PGP signature
RE:how to deal with py-file-not-bytecompiled
> A bit off-topic, but you should not use Qt 4 in new packages. > See https://lists.debian.org/debian-devel-announce/2017/08/msg6.html. I did the migration to qtcreator :)) do not worry Fred
git-dpm -> gbp conversion (mass-change)
Hi guys, čt 2. 8. 2018 v 23:25 odesílatel Nicolas Dandrimont napsal: > 2/ Ondrej Novy will do a mass-change from git-dpm to gbp on team packages. > Related to this, Piotr will review and amend the team policy if necessary, > as > well as work on the pipeline to make sure the policy gets published from > salsa. > I would like to do this in two phases: 1. convert git-dpm -> gbp 2. change default branch to debian/master First phase is ready, see: https://github.com/onovy/onovy-mass/blob/master/checks/git-dpm2gbp https://salsa.debian.org/python-team/modules/pytest/commit/af7cb5768e13b2be427774afe450c456cf96d0b4 Any suggestions for phase one please? Second phase is a bit harder, because everybody needs to change local checked-out branch manually or do clean "gbp clone". If someone forgot to do this and do push, we will get two distinct branches at salsa (master + debian/master). I think we need to coordinate this a bit more. Thanks. -- Best regards Ondřej Nový Email: n...@ondrej.org PGP: 3D98 3C52 EB85 980C 46A5 6090 3573 1255 9D1E 064B
Re: git-dpm -> gbp conversion (mass-change)
On 2018-08-03 11:06, Ondrej Novy wrote: > 2. change default branch to debian/master How about changing "upstream" to "upstream/latest" (for upstream releases, typically for unstable) and "upstream/master" (for following upstream master, typically for experimental)?
Re: git-dpm -> gbp conversion (mass-change)
On August 3, 2018 3:51:00 AM UTC, "W. Martin Borgert" wrote: >On 2018-08-03 11:06, Ondrej Novy wrote: >> 2. change default branch to debian/master > >How about changing "upstream" to "upstream/latest" (for upstream >releases, typically for unstable) and "upstream/master" (for >following upstream master, typically for experimental)? I think we should just follow DEP-14 branch naming conventions (which, having re-read it, I discover I haven't been doing). Scott K
Re: git-dpm -> gbp conversion (mass-change)
On 2018-08-03 04:33, Scott Kitterman wrote: > On August 3, 2018 3:51:00 AM UTC, "W. Martin Borgert" > wrote: > >How about changing "upstream" to "upstream/latest" (for upstream > >releases, typically for unstable) and "upstream/master" (for > >following upstream master, typically for experimental)? > > I think we should just follow DEP-14 branch naming conventions (which, having > re-read it, I discover I haven't been doing). In fact, I thought that "upstream/master" were DEP-14-ish, but only "upstream/latest" (for the newest release) is.
