Forum: CFEngine Help Subject: Utilising debian backports Author: simonblake Link to topic: https://cfengine.com/forum/read.php?3,23725,23725#msg-23725
Hi all Does anybody have some magic foo for dealing with packages from backports on debian/ubuntu systems? I'd like to pull certain newer packages from backports, but keep the bulk of the system from stable. By hand this is relatively straight forward, you add an extra repository as per http://backports-master.debian.org/Instructions/ , and then do something like apt-get -t squeeze-backports pacemaker to install the version of pacemaker from the backports repo, and automatically pull in the miscellaneous other updated packages it depends on. Within cf3 I can not see any way within a promise to tell apt to pull this package from a different repo, *and* satisfy all the dependencies it might have. You can pull in individual packages by going apt-get install pacemaker/squeeze-backports or apt-get install pacemaker=1.1.5-3~bpo60+1 these are less ideal, in that they don't pull in backport dependencies. Specifying minimum version numbers for each package seemed like a bunch of work, so as a workaround, I've done: vars: "packages" slist => {"pacemaker/squeeze-backports", "ocfs2-tools-pacemaker/squeeze-backports", "corosync/squeeze-backports", "libcorosync4/squeeze-backports", "libcluster-glue/squeeze-backports", "resource-agents/squeeze-backports", "ocfs2-tools/squeeze-backports", .... another dozen packages omitted }; packages: debian_6:: "$(packages)" package_policy => "addupdate", package_method => generic; Manual enumeration of the dependencies is pretty ugly, it will probably break if a newer version of a package in the list depends on a package not in the list. Is there someway of avoiding this enumeration that I've missed? Cheers Simon _______________________________________________ Help-cfengine mailing list Help-cfengine@cfengine.org https://cfengine.org/mailman/listinfo/help-cfengine
