Commit db86a004 authored by Bernhard Link's avatar Bernhard Link

fix spelling errors

parent 1f73fa8f
2006-10-31 Bernhard R. Link <brlink@debian.org>
* fix spelling mistakes in manpage (thanks to A. Costa)
fixed the same errors in the code and its messages
2006-10-29 Bernhard R. Link <brlink@debian.org>
* fix updatechecksums for .changes files not
listing entries from the .dsc
......@@ -15,7 +19,7 @@
2006-10-06 Bernhard R. Link <brlink@debian.org>
* FilterList in update and pull rules now
is a space seperated list of files.
is a space separated list of files.
2006-10-03 Bernhard R. Link <brlink@debian.org>
* fix typos and spelling errors in manpage (Thanks to Bruce Sass)
......@@ -503,7 +507,7 @@
* Add some #includes so that it also compiles without
warnings on sarge/i386
* --ignore= allows multiple options seperated by comas.
* --ignore= allows multiple options separated by comas.
* Tell about -b if conf/distributions cannot be found
......
......@@ -18,7 +18,7 @@ Updates since 1.2.0:
--ignore=surprisingbinary is given. (A .dsc with an other name
or a .deb with an other Source than the Source-header if the
.changes file is still not ignoreable due to file naming issues)
- FilterList in update and pull rules now has a space seperated list
- FilterList in update and pull rules now has a space separated list
of filenames instead of only a single filename.
- new Uploaders field in conf/distributions:
allows to specify what a .changes file has to be signed with to be allowed in
......
......@@ -460,7 +460,7 @@ retvalue dsc_addprepared(const struct dscpackage *pkg,const char *dbdir,referenc
retvalue r;
struct target *t = distribution_getpart(distribution,pkg->component,"source","dsc");
/* finaly put it into the source distribution */
/* finally put it into the source distribution */
r = target_initpackagesdb(t,dbdir);
if( !RET_WAS_ERROR(r) ) {
retvalue r2;
......
......@@ -405,7 +405,7 @@ retvalue chunk_getname(const char *chunk,const char *name,
field++;
name_end = field;
/* this has now checked somewhere else for correctness and
* is only a pure seperation process:
* is only a pure separation process:
* (as package(version) is possible, '(' must be checked) */
while( *name_end != '\0' && *name_end != '\n' && *name_end != '(' && !xisspace(*name_end) )
name_end++;
......@@ -459,7 +459,7 @@ retvalue chunk_getnameandversion(const char *chunk,const char *name,
field++;
name_end = field;
/* this has now checked somewhere else for correctness and
* is only a pure seperation process:
* is only a pure separation process:
* (as package(version) is possible, '(' must be checked) */
while( *name_end != '\0' && *name_end != '\n' && *name_end != '(' && !xisspace(*name_end) )
name_end++;
......
reprepro (1.3.1-1) UNRELEASED; urgency=low
* bugfix release
- make changestool's updatechecksums work with '-sd' .changes-files
- fix some spelling errors (Closes: 396316)
-- Bernhard R. Link <brlink@debian.org> Wed, 1 Nov 2006 13:45:35 +0100
reprepro (1.3.0-1) unstable;urgency=low
* make package description libdb version independent (Closes: 387345)
......
......@@ -66,7 +66,7 @@ retvalue dirs_make_parent(const char *filename) {
return RET_OK;
}
/* create dirname and any '/'-seperated part of it */
/* create dirname and any '/'-separated part of it */
retvalue dirs_make_recursive(const char *directory) {
retvalue r,result;
......
......@@ -12,7 +12,7 @@
/* create recursively all parent directories before the last '/' */
retvalue dirs_make_parent(const char *filename);
/* create dirname and any '/'-seperated part of it */
/* create dirname and any '/'-separated part of it */
retvalue dirs_make_recursive(const char *directory);
/* Behave like dirname(3) */
......
......@@ -39,7 +39,7 @@ struct distribution {
/*@null@*/char *signwith;
/* the override file to use by default */
/*@null@*/char *deb_override,*udeb_override,*dsc_override;
/* the list of components containing a debian-installer dir, normaly only "main" */
/* the list of components containing a debian-installer dir, normally only "main" */
struct strlist udebcomponents;
/* what kind of index files to generate */
struct exportmode dsc,deb,udeb;
......
......@@ -51,7 +51,7 @@ them up. Also up/downgrading a host from one distribution to the other
will not change the package but just keep the old (as they are the
same version, so they have to be the same, apt and dpkg will think).
How to deal with this without seperating repositories depends on how
How to deal with this without separating repositories depends on how
you reached this situation:
- in the past Debian's stable and stable-security buildds sometimes both
......@@ -74,12 +74,12 @@ you reached this situation:
dpkg's --compare-versions action).
- a package built for multiple distributions
is equivalent to the backports case
- localy modified packages that should be replace by newer official
- locally modified packages that should be replace by newer official
versions: append something like "a0myname". If it should be
replaced by security updates of the official package, make sure (using
dpkg's --compare-versions) that a security update would have
a higher version.
- localy modified packages that should not be replaced by newer
- locally modified packages that should not be replaced by newer
official versions: prefix the version with "99:" and perhaps appending
it with something like "-myname". (appending only makes it easier to
distinguish, as some tools do not show epochs).
......
......@@ -2,7 +2,7 @@ Some tipps what to do if (hopefully never), your database gets
corrupted:
First there are three different databases used, residing in three
files in your --dbdir (normaly db/):
files in your --dbdir (normally db/):
1) references.db
This file only contains the information which file in the pool/
......@@ -21,7 +21,7 @@ are known. Files not in here will not be deleted with
(and thus not corrected even if told to be newly included)
To get this database in textform use "_listmd5sums" without argument,
to add items manualy pipe it into "_addmd5sums". (Filenames
to add items manually pipe it into "_addmd5sums". (Filenames
are handled as strings, so be careful).
If the database is completely lost, you can regain it by moving
......
.TH REPREPRO 1 "11 October, 2006" "reprepro" REPREPRO
.TH REPREPRO 1 "1 November, 2006" "reprepro" REPREPRO
.SH NAME
reprepro \- produce, manage and sync a local repository of debian packages
.SH SYNOPSIS
......@@ -268,7 +268,7 @@ Plus if you cannot
download a updated package in the (hopefully) following update
run, you will end up with no package at all instead of an old one.
This will also blow up pindex files if you are using the tiffany
example or somethine similar.
example or something similar.
So be careful when using this option or better get some more space so
that update works.
.TP
......@@ -593,7 +593,7 @@ If it is 3, at least a third of yet uncached files and at most a
third of all files is read.
And so on...
After that a space seperated list of options can be given.
After that a space separated list of options can be given.
If there is a \fBudebs\fP keyword, \fB.udeb\fPs are also listed
(in a file called \fBuContents\-\fP\fIarchitecture\fP.)
If there is a \fBnodebs\fP keyword, \fB.deb\fPs are not listed.
......@@ -791,7 +791,7 @@ The codename of the distribution to pull packages from.
.TP
.B Components
The components of the distribution to get from.
Unknown items are ignored to ease rule reusal.
Unknown items are ignored to ease rule reuse.
If there are no items, all components from distribution are taken.
(Use some non existing like "none", if you want none).
.TP
......@@ -1149,13 +1149,13 @@ does not know anything needing them right know, you can use
To delete them:
.br
\fBreprepro deleteunreferenced\fP
.SH INTERUPTING
Interupting reprepro has its problems.
.SH INTERRUPTING
Interrupting reprepro has its problems.
Some things (like speaking with apt methods, database stuff) can cause
problems when interupted at the wrong time.
Then there are design problems of the code making it hard to destinguish
if the current state is dangerous or non-dangerous to interupt.
Thus if reprepro receives a signal normaly sent to tell a process to
problems when interrupted at the wrong time.
Then there are design problems of the code making it hard to distinguish
if the current state is dangerous or non-dangerous to interrupt.
Thus if reprepro receives a signal normally sent to tell a process to
terminate itself softly,
it continues its operation, but does not start any new operations.
(I.e. it will not tell the apt-methods any new file to download, it will
......@@ -1166,10 +1166,10 @@ it will not delete any files gotten dereferenced, and so on).
given type will terminate reprepro. You will risk database corruption
and have to remove the lockfile manually.\fP
Also note that even normal interuption leads to code-paths mostly untested
Also note that even normal interruption leads to code-paths mostly untested
and thus expose a multitude of bugs including those leading to data corruption.
Better think a second more before issuing a command than risking the need
for interuption.
for interruption.
.SH "REPORTING BUGS"
Report bugs or wishlist requests to <brlink@debian.org>
.br
......
......@@ -35,7 +35,7 @@ DebOverride: override
UDebOverride: override
DscOverride: srcoverride
Multiple entries are seperated with an empty line.
Multiple entries are separated with an empty line.
The codename is used to determine the directory to create.
The Update line is described later. If SignWith is there,
it will try to sign it. (Either use "yes" or give something
......
......@@ -326,7 +326,7 @@ static retvalue callexporthook(const char *confdir,/*@null@*/const char *hook, c
return RET_ERROR;
}
} else {
fprintf(stderr,"Exporthook terminated abnormaly. (status is %x)!\n",status);
fprintf(stderr,"Exporthook terminated abnormally. (status is %x)!\n",status);
return RET_ERROR;
}
}
......
......@@ -231,7 +231,7 @@ retvalue filelist_add(struct filelist_list *list,const struct filelist_package *
}
static const char header[] = "FILE LOCATION\n";
static const char seperator[] = "\t ";
static const char separator[] = "\t ";
static void filelist_writefiles(char *dir, size_t len,
struct filelist *files, struct filetorelease *file) {
......@@ -243,7 +243,7 @@ static void filelist_writefiles(char *dir, size_t len,
filelist_writefiles(dir,len,files->nextl,file);
(void)release_writedata(file,dir,len);
(void)release_writestring(file,files->name);
(void)release_writedata(file,seperator,sizeof(seperator)-1);
(void)release_writedata(file,separator,sizeof(separator)-1);
first = TRUE;
for( i = 0 ; i < files->count ; i ++ ) {
if( !first )
......
......@@ -724,23 +724,23 @@ retvalue splitlist(struct strlist *from,
/* * Iterator over components to update * */
r = RET_NOTHING;
for( i = 0 ; i < list->count ; i++ ) {
const char *item,*seperator;
const char *item,*separator;
char *origin,*destination;
item = list->values[i];
// TODO: isn't this broken for the !*(dest+1) case ?
if( (seperator = strchr(item,'>')) == NULL ) {
if( (separator = strchr(item,'>')) == NULL ) {
destination = strdup(item);
origin = strdup(item);
} else if( seperator == item ) {
destination = strdup(seperator+1);
origin = strdup(seperator+1);
} else if( *(seperator+1) == '\0' ) {
destination = strndup(item,seperator-item);
origin = strndup(item,seperator-item);
} else if( separator == item ) {
destination = strdup(separator+1);
origin = strdup(separator+1);
} else if( *(separator+1) == '\0' ) {
destination = strndup(item,separator-item);
origin = strndup(item,separator-item);
} else {
origin = strndup(item,seperator-item);
destination = strdup(seperator+1);
origin = strndup(item,separator-item);
destination = strdup(separator+1);
}
if( origin == NULL || destination == NULL ) {
free(origin);free(destination);
......
......@@ -734,7 +734,7 @@ static retvalue writegz(struct filetorelease *f, const char *data, size_t len) {
}
/* as we start with some data to process, Z_BUF_ERROR
* should only happend when no output is possible, as that
* gets possible again it should finaly produce more output
* gets possible again it should finally produce more output
* and return Z_OK and always terminate. Hopefully... */
} while( zret == Z_BUF_ERROR
|| ( zret == Z_OK && f->gzstream.avail_in != 0));
......
......@@ -128,7 +128,7 @@ static inline retvalue containskey(const char *key, const char *fingerprint) {
if( *keypart == '|' )
keypart++;
else {
fprintf(stderr,"Space seperated values in keyid '%s'!\n(Use | symbols to seperate multiple possible keys!)\n",key);
fprintf(stderr,"Space separated values in keyid '%s'!\n(Use | symbols to separate multiple possible keys!)\n",key);
return RET_ERROR;
}
}
......
......@@ -29,7 +29,7 @@ retvalue strlist_adduniq(struct strlist *strlist,/*@only@*/char *element);
/* like strlist_add, but strdup it first */
retvalue strlist_add_dup(struct strlist *strlist, const char *todup);
/* print a space seperated list of elements */
/* print a space separated list of elements */
retvalue strlist_fprint(FILE *file,const struct strlist *strlist);
/* duplicate with content */
......
......@@ -1128,7 +1128,7 @@ static retvalue verify(const char *changesfilename, struct changes *changes) {
name = NULL;
namelen = 0;
fprintf(stderr,
"Warning: '%s' does not contain a '_' seperating name and version!\n",
"Warning: '%s' does not contain a '_' separating name and version!\n",
file->basename);
}else {
name = file->basename;
......@@ -1152,7 +1152,7 @@ static retvalue verify(const char *changesfilename, struct changes *changes) {
#endif
if( name != NULL )
fprintf(stderr,
"ERROR: '%s' does not contain a '_' seperating name and version!\n",
"ERROR: '%s' does not contain a '_' separating name and version!\n",
file->basename);
} else {
version = p+1;
......
......@@ -1233,7 +1233,7 @@ static retvalue calllisthook(const char *listhook,struct update_index *index) {
return RET_ERROR;
}
} else {
fprintf(stderr,"Listhook terminated abnormaly. (status is %x)!\n",status);
fprintf(stderr,"Listhook terminated abnormally. (status is %x)!\n",status);
return RET_ERROR;
}
}
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment