Please backport apport 0.94 from Gutsy to Feisty

Bug #128595 reported by Marco Rodrigues
6
Affects Status Importance Assigned to Milestone
Feisty Backports
Invalid
Undecided
Unassigned

Bug Description

A lot of news and reporting system updated. It would be good to have it at feisty...

Revision history for this message
Automated Backports Builder (john-dong+backport-builder) wrote : Build Started: apport

This is a notification that the automatic backport of apport from gutsy to feisty has started.

You will be notified again once the build is finished.

For additional info and build logs, please see: http://sharkattack.media.mit.edu/inventory/check_builds/41

Thanks,

The Backports Builder

Revision history for this message
Automated Backports Builder (john-dong+backport-builder) wrote : Notification of build SUCCESS for apport

Howdy! This message is to inform you that the build you requested of apport from gutsy to feisty has been completed.
Its status is: SUCCESS
For further information, build logs, and testing .deb packages, please see: http://sharkattack.media.mit.edu/inventory/check_builds/41

Thanks,
The Backports Builder

Revision history for this message
John Dong (jdong) wrote : Re: Please backport apport 0.93 from Gutsy to Feisty

Is this compatible with Feisty's kernel and userland?

Revision history for this message
Marco Rodrigues (gothicx) wrote :

I really don't know, that's why I subscribed pitti to the bug, he should have something to say about this.

Revision history for this message
Martin Pitt (pitti) wrote :

It is compatible to the kernel, but it needs a newer python-launchpad-bugs in Feisty.

Also, I am not terribly convinced that we need it in feisty, since we disabled the automatic crash notification by default. I'm still fine with backporting it once someone runs /usr/share/apport/testsuite/run-tests on feisty with the backported packages and it succeeds.

Revision history for this message
Marco Rodrigues (gothicx) wrote :

I think with latest apport it will have better crash reports.. even with crash notification disabled by default. It also make more easy to submit crashs from people who know how to do it, using the apport-gtk =)

Revision history for this message
Valentin Rocher (bishiboosh) wrote :

python-launchpad-bugs and apport seem to backport and install well, however run-tests fails in the last test series with this message :

======================================================================
FAIL: Test add_proc_info().
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/usr/share/python-support/python-apport/apport/report.py", line 931, in test_add_proc_info
    self.assertEqual(pr['InterpreterPath'], open('/bin/zgrep').readline().strip()[2:])
AssertionError: '/bin/dash' != '/bin/sh'

Changed in feisty-backports:
status: New → Incomplete
Revision history for this message
Martin Pitt (pitti) wrote :

That test failure isn't too bad, it's just (more or less) a bug in the test suite which assumes a particular interpreter of /bin/zgrep (which was changed in gutsy). I can fix that in the next version.

Revision history for this message
Martin Pitt (pitti) wrote :

I fixed that test suite check in bzr head, report.py now has all tests passed in a feisty chroot. This will get uploaded soon as version 0.94.

Revision history for this message
Martin Pitt (pitti) wrote :
Revision history for this message
Automated Backports Builder (john-dong+backport-builder) wrote : Build Started: apport

This is a notification that the automatic backport of apport from gutsy to feisty has started.

You will be notified again once the build is finished.

For additional info and build logs, please see: http://sharkattack.media.mit.edu/inventory/check_builds/41

Thanks,

The Backports Builder

Revision history for this message
Automated Backports Builder (john-dong+backport-builder) wrote : Notification of build FAIL for apport

Howdy! This message is to inform you that the build you requested of apport from gutsy to feisty has been completed.
Its status is: FAIL
For further information, build logs, and testing .deb packages, please see: http://sharkattack.media.mit.edu/inventory/check_builds/41

Thanks,
The Backports Builder

Revision history for this message
Marco Rodrigues (gothicx) wrote :

It failed because of a bug in the script.. I've already reported it to jdong :)

Revision history for this message
Automated Backports Builder (john-dong+backport-builder) wrote : Build Started: apport

This is a notification that the automatic backport of apport from gutsy to feisty has started.

You will be notified again once the build is finished.

For additional info and build logs, please see: http://sharkattack.media.mit.edu/inventory/check_builds/41

Thanks,

The Backports Builder

Revision history for this message
Automated Backports Builder (john-dong+backport-builder) wrote : Notification of build SUCCESS for apport

Howdy! This message is to inform you that the build you requested of apport from gutsy to feisty has been completed.
Its status is: SUCCESS
For further information, build logs, and testing .deb packages, please see: http://sharkattack.media.mit.edu/inventory/check_builds/41

Thanks,
The Backports Builder

Revision history for this message
Marco Rodrigues (gothicx) wrote :

I've installed the .deb files from Gutsy repository and it works fine here at my Feisty.

Revision history for this message
Marco Rodrigues (gothicx) wrote :

I've talked to pitti and it's better to invalid this one.

Changed in feisty-backports:
status: Incomplete → Invalid
Revision history for this message
Automated Backports Builder (john-dong+backport-builder) wrote : Build Started: apport

This is a notification that the automatic backport of apport from gutsy to feisty has started.

You will be notified again once the build is finished.

For additional info and build logs, please see: http://sharkattack.media.mit.edu/inventory/check_builds/41

Thanks,

The Backports Builder

Revision history for this message
Automated Backports Builder (john-dong+backport-builder) wrote : Notification of build SUCCESS for apport

Howdy! This message is to inform you that the build you requested of apport from gutsy to feisty has been completed.
Its status is: SUCCESS
For further information, build logs, and testing .deb packages, please see: http://sharkattack.media.mit.edu/inventory/check_builds/41

Thanks,
The Backports Builder

Revision history for this message
Automated Backports Builder (john-dong+backport-builder) wrote : Build Started: apport

This is a notification that the automatic backport of apport from gutsy to feisty has started.

You will be notified again once the build is finished.

For additional info and build logs, please see: http://sharkattack.media.mit.edu/inventory/check_builds/41

Thanks,

The Backports Builder

Revision history for this message
Automated Backports Builder (john-dong+backport-builder) wrote : Notification of build SUCCESS for apport

Howdy! This message is to inform you that the build you requested of apport from gutsy to feisty has been completed.
Its status is: SUCCESS
For further information, build logs, and testing .deb packages, please see: http://sharkattack.media.mit.edu/inventory/check_builds/41

Thanks,
The Backports Builder

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.