Ublue-brew removed

Aurora
1

Just saw that the newest image has

Removed: ublue-brew-0.1.13-1.fc43.x86_64

Not yet installed. What does it mean for automatic brew updates?

2

Nothing, as brew comes from GitHub - ublue-os/brew: Homebrew tarball generation and integration

3

Yes, but I was thinking twice because of

rpm -ql ublue-brew

/etc/profile.d/brew-bash-completion.sh
/etc/profile.d/brew.sh
/etc/security/limits.d/30-brew-limits.conf
/usr/lib/systemd/system-preset/01-homebrew.preset
/usr/lib/systemd/system/brew-setup.service
/usr/lib/systemd/system/brew-update.service
/usr/lib/systemd/system/brew-update.timer
/usr/lib/systemd/system/brew-upgrade.service
/usr/lib/systemd/system/brew-upgrade.timer
/usr/lib/tmpfiles.d/homebrew.conf
/usr/share/fish/vendor_conf.d/ublue-brew.fish
/usr/share/homebrew.tar.zst

which looks to me that the update service will vanish.

4

Why would it vanish? It’s still part of common for example.

5

I thought when the package is removed there is no longer, e.g. `/usr/lib/systemd/system/brew-update.service`

6

Nothing stops us getting the needed stuff from elsewhere. In this case the common and brew repos

7

What is the common?

8

See this here:

1 Like
9

Thanks. I haven’t checked yet. Does it mean that this common stuff contains the brew update mechanism?

EDIT: It looks like. The common stuff seems to be “wild” stuff. I mean it is not in any rpm package.

10

The systemd services are here:

It’s ingested here:

1 Like
11

Don’t know what you mean by “wild”?

But the point is that we don’t want to rely on rpm packages if there is more native way of doing, like with OCIs.

12

When saying “wild” I mean to put stuff in /usr/… without having it packaged in an rpm package. :laughing:

IMHO, packages have some advantages. For example, I could find out to which package a file belongs: rpm -q –file /usr/lib/systemd/system/brew-update.timer

So, it seems that I can assume (but don’t know for sure) that “unpackaged” files in /usr belong to common.

1 Like