LineageOS build rooster going again.

The infrastructure hosting the build rooster was upgraded a bit, and it broke the build process.

It turned out to be a combination of three things: the build machine’s swap partition wasn’t prepared with mkswap (so the build was getting randomly zapped by the OOM killer), and the FreeNAS update blew away the crontab running the nightly rsync. After fixing those two, it turned out that the regular expression I was using to select which builds to rsync wasn’t matching anything built in December anyway.

The rooster should be good to go again. Sorry about the delay.

About Chris Kobayashi

I'm a security systems engineer, specializing in UNIX, network, and physical security. I'm in Tokyo, and I'm mostly retired now. I'm well-versed in both electrical and software engineering, with a particular interest in old computers and game consoles. You can contact me here.
This entry was posted in LineageOS. Bookmark the permalink.

6 Responses to LineageOS build rooster going again.

  1. Clinton says:

    Hi Chris
    Top of the year to you! Ive been enjoying your Lineage 14.1 flo builds for a month.
    Ive tried to donate via paypal from both XDA and your own website. Unable in both
    cases.
    I may be able to “send” money but require your email address per PayPal instructions.
    If you can provide it, i’ll see what I can do on my side. Happy New Year Chris.

    Oh, my Nexus7 (2013) is not tripping OTG function any longer. Tried 2 OTG cables, 1 keyboard. No Joy. Charging, data transfer work well though. Im suspecting a board level problem. Any tech suggestions. Ive tried everything, including tear down, removal of board and ribbons. Cleaned port ect. Rooted before your 14.1 build.
    No difference. Wanted to use the N7 OTG output for my DAC. With USB Audio Player Pro.

    • Hello Clinton,

      Happy new year to you too! I’m glad to hear that the LineageOS builds are useful.

      Thanks for letting me know that the donate buttons are broken. It appears that PayPal doesn’t like a “+” character in the email address.

      I’ve changed it in both places; if it still doesn’t work, please take a screenshot of the error and send it to “trade-paypal@disavowed.jp” (which should also work as the donation address).

      Regarding OTG, I’ll take a look at it. If memory serves, OTG was was disabled on this device at release, and silently enabled in a subsequent Google update. I’ll bet that it wasn’t rolled into LineageOS.

      Thanks again for your support,
      — Chris

      • Clinton says:

        Hi again Chris.
        Used the trade-paypal@disavowed.jp and that worked.
        Any insights to my OTG mystery? Snowed today in Vancouver. Started twiddling with the N7 and thought you may have something to share before I pull my hair out.
        Any Snow in Tokyo?
        Regards
        Clinton.

  2. Fede says:

    Hi there,
    I’m trying out your athene builds, but I can’t seem to find any information regarding the support status for android 7.1.2
    Are there still security patches for it?
    Any help will be appreciated. I really like los 14.1 and don’t want to switch to anything else unless necessary.

    Thanks again!

    • Hello,

      LineageOS 14.1 is receiving security patches. They generally lag a few weeks behind the AOSP tree, but they are regularly applied to the 14.1 branch. In fact, that’s why my builds exist — although the source code contains the patches, the LineageOS team doesn’t see fit to provide sustaining builds for folks like us.

      Automatically generating a header for the downloads that states the patch revision for each build is on my to-do list.

      Thanks for using my builds 🙂

  3. clinton says:

    Hello Chris.
    Gee, now Im in lockdown, BC Canada with time on my hands. Did you ever figure out if OTG is supported by this 14.1 kernel? Hope things are going as best as possible for you and your community.
    Clinton

Leave a Reply

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

This site uses Akismet to reduce spam. Learn how your comment data is processed.