chromium disappeared from quarterly

putin.is.a.thief

putin.is.a.thief

Looks like there is no more chromium in http://pkg.freebsd.org/${ABI}/quarterly

https://pkg.freebsd.org/FreeBSD:12:amd64/quarterly/All/ - no chromium

Same with pkg:
Code: 
$ sudo pkg install chromium
Password:
Updating FreeBSD repository catalogue...
FreeBSD repository is up to date.
All repositories are up to date.
pkg: No packages available to install matching 'chromium' have been found in the repositories

Code: 
$ sudo pkg search chromium
chromium-bsu-0.9.16.1_1        Arcade-style, top-scrolling space shooter

Code: 
$ pkg info|grep pkg
pkg-1.13.2                     Package manager
pkgconf-1.6.3,1                Utility to help to configure compiler and linker

Just updated with pkg update -f, quarterly repo.
Code: 
$ cat /etc/pkg/FreeBSD.conf
# ...
FreeBSD: {
  url: "pkg+[URL]http://pkg.freebsd.org/$[/URL]{ABI}/quarterly",
  mirror_type: "srv",
  signature_type: "fingerprints",
  fingerprints: "/usr/share/keys/pkg",
  enabled: yes
}
 
Looks like the port was last updated on Saturday. Maybe it needs time for the pkg to be built but that doesn't explain why the previous version was removed.

FreshPorts -- www/chromium: Google web browser based on WebKit

Chromium is an open-source browser project that aims to build a safer, faster, and more stable way for all users to experience the web. The Chromium website contains design documents, architecture overviews, testing information, and more to help you learn to build and work with the Chromium...
www.freshports.org www.freshports.org
 
Chromium failed to build on the latest quarterly runs.

Once the run is finished, the pkg repo is wiped clean and all the successfully built packages are then copied to the repo.
This is one reason why packages 'disappear' from time to time.
 
It's been several days chrome is not present in /latest pkg repo
This mean all new users which have installed FreeBSD can't install this browser right now, am I right? Is it ok? Seems to be a problem
 
Last built for latest failed.

putin.is.a.thief said:
This mean all new users which have installed FreeBSD can't install this browser right now, am I right?
Click to expand...
No. The default is set to quarterly and chrome is present there. It only failed in latest.

putin.is.a.thief said:
Seems to be a problem
Click to expand...
Packages fail to build all the time, for all sorts of reasons. Most of the time those issues are fixed fairly quickly.
 
SirDice said:
Packages fail to build all the time, for all sorts of reasons. Most of the time those issues are fixed fairly quickly.
Click to expand...
This one needs special attention. www/chromium builds fine for amd64/quarterly, but fails several time for amd64/latest, cause: build/timeout, runaway_process. For the last builds, chromium took ~ 32:04 hours before it was (assumed) killed (haven't checked, log file has 153M). Quarterly was build in 24:23 hours.
 
It often happens. It has a simple, but temporary solution. For example, at this moment in time:
  1. There's no chromium in the latest branch
    /usr/local/etc/pkg/repos/FreeBSD.conf
    Code: 
    FreeBSD: { url: "pkg+http://pkg.FreeBSD.org/${ABI}/latest",
mirror_type: "srv", signature_type: "fingerprints", fingerprints: "/usr/share/keys/pkg", enabled: yes }
  2. Switch to the quarterly branch, update and install chromium:
    /usr/local/etc/pkg/repos/FreeBSD.conf
    Code: 
    FreeBSD: { url: "pkg+http://pkg.FreeBSD.org/${ABI}/quarterly",
mirror_type: "srv", signature_type: "fingerprints", fingerprints: "/usr/share/keys/pkg", enabled: yes }
    pkg update -f
    pkg install chromium
  3. Now I Have a problem! I get a warning: vscode is going to get uninstall. Solution?
  4. Switch back to the latest branch, update pkg and delete the vscode:
    /usr/local/etc/pkg/repos/FreeBSD.conf
    Code: 
    FreeBSD: { url: "pkg+http://pkg.FreeBSD.org/${ABI}/latest",
mirror_type: "srv", signature_type: "fingerprints", fingerprints: "/usr/share/keys/pkg", enabled: yes }
    pkg update -f
    pkg delete vscode
  5. Now, switch to the quarterly, update and install both vscode and chromium:
    /usr/local/etc/pkg/repos/FreeBSD.conf
    Code: 
    FreeBSD: { url: "pkg+http://pkg.FreeBSD.org/${ABI}/quarterly",
mirror_type: "srv", signature_type: "fingerprints", fingerprints: "/usr/share/keys/pkg", enabled: yes }
    pkg update -f
    pkg install chromium vscode
  6. It's done (It's on the quarterly)
  7. Eventually, chromium pkg will show up in the latest branch, when it happens:
  8. Delete vscode and chromium, switch to latest, update and install them again:
    pkg delete chromium vscode
    /usr/local/etc/pkg/repos/FreeBSD.conf
    Code: 
    FreeBSD: { url: "pkg+http://pkg.FreeBSD.org/${ABI}/latest",
mirror_type: "srv", signature_type: "fingerprints", fingerprints: "/usr/share/keys/pkg", enabled: yes }
    pkg update -f
    pkg install chromium vscode
  9. It's done (It's on the latest)
  10. Just keep an eye on two branches and affected packages, in the mailing lists, bug reports, etc..
[EDIT]:
11. Or occasionally, switch back and forth between latest and quarterly, to check the status of package availability
 
They did it again. This is really (unprofessional [for the lack of a suitable term] and ) dangerous. This, without notice, leaves users dangling. It's like being punished for running updates. Seems like we need to keep jumping between quarterly to latest. Not everyone can rely upon the latest packages to not break things, some need to stay on quarterly to play it safe.

I installed the 'vulnerable' chrome pkg from cache and had to link new .so files as old to make chrome work. ungoogled-chromium seems to be more reliable when it comes to updates.
 
quakerdoomer said:
They did it again.
Click to expand...
Who's "they"? And what did they do?

quakerdoomer said:
Seems like we need to keep jumping between quarterly to latest.
Click to expand...
A new quarterly (2023Q1) was made recently, as a result quarterly and latest aren't that different at this point in time.

quakerdoomer said:
Not everyone can rely upon the latest packages to not break things, some need to stay on quarterly to play it safe.
Click to expand...
Once every quarter (guess why it's called quarterly), a new branch is made from the latest ports tree. This will be the new quarterly branch. 2023Q1 was just made.

I'm unsure why it failed to build in quarterly, latest did succeed and they both build the exact same version. The build on latest took more than 24 hours to complete though. On quarterly it croaked after a little more than 7 hours, so it might be a resource issue.
 
I was thinking earlier, when was the last time I thanked port maintainers for the stuff I use? Been a while I think. I think sometimes wisdom really does come with age; age doesn't mean how old one is, but how long one has been using something. I've been bitten by something disappearing but take a step back deep breath and realize "hey they do it for free, they have a life, it'll get fixed, how do I work around it". Basically, eh, don't sweat the things I can't control.
 
You can always set up your own repository and build everything yourself. Then you'll have complete control. Takes a lot of time though, and you need a fairly beefy machine if you want to build in a reasonable amount of time (my lowly old i5 typically takes 2 days to build 4 different repositories). But you don't have to build everything of course, only build what you actually need.
 
Note1:
On my older i7-8cores cpu building Chromium took 35hours to build. On my spick-splinter-new i5-12cores cpu building Chromium from ports takes at least 5hours.

Note2:
One can't complain people doing for free in their free time.
Chromium/Iridium will come back.
 
a6h said:
It often happens. It has a simple, but temporary solution. For example, at this moment in time:
  1. There's no chromium in the latest branch
    /usr/local/etc/pkg/repos/FreeBSD.conf
    Code: 
    FreeBSD: { url: "pkg+http://pkg.FreeBSD.org/${ABI}/latest",
mirror_type: "srv", signature_type: "fingerprints", fingerprints: "/usr/share/keys/pkg", enabled: yes }
  2. Switch to the quarterly branch, update and install chromium:
    /usr/local/etc/pkg/repos/FreeBSD.conf
    Code: 
    FreeBSD: { url: "pkg+http://pkg.FreeBSD.org/${ABI}/quarterly",
mirror_type: "srv", signature_type: "fingerprints", fingerprints: "/usr/share/keys/pkg", enabled: yes }
    pkg update -f
    pkg install chromium
  3. Now I Have a problem! I get a warning: vscode is going to get uninstall. Solution?
  4. Switch back to the latest branch, update pkg and delete the vscode:
    /usr/local/etc/pkg/repos/FreeBSD.conf
    Code: 
    FreeBSD: { url: "pkg+http://pkg.FreeBSD.org/${ABI}/latest",
mirror_type: "srv", signature_type: "fingerprints", fingerprints: "/usr/share/keys/pkg", enabled: yes }
    pkg update -f
    pkg delete vscode
  5. Now, switch to the quarterly, update and install both vscode and chromium:
    /usr/local/etc/pkg/repos/FreeBSD.conf
    Code: 
    FreeBSD: { url: "pkg+http://pkg.FreeBSD.org/${ABI}/quarterly",
mirror_type: "srv", signature_type: "fingerprints", fingerprints: "/usr/share/keys/pkg", enabled: yes }
    pkg update -f
    pkg install chromium vscode
  6. It's done (It's on the quarterly)
  7. Eventually, chromium pkg will show up in the latest branch, when it happens:
  8. Delete vscode and chromium, switch to latest, update and install them again:
    pkg delete chromium vscode
    /usr/local/etc/pkg/repos/FreeBSD.conf
    Code: 
    FreeBSD: { url: "pkg+http://pkg.FreeBSD.org/${ABI}/latest",
mirror_type: "srv", signature_type: "fingerprints", fingerprints: "/usr/share/keys/pkg", enabled: yes }
    pkg update -f
    pkg install chromium vscode
  9. It's done (It's on the latest)
  10. Just keep an eye on two branches and affected packages, in the mailing lists, bug reports, etc..
[EDIT]:
11. Or occasionally, switch back and forth between latest and quarterly, to check the status of package availability
Click to expand...

Thanks this has helped me.

Would be nice if we can use both quarterly and latest repo and be asked which repo to choose when doing a pkg install.

I also have an issue with chromium only whenever I do upgrades and updates for entire FreeBSD and never able to install chromium again from the package repository since it's never found in the latest repo.

I changed the ABI to quarterly and was able to install it.

Side note: Building chromium from scratch via the ports takes a whopping 4 hours on an AMD FX-8350 8 Core CPU.
 
quakerdoomer said:
They did it again. This is really (unprofessional [for the lack of a suitable term] and ) dangerous.
Click to expand...
Comments like that are kind of harmful. As I explained now several times on these forums, the way FreeBSD package repositories work is one non-perfect choice among three possible non-perfect choices (the "perfect world" being there would never ever be any build error, but it's pretty easy to show this is simply impossible in practice) – and in my opinion, definitely the "least bad" one.

quakerdoomer said:
This, without notice, leaves users dangling.
Click to expand...
It certainly doesn't. pkg never uninstalls a package without at least requesting your confirmation (unless you explicitly add -y).

Maybe the design decisions about FreeBSD package repositories should just be documented (including reasoning) more prominently ... plus some recommended best practices for package users.
 
You must log in or register to reply here.
Back
Top