From: Peter Chant on
Eric Hameleers wrote:

>
> Yes.

Does this mean we get to guess dates for 13.1? Seems to soon to me!

Only joking BTW.

Pete

--
http://www.petezilla.co.uk

From: Manuel Reimer on
Eric Hameleers wrote:
>> Does anyone know what's going on?

> Yes.

Nice to know and sorry for my imprecise question. Would you be so kind
to tell us what's going on?

As gentoo also doesn't have the SeaMonkey updates, so far, I think it's
no big problem that Slackware still needs some time. As long as it takes
for the patch to be available, I'm using an official binary package from
mozilla.org. If mozilla.org publishes a security update, it's usually a
pretty good idea to update immediately...

CU

Manuel

From: Mikhail Zotov on
On Tue, 23 Feb 2010 19:39:06 +0100
Manuel Reimer <mreimer(a)expires-28-02-2010.news-group.org> wrote:
....
> As gentoo also doesn't have the SeaMonkey updates, so far, I think
> it's no big problem that Slackware still needs some time. As long as
> it takes for the patch to be available, I'm using an official binary
> package from mozilla.org.

The `official' Slackware -current build script for Seamonkey-2.0.2
works fine for 2.0.3. Just delete (comment) a line below

# Fix missing #include <cstdio> in version 2.0.2:

Thus, no need to wait for an update.

--
Mikhail

From: Manuel Reimer on
Mikhail Zotov wrote:
> The `official' Slackware -current build script for Seamonkey-2.0.2
> works fine for 2.0.3. Just delete (comment) a line below

> # Fix missing #include <cstdio> in version 2.0.2:

> Thus, no need to wait for an update.

I'm already running my own PC with the official SeaMonkey 2.0.3 binary.

The problem is, that I have more than just one Slackware PC in my
relationship. Those PCs are auto-updated with official Slackware
packages. So I only have two options: Wait for the official patch, which
would be automatically installed on all those PCs, or walk from PC to PC
to install a self-made patch package.

CU

Manuel

From: Sylvain Robitaille on
Manuel Reimer wrote:

> ... only have two options: Wait for the official patch, which would be
> automatically installed on all those PCs, or walk from PC to PC to
> install a self-made patch package.

While you're at it, make sure to install and enable ssh so that next
time you're in a similar situation you'll be able to install your own
package on them all remotely.

--
----------------------------------------------------------------------
Sylvain Robitaille syl(a)encs.concordia.ca

Systems analyst / AITS Concordia University
Faculty of Engineering and Computer Science Montreal, Quebec, Canada
----------------------------------------------------------------------
First  |  Prev  |  Next  |  Last
Pages: 1 2 3 4
Prev: Alt.OS.Linux.Slackware FAQ pointer
Next: libgtk-1.2.so.0