Disappearing/missing packages #122

Closed
opened 2022-05-20 12:01:59 +02:00 by sirlucjan · 11 comments

Hi,

Thanks for the great work you are doing. I noticed yesterday that packages like gtk3, qt5-base and qt5-declarative have disappeared from the repositories. Today, packages like mesa, llvm, linux, linux-headers are also gone. What is the reason for this? Will these packages return to the repo?

Best regards.

Hi, Thanks for the great work you are doing. I noticed yesterday that packages like gtk3, qt5-base and qt5-declarative have disappeared from the repositories. Today, packages like mesa, llvm, linux, linux-headers are also gone. What is the reason for this? Will these packages return to the repo? Best regards.
anonfunc added the bug label 2022-05-20 12:23:39 +02:00
Owner

Hi @sirlucjan,

yes, they should have never left the repo. There seems to be a bug somewhere in the package-purge logic. I'll have a look.

Hi @sirlucjan, yes, they should have never left the repo. There seems to be a bug somewhere in the package-purge logic. I'll have a look.
Owner

I think I found the problem. Should be fixed with the last few commits. I'll keep monitoring for a while, we can leave this open until we are sure it does not repeat.

I think I found the problem. Should be fixed with the last few commits. I'll keep monitoring for a while, we can leave this open until we are sure it does not repeat.
Author

Thanks a lot. You are doing a great job and for that I really thank you.

Thanks a lot. You are doing a great job and for that I really thank you.
Author

I see that packages are being built/queued. When can we expect them in the repo?

I see that packages are being built/queued. When can we expect them in the repo?
Contributor

@anonfunc well, they were there, but in an older version. I saw that and thought it's kinda intentional if the new versions are still building. But they never came back :(

For example: :: firefox: local (100.0.2-1) is newer than extra-x86-64-v3 (100.0.1-1.1)

I see that packages are being built/queued. When can we expect them in the repo?

They are done when they are done :P

@anonfunc well, they were there, but in an older version. I saw that and thought it's kinda intentional if the new versions are still building. But they never came back :( For example: `:: firefox: local (100.0.2-1) is newer than extra-x86-64-v3 (100.0.1-1.1)` > I see that packages are being built/queued. When can we expect them in the repo? They are done when they are done :P
Owner

Seems like some of them are stuck in a build loop. They get build, housekeeping then resets them since their repo-version is not set for some reason. I'll have another look, something is still not working as intended.

EDIT: I think I found it. I accidentally removed packages from the repo which were up-to-date. Should be fine when the next build-cycle finishes.

Seems like some of them are stuck in a build loop. They get build, housekeeping then resets them since their repo-version is not set for some reason. I'll have another look, something is still not working as intended. EDIT: I think I found it. I accidentally removed packages from the repo which were up-to-date. Should be fine when the next build-cycle finishes.
Author

Thanks again and sorry for bothering you :)

Thanks again and sorry for bothering you :)
Contributor

@anonfunc

I found the culprit regarding firefox:

https://git.harting.dev/ALHP/ALHP.GO/pulls/123

@anonfunc I found the culprit regarding firefox: https://git.harting.dev/ALHP/ALHP.GO/pulls/123
Author

@anonfunc I hope the problem has been resolved. Let me know then I will close the thread.

@anonfunc I hope the problem has been resolved. Let me know then I will close the thread.
Owner

Seems this is fixed now.

Seems this is fixed now.
Author

Yes, I've had a major update and everything works as it should. Thanks a lot.

Yes, I've had a major update and everything works as it should. Thanks a lot.
Sign in to join this conversation.