http://bugzilla.suse.com/show_bug.cgi?id=1120189 http://bugzilla.suse.com/show_bug.cgi?id=1120189#c16 --- Comment #16 from William Brown <william.brown@suse.com> ---
Arguments why the version update is needed are still missing in this bug report. Also, the .changes file needs to refer to this bug (bsc#1120189). Then I can forward your request internally.
I sent the following text to my manager, so I'll paste it here: """ I’d like to recommend that we upgrade and repackage 389-ds for SLE-15-SP1 over the current version. As you have mentioned, the installed userbase is likely small, so making a change like this is unlikely to be disruptive. Red Hat and upstream design each series (1.4.x.x) to be able to be stable and upgraded over the course of an enterprise distributions life. This means that there should be very little changing from an administrator perspective there. However, a major changed has occured between 1.4.0.x and 1.4.1.x with regard to suse packaging of the 389-ds project. As an upstream core team member, I corrected a number of issues in the way the packaging was performed, and most notably, enabled the python administration toolkit. This has not been reflected in 1.4.0.x versions in SLE yet. It’s important to note, upstream had deprecated the perl admin tools since 1.3.x, So 1.4.x.x with perl was never an upstream supported combination. Enabling the python admin tools makes the setup process easier, and many administrative tasks become far easier to manage. An additional point is (this is my mistake) I have been working with the fantastic suse docs team, and reworking the SLE guide’s 389-ds section (from openldap) to assume the 1.4.x.x was used with the enabled python tools. This means the documentation doesn’t currently align to the packages in SLE-15-SP1. It would be awkward to rewrite the documentation to the old perl tools, only to have to bring it back to the python tools later. A risk to keep in mind is that YaST may or may not work with the python tools, however I am proactively reaching out to the YaST team to discuss this and to work with them to improve this situation. """ It's worth noting that the YAST situation is resolved, with the code approved for merge within the last 24 hours, so hopefully that can be backported without difficulty for yast-auth-server.
Nevertheless please escalate the missing access to build.suse.de. I've never seen issues related to obs login unresolved for that long.
I think it's a ticket system issue. I contacted the buildops team direct and my account works now. -- You are receiving this mail because: You are on the CC list for the bug.