** Visibility changed to: Public
--
aptitude crashed with SIGSEGV in pkgRecords::Lookup()
https://bugs.launchpad.net/bugs/181406
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
ht
Forwarded to upstream (debian).
** Bug watch added: Debian Bug tracker #472998
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=472998
** Also affects: aptitude via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=472998
Importance: Unknown
Status: Unknown
--
aptitude crashed wi
** Changed in: aptitude
Status: Unknown => New
--
aptitude crashed with SIGSEGV in pkgRecords::Lookup()
https://bugs.launchpad.net/bugs/181406
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bug
For me, the crash happened when i selected a package and hit "P" to mark
it to be purged
--
aptitude crashed with SIGSEGV in pkgRecords::Lookup()
https://bugs.launchpad.net/bugs/181406
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
I need some exercise and so I will have a look on this at weekend. Maybe
I can offer a patch for you guys.
--
aptitude crashed with SIGSEGV in pkgRecords::Lookup()
https://bugs.launchpad.net/bugs/181406
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribe
upstream cannot reproduce the problem in the most recent version of
aptitude. Maybe time for an update?
--
aptitude crashed with SIGSEGV in pkgRecords::Lookup()
https://bugs.launchpad.net/bugs/181406
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
> I run the osupgrade alias at least once a day to make sure my hardy
> installation is up to date.
hardy is still on 0.4.9 (the same as for the upstream bug report).
0.4.9 is according to the debian report more than a year old and it
seems the devs are unwilling to fix in it that version, especia
> 0.4.9 is according to the debian report more than a year old
well, the debian changelog tells a different story, of course. Changes
to 0.4.9 were still uploaded at the end of last year.
--
aptitude crashed with SIGSEGV in pkgRecords::Lookup()
https://bugs.launchpad.net/bugs/181406
You receive
** Changed in: aptitude
Status: New => Fix Released
--
aptitude crashed with SIGSEGV in pkgRecords::Lookup()
https://bugs.launchpad.net/bugs/181406
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubunt
upstream cannot reproduce the problem in the most recent version of
aptitude. Maybe time for an update?
--
aptitude crashed with SIGSEGV in pkgRecords::Lookup()
https://bugs.launchpad.net/bugs/181406
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
> I run the osupgrade alias at least once a day to make sure my hardy
> installation is up to date.
hardy is still on 0.4.9 (the same as for the upstream bug report).
0.4.9 is according to the debian report more than a year old and it
seems the devs are unwilling to fix in it that version, especia
> 0.4.9 is according to the debian report more than a year old
well, the debian changelog tells a different story, of course. Changes
to 0.4.9 were still uploaded at the end of last year.
--
aptitude crashed with SIGSEGV in pkgRecords::Lookup()
https://bugs.launchpad.net/bugs/181406
You receive
** Changed in: aptitude
Status: New => Fix Released
--
aptitude crashed with SIGSEGV in pkgRecords::Lookup()
https://bugs.launchpad.net/bugs/181406
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubunt
** Visibility changed to: Public
--
aptitude crashed with SIGSEGV in pkgRecords::Lookup()
https://bugs.launchpad.net/bugs/181406
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
ht
Forwarded to upstream (debian).
** Bug watch added: Debian Bug tracker #472998
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=472998
** Also affects: aptitude via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=472998
Importance: Unknown
Status: Unknown
--
aptitude crashed wi
** Changed in: aptitude
Status: Unknown => New
--
aptitude crashed with SIGSEGV in pkgRecords::Lookup()
https://bugs.launchpad.net/bugs/181406
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bug
For me, the crash happened when i selected a package and hit "P" to mark
it to be purged
--
aptitude crashed with SIGSEGV in pkgRecords::Lookup()
https://bugs.launchpad.net/bugs/181406
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
I need some exercise and so I will have a look on this at weekend. Maybe
I can offer a patch for you guys.
--
aptitude crashed with SIGSEGV in pkgRecords::Lookup()
https://bugs.launchpad.net/bugs/181406
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribe
upstream cannot reproduce the problem in the most recent version of
aptitude. Maybe time for an update?
--
aptitude crashed with SIGSEGV in pkgRecords::Lookup()
https://bugs.launchpad.net/bugs/181406
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
> I run the osupgrade alias at least once a day to make sure my hardy
> installation is up to date.
hardy is still on 0.4.9 (the same as for the upstream bug report).
0.4.9 is according to the debian report more than a year old and it
seems the devs are unwilling to fix in it that version, especia
> 0.4.9 is according to the debian report more than a year old
well, the debian changelog tells a different story, of course. Changes
to 0.4.9 were still uploaded at the end of last year.
--
aptitude crashed with SIGSEGV in pkgRecords::Lookup()
https://bugs.launchpad.net/bugs/181406
You receive
** Visibility changed to: Public
--
aptitude crashed with SIGSEGV in pkgRecords::Lookup()
https://bugs.launchpad.net/bugs/181406
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
ht
Forwarded to upstream (debian).
** Bug watch added: Debian Bug tracker #472998
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=472998
** Also affects: aptitude via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=472998
Importance: Unknown
Status: Unknown
--
aptitude crashed wi
** Changed in: aptitude
Status: Unknown => New
--
aptitude crashed with SIGSEGV in pkgRecords::Lookup()
https://bugs.launchpad.net/bugs/181406
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bug
For me, the crash happened when i selected a package and hit "P" to mark
it to be purged
--
aptitude crashed with SIGSEGV in pkgRecords::Lookup()
https://bugs.launchpad.net/bugs/181406
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
** Changed in: aptitude
Status: New => Fix Released
--
aptitude crashed with SIGSEGV in pkgRecords::Lookup()
https://bugs.launchpad.net/bugs/181406
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubunt
I need some exercise and so I will have a look on this at weekend. Maybe
I can offer a patch for you guys.
--
aptitude crashed with SIGSEGV in pkgRecords::Lookup()
https://bugs.launchpad.net/bugs/181406
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribe
upstream cannot reproduce the problem in the most recent version of
aptitude. Maybe time for an update?
--
aptitude crashed with SIGSEGV in pkgRecords::Lookup()
https://bugs.launchpad.net/bugs/181406
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
> I run the osupgrade alias at least once a day to make sure my hardy
> installation is up to date.
hardy is still on 0.4.9 (the same as for the upstream bug report).
0.4.9 is according to the debian report more than a year old and it
seems the devs are unwilling to fix in it that version, especia
> 0.4.9 is according to the debian report more than a year old
well, the debian changelog tells a different story, of course. Changes
to 0.4.9 were still uploaded at the end of last year.
--
aptitude crashed with SIGSEGV in pkgRecords::Lookup()
https://bugs.launchpad.net/bugs/181406
You receive
** Visibility changed to: Public
--
aptitude crashed with SIGSEGV in pkgRecords::Lookup()
https://bugs.launchpad.net/bugs/181406
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
ht
Forwarded to upstream (debian).
** Bug watch added: Debian Bug tracker #472998
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=472998
** Also affects: aptitude via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=472998
Importance: Unknown
Status: Unknown
--
aptitude crashed wi
** Changed in: aptitude
Status: Unknown => New
--
aptitude crashed with SIGSEGV in pkgRecords::Lookup()
https://bugs.launchpad.net/bugs/181406
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bug
For me, the crash happened when i selected a package and hit "P" to mark
it to be purged
--
aptitude crashed with SIGSEGV in pkgRecords::Lookup()
https://bugs.launchpad.net/bugs/181406
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
** Changed in: aptitude
Status: New => Fix Released
--
aptitude crashed with SIGSEGV in pkgRecords::Lookup()
https://bugs.launchpad.net/bugs/181406
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubunt
I need some exercise and so I will have a look on this at weekend. Maybe
I can offer a patch for you guys.
--
aptitude crashed with SIGSEGV in pkgRecords::Lookup()
https://bugs.launchpad.net/bugs/181406
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribe
I need some exercise and so I will have a look on this at weekend. Maybe
I can offer a patch for you guys.
--
aptitude crashed with SIGSEGV in pkgRecords::Lookup()
https://bugs.launchpad.net/bugs/181406
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribe
upstream cannot reproduce the problem in the most recent version of
aptitude. Maybe time for an update?
--
aptitude crashed with SIGSEGV in pkgRecords::Lookup()
https://bugs.launchpad.net/bugs/181406
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
> I run the osupgrade alias at least once a day to make sure my hardy
> installation is up to date.
hardy is still on 0.4.9 (the same as for the upstream bug report).
0.4.9 is according to the debian report more than a year old and it
seems the devs are unwilling to fix in it that version, especia
> 0.4.9 is according to the debian report more than a year old
well, the debian changelog tells a different story, of course. Changes
to 0.4.9 were still uploaded at the end of last year.
--
aptitude crashed with SIGSEGV in pkgRecords::Lookup()
https://bugs.launchpad.net/bugs/181406
You receive
** Visibility changed to: Public
--
aptitude crashed with SIGSEGV in pkgRecords::Lookup()
https://bugs.launchpad.net/bugs/181406
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
ht
Forwarded to upstream (debian).
** Bug watch added: Debian Bug tracker #472998
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=472998
** Also affects: aptitude via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=472998
Importance: Unknown
Status: Unknown
--
aptitude crashed wi
** Changed in: aptitude
Status: Unknown => New
--
aptitude crashed with SIGSEGV in pkgRecords::Lookup()
https://bugs.launchpad.net/bugs/181406
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bug
For me, the crash happened when i selected a package and hit "P" to mark
it to be purged
--
aptitude crashed with SIGSEGV in pkgRecords::Lookup()
https://bugs.launchpad.net/bugs/181406
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
** Changed in: aptitude
Status: New => Fix Released
--
aptitude crashed with SIGSEGV in pkgRecords::Lookup()
https://bugs.launchpad.net/bugs/181406
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubunt
** Visibility changed to: Public
--
aptitude crashed with SIGSEGV in pkgRecords::Lookup()
https://bugs.launchpad.net/bugs/181406
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
ht
Forwarded to upstream (debian).
** Bug watch added: Debian Bug tracker #472998
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=472998
** Also affects: aptitude via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=472998
Importance: Unknown
Status: Unknown
--
aptitude crashed wi
** Changed in: aptitude
Status: Unknown => New
--
aptitude crashed with SIGSEGV in pkgRecords::Lookup()
https://bugs.launchpad.net/bugs/181406
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bug
For me, the crash happened when i selected a package and hit "P" to mark
it to be purged
--
aptitude crashed with SIGSEGV in pkgRecords::Lookup()
https://bugs.launchpad.net/bugs/181406
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
I need some exercise and so I will have a look on this at weekend. Maybe
I can offer a patch for you guys.
--
aptitude crashed with SIGSEGV in pkgRecords::Lookup()
https://bugs.launchpad.net/bugs/181406
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribe
upstream cannot reproduce the problem in the most recent version of
aptitude. Maybe time for an update?
--
aptitude crashed with SIGSEGV in pkgRecords::Lookup()
https://bugs.launchpad.net/bugs/181406
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
> I run the osupgrade alias at least once a day to make sure my hardy
> installation is up to date.
hardy is still on 0.4.9 (the same as for the upstream bug report).
0.4.9 is according to the debian report more than a year old and it
seems the devs are unwilling to fix in it that version, especia
> 0.4.9 is according to the debian report more than a year old
well, the debian changelog tells a different story, of course. Changes
to 0.4.9 were still uploaded at the end of last year.
--
aptitude crashed with SIGSEGV in pkgRecords::Lookup()
https://bugs.launchpad.net/bugs/181406
You receive
** Changed in: aptitude
Status: New => Fix Released
--
aptitude crashed with SIGSEGV in pkgRecords::Lookup()
https://bugs.launchpad.net/bugs/181406
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubunt
Rolf,
Thank you for your reply. I have been noticing this issue after having
my system running for 3+ days. I have an alias set for easy updates
for me:
alias osupgrade="sudo aptitude update && sudo aptitude safe-upgrade"
I run the osupgrade alias at least once a day to make sure my hardy
instal
Rolf,
Thank you for your reply. I have been noticing this issue after having
my system running for 3+ days. I have an alias set for easy updates
for me:
alias osupgrade="sudo aptitude update && sudo aptitude safe-upgrade"
I run the osupgrade alias at least once a day to make sure my hardy
instal
Rolf,
Thank you for your reply. I have been noticing this issue after having
my system running for 3+ days. I have an alias set for easy updates
for me:
alias osupgrade="sudo aptitude update && sudo aptitude safe-upgrade"
I run the osupgrade alias at least once a day to make sure my hardy
instal
Rolf,
Thank you for your reply. I have been noticing this issue after having
my system running for 3+ days. I have an alias set for easy updates
for me:
alias osupgrade="sudo aptitude update && sudo aptitude safe-upgrade"
I run the osupgrade alias at least once a day to make sure my hardy
instal
Rolf,
Thank you for your reply. I have been noticing this issue after having
my system running for 3+ days. I have an alias set for easy updates
for me:
alias osupgrade="sudo aptitude update && sudo aptitude safe-upgrade"
I run the osupgrade alias at least once a day to make sure my hardy
instal
Rolf,
Thank you for your reply. I have been noticing this issue after having
my system running for 3+ days. I have an alias set for easy updates
for me:
alias osupgrade="sudo aptitude update && sudo aptitude safe-upgrade"
I run the osupgrade alias at least once a day to make sure my hardy
instal
60 matches
Mail list logo
