|
Bugzilla – Full Text Bug Listing |
| Summary: | Provide yast2-printer and yast2-scanner from SLE12 in openSUSE 13.2 | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE Distribution | Reporter: | Johannes Meixner <jsmeix> |
| Component: | YaST2 | Assignee: | Josef Reidinger <jreidinger> |
| Status: | RESOLVED FIXED | QA Contact: | Jiri Srain <jsrain> |
| Severity: | Normal | ||
| Priority: | P5 - None | CC: | dieter.jurzitza, forgotten_A9YPvv3rEp, jsmeix, maintenance, mgriessmeier |
| Version: | 13.2 RC 1 | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | openSUSE 13.2 | ||
| Whiteboard: | |||
| Found By: | --- | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
|
Description
Johannes Meixner
2014-10-27 09:48:47 UTC
*** Bug 902649 has been marked as a duplicate of this bug. *** Johannes - yast team automatic submit the latest version in git to factory. If something should be included in os13.2 and coolo do not pick it, then you should discuss it with him. see https://ci.opensuse.org/view/Yast/job/yast-printer-master/ latest version submitted is 3.1.1 and there is no version change, so it is not forwarded to factory. Only FYI: Currently I have no time (other issues with higher priority)... *** Bug 888782 has been marked as a duplicate of this bug. *** *** Bug 907451 has been marked as a duplicate of this bug. *** Only FYI: Pending GitHub pull request for yast2-scanner https://github.com/yast/yast-scanner/pull/3 Only FYI: Tried YaST GitHub pull request (comment#6) but failed to "fix mergebility". Currently I have no time for further fighting with YaST GitHub (other issues have higher priority). I wished there was a real OBS devel project for YaST that behaves as usual OBS devel projects do i.e. where branch and submitrequest "just works". I will fix it. Johannes I check git branch and SLE 12 branch do not contain anything that is not in opensuse or master. Do you have own secret source for SLE_12??? Reason why we have this setup is that we generate all stuff automatic from git repository, so as long as git repo on github in yast organization is up-todate, then also packages in BS is up-todate. I never found the time to make myself familiar with the YaST development on Github. I know I should have done it but there never was time for it because fixing this or that stuff always has higher priority. Therefore I did the changes that I neeed to do for SLE12 in a "quick and dirty" way in the source packages of our internal build service via usual branch and submitrequest. Accordingly the original "secret source for SLE_12" are our official source packages for SLE12. After SLE12 was rereased I made those sources public accessible in the openSUSE build service: yast2-printer at home:jsmeix yast2-printer-sle12 and Printing yast2-printer-SLE12 yast2-scanner only at home:jsmeix yast2-scanner-sle12 Same sources are also in SUSE:SLE-12:GA/yast2-printer and SUSE:SLE-12:GA/yast2-scanner (see comment#0). Johannes - OK, thanks for pointers. I will try to make it in sync. If you want quickly get familiar with yast development on github it is easy. Just create pull request as you did and after merge to master it will go to opensuse. For other branches, you need to call `rake osc:sr` to create maintenance request. We do not do it automatic as it overload maintenance team. I create pull requests to apply patches to git: https://github.com/yast/yast-printer/pull/4 https://github.com/yast/yast-scanner/pull/4 After review it will be merged and then I merge it to opensuse 13.2 and master branch. And then I probably create maintenance request for these two modules for opensuse 13.2 maintenance team - can I send fixes from SLE-12 for yast2-scanner and yast2-printer to opensuse 13.2? I think it much improve user experience. pr for opensuse 13.2 branch https://github.com/yast/yast-scanner/pull/5 https://github.com/yast/yast-printer/pull/5 and ones for master https://github.com/yast/yast-scanner/pull/6 https://github.com/yast/yast-printer/pull/6 after merge to master it will be automatically in TW and factory maintenance - still waiting for response Sorry for late response... Feel free to submit an update scanner: created request id Request: #283076 printer: created request id Request: #283077 |