apt_ppa does not refresh package list #268

New Issue

ungleich-gitea · 2021-11-20T15:22:57Z

ungleich-gitea commented

2021-11-20 15:22:57 +00:00

Created by: fidian

Here is one of my manifest files that just installs a package from a custom PPA:

#!/bin/sh -e

# Install PPA
__apt_ppa ppa:team-mayhem/ppa --state present

# Install node.js from PPA
require="__apt_ppa/ppa:team-mayhem/ppa" \
    __package php5-phpunit-test-helpers --state present

I'm using multiple different PPA repositories when provisioning new machine images. I can see that a package list does sometimes happen, but then I have PPAs that get added after the refresh and they are not refreshed again. Is this perhaps because __apt_update_index is a singleton? If that's the case, is there a good way to get all of the PPAs installed before the __apt_update_index type is created?

*Created by: fidian* Here is one of my manifest files that just installs a package from a custom PPA: ``` #!/bin/sh -e # Install PPA __apt_ppa ppa:team-mayhem/ppa --state present # Install node.js from PPA require="__apt_ppa/ppa:team-mayhem/ppa" \ __package php5-phpunit-test-helpers --state present ``` I'm using multiple different PPA repositories when provisioning new machine images. I can see that a package list does sometimes happen, but then I have PPAs that get added after the refresh and they are not refreshed again. Is this perhaps because __apt_update_index is a singleton? If that's the case, is there a good way to get all of the PPAs installed before the __apt_update_index type is created?

ungleich-gitea closed this issue

2021-11-20 15:22:57 +00:00

ungleich-gitea commented

2021-11-20 15:50:55 +00:00

Created by: telmich

weired - you should be able to reopen it - anyway, it seems there's a misunderstanding: we fixed / changed the flow of cdist, but what you are reporting is a logical issue -> continuing in the other ticket.

*Created by: telmich* weired - you should be able to reopen it - anyway, it seems there's a misunderstanding: we fixed / changed the flow of cdist, but what you are reporting is a logical issue -> continuing in the other ticket.

ungleich-gitea commented

2021-11-20 15:50:56 +00:00

Created by: fidian

I just tested this and the issue remains. Filing a new bug since I can't reopen this one.

*Created by: fidian* I just tested this and the issue remains. Filing a new bug since I can't reopen this one.

ungleich-gitea commented

2021-11-20 15:50:57 +00:00

Created by: fidian

I asked because I was using the master branch when the bug was filed, so if nothing changed between then and now, then I don't know how this bug should be closed.

*Created by: fidian* I asked because I was using the master branch when the bug was filed, so if nothing changed between then and now, then I don't know how this bug should be closed.

ungleich-gitea commented

2021-11-20 15:50:59 +00:00

Created by: telmich

Have a look at the commits around cdist/config_install.py and cdist/resolver.py. It should have been merged a bit longer than 14 days already, though.

*Created by: telmich* Have a look at the commits around cdist/config_install.py and cdist/resolver.py. It should have been merged a bit longer than 14 days already, though.

ungleich-gitea commented

2021-11-20 15:51:00 +00:00

Created by: fidian

Could you help point me to the commit that solves this problem? Was it
something that changed in the last 14 days on the master branch?

Tyler Akins

On Mon, Jun 10, 2013 at 4:26 AM, Nico Schottelius
notifications@github.comwrote:

Should be fixed with the new way we resolve dependencies.

—
Reply to this email directly or view it on GitHubhttps://github.com/telmich/cdist/issues/175#issuecomment-19188685
.

*Created by: fidian* Could you help point me to the commit that solves this problem? Was it something that changed in the last 14 days on the master branch? ## Tyler Akins On Mon, Jun 10, 2013 at 4:26 AM, Nico Schottelius notifications@github.comwrote: > Should be fixed with the new way we resolve dependencies. > > — > Reply to this email directly or view it on GitHubhttps://github.com/telmich/cdist/issues/175#issuecomment-19188685 > .

ungleich-gitea commented

2021-11-20 15:51:01 +00:00

Created by: telmich

Should be fixed with the new way we resolve dependencies.

*Created by: telmich* Should be fixed with the new way we resolve dependencies.

ungleich-gitea commented

2021-11-20 15:51:03 +00:00

Created by: telmich

I've to double check the depedency solver - this may have
been something we broke by removing the old resolver!

Nico

Tyler Akins [Sun, May 26, 2013 at 06:01:11PM -0700]:

If I change the require line to this ...
require="__apt_update_index/singleton" \
Then it works like a charm. Isn't there a way to have the __apt_update_index singleton be required by __apt_ppa in such a way that __apt_ppa is not satisfied until after the __apt_update_index is complete? I wouldn't want to have other types that trigger each other and then I'd have to list all of them instead of the one that I intend to use a couple lines above. Is there something easy that I am missing?

Reply to this email directly or view it on GitHub:
https://github.com/telmich/cdist/issues/175#issuecomment-18474024

PGP key: 7ED9 F7D3 6B10 81D7 0EC5 5C09 D7DC C8E4 3187 7DF0

*Created by: telmich* I've to double check the depedency solver - this may have been something we broke by removing the old resolver! Nico Tyler Akins [Sun, May 26, 2013 at 06:01:11PM -0700]: > If I change the require line to this ... > > ``` > require="__apt_update_index/singleton" \ > ``` > > Then it works like a charm. Isn't there a way to have the __apt_update_index singleton be required by __apt_ppa in such a way that __apt_ppa is not satisfied until after the __apt_update_index is complete? I wouldn't want to have other types that trigger each other and then I'd have to list all of them instead of the one that I intend to use a couple lines above. Is there something easy that I am missing? > > --- > > Reply to this email directly or view it on GitHub: > https://github.com/telmich/cdist/issues/175#issuecomment-18474024 ## PGP key: 7ED9 F7D3 6B10 81D7 0EC5 5C09 D7DC C8E4 3187 7DF0

ungleich-gitea commented

2021-11-20 15:51:04 +00:00

Created by: fidian

If I change the require line to this ...

require="__apt_update_index/singleton" \

Then it works like a charm. Isn't there a way to have the __apt_update_index singleton be required by __apt_ppa in such a way that __apt_ppa is not satisfied until after the __apt_update_index is complete? I wouldn't want to have other types that trigger each other and then I'd have to list all of them instead of the one that I intend to use a couple lines above. Is there something easy that I am missing?

*Created by: fidian* If I change the require line to this ... ``` require="__apt_update_index/singleton" \ ``` Then it works like a charm. Isn't there a way to have the __apt_update_index singleton be required by __apt_ppa in such a way that __apt_ppa is not satisfied until after the __apt_update_index is complete? I wouldn't want to have other types that trigger each other and then I'd have to list all of them instead of the one that I intend to use a couple lines above. Is there something easy that I am missing?

Sign in to join this conversation.