Re: keep specific versions of packages
Francesco Pietra [EMAIL PROTECTED] writes: I want to avoid any modification from apt-get commands to mpqc 2.3.1-0.2 specially compiled for amd64 with libint (which is not included in the package of same version on debian repositories) and installed with dpkg. I.e., I want to avoid downgrading to a version without libint. From apt-cache show mpqc version installed 2.3..1-0.2, though the list of dependencies does not show libint (which is in, because the software deals correctly with integrals that only libint allows to do) According to Silva's APT HOWTO I should manage with /etc/apt/preferences, though there is no such file or directory on my debiam amd64 etch, linux-image-2.6.18-3-amd64. Should I build a file preferences from scratch? I must say that I am not familiar with this aspect of apt. Thanks for advice francesco pietra There are a few things you can do. One already discussed is pinning. Here are some other options (in order of safety, lowest first): 1. Put mpqc on hold with dpkg or in dselect. apt will not change packages on hold unless you specifically ask for it. 2. Set an epoch of 666 and recompile mpqc. It will surley have a higher version. Without pining the highest version will be installed. But this might interfere with packages with Depends: mpqc (= 2.4.0) or similar. 3. Create a pseudo package Package: mypackages Version: 20070108-1 Priority: Required Essential: yes Depends: mpqc (= 2.3.1-0.2) Updating mpqc would remove mypackages and that will ask you to type in a long sentence to confirm. Apt tries real hard not to remove essential packages. MfG Goswin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: keep specific versions of packages
On Sat, 30 Dec 2006, Francesco Pietra wrote: dselect recognizes the mpqc 2.3.1-0.2 installation and I could place H on that. that's ok. You should actually put on hold all packages which come from the mpqc source package. To see what packages come from a given source package you can use the apt-cache command, as in apt-cache showsrc mpqc. This will tell you that the mpqc source package generates the binary packages: mpqc, libsc7, libsc-doc, libsc-dev, mpqc-support. You therefore ought to have produced a 2.3.1-0.2 version of all of them as well, when you compiled your personal mpqc. Install them and put them on hold as well. As to libint, is it a library which is included in mpqc? A system library? A library you compiled yourself as well which is not part of available debian packages? In any case, I don't think you should need to do anything special about it. Moreover, simply placing H on the mpqc package does prevent upgradind dependencies, or is that immaterial to mpqc functioning? Not necessarily. In any case, the only dependencies you should worry about and put on hold are the ones on libraries coming from mpqc itself. In principle it is possible that an upgrade to another library may cause problems to mpqc, but changes which make a library incompatible with previous versions are a very rare occurrence, avoided whenever possible (even in unstable) due to the havoc such things may easily wreak. Ciao Giacomo -- _ Giacomo Mulas [EMAIL PROTECTED] _ OSSERVATORIO ASTRONOMICO DI CAGLIARI Str. 54, Loc. Poggio dei Pini * 09012 Capoterra (CA) Tel. (OAC): +39 070 71180 248 Fax : +39 070 71180 222 Tel. (UNICA): +39 070 675 4916 _ When the storms are raging around you, stay right where you are (Freddy Mercury) _ -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: keep specific versions of packages
--- Giacomo Mulas [EMAIL PROTECTED] wrote: On Sun, 24 Dec 2006, Francesco Pietra wrote: I want to avoid any modification from apt-get commands to mpqc 2.3.1-0.2 Ciao Francesco. There are many ways to achieve what you want. The simplest one is just to put the mpqc packages in hold state. You can do that using any of the frontends (e.g. from dselect to synaptic just to name two). This will prevent _any_ automatic upgrade of mpqc. You will still be able to upgrade it, if needed, using a explicit command, but not with a general upgrade of the system. I have no gui on amd64 etch. Aptitude does not recognize the installation of mpqc 2.3.1-0.2, which was carried out with dpkg without uninstalling mpqc 2.3.1-1. At least not on science, where it recognizes only mpqc-support 2.3.1-1 from apt-get previous installation. dselect recognizes the mpqc 2.3.1-0.2 installation and I could place H on that. My only remaining concern (I am not in a hurry to command a apt-get upgrade) is about the dependencies, which are shown by apt-show mpqc. I have not checked them against those for mpqc 2.3.1-1 still existing on debian repositories, though libint was surely expressely introduced for the new version 0.2. Therefore, is placing H for mpqc 2.3.1-1 0.2 enough to prevent it being touched during apt-get upgrade if the same version appears on debian repositiries (I fear that the new version on debian repositories will not be compiled for libint, because this serves very special procedures only). Moreover, simply placing H on the mpqc package does prevent upgradind dependencies, or is that immaterial to mpqc functioning? This clarification will serve also for any future similar case. Thanks a lot francesco Another option: if you obtained those packages from a repository which includes release information, you can use the pin functionality of apt to force apt-get to always obtain a well-defined revision. This is achieved by adding stanzas to the file /etc/apt/preferences, such as Package: mpqc* Pin: release a=whateveritisinthatrepository Pin-Priority: higherthandefault where you should substitute whateveritisinthatrepository with the release name for packages in the repository you use, and higherthandefault with a number higher than the default and than any other general matching stanza (if you have others), to avoid your mpqc packages to be taken from another source. You should find more information about how to handle this functionality in the /usr/share/doc/Debian/apt-howto directory. Read it, it's worth the time you will spend with it, since you will probably save you quite a bit more time in solving trivial problems in the future. If necessary, install some apt-howto package (I think there is also one in Italian). If you compile your mpqc packages yourself and did not set up a full-fledged repository with release fields for it, you will probably be better off with the first option, i.e. put the packages on hold, but I also offer you a small suggestion from my own experience in maintaining locally a number of backported packages: when compiling your own packages, edit the debian/changelog to bump up your compiled version from the currently available one you are tracking (from unstable, perhaps?). I usually just add a .1 to the version number. Then install your local packages and put them on hold. This has 2 effects: the first one, as explained above, they will not be automatically upgraded; the second one, they will not even show up in the list of packages for which a newer version is available, until this is really the case, i.e. when a new version is release in debian. Therefore, it will not be automatically upgraded but you will know there was a new version released, possibly with bug fixes, and you will decide whether it's worth recompiling a new local version with those bug fixes. Have fun Giacomo P.S.: Buon Natale (in ritardo) e felice anno nuovo -- _ Giacomo Mulas [EMAIL PROTECTED] _ OSSERVATORIO ASTRONOMICO DI CAGLIARI Str. 54, Loc. Poggio dei Pini * 09012 Capoterra (CA) Tel. (OAC): +39 070 71180 248 Fax : +39 070 71180 222 Tel. (UNICA): +39 070 675 4916 _ When the storms are raging around you, stay right where you are (Freddy Mercury) _ -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around
Re: keep specific versions of packages
On Sun, 24 Dec 2006, Francesco Pietra wrote: I want to avoid any modification from apt-get commands to mpqc 2.3.1-0.2 Ciao Francesco. There are many ways to achieve what you want. The simplest one is just to put the mpqc packages in hold state. You can do that using any of the frontends (e.g. from dselect to synaptic just to name two). This will prevent _any_ automatic upgrade of mpqc. You will still be able to upgrade it, if needed, using a explicit command, but not with a general upgrade of the system. Another option: if you obtained those packages from a repository which includes release information, you can use the pin functionality of apt to force apt-get to always obtain a well-defined revision. This is achieved by adding stanzas to the file /etc/apt/preferences, such as Package: mpqc* Pin: release a=whateveritisinthatrepository Pin-Priority: higherthandefault where you should substitute whateveritisinthatrepository with the release name for packages in the repository you use, and higherthandefault with a number higher than the default and than any other general matching stanza (if you have others), to avoid your mpqc packages to be taken from another source. You should find more information about how to handle this functionality in the /usr/share/doc/Debian/apt-howto directory. Read it, it's worth the time you will spend with it, since you will probably save you quite a bit more time in solving trivial problems in the future. If necessary, install some apt-howto package (I think there is also one in Italian). If you compile your mpqc packages yourself and did not set up a full-fledged repository with release fields for it, you will probably be better off with the first option, i.e. put the packages on hold, but I also offer you a small suggestion from my own experience in maintaining locally a number of backported packages: when compiling your own packages, edit the debian/changelog to bump up your compiled version from the currently available one you are tracking (from unstable, perhaps?). I usually just add a .1 to the version number. Then install your local packages and put them on hold. This has 2 effects: the first one, as explained above, they will not be automatically upgraded; the second one, they will not even show up in the list of packages for which a newer version is available, until this is really the case, i.e. when a new version is release in debian. Therefore, it will not be automatically upgraded but you will know there was a new version released, possibly with bug fixes, and you will decide whether it's worth recompiling a new local version with those bug fixes. Have fun Giacomo P.S.: Buon Natale (in ritardo) e felice anno nuovo -- _ Giacomo Mulas [EMAIL PROTECTED] _ OSSERVATORIO ASTRONOMICO DI CAGLIARI Str. 54, Loc. Poggio dei Pini * 09012 Capoterra (CA) Tel. (OAC): +39 070 71180 248 Fax : +39 070 71180 222 Tel. (UNICA): +39 070 675 4916 _ When the storms are raging around you, stay right where you are (Freddy Mercury) _ -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: keep specific versions of packages
Francesco, On Wednesday 27 December 2006 01:54, Francesco Pietra wrote: --- Mike Reinehr [EMAIL PROTECTED] wrote: On Sunday 24 December 2006 09:03, Francesco Pietra wrote: I want to avoid any modification from apt-get commands to mpqc 2.3.1-0.2 specially compiled for amd64 with libint (which is not included in the package of same version on debian repositories) and installed with dpkg. I.e., I want to avoid downgrading to a version without libint. From apt-cache show mpqc version installed 2.3..1-0.2, though the list of dependencies does not show libint (which is in, because the software deals correctly with integrals that only libint allows to do) According to Silva's APT HOWTO I should manage with /etc/apt/preferences, though there is no such file or directory on my debiam amd64 etch, linux-image-2.6.18-3-amd64. Should I build a file preferences from scratch? I must say that I am not familiar with this aspect of apt. Thanks for advice francesco pietra Francesco, I've been trying to understand pinning from the time I first used Debian, several years now, and still feel that I'm missing something, but I think your problem has a simple solution. I believe all that you need in your /etc/apt/preferences file are the following three lines: Package: mpqc Pin: version 2.3.1-0.2 Pin-Priority: 1000 As I wrote, there is no preferences file on my system. Create from scratch? Yes, as root with a text editor, i.e., vi, vim, ed, ... and mode 0644. -rw-r--r-- 1 root root 245 Sep 2 17:06 /etc/apt/preferences See man apt_preferences for details. Besides this, what happens to the libraries if I free a package? For example, I wanted to check the stage of development of ghemical on GNOME, though it ptretends to install mpqc too, which is not compiled for the libraries I need (in part lower, in part lacking). If I understand you correctly, then, if you decided to remove ghemical and mpqc was marked as having been installed automatically to satisfy the dependencies of ghemical, it too would be removed, otherwise, not. If you attempted to upgrade ghemical to a newer version, it appears that apt would do so without complaint as the dependency does not appear to mandate any particular version of mpqc, as it does with some of the other dependencies. Thanks for answering francesco pietra HTH! cmr Hope this helps, but no warranty is express or implied! :-) cmr -- Debian 'Etch': Registered Linux User #241964 More laws, less justice. -- Marcus Tullius Ciceroca, 42 BC -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com -- Debian 'Etch': Registered Linux User #241964 More laws, less justice. -- Marcus Tullius Ciceroca, 42 BC -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: keep specific versions of packages
--- Mike Reinehr [EMAIL PROTECTED] wrote: On Sunday 24 December 2006 09:03, Francesco Pietra wrote: I want to avoid any modification from apt-get commands to mpqc 2.3.1-0.2 specially compiled for amd64 with libint (which is not included in the package of same version on debian repositories) and installed with dpkg. I.e., I want to avoid downgrading to a version without libint. From apt-cache show mpqc version installed 2.3..1-0.2, though the list of dependencies does not show libint (which is in, because the software deals correctly with integrals that only libint allows to do) According to Silva's APT HOWTO I should manage with /etc/apt/preferences, though there is no such file or directory on my debiam amd64 etch, linux-image-2.6.18-3-amd64. Should I build a file preferences from scratch? I must say that I am not familiar with this aspect of apt. Thanks for advice francesco pietra Francesco, I've been trying to understand pinning from the time I first used Debian, several years now, and still feel that I'm missing something, but I think your problem has a simple solution. I believe all that you need in your /etc/apt/preferences file are the following three lines: Package: mpqc Pin: version 2.3.1-0.2 Pin-Priority: 1000 As I wrote, there is no preferences file on my system. Create from scratch? Besides this, what happens to the libraries if I free a package? For example, I wanted to check the stage of development of ghemical on GNOME, though it ptretends to install mpqc too, which is not compiled for the libraries I need (in part lower, in part lacking). Thanks for answering francesco pietra Hope this helps, but no warranty is express or implied! :-) cmr -- Debian 'Etch': Registered Linux User #241964 More laws, less justice. -- Marcus Tullius Ciceroca, 42 BC -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: keep specific versions of packages
On Sunday 24 December 2006 09:03, Francesco Pietra wrote: I want to avoid any modification from apt-get commands to mpqc 2.3.1-0.2 specially compiled for amd64 with libint (which is not included in the package of same version on debian repositories) and installed with dpkg. I.e., I want to avoid downgrading to a version without libint. From apt-cache show mpqc version installed 2.3..1-0.2, though the list of dependencies does not show libint (which is in, because the software deals correctly with integrals that only libint allows to do) According to Silva's APT HOWTO I should manage with /etc/apt/preferences, though there is no such file or directory on my debiam amd64 etch, linux-image-2.6.18-3-amd64. Should I build a file preferences from scratch? I must say that I am not familiar with this aspect of apt. Thanks for advice francesco pietra Francesco, I've been trying to understand pinning from the time I first used Debian, several years now, and still feel that I'm missing something, but I think your problem has a simple solution. I believe all that you need in your /etc/apt/preferences file are the following three lines: Package: mpqc Pin: version 2.3.1-0.2 Pin-Priority: 1000 Hope this helps, but no warranty is express or implied! :-) cmr -- Debian 'Etch': Registered Linux User #241964 More laws, less justice. -- Marcus Tullius Ciceroca, 42 BC -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
