mbox series

[bug#51314,v3,00/21] Add Octoprint (v3)

Message ID 20211227233044.26475-1-monego@posteo.net
Headers show
Series Add Octoprint (v3) | expand

Message

Vinicius Monego Dec. 27, 2021, 11:30 p.m. UTC 
This is an update of the series after the core-updates-frozen merge. All packages are linted. The feedparser and flask updates were removed because they were pushed in other patches.

A few package versions were bumped. The server and UI seem to work, but still I can't test the full functionality of the program.

Vinicius Monego (21):
  gnu: Add python-sarge.
  gnu: Add python-pylru.
  gnu: Add python-pyscss.
  gnu: Add python-flask-assets.
  gnu: Add python-zipstream-new.
  gnu: Add python-executing.
  gnu: Add python-sentry-sdk.
  gnu: Add python-pytest-doctest-custom.
  gnu: python-feedparser: Enable tests.
  gnu: python-netifaces: Update to 0.11.0.
  gnu: python-websocket-client: Update to 0.59.0.
  gnu: python-pkginfo: Update to 1.8.2.
  gnu: python-watchdog: Update to 2.1.6.
  gnu: python-colorlog: Update to 6.6.0.
  gnu: python-zeroconf: Update to 0.38.1.
  gnu: python-wrapt: Update to 1.13.3.
  gnu: python-wrapt: Enable tests.
  gnu: Add octoprint-pisupport.
  gnu: Add octoprint-firmwarecheck.
  gnu: Add octoprint-filecheck.
  gnu: Add octoprint.

 gnu/packages/printers.scm     | 194 +++++++++++++++++++++-
 gnu/packages/python-check.scm |  29 ++++
 gnu/packages/python-web.scm   |  76 ++++++++-
 gnu/packages/python-xyz.scm   | 304 ++++++++++++++++++++++++++--------
 gnu/packages/web.scm          |  17 +-
 5 files changed, 542 insertions(+), 78 deletions(-)


base-commit: 28b477cb2e5d9185da16f305caff15809dfa06f3

Comments

Nicolas Goaziou Jan. 7, 2022, 9:02 p.m. UTC | #1 
Hello,

Vinicius Monego <monego@posteo.net> writes:

> This is an update of the series after the core-updates-frozen merge. All packages are linted. The feedparser and flask updates were removed because they were pushed in other patches.
>
> A few package versions were bumped. The server and UI seem to work,
> but still I can't test the full functionality of the program.

Thank you.

However this patchset cannot be applied on master branch because
updating python-wrapt entails rebuilding 300+ Python packages.

Could you rebase it on staging branch and send it again?

Regards,
Vinicius Monego Jan. 8, 2022, 5:41 a.m. UTC | #2 
Em sex, 2022-01-07 às 22:02 +0100, Nicolas Goaziou escreveu:
> Hello,
> 
> Vinicius Monego <monego@posteo.net> writes:
> 
> > This is an update of the series after the core-updates-frozen
> > merge. All packages are linted. The feedparser and flask updates
> > were removed because they were pushed in other patches.
> > 
> > A few package versions were bumped. The server and UI seem to work,
> > but still I can't test the full functionality of the program.
> 
> Thank you.
> 
> However this patchset cannot be applied on master branch because
> updating python-wrapt entails rebuilding 300+ Python packages.
> 
> Could you rebase it on staging branch and send it again?
> 
> Regards,

If the problem is just wrapt it can be skipped, then one line has to be
changed in octoprint's 'relax-version-requirements phase. All tests
still pass.

It's strange though, there are many errors in the '$ octoprint serve'
output about plugin files not being found because it's looking for
static files in different paths inside the same store item, and
flask2/jinja3 errors. Upstream only tests in flask 1 so maybe it's not
yet compatible with the flask2 that came with the c-u-f merge. I don't
know how much this affects usability, the server is still operational
and the UI loads. It would be good if someone who uses it daily could
report on how well the package works.

Maybe apply the patches before wrapt and leave this issue open until
the octoprint messages are worked on?
Nicolas Goaziou Jan. 11, 2022, 5:27 p.m. UTC | #3 
Hello,

Vinicius Monego <monego@posteo.net> writes:

> It's strange though, there are many errors in the '$ octoprint serve'
> output about plugin files not being found because it's looking for
> static files in different paths inside the same store item, and
> flask2/jinja3 errors. Upstream only tests in flask 1 so maybe it's not
> yet compatible with the flask2 that came with the c-u-f merge. I don't
> know how much this affects usability, the server is still operational
> and the UI loads. It would be good if someone who uses it daily could
> report on how well the package works.

I cannot tell, I don't use this.

> Maybe apply the patches before wrapt and leave this issue open until
> the octoprint messages are worked on?

OK. I applied the patches up to the python-zeroconf update. Thanks!

I let you decide if this bug should be closed and a new one opened.

Regards,