Why does "apt-get upgrade" want to upgrade my homebuilt packages?

[Martin Meredith]

you will need to update the version for it to not want to update from
apt ...

uuse something like

382-3~mypackage

So that 382-3 will be later than your version (and wont cause any compat
issues) but, your package will be classes as ahigher build than 382-2

Jaime wrote:
> Hi all.
> 
> In learning how to build and use my own deb packages, I've found a
> problem I can't fix. To briefly summarize, I have two (2) different
> copies of less_382-2_i386.deb - one I downloaded from:
> http://archive.ubuntu.com/ubuntu/pool/main/l/less/less_382-2_i386.deb
> (which I'll call "repodeb") and the other I built myself using
> dpkg-buildpackage (which I'll call "customdeb").
> 
> When I install repodeb (using "dpkg -i"), running "apt-get upgrade"
> tells me there's nothing to update. But if I purge repodeb from my
> system and install customdeb (also using "dpkg -i"), running "apt-get
> upgrade" tells me that customdeb needs upgrading.
> 
> I originally thought that there must be some difference in the control
> files. Here's the control file from repodeb:
> 
> Package: less
> Version: 382-2
> Section: text
> Priority: standard
> Architecture: i386
> Depends: libc6 (>= 2.3.2.ds1-4), libncurses5 (>= 5.4-1), debianutils (>=
> 1.8)
> Installed-Size: 252
> Maintainer: Thomas Schoepf <schoepf at debian.org>
> Description: Pager program similar to more
> Less is a program similar to more(1), but which allows backward
> movement in the file as well as forward movement.  Also, less does not
> have to read the entire input file before starting, so with large input
> files it starts up faster than text editors like vi(1).  Less uses
> termcap (or terminfo on some systems), so it can run on a variety of
> terminals.  There is even limited support for hardcopy terminals.
> .
> Homepage: http://www.greenwoodsoftware.com/less/
> 
> 
> The control file from customdeb is identical except for the
> Installed-Size field (which says 256), so I don't think the control file
> has anything to do with the problem.
> 
> I've also looked at the results of "apt-cache policy less" to try to
> work out what's going on. Here's "apt-cache policy less" with repodeb
> installed:
> less:
>   Installed: 382-2
>   Candidate: 382-2
>   Version table:
> *** 382-2 0
>         500 http://gb.archive.ubuntu.com hoary/main Packages
>         100 /var/lib/dpkg/status
> 
> And here's "apt-cache policy less" with customdeb installed:
> less:
>   Installed: 382-2
>   Candidate: 382-2
>   Version table:
>      382-2 0
>         500 http://gb.archive.ubuntu.com hoary/main Packages
> *** 382-2 0
>         100 /var/lib/dpkg/status
> 
> Unfortunately, I don't understand the output - what do the asterisks
> mean? "man apt_preferences" doesn't really help - to quote that man
> page, "The APT preferences file does not affect  the choice of instance,
> only the choice of version" - but repodeb and customdeb are the same
> version.
> 
> I realize that raising the version number of customdeb would stop
> apt-get wanting to upgrade it, but before I resort to artificial
> solutions, I'd like to know why apt-get thinks customdeb needs
> upgrading.
> 
> All always, any help, or pointers to somewhere/someone else would be
> appreciated.
> 
> Thanks, Jaime
> 
> 
> 

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 256 bytes
Desc: OpenPGP digital signature
URL: <https://lists.ubuntu.com/archives/ubuntu-users/attachments/20050611/37236a12/attachment.sig>