Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

rename of py-MarkupSafe does not reinstall py-markupsafe as a direct dependency of py-Jinja2 #1917

Closed
fichtner opened this issue Dec 16, 2020 · 2 comments

Comments

@fichtner
Copy link
Contributor

Installed packages to be UPGRADED:
	curl: 7.73.0 -> 7.74.0
	dhcp6c: 20200512 -> 20200512_1
	lighttpd: 1.4.55_1 -> 1.4.56
	nss: 3.59 -> 3.60
	openssl: 1.1.1h_1,1 -> 1.1.1i,1
	opnsense: 20.7.6 -> 20.7.7
	pcre2: 10.35 -> 10.36
	py37-Jinja2: 2.11.2 -> 2.11.2_1
	py37-cffi: 1.14.3 -> 1.14.4
	py37-cryptography: 2.6.1 -> 2.9.2
	sqlite3: 3.33.0_1,1 -> 3.34.0,1
	sudo: 1.9.3p1 -> 1.9.4_1
	unbound: 1.12.0 -> 1.13.0

The bad part is that pkg-autoremove will then delete orphaned package py-MarkupSafe

Deinstallation has been requested for the following 2 packages:

Installed packages to be REMOVED:
	py37-MarkupSafe: 1.1.1

And may leave the packages in a non-working state.

pkg-check can fix this, but it probably shouldn't happen.

@fichtner fichtner changed the title rename of py-MarkupSafe does not reinstall py-markupsafe as a direct rependency of py-Jinja2 rename of py-MarkupSafe does not reinstall py-markupsafe as a direct dependency of py-Jinja2 Dec 16, 2020
@fichtner
Copy link
Contributor Author

Proposed a workaround here https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=251900 but the bug definitely needs to be fixed.

@fichtner
Copy link
Contributor Author

Worked around via ports PR.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant