---------- Forwarded message ---------- From: Peter Hillier-Brook <[email protected]> Date: Sat, Feb 9, 2013 at 11:55 AM Subject: Re: Fwd: Fwd: Latest release To: [email protected]
On 09/02/13 00:29, James Cain wrote: > > > ---------- Forwarded message ---------- > From: *Scott Kitterman* <[email protected] <mailto:[email protected] > >> > Date: Wed, Feb 6, 2013 at 11:59 PM > Subject: Re: Fwd: Latest release > To: [email protected] <mailto:kubuntu-devel@lists.** > ubuntu.com <[email protected]>> > > > On Wednesday, February 06, 2013 08:24:41 PM James Cain wrote: > > FYI...Any insights? > > > > > > > > -- > > James Cain > > > > ---------- Forwarded message ---------- > > From: Peter Hillier-Brook <[email protected] > <mailto:[email protected]>> > > Date: Wed, Feb 6, 2013 at 3:51 PM > > Subject: Latest release > > To: [email protected] > <mailto:kubuntu-users@lists.**ubuntu.com <[email protected]>> > > > > > > Daft question, but am I under attack? I've just logged in and been > offered > > 13.04 and it's obviously not April. As this is a new machine I have no > > qualms about accepting the invitation - it can always be scrubbed back > to > > iron -but I am intrigued by what appears to be a genuinely new version > of > > Kubuntu. Can anyone clarify what is going on? > > > > Peter HB > > Whatever happened, it's not general as I haven't gotten offered that on a > quantal system. There is not anything intended to happen. Given the > way the > new release detector works, I'm quite surprised. > > It would be good to know what's in /etc/update-manager/release-**upgrades > and > meta-release. > > Scott K > > -- > kubuntu-devel mailing list > [email protected] > <mailto:kubuntu-devel@lists.**ubuntu.com<[email protected]> > > > > Modify settings or unsubscribe at: > https://lists.ubuntu.com/**mailman/listinfo/kubuntu-devel<https://lists.ubuntu.com/mailman/listinfo/kubuntu-devel> > > > > -- > James Cain > > James & Scott, many thanks for your interest in my un-expected upgrade to 13.04. FYI I'm pasting below the contents of /etc/update-manager/release-**upgrades # Default behavior for the release upgrader. [DEFAULT] # Default prompting behavior, valid options: # # never - Never check for a new release. # normal - Check to see if a new release is available. If more than one new # release is found, the release upgrader will attempt to upgrade to # the release that immediately succeeds the currently-running # release. # lts - Check to see if a new LTS release is available. The upgrader # will attempt to upgrade to the first LTS release available after # the currently-running one. Note that this option should not be # used if the currently-running release is not itself an LTS # release, since in that case the upgrader won't be able to # determine if a newer release is available. Prompt=normal and meta-release. # default location for the meta-release file [METARELEASE] URI = http://changelogs.ubuntu.com/**meta-release<http://changelogs.ubuntu.com/meta-release> URI_LTS = http://changelogs.ubuntu.com/**meta-release-lts<http://changelogs.ubuntu.com/meta-release-lts> URI_UNSTABLE_POSTFIX = -development URI_PROPOSED_POSTFIX = -proposed For what it is worth I'm running a fresh install of Kubuntu on an Intel based laptop with EFI. Interestingly I'm also running Kubuntu on a couple of desktops based on AMD-64 processors and standard BIOS and I have *not* been offered the upgrade. The 2 files you requested appear identical on the desktop machines with those on the laptop. If any other information would help, please just ask. Peter HB -- James Cain
-- kubuntu-devel mailing list [email protected] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/kubuntu-devel
