Dan,
Perhaps my email wasn't clear. It says "also need to provide user
instructions to backup the entire repo". By "also" I meant "in
addition to" a gold backup/recovery.
Thanks for clarifying a couple points I could not get an answer to:
1) Our only backup devices are the cluster disks.
2
Dear Mary,
I have read this in the Postegresql wiki page of the French Ubuntu community
about the release 8.3 :
"Il est important de remarquer que lors de l'installation, les bases de
données sont créées en unicode et qu'à cause de cela, il ne sera pas
possible de créer une base de données dans u
On Mon, 10 Aug 2009 12:48:25 -0600
Bob Gobeille wrote:
>
> On Aug 10, 2009, at 12:20 PM, Matt Taggart wrote:
>
> >> Are you saying you would rather move it to a separate package than
> >> remove it from the main package?
> >
> > I'm saying it should remain the the upstream fossology tarball,
>
Bob,
I agree with you, the best user experience would come from backup and
restore of the entire repository. In our case, however, there's a big
problem: We do not have enough unallocated disk space on the RFO cluster to
implement this.
So I don't see a problem in recommending the full
On August 10, 2009 Bob Gobeille wrote:
> On Aug 10, 2009, at 2:25 PM, Todd Beverly wrote:
>> I recently install fossology v 1.1 and made the decision to not use
>> the /repo/ sub directory in Apache. I got everything to work, except
>> the link in the email message always returns
>> http://$hostn
> Hello all.
>
> I recently install fossology v 1.1 and made the decision to not use
> the /repo/ sub directory in Apache. I got everything to work, except
> the link in the email message always returns
> http://$hostname/repo/?...I tracked this down to routine
> /usr/local/bin/fo_
On Aug 10, 2009, at 2:25 PM, Todd Beverly wrote:
Hello all.
I recently install fossology v 1.1 and made the decision to not
use
the /repo/ sub directory in Apache. I got everything to work, except
the link in the email message always returns
http://$hostname/repo/?...I tracked thi
Hello all.
I recently install fossology v 1.1 and made the decision to not use
the /repo/ sub directory in Apache. I got everything to work, except
the link in the email message always returns
http://$hostname/repo/?...I tracked this down to routine
/usr/local/bin/fo_notify, which
Hi Vincent,
As per my previous email, this is probably not a great way to back up
a fossology database. But it's good functionality to have because we
could add a feature that allows users to remove all non-reused files
except gold to save disk space. I don't see any bad ramifications
e
On Aug 10, 2009, at 1:44 PM, Donohoe, Mark wrote:
Laser, Mary wrote:
I agree. We did it mostly as an example to show our
potential. But now I'm thinking that we shouldn't have
released it until we actually use the data. Right now it's a
cost with no benefit unless people are doing direct db
Laser, Mary wrote:
I agree. We did it mostly as an example to show our
potential. But now I'm thinking that we shouldn't have
released it until we actually use the data. Right now it's a
cost with no benefit unless people are doing direct db
queries or are counting on a UI to use it in the
>
> I agree. We did it mostly as an example to show our
> potential. But now I'm thinking that we shouldn't have
> released it until we actually use the data. Right now it's a
> cost with no benefit unless people are doing direct db
> queries or are counting on a UI to use it in the future.
On Aug 10, 2009, at 12:20 PM, Matt Taggart wrote:
Are you saying you would rather move it to a separate package than
remove it from the main package?
I'm saying it should remain the the upstream fossology tarball, but
for
Debian I can put it in a separate package that won't be required (th
> Are you saying you would rather move it to a separate package than
> remove it from the main package?
I'm saying it should remain the the upstream fossology tarball, but for
Debian I can put it in a separate package that won't be required (the
fossology-agents package will only Recommends in
On Aug 10, 2009, at 11:22 AM, Matt Taggart wrote:
2) remove the Metadata analysis
If you are only interested in licenses, this analysis does nothing
for
you except cost you time and disk space. What it does is extract
metadata from images, doc files, etc. This agent has caused many of
you
> 1) switch to postgres 8.3 or greater
> Some of you already use 8.3 (or possibly 8.4). I would like to
> REQUIRE 8.3 or greater in order to provide better text searching and
> tools to facilitate database partitioning. This means that if you are
> using <8.3, you will have to upgrade postg
The next fossology release (what we are currently calling 1.2 but
maybe should be 2.0) involves some pretty large changes. Especially
for licenses, data persistence, and future sharing of repository data.
http://fossology.org/task_list
Because of this it would be most helpful if you could le
On Aug 10, 2009, at 4:31 AM, Jonathan Parès wrote:
Dear all,
As Qualipso project team member (http://qualipso.org/), I want to
use Fossology to retrieve some metrics about the licenses available
on a FLOSS projects. I would like to retrieve these following
metrics with Fossology :
- t
Hi Jonathan,
Thanks for the update. I spent several hours Friday examining the PostgreSQL
log file you sent me and could not find the source of your problem. I don't
think it's due to encoding but, I'll look specifically for that issue.
I will also try to recreate the problem you describe belo
Dear all,
As Qualipso project team member (http://qualipso.org/), I want to use
Fossology to retrieve some metrics about the licenses available on a FLOSS
projects. I would like to retrieve these following metrics with Fossology :
- the number of distinct licenses incorporated (called then LCS-1
Hi Bob,
If no dependencies with the unpacked files at the backup point, I think we
should not do unpack on the fly at the restore time. We just restore the gold
files and give the user's opinion to unpack the gold files as they needed.
Is this opinion make sense? Or this will bring some bad rami
21 matches
Mail list logo
