search

cassava / repoctl

Make it easy to manage your local Arch Linux repository.
MIT License
125 stars 14 forks source link

repoctl update - Error: exit status 1 #38

Closed aphirst closed 6 years ago

aphirst commented 6 years ago

I've set up repoctl to be used with a "custom" repo for aurutils (release, not -git, since I keep hitting -git releases where basic functionality is broken). To the best of my knowledge, I set up both in accordance with the aurutils documentation.

I've been removing some old, redundant package files from my "custom" repo folder, and also their build files from aurutils' build folder, and my understanding is that I'm supposed to be able to use repoctl update to ensure that these are not repeatedly redownloaded and rebuild, as is the intended behaviour when the packages are still "in" the custom database.

However, when I run repoctl update, I get the following output:

[adam@rakka custom]$ repoctl update --debug
removing package from database: 
removing package from database: gitg-git
removing package from database: icedove-enigmail-bin
removing package from database: ioquake3-git
Error: exit status 1

Those 3 named packages are ones I only just deleted. I was getting the exit status error even before I removed those.

I get the same output each time, which makes it look as if it's hitting the error before actually committing any changes.

I was asking about this in #aurutils on Freenode, but we hit a bit of a dead end working out what was going on.

I'd appreciate any ideas trying to work out what's gone wrong, and if there's anything more I can provide, please just ask. By being documented, hopefully future users should ultimately be able to avoid the same hurdle.

hcnelson99 commented 6 years ago

I am encountering this exact issue as well

aphirst commented 6 years ago

I managed to "fix" things by deleting the old repository files, and regenerating. I never worked out the underlying cause.

hcnelson99 commented 6 years ago

The above fix worked. Close this issue unless we can find a way to reproduce?

aphirst commented 6 years ago

I agree. It can always be reopened later if anyone else works out how to reproduce.

cassava commented 6 years ago

Woah! Didn't mean to leave you hanging there for so long! I've been a little under water of late. Sorry bout that!

cassava commented 6 years ago

When you say the "old repository files" you don't mean the actual packages do you? The database?

aphirst commented 6 years ago

Yes, it was just the database files I removed. I generated a new one based on the package files, following the same instructions as when I initially set up my aurutils custom repo.

AladW commented 6 years ago

It might help to get the actual output from repo-remove, which I believe repoctl runs on removing packages from the db.

cassava commented 6 years ago

repoctl does use repo-add and repo-remove in the background. The idea was to save me some work, both now and in the future. Getting the output though would be useful for the error case; propagating them to the user might be a challenge.