Arch Linux User Repository

i should note that 1.3 doesn't seem to build, though- though it seems to be upstream issue:

/tmp/doomseeker/src/doomseeker/src/core/version.cpp: In static member function ‘static QString Version::changeset()’:
/tmp/doomseeker/src/doomseeker/src/core/version.cpp:30:9: error: ‘HG_REVISION_HASH_STRING’ was not declared in this scope
   30 |  return HG_REVISION_HASH_STRING;
      |         ^~~~~~~~~~~~~~~~~~~~~~~
/tmp/doomseeker/src/doomseeker/src/core/version.cpp: In static member function ‘static QString Version::revision()’:
/tmp/doomseeker/src/doomseeker/src/core/version.cpp:58:9: error: ‘HG_TIME’ was not declared in this scope; did you mean ‘LC_TIME’?
   58 |  return HG_TIME;
      |         ^~~~~~~
      |         LC_TIME
/tmp/doomseeker/src/doomseeker/src/core/version.cpp: In static member function ‘static long long unsigned int Version::revisionNumber()’:
/tmp/doomseeker/src/doomseeker/src/core/version.cpp:63:9: error: ‘HG_REVISION_NUMBER’ was not declared in this scope
   63 |  return HG_REVISION_NUMBER;
      |         ^~~~~~~~~~~~~~~~~~
make[2]: *** [src/core/CMakeFiles/doomseeker.dir/build.make:3357: src/core/CMakeFiles/doomseeker.dir/version.cpp.o] Error 1
make[1]: *** [CMakeFiles/Makefile2:343: src/core/CMakeFiles/doomseeker.dir/all] Error 2
make: *** [Makefile:152: all] Error 2
==> ERROR: A failure occurred in build().
    Aborting...

Ok, I'll consider making the switch tomorrow, since you took the time ^-^

here's an ideal and still simple package

• uses proper release versions with no dependency on any specific VCS version (since it uses snapshots)
• gets rid of epoch (because you don't really need it; you can just modify pkgrel with this version)
• all you need to do is change the pkgver variable for new releases, unless the actual build process drastically changes.

(edit: AUR comments do not like source blocks)

The git repository is now up and running. Bitbucket will drop in no time the Mercurial support, so indeed these days this package has needed some readjustments to keep up with the deadlines. Now, the reason for using a commit instead of the 1.3 tag is that Doomseeker is VCS dependant on compilation to determine the version and so on, and since the Mercurial code no longer worked it was necessary to change some really minor things to get it to work in git. Now, the VCS checking could have been bypassed, but that would require a manual generation of a header file, and that's more complex than what it needs to be, since I can assure you that a commit on the master branch of the official repo will not be rebased. Now, using the actual tarball is a good idea, but back when 1.1 was the official release the tarball did stop working and it was necessary to move to a more modern commit. This could be redone to go back to using the tarball, but the last thing I want is to bump the epoch every time I have to switch back and forth because Qt (for instance) now does something differently.

TLDR: I am aware of these things, it's not ideal but how it's done is the simplest and more reliable way. If things did not break, I'd do as you say.

did it move again, or...

also you should use an actual release tarball or versioned release snapshot since this isn't a VCS package.

if they do any rebasing or release repointing, your build is going to break since it currently uses commit refs.

Fixing asap, We have moved the repo

It won't download

==> Retrieving sources... -> Cloning doomseeker hg repo... abort: HTTP Error 404: Not Found ==> ERROR: Failure while downloading doomseeker hg repo Aborting... Error downloading sources: doomseeker

I'm fixing this asap :)

Hi, right now this package fails to install for me giving this error after compiling seemingly fine:

...

-- Installing: /home/username/Downloads/doomseeker/pkg/doomseeker/usr/share/doomseeker/translations/turok2ex_pl_PL.qm

mv: cannot stat '/home/username/Downloads/doomseeker/pkg/doomseeker/usr/lib64': No such file or directory

Regards