Sorry, you need to enable JavaScript to visit this website.

Primary tabs

Linux Mint 17 based on ubuntu 14.04 fails in identifying distribution step.

18 posts / 0 new
01 Staff's picture
01 Staff (not verified)

Nov 29, 2014 - 04:13pm

  • fledermaus's picture
    fledermaus (not verified)

    It boils down to resources available: We have a small team and a fairly
    tight schedule, and we're required to do a certain amount of QA on each
    distribution we officially release for. In an ideal world we'd be able to
    support more, but we have to do what we reasonably can with what
    we've got available.

    Jan 06, 2015 - 06:46am
  • famewolf's picture
    famewolf (not verified)

    I understand your point but again it takes about 12 lines of code to put in an override switch, case statement whatever to allow the user to pass a parm and override the "auto detection".  This would not only allow other distro's to use the installer but allow it to be used by newer versions of some distro's where the base compatability is the same.  ie Linux Mint is sticking to ubuntu 14.04 for now.  Both Linux Mint 17 and 17.1 as well as the next several future releases will all be based on 14.04. 

    Jan 06, 2015 - 10:45am
  • fledermaus's picture
    fledermaus (not verified)

    It's not really the amount of code, I agree it would be easy to add that: It's
    that we're required to only release what we've tested: There's a long set
    of tests and different hardware configurations that we have to try for each
    distribution supported - we are simply not allowed to release something
    that hasn't gone through that (and that's just here, after we're done with it
    it goes to a separate QA team for even more gruelling testing).

    So yes, I could easily hack up a copy that would allow people to override the
    OS detection - but no, I could never get that signed off for release.

    I appreciate that you want the updated stack: the best advice I can offer
    here is that if you're comfortable with editing your apt sources, you can do
    that directly and install the packages with apt or aptitude or software-center
    or whatever: That will always work if the packages are compatible as we
    always try to make well-formed packages: We're not trying to replace any of
    the system packaging tools, just make things easier for people who aren't
    comfortable with that level of configuration of their systems.

    Jan 12, 2015 - 10:07am
  • yuvi's picture
    yuvi (not verified)

    Can't you add a warning label next to the switch? Like a "use at your own risk"\"only select this if you're sure you know what you are doing"?


    Also, how do we get the list of relevant packages? I don't mind using apt instead

    Jan 14, 2015 - 12:41pm
  • famewolf's picture
    famewolf (not verified)




    See my reply posted below.  I somehow attached the reply to the wrong message.

    Jan 14, 2015 - 01:59pm
  • fledermaus's picture
    fledermaus (not verified)

    The whole point of the installer is to provide upgrades for
    people who _aren't_ comfortable with that sort of thing. If
    you want the package list, you can extract it here:

    Jan 19, 2015 - 07:58am
  • manima's picture
    manima (not verified)

    Again, thanks for your support famewolf, I will check the site for instructions and change the repo to 14.04.

    Jan 05, 2015 - 04:13pm
  • famewolf's picture
    famewolf (not verified)

    The correct fix is not not use their installer at all since they are adding code that cripples it  (a very bad coding practice imho).   Use the article manima posted and change the version from 13.10 to 14.04 where appropriate.



    After you add the source and do an update when you tell it to install (the name is in the article) it will list all the required packages although I don't recall it really needing any dependencies that are not already installed.

    Jan 14, 2015 - 01:57pm