REPREPRO

NAME

SYNOPSIS

reprepro [ options ] command [ per-command-arguments ]  

DESCRIPTION

WARNING: Some functions are still quite experimental and not very heavily tested. Be careful.

Former working title of this program was mirrorer.  

GLOBAL OPTIONS

-h --help

Displays a short list of options and commands with description.

-v, -V, --verbose

Be more verbose. Can be applied multiple times. One upcase -V counts as five lowercase -v.

-f, --force

This option is ignored, as it no longer exists.

-b, --basedir basedir

Sets the base-dir of the repository to manage, i.e. where the pool/ subdirectory resides. If none is supplied and the REPREPRO_BASE_DIR environment variable is not set either, the current directory will be used.

--confdir confdir

Sets the directory where the configuration is searched in.

If none is given, basedir/conf will be used.

--distdir distdir

Sets the directory to generate index files relatively to. (i.e. things like Packages.gz, Sources.gz and Release.gpg)

If none is given, basedir/dists is used.

Note: apt has dists hard-coded in it, so this is mostly only useful for testing or when your webserver pretends another directory structure than your physical layout.

Warning: Beware when changing this forth and back between two values not ending in the same directory. Reprepro only looks if files it wants are there. If nothing of the content changed and there is a file it will not touch it, assuming it is the one it wrote last time, assuming any different --distdir ended in the same directory. So either clean a directory before setting --distdir to it or do an export with the new one first to have a consistent state.

--dbdir dbdir

Sets the directory where reprepro keeps its databases.

If none is given, basedir/db is used.

Note: This is permanent data, no cache. One has almost to regenerate the whole repository when this is lost.

--listdir listdir

Sets the directory where downloads it downloads indices to when importing from other repositories. This is temporary data and can be safely deleted when not in an update run.

If none is given, basedir/lists is used.

--overridedir overridedir

Sets the directory where specified override-files will be searched in if they do not start with a slash. If none is given, basedir/override is used.

--methoddir methoddir

Look in methoddir instead of /usr/lib/apt/methods for methods to call when importing from other repositories.

-C, --component component

Specify a component to force into, to remove from or to list only.

-A, --architecture architecture

Specify an architecture to only include into, remove from or list.

When including this does not lead to packages in the wrong architecture but will restrict effect to this architecture. This allows e.g. different versions of an Architecture: all -package in different architectures of the same distribution.

-T, --type dsc|deb|udeb

Specify which type of files to include, remove or list.

-S, --section section

Overrides the section of inclusions. (Also override possible override files)

-P, --priority priority

Overrides the priority of inclusions. (Also override possible override files)

--export=(never|changed|normal|force)

This option specify whether and how the high level actions (e.g. install, update, pull, delete) should export the index files of the distributions they work with.

--export=normal (default)

In this mode every distribution the action handled without error will be exported.
Note that only missing files and files whose intended content changed between before and after the action will be written. To get a guaranteed current export, use the export action.

--export=changed

Like normal, but do not look for missing files in distributions where nothing changed.

--export=force

Like normal, but exporting also happens for distributions where some error occurred.

--export=never

No index files are exported. You will have to call export later.
Note that you most likely additionally need the --keepunreferenced option, if you do want some of the files pointed to by the untouched index files to vanish.

--ignore=what

Ignore errors of type what. See the section ERROR IGNORING for possible values.

--nolistsdownload

When running update or checkupdate do not download any Release or index files (and also do not check them). This is hardly useful except when you just run one of those command for the same distributions.

--keepunreferencedfiles

Do not delete files that are no longer used because the package they are from is deleted/replaced with a newer version from the last distribution it was in.

--keepunneededlists

Do not try to delete files from lists/ before updating, that seem to belong to one of the updated distributions but will not be needed. Those file may happen to exist when you removed some Update: rule or changed Components/Architectures/... . This is mostly only useful if you want to temporarily disable some update rule and want to avoid downloading their index files again when you read it later.

--keepdirectories

Do not try to rmdir parent directories after files or directories have been removed from them. (Do this if your directories have special permissions you want keep, do not want to be pestered with warnings about errors to remove them, or have a buggy rmdir call deleting non-empty directories.)

--ask-passphrase

Ask for passphrases when signing things and one is needed. This is a quick and dirty implementation using the obsolete getpass(3) function with the description gpgme is supplying. So the prompt will look quite funny and support for passphrases with more than 8 characters depend on your libc. I suggest using gpg-agent or something like that instead.

--noskipold

When updating do not skip targets where no new index files and no files marked as already processed are available.

If you changed a script to preprocess downloaded index files or changed a Listfilter, you most likely want to call reprepro with --noskipold.

COMMANDS

export [ codenames ]

Generate all index files for the specified distributions. (For all if none is specified). This will normally be done automatically and more fine-tuned when including or removing packages, so seldom needed; but is nevertheless a good way to see if a new distributions config-file does the expected things.

createsymlinks [ --delete ] [ codenames ]

Creates suite symbolic links in the dists/-directory pointing to the corresponding codename.

It will not create links, when multiple of the given codenames would be linked from the same suite name, or if the link already exists (though when --delete is given it will delete already existing symlinks)

list codename packagename

List all packages (source and binary, except when -T or -A is given) with the given name in all components (except when -C is given) and architectures (except when -A is given) of the specified distribution.

listfilter codename condition

as list, but does not list a single package, but all packages matching the given condition.

reprepro -b . -T deb listfilter test2 'Source (==blub) | ( !Source , Package (==blub) )' will e.g. find all .deb Packages with Source blub. (Except those also specifying a version number with its Source, as binary and source version differ).

remove codename package name

same as list, but remove instead of list.

update [ codenames ]

Sync the specified distributions (all if none given) as specified in the config with their upstreams. See the description of conf/updates below.

iteratedupdate [ codenames ] (EXPERIMENTAL!)

This is an experimental variant of update, that processes the distributions and targets within them one by one, resulting in much lower memory consumption for an update of multiple distributions.

checkupdate [ codenames ]

Same like update, but will show what it will change instead of actually changing it.

predelete [ codenames ]

This will determine which packages a update would delete or replace and remove those packages. This can be useful for reducing space needed while upgrading, but there will be some time where packages are vanished from the lists so clients will mark them as obsolete. 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 something similar. So be careful when using this option or better get some more space so that update works.

pull [ codenames ]

pull in newer packages into the specified distributions (all if none given) from other distributions in the same repository. See the description of conf/pulls below.

checkpull [ codenames ]

Same like pull, but will show what it will change instead of actually changing it.

includedeb codename .deb-filename

Include the given binary Debian package (.deb) in the specified distribution, applying override information and guessing all values not given and guessable.

includeudeb codename .deb-filename

Same like includedeb, but for .udeb files.

includedsc codename .dsc-filename

Include the given Debian source package (.dsc, including other files like .orig.tar.gz, .tar.gz and/or .diff.gz) in the specified distribution, applying override information and guessing all values not given and guessable.

Note that as .dsc files do not contain section or priority, but the Sources.gz file does, you have to either specify a DscOverride or given them via -S and -P

include codename .changes-filename

Include in the specified distribution all packages found and suitable in the .changes file, applying override information guessing all values not given and guessable.

check [ codenames ]

Check if all packages in the specified distributions have all files needed properly registered.

checkpool [ fast ]

Check if all files believed to be in the pool are actually still there and have the known md5sum. When fast is specified md5sum is not checked.

rereference

Forget which files are needed and recollect this information.

dumpreferences

Print out which files are marked to be needed by whom.

dumpunreferenced

Print a list of all filed believed to be in the pool, that are not known to be needed.

deleteunreferenced

Remove all known files (and forget them) in the pool not marked to be needed by anything.

reoverride [ codenames ]

Reapply the override files to the given distributions (Or only parts thereof given by -Af,-C or -T).

Note: only the control information is changed. Changing a section to a value, that would cause an other component to be guessed, will not cause any warning.

dumptracks [ codenames ]

Print out all information about tracked source packages in the given distributions.

retrack [ codenames ]

Recreate a tracking database for the specified distributions. As this only takes information from the Indices into account, this will loose all information about older packages or changes files.

cleartracks [ codenames ]

Removes all source package tracking information for the given distributions.

removetrack codename sourcename version

Remove the trackingdata of the given version of a given sourcepackage from a given distribution. This also removes the references for all used files.

copy destination-codename source-codename packages...

Copy the given packages from one distribution to another. No overrides are read, nothing is changed.

clearvanished

Remove all package databases that no longer appear in conf/distributions. If --delete is specified, it will not stop if there are still packages left. Even without --delete it will unreference files still marked as needed by this target. (Use --keepunreferenced to not delete them if that was the last reference.)

Do not forget to remove all exported package indices manually.

internal commands

_detect [ filekeys ]

Look for the files, which filekey is given as argument or as a line of the input (when run without arguments), and calculate their md5sum and add them to the list of known files. (Warning: this is a low level operation, no input validation or normalization is done.)

_forget [ filekeys ]

Like _detect but remove the given filekey from the list of known files. (Warning: this is a low level operation, no input validation or normalization is done.)

_listmd5sums

Print a list of all known files and their md5sums.

_addmd5sums

Add information of known files (without any check done) in the strict format of _listmd5sums output (i.e. don't dare to use a single space anywhere more than needed).

_dumpcontents identifier

Printout all the stored information of the specified part of the repository. (Or in other words, the content the corresponding Packages or Sources file would get)

_addreference filekey identifier

Manually mark filekey to be needed by identifier

_removereferences identifier

Remove all references what is needed by identifier.

__extractcontrol.deb-filename

Look what reprepro believes to be the content of the control file of the specified .deb-file.

CONFIG FILES

If an file options exists, it is parsed line by line. Each line can be the long name of an command line option (without the --) plus an argument, where possible. Those are handled as if they were command line options given before (and thus lower priority than) any other command line option. (and also lower priority than any environment variable).

To allow command line options to override options file options, most boolean options also have a corresponding form starting with --no.

(The only exception is when the path to look for config files changes, the options file will only opened once and of course before any options within the options file are parsed.)

The file distributions is always needed and describes what distributions to manage, while updates is only needed when syncing with external repositories.

The last both are in the format control files in Debian are in, i.e. paragraphs separated by blank lines consisting of fields. Each field consists of an fieldname, followed by a colon, possible whitespace and the data. A field ends with a newline not followed by a space or tab.  

conf/distributions

Codename

This required field is the unique identifier of a distribution and used as directory name within dists/ It is also copied into the Release files.

Suite

This optional field is simply copied into the Release files. In Debian it contains names like stable, testing or unstable. To create symlinks from the Suite to the Codename, use the createsymlinks command of reprepro.

Version

This optional field is simply copied into the Release files.

Origin

This optional field is simply copied into the Release files.

Label

This optional field is simply copied into the Release files.

NotAutomatic

This optional field is simply copied into the Release files. (The value is handled as arbitrary string, though anything but yes does make much sense right now.)

Description

This optional field is simply copied into the Release files.

Architectures

This required field lists the binary architectures within this distribution and if it contains source (i.e. if there is an item source in this line this Distribution has source. All other items specify things to be put after "binary-" to form directory names and be checked against "Architecture:" fields.)

This will also be copied into the Release files. (With exception of the source item, which will not occur in the topmost Release file whether it is present here or not)

Components

This required field lists the component of a distribution. See GUESSING for rules which component packages are included into by default. This will also be copied into the Release files.

UDebComponents

Components with a debian-installer subhierarchy containing .udebs. (E.g. simply "main")

Update

When this field is present, it describes which update rules are used for this distribution. There also can be a magic rule minus ("-"), see below.

Pull

When this field is present, it describes which pull rules are used for this distribution. Pull rules are like Update rules, but get their stuff from other distributions and not from external sources. See the description for conf/pulls.

SignWith

When this field is present, a Release.gpg file will be generated. If the value is "yes" and "default", the default key is used. Otherwise the value will be given to libgpgme to determine to key to use. (That should be roughly the one gpg --list-secret-keys value would output). This key should either have no passphrase, you need to specify --ask-passphrase or use gpg-agent.

DebOverride

When this field is present, it describes the override file used when including .deb files.

UDebOverride

When this field is present, it describes the override file used when including .deb files.

DscOverride

When this field is present, it describes the override file used when including .dsc files.

DebIndices, UDebIndices, DscIndices

Choose what kind of Index files to export. The first part describes what the Index file shall be called. The second argument determines the name of a Release file to generate or not to generate if missing. Then at least one of ".", ".gz" or ".bz2" specifying whether to generate uncompressed output, gzipped output, bzip2ed output or any combination. (bzip2 is only available when compiled with bzip2 support, so it might not be available when you compiled it on your own). If an argument not starting with dot follows, it will be executed after all index files are generated. (See the examples for what argument this gets). The default is:
DebIndices Packages Release . .gz
UDebIndices Packages . .gz
DscIndices Sources Release .gz

Contents

Enable the creation of Contents files listing all the files within the binary packages of a distribution. (Which is quite slow, you have been warned).

The first argument is the rate at which to extract the files from packages. If it is 1, every file will be processed. If it is 2, at least half of the uncached files and at most half of all files are read to extract their filelist. 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 separated list of options can be given. If there is a udebs keyword, .udebs are also listed (in a file called uContents-architecture.) If there is a nodebs keyword, .debs are not listed. (Only usefull together with udebs) If there is at least one of the keywords ., .gz and/or .bz2, the Contents files are written uncompressed, gzipped and/or bzip2ed instead of only gzipped.

ContentsArchitectures

Limit generation of Contents files to the architectures given. If this field is not there or empty, all architectures are processed.

ContentsComponents

Limit what components are processed for the Contents files to the components given. If this field is not there or empty, all components are processed.

ContentsUComponents

Limit what components are processed for the uContents files to the components given. If this field is not there or empty, all components are processed. (Note unless you specify udebs in the Contents: line, no udeb Components are processed at all.)

Uploaders

Specified a file (relative to confdir if not starting with a slash) to specify who is allowed to upload packages. With this there are no limits, and this file can be ignored via --ignore=uploaders. See the section UPLOADERS FILES below.

Tracking

Enable the (experimental) tracking of source packages. The argument list needs to contain exactly one of the following:
keep Keeps all files of a given source package, until that is deleted explicitly via removetrack. This is currently the only possibility to keep older packages around when all indices contain newer files.
all Keep all files belonging to a given source package until the last file of it is no longer used within that distribution.
minimal Remove files no longer included in the tracked distribution. (Remove changes and includebyhand files once no file is in any part of the distribution).
And any number of the following (or none):
includechanges Add the .changes file to the tracked files of an source package. Thus it is also put into the pool.
includebyhand Not yet implemented.
ambargoalls Not yet implemented. keepsources Even when using minimal mode, do not remove source files until no file is needed any more. needsources Not yet implemented.

conf/updates

Name

The name of this update-upstream as it can be used in the Update field in conf/distributions.

Method

An URI as one could also give it apt, e.g. http://ftp.debian.de/debian which is simply given to the corresponding apt-get method. (So either apt-get has to be installed, or you have to point with --methoddir to a place where such methods are found.

Fallback

(Still experimental:) A fallback URI, where all files are tried that failed the first one. They are given to the same method as the previous URI (e.g. both http://), and the fallback-server must have everything at the same place. No recalculation is done, but single files are just retried from this location.

Config

This can contain any number of lines, each in the format apt-get --option would expect. (Multiple lines - as always - marked with leading spaces). For example: Config: Acquire::Http::Proxy=http://proxy.yours.org:8080

Suite

The suite to update from. If this is not present, the codename of the distribution using this one is used. Also "*/whatever" is replaced by "<codename>/whatever"

Components

The components to update. Each item can be either the name of a component or a pair of a upstream component and a local component separated with ">". (e.g. "main>all contrib>all non-free>notall") Items with a local part are ignored. If no items are there all from the updated distribution are taken. (Use some non existing like "none", if you want none).

Architectures

The architectures to update. If omitted all from the distribution to update from. (As with components, you can use ">" to download from one Architecture and add into an other one. (This only determine in which Package list they land, it neither overwrites the Architecture line in its description, nor the one in the filename determined from this one. In other words, it is no really useful without additional things)

UDebComponents

Like Components but for the udebs.

VerifyRelease

Download the Release.gpg file and check if it is a signature of the Releasefile with the key given here. (In the Format as "gpg --with-colons --list-key" prints it, i.e. the last 16 hex digits of the fingerprint) Multiple keys can be specified by separating them with a "|" sign. Then finding a signature from one of the will suffice.

IgnoreRelease

If this is present, no Release file will be downloaded and thus the md5sums of the other index files will not be checked.

FilterFormula

This can be a formula to specify which packages to accept from this source. The format is misusing the parser intended for Dependency lines. To get only architecture all packages use "architecture (== all)", to get only at least important packages use "priority (==required) | priority (==important)".

FilterList

This takes at least two arguments: The first one is the default action when something is not found, the then a list of filenames (relative to --confdir, if not starting with a slash), in the format of dpkg --get-selections and only packages listed in there as install will be installed. Things listed as deinstall or purge or nonexistent will be treated like not being known. A package being hold will not be upgraded but also not downgraded or removed. To abort the whole upgrade/pull if a package is available, use error.

ListHook

If this is given, it is executed for all downloaded index files with the downloaded list as first and a filename that will be used instead of this. (e.g. "ListHook: /bin/cp" works but does nothing.)

conf/pulls

Each rule consists out of the following fields:

Name

The name of this pull rule as it can be used in the Pull field in conf/distributions.

From

The codename of the distribution to pull packages from.

Components

The components of the distribution to get from. 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).

Architectures

The architectures to update. If omitted all from the distribution to pull from.

UDebComponents

Like Components but for the udebs.

FilterFormula

FilterList

The same as with update rules.

OVERRIDE FILES

packagename field name new value

For example:
kernel-image-2.4.31-yourorga Section protected/base
kernel-image-2.4.31-yourorga Priority standard
kernel-image-2.4.31-yourorga Maintainer That's me <me@localhost>
reprepro Priority required

All fields of a given package will be replaced by the new value specified in the override file. While the field name is compared case-insensitive, it is copied in exactly the form in the override file there. (Thus I suggest to keep to the exact case it is normally found in index files in case some other tool confuses them.) More than copied is the Section header (unless -S is supplied), which is also used to guess the component (unless -C is there). There is no protection against changing headers like Package, Filename, Size or MD5sum, though changing these functional fields may give the most curious results. (Most likely reprepro may error out in future invocations).  

UPLOADERS FILES

ERROR IGNORING

brokenold (hopefully never seen)

If there are errors parsing an installed version of package, do not error out, but assume it is older than anything else, has not files or no source name.

brokensignatures

If a .changes or .dsc file contains at least one invalid signature and no valid signature (not even expired or from an expired or revoked key), reprepro assumes the file got corrupted and refuses to use it unless this ignore directive is given.

brokenversioncmp (hopefully never seen)

If comparing an old and a new version fails, assume the new one is newer.

doublefield (better comment the second one)

Ignore doubled fields in the config files, instead of refusing to run then. In general the second one should be ignored then, but perhaps sometimes the first one. So I hope you know what you do.

emptyfilenamepart (insecure)

Allow strings to be empty that are used to construct filenames. (like versions, architectures, ...)

extension

Allow to includedeb files that do not end with .deb, to includedsc files not ending in .dsc and to include files not ending in .changes.

forbiddenchar (insecure)

Do not insist on Debian policy for package and source names and versions. Thus allowing all 7-bit characters but slashes (as they would break the file storage) and things syntactically active (spaces, underscores in filenames in .changes files, opening parentheses in source names of binary packages). To allow some 8-bit chars additionally, use 8bit additionally.

8bit (more insecure)

Allow 8-bit characters not looking like overlong UTF-8 sequences in filenames and things used as parts of filenames. Though it hopefully rejects overlong UTF-8 sequences, there might be other characters your filesystem confuses with special characters, thus creating filenames possibly equivalent to /mirror/pool/main/../../../etc/shadow (Which should be save, as you do not run reprepro as root, do you?) or simply overwriting your conf/distributions file adding some commands in there. So do not use this if you are paranoid, unless you are paranoid enough to have checked the code of your libs, kernel and filesystems.

ignore (for forward compatibility)

Ignore unknown ignore types given to --ignore.

malformedchunk (I hope you know what you do)

Do not stop when finding a line not starting with a space but no colon(:) in it. These are otherwise rejected as they have no defined meaning.

missingfield (save to ignore)

Ignore missing fields in a .changes file that are only checked but not processed. Those include: Format, Date, Urgency, Maintainer, Description, Changes

missingfile (might be insecure)

When including a .dsc file from a .changes file, try to get files needed but not listed in the .changes file (e.g. when someone forgot to specify -sa to dpkg-buildpackage) from the directory the .changes file is in instead of erroring out. (--delete will not work with those files, though.)

overlongcomments (I hope you know what you do)

Allow overlong comments. That is a line started with a hash(#) followed by lines starting with spaces. By default reprepro errors out in that case, as marking every line as comment is as easy and people might try to comment a single line within a multi-line header (which does not work but makes all the rest a comment).

shortkeyid (insecure)

Allow gpg-keys to be specified with less than 8 hexdigits of their fingerprint.

spaceonlyline (I hope you know what you do)

Allow lines containing only (but non-zero) spaces. As these do not separate chunks as thus will cause reprepro to behave unexpected, they cause error messages by default.

surprisingarch

Do not reject a .changes file containing files for a architecture not listed in the Architecture-header within it.

surprisingbinary

Do not reject a .changes file containing .deb files containing packages whose name is not listed in the "Binary:" header of that changes file.

unknownfield (for forward compatibility)

Ignore unknown fields in the config files, instead of refusing to run then.

unusedarch (save to ignore)

No longer reject a .changes file containing no files for any of the architectures listed in the Architecture-header within it.

wrongdistribution (save to ignore)

Do not error out if a .changes file is to be placed in a distribution not listed in that files' Distributions: header.

wrongsourceversion

Do not reject a .changes file containing .deb files with a different opinion on what the version of the source package is.
(Note: reprepro only compares literally here, not by meaning.)

wrongversion

Do not reject a .changes file containing .dsc files with a different version.
(Note: reprepro only compares literally here, not by meaning.)

GUESSING

Thus having specified the components: "main non-free contrib non-US/main non-US/non-free non-US/contrib" should map e.g. "non-US" to "non-US/main" and "contrib/editors" to "contrib", while having only "main non-free and contrib" as components should map "non-US/contrib" to "contrib" and "non-US" to "main".

NOTE: Always specify main as the first component, if you want things to end up there.

NOTE: unlike in dak, non-US and non-us are different things...  

NOMENCLATURE

basename

the name of a file without any directory information.

filekey

the position relative to the mirrordir. (as found as "Filename:" in Packages.gz)

full filename

the position relative to /

architecture

The term like sparc, i386, mips, ... . To refer to the source packages, source is sometimes also treated as architecture.

component

Things like main, non-free and contrib (by policy and some other programs also called section, reprepro follows the naming scheme of apt here.)

section

Things like base, interpreters, oldlibs and non-free/math (by policy and some other programs also called subsections).

md5sum

The checksum of a file in the format "<md5sum of file> <length of file>"

Some note on updates

A version is not overwritten with the same version.

The magic delete rule (-).

ENVIRONMENT VARIABLES

REPREPRO_BASE_DIR

The directory in this variable is used instead of the current directory, if no -b or --basedir options are supplied.

REPREPRO_CONFIG_DIR

The directory in this variable is used when no --confdir is supplied.

BUGS

While the source part is mostly considered as the architecture source some parts may still not use this notation.  

WORK-AROUNDS TO COMMON PROBLEMS

gpgme returned an impossible condition

With the woody version this normally meant that there was no .gnupg directory in $HOME, but it created one and reprepro succeeds when called again with the same command. Since sarge the problem sometimes shows up, too. But it is no longer reproducible and it does not fix itself, neither. Try running gpg --verify file-you-had-problems-with manually as the user reprepro is running and with the same $HOME. This alone might fix the problem. It should not print any messages except perhaps
gpg: no valid OpenPGP data found.
gpg: the signature could not be verified.
if it was an unsigned file.

not including .orig.tar.gz when a .changes file's version does not end in -0 or -1

If dpkg-buildpackage is run without the -sa option to build a version with a Debian revision not being -0 or -1, it does not list the .orig.tar.gz file in the .changes file. If you want to include such a file with repepro when the .orig.tar.gz file does not already exist in the pool, reprepro will report an error. This can be worked around by:
call dpkg-buildpackage with -sa (recommended)
copy the .orig.tar.gz file to the proper place in the pool before
call reprepro with --ignore=missingfile (discouraged)

leftover files in the pool directory.

reprepro is sometimes a bit too timid of deleting stuff. When things go wrong and there have been errors it sometimes just leaves everything where it is. To see what files reprepro remembers to be in your pool directory but does not know anything needing them right know, you can use
reprepro dumpunreferenced
To delete them:
reprepro deleteunreferenced

INTERRUPTING

It only catches the first signal of each type. The second signal of a given type will terminate reprepro. You will risk database corruption and have to remove the lockfile manually.

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 interruption.  

REPORTING BUGS

COPYRIGHT

Index

NAME

SYNOPSIS

DESCRIPTION

GLOBAL OPTIONS

COMMANDS

internal commands

CONFIG FILES

conf/distributions

conf/updates

conf/pulls

OVERRIDE FILES

UPLOADERS FILES

ERROR IGNORING

GUESSING

NOMENCLATURE

Some note on updates

A version is not overwritten with the same version.

The magic delete rule (-).

ENVIRONMENT VARIABLES

BUGS

WORK-AROUNDS TO COMMON PROBLEMS

INTERRUPTING

REPORTING BUGS

COPYRIGHT