1OSC(1) User Commands OSC(1)
2
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 COMMANDS
17 abortbuild
18 Aborts the build of a certain project or package
19 usage:
21 osc abortbuild [PROJECT [PACKAGE [REPOSITORY [ARCH]]]]
22 Options:
23 -h, --help show this help message and exit
24 --all Abort all running builds of entire project
25 -r REPO, --repo=REPO
26 Abort builds for a specific repository
27 -a ARCH, --arch=ARCH
28 Abort builds for a specific architecture
29 add Mark files to be added upon the next commit
33 In case a URL is given the file will get downloaded and regis‐
35 tered to be downloaded by the server as well via the down‐
36 load_url source service.
37 This is recommended for release tar balls to track their source
39 and to help others to review your changes esp. on version
40 upgrades.
41 usage:
43 osc add URL [URL...]
44 osc add FILE [FILE...]
45 addremove (ar)
48 Adds new files, removes disappeared files
49 Adds all files new in the local copy, and removes all disap‐
51 peared files.
52 ARG, if specified, is a package working copy.
54 Usage:
56 osc addremove [ARGS...]
57 Options:
59 -h, --help show this help message and exit
60 -r, --recursive
61 If CWD is a project dir then scan all package
62 dirs as
63 well
64 aggregatepac
68 "Aggregate" a package to another package
69 Aggregation of a package means that the build results (binaries)
71 of a package are basically copied into another project. This
72 can be used to make packages available from building that are
73 needed in a project but available only in a different project.
74 Note that this is done at the expense of disk space. See
75 http://en.opensuse.org/openSUSE:Build_Ser‐
76 vice_Tips_and_Tricks#link_and_aggregate for more information.
77 The DESTPAC name is optional; the source packages' name will be
79 used if DESTPAC is omitted.
80 usage:
82 osc aggregatepac SOURCEPRJ SOURCEPAC DESTPRJ [DESTPAC]
83 Options:
84 -h, --help show this help message and exit
85 -d, --disable-publish
86 disable publishing of the aggregated package
87 -m SRC=TARGET[,SRC=TARGET], --map-repo=SRC=TARGET[,SRC=TAR‐
88 GET]
89 Allows repository mapping(s) to be given as
90 SRC=TARGET[,SRC=TARGET]
91 --nosources
92 ignore source packages when copying build
93 results to
94 destination project
95 api Issue an arbitrary request to the API
99 Useful for testing.
101 URL can be specified either partially (only the path component),
103 or fully with URL scheme and hostname ('http://...').
104 Note the global -A and -H options (see osc help).
106 Examples:
108 osc api /source/home:user
109 osc api -X PUT -T /etc/fstab source/home:user/test5/myfstab
110 Usage:
112 osc api URL
113 Options:
115 -h, --help show this help message and exit
116 -a NAME STRING, --add-header=NAME STRING
117 add the specified header to the request
118 -T FILE, -f FILE, --file=FILE
119 specify filename for e.g. PUT or DELETE
120 -d STRING, --data=STRING
121 specify string data for e.g. POST
122 -X HTTP_METHOD, -m HTTP_METHOD, --method=HTTP_METHOD
123 specify HTTP method to use (GET|PUT|DELETE|POST)
124 branch (bco, branchco, getpac)
128 Branch a package
129 [See http://en.opensuse.org/openSUSE:Build_Service_Collaboration
131 for information on this topic.]
132 Create a source link from a package of an existing project to a
134 new subproject of the requesters home project (home:branches:)
135 The branched package will live in
137 home:USERNAME:branches:PROJECT/PACKAGE if nothing else spec‐
138 ified.
139 With getpac or bco, the branched package will come from one of
141 openSUSE:Factory (list of projects from oscrc:get‐
142 pac_default_project) if nothing else is specfied on the command
143 line.
144 usage:
146 osc branch
147 osc branch SOURCEPROJECT SOURCEPACKAGE
148 osc branch SOURCEPROJECT SOURCEPACKAGE TARGETPROJECT
149 osc branch SOURCEPROJECT SOURCEPACKAGE TARGETPROJECT TARGET‐
150 PACKAGE
151 osc getpac SOURCEPACKAGE
152 osc bco ... Options:
153 -h, --help show this help message and exit
154 -r rev, --revision=rev
155 branch against a specific revision
156 -m TEXT, --message=TEXT
157 specify message TEXT
158 --noaccess Create a hidden project
159 -f, --force
160 force branch, overwrite target
161 -c, --checkout
162 Checkout branched package afterwards using "co
163 -e
164 -S"('osc bco' is a shorthand for this option)
165 --nodevelproject
166 do not follow a defined devel project (primary
167 project
168 where a package is developed)
169 bugowner
173 Show bugowners of a project/package
174 osc bugowner PRJ
176 osc bugowner PRJ PKG
177 PRJ and PKG default to current working-copy path. Prints
179 bugowner if defined, or maintainer otherwise.
180 Shortcut for osc maintainer -B [PRJ] PKG
182 Options:
184 -h, --help show this help message and exit
185 -e, --email
186 show email addresses instead of user names
187 --nodevelproject
188 do not follow a defined devel project (primary
189 project
190 where a package is developed)
191 -v, --verbose
192 show more information
193 build Build a package on your local machine
197 You need to call the command inside a package directory, which
199 should be a buildsystem checkout. (Local modifications are
200 fine.)
201 The arguments REPOSITORY and ARCH can be taken from the first
203 two columns of the 'osc repos' output. BUILD_DESCR is either a
204 RPM spec file, or a Debian dsc file.
205 The command honours packagecachedir, build-root and build-uid
207 settings in .oscrc, if present. You may want to set su-wrapper =
208 'sudo' in .oscrc, and configure sudo with option NOPASSWD for
209 /usr/bin/build.
210 If neither --clean nor --noinit is given, build will reuse an
212 existing build-root again, removing unneeded packages and add
213 missing ones. This is usually the fastest option.
214 If the package doesn't exist on the server please use the
216 --local-package option. If the project of the package doesn't
217 exist on the server please use the --alternative-project <alter‐
218 native-project> option: Example:
219 osc build [OPTS] --alternative-project openSUSE:10.3 stan‐
220 dard i586 BUILD_DESCR
221 usage:
223 osc build [OPTS] REPOSITORY ARCH BUILD_DESCR
224 osc build [OPTS] REPOSITORY (ARCH = hostarch, BUILD_DESCR is
225 detected automatically)
226 osc build [OPTS] ARCH (REPOSITORY = build_repository (config
227 option), BUILD_DESCR is detected automatically)
228 osc build [OPTS] BUILD_DESCR (REPOSITORY = build_repository
229 (config option), ARCH = hostarch)
230 osc build [OPTS] (REPOSITORY = build_repository (config
231 option), ARCH = hostarch, BUILD_DESCR is detected automatically)
232 # Note: # Configuration can be overridden by envvars, e.g. #
234 OSC_SU_WRAPPER overrides the setting of su-wrapper. #
235 OSC_BUILD_ROOT overrides the setting of build-root. # OSC_PACK‐
236 AGECACHEDIR overrides the setting of packagecachedir.
237 Options:
239 -h, --help show this help message and exit
240 --oldpackages=DIR
241 take previous build from DIR (special values:
242 _self,
243 _link)
244 --disable-cpio-bulk-download
245 disable downloading packages as cpio archive
246 from api
247 --release=N
248 set release number of the package to N
249 -b, --baselibs
250 Create -32bit/-64bit/-x86 rpms for other archi‐
251 tectures
252 --disable-debuginfo
253 disable build of debuginfo packages
254 -d, --debuginfo
255 also build debuginfo sub-packages
256 --alternative-project=PROJECT
257 specify the build target project
258 --vm-type=TYPE
259 use VM type TYPE (e.g. kvm)
260 --linksources
261 use hard links instead of a deep copied source
262 --local-package
263 build a package which does not exist on the
264 server
265 --build-uid=uid:gid|"caller"
266 specify the numeric uid:gid pair to assign to
267 the
268 unprivileged "abuild" user or use "caller" to
269 use the
270 current user uid:gid
271 --userootforbuild
272 Run build as root. The default is to build as
273 unprivileged user. Note that a line "# noroot‐
274 forbuild"
275 in the spec file will invalidate this option.
276 --define='X Y'
277 define macro X with value Y
278 --without=X
279 disable feature X for build
280 --with=X enable feature X for build
281 --ccache use ccache to speed up rebuilds
282 --icecream=N
283 use N parallel build jobs with icecream
284 -j N, --jobs=N
285 Compile with N jobs
286 --root=ROOT
287 Build in specified directory
288 -x PAC, --extra-pkgs=PAC
289 Add this package when installing the build-root
290 -k DIR, --keep-pkgs=DIR
291 Save built packages into this directory
292 -p DIR, --prefer-pkgs=DIR
293 Prefer packages from this directory when
294 installing
295 the build-root
296 --noservice, --no-service
297 Skip run of local source services as specified
298 in
299 _service file.
300 --no-verify
301 Skip signature verification of packages used for
302 build. (Global config in .oscrc: no_verify)
303 --nochecks, --no-checks
304 Do not run post build checks on the resulting
305 packages.
306 --noinit, --no-init
307 Skip initialization of build root and start with
308 build
309 immediately.
310 --overlay=OVERLAY
311 Copy overlay filesystem to buildroot after
312 installing
313 all RPMs .
314 --rsync-dest=RSYNCDESTPATH
315 Copy folder to buildroot after installing all
316 RPMs.
317 Use together with --rsync-src. This is the path
318 on the
319 TARGET filesystem e.g.
320 /usr/src/packages/BUILD/linux-2.6 .
321 --rsync-src=RSYNCSRCPATH
322 Copy folder to buildroot after installing all
323 RPMs.
324 Use together with --rsync-dest. This is the path
325 on
326 the HOST filesystem e.g. /tmp/linux-kernel-tree.
327 It
328 defines RSYNCDONE 1 .
329 --no-changelog
330 don't update the package changelog from a
331 changes file
332 -l, --preload
333 Preload all files into the chache for offline
334 operation
335 -o, --offline
336 Start with cached prjconf and packages without
337 contacting the api server
338 --clean Delete old build root before initializing it
339 buildconfig
343 Shows the build config
344 Shows the build configuration which is used in building a pack‐
346 age. This command is mostly used internally by the 'build' com‐
347 mand.
348 The returned data is the project-wide build configuration in a
350 format which is directly readable by the build script. It con‐
351 tains RPM macros and BuildRequires expansions, for example.
352 The argument REPOSITORY an be taken from the first column of the
354 'osc repos' output.
355 usage:
357 osc buildconfig REPOSITORY (in pkg or
358 prj dir)
359 osc buildconfig PROJECT REPOSITORY
360 buildhistory (buildhist)
363 Shows the build history of a package
364 The arguments REPOSITORY and ARCH can be taken from the first
366 two columns of the 'osc repos' output.
367 usage:
369 osc buildhist REPOSITORY ARCHITECTURE
370 osc buildhist PROJECT PACKAGE REPOSITORY ARCHITECTURE
371 Options:
372 -h, --help show this help message and exit
373 --csv generate output in CSV (separated by |)
374 buildinfo
378 Shows the build info
379 Shows the build "info" which is used in building a package.
381 This command is mostly used internally by the 'build' subcom‐
382 mand. It needs to be called from within a package directory.
383 The BUILD_DESCR argument is optional. BUILD_DESCR is a local RPM
385 specfile or Debian "dsc" file. If specified, it is sent to the
386 server, and the buildinfo will be based on it. If the argument
387 is not supplied, the buildinfo is derived from the specfile
388 which is currently on the source repository server.
389 The returned data is XML and contains a list of the packages
391 used in building, their source, and the expanded BuildRequires.
392 The arguments REPOSITORY and ARCH are optional. They can be
394 taken from the first two columns of the 'osc repos' output. If
395 not specified, REPOSITORY defaults to the 'build_repositoy' con‐
396 fig entry in your '.oscrc' and ARCH defaults to your host archi‐
397 tecture.
398 usage:
400 in a package working copy:
401 osc buildinfo [OPTS] REPOSITORY ARCH BUILD_DESCR
402 osc buildinfo [OPTS] REPOSITORY (ARCH = hostarch,
403 BUILD_DESCR is detected automatically)
404 osc buildinfo [OPTS] ARCH (REPOSITORY = build_repository
405 (config option), BUILD_DESCR is detected automatically)
406 osc buildinfo [OPTS] BUILD_DESCR (REPOSITORY =
407 build_repository (config option), ARCH = hostarch)
408 osc buildinfo [OPTS] (REPOSITORY = build_repository
409 (config option), ARCH = hostarch, BUILD_DESCR is detected auto‐
410 matically)
411 Note: if BUILD_DESCR does not exist locally the remote
412 BUILD_DESCR is used
413 osc buildinfo [OPTS] PROJECT PACKAGE REPOSITORY ARCH
415 [BUILD_DESCR]
416 Options:
418 -h, --help show this help message and exit
419 -p DIR, --prefer-pkgs=DIR
420 Prefer packages from this directory when
421 installing
422 the build-root
423 -x PAC, --extra-pkgs=PAC
424 Add this package when computing the buildinfo
425 buildlog (bl, blt, buildlogtail)
429 Shows the build log of a package
430 Shows the log file of the build of a package. Can be used to
432 follow the log while it is being written. Needs to be called
433 from within a package directory.
434 When called as buildlogtail (or blt) it just shows the end of
436 the logfile. This is useful to see just a build failure rea‐
437 sons.
438 The arguments REPOSITORY and ARCH are the first two columns in
440 the 'osc results' output. If the buildlog url is used buildlog
441 command has the same behavior as remotebuildlog.
442 Usage:
444 osc buildlog [ARGS...]
445 [REPOSITORY ARCH | BUILDLOGURL] Options:
447 -h, --help show this help message and exit
448 -o OFFSET, --offset=OFFSET
449 get log start or end from the offset
450 cat (less)
454 Output the content of a file to standard output
455 Examples:
457 osc cat project package file
458 osc cat project/package/file
459 osc cat http://api.opensuse.org/build/.../_log
460 osc cat http://api.opensuse.org/source/../_link
461 Usage:
463 osc cat [ARGS...]
464 Options:
466 -h, --help show this help message and exit
467 -M, --meta list meta data files
468 -u, --unexpand
469 always work with unexpanded packages.
470 -e, --expand
471 force expansion of linked packages.
472 -r rev, --revision=rev
473 print out the specified revision
474 changedevelrequest (changedevelreq, cr)
478 Create request to change the devel package definition.
479 [See http://en.opensuse.org/openSUSE:Build_Service_Collaboration
481 for information on this topic.]
482 See the "request" command for showing and modifing existing
484 requests.
485 osc changedevelrequest PROJECT PACKAGE DEVEL_PROJECT
487 [DEVEL_PACKAGE]
488 checkout (co)
491 Check out content from the repository
492 Check out content from the repository server, creating a local
494 working copy.
495 When checking out a single package, the option --revision can be
497 used to specify a revision of the package to be checked out.
498 When a package is a source link, then it will be checked out in
500 expanded form. If --unexpand-link option is used, the checkout
501 will instead produce the raw _link file plus patches.
502 usage:
504 osc co PROJECT [PACKAGE] [FILE]
505 osc co PROJECT # entire project
506 osc co PROJECT PACKAGE # a package
507 osc co PROJECT PACKAGE FILE # single file -> to
508 current dir
509 while inside a project directory:
511 osc co PACKAGE # check out PACKAGE
512 from project
513 with the result of rpm -q --qf '%{disturl}n' PACKAGE
515 osc co obs://API/PROJECT/PLATFORM/REVISION-PACKAGE
516 Options:
518 -h, --help show this help message and exit
519 -l limit_size, --limit-size=limit_size
520 Skip all files with a given size
521 -S, --server-side-source-service-files
522 Use server side generated sources instead of
523 local
524 generation.
525 -s, --source-service-files
526 Run source services.
527 -c, --current-dir
528 place PACKAGE folder in the current directoryin‐
529 stead
530 of a PROJECT/PACKAGE directory
531 -M, --meta checkout out meta data instead of sources
532 -u, --unexpand-link
533 if a package is a link, check out the _link file
534 instead of the expanded sources
535 -e, --expand-link
536 if a package is a link, check out the expanded
537 sources
538 (no-op, since this became the default)
539 -r rev, --revision=rev
540 checkout the specified revision. NOTE: if you
541 checkout
542 the complete project this option is ignored!
543 chroot chroot into the buildchroot
547 chroot into the buildchroot for the given repository, arch and
549 build description (NOTE: this command does not work if "build-
550 type" is set in the config)
551 usage:
553 osc chroot [OPTS] REPOSITORY ARCH BUILD_DESCR
554 osc chroot [OPTS] REPOSITORY (ARCH = hostarch, BUILD_DESCR
555 is detected automatically)
556 osc chroot [OPTS] ARCH (REPOSITORY = build_repository (con‐
557 fig option), BUILD_DESCR is detected automatically)
558 osc chroot [OPTS] BUILD_DESCR (REPOSITORY = build_repository
559 (config option), ARCH = hostarch)
560 osc chroot [OPTS] (REPOSITORY = build_repository (config
561 option), ARCH = hostarch, BUILD_DESCR is detected automatically)
562 Options:
563 -h, --help show this help message and exit
564 -o, --offline
565 Use cached data without contacting the api
566 server
567 -r, --root login as root instead of abuild
568 --noinit, --no-init
569 do not guess/verify specified repository
570 --alternative-project=PROJECT
571 specify the used build target project
572 --local-package
573 package doesn't exist on the server
574 commit (checkin, ci)
578 Upload content to the repository server
579 Upload content which is changed in your working copy, to the
581 repository server.
582 Optionally checks the state of a working copy, if found a file
584 with unknown state, it requests an user input:
585 * skip - don't change anything, just move to another file
586 * remove - remove a file from dir
587 * edit file list - edit filelist using EDITOR
588 * commit - don't check anything and commit package
589 * abort - abort commit - this is default value This can be
590 supressed by check_filelist config item, or -f/--force command
591 line option.
592 examples:
594 osc ci # current dir
595 osc ci <dir>
596 osc ci file1 file2 ...
597 Usage:
599 osc commit [ARGS...]
600 Options:
602 -h, --help show this help message and exit
603 --skip-local-service-run
604 Skip service run of 'localonly' or 'trylocal'
605 configured source services
606 -v, --verbose
607 Run the source services and validation with ver‐
608 bose
609 information
610 --skip-validation
611 Skip the source validation
612 -f, --force
613 force commit - do not tests a file list
614 -F FILE, --file=FILE
615 read log message from FILE, '-' denotes standard
616 input.
617 -m TEXT, --message=TEXT
618 specify log message TEXT
619 config get/set a config option
623 Examples:
625 osc config section option (get current value)
626 osc config section option value (set to value)
627 osc config section option --delete (delete option/reset to
628 the default)
629 (section is either an apiurl or an alias or 'general')
630 osc config --dump (dump the complete configuration)
631 Usage:
633 osc config [ARGS...]
634 Options:
636 -h, --help show this help message and exit
637 --dump-full
638 dump the complete configuration (including
639 'pass' and
640 'passx' options)
641 --dump dump the complete configuration (without 'pass'
642 and
643 'passx' options)
644 --no-echo prompt for a value but do not echo entered char‐
645 acters
646 -p, --prompt
647 prompt for a value
648 -s, --stdin
649 indicates that the config value should be read
650 from
651 stdin
652 -d, --delete
653 delete option from config or reset option to the
654 default)
655 copypac
659 Copy a package
660 A way to copy package to somewhere else.
662 It can be done across buildservice instances, if the -t option
664 is used. In that case, a client-side copy and link expansion
665 are implied.
666 Using --client-side-copy always involves downloading all files,
668 and uploading them to the target.
669 The DESTPAC name is optional; the source packages' name will be
671 used if DESTPAC is omitted.
672 usage:
674 osc copypac SOURCEPRJ SOURCEPAC DESTPRJ [DESTPAC] Options:
675 -h, --help show this help message and exit
676 -e, --expand
677 if the source package is a link then copy the
678 expanded
679 version of the link
680 -m TEXT, --message=TEXT
681 specify message TEXT
682 -t URL, --to-apiurl=URL
683 URL of destination api server. Default is the
684 source
685 api server.
686 -r rev, --revision=rev
687 link the specified revision.
688 -d, --keep-develproject
689 keep develproject tag in the package metadata
690 -k, --keep-maintainers
691 keep original maintainers. Default is remove all
692 and
693 replace with the one calling the script.
694 -c, --client-side-copy
695 do a (slower) client-side copy
696 createincident
700 Create a maintenance incident
701 [See http://doc.opensuse.org/products/draft/OBS/obs-reference-
703 guide/cha.obs.maintenance_setup.html for information on this
704 topic.]
705 This command is asking to open an empty maintence incident. This
707 can usually only be done by a responsible maintenance team.
708 Please see the "mbranch" command on how to full such a project
709 content and the "patchinfo" command how add the required mainte‐
710 nance update information.
711 usage:
713 osc createincident [ MAINTENANCEPROJECT ] Options:
714 -h, --help show this help message and exit
715 -m TEXT, --message=TEXT
716 specify message TEXT
717 --noaccess Create a hidden project
718 -a ATTRIBUTE, --attribute=ATTRIBUTE
719 Use this attribute to find default maintenance
720 project
721 (default is OBS:MaintenanceProject)
722 createrequest (creq)
726 create multiple requests with a single command
727 usage:
729 osc creq [OPTIONS] [
730 -a submit SOURCEPRJ SOURCEPKG DESTPRJ [DESTPKG]
731 -a delete PROJECT [PACKAGE]
732 -a change_devel PROJECT PACKAGE DEVEL_PROJECT
733 [DEVEL_PACKAGE]
734 -a add_me ROLE PROJECT [PACKAGE]
735 -a add_group GROUP ROLE PROJECT [PACKAGE]
736 -a add_role USER ROLE PROJECT [PACKAGE]
737 -a set_bugowner USER PROJECT [PACKAGE]
738 ]
739 Option -m works for all types of request, the rest work only
741 for submit. example:
742 osc creq -a submit -a delete home:someone:branches:open‐
743 SUSE:Tools -a change_devel openSUSE:Tools osc home:some‐
744 one:branches:openSUSE:Tools -m ok
745 This will submit all modified packages under current direc‐
747 tory, delete project home:someone:branches:openSUSE:Tools and
748 change the devel project to home:someone:branches:openSUSE:Tools
749 for package osc in project openSUSE:Tools. Options:
750 -h, --help show this help message and exit
751 --yes proceed without asking.
752 -d, --diff show diff only instead of creating the actual
753 request
754 --no-update
755 never touch source package on accept (will break
756 source links)
757 --no-cleanup
758 never remove source package on accept, but
759 update its
760 content
761 --cleanup remove package if submission gets accepted
762 (default
763 for home:<id>:branch projects)
764 --nodevelproject
765 do not follow a defined devel project (primary
766 project
767 where a package is developed)
768 -s SUPERSEDE, --supersede=SUPERSEDE
769 Superseding another request by this one
770 -r REV, --revision=REV
771 for "create", specify a certain source revision
772 ID
773 (the md5 sum)
774 -m TEXT, --message=TEXT
775 specify message TEXT
776 -a, --action
777 specify action type of a request, can be :
778 submit/delete/change_devel/add_role/set_bugowner
779 delete (del, remove, rm)
783 Mark files or package directories to be deleted upon the next
784 'checkin'
785 usage:
787 cd .../PROJECT/PACKAGE
788 osc delete FILE [...]
789 cd .../PROJECT
790 osc delete PACKAGE [...]
791 This command works on check out copies. Use "rdelete" for work‐
793 ing on server side only. This is needed for removing the entire
794 project.
795 As a safety measure, projects must be empty (i.e., you need to
797 delete all packages first).
798 If you are sure that you want to remove a package and all its
800 files use '--force' switch. Sometimes this also works without
801 --force.
802 Options:
804 -h, --help show this help message and exit
805 -f, --force
806 forces removal of entire package and its files
807 deleterequest (deletereq, dr, dropreq, droprequest)
811 Request to delete (or 'drop') a package or project
812 usage:
814 osc deletereq [-m TEXT] # works in
815 checked out project/package
816 osc deletereq [-m TEXT] PROJECT [PACKAGE] Options:
817 -h, --help show this help message and exit
818 -m TEXT, --message=TEXT
819 specify message TEXT
820 dependson (whatdependson)
824 Show the build dependencies
825 The command dependson and whatdependson can be used to find out
827 what will be triggered when a certain package changes. This is
828 no guarantee, since the new build might have changed dependen‐
829 cies.
830 dependson shows the build dependencies inside of a project,
832 valid for a given repository and architecture. NOTE: to see all
833 binary packages, which can trigger a build you need to
834 refer the buildinfo, since this command shows only the
835 dependencies
836 inside of a project.
837 The arguments REPOSITORY and ARCH can be taken from the first
839 two columns of the 'osc repos' output.
840 usage in package or project directory:
842 osc dependson REPOSITORY ARCH
843 osc whatdependson REPOSITORY ARCH
844 usage:
846 osc dependson PROJECT [PACKAGE] REPOSITORY ARCH
847 osc whatdependson PROJECT [PACKAGE] REPOSITORY ARCH
848 detachbranch
852 replace a link with its expanded sources
853 If a package is a link it is replaced with its expanded sources.
855 The link does not exist anymore.
856 usage:
858 osc detachbranch # can be used in package
859 working copy
860 osc detachbranch PROJECT PACKAGE Options:
861 -h, --help show this help message and exit
862 -m TEXT, --message=TEXT
863 specify message TEXT
864 develproject (bsdevelproject)
868 print the bsdevelproject of a package
869 Examples:
871 osc develproject PRJ PKG
872 osc develproject Options:
873 -h, --help show this help message and exit
874 -r, --raw print raw xml snippet
875 diff (di, ldiff, linkdiff)
879 Generates a diff
880 Generates a diff, comparing local changes against the repository
882 server.
883 Usage:
885 osc diff [ARGS...]
886 ARG, if specified, is a filename to include in the diff.
888 Default: all files.
889 osc diff --link
891 osc linkdiff
892 Compare current checkout directory against the link
893 base.
894 osc diff --link PROJ PACK
896 osc linkdiff PROJ PACK
897 Compare a package against the link base (ignoring work‐
898 ing copy changes).
899 Options:
901 -h, --help show this help message and exit
902 --missingok
903 do not fail if the source or target
904 project/package
905 does not exist on the server
906 -l, --link (osc linkdiff): compare against the base revi‐
907 sion of
908 the link
909 -p, --plain
910 output the diff in plain (not unified) diff for‐
911 mat
912 -r rev1[:rev2], --revision=rev1[:rev2]
913 If rev1 is specified it will compare your work‐
914 ing copy
915 against the revision (rev1) on the server. If
916 rev1 and
917 rev2 are specified it will compare rev1 against
918 rev2
919 (NOTE: changes in your working copy are ignored
920 in
921 this case)
922 -c rev, --change=rev
923 the change made by revision rev (like -r
924 rev-1:rev).If
925 rev is negative this is like -r rev:rev-1.
926 distributions (dists)
930 Shows all available distributions
931 This command shows the available distributions. For active dis‐
933 tributions it shows the name, project and name of the repository
934 and a suggested default repository name.
935 usage:
937 osc distributions
938 getbinaries
942 Download binaries to a local directory
943 This command downloads packages directly from the api server.
945 Thus, it directly accesses the packages that are used for build‐
946 ing others even when they are not "published" yet.
947 usage:
949 osc getbinaries REPOSITORY #
950 works in checked out project/package (check out all archs in
951 subdirs)
952 osc getbinaries REPOSITORY ARCHITECTURE #
953 works in checked out project/package
954 osc getbinaries PROJECT PACKAGE REPOSITORY ARCHITECTURE
955 Options:
956 -h, --help show this help message and exit
957 --debug also fetch debug packages
958 --sources also fetch source packages
959 -d DIR, --destdir=DIR
960 destination directory
961 -q, --quiet
962 do not show downloading progress
963 help (?, h)
967 give detailed help on a specific sub-command
968 usage:
970 osc help [SUBCOMMAND]
971 importsrcpkg
974 Import a new package from a src.rpm
975 A new package dir will be created inside the project dir (if no
977 project is specified and the current working dir is a project
978 dir the package will be created in this project). If the package
979 does not exist on the server it will be created too otherwise
980 the meta data of the existing package will be updated (<title />
981 and <description />). The src.rpm will be extracted into the
982 package dir. The files won't be committed unless you explicitly
983 pass the --commit switch.
984 SRPM is the path of the src.rpm in the local filesystem, or an
986 URL.
987 Usage:
989 osc importsrcpkg SRPM
990 Options:
992 -h, --help show this help message and exit
993 -c, --commit
994 commit the new files
995 --delete-old-files
996 delete existing files from the server
997 -d description, --description=description
998 set the description of the package
999 -t title, --title=title
1000 set a title
1001 -n name, --name=name
1002 specify a package name
1003 -p project, --project=project
1004 specify the path to a project
1005 info Print information about a working copy
1009 Print information about each ARG (default: '.') ARG is a work‐
1011 ing-copy path.
1012 Usage:
1014 osc info [ARGS...]
1015 init Initialize a directory as working copy
1019 Initialize an existing directory to be a working copy of an
1021 (already existing) buildservice project/package.
1022 (This is the same as checking out a package and then copying
1024 sources into the directory. It does NOT create a new package. To
1025 create a package, use 'osc meta pkg ... ...')
1026 You wouldn't normally use this command.
1028 To get a working copy of a package (e.g. for building it or
1030 working on it, you would normally use the checkout command. Use
1031 "osc help checkout" to get help for it.
1032 usage:
1034 osc init PRJ
1035 osc init PRJ PAC
1036 jobhistory (jobhist)
1039 Shows the job history of a project
1040 The arguments REPOSITORY and ARCH can be taken from the first
1042 two columns of the 'osc repos' output.
1043 usage:
1045 osc jobhist REPOSITORY ARCHITECTURE (in project dir)
1046 osc jobhist PROJECT [PACKAGE] REPOSITORY ARCHITECTURE
1047 Options:
1048 -h, --help show this help message and exit
1049 -l limit, --limit=limit
1050 for setting the number of results
1051 --csv generate output in CSV (separated by |)
1052 linkpac
1056 "Link" a package to another package
1057 A linked package is a clone of another package, but plus local
1059 modifications. It can be cross-project.
1060 The DESTPAC name is optional; the source packages' name will be
1062 used if DESTPAC is omitted.
1063 Afterwards, you will want to 'checkout DESTPRJ DESTPAC'.
1065 To add a patch, add the patch as file and add it to the _link
1067 file. You can also specify text which will be inserted at the
1068 top of the spec file.
1069 See the examples in the _link file.
1071 NOTE: In case you are not aware about the difference of
1073 'linkpac' and 'branch' command
1074 you should use the 'branch' command by default.
1075 usage:
1077 osc linkpac SOURCEPRJ SOURCEPAC DESTPRJ [DESTPAC] Options:
1078 -h, --help show this help message and exit
1079 -d, --disable-publish
1080 disable publishing of the linked package
1081 -f, --force
1082 overwrite an existing link file if it is there.
1083 -r rev, --revision=rev
1084 link the specified revision.
1085 -c, --current
1086 link fixed against current revision.
1087 -C CICOUNT, --cicount=CICOUNT
1088 cicount attribute in the link, known values are
1089 add,
1090 copy, and local, default in buildservice is cur‐
1091 rently
1092 add.
1093 linktobranch
1097 Convert a package containing a classic link with patch to a
1098 branch
1099 This command tells the server to convert a _link with or without
1101 a project.diff to a branch. This is a full copy with a _link
1102 file pointing to the branched place.
1103 usage:
1105 osc linktobranch # can be used in checked
1106 out package
1107 osc linktobranch PROJECT PACKAGE
1108 list (LL, lL, ll, ls)
1111 List sources or binaries on the server
1112 Examples for listing sources:
1114 ls # list all projects (deprecated)
1115 ls / # list all projects
1116 ls . # take PROJECT/PACKAGE from cur‐
1117 rent dir.
1118 ls PROJECT # list packages in a project
1119 ls PROJECT PACKAGE # list source files of package of
1120 a project
1121 ls PROJECT PACKAGE <file> # list <file> if this file exists
1122 ls -v PROJECT PACKAGE # verbosely list source files of
1123 package
1124 ls -l PROJECT PACKAGE # verbosely list source files of
1125 package
1126 ll PROJECT PACKAGE # verbosely list source files of
1127 package
1128 LL PROJECT PACKAGE # verbosely list source files of
1129 expanded link
1130 With --verbose, the following fields will be shown for each
1132 item:
1133 MD5 hash of file
1134 Revision number of the last commit
1135 Size (in bytes)
1136 Date and time of the last commit
1137 Examples for listing binaries:
1139 ls -b PROJECT # list all binaries of a project
1140 ls -b PROJECT -a ARCH # list ARCH binaries of a project
1141 ls -b PROJECT -r REPO # list binaries in REPO
1142 ls -b PROJECT PACKAGE REPO ARCH
1143 Usage:
1145 list (LL, lL, ll, ls) [PROJECT [PACKAGE]]
1146 list (LL, lL, ll, ls) -b [PROJECT [PACKAGE [REPO [ARCH]]]]
1147 Options:
1148 -h, --help show this help message and exit
1149 -R REVISION, --revision=REVISION
1150 specify revision (only for sources)
1151 -M, --meta list meta data files
1152 -D, --deleted
1153 show only the former deleted projects or pack‐
1154 ages
1155 -l, --long print extra information
1156 -v, --verbose
1157 print extra information
1158 -u, --unexpand
1159 always work with unexpanded (source) packages
1160 -e, --expand
1161 expand linked package (only for sources)
1162 -b, --binaries
1163 list built binaries instead of sources
1164 -r REPO, --repo=REPO
1165 specify repository (only for binaries)
1166 -a ARCH, --arch=ARCH
1167 specify architecture (only for binaries)
1168 localbuildlog (lbl)
1172 Shows the build log of a local buildchroot
1173 usage:
1175 osc lbl [REPOSITORY ARCH]
1176 osc lbl # show log of newest last local build
1177 Options:
1179 -h, --help show this help message and exit
1180 -o OFFSET, --offset=OFFSET
1181 get log starting from offset
1182 log Shows the commit log of a package
1186 Usage:
1188 osc log (inside working copy)
1189 osc log remote_project [remote_package]
1190 Options:
1192 -h, --help show this help message and exit
1193 -M, --meta checkout out meta data instead of sources
1194 -D, --deleted
1195 work on deleted package
1196 --xml generate output in XML
1197 --csv generate output in CSV (separated by |)
1198 -r rev, --revision=rev
1199 show log of the specified revision
1200 maintainer
1204 Show maintainers of a project/package
1205 osc maintainer PRJ <options>
1207 osc maintainer PRJ PKG <options>
1208 PRJ and PKG default to current working-copy path.
1210 Usage:
1212 osc maintainer [ARGS...]
1213 Options:
1215 -h, --help show this help message and exit
1216 -r role, --role=role
1217 Specify user role
1218 -d user, --delete=user
1219 delete a maintainer/bugowner (can be specified
1220 via
1221 --role)
1222 -a user, --add=user
1223 add a new maintainer/bugowner (can be specified
1224 via
1225 --role)
1226 -D devel_project, --devel-project=devel_project
1227 define the project where this package is primar‐
1228 ily
1229 developed
1230 -v, --verbose
1231 show more information
1232 --nodevelproject
1233 do not follow a defined devel project (primary
1234 project
1235 where a package is developed)
1236 -e, --email
1237 show email addresses instead of user names
1238 -B, --bugowner
1239 Show only the bugowner if defined, or maintainer
1240 otherwise
1241 -b, --bugowner-only
1242 Show only the bugowner
1243 maintenancerequest
1247 Create a request for starting a maintenance incident.
1248 [See http://doc.opensuse.org/products/draft/OBS/obs-reference-
1250 guide/cha.obs.maintenance_setup.html for information on this
1251 topic.]
1252 This command is asking the maintence team to start a maintence
1254 incident based on a created maintenance update. Please see the
1255 "mbranch" command on how to create such a project and the
1256 "patchinfo" command how add the required maintenance update
1257 information.
1258 usage:
1260 osc maintenancerequest [ SOURCEPROJECT [ TARGETPROJECT ] ]
1261 Options:
1262 -h, --help show this help message and exit
1263 -m TEXT, --message=TEXT
1264 specify message TEXT
1265 -a ATTRIBUTE, --attribute=ATTRIBUTE
1266 Use this attribute to find default maintenance
1267 project
1268 (default is OBS:MaintenanceProject)
1269 man generates a man page
1273 usage:
1275 osc man
1276 mbranch
1279 Multiple branch of a package
1280 [See http://en.opensuse.org/openSUSE:Build_Service_Concept_Main‐
1282 tenance for information on this topic.]
1283 This command is used for creating multiple links of defined ver‐
1285 sion of a package in one project. This is esp. used for mainte‐
1286 nance updates.
1287 The branched package will live in
1289 home:USERNAME:branches:ATTRIBUTE:PACKAGE if nothing else
1290 specified.
1291 usage:
1293 osc mbranch [ SOURCEPACKAGE [ TARGETPROJECT ] ] Options:
1294 -h, --help show this help message and exit
1295 -u UPDATE_ATTRIBUTE,
1296 --update-project-attribute=UPDATE_ATTRIBUTE
1297 Use this attribute to find update projects
1298 (default is
1299 OBS:UpdateProject)
1300 --noaccess Create a hidden project
1301 -a ATTRIBUTE, --attribute=ATTRIBUTE
1302 Use this attribute to find affected packages
1303 (default
1304 is OBS:Maintained)
1305 -c, --checkout
1306 Checkout branched package afterwards ('osc bco'
1307 is a
1308 shorthand for this option)
1309 meta Show meta information, or edit it
1313 Show or edit build service metadata of type <prj|pkg|prj‐
1315 conf|user|pattern>.
1316 This command displays metadata on buildservice objects like
1318 projects, packages, or users. The type of metadata is specified
1319 by the word after "meta", like e.g. "meta prj".
1320 prj denotes metadata of a buildservice project. prjconf denotes
1322 the (build) configuration of a project. pkg denotes metadata of
1323 a buildservice package. user denotes the metadata of a user.
1324 pattern denotes installation patterns defined for a project.
1325 To list patterns, use 'osc meta pattern PRJ'. An additional
1327 argument will be the pattern file to view or edit.
1328 With the --edit switch, the metadata can be edited. Per default,
1330 osc opens the program specified by the environmental variable
1331 EDITOR with a temporary file. Alternatively, content to be saved
1332 can be supplied via the --file switch. If the argument is '-',
1333 input is taken from stdin: osc meta prjconf home:user | sed ...
1334 | osc meta prjconf home:user -F -
1335 When trying to edit a non-existing resource, it is created
1337 implicitly.
1338 Examples:
1341 osc meta prj PRJ
1342 osc meta pkg PRJ PKG
1343 osc meta pkg PRJ PKG -e
1344 osc meta attribute PRJ [PKG [SUBPACKAGE]] [--attribute
1345 ATTRIBUTE] [--create|--delete|--set [value_list]]
1346 Usage:
1348 osc meta <prj|pkg|prjconf|user|pattern|attribute> ARGS...
1349 osc meta <prj|pkg|prjconf|user|pattern|attribute> -e|--edit
1350 ARGS...
1351 osc meta <prj|pkg|prjconf|user|pattern|attribute> -F|--file
1352 ARGS...
1353 osc meta pattern --delete PRJ PATTERN Options:
1354 -h, --help show this help message and exit
1355 --delete delete a pattern or attribute
1356 -s ATTRIBUTE_VALUES, --set=ATTRIBUTE_VALUES
1357 set attribute values
1358 -c, --create
1359 create attribute without values
1360 -e, --edit edit metadata
1361 -F FILE, --file=FILE
1362 read metadata from FILE, instead of opening an
1363 editor.
1364 '-' denotes standard input.
1365 -f, --force
1366 force the save operation, allows one to ignores
1367 some
1368 errors like depending repositories. For prj meta
1369 only.
1370 --attribute-project
1371 include project values, if missing in packages
1372 --attribute-defaults
1373 include defined attribute defaults
1374 -a ATTRIBUTE, --attribute=ATTRIBUTE
1375 affect only a given attribute
1376 mkpac Create a new package under version control
1380 usage:
1382 osc mkpac new_package
1383 mv Move SOURCE file to DEST and keep it under version control
1386 Usage:
1388 osc mv SOURCE DEST
1389 Options:
1391 -h, --help show this help message and exit
1392 -f, --force
1393 forces removal of entire package and its files
1394 my show packages, projects or requests involving yourself
1398 Examples:
1400 # list packages where I am bugowner
1401 osc my pkg -b
1402 # list projects where I am maintainer
1403 osc my prj -m
1404 # list request for all my projects and packages
1405 osc my rq
1406 # list requests, excluding project 'foo' and 'bar'
1407 osc my rq --exclude-project foo,bar
1408 # list submitrequests I made
1409 osc my sr
1410 Usage:
1412 osc my TYPE
1413 where TYPE is one of requests, submitrequests,
1415 projects or packages (rq, sr, prj or pkg)
1416 Options:
1418 -h, --help
1419 show this help message and exit
1420 --maintained
1421 limit search results to packages with maintained
1422 attribute set.
1423 -v, --verbose
1424 verbose listing
1425 --exclude-project=EXCLUDE_PROJECT
1426 exclude requests for specified project
1427 -U USER, --user=USER
1428 search for USER instead of yourself
1429 -a, --all
1430 all involvements
1431 -m, --maintainer
1432 restrict listing to items where the user is
1433 maintainer
1434 -b, --bugowner
1435 restrict listing to items where the user is
1436 bugowner
1437 patchinfo
1441 Generate and edit a patchinfo file.
1442 A patchinfo file describes the packages for an update and the
1444 kind of problem it solves.
1445 Examples:
1447 osc patchinfo
1448 osc patchinfo PATCH_NAME Options:
1449 -h, --help show this help message and exit
1450 --force-update
1451 drops away collected packages from an already
1452 built
1453 patch and let it collect again
1454 -n, --new Use new, OBS 2.3 style patchinfo format. Will
1455 become
1456 default on release of OBS 2.3.
1457 -f, --force
1458 force generation of new patchinfo file
1459 pdiff Quick alias to diff the content of a package with its parent.
1463 Usage:
1465 osc pdiff [--plain|-p] [--nomissing-ok|-n]
1466 osc pdiff [--plain|-p] [--nomissing-ok|-n] PKG
1467 osc pdiff [--plain|-p] [--nomissing-ok|-n] PRJ PKG
1468 Options:
1470 -h, --help show this help message and exit
1471 -n, --nomissingok
1472 fail if the parent package does not exist on the
1473 server
1474 -p, --plain
1475 output the diff in plain (not unified) diff for‐
1476 mat
1477 prjresults (pr)
1481 Shows project-wide build results
1482 Usage:
1484 osc prjresults (inside working copy)
1485 osc prjresults PROJECT
1486 Options:
1488 -h, --help show this help message and exit
1489 --show-excluded
1490 show packages that are excluded in all repos,
1491 also
1492 hide repos that have only excluded packages
1493 -V, --vertical
1494 list packages vertically instead horizontally
1495 -r REPO, --repo=REPO
1496 show results only for specified repo(s)
1497 -a ARCH, --arch=ARCH
1498 show results only for specified architecture(s)
1499 -n EXPR, --name-filter=EXPR
1500 show only packages whose names match EXPR
1501 -s STATUS, --status-filter=STATUS
1502 show only packages with buildstatus STATUS (see
1503 legend)
1504 -c, --csv csv output
1505 -q, --hide-legend
1506 hide the legend
1507 pull merge the changes of the link target into your working copy.
1511 rdelete
1515 Delete a project or packages on the server.
1516 As a safety measure, project must be empty (i.e., you need to
1518 delete all packages first). Also, packages must have no requests
1519 pending (i.e., you need to accept/revoke such requests first).
1520 If you are sure that you want to remove this project and all its
1521 packages use '--recursive' switch. It may still not work
1522 because other depends on it. If you want to ignore this as well
1523 use '--force' switch.
1524 usage:
1526 osc rdelete [-r] [-f] PROJECT [PACKAGE]
1527 Options:
1529 -h, --help show this help message and exit
1530 -m TEXT, --message=TEXT
1531 specify log message TEXT
1532 -f, --force
1533 deletes a project where other depends on
1534 -r, --recursive
1535 deletes a project with packages inside
1536 rdiff Server-side "pretty" diff of two packages
1540 Compares two packages (three or four arguments) or shows the
1542 changes of a specified revision of a package (two arguments)
1543 If no revision is specified the latest revision is used.
1545 Note that this command doesn't return a normal diff (which could
1547 be applied as patch), but a "pretty" diff, which also compares
1548 the content of tarballs.
1549 usage:
1552 osc rdiff OLDPRJ OLDPAC NEWPRJ [NEWPAC]
1553 osc rdiff PROJECT PACKAGE Options:
1554 -h, --help show this help message and exit
1555 -u, --unexpand
1556 diff unexpanded version if sources are linked
1557 --missingok
1558 do not fail if the source or target
1559 project/package
1560 does not exist on the server
1561 -c rev, --change=rev
1562 the change made by revision rev (like -r
1563 rev-1:rev).
1564 If rev is negative this is like -r rev:rev-1.
1565 -p, --plain
1566 output the diff in plain (not unified) diff for‐
1567 mat
1568 -r N[:M], --revision=N[:M]
1569 revision id, where N = old revision and M = new
1570 revision
1571 -M, --meta diff meta data
1572 --oldpkg=OLDPKG
1573 package to compare against (deprecated, use 3
1574 argument
1575 form)
1576 --oldprj=OLDPRJ
1577 project to compare against (deprecated, use 3
1578 argument
1579 form)
1580 rebuild (rebuildpac)
1584 Trigger package rebuilds
1585 Note that it is normally NOT needed to kick off rebuilds like
1587 this, because they principally happen in a fully automatic way,
1588 triggered by source check-ins. In particular, the order in which
1589 packages are built is handled by the build service.
1590 The arguments REPOSITORY and ARCH can be taken from the first
1592 two columns of the 'osc repos' output.
1593 usage:
1595 osc rebuild [PROJECT [PACKAGE [REPOSITORY [ARCH]]]] Options:
1596 -h, --help show this help message and exit
1597 --all Rebuild all packages of entire project
1598 -f, --failed
1599 rebuild all failed packages
1600 -r REPO, --repo=REPO
1601 trigger rebuilds for a specific repository
1602 -a ARCH, --arch=ARCH
1603 trigger rebuilds for a specific architecture
1604 releaserequest
1608 Create a request for releasing a maintenance update.
1609 [See http://doc.opensuse.org/products/draft/OBS/obs-reference-
1611 guide/cha.obs.maintenance_setup.html
1612 for information on this topic.]
1613 This command is used by the maintence team to start the release
1615 process of a maintenance update. This includes usually testing
1616 based on the defined reviewers of the update project.
1617 usage:
1619 osc releaserequest [ SOURCEPROJECT ]
1620 Options:
1622 -h, --help show this help message and exit
1623 -m TEXT, --message=TEXT
1624 specify message TEXT
1625 remotebuildlog (rbl, rblt, rbuildlog, rbuildlogtail, remotebuildlog‐
1629 tail)
1630 Shows the build log of a package
1631 Shows the log file of the build of a package. Can be used to
1633 follow the log while it is being written.
1634 remotebuildlogtail shows just the tail of the log file.
1636 usage:
1638 osc remotebuildlog project package repository arch
1639 or
1640 osc remotebuildlog project/package/repository/arch
1641 or
1642 osc remotebuildlog buildlogurl Options:
1643 -h, --help show this help message and exit
1644 -o OFFSET, --offset=OFFSET
1645 get log starting or ending from the offset
1646 repairlink
1650 Repair a broken source link
1651 This command checks out a package with merged source changes. It
1653 uses a 3-way merge to resolve file conflicts. After review‐
1654 ing/repairing the merge, use 'osc resolved ...' and 'osc ci' to
1655 re-create a working source link.
1656 usage: * For merging conflicting changes of a checkout package:
1658 osc repairlink
1659 * Check out a package and merge changes:
1661 osc repairlink PROJECT PACKAGE
1662 * Pull conflicting changes from one project into another one:
1664 osc repairlink PROJECT PACKAGE INTO_PROJECT [INTO_PACKAGE]
1665 Options:
1667 -h, --help show this help message and exit
1668 -d DIR, --destdir=DIR
1669 destination directory
1670 repairwc
1674 try to repair an inconsistent working copy
1675 Examples:
1677 osc repairwc <path>
1678 Note: if <path> is omitted it defaults to '.' (<path> can be
1680 a project or package working copy)
1681 Warning: This command might delete some files in the storedir
1683 (.osc). Please check the state of the wc afterwards (via 'osc
1684 status').
1685 Usage:
1687 osc repairwc [ARGS...]
1688 Options:
1690 -h, --help show this help message and exit
1691 --force-apiurl
1692 ask once for an apiurl and force this apiurl for
1693 all
1694 inconsistent projects/packages
1695 repositories (platforms, repos)
1699 shows repositories configured for a project.
1700 It skips repositories by default which are dis‐
1701 abled for a given package.
1702 usage:
1704 osc repos
1705 osc repos [PROJECT] [PACKAGE]
1706 repourls
1710 Shows URLs of .repo files
1711 Shows URLs on which to access the project .repos files (yum-
1713 style metadata) on download.opensuse.org.
1714 usage:
1716 osc repourls [PROJECT]
1717 request (review, rq)
1721 Show or modify requests and reviews
1722 [See http://en.opensuse.org/openSUSE:Build_Service_Collaboration
1724 for information on this topic.]
1725 The 'request' command has the following sub commands:
1727 "list" lists open requests attached to a project or package or
1729 person. Uses the project/package of the current directory if
1730 none of -M, -U USER, project/package are given.
1731 "log" will show the history of the given ID
1733 "show" will show the request itself, and generate a diff for
1735 review, if used with the --diff option. The keyword show can be
1736 omitted if the ID is numeric.
1737 "decline" will change the request state to "declined"
1739 "reopen" will set the request back to new or review.
1741 "supersede" will supersede one request with another existing
1743 one.
1744 "revoke" will set the request state to "revoked"
1746 "accept" will change the request state to "accepted" and will
1748 trigger the actual submit process. That would normally be a
1749 server-side copy of the source package to the target package.
1750 "checkout" will checkout the request's source package ("submit"
1752 requests only).
1753 The 'review' command has the following sub commands:
1755 "list" lists open requests that need to be reviewed by the spec‐
1757 ified user or group
1758 "add" adds a person or group as reviewer to a request
1760 "accept" mark the review positive
1762 "decline" mark the review negative. A negative review will
1764 decline the request.
1765 usage:
1767 osc request list [-M] [-U USER] [-s state] [-D DAYS] [-t
1768 type] [-B] [PRJ [PKG]]
1769 osc request log ID
1770 osc request [show] [-d] [-b] ID
1771 osc request accept [-m TEXT] ID
1773 osc request decline [-m TEXT] ID
1774 osc request revoke [-m TEXT] ID
1775 osc request reopen [-m TEXT] ID
1776 osc request supersede [-m TEXT] ID SUPERSEDING_ID
1777 osc request approvenew [-m TEXT] PROJECT
1778 osc request checkout/co ID
1780 osc request clone [-m TEXT] ID
1781 osc review list [-U USER] [-G GROUP] [-P PROJECT [-p PACK‐
1783 AGE]] [-s state]
1784 osc review add [-m TEXT] [-U USER] [-G GROUP] [-P PROJECT
1785 [-p PACKAGE]] ID
1786 osc review accept [-m TEXT] [-U USER] [-G GROUP] [-P PROJECT
1787 [-p PACKAGE]] ID
1788 osc review decline [-m TEXT] [-U USER] [-G GROUP] [-P
1789 PROJECT [-p PACKAGE]] ID
1790 osc review reopen [-m TEXT] [-U USER] [-G GROUP] [-P PROJECT
1791 [-p PACKAGE]] ID
1792 osc review supersede [-m TEXT] [-U USER] [-G GROUP] [-P
1793 PROJECT [-p PACKAGE]] ID SUPERSEDING_ID
1794 Options:
1796 -h, --help show this help message and exit
1797 --source-buildstatus
1798 print the buildstatus of the source package
1799 (only
1800 works with "show")
1801 --involved-projects
1802 show all requests for project/packages where
1803 USER is
1804 involved
1805 --exclude-target-project=EXCLUDE_TARGET_PROJECT
1806 exclude target project from request list
1807 --non-interactive
1808 non-interactive review of request
1809 -i, --interactive
1810 interactive review of request
1811 -e, --edit edit a submit action
1812 -B, --bugowner
1813 also show requests about packages where I am
1814 bugowner
1815 -M, --mine only show requests created by yourself
1816 -b, --brief
1817 print output in list view as list subcommand
1818 -p PACKAGE, --package=PACKAGE
1819 requests or reviews limited for the specified
1820 PACKAGE,
1821 requires also a PROJECT
1822 -P PROJECT, --project=PROJECT
1823 requests or reviews limited for the specified
1824 PROJECT
1825 -G GROUP, --group=GROUP
1826 requests or reviews limited for the specified
1827 GROUP
1828 -U USER, --user=USER
1829 requests or reviews limited for the specified
1830 USER
1831 -D DAYS, --days=DAYS
1832 only list requests in state "new" or changed in
1833 the
1834 last DAYS. [default=0]
1835 -s STATE, --state=STATE
1836 only list requests in one of the comma separated
1837 given
1838 states (new/review/accepted/revoked/declined) or
1839 "all"
1840 [default="new,review", or "all", if no args
1841 given]
1842 -f, --force
1843 enforce state change, can be used to ignore open
1844 reviews
1845 -a, --all all states. Same as'-s all'
1846 -t TYPE, --type=TYPE
1847 limit to requests which contain a given action
1848 type
1849 (submit/delete/change_devel)
1850 -m TEXT, --message=TEXT
1851 specify message TEXT
1852 -u, --unified
1853 output the diff in the unified diff format
1854 -d, --diff generate a diff
1855 requestmaintainership (reqbs, reqbugownership, reqmaintainership,
1859 reqms, requestbugownership)
1860 requests to add user as maintainer or bugowner
1861 usage:
1863 osc requestmaintainership # for
1864 current user in checked out package
1865 osc requestmaintainership USER # for
1866 specified user in checked out package
1867 osc requestmaintainership PROJECT PACKAGE # for
1868 current user
1869 osc requestmaintainership PROJECT PACKAGE USER #
1870 request for specified user
1871 osc requestbugownership ... #
1873 accepts same parameters but uses bugowner role
1874 Options:
1876 -h, --help show this help message and exit
1877 -r role, --role=role
1878 specify user role (default: maintainer)
1879 -m TEXT, --message=TEXT
1880 specify message TEXT
1881 resolved
1885 Remove 'conflicted' state on working copy files
1886 If an upstream change can't be merged automatically, a file is
1888 put into in 'conflicted' ('C') state. Within the file, conflicts
1889 are marked with special <<<<<<< as well as ======== and >>>>>>>
1890 lines.
1891 After manually resolving all conflicting parts, use this command
1893 to remove the 'conflicted' state.
1894 Note: this subcommand does not semantically resolve conflicts
1896 or remove conflict markers; it merely removes the conflict-
1897 related artifact files and allows PATH to be committed again.
1898 usage:
1900 osc resolved FILE [FILE...]
1901 results (r)
1904 Shows the build results of a package or project
1905 Usage:
1907 osc results # (inside working copy of PRJ or
1908 PKG)
1909 osc results PROJECT [PACKAGE]
1910 Options:
1912 -h, --help show this help message and exit
1913 --format=FORMAT
1914 format string for csv output
1915 --csv generate output in CSV format
1916 --xml generate output in XML (former results_meta)
1917 -v, --verbose
1918 more verbose output
1919 -a ARCH, --arch=ARCH
1920 Show results only for specified architecture(s)
1921 -r REPO, --repo=REPO
1922 Show results only for specified repo(s)
1923 -l, --last-build
1924 show last build results (suc‐
1925 ceeded/failed/unknown)
1926 revert restore original wc file
1930 Examples:
1932 osc revert <modified file(s)>
1933 Note: this only works for files in a package working copy
1935 Usage:
1937 osc revert [FILES...]
1938 rremove
1942 Remove source files from selected package
1943 Usage:
1945 osc rremove PROJECT PACKAGE [FILES...]
1946 Options:
1948 -h, --help show this help message and exit
1949 -f, --force
1950 Don't ask and delete files
1951 search (bse, se, sm)
1955 Search for a project and/or package.
1956 If no option is specified osc will search for projects and pack‐
1958 ages which contains the 'search term' in their name, title or
1959 description.
1960 usage:
1962 osc search 'search term' <options>
1963 osc sm 'source package name' ('osc search --main‐
1964 tained')
1965 osc bse ... ('osc search --binary')
1966 osc se 'perl(Foo::Bar)' ('osc --package perl-
1967 Foo-Bar') Options:
1968 -h, --help show this help message and exit
1969 -B PROJECT, --baseproject=PROJECT
1970 search packages built for PROJECT (implies
1971 --binary)
1972 --binary search binary packages
1973 --csv generate output in CSV (separated by |)
1974 -M, --mine shorthand for --bugowner --package
1975 --maintained
1976 limit search results to packages with maintained
1977 attribute set.
1978 -m, --maintainer
1979 as -i, but only maintainer
1980 -b, --bugowner
1981 as -i, but only bugowner
1982 -i, --involved
1983 show projects/packages where given person (or
1984 myself)
1985 is involved as bugowner or maintainer
1986 -V, --version
1987 show package version, revision, and srcmd5. CAU‐
1988 TION:
1989 This is slow and unreliable
1990 -v, --verbose
1991 show more information
1992 -a ATTRIBUTE, --limit-to-attribute=ATTRIBUTE
1993 match only when given attribute exists in meta
1994 data
1995 --description
1996 search for matches in the 'description' element
1997 --title search for matches in the 'title' element
1998 --project search for a project
1999 --package search for a package
2000 -s, --substring
2001 Show also results where the search term is a sub
2002 string, slower search
2003 -e, --exact
2004 show only exact matches, this is default now
2005 --repos-baseurl
2006 show base URLs of download repositories
2007 service
2011 Handle source services
2012 Source services can be used to modify sources like downloading
2014 files, verify files, generating files or modify existing files.
2015 usage:
2017 osc service COMMAND (inside working copy)
2018 osc service run [SOURCE_SERVICE]
2019 osc service disabledrun
2020 osc service remoterun [PROJECT PACKAGE]
2021 COMMAND can be:
2023 run r run defined services locally, it takes an
2024 optional parameter to run only a
2025 specified source service. In case paramteres
2026 exists for this one in _service file
2027 they are used.
2028 disabledrun dr run only disabled services locally and store
2029 files as local created
2030 remoterun rr trigger a re-run on the server side
2031 setlinkrev
2035 Updates a revision number in a source link.
2036 This command adds or updates a specified revision number in a
2038 source link. The current revision of the source is used, if no
2039 revision number is specified.
2040 usage:
2042 osc setlinkrev
2043 osc setlinkrev PROJECT [PACKAGE] Options:
2044 -h, --help show this help message and exit
2045 -u, --unset
2046 remove revision in link, it will point always to
2047 latest revision
2048 -b, --use-baserev
2049 Use the revisions which exists when the original
2050 commit happend and don't try to merge later com‐
2051 mits.
2052 -R, --use-plain-revision
2053 Don't expand revsion based on baserev, the revi‐
2054 sion
2055 which was used when commit happened.
2056 -r rev, --revision=rev
2057 use the specified revision.
2058 signkey
2062 Manage Project Signing Key
2063 osc signkey [--create|--delete|--extend] <PROJECT> osc signkey
2065 [--notraverse] <PROJECT>
2066 This command is for managing gpg keys. It shows the public key
2068 by default. There is no way to download or upload the private
2069 part of a key by design.
2070 However you can create a new own key. You may want to consider
2072 to sign the public key with your own existing key.
2073 If a project has no key, the key from upper level project will
2075 be used (eg. when dropping "KDE:KDE4:Community" key, the one
2076 from "KDE:KDE4" will be used).
2077 WARNING: THE OLD KEY WILL NOT BE RESTORABLE WHEN USING DELETE OR
2079 CREATE
2080 Usage:
2082 osc signkey [ARGS...]
2083 Options:
2085 -h, --help show this help message and exit
2086 --notraverse
2087 don' traverse projects upwards to find key
2088 --delete delete the gpg signing key in this project
2089 --extend extend expiration date of the gpg public key for
2090 this
2091 project
2092 --create create new gpg signing key for this project
2093 status (st)
2097 Show status of files in working copy
2098 Show the status of files in a local working copy, indicating
2100 whether files have been changed locally, deleted, added, ...
2101 The first column in the output specifies the status and is one
2103 of the following characters:
2104 ' ' no modifications
2105 'A' Added
2106 'C' Conflicted
2107 'D' Deleted
2108 'M' Modified
2109 '?' item is not under version control
2110 '!' item is missing (removed by non-osc command) or incomplete
2111 examples:
2113 osc st
2114 osc st <directory>
2115 osc st file1 file2 ...
2116 usage:
2118 osc status [OPTS] [PATH...] Options:
2119 -h, --help show this help message and exit
2120 -e, --show-excluded
2121 also show files which are excluded by the
2122 "exclude_glob" config option
2123 -v, --verbose
2124 print extra information
2125 -q, --quiet
2126 print as little as possible
2127 submitrequest (sr, submitpac, submitreq)
2131 Create request to submit source into another Project
2132 [See http://en.opensuse.org/openSUSE:Build_Service_Collaboration
2134 for information on this topic.]
2135 See the "request" command for showing and modifing existing
2137 requests.
2138 usage:
2140 osc submitreq [OPTIONS]
2141 osc submitreq [OPTIONS] DESTPRJ [DESTPKG]
2142 osc submitreq [OPTIONS] SOURCEPRJ SOURCEPKG DESTPRJ
2143 [DESTPKG]
2144 osc submitpac ... is a shorthand for osc submitreq --cleanup
2146 ...
2147 Options:
2149 -h, --help show this help message and exit
2150 --yes proceed without asking.
2151 -d, --diff show diff only instead of creating the actual
2152 request
2153 --no-update
2154 never touch source package on accept (will break
2155 source links)
2156 --no-cleanup
2157 never remove source package on accept, but
2158 update its
2159 content
2160 --cleanup remove package if submission gets accepted
2161 (default
2162 for home:<id>:branch projects)
2163 --nodevelproject
2164 do not follow a defined devel project (primary
2165 project
2166 where a package is developed)
2167 -s SUPERSEDE, --supersede=SUPERSEDE
2168 Superseding another request by this one
2169 -r REV, --revision=REV
2170 specify a certain source revision ID (the md5
2171 sum) for
2172 the source package
2173 -m TEXT, --message=TEXT
2174 specify message TEXT
2175 triggerreason (tr)
2179 Show reason why a package got triggered to build
2180 The server decides when a package needs to get rebuild, this
2182 command shows the detailed reason for a package. A brief reason
2183 is also stored in the jobhistory, which can be accessed via "osc
2184 jobhistory".
2185 Trigger reasons might be:
2187 - new build (never build yet or rebuild manually forced)
2188 - source change (eg. on updating sources)
2189 - meta change (packages which are used for building have
2190 changed)
2191 - rebuild count sync (In case that it is configured to sync
2192 release numbers)
2193 usage in package or project directory:
2195 osc reason REPOSITORY ARCH
2196 osc reason PROJECT PACKAGE REPOSITORY ARCH
2197 undelete
2201 Restores a deleted project or package on the server.
2202 The server restores a package including the sources and meta
2204 configuration. Binaries remain to be lost and will be rebuild.
2205 usage:
2207 osc undelete PROJECT
2208 osc undelete PROJECT PACKAGE [PACKAGE ...]
2209 Options:
2211 -h, --help show this help message and exit
2212 -m TEXT, --message=TEXT
2213 specify log message TEXT
2214 update (up)
2218 Update a working copy
2219 examples:
2221 1. osc up
2223 If the current working directory is a package, update
2224 it.
2225 If the directory is a project directory, update all con‐
2226 tained
2227 packages, AND check out newly added packages.
2228 To update only checked out packages, without checking
2230 out new
2231 ones, you might want to use "osc up *" from within the
2232 project
2233 dir.
2234 2. osc up PAC
2236 Update the packages specified by the path argument(s)
2237 When --expand-link is used with source link packages, the
2239 expanded sources will be checked out. Without this option, the
2240 _link file and patches will be checked out. The option --unex‐
2241 pand-link can be used to switch back to the "raw" source with a
2242 _link file plus patch(es).
2243 Usage:
2245 osc update [ARGS...]
2246 Options:
2248 -h, --help show this help message and exit
2249 -l limit_size, --limit-size=limit_size
2250 Skip all files with a given size
2251 -S, --server-side-source-service-files
2252 Use server side generated sources instead of
2253 local
2254 generation.
2255 -s, --source-service-files
2256 Run local source services after update.
2257 -e, --expand-link
2258 if a package is a link, update to the expanded
2259 sources
2260 -u, --unexpand-link
2261 if a package is an expanded link, update to the
2262 raw
2263 _link file
2264 -r REV, --revision=REV
2265 update to specified revision (this option will
2266 be
2267 ignored if you are going to update the complete
2268 project or more than one package)
2269 updatepacmetafromspec (metafromspec)
2273 Update package meta information from a specfile
2274 ARG, if specified, is a package working copy.
2276 Usage:
2278 osc updatepacmetafromspec [ARGS...]
2279 Options:
2281 -h, --help show this help message and exit
2282 --specfile=FILE
2283 Path to specfile. (if you pass more than working
2284 copy
2285 this option is ignored)
2286 vc Edit the changes file
2290 osc vc [-m MESSAGE|-e] [filename[.changes]|path [file_with_com‐
2292 ment]] If no <filename> is given, exactly one *.changes or
2293 *.spec file has to be in the cwd or in path.
2294 The email address used in .changes file is read from BuildSer‐
2296 vice instance, or should be defined in ~/.oscrc
2297 [https://api.opensuse.org/] user = login pass = password email =
2298 user@defined.email
2299 or can be specified via mailaddr environment variable.
2301 Usage:
2303 osc vc [ARGS...]
2304 Options:
2306 -h, --help show this help message and exit
2307 -e, --just-edit
2308 just open changes (cannot be used with -m)
2309 -m MESSAGE, --message=MESSAGE
2310 add MESSAGE to changes (not open an editor)
2311 whois (user, who)
2315 Show fullname and email of a buildservice user
2316 Usage:
2318 osc whois [ARGS...]
2319 wipebinaries
2323 Delete all binary packages of a certain project/package
2324 With the optional argument <package> you can specify a certain
2326 package otherwise all binary packages in the project will be
2327 deleted.
2328 usage:
2330 osc wipebinaries OPTS # works in
2331 checked out project dir
2332 osc wipebinaries OPTS PROJECT [PACKAGE] Options:
2333 -h, --help show this help message and exit
2334 --all Delete all binaries regardless of the package
2335 status
2336 (previously default)
2337 --unresolvable
2338 Delete all binaries of packages which have
2339 dependency
2340 errors
2341 --broken Delete all binaries of packages for which the
2342 package
2343 source is bad
2344 --build-failed
2345 Delete all binaries of packages for which the
2346 build
2347 failed
2348 --build-disabled
2349 Delete all binaries of packages for which the
2350 build is
2351 disabled
2352 -r REPO, --repo=REPO
2353 Delete all binary packages for a specific repos‐
2354 itory
2355 -a ARCH, --arch=ARCH
2356 Delete all binary packages for a specific archi‐
2357 tecture
2358 GLOBAL OPTIONS
2363 Options:
2364 --version show program's version number and exit
2365 -h, --help show this help message and exit
2366 --debugger jump into the debugger before executing any‐
2367 thing
2368 --post-mortem jump into the debugger in case of errors
2369 -t, --traceback print call trace in case of errors
2370 -H, --http-debug debug HTTP traffic (filters some headers)
2371 --http-full-debug debug HTTP traffic (filters no headers)
2372 -d, --debug print info useful for debugging
2373 -A URL/alias, --apiurl=URL/alias
2374 specify URL to access API server at or an alias
2375 -c FILE, --config=FILE
2376 specify alternate configuration file
2377 --no-keyring disable usage of desktop keyring system
2378 --no-gnome-keyring disable usage of GNOME Keyring
2379 -v, --verbose increase verbosity
2380 -q, --quiet be quiet, not verbose
2381
2385 Type 'osc help <subcommand>' for more detailed help on a specific sub‐
2386 command.
2387 For additional information, see
2389 * http://en.opensuse.org/openSUSE:Build_Service_Tutorial
2390 * http://en.opensuse.org/openSUSE:OSC
2391 You can modify osc commands, or roll you own, via the plugin API:
2393 * http://en.opensuse.org/openSUSE:OSC_plugins
2394
2396 osc was written by several authors. This man page is automatically gen‐
2397 erated.
2398osc 0.132.4 Aug 2011 OSC(1)