Unsolved
This post is more than 5 years old
1 Rookie
•
32 Posts
0
9318
January 5th, 2012 14:00
Repository Manager behaviour questions
After using Rep Manager for a bit, I have two questions:
- If I make any changes to a local repository (i.e. adding bundles) and I try to exit, it warns me that I have an unsaved repository. When I click save, it behaves like Save As... That is, I have to choose a file name and location. If I point to the existing repository file (xml), the save errors out. I have to choose a new file name each time. Is this normal?
- Sometimes when I export bundles to an SUU, Rep Man warns me that some bundle components are out of date and will be skipped during export. If I go into the repository update screens and do a compare, I can see the newer files at Dell's FTP site. If I choose to include the updated components, Dell warns me that modifying a bundle "requires testing". I just want to deploy the Dell bundle intact....is there anyway to do this?
Thanks for any feedback.
No Events found!
Peter Tsai
2 Intern
•
272 Posts
0
January 9th, 2012 13:00
Hi jmbartlett,
Thanks for posting in the forum. First, I want to ask what version of Repository Manager you are using. I'm answering your questions based on version 1.4.104, which was available for download starting in Dec 2011
en.community.dell.com/.../repository-manager-1-4-released-and-ready-for-download.aspx
1. Using 1.4.104, I was just now able to load an existing repository, make a change, then save over the original XML successfully before exiting.
2. Our catalog files are updated once a week so sometimes updates are live on the website before the catalog gets updated. I think what you are seeing is a result of this. I'm not sure of a way to download the older version of the file instead skipping it. Let me try to find someone else with deeper product knowledge to answer this question.
Jim Bartlett
1 Rookie
•
32 Posts
0
July 16th, 2012 16:00
Just to close off this topic.
Issue #1 has disappeared with an update to Repository Manager 1.4.113. I can now just click "Save" and it works.
Issue #2 turns out to be what I would consider an "interface / usability" problem. If I use the "Update" feature to download components, although I receive the latest component files, I lose the version information with regards to the bundle. You have to delete the old bundle from the local catalog, select the new one at Dell and then save. Rep Man will only download the new components but then bring the new bundle version number with it. This avoids the "untested" status of the updated bundles.
Thanks.