On Mon, 2006-02-06 at 15:50 -0800, Dan Nicholson wrote:
For my own scripts, I would do the sed like Tushar mentioned. I don't
like compatibility symlinks at all. Just looked at configure for
evolution. Looks like
sed -i 's/mozilla-nss/nss/g' configure
might work. Haven't tested it,
Tim van der Molen wrote:
OpenSSH 4.3p1 has recently been released. Besides several bug fixes one
security bug has been addressed. The announcement is available at
http://marc.theaimsgroup.com/?l=openbsd-announcem=113893053104991w=2.
This is BLFS ticket #1791
Hello,
can the dates shown by Trac be modified so that they use another format,
preferably -MM-DD?
Example:
On URL:http://wiki.linuxfromscratch.org/blfs/ticket/1791, in the
Change History section, you can read:
02/01/06 11:36:05: Modified by [EMAIL PROTECTED]
I'm confused by this date
Nico R. wrote:
Hello,
can the dates shown by Trac be modified so that they use another format,
preferably -MM-DD?
I'll look into it. Thanks for the report.
--
JH
--
http://linuxfromscratch.org/mailman/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See
On Mit, 2006-02-08 at 06:06 -0800, Dan Nicholson wrote:
On 2/8/06, Juerg Billeter [EMAIL PROTECTED] wrote:
s/mozilla-ns/ns/g works fine for me with system nss and nspr for
evolution and evolution-data-server.
Juerg,
I was snooping around Paldo looking at how you set up
On Wed, 2006-02-08 at 06:06 -0800, Dan Nicholson wrote:
1. You install NSS and NSPR as separate packages. Do you know if this
is any different than using the NSPR that's bundled with NSS?
They have always been separate in the past. Only this last most
recent 3.11 version did they bundle them
On 2/8/06, Jürg Billeter [EMAIL PROTECTED] wrote:
On Mit, 2006-02-08 at 06:06 -0800, Dan Nicholson wrote:
2. You don't seem to make any corrections to the firefox-{nss,nspr}.pc
files. Have you noticed any other packages where this causes a
problem?
That's in fact a bug in our firefox
On 2/8/06, Randy McMurchy [EMAIL PROTECTED] wrote:
Dan Nicholson wrote these words on 02/08/06 10:03 CST:
Thanks, Juerg. I think I may make a patch that uses the
MOZ_NATIVE_NSPR and MOZ_NATIVE_NSS (introduced in the firefox nss
patch) to suppress the installation of firefox-{nss,nspr}.pc.
On Mit, 2006-02-08 at 10:06 -0600, Randy McMurchy wrote:
Dan Nicholson wrote these words on 02/08/06 10:03 CST:
Thanks, Juerg. I think I may make a patch that uses the
MOZ_NATIVE_NSPR and MOZ_NATIVE_NSS (introduced in the firefox nss
patch) to suppress the installation of
Dan Nicholson wrote these words on 02/08/06 10:21 CST:
Which packages look for {firefox,thunderbird}-{nss,nspr}.pc? We know
evolution looks for mozilla-{nss,nspr}.pc.
I don't remember off-hand, I'll let you do the research as you seem
interested in knowing the specifics.
Do we patch to fix
Dan Nicholson wrote these words on 02/08/06 10:03 CST:
Thanks, Juerg. I think I may make a patch that uses the
MOZ_NATIVE_NSPR and MOZ_NATIVE_NSS (introduced in the firefox nss
patch) to suppress the installation of firefox-{nss,nspr}.pc. I think
we're all in agreement that these are
Jürg Billeter wrote these words on 02/08/06 10:28 CST:
IMO the real bug is that Firefox/Thunderbird upstream uses
firefox-{nss,nspr}.pc instead of just {nss,nspr}.pc or
mozilla-{nss,nspr}.pc (whatever they like, it just shouldn't depend on
the tarball you're downloading).
The packages that
Randy McMurchy wrote:
My only point is that
we need to keep the files on the system until upstream is fixed.
Perhaps we should find out if upstream is going to address this issue.
In my experience, the best way to communicate with the Moz developers is
to input a bug into their bugzilla
Bruce Dubbs wrote these words on 02/08/06 11:03 CST:
Perhaps we should find out if upstream is going to address this issue.
However, we really cannot do that now, as upstream really doesn't
support using system-installed NSS/NSPR libs. Their implementation
is incomplete. It would probably be
On 2/8/06, Bruce Dubbs [EMAIL PROTECTED] wrote:
Perhaps we should find out if upstream is going to address this issue.
In my experience, the best way to communicate with the Moz developers is
to input a bug into their bugzilla describing the problem along with a
recommended fix.
Dan Nicholson wrote these words on 02/08/06 13:01 CST:
I think we should make some noise. I will add my two cents on these
bugs. I'm at work right now, though, and I already spent a bit too
much time on this. Will try to get some good comments in tonight.
Thanks for the research, Dan.
--
On 2/6/06, Randy McMurchy [EMAIL PROTECTED] wrote:
3) In the NSS instructions, make a symlink: mozilla-nss - nss.pc
This fixes the problem and if you install Mozilla it will simply
overwrite the symlink.
4) Other suggestions provided by the community.
Randy, I just had another thought which
On Mit, 2006-02-08 at 20:58 +, Alan Lord wrote:
In the Perl script set_soenv the offending line is:
ToFile( MOZ_NSPR_CFLAGS, @MOZ_NSPR_CFLAGS@, e );
Am I being thick? Should I have only applied the nspr patch?
On first glance it looks like you didn't regenerate the configure script
18 matches
Mail list logo
