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 #139304 (New): Request for a new devel project: devel:languages:harehttps://progress.opensuse.org/issues/1393042023-11-12T14:07:39Zsocvirnyl.estela@uncomfyhalomacro.pl
<p>Greetings openSUSE Team and Admin</p>
<p>I would like to request for a new devel project for <br>
<a href="https://harelang.org" class="external">https://harelang.org</a>, a new programming language written by Drew Devault.</p>
<p>The reasons for this is the language is fairly new and I think I made a <br>
mistake of adding it to openSUSE:Factory.</p>
<p>Once it reaches "stable", I will SR again to openSUSE:Factory. This also <br>
fixes the issue of using <em>newer</em> changes of QBE, a compiler backend that <br>
is used for hare by packaging the latest commit of QBE there as well. <br>
The QBE in <code>devel:tools:compiler</code> will be reverted back to point <br>
releases while this one will be renamed to fit with hare's dependency needs.</p>
<p>I hope my request will be given utmost consideration!</p>
<p>Thank you!</p>
<p>-- <br>
/Sincerely/</p>
<p><u><em>/Soc Virnyl Estela/</em></u></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 #135779 (Feedback): How's postfix mail queue doing?https://progress.opensuse.org/issues/1357792023-09-14T19:19:09Zluc14n0
<p>Yesterday - Wed Sep 13, 2023 -, or the day before, Icinga started showing an alarm (or maybe it was when I realized it, the alarm tells me it started 2d 4h ago) about Postfix mail queue been higher than its threshold for progress.i.o.o. Is this threshold there to avoid what exactly?</p>
<p><strong>progress.i.o.o</strong><br>
CRITICAL: <code>postfix mailq is 85 (threshold c = 50)</code></p>
<p>Other similar alarms that seem to be there for a while (or they come and go, I can't say right now):</p>
<p><strong>mailman3.i.o.o</strong></p>
<p>CRITICAL: <code>postfix mailq is 413 (threshold c = 50)</code></p>
<p><strong>openqa.i.o.o</strong></p>
<p>CRITICAL: <code>postfix mailq is 121 (threshold c = 50)</code></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 #134129 (New): Request for team project on build.opensuse.orghttps://progress.opensuse.org/issues/1341292023-08-11T10:53:46Zdominik.george@teckids.org
<p>Hi openSUSE admins,</p>
<p>we would like to provide openSUSE as alternative to Debian on<br>
the laptops we use for our workshops with children. Teckids<br>
is a German non-profit fostering self-determined use of<br>
technology for children and in education.</p>
<p>To build images based on openSUSE, we would like to use<br>
build.opensuse.org. The form to request a project states<br>
I should send mail to <a href="mailto:noreply@opensuse.org">noreply@opensuse.org</a>, but a chat on<br>
the OBS IRC channel suggested that admin@ might be more<br>
appropriate. It also concluded that probably, a project<br>
under the "isv:" namespace might be the way to go.</p>
<p>Therefore, I would like to request a project "Teckids" or<br>
"isv:Teckids".</p>
<p>My account on OBS is Klampfradler, which I am already using<br>
to contribute to Factory.</p>
<p>Kind regards,<br>
Nik</p>
<p>-- <br>
Dominik George (1. Vorstandsvorsitzender)<br>
Teckids e.V. — Digitale Freiheit mit Jugend und Bildung<br>
<a href="https://www.teckids.org/" class="external">https://www.teckids.org/</a></p>
openSUSE admin - tickets #124457 (Blocked): 2048 bit RSA intermediate at download.opensuse.orghttps://progress.opensuse.org/issues/1244572023-02-14T08:47:42Zmeissner@suse.demeissner@suse.de
<p>hi,</p>
<p>we received this:<br>
<a href="https://bugzilla.suse.com/show_bug.cgi?id=1208210" class="external">https://bugzilla.suse.com/show_bug.cgi?id=1208210</a></p>
<p>It seems genuine:</p>
<p>Certificate chain<br>
0 s:CN = opensuse.org<br>
i:C = US, O = Let's Encrypt, CN = R3<br>
a:PKEY: rsaEncryption, 4096 (bit); sigalg: RSA-SHA256<br>
v:NotBefore: Jan 9 00:42:31 2023 GMT; NotAfter: Apr 9 00:42:30 2023 GMT<br>
1 s:C = US, O = Let's Encrypt, CN = R3<br>
i:C = US, O = Internet Security Research Group, CN = ISRG Root X1<br>
a:PKEY: rsaEncryption, 2048 (bit); sigalg: RSA-SHA256<br>
v:NotBefore: Sep 4 00:00:00 2020 GMT; NotAfter: Sep 15 16:00:00 2025 GMT<br>
2 s:C = US, O = Internet Security Research Group, CN = ISRG Root X1<br>
i:O = Digital Signature Trust Co., CN = DST Root CA X3<br>
a:PKEY: rsaEncryption, 4096 (bit); sigalg: RSA-SHA256<br>
v:NotBefore: Jan 20 19:14:03 2021 GMT; NotAfter: Sep 30 18:14:03 2024 GMT</p>
<p>Can this be fixed?</p>
<p>Ciao, Marcus</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 #112208 (New): openSUSE-Leap-15.4-DVD-x86_64-Media.iso redirected to ope...https://progress.opensuse.org/issues/1122082022-06-08T14:24:00Zpjessenper@computer.org
<p>I don't know if this is actually an issue :-) </p>
<pre><code>wget -nd http://download.opensuse.org/distribution/leap/15.4/iso/openSUSE-Leap-15.4-DVD-x86_64-Media.iso
--2022-06-08 16:19:17-- http://download.opensuse.org/distribution/leap/15.4/iso/openSUSE-Leap-15.4-DVD-x86_64-Media.iso
Resolving download.opensuse.org (download.opensuse.org)... 195.135.221.134, 2001:67c:2178:8::13
Connecting to download.opensuse.org (download.opensuse.org)|195.135.221.134|:80... connected.
HTTP request sent, awaiting response... 302 Found
Location: /distribution/leap/15.4/iso/openSUSE-Leap-15.4-DVD-x86_64-Build243.2-Media.iso [following]
--2022-06-08 16:19:17-- http://download.opensuse.org/distribution/leap/15.4/iso/openSUSE-Leap-15.4-DVD-x86_64-Build243.2-Media.iso
Reusing existing connection to download.opensuse.org:80.
HTTP request sent, awaiting response... 302 Found
Location: http://mirrorcache-eu.opensuse.org/distribution/leap/15.4/iso/openSUSE-Leap-15.4-DVD-x86_64-Build243.2-Media.iso [following]
URL transformed to HTTPS due to an HSTS policy
--2022-06-08 16:19:17-- https://mirrorcache-eu.opensuse.org/distribution/leap/15.4/iso/openSUSE-Leap-15.4-DVD-x86_64-Build243.2-Media.iso
Resolving mirrorcache-eu.opensuse.org (mirrorcache-eu.opensuse.org)... 195.135.221.140, 2001:67c:2178:8::16
Connecting to mirrorcache-eu.opensuse.org (mirrorcache-eu.opensuse.org)|195.135.221.140|:443... connected.
HTTP request sent, awaiting response... 302 Found
Location: https://opensusemirror.lihaso.com//distribution/leap/15.4/iso/openSUSE-Leap-15.4-DVD-x86_64-Build243.2-Media.iso [following]
--2022-06-08 16:19:17-- https://opensusemirror.lihaso.com//distribution/leap/15.4/iso/openSUSE-Leap-15.4-DVD-x86_64-Build243.2-Media.iso
Resolving opensusemirror.lihaso.com (opensusemirror.lihaso.com)... 46.140.178.124
Connecting to opensusemirror.lihaso.com (opensusemirror.lihaso.com)|46.140.178.124|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 4083154944 (3.8G) [application/x-iso9660-image]
Saving to: ‘openSUSE-Leap-15.4-DVD-x86_64-Media.iso’
</code></pre>
<p>Should download.o.o really be giving me the symlink target <code>Location: /distribution/leap/15.4/iso/openSUSE-Leap-15.4-DVD-x86_64-Build243.2-Media.iso</code> ?<br><br>
There was already a question on the users list about the same - the iso was downloaded as <code>openSUSE-Leap-15.4-DVD-x86_64-Build243.2-Media.iso</code>, so when the user tried "sha256sum -c openSUSE-Leap-15.4-DVD-x86_64-Media.iso.sha256", it didn't work, file not found. </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 #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 admin - tickets #53462 (New): repopush - ftp.halifax.rwth-aachen.de - errorshttps://progress.opensuse.org/issues/534622019-06-22T13:32:21Zpjessenper@computer.org
<p>rsync: getaddrinfo 195.135.221.130: Address family for hostname not supported <br>
@ERROR: Unknown module 'opensuse-buildservice-push'</p>
<p>For now, I have updated the push script (/srv/bs/servers/ftp.halifax.rwth-aachen.de) to use '--address=stage.opensuse.org' instead of '--address=195.135.221.130'. Obviously this doesn't fix the rsync config ....</p>