3 ms·
The biggest thing was that SlackBuilds weren't being updated for the new release. There was also some unfriendliness in the mailing list related to getting it f
by bachmeier 11y ago
The biggest thing was that SlackBuilds weren't being updated for the new release. There was also some unfriendliness in the mailing list related to getting it fixed (in general, nothing I experienced). I don't remember exactly what it was though. This was quite a while back - probably 13.1 or 13.37.
- jsizz 11y agoThanks. FYI, for the upcoming 14.2 release we have an officially unofficial repo with hundreds of fixes for 14.2 ready to go (and hundreds more needed). I'll admit I get a little tetchy when people insist on telling me 'xxx is broken on -current' when I already know exactly which 400+ packages are broken, and when everybody should understand that -current is for beta testers.