Page 1 of 2 12 LastLast
Results 1 to 10 of 13

Thread: Why are some saucy packages newer than trusty packages?

  1. #1
    Join Date
    Oct 2010
    Beans
    259

    Why are some saucy packages newer than trusty packages?

    Currently Firefox for saucy: http://packages.ubuntu.com/de/saucy/firefox (26.0+build2-0ubuntu0.13.10.2)
    And for trusty: http://packages.ubuntu.com/de/trusty/firefox (25.0+build3-0ubuntu0.13.10.1)

    Interestingly this is also not the first time and seems not to be very rare. I have here just the same opinion as in the extras-repository thread: Maybe it would be the best if a package of a development release points to the previous release if it has a newer package. But such a behavior must be implemented first (if this feature doesn't already exist).

  2. #2
    Join Date
    Jun 2007
    Beans
    14,208

    Re: Why are some saucy packages newer than trusty packages?

    re: firefox
    $ apt-cache policy firefox
    firefox:
    Installed: 26.0~b6+build1-0ubuntu1
    Candidate: 26.0+build2-0ubuntu2
    Version table:
    26.0+build2-0ubuntu2 0
    500 http://mirror.cs.umn.edu/ubuntu/ trusty-proposed/main amd64 Packages
    *** 26.0~b6+build1-0ubuntu1 0
    100 /var/lib/dpkg/status
    25.0+build3-0ubuntu0.13.10.1 0
    500 http://mirror.cs.umn.edu/ubuntu/ trusty/main amd64 Packages

  3. #3
    Join Date
    Oct 2010
    Beans
    259

    Re: Why are some saucy packages newer than trusty packages?

    Code:
    sworddragon@ubuntu:~$ apt-cache policy firefox
    firefox:
      Installed: 26.0+build2-0ubuntu0.13.10.2
      Candidate: 26.0+build2-0ubuntu0.13.10.2
      Version table:
     *** 26.0+build2-0ubuntu0.13.10.2 0
            500 http://archive.ubuntu.com/ubuntu/ saucy-updates/main amd64 Packages
            500 http://security.ubuntu.com/ubuntu/ saucy-security/main amd64 Packages
            100 /var/lib/dpkg/status
         25.0+build3-0ubuntu0.13.10.1 0
            500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
         24.0+build1-0ubuntu1 0
            500 http://archive.ubuntu.com/ubuntu/ saucy/main amd64 Packages

    Firefox 26 is only available in saucy-security, saucy-updates and trusty-proposed. Now the question is why is it only in -proposed on trusty if it is declared as stable on saucy?

  4. #4
    Join Date
    Mar 2006
    Location
    Williams Lake
    Beans
    Hidden!
    Distro
    Ubuntu Development Release

    Re: Why are some saucy packages newer than trusty packages?

    Packages in proposed have nothing to do with stability problems, they are there while waiting for dependencies to catch up. If you are aware of the problems you might run into, you can still enable the proposed repositories, although it is advised not to, as it may break you system.

  5. #5
    Join Date
    Oct 2010
    Beans
    259

    Re: Why are some saucy packages newer than trusty packages?

    I know about the dependency policy which I was refering with "stable" to. But I'm still wondering why Firefox 26 on trusty has to wait for the dependencies as Firefox 26 on saucy does already fit with these (Firefox 26 on saucy can also be installed on trusty without dependency issues).

  6. #6
    Join Date
    Apr 2011
    Location
    Mystletainn Kick!
    Beans
    5,391
    Distro
    Ubuntu

    Re: Why are some saucy packages newer than trusty packages?

    Do you expect trusty to have to the same package versions as saucy?
    Probably not.
    So most likely, they're awaiting newer versions of the needed dependencies to come down the pipe.
    Splat Double Splat Triple Splat
    Earn Your Keep
    Don't mind me, I'm only passing through.
    Once in a blue moon, I'm actually helpful
    .

  7. #7
    Join Date
    May 2007
    Location
    The New Forest
    Beans
    Hidden!
    Distro
    Xubuntu Development Release

    Re: Why are some saucy packages newer than trusty packages?

    ff26 installs fine from proposed - just enable and select the 2 firefox packages

  8. #8
    Join Date
    Apr 2006
    Beans
    62

    Re: Why are some saucy packages newer than trusty packages?

    I don't know if this still apply, but I remember that Ubuntu LTS versions (i.e. 10.04) were based on Debian testing while non-LTS versions were based on Debian sid. Maybe some packages in Debian testing are still older than the Debian sid packages which Saucy used.

  9. #9
    Join Date
    Oct 2010
    Beans
    259

    Re: Why are some saucy packages newer than trusty packages?

    Quote Originally Posted by deadflowr View Post
    Do you expect trusty to have to the same package versions as saucy?
    Probably not.
    So most likely, they're awaiting newer versions of the needed dependencies to come down the pipe.
    Often the packages are identical and even if not they could use the saucy one first and replace it with the trusty one as ubuntun+1 if it is ready.


    Quote Originally Posted by ekerazha View Post
    I don't know if this still apply, but I remember that Ubuntu LTS versions (i.e. 10.04) were based on Debian testing while non-LTS versions were based on Debian sid. Maybe some packages in Debian testing are still older than the Debian sid packages which Saucy used.
    If this is true it would maybe explain this behavior.
    Last edited by Sworddragon; December 28th, 2013 at 04:44 PM.

  10. #10
    Join Date
    Jun 2010
    Location
    London, England
    Beans
    8,454
    Distro
    Ubuntu Development Release

    Re: Why are some saucy packages newer than trusty packages?

    I think that it is one thing to package an upstream application for a Ubuntu code base that was set, more or less, on release day and another thing to package that same upgrade to an application on a code base that is being changed on a daily basis. It might be possible for Firefox 26 to be packaged for Trusty as the code base now stands but what if the dependencies are broken by some package upgrade that comes in the next day or a week later? It would be like repainting the Forth bridge. A job that once finished has to be started again.

    There has been this intention for more than a year that the development branch be stable so developers could work on bringing their applications to Ubuntu on the latest code instead of waiting until release day or after. Bringing in applications like Firefox 26 too early in the development cycle could lead to perceptions that Trusty Tahr is buggy.

    Regards.
    Last edited by grahammechanical; December 28th, 2013 at 08:28 PM.
    It is a machine. It is more stupid than we are. It will not stop us from doing stupid things.
    Ubuntu user #33,200. Linux user #530,530


Page 1 of 2 12 LastLast

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •