$HeadURL$ $LastChangedRevision$ for 1.99.11 ########### Move the upgrade functions into a new file; having them in the one I'm always editing makes possible to apply global changes that should not be applied to those functions. This fails but should always succeed: spirali# paa editdb paa: ERROR: database schema is too old (do you need to run 'paa upgrade'?) spirali# This fails: spirali# paa -v access ALL-REPOS paa: INFO: centos: accessing ... /usr/include/paa/directives-all.sh: line 1844: access_: command not found paa: ERROR: application's entry function (paa) failed spirali# (I cloned fiori's database and changed all the hostname everywhere in the db in order to get to the point where I could run the above command.) Even with 'ALL-REPOS' replaced by 'centos' (which is not an appropriate repo for this host, but should be detected as such) produces the same error. for 2.0 ####### Nothing! (Deliberately! It's just a cosmetic version bump!) for post-2.0 ############ What functions in paa.sh can be moved into ade? Would be nice if an insert didn't produce these repeated messages: epilogue-pkgctrl.pasta-net: INFO: paa_1.99.3-1_all.deb: inserting into lenny,squeeze,wheezy ... paa: INFO: paa_1.99.3-1_all.deb: analysing ... paa: INFO: localpublic-deb: paa_1.99.3-1_all.deb: copying to repository ... paa: INFO: localpublic-deb: paa_1.99.3-1_all.deb: copying to repository ... paa: INFO: localpublic-deb: paa_1.99.3-1_all.deb: copying to repository ... paa: INFO: localpublic-deb: paa_1.99.3-1_all.deb: copying to repository ... paa: INFO: localpublic-deb: paa_1.99.3-1_all.deb: copying to repository ... paa: INFO: localpublic-deb: paa_1.99.3-1_all.deb: copying to repository ... (Submit it as a bug report later) Repos which are owned, should not be capable of being mirrored or frozen or anything else. Those are developer roles. It would be nice if the repository server could serve the list of respositories to the server (possibly by http) in a format that allowed the client to add them all to its own sqlite database.