EMULAB Forum

Please login or register.

Login with username, password and session length
Advanced search  

News:

The new forum is online, hope you enjoy it!

Pages: [1]   Go Down

Author Topic: Impropper Handling of "wrong merged" Moves  (Read 1929 times)

Kolano

  • Member
  • *
  • Karma: 0
  • Offline Offline
  • Posts: 8
  • Operating System:
  • Windows NT 10.0 Windows NT 10.0
  • Browser:
  • Firefox 137.0 Firefox 137.0
    • View Profile
Impropper Handling of "wrong merged" Moves
« on: 01 April 2025, 06:13 »

The file handling options for errors such as...
"XXX [folder: YYY - parent: ZZZ - size: VVVkb]
wrong merged ROM set: UUU (merge to: ZZZ)"
...are inappropriate. The base file ZZZ is moved rather than the problematic one YYY.

I'd likely need to deal with this less often if more appropriate support of 7z file updates were provided.

« Last Edit: 01 April 2025, 06:13 by Kolano »
Logged


Roman

  • Global Moderator
  • Member
  • ***
  • Karma: 120
  • Offline Offline
  • Posts: 3523
  • Operating System:
  • Windows NT 10.0 Windows NT 10.0
  • Browser:
  • Chrome 134.0.0.0 Chrome 134.0.0.0
    • View Profile
Re: Impropper Handling of "wrong merged" Moves
« Reply #1 on: 01 April 2025, 11:23 »

??? What do you mean in detail?

If you get a "wrong merged ROM set" message it means that you use full merged sets and have a clone set somewhere which shouldn't be there since in full merge mode, all clone files need to be placed in the parent set and the clone set itself doesn't exist. The parent set isn't moved.

Maybe you need to give a detailed example....and actually I don't understand your 7z file updates comment...
Logged
Pages: [1]   Go Up
 

Page created in 0.071 seconds with 19 queries.