[MIR] pitivi

Bug #502897 reported by Martin Pitt on 2010-01-04
18
This bug affects 2 people
Affects Status Importance Assigned to Milestone
gnonlin (Ubuntu)
Undecided
Unassigned
Lucid
Undecided
Unassigned
pitivi (Ubuntu)
Wishlist
Martin Pitt
Lucid
Wishlist
Martin Pitt
pygoocanvas (Ubuntu)
Undecided
Unassigned
Lucid
Undecided
Unassigned

Bug Description

Binary package hint: pitivi

In https://blueprints.launchpad.net/ubuntu/+spec/desktop-lucid-default-apps it was decided to install pitivi by default.

(Caveat: Right now, pitivi pulls hal back in; it should be ported to udev, or we need to change hal to be dbus activated)

Martin Pitt (pitti) on 2010-01-04
Changed in pitivi (Ubuntu):
assignee: nobody → Sebastien Bacher (seb128)
status: New → Incomplete
Changed in pitivi (Ubuntu Lucid):
milestone: none → lucid-alpha-2
Sebastien Bacher (seb128) wrote :

upstream bug about getting ride of the hal use: https://bugzilla.gnome.org/show_bug.cgi?id=605920

I would recommend including it only once they do clean it

Changed in pitivi (Ubuntu Lucid):
importance: Undecided → Wishlist
Sebastien Bacher (seb128) wrote :

The software is actively maintained upstream and in Debian, using python, the packaging is standard cdbs one, there is no known security issue and the software is an user one (ie no system service running)

Sebastien Bacher (seb128) wrote :

I've checked the mir requirements for pitivi and there is no issue worth mentioning there out of the use of outdated technologies which should be fixed for lucid if we want to use it in the default installation

Martin Pitt (pitti) on 2010-01-04
Changed in pitivi (Ubuntu Lucid):
assignee: Sebastien Bacher (seb128) → Martin Pitt (pitti)
status: Incomplete → New
Martin Pitt (pitti) wrote :

FYI, I changed hal to use dbus activation now, so any newly installed package which pulls in hal will now work (I tested pitivi), without having hal start during boot.

Martin Pitt (pitti) wrote :

Sebastien,

there's one grave and and one important bug in Debian; do they affect us?

Martin Pitt (pitti) wrote :

Also, the Ubuntu bug tracker is full of crash reports, which reflects the general feeling that this application is still quite buggy. Since in an editor like pitivi, crashes == data loss == fatal, this is quite an issue. Do you happen to know how responsive upstream is for fixes, and if there's someone who maintains pitivi in Ubuntu already?

Changed in pygoocanvas (Ubuntu Lucid):
status: New → Incomplete
Changed in gnonlin (Ubuntu Lucid):
status: New → Incomplete
Martin Pitt (pitti) wrote :

This pulls in gstreamer0.10-gnonlin and python-pygoocanvas which also need a MIR review (this should have been checked at the original MIR review, BTW)

I reviewed the pitivi packaging and it is fine.

Changed in pitivi (Ubuntu Lucid):
status: New → Incomplete

I'd like to know which crashes you're talking about. Last I checked (some 3 months ago maybe), all those crash reports were for old versions of pitivi

Jeff Fortin Tam (kiddo) wrote :

Martin, I just subscribed to the ubuntu bug reports for PiTiVi, as it seems that there was a huge unseen pile of bug reports, most of which are on obsolete releases. It seems there was not much bug triaging going on, so I will attempt to fill that role (as time permits). I'll start by attempting a cleanup of the obsolete bugs.

Basically, it boils down to: the devs will attend to bug reports if 1) they are on the latest pitivi release or the dev version 2) are brought to upstream (ie: gnome bugzilla). Bugs in launchpad must be triaged first (I can understand their position very well, it's already quite hard to not get lost in the ~200 bugs upstream to begin with).

Hello Jean,

Jean-François Fortin Tam [2010-01-05 14:18 -0000]:
> Martin, I just subscribed to the ubuntu bug reports for PiTiVi, as it
> seems that there was a huge unseen pile of bug reports, most of which
> are on obsolete releases. It seems there was not much bug triaging going
> on, so I will attempt to fill that role (as time permits). I'll start by
> attempting a cleanup of the obsolete bugs.

Right, I guess most of them are from karmic or even older. Thanks for
doing some cleanup there!

Martin
--
Martin Pitt | http://www.piware.de
Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org)

Martin Pitt (pitti) wrote :

I reviewed the two grave/important Debian bugs, and they aren't too much of a concern for us. Approved pitivi.

Changed in pitivi (Ubuntu Lucid):
status: Incomplete → Fix Committed
Martin Pitt (pitti) wrote :

pygoocanvas: I checked https://wiki.ubuntu.com/UbuntuMainInclusionRequirements and verified that the package meets all points. It's a rather harmless binding package.

Changed in pygoocanvas (Ubuntu Lucid):
status: Incomplete → Fix Committed
Martin Pitt (pitti) wrote :

gnonlin: I checked https://wiki.ubuntu.com/UbuntuMainInclusionRequirements and verified that the package meets all points. It's well maintained in Debian and has no bug reports. It has a test suite which gets run during build; the only nitpick is that a failing test suite does not fail the build. It currently succeeds on all architectures, and I don't think it's worth carrying a delta just for this, but I filed it as a Debian bug report. Aside from this, the package looks fine, approved.

Changed in gnonlin (Ubuntu Lucid):
status: Incomplete → Fix Committed
Martin Pitt (pitti) wrote :

seeded pitivi to ubuntu desktop, promoted these three.

Changed in pygoocanvas (Ubuntu Lucid):
status: Fix Committed → Fix Released
Changed in pitivi (Ubuntu Lucid):
status: Fix Committed → Fix Released
Changed in gnonlin (Ubuntu Lucid):
status: Fix Committed → Fix Released
Jeff Fortin Tam (kiddo) wrote :

Okay, I think there's a bunch of new bugs being filed on pitivi on launchpad due to ubuntu pulling out HAL (that's not even considering the bunch of bugs of people who can't import MPEG2-TS files)...

I can't triage them all alone, especially the HAL bugs, because I lack the expertise to figure them out (if they are duplicates, etc.). I need help on this, I'm getting confused.

By they way, who should I chat with (on IRC or whatnot) among ubuntu devs that are involved/interested in the inclusion of pitivi in Ubuntu main? There are some things I'm worried about regarding the timeline, dependencies, etc.

Martin Pitt (pitti) wrote :

Jean-François Fortin Tam [2010-01-17 16:04 -0000]:
> Okay, I think there's a bunch of new bugs being filed on pitivi on
> launchpad due to ubuntu pulling out HAL (that's not even considering the
> bunch of bugs of people who can't import MPEG2-TS files)...

We didn't. Since pitivi Depends: hal, hal will be, and is, installed
by default. Starting pitivi causes hal to start, too (works fine
here).

> I can't triage them all alone, especially the HAL bugs, because I lack
> the expertise to figure them out (if they are duplicates, etc.). I need
> help on this, I'm getting confused.

I don't understand -- pitivi didn't change anything wrt. hal recently,
we just changed hal to start on demand (via D-Bus activation) instead
of unconditionally at boot. What causes grief now?

> By they way, who should I chat with (on IRC or whatnot) among ubuntu
> devs that are involved/interested in the inclusion of pitivi in Ubuntu
> main? There are some things I'm worried about regarding the timeline,
> dependencies, etc.

https://lists.ubuntu.com/mailman/listinfo/ubuntu-desktop or
#ubuntu-desktop would be appropriate IMHO.

Martin

--
Martin Pitt | http://www.piware.de
Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org)

Jeff Fortin Tam (kiddo) wrote :

Ok, it was just me misunderstanding what happened then, because there's
a bunch of bug reports on launchpad I can do nothing about, I don't know
what is causing them exactly. There's a bunch of them that seem somewhat
similar but not quite, and they pretty much all lack sample files/repro
instructions.

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

Other bug subscribers

Remote bug watches

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