fyi during update today

Topic: fyi during update today (Read 346 times) previous topic - next topic

0 Members and 1 Guest are viewing this topic.

fyi during update today

11 May 2023, 01:46:21

error: failed to prepare transaction (could not satisfy dependencies)

:: installing alsa-lib (1.2.9-1) breaks dependency 'alsa-lib=1.2.8' required by lib32-alsa-lib

Re: fyi during update today

Reply #1 – 11 May 2023, 05:11:35

newer version already in gremlins repo, So I think we just wait.

Code: [Select]

$ pacman -Ss alsa-lib

world/alsa-lib 1.2.9-1 [installed: 1.2.8-1]
    An alternative implementation of Linux sound support
lib32/lib32-alsa-lib 1.2.8-1 [installed]
    An alternative implementation of Linux sound support (32 bit)
extra/alsa-lib 1.2.9-1 [installed: 1.2.8-1]
    An alternative implementation of Linux sound support
multilib/lib32-alsa-lib 1.2.9-1 [installed: 1.2.8-1]
    An alternative implementation of Linux sound support (32 bit)
lib32-gremlins/lib32-alsa-lib 1.2.9-1 [installed: 1.2.8-1]
    An alternative implementation of Linux sound support (32 bit)

Re: fyi during update today

Reply #2 – 11 May 2023, 15:28:04

Quote from: suren – on 11 May 2023, 05:11:35

newer version already in gremlins repo, So I think we just wait.

Code: [Select]

$ pacman -Ss alsa-lib

world/alsa-lib 1.2.9-1 [installed: 1.2.8-1]
    An alternative implementation of Linux sound support
lib32/lib32-alsa-lib 1.2.8-1 [installed]
    An alternative implementation of Linux sound support (32 bit)
extra/alsa-lib 1.2.9-1 [installed: 1.2.8-1]
    An alternative implementation of Linux sound support
multilib/lib32-alsa-lib 1.2.9-1 [installed: 1.2.8-1]
    An alternative implementation of Linux sound support (32 bit)
lib32-gremlins/lib32-alsa-lib 1.2.9-1 [installed: 1.2.8-1]
    An alternative implementation of Linux sound support (32 bit)

the purpose of an fyi post is to inform devs of something they may have overlooked. Yall need to stop with the "you need to wait" responses. Waiting has nothing to do with anything. Devs need to know if something is a bit hinky. In any case the update runs this morning so it looks like they addressed it.