This strikes me as a bug in the package, not a Puppet bug. Shouldn't
this be filed with the package maintainer?

On Fri, Jun 13, 2008 at 7:16 AM,  <[EMAIL PROTECTED]> wrote:
> Issue #1206 has been updated by RNHurt.
>
> OK, this is marked "Needs more info" but I think I already provided the
> requested data. If there is something else that is needed please let me know
> and I'll do what I can.
>
> NOTE: The original BoxBackup package that was having a problem has been
> updated and the new one works properly. I think I can still reproduce the
> but though using my own repository.
>
> ________________________________
>
> Bug #1206: aptitude provider does not recognize recovery efforts
>
> Author: RNHurt
> Status: Needs more information
> Priority: Normal
> Assigned to: community
> Category: Debian
> Target version:
> Keywords:
> Complexity: Unknown
> Patch: None
> Affected version:
>
> The boxbackup 0.10 package from Debian backports is failing to install via
> Puppet 0.2.24. It looks as though there is an error in the package and the
> initial configuration fails. However, aptitude (and I assume apt-get) by
> default tries to recover from the error and in this case succeeds.
> Subsequent aptitude purge & installs work just fine and only the initial
> install causes this error.
>
> The problem is that Puppet flags this install as a complete loss for some
> reason and keeps trying to install the package. I took the command out of
> the Puppet log file and ran it manually and captured the output as seen
> below. After I ran this install Puppet accepted the install and everything
> looks OK. The only problem is the initial install. Is there an option to the
> apt(itude) providers to allow them to perform the recovery or should I use a
> force
>
> 2D0987B9:~# /usr/bin/aptitude -y -o DPkg::Options::=--force-confold install
> boxbackup-client=0.10-1~bpo.1
> Reading package lists... Done
> Building dependency tree... Done
> Reading extended state information
> Initializing package states... Done
> Writing extended state information... Done
> Reading task descriptions... Done
> Building tag database... Done
> No packages will be installed, upgraded, or removed.
> 0 packages upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
> Need to get 0B of archives. After unpacking 0B will be used.
> Writing extended state information... Done
> Setting up boxbackup-client (0.10-1~bpo.1) ...
>
> Creating config file /etc/boxbackup/bbackupd.conf with new version
>
> Creating config file /etc/boxbackup/bbackupd/notifyadmin with new version
> /etc/init.d/boxbackup-client: line 27: [: too many arguments
> /etc/init.d/boxbackup-client: line 30: [: too many arguments
> Starting boxbackup-client: Box Backup Client v0.10, (c) Ben Summers and
> contributors 2003-2006
> bbackupd: failed to start: failed to open configuration file:
> /var/run/bbackupd.pidinvoke-rc.d: initscript boxbackup-client, action
> "start" failed.
> dpkg: error processing boxbackup-client (--configure):
>  subprocess post-installation script returned error exit status 1
> Errors were encountered while processing:
>  boxbackup-client
> E: Sub-process /usr/bin/dpkg returned an error code (1)
> A package failed to install.  Trying to recover:
> Setting up boxbackup-client (0.10-1~bpo.1) ...
> Replacing config file /etc/boxbackup/bbackupd.conf with new version
> Replacing config file /etc/boxbackup/bbackupd/notifyadmin with new version
>
> 2D0987B9:~#
>
> ________________________________
>
> You have received this notification because you have either subscribed to
> it, or are involved in it.
> To change your notification preferences, please click here:
> http://reductivelabs.com/redmine/my/account
>
> >
>

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Puppet Bugs" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/puppet-bugs?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to