Backport Pidgin 2.0.0 Final to Fiesty

Hold your horses man, packages haven't even been uploaded to Debian Experimental yet! When things settle and we get an upload in Ubuntu, I will take a look. I've already begun to play a bit with Debian SVN packaging. It looks promising and backportable when it comes out.

Please reopen this bug report when Ubuntu Gutsy gets an upload.

Sorry to be so preemptive, I guess; I just wanted to get the idea out there. Thanks for looking/the vote of confidence.

Second! Good luck with that.

On 5/5/07, Stephen Seplowitz <email address hidden> wrote:
>
> Sorry to be so preemptive, I guess; I just wanted to get the idea out
> there. Thanks for looking/the vote of confidence.
>
> --
> Backport Pidgin 2.0.0 Final to Fiesty
> https://bugs.launchpad.net/bugs/112511
> You received this bug notification because you are a member of Ubuntu
> Backporters, which is the registrant for Feisty Backports.
>
> --
> ubuntu-backports mailing list
> <email address hidden>
> Modify settings or unsubscribe at:
> https://lists.ubuntu.com/mailman/listinfo/ubuntu-backports
>

It would be cool actually to have it :)

this should be marked as needs info so people feel a little hope

Just tried in prevu now that pidgin hit the repos, fails with:

 -> Considering build-dep libebook1.2-dev
   -> Trying libebook1.2-dev
       -> Cannot install libebook1.2-dev; apt errors follow:
Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
  libebook1.2-dev: Depends: libebook1.2-9 (= 1.10.1-0ubuntu1) but it is not going to be installed
  libnss3-dev: Depends: libnspr4-dev (= 1.8.0.10-3ubuntu1) but it is not going to be installed
E: Broken packages
E: Could not satisfy build-dependency.

I built it from source (well, not ubuntu source, but the orig source fine, so i'm going to take a few looks around and see what can be done about this.)

after successfully backporting evolution-data-server (see https://bugs.launchpad.net/feisty-backports/+bug/114031), pidgin built without a hitch in prevu, and is running without a problem on my workstation right now. it even provides a gaim meta/transition package to help the upgrade path.

b/i/r +1

must build evolution-data-server (see https://bugs.launchpad.net/feisty-backports/+bug/114031) first
then re init prevu
then b/i/r under prevu
+1 feisty

Same here
b/i/r +1

The gutsy package builds fine in feisty if you replace the libnss3-dev with libnss-dev in the build-deps.

b/i/r in prevu
+1 for feisty

the need to backport eds gives me doubts about if this will ever be done officially.

same results here, same comments...

If libebook1.2-9 is present:
b/i/r with prevu
+1 feisty

If not:
 -> Considering build-dep libebook1.2-dev
   -> Trying libebook1.2-dev
       -> Cannot install libebook1.2-dev; apt errors follow:
Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
  libebook1.2-dev: Depends: libebook1.2-9 (= 1.10.1-0ubuntu1) but it is not going to be installed
  libnss3-dev: Depends: libnspr4-dev (= 1.8.0.10-3ubuntu1) but it is not going to be installed
E: Broken packages
E: Could not satisfy build-dependency.

Forgive my possible ignorance, but wouldn't the easiest way to install it, seeing it's in the gutsy repo's and all, be like this?

sudo cp /etc/apt/sources.list /etc/apt/sources.list.pidginbackup
sudo sed -i 's/^deb \([^ ]*\) feisty\(-security\|-updates\|\) \([a-z ]*\)$/deb \1 gutsy\2 \3/' /etc/apt/sources.list
sudo apt-get update
sudo apt-get -y install gaim
sudo mv /etc/apt/sources.list.pidginbackup /etc/apt/sources.list
sudo apt-get update

If it works in feisty, this oughta install the new gaim transitional package and therefore pidgin and all its dependencies. I'm a bit too scared to do it on my laptop, but maybe somebody knows any potential dangers or can deem it "safe"?

So, i held my breath and went to try it. It complained about not having gaim's dependency pidgin in the repos (turns out dk.archive.ubuntu.com isn't quite up-to-date with gutsy). Then when i changed it to use a different mirror that had it, it said the same. So i tried to install pidgin directly (without the -y flag, to see what it offered first), but it gave me a huge load of dependencies that it wanted to install but couldn't. So much for that idea. Sorry for taking your time with a stupid attempt, but i guess some people might learn from it.

We should consider all the reverse dependencies before backporting:
  gaim-autoprofile
  gaim-data
  gaim-dbg
  gaim-dev
  gaim-encryption
  gaim-extendedprefs
  gaim-guifications
  gaim-hotkeys
  gaim-irchelper
  gaim-otr
  gaim-themes
  gaim-thinklight
  galago-gaim-feed
 |gnome-fifth-toe
  meta-ul-desktop-base
  nautilus-sendto

Some of this plugins have now the equivalent for pidgin, but this is not the case for all. We should not break anything (no plugins) with this backport. I think we should wait for all plugins to be released for pidgin.

i know guifications has one
encryption has one

On 5/18/07, Lionel Porcheron <email address hidden> wrote:
> We should consider all the reverse dependencies before backporting:
> gaim-autoprofile
> gaim-data
> gaim-dbg
> gaim-dev
> gaim-encryption
> gaim-extendedprefs
> gaim-guifications
> gaim-hotkeys
> gaim-irchelper
> gaim-otr
> gaim-themes
> gaim-thinklight
> galago-gaim-feed
> |gnome-fifth-toe
> meta-ul-desktop-base
> nautilus-sendto
>
> Some of this plugins have now the equivalent for pidgin, but this is not
> the case for all. We should not break anything (no plugins) with this
> backport. I think we should wait for all plugins to be released for
> pidgin.
>
> --
> Backport Pidgin 2.0.0 Final to Fiesty
> https://bugs.launchpad.net/bugs/112511
> You received this bug notification because you are a direct subscriber
> of the bug.
>

Pidgin has been in Gutsy for a while now.

There are now several sources to get unofficial .debs from third party sources. That's a potential security risk, because theres no way of ensuring the content of the package. However, people seem to want it badly enough that they'll happily sudo away to install it. Also, version 2.0.1 is already out. Backporting this to Feisty is probably a good idea.

At least make it easier to uninstall gaim. As it is now, people are breaking packages trying to get rid of it.

any reason to not backport this package?

I guess it should be backported as fast as possible.
Feisty is a final (stable) release, and the amount of beta packages on it should be minimized. And since gaim is no longer "mantained" (only pidgin), it sould be a good idea to backport the latest stable release it to get upstream support (and also a more stable version).

I don't think we should wait for all the plugins to be released for pidgin since most of the people doesn't use any of them at all or only 2 or 3 (like guifications and extended prefs). Anyway, I think most of the users will be happy only with plain pidgin. And i really think some of the plugins will now be discontinued. And finally I don't consider "not backporting some plugins" a package breakage. All those plugins are recommends or suggests, not depends. Anyone who really needs a certain not-backported plugin should stick to gaim anyway.

I guess backporting pidgin to feisty is only a matter of removing gaim from ubuntu-desktop (or changing it to "gaim | pidgin") and repackaging it. Some upgrades might be necessary but i think people are already working on that.

--
Matt Nicholson
<email address hidden>

On 5/28/07, Mahdi <email address hidden> wrote:
>
> I guess it should be backported as fast as possible.
> Feisty is a final (stable) release, and the amount of beta packages on it
> should be minimized. And since gaim is no longer "mantained" (only pidgin),
> it sould be a good idea to backport the latest stable release it to get
> upstream support (and also a more stable version).
>
> I don't think we should wait for all the plugins to be released for
> pidgin since most of the people doesn't use any of them at all or only 2
> or 3 (like guifications and extended prefs). Anyway, I think most of the
> users will be happy only with plain pidgin. And i really think some of
> the plugins will now be discontinued. And finally I don't consider "not
> backporting some plugins" a package breakage. All those plugins are
> recommends or suggests, not depends. Anyone who really needs a certain
> not-backported plugin should stick to gaim anyway.
>
> I guess backporting pidgin to feisty is only a matter of removing gaim
> from ubuntu-desktop (or changing it to "gaim | pidgin") and repackaging
> it. Some upgrades might be necessary but i think people are already
> working on that.

acctually, when building pedgin in prevu, a gaim*>deb is generated, for the
sole purpose of allowing upgrades. since ubuntu-desktop depends on gaim, and
the new gaim package is nothing , or than depending on pidgin (well it
cleans up some things i think), the upgrade path is clean, and doesn't
require ubuntu-desktop etc to be rebuilt.

--
> Backport Pidgin 2.0.0 Final to Fiesty
> https://bugs.launchpad.net/bugs/112511
> You received this bug notification because you are a direct subscriber
> of the bug.
>

I am currently analyzing if the eds dependency will have any negative
consequences. Otherwise, it should be good for backporting. We will handle
the plugins after the backport of pidgin is complete.

On Tue, May 29, 2007 at 07:21:56PM -0000, John Dong wrote:
> I am currently analyzing if the eds dependency will have any negative
> consequences. Otherwise, it should be good for backporting. We will handle
> the plugins after the backport of pidgin is complete.

If you replace libnss3-dev with libnss-dev in the pidgin Build-Depends,
you don't need an updated eds.

I backported Pidgin 2.0.0 from the Gusty repo, and then updated it to 2.0.1, and built it along with OTR and Guifications (the two major external plugins that I use). The Pidgin packages are from Gusty's source and built (after being updated to Pidgin 2.0.1) and the OTR and Guifications packages were done with checkinstall because I couldn't figure out how to debianize them properly. They are all available in a tarball on my site though, at http://www.trausch.us/pidgin/ if anyone is interested. The packages in the tar file will drop into an IA32 Feisty system. I have not had any issues with these binaries as of yet, and I have been using them for a little bit now.

Note that while I am happy to provide the binaries to the entire world, I can't offer support for them; use them at your own risk if you choose to use them at all. But, it worked out with some minor tweaks to the build-deps in the Pidgin package, and it had been working for me since I built and installed it, so it seems good.

ah, how cool, I'll look more at this tomorrow and make a decision by the
end of the week.

On 5/29/07, Mikael Eriksson <email address hidden> wrote:
>
>
> If you replace libnss3-dev with libnss-dev in the pidgin Build-Depends,
> you don't need an updated eds.
>
> --
> Backport Pidgin 2.0.0 Final to Fiesty
> https://bugs.launchpad.net/bugs/112511
> You received this bug notification because you are a member of Ubuntu
> Backporters, which is the registrant for Feisty Backports.
>
> --
> ubuntu-backports mailing list
> <email address hidden>
> Modify settings or unsubscribe at:
> https://lists.ubuntu.com/mailman/listinfo/ubuntu-backports
>

It should definitely be 2.0.1 which should be backported. But it's not yet in the repos...

Is there a way that I can send my 2.0.1 sources that I built to Ubuntu for integration/inspection? I could do that. The plugins, however, are not even debianized, and the last time that I checked, they were not available from Gutsy’s source repository, either.

2.0.2 will be out next week...

Is there a way to view the changelog before release? Or will I have to wait for the release to see what is in it? I have no clue how to use the SCM system that they are using.

I'd also like to see the extra Gaim packages backported and renamed for Pidgin. Is this possible, or will these just not work with Pidgin? I know that pidgin-libnotify and pidgin-guifications are at least available on http://getdeb.net, and they work fine with Pidgin in my Feisty install.

gaim-autoprofile
gaim-encryption
gaim-extendedprefs
gaim-guifications
gaim-hotkeys
gaim-irchelper
gaim-libnotify
gaim-otr
gaim-themes
gaim-thinklight
gaim-xmms-remote

It would also be nice to see packages related to Gaim updated to work with Pidgin:
festival-gaim
galago-gaim-feed
nautilus-sendto

And does anyone know if Beagle packages need to be updated to index Pidgin logs?

http://developer.pidgin.im/roadmap will let you see which bugs have been closed against future releases... Don't put too much stock in the open bugs though, some of them get pushed back if they can't meet the deadline.

2.1.0 will be the next "big" upgrade and only 3 weeks away, so it probably doesn't particularly matter which version is in the repository version until then.

Any guess as to when this might be available? I'm trying to weigh my options...

On Wed, 2007-06-20 at 02:05 +0000, Jamie Jackson wrote:

> Any guess as to when this might be available? I'm trying to weigh my
> options...

I don't know when there will be an official backport... however, I do
have a package available (well, packages) available from
http://www.trausch.us/pidgin/ where you can download a tarball with
Pidgin 2.0.1 packages. Included in the tarball are the following:

 - gaim_2.0.1-1_all.deb: dummy upgrade package to satisfy the
ubuntu-desktop dependency.
 - pidgin-data_2.0.1-1_all.deb - replaces gaim-data (backported from
Gutsy, then updated to 2.0.1 from upstream)
 - pidgin_2.0.1-1_i386.deb - replaces gaim (backported from Gutsy, then
updated to 2.0.1 from upstream)
 - pidgin-guifications_2.14-1_i386.deb - Guifications plugin (built w/
checkinstall with upstream tarball)
 - libotr_3.0.0-1_i386.deb - OTR library (built w/ checkinstall with
upstream tarball)
 - pidgin-otr_3.0.0-1_i386.deb - OTR plugin (built w/ checkinstall with
upstream tarball)

The packages that are built with checkinstall will require that you
uninstall the previous ones, if necessary (that is, you have to manually
uninstall gaim-guifications, libotr, and gaim-otr from the Feisty system
if you have them; they were not available from the Gutsy repo when I
built Pidgin, though I can try to come up with the time tomorrow to make
cleaner packages if necessary). However, DO NOT UNINSTALL GAIM, as the
gaim/pidgin-data/pidgin packages will cleanly replace their Feisty
counterparts.

There seems to be two added dependencies, that you must fetch from the
repositories: libmeanwhile1 and libavahi-compat-howl0, both of which can
be installed from the repositories. libavahi-compat-howl0 is in
Universe, while libmeanwhile1 is in Main.

A note worth mentioning: While I have been using these packages since I
built them on May 29 without issue, I am not supporting the packages
actively. I am certainly willing to try to help with issues related
directly to them, but I don't have a great deal of time due to school
and all. I can be reached by Internet mail if there are any questions.
I don't know how to go about getting anything done in the backports
system, though, so this is about the best that I know how to, and can,
do for now. Of course, 2.0.2 is out now, and I hear that 2.1.0 is
coming soonish. If I have extra time I will update my packages to
2.0.2. And no, I don't have a repository setup, because I haven't had
the time to figure out how to do all that yet, and I only expect to be
keeping up with Pidgin until they are able to backport it.

    — Mike

--
Michael B. Trausch
           <email address hidden>
Phone: (404) 592-5746
                          Jabber IM:
           <email address hidden>
Demand Freedom! Use open and free protocols, standards, and software!
Support free speech---it is the most valuable freedom we have!

Very good.
Are there any amd64 builds avaiable other than getdeb's? Their version do not seem to be very clean (i.e.: do not replace gaim with a dummy pkg).
Does pidgin have any BIG change, or important feature not in Feisty's gaim?

[]z

M.

On Wed, 2007-06-20 at 12:30 +0000, Mahdi wrote:

> Very good.
> Are there any amd64 builds avaiable other than getdeb's? Their version
> do not seem to be very clean (i.e.: do not replace gaim with a dummy
> pkg).
> Does pidgin have any BIG change, or important feature not in Feisty's
> gaim?

It has hundreds of bugfixes, though I don't know if any of the AMD64
GAIM bugs are fixed. I might be able to build an AMD64 version, though,
at some point. I reverted to 32-bit Ubuntu because the 64-bit system
was fine overall, but GAIM crashed a LOT—which I couldn't deal with.

I can try making 64-bit packages later today.

    — Mike

--
Michael B. Trausch
           <email address hidden>
Phone: (404) 592-5746
                          Jabber IM:
           <email address hidden>
Demand Freedom! Use open and free protocols, standards, and software!
Support free speech---it is the most valuable freedom we have!

Hi Mike,

I've have installed from repos (via apt) and have installed from source
before. However, I haven't done much, if anything in-between (which this
seems to be). Once this stuff gets in the repos, will I automatically get
updates, etc. (as opposed to when I install from source)?

BTW, here's a step-by-step for noobs (like me), because it took me a little
while to figure out how to do it. I'd post it in your site's comments, but
the comments are closed.

Thanks,
Jamie

sudo apt-get install libmeanwhile1 libavahi-compat-howl0
cd ~
wget http://www.trausch.us/wp-content/uploads/pidgin-feisty.tar
mkdir pidgin-feisty
cd pidgin-feisty
tar xvf ../pidgin-feisty.tar
sudo dpkg -i ./*

On 6/19/07, Michael Trausch <email address hidden> wrote:
>
> On Wed, 2007-06-20 at 02:05 +0000, Jamie Jackson wrote:
>
> > Any guess as to when this might be available? I'm trying to weigh my
> > options...
>
>
> I don't know when there will be an official backport... however, I do
> have a package available (well, packages) available from
> http://www.trausch.us/pidgin/ where you can download a tarball with
> Pidgin 2.0.1 packages. Included in the tarball are the following:
>
> - gaim_2.0.1-1_all.deb: dummy upgrade package to satisfy the
> ubuntu-desktop dependency.
> - pidgin-data_2.0.1-1_all.deb - replaces gaim-data (backported from
> Gutsy, then updated to 2.0.1 from upstream)
> - pidgin_2.0.1-1_i386.deb - replaces gaim (backported from Gutsy, then
> updated to 2.0.1 from upstream)
> - pidgin-guifications_2.14-1_i386.deb - Guifications plugin (built w/
> checkinstall with upstream tarball)
> - libotr_3.0.0-1_i386.deb - OTR library (built w/ checkinstall with
> upstream tarball)
> - pidgin-otr_3.0.0-1_i386.deb - OTR plugin (built w/ checkinstall with
> upstream tarball)
>
> The packages that are built with checkinstall will require that you
> uninstall the previous ones, if necessary (that is, you have to manually
> uninstall gaim-guifications, libotr, and gaim-otr from the Feisty system
> if you have them; they were not available from the Gutsy repo when I
> built Pidgin, though I can try to come up with the time tomorrow to make
> cleaner packages if necessary). However, DO NOT UNINSTALL GAIM, as the
> gaim/pidgin-data/pidgin packages will cleanly replace their Feisty
> counterparts.
>
> There seems to be two added dependencies, that you must fetch from the
> repositories: libmeanwhile1 and libavahi-compat-howl0, both of which can
> be installed from the repositories. libavahi-compat-howl0 is in
> Universe, while libmeanwhile1 is in Main.
>
> A note worth mentioning: While I have been using these packages since I
> built them on May 29 without issue, I am not supporting the packages
> actively. I am certainly willing to try to help with issues related
> directly to them, but I don't have a great deal of time due to school
> and all. I can be reached by Internet mail if there are any questions.
> I don't know how to go about getting anything done in the backports
> system, though, so this is about the best that I know how to, and can,
> do for now. Of course, 2.0.2 is out now, and I hear that 2.1.0 is
> coming soonish. If I have extra time I will update m...

On Wed, 2007-06-20 at 21:33 +0000, Jamie Jackson wrote:

> I've have installed from repos (via apt) and have installed from
> source
> before. However, I haven't done much, if anything in-between (which
> this
> seems to be). Once this stuff gets in the repos, will I automatically
> get
> updates, etc. (as opposed to when I install from source)?
>
> BTW, here's a step-by-step for noobs (like me), because it took me a
> little
> while to figure out how to do it. I'd post it in your site's comments,
> but
> the comments are closed.

Sorry, I was going to get to it and I just got lost in all of the other
things going on. I put your stuff up on the page, so it is now
accessible. Thanks!

    — Mike

--
Michael B. Trausch
           <email address hidden>
Phone: (404) 592-5746
                          Jabber IM:
           <email address hidden>
Demand Freedom! Use open and free protocols, standards, and software!
Support free speech---it is the most valuable freedom we have!

Just built Pidgin 2.0.2 for Feisty AMD64 using prevu. Had to get source and change all references of libnss3 to libnss, but the application still runs flawlessly (since pidgin is designed to work with either libnss or libnss3 anyway). This was the only dependency I needed to change in my build. I'd attach the deb, but you need both the pidgin and pidgin-data backports. If people want it, I can upload both debs here or elsewhere.

I'll be working on backporting pidgin-otr next.

I have a new 32-bit version on my site: http://www.trausch.us/pidgin

All of the packages are now backported from Gutsy, and I have a shell
script that will manage the upgrade from my old checkinstall-generated
packages to the ones backported from Gutsy. I can still do a 64-bit
version soonish; I am planning on doing it anyway, all I need to do is
install 64-bit Feisty onto another partition and build it there.

Questions/comments/concerns are welcome to be aired at my site.

    — Mike

I ran it, and it seemed to work. Well, Pidgin still runs, anyway.

The installer just disappears at the end, though, and I think there might
have been some things that I missed. A pause at the end might be nice (and a
summary, even better).

Thanks for your efforts,

Jamie

On 6/25/07, Michael Trausch <email address hidden> wrote:
>
> I have a new 32-bit version on my site: http://www.trausch.us/pidgin
>
> All of the packages are now backported from Gutsy, and I have a shell
> script that will manage the upgrade from my old checkinstall-generated
> packages to the ones backported from Gutsy. I can still do a 64-bit
> version soonish; I am planning on doing it anyway, all I need to do is
> install 64-bit Feisty onto another partition and build it there.
>
> Questions/comments/concerns are welcome to be aired at my site.
>
> — Mike
>
> --
> Backport Pidgin 2.0.0 Final to Fiesty
> https://bugs.launchpad.net/bugs/112511
> You received this bug notification because you are a direct subscriber
> of the bug.
>

If you want, I can send you the debs built for my amd64 build so you don't have to take the time. Built with prevu from Gutsy sources pidgin and pidgin-data, changing all references of libnss3 to libnss

On Tue, 2007-06-26 at 00:50 +0000, Neatchee wrote:

> If you want, I can send you the debs built for my amd64 build so you
> don't have to take the time. Built with prevu from Gutsy sources
> pidgin
> and pidgin-data, changing all references of libnss3 to libnss

That should work. If you could e-mail them to me in a tar file, I can
get them up by tomorrow along with a script to automatically pull and
install them.

Unfortunately, I don't know quite how to do the APT repository dance,
and so I would be perfectly willing to contribute the binary packages
that I have (the src packages are available in the Feisty src tree) to
someone that has an APT repo or is willing to create one.

Incidentally, what is the status of the official backport to Feisty?
Are there plans for one? It works quite well, and would be far better
for everyone if they were added to feisty-backports.

    — Mike

--
Michael B. Trausch
           <email address hidden>
Phone: (404) 592-5746
                          Jabber IM:
           <email address hidden>
Demand Freedom! Use open and free protocols, standards, and software!
Support free speech---it is the most valuable freedom we have!

I'd second but I'm not second. So I'll just say I want this too...only I want 2.1.0 (which though it hasn't been released yet, probably will be by the time this is implemented ;))

On Thu, 2007-06-28 at 17:58 +0000, rageboy wrote:

> I'd second but I'm not second. So I'll just say I want this too...only
> I
> want 2.1.0 (which though it hasn't been released yet, probably will be
> by the time this is implemented ;))

Well, if/when 2.1.0 hits Gutsy I will update the packages on my web
site.

Or, if it doesn't and some time passes after it is released, I will
attempt to do the port to Feisty myself and see what happens.

    — Mike

--
Michael B. Trausch
           <email address hidden>
Phone: (404) 592-5746
                          Jabber IM:
           <email address hidden>
Demand Freedom! Use open and free protocols, standards, and software!
Support free speech---it is the most valuable freedom we have!

Hey Mike, did you get that tarball for x64 that I sent you? Want to make sure that it came through alright.

Let me know if you need anything else built (I don't necessarily keep up to date on Pidgin development)

On Thu, 2007-06-28 at 18:51 +0000, Neatchee wrote:

> Hey Mike, did you get that tarball for x64 that I sent you? Want to
> make sure that it came through alright.
>
> Let me know if you need anything else built (I don't necessarily keep
> up
> to date on Pidgin development)

Hrm. It doesn't seem so... it didn't hit my spam folder, either.

Is there somewhere that you can upload it to and I can download it and
then put it up?

    — Mike

--
Michael B. Trausch
           <email address hidden>
Phone: (404) 592-5746
                          Jabber IM:
           <email address hidden>
Demand Freedom! Use open and free protocols, standards, and software!
Support free speech---it is the most valuable freedom we have!

No worries, boss!

Pidgin_2.0.2-0ubuntu1~7.04prevu1_amd64.deb & Pidgin-data_2.0.2-0ubuntu1~7.04prevu1_amd64.deb, both required to build a basic working install of Pidgin on AMD64 feisty. Backported from Gutsy source repositories using prevu. Tarball: http://www.ansemreport.com/neatchee/pidgin+pidgin-data_2.0.2-0ubuntu1~7.04prevu1_amd64.tar

Pidgin-dev_2.0.2-0ubuntu1~7.04prevu1_amd64.deb & pidgin-dbg_2.0.2-0ubuntu1~7.04prevu1_amd64.deb, required for compiling some additional packages (such as Off the Record). Backported from Gusty srouces repositories using prevu. Tarball: http://www.ansemreport.com/neatchee/pidgin-dev+pidgin-dbg_2.0.2-0ubuntu1~7.04prevu1_amd64.tar

I might recommend running a test install, since this is my first backport XD

Basically I just downloaded the source for each package, made the changes necessary to get it to successfully build on Feisty (in this case, change all dependencies on libnss3 to just libnss), built the debs using preview and installed. The prevu-built debs are what you're getting here. That should be all that needs to be done, correct? Unless you're going to add scripts to have it successfully replace Gaim installations. That's all you though :)

On Thu, 2007-06-28 at 19:33 +0000, Neatchee wrote:

> Basically I just downloaded the source for each package, made the
> changes necessary to get it to successfully build on Feisty (in this
> case, change all dependencies on libnss3 to just libnss), built the
> debs
> using preview and installed. The prevu-built debs are what you're
> getting here. That should be all that needs to be done, correct?
> Unless you're going to add scripts to have it successfully replace
> Gaim
> installations. That's all you though :)

:-)

I have a script for the 32-bit version, but I only wrote that to update
from the previous version that I released that was broken (it used
checkinstall to do its work, and checkinstall doesn't do things in an
Ubuntu-compliant fashion). New installs can just dpkg -i * and then
pull any deps manually, though I can easily modify my existing script to
do that for users. It would probably be far easier to provide an apt
repo, but I can't figure out how to set that up with the amount of time
that I have available right now, so the script is the Right Thing.

I will download these and get them up within 24 hours.

    — Mike

--
Michael B. Trausch
           <email address hidden>
Phone: (404) 592-5746
                          Jabber IM:
           <email address hidden>
Demand Freedom! Use open and free protocols, standards, and software!
Support free speech---it is the most valuable freedom we have!

Eep!

Neatchee, those packages won't cleanly install as an upgrade—it's missing the dummy package!

There should also be a gaim-2.0.2 package that has next to no bulk to it whatsoever—it's a dummy compatibility/upgrade package for systems like Feisty where gaim has to be replaced. Do you have that to go along with your packages, as well?

Hey man. The dummy package, gaim_2.0.2-0ubuntu1_all.deb, is available from the Gutsy repos and works as-is as far as I'm aware. No backporting needed. I can't even TRY to backport it because when prevu tries to pull the source packages for the gaim transitional package, it's referenced to the pidgin source package XD (see the bottom of this page for what i'm talking about: http://packages.ubuntu.com/gutsy/net/gaim )

In short: you can use the same dummy upgrade package for amd64 feisty that you would use for your other pidgin backports :) Or you can link people to this download page: http://packages.ubuntu.com/cgi-bin/download.pl?arch=all&file=pool%2Fmain%2Fp%2Fpidgin%2Fgaim_2.0.2-0ubuntu1_all.deb&md5sum=e680a30bdd9145f191dbe8518d348b3e&arch=all&type=main

On Fri, 2007-06-29 at 14:40 +0000, Neatchee wrote:

> Hey man. The dummy package, gaim_2.0.2-0ubuntu1_all.deb, is available
> from the Gutsy repos and works as-is as far as I'm aware. No
> backporting needed. I can't even TRY to backport it because when
> prevu
> tries to pull the source packages for the gaim transitional package,
> it's referenced to the pidgin source package XD (see the bottom of
> this
> page for what i'm talking about:
> http://packages.ubuntu.com/gutsy/net/gaim )

I can do that. I just feel more comfy taking everything that is built
together and using that, if you know what I mean. :-) When you build
the pidgin source package, you get gaim, pidgin, pidgin-data,
pidgin-dev, pidgin-dbg as output binary packages. I can just include my
GAIM upgrade package with the distribution, and I will have it up later
today (I have to run out to do some errands, first).

    — Mike

--
Michael B. Trausch
           <email address hidden>
Phone: (404) 592-5746
                          Jabber IM:
           <email address hidden>
Demand Freedom! Use open and free protocols, standards, and software!
Support free speech---it is the most valuable freedom we have!

I'm getting the impression from the comments on here that an official backport in the repos isn't happening anytime soon?

On Fri, 2007-06-29 at 16:55 +0000, rageboy wrote:

> I'm getting the impression from the comments on here that an official
> backport in the repos isn't happening anytime soon?

AFAIK, there has been no mention of an official backport.

However, on my page I have:

http://www.trausch.us/pidgin - Instructions/links for installing Pidgin
from the packages that I have which have been backported from Gutsy.

The 32-bit version and OTR/Guifications plugins have been done by
myself; the 64-bit version was done by Neatchee. The 32-bit version has
a script available for its installation; I did it that way because the
older 32-bit version that I did wasn't 100% backported, while everything
that is up there now is.

    — Mike

--
Michael B. Trausch
           <email address hidden>
Phone: (404) 592-5746
                          Jabber IM:
           <email address hidden>
Demand Freedom! Use open and free protocols, standards, and software!
Support free speech---it is the most valuable freedom we have!

This bug is for getting informations for an official backport. This is not a forum for backporting pidgin. Thanks!

The amd64 pkgs work fine :) tkz a lot folks.

I'd like to interject that I don't think a simple backport of pidgin is possible. Yes, I know that it works fine - I'm using it myself - but there are integration problems. nautilus-sendto doesn't support pidgin because it has different dbus paths than gaim, for instance. There are also a large number of plugins that need to be backported with pidgin.

If people really want a backport either an unofficial backport (as some have already posted) or a backport which can be installed side-by-side with gaim would be best.

While pidgin does not properly integrate with nautilus-sendto, this is more of a convenience issue, isn't it? I've installed nautilus-sendto with pidgin, and while pidgin does not show up as a send-to option, it does not otherwise break nautilus-sendto. In addition, the functionality is still there (i.e. you can still send files via Pidgin, just not from a right-click menu). Convenience may be lost, yes, but it doesn't break anything.

I think a bigger concern is the fact that other plugins don't work properly, such as pidgin-otr (the version of libotr2 and libotr2-bin available in the feisty repos has a bug that makes it not work with pidgin-otr. This is fixed in the next version of libotr2, which is still officially in testing [though I'm using it and it seems perfectly stable])

I looked at the suggested list, and saw that two of the selections need a rewrite, which is...
galago-gaim-feed and meta-ul-desktop-base

as for more suggestions, how about the following, and also not forgetting to do pidgin version 2.0.2.
pidgin-console ( finch in other words )
pidgin-console-dbg ( debug version of finch. )
pidgin-console-dev ( development files for finch. )
pidgin-xfire ( svn release of code: http://www.fryx.ch/xfire/ )

Trausch and I have updated packages available on his website for Pidgin 2.1.0 We have i386 and AMD64 packages available, along with a plethora of plugins. You can grab them from http://www.trausch.us/pidgin (see below for more information on what packages are done)

In an attempt to get this moving towards an official backport I'm going to try and get a handle on where we are with all related packages that have been presented in this bug report...

Packages built and tested for i386 and AMD64 (available at http://www.trausch.us/pidgin):

   pidgin, pidgin-data, pidgin-dev, pidgin-dbg, libotr2, libotr2-dev, pidgin-otr, pidgin-guifications, pidgin-extprefs, pidgin-hotkeys, purple-plugin-pack, pidgin-blinklight, pidgin-lrvp, pidgin-libnotify, nautilus-sendto, gaim-xfire

**Notes -
    1. Many of these packages also have accompanying dummy transitional packages.
    2. nautilus-sendto was compiled from a source build that is in testing, but awaiting upload to the Debian FTP (at which point it will move to stable), with an additional patch for transition from gaim to pidgin
    3. gaim-xfire is built from the most recent snapshot available at http://gfire.sourceforge.net/snapshots/ It has not been thoroughly tested, but works cleanly as far as I can tell.

Packages that have been abandoned by their maintainer:

  gaim-autoprofile, festival-gaim, gaim-xmms-remote (only activity in the past 289 was to move the newest version from testing to stable, but this package still does not support pidgin, so I'm going to assume it's abandoned unless I hear otherwise)

Other packages:

  gaim-encryption has been upgraded to pidgin-encryption and included in gutsy, however our attempts to backport have been unsuccessful. pidgin-encryption requires libnspr4-dev to build (libnspr-dev fails), which in turn requires libnss3-dev (libnss-dev fails), which conflicts with the entire Feisty system pretty much (tries to remove gnome-desktop LOL). If anyone can lend their expertise on this item, it would be appreciated.

  gaim-irchelper has been merged into purple-plugin-pack

  gaim-themes has been merged into pidgin-data

  galago-gaim-feed is awaiting an update from the galago project team. Currently there are two conflicting patches in the trac. One patch transitions the package to pidgin (though I haven't tested it, and upon inspection, I'm skeptical of whether it works or not), while the other patch is from Ubuntu and adds German language support and fixes a timestamping problem. These two patches do not work together, and the galago team is due to update galago-gaim-feed soon anyway, based on their update schedule. Either way, I don't think there is very high demand for this plugin, though I could be wrong, not to mention that there is an Evolution integration plugin standard in pidgin now, so galago seems a bit superfluous, unless people are using it with other software.

  gnome-fifth-toe, meta-ul-desktop-base are package suites. They are empty packages that require a number of other packages. Basically a "best of" bundle. All that's needed is for the maintainers of these packages to change the dependencies from gaim to pidgin.

 pidgin-console, pidg...

Trausch went to bed, and his website requires that all comments be approved, so until he wakes up, here's where you can grab the i386 extra plugins: http://www.ansemreport.com/pidgin/pidgin-2.1.0-i386_extras.tar.bz2

gaim-xfire is now included in the extras plugin packages, so if you're looking for it, that's where you'll find it.

Hey Neatchee,

could you include http://code.google.com/p/musictracker/ in your extra plugins tar?

Music Tracker has been added to both extra plugin tarballs, as requested.

The amd64 package has been tested on my own PC. I don't have an i386 computer that I can test the package on (just one to build it on), so let me know if it doesn't work.

Thank you, i386 musictracker works fine...

Scratch that request for help on pidgin-encryption I'm just a little slow and forgot to change some of the flags in debian/rules We've now got pidgin-encryption working as well.

In addition to the inclusion of these extra packages, Trausch and I have also created an apt repository for all of our backports. You'll be able to get the following packages (i386, AMD64, and source):

pidgin
pidgin-blinklight
pidgin-data
pidgin-dbg
pidgin-dev
pidgin-encryption
pidgin-extprefs
pidgin-guifications
pidgin-hotkeys
pidgin-libnotify
pidgin-librvp
pidgin-otr
pidgin-plugin-pack
gaim-xfire --works with Pidgin, despite the gaim naming convention
libotr2
libotr2-bin
libotr2-dev
musictracker
nautilus-sendto
gaim (transitional)
gaim-extendedprefs (transitional)
gaim-guifications (transitional)
gaim-hotkeys (transitional)
gaim-irchelper (transitional)
gaim-libnotify (transitional)
gaim-thinklight (transitional)

To add our repository to your apt source.list, simply add the following lines:

deb http://www.ansemreport.com/pidgin/repo feisty feisty-backports
deb-src http://www.ansemreport.com/pidgin/repo feisty feisty-backports

Please put these packages under the full stress test. If we've done something wrong in the packaging (which I can probably guarantee you we have) let us know and we'll fix it. The more testing we can do, the higher the chances are of getting an official backport approved.

I tried the package and it seems to work fine for me. My settings have been successfully imported.

Hmm, I just noticed nautilius-sendto still says "Instant Message (Gaim)", which probably should be replaced by "Instant Message (Pidgin)" ...

The nautilus-sendto issue isn't something we would work on. Submit a bug report (report à la bug) to the nautilus-sendto developers :)

By request, we've also included pidgin-sipe in our repo, which adds support for the IM features of SIP/E. As I understand it, the protocol also works with Live Communication Server messaging.

Hi guys, I was able to build pidgin no problem but I couldn't really figure
out how to get the gaim-otr package to work. Did anyone else get it working
with pidgin? I guess it would be pidgin-otr now.

On 8/16/07, Neatchee <email address hidden> wrote:
>
> The nautilus-sendto issue isn't something we would work on. Submit a
> bug report (report à la bug) to the nautilus-sendto developers :)
>
> By request, we've also included pidgin-sipe in our repo, which adds
> support for the IM features of SIP/E. As I understand it, the protocol
> also works with Live Communication Server messaging.
>
> --
> Backport Pidgin 2.0.0 Final to Fiesty
> https://bugs.launchpad.net/bugs/112511
> You received this bug notification because you are a direct subscriber
> of the bug.
>

leps wrote:
> Hi guys, I was able to build pidgin no problem but I couldn't really figure
> out how to get the gaim-otr package to work. Did anyone else get it working
> with pidgin? I guess it would be pidgin-otr now.
>
> On 8/16/07, Neatchee <email address hidden> wrote:
>
>> The nautilus-sendto issue isn't something we would work on. Submit a
>> bug report (report à la bug) to the nautilus-sendto developers :)
>>
>> By request, we've also included pidgin-sipe in our repo, which adds
>> support for the IM features of SIP/E. As I understand it, the protocol
>> also works with Live Communication Server messaging.
>>
>> --
>> Backport Pidgin 2.0.0 Final to Fiesty
>> https://bugs.launchpad.net/bugs/112511
>> You received this bug notification because you are a direct subscriber
>> of the bug.
>>
>>
>
>
If you are using our repository, you should simply do "sudo apt-get
install pidgin-otr" and restart pidgin, Off-the-Record Messaging should
appear in the list of plugins. After that, you're getting into actual
configuration of OTR, for which you can find help all over the interwebs :)

If you're NOT using our repository, then you should be XD Haha, just
kidding. We included instructions on our website
(www.trausch.us/pidgin) for building OTR successfully for Pidgin. It
requires a few tweaks to the build-deps but it works just fine. If you
want detailed instructions on how to get OTR 3.1.0 working (since Gutsy
repos still only have 3.0.0), feel free to email us (as this isn't
really a build-help forum).

Jo Vermeulen wrote:
> Hmm, I just noticed nautilius-sendto still says "Instant Message
> (Gaim)", which probably should be replaced by "Instant Message (Pidgin)"
> ...
>
>
Just updated the repo with a new version of nautilus-sendto. Though
this version is still technically "unstable" i did some looking over it
and the only changes that were made shouldn't cause any problems. It
adds official support for Pidgin (instead of just applying a few patches
to make it work), and adds support for gnome-bluetooth. It also
includes the ubuntu patch which adds some dependency parameters, fixes a
bug with Thunderbird integration, and a few other things. See the
changelog for full details.

This should also fix it to say "Pidgin" instead of "Gaim" when using
sendto :)

Jo Vermeulen wrote:
> Hmm, I just noticed nautilius-sendto still says "Instant Message
> (Gaim)", which probably should be replaced by "Instant Message (Pidgin)"
> ...
>
>
Ok, scratch that. Apparently the package is thoroughly broken. Taking
it off the repo.

Brian Resnik wrote:
> Jo Vermeulen wrote:
>
>> Hmm, I just noticed nautilius-sendto still says "Instant Message
>> (Gaim)", which probably should be replaced by "Instant Message (Pidgin)"
>> ...
>>
>>
>>
> Ok, scratch that. Apparently the package is thoroughly broken. Taking
> it off the repo.
>
>

Problem solved. Two references to the function gaim_debug_info were
left unchanged. They should have been changed to purple_debug_info.
Patched, rebuilt, and reuploaded.

We've updated our repo with Pidgin 2.1.1 for Feisty. Again, instructions can be found at www.trausch.us/pidgin on how to use our repo, or build these backports yourself.

Updated pidgin from 2.1.1-1ubuntu1 --> 2.1.1-2ubuntu2, and included a patch to force the offline message emulation plugin to a lower priority, thus preventing it from interfering with other plugins (like /exec). Previously, OME would set the message content to NULL to early in the handling order, and cause a segfault in slashexec if both plugins were enabled. Final versioning is 2.1.1-2ubuntu3~7.04prevu1 (we know this isn't an official ubuntu version, but we wanted to delineate the fact that this has the patch included, while preserving proper upgrading prioritizing)

This update also splits the packages a bit differently. If you use finch, finch's development files, or the libpurple development files, you will need to take the additional step of installing those three packages: finch, finch-dev, and libpurple-dev, respectively.

We've also updated the purple-plugin-pack from the guifications plugins team from 1.0 --> 2.1.1 (the coincidence of the versioning is not lost on us). An additional patch was added (bringing it up to a self-versioned 2.1.1-2~7.04prevu1) which stops slashexec from causing a segfault, even if it receives a NULL content message. For a full list of updates, you can visit the guifications page at http://plugins.guifications.org

It should be noted that an official backport doesn't seem likely at this point. We've had some conversations with people behind the scenes here, and there are some...concerns. Mostly it seems they don't want to do the work involved with updating all the related packages (nautilus-sendto, etc, even though we've done all of the work we could find to do on related packages), but there's also an issue of trust. We're not known to the packaging team, and therefor aren't assumed as a trustworthy backporting team.

if you'd like to see our work supported in an official capacity, let the good people at canonical know that our packages are safe, breakage-free, and complete :)

As usual, all of this can be found over at http://www.trausch.us/pidgin

Hi Bug,<br/><br/>

<email address hidden> has invited you to Spokeo,
which finds your friends' updates across the Web.

On average, Spokeo finds 87 friends across 30 different social
networks. See what Spokeo can find for you now!

Click http://www.spokeo.com/public/join?c=0ad4b719c3d5d85da61d7d683a6d74482edd75d3 to accept your invitation.

-----
This invitation was sent with neatchee's approval.
If you wish to opt out of all future emails, go to http://www.spokeo.com/optout?c=1495450495451555449

Copyright (c) 2008 Spokeo, Inc. All rights reserved.
1685 Plymouth Street #200, Mountain View, CA 94043

My apologies to anyone who got that last email. Damn webapp sending out emails to everyone on my gmail that I ever sent or received an email from. Gotta be more careful with these things :(

This bug is irrelevant now.