Public bug reported: dpkg --set-selections does not work any more to find packages that have not already been installed on the system. If new packages are introduced, an error is produced with no effect on the selections. In the example below, "tidy" has not yet been installed on the system, but it gives the same result with any other package that has not yet been installed:
echo "tidy install" | dpkg --set-selections dpkg: warning: package not in database at line 1: tidy What should happen is that the package state be set properly so that "apt-get dselect upgrade" works. This might be related to Debian bug 684776 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=684776 ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: dpkg 1.16.10ubuntu3 ProcVersionSignature: Ubuntu 3.11.0-9.16-generic 3.11.2 Uname: Linux 3.11.0-9-generic x86_64 ApportVersion: 2.12.5-0ubuntu1 Architecture: amd64 Date: Sun Sep 29 10:12:58 2013 InstallationDate: Installed on 2013-09-26 (2 days ago) InstallationMedia: Lubuntu 13.10 "Saucy Salamander" - Beta amd64+mac (20130925) MarkForUpload: True SourcePackage: dpkg UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: dpkg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug saucy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1232661 Title: dpkg --set-selections : dpkg: warning: package not in database To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dpkg/+bug/1232661/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
