Package Base Details: lib32-gstreamer0.10-ugly

Git Clone URL: https://aur.archlinux.org/lib32-gstreamer0.10-ugly.git (read-only, click to copy)
Keywords:
Submitter: None
Maintainer: None
Last Packager: GordonGR
Votes: 11
Popularity: 0.000006
First Submitted: 2010-02-26 00:18 (UTC)
Last Updated: 2015-12-20 14:27 (UTC)

Latest Comments

1 2 3 Next › Last »

MarsSeed commented on 2023-06-03 08:36 (UTC)

Arch has dropped the 64-bit libsidplay from repos and from depends of gst-plugins-ugly. This package should follow that change and remove depends lib32-libsidplay, otherwise it cannot be built in clean environment.

In general I believe 32-bit libraries to play Commodore 64 music files are not needed anymore. Commodore emulators can be built in 32 or 64 bit and they play Commodore music on their own without GStreamer. So this dependency would be good to remove even if libsidplay becomes available again in Arch or AUR repo.

ector commented on 2017-01-31 09:38 (UTC)

I installed the package without problems thank you

nagar commented on 2017-01-28 04:51 (UTC)

Confirm Compiler error :) ==> ERROR: A failure occurred in build(). Aborting...

nagar commented on 2017-01-28 04:51 (UTC) (edited on 2017-01-28 04:51 (UTC) by nagar)

Confirm Compiler error :) ==> ERROR: A failure occurred in build(). Aborting...

Enverex commented on 2016-08-16 15:03 (UTC)

As there is no lib32-twolame, can you add --disable-twolame to the configure stage? That way it'll stop people running into the issue they're currently seeing due to it seeing the 64bit lib and trying to link to that.

Roken commented on 2015-12-14 21:01 (UTC)

Well, it's not the end of the world. Packer to get the builds, then a manual pacman -U to install works. I'm sure it will work with other AUR helpers.

GordonGR commented on 2015-12-14 14:51 (UTC)

FadeMind: Thank you. Rroken: Ah, now I understand. Yaourt does (or did, when I last used it) something similar: It would note that two packages must be updated. It would build one (so the other as well), install them both; then, for the second package, do the same thing all over again. These are bugs in the AUR helpers, I'm afraid. There is nothing to be done on our end and, of course, they are no reason to stop providing split packages. Lately I have been using cower. It only checks what packages need updating and downloads the source code for them (with -uud). Then it lets me compile them and build them myself.

FadeMind commented on 2015-12-14 12:14 (UTC)

--disable-twolame works here too. Regards

Roken commented on 2015-12-13 15:30 (UTC)

Using an AUR helper (packer in my case) gives a "duplicate target" error of the build when it tries to install. I'm pretty sure that this is an error that is coming from pacman, though I'm less sure whether it's directly related to the two packages being built, or both packages being built in conjunction with a separate plugins package being available, effectively duplicating the plugins. Unfortunately, I don't know enough about how pacman works behind the scenes to speculate.

GordonGR commented on 2015-12-13 11:34 (UTC)

Roken, thanks for reply, I will add it to the PKGBUILD. I'm sorry though, I don't understand what you mean by "duplicate target". The idea behind split packages is that the code is compiled once and produces two packages at the same time. Then you can install one or both (but obviously foo-plugins depends on foo). [extra] does it the same way, yes, and I think it's reasonable. How would you prefer it?

1 2 3 Next › Last »