Your message dated Sat, 7 Nov 2015 23:03:02 +0000
with message-id <[email protected]>
and subject line Re: [Aptitude-devel] Bug#797785: aptitude: TUI to catch
debtags warnins/errors
has caused the Debian Bug report #797785,
regarding aptitude: TUI to catch debtags warnins/errors
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.)
--
797785: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=797785
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: aptitude
Version: 0.6.11-1+b1
Severity: wishlist
Dear Maintainer,
would it be possible for aptitude in TUI to catch debtags errors/warnings,
instead of let them to mess up the interface ? Specifically, I have a problem
where certain old (but still usefull) apt-lists contains non-UTF8 characters.
That triggers debtags to report a warning that messes up the TUI. It would be
nice if aptitude was able to catch such errors and show them in a red dialog
instead.
Thanks,
Pavel
-- Package-specific info:
Terminal: xterm
$DISPLAY is set.
which aptitude: /usr/bin/aptitude
aptitude version information:
aptitude 0.6.11 compiled at Nov 8 2014 13:34:39
Compiler: g++ 4.9.1
Compiled against:
apt version 4.12.0
NCurses version 5.9
libsigc++ version: 2.4.0
Gtk+ support disabled.
Qt support disabled.
Current library versions:
NCurses version: ncurses 6.0.20150810
cwidget version: 0.5.17
Apt version: 4.12.0
aptitude linkage:
linux-vdso.so.1 (0x00007ffdf1ff5000)
libapt-pkg.so.4.12 => /usr/lib/x86_64-linux-gnu/libapt-pkg.so.4.12
(0x00007febbcb6d000)
libncursesw.so.5 => /lib/x86_64-linux-gnu/libncursesw.so.5
(0x00007febbc93d000)
libtinfo.so.5 => /lib/x86_64-linux-gnu/libtinfo.so.5
(0x00007febbc712000)
libsigc-2.0.so.0 => /usr/lib/x86_64-linux-gnu/libsigc-2.0.so.0
(0x00007febbc50c000)
libcwidget.so.3 => /usr/lib/x86_64-linux-gnu/libcwidget.so.3
(0x00007febbc1f6000)
libsqlite3.so.0 => /usr/lib/x86_64-linux-gnu/libsqlite3.so.0
(0x00007febbbf28000)
libboost_iostreams.so.1.55.0 =>
/usr/lib/x86_64-linux-gnu/libboost_iostreams.so.1.55.0 (0x00007febbbd10000)
libxapian.so.22 => /usr/lib/libxapian.so.22 (0x00007febbb8f9000)
libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0
(0x00007febbb6db000)
libstdc++.so.6 => /usr/lib/x86_64-linux-gnu/libstdc++.so.6
(0x00007febbb3cf000)
libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x00007febbb0ce000)
libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1
(0x00007febbaeb7000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007febbab0e000)
libutil.so.1 => /lib/x86_64-linux-gnu/libutil.so.1 (0x00007febba90b000)
libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x00007febba706000)
libz.so.1 => /lib/x86_64-linux-gnu/libz.so.1 (0x00007febba4eb000)
libbz2.so.1.0 => /lib/x86_64-linux-gnu/libbz2.so.1.0
(0x00007febba2db000)
liblzma.so.5 => /lib/x86_64-linux-gnu/liblzma.so.5 (0x00007febba0b7000)
librt.so.1 => /lib/x86_64-linux-gnu/librt.so.1 (0x00007febb9eaf000)
libuuid.so.1 => /lib/x86_64-linux-gnu/libuuid.so.1 (0x00007febb9ca9000)
/lib64/ld-linux-x86-64.so.2 (0x00005632aed9b000)
-- System Information:
Debian Release: stretch/sid
APT prefers testing-proposed-updates
APT policy: (840, 'testing-proposed-updates'), (840, 'testing'), (740,
'unstable'), (738, 'experimental'), (540, 'proposed-updates'), (540, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.1.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=cs_CZ.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages aptitude depends on:
ii aptitude-common 0.6.11-1
ii libapt-pkg4.12 1.0.9.10
ii libboost-iostreams1.55.0 1.55.0+dfsg-4
ii libc6 2.19-19
ii libcwidget3 0.5.17-2
ii libgcc1 1:5.1.1-14
ii libncursesw5 6.0+20150810-1
ii libsigc++-2.0-0c2a 2.4.1-1
ii libsqlite3-0 3.8.11.1-1
ii libstdc++6 5.1.1-14
ii libtinfo5 6.0+20150810-1
ii libxapian22 1.2.21-1
Versions of packages aptitude recommends:
ii aptitude-doc-en [aptitude-doc] 0.6.11-1
ii libparse-debianchangelog-perl 1.2.0-8
ii sensible-utils 0.0.9
Versions of packages aptitude suggests:
ii apt-xapian-index 0.47
ii debtags 2.0+nmu1
ii tasksel 3.33
-- Configuration Files:
/etc/logrotate.d/aptitude changed [not included]
-- no debconf information
--- End Message ---
--- Begin Message ---
2015-10-05 23:32 To Pavel Reznicek:
Hi Pavel,
2015-09-02 15:06 Axel Beckert:
Control: tag -1 + moreinfo
Hi Pavel,
Pavel Reznicek wrote:
would it be possible for aptitude in TUI to catch debtags
errors/warnings, instead of let them to mess up the interface ?
Specifically, I have a problem where certain old (but still usefull)
apt-lists contains non-UTF8 characters. That triggers debtags to
report a warning that messes up the TUI.
Is that APT repository public? If so, please tell us the according
line from sources.list so that we can try to reproduce this.
So, as Axel said, could you please tell us about the repository, or tell
a way to reproduce it with some file that you can produce?
Closing now, please reopen if you can provide the requested information.
--
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
