For interesting topics. But remember this is a Linux Forum. Do not post offensive topics that are meant to cause trouble with other members or are derogatory towards people of different genders, race, color, minors (this includes nudity and sex), politics or religion. Let's try to keep peace among the community and for visitors.
No spam on this or any other forums please! If you post advertisements on these forums, your account may be deleted.
Do not copy and paste entire or even up to half of someone else's words or articles into posts. Post only a few sentences or a paragraph and make sure to include a link back to original words or article. Otherwise it's copyright infringement.
You can talk about other distros here, but no MX bashing. You can email the developers of MX if you just want to say you dislike or hate MX.
Bits from the Release Team: frozen hard to get hot
Hi all,
According to schedule, we froze bullseye a bit more last week (12-03-2021). This means that we are one step closer to the release of bullseye and we expect everyone to follow the freeze policy [1]. This means that from now on key packages and packages without significant autopkgtest coverage need to be unblocked by the release team to be able to migrate from unstable to testing. If you need to request an unblock, check that your request is in line with the freeze policy and use $(reportbug release.debian.org) in order to get the meta data correct and get the template that helps us get the right information.
Note that packages that are not on the key-packages list, with non-superficial autopkgtests that succeed on all architectures and don't cause regressions will migrate without an unblock after 20 days. If
you're unsure about the current migration status of your package, you can check it at [3].
Now is a good time to help testing installations and upgrades to find as many issues as possible and fix rc bugs [4]. Please be aware of bug 984533 (libc6), 974552 (libcrypt1) and 953562 (libcrypt1) when you do. Add information to those bug if you can help them forward.
Please also remember to file bugs against the release-notes pseudo package if you know of issues that deserve being mentioned in the release notes. Ideally with proposed text, or even via a merge request on salsa [2], but even if you can only point us at issues that's already appreciated.
On behalf of the Release Team,
Paul
Looks like things are rolling fine till date apart from some basic bugs lying unfixed for long... awaiting official release later this year!
Last edited by agnivo007 on Sun Jul 18, 2021 3:55 am, edited 2 times in total.
- Roy, Kolkata, IN. "REDUCE-REUSE-RECYCLE-REPURPOSE"MX-21-AHS-KDE on [ H110M-H : Modded BIOS | Core i3-9350K | 8GB DDR4 | SP A60 NVMe PCIe3x4 | Samsung Evo 870 SSD | WD Black Mobile HDD ]
WOW! Is all I can say guys! Well, I am sure looking forward to the Debian future! And above all, the MX LINUX future! Are there any RC iso files for MX 21 out there?
pianokeyjoe wrote: Sun Mar 28, 2021 1:11 pm
WOW! Is all I can say guys! Well, I am sure looking forward to the Debian future! And above all, the MX LINUX future! Are there any RC iso files for MX 21 out there?
not yet. I may or may not be running an early pre-alpha build now.
The release announcement does acknowledge the known issue that for the lack of providing the binary-only AMD Radeon graphics firmware many AMD graphics cards may have display issues.
- Roy, Kolkata, IN. "REDUCE-REUSE-RECYCLE-REPURPOSE"MX-21-AHS-KDE on [ H110M-H : Modded BIOS | Core i3-9350K | 8GB DDR4 | SP A60 NVMe PCIe3x4 | Samsung Evo 870 SSD | WD Black Mobile HDD ]
Meanwhile we'd be having 10.10 (all clocks read that at the timepiece shops...)
The next point release for "buster" (10.10) is scheduled for Saturday June 19th. Processing of new uploads into buster-proposed-updates will be frozen during the preceding weekend.
- Roy, Kolkata, IN. "REDUCE-REUSE-RECYCLE-REPURPOSE"MX-21-AHS-KDE on [ H110M-H : Modded BIOS | Core i3-9350K | 8GB DDR4 | SP A60 NVMe PCIe3x4 | Samsung Evo 870 SSD | WD Black Mobile HDD ]
)
