From: Jordan Metzmeier on
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256


Last night I was attempting to install spamassassin on my Lenny box. I
had some difficulty doing so because it turned out that the volatile
version had a lesser version number.

The only ways I found to get the volatile version to install was to pin
the volatile repo to > 1000. I then found that this is the same case
with tzdata. Here are examples:

tzdata:
Installed: 2010a-0lenny1
Candidate: 2009l-0lenny1.1
Version table:
*** 2010a-0lenny1 0
500 http://ftp.grokthis.net lenny/main Packages
100 /var/lib/dpkg/status
2009l-0lenny1.1 0
1001 http://volatile.debian.org lenny/volatile/main Packages

spamassassin:
Installed: 3.2.5-2+lenny1.1~volatile1
Candidate: 3.2.5-2+lenny1.1~volatile1
Version table:
3.3.1-1~bpo50+1 0
1 http://ftp.backports.org lenny-backports/main Packages
3.2.5-2+lenny2 0
500 http://ftp.grokthis.net lenny/main Packages
*** 3.2.5-2+lenny1.1~volatile1 0
1001 http://volatile.debian.org lenny/volatile/main Packages
100 /var/lib/dpkg/status



Why are volatile versions made in a way so that using them is a
"downgrade"? Is it possible that a Lenny point-release has obsoleted a
volatile version of a package?

Something just did not seem right about this...


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)

iQIcBAEBCAAGBQJMI2TKAAoJEKj/C3qNthmTGd8QAJCexLEatv+jYNqIGCDZK/Sy
6N8qsodBco/S1NJRtjaR6M9GphzKwUtAds0HQKtgRi9N4rPsmAQgXs2nURcAQ4ei
F3zI6jmmLT9fx9uYuhMDiBb0zzvz8L31kAH2sW73b5jowHWLAgunI3J0cVOLR+to
tPZirrEzns/XPjitKJCEy1okwSvfKbXoq0BnpP3hpe+sGdPHIacTkoab383X5juV
JRmJxjZM3hSgzG2MqV5V327dG3/ufQg3m1KdV4npudHdwqzcz8Yofvk8Gvg+XpXm
YBTtbdRmg3UdCJTUT5hjNNUUmDbJRvJWK+qpw0TkhfvEd6hI+sgnFFLH9u6irVgl
/PhLvY425FJVhFeiaP1EF7ciCCo3bqMhvSCIdEpMXszvcwDAKyEjqC9ZS0qUWsGX
1k+K1sGoan37QSg2uI8gaDb4QT0N39YTc5IoMg5incmSGVkJ28mJQuKpPb8X9YBC
vSVXPyd/DiNyz836pLnYHTvFkjTLDsJz/nD2guTPfFPQf2gSaaWSKK7zUBy/N9PC
t+UAVS9TaAFTXLefCId0vNKHo9wr0o/p3TmWMHoSsEFYk1voqRxZVgL+4+oZjPs/
wGD1bTnLZfc0spxnlJF7Vll11Q+UjTmWbCLIyxZSj8QBZ8j+tTCgpTWZecLAL0Dg
S3VaQtKQpN2cRQzQDXiy
=9mZV
-----END PGP SIGNATURE-----


--
To UNSUBSCRIBE, email to debian-user-REQUEST(a)lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster(a)lists.debian.org
Archive: http://lists.debian.org/4C2364CA.7010102(a)gmail.com
From: Liam O'Toole on
On 2010-06-24, Jordan Metzmeier <titan8990(a)gmail.com> wrote:
>
>
> Last night I was attempting to install spamassassin on my Lenny box. I
> had some difficulty doing so because it turned out that the volatile
> version had a lesser version number.
>
> The only ways I found to get the volatile version to install was to pin
> the volatile repo to > 1000. I then found that this is the same case
> with tzdata. Here are examples:
>
> tzdata:
> Installed: 2010a-0lenny1
> Candidate: 2009l-0lenny1.1
> Version table:
> *** 2010a-0lenny1 0
> 500 http://ftp.grokthis.net lenny/main Packages
> 100 /var/lib/dpkg/status
> 2009l-0lenny1.1 0
> 1001 http://volatile.debian.org lenny/volatile/main Packages
>
> spamassassin:
> Installed: 3.2.5-2+lenny1.1~volatile1
> Candidate: 3.2.5-2+lenny1.1~volatile1
> Version table:
> 3.3.1-1~bpo50+1 0
> 1 http://ftp.backports.org lenny-backports/main Packages
> 3.2.5-2+lenny2 0
> 500 http://ftp.grokthis.net lenny/main Packages
> *** 3.2.5-2+lenny1.1~volatile1 0
> 1001 http://volatile.debian.org lenny/volatile/main Packages
> 100 /var/lib/dpkg/status
>
>
>
> Why are volatile versions made in a way so that using them is a
> "downgrade"? Is it possible that a Lenny point-release has obsoleted a
> volatile version of a package?
>
> Something just did not seem right about this...
>

Both packages were updated in the last Lenny update[1], at which time
they 'leap-frogged' the versions in volatile. Nothing to worry about.

[1] http://www.debian.org/News/2010/20100130

--
Liam O'Toole
Cork, Ireland



--
To UNSUBSCRIBE, email to debian-user-REQUEST(a)lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster(a)lists.debian.org
Archive: http://lists.debian.org/slrni2738i.56n.liam.p.otoole(a)dipsy.selfip.org
From: Jordan Metzmeier on
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On 06/24/2010 12:51 PM, Liam O'Toole wrote:
> Both packages were updated in the last Lenny update[1], at which time
> they 'leap-frogged' the versions in volatile. Nothing to worry about.
>
> [1] http://www.debian.org/News/2010/20100130
>

Got it, thanks for the reply.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)

iQIcBAEBCAAGBQJMJK3eAAoJEKj/C3qNthmTg8MQANBDkcSxxSMMKJ6/PzO5+q2u
SbPt8ToSp8XulMYZnZlMPQPwjGeLval20DlK1bObYl3srf3r9vOupQKUemtgIrww
s+REqYqPscNWchSQ6WmEAcTkgxZ3mKhCzzPXk/eqUhjYg9VIiAbQH3NQjmjsdJBh
KWNSfFSIunWemG/UdXAaWE1pQaC+gGnTumSRXRKuBKtxH6GMbXbF4wdVljdiTBiz
M9wo9//lPQQSmlTNlopC/M6orH2ulWGeTQ5nGJTaldRFBbBpoSfcwA7x2H12Qwwh
ML1clxdlsyFXWl8agLPDRCvFh9reTopfJNdXw2yfkvGAs7p/Yod5vUx4MeOg05Z2
pl2drnjXp+3oPo2A+yawgQgpfy0h0lEzQS4VwXq++KcSrQTmxRe0ibInj2YEXrk0
Y2pJ+epdYAkDU5Rr7ICI+LreqZjQ6GtF2YuDtYOrMi7T46XlwHtYpUupZqv1OVZp
MLG6YQnkMD6C8VMeVCZtU+JrO+uyD3XKGDj7BDzIhgqlNWFfn8uUlSwaVyy8Jw6N
e5hNxohRQXiTvDqkEL0uXZitSezioSqbj1FN/j3WI03E8vmTzoRk9laxSNgFflT2
2pHA0j9IAQIyBugVoMZXjTrxD6UhzF18bFgIFJdK9a38PS01Dq1IeGD5QuRFdsj/
0IlQ8y8ntAyDD7yIIeqr
=AOGW
-----END PGP SIGNATURE-----


--
To UNSUBSCRIBE, email to debian-user-REQUEST(a)lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster(a)lists.debian.org
Archive: http://lists.debian.org/4C24ADDF.1000506(a)gmail.com
From: Jordan Metzmeier on
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On 06/25/2010 12:00 PM, Boyd Stephen Smith Jr. wrote:
> On Thursday 24 June 2010 08:59:38 Jordan Metzmeier wrote:
>> Last night I was attempting to install spamassassin on my Lenny box. I
>> had some difficulty doing so because it turned out that the volatile
>> version had a lesser version number.
>
> Liam already explain why this was so.
>
>> The only ways I found to get the volatile version to install was to pin
>> the volatile repo to > 1000. I then found that this is the same case
>> with tzdata. Here are examples:
>
> Please remember to drop this pinning. It is giving you out-of-date versions
> on packages.

Yes, I did this once I discovered that the debian main packages really
were newer and included the same bug fixes in the changelogs.

Thanks again.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)

iQIcBAEBCAAGBQJMJNL9AAoJEKj/C3qNthmT4CwP/ROfw8Jo39DTcWM5nq7j0VD8
Aj8Rql8Ckaipa0y/DbHuCXgeRjYC5clAVMS4tdZ/q1568/V9dPMRX1wrEkbwpv/C
aqdJVG3STeClknnggucdfiJka4D4fyQgL8zbuoJcSGQURjU6nPLW7GcaBB89OZM3
nPMuzq43lxf/UWKugzOXdkge0R/6a3N6lQJRf9j4Y65eXt8dny12pQOT5GdMp5AU
t9HCKZ4ocptTAuQXsTT46acOhfWOXOzFWSCMWR/j7B3Tpt5JbyTGoKz6MlMiGE0K
l1AdIls92xD42vFmS8u15/s+xM49lwUvFFgYDFe7eY0+/MLpn0bJ3qqzeYial1ge
7ShqXUNckPuANfSYtmF64fBTjF70qHNja0mcM/CJttoJJHjkVK5n8PGAn+QeHdCy
nxRjjp7iyA6bsujtJbOAuPojp/jIVeyhxqtfn7P87VORlSC1SM1WYF+RoGwcRD6X
FvsLMApVbEP3iyVpQ5poY9MfFAWckMNC+085QLSkpt1otxSYckaB9TKFo1kQ9mFO
DjU1Ej5klieVqp6KDlpcdz67/4bgCBheBBKada1YrVioyxWrEzsPLBfYsSQ3FMQQ
tfNWO8OuG/JXRHK6WGlXZPijqu6mbJjCZ9TCMaSoX2ScyYaVoUTweckzxJNulZTy
1ZsjpHQ5qPKZAY6sjuUp
=Bhd+
-----END PGP SIGNATURE-----


--
To UNSUBSCRIBE, email to debian-user-REQUEST(a)lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster(a)lists.debian.org
Archive: http://lists.debian.org/4C24D2FD.7090308(a)gmail.com
From: Boyd Stephen Smith Jr. on
On Thursday 24 June 2010 08:59:38 Jordan Metzmeier wrote:
> Last night I was attempting to install spamassassin on my Lenny box. I
> had some difficulty doing so because it turned out that the volatile
> version had a lesser version number.

Liam already explain why this was so.

> The only ways I found to get the volatile version to install was to pin
> the volatile repo to > 1000. I then found that this is the same case
> with tzdata. Here are examples:

Please remember to drop this pinning. It is giving you out-of-date versions
on packages.
--
Boyd Stephen Smith Jr. ,= ,-_-. =.
bss(a)iguanasuicide.net ((_/)o o(\_))
ICQ: 514984 YM/AIM: DaTwinkDaddy `-'(. .)`-'
http://iguanasuicide.net/ \_/