Re: [Trac] style.css content.ticket with Jinja2

[Jonathan Laufersweiler]

>
> In the sources of a ticket package I can't find that .css anymore


Here's the stock ticket.css for the 1.4 branch:
https://trac.edgewall.org/browser/tags/trac-1.4/trac/htdocs/css/ticket.css
The others live in that directory too, rather than with their modules.

Best,
--Jonathan Laufersweiler

On Fri, Nov 15, 2019 at 8:24 AM Mo  wrote:

> Am Freitag, 15. November 2019 09:24:15 UTC+1 schrieb Jun Omae:
>
>> Try to use site_head.html file.
>> See
>> https://trac.edgewall.org/wiki/TracInterfaceCustomization#SiteAppearance.
>>
>>
>
> Ok, what do I need there to change the width. I found the example:
>
> 
> 
> 
>
> ..which makes use of the style.css again. I deployed both as static
> content. In the sources of a ticket package I can't find that .css anymore.
> What do I need to change the page width. I feel like that should be a
> configuration option anyway or should be adapting to modern screen
> resolutions.
>
> --
> You received this message because you are subscribed to the Google Groups
> "Trac Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to trac-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/trac-users/1af33081-4480-4dbe-afe7-1003e3050148%40googlegroups.com
> 
> .
>

-- 
You received this message because you are subscribed to the Google Groups "Trac 
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to trac-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/trac-users/CALF_GDHr3J-AatRNp%2BZUkb19jF7tVvy%3D8ML3LeeYtBxWasG0fg%40mail.gmail.com.

Re: [Trac] Re: Moving complete Trac installation to pip

[Jonathan Laufersweiler]

>
> You say it is also possible to use '*pip2 install .*' from the root of a
> svn or git cloned repo. That would only replace my .egg building and
> copying. I still need to pull or sync my repos. I guess maintaining a
> requirements_file is the best as you say. '*pip2 list --user --outdated*'
> shows me the available updates and '*pip2 install --user -Ur
> requirement_file'* applies the updates. There would only be the gap if
> there is a new version on SVN that is not published on PyPI yet, so I still
> need to monitor those a bit.


With compatibility between various plug-ins and Trac-versions being highly
version sensitive, packages on PyPI etc being sporadically updated,  and
occasionally needing to make some instance-specific customizations at the
module-level, I've been using Pip's VCS capability to target specific
branches and tagged versions and install the sources rather than eggs or
wheels.
https://pip.pypa.io/en/stable/reference/pip_install/#vcs-support
Requirements files support specifying VCS options as well:
https://pip.pypa.io/en/stable/reference/pip_install/#requirements-file-format
Pip can still fetch supporting libs and such from PyPI, if needed.

About the virtual environment that was recommended many times to me I don't
> see the advantage yet. As I have all the Trac installation concentrated to
> the ~trac/ now, this $HOME is isolated from the root installation anyway.
> Then I'm daily btrfs-snapshotting the home directories. That virtualenv
> sounds like perlbrew, having a portable complete installation with
> interpreter and libraries. This would be helpful if I need separated
> installations for the trac user account. Do I need this? My isolated python
> environment is ~trac/.local/ managed by '*pip2 install --user*'.


It sounds like your setup fulfills many of the same needs that a virtual
environment would. If it's working for you I wouldn't see much point in
scrapping it. Virtual environments can offer further capabilities in terms
of other Python tooing interacting with them programatically, such as using
Pipenv to make reproducible builds that include a v. e. and invoke things
within its context. A good tool to have in the toolbox, even if you stick
with what you've got for your Trac setup.

Some parts I found from the linux distribution like
> dev-python/simplejson-3.16.0 I installed as root, but I guess if those are
> only requred by Trac I would also move them to the ~trac/ home, as PyPI
> could be more up to date as some Linux distribution.


I recommend isolating any Python 2 dependencies Trac has from  your system
Python sooner rather than later. Gentoo gives you a great deal of
flexibility there, of course, but distro maintainers generally are moving
faster on transitioning to Python 3 than Trac is (understandable with
Trac's small developer pool and the DB API & Jinja transitions also
demanding their attention).

Best,
--Jonathan Laufersweiler

On Fri, Nov 15, 2019 at 1:42 AM Mo  wrote:

> Thank you very much.
> I think it's a good idea to use such a requirements_file, eventhough I
> still think it's part of a package manager to populate such a file after a 
> '*pip
> install*', just like every rpm, apt, yum or portage does.
>
> Who is reponsible for publishing to PyPI? Does every track-hacks plugin
> author need to push to PyPI and such a request to do so I should file on
> track-hacks? The usual plugin wiki does mention the SVN source, but no
> comments about availability on PyPI.
> I don't know much about PyPI, but if there was kind of repositories for
> pip it would be better to find all plugins on a separated trac repository
> instead of pushing every single trac plugin to the big PyPI repo. But it
> seems to be one big repository and Trac components usually are names like
> "Trac*". Though it is hard to find the packages, as for instance '*pip2
> search AccountManager*' does not find it while '*pip2 search
> TracAccountManager*' finds the (outdated) 0.5.0 version.
>
> You say it is also possible to use '*pip2 install .*' from the root of a
> svn or git cloned repo. That would only replace my .egg building and
> copying. I still need to pull or sync my repos. I guess maintaining a
> requirements_file is the best as you say. '*pip2 list --user --outdated*'
> shows me the available updates and '*pip2 install --user -Ur
> requirement_file'* applies the updates. There would only be the gap if
> there is a new version on SVN that is not published on PyPI yet, so I still
> need to monitor those a bit.
>
> About the virtual environment that was recommended many times to me I
> don't see the advantage yet. As I have all the Trac installation
> concentrated to the ~trac/ now, this $HOME is isolated from the root
> installation anyway. Then I'm daily btrfs-snapshotting the home directories.
> That virtualenv sounds like perlbrew, having a portable complete
> installation with interpreter and libraries. This would be helpful if I
> need separated installations for the 

Re: [Trac] style.css content.ticket with Jinja2

[Mo]

Am Freitag, 15. November 2019 09:24:15 UTC+1 schrieb Jun Omae:

> Try to use site_head.html file. 
> See 
> https://trac.edgewall.org/wiki/TracInterfaceCustomization#SiteAppearance. 
>

Ok, what do I need there to change the width. I found the example:





..which makes use of the style.css again. I deployed both as static 
content. In the sources of a ticket package I can't find that .css anymore. 
What do I need to change the page width. I feel like that should be a 
configuration option anyway or should be adapting to modern screen 
resolutions.

-- 
You received this message because you are subscribed to the Google Groups "Trac 
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to trac-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/trac-users/1af33081-4480-4dbe-afe7-1003e3050148%40googlegroups.com.

[Trac] Re: AccountManagerPlugin: Reset password not working for me

[Andreas]

still the same...
Do I have to create a new .htdigest-file or install something else?

Am Mittwoch, 13. November 2019 18:21:11 UTC+1 schrieb RjOllos:
>
>
>
> On Friday, November 8, 2019 at 2:02:46 AM UTC-8, Andreas wrote:
>>
>> Hello,
>>
>> I am using the latest trunk-version of AccountManagerPlugin on Trac 1.4
>>
>> My trac.ini looks like this:
>>
>> [account-manager]
>>> allow_delete_account = disabled
>>> htdigest_file = /var/lib/trac/testsystem/.htdigest
>>> htdigest_realm = testsystem
>>> password_store = HtDigestStore
>>> username_regexp = (?i)^[a-z0-9.]{3,}$
>>> verify_email = disabled
>>>
>>
>> Under [components], I have nothing related with this plugin.
>> The passwords are stored in /var/lib/trac/testsystem/.htdigest
>>
>> Via the Account Manager, creating a new user and setting a new password 
>> manually works as it should. 
>> When I select a user and click on "Reset password", the user gets an 
>> email with the new password. 
>> But when I then try to login with the new password, it's not working - 
>> only the old password is working.
>>
>> I found a ticket on trac-hacks (#11869) with a similar problem, but it 
>> seems like the logic has changed and the ResetPwStore and ResetPwStore 
>> does not exist anymore, but I'm not sure.
>> I am also not sure if this is an installation / setting issue or an issue 
>> of plugin.
>>
>> Can anybody help?
>>
>> Thank you!
>>
>> Best regards,
>> Andreas
>>
>
>
> Please try:
>
> password_store = HtPasswdStore,ResetPwStore 
>
> - Ryan
>

-- 
You received this message because you are subscribed to the Google Groups "Trac 
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to trac-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/trac-users/1f78fff6-ddce-4aa6-8dfb-832d0905f4eb%40googlegroups.com.

Re: [Trac] style.css content.ticket with Jinja2

[Jun Omae]

On Fri, Nov 15, 2019 at 4:58 PM Mo  wrote:
>
> Hi,
> after migrating from Trac 1.2.3 to 1.4, my custom style.css does not work 
> anymore. I have this to make tickets use more horizontal space on our default 
> 24" 1920px screens:
>
> $ cat htdocs/style.css
> #content.ticket
> {
> width: auto;
> max-width: 1400px;
> }
>
>
> I guess this is caused by the genshi > Jinja2 migration. How can I do this 
> modification now?
>
> Best regards.

Try to use site_head.html file.
See https://trac.edgewall.org/wiki/TracInterfaceCustomization#SiteAppearance.

-- 
Jun Omae  (大前 潤)

-- 
You received this message because you are subscribed to the Google Groups "Trac 
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to trac-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/trac-users/CAEVLMahrU-v4_WP1gVgX_JEXJq3Ar7GKO8m6vGMtF3UMvXYL9A%40mail.gmail.com.