package: trac severity: wishlist The following command should be automatically executed after a new version replaces an older version: trac-admin /path/to/projenv upgrade This command will do nothing if the environment is already up-to-date so it should be safe to always run after installation. More info about this at http://projects.edgewall.com/trac/wiki/TracUpgrade
Hi, you wrote: How can the postinstall script know what "/path/to/projenv" will look like on my box? That could be even be a network-mounted path, which happens to be unmounted at the time postinst is executed. So I think this cannot be put into the postinstall script, but should instead go as a debian/NEWS.Debian entry. Regards, Bastian -- ,''`. Bastian Kleineidam : :' : GnuPG Schlüssel `. `' gpg --keyserver wwwkeys.pgp.net --recv-keys 32EC6F3E `-
Hi, you wrote: How can the postinstall script know what "/path/to/projenv" will look like on my box? That could be even be a network-mounted path, which happens to be unmounted at the time postinst is executed. So I think this cannot be put into the postinstall script, but should instead go as a debian/NEWS.Debian entry. Regards, Bastian -- ,''`. Bastian Kleineidam : :' : GnuPG Schlüssel `. `' gpg --keyserver wwwkeys.pgp.net --recv-keys 32EC6F3E `-
hello there we would never be able to upgrade all trac's environments because we don't know how many of them are in the system. Although this would be good, there is a certain dificulty in doing so. I think this would be tagged "wontfix" Best regards Luis Matos
tags 343675 + wontfix thanks hello there the changes that this bug claims will not be made. Explaintion is made in the bug report. best regards Luis Matos
retitle 343675 Document deploy and upgrade process severity 343675 normal tags 343675 - wontfix + help tags 562963 + help thanks There are some implications of using (or not using) the commands "trac-admin deploy" and "trac-admin upgrade", that must be documented in README.Debian. E.g. - After a "trac-admin /path/to/env deploy", certain files are just copied into the Trac environment. If the original files are changed (upgrade of Trac or jQuery package), the copies remain unchanged. - After upgrading the Trac package or jQuery (if used), all environments must be upgraded using "trac-admin /path/to/env upgrade" for every single environment. Unfortunately, it is very difficult to do any of the steps automatically and very likely to do it wrong. So it's better to just document the necessary steps.
Dear submitter, as the package trac has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/948052 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmaster@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)