openSUSE Project Management Tool: Issueshttps://progress.opensuse.org/https://progress.opensuse.org/themes/openSUSE/favicon/favicon.ico?15829177842024-03-07T22:56:39ZopenSUSE Project Management Tool
Redmine openSUSE admin - communication #156874 (New): 2024-04-04 19:00 UTC: openSUSE Heroes meetinghttps://progress.opensuse.org/issues/1568742024-03-07T22:56:39Zcboltzsuse-beta@cboltz.de
<p>Where: <a href="https://meet.opensuse.org/heroes" class="external">https://meet.opensuse.org/heroes</a><br>
When: 2024-04-04 19:00 UTC / 20:00 CET<br>
Who: The openSUSE Heroes team and everybody else!</p>
<p>Topics:</p>
<ul>
<li>Questions and answers from the community</li>
<li>status reports about everything</li>
<li>review old tickets</li>
<li>(see/use checklist for additional topics)</li>
</ul>
openSUSE admin - tickets #155584 (New): New Project Space: Kernel:slowrollhttps://progress.opensuse.org/issues/1555842024-02-17T12:05:26Zrfrohlrfrohl@suse.com
<p>Hi all,</p>
<p>Looks like I need a devel project to be able to submit kernel-longterm <br>
to Factory, I opened a bug [0] but also wanted to highlight it via mail.</p>
<p>Thanks,<br>
Robert</p>
<a name="0-httpsbugzillaopensuseorgshow_bugcgiid1220027"></a>
<h2 >[0] <a href="https://bugzilla.opensuse.org/show_bug.cgi?id=1220027" class="external">https://bugzilla.opensuse.org/show_bug.cgi?id=1220027</a><a href="#0-httpsbugzillaopensuseorgshow_bugcgiid1220027" class="wiki-anchor">¶</a></h2>
<p>Security Engineer, SUSE Software Solutions Germany GmbH, Frankenstraße <br>
146, 90461 Nürnberg, Germany, GF: Ivo Totev, Andrew McDonald, Werner <br>
Knoblich (HRB 36809, AG Nürnberg)<br>
GPG: D29F 82AA 9FD5 9D6E 74B1 6370 089E DB3D 230A 2404</p>
openSUSE admin - tickets #155224 (New): OBS cannot fetch assets from code.o.ohttps://progress.opensuse.org/issues/1552242024-02-08T19:57:19Zcrameleongeorg.pfuetzenreuter@suse.com
<p>Hi,</p>
<p>trying to use the download_assets service to download a file from code.opensuse.org fails when run on the server side:</p>
<pre><code>Files could not be expanded: service error: fetching 1 asset from https://code.opensuse.org less info
service download_assets failed:
time="2024-02-08T19:51:20Z" level=warning msg="Path \"/etc/SUSEConnect\" from \"/etc/containers/mounts.conf\" doesn't exist, skipping"
time="2024-02-08T19:51:20Z" level=warning msg="Path \"/etc/zypp/credentials.d/SCCcredentials\" from \"/etc/containers/mounts.conf\" doesn't exist, skipping"
Running /usr/lib/obs/service//download_assets --outdir /var/cache/obs/6MwoWRndURl8/out
download of https://code.opensuse.org/heroes/salt-formulas/raw/main/f/test/scripts/proxy.sh failed: 500 Can't connect to code.opensuse.org:443 (Network is unreachable)
fetching 1 asset from https://code.opensuse.org
</code></pre>
<p>Using github.com works, but naturally I rather build with files downloaded from a trusted service.</p>
<p>Maybe this needs some firewall rule on the SUSE side?</p>
<p>Package/container to reproduce it with: <a href="https://build.opensuse.org/package/show/isv:SUSEInfra:Containers:Next/salt-development-heavy" class="external">https://build.opensuse.org/package/show/isv:SUSEInfra:Containers:Next/salt-development-heavy</a>.</p>
openSUSE admin - tickets #139310 (New): Dead links for package donwloadshttps://progress.opensuse.org/issues/1393102023-11-12T17:01:41Zadrian@mxlinux.org
<p>Hi,<br>
For a couple of days after build I get dead links, for example:</p>
<p><a href="https://download.opensuse.org/repositories/home:/mx-packaging/Debian_12/amd64/mx-boot-options_23.11.03_amd64.deb" class="external">https://download.opensuse.org/repositories/home:/mx-packaging/Debian_12/amd64/mx-boot-options_23.11.03_amd64.deb</a></p>
<p>The problem seems to be the binary file, the other files are correctly<br>
linked.</p>
<p>Also the "get binary packages directly" would still list the old debs<br>
<a href="https://software.opensuse.org//download.html?project=home%3Amx-packaging&package=mx-boot-options" class="external">https://software.opensuse.org//download.html?project=home%3Amx-packaging&package=mx-boot-options</a><br>
(here's we still have 23.11.02 instead of 23.11.03)</p>
<p>Is it me being impatient, how long does it usually take for a package to be<br>
listed? This was build a day ago and I cannot download the .deb files:<br>
<a href="https://build.opensuse.org/projects/home:mx-packaging/packages/mx-bootrepair/repositories/Debian_12/binaries" class="external">https://build.opensuse.org/projects/home:mx-packaging/packages/mx-bootrepair/repositories/Debian_12/binaries</a></p>
<p>Thanks,<br>
Adrian</p>
openSUSE admin - tickets #138911 (New): Failing DMARC authentification for obs mailhttps://progress.opensuse.org/issues/1389112023-10-31T20:12:10Zbruno_friedmannbruno@ioda-net.ch
<p>Hi dear admin team,</p>
<p>Since a few (one week maybe), I've seen all messages coming from obs going to <br>
be tagged as junk due to failure in DMARC auth.</p>
<p>Authentication-Results: share.ioda.net;<br>
dkim=none;<br>
spf=pass (share.ioda.net: domain of <a href="mailto:noreply@opensuse.org">noreply@opensuse.org</a> designates <br>
195.135.220.28 as permitted sender) smtp.mailfrom=<a href="mailto:noreply@opensuse.org">noreply@opensuse.org</a>;<br>
dmarc=fail reason="SPF not aligned (relaxed), No valid DKIM" <br>
header.from=suse.com (policy=quarantine)<br>
Received: from relay2.suse.de (relay2.suse.de [149.44.160.134])<br>
by smtp-out1.suse.de (Postfix) with ESMTP id D9B472185E;<br>
Fri, 20 Oct 2023 21:22:46 +0000 (UTC)<br>
Received: from obs-gateway-1.obsmgmt.opensuse.org (unknown [10.151.134.21])<br>
by relay2.suse.de (Postfix) with ESMTP id 9D0B82C9AD;<br>
Fri, 20 Oct 2023 21:22:46 +0000 (UTC)<br>
Received: from api.obsmgmt.opensuse.org (api.obsmgmt.opensuse.org <br>
[192.168.2.100])<br>
by obs-gateway-1.obsmgmt.opensuse.org (Postfix) with ESMTP id <br>
C137C135E8;<br>
Fri, 20 Oct 2023 21:22:46 +0000 (UTC)<br>
Received: by api.obsmgmt.opensuse.org (Postfix, from userid 30)<br>
id BF654399E9; Fri, 20 Oct 2023 21:22:46 +0000 (UTC)</p>
<p>Is it intentional? </p>
<p>-- <br>
Bruno Friedmann<br>
Ioda-Net Sàrl <a href="http://www.ioda-net.ch" class="external">www.ioda-net.ch</a><br>
expertise en open-source</p>
<p>GPG KEY: E4720D8715B696B4 <br>
irc: tigerfoot</p>
<p>Computing freedom with openSUSE Tumbleweed - 20231020<br>
Linux 6.5.6-1-default x86_64 GNU/Linux, nvidia: 535.113.01<br>
Qt: 5.15.11, KDE Frameworks: 5.111.0, Plasma: 5.27.8, kmail2 5.24.2 (23.08.2)</p>
openSUSE admin - tickets #135584 (New): ERROR:root: Stale lock must be removed manuallyhttps://progress.opensuse.org/issues/1355842023-09-12T09:05:35Zsven@nierlein.desven@nierlein.de
<p>Hi Admins,</p>
<p>Since a couple of days i am getting an error on:<br>
<a href="https://build.opensuse.org/package/show/home:naemon:daily/thruk" class="external">https://build.opensuse.org/package/show/home:naemon:daily/thruk</a></p>
<blockquote>
<p>Files could not be expanded: service error: ERROR:root: Stale lock must be removed manually: '/var/cache/obs/dCMVXiM3mrCg/scm-cache/e59b87037c509a38032b4257c7649d6a5009d265eb93d1ace4fff34266caaedb-pc/Thruk/../.lock' less info</p>
<p>service tar_scm failed:<br>
time="2023-09-12T07:57:58Z" level=warning msg="Path \"/etc/SUSEConnect\" from \"/etc/containers/mounts.conf\" doesn't exist, skipping"<br>
time="2023-09-12T07:57:58Z" level=warning msg="Path \"/etc/zypp/credentials.d/SCCcredentials\" from \"/etc/containers/mounts.conf\" doesn't exist, skipping"<br>
Running /usr/lib/obs/service//tar_scm --scm git --url <a href="https://github.com/sni/Thruk.git" class="external">https://github.com/sni/Thruk.git</a> --filename thruk --versionformat @PARENT_TAG@+@TAG_OFFSET@~%cd~%h --versionrewrite-pattern v(.*?)(-alpha|$) --versionrewrite-replacement \1 --changesgenerate enable --changesauthor <a href="mailto:devel@thruk.org">devel@thruk.org</a> --exclude debian/source/format --outdir /var/cache/obs/dCMVXiM3mrCg/out<br>
ERROR:root: Lock older than 24h<br>
ERROR:root: Please check if another process is currently running.<br>
ERROR:root: Stale lock must be removed manually: '/var/cache/obs/dCMVXiM3mrCg/scm-cache/e59b87037c509a38032b4257c7649d6a5009d265eb93d1ace4fff34266caaedb-pc/Thruk/../.lock'</p>
</blockquote>
<p>Is there anything i did wrong or anything i can do to resolve the situation?</p>
<p>Thanks,<br>
Sven</p>
openSUSE admin - tickets #126332 (New): Fwd: How to add a new project under specific namespace?https://progress.opensuse.org/issues/1263322023-03-22T01:33:05Zkenhys
<p>Hi,</p>
<p>I've posted "How to add a new project under specific namespace?" [1]<br>
Then Rubhan kindly advised me to contact <a href="mailto:admin@opensuse.org">admin@opensuse.org</a>.</p>
<p>[1] <a href="https://lists.opensuse.org/archives/list/buildservice@lists.opensuse.org/thread/UPOJG6UX7KMMISVIGPWT35JV4KPUWFRZ/">https://lists.opensuse.org/archives/list/buildservice@lists.opensuse.org/thread/UPOJG6UX7KMMISVIGPWT35JV4KPUWFRZ/</a></p>
<p>Here is the summary:</p>
<ul>
<li>want to create a completely new sub-project "milter-manager" under server:mail</li>
<li>want me (kenhys) [2] as a maintainer role for that "milter-manager"
sub-project.</li>
</ul>
<p>[2] <a href="https://build.opensuse.org/project/show/home:kenhys">https://build.opensuse.org/project/show/home:kenhys</a></p>
<p>Could you create above one, please?</p>
<p>Regards,</p>
<p>---------- Forwarded message ---------<br>
From: Rubhan Azeem <a href="mailto:rubhan.azeem@suse.com">rubhan.azeem@suse.com</a><br>
Date: 2023年3月22日(水) 0:39<br>
Subject: Re: How to add a new project under specific namespace?<br>
To: Kentaro Hayashi <a href="mailto:kenhys@gmail.com">kenhys@gmail.com</a></p>
<p>Hi Hayashi,</p>
<p>Thanks for contacting us. To create a new sub-project under<br>
server:mail you need to contact the maintainers. They can create a<br>
sub-project for you. If you want to create a completely new project<br>
outside of your home project, you can send a request to<br>
<a href="mailto:admin@opensuse.org">admin@opensuse.org</a>.</p>
<p>I hope it answers your query. If that doesn't help then please let us know.</p>
<p>Kind regards,<br>
Rubhan</p>
<hr>
<p>From: Kentaro Hayashi <a href="mailto:kenhys@gmail.com">kenhys@gmail.com</a><br>
Sent: Monday, March 20, 2023 8:29 AM<br>
To: <a href="mailto:buildservice@lists.opensuse.org">buildservice@lists.opensuse.org</a> <a href="mailto:buildservice@lists.opensuse.org">buildservice@lists.opensuse.org</a><br>
Subject: How to add a new project under specific namespace?</p>
<p>Hi,</p>
<p>According to <a href="https://build.opensuse.org/project/new">https://build.opensuse.org/project/new</a>,<br>
When I want to create a new project outside of my home project,<br>
I need to contact via email, but, apparently, it will not work because it<br>
bounces email (<a href="mailto:noreply@opensuse.org">noreply@opensuse.org</a>). It seems that it is a known-issue since<br>
2022.</p>
<p>[1] <a href="https://github.com/openSUSE/open-build-service/issues/12356">https://github.com/openSUSE/open-build-service/issues/12356</a></p>
<p>Is there documented instruction on how to request a new project under<br>
existing specific namespace (such as server:mail) ?</p>
<p>What I learned from the existing documentation, it should create a<br>
new project in my case, but I couldn't find official documentation to do it yet.</p>
<p>I've tried to use obs under my home project [2] whether it satisfies<br>
our requirement<br>
in beforehand.</p>
<p>Here are our requirements for milter-manager project:</p>
<ol>
<li><p>maintain the package under the meaningful namespace</p>
<ul>
<li>package itself may be maintained under the home project, but
it is better to maintain under a more meaningful namespace because
milter-manager is related to mail service.</li>
</ul></li>
<li><p>publish multiple versions in the same repository</p>
<ul>
<li>maintain the latest version only is not enough.</li>
<li>It may work by submitting multiple versioned package to
server:mail namespace, but
it causes namespace polutions with milter-manager-1.x.x,
milter-manager-2.x.x and more.</li>
<li>To avoid such a situation, it should be server:mail:milter-manager
project to group multiple versions
under it's own project namespace.</li>
</ul></li>
<li><p>want to publish not only openSUSE, but also other distributions</p>
<ul>
<li>It requires configuring project meta information to do, so it can't be
satisfied with submitting packages to server:mail.
It need to own server:mail:milter-manager project namespace.</li>
</ul></li>
</ol>
<p>To satisfy both of them, I want to create a new project.</p>
<p>Correct me if I understand wrongly.</p>
<p>Regards,</p>
<p>[2] <a href="https://build.opensuse.org/project/show/home:kenhys">https://build.opensuse.org/project/show/home:kenhys</a></p>
<p>-- <br>
Kentaro Hayashi <a href="mailto:kenhys@gmail.com">kenhys@gmail.com</a></p>
openSUSE admin - tickets #122254 (New): Migrate away from login proxies to SSOhttps://progress.opensuse.org/issues/1222542022-12-20T20:31:20Zhellcphel@lcp.world
<p>It would be nice to slowly migrate over to using SSO instead of login proxies for logging into our infrastructure. The list below covers all of the services that still use login proxies. Some of them aren't under our jurisdiction, some may not even have login capabilities, but they still are behind login proxies, because why not (they shouldn't be, get them out of there).</p>
openSUSE admin - tickets #121621 (New): A Dedicated Devel Project for Juliahttps://progress.opensuse.org/issues/1216212022-12-07T07:50:19Zuncomfyhalomacro
<p>Hello. Not sure if this is the right place to ask but I went to the<br>
openSUSE wiki and read that I need to contact you and the openSUSE team for<br>
a humble request.</p>
<p>The Julia language in the openSUSE science repository has stagnated for<br>
quite some time now and is stuck in version 1.6.3. Latest stable release is<br>
now 1.8.3.</p>
<p>Hence, I request for the openSUSE Team to allow me to have a dedicated<br>
devel project for Julia. This is to test future Julia builds and keep it in<br>
an isolated devel project environment so it won't mess up another devel<br>
project e.g. science.</p>
<p>I hope this request is accepted.</p>
<p>Sincerely,<br>
Soc Virnyl Estela</p>
openSUSE admin - tickets #121474 (New): OBS (build.opensuse.org) Arch Linux builds are broken, ma...https://progress.opensuse.org/issues/1214742022-12-06T00:47:58Z5aogkbi7kcm4@opayq.com
<p>Dear OBS Admins,</p>
<p>Recently Arch Linux packages on build.opensuse.org stop building, and it maybe because the OBS config is missing a package dependency.</p>
<p>Please also refer to:<br>
<a href="https://github.com/openSUSE/open-build-service/issues/13403" class="external">https://github.com/openSUSE/open-build-service/issues/13403</a><br>
<a href="https://github.com/openSUSE/obs-build/pull/903" class="external">https://github.com/openSUSE/obs-build/pull/903</a></p>
<p>I am forwarding this issue to OBS Admins as per hennevogel's comment on GitHub: <a href="https://github.com/openSUSE/open-build-service/issues/13403#issuecomment-1337651442" class="external">https://github.com/openSUSE/open-build-service/issues/13403#issuecomment-1337651442</a></p>
<p>Can you please look at the issue?</p>
<p>Thank you,<br>
antermin</p>
openSUSE admin - tickets #117166 (New): Archive redirecthttps://progress.opensuse.org/issues/1171662022-09-23T14:11:12Zyecril71plgiecrilj@stegny.2a.pl
<p>Kiedy pakiet staje się niedostępny do pobrania z repozytorium Tumbleweed i przenosi się do archiwum, klient, próbujący i pobrać, otrzymuje wynik 404 (zasób nie znaleziony), którego oprogramowanie pobierające pakiety nie umie dobrze obsłużyć. Omawiając zgłoszenie błędu 1203303, doszliśmy do wniosku, że w takiej sytuacji serwer powinien zwracać przekierowanie stałe do odpowiedniego pakietu, znajdującego się w archiwum.</p>
openSUSE admin - tickets #110482 (New): ls: cannot access '/home/mirror/publish_logs/15.2/2021/12...https://progress.opensuse.org/issues/1104822022-04-29T17:33:22Zpjessenper@computer.org
<p>This is regularly reported to admin-auto.<br>
For instance, since JUne 2021:</p>
<p>ls: cannot access '/home/mirror/publish_logs/15.2/2021/06/24/<em>-deletes.log': No such file or directory<br>
ls: cannot access '/home/mirror/publish_logs/15.2/2021/06/25/</em>-deletes.log': No such file or directory<br>
ls: cannot access '/home/mirror/publish_logs/15.2/2021/06/26/<em>-deletes.log': No such file or directory<br>
ls: cannot access '/home/mirror/publish_logs/15.2/2021/06/27/</em>-deletes.log': No such file or directory<br>
ls: cannot access '/home/mirror/publish_logs/15.2/2021/06/28/<em>-deletes.log': No such file or directory<br>
ls: cannot access '/home/mirror/publish_logs/15.2/2021/06/29/</em>-deletes.log': No such file or directory<br>
ls: cannot access '/home/mirror/publish_logs/15.2/2021/06/30/<em>-deletes.log': No such file or directory<br>
ls: cannot access '/home/mirror/publish_logs/15.2/2021/07/01/</em>-deletes.log': No such file or directory<br>
ls: cannot access '/home/mirror/publish_logs/15.2/2021/07/02/<em>-deletes.log': No such file or directory<br>
ls: cannot access '/home/mirror/publish_logs/15.2/2021/07/03/</em>-deletes.log': No such file or directory<br>
ls: cannot access '/home/mirror/publish_logs/15.2/2021/07/04/<em>-deletes.log': No such file or directory<br>
ls: cannot access '/home/mirror/publish_logs/15.2/2021/07/05/</em>-deletes.log': No such file or directory<br>
ls: cannot access '/home/mirror/publish_logs/15.2/2021/07/06/<em>-deletes.log': No such file or directory<br>
ls: cannot access '/home/mirror/publish_logs/15.2/2021/07/12/</em>-deletes.log': No such file or directory<br>
ls: cannot access '/home/mirror/publish_logs/15.2/2021/07/13/<em>-deletes.log': No such file or directory<br>
ls: cannot access '/home/mirror/publish_logs/15.2/2021/07/14/</em>-deletes.log': No such file or directory<br>
ls: cannot access '/home/mirror/publish_logs/15.2/2021/07/15/<em>-deletes.log': No such file or directory<br>
ls: cannot access '/home/mirror/publish_logs/15.2/2021/07/16/</em>-deletes.log': No such file or directory<br>
ls: cannot access '/home/mirror/publish_logs/15.2/2021/07/17/<em>-deletes.log': No such file or directory<br>
ls: cannot access '/home/mirror/publish_logs/15.2/2021/07/18/</em>-deletes.log': No such file or directory<br>
ls: cannot access '/home/mirror/publish_logs/15.2/2021/07/19/<em>-deletes.log': No such file or directory<br>
ls: cannot access '/home/mirror/publish_logs/15.2/2021/07/20/</em>-deletes.log': No such file or directory<br>
ls: cannot access '/home/mirror/publish_logs/15.2/2021/07/21/<em>-deletes.log': No such file or directory<br>
ls: cannot access '/home/mirror/publish_logs/15.2/2021/07/22/</em>-deletes.log': No such file or directory<br>
ls: cannot access '/home/mirror/publish_logs/15.2/2021/07/23/<em>-deletes.log': No such file or directory<br>
ls: cannot access '/home/mirror/publish_logs/15.2/2021/07/24/</em>-deletes.log': No such file or directory<br>
ls: cannot access '/home/mirror/publish_logs/15.2/2021/07/25/<em>-deletes.log': No such file or directory<br>
ls: cannot access '/home/mirror/publish_logs/15.2/2021/07/26/</em>-deletes.log': No such file or directory<br>
ls: cannot access '/home/mirror/publish_logs/15.2/2021/07/27/<em>-deletes.log': No such file or directory<br>
ls: cannot access '/home/mirror/publish_logs/15.2/2021/07/28/</em>-deletes.log': No such file or directory<br>
ls: cannot access '/home/mirror/publish_logs/15.2/2021/07/29/<em>-deletes.log': No such file or directory<br>
ls: cannot access '/home/mirror/publish_logs/15.2/2021/07/30/</em>-deletes.log': No such file or directory<br>
ls: cannot access '/home/mirror/publish_logs/15.2/2021/07/31/<em>-deletes.log': No such file or directory<br>
ls: cannot access '/home/mirror/publish_logs/15.2/2021/08/01/</em>-deletes.log': No such file or directory<br>
ls: cannot access '/home/mirror/publish_logs/15.2/2021/08/02/<em>-deletes.log': No such file or directory<br>
ls: cannot access '/home/mirror/publish_logs/15.2/2021/08/03/</em>-deletes.log': No such file or directory<br>
ls: cannot access '/home/mirror/publish_logs/15.2/2021/08/04/<em>-deletes.log': No such file or directory<br>
ls: cannot access '/home/mirror/publish_logs/15.2/2021/08/05/</em>-deletes.log': No such file or directory<br>
ls: cannot access '/home/mirror/publish_logs/15.2/2021/08/06/<em>-deletes.log': No such file or directory<br>
ls: cannot access '/home/mirror/publish_logs/15.2/2021/08/07/</em>-deletes.log': No such file or directory<br>
ls: cannot access '/home/mirror/publish_logs/15.2/2021/08/08/<em>-deletes.log': No such file or directory<br>
ls: cannot access '/home/mirror/publish_logs/15.2/2021/08/09/</em>-deletes.log': No such file or directory<br>
ls: cannot access '/home/mirror/publish_logs/15.2/2021/08/10/<em>-deletes.log': No such file or directory<br>
ls: cannot access '/home/mirror/publish_logs/15.2/2021/08/11/</em>-deletes.log': No such file or directory<br>
ls: cannot access '/home/mirror/publish_logs/15.2/2021/08/12/<em>-deletes.log': No such file or directory<br>
ls: cannot access '/home/mirror/publish_logs/15.2/2021/08/13/</em>-deletes.log': No such file or directory<br>
ls: cannot access '/home/mirror/publish_logs/15.2/2021/08/14/<em>-deletes.log': No such file or directory<br>
ls: cannot access '/home/mirror/publish_logs/15.2/2021/08/15/</em>-deletes.log': No such file or directory<br>
ls: cannot access '/home/mirror/publish_logs/15.2/2021/08/16/<em>-deletes.log': No such file or directory<br>
ls: cannot access '/home/mirror/publish_logs/15.2/2021/08/17/</em>-deletes.log': No such file or directory<br>
ls: cannot access '/home/mirror/publish_logs/15.2/2021/08/18/<em>-deletes.log': No such file or directory<br>
ls: cannot access '/home/mirror/publish_logs/15.2/2021/08/19/</em>-deletes.log': No such file or directory<br>
ls: cannot access '/home/mirror/publish_logs/15.2/2021/08/20/<em>-deletes.log': No such file or directory<br>
ls: cannot access '/home/mirror/publish_logs/15.2/2021/08/21/</em>-deletes.log': No such file or directory<br>
ls: cannot access '/home/mirror/publish_logs/15.2/2021/08/22/<em>-deletes.log': No such file or directory<br>
ls: cannot access '/home/mirror/publish_logs/15.2/2021/08/23/</em>-deletes.log': No such file or directory<br>
ls: cannot access '/home/mirror/publish_logs/15.2/2021/08/24/<em>-deletes.log': No such file or directory<br>
ls: cannot access '/home/mirror/publish_logs/15.2/2021/08/25/</em>-deletes.log': No such file or directory<br>
ls: cannot access '/home/mirror/publish_logs/15.2/2021/08/26/<em>-deletes.log': No such file or directory<br>
ls: cannot access '/home/mirror/publish_logs/15.2/2021/08/27/</em>-deletes.log': No such file or directory<br>
ls: cannot access '/home/mirror/publish_logs/15.2/2021/08/28/<em>-deletes.log': No such file or directory<br>
ls: cannot access '/home/mirror/publish_logs/15.2/2021/08/29/</em>-deletes.log': No such file or directory<br>
ls: cannot access '/home/mirror/publish_logs/15.2/2021/08/30/<em>-deletes.log': No such file or directory<br>
ls: cannot access '/home/mirror/publish_logs/15.2/2021/08/31/</em>-deletes.log': No such file or directory<br>
ls: cannot access '/home/mirror/publish_logs/15.2/2021/09/01/<em>-deletes.log': No such file or directory<br>
ls: cannot access '/home/mirror/publish_logs/15.2/2021/09/02/</em>-deletes.log': No such file or directory<br>
ls: cannot access '/home/mirror/publish_logs/15.2/2021/09/03/<em>-deletes.log': No such file or directory<br>
ls: cannot access '/home/mirror/publish_logs/15.2/2021/09/04/</em>-deletes.log': No such file or directory<br>
ls: cannot access '/home/mirror/publish_logs/15.2/2021/09/05/<em>-deletes.log': No such file or directory<br>
ls: cannot access '/home/mirror/publish_logs/15.2/2021/09/06/</em>-deletes.log': No such file or directory<br>
ls: cannot access '/home/mirror/publish_logs/15.2/2021/09/07/<em>-deletes.log': No such file or directory<br>
ls: cannot access '/home/mirror/publish_logs/15.2/2021/09/08/</em>-deletes.log': No such file or directory<br>
ls: cannot access '/home/mirror/publish_logs/15.2/2021/09/09/<em>-deletes.log': No such file or directory<br>
ls: cannot access '/home/mirror/publish_logs/15.2/2021/09/10/</em>-deletes.log': No such file or directory<br>
ls: cannot access '/home/mirror/publish_logs/15.2/2021/09/11/<em>-deletes.log': No such file or directory<br>
ls: cannot access '/home/mirror/publish_logs/15.2/2021/09/12/</em>-deletes.log': No such file or directory<br>
ls: cannot access '/home/mirror/publish_logs/15.2/2021/09/13/<em>-deletes.log': No such file or directory<br>
ls: cannot access '/home/mirror/publish_logs/15.2/2021/09/14/</em>-deletes.log': No such file or directory<br>
ls: cannot access '/home/mirror/publish_logs/15.2/2021/09/15/<em>-deletes.log': No such file or directory<br>
ls: cannot access '/home/mirror/publish_logs/15.2/2021/09/16/</em>-deletes.log': No such file or directory<br>
ls: cannot access '/home/mirror/publish_logs/15.2/2021/09/17/<em>-deletes.log': No such file or directory<br>
ls: cannot access '/home/mirror/publish_logs/15.2/2021/09/18/</em>-deletes.log': No such file or directory<br>
ls: cannot access '/home/mirror/publish_logs/15.2/2021/09/19/<em>-deletes.log': No such file or directory<br>
ls: cannot access '/home/mirror/publish_logs/15.2/2021/09/20/</em>-deletes.log': No such file or directory<br>
ls: cannot access '/home/mirror/publish_logs/15.2/2021/09/21/<em>-deletes.log': No such file or directory<br>
ls: cannot access '/home/mirror/publish_logs/15.2/2021/09/22/</em>-deletes.log': No such file or directory<br>
ls: cannot access '/home/mirror/publish_logs/15.2/2021/09/23/<em>-deletes.log': No such file or directory<br>
ls: cannot access '/home/mirror/publish_logs/15.2/2021/09/24/</em>-deletes.log': No such file or directory<br>
ls: cannot access '/home/mirror/publish_logs/15.2/2021/09/25/<em>-deletes.log': No such file or directory<br>
ls: cannot access '/home/mirror/publish_logs/15.2/2021/09/26/</em>-deletes.log': No such file or directory<br>
ls: cannot access '/home/mirror/publish_logs/15.2/2021/09/27/<em>-deletes.log': No such file or directory<br>
ls: cannot access '/home/mirror/publish_logs/15.2/2021/09/28/</em>-deletes.log': No such file or directory<br>
ls: cannot access '/home/mirror/publish_logs/15.2/2021/09/29/<em>-deletes.log': No such file or directory<br>
ls: cannot access '/home/mirror/publish_logs/15.2/2021/09/30/</em>-deletes.log': No such file or directory<br>
ls: cannot access '/home/mirror/publish_logs/15.2/2021/10/01/<em>-deletes.log': No such file or directory<br>
ls: cannot access '/home/mirror/publish_logs/15.2/2021/10/02/</em>-deletes.log': No such file or directory<br>
ls: cannot access '/home/mirror/publish_logs/15.2/2021/10/03/<em>-deletes.log': No such file or directory<br>
ls: cannot access '/home/mirror/publish_logs/15.2/2021/10/04/</em>-deletes.log': No such file or directory<br>
ls: cannot access '/home/mirror/publish_logs/15.2/2021/10/05/<em>-deletes.log': No such file or directory<br>
ls: cannot access '/home/mirror/publish_logs/15.2/2021/10/06/</em>-deletes.log': No such file or directory<br>
ls: cannot access '/home/mirror/publish_logs/15.2/2021/10/07/<em>-deletes.log': No such file or directory<br>
ls: cannot access '/home/mirror/publish_logs/15.2/2021/10/08/</em>-deletes.log': No such file or directory<br>
ls: cannot access '/home/mirror/publish_logs/15.2/2021/10/09/<em>-deletes.log': No such file or directory<br>
ls: cannot access '/home/mirror/publish_logs/15.2/2021/10/10/</em>-deletes.log': No such file or directory<br>
ls: cannot access '/home/mirror/publish_logs/15.2/2021/10/11/<em>-deletes.log': No such file or directory<br>
ls: cannot access '/home/mirror/publish_logs/15.2/2021/10/12/</em>-deletes.log': No such file or directory<br>
ls: cannot access '/home/mirror/publish_logs/15.2/2021/10/13/<em>-deletes.log': No such file or directory<br>
ls: cannot access '/home/mirror/publish_logs/15.2/2021/10/14/</em>-deletes.log': No such file or directory<br>
ls: cannot access '/home/mirror/publish_logs/15.2/2021/10/15/<em>-deletes.log': No such file or directory<br>
ls: cannot access '/home/mirror/publish_logs/15.2/2021/10/16/</em>-deletes.log': No such file or directory<br>
ls: cannot access '/home/mirror/publish_logs/15.2/2021/10/17/<em>-deletes.log': No such file or directory<br>
ls: cannot access '/home/mirror/publish_logs/15.2/2021/10/18/</em>-deletes.log': No such file or directory<br>
ls: cannot access '/home/mirror/publish_logs/15.2/2021/10/19/<em>-deletes.log': No such file or directory<br>
ls: cannot access '/home/mirror/publish_logs/15.2/2021/10/20/</em>-deletes.log': No such file or directory<br>
ls: cannot access '/home/mirror/publish_logs/15.2/2021/10/21/<em>-deletes.log': No such file or directory<br>
ls: cannot access '/home/mirror/publish_logs/15.2/2021/10/22/</em>-deletes.log': No such file or directory<br>
ls: cannot access '/home/mirror/publish_logs/15.2/2021/10/23/<em>-deletes.log': No such file or directory<br>
ls: cannot access '/home/mirror/publish_logs/15.2/2021/10/24/</em>-deletes.log': No such file or directory<br>
ls: cannot access '/home/mirror/publish_logs/15.2/2021/10/25/<em>-deletes.log': No such file or directory<br>
ls: cannot access '/home/mirror/publish_logs/15.2/2021/10/26/</em>-deletes.log': No such file or directory<br>
ls: cannot access '/home/mirror/publish_logs/15.2/2021/10/27/<em>-deletes.log': No such file or directory<br>
ls: cannot access '/home/mirror/publish_logs/15.2/2021/10/28/</em>-deletes.log': No such file or directory<br>
ls: cannot access '/home/mirror/publish_logs/15.2/2021/10/29/<em>-deletes.log': No such file or directory<br>
ls: cannot access '/home/mirror/publish_logs/15.2/2021/10/30/</em>-deletes.log': No such file or directory<br>
ls: cannot access '/home/mirror/publish_logs/15.2/2021/10/31/<em>-deletes.log': No such file or directory<br>
ls: cannot access '/home/mirror/publish_logs/15.2/2021/11/01/</em>-deletes.log': No such file or directory<br>
ls: cannot access '/home/mirror/publish_logs/15.2/2021/11/02/<em>-deletes.log': No such file or directory<br>
ls: cannot access '/home/mirror/publish_logs/15.2/2021/11/03/</em>-deletes.log': No such file or directory<br>
ls: cannot access '/home/mirror/publish_logs/15.2/2021/11/04/<em>-deletes.log': No such file or directory<br>
ls: cannot access '/home/mirror/publish_logs/15.2/2021/11/05/</em>-deletes.log': No such file or directory<br>
ls: cannot access '/home/mirror/publish_logs/15.2/2021/11/06/<em>-deletes.log': No such file or directory<br>
ls: cannot access '/home/mirror/publish_logs/15.2/2021/11/07/</em>-deletes.log': No such file or directory<br>
ls: cannot access '/home/mirror/publish_logs/15.2/2021/11/08/<em>-deletes.log': No such file or directory<br>
ls: cannot access '/home/mirror/publish_logs/15.2/2021/11/09/</em>-deletes.log': No such file or directory<br>
ls: cannot access '/home/mirror/publish_logs/15.2/2021/11/11/<em>-deletes.log': No such file or directory<br>
ls: cannot access '/home/mirror/publish_logs/15.2/2021/11/12/</em>-deletes.log': No such file or directory<br>
ls: cannot access '/home/mirror/publish_logs/15.2/2021/11/13/<em>-deletes.log': No such file or directory<br>
ls: cannot access '/home/mirror/publish_logs/15.2/2021/11/14/</em>-deletes.log': No such file or directory<br>
ls: cannot access '/home/mirror/publish_logs/15.2/2021/11/15/<em>-deletes.log': No such file or directory<br>
ls: cannot access '/home/mirror/publish_logs/15.2/2021/11/16/</em>-deletes.log': No such file or directory<br>
ls: cannot access '/home/mirror/publish_logs/15.2/2021/11/17/<em>-deletes.log': No such file or directory<br>
ls: cannot access '/home/mirror/publish_logs/15.2/2021/11/18/</em>-deletes.log': No such file or directory<br>
ls: cannot access '/home/mirror/publish_logs/15.2/2021/11/19/<em>-deletes.log': No such file or directory<br>
ls: cannot access '/home/mirror/publish_logs/15.2/2021/11/20/</em>-deletes.log': No such file or directory<br>
ls: cannot access '/home/mirror/publish_logs/15.2/2021/11/21/<em>-deletes.log': No such file or directory<br>
ls: cannot access '/home/mirror/publish_logs/15.2/2021/11/22/</em>-deletes.log': No such file or directory<br>
ls: cannot access '/home/mirror/publish_logs/15.2/2021/11/23/<em>-deletes.log': No such file or directory<br>
ls: cannot access '/home/mirror/publish_logs/15.2/2021/11/24/</em>-deletes.log': No such file or directory<br>
ls: cannot access '/home/mirror/publish_logs/15.2/2021/11/25/<em>-deletes.log': No such file or directory<br>
ls: cannot access '/home/mirror/publish_logs/15.2/2021/11/26/</em>-deletes.log': No such file or directory<br>
ls: cannot access '/home/mirror/publish_logs/15.2/2021/11/27/<em>-deletes.log': No such file or directory<br>
ls: cannot access '/home/mirror/publish_logs/15.2/2021/11/28/</em>-deletes.log': No such file or directory<br>
ls: cannot access '/home/mirror/publish_logs/15.2/2021/11/29/<em>-deletes.log': No such file or directory<br>
ls: cannot access '/home/mirror/publish_logs/15.2/2021/11/30/</em>-deletes.log': No such file or directory<br>
ls: cannot access '/home/mirror/publish_logs/15.2/2021/12/01/<em>-deletes.log': No such file or directory<br>
ls: cannot access '/home/mirror/publish_logs/15.2/2021/12/02/</em>-deletes.log': No such file or directory<br>
ls: cannot access '/home/mirror/publish_logs/15.2/2021/12/03/<em>-deletes.log': No such file or directory<br>
ls: cannot access '/home/mirror/publish_logs/15.2/2021/12/04/</em>-deletes.log': No such file or directory<br>
ls: cannot access '/home/mirror/publish_logs/15.2/2021/12/05/<em>-deletes.log': No such file or directory<br>
ls: cannot access '/home/mirror/publish_logs/15.2/2021/12/06/</em>-deletes.log': No such file or directory<br>
ls: cannot access '/home/mirror/publish_logs/15.2/2021/12/08/<em>-deletes.log': No such file or directory<br>
ls: cannot access '/home/mirror/publish_logs/15.2/2021/12/12/</em>-deletes.log': No such file or directory<br>
ls: cannot access '/home/mirror/publish_logs/15.2/2021/12/14/<em>-deletes.log': No such file or directory<br>
ls: cannot access '/home/mirror/publish_logs/15.2/2021/12/15/</em>-deletes.log': No such file or directory<br>
ls: cannot access '/home/mirror/publish_logs/15.2/2021/12/16/<em>-deletes.log': No such file or directory<br>
ls: cannot access '/home/mirror/publish_logs/15.2/2021/12/17/</em>-deletes.log': No such file or directory<br>
ls: cannot access '/home/mirror/publish_logs/15.2/2021/12/18/<em>-deletes.log': No such file or directory<br>
ls: cannot access '/home/mirror/publish_logs/15.2/2021/12/19/</em>-deletes.log': No such file or directory<br>
ls: cannot access '/home/mirror/publish_logs/15.2/2021/12/20/<em>-deletes.log': No such file or directory<br>
ls: cannot access '/home/mirror/publish_logs/15.2/2021/12/21/</em>-deletes.log': No such file or directory<br>
ls: cannot access '/home/mirror/publish_logs/15.2/2021/12/22/<em>-deletes.log': No such file or directory<br>
ls: cannot access '/home/mirror/publish_logs/15.2/2021/12/23/</em>-deletes.log': No such file or directory<br>
ls: cannot access '/home/mirror/publish_logs/15.2/2021/12/24/<em>-deletes.log': No such file or directory<br>
ls: cannot access '/home/mirror/publish_logs/15.2/2021/12/25/</em>-deletes.log': No such file or directory<br>
ls: cannot access '/home/mirror/publish_logs/15.2/2021/12/26/<em>-deletes.log': No such file or directory<br>
ls: cannot access '/home/mirror/publish_logs/15.2/2021/12/27/</em>-deletes.log': No such file or directory<br>
ls: cannot access '/home/mirror/publish_logs/15.2/2021/12/28/<em>-deletes.log': No such file or directory<br>
ls: cannot access '/home/mirror/publish_logs/15.2/2021/12/29/</em>-deletes.log': No such file or directory<br>
ls: cannot access '/home/mirror/publish_logs/15.2/2021/12/30/<em>-deletes.log': No such file or directory<br>
ls: cannot access '/home/mirror/publish_logs/15.2/2021/12/31/</em>-deletes.log': No such file or directory</p>
openSUSE admin - tickets #96473 (New): Adding "Everything" for openEuler 20.03https://progress.opensuse.org/issues/964732021-08-02T17:45:37Zjuliogonzalezgiljgonzalez@suse.com
<p>Right now:<br>
<a href="https://build.opensuse.org/projects/openEuler:20.03/meta" class="external">https://build.opensuse.org/projects/openEuler:20.03/meta</a></p>
<p>Has OS, updates (which in fact is disabled by default at least on 20.03-SP1), <br>
EPOL and EPOL-updates (are they broken? I see a red warning sign at https://<br>
build.opensuse.org/project/show/openEuler:20.03)</p>
<p>Question is: can the repository "Everything" be added as well?</p>
<p><a href="https://repo.openeuler.org/openEuler-20.03-LTS-SP1/everything/${arch}/" class="external">https://repo.openeuler.org/openEuler-20.03-LTS-SP1/everything/${arch}/</a></p>
<p>Most likely the same should be done for<br>
<a href="https://build.opensuse.org/project/show/openEuler:21.03" class="external">https://build.opensuse.org/project/show/openEuler:21.03</a></p>
<p>Thanks.</p>
<p>(Also reported at <a href="https://lists.opensuse.org/archives/list/buildservice@lists.opensuse.org/thread/GXTWI7GRO7OF23OPPH65ETMU5PFZSEZA/" class="external">https://lists.opensuse.org/archives/list/buildservice@lists.opensuse.org/thread/GXTWI7GRO7OF23OPPH65ETMU5PFZSEZA/</a>)</p>
<p>-- <br>
Julio González Gil<br>
Release Engineer, SUSE Manager and Uyuni<br>
<a href="mailto:jgonzalez@suse.com">jgonzalez@suse.com</a></p>
openSUSE admin - tickets #95045 (New): checksum failures - wrong name listed https://progress.opensuse.org/issues/950452021-07-03T08:26:10Znoel@ausat.net
<p>Seems there is a problem with your signing processes</p>
<p>D/l twice now over 2 days using 2 different mirrors, but no, same error. the plain DVD is looking for a snapshot file...</p>
<p>~$ ls -ls openSUSE-Tumbleweed-DVD-x86_64-Current.is*<br>
4560244 -rw-r--r-- 1 noel users 4665114624 Jul 3 18:11 openSUSE-Tumbleweed-DVD-x86_64-Current.iso<br>
8 -rw-r--r-- 1 noel users 124 Jul 3 17:43 openSUSE-Tumbleweed-DVD-x86_64-Current.iso.sha256</p>
<p>~$ sha256sum -c openSUSE-Tumbleweed-DVD-x86_64-Current.iso.sha256<br>
sha256sum: openSUSE-Tumbleweed-DVD-x86_64-Snapshot20210701-Media.iso: No such file or directory<br>
openSUSE-Tumbleweed-DVD-x86_64-Snapshot20210701-Media.iso: FAILED open or read<br>
sha256sum: WARNING: 1 listed file could not be read</p>
<p>-- <br>
Kind Regards,<br>
Noel Butler<br>
(b) <a href="https://blog.ausics.net" class="external">https://blog.ausics.net</a></p>
<p>This Email, including attachments, may contain sensitive and/or legally privileged information, therefore does at all times remain confidential and subject to copyright protected under international law. You may not disseminate any part of this message without the authors express written authority to do so. If you are not the intended recipient, please notify the sender then delete all copies of this message including attachments immediately. Confidentiality, copyright, and legal privilege are not waived or lost by reason of the mistaken delivery of this message.</p>
openSUSE Release Process - action #25216 (New): Transient errors and poor perf for PowerPC worker...https://progress.opensuse.org/issues/252162017-09-12T09:43:47Zmichel_mnonormand@linux.vnet.ibm.com
<p>As per irc chat with DimStar extracted below,<br>
there are problems on Power8 machines used for PowerPC workers used by OBS.</p>
<p>Could we have an analysing of the Power8 machines configurations (memory, perf, OS release/version)<br>
that could explain those problems ?</p>
<pre><code>```
10:32:40) DimStar: Good morning; I wanted to let you know that I'm going to remove ppc64le from the staging process - there are way too many random/weird fails and the build performance is 'low' - generally it slows down TW stagings, which in turn has negative impact on SLE
(10:42:25) michel_mno: Hello, I assume this will create more build errors detected only in the Factory::PowerPC
(10:47:28) DimStar: Sadly, yes - this is to be expected. But the fact that it's constantly the slowest arch to build, and the only one requesting me to trigger a build 10 times to get a successful build, makes it really painpuf
(10:47:45) DimStar: I will keep it in openSUSE:Factory:Rings - so it's also visible there
(11:01:07) DimStar: and if the situation improves, we can consider taking it in again (meaning: the rings do not show random broken build fails - and build performance is sort-of usable)
(11:02:21) michel_mno: DimStar who has access to those builders and responsible for their setup ?
(11:02:35) DimStar: on OBS? Adrian and his team
(11:02:40) michel_mno: I did not knew their were performance problem on them
(11:03:37) DimStar: would be greay if it turned out 'just' to be a config problem there
(11:04:20) DimStar: https://build.opensuse.org/package/live_build_log/openSUSE:Factory:Rings:2-TestDVD/hdf5/standard/ppc64le is one of the 'most annoying' packages failing on ppc64le (it takes ~ 30 minutes, and then fails 'a lot')
(11:09:32) michel_mno: I will check above; FYI yesterday I issued an osc build of Staging:A hdf5 and it passed without retry (it last 3994s)
(11:09:59) DimStar: lucky you :)
(11:11:06) DimStar: :J:DVD/hdf5 -> so far triggered 16 times - I would br REALLY surprised if anything in :J impacts the capability of hdf5 to build (it's a KDE stack upggrade)
(11:11:35) DimStar: K:DVD/hdf5 so far triggered 4 times
```
</code></pre>