Displaying 8 results from an estimated 8 matches for "reasom".
Did you mean:
reason
2016 Feb 02
1
[PATCH] remove src/share/utf8/Makefile.am
The patch <https://git.xiph.org/?p=flac.git;a=commitdiff;h=b3c3e2ac4fcac9d9b178ad240976634d52d5eece>
removed Makefile.am files from subdirs of src/share, but for
some reasom didn't remove src/share/utf8/Makefile.am.
This file is not included into release tarballs, so I think it's
indeed unnecessary. It's better to remove it than let it bit-rot.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: remove_unused_makefile.patch...
2017 Jul 06
4
Regarding R_LIBS_USER
Hello,
I just subscribed to the list to join the discussion after being
blindsided by the change and reading Dirk Eddelbuettel's reply to my
bug report at https://bugs.debian.org/866768 .
As far as I can tell the advantages of site library are:
1. Saves disk space and a little bit of user time spent installing and
upgrading.
2. Other Debian package manages, like pip, default?to
2017 Jul 06
1
Regarding R_LIBS_USER
...Usually R
libraries are not version specific, even though in the case of R 3.0.0 and
3.4.0 compatibility was interrupted.
> So maybe the change was too abrupt, and I think I may revert it. I
> generally prefer for packagers like myself to not divert from upstream
> unless they have good reasom or are unintrusive (and eg the added
> tab-completion we have here is both). But leaving newbies without
> installable directories is bad, as is possibly hiding existing
> installations.
I also like the idea of multiuser libraries, and in general the idea is that
the most current packag...
2017 Jul 06
2
Regarding R_LIBS_USER
...d directory less than ideal as well. But it ensures
> writeability. Which I cannot do easily from the package.
>
>
> So maybe the change was too abrupt, and I think I may revert it. I
> generally prefer for packagers like myself to not divert from upstream
> unless they have good reasom or are unintrusive (and eg the added
> tab-completion we have here is both). But leaving newbies without
> installable directories is bad, as is possibly hiding existing
> installations.
There are several entangled issues:
1. What should be the default places where packages are installed...
2017 Jul 06
0
Regarding R_LIBS_USER
...below $HOME and
in a versioned directory less than ideal as well. But it ensures
writeability. Which I cannot do easily from the package.
So maybe the change was too abrupt, and I think I may revert it. I
generally prefer for packagers like myself to not divert from upstream
unless they have good reasom or are unintrusive (and eg the added
tab-completion we have here is both). But leaving newbies without
installable directories is bad, as is possibly hiding existing
installations.
I am a little pressed for time (at useR!) and system (main server is
ill, as is backup machine) but I should get a 3...
2011 Mar 19
0
FW: Samba PDC error
________________________________
From: Arun Sasi V (WI01 - Manage IT)
Sent: Sat 3/19/2011 11:42 PM
To: samba-technical at lists.samba.org
Subject: Samba PDC error
I am not able to jon the domain ...
What could be the reasom ... I have configired samba as PDC and authenticating via Ldap
[2011/03/19 21:34:27, 0] libsmb/clientgen.c:cli_receive_smb(165)
Receiving SMB: Server stopped responding
[2011/03/19 21:34:27, 3] libsmb/cliconnect.c:cli_session_setup(1055)
SPNEGO login failed: NT_STATUS_IO_TIMEOUT
[2011/03/19...
2017 Jul 07
0
Regarding R_LIBS_USER
...well. But it ensures
> > writeability. Which I cannot do easily from the package.
> >
> >
> > So maybe the change was too abrupt, and I think I may revert it. I
> > generally prefer for packagers like myself to not divert from upstream
> > unless they have good reasom or are unintrusive (and eg the added
> > tab-completion we have here is both). But leaving newbies without
> > installable directories is bad, as is possibly hiding existing
> > installations.
>
> There are several entangled issues:
> 1. What should be the default place...
2017 Jul 07
1
Regarding R_LIBS_USER
...t; > writeability. Which I cannot do easily from the package.
> > >
> > >
> > > So maybe the change was too abrupt, and I think I may revert it. I
> > > generally prefer for packagers like myself to not divert from upstream
> > > unless they have good reasom or are unintrusive (and eg the added
> > > tab-completion we have here is both). But leaving newbies without
> > > installable directories is bad, as is possibly hiding existing
> > > installations.
> >
> > There are several entangled issues:
> > 1. Wha...