In the past, I had something similar regarding the symlink quirk quite a few years ago where applications sometimes got the real path. You would only start noticing the bigger issue when the “rollback” history removed the last folder with the code was dead. In my case, I was using Capistrano with a PHP application before deployer was about.
I just started a project using webpack 1.X, so I had a look around to find out if they are dropping development for the 1.X versions and just focusing on 2.X but I couldn’t see anything about this.
Anyone know what the roadmap/plan is? Only thing I could find was this but it doesn’t give much information regarding previous versions.
I don’t know the answer to your actual question but I have tried migrating a v1 project to Webpack 2 the other week but the ecosystem surrounding it just wasn’t there yet - lots of the loaders and plugins I was using had odd quirks under Webpack 2 or simply didn’t work at all with the new loader configuration format. It’ll take time for the system surrounding Webpack to play catch up, hopefully the official release will step that up a gear.
Fascinating read and I learned something new about the issue with AngularJS.
The only thing that didn’t seem to sit right with me was the disclosure timeframe; the initial contact after business hours on the 24th December and then the details publicly disclosed on the 5th Jan.
I think during this time of the year it’s quite common for people to be off during this time, more so office workers. Less than two weeks over a known holiday period just doesn’t seem like the right thing to me.
It’s even a little worse than that, as he doesn’t seem to have gotten any sort of acknowledgement of receipt of the disclosure until the 28th, has no word on whether he waited to hear back from them, or about whether the vulnerability is still live.
I just had a check out of interest, and it does seem to be vulnerable still.
For example, Slackware had some users just because it had BSD-style init scripts. But since they moved to systemd, they are like any other distribution but without dependencies handling.
I was surprised to read that Slackware had moved to systemd, I had a quick google about and could see that 14.2 doesn’t have systemd and even up to the prerelease changelog do you have any more information about this at all?
Oh! It seems I have a confusion about that. Sorry, it was my error. I’ll fix it.
i guess they won’t be using systemd for a while, at least not for 14.2. i would be surprised if ever.
what was introduced in 14.2 was pulseaudio as bluez decided to drop alsa support:
Wed Jan 13 00:01:23 UTC 2016
Hey folks, happy new year!
After upgrading to BlueZ 5 recently, everything seemed to be working great,
but then it was pointed out that Bluetooth audio was no longer working.
The reason was that the newer BlueZ branch had dropped ALSA support and now
required PulseAudio. So with some trepidation, we began investigating adding
PulseAudio to Slackware. Going back to BlueZ 4 wasn’t an option with various
dependent projects either having dropped support for it, or considering doing
so. After several iterations here refining the foundation packages and
recompiling and tweaking other packages to use PulseAudio, it’s working well
and you’ll likely not notice much of a change. But if you’re using Bluetooth
audio, or needing to direct audio through HDMI, you’ll probably find it a lot
easier to accomplish that.
Best of all, we’re finally a modern, relevant Linux distro! ;-)
Thanks to Mario Preksavec, Heinz Wiesinger, and Robby Workman for a lot of
help and testing. Bug reports, complaints, and threats can go to me.
Also, enjoy a shiny new LTS 4.4.0 kernel and consider this 14.2 beta 1.