This will also create the pbuilder environment if not already existing.
7. manual changes - create a gpg key for your packages
+
gpg --genkey
+
and read through 'man gpg-agent' to set it up. Add that key to the
pbuilder environment so the packages you signed and uploaded are
indeed acceptable to the distribution.
- pbuilder --login \
- --basetgz /var/cache/pbuilder/base-cran2deb-debian-amd64.tgz \
- --save-after-login
+ sudo pbuilder --login --save-after-login \
+ --basetgz /var/cache/pbuilder/base-cran2deb-debian-amd64.tgz
Once logged in, in a separate shell perform as cran2deb user a
creates a new pbuilder environment and will require the
adding of keys again.
+10. Educate yourself about the schema of the sqlite3 database,
+ which is likely to reside at ~/cache/cran2deb.db
+ and is directly accessible via calling from the
+ UNIX command line 'sqlite3 ~/cache/cran2deb.db' .
+
+ The sqlite3 shell will directly attach to the database.
+ See the tables first
+
+ sqlite> .tables
+ blacklist_packages debian_dependency license_override
+ builds forced_depends packages
+ database_versions license_hashes sysreq_override
+
+ and then the schema of the one or other table of interest, e.g.
+
+ sqlite> .schema debian_dependency
+ CREATE TABLE debian_dependency (
+ id INTEGER PRIMARY KEY AUTOINCREMENT NOT NULL,
+ alias TEXT NOT NULL,
+ build INTEGER NOT NULL,
+ debian_pkg TEXT NOT NULL ,
+ UNIQUE (alias,build,debian_pkg) );
+ sqlite> .schema forced_depends
+ CREATE TABLE forced_depends (
+ r_name TEXT NOT NULL,
+ depend_alias TEXT NOT NULL,
+ PRIMARY KEY (r_name,depend_alias) );
+ sqlite> .schema blacklist_packages
+ CREATE TABLE blacklist_packages (
+ package TEXT PRIMARY KEY NOT NULL,
+ nonfree INTEGER NOT NULL DEFAULT 0,
+ obsolete INTEGER NOT NULL DEFAULT 0,
+ broken_dependency INTEGER NOT NULL DEFAULT 0,
+ unsatisfied_dependency INTEGER NOT NULL DEFAULT 0,
+ breaks_cran2deb INTEGER NOT NULL DEFAULT 0,
+ other INTEGER NOT NULL DEFAULT 0,
+ explanation TEXT NOT NULL);
+ sqlite> .schema builds
+ CREATE TABLE builds (
+ id INTEGER PRIMARY KEY AUTOINCREMENT NOT NULL,
+ system TEXT NOT NULL ,package TEXT NOT NULL,
+ r_version TEXT NOT NULL ,deb_epoch INTEGER NOT NULL,
+ deb_revision INTEGER NOT NULL ,db_version INTEGER NOT NULL,
+ date_stamp TEXT NOT NULL ,time_stamp TEXT NOT NULL,
+ scm_revision TEXT NOT NULL ,success INTEGER NOT NULL,
+ log TEXT,
+ UNIQUE(package,system,r_version,deb_epoch,deb_revision,db_version));
+ sqlite> .schema database_versions
+ CREATE TABLE database_versions (
+ version INTEGER PRIMARY KEY AUTOINCREMENT NOT NULL,
+ version_date INTEGER NOT NULL,
+ base_epoch INTEGER NOT NULL );
+ sqlite> .schema license_hashes
+ CREATE TABLE license_hashes (
+ name TEXT NOT NULL,
+ sha1 TEXT PRIMARY KEY NOT NULL );
+ sqlite> .schema license_override
+ CREATE TABLE license_override (
+ name TEXT PRIMARY KEY NOT NULL,
+ accept INT NOT NULL );
+ sqlite> .schema packages
+ CREATE TABLE packages (
+ package TEXT PRIMARY KEY NOT NULL,
+ latest_r_version TEXT );
+ sqlite> .schema sysreq_override
+ CREATE TABLE sysreq_override (
+ depend_alias TEXT NOT NULL,
+ r_pattern TEXT PRIMARY KEY NOT NULL );
+
+ The sqlite3 shell allows to modify all those entries. For a
+ restart with defaults entries distributed via svn, run "cran2deb
+ repopulate". To update the data stored in svn, change to the data
+ directory and run "./pull". Caveat, prior to that, make sure the
+ license data was read in by you. This is not performed automatically in
+ repopulate, a bit to protect us and stress that everyone is reponsible
+ for their own respective interpretation of a license's constraints
+ and the effect on a redistribution of source and/or binary.
+
+11.Add licenses the way you think it is right. The script in
+ 'exec/repopulate' may offer ideas on how to mass-include what
+ you find in the svn. For new entries, you may prefer using
+ 'cran2deb' license that expects to learn from from the command
+ line how to treat individual licenses:
+
+ $ cran2deb license accept akima
+ I: cran2deb svn: 344 building for debian-amd64 at 2011-02-11 18:46:21
+ N: adding akima accept? TRUE
+
+ $ cran2deb license hash_sha1 akima 485316717b03afbd6d20f7810f9123b4445c8660
+ I: cran2deb svn: 344 building for debian-amd64 at 2011-02-11 18:46:37
+ N: adding hash 485316717b03afbd6d20f7810f9123b4445c8660 for akima
+
+ $ cran2deb license ls
+ I: cran2deb svn: 344 building for debian-amd64 at 2011-02-11 18:46:53
+ accept akima
+ hash_sha1 akima 485316717b03afbd6d20f7810f9123b4445c8660
+
+ What happens here is that a license file was read and if that is
+ having the same hash value, then it is mapped to the license 'akima'.
+ The license 'akima' then again is told to be acceptable. It happened
+ here that the license is of the same name as the package that it
+ occurs in.
+
To think about
1. After several updates of the repository, we have many outdated
- Debian packages in the archive cache. I prefer removing them
- with a skriptlet like
+ Debian packages in the pbuilder's archive cache. I prefer removing
+ them with a skriptlet like
cd /var/cache/apt/archives \
&& for i in $(ls | cut -f1 -d_ | uniq -c | egrep -v "^ *1 " | sed -e 's/^\s*[0-9]*\s//')
apt-cache search r-cran-$a
done
+3. If running on a separate partition, the place reserved for cran2deb is not unlikely
+ to exceed your expectation, especially when also running BioConductor. You may
+ consider running cran2deb on logical volumes, like by LVM. Together with a file
+ system that allows its extension, the process is rather straight forward:
+
+ # lvextend -L+40G /dev/vg0/cran2deb
+ Extending logical volume cran2deb to 115.04 GiB
+ Logical volume cran2deb successfully resized
+ # xfs_growfs /dev/vg0/cran2deb
+ meta-data=/dev/dm-6 isize=256 agcount=21, agsize=983040 blks
+ = sectsz=512 attr=2
+ data = bsize=4096 blocks=19671040, imaxpct=25
+ = sunit=0 swidth=0 blks
+ naming =version 2 bsize=4096 ascii-ci=0
+ log =internal bsize=4096 blocks=2560, version=2
+ = sectsz=512 sunit=0 blks, lazy-count=1
+ realtime =none extsz=4096 blocks=0, rtextents=0
+ data blocks changed from 19671040 to 30156800
+
+ The directory does not even need to unmounted for that with XFS.
+
+
To debug:
$ cran2deb help
To improve:
* The runtime dependencies for Rgraphviz are outdated (there is no libraphviz4
- any more). To get the package run (theoretically) this was not changed
- to "alias_run libgraphviz libgraphviz-dev" but this can certainly be
- optimised.
+ any more). To get the package run this was not changed to "alias_run
+ libgraphviz libgraphviz-dev" but this can certainly be optimised
+ towards something less resource-hungry.
Concerning data/:
pull that, when run from the data directory will recreate all the files from
the database EXCEPT for the licenses. The licenses cannot be recreated because
licenses can be based on one-way hashes. This process could certainly be
-improved.
+improved. But one gets the hang of it ater a while. So don't despair.
projects / cran2deb.git / blobdiff