Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

pip install does not install version-qualified package #652

Open
phmccarty opened this issue Feb 16, 2021 · 1 comment
Open

pip install does not install version-qualified package #652

phmccarty opened this issue Feb 16, 2021 · 1 comment
Labels
bug A defect in autospec's operation

Comments

@phmccarty
Copy link
Contributor

phmccarty commented Feb 16, 2021

When collecting PyPI metadata for PyPI package provides/requires, autospec runs pip install PACKAGE in a virtualenv. Instead, it should be running pip install PACKAGE==VERSION for the target package version.

This will fix issues that occasionally appear when a package is intentionally older than latest (e.g. Django remaining on the LTS series), and it will help avoid invalid queries when naming clashes exist between PyPI and other ecosystems (e.g. meld is a GNOME package, and a different project named meld is a PyPI package, and both use setuptools to build).

@phmccarty phmccarty added the bug A defect in autospec's operation label Feb 16, 2021
clrpackages pushed a commit to clearlinux-pkgs/meld that referenced this issue Feb 18, 2021
Packaging notes:

- A PyPI package exists with the name 'meld', but it's unrelated to this
  package. Autospec should probably have a heuristic to make a better
  guess about whether a package corresponds to a PyPI package with the
  same (canonicalized) name. For now, ban all pypi requires. Autospec
  issue filed at clearlinux/autospec#652.

Shortlog:

Andika Triwidada (1):
      Update Indonesian translation

Daniel Șerbănescu (3):
      Update Romanian translation
      Update Romanian translation
      Update Romanian translation

Kai Willadsen (13):
      Post-release version bump
      ui.msgarea: Allow Infobar text to wrap at character boundaries (#432)
      Fix dialog border width for custom filechooser (#451)
      meldapp: Mark clipboard targets to be kept after exit (#482)
      filediff: Handle our delete handler being called multiple times (#502)
      dirdiff: Fix sensitivity when cancelling existing folder scans (#499)
      Update DOAP links to HTTPS
      Update DOAP to reflect mailing list move to discourse
      Update README for discourse move
      vc.svn: Update xml.etree API usage for Python 3.9 (#526)
      CI: Sync up Windows build with the newer CI build from master
      CI: Add an explicit setuptools requirement
      Update NEWS + appdata

Sabri Ünal (1):
      Update Turkish translation

Stephan Woidowski (1):
      Update German translation

Yuri Chornoivan (3):
      Update Ukrainian translation
      Add Ukrainian translation
      Update Ukrainian translation

Мирослав Николић (1):
      Update Serbian translation

2021-02-13 meld 3.20.3
======================

  Fixes:

   * Fix folder comparison sensitivity breaking when cancelling a scan (Kai
     Willadsen)
   * Fix Subversion comparsion on Python 3.9 (Kai Willadsen)
   * Retain clipboard contents after exiting Meld (Kai Willadsen)
   * Fix wrapping in notification bars (Kai Willadsen)
   * Fix border width in our file selection dialog (Kai Willadsen)
   * Fix occasional traceback when closing comparisons (Kai Willadsen)
   * Update links to reflect move to Discourse (Kai Willadsen)

   * Issues fixed: 432, 451, 482, 499, 502, 526

(NEWS truncated at 15 lines)
phmccarty added a commit to phmccarty/autospec that referenced this issue Sep 9, 2021
In case a PyPI package being processed is not the "current" version
listed in the PyPI catalog, make sure to `pip install` an older release
of the package corresponding to the parsed content version string.

Fixes clearlinux#652

Signed-off-by: Patrick McCarty <patrick.mccarty@intel.com>
@phmccarty
Copy link
Contributor Author

I posted a possible solution for this issue to a branch:

https://github.com/phmccarty/autospec/commits/issue652

I'm not sure about this approach though, so I'll leave it there for now.

clrpackages pushed a commit to clearlinux-pkgs/ansible that referenced this issue Sep 16, 2021
Some pypi requires symbols needed to be banned for ansible 2.9.x due to
an open autospec bug [0]; packaging the latest ansible means that we do
not need to ban any of these symbols at the moment.

[0]: clearlinux/autospec#652

Signed-off-by: Patrick McCarty <patrick.mccarty@intel.com>
phmccarty added a commit to phmccarty/autospec that referenced this issue Mar 1, 2022
In case a PyPI package being processed is not the "current" version
listed in the PyPI catalog, make sure to `pip install` an older release
of the package corresponding to the parsed content version string.

Fixes clearlinux#652

Signed-off-by: Patrick McCarty <patrick.mccarty@intel.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug A defect in autospec's operation
Projects
None yet
Development

No branches or pull requests

1 participant