Am 20.11.21 um 09:58 schrieb François Andriot:
>
>
> Le 20/11/2021 à 00:58, Peter Schlaf a écrit :
>> [...]
>>
>> Please check if the URIs defined for this repository are pointing
>> to a valid repository.
>> Skipping repository 'trinity' because of the above error.
>> Retrieving repository 'trinity-noarch' metadata
>> .....................................................................................................................................................................................[error]
>> Repository 'trinity-noarch' is invalid.
>> [trinity-noarch|http://mirror.ppa.trinitydesktop.org/trinity/rpm/opensuse15.…]
>> Valid metadata not found at specified URL
>> History:
>> - File
>> './repodata/df43098b8eb4b9b9c38b0bdd574746245eefd9ee3a6677672736a3db059791b9-primary.xml.gz'
>> not found on medium
>> 'http://mirror.ppa.trinitydesktop.org/trinity/rpm/opensuse15.3/trinity-r14/R…'
>> - Can't provide
>> ./repodata/df43098b8eb4b9b9c38b0bdd574746245eefd9ee3a6677672736a3db059791b9-primary.xml.gz
>>
>>
>
> Hello,
>
> I've updated the repository metadata, you can wait for the mirror to
> synchronize and try again.
>
> François
>
>
> ____________________________________________________
> tde-devels mailing list --devels(a)trinitydesktop.org
> To unsubscribe send an email todevels-leave(a)trinitydesktop.org
> Web mail archive available athttps://mail.trinitydesktop.org/mailman3/hyperkitty/list/devels@trinityde…
Hello,
the "Signature verification failure" message has disappeared.
Refresh and update are working again.
Great job!
Thank you very much.
CU
Peter
To whom it may concern...
On a new machine with openSuSE Leap 15.3 i did (as root and according to
https://wiki.trinitydesktop.org/OpenSUSE_Trinity_Repository_Installation_In…)
rpm --import http://mirror.ppa.trinitydesktop.org/trinity/rpm/opensuse15.3/RPM-GPG-KEY-t…
zypper ar http://mirror.ppa.trinitydesktop.org/trinity/rpm/opensuse15.3/trinity-r14/R… trinity
zypper ar http://mirror.ppa.trinitydesktop.org/trinity/rpm/opensuse15.3/trinity-r14/R… trinity-noarch
without a problem. But the next command
zypper refresh
produced this:
Retrieving repository 'trinity' metadata
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------[\]
Signature verification failed for file 'repomd.xml' from repository
'trinity'.
Note: Signing data enables the recipient to verify that no
modifications occurred after the data
were signed. Accepting data with no, wrong or unknown signature
can lead to a corrupted system
and in extreme cases even to a system compromise.
Note: File 'repomd.xml' is the repositories master index file.
It ensures the integrity of the
whole repo.
Warning: This file was modified after it has been signed. This
may have been a malicious change,
so it might not be trustworthy anymore! You should not continue
unless you know it's safe.
Signature verification failed for file 'repomd.xml' from repository
'trinity'. Continue? [yes/no] (no): no
Retrieving repository 'trinity' metadata
............................................................................................................................................................................................[error]
Repository 'trinity' is invalid.
[trinity|http://mirror.ppa.trinitydesktop.org/trinity/rpm/opensuse15.3/trini…]
Valid metadata not found at specified URL
History:
- Signature verification failed for repomd.xml
- Can't provide /repodata/repomd.xml
Please check if the URIs defined for this repository are pointing to
a valid repository.
Skipping repository 'trinity' because of the above error.
Retrieving repository 'trinity-noarch' metadata
.....................................................................................................................................................................................[error]
Repository 'trinity-noarch' is invalid.
[trinity-noarch|http://mirror.ppa.trinitydesktop.org/trinity/rpm/opensuse15.…]
Valid metadata not found at specified URL
History:
- File
'./repodata/df43098b8eb4b9b9c38b0bdd574746245eefd9ee3a6677672736a3db059791b9-primary.xml.gz'
not found on medium
'http://mirror.ppa.trinitydesktop.org/trinity/rpm/opensuse15.3/trinity-r14/R…'
- Can't provide
./repodata/df43098b8eb4b9b9c38b0bdd574746245eefd9ee3a6677672736a3db059791b9-primary.xml.gz
Please check if the URIs defined for this repository are pointing to
a valid repository.
Skipping repository 'trinity-noarch' because of the above error.
Some of the repositories have not been refreshed because of an error.
The mirrors on
https://ftp.fau.de/trinity/trinity/rpm/opensuse15.3/trinity-r14/RPMS/x86_64http://mirror.nasutek.com/trinity/trinity/rpm/opensuse15.3/trinity-r14/RPMS…http://tde-mirror.yosemite.net/trinity/rpm/opensuse15.3/trinity-r14/RPMS/x8…
are showing the same problem.
CU
Peter
Hi,
I recall there was somewhere a post regarding the coding style convention
and I am sure it is somewhere on the web site, but I could not find it in
5-10min time frame.
Can someone point me to it please?
thank you in advance
BR
--
FCD6 3719 0FFB F1BF 38EA 4727 5348 5F1F DCFE BCB0
nothing provides trinity-filesystem >= 14.0.11 needed by trinity-*-14.0.11, among
others.
--
Evolution as taught in public schools is, like religion,
based on faith, not based on science.
Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!
Felix Miata
I was wondering if the R14.0.11 testing was only available on Debian-based GNU/Linux (that I know of). On FreeBSD I attempted to switch the version in the Makefile from 14.0.10 to 14.0.11 out of curiosity and this doesn't work. can wait a couple of days but I was just wondering if the testing/experimental branch is available for other OSes. Maybe I misunderstand how different versions of Trinity are handled, but thanks for any insight in advance.
On Thu October 28 2021 01:27:17 Tim Bishop wrote:
> Thanks for letting me know. I've been on leave this week so hadn't
> noticed the disk fill up on kuiper. I took it out of the load balancer
> so it shouldn't have been serving clients. I've now freed up some space,
> let it hopefully catch up, and have put it back on the load balancer.
Hi Tim,
Look's good now. Thank you.
--Mike
Hi Tim,
I hope all is well with you in these Covid times.
You had requested a heads up if our mirror monitoring noticed
persistent significant differences between Kuiper and Copernicus.
> 5 files missing from copernicus.mirrorservice.org::trinitydesktop.org/
> 50485 files missing from kuiper.mirrorservice.org::trinitydesktop.org/
Thank you for mirroring Trinity Desktop Environment.
--Mike