Daniel Richard G.

Generally, if the issue is only a warning and does not prevent the build from completing, it can be ignored. Some of those warnings are familiar and have always been...

Yep, the expired key is a side effect of the lack of active maintenance. Even if the key were current, all you'd see is an ungoogled-chromium package from well over...

Hi @eyalroz. Please have a look in [the `convert/` subdirectory](https://github.com/ungoogled-software/ungoogled-chromium-debian/tree/unified/convert) for a supported process of converting the normal Debian package of Chromium into an ungoogled-chromium one.

> [@PF4Public](https://github.com/PF4Public) : I see... I don't suppose there is someplace that _does_ get kept up-to-date for obtaining Debian packages of ungoogled chromium? There is no such place at present,...

> Ok, so... is it possible to arrange for an apt repository which is compatible with Trixie? That is forthcoming. With the conversion framework under the `convert/` subdirectory, it will...

> I haven't been able to get the convert/ packaging to work for me, which is why I went back to updating the Debian packaging for Chromium 120. Could you...

@salfter, which package of ungoogled-chromium are you using?

I see. That package you were trying to install is ooooooold. There is an alternative process for providing ungoogled-chromium for Debian, but I am still working on the automation that...

Hi @yanetix. Yep, I'm afraid the install is broken. In this case, it's kind of a good thing, because the version it was trying to install (112.0.5615.165) is _ancient_ and...

Hi @PF4Public, Note that I have all of this already running since about February. The differences are that (1) it's running on my own server, (2) it handles more than...