Bug#972134: chromium: please, consider moving the package to team-maintainance to properly maintain it

2021-01-10 Thread Michael Gilbert
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 >

Bug#972134: chromium: please, consider moving the package to team-maintainance to properly maintain it

2020-12-22 Thread Michel Le Bihan
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

Bug#972134: chromium: please, consider moving the package to team-maintainance to properly maintain it

2020-12-04 Thread Gedalya
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

2020-12-03 Thread Rogério Theodoro de Brito
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

Bug#972134: chromium: please, consider moving the package to team-maintainance to properly maintain it

2020-12-02 Thread Leandro Cunha
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

Bug#972134: chromium: please, consider moving the package to team-maintainance to properly maintain it

2020-12-02 Thread Riku Voipio
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

Bug#972134: chromium: please, consider moving the package to team-maintainance to properly maintain it

2020-12-02 Thread Vincent Bernat
❦ 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

Bug#972134: chromium: please, consider moving the package to team-maintainance to properly maintain it

2020-12-01 Thread Moritz Mühlenhoff
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

Bug#972134: chromium: please, consider moving the package to team-maintainance to properly maintain it

2020-10-12 Thread Rogério Brito
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