July 2017 - openSUSE Release Team - openSUSE Mailing Lists

[opensuse-releaseteam] Future home for osc-plugin-factory package based on upstreamed spec
by Jimmy Berry 27 Jul '17

27 Jul '17

I posted the following as a comment on NON_Public:infrastructure/osc-plugin- factory, but have not received a response so I emailed those who have made a revision to the package. Note that I have cc'd the openSUSE release team's mailing list which is public. ---- I reworked and upstreamed the spec. I plan to improve it further there. As such it would make sense to replace this package with the one build from the new spec as it is also auto updated. It seems this repo contains some of the python dependencies needed to build for SLE, but lacks some of the obs service deps. If you are already maintaining deps and such for SLE the[n] perhaps this would be the place, but considering the tool is open source it can be built in openSUSE:Tools if the required deps are provided there for SLE and maintained. Do you have a preference? I branched the package from openSUSE:Tools on IBS in https://build.suse.de/ package/show/home:jberry:branches:NON_Public:infrastructure/openSUSE-release- tools where you can see it properly builds. I also have an issue to figure out the right home if you were rather respond there: https://github.com/openSUSE/osc-plugin-factory/issues/1007. It may also make sense to add some obsoletes and/or recommends depending on how widely this package was used. ---- You can see the unresolvable deps for SLE in the project, principally python- cmdln. Note that spec has a number of %if 0%{?is_opensuse} conditionals that reduce the dependencies by among other things disabling running of the test suite during %check. It would seem preferable to run those, but those dependencies need to be maintained for SLE. My understanding is that some of the tools are deployed against IBS using this package which would need to be switched over to the new one. If that is the only real use-case perhaps a manual switch is easy enough, otherwise it may require a proper upgrade path. Given there are plans to deploy more tools against IBS it would be preferable to do so out of the updated package. I have plans to standardize the service files used for openSUSE so that they will apply easily for IBS. -- Jimmy -- To unsubscribe, e-mail: opensuse-releaseteam+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-releaseteam+owner(a)opensuse.org

1 0

[opensuse-releaseteam] New Repo Checker Status
by Jimmy Berry 13 Jul '17

13 Jul '17

opensuse-releaseteam, In order to finish things up in regards to the repo checker (#964) [1] I will summarize the situation in the hopes of agreeing on a path forward. As noted [2] on the pull request I had frozen the existing osc-check_repo.py on packagelists in preparation for merging with delayed deployment for Factory. The changes conflicted with the AppArmor profile and were rolled back by Dominique. The new repo-checker user on OBS and _opensuse.org-repo-checker along with new services have remained on packagelists. The new repo checker has been running against Leap:42.3 for the last two weeks and has managed to discover a few legitimate problems. One of the notifications generated a discussion that resulted in a correction without interaction by the release team! The remaining areas for discussion have corresponding issues: - #973: repo_checker: speed up reviews by comparing has of staging project psuedometa - #974: repo_checker: invoke mirror, cycle, and install checks in parallel - #978: repo-checker.pl: detect/handle corrupt package snippet and general error handling - #979: repo_checker: cycles discussion - #980: repo_checker: include non-targeted package messages from installcheck The last two are the primary issues of interest. The cycles difference should not be too common and has a set of pros and cons associated with the changes. The primary blocker is the the inclusion of all installcheck/fileconflict problems from letter stagings. This change is again beneficial in detecting problems encountered by more complex packaging, but does not pass for both Leap:42.3 nor Factory. I have sent a number of SRs to resolve some of the issues, but the rest need to be resolved before the new repo checker will accept letter stagings. My suggested path forward would be to continue making the fixes rather than relaxing the check and resume the freezing of old repo checker. Max had mentioned the AppArmor profile was relaxed/disabled which would be good to confirm. I will likely look around on packagelists and make the change again. Once all the issues have been resolved in Factory I suggest we add both repo checker users for review and see that the results make sense before disabling the old repo checker. Given that I encountered the package snippet corruption bug twice more during local testing it definitely occurs. For those not familiar I also found a case in the deployed cache on packagelists. Anytime the corruption is encountered the old repo checker will accept all reviews regardless of issues. As such it makes sense to target switching to the new repo checker as soon as possible. The last minor discussion point is that the ReviewBot currently operates either on a project + request type or reviews targeting a user/group. The current repo checker uses the user/group target, but that would mix reviews for Factory and Leap in one cycle. The ReviewBot could be changed (or extended) to allow filtering by project in addition to review target or all reviews could be run in the same cycle (same service on packagelists). Using the project method would need to be tweaked to allow for multiple request types (as currently it has to be run twice, once for submit and once for delete), but that method currently includes already reviewed requests which adds to clutter the repo checker has to dig through. Adding the project filter to review target method likely makes sense, but perhaps there are some unintended side-effects to other bots? Additionally, it will mean that two repo checkers may run at the same time which locks up 100% cpu across the two cores on packagelists which makes the box a tad unresponsive. Either packagelists needs increased resources, the new repo checker should find a new home, or we accept the situation. Given all the other tools are split out per project I am leaning towards adding the project filter. [1] https://github.com/openSUSE/osc-plugin-factory [2] https://github.com/openSUSE/osc-plugin-factory/pull/964#issuecomment-311499… I look forward to your thoughts, -- Jimmy -- To unsubscribe, e-mail: opensuse-releaseteam+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-releaseteam+owner(a)opensuse.org

3 6

[opensuse-releaseteam] Leap 42.3 status update w27/2017 - final deadline approaching
by Ludwig Nussel 05 Jul '17

05 Jul '17

Hi, Leap 42.3 development is finishing. If you didn't dare to install the new release it yet, please do so before it's really too late. File bug reports¹ for issues you find via bugzilla ASAP. There's basically only next week left to apply fixes! The test plan for manual testing² showed too little coverage especially in the areas of - dual boot with Windows - autoyast - non-english locales - development stacks like rails, salt etc So if you are on 42.3 and can cover those or other areas, please do so and take notes in the plan. Remaining build failures are about to be solved. So far nobody fixed the following packages, so the only choice left is to drop them: - ldapjdk - libatlas3 - qtsharp There will be a full rebuild on the weekend to make sure we are in a consistent state. Next week is left to integrate final bug fixes. *Package submissions after July 16th may not be considered anymore.* As usual, please contact the release team³ if your submission needs attention. cu Ludwig [1] https://en.opensuse.org/openSUSE:Submitting_bug_reports [2] https://docs.google.com/spreadsheets/d/1AGKijKpKiJCB616-bHVoNQuhWHpQLHPWCb3… [3] mailto:opensuse-releaseteam@opensuse.org -- (o_ Ludwig Nussel //\ V_/_ http://www.suse.com/ SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg) -- To unsubscribe, e-mail: opensuse-releaseteam+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-releaseteam+owner(a)opensuse.org

1 0