|
Bugzilla – Full Text Bug Listing |
| Summary: | django-admin does not work, django-admin.py does | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE Distribution | Reporter: | Oliver Kurz <okurz> |
| Component: | Development | Assignee: | Thomas Bechtold <tbechtold> |
| Status: | VERIFIED FIXED | QA Contact: | E-mail List <qa-bugs> |
| Severity: | Normal | ||
| Priority: | P5 - None | CC: | aplanas, dimstar, dmueller, maintenance, okurz |
| Version: | Leap 42.1 | ||
| Target Milestone: | --- | ||
| Hardware: | x86-64 | ||
| OS: | All | ||
| Whiteboard: | |||
| Found By: | --- | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
|
Description
Oliver Kurz
2015-10-27 12:57:52 UTC
@Oliver: Can you please post the traceback? I can't reproduce it here. Thomas: try: zypper rm python-setuptools - then you can reproduce it too it bascically boils down to: ImportError: No module named pkg_resources (In reply to Dominique Leuenberger from comment #2) > Thomas: try: zypper rm python-setuptools - then you can reproduce it too > > it bascically boils down to: > > ImportError: No module named pkg_resources Ah. Now I get it. It's a missing runtime requirement to python-setuptools . Created a SR: https://build.opensuse.org/request/show/343354 @Oliver: Can you test it please? Will do. I guess the right procedure is: 1. reproduce the error 2. add home:tbechtold:branches:openSUSE:Leap:42.1:Update repo 3. (re-)install package (confirm it also pulls in python-setuptools) 4. verify error disappeared right? I am new to the process but will learn. Hopefully next time I could do a package update (request) myself :-) (In reply to Oliver Kurz from comment #5) > Will do. I guess the right procedure is: > 1. reproduce the error > 2. add home:tbechtold:branches:openSUSE:Leap:42.1:Update repo > 3. (re-)install package (confirm it also pulls in python-setuptools) > 4. verify error disappeared > > right? Yes. > I am new to the process but will learn. Hopefully next time I could do a > package update (request) myself :-) Great! :) going to https://build.opensuse.org/project/repositories/home:tbechtold:branches:openSUSE:Leap:42.1:Update and clicking "Go to download repository" for "standard" gives me a 404. What am I doing wrong? (In reply to Oliver Kurz from comment #7) > going to > https://build.opensuse.org/project/repositories/home:tbechtold:branches: > openSUSE:Leap:42.1:Update and clicking "Go to download repository" for > "standard" gives me a 404. What am I doing wrong? Nothing. Publishing was disabled. Sorry. Should be available now. https://build.opensuse.org/request/show/343354 verified. So, what is the next step? Who/how can accept the request? (In reply to Oliver Kurz from comment #9) > https://build.opensuse.org/request/show/343354 verified. > > So, what is the next step? Who/how can accept the request? This is part of https://en.opensuse.org/Portal:Maintenance The maintenance team will review, accept, QA, release. The request is already accepted and the update will be release after a testing-period of ~7 days. Removing needinfo. Thanks! Update released for openSUSE Leap 42.1. Resolved fixed. openSUSE-RU-2015:2031-1: An update that has one recommended fix can now be installed. Category: recommended (moderate) Bug References: 952198 CVE References: Sources used: openSUSE Leap 42.1 (src): python-Django-1.8.4-3.1 LGTM This is an autogenerated message for OBS integration: This bug (952198) was mentioned in https://build.opensuse.org/request/show/559133 Factory / python-Django1 openSUSE-SU-2023:0077-1: An update that fixes 11 vulnerabilities is now available. Category: security (important) Bug References: 1077714,1102680,1208082,937524,952198,988420 CVE References: CVE-2015-3982,CVE-2015-5145,CVE-2015-5963,CVE-2017-12794,CVE-2017-7233,CVE-2017-7234,CVE-2018-14574,CVE-2018-6188,CVE-2018-7536,CVE-2018-7537,CVE-2023-24580 JIRA References: Sources used: SUSE Package Hub for SUSE Linux Enterprise 12 (src): python-Django-1.11.15-2.1 |