For more information, please see the discourse links below.
pulp_file: https://discourse.pulpproject.org/t/pulp-file-1-10-0-is-ga/181
pulp-cli:
https://discourse.pulpproject.org/t/pulp-cli-0-12-0-is-generally-available/185
David
___
Pulp-list mailing
Since the client_key is write_only, the only solution currently would be to
update the client_key with your entitlement cert. You could do this instead
of checking the client_key, or every time before sync or when you hit a 403.
I imagine that these solutions may not suffice for you though. In
The remote fields client_key, username, and password became no longer
readable in pulp 3.11. You can still set/update them but we considered
exposing them in the API as a security vulnerability.
https://docs.pulpproject.org/pulpcore/changes.html#id330
https://pulp.plan.io/issues/8202
David
On
Please visit discourse to propose/vote on/view potential sessions for
PulpCon 2021.
https://discourse.pulpproject.org/t/pulpcon-2021-call-for-proposals/134
David
___
Pulp-list mailing list
Pulp-list@redhat.com
More info:
https://discourse.pulpproject.org/t/pulp-file-1-9-1-is-generally-available/110
David
___
Pulp-list mailing list
Pulp-list@redhat.com
https://listman.redhat.com/mailman/listinfo/pulp-list
I've taken down Github Discussions. It looks like Github stores the
Discussions though so I can still re-enable them temporarily if anyone
needs info, etc.
David
On Tue, Aug 24, 2021 at 2:44 PM David Davis wrote:
> AFAICT, there's no way to make discussions readonly so any discussi
For more information, check out the post on Discourse:
https://discourse.pulpproject.org/t/pulpcore-3-15-0-is-generally-available/101
David
___
Pulp-list mailing list
Pulp-list@redhat.com
https://listman.redhat.com/mailman/listinfo/pulp-list
___
> From: pulp-dev-boun...@redhat.com on behalf
> of David Davis
> Sent: 23 August 2021 15:30
> To: Melanie Corr
> Cc: pulp-list; Pulp Development List
> Subject: Re: [Pulp-dev] [Pulp-list] Github Discussions
>
> If no one objects, I will be retiring
data to prove the increase in community engagement
>> after the move.
>>
>> Ar Aoine 18 Meith 2021 ag 16:33, scríobh Daniel Alley > >:
>>
>>> And Matrix integration.
>>> https://meta.discourse.org/t/chatroom-integration-plugin-discourse-chat-integrati
Have you considered using the chunked upload api? It was developed to deal
with this problem.
The pulp-cli uses it by default when uploading artifacts:
pulp artifact upload --file test.rpm
David
On Tue, Aug 17, 2021 at 10:54 AM Jan David
wrote:
> Hi,
>
>
>
> I’m running the docker
Hi Marcin,
I was able to reproduce this and filed a bug:
https://pulp.plan.io/issues/9102
I have also opened a fix:
https://github.com/pulp/pulp_file/pull/538/files#diff-6c586b4d1d0bff684f9c6a196269a636cb8f91d1f536f25d27ba392f86ea4ea6
You should be able to apply this patch locally (use `pip
I haven't heard any objections so I plan to move forward with upgrading our
CI and container images to Python 3.8 on Wednesday July 14 if there are no
objections.
David
On Wed, Jul 7, 2021 at 12:43 PM David Davis wrote:
> Just wanted to call attention to this thread for anyone not check
Just wanted to call attention to this thread for anyone not checking Github
Discussions.
https://github.com/pulp/community/discussions/3
Please submit feedback/questions on the thread.
David
___
Pulp-list mailing list
Pulp-list@redhat.com
, Jun 16, 2021 at 7:59 PM Neal Gompa wrote:
> On Wed, Jun 16, 2021 at 7:21 PM David Davis wrote:
> >
> > One of the main reasons we wanted to move off mailing lists is that
> signing up is inconvenient for users that may just want to ask a single
> question. But I agree th
in Gmail. It's pretty hard to do
>> filtering of GitHub mail...
>>
>> On Wed, Jun 16, 2021 at 4:29 PM David Davis
>> wrote:
>> >
>> > If you watch the repo, you should be able to get notifications when
>> there's new activity?
>> >
>> >
If you watch the repo, you should be able to get notifications when there's
new activity?
David
On Wed, Jun 16, 2021 at 3:13 PM Neal Gompa wrote:
> On Wed, Jun 16, 2021 at 11:59 AM David Davis
> wrote:
> >
> > Yesterday at open floor, we discussed decommissioning pulp-d
at 11:01 AM Brian Bouterse wrote:
> I did this also for the pulpcore meeting:
> https://github.com/pulp/community/discussions/8
>
> My format was a little different, but the same idea.
>
> On Thu, Jun 3, 2021 at 10:13 AM Grant Gainey wrote:
>
>> On Thu, Jun 3, 2021 at
Based on feedback, I've moved discussions to its own repo:
https://github.com/pulp/community/discussions.
David
On Tue, May 25, 2021 at 1:49 PM David Davis wrote:
> We've heard from the community about the amount of friction involved in
> getting help with Pulp and one of the areas I th
I started a discussion on Github about dropping support for Python 3.6 and
Django 2. Please respond with any comments/concerns/feedback.
https://github.com/pulp/pulpcore/discussions/1359
David
___
Pulp-list mailing list
Pulp-list@redhat.com
We've heard from the community about the amount of friction involved in
getting help with Pulp and one of the areas I think we could improve is
user communications. We currently run two mailing lists: pulp-list and
pulp-dev.
At today's open floor meeting, we talked about using Github's new
Over the past year, we've talked several times about moving off plan.io and
onto Github Issues. We've established that we need a plan for how to do so
though. I'd like to organize a meeting next week to come up with such a
plan. If you are interested in participating, please let me know today or
What about something like this?
http :/pulp/api/v3/tasks/ state==failed
started_at__gte=="2021-05-15T0:0:0.0Z" started_at__lte=="2021-05-20T0:0:0.0Z"
This would find the failed tasks that started between 2021-05-15 and
2021-05-20.
David
On Thu, May 20, 2021 at 4:00 PM Bin Li (BLOOMBERG/ 120
pulp-cli 0.9.0 has been released to PyPI[0]. It is considered beta software
until it reaches its 1.0 release. Future releases will likely break
compatibility.
The 0.9.0 release includes a bugfix caused by the recent release of click 8
as well as a setting for dry_run, better handling of
The /pulp/content/ endpoint should list all your distributions. I suspect
you're running into this bug:
https://pulp.plan.io/issues/8636
It should be fixed in 3.13 which releases tentatively on May 18. If you
can't wait, you can file a backport request[0] and we can get this into
3.12 for you.
Pulpcore 3.11.1 [0] and pulp_installer 3.11.1 [1] have been released.
This release fixes two race conditions in the task code and allows plugins
to unset queryset_filtering_required_permission for NamedModelViewSets.
For a full list of changes, please check the changelog for pulpcore [2] and
pie package.
>
> How can I install the https command on RHEL 7?
>
> Thanks,
> Ben Stanley.
> On 29/4/21 9:06 pm, David Davis wrote:
>
> Ben,
>
> Is your server at http://localhost or https://localhost? You said you
> accessed the schema at http://localhost/pulp/api/v
a
>>> few steps.
>>>
>>> Ben.
>>> On 29/4/21 5:10 am, Ina Panova wrote:
>>>
>>> Hey Ben,
>>>
>>> We also have docs on how to setup and run the migration should that help
>>> you or make it easier for you rather than following the video.
>
Hi Ben,
You're missing a slash.
http POST :/pulp/api/v3/migration-plans/ https://localhost/pulp/api/v3/migration-plans/.
Also, we've since added support for the pulp-2to3-migration to our CLI
which may be a bit easier to use than httpie.
https://github.com/pulp/pulp-cli
David
On Wed,
Pulpcore 3.12.1 [0] and pulp_installer 3.12.1 [1] have been released.
This release fixes a missing field (RepositoryVersionRelatedField) in the
plugin api that plugin writers need when moving from
RepositoryVersionDistribution to the new Distribution model.
For a full list of changes, please
pulp_file 1.7.0 is now available on PyPI.
This release adds support for auto-publishing and auto-distributing. It is
compatible with pulpcore 3.12 and 3.13.
PyPI: https://pypi.org/project/pulp-file/1.7.0
Changelog: https://docs.pulpproject.org/pulp_file/en/1.7.0/changes.html
Docs:
15 Apr 2021 at 07:50 David Davis wrote:
>
>> When you say you run the playbook again and got the same error, which
>> error do you mean? The "No such file or directory:
>> '/var/lib/pulp/assets/rest_framework/js/jquery-3.4.1.min.js'" one?
>>
>>
When you say you run the playbook again and got the same error, which error
do you mean? The "No such file or directory:
'/var/lib/pulp/assets/rest_framework/js/jquery-3.4.1.min.js'" one?
David
On Thu, Apr 15, 2021 at 4:43 AM Eric VS wrote:
> Hey Matthias,
>
> I ran the pulpcore-manager
It could potentially be this bug which was fixed in pulpcore 3.12:
https://pulp.plan.io/issues/8447
The stacktrace would be helpful though to know for sure.
David
On Mon, Apr 12, 2021 at 5:27 AM Matthias Dellweg
wrote:
> Can you monitor "journalctl -f -u pulpcore-content" while performing
the query string appending code).
> I'm back from away-from-keyboard vacation tomorrow, and should be able to
> get a some patches sent upstream. :)
>
> https://github.com/jschneier/django-storages/issues/997
>
> --Danny
>
> On Tue, Apr 6, 2021, 2:07 PM David Davis wrote:
>
Hi Danny,
I don't know much about AWS logging but Pulp does set the filename in the
response-content-disposition[0]. Could that be used to determine the
filename for each request?
If not, I'm looking at the boto3 docs for get_object[1] to see if there's
another parameter we could set to help you
David Davis wrote:
> It looks like everyone on the team has voted. The week of September 13-17
> seems to be the most popular week. Let's try to aim for some time that
> week. September 20-25 can be a possible backup week if the week of
> September 13 doesn't work out for some reason.
pulp_file 1.6.1 is now generally available. It is compatible with pulpcore
3.7 through 3.12.
For more details and full list of changes, see the changelog.
PyPI: https://pypi.org/project/pulp-file/
Changelog: https://docs.pulpproject.org/pulp_file/changes.html
Docs:
in the next month or so in terms of the
actual days/times.
Thanks again everyone.
David
On Wed, Mar 24, 2021 at 11:15 AM David Davis wrote:
> I haven't heard any objections to having PulpCon virtual this year so
> under that assumption, I wanted to gather feedback on when to have PulpCon.
On Tue, Mar 16, 2021 at 11:08 AM Brian Bouterse wrote:
>
>
> On Mon, Mar 15, 2021 at 11:12 AM David Davis
> wrote:
>
>> The topic of PulpCon came up today as spring is usually the time we begin
>> to plan PulpCon. The main question I think is whether we should hold
>>
To clarify, you're talking about having to install the django-storages
packages[0]?
I don't know if this exists today in the installer (maybe someone from the
pulp_installer team can confirm) but it would be great to have support for
setting up pulp to use non-fs storage backends.
With using
I'd be curious about the data that's causing this issue. Can you try
applying this patch and rerunning sync? It should give you more info about
the existing package that's causing the conflict.
https://gist.github.com/daviddavis/3716ff3a988be8a5d797da136c7b90bf
David
On Fri, Mar 19, 2021 at
I'm guessing there's a package that got saved with a bad pkgId. I think
what dalley recommends should work. I'd also make a backup of your current
database in case rolling back causes bigger problems.
David
On Thu, Mar 18, 2021 at 2:32 PM Daniel Alley wrote:
> Restoring postgresql from tape
The topic of PulpCon came up today as spring is usually the time we begin
to plan PulpCon. The main question I think is whether we should hold
PulpCon again virtually this year or not.
Optimally, we'd like to meet in person but given the uncertainty of our
current situation, I think we should
Great, thanks for the update.
David
On Fri, Mar 5, 2021 at 2:47 PM Bin Li (BLOOMBERG/ 120 PARK) <
bli...@bloomberg.net> wrote:
> Thanks Dave. Got the filename which has the inconsistent checksum after
> patching. We will ask upstream remote to update the repodata.
>
> From:
Regarding the error message, I've observed the problem myself. and have
filed an issue:
https://pulp.plan.io/issues/8357
In the meantime, if you can patch the code, this should tell you give you
more info:
https://gist.github.com/daviddavis/2e6ab1872d97230d144a6cd1f9d05e31
David
On Fri, Mar
pulp-cli 0.6.0 has been released to PyPI[0]. It is considered beta software
until pulp-cli reaches its 1.0 release. Future releases will likely break
compatibility.
This release features support for the upcoming component name change in
pulpcore 3.11. See the changelog for more details[1]. For
pulp-cli 0.5.0 has been released to PyPI[0]. It is considered beta software
until pulp-cli reaches its 1.0 release. Future releases will likely break
compatibility.
This release features pulp 2to3 migration support, multiple config support,
a worker command, and better validation of task states
If I understand you correctly, you want to take a new repository version
and distribute it. Currently, you have to publish the new repository
version and then associate the new publication with your distribution:
pulp rpm publication create --repository --version
pulp rpm distribution update
pulp-cli 0.3.0 has been released to PyPI[0]. It is considered beta software
until it reaches its 1.0 release. Future releases will likely break
compatibility.
The 0.3.0 release features support for labels, which were added in pulpcore
3.10. See the changelog for all changes[1]. For help
The pulp/pulp-fedora31 container image[0] has been replaced by
pulp/pulp[1]. I plan to remove pulp/pulp-fedora31 after February 5th if
there are no objections.
[0] https://hub.docker.com/r/pulp/pulp-fedora31
[1] https://hub.docker.com/r/pulp/pulp
David
pulp-cli 0.2.0 has been released to PyPI[0]. It is considered beta software
until it reaches its 1.0 release. Future releases will likely break
compatibility.
The 0.2.0 release features pulp_ansible support, a repository modify
command, and the ability to call --help without having to connect to
The first release of the pulp-cli has been released to PyPI[0]. While this
is the first release, the pulp-cli is still considered beta software until
it reaches its 1.0 release. Future releases will likely break compatibility.
The pulp-cli provides a user friendly alternative to the REST API in
FYI, the single container now includes pulp_python thanks to Fabricio.
https://hub.docker.com/repository/docker/pulp/pulp-fedora31
David
On Wed, Jan 13, 2021 at 8:06 AM David Davis wrote:
> Awesome! Thanks pulp_python team!
>
> David
>
>
> On Wed, Jan 13, 2021 at 4:00 A
Awesome! Thanks pulp_python team!
David
On Wed, Jan 13, 2021 at 4:00 AM Matthias Dellweg
wrote:
> Yay, finally! Thank you!
>
> On Wed, Jan 13, 2021 at 4:43 AM Grant Gainey wrote:
>
>> On Tue, Jan 12, 2021 at 6:30 PM Gerrod Ubben wrote:
>>
>>> pulp_python 3.0.0 is now Generally Available!
Tobias,
Glad to hear you are enjoying Pulp 3. We use https://pulp.plan.io/ to track
our issues. For the pulp_container project, you can report an issue at
https://pulp.plan.io/projects/pulp_container/issues/new (must be signed up
and logged in).
Your feedback regarding using Github to track
Pulpcore 3.9.0 [0] and pulp_installer 3.9.0 [1] have been released.
For a full list of changes, please check the changelog for pulpcore [2] and
pulp_installer [3].
# Installation and Upgrade
Users should use the 3.9.0 release of pulp_installer [1] to install or
upgrade their installations. This
Good question. I think the short/easy answer is to edit this line of code
and set default=False:
https://github.com/pulp/pulp-cli/blob/e913ca808e324f1dbfd51907450394dab4a935cc/pulpcore/cli/common.py#L54
Alternatively, the CLI uses requests and per the requests docs[0] I think
you can specify
Just wanted to mention that there will also be a lightning talk session on
Thursday that people can sign up for. Topics can include anything you think
would be of interest to people and not necessarily Pulp-related.
https://hackmd.io/_TRvX3PBRzyGgj49y35MNQ
David
On Tue, Sep 1, 2020 at 7:51 AM
This sounds identical to a bug that we're currently working on:
https://pulp.plan.io/issues/7321
We're having trouble reproducing it though. Would you be able to provide
more info (see https://pulp.plan.io/issues/7321#note-7).
Thanks.
David
On Sat, Aug 29, 2020 at 8:35 AM Bin Li (BLOOMBERG/
Since the Pulp 2 tests are now passing, we plan to backup and remove the
fixtures at https://repos.fedorapeople.org/pulp/pulp/fixtures/ next week if
there are no more objections.
David
On Wed, Jul 1, 2020 at 5:14 PM David Davis wrote:
> Hey thanks for pointing this out. Here's a PR:
>
&
; They are used in pulp 2 functional tests. Maybe we can move them to the
> new location as well until we reach EOL for pulp 2 or until we are sure
> that no new releases (e.g. with critical/security bugs) will be out.
>
> Thanks,
> Tanya
>
> On Tue, Jun 30, 2020 at 7:14 PM David
This is the final reminder that the fedorapeople.org pulp fixtures are
scheduled to be removed this week. If anyone needs more time, please reach
out to me.
David
On Tue, Jun 9, 2020 at 11:04 AM David Davis wrote:
> As part of our effort[0] to rehome fixtures to
>
I was able to reproduce this. It looks like at the beginning of the
publication creation task, an empty publication is getting created which
has an empty string for metadata_checksum_type. It's only at the end of the
task that the actual value for metadata_checksum_type gets set.
I filed an
As part of our effort[0] to rehome fixtures to
https://fixtures.pulpproject.org/, we plan to remove the old fixtures at
https://repos.fedorapeople.org/pulp/pulp/fixtures/ on July 1st unless there
are any objections.
[0] https://pulp.plan.io/issues/6638
David
Any chance we can get some background on how, why, where this decision was
made? I'm not opposed to it but having some more information in this
announcement would be helpful.
David
On Fri, May 15, 2020 at 11:21 AM Dennis Kliban wrote:
> Starting on May 19th, bug triage will be held in
Adding pulp-list to hopefully get user feedback on this.
David
On Mon, May 11, 2020 at 6:54 AM Matthias Dellweg
wrote:
> A first draft of the architecture that should eventually govern the pulp
> cli has been completed [0].
> The feature set is naturally very limited, since we want to
o the user which 'rpm' is
>> the plugin type and which 'rpm' is the resource type.
>>
>>
>>> +1 for
>>> pulp rpm content packages
>>> pulp rpm repositories rpm
>>> pulp rpm repositories mirror
>>> ...
>>>
>>> On Wed, May 6, 2020 a
Pulpcore 3.3.1[0] has been released. For a list of all changes, please
check the changelog for pulpcore[1]. This release contains three bug fixes
and no backwards incompatible changes.
# Installation and Upgrade
Users should use the 3.3.1 release of pulp_installer[2] to install or
upgrade their
?view#Prototype
David
On Thu, Apr 30, 2020 at 1:42 PM David Davis wrote:
> Today we met to discuss some ideas for a technical design for how the CLI
> would work. Here's a copy of our notes:
>
> https://hackmd.io/aH9RqAS_TrGyxoi1UGRgig#Technical-discussion
>
> And there
Matthias and I are planning to meet next week to look at creating a proof
of concept that would provide 2-3 commands. If anyone is interested in
joining us, please let me know and I can add you.
David
On Tue, Apr 28, 2020 at 8:06 AM David Davis wrote:
> I've also started working on some questi
I've also started working on some questions about how the CLI will work.
Feel free to add some of your own:
https://hackmd.io/aH9RqAS_TrGyxoi1UGRgig?view#Technical-discussion
David
On Tue, Apr 28, 2020 at 8:05 AM David Davis wrote:
> I have set up a meeting to discuss the CLI techni
)
David
On Fri, Apr 24, 2020 at 10:29 AM David Davis wrote:
> Today we met in #pulp-meeting on freenode to discuss the user stories for
> a Pulp 3 CLI MVP. The document with the user stories is available below.
> I'd like to ask for any feedback from users or plugin writers.
>
Today we met in #pulp-meeting on freenode to discuss the user stories for a
Pulp 3 CLI MVP. The document with the user stories is available below. I'd
like to ask for any feedback from users or plugin writers.
The goal of the CLI MVP is to cover the pulp_file happy path (sync,
publish,
Bin,
Which plugin are you referring to? Some plugins have metadata and therefore
require publications (pulp_file, pulp_rpm, etc) while others such as
pulp_ansible have live APIs and therefore do not require publications.
For plugins without publications, it's possible to set repository or
Correction: the version pinning should probably be "pulpcore>=3.2,<3.3"
unless plugin authors know their release is backwards compatible with older
versions of pulpcore.
David
On Thu, Feb 27, 2020 at 4:01 PM David Davis wrote:
> pulpcore 3.2.0[0] and pulp_file 0.2.0[1]
pulpcore 3.2.0[0] and pulp_file 0.2.0[1] have been released. For a list of
all changes, please check the changelogs for pulpcore[2] and pulp_file[3].
# Installation and Upgrade
Users should use the 3.2.0 release of ansible-pulp installer[4] to install
or upgrade their installations. This version
No, there is not. You cannot change your storage once you have set up and
started to use pulp.
I'm not sure what would be involved in migrating a Pulp system from one
storage type to another but you can open a story in our tracker if you'd
like.
David
On Tue, Jan 7, 2020 at 2:31 PM Bin Li
bindings: https://rubygems.org/gems/pulp_ansible_client/
David
On Fri, Nov 15, 2019 at 4:35 PM David Davis wrote:
> The pulpcore 3.0.0rc8 and pulp_file 0.1.0rc1 packages are available
> on PyPI [0][1]. There are a lot of changes that have happened; see the
> release notes for all the deta
The pulpcore 3.0.0rc8 and pulp_file 0.1.0rc1 packages are available
on PyPI [0][1]. There are a lot of changes that have happened; see the
release notes for all the details. Some of the major changes include typed
repos, the merging of pulpcore-plugin into pulpcore, browseable content, a
new
FWIW, here's a similar issue for Pulp 2 about how we log 404s for treeinfo
files:
https://pulp.plan.io/issues/4084
David
On Mon, Nov 11, 2019 at 7:38 AM Tatiana Tereshchenko
wrote:
> Unintentionally, this conversation went off-list on Friday. I'm sending
> this note to let everyone know that
seiller technique, Services du savoir, de l'information et de la
> technologie
> Conseil national de recherches Canada / Gouvernement du Canada
> joey.dum...@nrc-cnrc.gc.ca / Tél.: 613-990-8152 / Tél. cell.: 438-340-7436
> --
> *From:* Mike DePaulo
> *Se
You need to specify limit as a query string parameter in your GET request:
http GET :80/pulp/api/v3/repositories/?limit=500
David
On Tue, Oct 29, 2019 at 11:12 AM Bin Li (BLOOMBERG/ 120 PARK) <
bli...@bloomberg.net> wrote:
> We have over 100 repositories. However we can only list 100 repos.
DRF uses UTC because it expects whatever UI (CLI, web UI, etc) to convert
datetime fields to whatever timezone the user wants. It looks like there is
no out of the box solution for DRF or httpie to convert timezones. I think
we should file a story and look at it after the 3.0 GA.
David
On Mon,
This is an expected behavior. See https://pulp.plan.io/issues/3308. Feel
free to comment with any thoughts you have.
David
On Wed, Oct 23, 2019 at 8:58 PM Bin Li (BLOOMBERG/ 120 PARK) <
bli...@bloomberg.net> wrote:
> Any idea why repository version keep increasing even nothing was updated
> in
Not all plugins use publishers. RPM is an example of a plugin that doesn't
use publishers (currently, not sure if it might in the future). I think you
can safely ignore publishers when creating an rpm publication.
David
On Thu, Oct 17, 2019 at 1:14 PM Bin Li (BLOOMBERG/ 120 PARK) <
Yes, up until we the 3.0 GA in December, we're not supporting release to
release upgrades. So upgrading from release to release (or nightly to
nightly) is not guaranteed to work.
David
On Thu, Oct 17, 2019 at 11:12 AM Bin Li (BLOOMBERG/ 120 PARK) <
bli...@bloomberg.net> wrote:
> Yeah, I pulled
The pulpcore 3.0.0rc6, pulpcore-plugin 0.1.0rc6, pulp_rpm 3.0.0b6, and
pulp_file 0.1.0b3 packages are available on PyPI [0][1][2][3]. The core
release features changes to ProgressReports, plugin-managed repos, a new
SingleArtifactContentUploadSerializer, as well as other enhancements,
bugfixes,
The beta 5 release of pulp_rpm for Pulp 3 is now available:
https://pypi.org/project/pulp-rpm/3.0.0b5/
It includes support for pulpcore 3.0.0rc5 as well as support for kickstart
trees and custom repository metadata. For more information, see the release
notes:
The pulpcore 3.0.0rc5 and pulpcore-plugin 0.1.0rc5 packages are available
on PyPI [0][1]. This release features additional task filtering, the
pinning of dependencies to y releases, a CharInFilter for plugins, and a
way for plugins to define settings programmatically.
# Release Notes
pulpcore
Just wanted to remind everyone about our community survey. If you haven't
taken it yet, please do so. You'll get some free cool Pulp swag. We'll
leave it open for two more weeks (until July 31).
https://tinyurl.com/pulp2019survey
Thank you.
David
On Tue, May 28, 2019 at 12:33 PM David Davis
The beta 1 release of pulp_file 0.1.0 for Pulp 3 is now available:
https://pypi.org/project/pulp-file/0.1.0b1/
It includes support for pulpcore 3.0.0rc3. For more information, see the
release notes:
https://pulp-file.readthedocs.io/en/latest/changes.html#b1-2019-07-09
David
On Thu, Jul 4,
run 'systemctl daemon-reload'.
David
On Fri, Jul 5, 2019 at 12:12 PM Juan Cabrera wrote:
> Hi David,
> On 5/07/19 16:27, David Davis wrote:
>
> I tested and confirmed that the files are not being deleted. Mind opening
> a bug for that?
>
> I created an issue https://pul
ads using API
>
> for u in $(http $PORT/pulp/api/v3/uploads/ | jq -r '.results[] | ._href');
> do
> echo $u
> http DELETE $PORT$u
> done
>
> The files are not deleted.
>
> Juan
> On 5/07/19 12:44, David Davis wrote:
>
> Juan,
>
> There is
Juan,
There is in fact a 2GB limit currently on artifact size. I consider this a
bug and I filed this issue:
https://pulp.plan.io/issues/4998
The file in /var/lib/pulp/upload should be deleted once it's imported as an
artifact. I'm guessing it's maybe not happening since the server is
throwing
+1
David
On Wed, Jun 12, 2019 at 11:07 AM Dennis Kliban wrote:
> I've received some off-list feedback on this decision. As a result, this
> change is no longer going to happen. Pulp 3 services will instead be
> renamed to
>
> pulpcore-resource-manager
> pulpcore-workers
> pulpcore-worker-{n}
Today we are asking for community feedback in our second Pulp Community
Survey. The feedback we received in our first community survey provided
valuable insights into how our users use Pulp. For our second Community
Survey, we hope to also get feedback into how we can improve the upcoming
Pulp 3
Juan,
First off, which plugins are you using? I'm asking because the plugins are
in various states of development--some are beta while others are RC.
I don't think we can guarantee that there won't be any major breaking
changes in the API between now and Pulp 3.0 GA but personally I think that
The 'name' field in your case would be mailcap. We don't expose the file
name of the package or allow users to filter on it but we should. Would you
mind filing an issue?
https://pulp.plan.io/projects/pulp_rpm/issues/new
By the way, thanks for using the RC. Your feedback is very much
Actually I think this is the expected behavior. Distributions can exist
without serving a publication[0] so I don't think deleting a repository or
publication should in turn delete the distribution.
[0] https://pulp.plan.io/issues/4840
David
On Wed, May 22, 2019 at 10:46 AM Dennis Kliban
Juan,
We have removed the ability to remove a single content unit (for now)
because it could potentially interfere with other tasks like sync. We may
try to bring it back after 3.0. For now, you should use orphan cleanup:
http DELETE http://localhost:24817/pulp/api/v3/orphans/
There's no docs
1 - 100 of 130 matches
Mail list logo
