Package 0.59.2 broken

[Laurent Bigonville]

Binary package hint: update-notifier

Last version of the package is broken on upgrade

Unpacking update-notifier-common (from .../update-notifier-common_0.59.2_all.deb) ...
dpkg: error processing /var/cache/apt/archives/update-notifier-common_0.59.2_all.deb (--unpack):
 trying to overwrite `/usr/share/update-notifier/notify-reboot-required', which is also in package update-notifier
Errors were encountered while processing:
 /var/cache/apt/archives/update-notifier-common_0.59.2_all.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)

[Sebastien Bacher (seb128)]

Thank you for your bug. The new 0.59.3 should fix the issue

[Basilio Kublik (sourcercito)]

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.

[C. Cooke (ccooke)]

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 encountered while processing:
 /var/cache/apt/archives/update-notifier_0.59.3_i386.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)

... Looks like 0.59.3 doesn't fix it.

[Adam McDaniel (adamrmcd)]

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

[Shirish Agarwal (shirishag75)]

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/archives/update-notifier-common_0.59.3_all.deb (--unpack):
 trying to overwrite `/usr/share/update-notifier/notify-reboot-required', which is also in package update-notifier
Preparing to replace mount 2.13~rc3-2ubuntu2 (using .../mount_2.13~rc3-5_i386.deb) ...
Unpacking replacement mount ...
Errors were encountered while processing:
 /var/cache/apt/archives/update-notifier-common_0.59.3_all.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)
A package failed to install. Trying to recover:

[Sebastien Bacher (seb128)]

The new 0.59.4 should fix the bug

[zeddock (zeddock)]

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

[aschmitz (aschmitz-)]

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 there within a few hours.) You will then be able to update as normal if all goes well. As an aside, if you're not comfortable with Linux, it might be a good idea to stick to the more-stable Ubuntu Feisty, rather than using the unstable Gutsy, but you know how comfortable you are with problems like this.

[Adam McDaniel (adamrmcd)]

Confirmed. 0.54.4 fixes the problem.

Thanks :)

[Adam McDaniel (adamrmcd)]

oops. 0.59.4 :P

[zeddock (zeddock)]

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
Great!

Thanx.

That worked.

On 8/16/07, Andy Schmitz <email address hidden> wrote:
>
> 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 there within a few hours.) You will then be able to update as
> normal if all goes well. As an aside, if you're not comfortable with
> Linux, it might be a good idea to stick to the more-stable Ubuntu
> Feisty, rather than using the unstable Gutsy, but you know how
> comfortable you are with problems like this.
>
> --
> Package 0.59.2 broken
> https://bugs.launchpad.net/bugs/132941
> You received this bug notification because you are a direct subscriber
> of the bug.
>