Your message dated Wed, 23 Nov 2016 02:01:49 +0100 with message-id <[email protected]> and subject line Re: [Aptitude-devel] Bug#818919: aptitude runs wild has caused the Debian Bug report #818919, regarding aptitude markauto runs wild, if package does not exist 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.) -- 818919: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=818919 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: aptitude Version: 0.7.8-1 Severity: normal Tags: upstream Dear Maintainer, If PATTERN does not match a package, the command aptitude markauto PATTERN does not stop, using 100% CPU. Example aptitude markauto 1234 The same is true for "aptitude forbid-version". Regards, Martin -- Package-specific info: Terminal: linux $DISPLAY not set. which aptitude: /usr/bin/aptitude aptitude version information: aptitude 0.7.8 Compiler: g++ 5.3.1 20160224 Compiled against: apt version 5.0.0 NCurses version 6.0 libsigc++ version: 2.6.2 Gtk+ support disabled. Qt support disabled. Current library versions: NCurses version: ncurses 6.0.20160213 cwidget version: 0.5.17 Apt version: 5.0.0 aptitude linkage: linux-vdso.so.1 (0x00007ffe82493000) libapt-pkg.so.5.0 =3D> /usr/lib/x86_64-linux-gnu/libapt-pkg.so.5.0 (0x00= 007f304c83a000) libncursesw.so.5 =3D> /lib/x86_64-linux-gnu/libncursesw.so.5 (0x00007f30= 4c60a000) libtinfo.so.5 =3D> /lib/x86_64-linux-gnu/libtinfo.so.5 (0x00007f304c3df0= 00) libsigc-2.0.so.0 =3D> /usr/lib/x86_64-linux-gnu/libsigc-2.0.so.0 (0x0000= 7f304c1d9000) libcwidget.so.3 =3D> /usr/lib/x86_64-linux-gnu/libcwidget.so.3 (0x00007f= 304bedc000) libsqlite3.so.0 =3D> /usr/lib/x86_64-linux-gnu/libsqlite3.so.0 (0x00007f= 304bbe4000) libboost_iostreams.so.1.58.0 =3D> /usr/lib/x86_64-linux-gnu/libboost_ios= treams.so.1.58.0 (0x00007f304b9ca000) libboost_filesystem.so.1.58.0 =3D> /usr/lib/x86_64-linux-gnu/libboost_fi= lesystem.so.1.58.0 (0x00007f304b7b1000) libboost_system.so.1.58.0 =3D> /usr/lib/x86_64-linux-gnu/libboost_system= .so.1.58.0 (0x00007f304b5ac000) libxapian.so.22 =3D> /usr/lib/x86_64-linux-gnu/libxapian.so.22 (0x00007f= 304b1a8000) libpthread.so.0 =3D> /lib/x86_64-linux-gnu/libpthread.so.0 (0x00007f304a= f8b000) libstdc++.so.6 =3D> /usr/lib/x86_64-linux-gnu/libstdc++.so.6 (0x00007f30= 4ac0f000) libm.so.6 =3D> /lib/x86_64-linux-gnu/libm.so.6 (0x00007f304a911000) libgcc_s.so.1 =3D> /lib/x86_64-linux-gnu/libgcc_s.so.1 (0x00007f304a6fb0= 00) libc.so.6 =3D> /lib/x86_64-linux-gnu/libc.so.6 (0x00007f304a356000) libutil.so.1 =3D> /lib/x86_64-linux-gnu/libutil.so.1 (0x00007f304a153000= ) libdl.so.2 =3D> /lib/x86_64-linux-gnu/libdl.so.2 (0x00007f3049f4f000) libresolv.so.2 =3D> /lib/x86_64-linux-gnu/libresolv.so.2 (0x00007f3049d3= 7000) libz.so.1 =3D> /lib/x86_64-linux-gnu/libz.so.1 (0x00007f3049b1c000) libbz2.so.1.0 =3D> /lib/x86_64-linux-gnu/libbz2.so.1.0 (0x00007f304990c0= 00) liblzma.so.5 =3D> /lib/x86_64-linux-gnu/liblzma.so.5 (0x00007f30496e8000= ) liblz4.so.1 =3D> /usr/lib/x86_64-linux-gnu/liblz4.so.1 (0x00007f30494d60= 00) librt.so.1 =3D> /lib/x86_64-linux-gnu/librt.so.1 (0x00007f30492cd000) libuuid.so.1 =3D> /lib/x86_64-linux-gnu/libuuid.so.1 (0x00007f30490c8000= ) /lib64/ld-linux-x86-64.so.2 (0x000055e066e92000) -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (990, 'testing'), (50, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.5.0-00038-gafaea24 (SMP w/4 CPU cores) Locale: LANG=3Dde_DE, LC_CTYPE=3Dde_DE (charmap=3DISO-8859-1) Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) Versions of packages aptitude depends on: ii aptitude-common 0.7.8-1 ii libapt-pkg5.0 1.2.6 ii libboost-filesystem1.58.0 1.58.0+dfsg-5+b1 ii libboost-iostreams1.58.0 1.58.0+dfsg-5+b1 ii libboost-system1.58.0 1.58.0+dfsg-5+b1 ii libc6 2.22-3 ii libcwidget3v5 0.5.17-4+b1 ii libgcc1 1:5.3.1-11 ii libncursesw5 6.0+20160213-1 ii libsigc++-2.0-0v5 2.6.2-1 ii libsqlite3-0 3.11.1-1 ii libstdc++6 5.3.1-11 ii libtinfo5 6.0+20160213-1 ii libxapian22v5 1.2.22-3 Versions of packages aptitude recommends: ii aptitude-doc-en [aptitude-doc] 0.7.5-3 ii libparse-debianchangelog-perl 1.2.0-8 ii sensible-utils 0.0.9 Versions of packages aptitude suggests: pn apt-xapian-index <none> pn debtags <none> pn tasksel <none> -- no debconf information
--- End Message ---
--- Begin Message ---Hi Martin, please always Cc the bug itself when adding such information. In this case I'll more or less fully quote your mail so you don't need to resend it. [email protected] schrieb am Wed, Nov 23, 2016 at 12:37:57AM +0100: > the original problem with "aptitude markauto 1234" (and with > "forbid-version") is also solved for me: > > # time aptitude markauto 1234 > Kein solches Paket »1234« > > real 0m1,166s > user 0m1,132s > sys 0m0,028s > > (thanks!) Great! Closing the bug herewith. Not sure which apt or aptitude version actually fixed it, though. I though assume it's either a later 1.2.x apt release or an early 1.3.x release. > On the other hand I need much longer for "aptitude search > '?description(1234)'" > > $ time aptitude search '?description(1234)' > p golang-github-jinzhu-now-dev - time toolkit for golang > p libmath-nocarry-perl - Perl module for no carry arithmetic > p libnxml0 - C library for parsing, writing and > creatin > p libnxml0:i386 - C library for parsing, writing and > creatin > p libnxml0-dbg - shared libraries with debugging symbols > fo > p libnxml0-dbg:i386 - shared libraries with debugging symbols > fo > p libnxml0-dev - static library and C header files for > libn > p libnxml0-dev:i386 - static library and C header files for > libn > p libscalar-properties-perl - perl module to add run-time properties > on > p modem-cmd - send arbitrary AT commands to your modem > p modem-cmd:i386 - send arbitrary AT commands to your modem > p postgresql-9.6-prefix - Prefix Range module for PostgreSQL > p postgresql-9.6-prefix:i386 - Prefix Range module for PostgreSQL > p tcs - Zeichensatzbersetzer > p tcs:i386 - Zeichensatbersetzer > > real 3m33,786s > user 3m9,736s > sys 0m23,984s > > (This is a T450s with an SSD, the relevant files should be > on tempfs) Interesting. I indeed would have expected that an approximately 1.5 to 2 years old Thinkpad with SSD will be faster than my Xen DomU (VM) on a only a few months old server with RAID 1 over classic spinning disks. But then again, there are too many variables (CPU, amount of free RAM, actually cached stuff, amount and size of repositories in sources.list, etc.) that might influence the difference. Although I can't really imagine they make up factor 9 even though that server has a rather powerful CPU (Intel Xeon E5-2650). But since aptitude doesn't split the work (or at least that kind of work) over multiple processes or threads, it won't gain that much from a CPU with 10 cores. My VM has unstable, testing, stable and experimental as well as buildd-unstable, buildd-experimental, unstable-debug and experimental-debug plus some rather small 3rd party repos in its sources.list and is also multiarch amd64/i386. So that's a not so small to-be-cached package list in the end, either. Nevertheless even now, hours later where the data is probably no more cached, I still get the result within 24 seconds. On another machine (real hardware, Quad-Core i7 Skylake, lots of RAM, SSDs below, but no stable and only one architecture) it even only takes 1.5 seconds (without GzipIndexes). But there it takes also much more time, if GzipIndexes is enabled: 3m23s -- close to your value. So I currently assume I missed something on that VM where it was both times around 24s. But then again, I had on both machines the same issues with debtags if GzipIndexes was enabled, so somewhere enabling it made a difference. In the end, a slow down in average is expected with GzipIndexes on, but this difference seems to affect way fewer cases than in the past -- which is good. Regards, Axel -- ,''`. | Axel Beckert <[email protected]>, http://people.debian.org/~abe/ : :' : | Debian Developer, ftp.ch.debian.org Admin `. `' | 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5 `- | 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE
--- End Message ---
_______________________________________________ Aptitude-devel mailing list [email protected] http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/aptitude-devel
