Oh I am fine sticking on Gusty as it develops out. To be honest I am finding
Gusty more stable than most of my windows macxhines, even in Tribe 4 state!
Had a problem. Asked a question. Problem is solved, pushed toward next
release or makes me reconsider being on a developing OS. So far Really
oops. 0.59.4 :P
--
Package 0.59.2 broken
https://bugs.launchpad.net/bugs/132941
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubu
Confirmed. 0.54.4 fixes the problem.
Thanks :)
--
Package 0.59.2 broken
https://bugs.launchpad.net/bugs/132941
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists
Pretty new user to linux/ubuntu here. I too have received this error on
last update. How do I get around it? I tried to rename the `/usr/share
/update-notifier/notify-reboot-required'. No luck.
zeddock
--
Package 0.59.2 broken
https://bugs.launchpad.net/bugs/132941
You received this bug notifi
zeddock: When the updated package gets to the mirrors, you will probably
need to go to the command line (Terminal) and try "sudo apt-get update"
and then "sudo apt-get -f install". If the second command fails, the fix
hasn't yet made it to the mirrors. (As of right now, it hasn't. It
should be ther
The new 0.59.4 should fix the bug
** Changed in: update-notifier (Ubuntu)
Status: Confirmed => Fix Released
--
Package 0.59.2 broken
https://bugs.launchpad.net/bugs/132941
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
confirm that 0.59.3 doesn't also do it for me also.
Writing extended state information... Done
(Reading database ... 255717 files and directories currently installed.)
Unpacking update-notifier-common (from
.../update-notifier-common_0.59.3_all.deb) ...
dpkg: error processing
/var/cache/apt/arch
I just downloaded the deb source for update-notifier-0.59.3. Both
./debian/update-notifier.install and ./debian/update-notifier-
common.install still reference the file /usr/share/update-notifier
/notify-reboot-required
--
Package 0.59.2 broken
https://bugs.launchpad.net/bugs/132941
You received
** Changed in: update-notifier (Ubuntu)
Status: Fix Released => Confirmed
--
Package 0.59.2 broken
https://bugs.launchpad.net/bugs/132941
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bu
Unpacking update-notifier (from .../update-notifier_0.59.3_i386.deb) ...
dpkg: error processing /var/cache/apt/archives/update-notifier_0.59.3_i386.deb
(--unpack):
trying to overwrite `/usr/share/update-notifier/notify-reboot-required', which
is also in package update-notifier-common
Errors were
i confirm this too. ¿should update-notifier give an force-overwrite
option in cases like this? or is something that goes against the easy of
use and simplicity finality.
--
Package 0.59.2 broken
https://bugs.launchpad.net/bugs/132941
You received this bug notification because you are a member of
Thank you for your bug. The new 0.59.3 should fix the issue
** Changed in: update-notifier (Ubuntu)
Status: New => Fix Released
--
Package 0.59.2 broken
https://bugs.launchpad.net/bugs/132941
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug cont
12 matches
Mail list logo
