Update from Gibbon to Heron failed

Thanks for taking the time to report this bug and helping to make Ubuntu better. Could you please add all the files contained in /var/log/dist-upgrade/ to your bug report as separate attachments? Thanks in advance.

Pedro,
Here are the files you requested
After looking into it more, it doesnt seem to be an upgrade issue. I can't
tell if its an Ubuntu issue or not, but hopefully these files will help.
It seems to be an axyl application install gone bad. I can't seem to get rid
of the upgrade file. I'm still learning linux.

I love Ubuntu!!!!!!!!!!!! Tell your co-workers, you guys do GREAT work! I
am glad that it continues to grow and become competitive with pay operating
systems. I am all about open source code and hope to do something one day to
benefit Ubuntu.

Dave

On Fri, Apr 25, 2008 at 3:07 PM, Pedro Villavicencio <email address hidden>
wrote:

> Thanks for taking the time to report this bug and helping to make Ubuntu
> better. Could you please add all the files contained in /var/log/dist-
> upgrade/ to your bug report as separate attachments? Thanks in advance.
>
> ** Changed in: update-manager (Ubuntu)
> Status: New => Incomplete
>
> --
> Update from Gibbon to Heron failed
> https://bugs.launchpad.net/bugs/222000
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in Source Package "update-manager" in Ubuntu: Incomplete
>
> Bug description:
> Binary package hint: update-manager
>
> Update from Gibbon to Heron failed
>
> ProblemType: Package
> Architecture: i386
> Date: Fri Apr 25 11:38:35 2008
> DistroRelease: Ubuntu 8.04
> ErrorMessage: ErrorMessage: SystemError in cache.commit(): E:Sub-process
> /usr/bin/dpkg returned an error code (1), E:Sub-process /usr/bin/dpkg
> returned an error code (1)
>
> Package: update-manager 1:0.87.24
> PackageArchitecture: all
> SourcePackage: update-manager
> Title: package update-manager 1:0.87.24 failed to install/upgrade:
> ErrorMessage: SystemError in cache.commit(): E:Sub-process /usr/bin/dpkg
> returned an error code (1), E:Sub-process /usr/bin/dpkg returned an error
> code (1)
> Uname: Linux 2.6.24-16-generic i686
>

--
David Rebar
<email address hidden>
http://personal.frostburg.edu/drebar0/

Thanks for your logs,

here is what caused the error:
2008-04-25 10:35:59,195 ERROR got an error from dpkg for pkg: '/var/cache/apt/archives/axyl-lucene_2.1.10_all.deb': 'subprocess new post-removal script returned error exit status 2

Unpacking replacement axyl-lucene ...
i386.deb) ...
/usr/share/axyl/install/axyl-common-funcs.sh: 185: Syntax error: "(" unexpected
dpkg: warning - old post-removal script returned error exit status 2
dpkg - trying script from the new package instead ...
dpkg: error processing /var/cache/apt/archives/axyl-lucene_2.1.10_all.deb (--unpack):
 subprocess new post-removal script returned error exit status 2
dpkg: error while cleaning up:
 subprocess post-removal script returned error exit status 2

I reassign. Milestoned and marked high priority as it breaks ugprades.

It looks like axyl itself is pretty broken too, when I try to install it I get:

Setting up axyl (2.1.14) ...
mkdir: created directory `/var/lib/axyl'
mkdir: created directory `/var/lib/axyl/system'
mkdir: created directory `/var/log/axyl'
Unix user account axyl successfully added (104).
adduser: To avoid problems, the username should consist only of
letters, digits, underscores, periods, at signs and dashes, and not start with
a dash (as defined by IEEE Std 1003.1-2001). For compatibility with Samba
machine accounts $ is also supported at the end of the username
dpkg: error processing axyl (--configure):
 subprocess post-installation script returned error exit status 1

Michael,
Thank you for confirming what caused the error. However, I am not so sure
that it caused Gutsy not to upgrade to Hardy Heron. I reported that bug as
the option popped up during the upgrade, so I took the oportunity. I had
problems with Axyl-Lucene generating that message before the upgrade because
I did not give it a data base to access during initial installation. Drupal
also generated a similar message for the same reason, but I managed to
uninstall it okay.

Once I rebooted, the update to Heron seems to be working fine. So the
Axyl-lucene problem was preexisitng before upgrading. So the report may have
been premature. I got my wife to help me remove all traces of Axyl and Axyl
Lucene. It did take quite a bit of doing and deleting. Luckily she has
administered unix systems in the past.

Once we removed all traces, we still couldnt completely uninstall the
package. Axyl-Lucene reported in the one log file that several versions were
half installed. 2.1.9 and 2.1.12 and
2.1.14 . We couldnt go forward and we could go back or remove it completely.
We ended up forcing Ubuntu to Use the upgrade anyway of Axyl Lucene
2.1.14.Once we did that, we were able to completely remove Axyl-Lucene
completely.
I would like to try it one day again, but not willing to try it again until
finals are over here in a few weeks.

If you need more details about what we did exactly, I can get her to reply
to this with more precise language. But its fixed and upgrade to Hardy Heron
seems to be running fine now .

Dave

On 4/28/08, Michael Vogt <email address hidden> wrote:
>
> Thanks for your logs,
>
> here is what caused the error:
> 2008-04-25 10:35:59,195 ERROR got an error from dpkg for pkg:
> '/var/cache/apt/archives/axyl-lucene_2.1.10_all.deb': 'subprocess new
> post-removal script returned error exit status 2
>
> Unpacking replacement axyl-lucene ...
> i386.deb) ...
> /usr/share/axyl/install/axyl-common-funcs.sh: 185: Syntax error: "("
> unexpected
> dpkg: warning - old post-removal script returned error exit status 2
> dpkg - trying script from the new package instead ...
> dpkg: error processing /var/cache/apt/archives/axyl-lucene_2.1.10_all.deb
> (--unpack):
> subprocess new post-removal script returned error exit status 2
> dpkg: error while cleaning up:
> subprocess post-removal script returned error exit status 2
>
> I reassign. Milestoned and marked high priority as it breaks ugprades.
>
> ** Changed in: axyl-lucene (Ubuntu)
> Sourcepackagename: update-manager => axyl-lucene
> Importance: Undecided => High
> Status: Incomplete => Confirmed
> Target: None => ubuntu-8.04.1
>
>
> --
> Update from Gibbon to Heron failed
> https://bugs.launchpad.net/bugs/222000
> You received this bug notification because you are a direct subscriber
> of the bug.
>
>
> Status in Source Package "axyl-lucene" in Ubuntu: Confirmed
>
>
> Bug description:
> Binary package hint: update-manager
>
> Update from Gibbon to Heron failed
>
> ProblemType: Package
> Architecture: i386
> Date: Fri Apr 25 11:38:35 2008
> DistroRelease: Ubuntu 8.04
> ErrorMessage: ErrorMessage: SystemError in cache.commit(): E:Sub-process
> /usr/bin/dpkg returned an error code (1...

Subscribing motu-release for getting an ack.

Accepted into hardy-proposed, please test.

I hope I am not impatient, but I believe this bug is not ready for verification yet.
Testing the upgrade from Gutsy to Hardy with axyl-lucene installed and hardy-proposed enabled still fails:

dpkg - trying script from the new package instead ...
/usr/share/axyl/install/axyl-common-funcs.sh: 185: Syntax error: "(" unexpected
dpkg: error processing /var/cache/apt/archives/axyl-lucene_2.1.10ubuntu1_all.deb (--unpack):
 subprocess new post-removal script returned error exit status 2

apt-cache policy only shows a proposed version for axyl-lucene, not for axyl.
Manually removing the function keywords from /usr/share/axyl/install/axyl-common-funcs.sh, like Michaels debdiff for axyl would do, fixes this problem and makes the upgrade complete successfully. So I think a new version of axyl per Michaels debdiff is needed to verify and fix this bug.

ACK, but this fix is not yet in intrepid.

This bug was fixed in the package axyl - 2.5.0ubuntu1

---------------
axyl (2.5.0ubuntu1) intrepid; urgency=low

  * install/axyl-common-funcs.sh:
    - Fix bashisms which caused errors in configure phase (LP: #222000).
   * debian/control:
     - Update Maintainer field as per spec.

 -- Luca Falavigna <email address hidden> Tue, 17 Jun 2008 13:20:26 +0200

This bug was fixed in the package axyl-lucene - 2.2.0ubuntu1

---------------
axyl-lucene (2.2.0ubuntu1) intrepid; urgency=low

  * install/install-lucene.sh:
    - Fix bashisms which caused errors in configure phase (LP: #222000).
  * debian/control:
    - Update Maintainer field as per spec.

 -- Luca Falavigna <email address hidden> Tue, 17 Jun 2008 13:16:53 +0200

I uploaded axyl 2.1.14ubuntu1 to hardy-proposed including mvo's changes toghether with a fix from version 2.4.0 to perform a clean install with new Apache envvars file. Albert, please retry it once it will be available for testing, thanks.

Accepted into hardy-proposed, please test.

+1

After reproducing the bug before (see comment 11) the upgrade from gutsy to hardy now went fine in a kvm VM with -proposed enabled.

HARDY VERIFICATION:

Using axyl 2.1.14 and axyl-lucene 2.1.10 from hardy-release:
Setting up axyl (2.1.14) ...
mkdir: created directory `/var/lib/axyl/system'
mkdir: created directory `/var/log/axyl'
Unix user account axyl successfully added (104).
adduser: To avoid problems, the username should consist only of
letters, digits, underscores, periods, at signs and dashes, and not start with
a dash (as defined by IEEE Std 1003.1-2001). For compatibility with Samba
machine accounts $ is also supported at the end of the username
dpkg: error processing axyl (--configure):
 subprocess post-installation script returned error exit status 1
dpkg: dependency problems prevent configuration of axyl-lucene:
 axyl-lucene depends on axyl (>= 2.1.14); however:
  Package axyl is not configured yet.
dpkg: error processing axyl-lucene (--configure):
 dependency problems - leaving unconfigured
Processing triggers for libc6 ...
ldconfig deferred processing now taking place
Errors were encountered while processing:
 axyl
 axyl-lucene
E: Sub-process /usr/bin/dpkg returned an error code (1)

Using axyl 2.1.14ubuntu1 and axyl-lucene 2.1.10ubuntu1 from hardy-proposed:
Packages install and configure correctly.

Archive-admins, please copy axyl and axyl-lucene packages to hardy-updates at the same time or configure errors will show up again because this fix needs both packages to be fully functional.

Both copied to hardy-updates.