package nitroshare 0.3.0 failed to install/upgrade: there is no script in the new version of the package - giving up

Bug #1574391 reported by shaperton
28
This bug affects 4 people
Affects Status Importance Assigned to Milestone
nitroshare (Ubuntu)
Incomplete
Undecided
Nathan Osman

Bug Description

Just what the update to 16.04 generated.

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: nitroshare 0.3.0
ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
Uname: Linux 4.4.0-21-generic x86_64
ApportVersion: 2.20.1-0ubuntu2
Architecture: amd64
Date: Sun Apr 24 20:57:55 2016
ErrorMessage: there is no script in the new version of the package - giving up
InstallationDate: Installed on 2012-06-08 (1416 days ago)
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1
 apt 1.2.10ubuntu1
SourcePackage: nitroshare
Title: package nitroshare 0.3.0 failed to install/upgrade: there is no script in the new version of the package - giving up
UpgradeStatus: Upgraded to xenial on 2016-04-24 (0 days ago)

Revision history for this message
shaperton (hew-skaling) wrote :
Revision history for this message
Nathan Osman (george-edison55) wrote :

Thanks for reporting a bug! In order to process this report further and help pinpoint the issue, I'll need you to answer a couple of questions:

1. What release were you upgrading from? 12.04 or 14.04?
2. Where did you install NitroShare from? The stable PPA? The dev PPA? A DEB package?

Once I understand exactly what happened, I can take a closer look at what might have caused this and hopefully get it fixed.

Changed in nitroshare (Ubuntu):
assignee: nobody → Nathan Osman (george-edison55)
Thomas Ward (teward)
Changed in nitroshare (Ubuntu):
status: New → Incomplete
Revision history for this message
shaperton (hew-skaling) wrote :

Sure.

1. I was upgrading from 14.04.
2. I installed it from a DEB package.

As soon as I rebooted my computer, I reinstalled it again with the newest DEB package.
But I didn't do it because it had stopped working, it just bothered with the message.
Or that's what I've noticed.

The upgrade did all the work, I just relayed what it found out.

Revision history for this message
Nathan Osman (george-edison55) wrote :

Thanks! I'll see if I can figure out exactly what happened and report my findings back here.

Revision history for this message
Nathan Osman (george-edison55) wrote :

Just a quick update - I haven't forgotten about this bug. The last few weeks have been really busy dealing with the upgrade to 16.04 on all my systems.

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

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.