Re: Intersection of installed packages with orphaned packages
Stephen Quinney <[EMAIL PROTECTED]> writes: > On Fri, Apr 08, 2005 at 07:14:23PM +1000, Matthew Palmer wrote: >> On Fri, Apr 08, 2005 at 02:12:13AM -0700, Stephen Birch wrote: >> > I am interested in the intersection of packages installed on my >> > machines with the list of orphaned packages. >> >> You'd be wanting wnpp-check, in the devscripts package. Check out rc-check >> while you're at it. Both are cronable. > > I think you mean wnpp-alert and rc-alert (at least that's what they > seem to be called on my sid machine). On my systems, wnpp-alert lists packages that I don't have installed. For example: # wnpp-alert ... O 279824 perlftlib -- Perl module for the FreeType library ... # dpkg -l \*perlftlib\* No packages found matching *perlftlib*. Any idea why this might be happening? Thanks, Dan -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Intersection of installed packages with orphaned packages
Jeroen van Wolffelaar <[EMAIL PROTECTED]> writes: >> On my systems, wnpp-alert lists packages that I don't have installed. >> For example: >> >> # wnpp-alert >> ... >> O 279824 perlftlib -- Perl module for the FreeType library >> ... >> # dpkg -l \*perlftlib\* >> No packages found matching *perlftlib*. > > perlftlib is a source package, producing the binary packages fttools and > libft-perl. I guess you have one of these two installed. Thanks, I suspected something like that. Wouldn't it make more sense for wnpp-alert to list the binary packages that are installed? What's the command to find out which binary packages a source package produces? Dan -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
upgrading only urgency=high packages
Is there a way to upgrade all currently installed packages which have had an urgency=high version uploaded to the archive since I last upgraded? (And any necessary dependencies, of course.) I'm thinking of this for the unstable distribution. The idea is to frequently do such upgrades to get any security fixes, and less frequently do an entire dist-upgrade. (I know about testing, but for the machine in question I like to stay current with unstable most of the time.) I'm guessing that the information about the urgency fields might not be available except in the changelog, so it might be necessary to download the package and have a script look through the changelog. Could apt-listchanges be hacked to do this? Or could apt's new pinning mechanism help? Is urgency information stored anywhere besides the changelog? How do the testing scripts do this? Thanks for any suggestions, Dan
Re: upgrading only urgency=high packages
Matt Zimmerman <[EMAIL PROTECTED]> writes: > On Tue, May 01, 2001 at 02:12:24PM -0400, Dan Christensen wrote: > > > Is there a way to upgrade all currently installed packages which have > > had an urgency=high version uploaded to the archive since I last > > upgraded? > > I had an idea (and a working script) to extract changelogs from source > packages > and insert them into a SQL database. My original intention was to allow > apt-listchanges to display changelogs for packages before downloading them, > but > such a database would also allow for queries like this. It would also allow > the CGI changelog viewer to work again. > > If the daily lintian runs start up again, this script could easily be run when > a source package is unpacked, to keep the database up-to-date as new packages > come into the archive. These ideas sound great to me. In case they don't get implemented, or until they do, would it be hard to cook up a script that does what I want, even if it involves downloading the packages to see the changelogs? Can I get apt to print out the .deb's it is going to install? Something like "apt-get -s dist-upgrade | grep Inst", but with output suitable for apt-listchanges. This would be enough for me to cook up something, I think, although it would be a bit awkward. Dan
Re: upgrading only urgency=high packages
Matt Zimmerman <[EMAIL PROTECTED]> writes: > On Wed, May 02, 2001 at 08:38:23PM -0400, Dan Christensen wrote: > > > These ideas sound great to me. In case they don't get implemented, or until > > they do, would it be hard to cook up a script that does what I want, even if > > it involves downloading the packages to see the changelogs? > > If you don't mind downloading the packages, you can just use apt-listchanges. > It will sort its output by urgency, and you can use that information to decide > which packages to install. But I want the list of urgency=high packages to be generated and installed automatically. Even if I didn't want to do this automatically, apt-listchanges doesn't give me a way to tell apt to install just some of the proposed packages. This would be a great (orthogonal) feature, but would probably be tricky to implement. (I dare you to prove me wrong, though!) (I already use apt-listchanges, and am a big fan of it, by the way. Thanks for such a great tool.) Dan
