Flashplugin-nonfree in backports fails to install

Ack, crap... You guys will never stop laughing at me for this one... I mislabeled my Dapper and Edgy test environments, so when I thought I tested this in Dapper, I was actually testing this in Edgy!

Some syntax of update-rc.d has changed from Dapper to Edgy. I need to hunt this down.

Marking Ubuntu's flashplugin-nonfree as affected.... The original Dapper version of flashplugin doesn't install either due to upstream version bump.

So, dapper-updates will need a new flashplugin anyway.

Ubuntu Archive admins, please pull flashplugin-nonfree from dapper-backports. sorry for the inconvenience.

https://lists.ubuntu.com/archives/edgy-changes/2006-September/006078.html

Actually, ubuntu-archive, on second thoughts, why not backport ~ubuntu2 :)

Related Forum:
http://www.ubuntuforums.org/showthread.php?t=261179

 * Trying to backport flashplugin-nonfree...
  - <flashplugin-nonfree_7.0.68~ubuntu2.dsc: downloading from librarian>
  - <flashplugin-nonfree_7.0.68~ubuntu2.tar.gz: downloading from librarian>
I: Extracting flashplugin-nonfree_7.0.68~ubuntu2.dsc ... done.
I: Building backport of flashplugin-nonfree-7.0.68~ubuntu2 ... done.

Now, can somebody please revert this change in edgy?

7.0.68~ubuntu2 isn't showing up in dapper-backports via Synaptic yet, but the package is in the archives and works quite nicely with Gdebi :)

http://archive.ubuntu.com/ubuntu/pool/multiverse/f/flashplugin-nonfree/flashplugin-nonfree_7.0.68~ubuntu2_i386.deb

In Gdebi, be sure to click 'Terminal' to be able to say yes to the EULA.

There are now a dozen and a half duplicates of this bug! For each report there are probably quite a few people who either have remained silent or don't know how to file/track bugs. It is not an exaggeration to estimate that there are probably literally hundreds of people who have been bitten by this bug, continue to suffer a lack of a working Flash plugin after having been bitten and more who *will be bitten* because the problematic package has not yet been removed from the server. SABDFL just got through a round of apologizing for a bad package (http://www.markshuttleworth.com/archives/54) and shouldn't have to again so soon! ;)

If you have permission to remove packages from the server, please Please PLEASE do so ASAP!

As the applier of said changes, I am very -- no, let me emphasize, EXTREMELY -- unimpressed that a knee-jerk backport was applied. The first 7.0.68 Edgy package was NOT to be backported to Dapper. Knowing that many people use the flashplugin-nonfree package in Edgy, I intended to wait several days to ensure that nothing was seriously broken before giving my approval for it to be backported to Dapper.

Seriously folks, backport candidates need to be well-tested in the current development branch BEFORE being backported to the stable branch(es).

I have this bug too. Exactly the same error.
Thank god I didn't suffer from the last 2 upgrade issues.

/me pokes the QA team

It appears that 7.0.68~ubuntu2~dapper1 is now in the backports and appearing in Synaptic. Thank you to whomever made the update!

As a result of following this bug, I have filed a bug report (Bug #61957) against the Malone, the bugtracker used by Ubuntu.

The essence of the bug report is that Malone defaults to not showing reports if they are either "fix released" or "duplicate". This is counter-intuitive and has, in my opinion, contributed to the flood of duplicates. A user checking bug reports would reasonably believe that no report had been filed.

How do I get rid of ??

rid of what?

2010/1/10 Lisa Hetherington <email address hidden>

> How do I get rid of ??
>
> --
> Flashplugin-nonfree in backports fails to install
> https://bugs.launchpad.net/bugs/61404
> You received this bug notification because you are a direct subscriber
> of a duplicate bug.
>

--
Eduardo Alvarenga