2016-03-05 21:16 GMT+00:00 Katsuhiko Nishimra :
> I've confirmed with aptitude=0.7.8-1 that SIGABRT has gone even when
> quitting without accepting a solution.
Good, thanks for the feed-back.
BTW, it is strange that the other problem was not reported before, the
problem has
Hi,
On Thu, Mar 03, 2016 at 01:40:57AM +, Manuel A. Fernandez Montecelo wrote:
> Control: tags -1 - moreinfo unreproducible + pending
>
>
> Hi Katsuhiko,
>
> 2016-03-01 19:05 Katsuhiko Nishimra:
> >Hi, thank you for the reply.
> >
> >On Tue, Mar 01, 2016 at 12:30:51PM +, Manuel A.
Control: tags -1 - moreinfo unreproducible + pending
Hi Katsuhiko,
2016-03-01 19:05 Katsuhiko Nishimra:
Hi, thank you for the reply.
On Tue, Mar 01, 2016 at 12:30:51PM +, Manuel A. Fernandez Montecelo wrote:
I could not reproduce it in my systems with the same versions, with
either
Control: tags -1 + moreinfo unreproducible
Hi,
2016-02-29 20:46 Katsuhiko Nishimra:
Package: aptitude
Version: 0.7.6-1
Severity: important
Dear Maintainer,
I've run into a SIGABRT when quitting a conflict resolver in aptitude-
curses.
How to reproduce:
* Invoke conflicts by something like
Package: aptitude
Version: 0.6.11-1+b1
Dear maintainer,
I've confirmed this is also found in jessie.
Regards,
Katsuhiko
--- System information. ---
Architecture: amd64
Kernel: Linux 3.16.0-4-amd64
Debian Release: 8.3
500 stable-updates cdn.debian.or.jp
500 stable
Package: aptitude
Version: 0.7.6-1
Severity: important
Dear Maintainer,
I've run into a SIGABRT when quitting a conflict resolver in aptitude-
curses.
How to reproduce:
* Invoke conflicts by something like
$ aptitude -st experimental full-upgrade
* Enter the conflict resolver by hitting `e'
*
6 matches
Mail list logo