[ISSUE] go-ipfs: recent addition of vsv breaks upgradeability

[ISSUE] go-ipfs: recent addition of vsv breaks upgradeability

[nonchip]

[-- Attachment #1: Type: text/plain, Size: 1142 bytes --]

New issue by nonchip on void-packages repository

https://github.com/void-linux/void-packages/issues/28135

Description:
i already had a `ipfs` service before https://github.com/void-linux/void-packages/commit/65826688d9da8e9cb3c3f47c3c1862f46b327ae9, when trying to `xbps-install -Su` now it fails with:
```
go-ipfs-0.5.0_1: updating to 0.7.0_2 ...
go-ipfs-0.7.0_2: unpacking ...
ERROR: go-ipfs-0.7.0_2: [unpack] failed to extract file `./etc/sv/ipfs/supervise': Directory not empty
ERROR: go-ipfs-0.7.0_2: [unpack] failed to extract files: Directory not empty
ERROR: go-ipfs-0.7.0_2: [unpack] failed to unpack files from archive: Directory not empty
Transaction failed! see above for errors.
```

so 2 problems i have now:
* as far as I understand it, the `supervise` directory shouldn't be written (or at least not fail the update when it's non-empty) anyway, because it's non-empty for *any* running service, and breaking a system upgrade because services are running sounds like a rather bad idea
* how would one migrate an already existing service+systemuser to the new ones introduced without any documentation whatsoever?

Re: go-ipfs: addition of vsv breaks upgradeability

[nonchip]

[-- Attachment #1: Type: text/plain, Size: 638 bytes --]

New comment by nonchip on void-packages repository

https://github.com/void-linux/void-packages/issues/28135#issuecomment-766314428

Comment:
after maldrige "informed" me that (contrary to EVERYTHING the handbook says btw) my problem 1 was caused by me being so silly and using `/etc/sv` for it's allegedly intended purpose, combined with the fact that this change was, again, undocumented, i managed to temporarily move my old service out of the way and port everything using a horrible bunch of `mv`s and `chowns`.

next time PLEASE figure out what `INSTALL` files are for before introducing such a change in a mere package revision.

Re: [ISSUE] [CLOSED] go-ipfs: addition of vsv breaks upgradeability

[nonchip]

[-- Attachment #1: Type: text/plain, Size: 1063 bytes --]

Closed issue by nonchip on void-packages repository

https://github.com/void-linux/void-packages/issues/28135

Description:
i already had a `ipfs` service before https://github.com/void-linux/void-packages/commit/65826688d9da8e9cb3c3f47c3c1862f46b327ae9, when trying to `xbps-install -Su` now it fails with:
```
go-ipfs-0.5.0_1: updating to 0.7.0_2 ...
go-ipfs-0.7.0_2: unpacking ...
ERROR: go-ipfs-0.7.0_2: [unpack] failed to extract file `./etc/sv/ipfs/supervise': Directory not empty
ERROR: go-ipfs-0.7.0_2: [unpack] failed to extract files: Directory not empty
ERROR: go-ipfs-0.7.0_2: [unpack] failed to unpack files from archive: Directory not empty
Transaction failed! see above for errors.
```

so 2 problems i have now:
* as far as I understand it, the `supervise` directory shouldn't fail the update when it's non-empty (guess that's related to it not having been a symlink before), which brings me to question 2:
* how would one migrate an already existing service+systemuser to the new ones introduced without any documentation whatsoever?

Re: go-ipfs: addition of vsv breaks upgradeability

[nonchip]

[-- Attachment #1: Type: text/plain, Size: 681 bytes --]

New comment by nonchip on void-packages repository

https://github.com/void-linux/void-packages/issues/28135#issuecomment-766314428

Comment:
after maldrige "informed" me that (contrary to EVERYTHING the handbook says btw) my problem 1 was caused by me being so silly and using `/etc/sv` for it's allegedly intended purpose, combined with the fact that this change was, again, undocumented, i managed to temporarily move my old service out of the way and solve problem 2 by porting everything over to the new user using a horrible bunch of `mv`s and `chowns`.

next time PLEASE figure out what `INSTALL` files are for before introducing such a change in a mere package revision.