Will try to Maintain This Port

[AssassinK786]

I will try to maintain this port
Need Some Perquisites to maintain & develop

[networkException]

Any work on this highly appreciated! If you need anything I'll try my best to help

[AssassinK786]

Can you send some instructions to build and wiki

[networkException]

There are generic build instructions at https://github.com/ungoogled-software/ungoogled-chromium/blob/master/docs/building.md

[AssassinK786]

Getting OBS packages
Can you update it for Ubuntu jammy so that i can build the the packages
I will try on Ubuntu Focal
@networkException

[AssassinK786]

the build is building according to instructions
Just add that clang latest version is required

[ghost]

I can approve PRs if this gets anywhere.

[AssassinK786]

i am building it once again

[AssassinK786]

I'm building it on my laptop which is 10 yrs old
is there any way that i build these files without any hassle

[PF4Public]

is there any way that i build these files without any hassle

ccache could help immensely.

[AssassinK786]

Sorry For the Delay but it is taking time to build the file, like it has taken 3-4 days to build so I'm trying my best to get it done on time

Will try to create CI/CD pipeline for this project so that the work load reduces

[ghost]

Yea, kinda expected. My 8 core rig took like 4-8 hours to build it when I was still trying. I just got fed up when I ran into a JS performance issue I was unable to resolve.

[AssassinK786]

Stuck on this past 15minutes

[AssassinK786]

Yea, kinda expected. My 8 core rig took like 4-8 hours to build it when I was still trying. I just got fed up when I ran into a JS performance issue I was unable to resolve.

Mine is i3 intel 4 core processor

[ghost]

The link step tends to be the slowest part. I wonder if you're using enough builders then?

[AssassinK786]

give command to check it

[SugaryHull]

@AssassinK786 Redownload the 110 Compiler patch with the raw link

[SugaryHull]

They also have patches for Clang 13 and LLD 13. I'll try those out

Got ungoogled-chromium 111.0.5563.65 to build in a chroot environment with those patches. All I got was a singular ungoogled-chromium package and a debug symbols package. Is that normal?

[AssassinK786]

@AssassinK786 Redownload the 110 Compiler patch with the raw link

And which folder it should be dropped in ?

[SugaryHull]

@AssassinK786 Redownload the 110 Compiler patch with the raw link

And which folder it should be dropped in ?

I would put it in debian/patches because it's not specific to ungoogled-chromium

[SugaryHull]

Got ungoogled-chromium 111.0.5563.65 to build in a chroot environment with those patches. All I got was a singular ungoogled-chromium package and a debug symbols package. Is that normal?

I'll make a fork of ungoogled-chromium-debian with my changes and submit a pull-request

[AssassinK786]

They also have patches for Clang 13 and LLD 13. I'll try those out

Got ungoogled-chromium 111.0.5563.65 to build in a chroot environment with those patches. All I got was a singular ungoogled-chromium package and a debug symbols package. Is that normal?

Yes, You are right check my repo for deb file

[AssassinK786]

@AssassinK786 Redownload the 110 Compiler patch with the raw link

And which folder it should be dropped in ?

I would put it in debian/patches because it's not specific to ungoogled-chromium

Can you share your series file?

[SugaryHull]

This would be the series file you should have if you were to only add that 110 Compiler patch
https://0bin.net/paste/iYK5w1Hm#1zO+vZN1lYYNiAayF-vTTzqB4AU9MNhIIvwpgcyoSOZ

[AssassinK786]

This would be the series file you should have if you were to only add that 110 Compiler patch https://0bin.net/paste/iYK5w1Hm#1zO+vZN1lYYNiAayF-vTTzqB4AU9MNhIIvwpgcyoSOZ

There is not Debian/patches file for me
It is patches dir then core & extra dir with series file
both of them having debian dir
where should i ?

[AssassinK786]

This would be the series file you should have if you were to only add that 110 Compiler patch https://0bin.net/paste/iYK5w1Hm#1zO+vZN1lYYNiAayF-vTTzqB4AU9MNhIIvwpgcyoSOZ

https://0bin.net/paste/F0mYy3Mr#PgiJv1y1l5+ocUYApSYI5lBrF6MRW08SMZN7nxGlqLJ
this is my series File

[SugaryHull]

The series file is in the patches folder within the debian directory. You download the patch to the patches folder and then edit the series file in said folder to add the filename of the patch you downloaded. One filename per line

[ghost]

I have moved this to a discussion because it has basically turned into one.

[AssassinK786]

Ok no Problem

[AssassinK786]

@SugaryHull

This is Core Dir

This is extra Dir

in both dir have debian folder
So my Question is which debian folder you want me to put the patch

[SugaryHull]

That would explain it. I've been building from the Github repo. I would recommend doing that instead and just updating the ungoogled-chromium submodule to 111.0.5563.64-1. Doing it that way allows you to more easily contribute patches to this repo through a pull request

[SugaryHull]

I'm working on my own fork and am about to test the build to see if it's ready for a PR

[AssassinK786]

That would explain it. I've been building from the Github repo. I would recommend doing that instead and just updating the ungoogled-chromium submodule to 111.0.5563.64-1. Doing it that way allows you to more easily contribute patches to this repo through a pull request

how did update the submodules in github?

[SugaryHull]

Change the .gitmodules file to point to the current ungoogled-chromium repo, then initialize the submodules with git submodule update --init --recursive. If you've already initialized the submodules, then do the .gitmodules change and run git pull --all in the ungoogled-chromium submodule directory followed by git reset --hard ce036275d9d21a8408ef48ee9839b3c21b8448ca to change the version to .64

[AssassinK786]

Change the .gitmodules file to point to the current ungoogled-chromium repo, then initialize the submodules with git submodule update --init --recursive. If you've already initialized the submodules, then do the .gitmodules change and run git pull --all in the ungoogled-chromium submodule directory followed by git reset --hard ce036275d9d21a8408ef48ee9839b3c21b8448ca to change the version to .64

This didn't worked for me

[SugaryHull]

Since Debian 12 is out now, I decided to give maintaining ungoogled-chromium-debian for Debian Stable another shot. It looks like the package list for Jammy is the same in Bookworm. Currently, the pdfium and sql patches need to be updated, so I've stubbed those out of the series file for the time being to see if the latest ungoogled-chromium will even build.

[networkException]

Perhaps #328 could be of interest to you

[SugaryHull]

The build errored out, but I got over 100 MiB worth of warning text that I can't wade through. Is there some way to remove the -Wunknown-attributes compile flag within the debian-specific packaging?

[SugaryHull]

It looks like Debian has a patch that reverts clang::always_inline, which appears to be causing all of those warnings on Clang 14.

[SugaryHull]

I got it to build with two more fixes from Debian. Do you want me to work on fixing the SQL and pdfium patches for Chromium 114?

[AssassinK786]

So what is issue with maintaining the debian version @SugaryHull