Debian convert script #338
Replies: 4 comments 2 replies
-
Build completed without issue |
Beta Was this translation helpful? Give feedback.
-
Ah, I thought it might be The intent is that the conversion supports any of the current Debian packagings of Chromium: unstable, stable, and oldstable. In practice, I am currently only staying on top of unstable, because that is what is used for the XtraDeb package. The variable only needs to be set when there is a difference in how the patches between Debian and u-c are reconciled, as compared to unstable. (To be more specific, when a different value of |
Beta Was this translation helpful? Give feedback.
-
On Wed, 2024-07-24 at 18:45 +0000, Daniel Richard G. wrote:
Hi @debmint,
Note that DEBIAN_STABLE is only relevant when you are building
ungoogled-chromium. If it builds fine, and you didn't set the
variable, then you didn't need to set it. (If you did, it would have
been due to a very obvious patch conflict prior to the main build.)
I can't comment on the run-time messages, other than to note that
they are generally not intended for "end user" consumption. Check to
see if the browser is working correctly first, and if something is
wrong, then look in the messages for a clue. It's not necessarily
practical, or even possible, to make the browser run without any
complaints.
Haven't run it through its paces yet, but I did try a few sites and it
seemed to work alright. The main reason I wanted a native install
rather than a flatpak was that I depend on keepassxc to handle my
passwords and it's hard, if not impossible to get them to communicate.
I tried to do a passkey login on github with UC and it workeds without
a snag.
Thank you for your considerate response.
|
Beta Was this translation helpful? Give feedback.
-
On running "find" on this directory, it only occurs twice - both times
in the Makefile. One place it is defined (currently commented out),
and the in an ifdef, but there is nothing inside it, except for a
commented-out statement. So at this time, uncommenting it would have
no effect whatsoever. Thank you again for your consideration.
…On Wed, 2024-07-24 at 18:45 +0000, Daniel Richard G. wrote:
Hi @debmint,
Note that DEBIAN_STABLE is only relevant when you are building
ungoogled-chromium. If it builds fine, and you didn't set the
variable, then you didn't need to set it. (If you did, it would have
been due to a very obvious patch conflict prior to the main build.)
I can't comment on the run-time messages, other than to note that
they are generally not intended for "end user" consumption. Check to
see if the browser is working correctly first, and if something is
wrong, then look in the messages for a clue. It's not necessarily
practical, or even possible, to make the browser run without any
complaints.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you were mentioned.Message ID:
<ungoogled-software/ungoogled-chromium-debian/repo-
***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
@iskunk
(Continuing from #336)
I was able to get the script working and the build to start. I had previously overlooked the DEBIAN_STABLE parameter in the Makefile. Leaving it commented out caused some issues with the resulting source code when I went to build it.
Beta Was this translation helpful? Give feedback.
All reactions