update hacking requirements

Bug #1741693 reported by Matthew Thode
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
hacking
New
Undecided
Unassigned
Gentoo Linux
Fix Released
Medium

Bug Description

Hacking requiring specific versions of libraries

==pep8-1.5.7 for instance

This makes it hard for downstream to package because of the use of ancient and locked versions mean our users have to downgrade to use hacking or to install something with tests using hacking.

dev-python/pep8-1.7.0 is our current stable version of pep8 for instance.

What I'd like to see happen is either regularly update the locked version of the packages hacking depends upon or to unlock them entirely (and work with upstreams to deal with any breakage). If neither of these happen I'll probably move to remove hacking from our repo.

Revision history for this message
In , mgorny (mgorny-gentoo-bugs) wrote :

hacking-0.10.3.ebuild: ~dev-python/pep8-1.5.7[${PYTHON_USEDEP}]
hacking-0.13.0.ebuild: ~dev-python/pep8-1.5.7[${PYTHON_USEDEP}]
hacking-0.9.2.ebuild:RDEPEND="~dev-python/pep8-1.5.6[${PYTHON_USEDEP}]
hacking-0.9.6.ebuild:RDEPEND="~dev-python/pep8-1.5.6[${PYTHON_USEDEP}]

This is a really awful design that not only blocks cleanup of other packages but also forces people to downgrade. Please look into fixing this horrible package not to force specific old versions of other packages. Thank you.

Revision history for this message
In , mgorny (mgorny-gentoo-bugs) wrote :

Also:

hacking-0.10.3.ebuild: >=dev-python/testtools-0.9.36[${PYTHON_USEDEP}]
hacking-0.10.3.ebuild: <dev-python/testtools-1.2.0[${PYTHON_USEDEP}]
hacking-0.13.0.ebuild: >=dev-python/testtools-0.9.36[${PYTHON_USEDEP}]
hacking-0.13.0.ebuild: <dev-python/testtools-1.2.0[${PYTHON_USEDEP}]

Revision history for this message
In , prometheanfire (prometheanfire-gentoo-bugs) wrote :

yep, hacking is kinda bad about it, I've taken to patching it out of the ebuilds test-requirements.txt as a mater of course.

Even in 1.0.0 hacking still sets some stuff to only work with a certain version of various libraries. https://github.com/openstack-dev/hacking/blob/1.0.0/requirements.txt

If upstream doesn't update the requirements (and preferably uncap/lock them) then I think moving to remove it from tree makes sense.

Changed in gentoo:
importance: Unknown → Medium
Revision history for this message
In , asturm (asturm-gentoo-bugs) wrote :

This is fun.

> $ grep flake8 hacking-1.1.0.ebuild
> >=dev-python/flake8-2.6.0[${PYTHON_USEDEP}]
> <dev-python/flake8-2.7.0[${PYTHON_USEDEP}]

Keywords for dev-python/flake8:
      | | u |
      | a a a p s r | n |
      | l m r i p h m s p i m | e u s | r
      | p d a m a p c x p 6 3 a s i | a s l | e
      | h 6 r 6 6 p 6 8 p 8 9 s r c p | p e o | p
      | a 4 m 4 4 c 4 6 a k 0 h c v s | i d t | o
------+-------------------------------+-------+-------
2.1.0 | ~ + ~ ~ ~ ~ ~ + ~ o ~ o o o o | 5 # 0 | gentoo
2.2.5 | ~ + + o + + + + + o + o + o o | 5 # | gentoo
2.5.4 | ~ + + ~ + + + + + o o o o o o | 5 # | gentoo
3.5.0 | ~ + + ~ + + + + + o + o + o ~ | 6 o | gentoo
3.6.0 | ~ ~ ~ ~ ~ ~ ~ ~ ~ o ~ o ~ o ~ | 6 o | gentoo
3.7.9 | o + ~ + ~ ~ ~ ~ o o o o o o o | 7 o | gentoo

So, naturally:

> !!! Multiple package instances within a single package slot have been pulled
> !!! into the dependency graph, resulting in a slot conflict:
>
> dev-python/flake8:0
>
> (dev-python/flake8-2.5.4:0/0::gentoo, ebuild scheduled for merge) USE="-test" ABI_X86="(64)" PYTHON_TARGETS="python3_6 -python2_7 (-python3_7)" pulled in by
> <dev-python/flake8-2.7.0[python_targets_python3_6(-)?,python_targets_python3_7(-)?,-python_single_target_python3_6(-),-python_single_target_python3_7(-)] required by (dev-python/hacking-1.1.0:0/0::gentoo, ebuild scheduled for merge) USE="-doc -test" ABI_X86="(64)" PYTHON_TARGETS="python3_6 (-python3_7)"
> ^ ^^^^^
>
> (dev-python/flake8-3.7.9:0/0::gentoo, ebuild scheduled for merge) USE="-test" ABI_X86="(64)" PYTHON_TARGETS="python3_6 (-pypy3) -python2_7 (-python3_7) (-python3_8)" pulled in by
> >=dev-python/flake8-2.6.0[python_targets_python3_6(-)?,python_targets_python3_7(-)?,-python_single_target_python3_6(-),-python_single_target_python3_7(-)] required by (dev-python/hacking-1.1.0:0/0::gentoo, ebuild scheduled for merge) USE="-doc -test" ABI_X86="(64)" PYTHON_TARGETS="python3_6 (-python3_7)"
> ^^ ^^^^^

Revision history for this message
In , asturm (asturm-gentoo-bugs) wrote :

Please describe your process of stabilising 1.1.0 in commit a1c41da8f24305702c1e29b4fc3b69b78d6977ec.

Revision history for this message
In , mgorny (mgorny-gentoo-bugs) wrote :

The real fun is that flake8/pep8 has no value for gentoo users.

Revision history for this message
In , prometheanfire (prometheanfire-gentoo-bugs) wrote :

install/test, commit, same as always.

Revision history for this message
In , infra-gitbot (infra-gitbot-gentoo-bugs) wrote :

The bug has been referenced in the following commit(s):

https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=5f55303cb083c8dd5bcef6efdebcf75407f9bf07

commit 5f55303cb083c8dd5bcef6efdebcf75407f9bf07
Author: Matthew Thode <email address hidden>
AuthorDate: 2020-01-26 20:23:46 +0000
Commit: Matthew Thode <email address hidden>
CommitDate: 2020-01-26 20:24:14 +0000

    dev-python/hacking: 2.0.0 bump

    Bug: https://bugs.gentoo.org/643616
    Package-Manager: Portage-2.3.84, Repoman-2.3.20
    Signed-off-by: Matthew Thode <email address hidden>

 dev-python/hacking/Manifest | 4 +-
 dev-python/hacking/hacking-0.10.3.ebuild | 71 --------------------------------
 dev-python/hacking/hacking-0.9.2.ebuild | 61 ---------------------------
 dev-python/hacking/hacking-0.9.6.ebuild | 61 ---------------------------
 dev-python/hacking/hacking-2.0.0.ebuild | 59 ++++++++++++++++++++++++++
 5 files changed, 60 insertions(+), 196 deletions(-)

Revision history for this message
In , prometheanfire (prometheanfire-gentoo-bugs) wrote :

need bug 706412 so we can remove 1.1.0

Revision history for this message
In , infra-gitbot (infra-gitbot-gentoo-bugs) wrote :

The bug has been referenced in the following commit(s):

https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=b5418484968bf3e16a2feb4257a2ed24cce56d72

commit b5418484968bf3e16a2feb4257a2ed24cce56d72
Author: Matthew Thode <email address hidden>
AuthorDate: 2020-01-26 21:19:53 +0000
Commit: Matthew Thode <email address hidden>
CommitDate: 2020-01-26 21:25:11 +0000

    dev-python/hacking: 2.0.0 stable amd64 / x86 fast

    Bug: https://bugs.gentoo.org/643616
    Package-Manager: Portage-2.3.84, Repoman-2.3.20
    Signed-off-by: Matthew Thode <email address hidden>

 dev-python/hacking/hacking-2.0.0.ebuild | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

Revision history for this message
In , infra-gitbot (infra-gitbot-gentoo-bugs) wrote :

The bug has been closed via the following commit(s):

https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=c8d88a067fce0fb2b2c696ac93534a177efb056f

commit c8d88a067fce0fb2b2c696ac93534a177efb056f
Author: Matthew Thode <email address hidden>
AuthorDate: 2020-01-26 21:45:37 +0000
Commit: Matthew Thode <email address hidden>
CommitDate: 2020-01-26 21:46:22 +0000

    dev-python/hacking: 1.1.0 removed

    Closes: https://bugs.gentoo.org/643616
    Package-Manager: Portage-2.3.84, Repoman-2.3.20
    Signed-off-by: Matthew Thode <email address hidden>

 dev-python/hacking/Manifest | 1 -
 dev-python/hacking/hacking-1.1.0.ebuild | 59 ---------------------------------
 2 files changed, 60 deletions(-)

Changed in gentoo:
status: Unknown → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.