Version: (using KDE KDE 3.5.8) Installed from: Ubuntu Packages Compiler: gcc version 4.1.3 20070929 (prerelease) (Ubuntu 4.1.2-16ubuntu2) OS: Linux Actions to reproduce: 1. Tag a folder. 2. Deleted some files I didn't want in the tag. 3. Tag the folder again, placing a hook for "force tag creation, even if tag already exists". 4. Make more changes. 5. Tag again, REMOVING the hook (because I wanted to see the error message (never trust software!). 6. The tag went through without any error message or warning. (I checked if I had a typo in the tag, but it was not the case: only one tag exists for the folder, the one I was overwriting).
Thanks for the report. I can't confirm the bug. In my test I got the error message: "TEST_151178 already exists on version 1.1 : NOT MOVING tag to version 1.2" in the protocol view. Please verify with the "Browse Log" function that the Tag was really moved to the new revision. Thank you, Christian
Dear Bug Submitter, This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond. Thank you for helping us make KDE software even better for everyone!
Dear Bug Submitter, This is a reminder that this bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? Thank you for helping us make KDE software even better for everyone!
I stopped using KDE years ago, sorry. can't confirm.
Thank you for reporting this issue in KDE software. As it was reported on an older version, can we please ask you to see if you cazn reproduce the issue with a more recent software version? If you can confirm this issue still exists in a recent version, please change the version field and the status to "REPORTED" when replying. Thank you!
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!