My guess is that it happened in the past when the package switched from
directory to that symlink (between dapper and hardy somewhen) that it
didn't get handled properly (A directory will never be replaced by a
symbolic link to a directory or vice versa (Debian policy ยง6.6.4)). But
as this didn't
I upoaded a simple fix for this now. I'm not sure how the system got
into the situation that resulted in a dir instead of a symlink though.
But even then, it should not fail.
** Changed in: pango1.0 (Ubuntu Natty)
Status: Triaged = Fix Committed
--
You received this bug notification
thanks mvo!
** Changed in: pango1.0 (Ubuntu Natty)
Assignee: Sebastien Bacher (seb128) = Michael Vogt (mvo)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to pango1.0 in Ubuntu.
https://bugs.launchpad.net/bugs/703230
Title:
rm:
This bug was fixed in the package pango1.0 - 1.28.3-4ubuntu3
---
pango1.0 (1.28.3-4ubuntu3) natty; urgency=low
* debian/libpango1.0-0.preinst:
- check for symlink target before calling rm (LP: #703230)
This fixes a upgrade bug, thanks to Alexander Kurtz for
this
Reproduced during an upgrade from maverick.
** Also affects: pango1.0 (Ubuntu Natty)
Importance: Medium
Status: Triaged
** Changed in: pango1.0 (Ubuntu Natty)
Assignee: (unassigned) = Canonical Desktop Team (canonical-desktop-team)
--
You received this bug notification because
increasing importance to high because it completely breaks the upgrade,
leaving the system in a non working state (and recovering manually is
non trivial)
** Changed in: pango1.0 (Ubuntu Natty)
Importance: Medium = High
** Changed in: pango1.0 (Ubuntu Natty)
Assignee: Canonical Desktop
** Changed in: pango1.0 (Ubuntu Natty)
Assignee: (unassigned) = Sebastien Bacher (seb128)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to pango1.0 in ubuntu.
https://bugs.launchpad.net/bugs/703230
Title:
rm: cannot remove
Debian has http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=616577 about
that issue, I've added a comment there
** Bug watch added: Debian Bug tracker #616577
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=616577
** Also affects: pango1.0 (Debian) via
** Changed in: pango1.0 (Debian)
Status: Unknown = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to pango1.0 in ubuntu.
https://bugs.launchpad.net/bugs/703230
Title:
rm: cannot remove
** Changed in: pango1.0 (Ubuntu)
Status: New = Triaged
** Changed in: pango1.0 (Ubuntu)
Importance: Undecided = Medium
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to pango1.0 in ubuntu.
In my case the directory was empty, and rmdir instead of rm -f would
have fixed it.
It is more likely that rm -rf was meant to be used here.
I will investigate if I can find a reference to some bug about this and
provide a proper fix for this here.
** Changed in: pango1.0 (Ubuntu)
@pochu: you appear to have added this for 1.28.3-4 in Debian experimental.
Please look into fixing this, possibly by using rmdir, if you're expecting it
to be an empty directory - but then with || true maybe so that it does not
break installation in case if the directory is non-empty because of
12 matches
Mail list logo
