Opened 14 months ago

Last modified 4 weeks ago

#15068 new bug

[packagefs] Cannot handle package activations with identical names

Reported by: waddlesplash Owned by: bonefish
Priority: normal Milestone: R1/beta3
Component: File Systems/packagefs Version: R1/Development
Keywords: Cc:
Blocked By: Blocking: #13574, #15207, #15576
Platform: All


If you try to update or activate a package with an identical name (including revision) to an installed package, this occurs:

[system] Applying changes ...
*** failed to commit transaction: Failed to change the package activation in packagefs: Name in use

That's because of this code in packagefs.

Probably solving the TODO about looking packages up by node_ref rather than name would fix this.

Change History (13)

comment:1 by waddlesplash, 14 months ago

Blocking: 13574 added

comment:2 by waddlesplash, 11 months ago

Blocking: 15207 added

comment:3 by diver, 7 months ago

Blocking: 15576 added

comment:4 by diver, 8 weeks ago

Milestone: UnscheduledR1/beta2

Would be nice to fix before beta2 as it might prevent system updates.

comment:5 by pulkomandy, 7 weeks ago

System updates always come with a different version or revision number so they are not affected. Only trying to reinstall an already installed package will fail.

comment:6 by diver, 7 weeks ago

Still this is somehow happens: after a fresh install pkgman tries to update a selection of packages with the ones with the same name.

comment:7 by waddlesplash, 6 weeks ago

IIRC it was hard to get this problem to reproduce in the past; so are you saying this always reproduces under a beta2 image?

comment:8 by diver, 6 weeks ago

I haven't tried beta2 images yet but I could reproduce it easily using nightlies after a fresh install.

comment:9 by waddlesplash, 6 weeks ago

OK, then we should at least investigate why this occurs and fix that bug. It is indeed extremely odd.

comment:10 by Forza, 5 weeks ago


This problem happens with the beta2 release-candidate too ( Currently, every time I make a clean install and run the sw updater.

comment:11 by waddlesplash, 4 weeks ago

Can you please run "pkgman full-sync" in a Terminal, and paste the output of what it says it is going to do here?

comment:12 by waddlesplash, 4 weeks ago

Milestone: R1/beta2

Ticket retargeted after milestone closed

comment:13 by waddlesplash, 4 weeks ago

Milestone: R1/beta3
Note: See TracTickets for help on using tickets.