Opened 4 years ago
Closed 4 years ago
#60598 closed defect (fixed)
mypaint-brushes @1.3.0_0 and mypaint-brushes1 @1.3.1_0 in conflict over blend+paint.myb
| Reported by: | JDLH (Jim DeLaHunt) | Owned by: | ryandesign (Ryan Carsten Schmidt) |
|---|---|---|---|
| Priority: | Normal | Milestone: | |
| Component: | ports | Version: | 2.6.2 |
| Keywords: | Cc: | dbevans (David B. Evans) | |
| Port: | mypaint-brushes mypaint-brushes1 |
Description (last modified by JDLH (Jim DeLaHunt))
Each of the ports mypaint-brushes @1.3.0_0 and mypaint-brushes1 @1.3.1_0 refuses to activate when the other port is activated, because each activation gives an error that the other port is using /opt/local/share/mypaint-data/1.0/brushes/classic/blend+paint.myb .
The console output looks like:
% sudo port activate mypaint-brushes1 ---> Activating mypaint-brushes1 @1.3.1_0 Error: Failed to activate mypaint-brushes1: Image error: /opt/local/share/mypaint-data/1.0/brushes/classic/blend+paint.myb is being used by the active mypaint-brushes port. Please deactivate this port first, or use 'port -f activate mypaint-brushes1' to force the activation. Error: See /opt/local/var/macports/logs/_opt_local_var_macports_registry_portfiles_mypaint-brushes1-1.3.1_0_6ccfb0d1651ddeb0f6ad018d06e24276c433cb0b16e8d0e0074e05c7159634d2-1353/mypaint-brushes1/main.log for details. Warning: Failed to execute portfile from registry for mypaint-brushes1 @1.3.1_0 ---> Activating mypaint-brushes1 @1.3.1_0 Error: port activate failed: Image error: /opt/local/share/mypaint-data/1.0/brushes/classic/blend+paint.myb is being used by the active mypaint-brushes port. Please deactivate this port first, or use 'port -f activate mypaint-brushes1' to force the activation.
I'm attaching a log file from each activation attempt.
Attachments (2)
Change History (7)
Changed 4 years ago by JDLH (Jim DeLaHunt)
comment:1 Changed 4 years ago by ryandesign (Ryan Carsten Schmidt)
| Cc: | dbevans added; ryandesign removed |
|---|---|
| Owner: | changed from devans@… to ryandesign |
| Status: | assigned → accepted |
True... Please either uninstall or upgrade mypaint-brushes first. I'll add a fix for that.
Changed 4 years ago by JDLH (Jim DeLaHunt)
| Attachment: | main.2.log added |
|---|
/opt/local/var/macports/logs/_opt_local_var_macports_registry_portfiles_mypaint-brushes1-1.3.1_0_6ccfb0d1651ddeb0f6ad018d06e24276c433cb0b16e8d0e0074e05c7159634d2-1353/mypaint-brushes1/main.log is the log of trying to activate mypaint-brushes1 @1.3.1_0 while mypaint-brushes @1.3.0_0 is active
comment:2 Changed 4 years ago by JDLH (Jim DeLaHunt)
| Description: | modified (diff) |
|---|
comment:3 Changed 4 years ago by JDLH (Jim DeLaHunt)
Thank you, Ryan.
Was this in part a weird timing issue? I did a port outdated outdated about 30 minutes ago, and it did not include port mypaint-brushes as outdated. Now, I do a port upgrade on mypaint-brushes and it upgrades. Interesting.
comment:4 Changed 4 years ago by ryandesign (Ryan Carsten Schmidt)
Running sudo port upgrade outdated would run into the problem. Running sudo port upgrade mypaint-brushes first would avoid the problem. I hadn't considered that when I committed the updates yesterday. I'll add a fix for it shortly.
comment:5 Changed 4 years ago by ryandesign (Ryan Carsten Schmidt)
| Resolution: | → fixed |
|---|---|
| Status: | accepted → closed |
/opt/local/var/macports/logs/_opt_local_var_macports_registry_portfiles_mypaint-brushes-1.3.0_0_093f8933295b6195c9962793601d4b2100d2495f594ab36bb404fe6af1b230f7-1134/mypaint-brushes/main.log is the log of trying to activate mypaint-brushes @1.3.0_0 when mypaint-brushes1 @1.3.1_0 is active.