Quoting "anatoly techtonik" <techto...@gmail.com>:
1. Trac is not a package - it's an application.
Inside of Debian, applications, libraries, and many other things come as "package" as we call it. In Debian, trac is a package.
If there will be a problem in one of the files that shipped with Trac sources - it is a Trac bug.
And maybe 58 other Debian packages would be affected in the case of jQuery.
If in case of globally installed packages dependency analysis is a good (must) thing, then for standalone application autopsies contribute nothing to the quality of Debian releases. I would say quite contrary. In Python world there is a very nice thing called Virtualenv that was invented for Python Applications because global packages create stability mess.
His reminds me of an operating systems, I had to use sometimes, where every application came with their local copy of libraries etc. To me it sounds, like you prefer a manuall Trac installation from source, and Debian does not prevent this. Using the packaged version of Trac is an offer, not more.
2. Thing to consider. When you create Environment and "deploy" it with trac-admin (to generate fastcgi/mod_wsgi scripts) - copies of static resources for web-server, including JavaScript won't be updated when you fix your security package. Right now nobody handles this, but only trac-admin "upgrade" could potentially heal it given it will be able to detect old and new jQuery version in user Environment.
Trac works fine without having such copies. I really would not recommend this style of installation. Exactly for the reasons you mentioned. I use symlinks and shared directories.
Martin, you are wrong. http://trac.edgewall.org/wiki/TracDev/ApiChanges/0.11#NewDependencies http://trac.edgewall.org/wiki/TracDev/JavaScript#jQuery
But trac works perfectly well with any kind of JavaScript. (I have JavaScript disabled for anything, but some sites.)
Does that mean people won't be able to install Trac 0.12 on Lenny?
No. It would mean that two libjs-jquery packages would exist in parallel, one with the latest 1.2, the other with the latest 1.3 version and that Trac 0.11 could use one, 0.12 the other.
Consider that when people jump from Trac 0.10 to 0.11 they usually create two instances of Trac before switch and new one usually should be run on the same server. That was true for trac-hacks.org (there virtualenv was used) and that is true with me too, except that I am constrained to use Debian packages and therefore used two Debian servers. Admins would really appreciate an ability to have two Trac major versions on the same server.
Yes. I fear, we don't have the human power to maintain both 0.11 and 0.12 in parallel in Debian. OTOH, it would be cool to have 0.12 in the next Debian release, but of course we can't drop 0.11 at the moment, as too many people use it.
I fixed it with "aptitude install libjs-jquery=1.2.6" and it works for me.
This works, because you have the old jQuery version in one of your deb repositories. For most users this will not work with the next Debian release. Which plugin(s) exactly did not work with libjs-jquery >= 1.3? Do you have any further information what the problem is/was?
Sorry for the ignorance, but I still didn't read Debian Bible and ITP, RFP, WNPP and the whole bug-entering process is too way complicated to squeeze into my head at once.
I very well understand this! When/if it becomes clear to me, that a libjs-jquery-1.2 package makes sense, I will file the report. Today we will have 30°C, so I will postpone this a little bit :~) -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
