package bld 0.3.4.1-3 failed to install/upgrade:

Bug #483220 reported by tommaso
78
This bug affects 9 people
Affects Status Importance Assigned to Milestone
bld (Debian)
Fix Released
Unknown
bld (Ubuntu)
Fix Released
Wishlist
Unassigned
Karmic
Fix Released
Low
Unassigned

Bug Description

Binary package hint: bld

I cannot know if it's really different, my localizatiion is: ITALIAN;
the new I can add is I don't chose this, but it was among dependencies of somenthing I can't recall what among others,
and the crucial point of the error is --CONFIGURE passage, just as synaptic error message, it doesn't succeed installing,
as for an incompatableness with something else,
too vague, I'll try to gain some more information if it doesn't collapse.

ProblemType: Package
Architecture: i386
Date: Sun Nov 15 19:52:15 2009
DistroRelease: Ubuntu 9.10
ErrorMessage:
 ErrorMessage: subprocess installed post-installation script returned error exit status 1
Package: bld 0.3.4.1-3
ProcVersionSignature: Ubuntu 2.6.31-15.50-generic
SourcePackage: bld
Title: package bld 0.3.4.1-3 failed to install/upgrade:
Uname: Linux 2.6.31-15-generic i686

DESCRIPTION:
bld 0.3.4.1-3 fails to install on ubuntu karmic with error
chown: cannot access `/var/run/bld': No such file or directory
when running the post install script

TEST CASE:
run $apt-get install bld
resulting in error
Setting up bld (0.3.4.1-3) ...
chown: cannot access `/var/run/bld': No such file or directory
dpkg: error processing bld (--configure):
 subprocess installed post-installation script returned error exit status 1

FIX:
Applied in Debian version 0.3.4.1-4
move ownership change from post install script to the init script where /var/run/bld directory creation was moved to in 0.3.4.1-2

REGRESSION:
The package is currently unusable and the patch affects only files specific to this package, regression potential should be minimal

Revision history for this message
tommaso (mb3-tim) wrote :
Revision history for this message
Jean-Baptiste Lallement (jibel) wrote :

Thanks for taking the time to report this bug and helping to make Ubuntu better. The files attached seem corrupted. Could you please add the log files from '/var/log/dist-upgrade/' to this bug report as separate attachments? Thanks in advance.

Changed in bld (Ubuntu):
status: New → Incomplete
Revision history for this message
tommaso (mb3-tim) wrote :

Hope these attachment can be seen, if not you can ask me more specifically.
Tommaso
/var/log/dist-upgrade/20091105-2235
/var/log/dist-upgrade/20091114-1937
/var/log/dist-upgrade/20091114-1958
/var/log/dist-upgrade/20091115-1951
/var/log/dist-upgrade/apt.log
/var/log/dist-upgrade/apt-term.log
/var/log/dist-upgrade/main.log.partial

Revision history for this message
tommaso (mb3-tim) wrote :

1)

Revision history for this message
tommaso (mb3-tim) wrote :

2)/var/log/dist-upgrade/apt-term.log pasted content
Log started: 2009-11-15 19:52:13
Setting up bld (0.3.4.1-3) ...

chown: cannot access `/var/run/bld': No such file or directory

dpkg: error processing bld (--configure):

 subprocess installed post-installation script returned error exit status 1

Errors were encountered while processing:

 bld

Log ended: 2009-11-15 19:52:17

Revision history for this message
tommaso (mb3-tim) wrote :

3)

Revision history for this message
tommaso (mb3-tim) wrote :

4) from folder /20091115-1951

Revision history for this message
tommaso (mb3-tim) wrote :

5) from folder /20091115-1951/apt-term.log pasted content
Log started: 2009-11-14 19:59:27
Log ended: 2009-11-14 19:59:27

From here backward it seems normal but if needed I can attach the older folders
Bye for now

Revision history for this message
tommaso (mb3-tim) wrote :

Must I add something?
Tommaso

Revision history for this message
Niall Creech (sevenmachines-deactivatedaccount) wrote :

creation of /var/run/bld is now handled in the init script, so this can be removed from bld.postinst.

bld (0.3.4.1-3ubuntu1) lucid; urgency=low

  * debian/bld.postinst: drop creation and ownership changes of /var/run/bld,
    this is now handled by init script

https://launchpad.net/~sevenmachines/+archive/ppa/+packages

Changed in bld (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
tommaso (mb3-tim) wrote : Re: [Bug 483220] Re: package bld 0.3.4.1-3 failed to install/upgrade:

in my /var/run there is no bld file or folder, tell me if I must control
somewhere else.
Il giorno mar, 17/11/2009 alle 00.12 +0000, SevenMachines ha scritto:
> creation of /var/run/bld is now handled in the init script, so this can
> be removed from bld.postinst.
>
> bld (0.3.4.1-3ubuntu1) lucid; urgency=low
>
> * debian/bld.postinst: drop creation and ownership changes of /var/run/bld,
> this is now handled by init script
>
> https://launchpad.net/~sevenmachines/+archive/ppa/+packages
>
> ** Attachment added: "bld_0.3.4.1-3ubuntu1.debdiff"
> http://launchpadlibrarian.net/35764451/bld_0.3.4.1-3ubuntu1.debdiff
>
> ** Changed in: bld (Ubuntu)
> Status: Incomplete => Confirmed
>

Revision history for this message
Niall Creech (sevenmachines-deactivatedaccount) wrote :

Last patch wasnt completely useful, i'll take another look at it

Revision history for this message
Niall Creech (sevenmachines-deactivatedaccount) wrote :

hopefully better

bld (0.3.4.1-3ubuntu1) lucid; urgency=low

  * debian/bld.postinst: drop creation and ownership changes of /var/run/bld,
    this is now handled by init script
  * debian/bld.init: add ownership change of /var/run/bld

https://launchpad.net/~sevenmachines/+archive/ppa/+packages

Revision history for this message
Fabrice Coutadeur (fabricesp) wrote :

Hi,

And thanks to work on this, SevenMachines.

I'm not sure the change you propose in th e init file is equivalent to the one in the postinst:
- the line in .postint says: chown -R $user:$user /var/run/$user
- but you replace it by: chown $USER:$USER /var/run/bld

Can you please report this to Debian, and see what the Debian maintainer has to say about this install problem?

Thanks,
Fabrice

Revision history for this message
tommaso (mb3-tim) wrote :

I insalled bld with those other apps:

I seguenti pacchetti sono stati rimossi:
stardict-gnome

I seguenti pacchetti sono stati installati:
aspell-eo (2.1.2000.02.25-40)
bld (0.3.4.1-3)
bld-postfix (0.3.4.1-3)
bld-tools (0.3.4.1-3)
brazilian-conjugate (3.0~beta4-12)
context (2008.05.21-1)
context-doc-nonfree (2007.01.02-1)
context-nonfree (2007.03.22-1)
dacco-cat-users (0.9+20071227-4)
dacco-common (0.9+20071227-4)
dacco-eng-users (0.9+20071227-4)
debian-edu-doc-en (1.3~20090610~5.0.1+edu0~alpha)
debian-edu-doc-it (1.3~20090610~5.0.1+edu0~alpha)
debian-history (2.10)
debian-policy (3.8.3.0)
dict-freedict-eng-tur (1.3-4ubuntu1)
dict-freedict-tur-eng (1.3-4ubuntu1)
doc-linux-it (2003.12-1.1)
epwutil (1.1-8ubuntu1)
feynmf (1.08-5)
freespeak (0.3.0-3)
furiusisomount (0.11.1.1-0ubuntu2)
fuseiso (20070708-1)
fuseiso9660 (0.2b-1)
ibrazilian (3.0~beta4-12)
iesperanto (2.1.2000.02.25-40)
iitalian (1:2.3-2)
installation-report-generator (0.2.3-0ubuntu1)
libeb13 (4.4.1-1)
libgda-4.0-4 (4.0.4-1ubuntu3)
libgda-4.0-common (4.0.4-1ubuntu3)
libgdl-1-3 (2.28.0-1)
libgdl-1-common (2.28.0-1)
libqdaccolib0.7 (0.8-3)
libumlib0 (0.6-1)
luatex (0.40.5-1ubuntu2)
maint-guide-it (1.2.14)
murrine-themes (0.90.2)
python-eggtrayicon (2.25.3-3ubuntu1)
python-gda (2.25.3-3ubuntu1)
python-gdl (2.25.3-3ubuntu1)
python-gksu2 (2.25.3-3ubuntu1)
python-gnome2-extras (2.25.3-3ubuntu1)
python-gtkmozembed (2.25.3-3ubuntu1)
python-gtkmvc (1.2.2-1)
python-gtkspell (2.25.3-3ubuntu1)
python-xlib (0.14-2)
qdacco (0.8-3)
stardict-gtk (3.0.1-5)
tesseract-ocr-ita (2.00-1)
texlive-doc-it (2007.dfsg.2-2)
texlive-lang-italian (2007.dfsg.4-2)
texlive-metapost (2007.dfsg.2-7ubuntu1)
texlive-metapost-doc (2007.dfsg.2-7ubuntu1)
ttf-gfs-bodoni-classic (1.0-1)
ttf-gfs-solomos (1.000-1)
vera (1.17-5)

I don't remember of which is a dependency.
Now bld-postfix and bld-tool can be uninstalled, but not bld itself,
it doesn't seem to affect other uninstallment,
but adds its error to any installment, also if it succeeds normally,
but since its presence no update has been noticed from the manager,
if so, this last seems a relevant unwanted effect.

Thanks
Tommaso

Revision history for this message
tommaso (mb3-tim) wrote :

I looked the files:

I'm on an eeepc900,
with an huawei pendrive modem,
maybe its hard for it to search a port on an usb modem?
and seem a reinstall is
needed after changes of some of it's .conf files
anyway I changed nothing, it complainted since install.

Revision history for this message
Niall Creech (sevenmachines-deactivatedaccount) wrote :

hi fabrice, i mentioned this to the debian maintainer and he's made the changes in the attached diff (same as before but chown -R) to bld 0.3.4.1-4 in debian universe.

 bld (0.3.4.1-4) unstable; urgency=low
 .
   [ SevenMachines ]
   * debian/bld.postinst: drop creation and ownership changes of /var/run/bld,
     this is now handled by init script (Closes: #557084)
   * debian/bld.init: add ownership change of /var/run/bld
 .
   [ Martin Meredith ]
   * Sponsored Upload for SevenMachines <email address hidden>
   * Bumped Standards Version
   * Added README.source (from /usr/share/doc/dpatch/README.source.gz)

Changed in bld (Ubuntu):
status: Confirmed → New
Revision history for this message
Fabrice Coutadeur (fabricesp) wrote :

Great! Thats good news :-)

Thanks for taking care of that! This way, we will be able to sync this package for Lucid.

To get it fixed in Karmic, would you mind following the SRU process described at https://wiki.ubuntu.com/StableReleaseUpdates ?
Your debdiff seems good: for a SRU, you only have to change the version to ubuntu0.1, and change lucid by karmic-proposed.

If you prefer, I can do it for you.

Good job,
Fabrice

Changed in bld (Ubuntu):
importance: Undecided → Wishlist
Revision history for this message
Niall Creech (sevenmachines-deactivatedaccount) wrote :

DESCRIPTION:
bld 0.3.4.1-3 fails to install on ubuntu karmic with error
chown: cannot access `/var/run/bld': No such file or directory
when running the post install script

TEST CASE:
run $apt-get install bld
resulting in error
Setting up bld (0.3.4.1-3) ...
chown: cannot access `/var/run/bld': No such file or directory
dpkg: error processing bld (--configure):
 subprocess installed post-installation script returned error exit status 1

FIX:
Applied in Debian version 0.3.4.1-4
move ownership change from post install script to the init script where /var/run/bld directory creation was moved to in 0.3.4.1-2

REGRESSION:
The package is currently unusable and the patch affects only files specific to this package, regression potential should be minimal

https://launchpad.net/~sevenmachines/+archive/release/+packages

Revision history for this message
Niall Creech (sevenmachines-deactivatedaccount) wrote :

changelog: karmic->karmic-proposed

Changed in bld (Debian):
status: Unknown → Fix Released
Revision history for this message
Fabrice Coutadeur (fabricesp) wrote :

Uploaded to -proposed. Waiting for approval

description: updated
Changed in bld (Ubuntu Karmic):
importance: Undecided → Low
Revision history for this message
Martin Pitt (pitti) wrote : Please test proposed package

Accepted bld into karmic-proposed, the package will build now and be available in a few hours. Please test and give feedback here. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you in advance!

Changed in bld (Ubuntu Karmic):
status: New → Fix Committed
tags: added: verification-needed
Revision history for this message
Linuxexperte (andrea-koeth) wrote : Re: [Bug 483220] Re: package bld 0.3.4.1-3 failed to install/upgrade:

Hi Fabrice,
I just got your message referring to the problem with the package bld in
Karmic.
Now my question is, will there also be this package as amd64-version,
because my system is amd64 Karmic Koala.

Then I want to add, that my localization is: German.

I hope, I could give you some more information for the build.

As stated in my original error-message, this error-message came from
synaptic.

I will tet the new build when it is available and give you feedback as
wished from you.

Thank you for working on this problem and that Ubuntu Karmic Koala is
serviced so good. I love Karmic.

Greetings
Linuxexperte

Am 23.11.2009, 06:16 Uhr, schrieb Fabrice Coutadeur <email address hidden>:

> Uploaded to -proposed. Waiting for approval
>
> ** Description changed:
>
> Binary package hint: bld
> I cannot know if it's really different, my localizatiion is: ITALIAN;
> the new I can add is I don't chose this, but it was among dependencies
> of somenthing I can't recall what among others,
> and the crucial point of the error is --CONFIGURE passage, just as
> synaptic error message, it doesn't succeed installing,
> as for an incompatableness with something else,
> too vague, I'll try to gain some more information if it doesn't
> collapse.
> ProblemType: Package
> Architecture: i386
> Date: Sun Nov 15 19:52:15 2009
> DistroRelease: Ubuntu 9.10
> ErrorMessage:
> - ErrorMessage: subprocess installed post-installation script returned
> error exit status 1
> + ErrorMessage: subprocess installed post-installation script returned
> error exit status 1
> Package: bld 0.3.4.1-3
> ProcVersionSignature: Ubuntu 2.6.31-15.50-generic
> SourcePackage: bld
> Title: package bld 0.3.4.1-3 failed to install/upgrade:
> Uname: Linux 2.6.31-15-generic i686
> +
> + DESCRIPTION:
> + bld 0.3.4.1-3 fails to install on ubuntu karmic with error
> + chown: cannot access `/var/run/bld': No such file or directory
> + when running the post install script
> +
> + TEST CASE:
> + run $apt-get install bld
> + resulting in error
> + Setting up bld (0.3.4.1-3) ...
> + chown: cannot access `/var/run/bld': No such file or directory
> + dpkg: error processing bld (--configure):
> + subprocess installed post-installation script returned error exit
> status 1
> +
> + FIX:
> + Applied in Debian version 0.3.4.1-4
> + move ownership change from post install script to the init script
> where /var/run/bld directory creation was moved to in 0.3.4.1-2
> +
> + REGRESSION:
> + The package is currently unusable and the patch affects only files
> specific to this package, regression potential should be minimal
>
> ** Also affects: bld (Ubuntu Karmic)
> Importance: Undecided
> Status: New
>
> ** Changed in: bld (Ubuntu Karmic)
> Importance: Undecided => Low
>

--
Erstellt mit Operas revolutionärem E-Mail-Modul: http://www.opera.com/mail/

Revision history for this message
Niall Creech (sevenmachines-deactivatedaccount) wrote :

Note, to uninstall/upgrade the broken 0.3.4.1-3 package, you first need to need to
$ sudo mkdir /var/run/bld
$ /etc/init.d/bld start

as far as i know theres nothing the new package can do to 'unbreak' the bld 0.3.4.1-3 removal scripts

Revision history for this message
Linuxexperte (andrea-koeth) wrote :

Hey SevenMachines,

I have just lloked up in my Synaptic, that - since I have installed Karmic
Koala - this broken package is not installed by my for paying
attention to the stability of my system and for not running into the same
problems with this package anymore.

I will wait, until the new package will be published by the developer. He
informed me, the in a few hours there will be a new package out and that
the build is just running at the time. Let's see, how the situation will
be then.

Greetings
Linuxexperte

Am 23.11.2009, 12:51 Uhr, schrieb SevenMachines
<email address hidden>:

> Note, to uninstall/upgrade the broken 0.3.4.1-3 package, you first need
> to need to
> $ sudo mkdir /var/run/bld
> $ /etc/init.d/bld start
>
> as far as i know theres nothing the new package can do to 'unbreak' the
> bld 0.3.4.1-3 removal scripts
>

--
Erstellt mit Operas revolutionärem E-Mail-Modul: http://www.opera.com/mail/

Revision history for this message
tommaso (mb3-tim) wrote :

$ /etc/init.d/bld start
Starting Black List Daemon: start-stop-daemon: Unable to set gid to 131 (Operation not permitted)

Revision history for this message
tommaso (mb3-tim) wrote :

I must add that apart the error from console in my #26 post, the result is that it does no more give the error 1 while installing, deinstalling or updating other packages, while it continues to give it for itself if one tries to deinstall or reinstall it, and this operation has no effect, so maybe one has to change some more root/user permits also to update/upgrade it.

Revision history for this message
Jean-Baptiste Lallement (jibel) wrote :

0.3.4.1-4 is in Lucid, seting status to "Fix Released"

Changed in bld (Ubuntu):
status: New → Fix Released
Revision history for this message
Steve Beattie (sbeattie) wrote :

I've reproduced the problem installing bld 0.3.4.1-3 and can confirm that the version of bld in karmic-proposed, 0.3.4.1-3ubuntu0.1, successfully installs and appears to run. Given that, I'm willing consider this bug verification-done.

That said, SevenMachines, it is possible for an upgrading package to compensate for errors in a currently installed package; as part of the upgrade process, if the pre-removal script fails in the package being upgraded from, dpkg will re-attempt to run that step with pre-removal script from the version being upgraded to, like so:

    Preparing to replace bld 0.3.4.1-3 (using .../bld_0.3.4.1-3ubuntu0.1_amd64.deb) ...
    Stopping Black List Daemon: invoke-rc.d: initscript bld, action "stop" failed.
    dpkg: warning: old pre-removal script returned error exit status 1
=> dpkg - trying script from the new package instead ...
    Stopping Black List Daemon: invoke-rc.d: initscript bld, action "stop" failed.
    dpkg: error processing /var/cache/apt/archives/bld_0.3.4.1-3ubuntu0.1_amd64.deb (--unpack):

For SRUs, having the upgrading package correct for errors in the past gives a far better user experience than requiring them to track a bug report to find what manual steps need to be taken to correct their broken installation.

Thanks.

tags: added: verification-done
removed: verification-needed
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package bld - 0.3.4.1-3ubuntu0.1

---------------
bld (0.3.4.1-3ubuntu0.1) karmic-proposed; urgency=low

  * debian/bld.postinst: drop creation and ownership changes of /var/run/bld,
    this is now handled by init script. Fixed in debian 0.3.4.1-4
  * debian/bld.init: add ownership change of /var/run/bld. Fixed in debian
    0.3.4.1-4. (LP: #483220)
 -- SevenMachines <email address hidden> Fri, 20 Nov 2009 16:18:19 +0000

Changed in bld (Ubuntu Karmic):
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.