Sync gloox 1.0.9-2 (universe) from Debian experimental (main)

Bug #1273967 reported by Vincent Cheng
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
0ad (Ubuntu)
Fix Released
Undecided
Unassigned
fatrat (Ubuntu)
Fix Released
Undecided
Unassigned
gloox (Ubuntu)
Fix Released
Undecided
Unassigned
licq (Ubuntu)
Fix Released
Undecided
Unassigned
uwsgi (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

Please sync gloox 1.0.9-2 (universe) from Debian experimental (main)

Explanation of the Ubuntu delta and why it can be dropped:
  * Use dh-autoreconf instead of autotools-dev to also fix FTBFS on ppc64el by
    getting new libtool macros (still updates config.{sub,guess}).

Explanation: Ubuntu diff merged into Debian. Note that due to the soname bump, a few packages (0ad, licq, uwsgi, fatrat) have to be rebuilt, and I'm not sure what the protocol for requesting rebuilds of packages in Ubuntu is (I've already requested a transition slot / binNMUs in Debian, awaiting approval which is why it's in experimental and not unstable).

Ideally I'd like to get this into trusty to fix some connectivity issues in 0ad's in-game lobby.

Changelog entries since current trusty version 1.0-3ubuntu1:

gloox (1.0.9-2) experimental; urgency=medium

  * Run dh-autoreconf instead of autotools-dev. (Closes: #726278, #735987)

 -- Vincent Cheng <email address hidden> Mon, 27 Jan 2014 22:16:13 -0800

gloox (1.0.9-1) experimental; urgency=medium

  * Upload to experimental.
  * New upstream release. (Closes: #729074)
    - SRV record lookup enabled. (Closes: #593150)
    - Refresh patch.
  * Update debian/copyright (GPLv2+ -> GPLv3+).
  * Modify package name (libgloox8 -> libgloox11) to reflect SONAME bump.

 -- Vincent Cheng <email address hidden> Thu, 16 Jan 2014 10:42:06 -0800

Tags: sync
tags: added: sync
Revision history for this message
Dmitry Shachnev (mitya57) wrote :

I will take care of the rebuilds.

Changed in gloox (Ubuntu):
status: New → Fix Committed
Revision history for this message
Dmitry Shachnev (mitya57) wrote :

Uploaded rebuilds.

Changed in 0ad (Ubuntu):
status: New → Fix Committed
Changed in fatrat (Ubuntu):
status: New → Fix Committed
Changed in licq (Ubuntu):
status: New → Fix Committed
Changed in uwsgi (Ubuntu):
status: New → Fix Committed
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package 0ad - 0.0.15-2build1

---------------
0ad (0.0.15-2build1) trusty; urgency=medium

  * No-change rebuild for gloox transition (LP: #1273967).
 -- Dmitry Shachnev <email address hidden> Wed, 29 Jan 2014 17:03:20 +0400

Changed in 0ad (Ubuntu):
status: Fix Committed → Fix Released
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package uwsgi - 1.9.17.1-5build2

---------------
uwsgi (1.9.17.1-5build2) trusty; urgency=medium

  * Rebuild again, the previous build was still linked against old gloox
    on some archs.
 -- Dmitry Shachnev <email address hidden> Fri, 31 Jan 2014 20:23:50 +0400

Changed in uwsgi (Ubuntu):
status: Fix Committed → Fix Released
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package fatrat - 1.2.0~beta2-0ubuntu8

---------------
fatrat (1.2.0~beta2-0ubuntu8) trusty; urgency=medium

  * No-change rebuild for gloox transition (LP: #1273967).
 -- Dmitry Shachnev <email address hidden> Wed, 29 Jan 2014 17:04:17 +0400

Changed in fatrat (Ubuntu):
status: Fix Committed → Fix Released
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package licq - 1.8.1-2build1

---------------
licq (1.8.1-2build1) trusty; urgency=medium

  * No-change rebuild for gloox transition (LP: #1273967).
 -- Dmitry Shachnev <email address hidden> Wed, 29 Jan 2014 22:49:06 +0400

Changed in licq (Ubuntu):
status: Fix Committed → Fix Released
Changed in gloox (Ubuntu):
status: Fix Committed → Fix Released
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.