Your message dated Sun, 19 Jul 2015 17:43:24 +0200 with message-id <[email protected]> and subject line Re: Bug#792644: dpkg --set-selections < list results in 'found unknown packages' has caused the Debian Bug report #792644, regarding dpkg --set-selections < list results in 'found unknown packages' 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 [email protected] immediately.) -- 792644: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=792644 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: dpkg Version: 1.17.25 Severity: important Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? Goal make server1 have same packages as server2. I used dpkg --get-selections > package_list.txt to get list on server1. Then, I used dpkg --set-selections < package_list.txt on server2. A subset of packages generate a warning: package not in database at line <number> : <package name> * What exactly did you do (or not do) that was effective (or ineffective)? I tried installing dselect and running again but found that this bug existed back in 2013. http://debian.2.n7.nabble.com/Bug-703092-dpkg-set-selections-ignores-available-packages-never-installed-or-removed-by-dpkg-td2891633.html * What was the outcome of this action? Error as described above. * What outcome did you expect instead? I expected the new package list to be accepted and packages would install. *** End of the template - remove these template lines *** -- System Information: Debian Release: 8.1 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: i386 (i686) Kernel: Linux 3.16.0-4-686-pae (SMP w/1 CPU core) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages dpkg depends on: ii libbz2-1.0 1.0.6-7+b3 ii libc6 2.19-18 ii liblzma5 5.1.1alpha+20120614-2+b3 ii libselinux1 2.3-2 ii tar 1.27.1-2+b1 ii zlib1g 1:1.2.8.dfsg-2+b1 dpkg recommends no packages. Versions of packages dpkg suggests: ii apt 1.0.9.8 -- no debconf information
--- End Message ---
--- Begin Message ---Hi! On Thu, 2015-07-16 at 20:25:28 -0700, Peter wrote: > Package: dpkg > Version: 1.17.25 > Severity: important > * What led up to the situation? Goal make server1 have same packages as > server2. I used dpkg --get-selections > package_list.txt to get list on > server1. > Then, I used dpkg --set-selections < package_list.txt on server2. > A subset of packages generate a warning: package not in database at line > <number> : <package name> > > * What exactly did you do (or not do) that was effective (or > ineffective)? I tried installing dselect and running again but found > that this bug existed back in 2013. > http://debian.2.n7.nabble.com/Bug-703092-dpkg-set-selections-ignores-available-packages-never-installed-or-removed-by-dpkg-td2891633.html > * What was the outcome of this action? Error as described above. > * What outcome did you expect instead? I expected the new package list to > be accepted and packages would install. This is covered in the FAQ: <https://wiki.debian.org/Teams/Dpkg/FAQ#Q:_Why_does_.27.27dpkg_--set-selections.27.27_not_record_selections_for_unknown_packages.3F> I'm thus closing this report. Thanks, Guillem
--- End Message ---
