[Bug 664142] Re: Backport lyx 1.6.7-1 from maverick to lucid

Thanks for testing - ACK from backporters. ** Summary changed: - Backport lyx_1.6.7-1 to Lucid + Backport lyx 1.6.7-1 from maverick to lucid ** Changed in: lucid-backports Status: Confirmed => In Progress ** Changed in: lucid-backports Importance: Undecided => Wishlist -- You receiv

[Bug 691937] Re: Backport rakarrack from maverick to lucid

In the future, please don't use the "In progress" status on backports bugs - that status has a special meaning to the project, and it's likely to result in us ignoring the bug. Before we can proceed with the backport, we need some basic verification that the package can be expected to work once it

[Bug 652204] Re: [test-pkg-a] Backport Squid 3.1 to Lucid

Err, wait, I guess this backport request is about the squid3 package? That's not particularly clear from the current bug description. I'll clarify that. Anyway, here are the reverse-dependencies that need testing: mingo:~ evan$ chdist apt-cache lucid rdepends --no-suggests --no-conflicts --no-bre

[Bug 652204] Re: [test-pkg-a] Backport Squid 3.1 to Lucid

As Iain mentioned, squid has several reverse-dependencies: mingo:~ evan$ chdist apt-cache lucid rdepends --no-suggests --no-conflicts --no-breaks --no-replaces --no-enhances squid squid Reverse Depends: srg squidtaild |squidguard squid-prefetch squid-deb-proxy sqcwa |jesred gadmin-

[Bug 710296] Re: Please backport gnucash 1:2.4.0-4 from natty

It looks like natty released with gnucash version 1:2.4.2-1ubuntu1, not 1:2.4.0-4. I'm going to assume this is still acceptable, and update the bug appropriately. Before we can approve the backport, we need some basic verification that we can expect the backport to work. I've uploaded a test backp

[Bug 686766] Re: Please backport live-build 2.0.12-2 from natty to maverick

(Note to backporters: live-build's only r-dep is purely internal - the transitional package live-helper depends on live-build) -- You received this bug notification because you are a member of Ubuntu Backporters, which is subscribed to maverick-backports. https://bugs.launchpad.net/bugs/686766 T

[Bug 686766] Re: Please backport live-build

Hi Cody - It looks like natty released with live-build 2.0.12-2. Assuming that's still acceptable, I'll go ahead and update this bug appropriately. Can you please verify that a no-change backport of live-build builds, installs, and runs on maverick? If you need such a test backport, I've uploa

[Bug 721886] Re: Please backport tor-arm

Hi Damian, At this point, we can no longer backport to Karmic as it has been end- of-life'd, but we can still backport to Lucid and Maverick. A single bug is sufficient, but in the future you can open a separate "task" for each release to which you'd like to backport by using the "Also affects pro

[Bug 684842] Re: Please backport git 1.7.3.2 to Maverick

Ubuntu backports will only backport packages that are currently in the Ubuntu archive, not arbitrary releases from upstream. Looking at , it seems that Natty released with git 1.7.4.1. Would backporting that to maverick be satisfactory? ** Changed in: mave

[Bug 783006] Re: Please backport focuswriter 1.3.2.git.69e4975b-1 from oneiric to lucid, maverick, natty

Great, thanks for the verification. ACK from backporters for maverick. I've uploaded a revision of the Lucid backport that drops from requiring debhelper 8 to only requiring debhelper 7 (which Lucid already has). Please test once it's built. ** Changed in: maverick-backports Status: Confir

[Bug 755169] Re: backport drush into lucid LTS (or maverick?) once in natty

Before we can process this backport, there's some verification work that needs to be done. First, in order to ensure that there's a valid upgrade path away from Lucid, drush will definitely also need to be backported to Maverick. Second, the backports process requires some basic verification that

[Bug 771693] Re: Please backport unscd 0.47-2 from natty to lucid, maverick

(Marking as Incomplete to indicate that this is pending testing) ** Changed in: lucid-backports Status: New => Incomplete ** Changed in: maverick-backports Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Backporters, which is subs

[Bug 783006] Re: Please backport focuswriter 1.3.2.git.69e4975b-1 from oneiric to lucid, maverick, natty

focuswriter 1.3.2.git.69e4975b-1~maverick1~ppa1 from the PPA installed and ran without problems on a Maverick i386 system, though every time it launches it prints the following to stderr: Bus::open: Can not get ibus-daemon's address. IBusInputContext::createInputContext: no connection to ibus-dae

[Bug 719940] Re: Please backport memcached-1.4.5

I have a customer using Joomla who is having the same issue, we're using Ubuntu 10.04.2 LTS -- a backported 1.4.5 for lucid would be very much appreciated. here's the joomla forum that lead me to identify the problem: http://forum.joomla.org/viewtopic.php?p=2049813 post #11 which lead to: http:/

[Bug 783006] Please backport focuswriter 1.3.2.git.69e4975b-1 from oneiric to lucid, maverick, natty

I: Extracting focuswriter_1.3.2.git.69e4975b-1.dsc ... done. I: Building backport of focuswriter as 1.3.2.git.69e4975b-1~natty1 ... done. ** Changed in: natty-backports Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Backport

[Bug 786483] Please backport lintian 2.5.0ubuntu1

I: Extracting lintian_2.5.0ubuntu1.dsc ... done. I: Building backport of lintian as 2.5.0ubuntu1~natty1 ... done. ** Changed in: natty-backports Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Backporters, which is the regist

[Bug 775208] Please Backport unison 2.32.52-1ubuntu2 from maverick to lucid

I: Extracting unison_2.32.52-1ubuntu2.dsc ... done. I: Building backport of unison as 2.32.52-1ubuntu2~lucid1 ... done. ** Changed in: lucid-backports Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Backporters, which is subs

[Bug 778869] Re: [natty] fontconfig-voodoo -a does not work in Japanese locales

Sponsored and accepted into l/m-backports, thanks Gunnar! ** Changed in: lucid-backports Status: In Progress => Fix Released ** Changed in: maverick-backports Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Backporters,

[Bug 771661] Re: Allow .xsession-errors to be a symlink

Reopening to catch the "symlink to character device" case as well. ** Changed in: gdm (Ubuntu) Status: Fix Released => In Progress -- You received this bug notification because you are a member of Ubuntu Backporters, which is subscribed to lucid-backports. https://bugs.launchpad.net/bugs/

[Bug 771661] Re: Allow .xsession-errors to be a symlink

Alex, this would happen if ~/.xsession-errors is not a regular file, i. e. symlink to a nonexisting file, or a pipe or something. So in your case /dev/null is not S_ISREG, so it would fall back to creating a new file. -- You received this bug notification because you are a member of Ubuntu Backp