Your message dated Sun, 8 Nov 2015 00:23:33 +0000
with message-id <[email protected]>
and subject line Re: should wait for lock to be released instead of terminating
has caused the Debian Bug report #498424,
regarding should wait for lock to be released instead of terminating
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.)
--
498424: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=498424
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: aptitude
Version: 0.4.11.8-1
Severity: wishlist
Here's the scenario where I want aptitude to serve me better:
1. I run a dist-upgrade, chugging away
2. I discover that I want to install something
3. I run aptitude again while the dist-upgrade is running
4. Aptitude fails to acquire the lock and terminates
Here's the alternate step 4:
4. Aptitude polls the lock until it acquires it, then proceeds.
That way, aptitude is fire-and-forget instead of requiring babysitting :)
-- Package-specific info:
aptitude 0.4.11.8 compiled at Jul 4 2008 16:43:39
Compiler: g++ 4.3.1
Compiled against:
apt version 4.6.0
NCurses version 5.6
libsigc++ version: 2.0.18
Ept support enabled.
Current library versions:
NCurses version: ncurses 5.6.20080804
cwidget version: 0.5.12
Apt version: 4.6.0
linux-gate.so.1 => (0xb7f92000)
libapt-pkg-libc6.7-6.so.4.6 => /usr/lib/libapt-pkg-libc6.7-6.so.4.6
(0xb7eb8000)
libncursesw.so.5 => /lib/libncursesw.so.5 (0xb7e7a000)
libsigc-2.0.so.0 => /usr/lib/libsigc-2.0.so.0 (0xb7e73000)
libcwidget.so.3 => /usr/lib/libcwidget.so.3 (0xb7daf000)
libept.so.0 => /usr/lib/libept.so.0 (0xb7cee000)
libxapian.so.15 => /usr/lib/libxapian.so.15 (0xb7b98000)
libz.so.1 => /usr/lib/libz.so.1 (0xb7b83000)
libpthread.so.0 => /lib/i686/cmov/libpthread.so.0 (0xb7b6a000)
libstdc++.so.6 => /usr/lib/libstdc++.so.6 (0xb7a7b000)
libm.so.6 => /lib/i686/cmov/libm.so.6 (0xb7a55000)
libgcc_s.so.1 => /lib/libgcc_s.so.1 (0xb7a48000)
libc.so.6 => /lib/i686/cmov/libc.so.6 (0xb78ed000)
libutil.so.1 => /lib/i686/cmov/libutil.so.1 (0xb78e9000)
libdl.so.2 => /lib/i686/cmov/libdl.so.2 (0xb78e4000)
/lib/ld-linux.so.2 (0xb7f93000)
Terminal: screen
$DISPLAY is set.
`which aptitude`: /usr/bin/aptitude
aptitude version information:
aptitude linkage:
-- System Information:
Debian Release: lenny/sid
APT prefers testing
APT policy: (650, 'testing'), (600, 'stable'), (550, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.6.25-1-686 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages aptitude depends on:
ii apt [libapt-pkg-libc6. 0.7.14+b1 Advanced front-end for dpkg
ii libc6 2.7-13 GNU C Library: Shared libraries
ii libcwidget3 0.5.12-1 high-level terminal interface libr
ii libept0 0.5.22 High-level library for managing De
ii libgcc1 1:4.3.1-9 GCC support library
ii libncursesw5 5.6+20080804-1 shared libraries for terminal hand
ii libsigc++-2.0-0c2a 2.0.18-2 type-safe Signal Framework for C++
ii libstdc++6 4.3.1-9 The GNU Standard C++ Library v3
ii libxapian15 1.0.7-3 Search engine library
ii zlib1g 1:1.2.3.3.dfsg-12 compression library - runtime
Versions of packages aptitude recommends:
ii aptitude-doc-en [aptitude-doc 0.4.11.8-1 English manual for aptitude, a ter
ii libparse-debianchangelog-perl 1.1.1-2 parse Debian changelogs and output
Versions of packages aptitude suggests:
ii debtags 1.7.7 Enables support for package tags
pn tasksel <none> (no description available)
-- no debconf information
--
Jonas Kölker <[email protected]> <URL:http://jonaskoelker.ignorelist.com>
signature.asc
Description: Digital signature
--- End Message ---
--- Begin Message ---
2015-11-08 00:19 To Jonas Koelker:
Control: tags -1 + wontfix
Hi Jonas,
2008-09-09 22:39 Jonas Koelker:
Package: aptitude
Version: 0.4.11.8-1
Severity: wishlist
Here's the scenario where I want aptitude to serve me better:
1. I run a dist-upgrade, chugging away
2. I discover that I want to install something
3. I run aptitude again while the dist-upgrade is running
4. Aptitude fails to acquire the lock and terminates
Here's the alternate step 4:
4. Aptitude polls the lock until it acquires it, then proceeds.
That way, aptitude is fire-and-forget instead of requiring babysitting :)
I don't think that aptitude can be used in a fire-and-forget way in many
cases. For example:
a) aptitude or the package can fail in many ways, so even in the general
case, it requires attention to see if the action succeeded at some
point -- it's not completely "forget" in any case
b) the dist-upgrade or any previous commands can cause conflicts or
other problems, requiring attention, and an automatic attempt of
doing some other action can aggravate the consequences of anything
going wrong in previous runs
c) the new package to be installed, or its dependencies, can fail
because of conflicts or removals of the other packages involved in
the previous dist-upgrade, again requiring attention/decision
d) if the new command gets stuck for some reason (e.g. because of c)),
then other automatic tools can get stuck because of this (see
#564289)
e) probably more, but I think that the above are serious and common
enough to serve as an example
On the other hand, if one is so sure that all commands are going to
succeed and doesn't want to bother waiting for a very long dist-upgrade,
one can create a very simple loop in the shell to retry with a sleep
until it succeeds. (Or type in the same terminal, so the shell runs the
second command after the first finishes).
So, in short, I think that the advantages of implement this are not
many, and there are important risks, so I am marking it as +wontfix for
now. (But in reality, after 7+ years with no action and so many other
important problems in aptitude to solve and hundreds of bugs open, I
don't think that it's useful to keep this one open as well).
Submitter address bounced, unsurprising after all these years, so I will
close it now.
Cheers.
--
Manuel A. Fernandez Montecelo <[email protected]>
--- End Message ---
_______________________________________________
Aptitude-devel mailing list
[email protected]
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/aptitude-devel
