removing deb leaves symlink which causes apache to fail starting

Bug #84487 reported by KarlGoetz
6
Affects Status Importance Assigned to Milestone
backuppc (Ubuntu)
Undecided
Unassigned

Bug Description

Binary package hint: backuppc

on an Ubuntu 6.06.1 LTS system:
when backuppc is removed, it leaves a file in /etc/apache2/config.d which is a symlink called 'backuppc'. because backuppc is removed, the symlink breaks and apache is unable to find backuppc. this causes apache to fail to start. removing the link allows apache to start again.

Related branches

Revision history for this message
Aaron C. de Bruyn (darkpixel2k) wrote :

I also run into the same issue with package version 3.0.0-3ubuntu1~feisty1 in the backports repo.
When removed (and purged) it leaves a /etc/apache2/config.d/backuppc symlink sitting there which causes apache to fail.

Running Ubuntu 7.04 AMD64 2.6.20-16-generic #2 SMP Thu Jun 7 19:00:28 UTC 2007 x86_64 GNU/Linux

Revision history for this message
KarlGoetz (kgoetz) wrote :
Revision history for this message
KarlGoetz (kgoetz) wrote :

the 2nd poster seems to confirm this in a 2nd release

Changed in backuppc:
status: New → Confirmed
Revision history for this message
KarlGoetz (kgoetz) wrote :
Revision history for this message
Luca Falavigna (dktrkranz) wrote :

I can confirm it on an up-to-date Gutsy box. Karl's patch fixes this bug.

A little note for your reference: when specifying a Launchpad bug number, use the notation (LP: #84487), this way the bug report will be closed automagically when your fix will be uploaded.

You can subscribe this bug to ubuntu-universe-sponsors to make them aware of your effort. Thank you.

Revision history for this message
KarlGoetz (kgoetz) wrote : Re: [Bug 84487] Re: removing deb leaves symlink which causes apache to fail starting

Luca Falavigna wrote:
> I can confirm it on an up-to-date Gutsy box. Karl's patch fixes this
> bug.
>
> A little note for your reference: when specifying a Launchpad bug
> number, use the notation (LP: #84487), this way the bug report will be
> closed automagically when your fix will be uploaded.

thank you for looking into it.
When i get home i'll redo the debdiff incase it still needs it.

>
> You can subscribe this bug to ubuntu-universe-sponsors to make them

i'll do so when i get home

> aware of your effort. Thank you.
>

thanks

Revision history for this message
KarlGoetz (kgoetz) wrote :

Luca - i attempted to match the notation you meantion in your comment. Apart from that it is exactly the same patch.

Revision history for this message
Lionel Porcheron (lionel.porcheron) wrote :

Thanks for you work on this bug.

backuppc is in main, I'm unsubscribing Ubuntu Sponsors for universe and subscribing Ubuntu Sponsors for main.

Revision history for this message
KarlGoetz (kgoetz) wrote :

backuppc (3.0.0-3ubuntu2) gutsy; urgency=low

  * Add .conf to the symlink removal code in prerm. (LP: #84487)

 -- Karl Goetz <email address hidden> Mon, 27 Aug 2007 21:49:15 +0930

Changed in backuppc:
status: Confirmed → Fix Released
Revision history for this message
Reinhard Tartler (siretart) wrote :

backuppc (3.0.0-4ubuntu1) hardy; urgency=low

  * Merge from Debian unstable
  * Remaining Ubuntu changes:
    - Use LSB functions in the init script, and make /var/run/backuppc if
      needed.
    - Remove dependancy on wwwconfig-common.
    - We like apache 2 more, so move it first to the alternatives list.
    - Bump libfile-rsyncp-perl and rsync from Suggests to Depends.
    - Remove stop script symlinks from rc0 and rc6.
    - Don't chown /var/run/backuppc in the postinst.
    - Don't move /var/lib/backuppc/conf/* (and then delete) to /etc/backuppc
      in rules, upstream is shipping the config files in /etc/backuppc
      themselves.
    - Unfuzzify debian/config.pl.diff.
    - Munge Maintainer field as per spec.
    - Add .conf to the symlink removal code in prerm. (LP: #84487)

 -- Reinhard Tartler <email address hidden> Wed, 24 Oct 2007 15:55:31 +0200

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers