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

Bug#679401: packages.debian.org: searching packages by file name does not list results for unstable but does for testing?

Control: tag -1 patch

On Thu, Jun 28, 2012 at 03:38:45PM +0300, Timo Juhani Lindfors wrote:
> Both testing and unstable have libssl-dev with openssl/ssl.h but only
> the testing search finds it:
> http://packages.debian.org/search?searchon=contents&keywords=openssl%2Fssl.h&mode=path&suite=unstable&arch=any
> => Sorry, your search gave no results
> http://packages.debian.org/search?searchon=contents&keywords=openssl%2Fssl.h&mode=path&suite=testing&arch=any
> => /usr/include/openssl/ssl.h	 libssl-dev

This appears to be a matter of too much data and not enough /tmp.
Attached patch will stave off the issue for now.

GPG Key: 4096R/331BA3DB 2011-12-05 James McCoy <jamessan@debian.org>
From 279f30b2cc12f9161d58fccd02f2d357240ae908 Mon Sep 17 00:00:00 2001
From: James McCoy <jamessan@debian.org>
Date: Sun, 19 Aug 2012 22:44:26 -0400
Subject: [PATCH] Use --compress-prog=gzip when sorting reverse_${suite}_*.txt

Attempting to sort ~8GiB of text (all the reverse_sid_*.txt files) with 2GiB
of /tmp available doesn't work very well.  Instructing sort(1) to compress the
temporary files works around this problem.

Closes: #679401
Signed-off-by: James McCoy <jamessan@debian.org>
 bin/parse-contents |    2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/bin/parse-contents b/bin/parse-contents
index 16bc7e4..7a488c1 100755
--- a/bin/parse-contents
+++ b/bin/parse-contents
@@ -162,7 +162,7 @@ for my $suite (@suites) {
     print "Merging reverse path lists for ${suite}...\n";
-    open MERGED, "-|", "sort -m $DBDIR/reverse_${suite}_*.txt"
+    open MERGED, "-|", "sort -m --compress-prog=gzip $DBDIR/reverse_${suite}_*.txt"
 	or die "Failed to open merged list";
     open FILENAMES, ">", "$DBDIR/filenames_$suite.txt.new"
 	or die "Failed to open filenames list";

Attachment: signature.asc
Description: Digital signature

Reply to: