Pkgcore

Latest version: v0.12.28

Safety actively analyzes 682361 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 20 of 27

0.4.7.14

-----------------------------

- profile awareness of eapi files, *including* strict validation.

- tighter use dep and atom support in pkgcore for specified eapis.

- ticket 187; fix a traceback when a specific subset of cycles are
encountered.

- correct a python 2.6 incompatibility; object.__init__() is now strict
about taking no keywords.


-----------------------------

0.4.7.13

-----------------------------

- bug fix for transitive use atoms; if || ( a/b[x?] ), DepSet wasn't detecting
that there were conditionals w/in it, as such wasn't doing evaluation.


--------------------------------------------------------

0.4.7.12

--------------------------------------------------------

- security fix; force cwd to something controlled for ebuild env. This
blocks an attack detailed in glsa 200810-02; namely that an ebuild invoking
python -c (which looks in cwd for modules to load) allows for an attacker
to slip something in.


-----------------------------

0.4.7.11

-----------------------------

- fix EAPI2 issues: default related primarily, invoke src_prepare for
>=EAPI2 instead of >EAPI2.


-----------------------------

0.4.7.10

-----------------------------

- fix in setup.py to install eapi/* files.
die distutils, die.

- api for depset inspection for tristate (pcheck visibility mode) is fixed
to not tell the consumer to lovingly 'die in a fire'.

- correct a failure in EAPI=2 src_uri parsing complaining about
missing checksums for nonexistent files


----------------------------

0.4.7.9

----------------------------

- eapi2 is now supported.

- DepSet has grown a temp option named allow_src_uri_file_names; this
is to support eapi 2's -> SRC_URI extension. This functionality
will under go refactoring in the coming days- as such the api addition
isn't considered stable.

- we now match the forced phase ordering portage induced via breaking
eapi compatibilty for eapi0/1.

- tightened up allowed atom syntax; repository dep is available only when
eapi is unspecified (no longer available in eapi2 in other words).
atom USE dep parsing now requires it to follow slotting- this is done to
match the other EAPI2 standard.

Beyond that, better error msgs and tighter validation.


----------------------------

Page 20 of 27

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.