From rb.proj at gmail.com  Fri Sep  8 04:10:17 2023
From: rb.proj at gmail.com (Reimar Bauer)
Date: Fri, 8 Sep 2023 10:10:17 +0200
Subject: [moin-devel] moin-devel Digest, Vol 22, Issue 1
In-Reply-To: <mailman.18.1692115203.18793.moin-devel@python.org>
References: <mailman.18.1692115203.18793.moin-devel@python.org>
Message-ID: <CADfaKO_5pBj3=Ud7ApCeGj82kyCZC6DHmbU-sMa_uwRUwaWPmw@mail.gmail.com>

Moin Ulrich,


>
> Message: 1
> Date: Mon, 14 Aug 2023 20:17:24 +0000
> From: "Ulrich B." <UlrichB at posteo.de>
> To: moin-devel at python.org
> Subject: [moin-devel] moin2 release with core functionality
> Message-ID: <f81501a5-7aa3-1d96-68c7-030808069de8 at posteo.de>
> Content-Type: text/plain; charset=UTF-8; format=flowed
>
> Hello,
>
> many owners of a moin 1.9 wiki are waiting for a moin replacement based
> on Python3. If we limit the functionality of moin2 to the core features
> of moin1.9, IMO it should be possible to move to beta status or even
> better create a release candidate. For example, we can allow moinwiki
> markup and disable all other markup languages in the default
> configuration. They will then be treated as experimental.
>

I would prefer a feature freeze, there can still be much improved. But
that's always the case.
In that freeze a common set of the whole scope may be defined stable and
the rest experimental.



> Wiki owners can test if they can migrate their wiki data to moin2. This
> could be an option to get more people interested in the development and
> to push the release of moin2.
>

That is currently my situation. I am also aware that a lot of my plugins
won't work with an update.
And the time span where I can upgrade those gets also limited by deleting
py 2.7 from LTS distributions.
I have also to think about "what comes next after the wiki idea". I assume
any old user is in a similar situation.

The most important question is. Is it good enough to try for the moment?
If it is, please get into a semantic release cycle starting with moin-2.0,0
as soon as possible.
With a release instead of working with a repository are also steps of
"doings" for others defined.
In semantic versioning I would know that I have to verify and refactor
something again, with the next major.
For my users it would mean as long as we have only minor or patch level
releases
they can work similiar as they learned with the first change to moin-2.0.0.

best regards
Reimar


>
> What is your opinion about this idea? I look forward to your feedback.
>
> With regards,
>
> Ulrich
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mail.python.org/pipermail/moin-devel/attachments/20230908/0f02d81d/attachment.html>

From paul at boddie.org.uk  Sun Sep 10 13:25:03 2023
From: paul at boddie.org.uk (Paul Boddie)
Date: Sun, 10 Sep 2023 19:25:03 +0200
Subject: [moin-devel] Debian packages (Re: moin2 release with core
 functionality)
In-Reply-To: <20151829.TJA5HnV79j@jason>
References: <f81501a5-7aa3-1d96-68c7-030808069de8@posteo.de>
 <7728983.CRJIfxRXAY@jason> <20151829.TJA5HnV79j@jason>
Message-ID: <51346812.TGgVnonMyb@jason>

On Monday, 21 August 2023 00:16:05 CEST Paul Boddie wrote:
> 
> Now, it is possible to publish repositories of packages within Salsa, and
> this functionality is actually used to provide some new packages to the
> test environment that installs Moin and runs its tests. However, more work
> is needed to collect all of the new packages and to serve them up together.

Following up to myself again, I finally figured out a way of publishing a 
collection of packages on Debian's Salsa (GitLab) service. This should allow 
anyone running Debian unstable to try out the packages I have made for Moin 2.

The Salsa pipeline and job responsible for this output are these:

https://salsa.debian.org/moin-team/moin/-/pipelines/577973
https://salsa.debian.org/moin-team/moin/-/jobs/4683093

== Patches ==

Irritatingly, I had to fix various Flask-related incompatibilities to get the 
test suite working again. Since there has been a Debian release recently, 
people have bumped the versions of various packages and, of course, some 
software developers don't believe in API stability, so it broke Moin in 
various ways.

So, the patches currently applied in the packaging should probably be applied 
upstream:

https://salsa.debian.org/moin-team/moin/-/blob/debian/master/debian/patches/
016-fix-flask-babel-3-breakage

There are other patches that may benefit from application upstream.

== Packages ==

Currently, the packages are available from a package repository at the 
following location:

https://moin-team.pages.debian.net/-/moin/-/jobs/4683093/artifacts/aptly/
index.html

Now, to use this repository, it is probably best to follow the "one-line 
format" instructions at the bottom of that page, this involving the 
downloading of the public key and the creation of a sources list file.

However, I found that the source definition needs changing to specify an 
architecture of "all" as follows:

deb [arch=all signed-by=...] ...

In other words, "arch=all" needs adding, separated by a space. You should then 
be able to run the following:

apt-get update
apt-get install python3-moinmoin2

This will then download and install new and existing packages. Afterwards, you 
can then create and run an instance as follows:

moin create-instance
moin index-create
moin run

I hope this is useful to someone. I have had no feedback about this packaging 
work, despite spending a fair amount of time on it. If that continues, it will 
definitely influence how I spend my time in future.

Paul



From UlrichB at posteo.de  Mon Sep 11 16:53:57 2023
From: UlrichB at posteo.de (Ulrich B.)
Date: Mon, 11 Sep 2023 20:53:57 +0000
Subject: [moin-devel] Debian packages (Re: moin2 release with core
 functionality)
In-Reply-To: <51346812.TGgVnonMyb@jason>
References: <f81501a5-7aa3-1d96-68c7-030808069de8@posteo.de>
 <7728983.CRJIfxRXAY@jason> <20151829.TJA5HnV79j@jason>
 <51346812.TGgVnonMyb@jason>
Message-ID: <ce2a52cb-8899-73f5-7a28-1524c9d9f467@posteo.de>

Hi Paul,

Am 10.09.23 um 19:25 schrieb Paul Boddie:
>
> == Patches ==
>
> So, the patches currently applied in the packaging should probably be 
> applied
> upstream:
>
> https://salsa.debian.org/moin-team/moin/-/blob/debian/master/debian/patches/ 
>
> 016-fix-flask-babel-3-breakage
>
> There are other patches that may benefit from application upstream.
I will go thru your patches and create issues and pull requests.
> == Packages ==
>
> Currently, the packages are available from a package repository at the
> following location:

Setting up a new Debian and testing your package will take me some time.

> I hope this is useful to someone. I have had no feedback about this 
> packaging
> work, despite spending a fair amount of time on it.
thanks for all your work. I have great respect for your results, it 
definitely helps to keep the moinwiki project running.


Kind regards,

Ulrich
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mail.python.org/pipermail/moin-devel/attachments/20230911/cd6bb719/attachment.html>

From paul at boddie.org.uk  Mon Sep 11 17:44:12 2023
From: paul at boddie.org.uk (Paul Boddie)
Date: Mon, 11 Sep 2023 23:44:12 +0200
Subject: [moin-devel] Debian packages (Re: moin2 release with core
 functionality)
In-Reply-To: <ce2a52cb-8899-73f5-7a28-1524c9d9f467@posteo.de>
References: <f81501a5-7aa3-1d96-68c7-030808069de8@posteo.de>
 <51346812.TGgVnonMyb@jason> <ce2a52cb-8899-73f5-7a28-1524c9d9f467@posteo.de>
Message-ID: <2359065.vscqj5ukzW@jason>

Ulrich,

> I will go thru your patches and create issues and pull requests.

Thanks for offering to look at them! The ones that were required to adapt to 
package version changes were as follows:

001-pdfminer3-to-pdfminer      - uses pdfminer instead of pdfminer3
002-log-logger                 - fixes UnboundLocalError in logging
015-fix-test-time-zones        - use more conventional time zone names
016-fix-flask-babel-3-breakage - fix API breakage in Flask-Babel 3

There are numerous patches to setup.py, either adding files like intermap.txt 
or adjusting package details. The above pdfminer change introduces 
pdfminer.six instead of pdfminer3, for instance.

> thanks for all your work. I have great respect for your results, it
> definitely helps to keep the moinwiki project running.

Thank you for all your hard work keeping Moin itself going! I would really 
like to see the project take off again, but I have limited time and energy 
available to direct towards it.

Please let me know if you need any of the patches explaining or want to 
discuss them. I will attempt to track upstream development and hopefully 
eliminate patches over time.

If you need to set up Debian, I can recommend doing so in a chroot environment 
or a virtual machine. I don't know what kind of system you are running, but 
something like GNOME Boxes should make a virtual machine installation fairly 
straightforward in a Linux environment.

Myself, I use some scripts that create and manage chroot environments that 
have been useful to me over the years, but I cannot claim that they are 
"production quality":

https://hg.boddie.org.uk/userinstall

There are more cumbersome instructions for setting up a chroot on the Debian 
wiki:

https://wiki.debian.org/chroot

But a virtual machine might end up being the easiest approach to begin with, 
particularly if you are not running Linux.

Regards,

Paul



From paul at boddie.org.uk  Tue Sep 12 17:05:51 2023
From: paul at boddie.org.uk (Paul Boddie)
Date: Tue, 12 Sep 2023 23:05:51 +0200
Subject: [moin-devel] Debian packages (Re: moin2 release with core
 functionality)
In-Reply-To: <87cyyn3z46.fsf@navis.mail-host-address-is-not-set>
References: <f81501a5-7aa3-1d96-68c7-030808069de8@posteo.de>
 <51346812.TGgVnonMyb@jason>
 <87cyyn3z46.fsf@navis.mail-host-address-is-not-set>
Message-ID: <4971733.IGfacuGoRi@jason>

Nicholas,

> Thank you for already forwarding patches.  If you haven't already, and
> are interested in Debian metadata for patches, please take a look at
> "DEP-3: Patch Tagging Guidelines".

I'll try and review how I have formulated these patches. It was all very 
cumbersome to just get the actual substance of the patches to work, but then I 
discovered "gbp pq" which makes it somewhat easier.

So, I may clean up my patch branch and prepare a cleaner set of patches, 
reducing them from the 15 or so there are now to probably something closer to 
half that. There is definitely a distinction between Debian-specific patches, 
which may always need to be applied, and patches that can be moved upstream.

> Thank you very much for you work on this!  For feedback about your
> Debian packaging project, may I suggest one or more of the following
> lists:
> 
> debian-devel (general/main development list)
> debian-python (Python Team list)
> debian-admin (Debian System Administration list) <- maintain Debian
> infrastructure debian-mentors (for packaging-related and Debian Policy
> questions).

Thank you for the pointers! I have discussed some Salsa-related issues on 
debian-python already, leading to the availability of packages published from 
Salsa for broader convenience.

I imagine that debian-admin might have some interest in Moin 2, although I 
noticed a Salsa-based discussion where people were enthusiastic about 
migrating the Debian Wiki to MediaWiki instead of switching to Moin 2. Still, 
I think a broader audience would benefit from access to this software.

(Obviously, the ejection of Python 2 from Debian has exacerbated the Debian 
Wiki situation, and I think that more care should have been taken with the 
deprecation of Python 2. There is also a good argument for keeping a package 
for Python 2 itself around in the longer term, making sure that it still 
compiles using contemporary compilers, given that individual users may have 
scripts that still use it.)

> I think that it would be valuable to have your Moin2 package as an
> official Debian package in the standard repositories, and I hope you'll
> consider reaching out to one of the mailing lists noted above.  There
> are also IRC channels, and there is not necessarily overlap between the
> people who follow the lists vs irc.

I will probably stick to mailing lists, beginning with debian-python and 
debian-admin, I think.

> Debconf23 is currently ongoing in Kochi, India, so it's one of the perfect
> moments for announcing, discussing, and collaborating on projects.  Worst
> case scenario, I hope that you will find someone to carry the torch of your
> work the last 10%, but I think it's more likely you will find collaboration
> :)

Thank you for following up and for the encouragement!

Regards,

Paul



From paul at boddie.org.uk  Tue Sep 12 17:23:59 2023
From: paul at boddie.org.uk (Paul Boddie)
Date: Tue, 12 Sep 2023 23:23:59 +0200
Subject: [moin-devel] Debian packages (Re: moin2 release with core
 functionality)
In-Reply-To: <878r9b3ybp.fsf@navis.mail-host-address-is-not-set>
References: <f81501a5-7aa3-1d96-68c7-030808069de8@posteo.de>
 <2359065.vscqj5ukzW@jason>
 <878r9b3ybp.fsf@navis.mail-host-address-is-not-set>
Message-ID: <154102245.uT19Gn5oDC@jason>

On Tuesday, 12 September 2023 22:56:26 CEST Nicholas D Steeves wrote:
> 
> Paul, you're already forwarding patches, maintaining a package, and
> deploying it using a not-particularly-well-known apt_repo-in-Salsa
> method, so I think a Debian team context would be an asset for those
> times when--for example--you want to take a holiday :)  Also would mean
> that sysadmins who use downstreams like Ubuntu would also be able to
> benefit from your work, and this seems like it would reinvigorate Moin
> usage in the wild.

The moin-team group was Steve McIntyre's initiative, and publishing out of 
Salsa is just a workaround at present, but I agree that something more 
substantial is probably needed.

[...]

> sbuild-debian-developer-setup is the easiest way that I know to get a
> clean chroot:
>  
> https://manpages.debian.org/bookworm/sbuild-debian-developer-setup/sbuild-d
> ebian-developer-setup.1.en.html
> 
> Using sbuild will also do some minor fuzzing (eg: packages must declare
> all needed dependencies and must only write to safe locations during the
> package build)

Yes, I currently use gbp as follows:

gbp buildpackage --git-debian-branch=debian/master \
                 --git-upstream-tag='upstream/%(version)s' \
                 --git-builder=sbuild

I overlooked that sbuild might provide tools that are usable enough for more 
general activities, and I might even try this out myself!

Thanks once again for the suggestions!

Paul



From UlrichB at posteo.de  Fri Sep 15 17:31:18 2023
From: UlrichB at posteo.de (Ulrich B.)
Date: Fri, 15 Sep 2023 21:31:18 +0000
Subject: [moin-devel] Debian packages - patches
In-Reply-To: <2359065.vscqj5ukzW@jason>
References: <f81501a5-7aa3-1d96-68c7-030808069de8@posteo.de>
 <51346812.TGgVnonMyb@jason> <ce2a52cb-8899-73f5-7a28-1524c9d9f467@posteo.de>
 <2359065.vscqj5ukzW@jason>
Message-ID: <c2fc450d-be1a-ce54-0a30-0bde4e4c02de@posteo.de>

Hi Paul,

Am 11.09.23 um 23:44 schrieb Paul Boddie:
> Thanks for offering to look at them! The ones that were required to 
> adapt to
> package version changes were as follows:
>
> 001-pdfminer3-to-pdfminer????? - uses pdfminer instead of pdfminer3
This pdfminer patch has been merged into master today.
> 002-log-logger - fixes UnboundLocalError in logging
Can you provide an example how to reproduce this error?
> 015-fix-test-time-zones - use more conventional time zone names
Is this issue a bug or is it just cosmetic?
> 016-fix-flask-babel-3-breakage - fix API breakage in Flask-Babel 3

A pull request has been created for flask-babel 3.


Many thanks.

Ulrich
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mail.python.org/pipermail/moin-devel/attachments/20230915/18bd074f/attachment.html>

From paul at boddie.org.uk  Fri Sep 15 18:29:21 2023
From: paul at boddie.org.uk (Paul Boddie)
Date: Sat, 16 Sep 2023 00:29:21 +0200
Subject: [moin-devel] Debian packages - patches
In-Reply-To: <c2fc450d-be1a-ce54-0a30-0bde4e4c02de@posteo.de>
References: <f81501a5-7aa3-1d96-68c7-030808069de8@posteo.de>
 <2359065.vscqj5ukzW@jason> <c2fc450d-be1a-ce54-0a30-0bde4e4c02de@posteo.de>
Message-ID: <2274232.sCrPsA8A5L@jason>

On Friday, 15 September 2023 23:31:18 CEST Ulrich B. wrote:
> > 001-pdfminer3-to-pdfminer      - uses pdfminer instead of pdfminer3
> 
> This pdfminer patch has been merged into master today.

Excellent! I will eliminate the related patches in the packaging.

> > 002-log-logger - fixes UnboundLocalError in logging
> 
> Can you provide an example how to reproduce this error?

I'll look into reproducing this when I merge from your upstream branch and try 
and rebuild.

> > 015-fix-test-time-zones - use more conventional time zone names
> 
> Is this issue a bug or is it just cosmetic?

I think it is something to do with the kind of time zone involved. US/Arizona 
is some kind of alias, whereas America/Phoenix is one of the fundamental 
zones. For some reason, in the package build environment, the pytz 
configuration doesn't recognise the alias whereas it does generally.

It seems to be something that pytz in Debian unstable does not support:

>>> import pytz
>>> pytz.timezone("US/Arizona")
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/usr/lib/python3/dist-packages/pytz/__init__.py", line 200, in 
timezone
    raise UnknownTimeZoneError(zone)
pytz.exceptions.UnknownTimeZoneError: 'US/Arizona'

Looking further, it appears that pytz may be provided as some kind of wrapper 
around the zoneinfo module:

https://packages.debian.org/sid/python3-pytz-deprecation-shim

So, I guess this is yet another Python ecosystem regression.

> > 016-fix-flask-babel-3-breakage - fix API breakage in Flask-Babel 3
> 
> A pull request has been created for flask-babel 3.

Great! Thanks for following up with that. I suspect that they have broken the 
API deliberately, but you never know.

Paul



From paul at boddie.org.uk  Mon Sep 18 11:16:34 2023
From: paul at boddie.org.uk (Paul Boddie)
Date: Mon, 18 Sep 2023 17:16:34 +0200
Subject: [moin-devel] Debian packages - patches
In-Reply-To: <2274232.sCrPsA8A5L@jason>
References: <f81501a5-7aa3-1d96-68c7-030808069de8@posteo.de>
 <c2fc450d-be1a-ce54-0a30-0bde4e4c02de@posteo.de> <2274232.sCrPsA8A5L@jason>
Message-ID: <3593570.CsQU6rXYL0@jason>

On Saturday, 16 September 2023 00:29:21 CEST Paul Boddie wrote:
> On Friday, 15 September 2023 23:31:18 CEST Ulrich B. wrote:
> > > 002-log-logger - fixes UnboundLocalError in logging
> > 
> > Can you provide an example how to reproduce this error?
> 
> I'll look into reproducing this when I merge from your upstream branch and
> try and rebuild.

I have now eliminated this patch since it may only have been required as a 
consequence of another patch that has also been eliminated. I previously had 
difficulties getting Moin working when it needed to be run in the packaging 
environment.

Here are the current patches:

https://salsa.debian.org/moin-team/moin/-/tree/debian/master/debian/patches

Apart from patches adjusting package versions and availability, some of these 
do merit a bit more explanation.

First of all, I did experience problems copying package data, as can be seen 
from the 011-setup-package-data patch.

Another problem was encountered with some kind of change to the Python 
packaging tools, where I got warnings about namespace packages, but it is 
hopefully addressed with the 012-search-namespace-packages patch.

Testing with updated upstream code and some packaging adjustments was 
successful, with an updated package repository being made available here:

https://moin-team.pages.debian.net/-/moin/-/jobs/4712648/artifacts/aptly/
index.html

Again, the "old one-line format" approach can be used to access this 
repository with the following kind of amendment being made to the repository 
declaration lines:

deb [arch=all signed-by=...] https...

Here, "arch=all" has been added. Remember to acquire the public key!

Paul



From christoph.klassen at intevation.de  Thu Sep 21 10:16:00 2023
From: christoph.klassen at intevation.de (Christoph Klassen)
Date: Thu, 21 Sep 2023 16:16:00 +0200
Subject: [moin-devel] Moin2 - Create new theme
Message-ID: <202309211616.01170.christoph.klassen@intevation.de>

Hello everyone,

I'm working at Intevation GmbH and we were and are using the Moin wiki engine 
and would like to continue to do so with Moin 2 so thanks for your work! My 
other colleagues were already contributing to the new version and now I also 
want to do something to improve Moin 2. More precisely, I want to create a 
new theme.

To do so I first want to prepare myself with some documentation. I found the 
section on 
https://moin-20.readthedocs.io/en/latest/devel/development.html#templates-and-themes 
but are they any other places with documentation about themes?

And which icons are you using? Are they from Font Awesome?


Many greetings,
Christoph

-- 
Christoph Klassen | https://intevation.de
Intevation GmbH, Osnabr?ck, DE; Amtsgericht Osnabr?ck, HRB 18998
Gesch?ftsf?hrer: Frank Koormann, Bernhard Reiter

From paul at boddie.org.uk  Thu Sep 21 12:03:39 2023
From: paul at boddie.org.uk (Paul Boddie)
Date: Thu, 21 Sep 2023 18:03:39 +0200
Subject: [moin-devel] Moin2 - Create new theme
In-Reply-To: <202309211616.01170.christoph.klassen@intevation.de>
References: <202309211616.01170.christoph.klassen@intevation.de>
Message-ID: <2111020.dz6aNmVp7Z@jason>

On Thursday, 21 September 2023 16:16:00 CEST Christoph Klassen wrote:
> 
> And which icons are you using? Are they from Font Awesome?

They appear to be, yes. In the Debian package, the python3-xstatic-font-
awesome package is a dependency which depends on fonts-font-awesome.

I think the Debian package may need to incorporate a patch to upstream Moin 
sources because a stylesheet file in src/moin/templates/base.html called 
all.css is specified, whereas the Debian fonts-font-awesome package doesn't 
have such a file. Instead, it seems that font-awesome.css might be the 
appropriate file.

Although Debian unstable provides Font Awesome 5.x, which has the all.css file 
upstream, Debian appears to have maintained compatibility with 4.x. Indeed, 
the version of this package is given as...

5.0.10+really4.7.0~dfsg-4.1

So maybe there will be an upgrade to this package at some point.

Paul



From UlrichB at posteo.de  Thu Sep 21 17:07:07 2023
From: UlrichB at posteo.de (Ulrich B.)
Date: Thu, 21 Sep 2023 21:07:07 +0000
Subject: [moin-devel] Moin2 - Create new theme
In-Reply-To: <202309211616.01170.christoph.klassen@intevation.de>
References: <202309211616.01170.christoph.klassen@intevation.de>
Message-ID: <775c2dec-ccd4-2032-9c9f-94c4b1876ef7@posteo.de>

Hello Christoph,

thanks for your interest in moin2 and your support.

Am 21.09.23 um 16:16 schrieb Christoph Klassen:

> I also
> want to do something to improve Moin 2. More precisely, I want to create a
> new theme.
Maybe you also have ideas and improvements for the existing default theme.
> To do so I first want to prepare myself with some documentation. I found the
> section on
> https://moin-20.readthedocs.io/en/latest/devel/development.html#templates-and-themes  
> but are they any other places with documentation about themes?
>
Please also have a look at 
https://moin-20.readthedocs.io/en/latest/admin/configure.html#user-interface-customization 
and check the open issues containing "theme".

Kind regards,

Ulrich




From christoph.klassen at intevation.de  Fri Sep 22 10:07:02 2023
From: christoph.klassen at intevation.de (Christoph Klassen)
Date: Fri, 22 Sep 2023 16:07:02 +0200
Subject: [moin-devel] Moin2 - Create new theme
In-Reply-To: <2111020.dz6aNmVp7Z@jason>
References: <202309211616.01170.christoph.klassen@intevation.de>
 <2111020.dz6aNmVp7Z@jason>
Message-ID: <2416cd7a-a822-7d3b-98f0-73d03593703b@intevation.de>

Hi!

On 21.09.23 18:03, Paul Boddie wrote:
> Although Debian unstable provides Font Awesome 5.x, which has the all.css file
> upstream, Debian appears to have maintained compatibility with 4.x. Indeed,
> the version of this package is given as...
> 
> 5.0.10+really4.7.0~dfsg-4.1
This was new for me. Didn't know that Debian has a package for Font 
Awesome icons.

The name of the package is a bit confusing though. The page 
https://packages.debian.org/bookworm/fonts-font-awesome says that this 
is still Font Awesome 4.


> So maybe there will be an upgrade to this package at some point.
The page mentioned above has also the little addition "not Font Awesome 
5 or Font Awesome 6 which are different fonts with different licensing". 
Maybe these licenses are not compatible with Debian. But at least I know 
in which version I have to look for icons if I need them.

On 21.09.23 23:07, Ulrich B. wrote:
 > Maybe you also have ideas and improvements for the existing default 
theme.
Indeed, I have some suggestions. Maybe I will create a PR with some 
changes or at least create an issue.


 > Please also have a look at
 > 
https://moin-20.readthedocs.io/en/latest/admin/configure.html#user-interface-customization 
and check the open issues containing "theme".
This looks helpful. Thanks!

Many greetings,
Christoph

-- 
Christoph Klassen | https://intevation.de
Intevation GmbH, Osnabr?ck, DE; Amtsgericht Osnabr?ck, HRB 18998
Gesch?ftsf?hrer: Frank Koormann, Bernhard Reiter
-------------- next part --------------
A non-text attachment was scrubbed...
Name: OpenPGP_signature
Type: application/pgp-signature
Size: 665 bytes
Desc: OpenPGP digital signature
URL: <https://mail.python.org/pipermail/moin-devel/attachments/20230922/6d54d4d1/attachment.sig>

From sten at debian.org  Fri Sep 22 12:25:40 2023
From: sten at debian.org (Nicholas D Steeves)
Date: Fri, 22 Sep 2023 12:25:40 -0400
Subject: [moin-devel] Moin2 - Create new theme
In-Reply-To: <2111020.dz6aNmVp7Z@jason>
Message-ID: <87h6nmb2ez.fsf@digitalmercury.freeddns.org>

Paul Boddie <paul at boddie.org.uk> writes:

> On Thursday, 21 September 2023 16:16:00 CEST Christoph Klassen wrote:
>> 
>> And which icons are you using? Are they from Font Awesome?
>
> They appear to be, yes. In the Debian package, the python3-xstatic-font-
> awesome package is a dependency which depends on fonts-font-awesome.
>
> I think the Debian package may need to incorporate a patch to upstream Moin 
> sources because a stylesheet file in src/moin/templates/base.html called 
> all.css is specified, whereas the Debian fonts-font-awesome package doesn't 
> have such a file. Instead, it seems that font-awesome.css might be the 
> appropriate file.
>
> Although Debian unstable provides Font Awesome 5.x, which has the all.css file 
> upstream, Debian appears to have maintained compatibility with 4.x. Indeed, 
> the version of this package is given as...
>
> 5.0.10+really4.7.0~dfsg-4.1

I'm not sure why 5.x was uploaded to Debian in the first place, because
Font Awesome 5.x is does not meet the criteria for free software
according to the Debian Free Software Guidelines (dfsg).  Maybe its
license was poorly defined at that time?  "5.0.10+really4.7.0~dfsg"
means "sort as 5.0.10", while the semantic the upstream version is
really "4.7.0~dfsg" which means it has been made dfsg-compatible by the
removal of anything non-free.

  https://www.debian.org/social_contract#guidelines
  https://www.mail-archive.com/debian-bugs-dist at lists.debian.org/msg1631384.html
  https://github.com/syncthing/syncthing/issues/5236
  https://github.com/FortAwesome/Font-Awesome/issues/13467
  https://github.com/os-autoinst/openQA/issues/4158
  etc.

> So maybe there will be an upgrade to this package at some point.

This will only happen if Font Awesome opens the build system for ? v5
under a FLOSS license.  Projects that want something more up-to-date
than Font Awesome v4 are migrating to Fork Awesome:

  https://forkaweso.me/Fork-Awesome/

I hope this clears things up, and that you'll consider using Fork
Awesome!

Kind regards,
Nicholas
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 857 bytes
Desc: not available
URL: <https://mail.python.org/pipermail/moin-devel/attachments/20230922/bb8eb9f0/attachment.sig>

From sten at debian.org  Fri Sep 22 12:23:46 2023
From: sten at debian.org (Nicholas D Steeves)
Date: Fri, 22 Sep 2023 12:23:46 -0400
Subject: [moin-devel] Debian packages (Re: moin2 release with core
 functionality)
In-Reply-To: <154102245.uT19Gn5oDC@jason>
References: <f81501a5-7aa3-1d96-68c7-030808069de8@posteo.de>
 <2359065.vscqj5ukzW@jason>
 <878r9b3ybp.fsf@navis.mail-host-address-is-not-set>
 <154102245.uT19Gn5oDC@jason>
Message-ID: <87msxeb2i5.fsf@digitalmercury.freeddns.org>

Hi Paul,

Sorry for the belated response.  Reply follows in-line:

Paul Boddie <paul at boddie.org.uk> writes:

>> sbuild-debian-developer-setup is the easiest way that I know to get a
>> clean chroot:
>>  
>> https://manpages.debian.org/bookworm/sbuild-debian-developer-setup/sbuild-d
>> ebian-developer-setup.1.en.html
>> 
>> Using sbuild will also do some minor fuzzing (eg: packages must declare
>> all needed dependencies and must only write to safe locations during the
>> package build)
>
> Yes, I currently use gbp as follows:
>
> gbp buildpackage --git-debian-branch=debian/master \
>                  --git-upstream-tag='upstream/%(version)s' \
>                  --git-builder=sbuild
>
> I overlooked that sbuild might provide tools that are usable enough for more 
> general activities, and I might even try this out myself!

:) Well, you figured it out enough to get work done, which is something
that some people have complained is too hard!  Yes, by default sbuild
uses "schroot", which takes care of the creation and destruction of
clean chroots, with session management, since 2005.  If you prefer real
containers or a fully virtualised build machine (with LXC), gbp can also
uses these.  I prefer schroots, because they don't eat into the RAM as
much as real containers of VMs ;)

> Thanks once again for the suggestions!

You're welcome!

I wish you success,
Nicholas

From paul at boddie.org.uk  Fri Sep 22 15:38:39 2023
From: paul at boddie.org.uk (Paul Boddie)
Date: Fri, 22 Sep 2023 21:38:39 +0200
Subject: [moin-devel] Debian packages (Re: moin2 release with core
 functionality)
In-Reply-To: <87msxeb2i5.fsf@digitalmercury.freeddns.org>
References: <f81501a5-7aa3-1d96-68c7-030808069de8@posteo.de>
 <154102245.uT19Gn5oDC@jason> <87msxeb2i5.fsf@digitalmercury.freeddns.org>
Message-ID: <8114443.7rJWV3TyGg@jason>

On Friday, 22 September 2023 18:23:46 CEST Nicholas D Steeves wrote:
> 
> :) Well, you figured it out enough to get work done, which is something
> that some people have complained is too hard!  Yes, by default sbuild
> uses "schroot", which takes care of the creation and destruction of
> clean chroots, with session management, since 2005.

About a decade ago, I was using pbuilder which still seemed like the default 
choice. Of course, all of this is just tooling around chroot, as are my own 
tools for having local distribution installations.

I do think packaging is too hard. gbp does provide some automation for common 
tasks, but it needs to be used in precisely the right way or it can get in the 
way. And getting up to speed with the right way is not as obvious as it might 
be.

> If you prefer real containers or a fully virtualised build machine (with
> LXC), gbp can also uses these.  I prefer schroots, because they don't eat
> into the RAM as much as real containers of VMs ;)

Virtual machines and containers have their uses but are arguably excessive in 
many respects, and Debian's tooling works well enough with chroots, anyway. A 
lot of this seems so much better than what users of the Red Hat derivatives 
seem to put up with.

Steady progress is being made, and I intend to contact debian-www and to file 
ITP tickets for the different packages involved. That will surely awaken 
groups who have an interest in certain packages.

Thanks once again for the encouragement!

Regards,

Paul

P.S. I should ask whether there is a way of pruning chroots under /run/schroot 
that seem to be created but not removed.



From rb.proj at gmail.com  Thu Sep 28 14:29:50 2023
From: rb.proj at gmail.com (Reimar Bauer)
Date: Thu, 28 Sep 2023 20:29:50 +0200
Subject: [moin-devel] moin-devel Digest, Vol 23, Issue 8
In-Reply-To: <mailman.13.1695398403.31772.moin-devel@python.org>
References: <mailman.13.1695398403.31772.moin-devel@python.org>
Message-ID: <CADfaKO9hrhC=9GBgXO4UdsAXmOJPmVSqSbhADs_XPdEEsYE-ug@mail.gmail.com>

On Fri, Sep 22, 2023 at 6:00?PM <moin-devel-request at python.org> wrote:

> Send moin-devel mailing list submissions to
>         moin-devel at python.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
>         https://mail.python.org/mailman/listinfo/moin-devel
> or, via email, send a message with subject or body 'help' to
>         moin-devel-request at python.org
>
> You can reach the person managing the list at
>         moin-devel-owner at python.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of moin-devel digest..."
>
>
> Today's Topics:
>
>    1. Re: Moin2 - Create new theme (Paul Boddie)
>    2. Re: Moin2 - Create new theme (Ulrich B.)
>    3. Re: Moin2 - Create new theme (Christoph Klassen)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Thu, 21 Sep 2023 18:03:39 +0200
> From: Paul Boddie <paul at boddie.org.uk>
> To: moin-devel at python.org
> Subject: Re: [moin-devel] Moin2 - Create new theme
> Message-ID: <2111020.dz6aNmVp7Z at jason>
> Content-Type: text/plain; charset="us-ascii"
>
> On Thursday, 21 September 2023 16:16:00 CEST Christoph Klassen wrote:
> >
> > And which icons are you using? Are they from Font Awesome?
>
> They appear to be, yes. In the Debian package, the python3-xstatic-font-
> awesome package is a dependency which depends on fonts-font-awesome.
>
> I think the Debian package may need to incorporate a patch to upstream
> Moin
> sources because a stylesheet file in src/moin/templates/base.html called
> all.css is specified, whereas the Debian fonts-font-awesome package
> doesn't
> have such a file. Instead, it seems that font-awesome.css might be the
> appropriate file.
>
> Although Debian unstable provides Font Awesome 5.x, which has the all.css
> file
> upstream, Debian appears to have maintained compatibility with 4.x.
> Indeed,
> the version of this package is given as...
>
> 5.0.10+really4.7.0~dfsg-4.1
>
> So maybe there will be an upgrade to this package at some point.
>
> Paul
>
>
>
> I had builded last year the V6.2.1 on  Pypi, compared to the old 4.1.0,
this was a big change
https://github.com/xstatic-py/xstatic-font-awesome/pull/1/files

Likly in november I will update this to 6.4.0 or newer

Reimar
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mail.python.org/pipermail/moin-devel/attachments/20230928/3f2ebea4/attachment.html>