[13:52:25]
<ljf> About mount --bind:
* some apps are unable to follow symlink,
* some apps could (or should) be chrooted so mount is a good way to access file in this case
[13:54:37]
<ljf> however you are right (it needs /etc/fstab management... so it could failed for x reasons and create bugs like no space in a partition, file that disappear or whatever)
[13:54:46]
<bettyvschmartz> It could also cause issue with backup too couldn't it?
[13:56:57]
<ljf> deduplicated backup should backup data one times, but if you don't use deduplication it could increase the size of the backup. Restore is a pain if you have a lot of `mount --bind` everywhere i guess.
[13:56:58]
<bettyvschmartz> > <@ljf:sans-nuage.fr> deduplicated backup should backup data one times, but if you don't use deduplication it could increase the size of the backup. Restore is a pain if you have a lot of `mount --bind` everywhere i guess.
That is true with dedup
[13:57:04]
<ljf> In more backup multimedia folder is still a big question (due to people that use it for sharing video between apps)
[13:59:38]
<ljf> That means finding a way to indicates which files should be ignored by default in backup... (or something like that)
[13:59:39]
<Yunohost Git/Infra notifications> [yunohost/dev] appsv2: add support for a packages_from_raw_bash option in apt where one can add a multiline bash snippet to echo packag... - Alexandre Aubin
[13:59:39]
<Yunohost Git/Infra notifications> [yunohost] @alexAubin pushed 3 commits to dev ([b887545c3e23...888593ad223d](https://github.com/YunoHost/yunohost/compare/b887545c3e23...888593ad223d))
[13:59:39]
<Yunohost Git/Infra notifications> [yunohost/dev] appsv2: fix resource provisioning scripts picking up already-closed operation logger, resulting in confusing debugging o... - Alexandre Aubin
[13:59:39]
<Yunohost Git/Infra notifications> [yunohost/dev] apps: add YNH_DEBIAN_VERSION variable in apps contexts - Alexandre Aubin
[16:24:23]
<Yunohost Git/Infra notifications> [yunohost] @Axolotle pushed 7 commits to pydantic-configpanel ([cb965d9b9421^...15daf82a6fb3](https://github.com/YunoHost/yunohost/compare/cb965d9b9421^...15daf82a6fb3))
[16:24:23]
<Yunohost Git/Infra notifications> [yunohost] @Axolotle opened [pull request #1603](https://github.com/YunoHost/yunohost/pull/1603): WIP: Use pydantic for config panels and app install
[16:24:23]
<Yunohost Git/Infra notifications> [yunohost] @alexAubin pushed 1 commit to dev: ci: hmf try to understand what that re2 syntax gitlab is talking about is ([4fd10b5a](https://github.com/YunoHost/yunohost/commit/4fd10b5a1d0027ff43f0e48d39b1cb05474c4714))
[16:24:23]
<Yunohost Git/Infra notifications> [yunohost] 🔴 Pipeline [#784480076](https://gitlab.com/yunohost/yunohost/-/pipelines/784480076) failed on branch pydantic-configpanel
[16:24:23]
<Yunohost Git/Infra notifications> ✔️ Completed build for yunohost/11.1.9+202302211615 for bullseye/unstable/all.
[16:24:23]
<Yunohost Git/Infra notifications> [yunohost/pydantic-configpanel] form: add prompt/fill generic function for simple list of options - axolotle
[16:24:39]
<Yunohost Git/Infra notifications> [yunohost] @Axolotle created new branch pydantic-configpanel
[16:24:39]
<Yunohost Git/Infra notifications> [yunohost] 🔴 Pipeline [#784477666](https://gitlab.com/yunohost/yunohost/-/pipelines/784477666) failed on branch dev
[16:24:39]
<Yunohost Git/Infra notifications> [yunohost] 🔴 Pipeline [#784451222](https://gitlab.com/yunohost/yunohost/-/pipelines/784451222) failed on branch pydantic-configpanel
[16:24:39]
<Yunohost Git/Infra notifications> [yunohost/dev] appsv2: fix reload_only_if_change option not working as expected, resulting in incorrect Firewall reloaded messages - Alexandre Aubin
[16:24:39]
<Yunohost Git/Infra notifications> [yunohost/pydantic-configpanel] update domain.py to new config panel - axolotle
[16:24:39]
<Yunohost Git/Infra notifications> [yunohost] @alexAubin pushed 2 commits to dev ([888593ad223d...1dc8b75315ab](https://github.com/YunoHost/yunohost/compare/888593ad223d...1dc8b75315ab))
[16:24:39]
<Yunohost Git/Infra notifications> [yunohost] @github-code-scanning[bot] commented [pull request #1603](https://github.com/YunoHost/yunohost/pull/1603#pullrequestreview-1307756750) WIP: Use pydantic for config panels and app install : CodeQL found more than 10 potential problems in the proposed changes. Check the [Files changed](/YunoHost/yunohost/pull/...
[16:24:39]
<Yunohost Git/Infra notifications> [yunohost/pydantic-configpanel] app_install: use new generic prompt/fill for install questions - axolotle
[16:24:39]
<Yunohost Git/Infra notifications> [yunohost/dev] appsv2: fix check that postgresql db exists... - Alexandre Aubin
[17:05:08]
<Yunohost Git/Infra notifications> [issues] @alexAubin edited [issue #2050](https://github.com/YunoHost/issues/issues/2050): Support Debian 12 "Bookworm"
[17:05:32]
<Yunohost Git/Infra notifications> [issues] @alexAubin edited [issue #2050](https://github.com/YunoHost/issues/issues/2050): Support Debian 12 "Bookworm"
[17:21:24]
<tituspijean[m]> ^ "Past trauma". 😆
[17:23:29]
<Aleks (he/him/il/lui)> yeah
[17:24:43]
<Aleks (he/him/il/lui)> shall we create the "Support Trixie" issue already 👀
[17:24:56]
<tituspijean[m]> Note to self, ask ChatGPT to generate a Nostradamus-like prediction about {the challenges of upgrading Debian, enduring demanding project management wanabies}
[17:25:04]
<Aleks (he/him/il/lui)> hell, let's create all the "Support Debian N" with N up to 20 already :P
[17:25:10]
<Aleks (he/him/il/lui)> haha
[17:25:44]
<Aleks (he/him/il/lui)> "Can you create an issue comment, in the style of Neustradamus, a famous YunoHost non-contributor"
[17:26:01]
<tituspijean[m]> "infamous" would be word
[17:26:10]
<Aleks (he/him/il/lui)> :D
[17:26:19]
<tituspijean[m]> (also, DON'T YOU DARE)
[17:29:17]
<tituspijean[m]> oh god oh god
[17:29:26]
<Aleks (he/him/il/lui)> wut
[17:29:37]
<tituspijean[m]> it's making a whole poem
[17:29:41]
<Aleks (he/him/il/lui)> what xD
[17:29:56]
<tituspijean[m]> In the style of Nostradamus, I offer the following prediction regarding the difficulties of upgrading Debian:
"When the stars align and the moon wanes,
Debian users shall face trials and pains.
Upgrading their systems, they shall find,
Will be a task that tests the mind.
Bugs and errors shall arise with great force,
Resisting all efforts to stay on course.
The code shall prove a labyrinthine maze,
And the user shall long for simpler days.
Yet fear not, for all hope is not lost,
With knowledge and patience, the line can be crossed.
Through perseverance and diligent care,
The Debian user shall emerge, triumphant and fair."
May this prediction serve as a reminder that while upgrading Debian may come with its challenges, with dedication and persistence, it is a task that can be accomplished.
[17:30:28]
<Aleks (he/him/il/lui)> omg
[17:30:44]
<eric_G> he must have gotten the wrong Nostradamus
[17:30:54]
<Aleks (he/him/il/lui)> >The code shall prove a labyrinthine maze,
And the user shall long for simpler days.
[17:31:09]
<tituspijean[m]> I was willingly asking for Nostra, not Neustra 😛
[17:32:05]
<Aleks (he/him/il/lui)> we should add this poem as disclaimer for the next debian upgrade
[17:32:31]
<tituspijean[m]> erf, it ignores the "mispelling" of Neustra/Nostra:
[17:32:33]
<tituspijean[m]> Can you create an issue comment, in the style of Neustradamus, an infamous YunoHost non-contributor
In the style of Nostradamus, I offer the following issue comment from an infamous YunoHost non-contributor:
"Oh YunoHost, the system of my disdain,
I bring forth my thoughts, but they are in vain.
Your code is a labyrinth, a puzzle to behold,
A feat of engineering, but your issues never get old.
I see your contributors toil and sweat,
Trying to fix bugs and close PRs, I bet.
But alas, it seems the road is long,
And the end of it is always wrong.
Your documentation is obscure and dense,
Trying to decipher it makes no sense.
I shout into the void, but no one hears my cries,
Asking myself why bother, it's all just lies.
But still I must try, for I know deep inside,
That YunoHost can be a great ride.
So I'll pick up the gauntlet, and charge forth with might,
And maybe one day, I'll get it right."
May this comment serve as a reminder that even though YunoHost may be challenging for some, there are those who persevere and continue to work towards making it better. And who knows, with dedication and effort, even the most infamous non-contributor may one day become a valuable member of the community.
[17:32:56]
<Aleks (he/him/il/lui)> >A feat of engineering, but your issues never get old.
[17:32:58]
<Aleks (he/him/il/lui)> i'm dying
[17:33:08]
<tituspijean[m]> OK that's a lie.
[17:33:34]
<Aleks (he/him/il/lui)> >Your documentation is obscure and dense,
Trying to decipher it makes no sense.
omg
[17:33:38]
<Aleks (he/him/il/lui)> howdareyou.jpg
[17:33:59]
<tituspijean[m]> First documented (hum) instance of emotional damage by a robot
[17:34:38]
<Aleks (he/him/il/lui)> >even the most infamous non-contributor may one day become a valuable member of the community.
😬 u wot m8
[17:35:07]
<tituspijean[m]> "Don't make Neustra happen, it is not gonna happen."
[17:36:24]
<Aleks (he/him/il/lui)> can you ask ChatGPT what is the SCRAM-SHA thingy Neustradamus is always rambling about ? 😬
[17:38:01]
<tituspijean[m]> It's taking the high road 😕
[17:38:17]
<tituspijean[m]> `What is the SCRAM-SHA thingy Neustradamus is always rambling about ?`
I'm sorry, but as an AI language model, I don't have any information about a person named Neustradamus and their rants on SCRAM-SHA. However, I can provide an explanation of what SCRAM-SHA is.
SCRAM-SHA (Salted Challenge Response Authentication Mechanism - Secure Hash Algorithm) is a widely used authentication mechanism in the context of web applications and databases. It is designed to prevent password-based attacks, such as brute-force or dictionary attacks, by incorporating a random "salt" value and an iterative hashing function. The salt value is a random string that is added to the password before hashing, making it unique for each user and protecting against precomputed tables or rainbow tables that hackers can use to crack passwords. The iterative hashing function is applied multiple times to slow down password guessing attacks.
In the context of web applications and databases, SCRAM-SHA is often used with protocols such as LDAP, MongoDB, and PostgreSQL to provide secure authentication of users. It is considered a strong and secure authentication mechanism and is recommended as a best practice for password-based authentication.
[17:41:56]
<Aleks (he/him/il/lui)> so it's like just salted hashes ? x_X
[17:42:22]
<Aleks (he/him/il/lui)> i'm just as confused as to what exactly he was rambling about ... I thought this was like a brand new thing or whatever ..
[17:44:15]
<Aleks (he/him/il/lui)> anyway, goude niouze aivriouane, there's now RAM metric in the CI thanks to the PR from Salamandar /o/
[17:46:09]
<Salamandar> > <@Alekswag:matrix.org> anyway, goude niouze aivriouane, there's now RAM metric in the CI thanks to the PR from Salamandar /o/
Oh wow, it works ? :p
[17:47:02]
<Aleks (he/him/il/lui)> yup ;P
[17:47:03]
<Salamandar> Oh nice, for an untested code O:)
[17:47:25]
<Aleks (he/him/il/lui)> I tweaked it a bit tho, such that it only measures the diff/peak right around the start of the install, otherwise the full test includes a bunch of LXC snapshot create/restore and I'm guessing this loosen the accuracy etc
[17:47:40]
<Salamandar> Yeah I can see the "ram usage diff after test"
[17:47:48]
<Aleks (he/him/il/lui)> https://ci-apps-dev.yunohost.org/ci/job/5772
>RAM usage diff after test: -144MB
well eh
[17:48:05]
<Salamandar> Is it only ran on install/restore/upgrade ?
[17:48:11]
<Salamandar> (i don't see the message on remove for example)
[17:48:29]
<Aleks (he/him/il/lui)> install, upgrade, restore
[17:48:32]
<Aleks (he/him/il/lui)> remove aint really relevant
[17:48:36]
<Salamandar> reinstall after remove neither
[17:48:38]
<Salamandar> https://ci-apps.yunohost.org/ci/job/13740
[17:49:17]
<Salamandar> > <@Alekswag:matrix.org> https://ci-apps-dev.yunohost.org/ci/job/5772
>
> >RAM usage diff after test: -144MB
>
> well eh
oh weird ahah
[17:49:23]
<Aleks (he/him/il/lui)> yeah whatever, i mean the point is mostly to know roughly that you need Xish hundreds of MB to prevent situation where people install an app that need an important quantity of RAM to not miserably crash during the build
[17:49:34]
<Salamandar> > <@Alekswag:matrix.org> yeah whatever, i mean the point is mostly to know roughly that you need Xish hundreds of MB to prevent situation where people install an app that need an important quantity of RAM to not miserably crash during the build
Yeah i fully understand :D
[17:50:58]
<Aleks (he/him/il/lui)> now I'm wondering if `free` inside the container does yield something independent of other LXCs or not :/
[17:59:04]
<Yunohost Git/Infra notifications> [yunohost] @alexAubin created new tag debian/11.1.10
[17:59:04]
<Yunohost Git/Infra notifications> [yunohost] @alexAubin pushed 1 commit to dev: Update changelog for 11.1.10 ([232d38f2](https://github.com/YunoHost/yunohost/commit/232d38f22187d5e0a6635f047c6c9eb161d36751))
[18:00:21]
<Yunohost Git/Infra notifications> 🏗️ Starting build for yunohost/11.1.10+202302211800 for bullseye/unstable/all ...
[18:01:41]
<Yunohost Git/Infra notifications> ✔️ Completed build for yunohost/11.1.10+202302211800 for bullseye/unstable/all.
[18:05:48]
<Yunohost Git/Infra notifications> [yunohost] @alexAubin [commented](https://github.com/YunoHost/yunohost/pull/1602#discussion_r1113405353) on pull request #1602 feat: add --continue-on-failure to yunohost app upgrade: Im wondering if we shouldnt still *not* continue if broke_the_system is True ... like, this means that either dpkg is...
[18:05:48]
<Yunohost Git/Infra notifications> [yunohost] @alexAubin approved [pull request #1602](https://github.com/YunoHost/yunohost/pull/1602#pullrequestreview-1307930363) feat: add --continue-on-failure to yunohost app upgrade
[18:05:49]
<Yunohost Git/Infra notifications> [yunohost] @alexAubin [commented](https://github.com/YunoHost/yunohost/pull/1602#discussion_r1113406450) on pull request #1602 feat: add --continue-on-failure to yunohost app upgrade: suggestion "app_failed_to_upgrade_but_continue": "Application {failed_app} failed to upgrade, but YunoHost will c...
[18:05:51]
<Yunohost Git/Infra notifications> [yunohost] @alexAubin [commented](https://github.com/YunoHost/yunohost/pull/1602#discussion_r1113407133) on pull request #1602 feat: add --continue-on-failure to yunohost app upgrade: suggestion "apps_failed_to_upgrade_line": "\n * {app_id} (to see corresponding error logs, use yunohost log show...
[18:05:51]
<Yunohost Git/Infra notifications> [yunohost] @alexAubin [commented](https://github.com/YunoHost/yunohost/pull/1602#discussion_r1113406583) on pull request #1602 feat: add --continue-on-failure to yunohost app upgrade: suggestion "apps_failed_to_upgrade": "Those applications failed to upgrade: {apps}",
[18:05:51]
<Yunohost Git/Infra notifications> [yunohost] @alexAubin edited review [pull request #1602](https://github.com/YunoHost/yunohost/pull/1602#pullrequestreview-1307930363): feat: add --continue-on-failure to yunohost app upgrade
[18:07:55]
<Aleks (he/him/il/lui)> yay the coverage badge is fixed in YunoHost's README /o/
[18:08:03]
<Aleks (he/him/il/lui)> we have ... 45% /o/
[18:08:10]
<Aleks (he/him/il/lui)> ¯\_(ツ)_/¯ which is larger than 0
[18:19:24]
<Yunohost Git/Infra notifications> [issues] @zamentur [commented](https://github.com/YunoHost/issues/issues/2154#issuecomment-1438913045) on [issue #2154](https://github.com/YunoHost/issues/issues/2154) Be able to inject a password hash for users to ease migrating between systems: Its a good idea however this feature will not be compatible with some user_update hooks that need YNH_USER_PASSWORD b...
[18:23:48]
<Yunohost Git/Infra notifications> [yunohost] @alexAubin pushed 1 commit to dev: swag: update README badges ([127c241c](https://github.com/YunoHost/yunohost/commit/127c241c9a42d930f5bbc4f646a5016942966738))
[18:24:07]
<Yunohost Git/Infra notifications> [yunohost] ✖️ Pipeline [#784578098](https://gitlab.com/yunohost/yunohost/-/pipelines/784578098) canceled on branch dev
[18:30:16]
<Yunohost Git/Infra notifications> 🏗️ Starting build for yunohost/11.1.10+202302211830 for bullseye/unstable/all ...
[18:31:26]
<Yunohost Git/Infra notifications> ✔️ Completed build for yunohost/11.1.10+202302211830 for bullseye/unstable/all.
[18:33:55]
<Yunohost Git/Infra notifications> [yunohost-admin] @alexAubin pushed 2 commits to dev ([b746aa9ce1a0...c54ca1c6fe98](https://github.com/YunoHost/yunohost-admin/compare/b746aa9ce1a0...c54ca1c6fe98))
[18:33:59]
<Yunohost Git/Infra notifications> [yunohost-admin/dev] swag: update README badges - Alexandre Aubin
[18:34:37]
<Yunohost Git/Infra notifications> [yunohost-admin/dev] Delete CONTRIBUTORS.md ... hasnt been updated in 6 years ... - Alexandre Aubin
[18:34:40]
<Yunohost Git/Infra notifications> [yunohost] @alexAubin pushed 1 commit to dev: Remove .lgtm.yml, the service doesnt exists anymore :| ([87243297](https://github.com/YunoHost/yunohost/commit/872432973854707e5630c32db8dc00b313f9e663))
[18:34:48]
<Yunohost Git/Infra notifications> [yunohost] ✖️ Pipeline [#784597994](https://gitlab.com/yunohost/yunohost/-/pipelines/784597994) canceled on branch dev
[18:45:08]
<Yunohost Git/Infra notifications> [yunohost] @alexAubin pushed 1 commit to dev: ci: zblerg, try to fix the coverage thingy computing coverage on test and vendor files x_x ([90b8e78e](https://github.com/YunoHost/yunohost/commit/90b8e78effb7315b779ca0610231438f4e84fee2))
[18:45:15]
<Yunohost Git/Infra notifications> 🏗️ Starting build for yunohost/11.1.10+202302211845 for bullseye/unstable/all ...
[18:46:07]
<Yunohost Git/Infra notifications> [yunohost] ✖️ Pipeline [#784605608](https://gitlab.com/yunohost/yunohost/-/pipelines/784605608) canceled on branch dev
[18:46:26]
<Yunohost Git/Infra notifications> ✔️ Completed build for yunohost/11.1.10+202302211845 for bullseye/unstable/all.
[18:46:32]
<Yunohost Git/Infra notifications> 🏗️ Starting build for yunohost-admin/11.1.6+202302211845 for bullseye/unstable/all ...
[18:52:26]
<Yunohost Git/Infra notifications> ✔️ Completed build for yunohost-admin/11.1.6+202302211845 for bullseye/unstable/all.
[19:33:57]
<mh4ckt3mh4ckt1c4s> Hi, can somebody if we need increasing versions in a package to be able to trigger an update ? Or just a change ? Because I'm on packaging searxng which is a rolling release and there is no version per se, so I thought about using the commit hash for the version but I'm not sure this will not trigger any bugs with the update detection within ynh
[19:34:08]
<Yunohost Git/Infra notifications> [yunohost] @zamentur [commented](https://github.com/YunoHost/yunohost/pull/1603#issuecomment-1438967227) on [issue #1603](https://github.com/YunoHost/yunohost/pull/1603) WIP: Use pydantic for config panels and app install : Note: i use also configpanel into backup pr https://github.com/YunoHost/yunohost/pull/531/files
[19:47:18]
<Yunohost Git/Infra notifications> @milouse forked yunohost to [milouse/yunohost](https://github.com/milouse/yunohost)
[19:50:12]
<Yunohost Git/Infra notifications> [yunohost] @yunohost-bot created new branch ci-format-debian/11.1.10
[19:50:12]
<Yunohost Git/Infra notifications> [yunohost] @yunohost-bot opened [pull request #1604](https://github.com/YunoHost/yunohost/pull/1604): [CI] Format code with Black
[19:50:12]
<Yunohost Git/Infra notifications> [yunohost] @yunohost-bot pushed 1 commit to ci-format-debian/11.1.10: [CI] Format code with Black ([aa50526c](https://github.com/YunoHost/yunohost/commit/aa50526ccdc3b5ffc3ef10e641015185fe32886d))
[19:55:21]
<Aleks (he/him/il/lui)> > Hi, can somebody if we need increasing versions in a package to be able to trigger an update ? Or just a change ? Because I'm on packaging searxng which is a rolling release and there is no version per se, so I thought about using the commit hash for the version but I'm not sure this will not trigger any bugs with the update detection within ynh
if there's no version per se, then I would recommend using the date, e.g. 2023.02.21
[19:56:19]
<Aleks (he/him/il/lui)> like yes one way or another you need to have increasing versions, with numbers separated by dots
[19:59:47]
<Yunohost Git/Infra notifications> [yunohost] @milouse opened [pull request #1605](https://github.com/YunoHost/yunohost/pull/1605): regenconf: Add a new ssh security setting to hide the banner
[20:00:41]
<tituspijean[m]> > <@Alekswag:matrix.org> like yes one way or another you need to have increasing versions, with numbers separated by dots
I would preface the date with `0.`, just in case they change their version scheme at some point.
[20:01:48]
<Aleks (he/him/il/lui)> yeah +1
[20:03:53]
<Yunohost Git/Infra notifications> [yunohost] @alexAubin pushed 2 commits to dev ([90b8e78effb7...79c9a7b29459](https://github.com/YunoHost/yunohost/compare/90b8e78effb7...79c9a7b29459))
[20:03:53]
<Yunohost Git/Infra notifications> [yunohost] @alexAubin merged [pull request #1604](https://github.com/YunoHost/yunohost/pull/1604): [CI] Format code with Black
[20:03:55]
<Yunohost Git/Infra notifications> [yunohost] @alexAubin deleted branch ci-format-debian/11.1.10
[20:03:56]
<Yunohost Git/Infra notifications> [yunohost/dev] [CI] Format code with Black - yunohost-bot
[20:04:01]
<Yunohost Git/Infra notifications> [yunohost/dev] Merge pull request #1604 from YunoHost/ci-format-debian/11.1.10 [CI] Format code with Black - Alexandre Aubin
[20:04:30]
<Yunohost Git/Infra notifications> [yunohost] ✖️ Pipeline [#784613039](https://gitlab.com/yunohost/yunohost/-/pipelines/784613039) canceled on branch dev
[20:13:19]
<Yunohost Git/Infra notifications> 🏗️ Starting build for yunohost/11.1.10 for bullseye/stable/all ...
[20:14:27]
<Yunohost Git/Infra notifications> ✔️ Completed build for yunohost/11.1.10 for bullseye/stable/all.
[20:16:03]
<Yunohost Git/Infra notifications> 🏗️ Starting build for yunohost/11.1.10+202302212015 for bullseye/unstable/all ...
[20:17:26]
<Yunohost Git/Infra notifications> ✔️ Completed build for yunohost/11.1.10+202302212015 for bullseye/unstable/all.
[20:31:37]
<Yunohost Git/Infra notifications> [yunohost] @Axolotle [commented](https://github.com/YunoHost/yunohost/pull/1603#issuecomment-1439054886) on [issue #1603](https://github.com/YunoHost/yunohost/pull/1603) WIP: Use pydantic for config panels and app install : > Note: i use also configpanel into backup pr https://github.com/YunoHost/yunohost/pull/531/files oh god
[20:41:57]
<mh4ckt3mh4ckt1c4s> > <@Alekswag:matrix.org> if there's no version per se, then I would recommend using the date, e.g. 2023.02.21
Thanks, I'll do that then. Any idea to deal with multiple commits the same day ?
[21:01:58]
<Aleks (he/him/il/lui)> hmmm you could add the hour+minute i guess...
[21:02:22]
<Aleks (he/him/il/lui)> i mean 2023.02.21.22.02 for example
[21:27:43]
<mh4ckt3mh4ckt1c4s> Yeah that'd be the simplest I guess
[22:01:14]
<Yunohost Git/Infra notifications> [yunohost] 🔴 Pipeline [#784657242](https://gitlab.com/yunohost/yunohost/-/pipelines/784657242) failed on branch dev
[22:55:13]
<Yunohost Git/Infra notifications> [yunohost] @Psycojoker [commented](https://github.com/YunoHost/yunohost/pull/1602#discussion_r1113652731) on pull request #1602 feat: add --continue-on-failure to yunohost app upgrade: Ah yeah make totally sens :)
[22:55:14]
<Yunohost Git/Infra notifications> [yunohost] @Psycojoker pushed 1 commit to app-upgrade-continue-on-failures: Update locales/en.json Co-authored-by: Alexandre Aubin <alex.aubin@mailoo.org> ([31676504](https://github.com/YunoHost/yunohost/commit/316765042a80fa124150721ef350f79c5e41a5c1))
[22:57:21]
<Yunohost Git/Infra notifications> [yunohost] @Psycojoker [commented](https://github.com/YunoHost/yunohost/pull/1602#discussion_r1113654227) on pull request #1602 feat: add --continue-on-failure to yunohost app upgrade: Im dont think you want that because this is merged with the next line en en.json that will add a "\n" (but tbf it won...
[22:57:21]
<Yunohost Git/Infra notifications> [yunohost] @Psycojoker pushed 1 commit to app-upgrade-continue-on-failures: Update locales/en.json Co-authored-by: Alexandre Aubin <alex.aubin@mailoo.org> ([961c3fef](https://github.com/YunoHost/yunohost/commit/961c3fef2ac554918e029211e3285c6c532740b4))
[23:00:57]
<Yunohost Git/Infra notifications> [yunohost] 🔴 Pipeline [#784807511](https://gitlab.com/yunohost/yunohost/-/pipelines/784807511) failed on branch app-upgrade-continue-on-failures