Dep issues in manager show description rather than expansion, then fail to show at second attempt.

[OoMrFlibble]

See second line. The description for the errant expansion is shown, rather than the name.

Using oolite_test-1.93.1-67-x86_64.AppImage

Close Oolite and retry, the updates show but "Update installed expansion packs" fails silently:

This is what I see from Latest.log after hitting Update:

11:29:23.793 [version.debug]: oolite.oxp.z.phkb.XenonUI mv:3.13 mav:3.14
11:29:23.796 [version.debug]: oolite.oxp.Murgh.HoOpyCasino mv:2.3 mav:2.3.3
11:29:23.799 [version.debug]: oolite.oxp.phkb.MaintenanceTuneUp mv:0.6 mav:0.7
11:29:23.800 [version.debug]: oolite.oxp.spara.market_observer mv:3.7 mav:2.3.2
11:29:23.802 [version.debug]: oolite.oxp.phkb.NavigationBeaconsMFD mv:1.1 mav:1.2
11:29:23.804 [version.debug]: oolite.oxp.cim.new-cargoes mv:2.1 mav:2.2
11:29:23.806 [version.debug]: oolite.oxp.phkb.ExpandedWeaponInfo mv:1.1 mav:1.2
11:29:23.806 [version.debug]: oolite.oxp.Svengali.Library mv:1.8.5 mav:1.9.1
11:29:23.806 [version.debug]: oolite.oxp.phkb.LoadoutByCategory mv:1.10 mav:1.12
11:29:23.815 [version.debug]: oolite.oxp.Thargoid.Planetfall mv:2.30 mav:2.32
11:29:23.821 [version.debug]: oolite.oxp.z.phkb.XenonUI mv:3.13 mav:3.14
11:29:23.822 [version.debug]: oolite.oxp.Murgh.HoOpyCasino mv:2.3 mav:2.3.3
11:29:23.824 [version.debug]: oolite.oxp.phkb.MaintenanceTuneUp mv:0.6 mav:0.7
11:29:23.824 [version.debug]: oolite.oxp.spara.market_observer mv:3.7 mav:2.3.2
11:29:23.827 [version.debug]: oolite.oxp.phkb.NavigationBeaconsMFD mv:1.1 mav:1.2
11:29:23.830 [version.debug]: oolite.oxp.cim.new-cargoes mv:2.1 mav:2.2
11:29:23.832 [version.debug]: oolite.oxp.phkb.ExpandedWeaponInfo mv:1.1 mav:1.2
11:29:23.833 [version.debug]: oolite.oxp.Svengali.Library mv:1.8.5 mav:1.9.1
11:29:23.833 [version.debug]: oolite.oxp.phkb.LoadoutByCategory mv:1.10 mav:1.12
11:29:23.841 [version.debug]: oolite.oxp.Thargoid.Planetfall mv:2.30 mav:2.32
11:29:23.842 [version.debug]: oolite.oxp.z.phkb.XenonUI mv:3.13 mav:3.14
11:29:23.843 [version.debug]: oolite.oxp.Murgh.HoOpyCasino mv:2.3 mav:2.3.3
11:29:23.843 [version.debug]: oolite.oxp.phkb.MaintenanceTuneUp mv:0.6 mav:0.7
11:29:23.843 [version.debug]: oolite.oxp.phkb.NavigationBeaconsMFD mv:1.1 mav:1.2
11:29:23.844 [version.debug]: oolite.oxp.cim.new-cargoes mv:2.1 mav:2.2
11:29:23.844 [version.debug]: oolite.oxp.phkb.ExpandedWeaponInfo mv:1.1 mav:1.2
11:29:23.846 [version.debug]: oolite.oxp.Svengali.Library mv:1.8.5 mav:1.9.1
11:29:23.846 [version.debug]: oolite.oxp.phkb.LoadoutByCategory mv:1.10 mav:1.12
11:29:23.847 [version.debug]: oolite.oxp.Thargoid.Planetfall mv:2.30 mav:2.32

But The fails silently. Over and over. The error does not show again, and the user has no clue.

Attempting to manually update an affected package causes the conflict from the first attempt to show again.

For this case, updating "Loadout by category" manually unblocked it and the rest ran normally.

It occurs to me that a missing dep should be checked for in the current update list, and moved to top of install queue. In this case, user interaction would have been avoided.

[oocube]

Any chance to know what OoliteStarter says on the state of your expansions?

[OoMrFlibble]

Not at this point. As my OP suggests, I successfully updated by filtering on upgradeable, attempting to upgrade one item to re-invoke the error message, then guessing from the description that loadout_by_category needed to be installed to satisfy another upgrades' dep. I'll test with starter next time I get the issue.

…

On 25 May 2026 20:50:11 BST, oocube ***@***.***> wrote: oocube left a comment (OoliteProject/oolite#655) Any chance to know what OoliteStarter says on the state of your expansions? -- Reply to this email directly or view it on GitHub: #655 (comment) You are receiving this because you authored the thread. Message ID: ***@***.***>

[phkb]

What's particularly confusing is that I'm not aware of any mod that requires "Loadout By Category". None of the mods in your list do.

[OoMrFlibble]

Might be my bad.. Does Loadout By Category have any deps? Library perhaps? I may have instinctively updated that first. Not an easy one to rewind.

Will pay more attention next time. Am intentionally leaving updates for a while to hopefully trigger similar. It's happened a few times before.

[phkb]

For reference, Loadout By Category doesn't have any dependencies.

[oocube]

phkb is right. Here is the catalog entry:

https://ooliteproject.github.io/oolite-expansion-catalog/expansions/oolite.oxp.phkb.LoadoutByCategory.html

[OoMrFlibble]

I have no reason to invent this. Will give it a few days and hope for a similar clash to give us something to dissect in a more scientific way.

[phkb]

Definitely not claiming you're inventing anything. It clearly happened. Just making a note for whoever looks at the error that it might be more complicated than simple dependency links.

[OoMrFlibble]

Acknowledged. And thank you. Standing by for next event.

[oocube]

I'm wondering whether we have to wait for a reoccurrence or we could invent a test scenario for the expansion manager. It is just about OXP updates and dependencies, right?

[phkb]

I've tried putting old copies of OXP's into the ManagedAddOns and then initiating the update process. It's gone through flawlessly so far. I'll try again with the same list MrFlibble gave.

[phkb]

I've narrowed down the issue. There seems to be a problem with updating Loadout by Category. Working on it now.

[phkb]

I think I've found the issue. I'd ended up giving both the 1.90 and 1.91 versions of Loadout By Category the same identifier. I'm just updating the catalog now, and will confirm everything is working ok shortly.

[phkb]

My tests have confirmed everything is working OK now. All updates went through without a hitch, including Loadout By Category.
I'd be happy to close this one off after MrFlibble has a chance to respond.

[OoMrFlibble]

Great work phkb. I'm sure I've seen similar before. Will re-open if I catch another.