The Opera sources files looks like this by default:

# This file makes sure that Opera Browser is kept up-to-date
# as part of regular system upgrades

deb http://deb.opera.com/opera/ stable non-free #Opera Browser (final releases)

# The line above will make sure you get all final public releases.
# Uncomment the following line if you want to get alpha and beta
# releases, too.

# deb http://deb.opera.com/opera-beta/ stable non-free #Opera Browser (beta releases)

If you manually uncommented the last line to opt into receiving betas your Opera 11.52 would have been updated. Most users have not done this so would not receive an update to Opera.

To clarify only the opt-in "opera-beta" repository was updated. The default repository "opera" was not.

Compare the contents of: http://deb.opera.com/opera/pool/non-free/o/opera/

with: http://deb.opera.com/opera-beta/pool/non-free/o/opera/

Originally posted by Frenzie:

But I didn't.

Well look in http://deb.opera.com/opera/pool/non-free/o/opera/ as you can see the 11.60 build isn't even offered so if you still received it then apt/software center/update manager is reading deb source lines that are commented out.

First I would look in /etc/apt/sources.list and /etc/apt/sources.list.d/opera.list and check that there is no uncommented "deb http://deb.opera.com/opera-beta/ stable non-free #Opera Browser (beta releases)" line. If there is then you need to work out how this got uncommented.

We don't touch /etc/apt/sources.list ourselves and the /etc/apt/sources.list.d/opera.list that our packages create certainly is commented. If you need to prove this to yourself have a look at the part of the post install script that creates these files in recent version of Opera and Opera Next, e.g.

Opera 11.52 32-bit final:

$ ar p opera_11.52.1100_i386.deb control.tar.gz | tar -xzOf- ./postinst | grep -A11 "cat >/etc/apt/sources.list.d/opera.list"
                                cat >/etc/apt/sources.list.d/opera.list <<EOF
# This file makes sure that Opera Browser is kept up-to-date
# as part of regular system upgrades

deb http://deb.opera.com/opera/ stable non-free #Opera Browser (final releases)

# The line above will make sure you get all final public releases.
# Uncomment the following line if you want to get alpha and beta
# releases, too.

# deb http://deb.opera.com/opera-beta/ stable non-free #Opera Browser (beta releases)
EOF

Opera Next 32-bit 12.00-1116:

$ ar p opera-next_12.00.1116_i386.deb control.tar.gz | tar -xzOf- ./postinst | grep -A11 "cat >/etc/apt/sources.list.d/opera.list" 
                                cat >/etc/apt/sources.list.d/opera.list <<EOF
# This file makes sure that Opera Browser is kept up-to-date
# as part of regular system upgrades

deb http://deb.opera.com/opera/ stable non-free #Opera Browser (final releases)

# The line above will make sure you get all final public releases.
# Uncomment the following line if you want to get alpha and beta
# releases, too.

# deb http://deb.opera.com/opera-beta/ stable non-free #Opera Browser (beta releases)
EOF

One final point. If you use Opera Next for testing you do not need to uncomment the "opera-beta" repro, as we also offer the latest Opera Next version in the "opera" repro. You should only uncomment that line if you want your regular Opera to upgrade to Beta versions, which is exactly what happened here.

Hence the issue that you saw is actually intended behaviour at least from our perceptive. If you didn't intend to uncomment the opera-beta repro and this happened anyway outside of your control then perhaps there is some bug but this could equally be a problem with one of the package mangers on your system. It is not necessarily an Opera issue.

Hmm .. well, assuming it wasn't a memory lapse if you ever find out how it got uncommented report back. In the mean time if you don't want this to happen again re-comment that last line.