On Fri, May 18, 2007 at 17:44:42 +0200, Jakub Narojczyk wrote: > Florian Kulzer napisał(a): >> On Wed, May 16, 2007 at 22:43:18 +0200, Jakub Narojczyk wrote: >> OK, I have to admit that I really don't understand what is going on >> here. For some reason your apt regarded the gimp 2.2.13-1 package on the >> server as being different from the gimp 2.2.13-1 that you had installed >> already and it "upgraded" accordingly. Your package pin cannot prevent >> this since both are "2.2.13-1". >> It would interesting to see what "apt-cache policy gimp" produces now, >> and also "apt-cache show" for one of the "not upgraded" packages, e.g. >> "apt-cache show gimp-data". > well, "apt-cache policy gimp" gives: > > gimp: > Installed: 2.2.13-1 > Candidate: 2.2.13-1 > Package pin: 2.2.13-1 > Version table: > *** 2.2.13-1 1001 > 500 ftp://ftp.task.gda.pl etch/main Packages > 100 /var/lib/dpkg/status > > were "apt-cache policy gimp-data" gives: > > gimp-data: > Installed: 2.2.13-1 > Candidate: 2.2.13-1 > Package pin: 2.2.13-1 > Version table: > 2.2.13-1 1001 > 500 ftp://ftp.task.gda.pl etch/main Packages > *** 2.2.13-1 1001 > 100 /var/lib/dpkg/status > > as for apt-cache show > > gimp: > > Package: gimp > Priority: optional > Section: graphics > Installed-Size: 7792 > Maintainer: Ari Pollak <[EMAIL PROTECTED]> > Architecture: i386 > Version: 2.2.13-1 > Replaces: gimp-data (<< 2.2.11-2) > Depends: wget, gimp-data (= 2.2.13-1), libaa1 (>= 1.2), libart-2.0-2 (>= > 2.3.16), libatk1.0-0 (>= 1.12.1), libc6 (>= 2.3.6-6), libcairo2 (>= 1.2.4), > libexif12, libexpat1 (>= 1.95.8), libfontconfig1 (>= 2.3.0), libfreetype6 > (>= 2.2), libgimp2.0 (>= 2.2.0+rel), libglib2.0-0 (>= 2.10.0), libgtk2.0-0 > (>= 2.8.0), libice6, libjpeg62, liblcms1 (>= 1.08-1), libmng1 (>= 1.0.3-1), > libpango1.0-0 (>= 1.12.3), libpng12-0 (>= 1.2.8rel), libsm6, libtiff4, > libwmf0.2-7 (>= 0.2.8.4), libx11-6, libxcursor1 (>> 1.1.2), libxext6, > libxfixes3, libxi6, libxinerama1, libxmu6, libxpm4, libxrandr2, > libxrender1, libxt6, zlib1g (>= 1:1.2.1) > Recommends: gimp-svg, gimp-print > Suggests: gimp-help-en | gimp-help, gimp-python, libgimp-perl, > gimp-data-extras, libasound2 (>= 1.0.0) > Conflicts: gimp-data (<< 2.2.11-2), libgimp2.0 (>= 2.3.0) > Filename: pool/main/g/gimp/gimp_2.2.13-1_i386.deb > Size: 3067832 > MD5sum: c6bf2c928770e3e03d67fe9e2b5410d1 > SHA1: e8ddf11478b16eeee96dad39abd9d4de0b147daa > SHA256: a00529749b8f09ffe7a007039c790a24992fb82485e9cb3e9221d234f8a954d3 > Description: The GNU Image Manipulation Program > The GIMP lets you draw, paint, edit images, and much more! GIMP > includes the functionality and plug-ins of other famous image > editing and processing programs. > . > If you'd like to use a MIDI device as an input controller in GIMP, > install libasound2 and read the how-to at /usr/share/doc/gimp/README.MIDI > Tag: interface::x11, role::program, role::shared-lib, scope::application, > suite::gimp, uitoolkit::gtk, use::editing, works-with::image, > works-with::image:raster, x11::application > Task: desktop > > gimp-data > > Package: gimp-data > Priority: optional > Section: graphics > Installed-Size: 20400 > Maintainer: Ari Pollak <[EMAIL PROTECTED]> > Architecture: all > Source: gimp > Version: 2.2.13-1 > Recommends: gimp > Filename: pool/main/g/gimp/gimp-data_2.2.13-1_all.deb > Size: 6776230 > MD5sum: 58bcb4b9bd29a004ae58abc8ef27b944 > SHA1: 85108add26ae101f8b2a842e0ea7375c2a825aa7 > SHA256: fce925cd7233816ac6d759ae866fe8ad1863d443b8ab851952825bc01a90665d > Description: Data files for The GIMP > This package contains architecture-independent supporting data files > for use with The GIMP. > Tag: made-of::data:icons, role::app-data, special::auto-inst-parts, > suite::gimp, uitoolkit::gtk, works-with::image, works-with::image:raster > > Package: gimp-data > Status: install ok installed > Priority: optional > Section: graphics > Installed-Size: 19586 > Maintainer: Ari Pollak <[EMAIL PROTECTED]> > Architecture: all > Source: gimp > Version: 2.2.13-1 > Recommends: gimp > Conffiles: > /etc/gimp/2.0/gtkrc e1b477a10123f796e0e4660bd1307165 > /etc/gimp/2.0/sessionrc 0e7d0d195286139b2a4214bca01ac63b > /etc/gimp/2.0/gimprc 9c7860a21cf2843b258ad5bcc2353a32 > /etc/gimp/2.0/unitrc 3ec404ec597ef5460600cccf0192f4d6 > /etc/gimp/2.0/ps-menurc 70aeff88269e7cba118c5fbe38685938 > /etc/gimp/2.0/controllerrc dc285f9d351d26a538cd4f683786a3aa > /etc/gimp/2.0/templaterc 34b5343551f53a1db6ee8f921e9bf351 > Description: Data files for The GIMP > This package contains architecture-independent supporting data files > for use with The GIMP. > > May by it's a bug of some sort, some conditional instructions are randomly > interpreted in some rare cases. some of the packages were held back as they > should. maybe a work around would be to change the version of the compiled > packages slightly up, eg. 2.2.13-1 to 2.2.13-2? although > I will have to dig through the how-to about making debs becouse at this > moment I don't know where to change this numbers
OK, I missed the part about the self-compiled packages in your first message. (I only saw the missing blank lines and thought I had found the problem; later on I never looked at that first message again.) I think you can use pinning by origin to distinguish between local packages and the ones from Debian. The manpage of apt_preferences has some examples of this. I never used it myself, so I don't know how well it works. -- Regards, | http://users.icfo.es/Florian.Kulzer Florian |
