Bug#668620: Info. asked about megaglest crasher -
tomreyn at megaglest.org
Thu Apr 19 22:35:17 UTC 2012
On 19.04.2012 22:20 shirish à¤¶à¤¿à¤°à¥à¤· wrote:
> As an aside though, I do have another query though, in your first
> reply you had spoken about
> "on a mixed Debian stable/testing/unstable system " . Was that because
> of the policy ?
> APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'),
> (1, 'experimental')
> or something else. Because what I try to do is have the highest
> version of each and every package in sid. The other releases are just
> for me to check on what version numbers others are at (info. which
> is/can be handy at times.) . Also if I do get some nasty update then
> can switch to the testing or stable versions of software if need be
> till it gets fixed (hasn't had to use that for a long time since
> apt-listbugs does it job well).
> Just thought I would mention it so there's no confusion.
Thanks for clarifying, Shirish. Indeed the APT policy report is what
made me think you may have a mixed stable/testing/unstable system. Take
a look at rmadison (package "devscripts") for a way to easily determine
version numbers of various distros and releases.
More information about the Pkg-games-devel