On 8 December 2013 19:17, member graysky <gray...@archlinux.us> wrote: > On Sat, Dec 7, 2013 at 9:27 PM, Felix Yan <felixonm...@gmail.com> wrote: >> >> Just had a look, but now 'mprime' also has comments for itself. So I'd >> suggest to merge mprime-bin (with its votes/comments) to mprime, then you >> just re-upload the mprime-bin package. Please let me know if this is ok so I >> proceed, or maybe a better approach? :D >> > > Hi Felix. If you do that, and I then reup mprime-bin, won't that mean > all the votes will be with the mprime package? That is not a > reflection of reality. The votes/comments should stay with the > mprime-bin package. What do you think?
Your mistake was to update the mprime package before requesting a merge. You were probably not aware of the merge functionality that TUs have access to. The merge is one way -- meaning, you can't copy and retain data for reuse more than once. Now, your original package has new comments that are only relevant since the update. Your mprime-bin is a loner at this point. Barring intervention from an AUR developer, you have to sacrifice data of either one of the packages. For -bin: 1. Backup mprime 2. Merge mprime into mprime-bin 3. Delete non-relevant comments from mprime-bin 4. Reupload mprime from backup This should work to retain mprime-bin's data, but I'm not intricately familiar with the process. Unfortunately, you can't remove non-relevant votes (but you can tell others to remove theirs).