Package Details: loot 0.18.6-4

Git Clone URL: https://aur.archlinux.org/loot.git (read-only, click to copy)
Package Base: loot
Description: A load order optimisation tool for the Elder Scrolls (Morrowind and later) and Fallout (3 and later) games.
Upstream URL: https://loot.github.io
Licenses: GPL3
Submitter: gargan
Maintainer: gargan (C0rn3j)
Last Packager: C0rn3j
Votes: 5
Popularity: 0.000065
First Submitted: 2019-10-24 01:46 (UTC)
Last Updated: 2022-11-15 22:50 (UTC)

Latest Comments

1 2 Next › Last »

65a commented on 2022-11-15 03:50 (UTC)

I missed removing that other yarn line, I believe it should be removed as yarn is a web frontend technology, looks like LOOT only uses QT now. We can remove that line and the dep. Thanks for the 18.6 update, just built fine and basic use case works.

C0rn3j commented on 2022-11-07 09:18 (UTC)

65a: Thanks a bunch, removing yarn dep should be wrong as yarn is still used in build() in your patch. I've kept the http-parser remove.

I also bumped it up to 0.18.6.

I unfortunately don't have time to test it properly at the moment, but at least the PKGBUILD isn't completely broken anymore.

65a commented on 2022-11-03 02:31 (UTC)

Here is a patch to update to 18.2, and remove some old hacks. CEF is thankfully dead, it uses QT5 now. I'm not sure the depends are correct, but this builds locally for me applied to a cloned copy of the AUR: https://pastebin.com/qNtyiBe9

Tom_B commented on 2022-03-19 18:06 (UTC)

Currently failing to build:

yarn install v1.22.18
[1/4] Resolving packages...
[2/4] Fetching packages...
error Command failed.
Exit code: 128
Command: git
Arguments: ls-remote --tags --heads git://github.com/loot/babel-gettext-extractor
Directory: /home/tom/.cache/yay/loot/src/loot-0.16.1
Output:
fatal: remote error:
  The unauthenticated git protocol on port 9418 is no longer supported.
Please see https://github.blog/2021-09-01-improving-git-protocol-security-github/ for more information.
info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command.
==> ERROR: A failure occurred in build().
    Aborting...
 -> error making: loot

laxzka commented on 2021-10-17 14:21 (UTC) (edited on 2021-10-17 14:43 (UTC) by laxzka)

loot crashes when used due to an out-of-bounds array access; https://github.com/loot/loot/issues/1615

apparently it's fixed in the 'fix-vector-access' branch of 'libloot', hopefully they'll release a new libloot version soon so that it's easier to switch to. (and thanks for this package, it makes modding skyrim a much easier thing on linux :)

65a commented on 2021-10-10 04:28 (UTC)

Haven't gotten a chance to do that. For this PKGBUILD, I found another issue that might affect others. I had one machine with rustup installed, but no default toolchain set in rustup. This will cause the build to fail, but the error message is not obvious. If anyone encounters this, run 'rustup toolchain default'. It's probably possible to check for this status in the prepare stage and return a more useful error.

C0rn3j commented on 2021-06-15 13:08 (UTC)

@65a You should try replicating it against current git - https://github.com/loot/loot/pull/1162#issuecomment-545120145 - and if it is still an issue there, report it upstream, I don't understand the issue enough to fix it either.

I've updated the package to 0.16.1/0.16.3 loot/libloot (from May), hopefully nailing the new .pak packaging, and added your hack to keep it building for now.

65a commented on 2021-06-15 00:30 (UTC)

I was having issues building this. It appears to be an upstream problem with CMakeLists.txt, but I added the following hack to the PKGBUILD to brute force it. tl;dr "--config $(CONFIGURATION)" is set everywhere, but I don't think we usually have these outside of visual studio/multi-compiler land, IIUC.

Put this in the first line of build() to replicate. find ./ -type f -exec sed -i 's#--config $(CONFIGURATION)##g' {} \;

I'm unsure of the correct upstream fix, this seems like it's probably necessary on Windows...can we just set CONFIGURATION to default or something if Linux?

orlfman commented on 2021-05-05 19:37 (UTC) (edited on 2021-05-05 19:53 (UTC) by orlfman)

huh manual building worked just fine. wonder why its failing with paru. that's weird.

got another noob question, how can i get it to see my skyrim special edition? it doesn't detect it. i have it installed via steam.

edit: nvm i got it to work. had to edit ~/.config/LOOT/settings.toml and add:

local_path = "/mnt/storage0/SteamLibrary/steamapps/compatdata/489830/pfx/drive_c/users/steamuser/Local Settings/Application Data/Skyrim Special Edition"

path = "/mnt/storage0/SteamLibrary/steamapps/common/Skyrim Special Edition"

to the skyrim se column

C0rn3j commented on 2021-05-05 08:04 (UTC)

Try building the package manually, not with an AUR helper

1 2 Next › Last »