[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#855024: marked as done (apt-get install <package>/<target> does not fetch dependencies from <target>)

Your message dated Tue, 28 Mar 2017 20:37:26 +0200
with message-id <20170328183726.ib2uq2lsapcf3wmy@crossbow>
and subject line Re: Bug#855024: Install nvidia-driver package from jessie-backports using different methods
has caused the Debian Bug report #855024,
regarding apt-get install <package>/<target> does not fetch dependencies from <target>
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
855024: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=855024
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: nvidia-driver
Version: 375.26-1~bpo8+1
I have tried two different methods to install the 'nvidia-driver' package from the 'jessie-backports' repository using 'apt-get' and only one method succeeds. As far as I know you can install a package from 'jessie-backports' by using two different methods. Method one would be to use the option 'apt-get install -t jessie-backports nvidia-driver' and the second one would be 'apt-get install nvidia-driver/jessie-backports'. But the second method fails for the 'nvidia-driver' package. 

Here is a sample output from both commands:

# apt-get install -t jessie-backports nvidia-driver
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following extra packages will be installed:
dkms glx-alternative-mesa glx-alternative-nvidia glx-diversions libdrm-amdgpu1 libdrm-intel1 libdrm-nouveau2 libdrm-radeon1 libdrm2 libegl-nvidia0 libegl1-glvnd-nvidia libegl1-mesa libepoxy0 libfontenc1 libgbm1 libgl1-glvnd-nvidia-glx libgl1-mesa-dri libgl1-mesa-glx libgl1-nvidia-glvnd-glx libglapi-mesa libgldispatch0-nvidia libgles-nvidia1 libgles-nvidia2 libgles1-glvnd-nvidia libgles2-glvnd-nvidia libglx-nvidia0 libglx0-glvnd-nvidia libjansson4 libllvm3.8 libnvidia-cfg1 libnvidia-eglcore libnvidia-glcore libnvidia-ml1 libopengl0-glvnd-nvidia libpciaccess0 libtxc-dxtn-s2tc0 libvdpau1 libvulkan1 libwayland-client0 libwayland-server0 libxaw7 libxcb-dri2-0 libxcb-dri3-0 libxcb-glx0 libxcb-present0 libxcb-shape0 libxcb-sync1 libxcb-xfixes0 libxfont1 libxkbfile1 libxmu6 libxnvctrl0 libxshmfence1 libxt6 libxxf86vm1 linux-headers-4.9.0-0.bpo.1-amd64 linux-headers-4.9.0-0.bpo.1-common linux-headers-amd64 linux-kbuild-4.9 nvidia-alternative nvidia-driver-bin nvidia-driver-libs nvidia-egl-common nvidia-egl-icd nvidia-installer-cleanup nvidia-kernel-common nvidia-kernel-dkms nvidia-kernel-support nvidia-legacy-check nvidia-modprobe nvidia-persistenced nvidia-settings nvidia-support nvidia-vdpau-driver nvidia-vulkan-common nvidia-vulkan-icd update-glx x11-xkb-utils xfonts-base xfonts-encodings xfonts-utils xserver-common xserver-xorg-core xserver-xorg-video-nvidia 
Suggested packages:
python3-apport menu vulkan-utils xfs xserver xfonts-100dpi xfonts-75dpi xfonts-scalable 
Recommended packages:
  nvidia-driver-libs-i386
The following NEW packages will be installed:
dkms glx-alternative-mesa glx-alternative-nvidia glx-diversions libdrm-amdgpu1 libdrm-intel1 libdrm-nouveau2 libdrm-radeon1 libegl-nvidia0 libegl1-glvnd-nvidia libegl1-mesa libepoxy0 libfontenc1 libgbm1 libgl1-glvnd-nvidia-glx libgl1-mesa-dri libgl1-mesa-glx libgl1-nvidia-glvnd-glx libglapi-mesa libgldispatch0-nvidia libgles-nvidia1 libgles-nvidia2 libgles1-glvnd-nvidia libgles2-glvnd-nvidia libglx-nvidia0 libglx0-glvnd-nvidia libjansson4 libllvm3.8 libnvidia-cfg1 libnvidia-eglcore libnvidia-glcore libnvidia-ml1 libopengl0-glvnd-nvidia libpciaccess0 libtxc-dxtn-s2tc0 libvdpau1 libvulkan1 libwayland-client0 libwayland-server0 libxaw7 libxcb-dri2-0 libxcb-dri3-0 libxcb-glx0 libxcb-present0 libxcb-shape0 libxcb-sync1 libxcb-xfixes0 libxfont1 libxkbfile1 libxmu6 libxnvctrl0 libxshmfence1 libxt6 libxxf86vm1 linux-headers-4.9.0-0.bpo.1-amd64 linux-headers-4.9.0-0.bpo.1-common linux-headers-amd64 linux-kbuild-4.9 nvidia-alternative nvidia-driver nvidia-driver-bin nvidia-driver-libs nvidia-egl-common nvidia-egl-icd nvidia-installer-cleanup nvidia-kernel-common nvidia-kernel-dkms nvidia-kernel-support nvidia-legacy-check nvidia-modprobe nvidia-persistenced nvidia-settings nvidia-support nvidia-vdpau-driver nvidia-vulkan-common nvidia-vulkan-icd update-glx x11-xkb-utils xfonts-base xfonts-encodings xfonts-utils xserver-common xserver-xorg-core xserver-xorg-video-nvidia 
The following packages will be upgraded:
  libdrm2
1 upgraded, 84 newly installed, 0 to remove and 104 not upgraded.
Need to get 67.5 MB of archives.
After this operation, 256 MB of additional disk space will be used.
Do you want to continue? [Y/n] ^C

# apt-get install nvidia-driver/jessie-backports
Reading package lists... Done
Building dependency tree
Reading state information... Done
Selected version '375.26-1~bpo8+1' (Debian Backports:jessie-backports [amd64]) for 'nvidia-driver' 
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
nvidia-driver : Depends: nvidia-driver-libs (= 375.26-1~bpo8+1) but it is not going to be installed Depends: nvidia-driver-bin (= 375.26-1~bpo8+1) but it is not going to be installed Depends: xserver-xorg-video-nvidia (= 375.26-1~bpo8+1) but it is not going to be installed Depends: nvidia-vdpau-driver (= 375.26-1~bpo8+1) but it is not going to be installed Depends: nvidia-alternative (= 375.26-1~bpo8+1) but it is not going to be installed Depends: nvidia-kernel-dkms (= 375.26-1~bpo8+1) but it is not going to be installed or 
                          nvidia-kernel-375.26
Recommends: nvidia-settings (>= 375) but it is not going to be installed Recommends: nvidia-persistenced but it is not going to be installed 
E: Unable to correct problems, you have held broken packages.
As you can see the second commands fails as a result of unsolved dependencies. The previous version of the 'nvidia-driver' package '367.57-2~bpo8+1' could be installed using both methods. 

Some info about my system:
$ uname -o -m -r -v
3.16.0-4-amd64 #1 SMP Debian 3.16.7-ckt25-1 (2016-03-06) x86_64 GNU/Linux

--- End Message ---
--- Begin Message --- 
On Mon, Mar 27, 2017 at 03:27:50PM +0100, Adam D. Barratt wrote:
> [fwiw, due to the way the bug was reassigned, it's entirely possible that
> none of the maintainers actually saw your original query - all that the
> mailing list received was
> https://lists.debian.org/deity/2017/02/msg00051.html ]
> 
> On 2017-03-27 12:51, Markus Lindberg wrote:
> > Could anyone at least point me in the right direction?
> 
> So far as I can tell, what you're seeing is expected behaviour.

Yes, which is why I am closing this bugreport. The "error" message could
surely be better, but there are various open bugreports about that
already and it would be a massive project which from experience tend to
be hindered by collections of multiple vague bugreports more than that
they help…


> "apt-get install foo/jessie-backports" says "install foo from
> jessie-backports but otherwise respect apt's policy on which release
> packages should be installed from", so will not pull in any other packages
> from backports unless you've added explicit pinning to make that happen.

apt tries to be a tiny bit more helpful here in that if foo/backports
has a direct and obvious dependency which can't be statisfied by the
current candidate but could be if that package is also picked from
jessie-backports it will do so (with the same switching message as for
foo), so that in the best and simplest cases that does what is needed.

But that really only follows dependencies like "foo depends foo-data (=
bpo)", nothing more complex like conflicts resulting from using certain
versions.

The obvious guess is hence that simple was enough in the older versions,
but the newer one has additional requirements which aren't as simple and
need hence more handholding and/or the allowance from the user to do
'more'.

See also #858537 which had a similar topic and explains related matters.


Best regards

David Kalnischkies

Attachment: signature.asc
Description: PGP signature


--- End Message ---
Reply to: