Install The Newest Firefox ppa with command "add-apt-repository" (9.10 & above)

[SilverWave]

So, ff 3.5.7 made it into the karmic repo today. that makes 3 days since mozilla release.

Well, not too bad - before, it used to be at least a week.

I think you may have missed Post 26#

Mozilla Firefox 3.5.7 out 6th. Available in ubuntu-mozilla-security Same Day!


firefox-3.0 3.0.17+nobinonly-0ubuntu0.9.04.1 Alexander Sack (2010-01-06)
firefox-3.0 3.0.17+nobinonly-0ubuntu0.8.10.1 Alexander Sack (2010-01-06)
firefox-3.0 3.0.17+nobinonly-0ubuntu0.8.04.1 Alexander Sack (2010-01-06)

firefox-3.5 3.5.7+nobinonly-0ubuntu1 Alexander Sack (2010-01-06)
firefox-3.5 3.5.7+nobinonly-0ubuntu0.9.10.1 Alexander Sack (2010-01-06)
firefox-3.5 3.5.7+nobinonly-0ubuntu0.9.04.1 Alexander Sack (2010-01-06)

And my updated help:

Latest Firefox Packages

• If you want to have them earlier, enable ubuntu-mozilla-security PPA where the bits will land first. Enabling this PPA also will help us test security updates before they get rolled to the masses in future; so if you don’t mind a slightly increased risk of breakage keep this enabled; in the unlikely event that you see a regression from this archive, instantly report them to the ubuntu mozillateam.

This is the Holy Grail for a user who just wants the updates immediately.

You just add the security ppa once and forget about it

[nanotube]

no, i didn't miss your post about the ubuntu mozilla security ppa.

i was talking about the official ubuntu repositories.

that ppa is not part of the 'official ubuntu repositories' which is what most people have in their sources.list.

further, they seem to only be tracking firefox, and not thunderbird and seamonkey.

[SilverWave]

no, i didn't miss your post about the ubuntu mozilla security ppa.

i was talking about the official ubuntu repositories.

that ppa is not part of the 'official ubuntu repositories' which is what most people have in their sources.list.

Well... I think given the people involved and that they are hosted as a ppa... that their reputation is good enough for me
Also advising on how to add a ppa to your sources.list is the focus of this How-to

further, they seem to only be tracking firefox, and not thunderbird and seamonkey.

True but "Install The Newest Firefox..." is the focus of this How-to

[SilverWave]

Note that although based on the man for apt_preferences I am altering it for my own use.
__________________

apt_preferences(5) - Linux man page

Name

apt_preferences - Preference control file for APT

Description

The APT preferences file /etc/apt/preferences.d/file can be used to control which versions of packages will be selected for installation.

Example

/etc/apt/preferences.d/ubuntu-mozilla-daily-pin-400

Package: *
Pin: release o=LP-PPA-ubuntu-mozilla-daily
Pin-Priority: 400

Make sure the file name does not have a dot in it!
ubuntu-mozilla-daily.pin < Nope!
ubuntu-mozilla-daily-pin < OK

Needs to document which files are considered below /etc/apt/preferences.d APT Bug #505880

Loïc Minier wrote on 2010-01-11: #1
This is correct; the code will skip files which start with a dot, or if it contains a character which is not alpha numeric or "-" or "_"; it will also only consider regular files for some reason (ignoring e.g. symbolic links and subdirs).
This is supposed to be some run-parts-alike filter mechanism to avoid reading editor backup files, or files leftover by the dpkg conffile mechanism.
However, this should be documented in the man page.
See the sources.list man page and the section on .list files for some example filenames (ignore the requirement of files ending in .list)

Several versions of a package may be available for installation when the sources.list(5) file contains references to more than one distribution (for example, stable and testing). APT assigns a priority to each version that is available. Subject to dependency constraints, apt-get selects the version with the highest priority for installation. The APT preferences file overrides the priorities that APT assigns to package versions by default, thus giving the user control over which one is selected for installation.

Several instances of the same version of a package may be available when the sources.list(5) file contains references to more than one source. In this case apt-get downloads the instance listed earliest in the sources.list(5) file. The APT preferences file does not affect the choice of instance, only the choice of version.

Apt's Default Priority Assignments

If there is no preferences file or if there is no entry in the file that applies to a particular version then the priority assigned to that version is the priority of the distribution to which that version belongs. It is possible to single out a distribution, "the target release", which receives a higher priority than other distributions do by default. The target release can be set on the apt-get command line or in the APT configuration file /etc/apt/apt.conf. For example,

apt-get install -t testing some-package

APT: : Default-Release "stable";

If the target release has been specified then APT uses the following algorithm to set the priorities of the versions of a package.

Assign:

priority 100
To the version that is already installed (if any).

priority 500
To the versions that are not installed and do not belong to the target release.

priority 990
To the versions that are not installed and belong to the target release.

If the target release has not been specified then APT simply assigns priority 100 to all installed package versions and priority 500 to all uninstalled package versions.

APT then applies the following rules, listed in order of precedence, to determine which version of a package to install.

• Never downgrade unless the priority of an available version exceeds 1000. ("Downgrading" is installing a less recent version of a package in place of a more recent version. Note that none of APT's default priorities exceeds 1000; such high priorities can only be set in the preferences file. Note also that downgrading a package can be risky.)
• Install the highest priority version.
• If two or more versions have the same priority, install the most recent one (that is, the one with the higher version number).
• If two or more versions have the same priority and version number but either the packages differ in some of their metadata or the --reinstall option is given, install the uninstalled one.

In a typical situation, the installed version of a package (priority 100) is not as recent as one of the versions available from the sources listed in the sources.list(5) file (priority 500 or 990). Then the package will be upgraded when apt-get install some-package or apt-get upgrade is executed.

More rarely, the installed version of a package is more recent than any of the other available versions. The package will not be downgraded when apt-get install some-package or apt-get upgrade is executed.

Sometimes the installed version of a package is more recent than the version belonging to the target release, but not as recent as a version belonging to some other distribution. Such a package will indeed be upgraded when apt-get install some-package or apt-get upgrade is executed, because at least one of the available versions has a higher priority than the installed version.

The Effect of Apt Preferences

The APT preferences file allows the system administrator to control the assignment of priorities. The file consists of one or more multi-line records separated by blank lines. Records can have one of two forms, a specific form and a general form.

• The specific form assigns a priority (a "Pin-Priority") to a specified package and specified version or version range. For example, the following record assigns a high priority to all versions of the perl package whose version number begins with "5.8".
  
  Package: perl
  Pin: version 5.8*
  Pin-Priority: 1001
• The general form assigns a priority to all of the package versions in a given distribution (that is, to all the versions of packages that are listed in a certain Release file) or to all of the package versions coming from a particular Internet site, as identified by the site's fully qualified domain name.
  
  This general-form entry in the APT preferences file applies only to groups of packages. For example, the following record assigns a high priority to all package versions available from the local site.
  
  Package: *
  Pin: origin ""
  Pin-Priority: 999
  
  A note of caution: the keyword used here is "origin". This should not be confused with the Origin of a distribution as specified in a Release file. What follows the "Origin:" tag in a Release file is not an Internet address but an author or vendor name, such as "Debian" or "Ximian".
  
  The following record assigns a low priority to all package versions belonging to any distribution whose Archive name is "unstable".
  
  Package: *
  Pin: release a=unstable
  Pin-Priority: 50
  
  The following record assigns a high priority to all package versions belonging to any release whose Archive name is "stable" and whose release Version number is "3.0".
  
  Package: *
  Pin: release a=unstable, v=3.0
  Pin-Priority: 50

How Apt Interprets Priorities

Priorities (P) assigned in the APT preferences file must be positive or negative integers. They are interpreted as follows (roughly speaking):

[1001, 1002]... P > 1000
causes a version to be installed even if this constitutes a downgrade of the package

[991 - 1000]... 990 < P <=1000
causes a version to be installed even if it does not come from the target release, unless the installed version is more recent

[501 to 990]... 500 < P <=990
causes a version to be installed unless there is a version available belonging to the target release or the installed version is more recent

[101 to 500]... 100 < P <=500
causes a version to be installed unless there is a version available belonging to some other distribution or the installed version is more recent

[001 to 100]... 0 < P <=100
causes a version to be installed only if there is no installed version of the package

[-001, -002]... P < 0
prevents the version from being installed

If any specific-form records match an available package version then the first such record determines the priority of the package version. Failing that, if any general-form records match an available package version then the first such record determines the priority of the package version.

For example, suppose the APT preferences file contains the three records presented earlier:

Package: perl
Pin: version 5.8*
Pin-Priority: 1001

Package: *
Pin: origin ""
Pin-Priority: 999

Package: *
Pin: release unstable
Pin-Priority: 50

Then:

• The most recent available version of the perl package will be installed, so long as that version's version number begins with "5.8". If any 5.8* version of perl is available and the installed version is 5.9*, then perl will be downgraded.
• A version of any package other than perl that is available from the local system has priority over other versions, even versions belonging to the target release.
• A version of a package whose origin is not the local system but some other site listed in sources.list(5) and which belongs to an unstable distribution is only installed if it is selected for installation and no version of the package is already installed.

Determination of Package Version and Distribution Properties

The locations listed in the sources.list(5) file should provide Packages and Release files to describe the packages available at that location.

The Packages file is normally found in the directory .../dists/dist-name/component/arch: for example, .../dists/stable/main/binary-i386/Packages. It consists of a series of multi-line records, one for each package available in that directory. Only two lines in each record are relevant for setting APT priorities:

The Package: line
gives the package name

The Version: line
gives the version number for the named package

The Release file is normally found in the directory .../dists/dist-name: for example, .../dists/stable/Release, or .../dists/woody/Release. It consists of a single multi-line record which applies to all of the packages in the directory tree below its parent. Unlike the Packages file, nearly all of the lines in a Release file are relevant for setting APT priorities:

The Archive: line
names the archive to which all the packages in the directory tree belong. For example, the line "Archive: stable" specifies that all of the packages in the directory tree below the parent of the Release file are in a stable archive. Specifying this value in the APT preferences file would require the line:

Pin: release a=stable

The Version: line
names the release version. For example, the packages in the tree might belong to Debian GNU/Linux release version 3.0. Note that there is normally no version number for the testing and unstable distributions because they have not been released yet. Specifying this in the APT preferences file would require one of the following lines.

Pin: release v=3.0
Pin: release a=stable, v=3.0
Pin: release 3.0

The Component: line
names the licensing component associated with the packages in the directory tree of the Release file. For example, the line "Component: main" specifies that all the packages in the directory tree are from the main component, which entails that they are licensed under terms listed in the Debian Free Software Guidelines. Specifying this component in the APT preferences file would require the line:

Pin: release c=main

The Origin: line
names the originator of the packages in the directory tree of the Release file. Most commonly, this is Debian. Specifying this origin in the APT preferences file would require the line:

Pin: release o=Debian

The Label: line
names the label of the packages in the directory tree of the Release file. Most commonly, this is Debian. Specifying this label in the APT preferences file would require the line:

Pin: release l=Debian

All of the Packages and Release files retrieved from locations listed in the sources.list(5) file are stored in the directory /var/lib/apt/lists, or in the file named by the variable Dir::State::Lists in the apt.conf file. For example, the file debian.lcs.mit.edu_debian_dists_unstable_contrib_b inary-i386_Release contains the Release file retrieved from the site debian.lcs.mit.edu for binary-i386 architecture files from the contrib component of the unstable distribution.

Optional Lines in an Apt Preferences Record

Each record in the APT preferences file can optionally begin with one or more lines beginning with the word Explanation:. This provides a place for comments.

The Pin-Priority: line in each APT preferences record is optional. If omitted, APT assigs a priority of 1 less than the last value specified on a line beginning with Pin-Priority: release ....

Examples

Tracking Stable

The following APT preferences file will cause APT to assign a priority higher than the default (500) to all package versions belonging to a stable distribution and a prohibitively low priority to package versions belonging to other Debian distributions.

Explanation: Uninstall or do not install any Debian-originated
Explanation: package versions other than those in the stable distro
Package: *
Pin: release a=stable
Pin-Priority: 900

Package: *
Pin: release o=Debian
Pin-Priority: -10

With a suitable sources.list(5) file and the above preferences file, any of the following commands will cause APT to upgrade to the latest stable version(s).

apt-get install package-name
apt-get upgrade
apt-get dist-upgrade

The following command will cause APT to upgrade the specified package to the latest version from the testing distribution; the package will not be upgraded again unless this command is given again.

apt-get install package/testing

Tracking Testing or Unstable

The following APT preferences file will cause APT to assign a high priority to package versions from the testing distribution, a lower priority to package versions from the unstable distribution, and a prohibitively low priority to package versions from other Debian distributions.

Package: *
Pin: release a=testing
Pin-Priority: 900

Package: *
Pin: release a=unstable
Pin-Priority: 800

Package: *
Pin: release o=Debian
Pin-Priority: -10

With a suitable sources.list(5) file and the above preferences file, any of the following commands will cause APT to upgrade to the latest testing version(s).

apt-get install package-name
apt-get upgrade
apt-get dist-upgrade

The following command will cause APT to upgrade the specified package to the latest version from the unstable distribution. Thereafter, apt-get upgrade will upgrade the package to the most recent testing version if that is more recent than the installed version, otherwise, to the most recent unstable version if that is more recent than the installed version.

apt-get install package/unstable

See Also

apt-get(8 ) apt-cache(8 ) apt.conf(5) sources.list(5)

Bugs

See the APT bug page http://bugs.debian.org/src:apt. If you wish to report a bug in APT, please see /usr/share/doc/debian/bug-reporting.txt or the reportbug(1) command.

Author

APT was written by the APT team <apt@packages.debian.org>.

Referenced By

apt.conf(5)

__________________

Note that although based on the man for apt_preferences I am altering it for my own use.

Useful Commands
apt-cache policy
apt-cache policy firefox-3.5

[SilverWave]

Already added this repo. My intention is to use thunderbird from here, but keep firefox in sync with current ubuntu repos. If i hold firefox, i don't get any update...is i do and update i get the firefox from this ppa.
Is there any way to do this? I mean thunderbird from ppa and firefox from official repos?

Cheers.

I think this is exactly what you are looking for:

http://www.dataforte.net/blog/2009/1...3-0-on-karmic/

Firefox 3.6 and Thunderbird 3.0 on Karmic

" I regularly use Thunderbird 3.0 betas on my Karmic via the Ubuntu Daily Mozilla PPA. Unfortunately the PPA also contains snapshot builds of Firefox 3.5 and XulRunner 1.9.1, which I want to keep at their standard Ubuntu versions. To make apt-get upgradeing as painless as possible I am using package pinning to stop unwanted packages from other repositories to override the defaults."

[EDIT]
hmm... unfortunately that does not seem to work for me.

[EDIT]
Wow what a gotcha!
Make sure the file name does not have a dot in it! APT Bug #505880
ubuntu-mozilla-daily.pin < Nope!
ubuntu-mozilla-daily-pin < OK

Although the code in the blog above does work there is an easier way to do this:

file: ubuntu-mozilla-daily-pin-400

Package: *
Pin: release o=LP-PPA-ubuntu-mozilla-daily
Pin-Priority: 400

For details see the next post...

But it does work as advertised

[SilverWave]

"I regularly use a package from the Ubuntu Daily Mozilla PPA. Unfortunately the PPA also contains snapshot builds of Firefox 3.5 and XulRunner 1.9.1, which I want to keep at their standard Ubuntu versions".

The Pinning Solution

To make apt-get upgrading as painless as possible set a lower Pin-Priority on the PPA, this will stop unwanted package versions from installing. Once set, packages from the ubuntu-mozilla-daily PPA will always lose in any contest with packages from other repositories, even if they have a higher version.

Create the file:

1. /etc/apt/preferences.d/ubuntu-mozilla-daily-pin-400
   
   
2. Add the following to the file:
   

   Package: *
   Pin: release o=LP-PPA-ubuntu-mozilla-daily
   Pin-Priority: 400

The Rules

If the target release has not been specified then APT simply assigns priority 100 to all installed package versions and priority 500 to all uninstalled package versions.

APT then applies the following rules, listed in order of precedence, to determine which version of a package to install.

• Never downgrade unless the priority of an available version exceeds 1000. ("Downgrading" is installing a less recent version of a package in place of a more recent version. Note that none of APT's default priorities exceeds 1000; such high priorities can only be set in the preferences file. Note also that downgrading a package can be risky.)
• Install the highest priority version.
• If two or more versions have the same priority, install the most recent one (that is, the one with the higher version number).
• If two or more versions have the same priority and version number but either the packages differ in some of their metadata or the --reinstall option is given, install the uninstalled one. Details.

Before Pinning

apt-cache policy

:~$ apt-cache policy
Package files:
 100 /var/lib/dpkg/status
     release a=now
 500 http://ppa.launchpad.net karmic/main Packages
     release v=9.10,o=LP-PPA-ubuntu-mozilla-security,a=karmic,n=karmic,l=PPA for Ubuntu Mozilla Security Team,c=main
     origin ppa.launchpad.net
 500 http://ppa.launchpad.net karmic/main Packages
     release v=9.10,o=LP-PPA-ubuntu-mozilla-daily,a=karmic,n=karmic,l=PPA for Ubuntu Mozilla Daily Build Team,c=main
     origin ppa.launchpad.net
 500 http://packages.medibuntu.org karmic/non-free Packages
     release v=9.10,o=Medibuntu,a=karmic,n=karmic,l=Medibuntu,c=non-free
     origin packages.medibuntu.org
 500 http://packages.medibuntu.org karmic/free Packages
     release v=9.10,o=Medibuntu,a=karmic,n=karmic,l=Medibuntu,c=free
     origin packages.medibuntu.org
 500 http://security.ubuntu.com karmic-security/multiverse Packages
     release v=9.10,o=Ubuntu,a=karmic-security,n=karmic,l=Ubuntu,c=multiverse
     origin security.ubuntu.com
 500 http://security.ubuntu.com karmic-security/universe Packages
     release v=9.10,o=Ubuntu,a=karmic-security,n=karmic,l=Ubuntu,c=universe
     origin security.ubuntu.com
 500 http://security.ubuntu.com karmic-security/restricted Packages
     release v=9.10,o=Ubuntu,a=karmic-security,n=karmic,l=Ubuntu,c=restricted
     origin security.ubuntu.com
 500 http://security.ubuntu.com karmic-security/main Packages
     release v=9.10,o=Ubuntu,a=karmic-security,n=karmic,l=Ubuntu,c=main
     origin security.ubuntu.com
 500 http://gb.archive.ubuntu.com karmic-updates/multiverse Packages
     release v=9.10,o=Ubuntu,a=karmic-updates,n=karmic,l=Ubuntu,c=multiverse
     origin gb.archive.ubuntu.com
 500 http://gb.archive.ubuntu.com karmic-updates/universe Packages
     release v=9.10,o=Ubuntu,a=karmic-updates,n=karmic,l=Ubuntu,c=universe
     origin gb.archive.ubuntu.com
 500 http://gb.archive.ubuntu.com karmic-updates/restricted Packages
     release v=9.10,o=Ubuntu,a=karmic-updates,n=karmic,l=Ubuntu,c=restricted
     origin gb.archive.ubuntu.com
 500 http://gb.archive.ubuntu.com karmic-updates/main Packages
     release v=9.10,o=Ubuntu,a=karmic-updates,n=karmic,l=Ubuntu,c=main
     origin gb.archive.ubuntu.com
 500 http://gb.archive.ubuntu.com karmic/multiverse Translation-en_GB
 500 http://gb.archive.ubuntu.com karmic/multiverse Packages
     release v=9.10,o=Ubuntu,a=karmic,n=karmic,l=Ubuntu,c=multiverse
     origin gb.archive.ubuntu.com
 500 http://gb.archive.ubuntu.com karmic/universe Translation-en_GB
 500 http://gb.archive.ubuntu.com karmic/universe Packages
     release v=9.10,o=Ubuntu,a=karmic,n=karmic,l=Ubuntu,c=universe
     origin gb.archive.ubuntu.com
 500 http://gb.archive.ubuntu.com karmic/restricted Translation-en_GB
 500 http://gb.archive.ubuntu.com karmic/restricted Packages
     release v=9.10,o=Ubuntu,a=karmic,n=karmic,l=Ubuntu,c=restricted
     origin gb.archive.ubuntu.com
 500 http://gb.archive.ubuntu.com karmic/main Translation-en_GB
 500 http://gb.archive.ubuntu.com karmic/main Packages
     release v=9.10,o=Ubuntu,a=karmic,n=karmic,l=Ubuntu,c=main
     origin gb.archive.ubuntu.com
Pinned packages:
:~$

apt-cache policy firefox-3.5

:~$ apt-cache policy firefox-3.5
firefox-3.5:
  Installed: 3.5.7+nobinonly-0ubuntu0.9.10.1
  Candidate: 3.5.8~hg20100105r26710+nobinonly-0ubuntu2~umd1~karmic
  Version table:
     3.5.8~hg20100105r26710+nobinonly-0ubuntu2~umd1~karmic 0
        500 http://ppa.launchpad.net karmic/main Packages
 *** 3.5.7+nobinonly-0ubuntu0.9.10.1 0
        500 http://gb.archive.ubuntu.com karmic-updates/main Packages
        500 http://security.ubuntu.com karmic-security/main Packages
        500 http://ppa.launchpad.net karmic/main Packages
        100 /var/lib/dpkg/status
     3.5.3+build1+nobinonly-0ubuntu6 0
        500 http://gb.archive.ubuntu.com karmic/main Packages
:~$

Pinning

/etc/apt/preferences.d/ubuntu-mozilla-daily-pin-400

Package: *
Pin: release o=LP-PPA-ubuntu-mozilla-daily
Pin-Priority: 400

After Pinning

:~$ apt-cache policy firefox-3.5
firefox-3.5:
  Installed: 3.5.7+nobinonly-0ubuntu0.9.10.1
  Candidate: 3.5.7+nobinonly-0ubuntu0.9.10.1
  Version table:
     3.5.8~hg20100105r26710+nobinonly-0ubuntu2~umd1~karmic 0
        400 http://ppa.launchpad.net karmic/main Packages
 *** 3.5.7+nobinonly-0ubuntu0.9.10.1 0
        500 http://gb.archive.ubuntu.com karmic-updates/main Packages
        500 http://security.ubuntu.com karmic-security/main Packages
        500 http://ppa.launchpad.net karmic/main Packages
        100 /var/lib/dpkg/status
     3.5.3+build1+nobinonly-0ubuntu6 0
        500 http://gb.archive.ubuntu.com karmic/main Packages
:~$

:~$ apt-cache policy
Package files:
 100 /var/lib/dpkg/status
     release a=now
 500 http://ppa.launchpad.net karmic/main Packages
     release v=9.10,o=LP-PPA-ubuntu-mozilla-security,a=karmic,n=karmic,l=PPA for Ubuntu Mozilla Security Team,c=main
     origin ppa.launchpad.net
 400 http://ppa.launchpad.net karmic/main Packages
     release v=9.10,o=LP-PPA-ubuntu-mozilla-daily,a=karmic,n=karmic,l=PPA for Ubuntu Mozilla Daily Build Team,c=main
     origin ppa.launchpad.net
[...]
 500 http://gb.archive.ubuntu.com karmic/main Packages
     release v=9.10,o=Ubuntu,a=karmic,n=karmic,l=Ubuntu,c=main
     origin gb.archive.ubuntu.com
Pinned packages:
:~$

Nice

Run "Update Manager" and check the section called "Other updates (LP-PPA-ubuntu-mozilla-daily)" to confirm all is well.

__________________

Note that the name of the file you create can not contain a dot.

Based mainly on Pin down the official Firefox version in Ubuntu and the Linux man page for apt_preferences.
With bits from Firefox 3.6 and Thunderbird 3.0 on Karmic.

[SilverWave]

APT Bug #505880

Bug Description

The APT preferences file does not work if its filename contains a dot.
/etc/apt/preferences.d/ubuntu-mozilla-daily-pin.400 < Nope!
/etc/apt/preferences.d/ubuntu-mozilla-daily-pin-400 < OK
Linux neon 2.6.31-17-generic #54-Ubuntu SMP Thu Dec 10 17:01:44 UTC 2009 x86_64 GNU/Linux
__________________
Example that works:
/etc/apt/preferences.d/ubuntu-mozilla-daily-pin-400
Code:
Package: *
Pin: release o=LP-PPA-ubuntu-mozilla-daily
Pin-Priority: 400
__________________
Notes:
The example at the link below didn't work for me:
https://wiki.ubuntu.com/MozillaTeam/PPAs
Found the problem here:
http://ubuntuforums.org/showpost.php...3&postcount=35
http://ubuntuforums.org/showpost.php...7&postcount=36

Loïc Minier on 2010-01-11
summary: - apt_preferences APT preferences filename can not contain a dot.
+ Needs to document which files are considered below
+ /etc/apt/preferences.d

Loïc Minier on 2010-01-11
Changed in apt (Ubuntu): status: New → Triaged

Loïc Minier on 2010-01-11
Changed in apt (Ubuntu): importance: Undecided → Low

Loïc Minier on 2010-01-11
Changed in apt: status: New → Confirmed

Loïc Minier wrote on 2010-01-11: #1
This is correct; the code will skip files which start with a dot, or if it contains a character which is not alpha numeric or "-" or "_"; it will also only consider regular files for some reason (ignoring e.g. symbolic links and subdirs).
This is supposed to be some run-parts-alike filter mechanism to avoid reading editor backup files, or files leftover by the dpkg conffile mechanism.
However, this should be documented in the man page.
See the sources.list man page and the section on .list files for some example filenames (ignore the requirement of files ending in .list).

[SilverWave]

Changes for the versions:
3.6~hg20100108r33503+nobinonly-0ubuntu1~umd1~karmic
3.6~hg20100117r33523+nobinonly-0ubuntu1~umd1~karmic

This change is not coming from a source that supports changelogs.

[SilverWave]

Mozilla Developer News » Blog Archive » Firefox 3.6 Release Candidate updated http://bit.ly/8L9yYn

An update to the Firefox 3.6 Release Candidate is now available. This second release candidate is available for free download and has been issued as an automatic update to all Firefox 3.6 Beta and Release Candidate users.

[SilverWave]

This is the latest 14:20 PM UK

firefox 3.6~hg20100120r33527+nobinonly-0ubuntu1~umd2~karmic Fabien Tassin (8 hours ago)
firefox-3.5 3.5.8~hg20100121r26729+nobinonly-0ubuntu1~umd1~karmic Fabien Tassin (8 hours ago)
firefox-3.6 3.6~hg20100119r33526+nobinonly-0ubuntu1~umd1~karmic Fabien Tassin (2010-01-20)
firefox-3.7 3.7~a1~hg20100121r37362+nobinonly-0ubuntu1~umd1~karmic Fabien Tassin (8 hours ago)

xulrunner-1.9.1 1.9.1.8~hg20100121r26729+nobinonly-0ubuntu2~umd1~karmic Fabien Tassin (8 hours ago)
xulrunner-1.9.2 1.9.2~hg20100120r33527+nobinonly-0ubuntu1~umd1~karmic Fabien Tassin (8 hours ago)
xulrunner-1.9.3 1.9.3~a1~hg20100121r37362+nobinonly-0ubuntu1~umd1~karmic Fabien Tassin (8 hours ago)

I was only offered xulrunner as an update:

xulrunner-1.9.2 1.9.2~hg20100120r33527+nobinonly-0ubuntu1~umd1~karmic Fabien Tassin (8 hours ago)

Looking at apt-cache policy for firefox-3.6

But my machine says latest is: 3.6~hg20100117r33523+nobinonly-0ubuntu1~umd1~karmic

So I seem to be missing out on:

firefox-3.6 3.6~hg20100119r33526+nobinonly-0ubuntu1~umd1~karmic Fabien Tassin (2010-01-20)

:~$ apt-cache policy firefox-3.6
firefox-3.6:
  Installed: 3.6~hg20100117r33523+nobinonly-0ubuntu1~umd1~karmic
  Candidate: 3.6~hg20100117r33523+nobinonly-0ubuntu1~umd1~karmic
  Version table:
 *** 3.6~hg20100117r33523+nobinonly-0ubuntu1~umd1~karmic 0
        400 http://ppa.launchpad.net karmic/main Packages
        100 /var/lib/dpkg/status

If I check apt-cache policy firefox instead:

:~$ apt-cache policy firefox
firefox:
  Installed: 3.5.7+nobinonly-0ubuntu0.9.10.1
  Candidate: 3.5.7+nobinonly-0ubuntu0.9.10.1
  Version table:
     3.6~hg20100120r33527+nobinonly-0ubuntu1~umd2~karmic 0
        400 http://ppa.launchpad.net karmic/main Packages
 *** 3.5.7+nobinonly-0ubuntu0.9.10.1 0
        500 http://gb.archive.ubuntu.com karmic-updates/main Packages
        500 http://gb.archive.ubuntu.com karmic-security/main Packages
        500 http://ppa.launchpad.net karmic/main Packages
        100 /var/lib/dpkg/status
     3.5.3+build1+nobinonly-0ubuntu6 0
        500 http://gb.archive.ubuntu.com karmic/main Packages

OK that is a little clearer, The package firefox is now pointing to a 3.6 package not 3.5. So that must be a change relating to the change from a release candidate to the real thing.

And because I have Pinned the UMD PPA to priority 400, it loses against 3.5.
Great, this is the behaviour that I wanted, although I did not expect it to manifest in exactly this way

That is a didn't want the Official Ubuntu Karmic 3.5 to be replaced by a daily build.

So I suppose that my next update from the dailies will be firefox-3.6 *something* odd as I did not get
3.6~hg20100119r33526

hmm... could it be because Firefox is 3.6~hg20100120r33527?

I'll wait for the next build and see.

Of course once an official Firefox 3.6 is available via the Ubuntu repositories that will be interesting.


================================================== ==============
[UPDATE 2010/01/21 UK 9:41PM]

OK I disabled the Pinning against UDM and allowed the updates after a refresh...
What happened was that the Official Ubuntu 3.5 was upgraded to 3.6 which I did not want.
So via Synaptic Package Manager I uninstalled 3.5 and 3.6 then reinstalled the Official Ubuntu 3.5 after turning off the UDM PPA.
Then, after once again enabling the UDM PPA, I installed 3.6.

So now I am back to having the Official Ubuntu Firefox 3.5 and a separate install of the daily 3.6.

Looking at the UDM builds the firefox package is marked as umd2 and firefox-3.6 as umd1.

firefox       3.6~hg20100120r33527+nobinonly-0ubuntu1~umd2~karmic        Fabien Tassin  (8 hours ago)
firefox-3.6      3.6~hg20100119r33526+nobinonly-0ubuntu1~umd1~karmic     Fabien Tassin  (2010-01-20)

This is my latest "apt-cache policy" info, with no pinning:

:~$ apt-cache policy firefox-3.6
firefox-3.6:
  Installed: 3.6~hg20100117r33523+nobinonly-0ubuntu1~umd1~karmic
  Candidate: 3.6~hg20100117r33523+nobinonly-0ubuntu1~umd1~karmic
  Version table:
 *** 3.6~hg20100117r33523+nobinonly-0ubuntu1~umd1~karmic 0
        500 http://ppa.launchpad.net karmic/main Packages
        100 /var/lib/dpkg/status

:~$ apt-cache policy firefox-3.5
firefox-3.5:
  Installed: 3.5.7+nobinonly-0ubuntu0.9.10.1
  Candidate: 3.6~hg20100120r33527+nobinonly-0ubuntu1~umd2~karmic
  Version table:
     3.6~hg20100120r33527+nobinonly-0ubuntu1~umd2~karmic 0
        500 http://ppa.launchpad.net karmic/main Packages
 *** 3.5.7+nobinonly-0ubuntu0.9.10.1 0
        500 http://gb.archive.ubuntu.com karmic-updates/main Packages
        500 http://gb.archive.ubuntu.com karmic-security/main Packages
        100 /var/lib/dpkg/status
     3.5.3+build1+nobinonly-0ubuntu6 0
        500 http://gb.archive.ubuntu.com karmic/main Packages

:~$ apt-cache policy firefox
firefox:
  Installed: 3.5.7+nobinonly-0ubuntu0.9.10.1
  Candidate: 3.6~hg20100120r33527+nobinonly-0ubuntu1~umd2~karmic
  Version table:
     3.6~hg20100120r33527+nobinonly-0ubuntu1~umd2~karmic 0
        500 http://ppa.launchpad.net karmic/main Packages
 *** 3.5.7+nobinonly-0ubuntu0.9.10.1 0
        500 http://gb.archive.ubuntu.com karmic-updates/main Packages
        500 http://gb.archive.ubuntu.com karmic-security/main Packages
        100 /var/lib/dpkg/status
     3.5.3+build1+nobinonly-0ubuntu6 0
        500 http://gb.archive.ubuntu.com karmic/main Packages
:~$

With Pinning

:~$ apt-cache policy firefox-3.6
firefox-3.6:
  Installed: 3.6~hg20100117r33523+nobinonly-0ubuntu1~umd1~karmic
  Candidate: 3.6~hg20100117r33523+nobinonly-0ubuntu1~umd1~karmic
  Version table:
 *** 3.6~hg20100117r33523+nobinonly-0ubuntu1~umd1~karmic 0
        400 http://ppa.launchpad.net karmic/main Packages
        100 /var/lib/dpkg/status

:~$ apt-cache policy firefox-3.5
firefox-3.5:
  Installed: 3.5.7+nobinonly-0ubuntu0.9.10.1
  Candidate: 3.5.7+nobinonly-0ubuntu0.9.10.1
  Version table:
     3.6~hg20100120r33527+nobinonly-0ubuntu1~umd2~karmic 0
        400 http://ppa.launchpad.net karmic/main Packages
 *** 3.5.7+nobinonly-0ubuntu0.9.10.1 0
        500 http://gb.archive.ubuntu.com karmic-updates/main Packages
        500 http://gb.archive.ubuntu.com karmic-security/main Packages
        100 /var/lib/dpkg/status
     3.5.3+build1+nobinonly-0ubuntu6 0
        500 http://gb.archive.ubuntu.com karmic/main Packages

:~$ apt-cache policy firefox
firefox:
  Installed: 3.5.7+nobinonly-0ubuntu0.9.10.1
  Candidate: 3.5.7+nobinonly-0ubuntu0.9.10.1
  Version table:
     3.6~hg20100120r33527+nobinonly-0ubuntu1~umd2~karmic 0
        400 http://ppa.launchpad.net karmic/main Packages
 *** 3.5.7+nobinonly-0ubuntu0.9.10.1 0
        500 http://gb.archive.ubuntu.com karmic-updates/main Packages
        500 http://gb.archive.ubuntu.com karmic-security/main Packages
        100 /var/lib/dpkg/status
     3.5.3+build1+nobinonly-0ubuntu6 0
        500 http://gb.archive.ubuntu.com karmic/main Packages

So Firefox-3.6 build 33523 is seen as the latest even though 33526 looks to be available. hmm interesting.
xulrunner-1.9.2 has updated to the latest build 33527.

:~$ apt-cache policy xulrunner-1.9.2
xulrunner-1.9.2:
  Installed: 1.9.2~hg20100120r33527+nobinonly-0ubuntu1~umd1~karmic
  Candidate: 1.9.2~hg20100120r33527+nobinonly-0ubuntu1~umd1~karmic
  Version table:
 *** 1.9.2~hg20100120r33527+nobinonly-0ubuntu1~umd1~karmic 0
        400 http://ppa.launchpad.net karmic/main Packages
        100 /var/lib/dpkg/status