abra app upgrade -f reports "no published release discovered" #444
Closed
opened 2023-04-12 09:29:18 +00:00 by decentral1se
·
4 comments
Labels
Clear labels
abra
awaiting-feedback
backups
bug
build
ci/cd
community organising
contributing
coopcloud.tech
design
documentation
duplicate
enhancement
fedi
fedi-infra
finance
funding
good first issue
help wanted
installer
legal
performance
proposal
question
security
test
wontfix
Everything to do with abra
Ping/pong on comms
Something is not working
Go build related issues
Getting the robots into the mix
Opening this thing up
Contributors stuff
Our main website
Design thinking required
Let's write things together
This issue or pull request already exists
New feature
Democratic decision making
Money things
Anything related to grant funding
Easy start with development
Need some help
Installation related issues
Performance related
Large change which requires feedback & decisin making
More information is needed
Securing our shit
Unit or integration test suite
This won't be fixed
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Assignees
3wordchant
aadil (Aadil Ayub)
abra-bot (Abra Bot)
ammaratef45
amras (Sarma)
Apfelwurm
BornDeleuze (Born Deleuze)
Brooke
carla
cas (Cassowary)
coopcloud
cyrnel
dannygroenewegen (Danny Groenewegen)
decentral1se (d1)
dede
devydave
fauno (fauno)
iexos
jade (Jade Ambrose)
jjsfunhouse
jmakdah2 (Jackie Makdah)
joe-irving (Joe Irving)
kawaiipunk (KawaiiPunk)
knoflook
kolaente
lambdabundesverband
linnealovespie (April)
moosemower
moritz
notplants
oxaliq (sorrel)
p4u1 (p4u1)
pharaohgraphy (Andrew 🐦🔥❤️🔥✴️)
renovate-bot (Comrade Renovate Bot)
ripclap
simon
sixsmith (Sixsmith)
stevensting (stevensting)
trav (Trav Fryer)
val (val (he/him))
yksflip
Clear assignees
No Assignees
decentral1se
Notifications
Total Time Spent: 1 hour 30 minutes
decentral1se
1 hour 30 minutes
No due date set.
Dependencies
No dependencies set.
Reference: toolshed/organising#444
Reference in New Issue
Block a user
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
I have a matrix-synapse install which is on the latest catalogue version. I've just upgraded it. While reading coop-cloud/organising#440 I wanted to try
upgrade -fto see what it does. It reports:I can confirm that I have the latest catalogue locally and the recipe is up-to-date. So, I am not sure what's going on? I was hoping that it would have the same functionality as
deploy -fwhich does work.I've seen this too, also unsure of cause.
Also happening to me even on a fresh deploy.
-doutput.coop-cloud/abra#329 coming down the tubes...
@3wordchant coop-cloud/organising#444 (comment) seems to be an unrelated issue to do with
deploylogic. From the error message, it seems thatabrahad figured outchoosing 3.5.0+v1.81.0 as version to deployfrom the catalogue but then foundread 1.0.1+1.48.0, 1.1.0+v1.51.0, 1.2.0+v1.52.0, 1.3.0+v1.55.2, 2.0.0+v1.58.1, 2.1.0+v1.62.0, 2.2.0+v1.68.0, 2.3.0+v1.71.0, 2.4. 0+v1.72.0, 2.5.0+v1.73.0, 2.6.0+v1.74.0, 3.0.0+v1.74.0, 3.1.0+v1.76.0, 3.2.0+v1.77.0, 3.3.0+v1.78.0from the recipe.It's definitely there:
I can confirm the code of
EnsureVersiondetects them all:Any ideas why
abracouldn't read those tags? Putting some bogus version in the catalogue and then trying to run the commands, I can reproduce the error. So, it just seems the catalogue is out of sync somehow with the local recipe repository? I changed the error message to be more helpful for next time, if we can't get an answer to this now (9f478dac1d/pkg/recipe/recipe.go (L320)).Ah, let's focus on that issue on coop-cloud/organising#414.