Great, thanks for clarification, So it seems that Bug #461864
(Seamonkey 2.0) should come into some serious consideration, then.
--
[MASTER] Please update seamonkey to latest 1.1.18
https://bugs.launchpad.net/bugs/356274
You received this bug notification because you are a member of Ubuntu
Bugs,
Probably updating to 1.1.18 is pointless for the reasons described here:
http://www.mail-archive.com/secure-testing-t...@lists.alioth.debian.org/msg02588.html
One more reason is Seamonkey 1.x series is pronounced not oldstable
anymore but unsupported instead so may be reasonable to start looking
i
On 10/12/2009 06:02 PM, Nikola M wrote:
> Surprised it still is not released in Ubuntu. (Just came back from a trip ;)
> Hmm, I would need to learn this packaging stuff..
>
Sorry i havent had time to work out the errors yet. This late
i will be looking for 1.1.19 to update to. I will update the
bu
Surprised it still is not released in Ubuntu. (Just came back from a trip ;)
Hmm, I would need to learn this packaging stuff..
--
[MASTER] Please update seamonkey to latest 1.1.18
https://bugs.launchpad.net/bugs/356274
You received this bug notification because you are a member of Ubuntu
Bugs, wh
Bug #425757 should get fixed when we update to 1.1.18.
The is a slight conflict with pataches for whom ever gets to it before i do.
** Changed in: seamonkey (Ubuntu)
Status: In Progress => Confirmed
** Changed in: seamonkey (Ubuntu Jaunty)
Status: In Progress => Confirmed
** Chang
ok I up0dated the bug for 1.1.18 it was released yesterday i think, but
either way i was gone when it was released. I'm going to try and have
this done for Alexander to push
** Summary changed:
- [MASTER] Please update seamonkey to latest 1.1.17
+ [MASTER] Please update seamonkey to latest 1.1.18
