Nikola:
It should have been pushed into Hardy repos as well as all the other ones Hardy
- Karmic
--
[MASTER] Please update seamonkey to latest 1.1.17
https://bugs.launchpad.net/bugs/356274
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I see :) it is nice to see that, thanks a lot ;)
--
[MASTER] Please update seamonkey to latest 1.1.17
https://bugs.launchpad.net/bugs/356274
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
On 08/15/2009 06:50 AM, Nikola M wrote:
Somehow I don`t understand.
But if there is some documentation or discussion describing this process and
how and why
security-related updateted packages for Firefox could be uploaded to users
and Seamonkey can`t.
Last i talked to Alexander he was
https://launchpad.net/~ubuntu-mozilla-security/+archive/ppa Has all builds for
Seamonkey-1.1.17 can you please test on Hardy.
Seamonkey-1.1.18 should be released next week sometime i will start on it than,
should be done in a few days after release, and will do this all over again :)
but
The above comment about 1.1.18 releasing next week seems to be wrong it
has not been tagged for release by Mozilla so we will try to get 1.1.17
in today or tomorrow but still would like testers for at least hardy. I
have tested jaunty and karmic so far intrepid isnt really on my worry
list but
This bug was fixed in the package seamonkey - 1.1.17+nobinonly-
0ubuntu0.8.04.1
---
seamonkey (1.1.17+nobinonly-0ubuntu0.8.04.1) hardy-security; urgency=low
* New upstream security release: 1.1.17 (LP: #356274)
- CVE-2009-1841: JavaScript chrome privilege escalation
-
This bug was fixed in the package seamonkey - 1.1.17+nobinonly-
0ubuntu0.9.04.1
---
seamonkey (1.1.17+nobinonly-0ubuntu0.9.04.1) jaunty-security; urgency=low
* New upstream security release: 1.1.17 (LP: #356274)
- CVE-2009-1841: JavaScript chrome privilege escalation
-
I am using 1.1.17 from PPA for a very long time on Hardy 8.04/LTS 64-bit.
It is behaving just fine, as usual.
Sometimes it happens that it starts with its security subsystem disabled, and
works fine after start again, but it was happening also in versions before,
very rarely
and is no cause for
...
I still don`t see 1.1.17 released and/or on packages.ubuntu.com.
I am truly positive about Seamonkey and *Ubuntu and i am willing to commit my
time to see it
upgraded fo all user, faster then this.. Feel free to contact me.
June 22, 2009
SeaMonkey 1.1.17 Released
So maybe after 2 months
I think this could only happen after Seamonkey project releases 1.1.18.
Too many gears with too much friction are engaged in Ubuntu release
processes.
--
[MASTER] Please update seamonkey to latest 1.1.17
https://bugs.launchpad.net/bugs/356274
You received this bug notification because you are a
Somehow I don`t understand.
But if there is some documentation or discussion describing this process and
how and why
security-related updateted packages for Firefox could be uploaded to users and
Seamonkey can`t.
--
[MASTER] Please update seamonkey to latest 1.1.17
** Tags added: upgrade
--
[MASTER] Please update seamonkey to latest 1.1.17
https://bugs.launchpad.net/bugs/356274
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
On 08/05/2009 01:31 PM, Nikola M wrote:
We need to see to it, that this process is a bit faster in the future,
after all, browser update should be security thing, like it is for
Firefox. Me- volunteering to testing.
Talked to Alexander yesterday and he forgot about seamonkey
that is why it
On 08/04/2009 06:18 PM, Nikola M wrote:
Soo.. I don`t see Sm 1.1.17 on packages.ubuntu.com..
Ordinary users still using old one, I suppose.
What needs to be done for upgrade to hit all users, instead only ones that
have security repo On?
Right now its in Mozilla teams security release PPA
We need to see to it, that this process is a bit faster in the future,
after all, browser update should be security thing, like it is for
Firefox. Me- volunteering to testing.
--
[MASTER] Please update seamonkey to latest 1.1.17
https://bugs.launchpad.net/bugs/356274
You received this bug
Soo.. I don`t see Sm 1.1.17 on packages.ubuntu.com..
Ordinary users still using old one, I suppose.
What needs to be done for upgrade to hit all users, instead only ones that
have security repo On?
--
[MASTER] Please update seamonkey to latest 1.1.17
https://bugs.launchpad.net/bugs/356274
You
** Branch linked: lp:~mozillateam/seamonkey/seamonkey-1.1.dev
** Branch linked: lp:~mozillateam/seamonkey/seamonkey-1.1.jaunty
** Branch linked: lp:~mozillateam/seamonkey/seamonkey-1.1.intrepid
** Branch linked: lp:~mozillateam/seamonkey/seamonkey-1.1.hardy
--
[MASTER] Please update seamonkey
The branches have been merged from mine so it shouldnt be long for them
to hit.
--
[MASTER] Please update seamonkey to latest 1.1.17
https://bugs.launchpad.net/bugs/356274
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
Well at least should have been.
--
[MASTER] Please update seamonkey to latest 1.1.17
https://bugs.launchpad.net/bugs/356274
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Eh i didnt see you said on 64bit. i only tested 32bit.
--
[MASTER] Please update seamonkey to latest 1.1.17
https://bugs.launchpad.net/bugs/356274
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
It does work fine i tested this on my system before packaging it for
PPA. I have asked Alexander to push this to archives a few times and its
on his to do list. Unless im not here for some reason (like this week) i
package them the day they are released give or take a day.
--
[MASTER] Please
On 07/26/2009 09:22 AM, John Vivirito wrote:
Well at least should have been.
They were merged and sponsored by Alexander so the updates should hit soon.
--
Sincerely Yours,
John Vivirito
https://launchpad.net/~gnomefreak
https://wiki.ubuntu.com/JohnVivirito
Linux User# 414246
How can i
I am using 1.1.7 i compiled from PPA, I must say, it is working just
fine under my Hardy 64-bit. Release time?
--
[MASTER] Please update seamonkey to latest 1.1.17
https://bugs.launchpad.net/bugs/356274
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I downloaded Source code of Seamonkey 1.1.17 from Gnomefreak`s PPA
and made deb`s under Xubuntu 8.04.3/Hardy 64-bit. It works nice for now, :)
so I think it is ready po be pushed in Hardy-updates and other official repos
for supported releases.
--
[MASTER] Please update seamonkey to latest
Also Alexander, why is Seamonkey 1.1.17 declined for Hardy LTS and/or Interpid?
Security vunerabilities 1.1.17 is fixing:
http://www.mozilla.org/security/known-vulnerabilities/seamonkey11.html#seamonkey1.1.17
MFSA 2009-33 Crash viewing multipart/alternative message with text/enhanced
part
MFSA
Alexander can you please reopen them. i wont be back after today
07-19-2009 until the 21st. Im in meetings all day monday
--
[MASTER] Please update seamonkey to latest 1.1.17
https://bugs.launchpad.net/bugs/356274
You received this bug notification because you are a member of Ubuntu
Bugs, which
ok working on this for karmic atm if it all goes well jaunty intrepid
hardy to follow
** Changed in: seamonkey (Ubuntu Jaunty)
Status: Won't Fix = Triaged
** Changed in: seamonkey (Ubuntu)
Status: Incomplete = Triaged
--
[MASTER] Please update seamonkey to latest 1.1.17
On 07/06/2009 09:27 AM, John Vivirito wrote:
ok working on this for karmic atm if it all goes well jaunty intrepid
hardy to follow
** Changed in: seamonkey (Ubuntu Jaunty)
Status: Won't Fix = Triaged
** Changed in: seamonkey (Ubuntu)
Status: Incomplete = Triaged
I'm done
On 07/06/2009 09:27 AM, John Vivirito wrote:
ok working on this for karmic atm if it all goes well jaunty intrepid
hardy to follow
** Changed in: seamonkey (Ubuntu Jaunty)
Status: Won't Fix = Triaged
** Changed in: seamonkey (Ubuntu)
Status: Incomplete = Triaged
I'm done
On 06/25/2009 05:07 AM, Nikola M wrote:
It seems that 1.1.17 is released now.
Im ot for a bit longer ~a month. I sent an email to Alexander
to please update Seamonkey 1.x.x. A little while ago.
--
Sincerely Yours,
John Vivirito
https://launchpad.net/~gnomefreak
It seems that 1.1.17 is released now.
--
[MASTER] Please update seamonkey to latest 1.1.17
https://bugs.launchpad.net/bugs/356274
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
On 04/18/2009 05:44 PM, Steve Langasek wrote:
If the security fixes are already in, there doesn't seem to be a reason
to update jaunty after release. Declining the jaunty target.
** Changed in: seamonkey (Ubuntu Jaunty)
Status: Incomplete = Won't Fix
** Changed in: seamonkey
If the security fixes are already in, there doesn't seem to be a reason
to update jaunty after release. Declining the jaunty target.
** Changed in: seamonkey (Ubuntu Jaunty)
Status: Incomplete = Won't Fix
** Changed in: seamonkey (Ubuntu Jaunty)
Milestone: ubuntu-9.04 = None
--
Alexander thepatches were it they didnt release any more updates in the last
week or so.
Moving on to 1.1.17 when its released.
--
[MASTER] Please update seamonkey to latest 1.1.17
https://bugs.launchpad.net/bugs/356274
You received this bug notification because you are a member of Ubuntu
Bugs,
34 matches
Mail list logo
