summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* runtests: make sure we are in the right dirMike Frysinger2011-10-091-0/+3
| | | | | | | | The code assumes we're in the top of the tree (when it tries to run with the full path "pym/portage/tests/runTests"), so try to make sure we are in the right place to allow things like `../runtests.sh` to "just work". Signed-off-by: Mike Frysinger <vapier@gentoo.org>
* Revert "RepoConfigLoader: Recursively expand masters."Zac Medico2011-10-091-27/+21
| | | | | This reverts commit ab2a6cc357ba3c8272a4a1556e2c0bcd4bee102e. Reverting all masters recursion code for now (see bug #386569).
* Revert "MaskManager: Fix stacking of lines from master repositories."Zac Medico2011-10-091-5/+4
| | | | | This reverts commit 37f05a23fd55b633674f91f4d7658c19e41d2d63. Reverting all masters recursion code for now (see bug #386569).
* Revert "get_masters: protect against infinite recursion"Zac Medico2011-10-091-30/+23
| | | | | This reverts commit 5628dac1538985af640102654bce60a8e526daeb. Reverting all masters recursion code for now (see bug #386569).
* get_masters: protect against infinite recursionZac Medico2011-10-081-23/+30
| | | | We can't have portage crash because of circular deps in layout.conf.
* RepoConfig: allow repos.conf 'masters' overrideZac Medico2011-10-082-8/+25
| | | | | | | | | | | | | This give the user the power to override 'masters' settings from layout.conf, is case they want use a different set of masters to satisfy dependencies. This is especially important now that recursive expansion of masters is supported since commit ab2a6cc357ba3c8272a4a1556e2c0bcd4bee102e, so that the user can avoid pulling in unwanted repositories as dependencies, if necessary. Also, empty 'masters' settings are now supported, in case a repo wants to avoid implicit inheritance of PORTDIR settings like package.mask.
* tests: fix whitespace to be consistentMike Frysinger2011-10-081-10/+10
| | | | Signed-off-by: Mike Frysinger <vapier@gentoo.org>
* MaskManager: Fix stacking of lines from master repositories.Arfrever Frehtes Taifersar Arahesis2011-10-081-4/+5
|
* RepoConfigLoader: Recursively expand masters.Arfrever Frehtes Taifersar Arahesis2011-10-081-21/+27
|
* whirlpool.py: tabs to spacesv2.2.0_alpha64Zac Medico2011-10-081-6/+6
|
* portage/mail: always UTF-8 charset for MIMETextZac Medico2011-10-081-2/+1
| | | | This will fix bug #386095.
* repoman: add 'repository' to portdbapi cacheZac Medico2011-10-071-1/+1
| | | | | | | This fixes _getMaskAtom to work correctly with the repo atoms that are generated by MaskManager, solving the issue reported here: https://github.com/cschwan/sage-on-gentoo/issues/90#issuecomment-2324953
* repoman: tweak myupdates/myheaders commit logicv2.2.0_alpha63Zac Medico2011-10-071-2/+1
| | | | | | | | If we unconditionally exclude myremoved from myupdates, then removed files will also be excluded from myheaders. This allows us to avoid unnecessary separate manifest commits in cases when "myheaders" only contained files that were being removed. Since our code always uses myupdates + myremoved, this change in logic doesn't break anything.
* repoman: tweak commit logic wrt thin-manifestZac Medico2011-10-071-1/+1
| | | | | Don't populate the "myheaders" variable when we have thin-manifests that contain only DIST entries.
* Don't do a split signed Manifest commit when no headers will change. Fixes ↵Nathan Phillip Brink2011-10-071-6/+9
| | | | bug #340475.
* elog/collect_ebuild_messages: strip trailing \nv2.2.0_alpha62Zac Medico2011-10-051-0/+1
| | | | | This fixes unintended extra blank lines since commit 1c8ff00a26b0e2e3627e9c552374f71235ee6c39.
* match_to_list: preserve orderZac Medico2011-10-051-1/+8
| | | | | This allows us to properly test behavior of best_match_to_list with different permutations of the input.
* test_best_match_to_list: test all permutationsv2.2.0_alpha61Zac Medico2011-10-051-9/+19
|
* dblink._elog_process: preserve empty linesZac Medico2011-10-041-2/+0
|
* Execute tests bundled with the whirlpool module.Zac Medico2011-10-041-0/+16
|
* Mark some messages for translation.Arfrever Frehtes Taifersar Arahesis2011-10-051-10/+14
|
* whirlpool.py: fix for python3Zac Medico2011-10-041-4/+5
|
* whirlpool.py: skip tests during importZac Medico2011-10-041-6/+7
|
* RepoConfig: sort __slots__Zac Medico2011-10-041-4/+6
|
* testManifest: enable manifest-hashesZac Medico2011-10-031-0/+1
|
* repoman: bail out if unsupported manifest-hashesZac Medico2011-10-031-0/+25
|
* best_match_to_list: order by version numberZac Medico2011-10-032-1/+39
| | | | This should fix the issue shown in bug 375265, comment #10.
* Suppress warnings with DeprecationWarning.Zac Medico2011-10-031-2/+2
| | | | | These manifest-hashes warnings are irrelevant to regular users, so suppress them by default.
* Warn for questionable layout.conf manifest-hashesZac Medico2011-10-031-1/+23
|
* manfest.py: import constants directlyZac Medico2011-10-031-17/+20
|
* repoman: account for GLEP 59 in RMD160 checkZac Medico2011-10-031-20/+20
|
* GLEP 59: use manifest-hashes list in layout.confZac Medico2011-10-033-31/+19
| | | | | | | | | | | | | The manifest-hashes layout.conf setting simply overrides the hashes that are generated. When unspecified, the MANIFEST2_HASH_DEFAULTS constant is used instead (current value contains SHA1, SHA256, and RMD160). In order to enable SHA512 and WHIRLPOOL, and drop RMD160 and SHA1, simply set "manifest-hashes = SHA256 SHA512 WHIRLPOOL" in layout.conf. As with the previous boolean flags approach, manifest-hashes settings become redundant and can be removed from layout.conf after a version of portage with equivalent defaults is stable.
* Implement GLEP 59 with control via layout.conf.Zac Medico2011-10-023-7/+59
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The portage.const changes are derived from an earlier patch that was submitted by Robin H. Johnson <robbat2@gentoo.org>: http://archives.gentoo.org/gentoo-portage-dev/msg_911574e7cb615f67e4c21fc75c043f65.xml This patch has no affect on a repository unless it contains a metadata/layout.conf file which contains boolean flags that enable or disable manifest hash types. The plan is to deploy portage with this patch, and once it has been stabilized, add the following metadata/layout.conf settings to gentoo-x86: manifest-rmd160 = false manifest-sha1 = false manifest-whirlpool = true The above settings will become the default settings in a future portage release, making them redundant and eligible for removal from layout.conf (in order to avoid cluttering layout.conf with obsolete information). Future events: After WHIRLPOOL is supported in stable portage: - Add WHIRLPOOL to MANIFEST2_HASH_DEFAULTS. - Remove SHA1 and RMD160 from MANIFEST2_HASH_*. - Toggle gentoo-x86/metadata/layout.conf settings to match. After WHIRLPOOL is supported in stable portage for at least 1 year: - Change MANIFEST2_REQUIRED_HASH to WHIRLPOOL. - Remove SHA256 from MANIFEST2_HASH_*. - Toggle gentoo-x86/metadata/layout.conf settings to match. After SHA-3 is approved: - Add new hashes to MANIFEST2_HASH_*. After SHA-3 is supported in stable portage: - Toggle gentoo-x86/metadata/layout.conf settings to match. After layout.conf settings correspond to defaults in stable portage: - Remove redundant settings from gentoo-x86/metadata/layout.conf.
* Manifest.create(): tweak assume-digests codeZac Medico2011-10-021-1/+1
| | | | | | If we have a local file, before we assume that we don't need to compute any digests, make sure that the pre-computed digest types are exactly the same types that we desire.
* Manifest.create(): pass allow_* to constructorZac Medico2011-10-021-1/+2
| | | | | This fixes commit f3101b3adce6731790f80f83fafece54b7bd8a63 to ensure that Manifest.create() works correctly.
* Prefer slot conflict over blocker display.Zac Medico2011-10-021-5/+6
| | | | | | | | The slot conflict display has better noise reduction than the unsatisfied blockers display, so skip unsatisfied blockers display if there are slot conflicts (see bug #385391). Note that this reverses the logic from bug 159310, since the slot conflict display has evolved a lot since then.
* print_changelog: if no changelogs, no newlineZac Medico2011-10-021-0/+2
| | | | This will fix bug #385413.
* dblink._elog_process: handle newlines in messagesZac Medico2011-10-021-3/+6
| | | | This will fix bug #385341.
* checksum.py: use fchksum.fmd5t directlyZac Medico2011-10-011-4/+1
|
* checksum.py: lazily import bundled whirlpoolZac Medico2011-10-011-7/+7
|
* Manifest2 hash backend provider: mhashRobin H. Johnson2011-10-011-0/+19
| | | | | | | | | | Offer mhash as a provider for Manifest2 hash generation and validation. This is important as either of pycrypto or fchksum offer an accelerated Whirlpool implementation, and hashlib might not offer it. Additionally, the mhash implementation is accelerated and ships with a rigorious testsuite. Signed-off-by: Robin H. Johnson <robbat2@gentoo.org>
* whirlpool.py: handle xrange for python3Zac Medico2011-10-011-0/+4
|
* Manifest2 hash: SHA512Robin H. Johnson2011-10-011-0/+1
| | | | | | Provide SHA512 hash algorithm to be used as new Manifest2 hash. Signed-off-by: Robin H. Johnson <robbat2@gentoo.org>
* Manifest2 hash: WhirlpoolRobin H. Johnson2011-10-012-2/+794
| | | | | | | Provide public-domain implementation of the Whirlpool hash algorithm to be used as new Manifest2 hash. Signed-off-by: Robin H. Johnson <robbat2@gentoo.org>
* Refactor RMD160 hashlib code for less-hardcodingRobin H. Johnson2011-10-011-9/+12
| | | | | | To be used shortly for WHIRLPOOL as well as RMD160. Signed-off-by: Robin H. Johnson <robbat2@gentoo.org>
* Convert _generate_hash_function into a class.Zac Medico2011-10-011-6/+11
|
* Convert create_color_func into a class.Zac Medico2011-10-011-6/+6
|
* Add tests for KEYWORDS masking.Zac Medico2011-10-012-1/+357
|
* KeywordsManager: support ~* in KEYWORDSZac Medico2011-10-011-6/+10
| | | | | | | | | | | | This allows ~* in KEYWORDS to be match by any unstable keyword in the user's configuration, similar to how * in KEYWORDS already matches any user configuration. Thanks to Daniel Robbins <drobbins@funtoo.org> for the suggestion. Also, the warning about * or -* in KEYWORDS is now gone, so that ebuilds from the funtoo tree will be usable without triggering warnings like this. If necessary, we can add ways to selectively enable these kinds of warnings via layout.conf and/or repos.conf.
* dispatch-conf: fix replace-wscomments patternRyan Hill2011-10-011-1/+1
| | | | This will fix bug #375613.
generated by cgit v1.2.3-1-g7c22 (git 2.25.1) at 2024-07-02 08:31:08 +0000