updating packagers' info (patches etc)

18 views
Skip to first unread message

Paweł Hajdan, Jr.

unread,
Mar 19, 2018, 5:59:02 PM3/19/18
to chromium-...@chromium.org
From some recent threads (example) looks like it'd be useful to share some patches more.

It may also be an interesting idea to link to bug trackers - at least I check out other distros' trackers out of curiosity from time to time.

Please consider checking if https://chromium.googlesource.com/chromium/src/+/master/docs/linux_chromium_packages.md is up-to-date for your distro.

Feel free to upload CLs to update it, and if you prefer I could also update it for you.

Paweł

Tomáš Popela

unread,
Mar 20, 2018, 5:10:45 AM3/20/18
to chromium-packagers
I've updated the information for Fedora - https://chromium-review.googlesource.com/970244

Dne pondělí 19. března 2018 22:59:02 UTC+1 Paweł Hajdan, Jr. napsal(a):

Olivier Tilloy

unread,
Mar 20, 2018, 6:28:04 AM3/20/18
to Paweł Hajdan, Jr., chromium-...@chromium.org
Here's the updated info for Ubuntu:
https://chromium-review.googlesource.com/c/chromium/src/+/970464

Thanks for bringing this to my attention!

Olivier

Tomáš Chvátal

unread,
Mar 21, 2018, 11:12:01 AM3/21/18
to chromium-...@chromium.org
I wonder how I should update the openSUSE informations to fit in...

We have 3 packages:

For all 3 there might be different patches inlined in the same links. And as interesting path we always have latest package buildlog on newest rolling release [1], I always put there the latest snapshot even if it fails to build so others can see its "progress".

Also we at SUSE backport stuff to GCC7 currently to make sure the 65 builds with the compiler (the same can't be said for 66 where there is currently bug in GCC [2]).
For 67 -dev channel I could not get it to start produce something yet, but I dunno if I will have more time to prod it before Sunday...

Cheers

Tom



--
You received this message because you are subscribed to the Google Groups "chromium-packagers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to chromium-packagers+unsub...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/chromium-packagers/CAATLsPZMeBBmc3fSSBT5rSAkLwZY924HWObd_Ap2RQ4Sha2Mgg%40mail.gmail.com.

Timo Gurr

unread,
Mar 21, 2018, 11:31:05 AM3/21/18
to chromium-packagers

Raphael Kubo da Costa

unread,
Mar 21, 2018, 12:09:12 PM3/21/18
to Tomáš Chvátal, chromium-...@chromium.org
Tomáš Chvátal <tomas....@gmail.com> writes:

> I wonder how I should update the openSUSE informations to fit in...
>
> We have 3 packages:
> https://build.opensuse.org/package/show/network:chromium/chromium
> https://build.opensuse.org/package/show/network:chromium/chromium-beta
> https://build.opensuse.org/package/show/network:chromium/chromium-dev
>
> For all 3 there might be different patches inlined in the same links. And
> as interesting path we always have latest package buildlog on newest
> rolling release [1], I always put there the latest snapshot even if it
> fails to build so others can see its "progress".

Personally I'd just add the links to the stable package to follow what
other distros seem to do there (alternatively, I guess you could link to
all the different packages by using some short words in Markdown).

> (the same can't be said for 66 where there is currently bug in GCC
> [2]).

Looking at the bug, I think it's a duplicate of
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70431, which was worked
around in master via
https://chromium-review.googlesource.com/c/chromium/src/+/944403
Reply all
Reply to author
Forward
0 new messages