pmoravec@redhat.com
- Login: pmoravec@redhat.com
- Email: pmoravec@redhat.com
- Registered on: 02/28/2015
- Last connection: 05/26/2021
Issues
| open | closed | Total | |
|---|---|---|---|
| Assigned issues | 0 | 1 | 1 |
| Reported issues | 0 | 3 | 3 |
Projects
| Project | Roles | Registered on |
|---|---|---|
| Container Support | Private Access | 12/06/2019 |
| Crane | Private Access | 02/28/2015 |
| Debian Support | Private Access | 02/28/2015 |
| Docker Support | Private Access | 02/28/2015 |
| File Support | Private Access | 07/17/2017 |
| Migration Plugin | Private Access | 01/14/2020 |
| Nectar | Private Access | 02/28/2015 |
| OSTree Support | Private Access | 02/28/2015 |
| Packaging | Private Access | 02/28/2015 |
| Pulp | Private Access | 02/28/2015 |
| Puppet Support | Private Access | 02/28/2015 |
| Python Support | Private Access | 02/28/2015 |
| RPM Support | Private Access | 02/28/2015 |
Activity
01/21/2021
-
This completes the commit d62c61f where pulp solves wrong dependencies
because wrong evr is parsed to the solvable unit.
closes: #8110
https://pulp.plan.io/issues/8110
Signed-off-by: Pavel Moravec <pmoravec@redhat.com>
(cherry picked f... Revision 2b5119bd: Fix pulp depsolv issue when copy rpms with recursive config 2/2 -
This completes the commit d62c61f where pulp solves wrong dependencies
because wrong evr is parsed to the solvable unit.
closes: #8110
https://pulp.plan.io/issues/8110
Signed-off-by: Pavel Moravec <pmoravec@redhat.com> Revision 3b82d8df: Fix pulp depsolv issue when copy rpms with recursive config 2/2 -
A complementary & mandatory PR: https://github.com/pulp/pulp_rpm/pull/1926 (dunno why pulp bot didnt commented the same) Issue #8110: Wrong deps are copied to the repo when using "recursive" option to copy rpms**## Cloned from bugzilla 1917076 ##**
Description of problem:
Pulp solves the wrong dependent packages which will cause conflict to other packages.
Steps to Reproduce:
1. Enable the pulp debug log level and restart Pulp services...
10/26/2020
-
Comparing config override to decide (non)operational publish can safely ignore
force_full option; this option itself determines the non-operational publish
independently.
closes #7526
https://pulp.plan.io/issues/7526
Signed-off-by: Pav... Revision 8c394e24 (pulp): Ignore force_full in config override when deciding publish to be operational -
Applied in changeset commit:pulp|49a87aef4c411b94648d31ff17deee866f6d33c8. Issue #7526 (MODIFIED): Publish is operational when the only change in config is "force_full" settingTo reproduce:
- Publish a repo override_config {"force_full":true}
- Then publish without override config or with {"force_full":false}.
The second publish will be operational. -
Comparing config override to decide (non)operational publish can safely ignore
force_full option; this option itself determines the non-operational publish
independently.
closes #7526
https://pulp.plan.io/issues/7526
Signed-off-by: Pav... Revision 49a87aef (pulp): Ignore force_full in config override when deciding publish to be operational
11/16/2017
-
Issue #3140 (CLOSED - DUPLICATE): pulp_streamer doesnt set HTTP response headers, causing squid cache is not usedWhen installing a package from a repository with on demand download policy, `squid` should cache the responses to 1) limit response times of further client requests, and 2) to save bandwidth between the pulp server and the upstream repo....
11/03/2017
-
Issue #3115 (CLOSED - CURRENTRELEASE): One sample request in API doc for regenerate_applicability is wrongIn https://docs.pulpproject.org/dev-guide/integration/rest-api/consumer/applicability.html , section "Generate Content Applicability for Updated Repositories", there is Sample request:
~~~
{
"repo_criteria": {
"filters": {"id": ...
08/16/2016
-
FYI `pulp-katello` hit an identical issue and they fixed it by https://github.com/Katello/pulp-katello/pull/21/files
Issue #2047: directory creation race condition during publishIf two repos are published concurrently and share a parent directory, there is a chance they will try to create the parent directory at the same time, and the loser will fail with a traceback like this:
~~~
traceback: ! "Traceback (m...
08/03/2016
-
Story #2125 (CLOSED - WONTFIX): make pulp regenerate applicability calculation incrementalAssume pulp has already synced a big repo with thousands of RPMs and hundreds of erratas. These have been already calculated in regenerate applicability.
Now, syncing a new content from an importer brings say tens RPMs and few errata....
Also available in: Atom
.