After a timely Chromium update, I checked what version was in other Distros, and found that MX is more up-to-date than many others (and not behind Arch). This isn't a surprise, as it's one of the reasons that I use MX Linux. But it got me thinking; who built and uploaded this to the repos?
So, how about a thread/sticky/notice of who does what in the dev team? Or is there one already that has escaped my notice? There's a great deal of work goes on in the background to maintain a Distro... might be good to publicise more those that beaver-away in the background
Who does what?
Who does what?
Chris
MX 18 MX 19 - Manjaro
MX 18 MX 19 - Manjaro
Re: Who does what?
There's a gross overview on the Home page, About Us
Production: 5.10, MX-23 Xfce, AMD FX-4130 Quad-Core, GeForce GT 630/PCIe/SSE2, 16 GB, SSD 120 GB, Data 1TB
Personal: Lenovo X1 Carbon with MX-23 Fluxbox and Windows 10
Other: Raspberry Pi 5 with MX-23 Xfce Raspberry Pi Respin
Personal: Lenovo X1 Carbon with MX-23 Fluxbox and Windows 10
Other: Raspberry Pi 5 with MX-23 Xfce Raspberry Pi Respin
Re: Who does what?
Thanks, Jerry - you can delete this pointless thread now
Chris
MX 18 MX 19 - Manjaro
MX 18 MX 19 - Manjaro
Re: Who does what?
Ah, but the devil's in the details!
Production: 5.10, MX-23 Xfce, AMD FX-4130 Quad-Core, GeForce GT 630/PCIe/SSE2, 16 GB, SSD 120 GB, Data 1TB
Personal: Lenovo X1 Carbon with MX-23 Fluxbox and Windows 10
Other: Raspberry Pi 5 with MX-23 Xfce Raspberry Pi Respin
Personal: Lenovo X1 Carbon with MX-23 Fluxbox and Windows 10
Other: Raspberry Pi 5 with MX-23 Xfce Raspberry Pi Respin
Re: Who does what?
Debian is currently keeping Chromium backported in their stable repos, because of security holes in older versions and the difficulty of backporting the fixes. Packages that they make an exception for the "no newer versions" policy because of those concerns are called "leaf" packages, and another example are the recent VLC 3.02 and 3.0.3 upgrades. We were doing our own backports of VLC before, but Debian made those obsolete.
We do have a thread where the packagers can post what they're working on, or there's this page: http://mxrepo.com/ though it should be updated for the dropping of MX 14 and MEPIS 12 support.
You can tell where they from by looking at the end of the version.
The "deb9u1" means that it's update 1 for Debian 9. You can also see which repo it came from with that command. MX packages should have "mx" somewhere in the version, though an exception can be made for native MX programs such as MX Tools.
AntiX doesn't seem to add suffixes to the version, so you'd have to look at the repository listing instead.
We do have a thread where the packagers can post what they're working on, or there's this page: http://mxrepo.com/ though it should be updated for the dropping of MX 14 and MEPIS 12 support.
You can tell where they from by looking at the end of the version.
Code: Select all
$ apt policy chromium
chromium:
Installed: 68.0.3440.75-1~deb9u1
Candidate: 68.0.3440.75-1~deb9u1
Version table:
*** 68.0.3440.75-1~deb9u1 500
500 http://security.debian.org stretch/updates/main amd64 Packages
100 /var/lib/dpkg/status
63.0.3239.84-1~deb9u1 500
500 http://ftp.us.debian.org/debian stretch/main amd64 Packages
AntiX doesn't seem to add suffixes to the version, so you'd have to look at the repository listing instead.
Re: Who does what?
Pretty sure Stevo posted in the wrong thread...
Production: 5.10, MX-23 Xfce, AMD FX-4130 Quad-Core, GeForce GT 630/PCIe/SSE2, 16 GB, SSD 120 GB, Data 1TB
Personal: Lenovo X1 Carbon with MX-23 Fluxbox and Windows 10
Other: Raspberry Pi 5 with MX-23 Xfce Raspberry Pi Respin
Personal: Lenovo X1 Carbon with MX-23 Fluxbox and Windows 10
Other: Raspberry Pi 5 with MX-23 Xfce Raspberry Pi Respin
Re: Who does what?
I think he's saying; "it wasn't us, it was Debian that supplied the update to Chromium". So I should have checked apt before using it as an example
EDIT: I forgot to say thanks to @Stevo for the detailed info
Chris
MX 18 MX 19 - Manjaro
MX 18 MX 19 - Manjaro
Re: Who does what?
Yes, that's what I was replying to.
Deb-multimedia also adds "dmo" to their versioning, and having one of those show up in installed packages often is the first clue to why someone's multimedia playback has gone south.