Your message dated Tue, 24 Feb 2009 15:17:11 +0000 with message-id <e1lbz1z-0000os...@ries.debian.org> and subject line Bug#516728: fixed in apt-xapian-index 0.18 has caused the Debian Bug report #516728, regarding update-a-x-i should not run under pbuilder and similar systems 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 ow...@bugs.debian.org immediately.) -- 516728: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=516728 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---Package: apt-xapian-index Severity: serious On Mon, Feb 23, 2009 at 12:02:32PM +0900, Junichi Uekawa wrote: We drifted a bit away from the original bug report, and I think this issue deserves its own bug number. > > That's a good point. How come your pbuilder setup installs > > apt-xapian-index? It's usually pulled in by aptitude, but as a > > Recommends, not a Depends. In theory, buildds and pbuilder chroots > > shouldn't install Recommends, or am I mistaken? > aptitude is depending on apt-xapian-index. > Package: aptitude [...] > Depends: apt-xapian-index, libapt-pkg-libc6.7-6-4.6, libc6 (>= 2.7-1), > libcwidget3, libept0 (>= 0.5.26), libgcc1 (>= 1:4.1.1), libncursesw5 (>= > 5.6+20071006-3), libsigc++-2.0-0c2 > a (>= 2.0.2), libstdc++6 (>= 4.2.1), libxapian15, zlib1g (>= 1:1.1.4) Oh, no. I've opened a bug with aptitude asking if it can be downgraded to a Recommends (#516719). I'm happy to have aptitude on my openmoko, but I certainly don't want to have apt-xapia-index in it. > > I'd be happy to work out a way not to have apt-xapian-index run in cases > > like pbuilder. Is invoke-rc.d the only tool that honours the init > > script policy? Would it be acceptable if apt-xapian-index's postinst > > checked with policy-rc.d to see if it should run the reindexing or not? > For pbuillder specific, it's okay to check for policy-rc.d output. Where can I find instructions on how to query policy-rc.d for this specific case? Can it be just a case of: if [ ! -x /usr/sbin/policy-rc.d ] || /usr/sbin/policy-rc.d apt-xapian-index start then update-apt-xapian-index --quiet & fi > So, you really don't need the data until a client application requests > it. The first invocation can probably wait, and the invocation afterwards > can wait > > Or you can make installation wait for the rebuild of database. > There isn't much point in making it run in background. The point is that the rebuild takes time, and a common use case is that the data is needed by the package manager just after apt-xapian-index is installed for the first time. Rebuilding in background means that when the installation is finished and we're back to the package manager, the data will be almost readily available, instead of having to look at a progress bar for a minute or two. > If it's a long process, you should take care to make it run in the > background maybe niced. You're right here, I had forgot to nice it. I've fixed that in git. > Well, because you are running the indexing in background, it is > reasonable that someone would want to stop it, and if stopping is > possible, a restart/start. update-apt-xapian-index --stop to stop a running background indexer is certainly a good idea: I've added it to the todo list (bug#TODO-TO-BE-ASSIGNED). Restarting it is just a matter of running update-apt-xapian-index again. > > However, I 100% agree that update-a-x-i must NOT run on chroots and slow > > down builds. Let's find a way to do so. Here are the options that I > > can think of: > > - Study how policy-rc.d works, and query it in postinst to see if I > > should run the update or not > > - What does man-db do to prevent the index update? > Probably, man-db just rebuilds the index now in triggers. I don't mind to use triggers, but I understand that they are only run at the end of the installation, so it would defeat the idea to start it soon so that at the end of the installation it's almost done. Or is there a way to start triggers sooner? > > - Disabling the update in postinst via a preseedable debconf > > low-priority question > Feasible, but that is probably counterintuitive for users, and I need > a hack for apt-xapian-index in pbuilder. Indeed. It could still be useful in other cases, but not for pbuilder. It seems that the best way so far is to check policy-rc.d. I've never used it, nor I found documentation about how to query it, so I inferred from invoke-rc.d source code. If you confirm me the code snippet above on how to query it, I'll be happy to make an upload right away. Ciao, Enrico -- GPG key: 1024D/797EBFAB 2000-12-05 Enrico Zini <enr...@debian.org>
signature.asc
Description: Digital signature
--- End Message ---
--- Begin Message ---Source: apt-xapian-index Source-Version: 0.18 We believe that the bug you reported is fixed in the latest version of apt-xapian-index, which is due to be installed in the Debian FTP archive: apt-xapian-index_0.18.dsc to pool/main/a/apt-xapian-index/apt-xapian-index_0.18.dsc apt-xapian-index_0.18.tar.gz to pool/main/a/apt-xapian-index/apt-xapian-index_0.18.tar.gz apt-xapian-index_0.18_all.deb to pool/main/a/apt-xapian-index/apt-xapian-index_0.18_all.deb A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 516...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Enrico Zini <enr...@debian.org> (supplier of updated apt-xapian-index package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@debian.org) -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Format: 1.8 Date: Tue, 24 Feb 2009 15:08:57 +0000 Source: apt-xapian-index Binary: apt-xapian-index Architecture: source all Version: 0.18 Distribution: unstable Urgency: low Maintainer: Enrico Zini <enr...@debian.org> Changed-By: Enrico Zini <enr...@debian.org> Description: apt-xapian-index - maintenance tools for a Xapian index of Debian packages Closes: 516728 Changes: apt-xapian-index (0.18) unstable; urgency=low . * Run the background update niced. * Check policy-rc.d to see if it should start update-apt-xapian-index in the background. Closes: #516728. Checksums-Sha1: 8fc5e1305b50863ca34e77dfa8f9693ee94b79c5 1559 apt-xapian-index_0.18.dsc 13473ec8c4a83f816570881c81e3934e1e5bba49 22987 apt-xapian-index_0.18.tar.gz aff98c44743d57b43ac218bf73513f528d18477e 32860 apt-xapian-index_0.18_all.deb Checksums-Sha256: c7f256ce597b7f84a2fade8ac54c9cc9618afdcc1619cd03dd430e18bdc72dcf 1559 apt-xapian-index_0.18.dsc 61762ecf045c92cc1dc5c4eb2be565e45416965aeaa2eba851d43a86142f62bd 22987 apt-xapian-index_0.18.tar.gz 16b0cfa54691c4f171f57188057f718872775821779662cee5249845d4f49c4b 32860 apt-xapian-index_0.18_all.deb Files: 801b34221820daee4abe5abb484a21db 1559 admin optional apt-xapian-index_0.18.dsc 698393e840539dc65ff5f92f29cc6e3a 22987 admin optional apt-xapian-index_0.18.tar.gz 0b05ba887cefd0c1c573ea4e46d7bde4 32860 admin optional apt-xapian-index_0.18_all.deb -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) iQIcBAEBAgAGBQJJpA4cAAoJEB5qw/OH8O2sA7QP/R+MQ7iST8xA+sdumu0e3qKu Zc9sv3egAJi8vgPHkDYsFzWUJiJugkm1ZPA4PRBG7OzsGCXOSl4attFUczy/bL10 RTH2gptBoPx+vML+CNhqIBgKhR/xIU1QyoQczphb8AIxNnPwLxBig1tx54eK6cd9 LHuaOp/MRGvOW3GpzC5ipYIfAKgtxp0oY+fT3aNy3BgH6bjH6Sh27VL5PX+Rhg+J /iE4UP/XG5+kld+5vPwaHIjOaQ1HJiS3c/zIP4MsTY2EVl9rw7srFgW3u8r2c8VZ M+9tly05Xe9aFYLlQkWSJXsqD6vn8TzXqe8WF2yQ/VIPZImVStAv+1GKYyjMsXhB vQlEA26JIJj/XYy5vVS22mMmhiUTqY++CAhuRyupqVkhsw0RYD35mgMSXSqR0plI 1qWJf8pJnbnDU7aXeT2F49BaO3DueiHduh5BdqOTJ1i4dBOtKwFn1cogzoRnMQ2A aOFpHaQFEbUxTTLAA0961c+EScUxIu7mKrbcOETB89qh4MuzswaFrJtpaCvqL6sW sdof1xqy7zawXFxLgkezroCstuqC88spVSJ5CaoGKv9ZG+vagAUCHoncqmdLLtBN qo6LWP8NqnGgfhr7kdIn9tc0gWoL8bh23mmi++wyaEpDFG+QVggaU4eVv3IEMlkH 9esFBwz/HXV6sX/V69Vp =rbC6 -----END PGP SIGNATURE-----
--- End Message ---
