Missing binary package for www/ungoogled-chromium in 15.0 latest

tembun

tembun

Hello there!

I've just upgraded from 14-STABLE to 15-STABLE:
Code: 
$ uname -r
15.0-ALPHA1
As part of that, I reinstalled pkg(7) with pkg bootstrap -f and was just about to perform a pkg upgrade, but it reported me the following:
Code: 
Installed packages to be REMOVED:
        ...
        ungoogled-chromium: 137.0.7151.103_2
        ...

There were some other packages that would be removed, but those now have different name or something like that (so I can still find them), but I'm confused about www/ungoogled-chromium - why there's no binary package for it? I fetch the packages from 'latest', here's my /etc/pkg/FreeBSD.conf:
Code: 
FreeBSD: {
  url: "pkg+https://pkg.FreeBSD.org/${ABI}/latest",
  mirror_type: "srv",
  signature_type: "fingerprints",
  fingerprints: "/usr/share/keys/pkg",
  enabled: yes
}

Indeed, pkg-search(8) can't locate it:
Code: 
$ pkg sea ungoogled-chromium
echoes nothing.
Interestingly, package for www/chromium is present:
Code: 
$ pkg sea chromium
chromium-139.0.7258.127        Google web browser based on WebKit
chromium-bsu-0.9.16.1_3        Arcade-style, top-scrolling space shooter

So, i'm confused: does it mean that I have to compile it (again :)) from sources only? Or maybe this package will come a bit later? Because when I was running 14-STABLE and tracking latest packages as well, this package was there.

Thanks,
Artem.
 
Emrion said:
It's not 15-STABLE. See https://www.freebsd.org/releases/15.0R/schedule/
Click to expand...
Well, it is, as I can see. Link that you sent says that stable/15 was branched-off 5 September 2025 - and this is exactly the git branch I've built from. Regarding 15.0-ALPHA1: yeah, technically, it's no longer 15-STABLE, because 15-STABLE updated to 15.0-ALPHA2 almost 2 days ago, but I started build(7)ing the world a little bit earlier, before this change was commited.

Emrion said:
For the missing package, check this: https://forums.freebsd.org/threads/package-for-xyz-doesnt-exist-cannot-be-found.94582/
Click to expand...
Thanks! I will check it out.
 
This happened at some point with 14.x as well. I only vaguely remember it, because at some point, I thought I would install it, but didn't find a package. I went to build it on a reasonably powerful machine (32G 16 CPU) and it took over 12 hours. Eventually, it did show up in packages. T-Aoki has also mentioned that it took 12 plus hours to build from ports for him. Now, you said you're using 15, which is called stable, but if I remember, it is actually still doing Beta2 or 3. As such, I'm guessing it's using latest for packages, which is where you're often likely to have (temporarily) non-building ports. I would guess that if you can be patient, it will show up eventually. And, if you're not patient, you could try building from ports, but it will take several hours.
 
I'm also interested in installing ungoogled-chromium on FreeBSD 15 as a binary package. I guess this is a good place to make this known and also that it doesn't seem possible right now.
 
AlfredoLlaquet said:
I'm also interested in installing ungoogled-chromium on FreeBSD 15 as a binary package. I guess this is a good place to make this known and also that it doesn't seem possible right now.
Click to expand...
Unfortunately, the package for it still has not been built. It's now just blacklisted in all builds for 15-amd64 (you can find it in 'Ignored ports' section).

Well, I myself already suspected that this is not about to be fixed any soon probably after month of waiting. Yesterday I finally compiled ungoogled-chromium from ports. It took me ~2.5 days :) But lucky for me, there were no compilation errors whatsoever, in fact, a couple days ago a crucial patch that fixed one nasty compilation error was applied, so I decided to compile it from source just in time.
 
tingo said:
We will just have to wait, it will show up eventually, when they fix whatever fallout which is currently stopping the package to build successfully.
Click to expand...
Well, I didn't look very deeply on the exact problem there, but right now (after that patch I mentioned above) I would guess that the only reason it can't be compiled now is the compilation time (poudriere by default kills a build process after 24 hours or so). So I suppose it can be fixed just by adjusting a poudriere config flag for timeout limit.

At the very least, I did compile it successfully, so I believe there should be no compilation errors for package builds as well.
 
You must log in or register to reply here.
Back
Top