Re: [moin-devel] [moin-user] moinmoin 2.0 stable release
(Dropping moin-user from this discussion...) On Monday, 28 February 2022 18:46:08 CET Lukasz Szybalski wrote:
On Fri, Feb 25, 2022 at 5:01 PM Paul Boddie <paul@boddie.org.uk> wrote:
I looked into the Debian packaging requirements, and it seems to me that the following packages are needed (not being available in Debian):
Awsome. Thank you!!
No problem!
emeraldtree Flask-Theme flatland XStatic-CKEditor XStatic-autosize XStatic-jQuery-File-Upload XStatic-TWikiDraw-moin XStatic-AnyWikiDraw XStatic-svg-edit-moin XStatic-JQuery.TableSorter XStatic-Pygments
There are already Flask and XStatic packages in Debian, but not those listed above. I have just been looking at the first three in this list, and it seems feasible to try and put together some quick packages for them, assuming that I can rediscover how to make Debian packages.
If you do, and have the instructions please share, we can assist in packaging the rest. I wonder if there is somone we should cc, that has in a past packaged python packages like this, that would be able to guide us through this over the next two weeks?
OK, my approach has been as follows. First of all, I set up sbuild so that I can build packages cleanly. The Debian Wiki has instructions for this, but their styling is broken, making the code fragments difficult to read: https://wiki.debian.org/sbuild I found that installing sbuild and following the instructions mostly helped. You need to add yourself to the sbuild group and log out and in again, or use newgrp to get immediate access to the group. You also need to create a chroot for sbuild, which I did by copying from the sbuild-createchroot manual page: sudo sbuild-createchroot unstable /srv/chroot/unstable-amd64 \ --alias=sid --alias=UNRELEASED \ http://deb.debian.org/debian For each package, I obtain the unpackaged source code, which is usually just doing a git clone. So, something like this: git clone https://github.com/moinwiki/emeraldtree.git Then, I've made an "original source" archive from that for a given tag. Git's interface for this is cumbersome, of course, but here's what I do: cd emeraldtree git archive --format=tgz \ --prefix=emeraldtree-0.9.2/ \ --output=../emeraldtree_0.9.2.orig.tar.gz \ 0.9.2 This puts the archive in the parent directory. With that, I then found that it rather helped to actually check out the changeset corresponding to the chosen tag: git checkout 0.9.2 Otherwise, the Debian tools complain about the files not matching the "original source" archive. Now, at this point, the actual packaging files need to be written. Apparently, the debmake tool can initiate this process, but I just went and found reasonable enough files from other packages and then made my own packaging files. These all live in the debian directory within the repository being packaged. Here, "apt-get source <package>" for similar packages can be helpful to see what they do. Finally, I run sbuild to perform the build: sbuild . Hopefully, this all works and you get a bunch of files produced in the parent directory. So, in summary, here's the process: cd <name> git archive --format=tgz \ --prefix=<name>-<version>/ \ --output=../<name>_<version>.orig.tar.gz \ <changeset> git checkout <changeset> # <- Here we populate the debian directory. sbuild . I did find the following pages somewhat helpful: https://www.debian.org/doc/manuals/debmake-doc/index.en.html https://wiki.debian.org/Python/LibraryStyleGuide However, the documentation in general suffers from adding even more words and more links to a Web page, and if that doesn't help explain everything, just add even more. Consequently, the above process is probably not optimal, but then that is what happens when confronted with lots of apparent choices and special cases, even though the tooling has tried to automate a lot of the adaptation required. I have put my own packaging attempts here in Mercurial repositories: https://hg.boddie.org.uk/Moin/ What I do, when the process demands the debian directory, is to copy the directory out of my packaging repository: cp -R ../Packaging/emeraldtree/debian . None of this is elegant, but I did make it work in a reasonable amount of time without having to spend even longer second-guessing tools or hunting down the preferred tool or wrapper that would supposedly make it elegant. Anyway, I hope this is informative if not completely helpful. I suppose the next step would be for me to file an "intent to package" (ITP) issue in the Debian bug tracker for each package and then find a packaging mentor. That is what I did last time I packaged anything in Debian. Paul
Hi y'all. I just finished a couple semesters of Python at BYU-Idaho, so I am now a Python expert... haha, not really!!! Actually I do have a couple decades of development in Java. But I am eager to get Moin2 up and running and am willing to start and help out with my, so far limited python 3 skills. I've already cloned the repository at https://github.com/moinwiki/moin.git. And opened it up in VSCode for Windows. After banging on quickstart.py for several hours, I *finally* got it to work. I *think* the problem is with VSCode using PowerShell on Windows 10. ? So, I now have something running. :-) What do I do now? How can I help? I do have some time that I can spare and work on Moin2. Scott.
Add to the list or fix one: https://github.com/moinwiki/moin/issues On Friday, July 22, 2022 at 01:18:30 AM MST, M. Scott Reynolds <mscottreynolds@gmail.com> wrote: Hi y'all. I just finished a couple semesters of Python at BYU-Idaho, so I am now a Python expert... haha, not really!!! Actually I do have a couple decades of development in Java. But I am eager to get Moin2 up and running and am willing to start and help out with my, so far limited python 3 skills. I've already cloned the repository at https://github.com/moinwiki/moin.git. And opened it up in VSCode for Windows. After banging on quickstart.py for several hours, I *finally* got it to work. I *think* the problem is with VSCode using PowerShell on Windows 10. ? So, I now have something running. :-) What do I do now? How can I help? I do have some time that I can spare and work on Moin2. Scott. _______________________________________________ moin-devel mailing list moin-devel@python.org https://mail.python.org/mailman/listinfo/moin-devel
On 2022-07-22 14:23, Roger Haase via moin-devel wrote:
Add to the list or fix one: https://github.com/moinwiki/moin/issues
There has been a certain amount of work done recently on packaging Moin 2 for Debian, and one significant obstacle is Moin's continued reliance on Flask 1.x, where future Debian releases will provide Flask 2.x. I see that there is an issue recorded for such matters: https://github.com/moinwiki/moin/issues/1109 If we can get Moin 2 working with newer Flask versions, its journey into Debian will be quicker and it will potentially get a bit more adoption, which is certainly what is needed at this point. See here for the Debian packaging initiative: https://salsa.debian.org/moin-team Paul
On 7/22/2022 11:23, Paul Boddie wrote:
On 2022-07-22 14:23, Roger Haase via moin-devel wrote:
Add to the list or fix one: https://github.com/moinwiki/moin/issues
There has been a certain amount of work done recently on packaging Moin 2 for Debian, and one significant obstacle is Moin's continued reliance on Flask 1.x, where future Debian releases will provide Flask 2.x. I see that there is an issue recorded for such matters:
https://github.com/moinwiki/moin/issues/1109
If we can get Moin 2 working with newer Flask versions, its journey into Debian will be quicker and it will potentially get a bit more adoption, which is certainly what is needed at this point. See here for the Debian packaging initiative:
https://salsa.debian.org/moin-team
Paul
I know there is a lot of focus getting Moin 2 working for Debian, and for good reasons. But what about the Windows environment? How much demand is there for running Moin 2 on Windows 10? I ask because that is my current setup for running Moin 2; VSCode with Python 3.10. Other than WSL I currently don't have access to a Linux machine. Scott
Most stuff is OS independent, developing on Windows is fine. If you help working on Moin2 and migration to flask 2.x, it will help with Debian packaging. Debian is important for the big public MoinWikis. To find some tasks you can search for issues with the label "good first issue", for more information about development, testing and workflows you can have a look at https://moin-20.readthedocs.io/en/latest/devel/development.html Am 22.07.22 um 20:31 schrieb M. Scott Reynolds:
I know there is a lot of focus getting Moin 2 working for Debian, and for good reasons. But what about the Windows environment? How much demand is there for running Moin 2 on Windows 10? I ask because that is my current setup for running Moin 2; VSCode with Python 3.10. Other than WSL I currently don't have access to a Linux machine.
Oh, lots of good stuff there! I will start with that documentation. Thank you! Scott On 7/22/2022 13:22, Ulrich B. wrote:
Most stuff is OS independent, developing on Windows is fine. If you help working on Moin2 and migration to flask 2.x, it will help with Debian packaging. Debian is important for the big public MoinWikis.
To find some tasks you can search for issues with the label "good first issue", for more information about development, testing and workflows you can have a look at https://moin-20.readthedocs.io/en/latest/devel/development.html
Am 22.07.22 um 20:31 schrieb M. Scott Reynolds:
I know there is a lot of focus getting Moin 2 working for Debian, and for good reasons. But what about the Windows environment? How much demand is there for running Moin 2 on Windows 10? I ask because that is my current setup for running Moin 2; VSCode with Python 3.10. Other than WSL I currently don't have access to a Linux machine.
_______________________________________________ moin-devel mailing list moin-devel@python.org https://mail.python.org/mailman/listinfo/moin-devel
I got to the developer documentation where it has me run checks for coding errors like trailing spaces etc: "./m coding-std". A handful of of "Trailing blanks removed" and "End of line character added..." showed up. What is the priority on fixing stuff like that? Scott. On 7/22/2022 13:36, M. Scott Reynolds wrote:
Oh, lots of good stuff there! I will start with that documentation. Thank you!
Scott
On 7/22/2022 13:22, Ulrich B. wrote:
Most stuff is OS independent, developing on Windows is fine. If you help working on Moin2 and migration to flask 2.x, it will help with Debian packaging. Debian is important for the big public MoinWikis.
To find some tasks you can search for issues with the label "good first issue", for more information about development, testing and workflows you can have a look at https://moin-20.readthedocs.io/en/latest/devel/development.html
See Development — MoinMoin 0.1.dev116+gf3cf86e documentation (moin-20.readthedocs.io) - set options on your favorite editor or IDE - convert tabs to 4 spaces - delete trailing blanks on file save - use unix line endings (use Windows line endings on .bat and .cmd files) - use mono-spaced font for editing Create a pull request to fix the files. Everyone should have the same editor setting to avoid patches showing unrelated changes - one developer adds trailing blanks, next developer removes them. On Friday, July 22, 2022 at 07:21:51 PM MST, M. Scott Reynolds <mscottreynolds@gmail.com> wrote: I got to the developer documentation where it has me run checks for coding errors like trailing spaces etc: "./m coding-std". A handful of of "Trailing blanks removed" and "End of line character added..." showed up. What is the priority on fixing stuff like that? Scott. On 7/22/2022 13:36, M. Scott Reynolds wrote:
Oh, lots of good stuff there! I will start with that documentation. Thank you!
Scott
On 7/22/2022 13:22, Ulrich B. wrote:
Most stuff is OS independent, developing on Windows is fine. If you help working on Moin2 and migration to flask 2.x, it will help with Debian packaging. Debian is important for the big public MoinWikis.
To find some tasks you can search for issues with the label "good first issue", for more information about development, testing and workflows you can have a look at https://moin-20.readthedocs.io/en/latest/devel/development.html
moin-devel mailing list moin-devel@python.org https://mail.python.org/mailman/listinfo/moin-devel
That development link above has not been updated in a while. We use venv not virtualenv; lessc is no longer used; probably more updates are needed. On Saturday, July 23, 2022 at 07:54:55 AM MST, Roger Haase via moin-devel <moin-devel@python.org> wrote: See Development — MoinMoin 0.1.dev116+gf3cf86e documentation (moin-20.readthedocs.io) - set options on your favorite editor or IDE - convert tabs to 4 spaces - delete trailing blanks on file save - use unix line endings (use Windows line endings on .bat and .cmd files) - use mono-spaced font for editing Create a pull request to fix the files. Everyone should have the same editor setting to avoid patches showing unrelated changes - one developer adds trailing blanks, next developer removes them. On Friday, July 22, 2022 at 07:21:51 PM MST, M. Scott Reynolds <mscottreynolds@gmail.com> wrote: I got to the developer documentation where it has me run checks for coding errors like trailing spaces etc: "./m coding-std". A handful of of "Trailing blanks removed" and "End of line character added..." showed up. What is the priority on fixing stuff like that? Scott. On 7/22/2022 13:36, M. Scott Reynolds wrote:
Oh, lots of good stuff there! I will start with that documentation. Thank you!
Scott
On 7/22/2022 13:22, Ulrich B. wrote:
Most stuff is OS independent, developing on Windows is fine. If you help working on Moin2 and migration to flask 2.x, it will help with Debian packaging. Debian is important for the big public MoinWikis.
To find some tasks you can search for issues with the label "good first issue", for more information about development, testing and workflows you can have a look at https://moin-20.readthedocs.io/en/latest/devel/development.html
moin-devel mailing list moin-devel@python.org https://mail.python.org/mailman/listinfo/moin-devel _______________________________________________ moin-devel mailing list moin-devel@python.org https://mail.python.org/mailman/listinfo/moin-devel
Maybe you create an issue in github first and list some of the typical objects, then we can decide what the best solution is. The last time I ran coding-std it found some of the new help pages and no code, if I remember correctly. Am 23.07.22 um 04:21 schrieb M. Scott Reynolds:
I got to the developer documentation where it has me run checks for coding errors like trailing spaces etc: "./m coding-std". A handful of of "Trailing blanks removed" and "End of line character added..." showed up. What is the priority on fixing stuff like that?
participants (4)
-
M. Scott Reynolds -
Paul Boddie -
Roger Haase -
Ulrich B.