>
> I've prepared an update to the git-ubuntu snap to move from a base of
> core20 to core24.
>
> Automated tests are passing as expected, including various snap
> integration tests. But the interactions between git-ubuntu and the host
> system are complex. I'd appreciate additional testing!
>
> You can update to a build of my core24 snap branch[1] using:
>
> sudo snap refresh git-ubuntu --channel=latest/edge/core24
>
> Please start by running:
>
> git-ubuntu.self-test
Thank you Robie
FYI (so you not only get negative cross test results) the Test ran
successfully for me (Noble):
458 passed, 3 xfailed, 2 warnings in 175.02s (0:02:55)
The two warnings seem to be deprecation warnings that probably happen
for every user:
gitubuntu/__main__.py:7
/snap/git-ubuntu/1613/usr/lib/python3/dist-packages/gitubuntu/__main__.py:7:
DeprecationWarning: pkg_resources is deprecated as an API. See
https://setuptools.pypa.io/en/latest/pkg_resources.html
import pkg_resources
pkg_resources/__init__.py:2871
/snap/git-ubuntu/1613/usr/lib/python3/dist-packages/pkg_resources/__init__.py:2871:
DeprecationWarning: Deprecated call to
`pkg_resources.declare_namespace('logilab')`.
Implementing implicit namespace packages (as specified in PEP 420)
is preferred to `pkg_resources.declare_namespace`. See
https://setuptools.pypa.io/en/latest/references/keywords.html#keyword-namespace-packages
declare_namespace(pkg)
> ...and check that it passes. Then use git-ubuntu like you normally do,
> and please report any regressions.
I ran a few basics (clone and checking the repo matches what I got
last time) which still worked as they did last week with the former
version.
export-orig and merge-start worked for me as well without behaving differently.
Tested on 1.1-55-gcab5296 (1613).
> If no issues are reported, I'll push this to latest/edge in the next few
> days.
>
> Architectures other than amd64 are also now available, but I haven't
> published a core24 branch for those. They will get the build with core24
> shortly after I push to latest/edge in a few days. Until then, builds
> continue to be available following the main branch, based on core20.
>
> Known issues:
>
> Python's keyring storage location has moved from $XDG_DATA_HOME to
> $XDG_CONFIG_HOME. This may result in the the following error:
>
> > RuntimeError: Keyring config exists only in the old location
> > $HOME/.local/share/python_keyring/keyringrc.cfg and should be moved to
> > $HOME/.config/python_keyring/keyringrc.cfg to work with this version
> > of keyring.
>
> This comes from the python3-keyring package in 24.04.
>
> It seems dangerous to migrate this automatically since other tools may
> also keyrings stored in the same places. It's probably best to leave
> this for users to resolve themselves. I think the worst case is that you
> will need to reauthenticate with Launchpad after renaming the old
> keyring away, but please let me know your experience.
>
> When running git-ubuntu.self-test, you will see:
One more thing you want to confirm and explain to lower the
suspicious-eye-brow count.
Whole running importer/tag_test.py the test will use the user's GPG
setup (like when running import locally), so it might pop up a GPG
prompt.
> > python-debianbts 4.0.2 requires pysimplesoap, which is not installed.
> > pip check failed but ignoring due to LP: #2084358
>
> This is caused by python3-debianbts in 24.04 causing pip in 24.04 to
> detect an anomaly. For this reason, the result of the "pip check" test
> in git-ubuntu.self-test is still printed, but the failure is ignored.
>
> Thank you for testing!
>
> Robie
>
> [1] Sources: https://git.launchpad.net/~racb/git-ubuntu/ branch "core24"
> --
> ubuntu-devel mailing list
> ubuntu-devel@lists.ubuntu.com
> Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel
--
Christian Ehrhardt
Director of Engineering, Ubuntu Server
Canonical Ltd
--
ubuntu-devel mailing list
ubuntu-devel@lists.ubuntu.com
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel
