Bug 17267 - MageiaSync doesn't sync if local directory is empty
Summary: MageiaSync doesn't sync if local directory is empty
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 5
Hardware: All Linux
Priority: Normal normal
Target Milestone: ---
Assignee: QA Team
QA Contact:
URL:
Whiteboard: MGA5-32-OK MGA5-64-OK advisory
Keywords: validated_update
Depends on:
Blocks:
 
Reported: 2015-12-01 18:49 CET by Thomas Andrews
Modified: 2015-12-09 11:53 CET (History)
4 users (show)

See Also:
Source RPM: python-mageiasync 0.1.5-1.mga5
CVE:
Status comment:


Attachments

Description Thomas Andrews 2015-12-01 18:49:12 CET
Description of problem:

If the directory selected from the Remote pane does not already exist in the Local directory, MageiaSync will not create it when the "Do Sync" button is pressed. Instead, the error message "no entry selected" appears in the Report pane. 

If, however, Remote directories are selected and one clicks on "Check" from the "Sync" menu, the directories that were selected appear in the Local pane and syncing will proceed as expected.

This may be expected behavior, but if it is it isn't explained as such on the wiki page: https://wiki.mageia.org/en/ISO_testing_rsync_tools

In addition, there is no documentation that I can find on what exactly the "Check" button is for, and how to use it. So if all I have done is stumble upon the proper procedure, the wiki should be edited to avoid confusing new users.


Reproducible: 

Steps to Reproduce:
Rémi Verschelde 2015-12-01 18:51:04 CET

CC: (none) => geiger.david68210, qa-bugs
Assignee: bugsquad => yves.brungard_mageia

Comment 1 papoteur 2015-12-01 21:43:51 CET
Hello Thomas,
Thanks for reporting.
I have seen this bug and corrected it in release 0.1.7, already in cauldron.
We have to port it also in Mageia 5.
I will have also a look in wiki.
papoteur 2015-12-01 21:44:34 CET

Assignee: yves.brungard_mageia => geiger.david68210

Comment 2 David GEIGER 2015-12-04 08:38:48 CET
now fixed for mga5 too with python-mageisync-0.1.7 in Core/Updates_testing repo.
Comment 3 Thomas Andrews 2015-12-04 16:48:06 CET
Seems to be working OK on both i586 and x86-64 systems. Adding both to the Whiteboard...

Whiteboard: (none) => MGA5-32-OK MGA5-64-OK

Comment 4 David GEIGER 2015-12-06 08:42:43 CET
papoteur can you provide an advisory for this update, please? 

Thanks in advance!
Comment 5 papoteur 2015-12-08 14:36:15 CET
Advisory:
========================

Before the update:
If the directory selected from the Remote pane does not already exist in the Local directory, MageiaSync will not create it in said panel when the "Do Sync" button is pressed.
After this update:
An entry is created for non existing local image when syncing it.

========================

Packages in 5/core/updates_testing:
python-mageisync-0.1.7-1.mga5.noarch.rpm

========================

CC: (none) => yves.brungard_mageia

Comment 6 David GEIGER 2015-12-09 06:42:13 CET
Assigning to QA,


Advisory:
========================

Before the update:
If the directory selected from the Remote pane does not already exist in the Local directory, MageiaSync will not create it in said panel when the "Do Sync" button is pressed.
After this update:
An entry is created for non existing local image when syncing it.
Also mageiasync is now switched to python 3.

========================

Packages in 5/core/updates_testing:
python-mageiasync-0.1.7-1.mga5.noarch.rpm

========================

Source RPM: 
========================
python-mageiasync-0.1.7-1.mga5.src.rpm

Assignee: geiger.david68210 => qa-bugs

Comment 7 Rémi Verschelde 2015-12-09 08:26:42 CET
Validating, advisory uploaded.

Keywords: (none) => validated_update
Whiteboard: MGA5-32-OK MGA5-64-OK => MGA5-32-OK MGA5-64-OK advisory
CC: (none) => sysadmin-bugs

Comment 8 Mageia Robot 2015-12-09 11:53:40 CET
An update for this issue has been pushed to Mageia Updates repository.

http://advisories.mageia.org/MGAA-2015-0203.html

Status: NEW => RESOLVED
Resolution: (none) => FIXED


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