I'm an avid user of Terminator (http://www.tenshu.net/p/terminator.html). The version in the repos is kinda out of date, so I downloaded it myself and built a .deb from the latest code. I've built and manually installed 1.0, but APT stubbornly keeps nagging me to downgrade it to 0.93-4-bzr1026 every time I run
. What's up with that, why is it nagging me when the version number is lower, and how can I prevent it in the future?
Thanks in advance.
Last edited by tinche (2012-12-29 02:08:46)
I do not know what wajig dailyupgrade is or what it is trying to do, that may help in solving this
I build from source all the time and use a prefix parameter to put the source in /usr that way it takes over the apt/dpkg version of terminator or whatever app I am building.
Typically, the install instructions in the source tarball has these instructions
I looked on that page and cannot find the source files for version 1.0
It says for debian users to use whatever is the latest in sid, that is version 0.96-2
Out of curiosity, what is it that you are wanting/needing from version 1.0?
There is also this on that page you posted
If you'd like to discuss Terminator, please feel free to drop by our IRC channel - #terminator on irc.freenode.net
There may be some help there.
Just, curious, what's in the new version of terminator that you want/need so badly?
Thanks for the replies.
Wajig is basically a wrapper around apt-get, dpkg, apt-cache etc. The point is there's a single command to encapsulate all the apt/dpkg commands.
is basically equivalent to
sudo apt-get update && sudo apt-get upgrade
, except it's one command and I don't have to enter sudo beforehand (it'll ask if it needs it). In hindsight I should have just mentioned apt-get update/upgrade to avoid confusion, sorry about that.
I don't actually need anything from 1.0 specifically, but 0.93 that I'm being offered is too old for me (for example, it doesn't have copy-on-selection). Even putting this Terminator issue aside, I'd like to understand how exactly APT works in this regard. If I've manually installed a package with a higher version than is available, why is it insisting on performing a downgrade? Intuitively, I figured it'd keep quiet until a higher version package was available and then suggest an upgrade.
As for Terminator, I just checked out the latest version from their Launchpad repo and built a .deb with the usual
debuild --no-lintian -uc -us
, this gives me a working package that replaced my old one when installed. I find this a nicer way than doing something like make install with a specific prefix and overwriting files belonging to another package.
Sure, I can check out their IRC channel, but this looked like an APT thing to me. If someone could shed some light on what exactly is APT trying to do here, and why, that'd be much appreciated.
Tell us how you built this 1.0 version and I think we can see what happened.
As I said, I build all the time and never have had this issue.
I have had issues where I wanted to hold a package from upgrading. Apt/dpkg are only that, an upgrade system, not a downgrade system. Something strange happened in the build process that apt knows nothing about.
Sure, here we go.
~$ mkdir terminator ~$ cd terminator/ ~/terminator$
Check out the latest:
~/terminator$ bzr branch lp:terminator Branched 1352 revisions. ~/terminator$ cd terminator ~/terminator/terminator$
~/terminator/terminator$ cd debian ~/terminator/terminator/debian$ debuild --no-lintian -us -uc ... http://pastebin.com/RY9vnpMg (~600 lines)...
~/terminator/terminator/debian$ cd ../../ ~/terminator$ sudo dpkg -i terminator_1.0_all.deb [sudo] password for tin: Selecting previously unselected package terminator. (Reading database ... 131977 files and directories currently installed.) Unpacking terminator (from terminator_1.0_all.deb) ... Setting up terminator (1.0) ... update-alternatives: using /usr/bin/terminator to provide /usr/bin/x-terminal-emulator (x-terminal-emulator) in auto mode Processing triggers for man-db ... Processing triggers for desktop-file-utils ... Processing triggers for hicolor-icon-theme ...
Now APT wants to downgrade me:
~/terminator$ sudo apt-get upgrade Reading package lists... Done Building dependency tree Reading state information... Done The following packages will be DOWNGRADED: terminator 0 upgraded, 0 newly installed, 1 downgraded, 0 to remove and 0 not upgraded. Need to get 0 B/191 kB of archives. After this operation, 303 kB disk space will be freed. Do you want to continue [Y/n]?
apt-cache show terminator: http://pastebin.com/dMAPFpT1
Run and show the output of:
apt-cache policy terminator
I am curious if that will show two terminators installed
Also you can do this and it should stop that one from even trying to install.
sudo aptitude hold terminator
$ apt-cache policy terminator terminator: Installed: 1.0 Candidate: 0.93-4-bzr1026 Version table: *** 1.0 0 100 /var/lib/dpkg/status 0.95-1 0 500 http://http.debian.net/debian/ wheezy/main i386 Packages 0.93-4-bzr1026 0 1001 http://packages.crunchbang.org/waldorf/ waldorf/main i386 Packages
Ah, I see now. My /etc/apt/preferences contains:
Package: * Pin: release a=waldorf Pin-Priority: 1001
and man apt_preferences clearly states:
How APT Interprets Priorities Priorities (P) assigned in the APT preferences file must be positive or negative integers. They are interpreted as follows (roughly speaking): P >= 1000 causes a version to be installed even if this constitutes a downgrade of the package ...
In other words, my system is configured to highly prioritize Waldorf packages. That's the info I was after all along
Thanks for nudging me in the right direction, VastOne.
Great to hear, glad you resolved it.. Well done.
Please mark the thread as (SOLVED) by editing the topic of your first post.