Re: DUB 0.9.22 released
Am 02.10.2014 14:27, schrieb Ben Boeckel via Digitalmars-d-announce: On Fri, Sep 26, 2014 at 06:29:19 +, Dragos Carp via Digitalmars-d-announce wrote: 1.2.3.x is an invalid version number. Only 3 group numbers are allowed [1]. Though you could use prerelease and/or build suffixes (1.2.3-0w / 1.2.3+0w). How would you version a library which wraps another with 4 version components? Enforced semver to the limit that only 3 components are supported seems a little heavy-handed to me. --Ben The idea is to have an interoperable standard - modifying it in any way would break that, so that we could as well completely invent our own standard. The way I see it is that the binding should be considered as individually versioned. It should usually start at 1.0.0 (maybe X.0.0, where X is the major version of the wrapped library, if that makes sense for the original version scheme) and be incremented purely according to SemVer. The version of the wrapped library can be documented as build metadata, but that's it. To me a big argument against supporting something non-standard, such as a fourth version digit is that it facilitates blindly adopting a libraries original version scheme, even if that may work in a completely different way w.r.t. major, minor and patch versions. But the idea of SemVer is that you can safely specify a version range such as 1.2.x and be sure to only get bugfixes, or 1.x.x and only get backwards compatible changes. Many other schemes don't have such guarantees, so directly translating them would be the a step to chaos.
Re: [OT Security PSA] Shellshock: Update your bash, now!
On Thursday, 2 October 2014 at 11:12:12 UTC, Kagamin wrote: On Thursday, 2 October 2014 at 07:43:54 UTC, eles wrote: update-manager -d It works. Does it perform package upgrade? The comments are rather scary: --- Hi, I have installed Linux mint 15 with Mint4Win as Dual boot with Windows 7. Then upgraded it to Mint 16 and it was running fine. But when I upgrade to Mint 17 (Qiana), after restarting the partition loop0 (or loopback0 or something like that) fails to load. It shows an error like, Press I to ignore, S to skip or M for manual recovery. Hi, A bit of news here, as just updated my knoledge about Linux Mint Linux Mint Debian Edition. In short, from this discussion and its comments: http://segfault.linuxmint.com/2014/08/upcoming-lmde-2-to-be-named-betsy/ Linux Mint Debian abandons its (semi-)rolling model and will basically become just a kind of Ubuntu, but based on Debian Stable (Ubuntu, AFAIK, is based on Debian Unstable). The will require full-upgrades every 2 years, but the upgrades shall be smooth (no reinstall required). For two years, you will not need to do such upgrade, just the basic security upgrades and some updates (mainly browser and email clients). Linux Mint, starting from version 17, marks a departure from previous releases (this is why you migh have encountered difficulties in upgrading) by keeping the same code base (Ubuntu 14.04 LTS) for the next 5 years. So, during this time, it will basically be a rolling-distribution, as some software will get updated just as regular (security fixes etc.) happens. Probably, after those 5 years, they will change the code base to the next Ubuntu LTS, which will start a new 5-years long upgrade. One piece of advice: Debian Testing might seem (by the name) more secure than Debian Unstable. The truth is that the latter is more up-to-date and receives security fixes first (they are entering the Debian Unstable first, then they are pre-validated before going in Debian Testing). More, Debian Unstable is not as unstable as its name might tell but, yes, it requires you messing sometimes (read: maybe once every three months) with the apt-get and vim. But is not such a big deal.
Re: SDC-32bit
I just updated my fork. https://github.com/UplinkCoder/sdc32-experimental * test0037 passes now meaning that alias works in more cases * I implemented foreach for Arrays though since ArrayLiterals are currently not supported this is not too helpful.
Re: [OT Security PSA] Shellshock: Update your bash, now!
On 10/01/2014 04:50 PM, Nick Sabalausky wrote: On 10/01/2014 01:38 PM, Iain Buclaw via Digitalmars-d-announce wrote: One nice thing about Ubuntu is that they even give you access to future kernel versions through what they call HWE. In short, I can run a 14.04 LTS kernel on a 12.04 server, so that I'm able to use modern hardware and take advantage of software that uses features of Linux that are actively worked on (like LXC) on an older software stack. Is there anything similar in Debian? Debian Backports: backports.debian.org -- Paul O'Neil Github / IRC: todayman
Re: [OT Security PSA] Shellshock: Update your bash, now!
On Friday, 3 October 2014 at 11:25:59 UTC, eles wrote: Debian and Debian-based asks you to confirm file overwrite (usually, the diff is displayed too). Isn't it the same package manager? It should be able to do the same on mint. Or may be fstab can be copied somewhere and then back at some point? On Sunday, 5 October 2014 at 08:54:46 UTC, eles wrote: Linux Mint, starting from version 17, marks a departure from previous releases (this is why you migh have encountered difficulties in upgrading) by keeping the same code base (Ubuntu 14.04 LTS) for the next 5 years. So, during this time, it will basically be a rolling-distribution, as some software will get updated just as regular (security fixes etc.) happens. Truly rolling or only security updates? Well, I'm ok with a fresh install. But can it run under the target linux itself? Or rather what to run from the disk? Since mint4win installation is a virtual disk, I'm not sure the installer will find it gracefully, they're usually partition-oriented. Not sure if this eliminates problem with fstab though.
Re: [OT Security PSA] Shellshock: Update your bash, now!
On Sunday, 5 October 2014 at 21:13:01 UTC, Kagamin wrote: On Friday, 3 October 2014 at 11:25:59 UTC, eles wrote: Debian and Debian-based asks you to confirm file overwrite (usually, the diff is displayed too). Isn't it the same package manager? It should be able to do the same on mint. Or may be fstab can be copied somewhere and then back at some point? It should be the same, but I am never sure about the homegrown patches that the Mint team applies (for example, they applied that patch that presents update packs). Truly rolling or only security updates? Actually, a kind of releases, every 6 months, but that only comes down to updating the Mint plug-ins and a selected handful of programs (probably, browser, update manager and e-mail clients). There is no much difference wrt a rolling release, because the code base does not change. Basically, the releases will be nothing else that some glorified update packs, so basically the same that LMDE does today. Call it a semi-rolling. At least this is my understanding of it. Well, I'm ok with a fresh install. My advice is to wait a bit for the new LMDE to get out. Installing LMDE now as the current model approaches its end of life is not the best, since mostly sure, you'll have to do it again since they change the code base (from testing to stable). But can it run under the target linux itself? Or rather what to run from the disk? Since mint4win installation is a virtual disk, I'm not sure the installer will find it gracefully, they're usually partition-oriented. Not sure if this eliminates problem with fstab though. Sorry, I have no direct experience with Mint directly, I extrapolate my understanding of other distribution to it, from the comments. Could not answer to those questions as they require first-hand experience. Anyway, if you feel a bit adventurous, the current LMDE model is somewhat continued by a distribution called SolidXK (google it) and a new-comer on the scene is Tranglu, that I just installed in a VM and which looks very promising (a mix of Debian Stable, Testing and Unstable, release-style, but hopefully with undisruptive upgrades).
