1OSC(1) User Commands OSC(1)
2
3
4
6 osc - openSUSE build service command-line tool.
7
9 osc [GLOBALOPTS] SUBCOMMAND [OPTS] [ARGS...]
10 osc help SUBCOMMAND
11
13 openSUSE build service command-line tool.
14
15
16 COMMANDS
17 add Mark files to be added upon the next commit
18
19 In case a URL is given the file will get downloaded and regis‐
20 tered to be downloaded by the server as well via the down‐
21 load_url source service.
22
23 This is recommended for release tar balls to track their source
24 and to help others to review your changes esp. on version
25 upgrades.
26
27 usage:
28 osc add URL [URL...]
29 osc add FILE [FILE...]
30
31
32 addchannels
33 Add channels to project.
34
35 The command adds all channels which are defined to be used for a
36 given source package. The source link target is used to lookup
37 the channels. The command can be used for a certain package or
38 for all in the specified project.
39
40 In case no channel is defined the operation is just returning.
41
42 Examples:
43 osc addchannels [PROJECT [PACKAGE]] Options:
44 -h, --help show this help message and exit
45 -e, --enable-all
46 Enable all added channels including the ones
47 disabled
48 by default.
49 -s, --skip-disabled
50 Skip disabled channels. Otherwise the source
51 gets
52 added, but not the repositories.
53
54
55
56 addcontainers
57 Add maintained containers for a give package
58
59 The command adds all containers which are marked as maintained
60 and contain an rpm originating from the specified source pack‐
61 age.
62
63 Examples:
64 osc addcontainers [PROJECT PACKAGE] Options:
65 -h, --help show this help message and exit
66 --extend-package-names
67 Extend packages names with project name as suf‐
68 fix
69
70
71
72 addremove (ar)
73 Adds new files, removes disappeared files
74
75 Adds all files new in the local copy, and removes all disap‐
76 peared files.
77
78 ARG, if specified, is a package working copy.
79
80 Usage:
81 osc addremove [ARGS...]
82
83 Options:
84 -h, --help show this help message and exit
85 -r, --recursive
86 If CWD is a project dir then scan all package
87 dirs as
88 well
89
90
91
92 aggregatepac
93 "Aggregate" a package to another package
94
95 Aggregation of a package means that the build results (binaries)
96 of a package are basically copied into another project. This
97 can be used to make packages available from building that are
98 needed in a project but available only in a different project.
99 Note that this is done at the expense of disk space. See
100 http://en.opensuse.org/openSUSE:Build_Ser‐
101 vice_Tips_and_Tricks#link_and_aggregate for more information.
102
103 The DESTPAC name is optional; the source packages' name will be
104 used if DESTPAC is omitted.
105
106 usage:
107 osc aggregatepac SOURCEPRJ SOURCEPAC DESTPRJ [DESTPAC]
108 Options:
109 -h, --help show this help message and exit
110 -d, --disable-publish
111 disable publishing of the aggregated package
112 -m SRC=TARGET[,SRC=TARGET], --map-repo=SRC=TARGET[,SRC=TAR‐
113 GET]
114 Allows repository mapping(s) to be given as
115 SRC=TARGET[,SRC=TARGET]
116 --nosources
117 ignore source packages when copying build
118 results to
119 destination project
120
121
122
123 api Issue an arbitrary request to the API
124
125 Useful for testing.
126
127 URL can be specified either partially (only the path component),
128 or fully with URL scheme and hostname ('http://...').
129
130 Note the global -A and -H options (see osc help).
131
132 Examples:
133 osc api /source/home:user
134 osc api -X PUT -T /etc/fstab source/home:user/test5/myfstab
135 osc api -e /configuration
136
137 Usage:
138 osc api URL
139
140 Options:
141 -h, --help show this help message and exit
142 -a NAME STRING, --add-header=NAME STRING
143 add the specified header to the request
144 -T FILE, -f FILE, --file=FILE
145 specify filename to upload, uses PUT mode by
146 default
147 -d STRING, --data=STRING
148 specify string data for e.g. POST
149 -e, --edit GET, edit and PUT the location
150 -X HTTP_METHOD, -m HTTP_METHOD, --method=HTTP_METHOD
151 specify HTTP method to use (GET|PUT|DELETE|POST)
152
153
154
155 branch (bco, branchco, getpac)
156 Branch a package
157
158 [See http://en.opensuse.org/openSUSE:Build_Service_Collaboration
159 for information on this topic.]
160
161 Create a source link from a package of an existing project to a
162 new subproject of the requesters home project (home:branches:)
163
164 The branched package will live in
165 home:USERNAME:branches:PROJECT/PACKAGE if nothing else spec‐
166 ified.
167
168 With getpac or bco, the branched package will come from one of
169 openSUSE:Factory (list of projects from oscrc:get‐
170 pac_default_project) if nothing else is specfied on the command
171 line.
172
173 In case of branch errors, where the source has currently merge
174 conflicts use --linkrev=base option.
175
176 usage:
177 osc branch
178 osc branch SOURCEPROJECT SOURCEPACKAGE
179 osc branch SOURCEPROJECT SOURCEPACKAGE TARGETPROJECT
180 osc branch SOURCEPROJECT SOURCEPACKAGE TARGETPROJECT TARGET‐
181 PACKAGE
182 osc getpac SOURCEPACKAGE
183 osc bco ... Options:
184 -h, --help show this help message and exit
185 --add-repositories-rebuild=add_repositories_rebuild
186 specify the used rebuild strategy for new repos‐
187 itories
188 --add-repositories-block=add_repositories_block
189 specify the used block strategy for new reposi‐
190 tories
191 --linkrev=linkrev
192 specify the used revision in the link target.
193 -r rev, --revision=rev
194 branch against a specific revision
195 -N, --new-package
196 create a branch pointing to a not yet existing
197 package
198 -M, --maintenance
199 Create project and package in maintenance mode
200 -m TEXT, --message=TEXT
201 specify message TEXT
202 --noaccess Create a hidden project
203 --extend-package-names
204 Extend packages names with project name as suf‐
205 fix
206 --add-repositories
207 Add repositories to target project (happens by
208 default
209 when project is new)
210 -f, --force
211 force branch, overwrite target
212 -c, --checkout
213 Checkout branched package afterwards using "co
214 -e
215 -S"('osc bco' is a shorthand for this option)
216 --nodevelproject
217 do not follow a defined devel project (primary
218 project
219 where a package is developed)
220
221
222
223 browse opens browser
224
225 usage:
226 osc browse [PROJECT [PACKAGE]]
227
228
229
230 build Build a package on your local machine
231
232 You need to call the command inside a package directory, which
233 should be a buildsystem checkout. (Local modifications are
234 fine.)
235
236 The arguments REPOSITORY and ARCH can be taken from the first
237 two columns of the 'osc repos' output. BUILD_DESCR is either a
238 RPM spec file, or a Debian dsc file.
239
240 The command honors packagecachedir, build-root and build-uid
241 settings in oscrc, if present. You may want to set su-wrapper =
242 'sudo' in oscrc, and configure sudo with option NOPASSWD for
243 /usr/bin/build.
244
245 If neither --clean nor --noinit is given, build will reuse an
246 existing build-root again, removing unneeded packages and add
247 missing ones. This is usually the fastest option.
248
249 If the package doesn't exist on the server please use the
250 --local-package option. If the project of the package doesn't
251 exist on the server please use the --alternative-project <alter‐
252 native-project> option: Example:
253 osc build [OPTS] --alternative-project openSUSE:10.3 stan‐
254 dard i586 BUILD_DESCR
255
256 usage:
257 osc build [OPTS] REPOSITORY ARCH BUILD_DESCR
258 osc build [OPTS] REPOSITORY ARCH
259 osc build [OPTS] REPOSITORY (ARCH = hostarch, BUILD_DESCR is
260 detected automatically)
261 osc build [OPTS] ARCH (REPOSITORY = build_repository (config
262 option), BUILD_DESCR is detected automatically)
263 osc build [OPTS] BUILD_DESCR (REPOSITORY = build_repository
264 (config option), ARCH = hostarch)
265 osc build [OPTS] (REPOSITORY = build_repository (config
266 option), ARCH = hostarch, BUILD_DESCR is detected automatically)
267
268 # Note: # Configuration can be overridden by envvars, e.g. #
269 OSC_SU_WRAPPER overrides the setting of su-wrapper. #
270 OSC_BUILD_ROOT overrides the setting of build-root. # OSC_PACK‐
271 AGECACHEDIR overrides the setting of packagecachedir.
272
273 Options:
274 -h, --help show this help message and exit
275 --nopreinstallimage, --no-preinstallimage
276 Do not use preinstall images for creating the
277 build
278 root.
279 --trust-all-projects
280 trust packages from all projects
281 --host=HOST
282 perform the build on a remote server -
283 user@server:~/remote/directory
284 --oldpackages=DIR
285 take previous build from DIR (special values:
286 _self,
287 _link)
288 --download-api-only
289 only fetch packages from the api
290 --disable-cpio-bulk-download
291 disable downloading packages as cpio archive
292 from api
293 --release=N
294 set release number of the package to N
295 -b, --baselibs
296 Create -32bit/-64bit/-x86 rpms for other archi‐
297 tectures
298 --disable-debuginfo
299 disable build of debuginfo packages
300 -d, --debuginfo
301 also build debuginfo sub-packages
302 --alternative-project=PROJECT
303 specify the build target project
304 --target=TARGET
305 define target platform
306 --vm-telnet=TELNET
307 Launch a telnet server inside of VM build
308 --vm-type=TYPE
309 use VM type TYPE (e.g. kvm)
310 --vm-memory=MEMORY
311 use given MB for VM
312 --linksources
313 use hard links instead of a deep copied source
314 --local-package
315 build a package which does not exist on the
316 server
317 --build-uid=uid:gid|"caller"
318 specify the numeric uid:gid pair to assign to
319 the
320 unprivileged "abuild" user or use "caller" to
321 use the
322 current user uid:gid
323 --userootforbuild
324 Run build as root. The default is to build as
325 unprivileged user. Note that a line "# noroot‐
326 forbuild"
327 in the spec file will invalidate this option.
328 --build-opt=OPT
329 pass option OPT to the build command
330 --define='X Y'
331 define macro X with value Y
332 --without=X
333 disable feature X for build
334 --with=X enable feature X for build
335 --ccache use ccache to speed up rebuilds
336 --icecream=N
337 use N parallel build jobs with icecream
338 -t N, --threads=N
339 Compile with N threads
340 -j N, --jobs=N
341 Compile with N jobs
342 --root=ROOT
343 Build in specified directory
344 -x PAC, --extra-pkgs=PAC
345 Add this package when installing the build-root
346 -M MPAC, --multibuild-package=MPAC
347 Build the specified multibuild package
348 -k DIR, --keep-pkgs=DIR
349 Save built packages into this directory
350 -p DIR, --prefer-pkgs=DIR
351 Prefer packages from this directory when
352 installing
353 the build-root
354 --noservice, --no-service
355 Skip run of local source services as specified
356 in
357 _service file.
358 --no-verify, --noverify
359 Skip signature verification (via pgp keys) of
360 packages
361 used for build. (Global config in oscrc: no_ver‐
362 ify)
363 --nochecks, --no-checks
364 Do not run build checks on the resulting pack‐
365 ages.
366 --noinit, --no-init
367 Skip initialization of build root and start with
368 build
369 immediately.
370 --overlay=OVERLAY
371 Copy overlay filesystem to buildroot after
372 installing
373 all RPMs .
374 --rsync-dest=RSYNCDESTPATH
375 Copy folder to buildroot after installing all
376 RPMs.
377 Use together with --rsync-src. This is the path
378 on the
379 TARGET filesystem e.g.
380 /usr/src/packages/BUILD/linux-2.6 .
381 --rsync-src=RSYNCSRCPATH
382 Copy folder to buildroot after installing all
383 RPMs.
384 Use together with --rsync-dest. This is the path
385 on
386 the HOST filesystem e.g. /tmp/linux-kernel-tree.
387 It
388 defines RSYNCDONE 1 .
389 --no-changelog
390 don't update the package changelog from a
391 changes file
392 -l, --preload
393 Preload all files into the cache for offline
394 operation
395 -o, --offline
396 Start with cached prjconf and packages without
397 contacting the api server
398 --clean Delete old build root before initializing it
399
400
401
402 buildconfig
403 Shows the build config
404
405 Shows the build configuration which is used in building a pack‐
406 age. This command is mostly used internally by the 'build' com‐
407 mand.
408
409 The returned data is the project-wide build configuration in a
410 format which is directly readable by the build script. It con‐
411 tains RPM macros and BuildRequires expansions, for example.
412
413 The argument REPOSITORY an be taken from the first column of the
414 'osc repos' output.
415
416 usage:
417 osc buildconfig REPOSITORY (in pkg or
418 prj dir)
419 osc buildconfig PROJECT REPOSITORY
420
421
422 buildhistory (buildhist)
423 Shows the build history of a package
424
425 The arguments REPOSITORY and ARCH can be taken from the first
426 two columns of the 'osc repos' output.
427
428 usage:
429 osc buildhist REPOSITORY ARCHITECTURE
430 osc buildhist PROJECT PACKAGE REPOSITORY ARCHITECTURE
431 Options:
432 -h, --help show this help message and exit
433 -M MPAC, --multibuild-package=MPAC
434 Show the buildhistory of the specified multi‐
435 build
436 package
437 -l limit, --limit=limit
438 for setting the number of results
439 --csv generate output in CSV (separated by |)
440
441
442
443 buildinfo
444 Shows the build info
445
446 Shows the build "info" which is used in building a package.
447 This command is mostly used internally by the 'build' subcom‐
448 mand. It needs to be called from within a package directory.
449
450 The BUILD_DESCR argument is optional. BUILD_DESCR is a local RPM
451 specfile or Debian "dsc" file. If specified, it is sent to the
452 server, and the buildinfo will be based on it. If the argument
453 is not supplied, the buildinfo is derived from the specfile
454 which is currently on the source repository server.
455
456 The returned data is XML and contains a list of the packages
457 used in building, their source, and the expanded BuildRequires.
458
459 The arguments REPOSITORY and ARCH are optional. They can be
460 taken from the first two columns of the 'osc repos' output. If
461 not specified, REPOSITORY defaults to the 'build_repository'
462 config entry in your 'oscrc' and ARCH defaults to your host
463 architecture.
464
465 usage:
466 in a package working copy:
467 osc buildinfo [OPTS] REPOSITORY ARCH BUILD_DESCR
468 osc buildinfo [OPTS] REPOSITORY (ARCH = hostarch,
469 BUILD_DESCR is detected automatically)
470 osc buildinfo [OPTS] ARCH (REPOSITORY = build_repository
471 (config option), BUILD_DESCR is detected automatically)
472 osc buildinfo [OPTS] BUILD_DESCR (REPOSITORY =
473 build_repository (config option), ARCH = hostarch)
474 osc buildinfo [OPTS] (REPOSITORY = build_repository
475 (config option), ARCH = hostarch, BUILD_DESCR is detected auto‐
476 matically)
477 Note: if BUILD_DESCR does not exist locally the remote
478 BUILD_DESCR is used
479
480 osc buildinfo [OPTS] PROJECT PACKAGE REPOSITORY ARCH
481 [BUILD_DESCR]
482
483 Options:
484 -h, --help show this help message and exit
485 -p DIR, --prefer-pkgs=DIR
486 Prefer packages from this directory when
487 installing
488 the build-root
489 -x PAC, --extra-pkgs=PAC
490 Add this package when computing the buildinfo
491 -M MPAC, --multibuild-package=MPAC
492 Show the buildinfo of the specified multibuild
493 package
494 --alternative-project=PROJECT
495 specify the build target project
496 -d, --debug
497 verbose output of build dependencies
498
499
500
501 buildlog (bl, blt, buildlogtail)
502 Shows the build log of a package
503
504 Shows the log file of the build of a package. Can be used to
505 follow the log while it is being written. Needs to be called
506 from within a package directory.
507
508 When called as buildlogtail (or blt) it just shows the end of
509 the logfile. This is useful to see just a build failure rea‐
510 sons.
511
512 The arguments REPOSITORY and ARCH are the first two columns in
513 the 'osc results' output. If the buildlog url is used buildlog
514 command has the same behavior as remotebuildlog.
515
516 Usage:
517 osc buildlog [ARGS...]
518
519 [REPOSITORY ARCH | BUILDLOGURL] Options:
520 -h, --help show this help message and exit
521 -s, --strip-time
522 strip leading build time from the log
523 -o OFFSET, --offset=OFFSET
524 get log start or end from the offset
525 -M MPAC, --multibuild-package=MPAC
526 get log of the specified multibuild package
527 -l, --last Show the last finished log file
528
529
530
531 cat (blame, less)
532 Output the content of a file to standard output
533
534 Examples:
535 osc cat file
536 osc cat project package file
537 osc cat project/package/file
538 osc cat http://api.opensuse.org/build/.../_log
539 osc cat http://api.opensuse.org/source/../_link
540
541 osc less file
542 osc less project package file
543
544 osc blame file
545 osc blame project package file
546
547 Usage:
548 osc cat [ARGS...]
549
550 Options:
551 -h, --help show this help message and exit
552 -M, --meta list meta data files
553 -D, --deleted
554 access file in a deleted package
555 -u, --unexpand
556 always work with unexpanded packages.
557 -e, --expand
558 (default) force expansion of linked packages.
559 -r rev, --revision=rev
560 print out the specified revision
561
562
563
564 changedevelrequest (changedevelreq, cr)
565 Create request to change the devel package definition.
566
567 [See http://en.opensuse.org/openSUSE:Build_Service_Collaboration
568 for information on this topic.]
569
570 See the "request" command for showing and modifying existing
571 requests.
572
573 osc changedevelrequest PROJECT PACKAGE DEVEL_PROJECT
574 [DEVEL_PACKAGE]
575
576
577 checkconstraints
578 check the constraints and view compliant workers
579
580 Checks the constraints for compliant workers.
581
582 usage:
583 remote request:
584 osc checkconstraints [OPTS] PROJECT PACKAGE REPOSITORY
585 ARCH
586
587 in a package working copy:
588 osc checkconstraints [OPTS] REPOSITORY ARCH CONSTRAINTS‐
589 FILE
590 osc checkconstraints [OPTS] CONSTRAINTSFILE
591 osc checkconstraints [OPTS]
592
593 Options:
594 -h, --help show this help message and exit
595 --ignore-file
596 ignore _constraints file and only check project
597 constraints
598
599
600
601 checkout (co)
602 Check out content from the repository
603
604 Check out content from the repository server, creating a local
605 working copy.
606
607 When checking out a single package, the option --revision can be
608 used to specify a revision of the package to be checked out.
609
610 When a package is a source link, then it will be checked out in
611 expanded form. If --unexpand-link option is used, the checkout
612 will instead produce the raw _link file plus patches.
613
614 usage:
615 osc co PROJECT [PACKAGE] [FILE]
616 osc co PROJECT # entire project
617 osc co PROJECT PACKAGE # a package
618 osc co PROJECT PACKAGE FILE # single file -> to
619 current dir
620
621 while inside a project directory:
622 osc co PACKAGE # check out PACKAGE
623 from project
624
625 with the result of rpm -q --qf '%{DISTURL}0 PACKAGE
626 osc co obs://API/PROJECT/PLATFORM/REVISION-PACKAGE
627
628 Options:
629 -h, --help show this help message and exit
630 -l limit_size, --limit-size=limit_size
631 Skip all files with a given size
632 -S, --server-side-source-service-files
633 Use server side generated sources instead of
634 local
635 generation.
636 -s, --source-service-files
637 Run source services.
638 -o outdir, --output-dir=outdir
639 place package in the specified directory instead
640 of a
641 PROJECT/PACKAGE directory
642 -c, --current-dir
643 place PACKAGE folder in the current directory
644 instead
645 of a PROJECT/PACKAGE directory
646 -M, --meta checkout out meta data instead of sources
647 -u, --unexpand-link
648 if a package is a link, check out the _link file
649 instead of the expanded sources
650 -D, --deleted
651 checkout an already deleted package. No meta
652 information
653 -e, --expand-link
654 if a package is a link, check out the expanded
655 sources
656 (no-op, since this became the default)
657 -r rev, --revision=rev
658 checkout the specified revision. NOTE: if you
659 checkout
660 the complete project this option is ignored!
661
662
663
664 chroot opens a shell inside of the build root
665
666 chroot into the build root for the given repository, arch and
667 build description (NOTE: this command does not work if a VM is
668 used)
669
670 usage:
671 osc chroot [OPTS] REPOSITORY ARCH BUILD_DESCR
672 osc chroot [OPTS] REPOSITORY (ARCH = hostarch, BUILD_DESCR
673 is detected automatically)
674 osc chroot [OPTS] ARCH (REPOSITORY = build_repository (con‐
675 fig option), BUILD_DESCR is detected automatically)
676 osc chroot [OPTS] BUILD_DESCR (REPOSITORY = build_repository
677 (config option), ARCH = hostarch)
678 osc chroot [OPTS] (REPOSITORY = build_repository (config
679 option), ARCH = hostarch, BUILD_DESCR is detected automatically)
680 Options:
681 -h, --help show this help message and exit
682 -f, --force
683 Do not ask confirmation for wipe
684 --wipe Delete the build root instead of chrooting into
685 it
686 -o, --offline
687 Use cached data without contacting the api
688 server
689 --root=ROOT
690 Path to the buildroot
691 -r, --login-as-root
692 login as root instead of abuild
693 --noinit, --no-init
694 do not guess/verify specified repository
695 --alternative-project=PROJECT
696 specify the used build target project
697 --local-package
698 package doesn't exist on the server
699
700
701
702 clean removes all untracked files from the package working copy
703
704 Examples:
705 osc clean <path>
706
707 Note: if <path> is omitted it defaults to '.' (<path> has to
708 be a package working copy)
709
710 Warning: This command removes all files with status '?'.
711
712 Usage:
713 osc clean [ARGS...]
714
715 Options:
716 -h, --help show this help message and exit
717 -n, --dry-run
718 print the results without actually removing a
719 file
720
721
722
723 comment
724 List / create / delete comments
725
726 On create:
727 If -p is given a reply to the ID is created. Otherwise
728 a toplevel comment is created.
729 If -c is not given the default editor will be opened and
730 you can type your comment
731
732 usage:
733 osc comment list package PROJECT PACKAGE
734 osc comment list project PROJECT
735 osc comment list request REQUEST_ID
736
737 osc comment create [-p PARENT_ID] [-c COMMENT] package
738 PROJECT PACKAGE
739 osc comment create [-p PARENT_ID] [-c COMMENT] project
740 PROJECT
741 osc comment create [-p PARENT_ID] [-c COMMENT] request
742 REQUEST_ID
743
744 osc comment delete ID
745
746
747
748 commit (checkin, ci)
749 Upload content to the repository server
750
751 Upload content which is changed in your working copy, to the
752 repository server.
753
754 examples:
755 osc ci # current dir
756 osc ci <dir>
757 osc ci file1 file2 ...
758
759 Usage:
760 osc commit [ARGS...]
761
762 Options:
763 -h, --help show this help message and exit
764 --skip-local-service-run, --noservice
765 Skip service run of configured source services
766 for
767 local run
768 -v, --verbose
769 Run the source services with verbose information
770 --skip-validation
771 deprecated, don't use it
772 -f, --force
773 force commit, even if there were no changes
774 -F FILE, --file=FILE
775 read log message from FILE, '-' denotes standard
776 input.
777 -n, --no-message
778 do not specify a log message
779 -m TEXT, --message=TEXT
780 specify log message TEXT
781
782
783
784 config get/set a config option
785
786 Examples:
787 osc config section option (get current value)
788 osc config section option value (set to value)
789 osc config section option --delete (delete option/reset to
790 the default)
791 osc config section --change-password (changes the password
792 in section "section")
793 (section is either an apiurl or an alias or 'general')
794 osc config --dump (dump the complete configuration)
795
796 Usage:
797 osc config [ARGS...]
798
799 Options:
800 -h, --help show this help message and exit
801 --dump-full
802 dump the complete configuration (including
803 'pass' and
804 'passx' options)
805 --dump dump the complete configuration (without 'pass'
806 and
807 'passx' options)
808 --no-echo prompt for a value but do not echo entered char‐
809 acters
810 --select-password-store
811 Change the password store
812 --change-password
813 Change password
814 -p, --prompt
815 prompt for a value
816 -s, --stdin
817 indicates that the config value should be read
818 from
819 stdin
820 -d, --delete
821 delete option from config or reset option to the
822 default)
823
824
825
826 copypac
827 Copy a package
828
829 A way to copy package to somewhere else.
830
831 It can be done across buildservice instances, if the -t option
832 is used. In that case, a client-side copy and link expansion
833 are implied.
834
835 Using --client-side-copy always involves downloading all files,
836 and uploading them to the target.
837
838 The DESTPAC name is optional; the source packages' name will be
839 used if DESTPAC is omitted.
840
841 usage:
842 osc copypac SOURCEPRJ SOURCEPAC DESTPRJ [DESTPAC] Options:
843 -h, --help show this help message and exit
844 -e, --expand
845 if the source package is a link then copy the
846 expanded
847 version of the link
848 -m TEXT, --message=TEXT
849 specify message TEXT
850 -t URL, --to-apiurl=URL
851 URL of destination api server. Default is the
852 source
853 api server.
854 -r rev, --revision=rev
855 copy the specified revision.
856 -d, --keep-develproject
857 keep develproject tag in the package metadata
858 -K, --keep-link
859 If the target package is a link, the link is
860 kept, but
861 may be updated. If the source package is a link,
862 its
863 expanded version is considered.
864 -k, --keep-maintainers
865 keep original maintainers. Default is remove all
866 and
867 replace with the one calling the script.
868 -c, --client-side-copy
869 do a (slower) client-side copy
870
871
872
873 createincident
874 Create a maintenance incident
875
876 [See http://openbuildservice.org/help/manuals/obs-reference-
877 guide/cha.obs.maintenance_setup.html for information on this
878 topic.]
879
880 This command is asking to open an empty maintenance incident.
881 This can usually only be done by a responsible maintenance team.
882 Please see the "mbranch" command on how to full such a project
883 content and the "patchinfo" command how add the required mainte‐
884 nance update information.
885
886 usage:
887 osc createincident [ MAINTENANCEPROJECT ] Options:
888 -h, --help show this help message and exit
889 -m TEXT, --message=TEXT
890 specify message TEXT
891 --noaccess Create a hidden project
892 -a ATTRIBUTE, --attribute=ATTRIBUTE
893 Use this attribute to find default maintenance
894 project
895 (default is OBS:MaintenanceProject)
896
897
898
899 createrequest (creq)
900 create multiple requests with a single command
901
902 usage:
903 osc creq [OPTIONS] [
904 -a submit SOURCEPRJ SOURCEPKG DESTPRJ [DESTPKG]
905 -a delete PROJECT [PACKAGE]
906 -a change_devel PROJECT PACKAGE DEVEL_PROJECT
907 [DEVEL_PACKAGE]
908 -a add_me ROLE PROJECT [PACKAGE]
909 -a add_group GROUP ROLE PROJECT [PACKAGE]
910 -a add_role USER ROLE PROJECT [PACKAGE]
911 -a set_bugowner USER PROJECT [PACKAGE]
912 ]
913
914 Option -m works for all types of request, the rest work only
915 for submit. example:
916 osc creq -a submit -a delete home:someone:branches:open‐
917 SUSE:Tools -a change_devel openSUSE:Tools osc home:some‐
918 one:branches:openSUSE:Tools -m ok
919
920 This will submit all modified packages under current direc‐
921 tory, delete project home:someone:branches:openSUSE:Tools and
922 change the devel project to home:someone:branches:openSUSE:Tools
923 for package osc in project openSUSE:Tools. Options:
924 -h, --help show this help message and exit
925 --yes proceed without asking.
926 --no-update
927 never touch source package on accept (will break
928 source links)
929 --no-cleanup
930 never remove source package on accept, but
931 update its
932 content
933 --cleanup remove package if submission gets accepted
934 (default
935 for home:<id>:branch projects)
936 --nodevelproject
937 do not follow a defined devel project (primary
938 project
939 where a package is developed)
940 -s REQUEST_ID, --supersede=REQUEST_ID
941 Superseding another request by this one
942 -r REV, --revision=REV
943 for "create", specify a certain source revision
944 ID
945 (the md5 sum)
946 -m TEXT, --message=TEXT
947 specify message TEXT
948 -a, --action
949 specify action type of a request, can be :
950 submit/delete/change_devel/add_role/set_bugowner
951
952
953
954 delete (del, remove, rm)
955 Mark files or package directories to be deleted upon the next
956 'checkin'
957
958 usage:
959 cd .../PROJECT/PACKAGE
960 osc delete FILE [...]
961 cd .../PROJECT
962 osc delete PACKAGE [...]
963
964 This command works on check out copies. Use "rdelete" for work‐
965 ing on server side only. This is needed for removing the entire
966 project.
967
968 As a safety measure, projects must be empty (i.e., you need to
969 delete all packages first).
970
971 If you are sure that you want to remove a package and all its
972 files use '--force' switch. Sometimes this also works without
973 --force.
974
975 Options:
976 -h, --help show this help message and exit
977 -f, --force
978 forces removal of entire package and its files
979
980
981
982 deleterequest (deletereq, dr, dropreq, droprequest)
983 Request to delete (or 'drop') a package or project
984
985 usage:
986 osc deletereq [-m TEXT] # works in
987 checked out project/package
988 osc deletereq [-m TEXT] PROJECT PACKAGE
989 osc deletereq [-m TEXT] PROJECT [--all|--repository REPOSI‐
990 TORY] Options:
991 -h, --help show this help message and exit
992 --accept-in-hours=HOURS
993 specify time when request shall get accepted
994 automatically. Only works with write permissions
995 in
996 target.
997 --all deletes entire project with packages inside
998 -r REPOSITORY, --repository=REPOSITORY
999 specify repository
1000 -m TEXT, --message=TEXT
1001 specify message TEXT
1002
1003
1004
1005 dependson (whatdependson)
1006 Show the build dependencies
1007
1008 The command dependson and whatdependson can be used to find out
1009 what will be triggered when a certain package changes. This is
1010 no guarantee, since the new build might have changed dependen‐
1011 cies.
1012
1013 dependson shows the build dependencies inside of a project,
1014 valid for a given repository and architecture. NOTE: to see all
1015 binary packages, which can trigger a build you need to
1016 refer the buildinfo, since this command shows only the
1017 dependencies
1018 inside of a project.
1019
1020 The arguments REPOSITORY and ARCH can be taken from the first
1021 two columns of the 'osc repos' output.
1022
1023 usage in package or project directory:
1024 osc dependson REPOSITORY ARCH
1025 osc whatdependson REPOSITORY ARCH
1026
1027 usage:
1028 osc dependson PROJECT [PACKAGE] REPOSITORY ARCH
1029 osc whatdependson PROJECT [PACKAGE] REPOSITORY ARCH
1030
1031
1032
1033 detachbranch
1034 replace a link with its expanded sources
1035
1036 If a package is a link it is replaced with its expanded sources.
1037 The link does not exist anymore.
1038
1039 usage:
1040 osc detachbranch # can be used in package
1041 working copy
1042 osc detachbranch PROJECT PACKAGE Options:
1043 -h, --help show this help message and exit
1044 -m TEXT, --message=TEXT
1045 specify message TEXT
1046
1047
1048
1049 develproject (bsdevelproject, dp)
1050 print the devel project / package of a package
1051
1052 Examples:
1053 osc develproject PRJ PKG
1054 osc develproject Options:
1055 -h, --help show this help message and exit
1056 -r, --raw deprecated option
1057
1058
1059
1060 diff (di, ldiff, linkdiff)
1061 Generates a diff
1062
1063 Generates a diff, comparing local changes against the repository
1064 server.
1065
1066 Usage:
1067 osc diff [ARGS...]
1068
1069 ARG, if specified, is a filename to include in the diff.
1070 Default: all files.
1071
1072 osc diff --link
1073 osc linkdiff
1074 Compare current checkout directory against the link
1075 base.
1076
1077 osc diff --link PROJ PACK
1078 osc linkdiff PROJ PACK
1079 Compare a package against the link base (ignoring work‐
1080 ing copy changes).
1081
1082 Options:
1083 -h, --help show this help message and exit
1084 -u, --unexpand
1085 Local changes only, ignore changes in linked
1086 package
1087 sources
1088 --missingok
1089 do not fail if the source or target
1090 project/package
1091 does not exist on the server
1092 -l, --link (osc linkdiff): compare against the base revi‐
1093 sion of
1094 the link
1095 -p, --plain
1096 output the diff in plain (not unified) diff for‐
1097 mat
1098 -M, --meta operate on meta files
1099 -r rev1[:rev2], --revision=rev1[:rev2]
1100 If rev1 is specified it will compare your work‐
1101 ing copy
1102 against the revision (rev1) on the server. If
1103 rev1 and
1104 rev2 are specified it will compare rev1 against
1105 rev2
1106 (NOTE: changes in your working copy are ignored
1107 in
1108 this case)
1109 -c rev, --change=rev
1110 the change made by revision rev (like -r
1111 rev-1:rev).If
1112 rev is negative this is like -r rev:rev-1.
1113
1114
1115
1116 distributions (dists)
1117 Shows all available distributions
1118
1119 This command shows the available distributions. For active dis‐
1120 tributions it shows the name, project and name of the repository
1121 and a suggested default repository name.
1122
1123 usage:
1124 osc distributions
1125
1126
1127
1128 enablechannels (enablechannel)
1129 Enables channels
1130
1131 Enables existing channel packages in a project. Enabling means
1132 adding the needed repositories for building. The command can be
1133 used to enable a specific one or all channels of a project.
1134
1135 Examples:
1136 osc enablechannels [PROJECT [CHANNEL_PACKAGE]]
1137
1138
1139 getbinaries
1140 Download binaries to a local directory
1141
1142 This command downloads packages directly from the api server.
1143 Thus, it directly accesses the packages that are used for build‐
1144 ing others even when they are not "published" yet.
1145
1146 usage:
1147 osc getbinaries REPOSITORY #
1148 works in checked out project/package (check out all archs in
1149 subdirs)
1150 osc getbinaries REPOSITORY ARCHITECTURE #
1151 works in checked out project/package
1152 osc getbinaries PROJECT REPOSITORY ARCHITECTURE
1153 osc getbinaries PROJECT PACKAGE REPOSITORY ARCHITECTURE
1154 osc getbinaries PROJECT PACKAGE REPOSITORY ARCHITECTURE FILE
1155 Options:
1156 -h, --help show this help message and exit
1157 --debug also fetch debug packages
1158 --sources also fetch source packages
1159 -M MULTIBUILD_PACKAGE, --multibuild-package=MULTIBUILD_PACK‐
1160 AGE
1161 get binaries from specified multibuild package
1162 -d DIR, --destdir=DIR
1163 destination directory
1164 -q, --quiet
1165 do not show downloading progress
1166
1167
1168
1169 help (?, h)
1170 give detailed help on a specific sub-command
1171
1172 usage:
1173 osc help [SUBCOMMAND]
1174
1175
1176 importsrcpkg
1177 Import a new package from a src.rpm
1178
1179 A new package dir will be created inside the project dir (if no
1180 project is specified and the current working dir is a project
1181 dir the package will be created in this project). If the package
1182 does not exist on the server it will be created too otherwise
1183 the meta data of the existing package will be updated (<title />
1184 and <description />). The src.rpm will be extracted into the
1185 package dir. The files won't be committed unless you explicitly
1186 pass the --commit switch.
1187
1188 SRPM is the path of the src.rpm in the local filesystem, or an
1189 URL.
1190
1191 Usage:
1192 osc importsrcpkg SRPM
1193
1194 Options:
1195 -h, --help show this help message and exit
1196 -c, --commit
1197 commit the new files
1198 --delete-old-files
1199 delete existing files from the server
1200 -d description, --description=description
1201 set the description of the package
1202 -t title, --title=title
1203 set a title
1204 -n name, --name=name
1205 specify a package name
1206 -p project, --project=project
1207 specify the path to a project
1208
1209
1210
1211 info Print information about a working copy
1212
1213 Print information about each ARG (default: '.') ARG is a work‐
1214 ing-copy path.
1215
1216 Usage:
1217 osc info [ARGS...]
1218
1219
1220
1221 init Initialize a directory as working copy
1222
1223 Initialize an existing directory to be a working copy of an
1224 (already existing) buildservice project/package.
1225
1226 (This is the same as checking out a package and then copying
1227 sources into the directory. It does NOT create a new package. To
1228 create a package, use 'osc meta pkg ... ...')
1229
1230 You wouldn't normally use this command.
1231
1232 To get a working copy of a package (e.g. for building it or
1233 working on it, you would normally use the checkout command. Use
1234 "osc help checkout" to get help for it.
1235
1236 usage:
1237 osc init PRJ
1238 osc init PRJ PAC
1239
1240
1241 jobhistory (jobhist)
1242 Shows the job history of a project
1243
1244 The arguments REPOSITORY and ARCH can be taken from the first
1245 two columns of the 'osc repos' output.
1246
1247 usage:
1248 osc jobhist REPOSITORY ARCHITECTURE (in project dir)
1249 osc jobhist PROJECT [PACKAGE] REPOSITORY ARCHITECTURE
1250 Options:
1251 -h, --help show this help message and exit
1252 -M MPAC, --multibuild-package=MPAC
1253 get jobhistory for the specified multibuild
1254 package
1255 -l limit, --limit=limit
1256 for setting the number of results
1257 --csv generate output in CSV (separated by |)
1258
1259
1260
1261 linkpac
1262 "Link" a package to another package
1263
1264 A linked package is a clone of another package, but plus local
1265 modifications. It can be cross-project.
1266
1267 The DESTPAC name is optional; the source packages' name will be
1268 used if DESTPAC is omitted.
1269
1270 Afterwards, you will want to 'checkout DESTPRJ DESTPAC'.
1271
1272 To add a patch, add the patch as file and add it to the _link
1273 file. You can also specify text which will be inserted at the
1274 top of the spec file.
1275
1276 See the examples in the _link file.
1277
1278 NOTE: In case you want to fix or update another package, you
1279 should use the 'branch'
1280 command. A branch has correct repositories (and a link)
1281 setup up by default and
1282 will be cleaned up automatically after it was submitted
1283 back.
1284
1285 usage:
1286 osc linkpac SOURCEPRJ SOURCEPAC DESTPRJ [DESTPAC] Options:
1287 -h, --help show this help message and exit
1288 -N, --new-package
1289 create a link to a not yet existing package
1290 -d, --disable-publish
1291 disable publishing of the linked package
1292 -f, --force
1293 overwrite an existing link file if it is there.
1294 -r rev, --revision=rev
1295 link the specified revision.
1296 -c, --current
1297 link fixed against current revision.
1298 -C CICOUNT, --cicount=CICOUNT
1299 cicount attribute in the link, known values are
1300 add,
1301 copy, and local, default in buildservice is cur‐
1302 rently
1303 add.
1304
1305
1306
1307 linktobranch
1308 Convert a package containing a classic link with patch to a
1309 branch
1310
1311 This command tells the server to convert a _link with or without
1312 a project.diff to a branch. This is a full copy with a _link
1313 file pointing to the branched place.
1314
1315 usage:
1316 osc linktobranch # can be used in checked
1317 out package
1318 osc linktobranch PROJECT PACKAGE
1319
1320
1321 list (LL, lL, ll, ls)
1322 List sources or binaries on the server
1323
1324 Examples for listing sources:
1325 ls # list all projects (deprecated)
1326 ls / # list all projects
1327 ls . # take PROJECT/PACKAGE from cur‐
1328 rent dir.
1329 ls PROJECT # list packages in a project
1330 ls PROJECT PACKAGE # list source files of package of
1331 a project
1332 ls PROJECT PACKAGE <file> # list <file> if this file exists
1333 ls -v PROJECT PACKAGE # verbosely list source files of
1334 package
1335 ls -l PROJECT PACKAGE # verbosely list source files of
1336 package
1337 ll PROJECT PACKAGE # verbosely list source files of
1338 package
1339 LL PROJECT PACKAGE # verbosely list source files of
1340 expanded link
1341
1342 With --verbose, the following fields will be shown for each
1343 item:
1344 MD5 hash of file
1345 Revision number of the last commit
1346 Size (in bytes)
1347 Date and time of the last commit
1348
1349 Examples for listing binaries:
1350 ls -b PROJECT # list all binaries of a project
1351 ls -b PROJECT -a ARCH # list ARCH binaries of a project
1352 ls -b PROJECT -r REPO # list binaries in REPO
1353 ls -b PROJECT PACKAGE REPO ARCH
1354
1355 Usage:
1356 list (LL, lL, ll, ls) [PROJECT [PACKAGE]]
1357 list (LL, lL, ll, ls) -b [PROJECT [PACKAGE [REPO [ARCH]]]]
1358 Options:
1359 -h, --help show this help message and exit
1360 -R REVISION, --revision=REVISION
1361 specify revision (only for sources)
1362 -M, --meta list meta data files
1363 -D, --deleted
1364 show only the former deleted projects or pack‐
1365 ages
1366 -l, --long print extra information
1367 -v, --verbose
1368 print extra information
1369 -u, --unexpand
1370 always work with unexpanded (source) packages
1371 -e, --expand
1372 expand linked package (only for sources)
1373 -b, --binaries
1374 list built binaries instead of sources
1375 -r REPO, --repo=REPO
1376 specify repository (only for binaries)
1377 -a ARCH, --arch=ARCH
1378 specify architecture (only for binaries)
1379
1380
1381
1382 localbuildlog (lbl)
1383 Shows the build log of a local buildchroot
1384
1385 usage:
1386 osc lbl [REPOSITORY [ARCH]]
1387 osc lbl # show log of newest last local build
1388
1389 Options:
1390 -h, --help show this help message and exit
1391 -s, --strip-time
1392 strip leading build time from the log
1393 -o OFFSET, --offset=OFFSET
1394 get log starting from offset
1395
1396
1397
1398 lock Locks a project or package.
1399
1400 usage:
1401 osc lock PROJECT [PACKAGE]
1402
1403 Options:
1404 -h, --help show this help message and exit
1405 -m TEXT, --message=TEXT
1406 specify log message TEXT
1407
1408
1409
1410 log Shows the commit log of a package
1411
1412 Usage:
1413 osc log (inside working copy)
1414 osc log remote_project [remote_package]
1415
1416 Options:
1417 -h, --help show this help message and exit
1418 -M, --meta checkout out meta data instead of sources
1419 -D, --deleted
1420 work on deleted package
1421 --xml generate output in XML
1422 --csv generate output in CSV (separated by |)
1423 -r rev, --revision=rev
1424 show log of the specified revision
1425
1426
1427
1428 maintainer (bugowner)
1429 Show maintainers according to server side configuration
1430
1431 # Search for official maintained sources in OBS instance
1432 osc maintainer BINARY <options>
1433 osc maintainer -U <user> <options>
1434 osc maintainer -G <group> <options>
1435
1436 # Lookup via containers
1437 osc maintainer <options>
1438 osc maintainer PRJ <options>
1439 osc maintainer PRJ PKG <options>
1440
1441 The tool looks up the default responsible person for a certain
1442 project or package. When using with an OBS 2.4 (or later)
1443 server it is doing the lookup for a given binary according to
1444 the server side configuration of default owners.
1445
1446 The tool is also looking into devel packages and supports to
1447 fallback to the project in case a package has no defined main‐
1448 tainer.
1449
1450 Please use "osc meta pkg" in case you need to know the defini‐
1451 tion in a specific container.
1452
1453 PRJ and PKG default to current working-copy path.
1454
1455 Usage:
1456 osc maintainer [ARGS...]
1457
1458 Options:
1459 -h, --help show this help message and exit
1460 -m MESSAGE, --message=MESSAGE
1461 Define message as commit entry or request
1462 description
1463 -r role, --role=role
1464 Specify user role
1465 -d user, --delete=user
1466 delete a maintainer/bugowner (can be specified
1467 via
1468 --role)
1469 -G GROUP, --group=GROUP
1470 All official maintained instances for the speci‐
1471 fied
1472 GROUP
1473 -U USER, --user=USER
1474 All official maintained instances for the speci‐
1475 fied
1476 USER
1477 -S user, --set-bugowner-request=user
1478 Set the bugowner to specified person via a
1479 request (or
1480 group via group: prefix)
1481 -s user, --set-bugowner=user
1482 Set the bugowner to specified person (or group
1483 via
1484 group: prefix)
1485 -A, --all list all found entries not just the first one
1486 -a user, --add=user
1487 add a new person for given role ("maintainer" by
1488 default)
1489 -D devel_project, --devel-project=devel_project
1490 define the project where this package is primar‐
1491 ily
1492 developed
1493 -v, --verbose
1494 show more information
1495 --nodevelproject
1496 do not follow a defined devel project (primary
1497 project
1498 where a package is developed)
1499 -e, --email
1500 show email addresses instead of user names
1501 -B, --bugowner
1502 Show only the bugowner if defined, or maintainer
1503 otherwise
1504 -b, --bugowner-only
1505 Show only the bugowner
1506
1507
1508
1509 maintenancerequest (mr)
1510 Create a request for starting a maintenance incident.
1511
1512 [See http://openbuildservice.org/help/manuals/obs-reference-
1513 guide/cha.obs.maintenance_setup.html for information on this
1514 topic.]
1515
1516 This command is asking the maintenance team to start a mainte‐
1517 nance incident based on a created maintenance update. Please see
1518 the "mbranch" command on how to create such a project and the
1519 "patchinfo" command how add the required maintenance update
1520 information.
1521
1522 usage:
1523 osc maintenancerequest [ SOURCEPROJECT [ SOURCEPACKAGES
1524 RELEASEPROJECT ] ]
1525 osc maintenancerequest .
1526
1527 The 2nd line when issued within a package directory provides a
1528 short cut to submit a single package (the one in the current
1529 directory) from the project of this package to be submitted to
1530 the release project this package links to. This syntax is only
1531 valid when specified from a package subdirectory. Options:
1532 -h, --help show this help message and exit
1533 -s REQUEST_ID, --supersede=REQUEST_ID
1534 Superseding another request by this one
1535 --incident-project=INCIDENT_PROJECT
1536 specify incident project to merge in
1537 --incident=INCIDENT
1538 specify incident number to merge in
1539 --cleanup do remove source project on accept
1540 --no-cleanup
1541 do not remove source project on accept
1542 --enforce-branching
1543 submit from a fresh branched project
1544 --release-project=RELEASEPROJECT
1545 Specify the release project
1546 -m TEXT, --message=TEXT
1547 specify message TEXT
1548 -a ATTRIBUTE, --attribute=ATTRIBUTE
1549 Use this attribute to find default maintenance
1550 project
1551 (default is OBS:MaintenanceProject)
1552
1553
1554
1555 man generates a man page
1556
1557 usage:
1558 osc man
1559
1560
1561 mbranch (maintained, sm)
1562 Search or branch multiple instances of a package
1563
1564 This command is used for searching all relevant instances of
1565 packages and creating links of them in one project. This is
1566 esp. used for maintenance updates. It can also be used to branch
1567 all packages marked before with a given attribute.
1568
1569 [See http://en.opensuse.org/openSUSE:Build_Service_Concept_Main‐
1570 tenance for information on this topic.]
1571
1572 The branched package will live in
1573 home:USERNAME:branches:ATTRIBUTE:PACKAGE if nothing else
1574 specified.
1575
1576 If osc maintained or sm is issued only the relevant instances of
1577 a package will be shown. No branch will be created. This is sim‐
1578 ilar to osc mbranch --dryrun.
1579
1580 usage:
1581 osc sm [SOURCEPACKAGE] [-a ATTRIBUTE]
1582 osc mbranch [ SOURCEPACKAGE [ TARGETPROJECT ] ] Options:
1583 -h, --help show this help message and exit
1584 --nodevelproject
1585 do not follow a defined devel project (primary
1586 project
1587 where a package is developed)
1588 --noaccess Create a hidden project
1589 --dryrun Just simulate the action and report back the
1590 result.
1591 -u UPDATE_ATTRIBUTE,
1592 --update-project-attribute=UPDATE_ATTRIBUTE
1593 Use this attribute to find update projects
1594 (default is
1595 OBS:UpdateProject)
1596 -a ATTRIBUTE, --attribute=ATTRIBUTE
1597 Use this attribute to find affected packages
1598 (default
1599 is OBS:Maintained)
1600 -c, --checkout
1601 Checkout branched package afterwards ('osc bco'
1602 is a
1603 shorthand for this option)
1604
1605
1606
1607 meta Show meta information, or edit it
1608
1609 Show or edit build service metadata of type <prj|pkg|prj‐
1610 conf|user|pattern>.
1611
1612 This command displays metadata on buildservice objects like
1613 projects, packages, or users. The type of metadata is specified
1614 by the word after "meta", like e.g. "meta prj".
1615
1616 prj denotes metadata of a buildservice project. prjconf denotes
1617 the (build) configuration of a project. pkg denotes metadata of
1618 a buildservice package. user denotes the metadata of a user.
1619 group denotes the metadata of a group. pattern denotes instal‐
1620 lation patterns defined for a project.
1621
1622 To list patterns, use 'osc meta pattern PRJ'. An additional
1623 argument will be the pattern file to view or edit.
1624
1625 With the --edit switch, the metadata can be edited. Per default,
1626 osc opens the program specified by the environmental variable
1627 EDITOR with a temporary file. Alternatively, content to be saved
1628 can be supplied via the --file switch. If the argument is '-',
1629 input is taken from stdin: osc meta prjconf home:user | sed ...
1630 | osc meta prjconf home:user -F -
1631
1632 For meta prj and prjconf updates optional commit messages can be
1633 applied with --message.
1634
1635 When trying to edit a non-existing resource, it is created
1636 implicitly.
1637
1638
1639 Examples:
1640 osc meta prj PRJ
1641 osc meta pkg PRJ PKG
1642 osc meta pkg PRJ PKG -e
1643
1644 Usage:
1645 osc meta <prj|prjconf> [-r|--revision REV] ARGS...
1646 osc meta <prj|pkg|prjconf|user|group|pattern> ARGS...
1647 osc meta <prj|pkg|prjconf|user|group|pattern> [-m|--message
1648 TEXT] -e|--edit ARGS...
1649 osc meta <prj|pkg|prjconf|user|group|pattern> [-m|--message
1650 TEXT] -F|--file ARGS...
1651 osc meta pattern --delete PRJ PATTERN
1652 osc meta attribute PRJ [PKG [SUBPACKAGE]] [--attribute
1653 ATTRIBUTE] [--create [--set <value_list>]|--delete|--set
1654 <value_list>] Options:
1655 -h, --help show this help message and exit
1656 --delete delete a pattern or attribute
1657 -s ATTRIBUTE_VALUES, --set=ATTRIBUTE_VALUES
1658 set attribute values
1659 -R, --remove-linking-repositories
1660 Try to remove also all repositories building
1661 against
1662 remove ones.
1663 -c, --create
1664 create attribute without values
1665 -e, --edit edit metadata
1666 -m TEXT, --message=TEXT
1667 specify log message TEXT. For prj and prjconf
1668 meta
1669 only
1670 -r REV, --revision=REV
1671 checkout given revision instead of head revi‐
1672 sion. For
1673 prj and prjconf meta only
1674 -F FILE, --file=FILE
1675 read metadata from FILE, instead of opening an
1676 editor.
1677 '-' denotes standard input.
1678 -f, --force
1679 force the save operation, allows one to ignores
1680 some
1681 errors like depending repositories. For prj meta
1682 only.
1683 --blame show author and time of each line
1684 --attribute-project
1685 include project values, if missing in packages
1686 --attribute-defaults
1687 include defined attribute defaults
1688 -a ATTRIBUTE, --attribute=ATTRIBUTE
1689 affect only a given attribute
1690
1691
1692
1693 mkpac Create a new package under version control
1694
1695 usage:
1696 osc mkpac new_package
1697
1698
1699 mv Move SOURCE file to DEST and keep it under version control
1700
1701 Usage:
1702 osc mv SOURCE DEST
1703
1704 Options:
1705 -h, --help show this help message and exit
1706 -f, --force
1707 forces removal of entire package and its files
1708
1709
1710
1711 my show waiting work, packages, projects or requests involving
1712 yourself
1713
1714 Examples:
1715 # list all open tasks for me
1716 osc my [work]
1717 # list packages where I am bugowner
1718 osc my pkg -b
1719 # list projects where I am maintainer
1720 osc my prj -m
1721 # list request for all my projects and packages
1722 osc my rq
1723 # list requests, excluding project 'foo' and 'bar'
1724 osc my rq --exclude-project foo,bar
1725 # list requests I made
1726 osc my sr
1727
1728 Usage:
1729 osc my [ARGS...]
1730
1731 where TYPE is one of requests, submitrequests,
1732 projects or packages (rq, sr, prj or pkg)
1733
1734 Options:
1735 -h, --help
1736 show this help message and exit
1737 --maintained
1738 limit search results to packages with maintained
1739 attribute set.
1740 -v, --verbose
1741 verbose listing
1742 --exclude-project=EXCLUDE_PROJECT
1743 exclude requests for specified project
1744 -U USER, --user=USER
1745 search for USER instead of yourself
1746 -a, --all
1747 all involvements
1748 -m, --maintainer
1749 restrict listing to items where the user is
1750 maintainer
1751 -b, --bugowner
1752 restrict listing to items where the user is
1753 bugowner
1754
1755
1756
1757 patchinfo
1758 Generate and edit a patchinfo file.
1759
1760 A patchinfo file describes the packages for an update and the
1761 kind of problem it solves.
1762
1763 This command either creates a new _patchinfo or updates an
1764 existing one.
1765
1766 Examples:
1767 osc patchinfo
1768 osc patchinfo [PROJECT [PATCH_NAME]] Options:
1769 -h, --help show this help message and exit
1770 -f, --force
1771 force generation of new patchinfo file, do not
1772 update
1773 existing one.
1774
1775
1776
1777 pdiff Quick alias to diff the content of a package with its parent.
1778
1779 Usage:
1780 osc pdiff [--plain|-p] [--nomissing-ok|-n]
1781 osc pdiff [--plain|-p] [--nomissing-ok|-n] PKG
1782 osc pdiff [--plain|-p] [--nomissing-ok|-n] PRJ PKG
1783
1784 Options:
1785 -h, --help show this help message and exit
1786 -n, --nomissingok
1787 fail if the parent package does not exist on the
1788 server
1789 -p, --plain
1790 output the diff in plain (not unified) diff for‐
1791 mat
1792
1793
1794
1795 prdiff (projdiff, projectdiff)
1796 Server-side diff of two projects
1797
1798 Compares two projects and either summarizes or outputs the dif‐
1799 ferences in full. In the second form, a project is compared
1800 with one of its branches inside a home:$USER project (the branch
1801 is treated as NEWPRJ). The home branch is optional if the cur‐
1802 rent working directory is a checked out copy of it.
1803
1804 Usage:
1805 osc prdiff [OPTIONS] OLDPRJ NEWPRJ
1806 osc prdiff [OPTIONS] [home:$USER:branch:$PRJ]
1807
1808 Options:
1809 -h, --help show this help message and exit
1810 -d, --diffstat
1811 show diffstat of differences
1812 -u, --unified
1813 show full unified diffs of differences
1814 -o, --show-not-in-new
1815 show packages only in the old project
1816 -n, --show-not-in-old
1817 show packages only in the new project
1818 -i REGEXP, --include=REGEXP
1819 only consider packages matching REGEXP
1820 -e REGEXP, --exclude=REGEXP
1821 skip packages matching REGEXP
1822 -r, --requests
1823 show open requests for any packages with differ‐
1824 ences
1825
1826
1827
1828 prjresults (pr)
1829 Shows project-wide build results
1830
1831 Usage:
1832 osc prjresults (inside working copy)
1833 osc prjresults PROJECT
1834
1835 Options:
1836 -h, --help show this help message and exit
1837 --show-excluded
1838 show packages that are excluded in all repos,
1839 also
1840 hide repos that have only excluded packages
1841 -V, --vertical
1842 list packages vertically instead horizontally
1843 -r REPO, --repo=REPO
1844 show results only for specified repo(s)
1845 -a ARCH, --arch=ARCH
1846 show results only for specified architecture(s)
1847 -n EXPR, --name-filter=EXPR
1848 show only packages whose names match EXPR
1849 -s STATUS, --status-filter=STATUS
1850 show only packages with buildstatus STATUS (see
1851 legend)
1852 --xml generate output in XML
1853 -c, --csv csv output
1854 -w, --watch
1855 watch the results until all finished building,
1856 only
1857 supported with --xml
1858 -q, --hide-legend
1859 hide the legend
1860
1861
1862
1863 pull merge the changes of the link target into your working copy.
1864
1865
1866
1867 rdelete
1868 Delete a project or packages on the server.
1869
1870 As a safety measure, project must be empty (i.e., you need to
1871 delete all packages first). Also, packages must have no requests
1872 pending (i.e., you need to accept/revoke such requests first).
1873 If you are sure that you want to remove this project and all its
1874 packages use '--recursive' switch. It may still not work
1875 because other depends on it. If you want to ignore this as well
1876 use '--force' switch.
1877
1878 usage:
1879 osc rdelete [-r] [-f] PROJECT [PACKAGE]
1880
1881 Options:
1882 -h, --help show this help message and exit
1883 -m TEXT, --message=TEXT
1884 specify log message TEXT
1885 -f, --force
1886 deletes a project where other depends on
1887 -r, --recursive
1888 deletes a project with packages inside
1889
1890
1891
1892 rdiff Server-side "pretty" diff of two packages
1893
1894 Compares two packages (three or four arguments) or shows the
1895 changes of a specified revision of a package (two arguments)
1896
1897 If no revision is specified the latest revision is used.
1898
1899 Note that this command doesn't return a normal diff (which could
1900 be applied as patch), but a "pretty" diff, which also compares
1901 the content of tarballs.
1902
1903
1904 usage:
1905 osc rdiff OLDPRJ OLDPAC NEWPRJ [NEWPAC]
1906 osc rdiff PROJECT PACKAGE Options:
1907 -h, --help show this help message and exit
1908 -u, --unexpand
1909 diff unexpanded version if sources are linked
1910 --missingok
1911 do not fail if the source or target
1912 project/package
1913 does not exist on the server
1914 -c rev, --change=rev
1915 the change made by revision rev (like -r
1916 rev-1:rev).
1917 If rev is negative this is like -r rev:rev-1.
1918 -p, --plain
1919 output the diff in plain (not unified) diff for‐
1920 mat
1921 -r N[:M], --revision=N[:M]
1922 revision id, where N = old revision and M = new
1923 revision
1924 -M, --meta diff meta data
1925 --issues-only
1926 show only issues in diff
1927 --oldpkg=OLDPKG
1928 package to compare against (deprecated, use 3
1929 argument
1930 form)
1931 --oldprj=OLDPRJ
1932 project to compare against (deprecated, use 3
1933 argument
1934 form)
1935
1936
1937
1938 rebuild (rebuildpac)
1939 Trigger package rebuilds
1940
1941 Note that it is normally NOT needed to kick off rebuilds like
1942 this, because they principally happen in a fully automatic way,
1943 triggered by source check-ins. In particular, the order in which
1944 packages are built is handled by the build service.
1945
1946 The arguments REPOSITORY and ARCH can be taken from the first
1947 two columns of the 'osc repos' output.
1948
1949 usage:
1950 osc rebuild [PROJECT [PACKAGE [REPOSITORY [ARCH]]]] Options:
1951 -h, --help show this help message and exit
1952 --all Rebuild all packages of entire project
1953 -M MULTIBUILD_PACKAGE, --multibuild-package=MULTIBUILD_PACK‐
1954 AGE
1955 rebuild specified multibuild package
1956 -f, --failed
1957 rebuild all failed packages
1958 -r REPO, --repo=REPO
1959 trigger rebuilds for a specific repository
1960 -a ARCH, --arch=ARCH
1961 trigger rebuilds for a specific architecture
1962
1963
1964
1965 release
1966 Release sources and binaries
1967
1968 This command is used to transfer sources and binaries without
1969 rebuilding them. It requires defined release targets set to
1970 trigger="manual". Please refer the release management chapter in
1971 the OBS book for details.
1972
1973 usage:
1974 osc release [ SOURCEPROJECT [ SOURCEPACKAGE ] ]
1975
1976 Options:
1977 -h, --help show this help message and exit
1978 --no-delay Don't put the release job in a queue to be run
1979 later,
1980 but immediately run it. Thus the next call to
1981 osc
1982 prjresult will reflect it. Otherwise there is no
1983 way
1984 to know if it is finished or didn't start yet.
1985 --set-release=RELEASETAG
1986 rename binaries during release using this
1987 release tag
1988 --target-repository=TARGETREPOSITORY
1989 Release only to specified repository
1990 --target-project=TARGETPROJECT
1991 Release only to specified project
1992 -r REPO, --repo=REPO
1993 Release only binaries from the specified reposi‐
1994 tory
1995
1996
1997
1998 releaserequest
1999 Create a request for releasing a maintenance update.
2000
2001 [See http://openbuildservice.org/help/manuals/obs-reference-
2002 guide/cha.obs.maintenance_setup.html
2003 for information on this topic.]
2004
2005 This command is used by the maintenance team to start the
2006 release process of a maintenance update. This includes usually
2007 testing based on the defined reviewers of the update project.
2008
2009 usage:
2010 osc releaserequest [ SOURCEPROJECT ]
2011
2012 Options:
2013 -h, --help show this help message and exit
2014 -m TEXT, --message=TEXT
2015 specify message TEXT
2016
2017
2018
2019 remotebuildlog (rbl, rblt, rbuildlog, rbuildlogtail, remotebuildlog‐
2020 tail)
2021 Shows the build log of a package
2022
2023 Shows the log file of the build of a package. Can be used to
2024 follow the log while it is being written.
2025
2026 remotebuildlogtail shows just the tail of the log file.
2027
2028 usage:
2029 osc remotebuildlog project package repository arch
2030 or
2031 osc remotebuildlog project/package/repository/arch
2032 or
2033 osc remotebuildlog buildlogurl Options:
2034 -h, --help show this help message and exit
2035 -s, --strip-time
2036 strip leading build time from the log
2037 -o OFFSET, --offset=OFFSET
2038 get log starting or ending from the offset
2039 -M MPAC, --multibuild-package=MPAC
2040 show log file for specified multibuild package
2041 -l, --last Show the last finished log file
2042
2043
2044
2045 repairlink
2046 Repair a broken source link
2047
2048 This command checks out a package with merged source changes. It
2049 uses a 3-way merge to resolve file conflicts. After review‐
2050 ing/repairing the merge, use 'osc resolved ...' and 'osc ci' to
2051 re-create a working source link.
2052
2053 usage: * For merging conflicting changes of a checkout package:
2054 osc repairlink
2055
2056 * Check out a package and merge changes:
2057 osc repairlink PROJECT PACKAGE
2058
2059 * Pull conflicting changes from one project into another one:
2060 osc repairlink PROJECT PACKAGE INTO_PROJECT [INTO_PACKAGE]
2061
2062 Options:
2063 -h, --help show this help message and exit
2064 -d DIR, --destdir=DIR
2065 destination directory
2066
2067
2068
2069 repairwc
2070 try to repair an inconsistent working copy
2071
2072 Examples:
2073 osc repairwc <path>
2074
2075 Note: if <path> is omitted it defaults to '.' (<path> can be
2076 a project or package working copy)
2077
2078 Warning: This command might delete some files in the storedir
2079 (.osc). Please check the state of the wc afterwards (via 'osc
2080 status').
2081
2082 Usage:
2083 osc repairwc [ARGS...]
2084
2085 Options:
2086 -h, --help show this help message and exit
2087 --force-apiurl
2088 ask once for an apiurl and force this apiurl for
2089 all
2090 inconsistent projects/packages
2091
2092
2093
2094 repositories (platforms, repos)
2095 shows repositories configured for a project.
2096 It skips repositories by default which are dis‐
2097 abled for a given package.
2098
2099 usage:
2100 osc repos
2101 osc repos [PROJECT] [PACKAGE]
2102
2103
2104
2105 repourls
2106 Shows URLs of .repo files
2107
2108 Shows URLs on which to access the project .repos files (yum-
2109 style metadata) on download.opensuse.org.
2110
2111 usage:
2112 osc repourls [PROJECT]
2113
2114
2115
2116 request (review, rq)
2117 Show or modify requests and reviews
2118
2119 [See http://en.opensuse.org/openSUSE:Build_Service_Collaboration
2120 for information on this topic.]
2121
2122 The 'request' command has the following sub commands:
2123
2124 "list" lists open requests attached to a project or package or
2125 person. Uses the project/package of the current directory if
2126 none of -M, -U USER, project/package are given.
2127
2128 "log" will show the history of the given ID
2129
2130 "show" will show the request itself, and generate a diff for
2131 review, if used with the --diff option. The keyword show can be
2132 omitted if the ID is numeric.
2133
2134 "decline" will change the request state to "declined"
2135
2136 "reopen" will set the request back to new or review.
2137
2138 "setincident" will direct "maintenance" requests into specific
2139 incidents
2140
2141 "supersede" will supersede one request with another existing
2142 one.
2143
2144 "revoke" will set the request state to "revoked"
2145
2146 "accept" will change the request state to "accepted" and will
2147 trigger the actual submit process. That would normally be a
2148 server-side copy of the source package to the target package.
2149
2150 "approve" marks a requests in "review" state as approved. This
2151 request will get accepted automatically when the last review got
2152 accepted.
2153
2154 "checkout" will checkout the request's source package ("submit"
2155 requests only).
2156
2157 "prioritize" change the priority of a request to either "criti‐
2158 cal", "important", "moderate" or "low"
2159
2160
2161 The 'review' command has the following sub commands:
2162
2163 "list" lists open requests that need to be reviewed by the spec‐
2164 ified user or group
2165
2166 "add" adds a person or group as reviewer to a request
2167
2168 "accept" mark the review positive
2169
2170 "decline" mark the review negative. A negative review will
2171 decline the request.
2172
2173 usage:
2174 osc request list [-M] [-U USER] [-s state] [-D DAYS] [-t
2175 type] [-B] [PRJ [PKG]]
2176 osc request log ID
2177 osc request [show] [-d] [-b] ID
2178
2179 osc request accept [-m TEXT] ID
2180 osc request approve [-m TEXT] ID
2181 osc request cancelapprove [-m TEXT] ID
2182 osc request decline [-m TEXT] ID
2183 osc request revoke [-m TEXT] ID
2184 osc request reopen [-m TEXT] ID
2185 osc request setincident [-m TEXT] ID INCIDENT
2186 osc request supersede [-m TEXT] ID SUPERSEDING_ID
2187 osc request approvenew [-m TEXT] PROJECT
2188 osc request prioritize [-m TEXT] ID PRIORITY
2189
2190 osc request checkout/co ID
2191 osc request clone [-m TEXT] ID
2192
2193 osc review show [-d] [-b] ID
2194 osc review list [-U USER] [-G GROUP] [-P PROJECT [-p PACK‐
2195 AGE]] [-s state]
2196 osc review add [-m TEXT] [-U USER] [-G GROUP] [-P PROJECT
2197 [-p PACKAGE]] ID
2198 osc review accept [-m TEXT] [-U USER] [-G GROUP] [-P PROJECT
2199 [-p PACKAGE]] ID
2200 osc review decline [-m TEXT] [-U USER] [-G GROUP] [-P
2201 PROJECT [-p PACKAGE]] ID
2202 osc review reopen [-m TEXT] [-U USER] [-G GROUP] [-P PROJECT
2203 [-p PACKAGE]] ID
2204 osc review supersede [-m TEXT] [-U USER] [-G GROUP] [-P
2205 PROJECT [-p PACKAGE]] ID SUPERSEDING_ID
2206
2207 Options:
2208 -h, --help show this help message and exit
2209 --source-buildstatus
2210 print the buildstatus of the source package
2211 (only
2212 works with "show" and the interactive review)
2213 --target-package-filter=TARGET_PACKAGE_FILTER
2214 only list requests for the packages matching the
2215 package filter. A (python) regular expression is
2216 expected.
2217 --involved-projects
2218 show all requests for project/packages where
2219 USER is
2220 involved
2221 --incoming Show only requests where the project is target
2222 --exclude-target-project=EXCLUDE_TARGET_PROJECT
2223 exclude target project from request list
2224 --non-interactive
2225 non-interactive review of request
2226 --or-revoke
2227 For automation scripts: accepts (if using with
2228 accept
2229 argument) a request when it is in new or review
2230 state.
2231 Or revoke it when it got declined. Otherwise
2232 just do
2233 nothing.
2234 -i, --interactive
2235 interactive review of request
2236 -e, --edit edit a submit action
2237 -B, --bugowner
2238 also show requests about packages where I am
2239 bugowner
2240 -M, --mine only show requests created by yourself
2241 -b, --brief
2242 print output in list view as list subcommand
2243 -p PACKAGE, --package=PACKAGE
2244 requests or reviews limited for the specified
2245 PACKAGE,
2246 requires also a PROJECT
2247 -P PROJECT, --project=PROJECT
2248 requests or reviews limited for the specified
2249 PROJECT
2250 -G GROUP, --group=GROUP
2251 requests or reviews limited for the specified
2252 GROUP
2253 -U USER, --user=USER
2254 requests or reviews limited for the specified
2255 USER
2256 -D DAYS, --days=DAYS
2257 only list requests in state "new" or changed in
2258 the
2259 last DAYS. [default=0]
2260 -s STATE, --state=STATE
2261 only list requests in one of the comma separated
2262 given
2263 states (new/review/accepted/revoked/declined) or
2264 "all"
2265 [default="declined,new,review", or "all", if no
2266 args
2267 given]
2268 -f, --force
2269 enforce state change, can be used to ignore open
2270 reviews
2271 -a, --all all states. Same as'-s all'
2272 -t TYPE, --type=TYPE
2273 limit to requests which contain a given action
2274 type (s
2275 ubmit/delete/change_devel/add_role/set_bugowner/mainte
2276 nance_incident/maintenance_release)
2277 -m TEXT, --message=TEXT
2278 specify message TEXT
2279 --no-devel Do not attempt to forward to devel project
2280 -u, --unified
2281 output the diff in the unified diff format
2282 -d, --diff generate a diff
2283
2284
2285
2286 requestmaintainership (reqbs, reqbugownership, reqmaintainership,
2287 reqms, requestbugownership)
2288 requests to add user as maintainer or bugowner
2289
2290 usage:
2291 osc requestmaintainership # for
2292 current user in checked out package
2293 osc requestmaintainership USER # for
2294 specified user in checked out package
2295 osc requestmaintainership PROJECT # for
2296 current user if cwd is not a checked out package
2297 osc requestmaintainership PROJECT group:NAME #
2298 request for specified group
2299 osc requestmaintainership PROJECT PACKAGE # for
2300 current user
2301 osc requestmaintainership PROJECT PACKAGE USER #
2302 request for specified user
2303 osc requestmaintainership PROJECT PACKAGE group:NAME #
2304 request for specified group
2305
2306 osc requestbugownership ... #
2307 accepts same parameters but uses bugowner role
2308
2309 Options:
2310 -h, --help show this help message and exit
2311 -r role, --role=role
2312 specify user role (default: maintainer)
2313 -m TEXT, --message=TEXT
2314 specify message TEXT
2315
2316
2317
2318 resolved
2319 Remove 'conflicted' state on working copy files
2320
2321 If an upstream change can't be merged automatically, a file is
2322 put into in 'conflicted' ('C') state. Within the file, conflicts
2323 are marked with special <<<<<<< as well as ======== and >>>>>>>
2324 lines.
2325
2326 After manually resolving all conflicting parts, use this command
2327 to remove the 'conflicted' state.
2328
2329 Note: this subcommand does not semantically resolve conflicts
2330 or remove conflict markers; it merely removes the conflict-
2331 related artifact files and allows PATH to be committed again.
2332
2333 usage:
2334 osc resolved FILE [FILE...]
2335
2336
2337 restartbuild (abortbuild)
2338 Restart the build of a certain project or package
2339
2340 usage:
2341 osc restartbuild [PROJECT [PACKAGE [REPOSITORY [ARCH]]]]
2342 Options:
2343 -h, --help show this help message and exit
2344 --all Restart all running builds of entire project
2345 -r REPO, --repo=REPO
2346 Restart builds for a specific repository
2347 -M MULTIBUILD_PACKAGE, --multibuild-package=MULTIBUILD_PACK‐
2348 AGE
2349 Restart builds for specified multibuild package
2350 -a ARCH, --arch=ARCH
2351 Restart builds for a specific architecture
2352
2353
2354
2355 results (r)
2356 Shows the build results of a package or project
2357
2358 Usage:
2359 osc results # (inside working copy of PRJ or
2360 PKG)
2361 osc results PROJECT [PACKAGE]
2362
2363 Options:
2364 -h, --help show this help message and exit
2365 --show-excluded
2366 show repos that are excluded for this package
2367 --format=FORMAT
2368 format string for csv output
2369 --csv generate output in CSV format
2370 --xml generate output in XML (former results_meta)
2371 -w, --watch
2372 watch the results until all finished building
2373 -M MULTIBUILD_PACKAGE, --multibuild-package=MULTIBUILD_PACK‐
2374 AGE
2375 Only show results for the specified multibuild
2376 package
2377 --no-multibuild
2378 Disable results for all direct affect packages
2379 inside
2380 of the project
2381 -v, --verbose
2382 more verbose output
2383 -a ARCH, --arch=ARCH
2384 Show results only for specified architecture(s)
2385 -r REPO, --repo=REPO
2386 Show results only for specified repo(s)
2387 -l, --last-build
2388 show last build results (suc‐
2389 ceeded/failed/unknown)
2390
2391
2392
2393 revert Restore changed files or the entire working copy.
2394
2395 Examples:
2396 osc revert <modified file(s)>
2397 osc revert . Note: this only works for package working
2398 copies
2399
2400 Usage:
2401 osc revert [FILES...]
2402
2403
2404
2405 rpmlintlog (lint, rpmlint)
2406 Shows the rpmlint logfile
2407
2408 Shows the rpmlint logfile to analyse if there are any problems
2409 with the spec file and the built binaries.
2410
2411 usage:
2412 osc rpmlintlog project package repository arch
2413
2414
2415 rremove
2416 Remove source files from selected package
2417
2418 Usage:
2419 osc rremove PROJECT PACKAGE [FILES...]
2420
2421 Options:
2422 -h, --help show this help message and exit
2423 -f, --force
2424 Don't ask and delete files
2425
2426
2427
2428 search (bse, se)
2429 Search for a project and/or package.
2430
2431 If no option is specified osc will search for projects and pack‐
2432 ages which contains the 'search term' in their name, title or
2433 description.
2434
2435 usage:
2436 osc search 'search term' <options>
2437 osc bse ... ('osc search --binary')
2438 osc se 'perl(Foo::Bar)' ('osc search --package
2439 perl-Foo-Bar') Options:
2440 -h, --help show this help message and exit
2441 --binaryversion=VERSION
2442 search for binary with specified version
2443 (implies
2444 --binary)
2445 -B PROJECT, --baseproject=PROJECT
2446 search packages built for PROJECT (implies
2447 --binary)
2448 --binary search binary packages
2449 --csv generate output in CSV (separated by |)
2450 -M, --mine shorthand for --bugowner --package
2451 --maintained
2452 OBSOLETE: please use maintained command instead.
2453 -m, --maintainer
2454 as -i, but only maintainer
2455 -b, --bugowner
2456 as -i, but only bugowner
2457 -i, --involved
2458 show projects/packages where given person (or
2459 myself)
2460 is involved as bugowner or maintainer
2461 [[{group|person}/]<name>] default: person
2462 -V, --version
2463 show package version, revision, and srcmd5. CAU‐
2464 TION:
2465 This is slow and unreliable
2466 -v, --verbose
2467 show more information
2468 -a ATTRIBUTE, --limit-to-attribute=ATTRIBUTE
2469 match only when given attribute exists in meta
2470 data
2471 --description
2472 search for matches in the 'description' element
2473 --title search for matches in the 'title' element
2474 --project search for a project
2475 --package search for a package
2476 -s, --substring
2477 Show also results where the search term is a sub
2478 string, slower search
2479 -e, --exact
2480 show only exact matches, this is default now
2481 --repos-baseurl
2482 show base URLs of download repositories
2483
2484
2485
2486 sendsysrq
2487 trigger a sysrq in a running build
2488
2489 This is only going to work when the build is running in a sup‐
2490 ported VM. Also only a subset of sysrq are supported. Typical
2491 use case for debugging are 9, t and w in this sequence.
2492
2493 usage:
2494 osc sendsysrq REPOSITORY ARCH SYSRQ
2495 osc sendsysrq PROJECT PACKAGE REPOSITORY ARCH SYSRQ Options:
2496 -h, --help show this help message and exit
2497 -M MULTIBUILD_PACKAGE, --multibuild-package=MULTIBUILD_PACK‐
2498 AGE
2499 specify a specific multibuild flavor
2500
2501
2502
2503 service
2504 Handle source services
2505
2506 Source services can be used to modify sources like downloading
2507 files, verify files, generating files or modify existing files.
2508
2509 usage:
2510 osc service COMMAND (inside working copy)
2511 osc service run [SOURCE_SERVICE]
2512 osc service runall
2513 osc service localrun
2514 osc service disabledrun
2515 osc service remoterun [PROJECT PACKAGE]
2516 osc service merge [PROJECT PACKAGE]
2517 osc service wait [PROJECT PACKAGE]
2518
2519 COMMAND can be:
2520 run r run defined services locally, it takes an
2521 optional parameter to run only a
2522 specified source service. In case parameters
2523 exist for this one in _service file
2524 they are used.
2525 runall ra run all services independent of the used mode
2526 localrun lr run all services except the ones with mode
2527 "buildtime", "disabled", or
2528 "serveronly" (deprecated)
2529 disabledrun dr run all services with mode "disabled" or
2530 "serveronly" (deprecated)
2531 remoterun rr trigger a re-run on the server side
2532 merge commits all server side generated files and
2533 drops the _service definition
2534 wait waits until the service finishes and returns
2535 with an error if it failed
2536
2537
2538
2539 setdevelproject (sdp)
2540 Set the devel project / package of a package
2541
2542 Examples:
2543 osc setdevelproject [PRJ PKG] DEVPRJ [DEVPKG] Options:
2544 -h, --help show this help message and exit
2545 -u, --unset
2546 remove devel project
2547
2548
2549
2550 setlinkrev
2551 Updates a revision number in a source link.
2552
2553 This command adds or updates a specified revision number in a
2554 source link. The current revision of the source is used, if no
2555 revision number is specified.
2556
2557 usage:
2558 osc setlinkrev
2559 osc setlinkrev PROJECT [PACKAGE] Options:
2560 -h, --help show this help message and exit
2561 -u, --unset
2562 remove revision in link, it will point always to
2563 latest revision
2564 -R, --use-plain-revision
2565 Do not expand revision the specified or latest
2566 rev
2567 -r rev, --revision=rev
2568 use the specified revision.
2569
2570
2571
2572 signkey
2573 Manage Project Signing Key
2574
2575 osc signkey [--create|--delete|--extend] <PROJECT> osc signkey
2576 [--notraverse] <PROJECT>
2577
2578 This command is for managing gpg keys. It shows the public key
2579 by default. There is no way to download or upload the private
2580 part of a key by design.
2581
2582 However you can create a new own key. You may want to consider
2583 to sign the public key with your own existing key.
2584
2585 If a project has no key, the key from upper level project will
2586 be used (e.g. when dropping "KDE:KDE4:Community" key, the one
2587 from "KDE:KDE4" will be used).
2588
2589 WARNING: THE OLD KEY CANNOT BE RESTORED AFTER USING DELETE OR
2590 CREATE
2591
2592 Usage:
2593 osc signkey [ARGS...]
2594
2595 Options:
2596 -h, --help show this help message and exit
2597 --sslcert fetch SSL certificate instead of GPG key
2598 --notraverse
2599 don' traverse projects upwards to find key
2600 --delete delete the gpg signing key in this project
2601 --extend extend expiration date of the gpg public key for
2602 this
2603 project
2604 --create create new gpg signing key for this project
2605
2606
2607
2608 status (st)
2609 Show status of files in working copy
2610
2611 Show the status of files in a local working copy, indicating
2612 whether files have been changed locally, deleted, added, ...
2613
2614 The first column in the output specifies the status and is one
2615 of the following characters:
2616 ' ' no modifications
2617 'A' Added
2618 'C' Conflicted
2619 'D' Deleted
2620 'M' Modified
2621 'R' Replaced (file was deleted and added again afterwards)
2622 '?' item is not under version control
2623 '!' item is missing (removed by non-osc command) or incomplete
2624 'S' item is skipped (item exceeds a file size limit or is
2625 _service:* file)
2626 'F' Frozen (use "osc pull" to merge conflicts) (package-only
2627 state)
2628
2629 examples:
2630 osc st
2631 osc st <directory>
2632 osc st file1 file2 ...
2633
2634 usage:
2635 osc status [OPTS] [PATH...] Options:
2636 -h, --help show this help message and exit
2637 -e, --show-excluded
2638 also show files which are excluded by the
2639 "exclude_glob" config option
2640 -v, --verbose
2641 print extra information
2642 -q, --quiet
2643 print as little as possible
2644
2645
2646
2647 submitrequest (sr, submitpac, submitreq)
2648 Create request to submit source into another Project
2649
2650 [See http://en.opensuse.org/openSUSE:Build_Service_Collaboration
2651 for information on this topic.]
2652
2653 See the "request" command for showing and modifying existing
2654 requests.
2655
2656 usage:
2657 osc submitreq [OPTIONS]
2658 osc submitreq [OPTIONS] DESTPRJ [DESTPKG]
2659 osc submitreq [OPTIONS] SOURCEPRJ SOURCEPKG DESTPRJ
2660 [DESTPKG]
2661
2662 osc submitpac ... is a shorthand for osc submitreq --cleanup
2663 ...
2664
2665 Options:
2666 -h, --help show this help message and exit
2667 --yes proceed without asking.
2668 -d, --diff show diff only instead of creating the actual
2669 request
2670 --update-link
2671 This transfers the source including the _link
2672 file.
2673 --no-update
2674 never touch source package on accept (will break
2675 source links)
2676 --no-cleanup
2677 never remove source package on accept, but
2678 update its
2679 content
2680 --cleanup remove package if submission gets accepted
2681 (default
2682 for home:<id>:branch projects)
2683 --seperate-requests
2684 Deprecated (wrong spelling - see --sepa‐
2685 rate-requests)
2686 --separate-requests
2687 Create multiple requests instead of a single one
2688 (when
2689 command is used for entire project)
2690 --nodevelproject
2691 do not follow a defined devel project (primary
2692 project
2693 where a package is developed)
2694 -s REQUEST_ID, --supersede=REQUEST_ID
2695 Superseding another request by this one
2696 -r REV, --revision=REV
2697 specify a certain source revision ID (the md5
2698 sum) for
2699 the source package
2700 -m TEXT, --message=TEXT
2701 specify message TEXT
2702
2703
2704
2705 token Show and manage authentication token
2706
2707 Authentication token can be used to run specific commands with‐
2708 out sending credentials.
2709
2710 Usage:
2711 osc token
2712 osc token --create [--operation <OPERATION>] [<PROJECT>
2713 <PACKAGE>]
2714 osc token --delete <TOKENID>
2715 osc token --trigger <TOKENSTRING> [--operation <OPERATION>]
2716 [<PROJECT> <PACKAGE>] Options:
2717 -h, --help show this help message and exit
2718 -t TOKENSTRING, --trigger=TOKENSTRING
2719 Trigger the action of a token
2720 -o OPERATION, --operation=OPERATION
2721 Default is "runservice", but "release" or
2722 "rebuild"
2723 can also be used
2724 -d TOKENID, --delete=TOKENID
2725 Delete a token
2726 -c, --create
2727 Create a new token
2728
2729
2730
2731 triggerreason (tr)
2732 Show reason why a package got triggered to build
2733
2734 The server decides when a package needs to get rebuild, this
2735 command shows the detailed reason for a package. A brief reason
2736 is also stored in the jobhistory, which can be accessed via "osc
2737 jobhistory".
2738
2739 Trigger reasons might be:
2740 - new build (never build yet or rebuild manually forced)
2741 - source change (e.g. on updating sources)
2742 - meta change (packages which are used for building have
2743 changed)
2744 - rebuild count sync (In case that it is configured to sync
2745 release numbers)
2746
2747 usage in package or project directory:
2748 osc triggerreason REPOSITORY ARCH
2749 osc triggerreason PROJECT PACKAGE REPOSITORY ARCH
2750
2751 Options:
2752 -h, --help show this help message and exit
2753 -M MPAC, --multibuild-package=MPAC
2754 get triggerreason of the specified multibuild
2755 package
2756
2757
2758
2759 undelete
2760 Restores a deleted project or package on the server.
2761
2762 The server restores a package including the sources and meta
2763 configuration. Binaries remain to be lost and will be rebuild.
2764
2765 usage:
2766 osc undelete PROJECT
2767 osc undelete PROJECT PACKAGE [PACKAGE ...]
2768
2769 Options:
2770 -h, --help show this help message and exit
2771 -m TEXT, --message=TEXT
2772 specify log message TEXT
2773
2774
2775
2776 unlock Unlocks a project or package
2777
2778 Unlocks a locked project or package. A comment is required.
2779
2780 usage:
2781 osc unlock PROJECT [PACKAGE]
2782
2783 Options:
2784 -h, --help show this help message and exit
2785 -m TEXT, --message=TEXT
2786 specify log message TEXT
2787
2788
2789
2790 update (up)
2791 Update a working copy
2792
2793 examples:
2794
2795 1. osc up
2796 If the current working directory is a package, update
2797 it.
2798 If the directory is a project directory, update all con‐
2799 tained
2800 packages, AND check out newly added packages.
2801
2802 To update only checked out packages, without checking
2803 out new
2804 ones, you might want to use "osc up *" from within the
2805 project
2806 dir.
2807
2808 2. osc up PAC
2809 Update the packages specified by the path argument(s)
2810
2811 When --expand-link is used with source link packages, the
2812 expanded sources will be checked out. Without this option, the
2813 _link file and patches will be checked out. The option --unex‐
2814 pand-link can be used to switch back to the "raw" source with a
2815 _link file plus patch(es).
2816
2817 Usage:
2818 osc update [ARGS...]
2819
2820 Options:
2821 -h, --help show this help message and exit
2822 -l limit_size, --limit-size=limit_size
2823 Skip all files with a given size
2824 -S, --server-side-source-service-files
2825 Use server side generated sources instead of
2826 local
2827 generation.
2828 -s, --source-service-files
2829 Run local source services after update.
2830 -e, --expand-link
2831 if a package is a link, update to the expanded
2832 sources
2833 -u, --unexpand-link
2834 if a package is an expanded link, update to the
2835 raw
2836 _link file
2837 --linkrev=REV
2838 revision of the link target that is used during
2839 link
2840 expansion
2841 -r REV, --revision=REV
2842 update to specified revision (this option will
2843 be
2844 ignored if you are going to update the complete
2845 project or more than one package)
2846
2847
2848
2849 updatepacmetafromspec (metafromspec, updatepkgmetafromspec)
2850 Update package meta information from a specfile
2851
2852 ARG, if specified, is a package working copy.
2853
2854 Usage:
2855 osc updatepacmetafromspec [ARGS...]
2856
2857 Options:
2858 -h, --help show this help message and exit
2859 --specfile=FILE
2860 Path to specfile. (if you pass more than working
2861 copy
2862 this option is ignored)
2863
2864
2865
2866 vc Edit the changes file
2867
2868 osc vc [-m MESSAGE|-e] [filename[.changes]|path [file_with_com‐
2869 ment]] If no <filename> is given, exactly one *.changes or
2870 *.spec file has to be in the cwd or in path.
2871
2872 The email address used in .changes file is read from BuildSer‐
2873 vice instance, or should be defined in oscrc [https://api.open‐
2874 suse.org/] user = login pass = password email =
2875 user@defined.email
2876
2877 or can be specified via mailaddr environment variable.
2878
2879 Usage:
2880 osc vc [ARGS...]
2881
2882 Options:
2883 -h, --help show this help message and exit
2884 -e, --just-edit
2885 just open changes (cannot be used with -m)
2886 -F FILE, --file=FILE
2887 read changes message from FILE (do not open an
2888 editor)
2889 -m MESSAGE, --message=MESSAGE
2890 add MESSAGE to changes (do not open an editor)
2891
2892
2893
2894 whois (user, who)
2895 Show fullname and email of a buildservice user
2896
2897 Usage:
2898 osc whois [USERNAMES...]
2899
2900
2901
2902 wipebinaries (unpublish)
2903 Delete all binary packages of a certain project/package
2904
2905 With the optional argument <package> you can specify a certain
2906 package otherwise all binary packages in the project will be
2907 deleted.
2908
2909 usage:
2910 osc wipebinaries OPTS # works in
2911 checked out project dir
2912 osc wipebinaries OPTS PROJECT [PACKAGE]
2913 osc unpublish OPTS # works in checked
2914 out project dir
2915 osc unpublish OPTS PROJECT [PACKAGE] Options:
2916 -h, --help show this help message and exit
2917 --all Delete all binaries regardless of the package
2918 status
2919 (previously default)
2920 --unresolvable
2921 Delete all binaries of packages which have
2922 dependency
2923 errors
2924 --broken Delete all binaries of packages for which the
2925 package
2926 source is bad
2927 --build-failed
2928 Delete all binaries of packages for which the
2929 build
2930 failed
2931 --build-disabled
2932 Delete all binaries of packages for which the
2933 build is
2934 disabled
2935 -r REPO, --repo=REPO
2936 Delete all binary packages for a specific repos‐
2937 itory
2938 -M MULTIBUILD_PACKAGE, --multibuild-package=MULTIBUILD_PACK‐
2939 AGE
2940 Delete all binary packages for specified multi‐
2941 build
2942 package
2943 -a ARCH, --arch=ARCH
2944 Delete all binary packages for a specific archi‐
2945 tecture
2946
2947
2948
2949 workerinfo
2950 gets the information to a worker from the server
2951
2952 Examples:
2953 osc workerinfo <workername>
2954
2955 Usage:
2956 osc workerinfo WORKER
2957
2958
2959
2960
2961 GLOBAL OPTIONS
2962 Options:
2963 --version show program's version number and exit
2964 -h, --help show this help message and exit
2965 --debugger jump into the debugger before executing any‐
2966 thing
2967 --post-mortem jump into the debugger in case of errors
2968 -t, --traceback print call trace in case of errors
2969 -H, --http-debug debug HTTP traffic (filters some headers)
2970 --http-full-debug debug HTTP traffic (filters no headers)
2971 -d, --debug print info useful for debugging
2972 -A URL/alias, --apiurl=URL/alias
2973 specify URL to access API server at or an alias
2974 -c FILE, --config=FILE
2975 specify alternate configuration file
2976 --no-keyring disable usage of desktop keyring system
2977 --no-gnome-keyring disable usage of GNOME Keyring
2978 -v, --verbose increase verbosity
2979 -q, --quiet be quiet, not verbose
2980
2981
2982
2984 Type 'osc help <subcommand>' for more detailed help on a specific sub‐
2985 command.
2986
2987 For additional information, see
2988 * http://en.opensuse.org/openSUSE:Build_Service_Tutorial
2989 * http://en.opensuse.org/openSUSE:OSC
2990
2991 You can modify osc commands, or roll your own, via the plugin API:
2992 * http://en.opensuse.org/openSUSE:OSC_plugins
2993
2995 osc was written by several authors. This man page is automatically gen‐
2996 erated.
2997
2998
2999
3000osc 0.166.2 Nov 2019 OSC(1)