This is a regression from Feisty, where the plugin was built.
During gutsy's cycle, Debian moved from lua50 to lua51 (which is in universe), 
so I reverted back the change, but looks like I did it wrong (but I blame the 
lua packaging! (-: ).

The bug is already fixed in Hardy, in 1.4.7-0ubuntu1:

  * debian/control: change liblua50-dev to liblualib50-dev, so configure
    recognizes LUA50. This builds the Script Manager. LP: #158422.

The above debdiff fixes it for Gutsy.

To reproduce the bug:
1/ Open Liferea
2/ Click on Tools->Script Manager
3/ No scripting support.

I think there's no regression in this, since actually the Script Manager
wasn't built. So in case it doesn't work well (although it should) it
won't be worse than before, when there wasn't scripting support at all.

** Description changed:

  Binary package hint: liferea
  
  Choosing Tools->Script Manager used to bring up a script window in
  feisty. Now I get an error message that scripting support is not
  available. I've already installed lua50 but that doesn't change
  anything.
+ 
+ TEST CASE: Open Liferea, click on Tools>Script Manager. There's no
+ scripting support. This is a regression from Feisty

-- 
[gutsy] liferea scripting support not working/activated
https://bugs.launchpad.net/bugs/158422
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/ubuntu-bugs

Reply via email to