Bug 30240 - Update request QOwnNotes
Summary: Update request QOwnNotes
Status: RESOLVED OLD
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 8
Hardware: All Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL: https://www.qownnotes.org/changelog.html
Whiteboard:
Keywords: UPSTREAM
Depends on:
Blocks:
 
Reported: 2022-04-03 14:37 CEST by Morgan Leijström
Modified: 2024-08-22 23:01 CEST (History)
2 users (show)

See Also:
Source RPM: qownnotes-20.8.10-2.mga8
CVE:
Status comment: To backport as is, if upstream do not fix


Attachments

Description Morgan Leijström 2022-04-03 14:37:35 CEST
This is a great companion to Nextcloud, or standalone.

Version in mga8 : 20.8.10 which it got while it was Cauldron, Bug 27181
Cauldron now have 21.5.3
Upstream released 22.3.4

Lots of incremental bugfixes and translations.
Comment 1 Morgan Leijström 2022-04-03 19:49:01 CEST
David G, you are the registered maintainer :)

Assignee: bugsquad => geiger.david68210

Comment 2 David GEIGER 2023-01-31 06:45:16 CET
You can now test latest qownnotes 23.1.4 in 8/Core/Updates_testing repo!
Comment 3 Morgan Leijström 2023-01-31 12:04:05 CET
mga8-64 OK
Plasma, Intel, nvidia-current, backport kernel
Swedish localisation
Tested editing files locally, and syncing the Notes folder using our nextcloud-client to a NextCloud 25 server which edited same files with the NC app Notes. 

(and with server app QOwnNotres API installed - though I have not tested about that latter functionality as I am not sure what it does)

Seem to be working perfectly, thanks :)

Advisory?

Whiteboard: (none) => MGA8-64-OK
Keywords: (none) => validated_update
CC: (none) => sysadmin-bugs

Comment 4 David GEIGER 2023-01-31 18:14:54 CET
Feel free to do an advisory, please.

Thanks in advance.
Comment 5 David GEIGER 2023-02-03 06:52:51 CET
Updated packages in core/updates_testing:
========================
qownnotes-23.1.4-1.mga8
qownnotes-translations-23.1.4-1.mga8.noarch.rpm

from SRPMS:
qownnotes-23.1.4-1.mga8.src.rpm
David GEIGER 2023-02-03 06:53:24 CET

Assignee: geiger.david68210 => qa-bugs

Comment 6 Dave Hodgins 2023-02-06 23:15:27 CET
Reviewed the changelogs of all of the versions since 20.8. Noticed that it no longer
allows using the same name with different cases.

Created a note that I renamed to alpha, another one that I renamed to ALPHA.
Installed the update. The ALPHA note disappeared.

An update with such a change is not allowed in a stable release.

CC: (none) => davidwhodgins
Status: NEW => RESOLVED
Resolution: (none) => WONTFIX
Keywords: validated_update => (none)
Whiteboard: MGA8-64-OK => (none)

Comment 7 Morgan Leijström 2023-02-07 09:30:07 CET
Well spotted, and good test!

- And I verify; using old version I created notes with names: note, Note, NOTE.
After update only "note" was listed.

However, the files are still there. Using Nextcloud file browser to rename "Note" and "NOTE" to "Note-2" and "NOTE-3", makes all three show up in QOwnNotes.
 
So, a bad implementation of a fix for a for many users foreign filesystem...


This is an app which is a companion to file syncing using Nextcloud.
As such it may sync on different file systems.

In this light it is a design bug fix
20.12.7: "now storing notes in different cases is also prohibited to prevent more problems on case-insensitive filesystems, like NTFS (for #1988 (opens new window))"



So... maybe backport? (for the many other bugfixes, translations, additions)

- But hold off a while, I will report upstream and ask for a fix.

Status: RESOLVED => REOPENED
Resolution: WONTFIX => (none)

Comment 8 Morgan Leijström 2023-02-07 09:53:23 CET
https://github.com/pbek/QOwnNotes/issues/2727

Keywords: (none) => UPSTREAM
Status comment: (none) => To backport as is, if upstream do not fix

Comment 9 Morgan Leijström 2023-02-07 10:25:18 CET
Upstream is on it

Assignee: qa-bugs => bugsquad

Lewis Smith 2023-05-08 20:23:34 CEST

Status: REOPENED => UPSTREAM

Comment 10 Morgan Leijström 2023-05-08 21:16:26 CEST
Closed upstream, reason: stale.
Comment 11 Marja Van Waes 2024-08-22 23:01:54 CEST
We stopped supporting Mageia 8 almost 8 months ago 
https://blog.mageia.org/en/2023/12/30/mageia-8-end-of-life/

That means we also stopped fixing Mageia 8 bugs and that this bug report needs to be closed, regardless of whether it was fixed for Mageia 8 or not.

If this particular bug did not get fixed for Mageia 8, then we do regret that.

If this issue is still present in Mageia 9 or cauldron, then please reopen this report, write a comment and adjust the "Version:" field.

If you are not yet a member of one or our teams, then please consider becoming one. https://wiki.mageia.org/en/Contributing
Mageia is a community project, meaning that we, the users, make Mageia together.

The more active contributors we have, the more bug reports will get fixed.
Besides, being active in a team can be very rewarding. It was and is certainly rewarding to me :-D

Status: UPSTREAM => RESOLVED
Resolution: (none) => OLD


Note You need to log in before you can comment on or make changes to this bug.