Martin, your patch for this is considered landed in trunk, but Rejected
for 2.1. So I'm going to mark this as such, and change the In Progress
setting.
** Changed in: bzr
Status: In Progress = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs,
On 21 April 2011 23:12, John A Meinel j...@arbash-meinel.com wrote:
Martin, your patch for this is considered landed in trunk, but Rejected
for 2.1. So I'm going to mark this as such, and change the In Progress
setting.
** Changed in: bzr
Status: In Progress = Fix Released
I think
** Changed in: bzr (Ubuntu)
Status: New = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/391015
Title:
apport package hook for Bazaar
--
ubuntu-bugs mailing list
The branch looks okay to me. I just don't understand why bzrlib/crash.py
would need to set CrashDb, SourcePackage, and Package fields? The latter
two are done during post-processing in the Apport UI, and the apport
hook sets CrashDb already.
--
apport package hook for Bazaar
On 30 March 2010 17:48, Martin Pitt martin.p...@ubuntu.com wrote:
The branch looks okay to me. I just don't understand why bzrlib/crash.py
would need to set CrashDb, SourcePackage, and Package fields? The latter
two are done during post-processing in the Apport UI, and the apport
hook sets
The problem there rather seems to be that the initial report is missing
ExecutablePath.
--
apport package hook for Bazaar
https://bugs.launchpad.net/bugs/391015
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
I wonder if it's more tasteful to install it from the upstream setup.py,
or from the debian/ubuntu packaging? Perhaps the latter, at least for
now, because installing into arbitrary directories owned by other
packages is not really in the normal scope of setup.py, and apport is
unlikely to be
** Branch linked: lp:~mbp/bzr/2.1-528114-apport
--
apport package hook for Bazaar
https://bugs.launchpad.net/bugs/391015
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
An updated version of the source hook and crashdb config is now in
./contrib/apport in bzr, but it's not yet installed by either the
package or make install.
--
apport package hook for Bazaar
https://bugs.launchpad.net/bugs/391015
You received this bug notification because you are a member of
** Tags added: apport
--
apport package hook for Bazaar
https://bugs.launchpad.net/bugs/391015
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
** Changed in: bzr
Assignee: (unassigned) = Martin Pool (mbp)
--
apport package hook for Bazaar
https://bugs.launchpad.net/bugs/391015
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
** Branch linked: lp:ubuntu/karmic/apport
--
apport package hook for Bazaar
https://bugs.launchpad.net/bugs/391015
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
** Branch linked: lp:~ubuntu-core-dev/ubuntu/karmic/apport/ubuntu
--
apport package hook for Bazaar
https://bugs.launchpad.net/bugs/391015
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
This bug was fixed in the package apport - 1.4-0ubuntu1
---
apport (1.4-0ubuntu1) karmic; urgency=low
* New upstream release. Compared to our previous snapshot, this changes:
- Replace Qt4 frontend with KDE frontend, thanks to Richard Johnson!
- apport/ui.py,
Good, then I recommend the approach in comment 10. This works from
Ubuntu 9.04 on.
--
apport package hook for Bazaar
https://bugs.launchpad.net/bugs/391015
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Thanks for your help.
I wonder, should we put this into the bzr tarball or just into the deb
packages? It could be of use on other platforms I suppose.
--
apport package hook for Bazaar
https://bugs.launchpad.net/bugs/391015
You received this bug notification because you are a member of Ubuntu
On Wed, 2009-06-24 at 21:23 +, Martin Pool wrote:
Thanks for your help.
I wonder, should we put this into the bzr tarball or just into the deb
packages? It could be of use on other platforms I suppose.
Yes, Ubuntu isn't the only distro using apport, so putting it in the
tarball (even if
** Also affects: bzr
Importance: Undecided
Status: New
** Changed in: bzr
Importance: Undecided = Medium
** Changed in: bzr
Status: New = In Progress
--
apport package hook for Bazaar
https://bugs.launchpad.net/bugs/391015
You received this bug notification because you are
2009/6/23 Martin Pitt martin.p...@ubuntu.com:
I just wonder whether it would actually help anyone to have these bugs
on the upstream product? Or do the bzr developers only follow the
upstream bug reports, and not the Ubuntu package ones?
We should/do follow the Ubuntu bugs, however we do also
** Attachment added: source_bzr.py
http://launchpadlibrarian.net/28237388/source_bzr.py
** Attachment added: BzrLogTail.txt
http://launchpadlibrarian.net/28237389/BzrLogTail.txt
** Attachment added: BzrPlugins.txt
http://launchpadlibrarian.net/28237390/BzrPlugins.txt
** Attachment
I reported this bug using the hook, so that you can see what it looks
like
--
apport package hook for Bazaar
https://bugs.launchpad.net/bugs/391015
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
I also recommend installing the following symlinks:
/usr/share/apport/package-hooks/source_bzrtools.py - source_bzr.py
/usr/share/apport/package-hooks/source_bzr-gtk.py - source_bzr.py
and likewise for other Bazaar-related packages which would benefit from
the same information. This way, if a
If you want all or some bugs to be filed against the bzr product instead
of the bzr package, this can be done with two steps:
1. define a new crash database for upstream bzr, like
$ cat /etc/apport/crashdb.conf.d/bzr.conf
bzr = {
'impl': 'launchpad',
'bug_pattern_base':
Fixed above behaviour in in lp:apport r1476.
** Changed in: apport (Ubuntu)
Importance: Undecided = Medium
** Changed in: apport (Ubuntu)
Status: New = Fix Committed
** Changed in: apport (Ubuntu)
Assignee: (unassigned) = Martin Pitt (pitti)
--
apport package hook for Bazaar
** Branch linked: lp:apport
--
apport package hook for Bazaar
https://bugs.launchpad.net/bugs/391015
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
I just wonder whether it would actually help anyone to have these bugs
on the upstream product? Or do the bzr developers only follow the
upstream bug reports, and not the Ubuntu package ones?
For the record, if you want PPA package reports to be filed against the
Ubuntu package, you can disable
On Tue, 2009-06-23 at 11:23 +, Martin Pitt wrote:
I just wonder whether it would actually help anyone to have these bugs
on the upstream product? Or do the bzr developers only follow the
upstream bug reports, and not the Ubuntu package ones?
We don't generally look at package bugs. I think
27 matches
Mail list logo
