In the openSUSE:Factory project, I did not understand the standard configuration of repositories.
When building the packages in the standard , where the workers download the packages required by chroot?
Is this method used? --> “Use Repository Binary Import”
The command is:
osc build --nodebugpackages xUbuntu_20.10 i586
the result :
[ 355s] [164/207] installing tex-common-6.15
[ 358s] /usr/sbin/update-updmap: line 166: getopt: command not found
[ 358s] dpkg: error processing package tex-common (--install):
[ 358s] installed tex-common package post-installation script
subprocess returned error exit status 127
[ 358s] Processing triggers for man-db (2.9.3-2) ...
[ 358s] Errors were encountered while processing:
[ 358s] tex-common
[ 358s] exit ...
[ 358s] opensuse failed "build guile18.dsc" at Thu Dec 3 15:11:38 UTC
although there is no problem with the online compilation :
[ 1s] lamb04 started "build guile18.dsc" at Thu Dec 3 13:43:28 UTC 2020.
[ 1s] Building Guile18 for project 'home:DenisRx:TeXmacs' repository 'xUbuntu_20.10' arch 'i586' srcmd5 'f9630deebb722ec55687291d0c9e8334'
[ 1s] processing recipe /var/cache/obs/worker/root_3/.build-srcdir/guile18.dsc ...
[ 71s] [163/207] installing libpython3.8-minimal-3.8.6-1
[ 71s] [164/207] installing tex-common-6.15
[ 71s] update-language: texlive-base not installed and configured, doing nothing!
[ 71s] Processing triggers for man-db (2.9.3-2) ...
and tex-common seems to be included on ubuntu20.10 as it appears in the
$ egrep 'Package: *tex-common' -A6 Packages
in the meantime I was able to resolve the issue - though I still do not
understand. I switched (for other reasons ...) to xrandr and use it without
explicit path information - that is working now.
Thank you for considering,
Dr.-Ing. Dieter Jurzitza 76131 Karlsruhe
I plan to use Publish Hooks. I refer to section 4.6.1 in the document "obs-admin-guild".
But I did not understand how to configure the following three parameters.
1）information about the project and its repository
2）path to published repository
Has anyone used it?Please guide me
I originally planned to use openSUSE's OBS, but unfortunately it does not support mips64el architecture, so I built an OBS on my computer.
The software package can now be compiled normally.I plan to use it to build a complete distribution, I refer toopenSUSE:Factory,
But I did not understand how the standard in its repositories is configured.Does anyone understand?Can you give me some guidance?
On Fri 18 Dec 2020 09:30:06 AM CST, Mark Stopka wrote:
>Hi all, could someone please create me a project hardware:FPGA
>(capital if possible) for tools required for FPGA development and chip
Just an observation, the verilator and iverilog packages are already
present (and in the openSUSE releases) and maintained in the electronics
Perhaps you can check for other packages with osc se <package> and see
if home project users eg cocotb might be interested in pushing to a
development project and maintaining?
Cheers Malcolm °¿° SUSE Knowledge Partner (Linux Counter #276890)
Tumbleweed 20201216 | GNOME Shell 3.38.2 | 5.9.14-1-default
Intel DQ77MK MB | Xeon E3-1245 V2 X8 @ 3.40 GHz | Intel/Nvidia
up 11:40, 2 users, load average: 0.57, 0.48, 0.43
In d:l:R:autoCRAN I face the situation that after a rebuild avalanche
quite a few packages fail with
getoldpackages: connect to back-other-opensuse:5253: Connection timed out
(worker was build79:3)
Seems it's always back-other-opensuse:5253, different builders.
Triggering a rebuild fixes each of these packages, but using the webui
is very tedius, i.e. this time 170 packages were left in this state.
Is it possible from the command line to trigger rebuilds for all
If not: Is it possible to trigger rebuilds for all failed packages?
Normally there shouldn`t be many real fails, because packages only land
in the repo if they build successfully on a local machine.
I can write scripts to do this, but maybe any of the myriad of osc options
already does it :-)
I am trying to configure subproject prjconf to override inherited prjconf "Prefer: go" from the parent project. The objective is to have devel:languages:go:metapackage_provides exhibit the error:
"unresolvable: have choice for go >= 1.14: go1.14 go1.15"
Both go1.x and the go metapackage provide go, and the ability to trigger the error in any project will serve as a baseline for refactoring work. Setting prjconf "Prefer: -go" or "Prefer: !go" do not seem to have any effect, and the subproject project package hugo builds without the desired error.
https://build.opensuse.org/project/show/devel:languages:go (Prefer: go)
https://build.opensuse.org/project/show/devel:languages:go:metapackage_prov… (Prefer: !go)
The behavior is identical in a home branch, where the parent has no prjconf Prefer: go:
Are there other methods to enforce unsetting a prjconf value? Or to display the prjconf value in effect at build time?
Software Engineer, Go Developer Experience
I'm struggling to delete the file
python3-python-dateutil-2.7.5-40.3.noarch.rpm from this repository:
and I'm asking for help.
According to the docs, the command would be
osc unpublish --repo CentOS_8 --all home:sebix:intelmq
which did not work, as well as the button in the Web UI. They only
delete the binaries as visible at
I also tried already numerous different settings for the Publish-Flag of
this package, as as well all the different combinations with rebuilds.
No matter what I try, the rpm-file with the last modification date
24-Jun-2020 remains in the repository.
I appreciate any hint what I could try next.