Calckey has been rebranded into Firefish

[alexAubin]

cf https://calckey.social/notes/9fatefrf0h

We should be doing an RC2 for v14 soon, and if everything is fine, we'll release v14 a few days later. However, we're in the process of rebranding, so this might affect new releases a little.

[lapineige]

I saw that but I don't understand what it means.

[alexAubin]

From what I undestand, it means it will be changing name ?

[lapineige]

I guess so ?

[ThatOneCalculator]

From what I undestand, it means it will be changing name ?

Yes

[lapineige]

Thanks for sharing this.

Then we will need to figure out how to rename this app and migrate everyone… 😅

[benborges]

It's live, the new name is Firefish : https://fedi.software/notes/9hdnh5z5hiccne81

[lapineige]

We're already on it, but we need to figure out the best way to migrate this app :)

[Minecodes]

We're already on it, but we need to figure out the best way to migrate this app :)

There's a migration guide in the docs: joinfirefish.org/docs/en/migrating/

[tr1p0p]

We're already on it, but we need to figure out the best way to migrate this app :)

There's a migration guide in the docs: joinfirefish.org/docs/en/migrating/

It's more this that explain how to upgrade from last stable : here Ours seem to be for misskey migration, it's not the same

[ThatOneCalculator]

We're already on it, but we need to figure out the best way to migrate this app :)

There's a migration guide in the docs: joinfirefish.org/docs/en/migrating/

That's for Misskey -> Firefish, not Calckey -> Firefish. The latter should be treated like any other Calckey upgrade.

[lapineige]

And this is mainly a Yunohost packaging issue, it's hard to deal with a changing package name, we have to setup another repository with a working Firefish version, and then set up this one to have a script to migrate everyone flawlessly.

[MatKlein]

Is it possible to provide a functioning repository for Firefish? Then those who want to start a new instance could already get started.

[lapineige]

You will have to wait for us to prepare one :)

[tr1p0p]

And this is mainly a Yunohost packaging issue, it's hard to deal with a changing package name, we have to setup another repository with a working Firefish version, and then set up this one to have a script to migrate everyone flawlessly.

And we cannot just like, keep the id of the apps (like on the manifest file), but just change the name ?

It's just a new name not like, a complete rebuild of the app, so how it can be so difficult to make a upgrade ?

Also to respond @MatKlein : seem they have a "firefish" branch in this repo, so maybe you can try that ?

(Also i volunter to test some build or stuff like that)

[lapineige]

And we cannot just like, keep the id of the apps (like on the manifest file), but just change the name ?

In the short-term, yes. In the long run, this will lead to troubles.

It's better to do the dirty work now, with less chances to break things. People willing to run Calckey v13, or even v14 (RC3, in testing) can still do it for now. For Firefish new installs, a repository will be available soon. Then we will take the time to prepare for a proper migration.

It's just a new name not like, a complete rebuild of the app, so how it can be so difficult to make a upgrade ?

Change in dependencies, way of installing it… it can vary :) In that case, @oufmilo already did the hardwork on the v14 of Calckey (now Firefish). The hard task now is to prepare a migration script.

(Also i volunter to test some build or stuff like that)

Great, appreciated :)

---

Also to respond @MatKlein : seem they have a "firefish" branch in this repo, so maybe you can try that ?

Please don't. I wasn't aware of that branch (lack of coordination, that's another topic) ¹, but it wasn't planned to do it like this. This will make a future migration more complicated, and likely not automated. If you wanna use most of Firefish additions right now, use Calckey v14rc3, available in testing branch. This has been quite tested. Otherwise, for fresh installs a new (tested) repository will be available soon. Please be patient :wink: As for migrations, this will take longer, but yeah, again be patient please, or do it at your own risk (= not being able to migrate (easily) in the future).

¹ well well… I forgot it, but I was aware : #48. But you should not use it anyway, the rest doesn't change, that's now how it will work.

[tituspijean]

FYI I have pushed two different commits to testing and master to add a deprecation notice in the manifest (I wanted to make a PR from testing to master, but discovered there was pending commits in testing). You will need to fix that with the next merging, sorry. 😅