[Touch-packages] [Bug 1760810] Re: Non-pinned available package in -proposed not chosen

2018-06-03 Thread Paul Gevers
Please give feedback on my proposed implementation in autopkgtest. It also adds support for submission of versioned packages that need to come from -proposed. https://salsa.debian.org/ci-team/autopkgtest/merge_requests/17 -- You received this bug notification because you are a member of Ubuntu

[Touch-packages] [Bug 1760810] Re: Non-pinned available package in -proposed not chosen

2018-05-19 Thread Paul Gevers
> I'll check, but I think autopkgtest will happily take it. I don't think this is supported by autopkgtest yet. I'll file a bug about that. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu.

Re: [Touch-packages] [Bug 1760810] Re: Non-pinned available package in -proposed not chosen

2018-05-19 Thread Paul Gevers
On 18-05-18 22:23, Julian Andres Klode wrote: > Oh, you got a working result? I tried aspcud in various variants, but I > don't get any solutions. https://bugs.debian.org/cgi- > bin/bugreport.cgi?bug=897330 I think it is wise to provide your command line. (I did one that worked on that bug. > Of

[Touch-packages] [Bug 1760810] Re: Non-pinned available package in -proposed not chosen

2018-05-18 Thread Julian Andres Klode
Oh, you got a working result? I tried aspcud in various variants, but I don't get any solutions. https://bugs.debian.org/cgi- bin/bugreport.cgi?bug=897330 Of course the autopkgtest-sat-dep package should have versioned dependencies and/or on the command-line, versions should be specified IMO. **

[Touch-packages] [Bug 1760810] Re: Non-pinned available package in -proposed not chosen

2018-05-18 Thread Paul Gevers
Hmm, maybe it was just the syntax being wrong. The following line at least succeeded: --solver aspcud -o APT::Solver::Strict-Pinning=false -o APT::Solver::aspcud::Preferences='-removed,-changed,-new,+count(solution ,APT-Pin:=/995/)' Next up, checking that it does what I want. Just a worry that

[Touch-packages] [Bug 1760810] Re: Non-pinned available package in -proposed not chosen

2018-04-21 Thread Paul Gevers
After discussion on IRC (#debian-devel) I filed Debian bug 896506ยน about this failing command. I'll continue to pursue a solution in this area. Maybe (suggested by josch): --solver aspcud -o APT::Solver::Strict-Pinning=false -o

[Touch-packages] [Bug 1760810] Re: Non-pinned available package in -proposed not chosen

2018-04-20 Thread Paul Gevers
@juliank: I tried your command (with --simulate) on my own laptop and with this option it says that gnome can't be installed, while plain apt will happily install it. For the history I'll attach my logging. ** Attachment added: "logging of installing gnome with and without aspcud solver"

Re: [Touch-packages] [Bug 1760810] Re: Non-pinned available package in -proposed not chosen

2018-04-03 Thread Iain Lane
On Tue, Apr 03, 2018 at 09:26:55AM -, Julian Andres Klode wrote: > APT, by design, only picks candidate versions when installing > dependencies, and the non-pinned proposed version is not the candidate. > apt install foo/target has some logic to switch dependencies to target > too, which works

[Touch-packages] [Bug 1760810] Re: Non-pinned available package in -proposed not chosen

2018-04-03 Thread Julian Andres Klode
sbuild passes: --solver aspcud -o APT::Solver::Strict-Pinning=false -o 'APT::Solver::aspcud::Preferences=-removed,-changed,-new,+sum(solution ,apt-pin)' That probably works here too. I guess I'd try without, and then fall back to it if pure APT can't handle it. -- You received this bug

[Touch-packages] [Bug 1760810] Re: Non-pinned available package in -proposed not chosen

2018-04-03 Thread Julian Andres Klode
APT, by design, only picks candidate versions when installing dependencies, and the non-pinned proposed version is not the candidate. apt install foo/target has some logic to switch dependencies to target too, which works sometimes, but it's nothing that happens when using pinning. ** Changed in: