@Nikola M: of course one can download the source, the question is: will
it compile gracefully? I am sure you're aware of the dependency chains
that have to be satisfied in order to have a stable system. Sometimes
it's just not possible to have a newer version of software X without
updating chains
Tiberiu Cristea wrote on 2009-04-08:
In Windows or MacOS X anyone can fix this issue by themselves, by just
visiting the developer's site and
downloading the latest version. This bug clearly shows how the centralised
repository system is a failure.
You are terribly wrong and your saying
I guess that's what you get for using a development process that
includes middlemen, such as the package maintainers. The fix exists,
it's been available upstream, yet people depend on a lazy package
maintainer to deliver the fix.
In Windows or MacOS X anyone can fix this issue by themselves, by
Seamonkey was updated to 1.1.15 on April 1 for Hardy and Intrepid.
** Changed in: seamonkey (Ubuntu Hardy)
Status: Triaged = Fix Released
** Changed in: seamonkey (Ubuntu Intrepid)
Status: Triaged = Fix Released
--
Seamonkey should be updated to 1.1.13
We post bugs because we Love to see things fixed to the benefit to us and the
other users.
That is all about development process. We contribute, it comes back to all.
Seamonkey itself is in Universe repository and that means that it is not core
of Ubuntu but included
to user`s request. So Core
Hi.
I can download and install 64-bit binary from seamonkey-project.org but It`s
not the point.
I Need to do that to my notebook computer, to my VM installations, to my
friend`s computer, etc etc..
I would rather make all effort I can and is in my power to make newer SM
available to *Ubuntu
Oh, I understand.
I guess I'm just a little disappointed by the fact that there hasn't
been any official response to this.
Supposedly 30 different people and the so-called Ubuntu Security Team
have been notified of this bug. And not one single one of these people
has said boo about it.
Now I
Well, after dealing with my own bug in Seamonkey 1.1.12 for two months
https://bugs.launchpad.net/ubuntu/+source/seamonkey/+bug/290857
And starting to realize that there is a serious security problem with the
Seamonkey package in Intrepid's repositories, I upgraded to Seamonkey 1.1.14
about a
Since Seamonkey 1.1.14 is released it would be good idea for Seamonkey package
to be released for Hardy and Interpid, instead of 1.1.13. I think yamo have a
point here.
Or we should make another Bug about upgrading to 1.1.14?
Seamonkey 1.1.14 security and bug fixes:
I don't see a fixed bug on SSL here : http://www.mozilla.org/security
/known-vulnerabilities/seamonkey11.html#seamonkey1.1.13.
May be the Seamonkey 1.1.14 on 2008-12-16 will fix it ; so is it
possible to directly move from 1.1.12 to 1.1.14?
--
Seamonkey should be updated to 1.1.13
Anybody know where we stand on this?
I've been dealing with a really annoying bug in 1.1.12
https://bugs.launchpad.net/ubuntu/+source/seamonkey/+bug/290857
that I am hoping will be fixed with version 1.1.13.
--
Seamonkey should be updated to 1.1.13
https://bugs.launchpad.net/bugs/297789
You
This bug was fixed in the package seamonkey - 1.1.13+nobinonly-0ubuntu1
---
seamonkey (1.1.13+nobinonly-0ubuntu1) jaunty; urgency=low
* New security upstream release: 1.1.13 (LP: #297789)
- CVE-2008-4582: Information stealing via local shortcut files
- CVE-2008-5012: Image
** Changed in: seamonkey (Ubuntu Hardy)
Importance: Undecided = Critical
Status: New = Triaged
** Changed in: seamonkey (Ubuntu Intrepid)
Importance: Undecided = Critical
Status: New = Triaged
--
Seamonkey should be updated to 1.1.13
https://bugs.launchpad.net/bugs/297789
According to packages.debian.org, there is Iceape 1.1.13 available i their
repository.
So, Seamonkey 1.1.13 for Ubuntu should be made available.
I take a look to other distributions releases and they all updated this
security-related
release to version 1.1.13 (Debian, Fedora, Slackware,
14 matches
Mail list logo
