Apt provider can't install packages from different default release

I try to fix this in http://github.com/igloonet/chef/tree/CHEF-1547

As I said before, I'm not 100% sure if this is right approach, but it works and don't mix into other providers

marking as resolved so I see it when I merge patches.

I think it might be better to add a default_release attribute to the apt_package resource. That is about the same amount of work/typing for the user, and makes it more explicit why the options are being set for apt-cache. Also, I need to have tests before I can merge the patch so that it is clear why the code is there and we get an early warning if some future patch breaks this feature.

If you need any tips writing rspec tests, feel free to stop by the #chef-hacking channel on irc.freenode.net or ping the dev mailing list.

Thanks

bulk updating fix versions to next release

I have the same problem, and I need to resort to installing a particular version, which is hacky because the version may change in a repository.

Daniel, can you please explain a bit what the state of this bug is? With all the "Fix Version/s" changes I have no idea whether the current state means it's going to be fixed in 0.9.14 or not.

Problem is fixed in my chef repo but I have no time yet to write tests I'll try to do it ASAP because it cause us a lot of trouble (we have to maintain our own repo with changed chef gems)

The best thing I could come up with on this one is to explicitly manage your backports priorities outside of the "package" resource.

• See: http://backports.debian.org/Instructions/
• See: http://www.argon.org/~roderick/apt-pinning.html
• See: http://www.pbandjelly.org/2009/08/lenny-apt-configs/
• See: 'apt-cache policy <pkg>' for what decision will be made (highest wins)

What made sense in my situation was to add the following file:

/etc/apt/apt.conf.d/50lenny-backports:
APT::Default-Release "lenny-backports";

And define the "lenny-backports" release in a file under /etc/apt/sources.list.d/

Then, all of my "package" resources just worked and pulled the latest from lenny-backports, which in my case, was exactly what I wanted.

Hope this helps.

Unfortunatelly, this isn't sufficient solution. Problem is when you need to install only one package from backports which has many dependencies some from backports and some not. It simply don't work 100% as we want according to our tests.

My fix is really working but I have not time yet to submit tests It will be great if anybody volunteer to help with creating rspec tests.

I've pushed an attempt at specs for this to jdsumsion/CHEF-1547. I don't have time right now to set up a chef development environment – and I can't seem to find the HOWTO for that – it needs to be easier to find. If I get back to it, I'll try out the specs and push any fixes.

You can do the same in the meantime if you like.

The simplest workaround would be:

execute "install syslog-ng from backports" do
  command "apt-get -t #{node[:os_codename]}-backports install syslog-ng -y"
  not_if "dpkg-query -W syslog-ng"
end

Hopefully correct fix is in https://github.com/igloonet/chef/tree/CHEF-1547 so please review it and accept if possible.

Tests are included now with use of ones provided by John Sumsion.

Marking resolved with new patch to review at triage.

We need to get a CLA from John Sumsion if we include his tests. John, can you follow the steps outlined in How to Contribute?

Looks good, except we need to either get a CLA from John or not include his test. You can tell we don't have a CLA yet because when you click on his user he isn't in the 'jira-developers' group.

I've signed the CLA, so this can move forward.

CLA issues taken care of, marking resolved.

and also https://github.com/opscode/chef/pull/165/files

what is the status of this triaged ticket, it doesn't seem to have made it in to the main source tree, and I am currently running in to this issue myself? is there a way to get this in to the next release?

This has been merged, thanks everyone!