Ubuntu Forums Archive Viewer

Request: Totem 1.1.3

Archived thread 48840 from Closed Requests. Markdown source: Closed_Requests/thread_48840_Request_Totem_1.1.3.md

Original URL About this archive
#1

Hi . Is possible backport Totem 1.1.3 ? Its in Breezy http://lists.ubuntu.com/archives/breezy-changes/2005-July/007935.html

Thanks

#2
#3

Thanks :-)

Work for me yet ..

#4

If you're making custom packages, please be responsible and add a "~something" version trailer to it. Otherwise, you're setting up users for an upgrade DISASTER with the Breezy transition.

This is a valid Backports request, accepted.

#5

I can't get it to compile...

Build Deps can't be satisfied...

#6

I can't get it to compile...

Build Deps can't be satisfied... That's why you have to fix them :)

totem (1.1.3-0ubuntu3~5.04ubp1) hoary; urgency=low

  * Backport to Ubuntu Hoary
  * Change build-dep in control.in on firefox-dev => mozilla-firefox-dev

 -- Seth Kinast <seth@sethkinast.com>  Thu, 21 Jul 2005 03:59:57 +0000

http://sethkinast.com/ubuntu/hoary/backports/totem/

#7

I don't know how to do that. Looks like I have a lot to learn :D

#8

I don't know how to do that. Looks like I have a lot to learn :D Well, for this particular one, pbuilder-satisfydepends said that firefox-dev couldn't be installed.

So I went to http://packages.ubuntu.com/ and looked up firefox-dev. It is a new package in Breezy; as you can see it has only a Breezy version. The Hoary version is called mozilla-firefox-dev.

So I went into the source tree of totem, into the debian directory, and edited the file control.in to change the Build-Depends from firefox-dev to mozilla-firefox-dev. Cake :)

#9

what is pbuilder-satisflydepends?

Oh, I tried that with my copy, but my depends still aren't satisfied

#10

what is pbuilder-satisflydepends?

Oh, I tried that with my copy, but my depends still aren't satisfied Pbuilder rocks for making backports, because even though I run Breezy, I can backport in a clean-room Hoary environment. See https://wiki.ubuntu.com/PbuilderHowto for more details.

Did you change control.in and not control? If you're not using Pbuilder, you'll need to run sudo apt-get build-dep totem as well.

#11

**Seth]That's why you have to fix them :)

totem (1.1.3-0ubuntu3~5.04ubp1) hoary said:**
> http://sethkinast.com/ubuntu/hoary/backports/totem/[/url]

I have problem with this backport.I have same problem when trying backport Totem 1.1.3 .I install totem , totem-xine and libtotem-plparser0 .Then run Totem click Help --> About .

Totem 1.1.3

**Movie Player using GStreamer version 0.8.9 **

I not install totem-gstreamer.In hoary is gstreamer version 0.8.8 in breezy 0.8.9 

Maybe problem with libxine .In hoary is libxine0 and in breezy libxine1c2
#12

Pbuilder rocks for making backports, because even though I run Breezy, I can backport in a clean-room Hoary environment. See https://wiki.ubuntu.com/PbuilderHowto for more details.

Did you change control.in and not control? If you're not using Pbuilder, you'll need to run sudo apt-get build-dep totem as well.

Yah I changed control.in

Source: totem
Section: gnome
Priority: optional
Maintainer: Sebastien Bacher <seb128@debian.org>
Uploaders: @GNOME_TEAM@
Build-Depends: debhelper (>= 4.2.21), dpatch, libgtk2.0-dev (>= 2.6.0), libglib2.0-dev (>= 2.6.3), libgnomeui-dev (>= 2.6.1.1-4), libglade2-dev (>= 2.4.0), libgnomevfs2-dev (>= 2.8.4), libxine-dev (>= 1-rc5-1), liblircclient-dev (>= 0.6.6), libirman-dev (>= 0.4.2), libgnome-desktop-dev (>= 2.6.1-2), gnome-pkg-tools, scrollkeeper (>= 0.3.14-5), mozilla-firefox-dev, libxml-parser-perl, libgstreamer-gconf0.8-dev (>= 0.8.4.1), libgstreamer0.8-dev (>= 0.8.6.1), libnautilus-burn-dev (>= 2.9.0), libgstreamer-plugins0.8-dev (>= 0.8.4.1), libnautilus-extension-dev, iso-codes, libmusicbrainz4-dev, gnome-icon-theme
Standards-Version: 3.6.1.1

Thats at the top of mine. Yet when I do a sudo apt-get build-dep totem

sudo apt-get build-dep totem
Reading package lists... Done
Building dependency tree... Done
E: Build-dependencies for totem could not be satisfied.
#13

If you're making custom packages, please be responsible and add a "~something" version trailer to it. How would i go about doing this? I've always made the packages just for myself primarily so i never gave it much thought.

#14

How would i go about doing this? I've always made the packages just for myself primarily so i never gave it much thought. To add a custom version string, cd into the root of your source tree after extracting.

Then, run the command dch -i (Debian changelog: insert)

Change the version string to be identical to the version string below yours. Add ~5.04ubp1 Change the target to hoary. [color=red]Note: if the package you're backporting is not Backports-compliant (not in Ubuntu Breezy, for example), you might add your initials to the version string instead of ubp.

Add a changelog entry, something like ** * Backport to Ubuntu Hoary**.

Change the e-mail address to the one specified in your GPG keyring. CTRL - X exits.

You can then run a build and a deb will be created with your new version string :)

#15

What if you don't HAVE a GPG Keyring?

#16

now a bit OT, but built and uploaded :)

#17

I neither have a GPG keyring nor am i sure that i want one ;) Actually i don't even know exaxctly what it is.

#18

I have problem with this backport.I have same problem when trying backport Totem 1.1.3 .I install totem , totem-xine and libtotem-plparser0 .Then run Totem click Help --> About .

Totem 1.1.3

Movie Player using GStreamer version 0.8.9

I not install totem-gstreamer.In hoary is gstreamer version 0.8.8 in breezy 0.8.9

Maybe problem with libxine .In hoary is libxine0 and in breezy libxine1c2

Same problem here. The totem-xine package was accidently built against gstreamer. ;)

  • Rpg Cyco
#19

Yep, I noticed that totem-xine is build against gstreamer too :-(

#20

Yep, I noticed that totem-xine is build against gstreamer too :-( Me too. Actually was a bit interesting to note that Totem-Gstreamer now handles quite a lot of what I need - it was quite a while since I tried it last. I suspect it never will handle it all though, if I've understood the policys correctly.

Any news on a correct rebuild?