summaryrefslogtreecommitdiffstats
path: root/pym
Commit message (Collapse)AuthorAgeFilesLines
* Remove FEATURES=fixpackages support.v2.2.0_alpha67Zac Medico2011-10-112-3/+2
| | | | | | | This reduces the probability of users encountering issues related to package moves when they disable --dynamic-deps, and --package-moves=n can be set in EMERGE_DEFAULT_OPTS if package moves need to be temporarily avoided for some reason.
* Ensure correct IUSE in vdb for bug #386829.Zac Medico2011-10-111-7/+16
|
* fetch: tweak space msg for bug #386797Zac Medico2011-10-111-12/+14
|
* elog_process: fix ridicoulus newlines bug #386771Zac Medico2011-10-111-4/+12
| | | | | | This fixes a regression since commit 8a119ea94ecc6668797e3a1358465ef3733f3a3e which added a newline after each character. This boosts efficiency since we no longer convert a strings to lists of characters.
* FakeVartree: disable match wrapper if necessaryv2.2.0_alpha66Zac Medico2011-10-101-2/+2
|
* FakeVartree: type from last commitZac Medico2011-10-101-1/+1
|
* FakeVartree: fix sync for --dynamic-deps=nZac Medico2011-10-101-1/+2
|
* Scheduler: fix myopts typo from last commitZac Medico2011-10-101-1/+1
|
* Add emerge --dynamic-deps <y|n> option.Zac Medico2011-10-105-6/+27
| | | | | | | | | | | | | This makes it possible to disable the dynamic dependency updates that FakeVartree performs by default. WARNING: If --dynamic-deps is disabled, then it is necessary to ensure that an alternative method is used to handle package moves in dependencies of installed packages. Normally, this is handled by FEATURES="fixpackages", which is enabled by default and may be disabled via make.conf(5). Alternatively, in order to manually apply package moves, run `emaint --fix moveinst` after each emerge --sync operation (see emaint(1)).
* mod_syslog: add newlines for bug #386627Zac Medico2011-10-101-5/+4
| | | | | This fixes omission of newlines in syslog messages since commit ca7bef7821876791a26a5f9df6938f4c77fe571f.
* elog_process: add newlines for bug #386627Zac Medico2011-10-101-4/+4
| | | | | This fixes omission of newlines in saved messages since commit ca7bef7821876791a26a5f9df6938f4c77fe571f.
* tests/dodir: check relative path by itselfMike Frysinger2011-10-091-0/+2
| | | | Signed-off-by: Mike Frysinger <vapier@gentoo.org>
* tests: setup default bin env moreMike Frysinger2011-10-091-0/+3
| | | | | | We want the default testing env to match default portage env. Signed-off-by: Mike Frysinger <vapier@gentoo.org>
* tests/__init__: return int from main()Zac Medico2011-10-092-8/+9
|
* tests/__init__: import print_functionZac Medico2011-10-091-0/+2
|
* MaskManager: fix "Unmatched removal", bug #386569Zac Medico2011-10-091-5/+40
|
* Skip PORTAGE_TMPDIR write check for fetchonly.Zac Medico2011-10-091-6/+7
| | | | Bug #286201
* show_ignored_binaries: filter noise, bug #386379Zac Medico2011-10-091-0/+26
|
* tests: add --list flag to show available testsMike Frysinger2011-10-091-21/+34
| | | | | | | | | Trying to guess at what runtests actually wants in terms of command line tests is pretty hard. Any invalid value just gives you an ugly traceback. So add a helper --list option so the user can easily figure out what the code wants *exactly*. Signed-off-by: Mike Frysinger <vapier@gentoo.org>
* tests: add a --help option to make runtest more friendlyMike Frysinger2011-10-091-2/+7
| | | | | | | At the moment, trying to do `./runtests.h -h` just produces an ugly and indecipherable traceback. Make it a bit more friendly. Signed-off-by: Mike Frysinger <vapier@gentoo.org>
* tests: split up getTests into helper funcs to avoid duplicationMike Frysinger2011-10-091-20/+17
| | | | | | | This avoids a little duplication between the getTestFromCommandLine and getTests funcs, and they'll get utilized even more in follow up patches. 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-081-8/+18
| | | | | | | | | | | | | 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.
* 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
|
* 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
|
* 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.
generated by cgit v1.2.3-1-g7c22 (git 2.25.1) at 2024-06-30 13:43:05 +0000