Bug#972134: chromium: please, consider moving the package to team-maintainance to properly maintain it
On Tue, Dec 22, 2020 at 3:45 AM Michel Le Bihan wrote: > I my NMU 87.0.4280.88-0.2 has just been uploaded to unstable and I'm > interested in joining and helping with the package. My work is in > https://salsa.debian.org/mimi8/chromium/ . Please also see the > discussion under > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973848 . Hi Michel, Thank you for helping out with the package over the past couple months. Clearly I have not had time lately. I just added you to the salsa group. Please feel free to add yourself as an uploader. Best wishes, Mike
Bug#972134: chromium: please, consider moving the package to team-maintainance to properly maintain it
Hello, I my NMU 87.0.4280.88-0.2 has just been uploaded to unstable and I'm interested in joining and helping with the package. My work is in https://salsa.debian.org/mimi8/chromium/ . Please also see the discussion under https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973848 . Michel Le Bihan
Bug#972134: chromium: please, consider moving the package to team-maintainance to properly maintain it
Opened an issue with ungoogled-chromium to discuss this on their end. https://github.com/ungoogled-software/ungoogled-chromium-debian/issues/184
Bug#972134: chromium: please, consider moving the package to team-maintainance to properly maintain it
First of all, thank you for including me on replies. Regarding the subject, I think that the best way to proceed would be to, essentially, create a task force to maintain chromium properly. I don't think that I have the computational means to compile chromium frequently (I hope that using ccache and/or distcc can be used), but I may be interested in, participating in the effort. That being said, I think that inviting other people would be the way to go, including the maintainers from Linux Mint, and other distributions. There are other people maintaining chromium forks out there, IIRC, like a project called de-googled chromium, or something like that. Inviting all those people in a task force and working openly (and with redundant human resources) is, IMVHO, something desired, not only for chromium, but for other software. Since you mentioned armhf, Riku, we may try to get people from raspbian and other downstreams to also take part. Also, given enough hands, splitting components/vendored libraries that chromium quite possibly includes (like the last time that I checked) could be something desired for, say, security purposes and, also, for other teams (IIRC, there is a bunch of multimedia libraries that were vendored). (Of course, the "de-vendoring" should occur only when feasible). That is my vision of how the packaging could go forward. Thanks, Rogério Brito. -- Sent from my Android device with K-9 Mail. Please excuse my brevity.
Bug#972134: chromium: please, consider moving the package to team-maintainance to properly maintain it
Hi, Is there any dependency that needs to be packaged for the package to be updated? I remember seeing on the tracker that there are packages in python2 that according to a Debian Developer told me that it is not being allowed to enter the official repositories. The number of CVEs continues to rise. I would be happy to help.
Bug#972134: chromium: please, consider moving the package to team-maintainance to properly maintain it
Hi, On Wed, Dec 02, 2020 at 09:41:01AM +0100, Vincent Bernat wrote: > ❦ 1 décembre 2020 22:28 +01, Moritz Mühlenhoff: > > Michael has been heroically keeping up with this beast of a codebase for > > years, > > but we clearly need a broader base to sustain it going forward. > In the past, it was team-maintained. I don't remember exactly, but I > think there was a disagreement between Michael and Riku over > some items, including collaborating on the git repository. Maybe Riku > can reconsider helping with Chromium? Chromium is a team effort.. ..in that Michael takes (took?) care of most things and I focus on keeping chromium working on armhf/arm64. I really appreceate all the work Michael has done on chromium despite that often rather harrasive mails from endusers. I don't think I'm stoic enough to become the main maintainer for chromium. Regards, Riku
Bug#972134: chromium: please, consider moving the package to team-maintainance to properly maintain it
❦ 1 décembre 2020 22:28 +01, Moritz Mühlenhoff: > Michael has been heroically keeping up with this beast of a codebase for > years, > but we clearly need a broader base to sustain it going forward. In the past, it was team-maintained. I don't remember exactly, but I think there was a disagreement between Michael and Riku over some items, including collaborating on the git repository. Maybe Riku can reconsider helping with Chromium? -- Make the coupling between modules visible. - The Elements of Programming Style (Kernighan & Plauger)
Bug#972134: chromium: please, consider moving the package to team-maintainance to properly maintain it
On Tue, Oct 13, 2020 at 12:32:28AM -0300, Rogério Brito wrote: > Currently, the way that chromium is being maintained is far from the > standards that we expect in Debian. > > A considerable number of reasonable bug reports (like, for instance the one > for enabling sharing one's desktop in this age of pandemic and many people > having to work from home) are not answered or ignored. > > Besides that, there is a skeleton of a version 84 in the repo, but the > package manager (and https://packages.debian.org/search?keywords=chromium) > doesn't know about it. > > Going even further, Google Chrome (which I really, really don't want to > install on my systems) is already at version 86 according to both > https://en.wikipedia.org/wiki/Google_Chrome_version_history and > https://chromereleases.googleblog.com/2020/10/stable-channel-update-for-desktop_12.html > > Furthermore, https://tracker.debian.org/pkg/chromium lists, at this moment, > 100 security issues in sid, buster and bullseye. > > Honestly, if one can't keep up with updates to their packages, at least make > a call for a group of buddy developers to help (the package tracker doesn't > show any kind of RFH bug open) or find someone else that is willing to > maintain the package. I'm raising this bug to RC severity, we should only include Chromium in Bullseye if we have more maintainence person power available to make sure it gets updated in unstable and stable in a timely manner Michael has been heroically keeping up with this beast of a codebase for years, but we clearly need a broader base to sustain it going forward. Cheers, Moritz
Bug#972134: chromium: please, consider moving the package to team-maintainance to properly maintain it
Package: chromium
Version: 83.0.4103.116-3.1
Severity: wishlist
Currently, the way that chromium is being maintained is far from the
standards that we expect in Debian.
A considerable number of reasonable bug reports (like, for instance the one
for enabling sharing one's desktop in this age of pandemic and many people
having to work from home) are not answered or ignored.
Besides that, there is a skeleton of a version 84 in the repo, but the
package manager (and https://packages.debian.org/search?keywords=chromium)
doesn't know about it.
Going even further, Google Chrome (which I really, really don't want to
install on my systems) is already at version 86 according to both
https://en.wikipedia.org/wiki/Google_Chrome_version_history and
https://chromereleases.googleblog.com/2020/10/stable-channel-update-for-desktop_12.html
Furthermore, https://tracker.debian.org/pkg/chromium lists, at this moment,
100 security issues in sid, buster and bullseye.
Honestly, if one can't keep up with updates to their packages, at least make
a call for a group of buddy developers to help (the package tracker doesn't
show any kind of RFH bug open) or find someone else that is willing to
maintain the package.
Thanks,
Rogério Brito.
-- System Information:
Debian Release: bullseye/sid
APT prefers testing
APT policy: (500, 'testing'), (200, 'unstable'), (150, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 5.8.0-2-amd64 (SMP w/4 CPU threads)
Kernel taint flags: TAINT_FIRMWARE_WORKAROUND
Locale: LANG=en_US.UTF-8, LC_CTYPE=pt_BR.UTF-8 (charmap=UTF-8),
LANGUAGE=en_US.UTF-8
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages chromium depends on:
ii chromium-common 83.0.4103.116-3.1
ii libasound2 1.2.3.2-1
ii libatk-bridge2.0-0 2.38.0-1
ii libatk1.0-0 2.36.0-2
ii libatspi2.0-02.38.0-2
ii libavcodec58 7:4.3.1-4
ii libavformat587:4.3.1-4
ii libavutil56 7:4.3.1-4
ii libc62.31-3
ii libcairo21.16.0-4
ii libcups2 2.3.3-3
ii libdbus-1-3 1.12.20-1
ii libdrm2 2.4.102-1
ii libevent-2.1-7 2.1.12-stable-1
ii libexpat12.2.10-1
ii libflac8 1.3.3-1
ii libfontconfig1 2.13.1-4.2
ii libfreetype6 2.10.2+dfsg-3
ii libgbm1 20.1.9-1
ii libgcc-s110.2.0-13
ii libgdk-pixbuf2.0-0 2.40.0+dfsg-5
ii libglib2.0-0 2.66.0-2
ii libgtk-3-0 3.24.23-2
ii libharfbuzz0b2.6.7-1
ii libicu67 67.1-4
ii libjpeg62-turbo 1:2.0.5-1.1
ii libjsoncpp1 1.7.4-3.1
ii liblcms2-2 2.9-4+b1
ii libminizip1 1.1-8+b1
ii libnspr4 2:4.28-1
ii libnss3 2:3.56-1
ii libopenjp2-7 2.3.1-1
ii libopus0 1.3.1-0.1
ii libpango-1.0-0 1.46.2-1
ii libpangocairo-1.0-0 1.46.2-1
ii libpng16-16 1.6.37-3
ii libpulse013.0-5
ii libre2-8 20201001+dfsg-1
ii libsnappy1v5 1.1.8-1
ii libstdc++6 10.2.0-13
ii libvpx6 1.8.2-1
ii libwebp6 0.6.1-2+b1
ii libwebpdemux20.6.1-2+b1
ii libwebpmux3 0.6.1-2+b1
ii libx11-6 2:1.6.12-1
ii libx11-xcb1 2:1.6.12-1
ii libxcb-dri3-01.14-2
ii libxcb1 1.14-2
ii libxcomposite1 1:0.4.5-1
ii libxcursor1 1:1.2.0-2
ii libxdamage1 1:1.1.5-2
ii libxext6 2:1.3.3-1+b2
ii libxfixes3 1:5.0.3-2
ii libxi6 2:1.7.10-1
ii libxml2 2.9.10+dfsg-6
ii libxrandr2 2:1.5.1-1
ii libxrender1 1:0.9.10-1
ii libxslt1.1 1.1.34-4
ii libxss1 1:1.2.3-1
ii libxtst6 2:1.2.3-1
ii zlib1g 1:1.2.11.dfsg-2
Versions of packages chromium recommends:
ii chromium-sandbox 83.0.4103.116-3.1
Versions of packages chromium suggests:
pn chromium-driver
pn chromium-l10n
pn chromium-shell
Versions of packages chromium-common depends on:
ii x11-utils 7.7+5
ii xdg-utils 1.1.3-2
Versions of packages chromium-common recommends:
ii chromium-sandbox83.0.4103.116-3.1
ii fonts-liberation1:1.07.4-11
ii libgl1-mesa-dri 20.1.9-1
pn libu2f-udev
ii mate-notification-daemon [notification-daemon] 1.24.1-1
ii system-config-printer 1.5.12-1
ii upower 0.99.11-2
Versions of packages chromium-sandbox depends on:
ii libc6 2.31-3
-- no debconf information
--
Rogério Brito : rbrito@{ime.usp.br,gmail.com} : GPG key 4096R/BCFC
http://cynic.cc/blog/ : github.com/rbrito : profiles.google.com/rbrito
DebianQA: http://qa.debian.org/developer.php?login=rbrito%40ime.usp.br
