NuxRef Repository

Introduction

The NuxRef Repository contains packages I maintained which are either original or a fork of the original changed for my own needs. Most RPMs on here are additionally featured in my blog entries.

Note: These repositories only supports 64-bit architectures.

Setup

The following RPMs will get you set up:

Repositories

Content/Repositories are grouped as follows:

  • nuxref – el6/src/rss, el7/src/rss, el8/src/rss, fc29/src/rss, fc30/src/rss, fc31/src/rss, fc32/src/rss, fc33/src/rss, fc34/src/rss : All custom packages rebuilt reside here.
  • nuxref-testing – el6/src/rss, el7/src/rss, el8/src/rss, fc29/src/rss, fc30/src/rss, fc31/src/rss, fc32/src/rss, fc33/src/rss, fc34/src/rss : This is where I build early releases of projects I took on as my own. It’s also where I build newer versions of code already shared in the nuxref repository above. Once I’m satisfied with something here, it’ll eventually move into the nuxref repository.
  • nuxref-shared – el6/src/rss, el7/src/rss, el8/src/rss, fc29/src/rss, fc30/src/rss, fc31/src/rss, fc32/src/rss, fc33/src/rss, fc34/src/rss: This is really just a snapshot in time of packages I used from the different external repositories I don’t maintain. It may not always be up to date, but it can be thought of as a baseline I use to support other blog entries I wrote. Anything you intend to install from the nuxref or the nuxref-testing repository may also require dependencies. I try to include those here to ease things for other people so they don’t run into dependency nightmares in the future. It’s also important to note that even though these packages are not mine, I re-write their rpm signature as an act to let you know it’s safe.

Repository Priorities

Most of my packaging is original, but some of it is based on and/or replaces content to which other repositories neglected or had just simply forgotten to maintain. I’ll only repackage something here because I either found a bug, or that I updated it to a more recent version. This process can however introduce conflicts over time when the original source finally gets around to updating their version. As recommended in one of the comments below, it would be advisable to install yum-priorities on your system. This can allow the original’s sources content to always over-ride mine.

# CentOS 6 & 7 users may wish to do this:
yum install yum-plugin-priorities

# DNF (for Fedora users) already has priorities built into it
# The following command will lower the priority for you:
sed -i -e 's/^\(priority\)=.*/\1=2/g' /etc/yum.repos.d/nuxref.repo

Consider that this can also work against you as well. Some of the packages I host add additional enhancements and patches that improve the usability of the product. If you chose to lower the priority of this repository and acquire the one hosted by the original source, you may lose functionality you once had (hence the reason I repackaged it in the first place).

If there are ever conflicts with my repository and another, please feel free to email me and let me know or just leave a comment in comment section below. I have no problem upgrading packages (and/or just simply abandoning them if there is no need to rehost them anymore). My goal is to keep all of the 3rd party repositories out there in working harmony with mine (if I can). My repositories are to just simply offer another (open source) solution for people.

Appreciation

I do all this for free and only when I have time on weekends (and some evenings). This includes hosting fees, system updates, the repository hosting, and all of the research for new packaging that I share. I certainly want to be clear by saying that no one owes me anything at all. But if you want to lend a helping hand by just buying me a cup of coffee (if I was able to help you out), it would certainly be greatly appreciated.

69 thoughts on “NuxRef Repository”

  1. Thanks for your updates. I haven’t had time to get any of this working out of the box with an actual Fedora 28 and 29 RPM only because they changed how the product that i normally use works with these flavors.

    Glad to see you have a workaround though and thanks for sharing it! 🙂

    Reply

  2. For now, you could try adding –ignorerepo=epel to your yum command as there appears to be a conflict taking place. Alternatively if it’s just my repository that is holding you back, you could try –ignorerepo=nuxref instad and see if the update goes a little smoother.

    The packages on nuxref (my repository) for NodeJS are probably pretty old now; at the time they would have been better than EPEL, but it’s possible the EPEL repository has finally caught up (this is a good thing).

    Anyway; thanks for sharing your issue; I’ll see if i can investigate this further in the next couple of days and make the 2 repositories work in harmony again.

    Reply

    1. Thank you for your reply. I have tried your “-ignorerepo” command but this didn’t worked. But with “yum update –disablerepo=nuxref*” I was able to run my update command for all other packages 😉

      Hope to hear from you soon. 😉

      Reply

      1. Hi Toxic,

        I made one small change to the repository that should help you out. You’ll want to clean any nuxref metadata you have cached with yum first (otherwise it won’t see this new package):

        # as root
# the below just clears the nuxref metadata
yum clean all --disablerepo=* --enablerepo=nuxref*

        Then you should be able to get the package you’re stuck on (node-gyp). EPEL refers to it as node-gyp which is against their normal naming convention (which prefixes everything with “nodejs-“). I updated my copy of it which will hopefully resolve your issue. So… back on topic: after clearing your yum cache, this command should actually pull from nuxref’s repo and not epel:

        # as root
yum install node-gyp

        Alternatively; you should be able to just try your original yum install command again and it will work.

        Reply

        1. Thank you for your solution but this worked partial I have some issues left:

          Fehler: Paket: nodejs-npmconf-0.1.3-1.el7.noarch (@epel)
          Benötigt: npm(once) < 1.2
          Entfernen: nodejs-once-1.1.1-5.el7.noarch (@epel)
          npm(once) = 1.1.1
          Aktualisiert durch: nodejs-once-1.3.3-1.el7.nuxref.noarch (nuxref)
          npm(once) = 1.3.3
          Fehler: Paket: nodejs-npmconf-0.1.3-1.el7.noarch (@epel)
          Benötigt: npm(osenv) = 0.0.3
          Entfernen: nodejs-osenv-0.0.3-5.el7.noarch (@epel)
          npm(osenv) = 0.0.3
          Aktualisiert durch: nodejs-osenv-0.1.3-1.el7.nuxref.noarch (nuxref)
          npm(osenv) = 0.1.3
          Fehler: Paket: nodejs-npmconf-0.1.3-1.el7.noarch (@epel)
          Benötigt: npm(ini) < 1.2
          Entfernen: nodejs-ini-1.1.0-3.el7.noarch (@epel)
          npm(ini) = 1.1.0
          Aktualisiert durch: nodejs-ini-1.3.4-1.el7.nuxref.noarch (nuxref)
          npm(ini) = 1.3.4
          Fehler: Paket: nodejs-npmconf-0.1.3-1.el7.noarch (@epel)
          Benötigt: npm(mkdirp) < 0.4
          Entfernen: nodejs-mkdirp-0.3.5-3.el7.noarch (@epel)
          npm(mkdirp) = 0.3.5
          Aktualisiert durch: nodejs-mkdirp-0.5.1-1.el7.nuxref.noarch (nuxref)
          npm(mkdirp) = 0.5.1
          Fehler: Paket: nodejs-npmconf-0.1.3-1.el7.noarch (@epel)
          Benötigt: npm(semver) < 3
          Entfernen: nodejs-semver-2.1.0-3.el7.noarch (@epel)
          npm(semver) = 2.1.0
          Aktualisiert durch: nodejs-semver-5.1.0-1.el7.nuxref.noarch (nuxref)
          npm(semver) = 5.1.0

          Reply

          1. We’ll just keep tackling this one package at a time. I updated package at the top of your error list (nodejs-npmconf) on my site (to attempt to be compatible with what you’re trying to do).

            You’ll have to clean your nuxref cache again before trying again (see our previous chat exchange) and give it another try. Let me know how it goes! If you get into another pickle, just keep pasting your errors and we’ll slowly figure them out! 🙂

            Thanks for being patient in this matter!

            Good luck!

        2. I can’t answer to your last comment.

          However your last solution works now and I was able to run my yum update command.

          Thank you for your support 😉

          Reply

    1. Hi,

      This is probably the one (and only) time I actually had this package updated just hours after it was released :). It’s already available through yum (and was at the time you made this post). But you can also get it directly here.

      Reply

  5. Hey,

    it’s me again. 😉
    Actually I have 2 dependencies issues with your repo:

    Fehler: Paket: python2-josepy-1.2.0-1.el7.noarch (epel)
    Benötigt: python2-setuptools
    Verfügbar: python-setuptools-0.9.8-7.el7.noarch (base)
    python2-setuptools = 0.9.8-7.el7
    Installiert: python-setuptools-25.0.1-1.el7.nuxref.noarch (@nuxref)
    ~python-setuptools = 25.0.1-1.el7.nuxref
    Fehler: Paket: nodejs-validate-npm-package-name-2.2.2-1.el7.nuxref.noarch (@nuxref)
    Benötigt: npm(builtins) = 0.0.7
    Entfernen: nodejs-builtins-0.0.7-1.el7.nuxref.noarch (@nuxref)
    npm(builtins) = 0.0.7
    Aktualisiert durch: nodejs-builtins-1.0.2-1.el7.noarch (epel)
    npm(builtins) = 1.0.2

    Do you have any solutions?

    Greetings

    Reply

    1. Sorry to take so long to get back to you. It looks like the EPEL Repository is conflicting with mine. What happens if you just try something like:

      yum --disablerepo=* --enablerepo=epel install python2-josepy

      Does that work?

      Reply

      1. Nope not really.

        Fehler: Paket: python2-josepy-1.2.0-1.el7.noarch (epel)
        Benötigt: python2-setuptools

        It needs python2-setuptools but my system has python2-2-setuptools. ?

        Reply

        1. First off,

          Sorry to take so long to get back to you. Life is a busy one :). This weekend i will try to repackage python-setuptools (my copy here) to additionally mask itself as python2-setuptools and python2-2-setuptools. That should hopefully fix your issue.

          Reply

        2. I pushed a small update that may work for you. You’ll need to make sure you clear your yum cache first before you give it another shot. Let me know how it goes. 🙂

          Reply

          1. Thank you for your reply.

            It seems like that python2-josepy update is working. The only package left is the nodejs-builtins. Your package is behind the epel release package. I think an update to the latest version would solve the problem. 😉

            An update to nodejs-builtins from 0.0.7-1.el7.nuxref to 1.0.2-1.el7 is available.

          2. I upgraded it to 2.0.1; It is possible I broke things though. Please let me know and I’ll revert back to the version you suggested instead.

          3. Sorry for my late response…yes you broke things 😛

            —> Paket nodejs-builtins.noarch 0:0.0.7-1.el7.nuxref markiert, um aktualisiert zu werden
            –> Abhängigkeit npm(builtins) = 0.0.7 wird für Paket nodejs-validate-npm-package-name-2.2.2-1.el7.nuxref.noarch verarbeitet
            —> Paket nodejs-builtins.noarch 0:2.0.1-1.el7.nuxref markiert, um eine Aktualisierung zu werden
            –> Abhängigkeit npm(semver) >= 6.0.0 wird für Paket nodejs-builtins-2.0.1-1.el7.nuxref.noarch verarbeitet
            –> Abhängigkeitsauflösung beendet
            Fehler: Paket: nodejs-builtins-2.0.1-1.el7.nuxref.noarch (nuxref)
            Benötigt: npm(semver) >= 6.0.0
            Installiert: nodejs-semver-5.1.0-1.el7.nuxref.noarch (@nuxref)
            npm(semver) = 5.1.0
            Verfügbar: nodejs-semver-2.1.0-3.el7.noarch (epel)
            npm(semver) = 2.1.0
            Fehler: Paket: nodejs-validate-npm-package-name-2.2.2-1.el7.nuxref.noarch (@nuxref)
            Benötigt: npm(builtins) = 0.0.7
            Entfernen: nodejs-builtins-0.0.7-1.el7.nuxref.noarch (@nuxref)
            npm(builtins) = 0.0.7
            Aktualisiert durch: nodejs-builtins-2.0.1-1.el7.nuxref.noarch (nuxref)
            npm(builtins) = 2.0.1
            Verfügbar: nodejs-builtins-1.0.2-1.el7.noarch (epel)
            npm(builtins) = 1.0.2

  6. Nope not really.

    Fehler: Paket: python2-josepy-1.2.0-1.el7.noarch (epel)
    Benötigt: python2-setuptools

    It needs python2-setuptools but my system has python2-2-setuptools. 😉

    Reply

  7. Thanks for all the hard work you did over the years, i have used your repo on Centos 7 for a while.
    im swithing to Centos 8 at the moment, and im wondering if you expect to start offering the repo for Centos 8 as well?

    Reply

    1. I hope so soon. I apologize for not having done much. I just haven’t had much incentive to keep this thing going ?. It’s a lot of work to maintain for little reward. But comments like yours (implying that you did actually use it) are always nice.

      Reply

  8. Any plans to support Fedora 31? Also I see the repo even on FC30 is somewhat behind the latest version.
    With my FC31 install python has been upgraded to ver 3 so I has to change the systemd files to explicitly run python2.

    Reply

    1. You caught me red handed. ? Starting with FC30 (I think) they completely dropped Python 2 support. I hadn’t begun the massive overhaul to start re-figuring out Sabnzbd, CouchPotato, etc.. I’m just a one man team over here doing it for free and have just had other priorities at the time.

      No promises, but the goal would really be to start seeing what can get ported to python 3 and doing it.

      Reply

        1. The problem is that Fedora 32 no longer supports Python 2.x which is the base of most systems. Other then NZBGet, there wouldn’t be much to prepare.

          Reply

    2. I just put it in the repo now but it’s not tested yet. I need to update the HTML on the main page, but if you swap fc30 for say fc31 or fc32 or even el8 you should get the desired results. I’m still slowly updating the repositories with all of the new stuff.

      Edit: repo website update 🙂

      Reply

      1. Got some time to test the latest repo. Fresh install of CentOS 8 (2004). Linked the nuxref repo el8. Installed python3. And finally ran : yum install –enablerepo=nuxref –enablerepo=nuxref-shared sabnzbd which errored out:

        # yum -y install sabnzbd
        Last metadata expiration check: 0:09:14 ago on Wed 09 Sep 2020 01:02:15 PM EDT.
        Error:
        Problem: cannot install the best candidate for the job
        – nothing provides dbus-python needed by sabnzbd-3.0.2-2.el8.nuxref.noarch
        – nothing provides python3-feedparser needed by sabnzbd-3.0.2-2.el8.nuxref.noarch
        (try to add ‘–skip-broken’ to skip uninstallable packages or ‘–nobest’ to use not only best candidate packages)

        Extra packages should be installed separately or are part of sabnzbd dep-s? Thx much!

        Reply

        1. Dan,

          Thanks for all your help testing! Your report was very complimentary to another (source). Basically it comes down to: I think i fixed it now. 🙂

          • I didn’t realize that python3-feedparser doesn’t ship with EL8 (but does with all Fedora versions). I built it for EL8 and added it to the repo. That will fix that entry.
          • I built the unrar packages as well and am now hosting them; so that will no longer be a problem.
          • dbus-python I dropped as a Required RPM; I don’t feel it’s needed personally.

          Consider flushing your cache to pull in the new repo updates:

          sudo dnf clean all
sudo dnf install sabnzbd
          Reply

          1. hmm git this at install:

            error: lsetfilecon: (/var/lib/sabnzbd/admin, system_u:object_r:var_lib_t:s0) Operation not supported
            error: lsetfilecon: (/var/lib/sabnzbd/complete, system_u:object_r:var_lib_t:s0) Operation not supported
            error: lsetfilecon: (/var/lib/sabnzbd/email, system_u:object_r:var_lib_t:s0) Operation not supported
            error: lsetfilecon: (/var/lib/sabnzbd/incomplete, system_u:object_r:var_lib_t:s0) Operation not supported
            error: lsetfilecon: (/var/lib/sabnzbd/nzb_backups, system_u:object_r:var_lib_t:s0) Operation not supported
            error: lsetfilecon: (/var/lib/sabnzbd/scan, system_u:object_r:var_lib_t:s0) Operation not supported

            what is the problem?

          2. systemctl start sabnzbd fails and i see this in messages:

            Sep 10 10:28:26 leviathan python2[215874]: Sorry, requires Python 3.5 or above
            Sep 10 10:28:26 leviathan python2[215874]: You can read more at: https://sabnzbd.org/python3

            hmm I’ve installed python36 hmmmm

          3. And fixed it you have Sir! Install went w/o a hiccup. In addition to that, sabnzbd v3 booted fine with v2 conf. So, all’s good.

            Thanks a bunch for holding up providing these rpm-s. Saves a lot of hassle. Cup of coffee well deserved! 🙂 Cheers!

    1. It’s a bit of a bigger challenge because Python 3.x support is somewhat spotty for CentOS 7.x. I’ll look into it, but no promises only because i already foresee having to build a lot of packages to make it possible (for Python 3.x that aren’t otherwise available).

      Reply

    1. That’s strange; What happens if you do follow through with the instructions… or even take it one step further:

      yum clean all --disablerepo=* --enablerepo=nuxref*
      Reply

      1. I am running into the same issue. I ran the command above, then tried yum update again, same exact error.

        If I download the rpm directly and attempt to run “yum install” I get this error:
        ERROR You need to update rpm to handle:
        rpmlib(PayloadIsZstd) <= 5.4.18-1 is needed by nuxref-release-1.0.0-5.el7.nuxref .noarch
        RPM needs to be updated
        You could try running: rpm -Va –nofiles –nodigest

        Reply

        1. I built the Centos 7.x 1.0.0-5 RPM using Fedora 32; that was probably my first mistake. The good news is, there is no difference between 1.0.0-4 and 1.0.0-5 anyway (for CentOS 7), so i just removed the newer RPM entirely. This should the repo error you and the previous user was getting.

          Let me know! 🙂

          Reply

          1. Well, I ran the command to clear the nuxref metadata, but running yum update still thinsk there is a 1.0.0.5 release, now it just fails to download it and generates a different error.

            —————-
            Downloading packages:
            Delta RPMs disabled because /usr/bin/applydeltarpm not installed.
            nuxref-release-1.0.0-5.el7.nux FAILED
            http://repo.nuxref.com/centos/7/en/x86_64/custom/nuxref-release-1.0.0-5.el7.nuxr ef.noarch.rpm: [Errno 14] HTTP Error 404 – Not Found
            Trying other mirror.
            To address this issue please refer to the below wiki article

            https://wiki.centos.org/yum-errors

            If above article doesn’t help to resolve this issue please use https://bugs.cent os.org/.

            Error downloading packages:
            nuxref-release-1.0.0-5.el7.nuxref.noarch: [Errno 256] No more mirrors to try.
            ———————

          2. Unfortunately the error you shared definitely identifies that your meta data hasn’t been entirely flushed because as your pointing out, it’s still looking for an rpm (that isn’t there).

            sudo yum clean all --disablerepo=* --enablerepo=nuxref*
sudo yum update

            give it one more try and let me know 🙂

          3. Hey,
            I’m also having the same issue. Followed all the steps by disabling repos, just enabling nuxref. Cleared the yum cache.
            I’ve also tried manually removing nuxref and reinstalling that didn’t seem to help at all still erroring out at the same place. It really wants to download that updated nuxref-release 😀

            Thanks.

  13. Hey,

    I’ve flushed all the metadata, done yum clean multiple times, tried disabling nuxref removing it, reinstalling it.. and I am still getting the error where it is looking for 1.0.0-5 for el7.

    Not sure if there is anything else i can try.

    Thanks!

    Reply

    1. Sorry that you’re having all of these troubles. I’ve actually move nuxref to another server (behind the scenes). I didn’t realize i was no longer building the repo meta data properly. I think I’ve fixed it now :). Try clearing your meta data again (hopefully for the final try) and give it another go; keep me posted.

      Reply

        1. Okay, i set up a CentOS 7 VM and made what should be the final change i need to on my end. This time i even tested it through the VM. These words are getting repetitive at this point, but i truly thank you for hanging in there and helping me out. Give it another cache clean and one more try. This should be the final time.

          Reply

  14. trying to install on centos 8 and this is the error i get

    rpm -Uhi http://repo.nuxref.com/centos/8/en/x86_64/custom/nuxref-release-1.0.0-5.el8.nuxref.noarch.rpm
    warning: /var/tmp/rpm-tmp.n0UZPM: Header V4 RSA/SHA1 Signature, key ID efe82e3b: NOKEY
    ################################# [100%]
    ################################# [100%]
    Updating / installing…
    ################################# [100%]
    error: can’t create transaction lock on /var/lib/rpm/.rpm.lock (Resource temporarily unavailable)
    error: /etc/pki/rpm-gpg/RPM-GPG-KEY-nuxref-com: key 1 import failed.
    [root@pumba usr]# dnf install -y sabnzbd
    RHEL 8 – nuxref.com 19 kB/s | 3.9 kB 00:00
    Errors during downloading metadata for repository ‘nuxref’:
    – Status code: 404 for http://repo.nuxref.com/centos/8/en/x86_64/custom/repodata/repomd.xml (IP: 165.22.234.27)
    Error: Failed to download metadata for repo ‘nuxref’: Cannot download repomd.xml: Cannot download repodata/repomd.xml: All mirrors were tried

    Reply

    1. Clear your cash and try it one more time; this is a result of a lot of serverside changes that occurred on my side. I’ve re-generated the file in question manually; you should be good to go (you may need to clear your dnf cache first though). Thank you for your patients!

      Reply

    1. I just pushed it now; let me know if you have any problems. Servers are running on CentOS 8 now (not 7 like before). As a result I lost the tool used to auto-generate the nice web preview of what has been uploaded (because of the remove of yum). I need to fix this. – Update 2020.12.11 Fixed!
      But for now if you clear your dnf/yum cache and try again, you should be good to go.

      Reply

  17. I’m not getting errors any more. Thanks for all of the hard work.! Can we get an update to the SABnzbd rpm? I’m getting

    sabnzbd-2.3.9-1.el7.nuxref.noarch already installed and latest version

    from the repo. Is that accurate?

    Reply

  18. Hi …. been a while, sabnzbd is up to 3.5.1. Your latest build is at 3.1.1. Any chance you’d feel like rebuilding sab and updating the repo? Much appreciated… Dan.

    Reply

  19. Hi… sabnzbd is up to 3.5.1. Would you feel like building it and updating the repo? I think the last one you did is 3.1.1. Thx mch! Dan

    __ Sorry if duplicate-posted … previous post seemingly got through.. but is nowhere to be seen.

    Reply

  23. Nuxref seems pretty moribund, sadly.

    Any chance you could post your SRPMs (or specfiles) somewhere so that others can pick up the torch?

    Reply

Leave a Reply

Your email address will not be published. Required fields are marked *

Linux Solutions