Bug #5143

not getting prompted to upgrade to available patched version in test area

Added by Derik Barseghian almost 12 years ago. Updated almost 12 years ago.

build system
Target version:
Start date:
Due date:
% Done:


Estimated time:


I current have published to the test area reporting-2.0.0, reporting-2.1.0, and reporting-2.1.1. If you're run reporting-2.1.0, you're not prompted on startup to get 2.1.1, like i believe is expected.

Related issues

Blocks Kepler - Bug #5147: Resolve issue with modules.txtResolved08/12/2010

Blocked by Kepler - Bug #5099: Import Dependent Modules for KAR doesn't workResolved07/21/2010


#1 Updated by David Welker almost 12 years ago

I have finally figured out the source of this problem. This bug is intimately related to 5147. Basically, the reason that reporting cannot be patched is because it is the main suite and therefore does not have a ^ reference. I got patching to work only when I made another suite that referenced reporting and put a ^ at the end of it.

While I did get the upgrade to work, I found another curious problem. Namely, the progress indicator fails to show the user the progress in downloading. For relatively large modules like reporting, this is a problem (although in the future I want to optimize patching to make patches much smaller), as the user feels as though the program has frozen.

I am not going to do further work on this bug directly, as I expect the resolution of Bug 5147 to completely resolve this bug and I am opening a separate bug report for the progress indicator. However, I will not close this bug until I verify that the fix to Bug 5147 also fixes this bug.

#2 Updated by David Welker almost 12 years ago

After fixing bug 5147, I have verified that this functionality now works.

#3 Updated by Redmine Admin over 9 years ago

Original Bugzilla ID was 5143

Also available in: Atom PDF