Re: package version problem
BM> I have no clue why it deletes it since there is no mention of any
BM> ssh package higher than 2.5.2p2 from debian... so what can I do to
BM> make this work. And another question.. when I create some package
BM> from the debian source (for instance by running apt-get -b source
BM> somepackage). When I install that newly created .deb file and than
BM> run apt-get upgrade, that same package is marked as old and
BM> replaced by the original debian file... what does one have to do
BM> for the package only be replaced by higher version number and not
BM> the same version...
Because ssh package on debian has epoch in its Version field.
$ dpkg -s ssh
Package: ssh
...
Version: 1:2.3.0p1-0.11
^^^
1: in Version field is epoch. Package with higher epoch is
considered as always having higher version number. Default epoch is
0. You need to set epoch for your package to 1.
--
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
| Ilya Martynov (http://martynov.org/) |
| GnuPG 1024D/323BDEE6 D7F7 561E 4C1D 8A15 8E80 E4AE BE1A 53EB 323B DEE6 |
| AGAVA Software Company (http://www.agava.com/) |
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Reply to: