FreeBSD ports frozen after someone commits the entire 150MB Linux Copilot binary – OSnews
Home > FreeBSD > FreeBSD ports frozen after someone commits the entire 150MB Linux Copilot binary<br>A rather unusual announcement was made late last night: the FreeBSD project has frozen their ports repository. For more than 48 hours now, no changes have been accepted or made to the tree, and here’s why.<br>A 150MB binary file was recently committed to the ports tree and, as a result, core@ made the decision to implement a temporary freeze of the ports tree in order to implement some clean up efforts. The commit in question severed our ports tree mirroring to github.com due to their filesize hard limit of 100MB, and introduced a blob of questionable licensing into the repository history.
↫ Kyle Evans in freebsd-announce<br>While FreeBSD’s ports tree is not hosted by GitHub – it’s merely mirrored there – the FreeBSD team believes the community values the GitHub mirror too much, and as such, steps had to be taken to fix this. Ports has not been compromised and users’ systems do not appear to be at risk in any way due to this occurrence, which is good news.<br>Curiously, the official announcement makes no mention of which 150MB file, exactly, was committed to ports, but it didn’t take for people long to pinpoint the offending commit (screenshot). It turns out someone committed the entire github-copilot-cli Linux binary to ports, as part of the github-copilot-cli port. This FreeBSD port is effectively a way to easily install and run this tool on FreeBSD using Linuxulator, FreeBSD’s Linux compatibility layer that allows you to run unmodified Linux binaries on FreeBSD.<br>It’s important to note this FreeBSD port is not actually a port of the Linux version of github-copilot-cli to FreeBSD; the FreeBSD "port" merely acts as a setup script to run the unmodified Linux binary using Linuxulator. It’s not a "real" port because the tool isn’t open source and its license doesn’t allow for modifications. That’s why the announcement specifically mentions "questionable licensing" – github-copilot-cli is licensed under some custom license specifically made for this tool, and is not open source.<br>Anyway, for whatever reason, the maintainer of this FreeBSD port accidentally made a commit that added the actual, full 150MB Linux binary to FreeBSD ports. I’m assuming that under normal circumstances, building and installing the github-copilot-cli FreeBSD port would merely download the binary off GitHub and set Linuxulator up so that it could run it. Mistakes happen, and since there’s clearly nothing malicious going on, there’s not much to worry about. In fact, this may lead to new checks and balances to prevent this from happening in the future, which would be good news.<br>The FreeBSD team is working on rolling back, fixing the issue, and investigating how this could have happened. Ports is still frozen at the time of writing, but I’m sure we’ll have a more detailed account soon.
About The Author
Thom Holwerda
Follow me on Mastodon @[email protected]
4 Comments
2026-07-24 12:05 pm
KelsonV I’d guess the maintainer ran "git add ." by mistake and didn’t catch it before they pushed it upstream. We’ve* all done that at least once.<br>*In this case, we = programmers who use git at least sometimes.
Log in to Reply
2026-07-24 5:54 pm
Kochise Just like some leaders push the red button by mistake.
Log in to Reply
Leave a Reply Cancel reply<br>You must be logged in to post a comment.
Donate to OSNews
You can also:<br>Become a Patreon<br>Buy OSNews merch
Search OSNEWS
OSnews Accounts<br>Create Account<br>Login
Topics<br>TopicsSelect Category.NET3DAcademic OSesAMDAmiga & AROSAndroidAppleBenchmarksBSD & DarwinBugs & VirusesClown carComicsDatabasesDebianDesktop environmentsEditorialFedora CoreFinanceFreeBSDFuchsiaGamesGeek stuffGeneral DevelopmentGenodeGentooGifts, ContestsGnomeGoogleGraphicsGTK+HaikuHardwareHealthHumorIBMIn the NewsIntelInternetInternet ExplorerJavaKDELegacy OSesLegalLinspireLinuxmacOSMandriva, Mandrake, LycorisMicrosoftMobileMonoMorphosMozilla, GeckoMultimedia, AVNetBSDNovell and XimianOfficeOpen SourceOpenBSDOpenStep, GNUstepOperaOracle and SUNOriginal OSNews InterviewsOS NewsOS/2PC-BSDPodcastsPrivacy, SecurityQNXQtReactOSRed HatRedox OSRetro computingRISC OSRumorsSCOServoSGI and IRIXSkyOSSlackware, SlaxSolarisSponsorSuSE, openSUSESyllable, AtheOSTechnofascismUbuntuUnixWaylandWeb 2.0WindowsWirelessXfceZeta
Related Posts
FreeBSD 6.0 Will Target Wireless Devices
August 19, 2005 •<br>63 Comments
Review: FreeBSD 6.0
November 8, 2005 •<br>112 Comments
KSE Progress on FreeBSD SMP Environment
June 24, 2003 •<br>14 Comments
A trip into FreeBSD
February 17, 2021 •<br>3 Comments
FreeBSD 5.4-RC3 Released
April 19, 2005 •<br>28 Comments
Popular Posts
You paid me, a long-time Linux user, to use Windows 11 exclusively for a month: here’s how it went
July 8, 2026 •<br>60 Comments
What was nice about the UI of Windows 2000
June 19, 2026 •<br>57...