Opened 6 years ago

Closed 3 years ago

#10914 closed bug (fixed)

Repeatedly adding a package causes activation/deactivation

Reported by: luroh Owned by: bonefish
Priority: normal Milestone: R1
Component: Kits/Package Kit Version: R1/Development
Keywords: Cc: brendan.brewster@…
Blocked By: Blocking:
Platform: All

Description (last modified by luroh)

hrev47327, gcc2.

  1. Run the 'install-wifi-firmwares' script, it will put a wifi_firmwares-1-any.hpkg into system/packages/
  2. Open a Tracker window to monitor the contents of the system/data/firmware folder
  3. Repeatedly create and move a copy of wifi_firmwares-1-any.hpkg into system/packages/
  4. Observe in the Tracker window how the package gets either mounted or unmounted every time the package is added

Running the 'install-wifi-firmwares' script several times will display the same symptom, of course. Also, my test case in #7000 might possibly be related.

Change History (7)

comment:1 by diver, 6 years ago

Ah, yes, this one is very annoying. Have to copy/symlink files twice, see description in #10872.

comment:2 by bonefish, 6 years ago

I don't understand the problem. You replace a package file in system/packages with a new file. I would expect that the old package gets deactivated and the new one activated. The description reads like that is exactly what happens.

in reply to:  2 comment:3 by luroh, 6 years ago

Description: modified (diff)

Replying to bonefish:

I would expect that the old package gets deactivated and the new one activated.

Exactly, but this doesn't happen. Only every other package you replace causes activation or deactivation of the package in question. Item 4. in the description amended.

comment:4 by luroh, 6 years ago

Description: modified (diff)

Item 4. reworded some more.

comment:5 by taos, 6 years ago

Some of my issues in #10464 seem related to this.

comment:6 by br3wski3, 6 years ago

Cc: brendan.brewster@… added

comment:7 by luroh, 3 years ago

Resolution: fixed
Status: newclosed

Confirmed fixed in hrev51233.

Note: See TracTickets for help on using tickets.