[ISSUE] libblockdev-32bit: MISSING: dmraid-32bit>=1.0.0.rc16.3_5

[ISSUE] libblockdev-32bit: MISSING: dmraid-32bit>=1.0.0.rc16.3_5

[rubin55]

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

New issue by rubin55 on void-packages repository

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

Description:
### System

* xuname:  
  `Void 5.16.7_1 x86_64 AuthenticAMD uptodate rrmFF`
* package:  
  `libblockdev-32bit-2.26_1`

### Expected behavior
For `xbps-install libblockdev-32bit` to work.

### Actual behavior
```shell
# xbps-install libblockdev-32bit
MISSING: dmraid-32bit>=1.0.0.rc16.3_5
Transaction aborted due to unresolved dependencies.
```

### Steps to reproduce the behavior
Try to install the package, observe dependency error.

Re: [ISSUE] [CLOSED] libblockdev-32bit: MISSING: dmraid-32bit>=1.0.0.rc16.3_5

[Chocimier]

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

Closed issue by rubin55 on void-packages repository

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

Description:
### System

* xuname:  
  `Void 5.16.7_1 x86_64 AuthenticAMD uptodate rrmFF`
* package:  
  `libblockdev-32bit-2.26_1`

### Expected behavior
For `xbps-install libblockdev-32bit` to work.

### Actual behavior
```shell
# xbps-install libblockdev-32bit
MISSING: dmraid-32bit>=1.0.0.rc16.3_5
Transaction aborted due to unresolved dependencies.
```

### Steps to reproduce the behavior
Try to install the package, observe dependency error.

Re: libblockdev-32bit: MISSING: dmraid-32bit>=1.0.0.rc16.3_5

[rubin55]

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

New comment by rubin55 on void-packages repository

https://github.com/void-linux/void-packages/issues/35769#issuecomment-1058224136

Comment:
@Chocimier why the close without comment? Is the issue fixed or is the package removed from the repository?

Re: libblockdev-32bit: MISSING: dmraid-32bit>=1.0.0.rc16.3_5

[Chocimier]

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

New comment by Chocimier on void-packages repository

https://github.com/void-linux/void-packages/issues/35769#issuecomment-1058228774

Comment:
They are duplicates, underlying problem is the same. You can list packages in one ticket, as asked by @abenson. Solution won't consist of chasing individual packages anyway.

Re: libblockdev-32bit: MISSING: dmraid-32bit>=1.0.0.rc16.3_5

[rubin55]

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

New comment by rubin55 on void-packages repository

https://github.com/void-linux/void-packages/issues/35769#issuecomment-1058230254

Comment:
Alright, is there a new issue for that already or do I need to create it?

Re: libblockdev-32bit: MISSING: dmraid-32bit>=1.0.0.rc16.3_5

[Chocimier]

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

New comment by Chocimier on void-packages repository

https://github.com/void-linux/void-packages/issues/35769#issuecomment-1058236036

Comment:
Pick one of two left open, depending on which discussion thread you want to continue.

Re: libblockdev-32bit: MISSING: dmraid-32bit>=1.0.0.rc16.3_5

[rubin55]

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

New comment by rubin55 on void-packages repository

https://github.com/void-linux/void-packages/issues/35769#issuecomment-1058248191

Comment:
I created #35948, we can continue discussion there.

Re: libblockdev-32bit: MISSING: dmraid-32bit>=1.0.0.rc16.3_5

[Chocimier]

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

New comment by Chocimier on void-packages repository

https://github.com/void-linux/void-packages/issues/35769#issuecomment-1058250638

Comment:
Spamming us by tagging us on all of those really doesn't help your cause.

Re: libblockdev-32bit: MISSING: dmraid-32bit>=1.0.0.rc16.3_5

[rubin55]

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

New comment by rubin55 on void-packages repository

https://github.com/void-linux/void-packages/issues/35769#issuecomment-1058254432

Comment:
Not intended as spamming, simply good issue hygiene. My thinking is, if someone runs into this and does a google search, they might run into one of those closed issues and in this way they would also be directed to the new issue that collects these together.