[Bug 173890] Re: flashplugin-nonfree fails to install... new version?
kane.michael.john at gmail.com
Wed Dec 19 21:40:56 UTC 2007
GICodeWarrior Couldn't a complete backup of the previous known working
version be keep on a Canonical/Ubuntu server. This way if there is any
problems with this particular package again the user could simply use
aptitude to pull the package from a dedicated Ubuntu server/repo, and not
pull it direct from adobe?
Note: not sure this is possible.
On Dec 19, 2007 4:22 PM, GICodeWarrior <GICodeWarrior at hotmail.com>
> David Walker wrote on 2007-12-17:
> > Couldn't something be done to not use md5sums in the .deb file? Since we
> > no idea when Adobe may change the file, could there be a way to say,
> > the file 2 or 3 times and see if the sum is all the same. OR, have some
> > dedicated machine somewhere that once-a-day downloads and generates the
> > md5sum, which users can check against?
> The md5sum check is not only to verify the integrity of the file. It is
> also to verify the version.
> When the version changes, two things need to happen. The package needs
> to be updated to reflect the version change, so users are notified of
> the available upgrade. Also, the new version needs to be tested.
> If the new version was automagically pushed, everyones flash
> installations could be broken.
> Perhaps a better route would be to ask Adobe to distribute the previous
> versions of the plugin separately rather than in a massive tarball. If
> they had each version in a separate, numbered tarball each version of
> the flash package could point directly to the proper version, and this
> problem would go away.
> flashplugin-nonfree fails to install... new version?
> You received this bug notification because you are a direct subscriber
> of a duplicate bug.
flashplugin-nonfree fails to install... new version?
You received this bug notification because you are a member of Mozilla
Bugs, which is a bug contact for flashplugin-nonfree in ubuntu.
More information about the Ubuntu-mozillateam-bugs