[ Date Index ] [ Thread Index ] [ <= Previous by date / thread ] [ Next by date / thread => ]
Hi Paul The best way to tackle this is to use APT's pin facility. I don't have a full explanation to hand, but google "Pin Debian packages for Apt" will show you how. In brief in /etc/apt you provide a list of packages and their version numbers, this config file tells apt not to upgrade them. Hope that helps you Regards and Best Wishes Rick Timmis Abazander Ltd Sent from my Dragon 32 On 20 Jun 2012, at 11:07, David Hare <davidhare77@xxxxxxxxxxx> wrote: > On 16/06/12 10:44, Gordon Henderson wrote: >> >> I need to make a new version of an existing Debian package. Basically I >> need to take an existing source package, apply some patches to it, then >> re package it. >> >> I've actually done this - and it works. >> >> However, a recent apt-get update/upgrade has replaced my package with a >> new off off Debian. >> >> So I need to know the best way to stop this happening... >> >> Ideally, I need my package to replace an existing package if it's >> already installed, or to stop a future update replacing my package with >> the older version off Debian. (Let's not wory about security concerns >> for now - unlikely to be any, however) >> >> So what do I do? Increment the version number? Or is there some better >> way of doing it? >> >> The patches I'm applying to the package are not in Wheezy either, so no >> ponit using backports for it. (the patches don't apply cleanly to the >> latest version of this software either, so I'm stuck with an older version) >> >> It's avrdude - the program for uploading to ATmega microcnotrollers if >> anyones intersted. I can now use the Raspberry Pi's GPIO pins to upload >> directly into an AVR chip without going via serial... >> >> And it's rather critical that I maintain the ability to do this as >> serial is not a viable option for this project, however it might well be >> used by 100's or even 1000's of people, so needs to be as easy to >> install as possible - wget the new version off my site, and dpkg -i is >> acceptable, but a future apt-get update/upgrade overwriting it isn't... >> >> Clues/hints welcome! >> >> Gordon >> > > No expert, but something like this has worked for me before: > > Unpack and rename the custom package, edit the control file with the original name > in the "Conflicts" and "Provides" fields > > Repack it and install normally with apt or dpkg -i > > David > > -- > The Mailing List for the Devon & Cornwall LUG > http://mailman.dclug.org.uk/listinfo/list > FAQ: http://www.dcglug.org.uk/listfaq -- The Mailing List for the Devon & Cornwall LUG http://mailman.dclug.org.uk/listinfo/list FAQ: http://www.dcglug.org.uk/listfaq